{"generated_at":"2026-07-29T08:46:23.234561+00:00","corpus_anchor_id":"legal:eidas-consolidated","nodes":[{"id":"ARF TS01 V1.2","type":"specification","body":"ARF","designation":"TS01","version":"1.2","title":"Specification of EUDI Wallet Trust Mark","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts1-eudi-wallet-trust-mark.md"],"folder":"ARF/TS01-V1.2","files":{"md":{"path":"standards/ARF/TS01-V1.2/TS01-V1.2.md","sha256":"8aa27027c5734f813482466073ad208c8e91541fe70ddd132b4616042a784695"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the technical specification and requirements for EUDI Wallet Trust Mark.","scope_keywords":["eudi","trust","wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS01 1.2 Specification of EUDI Wallet Trust Mark The present document specifies the technical specification and requirements for EUDI Wallet Trust Mark. eudi trust wallet arf-technical-spec unchanged"},{"id":"ARF TS02 V1.0.1","type":"specification","body":"ARF","designation":"TS02","version":"1.0.1","title":"Specification of systems enabling the notification and subsequent publication of Provider information","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts2-notification-publication-provider-information.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts2-notification-publication-provider-information.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts2-notification-publication-provider-information.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts2-notification-publication-provider-information.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts2-notification-publication-provider-information.md"],"folder":"ARF/TS02-V1.0.1","files":{"md":{"path":"standards/ARF/TS02-V1.0.1/TS02-V1.0.1.md","sha256":"03862f0f99b2af1d9e4c6d84ce5654685e621f40e1ef9af430953d76e4c1344e"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the data model and systems enabling the notification and subsequent publication of Provider information.","scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS02 1.0.1 Specification of systems enabling the notification and subsequent publication of Provider information The present document specifies the data model and systems enabling the notification and subsequent publication of Provider information. arf-technical-spec unchanged"},{"id":"ARF TS03 V1.5.2","type":"specification","body":"ARF","designation":"TS03","version":"1.5.2","title":"Specification of Wallet Unit Attestations (WUA) used in issuance of PID and Attestations","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts3-wallet-unit-attestation.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts3-wallet-unit-attestation.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts3-wallet-unit-attestation.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts3-wallet-unit-attestation.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts3-wallet-unit-attestation.md"],"folder":"ARF/TS03-V1.5.2","files":{"md":{"path":"standards/ARF/TS03-V1.5.2/TS03-V1.5.2.md","sha256":"14d6c1f313cd28b28e38a0611328aba62bc8b34b8971064848a823f68fafa83d"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies how Wallet Unit Attestations (WUAs) -- comprising Wallet Instance Attestations (WIAs) and Key Attestations (KAs) -- are used in connection with PID Providers and Attestation Providers.","scope_keywords":["attestation","attestations","eudi","key","pid","wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS03 1.5.2 Specification of Wallet Unit Attestations (WUA) used in issuance of PID and Attestations The present document specifies how Wallet Unit Attestations (WUAs) -- comprising Wallet Instance Attestations (WIAs) and Key Attestations (KAs) -- are used in connection with PID Providers and Attestation Providers. attestation attestations eudi key pid wallet arf-technical-spec unchanged"},{"id":"ARF TS04 V1.0.1","type":"specification","body":"ARF","designation":"TS04","version":"1.0.1","title":"Specification for ZKP Implementation in EUDI Wallet","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts4-zkp.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts4-zkp.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts4-zkp.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts4-zkp.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts4-zkp.md"],"folder":"ARF/TS04-V1.0.1","files":{"md":{"path":"standards/ARF/TS04-V1.0.1/TS04-V1.0.1.md","sha256":"5ea7ef886e0d2da06308f937bc8848d89a15b76da37ba003c6bd372afa0cd451"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the technical specification and requirements for Zero-Knowledge Proof (ZKP) Implementation in EUDI Wallet.","scope_keywords":["eudi","wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS04 1.0.1 Specification for ZKP Implementation in EUDI Wallet The present document specifies the technical specification and requirements for Zero-Knowledge Proof (ZKP) Implementation in EUDI Wallet. eudi wallet arf-technical-spec unchanged"},{"id":"ARF TS05 V1.2.1","type":"specification","body":"ARF","designation":"TS05","version":"1.2.1","title":"Specification of common formats and API for Relying Party Registration information","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts5-common-formats-and-api-for-rp-registration-information.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts5-common-formats-and-api-for-rp-registration-information.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts5-common-formats-and-api-for-rp-registration-information.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts5-common-formats-and-api-for-rp-registration-information.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts5-common-formats-and-api-for-rp-registration-information.md"],"folder":"ARF/TS05-V1.2.1","files":{"md":{"path":"standards/ARF/TS05-V1.2.1/TS05-V1.2.1.md","sha256":"3260450645d27ca566ac8e8a1ced18094d6481dc787467349abf2bb5e5686979"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the data formats and application programming interface (API) for the machine-readable Relying Party Registration required by the European Digital Identity Regulation (EU 910/2014).","scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS05 1.2.1 Specification of common formats and API for Relying Party Registration information The present document specifies the data formats and application programming interface (API) for the machine-readable Relying Party Registration required by the European Digital Identity Regulation (EU 910/2014). arf-technical-spec unchanged"},{"id":"ARF TS06 V1.0.1","type":"specification","body":"ARF","designation":"TS06","version":"1.0.1","title":"Common Set of Relying Party Information to be Registered","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts6-common-set-of-rp-information-to-be-registered.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts6-common-set-of-rp-information-to-be-registered.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts6-common-set-of-rp-information-to-be-registered.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts6-common-set-of-rp-information-to-be-registered.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts6-common-set-of-rp-information-to-be-registered.md"],"folder":"ARF/TS06-V1.0.1","files":{"md":{"path":"standards/ARF/TS06-V1.0.1/TS06-V1.0.1.md","sha256":"ced31ac20a516f529b642fd8a46d2b49b533c2d415bff70c5b91bcd5d4871f8e"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the common data set required for Relying Party Registration as required by the European Digital Identity Regulation (EU 2024/1183).","scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS06 1.0.1 Common Set of Relying Party Information to be Registered The present document specifies the common data set required for Relying Party Registration as required by the European Digital Identity Regulation (EU 2024/1183). arf-technical-spec unchanged"},{"id":"ARF TS07 V0.11","type":"specification","body":"ARF","designation":"TS07","version":"0.11","title":"Specification of Common Interface for Data Deletion Requests to Relying Parties","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts7-common-interface-for-data-deletion-request.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts7-common-interface-for-data-deletion-request.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts7-common-interface-for-data-deletion-request.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts7-common-interface-for-data-deletion-request.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts7-common-interface-for-data-deletion-request.md"],"folder":"ARF/TS07-V0.11","files":{"md":{"path":"standards/ARF/TS07-V0.11/TS07-V0.11.md","sha256":"ac97dbeac075c143fb1a5e956a15da070b417d48fc8e6c41ec6f5eae99f10d1a"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the common protocols and interfaces according to Article 5a (5) (a) (ix) of\n(EU) No 910/2014 used by a Wallet Unit for invoking a suitable external application,\nsuch as a browser, an email client or a phone application, for requesting the\nerasure of personal data pursuant to Article 17 of Regulation (EU) 2016/679\nat a Wallet-Relying Party for personal data, which was previously provided by a Wallet Unit.","scope_keywords":["wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS07 0.11 Specification of Common Interface for Data Deletion Requests to Relying Parties The present document specifies the common protocols and interfaces according to Article 5a (5) (a) (ix) of\n(EU) No 910/2014 used by a Wallet Unit for invoking a suitable external application,\nsuch as a browser, an email client or a phone application, for requesting the\nerasure of personal data pursuant to Article 17 of Regulation (EU) 2016/679\nat a Wallet-Relying Party for personal data, which was previously provided by a Wallet Unit. wallet arf-technical-spec unchanged"},{"id":"ARF TS08 V0.11","type":"specification","body":"ARF","designation":"TS08","version":"0.11","title":"Specification of Common Interface for reporting of Relying Parties to Data Protection Authorities","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts8-common-interface-for-reporting-of-wrp-to-dpa.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts8-common-interface-for-reporting-of-wrp-to-dpa.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts8-common-interface-for-reporting-of-wrp-to-dpa.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts8-common-interface-for-reporting-of-wrp-to-dpa.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts8-common-interface-for-reporting-of-wrp-to-dpa.md"],"folder":"ARF/TS08-V0.11","files":{"md":{"path":"standards/ARF/TS08-V0.11/TS08-V0.11.md","sha256":"9b185b4e9e9cbb9ff5a1e628848104e49d5ddc71925cce3cdde3386193160c8d"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the common protocols and interfaces according to Article 5a (5) (a) (x) of\n(EU) No 910/2014 used by a Wallet Unit for reporting a Wallet-Relying Party\nto the competent national Data Protection Authority where an allegedly unlawful or\nsuspicious request for data is received.","scope_keywords":["wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS08 0.11 Specification of Common Interface for reporting of Relying Parties to Data Protection Authorities The present document specifies the common protocols and interfaces according to Article 5a (5) (a) (x) of\n(EU) No 910/2014 used by a Wallet Unit for reporting a Wallet-Relying Party\nto the competent national Data Protection Authority where an allegedly unlawful or\nsuspicious request for data is received. wallet arf-technical-spec unchanged"},{"id":"ARF TS09 V1.1","type":"specification","body":"ARF","designation":"TS09","version":"1.1","title":"Specification of Wallet to Wallet interactions","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts9-wallet-to-wallet-interactions.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts9-wallet-to-wallet-interactions.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts9-wallet-to-wallet-interactions.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts9-wallet-to-wallet-interactions.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts9-wallet-to-wallet-interactions.md"],"folder":"ARF/TS09-V1.1","files":{"md":{"path":"standards/ARF/TS09-V1.1/TS09-V1.1.md","sha256":"e0faadb1de355e40fdcb8fbb811900e48b02d94e7700dae554482194c6910b58"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the common protocols and interfaces according to Article 5a (4) (c) and Article 5a (5) (a) (vi) of\n(EU) No 910/2014 used by a Wallet Unit to interact with another\nWallet Unit.","scope_keywords":["wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS09 1.1 Specification of Wallet to Wallet interactions The present document specifies the common protocols and interfaces according to Article 5a (4) (c) and Article 5a (5) (a) (vi) of\n(EU) No 910/2014 used by a Wallet Unit to interact with another\nWallet Unit. wallet arf-technical-spec unchanged"},{"id":"ARF TS10 V1.2","type":"specification","body":"ARF","designation":"TS10","version":"1.2","title":"Data Portability and Download (Export)","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts10-data-portability-and-download-%28export%29.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts10-data-portability-and-download-%28export%29.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts10-data-portability-and-download-%28export%29.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts10-data-portability-and-download-%28export%29.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts10-data-portability-and-download-%28export%29.md"],"folder":"ARF/TS10-V1.2","files":{"md":{"path":"standards/ARF/TS10-V1.2/TS10-V1.2.md","sha256":"fd358293643ca3516203429e68ac54d91ab9ff3670d777e97cd7003857cebce1"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the common format and data set for the transaction log and the Migration Object, as well as protocols related to exporting those objects from a Wallet Unit and importing to another one in a backup, recovery and migration scenarios, as required by the European Digital Identity Regulation (EU 2024/1183) and CIR 2024/2979.","scope_keywords":["wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS10 1.2 Data Portability and Download (Export) The present document specifies the common format and data set for the transaction log and the Migration Object, as well as protocols related to exporting those objects from a Wallet Unit and importing to another one in a backup, recovery and migration scenarios, as required by the European Digital Identity Regulation (EU 2024/1183) and CIR 2024/2979. wallet arf-technical-spec unchanged"},{"id":"ARF TS11 V1.0.1","type":"specification","body":"ARF","designation":"TS11","version":"1.0.1","title":"Specification of interfaces and formats for the catalogue of attributes and the catalogue of attestations","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts11-interfaces-and-formats-for-catalogue-of-attributes-and-catalogue-of-schemes.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts11-interfaces-and-formats-for-catalogue-of-attributes-and-catalogue-of-schemes.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts11-interfaces-and-formats-for-catalogue-of-attributes-and-catalogue-of-schemes.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts11-interfaces-and-formats-for-catalogue-of-attributes-and-catalogue-of-schemes.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts11-interfaces-and-formats-for-catalogue-of-attributes-and-catalogue-of-schemes.md"],"folder":"ARF/TS11-V1.0.1","files":{"md":{"path":"standards/ARF/TS11-V1.0.1/TS11-V1.0.1.md","sha256":"22b73ecb74aa05ea8316767c46e53cb66aadcce34dc5e3b2e33d33e2fb944d06"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies the interfaces and formats of European Commission’s catalogue of attributes and catalogue of attestations required by the European Digital Identity Regulation (EU 910/2014). Specification includes a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable application programming interface (API) for management of machine-readable attestation schemas.\n\nManagement of attribute schemas for the core attributes listed in Appendix VI of the European Digital Identity Regulation (EU 910/2014) is proposed to be handled through the European Commission's OOTS services and infrastructure. This specification defines the data model to be used, and refers to the OOTS Common Services eDelivery (which uses ISO 15000-3:2022 as the basis of implementation) and ETSI technical specification 119 478 regarding implement","scope_keywords":["attestation","attestations","attribute","attributes","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS11 1.0.1 Specification of interfaces and formats for the catalogue of attributes and the catalogue of attestations The present document specifies the interfaces and formats of European Commission’s catalogue of attributes and catalogue of attestations required by the European Digital Identity Regulation (EU 910/2014). Specification includes a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable application programming interface (API) for management of machine-readable attestation schemas.\n\nManagement of attribute schemas for the core attributes listed in Appendix VI of the European Digital Identity Regulation (EU 910/2014) is proposed to be handled through the European Commission's OOTS services and infrastructure. This specification defines the data model to be used, and refers to the OOTS Common Services eDelivery (which uses ISO 15000-3:2022 as the basis of implementation) and ETSI technical specification 119 478 regarding implement attestation attestations attribute attributes delivery management arf-technical-spec unchanged"},{"id":"ARF TS12 V1.0.1","type":"specification","body":"ARF","designation":"TS12","version":"1.0.1","title":"Specification of Strong Customer Authentication (SCA) Implementation with the Wallet","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts12-electronic-payments-SCA-implementation-with-wallet.md"],"folder":"ARF/TS12-V1.0.1","files":{"md":{"path":"standards/ARF/TS12-V1.0.1/TS12-V1.0.1.md","sha256":"a8a7fd731c8a421c8d7236f1d5b40a798ff689fe3eeaf2e52d064548e525e2cb"}},"tags":["arf-technical-spec","unchanged"],"summary":"The present document specifies data structures and processing rules for conducting Strong Customer Authentication (SCA) according to [PSD2] with use of the European Digital Identity Wallets.","scope_keywords":["authentication","wallet","wallets"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS12 1.0.1 Specification of Strong Customer Authentication (SCA) Implementation with the Wallet The present document specifies data structures and processing rules for conducting Strong Customer Authentication (SCA) according to [PSD2] with use of the European Digital Identity Wallets. authentication wallet wallets arf-technical-spec unchanged"},{"id":"ARF TS13","type":"specification","body":"ARF","designation":"TS13","version":null,"title":"Specification of zk-SNARKs","purpose":null,"status":"error","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts13-zksnarks.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts13-zksnarks.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts13-zksnarks.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts13-zksnarks.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts13-zksnarks.md"],"folder":"ARF/TS13","files":{},"tags":["arf-technical-spec"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS13 Specification of zk-SNARKs arf-technical-spec"},{"id":"ARF TS14 V1.0","type":"specification","body":"ARF","designation":"TS14","version":"1.0","title":"Specification for the implementation of Zero-Knowledge Proofs based on multi-message signatures in the EUDI Wallet","purpose":null,"status":"unchanged","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts14-zkps-from-mms.md","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/blob/main/docs/technical-specifications/ts14-zkps-from-mms.md","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications/ts14-zkps-from-mms.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/main/docs/technical-specifications/ts14-zkps-from-mms.md","https://raw.githubusercontent.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/v3.0.0/docs/technical-specifications/ts14-zkps-from-mms.md"],"folder":"ARF/TS14-V1.0","files":{"md":{"path":"standards/ARF/TS14-V1.0/TS14-V1.0.md","sha256":"37748443d581d5d67a222d9bb26a870ba209145fa8b7d3c07dc5b15ace0bd020"}},"tags":["arf-technical-spec","unchanged"],"summary":"Multi-Message-Signature (MMS) schemes are a class of signature schemes that allows signing of multiple messages at once.\nMany MMS schemes are particularly friendly to Zero Knowledge Proof (ZKP) techniques, making them interesting in an EUDI wallet ecosystem context.\nOn the other hand, MMS schemes are relatively immature (when compared to more established digital signature schemes) and so require more effort to integrate into a digital ecosystem.","scope_keywords":["eudi","signature","wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF TS14 1.0 Specification for the implementation of Zero-Knowledge Proofs based on multi-message signatures in the EUDI Wallet Multi-Message-Signature (MMS) schemes are a class of signature schemes that allows signing of multiple messages at once.\nMany MMS schemes are particularly friendly to Zero Knowledge Proof (ZKP) techniques, making them interesting in an EUDI wallet ecosystem context.\nOn the other hand, MMS schemes are relatively immature (when compared to more established digital signature schemes) and so require more effort to integrate into a digital ecosystem. eudi signature wallet arf-technical-spec unchanged"},{"id":"ARF EC technical specifications (TS01–TS14) V3.0.0","type":"specification","body":"ARF","designation":"EC technical specifications (TS01–TS14)","version":"3.0.0","title":"EUDI Wallet ARF complementary technical specifications","purpose":null,"status":"downloaded","download_url":"https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications","download_urls":["https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/releases/tag/v3.0.0","https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/tree/v3.0.0/docs/technical-specifications","https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/tree/main/docs/technical-specifications"],"folder":"ARF","files":{},"tags":["arf-technical-spec"],"summary":"European Commission complementary technical specifications (TS01–TS14) aligned with EUDI Wallet Architecture and Reference Framework v3.0.0; each TS is synced under standards/ARF/<designation>-<version>/ (index: eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework@v3.0.0; full text: eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications@main).","scope_keywords":["attestation","eudi","pid","trust","wallet"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ARF EC technical specifications (TS01–TS14) 3.0.0 EUDI Wallet ARF complementary technical specifications European Commission complementary technical specifications (TS01–TS14) aligned with EUDI Wallet Architecture and Reference Framework v3.0.0; each TS is synced under standards/ARF/<designation>-<version>/ (index: eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework@v3.0.0; full text: eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications@main). attestation eudi pid trust wallet arf-technical-spec"},{"id":"CEN CEN/TS","type":"specification","body":"CEN","designation":"CEN/TS ","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:,25","download_urls":["https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:,25","https://www.cencenelec.eu/standards/"],"folder":"CEN/CEN-TS-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"}],"search_text":"CEN CEN/TS  nested-reference unavailable"},{"id":"ETSI EN 319 421 V1.3.1","type":"specification","body":"ETSI","designation":"EN 319 421","version":"1.3.1","title":"ETSI EN 319 421","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/319421/01.03.01_60/en_319421v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/319421/01.03.01_60/en_319421v010301p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/319421/01.03.01_20/en_319421v010301a.pdf"],"folder":"ETSI/EN-319-421-V1.3.1","files":{"pdf":{"path":"standards/ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","sha256":"672e730071a4e1a46760fa650fa52a41e969884b9d27fbbb3b6b8daad2f6d3c7"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, timestamping, trust services.","scope_keywords":["e-commerce","electronic signature","security","timestamping","trust services","319","421","archiving","authorization","identification","key","policies","policy","qualified","risk","signature"],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"},{"celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","id":"2025-2532","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2532/2025-2532.md","title":"Qualified electronic archiving services"}],"parent_specifications":[],"search_text":"ETSI EN 319 421 1.3.1 ETSI EN 319 421 Covers: e-commerce, electronic signature, security, timestamping, trust services. e-commerce electronic signature security timestamping trust services 319 421 archiving authorization identification key policies policy qualified risk signature 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1929 Qualified electronic time stamps 32025R1929 2025-2532 Qualified electronic archiving services 32025R2532"},{"id":"CEN CEN/TS 18170 V2025","type":"specification","body":"CEN","designation":"CEN/TS 18170","version":"2025","title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:18170,25","download_urls":["https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:18170,25","https://www.cencenelec.eu/standards/"],"folder":"CEN/CEN-TS-18170-V2025","files":{},"tags":["cited-by-eu-law","common-criteria","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"},{"celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","id":"2025-2532","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2532/2025-2532.md","title":"Qualified electronic archiving services"}],"parent_specifications":[],"search_text":"CEN CEN/TS 18170 2025 cited-by-eu-law common-criteria implementing-regulation unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162 2025-2532 Qualified electronic archiving services 32025R2532"},{"id":"legal:2025-2162","type":"legal_regulation","act_id":"2025-2162","title":"Accreditation of conformity assessment bodies","celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/99b393e7-b39f-11f0-b37f-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-2162/2025-2162.html","sha256":"e94ac9c98fc3ea6f81632c17a99cd8c92dfdd286bca066fb304035141d92986e","size":217758},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/99b393e7-b39f-11f0-b37f-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-2162/2025-2162.pdf","sha256":"36c99f0cb42d6fde9b287cf8383e8b04ad63a3ecca03e53fb8b392f961cc39e2","size":664557}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and the Council as regards the accreditation of conformity assessment bodies performing the assessment of qualified trust service providers and the qualified trust services they provide, the conformity assessment report and the conformity assessment scheme Pursuant to Articles 20(1) and 21(1) of Regulation (EU) No 910/2014, qualified trust service providers and the qualified trust services they provide are to be audited by conformity assessment bodies. The resulting conformity assessment reports confirm whether the requirements laid down in that Regulation and in Article 21 of Directive (EU) 2022/2555 of the European Parliament and of the Council  ( 2 ) are… ‘scheme owner’ means an entity or a group of entities which is responsible for developing and maintaining a conformity assessment scheme;","scope_keywords":["accreditation","article","assessment","bodies","certificate","certificates","conformity","council","directive","down","european","parliament","provide","providers","qualified","regulation","report","rules","scheme","service","services","subject","they","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.382887+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2162 Accreditation of conformity assessment bodies 32025R2162 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and the Council as regards the accreditation of conformity assessment bodies performing the assessment of qualified trust service providers and the qualified trust services they provide, the conformity assessment report and the conformity assessment scheme Pursuant to Articles 20(1) and 21(1) of Regulation (EU) No 910/2014, qualified trust service providers and the qualified trust services they provide are to be audited by conformity assessment bodies. The resulting conformity assessment reports confirm whether the requirements laid down in that Regulation and in Article 21 of Directive (EU) 2022/2555 of the European Parliament and of the Council  ( 2 ) are… ‘scheme owner’ means an entity or a group of entities which is responsible for developing and maintaining a conformity assessment scheme; accreditation article assessment bodies certificate certificates conformity council directive down european parliament provide providers qualified regulation report rules scheme service services subject they trust"},{"id":"legal:2025-2532","type":"legal_regulation","act_id":"2025-2532","title":"Qualified electronic archiving services","celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/d3945a29-daeb-11f0-8da2-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-2532/2025-2532.html","sha256":"cb920d9b75851f712fecc6b47fbce552323ce1e7f51fa560b5a27a78a449449f","size":60846},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/d3945a29-daeb-11f0-8da2-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-2532/2025-2532.pdf","sha256":"57c34f8fc5b638fb9cd0b357f1a50e176351c594a8efa77f0fa01fa3c328f05d","size":754546}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for qualified electronic archiving services By Regulation (EU) 2024/1183 of the European Parliament and of the Council  ( 2 ) , a list of new trust services and qualified trust services, including the qualified electronic archiving service, was introduced in Regulation (EU) No 910/2014. The Commission is to establish a list of reference standards and, where necessary, establish specifications for such services. Electronic archiving is a service for the receipt, storage, retrieval and deletion of electronic data and electronic documents to ensure their durability and legibility as well as to preserve their integrity, confidentiality and proof of origin throughout the preservation period. Qualified electronic archiving…","scope_keywords":["archiving","commission","council","data","documents","electronic","establish","european","integrity","list","origin","parliament","period","preservation","qualified","reference","regulation","service","services","signatures","specifications","standards","their","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.467104+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2532 Qualified electronic archiving services 32025R2532 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for qualified electronic archiving services By Regulation (EU) 2024/1183 of the European Parliament and of the Council  ( 2 ) , a list of new trust services and qualified trust services, including the qualified electronic archiving service, was introduced in Regulation (EU) No 910/2014. The Commission is to establish a list of reference standards and, where necessary, establish specifications for such services. Electronic archiving is a service for the receipt, storage, retrieval and deletion of electronic data and electronic documents to ensure their durability and legibility as well as to preserve their integrity, confidentiality and proof of origin throughout the preservation period. Qualified electronic archiving… archiving commission council data documents electronic establish european integrity list origin parliament period preservation qualified reference regulation service services signatures specifications standards their trust"},{"id":"CEN CEN/TS 419261 V2015","type":"specification","body":"CEN","designation":"CEN/TS 419261","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:419261,25","download_urls":["https://standards.cencenelec.eu/dyn/www/f?p=204:32:0::::FSP_PROJECT,FSP_LANG_ID:419261,25","https://www.cencenelec.eu/standards/"],"folder":"CEN/CEN-TS-419261-V2015","files":{},"tags":["cited-by-eu-law","implementing-regulation","trust-services","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"}],"parent_specifications":[],"search_text":"CEN CEN/TS 419261 2015 cited-by-eu-law implementing-regulation trust-services unavailable 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943"},{"id":"legal:2025-1943","type":"legal_regulation","act_id":"2025-1943","title":"Reference standards and validation procedures (QTSP)","celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/c3d31ae8-9d97-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1943/2025-1943.html","sha256":"5fd6f28c95fea3df07d0f1a0d4587dfaaea74c6fc4c671fa932f87853a9c58a2","size":176060},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/c3d31ae8-9d97-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1943/2025-1943.pdf","sha256":"a01ada3899bc226a92fb06bf42cef1bc4e5bfe9cbc08b8b5fb4130fdc7a7c728","size":580587}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for qualified certificates for electronic signatures and qualified certificates for electronic seals Qualified certificates for electronic signatures and qualified certificates for electronic seals play a crucial role in the digital business environment by promoting the transition from traditional paper-based processes to electronic equivalent ones. By linking electronic signature validation data or electronic seal validation data to a natural or legal person respectively and by confirming the name of that… The presumption of compliance laid down in Article 28(6) and Article 38(6) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the issuance of qualified certificates for electronic signatures and qualified…","scope_keywords":["article","certificate","certificates","council","data","electronic","european","http","natural","parliament","policy","profiles","qualified","reference","regulation","seal","seals","service","services","signature","signatures","standards","trust","validation"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.302771+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for qualified certificates for electronic signatures and qualified certificates for electronic seals Qualified certificates for electronic signatures and qualified certificates for electronic seals play a crucial role in the digital business environment by promoting the transition from traditional paper-based processes to electronic equivalent ones. By linking electronic signature validation data or electronic seal validation data to a natural or legal person respectively and by confirming the name of that… The presumption of compliance laid down in Article 28(6) and Article 38(6) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the issuance of qualified certificates for electronic signatures and qualified… article certificate certificates council data electronic european http natural parliament policy profiles qualified reference regulation seal seals service services signature signatures standards trust validation"},{"id":"ETSI EN 319 102-1 V1.4.1","type":"specification","body":"ETSI","designation":"EN 319 102-1","version":"1.4.1","title":"ETSI EN 319 102-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31910201/01.04.01_60/en_31910201v010401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31910201/01.04.01_60/en_31910201v010401p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31910201/01.04.01_20/en_31910201v010401a.pdf"],"folder":"ETSI/EN-319-102-1-V1.4.1","files":{"pdf":{"path":"standards/ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","sha256":"11168f0059997cb58915c83ec1347fc66fdbabcd827e5ca7c23ecaf3cf457b3d"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","nested-reference","trust-services","unchanged"],"summary":"Covers: electronic signature, security, trust services.","scope_keywords":["electronic signature","security","trust services","319","102-1","attribute","attributes","authorization","certificate","certificates","http","https","key","policy","presentation","preservation"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","id":"2025-1945","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1945/2025-1945.md","title":"Qualified certificates for signatures and seals"},{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 441","folder":"ETSI/TS-119-441-V1.2.1","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ETSI EN 319 102-1 1.4.1 ETSI EN 319 102-1 Covers: electronic signature, security, trust services. electronic signature security trust services 319 102-1 attribute attributes authorization certificate certificates http https key policy presentation preservation 319-series cited-by-eu-law implementing-regulation nested-reference trust-services unchanged 2025-1942 Recognition of qualified validation services 32025R1942 2025-1945 Qualified certificates for signatures and seals 32025R1945 2025-1946 Qualified preservation services for signatures and seals 32025R1946"},{"id":"legal:2025-1942","type":"legal_regulation","act_id":"2025-1942","title":"Recognition of qualified validation services","celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/fb634c13-9db7-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1942/2025-1942.html","sha256":"2cd7cdf85c0a8f990380a873992b9272867b6c924e99e6990a9f6090129817b3","size":102860},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/fb634c13-9db7-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1942/2025-1942.pdf","sha256":"dee6af13b0dbd6a7e8d080afea4604e926a2a01202e1ab126669f62050e89516","size":537268}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified validation services for qualified electronic signatures and qualified validation services for qualified electronic seals Qualified validation services for qualified electronic signatures and for qualified electronic seals ensure the integrity, authenticity and correctness of the process and results of the validation of qualified electronic signatures and of qualified electronic seals respectively. Those qualified trust services play a crucial role in the digital business environment by promoting the transition from traditional… The presumption of compliance laid down in Article 33(2) and Article (40) of Regulation (EU) No 910/2014 should only apply where qualified validation services for qualified electronic signatures and for qualified electronic…","scope_keywords":["apply","article","compliance","council","data","digital","down","electronic","european","http","laying","parliament","policy","qualified","regard","regards","regulation","rules","seals","services","signature","signatures","trust","validation"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.281242+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1942 Recognition of qualified validation services 32025R1942 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified validation services for qualified electronic signatures and qualified validation services for qualified electronic seals Qualified validation services for qualified electronic signatures and for qualified electronic seals ensure the integrity, authenticity and correctness of the process and results of the validation of qualified electronic signatures and of qualified electronic seals respectively. Those qualified trust services play a crucial role in the digital business environment by promoting the transition from traditional… The presumption of compliance laid down in Article 33(2) and Article (40) of Regulation (EU) No 910/2014 should only apply where qualified validation services for qualified electronic signatures and for qualified electronic… apply article compliance council data digital down electronic european http laying parliament policy qualified regard regards regulation rules seals services signature signatures trust validation"},{"id":"legal:2025-1945","type":"legal_regulation","act_id":"2025-1945","title":"Qualified certificates for signatures and seals","celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/dead57ac-9d97-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1945/2025-1945.html","sha256":"45105e39f05717000e78dac718743b399450f26336306c8a326f27172e3fefc9","size":58292},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/dead57ac-9d97-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1945/2025-1945.pdf","sha256":"6bf7de9160da98f73d89aae0779e7a722d2339b9fb28b0d5c312db2cb8f8ed59","size":503855}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the validation of qualified electronic signatures and of qualified electronic seals and the validation of advanced electronic signatures based on qualified certificates and of advanced electronic seals based on qualified certificates Qualified electronic signatures, qualified electronic seals, advanced electronic signatures based on qualified certificates for electronic signatures and advanced electronic seals based on qualified certificates for electronic seals, provided their validity can be confirmed, ensure to relying parties the integrity and authenticity of the signed or sealed data, and enhance the certainty regarding the identity of… The presumption of compliance laid down in Article 32(1), Article 40, Article 32a(3) and Article 40a of Regulation (EU)…","scope_keywords":["advanced","article","based","certificate","certificates","council","data","down","electronic","european","http","parliament","provided","qualified","regard","regards","regulation","rules","seals","signature","signatures","their","trust","validation"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.327932+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1945 Qualified certificates for signatures and seals 32025R1945 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the validation of qualified electronic signatures and of qualified electronic seals and the validation of advanced electronic signatures based on qualified certificates and of advanced electronic seals based on qualified certificates Qualified electronic signatures, qualified electronic seals, advanced electronic signatures based on qualified certificates for electronic signatures and advanced electronic seals based on qualified certificates for electronic seals, provided their validity can be confirmed, ensure to relying parties the integrity and authenticity of the signed or sealed data, and enhance the certainty regarding the identity of… The presumption of compliance laid down in Article 32(1), Article 40, Article 32a(3) and Article 40a of Regulation (EU)… advanced article based certificate certificates council data down electronic european http parliament provided qualified regard regards regulation rules seals signature signatures their trust validation"},{"id":"legal:2025-1946","type":"legal_regulation","act_id":"2025-1946","title":"Qualified preservation services for signatures and seals","celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/2fa94e9a-9d98-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1946/2025-1946.html","sha256":"a1e54901417db951b2adb46a9a5ec8fbc888c2ea19c936e4d83694dd4dcbffcc","size":73380},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/2fa94e9a-9d98-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1946/2025-1946.pdf","sha256":"c76af17d87b592f7dbe5d13f129a86d954826435119bdaa0685e4932d5a14bd2","size":513651}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified preservation services for qualified electronic signatures and for qualified electronic seals Qualified preservation services for qualified electronic signatures and for qualified electronic seals ensure the long-term integrity, authenticity, proof of existence and accessibility of preservation evidence of those electronic signatures and electronic seals. This allows the demonstration of their legal validity over extended periods of time and guarantees that they can be validated irrespective of future… The presumption of compliance laid down in Article 34(1a) and Article 40 of Regulation (EU) No 910/2014 should only apply where qualified preservation services for qualified electronic signatures and for qualified electronic seals comply with the…","scope_keywords":["application","apply","article","compliance","council","data","down","electronic","european","http","laying","parliament","preservation","qualified","regard","regards","regulation","rules","seals","service","services","signature","signatures","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.342569+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1946 Qualified preservation services for signatures and seals 32025R1946 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified preservation services for qualified electronic signatures and for qualified electronic seals Qualified preservation services for qualified electronic signatures and for qualified electronic seals ensure the long-term integrity, authenticity, proof of existence and accessibility of preservation evidence of those electronic signatures and electronic seals. This allows the demonstration of their legal validity over extended periods of time and guarantees that they can be validated irrespective of future… The presumption of compliance laid down in Article 34(1a) and Article 40 of Regulation (EU) No 910/2014 should only apply where qualified preservation services for qualified electronic signatures and for qualified electronic seals comply with the… application apply article compliance council data down electronic european http laying parliament preservation qualified regard regards regulation rules seals service services signature signatures trust"},{"id":"ETSI TS 119 441 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 441","version":"1.2.1","title":"ETSI TS 119 441","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.02.01_60/ts_119441v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.02.01_60/ts_119441v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.02.01_20/ts_119441v010201a.pdf"],"folder":"ETSI/TS-119-441-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","sha256":"2bc867376f2b3e6411f25a9ca9edac834a7516a27d0bb274dc0636ad4e4cbeb7"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: electronic signature, security, trust services.","scope_keywords":["electronic signature","security","trust services","119","441","authorization","http","https","key","policies","policy","presentation","qualified","risk","signature","signatures"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"}],"parent_specifications":[],"search_text":"ETSI TS 119 441 1.2.1 ETSI TS 119 441 Covers: electronic signature, security, trust services. electronic signature security trust services 119 441 authorization http https key policies policy presentation qualified risk signature signatures 119-series cited-by-eu-law implementing-regulation unchanged 2025-1942 Recognition of qualified validation services 32025R1942"},{"id":"ETSI EN 319 122-1 V1.3.1","type":"specification","body":"ETSI","designation":"EN 319 122-1","version":"1.3.1","title":"ETSI EN 319 122-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_20/en_31912201v010301a.pdf"],"folder":"ETSI/EN-319-122-1-V1.3.1","files":{"pdf":{"path":"standards/ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","sha256":"e99e76e519d9bd8e1410775bccedb1a588021e5e7c705c9fcc1f91c6a6227c21"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: ASN.1, CAdES, electronic signature, profile, security.","scope_keywords":["asn.1","cades","electronic signature","profile","security","319","122-1","attribute","attributes","authorization","http","https","key","ledger","qualified","signature"],"parent_legal_regulations":[{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"}],"parent_specifications":[],"search_text":"ETSI EN 319 122-1 1.3.1 ETSI EN 319 122-1 Covers: ASN.1, CAdES, electronic signature, profile, security. asn.1 cades electronic signature profile security 319 122-1 attribute attributes authorization http https key ledger qualified signature 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-2531 Qualified electronic ledgers 32025R2531"},{"id":"legal:2025-2531","type":"legal_regulation","act_id":"2025-2531","title":"Qualified electronic ledgers","celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/cbd048d0-daeb-11f0-8da2-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-2531/2025-2531.html","sha256":"59a927c37a98ac20d009012497fe173acd53b2bea32a5afea586ab7a31881abe","size":93940},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/cbd048d0-daeb-11f0-8da2-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-2531/2025-2531.pdf","sha256":"be7bf1cfb854f402481e0e8dc0e50df4aa8089979d792c581d7994b73dd2a34c","size":777193}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for qualified electronic ledgers By Regulation (EU) 2024/1183 of the European Parliament and of the Council  ( 2 ) , a list of new trust services and qualified trust services, including the recording of electronic data in a qualified electronic ledger, was introduced in Regulation (EU) No 910/2014. The Commission is to establish a list of reference standards and, where necessary, establish specifications for such services. An electronic ledger is a sequence of electronic data records which is to ensure the integrity of those data records and the accuracy of the chronological ordering of those records. In order to ensure that the recording of data in a qualified electronic ledger is chronologically ordered, consistent and…","scope_keywords":["commission","council","data","down","electronic","establish","european","http","https","ledger","ledgers","list","new","parliament","qualified","recording","records","reference","regards","regulation","services","specifications","standards","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.440900+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2531 Qualified electronic ledgers 32025R2531 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for qualified electronic ledgers By Regulation (EU) 2024/1183 of the European Parliament and of the Council  ( 2 ) , a list of new trust services and qualified trust services, including the recording of electronic data in a qualified electronic ledger, was introduced in Regulation (EU) No 910/2014. The Commission is to establish a list of reference standards and, where necessary, establish specifications for such services. An electronic ledger is a sequence of electronic data records which is to ensure the integrity of those data records and the accuracy of the chronological ordering of those records. In order to ensure that the recording of data in a qualified electronic ledger is chronologically ordered, consistent and… commission council data down electronic establish european http https ledger ledgers list new parliament qualified recording records reference regards regulation services specifications standards trust"},{"id":"ETSI EN 319 132-1 V1.3.1","type":"specification","body":"ETSI","designation":"EN 319 132-1","version":"1.3.1","title":"ETSI EN 319 132-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_20/en_31913201v010301a.pdf"],"folder":"ETSI/EN-319-132-1-V1.3.1","files":{"pdf":{"path":"standards/ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","sha256":"83fc87ee09de90274131a1f60cb73edb742cebc7cd8961342586ed06133664c5"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: electronic signature, security, XAdES, XML.","scope_keywords":["electronic signature","security","xades","xml","319","132-1","authorization","eudi","key","ledger","qualified","signature","signatures","trust","wallet","wallets"],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"},{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"}],"parent_specifications":[],"search_text":"ETSI EN 319 132-1 1.3.1 ETSI EN 319 132-1 Covers: electronic signature, security, XAdES, XML. electronic signature security xades xml 319 132-1 authorization eudi key ledger qualified signature signatures trust wallet wallets 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979 2025-2531 Qualified electronic ledgers 32025R2531"},{"id":"legal:2024-2979","type":"legal_regulation","act_id":"2024-2979","title":"Integrity and core functionalities of EUDI Wallets","celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/a7576de1-b1e0-11ef-acb1-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2024-2979/2024-2979.html","sha256":"ac7e5fff2a72a3bb4ad6fa442745e59ee59ad3e65dc578f6acdd6575040b8b5a","size":93583},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/a7576de1-b1e0-11ef-acb1-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2024-2979/2024-2979.pdf","sha256":"3e4a72ef042bba0904e3801ae92d9efd81235fe3e3a1eb7c84674a2c4b96a2e8","size":607301}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the integrity and core functionalities of European Digital Identity Wallets The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, for natural and legal persons, while ensuring the… ‘wallet secure cryptographic application’ means an application that manages critical assets by being linked to and using the cryptographic and non-cryptographic functions provided by the wallet secure cryptographic device;","scope_keywords":["access","across","application","attestations","attributes","commission","core","council","cryptographic","digital","european","framework","functionalities","identification","identity","integrity","parliament","provided","regulation","secure","services","union","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.055683+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the integrity and core functionalities of European Digital Identity Wallets The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, for natural and legal persons, while ensuring the… ‘wallet secure cryptographic application’ means an application that manages critical assets by being linked to and using the cryptographic and non-cryptographic functions provided by the wallet secure cryptographic device; access across application attestations attributes commission core council cryptographic digital european framework functionalities identification identity integrity parliament provided regulation secure services union wallet wallets"},{"id":"ETSI EN 319 142-1 V1.2.1","type":"specification","body":"ETSI","designation":"EN 319 142-1","version":"1.2.1","title":"ETSI EN 319 142-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_20/en_31914201v010201a.pdf"],"folder":"ETSI/EN-319-142-1-V1.2.1","files":{"pdf":{"path":"standards/ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","sha256":"93e01407673ae22bdd0fadfc3a85df76411f1cfb1a3b53db47326a9d9658efb3"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: electronic signature, PAdES, profile, security.","scope_keywords":["electronic signature","pades","profile","security","319","142-1","attribute","attributes","authorization","encryption","eudi","http","https","key","signature","signatures"],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI EN 319 142-1 1.2.1 ETSI EN 319 142-1 Covers: electronic signature, PAdES, profile, security. electronic signature pades profile security 319 142-1 attribute attributes authorization encryption eudi http https key signature signatures 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"legal:2026-1731","type":"legal_regulation","act_id":"2026-1731","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs","celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"sha256":"716f17c983e24d60d54e577a696e691518bc082330920298c6f7fe64c24d0f73","size":698370,"item_url":"http://publications.europa.eu/resource/cellar/802ddc72-856b-11f1-bf5e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2026-1731/2026-1731.html"},"pdf":{"sha256":"c8680b48a5ff5eb0f600c6e5aeaea775e8b2e31dbb0a10797b317bc9d4b6be1c","size":1692338,"item_url":"http://publications.europa.eu/resource/cellar/802ddc72-856b-11f1-bf5e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2026-1731/2026-1731.pdf"}},"search_text":"2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731 implementing_regulation implementing-acts"},{"id":"ETSI EN 319 162-1 V1.1.1","type":"specification","body":"ETSI","designation":"EN 319 162-1","version":"1.1.1","title":"ETSI EN 319 162-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31916201/01.01.01_60/en_31916201v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31916201/01.01.01_60/en_31916201v010101p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31916201/01.01.01_20/en_31916201v010101a.pdf"],"folder":"ETSI/EN-319-162-1-V1.1.1","files":{"pdf":{"path":"standards/ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","sha256":"05b434cdbfdd794d4041b5e16b291702c4236fc2c3261804b23b95faaf71ce87"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: ASiC, e-commerce, electronic signature, security.","scope_keywords":["asic","e-commerce","electronic signature","security","319","162-1","authorization","eudi","http","https","identification","key","registered","signature","signatures","subject"],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"}],"parent_specifications":[],"search_text":"ETSI EN 319 162-1 1.1.1 ETSI EN 319 162-1 Covers: ASiC, e-commerce, electronic signature, security. asic e-commerce electronic signature security 319 162-1 authorization eudi http https identification key registered signature signatures subject 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979"},{"id":"ETSI EN 319 162-2 V1.1.1","type":"specification","body":"ETSI","designation":"EN 319 162-2","version":"1.1.1","title":"ETSI EN 319 162-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319100_319199/31916202/01.01.01_60/en_31916202v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319100_319199/31916202/01.01.01_60/en_31916202v010101p.pdf","https://www.etsi.org/deliver/etsi_en/319100_319199/31916202/01.01.01_20/en_31916202v010101a.pdf"],"folder":"ETSI/EN-319-162-2-V1.1.1","files":{"pdf":{"path":"standards/ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf","sha256":"b1b489bea3c5ae12d028d6e800935e30126ef7237fc09f0d79395d8a51c2351b"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: ASiC, e-commerce, electronic signature, security.","scope_keywords":["asic","e-commerce","electronic signature","security","319","162-2","authorization","eudi","http","https","key","policy","registered","signature","signatures","subject"],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"}],"parent_specifications":[],"search_text":"ETSI EN 319 162-2 1.1.1 ETSI EN 319 162-2 Covers: ASiC, e-commerce, electronic signature, security. asic e-commerce electronic signature security 319 162-2 authorization eudi http https key policy registered signature signatures subject 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979"},{"id":"ETSI EN 319 401 V3.2.1","type":"specification","body":"ETSI","designation":"EN 319 401","version":"3.2.1","title":"ETSI EN 319 401","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.02.01_60/en_319401v030201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.02.01_60/en_319401v030201p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.02.01_20/en_319401v030201a.pdf"],"folder":"ETSI/EN-319-401-V3.2.1","files":{"pdf":{"path":"standards/ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf","sha256":"d978e757e8e1087aef78d7316e3bf309ef7a15e13e7163c30e11fd9f61c960ec"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","nested-reference","trust-services","unchanged"],"summary":"Covers: cybersecurity, electronic signature, provider, security, trust services.","scope_keywords":["cybersecurity","electronic signature","provider","security","trust services","319","401","attestation","attestations","attribute","attributes","authorization","certificate","certificates","key","management"],"parent_legal_regulations":[{"celex":"32025R1566","eli":"https://data.europa.eu/eli/reg_impl/2025/1566/oj/eng","id":"2025-1566","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1566/2025-1566.md","title":"Identity and recipients of qualified certificates"},{"celex":"32025R1567","eli":"https://data.europa.eu/eli/reg_impl/2025/1567/oj/eng","id":"2025-1567","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1567/2025-1567.md","title":"Remote qualified signature/seal creation devices"},{"celex":"32025R1569","eli":"https://data.europa.eu/eli/reg_impl/2025/1569/oj/eng","id":"2025-1569","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1569/2025-1569.md","title":"Verification of electronic attestations of attributes"},{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"},{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"},{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"},{"celex":"32025R2160","eli":"https://data.europa.eu/eli/reg_impl/2025/2160/oj/eng","id":"2025-2160","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2160/2025-2160.md","title":"Risk management for non-qualified trust service providers"},{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"},{"celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","id":"2025-2532","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2532/2025-2532.md","title":"Qualified electronic archiving services"},{"celex":"32026R1735","eli":"https://data.europa.eu/eli/reg_impl/2026/1735/oj/eng","id":"2026-1735","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1735/2026-1735.md","title":"Amending CIR 2025/1569 — electronic attestations of attributes (EAA)"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 431-1","folder":"ETSI/TS-119-431-1-V1.3.1","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf","version":"1.3.1"}],"search_text":"ETSI EN 319 401 3.2.1 ETSI EN 319 401 Covers: cybersecurity, electronic signature, provider, security, trust services. cybersecurity electronic signature provider security trust services 319 401 attestation attestations attribute attributes authorization certificate certificates key management 319-series cited-by-eu-law implementing-regulation nested-reference trust-services unchanged 2025-1566 Identity and recipients of qualified certificates 32025R1566 2025-1567 Remote qualified signature/seal creation devices 32025R1567 2025-1569 Verification of electronic attestations of attributes 32025R1569 2025-1929 Qualified electronic time stamps 32025R1929 2025-1942 Recognition of qualified validation services 32025R1942 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2025-1944 Qualified electronic registered delivery services 32025R1944 2025-1946 Qualified preservation services for signatures and seals 32025R1946 2025-2160 Risk management for non-qualified trust service providers 32025R2160 2025-2531 Qualified electronic ledgers 32025R2531 2025-2532 Qualified electronic archiving services 32025R2532 2026-1735 Amending CIR 2025/1569 — electronic attestations of attributes (EAA) 32026R1735"},{"id":"legal:2025-1566","type":"legal_regulation","act_id":"2025-1566","title":"Identity and recipients of qualified certificates","celex":"32025R1566","eli":"https://data.europa.eu/eli/reg_impl/2025/1566/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/9738ce8b-6cdd-11f0-bf4e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1566/2025-1566.html","sha256":"e5f933072b3c76a9e88d9f222a15eb66f380e7aa481d9d4955956bb9ff5f943e","size":26051},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/9738ce8b-6cdd-11f0-bf4e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1566/2025-1566.pdf","sha256":"4af0976d9f9304d468e2a0ec04d90544bba7e530bcf04c3951e6272d12773dda","size":477654}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for the verification of the identity and attributes of the person to whom the qualified certificate or the qualified electronic attestation of attributes is to be issued Article 24 of Regulation (EU) No 910/2014 requires that qualified trust service providers verify the identity and, if applicable, any specific attributes of a natural or legal person when issuing qualified certificates or qualified electronic attestations of attributes to that person. In order to ensure equal treatment and ability to trust the result of the verification process, verifications should be carried out in an equivalent manner by all qualified trust service providers when issuing a qualified certificate or a qualified electronic attestation of attributes. In…","scope_keywords":["article","attestation","attestations","attributes","certificate","certificates","council","electronic","european","http","identification","identity","parliament","person","process","providers","qualified","reference","regards","regulation","service","standards","trust","verification"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.149326+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1566 Identity and recipients of qualified certificates 32025R1566 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for the verification of the identity and attributes of the person to whom the qualified certificate or the qualified electronic attestation of attributes is to be issued Article 24 of Regulation (EU) No 910/2014 requires that qualified trust service providers verify the identity and, if applicable, any specific attributes of a natural or legal person when issuing qualified certificates or qualified electronic attestations of attributes to that person. In order to ensure equal treatment and ability to trust the result of the verification process, verifications should be carried out in an equivalent manner by all qualified trust service providers when issuing a qualified certificate or a qualified electronic attestation of attributes. In… article attestation attestations attributes certificate certificates council electronic european http identification identity parliament person process providers qualified reference regards regulation service standards trust verification"},{"id":"legal:2025-1567","type":"legal_regulation","act_id":"2025-1567","title":"Remote qualified signature/seal creation devices","celex":"32025R1567","eli":"https://data.europa.eu/eli/reg_impl/2025/1567/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/8a505cff-6cdd-11f0-bf4e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1567/2025-1567.html","sha256":"827de55730176c120628a972672ca99a2b82c0d39e22bd6a26e45676be5bf937","size":29116},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/8a505cff-6cdd-11f0-bf4e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1567/2025-1567.pdf","sha256":"aefd18408155044b3cde95c80d2fd236893756c9b29d3083bd66b854f3348e56","size":481239}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the management of remote qualified electronic signature creation devices and of remote qualified electronic seal creation devices as qualified trust services Qualified trust services for the management of remote qualified electronic signature creation devices and for the management of remote qualified electronic seal creation devices play a crucial role in the digital business environment by promoting the transition from traditional paper-based processes to electronic equivalents. Those qualified trust services contribute to a secure and trustworthy management of… To enhance the legal certainty and trustworthiness of qualified trust services for the management of remote qualified electronic signature creation devices and qualified trust services for the…","scope_keywords":["application","article","council","creation","data","devices","digital","electronic","european","http","management","parliament","qualified","regard","regards","regulation","remote","seal","service","services","signature","signatures","trust","trustworthiness"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.162009+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1567 Remote qualified signature/seal creation devices 32025R1567 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the management of remote qualified electronic signature creation devices and of remote qualified electronic seal creation devices as qualified trust services Qualified trust services for the management of remote qualified electronic signature creation devices and for the management of remote qualified electronic seal creation devices play a crucial role in the digital business environment by promoting the transition from traditional paper-based processes to electronic equivalents. Those qualified trust services contribute to a secure and trustworthy management of… To enhance the legal certainty and trustworthiness of qualified trust services for the management of remote qualified electronic signature creation devices and qualified trust services for the… application article council creation data devices digital electronic european http management parliament qualified regard regards regulation remote seal service services signature signatures trust trustworthiness"},{"id":"legal:2025-1569","type":"legal_regulation","act_id":"2025-1569","title":"Verification of electronic attestations of attributes","celex":"32025R1569","eli":"https://data.europa.eu/eli/reg_impl/2025/1569/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/990be0dd-6cdd-11f0-bf4e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1569/2025-1569.html","sha256":"23c8a3afa32dabf28c76ed30529cba0f7fcf93dbb4ef22d58f070dd02b9fcfd6","size":98096},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/990be0dd-6cdd-11f0-bf4e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1569/2025-1569.pdf","sha256":"9e763ef037964c10385c43abfc73f7ae8d032c55c3a64229b6b834a5475600bd","size":596450}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified electronic attestations of attributes and electronic attestations of attributes provided by or on behalf of a public sector body responsible for an authentic source Regulation (EU) No 910/2014 creates a legal framework for the issuance and validation of electronic attestations of attrib.utes, including an obligation for providers of electronic attestations of attributes to provide European Digital Identity Wallet (‘wallet’) users with the possibility to request, obtain, store and manage the electronic attestation of attributes irrespective of the Member State where the… ‘wallet unit’ means a unique configuration of a wallet solution that includes wallet instances, wallet secure cryptographic applications and wallet secure cryptographic devices provided…","scope_keywords":["attestation","attestations","attributes","authentic","behalf","body","digital","electronic","european","framework","identity","member","parliament","provided","providers","public","qualified","regulation","responsible","sector","source","validation","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.207907+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1569 Verification of electronic attestations of attributes 32025R1569 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified electronic attestations of attributes and electronic attestations of attributes provided by or on behalf of a public sector body responsible for an authentic source Regulation (EU) No 910/2014 creates a legal framework for the issuance and validation of electronic attestations of attrib.utes, including an obligation for providers of electronic attestations of attributes to provide European Digital Identity Wallet (‘wallet’) users with the possibility to request, obtain, store and manage the electronic attestation of attributes irrespective of the Member State where the… ‘wallet unit’ means a unique configuration of a wallet solution that includes wallet instances, wallet secure cryptographic applications and wallet secure cryptographic devices provided… attestation attestations attributes authentic behalf body digital electronic european framework identity member parliament provided providers public qualified regulation responsible sector source validation wallet wallets"},{"id":"legal:2025-1929","type":"legal_regulation","act_id":"2025-1929","title":"Qualified electronic time stamps","celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/31a2d4ad-9d98-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1929/2025-1929.html","sha256":"835e781cf749d86666a81b4faed073d507b8603c271e79ca8fdcf0bd12dbb0bf","size":86495},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/31a2d4ad-9d98-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1929/2025-1929.pdf","sha256":"30e21df469306e69584ca2e95e2165bd2cf1d04fbc9f8f74b8551a67270edade","size":523779}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the binding of date and time to data and establishing the accuracy of the time sources for the provision of qualified electronic time stamps Qualified electronic time stamps play a crucial role in the digital environment by promoting the transition from traditional paper-based processes to electronic equivalents. By binding date and time information to electronic data, qualified electronic time stamps help ensuring the accuracy of date and time they indicate and the integrity of digital documents to which the date and time are bound. The presumption of compliance laid down in Article 42(1a) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the issuance of qualified time stamps comply with the standards set out in this…","scope_keywords":["accuracy","apply","article","binding","compliance","council","data","date","digital","down","electronic","european","http","information","parliament","qualified","regards","regulation","service","services","stamps","standards","time","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.266317+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1929 Qualified electronic time stamps 32025R1929 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the binding of date and time to data and establishing the accuracy of the time sources for the provision of qualified electronic time stamps Qualified electronic time stamps play a crucial role in the digital environment by promoting the transition from traditional paper-based processes to electronic equivalents. By binding date and time information to electronic data, qualified electronic time stamps help ensuring the accuracy of date and time they indicate and the integrity of digital documents to which the date and time are bound. The presumption of compliance laid down in Article 42(1a) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the issuance of qualified time stamps comply with the standards set out in this… accuracy apply article binding compliance council data date digital down electronic european http information parliament qualified regards regulation service services stamps standards time trust"},{"id":"legal:2025-1944","type":"legal_regulation","act_id":"2025-1944","title":"Qualified electronic registered delivery services","celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/d8575546-9d97-11f0-97c8-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1944/2025-1944.html","sha256":"726c6fc75820068633d1b4d64f93604bf14445c7145c3fa12a5c1f046760ba8d","size":86721},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/d8575546-9d97-11f0-97c8-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1944/2025-1944.pdf","sha256":"ad8e3d12ac7455ad46b25371ae051658fa11ded70d7936b06e5f7e21470e0b19","size":527934}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for processes for sending and receiving data in qualified electronic registered delivery services and as regards interoperability of those services Qualified electronic registered delivery services provide a secure channel for the transmission of documents, including proof of sending and receiving the data. They aim at providing certainty in identifying the addressee and ensure a high level of confidence in the identification of the sender. The presumption of compliance laid down in Article 44(1a) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the provision of qualified electronic registered delivery services comply with the standards set out in this Regulation. These standards should reflect established…","scope_keywords":["article","council","data","delivery","down","electronic","eli","european","http","identification","out","parliament","qualified","reference","regards","registered","regulation","sending","service","services","set","signatures","standards","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.316312+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1944 Qualified electronic registered delivery services 32025R1944 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for processes for sending and receiving data in qualified electronic registered delivery services and as regards interoperability of those services Qualified electronic registered delivery services provide a secure channel for the transmission of documents, including proof of sending and receiving the data. They aim at providing certainty in identifying the addressee and ensure a high level of confidence in the identification of the sender. The presumption of compliance laid down in Article 44(1a) of Regulation (EU) No 910/2014 should only apply where qualified trust services for the provision of qualified electronic registered delivery services comply with the standards set out in this Regulation. These standards should reflect established… article council data delivery down electronic eli european http identification out parliament qualified reference regards registered regulation sending service services set signatures standards trust"},{"id":"legal:2025-2160","type":"legal_regulation","act_id":"2025-2160","title":"Risk management for non-qualified trust service providers","celex":"32025R2160","eli":"https://data.europa.eu/eli/reg_impl/2025/2160/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/99582d76-b39f-11f0-b37f-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-2160/2025-2160.html","sha256":"2a4ae9ca1a2277100c05aaff58a64fe31eeeca4d959e66fe5fcd756bd4b4bcaa","size":48908},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/99582d76-b39f-11f0-b37f-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-2160/2025-2160.pdf","sha256":"e9d4815d67f154c00caa8007fc41449a7f4098a0d1137493184647c65d9fa1ab","size":512230}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards, specifications and procedures for the management of risks to the provision of non-qualified trust services Non-qualified trust service providers play an important role in the digital environment by providing trust services that facilitate secure electronic transactions. Regulation (EU) No 910/2014 places fewer regulatory requirements on non-qualified trust service providers than on qualified trust service providers. However, all trust service providers are subject to requirements on security and liability to ensure… Non-qualified trust service providers can be considered important or essential entities in accordance with Article 3 of Directive (EU) 2022/2555 of the European Parliament and of the Council  ( 2 ) . Thus, Commission Implementing…","scope_keywords":["accordance","article","commission","council","directive","down","ensure","european","implementing","management","non-qualified","parliament","procedures","providers","qualified","regulation","risk","risks","service","services","specifications","standards","subject","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.356443+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2160 Risk management for non-qualified trust service providers 32025R2160 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards, specifications and procedures for the management of risks to the provision of non-qualified trust services Non-qualified trust service providers play an important role in the digital environment by providing trust services that facilitate secure electronic transactions. Regulation (EU) No 910/2014 places fewer regulatory requirements on non-qualified trust service providers than on qualified trust service providers. However, all trust service providers are subject to requirements on security and liability to ensure… Non-qualified trust service providers can be considered important or essential entities in accordance with Article 3 of Directive (EU) 2022/2555 of the European Parliament and of the Council  ( 2 ) . Thus, Commission Implementing… accordance article commission council directive down ensure european implementing management non-qualified parliament procedures providers qualified regulation risk risks service services specifications standards subject trust"},{"id":"legal:2026-1735","type":"legal_regulation","act_id":"2026-1735","title":"Amending CIR 2025/1569 — electronic attestations of attributes (EAA)","celex":"32026R1735","eli":"https://data.europa.eu/eli/reg_impl/2026/1735/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"sha256":"5c1546cdd7c673694780e978cc75ab1af0963df6d5bdf6664bdf036baacd0b76","size":77165,"item_url":"http://publications.europa.eu/resource/cellar/f0386031-856a-11f1-bf5e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2026-1735/2026-1735.html"},"pdf":{"sha256":"a014d6b100160ae66de2b842c6712ceedf6cc065d5c633d0d81f256d75891cee","size":535382,"item_url":"http://publications.europa.eu/resource/cellar/f0386031-856a-11f1-bf5e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2026-1735/2026-1735.pdf"}},"search_text":"2026-1735 Amending CIR 2025/1569 — electronic attestations of attributes (EAA) 32026R1735 implementing_regulation implementing-acts"},{"id":"ETSI TS 119 431-1 V1.3.1","type":"specification","body":"ETSI","designation":"TS 119 431-1","version":"1.3.1","title":"ETSI TS 119 431-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11943101/01.03.01_60/ts_11943101v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11943101/01.03.01_60/ts_11943101v010301p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11943101/01.03.01_20/ts_11943101v010301a.pdf"],"folder":"ETSI/TS-119-431-1-V1.3.1","files":{"pdf":{"path":"standards/ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf","sha256":"005516006e7558354bd4634663fa21fc1b5d944a53679d5877b4f18c292087c7"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: e-commerce, electronic signature, remote, security, trust services.","scope_keywords":["e-commerce","electronic signature","remote","security","trust services","119","431-1","authorization","identification","key","policies","policy","presentation","qualified","seal","signature"],"parent_legal_regulations":[{"celex":"32025R1567","eli":"https://data.europa.eu/eli/reg_impl/2025/1567/oj/eng","id":"2025-1567","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1567/2025-1567.md","title":"Remote qualified signature/seal creation devices"}],"parent_specifications":[],"search_text":"ETSI TS 119 431-1 1.3.1 ETSI TS 119 431-1 Covers: e-commerce, electronic signature, remote, security, trust services. e-commerce electronic signature remote security trust services 119 431-1 authorization identification key policies policy presentation qualified seal signature 119-series cited-by-eu-law implementing-regulation unchanged 2025-1567 Remote qualified signature/seal creation devices 32025R1567"},{"id":"ETSI EN 319 403-1 V2.3.1","type":"specification","body":"ETSI","designation":"EN 319 403-1","version":"2.3.1","title":"ETSI EN 319 403-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31940301/02.03.01_60/en_31940301v020301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31940301/02.03.01_60/en_31940301v020301p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31940301/02.03.01_20/en_31940301v020301a.pdf"],"folder":"ETSI/EN-319-403-1-V2.3.1","files":{"pdf":{"path":"standards/ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","sha256":"d5d20556966e8b7fb9cf3b50fe5d09dc2cf91588debbc72b426fc1e78e93bb9a"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: conformity, e-commerce, electronic signature, security, trust services.","scope_keywords":["conformity","e-commerce","electronic signature","security","trust services","319","403-1","accreditation","audit","authorization","certificate","certificates","http","https","key","license"],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ETSI EN 319 403-1 2.3.1 ETSI EN 319 403-1 Covers: conformity, e-commerce, electronic signature, security, trust services. conformity e-commerce electronic signature security trust services 319 403-1 accreditation audit authorization certificate certificates http https key license 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ETSI EN 319 403 V2.3.0","type":"specification","body":"ETSI","designation":"EN 319 403","version":"2.3.0","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/319403/02.03.00_60/en_319403v020300p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/319403/02.03.00_60/en_319403v020300p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/319403/02.03.00_20/en_319403v020300a.pdf"],"folder":"ETSI/EN-319-403-V2.3.0","files":{},"tags":["319-series","nested-reference","trust-services","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"}],"search_text":"ETSI EN 319 403 2.3.0 319-series nested-reference trust-services unavailable"},{"id":"ETSI EN 319 411-1 V1.5.1","type":"specification","body":"ETSI","designation":"EN 319 411-1","version":"1.5.1","title":"ETSI EN 319 411-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941101/01.05.01_60/en_31941101v010501p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941101/01.05.01_60/en_31941101v010501p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941101/01.05.01_20/en_31941101v010501a.pdf"],"folder":"ETSI/EN-319-411-1-V1.5.1","files":{"pdf":{"path":"standards/ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","sha256":"273705802db7e2c68574ae83f169c1dbaa50b30f18f0ad7e8dfa23d606e425c6"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-commerce, electronic signature, extended validation certificate, public key, security, trust services.","scope_keywords":["e-commerce","electronic signature","extended validation certificate","public key","security","trust services","319","411-1","authorization","certificate","certificates","delivery","identification","key","pki","policies"],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[],"search_text":"ETSI EN 319 411-1 1.5.1 ETSI EN 319 411-1 Covers: e-commerce, electronic signature, extended validation certificate, public key, security, trust services. e-commerce electronic signature extended validation certificate public key security trust services 319 411-1 authorization certificate certificates delivery identification key pki policies 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ETSI EN 319 411-2 V2.6.1","type":"specification","body":"ETSI","designation":"EN 319 411-2","version":"2.6.1","title":"ETSI EN 319 411-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_20/en_31941102v020601a.pdf"],"folder":"ETSI/EN-319-411-2-V2.6.1","files":{"pdf":{"path":"standards/ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf","sha256":"480d0770414e3fa6adaa52fa5ebe0931186e8c43bf63836ad0bc166ba964989a"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","319","411-2","authentication","authorization","certificate","certificates","identification","key","pki","policies","policy","qtsp"],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32025R2527","eli":"https://data.europa.eu/eli/reg_impl/2025/2527/oj/eng","id":"2025-2527","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2527/2025-2527.md","title":"Qualified certificates for website authentication"}],"parent_specifications":[],"search_text":"ETSI EN 319 411-2 2.6.1 ETSI EN 319 411-2 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 319 411-2 authentication authorization certificate certificates identification key pki policies policy qtsp 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2025-2527 Qualified certificates for website authentication 32025R2527"},{"id":"legal:2025-2527","type":"legal_regulation","act_id":"2025-2527","title":"Qualified certificates for website authentication","celex":"32025R2527","eli":"https://data.europa.eu/eli/reg_impl/2025/2527/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/97a07e59-daec-11f0-8da2-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-2527/2025-2527.html","sha256":"6740c4702f84d990c441e85d2bfadbdbbb1d2db76200366ef955484d15568f83","size":18944},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/97a07e59-daec-11f0-8da2-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-2527/2025-2527.pdf","sha256":"421b3186a650a3812809d230ce5c56e70d114f89c89f23c58e9fb33cf5afaee1","size":474645}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for qualified certificates for website authentication Qualified certificates for website authentication are essential for ensuring trust and transparency in online interactions. They make it possible to authenticate a website and link the website to the natural or legal person to whom the certificate is issued. The Commission is to establish a list of reference standards for such certificates. The reference standards should allow for the implementation of different types of qualified certificates for website authentication for various use cases, including their use under Directive (EU) 2015/2366 of the European Parliament and of the Council  ( 2 ) . They should reflect established practices and be widely recognised within the relevant…","scope_keywords":["authentication","certificate","certificates","commission","council","data","directive","european","http","issued","laying","natural","parliament","policy","practices","qualified","reference","regard","regards","regulation","standards","they","trust","website"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.393440+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2527 Qualified certificates for website authentication 32025R2527 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards for qualified certificates for website authentication Qualified certificates for website authentication are essential for ensuring trust and transparency in online interactions. They make it possible to authenticate a website and link the website to the natural or legal person to whom the certificate is issued. The Commission is to establish a list of reference standards for such certificates. The reference standards should allow for the implementation of different types of qualified certificates for website authentication for various use cases, including their use under Directive (EU) 2015/2366 of the European Parliament and of the Council  ( 2 ) . They should reflect established practices and be widely recognised within the relevant… authentication certificate certificates commission council data directive european http issued laying natural parliament policy practices qualified reference regard regards regulation standards they trust website"},{"id":"ETSI EN 319 412-1 V1.7.0","type":"specification","body":"ETSI","designation":"EN 319 412-1","version":"1.7.0","title":null,"purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941201/01.07.00_20/en_31941201v010700a.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941201/01.07.00_60/en_31941201v010700p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941201/01.07.00_20/en_31941201v010700a.pdf"],"folder":"ETSI/EN-319-412-1-V1.7.0","files":{"pdf":{"path":"standards/ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","sha256":"196c7eca2f649af100146173f2fe93909dc696e6dfecfe3a79d8c17ff1d4a2ff"}},"tags":["319-series","trust-services","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","319","412-1","authorization","certificate","eidas","key","profile","profiles","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ETSI EN 319 412-1 1.7.0 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 319 412-1 authorization certificate eidas key profile profiles signature signatures trust 319-series trust-services unchanged"},{"id":"ETSI EN 319 412-2 V2.4.1","type":"specification","body":"ETSI","designation":"EN 319 412-2","version":"2.4.1","title":"ETSI EN 319 412-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941202/02.04.01_60/en_31941202v020401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941202/02.04.01_60/en_31941202v020401p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941202/02.04.01_20/en_31941202v020401a.pdf"],"folder":"ETSI/EN-319-412-2-V2.4.1","files":{"pdf":{"path":"standards/ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","sha256":"5531054bdca3d5786fdc62d5d3bcbd9e735fcb0fab73a4e5794781471ab9c065"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: electronic signature, profile, security, trust services.","scope_keywords":["electronic signature","profile","security","trust services","319","412-2","authorization","certificate","certificates","issuer","key","policies","policy","profiles","qtsp","signature"],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI EN 319 412-2 2.4.1 ETSI EN 319 412-2 Covers: electronic signature, profile, security, trust services. electronic signature profile security trust services 319 412-2 authorization certificate certificates issuer key policies policy profiles qtsp signature 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI EN 319 412-3 V1.3.1","type":"specification","body":"ETSI","designation":"EN 319 412-3","version":"1.3.1","title":"ETSI EN 319 412-3","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941203/01.03.01_60/en_31941203v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941203/01.03.01_60/en_31941203v010301p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941203/01.03.01_20/en_31941203v010301a.pdf"],"folder":"ETSI/EN-319-412-3-V1.3.1","files":{"pdf":{"path":"standards/ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf","sha256":"13701a6a3ca96b24ee4cfd3ac0114a42658e901db18093a1be7b9dd88faeb5cc"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: electronic signature, profile, security, trust services.","scope_keywords":["electronic signature","profile","security","trust services","319","412-3","authorization","certificate","certificates","http","https","key","policy","profiles","qtsp","registered"],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI EN 319 412-3 1.3.1 ETSI EN 319 412-3 Covers: electronic signature, profile, security, trust services. electronic signature profile security trust services 319 412-3 authorization certificate certificates http https key policy profiles qtsp registered 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI EN 319 412-4 V1.3.0","type":"specification","body":"ETSI","designation":"EN 319 412-4","version":"1.3.0","title":null,"purpose":null,"status":"downloaded","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941204/01.03.00_20/en_31941204v010300a.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941204/01.03.00_60/en_31941204v010300p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941204/01.03.00_20/en_31941204v010300a.pdf"],"folder":"ETSI/EN-319-412-4-V1.3.0","files":{"pdf":{"path":"standards/ETSI/EN-319-412-4-V1.3.0/EN-319-412-4-V1.3.0.pdf","sha256":"385ee2d1a475cea4a64583f14449a70b3b4520e69c1d582c0fd291304f0ff511"}},"tags":["319-series","downloaded","nested-reference","trust-services"],"summary":"Covers: electronic signature, profile, security, trust services.","scope_keywords":["electronic signature","profile","security","trust services","319","412-4","authorization","certificate","certificates","http","https","key","policies","policy","profiles","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"}],"search_text":"ETSI EN 319 412-4 1.3.0 Covers: electronic signature, profile, security, trust services. electronic signature profile security trust services 319 412-4 authorization certificate certificates http https key policies policy profiles qualified 319-series downloaded nested-reference trust-services"},{"id":"ETSI TS 119 495 V1.7.1","type":"specification","body":"ETSI","designation":"TS 119 495","version":"1.7.1","title":"ETSI TS 119 495","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119495/01.07.01_60/ts_119495v010701p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119495/01.07.01_60/ts_119495v010701p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119495/01.07.01_20/ts_119495v010701a.pdf"],"folder":"ETSI/TS-119-495-V1.7.1","files":{"pdf":{"path":"standards/ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","sha256":"37cf7c67d5f6d0ae8632385810b23b8168a6c9ef90828b8f69436578dd138f77"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: e-commerce, electronic signature, extended validation certificate, payment, public key, security, trust services.","scope_keywords":["e-commerce","electronic signature","extended validation certificate","payment","public key","security","trust services","119","495","attribute","attributes","authentication","authorization","certificate","certificates","http"],"parent_legal_regulations":[{"celex":"32025R2527","eli":"https://data.europa.eu/eli/reg_impl/2025/2527/oj/eng","id":"2025-2527","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2527/2025-2527.md","title":"Qualified certificates for website authentication"}],"parent_specifications":[],"search_text":"ETSI TS 119 495 1.7.1 ETSI TS 119 495 Covers: e-commerce, electronic signature, extended validation certificate, payment, public key, security, trust services. e-commerce electronic signature extended validation certificate payment public key security trust services 119 495 attribute attributes authentication authorization certificate certificates http 119-series cited-by-eu-law implementing-regulation unchanged 2025-2527 Qualified certificates for website authentication 32025R2527"},{"id":"ETSI EN 319 412-5 V2.6.0","type":"specification","body":"ETSI","designation":"EN 319 412-5","version":"2.6.0","title":null,"purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/31941205/02.06.00_20/en_31941205v020600a.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/31941205/02.06.00_60/en_31941205v020600p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/31941205/02.06.00_20/en_31941205v020600a.pdf"],"folder":"ETSI/EN-319-412-5-V2.6.0","files":{"pdf":{"path":"standards/ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","sha256":"c1f77caa81f41ac5a27d99c15e3cccec8650f17d8674a6b59741f03bcefe9628"}},"tags":["319-series","trust-services","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","319","412-5","authorization","certificate","certificates","eidas","identification","key","pki","profile","profiles","qualified"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ETSI EN 319 412-5 2.6.0 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 319 412-5 authorization certificate certificates eidas identification key pki profile profiles qualified 319-series trust-services unchanged"},{"id":"ETSI EN 319 422 V1.1.1","type":"specification","body":"ETSI","designation":"EN 319 422","version":"1.1.1","title":"ETSI EN 319 422","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf","https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_20/en_319422v010101a.pdf"],"folder":"ETSI/EN-319-422-V1.1.1","files":{"pdf":{"path":"standards/ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","sha256":"b8dce6e415c906877ce36fd3d91b41e0543eda332f400cb444116ec760b5a4bf"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: electronic signature, security, time-stamping, trust services.","scope_keywords":["electronic signature","security","time-stamping","trust services","319","422","algorithm","algorithms","authorization","certificate","hash","http","https","key","profile","profiles"],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"}],"parent_specifications":[],"search_text":"ETSI EN 319 422 1.1.1 ETSI EN 319 422 Covers: electronic signature, security, time-stamping, trust services. electronic signature security time-stamping trust services 319 422 algorithm algorithms authorization certificate hash http https key profile profiles 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1929 Qualified electronic time stamps 32025R1929"},{"id":"ETSI EN 319 521 V1.1.1","type":"specification","body":"ETSI","designation":"EN 319 521","version":"1.1.1","title":"ETSI EN 319 521","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319500_319599/319521/01.01.01_60/en_319521v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319500_319599/319521/01.01.01_60/en_319521v010101p.pdf","https://www.etsi.org/deliver/etsi_en/319500_319599/319521/01.01.01_20/en_319521v010101a.pdf"],"folder":"ETSI/EN-319-521-V1.1.1","files":{"pdf":{"path":"standards/ETSI/EN-319-521-V1.1.1/EN-319-521-V1.1.1.pdf","sha256":"82b0f57a50ccb079290c55e84d08ac699a4445d5c8ea89b70dc57220a08a3bc8"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-delivery services, policy requirements, registered e-delivery services, security, trust services.","scope_keywords":["e-delivery services","policy requirements","registered e-delivery services","security","trust services","319","521","authentication","authorization","delivery","http","https","identification","key","policies","policy"],"parent_legal_regulations":[{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[],"search_text":"ETSI EN 319 521 1.1.1 ETSI EN 319 521 Covers: e-delivery services, policy requirements, registered e-delivery services, security, trust services. e-delivery services policy requirements registered e-delivery services security trust services 319 521 authentication authorization delivery http https identification key policies policy 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ETSI EN 319 522-1 V1.2.1","type":"specification","body":"ETSI","designation":"EN 319 522-1","version":"1.2.1","title":"ETSI EN 319 522-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319500_319599/31952201/01.02.01_60/en_31952201v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319500_319599/31952201/01.02.01_60/en_31952201v010201p.pdf","https://www.etsi.org/deliver/etsi_en/319500_319599/31952201/01.02.01_20/en_31952201v010201a.pdf"],"folder":"ETSI/EN-319-522-1-V1.2.1","files":{"pdf":{"path":"standards/ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf","sha256":"e6473180098fd860f8798ef4effe6e8718066cc4ff8b60474a836401c28cbcb3"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-delivery services, registered e-delivery services, registered electronic mail.","scope_keywords":["e-delivery services","registered e-delivery services","registered electronic mail","319","522-1","authorization","delivery","http","https","key","qualified","registered","signature","signatures","subject"],"parent_legal_regulations":[{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[],"search_text":"ETSI EN 319 522-1 1.2.1 ETSI EN 319 522-1 Covers: e-delivery services, registered e-delivery services, registered electronic mail. e-delivery services registered e-delivery services registered electronic mail 319 522-1 authorization delivery http https key qualified registered signature signatures subject 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ETSI EN 319 522-2 V1.2.1","type":"specification","body":"ETSI","designation":"EN 319 522-2","version":"1.2.1","title":"ETSI EN 319 522-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319500_319599/31952202/01.02.01_60/en_31952202v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319500_319599/31952202/01.02.01_60/en_31952202v010201p.pdf","https://www.etsi.org/deliver/etsi_en/319500_319599/31952202/01.02.01_20/en_31952202v010201a.pdf"],"folder":"ETSI/EN-319-522-2-V1.2.1","files":{"pdf":{"path":"standards/ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf","sha256":"2cbe75461facdb502df51eeda67957ba89bdac4ad04e75e20e64d6a76a4e7433"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-delivery services, registered e-delivery services, registered electronic mail.","scope_keywords":["e-delivery services","registered e-delivery services","registered electronic mail","319","522-2","attribute","attributes","authentication","authorization","delivery","http","https","identification","key","policy","qualified"],"parent_legal_regulations":[{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[],"search_text":"ETSI EN 319 522-2 1.2.1 ETSI EN 319 522-2 Covers: e-delivery services, registered e-delivery services, registered electronic mail. e-delivery services registered e-delivery services registered electronic mail 319 522-2 attribute attributes authentication authorization delivery http https identification key policy qualified 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ETSI EN 319 522-3 V1.2.1","type":"specification","body":"ETSI","designation":"EN 319 522-3","version":"1.2.1","title":"ETSI EN 319 522-3","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_en/319500_319599/31952203/01.02.01_60/en_31952203v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/319500_319599/31952203/01.02.01_60/en_31952203v010201p.pdf","https://www.etsi.org/deliver/etsi_en/319500_319599/31952203/01.02.01_20/en_31952203v010201a.pdf"],"folder":"ETSI/EN-319-522-3-V1.2.1","files":{"pdf":{"path":"standards/ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","sha256":"cffb726b5d9b6adf73cc8ca6df9028c25a0772894dbb5afdc12b561758ce9301"}},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unchanged"],"summary":"Covers: e-delivery services, registered e-delivery services, registered electronic mail.","scope_keywords":["e-delivery services","registered e-delivery services","registered electronic mail","319","522-3","authorization","delivery","http","https","key","qualified","registered","signature","signatures","subject"],"parent_legal_regulations":[{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[],"search_text":"ETSI EN 319 522-3 1.2.1 ETSI EN 319 522-3 Covers: e-delivery services, registered e-delivery services, registered electronic mail. e-delivery services registered e-delivery services registered electronic mail 319 522-3 authorization delivery http https key qualified registered signature signatures subject 319-series cited-by-eu-law implementing-regulation trust-services unchanged 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ETSI EN 3191 22-1 V1.3.1","type":"specification","body":"ETSI","designation":"EN 3191 22-1","version":"1.3.1","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_en/3191000_3191099/319102201/01.03.01_60/en_319102201v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/3191000_3191099/319102201/01.03.01_60/en_319102201v010301p.pdf","https://www.etsi.org/deliver/etsi_en/3191000_3191099/319102201/01.03.01_20/en_319102201v010301a.pdf"],"folder":"ETSI/EN-3191-22-1-V1.3.1","files":{},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"}],"parent_specifications":[],"search_text":"ETSI EN 3191 22-1 1.3.1 319-series cited-by-eu-law implementing-regulation trust-services unavailable 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979"},{"id":"ETSI EN 319403-1 V2.3.1","type":"specification","body":"ETSI","designation":"EN 319403-1","version":"2.3.1","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_en/3194000_3194099/319403001/02.03.01_60/en_319403001v020301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_en/3194000_3194099/319403001/02.03.01_60/en_319403001v020301p.pdf","https://www.etsi.org/deliver/etsi_en/3194000_3194099/319403001/02.03.01_20/en_319403001v020301a.pdf"],"folder":"ETSI/EN-319403-1-V2.3.1","files":{},"tags":["319-series","cited-by-eu-law","implementing-regulation","trust-services","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ETSI EN 319403-1 2.3.1 319-series cited-by-eu-law implementing-regulation trust-services unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ETSI TR 102 272 V1.1.1","type":"specification","body":"ETSI","designation":"TR 102 272","version":"1.1.1","title":"ETSI TR 102 272","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_tr/102200_102299/102272/01.01.01_60/tr_102272v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_tr/102200_102299/102272/01.01.01_60/tr_102272v010101p.pdf","https://www.etsi.org/deliver/etsi_tr/102200_102299/102272/01.01.01_20/tr_102272v010101a.pdf"],"folder":"ETSI/TR-102-272-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","sha256":"d01ee36f69555286b06e6d27d88de7e66d4a371508ae8d7ff0becd7c15a10981"}},"tags":["nested-reference","unchanged"],"summary":"Covers: ASN.1, electronic signature, security, e-commerce.","scope_keywords":["asn.1","electronic signature","security","e-commerce","102","272","algorithm","attribute","certificate","http","identification","key","path","policies","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ETSI TR 102 272 1.1.1 ETSI TR 102 272 Covers: ASN.1, electronic signature, security, e-commerce. asn.1 electronic signature security e-commerce 102 272 algorithm attribute certificate http identification key path policies policy registered nested-reference unchanged"},{"id":"IETF RFC 5126","type":"specification","body":"IETF","designation":"RFC 5126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5126.txt","https://www.rfc-editor.org/rfc/rfc5126.pdf"],"folder":"IETF/RFC-5126","files":{"txt":{"path":"standards/IETF/RFC-5126/RFC-5126.txt","sha256":"07d822ec1f060dd485f3d998355fe8e736c15d8a09491e933e75c9bea6751d18"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format of an electronic signature that can\n remain valid over long periods. This includes evidence as to its\n validity even if the signer or verifying party later attempts to deny\n (i.e., repudiates) the validity of the signature.\n\n The format can be considered as an extension to RFC 3852 and RFC\n 2634, where, when appropriate, additional signed and unsigned\n attributes have been defined.\n\n The contents of this Informational RFC amount to a transposition of\n the ETSI Technical Specification (TS) 101 733 V.1.7.4 (CMS Advanced\n Electronic Signatures -- CAdES) and is technically equivalent to it.\n\n The technical contents of this specification are maintained by ETSI.\n The ETSI TS and further updates are available free of charge at:\n http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx\n\nPinkas, et al. Informational [Page 1]\n\f\nRFC 5126 CMS Advanced Electronic ","scope_keywords":["5126","attribute","attributes","certificate","http","policies","policy","revocation","signature","signatures","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null}],"search_text":"IETF RFC 5126 This document defines the format of an electronic signature that can\n remain valid over long periods. This includes evidence as to its\n validity even if the signer or verifying party later attempts to deny\n (i.e., repudiates) the validity of the signature.\n\n The format can be considered as an extension to RFC 3852 and RFC\n 2634, where, when appropriate, additional signed and unsigned\n attributes have been defined.\n\n The contents of this Informational RFC amount to a transposition of\n the ETSI Technical Specification (TS) 101 733 V.1.7.4 (CMS Advanced\n Electronic Signatures -- CAdES) and is technically equivalent to it.\n\n The technical contents of this specification are maintained by ETSI.\n The ETSI TS and further updates are available free of charge at:\n http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx\n\nPinkas, et al. Informational [Page 1]\n\f\nRFC 5126 CMS Advanced Electronic  5126 attribute attributes certificate http policies policy revocation signature signatures validation nested-reference unchanged"},{"id":"ETSI TR 119 411-5 V2.1.1","type":"specification","body":"ETSI","designation":"TR 119 411-5","version":"2.1.1","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_tr/119400_119499/11941105/02.01.01_60/tr_11941105v020101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_tr/119400_119499/11941105/02.01.01_60/tr_11941105v020101p.pdf","https://www.etsi.org/deliver/etsi_tr/119400_119499/11941105/02.01.01_20/tr_11941105v020101a.pdf"],"folder":"ETSI/TR-119-411-5-V2.1.1","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ETSI TR 119 411-5 2.1.1 119-series nested-reference unavailable"},{"id":"ETSI TS 119 411-5 V2.1.1","type":"specification","body":"ETSI","designation":"TS 119 411-5","version":"2.1.1","title":"ETSI TS 119 411-5","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11941105/02.01.01_60/ts_11941105v020101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11941105/02.01.01_60/ts_11941105v020101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11941105/02.01.01_20/ts_11941105v020101a.pdf"],"folder":"ETSI/TS-119-411-5-V2.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","sha256":"8394c2de60f811faa7d98d4b84603d9de74445a43355efa0041158dbb8a8f344"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: cyber security, electronic signature, extended validation certificate, internet, public key, security, trust services.","scope_keywords":["cyber security","electronic signature","extended validation certificate","internet","public key","security","trust services","119","411-5","authentication","authorization","certificate","certificates","key","policy","presentation"],"parent_legal_regulations":[{"celex":"32025R2527","eli":"https://data.europa.eu/eli/reg_impl/2025/2527/oj/eng","id":"2025-2527","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2527/2025-2527.md","title":"Qualified certificates for website authentication"}],"parent_specifications":[],"search_text":"ETSI TS 119 411-5 2.1.1 ETSI TS 119 411-5 Covers: cyber security, electronic signature, extended validation certificate, internet, public key, security, trust services. cyber security electronic signature extended validation certificate internet public key security trust services 119 411-5 authentication authorization certificate certificates key policy presentation 119-series cited-by-eu-law implementing-regulation unchanged 2025-2527 Qualified certificates for website authentication 32025R2527"},{"id":"ETSI TR 119 476 V1.2.1","type":"specification","body":"ETSI","designation":"TR 119 476","version":"1.2.1","title":"ETSI TR 119 476","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_tr/119400_119499/119476/01.02.01_60/tr_119476v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_tr/119400_119499/119476/01.02.01_60/tr_119476v010201p.pdf","https://www.etsi.org/deliver/etsi_tr/119400_119499/119476/01.02.01_20/tr_119476v010201a.pdf"],"folder":"ETSI/TR-119-476-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","sha256":"83febff960cc925f879abfd51cf482ed78d2962682e064449e4978fb78e8e9ba"}},"tags":["119-series","nested-reference","unchanged"],"summary":"Covers: identity, trust services.","scope_keywords":["identity","trust services","119","476","attestation","attribute","attributes","authorization","http","https","key","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS04","folder":"ARF/TS04-V1.0.1","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md","version":"1.0.1"}],"search_text":"ETSI TR 119 476 1.2.1 ETSI TR 119 476 Covers: identity, trust services. identity trust services 119 476 attestation attribute attributes authorization http https key presentation signature signatures subject trust 119-series nested-reference unchanged"},{"id":"ETSI TS 101 270-1 V1.2.1","type":"specification","body":"ETSI","designation":"TS 101 270-1","version":"1.2.1","title":"ETSI TS 101 270-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/101200_101299/10127001/01.02.01_60/ts_10127001v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/101200_101299/10127001/01.02.01_60/ts_10127001v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/101200_101299/10127001/01.02.01_20/ts_10127001v010201a.pdf"],"folder":"ETSI/TS-101-270-1-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","sha256":"f510229dad013faf673a78eb2f660ad19337c9b81c064c001d0bf400c862028c"}},"tags":["nested-reference","unchanged"],"summary":"Covers: access, ATM, B-ISDN, transmission, VDSL.","scope_keywords":["access","atm","b-isdn","transmission","vdsl","101","270-1","http","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null}],"search_text":"ETSI TS 101 270-1 1.2.1 ETSI TS 101 270-1 Covers: access, ATM, B-ISDN, transmission, VDSL. access atm b-isdn transmission vdsl 101 270-1 http key path nested-reference unchanged"},{"id":"IETF RFC 3728","type":"specification","body":"IETF","designation":"RFC 3728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3728.txt","https://www.rfc-editor.org/rfc/rfc3728.pdf"],"folder":"IETF/RFC-3728","files":{"txt":{"path":"standards/IETF/RFC-3728/RFC-3728.txt","sha256":"5db22dd39cc53aeedc1ceda5a460b6fda8b657d43922091ec31e19cb16b2b688"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing Very High Speed\n Digital Subscriber Line (VDSL) interfaces.","scope_keywords":["3728","attribute","attributes","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"IETF RFC 3728 This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing Very High Speed\n Digital Subscriber Line (VDSL) interfaces. 3728 attribute attributes key management profile profiles nested-reference unchanged"},{"id":"ETSI TS 101 270-2 V1.1.1","type":"specification","body":"ETSI","designation":"TS 101 270-2","version":"1.1.1","title":"ETSI TS 101 270-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/101200_101299/10127002/01.01.01_60/ts_10127002v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/101200_101299/10127002/01.01.01_60/ts_10127002v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/101200_101299/10127002/01.01.01_20/ts_10127002v010101a.pdf"],"folder":"ETSI/TS-101-270-2-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","sha256":"c937115846f94828cf550892d47c3829965c12dbe7a656d3a53f86c5582c18c4"}},"tags":["nested-reference","unchanged"],"summary":"Covers: access, ATM, B-ISDN, transmission, VDSL.","scope_keywords":["access","atm","b-isdn","transmission","vdsl","101","270-2","http","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null}],"search_text":"ETSI TS 101 270-2 1.1.1 ETSI TS 101 270-2 Covers: access, ATM, B-ISDN, transmission, VDSL. access atm b-isdn transmission vdsl 101 270-2 http key subject nested-reference unchanged"},{"id":"ETSI TS 101 329-5 V1.1.2","type":"specification","body":"ETSI","designation":"TS 101 329-5","version":"1.1.2","title":"ETSI TS 101 329-5","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/101300_101399/10132905/01.01.02_60/ts_10132905v010102p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/101300_101399/10132905/01.01.02_60/ts_10132905v010102p.pdf","https://www.etsi.org/deliver/etsi_ts/101300_101399/10132905/01.01.02_20/ts_10132905v010102a.pdf"],"folder":"ETSI/TS-101-329-5-V1.1.2","files":{"pdf":{"path":"standards/ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","sha256":"dfd9618b09ffb5f0ead6f5899335c2ff37d08e9857b8f626724022da1c4ec2d8"}},"tags":["nested-reference","unchanged"],"summary":"Covers: internet, methodology, quality, service, system, telephony.","scope_keywords":["internet","methodology","quality","service","system","telephony","101","329-5","http","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ETSI TS 101 329-5 1.1.2 ETSI TS 101 329-5 Covers: internet, methodology, quality, service, system, telephony. internet methodology quality service system telephony 101 329-5 http key path subject nested-reference unchanged"},{"id":"IETF RFC 3432","type":"specification","body":"IETF","designation":"RFC 3432","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3432.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3432.txt","https://www.rfc-editor.org/rfc/rfc3432.pdf"],"folder":"IETF/RFC-3432","files":{"txt":{"path":"standards/IETF/RFC-3432/RFC-3432.txt","sha256":"cdcb1476910ac4b6139610121739ebbe90e177592c2fb0a0b6ea35aa03c723d3"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a periodic sampling method and relevant metrics\n for assessing the performance of IP networks. First, the memo\n motivates periodic sampling and addresses the question of its value\n as an alternative to the Poisson sampling described in RFC 2330. The\n benefits include applicability to active and passive measurements,\n simulation of constant bit rate (CBR) traffic (typical of multimedia\n communication, or nearly CBR, as found with voice activity\n detection), and several instances in which analysis can be\n simplified. The sampling method avoids predictability by mandating\n random start times and finite length tests. Following descriptions\n of the sampling method and sample metric parameters, measurement\n methods and errors are discussed. Finally, we give additional\n information on periodic measurements, including security\n considerations.\n\nRaisanen, et al. Standards Trac","scope_keywords":["3432","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 3432 This memo describes a periodic sampling method and relevant metrics\n for assessing the performance of IP networks. First, the memo\n motivates periodic sampling and addresses the question of its value\n as an alternative to the Poisson sampling described in RFC 2330. The\n benefits include applicability to active and passive measurements,\n simulation of constant bit rate (CBR) traffic (typical of multimedia\n communication, or nearly CBR, as found with voice activity\n detection), and several instances in which analysis can be\n simplified. The sampling method avoids predictability by mandating\n random start times and finite length tests. Following descriptions\n of the sampling method and sample metric parameters, measurement\n methods and errors are discussed. Finally, we give additional\n information on periodic measurements, including security\n considerations.\n\nRaisanen, et al. Standards Trac 3432 key nested-reference unchanged"},{"id":"IETF RFC 3611","type":"specification","body":"IETF","designation":"RFC 3611","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3611.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3611.txt","https://www.rfc-editor.org/rfc/rfc3611.pdf"],"folder":"IETF/RFC-3611","files":{"txt":{"path":"standards/IETF/RFC-3611/RFC-3611.txt","sha256":"a365d4b99a1993b43bd0cefa68ef1b57a27ec716c752e3361cef21415de89f2d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Extended Report (XR) packet type for the\n RTP Control Protocol (RTCP), and defines how the use of XR packets\n can be signaled by an application if it employs the Session\n Description Protocol (SDP). XR packets are composed of report\n blocks, and seven block types are defined here. The purpose of the\n extended reporting format is to convey information that supplements\n the six statistics that are contained in the report blocks used by\n RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some\n applications, such as multicast inference of network characteristics\n (MINC) or voice over IP (VoIP) monitoring, require other and more\n detailed statistics. In addition to the block types defined here,\n additional block types may be defined in the future by adhering to\n the framework that this document provides.\n\nFriedman, et al. Standards Track [Page 1]\n\f\nRFC 3611 ","scope_keywords":["3611","algorithm","algorithms","attribute","management","profile","profiles","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 3611 This document defines the Extended Report (XR) packet type for the\n RTP Control Protocol (RTCP), and defines how the use of XR packets\n can be signaled by an application if it employs the Session\n Description Protocol (SDP). XR packets are composed of report\n blocks, and seven block types are defined here. The purpose of the\n extended reporting format is to convey information that supplements\n the six statistics that are contained in the report blocks used by\n RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some\n applications, such as multicast inference of network characteristics\n (MINC) or voice over IP (VoIP) monitoring, require other and more\n detailed statistics. In addition to the block types defined here,\n additional block types may be defined in the future by adhering to\n the framework that this document provides.\n\nFriedman, et al. Standards Track [Page 1]\n\f\nRFC 3611  3611 algorithm algorithms attribute management profile profiles timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 7266","type":"specification","body":"IETF","designation":"RFC 7266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7266.txt","https://www.rfc-editor.org/rfc/rfc7266.pdf"],"folder":"IETF/RFC-7266","files":{"txt":{"path":"standards/IETF/RFC-7266/RFC-7266.txt","sha256":"7ad2372c21f31288123bc2def9ed0fc3f8cbed4f07c2c61872fb6b2f3706aecb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) Block including two new segment types and associated Session\n Description Protocol (SDP) parameters that allow the reporting of\n mean opinion score (MOS) Metrics for use in a range of RTP\n applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7266.\n\nClark, et al. Standards Track [Page 1]\n\f\nRFC 7266 RTCP XR","scope_keywords":["7266","algorithm","algorithms","attribute","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7266 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) Block including two new segment types and associated Session\n Description Protocol (SDP) parameters that allow the reporting of\n mean opinion score (MOS) Metrics for use in a range of RTP\n applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7266.\n\nClark, et al. Standards Track [Page 1]\n\f\nRFC 7266 RTCP XR 7266 algorithm algorithms attribute delivery http key license subject trust nested-reference unchanged"},{"id":"ETSI TS 101 861 V1.4.1","type":"specification","body":"ETSI","designation":"TS 101 861","version":"1.4.1","title":"ETSI TS 101 861","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/101800_101899/101861/01.04.01_60/ts_101861v010401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/101800_101899/101861/01.04.01_60/ts_101861v010401p.pdf","https://www.etsi.org/deliver/etsi_ts/101800_101899/101861/01.04.01_20/ts_101861v010401a.pdf"],"folder":"ETSI/TS-101-861-V1.4.1","files":{"pdf":{"path":"standards/ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","sha256":"f7207c7bcb3772a45914848d3d87340129e57508a564d483769c143db83731b4"}},"tags":["nested-reference","unchanged"],"summary":"Covers: electronic signature, security.","scope_keywords":["electronic signature","security","101","861","algorithm","algorithms","certificate","certificates","hash","http","key","policy","profile","profiles","registered","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ETSI TS 101 861 1.4.1 ETSI TS 101 861 Covers: electronic signature, security. electronic signature security 101 861 algorithm algorithms certificate certificates hash http key policy profile profiles registered signature nested-reference unchanged"},{"id":"ETSI TS 101 903 V1.3.2","type":"specification","body":"ETSI","designation":"TS 101 903","version":"1.3.2","title":"ETSI TS 101 903","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.03.02_60/ts_101903v010302p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.03.02_60/ts_101903v010302p.pdf","https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.03.02_20/ts_101903v010302a.pdf"],"folder":"ETSI/TS-101-903-V1.3.2","files":{"pdf":{"path":"standards/ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","sha256":"503519aadce0978098a3642abb7f149f9b54d595d06d1b10274181ab45df9bb5"}},"tags":["nested-reference","unchanged"],"summary":"Covers: e-commerce, electronic signature, security.","scope_keywords":["e-commerce","electronic signature","security","101","903","http","key","management","pki","policies","policy","registered","signature","signatures","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null}],"search_text":"ETSI TS 101 903 1.3.2 ETSI TS 101 903 Covers: e-commerce, electronic signature, security. e-commerce electronic signature security 101 903 http key management pki policies policy registered signature signatures subject validation nested-reference unchanged"},{"id":"IETF RFC 5698","type":"specification","body":"IETF","designation":"RFC 5698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5698.txt","https://www.rfc-editor.org/rfc/rfc5698.pdf"],"folder":"IETF/RFC-5698","files":{"txt":{"path":"standards/IETF/RFC-5698/RFC-5698.txt","sha256":"af5806751aa37bfc76e5fd9bedf26728e438ce25a6314453e098b558bfa0e313"}},"tags":["nested-reference","unchanged"],"summary":"Since cryptographic algorithms can become weak over the years, it is\n necessary to evaluate their security suitability. When signing or\n verifying data, or when encrypting or decrypting data, these\n evaluations must be considered. This document specifies a data\n structure that enables an automated analysis of the security\n suitability of a given cryptographic algorithm at a given point of\n time, which may be in the past, the present, or the future.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n","scope_keywords":["5698","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","http","key","keys","license","policies","policy","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null}],"search_text":"IETF RFC 5698 Since cryptographic algorithms can become weak over the years, it is\n necessary to evaluate their security suitability. When signing or\n verifying data, or when encrypting or decrypting data, these\n evaluations must be considered. This document specifies a data\n structure that enables an automated analysis of the security\n suitability of a given cryptographic algorithm at a given point of\n time, which may be in the past, the present, or the future.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n 5698 algorithm algorithms authentication certificate certificates encryption hash http key keys license policies policy signature signatures nested-reference unchanged"},{"id":"ETSI TS 102 034 V1.4.1","type":"specification","body":"ETSI","designation":"TS 102 034","version":"1.4.1","title":"ETSI TS 102 034","purpose":null,"status":"downloaded","download_url":"https://www.etsi.org/deliver/etsi_ts/102000_102099/102034/01.04.01_60/ts_102034v010401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/102000_102099/102034/01.04.01_60/ts_102034v010401p.pdf","https://www.etsi.org/deliver/etsi_ts/102000_102099/102034/01.04.01_20/ts_102034v010401a.pdf"],"folder":"ETSI/TS-102-034-V1.4.1","files":{"pdf":{"path":"standards/ETSI/TS-102-034-V1.4.1/TS-102-034-V1.4.1.pdf","sha256":"62a25f0e74ea5c4f95260a3fa2228d4aeb3afe3b5cc8ce1406849dace0a2e095"}},"tags":["downloaded","nested-reference"],"summary":"Covers: broadcasting, digital, DVB, satellite, video.","scope_keywords":["broadcasting","digital","dvb","satellite","video","102","034","http","identification","key","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null}],"search_text":"ETSI TS 102 034 1.4.1 ETSI TS 102 034 Covers: broadcasting, digital, DVB, satellite, video. broadcasting digital dvb satellite video 102 034 http identification key registered subject downloaded nested-reference"},{"id":"IETF RFC 6015","type":"specification","body":"IETF","designation":"RFC 6015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6015.txt","https://www.rfc-editor.org/rfc/rfc6015.pdf"],"folder":"IETF/RFC-6015","files":{"txt":{"path":"standards/IETF/RFC-6015/RFC-6015.txt","sha256":"a5ccf7db8e1c4f32dcbca9da28e5842fd35742474c2f85c3b5713caa6658c83b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new RTP payload format for the Forward Error\n Correction (FEC) that is generated by the 1-D interleaved parity code\n from a source media encapsulated in RTP. The 1-D interleaved parity\n code is a systematic code, where a number of repair symbols are\n generated from a set of source symbols and sent in a repair flow\n separate from the source flow that carries the source symbols. The\n 1-D interleaved parity code offers a good protection against bursty\n packet losses at a cost of reasonable complexity. The new payload\n format defined in this document should only be used (with some\n exceptions) as a part of the Digital Video Broadcasting-IPTV (DVB-\n IPTV) Application-layer FEC specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the","scope_keywords":["6015","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null}],"search_text":"IETF RFC 6015 This document defines a new RTP payload format for the Forward Error\n Correction (FEC) that is generated by the 1-D interleaved parity code\n from a source media encapsulated in RTP. The 1-D interleaved parity\n code is a systematic code, where a number of repair symbols are\n generated from a set of source symbols and sent in a repair flow\n separate from the source flow that carries the source symbols. The\n 1-D interleaved parity code offers a good protection against bursty\n packet losses at a cost of reasonable complexity. The new payload\n format defined in this document should only be used (with some\n exceptions) as a part of the Digital Video Broadcasting-IPTV (DVB-\n IPTV) Application-layer FEC specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the 6015 http license registered subject trust nested-reference unchanged"},{"id":"ETSI TS 102 176-1 V2.0.0","type":"specification","body":"ETSI","designation":"TS 102 176-1","version":"2.0.0","title":"ETSI TS 102 176-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/102100_102199/10217601/02.00.00_60/ts_10217601v020000p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/102100_102199/10217601/02.00.00_60/ts_10217601v020000p.pdf","https://www.etsi.org/deliver/etsi_ts/102100_102199/10217601/02.00.00_20/ts_10217601v020000a.pdf"],"folder":"ETSI/TS-102-176-1-V2.0.0","files":{"pdf":{"path":"standards/ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","sha256":"8189c883274a096a81258b216128ef9960aab6520f3d66dcc6ba8220f19951dd"}},"tags":["nested-reference","unchanged"],"summary":"Covers: e-commerce, electronic signature, security.","scope_keywords":["e-commerce","electronic signature","security","102","176-1","algorithm","algorithms","hash","http","key","registered","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null}],"search_text":"ETSI TS 102 176-1 2.0.0 ETSI TS 102 176-1 Covers: e-commerce, electronic signature, security. e-commerce electronic signature security 102 176-1 algorithm algorithms hash http key registered signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 4998","type":"specification","body":"IETF","designation":"RFC 4998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4998.txt","https://www.rfc-editor.org/rfc/rfc4998.pdf"],"folder":"IETF/RFC-4998","files":{"txt":{"path":"standards/IETF/RFC-4998/RFC-4998.txt","sha256":"c194b696364f6b5ed1e2fac6da676fc8d29219b84e48a2e2d30d20fde5b14b43"}},"tags":["nested-reference","unchanged"],"summary":"In many scenarios, users must be able prove the existence and\n integrity of data, including digitally signed data, in a common and\n reproducible way over a long and possibly undetermined period of\n time. This document specifies the syntax and processing of an\n Evidence Record, a structure designed to support long-term non-\n repudiation of existence of data.\n\nGondrom, et al. Standards Track [Page 1]\n\f\nRFC 4998 ERS August 2007","scope_keywords":["4998","algorithm","algorithms","attribute","authentication","certificate","certificates","encryption","hash","identification","key","preservation","signature","signatures","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"EN 319 162-2","folder":"ETSI/EN-319-162-2-V1.1.1","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null}],"search_text":"IETF RFC 4998 In many scenarios, users must be able prove the existence and\n integrity of data, including digitally signed data, in a common and\n reproducible way over a long and possibly undetermined period of\n time. This document specifies the syntax and processing of an\n Evidence Record, a structure designed to support long-term non-\n repudiation of existence of data.\n\nGondrom, et al. Standards Track [Page 1]\n\f\nRFC 4998 ERS August 2007 4998 algorithm algorithms attribute authentication certificate certificates encryption hash identification key preservation signature signatures subject timestamp nested-reference unchanged"},{"id":"IETF RFC 6283","type":"specification","body":"IETF","designation":"RFC 6283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6283.txt","https://www.rfc-editor.org/rfc/rfc6283.pdf"],"folder":"IETF/RFC-6283","files":{"txt":{"path":"standards/IETF/RFC-6283/RFC-6283.txt","sha256":"898cdca15baac3471239ae3b26c875b4ef02a3e1aa86c9c61e3c41ad68b1ff24"}},"tags":["nested-reference","unchanged"],"summary":"In many scenarios, users must be able to demonstrate the (time of)\n existence, integrity, and validity of data including signed data for\n long or undetermined periods of time. This document specifies XML\n syntax and processing rules for creating evidence for long-term non-\n repudiation of existence and integrity of data. The Extensible\n Markup Language Evidence Record Syntax XMLERS provides alternative\n syntax and processing rules to the ASN.1 (Abstract Syntax Notation\n One) ERS (Evidence Record Syntax) (RFC 4998) syntax by using XML.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard","scope_keywords":["6283","algorithm","algorithms","certificate","encryption","hash","http","key","keys","license","policies","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"EN 319 162-2","folder":"ETSI/EN-319-162-2-V1.1.1","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"IETF RFC 6283 In many scenarios, users must be able to demonstrate the (time of)\n existence, integrity, and validity of data including signed data for\n long or undetermined periods of time. This document specifies XML\n syntax and processing rules for creating evidence for long-term non-\n repudiation of existence and integrity of data. The Extensible\n Markup Language Evidence Record Syntax XMLERS provides alternative\n syntax and processing rules to the ASN.1 (Abstract Syntax Notation\n One) ERS (Evidence Record Syntax) (RFC 4998) syntax by using XML.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard 6283 algorithm algorithms certificate encryption hash http key keys license policies signature signatures subject trust nested-reference unchanged"},{"id":"ETSI TS 119 101 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 101","version":"1.1.1","title":"ETSI TS 119 101","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/119101/01.01.01_60/ts_119101v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/119101/01.01.01_60/ts_119101v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/119101/01.01.01_20/ts_119101v010101a.pdf"],"folder":"ETSI/TS-119-101-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","sha256":"e94f01df44e9eeaf320c1f9d94df8491c1f5f55c241464242d14df0d1bc02f77"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","119","101","attribute","authorization","certificate","certificates","http","https","key","management","policy","preservation"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","id":"2025-1945","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1945/2025-1945.md","title":"Qualified certificates for signatures and seals"},{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"}],"parent_specifications":[],"search_text":"ETSI TS 119 101 1.1.1 ETSI TS 119 101 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 119 101 attribute authorization certificate certificates http https key management policy preservation 119-series cited-by-eu-law implementing-regulation unchanged 2025-1942 Recognition of qualified validation services 32025R1942 2025-1945 Qualified certificates for signatures and seals 32025R1945 2025-1946 Qualified preservation services for signatures and seals 32025R1946"},{"id":"ETSI TS 119 102-1 V1.3.1","type":"specification","body":"ETSI","designation":"TS 119 102-1","version":"1.3.1","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11910201/01.03.01_60/ts_11910201v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11910201/01.03.01_60/ts_11910201v010301p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11910201/01.03.01_20/ts_11910201v010301a.pdf"],"folder":"ETSI/TS-119-102-1-V1.3.1","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 441","folder":"ETSI/TS-119-441-V1.2.1","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ETSI TS 119 102-1 1.3.1 119-series nested-reference unavailable"},{"id":"ETSI TS 119 102-2 V1.4.1","type":"specification","body":"ETSI","designation":"TS 119 102-2","version":"1.4.1","title":"ETSI TS 119 102-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11910202/01.04.01_60/ts_11910202v010401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11910202/01.04.01_60/ts_11910202v010401p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11910202/01.04.01_20/ts_11910202v010401a.pdf"],"folder":"ETSI/TS-119-102-2-V1.4.1","files":{"pdf":{"path":"standards/ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","sha256":"b3481e9078e60901dd480ec2605e1daa2b84e47aebd73bf6b681e25ef27dfb83"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: electronic signature, trust services, validation.","scope_keywords":["electronic signature","trust services","validation","119","102-2","authorization","certificate","certificates","http","https","key","presentation","qualified","seal","signature","signatures"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","id":"2025-1945","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1945/2025-1945.md","title":"Qualified certificates for signatures and seals"}],"parent_specifications":[],"search_text":"ETSI TS 119 102-2 1.4.1 ETSI TS 119 102-2 Covers: electronic signature, trust services, validation. electronic signature trust services validation 119 102-2 authorization certificate certificates http https key presentation qualified seal signature signatures 119-series cited-by-eu-law implementing-regulation unchanged 2025-1942 Recognition of qualified validation services 32025R1942 2025-1945 Qualified certificates for signatures and seals 32025R1945"},{"id":"ETSI TS 119 142-1 V1.1.0","type":"specification","body":"ETSI","designation":"TS 119 142-1","version":"1.1.0","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11914201/01.01.00_60/ts_11914201v010100p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11914201/01.01.00_60/ts_11914201v010100p.pdf"],"folder":"ETSI/TS-119-142-1-V1.1.0","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.1.1","source":"ETSI/EN-319-142-1-V1.1.1/EN-319-142-1-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ETSI TS 119 142-1 1.1.0 119-series nested-reference unavailable"},{"id":"ETSI TS 119 162-1 V1.1.0","type":"specification","body":"ETSI","designation":"TS 119 162-1","version":"1.1.0","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11916201/01.01.00_60/ts_11916201v010100p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11916201/01.01.00_60/ts_11916201v010100p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11916201/01.01.00_20/ts_11916201v010100a.pdf"],"folder":"ETSI/TS-119-162-1-V1.1.0","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ETSI TS 119 162-1 1.1.0 119-series nested-reference unavailable"},{"id":"ETSI TS 119 162-2 V1.1.0","type":"specification","body":"ETSI","designation":"TS 119 162-2","version":"1.1.0","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11916202/01.01.00_60/ts_11916202v010100p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11916202/01.01.00_60/ts_11916202v010100p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11916202/01.01.00_20/ts_11916202v010100a.pdf"],"folder":"ETSI/TS-119-162-2-V1.1.0","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-2","folder":"ETSI/EN-319-162-2-V1.1.1","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ETSI TS 119 162-2 1.1.0 119-series nested-reference unavailable"},{"id":"ETSI TS 119 172-4 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 172-4","version":"1.1.1","title":"ETSI TS 119 172-4","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.01.01_60/ts_11917204v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.01.01_60/ts_11917204v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.01.01_20/ts_11917204v010101a.pdf"],"folder":"ETSI/TS-119-172-4-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-172-4-V1.1.1/TS-119-172-4-V1.1.1.pdf","sha256":"ec59dd8f8b5664f0cef8776f88ddc335c138ba3136ae30084d77b506b32ba040"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: e-commerce, electronic signature, trust services.","scope_keywords":["e-commerce","electronic signature","trust services","119","172-4","authorization","certificate","certificates","http","https","key","policies","policy","presentation","preservation","qualified"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","id":"2025-1945","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1945/2025-1945.md","title":"Qualified certificates for signatures and seals"},{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"}],"parent_specifications":[],"search_text":"ETSI TS 119 172-4 1.1.1 ETSI TS 119 172-4 Covers: e-commerce, electronic signature, trust services. e-commerce electronic signature trust services 119 172-4 authorization certificate certificates http https key policies policy presentation preservation qualified 119-series cited-by-eu-law implementing-regulation unchanged 2025-1942 Recognition of qualified validation services 32025R1942 2025-1945 Qualified certificates for signatures and seals 32025R1945 2025-1946 Qualified preservation services for signatures and seals 32025R1946"},{"id":"ETSI TS 119 182-1 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 182-1","version":"1.2.1","title":"ETSI TS 119 182-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_20/ts_11918201v010201a.pdf"],"folder":"ETSI/TS-119-182-1-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","sha256":"6af9bc5621c878b1ee7dfb64e2ba617368b351ddb91ece755879597c42368f9f"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: electronic signature, JSON.","scope_keywords":["electronic signature","json","119","182-1","authorization","certificate","eudi","http","https","key","ledger","presentation","qualified","signature","signatures","subject"],"parent_legal_regulations":[{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"},{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"}],"parent_specifications":[],"search_text":"ETSI TS 119 182-1 1.2.1 ETSI TS 119 182-1 Covers: electronic signature, JSON. electronic signature json 119 182-1 authorization certificate eudi http https key ledger presentation qualified signature signatures subject 119-series cited-by-eu-law implementing-regulation unchanged 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979 2025-2531 Qualified electronic ledgers 32025R2531"},{"id":"ETSI TS 119 411-8 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 411-8","version":"1.1.1","title":"ETSI TS 119 411-8","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11941108/01.01.01_60/ts_11941108v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11941108/01.01.01_60/ts_11941108v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11941108/01.01.01_20/ts_11941108v010101a.pdf"],"folder":"ETSI/TS-119-411-8-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf","sha256":"2bbfffeca655b96b09e52d937a930744215c2c9e3ee7f41f14d990968c845fe3"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: e-commerce, electronic signature, EUDI wallet, security, trust services.","scope_keywords":["e-commerce","electronic signature","eudi wallet","security","trust services","119","411-8","authorization","certificate","certificates","eudi","identification","key","pki","policies","policy"],"parent_legal_regulations":[{"celex":"32026R1730","eli":"https://data.europa.eu/eli/reg_impl/2026/1730/oj/eng","id":"2026-1730","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1730/2026-1730.md","title":"Amending CIR 2025/848 — Relying Party Registration"}],"parent_specifications":[],"search_text":"ETSI TS 119 411-8 1.1.1 ETSI TS 119 411-8 Covers: e-commerce, electronic signature, EUDI wallet, security, trust services. e-commerce electronic signature eudi wallet security trust services 119 411-8 authorization certificate certificates eudi identification key pki policies policy 119-series cited-by-eu-law implementing-regulation unchanged 2026-1730 Amending CIR 2025/848 — Relying Party Registration 32026R1730"},{"id":"legal:2026-1730","type":"legal_regulation","act_id":"2026-1730","title":"Amending CIR 2025/848 — Relying Party Registration","celex":"32026R1730","eli":"https://data.europa.eu/eli/reg_impl/2026/1730/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"sha256":"2d939d209aeb176ac76a05062e05fad7f630251c95afa8f0874f815c8421269f","size":42532,"item_url":"http://publications.europa.eu/resource/cellar/933ea5f2-856a-11f1-bf5e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2026-1730/2026-1730.html"},"pdf":{"sha256":"841c17589b842a2249a2eb35091e6c0d4c6b1218a3e6c56f0346cef3f8bb8fd4","size":495492,"item_url":"http://publications.europa.eu/resource/cellar/933ea5f2-856a-11f1-bf5e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2026-1730/2026-1730.pdf"}},"search_text":"2026-1730 Amending CIR 2025/848 — Relying Party Registration 32026R1730 implementing_regulation implementing-acts"},{"id":"ETSI TS 119 412-1 V1.4.4","type":"specification","body":"ETSI","designation":"TS 119 412-1","version":"1.4.4","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11941201/01.04.04_60/ts_11941201v010404p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11941201/01.04.04_60/ts_11941201v010404p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11941201/01.04.04_20/ts_11941201v010404a.pdf"],"folder":"ETSI/TS-119-412-1-V1.4.4","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"}],"search_text":"ETSI TS 119 412-1 1.4.4 119-series nested-reference unavailable"},{"id":"ETSI TS 119 412-6 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 412-6","version":"1.2.1","title":"ETSI TS 119 412-6","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11941206/01.02.01_60/ts_11941206v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11941206/01.02.01_60/ts_11941206v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11941206/01.02.01_20/ts_11941206v010201a.pdf"],"folder":"ETSI/TS-119-412-6-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","sha256":"d0dc8b9ea239e46528c19e741bb64f9989f102cdfdf6db5ead19648fe71dd1e1"}},"tags":["119-series","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","119","412-6","attribute","authorization","certificate","issuer","key","pid","presentation","profile","profiles","seal"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ETSI TS 119 412-6 1.2.1 ETSI TS 119 412-6 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 119 412-6 attribute authorization certificate issuer key pid presentation profile profiles seal 119-series unchanged"},{"id":"ETSI TS 119 422 V1.1.0","type":"specification","body":"ETSI","designation":"TS 119 422","version":"1.1.0","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119422/01.01.00_60/ts_119422v010100p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119422/01.01.00_60/ts_119422v010100p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119422/01.01.00_20/ts_119422v010100a.pdf"],"folder":"ETSI/TS-119-422-V1.1.0","files":{},"tags":["119-series","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ETSI TS 119 422 1.1.0 119-series nested-reference unavailable"},{"id":"ETSI TS 119 432 V1.3.1","type":"specification","body":"ETSI","designation":"TS 119 432","version":"1.3.1","title":"ETSI TS 119 432","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.03.01_60/ts_119432v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.03.01_60/ts_119432v010301p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.03.01_20/ts_119432v010301a.pdf"],"folder":"ETSI/TS-119-432-V1.3.1","files":{"pdf":{"path":"standards/ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","sha256":"6a660566d6a2a1fa57f7cd5c0526ae1127714590a6197ef3adf2b5ee02df3b54"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: authentication, authorization, electronic signature, protocol, remote, security, trust services.","scope_keywords":["authentication","authorization","electronic signature","protocol","remote","security","trust services","119","432","hash","hashing","key","presentation","signature","signatures","trust"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI TS 119 432 1.3.1 ETSI TS 119 432 Covers: authentication, authorization, electronic signature, protocol, remote, security, trust services. authentication authorization electronic signature protocol remote security trust services 119 432 hash hashing key presentation signature signatures trust 119-series cited-by-eu-law implementing-regulation unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI TS 119 461 V2.1.1","type":"specification","body":"ETSI","designation":"TS 119 461","version":"2.1.1","title":"ETSI TS 119 461","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_60/ts_119461v020101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_60/ts_119461v020101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_20/ts_119461v020101a.pdf"],"folder":"ETSI/TS-119-461-V2.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","sha256":"4f8f821a7063b14b704cd5040540bf442e367ba6234591119ffe3d24ca845bd3"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: electronic signature, security, trust services.","scope_keywords":["electronic signature","security","trust services","119","461","authorization","certificate","certificates","eudi","key","management","policies","policy","presentation","qualified","risk"],"parent_legal_regulations":[{"celex":"32025R1566","eli":"https://data.europa.eu/eli/reg_impl/2025/1566/oj/eng","id":"2025-1566","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1566/2025-1566.md","title":"Identity and recipients of qualified certificates"},{"celex":"32026R0798","eli":"https://data.europa.eu/eli/reg_impl/2026/798/oj/eng","id":"2026-798","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-798/2026-798.md","title":"Remote onboarding to EUDI Wallets (eID substantial)"}],"parent_specifications":[],"search_text":"ETSI TS 119 461 2.1.1 ETSI TS 119 461 Covers: electronic signature, security, trust services. electronic signature security trust services 119 461 authorization certificate certificates eudi key management policies policy presentation qualified risk 119-series cited-by-eu-law implementing-regulation unchanged 2025-1566 Identity and recipients of qualified certificates 32025R1566 2026-798 Remote onboarding to EUDI Wallets (eID substantial) 32026R0798"},{"id":"legal:2026-798","type":"legal_regulation","act_id":"2026-798","title":"Remote onboarding to EUDI Wallets (eID substantial)","celex":"32026R0798","eli":"https://data.europa.eu/eli/reg_impl/2026/798/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/371b31a8-32e3-11f1-be39-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2026-798/2026-798.html","sha256":"3d367d68afb6ac16f90d71e11ece5ee06e374eb037ab2f3964333151c89c634a","size":53730},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/371b31a8-32e3-11f1-be39-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2026-798/2026-798.pdf","sha256":"cde2d10b67a421be7a6945fcdc3f4318ddde9700d3503cf88533f4b845604941","size":529662}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for the remote onboarding of users to the European Digital Identity Wallets by electronic identification means conforming to assurance level substantial in conjunction with additional remote onboarding procedures where the combination meets the requirements of assurance level high The onboarding of users to the European Digital Identity Wallets (‘wallets’) is a crucial step as regards the verification of the identity of the wallet users, the binding of the personal identification data of the users to their wallets and to the user device in which the wallet units are installed. To foster a high level of trust and security as well as a harmonised approach across Member States for the onboarding of wallet users with remote…","scope_keywords":["assurance","council","data","digital","electronic","european","high","http","identification","identity","level","means","onboarding","parliament","procedures","regards","regulation","remote","specifications","standards","trust","users","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.568489+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2026-798 Remote onboarding to EUDI Wallets (eID substantial) 32026R0798 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards reference standards and specifications for the remote onboarding of users to the European Digital Identity Wallets by electronic identification means conforming to assurance level substantial in conjunction with additional remote onboarding procedures where the combination meets the requirements of assurance level high The onboarding of users to the European Digital Identity Wallets (‘wallets’) is a crucial step as regards the verification of the identity of the wallet users, the binding of the personal identification data of the users to their wallets and to the user device in which the wallet units are installed. To foster a high level of trust and security as well as a harmonised approach across Member States for the onboarding of wallet users with remote… assurance council data digital electronic european high http identification identity level means onboarding parliament procedures regards regulation remote specifications standards trust users wallet wallets"},{"id":"ETSI TS 119 471 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 471","version":"1.1.1","title":"ETSI TS 119 471","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119471/01.01.01_60/ts_119471v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119471/01.01.01_60/ts_119471v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119471/01.01.01_20/ts_119471v010101a.pdf"],"folder":"ETSI/TS-119-471-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","sha256":"bd1f179cb8dd15c681dd7f2a3ab6c0d6f81fa5be727669124433442fe7b0c94e"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: digital identity, EAA, EUDI wallet, identity, trust services.","scope_keywords":["digital identity","eaa","eudi wallet","identity","trust services","119","471","attestation","attestations","attribute","attributes","authorization","eudi","key","policy","presentation"],"parent_legal_regulations":[{"celex":"32026R1735","eli":"https://data.europa.eu/eli/reg_impl/2026/1735/oj/eng","id":"2026-1735","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1735/2026-1735.md","title":"Amending CIR 2025/1569 — electronic attestations of attributes (EAA)"}],"parent_specifications":[],"search_text":"ETSI TS 119 471 1.1.1 ETSI TS 119 471 Covers: digital identity, EAA, EUDI wallet, identity, trust services. digital identity eaa eudi wallet identity trust services 119 471 attestation attestations attribute attributes authorization eudi key policy presentation 119-series cited-by-eu-law implementing-regulation unchanged 2026-1735 Amending CIR 2025/1569 — electronic attestations of attributes (EAA) 32026R1735"},{"id":"ETSI TS 119 472-1 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 472-1","version":"1.2.1","title":"ETSI TS 119 472-1","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11947201/01.02.01_60/ts_11947201v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11947201/01.02.01_60/ts_11947201v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11947201/01.02.01_20/ts_11947201v010201a.pdf"],"folder":"ETSI/TS-119-472-1-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","sha256":"0f76ce7cad5f046802146b0c2a9cd8af9db3c1db77db5eeca86d2a4559fcfc3f"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: attribute attestation, digital identity, EUDI Wallet, trust services.","scope_keywords":["attribute attestation","digital identity","eudi wallet","trust services","119","472-1","attestation","attribute","attributes","authorization","eudi","issuer","key","presentation","profile","profiles"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI TS 119 472-1 1.2.1 ETSI TS 119 472-1 Covers: attribute attestation, digital identity, EUDI Wallet, trust services. attribute attestation digital identity eudi wallet trust services 119 472-1 attestation attribute attributes authorization eudi issuer key presentation profile profiles 119-series cited-by-eu-law implementing-regulation unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI TS 119 472-2 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 472-2","version":"1.2.1","title":"ETSI TS 119 472-2","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11947202/01.02.01_60/ts_11947202v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11947202/01.02.01_60/ts_11947202v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11947202/01.02.01_20/ts_11947202v010201a.pdf"],"folder":"ETSI/TS-119-472-2-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","sha256":"128c51ed497a82ee01a709070669e53bef4f38a0da3ec8792542f659f86e3b1f"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: attribute attestation, digital identity, EUDI Wallet, trust services.","scope_keywords":["attribute attestation","digital identity","eudi wallet","trust services","119","472-2","attestation","attribute","attributes","authorization","eudi","key","pid","presentation","profile","profiles"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI TS 119 472-2 1.2.1 ETSI TS 119 472-2 Covers: attribute attestation, digital identity, EUDI Wallet, trust services. attribute attestation digital identity eudi wallet trust services 119 472-2 attestation attribute attributes authorization eudi key pid presentation profile profiles 119-series cited-by-eu-law implementing-regulation unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI TS 119 472-3 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 472-3","version":"1.1.1","title":"ETSI TS 119 472-3","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/11947203/01.01.01_60/ts_11947203v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/11947203/01.01.01_60/ts_11947203v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/11947203/01.01.01_20/ts_11947203v010101a.pdf"],"folder":"ETSI/TS-119-472-3-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","sha256":"2919437478c7469881afc5acd5aa68d847a4cfdc1bbf6da9224f4c9fae7167ba"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: attribute attestation, digital identity, EUDI Wallet, trust services.","scope_keywords":["attribute attestation","digital identity","eudi wallet","trust services","119","472-3","attestation","attribute","attributes","certificate","certificates","credential","eudi","issuer","key","pid"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ETSI TS 119 472-3 1.1.1 ETSI TS 119 472-3 Covers: attribute attestation, digital identity, EUDI Wallet, trust services. attribute attestation digital identity eudi wallet trust services 119 472-3 attestation attribute attributes certificate certificates credential eudi issuer key pid 119-series cited-by-eu-law implementing-regulation unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ETSI TS 119 475 V1.2.1","type":"specification","body":"ETSI","designation":"TS 119 475","version":"1.2.1","title":"ETSI TS 119 475","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119475/01.02.01_60/ts_119475v010201p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119475/01.02.01_60/ts_119475v010201p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119475/01.02.01_20/ts_119475v010201a.pdf"],"folder":"ETSI/TS-119-475-V1.2.1","files":{"pdf":{"path":"standards/ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","sha256":"77bf8e71715c495494113da23ccba89c0af8bf6b457fe2da38b5a12738ace55f"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"Covers: digital certificate, digital identity, trust services.","scope_keywords":["digital certificate","digital identity","trust services","119","475","attribute","attributes","authorization","certificate","certificates","eudi","identification","key","policies","presentation","profile"],"parent_legal_regulations":[{"celex":"32026R1730","eli":"https://data.europa.eu/eli/reg_impl/2026/1730/oj/eng","id":"2026-1730","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1730/2026-1730.md","title":"Amending CIR 2025/848 — Relying Party Registration"}],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS06","folder":"ARF/TS06-V1.0.1","source":"ARF/TS06-V1.0.1/TS06-V1.0.1.md","version":"1.0.1"}],"search_text":"ETSI TS 119 475 1.2.1 ETSI TS 119 475 Covers: digital certificate, digital identity, trust services. digital certificate digital identity trust services 119 475 attribute attributes authorization certificate certificates eudi identification key policies presentation profile 119-series cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1730 Amending CIR 2025/848 — Relying Party Registration 32026R1730"},{"id":"ETSI TS 119 478 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 478","version":"1.1.1","title":"ETSI TS 119 478","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119400_119499/119478/01.01.01_60/ts_119478v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119400_119499/119478/01.01.01_60/ts_119478v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119400_119499/119478/01.01.01_20/ts_119478v010101a.pdf"],"folder":"ETSI/TS-119-478-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","sha256":"80926b200713c2a9577d6d24095d7438dc970747b36228541b197f3edd6c6295"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"Covers: API, authentication, authorization, EUDI Wallet, smart interface.","scope_keywords":["api","authentication","authorization","eudi wallet","smart interface","119","478","attestation","attestations","attribute","attributes","eudi","key","presentation","signature","signatures"],"parent_legal_regulations":[{"celex":"32026R1735","eli":"https://data.europa.eu/eli/reg_impl/2026/1735/oj/eng","id":"2026-1735","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1735/2026-1735.md","title":"Amending CIR 2025/1569 — electronic attestations of attributes (EAA)"}],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ETSI TS 119 478 1.1.1 ETSI TS 119 478 Covers: API, authentication, authorization, EUDI Wallet, smart interface. api authentication authorization eudi wallet smart interface 119 478 attestation attestations attribute attributes eudi key presentation signature signatures 119-series cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1735 Amending CIR 2025/1569 — electronic attestations of attributes (EAA) 32026R1735"},{"id":"ETSI TS 119 511 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 511","version":"1.1.1","title":"ETSI TS 119 511","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_20/ts_119511v010101a.pdf"],"folder":"ETSI/TS-119-511-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","sha256":"3130c1e5979de406e1ac9299c424628a09156840809aa0965da0b71511fe4024"}},"tags":["119-series","cited-by-eu-law","implementing-regulation","unchanged"],"summary":"Covers: electronic preservation, electronic signature, trust services.","scope_keywords":["electronic preservation","electronic signature","trust services","119","511","authorization","http","https","key","policies","policy","preservation","profile","profiles","qualified","registered"],"parent_legal_regulations":[{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"}],"parent_specifications":[],"search_text":"ETSI TS 119 511 1.1.1 ETSI TS 119 511 Covers: electronic preservation, electronic signature, trust services. electronic preservation electronic signature trust services 119 511 authorization http https key policies policy preservation profile profiles qualified registered 119-series cited-by-eu-law implementing-regulation unchanged 2025-1946 Qualified preservation services for signatures and seals 32025R1946"},{"id":"ETSI TS 119 602 V1.1.1","type":"specification","body":"ETSI","designation":"TS 119 602","version":"1.1.1","title":"ETSI TS 119 602","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_60/ts_119602v010101p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_60/ts_119602v010101p.pdf","https://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_20/ts_119602v010101a.pdf"],"folder":"ETSI/TS-119-602-V1.1.1","files":{"pdf":{"path":"standards/ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","sha256":"27a00765a20661ecd04076a406b26a5be1123228a2f44a2dc74caeb3041155ec"}},"tags":["119-series","nested-reference","unchanged"],"summary":"Covers: e-commerce, electronic signature, eudi wallet, security, trust services.","scope_keywords":["e-commerce","electronic signature","eudi wallet","security","trust services","119","602","authorization","eudi","key","presentation","profile","profiles","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS03","folder":"ARF/TS03-V1.5.2","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md","version":"1.5.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ETSI TS 119 602 1.1.1 ETSI TS 119 602 Covers: e-commerce, electronic signature, eudi wallet, security, trust services. e-commerce electronic signature eudi wallet security trust services 119 602 authorization eudi key presentation profile profiles signature signatures trust 119-series nested-reference unchanged"},{"id":"ETSI TS 119 612 V2.4.1","type":"specification","body":"ETSI","designation":"TS 119 612","version":"2.4.1","title":"ETSI TS 119 612","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf","https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_20/ts_119612v020401a.pdf"],"folder":"ETSI/TS-119-612-V2.4.1","files":{"pdf":{"path":"standards/ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","sha256":"83285a1069e369d225cf16a0051a46b1f9d8961b6ad5d66bb7650351309a5196"}},"tags":["119-series","cited-by-eu-law","implementing-decision","implementing-regulation","nested-reference","unchanged"],"summary":"Covers: e-commerce, electronic signature, security, trust services.","scope_keywords":["e-commerce","electronic signature","security","trust services","119","612","accreditation","authorization","certificate","certificates","conformity","key","presentation","qualified","seal","signature"],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1945","eli":"https://data.europa.eu/eli/reg_impl/2025/1945/oj/eng","id":"2025-1945","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1945/2025-1945.md","title":"Qualified certificates for signatures and seals"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"},{"celex":"32025D2164","eli":"https://data.europa.eu/eli/dec_impl/2025/2164/oj/eng","id":"2025-2164","kind":"implementing_decision","section":"implementing-decisions","source":"implementing-decisions/2025-2164/2025-2164.md","title":"Trusted lists of trust service providers"}],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ETSI TS 119 612 2.4.1 ETSI TS 119 612 Covers: e-commerce, electronic signature, security, trust services. e-commerce electronic signature security trust services 119 612 accreditation authorization certificate certificates conformity key presentation qualified seal signature 119-series cited-by-eu-law implementing-decision implementing-regulation nested-reference unchanged 2025-1942 Recognition of qualified validation services 32025R1942 2025-1945 Qualified certificates for signatures and seals 32025R1945 2025-2162 Accreditation of conformity assessment bodies 32025R2162 2025-2164 Trusted lists of trust service providers 32025D2164"},{"id":"legal:2025-2164","type":"legal_regulation","act_id":"2025-2164","title":"Trusted lists of trust service providers","celex":"32025D2164","eli":"https://data.europa.eu/eli/dec_impl/2025/2164/oj/eng","kind":"implementing_decision","section":"implementing-decisions","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/8f6925cf-b39f-11f0-b37f-01aa75ed71a1.0006.03/DOC_1","path":"implementing-decisions/2025-2164/2025-2164.html","sha256":"8623cd654017fc3ea5045e1e3064837fc3d9d807f39fea66f707e4c1b59c320a","size":97717},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/8f6925cf-b39f-11f0-b37f-01aa75ed71a1.0006.01/DOC_1","path":"implementing-decisions/2025-2164/2025-2164.pdf","sha256":"c7b006707431357cd1f07bbcf2a467a6fbbbc42bc05ca075436ecad1d13aff82","size":906175}},"summary":"amending Implementing Decision (EU) 2015/1505 as regards the version of the standard on which the common template for the trusted lists is based Trusted lists provided for in Article 22(1) of Regulation (EU) No 910/2014 are essential for building trust among market operators as they allow a validation of the qualified status of the trust service providers and of the trust services they provide. Therefore, qualified trust service providers are only to begin to provide a qualified trust service after the qualified status has been indicated in the trusted lists. Commission Implementing Decision (EU) 2015/1505  ( 2 ) lays down technical specifications and formats relating to trusted lists. Those specifications and formats leverage the specifications and requirements set out in standard ETSI TS 119 612 version 2.1.1.","scope_keywords":["article","commission","common","decision","electronic","european","formats","has","http","implementing","lists","market","providers","qualified","regards","regulation","service","services","set","specifications","status","trust","trusted","validation"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.579050+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-2164 Trusted lists of trust service providers 32025D2164 implementing_decision implementing-decisions amending Implementing Decision (EU) 2015/1505 as regards the version of the standard on which the common template for the trusted lists is based Trusted lists provided for in Article 22(1) of Regulation (EU) No 910/2014 are essential for building trust among market operators as they allow a validation of the qualified status of the trust service providers and of the trust services they provide. Therefore, qualified trust service providers are only to begin to provide a qualified trust service after the qualified status has been indicated in the trusted lists. Commission Implementing Decision (EU) 2015/1505  ( 2 ) lays down technical specifications and formats relating to trusted lists. Those specifications and formats leverage the specifications and requirements set out in standard ETSI TS 119 612 version 2.1.1. article commission common decision electronic european formats has http implementing lists market providers qualified regards regulation service services set specifications status trust trusted validation"},{"id":"ETSI TS 119 615 V1.3.1","type":"specification","body":"ETSI","designation":"TS 119 615","version":"1.3.1","title":"ETSI TS 119 615","purpose":null,"status":"unchanged","download_url":"https://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.03.01_60/ts_119615v010301p.pdf","download_urls":["https://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.03.01_60/ts_119615v010301p.pdf","https://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.03.01_20/ts_119615v010301a.pdf"],"folder":"ETSI/TS-119-615-V1.3.1","files":{"pdf":{"path":"standards/ETSI/TS-119-615-V1.3.1/TS-119-615-V1.3.1.pdf","sha256":"06507df3ae7d1d2b957964c264f18477c6cfa6f40b352d550002f9202286869c"}},"tags":["119-series","unchanged"],"summary":"Covers: e-commerce, electronic signature, EU qualified, security, trust services.","scope_keywords":["e-commerce","electronic signature","eu qualified","security","trust services","119","615","authorization","certificate","key","presentation","qualified","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ETSI TS 119 615 1.3.1 ETSI TS 119 615 Covers: e-commerce, electronic signature, EU qualified, security, trust services. e-commerce electronic signature eu qualified security trust services 119 615 authorization certificate key presentation qualified signature signatures trust 119-series unchanged"},{"id":"IEEE IEEE -","type":"specification","body":"IEEE","designation":"IEEE -","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/-.html","download_urls":["https://standards.ieee.org/standard/-.html"],"folder":"IEEE/IEEE--","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null}],"search_text":"IEEE IEEE - nested-reference unavailable"},{"id":"IETF RFC 1060","type":"specification","body":"IETF","designation":"RFC 1060","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1060.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1060.txt","https://www.rfc-editor.org/rfc/rfc1060.pdf"],"folder":"IETF/RFC-1060","files":{"txt":{"path":"standards/IETF/RFC-1060/RFC-1060.txt","sha256":"ca85d33f6c126a6124476e6ce13f7f8b4fce5f6bc533e8c50b7daee0a75edc6c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1060 J. Postel\nObsoletes RFCs: 1010, 990, 960, 943, 923, 900, 870, ISI\n820, 790, 776, 770, 762, 758,755, 750, 739, 604, March 1990\n503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nSTATUS OF THIS MEMO\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\n Table of Contents\n\nINTRODUCTION.................................................... 2\nData Notations.................................................. 3\nSpecial Addresses............................................... 4\nVERSION NUMBERS................................................. 6\nPROTOCOL NUMBERS................................................ 7\nPORT NUMBERS.................................................... 9\nUNIX PORTS................................","scope_keywords":["1060","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1172","folder":"IETF/RFC-1172","source":"IETF/RFC-1172/RFC-1172.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1224","folder":"IETF/RFC-1224","source":"IETF/RFC-1224/RFC-1224.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null},{"body":"IETF","designation":"RFC 1246","folder":"IETF/RFC-1246","source":"IETF/RFC-1246/RFC-1246.txt","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1331","folder":"IETF/RFC-1331","source":"IETF/RFC-1331/RFC-1331.txt","version":null},{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null}],"search_text":"IETF RFC 1060 Network Working Group J. Reynolds\nRequest for Comments: 1060 J. Postel\nObsoletes RFCs: 1010, 990, 960, 943, 923, 900, 870, ISI\n820, 790, 776, 770, 762, 758,755, 750, 739, 604, March 1990\n503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nSTATUS OF THIS MEMO\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\n Table of Contents\n\nINTRODUCTION.................................................... 2\nData Notations.................................................. 3\nSpecial Addresses............................................... 4\nVERSION NUMBERS................................................. 6\nPROTOCOL NUMBERS................................................ 7\nPORT NUMBERS.................................................... 9\nUNIX PORTS................................ 1060 encryption key management nested-reference unchanged"},{"id":"IETF RFC 1340","type":"specification","body":"IETF","designation":"RFC 1340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1340.txt","https://www.rfc-editor.org/rfc/rfc1340.pdf"],"folder":"IETF/RFC-1340","files":{"txt":{"path":"standards/IETF/RFC-1340/RFC-1340.txt","sha256":"c20ce52dbcdcf311d83c8a42138f27d99d8287364d74bdc30c4e24aabede78a1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1340 J. Postel\nObsoletes RFCs: 1060, 1010, 990, 960, ISI\n943, 923, 900, 870, 820, 790, 776, 770, July 1992\n762, 758,755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n INTRODUCTION................................................... 2\n Data Notations................................................. 3\n Special Addresses.............................................. 4\n VERSION NUMBERS................................................ 6\n PROTOCOL NUMBERS............................................... 7\n WELL KNOWN PORT NUMBERS........................................ 9\n REGISTERED PORT NUMBERS..............","scope_keywords":["1340","encryption","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1334","folder":"IETF/RFC-1334","source":"IETF/RFC-1334/RFC-1334.txt","version":null},{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1393","folder":"IETF/RFC-1393","source":"IETF/RFC-1393/RFC-1393.txt","version":null},{"body":"IETF","designation":"RFC 1408","folder":"IETF/RFC-1408","source":"IETF/RFC-1408/RFC-1408.txt","version":null},{"body":"IETF","designation":"RFC 1409","folder":"IETF/RFC-1409","source":"IETF/RFC-1409/RFC-1409.txt","version":null},{"body":"IETF","designation":"RFC 1413","folder":"IETF/RFC-1413","source":"IETF/RFC-1413/RFC-1413.txt","version":null},{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1416","folder":"IETF/RFC-1416","source":"IETF/RFC-1416/RFC-1416.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1492","folder":"IETF/RFC-1492","source":"IETF/RFC-1492/RFC-1492.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1522","folder":"IETF/RFC-1522","source":"IETF/RFC-1522/RFC-1522.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1548","folder":"IETF/RFC-1548","source":"IETF/RFC-1548/RFC-1548.txt","version":null},{"body":"IETF","designation":"RFC 1552","folder":"IETF/RFC-1552","source":"IETF/RFC-1552/RFC-1552.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1570","folder":"IETF/RFC-1570","source":"IETF/RFC-1570/RFC-1570.txt","version":null},{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1590","folder":"IETF/RFC-1590","source":"IETF/RFC-1590/RFC-1590.txt","version":null},{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1602","folder":"IETF/RFC-1602","source":"IETF/RFC-1602/RFC-1602.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1639","folder":"IETF/RFC-1639","source":"IETF/RFC-1639/RFC-1639.txt","version":null},{"body":"IETF","designation":"RFC 1661","folder":"IETF/RFC-1661","source":"IETF/RFC-1661/RFC-1661.txt","version":null},{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null},{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 1340 Network Working Group J. Reynolds\nRequest for Comments: 1340 J. Postel\nObsoletes RFCs: 1060, 1010, 990, 960, ISI\n943, 923, 900, 870, 820, 790, 776, 770, July 1992\n762, 758,755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n INTRODUCTION................................................... 2\n Data Notations................................................. 3\n Special Addresses.............................................. 4\n VERSION NUMBERS................................................ 6\n PROTOCOL NUMBERS............................................... 7\n WELL KNOWN PORT NUMBERS........................................ 9\n REGISTERED PORT NUMBERS.............. 1340 encryption key management registered nested-reference unchanged"},{"id":"IETF RFC 1700","type":"specification","body":"IETF","designation":"RFC 1700","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1700.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1700.txt","https://www.rfc-editor.org/rfc/rfc1700.pdf"],"folder":"IETF/RFC-1700","files":{"txt":{"path":"standards/IETF/RFC-1700/RFC-1700.txt","sha256":"77de0532a5b4b6bef3d233795b5a87aae1838358b98e7da82676e0c6455eb03e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1700 J. Postel\nSTD: 2 ISI\nObsoletes RFCs: 1340, 1060, 1010, 990, 960, October 1994\n943, 923, 900, 870, 820, 790, 776, 770,\n762, 758,755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\nCategory: Standards Track\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\nOVERVIEW\n\nThis RFC is a snapshot of the ongoing process of the assignment of\nprotocol parameters for the Internet protocol suite. To make the\ncurrent information readily available the assignments are kept up-to-\ndate in a set of online text files. This RFC has been assembled by\ncatinating these files together with a minimum of formatting \"glue\".\nThe authors appologize for the somewhat rougher formatting and style\n","scope_keywords":["1700","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1710","folder":"IETF/RFC-1710","source":"IETF/RFC-1710/RFC-1710.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 1788","folder":"IETF/RFC-1788","source":"IETF/RFC-1788/RFC-1788.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1851","folder":"IETF/RFC-1851","source":"IETF/RFC-1851/RFC-1851.txt","version":null},{"body":"IETF","designation":"RFC 1852","folder":"IETF/RFC-1852","source":"IETF/RFC-1852/RFC-1852.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1962","folder":"IETF/RFC-1962","source":"IETF/RFC-1962/RFC-1962.txt","version":null},{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 1994","folder":"IETF/RFC-1994","source":"IETF/RFC-1994/RFC-1994.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2059","folder":"IETF/RFC-2059","source":"IETF/RFC-2059/RFC-2059.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2139","folder":"IETF/RFC-2139","source":"IETF/RFC-2139/RFC-2139.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2181","folder":"IETF/RFC-2181","source":"IETF/RFC-2181/RFC-2181.txt","version":null},{"body":"IETF","designation":"RFC 2189","folder":"IETF/RFC-2189","source":"IETF/RFC-2189/RFC-2189.txt","version":null},{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2283","folder":"IETF/RFC-2283","source":"IETF/RFC-2283/RFC-2283.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2335","folder":"IETF/RFC-2335","source":"IETF/RFC-2335/RFC-2335.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2365","folder":"IETF/RFC-2365","source":"IETF/RFC-2365/RFC-2365.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2723","folder":"IETF/RFC-2723","source":"IETF/RFC-2723/RFC-2723.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3025","folder":"IETF/RFC-3025","source":"IETF/RFC-3025/RFC-3025.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3208","folder":"IETF/RFC-3208","source":"IETF/RFC-3208/RFC-3208.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3232","folder":"IETF/RFC-3232","source":"IETF/RFC-3232/RFC-3232.txt","version":null},{"body":"IETF","designation":"RFC 3309","folder":"IETF/RFC-3309","source":"IETF/RFC-3309/RFC-3309.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3359","folder":"IETF/RFC-3359","source":"IETF/RFC-3359/RFC-3359.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 1700 Network Working Group J. Reynolds\nRequest for Comments: 1700 J. Postel\nSTD: 2 ISI\nObsoletes RFCs: 1340, 1060, 1010, 990, 960, October 1994\n943, 923, 900, 870, 820, 790, 776, 770,\n762, 758,755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\nCategory: Standards Track\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the parameters (i.e., numbers and\n keywords) used in protocols in the Internet community. Distribution\n of this memo is unlimited.\n\nOVERVIEW\n\nThis RFC is a snapshot of the ongoing process of the assignment of\nprotocol parameters for the Internet protocol suite. To make the\ncurrent information readily available the assignments are kept up-to-\ndate in a set of online text files. This RFC has been assembled by\ncatinating these files together with a minimum of formatting \"glue\".\nThe authors appologize for the somewhat rougher formatting and style\n 1700 key management nested-reference unchanged"},{"id":"IETF RFC 2764","type":"specification","body":"IETF","designation":"RFC 2764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2764.txt","https://www.rfc-editor.org/rfc/rfc2764.pdf"],"folder":"IETF/RFC-2764","files":{"txt":{"path":"standards/IETF/RFC-2764/RFC-2764.txt","sha256":"0ba1f8f1de0fd1b770a2d3484e84a1933889ab10cfd2d8ad6690c2fa2cf71c1d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for Virtual Private Networks\n (VPNs) running across IP backbones. It discusses the various\n different types of VPNs, their respective requirements, and proposes\n specific mechanisms that could be used to implement each type of VPN\n using existing or proposed specifications. The objective of this\n document is to serve as a framework for related protocol development\n in order to develop the full set of specifications required for\n widespread deployment of interoperable VPN solutions.\n\nGleeson, et al. Informational [Page 1]\n\f\nRFC 2764 IP Based Virtual Private Networks February 2000","scope_keywords":["2764","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 4026","folder":"IETF/RFC-4026","source":"IETF/RFC-4026/RFC-4026.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null}],"search_text":"IETF RFC 2764 This document describes a framework for Virtual Private Networks\n (VPNs) running across IP backbones. It discusses the various\n different types of VPNs, their respective requirements, and proposes\n specific mechanisms that could be used to implement each type of VPN\n using existing or proposed specifications. The objective of this\n document is to serve as a framework for related protocol development\n in order to develop the full set of specifications required for\n widespread deployment of interoperable VPN solutions.\n\nGleeson, et al. Informational [Page 1]\n\f\nRFC 2764 IP Based Virtual Private Networks February 2000 2764 management nested-reference unchanged"},{"id":"IETF RFC 6325","type":"specification","body":"IETF","designation":"RFC 6325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6325.txt","https://www.rfc-editor.org/rfc/rfc6325.pdf"],"folder":"IETF/RFC-6325","files":{"txt":{"path":"standards/IETF/RFC-6325/RFC-6325.txt","sha256":"1b5c66cc4504d19fa8d20e133f3ea5dd2aeedafb4e1a90feb111fc98d5360eb4"}},"tags":["nested-reference","unchanged"],"summary":"Routing Bridges (RBridges) provide optimal pair-wise forwarding\n without configuration, safe forwarding even during periods of\n temporary loops, and support for multipathing of both unicast and\n multicast traffic. They achieve these goals using IS-IS routing and\n encapsulation of traffic with a header that includes a hop count.\n\n RBridges are compatible with previous IEEE 802.1 customer bridges as\n well as IPv4 and IPv6 routers and end nodes. They are as invisible\n to current IP routers as bridges are and, like routers, they\n terminate the bridge spanning tree protocol.\n\n The design supports VLANs and the optimization of the distribution of\n multi-destination frames based on VLAN ID and based on IP-derived\n multicast groups. It also allows unicast forwarding tables at\n transit RBridges to be sized according to the number of RBridges\n (rather than the number of end nodes), which allows th","scope_keywords":["6325","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IETF RFC 6325 Routing Bridges (RBridges) provide optimal pair-wise forwarding\n without configuration, safe forwarding even during periods of\n temporary loops, and support for multipathing of both unicast and\n multicast traffic. They achieve these goals using IS-IS routing and\n encapsulation of traffic with a header that includes a hop count.\n\n RBridges are compatible with previous IEEE 802.1 customer bridges as\n well as IPv4 and IPv6 routers and end nodes. They are as invisible\n to current IP routers as bridges are and, like routers, they\n terminate the bridge spanning tree protocol.\n\n The design supports VLANs and the optimization of the distribution of\n multi-destination frames based on VLAN ID and based on IP-derived\n multicast groups. It also allows unicast forwarding tables at\n transit RBridges to be sized according to the number of RBridges\n (rather than the number of end nodes), which allows th 6325 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7174","type":"specification","body":"IETF","designation":"RFC 7174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7174.txt","https://www.rfc-editor.org/rfc/rfc7174.pdf"],"folder":"IETF/RFC-7174","files":{"txt":{"path":"standards/IETF/RFC-7174/RFC-7174.txt","sha256":"9423687e1c99520bb8ed67a7de289af46e54095064f617e5986ac3c1ed6f8d27"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a reference framework for Operations,\n Administration, and Maintenance (OAM) in Transparent Interconnection\n of Lots of Links (TRILL) networks. The focus of the document is on\n the fault and performance management aspects of TRILL OAM.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-","scope_keywords":["7174","delivery","http","identification","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null}],"search_text":"IETF RFC 7174 This document specifies a reference framework for Operations,\n Administration, and Maintenance (OAM) in Transparent Interconnection\n of Lots of Links (TRILL) networks. The focus of the document is on\n the fault and performance management aspects of TRILL OAM.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc- 7174 delivery http identification license management path subject trust nested-reference unchanged"},{"id":"IEEE IEEE --","type":"specification","body":"IEEE","designation":"IEEE --","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/--.html","download_urls":["https://standards.ieee.org/standard/--.html"],"folder":"IEEE/IEEE---","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null}],"search_text":"IEEE IEEE -- nested-reference unavailable"},{"id":"IETF RFC 1230","type":"specification","body":"IETF","designation":"RFC 1230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1230.txt","https://www.rfc-editor.org/rfc/rfc1230.pdf"],"folder":"IETF/RFC-1230","files":{"txt":{"path":"standards/IETF/RFC-1230/RFC-1230.txt","sha256":"871e4c5082c905a4a4105e4bf7205edc091a9a104bfe4811e13b3c7a54a11719"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines managed\n objects used for managing subnetworks which use the IEEE 802.4 Token\n Bus technology described in 802.4 Token-Passing Bus Access Method and\n Physical Layer Specifications, IEEE Standard 802.4.\n\nTransmission Working Group [Page 1]\n\f\nRFC 1230 IEEE 802.4 MIB May 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of","scope_keywords":["1230","management","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1230 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines managed\n objects used for managing subnetworks which use the IEEE 802.4 Token\n Bus technology described in 802.4 Token-Passing Bus Access Method and\n Physical Layer Specifications, IEEE Standard 802.4.\n\nTransmission Working Group [Page 1]\n\f\nRFC 1230 IEEE 802.4 MIB May 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of 1230 management registered subject nested-reference unchanged"},{"id":"IETF RFC 1285","type":"specification","body":"IETF","designation":"RFC 1285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1285.txt","https://www.rfc-editor.org/rfc/rfc1285.pdf"],"folder":"IETF/RFC-1285","files":{"txt":{"path":"standards/IETF/RFC-1285/RFC-1285.txt","sha256":"8413a544277d356c45404325ab8e7836ca35fcae380c64115416c734ea854b5b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing devices which\n implement the FDDI.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\nCase [Page 1]\n\f\nRFC 1285 FDDI MIB January 1992\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for net","scope_keywords":["1285","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1285 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing devices which\n implement the FDDI.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\nCase [Page 1]\n\f\nRFC 1285 FDDI MIB January 1992\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for net 1285 management path subject nested-reference unchanged"},{"id":"IETF RFC 1512","type":"specification","body":"IETF","designation":"RFC 1512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1512.txt","https://www.rfc-editor.org/rfc/rfc1512.pdf"],"folder":"IETF/RFC-1512","files":{"txt":{"path":"standards/IETF/RFC-1512/RFC-1512.txt","sha256":"fc233f074714700baedcf116a0760685b0399fd87d4262738ff00d51229085bc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing devices which\n implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard [8],\n which has been forwarded for publication by the X3T9.5 committee.","scope_keywords":["1512","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1512 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing devices which\n implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard [8],\n which has been forwarded for publication by the X3T9.5 committee. 1512 management path nested-reference unchanged"},{"id":"IEEE IEEE ---","type":"specification","body":"IEEE","designation":"IEEE ---","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/---.html","download_urls":["https://standards.ieee.org/standard/---.html"],"folder":"IEEE/IEEE----","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IEEE IEEE --- nested-reference unavailable"},{"id":"IETF RFC 1010","type":"specification","body":"IETF","designation":"RFC 1010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1010.txt","https://www.rfc-editor.org/rfc/rfc1010.pdf"],"folder":"IETF/RFC-1010","files":{"txt":{"path":"standards/IETF/RFC-1010/RFC-1010.txt","sha256":"f40e83dee4fbfe013e83ff5cc25ab5a5f629475605f793dfa4138cb20567cdea"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1010 J. Postel\n ISI\nObsoletes RFCs: 990, 960, 943, 923, 900, 870, May 1987\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the Internet community. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. If you are developing a protocol or application\n that will require the use of a link, socket, port, protocol, etc.,\n please contact Joyce to receive a number assignment.\n\n Joyce K. Reynolds\n USC - Inf","scope_keywords":["1010","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1081","folder":"IETF/RFC-1081","source":"IETF/RFC-1081/RFC-1081.txt","version":null},{"body":"IETF","designation":"RFC 1091","folder":"IETF/RFC-1091","source":"IETF/RFC-1091/RFC-1091.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1131","folder":"IETF/RFC-1131","source":"IETF/RFC-1131/RFC-1131.pdf","version":null},{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null}],"search_text":"IETF RFC 1010 Network Working Group J. Reynolds\nRequest for Comments: 1010 J. Postel\n ISI\nObsoletes RFCs: 990, 960, 943, 923, 900, 870, May 1987\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the Internet community. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. If you are developing a protocol or application\n that will require the use of a link, socket, port, protocol, etc.,\n please contact Joyce to receive a number assignment.\n\n Joyce K. Reynolds\n USC - Inf 1010 key management nested-reference unchanged"},{"id":"IETF RFC 990","type":"specification","body":"IETF","designation":"RFC 990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc990.txt","https://www.rfc-editor.org/rfc/rfc990.pdf"],"folder":"IETF/RFC-990","files":{"txt":{"path":"standards/IETF/RFC-990/RFC-990.txt","sha256":"f9a341462ed2f494d7878ad27ac4f7803bf1efa13a16ad9c41c5facd8c7da33a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 990 J. Postel\n ISI\nObsoletes RFCs: 960, 943, 923, 900, November 1986\n870, 820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please con","scope_keywords":["990"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1002","folder":"IETF/RFC-1002","source":"IETF/RFC-1002/RFC-1002.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 990 Network Working Group J. Reynolds\nRequest for Comments: 990 J. Postel\n ISI\nObsoletes RFCs: 960, 943, 923, 900, November 1986\n870, 820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please con 990 nested-reference unchanged"},{"id":"IEEE IEEE -----","type":"specification","body":"IEEE","designation":"IEEE -----","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/-----.html","download_urls":["https://standards.ieee.org/standard/-----.html"],"folder":"IEEE/IEEE------","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IEEE IEEE ----- nested-reference unavailable"},{"id":"IETF RFC 4363","type":"specification","body":"IETF","designation":"RFC 4363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4363.txt","https://www.rfc-editor.org/rfc/rfc4363.pdf"],"folder":"IETF/RFC-4363","files":{"txt":{"path":"standards/IETF/RFC-4363/RFC-4363.txt","sha256":"2abcfd71569fc8788644faa0e91a3bc6602e76c7c9e49c5e04c43f91cdcb3183"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines two MIB modules for managing the\n capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC\n Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards\n for bridging between Local Area Network (LAN) segments. One MIB\n module defines objects for managing the 'Traffic Classes' and\n 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and\n P802.1t-2001 (TM). The other MIB module defines objects for managing\n VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM), and P802.1v\n (TM).\n\n Provisions are made for support of transparent bridging. Provisions\n are also made so that these objects apply to bridges connected by\n subnetworks other than LAN segments.\n\n This memo supplements RFC 4188 and obsoletes R","scope_keywords":["4363","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4363 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines two MIB modules for managing the\n capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC\n Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards\n for bridging between Local Area Network (LAN) segments. One MIB\n module defines objects for managing the 'Traffic Classes' and\n 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and\n P802.1t-2001 (TM). The other MIB module defines objects for managing\n VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM), and P802.1v\n (TM).\n\n Provisions are made for support of transparent bridging. Provisions\n are also made so that these objects apply to bridges connected by\n subnetworks other than LAN segments.\n\n This memo supplements RFC 4188 and obsoletes R 4363 management subject nested-reference unchanged"},{"id":"IEEE IEEE .....................96","type":"specification","body":"IEEE","designation":"IEEE .....................96","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/.....................96.html","download_urls":["https://standards.ieee.org/standard/.....................96.html"],"folder":"IEEE/IEEE-.....................96","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IEEE IEEE .....................96 nested-reference unavailable"},{"id":"IEEE IEEE 100","type":"specification","body":"IEEE","designation":"IEEE 100","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/100.html","download_urls":["https://standards.ieee.org/standard/100.html"],"folder":"IEEE/IEEE-100","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null}],"search_text":"IEEE IEEE 100 nested-reference unavailable"},{"id":"IETF RFC 6988","type":"specification","body":"IETF","designation":"RFC 6988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6988.txt","https://www.rfc-editor.org/rfc/rfc6988.pdf"],"folder":"IETF/RFC-6988","files":{"txt":{"path":"standards/IETF/RFC-6988/RFC-6988.txt","sha256":"b5e23e1bb1ee7614ff6b054e7ecc32714aa4536933d3364ad02258f319ff68eb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines requirements for standards specifications for\n Energy Management. The requirements defined in this document are\n concerned with monitoring functions as well as control functions.\n Monitoring functions include identifying energy-managed devices and\n their components, as well as monitoring their Power States, Power\n Inlets, Power Outlets, actual power, Power Attributes, received\n energy, provided energy, and contained batteries. Control functions\n include such functions as controlling power supply and Power State of\n energy-managed devices and their components.\n\n This document does not specify the features that must be implemented\n by compliant implementations but rather lists features that must be\n supported by standards for Energy Management.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pur","scope_keywords":["6988","attribute","attributes","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 6988 This document defines requirements for standards specifications for\n Energy Management. The requirements defined in this document are\n concerned with monitoring functions as well as control functions.\n Monitoring functions include identifying energy-managed devices and\n their components, as well as monitoring their Power States, Power\n Inlets, Power Outlets, actual power, Power Attributes, received\n energy, provided energy, and contained batteries. Control functions\n include such functions as controlling power supply and Power State of\n energy-managed devices and their components.\n\n This document does not specify the features that must be implemented\n by compliant implementations but rather lists features that must be\n supported by standards for Energy Management.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pur 6988 attribute attributes http identification license management subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1003.1","type":"specification","body":"IEEE","designation":"IEEE 1003.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.1.html","download_urls":["https://standards.ieee.org/standard/1003.1.html"],"folder":"IEEE/IEEE-1003.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2133","folder":"IETF/RFC-2133","source":"IETF/RFC-2133/RFC-2133.txt","version":null},{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3679","folder":"IETF/RFC-3679","source":"IETF/RFC-3679/RFC-3679.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8943","folder":"IETF/RFC-8943","source":"IETF/RFC-8943/RFC-8943.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IEEE IEEE 1003.1 nested-reference unavailable"},{"id":"IETF RFC 2130","type":"specification","body":"IETF","designation":"RFC 2130","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2130.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2130.txt","https://www.rfc-editor.org/rfc/rfc2130.pdf"],"folder":"IETF/RFC-2130","files":{"txt":{"path":"standards/IETF/RFC-2130/RFC-2130.txt","sha256":"e08fc9e575ddf7da3e5d68a9934a94ade2a94d0f2eade59534b4c14a429616e2"}},"tags":["nested-reference","unchanged"],"summary":"0: Executive summary.......................................... 2\n 1: Introduction............................................... 3\n 2: Character sets on the Internet -- the problem.............. 3\n 2.1: Character set handling in existing protocols............... 4\n 3: Architectural model........................................ 6\n 3.1: Segments defined........................................... 7\n 3.2: On the wire................................................ 8\n\nWeider, et. al. Informational [Page 1]\n\f\nRFC 2130 Character Set Workshop Report April 1997","scope_keywords":["2130","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3375","folder":"IETF/RFC-3375","source":"IETF/RFC-3375/RFC-3375.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"IETF RFC 2130 0: Executive summary.......................................... 2\n 1: Introduction............................................... 3\n 2: Character sets on the Internet -- the problem.............. 3\n 2.1: Character set handling in existing protocols............... 4\n 3: Architectural model........................................ 6\n 3.1: Segments defined........................................... 7\n 3.2: On the wire................................................ 8\n\nWeider, et. al. Informational [Page 1]\n\f\nRFC 2130 Character Set Workshop Report April 1997 2130 presentation nested-reference unchanged"},{"id":"IETF RFC 2133","type":"specification","body":"IETF","designation":"RFC 2133","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2133.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2133.txt","https://www.rfc-editor.org/rfc/rfc2133.pdf"],"folder":"IETF/RFC-2133","files":{"txt":{"path":"standards/IETF/RFC-2133/RFC-2133.txt","sha256":"2b0897d4522a5b0de358aa661922c69792c7aeca973ad48b15cac3bfd9fd70a3"}},"tags":["nested-reference","unchanged"],"summary":"The de facto standard application program interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl","scope_keywords":["2133","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2292","folder":"IETF/RFC-2292","source":"IETF/RFC-2292/RFC-2292.txt","version":null},{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null}],"search_text":"IETF RFC 2133 The de facto standard application program interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl 2133 identification nested-reference unchanged"},{"id":"IETF RFC 2553","type":"specification","body":"IETF","designation":"RFC 2553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2553.txt","https://www.rfc-editor.org/rfc/rfc2553.pdf"],"folder":"IETF/RFC-2553","files":{"txt":{"path":"standards/IETF/RFC-2553/RFC-2553.txt","sha256":"e459f3196ca085a9263ac29c6179ea922787ac81318bb851a7c4efaffae780e4"}},"tags":["nested-reference","unchanged"],"summary":"The de facto standard application program interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl","scope_keywords":["2553","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null}],"search_text":"IETF RFC 2553 The de facto standard application program interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl 2553 identification nested-reference unchanged"},{"id":"IETF RFC 2828","type":"specification","body":"IETF","designation":"RFC 2828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2828.txt","https://www.rfc-editor.org/rfc/rfc2828.pdf"],"folder":"IETF/RFC-2828","files":{"txt":{"path":"standards/IETF/RFC-2828/RFC-2828.txt","sha256":"b956b466d041e4d10a1ef8133100406375092535c05b3d8d66f54bbe1f8ed176"}},"tags":["nested-reference","unchanged"],"summary":"This Glossary (191 pages of definitions and 13 pages of references)\n provides abbreviations, explanations, and recommendations for use of\n information system security terminology. The intent is to improve the\n comprehensibility of writing that deals with Internet security,\n particularly Internet Standards documents (ISDs). To avoid confusion,\n ISDs should use the same term or definition whenever the same concept\n is mentioned. To improve international understanding, ISDs should use\n terms in their plainest, dictionary sense. ISDs should use terms\n established in standards documents and other well-founded\n publications and should avoid substituting private or newly made-up\n terms. ISDs should avoid terms that are proprietary or otherwise\n favor a particular vendor, or that create a bias toward a particular\n security technology or mechanism versus other, competing techniques\n that already ","scope_keywords":["2828","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4766","folder":"IETF/RFC-4766","source":"IETF/RFC-4766/RFC-4766.txt","version":null},{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2828 This Glossary (191 pages of definitions and 13 pages of references)\n provides abbreviations, explanations, and recommendations for use of\n information system security terminology. The intent is to improve the\n comprehensibility of writing that deals with Internet security,\n particularly Internet Standards documents (ISDs). To avoid confusion,\n ISDs should use the same term or definition whenever the same concept\n is mentioned. To improve international understanding, ISDs should use\n terms in their plainest, dictionary sense. ISDs should use terms\n established in standards documents and other well-founded\n publications and should avoid substituting private or newly made-up\n terms. ISDs should avoid terms that are proprietary or otherwise\n favor a particular vendor, or that create a bias toward a particular\n security technology or mechanism versus other, competing techniques\n that already  2828 key nested-reference unchanged"},{"id":"IETF RFC 3679","type":"specification","body":"IETF","designation":"RFC 3679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3679.txt","https://www.rfc-editor.org/rfc/rfc3679.pdf"],"folder":"IETF/RFC-3679","files":{"txt":{"path":"standards/IETF/RFC-3679/RFC-3679.txt","sha256":"f962fd3bdb4ff7d6744ac05be880d71bdbea735578f8218d3c1d5cc72fa82852"}},"tags":["nested-reference","unchanged"],"summary":"Prior to the publication of RFC 2489 (which was updated by RFC 2939),\n several option codes were assigned to proposed Dynamic Host\n Configuration Protocol (DHCP) options that were subsequently never\n used. This document lists those unused option codes and directs IANA\n to make these option codes available for assignment to other DHCP\n options in the future.\n\n The document also lists several option codes that are not currently\n documented in an RFC but should not be made available for\n reassignment to future DHCP options.\n\n1. Introduction\n\n Section 2 of this document lists the unused DHCP option codes from\n the IANA list of BOOTP and DHCP option codes [1]. Each option code\n includes any known documentation and contact information from the\n IANA list. IANA will make these option codes available for\n assignment to other DHCP options in the future.\n\n Section 3 lists several DHCP option codes","scope_keywords":["3679","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null}],"search_text":"IETF RFC 3679 Prior to the publication of RFC 2489 (which was updated by RFC 2939),\n several option codes were assigned to proposed Dynamic Host\n Configuration Protocol (DHCP) options that were subsequently never\n used. This document lists those unused option codes and directs IANA\n to make these option codes available for assignment to other DHCP\n options in the future.\n\n The document also lists several option codes that are not currently\n documented in an RFC but should not be made available for\n reassignment to future DHCP options.\n\n1. Introduction\n\n Section 2 of this document lists the unused DHCP option codes from\n the IANA list of BOOTP and DHCP option codes [1]. Each option code\n includes any known documentation and contact information from the\n IANA list. IANA will make these option codes available for\n assignment to other DHCP options in the future.\n\n Section 3 lists several DHCP option codes 3679 path subject nested-reference unchanged"},{"id":"IETF RFC 4833","type":"specification","body":"IETF","designation":"RFC 4833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4833.txt","https://www.rfc-editor.org/rfc/rfc4833.pdf"],"folder":"IETF/RFC-4833","files":{"txt":{"path":"standards/IETF/RFC-4833/RFC-4833.txt","sha256":"f7e9c6e8f9274073eab9f5aaae20a22d20111cdd0b1cb479ecb52ef3a2f1cc80"}},"tags":["nested-reference","unchanged"],"summary":"Two common ways to communicate timezone information are POSIX 1003.1\n timezone strings and timezone database names. This memo specifies\n DHCP options for each of those methods. The DHCPv4 time offset\n option is deprecated.\n\nLear & Eggert Standards Track [Page 1]\n\f\nRFC 4833 Timezone Options for DHCP April 2007\n\n1. Introduction\n\n This memo specifies a means to provide hosts with more accurate\n timezone information than was previously available. To do this we\n make use of two commonly used methods to configure timezones:\n\n o POSIX TZ strings\n\n o Reference to the name of the time zone entry in the TZ Database\n\n POSIX [1] provides a standard for how to express timezone information\n in a character string. Use of such a string can provide accuracy for\n at least one transition into and out of daylight saving time (DST),\n and possibly for more transitions if the transitions are regular\n enough (e","scope_keywords":["4833","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 4833 Two common ways to communicate timezone information are POSIX 1003.1\n timezone strings and timezone database names. This memo specifies\n DHCP options for each of those methods. The DHCPv4 time offset\n option is deprecated.\n\nLear & Eggert Standards Track [Page 1]\n\f\nRFC 4833 Timezone Options for DHCP April 2007\n\n1. Introduction\n\n This memo specifies a means to provide hosts with more accurate\n timezone information than was previously available. To do this we\n make use of two commonly used methods to configure timezones:\n\n o POSIX TZ strings\n\n o Reference to the name of the time zone entry in the TZ Database\n\n POSIX [1] provides a standard for how to express timezone information\n in a character string. Use of such a string can provide accuracy for\n at least one transition into and out of daylight saving time (DST),\n and possibly for more transitions if the transitions are regular\n enough (e 4833 key trust nested-reference unchanged"},{"id":"IETF RFC 4898","type":"specification","body":"IETF","designation":"RFC 4898","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4898.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4898.txt","https://www.rfc-editor.org/rfc/rfc4898.pdf"],"folder":"IETF/RFC-4898","files":{"txt":{"path":"standards/IETF/RFC-4898/RFC-4898.txt","sha256":"b17d50dc6be2c6fd1eb6817180a2187d1a379defa0b15ccc6e5d1588ae28d780"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extended performance statistics for TCP.\n They are designed to use TCP's ideal vantage point to diagnose\n performance problems in both the network and the application. If a\n network-based application is performing poorly, TCP can determine if\n the bottleneck is in the sender, the receiver, or the network itself.\n If the bottleneck is in the network, TCP can provide specific\n information about its nature.","scope_keywords":["4898","algorithm","algorithms","key","management","path","pid","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4898 This document describes extended performance statistics for TCP.\n They are designed to use TCP's ideal vantage point to diagnose\n performance problems in both the network and the application. If a\n network-based application is performing poorly, TCP can determine if\n the bottleneck is in the sender, the receiver, or the network itself.\n If the bottleneck is in the network, TCP can provide specific\n information about its nature. 4898 algorithm algorithms key management path pid trust tsp nested-reference unchanged"},{"id":"IETF RFC 4949","type":"specification","body":"IETF","designation":"RFC 4949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4949.txt","https://www.rfc-editor.org/rfc/rfc4949.pdf"],"folder":"IETF/RFC-4949","files":{"txt":{"path":"standards/IETF/RFC-4949/RFC-4949.txt","sha256":"32d1e3837ae5a7d2e99a63f43c6fea3dd350ffc6ac55b3aaadad250546ad7f87"}},"tags":["nested-reference","unchanged"],"summary":"This Glossary provides definitions, abbreviations, and explanations\n of terminology for information system security. The 334 pages of\n entries offer recommendations to improve the comprehensibility of\n written material that is generated in the Internet Standards Process\n (RFC 2026). The recommendations follow the principles that such\n writing should (a) use the same term or definition whenever the same\n concept is mentioned; (b) use terms in their plainest, dictionary\n sense; (c) use terms that are already well-established in open\n publications; and (d) avoid terms that either favor a particular\n vendor or favor a particular technology or mechanism over other,\n competing techniques that already exist or could be developed.","scope_keywords":["4949","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 4949 This Glossary provides definitions, abbreviations, and explanations\n of terminology for information system security. The 334 pages of\n entries offer recommendations to improve the comprehensibility of\n written material that is generated in the Internet Standards Process\n (RFC 2026). The recommendations follow the principles that such\n writing should (a) use the same term or definition whenever the same\n concept is mentioned; (b) use terms in their plainest, dictionary\n sense; (c) use terms that are already well-established in open\n publications; and (d) avoid terms that either favor a particular\n vendor or favor a particular technology or mechanism over other,\n competing techniques that already exist or could be developed. 4949 pid trust nested-reference unchanged"},{"id":"IETF RFC 5444","type":"specification","body":"IETF","designation":"RFC 5444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5444.txt","https://www.rfc-editor.org/rfc/rfc5444.pdf"],"folder":"IETF/RFC-5444","files":{"txt":{"path":"standards/IETF/RFC-5444/RFC-5444.txt","sha256":"07097bf766b0197c4b8f110bba3cd90d3d8319a8869f0f1a9ccafc15b73639cd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a packet format capable of carrying multiple\n messages that may be used by mobile ad hoc network routing protocols.\n\nClausen, et al. Standards Track [Page 1]\n\f\nRFC 5444 MANET Packet Format February 2009","scope_keywords":["5444","attribute","attributes","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5497","folder":"IETF/RFC-5497","source":"IETF/RFC-5497/RFC-5497.txt","version":null},{"body":"IETF","designation":"RFC 5498","folder":"IETF/RFC-5498","source":"IETF/RFC-5498/RFC-5498.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null}],"search_text":"IETF RFC 5444 This document specifies a packet format capable of carrying multiple\n messages that may be used by mobile ad hoc network routing protocols.\n\nClausen, et al. Standards Track [Page 1]\n\f\nRFC 5444 MANET Packet Format February 2009 5444 attribute attributes authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5661","type":"specification","body":"IETF","designation":"RFC 5661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5661.txt","https://www.rfc-editor.org/rfc/rfc5661.pdf"],"folder":"IETF/RFC-5661","files":{"txt":{"path":"standards/IETF/RFC-5661/RFC-5661.txt","sha256":"41f2e123acf007e1eb53b5b47b97da72d62936f6acba7b2bfd3e38fae77167c4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Network File System (NFS) version 4 minor\n version 1, including features retained from the base protocol (NFS\n version 4 minor version 0, which is specified in RFC 3530) and\n protocol extensions made subsequently. Major extensions introduced\n in NFS version 4 minor version 1 include Sessions, Directory\n Delegations, and parallel NFS (pNFS). NFS version 4 minor version 1\n has no dependencies on NFS version 4 minor version 0, and it is\n considered a separate protocol. Thus, this document neither updates\n nor obsoletes RFC 3530. NFS minor version 1 is deemed superior to\n NFS minor version 0 with no loss of functionality, and its use is\n preferred over version 0. Both NFS minor versions 0 and 1 can be\n used simultaneously on the same network, between the same client and\n server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document i","scope_keywords":["5661","attribute","attributes","http","license","management","policy","presentation","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5663","folder":"IETF/RFC-5663","source":"IETF/RFC-5663/RFC-5663.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 5661 This document describes the Network File System (NFS) version 4 minor\n version 1, including features retained from the base protocol (NFS\n version 4 minor version 0, which is specified in RFC 3530) and\n protocol extensions made subsequently. Major extensions introduced\n in NFS version 4 minor version 1 include Sessions, Directory\n Delegations, and parallel NFS (pNFS). NFS version 4 minor version 1\n has no dependencies on NFS version 4 minor version 0, and it is\n considered a separate protocol. Thus, this document neither updates\n nor obsoletes RFC 3530. NFS minor version 1 is deemed superior to\n NFS minor version 0 with no loss of functionality, and its use is\n preferred over version 0. Both NFS minor versions 0 and 1 can be\n used simultaneously on the same network, between the same client and\n server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document i 5661 attribute attributes http license management policy presentation revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6557","type":"specification","body":"IETF","designation":"RFC 6557","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6557.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6557.txt","https://www.rfc-editor.org/rfc/rfc6557.pdf"],"folder":"IETF/RFC-6557","files":{"txt":{"path":"standards/IETF/RFC-6557/RFC-6557.txt","sha256":"005eaa4040638548c050da28747d30fb21dffefe2c972c070772f3c0b2961f6c"}},"tags":["nested-reference","unchanged"],"summary":"Time zone information serves as a basic protocol element in\n protocols, such as the calendaring suite and DHCP. The Time Zone\n (TZ) Database specifies the indices used in various protocols, as\n well as their semantic meanings, for all localities throughout the\n world. This database has been meticulously maintained and\n distributed free of charge by a group of volunteers, coordinated by a\n single volunteer who is now planning to retire. This memo specifies\n procedures involved with maintenance of the TZ database and\n associated code, including how to submit proposed updates, how\n decisions for inclusion of those updates are made, and the selection\n of a designated expert by and for the time zone community. The\n intent of this memo is, to the extent possible, to document existing\n practice and provide a means to ease succession of the database\n maintainers.\n\nStatus of This Memo\n\n This memo","scope_keywords":["6557","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null}],"search_text":"IETF RFC 6557 Time zone information serves as a basic protocol element in\n protocols, such as the calendaring suite and DHCP. The Time Zone\n (TZ) Database specifies the indices used in various protocols, as\n well as their semantic meanings, for all localities throughout the\n world. This database has been meticulously maintained and\n distributed free of charge by a group of volunteers, coordinated by a\n single volunteer who is now planning to retire. This memo specifies\n procedures involved with maintenance of the TZ database and\n associated code, including how to submit proposed updates, how\n decisions for inclusion of those updates are made, and the selection\n of a designated expert by and for the time zone community. The\n intent of this memo is, to the extent possible, to document existing\n practice and provide a means to ease succession of the database\n maintainers.\n\nStatus of This Memo\n\n This memo 6557 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6943","type":"specification","body":"IETF","designation":"RFC 6943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6943.txt","https://www.rfc-editor.org/rfc/rfc6943.pdf"],"folder":"IETF/RFC-6943","files":{"txt":{"path":"standards/IETF/RFC-6943/RFC-6943.txt","sha256":"11790ac7861191dcbd3dca4ae27e5d12acf4839d61d6053e713e0dd573a71cb6"}},"tags":["nested-reference","unchanged"],"summary":"Identifiers such as hostnames, URIs, IP addresses, and email\n addresses are often used in security contexts to identify security\n principals and resources. In such contexts, an identifier presented\n via some protocol is often compared using some policy to make\n security decisions such as whether the security principal may access\n the resource, what level of authentication or encryption is required,\n etc. If the parties involved in a security decision use different\n algorithms to compare identifiers, then failure scenarios ranging\n from denial of service to elevation of privilege can result. This\n document provides a discussion of these issues that designers should\n consider when defining identifiers and protocols, and when\n constructing architectures that use multiple protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for in","scope_keywords":["6943","algorithm","algorithms","authentication","encryption","holder","http","license","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null}],"search_text":"IETF RFC 6943 Identifiers such as hostnames, URIs, IP addresses, and email\n addresses are often used in security contexts to identify security\n principals and resources. In such contexts, an identifier presented\n via some protocol is often compared using some policy to make\n security decisions such as whether the security principal may access\n the resource, what level of authentication or encryption is required,\n etc. If the parties involved in a security decision use different\n algorithms to compare identifiers, then failure scenarios ranging\n from denial of service to elevation of privilege can result. This\n document provides a discussion of these issues that designers should\n consider when defining identifiers and protocols, and when\n constructing architectures that use multiple protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for in 6943 algorithm algorithms authentication encryption holder http license path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7049","type":"specification","body":"IETF","designation":"RFC 7049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7049.txt","https://www.rfc-editor.org/rfc/rfc7049.pdf"],"folder":"IETF/RFC-7049","files":{"txt":{"path":"standards/IETF/RFC-7049/RFC-7049.txt","sha256":"2b65264a9606b2182f536bffad10f12176837747e23a12f89e795d886d6ac33b"}},"tags":["nested-reference","unchanged"],"summary":"The Concise Binary Object Representation (CBOR) is a data format\n whose design goals include the possibility of extremely small code\n size, fairly small message size, and extensibility without the need\n for version negotiation. These design goals make it different from\n earlier binary serializations such as ASN.1 and MessagePack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7049.\n\nCop","scope_keywords":["7049","http","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8943","folder":"IETF/RFC-8943","source":"IETF/RFC-8943/RFC-8943.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 7049 The Concise Binary Object Representation (CBOR) is a data format\n whose design goals include the possibility of extremely small code\n size, fairly small message size, and extensibility without the need\n for version negotiation. These design goals make it different from\n earlier binary serializations such as ASN.1 and MessagePack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7049.\n\nCop 7049 http key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7252","type":"specification","body":"IETF","designation":"RFC 7252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7252.txt","https://www.rfc-editor.org/rfc/rfc7252.pdf"],"folder":"IETF/RFC-7252","files":{"txt":{"path":"standards/IETF/RFC-7252/RFC-7252.txt","sha256":"abfe8cce3370b5b32487421b35725eb6eaf962ea454cad008b5a5cd052e27c5f"}},"tags":["nested-reference","unchanged"],"summary":"The Constrained Application Protocol (CoAP) is a specialized web\n transfer protocol for use with constrained nodes and constrained\n (e.g., low-power, lossy) networks. The nodes often have 8-bit\n microcontrollers with small amounts of ROM and RAM, while constrained\n networks such as IPv6 over Low-Power Wireless Personal Area Networks\n (6LoWPANs) often have high packet error rates and a typical\n throughput of 10s of kbit/s. The protocol is designed for machine-\n to-machine (M2M) applications such as smart energy and building\n automation.\n\n CoAP provides a request/response interaction model between\n application endpoints, supports built-in discovery of services and\n resources, and includes key concepts of the Web such as URIs and\n Internet media types. CoAP is designed to easily interface with HTTP\n for integration with the Web while meeting specialized requirements\n such as multicast suppo","scope_keywords":["7252","http","key","license","path","presentation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8307","folder":"IETF/RFC-8307","source":"IETF/RFC-8307/RFC-8307.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 7252 The Constrained Application Protocol (CoAP) is a specialized web\n transfer protocol for use with constrained nodes and constrained\n (e.g., low-power, lossy) networks. The nodes often have 8-bit\n microcontrollers with small amounts of ROM and RAM, while constrained\n networks such as IPv6 over Low-Power Wireless Personal Area Networks\n (6LoWPANs) often have high packet error rates and a typical\n throughput of 10s of kbit/s. The protocol is designed for machine-\n to-machine (M2M) applications such as smart energy and building\n automation.\n\n CoAP provides a request/response interaction model between\n application endpoints, supports built-in discovery of services and\n resources, and includes key concepts of the Web such as URIs and\n Internet media types. CoAP is designed to easily interface with HTTP\n for integration with the Web while meeting specialized requirements\n such as multicast suppo 7252 http key license path presentation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7519","type":"specification","body":"IETF","designation":"RFC 7519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7519.txt","https://www.rfc-editor.org/rfc/rfc7519.pdf"],"folder":"IETF/RFC-7519","files":{"txt":{"path":"standards/IETF/RFC-7519/RFC-7519.txt","sha256":"fecd930e9ccf2276b95c0017c6c4ff5d09352e4bc3c7629946447894e0f97248"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"JSON Web Token (JWT) is a compact, URL-safe means of representing\n claims to be transferred between two parties. The claims in a JWT\n are encoded as a JSON object that is used as the payload of a JSON\n Web Signature (JWS) structure or as the plaintext of a JSON Web\n Encryption (JWE) structure, enabling the claims to be digitally\n signed or integrity protected with a Message Authentication Code\n (MAC) and/or encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how ","scope_keywords":["7519","authentication","authorization","encryption","http","issuer","key","license","presentation","registered","signature","subject","trust","wallet"],"parent_legal_regulations":[{"celex":"32025R0848","eli":"https://data.europa.eu/eli/reg_impl/2025/848/oj/eng","id":"2025-848","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-848/2025-848.md","title":"Registration of wallet-relying parties"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS03","folder":"ARF/TS03-V1.5.2","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md","version":"1.5.2"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 7519 JSON Web Token (JWT) is a compact, URL-safe means of representing\n claims to be transferred between two parties. The claims in a JWT\n are encoded as a JSON object that is used as the payload of a JSON\n Web Signature (JWS) structure or as the plaintext of a JSON Web\n Encryption (JWE) structure, enabling the claims to be digitally\n signed or integrity protected with a Message Authentication Code\n (MAC) and/or encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how  7519 authentication authorization encryption http issuer key license presentation registered signature subject trust wallet cited-by-eu-law implementing-regulation nested-reference unchanged 2025-848 Registration of wallet-relying parties 32025R0848 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 7530","type":"specification","body":"IETF","designation":"RFC 7530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7530.txt","https://www.rfc-editor.org/rfc/rfc7530.pdf"],"folder":"IETF/RFC-7530","files":{"txt":{"path":"standards/IETF/RFC-7530/RFC-7530.txt","sha256":"7ed40eee2f8019ccbfa54ff092290775abd8842a5106b9a4b84148067366e54e"}},"tags":["nested-reference","unchanged"],"summary":"The Network File System (NFS) version 4 protocol is a distributed\n file system protocol that builds on the heritage of NFS protocol\n version 2 (RFC 1094) and version 3 (RFC 1813). Unlike earlier\n versions, the NFS version 4 protocol supports traditional file access\n while integrating support for file locking and the MOUNT protocol.\n In addition, support for strong security (and its negotiation),\n COMPOUND operations, client caching, and internationalization has\n been added. Of course, attention has been applied to making NFS\n version 4 operate well in an Internet environment.\n\n This document, together with the companion External Data\n Representation (XDR) description document, RFC 7531, obsoletes RFC\n 3530 as the definition of the NFS version 4 protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Forc","scope_keywords":["7530","attribute","attributes","authentication","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null}],"search_text":"IETF RFC 7530 The Network File System (NFS) version 4 protocol is a distributed\n file system protocol that builds on the heritage of NFS protocol\n version 2 (RFC 1094) and version 3 (RFC 1813). Unlike earlier\n versions, the NFS version 4 protocol supports traditional file access\n while integrating support for file locking and the MOUNT protocol.\n In addition, support for strong security (and its negotiation),\n COMPOUND operations, client caching, and internationalization has\n been added. Of course, attention has been applied to making NFS\n version 4 operate well in an Internet environment.\n\n This document, together with the companion External Data\n Representation (XDR) description document, RFC 7531, obsoletes RFC\n 3530 as the definition of the NFS version 4 protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Forc 7530 attribute attributes authentication http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8089","type":"specification","body":"IETF","designation":"RFC 8089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8089.txt","https://www.rfc-editor.org/rfc/rfc8089.pdf"],"folder":"IETF/RFC-8089","files":{"txt":{"path":"standards/IETF/RFC-8089/RFC-8089.txt","sha256":"b5b3b7892f56ed371b5c53c625a4cde78cabf15276e4d7d9a22da184faf2fe26"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a more complete specification of the \"file\"\n Uniform Resource Identifier (URI) scheme and replaces the very brief\n definition in Section 3.10 of RFC 1738.\n\n It defines a common syntax that is intended to interoperate across\n the broad spectrum of existing usages. At the same time, it notes\n some other current practices around the use of file URIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n htt","scope_keywords":["8089","http","key","license","path","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null}],"search_text":"IETF RFC 8089 This document provides a more complete specification of the \"file\"\n Uniform Resource Identifier (URI) scheme and replaces the very brief\n definition in Section 3.10 of RFC 1738.\n\n It defines a common syntax that is intended to interoperate across\n the broad spectrum of existing usages. At the same time, it notes\n some other current practices around the use of file URIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n htt 8089 http key license path qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 8943","type":"specification","body":"IETF","designation":"RFC 8943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8943.txt","https://www.rfc-editor.org/rfc/rfc8943.pdf"],"folder":"IETF/RFC-8943","files":{"pdf":{"path":"standards/IETF/RFC-8943/RFC-8943.pdf","sha256":"663ef178831ffb99d4569af7d4da9b77302f756e93bac828b3d0ff2a9c0b9355"},"txt":{"path":"standards/IETF/RFC-8943/RFC-8943.txt","sha256":"bb3a62834af19f6d5d15e5a7faca922e2eab58541050f5bddf9cf477af3b7850"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"The Concise Binary Object Representation (CBOR), as specified in RFC\n 7049, is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n In CBOR, one point of extensibility is the definition of CBOR tags.\n RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as\n per RFC 3339) and tag 1 (POSIX \"seconds since the epoch\"). Since\n then, additional requirements have become known. This specification\n defines a CBOR tag for a date text string (as per RFC 3339) for\n applications needing a textual date representation within the\n Gregorian calendar without a time. It also defines a CBOR tag for\n days since the date 1970-01-01 in the Gregorian calendar for\n applications needing a numeric date representation without a time.\n This specification is the reference document ","scope_keywords":["8943","algorithm","algorithms","http","https","license","presentation","subject","trust"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null}],"search_text":"IETF RFC 8943 The Concise Binary Object Representation (CBOR), as specified in RFC\n 7049, is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n In CBOR, one point of extensibility is the definition of CBOR tags.\n RFC 7049 defines two tags for time: CBOR tag 0 (date/time string as\n per RFC 3339) and tag 1 (POSIX \"seconds since the epoch\"). Since\n then, additional requirements have become known. This specification\n defines a CBOR tag for a date text string (as per RFC 3339) for\n applications needing a textual date representation within the\n Gregorian calendar without a time. It also defines a CBOR tag for\n days since the date 1970-01-01 in the Gregorian calendar for\n applications needing a numeric date representation without a time.\n This specification is the reference document  8943 algorithm algorithms http https license presentation subject trust cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 8949","type":"specification","body":"IETF","designation":"RFC 8949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8949.txt","https://www.rfc-editor.org/rfc/rfc8949.pdf"],"folder":"IETF/RFC-8949","files":{"pdf":{"path":"standards/IETF/RFC-8949/RFC-8949.pdf","sha256":"e0973600e135646becc8e337a74da9d5e16587f26a4592a5ca4bb47df413e539"},"txt":{"path":"standards/IETF/RFC-8949/RFC-8949.txt","sha256":"f1164a5b31a39350ad46abe29b83575eb933ca6c45366989c118b6b1058a214a"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"The Concise Binary Object Representation (CBOR) is a data format\n whose design goals include the possibility of extremely small code\n size, fairly small message size, and extensibility without the need\n for version negotiation. These design goals make it different from\n earlier binary serializations such as ASN.1 and MessagePack.\n\n This document obsoletes RFC 7049, providing editorial improvements,\n new details, and errata fixes while keeping full compatibility with\n the interchange format of RFC 7049. It does not create a new version\n of the format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n I","scope_keywords":["8949","http","https","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 8949 The Concise Binary Object Representation (CBOR) is a data format\n whose design goals include the possibility of extremely small code\n size, fairly small message size, and extensibility without the need\n for version negotiation. These design goals make it different from\n earlier binary serializations such as ASN.1 and MessagePack.\n\n This document obsoletes RFC 7049, providing editorial improvements,\n new details, and errata fixes while keeping full compatibility with\n the interchange format of RFC 7049. It does not create a new version\n of the format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n I 8949 http https key keys license presentation subject trust cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 8981","type":"specification","body":"IETF","designation":"RFC 8981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8981.txt","https://www.rfc-editor.org/rfc/rfc8981.pdf"],"folder":"IETF/RFC-8981","files":{"pdf":{"path":"standards/IETF/RFC-8981/RFC-8981.pdf","sha256":"0483e65d2f2d67e37771311dba19a2a1cbab56efed299278abf42b130a4b6cb0"},"txt":{"path":"standards/IETF/RFC-8981/RFC-8981.txt","sha256":"18f61209d7abc7a9aa8f758ca823de10c1c3a24b272c4262064b84dd703c9a01"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to IPv6 Stateless Address\n Autoconfiguration that causes hosts to generate temporary addresses\n with randomized interface identifiers for each prefix advertised with\n autoconfiguration enabled. Changing addresses over time limits the\n window of time during which eavesdroppers and other information\n collectors may trivially perform address-based network-activity\n correlation when the same address is employed for multiple\n transactions by the same host. Additionally, it reduces the window\n of exposure of a host as being accessible via an address that becomes\n revealed as a result of active communication. This document\n obsoletes RFC 4941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ","scope_keywords":["8981","http","https","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 8981 This document describes an extension to IPv6 Stateless Address\n Autoconfiguration that causes hosts to generate temporary addresses\n with randomized interface identifiers for each prefix advertised with\n autoconfiguration enabled. Changing addresses over time limits the\n window of time during which eavesdroppers and other information\n collectors may trivially perform address-based network-activity\n correlation when the same address is employed for multiple\n transactions by the same host. Additionally, it reduces the window\n of exposure of a host as being accessible via an address that becomes\n revealed as a result of active communication. This document\n obsoletes RFC 4941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ 8981 http https key license path subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1003.1-2001","type":"specification","body":"IEEE","designation":"IEEE 1003.1-2001","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.1-2001.html","download_urls":["https://standards.ieee.org/standard/1003.1-2001.html"],"folder":"IEEE/IEEE-1003.1-2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"IEEE IEEE 1003.1-2001 nested-reference unavailable"},{"id":"IETF RFC 7970","type":"specification","body":"IETF","designation":"RFC 7970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7970.txt","https://www.rfc-editor.org/rfc/rfc7970.pdf"],"folder":"IETF/RFC-7970","files":{"txt":{"path":"standards/IETF/RFC-7970/RFC-7970.txt","sha256":"63e23655024199260e1deba59c9d4e2ae154f3e95bfc34aa2fae95e6826acd63"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) defines a\n data representation for security incident reports and indicators\n commonly exchanged by operational security teams for mitigation and\n watch and warning. This document describes an updated information\n model for the IODEF and provides an associated data model specified\n with the XML schema. This new information and data model obsoletes\n RFCs 5070 and 6685.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and ","scope_keywords":["7970","attribute","attributes","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 7970 The Incident Object Description Exchange Format (IODEF) defines a\n data representation for security incident reports and indicators\n commonly exchanged by operational security teams for mitigation and\n watch and warning. This document describes an updated information\n model for the IODEF and provides an associated data model specified\n with the XML schema. This new information and data model obsoletes\n RFCs 5070 and 6685.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and  7970 attribute attributes http license presentation subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1003.1-2004","type":"specification","body":"IEEE","designation":"IEEE 1003.1-2004","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.1-2004.html","download_urls":["https://standards.ieee.org/standard/1003.1-2004.html"],"folder":"IEEE/IEEE-1003.1-2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null}],"search_text":"IEEE IEEE 1003.1-2004 nested-reference unavailable"},{"id":"IEEE IEEE 1003.1-2008","type":"specification","body":"IEEE","designation":"IEEE 1003.1-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.1-2008.html","download_urls":["https://standards.ieee.org/standard/1003.1-2008.html"],"folder":"IEEE/IEEE-1003.1-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IEEE IEEE 1003.1-2008 nested-reference unavailable"},{"id":"IETF RFC 6622","type":"specification","body":"IETF","designation":"RFC 6622","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6622.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6622.txt","https://www.rfc-editor.org/rfc/rfc6622.pdf"],"folder":"IETF/RFC-6622","files":{"txt":{"path":"standards/IETF/RFC-6622/RFC-6622.txt","sha256":"21b79b2640d27eef6ffa899f8ded1742afdee6c295c8556252ad9779c9bca666"}},"tags":["nested-reference","unchanged"],"summary":"This document describes general and flexible TLVs for representing\n cryptographic Integrity Check Values (ICVs) (i.e., digital signatures\n or Message Authentication Codes (MACs)) as well as timestamps, using\n the generalized Mobile Ad Hoc Network (MANET) packet/message format\n defined in RFC 5444. It defines two Packet TLVs, two Message TLVs,\n and two Address Block TLVs for affixing ICVs and timestamps to a\n packet, a message, and an address, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status ","scope_keywords":["6622","authentication","hash","http","key","license","signature","signatures","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null}],"search_text":"IETF RFC 6622 This document describes general and flexible TLVs for representing\n cryptographic Integrity Check Values (ICVs) (i.e., digital signatures\n or Message Authentication Codes (MACs)) as well as timestamps, using\n the generalized Mobile Ad Hoc Network (MANET) packet/message format\n defined in RFC 5444. It defines two Packet TLVs, two Message TLVs,\n and two Address Block TLVs for affixing ICVs and timestamps to a\n packet, a message, and an address, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status  6622 authentication hash http key license signature signatures subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7011","type":"specification","body":"IETF","designation":"RFC 7011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7011.txt","https://www.rfc-editor.org/rfc/rfc7011.pdf"],"folder":"IETF/RFC-7011","files":{"txt":{"path":"standards/IETF/RFC-7011/RFC-7011.txt","sha256":"59b7ddb1c0350ae711ba41d771d93f4d440ee04755403446f580bb777b928f73"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IP Flow Information Export (IPFIX)\n protocol, which serves as a means for transmitting Traffic Flow\n information over the network. In order to transmit Traffic Flow\n information from an Exporting Process to a Collecting Process, a\n common representation of flow data and a standard means of\n communicating them are required. This document describes how the\n IPFIX Data and Template Records are carried over a number of\n transport protocols from an IPFIX Exporting Process to an IPFIX\n Collecting Process. This document obsoletes RFC 5101.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informa","scope_keywords":["7011","http","key","keys","license","management","presentation","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IETF RFC 7011 This document specifies the IP Flow Information Export (IPFIX)\n protocol, which serves as a means for transmitting Traffic Flow\n information over the network. In order to transmit Traffic Flow\n information from an Exporting Process to a Collecting Process, a\n common representation of flow data and a standard means of\n communicating them are required. This document describes how the\n IPFIX Data and Template Records are carried over a number of\n transport protocols from an IPFIX Exporting Process to an IPFIX\n Collecting Process. This document obsoletes RFC 5101.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informa 7011 http key keys license management presentation subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7182","type":"specification","body":"IETF","designation":"RFC 7182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7182.txt","https://www.rfc-editor.org/rfc/rfc7182.pdf"],"folder":"IETF/RFC-7182","files":{"txt":{"path":"standards/IETF/RFC-7182/RFC-7182.txt","sha256":"94cb491c5f0388658f14ee8c853fab8aba9304e1ae520e8c154928d33409ccc3"}},"tags":["nested-reference","unchanged"],"summary":"This document revises, extends, and replaces RFC 6622. It describes\n general and flexible TLVs for representing cryptographic Integrity\n Check Values (ICVs) and timestamps, using the generalized Mobile Ad\n Hoc Network (MANET) packet/message format defined in RFC 5444. It\n defines two Packet TLVs, two Message TLVs, and two Address Block TLVs\n for affixing ICVs and timestamps to a packet, a message, and one or\n more addresses, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, ","scope_keywords":["7182","hash","http","license","presentation","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null}],"search_text":"IETF RFC 7182 This document revises, extends, and replaces RFC 6622. It describes\n general and flexible TLVs for representing cryptographic Integrity\n Check Values (ICVs) and timestamps, using the generalized Mobile Ad\n Hoc Network (MANET) packet/message format defined in RFC 5444. It\n defines two Packet TLVs, two Message TLVs, and two Address Block TLVs\n for affixing ICVs and timestamps to a packet, a message, and one or\n more addresses, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document,  7182 hash http license presentation subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 9162","type":"specification","body":"IETF","designation":"RFC 9162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9162.txt","https://www.rfc-editor.org/rfc/rfc9162.pdf"],"folder":"IETF/RFC-9162","files":{"pdf":{"path":"standards/IETF/RFC-9162/RFC-9162.pdf","sha256":"f0fafb9ef6f0555fc9ea5a65fb3552dea5957999aeb04162b2e8d0a748b1a89d"},"txt":{"path":"standards/IETF/RFC-9162/RFC-9162.txt","sha256":"a0e432ce7580c99fcc8faf0cf3f6191f9ce6b4864f949158e020d4ecb295081f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2.0 of the Certificate Transparency\n (CT) protocol for publicly logging the existence of Transport Layer\n Security (TLS) server certificates as they are issued or observed, in\n a manner that allows anyone to audit certification authority (CA)\n activity and notice the issuance of suspect certificates as well as\n to audit the certificate logs themselves. The intent is that\n eventually clients would refuse to honor certificates that do not\n appear in a log, effectively forcing CAs to add all issued\n certificates to the logs.\n\n This document obsoletes RFC 6962. It also specifies a new TLS\n extension that is used to send various CT log artifacts.\n\n Logs are network services that implement the protocol operations for\n submissions and queries that are defined in this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; ","scope_keywords":["9162","algorithm","algorithms","audit","authentication","certificate","certificates","hash","holder","http","https","license","ocsp","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 411-8","folder":"ETSI/TS-119-411-8-V1.1.1","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 9162 This document describes version 2.0 of the Certificate Transparency\n (CT) protocol for publicly logging the existence of Transport Layer\n Security (TLS) server certificates as they are issued or observed, in\n a manner that allows anyone to audit certification authority (CA)\n activity and notice the issuance of suspect certificates as well as\n to audit the certificate logs themselves. The intent is that\n eventually clients would refuse to honor certificates that do not\n appear in a log, effectively forcing CAs to add all issued\n certificates to the logs.\n\n This document obsoletes RFC 6962. It also specifies a new TLS\n extension that is used to send various CT log artifacts.\n\n Logs are network services that implement the protocol operations for\n submissions and queries that are defined in this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification;  9162 algorithm algorithms audit authentication certificate certificates hash holder http https license ocsp signature signatures subject nested-reference unchanged"},{"id":"IEEE IEEE 1003.1.","type":"specification","body":"IEEE","designation":"IEEE 1003.1.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.1..html","download_urls":["https://standards.ieee.org/standard/1003.1..html"],"folder":"IEEE/IEEE-1003.1.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null}],"search_text":"IEEE IEEE 1003.1. nested-reference unavailable"},{"id":"IEEE IEEE 1003.2-1992","type":"specification","body":"IEEE","designation":"IEEE 1003.2-1992","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1003.2-1992.html","download_urls":["https://standards.ieee.org/standard/1003.2-1992.html"],"folder":"IEEE/IEEE-1003.2-1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2168","folder":"IETF/RFC-2168","source":"IETF/RFC-2168/RFC-2168.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null}],"search_text":"IEEE IEEE 1003.2-1992 nested-reference unavailable"},{"id":"IETF RFC 2168","type":"specification","body":"IETF","designation":"RFC 2168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2168.txt","https://www.rfc-editor.org/rfc/rfc2168.pdf"],"folder":"IETF/RFC-2168","files":{"txt":{"path":"standards/IETF/RFC-2168/RFC-2168.txt","sha256":"8cb4b01fd21aab2ce0d174fd1283c3505709e17b113813199e8e5ee16bd78689"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Daniel\nRequest for Comments: 2168 Los Alamos National Laboratory\nCategory: Experimental M. Mealling\n Network Solutions, Inc.\n June 1997\n\n Resolution of Uniform Resource Identifiers\n using the Domain Name System\n\nStatus of this Memo\n===================\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract:\n=========\n\n Uniform Resource Locators (URLs) are the foundation of the World Wide\n Web, and are a vital Internet technology. However, they have proven\n to be brittle in practice. The basic problem is that URLs typically\n identify a particular path to a file on a particular host. There is\n no graceful way of changing the path or host once the URL has been\n assigned. Neither i","scope_keywords":["2168","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2169","folder":"IETF/RFC-2169","source":"IETF/RFC-2169/RFC-2169.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 2168 Network Working Group R. Daniel\nRequest for Comments: 2168 Los Alamos National Laboratory\nCategory: Experimental M. Mealling\n Network Solutions, Inc.\n June 1997\n\n Resolution of Uniform Resource Identifiers\n using the Domain Name System\n\nStatus of this Memo\n===================\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract:\n=========\n\n Uniform Resource Locators (URLs) are the foundation of the World Wide\n Web, and are a vital Internet technology. However, they have proven\n to be brittle in practice. The basic problem is that URLs typically\n identify a particular path to a file on a particular host. There is\n no graceful way of changing the path or host once the URL has been\n assigned. Neither i 2168 path nested-reference unchanged"},{"id":"IETF RFC 2915","type":"specification","body":"IETF","designation":"RFC 2915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2915.txt","https://www.rfc-editor.org/rfc/rfc2915.pdf"],"folder":"IETF/RFC-2915","files":{"txt":{"path":"standards/IETF/RFC-2915/RFC-2915.txt","sha256":"c2766b1b18a56a0517c6d8a9364a80cbd2b956fab1893045d69b8878d9f6b7d4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Domain Name System (DNS) resource record\n which specifies a regular expression based rewrite rule that, when\n applied to an existing string, will produce a new domain label or\n Uniform Resource Identifier (URI). Depending on the value of the\n flags field of the resource record, the resulting domain label or URI\n may be used in subsequent queries for the Naming Authority Pointer\n (NAPTR) resource records (to delegate the name lookup) or as the\n output of the entire process for which this system is used (a\n resolution server for URI resolution, a service URI for ENUM style\n e.164 number to URI mapping, etc).\n\n This allows the DNS to be used to lookup services for a wide variety\n of resource names (including URIs) which are not in domain name\n syntax. Reasons for doing this range from URN Resource Discovery\n Systems to moving out-of-date services to new domains.\n\n ","scope_keywords":["2915","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 2915 This document describes a Domain Name System (DNS) resource record\n which specifies a regular expression based rewrite rule that, when\n applied to an existing string, will produce a new domain label or\n Uniform Resource Identifier (URI). Depending on the value of the\n flags field of the resource record, the resulting domain label or URI\n may be used in subsequent queries for the Naming Authority Pointer\n (NAPTR) resource records (to delegate the name lookup) or as the\n output of the entire process for which this system is used (a\n resolution server for URI resolution, a service URI for ENUM style\n e.164 number to URI mapping, etc).\n\n This allows the DNS to be used to lookup services for a wide variety\n of resource names (including URIs) which are not in domain name\n syntax. Reasons for doing this range from URN Resource Discovery\n Systems to moving out-of-date services to new domains.\n\n  2915 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 3402","type":"specification","body":"IETF","designation":"RFC 3402","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3402.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3402.txt","https://www.rfc-editor.org/rfc/rfc3402.pdf"],"folder":"IETF/RFC-3402","files":{"txt":{"path":"standards/IETF/RFC-3402/RFC-3402.txt","sha256":"67e1c1d0fd6d95463ed062a2f7302cc7f5263b71ea1c9b6c18b2dd6c58b869e0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Dynamic Delegation Discovery System\n (DDDS) algorithm for applying dynamically retrieved string\n transformation rules to an application-unique string. Well-formed\n transformation rules will reflect the delegation of management of\n information associated with the string. This document is also part\n of a series that is completely specified in \"Dynamic Delegation\n Discovery System (DDDS) Part One: The Comprehensive DDDS\" (RFC 3401).\n It is very important to note that it is impossible to read and\n understand any document in this series without reading the others.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3402 DDDS - The Algorithm October 2002","scope_keywords":["3402","algorithm","identification","key","keys","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 3402 This document describes the Dynamic Delegation Discovery System\n (DDDS) algorithm for applying dynamically retrieved string\n transformation rules to an application-unique string. Well-formed\n transformation rules will reflect the delegation of management of\n information associated with the string. This document is also part\n of a series that is completely specified in \"Dynamic Delegation\n Discovery System (DDDS) Part One: The Comprehensive DDDS\" (RFC 3401).\n It is very important to note that it is impossible to read and\n understand any document in this series without reading the others.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3402 DDDS - The Algorithm October 2002 3402 algorithm identification key keys management path nested-reference unchanged"},{"id":"IETF RFC 3403","type":"specification","body":"IETF","designation":"RFC 3403","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3403.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3403.txt","https://www.rfc-editor.org/rfc/rfc3403.pdf"],"folder":"IETF/RFC-3403","files":{"txt":{"path":"standards/IETF/RFC-3403/RFC-3403.txt","sha256":"d7adf0996018de9675c1b4e89317a67e0767e75c3c8dbd64ed4d1b91992e322b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Dynamic Delegation Discovery System (DDDS)\n Database using the Domain Name System (DNS) as a distributed database\n of Rules. The Keys are domain-names and the Rules are encoded using\n the Naming Authority Pointer (NAPTR) Resource Record (RR).\n\n Since this document obsoletes RFC 2915, it is the official\n specification for the NAPTR DNS Resource Record. It is also part of\n a series that is completely specified in \"Dynamic Delegation\n Discovery System (DDDS) Part One: The Comprehensive DDDS\" (RFC 3401).\n It is very important to note that it is impossible to read and\n understand any document in this series without reading the others.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3403 DDDS DNS Database October 2002","scope_keywords":["3403","algorithm","key","keys","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3486","folder":"IETF/RFC-3486","source":"IETF/RFC-3486/RFC-3486.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 3403 This document describes a Dynamic Delegation Discovery System (DDDS)\n Database using the Domain Name System (DNS) as a distributed database\n of Rules. The Keys are domain-names and the Rules are encoded using\n the Naming Authority Pointer (NAPTR) Resource Record (RR).\n\n Since this document obsoletes RFC 2915, it is the official\n specification for the NAPTR DNS Resource Record. It is also part of\n a series that is completely specified in \"Dynamic Delegation\n Discovery System (DDDS) Part One: The Comprehensive DDDS\" (RFC 3401).\n It is very important to note that it is impossible to read and\n understand any document in this series without reading the others.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3403 DDDS DNS Database October 2002 3403 algorithm key keys path nested-reference unchanged"},{"id":"IEEE IEEE 105","type":"specification","body":"IEEE","designation":"IEEE 105","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/105.html","download_urls":["https://standards.ieee.org/standard/105.html"],"folder":"IEEE/IEEE-105","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IEEE IEEE 105 nested-reference unavailable"},{"id":"IETF RFC 9110","type":"specification","body":"IETF","designation":"RFC 9110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9110.txt","https://www.rfc-editor.org/rfc/rfc9110.pdf"],"folder":"IETF/RFC-9110","files":{"pdf":{"path":"standards/IETF/RFC-9110/RFC-9110.pdf","sha256":"60b30efa1048900833d1758440247fe8ac85a3134f2327388dcb24e07d814c89"},"txt":{"path":"standards/IETF/RFC-9110/RFC-9110.txt","sha256":"21c1cdce6ab0e5509b04d84a28000836c7a087cf786efe6f04877ebfff47232a"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document describes the overall architecture of HTTP,\n establishes common terminology, and defines aspects of the protocol\n that are shared by all versions. In this definition are core\n protocol elements, extensibility mechanisms, and the \"http\" and\n \"https\" Uniform Resource Identifier (URI) schemes.\n\n This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232,\n 7233, 7235, 7538, 7615, 7694, and portions of 7230.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furthe","scope_keywords":["9110","authentication","authorization","certificate","credential","credentials","http","https","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 9110 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document describes the overall architecture of HTTP,\n establishes common terminology, and defines aspects of the protocol\n that are shared by all versions. In this definition are core\n protocol elements, extensibility mechanisms, and the \"http\" and\n \"https\" Uniform Resource Identifier (URI) schemes.\n\n This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232,\n 7233, 7235, 7538, 7615, 7694, and portions of 7230.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furthe 9110 authentication authorization certificate credential credentials http https license presentation qualified subject trust cited-by-eu-law implementing-regulation nested-reference unchanged 2025-1929 Qualified electronic time stamps 32025R1929"},{"id":"IEEE IEEE 1149.7-2009","type":"specification","body":"IEEE","designation":"IEEE 1149.7-2009","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1149.7-2009.html","download_urls":["https://standards.ieee.org/standard/1149.7-2009.html"],"folder":"IEEE/IEEE-1149.7-2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IEEE IEEE 1149.7-2009 nested-reference unavailable"},{"id":"IETF RFC 9711","type":"specification","body":"IETF","designation":"RFC 9711","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9711.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9711.txt","https://www.rfc-editor.org/rfc/rfc9711.pdf"],"folder":"IETF/RFC-9711","files":{"pdf":{"path":"standards/IETF/RFC-9711/RFC-9711.pdf","sha256":"5220536e11ebff047b13b307fcc6f15075b557bc550013d209e2f99f6a714564"},"txt":{"path":"standards/IETF/RFC-9711/RFC-9711.txt","sha256":"20d43b5a03151e5023533e069835e5581ebcaf5a70779a216d3d0ca06f2fd2c7"}},"tags":["nested-reference","unchanged"],"summary":"An Entity Attestation Token (EAT) provides an attested claims set\n that describes the state and characteristics of an entity, a device\n such as a smartphone, an Internet of Things (IoT) device, network\n equipment, or such. This claims set is used by a relying party,\n server, or service to determine the type and degree of trust placed\n in the entity.\n\n An EAT is either a CBOR Web Token (CWT) or a JSON Web Token (JWT)\n with attestation-oriented claims.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of thi","scope_keywords":["9711","algorithm","algorithms","attestation","certificate","http","https","identification","key","keys","license","profile","profiles","registered","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9711 An Entity Attestation Token (EAT) provides an attested claims set\n that describes the state and characteristics of an entity, a device\n such as a smartphone, an Internet of Things (IoT) device, network\n equipment, or such. This claims set is used by a relying party,\n server, or service to determine the type and degree of trust placed\n in the entity.\n\n An EAT is either a CBOR Web Token (CWT) or a JSON Web Token (JWT)\n with attestation-oriented claims.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of thi 9711 algorithm algorithms attestation certificate http https identification key keys license profile profiles registered subject timestamp nested-reference unchanged"},{"id":"IEEE IEEE 1278.1","type":"specification","body":"IEEE","designation":"IEEE 1278.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1278.1.html","download_urls":["https://standards.ieee.org/standard/1278.1.html"],"folder":"IEEE/IEEE-1278.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1667","folder":"IETF/RFC-1667","source":"IETF/RFC-1667/RFC-1667.txt","version":null}],"search_text":"IEEE IEEE 1278.1 nested-reference unavailable"},{"id":"IETF RFC 1667","type":"specification","body":"IETF","designation":"RFC 1667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1667.txt","https://www.rfc-editor.org/rfc/rfc1667.pdf"],"folder":"IETF/RFC-1667","files":{"txt":{"path":"standards/IETF/RFC-1667/RFC-1667.txt","sha256":"2679c7e26e6060bd62d3c913e9efbacf41ff05d21e6697c7b082982ce115a602"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Symington\nRequest for Comments: 1667 MITRE Corporation\nCategory: Informational D. Wood\n MITRE Corporation\n M. Pullen\n George Mason University\n August 1994\n\n Modeling and Simulation Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The Defense Modeling and Simulation community is a major user of\n packet networks and as such has a stake in the definition of IPng.\n This white paper summarizes the Distributed Interactive Simula","scope_keywords":["1667","driving"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 2502","folder":"IETF/RFC-2502","source":"IETF/RFC-2502/RFC-2502.txt","version":null}],"search_text":"IETF RFC 1667 Network Working Group S. Symington\nRequest for Comments: 1667 MITRE Corporation\nCategory: Informational D. Wood\n MITRE Corporation\n M. Pullen\n George Mason University\n August 1994\n\n Modeling and Simulation Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The Defense Modeling and Simulation community is a major user of\n packet networks and as such has a stake in the definition of IPng.\n This white paper summarizes the Distributed Interactive Simula 1667 driving nested-reference unchanged"},{"id":"IEEE IEEE 1278.1-1995","type":"specification","body":"IEEE","designation":"IEEE 1278.1-1995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1278.1-1995.html","download_urls":["https://standards.ieee.org/standard/1278.1-1995.html"],"folder":"IEEE/IEEE-1278.1-1995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2502","folder":"IETF/RFC-2502","source":"IETF/RFC-2502/RFC-2502.txt","version":null}],"search_text":"IEEE IEEE 1278.1-1995 nested-reference unavailable"},{"id":"IETF RFC 2502","type":"specification","body":"IETF","designation":"RFC 2502","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2502.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2502.txt","https://www.rfc-editor.org/rfc/rfc2502.pdf"],"folder":"IETF/RFC-2502","files":{"txt":{"path":"standards/IETF/RFC-2502/RFC-2502.txt","sha256":"7879ef178d2516d1cc322b0b69d2f489b16eadd6d1d30e0b04d2ba6927f76ca4"}},"tags":["nested-reference","unchanged"],"summary":"The Large-Scale Multicast Applications (LSMA) working group was\n chartered to produce documents aimed at a consensus based development\n of the Internet protocols to support large scale multicast\n applications including real-time distributed simulation. This memo\n defines services that LSMA has found to be required, and aspects of\n the Internet protocols that LSMA has found to need further\n development in order to meet these requirements.\n\n1. The Large Multicast Environment\n\n The Large-Scale Multicast Applications working group (LSMA) was\n formed to create a consensus based requirement for Internet Protocols\n to support Distributed Interactive Simulation (DIS) [DIS94], its\n successor the High Level Architecture for simulation (HLA) [DMSO96],\n and related applications. The applications are characterized by the\n need to distribute a real-time applications over a shared wide area\n network in","scope_keywords":["2502","attribute","attributes","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null}],"search_text":"IETF RFC 2502 The Large-Scale Multicast Applications (LSMA) working group was\n chartered to produce documents aimed at a consensus based development\n of the Internet protocols to support large scale multicast\n applications including real-time distributed simulation. This memo\n defines services that LSMA has found to be required, and aspects of\n the Internet protocols that LSMA has found to need further\n development in order to meet these requirements.\n\n1. The Large Multicast Environment\n\n The Large-Scale Multicast Applications working group (LSMA) was\n formed to create a consensus based requirement for Internet Protocols\n to support Distributed Interactive Simulation (DIS) [DIS94], its\n successor the High Level Architecture for simulation (HLA) [DMSO96],\n and related applications. The applications are characterized by the\n need to distribute a real-time applications over a shared wide area\n network in 2502 attribute attributes pid nested-reference unchanged"},{"id":"IEEE IEEE 1278.2-1995","type":"specification","body":"IEEE","designation":"IEEE 1278.2-1995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1278.2-1995.html","download_urls":["https://standards.ieee.org/standard/1278.2-1995.html"],"folder":"IEEE/IEEE-1278.2-1995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2502","folder":"IETF/RFC-2502","source":"IETF/RFC-2502/RFC-2502.txt","version":null}],"search_text":"IEEE IEEE 1278.2-1995 nested-reference unavailable"},{"id":"IEEE IEEE 1284","type":"specification","body":"IEEE","designation":"IEEE 1284","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1284.html","download_urls":["https://standards.ieee.org/standard/1284.html"],"folder":"IEEE/IEEE-1284","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"IEEE IEEE 1284 nested-reference unavailable"},{"id":"IETF RFC 1759","type":"specification","body":"IETF","designation":"RFC 1759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1759.txt","https://www.rfc-editor.org/rfc/rfc1759.pdf"],"folder":"IETF/RFC-1759","files":{"txt":{"path":"standards/IETF/RFC-1759/RFC-1759.txt","sha256":"2c3a25769864b77a9930ef041e26d55065025ec1d8d599631b0927abe518cd15"}},"tags":["nested-reference","unchanged"],"summary":"model of the printer is needed to represent the sub-units from which\n the printer is composed. A printer can be described as consisting of\n 13 types of sub-units. It is important to note that the sub-units of\n a printer do not necessarily relate directly to any physically\n identifiable mechanism. Sub-units can also be a set of definable\n logical processes, such as interpreters for page description\n languages or command processors that set various operating modes of\n the printer.\n\nSmith, Wright, Hastings, Zilles & Gyllenskog [Page 6]\n\f\nRFC 1759 Printer MIB March 1995\n\n Figure 2 shows a block diagram of the printer and its basic 13 sub-\n units.\n\n Figure 2 - Printer Block Diagram\n\n Physical Connections\n |\n +-----------+\n | |\n +-------------+ |\n | Interface |-+\n | (RFC1213) |\n +-------------+\n |\n +-----------+\n | |\n +-------------+ | +-----------+\n | Channel |-+ | Operator |\n | | | Console |","scope_keywords":["1759","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"IETF RFC 1759 model of the printer is needed to represent the sub-units from which\n the printer is composed. A printer can be described as consisting of\n 13 types of sub-units. It is important to note that the sub-units of\n a printer do not necessarily relate directly to any physically\n identifiable mechanism. Sub-units can also be a set of definable\n logical processes, such as interpreters for page description\n languages or command processors that set various operating modes of\n the printer.\n\nSmith, Wright, Hastings, Zilles & Gyllenskog [Page 6]\n\f\nRFC 1759 Printer MIB March 1995\n\n Figure 2 shows a block diagram of the printer and its basic 13 sub-\n units.\n\n Figure 2 - Printer Block Diagram\n\n Physical Connections\n |\n +-----------+\n | |\n +-------------+ |\n | Interface |-+\n | (RFC1213) |\n +-------------+\n |\n +-----------+\n | |\n +-------------+ | +-----------+\n | Channel |-+ | Operator |\n | | | Console | 1759 management path subject nested-reference unchanged"},{"id":"IETF RFC 3805","type":"specification","body":"IETF","designation":"RFC 3805","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3805.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3805.txt","https://www.rfc-editor.org/rfc/rfc3805.pdf"],"folder":"IETF/RFC-3805","files":{"txt":{"path":"standards/IETF/RFC-3805/RFC-3805.txt","sha256":"65d5e95ea411563e94fcbb7f2514ca837cffb8d6f8e9d272d0df9caba73e332c"}},"tags":["nested-reference","unchanged"],"summary":"This document provides definitions of models and manageable objects\n for printing environments. The objects included in this MIB apply to\n physical, as well as logical entities within a printing device. This\n document obsoletes RFC 1759.\n\nBergman, et al. Standards Track [Page 1]\n\f\nRFC 3805 Printer MIB v2 June 2004","scope_keywords":["3805","delivery","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 3805 This document provides definitions of models and manageable objects\n for printing environments. The objects included in this MIB apply to\n physical, as well as logical entities within a printing device. This\n document obsoletes RFC 1759.\n\nBergman, et al. Standards Track [Page 1]\n\f\nRFC 3805 Printer MIB v2 June 2004 3805 delivery management path nested-reference unchanged"},{"id":"IEEE IEEE 1284.1","type":"specification","body":"IEEE","designation":"IEEE 1284.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1284.1.html","download_urls":["https://standards.ieee.org/standard/1284.1.html"],"folder":"IEEE/IEEE-1284.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"IEEE IEEE 1284.1 nested-reference unavailable"},{"id":"IEEE IEEE 1363","type":"specification","body":"IEEE","designation":"IEEE 1363","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1363.html","download_urls":["https://standards.ieee.org/standard/1363.html"],"folder":"IEEE/IEEE-1363","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 4050","folder":"IETF/RFC-4050","source":"IETF/RFC-4050/RFC-4050.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IEEE IEEE 1363 nested-reference unavailable"},{"id":"IETF RFC 3075","type":"specification","body":"IETF","designation":"RFC 3075","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3075.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3075.txt","https://www.rfc-editor.org/rfc/rfc3075.pdf"],"folder":"IETF/RFC-3075","files":{"txt":{"path":"standards/IETF/RFC-3075/RFC-3075.txt","sha256":"6f0e4904238f79df5d96e88d987d1dc74f930e15569bd93f500d1dc37b2d3857"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies XML (Extensible Markup Language) digital\n signature processing rules and syntax. XML Signatures provide\n integrity, message authentication, and/or signer authentication\n services for data of any type, whether located within the XML that\n includes the signature or elsewhere.","scope_keywords":["3075","algorithm","algorithms","attribute","authentication","key","path","pki","signature","signatures","validation","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 3075 This document specifies XML (Extensible Markup Language) digital\n signature processing rules and syntax. XML Signatures provide\n integrity, message authentication, and/or signer authentication\n services for data of any type, whether located within the XML that\n includes the signature or elsewhere. 3075 algorithm algorithms attribute authentication key path pki signature signatures validation x509 nested-reference unchanged"},{"id":"IETF RFC 3275","type":"specification","body":"IETF","designation":"RFC 3275","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3275.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3275.txt","https://www.rfc-editor.org/rfc/rfc3275.pdf"],"folder":"IETF/RFC-3275","files":{"txt":{"path":"standards/IETF/RFC-3275/RFC-3275.txt","sha256":"822169ad00c4b1de47fc2435c014e171c9bdc1aafb5049a7f80fecff6194d576"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies XML (Extensible Markup Language) digital\n signature processing rules and syntax. XML Signatures provide\n integrity, message authentication, and/or signer authentication\n services for data of any type, whether located within the XML that\n includes the signature or elsewhere.","scope_keywords":["3275","algorithm","algorithms","attribute","authentication","certificate","certificates","key","path","pki","signature","signatures","validation","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3741","folder":"IETF/RFC-3741","source":"IETF/RFC-3741/RFC-3741.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4050","folder":"IETF/RFC-4050","source":"IETF/RFC-4050/RFC-4050.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4231","folder":"IETF/RFC-4231","source":"IETF/RFC-4231/RFC-4231.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 3275 This document specifies XML (Extensible Markup Language) digital\n signature processing rules and syntax. XML Signatures provide\n integrity, message authentication, and/or signer authentication\n services for data of any type, whether located within the XML that\n includes the signature or elsewhere. 3275 algorithm algorithms attribute authentication certificate certificates key path pki signature signatures validation x509 nested-reference unchanged"},{"id":"IETF RFC 3278","type":"specification","body":"IETF","designation":"RFC 3278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3278.txt","https://www.rfc-editor.org/rfc/rfc3278.pdf"],"folder":"IETF/RFC-3278","files":{"txt":{"path":"standards/IETF/RFC-3278/RFC-3278.txt","sha256":"95f3a4d2faf61822eb9c0ed1d9a3d11a8445027d669974ee9b714551e068e7af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use Elliptic Curve Cryptography (ECC)\n public-key algorithms in the Cryptographic Message Syntax (CMS). The\n ECC algorithms support the creation of digital signatures and the\n exchange of keys to encrypt or authenticate content. The definition\n of the algorithm processing is based on the ANSI X9.62 standard,\n developed by the ANSI X9F1 working group, the IEEE 1363 standard, and\n the SEC 1 standard.\n\n The readers attention is called to the Intellectual Property Rights\n section at the end of this document.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 3278 Use of ECC Algorithms in CMS April 2002","scope_keywords":["3278","algorithm","algorithms","attribute","authentication","certificate","certificates","encryption","hash","key","keys","profile","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null}],"search_text":"IETF RFC 3278 This document describes how to use Elliptic Curve Cryptography (ECC)\n public-key algorithms in the Cryptographic Message Syntax (CMS). The\n ECC algorithms support the creation of digital signatures and the\n exchange of keys to encrypt or authenticate content. The definition\n of the algorithm processing is based on the ANSI X9.62 standard,\n developed by the ANSI X9F1 working group, the IEEE 1363 standard, and\n the SEC 1 standard.\n\n The readers attention is called to the Intellectual Property Rights\n section at the end of this document.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 3278 Use of ECC Algorithms in CMS April 2002 3278 algorithm algorithms attribute authentication certificate certificates encryption hash key keys profile signature signatures nested-reference unchanged"},{"id":"IETF RFC 4050","type":"specification","body":"IETF","designation":"RFC 4050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4050.txt","https://www.rfc-editor.org/rfc/rfc4050.pdf"],"folder":"IETF/RFC-4050","files":{"txt":{"path":"standards/IETF/RFC-4050/RFC-4050.txt","sha256":"f3713df55fc3faa4ff3717aff17d64b4c761e62edcf8c4f7f2553169bfaf7109"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use Elliptic Curve Digital Signature\n Algorithm (ECDSA) with XML Signatures. The mechanism specified\n provides integrity, message authentication, and/or signer\n authentication services for data of any type, whether located within\n the XML that includes the signature or included by reference.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 4050 ECDSA for XML Digital Signatures April 2005","scope_keywords":["4050","algorithm","algorithms","attribute","authentication","certificate","certificates","hash","http","key","keys","presentation","qualified","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 4050 This document specifies how to use Elliptic Curve Digital Signature\n Algorithm (ECDSA) with XML Signatures. The mechanism specified\n provides integrity, message authentication, and/or signer\n authentication services for data of any type, whether located within\n the XML that includes the signature or included by reference.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 4050 ECDSA for XML Digital Signatures April 2005 4050 algorithm algorithms attribute authentication certificate certificates hash http key keys presentation qualified signature signatures nested-reference unchanged"},{"id":"IETF RFC 4055","type":"specification","body":"IETF","designation":"RFC 4055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4055.txt","https://www.rfc-editor.org/rfc/rfc4055.pdf"],"folder":"IETF/RFC-4055","files":{"txt":{"path":"standards/IETF/RFC-4055/RFC-4055.txt","sha256":"b8a1ef3fb135c32aed4eee121264f3ec83a46def746c8fe68e05bd1b60324e9a"}},"tags":["nested-reference","unchanged"],"summary":"This document supplements RFC 3279. It describes the conventions for\n using the RSA Probabilistic Signature Scheme (RSASSA-PSS) signature\n algorithm, the RSA Encryption Scheme - Optimal Asymmetric Encryption\n Padding (RSAES-OAEP) key transport algorithm and additional one-way\n hash functions with the Public-Key Cryptography Standards (PKCS) #1\n version 1.5 signature algorithm in the Internet X.509 Public Key\n Infrastructure (PKI). Encoding formats, algorithm identifiers, and\n parameter formats are specified.\n\nSchaad, et al. Standards Track [Page 1]\n\f\nRFC 4055 Additional RSA Algorithms and Identifiers June 2005","scope_keywords":["4055","algorithm","algorithms","certificate","certificates","crl","encryption","hash","key","keys","pki","profile","profiles","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5756","folder":"IETF/RFC-5756","source":"IETF/RFC-5756/RFC-5756.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 4055 This document supplements RFC 3279. It describes the conventions for\n using the RSA Probabilistic Signature Scheme (RSASSA-PSS) signature\n algorithm, the RSA Encryption Scheme - Optimal Asymmetric Encryption\n Padding (RSAES-OAEP) key transport algorithm and additional one-way\n hash functions with the Public-Key Cryptography Standards (PKCS) #1\n version 1.5 signature algorithm in the Internet X.509 Public Key\n Infrastructure (PKI). Encoding formats, algorithm identifiers, and\n parameter formats are specified.\n\nSchaad, et al. Standards Track [Page 1]\n\f\nRFC 4055 Additional RSA Algorithms and Identifiers June 2005 4055 algorithm algorithms certificate certificates crl encryption hash key keys pki profile profiles revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 4492","type":"specification","body":"IETF","designation":"RFC 4492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4492.txt","https://www.rfc-editor.org/rfc/rfc4492.pdf"],"folder":"IETF/RFC-4492","files":{"txt":{"path":"standards/IETF/RFC-4492/RFC-4492.txt","sha256":"360aa48e5f86f3c77458b15dc5683bc005909480eb9c1de2d116e341112b8461"}},"tags":["nested-reference","unchanged"],"summary":"This document describes new key exchange algorithms based on Elliptic\n Curve Cryptography (ECC) for the Transport Layer Security (TLS)\n protocol. In particular, it specifies the use of Elliptic Curve\n Diffie-Hellman (ECDH) key agreement in a TLS handshake and the use of\n Elliptic Curve Digital Signature Algorithm (ECDSA) as a new\n authentication mechanism.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 4492 ECC Cipher Suites for TLS May 2006","scope_keywords":["4492","algorithm","algorithms","authentication","certificate","certificates","encryption","key","keys","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4492 This document describes new key exchange algorithms based on Elliptic\n Curve Cryptography (ECC) for the Transport Layer Security (TLS)\n protocol. In particular, it specifies the use of Elliptic Curve\n Diffie-Hellman (ECDH) key agreement in a TLS handshake and the use of\n Elliptic Curve Digital Signature Algorithm (ECDSA) as a new\n authentication mechanism.\n\nBlake-Wilson, et al. Informational [Page 1]\n\f\nRFC 4492 ECC Cipher Suites for TLS May 2006 4492 algorithm algorithms authentication certificate certificates encryption key keys signature tls nested-reference unchanged"},{"id":"IETF RFC 4556","type":"specification","body":"IETF","designation":"RFC 4556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4556.txt","https://www.rfc-editor.org/rfc/rfc4556.pdf"],"folder":"IETF/RFC-4556","files":{"txt":{"path":"standards/IETF/RFC-4556/RFC-4556.txt","sha256":"4d093f20b584557ec59ce3d0557a36da5d4deedf576cac4ea2c2295c01feb538"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol extensions (hereafter called PKINIT)\n to the Kerberos protocol specification. These extensions provide a\n method for integrating public key cryptography into the initial\n authentication exchange, by using asymmetric-key signature and/or\n encryption algorithms in pre-authentication data fields.","scope_keywords":["4556","algorithm","algorithms","authentication","certificate","certificates","encryption","key","keys","management","pki","signature","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null}],"search_text":"IETF RFC 4556 This document describes protocol extensions (hereafter called PKINIT)\n to the Kerberos protocol specification. These extensions provide a\n method for integrating public key cryptography into the initial\n authentication exchange, by using asymmetric-key signature and/or\n encryption algorithms in pre-authentication data fields. 4556 algorithm algorithms authentication certificate certificates encryption key keys management pki signature timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4754","type":"specification","body":"IETF","designation":"RFC 4754","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4754.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4754.txt","https://www.rfc-editor.org/rfc/rfc4754.pdf"],"folder":"IETF/RFC-4754","files":{"txt":{"path":"standards/IETF/RFC-4754/RFC-4754.txt","sha256":"c20b4f9d331c776d73e3028e549fd36965731701ee10035ab9f6a44a90db207e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the Elliptic Curve Digital Signature\n Algorithm (ECDSA) may be used as the authentication method within the\n Internet Key Exchange (IKE) and Internet Key Exchange version 2\n (IKEv2) protocols. ECDSA may provide benefits including\n computational efficiency, small signature sizes, and minimal\n bandwidth compared to other available digital signature methods.\n This document adds ECDSA capability to IKE and IKEv2 without\n introducing any changes to existing IKE operation.","scope_keywords":["4754","algorithm","algorithms","attribute","authentication","certificate","certificates","encryption","hash","key","keys","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null}],"search_text":"IETF RFC 4754 This document describes how the Elliptic Curve Digital Signature\n Algorithm (ECDSA) may be used as the authentication method within the\n Internet Key Exchange (IKE) and Internet Key Exchange version 2\n (IKEv2) protocols. ECDSA may provide benefits including\n computational efficiency, small signature sizes, and minimal\n bandwidth compared to other available digital signature methods.\n This document adds ECDSA capability to IKE and IKEv2 without\n introducing any changes to existing IKE operation. 4754 algorithm algorithms attribute authentication certificate certificates encryption hash key keys signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 5008","type":"specification","body":"IETF","designation":"RFC 5008","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5008.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5008.txt","https://www.rfc-editor.org/rfc/rfc5008.pdf"],"folder":"IETF/RFC-5008","files":{"txt":{"path":"standards/IETF/RFC-5008/RFC-5008.txt","sha256":"edb0cc952371830e5827f855039a9b8ac7be297b1f78189ee167cc077cba5423"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms in Secure/Multipurpose\n Internet Mail Extensions (S/MIME) as specified in RFC 3851.\n\n1. Introduction\n\n This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms [SuiteB] in\n Secure/Multipurpose Internet Mail Extensions (S/MIME) [MSG]. S/MIME\n makes use of the Cryptographic Message Syntax (CMS) [CMS]. In\n particular, the signed-data and the enveloped-data content types are\n used.\n\n Since many of the Suite B algorithms enjoy uses in other environments\n as well, the majority of the conventions needed for the Suite B\n algorithms are already specified in other documents. This document\n references the source of these conventions, and the relevant details\n are repeated to aid developers that choose to support Suite B. In a\n f","scope_keywords":["5008","algorithm","algorithms","attribute","attributes","certificate","certificates","encryption","hash","key","keys","pki","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null}],"search_text":"IETF RFC 5008 This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms in Secure/Multipurpose\n Internet Mail Extensions (S/MIME) as specified in RFC 3851.\n\n1. Introduction\n\n This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms [SuiteB] in\n Secure/Multipurpose Internet Mail Extensions (S/MIME) [MSG]. S/MIME\n makes use of the Cryptographic Message Syntax (CMS) [CMS]. In\n particular, the signed-data and the enveloped-data content types are\n used.\n\n Since many of the Suite B algorithms enjoy uses in other environments\n as well, the majority of the conventions needed for the Suite B\n algorithms are already specified in other documents. This document\n references the source of these conventions, and the relevant details\n are repeated to aid developers that choose to support Suite B. In a\n f 5008 algorithm algorithms attribute attributes certificate certificates encryption hash key keys pki signature subject nested-reference unchanged"},{"id":"IETF RFC 5869","type":"specification","body":"IETF","designation":"RFC 5869","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5869.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5869.txt","https://www.rfc-editor.org/rfc/rfc5869.pdf"],"folder":"IETF/RFC-5869","files":{"txt":{"path":"standards/IETF/RFC-5869/RFC-5869.txt","sha256":"7a40eb3835b35fc947eb12a2ed614db079d43b26e50dbc537c31fba16397089c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a simple Hashed Message Authentication Code\n (HMAC)-based key derivation function (HKDF), which can be used as a\n building block in various protocols and applications. The key\n derivation function (KDF) is intended to support a wide range of\n applications and requirements, and is conservative in its use of\n cryptographic hash functions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current stat","scope_keywords":["5869","algorithm","algorithms","authentication","hash","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 5869 This document specifies a simple Hashed Message Authentication Code\n (HMAC)-based key derivation function (HKDF), which can be used as a\n building block in various protocols and applications. The key\n derivation function (KDF) is intended to support a wide range of\n applications and requirements, and is conservative in its use of\n cryptographic hash functions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current stat 5869 algorithm algorithms authentication hash http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6931","type":"specification","body":"IETF","designation":"RFC 6931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6931.txt","https://www.rfc-editor.org/rfc/rfc6931.pdf"],"folder":"IETF/RFC-6931","files":{"txt":{"path":"standards/IETF/RFC-6931/RFC-6931.txt","sha256":"65d2eb41a34abc0b08f70040bc9d63622a1fa7fc0c63a7e2aa284fbe9d44cb55"}},"tags":["nested-reference","unchanged"],"summary":"This document expands, updates, and establishes an IANA registry for\n the list of URIs intended for use with XML digital signatures,\n encryption, canonicalization, and key management. These URIs\n identify algorithms and types of information. This document\n obsoletes RFC 4051.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6931.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the p","scope_keywords":["6931","algorithm","algorithms","certificate","certificates","crl","encryption","hash","http","key","license","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null}],"search_text":"IETF RFC 6931 This document expands, updates, and establishes an IANA registry for\n the list of URIs intended for use with XML digital signatures,\n encryption, canonicalization, and key management. These URIs\n identify algorithms and types of information. This document\n obsoletes RFC 4051.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6931.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the p 6931 algorithm algorithms certificate certificates crl encryption hash http key license management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8017","type":"specification","body":"IETF","designation":"RFC 8017","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8017.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8017.txt","https://www.rfc-editor.org/rfc/rfc8017.pdf"],"folder":"IETF/RFC-8017","files":{"txt":{"path":"standards/IETF/RFC-8017/RFC-8017.txt","sha256":"1e72dc473d18df3fc5598cdc12795a9f18f36f1aef15abc23a55eb0d58151d11"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations for the implementation of\n public-key cryptography based on the RSA algorithm, covering\n cryptographic primitives, encryption schemes, signature schemes with\n appendix, and ASN.1 syntax for representing keys and for identifying\n the schemes.\n\n This document represents a republication of PKCS #1 v2.2 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\n This document also obsoletes RFC 3447.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG","scope_keywords":["8017","algorithm","encryption","hash","http","identification","key","keys","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 8017 This document provides recommendations for the implementation of\n public-key cryptography based on the RSA algorithm, covering\n cryptographic primitives, encryption schemes, signature schemes with\n appendix, and ASN.1 syntax for representing keys and for identifying\n the schemes.\n\n This document represents a republication of PKCS #1 v2.2 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\n This document also obsoletes RFC 3447.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG 8017 algorithm encryption hash http identification key keys license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8422","type":"specification","body":"IETF","designation":"RFC 8422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8422.txt","https://www.rfc-editor.org/rfc/rfc8422.pdf"],"folder":"IETF/RFC-8422","files":{"txt":{"path":"standards/IETF/RFC-8422/RFC-8422.txt","sha256":"cac45754399e5115342cf1d773a51ac5a77ad221e9336e43ceadd8f294712350"}},"tags":["nested-reference","unchanged"],"summary":"This document describes key exchange algorithms based on Elliptic\n Curve Cryptography (ECC) for the Transport Layer Security (TLS)\n protocol. In particular, it specifies the use of Ephemeral Elliptic\n Curve Diffie-Hellman (ECDHE) key agreement in a TLS handshake and the\n use of the Elliptic Curve Digital Signature Algorithm (ECDSA) and\n Edwards-curve Digital Signature Algorithm (EdDSA) as authentication\n mechanisms.\n\n This document obsoletes RFC 4492.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of th","scope_keywords":["8422","algorithm","algorithms","authentication","certificate","certificates","encryption","http","https","key","keys","license","signature","signatures","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 8422 This document describes key exchange algorithms based on Elliptic\n Curve Cryptography (ECC) for the Transport Layer Security (TLS)\n protocol. In particular, it specifies the use of Ephemeral Elliptic\n Curve Diffie-Hellman (ECDHE) key agreement in a TLS handshake and the\n use of the Elliptic Curve Digital Signature Algorithm (ECDSA) and\n Edwards-curve Digital Signature Algorithm (EdDSA) as authentication\n mechanisms.\n\n This document obsoletes RFC 4492.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of th 8422 algorithm algorithms authentication certificate certificates encryption http https key keys license signature signatures subject tls nested-reference unchanged"},{"id":"IETF RFC 8446","type":"specification","body":"IETF","designation":"RFC 8446","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8446.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8446.txt","https://www.rfc-editor.org/rfc/rfc8446.pdf"],"folder":"IETF/RFC-8446","files":{"txt":{"path":"standards/IETF/RFC-8446/RFC-8446.txt","sha256":"47871bc8820a2c3b6ea89f061055577058862cf543686b82d10131239702b3bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 1.3 of the Transport Layer Security\n (TLS) protocol. TLS allows client/server applications to communicate\n over the Internet in a way that is designed to prevent eavesdropping,\n tampering, and message forgery.\n\n This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077,\n 5246, and 6961. This document also specifies new requirements for\n TLS 1.2 implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedbac","scope_keywords":["8446","algorithm","algorithms","authentication","certificate","hash","http","https","key","license","presentation","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 8446 This document specifies version 1.3 of the Transport Layer Security\n (TLS) protocol. TLS allows client/server applications to communicate\n over the Internet in a way that is designed to prevent eavesdropping,\n tampering, and message forgery.\n\n This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077,\n 5246, and 6961. This document also specifies new requirements for\n TLS 1.2 implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedbac 8446 algorithm algorithms authentication certificate hash http https key license presentation signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9180","type":"specification","body":"IETF","designation":"RFC 9180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9180.txt","https://www.rfc-editor.org/rfc/rfc9180.pdf"],"folder":"IETF/RFC-9180","files":{"pdf":{"path":"standards/IETF/RFC-9180/RFC-9180.pdf","sha256":"6b2fe0ad177752d43d1de4a53b79ebcd244cb8d62843d65a889ebac78cff3adb"},"txt":{"path":"standards/IETF/RFC-9180/RFC-9180.txt","sha256":"f45a8b7c30231b26d668b1e8168074e5ab514b174d656b67e859895117f1f8f6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a scheme for hybrid public key encryption\n (HPKE). This scheme provides a variant of public key encryption of\n arbitrary-sized plaintexts for a recipient public key. It also\n includes three authenticated variants, including one that\n authenticates possession of a pre-shared key and two optional ones\n that authenticate possession of a key encapsulation mechanism (KEM)\n private key. HPKE works for any combination of an asymmetric KEM,\n key derivation function (KDF), and authenticated encryption with\n additional data (AEAD) encryption function. Some authenticated\n variants may not be supported by all KEMs. We provide instantiations\n of the scheme using widely used and efficient primitives, such as\n Elliptic Curve Diffie-Hellman (ECDH) key agreement, HMAC-based key\n derivation function (HKDF), and SHA2.\n\n This document is a product of the Crypto Forum Research Group (","scope_keywords":["9180","algorithm","algorithms","authentication","encryption","http","https","key","license","management","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 9180 This document describes a scheme for hybrid public key encryption\n (HPKE). This scheme provides a variant of public key encryption of\n arbitrary-sized plaintexts for a recipient public key. It also\n includes three authenticated variants, including one that\n authenticates possession of a pre-shared key and two optional ones\n that authenticate possession of a key encapsulation mechanism (KEM)\n private key. HPKE works for any combination of an asymmetric KEM,\n key derivation function (KDF), and authenticated encryption with\n additional data (AEAD) encryption function. Some authenticated\n variants may not be supported by all KEMs. We provide instantiations\n of the scheme using widely used and efficient primitives, such as\n Elliptic Curve Diffie-Hellman (ECDH) key agreement, HMAC-based key\n derivation function (HKDF), and SHA2.\n\n This document is a product of the Crypto Forum Research Group ( 9180 algorithm algorithms authentication encryption http https key license management subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9380","type":"specification","body":"IETF","designation":"RFC 9380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9380.txt","https://www.rfc-editor.org/rfc/rfc9380.pdf"],"folder":"IETF/RFC-9380","files":{"pdf":{"path":"standards/IETF/RFC-9380/RFC-9380.pdf","sha256":"13df469614c21fa6c4ca323129a1d0baaa2a55fe854043235487fc4a07af944b"},"txt":{"path":"standards/IETF/RFC-9380/RFC-9380.txt","sha256":"a2e6ab02b2117d6f52ac293020857752972b2e23ae005c33f612e40436ff4b6d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a number of algorithms for encoding or\n hashing an arbitrary string to a point on an elliptic curve. This\n document is a product of the Crypto Forum Research Group (CFRG) in\n the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback ","scope_keywords":["9380","algorithm","algorithms","hash","hashing","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"}],"search_text":"IETF RFC 9380 This document specifies a number of algorithms for encoding or\n hashing an arbitrary string to a point on an elliptic curve. This\n document is a product of the Crypto Forum Research Group (CFRG) in\n the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback  9380 algorithm algorithms hash hashing http https license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1363-2000","type":"specification","body":"IEEE","designation":"IEEE 1363-2000","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1363-2000.html","download_urls":["https://standards.ieee.org/standard/1363-2000.html"],"folder":"IEEE/IEEE-1363-2000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"IEEE IEEE 1363-2000 nested-reference unavailable"},{"id":"IETF RFC 3447","type":"specification","body":"IETF","designation":"RFC 3447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3447.txt","https://www.rfc-editor.org/rfc/rfc3447.pdf"],"folder":"IETF/RFC-3447","files":{"txt":{"path":"standards/IETF/RFC-3447/RFC-3447.txt","sha256":"817490b4ad83445b5fe708bf70cec2897e119eb6c0f616bdc6a75961a35b61fe"}},"tags":["nested-reference","unchanged"],"summary":"This memo represents a republication of PKCS #1 v2.1 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document is taken directly from the PKCS #1 v2.1 document, with\n certain corrections made during the publication process.","scope_keywords":["3447","algorithm","encryption","hash","identification","key","keys","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 3447 This memo represents a republication of PKCS #1 v2.1 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document is taken directly from the PKCS #1 v2.1 document, with\n certain corrections made during the publication process. 3447 algorithm encryption hash identification key keys presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 4753","type":"specification","body":"IETF","designation":"RFC 4753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4753.txt","https://www.rfc-editor.org/rfc/rfc4753.pdf"],"folder":"IETF/RFC-4753","files":{"txt":{"path":"standards/IETF/RFC-4753/RFC-4753.txt","sha256":"07abe587a271e036dbc93252b9a1554389bf6ecf9a563d86bf9099c970502dae"}},"tags":["nested-reference","unchanged"],"summary":"This document describes new Elliptic Curve Cryptography (ECC) groups\n for use in the Internet Key Exchange (IKE) and Internet Key Exchange\n version 2 (IKEv2) protocols in addition to previously defined groups.\n Specifically, the new curve groups are based on modular arithmetic\n rather than binary arithmetic. These new groups are defined to align\n IKE and IKEv2 with other ECC implementations and standards,\n particularly NIST standards. In addition, the curves defined here\n can provide more efficient implementation than previously defined ECC\n groups.","scope_keywords":["4753","encryption","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null}],"search_text":"IETF RFC 4753 This document describes new Elliptic Curve Cryptography (ECC) groups\n for use in the Internet Key Exchange (IKE) and Internet Key Exchange\n version 2 (IKEv2) protocols in addition to previously defined groups.\n Specifically, the new curve groups are based on modular arithmetic\n rather than binary arithmetic. These new groups are defined to align\n IKE and IKEv2 with other ECC implementations and standards,\n particularly NIST standards. In addition, the curves defined here\n can provide more efficient implementation than previously defined ECC\n groups. 4753 encryption key trust nested-reference unchanged"},{"id":"IETF RFC 5903","type":"specification","body":"IETF","designation":"RFC 5903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5903.txt","https://www.rfc-editor.org/rfc/rfc5903.pdf"],"folder":"IETF/RFC-5903","files":{"txt":{"path":"standards/IETF/RFC-5903/RFC-5903.txt","sha256":"939fab548a6e6bb49a5b3c4dd24a3c5df54a46645447b2d6f4df4fd88ff2d69f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes three Elliptic Curve Cryptography (ECC)\n groups for use in the Internet Key Exchange (IKE) and Internet Key\n Exchange version 2 (IKEv2) protocols in addition to previously\n defined groups. These groups are based on modular arithmetic rather\n than binary arithmetic. These groups are defined to align IKE and\n IKEv2 with other ECC implementations and standards, particularly NIST\n standards. In addition, the curves defined here can provide more\n efficient implementation than previously defined ECC groups. This\n document obsoletes RFC 4753.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th","scope_keywords":["5903","encryption","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null}],"search_text":"IETF RFC 5903 This document describes three Elliptic Curve Cryptography (ECC)\n groups for use in the Internet Key Exchange (IKE) and Internet Key\n Exchange version 2 (IKEv2) protocols in addition to previously\n defined groups. These groups are based on modular arithmetic rather\n than binary arithmetic. These groups are defined to align IKE and\n IKEv2 with other ECC implementations and standards, particularly NIST\n standards. In addition, the curves defined here can provide more\n efficient implementation than previously defined ECC groups. This\n document obsoletes RFC 4753.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th 5903 encryption http key license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1363.2-2008","type":"specification","body":"IEEE","designation":"IEEE 1363.2-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1363.2-2008.html","download_urls":["https://standards.ieee.org/standard/1363.2-2008.html"],"folder":"IEEE/IEEE-1363.2-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IEEE IEEE 1363.2-2008 nested-reference unavailable"},{"id":"IEEE IEEE 1394","type":"specification","body":"IEEE","designation":"IEEE 1394","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1394.html","download_urls":["https://standards.ieee.org/standard/1394.html"],"folder":"IEEE/IEEE-1394","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2734","folder":"IETF/RFC-2734","source":"IETF/RFC-2734/RFC-2734.txt","version":null},{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 1394 nested-reference unavailable"},{"id":"IETF RFC 2734","type":"specification","body":"IETF","designation":"RFC 2734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2734.txt","https://www.rfc-editor.org/rfc/rfc2734.pdf"],"folder":"IETF/RFC-2734","files":{"txt":{"path":"standards/IETF/RFC-2734/RFC-2734.txt","sha256":"53bc232d42fbae2199fbe7c345b2149426c7af6973a6bf41acb2b5ca73a089c5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use IEEE Std 1394-1995, Standard for a\n High Performance Serial Bus (and its supplements), for the transport\n of Internet Protocol Version 4 (IPv4) datagrams; it defines the\n necessary methods, data structures and codes for that purpose. These\n include not only packet formats and encapsulation methods for\n datagrams, but also an address resolution protocol (1394 ARP) and a\n multicast channel allocation protocol (MCAP). Both 1394 ARP and MCAP\n are specific to Serial Bus; the latter permits management of Serial\n Bus resources when used by IP multicast groups.","scope_keywords":["2734","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null}],"search_text":"IETF RFC 2734 This document specifies how to use IEEE Std 1394-1995, Standard for a\n High Performance Serial Bus (and its supplements), for the transport\n of Internet Protocol Version 4 (IPv4) datagrams; it defines the\n necessary methods, data structures and codes for that purpose. These\n include not only packet formats and encapsulation methods for\n datagrams, but also an address resolution protocol (1394 ARP) and a\n multicast channel allocation protocol (MCAP). Both 1394 ARP and MCAP\n are specific to Serial Bus; the latter permits management of Serial\n Bus resources when used by IP multicast groups. 2734 delivery management subject nested-reference unchanged"},{"id":"IETF RFC 2855","type":"specification","body":"IETF","designation":"RFC 2855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2855.txt","https://www.rfc-editor.org/rfc/rfc2855.pdf"],"folder":"IETF/RFC-2855","files":{"txt":{"path":"standards/IETF/RFC-2855/RFC-2855.txt","sha256":"6ddc4ad1f67c03ff7a0d7b933b331bddf9e9c435a7b5af94467112c89097d162"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Fujisawa\nRequest for Comments: 2855 Sony Corporation\nCategory: Standards Track June 2000\n\n DHCP for IEEE 1394\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n IEEE Std 1394-1995 is a standard for a High Performance Serial Bus.\n Since 1394 uses a different link-layer addressing method than\n conventional IEEE802/Ethernet, the usage of some fields must be\n clarified to achieve interoperability. This memo describes the 1394\n specific usage of some fields of DHCP me","scope_keywords":["2855","authentication","http","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null}],"search_text":"IETF RFC 2855 Network Working Group K. Fujisawa\nRequest for Comments: 2855 Sony Corporation\nCategory: Standards Track June 2000\n\n DHCP for IEEE 1394\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n IEEE Std 1394-1995 is a standard for a High Performance Serial Bus.\n Since 1394 uses a different link-layer addressing method than\n conventional IEEE802/Ethernet, the usage of some fields must be\n clarified to achieve interoperability. This memo describes the 1394\n specific usage of some fields of DHCP me 2855 authentication http key qualified nested-reference unchanged"},{"id":"IETF RFC 3146","type":"specification","body":"IETF","designation":"RFC 3146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3146.txt","https://www.rfc-editor.org/rfc/rfc3146.pdf"],"folder":"IETF/RFC-3146","files":{"txt":{"path":"standards/IETF/RFC-3146/RFC-3146.txt","sha256":"1b86a3396311b969009f8d9ce264ba7d61e763f4f1e28efa6d66f162518b3656"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Fujisawa\nRequest for Comments: 3146 A. Onoe\nCategory: Standards Track Sony Corporation\n October 2001\n\n Transmission of IPv6 Packets over IEEE 1394 Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on IEEE1394 networks.\n\n1. INTRODUCTION\n\n IEEE Std 1394-1995 (and its amendment) is a standa","scope_keywords":["3146","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 3146 Network Working Group K. Fujisawa\nRequest for Comments: 3146 A. Onoe\nCategory: Standards Track Sony Corporation\n October 2001\n\n Transmission of IPv6 Packets over IEEE 1394 Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on IEEE1394 networks.\n\n1. INTRODUCTION\n\n IEEE Std 1394-1995 (and its amendment) is a standa 3146 key management nested-reference unchanged"},{"id":"IETF RFC 3189","type":"specification","body":"IETF","designation":"RFC 3189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3189.txt","https://www.rfc-editor.org/rfc/rfc3189.pdf"],"folder":"IETF/RFC-3189","files":{"txt":{"path":"standards/IETF/RFC-3189/RFC-3189.txt","sha256":"37ae4bd319c45a6da3dcdb914030fccd306a46f7859c5b383130ff8165a641ce"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the packetization scheme for encapsulating\n the compressed digital video data streams commonly known as \"DV\" into\n a payload format for the Real-Time Transport Protocol (RTP).\n\n1. Introduction\n\n This document specifies payload formats for encapsulating both\n consumer- and professional-use DV format data streams into the Real-\n time Transport Protocol (RTP), version 2 [6]. DV compression audio\n and video formats were designed for helical-scan magnetic tape media.\n The DV standards for consumer-market devices, the IEC 61883 and 61834\n series, cover many aspects of consumer-use digital video, including\n mechanical specifications of a cassette, magnetic recording format,\n error correction on the magnetic tape, DCT video encoding format, and\n audio encoding format [1]. The digital interface part of IEC 61883\n defines an interface on an IEEE 1394 network [2,3]. This\n sp","scope_keywords":["3189","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null}],"search_text":"IETF RFC 3189 This document specifies the packetization scheme for encapsulating\n the compressed digital video data streams commonly known as \"DV\" into\n a payload format for the Real-Time Transport Protocol (RTP).\n\n1. Introduction\n\n This document specifies payload formats for encapsulating both\n consumer- and professional-use DV format data streams into the Real-\n time Transport Protocol (RTP), version 2 [6]. DV compression audio\n and video formats were designed for helical-scan magnetic tape media.\n The DV standards for consumer-market devices, the IEC 61883 and 61834\n series, cover many aspects of consumer-use digital video, including\n mechanical specifications of a cassette, magnetic recording format,\n error correction on the magnetic tape, DCT video encoding format, and\n audio encoding format [1]. The digital interface part of IEC 61883\n defines an interface on an IEEE 1394 network [2,3]. This\n sp 3189 key timestamp nested-reference unchanged"},{"id":"IETF RFC 3790","type":"specification","body":"IETF","designation":"RFC 3790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3790.txt","https://www.rfc-editor.org/rfc/rfc3790.pdf"],"folder":"IETF/RFC-3790","files":{"txt":{"path":"standards/IETF/RFC-3790/RFC-3790.txt","sha256":"c631617a58fbea7e452e928b1e3a8832da47f671c01b1dbf5e8d404efa5fc9b8"}},"tags":["nested-reference","unchanged"],"summary":"This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Internet Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented.","scope_keywords":["3790","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 3790 This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Internet Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented. 3790 authentication path nested-reference unchanged"},{"id":"IETF RFC 3831","type":"specification","body":"IETF","designation":"RFC 3831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3831.txt","https://www.rfc-editor.org/rfc/rfc3831.pdf"],"folder":"IETF/RFC-3831","files":{"txt":{"path":"standards/IETF/RFC-3831/RFC-3831.txt","sha256":"fe36d60c5f5b83181fce74374eb0acd7354304bd7c9428ca9a62ac28624c3157"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the way of encapsulating IPv6 packets over\n Fibre Channel, and the method of forming IPv6 link-local addresses\n and statelessly autoconfigured addresses on Fibre Channel networks.","scope_keywords":["3831","key","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null}],"search_text":"IETF RFC 3831 This document specifies the way of encapsulating IPv6 packets over\n Fibre Channel, and the method of forming IPv6 link-local addresses\n and statelessly autoconfigured addresses on Fibre Channel networks. 3831 key management validation nested-reference unchanged"},{"id":"IETF RFC 4390","type":"specification","body":"IETF","designation":"RFC 4390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4390.txt","https://www.rfc-editor.org/rfc/rfc4390.pdf"],"folder":"IETF/RFC-4390","files":{"txt":{"path":"standards/IETF/RFC-4390/RFC-4390.txt","sha256":"d3871009fb265f8e157c299e1f902b1ecd8f5fca1377cf06d6e8c8ceef1e4ee4"}},"tags":["nested-reference","unchanged"],"summary":"IP over Infiniband (IPoIB) link-layer address is 20 octets long.\n This is larger than the 16 octets reserved for the hardware address\n in a Dynamic Host Configuration Protocol/Bootstrap Protocol\n (DHCP/BOOTP) message. The above inequality imposes restrictions on\n the use of the DHCP message fields when used over an IPoIB network.\n This document describes the use of DHCP message fields when\n implementing DHCP over IPoIB.","scope_keywords":["4390","authentication","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null}],"search_text":"IETF RFC 4390 IP over Infiniband (IPoIB) link-layer address is 20 octets long.\n This is larger than the 16 octets reserved for the hardware address\n in a Dynamic Host Configuration Protocol/Bootstrap Protocol\n (DHCP/BOOTP) message. The above inequality imposes restrictions on\n the use of the DHCP message fields when used over an IPoIB network.\n This document describes the use of DHCP message fields when\n implementing DHCP over IPoIB. 4390 authentication http key nested-reference unchanged"},{"id":"IETF RFC 4541","type":"specification","body":"IETF","designation":"RFC 4541","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4541.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4541.txt","https://www.rfc-editor.org/rfc/rfc4541.pdf"],"folder":"IETF/RFC-4541","files":{"txt":{"path":"standards/IETF/RFC-4541/RFC-4541.txt","sha256":"4cfb82931af6775125e05348e0224ab7661542575a9ba3315696de3ebaf6ae3f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the recommendations for Internet Group Management\n Protocol (IGMP) and Multicast Listener Discovery (MLD) snooping\n switches. These are based on best current practices for IGMPv2, with\n further considerations for IGMPv3- and MLDv2-snooping. Additional\n areas of relevance, such as link layer topology changes and\n Ethernet-specific encapsulation issues, are also considered.\n\n1. Introduction\n\n The IEEE bridge standard [BRIDGE] specifies how LAN packets are\n 'bridged', or as is more commonly used today, switched between LAN\n segments. The operation of a switch with respect to multicast\n packets can be summarized as follows. When processing a packet whose\n destination MAC address is a multicast address, the switch will\n forward a copy of the packet into each of the remaining network\n interfaces that are in the forwarding state in accordance with\n [BRIDGE]. The spanning tre","scope_keywords":["4541","algorithm","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 463","folder":"IETF/RFC-463","source":"IETF/RFC-463/RFC-463.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null}],"search_text":"IETF RFC 4541 This memo describes the recommendations for Internet Group Management\n Protocol (IGMP) and Multicast Listener Discovery (MLD) snooping\n switches. These are based on best current practices for IGMPv2, with\n further considerations for IGMPv3- and MLDv2-snooping. Additional\n areas of relevance, such as link layer topology changes and\n Ethernet-specific encapsulation issues, are also considered.\n\n1. Introduction\n\n The IEEE bridge standard [BRIDGE] specifies how LAN packets are\n 'bridged', or as is more commonly used today, switched between LAN\n segments. The operation of a switch with respect to multicast\n packets can be summarized as follows. When processing a packet whose\n destination MAC address is a multicast address, the switch will\n forward a copy of the packet into each of the remaining network\n interfaces that are in the forwarding state in accordance with\n [BRIDGE]. The spanning tre 4541 algorithm management path nested-reference unchanged"},{"id":"IETF RFC 5342","type":"specification","body":"IETF","designation":"RFC 5342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5342.txt","https://www.rfc-editor.org/rfc/rfc5342.pdf"],"folder":"IETF/RFC-5342","files":{"txt":{"path":"standards/IETF/RFC-5342/RFC-5342.txt","sha256":"b048b496c941f53936cc82bb353936e21e80847e243ac4e4051fb2ae77d0f6ae"}},"tags":["nested-reference","unchanged"],"summary":"Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses some use of such parameters in\n IETF protocols and specifies IANA considerations for allocation of\n code points under the IANA OUI (Organizationally Unique Identifier).\n\nEastlake 3rd Best Current Practice [Page 1]\n\f\nRFC 5342 IANA & IETF Use of IEEE 802 Parameters September 2008","scope_keywords":["5342","authentication","holder","http","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 5342 Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses some use of such parameters in\n IETF protocols and specifies IANA considerations for allocation of\n code points under the IANA OUI (Organizationally Unique Identifier).\n\nEastlake 3rd Best Current Practice [Page 1]\n\f\nRFC 5342 IANA & IETF Use of IEEE 802 Parameters September 2008 5342 authentication holder http policies nested-reference unchanged"},{"id":"IETF RFC 6434","type":"specification","body":"IETF","designation":"RFC 6434","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6434.txt","https://www.rfc-editor.org/rfc/rfc6434.pdf"],"folder":"IETF/RFC-6434","files":{"txt":{"path":"standards/IETF/RFC-6434/RFC-6434.txt","sha256":"ae2543bb651a3c24e92f2335d5abce4824640f81983411da8e507f1736bf4c76"}},"tags":["nested-reference","unchanged"],"summary":"This document defines requirements for IPv6 nodes. It is expected\n that IPv6 will be deployed in a wide range of devices and situations.\n Specifying the requirements for IPv6 nodes allows IPv6 to function\n well and interoperate in a large number of situations and\n deployments.\n\n This document obsoletes RFC 4294.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov","scope_keywords":["6434","algorithm","algorithms","http","license","management","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 6434 This document defines requirements for IPv6 nodes. It is expected\n that IPv6 will be deployed in a wide range of devices and situations.\n Specifying the requirements for IPv6 nodes allows IPv6 to function\n well and interoperate in a large number of situations and\n deployments.\n\n This document obsoletes RFC 4294.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov 6434 algorithm algorithms http license management path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6741","type":"specification","body":"IETF","designation":"RFC 6741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6741.txt","https://www.rfc-editor.org/rfc/rfc6741.pdf"],"folder":"IETF/RFC-6741","files":{"txt":{"path":"standards/IETF/RFC-6741/RFC-6741.txt","sha256":"118477e5a38e00fb2493667d32e73bc9ed8cb260f0438aa37eed42082e7613cd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes common (i.e., version independent)\n engineering details for the Identifier-Locator Network Protocol\n (ILNP), which is an experimental, evolutionary enhancement to IP.\n This document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by th","scope_keywords":["6741","authentication","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 6741 This document describes common (i.e., version independent)\n engineering details for the Identifier-Locator Network Protocol\n (ILNP), which is an experimental, evolutionary enhancement to IP.\n This document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by th 6741 authentication http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7042","type":"specification","body":"IETF","designation":"RFC 7042","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7042.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7042.txt","https://www.rfc-editor.org/rfc/rfc7042.pdf"],"folder":"IETF/RFC-7042","files":{"txt":{"path":"standards/IETF/RFC-7042/RFC-7042.txt","sha256":"8ad7b042253d1204cef2a5eddd6682072a5d4f9edc3b749df15df7bccdeca1df"}},"tags":["nested-reference","unchanged"],"summary":"Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses several uses of such parameters\n in IETF protocols, specifies IANA considerations for assignment of\n points under the IANA OUI (Organizationally Unique Identifier), and\n provides some values for use in documentation. This document\n obsoletes RFC 5342.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or","scope_keywords":["7042","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 7042 Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses several uses of such parameters\n in IETF protocols, specifies IANA considerations for assignment of\n points under the IANA OUI (Organizationally Unique Identifier), and\n provides some values for use in documentation. This document\n obsoletes RFC 5342.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or 7042 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7143","type":"specification","body":"IETF","designation":"RFC 7143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7143.txt","https://www.rfc-editor.org/rfc/rfc7143.pdf"],"folder":"IETF/RFC-7143","files":{"txt":{"path":"standards/IETF/RFC-7143/RFC-7143.txt","sha256":"046e834ca5fb24658bb52dbbd37b685f0fd864535345f8afb3ac3d5acbc80add"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a transport protocol for SCSI that works on\n top of TCP. The iSCSI protocol aims to be fully compliant with the\n standardized SCSI Architecture Model (SAM-2). RFC 3720 defined the\n original iSCSI protocol. RFC 3721 discusses iSCSI naming examples\n and discovery techniques. Subsequently, RFC 3980 added an additional\n naming format to the iSCSI protocol. RFC 4850 followed up by adding\n a new public extension key to iSCSI. RFC 5048 offered a number of\n clarifications as well as a few improvements and corrections to the\n original iSCSI protocol.\n\n This document obsoletes RFCs 3720, 3980, 4850, and 5048 by\n consolidating them into a single document and making additional\n updates to the consolidated specification. This document also\n updates RFC 3721. The text in this document thus supersedes the text\n in all the noted RFCs wherever there is a difference in semantics.\n\n","scope_keywords":["7143","http","key","license","management","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7143 This document describes a transport protocol for SCSI that works on\n top of TCP. The iSCSI protocol aims to be fully compliant with the\n standardized SCSI Architecture Model (SAM-2). RFC 3720 defined the\n original iSCSI protocol. RFC 3721 discusses iSCSI naming examples\n and discovery techniques. Subsequently, RFC 3980 added an additional\n naming format to the iSCSI protocol. RFC 4850 followed up by adding\n a new public extension key to iSCSI. RFC 5048 offered a number of\n clarifications as well as a few improvements and corrections to the\n original iSCSI protocol.\n\n This document obsoletes RFCs 3720, 3980, 4850, and 5048 by\n consolidating them into a single document and making additional\n updates to the consolidated specification. This document also\n updates RFC 3721. The text in this document thus supersedes the text\n in all the noted RFCs wherever there is a difference in semantics.\n\n 7143 http key license management qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 7421","type":"specification","body":"IETF","designation":"RFC 7421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7421.txt","https://www.rfc-editor.org/rfc/rfc7421.pdf"],"folder":"IETF/RFC-7421","files":{"txt":{"path":"standards/IETF/RFC-7421/RFC-7421.txt","sha256":"abf1848f7b7606e838a76c5e08db3b4f3fcfead6a3d1356065b48c4293aefa7b"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 unicast addressing format includes a separation between the\n prefix used to route packets to a subnet and the interface identifier\n used to specify a given interface connected to that subnet.\n Currently, the interface identifier is defined as 64 bits long for\n almost every case, leaving 64 bits for the subnet prefix. This\n document describes the advantages of this fixed boundary and analyzes\n the issues that would be involved in treating it as a variable\n boundary.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG ","scope_keywords":["7421","audit","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7421 The IPv6 unicast addressing format includes a separation between the\n prefix used to route packets to a subnet and the interface identifier\n used to specify a given interface connected to that subnet.\n Currently, the interface identifier is defined as 64 bits long for\n almost every case, leaving 64 bits for the subnet prefix. This\n document describes the advantages of this fixed boundary and analyzes\n the issues that would be involved in treating it as a variable\n boundary.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG  7421 audit http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8064","type":"specification","body":"IETF","designation":"RFC 8064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8064.txt","https://www.rfc-editor.org/rfc/rfc8064.pdf"],"folder":"IETF/RFC-8064","files":{"txt":{"path":"standards/IETF/RFC-8064/RFC-8064.txt","sha256":"894054810bdc10b76a39907b72e28c2f7980a729949f2b85a0b52bf99ca52592"}},"tags":["nested-reference","unchanged"],"summary":"This document changes the recommended default Interface Identifier\n (IID) generation scheme for cases where Stateless Address\n Autoconfiguration (SLAAC) is used to generate a stable IPv6 address.\n It recommends using the mechanism specified in RFC 7217 in such\n cases, and recommends against embedding stable link-layer addresses\n in IPv6 IIDs. It formally updates RFC 2464, RFC 2467, RFC 2470, RFC\n 2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC\n 4338, RFC 4391, RFC 5072, and RFC 5121. This document does not\n change any existing recommendations concerning the use of temporary\n addresses as specified in RFC 4941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for public","scope_keywords":["8064","algorithm","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8064 This document changes the recommended default Interface Identifier\n (IID) generation scheme for cases where Stateless Address\n Autoconfiguration (SLAAC) is used to generate a stable IPv6 address.\n It recommends using the mechanism specified in RFC 7217 in such\n cases, and recommends against embedding stable link-layer addresses\n in IPv6 IIDs. It formally updates RFC 2464, RFC 2467, RFC 2470, RFC\n 2491, RFC 2492, RFC 2497, RFC 2590, RFC 3146, RFC 3572, RFC 4291, RFC\n 4338, RFC 4391, RFC 5072, and RFC 5121. This document does not\n change any existing recommendations concerning the use of temporary\n addresses as specified in RFC 4941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for public 8064 algorithm http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 9542","type":"specification","body":"IETF","designation":"RFC 9542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9542.txt","https://www.rfc-editor.org/rfc/rfc9542.pdf"],"folder":"IETF/RFC-9542","files":{"pdf":{"path":"standards/IETF/RFC-9542/RFC-9542.pdf","sha256":"0d3d08bb772528c7935b49e0072d702a84309bc02f3a2f263d0f1f274893e8c2"},"txt":{"path":"standards/IETF/RFC-9542/RFC-9542.txt","sha256":"5c52f6cb6aacb1dea947a206bc8775ec8aaed52d74b92c600f1b1166d5c3c0f1"}},"tags":["nested-reference","unchanged"],"summary":"Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses several aspects of such\n parameters and their use in IETF protocols, specifies IANA\n considerations for assignment of points under the IANA\n Organizationally Unique Identifier (OUI), and provides some values\n for use in documentation. This document obsoletes RFC 7042.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https:/","scope_keywords":["9542","http","https","license","management","policies","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 9542 Some IETF protocols make use of Ethernet frame formats and IEEE 802\n parameters. This document discusses several aspects of such\n parameters and their use in IETF protocols, specifies IANA\n considerations for assignment of points under the IANA\n Organizationally Unique Identifier (OUI), and provides some values\n for use in documentation. This document obsoletes RFC 7042.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https:/ 9542 http https license management policies presentation subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1394-1995","type":"specification","body":"IEEE","designation":"IEEE 1394-1995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1394-1995.html","download_urls":["https://standards.ieee.org/standard/1394-1995.html"],"folder":"IEEE/IEEE-1394-1995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2734","folder":"IETF/RFC-2734","source":"IETF/RFC-2734/RFC-2734.txt","version":null},{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null}],"search_text":"IEEE IEEE 1394-1995 nested-reference unavailable"},{"id":"IEEE IEEE 1394-2008","type":"specification","body":"IEEE","designation":"IEEE 1394-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1394-2008.html","download_urls":["https://standards.ieee.org/standard/1394-2008.html"],"folder":"IEEE/IEEE-1394-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 1394-2008 nested-reference unavailable"},{"id":"IEEE IEEE 1394.","type":"specification","body":"IEEE","designation":"IEEE 1394.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1394..html","download_urls":["https://standards.ieee.org/standard/1394..html"],"folder":"IEEE/IEEE-1394.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IEEE IEEE 1394. nested-reference unavailable"},{"id":"IEEE IEEE 1588","type":"specification","body":"IEEE","designation":"IEEE 1588","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1588.html","download_urls":["https://standards.ieee.org/standard/1588.html"],"folder":"IEEE/IEEE-1588","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 7164","folder":"IETF/RFC-7164","source":"IETF/RFC-7164/RFC-7164.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null}],"search_text":"IEEE IEEE 1588 nested-reference unavailable"},{"id":"IETF RFC 6374","type":"specification","body":"IETF","designation":"RFC 6374","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6374.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6374.txt","https://www.rfc-editor.org/rfc/rfc6374.pdf"],"folder":"IETF/RFC-6374","files":{"txt":{"path":"standards/IETF/RFC-6374/RFC-6374.txt","sha256":"843d347c6c020e2bef3111e4b19d8be06236f79feeb2dbf8704cc3ee4a3aff62"}},"tags":["nested-reference","unchanged"],"summary":"Many service provider service level agreements (SLAs) depend on the\n ability to measure and monitor performance metrics for packet loss\n and one-way and two-way delay, as well as related metrics such as\n delay variation and channel throughput. This measurement capability\n also provides operators with greater visibility into the performance\n characteristics of their networks, thereby facilitating planning,\n troubleshooting, and network performance evaluation. This document\n specifies protocol mechanisms to enable the efficient and accurate\n measurement of these performance metrics in MPLS networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering ","scope_keywords":["6374","http","license","path","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 6374 Many service provider service level agreements (SLAs) depend on the\n ability to measure and monitor performance metrics for packet loss\n and one-way and two-way delay, as well as related metrics such as\n delay variation and channel throughput. This measurement capability\n also provides operators with greater visibility into the performance\n characteristics of their networks, thereby facilitating planning,\n troubleshooting, and network performance evaluation. This document\n specifies protocol mechanisms to enable the efficient and accurate\n measurement of these performance metrics in MPLS networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering  6374 http license path subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7164","type":"specification","body":"IETF","designation":"RFC 7164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7164.txt","https://www.rfc-editor.org/rfc/rfc7164.pdf"],"folder":"IETF/RFC-7164","files":{"txt":{"path":"standards/IETF/RFC-7164/RFC-7164.txt","sha256":"09c05d168e79d8b1b2af80e43bafcc299488be135e1fa5d4635d56354982b522"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses issues that arise when RTP sessions span\n Coordinated Universal Time (UTC) leap seconds. It updates RFC 3550\n by describing how RTP senders and receivers should behave in the\n presence of leap seconds.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7164.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rig","scope_keywords":["7164","http","key","license","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7164 This document discusses issues that arise when RTP sessions span\n Coordinated Universal Time (UTC) leap seconds. It updates RFC 3550\n by describing how RTP senders and receivers should behave in the\n presence of leap seconds.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7164.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rig 7164 http key license subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7273","type":"specification","body":"IETF","designation":"RFC 7273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7273.txt","https://www.rfc-editor.org/rfc/rfc7273.pdf"],"folder":"IETF/RFC-7273","files":{"txt":{"path":"standards/IETF/RFC-7273/RFC-7273.txt","sha256":"003f5c85a2be025a1c06a88e11df0e2d5004b7cb70011a736d7395b313ce2717"}},"tags":["nested-reference","unchanged"],"summary":"NTP format timestamps are used by several RTP protocols for\n synchronisation and statistical measurements. This memo specifies\n Session Description Protocol (SDP) signalling that identifies\n timestamp reference clock sources and SDP signalling that identifies\n the media clock sources in a multimedia session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7273.\n\nCopyright Notice\n\n Copyri","scope_keywords":["7273","attribute","attributes","http","key","license","path","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7273 NTP format timestamps are used by several RTP protocols for\n synchronisation and statistical measurements. This memo specifies\n Session Description Protocol (SDP) signalling that identifies\n timestamp reference clock sources and SDP signalling that identifies\n the media clock sources in a multimedia session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7273.\n\nCopyright Notice\n\n Copyri 7273 attribute attributes http key license path subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7384","type":"specification","body":"IETF","designation":"RFC 7384","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7384.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7384.txt","https://www.rfc-editor.org/rfc/rfc7384.pdf"],"folder":"IETF/RFC-7384","files":{"txt":{"path":"standards/IETF/RFC-7384/RFC-7384.txt","sha256":"f9c409e86f88beb290bfa3f03269818e2a7a1638e8400b352f6ba9682f6bbce5"}},"tags":["nested-reference","unchanged"],"summary":"As time and frequency distribution protocols are becoming\n increasingly common and widely deployed, concern about their exposure\n to various security threats is increasing. This document defines a\n set of security requirements for time protocols, focusing on the\n Precision Time Protocol (PTP) and the Network Time Protocol (NTP).\n This document also discusses the security impacts of time protocol\n practices, the performance implications of external security\n practices on time protocols, and the dependencies between other\n security services and time synchronization.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication ","scope_keywords":["7384","authentication","authorization","certificate","certificates","http","key","keys","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null}],"search_text":"IETF RFC 7384 As time and frequency distribution protocols are becoming\n increasingly common and widely deployed, concern about their exposure\n to various security threats is increasing. This document defines a\n set of security requirements for time protocols, focusing on the\n Precision Time Protocol (PTP) and the Network Time Protocol (NTP).\n This document also discusses the security impacts of time protocol\n practices, the performance implications of external security\n practices on time protocols, and the dependencies between other\n security services and time synchronization.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication  7384 authentication authorization certificate certificates http key keys license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7456","type":"specification","body":"IETF","designation":"RFC 7456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7456.txt","https://www.rfc-editor.org/rfc/rfc7456.pdf"],"folder":"IETF/RFC-7456","files":{"txt":{"path":"standards/IETF/RFC-7456/RFC-7456.txt","sha256":"433de22e86b27303e1e778cff2c1fda98ecaff2cd50aaef31a839ad4651ca69f"}},"tags":["nested-reference","unchanged"],"summary":"Performance Monitoring (PM) is a key aspect of Operations,\n Administration, and Maintenance (OAM). It allows network operators\n to verify the Service Level Agreement (SLA) provided to customers and\n to detect network anomalies. This document specifies mechanisms for\n Loss Measurement and Delay Measurement in Transparent Interconnection\n of Lots of Links (TRILL) networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht","scope_keywords":["7456","delivery","http","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null}],"search_text":"IETF RFC 7456 Performance Monitoring (PM) is a key aspect of Operations,\n Administration, and Maintenance (OAM). It allows network operators\n to verify the Service Level Agreement (SLA) provided to customers and\n to detect network anomalies. This document specifies mechanisms for\n Loss Measurement and Delay Measurement in Transparent Interconnection\n of Lots of Links (TRILL) networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht 7456 delivery http key license subject timestamp trust nested-reference unchanged"},{"id":"IEEE IEEE 1588-2002","type":"specification","body":"IEEE","designation":"IEEE 1588-2002","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1588-2002.html","download_urls":["https://standards.ieee.org/standard/1588-2002.html"],"folder":"IEEE/IEEE-1588-2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null}],"search_text":"IEEE IEEE 1588-2002 nested-reference unavailable"},{"id":"IEEE IEEE 1588-2002.","type":"specification","body":"IEEE","designation":"IEEE 1588-2002.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1588-2002..html","download_urls":["https://standards.ieee.org/standard/1588-2002..html"],"folder":"IEEE/IEEE-1588-2002.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null}],"search_text":"IEEE IEEE 1588-2002. nested-reference unavailable"},{"id":"IEEE IEEE 1588-2008","type":"specification","body":"IEEE","designation":"IEEE 1588-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1588-2008.html","download_urls":["https://standards.ieee.org/standard/1588-2008.html"],"folder":"IEEE/IEEE-1588-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null}],"search_text":"IEEE IEEE 1588-2008 nested-reference unavailable"},{"id":"IETF RFC 7821","type":"specification","body":"IETF","designation":"RFC 7821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7821.txt","https://www.rfc-editor.org/rfc/rfc7821.pdf"],"folder":"IETF/RFC-7821","files":{"txt":{"path":"standards/IETF/RFC-7821/RFC-7821.txt","sha256":"ba100f3e2dc7f92724a9fc324d0b981c152d5bddccbbd07e4360ab1bb5a030c1"}},"tags":["nested-reference","unchanged"],"summary":"The Network Time Protocol (NTP) allows clients to synchronize to a\n time server using timestamped protocol messages. To facilitate\n accurate timestamping, some implementations use hardware-based\n timestamping engines that integrate the accurate transmission time\n into every outgoing NTP packet during transmission. Since these\n packets are transported over UDP, the UDP Checksum field is then\n updated to reflect this modification. This document proposes an\n extension field that includes a 2-octet Checksum Complement, allowing\n timestamping engines to reflect the checksum modification in the last\n 2 octets of the packet rather than in the UDP Checksum field. The\n behavior defined in this document is interoperable with existing NTP\n implementations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementa","scope_keywords":["7821","authentication","http","license","path","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null}],"search_text":"IETF RFC 7821 The Network Time Protocol (NTP) allows clients to synchronize to a\n time server using timestamped protocol messages. To facilitate\n accurate timestamping, some implementations use hardware-based\n timestamping engines that integrate the accurate transmission time\n into every outgoing NTP packet during transmission. Since these\n packets are transported over UDP, the UDP Checksum field is then\n updated to reflect this modification. This document proposes an\n extension field that includes a 2-octet Checksum Complement, allowing\n timestamping engines to reflect the checksum modification in the last\n 2 octets of the packet rather than in the UDP Checksum field. The\n behavior defined in this document is interoperable with existing NTP\n implementations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementa 7821 authentication http license path subject timestamp trust nested-reference unchanged"},{"id":"IEEE IEEE 1621","type":"specification","body":"IEEE","designation":"IEEE 1621","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1621.html","download_urls":["https://standards.ieee.org/standard/1621.html"],"folder":"IEEE/IEEE-1621","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null}],"search_text":"IEEE IEEE 1621 nested-reference unavailable"},{"id":"IETF RFC 7326","type":"specification","body":"IETF","designation":"RFC 7326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7326.txt","https://www.rfc-editor.org/rfc/rfc7326.pdf"],"folder":"IETF/RFC-7326","files":{"txt":{"path":"standards/IETF/RFC-7326/RFC-7326.txt","sha256":"1a295c2e2ee7564de8061167f75660ae9d80cabc8a7ad44254e781a2cb22067c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for Energy Management (EMAN) for\n devices and device components within, or connected to, communication\n networks. The framework presents a physical reference model and\n information model. The information model consists of an Energy\n Management Domain as a set of Energy Objects. Each Energy Object can\n be attributed with identity, classification, and context. Energy\n Objects can be monitored and controlled with respect to power, Power\n State, energy, demand, Power Attributes, and battery. Additionally,\n the framework models relationships and capabilities between Energy\n Objects.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ","scope_keywords":["7326","attribute","attributes","http","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 7326 This document defines a framework for Energy Management (EMAN) for\n devices and device components within, or connected to, communication\n networks. The framework presents a physical reference model and\n information model. The information model consists of an Energy\n Management Domain as a set of Energy Objects. Each Energy Object can\n be attributed with identity, classification, and context. Energy\n Objects can be monitored and controlled with respect to power, Power\n State, energy, demand, Power Attributes, and battery. Additionally,\n the framework models relationships and capabilities between Energy\n Objects.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ 7326 attribute attributes http license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7460","type":"specification","body":"IETF","designation":"RFC 7460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7460.txt","https://www.rfc-editor.org/rfc/rfc7460.pdf"],"folder":"IETF/RFC-7460","files":{"txt":{"path":"standards/IETF/RFC-7460/RFC-7460.txt","sha256":"1ab8ab4ce1f02ac800696f216a29b03ea48dbb41db6f0007e89b8cea6ade4102"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a subset of the Management Information Base\n (MIB) for power and energy monitoring of devices.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7460.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Do","scope_keywords":["7460","attribute","attributes","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 7460 This document defines a subset of the Management Information Base\n (MIB) for power and energy monitoring of devices.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7460.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Do 7460 attribute attributes http key license management subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1621-2004","type":"specification","body":"IEEE","designation":"IEEE 1621-2004","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1621-2004.html","download_urls":["https://standards.ieee.org/standard/1621-2004.html"],"folder":"IEEE/IEEE-1621-2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null}],"search_text":"IEEE IEEE 1621-2004 nested-reference unavailable"},{"id":"IEEE IEEE 1722","type":"specification","body":"IEEE","designation":"IEEE 1722","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1722.html","download_urls":["https://standards.ieee.org/standard/1722.html"],"folder":"IEEE/IEEE-1722","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null}],"search_text":"IEEE IEEE 1722 nested-reference unavailable"},{"id":"IEEE IEEE 1901","type":"specification","body":"IEEE","designation":"IEEE 1901","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1901.html","download_urls":["https://standards.ieee.org/standard/1901.html"],"folder":"IEEE/IEEE-1901","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IEEE IEEE 1901 nested-reference unavailable"},{"id":"IETF RFC 6272","type":"specification","body":"IETF","designation":"RFC 6272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6272.txt","https://www.rfc-editor.org/rfc/rfc6272.pdf"],"folder":"IETF/RFC-6272","files":{"txt":{"path":"standards/IETF/RFC-6272/RFC-6272.txt","sha256":"2c171e4f2bc13052cb1686e653665fb00913a75ca507c4ee3b3af213022b8c49"}},"tags":["nested-reference","unchanged"],"summary":"This note identifies the key infrastructure protocols of the Internet\n Protocol Suite for use in the Smart Grid. The target audience is\n those people seeking guidance on how to construct an appropriate\n Internet Protocol Suite profile for the Smart Grid. In practice,\n such a profile would consist of selecting what is needed for Smart\n Grid deployment from the picture presented here.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information","scope_keywords":["6272","authentication","authorization","http","key","license","management","path","pki","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null}],"search_text":"IETF RFC 6272 This note identifies the key infrastructure protocols of the Internet\n Protocol Suite for use in the Smart Grid. The target audience is\n those people seeking guidance on how to construct an appropriate\n Internet Protocol Suite profile for the Smart Grid. In practice,\n such a profile would consist of selecting what is needed for Smart\n Grid deployment from the picture presented here.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information 6272 authentication authorization http key license management path pki profile subject trust nested-reference unchanged"},{"id":"IEEE IEEE 1988.","type":"specification","body":"IEEE","designation":"IEEE 1988.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/1988..html","download_urls":["https://standards.ieee.org/standard/1988..html"],"folder":"IEEE/IEEE-1988.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null}],"search_text":"IEEE IEEE 1988. nested-reference unavailable"},{"id":"IETF RFC 3385","type":"specification","body":"IETF","designation":"RFC 3385","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3385.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3385.txt","https://www.rfc-editor.org/rfc/rfc3385.pdf"],"folder":"IETF/RFC-3385","files":{"txt":{"path":"standards/IETF/RFC-3385/RFC-3385.txt","sha256":"75a5bbc18b87cfe2979983cd9638dfa0ffa72f72a2d2c544758845432d98e2d6"}},"tags":["nested-reference","unchanged"],"summary":"In this memo, we attempt to give some estimates for the probability\n of undetected errors to facilitate the selection of an error\n detection code for the Internet Protocol Small Computer System\n Interface (iSCSI).\n\n We will also attempt to compare Cyclic Redundancy Checks (CRCs) with\n other checksum forms (e.g., Fletcher, Adler, weighted checksums), as\n permitted by available data.\n\n1. Introduction\n\n Cyclic Redundancy Check (CRC) codes [Peterson] are shortened cyclic\n codes used for error detection. A number of CRC codes have been\n adopted in standards: ATM, IEC, IEEE, CCITT, IBM-SDLC, and more\n [Baicheva]. The most important expectation from this kind of code is\n a very low probability for undetected errors. The probability of\n undetected errors in such codes has been, and still is, subject to\n extensive studies that have included both analytical models and\n simulations. Those codes hav","scope_keywords":["3385","algorithm","algorithms","attribute","attributes","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 3385 In this memo, we attempt to give some estimates for the probability\n of undetected errors to facilitate the selection of an error\n detection code for the Internet Protocol Small Computer System\n Interface (iSCSI).\n\n We will also attempt to compare Cyclic Redundancy Checks (CRCs) with\n other checksum forms (e.g., Fletcher, Adler, weighted checksums), as\n permitted by available data.\n\n1. Introduction\n\n Cyclic Redundancy Check (CRC) codes [Peterson] are shortened cyclic\n codes used for error detection. A number of CRC codes have been\n adopted in standards: ATM, IEC, IEEE, CCITT, IBM-SDLC, and more\n [Baicheva]. The most important expectation from this kind of code is\n a very low probability for undetected errors. The probability of\n undetected errors in such codes has been, and still is, subject to\n extensive studies that have included both analytical models and\n simulations. Those codes hav 3385 algorithm algorithms attribute attributes subject nested-reference unchanged"},{"id":"IEEE IEEE 28","type":"specification","body":"IEEE","designation":"IEEE 28","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/28.html","download_urls":["https://standards.ieee.org/standard/28.html"],"folder":"IEEE/IEEE-28","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1993","folder":"IETF/RFC-1993","source":"IETF/RFC-1993/RFC-1993.txt","version":null}],"search_text":"IEEE IEEE 28 nested-reference unavailable"},{"id":"IETF RFC 1993","type":"specification","body":"IETF","designation":"RFC 1993","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1993.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1993.txt","https://www.rfc-editor.org/rfc/rfc1993.pdf"],"folder":"IETF/RFC-1993","files":{"txt":{"path":"standards/IETF/RFC-1993/RFC-1993.txt","sha256":"0f3704966dffa406bf6f502ebf2c4c349a1c33e087e20f7b96f37e01244f765d"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Gandalf FZA data compression\n algorithm [3] for compressing PPP encapsulated packets.","scope_keywords":["1993","algorithm","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null}],"search_text":"IETF RFC 1993 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Gandalf FZA data compression\n algorithm [3] for compressing PPP encapsulated packets. 1993 algorithm license nested-reference unchanged"},{"id":"IEEE IEEE 3","type":"specification","body":"IEEE","designation":"IEEE 3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/3.html","download_urls":["https://standards.ieee.org/standard/3.html"],"folder":"IEEE/IEEE-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null}],"search_text":"IEEE IEEE 3 nested-reference unavailable"},{"id":"IETF RFC 6819","type":"specification","body":"IETF","designation":"RFC 6819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6819.txt","https://www.rfc-editor.org/rfc/rfc6819.pdf"],"folder":"IETF/RFC-6819","files":{"txt":{"path":"standards/IETF/RFC-6819/RFC-6819.txt","sha256":"7130b62c2861e8f8a7a28aa1af9d12b6dd49e9f1353f51a84314026fbcf9dd08"}},"tags":["nested-reference","unchanged"],"summary":"This document gives additional security considerations for OAuth,\n beyond those in the OAuth 2.0 specification, based on a comprehensive\n threat model for the OAuth 2.0 protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6819.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and th","scope_keywords":["6819","authorization","credential","credentials","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 6819 This document gives additional security considerations for OAuth,\n beyond those in the OAuth 2.0 specification, based on a comprehensive\n threat model for the OAuth 2.0 protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6819.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and th 6819 authorization credential credentials http license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 33","type":"specification","body":"IEEE","designation":"IEEE 33","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/33.html","download_urls":["https://standards.ieee.org/standard/33.html"],"folder":"IEEE/IEEE-33","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null}],"search_text":"IEEE IEEE 33 nested-reference unavailable"},{"id":"IETF RFC 8937","type":"specification","body":"IETF","designation":"RFC 8937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8937.txt","https://www.rfc-editor.org/rfc/rfc8937.pdf"],"folder":"IETF/RFC-8937","files":{"pdf":{"path":"standards/IETF/RFC-8937/RFC-8937.pdf","sha256":"097119c46b783560ac6c857c93afdfe30cddef5ce2ce398c2a441b2a2e334de4"},"txt":{"path":"standards/IETF/RFC-8937/RFC-8937.txt","sha256":"a017b113aefaa8e7e4f17ea2e2b2575ec2a89b90a1d1abd8ec290a004919481a"}},"tags":["nested-reference","unchanged"],"summary":"Randomness is a crucial ingredient for Transport Layer Security (TLS)\n and related security protocols. Weak or predictable\n \"cryptographically secure\" pseudorandom number generators (CSPRNGs)\n can be abused or exploited for malicious purposes. An initial\n entropy source that seeds a CSPRNG might be weak or broken as well,\n which can also lead to critical and systemic security problems. This\n document describes a way for security protocol implementations to\n augment their CSPRNGs using long-term private keys. This improves\n randomness from broken or otherwise subverted CSPRNGs.\n\n This document is a product of the Crypto Forum Research Group (CFRG)\n in the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the re","scope_keywords":["8937","algorithm","hash","http","https","key","keys","license","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 8937 Randomness is a crucial ingredient for Transport Layer Security (TLS)\n and related security protocols. Weak or predictable\n \"cryptographically secure\" pseudorandom number generators (CSPRNGs)\n can be abused or exploited for malicious purposes. An initial\n entropy source that seeds a CSPRNG might be weak or broken as well,\n which can also lead to critical and systemic security problems. This\n document describes a way for security protocol implementations to\n augment their CSPRNGs using long-term private keys. This improves\n randomness from broken or otherwise subverted CSPRNGs.\n\n This document is a product of the Crypto Forum Research Group (CFRG)\n in the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the re 8937 algorithm hash http https key keys license signature subject tls trust nested-reference unchanged"},{"id":"IEEE IEEE 48","type":"specification","body":"IEEE","designation":"IEEE 48","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/48.html","download_urls":["https://standards.ieee.org/standard/48.html"],"folder":"IEEE/IEEE-48","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null}],"search_text":"IEEE IEEE 48 nested-reference unavailable"},{"id":"IETF RFC 2373","type":"specification","body":"IETF","designation":"RFC 2373","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2373.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2373.txt","https://www.rfc-editor.org/rfc/rfc2373.pdf"],"folder":"IETF/RFC-2373","files":{"txt":{"path":"standards/IETF/RFC-2373/RFC-2373.txt","sha256":"ce445bc8fb3db984c050170699ba78b987ac83a9b7c5f7e027b471d6370615ae"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the addressing architecture of the IP\n Version 6 protocol [IPV6]. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses.","scope_keywords":["2373","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2526","folder":"IETF/RFC-2526","source":"IETF/RFC-2526/RFC-2526.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2546","folder":"IETF/RFC-2546","source":"IETF/RFC-2546/RFC-2546.txt","version":null},{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2723","folder":"IETF/RFC-2723","source":"IETF/RFC-2723/RFC-2723.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2732","folder":"IETF/RFC-2732","source":"IETF/RFC-2732/RFC-2732.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2373 This specification defines the addressing architecture of the IP\n Version 6 protocol [IPV6]. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses. 2373 key presentation nested-reference unchanged"},{"id":"IETF RFC 2374","type":"specification","body":"IETF","designation":"RFC 2374","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2374.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2374.txt","https://www.rfc-editor.org/rfc/rfc2374.pdf"],"folder":"IETF/RFC-2374","files":{"txt":{"path":"standards/IETF/RFC-2374/RFC-2374.txt","sha256":"5b5942ee7346fd90424f6098cdbac46ddabb892685a829669d372e414b743266"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 2374 Nokia\nObsoletes: 2073 M. O'Dell\nCategory: Standards Track UUNET\n S. Deering\n Cisco\n July 1998\n\n An IPv6 Aggregatable Global Unicast Address Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document defines an IPv6 aggregatable global unicast address\n format for use in the Internet. The address format defined in this\n document is consistent with the IPv6 Protocol [IPV6] and the \"IPv6\n Addressing Architecture\"","scope_keywords":["2374","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 2770","folder":"IETF/RFC-2770","source":"IETF/RFC-2770/RFC-2770.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3587","folder":"IETF/RFC-3587","source":"IETF/RFC-3587/RFC-3587.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null}],"search_text":"IETF RFC 2374 Network Working Group R. Hinden\nRequest for Comments: 2374 Nokia\nObsoletes: 2073 M. O'Dell\nCategory: Standards Track UUNET\n S. Deering\n Cisco\n July 1998\n\n An IPv6 Aggregatable Global Unicast Address Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document defines an IPv6 aggregatable global unicast address\n format for use in the Internet. The address format defined in this\n document is consistent with the IPv6 Protocol [IPV6] and the \"IPv6\n Addressing Architecture\" 2374 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3513","type":"specification","body":"IETF","designation":"RFC 3513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3513.txt","https://www.rfc-editor.org/rfc/rfc3513.pdf"],"folder":"IETF/RFC-3513","files":{"txt":{"path":"standards/IETF/RFC-3513/RFC-3513.txt","sha256":"5bb3ddde94a4699319f782fd969e42448483065be80163a4c4a20e25e68cb4be"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the addressing architecture of the IP\n Version 6 (IPv6) protocol. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses.\n\nHinden & Deering Standards Track [Page 1]\n\f\nRFC 3513 IPv6 Addressing Architecture April 2003","scope_keywords":["3513","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3587","folder":"IETF/RFC-3587","source":"IETF/RFC-3587/RFC-3587.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3627","folder":"IETF/RFC-3627","source":"IETF/RFC-3627/RFC-3627.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3769","folder":"IETF/RFC-3769","source":"IETF/RFC-3769/RFC-3769.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3849","folder":"IETF/RFC-3849","source":"IETF/RFC-3849/RFC-3849.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3956","folder":"IETF/RFC-3956","source":"IETF/RFC-3956/RFC-3956.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4012","folder":"IETF/RFC-4012","source":"IETF/RFC-4012/RFC-4012.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4219","folder":"IETF/RFC-4219","source":"IETF/RFC-4219/RFC-4219.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 3513 This specification defines the addressing architecture of the IP\n Version 6 (IPv6) protocol. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses.\n\nHinden & Deering Standards Track [Page 1]\n\f\nRFC 3513 IPv6 Addressing Architecture April 2003 3513 identification presentation nested-reference unchanged"},{"id":"IEEE IEEE 48-","type":"specification","body":"IEEE","designation":"IEEE 48-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/48-.html","download_urls":["https://standards.ieee.org/standard/48-.html"],"folder":"IEEE/IEEE-48-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null}],"search_text":"IEEE IEEE 48- nested-reference unavailable"},{"id":"IETF RFC 2625","type":"specification","body":"IETF","designation":"RFC 2625","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2625.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2625.txt","https://www.rfc-editor.org/rfc/rfc2625.pdf"],"folder":"IETF/RFC-2625","files":{"txt":{"path":"standards/IETF/RFC-2625/RFC-2625.txt","sha256":"0144ef1d9acdee831cf3a3715c5e9377ab40be25443466d17a9f29ac0f218989"}},"tags":["nested-reference","unchanged"],"summary":"Fibre Channel (FC) is a high speed serial interface technology that\n supports several higher layer protocols including Small Computer\n System Interface (SCSI) and Internet Protocol(IP). Until now, SCSI\n has been the only widely used protocol over FC. Existing FC standards\n [3] do not adequately specify how IP packets may be transported over\n FC and how IP addresses are resolved to FC addresses. The purpose of\n this document is to specify a way of encapsulating IP and Address\n Resolution Protocol(ARP) over Fibre Channel and also to describe a\n mechanism(s) for IP address resolution.","scope_keywords":["2625","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null}],"search_text":"IETF RFC 2625 Fibre Channel (FC) is a high speed serial interface technology that\n supports several higher layer protocols including Small Computer\n System Interface (SCSI) and Internet Protocol(IP). Until now, SCSI\n has been the only widely used protocol over FC. Existing FC standards\n [3] do not adequately specify how IP packets may be transported over\n FC and how IP addresses are resolved to FC addresses. The purpose of\n this document is to specify a way of encapsulating IP and Address\n Resolution Protocol(ARP) over Fibre Channel and also to describe a\n mechanism(s) for IP address resolution. 2625 management validation nested-reference unchanged"},{"id":"IETF RFC 4291","type":"specification","body":"IETF","designation":"RFC 4291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4291.txt","https://www.rfc-editor.org/rfc/rfc4291.pdf"],"folder":"IETF/RFC-4291","files":{"txt":{"path":"standards/IETF/RFC-4291/RFC-4291.txt","sha256":"4d58dff6b432d5d524bf3a3b7f0337a4177fa65f92ed72f2a92e97b471de48b2"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the addressing architecture of the IP\n Version 6 (IPv6) protocol. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses.\n\n This document obsoletes RFC 3513, \"IP Version 6 Addressing\n Architecture\".\n\nHinden Standards Track [Page 1]\n\f\nRFC 4291 IPv6 Addressing Architecture February 2006","scope_keywords":["4291","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4692","folder":"IETF/RFC-4692","source":"IETF/RFC-4692/RFC-4692.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5498","folder":"IETF/RFC-5498","source":"IETF/RFC-5498/RFC-5498.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7346","folder":"IETF/RFC-7346","source":"IETF/RFC-7346/RFC-7346.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 4291 This specification defines the addressing architecture of the IP\n Version 6 (IPv6) protocol. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 node's required addresses.\n\n This document obsoletes RFC 3513, \"IP Version 6 Addressing\n Architecture\".\n\nHinden Standards Track [Page 1]\n\f\nRFC 4291 IPv6 Addressing Architecture February 2006 4291 identification presentation nested-reference unchanged"},{"id":"IETF RFC 4338","type":"specification","body":"IETF","designation":"RFC 4338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4338.txt","https://www.rfc-editor.org/rfc/rfc4338.pdf"],"folder":"IETF/RFC-4338","files":{"txt":{"path":"standards/IETF/RFC-4338/RFC-4338.txt","sha256":"2f5888ec24bf46fa41379fbcc893a9035abd728fbf565db207fdc3f3832511cf"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the way of encapsulating IPv6, IPv4, and\n Address Resolution Protocol (ARP) packets over Fibre Channel. This\n document also specifies the method of forming IPv6 link-local\n addresses and statelessly autoconfigured IPv6 addresses on Fibre\n Channel networks, and a mechanism to perform IPv4 address resolution\n over Fibre Channel networks.\n\n This document obsoletes RFC 2625 and RFC 3831.\n\nDeSanti, et al. Standards Track [Page 1]\n\f\nRFC 4338 IP over Fibre Channel January 2006","scope_keywords":["4338","key","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 4338 This document specifies the way of encapsulating IPv6, IPv4, and\n Address Resolution Protocol (ARP) packets over Fibre Channel. This\n document also specifies the method of forming IPv6 link-local\n addresses and statelessly autoconfigured IPv6 addresses on Fibre\n Channel networks, and a mechanism to perform IPv4 address resolution\n over Fibre Channel networks.\n\n This document obsoletes RFC 2625 and RFC 3831.\n\nDeSanti, et al. Standards Track [Page 1]\n\f\nRFC 4338 IP over Fibre Channel January 2006 4338 key management validation nested-reference unchanged"},{"id":"IETF RFC 8948","type":"specification","body":"IETF","designation":"RFC 8948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8948.txt","https://www.rfc-editor.org/rfc/rfc8948.pdf"],"folder":"IETF/RFC-8948","files":{"pdf":{"path":"standards/IETF/RFC-8948/RFC-8948.pdf","sha256":"1cb3c15fa557280d8b155ad56f0fa665c0e4f0e064f226728f763809e60072a3"},"txt":{"path":"standards/IETF/RFC-8948/RFC-8948.txt","sha256":"8243eae41445cfc04c473969531e56e03933bd96e23902ceb2917b7388da9e3c"}},"tags":["nested-reference","unchanged"],"summary":"The IEEE originally structured the 48-bit Media Access Control (MAC)\n address space in such a way that half of it was reserved for local\n use. In 2017, the IEEE published a new standard (IEEE Std 802c) with\n a new optional Structured Local Address Plan (SLAP). It specifies\n different assignment approaches in four specified regions of the\n local MAC address space.\n\n The IEEE is developing protocols to assign addresses (IEEE P802.1CQ).\n There is also work in the IETF on specifying a new mechanism that\n extends DHCPv6 operation to handle the local MAC address assignments.\n\n This document proposes extensions to DHCPv6 protocols to enable a\n DHCPv6 client or a DHCPv6 relay to indicate a preferred SLAP quadrant\n to the server so that the server may allocate MAC addresses in the\n quadrant requested by the relay or client. A new DHCPv6 option\n (QUAD) is defined for this purpose.\n\nStatus of This ","scope_keywords":["8948","http","https","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8948 The IEEE originally structured the 48-bit Media Access Control (MAC)\n address space in such a way that half of it was reserved for local\n use. In 2017, the IEEE published a new standard (IEEE Std 802c) with\n a new optional Structured Local Address Plan (SLAP). It specifies\n different assignment approaches in four specified regions of the\n local MAC address space.\n\n The IEEE is developing protocols to assign addresses (IEEE P802.1CQ).\n There is also work in the IETF on specifying a new mechanism that\n extends DHCPv6 operation to handle the local MAC address assignments.\n\n This document proposes extensions to DHCPv6 protocols to enable a\n DHCPv6 client or a DHCPv6 relay to indicate a preferred SLAP quadrant\n to the server so that the server may allocate MAC addresses in the\n quadrant requested by the relay or client. A new DHCPv6 option\n (QUAD) is defined for this purpose.\n\nStatus of This  8948 http https license presentation subject trust nested-reference unchanged"},{"id":"IEEE IEEE 61850","type":"specification","body":"IEEE","designation":"IEEE 61850","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/61850.html","download_urls":["https://standards.ieee.org/standard/61850.html"],"folder":"IEEE/IEEE-61850","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null}],"search_text":"IEEE IEEE 61850 nested-reference unavailable"},{"id":"IEEE IEEE 64-","type":"specification","body":"IEEE","designation":"IEEE 64-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/64-.html","download_urls":["https://standards.ieee.org/standard/64-.html"],"folder":"IEEE/IEEE-64-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IEEE IEEE 64- nested-reference unavailable"},{"id":"IETF RFC 4881","type":"specification","body":"IETF","designation":"RFC 4881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4881.txt","https://www.rfc-editor.org/rfc/rfc4881.pdf"],"folder":"IETF/RFC-4881","files":{"txt":{"path":"standards/IETF/RFC-4881/RFC-4881.txt","sha256":"530b9237ce560ecf67c11de809626280c18c90c599df633092c2d85e98a40c53"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv4 describes how a Mobile Node can perform IPv4-layer\n handoffs between subnets served by different Foreign Agents. In\n certain cases, the latency involved in these handoffs can be above\n the threshold required for the support of delay-sensitive or real-\n time services. The aim of this document is to present two methods to\n achieve low-latency Mobile IPv4 handoffs. In addition, a combination\n of these two methods is described. The described techniques allow\n greater support for real-time services on a Mobile IPv4 network by\n minimizing the period of time when a Mobile Node is unable to send or\n receive IPv4 packets due to the delay in the Mobile IPv4 Registration\n process.","scope_keywords":["4881","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null}],"search_text":"IETF RFC 4881 Mobile IPv4 describes how a Mobile Node can perform IPv4-layer\n handoffs between subnets served by different Foreign Agents. In\n certain cases, the latency involved in these handoffs can be above\n the threshold required for the support of delay-sensitive or real-\n time services. The aim of this document is to present two methods to\n achieve low-latency Mobile IPv4 handoffs. In addition, a combination\n of these two methods is described. The described techniques allow\n greater support for real-time services on a Mobile IPv4 network by\n minimizing the period of time when a Mobile Node is unable to send or\n receive IPv4 packets due to the delay in the Mobile IPv4 Registration\n process. 4881 trust nested-reference unchanged"},{"id":"IETF RFC 4919","type":"specification","body":"IETF","designation":"RFC 4919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4919.txt","https://www.rfc-editor.org/rfc/rfc4919.pdf"],"folder":"IETF/RFC-4919","files":{"txt":{"path":"standards/IETF/RFC-4919/RFC-4919.txt","sha256":"d52a05d64e2dbf50b2819c7078c95162c37501eb1106cf374346cbd2367829f5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the assumptions, problem statement, and goals\n for transmitting IP over IEEE 802.15.4 networks. The set of goals\n enumerated in this document form an initial set only.","scope_keywords":["4919","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5673","folder":"IETF/RFC-5673","source":"IETF/RFC-5673/RFC-5673.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null}],"search_text":"IETF RFC 4919 This document describes the assumptions, problem statement, and goals\n for transmitting IP over IEEE 802.15.4 networks. The set of goals\n enumerated in this document form an initial set only. 4919 management trust nested-reference unchanged"},{"id":"IETF RFC 4944","type":"specification","body":"IETF","designation":"RFC 4944","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4944.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4944.txt","https://www.rfc-editor.org/rfc/rfc4944.pdf"],"folder":"IETF/RFC-4944","files":{"txt":{"path":"standards/IETF/RFC-4944/RFC-4944.txt","sha256":"2a1d639aa85e37d860f4c1e535865cdcc3dfc9f48518a2fcc922b3b18ce78c63"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on IEEE 802.15.4 networks.\n Additional specifications include a simple header compression scheme\n using shared context and provisions for packet delivery in IEEE\n 802.15.4 meshes.\n\nMontenegro, et al. Standards Track [Page 1]\n\f\nRFC 4944 IPv6 over IEEE 802.15.4 September 2007","scope_keywords":["4944","delivery","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null}],"search_text":"IETF RFC 4944 This document describes the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on IEEE 802.15.4 networks.\n Additional specifications include a simple header compression scheme\n using shared context and provisions for packet delivery in IEEE\n 802.15.4 meshes.\n\nMontenegro, et al. Standards Track [Page 1]\n\f\nRFC 4944 IPv6 over IEEE 802.15.4 September 2007 4944 delivery encryption key nested-reference unchanged"},{"id":"IETF RFC 7721","type":"specification","body":"IETF","designation":"RFC 7721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7721.txt","https://www.rfc-editor.org/rfc/rfc7721.pdf"],"folder":"IETF/RFC-7721","files":{"txt":{"path":"standards/IETF/RFC-7721/RFC-7721.txt","sha256":"912e018bd148cd8550efd371fbc7b451a07ad120665dd8ab91696d84733f1311"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses privacy and security considerations for\n several IPv6 address generation mechanisms, both standardized and\n non-standardized. It evaluates how different mechanisms mitigate\n different threats and the trade-offs that implementors, developers,\n and users face in choosing different addresses or address generation\n mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this doc","scope_keywords":["7721","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7721 This document discusses privacy and security considerations for\n several IPv6 address generation mechanisms, both standardized and\n non-standardized. It evaluates how different mechanisms mitigate\n different threats and the trade-offs that implementors, developers,\n and users face in choosing different addresses or address generation\n mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this doc 7721 hash http license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 66","type":"specification","body":"IEEE","designation":"IEEE 66","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/66.html","download_urls":["https://standards.ieee.org/standard/66.html"],"folder":"IEEE/IEEE-66","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0919","folder":"IETF/RFC-0919","source":"IETF/RFC-0919/RFC-0919.txt","version":null},{"body":"IETF","designation":"RFC 0922","folder":"IETF/RFC-0922","source":"IETF/RFC-0922/RFC-0922.txt","version":null},{"body":"IETF","designation":"RFC 919","folder":"IETF/RFC-919","source":"IETF/RFC-919/RFC-919.txt","version":null},{"body":"IETF","designation":"RFC 922","folder":"IETF/RFC-922","source":"IETF/RFC-922/RFC-922.txt","version":null}],"search_text":"IEEE IEEE 66 nested-reference unavailable"},{"id":"IETF RFC 0919","type":"specification","body":"IETF","designation":"RFC 0919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0919.txt","https://www.rfc-editor.org/rfc/rfc0919.pdf"],"folder":"IETF/RFC-0919","files":{"txt":{"path":"standards/IETF/RFC-0919/RFC-0919.txt","sha256":"37d6bdb202cd4336e0922b862dbcff0516cd0d7cfa5219d0109e16545b1df64e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jeffrey Mogul\nRequest for Comments: 919 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal is the result of discussion with several other people,\n especially J. Noel Chiappa and Christopher A. Kent, both of whom both\n pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting is not\n covered in the basic IP","scope_keywords":["0919","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null}],"search_text":"IETF RFC 0919 Network Working Group Jeffrey Mogul\nRequest for Comments: 919 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal is the result of discussion with several other people,\n especially J. Noel Chiappa and Christopher A. Kent, both of whom both\n pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting is not\n covered in the basic IP 0919 delivery management subject nested-reference unchanged"},{"id":"IETF RFC 0922","type":"specification","body":"IETF","designation":"RFC 0922","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0922.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0922.txt","https://www.rfc-editor.org/rfc/rfc0922.pdf"],"folder":"IETF/RFC-0922","files":{"txt":{"path":"standards/IETF/RFC-0922/RFC-0922.txt","sha256":"d2d83fc30008c551e4794816aa23311abb383425704b71cd1dfed5ee0783bee0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jeffrey Mogul\nRequest for Comments: 922 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS IN THE PRESENCE OF SUBNETS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal here is the result of discussion with several other\n people, especially J. Noel Chiappa and Christopher A. Kent, both of\n whom both pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting","scope_keywords":["0922","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null}],"search_text":"IETF RFC 0922 Network Working Group Jeffrey Mogul\nRequest for Comments: 922 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS IN THE PRESENCE OF SUBNETS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal here is the result of discussion with several other\n people, especially J. Noel Chiappa and Christopher A. Kent, both of\n whom both pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting 0922 delivery management subject nested-reference unchanged"},{"id":"IETF RFC 919","type":"specification","body":"IETF","designation":"RFC 919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc919.txt","https://www.rfc-editor.org/rfc/rfc919.pdf"],"folder":"IETF/RFC-919","files":{"txt":{"path":"standards/IETF/RFC-919/RFC-919.txt","sha256":"37d6bdb202cd4336e0922b862dbcff0516cd0d7cfa5219d0109e16545b1df64e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jeffrey Mogul\nRequest for Comments: 919 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal is the result of discussion with several other people,\n especially J. Noel Chiappa and Christopher A. Kent, both of whom both\n pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting is not\n covered in the basic IP","scope_keywords":["919","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0919","folder":"IETF/RFC-0919","source":"IETF/RFC-0919/RFC-0919.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 919 Network Working Group Jeffrey Mogul\nRequest for Comments: 919 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal is the result of discussion with several other people,\n especially J. Noel Chiappa and Christopher A. Kent, both of whom both\n pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting is not\n covered in the basic IP 919 delivery management subject nested-reference unchanged"},{"id":"IETF RFC 922","type":"specification","body":"IETF","designation":"RFC 922","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc922.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc922.txt","https://www.rfc-editor.org/rfc/rfc922.pdf"],"folder":"IETF/RFC-922","files":{"txt":{"path":"standards/IETF/RFC-922/RFC-922.txt","sha256":"d2d83fc30008c551e4794816aa23311abb383425704b71cd1dfed5ee0783bee0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jeffrey Mogul\nRequest for Comments: 922 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS IN THE PRESENCE OF SUBNETS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal here is the result of discussion with several other\n people, especially J. Noel Chiappa and Christopher A. Kent, both of\n whom both pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting","scope_keywords":["922","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0922","folder":"IETF/RFC-0922","source":"IETF/RFC-0922/RFC-0922.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1878","folder":"IETF/RFC-1878","source":"IETF/RFC-1878/RFC-1878.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 922 Network Working Group Jeffrey Mogul\nRequest for Comments: 922 Computer Science Department\n Stanford University\n October 1984\n\n BROADCASTING INTERNET DATAGRAMS IN THE PRESENCE OF SUBNETS\n\nStatus of this Memo\n\n We propose simple rules for broadcasting Internet datagrams on local\n networks that support broadcast, for addressing broadcasts, and for\n how gateways should handle them.\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nAcknowledgement\n\n This proposal here is the result of discussion with several other\n people, especially J. Noel Chiappa and Christopher A. Kent, both of\n whom both pointed me at important references.\n\n1. Introduction\n\n The use of broadcasts, especially on high-speed local area networks,\n is a good base for many applications. Since broadcasting 922 delivery management subject nested-reference unchanged"},{"id":"IEEE IEEE 754","type":"specification","body":"IEEE","designation":"IEEE 754","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754.html","download_urls":["https://standards.ieee.org/standard/754.html"],"folder":"IEEE/IEEE-754","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IEEE IEEE 754 nested-reference unavailable"},{"id":"IETF RFC 6397","type":"specification","body":"IETF","designation":"RFC 6397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6397.txt","https://www.rfc-editor.org/rfc/rfc6397.pdf"],"folder":"IETF/RFC-6397","files":{"txt":{"path":"standards/IETF/RFC-6397/RFC-6397.txt","sha256":"353a9f1c6866d8b1297a47c428eb2fa9783fc0409a671bafc0894aaabe1aa615"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the Multi-threaded Routing Toolkit (MRT) export\n format for Border Gateway Protocol (BGP) routing information by\n extending it to include optional terrestrial coordinates of a BGP\n collector and its BGP peers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6397.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. A","scope_keywords":["6397","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null}],"search_text":"IETF RFC 6397 This document updates the Multi-threaded Routing Toolkit (MRT) export\n format for Border Gateway Protocol (BGP) routing information by\n extending it to include optional terrestrial coordinates of a BGP\n collector and its BGP peers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6397.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. A 6397 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7285","type":"specification","body":"IETF","designation":"RFC 7285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7285.txt","https://www.rfc-editor.org/rfc/rfc7285.pdf"],"folder":"IETF/RFC-7285","files":{"txt":{"path":"standards/IETF/RFC-7285/RFC-7285.txt","sha256":"d951ad6acdd66b9882489c5d2f5e6f6a64f2abd9f858ed4a24e2b9db3cf117b5"}},"tags":["nested-reference","unchanged"],"summary":"Applications using the Internet already have access to some topology\n information of Internet Service Provider (ISP) networks. For\n example, views to Internet routing tables at Looking Glass servers\n are available and can be practically downloaded to many network\n application clients. What is missing is knowledge of the underlying\n network topologies from the point of view of ISPs. In other words,\n what an ISP prefers in terms of traffic optimization -- and a way to\n distribute it.\n\n The Application-Layer Traffic Optimization (ALTO) services defined in\n this document provide network information (e.g., basic network\n location structure and preferences of network paths) with the goal of\n modifying network resource consumption patterns while maintaining or\n improving application performance. The basic information of ALTO is\n based on abstract maps of a network. These maps provide a simplifi","scope_keywords":["7285","authentication","delivery","encryption","http","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 7285 Applications using the Internet already have access to some topology\n information of Internet Service Provider (ISP) networks. For\n example, views to Internet routing tables at Looking Glass servers\n are available and can be practically downloaded to many network\n application clients. What is missing is knowledge of the underlying\n network topologies from the point of view of ISPs. In other words,\n what an ISP prefers in terms of traffic optimization -- and a way to\n distribute it.\n\n The Application-Layer Traffic Optimization (ALTO) services defined in\n this document provide network information (e.g., basic network\n location structure and preferences of network paths) with the goal of\n modifying network resource consumption patterns while maintaining or\n improving application performance. The basic information of ALTO is\n based on abstract maps of a network. These maps provide a simplifi 7285 authentication delivery encryption http license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7493","type":"specification","body":"IETF","designation":"RFC 7493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7493.txt","https://www.rfc-editor.org/rfc/rfc7493.pdf"],"folder":"IETF/RFC-7493","files":{"txt":{"path":"standards/IETF/RFC-7493/RFC-7493.txt","sha256":"a44ccf1451a7bf4f4bbb78b39e10ed0e9a27ff2ee5b639c6458042b5a7197062"}},"tags":["nested-reference","unchanged"],"summary":"I-JSON (short for \"Internet JSON\") is a restricted profile of JSON\n designed to maximize interoperability and increase confidence that\n software can process it successfully with predictable results.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7493.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume","scope_keywords":["7493","http","key","license","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 7493 I-JSON (short for \"Internet JSON\") is a restricted profile of JSON\n designed to maximize interoperability and increase confidence that\n software can process it successfully with predictable results.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7493.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume 7493 http key license policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7950","type":"specification","body":"IETF","designation":"RFC 7950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7950.txt","https://www.rfc-editor.org/rfc/rfc7950.pdf"],"folder":"IETF/RFC-7950","files":{"txt":{"path":"standards/IETF/RFC-7950/RFC-7950.txt","sha256":"b71ae68e7aaff84a3321e1538a0cd788f549e4889ac375bf891f67cd8876908d"}},"tags":["nested-reference","unchanged"],"summary":"YANG is a data modeling language used to model configuration data,\n state data, Remote Procedure Calls, and notifications for network\n management protocols. This document describes the syntax and\n semantics of version 1.1 of the YANG language. YANG version 1.1 is a\n maintenance release of the YANG language, addressing ambiguities and\n defects in the original specification. There are a small number of\n backward incompatibilities from YANG version 1. This document also\n specifies the YANG mappings to the Network Configuration Protocol\n (NETCONF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Interne","scope_keywords":["7950","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7950 YANG is a data modeling language used to model configuration data,\n state data, Remote Procedure Calls, and notifications for network\n management protocols. This document describes the syntax and\n semantics of version 1.1 of the YANG language. YANG version 1.1 is a\n maintenance release of the YANG language, addressing ambiguities and\n defects in the original specification. There are a small number of\n backward incompatibilities from YANG version 1. This document also\n specifies the YANG mappings to the Network Configuration Protocol\n (NETCONF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Interne 7950 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8259","type":"specification","body":"IETF","designation":"RFC 8259","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8259.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8259.txt","https://www.rfc-editor.org/rfc/rfc8259.pdf"],"folder":"IETF/RFC-8259","files":{"txt":{"path":"standards/IETF/RFC-8259/RFC-8259.txt","sha256":"61a5378f4255c720beb2a4b4a63b29540147c140f36988bf086291989b4cd2d7"}},"tags":["nested-reference","unchanged"],"summary":"JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n This document removes inconsistencies with other specifications of\n JSON, repairs specification errors, and offers experience-based\n interoperability guidance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any ","scope_keywords":["8259","http","https","key","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 8259 JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n This document removes inconsistencies with other specifications of\n JSON, repairs specification errors, and offers experience-based\n interoperability guidance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any  8259 http https key license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8746","type":"specification","body":"IETF","designation":"RFC 8746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8746.txt","https://www.rfc-editor.org/rfc/rfc8746.pdf"],"folder":"IETF/RFC-8746","files":{"pdf":{"path":"standards/IETF/RFC-8746/RFC-8746.pdf","sha256":"7bc2a7b4f71770d305ed91371c3463ef6ec574edeb6ba50ad2a6fa023dcc9e06"},"txt":{"path":"standards/IETF/RFC-8746/RFC-8746.txt","sha256":"26d0f7d0ee9d2e7dedc382cff6ad1dfe74d25f28fb66b20157a3bbd78baf4fe8"}},"tags":["nested-reference","unchanged"],"summary":"The Concise Binary Object Representation (CBOR), as defined in RFC\n 7049, is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n This document makes use of this extensibility to define a number of\n CBOR tags for typed arrays of numeric data, as well as additional\n tags for multi-dimensional and homogeneous arrays. It is intended as\n the reference document for the IANA registration of the CBOR tags\n defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is","scope_keywords":["8746","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 8746 The Concise Binary Object Representation (CBOR), as defined in RFC\n 7049, is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n This document makes use of this extensibility to define a number of\n CBOR tags for typed arrays of numeric data, as well as additional\n tags for multi-dimensional and homogeneous arrays. It is intended as\n the reference document for the IANA registration of the CBOR tags\n defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is 8746 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8785","type":"specification","body":"IETF","designation":"RFC 8785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8785.txt","https://www.rfc-editor.org/rfc/rfc8785.pdf"],"folder":"IETF/RFC-8785","files":{"pdf":{"path":"standards/IETF/RFC-8785/RFC-8785.pdf","sha256":"1796e120ab220ede15bd88f3740c29f00ebd0d52bd39014aee0cd98b49b8a973"},"txt":{"path":"standards/IETF/RFC-8785/RFC-8785.txt","sha256":"63d52294eb0e3f0014174288186d388b4ddbf2c67d1ce8af1d9726eb0c3ab240"}},"tags":["nested-reference","unchanged"],"summary":"Cryptographic operations like hashing and signing need the data to be\n expressed in an invariant format so that the operations are reliably\n repeatable. One way to address this is to create a canonical\n representation of the data. Canonicalization also permits data to be\n exchanged in its original form on the \"wire\" while cryptographic\n operations performed on the canonicalized counterpart of the data in\n the producer and consumer endpoints generate consistent results.\n\n This document describes the JSON Canonicalization Scheme (JCS). This\n specification defines how to create a canonical representation of\n JSON data by building on the strict serialization methods for JSON\n primitives defined by ECMAScript, constraining JSON data to the\n Internet JSON (I-JSON) subset, and by using deterministic property\n sorting.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track speci","scope_keywords":["8785","hash","hashing","http","https","key","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 8785 Cryptographic operations like hashing and signing need the data to be\n expressed in an invariant format so that the operations are reliably\n repeatable. One way to address this is to create a canonical\n representation of the data. Canonicalization also permits data to be\n exchanged in its original form on the \"wire\" while cryptographic\n operations performed on the canonicalized counterpart of the data in\n the producer and consumer endpoints generate consistent results.\n\n This document describes the JSON Canonicalization Scheme (JCS). This\n specification defines how to create a canonical representation of\n JSON data by building on the strict serialization methods for JSON\n primitives defined by ECMAScript, constraining JSON data to the\n Internet JSON (I-JSON) subset, and by using deterministic property\n sorting.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track speci 8785 hash hashing http https key license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8941","type":"specification","body":"IETF","designation":"RFC 8941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8941.txt","https://www.rfc-editor.org/rfc/rfc8941.pdf"],"folder":"IETF/RFC-8941","files":{"pdf":{"path":"standards/IETF/RFC-8941/RFC-8941.pdf","sha256":"4572b01a5d837cc4e19bdadaf636a43cc18b221b02046fc3ddf86d84e7fe7651"},"txt":{"path":"standards/IETF/RFC-8941/RFC-8941.txt","sha256":"92e07becbe27974319d79de6195e72e25062b4193f68623e90ea4f7deaf33bb9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of data types and associated algorithms\n that are intended to make it easier and safer to define and handle\n HTTP header and trailer fields, known as \"Structured Fields\",\n \"Structured Headers\", or \"Structured Trailers\". It is intended for\n use by specifications of new HTTP fields that wish to use a common\n syntax that is more restrictive than traditional HTTP field values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedb","scope_keywords":["8941","algorithm","algorithms","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 8941 This document describes a set of data types and associated algorithms\n that are intended to make it easier and safer to define and handle\n HTTP header and trailer fields, known as \"Structured Fields\",\n \"Structured Headers\", or \"Structured Trailers\". It is intended for\n use by specifications of new HTTP fields that wish to use a common\n syntax that is more restrictive than traditional HTTP field values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedb 8941 algorithm algorithms http https key license presentation subject trust nested-reference unchanged"},{"id":"IEEE IEEE 754-1985","type":"specification","body":"IEEE","designation":"IEEE 754-1985","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754-1985.html","download_urls":["https://standards.ieee.org/standard/754-1985.html"],"folder":"IEEE/IEEE-754-1985","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null}],"search_text":"IEEE IEEE 754-1985 nested-reference unavailable"},{"id":"IETF RFC 2906","type":"specification","body":"IETF","designation":"RFC 2906","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2906.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2906.txt","https://www.rfc-editor.org/rfc/rfc2906.pdf"],"folder":"IETF/RFC-2906","files":{"txt":{"path":"standards/IETF/RFC-2906/RFC-2906.txt","sha256":"2c5228e909d7b3fc780129daaa7567b528cc087f0eebfd60eb6dd835509d613c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements that Authentication\n Authorization Accounting (AAA) protocols must meet in order to\n support authorization services in the Internet. The requirements have\n been elicited from a study of a range of applications including\n mobile-IP, roamops and others.\n\nFarrell, et al. Informational [Page 1]\n\f\nRFC 2906 AAA Authorization Requirements August 2000","scope_keywords":["2906","attribute","attributes","authentication","authorization","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2903","folder":"IETF/RFC-2903","source":"IETF/RFC-2903/RFC-2903.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null}],"search_text":"IETF RFC 2906 This document specifies the requirements that Authentication\n Authorization Accounting (AAA) protocols must meet in order to\n support authorization services in the Internet. The requirements have\n been elicited from a study of a range of applications including\n mobile-IP, roamops and others.\n\nFarrell, et al. Informational [Page 1]\n\f\nRFC 2906 AAA Authorization Requirements August 2000 2906 attribute attributes authentication authorization key trust nested-reference unchanged"},{"id":"IETF RFC 5976","type":"specification","body":"IETF","designation":"RFC 5976","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5976.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5976.txt","https://www.rfc-editor.org/rfc/rfc5976.pdf"],"folder":"IETF/RFC-5976","files":{"txt":{"path":"standards/IETF/RFC-5976/RFC-5976.txt","sha256":"e241d33ada3a89d489852845b7b42b8df07ad0e0a874b402ed0a7c9b7174e568"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a QoS-NSLP Quality-of-Service model (QOSM)\n based on ITU-T Recommendation Y.1541 Network QoS Classes and related\n guidance on signaling. Y.1541 specifies 8 classes of Network\n Performance objectives, and the Y.1541-QOSM extensions include\n additional QSPEC parameters and QOSM processing guidelines.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet S","scope_keywords":["5976","http","key","license","management","policy","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 5976 This document describes a QoS-NSLP Quality-of-Service model (QOSM)\n based on ITU-T Recommendation Y.1541 Network QoS Classes and related\n guidance on signaling. Y.1541 specifies 8 classes of Network\n Performance objectives, and the Y.1541-QOSM extensions include\n additional QSPEC parameters and QOSM processing guidelines.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet S 5976 http key license management policy subject trust tsp nested-reference unchanged"},{"id":"IEEE IEEE 754-2008","type":"specification","body":"IEEE","designation":"IEEE 754-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754-2008.html","download_urls":["https://standards.ieee.org/standard/754-2008.html"],"folder":"IEEE/IEEE-754-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null}],"search_text":"IEEE IEEE 754-2008 nested-reference unavailable"},{"id":"IETF RFC 6340","type":"specification","body":"IETF","designation":"RFC 6340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6340.txt","https://www.rfc-editor.org/rfc/rfc6340.pdf"],"folder":"IETF/RFC-6340","files":{"txt":{"path":"standards/IETF/RFC-6340/RFC-6340.txt","sha256":"4bed0b9b90fcdc2521b89fde1a6276f169427cb89a64b8a1037a6e084b2f931d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) module\n containing textual conventions (TCs) to represent floating-point\n numbers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6340.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions","scope_keywords":["6340","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null}],"search_text":"IETF RFC 6340 This memo defines a Management Information Base (MIB) module\n containing textual conventions (TCs) to represent floating-point\n numbers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6340.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions 6340 http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7159","type":"specification","body":"IETF","designation":"RFC 7159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7159.txt","https://www.rfc-editor.org/rfc/rfc7159.pdf"],"folder":"IETF/RFC-7159","files":{"txt":{"path":"standards/IETF/RFC-7159/RFC-7159.txt","sha256":"50aa72534210945457f5460a50f263c1d6cf87a3da8c814c1d9f54cb04f22342"}},"tags":["nested-reference","unchanged"],"summary":"JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n This document removes inconsistencies with other specifications of\n JSON, repairs specification errors, and offers experience-based\n interoperability guidance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any ","scope_keywords":["7159","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7396","folder":"IETF/RFC-7396","source":"IETF/RFC-7396/RFC-7396.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 7159 JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n This document removes inconsistencies with other specifications of\n JSON, repairs specification errors, and offers experience-based\n interoperability guidance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any  7159 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7951","type":"specification","body":"IETF","designation":"RFC 7951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7951.txt","https://www.rfc-editor.org/rfc/rfc7951.pdf"],"folder":"IETF/RFC-7951","files":{"txt":{"path":"standards/IETF/RFC-7951/RFC-7951.txt","sha256":"7cb8e9bb143548519d0d1068e02dbf004301ace17afc542edf331bde1791c343"}},"tags":["nested-reference","unchanged"],"summary":"This document defines encoding rules for representing configuration\n data, state data, parameters of Remote Procedure Call (RPC)\n operations or actions, and notifications defined using YANG as\n JavaScript Object Notation (JSON) text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7951.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors.","scope_keywords":["7951","http","key","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 7951 This document defines encoding rules for representing configuration\n data, state data, parameters of Remote Procedure Call (RPC)\n operations or actions, and notifications defined using YANG as\n JavaScript Object Notation (JSON) text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7951.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. 7951 http key license management profile subject trust nested-reference unchanged"},{"id":"IEEE IEEE 754-2008.","type":"specification","body":"IEEE","designation":"IEEE 754-2008.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754-2008..html","download_urls":["https://standards.ieee.org/standard/754-2008..html"],"folder":"IEEE/IEEE-754-2008.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null}],"search_text":"IEEE IEEE 754-2008. nested-reference unavailable"},{"id":"IETF RFC 8610","type":"specification","body":"IETF","designation":"RFC 8610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8610.txt","https://www.rfc-editor.org/rfc/rfc8610.pdf"],"folder":"IETF/RFC-8610","files":{"txt":{"path":"standards/IETF/RFC-8610/RFC-8610.txt","sha256":"3713f2a50e23a2bea0a6147ad6c4433605a00c3d00a868bfa86a42b204997089"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document proposes a notational convention to express Concise\n Binary Object Representation (CBOR) data structures (RFC 7049). Its\n main goal is to provide an easy and unambiguous way to express\n structures for protocol messages and data formats that use CBOR or\n JSON.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8610.\n\nBirkholz, et al. Standards Track [Page 1]\n\f\nRFC 8610 CDDL Ju","scope_keywords":["8610","http","https","license","presentation","subject","trust"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 8610 This document proposes a notational convention to express Concise\n Binary Object Representation (CBOR) data structures (RFC 7049). Its\n main goal is to provide an easy and unambiguous way to express\n structures for protocol messages and data formats that use CBOR or\n JSON.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8610.\n\nBirkholz, et al. Standards Track [Page 1]\n\f\nRFC 8610 CDDL Ju 8610 http https license presentation subject trust cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IEEE IEEE 754-2019","type":"specification","body":"IEEE","designation":"IEEE 754-2019","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754-2019.html","download_urls":["https://standards.ieee.org/standard/754-2019.html"],"folder":"IEEE/IEEE-754-2019","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IEEE IEEE 754-2019 nested-reference unavailable"},{"id":"IETF RFC 9562","type":"specification","body":"IETF","designation":"RFC 9562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9562.txt","https://www.rfc-editor.org/rfc/rfc9562.pdf"],"folder":"IETF/RFC-9562","files":{"pdf":{"path":"standards/IETF/RFC-9562/RFC-9562.pdf","sha256":"10db61467c7e297463c184536efe162d46be60746e01c044ec601281492387e8"},"txt":{"path":"standards/IETF/RFC-9562/RFC-9562.txt","sha256":"041870106b8701d9fa9261dcbc1679a6b7ab18cb179b37b69d7232431eac8042"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines UUIDs (Universally Unique IDentifiers) --\n also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform\n Resource Name namespace for UUIDs. A UUID is 128 bits long and is\n intended to guarantee uniqueness across space and time. UUIDs were\n originally used in the Apollo Network Computing System (NCS), later\n in the Open Software Foundation's (OSF's) Distributed Computing\n Environment (DCE), and then in Microsoft Windows platforms.\n\n This specification is derived from the OSF DCE specification with the\n kind permission of the OSF (now known as \"The Open Group\").\n Information from earlier versions of the OSF DCE specification have\n been incorporated into this document. This document obsoletes RFC\n 4122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen","scope_keywords":["9562","algorithm","hash","hashing","http","https","key","keys","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 9562 This specification defines UUIDs (Universally Unique IDentifiers) --\n also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform\n Resource Name namespace for UUIDs. A UUID is 128 bits long and is\n intended to guarantee uniqueness across space and time. UUIDs were\n originally used in the Apollo Network Computing System (NCS), later\n in the Open Software Foundation's (OSF's) Distributed Computing\n Environment (DCE), and then in Microsoft Windows platforms.\n\n This specification is derived from the OSF DCE specification with the\n kind permission of the OSF (now known as \"The Open Group\").\n Information from earlier versions of the OSF DCE specification have\n been incorporated into this document. This document obsoletes RFC\n 4122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen 9562 algorithm hash hashing http https key keys license subject timestamp trust nested-reference unchanged"},{"id":"IEEE IEEE 754.","type":"specification","body":"IEEE","designation":"IEEE 754.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/754..html","download_urls":["https://standards.ieee.org/standard/754..html"],"folder":"IEEE/IEEE-754.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IEEE IEEE 754. nested-reference unavailable"},{"id":"IEEE IEEE 78","type":"specification","body":"IEEE","designation":"IEEE 78","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/78.html","download_urls":["https://standards.ieee.org/standard/78.html"],"folder":"IEEE/IEEE-78","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null}],"search_text":"IEEE IEEE 78 nested-reference unavailable"},{"id":"IETF RFC 1120","type":"specification","body":"IETF","designation":"RFC 1120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1120.txt","https://www.rfc-editor.org/rfc/rfc1120.pdf"],"folder":"IETF/RFC-1120","files":{"txt":{"path":"standards/IETF/RFC-1120/RFC-1120.txt","sha256":"09ef5e105982e00362ebb4b82fcbce46cffeea9e077f6bb86e7872cfbf1513db"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1120 NRI\n September 1989\n\n The Internet Activities Board\n\nStatus of this Memo\n\n This RFC provides a history and description of the Internet\n Activities Board (IAB) and its subsidiary organizations. This memo\n is for informational use and does not constitute a standard.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA)\n initiated an effort to develop a technology which is now known as\n packet switching. This technology had its roots in message switching\n methods, but was strongly influenced by the development of low-cost\n minicomputers and digital telecommunications techniques during the\n mid-1960's [BARAN 64, ROBERTS 70, HEART 70, ROBERTS 78]. A very\n useful survey of this technology can be found in [IEEE 78].\n\n During the early 1970's, DARPA initiated a numbe","scope_keywords":["1120","archiving","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null}],"search_text":"IETF RFC 1120 Network Working Group V. Cerf\nRequest for Comments: 1120 NRI\n September 1989\n\n The Internet Activities Board\n\nStatus of this Memo\n\n This RFC provides a history and description of the Internet\n Activities Board (IAB) and its subsidiary organizations. This memo\n is for informational use and does not constitute a standard.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA)\n initiated an effort to develop a technology which is now known as\n packet switching. This technology had its roots in message switching\n methods, but was strongly influenced by the development of low-cost\n minicomputers and digital telecommunications techniques during the\n mid-1960's [BARAN 64, ROBERTS 70, HEART 70, ROBERTS 78]. A very\n useful survey of this technology can be found in [IEEE 78].\n\n During the early 1970's, DARPA initiated a numbe 1120 archiving key management nested-reference unchanged"},{"id":"IETF RFC 1160","type":"specification","body":"IETF","designation":"RFC 1160","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1160.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1160.txt","https://www.rfc-editor.org/rfc/rfc1160.pdf"],"folder":"IETF/RFC-1160","files":{"txt":{"path":"standards/IETF/RFC-1160/RFC-1160.txt","sha256":"57a016bbeeafdc3f82bba66f2541263e814500ba11262d4c62b97446e7ce5dbb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1160 NRI\nObsoletes: RFC 1120 May 1990\n\n The Internet Activities Board\n\nStatus of this Memo\n\n This RFC provides a history and description of the Internet\n Activities Board (IAB) and its subsidiary organizations. This memo\n is for informational use and does not constitute a standard. This is\n a revision of RFC 1120. Distribution of this memo is unlimited.\n\n1. Introduction\n\n In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA)\n initiated an effort to develop a technology which is now known as\n packet switching. This technology had its roots in message switching\n methods, but was strongly influenced by the development of low-cost\n minicomputers and digital telecommunications techniques during the\n mid-1960's [BARAN 64, ROBERTS 70, HEART 70, ROBERTS 78]. A very\n useful survey of this technology can be found in [IEEE 78].\n\n Dur","scope_keywords":["1160","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null}],"search_text":"IETF RFC 1160 Network Working Group V. Cerf\nRequest for Comments: 1160 NRI\nObsoletes: RFC 1120 May 1990\n\n The Internet Activities Board\n\nStatus of this Memo\n\n This RFC provides a history and description of the Internet\n Activities Board (IAB) and its subsidiary organizations. This memo\n is for informational use and does not constitute a standard. This is\n a revision of RFC 1120. Distribution of this memo is unlimited.\n\n1. Introduction\n\n In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA)\n initiated an effort to develop a technology which is now known as\n packet switching. This technology had its roots in message switching\n methods, but was strongly influenced by the development of low-cost\n minicomputers and digital telecommunications techniques during the\n mid-1960's [BARAN 64, ROBERTS 70, HEART 70, ROBERTS 78]. A very\n useful survey of this technology can be found in [IEEE 78].\n\n Dur 1160 key management policy nested-reference unchanged"},{"id":"IEEE IEEE 801.1","type":"specification","body":"IEEE","designation":"IEEE 801.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/801.1.html","download_urls":["https://standards.ieee.org/standard/801.1.html"],"folder":"IEEE/IEEE-801.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IEEE IEEE 801.1 nested-reference unavailable"},{"id":"IETF RFC 8519","type":"specification","body":"IETF","designation":"RFC 8519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8519.txt","https://www.rfc-editor.org/rfc/rfc8519.pdf"],"folder":"IETF/RFC-8519","files":{"txt":{"path":"standards/IETF/RFC-8519/RFC-8519.txt","sha256":"8168188c1243d859f170f404c87e1ee3c087e034d05bf62f3837770d73246d81"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a data model for Access Control Lists (ACLs).\n An ACL is a user-ordered set of rules used to configure the\n forwarding behavior in a device. Each rule is used to find a match\n on a packet and define actions that will be performed on the packet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8519.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons id","scope_keywords":["8519","http","https","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 8519 This document defines a data model for Access Control Lists (ACLs).\n An ACL is a user-ordered set of rules used to configure the\n forwarding behavior in a device. Each rule is used to find a match\n on a packet and define actions that will be performed on the packet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8519.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons id 8519 http https key license policy subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802","type":"specification","body":"IEEE","designation":"IEEE 802","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.html","download_urls":["https://standards.ieee.org/standard/802.html"],"folder":"IEEE/IEEE-802","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1009","folder":"IETF/RFC-1009","source":"IETF/RFC-1009/RFC-1009.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1083","folder":"IETF/RFC-1083","source":"IETF/RFC-1083/RFC-1083.txt","version":null},{"body":"IETF","designation":"RFC 1088","folder":"IETF/RFC-1088","source":"IETF/RFC-1088/RFC-1088.txt","version":null},{"body":"IETF","designation":"RFC 1089","folder":"IETF/RFC-1089","source":"IETF/RFC-1089/RFC-1089.txt","version":null},{"body":"IETF","designation":"RFC 1100","folder":"IETF/RFC-1100","source":"IETF/RFC-1100/RFC-1100.txt","version":null},{"body":"IETF","designation":"RFC 1103","folder":"IETF/RFC-1103","source":"IETF/RFC-1103/RFC-1103.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1118","folder":"IETF/RFC-1118","source":"IETF/RFC-1118/RFC-1118.txt","version":null},{"body":"IETF","designation":"RFC 1122","folder":"IETF/RFC-1122","source":"IETF/RFC-1122/RFC-1122.txt","version":null},{"body":"IETF","designation":"RFC 1132","folder":"IETF/RFC-1132","source":"IETF/RFC-1132/RFC-1132.txt","version":null},{"body":"IETF","designation":"RFC 1140","folder":"IETF/RFC-1140","source":"IETF/RFC-1140/RFC-1140.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.pdf","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1200","folder":"IETF/RFC-1200","source":"IETF/RFC-1200/RFC-1200.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1250","folder":"IETF/RFC-1250","source":"IETF/RFC-1250/RFC-1250.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1294","folder":"IETF/RFC-1294","source":"IETF/RFC-1294/RFC-1294.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1715","folder":"IETF/RFC-1715","source":"IETF/RFC-1715/RFC-1715.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 1897","folder":"IETF/RFC-1897","source":"IETF/RFC-1897/RFC-1897.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 1972","folder":"IETF/RFC-1972","source":"IETF/RFC-1972/RFC-1972.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2153","folder":"IETF/RFC-2153","source":"IETF/RFC-2153/RFC-2153.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2522","folder":"IETF/RFC-2522","source":"IETF/RFC-2522/RFC-2522.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 948","folder":"IETF/RFC-948","source":"IETF/RFC-948/RFC-948.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 985","folder":"IETF/RFC-985","source":"IETF/RFC-985/RFC-985.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IEEE IEEE 802 nested-reference unavailable"},{"id":"IETF RFC 0900","type":"specification","body":"IETF","designation":"RFC 0900","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0900.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0900.txt","https://www.rfc-editor.org/rfc/rfc0900.pdf"],"folder":"IETF/RFC-0900","files":{"txt":{"path":"standards/IETF/RFC-0900/RFC-0900.txt","sha256":"2f2f7c2bb2728d83291365bda894a44b0c8a58594421eeaf6b859d1239a1da9e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 900 J. Postel\n ISI\nObsoletes RFCs: 870, 820, June 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to receive a number assignment.\n\n Joyce Reynolds\n USC ","scope_keywords":["0900","identification","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0900 Network Working Group J. Reynolds\nRequest for Comments: 900 J. Postel\n ISI\nObsoletes RFCs: 870, 820, June 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to receive a number assignment.\n\n Joyce Reynolds\n USC  0900 identification risk nested-reference unchanged"},{"id":"IETF RFC 1009","type":"specification","body":"IETF","designation":"RFC 1009","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1009.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1009.txt","https://www.rfc-editor.org/rfc/rfc1009.pdf"],"folder":"IETF/RFC-1009","files":{"txt":{"path":"standards/IETF/RFC-1009/RFC-1009.txt","sha256":"3244485409fd4c02f54d04de034fbde4de2326b17e081721476b0134629856db"}},"tags":["nested-reference","unchanged"],"summary":"hardware may also be used (and may be required for future\n higher-throughput gateways).","scope_keywords":["1009","delivery","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1254","folder":"IETF/RFC-1254","source":"IETF/RFC-1254/RFC-1254.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2453","folder":"IETF/RFC-2453","source":"IETF/RFC-2453/RFC-2453.txt","version":null}],"search_text":"IETF RFC 1009 hardware may also be used (and may be required for future\n higher-throughput gateways). 1009 delivery policy nested-reference unchanged"},{"id":"IETF RFC 1011","type":"specification","body":"IETF","designation":"RFC 1011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1011.txt","https://www.rfc-editor.org/rfc/rfc1011.pdf"],"folder":"IETF/RFC-1011","files":{"txt":{"path":"standards/IETF/RFC-1011/RFC-1011.txt","sha256":"aea927018a79c23b697273d62b50dfcf698b738299323b647751c3bbca5c0de9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1011 J. Postel\n ISI\nObsoletes: RFCs 991, 961, 943, 924, 901, 880, 840 May 1987\n\n OFFICIAL INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those specified in the\n \"DDN Protocol Handbook\" (DPH), dated December 1985 (this is a three\n volume set with a total thickness of about 5 inches).\n\n Older collections that include many of these specifications are the\n \"Internet Protocol Transition Workbook\" (IPTW), dated March 1982; the\n \"Internet Mail Protocols\", dated November 1982; and the \"Internet\n Telnet Protocols and O","scope_keywords":["1011","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null}],"search_text":"IETF RFC 1011 Network Working Group J. Reynolds\nRequest for Comments: 1011 J. Postel\n ISI\nObsoletes: RFCs 991, 961, 943, 924, 901, 880, 840 May 1987\n\n OFFICIAL INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those specified in the\n \"DDN Protocol Handbook\" (DPH), dated December 1985 (this is a three\n volume set with a total thickness of about 5 inches).\n\n Older collections that include many of these specifications are the\n \"Internet Protocol Transition Workbook\" (IPTW), dated March 1982; the\n \"Internet Mail Protocols\", dated November 1982; and the \"Internet\n Telnet Protocols and O 1011 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1042","type":"specification","body":"IETF","designation":"RFC 1042","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1042.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1042.txt","https://www.rfc-editor.org/rfc/rfc1042.pdf"],"folder":"IETF/RFC-1042","files":{"txt":{"path":"standards/IETF/RFC-1042/RFC-1042.txt","sha256":"e8737abe7f7b80ae2e84b8cada0ea02d8cc3c4ad2414e902cc055e6953a01c55"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1042 J. Reynolds\n ISI\nObsoletes: RFC-948 February 1988\n\n A Standard for the Transmission of IP Datagrams over IEEE 802 Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating the Internet\n Protocol (IP) [1] datagrams and Address Resolution Protocol (ARP) [2]\n requests and replies on IEEE 802 Networks. This RFC specifies a\n protocol standard for the Internet community. Distribution of this\n memo is unlimited.\n\nAcknowledgment\n\n This memo would not exist with out the very significant contributions\n of Drew Perkins of Carnegie Mellon University, Jacob Rekhter of the\n T.J. Watson Research Center, IBM Corporation, and Joseph Cimmino of\n the University of Maryland.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting IP datagrams and ARP\n reque","scope_keywords":["1042"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1103","folder":"IETF/RFC-1103","source":"IETF/RFC-1103/RFC-1103.txt","version":null},{"body":"IETF","designation":"RFC 1132","folder":"IETF/RFC-1132","source":"IETF/RFC-1132/RFC-1132.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1042 Network Working Group J. Postel\nRequest for Comments: 1042 J. Reynolds\n ISI\nObsoletes: RFC-948 February 1988\n\n A Standard for the Transmission of IP Datagrams over IEEE 802 Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating the Internet\n Protocol (IP) [1] datagrams and Address Resolution Protocol (ARP) [2]\n requests and replies on IEEE 802 Networks. This RFC specifies a\n protocol standard for the Internet community. Distribution of this\n memo is unlimited.\n\nAcknowledgment\n\n This memo would not exist with out the very significant contributions\n of Drew Perkins of Carnegie Mellon University, Jacob Rekhter of the\n T.J. Watson Research Center, IBM Corporation, and Joseph Cimmino of\n the University of Maryland.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting IP datagrams and ARP\n reque 1042 nested-reference unchanged"},{"id":"IETF RFC 1083","type":"specification","body":"IETF","designation":"RFC 1083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1083.txt","https://www.rfc-editor.org/rfc/rfc1083.pdf"],"folder":"IETF/RFC-1083","files":{"txt":{"path":"standards/IETF/RFC-1083/RFC-1083.txt","sha256":"6939f874bf7d3ac8d706e4f24235ce13d2a83c9c744375f3f7f017fa4e665ceb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1083 December 1988\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n An overview of the standards procedures is presented first, followed\n by discussions of the standardization process and the RFC document\n series, then the explanation of the terms is presented, the lists of\n protocols in each stage of standardization follows, and finally\n pointers to references and contacts for further information.\n\n This memo is issued quarterly, please be sure the copy you are\n reading is dated within the last three months. Current copies may be\n obtained from the Network Information Center or from the Internet\n Assigned Numbers Authority (see the contact information at the end of\n this me","scope_keywords":["1083","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1100","folder":"IETF/RFC-1100","source":"IETF/RFC-1100/RFC-1100.txt","version":null}],"search_text":"IETF RFC 1083 Network Working Group Internet Activities Board\nRequest for Comments: 1083 December 1988\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n An overview of the standards procedures is presented first, followed\n by discussions of the standardization process and the RFC document\n series, then the explanation of the terms is presented, the lists of\n protocols in each stage of standardization follows, and finally\n pointers to references and contacts for further information.\n\n This memo is issued quarterly, please be sure the copy you are\n reading is dated within the last three months. Current copies may be\n obtained from the Network Information Center or from the Internet\n Assigned Numbers Authority (see the contact information at the end of\n this me 1083 policy nested-reference unchanged"},{"id":"IETF RFC 1088","type":"specification","body":"IETF","designation":"RFC 1088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1088.txt","https://www.rfc-editor.org/rfc/rfc1088.pdf"],"folder":"IETF/RFC-1088","files":{"txt":{"path":"standards/IETF/RFC-1088/RFC-1088.txt","sha256":"4348fad7ae36e4d990cd6a49d6b47ad33d6a4e1afb8c355a910a91311629c0de"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. McLaughlin III\nRequest for Comments: 1088 TWG\n February 1989\n\n A Standard for the Transmission of IP Datagrams over NetBIOS Networks\n\nStatus of this Memo\n\n This document specifies a standard method of encapsulating the\n Internet Protocol [1] (IP) datagrams on NetBIOS [2] networks.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting IP datagrams over\n NetBIOS networks.\n\n NetBIOS is a standard which specifies a means of creating virtual\n circuits and of transmitting and receiving point-to-point, multicast,\n and broadcast datagrams. This specification uses only the datagram\n services.\n\n Previous versions of this memo specified the use of the NetBIOS\n broadcast datagram services instead of the NetBIOS group name\n services to implement IP broadcasting. These ","scope_keywords":["1088","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1088 Network Working Group L. McLaughlin III\nRequest for Comments: 1088 TWG\n February 1989\n\n A Standard for the Transmission of IP Datagrams over NetBIOS Networks\n\nStatus of this Memo\n\n This document specifies a standard method of encapsulating the\n Internet Protocol [1] (IP) datagrams on NetBIOS [2] networks.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting IP datagrams over\n NetBIOS networks.\n\n NetBIOS is a standard which specifies a means of creating virtual\n circuits and of transmitting and receiving point-to-point, multicast,\n and broadcast datagrams. This specification uses only the datagram\n services.\n\n Previous versions of this memo specified the use of the NetBIOS\n broadcast datagram services instead of the NetBIOS group name\n services to implement IP broadcasting. These  1088 presentation nested-reference unchanged"},{"id":"IETF RFC 1089","type":"specification","body":"IETF","designation":"RFC 1089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1089.txt","https://www.rfc-editor.org/rfc/rfc1089.pdf"],"folder":"IETF/RFC-1089","files":{"txt":{"path":"standards/IETF/RFC-1089/RFC-1089.txt","sha256":"e8591c103dd77168e9efe8a55e7e2af77aae0d5afaa2a4b7cde356328e4637de"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Schoffstall\nRequest for Comments: 1089 Rensselaer Polytechnic Institute\n C. Davin\n MIT Laboratory for Computer Science\n M. Fedor\n NYSERNet, Inc.\n J. Case\n University of Tennessee at Knoxville\n February 1989\n\n SNMP over Ethernet\n\nStatus of This Memo\n\n This memo describes an experimental method by which the Simple\n Network Management Protocol (SNMP) as specified in [1] can be used\n over Ethernet MAC layer framing [2] instead of the Internet UDP/IP\n protocol stack. This specification is useful for LAN based network\n elements that support no higher layer protocols beyond the MAC sub-\n layer. Distribution of this memo is unlimited.\n\nOverview and Rational\n\n SNMP has been successful in managing Internet capable network\n elements which support the protocol stack at least through UDP the\n connectionless Internet transport layer protocol. As originally\n designed, SNMP is c","scope_keywords":["1089","conformity","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1419","folder":"IETF/RFC-1419","source":"IETF/RFC-1419/RFC-1419.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null}],"search_text":"IETF RFC 1089 Network Working Group M. Schoffstall\nRequest for Comments: 1089 Rensselaer Polytechnic Institute\n C. Davin\n MIT Laboratory for Computer Science\n M. Fedor\n NYSERNet, Inc.\n J. Case\n University of Tennessee at Knoxville\n February 1989\n\n SNMP over Ethernet\n\nStatus of This Memo\n\n This memo describes an experimental method by which the Simple\n Network Management Protocol (SNMP) as specified in [1] can be used\n over Ethernet MAC layer framing [2] instead of the Internet UDP/IP\n protocol stack. This specification is useful for LAN based network\n elements that support no higher layer protocols beyond the MAC sub-\n layer. Distribution of this memo is unlimited.\n\nOverview and Rational\n\n SNMP has been successful in managing Internet capable network\n elements which support the protocol stack at least through UDP the\n connectionless Internet transport layer protocol. As originally\n designed, SNMP is c 1089 conformity management nested-reference unchanged"},{"id":"IETF RFC 1100","type":"specification","body":"IETF","designation":"RFC 1100","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1100.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1100.txt","https://www.rfc-editor.org/rfc/rfc1100.pdf"],"folder":"IETF/RFC-1100","files":{"txt":{"path":"standards/IETF/RFC-1100/RFC-1100.txt","sha256":"40273529c868d9ecf9037e8ec64b9b4ae4b6f8a7f6612755d85f2d82bce82bcc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1100 April 1989\nObsoletes: RFC 1083\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n An overview of the standards procedures is presented first, followed\n by discussions of the standardization process and the RFC document\n series, then the explanation of the terms is presented, the lists of\n protocols in each stage of standardization follows, and finally\n pointers to references and contacts for further information.\n\n This memo is issued quarterly, please be sure the copy you are\n reading is dated within the last three months. Current copies may be\n obtained from the Network Information Center or from the Internet\n Assigned Numbers Authority (see the contact information at th","scope_keywords":["1100","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null}],"search_text":"IETF RFC 1100 Network Working Group Internet Activities Board\nRequest for Comments: 1100 April 1989\nObsoletes: RFC 1083\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n An overview of the standards procedures is presented first, followed\n by discussions of the standardization process and the RFC document\n series, then the explanation of the terms is presented, the lists of\n protocols in each stage of standardization follows, and finally\n pointers to references and contacts for further information.\n\n This memo is issued quarterly, please be sure the copy you are\n reading is dated within the last three months. Current copies may be\n obtained from the Network Information Center or from the Internet\n Assigned Numbers Authority (see the contact information at th 1100 policy nested-reference unchanged"},{"id":"IETF RFC 1103","type":"specification","body":"IETF","designation":"RFC 1103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1103.txt","https://www.rfc-editor.org/rfc/rfc1103.pdf"],"folder":"IETF/RFC-1103","files":{"txt":{"path":"standards/IETF/RFC-1103/RFC-1103.txt","sha256":"d9b3f90347b8ea2687a61ed7858a07a1ac8b0c7854eb55d56e1fe24cae124b3f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Katz\nRequest for Comments: 1103 Merit/NSFNET\n June 1989\n\n A Proposed Standard for the Transmission of\n IP Datagrams over FDDI Networks\n\nStatus of this Memo\n\n This RFC specifies a method of encapsulating the Internet Protocol\n (IP) [1] datagrams and Address Resolution Protocol (ARP) [2] requests\n and replies on Fiber Distributed Data Interface (FDDI) Networks.\n This RFC specifies a proposed protocol standard for the Internet\n community. Comments are welcome. Distribution of this memo is\n unlimited.\n\nAcknowledgment\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must\" or \"Mandatory\"--the item is an absolute requirement of the\n specification.\n\n \"Should","scope_keywords":["1103","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null}],"search_text":"IETF RFC 1103 Network Working Group D. Katz\nRequest for Comments: 1103 Merit/NSFNET\n June 1989\n\n A Proposed Standard for the Transmission of\n IP Datagrams over FDDI Networks\n\nStatus of this Memo\n\n This RFC specifies a method of encapsulating the Internet Protocol\n (IP) [1] datagrams and Address Resolution Protocol (ARP) [2] requests\n and replies on Fiber Distributed Data Interface (FDDI) Networks.\n This RFC specifies a proposed protocol standard for the Internet\n community. Comments are welcome. Distribution of this memo is\n unlimited.\n\nAcknowledgment\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must\" or \"Mandatory\"--the item is an absolute requirement of the\n specification.\n\n \"Should 1103 management nested-reference unchanged"},{"id":"IETF RFC 1109","type":"specification","body":"IETF","designation":"RFC 1109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1109.txt","https://www.rfc-editor.org/rfc/rfc1109.pdf"],"folder":"IETF/RFC-1109","files":{"txt":{"path":"standards/IETF/RFC-1109/RFC-1109.txt","sha256":"af7e85c264517ccf00579b66c557dbf2bf374c1d229a2c2c2295b849997f6ac2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1109 NRI\n August 1989\n\n Report of the Second Ad Hoc Network Management Review Group\n\nStatus of this Memo\n\n This RFC reports an official Internet Activities Board (IAB) policy\n position on the treatment of Network Management in the Internet. This\n RFC presents the results and recommendations of the second Ad Hoc\n Network Management Review on June 12, 1989. The results of the first\n such meeting were reported in RFC 1052 [1]. This report was approved\n and its recommendations adopted by the IAB as assembled on July 11-\n 13, 1989. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n On February 29, 1988, an Ad Hoc Network Management Review Group was\n convened to consider the state of network management technology for\n the Internet and to make recommendations to the Internet Activities\n Board as to network management policy. The outcome o","scope_keywords":["1109","authentication","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1155","folder":"IETF/RFC-1155","source":"IETF/RFC-1155/RFC-1155.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null}],"search_text":"IETF RFC 1109 Network Working Group V. Cerf\nRequest for Comments: 1109 NRI\n August 1989\n\n Report of the Second Ad Hoc Network Management Review Group\n\nStatus of this Memo\n\n This RFC reports an official Internet Activities Board (IAB) policy\n position on the treatment of Network Management in the Internet. This\n RFC presents the results and recommendations of the second Ad Hoc\n Network Management Review on June 12, 1989. The results of the first\n such meeting were reported in RFC 1052 [1]. This report was approved\n and its recommendations adopted by the IAB as assembled on July 11-\n 13, 1989. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n On February 29, 1988, an Ad Hoc Network Management Review Group was\n convened to consider the state of network management technology for\n the Internet and to make recommendations to the Internet Activities\n Board as to network management policy. The outcome o 1109 authentication key management policy nested-reference unchanged"},{"id":"IETF RFC 1118","type":"specification","body":"IETF","designation":"RFC 1118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1118.txt","https://www.rfc-editor.org/rfc/rfc1118.pdf"],"folder":"IETF/RFC-1118","files":{"txt":{"path":"standards/IETF/RFC-1118/RFC-1118.txt","sha256":"161fba8a31bf1873eb64e280f44f5fd6b2f44745bb400ce4dbc0c5e2d8207015"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Krol\nRequest for Comments: 1118 University of Illinois Urbana\n September 1989\n\n The Hitchhikers Guide to the Internet\n\nStatus of this Memo\n\n This RFC is being distributed to members of the Internet community in\n order to make available some \"hints\" which will allow new network\n participants to understand how the direction of the Internet is set,\n how to acquire online information and how to be a good Internet\n neighbor. While the information discussed may not be relevant to the\n research problems of the Internet, it may be interesting to a number\n of researchers and implementors. No standards are defined or\n specified in this memo. Distribution of this memo is unlimited.\n\nNOTICE:\n\n The hitchhikers guide to the Internet is a very unevenly edited memo\n and contains many passages which simply seemed to its editors like a\n good idea at the time. It is an indispensabl","scope_keywords":["1118"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null}],"search_text":"IETF RFC 1118 Network Working Group E. Krol\nRequest for Comments: 1118 University of Illinois Urbana\n September 1989\n\n The Hitchhikers Guide to the Internet\n\nStatus of this Memo\n\n This RFC is being distributed to members of the Internet community in\n order to make available some \"hints\" which will allow new network\n participants to understand how the direction of the Internet is set,\n how to acquire online information and how to be a good Internet\n neighbor. While the information discussed may not be relevant to the\n research problems of the Internet, it may be interesting to a number\n of researchers and implementors. No standards are defined or\n specified in this memo. Distribution of this memo is unlimited.\n\nNOTICE:\n\n The hitchhikers guide to the Internet is a very unevenly edited memo\n and contains many passages which simply seemed to its editors like a\n good idea at the time. It is an indispensabl 1118 nested-reference unchanged"},{"id":"IETF RFC 1122","type":"specification","body":"IETF","designation":"RFC 1122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1122.txt","https://www.rfc-editor.org/rfc/rfc1122.pdf"],"folder":"IETF/RFC-1122","files":{"txt":{"path":"standards/IETF/RFC-1122/RFC-1122.txt","sha256":"9f526e6bebc868324fedb90aebbcf6e5b15c53fd373ca5d5ce1c2cdcd264e04f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Engineering Task Force\nRequest for Comments: 1122 R. Braden, Editor\n October 1989\n\n Requirements for Internet Hosts -- Communication Layers\n\nStatus of This Memo\n\n This RFC is an official specification for the Internet community. It\n incorporates by reference, amends, corrects, and supplements the\n primary protocol standards documents relating to hosts. Distribution\n of this document is unlimited.\n\nSummary\n\n This is one RFC of a pair that defines and discusses the requirements\n for Internet host software. This RFC covers the communications\n protocol layers: link layer, IP layer, and transport layer; its\n companion RFC-1123 covers the application and support protocols.\n\n Table of Contents\n\n 1. INTRODUCTION ............................................... 5\n 1.1 The Internet Architecture .............................. 6\n 1.1.1 Internet Hosts ...................","scope_keywords":["1122","identification","management","timestamp","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1108","folder":"IETF/RFC-1108","source":"IETF/RFC-1108/RFC-1108.txt","version":null},{"body":"IETF","designation":"RFC 1145","folder":"IETF/RFC-1145","source":"IETF/RFC-1145/RFC-1145.txt","version":null},{"body":"IETF","designation":"RFC 1146","folder":"IETF/RFC-1146","source":"IETF/RFC-1146/RFC-1146.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1180","folder":"IETF/RFC-1180","source":"IETF/RFC-1180/RFC-1180.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1254","folder":"IETF/RFC-1254","source":"IETF/RFC-1254/RFC-1254.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1370","folder":"IETF/RFC-1370","source":"IETF/RFC-1370/RFC-1370.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1546","folder":"IETF/RFC-1546","source":"IETF/RFC-1546/RFC-1546.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1770","folder":"IETF/RFC-1770","source":"IETF/RFC-1770/RFC-1770.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 1937","folder":"IETF/RFC-1937","source":"IETF/RFC-1937/RFC-1937.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2001","folder":"IETF/RFC-2001","source":"IETF/RFC-2001/RFC-2001.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2075","folder":"IETF/RFC-2075","source":"IETF/RFC-2075/RFC-2075.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2309","folder":"IETF/RFC-2309","source":"IETF/RFC-2309/RFC-2309.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2555","folder":"IETF/RFC-2555","source":"IETF/RFC-2555/RFC-2555.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2678","folder":"IETF/RFC-2678","source":"IETF/RFC-2678/RFC-2678.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2988","folder":"IETF/RFC-2988","source":"IETF/RFC-2988/RFC-2988.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3081","folder":"IETF/RFC-3081","source":"IETF/RFC-3081/RFC-3081.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4943","folder":"IETF/RFC-4943","source":"IETF/RFC-4943/RFC-4943.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6419","folder":"IETF/RFC-6419","source":"IETF/RFC-6419/RFC-6419.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 1122 Network Working Group Internet Engineering Task Force\nRequest for Comments: 1122 R. Braden, Editor\n October 1989\n\n Requirements for Internet Hosts -- Communication Layers\n\nStatus of This Memo\n\n This RFC is an official specification for the Internet community. It\n incorporates by reference, amends, corrects, and supplements the\n primary protocol standards documents relating to hosts. Distribution\n of this document is unlimited.\n\nSummary\n\n This is one RFC of a pair that defines and discusses the requirements\n for Internet host software. This RFC covers the communications\n protocol layers: link layer, IP layer, and transport layer; its\n companion RFC-1123 covers the application and support protocols.\n\n Table of Contents\n\n 1. INTRODUCTION ............................................... 5\n 1.1 The Internet Architecture .............................. 6\n 1.1.1 Internet Hosts ................... 1122 identification management timestamp validation nested-reference unchanged"},{"id":"IETF RFC 1132","type":"specification","body":"IETF","designation":"RFC 1132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1132.txt","https://www.rfc-editor.org/rfc/rfc1132.pdf"],"folder":"IETF/RFC-1132","files":{"txt":{"path":"standards/IETF/RFC-1132/RFC-1132.txt","sha256":"9c97923e0006edb5e953844a573c3f225f111ab41a56414fb13dff56788bcc8c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. McLaughlin III\nRequest for Comments: 1132 The Wollongong Group\n November 1989\n\n A Standard for the Transmission of 802.2 Packets over IPX Networks\n\nStatus of this Memo\n\n This document specifies a standard method of encapsulating 802.2 [1]\n packets on networks supporting Novell's Internet Packet Exchange\n Protocol [2] (IPX). It obsoletes earlier documents detailing the\n transmission of Internet packets over IPX networks. It differs from\n these earlier documents in that it allows for the transmission of\n multiple network protocols over IPX and for the transmission of\n packets through IPX bridges. Distribution of this memo is unlimited.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting Internet packets such\n as the Internet Protocol [3] (IP) and Address Resolution Protocol [4]\n (ARP) as well as ","scope_keywords":["1132"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1132 Network Working Group L. McLaughlin III\nRequest for Comments: 1132 The Wollongong Group\n November 1989\n\n A Standard for the Transmission of 802.2 Packets over IPX Networks\n\nStatus of this Memo\n\n This document specifies a standard method of encapsulating 802.2 [1]\n packets on networks supporting Novell's Internet Packet Exchange\n Protocol [2] (IPX). It obsoletes earlier documents detailing the\n transmission of Internet packets over IPX networks. It differs from\n these earlier documents in that it allows for the transmission of\n multiple network protocols over IPX and for the transmission of\n packets through IPX bridges. Distribution of this memo is unlimited.\n\nIntroduction\n\n The goal of this specification is to allow compatible and\n interoperable implementations for transmitting Internet packets such\n as the Internet Protocol [3] (IP) and Address Resolution Protocol [4]\n (ARP) as well as  1132 nested-reference unchanged"},{"id":"IETF RFC 1140","type":"specification","body":"IETF","designation":"RFC 1140","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1140.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1140.txt","https://www.rfc-editor.org/rfc/rfc1140.pdf"],"folder":"IETF/RFC-1140","files":{"txt":{"path":"standards/IETF/RFC-1140/RFC-1140.txt","sha256":"aa7dadd9ae02b2515e228c16713a32e4d438688486fb668575e82b9e5a70c890"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1140 J. Postel, Editor\nObsoletes: RFCs 1130, May 1990\n 1100, 1083\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements . . . . . . . . ","scope_keywords":["1140"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null}],"search_text":"IETF RFC 1140 Network Working Group Internet Activities Board\nRequest for Comments: 1140 J. Postel, Editor\nObsoletes: RFCs 1130, May 1990\n 1100, 1083\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements . . . . . . . .  1140 nested-reference unchanged"},{"id":"IETF RFC 1142","type":"specification","body":"IETF","designation":"RFC 1142","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1142.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1142.txt","https://www.rfc-editor.org/rfc/rfc1142.pdf"],"folder":"IETF/RFC-1142","files":{"pdf":{"path":"standards/IETF/RFC-1142/RFC-1142.pdf","sha256":"87a00919dd935378461021080350a43e8f08f0ff5833f0f1525a31fef341559d"},"txt":{"path":"standards/IETF/RFC-1142/RFC-1142.txt","sha256":"b8693e5e991f6273f03c8e22cb08165e22b230b59846f59b0de489783a0c6852"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Oran, Editor\nRequest for Comments: 1142 Digital Equipment Corp.\n February 1990\n\n OSI IS-IS Intra-domain Routing Protocol\n \nStatus of this Memo\n\n This RFC is a republication of ISO DP 10589 as a service to the\n Internet community. This is not an Internet standard.\n Distribution of this memo is unlimited.\n \n\nNOTE: This is a bad ASCII version of this document. The official\ndocument is the PostScript file, which has the diagrams in place.\nPlease use the PostScript version of this memo.\n\nISO/IEC DIS 10589\n \nInformation technology Telecommunications and information exchange\nbetween systems Interme diate system to Intermediate system\nIntra-Domain routeing exchange protocol for use in Conjunction with\nthe Protocol for providing the Connectionless- mode Network Service\n(ISO 8473) Technologies de l'information Communication de donnies et\nichange d'information entre systhme","scope_keywords":["1142","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2966","folder":"IETF/RFC-2966","source":"IETF/RFC-2966/RFC-2966.txt","version":null},{"body":"IETF","designation":"RFC 3358","folder":"IETF/RFC-3358","source":"IETF/RFC-3358/RFC-3358.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null}],"search_text":"IETF RFC 1142 Network Working Group D. Oran, Editor\nRequest for Comments: 1142 Digital Equipment Corp.\n February 1990\n\n OSI IS-IS Intra-domain Routing Protocol\n \nStatus of this Memo\n\n This RFC is a republication of ISO DP 10589 as a service to the\n Internet community. This is not an Internet standard.\n Distribution of this memo is unlimited.\n \n\nNOTE: This is a bad ASCII version of this document. The official\ndocument is the PostScript file, which has the diagrams in place.\nPlease use the PostScript version of this memo.\n\nISO/IEC DIS 10589\n \nInformation technology Telecommunications and information exchange\nbetween systems Interme diate system to Intermediate system\nIntra-Domain routeing exchange protocol for use in Conjunction with\nthe Protocol for providing the Connectionless- mode Network Service\n(ISO 8473) Technologies de l'information Communication de donnies et\nichange d'information entre systhme 1142 management path subject nested-reference unchanged"},{"id":"IETF RFC 1147","type":"specification","body":"IETF","designation":"RFC 1147","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1147.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1147.txt","https://www.rfc-editor.org/rfc/rfc1147.pdf"],"folder":"IETF/RFC-1147","files":{"pdf":{"path":"standards/IETF/RFC-1147/RFC-1147.pdf","sha256":"ee0a62b5121162f6267957dce8de34f1fd9bb4d43b425cfc8956445b0c67d025"},"txt":{"path":"standards/IETF/RFC-1147/RFC-1147.txt","sha256":"72b39a2dd563c3636ea5d0d3b5b4f36d45aef383ec314ec152277ea5bc9ca268"}},"tags":["nested-reference","unchanged"],"summary":"The practice of re-inventing the wheel seems endemic to the\n field of data communications. The primary goal of this","scope_keywords":["1147","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 1147 The practice of re-inventing the wheel seems endemic to the\n field of data communications. The primary goal of this 1147 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 1175","type":"specification","body":"IETF","designation":"RFC 1175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1175.txt","https://www.rfc-editor.org/rfc/rfc1175.pdf"],"folder":"IETF/RFC-1175","files":{"txt":{"path":"standards/IETF/RFC-1175/RFC-1175.txt","sha256":"098fe0b95d738e78a9539286d20198cefdcd0d7484f149dcccd3991cf16b03ec"}},"tags":["nested-reference","unchanged"],"summary":"The intent of this bibliography is to offer a representative\n collection of resources of information that will help the reader\n become familiar with the concepts of internetworking. It is meant to\n be a starting place for further research. There are references to\n other sources of information for those users wishing to pursue, in\n greater depth, the issues and complexities of the current networking\n environment.\n\nUser Documents Working Group [Page i]\n\f\nRFC 1175 FYI - Bibliography August 1990","scope_keywords":["1175","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1463","folder":"IETF/RFC-1463","source":"IETF/RFC-1463/RFC-1463.txt","version":null}],"search_text":"IETF RFC 1175 The intent of this bibliography is to offer a representative\n collection of resources of information that will help the reader\n become familiar with the concepts of internetworking. It is meant to\n be a starting place for further research. There are references to\n other sources of information for those users wishing to pursue, in\n greater depth, the issues and complexities of the current networking\n environment.\n\nUser Documents Working Group [Page i]\n\f\nRFC 1175 FYI - Bibliography August 1990 1175 key nested-reference unchanged"},{"id":"IETF RFC 1177","type":"specification","body":"IETF","designation":"RFC 1177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1177.txt","https://www.rfc-editor.org/rfc/rfc1177.pdf"],"folder":"IETF/RFC-1177","files":{"txt":{"path":"standards/IETF/RFC-1177/RFC-1177.txt","sha256":"b8210772e7be5fe6d9823633f3ab753c77d1bf831d5471545cc4c058ee9e153a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1177 FTP Software, Inc.\nFYI: 4 A. Marine\n SRI\n J. Reynolds\n ISI\n August 1990\n\n FYI on Questions and Answers\n Answers to Commonly asked \"New Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of three FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group (USWG) of the\n Internet Engineering Task Force (IETF). The goal is to document the\n most commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.................................................... 1\n 2. Acknowledgements................................................ 2\n 3. Questions About the Internet.................................... 2\n 4. Questions About TCP/IP.","scope_keywords":["1177","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null}],"search_text":"IETF RFC 1177 Network Working Group G. Malkin\nRequest for Comments: 1177 FTP Software, Inc.\nFYI: 4 A. Marine\n SRI\n J. Reynolds\n ISI\n August 1990\n\n FYI on Questions and Answers\n Answers to Commonly asked \"New Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of three FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group (USWG) of the\n Internet Engineering Task Force (IETF). The goal is to document the\n most commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.................................................... 1\n 2. Acknowledgements................................................ 2\n 3. Questions About the Internet.................................... 2\n 4. Questions About TCP/IP. 1177 registered nested-reference unchanged"},{"id":"IETF RFC 1188","type":"specification","body":"IETF","designation":"RFC 1188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1188.txt","https://www.rfc-editor.org/rfc/rfc1188.pdf"],"folder":"IETF/RFC-1188","files":{"txt":{"path":"standards/IETF/RFC-1188/RFC-1188.txt","sha256":"48c1d4ae531a521fbe23f57962426ad079f5caf05fa681f31b1b05d28859176d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for the use of IP and ARP on FDDI\n networks. The encapsulation method used is described, as well as\n various media-specific issues.\n\nAcknowledgments\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute. The author would also like to acknowledge the\n contributions of the IP Over FDDI Working Group of the IETF, members\n of ANSI ASC X3T9.5, and others in the FDDI community.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must,\" \"Shall,\" or \"Mandatory\"--the item is an absolute\n requirement of the specification.\n\n \"Should\" or \"Recommended\"--the item should generally be followed\n for all but exceptional circumstances.\n\nKatz [Page 1]\n\f\nRFC 1188 IP and ARP on FDDI Networks October 1990\n\n \"May\" or \"Opti","scope_keywords":["1188","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1469","folder":"IETF/RFC-1469","source":"IETF/RFC-1469/RFC-1469.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1188 This document specifies a method for the use of IP and ARP on FDDI\n networks. The encapsulation method used is described, as well as\n various media-specific issues.\n\nAcknowledgments\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute. The author would also like to acknowledge the\n contributions of the IP Over FDDI Working Group of the IETF, members\n of ANSI ASC X3T9.5, and others in the FDDI community.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must,\" \"Shall,\" or \"Mandatory\"--the item is an absolute\n requirement of the specification.\n\n \"Should\" or \"Recommended\"--the item should generally be followed\n for all but exceptional circumstances.\n\nKatz [Page 1]\n\f\nRFC 1188 IP and ARP on FDDI Networks October 1990\n\n \"May\" or \"Opti 1188 management nested-reference unchanged"},{"id":"IETF RFC 1191","type":"specification","body":"IETF","designation":"RFC 1191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1191.txt","https://www.rfc-editor.org/rfc/rfc1191.pdf"],"folder":"IETF/RFC-1191","files":{"txt":{"path":"standards/IETF/RFC-1191/RFC-1191.txt","sha256":"3de7c2cb99832c6d1929f9f918172865831848f77e8ab585488125581afa6b68"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a technique for dynamically discovering the\n maximum transmission unit (MTU) of an arbitrary internet path. It\n specifies a small change to the way routers generate one type of ICMP\n message. For a path that passes through a router that has not been\n so changed, this technique might not discover the correct Path MTU,\n but it will always choose a Path MTU as accurate as, and in many\n cases more accurate than, the Path MTU that would be chosen by\n current practice.\n\nAcknowledgements\n\n This proposal is a product of the IETF MTU Discovery Working Group.\n\n The mechanism proposed here was first suggested by Geof Cooper [2],\n who in two short paragraphs set out all the basic ideas that took the\n Working Group months to reinvent.\n\n1. Introduction\n\n When one IP host has a large amount of data to send to another host,\n the data is transmitted as a series of IP datagrams. It is ","scope_keywords":["1191","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1435","folder":"IETF/RFC-1435","source":"IETF/RFC-1435/RFC-1435.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 1981","folder":"IETF/RFC-1981","source":"IETF/RFC-1981/RFC-1981.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2004","folder":"IETF/RFC-2004","source":"IETF/RFC-2004/RFC-2004.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2343","folder":"IETF/RFC-2343","source":"IETF/RFC-2343/RFC-2343.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2431","folder":"IETF/RFC-2431","source":"IETF/RFC-2431/RFC-2431.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2979","folder":"IETF/RFC-2979","source":"IETF/RFC-2979/RFC-2979.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 1191 This memo describes a technique for dynamically discovering the\n maximum transmission unit (MTU) of an arbitrary internet path. It\n specifies a small change to the way routers generate one type of ICMP\n message. For a path that passes through a router that has not been\n so changed, this technique might not discover the correct Path MTU,\n but it will always choose a Path MTU as accurate as, and in many\n cases more accurate than, the Path MTU that would be chosen by\n current practice.\n\nAcknowledgements\n\n This proposal is a product of the IETF MTU Discovery Working Group.\n\n The mechanism proposed here was first suggested by Geof Cooper [2],\n who in two short paragraphs set out all the basic ideas that took the\n Working Group months to reinvent.\n\n1. Introduction\n\n When one IP host has a large amount of data to send to another host,\n the data is transmitted as a series of IP datagrams. It is  1191 management path nested-reference unchanged"},{"id":"IETF RFC 1195","type":"specification","body":"IETF","designation":"RFC 1195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1195.txt","https://www.rfc-editor.org/rfc/rfc1195.pdf"],"folder":"IETF/RFC-1195","files":{"pdf":{"path":"standards/IETF/RFC-1195/RFC-1195.pdf","sha256":"24938211b319a23199ba9c5f021e9ee7feb50e8ef3ec495dafcd450b9b314522"},"txt":{"path":"standards/IETF/RFC-1195/RFC-1195.txt","sha256":"e8b95f5c24d95cbcc6da37985058a1fd27317dd6ad6c9eaf743a5fa202d8ed4b"}},"tags":["nested-reference","unchanged"],"summary":"This RFC specifies an integrated routing protocol, based on the OSI\n Intra-Domain IS-IS Routing Protocol, which may be used as an interior\n gateway protocol (IGP) to support TCP/IP as well as OSI. This allows\n a single routing protocol to be used to support pure IP environments,\n pure OSI environments, and dual environments. This specification was\n developed by the IS-IS working group of the Internet Engineering Task\n Force.\n\n The OSI IS-IS protocol has reached a mature state, and is ready for\n implementation and operational use. The most recent version of the\n OSI IS-IS protocol is contained in ISO DP 10589 [1]. The proposed\n standard for using IS-IS for support of TCP/IP will therefore make\n use of this version (with a minor bug correction, as discussed in\n Annex B). We expect that future versions of this proposed standard\n will upgrade to the final International Standard version of IS","scope_keywords":["1195","algorithm","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2966","folder":"IETF/RFC-2966","source":"IETF/RFC-2966/RFC-2966.txt","version":null},{"body":"IETF","designation":"RFC 3358","folder":"IETF/RFC-3358","source":"IETF/RFC-3358/RFC-3358.txt","version":null},{"body":"IETF","designation":"RFC 3359","folder":"IETF/RFC-3359","source":"IETF/RFC-3359/RFC-3359.txt","version":null},{"body":"IETF","designation":"RFC 3373","folder":"IETF/RFC-3373","source":"IETF/RFC-3373/RFC-3373.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null}],"search_text":"IETF RFC 1195 This RFC specifies an integrated routing protocol, based on the OSI\n Intra-Domain IS-IS Routing Protocol, which may be used as an interior\n gateway protocol (IGP) to support TCP/IP as well as OSI. This allows\n a single routing protocol to be used to support pure IP environments,\n pure OSI environments, and dual environments. This specification was\n developed by the IS-IS working group of the Internet Engineering Task\n Force.\n\n The OSI IS-IS protocol has reached a mature state, and is ready for\n implementation and operational use. The most recent version of the\n OSI IS-IS protocol is contained in ISO DP 10589 [1]. The proposed\n standard for using IS-IS for support of TCP/IP will therefore make\n use of this version (with a minor bug correction, as discussed in\n Annex B). We expect that future versions of this proposed standard\n will upgrade to the final International Standard version of IS 1195 algorithm authentication nested-reference unchanged"},{"id":"IETF RFC 1200","type":"specification","body":"IETF","designation":"RFC 1200","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1200.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1200.txt","https://www.rfc-editor.org/rfc/rfc1200.pdf"],"folder":"IETF/RFC-1200","files":{"txt":{"path":"standards/IETF/RFC-1200/RFC-1200.txt","sha256":"1f27586a7915116d09ddc70a1ea6873d0bd42f876c7f7d34fc60862a8c400e65"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1200 J. Postel, Editor\nObsoletes: RFCs 1140, April 1991\n 1100, 1083, 1130\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements . . . . ","scope_keywords":["1200","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null}],"search_text":"IETF RFC 1200 Network Working Group Internet Activities Board\nRequest for Comments: 1200 J. Postel, Editor\nObsoletes: RFCs 1140, April 1991\n 1100, 1083, 1130\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements . . . .  1200 risk nested-reference unchanged"},{"id":"IETF RFC 1206","type":"specification","body":"IETF","designation":"RFC 1206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1206.txt","https://www.rfc-editor.org/rfc/rfc1206.pdf"],"folder":"IETF/RFC-1206","files":{"txt":{"path":"standards/IETF/RFC-1206/RFC-1206.txt","sha256":"637d0ab218f9dfa7a8dc0047cfa540a1c27eae8219293d7a8a833fd32eca3f3f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1206 FTP Software, Inc.\nFYI: 4 A. Marine\nObsoletes: RFC 1177 SRI\n February 1991\n\n FYI on Questions and Answers\n Answers to Commonly asked \"New Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction................................................. 1\n 2. Acknowledgements............................................. 2\n 3. Questions About the Internet................................. 2\n 4. Questions About TCP/IP................","scope_keywords":["1206","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null}],"search_text":"IETF RFC 1206 Network Working Group G. Malkin\nRequest for Comments: 1206 FTP Software, Inc.\nFYI: 4 A. Marine\nObsoletes: RFC 1177 SRI\n February 1991\n\n FYI on Questions and Answers\n Answers to Commonly asked \"New Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction................................................. 1\n 2. Acknowledgements............................................. 2\n 3. Questions About the Internet................................. 2\n 4. Questions About TCP/IP................ 1206 registered nested-reference unchanged"},{"id":"IETF RFC 1209","type":"specification","body":"IETF","designation":"RFC 1209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1209.txt","https://www.rfc-editor.org/rfc/rfc1209.pdf"],"folder":"IETF/RFC-1209","files":{"txt":{"path":"standards/IETF/RFC-1209/RFC-1209.txt","sha256":"98a21dc738b6f238357c45e3654ed4a1b782393324103a94fac1ab7994c0b5f8"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an initial use of IP and ARP in an SMDS service\n environment configured as a logical IP subnetwork, LIS (described\n below). The encapsulation method used is described, as well as\n various service-specific issues. This memo does not preclude\n subsequent treatment of the SMDS Service in configurations other than\n LIS; specifically, public or inter-company, inter-enterprise\n configurations may be treated differently and will be described in\n future documents. This document considers only directly connected IP\n end-stations or routers; issues raised by MAC level bridging are\n beyond the scope of this paper.\n\nAcknowledgment\n\n This memo draws heavily in both concept and text from [4], written by\n Jon Postel and Joyce K. Reynolds of ISI and [5], written by David\n Katz of Merit, Inc. The authors would also like to acknowledge the\n contributions of the IP Over SMDS Service wor","scope_keywords":["1209","delivery","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1735","folder":"IETF/RFC-1735","source":"IETF/RFC-1735/RFC-1735.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1209 This memo describes an initial use of IP and ARP in an SMDS service\n environment configured as a logical IP subnetwork, LIS (described\n below). The encapsulation method used is described, as well as\n various service-specific issues. This memo does not preclude\n subsequent treatment of the SMDS Service in configurations other than\n LIS; specifically, public or inter-company, inter-enterprise\n configurations may be treated differently and will be described in\n future documents. This document considers only directly connected IP\n end-stations or routers; issues raised by MAC level bridging are\n beyond the scope of this paper.\n\nAcknowledgment\n\n This memo draws heavily in both concept and text from [4], written by\n Jon Postel and Joyce K. Reynolds of ISI and [5], written by David\n Katz of Merit, Inc. The authors would also like to acknowledge the\n contributions of the IP Over SMDS Service wor 1209 delivery path validation nested-reference unchanged"},{"id":"IETF RFC 1220","type":"specification","body":"IETF","designation":"RFC 1220","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1220.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1220.txt","https://www.rfc-editor.org/rfc/rfc1220.pdf"],"folder":"IETF/RFC-1220","files":{"txt":{"path":"standards/IETF/RFC-1220/RFC-1220.txt","sha256":"da28d5d99bf9a5844feea950641877164da495bd850fe9c01f59a4ccfdb85b18"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Baker, Editor\nRequest for Comments: 1220 ACC\n April 1991\n\n Point-to-Point Protocol Extensions for Bridging\n\n1. Status of this Memo\n\n This document defines an extension of the Internet Point-to-Point\n Protocol (PPP) described in RFC 1171, targeting the use of Point-to-\n Point lines for Remote Bridging. It is a product of the Point-to-\n Point Protocol Extensions Working Group of the Internet Engineering\n Task Force (IETF).\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n2. Historical Perspective\n\n Two basic algorithms are ambient in the industry for Bridging of\n Local Area Networks. The more common","scope_keywords":["1220","algorithm","algorithms","path","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null}],"search_text":"IETF RFC 1220 Network Working Group F. Baker, Editor\nRequest for Comments: 1220 ACC\n April 1991\n\n Point-to-Point Protocol Extensions for Bridging\n\n1. Status of this Memo\n\n This document defines an extension of the Internet Point-to-Point\n Protocol (PPP) described in RFC 1171, targeting the use of Point-to-\n Point lines for Remote Bridging. It is a product of the Point-to-\n Point Protocol Extensions Working Group of the Internet Engineering\n Task Force (IETF).\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n2. Historical Perspective\n\n Two basic algorithms are ambient in the industry for Bridging of\n Local Area Networks. The more common 1220 algorithm algorithms path preservation nested-reference unchanged"},{"id":"IETF RFC 1250","type":"specification","body":"IETF","designation":"RFC 1250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1250.txt","https://www.rfc-editor.org/rfc/rfc1250.pdf"],"folder":"IETF/RFC-1250","files":{"txt":{"path":"standards/IETF/RFC-1250/RFC-1250.txt","sha256":"685f3e510fcdcbb552b3860c756c76d37e19dc46361973653e6bcf6fccb38352"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1250 J. Postel, Editor\nObsoletes: RFCs 1200, August 1991\n1100, 1083, 1130, 1140\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements . ","scope_keywords":["1250","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1264","folder":"IETF/RFC-1264","source":"IETF/RFC-1264/RFC-1264.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null}],"search_text":"IETF RFC 1250 Network Working Group Internet Activities Board\nRequest for Comments: 1250 J. Postel, Editor\nObsoletes: RFCs 1200, August 1991\n1100, 1083, 1130, 1140\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Annotated Internet Protocols . . . . . . . . . . . . . . . 6\n 3.3. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.4. Host Requirements .  1250 risk nested-reference unchanged"},{"id":"IETF RFC 1280","type":"specification","body":"IETF","designation":"RFC 1280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1280.txt","https://www.rfc-editor.org/rfc/rfc1280.pdf"],"folder":"IETF/RFC-1280","files":{"txt":{"path":"standards/IETF/RFC-1280/RFC-1280.txt","sha256":"9ddbf7e9829c1da82a90c19c0e969c31511dfb6c9c6b308f0c62602fac50aa1f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1280 J. Postel, Editor\nObsoletes: RFCs 1250, March 1992\n1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . . . . . . . 6\n 3.4. The MIL-S","scope_keywords":["1280","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null}],"search_text":"IETF RFC 1280 Network Working Group Internet Activities Board\nRequest for Comments: 1280 J. Postel, Editor\nObsoletes: RFCs 1250, March 1992\n1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Activities Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . . . . . . . 6\n 3.4. The MIL-S 1280 risk nested-reference unchanged"},{"id":"IETF RFC 1294","type":"specification","body":"IETF","designation":"RFC 1294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1294.txt","https://www.rfc-editor.org/rfc/rfc1294.pdf"],"folder":"IETF/RFC-1294","files":{"txt":{"path":"standards/IETF/RFC-1294/RFC-1294.txt","sha256":"5f3222b537b07db23bb884eaab911b3cf528c185468e420c3e590ba584912d79"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing. Systems with the ability to transfer\n both this encapsulation method, and others must have a priori\n knowledge of which virtual circuits will carry which encapsulation\n method and this encapsulation must only be used over virtual circuits\n that have been explicitly configured for its use.\n\n3. Acknowledgements\n\n Comments and contributions from many sources, especially those from\n Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker\n and Charles Carvalho of Advanced Computer Communications and Mostafa\n Sherif of AT&T have been incorporated into this document. Special\n thanks to Dory Leifer of University of Michigan for his contributions\n to the resolution of fragmentation issues. This document could not\n have be","scope_keywords":["1294","identification","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1362","folder":"IETF/RFC-1362","source":"IETF/RFC-1362/RFC-1362.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1586","folder":"IETF/RFC-1586","source":"IETF/RFC-1586/RFC-1586.txt","version":null}],"search_text":"IETF RFC 1294 This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing. Systems with the ability to transfer\n both this encapsulation method, and others must have a priori\n knowledge of which virtual circuits will carry which encapsulation\n method and this encapsulation must only be used over virtual circuits\n that have been explicitly configured for its use.\n\n3. Acknowledgements\n\n Comments and contributions from many sources, especially those from\n Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker\n and Charles Carvalho of Advanced Computer Communications and Mostafa\n Sherif of AT&T have been incorporated into this document. Special\n thanks to Dory Leifer of University of Michigan for his contributions\n to the resolution of fragmentation issues. This document could not\n have be 1294 identification pid nested-reference unchanged"},{"id":"IETF RFC 1325","type":"specification","body":"IETF","designation":"RFC 1325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1325.txt","https://www.rfc-editor.org/rfc/rfc1325.pdf"],"folder":"IETF/RFC-1325","files":{"txt":{"path":"standards/IETF/RFC-1325/RFC-1325.txt","sha256":"7b482f77a803a62a1edb5809869b5cffc660ade522762f656ac64b7336696310"}},"tags":["nested-reference","unchanged"],"summary":"This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\nNew Questions and Answers\n\n In addition to updating information contained in the previous version\n of this FYI RFC, the following new questions have been added:\n\n Questions About the Internet:\n How do I get a list of all the hosts on the Internet?\n\n Questions About Internet Documentation:\n What is the RFC-INFO service?\n What is an FYI?\n What is an STD?\n What is the Internet Monthly Report?\n\n Questions About Internet Organizations:\n What is the Internet Society?\n\n Questions About Internet Services:\n What is \"archie\"?\n How do I Connect to archie?\n\n Mailing Lists and Sending Mail\n How Do I Send Mail to Other Networks?\n\nUser Services Working ","scope_keywords":["1325"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1463","folder":"IETF/RFC-1463","source":"IETF/RFC-1463/RFC-1463.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null}],"search_text":"IETF RFC 1325 This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\nNew Questions and Answers\n\n In addition to updating information contained in the previous version\n of this FYI RFC, the following new questions have been added:\n\n Questions About the Internet:\n How do I get a list of all the hosts on the Internet?\n\n Questions About Internet Documentation:\n What is the RFC-INFO service?\n What is an FYI?\n What is an STD?\n What is the Internet Monthly Report?\n\n Questions About Internet Organizations:\n What is the Internet Society?\n\n Questions About Internet Services:\n What is \"archie\"?\n How do I Connect to archie?\n\n Mailing Lists and Sending Mail\n How Do I Send Mail to Other Networks?\n\nUser Services Working  1325 nested-reference unchanged"},{"id":"IETF RFC 1360","type":"specification","body":"IETF","designation":"RFC 1360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1360.txt","https://www.rfc-editor.org/rfc/rfc1360.pdf"],"folder":"IETF/RFC-1360","files":{"txt":{"path":"standards/IETF/RFC-1360/RFC-1360.txt","sha256":"d347877758f35c9e297129c2694fb438d5764c8a956c6a0ac9a8a11d0356cad6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1360 J. Postel, Editor\nObsoletes: RFCs 1280, 1250, September 1992\n1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . . . . . . . 6\n ","scope_keywords":["1360","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null}],"search_text":"IETF RFC 1360 Network Working Group Internet Architecture Board\nRequest for Comments: 1360 J. Postel, Editor\nObsoletes: RFCs 1280, 1250, September 1992\n1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n IAB OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . . . . . . . 6\n  1360 risk nested-reference unchanged"},{"id":"IETF RFC 1374","type":"specification","body":"IETF","designation":"RFC 1374","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1374.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1374.txt","https://www.rfc-editor.org/rfc/rfc1374.pdf"],"folder":"IETF/RFC-1374","files":{"txt":{"path":"standards/IETF/RFC-1374/RFC-1374.txt","sha256":"8436d4c7cb6955f8a5ee6eca3f2596e70d40173e9673b81af6c775d8a51ec2b1"}},"tags":["nested-reference","unchanged"],"summary":"The ANSI X3T9.3 committee has drafted a proposal for the\n encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on\n HIPPI. Another X3T9.3 draft describes the operation of HIPPI\n physical switches. X3T9.3 chose to leave HIPPI networking issues\n largely outside the scope of their standards; this document discusses\n methods of using of ANSI standard HIPPI hardware and protocols in the\n context of the Internet, including the use of HIPPI switches as LANs\n and interoperation with other networks.","scope_keywords":["1374","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null}],"search_text":"IETF RFC 1374 The ANSI X3T9.3 committee has drafted a proposal for the\n encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on\n HIPPI. Another X3T9.3 draft describes the operation of HIPPI\n physical switches. X3T9.3 chose to leave HIPPI networking issues\n largely outside the scope of their standards; this document discusses\n methods of using of ANSI standard HIPPI hardware and protocols in the\n context of the Internet, including the use of HIPPI switches as LANs\n and interoperation with other networks. 1374 management path nested-reference unchanged"},{"id":"IETF RFC 1390","type":"specification","body":"IETF","designation":"RFC 1390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1390.txt","https://www.rfc-editor.org/rfc/rfc1390.pdf"],"folder":"IETF/RFC-1390","files":{"txt":{"path":"standards/IETF/RFC-1390/RFC-1390.txt","sha256":"b068ce48f31bde542ffd6805259b92af329b079fe15583ebef449ff3d05bf1ef"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a method of encapsulating the Internet Protocol\n (IP) datagrams and Address Resolution Protocol (ARP) requests and\n replies on Fiber Distributed Data Interface (FDDI) Networks.\n\n This RFC is the product of the IP over FDDI Working Group of the\n Internet Engineering Task Force (IETF).\n\nAcknowledgments\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute. The author would also like to acknowledge the\n contributions of the IP Over FDDI Working Group of the IETF, members\n of ANSI ASC X3T9.5, and others in the FDDI community.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must,\" \"Shall,\" or \"Mandatory\"--the item is an absolute\n requirement of the specification.\n\n \"Should\" or \"Recommended\"--the item should general","scope_keywords":["1390","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1390 This memo defines a method of encapsulating the Internet Protocol\n (IP) datagrams and Address Resolution Protocol (ARP) requests and\n replies on Fiber Distributed Data Interface (FDDI) Networks.\n\n This RFC is the product of the IP over FDDI Working Group of the\n Internet Engineering Task Force (IETF).\n\nAcknowledgments\n\n This memo draws heavily in both concept and text from RFC 1042 [3],\n written by Jon Postel and Joyce K. Reynolds of USC/Information\n Sciences Institute. The author would also like to acknowledge the\n contributions of the IP Over FDDI Working Group of the IETF, members\n of ANSI ASC X3T9.5, and others in the FDDI community.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n \"Must,\" \"Shall,\" or \"Mandatory\"--the item is an absolute\n requirement of the specification.\n\n \"Should\" or \"Recommended\"--the item should general 1390 management nested-reference unchanged"},{"id":"IETF RFC 1392","type":"specification","body":"IETF","designation":"RFC 1392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1392.txt","https://www.rfc-editor.org/rfc/rfc1392.pdf"],"folder":"IETF/RFC-1392","files":{"txt":{"path":"standards/IETF/RFC-1392/RFC-1392.txt","sha256":"c1761d1374454a9a093f40359766cb4b5996a7ebcb5f1d27f82516859c795160"}},"tags":["nested-reference","unchanged"],"summary":"There are many networking glossaries in existence. This glossary\n concentrates on terms which are specific to the Internet. Naturally,\n there are entries for some basic terms and acronyms because other\n entries refer to them.\n\nAcknowledgements\n\n This document is the work of the User Glossary Working Group of the\n User Services Area of the Internet Engineering Task Force (IETF).\n Special thanks go to Jon Postel for his definitive definition of\n \"datagram\".","scope_keywords":["1392","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1463","folder":"IETF/RFC-1463","source":"IETF/RFC-1463/RFC-1463.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1392 There are many networking glossaries in existence. This glossary\n concentrates on terms which are specific to the Internet. Naturally,\n there are entries for some basic terms and acronyms because other\n entries refer to them.\n\nAcknowledgements\n\n This document is the work of the User Glossary Working Group of the\n User Services Area of the Internet Engineering Task Force (IETF).\n Special thanks go to Jon Postel for his definitive definition of\n \"datagram\". 1392 policies policy nested-reference unchanged"},{"id":"IETF RFC 1470","type":"specification","body":"IETF","designation":"RFC 1470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1470.txt","https://www.rfc-editor.org/rfc/rfc1470.pdf"],"folder":"IETF/RFC-1470","files":{"txt":{"path":"standards/IETF/RFC-1470/RFC-1470.txt","sha256":"93462826dafeca94e6122d67c31980a8c3025026803ca19e406869f6f1484ee2"}},"tags":["nested-reference","unchanged"],"summary":"The goal of this FYI memo is to provide an update to FYI 2, RFC 1147\n [1], which provided practical information to site administrators and\n network managers. New and/or updated tools are listed in this RFC.\n Additonal descriptions are welcome, and should be sent to: noctools-\n entries@merit.edu.","scope_keywords":["1470","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1470 The goal of this FYI memo is to provide an update to FYI 2, RFC 1147\n [1], which provided practical information to site administrators and\n network managers. New and/or updated tools are listed in this RFC.\n Additonal descriptions are welcome, and should be sent to: noctools-\n entries@merit.edu. 1470 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 1483","type":"specification","body":"IETF","designation":"RFC 1483","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1483.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1483.txt","https://www.rfc-editor.org/rfc/rfc1483.pdf"],"folder":"IETF/RFC-1483","files":{"txt":{"path":"standards/IETF/RFC-1483/RFC-1483.txt","sha256":"6e4b475089d40a9b7b2812dc9b8048620fcf9bbfe758e6f453d79bd222f1ad31"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes two encapsulations methods for carrying network\n interconnect traffic over ATM AAL5. The first method allows\n multiplexing of multiple protocols over a single ATM virtual circuit\n whereas the second method assumes that each protocol is carried over\n a separate ATM virtual circuit.\n\n1. Introduction\n\n Asynchronous Transfer Mode (ATM) based networks are of increasing\n interest for both local and wide area applications. This memo\n describes two different methods for carrying connectionless network\n interconnect traffic, routed and bridged Protocol Data Units (PDUs),\n over an ATM network. The first method allows multiplexing of\n multiple protocols over a single ATM virtual circuit. The protocol\n of a carried PDU is identified by prefixing the PDU by an IEEE 802.2\n Logical Link Control (LLC) header. This method is in the following\n called \"LLC Encapsulation\" and a subset of","scope_keywords":["1483","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2098","folder":"IETF/RFC-2098","source":"IETF/RFC-2098/RFC-2098.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1483 This memo describes two encapsulations methods for carrying network\n interconnect traffic over ATM AAL5. The first method allows\n multiplexing of multiple protocols over a single ATM virtual circuit\n whereas the second method assumes that each protocol is carried over\n a separate ATM virtual circuit.\n\n1. Introduction\n\n Asynchronous Transfer Mode (ATM) based networks are of increasing\n interest for both local and wide area applications. This memo\n describes two different methods for carrying connectionless network\n interconnect traffic, routed and bridged Protocol Data Units (PDUs),\n over an ATM network. The first method allows multiplexing of\n multiple protocols over a single ATM virtual circuit. The protocol\n of a carried PDU is identified by prefixing the PDU by an IEEE 802.2\n Logical Link Control (LLC) header. This method is in the following\n called \"LLC Encapsulation\" and a subset of 1483 pid nested-reference unchanged"},{"id":"IETF RFC 1490","type":"specification","body":"IETF","designation":"RFC 1490","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1490.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1490.txt","https://www.rfc-editor.org/rfc/rfc1490.pdf"],"folder":"IETF/RFC-1490","files":{"txt":{"path":"standards/IETF/RFC-1490/RFC-1490.txt","sha256":"e2c4627fb8f0ab4417235a0c5c1e23c93c83dcffa22c99a12e5761d245b45151"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing. Additionally, it describes a simple\n fragmentation procedure for carrying large frames over a frame relay\n network with a smaller MTU.\n\n Systems with the ability to transfer both the encapsulation method\n described in this document, and others must have a priori knowledge\n of which virtual circuits will carry which encapsulation method and\n this encapsulation must only be used over virtual circuits that have\n been explicitly configured for its use.\n\nAcknowledgements\n\n Comments and contributions from many sources, especially those from\n Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker\n and Charles Carvalho of Advanced Computer Communications and Mostafa\n Sherif of AT&T have been incorporated into this docum","scope_keywords":["1490","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1973","folder":"IETF/RFC-1973","source":"IETF/RFC-1973/RFC-1973.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 3070","folder":"IETF/RFC-3070","source":"IETF/RFC-3070/RFC-3070.txt","version":null}],"search_text":"IETF RFC 1490 This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing. Additionally, it describes a simple\n fragmentation procedure for carrying large frames over a frame relay\n network with a smaller MTU.\n\n Systems with the ability to transfer both the encapsulation method\n described in this document, and others must have a priori knowledge\n of which virtual circuits will carry which encapsulation method and\n this encapsulation must only be used over virtual circuits that have\n been explicitly configured for its use.\n\nAcknowledgements\n\n Comments and contributions from many sources, especially those from\n Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker\n and Charles Carvalho of Advanced Computer Communications and Mostafa\n Sherif of AT&T have been incorporated into this docum 1490 pid nested-reference unchanged"},{"id":"IETF RFC 1500","type":"specification","body":"IETF","designation":"RFC 1500","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1500.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1500.txt","https://www.rfc-editor.org/rfc/rfc1500.pdf"],"folder":"IETF/RFC-1500","files":{"txt":{"path":"standards/IETF/RFC-1500/RFC-1500.txt","sha256":"95d69bde329baff53a3ee4961c133281f4a36c10679c6766456446ac2e45b7b4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1500 J. Postel, Editor\nObsoletes: RFCs 1410, 1360, 1280, August 1993\n1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . .","scope_keywords":["1500","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null}],"search_text":"IETF RFC 1500 Network Working Group Internet Architecture Board\nRequest for Comments: 1500 J. Postel, Editor\nObsoletes: RFCs 1410, 1360, 1280, August 1993\n1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requirements . . . . . . . . . . . . . . . 1500 risk nested-reference unchanged"},{"id":"IETF RFC 1526","type":"specification","body":"IETF","designation":"RFC 1526","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1526.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1526.txt","https://www.rfc-editor.org/rfc/rfc1526.pdf"],"folder":"IETF/RFC-1526","files":{"txt":{"path":"standards/IETF/RFC-1526/RFC-1526.txt","sha256":"e36897c7242b0081a962dec22bb82b66213ddf4b76ec48f73e517621f7dae6f0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes conventions whereby the system identifier\n portion of an RFC 1237 style NSAP address may be guaranteed\n uniqueness within a routing domain for the purpose of\n autoconfiguration in TUBA/CLNP internets. The mechanism is extensible\n and can provide a basis for assigning system identifiers in a\n globally unique fashion.","scope_keywords":["1526","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null}],"search_text":"IETF RFC 1526 This document describes conventions whereby the system identifier\n portion of an RFC 1237 style NSAP address may be guaranteed\n uniqueness within a routing domain for the purpose of\n autoconfiguration in TUBA/CLNP internets. The mechanism is extensible\n and can provide a basis for assigning system identifiers in a\n globally unique fashion. 1526 subject nested-reference unchanged"},{"id":"IETF RFC 1533","type":"specification","body":"IETF","designation":"RFC 1533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1533.txt","https://www.rfc-editor.org/rfc/rfc1533.pdf"],"folder":"IETF/RFC-1533","files":{"txt":{"path":"standards/IETF/RFC-1533/RFC-1533.txt","sha256":"a558a69bd13def55cc4d5f152e97e78b3af990b2f5ca4ed368593dbb4160e331"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) [1] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. Configuration parameters and other control information are\n carried in tagged data items that are stored in the \"options\" field\n of the DHCP message. The data items themselves are also called\n \"options.\"\n\n This document specifies the current set of DHCP options. This\n document will be periodically updated as new options are defined.\n Each superseding document will include the entire current list of\n valid options.\n\n All of the vendor information extensions defined in RFC 1497 [2] may\n be used as DHCP options. The definitions given in RFC 1497 are\n included in this document, which supersedes RFC 1497. All of the\n DHCP options defined in this document, except for those specific to\n DHCP as defined in section 9, may be used as BOOTP vendor information","scope_keywords":["1533"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1534","folder":"IETF/RFC-1534","source":"IETF/RFC-1534/RFC-1534.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null}],"search_text":"IETF RFC 1533 The Dynamic Host Configuration Protocol (DHCP) [1] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. Configuration parameters and other control information are\n carried in tagged data items that are stored in the \"options\" field\n of the DHCP message. The data items themselves are also called\n \"options.\"\n\n This document specifies the current set of DHCP options. This\n document will be periodically updated as new options are defined.\n Each superseding document will include the entire current list of\n valid options.\n\n All of the vendor information extensions defined in RFC 1497 [2] may\n be used as DHCP options. The definitions given in RFC 1497 are\n included in this document, which supersedes RFC 1497. All of the\n DHCP options defined in this document, except for those specific to\n DHCP as defined in section 9, may be used as BOOTP vendor information 1533 nested-reference unchanged"},{"id":"IETF RFC 1540","type":"specification","body":"IETF","designation":"RFC 1540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1540.txt","https://www.rfc-editor.org/rfc/rfc1540.pdf"],"folder":"IETF/RFC-1540","files":{"txt":{"path":"standards/IETF/RFC-1540/RFC-1540.txt","sha256":"a890083de47d9ab806ab91b50398be41a9763c4b1168d870169ea17327e03a96"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1540 J. Postel, Editor\nObsoletes: RFCs 1500, 1410, 1360, October 1993\n1280, 1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requireme","scope_keywords":["1540","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1543","folder":"IETF/RFC-1543","source":"IETF/RFC-1543/RFC-1543.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null}],"search_text":"IETF RFC 1540 Network Working Group Internet Architecture Board\nRequest for Comments: 1540 J. Postel, Editor\nObsoletes: RFCs 1500, 1410, 1360, October 1993\n1280, 1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 2\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . . . . . . . . . . 6\n 3.3. Host Requireme 1540 risk nested-reference unchanged"},{"id":"IETF RFC 1577","type":"specification","body":"IETF","designation":"RFC 1577","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1577.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1577.txt","https://www.rfc-editor.org/rfc/rfc1577.pdf"],"folder":"IETF/RFC-1577","files":{"txt":{"path":"standards/IETF/RFC-1577/RFC-1577.txt","sha256":"269958fa24cd8a771c3c7073ff42043b056de17102b3909b25b75542913d3fe3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an initial application of classical IP and ARP in\n an Asynchronous Transfer Mode (ATM) network environment configured as\n a Logical IP Subnetwork (LIS) as described in Section 3. This memo\n does not preclude the subsequent development of ATM technology into\n areas other than a LIS; specifically, as single ATM networks grow to\n replace many ethernet local LAN segments and as these networks become\n globally connected, the application of IP and ARP will be treated\n differently. This memo considers only the application of ATM as a\n direct replacement for the \"wires\" and local LAN segments connecting\n IP end-stations (\"members\") and routers operating in the \"classical\"\n LAN-based paradigm. Issues raised by MAC level bridging and LAN\n emulation are beyond the scope of this paper.\n\n This memo introduces general ATM technology and nomenclature.\n Readers are encouraged to review","scope_keywords":["1577","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1671","folder":"IETF/RFC-1671","source":"IETF/RFC-1671/RFC-1671.txt","version":null},{"body":"IETF","designation":"RFC 1680","folder":"IETF/RFC-1680","source":"IETF/RFC-1680/RFC-1680.txt","version":null},{"body":"IETF","designation":"RFC 1735","folder":"IETF/RFC-1735","source":"IETF/RFC-1735/RFC-1735.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 1937","folder":"IETF/RFC-1937","source":"IETF/RFC-1937/RFC-1937.txt","version":null},{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2098","folder":"IETF/RFC-2098","source":"IETF/RFC-2098/RFC-2098.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null}],"search_text":"IETF RFC 1577 This memo defines an initial application of classical IP and ARP in\n an Asynchronous Transfer Mode (ATM) network environment configured as\n a Logical IP Subnetwork (LIS) as described in Section 3. This memo\n does not preclude the subsequent development of ATM technology into\n areas other than a LIS; specifically, as single ATM networks grow to\n replace many ethernet local LAN segments and as these networks become\n globally connected, the application of IP and ARP will be treated\n differently. This memo considers only the application of ATM as a\n direct replacement for the \"wires\" and local LAN segments connecting\n IP end-stations (\"members\") and routers operating in the \"classical\"\n LAN-based paradigm. Issues raised by MAC level bridging and LAN\n emulation are beyond the scope of this paper.\n\n This memo introduces general ATM technology and nomenclature.\n Readers are encouraged to review 1577 management path nested-reference unchanged"},{"id":"IETF RFC 1594","type":"specification","body":"IETF","designation":"RFC 1594","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1594.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1594.txt","https://www.rfc-editor.org/rfc/rfc1594.pdf"],"folder":"IETF/RFC-1594","files":{"txt":{"path":"standards/IETF/RFC-1594/RFC-1594.txt","sha256":"3e1d1145a22d56e541241891a196cbf59ab530b3b52cf4fe4fb968d3ffc71c89"}},"tags":["nested-reference","unchanged"],"summary":"This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\nNew Questions and Answers\n\n In addition to updating information contained in the previous version\n of this FYI RFC, the following new questions have been added:\n\n Questions about Internet Organizations and Contacts:\n\n What is the InterNIC?\n\n Questions About Internet Services:\n\n What is gopher?\n What is the World Wide Web? What is Mosaic?\n How do I find out about other Internet resource discovery tools?\n\nUser Services Working Group [Page 1]\n\f\nRFC 1594 FYI Q/A - for New Internet Users March 1994","scope_keywords":["1594"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1900","folder":"IETF/RFC-1900","source":"IETF/RFC-1900/RFC-1900.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null}],"search_text":"IETF RFC 1594 This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\nNew Questions and Answers\n\n In addition to updating information contained in the previous version\n of this FYI RFC, the following new questions have been added:\n\n Questions about Internet Organizations and Contacts:\n\n What is the InterNIC?\n\n Questions About Internet Services:\n\n What is gopher?\n What is the World Wide Web? What is Mosaic?\n How do I find out about other Internet resource discovery tools?\n\nUser Services Working Group [Page 1]\n\f\nRFC 1594 FYI Q/A - for New Internet Users March 1994 1594 nested-reference unchanged"},{"id":"IETF RFC 1600","type":"specification","body":"IETF","designation":"RFC 1600","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1600.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1600.txt","https://www.rfc-editor.org/rfc/rfc1600.pdf"],"folder":"IETF/RFC-1600","files":{"txt":{"path":"standards/IETF/RFC-1600/RFC-1600.txt","sha256":"27bb9a4b46d2c16dec6bc964b90f70ed3a9c3c7f7ca679f30fbc2c3e7d4c615e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1600 J. Postel, Editor\nObsoletes: RFCs 1540, 1500, 1410, 1360, March 1994\n1280, 1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . . ","scope_keywords":["1600","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1602","folder":"IETF/RFC-1602","source":"IETF/RFC-1602/RFC-1602.txt","version":null},{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null}],"search_text":"IETF RFC 1600 Network Working Group Internet Architecture Board\nRequest for Comments: 1600 J. Postel, Editor\nObsoletes: RFCs 1540, 1500, 1410, 1360, March 1994\n1280, 1250, 1100, 1083, 1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . . .  1600 risk nested-reference unchanged"},{"id":"IETF RFC 1610","type":"specification","body":"IETF","designation":"RFC 1610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1610.txt","https://www.rfc-editor.org/rfc/rfc1610.pdf"],"folder":"IETF/RFC-1610","files":{"txt":{"path":"standards/IETF/RFC-1610/RFC-1610.txt","sha256":"e46a02ff52eb1c6f0a35ce2aa13951b90d22fa96c666ab4ca1f64b22f8c3591d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1610 J. Postel, Editor\nObsoletes: RFCs 1600, 1540, 1500, 1410, July 1994\n1360, 1280, 1250, 1100, 1083, 1130,\n1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . .","scope_keywords":["1610","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null}],"search_text":"IETF RFC 1610 Network Working Group Internet Architecture Board\nRequest for Comments: 1610 J. Postel, Editor\nObsoletes: RFCs 1600, 1540, 1500, 1410, July 1994\n1360, 1280, 1250, 1100, 1083, 1130,\n1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . . . . . . 1610 risk nested-reference unchanged"},{"id":"IETF RFC 1638","type":"specification","body":"IETF","designation":"RFC 1638","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1638.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1638.txt","https://www.rfc-editor.org/rfc/rfc1638.pdf"],"folder":"IETF/RFC-1638","files":{"txt":{"path":"standards/IETF/RFC-1638/RFC-1638.txt","sha256":"d6654dca289a2384e7dd145a9544dda7a08255e43bdf83ec8ebde159598c8d74"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [6] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring Remote Bridging for PPP links.","scope_keywords":["1638","algorithm","algorithms","identification","path","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null}],"search_text":"IETF RFC 1638 The Point-to-Point Protocol (PPP) [6] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring Remote Bridging for PPP links. 1638 algorithm algorithms identification path preservation nested-reference unchanged"},{"id":"IETF RFC 1715","type":"specification","body":"IETF","designation":"RFC 1715","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1715.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1715.txt","https://www.rfc-editor.org/rfc/rfc1715.pdf"],"folder":"IETF/RFC-1715","files":{"txt":{"path":"standards/IETF/RFC-1715/RFC-1715.txt","sha256":"1a0babc82e9464af4db0fba5a89e59476bc53d5660d195d998d395fd3f8bbf1a"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the author and/or the sipp@sunroof.eng.sun.com mailing\n list.","scope_keywords":["1715"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3194","folder":"IETF/RFC-3194","source":"IETF/RFC-3194/RFC-3194.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 4692","folder":"IETF/RFC-4692","source":"IETF/RFC-4692/RFC-4692.txt","version":null}],"search_text":"IETF RFC 1715 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the author and/or the sipp@sunroof.eng.sun.com mailing\n list. 1715 nested-reference unchanged"},{"id":"IETF RFC 1720","type":"specification","body":"IETF","designation":"RFC 1720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1720.txt","https://www.rfc-editor.org/rfc/rfc1720.pdf"],"folder":"IETF/RFC-1720","files":{"txt":{"path":"standards/IETF/RFC-1720/RFC-1720.txt","sha256":"fcfcb284d5dbe7108710211cd1081f46424fd1094d15a2761668cb208a3e6a4a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1720 J. Postel, Editor\nObsoletes: RFCs 1610, 1600, 1540, 1500, November 1994\n1410, 1360, 1280, 1250, 1100, 1083,\n1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . .","scope_keywords":["1720","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1720 Network Working Group Internet Architecture Board\nRequest for Comments: 1720 J. Postel, Editor\nObsoletes: RFCs 1610, 1600, 1540, 1500, November 1994\n1410, 1360, 1280, 1250, 1100, 1083,\n1130, 1140, 1200\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . . . 1720 risk nested-reference unchanged"},{"id":"IETF RFC 1752","type":"specification","body":"IETF","designation":"RFC 1752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1752.txt","https://www.rfc-editor.org/rfc/rfc1752.pdf"],"folder":"IETF/RFC-1752","files":{"txt":{"path":"standards/IETF/RFC-1752/RFC-1752.txt","sha256":"8eee375801368eac5de69150fbd36a46f03907057cb1ed6cfd2f4003c100e2be"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the recommendation of the IPng Area Directors\n on what should be used to replace the current version of the Internet\n Protocol. This recommendation was accepted by the Internet\n Engineering Steering Group (IESG).","scope_keywords":["1752","authentication","encryption","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 1752 This document presents the recommendation of the IPng Area Directors\n on what should be used to replace the current version of the Internet\n Protocol. This recommendation was accepted by the Internet\n Engineering Steering Group (IESG). 1752 authentication encryption policies policy nested-reference unchanged"},{"id":"IETF RFC 1768","type":"specification","body":"IETF","designation":"RFC 1768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1768.txt","https://www.rfc-editor.org/rfc/rfc1768.pdf"],"folder":"IETF/RFC-1768","files":{"txt":{"path":"standards/IETF/RFC-1768/RFC-1768.txt","sha256":"a104ac8dda445e23c2290446ddcf8d7b46e50b1ec43a1777c3373550761f28ed"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents work performed in the TUBA (TCP/UDP over Bigger\n Addresses) working group of IPng area prior to the July 1994 decision\n to utilize SIPP-16 as the basis for IPng. The TUBA group worked on\n extending the Internet Protocol suite by the use of ISO 8473 (CLNP)\n and its related routing protocols. This memo describes multicast\n extensions to CLNP and its related routing protocols for Internet\n multicast use. Publication of this memo does not imply acceptance by\n any IETF Working Group for the ideas expressed within.\n\n This memo provides a specification for multicast extensions to the\n CLNP protocol similar to those provided to IP by RFC1112. These\n extensions are intended to provide the mechanisms needed by a host\n for multicasting in a CLNP based Internet. This memo covers\n addressing extensions to the CLNP addressing structure, extensions to\n the CLNP protocol and extensio","scope_keywords":["1768","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null}],"search_text":"IETF RFC 1768 This memo documents work performed in the TUBA (TCP/UDP over Bigger\n Addresses) working group of IPng area prior to the July 1994 decision\n to utilize SIPP-16 as the basis for IPng. The TUBA group worked on\n extending the Internet Protocol suite by the use of ISO 8473 (CLNP)\n and its related routing protocols. This memo describes multicast\n extensions to CLNP and its related routing protocols for Internet\n multicast use. Publication of this memo does not imply acceptance by\n any IETF Working Group for the ideas expressed within.\n\n This memo provides a specification for multicast extensions to the\n CLNP protocol similar to those provided to IP by RFC1112. These\n extensions are intended to provide the mechanisms needed by a host\n for multicasting in a CLNP based Internet. This memo covers\n addressing extensions to the CLNP addressing structure, extensions to\n the CLNP protocol and extensio 1768 key path nested-reference unchanged"},{"id":"IETF RFC 1780","type":"specification","body":"IETF","designation":"RFC 1780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1780.txt","https://www.rfc-editor.org/rfc/rfc1780.pdf"],"folder":"IETF/RFC-1780","files":{"txt":{"path":"standards/IETF/RFC-1780/RFC-1780.txt","sha256":"06364c21071f3f594ef6af6f96ee829fd131e7a3b6e428f3c0751acb6bbeaa35"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1780 J. Postel, Editor\nObsoletes: RFCs 1720, 1610, 1600, 1540, March 1995\n1500, 1410, 1360, 1280, 1250, 1200,\n1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements . ","scope_keywords":["1780","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1780 Network Working Group Internet Architecture Board\nRequest for Comments: 1780 J. Postel, Editor\nObsoletes: RFCs 1720, 1610, 1600, 1540, March 1995\n1500, 1410, 1360, 1280, 1250, 1200,\n1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requirements .  1780 risk nested-reference unchanged"},{"id":"IETF RFC 1800","type":"specification","body":"IETF","designation":"RFC 1800","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1800.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1800.txt","https://www.rfc-editor.org/rfc/rfc1800.pdf"],"folder":"IETF/RFC-1800","files":{"txt":{"path":"standards/IETF/RFC-1800/RFC-1800.txt","sha256":"f9f4968bb0469e23f5b85a2a72d1b8bc9ae5f97a4b2d59739de7c4e970057ff4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1800 J. Postel, Editor\nObsoletes: RFCs 1780, 1720, 1610, 1600, July 1995\n1540, 1500, 1410, 1360, 1280, 1250,\n1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requiremen","scope_keywords":["1800","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 1851","folder":"IETF/RFC-1851","source":"IETF/RFC-1851/RFC-1851.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null}],"search_text":"IETF RFC 1800 Network Working Group Internet Architecture Board\nRequest for Comments: 1800 J. Postel, Editor\nObsoletes: RFCs 1780, 1720, 1610, 1600, July 1995\n1540, 1500, 1410, 1360, 1280, 1250,\n1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Requiremen 1800 risk nested-reference unchanged"},{"id":"IETF RFC 1884","type":"specification","body":"IETF","designation":"RFC 1884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1884.txt","https://www.rfc-editor.org/rfc/rfc1884.pdf"],"folder":"IETF/RFC-1884","files":{"txt":{"path":"standards/IETF/RFC-1884/RFC-1884.txt","sha256":"20cfb87e08f312e33934f56f0224f46d9c8d8b85020cc52874768fae94d596ca"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the addressing architecture of the IP\n Version 6 protocol [IPV6]. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 nodes required addresses.\n\nHinden & Deering Standards Track [Page 1]\n\f\nRFC 1884 IPv6 Addressing Architecture December 1995","scope_keywords":["1884","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1886","folder":"IETF/RFC-1886","source":"IETF/RFC-1886/RFC-1886.txt","version":null},{"body":"IETF","designation":"RFC 1887","folder":"IETF/RFC-1887","source":"IETF/RFC-1887/RFC-1887.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1897","folder":"IETF/RFC-1897","source":"IETF/RFC-1897/RFC-1897.txt","version":null},{"body":"IETF","designation":"RFC 1924","folder":"IETF/RFC-1924","source":"IETF/RFC-1924/RFC-1924.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 1972","folder":"IETF/RFC-1972","source":"IETF/RFC-1972/RFC-1972.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2073","folder":"IETF/RFC-2073","source":"IETF/RFC-2073/RFC-2073.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2133","folder":"IETF/RFC-2133","source":"IETF/RFC-2133/RFC-2133.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2365","folder":"IETF/RFC-2365","source":"IETF/RFC-2365/RFC-2365.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 1884 This specification defines the addressing architecture of the IP\n Version 6 protocol [IPV6]. The document includes the IPv6 addressing\n model, text representations of IPv6 addresses, definition of IPv6\n unicast addresses, anycast addresses, and multicast addresses, and an\n IPv6 nodes required addresses.\n\nHinden & Deering Standards Track [Page 1]\n\f\nRFC 1884 IPv6 Addressing Architecture December 1995 1884 presentation nested-reference unchanged"},{"id":"IETF RFC 1897","type":"specification","body":"IETF","designation":"RFC 1897","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1897.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1897.txt","https://www.rfc-editor.org/rfc/rfc1897.pdf"],"folder":"IETF/RFC-1897","files":{"txt":{"path":"standards/IETF/RFC-1897/RFC-1897.txt","sha256":"73b50e9b2bc80fabda30f88440e1b1a32aee33cd224f61555a34b17577e5d57d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 1897 Ipsilon Networks\nCategory: Experimental J. Postel\n ISI\n January 1996\n\n IPv6 Testing Address Allocation\n\nStatus of this Memo\n\n This document specifies an Experimental protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n This document describes an allocation plan for IPv6 addresses to be\n used in testing IPv6 prototype software. These addresses are\n temporary and will be reclaimed in the future. Any IPv6 system using\n these addresses will have to renumber at some time in the future.\n These addresses will not to be routable in the Internet other than\n for IPv6 testing.\n\n The addresses described in this document are consistent with the IPv6\n Addressing Architecture [ARCH","scope_keywords":["1897","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null}],"search_text":"IETF RFC 1897 Network Working Group R. Hinden\nRequest for Comments: 1897 Ipsilon Networks\nCategory: Experimental J. Postel\n ISI\n January 1996\n\n IPv6 Testing Address Allocation\n\nStatus of this Memo\n\n This document specifies an Experimental protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n This document describes an allocation plan for IPv6 addresses to be\n used in testing IPv6 prototype software. These addresses are\n temporary and will be reclaimed in the future. Any IPv6 system using\n these addresses will have to renumber at some time in the future.\n These addresses will not to be routable in the Internet other than\n for IPv6 testing.\n\n The addresses described in this document are consistent with the IPv6\n Addressing Architecture [ARCH 1897 algorithm nested-reference unchanged"},{"id":"IETF RFC 1920","type":"specification","body":"IETF","designation":"RFC 1920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1920.txt","https://www.rfc-editor.org/rfc/rfc1920.pdf"],"folder":"IETF/RFC-1920","files":{"txt":{"path":"standards/IETF/RFC-1920/RFC-1920.txt","sha256":"6bfeacc750cb7bebac32f60a1afc7b34c2eae20f726e13791f6daf23fef86cb4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1920 J. Postel, Editor\nObsoletes: 1880, 1800, 1780, 1720, March 1996\n1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Re","scope_keywords":["1920","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null}],"search_text":"IETF RFC 1920 Network Working Group Internet Architecture Board\nRequest for Comments: 1920 J. Postel, Editor\nObsoletes: 1880, 1800, 1780, 1720, March 1996\n1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. Gateway Re 1920 risk nested-reference unchanged"},{"id":"IETF RFC 1931","type":"specification","body":"IETF","designation":"RFC 1931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1931.txt","https://www.rfc-editor.org/rfc/rfc1931.pdf"],"folder":"IETF/RFC-1931","files":{"txt":{"path":"standards/IETF/RFC-1931/RFC-1931.txt","sha256":"b8f47817eff31dff8fb0c12bc036e8ab4a349a67d8b231ce27dd707acf35a381"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Brownell\nRequest For Comments: 1931 Sun Microsystems, Inc.\nCategory: Informational April 1996\n\n Dynamic RARP Extensions for\n Automatic Network Address Acquisition\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not define an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo describes extensions to the Reverse Address Resolution\n Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-\n RARP). The role of DRARP, and to some extent the configuration\n protocol used in conjunction with it, has subsequently been addressed\n by the DHCP protocol [9]. This memo is being published now to\n document this protocol for the record.\n\n DRARP is used to acquire (or allocate) a protocol level address given\n the fixed hardware address for a host. Its clients are systems bei","scope_keywords":["1931","authentication","key","keys","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 1931 Network Working Group D. Brownell\nRequest For Comments: 1931 Sun Microsystems, Inc.\nCategory: Informational April 1996\n\n Dynamic RARP Extensions for\n Automatic Network Address Acquisition\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not define an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo describes extensions to the Reverse Address Resolution\n Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-\n RARP). The role of DRARP, and to some extent the configuration\n protocol used in conjunction with it, has subsequently been addressed\n by the DHCP protocol [9]. This memo is being published now to\n document this protocol for the record.\n\n DRARP is used to acquire (or allocate) a protocol level address given\n the fixed hardware address for a host. Its clients are systems bei 1931 authentication key keys policies subject nested-reference unchanged"},{"id":"IETF RFC 1970","type":"specification","body":"IETF","designation":"RFC 1970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1970.txt","https://www.rfc-editor.org/rfc/rfc1970.pdf"],"folder":"IETF/RFC-1970","files":{"txt":{"path":"standards/IETF/RFC-1970/RFC-1970.txt","sha256":"1c6801883a453351c781bfe8196f4fd19a0f7772da55210bbe632acf98f08479"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers and to maintain reachability information\n about the paths to active neighbors.","scope_keywords":["1970","algorithm","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 1972","folder":"IETF/RFC-1972","source":"IETF/RFC-1972/RFC-1972.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2292","folder":"IETF/RFC-2292","source":"IETF/RFC-2292/RFC-2292.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null}],"search_text":"IETF RFC 1970 This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers and to maintain reachability information\n about the paths to active neighbors. 1970 algorithm path validation nested-reference unchanged"},{"id":"IETF RFC 1971","type":"specification","body":"IETF","designation":"RFC 1971","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1971.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1971.txt","https://www.rfc-editor.org/rfc/rfc1971.pdf"],"folder":"IETF/RFC-1971","files":{"txt":{"path":"standards/IETF/RFC-1971/RFC-1971.txt","sha256":"97fb195f5803965fae3463ba3f3ae298a1dc6549e4325123a5266530656b50ff"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes creating a link-local address and verifying its\n uniqueness on a link, determining what information should be\n autoconfigured (addresses, other information, or both), and in the\n case of addresses, whether they should be obtained through the\n stateless mechanism, the stateful mechanism, or both. This document\n defines the process for generating a link-local address, the process\n for generating site-local and global addresses via stateless address\n autoconfiguration, and the Duplicate Address Detection procedure. The\n details of autoconfiguration using the stateful protocol are\n specified elsewhere.","scope_keywords":["1971","algorithm","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1972","folder":"IETF/RFC-1972","source":"IETF/RFC-1972/RFC-1972.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 1971 This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes creating a link-local address and verifying its\n uniqueness on a link, determining what information should be\n autoconfigured (addresses, other information, or both), and in the\n case of addresses, whether they should be obtained through the\n stateless mechanism, the stateful mechanism, or both. This document\n defines the process for generating a link-local address, the process\n for generating site-local and global addresses via stateless address\n autoconfiguration, and the Duplicate Address Detection procedure. The\n details of autoconfiguration using the stateful protocol are\n specified elsewhere. 1971 algorithm validation nested-reference unchanged"},{"id":"IETF RFC 1972","type":"specification","body":"IETF","designation":"RFC 1972","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1972.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1972.txt","https://www.rfc-editor.org/rfc/rfc1972.pdf"],"folder":"IETF/RFC-1972","files":{"txt":{"path":"standards/IETF/RFC-1972/RFC-1972.txt","sha256":"5186afdbd17b7077f32f61490fa5f256b871683e84c32078949958a7a5618694"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 1972 Fermilab\nCategory: Standards Track August 1996\n\n A Method for the Transmission of IPv6 Packets over Ethernet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo specifies the frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local addresses on\n Ethernet networks. It also specifies the content of the\n Source/Target Link-layer Address option used the the Router\n Solicitation, Router Advertisement, Neighbor Solicitation, and\n Neighbor Advertisement mes","scope_keywords":["1972"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 2073","folder":"IETF/RFC-2073","source":"IETF/RFC-2073/RFC-2073.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 1972 Network Working Group M. Crawford\nRequest for Comments: 1972 Fermilab\nCategory: Standards Track August 1996\n\n A Method for the Transmission of IPv6 Packets over Ethernet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo specifies the frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local addresses on\n Ethernet networks. It also specifies the content of the\n Source/Target Link-layer Address option used the the Router\n Solicitation, Router Advertisement, Neighbor Solicitation, and\n Neighbor Advertisement mes 1972 nested-reference unchanged"},{"id":"IETF RFC 1983","type":"specification","body":"IETF","designation":"RFC 1983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1983.txt","https://www.rfc-editor.org/rfc/rfc1983.pdf"],"folder":"IETF/RFC-1983","files":{"txt":{"path":"standards/IETF/RFC-1983/RFC-1983.txt","sha256":"c582b0d25b0a3bcfec0716af50e99a3be7e84907529ebb1f4530b6fb4718c543"}},"tags":["nested-reference","unchanged"],"summary":"There are many networking glossaries in existence. This glossary\n concentrates on terms which are specific to the Internet. Naturally,\n there are entries for some basic terms and acronyms because other\n entries refer to them.\n\nAcknowledgements\n\n This document is the work of the User Glossary Working Group of the\n User Services Area of the Internet Engineering Task Force. I would\n especially like to thank Ryan Moats/InterNIC for his careful review\n and many contributions to this document.","scope_keywords":["1983","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2350","folder":"IETF/RFC-2350","source":"IETF/RFC-2350/RFC-2350.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2504","folder":"IETF/RFC-2504","source":"IETF/RFC-2504/RFC-2504.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 1983 There are many networking glossaries in existence. This glossary\n concentrates on terms which are specific to the Internet. Naturally,\n there are entries for some basic terms and acronyms because other\n entries refer to them.\n\nAcknowledgements\n\n This document is the work of the User Glossary Working Group of the\n User Services Area of the Internet Engineering Task Force. I would\n especially like to thank Ryan Moats/InterNIC for his careful review\n and many contributions to this document. 1983 policies policy nested-reference unchanged"},{"id":"IETF RFC 2000","type":"specification","body":"IETF","designation":"RFC 2000","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2000.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2000.txt","https://www.rfc-editor.org/rfc/rfc2000.pdf"],"folder":"IETF/RFC-2000","files":{"txt":{"path":"standards/IETF/RFC-2000/RFC-2000.txt","sha256":"b91b48f14c9c665d17c772d392bb0d27c9fbef2e64bd3e5de89e2549dbb4df2e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 2000 J. Postel, Editor\nObsoletes: 1920, 1880, 1800, 1780, 1720, February 1997\n1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. G","scope_keywords":["2000","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 2000 Network Working Group Internet Architecture Board\nRequest for Comments: 2000 J. Postel, Editor\nObsoletes: 1920, 1880, 1800, 1780, 1720, February 1997\n1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. G 2000 risk nested-reference unchanged"},{"id":"IETF RFC 2019","type":"specification","body":"IETF","designation":"RFC 2019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2019.txt","https://www.rfc-editor.org/rfc/rfc2019.pdf"],"folder":"IETF/RFC-2019","files":{"txt":{"path":"standards/IETF/RFC-2019/RFC-2019.txt","sha256":"b0c9c4692104828f9526f48a3f8daa49b1b0306cd81f6b6dfd323a92e396b126"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2019 Fermilab\nCategory: Standards Track October 1996\n\n A Method for the Transmission of IPv6 Packets over FDDI Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo specifies the MTU and frame format for transmission of IPv6\n [IPV6] packets on FDDI networks, including a method for MTU\n determination in the presence of 802.1d bridges to other media. It\n also specifies the method of forming IPv6 link-local addresses on\n FDDI networks and the content of the Source/Target Link-layer Address\n option ","scope_keywords":["2019","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null}],"search_text":"IETF RFC 2019 Network Working Group M. Crawford\nRequest for Comments: 2019 Fermilab\nCategory: Standards Track October 1996\n\n A Method for the Transmission of IPv6 Packets over FDDI Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo specifies the MTU and frame format for transmission of IPv6\n [IPV6] packets on FDDI networks, including a method for MTU\n determination in the presence of 802.1d bridges to other media. It\n also specifies the method of forming IPv6 link-local addresses on\n FDDI networks and the content of the Source/Target Link-layer Address\n option  2019 management path nested-reference unchanged"},{"id":"IETF RFC 2064","type":"specification","body":"IETF","designation":"RFC 2064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2064.txt","https://www.rfc-editor.org/rfc/rfc2064.pdf"],"folder":"IETF/RFC-2064","files":{"txt":{"path":"standards/IETF/RFC-2064/RFC-2064.txt","sha256":"c92c4bc1d2c75b15844484a40102855f13608f79abe1850964d4eff9c064e3c1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, this memo defines managed objects used for obtaining\n traffic flow information from network traffic meters.","scope_keywords":["2064","attribute","attributes","management","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2063","folder":"IETF/RFC-2063","source":"IETF/RFC-2063/RFC-2063.txt","version":null},{"body":"IETF","designation":"RFC 2123","folder":"IETF/RFC-2123","source":"IETF/RFC-2123/RFC-2123.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null}],"search_text":"IETF RFC 2064 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, this memo defines managed objects used for obtaining\n traffic flow information from network traffic meters. 2064 attribute attributes management registered subject nested-reference unchanged"},{"id":"IETF RFC 2132","type":"specification","body":"IETF","designation":"RFC 2132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2132.txt","https://www.rfc-editor.org/rfc/rfc2132.pdf"],"folder":"IETF/RFC-2132","files":{"txt":{"path":"standards/IETF/RFC-2132/RFC-2132.txt","sha256":"0cfbedab7cfe859624ae78c07a722bc51bf8ea123a7b43b099fc546ddcf00b90"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) [1] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. Configuration parameters and other control information are\n carried in tagged data items that are stored in the 'options' field\n of the DHCP message. The data items themselves are also called\n \"options.\"\n\n This document specifies the current set of DHCP options. Future\n options will be specified in separate RFCs. The current list of\n valid options is also available in ftp://ftp.isi.edu/in-\n notes/iana/assignments [22].\n\n All of the vendor information extensions defined in RFC 1497 [2] may\n be used as DHCP options. The definitions given in RFC 1497 are\n included in this document, which supersedes RFC 1497. All of the\n DHCP options defined in this document, except for those specific to\n DHCP as defined in section 9, may be used as BOOTP vendor inform","scope_keywords":["2132"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2489","folder":"IETF/RFC-2489","source":"IETF/RFC-2489/RFC-2489.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 2937","folder":"IETF/RFC-2937","source":"IETF/RFC-2937/RFC-2937.txt","version":null},{"body":"IETF","designation":"RFC 2939","folder":"IETF/RFC-2939","source":"IETF/RFC-2939/RFC-2939.txt","version":null},{"body":"IETF","designation":"RFC 3004","folder":"IETF/RFC-3004","source":"IETF/RFC-3004/RFC-3004.txt","version":null},{"body":"IETF","designation":"RFC 3011","folder":"IETF/RFC-3011","source":"IETF/RFC-3011/RFC-3011.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3396","folder":"IETF/RFC-3396","source":"IETF/RFC-3396/RFC-3396.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3898","folder":"IETF/RFC-3898","source":"IETF/RFC-3898/RFC-3898.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4075","folder":"IETF/RFC-4075","source":"IETF/RFC-4075/RFC-4075.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4361","folder":"IETF/RFC-4361","source":"IETF/RFC-4361/RFC-4361.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6355","folder":"IETF/RFC-6355","source":"IETF/RFC-6355/RFC-6355.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 2132 The Dynamic Host Configuration Protocol (DHCP) [1] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. Configuration parameters and other control information are\n carried in tagged data items that are stored in the 'options' field\n of the DHCP message. The data items themselves are also called\n \"options.\"\n\n This document specifies the current set of DHCP options. Future\n options will be specified in separate RFCs. The current list of\n valid options is also available in ftp://ftp.isi.edu/in-\n notes/iana/assignments [22].\n\n All of the vendor information extensions defined in RFC 1497 [2] may\n be used as DHCP options. The definitions given in RFC 1497 are\n included in this document, which supersedes RFC 1497. All of the\n DHCP options defined in this document, except for those specific to\n DHCP as defined in section 9, may be used as BOOTP vendor inform 2132 nested-reference unchanged"},{"id":"IETF RFC 2153","type":"specification","body":"IETF","designation":"RFC 2153","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2153.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2153.txt","https://www.rfc-editor.org/rfc/rfc2153.pdf"],"folder":"IETF/RFC-2153","files":{"txt":{"path":"standards/IETF/RFC-2153/RFC-2153.txt","sha256":"932d168cfab2d022f0a3def121b9369f0bcacb905d3614676ec6727fa7d1dcf5"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) for establishing,\n configuring, and testing the data-link connection; and a family of\n Network Control Protocols (NCPs) for establishing and configuring\n different network-layer protocols.\n\n This document defines a general mechanism for proprietary vendor\n extensions.\n\nSimpson Informational [Page i]\n\nRFC 2153 PPP vendor extensions May 1997","scope_keywords":["2153","algorithm","algorithms","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 2153 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) for establishing,\n configuring, and testing the data-link connection; and a family of\n Network Control Protocols (NCPs) for establishing and configuring\n different network-layer protocols.\n\n This document defines a general mechanism for proprietary vendor\n extensions.\n\nSimpson Informational [Page i]\n\nRFC 2153 PPP vendor extensions May 1997 2153 algorithm algorithms attribute attributes nested-reference unchanged"},{"id":"IETF RFC 2200","type":"specification","body":"IETF","designation":"RFC 2200","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2200.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2200.txt","https://www.rfc-editor.org/rfc/rfc2200.pdf"],"folder":"IETF/RFC-2200","files":{"txt":{"path":"standards/IETF/RFC-2200/RFC-2200.txt","sha256":"84a5a5f8e5c77a1f34e8b4cf16ea8057427ef5657a282346899542f78f6e3b68"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 2200 J. Postel, Editor\nObsoletes: 2000, 1920, 1880, 1800, 1780, June 1997\n1720, 1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2.","scope_keywords":["2200","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 2629","folder":"IETF/RFC-2629","source":"IETF/RFC-2629/RFC-2629.txt","version":null}],"search_text":"IETF RFC 2200 Network Working Group Internet Architecture Board\nRequest for Comments: 2200 J. Postel, Editor\nObsoletes: 2000, 1920, 1880, 1800, 1780, June 1997\n1720, 1610, 1600, 1540, 1500, 1410, 1360,\n1280, 1250, 1200, 1140, 1130, 1100, 1083\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . . 5\n 3. Other Reference Documents . . . . . . . . . . . . . . . . . 6\n 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6\n 3.2. 2200 risk nested-reference unchanged"},{"id":"IETF RFC 2225","type":"specification","body":"IETF","designation":"RFC 2225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2225.txt","https://www.rfc-editor.org/rfc/rfc2225.pdf"],"folder":"IETF/RFC-2225","files":{"txt":{"path":"standards/IETF/RFC-2225/RFC-2225.txt","sha256":"730397c7ef60dfc71a77937d43e77874a4fc8e8878dd530ec8133e0c1c5bc4ac"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an initial application of classical IP and ARP in\n an Asynchronous Transfer Mode (ATM) network environment configured as\n a Logical IP Subnetwork (LIS) as described in Section 5. This memo\n does not preclude the subsequent development of ATM technology into\n areas other than a LIS; specifically, as single ATM networks grow to\n replace many Ethernet local LAN segments and as these networks become\n globally connected, the application of IP and ARP will be treated\n differently. This memo considers only the application of ATM as a\n direct replacement for the \"wires\" and local LAN segments connecting\n IP end-stations (\"members\") and routers operating in the \"classical\"\n LAN-based paradigm. Issues raised by MAC level bridging and LAN\n emulation are beyond the scope of this paper.\n\n This memo introduces general ATM technology and nomenclature.\n Readers are encouraged to review","scope_keywords":["2225","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2601","folder":"IETF/RFC-2601","source":"IETF/RFC-2601/RFC-2601.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null}],"search_text":"IETF RFC 2225 This memo defines an initial application of classical IP and ARP in\n an Asynchronous Transfer Mode (ATM) network environment configured as\n a Logical IP Subnetwork (LIS) as described in Section 5. This memo\n does not preclude the subsequent development of ATM technology into\n areas other than a LIS; specifically, as single ATM networks grow to\n replace many Ethernet local LAN segments and as these networks become\n globally connected, the application of IP and ARP will be treated\n differently. This memo considers only the application of ATM as a\n direct replacement for the \"wires\" and local LAN segments connecting\n IP end-stations (\"members\") and routers operating in the \"classical\"\n LAN-based paradigm. Issues raised by MAC level bridging and LAN\n emulation are beyond the scope of this paper.\n\n This memo introduces general ATM technology and nomenclature.\n Readers are encouraged to review 2225 key path nested-reference unchanged"},{"id":"IETF RFC 2338","type":"specification","body":"IETF","designation":"RFC 2338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2338.txt","https://www.rfc-editor.org/rfc/rfc2338.pdf"],"folder":"IETF/RFC-2338","files":{"txt":{"path":"standards/IETF/RFC-2338/RFC-2338.txt","sha256":"6c5a8158ee3a1789e2dd58fb6e35dcd03f772d495b84f053fc4d7bb1b23a5363"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Virtual Router Redundancy Protocol (VRRP).\n VRRP specifies an election protocol that dynamically assigns\n responsibility for a virtual router to one of the VRRP routers on a\n LAN. The VRRP router controlling the IP address(es) associated with\n a virtual router is called the Master, and forwards packets sent to\n these IP addresses. The election process provides dynamic fail over\n in the forwarding responsibility should the Master become\n unavailable. This allows any of the virtual router IP addresses on\n the LAN to be used as the default first hop router by end-hosts. The\n advantage gained from using VRRP is a higher availability default\n path without requiring configuration of dynamic routing or router\n discovery protocols on every end-host.\n\nKnight, et. al. Standards Track [Page 1]\n\f\nRFC 2338 VRRP April 1998","scope_keywords":["2338","authentication","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null}],"search_text":"IETF RFC 2338 This memo defines the Virtual Router Redundancy Protocol (VRRP).\n VRRP specifies an election protocol that dynamically assigns\n responsibility for a virtual router to one of the VRRP routers on a\n LAN. The VRRP router controlling the IP address(es) associated with\n a virtual router is called the Master, and forwards packets sent to\n these IP addresses. The election process provides dynamic fail over\n in the forwarding responsibility should the Master become\n unavailable. This allows any of the virtual router IP addresses on\n the LAN to be used as the default first hop router by end-hosts. The\n advantage gained from using VRRP is a higher availability default\n path without requiring configuration of dynamic routing or router\n discovery protocols on every end-host.\n\nKnight, et. al. Standards Track [Page 1]\n\f\nRFC 2338 VRRP April 1998 2338 authentication key path nested-reference unchanged"},{"id":"IETF RFC 2386","type":"specification","body":"IETF","designation":"RFC 2386","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2386.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2386.txt","https://www.rfc-editor.org/rfc/rfc2386.pdf"],"folder":"IETF/RFC-2386","files":{"txt":{"path":"standards/IETF/RFC-2386/RFC-2386.txt","sha256":"2f10cf4fd48d5c9e42952f95451e41a58f1ecd3609db8b78e02b479c3bdd484e"}},"tags":["nested-reference","unchanged"],"summary":"QoS-based routing has been recognized as a missing piece in the\n evolution of QoS-based service offerings in the Internet. This\n document describes some of the QoS-based routing issues and\n requirements, and proposes a framework for QoS-based routing in the\n Internet. This framework is based on extending the current Internet\n routing model of intra and interdomain routing to support QoS.\n\n1. SCOPE OF DOCUMENT & PHILOSOPHY\n\n This document proposes a framework for QoS-based routing, with the\n objective of fostering the development of an Internet-wide solution\n while encouraging innovations in solving the many problems that\n arise. QoS-based routing has many complex facets and it is\n recommended that the following two-pronged approach be employed\n towards its development:\n\n 1. Encourage the growth and evolution of novel intradomain QoS-based\n routing architectures. This is to allow the deve","scope_keywords":["2386","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2702","folder":"IETF/RFC-2702","source":"IETF/RFC-2702/RFC-2702.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null}],"search_text":"IETF RFC 2386 QoS-based routing has been recognized as a missing piece in the\n evolution of QoS-based service offerings in the Internet. This\n document describes some of the QoS-based routing issues and\n requirements, and proposes a framework for QoS-based routing in the\n Internet. This framework is based on extending the current Internet\n routing model of intra and interdomain routing to support QoS.\n\n1. SCOPE OF DOCUMENT & PHILOSOPHY\n\n This document proposes a framework for QoS-based routing, with the\n objective of fostering the development of an Internet-wide solution\n while encouraging innovations in solving the many problems that\n arise. QoS-based routing has many complex facets and it is\n recommended that the following two-pronged approach be employed\n towards its development:\n\n 1. Encourage the growth and evolution of novel intradomain QoS-based\n routing architectures. This is to allow the deve 2386 path policy nested-reference unchanged"},{"id":"IETF RFC 2400","type":"specification","body":"IETF","designation":"RFC 2400","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2400.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2400.txt","https://www.rfc-editor.org/rfc/rfc2400.pdf"],"folder":"IETF/RFC-2400","files":{"txt":{"path":"standards/IETF/RFC-2400/RFC-2400.txt","sha256":"ced94cf05a7b54b1a20cdd3b663dabf2415199e2ab386391f8c19f68929a4a42"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 2400 J. Postel\nObsoletes: 2300, 2200, 2000, 1920, 1880, J. Reynolds\n1800, 1780, 1720, 1610, 1600, 1540, 1500, 1410, Editors\n1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 September 1998\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . 5\n 3. Other Reference Documents .","scope_keywords":["2400","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null}],"search_text":"IETF RFC 2400 Network Working Group Internet Architecture Board\nRequest for Comments: 2400 J. Postel\nObsoletes: 2300, 2200, 2000, 1920, 1880, J. Reynolds\n1800, 1780, 1720, 1610, 1600, 1540, 1500, 1410, Editors\n1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 September 1998\nSTD: 1\nCategory: Standards Track\n\n INTERNET OFFICIAL PROTOCOL STANDARDS\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Architecture Board (IAB).\n This memo is an Internet Standard. Distribution of this memo is\n unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1. The Standardization Process . . . . . . . . . . . . . . . 3\n 2. The Request for Comments Documents . . . . . . . . . . . . 5\n 3. Other Reference Documents . 2400 risk nested-reference unchanged"},{"id":"IETF RFC 2427","type":"specification","body":"IETF","designation":"RFC 2427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2427.txt","https://www.rfc-editor.org/rfc/rfc2427.pdf"],"folder":"IETF/RFC-2427","files":{"txt":{"path":"standards/IETF/RFC-2427/RFC-2427.txt","sha256":"5c5a71a59d4280039c680a6cfd14e83e35c15133e8cc94827873e99c231f74a4"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing.\n\n Systems with the ability to transfer both the encapsulation method\n described in this document, and others must have a priori knowledge\n of which virtual circuits will carry which encapsulation method and\n this encapsulation must only be used over virtual circuits that have\n been explicitly configured for its use.\n\nAcknowledgments\n\n This document could not have been completed without the support of\n Terry Bradley of Avici Systems, Inc.. Comments and contributions\n from many sources, especially those from Ray Samora of Proteon, Ken\n Rehbehn of Visual Networks, Fred Baker and Charles Carvalho of Cisco\n Systems, and Mostafa Sherif of AT&T have been incorporated into this\n document. Special thanks to Dory Leifer of University o","scope_keywords":["2427","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2795","folder":"IETF/RFC-2795","source":"IETF/RFC-2795/RFC-2795.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2427 This memo describes an encapsulation method for carrying network\n interconnect traffic over a Frame Relay backbone. It covers aspects\n of both Bridging and Routing.\n\n Systems with the ability to transfer both the encapsulation method\n described in this document, and others must have a priori knowledge\n of which virtual circuits will carry which encapsulation method and\n this encapsulation must only be used over virtual circuits that have\n been explicitly configured for its use.\n\nAcknowledgments\n\n This document could not have been completed without the support of\n Terry Bradley of Avici Systems, Inc.. Comments and contributions\n from many sources, especially those from Ray Samora of Proteon, Ken\n Rehbehn of Visual Networks, Fred Baker and Charles Carvalho of Cisco\n Systems, and Mostafa Sherif of AT&T have been incorporated into this\n document. Special thanks to Dory Leifer of University o 2427 key pid nested-reference unchanged"},{"id":"IETF RFC 2461","type":"specification","body":"IETF","designation":"RFC 2461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2461.txt","https://www.rfc-editor.org/rfc/rfc2461.pdf"],"folder":"IETF/RFC-2461","files":{"txt":{"path":"standards/IETF/RFC-2461/RFC-2461.txt","sha256":"6b24fb8f23e515cb2bb115b26a1b4b93127350cedb280dbaac333d86b71a6695"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers and to maintain reachability information\n about the paths to active neighbors.","scope_keywords":["2461","algorithm","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2469","folder":"IETF/RFC-2469","source":"IETF/RFC-2469/RFC-2469.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3590","folder":"IETF/RFC-3590","source":"IETF/RFC-3590/RFC-3590.txt","version":null},{"body":"IETF","designation":"RFC 3627","folder":"IETF/RFC-3627","source":"IETF/RFC-3627/RFC-3627.txt","version":null},{"body":"IETF","designation":"RFC 3633","folder":"IETF/RFC-3633","source":"IETF/RFC-3633/RFC-3633.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3756","folder":"IETF/RFC-3756","source":"IETF/RFC-3756/RFC-3756.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4076","folder":"IETF/RFC-4076","source":"IETF/RFC-4076/RFC-4076.txt","version":null},{"body":"IETF","designation":"RFC 4135","folder":"IETF/RFC-4135","source":"IETF/RFC-4135/RFC-4135.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4311","folder":"IETF/RFC-4311","source":"IETF/RFC-4311/RFC-4311.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4554","folder":"IETF/RFC-4554","source":"IETF/RFC-4554/RFC-4554.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4943","folder":"IETF/RFC-4943","source":"IETF/RFC-4943/RFC-4943.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 2461 This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers and to maintain reachability information\n about the paths to active neighbors. 2461 algorithm path validation nested-reference unchanged"},{"id":"IETF RFC 2462","type":"specification","body":"IETF","designation":"RFC 2462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2462.txt","https://www.rfc-editor.org/rfc/rfc2462.pdf"],"folder":"IETF/RFC-2462","files":{"txt":{"path":"standards/IETF/RFC-2462/RFC-2462.txt","sha256":"6a92ab0b4159b5b79d6d8bd07368099e6d6b2318289c8d7fb5644a572f7aa975"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes creating a link-local address and verifying its\n uniqueness on a link, determining what information should be\n autoconfigured (addresses, other information, or both), and in the\n case of addresses, whether they should be obtained through the\n stateless mechanism, the stateful mechanism, or both. This document\n defines the process for generating a link-local address, the process\n for generating site-local and global addresses via stateless address\n autoconfiguration, and the Duplicate Address Detection procedure. The\n details of autoconfiguration using the stateful protocol are\n specified elsewhere.","scope_keywords":["2462","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3590","folder":"IETF/RFC-3590","source":"IETF/RFC-3590/RFC-3590.txt","version":null},{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3756","folder":"IETF/RFC-3756","source":"IETF/RFC-3756/RFC-3756.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4057","folder":"IETF/RFC-4057","source":"IETF/RFC-4057/RFC-4057.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4076","folder":"IETF/RFC-4076","source":"IETF/RFC-4076/RFC-4076.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4242","folder":"IETF/RFC-4242","source":"IETF/RFC-4242/RFC-4242.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null}],"search_text":"IETF RFC 2462 This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes creating a link-local address and verifying its\n uniqueness on a link, determining what information should be\n autoconfigured (addresses, other information, or both), and in the\n case of addresses, whether they should be obtained through the\n stateless mechanism, the stateful mechanism, or both. This document\n defines the process for generating a link-local address, the process\n for generating site-local and global addresses via stateless address\n autoconfiguration, and the Duplicate Address Detection procedure. The\n details of autoconfiguration using the stateful protocol are\n specified elsewhere. 2462 subject validation nested-reference unchanged"},{"id":"IETF RFC 2464","type":"specification","body":"IETF","designation":"RFC 2464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2464.txt","https://www.rfc-editor.org/rfc/rfc2464.pdf"],"folder":"IETF/RFC-2464","files":{"txt":{"path":"standards/IETF/RFC-2464/RFC-2464.txt","sha256":"f9554329ef1f4e093513e5b6f7af00bb5d206710e0c61d08bd578fa5f00aee9a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2464 Fermilab\nObsoletes: 1972 December 1998\nCategory: Standards Track\n\n Transmission of IPv6 Packets over Ethernet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on Ethernet networks. It also\n specifies the content of the Source/Target Link-layer ","scope_keywords":["2464","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2469","folder":"IETF/RFC-2469","source":"IETF/RFC-2469/RFC-2469.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 6085","folder":"IETF/RFC-6085","source":"IETF/RFC-6085/RFC-6085.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 2464 Network Working Group M. Crawford\nRequest for Comments: 2464 Fermilab\nObsoletes: 1972 December 1998\nCategory: Standards Track\n\n Transmission of IPv6 Packets over Ethernet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on Ethernet networks. It also\n specifies the content of the Source/Target Link-layer  2464 key management nested-reference unchanged"},{"id":"IETF RFC 2467","type":"specification","body":"IETF","designation":"RFC 2467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2467.txt","https://www.rfc-editor.org/rfc/rfc2467.pdf"],"folder":"IETF/RFC-2467","files":{"txt":{"path":"standards/IETF/RFC-2467/RFC-2467.txt","sha256":"033f864c1ef951d27eedfecc051385d32eab4eb8f1180726431fe190a50f2d3d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2467 Fermilab\nObsoletes: 2019 December 1998\nCategory: Standards Track\n\n Transmission of IPv6 Packets over FDDI Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on FDDI networks. It also\n specifies the content of the Source/Target Link-layer Address ","scope_keywords":["2467","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2469","folder":"IETF/RFC-2469","source":"IETF/RFC-2469/RFC-2469.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2467 Network Working Group M. Crawford\nRequest for Comments: 2467 Fermilab\nObsoletes: 2019 December 1998\nCategory: Standards Track\n\n Transmission of IPv6 Packets over FDDI Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies the frame format for transmission of IPv6\n packets and the method of forming IPv6 link-local addresses and\n statelessly autoconfigured addresses on FDDI networks. It also\n specifies the content of the Source/Target Link-layer Address  2467 key management path nested-reference unchanged"},{"id":"IETF RFC 2470","type":"specification","body":"IETF","designation":"RFC 2470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2470.txt","https://www.rfc-editor.org/rfc/rfc2470.pdf"],"folder":"IETF/RFC-2470","files":{"txt":{"path":"standards/IETF/RFC-2470/RFC-2470.txt","sha256":"4a40f5cdfc98dff9284eb2e621a190da7e50c322fa71bb39aac238dc211e589e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2470 Fermilab\nCategory: Standards Track T. Narten\n IBM\n S. Thomas\n TransNexus\n December 1998\n\n Transmission of IPv6 Packets over Token Ring Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo specifies the MTU and frame format for transmission of IPv6\n packets on Token Ring networks. It also specifies the method of\n forming IPv6 link-local addresses on Token Ring networks and the\n content of the Source/Targe","scope_keywords":["2470","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2469","folder":"IETF/RFC-2469","source":"IETF/RFC-2469/RFC-2469.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2470 Network Working Group M. Crawford\nRequest for Comments: 2470 Fermilab\nCategory: Standards Track T. Narten\n IBM\n S. Thomas\n TransNexus\n December 1998\n\n Transmission of IPv6 Packets over Token Ring Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo specifies the MTU and frame format for transmission of IPv6\n packets on Token Ring networks. It also specifies the method of\n forming IPv6 link-local addresses on Token Ring networks and the\n content of the Source/Targe 2470 key path nested-reference unchanged"},{"id":"IETF RFC 2518","type":"specification","body":"IETF","designation":"RFC 2518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2518.txt","https://www.rfc-editor.org/rfc/rfc2518.pdf"],"folder":"IETF/RFC-2518","files":{"txt":{"path":"standards/IETF/RFC-2518/RFC-2518.txt","sha256":"64edb8d7a9a9a2fb1fbbfe131a600cde15b22f4f746f1e57eccfdbdf0ee8f63f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of methods, headers, and content-types\n ancillary to HTTP/1.1 for the management of resource properties,\n creation and management of resource collections, namespace\n manipulation, and resource locking (collision avoidance).","scope_keywords":["2518","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4331","folder":"IETF/RFC-4331","source":"IETF/RFC-4331/RFC-4331.txt","version":null},{"body":"IETF","designation":"RFC 4437","folder":"IETF/RFC-4437","source":"IETF/RFC-4437/RFC-4437.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null}],"search_text":"IETF RFC 2518 This document specifies a set of methods, headers, and content-types\n ancillary to HTTP/1.1 for the management of resource properties,\n creation and management of resource collections, namespace\n manipulation, and resource locking (collision avoidance). 2518 http management nested-reference unchanged"},{"id":"IETF RFC 2522","type":"specification","body":"IETF","designation":"RFC 2522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2522.txt","https://www.rfc-editor.org/rfc/rfc2522.pdf"],"folder":"IETF/RFC-2522","files":{"txt":{"path":"standards/IETF/RFC-2522/RFC-2522.txt","sha256":"9da6331f298e00ff02eca8e217825d1c160be3662c0df415d41522410251a263"}},"tags":["nested-reference","unchanged"],"summary":"Photuris is a session-key management protocol intended for use with\n the IP Security Protocols (AH and ESP). This document defines the\n basic protocol mechanisms.\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2522 Photuris Protocol March 1999","scope_keywords":["2522","attribute","attributes","authentication","hash","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 2522 Photuris is a session-key management protocol intended for use with\n the IP Security Protocols (AH and ESP). This document defines the\n basic protocol mechanisms.\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2522 Photuris Protocol March 1999 2522 attribute attributes authentication hash identification key management nested-reference unchanged"},{"id":"IETF RFC 2684","type":"specification","body":"IETF","designation":"RFC 2684","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2684.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2684.txt","https://www.rfc-editor.org/rfc/rfc2684.pdf"],"folder":"IETF/RFC-2684","files":{"txt":{"path":"standards/IETF/RFC-2684/RFC-2684.txt","sha256":"d8bbecb6c6816aecd891c06f1471f861c6823748c8dad7a3591e5b05f5fd1b3e"}},"tags":["nested-reference","unchanged"],"summary":"This memo replaces RFC 1483. It describes two encapsulations methods\n for carrying network interconnect traffic over AAL type 5 over ATM.\n The first method allows multiplexing of multiple protocols over a\n single ATM virtual connection whereas the second method assumes that\n each protocol is carried over a separate ATM virtual connection.\n\nApplicability\n\n This specification is intended to be used in implementations which\n use ATM networks to carry multiprotocol traffic among hosts, routers\n and bridges which are ATM end systems.\n\n1. Introduction\n\n Asynchronous Transfer Mode (ATM) wide area, campus and local area\n networks are used to transport IP datagrams and other connectionless\n traffic between hosts, routers, bridges and other networking devices.\n This memo describes two methods for carrying connectionless routed\n and bridged Protocol Data Units (PDUs) over an ATM network. The \"LLC\n ","scope_keywords":["2684","delivery","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2685","folder":"IETF/RFC-2685","source":"IETF/RFC-2685/RFC-2685.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2684 This memo replaces RFC 1483. It describes two encapsulations methods\n for carrying network interconnect traffic over AAL type 5 over ATM.\n The first method allows multiplexing of multiple protocols over a\n single ATM virtual connection whereas the second method assumes that\n each protocol is carried over a separate ATM virtual connection.\n\nApplicability\n\n This specification is intended to be used in implementations which\n use ATM networks to carry multiprotocol traffic among hosts, routers\n and bridges which are ATM end systems.\n\n1. Introduction\n\n Asynchronous Transfer Mode (ATM) wide area, campus and local area\n networks are used to transport IP datagrams and other connectionless\n traffic between hosts, routers, bridges and other networking devices.\n This memo describes two methods for carrying connectionless routed\n and bridged Protocol Data Units (PDUs) over an ATM network. The \"LLC\n  2684 delivery key pid nested-reference unchanged"},{"id":"IETF RFC 2720","type":"specification","body":"IETF","designation":"RFC 2720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2720.txt","https://www.rfc-editor.org/rfc/rfc2720.pdf"],"folder":"IETF/RFC-2720","files":{"txt":{"path":"standards/IETF/RFC-2720/RFC-2720.txt","sha256":"9fc8810572044f1e80540db3f96669da586dd3fe3cd17d99c16c3586550d87b0"}},"tags":["nested-reference","unchanged"],"summary":"The RTFM Traffic Measurement Architecture provides a general\n framework for describing and measuring network traffic flows. Flows\n are defined in terms of their Address Attribute values and measured\n by a 'Traffic Meter'.\n\n This document defines a Management Information Base (MIB) for use in\n controlling an RTFM Traffic Meter, in particular for specifying the\n flows to be measured. It also provides an efficient mechanism for\n retrieving flow data from the meter using SNMP. Security issues\n concerning the operation of traffic meters are summarised.","scope_keywords":["2720","attribute","attributes","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2723","folder":"IETF/RFC-2723","source":"IETF/RFC-2723/RFC-2723.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null}],"search_text":"IETF RFC 2720 The RTFM Traffic Measurement Architecture provides a general\n framework for describing and measuring network traffic flows. Flows\n are defined in terms of their Address Attribute values and measured\n by a 'Traffic Meter'.\n\n This document defines a Management Information Base (MIB) for use in\n controlling an RTFM Traffic Meter, in particular for specifying the\n flows to be measured. It also provides an efficient mechanism for\n retrieving flow data from the meter using SNMP. Security issues\n concerning the operation of traffic meters are summarised. 2720 attribute attributes management registered nested-reference unchanged"},{"id":"IETF RFC 2814","type":"specification","body":"IETF","designation":"RFC 2814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2814.txt","https://www.rfc-editor.org/rfc/rfc2814.pdf"],"folder":"IETF/RFC-2814","files":{"txt":{"path":"standards/IETF/RFC-2814/RFC-2814.txt","sha256":"5a1d3184f4a1e391bd7427cbf5f0d8a3dac5593044cb8f19a64936eb850e62be"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a signaling method and protocol for RSVP-\n based admission control over IEEE 802-style LANs. The protocol is\n designed to work both with the current generation of IEEE 802 LANs as\n well as with the recent work completed by the IEEE 802.1 committee.\n\n1. Introduction\n\n New extensions to the Internet architecture and service models have\n been defined for an integrated services Internet [RFC-1633, RFC-2205,\n RFC-2210] so that applications can request specific qualities or\n levels of service from an internetwork in addition to the current IP\n best-effort service. These extensions include RSVP, a resource\n reservation setup protocol, and definition of new service classes to\n be supported by Integrated Services routers. RSVP and service class\n definitions are largely independent of the underlying networking\n technologies and it is necessary to define the mapping of RSVP ","scope_keywords":["2814","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null}],"search_text":"IETF RFC 2814 This document describes a signaling method and protocol for RSVP-\n based admission control over IEEE 802-style LANs. The protocol is\n designed to work both with the current generation of IEEE 802 LANs as\n well as with the recent work completed by the IEEE 802.1 committee.\n\n1. Introduction\n\n New extensions to the Internet architecture and service models have\n been defined for an integrated services Internet [RFC-1633, RFC-2205,\n RFC-2210] so that applications can request specific qualities or\n levels of service from an internetwork in addition to the current IP\n best-effort service. These extensions include RSVP, a resource\n reservation setup protocol, and definition of new service classes to\n be supported by Integrated Services routers. RSVP and service class\n definitions are largely independent of the underlying networking\n technologies and it is necessary to define the mapping of RSVP  2814 management nested-reference unchanged"},{"id":"IETF RFC 2815","type":"specification","body":"IETF","designation":"RFC 2815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2815.txt","https://www.rfc-editor.org/rfc/rfc2815.pdf"],"folder":"IETF/RFC-2815","files":{"txt":{"path":"standards/IETF/RFC-2815/RFC-2815.txt","sha256":"9d49c7b0ecb9df753a545ce901ad88fcd3660a9125475360f1fa7423f719e6f7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes mappings of IETF Integrated Services over\n LANs built from IEEE 802 network segments which may be interconnected\n by IEEE 802.1D MAC Bridges (switches). It describes parameter\n mappings for supporting Controlled Load and Guaranteed Service using\n the inherent capabilities of relevant IEEE 802 technologies and, in\n particular, 802.1D-1998 queuing features in switches.\n\n These mappings are one component of the Integrated Services over IEEE\n 802 LANs framework.\n\nSeaman, et al. Standards Track [Page 1]\n\f\nRFC 2815 Int-Serv Mappings on IEEE 802 Networks May 2000","scope_keywords":["2815","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2815 This document describes mappings of IETF Integrated Services over\n LANs built from IEEE 802 network segments which may be interconnected\n by IEEE 802.1D MAC Bridges (switches). It describes parameter\n mappings for supporting Controlled Load and Guaranteed Service using\n the inherent capabilities of relevant IEEE 802 technologies and, in\n particular, 802.1D-1998 queuing features in switches.\n\n These mappings are one component of the Integrated Services over IEEE\n 802 LANs framework.\n\nSeaman, et al. Standards Track [Page 1]\n\f\nRFC 2815 Int-Serv Mappings on IEEE 802 Networks May 2000 2815 identification path nested-reference unchanged"},{"id":"IETF RFC 2816","type":"specification","body":"IETF","designation":"RFC 2816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2816.txt","https://www.rfc-editor.org/rfc/rfc2816.pdf"],"folder":"IETF/RFC-2816","files":{"txt":{"path":"standards/IETF/RFC-2816/RFC-2816.txt","sha256":"dc5e871a6e643d1a2fd5877c4e98956a2dd67aab8abf0d6ac5ce940699cfa0ea"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a framework for supporting IETF Integrated\n Services on shared and switched LAN infrastructure. It includes\n background material on the capabilities of IEEE 802 like networks\n with regard to parameters that affect Integrated Services such as\n access latency, delay variation and queuing support in LAN switches.\n It discusses aspects of IETF's Integrated Services model that cannot\n easily be accommodated in different LAN environments. It outlines a\n functional model for supporting the Resource Reservation Protocol\n (RSVP) in such LAN environments. Details of extensions to RSVP for\n use over LANs are described in an accompanying memo [14]. Mappings\n of the various Integrated Services onto IEEE 802 LANs are described\n in another memo [13].\n\nGhanwani, et al. Informational [Page 1]\n\f\nRFC 2816 Framework for Int-Serv Over IEEE 802 LAN May 2000\n\nContents\n\n 1. Introduction . . ","scope_keywords":["2816"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null}],"search_text":"IETF RFC 2816 This memo describes a framework for supporting IETF Integrated\n Services on shared and switched LAN infrastructure. It includes\n background material on the capabilities of IEEE 802 like networks\n with regard to parameters that affect Integrated Services such as\n access latency, delay variation and queuing support in LAN switches.\n It discusses aspects of IETF's Integrated Services model that cannot\n easily be accommodated in different LAN environments. It outlines a\n functional model for supporting the Resource Reservation Protocol\n (RSVP) in such LAN environments. Details of extensions to RSVP for\n use over LANs are described in an accompanying memo [14]. Mappings\n of the various Integrated Services onto IEEE 802 LANs are described\n in another memo [13].\n\nGhanwani, et al. Informational [Page 1]\n\f\nRFC 2816 Framework for Int-Serv Over IEEE 802 LAN May 2000\n\nContents\n\n 1. Introduction . .  2816 nested-reference unchanged"},{"id":"IETF RFC 2834","type":"specification","body":"IETF","designation":"RFC 2834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2834.txt","https://www.rfc-editor.org/rfc/rfc2834.pdf"],"folder":"IETF/RFC-2834","files":{"txt":{"path":"standards/IETF/RFC-2834/RFC-2834.txt","sha256":"5a12c7abada89f71e67cdf23813830ea6a88c3b9d11072d91538828d61f4bd05"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for resolving IP addresses to ANSI\n High-Performance Parallel Interface (HIPPI) hardware addresses and\n for emulating IP broadcast in a logical IP subnet (LIS) as a direct\n extension of HARP. This memo defines a HARP that will interoperate\n between HIPPI-800 and HIPPI-6400 (also known as Gigabyte System\n Network, GSN). This document (when combined with RFC-2067 \"IP over\n HIPPI\") obsoletes RFC-1374.","scope_keywords":["2834","algorithm","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 2834 This document specifies a method for resolving IP addresses to ANSI\n High-Performance Parallel Interface (HIPPI) hardware addresses and\n for emulating IP broadcast in a logical IP subnet (LIS) as a direct\n extension of HARP. This memo defines a HARP that will interoperate\n between HIPPI-800 and HIPPI-6400 (also known as Gigabyte System\n Network, GSN). This document (when combined with RFC-2067 \"IP over\n HIPPI\") obsoletes RFC-1374. 2834 algorithm http key nested-reference unchanged"},{"id":"IETF RFC 2835","type":"specification","body":"IETF","designation":"RFC 2835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2835.txt","https://www.rfc-editor.org/rfc/rfc2835.pdf"],"folder":"IETF/RFC-2835","files":{"txt":{"path":"standards/IETF/RFC-2835/RFC-2835.txt","sha256":"a61df3b0b8b23cbb53e59f743df401709d93429094470f7401409a5c38937ff3"}},"tags":["nested-reference","unchanged"],"summary":"The ANSI T11.1 task force has standardized HIPPI-6400 also known as\n Gigabyte System Network (GSN), a physical-level, point-to-point,\n full-duplex, link interface for reliable, flow-controlled,\n transmission of user data at 6400 Mbit/s, per direction. A parallel\n copper cable interface for distances of up to 40 m is specified in\n HIPPI-6400-PH [1]. Connections to a longer-distance optical\n interface are standardized in HIPPI-6400-OPT [3].\n\n HIPPI-6400-PH [1] defines the encapsulation of IEEE 802.2 LLC PDUs\n [10] and by implication, IP on GSN. Another T11.1 standard describes\n the operation of HIPPI-6400 physical switches HIPPI-6400-SC [2].\n T11.1 chose to leave HIPPI-6400 networking issues largely outside the\n scope of their standards; this document specifies the use of HIPPI-\n 6400 switches as IP local area networks. This document further\n specifies a method for resolving IP addresses t","scope_keywords":["2835","algorithm","delivery","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 2835 The ANSI T11.1 task force has standardized HIPPI-6400 also known as\n Gigabyte System Network (GSN), a physical-level, point-to-point,\n full-duplex, link interface for reliable, flow-controlled,\n transmission of user data at 6400 Mbit/s, per direction. A parallel\n copper cable interface for distances of up to 40 m is specified in\n HIPPI-6400-PH [1]. Connections to a longer-distance optical\n interface are standardized in HIPPI-6400-OPT [3].\n\n HIPPI-6400-PH [1] defines the encapsulation of IEEE 802.2 LLC PDUs\n [10] and by implication, IP on GSN. Another T11.1 standard describes\n the operation of HIPPI-6400 physical switches HIPPI-6400-SC [2].\n T11.1 chose to leave HIPPI-6400 networking issues largely outside the\n scope of their standards; this document specifies the use of HIPPI-\n 6400 switches as IP local area networks. This document further\n specifies a method for resolving IP addresses t 2835 algorithm delivery http key nested-reference unchanged"},{"id":"IETF RFC 2878","type":"specification","body":"IETF","designation":"RFC 2878","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2878.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2878.txt","https://www.rfc-editor.org/rfc/rfc2878.pdf"],"folder":"IETF/RFC-2878","files":{"txt":{"path":"standards/IETF/RFC-2878/RFC-2878.txt","sha256":"f89bb54e4b5b588123f2acc064651e82741a7e15476d114ba91e4e248b10b0c6"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [6] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring Remote Bridging for PPP links.\n\n This document obsoletes RFC 1638, which was based on the IEEE\n 802.1D-1993 MAC Bridge[3]. This document extends that specification\n by including the IEEE 802.1D-1998 MAC Bridge[8] and IEEE 802.1Q\n Virtual LAN (VLAN)[9] standards. This document also improves the\n protocol in order to support high-speed switched LANs.\n\nHigashiyama & Baker Standards Track [Page 1]\n\f\nRFC 2878 PPP Bridging Control Protocol (BCP) July 2000","scope_keywords":["2878","algorithm","algorithms","identification","key","management","path","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null}],"search_text":"IETF RFC 2878 The Point-to-Point Protocol (PPP) [6] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring Remote Bridging for PPP links.\n\n This document obsoletes RFC 1638, which was based on the IEEE\n 802.1D-1993 MAC Bridge[3]. This document extends that specification\n by including the IEEE 802.1D-1998 MAC Bridge[8] and IEEE 802.1Q\n Virtual LAN (VLAN)[9] standards. This document also improves the\n protocol in order to support high-speed switched LANs.\n\nHigashiyama & Baker Standards Track [Page 1]\n\f\nRFC 2878 PPP Bridging Control Protocol (BCP) July 2000 2878 algorithm algorithms identification key management path preservation nested-reference unchanged"},{"id":"IETF RFC 2998","type":"specification","body":"IETF","designation":"RFC 2998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2998.txt","https://www.rfc-editor.org/rfc/rfc2998.pdf"],"folder":"IETF/RFC-2998","files":{"txt":{"path":"standards/IETF/RFC-2998/RFC-2998.txt","sha256":"6ec31464c92c42c48e5b04d69c46140de0101a71d4a360d43cebf777e25c406d"}},"tags":["nested-reference","unchanged"],"summary":"The Integrated Services (Intserv) architecture provides a means for\n the delivery of end-to-end Quality of Service (QoS) to applications\n over heterogeneous networks. To support this end-to-end model, the\n Intserv architecture must be supported over a wide variety of\n different types of network elements. In this context, a network that\n supports Differentiated Services (Diffserv) may be viewed as a\n network element in the total end-to-end path. This document\n describes a framework by which Integrated Services may be supported\n over Diffserv networks.\n\nBernet, et al. Informational [Page 1]\n\f\nRFC 2998 Integrated Services Over Diffserv Networks November 2000","scope_keywords":["2998","delivery","identification","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 2996","folder":"IETF/RFC-2996","source":"IETF/RFC-2996/RFC-2996.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3583","folder":"IETF/RFC-3583","source":"IETF/RFC-3583/RFC-3583.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 2998 The Integrated Services (Intserv) architecture provides a means for\n the delivery of end-to-end Quality of Service (QoS) to applications\n over heterogeneous networks. To support this end-to-end model, the\n Intserv architecture must be supported over a wide variety of\n different types of network elements. In this context, a network that\n supports Differentiated Services (Diffserv) may be viewed as a\n network element in the total end-to-end path. This document\n describes a framework by which Integrated Services may be supported\n over Diffserv networks.\n\nBernet, et al. Informational [Page 1]\n\f\nRFC 2998 Integrated Services Over Diffserv Networks November 2000 2998 delivery identification key management path policy nested-reference unchanged"},{"id":"IETF RFC 3002","type":"specification","body":"IETF","designation":"RFC 3002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3002.txt","https://www.rfc-editor.org/rfc/rfc3002.pdf"],"folder":"IETF/RFC-3002","files":{"txt":{"path":"standards/IETF/RFC-3002/RFC-3002.txt","sha256":"3a159a786e3db39e6367f46ae26505dca588149ac0b06e058534727a329cd9cc"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on wireless internetworking. The workshop\n was hosted by Nokia in Mountain View, CA, USA on February 29 thru\n March 2, 2000. The goal of the workshop was to assess current and\n future uses of Internet technology in wireless environments, to make\n recommendations on research and standardization tasks to improve\n acceptance of Internet network and transport protocols in wireless\n environments, and to evaluate methods to improve communication and\n collaboration among Internet standards working groups and those of\n the telephony and wireless sectors. This report summarizes the\n conclusions and recommendations of the IAB on behalf of the IETF\n community.\n\n Comments should be submitted to the IAB-Wireless-Workshop@ietf.org\n mailing list.","scope_keywords":["3002","http","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null}],"search_text":"IETF RFC 3002 This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on wireless internetworking. The workshop\n was hosted by Nokia in Mountain View, CA, USA on February 29 thru\n March 2, 2000. The goal of the workshop was to assess current and\n future uses of Internet technology in wireless environments, to make\n recommendations on research and standardization tasks to improve\n acceptance of Internet network and transport protocols in wireless\n environments, and to evaluate methods to improve communication and\n collaboration among Internet standards working groups and those of\n the telephony and wireless sectors. This report summarizes the\n conclusions and recommendations of the IAB on behalf of the IETF\n community.\n\n Comments should be submitted to the IAB-Wireless-Workshop@ietf.org\n mailing list. 3002 http path policy presentation nested-reference unchanged"},{"id":"IETF RFC 3077","type":"specification","body":"IETF","designation":"RFC 3077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3077.txt","https://www.rfc-editor.org/rfc/rfc3077.pdf"],"folder":"IETF/RFC-3077","files":{"txt":{"path":"standards/IETF/RFC-3077/RFC-3077.txt","sha256":"be5eeceb5046f028563e64c0375abad556c4d7e568842ae3948670668a867e7f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to emulate full bidirectional\n connectivity between all nodes that are directly connected by a\n unidirectional link. The \"receiver\" uses a link-layer tunneling\n mechanism to forward datagrams to \"feeds\" over a separate\n bidirectional IP (Internet Protocol) network. As it is implemented\n at the link-layer, protocols in addition to IP may also be supported\n by this mechanism.\n\n1. Introduction\n\n Internet routing and upper layer protocols assume that links are\n bidirectional, i.e., directly connected hosts can communicate with\n each other over the same link.\n\n This document describes a link-layer tunneling mechanism that allows\n a set of nodes (feeds and receivers, see Section 2 for terminology)\n which are directly connected by a unidirectional link to send\n datagrams as if they were all connected by a bidirectional link. We\n present a generic topology in ","scope_keywords":["3077","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 3077 This document describes a mechanism to emulate full bidirectional\n connectivity between all nodes that are directly connected by a\n unidirectional link. The \"receiver\" uses a link-layer tunneling\n mechanism to forward datagrams to \"feeds\" over a separate\n bidirectional IP (Internet Protocol) network. As it is implemented\n at the link-layer, protocols in addition to IP may also be supported\n by this mechanism.\n\n1. Introduction\n\n Internet routing and upper layer protocols assume that links are\n bidirectional, i.e., directly connected hosts can communicate with\n each other over the same link.\n\n This document describes a link-layer tunneling mechanism that allows\n a set of nodes (feeds and receivers, see Section 2 for terminology)\n which are directly connected by a unidirectional link to send\n datagrams as if they were all connected by a bidirectional link. We\n present a generic topology in  3077 key nested-reference unchanged"},{"id":"IETF RFC 3193","type":"specification","body":"IETF","designation":"RFC 3193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3193.txt","https://www.rfc-editor.org/rfc/rfc3193.pdf"],"folder":"IETF/RFC-3193","files":{"txt":{"path":"standards/IETF/RFC-3193/RFC-3193.txt","sha256":"a8a7384e835daa6eb5bc270739810b45aa4351eb115befa56c99e9f6d4ebb532"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how L2TP (Layer Two Tunneling Protocol) may\n utilize IPsec to provide for tunnel authentication, privacy\n protection, integrity checking and replay protection. Both the\n voluntary and compulsory tunneling cases are discussed.\n\nPatel, et al. Standards Track [Page 1]\n\f\nRFC 3193 Securing L2TP using IPsec November 2001","scope_keywords":["3193","authentication","encryption","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null}],"search_text":"IETF RFC 3193 This document discusses how L2TP (Layer Two Tunneling Protocol) may\n utilize IPsec to provide for tunnel authentication, privacy\n protection, integrity checking and replay protection. Both the\n voluntary and compulsory tunneling cases are discussed.\n\nPatel, et al. Standards Track [Page 1]\n\f\nRFC 3193 Securing L2TP using IPsec November 2001 3193 authentication encryption key management tls nested-reference unchanged"},{"id":"IETF RFC 3252","type":"specification","body":"IETF","designation":"RFC 3252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3252.txt","https://www.rfc-editor.org/rfc/rfc3252.pdf"],"folder":"IETF/RFC-3252","files":{"txt":{"path":"standards/IETF/RFC-3252/RFC-3252.txt","sha256":"50c323dedce95e4fdc2db35cd1b8ebf9d74711bf5296ef438b88d186d7dd082d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a reformulation of IP and two transport layer\n protocols (TCP and UDP) as XML applications.\n\n1. Introduction","scope_keywords":["3252","algorithm","attribute","attributes","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null}],"search_text":"IETF RFC 3252 This document defines a reformulation of IP and two transport layer\n protocols (TCP and UDP) as XML applications.\n\n1. Introduction 3252 algorithm attribute attributes key validation nested-reference unchanged"},{"id":"IETF RFC 3315","type":"specification","body":"IETF","designation":"RFC 3315","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3315.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3315.txt","https://www.rfc-editor.org/rfc/rfc3315.pdf"],"folder":"IETF/RFC-3315","files":{"txt":{"path":"standards/IETF/RFC-3315/RFC-3315.txt","sha256":"380b2d6367df695afcf6aae0ab10d0947509047406da664fd9b95a3afac4fb92"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP\n servers to pass configuration parameters such as IPv6 network\n addresses to IPv6 nodes. It offers the capability of automatic\n allocation of reusable network addresses and additional configuration\n flexibility. This protocol is a stateful counterpart to \"IPv6\n Stateless Address Autoconfiguration\" (RFC 2462), and can be used\n separately or concurrently with the latter to obtain configuration\n parameters.\n\nDroms, et al. Standards Track [Page 1]\n\f\nRFC 3315 DHCP for IPv6 July 2003","scope_keywords":["3315","management","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 3633","folder":"IETF/RFC-3633","source":"IETF/RFC-3633/RFC-3633.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3898","folder":"IETF/RFC-3898","source":"IETF/RFC-3898/RFC-3898.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4057","folder":"IETF/RFC-4057","source":"IETF/RFC-4057/RFC-4057.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4075","folder":"IETF/RFC-4075","source":"IETF/RFC-4075/RFC-4075.txt","version":null},{"body":"IETF","designation":"RFC 4076","folder":"IETF/RFC-4076","source":"IETF/RFC-4076/RFC-4076.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4242","folder":"IETF/RFC-4242","source":"IETF/RFC-4242/RFC-4242.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4361","folder":"IETF/RFC-4361","source":"IETF/RFC-4361/RFC-4361.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4580","folder":"IETF/RFC-4580","source":"IETF/RFC-4580/RFC-4580.txt","version":null},{"body":"IETF","designation":"RFC 4649","folder":"IETF/RFC-4649","source":"IETF/RFC-4649/RFC-4649.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 4994","folder":"IETF/RFC-4994","source":"IETF/RFC-4994/RFC-4994.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6221","folder":"IETF/RFC-6221","source":"IETF/RFC-6221/RFC-6221.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6355","folder":"IETF/RFC-6355","source":"IETF/RFC-6355/RFC-6355.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6603","folder":"IETF/RFC-6603","source":"IETF/RFC-6603/RFC-6603.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6644","folder":"IETF/RFC-6644","source":"IETF/RFC-6644/RFC-6644.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7083","folder":"IETF/RFC-7083","source":"IETF/RFC-7083/RFC-7083.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7283","folder":"IETF/RFC-7283","source":"IETF/RFC-7283/RFC-7283.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3315 The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables DHCP\n servers to pass configuration parameters such as IPv6 network\n addresses to IPv6 nodes. It offers the capability of automatic\n allocation of reusable network addresses and additional configuration\n flexibility. This protocol is a stateful counterpart to \"IPv6\n Stateless Address Autoconfiguration\" (RFC 2462), and can be used\n separately or concurrently with the latter to obtain configuration\n parameters.\n\nDroms, et al. Standards Track [Page 1]\n\f\nRFC 3315 DHCP for IPv6 July 2003 3315 management presentation validation nested-reference unchanged"},{"id":"IETF RFC 3318","type":"specification","body":"IETF","designation":"RFC 3318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3318.txt","https://www.rfc-editor.org/rfc/rfc3318.pdf"],"folder":"IETF/RFC-3318","files":{"txt":{"path":"standards/IETF/RFC-3318/RFC-3318.txt","sha256":"f69f24801c4fd83c13022c709e578de282c26ce1e8103ab9a9b5ca1e99146789"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of PRovisioning Classes (PRCs) and\n textual conventions that are common to all clients that provision\n policy using Common Open Policy Service (COPS) protocol for\n Provisioning.\n\n Structure of Policy Provisioning Information (SPPI) describes a\n structure for specifying policy information that can then be\n transmitted to a network device for the purpose of configuring policy\n at that device. The model underlying this structure is one of well-\n defined (PRCs) and instances of these classes (PRIs) residing in a\n virtual information store called the Policy Information Base (PIB).\n\n One way to provision policy is by means of the (COPS) protocol with\n the extensions for provisioning. This protocol supports multiple\n clients, each of which may provision policy for a specific policy\n domain such as QoS, virtual private networks, or security.\n\n As described in COPS usa","scope_keywords":["3318","attribute","identification","key","management","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IETF RFC 3318 This document defines a set of PRovisioning Classes (PRCs) and\n textual conventions that are common to all clients that provision\n policy using Common Open Policy Service (COPS) protocol for\n Provisioning.\n\n Structure of Policy Provisioning Information (SPPI) describes a\n structure for specifying policy information that can then be\n transmitted to a network device for the purpose of configuring policy\n at that device. The model underlying this structure is one of well-\n defined (PRCs) and instances of these classes (PRIs) residing in a\n virtual information store called the Policy Information Base (PIB).\n\n One way to provision policy is by means of the (COPS) protocol with\n the extensions for provisioning. This protocol supports multiple\n clients, each of which may provision policy for a specific policy\n domain such as QoS, virtual private networks, or security.\n\n As described in COPS usa 3318 attribute identification key management policies policy subject nested-reference unchanged"},{"id":"IETF RFC 3374","type":"specification","body":"IETF","designation":"RFC 3374","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3374.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3374.txt","https://www.rfc-editor.org/rfc/rfc3374.pdf"],"folder":"IETF/RFC-3374","files":{"txt":{"path":"standards/IETF/RFC-3374/RFC-3374.txt","sha256":"01dc2f47f1978c9bd8e7b5cdd5c7d142818e8757bd5a99655bb4377b9062a5b3"}},"tags":["nested-reference","unchanged"],"summary":"In IP access networks that support host mobility, the routing paths\n between the host and the network may change frequently and rapidly.\n In some cases, the host may establish certain context transfer\n candidate services on subnets that are left behind when the host\n moves. Examples of such services are Authentication, Authorization,\n and Accounting (AAA), header compression, and Quality of Service\n (QoS). In order for the host to obtain those services on the new\n subnet, the host must explicitly re-establish the service by\n performing the necessary signaling flows from scratch. In some\n cases, this process would considerably slow the process of\n establishing the mobile host on the new subnet. An alternative is to\n transfer information on the existing state associated with these\n services, or context, to the new subnet, a process called \"context\n transfer\". This document discusses the de","scope_keywords":["3374","authentication","authorization","http","path","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3583","folder":"IETF/RFC-3583","source":"IETF/RFC-3583/RFC-3583.txt","version":null},{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null}],"search_text":"IETF RFC 3374 In IP access networks that support host mobility, the routing paths\n between the host and the network may change frequently and rapidly.\n In some cases, the host may establish certain context transfer\n candidate services on subnets that are left behind when the host\n moves. Examples of such services are Authentication, Authorization,\n and Accounting (AAA), header compression, and Quality of Service\n (QoS). In order for the host to obtain those services on the new\n subnet, the host must explicitly re-establish the service by\n performing the necessary signaling flows from scratch. In some\n cases, this process would considerably slow the process of\n establishing the mobile host on the new subnet. An alternative is to\n transfer information on the existing state associated with these\n services, or context, to the new subnet, a process called \"context\n transfer\". This document discusses the de 3374 authentication authorization http path pid policy nested-reference unchanged"},{"id":"IETF RFC 3460","type":"specification","body":"IETF","designation":"RFC 3460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3460.txt","https://www.rfc-editor.org/rfc/rfc3460.pdf"],"folder":"IETF/RFC-3460","files":{"txt":{"path":"standards/IETF/RFC-3460/RFC-3460.txt","sha256":"c89bd54c73e58c426057b77172d468bb10cf6f79e4ee804f509046e6ab400cfd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a number of changes to the Policy Core\n Information Model (PCIM, RFC 3060). Two types of changes are\n included. First, several completely new elements are introduced, for\n example, classes for header filtering, that extend PCIM into areas\n that it did not previously cover. Second, there are cases where\n elements of PCIM (for example, policy rule priorities) are\n deprecated, and replacement elements are defined (in this case,\n priorities tied to associations that refer to policy rules). Both\n types of changes are done in such a way that, to the extent possible,\n interoperability with implementations of the original PCIM model is\n preserved. This document updates RFC 3060.","scope_keywords":["3460","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3460 This document specifies a number of changes to the Policy Core\n Information Model (PCIM, RFC 3060). Two types of changes are\n included. First, several completely new elements are introduced, for\n example, classes for header filtering, that extend PCIM into areas\n that it did not previously cover. Second, there are cases where\n elements of PCIM (for example, policy rule priorities) are\n deprecated, and replacement elements are defined (in this case,\n priorities tied to associations that refer to policy rules). Both\n types of changes are done in such a way that, to the extent possible,\n interoperability with implementations of the original PCIM model is\n preserved. This document updates RFC 3060. 3460 policies policy nested-reference unchanged"},{"id":"IETF RFC 3518","type":"specification","body":"IETF","designation":"RFC 3518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3518.txt","https://www.rfc-editor.org/rfc/rfc3518.pdf"],"folder":"IETF/RFC-3518","files":{"txt":{"path":"standards/IETF/RFC-3518/RFC-3518.txt","sha256":"c545ece048b4dfa5f45a5c43ab6e3a4fe06012688e00be1fddd062c5abf39656"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) and proposes a\n family of Network Control Protocols (NCP) for establishing and\n configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring Remote\n Bridging for PPP links.\n\n This document obsoletes RFC 2878, which was based on the IEEE\n 802.1D-1993 MAC Bridge. This document extends that specification by\n improving support for bridge control packets.","scope_keywords":["3518","algorithm","algorithms","identification","key","management","path","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null}],"search_text":"IETF RFC 3518 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) and proposes a\n family of Network Control Protocols (NCP) for establishing and\n configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring Remote\n Bridging for PPP links.\n\n This document obsoletes RFC 2878, which was based on the IEEE\n 802.1D-1993 MAC Bridge. This document extends that specification by\n improving support for bridge control packets. 3518 algorithm algorithms identification key management path preservation nested-reference unchanged"},{"id":"IETF RFC 3576","type":"specification","body":"IETF","designation":"RFC 3576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3576.txt","https://www.rfc-editor.org/rfc/rfc3576.pdf"],"folder":"IETF/RFC-3576","files":{"txt":{"path":"standards/IETF/RFC-3576/RFC-3576.txt","sha256":"93531ff96e5d44a1412bb86f348553c428b9452f8eb29d1f3b464e860f8d72b1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a currently deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, allowing\n dynamic changes to a user session, as implemented by network access\n server products. This includes support for disconnecting users and\n changing authorizations applicable to a user session.\n\nChiba, et al. Informational [Page 1]\n\f\nRFC 3576 Dynamic Authorization Extensions to RADIUS July 2003","scope_keywords":["3576","algorithm","algorithms","attribute","attributes","authentication","authorization","identification","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null}],"search_text":"IETF RFC 3576 This document describes a currently deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, allowing\n dynamic changes to a user session, as implemented by network access\n server products. This includes support for disconnecting users and\n changing authorizations applicable to a user session.\n\nChiba, et al. Informational [Page 1]\n\f\nRFC 3576 Dynamic Authorization Extensions to RADIUS July 2003 3576 algorithm algorithms attribute attributes authentication authorization identification path timestamp nested-reference unchanged"},{"id":"IETF RFC 3579","type":"specification","body":"IETF","designation":"RFC 3579","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3579.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3579.txt","https://www.rfc-editor.org/rfc/rfc3579.pdf"],"folder":"IETF/RFC-3579","files":{"txt":{"path":"standards/IETF/RFC-3579/RFC-3579.txt","sha256":"9b8b209a72edf51ad74d634d556086dcbdb7fb13911d9f41b3c1ccd85f1b3cf6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Remote Authentication Dial In User Service\n (RADIUS) support for the Extensible Authentication Protocol (EAP), an\n authentication framework which supports multiple authentication\n mechanisms. In the proposed scheme, the Network Access Server (NAS)\n forwards EAP packets to and from the RADIUS server, encapsulated\n within EAP-Message attributes. This has the advantage of allowing\n the NAS to support any EAP authentication method, without the need\n for method-specific code, which resides on the RADIUS server. While\n EAP was originally developed for use with PPP, it is now also in use\n with IEEE 802.\n\n This document updates RFC 2869.\n\nAboba & Calhoun Informational [Page 1]\n\f\nRFC 3579 RADIUS & EAP September 2003","scope_keywords":["3579","attribute","attributes","authentication","authorization","credential","credentials","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4016","folder":"IETF/RFC-4016","source":"IETF/RFC-4016/RFC-4016.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4137","folder":"IETF/RFC-4137","source":"IETF/RFC-4137/RFC-4137.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 3579 This document defines Remote Authentication Dial In User Service\n (RADIUS) support for the Extensible Authentication Protocol (EAP), an\n authentication framework which supports multiple authentication\n mechanisms. In the proposed scheme, the Network Access Server (NAS)\n forwards EAP packets to and from the RADIUS server, encapsulated\n within EAP-Message attributes. This has the advantage of allowing\n the NAS to support any EAP authentication method, without the need\n for method-specific code, which resides on the RADIUS server. While\n EAP was originally developed for use with PPP, it is now also in use\n with IEEE 802.\n\n This document updates RFC 2869.\n\nAboba & Calhoun Informational [Page 1]\n\f\nRFC 3579 RADIUS & EAP September 2003 3579 attribute attributes authentication authorization credential credentials key nested-reference unchanged"},{"id":"IETF RFC 3580","type":"specification","body":"IETF","designation":"RFC 3580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3580.txt","https://www.rfc-editor.org/rfc/rfc3580.pdf"],"folder":"IETF/RFC-3580","files":{"txt":{"path":"standards/IETF/RFC-3580/RFC-3580.txt","sha256":"51ea2e7296c23459aaf27c2e67207ba66e42007a5da98f8ee517267b7b30ce03"}},"tags":["nested-reference","unchanged"],"summary":"This document provides suggestions on Remote Authentication Dial In\n User Service (RADIUS) usage by IEEE 802.1X Authenticators. The\n material in this document is also included within a non-normative\n Appendix within the IEEE 802.1X specification, and is being presented\n as an IETF RFC for informational purposes.\n\nCongdon, et al. Informational [Page 1]\n\f\nRFC 3580 IEEE 802.1X RADIUS September 2003","scope_keywords":["3580","attribute","attributes","authentication","authorization","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 3580 This document provides suggestions on Remote Authentication Dial In\n User Service (RADIUS) usage by IEEE 802.1X Authenticators. The\n material in this document is also included within a non-normative\n Appendix within the IEEE 802.1X specification, and is being presented\n as an IETF RFC for informational purposes.\n\nCongdon, et al. Informational [Page 1]\n\f\nRFC 3580 IEEE 802.1X RADIUS September 2003 3580 attribute attributes authentication authorization key management nested-reference unchanged"},{"id":"IETF RFC 3748","type":"specification","body":"IETF","designation":"RFC 3748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3748.txt","https://www.rfc-editor.org/rfc/rfc3748.pdf"],"folder":"IETF/RFC-3748","files":{"txt":{"path":"standards/IETF/RFC-3748/RFC-3748.txt","sha256":"47b3a35dcc8b52f8e0ff67477a8d38b3d801a5478e62b9f6b3c20246428d1d74"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Extensible Authentication Protocol (EAP),\n an authentication framework which supports multiple authentication\n methods. EAP typically runs directly over data link layers such as\n Point-to-Point Protocol (PPP) or IEEE 802, without requiring IP. EAP\n provides its own support for duplicate elimination and\n retransmission, but is reliant on lower layer ordering guarantees.\n Fragmentation is not supported within EAP itself; however, individual\n EAP methods may support this.\n\n This document obsoletes RFC 2284. A summary of the changes between\n this document and RFC 2284 is available in Appendix A.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 3748 EAP June 2004","scope_keywords":["3748","authentication","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4137","folder":"IETF/RFC-4137","source":"IETF/RFC-4137/RFC-4137.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4739","folder":"IETF/RFC-4739","source":"IETF/RFC-4739/RFC-4739.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 3748 This document defines the Extensible Authentication Protocol (EAP),\n an authentication framework which supports multiple authentication\n methods. EAP typically runs directly over data link layers such as\n Point-to-Point Protocol (PPP) or IEEE 802, without requiring IP. EAP\n provides its own support for duplicate elimination and\n retransmission, but is reliant on lower layer ordering guarantees.\n Fragmentation is not supported within EAP itself; however, individual\n EAP methods may support this.\n\n This document obsoletes RFC 2284. A summary of the changes between\n this document and RFC 2284 is available in Appendix A.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 3748 EAP June 2004 3748 authentication key trust nested-reference unchanged"},{"id":"IETF RFC 3768","type":"specification","body":"IETF","designation":"RFC 3768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3768.txt","https://www.rfc-editor.org/rfc/rfc3768.pdf"],"folder":"IETF/RFC-3768","files":{"txt":{"path":"standards/IETF/RFC-3768/RFC-3768.txt","sha256":"5f1571913f2d3b800f636ec7aa25c0dd3de43cdde9de570a6232e9fc882c7844"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Virtual Router Redundancy Protocol (VRRP).\n VRRP specifies an election protocol that dynamically assigns\n responsibility for a virtual router to one of the VRRP routers on a\n LAN. The VRRP router controlling the IP address(es) associated with\n a virtual router is called the Master, and forwards packets sent to\n these IP addresses. The election process provides dynamic fail over\n in the forwarding responsibility should the Master become\n unavailable. This allows any of the virtual router IP addresses on\n the LAN to be used as the default first hop router by end-hosts. The\n advantage gained from using VRRP is a higher availability default\n path without requiring configuration of dynamic routing or router\n discovery protocols on every end-host.","scope_keywords":["3768","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null}],"search_text":"IETF RFC 3768 This memo defines the Virtual Router Redundancy Protocol (VRRP).\n VRRP specifies an election protocol that dynamically assigns\n responsibility for a virtual router to one of the VRRP routers on a\n LAN. The VRRP router controlling the IP address(es) associated with\n a virtual router is called the Master, and forwards packets sent to\n these IP addresses. The election process provides dynamic fail over\n in the forwarding responsibility should the Master become\n unavailable. This allows any of the virtual router IP addresses on\n the LAN to be used as the default first hop router by end-hosts. The\n advantage gained from using VRRP is a higher availability default\n path without requiring configuration of dynamic routing or router\n discovery protocols on every end-host. 3768 key path nested-reference unchanged"},{"id":"IETF RFC 3775","type":"specification","body":"IETF","designation":"RFC 3775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3775.txt","https://www.rfc-editor.org/rfc/rfc3775.pdf"],"folder":"IETF/RFC-3775","files":{"txt":{"path":"standards/IETF/RFC-3775/RFC-3775.txt","sha256":"2e1788f3674cefdb1731f9a9dbadeba6b07d8d2218f7b93bc0ac33b9b557d61d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol which allows nodes to remain\n reachable while moving around in the IPv6 Internet. Each mobile node\n is always identified by its home address, regardless of its current\n point of attachment to the Internet. While situated away from its\n home, a mobile node is also associated with a care-of address, which\n provides information about the mobile node's current location. IPv6\n packets addressed to a mobile node's home address are transparently\n routed to its care-of address. The protocol enables IPv6 nodes to\n cache the binding of a mobile node's home address with its care-of\n address, and to then send any packets destined for the mobile node\n directly to it at this care-of address. To support this operation,\n Mobile IPv6 defines a new IPv6 protocol and a new destination option.\n All IPv6 nodes, whether mobile or stationary, can communicate with\n mobile node","scope_keywords":["3775","authorization","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4135","folder":"IETF/RFC-4135","source":"IETF/RFC-4135/RFC-4135.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4177","folder":"IETF/RFC-4177","source":"IETF/RFC-4177/RFC-4177.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4219","folder":"IETF/RFC-4219","source":"IETF/RFC-4219/RFC-4219.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4449","folder":"IETF/RFC-4449","source":"IETF/RFC-4449/RFC-4449.txt","version":null},{"body":"IETF","designation":"RFC 4487","folder":"IETF/RFC-4487","source":"IETF/RFC-4487/RFC-4487.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5094","folder":"IETF/RFC-5094","source":"IETF/RFC-5094/RFC-5094.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5142","folder":"IETF/RFC-5142","source":"IETF/RFC-5142/RFC-5142.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 3775 This document specifies a protocol which allows nodes to remain\n reachable while moving around in the IPv6 Internet. Each mobile node\n is always identified by its home address, regardless of its current\n point of attachment to the Internet. While situated away from its\n home, a mobile node is also associated with a care-of address, which\n provides information about the mobile node's current location. IPv6\n packets addressed to a mobile node's home address are transparently\n routed to its care-of address. The protocol enables IPv6 nodes to\n cache the binding of a mobile node's home address with its care-of\n address, and to then send any packets destined for the mobile node\n directly to it at this care-of address. To support this operation,\n Mobile IPv6 defines a new IPv6 protocol and a new destination option.\n All IPv6 nodes, whether mobile or stationary, can communicate with\n mobile node 3775 authorization key keys management nested-reference unchanged"},{"id":"IETF RFC 3780","type":"specification","body":"IETF","designation":"RFC 3780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3780.txt","https://www.rfc-editor.org/rfc/rfc3780.pdf"],"folder":"IETF/RFC-3780","files":{"txt":{"path":"standards/IETF/RFC-3780/RFC-3780.txt","sha256":"617114bda71f645bbcd02086ffb2a0cf20b3867a248a44d692bd8200c25289ec"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the base SMIng (Structure of Management\n Information, Next Generation) language. SMIng is a data definition\n language that provides a protocol-independent representation for\n management information. Separate RFCs define mappings of SMIng to\n specific management protocols, including SNMP.","scope_keywords":["3780","attribute","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null}],"search_text":"IETF RFC 3780 This memo defines the base SMIng (Structure of Management\n Information, Next Generation) language. SMIng is a data definition\n language that provides a protocol-independent representation for\n management information. Separate RFCs define mappings of SMIng to\n specific management protocols, including SNMP. 3780 attribute management presentation nested-reference unchanged"},{"id":"IETF RFC 3794","type":"specification","body":"IETF","designation":"RFC 3794","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3794.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3794.txt","https://www.rfc-editor.org/rfc/rfc3794.pdf"],"folder":"IETF/RFC-3794","files":{"txt":{"path":"standards/IETF/RFC-3794/RFC-3794.txt","sha256":"46a2e1c9deb704246d8d2cc7eb9182c2e00b2128942e2011806cf669aafd72b9"}},"tags":["nested-reference","unchanged"],"summary":"This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Transport Area documented standards. In\n order to successfully transition from an all IPv4 Internet to an all\n IPv6 Internet, many interim steps will be taken. One of these steps\n is the evolution of current protocols that have IPv4 dependencies.\n It is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented.","scope_keywords":["3794","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 3794 This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Transport Area documented standards. In\n order to successfully transition from an all IPv4 Internet to an all\n IPv6 Internet, many interim steps will be taken. One of these steps\n is the evolution of current protocols that have IPv4 dependencies.\n It is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented. 3794 management nested-reference unchanged"},{"id":"IETF RFC 3819","type":"specification","body":"IETF","designation":"RFC 3819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3819.txt","https://www.rfc-editor.org/rfc/rfc3819.pdf"],"folder":"IETF/RFC-3819","files":{"txt":{"path":"standards/IETF/RFC-3819/RFC-3819.txt","sha256":"ccf0cbecb7dad5381d818daf36ca36bd175fd9bc34feb201f3ba50532b4a8fd3"}},"tags":["nested-reference","unchanged"],"summary":"This document provides advice to the designers of digital\n communication equipment, link-layer protocols, and packet-switched\n local networks (collectively referred to as subnetworks), who wish to\n support the Internet protocols but may be unfamiliar with the\n Internet architecture and the implications of their design choices on\n the performance and efficiency of the Internet.\n\nKarn, et al. Best Current Practice [Page 1]\n\f\nRFC 3819 Advice for Internet Subnetwork Designers July 2004","scope_keywords":["3819","attribute"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 3819 This document provides advice to the designers of digital\n communication equipment, link-layer protocols, and packet-switched\n local networks (collectively referred to as subnetworks), who wish to\n support the Internet protocols but may be unfamiliar with the\n Internet architecture and the implications of their design choices on\n the performance and efficiency of the Internet.\n\nKarn, et al. Best Current Practice [Page 1]\n\f\nRFC 3819 Advice for Internet Subnetwork Designers July 2004 3819 attribute nested-reference unchanged"},{"id":"IETF RFC 3927","type":"specification","body":"IETF","designation":"RFC 3927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3927.txt","https://www.rfc-editor.org/rfc/rfc3927.pdf"],"folder":"IETF/RFC-3927","files":{"txt":{"path":"standards/IETF/RFC-3927/RFC-3927.txt","sha256":"8f267f455dc791ca9c63b8a4ff6a9abeb61f6cfbfc288b29483c593fe4cb90e6"}},"tags":["nested-reference","unchanged"],"summary":"To participate in wide-area IP networking, a host needs to be\n configured with IP addresses for its interfaces, either manually by\n the user or automatically from a source on the network such as a\n Dynamic Host Configuration Protocol (DHCP) server. Unfortunately,\n such address configuration information may not always be available.\n It is therefore beneficial for a host to be able to depend on a\n useful subset of IP networking functions even when no address\n configuration is available. This document describes how a host may\n automatically configure an interface with an IPv4 address within the\n 169.254/16 prefix that is valid for communication with other devices\n connected to the same physical (or logical) link.\n\n IPv4 Link-Local addresses are not suitable for communication with\n devices not directly connected to the same physical (or logical)\n link, and are only used where stable, routabl","scope_keywords":["3927","delivery","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null}],"search_text":"IETF RFC 3927 To participate in wide-area IP networking, a host needs to be\n configured with IP addresses for its interfaces, either manually by\n the user or automatically from a source on the network such as a\n Dynamic Host Configuration Protocol (DHCP) server. Unfortunately,\n such address configuration information may not always be available.\n It is therefore beneficial for a host to be able to depend on a\n useful subset of IP networking functions even when no address\n configuration is available. This document describes how a host may\n automatically configure an interface with an IPv4 address within the\n 169.254/16 prefix that is valid for communication with other devices\n connected to the same physical (or logical) link.\n\n IPv4 Link-Local addresses are not suitable for communication with\n devices not directly connected to the same physical (or logical)\n link, and are only used where stable, routabl 3927 delivery key registered nested-reference unchanged"},{"id":"IETF RFC 3931","type":"specification","body":"IETF","designation":"RFC 3931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3931.txt","https://www.rfc-editor.org/rfc/rfc3931.pdf"],"folder":"IETF/RFC-3931","files":{"txt":{"path":"standards/IETF/RFC-3931/RFC-3931.txt","sha256":"7812f2b731779732690be64e959f16985dbdb776fd231abc01ab585982802f70"}},"tags":["nested-reference","unchanged"],"summary":"This document describes \"version 3\" of the Layer Two Tunneling\n Protocol (L2TPv3). L2TPv3 defines the base control protocol and\n encapsulation for tunneling multiple Layer 2 connections between two\n IP nodes. Additional documents detail the specifics for each data\n link type being emulated.","scope_keywords":["3931","attribute","authentication","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4349","folder":"IETF/RFC-4349","source":"IETF/RFC-4349/RFC-4349.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4667","folder":"IETF/RFC-4667","source":"IETF/RFC-4667/RFC-4667.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5640","folder":"IETF/RFC-5640","source":"IETF/RFC-5640/RFC-5640.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null}],"search_text":"IETF RFC 3931 This document describes \"version 3\" of the Layer Two Tunneling\n Protocol (L2TPv3). L2TPv3 defines the base control protocol and\n encapsulation for tunneling multiple Layer 2 connections between two\n IP nodes. Additional documents detail the specifics for each data\n link type being emulated. 3931 attribute authentication delivery management nested-reference unchanged"},{"id":"IETF RFC 4005","type":"specification","body":"IETF","designation":"RFC 4005","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4005.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4005.txt","https://www.rfc-editor.org/rfc/rfc4005.pdf"],"folder":"IETF/RFC-4005","files":{"txt":{"path":"standards/IETF/RFC-4005/RFC-4005.txt","sha256":"fcca15c171fea9347301ebb71c330db4fe3ff00d999a1af754b7d8bf8de273db"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Diameter protocol application used for\n Authentication, Authorization, and Accounting (AAA) services in the\n Network Access Server (NAS) environment. When combined with the\n Diameter Base protocol, Transport Profile, and Extensible\n Authentication Protocol specifications, this application\n specification satisfies typical network access services requirements.\n\n Initial deployments of the Diameter protocol are expected to include\n legacy systems. Therefore, this application has been carefully\n designed to ease the burden of protocol conversion between RADIUS and\n Diameter. This is achieved by including the RADIUS attribute space\n to eliminate the need to perform many attribute translations.\n\n The interactions between Diameter applications and RADIUS specified\n in this document are to be applied to all Diameter applications. In\n this sense, this document extends ","scope_keywords":["4005","algorithm","attribute","authentication","authorization","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 4005 This document describes the Diameter protocol application used for\n Authentication, Authorization, and Accounting (AAA) services in the\n Network Access Server (NAS) environment. When combined with the\n Diameter Base protocol, Transport Profile, and Extensible\n Authentication Protocol specifications, this application\n specification satisfies typical network access services requirements.\n\n Initial deployments of the Diameter protocol are expected to include\n legacy systems. Therefore, this application has been carefully\n designed to ease the burden of protocol conversion between RADIUS and\n Diameter. This is achieved by including the RADIUS attribute space\n to eliminate the need to perform many attribute translations.\n\n The interactions between Diameter applications and RADIUS specified\n in this document are to be applied to all Diameter applications. In\n this sense, this document extends  4005 algorithm attribute authentication authorization profile nested-reference unchanged"},{"id":"IETF RFC 4006","type":"specification","body":"IETF","designation":"RFC 4006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4006.txt","https://www.rfc-editor.org/rfc/rfc4006.pdf"],"folder":"IETF/RFC-4006","files":{"txt":{"path":"standards/IETF/RFC-4006/RFC-4006.txt","sha256":"036788a26ad4f82bfb71134d21af2fdd185fa95c84ad22cb56499b7f8dce426a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Diameter application that can be used to\n implement real-time credit-control for a variety of end user services\n such as network access, Session Initiation Protocol (SIP) services,\n messaging services, and download services.","scope_keywords":["4006","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5431","folder":"IETF/RFC-5431","source":"IETF/RFC-5431/RFC-5431.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 4006 This document specifies a Diameter application that can be used to\n implement real-time credit-control for a variety of end user services\n such as network access, Session Initiation Protocol (SIP) services,\n messaging services, and download services. 4006 authorization nested-reference unchanged"},{"id":"IETF RFC 4058","type":"specification","body":"IETF","designation":"RFC 4058","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4058.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4058.txt","https://www.rfc-editor.org/rfc/rfc4058.pdf"],"folder":"IETF/RFC-4058","files":{"txt":{"path":"standards/IETF/RFC-4058/RFC-4058.txt","sha256":"0d5ce7c86c0b004711ecacefab361afb75da8accb0dd7b3fdfcd442fc2ef53a7"}},"tags":["nested-reference","unchanged"],"summary":"It is expected that future IP devices will have a variety of access\n technologies to gain network connectivity. Currently there are\n access-specific mechanisms for providing client information to the\n network for authentication and authorization purposes. In addition\n to being limited to specific access media (e.g., 802.1X for IEEE 802\n links), some of these protocols are limited to specific network\n topologies (e.g., PPP for point-to-point links). The goal of this\n document is to identify the requirements for a link-layer agnostic\n protocol that allows a host and a network to authenticate each other\n for network access. This protocol will run between a client's device\n and an agent in the network where the agent might be a client of the\n AAA infrastructure.\n\nYegin, et al. Informational [Page 1]\n\f\nRFC 4058 PANA Requirements May 2005","scope_keywords":["4058","authentication","authorization","credential","credentials","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4739","folder":"IETF/RFC-4739","source":"IETF/RFC-4739/RFC-4739.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null}],"search_text":"IETF RFC 4058 It is expected that future IP devices will have a variety of access\n technologies to gain network connectivity. Currently there are\n access-specific mechanisms for providing client information to the\n network for authentication and authorization purposes. In addition\n to being limited to specific access media (e.g., 802.1X for IEEE 802\n links), some of these protocols are limited to specific network\n topologies (e.g., PPP for point-to-point links). The goal of this\n document is to identify the requirements for a link-layer agnostic\n protocol that allows a host and a network to authenticate each other\n for network access. This protocol will run between a client's device\n and an agent in the network where the agent might be a client of the\n AAA infrastructure.\n\nYegin, et al. Informational [Page 1]\n\f\nRFC 4058 PANA Requirements May 2005 4058 authentication authorization credential credentials key management tls nested-reference unchanged"},{"id":"IETF RFC 4072","type":"specification","body":"IETF","designation":"RFC 4072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4072.txt","https://www.rfc-editor.org/rfc/rfc4072.pdf"],"folder":"IETF/RFC-4072","files":{"txt":{"path":"standards/IETF/RFC-4072/RFC-4072.txt","sha256":"bec22b78115b34a0583fd4e8863887d5a288d623c23367b0a1e9ca2c12d58d53"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) provides a standard\n mechanism for support of various authentication methods. This\n document defines the Command-Codes and AVPs necessary to carry EAP\n packets between a Network Access Server (NAS) and a back-end\n authentication server.","scope_keywords":["4072","attribute","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 4072 The Extensible Authentication Protocol (EAP) provides a standard\n mechanism for support of various authentication methods. This\n document defines the Command-Codes and AVPs necessary to carry EAP\n packets between a Network Access Server (NAS) and a back-end\n authentication server. 4072 attribute authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 4118","type":"specification","body":"IETF","designation":"RFC 4118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4118.txt","https://www.rfc-editor.org/rfc/rfc4118.pdf"],"folder":"IETF/RFC-4118","files":{"txt":{"path":"standards/IETF/RFC-4118/RFC-4118.txt","sha256":"5588532849ebe75c071e9e5d4ae0341f44730804941ab57480f8e5fdc2b065b6"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a taxonomy of the architectures employed in\n the existing IEEE 802.11 products in the market, by analyzing\n Wireless LAN (WLAN) functions and services and describing the\n different variants in distributing these functions and services among\n the architectural entities.","scope_keywords":["4118","authentication","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4118 This document provides a taxonomy of the architectures employed in\n the existing IEEE 802.11 products in the market, by analyzing\n Wireless LAN (WLAN) functions and services and describing the\n different variants in distributing these functions and services among\n the architectural entities. 4118 authentication delivery management nested-reference unchanged"},{"id":"IETF RFC 4122","type":"specification","body":"IETF","designation":"RFC 4122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4122.txt","https://www.rfc-editor.org/rfc/rfc4122.pdf"],"folder":"IETF/RFC-4122","files":{"txt":{"path":"standards/IETF/RFC-4122/RFC-4122.txt","sha256":"3825a334d337243035be8e2656508551a48e0cd42ae16cebf66f164ca66e0c31"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a Uniform Resource Name namespace for\n UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally\n Unique IDentifier). A UUID is 128 bits long, and can guarantee\n uniqueness across space and time. UUIDs were originally used in the\n Apollo Network Computing System and later in the Open Software\n Foundation's (OSF) Distributed Computing Environment (DCE), and then\n in Microsoft Windows platforms.\n\n This specification is derived from the DCE specification with the\n kind permission of the OSF (now known as The Open Group).\n Information from earlier versions of the DCE specification have been\n incorporated into this document.\n\nLeach, et al. Standards Track [Page 1]\n\f\nRFC 4122 A UUID URN Namespace July 2005","scope_keywords":["4122","algorithm","algorithms","hash","hashing","http","presentation","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-2","folder":"ETSI/EN-319-522-2-V1.2.1","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6355","folder":"IETF/RFC-6355","source":"IETF/RFC-6355/RFC-6355.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 4122 This specification defines a Uniform Resource Name namespace for\n UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally\n Unique IDentifier). A UUID is 128 bits long, and can guarantee\n uniqueness across space and time. UUIDs were originally used in the\n Apollo Network Computing System and later in the Open Software\n Foundation's (OSF) Distributed Computing Environment (DCE), and then\n in Microsoft Windows platforms.\n\n This specification is derived from the DCE specification with the\n kind permission of the OSF (now known as The Open Group).\n Information from earlier versions of the DCE specification have been\n incorporated into this document.\n\nLeach, et al. Standards Track [Page 1]\n\f\nRFC 4122 A UUID URN Namespace July 2005 4122 algorithm algorithms hash hashing http presentation timestamp nested-reference unchanged"},{"id":"IETF RFC 4259","type":"specification","body":"IETF","designation":"RFC 4259","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4259.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4259.txt","https://www.rfc-editor.org/rfc/rfc4259.pdf"],"folder":"IETF/RFC-4259","files":{"txt":{"path":"standards/IETF/RFC-4259/RFC-4259.txt","sha256":"2ce42eac48f033a24be30d5553bb2d3af63eeea3d9d2feb30e98251c65d32bf1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for the transport of IP\n Datagrams over ISO MPEG-2 Transport Streams (TS). The MPEG-2 TS has\n been widely accepted not only for providing digital TV services but\n also as a subnetwork technology for building IP networks. Examples\n of systems using MPEG-2 include the Digital Video Broadcast (DVB) and\n Advanced Television Systems Committee (ATSC) Standards for Digital\n Television.\n\n The document identifies the need for a set of Internet standards\n defining the interface between the MPEG-2 Transport Stream and an IP\n subnetwork. It suggests a new encapsulation method for IP datagrams\n and proposes protocols to perform IPv6/IPv4 address resolution, to\n associate IP packets with the properties of the Logical Channels\n provided by an MPEG-2 TS.\n\nMontpetit, et al. Informational [Page 1]\n\f\nRFC 4259 IP Transport over MPEG-2 Networks November 2005","scope_keywords":["4259","authentication","delivery","encryption","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 4259 This document describes an architecture for the transport of IP\n Datagrams over ISO MPEG-2 Transport Streams (TS). The MPEG-2 TS has\n been widely accepted not only for providing digital TV services but\n also as a subnetwork technology for building IP networks. Examples\n of systems using MPEG-2 include the Digital Video Broadcast (DVB) and\n Advanced Television Systems Committee (ATSC) Standards for Digital\n Television.\n\n The document identifies the need for a set of Internet standards\n defining the interface between the MPEG-2 Transport Stream and an IP\n subnetwork. It suggests a new encapsulation method for IP datagrams\n and proposes protocols to perform IPv6/IPv4 address resolution, to\n associate IP packets with the properties of the Logical Channels\n provided by an MPEG-2 TS.\n\nMontpetit, et al. Informational [Page 1]\n\f\nRFC 4259 IP Transport over MPEG-2 Networks November 2005 4259 authentication delivery encryption identification nested-reference unchanged"},{"id":"IETF RFC 4326","type":"specification","body":"IETF","designation":"RFC 4326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4326.txt","https://www.rfc-editor.org/rfc/rfc4326.pdf"],"folder":"IETF/RFC-4326","files":{"txt":{"path":"standards/IETF/RFC-4326/RFC-4326.txt","sha256":"6ae512cd7a87d457b4816ebd48e82a456d579a0203863367adecef3a2e499747"}},"tags":["nested-reference","unchanged"],"summary":"The MPEG-2 Transport Stream (TS) has been widely accepted not only\n for providing digital TV services, but also as a subnetwork\n technology for building IP networks.\n\n This document describes a Unidirectional Lightweight Encapsulation\n (ULE) mechanism for the transport of IPv4 and IPv6 Datagrams and\n other network protocol packets directly over the ISO MPEG-2 Transport\n Stream as TS Private Data. ULE specifies a base encapsulation format\n and supports an extension format that allows it to carry additional\n header information to assist in network/Receiver processing.\n\nFairhurst & Collini-Nocker Standards Track [Page 1]\n\f\nRFC 4326 ULE for IP over MPEG-2/DVB December 2005","scope_keywords":["4326","key","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 4326 The MPEG-2 Transport Stream (TS) has been widely accepted not only\n for providing digital TV services, but also as a subnetwork\n technology for building IP networks.\n\n This document describes a Unidirectional Lightweight Encapsulation\n (ULE) mechanism for the transport of IPv4 and IPv6 Datagrams and\n other network protocol packets directly over the ISO MPEG-2 Transport\n Stream as TS Private Data. ULE specifies a base encapsulation format\n and supports an extension format that allows it to carry additional\n header information to assist in network/Receiver processing.\n\nFairhurst & Collini-Nocker Standards Track [Page 1]\n\f\nRFC 4326 ULE for IP over MPEG-2/DVB December 2005 4326 key pid registered nested-reference unchanged"},{"id":"IETF RFC 4334","type":"specification","body":"IETF","designation":"RFC 4334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4334.txt","https://www.rfc-editor.org/rfc/rfc4334.pdf"],"folder":"IETF/RFC-4334","files":{"txt":{"path":"standards/IETF/RFC-4334/RFC-4334.txt","sha256":"ebc429058bb089d5640e0c7b51eb0050e27a5b153a96b27185dc7725383eac31"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two Extensible Authentication Protocol (EAP)\n extended key usage values and a public key certificate extension to\n carry Wireless LAN (WLAN) System Service identifiers (SSIDs). This\n document obsoletes RFC 3770.\n\nHousley & Moore Standards Track [Page 1]\n\f\nRFC 4334 Supporting Authentication in PPP and WLAN February 2006\n\n1. Introduction\n\n Several Extensible Authentication Protocol (EAP) [EAP] authentication\n methods employ X.509 public key certificates. For example, EAP-TLS\n [EAP-TLS] can be used with PPP [PPP] as well as IEEE 802.1X [802.1X].\n PPP is used for dial-up and VPN environments. IEEE 802.1X defines\n port-based, network access control, and it is used to provide\n authenticated network access for Ethernet, Token Ring, Wireless LANs\n (WLANs) [802.11], and other IEEE 802 networks.\n\n Automated selection of client certificates for use with PPP and IEEE\n 802.1X is","scope_keywords":["4334","attribute","attributes","authentication","certificate","certificates","issuer","key","pki","profile","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null}],"search_text":"IETF RFC 4334 This document defines two Extensible Authentication Protocol (EAP)\n extended key usage values and a public key certificate extension to\n carry Wireless LAN (WLAN) System Service identifiers (SSIDs). This\n document obsoletes RFC 3770.\n\nHousley & Moore Standards Track [Page 1]\n\f\nRFC 4334 Supporting Authentication in PPP and WLAN February 2006\n\n1. Introduction\n\n Several Extensible Authentication Protocol (EAP) [EAP] authentication\n methods employ X.509 public key certificates. For example, EAP-TLS\n [EAP-TLS] can be used with PPP [PPP] as well as IEEE 802.1X [802.1X].\n PPP is used for dial-up and VPN environments. IEEE 802.1X defines\n port-based, network access control, and it is used to provide\n authenticated network access for Ethernet, Token Ring, Wireless LANs\n (WLANs) [802.11], and other IEEE 802 networks.\n\n Automated selection of client certificates for use with PPP and IEEE\n 802.1X is 4334 attribute attributes authentication certificate certificates issuer key pki profile tls tsp nested-reference unchanged"},{"id":"IETF RFC 4389","type":"specification","body":"IETF","designation":"RFC 4389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4389.txt","https://www.rfc-editor.org/rfc/rfc4389.pdf"],"folder":"IETF/RFC-4389","files":{"txt":{"path":"standards/IETF/RFC-4389/RFC-4389.txt","sha256":"c19c8540d0f59b0b9d34cfea12323b2efcff6db55647e002f3f48aca716fc873"}},"tags":["nested-reference","unchanged"],"summary":"Bridging multiple links into a single entity has several operational\n advantages. A single subnet prefix is sufficient to support multiple\n physical links. There is no need to allocate subnet numbers to the\n different networks, simplifying management. Bridging some types of\n media requires network-layer support, however. This document\n describes these cases and specifies the IP-layer support that enables\n bridging under these circumstances.\n\nThaler, et al. Experimental [Page 1]\n\f\nRFC 4389 ND Proxy April 2006","scope_keywords":["4389","encryption","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 4389 Bridging multiple links into a single entity has several operational\n advantages. A single subnet prefix is sufficient to support multiple\n physical links. There is no need to allocate subnet numbers to the\n different networks, simplifying management. Bridging some types of\n media requires network-layer support, however. This document\n describes these cases and specifies the IP-layer support that enables\n bridging under these circumstances.\n\nThaler, et al. Experimental [Page 1]\n\f\nRFC 4389 ND Proxy April 2006 4389 encryption management policies nested-reference unchanged"},{"id":"IETF RFC 4564","type":"specification","body":"IETF","designation":"RFC 4564","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4564.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4564.txt","https://www.rfc-editor.org/rfc/rfc4564.pdf"],"folder":"IETF/RFC-4564","files":{"txt":{"path":"standards/IETF/RFC-4564/RFC-4564.txt","sha256":"4046fcfadfb303d17d71c012bfc24e039d3d0eec7e5a1f5e64715b1c0922e19c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents objectives for an interoperable protocol for\n the Control and Provisioning of Wireless Access Points (CAPWAP). The\n document aims to establish a set of focused requirements for the\n development and evaluation of a CAPWAP protocol. The objectives\n address architecture, operation, security, and network operator\n requirements that are necessary to enable interoperability among\n Wireless Local Area Network (WLAN) devices of alternative designs.\n\nGovindan, et al. Informational [Page 1]\n\f\nRFC 4564 CAPWAP Objectives July 2006","scope_keywords":["4564","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4564 This document presents objectives for an interoperable protocol for\n the Control and Provisioning of Wireless Access Points (CAPWAP). The\n document aims to establish a set of focused requirements for the\n development and evaluation of a CAPWAP protocol. The objectives\n address architecture, operation, security, and network operator\n requirements that are necessary to enable interoperability among\n Wireless Local Area Network (WLAN) devices of alternative designs.\n\nGovindan, et al. Informational [Page 1]\n\f\nRFC 4564 CAPWAP Objectives July 2006 4564 authentication management nested-reference unchanged"},{"id":"IETF RFC 4663","type":"specification","body":"IETF","designation":"RFC 4663","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4663.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4663.txt","https://www.rfc-editor.org/rfc/rfc4663.pdf"],"folder":"IETF/RFC-4663","files":{"txt":{"path":"standards/IETF/RFC-4663/RFC-4663.txt","sha256":"8dccace4bd77d2fb7d59ac6d31c9630bd11bbe477be2565bad03abe00bfbf0a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the plan to transition responsibility for\n bridging-related MIB modules from the IETF Bridge MIB Working Group\n to the IEEE 802.1 Working Group, which develops the bridging\n technology the MIB modules are designed to manage.\n\nHarrington Informational [Page 1]\n\f\nRFC 4663 802.1 MIB Transition September 2006","scope_keywords":["4663","authorization","http","management","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4663 This document describes the plan to transition responsibility for\n bridging-related MIB modules from the IETF Bridge MIB Working Group\n to the IEEE 802.1 Working Group, which develops the bridging\n technology the MIB modules are designed to manage.\n\nHarrington Informational [Page 1]\n\f\nRFC 4663 802.1 MIB Transition September 2006 4663 authorization http management pid subject nested-reference unchanged"},{"id":"IETF RFC 4675","type":"specification","body":"IETF","designation":"RFC 4675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4675.txt","https://www.rfc-editor.org/rfc/rfc4675.pdf"],"folder":"IETF/RFC-4675","files":{"txt":{"path":"standards/IETF/RFC-4675/RFC-4675.txt","sha256":"2c953f83baec1c34f861d01ca231db727ae2f7b2095411b675524717b36741cc"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes additional Remote Authentication Dial-In User\n Service (RADIUS) attributes for dynamic Virtual LAN assignment and\n prioritization, for use in provisioning of access to IEEE 802 local\n area networks. These attributes are usable within either RADIUS or\n Diameter.\n\nCongdon, et al. Standards Track [Page 1]\n\f\nRFC 4675 VLAN and Priority Attributes September 2006","scope_keywords":["4675","attribute","attributes","authentication","authorization","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4675 This document proposes additional Remote Authentication Dial-In User\n Service (RADIUS) attributes for dynamic Virtual LAN assignment and\n prioritization, for use in provisioning of access to IEEE 802 local\n area networks. These attributes are usable within either RADIUS or\n Diameter.\n\nCongdon, et al. Standards Track [Page 1]\n\f\nRFC 4675 VLAN and Priority Attributes September 2006 4675 attribute attributes authentication authorization key management nested-reference unchanged"},{"id":"IETF RFC 4691","type":"specification","body":"IETF","designation":"RFC 4691","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4691.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4691.txt","https://www.rfc-editor.org/rfc/rfc4691.pdf"],"folder":"IETF/RFC-4691","files":{"txt":{"path":"standards/IETF/RFC-4691/RFC-4691.txt","sha256":"fc145fc0bd12f530cfb764ef9290d95fd10abe5a95aff12cece800ce3a1fc69a"}},"tags":["nested-reference","unchanged"],"summary":"Whenever the IETF decides to enter into a liaison relationship with\n another organization, such as a Standards Development Organization\n (SDO), a consortium, or an industrial forum, a liaison manager is\n appointed. The procedures used by the IAB to establish and maintain\n liaison relationships between the IETF and other organizations are\n described in RFC 4052. This document expands on the role of liaison\n managers and liaison representatives, giving guidelines on their\n mandate and the expectations, tasks, and responsibilities placed on\n them.","scope_keywords":["4691","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null}],"search_text":"IETF RFC 4691 Whenever the IETF decides to enter into a liaison relationship with\n another organization, such as a Standards Development Organization\n (SDO), a consortium, or an industrial forum, a liaison manager is\n appointed. The procedures used by the IAB to establish and maintain\n liaison relationships between the IETF and other organizations are\n described in RFC 4052. This document expands on the role of liaison\n managers and liaison representatives, giving guidelines on their\n mandate and the expectations, tasks, and responsibilities placed on\n them. 4691 management nested-reference unchanged"},{"id":"IETF RFC 4762","type":"specification","body":"IETF","designation":"RFC 4762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4762.txt","https://www.rfc-editor.org/rfc/rfc4762.pdf"],"folder":"IETF/RFC-4762","files":{"txt":{"path":"standards/IETF/RFC-4762/RFC-4762.txt","sha256":"5c1f8ae4b6ae226f843c3bd56af3af3971c8bcf4ac55b10f0caaa7bc1f82bb57"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Virtual Private LAN Service (VPLS) solution\n using pseudowires, a service previously implemented over other\n tunneling technologies and known as Transparent LAN Services (TLS).\n A VPLS creates an emulated LAN segment for a given set of users;\n i.e., it creates a Layer 2 broadcast domain that is fully capable of\n learning and forwarding on Ethernet MAC addresses and that is closed\n to a given set of users. Multiple VPLS services can be supported\n from a single Provider Edge (PE) node.\n\n This document describes the control plane functions of signaling\n pseudowire labels using Label Distribution Protocol (LDP), extending\n RFC 4447. It is agnostic to discovery protocols. The data plane\n functions of forwarding are also described, focusing in particular on\n the learning of MAC addresses. The encapsulation of VPLS packets is\n described by RFC 4448.\n\nLasserre & Kompell","scope_keywords":["4762","qualified","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 4762 This document describes a Virtual Private LAN Service (VPLS) solution\n using pseudowires, a service previously implemented over other\n tunneling technologies and known as Transparent LAN Services (TLS).\n A VPLS creates an emulated LAN segment for a given set of users;\n i.e., it creates a Layer 2 broadcast domain that is fully capable of\n learning and forwarding on Ethernet MAC addresses and that is closed\n to a given set of users. Multiple VPLS services can be supported\n from a single Provider Edge (PE) node.\n\n This document describes the control plane functions of signaling\n pseudowire labels using Label Distribution Protocol (LDP), extending\n RFC 4447. It is agnostic to discovery protocols. The data plane\n functions of forwarding are also described, focusing in particular on\n the learning of MAC addresses. The encapsulation of VPLS packets is\n described by RFC 4448.\n\nLasserre & Kompell 4762 qualified tls trust nested-reference unchanged"},{"id":"IETF RFC 4763","type":"specification","body":"IETF","designation":"RFC 4763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4763.txt","https://www.rfc-editor.org/rfc/rfc4763.pdf"],"folder":"IETF/RFC-4763","files":{"txt":{"path":"standards/IETF/RFC-4763/RFC-4763.txt","sha256":"95166916d4ac1565e08f83bbcc24bb00b1dc06442a523b4033f595baca7fb072"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for Shared-secret Authentication and Key Establishment\n (SAKE). This RFC is published as documentation for the IANA\n assignment of an EAP Type for a vendor's EAP method per RFC 3748.\n The specification has passed Designated Expert review for this IANA\n assignment.\n\nVanderveen & Soliman Informational [Page 1]\n\f\nRFC 4763 EAP-SAKE November 2006","scope_keywords":["4763","algorithm","algorithms","attribute","authentication","encryption","key","keys","management","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null}],"search_text":"IETF RFC 4763 This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for Shared-secret Authentication and Key Establishment\n (SAKE). This RFC is published as documentation for the IANA\n assignment of an EAP Type for a vendor's EAP method per RFC 3748.\n The specification has passed Designated Expert review for this IANA\n assignment.\n\nVanderveen & Soliman Informational [Page 1]\n\f\nRFC 4763 EAP-SAKE November 2006 4763 algorithm algorithms attribute authentication encryption key keys management tls trust nested-reference unchanged"},{"id":"IETF RFC 4789","type":"specification","body":"IETF","designation":"RFC 4789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4789.txt","https://www.rfc-editor.org/rfc/rfc4789.pdf"],"folder":"IETF/RFC-4789","files":{"txt":{"path":"standards/IETF/RFC-4789/RFC-4789.txt","sha256":"1f87de45e7f3f475b3be3b1b075d0f6fb9637a5a1ff06e5a85edde43e8a4b1ee"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how Simple Network Management Protocol (SNMP)\n messages can be transmitted directly over IEEE 802 networks.\n\n This document obsoletes RFC 1089.","scope_keywords":["4789","identification","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4789 This document specifies how Simple Network Management Protocol (SNMP)\n messages can be transmitted directly over IEEE 802 networks.\n\n This document obsoletes RFC 1089. 4789 identification key management trust nested-reference unchanged"},{"id":"IETF RFC 4795","type":"specification","body":"IETF","designation":"RFC 4795","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4795.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4795.txt","https://www.rfc-editor.org/rfc/rfc4795.pdf"],"folder":"IETF/RFC-4795","files":{"txt":{"path":"standards/IETF/RFC-4795/RFC-4795.txt","sha256":"84dc17ee8bf0d18c608a19318ce4b1d5b0fdded54732d098ed14cae98601d2df"}},"tags":["nested-reference","unchanged"],"summary":"The goal of Link-Local Multicast Name Resolution (LLMNR) is to enable\n name resolution in scenarios in which conventional DNS name\n resolution is not possible. LLMNR supports all current and future\n DNS formats, types, and classes, while operating on a separate port\n from DNS, and with a distinct resolver cache. Since LLMNR only\n operates on the local link, it cannot be considered a substitute for\n DNS.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 4795 LLMNR January 2007","scope_keywords":["4795","authentication","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null}],"search_text":"IETF RFC 4795 The goal of Link-Local Multicast Name Resolution (LLMNR) is to enable\n name resolution in scenarios in which conventional DNS name\n resolution is not possible. LLMNR supports all current and future\n DNS formats, types, and classes, while operating on a separate port\n from DNS, and with a distinct resolver cache. Since LLMNR only\n operates on the local link, it cannot be considered a substitute for\n DNS.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 4795 LLMNR January 2007 4795 authentication key trust nested-reference unchanged"},{"id":"IETF RFC 4814","type":"specification","body":"IETF","designation":"RFC 4814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4814.txt","https://www.rfc-editor.org/rfc/rfc4814.pdf"],"folder":"IETF/RFC-4814","files":{"txt":{"path":"standards/IETF/RFC-4814/RFC-4814.txt","sha256":"db545acb06e603e38c85c2a86ecf7106f3b00cbb822141b1b33e2a7d51a02edd"}},"tags":["nested-reference","unchanged"],"summary":"Test engineers take pains to declare all factors that affect a given\n measurement, including intended load, packet length, test duration,\n and traffic orientation. However, current benchmarking practice\n overlooks two factors that have a profound impact on test results.\n First, existing methodologies do not require the reporting of\n addresses or other test traffic contents, even though these fields\n can affect test results. Second, \"stuff\" bits and bytes inserted in\n test traffic by some link-layer technologies add significant and\n variable overhead, which in turn affects test results. This document\n describes the effects of these factors; recommends guidelines for\n test traffic contents; and offers formulas for determining the\n probability of bit- and byte-stuffing in test traffic.\n\nNewman & Player Informational [Page 1]\n\f\nRFC 4814 Hash and Stuffing March 2007","scope_keywords":["4814","hash","key","management","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null}],"search_text":"IETF RFC 4814 Test engineers take pains to declare all factors that affect a given\n measurement, including intended load, packet length, test duration,\n and traffic orientation. However, current benchmarking practice\n overlooks two factors that have a profound impact on test results.\n First, existing methodologies do not require the reporting of\n addresses or other test traffic contents, even though these fields\n can affect test results. Second, \"stuff\" bits and bytes inserted in\n test traffic by some link-layer technologies add significant and\n variable overhead, which in turn affects test results. This document\n describes the effects of these factors; recommends guidelines for\n test traffic contents; and offers formulas for determining the\n probability of bit- and byte-stuffing in test traffic.\n\nNewman & Player Informational [Page 1]\n\f\nRFC 4814 Hash and Stuffing March 2007 4814 hash key management timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 4840","type":"specification","body":"IETF","designation":"RFC 4840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4840.txt","https://www.rfc-editor.org/rfc/rfc4840.pdf"],"folder":"IETF/RFC-4840","files":{"txt":{"path":"standards/IETF/RFC-4840/RFC-4840.txt","sha256":"87172120ce46e2f766aa9a68a5d156d01e98404c656b3c17fb5e595527f54c2d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes architectural and operational issues that\n arise from link-layer protocols supporting multiple Internet Protocol\n encapsulation methods.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 4840 Multiple Encapsulation Methods Harmful April 2007","scope_keywords":["4840","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null}],"search_text":"IETF RFC 4840 This document describes architectural and operational issues that\n arise from link-layer protocols supporting multiple Internet Protocol\n encapsulation methods.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 4840 Multiple Encapsulation Methods Harmful April 2007 4840 key management trust nested-reference unchanged"},{"id":"IETF RFC 4861","type":"specification","body":"IETF","designation":"RFC 4861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4861.txt","https://www.rfc-editor.org/rfc/rfc4861.pdf"],"folder":"IETF/RFC-4861","files":{"txt":{"path":"standards/IETF/RFC-4861/RFC-4861.txt","sha256":"1a4309c117d765a7c0edfcb2297fc90c3c09f0fcae255f15e53b20748bcc09fb"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers, and to maintain reachability information\n about the paths to active neighbors.\n\nNarten, et al. Standards Track [Page 1]\n\f\nRFC 4861 Neighbor Discovery in IPv6 September 2007","scope_keywords":["4861","algorithm","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4943","folder":"IETF/RFC-4943","source":"IETF/RFC-4943/RFC-4943.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6105","folder":"IETF/RFC-6105","source":"IETF/RFC-6105/RFC-6105.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 4861 This document specifies the Neighbor Discovery protocol for IP\n Version 6. IPv6 nodes on the same link use Neighbor Discovery to\n discover each other's presence, to determine each other's link-layer\n addresses, to find routers, and to maintain reachability information\n about the paths to active neighbors.\n\nNarten, et al. Standards Track [Page 1]\n\f\nRFC 4861 Neighbor Discovery in IPv6 September 2007 4861 algorithm path validation nested-reference unchanged"},{"id":"IETF RFC 4862","type":"specification","body":"IETF","designation":"RFC 4862","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4862.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4862.txt","https://www.rfc-editor.org/rfc/rfc4862.pdf"],"folder":"IETF/RFC-4862","files":{"txt":{"path":"standards/IETF/RFC-4862/RFC-4862.txt","sha256":"6d3d2af5d2f6c9109b4ebd038ff7a6cec56771bbb0b5d8bd520357e03f097aa2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes generating a link-local address, generating global\n addresses via stateless address autoconfiguration, and the Duplicate\n Address Detection procedure to verify the uniqueness of the addresses\n on a link.\n\nThomson, et al. Standards Track [Page 1]\n\f\nRFC 4862 IPv6 Stateless Address Autoconfiguration September 2007","scope_keywords":["4862","algorithm","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 6603","folder":"IETF/RFC-6603","source":"IETF/RFC-6603/RFC-6603.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 4862 This document specifies the steps a host takes in deciding how to\n autoconfigure its interfaces in IP version 6. The autoconfiguration\n process includes generating a link-local address, generating global\n addresses via stateless address autoconfiguration, and the Duplicate\n Address Detection procedure to verify the uniqueness of the addresses\n on a link.\n\nThomson, et al. Standards Track [Page 1]\n\f\nRFC 4862 IPv6 Stateless Address Autoconfiguration September 2007 4862 algorithm validation nested-reference unchanged"},{"id":"IETF RFC 4907","type":"specification","body":"IETF","designation":"RFC 4907","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4907.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4907.txt","https://www.rfc-editor.org/rfc/rfc4907.pdf"],"folder":"IETF/RFC-4907","files":{"txt":{"path":"standards/IETF/RFC-4907/RFC-4907.txt","sha256":"744154e0b1545cc4ac4b850616c9a8c589d97a0afdd989eca3868ef11fa9f2e7"}},"tags":["nested-reference","unchanged"],"summary":"A link indication represents information provided by the link layer\n to higher layers regarding the state of the link. This document\n describes the role of link indications within the Internet\n architecture. While the judicious use of link indications can\n provide performance benefits, inappropriate use can degrade both\n robustness and performance. This document summarizes current\n proposals, describes the architectural issues, and provides examples\n of appropriate and inappropriate uses of link indications.\n\nIAB Informational [Page 1]\n\f\nRFC 4907 Link Indications June 2007","scope_keywords":["4907","key","path","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null}],"search_text":"IETF RFC 4907 A link indication represents information provided by the link layer\n to higher layers regarding the state of the link. This document\n describes the role of link indications within the Internet\n architecture. While the judicious use of link indications can\n provide performance benefits, inappropriate use can degrade both\n robustness and performance. This document summarizes current\n proposals, describes the architectural issues, and provides examples\n of appropriate and inappropriate uses of link indications.\n\nIAB Informational [Page 1]\n\f\nRFC 4907 Link Indications June 2007 4907 key path trust validation nested-reference unchanged"},{"id":"IETF RFC 4918","type":"specification","body":"IETF","designation":"RFC 4918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4918.txt","https://www.rfc-editor.org/rfc/rfc4918.pdf"],"folder":"IETF/RFC-4918","files":{"txt":{"path":"standards/IETF/RFC-4918/RFC-4918.txt","sha256":"619ad705b4c0e26af2d0652bb48ca1fa9bd080546993d46730d604b9fe2bdf25"}},"tags":["nested-reference","unchanged"],"summary":"Web Distributed Authoring and Versioning (WebDAV) consists of a set\n of methods, headers, and content-types ancillary to HTTP/1.1 for the\n management of resource properties, creation and management of\n resource collections, URL namespace manipulation, and resource\n locking (collision avoidance).\n\n RFC 2518 was published in February 1999, and this specification\n obsoletes RFC 2518 with minor revisions mostly due to\n interoperability experience.\n\nDusseault Standards Track [Page 1]\n\f\nRFC 4918 WebDAV June 2007","scope_keywords":["4918","http","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5397","folder":"IETF/RFC-5397","source":"IETF/RFC-5397/RFC-5397.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6585","folder":"IETF/RFC-6585","source":"IETF/RFC-6585/RFC-6585.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 4918 Web Distributed Authoring and Versioning (WebDAV) consists of a set\n of methods, headers, and content-types ancillary to HTTP/1.1 for the\n management of resource properties, creation and management of\n resource collections, URL namespace manipulation, and resource\n locking (collision avoidance).\n\n RFC 2518 was published in February 1999, and this specification\n obsoletes RFC 2518 with minor revisions mostly due to\n interoperability experience.\n\nDusseault Standards Track [Page 1]\n\f\nRFC 4918 WebDAV June 2007 4918 http management trust nested-reference unchanged"},{"id":"IETF RFC 4947","type":"specification","body":"IETF","designation":"RFC 4947","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4947.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4947.txt","https://www.rfc-editor.org/rfc/rfc4947.pdf"],"folder":"IETF/RFC-4947","files":{"txt":{"path":"standards/IETF/RFC-4947/RFC-4947.txt","sha256":"5887f6debad3fef20fcd0433b72b760d704f500d6993bdc0d6e53a42894c5ff3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the process of binding/associating IPv4/IPv6\n addresses with MPEG-2 Transport Streams (TS). This procedure is\n known as Address Resolution (AR) or Neighbor Discovery (ND). Such\n address resolution complements the higher-layer resource discovery\n tools that are used to advertise IP sessions.\n\n In MPEG-2 Networks, an IP address must be associated with a Packet ID\n (PID) value and a specific Transmission Multiplex. This document\n reviews current methods appropriate to a range of technologies (such\n as DVB (Digital Video Broadcasting), ATSC (Advanced Television\n Systems Committee), DOCSIS (Data-Over-Cable Service Interface\n Specifications), and variants). It also describes the interaction\n with well-known protocols for address management including DHCP, ARP,\n and the ND protocol.\n\nFairhurst & Montpetit Informational [Page 1]\n\f\nRFC 4947 AR Mechanisms for IP over MPEG-2","scope_keywords":["4947","encryption","management","path","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 4947 This document describes the process of binding/associating IPv4/IPv6\n addresses with MPEG-2 Transport Streams (TS). This procedure is\n known as Address Resolution (AR) or Neighbor Discovery (ND). Such\n address resolution complements the higher-layer resource discovery\n tools that are used to advertise IP sessions.\n\n In MPEG-2 Networks, an IP address must be associated with a Packet ID\n (PID) value and a specific Transmission Multiplex. This document\n reviews current methods appropriate to a range of technologies (such\n as DVB (Digital Video Broadcasting), ATSC (Advanced Television\n Systems Committee), DOCSIS (Data-Over-Cable Service Interface\n Specifications), and variants). It also describes the interaction\n with well-known protocols for address management including DHCP, ARP,\n and the ND protocol.\n\nFairhurst & Montpetit Informational [Page 1]\n\f\nRFC 4947 AR Mechanisms for IP over MPEG-2 4947 encryption management path pid trust nested-reference unchanged"},{"id":"IETF RFC 4957","type":"specification","body":"IETF","designation":"RFC 4957","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4957.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4957.txt","https://www.rfc-editor.org/rfc/rfc4957.pdf"],"folder":"IETF/RFC-4957","files":{"txt":{"path":"standards/IETF/RFC-4957/RFC-4957.txt","sha256":"5780e2aac601d86e33ab52ad210000be3d49130cc3458439faa1017d9e8e37bf"}},"tags":["nested-reference","unchanged"],"summary":"Certain network access technologies are capable of providing various\n types of link-layer status information to IP. Link-layer event\n notifications can help IP expeditiously detect configuration changes.\n This document provides a non-exhaustive catalogue of information\n available from well-known access technologies.\n\nKrishnan, et al. Informational [Page 1]\n\f\nRFC 4957 L2 Notifications for DNA August 2007","scope_keywords":["4957","identification","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 4957 Certain network access technologies are capable of providing various\n types of link-layer status information to IP. Link-layer event\n notifications can help IP expeditiously detect configuration changes.\n This document provides a non-exhaustive catalogue of information\n available from well-known access technologies.\n\nKrishnan, et al. Informational [Page 1]\n\f\nRFC 4957 L2 Notifications for DNA August 2007 4957 identification trust nested-reference unchanged"},{"id":"IETF RFC 4962","type":"specification","body":"IETF","designation":"RFC 4962","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4962.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4962.txt","https://www.rfc-editor.org/rfc/rfc4962.pdf"],"folder":"IETF/RFC-4962","files":{"txt":{"path":"standards/IETF/RFC-4962/RFC-4962.txt","sha256":"d8790e4b83bf6503eb25ef4977de62e9fdb3f29101c050294ac70b170b204235"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance to designers of Authentication,\n Authorization, and Accounting (AAA) key management protocols. The\n guidance is also useful to designers of systems and solutions that\n include AAA key management protocols. Given the complexity and\n difficulty in designing secure, long-lasting key management\n algorithms and protocols by experts in the field, it is almost\n certainly inappropriate for IETF working groups without deep\n expertise in the area to be designing their own key management\n algorithms and protocols based on Authentication, Authorization, and\n Accounting (AAA) protocols. The guidelines in this document apply to\n documents requesting publication as IETF RFCs. Further, these\n guidelines will be useful to other standards development\n organizations (SDOs) that specify AAA key management.\n\nHousley & Aboba Best Current Practice [Page 1]\n\f\nRFC 4962 Guidance fo","scope_keywords":["4962","algorithm","algorithms","authentication","authorization","encryption","key","management","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 4962 This document provides guidance to designers of Authentication,\n Authorization, and Accounting (AAA) key management protocols. The\n guidance is also useful to designers of systems and solutions that\n include AAA key management protocols. Given the complexity and\n difficulty in designing secure, long-lasting key management\n algorithms and protocols by experts in the field, it is almost\n certainly inappropriate for IETF working groups without deep\n expertise in the area to be designing their own key management\n algorithms and protocols based on Authentication, Authorization, and\n Accounting (AAA) protocols. The guidelines in this document apply to\n documents requesting publication as IETF RFCs. Further, these\n guidelines will be useful to other standards development\n organizations (SDOs) that specify AAA key management.\n\nHousley & Aboba Best Current Practice [Page 1]\n\f\nRFC 4962 Guidance fo 4962 algorithm algorithms authentication authorization encryption key management presentation trust nested-reference unchanged"},{"id":"IETF RFC 5080","type":"specification","body":"IETF","designation":"RFC 5080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5080.txt","https://www.rfc-editor.org/rfc/rfc5080.pdf"],"folder":"IETF/RFC-5080","files":{"txt":{"path":"standards/IETF/RFC-5080/RFC-5080.txt","sha256":"d740fa71e5ccc73b6497e95b4defc579bee5095ffa1c194c38a87d9e12208e3f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes common issues seen in Remote Authentication\n Dial In User Service (RADIUS) implementations and suggests some\n fixes. Where applicable, ambiguities and errors in previous RADIUS\n specifications are clarified.\n\nNelson & DeKok Standards Track [Page 1]\n\f\nRFC 5080 RADIUS Issues & Fixes December 2007","scope_keywords":["5080","attribute","attributes","authentication","delivery","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null}],"search_text":"IETF RFC 5080 This document describes common issues seen in Remote Authentication\n Dial In User Service (RADIUS) implementations and suggests some\n fixes. Where applicable, ambiguities and errors in previous RADIUS\n specifications are clarified.\n\nNelson & DeKok Standards Track [Page 1]\n\f\nRFC 5080 RADIUS Issues & Fixes December 2007 5080 attribute attributes authentication delivery key management nested-reference unchanged"},{"id":"IETF RFC 5102","type":"specification","body":"IETF","designation":"RFC 5102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5102.txt","https://www.rfc-editor.org/rfc/rfc5102.pdf"],"folder":"IETF/RFC-5102","files":{"txt":{"path":"standards/IETF/RFC-5102/RFC-5102.txt","sha256":"e66892d25ff38418bf59ecf384229e31e864b35cd4c3eceaebd101f3105ef91a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an information model for the IP Flow Information\n eXport (IPFIX) protocol. It is used by the IPFIX protocol for\n encoding measured traffic information and information related to the\n traffic Observation Point, the traffic Metering Process, and the\n Exporting Process. Although developed for the IPFIX protocol, the\n model is defined in an open way that easily allows using it in other\n protocols, interfaces, and applications.","scope_keywords":["5102","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5103","folder":"IETF/RFC-5103","source":"IETF/RFC-5103/RFC-5103.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 5102 This memo defines an information model for the IP Flow Information\n eXport (IPFIX) protocol. It is used by the IPFIX protocol for\n encoding measured traffic information and information related to the\n traffic Observation Point, the traffic Metering Process, and the\n Exporting Process. Although developed for the IPFIX protocol, the\n model is defined in an open way that easily allows using it in other\n protocols, interfaces, and applications. 5102 key nested-reference unchanged"},{"id":"IETF RFC 5113","type":"specification","body":"IETF","designation":"RFC 5113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5113.txt","https://www.rfc-editor.org/rfc/rfc5113.pdf"],"folder":"IETF/RFC-5113","files":{"txt":{"path":"standards/IETF/RFC-5113/RFC-5113.txt","sha256":"90923c145d3b99a17f12bb15d767ec34c88a12b1697493c88d77ec3eeb345f49"}},"tags":["nested-reference","unchanged"],"summary":"When multiple access networks are available, users may have\n difficulty in selecting which network to connect to and how to\n authenticate with that network. This document defines the network\n discovery and selection problem, dividing it into multiple sub-\n problems. Some constraints on potential solutions are outlined, and\n the limitations of several solutions (including existing ones) are\n discussed.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 5113 Network Discovery and SP January 2008","scope_keywords":["5113","authentication","credential","credentials","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null}],"search_text":"IETF RFC 5113 When multiple access networks are available, users may have\n difficulty in selecting which network to connect to and how to\n authenticate with that network. This document defines the network\n discovery and selection problem, dividing it into multiple sub-\n problems. Some constraints on potential solutions are outlined, and\n the limitations of several solutions (including existing ones) are\n discussed.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 5113 Network Discovery and SP January 2008 5113 authentication credential credentials management path policy nested-reference unchanged"},{"id":"IETF RFC 5121","type":"specification","body":"IETF","designation":"RFC 5121","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5121.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5121.txt","https://www.rfc-editor.org/rfc/rfc5121.pdf"],"folder":"IETF/RFC-5121","files":{"txt":{"path":"standards/IETF/RFC-5121/RFC-5121.txt","sha256":"d75845e23cbb48f4ae510ba9b603a270c8a24c74a883293ee218b58cb298227b"}},"tags":["nested-reference","unchanged"],"summary":"IEEE Std 802.16 is an air interface specification for fixed and\n mobile Broadband Wireless Access Systems. Service-specific\n convergence sublayers to which upper-layer protocols interface are a\n part of the IEEE 802.16 MAC (Medium Access Control). The Packet\n convergence sublayer (CS) is used for the transport of all packet-\n based protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN\n CSMA/CD Access Method (Ethernet). IPv6 packets can be sent and\n received via the IP-specific part of the Packet CS. This document\n specifies the addressing and operation of IPv6 over the IP-specific\n part of the Packet CS for hosts served by a network that utilizes the\n IEEE Std 802.16 air interface. It recommends the assignment of a\n unique prefix (or prefixes) to each host and allows the host to use\n multiple identifiers within that prefix, including support for\n randomly generated interface id","scope_keywords":["5121","key","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 5121 IEEE Std 802.16 is an air interface specification for fixed and\n mobile Broadband Wireless Access Systems. Service-specific\n convergence sublayers to which upper-layer protocols interface are a\n part of the IEEE 802.16 MAC (Medium Access Control). The Packet\n convergence sublayer (CS) is used for the transport of all packet-\n based protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN\n CSMA/CD Access Method (Ethernet). IPv6 packets can be sent and\n received via the IP-specific part of the Packet CS. This document\n specifies the addressing and operation of IPv6 over the IP-specific\n part of the Packet CS for hosts served by a network that utilizes the\n IEEE Std 802.16 air interface. It recommends the assignment of a\n unique prefix (or prefixes) to each host and allows the host to use\n multiple identifiers within that prefix, including support for\n randomly generated interface id 5121 key license nested-reference unchanged"},{"id":"IETF RFC 5154","type":"specification","body":"IETF","designation":"RFC 5154","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5154.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5154.txt","https://www.rfc-editor.org/rfc/rfc5154.pdf"],"folder":"IETF/RFC-5154","files":{"txt":{"path":"standards/IETF/RFC-5154/RFC-5154.txt","sha256":"30520b88daec00c7e0da76dd4d327fb6315f16c79cba338d11d7964496799fdd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies problems in running IP over IEEE 802.16\n networks by identifying specific gaps in the IEEE 802.16 Media Access\n Control (MAC) for IPv4 and IPv6 support. This document also provides\n an overview of IEEE 802.16 network characteristics and convergence\n sublayers. Common terminology used for the base guideline while\n defining the solution framework is also presented.","scope_keywords":["5154","attribute","attributes","encryption","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null}],"search_text":"IETF RFC 5154 This document specifies problems in running IP over IEEE 802.16\n networks by identifying specific gaps in the IEEE 802.16 Media Access\n Control (MAC) for IPv4 and IPv6 support. This document also provides\n an overview of IEEE 802.16 network characteristics and convergence\n sublayers. Common terminology used for the base guideline while\n defining the solution framework is also presented. 5154 attribute attributes encryption management nested-reference unchanged"},{"id":"IETF RFC 5176","type":"specification","body":"IETF","designation":"RFC 5176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5176.txt","https://www.rfc-editor.org/rfc/rfc5176.pdf"],"folder":"IETF/RFC-5176","files":{"txt":{"path":"standards/IETF/RFC-5176/RFC-5176.txt","sha256":"084ee4d8a99866ad6a121847861cb3eed1dd5623ef00515d0a7985fce791e958"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a currently deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, allowing\n dynamic changes to a user session, as implemented by network access\n server products. This includes support for disconnecting users and\n changing authorizations applicable to a user session.\n\nChiba, et al. Informational [Page 1]\n\f\nRFC 5176 Dynamic Authorization Extensions to RADIUS January 2008","scope_keywords":["5176","algorithm","algorithms","attribute","attributes","authentication","authorization","identification","key","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null}],"search_text":"IETF RFC 5176 This document describes a currently deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, allowing\n dynamic changes to a user session, as implemented by network access\n server products. This includes support for disconnecting users and\n changing authorizations applicable to a user session.\n\nChiba, et al. Informational [Page 1]\n\f\nRFC 5176 Dynamic Authorization Extensions to RADIUS January 2008 5176 algorithm algorithms attribute attributes authentication authorization identification key path timestamp nested-reference unchanged"},{"id":"IETF RFC 5216","type":"specification","body":"IETF","designation":"RFC 5216","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5216.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5216.txt","https://www.rfc-editor.org/rfc/rfc5216.pdf"],"folder":"IETF/RFC-5216","files":{"txt":{"path":"standards/IETF/RFC-5216/RFC-5216.txt","sha256":"4cb073306d1fd4f33290b8e4a0ba4a985980b984d071567d624983b39de53185"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides support for multiple authentication methods. Transport\n Layer Security (TLS) provides for mutual authentication, integrity-\n protected ciphersuite negotiation, and key exchange between two\n endpoints. This document defines EAP-TLS, which includes support for\n certificate-based mutual authentication and key derivation.\n\n This document obsoletes RFC 2716. A summary of the changes between\n this document and RFC 2716 is available in Appendix A.\n\nSimon, et al. Standards Track [Page 1]\n\f\nRFC 5216 EAP-TLS Authentication Protocol March 2008","scope_keywords":["5216","authentication","certificate","key","management","revocation","tls","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 5216 The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides support for multiple authentication methods. Transport\n Layer Security (TLS) provides for mutual authentication, integrity-\n protected ciphersuite negotiation, and key exchange between two\n endpoints. This document defines EAP-TLS, which includes support for\n certificate-based mutual authentication and key derivation.\n\n This document obsoletes RFC 2716. A summary of the changes between\n this document and RFC 2716 is available in Appendix A.\n\nSimon, et al. Standards Track [Page 1]\n\f\nRFC 5216 EAP-TLS Authentication Protocol March 2008 5216 authentication certificate key management revocation tls validation nested-reference unchanged"},{"id":"IETF RFC 5227","type":"specification","body":"IETF","designation":"RFC 5227","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5227.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5227.txt","https://www.rfc-editor.org/rfc/rfc5227.pdf"],"folder":"IETF/RFC-5227","files":{"txt":{"path":"standards/IETF/RFC-5227/RFC-5227.txt","sha256":"bfe6de915c68fddffa6bee54dd217a377d2c694c4233cef1696c936d4202ecd4"}},"tags":["nested-reference","unchanged"],"summary":"When two hosts on the same link attempt to use the same IPv4 address\n at the same time (except in rare special cases where this has been\n arranged by prior coordination), problems ensue for one or both\n hosts. This document describes (i) a simple precaution that a host\n can take in advance to help prevent this misconfiguration from\n happening, and (ii) if this misconfiguration does occur, a simple\n mechanism by which a host can passively detect, after the fact, that\n it has happened, so that the host or administrator may respond to\n rectify the problem.\n\nCheshire Standards Track [Page 1]\n\f\nRFC 5227 IPv4 Address Conflict Detection July 2008","scope_keywords":["5227","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null}],"search_text":"IETF RFC 5227 When two hosts on the same link attempt to use the same IPv4 address\n at the same time (except in rare special cases where this has been\n arranged by prior coordination), problems ensue for one or both\n hosts. This document describes (i) a simple precaution that a host\n can take in advance to help prevent this misconfiguration from\n happening, and (ii) if this misconfiguration does occur, a simple\n mechanism by which a host can passively detect, after the fact, that\n it has happened, so that the host or administrator may respond to\n rectify the problem.\n\nCheshire Standards Track [Page 1]\n\f\nRFC 5227 IPv4 Address Conflict Detection July 2008 5227 management path nested-reference unchanged"},{"id":"IETF RFC 5247","type":"specification","body":"IETF","designation":"RFC 5247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5247.txt","https://www.rfc-editor.org/rfc/rfc5247.pdf"],"folder":"IETF/RFC-5247","files":{"txt":{"path":"standards/IETF/RFC-5247/RFC-5247.txt","sha256":"616ab9161cea63bf3637f7769a1e41bed57325d719e01482991344aab912f032"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n enables extensible network access authentication. This document\n specifies the EAP key hierarchy and provides a framework for the\n transport and usage of keying material and parameters generated by\n EAP authentication algorithms, known as \"methods\". It also provides\n a detailed system-level security analysis, describing the conditions\n under which the key management guidelines described in RFC 4962 can\n be satisfied.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 5247 EAP Key Management Framework August 2008","scope_keywords":["5247","algorithm","algorithms","authentication","authorization","identification","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 5247 The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n enables extensible network access authentication. This document\n specifies the EAP key hierarchy and provides a framework for the\n transport and usage of keying material and parameters generated by\n EAP authentication algorithms, known as \"methods\". It also provides\n a detailed system-level security analysis, describing the conditions\n under which the key management guidelines described in RFC 4962 can\n be satisfied.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 5247 EAP Key Management Framework August 2008 5247 algorithm algorithms authentication authorization identification key keys management nested-reference unchanged"},{"id":"IETF RFC 5494","type":"specification","body":"IETF","designation":"RFC 5494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5494.txt","https://www.rfc-editor.org/rfc/rfc5494.pdf"],"folder":"IETF/RFC-5494","files":{"txt":{"path":"standards/IETF/RFC-5494/RFC-5494.txt","sha256":"f1e80827b1a5a51d4635b77189bed75ace37155cb93cbb9ec73d2602cef92288"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IANA guidelines for allocating new values\n in the Address Resolution Protocol (ARP). This document also\n reserves some numbers for experimentation purposes. The changes also\n affect other protocols that employ values from the ARP name spaces.\n\nArkko & Pignataro Standards Track [Page 1]\n\f\nRFC 5494 ARP IANA Rules April 2009\n\n1. Introduction\n\n This document specifies the IANA guidelines [RFC5226] for allocating\n new values for various fields in the Address Resolution Protocol\n (ARP) [RFC0826]. The change is also applicable to extensions of ARP\n that use the same message format, such as [RFC0903], [RFC1931], and\n [RFC2390].\n\n The change also affects other protocols that employ values from the\n ARP name spaces. For instance, the ARP hardware address type\n (ar$hrd) number space is also used in the \"htype\" (hardware address\n type) fields in the Bootstrap Protocol (BO","scope_keywords":["5494","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null}],"search_text":"IETF RFC 5494 This document specifies the IANA guidelines for allocating new values\n in the Address Resolution Protocol (ARP). This document also\n reserves some numbers for experimentation purposes. The changes also\n affect other protocols that employ values from the ARP name spaces.\n\nArkko & Pignataro Standards Track [Page 1]\n\f\nRFC 5494 ARP IANA Rules April 2009\n\n1. Introduction\n\n This document specifies the IANA guidelines [RFC5226] for allocating\n new values for various fields in the Address Resolution Protocol\n (ARP) [RFC0826]. The change is also applicable to extensions of ARP\n that use the same message format, such as [RFC0903], [RFC1931], and\n [RFC2390].\n\n The change also affects other protocols that employ values from the\n ARP name spaces. For instance, the ARP hardware address type\n (ar$hrd) number space is also used in the \"htype\" (hardware address\n type) fields in the Bootstrap Protocol (BO 5494 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5556","type":"specification","body":"IETF","designation":"RFC 5556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5556.txt","https://www.rfc-editor.org/rfc/rfc5556.pdf"],"folder":"IETF/RFC-5556","files":{"txt":{"path":"standards/IETF/RFC-5556/RFC-5556.txt","sha256":"d6e7cda4329a883121d7d846b5f8da92b4f16a964c551c6be18663dba091bfca"}},"tags":["nested-reference","unchanged"],"summary":"Current IEEE 802.1 LANs use spanning tree protocols that have a\n number of challenges. These protocols need to strictly avoid loops,\n even temporary ones, during route propagation, because of the lack of\n header loop detection support. Routing tends not to take full\n advantage of alternate paths, or even non-overlapping pairwise paths\n (in the case of spanning trees). This document addresses these\n concerns and suggests applying modern network-layer routing protocols\n at the link layer. This document assumes that solutions would not\n address issues of scalability beyond that of existing IEEE 802.1\n bridged links, but that a solution would be backward compatible with\n 802.1, including hubs, bridges, and their existing plug-and-play\n capabilities.\n\nTouch & Perlman Informational [Page 1]\n\f\nRFC 5556 TRILL: Problem and Applicability May 2009","scope_keywords":["5556","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null}],"search_text":"IETF RFC 5556 Current IEEE 802.1 LANs use spanning tree protocols that have a\n number of challenges. These protocols need to strictly avoid loops,\n even temporary ones, during route propagation, because of the lack of\n header loop detection support. Routing tends not to take full\n advantage of alternate paths, or even non-overlapping pairwise paths\n (in the case of spanning trees). This document addresses these\n concerns and suggests applying modern network-layer routing protocols\n at the link layer. This document assumes that solutions would not\n address issues of scalability beyond that of existing IEEE 802.1\n bridged links, but that a solution would be backward compatible with\n 802.1, including hubs, bridges, and their existing plug-and-play\n capabilities.\n\nTouch & Perlman Informational [Page 1]\n\f\nRFC 5556 TRILL: Problem and Applicability May 2009 5556 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5570","type":"specification","body":"IETF","designation":"RFC 5570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5570.txt","https://www.rfc-editor.org/rfc/rfc5570.pdf"],"folder":"IETF/RFC-5570","files":{"txt":{"path":"standards/IETF/RFC-5570/RFC-5570.txt","sha256":"634d474f784ab82bd7f10e8bc29bc463e5d333897dd6a87b02fc6f342a916986"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an optional method for encoding explicit\n packet Sensitivity Labels on IPv6 packets. It is intended for use\n only within Multi-Level Secure (MLS) networking environments that are\n both trusted and trustworthy.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nIESG Note\n\n This RFC specifies the use of an IPv6 hop-by-hop option. The IESG\n notes that general deployment of protocols with hop-by-hop options\n are problematic, and the development of such protocols is\n consequently discouraged. After careful review, the IETF has\n determined that a hop-by-hop option is an appropriate solution for\n this specific limited environment and use case. Furthermore, the\n mechanism specified in this RFC is only applicable to closed IP\n networks. It is unsu","scope_keywords":["5570","encryption","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null}],"search_text":"IETF RFC 5570 This document describes an optional method for encoding explicit\n packet Sensitivity Labels on IPv6 packets. It is intended for use\n only within Multi-Level Secure (MLS) networking environments that are\n both trusted and trustworthy.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nIESG Note\n\n This RFC specifies the use of an IPv6 hop-by-hop option. The IESG\n notes that general deployment of protocols with hop-by-hop options\n are problematic, and the development of such protocols is\n consequently discouraged. After careful review, the IETF has\n determined that a hop-by-hop option is an appropriate solution for\n this specific limited environment and use case. Furthermore, the\n mechanism specified in this RFC is only applicable to closed IP\n networks. It is unsu 5570 encryption http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5798","type":"specification","body":"IETF","designation":"RFC 5798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5798.txt","https://www.rfc-editor.org/rfc/rfc5798.pdf"],"folder":"IETF/RFC-5798","files":{"txt":{"path":"standards/IETF/RFC-5798/RFC-5798.txt","sha256":"8c82b43dc73bb3f0bffb3c79d9c6107b2a4549008988e2d5c1f63f2dfc1571e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Virtual Router Redundancy Protocol (VRRP) for\n IPv4 and IPv6. It is version three (3) of the protocol, and it is\n based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in\n \"Virtual Router Redundancy Protocol for IPv6\". VRRP specifies an\n election protocol that dynamically assigns responsibility for a\n virtual router to one of the VRRP routers on a LAN. The VRRP router\n controlling the IPv4 or IPv6 address(es) associated with a virtual\n router is called the Master, and it forwards packets sent to these\n IPv4 or IPv6 addresses. VRRP Master routers are configured with\n virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the\n address family of the virtual addresses being carried based on the\n transport protocol. Within a VRRP router, the virtual routers in\n each of the IPv4 and IPv6 address families are a domain unto\n themselves and do not overlap","scope_keywords":["5798","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 5798 This memo defines the Virtual Router Redundancy Protocol (VRRP) for\n IPv4 and IPv6. It is version three (3) of the protocol, and it is\n based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in\n \"Virtual Router Redundancy Protocol for IPv6\". VRRP specifies an\n election protocol that dynamically assigns responsibility for a\n virtual router to one of the VRRP routers on a LAN. The VRRP router\n controlling the IPv4 or IPv6 address(es) associated with a virtual\n router is called the Master, and it forwards packets sent to these\n IPv4 or IPv6 addresses. VRRP Master routers are configured with\n virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the\n address family of the virtual addresses being carried based on the\n transport protocol. Within a VRRP router, the virtual routers in\n each of the IPv4 and IPv6 address families are a domain unto\n themselves and do not overlap 5798 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5836","type":"specification","body":"IETF","designation":"RFC 5836","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5836.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5836.txt","https://www.rfc-editor.org/rfc/rfc5836.pdf"],"folder":"IETF/RFC-5836","files":{"txt":{"path":"standards/IETF/RFC-5836/RFC-5836.txt","sha256":"4bd2da31980551ffb15fe32d12656ea4f5fe22b5184a2d4fd4515c99a9c937a8"}},"tags":["nested-reference","unchanged"],"summary":"Extensible Authentication Protocol (EAP) early authentication may be\n defined as the use of EAP by a mobile device to establish\n authenticated keying material on a target attachment point prior to\n its arrival. This document discusses the EAP early authentication\n problem in detail.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta","scope_keywords":["5836","authentication","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null}],"search_text":"IETF RFC 5836 Extensible Authentication Protocol (EAP) early authentication may be\n defined as the use of EAP by a mobile device to establish\n authenticated keying material on a target attachment point prior to\n its arrival. This document discusses the EAP early authentication\n problem in detail.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta 5836 authentication authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5998","type":"specification","body":"IETF","designation":"RFC 5998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5998.txt","https://www.rfc-editor.org/rfc/rfc5998.pdf"],"folder":"IETF/RFC-5998","files":{"txt":{"path":"standards/IETF/RFC-5998/RFC-5998.txt","sha256":"a95b460446362fdb051803458f5dc439471fb4bcdbfda2b3715e3fe557f68615"}},"tags":["nested-reference","unchanged"],"summary":"IKEv2 specifies that Extensible Authentication Protocol (EAP)\n authentication must be used together with responder authentication\n based on public key signatures. This is necessary with old EAP\n methods that provide only unilateral authentication using, e.g., one-\n time passwords or token cards.\n\n This document specifies how EAP methods that provide mutual\n authentication and key agreement can be used to provide extensible\n responder authentication for IKEv2 based on methods other than public\n key signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section ","scope_keywords":["5998","authentication","authorization","certificate","credential","credentials","http","key","license","management","pki","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5998 IKEv2 specifies that Extensible Authentication Protocol (EAP)\n authentication must be used together with responder authentication\n based on public key signatures. This is necessary with old EAP\n methods that provide only unilateral authentication using, e.g., one-\n time passwords or token cards.\n\n This document specifies how EAP methods that provide mutual\n authentication and key agreement can be used to provide extensible\n responder authentication for IKEv2 based on methods other than public\n key signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section  5998 authentication authorization certificate credential credentials http key license management pki signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6021","type":"specification","body":"IETF","designation":"RFC 6021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6021.txt","https://www.rfc-editor.org/rfc/rfc6021.pdf"],"folder":"IETF/RFC-6021","files":{"txt":{"path":"standards/IETF/RFC-6021/RFC-6021.txt","sha256":"97a5d6e71ad40990088636ba982e7c301e5a497b6679f117cc99c04035727dcd"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces a collection of common data types to be used\n with the YANG data modeling language.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6021.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n","scope_keywords":["6021","http","key","license","management","path","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 6021 This document introduces a collection of common data types to be used\n with the YANG data modeling language.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6021.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n 6021 http key license management path subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6158","type":"specification","body":"IETF","designation":"RFC 6158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6158.txt","https://www.rfc-editor.org/rfc/rfc6158.pdf"],"folder":"IETF/RFC-6158","files":{"txt":{"path":"standards/IETF/RFC-6158/RFC-6158.txt","sha256":"273a3bce275466fa8882877db5498843060379654c99bae9f4a344d44135b291"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for the design of attributes used\n by the Remote Authentication Dial In User Service (RADIUS) protocol.\n It is expected that these guidelines will prove useful to authors and\n reviewers of future RADIUS attribute specifications, within the IETF\n as well as other Standards Development Organizations (SDOs).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6158.\n","scope_keywords":["6158","attribute","attributes","authentication","authorization","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null}],"search_text":"IETF RFC 6158 This document provides guidelines for the design of attributes used\n by the Remote Authentication Dial In User Service (RADIUS) protocol.\n It is expected that these guidelines will prove useful to authors and\n reviewers of future RADIUS attribute specifications, within the IETF\n as well as other Standards Development Organizations (SDOs).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6158.\n 6158 attribute attributes authentication authorization http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6222","type":"specification","body":"IETF","designation":"RFC 6222","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6222.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6222.txt","https://www.rfc-editor.org/rfc/rfc6222.pdf"],"folder":"IETF/RFC-6222","files":{"txt":{"path":"standards/IETF/RFC-6222/RFC-6222.txt","sha256":"010795e127dd81a987c0233f576f09dd2d0f5e85aaecd3dc778f7dbd0cfc32bc"}},"tags":["nested-reference","unchanged"],"summary":"The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a\n persistent transport-level identifier for an RTP endpoint. While the\n Synchronization Source (SSRC) identifier of an RTP endpoint may\n change if a collision is detected or when the RTP application is\n restarted, its RTCP CNAME is meant to stay unchanged, so that RTP\n endpoints can be uniquely identified and associated with their RTP\n media streams. For proper functionality, RTCP CNAMEs should be\n unique within the participants of an RTP session. However, the\n existing guidelines for choosing the RTCP CNAME provided in the RTP\n standard are insufficient to achieve this uniqueness. This memo\n updates those guidelines to allow endpoints to choose unique RTCP\n CNAMEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co","scope_keywords":["6222","http","key","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null}],"search_text":"IETF RFC 6222 The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a\n persistent transport-level identifier for an RTP endpoint. While the\n Synchronization Source (SSRC) identifier of an RTP endpoint may\n change if a collision is detected or when the RTP application is\n restarted, its RTCP CNAME is meant to stay unchanged, so that RTP\n endpoints can be uniquely identified and associated with their RTP\n media streams. For proper functionality, RTCP CNAMEs should be\n unique within the participants of an RTP session. However, the\n existing guidelines for choosing the RTCP CNAME provided in the RTP\n standard are insufficient to achieve this uniqueness. This memo\n updates those guidelines to allow endpoints to choose unique RTCP\n CNAMEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co 6222 http key license presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6275","type":"specification","body":"IETF","designation":"RFC 6275","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6275.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6275.txt","https://www.rfc-editor.org/rfc/rfc6275.pdf"],"folder":"IETF/RFC-6275","files":{"txt":{"path":"standards/IETF/RFC-6275/RFC-6275.txt","sha256":"5773ab98e91a06be49ac9f3821836dca6372227e2126db81c414f938c03fe20a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Mobile IPv6, a protocol that allows nodes to\n remain reachable while moving around in the IPv6 Internet. Each\n mobile node is always identified by its home address, regardless of\n its current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about the mobile node's current\n location. IPv6 packets addressed to a mobile node's home address are\n transparently routed to its care-of address. The protocol enables\n IPv6 nodes to cache the binding of a mobile node's home address with\n its care-of address, and to then send any packets destined for the\n mobile node directly to it at this care-of address. To support this\n operation, Mobile IPv6 defines a new IPv6 protocol and a new\n destination option. All IPv6 nodes, whether mobile or stationary,\n can communicate with","scope_keywords":["6275","authorization","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 6275 This document specifies Mobile IPv6, a protocol that allows nodes to\n remain reachable while moving around in the IPv6 Internet. Each\n mobile node is always identified by its home address, regardless of\n its current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about the mobile node's current\n location. IPv6 packets addressed to a mobile node's home address are\n transparently routed to its care-of address. The protocol enables\n IPv6 nodes to cache the binding of a mobile node's home address with\n its care-of address, and to then send any packets destined for the\n mobile node directly to it at this care-of address. To support this\n operation, Mobile IPv6 defines a new IPv6 protocol and a new\n destination option. All IPv6 nodes, whether mobile or stationary,\n can communicate with 6275 authorization http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6320","type":"specification","body":"IETF","designation":"RFC 6320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6320.txt","https://www.rfc-editor.org/rfc/rfc6320.pdf"],"folder":"IETF/RFC-6320","files":{"txt":{"path":"standards/IETF/RFC-6320/RFC-6320.txt","sha256":"597cca01fc9891eae07c0da4f406ddd796cf467178ead26d5fc77eab286e91b2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Access Node Control Protocol (ANCP).\n ANCP operates between a Network Access Server (NAS) and an Access\n Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in\n a multi-service reference architecture in order to perform operations\n related to Quality of Service, service, and subscribers. Use cases\n for ANCP are documented in RFC 5851. As well as describing the base\n ANCP protocol, this document specifies capabilities for Digital\n Subscriber Line (DSL) topology discovery, line configuration, and\n remote line connectivity testing. The design of ANCP allows for\n protocol extensions in other documents if they are needed to support\n other use cases and other access technologies.\n\n ANCP is based on the General Switch Management Protocol version 3\n (GSMPv3) described in RFC 3292, but with many modifications and\n extensions, to the point that the two pro","scope_keywords":["6320","attribute","attributes","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 6320 This document describes the Access Node Control Protocol (ANCP).\n ANCP operates between a Network Access Server (NAS) and an Access\n Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in\n a multi-service reference architecture in order to perform operations\n related to Quality of Service, service, and subscribers. Use cases\n for ANCP are documented in RFC 5851. As well as describing the base\n ANCP protocol, this document specifies capabilities for Digital\n Subscriber Line (DSL) topology discovery, line configuration, and\n remote line connectivity testing. The design of ANCP allows for\n protocol extensions in other documents if they are needed to support\n other use cases and other access technologies.\n\n ANCP is based on the General Switch Management Protocol version 3\n (GSMPv3) described in RFC 3292, but with many modifications and\n extensions, to the point that the two pro 6320 attribute attributes http identification license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6328","type":"specification","body":"IETF","designation":"RFC 6328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6328.txt","https://www.rfc-editor.org/rfc/rfc6328.pdf"],"folder":"IETF/RFC-6328","files":{"txt":{"path":"standards/IETF/RFC-6328/RFC-6328.txt","sha256":"75a084ed75202ef35ef4eadd486c25384137012384d57201c42d928096adc5e3"}},"tags":["nested-reference","unchanged"],"summary":"Some protocols being developed or extended by the IETF make use of\n the ISO/IEC (International Organization for Standardization /\n International Electrotechnical Commission) Network Layer Protocol\n Identifier (NLPID). This document provides NLPID IANA\n considerations.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6328.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identi","scope_keywords":["6328","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 6328 Some protocols being developed or extended by the IETF make use of\n the ISO/IEC (International Organization for Standardization /\n International Electrotechnical Commission) Network Layer Protocol\n Identifier (NLPID). This document provides NLPID IANA\n considerations.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6328.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identi 6328 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6459","type":"specification","body":"IETF","designation":"RFC 6459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6459.txt","https://www.rfc-editor.org/rfc/rfc6459.pdf"],"folder":"IETF/RFC-6459","files":{"txt":{"path":"standards/IETF/RFC-6459/RFC-6459.txt","sha256":"6c93f61936eb2e5acee396dba4d572050430b93f943e6af1d459dd02f1f5a92c"}},"tags":["nested-reference","unchanged"],"summary":"The use of cellular broadband for accessing the Internet and other\n data services via smartphones, tablets, and notebook/netbook\n computers has increased rapidly as a result of high-speed packet data\n networks such as HSPA, HSPA+, and now Long-Term Evolution (LTE) being\n deployed. Operators that have deployed networks based on 3rd\n Generation Partnership Project (3GPP) network architectures are\n facing IPv4 address shortages at the Internet registries and are\n feeling pressure to migrate to IPv6. This document describes the\n support for IPv6 in 3GPP network architectures.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publ","scope_keywords":["6459","attribute","http","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 6459 The use of cellular broadband for accessing the Internet and other\n data services via smartphones, tablets, and notebook/netbook\n computers has increased rapidly as a result of high-speed packet data\n networks such as HSPA, HSPA+, and now Long-Term Evolution (LTE) being\n deployed. Operators that have deployed networks based on 3rd\n Generation Partnership Project (3GPP) network architectures are\n facing IPv4 address shortages at the Internet registries and are\n feeling pressure to migrate to IPv6. This document describes the\n support for IPv6 in 3GPP network architectures.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publ 6459 attribute http license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6632","type":"specification","body":"IETF","designation":"RFC 6632","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6632.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6632.txt","https://www.rfc-editor.org/rfc/rfc6632.pdf"],"folder":"IETF/RFC-6632","files":{"txt":{"path":"standards/IETF/RFC-6632/RFC-6632.txt","sha256":"ba9509de7b0b75c83c33c5c389ddb31fa3a8748718902d5aa7ea32349fffbd66"}},"tags":["nested-reference","unchanged"],"summary":"This document gives an overview of the IETF network management\n standards and summarizes existing and ongoing development of IETF\n Standards Track network management protocols and data models. The\n document refers to other overview documents, where they exist and\n classifies the standards for easy orientation. The purpose of this\n document is, on the one hand, to help system developers and users to\n select appropriate standard management protocols and data models to\n address relevant management needs. On the other hand, the document\n can be used as an overview and guideline by other Standard\n Development Organizations or bodies planning to use IETF management\n technologies and data models. This document does not cover\n Operations, Administration, and Maintenance (OAM) technologies on the\n data-path, e.g., OAM of tunnels, MPLS Transport Profile (MPLS-TP)\n OAM, and pseudowire as well as th","scope_keywords":["6632","authentication","http","license","management","path","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 6632 This document gives an overview of the IETF network management\n standards and summarizes existing and ongoing development of IETF\n Standards Track network management protocols and data models. The\n document refers to other overview documents, where they exist and\n classifies the standards for easy orientation. The purpose of this\n document is, on the one hand, to help system developers and users to\n select appropriate standard management protocols and data models to\n address relevant management needs. On the other hand, the document\n can be used as an overview and guideline by other Standard\n Development Organizations or bodies planning to use IETF management\n technologies and data models. This document does not cover\n Operations, Administration, and Maintenance (OAM) technologies on the\n data-path, e.g., OAM of tunnels, MPLS Transport Profile (MPLS-TP)\n OAM, and pseudowire as well as th 6632 authentication http license management path policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6677","type":"specification","body":"IETF","designation":"RFC 6677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6677.txt","https://www.rfc-editor.org/rfc/rfc6677.pdf"],"folder":"IETF/RFC-6677","files":{"txt":{"path":"standards/IETF/RFC-6677/RFC-6677.txt","sha256":"4c22ff7fffe8acedda593a3a61322af441b9eeea5873864a492b53145638852a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines how to implement channel bindings for\n Extensible Authentication Protocol (EAP) methods to address the\n \"lying Network Access Service (NAS)\" problem as well as the \"lying\n provider\" problem.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6677.\n\nHartman, et al. Standards Track [Page 1]\n\f\nRFC 6677 EAP Channel Binding July 2012\n\nCopyright Notice\n\n Copyright (c) 2012 I","scope_keywords":["6677","attribute","authentication","authorization","credential","credentials","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 6677 This document defines how to implement channel bindings for\n Extensible Authentication Protocol (EAP) methods to address the\n \"lying Network Access Service (NAS)\" problem as well as the \"lying\n provider\" problem.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6677.\n\nHartman, et al. Standards Track [Page 1]\n\f\nRFC 6677 EAP Channel Binding July 2012\n\nCopyright Notice\n\n Copyright (c) 2012 I 6677 attribute authentication authorization credential credentials http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6763","type":"specification","body":"IETF","designation":"RFC 6763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6763.txt","https://www.rfc-editor.org/rfc/rfc6763.pdf"],"folder":"IETF/RFC-6763","files":{"txt":{"path":"standards/IETF/RFC-6763/RFC-6763.txt","sha256":"624208b2b36b91809475c0612a9bd168b34a4e2d4fdca8302ba99ffb43de98e7"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how DNS resource records are named and\n structured to facilitate service discovery. Given a type of service\n that a client is looking for, and a domain in which the client is\n looking for that service, this mechanism allows clients to discover\n a list of named instances of that desired service, using standard\n DNS queries. This mechanism is referred to as DNS-based Service\n Discovery, or DNS-SD.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how","scope_keywords":["6763","http","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null}],"search_text":"IETF RFC 6763 This document specifies how DNS resource records are named and\n structured to facilitate service discovery. Given a type of service\n that a client is looking for, and a domain in which the client is\n looking for that service, this mechanism allows clients to discover\n a list of named instances of that desired service, using standard\n DNS queries. This mechanism is referred to as DNS-based Service\n Discovery, or DNS-SD.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how 6763 http key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6822","type":"specification","body":"IETF","designation":"RFC 6822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6822.txt","https://www.rfc-editor.org/rfc/rfc6822.pdf"],"folder":"IETF/RFC-6822","files":{"txt":{"path":"standards/IETF/RFC-6822/RFC-6822.txt","sha256":"18a342e3047cc69978200f29cc1fa02cfdd079b86fcbc7719293d05f9fa50fdd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that allows a single router to\n share one or more circuits among multiple Intermediate System to\n Intermediate System (IS-IS) routing protocol instances.\n\n Multiple instances allow the isolation of resources associated with\n each instance. Routers will form instance-specific adjacencies.\n Each instance can support multiple topologies. Each topology has a\n unique Link State Database (LSDB). Each Protocol Data Unit (PDU)\n will contain a new Type-Length-Value (TLV) identifying the instance\n and the topology (or topologies) to which the PDU belongs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (I","scope_keywords":["6822","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 6822 This document describes a mechanism that allows a single router to\n share one or more circuits among multiple Intermediate System to\n Intermediate System (IS-IS) routing protocol instances.\n\n Multiple instances allow the isolation of resources associated with\n each instance. Routers will form instance-specific adjacencies.\n Each instance can support multiple topologies. Each topology has a\n unique Link State Database (LSDB). Each Protocol Data Unit (PDU)\n will contain a new Type-Length-Value (TLV) identifying the instance\n and the topology (or topologies) to which the PDU belongs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (I 6822 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6959","type":"specification","body":"IETF","designation":"RFC 6959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6959.txt","https://www.rfc-editor.org/rfc/rfc6959.pdf"],"folder":"IETF/RFC-6959","files":{"txt":{"path":"standards/IETF/RFC-6959/RFC-6959.txt","sha256":"7e3eb82c06daeea3554b3e50e6433b94ad301e4d7414f5076767254b7a8217cb"}},"tags":["nested-reference","unchanged"],"summary":"The Source Address Validation Improvement (SAVI) effort aims to\n complement ingress filtering with finer-grained, standardized IP\n source address validation. This document describes threats enabled\n by IP source address spoofing both in the global and finer-grained\n context, describes currently available solutions and challenges, and\n provides a starting point analysis for finer-grained (host\n granularity) anti-spoofing work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standa","scope_keywords":["6959","http","license","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null}],"search_text":"IETF RFC 6959 The Source Address Validation Improvement (SAVI) effort aims to\n complement ingress filtering with finer-grained, standardized IP\n source address validation. This document describes threats enabled\n by IP source address spoofing both in the global and finer-grained\n context, describes currently available solutions and challenges, and\n provides a starting point analysis for finer-grained (host\n granularity) anti-spoofing work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standa 6959 http license policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6991","type":"specification","body":"IETF","designation":"RFC 6991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6991.txt","https://www.rfc-editor.org/rfc/rfc6991.pdf"],"folder":"IETF/RFC-6991","files":{"txt":{"path":"standards/IETF/RFC-6991/RFC-6991.txt","sha256":"4c63e327ee753e1b63ce37d370a5a4ff41d735cf38ef0c32b0aabb18883a64dc"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces a collection of common data types to be used\n with the YANG data modeling language. This document obsoletes RFC\n 6021.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6991.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro","scope_keywords":["6991","http","key","license","management","path","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6991 This document introduces a collection of common data types to be used\n with the YANG data modeling language. This document obsoletes RFC\n 6021.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6991.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro 6991 http key license management path subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7043","type":"specification","body":"IETF","designation":"RFC 7043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7043.txt","https://www.rfc-editor.org/rfc/rfc7043.pdf"],"folder":"IETF/RFC-7043","files":{"txt":{"path":"standards/IETF/RFC-7043/RFC-7043.txt","sha256":"afca5d667bc2055e9329435eb29aa1b8a5c8d87377d10bed14d8a46d342928c7"}},"tags":["nested-reference","unchanged"],"summary":"48-bit Extended Unique Identifier (EUI-48) and 64-bit Extended Unique\n Identifier (EUI-64) are address formats specified by the IEEE for use\n in various layer-2 networks, e.g., Ethernet.\n\n This document describes two new DNS resource record types, EUI48 and\n EUI64, for encoding Ethernet addresses in the DNS.\n\n This document describes potentially severe privacy implications\n resulting from indiscriminate publication of link-layer addresses in\n the DNS. EUI-48 or EUI-64 addresses SHOULD NOT be published in the\n public DNS. This document specifies an interoperable encoding of\n these address types for use in private DNS namespaces, where the\n privacy concerns can be constrained and mitigated.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (","scope_keywords":["7043","http","key","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 7043 48-bit Extended Unique Identifier (EUI-48) and 64-bit Extended Unique\n Identifier (EUI-64) are address formats specified by the IEEE for use\n in various layer-2 networks, e.g., Ethernet.\n\n This document describes two new DNS resource record types, EUI48 and\n EUI64, for encoding Ethernet addresses in the DNS.\n\n This document describes potentially severe privacy implications\n resulting from indiscriminate publication of link-layer addresses in\n the DNS. EUI-48 or EUI-64 addresses SHOULD NOT be published in the\n public DNS. This document specifies an interoperable encoding of\n these address types for use in private DNS namespaces, where the\n privacy concerns can be constrained and mitigated.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n ( 7043 http key license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7136","type":"specification","body":"IETF","designation":"RFC 7136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7136.txt","https://www.rfc-editor.org/rfc/rfc7136.pdf"],"folder":"IETF/RFC-7136","files":{"txt":{"path":"standards/IETF/RFC-7136/RFC-7136.txt","sha256":"5edce73bc7b100fb38cea77551c4f16f0eeb4e428ad512c8c983eef7a32cc82f"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 addressing architecture includes a unicast interface\n identifier that is used in the creation of many IPv6 addresses.\n Interface identifiers are formed by a variety of methods. This\n document clarifies that the bits in an interface identifier have no\n meaning and that the entire identifier should be treated as an opaque\n value. In particular, RFC 4291 defines a method by which the\n Universal and Group bits of an IEEE link-layer address are mapped\n into an IPv6 unicast interface identifier. This document clarifies\n that those two bits are significant only in the process of deriving\n interface identifiers from an IEEE link-layer address, and it updates\n RFC 4291 accordingly.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n rece","scope_keywords":["7136","hash","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7136 The IPv6 addressing architecture includes a unicast interface\n identifier that is used in the creation of many IPv6 addresses.\n Interface identifiers are formed by a variety of methods. This\n document clarifies that the bits in an interface identifier have no\n meaning and that the entire identifier should be treated as an opaque\n value. In particular, RFC 4291 defines a method by which the\n Universal and Group bits of an IEEE link-layer address are mapped\n into an IPv6 unicast interface identifier. This document clarifies\n that those two bits are significant only in the process of deriving\n interface identifiers from an IEEE link-layer address, and it updates\n RFC 4291 accordingly.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n rece 7136 hash http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7155","type":"specification","body":"IETF","designation":"RFC 7155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7155.txt","https://www.rfc-editor.org/rfc/rfc7155.pdf"],"folder":"IETF/RFC-7155","files":{"txt":{"path":"standards/IETF/RFC-7155/RFC-7155.txt","sha256":"f100a5a47def22bda012369e8926f5d17c57b9a73a0fe4daeac16bb01b272cd5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Diameter protocol application used for\n Authentication, Authorization, and Accounting services in the Network\n Access Server (NAS) environment; it obsoletes RFC 4005. When\n combined with the Diameter Base protocol, Transport Profile, and\n Extensible Authentication Protocol specifications, this application\n specification satisfies typical network access services requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb","scope_keywords":["7155","algorithm","authentication","authorization","http","identification","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null}],"search_text":"IETF RFC 7155 This document describes the Diameter protocol application used for\n Authentication, Authorization, and Accounting services in the Network\n Access Server (NAS) environment; it obsoletes RFC 4005. When\n combined with the Diameter Base protocol, Transport Profile, and\n Extensible Authentication Protocol specifications, this application\n specification satisfies typical network access services requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb 7155 algorithm authentication authorization http identification license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7176","type":"specification","body":"IETF","designation":"RFC 7176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7176.txt","https://www.rfc-editor.org/rfc/rfc7176.pdf"],"folder":"IETF/RFC-7176","files":{"txt":{"path":"standards/IETF/RFC-7176/RFC-7176.txt","sha256":"6d5598aca7ab28ad8e5c62a6185c4f607c4b9a6b381cc0736a6cc437e5812557"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol provides optimal pair-wise data frame forwarding without\n configuration in multi-hop networks with arbitrary topology and link\n technology; it also provides support for multipathing of both unicast\n and multicast traffic. This document specifies the data formats and\n code points for the IS-IS extensions to support TRILL. These data\n formats and code points may also be used by technologies other than\n TRILL. This document obsoletes RFC 6326.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Sectio","scope_keywords":["7176","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7176 The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol provides optimal pair-wise data frame forwarding without\n configuration in multi-hop networks with arbitrary topology and link\n technology; it also provides support for multipathing of both unicast\n and multicast traffic. This document specifies the data formats and\n code points for the IS-IS extensions to support TRILL. These data\n formats and code points may also be used by technologies other than\n TRILL. This document obsoletes RFC 6326.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Sectio 7176 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7180","type":"specification","body":"IETF","designation":"RFC 7180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7180.txt","https://www.rfc-editor.org/rfc/rfc7180.pdf"],"folder":"IETF/RFC-7180","files":{"txt":{"path":"standards/IETF/RFC-7180/RFC-7180.txt","sha256":"6bcebac2b04edefd8e3671b54d8ae5070b2d338d3fb449994daf5e715caf783b"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol provides least-cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topology and link\n technology, safe forwarding even during periods of temporary loops,\n and support for multipathing of both unicast and multicast traffic.\n TRILL accomplishes this by using Intermediate System to Intermediate\n System (IS-IS) link-state routing and by encapsulating traffic using\n a header that includes a hop count. Since publication of the TRILL\n base protocol in July 2011, active development of TRILL has revealed\n errata in RFC 6325 and some cases that could use clarifications or\n updates.\n\n RFCs 6327 and 6439 provide clarifications and updates with respect to\n adjacency and Appointed Forwarders. This document provides other\n known clarifications, corrections, and updates to RFCs 6325, 6327,\n and","scope_keywords":["7180","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7180 The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol provides least-cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topology and link\n technology, safe forwarding even during periods of temporary loops,\n and support for multipathing of both unicast and multicast traffic.\n TRILL accomplishes this by using Intermediate System to Intermediate\n System (IS-IS) link-state routing and by encapsulating traffic using\n a header that includes a hop count. Since publication of the TRILL\n base protocol in July 2011, active development of TRILL has revealed\n errata in RFC 6325 and some cases that could use clarifications or\n updates.\n\n RFCs 6327 and 6439 provide clarifications and updates with respect to\n adjacency and Appointed Forwarders. This document provides other\n known clarifications, corrections, and updates to RFCs 6325, 6327,\n and 7180 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7228","type":"specification","body":"IETF","designation":"RFC 7228","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7228.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7228.txt","https://www.rfc-editor.org/rfc/rfc7228.pdf"],"folder":"IETF/RFC-7228","files":{"txt":{"path":"standards/IETF/RFC-7228/RFC-7228.txt","sha256":"486bfa37c3b92be7411bccc03ee81bcde0ed38bbdb54d10b7f98776e3669153e"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Protocol Suite is increasingly used on small devices\n with severe constraints on power, memory, and processing resources,\n creating constrained-node networks. This document provides a number\n of basic terms that have been useful in the standardization work for\n constrained-node networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback","scope_keywords":["7228","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7228 The Internet Protocol Suite is increasingly used on small devices\n with severe constraints on power, memory, and processing resources,\n creating constrained-node networks. This document provides a number\n of basic terms that have been useful in the standardization work for\n constrained-node networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback 7228 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7624","type":"specification","body":"IETF","designation":"RFC 7624","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7624.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7624.txt","https://www.rfc-editor.org/rfc/rfc7624.pdf"],"folder":"IETF/RFC-7624","files":{"txt":{"path":"standards/IETF/RFC-7624/RFC-7624.txt","sha256":"6ee1f5de76ddd3cf595cdf1746b3e2e4733429e34153860d8bea9fb950f867bd"}},"tags":["nested-reference","unchanged"],"summary":"Since the initial revelations of pervasive surveillance in 2013,\n several classes of attacks on Internet communications have been\n discovered. In this document, we develop a threat model that\n describes these attacks on Internet confidentiality. We assume an\n attacker that is interested in undetected, indiscriminate\n eavesdropping. The threat model is based on published, verified\n attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Inform","scope_keywords":["7624","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7624 Since the initial revelations of pervasive surveillance in 2013,\n several classes of attacks on Internet communications have been\n discovered. In this document, we develop a threat model that\n describes these attacks on Internet confidentiality. We assume an\n attacker that is interested in undetected, indiscriminate\n eavesdropping. The threat model is based on published, verified\n attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Inform 7624 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7637","type":"specification","body":"IETF","designation":"RFC 7637","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7637.txt","https://www.rfc-editor.org/rfc/rfc7637.pdf"],"folder":"IETF/RFC-7637","files":{"txt":{"path":"standards/IETF/RFC-7637/RFC-7637.txt","sha256":"d24b4b2c39fb5346d72cf6d8535df974a4b0e7d1df2667c948526fd20b31c9de"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of the Generic Routing\n Encapsulation (GRE) header for Network Virtualization (NVGRE) in\n multi-tenant data centers. Network Virtualization decouples virtual\n networks and addresses from physical network infrastructure,\n providing isolation and concurrency between multiple virtual networks\n on the same physical network infrastructure. This document also\n introduces a Network Virtualization framework to illustrate the use\n cases, but the focus is on specifying the data-plane aspect of NVGRE.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents ","scope_keywords":["7637","http","key","license","management","path","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 7637 This document describes the usage of the Generic Routing\n Encapsulation (GRE) header for Network Virtualization (NVGRE) in\n multi-tenant data centers. Network Virtualization decouples virtual\n networks and addresses from physical network infrastructure,\n providing isolation and concurrency between multiple virtual networks\n on the same physical network infrastructure. This document also\n introduces a Network Virtualization framework to illustrate the use\n cases, but the focus is on specifying the data-plane aspect of NVGRE.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents  7637 http key license management path pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7676","type":"specification","body":"IETF","designation":"RFC 7676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7676.txt","https://www.rfc-editor.org/rfc/rfc7676.pdf"],"folder":"IETF/RFC-7676","files":{"txt":{"path":"standards/IETF/RFC-7676/RFC-7676.txt","sha256":"29640b08a12ccb8ace0f78d4b096ab39e8d9eeb048fdbd617e2fb34bc3f5c15b"}},"tags":["nested-reference","unchanged"],"summary":"Generic Routing Encapsulation (GRE) can be used to carry any network-\n layer payload protocol over any network-layer delivery protocol.\n Currently, GRE procedures are specified for IPv4, used as either the\n payload or delivery protocol. However, GRE procedures are not\n specified for IPv6.\n\n This document specifies GRE procedures for IPv6, used as either the\n payload or delivery protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b","scope_keywords":["7676","delivery","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7676 Generic Routing Encapsulation (GRE) can be used to carry any network-\n layer payload protocol over any network-layer delivery protocol.\n Currently, GRE procedures are specified for IPv4, used as either the\n payload or delivery protocol. However, GRE procedures are not\n specified for IPv6.\n\n This document specifies GRE procedures for IPv6, used as either the\n payload or delivery protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b 7676 delivery http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7780","type":"specification","body":"IETF","designation":"RFC 7780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7780.txt","https://www.rfc-editor.org/rfc/rfc7780.pdf"],"folder":"IETF/RFC-7780","files":{"txt":{"path":"standards/IETF/RFC-7780/RFC-7780.txt","sha256":"eb157c0018c0abb0d98d2d67783915b878042aa75c05d1ae25aae84810dc0208"}},"tags":["nested-reference","unchanged"],"summary":"Since the publication of the TRILL (Transparent Interconnection of\n Lots of Links) base protocol in 2011, active development and\n deployment of TRILL have revealed errata in RFC 6325 and areas that\n could use clarifications or updates. RFC 7177, RFC 7357, and an\n intended replacement of RFC 6439 provide clarifications and updates\n with respect to adjacency, the TRILL ESADI (End Station Address\n Distribution Information) protocol, and Appointed Forwarders,\n respectively. This document provides other known clarifications,\n corrections, and updates. It obsoletes RFC 7180 (the previous \"TRILL\n clarifications, corrections, and updates\" RFC), and it updates RFCs\n 6325, 7177, and 7179.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive","scope_keywords":["7780","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7780 Since the publication of the TRILL (Transparent Interconnection of\n Lots of Links) base protocol in 2011, active development and\n deployment of TRILL have revealed errata in RFC 6325 and areas that\n could use clarifications or updates. RFC 7177, RFC 7357, and an\n intended replacement of RFC 6439 provide clarifications and updates\n with respect to adjacency, the TRILL ESADI (End Station Address\n Distribution Information) protocol, and Appointed Forwarders,\n respectively. This document provides other known clarifications,\n corrections, and updates. It obsoletes RFC 7180 (the previous \"TRILL\n clarifications, corrections, and updates\" RFC), and it updates RFCs\n 6325, 7177, and 7179.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive 7780 http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 7844","type":"specification","body":"IETF","designation":"RFC 7844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7844.txt","https://www.rfc-editor.org/rfc/rfc7844.pdf"],"folder":"IETF/RFC-7844","files":{"txt":{"path":"standards/IETF/RFC-7844/RFC-7844.txt","sha256":"359b456e9be5acaa618d654aa10f0d330696e8c2cf9a09ca6c143df7881fa3c8"}},"tags":["nested-reference","unchanged"],"summary":"Some DHCP options carry unique identifiers. These identifiers can\n enable device tracking even if the device administrator takes care of\n randomizing other potential identifications like link-layer addresses\n or IPv6 addresses. The anonymity profiles are designed for clients\n that wish to remain anonymous to the visited network. The profiles\n provide guidelines on the composition of DHCP or DHCPv6 messages,\n designed to minimize disclosure of identifying information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr","scope_keywords":["7844","authentication","http","identification","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null}],"search_text":"IETF RFC 7844 Some DHCP options carry unique identifiers. These identifiers can\n enable device tracking even if the device administrator takes care of\n randomizing other potential identifications like link-layer addresses\n or IPv6 addresses. The anonymity profiles are designed for clients\n that wish to remain anonymous to the visited network. The profiles\n provide guidelines on the composition of DHCP or DHCPv6 messages,\n designed to minimize disclosure of identifying information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr 7844 authentication http identification key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7961","type":"specification","body":"IETF","designation":"RFC 7961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7961.txt","https://www.rfc-editor.org/rfc/rfc7961.pdf"],"folder":"IETF/RFC-7961","files":{"txt":{"path":"standards/IETF/RFC-7961/RFC-7961.txt","sha256":"173bb0ecff28e9f1cd33ee4a9ffa4d1c464c008f1ed985a0575a8decc2b6f40b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a TRILL (Transparent Interconnection of Lots\n of Links) IS-IS application sub-TLV that enables the reporting by a\n TRILL switch of sets of addresses. Each set of addresses reports all\n of the addresses that designate the same interface (port) and also\n reports the TRILL switch by which that interface is reachable. For\n example, a 48-bit MAC (Media Access Control) address, IPv4 address,\n and IPv6 address can be reported as all corresponding to the same\n interface reachable by a particular TRILL switch. Such information\n could be used in some cases to synthesize responses to, or bypass the\n need for, the Address Resolution Protocol (ARP), the IPv6 Neighbor\n Discovery (ND) protocol, or the flooding of unknown MAC addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF).","scope_keywords":["7961","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 7961 This document specifies a TRILL (Transparent Interconnection of Lots\n of Links) IS-IS application sub-TLV that enables the reporting by a\n TRILL switch of sets of addresses. Each set of addresses reports all\n of the addresses that designate the same interface (port) and also\n reports the TRILL switch by which that interface is reachable. For\n example, a 48-bit MAC (Media Access Control) address, IPv4 address,\n and IPv6 address can be reported as all corresponding to the same\n interface reachable by a particular TRILL switch. Such information\n could be used in some cases to synthesize responses to, or bypass the\n need for, the Address Resolution Protocol (ARP), the IPv6 Neighbor\n Discovery (ND) protocol, or the flooding of unknown MAC addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). 7961 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8086","type":"specification","body":"IETF","designation":"RFC 8086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8086.txt","https://www.rfc-editor.org/rfc/rfc8086.pdf"],"folder":"IETF/RFC-8086","files":{"txt":{"path":"standards/IETF/RFC-8086/RFC-8086.txt","sha256":"84b1c4c47cf8ca824ce69066a29014fe87ce9aab65d381d4ba8b25d99fdd912e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method of encapsulating network protocol\n packets within GRE and UDP headers. This GRE-in-UDP encapsulation\n allows the UDP source port field to be used as an entropy field.\n This may be used for load-balancing of GRE traffic in transit\n networks using existing Equal-Cost Multipath (ECMP) mechanisms.\n There are two applicability scenarios for GRE-in-UDP with different\n requirements: (1) general Internet and (2) a traffic-managed\n controlled environment. The controlled environment has less\n restrictive requirements than the general Internet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further i","scope_keywords":["8086","hash","hashing","http","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 8086 This document specifies a method of encapsulating network protocol\n packets within GRE and UDP headers. This GRE-in-UDP encapsulation\n allows the UDP source port field to be used as an entropy field.\n This may be used for load-balancing of GRE traffic in transit\n networks using existing Equal-Cost Multipath (ECMP) mechanisms.\n There are two applicability scenarios for GRE-in-UDP with different\n requirements: (1) general Internet and (2) a traffic-managed\n controlled environment. The controlled environment has less\n restrictive requirements than the general Internet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further i 8086 hash hashing http license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8415","type":"specification","body":"IETF","designation":"RFC 8415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8415.txt","https://www.rfc-editor.org/rfc/rfc8415.pdf"],"folder":"IETF/RFC-8415","files":{"txt":{"path":"standards/IETF/RFC-8415/RFC-8415.txt","sha256":"3a3540c90ef2da48caa5cba627455025ef8cff6d1f988c6d0a83305485e4aa0a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6): an extensible mechanism for configuring nodes with\n network configuration parameters, IP addresses, and prefixes.\n Parameters can be provided statelessly, or in combination with\n stateful assignment of one or more IPv6 addresses and/or IPv6\n prefixes. DHCPv6 can operate either in place of or in addition to\n stateless address autoconfiguration (SLAAC).\n\n This document updates the text from RFC 3315 (the original DHCPv6\n specification) and incorporates prefix delegation (RFC 3633),\n stateless DHCPv6 (RFC 3736), an option to specify an upper bound for\n how long a client should wait before refreshing information (RFC\n 4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service\n is not available (RFC 7083), and relay agent handling of unknown\n messages (RFC 7283). In addition, this document clarifies ","scope_keywords":["8415","http","https","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8415 This document describes the Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6): an extensible mechanism for configuring nodes with\n network configuration parameters, IP addresses, and prefixes.\n Parameters can be provided statelessly, or in combination with\n stateful assignment of one or more IPv6 addresses and/or IPv6\n prefixes. DHCPv6 can operate either in place of or in addition to\n stateless address autoconfiguration (SLAAC).\n\n This document updates the text from RFC 3315 (the original DHCPv6\n specification) and incorporates prefix delegation (RFC 3633),\n stateless DHCPv6 (RFC 3736), an option to specify an upper bound for\n how long a client should wait before refreshing information (RFC\n 4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service\n is not available (RFC 7083), and relay agent handling of unknown\n messages (RFC 7283). In addition, this document clarifies  8415 http https license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8520","type":"specification","body":"IETF","designation":"RFC 8520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8520.txt","https://www.rfc-editor.org/rfc/rfc8520.pdf"],"folder":"IETF/RFC-8520","files":{"txt":{"path":"standards/IETF/RFC-8520/RFC-8520.txt","sha256":"71b163203172fc40168f047fb9a7548a4140d5759eb9f508f575ff0da0797802"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies a component-based architecture for Manufacturer\n Usage Descriptions (MUDs). The goal of MUD is to provide a means for\n end devices to signal to the network what sort of access and network\n functionality they require to properly function. The initial focus\n is on access control. Later work can delve into other aspects.\n\n This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a\n Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate\n extension, and a means to sign and verify the descriptions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standar","scope_keywords":["8520","certificate","http","https","license","pki","policies","policy","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8520 This memo specifies a component-based architecture for Manufacturer\n Usage Descriptions (MUDs). The goal of MUD is to provide a means for\n end devices to signal to the network what sort of access and network\n functionality they require to properly function. The initial focus\n is on access control. Later work can delve into other aspects.\n\n This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a\n Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate\n extension, and a means to sign and verify the descriptions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standar 8520 certificate http https license pki policies policy signature subject trust nested-reference unchanged"},{"id":"IETF RFC 8926","type":"specification","body":"IETF","designation":"RFC 8926","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8926.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8926.txt","https://www.rfc-editor.org/rfc/rfc8926.pdf"],"folder":"IETF/RFC-8926","files":{"pdf":{"path":"standards/IETF/RFC-8926/RFC-8926.pdf","sha256":"d2f2bca0b8a4d11e73ba939b41102d70fb709506dee1c9ada85ce98029deaf7c"},"txt":{"path":"standards/IETF/RFC-8926/RFC-8926.txt","sha256":"23a9fcd3c23b93a103c0228128b2dce808323a7a9d15ea9cbb395fdb9f67e37d"}},"tags":["nested-reference","unchanged"],"summary":"Network virtualization involves the cooperation of devices with a\n wide variety of capabilities such as software and hardware tunnel\n endpoints, transit fabrics, and centralized control clusters. As a\n result of their role in tying together different elements of the\n system, the requirements on tunnels are influenced by all of these\n components. Therefore, flexibility is the most important aspect of a\n tunneling protocol if it is to keep pace with the evolution of\n technology. This document describes Geneve, an encapsulation\n protocol designed to recognize and accommodate these changing\n capabilities and needs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Interne","scope_keywords":["8926","authentication","http","https","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8926 Network virtualization involves the cooperation of devices with a\n wide variety of capabilities such as software and hardware tunnel\n endpoints, transit fabrics, and centralized control clusters. As a\n result of their role in tying together different elements of the\n system, the requirements on tunnels are influenced by all of these\n components. Therefore, flexibility is the most important aspect of a\n tunneling protocol if it is to keep pace with the evolution of\n technology. This document describes Geneve, an encapsulation\n protocol designed to recognize and accommodate these changing\n capabilities and needs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Interne 8926 authentication http https key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 8947","type":"specification","body":"IETF","designation":"RFC 8947","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8947.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8947.txt","https://www.rfc-editor.org/rfc/rfc8947.pdf"],"folder":"IETF/RFC-8947","files":{"pdf":{"path":"standards/IETF/RFC-8947/RFC-8947.pdf","sha256":"a77134c11628a722bfbac2be2a0bf26cee9a47f79e9ab7f5f126db99e75a3086"},"txt":{"path":"standards/IETF/RFC-8947/RFC-8947.txt","sha256":"9251248c9c242846c9237a766d8665ab3895f1963ae126bdb2d30b21d1742dc5"}},"tags":["nested-reference","unchanged"],"summary":"In certain environments, e.g., large-scale virtualization\n deployments, new devices are created in an automated manner. Such\n devices may have their link-layer addresses assigned in an automated\n fashion. With sufficient scale, the likelihood of a collision using\n random assignment without duplication detection is not acceptable.\n Therefore, an allocation mechanism is required. This document\n proposes an extension to DHCPv6 that allows a scalable approach to\n link-layer address assignments where preassigned link-layer address\n assignments (such as by a manufacturer) are not possible or are\n unnecessary.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine","scope_keywords":["8947","http","https","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 8947 In certain environments, e.g., large-scale virtualization\n deployments, new devices are created in an automated manner. Such\n devices may have their link-layer addresses assigned in an automated\n fashion. With sufficient scale, the likelihood of a collision using\n random assignment without duplication detection is not acceptable.\n Therefore, an allocation mechanism is required. This document\n proposes an extension to DHCPv6 that allows a scalable approach to\n link-layer address assignments where preassigned link-layer address\n assignments (such as by a manufacturer) are not possible or are\n unnecessary.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine 8947 http https key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 900","type":"specification","body":"IETF","designation":"RFC 900","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc900.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc900.txt","https://www.rfc-editor.org/rfc/rfc900.pdf"],"folder":"IETF/RFC-900","files":{"txt":{"path":"standards/IETF/RFC-900/RFC-900.txt","sha256":"2f2f7c2bb2728d83291365bda894a44b0c8a58594421eeaf6b859d1239a1da9e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 900 J. Postel\n ISI\nObsoletes RFCs: 870, 820, June 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to receive a number assignment.\n\n Joyce Reynolds\n USC ","scope_keywords":["900","identification","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null}],"search_text":"IETF RFC 900 Network Working Group J. Reynolds\nRequest for Comments: 900 J. Postel\n ISI\nObsoletes RFCs: 870, 820, June 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to receive a number assignment.\n\n Joyce Reynolds\n USC  900 identification risk nested-reference unchanged"},{"id":"IETF RFC 923","type":"specification","body":"IETF","designation":"RFC 923","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc923.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc923.txt","https://www.rfc-editor.org/rfc/rfc923.pdf"],"folder":"IETF/RFC-923","files":{"txt":{"path":"standards/IETF/RFC-923/RFC-923.txt","sha256":"46d8d4240de9cdf2b74bfb797216903b150b3fad8733b653c64d330d4403810f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 923 J. Postel\n ISI\nObsoletes RFCs: 900, 870, 820, October 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to re","scope_keywords":["923","identification","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 937","folder":"IETF/RFC-937","source":"IETF/RFC-937/RFC-937.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null}],"search_text":"IETF RFC 923 Network Working Group J. Reynolds\nRequest for Comments: 923 J. Postel\n ISI\nObsoletes RFCs: 900, 870, 820, October 1984\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to re 923 identification risk nested-reference unchanged"},{"id":"IETF RFC 943","type":"specification","body":"IETF","designation":"RFC 943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc943.txt","https://www.rfc-editor.org/rfc/rfc943.pdf"],"folder":"IETF/RFC-943","files":{"txt":{"path":"standards/IETF/RFC-943/RFC-943.txt","sha256":"cc07ca5aa98670c0689f177192eaa708bbddff9b83d05ffe434ac9f442b7270b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 943 J. Postel\n ISI\nObsoletes RFCs: 923, 900, 870, April 1985\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to","scope_keywords":["943","identification","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 943 Network Working Group J. Reynolds\nRequest for Comments: 943 J. Postel\n ISI\nObsoletes RFCs: 923, 900, 870, April 1985\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact Joyce to 943 identification risk nested-reference unchanged"},{"id":"IETF RFC 948","type":"specification","body":"IETF","designation":"RFC 948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc948.txt","https://www.rfc-editor.org/rfc/rfc948.pdf"],"folder":"IETF/RFC-948","files":{"txt":{"path":"standards/IETF/RFC-948/RFC-948.txt","sha256":"e77d0cf4ff489cd01b16e4c900b99bb6b824dc67bd943e0b280f829450344347"}},"tags":["nested-reference","unchanged"],"summary":"---------\n\f\n\n , 11-Jun-85 21:31-PDT JBP ;;;;\n\nWinston [Page 0]\n\f\n\nNetwork Working Group Ira Winston\nRequest for Comments: 948 University of Pennsylvania\n June 1985\n\n TWO METHODS FOR THE TRANSMISSION OF IP DATAGRAMS OVER\n IEEE 802.3 NETWORKS\n\nStatus of this Memo\n\n This memo describes two methods of encapsulating Internet\n Protocol (IP) [1] datagrams on an IEEE 802.3 network [2]. This RFC\n suggests a proposed protocol for the ARPA-Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n The IEEE 802 project has defined a family of standards for Local Area\n Networks (LANs) that deals with the Physical and Data Link Layers as\n defined by the ISO Open System Interconnection Reference Model\n (ISO/OSI). Several Physical Layer standards (802.3, 802.4, and\n 802.5) [2, 3, 4] and one Data Link Layer Standard (802.2) [5] ","scope_keywords":["948"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 948 ---------\n\f\n\n , 11-Jun-85 21:31-PDT JBP ;;;;\n\nWinston [Page 0]\n\f\n\nNetwork Working Group Ira Winston\nRequest for Comments: 948 University of Pennsylvania\n June 1985\n\n TWO METHODS FOR THE TRANSMISSION OF IP DATAGRAMS OVER\n IEEE 802.3 NETWORKS\n\nStatus of this Memo\n\n This memo describes two methods of encapsulating Internet\n Protocol (IP) [1] datagrams on an IEEE 802.3 network [2]. This RFC\n suggests a proposed protocol for the ARPA-Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n The IEEE 802 project has defined a family of standards for Local Area\n Networks (LANs) that deals with the Physical and Data Link Layers as\n defined by the ISO Open System Interconnection Reference Model\n (ISO/OSI). Several Physical Layer standards (802.3, 802.4, and\n 802.5) [2, 3, 4] and one Data Link Layer Standard (802.2) [5]  948 nested-reference unchanged"},{"id":"IETF RFC 960","type":"specification","body":"IETF","designation":"RFC 960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc960.txt","https://www.rfc-editor.org/rfc/rfc960.pdf"],"folder":"IETF/RFC-960","files":{"txt":{"path":"standards/IETF/RFC-960/RFC-960.txt","sha256":"2513cea029c55044dd3e3e603213f3dce0d6dcd96dbcbdf05ec11bd6ce4f5d61"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 960 J. Postel\n ISI\nObsoletes RFCs: 943, 923, 900, 870, December 1985\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact ","scope_keywords":["960","identification","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 960 Network Working Group J. Reynolds\nRequest for Comments: 960 J. Postel\n ISI\nObsoletes RFCs: 943, 923, 900, 870, December 1985\n820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the numbers used in\n protocols in the ARPA-Internet community. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned values from several series of numbers used in\n network protocol implementations. This RFC will be updated\n periodically, and in any case current information can be obtained\n from Joyce Reynolds. The assignment of numbers is also handled by\n Joyce. If you are developing a protocol or application that will\n require the use of a link, socket, port, protocol, network number,\n etc., please contact  960 identification risk nested-reference unchanged"},{"id":"IETF RFC 985","type":"specification","body":"IETF","designation":"RFC 985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc985.txt","https://www.rfc-editor.org/rfc/rfc985.pdf"],"folder":"IETF/RFC-985","files":{"txt":{"path":"standards/IETF/RFC-985/RFC-985.txt","sha256":"abff272676535168f3d1c044252c38192ba4ebffabaf9ba69b93871bcc24a646"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Network Technical Advisory Group\nRequest for Comments: 985 NSF\n May 1986\n\n Requirements for Internet Gateways -- Draft\n\nStatus of this Memo\n\n This RFC summarizes the requirements for gateways to be used on\n networks supporting the DARPA Internet protocols. While it applies\n specifically to National Science Foundation research programs, the\n requirements are stated in a general context and are believed\n applicable throughout the Internet community. This document was\n prepared by the Gateway Requirements Subcommittee of the NSF Network\n Technical Advisory Group in cooperation with the Internet Activities\n Board, Internet Architecture Task Force and Internet Engineering Task\n Force. It requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n The purpose of this document is to present guidance for vendors\n offering products that m","scope_keywords":["985","delivery","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null}],"search_text":"IETF RFC 985 Network Working Group Network Technical Advisory Group\nRequest for Comments: 985 NSF\n May 1986\n\n Requirements for Internet Gateways -- Draft\n\nStatus of this Memo\n\n This RFC summarizes the requirements for gateways to be used on\n networks supporting the DARPA Internet protocols. While it applies\n specifically to National Science Foundation research programs, the\n requirements are stated in a general context and are believed\n applicable throughout the Internet community. This document was\n prepared by the Gateway Requirements Subcommittee of the NSF Network\n Technical Advisory Group in cooperation with the Internet Activities\n Board, Internet Architecture Task Force and Internet Engineering Task\n Force. It requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n The purpose of this document is to present guidance for vendors\n offering products that m 985 delivery policy registered nested-reference unchanged"},{"id":"IETF RFC 991","type":"specification","body":"IETF","designation":"RFC 991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc991.txt","https://www.rfc-editor.org/rfc/rfc991.pdf"],"folder":"IETF/RFC-991","files":{"txt":{"path":"standards/IETF/RFC-991/RFC-991.txt","sha256":"78d556df4b4dac4326fe0f57145fe32873be63f0fa6d8b279dd44dcf8925a747"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 991 J. Postel\n ISI\nObsoletes: RFCs 961, 943, 924, 901, 880, 840 November 1986\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those specified in the\n \"DDN Protocol Handbook\" (DPH), dated December 1985 (this is a three\n volume set with a total thickness of about 5 inches).\n\n Older collections that include many of these specifications are the\n \"Internet Protocol Transition Workbook\" (IPTW), dated March 1982; the\n \"Internet Mail Protocols\", dated November 1982; and the \"Internet\n Telnet Protoc","scope_keywords":["991","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 991 Network Working Group J. Reynolds\nRequest for Comments: 991 J. Postel\n ISI\nObsoletes: RFCs 961, 943, 924, 901, 880, 840 November 1986\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those specified in the\n \"DDN Protocol Handbook\" (DPH), dated December 1985 (this is a three\n volume set with a total thickness of about 5 inches).\n\n Older collections that include many of these specifications are the\n \"Internet Protocol Transition Workbook\" (IPTW), dated March 1982; the\n \"Internet Mail Protocols\", dated November 1982; and the \"Internet\n Telnet Protoc 991 algorithm algorithms nested-reference unchanged"},{"id":"IEEE IEEE 802-","type":"specification","body":"IEEE","designation":"IEEE 802-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802-.html","download_urls":["https://standards.ieee.org/standard/802-.html"],"folder":"IEEE/IEEE-802-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null}],"search_text":"IEEE IEEE 802- nested-reference unavailable"},{"id":"IETF RFC 3033","type":"specification","body":"IETF","designation":"RFC 3033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3033.txt","https://www.rfc-editor.org/rfc/rfc3033.pdf"],"folder":"IETF/RFC-3033","files":{"txt":{"path":"standards/IETF/RFC-3033/RFC-3033.txt","sha256":"841f6fa3ab2005e35a88d1d0cb74f5a184de994c44ae521043ed254367456a03"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to specify the assignment of the\n information field and protocol identifier in the Q.2941 Generic\n Identifier and Q.2957 User-to-user Signaling for the Internet\n protocol.\n\n The assignment, that is specified in section 4 of this document, is\n designed for advanced B-ISDN signaling support of the Internet\n protocol, especially the B-ISDN signaling support for the connection\n that corresponds to the session in the Internet protocol which is\n clarified in section 2. This specification provides an indispensable\n framework for the implementation of long-lived session and QoS-\n sensitive session transfers over ATM.\n\n1. Purpose of Document\n\n The purpose of this document is to specify the assignment of the\n information field and protocol identifier in the Q.2941 Generic\n Identifier and Q.2957 User-to-user Signaling for the Internet\n protocol.\n\n The assignment, tha","scope_keywords":["3033","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3038","folder":"IETF/RFC-3038","source":"IETF/RFC-3038/RFC-3038.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 3033 The purpose of this document is to specify the assignment of the\n information field and protocol identifier in the Q.2941 Generic\n Identifier and Q.2957 User-to-user Signaling for the Internet\n protocol.\n\n The assignment, that is specified in section 4 of this document, is\n designed for advanced B-ISDN signaling support of the Internet\n protocol, especially the B-ISDN signaling support for the connection\n that corresponds to the session in the Internet protocol which is\n clarified in section 2. This specification provides an indispensable\n framework for the implementation of long-lived session and QoS-\n sensitive session transfers over ATM.\n\n1. Purpose of Document\n\n The purpose of this document is to specify the assignment of the\n information field and protocol identifier in the Q.2941 Generic\n Identifier and Q.2957 User-to-user Signaling for the Internet\n protocol.\n\n The assignment, tha 3033 management nested-reference unchanged"},{"id":"IETF RFC 4094","type":"specification","body":"IETF","designation":"RFC 4094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4094.txt","https://www.rfc-editor.org/rfc/rfc4094.pdf"],"folder":"IETF/RFC-4094","files":{"txt":{"path":"standards/IETF/RFC-4094/RFC-4094.txt","sha256":"3ed58c7157e47968b50e0a192afa23caf9a2cb275ce8ae94ec873c6873e478ef"}},"tags":["nested-reference","unchanged"],"summary":"This document reviews some of the existing Quality of Service (QoS)\n signaling protocols for an IP network. The goal here is to learn\n from them and to avoid common misconceptions. Further, we need to\n avoid mistakes during the design and implementation of any new\n protocol in this area.","scope_keywords":["4094","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 4094 This document reviews some of the existing Quality of Service (QoS)\n signaling protocols for an IP network. The goal here is to learn\n from them and to avoid common misconceptions. Further, we need to\n avoid mistakes during the design and implementation of any new\n protocol in this area. 4094 policy nested-reference unchanged"},{"id":"IEEE IEEE 802-1990","type":"specification","body":"IEEE","designation":"IEEE 802-1990","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802-1990.html","download_urls":["https://standards.ieee.org/standard/802-1990.html"],"folder":"IEEE/IEEE-802-1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2685","folder":"IETF/RFC-2685","source":"IETF/RFC-2685/RFC-2685.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null}],"search_text":"IEEE IEEE 802-1990 nested-reference unavailable"},{"id":"IETF RFC 2685","type":"specification","body":"IETF","designation":"RFC 2685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2685.txt","https://www.rfc-editor.org/rfc/rfc2685.pdf"],"folder":"IETF/RFC-2685","files":{"txt":{"path":"standards/IETF/RFC-2685/RFC-2685.txt","sha256":"372892c45ac5700daec06e96a2d60972a412c304145bf71daab440e9c91cdb76"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Fox\nRequest for Comments: 2685 Lucent Technologies\nCategory: Standards Track B. Gleeson\n Nortel Networks\n September 1999\n\n Virtual Private Networks Identifier\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n Virtual Private IP networks may span multiple Autonomous Systems or\n Service Providers. There is a requirement for the use of a globally\n unique VPN identifier in order to be able to refer to a particular\n VPN (see section 6.1.1 of [1]). This document propo","scope_keywords":["2685","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null}],"search_text":"IETF RFC 2685 Network Working Group B. Fox\nRequest for Comments: 2685 Lucent Technologies\nCategory: Standards Track B. Gleeson\n Nortel Networks\n September 1999\n\n Virtual Private Networks Identifier\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n Virtual Private IP networks may span multiple Autonomous Systems or\n Service Providers. There is a requirement for the use of a globally\n unique VPN identifier in order to be able to refer to a particular\n VPN (see section 6.1.1 of [1]). This document propo 2685 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 4171","type":"specification","body":"IETF","designation":"RFC 4171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4171.txt","https://www.rfc-editor.org/rfc/rfc4171.pdf"],"folder":"IETF/RFC-4171","files":{"txt":{"path":"standards/IETF/RFC-4171/RFC-4171.txt","sha256":"2a85b2434854b5276a25779980bc58bee56611f0eb7510b354f08d5be2b87e21"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Internet Storage Name Service (iSNS)\n protocol, used for interaction between iSNS servers and iSNS clients,\n which facilitates automated discovery, management, and configuration\n of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP\n network. iSNS provides intelligent storage discovery and management\n services comparable to those found in Fibre Channel networks,\n allowing a commodity IP network to function in a capacity similar to\n that of a storage area network. iSNS facilitates a seamless\n integration of IP and Fibre Channel networks due to its ability to\n emulate Fibre Channel fabric services and to manage both iSCSI and\n Fibre Channel devices. iSNS thereby provides value in any storage\n network comprised of iSCSI devices, Fibre Channel devices (using iFCP\n gateways), or any combination thereof.\n\nTseng, et al. Standards Track [Page 1]\n\f\nRFC 4","scope_keywords":["4171","attribute","attributes","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 4171 This document specifies the Internet Storage Name Service (iSNS)\n protocol, used for interaction between iSNS servers and iSNS clients,\n which facilitates automated discovery, management, and configuration\n of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP\n network. iSNS provides intelligent storage discovery and management\n services comparable to those found in Fibre Channel networks,\n allowing a commodity IP network to function in a capacity similar to\n that of a storage area network. iSNS facilitates a seamless\n integration of IP and Fibre Channel networks due to its ability to\n emulate Fibre Channel fabric services and to manage both iSCSI and\n Fibre Channel devices. iSNS thereby provides value in any storage\n network comprised of iSCSI devices, Fibre Channel devices (using iFCP\n gateways), or any combination thereof.\n\nTseng, et al. Standards Track [Page 1]\n\f\nRFC 4 4171 attribute attributes authentication key management nested-reference unchanged"},{"id":"IEEE IEEE 802-2001","type":"specification","body":"IEEE","designation":"IEEE 802-2001","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802-2001.html","download_urls":["https://standards.ieee.org/standard/802-2001.html"],"folder":"IEEE/IEEE-802-2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IEEE IEEE 802-2001 nested-reference unavailable"},{"id":"IETF RFC 6994","type":"specification","body":"IETF","designation":"RFC 6994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6994.txt","https://www.rfc-editor.org/rfc/rfc6994.pdf"],"folder":"IETF/RFC-6994","files":{"txt":{"path":"standards/IETF/RFC-6994/RFC-6994.txt","sha256":"6bb89855b31381026e6049423be8dd0f3457f0b6ac381cefa129159d9df03731"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the experimental TCP option codepoints\n can concurrently support multiple TCP extensions, even within the\n same connection, using a new IANA TCP experiment identifier. This\n approach is robust to experiments that are not registered and to\n those that do not use this sharing mechanism. It is recommended for\n all new TCP options that use these codepoints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai","scope_keywords":["6994","authentication","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 6994 This document describes how the experimental TCP option codepoints\n can concurrently support multiple TCP extensions, even within the\n same connection, using a new IANA TCP experiment identifier. This\n approach is robust to experiments that are not registered and to\n those that do not use this sharing mechanism. It is recommended for\n all new TCP options that use these codepoints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai 6994 authentication http key license registered subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802-2014","type":"specification","body":"IEEE","designation":"IEEE 802-2014","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802-2014.html","download_urls":["https://standards.ieee.org/standard/802-2014.html"],"folder":"IEEE/IEEE-802-2014","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IEEE IEEE 802-2014 nested-reference unavailable"},{"id":"IEEE IEEE 802-2014.","type":"specification","body":"IEEE","designation":"IEEE 802-2014.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802-2014..html","download_urls":["https://standards.ieee.org/standard/802-2014..html"],"folder":"IEEE/IEEE-802-2014.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IEEE IEEE 802-2014. nested-reference unavailable"},{"id":"IEEE IEEE 802.","type":"specification","body":"IEEE","designation":"IEEE 802.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802..html","download_urls":["https://standards.ieee.org/standard/802..html"],"folder":"IEEE/IEEE-802.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0970","folder":"IETF/RFC-0970","source":"IETF/RFC-0970/RFC-0970.txt","version":null},{"body":"IETF","designation":"RFC 1132","folder":"IETF/RFC-1132","source":"IETF/RFC-1132/RFC-1132.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1962","folder":"IETF/RFC-1962","source":"IETF/RFC-1962/RFC-1962.txt","version":null},{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 2723","folder":"IETF/RFC-2723","source":"IETF/RFC-2723/RFC-2723.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 970","folder":"IETF/RFC-970","source":"IETF/RFC-970/RFC-970.txt","version":null}],"search_text":"IEEE IEEE 802. nested-reference unavailable"},{"id":"IETF RFC 0970","type":"specification","body":"IETF","designation":"RFC 0970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0970.txt","https://www.rfc-editor.org/rfc/rfc0970.pdf"],"folder":"IETF/RFC-0970","files":{"txt":{"path":"standards/IETF/RFC-0970/RFC-0970.txt","sha256":"ebdc3c0c9199ce49c8f1c2856563e1e4097a3d8a4e6d87de4260b56740cc9c97"}},"tags":["nested-reference","unchanged"],"summary":"Most prior work on congestion in datagram systems focuses on buffer\n management. We find it illuminating to consider the case of a packet\n switch with infinite storage. Such a packet switch can never run out\n of buffers. It can, however, still become congested. The meaning of\n congestion in an infinite-storage system is explored. We demonstrate\n the unexpected result that a datagram network with infinite storage,\n first-in-first-out queuing, at least two packet switches, and a\n finite packet lifetime will, under overload, drop all packets. By\n attacking the problem of congestion for the infinite-storage case, we\n discover new solutions applicable to switches with finite storage.","scope_keywords":["0970","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null}],"search_text":"IETF RFC 0970 Most prior work on congestion in datagram systems focuses on buffer\n management. We find it illuminating to consider the case of a packet\n switch with infinite storage. Such a packet switch can never run out\n of buffers. It can, however, still become congested. The meaning of\n congestion in an infinite-storage system is explored. We demonstrate\n the unexpected result that a datagram network with infinite storage,\n first-in-first-out queuing, at least two packet switches, and a\n finite packet lifetime will, under overload, drop all packets. By\n attacking the problem of congestion for the infinite-storage case, we\n discover new solutions applicable to switches with finite storage. 0970 management nested-reference unchanged"},{"id":"IETF RFC 1707","type":"specification","body":"IETF","designation":"RFC 1707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1707.txt","https://www.rfc-editor.org/rfc/rfc1707.pdf"],"folder":"IETF/RFC-1707","files":{"txt":{"path":"standards/IETF/RFC-1707/RFC-1707.txt","sha256":"5ba8421eb97bb1bf573e900c8a998331917999e49e82b00d7e2ddd7aba592be5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group: M. McGovern\nRequest for Comments: 1707 Sunspot Graphics\nCategory: Informational R. Ullmann\n Lotus Development Corporation\n October 1994\n\n CATNIP: Common Architecture for the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550 Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n This paper describes a common architecture for the network layer\n protocol. The Common Architecture for Next Generation Internet\n Protocol (CATNIP) provides a compressed form of the existing network\n layer protocols. Ea","scope_keywords":["1707","algorithm","identification","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 1707 Network Working Group: M. McGovern\nRequest for Comments: 1707 Sunspot Graphics\nCategory: Informational R. Ullmann\n Lotus Development Corporation\n October 1994\n\n CATNIP: Common Architecture for the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550 Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n This paper describes a common architecture for the network layer\n protocol. The Common Architecture for Next Generation Internet\n Protocol (CATNIP) provides a compressed form of the existing network\n layer protocols. Ea 1707 algorithm identification path pid nested-reference unchanged"},{"id":"IETF RFC 1962","type":"specification","body":"IETF","designation":"RFC 1962","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1962.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1962.txt","https://www.rfc-editor.org/rfc/rfc1962.pdf"],"folder":"IETF/RFC-1962","files":{"txt":{"path":"standards/IETF/RFC-1962/RFC-1962.txt","sha256":"513b4bc07b95fb1e47bc5717a9ba7101ea2747c8f553edb8b698c1238ab1d778"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol.\n\n This document defines a method for negotiating data compression over\n PPP links.","scope_keywords":["1962","algorithm","algorithms","authentication","hash"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1967","folder":"IETF/RFC-1967","source":"IETF/RFC-1967/RFC-1967.txt","version":null},{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 1974","folder":"IETF/RFC-1974","source":"IETF/RFC-1974/RFC-1974.txt","version":null},{"body":"IETF","designation":"RFC 1977","folder":"IETF/RFC-1977","source":"IETF/RFC-1977/RFC-1977.txt","version":null},{"body":"IETF","designation":"RFC 1979","folder":"IETF/RFC-1979","source":"IETF/RFC-1979/RFC-1979.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 1993","folder":"IETF/RFC-1993","source":"IETF/RFC-1993/RFC-1993.txt","version":null},{"body":"IETF","designation":"RFC 2118","folder":"IETF/RFC-2118","source":"IETF/RFC-2118/RFC-2118.txt","version":null},{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null}],"search_text":"IETF RFC 1962 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol.\n\n This document defines a method for negotiating data compression over\n PPP links. 1962 algorithm algorithms authentication hash nested-reference unchanged"},{"id":"IETF RFC 1968","type":"specification","body":"IETF","designation":"RFC 1968","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1968.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1968.txt","https://www.rfc-editor.org/rfc/rfc1968.pdf"],"folder":"IETF/RFC-1968","files":{"txt":{"path":"standards/IETF/RFC-1968/RFC-1968.txt","sha256":"93c3d471e2ca9cf7e0966444e08abfdb5b9a06bcc7886cf6310e7b1e0aac8a5c"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol.\n\n This document defines a method for negotiating data encryption over\n PPP links.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o MUST -- the item is an absolute requirement of the specification.\n MUST is only used where it is actually required for interopera-\n tion, not to try to impose a particular method on implementors\n where not required for interoperability.\n\n o SHOULD -- the item should be followed for all but exceptional cir-\n cumstances.\n\n o MAY or optional -- the item is truly optional and may be followed\n or ignored according to the needs of the implementor.\n\n The words \"should\" and \"may\" are also used, in lower case, in\n their","scope_keywords":["1968","algorithm","algorithms","authentication","encryption","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1969","folder":"IETF/RFC-1969","source":"IETF/RFC-1969/RFC-1969.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 2420","folder":"IETF/RFC-2420","source":"IETF/RFC-2420/RFC-2420.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null}],"search_text":"IETF RFC 1968 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol.\n\n This document defines a method for negotiating data encryption over\n PPP links.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o MUST -- the item is an absolute requirement of the specification.\n MUST is only used where it is actually required for interopera-\n tion, not to try to impose a particular method on implementors\n where not required for interoperability.\n\n o SHOULD -- the item should be followed for all but exceptional cir-\n cumstances.\n\n o MAY or optional -- the item is truly optional and may be followed\n or ignored according to the needs of the implementor.\n\n The words \"should\" and \"may\" are also used, in lower case, in\n their 1968 algorithm algorithms authentication encryption pid nested-reference unchanged"},{"id":"IETF RFC 2723","type":"specification","body":"IETF","designation":"RFC 2723","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2723.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2723.txt","https://www.rfc-editor.org/rfc/rfc2723.pdf"],"folder":"IETF/RFC-2723","files":{"txt":{"path":"standards/IETF/RFC-2723/RFC-2723.txt","sha256":"62d1e1d4e2b468e5bd56f091d63f835c68023e3b1a7d0311920b9f8d534228f9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a language for specifying rulesets, i.e.\n configuration files which may be loaded into a traffic flow meter so\n as to specify which traffic flows are measured by the meter, and the\n information it will store for each flow.","scope_keywords":["2723","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null}],"search_text":"IETF RFC 2723 This document describes a language for specifying rulesets, i.e.\n configuration files which may be loaded into a traffic flow meter so\n as to specify which traffic flows are measured by the meter, and the\n information it will store for each flow. 2723 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 3621","type":"specification","body":"IETF","designation":"RFC 3621","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3621.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3621.txt","https://www.rfc-editor.org/rfc/rfc3621.pdf"],"folder":"IETF/RFC-3621","files":{"txt":{"path":"standards/IETF/RFC-3621/RFC-3621.txt","sha256":"ed0afcda8d0d91561a2fa93c294a75cb85b9fe65f90c091f8789a53f14a4df29"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This document proposes an extension to the Ethernet-like Interfaces\n MIB with a set of objects for managing Power Sourcing Equipment\n (PSE).","scope_keywords":["3621","http","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null}],"search_text":"IETF RFC 3621 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This document proposes an extension to the Ethernet-like Interfaces\n MIB with a set of objects for managing Power Sourcing Equipment\n (PSE). 3621 http key management subject nested-reference unchanged"},{"id":"IETF RFC 5416","type":"specification","body":"IETF","designation":"RFC 5416","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5416.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5416.txt","https://www.rfc-editor.org/rfc/rfc5416.pdf"],"folder":"IETF/RFC-5416","files":{"txt":{"path":"standards/IETF/RFC-5416/RFC-5416.txt","sha256":"ef326f22d2302b43547dcad37fbc545b075dcae7941372b0569fd84e0f5a4af2"}},"tags":["nested-reference","unchanged"],"summary":"Wireless LAN product architectures have evolved from single\n autonomous access points to systems consisting of a centralized\n Access Controller (AC) and Wireless Termination Points (WTPs). The\n general goal of centralized control architectures is to move access\n control, including user authentication and authorization, mobility\n management, and radio management from the single access point to a\n centralized controller.\n\n This specification defines the Control And Provisioning of Wireless\n Access Points (CAPWAP) Protocol Binding Specification for use with\n the IEEE 802.11 Wireless Local Area Network protocol.","scope_keywords":["5416","authentication","authorization","http","key","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5416 Wireless LAN product architectures have evolved from single\n autonomous access points to systems consisting of a centralized\n Access Controller (AC) and Wireless Termination Points (WTPs). The\n general goal of centralized control architectures is to move access\n control, including user authentication and authorization, mobility\n management, and radio management from the single access point to a\n centralized controller.\n\n This specification defines the Control And Provisioning of Wireless\n Access Points (CAPWAP) Protocol Binding Specification for use with\n the IEEE 802.11 Wireless Local Area Network protocol. 5416 authentication authorization http key license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 970","type":"specification","body":"IETF","designation":"RFC 970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc970.txt","https://www.rfc-editor.org/rfc/rfc970.pdf"],"folder":"IETF/RFC-970","files":{"txt":{"path":"standards/IETF/RFC-970/RFC-970.txt","sha256":"ebdc3c0c9199ce49c8f1c2856563e1e4097a3d8a4e6d87de4260b56740cc9c97"}},"tags":["nested-reference","unchanged"],"summary":"Most prior work on congestion in datagram systems focuses on buffer\n management. We find it illuminating to consider the case of a packet\n switch with infinite storage. Such a packet switch can never run out\n of buffers. It can, however, still become congested. The meaning of\n congestion in an infinite-storage system is explored. We demonstrate\n the unexpected result that a datagram network with infinite storage,\n first-in-first-out queuing, at least two packet switches, and a\n finite packet lifetime will, under overload, drop all packets. By\n attacking the problem of congestion for the infinite-storage case, we\n discover new solutions applicable to switches with finite storage.","scope_keywords":["970","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0970","folder":"IETF/RFC-0970","source":"IETF/RFC-0970/RFC-0970.txt","version":null},{"body":"IETF","designation":"RFC 1016","folder":"IETF/RFC-1016","source":"IETF/RFC-1016/RFC-1016.txt","version":null},{"body":"IETF","designation":"RFC 1254","folder":"IETF/RFC-1254","source":"IETF/RFC-1254/RFC-1254.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null}],"search_text":"IETF RFC 970 Most prior work on congestion in datagram systems focuses on buffer\n management. We find it illuminating to consider the case of a packet\n switch with infinite storage. Such a packet switch can never run out\n of buffers. It can, however, still become congested. The meaning of\n congestion in an infinite-storage system is explored. We demonstrate\n the unexpected result that a datagram network with infinite storage,\n first-in-first-out queuing, at least two packet switches, and a\n finite packet lifetime will, under overload, drop all packets. By\n attacking the problem of congestion for the infinite-storage case, we\n discover new solutions applicable to switches with finite storage. 970 management nested-reference unchanged"},{"id":"IEEE IEEE 802.1","type":"specification","body":"IEEE","designation":"IEEE 802.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.1.html","download_urls":["https://standards.ieee.org/standard/802.1.html"],"folder":"IEEE/IEEE-802.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 1903","folder":"IETF/RFC-1903","source":"IETF/RFC-1903/RFC-1903.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2285","folder":"IETF/RFC-2285","source":"IETF/RFC-2285/RFC-2285.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2579","folder":"IETF/RFC-2579","source":"IETF/RFC-2579/RFC-2579.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 3069","folder":"IETF/RFC-3069","source":"IETF/RFC-3069/RFC-3069.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4026","folder":"IETF/RFC-4026","source":"IETF/RFC-4026/RFC-4026.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4137","folder":"IETF/RFC-4137","source":"IETF/RFC-4137/RFC-4137.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4554","folder":"IETF/RFC-4554","source":"IETF/RFC-4554/RFC-4554.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6221","folder":"IETF/RFC-6221","source":"IETF/RFC-6221/RFC-6221.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7319","folder":"IETF/RFC-7319","source":"IETF/RFC-7319/RFC-7319.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8034","folder":"IETF/RFC-8034","source":"IETF/RFC-8034/RFC-8034.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IEEE IEEE 802.1 nested-reference unavailable"},{"id":"IETF RFC 1095","type":"specification","body":"IETF","designation":"RFC 1095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1095.txt","https://www.rfc-editor.org/rfc/rfc1095.pdf"],"folder":"IETF/RFC-1095","files":{"txt":{"path":"standards/IETF/RFC-1095/RFC-1095.txt","sha256":"450fa778d8e5e4caafa8a37bee90470fea75ef569c49d2521e54ab371e30de1a"}},"tags":["nested-reference","unchanged"],"summary":"management information defined in the Internet-standard SMI and MIB\n map into CMIP. The second part of this memo is divided into sections\n for each of the protocols for which implementors' agreements are\n needed: CMISE, ACSE, ROSE, and the lightweight presentation protocol.\n The protocol profile defined in this part draws on the technical work\n of the OSI Network Management Forum [14] and the Network Management\n Special Interest Group (NMSIG) of the National Institute of Standards\n and Technology (NIST) (formerly the National Bureau of Standards).\n Wherever possible, an attempt has been made to remain consistent with\n the protocol agreements reached by these groups.\n\nWarrier & Besaw [Page 6]\n\f\nRFC 1095 CMOT April 1989\n\n Part I: Concepts and Models\n\n3. The OSI Management Framework\n\n The OSI management framework [15] presents the basic concepts and\n models required for developing network m","scope_keywords":["1095","attribute","attributes","management","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1095 management information defined in the Internet-standard SMI and MIB\n map into CMIP. The second part of this memo is divided into sections\n for each of the protocols for which implementors' agreements are\n needed: CMISE, ACSE, ROSE, and the lightweight presentation protocol.\n The protocol profile defined in this part draws on the technical work\n of the OSI Network Management Forum [14] and the Network Management\n Special Interest Group (NMSIG) of the National Institute of Standards\n and Technology (NIST) (formerly the National Bureau of Standards).\n Wherever possible, an attempt has been made to remain consistent with\n the protocol agreements reached by these groups.\n\nWarrier & Besaw [Page 6]\n\f\nRFC 1095 CMOT April 1989\n\n Part I: Concepts and Models\n\n3. The OSI Management Framework\n\n The OSI management framework [15] presents the basic concepts and\n models required for developing network m 1095 attribute attributes management presentation profile nested-reference unchanged"},{"id":"IETF RFC 1231","type":"specification","body":"IETF","designation":"RFC 1231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1231.txt","https://www.rfc-editor.org/rfc/rfc1231.pdf"],"folder":"IETF/RFC-1231","files":{"txt":{"path":"standards/IETF/RFC-1231/RFC-1231.txt","sha256":"1d30f7dd13c7b7d134fa072b1d7af51cbee91935ac104a79a389063c03a2141e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines managed\n objects used for managing subnetworks which use the IEEE 802.5 Token\n Ring technology described in 802.5 Token Ring Access Method and\n Physical Layer Specifications, IEEE Standard 802.5-1989.\n\nTransmission Working Group [Page 1]\n\f\nRFC 1231 IEEE 802.5 MIB May 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of ","scope_keywords":["1231","management","presentation","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null}],"search_text":"IETF RFC 1231 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines managed\n objects used for managing subnetworks which use the IEEE 802.5 Token\n Ring technology described in 802.5 Token Ring Access Method and\n Physical Layer Specifications, IEEE Standard 802.5-1989.\n\nTransmission Working Group [Page 1]\n\f\nRFC 1231 IEEE 802.5 MIB May 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of  1231 management presentation registered subject nested-reference unchanged"},{"id":"IETF RFC 1286","type":"specification","body":"IETF","designation":"RFC 1286","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1286.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1286.txt","https://www.rfc-editor.org/rfc/rfc1286.pdf"],"folder":"IETF/RFC-1286","files":{"txt":{"path":"standards/IETF/RFC-1286/RFC-1286.txt","sha256":"0af8a284f3b208e566b5aeb2d04508fa8938a20974d844c4614e2d5b2aee327c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing bridges based on the\n IEEE 802.1d draft standard between Local Area Network (LAN) segments.\n Provisions are made for support of transparent and source route\n bridging. Provisions are also made so that these objects apply to\n bridges connected by subnetworks other than LAN segments.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet ","scope_keywords":["1286","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null}],"search_text":"IETF RFC 1286 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing bridges based on the\n IEEE 802.1d draft standard between Local Area Network (LAN) segments.\n Provisions are made for support of transparent and source route\n bridging. Provisions are also made so that these objects apply to\n bridges connected by subnetworks other than LAN segments.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet  1286 management subject nested-reference unchanged"},{"id":"IETF RFC 1356","type":"specification","body":"IETF","designation":"RFC 1356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1356.txt","https://www.rfc-editor.org/rfc/rfc1356.pdf"],"folder":"IETF/RFC-1356","files":{"txt":{"path":"standards/IETF/RFC-1356/RFC-1356.txt","sha256":"5f6126be0228ad186c1eefcfd668bfa6f517b27ab724344fca4334a613984abd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the encapsulation of IP and other network\n layer protocols over X.25 networks, in accordance and alignment with\n ISO/IEC and CCITT standards. It is a replacement for RFC 877, \"A\n Standard for the Transmission of IP Datagrams Over Public Data\n Networks\" [1].\n\n It was written to correct several ambiguities in the Internet\n Standard for IP/X.25 (RFC 877), to align it with ISO/IEC standards\n that have been written following RFC 877, to allow interoperable\n multiprotocol operation between routers and bridges over X.25, and to\n add some additional remarks based upon practical experience with the\n specification over the 8 years since that RFC.\n\n The substantive change to the IP encapsulation is an increase in the\n allowed IP datagram Maximum Transmission Unit from 576 to 1600, to\n reflect existing practice.\n\n This document also specifies the Internet encapsulation for\n p","scope_keywords":["1356","identification","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1362","folder":"IETF/RFC-1362","source":"IETF/RFC-1362/RFC-1362.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null},{"body":"IETF","designation":"RFC 1582","folder":"IETF/RFC-1582","source":"IETF/RFC-1582/RFC-1582.txt","version":null},{"body":"IETF","designation":"RFC 1598","folder":"IETF/RFC-1598","source":"IETF/RFC-1598/RFC-1598.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1356 This document specifies the encapsulation of IP and other network\n layer protocols over X.25 networks, in accordance and alignment with\n ISO/IEC and CCITT standards. It is a replacement for RFC 877, \"A\n Standard for the Transmission of IP Datagrams Over Public Data\n Networks\" [1].\n\n It was written to correct several ambiguities in the Internet\n Standard for IP/X.25 (RFC 877), to align it with ISO/IEC standards\n that have been written following RFC 877, to allow interoperable\n multiprotocol operation between routers and bridges over X.25, and to\n add some additional remarks based upon practical experience with the\n specification over the 8 years since that RFC.\n\n The substantive change to the IP encapsulation is an increase in the\n allowed IP datagram Maximum Transmission Unit from 576 to 1600, to\n reflect existing practice.\n\n This document also specifies the Internet encapsulation for\n p 1356 identification management pid nested-reference unchanged"},{"id":"IETF RFC 1368","type":"specification","body":"IETF","designation":"RFC 1368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1368.txt","https://www.rfc-editor.org/rfc/rfc1368.pdf"],"folder":"IETF/RFC-1368","files":{"txt":{"path":"standards/IETF/RFC-1368/RFC-1368.txt","sha256":"ff74822e4d545103e2db5f734e273aa21d41de2d70fdcf624a82d5f2efa28e52"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing IEEE 802.3 10\n Mb/second baseband repeaters, sometimes referred to as \"hubs.\"","scope_keywords":["1368","attribute","attributes","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null}],"search_text":"IETF RFC 1368 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing IEEE 802.3 10\n Mb/second baseband repeaters, sometimes referred to as \"hubs.\" 1368 attribute attributes management subject nested-reference unchanged"},{"id":"IETF RFC 1443","type":"specification","body":"IETF","designation":"RFC 1443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1443.txt","https://www.rfc-editor.org/rfc/rfc1443.pdf"],"folder":"IETF/RFC-1443","files":{"txt":{"path":"standards/IETF/RFC-1443/RFC-1443.txt","sha256":"ab9cf8a2d1a3a02f38c8ba95041d9bf25de95b897d97d1e53e232760f305038c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1443 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Textual Conventions\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 2 Definitions ........................................... 4\n 3 Mapping of the TEXTUAL-CONVENTION macro ............... ","scope_keywords":["1443","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1665","folder":"IETF/RFC-1665","source":"IETF/RFC-1665/RFC-1665.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null}],"search_text":"IETF RFC 1443 Network Working Group J. Case\n Request for Comments: 1443 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Textual Conventions\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 2 Definitions ........................................... 4\n 3 Mapping of the TEXTUAL-CONVENTION macro ...............  1443 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1493","type":"specification","body":"IETF","designation":"RFC 1493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1493.txt","https://www.rfc-editor.org/rfc/rfc1493.pdf"],"folder":"IETF/RFC-1493","files":{"txt":{"path":"standards/IETF/RFC-1493/RFC-1493.txt","sha256":"a5deee17d80089f9807495f49abf42b276c5f6c515655a5be6d39298681ed320"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing MAC bridges based on\n the IEEE 802.1D-1990 standard between Local Area Network (LAN)\n segments. Provisions are made for support of transparent bridging.\n Provisions are also made so that these objects apply to bridges\n connected by subnetworks other than LAN segments.","scope_keywords":["1493","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null}],"search_text":"IETF RFC 1493 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing MAC bridges based on\n the IEEE 802.1D-1990 standard between Local Area Network (LAN)\n segments. Provisions are made for support of transparent bridging.\n Provisions are also made so that these objects apply to bridges\n connected by subnetworks other than LAN segments. 1493 management nested-reference unchanged"},{"id":"IETF RFC 1513","type":"specification","body":"IETF","designation":"RFC 1513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1513.txt","https://www.rfc-editor.org/rfc/rfc1513.pdf"],"folder":"IETF/RFC-1513","files":{"txt":{"path":"standards/IETF/RFC-1513/RFC-1513.txt","sha256":"54f39fffa952865ecb74d710c1661f6cb035c6932aa832d537c459c027e896eb"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines extensions to the Remote Network Monitoring MIB for\n managing 802.5 Token Ring networks.\n\n The Remote Network Monitoring MIB, RFC 1271, defines a framework for\n remote monitoring functions implemented on a network probe. That MIB\n defines objects broken down into nine functional groups. Some of\n those functional groups, the statistics and the history groups, have\n a view of the data-link layer that is specific to the media type and\n require specific objects to be defined for each media type. RFC 1271\n defined those specific objects necessary for Ethernet. This\n companion memo defines those specific objects necessary for Token\n Ring LANs.\n\n In addition, this memo defines some additional monitoring functions\n specifically for Token Ring. These are defined in the Ring Station\n Group, the Ring Station Order Group, the Ring Station Configuration\n Group, and the Source Routin","scope_keywords":["1513","algorithm","authorization","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null}],"search_text":"IETF RFC 1513 This memo defines extensions to the Remote Network Monitoring MIB for\n managing 802.5 Token Ring networks.\n\n The Remote Network Monitoring MIB, RFC 1271, defines a framework for\n remote monitoring functions implemented on a network probe. That MIB\n defines objects broken down into nine functional groups. Some of\n those functional groups, the statistics and the history groups, have\n a view of the data-link layer that is specific to the media type and\n require specific objects to be defined for each media type. RFC 1271\n defined those specific objects necessary for Ethernet. This\n companion memo defines those specific objects necessary for Token\n Ring LANs.\n\n In addition, this memo defines some additional monitoring functions\n specifically for Token Ring. These are defined in the Ring Station\n Group, the Ring Station Order Group, the Ring Station Configuration\n Group, and the Source Routin 1513 algorithm authorization management policy nested-reference unchanged"},{"id":"IETF RFC 1516","type":"specification","body":"IETF","designation":"RFC 1516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1516.txt","https://www.rfc-editor.org/rfc/rfc1516.pdf"],"folder":"IETF/RFC-1516","files":{"txt":{"path":"standards/IETF/RFC-1516/RFC-1516.txt","sha256":"b864d12524727f6b1ebf0354b786c157bf4a1290193376128cd9c6e3dc021e13"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 10\n Mb/second baseband repeaters, sometimes referred to as \"hubs.\"","scope_keywords":["1516","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 1516 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 10\n Mb/second baseband repeaters, sometimes referred to as \"hubs.\" 1516 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1525","type":"specification","body":"IETF","designation":"RFC 1525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1525.txt","https://www.rfc-editor.org/rfc/rfc1525.pdf"],"folder":"IETF/RFC-1525","files":{"txt":{"path":"standards/IETF/RFC-1525/RFC-1525.txt","sha256":"3b9b12d0ee4a34c7774851c6882fe81bfb890b0abd309ae194b65a899fb05103"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Decker\nRequest for Comments: 1525 cisco Systems, Inc.\nObsoletes: 1286 K. McCloghrie\nCategory: Standards Track Hughes LAN Systems, Inc.\n P. Langille\n DEC\n A. Rijsinghani\n DEC\n September 1993\n\n Definitions of Managed Objects for\n Source Routing Bridges\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ......................................... 2\n 2. The Network Management Framework ..................... 2\n 2.1 Object Definitions .................................. 2\n 3. Overview ............................................. 2\n 3.1 Struc","scope_keywords":["1525","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null}],"search_text":"IETF RFC 1525 Network Working Group E. Decker\nRequest for Comments: 1525 cisco Systems, Inc.\nObsoletes: 1286 K. McCloghrie\nCategory: Standards Track Hughes LAN Systems, Inc.\n P. Langille\n DEC\n A. Rijsinghani\n DEC\n September 1993\n\n Definitions of Managed Objects for\n Source Routing Bridges\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ......................................... 2\n 2. The Network Management Framework ..................... 2\n 2.1 Object Definitions .................................. 2\n 3. Overview ............................................. 2\n 3.1 Struc 1525 management nested-reference unchanged"},{"id":"IETF RFC 1717","type":"specification","body":"IETF","designation":"RFC 1717","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1717.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1717.txt","https://www.rfc-editor.org/rfc/rfc1717.pdf"],"folder":"IETF/RFC-1717","files":{"txt":{"path":"standards/IETF/RFC-1717/RFC-1717.txt","sha256":"579d9b8e51b6604726f71fe683cfdbb588b32f53962c794874960084fd273fe6"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method for splitting, recombining and\n sequencing datagrams across multiple logical data links. This work\n was originally motivated by the desire to exploit multiple bearer\n channels in ISDN, but is equally applicable to any situation in which\n multiple PPP links connect two systems, including async links. This\n is accomplished by means of new PPP [2] options and protocols.\n\nAcknowledgements\n\n The authors specifically wish to thank Fred Baker of ACC, Craig Fox\n of Network Systems, Gerry Meyer of Spider Systems, Tom Coradetti of\n Digiboard (for the Endpoint Discriminator option), Dan Brennan of\n Penril Datability Networks, Vernon Schryver of SGI (for the\n comprehensive discussion of padding), and the members of the IP over\n Large Public Data Networks and PPP Extensions working groups, for\n much useful discussion on the subject.","scope_keywords":["1717","algorithm","algorithms","authentication","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 1969","folder":"IETF/RFC-1969","source":"IETF/RFC-1969/RFC-1969.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null}],"search_text":"IETF RFC 1717 This document proposes a method for splitting, recombining and\n sequencing datagrams across multiple logical data links. This work\n was originally motivated by the desire to exploit multiple bearer\n channels in ISDN, but is equally applicable to any situation in which\n multiple PPP links connect two systems, including async links. This\n is accomplished by means of new PPP [2] options and protocols.\n\nAcknowledgements\n\n The authors specifically wish to thank Fred Baker of ACC, Craig Fox\n of Network Systems, Gerry Meyer of Spider Systems, Tom Coradetti of\n Digiboard (for the Endpoint Discriminator option), Dan Brennan of\n Penril Datability Networks, Vernon Schryver of SGI (for the\n comprehensive discussion of padding), and the members of the IP over\n Large Public Data Networks and PPP Extensions working groups, for\n much useful discussion on the subject. 1717 algorithm algorithms authentication pid subject nested-reference unchanged"},{"id":"IETF RFC 1748","type":"specification","body":"IETF","designation":"RFC 1748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1748.txt","https://www.rfc-editor.org/rfc/rfc1748.pdf"],"folder":"IETF/RFC-1748","files":{"txt":{"path":"standards/IETF/RFC-1748/RFC-1748.txt","sha256":"3e2a61bb879909650aa0efced1251197e9bea7e8462f6e1797df477068cfeb93"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 1748 E. Decker\nObsoletes: 1743, 1231 cisco Systems, Inc.\nCategory: Standards Track December 1994\n\n IEEE 802.5 MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 2\n 3. Overview ................................................. 2\n 3.1 MAC Addresses ........................................... 3\n 3.2 Rel","scope_keywords":["1748","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1748 Network Working Group K. McCloghrie\nRequest for Comments: 1748 E. Decker\nObsoletes: 1743, 1231 cisco Systems, Inc.\nCategory: Standards Track December 1994\n\n IEEE 802.5 MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 2\n 3. Overview ................................................. 2\n 3.1 MAC Addresses ........................................... 3\n 3.2 Rel 1748 management presentation nested-reference unchanged"},{"id":"IETF RFC 1749","type":"specification","body":"IETF","designation":"RFC 1749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1749.txt","https://www.rfc-editor.org/rfc/rfc1749.pdf"],"folder":"IETF/RFC-1749","files":{"txt":{"path":"standards/IETF/RFC-1749/RFC-1749.txt","sha256":"32fb19ee6a117e942e2d3cdb63062bc9a859b106c46de194813f48d4c52b4408"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 1749 F. Baker\nUpdates: 1748 E. Decker\nCategory: Standards Track cisco Systems, Inc.\n December 1994\n\n IEEE 802.5 Station Source Routing MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 2\n 3. Overview ................................................. 2\n 3.1 Source Routing ............................","scope_keywords":["1749","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1749 Network Working Group K. McCloghrie\nRequest for Comments: 1749 F. Baker\nUpdates: 1748 E. Decker\nCategory: Standards Track cisco Systems, Inc.\n December 1994\n\n IEEE 802.5 Station Source Routing MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 2\n 3. Overview ................................................. 2\n 3.1 Source Routing ............................ 1749 management nested-reference unchanged"},{"id":"IETF RFC 1903","type":"specification","body":"IETF","designation":"RFC 1903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1903.txt","https://www.rfc-editor.org/rfc/rfc1903.pdf"],"folder":"IETF/RFC-1903","files":{"txt":{"path":"standards/IETF/RFC-1903/RFC-1903.txt","sha256":"67497f6d52a4461114a20c41402eddb18208b2473ae642b8054c414874199352"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1903 J. Case\nObsoletes: 1443 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Textual Conventions\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 1.1 A Note on Terminology ...................................... 2\n 2. Definitions .","scope_keywords":["1903","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2493","folder":"IETF/RFC-2493","source":"IETF/RFC-2493/RFC-2493.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2514","folder":"IETF/RFC-2514","source":"IETF/RFC-2514/RFC-2514.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1903 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1903 J. Case\nObsoletes: 1443 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Textual Conventions\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 1.1 A Note on Terminology ...................................... 2\n 2. Definitions . 1903 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1990","type":"specification","body":"IETF","designation":"RFC 1990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1990.txt","https://www.rfc-editor.org/rfc/rfc1990.pdf"],"folder":"IETF/RFC-1990","files":{"txt":{"path":"standards/IETF/RFC-1990/RFC-1990.txt","sha256":"f723ef6d55f58f7b6edd92ab3ea56befe5d0b7c9efa7ee7ee9aff27adedbf775"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method for splitting, recombining and\n sequencing datagrams across multiple logical data links. This work\n was originally motivated by the desire to exploit multiple bearer\n channels in ISDN, but is equally applicable to any situation in which\n multiple PPP links connect two systems, including async links. This\n is accomplished by means of new PPP [2] options and protocols.\n\n The differences between the current PPP Multilink specification (RFC\n 1717) and this memo are explained in Section 11. Any system\n implementing the additional restrictions required by this memo will\n be backwards compatible with conforming RFC 1717 implementations.\n\nAcknowledgements\n\n The authors specifically wish to thank Fred Baker of ACC, Craig Fox\n of Network Systems, Gerry Meyer of Spider Systems, Dan Brennan of\n Penril Datability Networks, Vernon Schryver of SGI (for the\n comprehensive","scope_keywords":["1990","algorithm","algorithms","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2125","folder":"IETF/RFC-2125","source":"IETF/RFC-2125/RFC-2125.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 1990 This document proposes a method for splitting, recombining and\n sequencing datagrams across multiple logical data links. This work\n was originally motivated by the desire to exploit multiple bearer\n channels in ISDN, but is equally applicable to any situation in which\n multiple PPP links connect two systems, including async links. This\n is accomplished by means of new PPP [2] options and protocols.\n\n The differences between the current PPP Multilink specification (RFC\n 1717) and this memo are explained in Section 11. Any system\n implementing the additional restrictions required by this memo will\n be backwards compatible with conforming RFC 1717 implementations.\n\nAcknowledgements\n\n The authors specifically wish to thank Fred Baker of ACC, Craig Fox\n of Network Systems, Gerry Meyer of Spider Systems, Dan Brennan of\n Penril Datability Networks, Vernon Schryver of SGI (for the\n comprehensive 1990 algorithm algorithms pid subject nested-reference unchanged"},{"id":"IETF RFC 2067","type":"specification","body":"IETF","designation":"RFC 2067","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2067.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2067.txt","https://www.rfc-editor.org/rfc/rfc2067.pdf"],"folder":"IETF/RFC-2067","files":{"txt":{"path":"standards/IETF/RFC-2067/RFC-2067.txt","sha256":"8140792445ac71d1163d7fcbba316583cf8c09ca5f6ceb32fe953ddb0b19dc5d"}},"tags":["nested-reference","unchanged"],"summary":"ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of\n IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. ANSI X3.222-\n 1993 (HIPPI-SC[4]) describes the operation of HIPPI physical\n switches. The ANSI committee responsible for these standards chose\n to leave HIPPI networking issues largely outside the scope of their\n standards; this document describes the use of HIPPI switches as IP\n local area networks.\n\n This memo is a revision of RFC 1374, \"IP and ARP on HIPPI\", and is\n intended to replace it in the Standards Track. RFC 1374 has been a\n Proposed Standard since November, 1992, with at least 10\n implementations of IP encapsulation and HIPPI switch discipline. No\n major changes to it are required. However, the ARP part of RFC 1374\n has not had sufficient implementation experience to be advanced to\n Draft Standard. The present document contains all of RFC 1374 except\n fo","scope_keywords":["2067","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2067 ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of\n IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. ANSI X3.222-\n 1993 (HIPPI-SC[4]) describes the operation of HIPPI physical\n switches. The ANSI committee responsible for these standards chose\n to leave HIPPI networking issues largely outside the scope of their\n standards; this document describes the use of HIPPI switches as IP\n local area networks.\n\n This memo is a revision of RFC 1374, \"IP and ARP on HIPPI\", and is\n intended to replace it in the Standards Track. RFC 1374 has been a\n Proposed Standard since November, 1992, with at least 10\n implementations of IP encapsulation and HIPPI switch discipline. No\n major changes to it are required. However, the ARP part of RFC 1374\n has not had sufficient implementation experience to be advanced to\n Draft Standard. The present document contains all of RFC 1374 except\n fo 2067 management path nested-reference unchanged"},{"id":"IETF RFC 2108","type":"specification","body":"IETF","designation":"RFC 2108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2108.txt","https://www.rfc-editor.org/rfc/rfc2108.pdf"],"folder":"IETF/RFC-2108","files":{"txt":{"path":"standards/IETF/RFC-2108/RFC-2108.txt","sha256":"840ce79afde48ef6a8f8f16ef27158722e3587497d869f103e14bfac6975ad85"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 10 and 100\n Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, \"10\n & 100 Mb/s Management,\" October 26, 1995.","scope_keywords":["2108","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 2108 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 10 and 100\n Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, \"10\n & 100 Mb/s Management,\" October 26, 1995. 2108 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 2285","type":"specification","body":"IETF","designation":"RFC 2285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2285.txt","https://www.rfc-editor.org/rfc/rfc2285.pdf"],"folder":"IETF/RFC-2285","files":{"txt":{"path":"standards/IETF/RFC-2285/RFC-2285.txt","sha256":"460640bb3321aa55110540cbc61a631eaafcb10193debd6a6d3ced34c5602890"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Mandeville\nRequest for Comments: 2285 European Network Laboratories\nCategory: Informational February 1998\n\n Benchmarking Terminology for LAN Switching Devices\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Existing definitions . . . . . . . . . . . . . . . . . . . . . . 2\n 3. Term definitions . . . . . . . . . . . . . . . . . . . . . . . . 3\n 3.1 Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 3\n 3.1.1 Device under test (DUT) . . . . . . . . . . . . . . . . 3\n 3.1.2 System under test (SUT) . . . . . . . . . . . . . . . . 3\n 3.2 Traffic orientatio","scope_keywords":["2285","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2432","folder":"IETF/RFC-2432","source":"IETF/RFC-2432/RFC-2432.txt","version":null},{"body":"IETF","designation":"RFC 2647","folder":"IETF/RFC-2647","source":"IETF/RFC-2647/RFC-2647.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null}],"search_text":"IETF RFC 2285 Network Working Group R. Mandeville\nRequest for Comments: 2285 European Network Laboratories\nCategory: Informational February 1998\n\n Benchmarking Terminology for LAN Switching Devices\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Existing definitions . . . . . . . . . . . . . . . . . . . . . . 2\n 3. Term definitions . . . . . . . . . . . . . . . . . . . . . . . . 3\n 3.1 Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 3\n 3.1.1 Device under test (DUT) . . . . . . . . . . . . . . . . 3\n 3.1.2 System under test (SUT) . . . . . . . . . . . . . . . . 3\n 3.2 Traffic orientatio 2285 key nested-reference unchanged"},{"id":"IETF RFC 2579","type":"specification","body":"IETF","designation":"RFC 2579","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2579.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2579.txt","https://www.rfc-editor.org/rfc/rfc2579.pdf"],"folder":"IETF/RFC-2579","files":{"txt":{"path":"standards/IETF/RFC-2579/RFC-2579.txt","sha256":"1bde590451bdd6441af9dc4648ed02529816ea11f5f42b52a5f5d42066ea7440"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Editors of this version:\nRequest for Comments: 2579 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1903 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Textual Conventions for SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ..","scope_keywords":["2579","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3595","folder":"IETF/RFC-3595","source":"IETF/RFC-3595/RFC-3595.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null}],"search_text":"IETF RFC 2579 Network Working Group Editors of this version:\nRequest for Comments: 2579 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1903 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Textual Conventions for SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .. 2579 management nested-reference unchanged"},{"id":"IETF RFC 2613","type":"specification","body":"IETF","designation":"RFC 2613","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2613.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2613.txt","https://www.rfc-editor.org/rfc/rfc2613.pdf"],"folder":"IETF/RFC-2613","files":{"txt":{"path":"standards/IETF/RFC-2613/RFC-2613.txt","sha256":"d2eb5ad114623312ffcca6cb789c656df9e5dcdc354c9196a2b61d262cace5c5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices in switched networks environments.","scope_keywords":["2613","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2613 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices in switched networks environments. 2613 key management nested-reference unchanged"},{"id":"IETF RFC 2674","type":"specification","body":"IETF","designation":"RFC 2674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2674.txt","https://www.rfc-editor.org/rfc/rfc2674.pdf"],"folder":"IETF/RFC-2674","files":{"txt":{"path":"standards/IETF/RFC-2674/RFC-2674.txt","sha256":"d6d9ad08a94b131fe064cf8d17a3a319e08826d97ac10376a719b42027dd87e3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines two MIB modules for managing the new\n capabilities of MAC bridges defined by the IEEE 802.1D-1998 MAC\n Bridges and the IEEE 802.1Q-1998 Virtual LAN (VLAN) standards for\n bridging between Local Area Network (LAN) segments. One MIB module\n defines objects for managing the 'Traffic Classes' and 'Enhanced\n Multicast Filtering' components of IEEE 802.1D-1998. The other MIB\n module defines objects for managing IEEE 802.1Q VLANs.\n\n Provisions are made for support of transparent bridging. Provisions\n are also made so that these objects apply to bridges connected by\n subnetworks other than LAN segments. This memo also includes several\n MIB modules in a manner that is compliant to the SMIv2 [V2SMI].\n\n This memo supplements RFC 1493 [B","scope_keywords":["2674","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null}],"search_text":"IETF RFC 2674 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines two MIB modules for managing the new\n capabilities of MAC bridges defined by the IEEE 802.1D-1998 MAC\n Bridges and the IEEE 802.1Q-1998 Virtual LAN (VLAN) standards for\n bridging between Local Area Network (LAN) segments. One MIB module\n defines objects for managing the 'Traffic Classes' and 'Enhanced\n Multicast Filtering' components of IEEE 802.1D-1998. The other MIB\n module defines objects for managing IEEE 802.1Q VLANs.\n\n Provisions are made for support of transparent bridging. Provisions\n are also made so that these objects apply to bridges connected by\n subnetworks other than LAN segments. This memo also includes several\n MIB modules in a manner that is compliant to the SMIv2 [V2SMI].\n\n This memo supplements RFC 1493 [B 2674 management nested-reference unchanged"},{"id":"IETF RFC 2895","type":"specification","body":"IETF","designation":"RFC 2895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2895.txt","https://www.rfc-editor.org/rfc/rfc2895.pdf"],"folder":"IETF/RFC-2895","files":{"txt":{"path":"standards/IETF/RFC-2895/RFC-2895.txt","sha256":"924a9fe143a65944108b2b54b7df6ec54bde169fb1f4367d7e504beda29d2e50"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a notation describing protocol layers in a protocol\n encapsulation, specifically for use in encoding INDEX values for the\n protocolDirTable, found in the RMON-2 MIB (Remote Network Monitoring\n Management Information Base) [RFC2021]. The definitions for the\n standard protocol directory base layer identifiers are also included.\n\n The first version of the RMON Protocol Identifiers Document [RFC2074]\n has been split into a standards-track Reference portion (this\n document), and an Informational document. The RMON Protocol\n Identifier Macros document [RFC2896] now contains the non-normative\n portion of that specification.\n\n This document obsoletes RFC 2074.\n\nBierman, et al. Standards Track [Page 1]\n\f\nRFC 2895 RMON PI Reference August 2000","scope_keywords":["2895","algorithm","algorithms","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null}],"search_text":"IETF RFC 2895 This memo defines a notation describing protocol layers in a protocol\n encapsulation, specifically for use in encoding INDEX values for the\n protocolDirTable, found in the RMON-2 MIB (Remote Network Monitoring\n Management Information Base) [RFC2021]. The definitions for the\n standard protocol directory base layer identifiers are also included.\n\n The first version of the RMON Protocol Identifiers Document [RFC2074]\n has been split into a standards-track Reference portion (this\n document), and an Informational document. The RMON Protocol\n Identifier Macros document [RFC2896] now contains the non-normative\n portion of that specification.\n\n This document obsoletes RFC 2074.\n\nBierman, et al. Standards Track [Page 1]\n\f\nRFC 2895 RMON PI Reference August 2000 2895 algorithm algorithms attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 3069","type":"specification","body":"IETF","designation":"RFC 3069","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3069.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3069.txt","https://www.rfc-editor.org/rfc/rfc3069.pdf"],"folder":"IETF/RFC-3069","files":{"txt":{"path":"standards/IETF/RFC-3069/RFC-3069.txt","sha256":"2b6c1d6e81093d5fcefa390c5ac548b85beff07347f3f297bcde9c5fcc039559"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. McPherson\nRequest for Comments: 3069 Amber Networks, Inc.\nCategory: Informational B. Dykes\n Onesecure, Inc.\n February 2001\n\n VLAN Aggregation for Efficient IP Address Allocation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document introduces the concept of Virtual Local Area Network\n (VLAN) aggregation as it relates to IPv4 address allocation. A\n mechanism is described by which hosts that reside in the same\n physical switched infrastructure, but separate virtual broadcast\n domains, are addressed from the same IPv4 subnet and share a common\n default gateway IP address, thereby removing the requirement of a\n dedicated IP subnet for ea","scope_keywords":["3069"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 3069 Network Working Group D. McPherson\nRequest for Comments: 3069 Amber Networks, Inc.\nCategory: Informational B. Dykes\n Onesecure, Inc.\n February 2001\n\n VLAN Aggregation for Efficient IP Address Allocation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document introduces the concept of Virtual Local Area Network\n (VLAN) aggregation as it relates to IPv4 address allocation. A\n mechanism is described by which hosts that reside in the same\n physical switched infrastructure, but separate virtual broadcast\n domains, are addressed from the same IPv4 subnet and share a common\n default gateway IP address, thereby removing the requirement of a\n dedicated IP subnet for ea 3069 nested-reference unchanged"},{"id":"IETF RFC 3176","type":"specification","body":"IETF","designation":"RFC 3176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3176.txt","https://www.rfc-editor.org/rfc/rfc3176.pdf"],"folder":"IETF/RFC-3176","files":{"txt":{"path":"standards/IETF/RFC-3176/RFC-3176.txt","sha256":"0c00221e9cd564997f28bbc9be670df8d3d207783ebe0c28033206d540f686e4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines InMon Coporation's sFlow system. sFlow is a\n technology for monitoring traffic in data networks containing\n switches and routers. In particular, it defines the sampling\n mechanisms implemented in an sFlow Agent for monitoring traffic, the\n sFlow MIB for controlling the sFlow Agent, and the format of sample\n data used by the sFlow Agent when forwarding data to a central data\n collector.","scope_keywords":["3176","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null}],"search_text":"IETF RFC 3176 This memo defines InMon Coporation's sFlow system. sFlow is a\n technology for monitoring traffic in data networks containing\n switches and routers. In particular, it defines the sampling\n mechanisms implemented in an sFlow Agent for monitoring traffic, the\n sFlow MIB for controlling the sFlow Agent, and the format of sample\n data used by the sFlow Agent when forwarding data to a central data\n collector. 3176 management nested-reference unchanged"},{"id":"IETF RFC 3270","type":"specification","body":"IETF","designation":"RFC 3270","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3270.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3270.txt","https://www.rfc-editor.org/rfc/rfc3270.pdf"],"folder":"IETF/RFC-3270","files":{"txt":{"path":"standards/IETF/RFC-3270/RFC-3270.txt","sha256":"a51accebf603c9de8e4d08f350ab531c5d74d7bfe54b133f12031de9485bab70"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a flexible solution for support of\n Differentiated Services (Diff-Serv) over Multi-Protocol Label\n Switching (MPLS) networks.\n\n This solution allows the MPLS network administrator to select how\n Diff-Serv Behavior Aggregates (BAs) are mapped onto Label Switched\n Paths (LSPs) so that he/she can best match the Diff-Serv, Traffic\n Engineering and protection objectives within his/her particular\n network. For instance, this solution allows the network\n administrator to decide whether different sets of BAs are to be\n mapped onto the same LSP or mapped onto separate LSPs.\n\nLe Faucheur, et. al. Standards Track [Page 1]\n\f\nRFC 3270 MPLS Support of Differentiated Services May 2002","scope_keywords":["3270","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4182","folder":"IETF/RFC-4182","source":"IETF/RFC-4182/RFC-4182.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 3270 This document defines a flexible solution for support of\n Differentiated Services (Diff-Serv) over Multi-Protocol Label\n Switching (MPLS) networks.\n\n This solution allows the MPLS network administrator to select how\n Diff-Serv Behavior Aggregates (BAs) are mapped onto Label Switched\n Paths (LSPs) so that he/she can best match the Diff-Serv, Traffic\n Engineering and protection objectives within his/her particular\n network. For instance, this solution allows the network\n administrator to decide whether different sets of BAs are to be\n mapped onto the same LSP or mapped onto separate LSPs.\n\nLe Faucheur, et. al. Standards Track [Page 1]\n\f\nRFC 3270 MPLS Support of Differentiated Services May 2002 3270 management path nested-reference unchanged"},{"id":"IETF RFC 3289","type":"specification","body":"IETF","designation":"RFC 3289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3289.txt","https://www.rfc-editor.org/rfc/rfc3289.pdf"],"folder":"IETF/RFC-3289","files":{"txt":{"path":"standards/IETF/RFC-3289/RFC-3289.txt","sha256":"dd21adbb42380659f25d5e4f17386f0392f80be2e14e9a2bc87115680f90c1ea"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an SMIv2 (Structure of Management Information\n version 2) MIB for a device implementing the Differentiated Services\n Architecture. It may be used both for monitoring and configuration\n of a router or switch capable of Differentiated Services\n functionality.","scope_keywords":["3289","algorithm","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 3289 This memo describes an SMIv2 (Structure of Management Information\n version 2) MIB for a device implementing the Differentiated Services\n Architecture. It may be used both for monitoring and configuration\n of a router or switch capable of Differentiated Services\n functionality. 3289 algorithm management path policy nested-reference unchanged"},{"id":"IETF RFC 3290","type":"specification","body":"IETF","designation":"RFC 3290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3290.txt","https://www.rfc-editor.org/rfc/rfc3290.pdf"],"folder":"IETF/RFC-3290","files":{"txt":{"path":"standards/IETF/RFC-3290/RFC-3290.txt","sha256":"048dae7f3f6e3da1a2b0fc6027e4f4bcebf33327e18ba3f38da3f2d18c76b0fa"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an informal management model of Differentiated\n Services (Diffserv) routers for use in their management and\n configuration. This model defines functional datapath elements\n (e.g., classifiers, meters, actions, marking, absolute dropping,\n counting, multiplexing), algorithmic droppers, queues and schedulers.\n It describes possible configuration parameters for these elements and\n how they might be interconnected to realize the range of traffic\n conditioning and per-hop behavior (PHB) functionalities described in\n the Diffserv Architecture.","scope_keywords":["3290","algorithm","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3290 This document proposes an informal management model of Differentiated\n Services (Diffserv) routers for use in their management and\n configuration. This model defines functional datapath elements\n (e.g., classifiers, meters, actions, marking, absolute dropping,\n counting, multiplexing), algorithmic droppers, queues and schedulers.\n It describes possible configuration parameters for these elements and\n how they might be interconnected to realize the range of traffic\n conditioning and per-hop behavior (PHB) functionalities described in\n the Diffserv Architecture. 3290 algorithm management path trust nested-reference unchanged"},{"id":"IETF RFC 3355","type":"specification","body":"IETF","designation":"RFC 3355","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3355.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3355.txt","https://www.rfc-editor.org/rfc/rfc3355.pdf"],"folder":"IETF/RFC-3355","files":{"txt":{"path":"standards/IETF/RFC-3355/RFC-3355.txt","sha256":"636bcc5db57d8c0078cc70f62534fc5b37980be232e87555be38a2f1db6403c1"}},"tags":["nested-reference","unchanged"],"summary":"The Layer Two Tunneling Protocol (L2TP) provides a standard method\n for transporting the link layer of the Point-to-Point Protocol (PPP)\n between a dial-up server and a Network Access Server, using a network\n connection in lieu of a physical point-to-point connection. This\n document describes the use of an Asynchronous Transfer Mode (ATM)\n network for the underlying network connection. ATM User-Network\n Interface (UNI) Signaling Specification Version 4.0 or Version 3.1\n with ATM Adaptation Layer 5 (AAL5) are supported as interfaces to the\n ATM network.\n\nApplicability\n\n This specification is intended for implementations of L2TP that use\n ATM to provide the communications link between the L2TP Access\n Concentrator and the L2TP Network Server.\n\nSingh, et. al. Standards Track [Page 1]\n\f\nRFC 3355 L2TP Over AAL5 August 2002\n\n1. Introduction\n\n The Point-to-Point Protocol (PPP) [RFC1661], is fre","scope_keywords":["3355","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null}],"search_text":"IETF RFC 3355 The Layer Two Tunneling Protocol (L2TP) provides a standard method\n for transporting the link layer of the Point-to-Point Protocol (PPP)\n between a dial-up server and a Network Access Server, using a network\n connection in lieu of a physical point-to-point connection. This\n document describes the use of an Asynchronous Transfer Mode (ATM)\n network for the underlying network connection. ATM User-Network\n Interface (UNI) Signaling Specification Version 4.0 or Version 3.1\n with ATM Adaptation Layer 5 (AAL5) are supported as interfaces to the\n ATM network.\n\nApplicability\n\n This specification is intended for implementations of L2TP that use\n ATM to provide the communications link between the L2TP Access\n Concentrator and the L2TP Network Server.\n\nSingh, et. al. Standards Track [Page 1]\n\f\nRFC 3355 L2TP Over AAL5 August 2002\n\n1. Introduction\n\n The Point-to-Point Protocol (PPP) [RFC1661], is fre 3355 delivery key nested-reference unchanged"},{"id":"IETF RFC 3488","type":"specification","body":"IETF","designation":"RFC 3488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3488.txt","https://www.rfc-editor.org/rfc/rfc3488.pdf"],"folder":"IETF/RFC-3488","files":{"txt":{"path":"standards/IETF/RFC-3488/RFC-3488.txt","sha256":"9e81ea384311eb21e8b09b41f0ba672834baf5591156b65c66f9d459bbf7cb84"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Router-port Group Management Protocol\n (RGMP). This protocol was developed by Cisco Systems and is used\n between multicast routers and switches to restrict multicast packet\n forwarding in switches to those routers where the packets may be\n needed.\n\n RGMP is designed for backbone switched networks where multiple, high\n speed routers are interconnected.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].\n\n2. Introduction\n\n IGMP Snooping is a popular, but not well documented mechanism to\n restrict multicast traffic, in switched networks, to those ports that\n want to receive the multicast traffic. It dynamically establishes\n and terminates multicast group specific forward","scope_keywords":["3488","algorithm","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null}],"search_text":"IETF RFC 3488 This document describes the Router-port Group Management Protocol\n (RGMP). This protocol was developed by Cisco Systems and is used\n between multicast routers and switches to restrict multicast packet\n forwarding in switches to those routers where the packets may be\n needed.\n\n RGMP is designed for backbone switched networks where multiple, high\n speed routers are interconnected.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].\n\n2. Introduction\n\n IGMP Snooping is a popular, but not well documented mechanism to\n restrict multicast traffic, in switched networks, to those ports that\n want to receive the multicast traffic. It dynamically establishes\n and terminates multicast group specific forward 3488 algorithm key management nested-reference unchanged"},{"id":"IETF RFC 3512","type":"specification","body":"IETF","designation":"RFC 3512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3512.txt","https://www.rfc-editor.org/rfc/rfc3512.pdf"],"folder":"IETF/RFC-3512","files":{"txt":{"path":"standards/IETF/RFC-3512/RFC-3512.txt","sha256":"93b39657f2a2cce653a26100b56abd13b17c5f054e76fb3cbc99e4df7f4a9fc5"}},"tags":["nested-reference","unchanged"],"summary":"This document is written for readers interested in the Internet\n Standard Management Framework and its protocol, the Simple Network\n Management Protocol (SNMP). In particular, it offers guidance in the\n effective use of SNMP for configuration management. This information\n is relevant to vendors that build network elements, management\n application developers, and those that acquire and deploy this\n technology in their networks.","scope_keywords":["3512","authentication","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null}],"search_text":"IETF RFC 3512 This document is written for readers interested in the Internet\n Standard Management Framework and its protocol, the Simple Network\n Management Protocol (SNMP). In particular, it offers guidance in the\n effective use of SNMP for configuration management. This information\n is relevant to vendors that build network elements, management\n application developers, and those that acquire and deploy this\n technology in their networks. 3512 authentication management policy nested-reference unchanged"},{"id":"IETF RFC 3577","type":"specification","body":"IETF","designation":"RFC 3577","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3577.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3577.txt","https://www.rfc-editor.org/rfc/rfc3577.pdf"],"folder":"IETF/RFC-3577","files":{"txt":{"path":"standards/IETF/RFC-3577/RFC-3577.txt","sha256":"6fff8e3f7451e19960986f48d8794b18c5462a43b9f26c60e2f08f557fe59ae7"}},"tags":["nested-reference","unchanged"],"summary":"The Remote Monitoring (RMON) Framework consists of a number of\n interrelated documents. This memo describes these documents and how\n they relate to one another.","scope_keywords":["3577","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3577 The Remote Monitoring (RMON) Framework consists of a number of\n interrelated documents. This memo describes these documents and how\n they relate to one another. 3577 management nested-reference unchanged"},{"id":"IETF RFC 3670","type":"specification","body":"IETF","designation":"RFC 3670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3670.txt","https://www.rfc-editor.org/rfc/rfc3670.pdf"],"folder":"IETF/RFC-3670","files":{"txt":{"path":"standards/IETF/RFC-3670/RFC-3670.txt","sha256":"d0e25e44adb8fbeee3b363a1414e9e6c6da2d6520cb4ea011d962ba8af059afb"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to define an information model to\n describe the quality of service (QoS) mechanisms inherent in\n different network devices, including hosts. Broadly speaking, these\n mechanisms describe the properties common to selecting and\n conditioning traffic through the forwarding path (datapath) of a\n network device. This selection and conditioning of traffic in the\n datapath spans both major QoS architectures: Differentiated Services\n and Integrated Services.\n\n This document should be used with the QoS Policy Information Model\n (QPIM) to model how policies can be defined to manage and configure\n the QoS mechanisms (i.e., the classification, marking, metering,\n dropping, queuing, and scheduling functionality) of devices.\n Together, these two documents describe how to write QoS policy rules\n to configure and manage the QoS mechanisms present in the datapaths\n of devic","scope_keywords":["3670","attribute","attributes","management","path","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 3670 The purpose of this document is to define an information model to\n describe the quality of service (QoS) mechanisms inherent in\n different network devices, including hosts. Broadly speaking, these\n mechanisms describe the properties common to selecting and\n conditioning traffic through the forwarding path (datapath) of a\n network device. This selection and conditioning of traffic in the\n datapath spans both major QoS architectures: Differentiated Services\n and Integrated Services.\n\n This document should be used with the QoS Policy Information Model\n (QPIM) to model how policies can be defined to manage and configure\n the QoS mechanisms (i.e., the classification, marking, metering,\n dropping, queuing, and scheduling functionality) of devices.\n Together, these two documents describe how to write QoS policy rules\n to configure and manage the QoS mechanisms present in the datapaths\n of devic 3670 attribute attributes management path policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 3770","type":"specification","body":"IETF","designation":"RFC 3770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3770.txt","https://www.rfc-editor.org/rfc/rfc3770.pdf"],"folder":"IETF/RFC-3770","files":{"txt":{"path":"standards/IETF/RFC-3770/RFC-3770.txt","sha256":"260e04a966cc06a49426a28ed8d86b9fa751540c988436309bcfbd5d8dc338ee"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two EAP extended key usage values and a public\n key certificate extension to carry Wireless LAN (WLAN) System Service\n identifiers (SSIDs).\n\n1. Introduction\n\n Several Extensible Authentication Protocol (EAP) [EAP] authentication\n methods employ X.509 public key certificates. For example, EAP-TLS\n [EAP-TLS] can be used with PPP [PPP] as well as IEEE 802.1X [802.1X].\n PPP is used for dial-up and VPN environments. IEEE 802.1X defines\n port-based, network access control, and it is used to provide\n authenticated network access for Ethernet, Token Ring, and Wireless\n LANs (WLANs) [802.11].\n\n Automated selection of certificates for PPP and IEEE 802.1X clients\n is highly desirable. By using certificate extensions to identify the\n intended environment for a particular certificate, the need for user\n input is minimized. Further, the certificate extensions facilitate\n the sepa","scope_keywords":["3770","attribute","attributes","authentication","certificate","certificates","issuer","key","pki","profile","signature","signatures","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null}],"search_text":"IETF RFC 3770 This document defines two EAP extended key usage values and a public\n key certificate extension to carry Wireless LAN (WLAN) System Service\n identifiers (SSIDs).\n\n1. Introduction\n\n Several Extensible Authentication Protocol (EAP) [EAP] authentication\n methods employ X.509 public key certificates. For example, EAP-TLS\n [EAP-TLS] can be used with PPP [PPP] as well as IEEE 802.1X [802.1X].\n PPP is used for dial-up and VPN environments. IEEE 802.1X defines\n port-based, network access control, and it is used to provide\n authenticated network access for Ethernet, Token Ring, and Wireless\n LANs (WLANs) [802.11].\n\n Automated selection of certificates for PPP and IEEE 802.1X clients\n is highly desirable. By using certificate extensions to identify the\n intended environment for a particular certificate, the need for user\n input is minimized. Further, the certificate extensions facilitate\n the sepa 3770 attribute attributes authentication certificate certificates issuer key pki profile signature signatures tls tsp nested-reference unchanged"},{"id":"IETF RFC 3821","type":"specification","body":"IETF","designation":"RFC 3821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3821.txt","https://www.rfc-editor.org/rfc/rfc3821.pdf"],"folder":"IETF/RFC-3821","files":{"txt":{"path":"standards/IETF/RFC-3821/RFC-3821.txt","sha256":"a60ca9c96d2aa56cc619fd12b88fb462e815e9f3b73b8300755138bdd8b4bfef"}},"tags":["nested-reference","unchanged"],"summary":"Fibre Channel Over TCP/IP (FCIP) describes mechanisms that allow the\n interconnection of islands of Fibre Channel storage area networks\n over IP-based networks to form a unified storage area network in a\n single Fibre Channel fabric. FCIP relies on IP-based network\n services to provide the connectivity between the storage area network\n islands over local area networks, metropolitan area networks, or wide\n area networks.","scope_keywords":["3821","algorithm","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 3821 Fibre Channel Over TCP/IP (FCIP) describes mechanisms that allow the\n interconnection of islands of Fibre Channel storage area networks\n over IP-based networks to form a unified storage area network in a\n single Fibre Channel fabric. FCIP relies on IP-based network\n services to provide the connectivity between the storage area network\n islands over local area networks, metropolitan area networks, or wide\n area networks. 3821 algorithm authentication key management nested-reference unchanged"},{"id":"IETF RFC 4017","type":"specification","body":"IETF","designation":"RFC 4017","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4017.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4017.txt","https://www.rfc-editor.org/rfc/rfc4017.pdf"],"folder":"IETF/RFC-4017","files":{"txt":{"path":"standards/IETF/RFC-4017/RFC-4017.txt","sha256":"22a3a115d6b577d81dab345218476fab3daa8ecbc8f8aec536a1987138af00b5"}},"tags":["nested-reference","unchanged"],"summary":"The IEEE 802.11i MAC Security Enhancements Amendment makes use of\n IEEE 802.1X, which in turn relies on the Extensible Authentication\n Protocol (EAP). This document defines requirements for EAP methods\n used in IEEE 802.11 wireless LAN deployments. The material in this\n document has been approved by IEEE 802.11 and is being presented as\n an IETF RFC for informational purposes.","scope_keywords":["4017","authentication","certificate","certificates","credential","credentials","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 4017 The IEEE 802.11i MAC Security Enhancements Amendment makes use of\n IEEE 802.1X, which in turn relies on the Extensible Authentication\n Protocol (EAP). This document defines requirements for EAP methods\n used in IEEE 802.11 wireless LAN deployments. The material in this\n document has been approved by IEEE 802.11 and is being presented as\n an IETF RFC for informational purposes. 4017 authentication certificate certificates credential credentials key management tls nested-reference unchanged"},{"id":"IETF RFC 4026","type":"specification","body":"IETF","designation":"RFC 4026","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4026.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4026.txt","https://www.rfc-editor.org/rfc/rfc4026.pdf"],"folder":"IETF/RFC-4026","files":{"txt":{"path":"standards/IETF/RFC-4026/RFC-4026.txt","sha256":"2699d9b3c82bae24b59bd615995109f0ddc7d7c60b45909ac7bace7224c0ba5f"}},"tags":["nested-reference","unchanged"],"summary":"The widespread interest in provider-provisioned Virtual Private\n Network (VPN) solutions lead to memos proposing different and\n overlapping solutions. The IETF working groups (first Provider\n Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have\n discussed these proposals and documented specifications. This has\n lead to the development of a partially new set of concepts used to\n describe the set of VPN services.\n\n To a certain extent, more than one term covers the same concept, and\n sometimes the same term covers more than one concept. This document\n seeks to make the terminology in the area clearer and more intuitive.","scope_keywords":["4026","qualified","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null}],"search_text":"IETF RFC 4026 The widespread interest in provider-provisioned Virtual Private\n Network (VPN) solutions lead to memos proposing different and\n overlapping solutions. The IETF working groups (first Provider\n Provisioned VPNs and later Layer 2 VPNs and Layer 3 VPNs) have\n discussed these proposals and documented specifications. This has\n lead to the development of a partially new set of concepts used to\n describe the set of VPN services.\n\n To a certain extent, more than one term covers the same concept, and\n sometimes the same term covers more than one concept. This document\n seeks to make the terminology in the area clearer and more intuitive. 4026 qualified tls nested-reference unchanged"},{"id":"IETF RFC 4137","type":"specification","body":"IETF","designation":"RFC 4137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4137.txt","https://www.rfc-editor.org/rfc/rfc4137.pdf"],"folder":"IETF/RFC-4137","files":{"pdf":{"path":"standards/IETF/RFC-4137/RFC-4137.pdf","sha256":"be87ec5633cab4ade2050b31b6cd06f8abb9d5d3b16f2c0466541f31b84fc573"},"txt":{"path":"standards/IETF/RFC-4137/RFC-4137.txt","sha256":"e9a70e675f27b80259665bdc2a11e8f0adbbdbe173bba3839aa64c9346d18f7b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of state machines for Extensible\n Authentication Protocol (EAP) peer, EAP stand-alone authenticator\n (non-pass-through), EAP backend authenticator (for use on\n Authentication, Authorization, and Accounting (AAA) servers), and EAP\n full authenticator (for both local and pass-through). This set of\n state machines shows how EAP can be implemented to support deployment\n in either a peer/authenticator or peer/authenticator/AAA Server\n environment. The peer and stand-alone authenticator machines are\n illustrative of how the EAP protocol defined in RFC 3748 may be\n implemented. The backend and full/pass-through authenticators\n illustrate how EAP/AAA protocol support defined in RFC 3579 may be\n implemented. Where there are differences, RFC 3748 and RFC 3579 are\n authoritative.\n\n The state machines are based on the EAP \"Switch\" model. This model\n includes events and ","scope_keywords":["4137","authentication","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 4137 This document describes a set of state machines for Extensible\n Authentication Protocol (EAP) peer, EAP stand-alone authenticator\n (non-pass-through), EAP backend authenticator (for use on\n Authentication, Authorization, and Accounting (AAA) servers), and EAP\n full authenticator (for both local and pass-through). This set of\n state machines shows how EAP can be implemented to support deployment\n in either a peer/authenticator or peer/authenticator/AAA Server\n environment. The peer and stand-alone authenticator machines are\n illustrative of how the EAP protocol defined in RFC 3748 may be\n implemented. The backend and full/pass-through authenticators\n illustrate how EAP/AAA protocol support defined in RFC 3579 may be\n implemented. Where there are differences, RFC 3748 and RFC 3579 are\n authoritative.\n\n The state machines are based on the EAP \"Switch\" model. This model\n includes events and  4137 authentication authorization nested-reference unchanged"},{"id":"IETF RFC 4149","type":"specification","body":"IETF","designation":"RFC 4149","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4149.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4149.txt","https://www.rfc-editor.org/rfc/rfc4149.pdf"],"folder":"IETF/RFC-4149","files":{"txt":{"path":"standards/IETF/RFC-4149/RFC-4149.txt","sha256":"740308903dbf9a264c8930cbff1eb667db3f0cdd8f0ecac1d1a0f2e3085cbc5a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects for configuring Synthetic Sources\n for Performance Monitoring (SSPM) algorithms.\n\nKalbfleisch, et al. Standards Track [Page 1]\n\f\nRFC 4149 SSPM-MIB August 2005","scope_keywords":["4149","algorithm","algorithms","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IETF RFC 4149 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects for configuring Synthetic Sources\n for Performance Monitoring (SSPM) algorithms.\n\nKalbfleisch, et al. Standards Track [Page 1]\n\f\nRFC 4149 SSPM-MIB August 2005 4149 algorithm algorithms key management path nested-reference unchanged"},{"id":"IETF RFC 4188","type":"specification","body":"IETF","designation":"RFC 4188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4188.txt","https://www.rfc-editor.org/rfc/rfc4188.pdf"],"folder":"IETF/RFC-4188","files":{"txt":{"path":"standards/IETF/RFC-4188/RFC-4188.txt","sha256":"f85ce6fb0b5829a4aadc05d94b50c7e44c65dd9caa6936b3cd2ac48eb0b7af5a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing MAC bridges based on\n the IEEE 802.1D-1998 standard between Local Area Network (LAN)\n segments. Provisions are made for the support of transparent\n bridging. Provisions are also made so that these objects apply to\n bridges connected by subnetworks other than LAN segments.\n\n The MIB module presented in this memo is a translation of the\n BRIDGE-MIB defined in RFC 1493 to the SMIv2 syntax.\n\n This memo obsoletes RFC 1493.\n\nNorseth & Bell, Eds. Standards Track [Page 1]\n\f\nRFC 4188 Bridge MIB September 2005","scope_keywords":["4188","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 4188 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing MAC bridges based on\n the IEEE 802.1D-1998 standard between Local Area Network (LAN)\n segments. Provisions are made for the support of transparent\n bridging. Provisions are also made so that these objects apply to\n bridges connected by subnetworks other than LAN segments.\n\n The MIB module presented in this memo is a translation of the\n BRIDGE-MIB defined in RFC 1493 to the SMIv2 syntax.\n\n This memo obsoletes RFC 1493.\n\nNorseth & Bell, Eds. Standards Track [Page 1]\n\f\nRFC 4188 Bridge MIB September 2005 4188 key management path nested-reference unchanged"},{"id":"IETF RFC 4318","type":"specification","body":"IETF","designation":"RFC 4318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4318.txt","https://www.rfc-editor.org/rfc/rfc4318.pdf"],"folder":"IETF/RFC-4318","files":{"txt":{"path":"standards/IETF/RFC-4318/RFC-4318.txt","sha256":"01edb7558bc81c465649824e1dc9a71495cd5357bca938e4f3a74f73c63d38b9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an SMIv2 MIB module for managing the Rapid Spanning\n Tree capability defined by the IEEE P802.1t and P802.1w amendments to\n IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)\n segments. The objects in this MIB are defined to apply both to\n transparent bridging and to bridges connected by subnetworks other\n than LAN segments.","scope_keywords":["4318","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4318 This memo defines an SMIv2 MIB module for managing the Rapid Spanning\n Tree capability defined by the IEEE P802.1t and P802.1w amendments to\n IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)\n segments. The objects in this MIB are defined to apply both to\n transparent bridging and to bridges connected by subnetworks other\n than LAN segments. 4318 management path pid nested-reference unchanged"},{"id":"IETF RFC 4448","type":"specification","body":"IETF","designation":"RFC 4448","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4448.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4448.txt","https://www.rfc-editor.org/rfc/rfc4448.pdf"],"folder":"IETF/RFC-4448","files":{"txt":{"path":"standards/IETF/RFC-4448/RFC-4448.txt","sha256":"b90e2927f0ed24d241eec3d7bc2b73e5a54a1e807a39e62c72283f27f3e9eb71"}},"tags":["nested-reference","unchanged"],"summary":"An Ethernet pseudowire (PW) is used to carry Ethernet/802.3 Protocol\n Data Units (PDUs) over an MPLS network. This enables service\n providers to offer \"emulated\" Ethernet services over existing MPLS\n networks. This document specifies the encapsulation of\n Ethernet/802.3 PDUs within a pseudowire. It also specifies the\n procedures for using a PW to provide a \"point-to-point Ethernet\"\n service.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4448 Encapsulation of Ethernet over MPLS April 2006","scope_keywords":["4448","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 4448 An Ethernet pseudowire (PW) is used to carry Ethernet/802.3 Protocol\n Data Units (PDUs) over an MPLS network. This enables service\n providers to offer \"emulated\" Ethernet services over existing MPLS\n networks. This document specifies the encapsulation of\n Ethernet/802.3 PDUs within a pseudowire. It also specifies the\n procedures for using a PW to provide a \"point-to-point Ethernet\"\n service.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4448 Encapsulation of Ethernet over MPLS April 2006 4448 management nested-reference unchanged"},{"id":"IETF RFC 4504","type":"specification","body":"IETF","designation":"RFC 4504","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4504.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4504.txt","https://www.rfc-editor.org/rfc/rfc4504.pdf"],"folder":"IETF/RFC-4504","files":{"txt":{"path":"standards/IETF/RFC-4504/RFC-4504.txt","sha256":"7e40e43139562b47ef7190b818a4d3fdae9dbfbec7e9d7cee1e8dc3093d5e9f3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the requirements for SIP telephony devices,\n based on the deployment experience of large numbers of SIP phones and\n PC clients using different implementations in various networks. The\n objectives of the requirements are a well-defined set of\n interoperability and multi-vendor-supported core features, so as to\n enable similar ease of purchase, installation, and operation as found\n for PCs, PDAs, analog feature phones or mobile phones.\n\n We present a glossary of the most common settings and some of the\n more widely used values for some settings.","scope_keywords":["4504","authentication","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null}],"search_text":"IETF RFC 4504 This document describes the requirements for SIP telephony devices,\n based on the deployment experience of large numbers of SIP phones and\n PC clients using different implementations in various networks. The\n objectives of the requirements are a well-defined set of\n interoperability and multi-vendor-supported core features, so as to\n enable similar ease of purchase, installation, and operation as found\n for PCs, PDAs, analog feature phones or mobile phones.\n\n We present a glossary of the most common settings and some of the\n more widely used values for some settings. 4504 authentication key management presentation nested-reference unchanged"},{"id":"IETF RFC 4554","type":"specification","body":"IETF","designation":"RFC 4554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4554.txt","https://www.rfc-editor.org/rfc/rfc4554.pdf"],"folder":"IETF/RFC-4554","files":{"txt":{"path":"standards/IETF/RFC-4554/RFC-4554.txt","sha256":"c69a584e06c6458d9ae770786fb2fc7ac263c5b8c3020dea8dd31e6b9953fe84"}},"tags":["nested-reference","unchanged"],"summary":"Ethernet VLANs are quite commonly used in enterprise networks for the\n purposes of traffic segregation. This document describes how such\n VLANs can be readily used to deploy IPv6 networking in an enterprise,\n which focuses on the scenario of early deployment prior to\n availability of IPv6-capable switch-router equipment. In this\n method, IPv6 may be routed in parallel with the existing IPv4 in the\n enterprise and delivered at Layer 2 via VLAN technology. The IPv6\n connectivity to the enterprise may or may not enter the site via the\n same physical link.","scope_keywords":["4554","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 501","folder":"IETF/RFC-501","source":"IETF/RFC-501/RFC-501.txt","version":null}],"search_text":"IETF RFC 4554 Ethernet VLANs are quite commonly used in enterprise networks for the\n purposes of traffic segregation. This document describes how such\n VLANs can be readily used to deploy IPv6 networking in an enterprise,\n which focuses on the scenario of early deployment prior to\n availability of IPv6-capable switch-router equipment. In this\n method, IPv6 may be routed in parallel with the existing IPv4 in the\n enterprise and delivered at Layer 2 via VLAN technology. The IPv6\n connectivity to the enterprise may or may not enter the site via the\n same physical link. 4554 policy nested-reference unchanged"},{"id":"IETF RFC 4664","type":"specification","body":"IETF","designation":"RFC 4664","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4664.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4664.txt","https://www.rfc-editor.org/rfc/rfc4664.pdf"],"folder":"IETF/RFC-4664","files":{"txt":{"path":"standards/IETF/RFC-4664/RFC-4664.txt","sha256":"e372533a0d01f5a0d7dcbc81a6323cefc9857aa7a574eeb6999a4d15521a002f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for Layer 2 Provider Provisioned\n Virtual Private Networks (L2VPNs). This framework is intended to aid\n in standardizing protocols and mechanisms to support interoperable\n L2VPNs.\n\nAndersson & Rosen Informational [Page 1]\n\f\nRFC 4664 Framework for Layer 2 VPNs September 2006","scope_keywords":["4664","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4667","folder":"IETF/RFC-4667","source":"IETF/RFC-4667/RFC-4667.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 4664 This document provides a framework for Layer 2 Provider Provisioned\n Virtual Private Networks (L2VPNs). This framework is intended to aid\n in standardizing protocols and mechanisms to support interoperable\n L2VPNs.\n\nAndersson & Rosen Informational [Page 1]\n\f\nRFC 4664 Framework for Layer 2 VPNs September 2006 4664 key management nested-reference unchanged"},{"id":"IETF RFC 4665","type":"specification","body":"IETF","designation":"RFC 4665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4665.txt","https://www.rfc-editor.org/rfc/rfc4665.pdf"],"folder":"IETF/RFC-4665","files":{"txt":{"path":"standards/IETF/RFC-4665/RFC-4665.txt","sha256":"18b1073d9e420425fa0beee1cf4fbacb08ff0ba8856ebaa10c624b12071bf077"}},"tags":["nested-reference","unchanged"],"summary":"This document provides requirements for Layer 2 Provider-Provisioned\n Virtual Private Networks (L2VPNs). It first provides taxonomy and\n terminology and states generic and general service requirements. It\n covers point-to-point VPNs, referred to as Virtual Private Wire\n Service (VPWS), as well as multipoint-to-multipoint VPNs, also known\n as Virtual Private LAN Service (VPLS). Detailed requirements are\n expressed from both a customer as well as a service provider\n perspectives.\n\nAugustyn & Serbest Informational [Page 1]\n\f\nRFC 4665 Service Requirements for L2VPNs September 2006","scope_keywords":["4665","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null}],"search_text":"IETF RFC 4665 This document provides requirements for Layer 2 Provider-Provisioned\n Virtual Private Networks (L2VPNs). It first provides taxonomy and\n terminology and states generic and general service requirements. It\n covers point-to-point VPNs, referred to as Virtual Private Wire\n Service (VPWS), as well as multipoint-to-multipoint VPNs, also known\n as Virtual Private LAN Service (VPLS). Detailed requirements are\n expressed from both a customer as well as a service provider\n perspectives.\n\nAugustyn & Serbest Informational [Page 1]\n\f\nRFC 4665 Service Requirements for L2VPNs September 2006 4665 management nested-reference unchanged"},{"id":"IETF RFC 4679","type":"specification","body":"IETF","designation":"RFC 4679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4679.txt","https://www.rfc-editor.org/rfc/rfc4679.pdf"],"folder":"IETF/RFC-4679","files":{"txt":{"path":"standards/IETF/RFC-4679/RFC-4679.txt","sha256":"a080900d808e0ad4bcebfb3a21b1a5aabb6ba2bb98d59176619d328d1daf8839"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the set of Remote Authentication Dial-In User\n Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL\n Forum.\n\n These attributes are designed to transport Digital Subscriber Line\n (DSL) information that is not supported by the standard RADIUS\n attribute set. It is expected that this document will be updated if\n and when the DSL Forum defines additional vendor-specific attributes,\n since its primary purpose is to provide a reference for DSL equipment\n vendors wishing to interoperate with other vendors' products.\n\nMammoliti, et al. Informational [Page 1]\n\f\nRFC 4679 DSL Forum RADIUS VSA September 2006","scope_keywords":["4679","attribute","attributes","authentication","identification","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null}],"search_text":"IETF RFC 4679 This document describes the set of Remote Authentication Dial-In User\n Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL\n Forum.\n\n These attributes are designed to transport Digital Subscriber Line\n (DSL) information that is not supported by the standard RADIUS\n attribute set. It is expected that this document will be updated if\n and when the DSL Forum defines additional vendor-specific attributes,\n since its primary purpose is to provide a reference for DSL equipment\n vendors wishing to interoperate with other vendors' products.\n\nMammoliti, et al. Informational [Page 1]\n\f\nRFC 4679 DSL Forum RADIUS VSA September 2006 4679 attribute attributes authentication identification key management policies policy nested-reference unchanged"},{"id":"IETF RFC 4710","type":"specification","body":"IETF","designation":"RFC 4710","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4710.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4710.txt","https://www.rfc-editor.org/rfc/rfc4710.pdf"],"folder":"IETF/RFC-4710","files":{"txt":{"path":"standards/IETF/RFC-4710/RFC-4710.txt","sha256":"0fe41320fd47461a74588963cfc1a034c205a99658841387b028132e1cbbeb68"}},"tags":["nested-reference","unchanged"],"summary":"There is a need to monitor end-devices such as IP phones, pagers,\n Instant Messaging clients, mobile phones, and various other handheld\n computing devices. This memo extends the remote network monitoring\n (RMON) family of specifications to allow real-time quality-of-service\n (QoS) monitoring of various applications that run on these devices\n and allows this information to be integrated with the RMON family\n using the Simple Network Management Protocol (SNMP). This memo\n defines the framework, architecture, relevant metrics, and transport\n requirements for real-time QoS monitoring of applications.","scope_keywords":["4710","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4710 There is a need to monitor end-devices such as IP phones, pagers,\n Instant Messaging clients, mobile phones, and various other handheld\n computing devices. This memo extends the remote network monitoring\n (RMON) family of specifications to allow real-time quality-of-service\n (QoS) monitoring of various applications that run on these devices\n and allows this information to be integrated with the RMON family\n using the Simple Network Management Protocol (SNMP). This memo\n defines the framework, architecture, relevant metrics, and transport\n requirements for real-time QoS monitoring of applications. 4710 management nested-reference unchanged"},{"id":"IETF RFC 4712","type":"specification","body":"IETF","designation":"RFC 4712","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4712.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4712.txt","https://www.rfc-editor.org/rfc/rfc4712.pdf"],"folder":"IETF/RFC-4712","files":{"txt":{"path":"standards/IETF/RFC-4712/RFC-4712.txt","sha256":"88e3e84bc6a78cf16f00e3031adb5c926580f68c00faba5e42f1a93b28294c93"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies two transport mappings of the Real-Time\n Application Quality-of-Service Monitoring (RAQMON) information model\n defined in RFC 4710 using TCP as a native transport and the Simple\n Network Management Protocol (SNMP) to carry the RAQMON information\n from a RAQMON Data Source (RDS) to a RAQMON Report Collector (RRC).\n\nSiddiqui, et al. Standards Track [Page 1]\n\f\nRFC 4712 Transport Mappings for RAQMON PDU October 2006","scope_keywords":["4712","authorization","http","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4712 This memo specifies two transport mappings of the Real-Time\n Application Quality-of-Service Monitoring (RAQMON) information model\n defined in RFC 4710 using TCP as a native transport and the Simple\n Network Management Protocol (SNMP) to carry the RAQMON information\n from a RAQMON Data Source (RDS) to a RAQMON Report Collector (RRC).\n\nSiddiqui, et al. Standards Track [Page 1]\n\f\nRFC 4712 Transport Mappings for RAQMON PDU October 2006 4712 authorization http key management tls nested-reference unchanged"},{"id":"IETF RFC 4719","type":"specification","body":"IETF","designation":"RFC 4719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4719.txt","https://www.rfc-editor.org/rfc/rfc4719.pdf"],"folder":"IETF/RFC-4719","files":{"txt":{"path":"standards/IETF/RFC-4719/RFC-4719.txt","sha256":"eda6047693c7842aa4be06ab453a82b70870471751db273f55e2369ecd885c1a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the transport of Ethernet frames over the\n Layer 2 Tunneling Protocol, Version 3 (L2TPv3). This includes the\n transport of Ethernet port-to-port frames as well as the transport of\n Ethernet VLAN frames. The mechanism described in this document can\n be used in the creation of Pseudowires to transport Ethernet frames\n over an IP network.\n\nAggarwal, et al. Standards Track [Page 1]\n\f\nRFC 4719 Transport of Ethernet Frames over L2TPv3 November 2006","scope_keywords":["4719","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null}],"search_text":"IETF RFC 4719 This document describes the transport of Ethernet frames over the\n Layer 2 Tunneling Protocol, Version 3 (L2TPv3). This includes the\n transport of Ethernet port-to-port frames as well as the transport of\n Ethernet VLAN frames. The mechanism described in this document can\n be used in the creation of Pseudowires to transport Ethernet frames\n over an IP network.\n\nAggarwal, et al. Standards Track [Page 1]\n\f\nRFC 4719 Transport of Ethernet Frames over L2TPv3 November 2006 4719 key trust nested-reference unchanged"},{"id":"IETF RFC 4779","type":"specification","body":"IETF","designation":"RFC 4779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4779.txt","https://www.rfc-editor.org/rfc/rfc4779.pdf"],"folder":"IETF/RFC-4779","files":{"txt":{"path":"standards/IETF/RFC-4779/RFC-4779.txt","sha256":"967b3c62a8f365e670b7526bb6318747a49353cbd27911d1fab1bd2b04293158"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a detailed description of IPv6 deployment and\n integration methods and scenarios in today's Service Provider (SP)\n Broadband (BB) networks in coexistence with deployed IPv4 services.\n Cable/HFC, BB Ethernet, xDSL, and WLAN are the main BB technologies\n that are currently deployed, and discussed in this document. The\n emerging Broadband Power Line Communications (PLC/BPL) access\n technology is also discussed for completeness. In this document we\n will discuss main components of IPv6 BB networks, their differences\n from IPv4 BB networks, and how IPv6 is deployed and integrated in\n each of these networks using tunneling mechanisms and native IPv6.\n\nAsadullah, et al. Informational [Page 1]\n\f\nRFC 4779 ISP IPv6 Deployment Scenarios in BB January 2007","scope_keywords":["4779","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null}],"search_text":"IETF RFC 4779 This document provides a detailed description of IPv6 deployment and\n integration methods and scenarios in today's Service Provider (SP)\n Broadband (BB) networks in coexistence with deployed IPv4 services.\n Cable/HFC, BB Ethernet, xDSL, and WLAN are the main BB technologies\n that are currently deployed, and discussed in this document. The\n emerging Broadband Power Line Communications (PLC/BPL) access\n technology is also discussed for completeness. In this document we\n will discuss main components of IPv6 BB networks, their differences\n from IPv4 BB networks, and how IPv6 is deployed and integrated in\n each of these networks using tunneling mechanisms and native IPv6.\n\nAsadullah, et al. Informational [Page 1]\n\f\nRFC 4779 ISP IPv6 Deployment Scenarios in BB January 2007 4779 management trust nested-reference unchanged"},{"id":"IETF RFC 4793","type":"specification","body":"IETF","designation":"RFC 4793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4793.txt","https://www.rfc-editor.org/rfc/rfc4793.pdf"],"folder":"IETF/RFC-4793","files":{"txt":{"path":"standards/IETF/RFC-4793/RFC-4793.txt","sha256":"b403a03e7c08227e99e7da97ad419208f9547e962abdf7c38b76215ed3ea7c67"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general Extensible Authentication Protocol\n (EAP) method suitable for use with One-Time Password (OTP) tokens,\n and offers particular advantages for tokens with direct electronic\n interfaces to their associated clients. The method can be used to\n provide unilateral or mutual authentication, and key material, in\n protocols utilizing EAP, such as PPP, IEEE 802.1X, and Internet Key\n Exchange Protocol Version 2 (IKEv2).\n\nNystroem Informational [Page 1]\n\f\nRFC 4793 EAP-POTP February 2007","scope_keywords":["4793","algorithm","algorithms","attribute","attributes","authentication","hash","key","management","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null}],"search_text":"IETF RFC 4793 This document describes a general Extensible Authentication Protocol\n (EAP) method suitable for use with One-Time Password (OTP) tokens,\n and offers particular advantages for tokens with direct electronic\n interfaces to their associated clients. The method can be used to\n provide unilateral or mutual authentication, and key material, in\n protocols utilizing EAP, such as PPP, IEEE 802.1X, and Internet Key\n Exchange Protocol Version 2 (IKEv2).\n\nNystroem Informational [Page 1]\n\f\nRFC 4793 EAP-POTP February 2007 4793 algorithm algorithms attribute attributes authentication hash key management profile trust nested-reference unchanged"},{"id":"IETF RFC 4835","type":"specification","body":"IETF","designation":"RFC 4835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4835.txt","https://www.rfc-editor.org/rfc/rfc4835.pdf"],"folder":"IETF/RFC-4835","files":{"txt":{"path":"standards/IETF/RFC-4835/RFC-4835.txt","sha256":"814aaa6a798b5db31e05fc7e022d04413acee1678deb3d53f20dd23291c6353d"}},"tags":["nested-reference","unchanged"],"summary":"The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Encapsulating\n Security Payload (ESP) and the Authentication Header (AH) provide two\n mechanisms for protecting data being sent over an IPsec Security\n Association (SA). To ensure interoperability between disparate\n implementations, it is necessary to specify a set of mandatory-to-\n implement algorithms to ensure that there is at least one algorithm\n that all implementations will have available. This document defines\n the current set of mandatory-to-implement algorithms for ESP and AH\n as well as specifying algorithms that should be implemented because\n they may be promoted to mandatory at some future time.\n\nManral Standards Track [Page 1]\n\f\nRFC 4835 Cryptographic Algorithms ESP and AH April 2007","scope_keywords":["4835","algorithm","algorithms","authentication","encryption","key","keys","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 4835 The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Encapsulating\n Security Payload (ESP) and the Authentication Header (AH) provide two\n mechanisms for protecting data being sent over an IPsec Security\n Association (SA). To ensure interoperability between disparate\n implementations, it is necessary to specify a set of mandatory-to-\n implement algorithms to ensure that there is at least one algorithm\n that all implementations will have available. This document defines\n the current set of mandatory-to-implement algorithms for ESP and AH\n as well as specifying algorithms that should be implemented because\n they may be promoted to mandatory at some future time.\n\nManral Standards Track [Page 1]\n\f\nRFC 4835 Cryptographic Algorithms ESP and AH April 2007 4835 algorithm algorithms authentication encryption key keys subject trust nested-reference unchanged"},{"id":"IETF RFC 4849","type":"specification","body":"IETF","designation":"RFC 4849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4849.txt","https://www.rfc-editor.org/rfc/rfc4849.pdf"],"folder":"IETF/RFC-4849","files":{"txt":{"path":"standards/IETF/RFC-4849/RFC-4849.txt","sha256":"e90ffe6d4b3fd9466dcc887659d1a96908e51c49593d5433f4fb2f60b2eca3f9"}},"tags":["nested-reference","unchanged"],"summary":"While RFC 2865 defines the Filter-Id attribute, it requires that the\n Network Access Server (NAS) be pre-populated with the desired\n filters. However, in situations where the server operator does not\n know which filters have been pre-populated, it is useful to specify\n filter rules explicitly. This document defines the NAS-Filter-Rule\n attribute within the Remote Authentication Dial In User Service\n (RADIUS). This attribute is based on the Diameter NAS-Filter-Rule\n Attribute Value Pair (AVP) described in RFC 4005, and the\n IPFilterRule syntax defined in RFC 3588.\n\nCongdon, et al. Standards Track [Page 1]\n\f\nRFC 4849 Filter Rule Attribute April 2007","scope_keywords":["4849","attribute","attributes","authentication","authorization","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null}],"search_text":"IETF RFC 4849 While RFC 2865 defines the Filter-Id attribute, it requires that the\n Network Access Server (NAS) be pre-populated with the desired\n filters. However, in situations where the server operator does not\n know which filters have been pre-populated, it is useful to specify\n filter rules explicitly. This document defines the NAS-Filter-Rule\n attribute within the Remote Authentication Dial In User Service\n (RADIUS). This attribute is based on the Diameter NAS-Filter-Rule\n Attribute Value Pair (AVP) described in RFC 4005, and the\n IPFilterRule syntax defined in RFC 3588.\n\nCongdon, et al. Standards Track [Page 1]\n\f\nRFC 4849 Filter Rule Attribute April 2007 4849 attribute attributes authentication authorization key trust nested-reference unchanged"},{"id":"IETF RFC 4851","type":"specification","body":"IETF","designation":"RFC 4851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4851.txt","https://www.rfc-editor.org/rfc/rfc4851.pdf"],"folder":"IETF/RFC-4851","files":{"txt":{"path":"standards/IETF/RFC-4851/RFC-4851.txt","sha256":"52b8953fe1ba8cd479621d7b6eb9b23e6ad798329e36aaad51fc5cf10d59e5ff"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Extensible Authentication Protocol (EAP)\n based Flexible Authentication via Secure Tunneling (EAP-FAST)\n protocol. EAP-FAST is an EAP method that enables secure\n communication between a peer and a server by using the Transport\n Layer Security (TLS) to establish a mutually authenticated tunnel.\n Within the tunnel, Type-Length-Value (TLV) objects are used to convey\n authentication related data between the peer and the EAP server.\n\nCam-Winget, et al. Informational [Page 1]\n\f\nRFC 4851 EAP-FAST May 2007","scope_keywords":["4851","authentication","certificate","credential","credentials","key","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 4851 This document defines the Extensible Authentication Protocol (EAP)\n based Flexible Authentication via Secure Tunneling (EAP-FAST)\n protocol. EAP-FAST is an EAP method that enables secure\n communication between a peer and a server by using the Transport\n Layer Security (TLS) to establish a mutually authenticated tunnel.\n Within the tunnel, Type-Length-Value (TLV) objects are used to convey\n authentication related data between the peer and the EAP server.\n\nCam-Winget, et al. Informational [Page 1]\n\f\nRFC 4851 EAP-FAST May 2007 4851 authentication certificate credential credentials key tls trust validation nested-reference unchanged"},{"id":"IETF RFC 4852","type":"specification","body":"IETF","designation":"RFC 4852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4852.txt","https://www.rfc-editor.org/rfc/rfc4852.pdf"],"folder":"IETF/RFC-4852","files":{"txt":{"path":"standards/IETF/RFC-4852/RFC-4852.txt","sha256":"9c720e7a6c875f979c7b3127485ea057af769a19abb0bbadb2011b5cdd3a3cc0"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes the transition to IPv6 in enterprise networks\n focusing on IP Layer 3. These networks are characterized as having\n multiple internal links and one or more router connections to one or\n more Providers, and as being managed by a network operations entity.\n The analysis focuses on a base set of transition notational networks\n and requirements expanded from a previous document on enterprise\n scenarios. Discussion is provided on a focused set of transition\n analysis required for the enterprise to transition to IPv6, assuming\n a Dual-IP layer (IPv4 and IPv6) network and node environment within\n the enterprise. Then, a set of transition mechanisms are recommended\n for each notational network.\n\nBound, et al. Informational [Page 1]\n\f\nRFC 4852 IPv6 Enterprise Network Analysis April 2007","scope_keywords":["4852","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null}],"search_text":"IETF RFC 4852 This document analyzes the transition to IPv6 in enterprise networks\n focusing on IP Layer 3. These networks are characterized as having\n multiple internal links and one or more router connections to one or\n more Providers, and as being managed by a network operations entity.\n The analysis focuses on a base set of transition notational networks\n and requirements expanded from a previous document on enterprise\n scenarios. Discussion is provided on a focused set of transition\n analysis required for the enterprise to transition to IPv6, assuming\n a Dual-IP layer (IPv4 and IPv6) network and node environment within\n the enterprise. Then, a set of transition mechanisms are recommended\n for each notational network.\n\nBound, et al. Informational [Page 1]\n\f\nRFC 4852 IPv6 Enterprise Network Analysis April 2007 4852 management trust nested-reference unchanged"},{"id":"IETF RFC 4903","type":"specification","body":"IETF","designation":"RFC 4903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4903.txt","https://www.rfc-editor.org/rfc/rfc4903.pdf"],"folder":"IETF/RFC-4903","files":{"txt":{"path":"standards/IETF/RFC-4903/RFC-4903.txt","sha256":"5a111e7b97e380c5738533e615dce476f57b701a9667df46c6bf7308fb93b1a6"}},"tags":["nested-reference","unchanged"],"summary":"There have been several proposals around the notion that a subnet may\n span multiple links connected by routers. This memo documents the\n issues and potential problems that have been raised with such an\n approach.","scope_keywords":["4903","key","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null}],"search_text":"IETF RFC 4903 There have been several proposals around the notion that a subnet may\n span multiple links connected by routers. This memo documents the\n issues and potential problems that have been raised with such an\n approach. 4903 key pid trust nested-reference unchanged"},{"id":"IETF RFC 4942","type":"specification","body":"IETF","designation":"RFC 4942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4942.txt","https://www.rfc-editor.org/rfc/rfc4942.pdf"],"folder":"IETF/RFC-4942","files":{"txt":{"path":"standards/IETF/RFC-4942/RFC-4942.txt","sha256":"3ce121a87b663661ac14b4907f639ee174a375031c4bbdbbb368975f997c5e5e"}},"tags":["nested-reference","unchanged"],"summary":"The transition from a pure IPv4 network to a network where IPv4 and\n IPv6 coexist brings a number of extra security considerations that\n need to be taken into account when deploying IPv6 and operating the\n dual-protocol network and the associated transition mechanisms. This\n document attempts to give an overview of the various issues grouped\n into three categories:\n o issues due to the IPv6 protocol itself,\n o issues due to transition mechanisms, and\n o issues due to IPv6 deployment.\n\nDavies, et al. Informational [Page 1]\n\f\nRFC 4942 IPv6 Security Overview September 2007","scope_keywords":["4942","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5722","folder":"IETF/RFC-5722","source":"IETF/RFC-5722/RFC-5722.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null}],"search_text":"IETF RFC 4942 The transition from a pure IPv4 network to a network where IPv4 and\n IPv6 coexist brings a number of extra security considerations that\n need to be taken into account when deploying IPv6 and operating the\n dual-protocol network and the associated transition mechanisms. This\n document attempts to give an overview of the various issues grouped\n into three categories:\n o issues due to the IPv6 protocol itself,\n o issues due to transition mechanisms, and\n o issues due to IPv6 deployment.\n\nDavies, et al. Informational [Page 1]\n\f\nRFC 4942 IPv6 Security Overview September 2007 4942 identification nested-reference unchanged"},{"id":"IETF RFC 4968","type":"specification","body":"IETF","designation":"RFC 4968","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4968.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4968.txt","https://www.rfc-editor.org/rfc/rfc4968.pdf"],"folder":"IETF/RFC-4968","files":{"txt":{"path":"standards/IETF/RFC-4968/RFC-4968.txt","sha256":"1c42c95b6d721808894c8dc35602aefeba48ecb1999055f11b5e073940efcdb0"}},"tags":["nested-reference","unchanged"],"summary":"This document provides different IPv6 link models that are suitable\n for IEEE 802.16 based networks and provides analysis of various\n considerations for each link model and the applicability of each link\n model under different deployment scenarios. This document is the\n result of a design team (DT) that was formed to analyze the IPv6 link\n models for IEEE 802.16 based networks.\n\nMadanapalli Informational [Page 1]\n\f\nRFC 4968 IPv6 Link Models for IEEE 802.16 August 2007","scope_keywords":["4968","authentication","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null}],"search_text":"IETF RFC 4968 This document provides different IPv6 link models that are suitable\n for IEEE 802.16 based networks and provides analysis of various\n considerations for each link model and the applicability of each link\n model under different deployment scenarios. This document is the\n result of a design team (DT) that was formed to analyze the IPv6 link\n models for IEEE 802.16 based networks.\n\nMadanapalli Informational [Page 1]\n\f\nRFC 4968 IPv6 Link Models for IEEE 802.16 August 2007 4968 authentication trust nested-reference unchanged"},{"id":"IETF RFC 5087","type":"specification","body":"IETF","designation":"RFC 5087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5087.txt","https://www.rfc-editor.org/rfc/rfc5087.pdf"],"folder":"IETF/RFC-5087","files":{"txt":{"path":"standards/IETF/RFC-5087/RFC-5087.txt","sha256":"cd6338509411b77869d02ec27e60ab6d4f9be3423512d17866acd7194be96527"}},"tags":["nested-reference","unchanged"],"summary":"Time Division Multiplexing over IP (TDMoIP) is a structure-aware\n method for transporting Time Division Multiplexed (TDM) signals using\n pseudowires (PWs). Being structure-aware, TDMoIP is able to ensure\n TDM structure integrity, and thus withstand network degradations\n better than structure-agnostic transport. Structure-aware methods\n can distinguish individual channels, enabling packet loss concealment\n and bandwidth conservation. Accesibility of TDM signaling\n facilitates mechanisms that exploit or manipulate signaling.\n\nStein, et al. Informational [Page 1]\n\f\nRFC 5087 TDMoIP December 2007","scope_keywords":["5087","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 5087 Time Division Multiplexing over IP (TDMoIP) is a structure-aware\n method for transporting Time Division Multiplexed (TDM) signals using\n pseudowires (PWs). Being structure-aware, TDMoIP is able to ensure\n TDM structure integrity, and thus withstand network degradations\n better than structure-agnostic transport. Structure-aware methods\n can distinguish individual channels, enabling packet loss concealment\n and bandwidth conservation. Accesibility of TDM signaling\n facilitates mechanisms that exploit or manipulate signaling.\n\nStein, et al. Informational [Page 1]\n\f\nRFC 5087 TDMoIP December 2007 5087 hash key nested-reference unchanged"},{"id":"IETF RFC 5110","type":"specification","body":"IETF","designation":"RFC 5110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5110.txt","https://www.rfc-editor.org/rfc/rfc5110.pdf"],"folder":"IETF/RFC-5110","files":{"txt":{"path":"standards/IETF/RFC-5110/RFC-5110.txt","sha256":"fcf3f1559d6cf77714db43c8c3adcc16ce81319c5c4dcd342d3e0cf33202ec95"}},"tags":["nested-reference","unchanged"],"summary":"This document describes multicast routing architectures that are\n currently deployed on the Internet. This document briefly describes\n those protocols and references their specifications.\n\n This memo also reclassifies several older RFCs to Historic. These\n RFCs describe multicast routing protocols that were never widely\n deployed or have fallen into disuse.","scope_keywords":["5110","attribute","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 5110 This document describes multicast routing architectures that are\n currently deployed on the Internet. This document briefly describes\n those protocols and references their specifications.\n\n This memo also reclassifies several older RFCs to Historic. These\n RFCs describe multicast routing protocols that were never widely\n deployed or have fallen into disuse. 5110 attribute management path nested-reference unchanged"},{"id":"IETF RFC 5180","type":"specification","body":"IETF","designation":"RFC 5180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5180.txt","https://www.rfc-editor.org/rfc/rfc5180.pdf"],"folder":"IETF/RFC-5180","files":{"txt":{"path":"standards/IETF/RFC-5180/RFC-5180.txt","sha256":"f62030c5ed82ce7aaa483326f6cc36dde81b876dd5e7fc81de0853147781f3d7"}},"tags":["nested-reference","unchanged"],"summary":"The benchmarking methodologies defined in RFC 2544 are IP version\n independent. However, RFC 2544 does not address some of the\n specificities of IPv6. This document provides additional\n benchmarking guidelines, which in conjunction with RFC 2544, lead to\n a more complete and realistic evaluation of the IPv6 performance of\n network interconnect devices. IPv6 transition mechanisms are outside\n the scope of this document.\n\nPopoviciu, et al. Informational [Page 1]\n\f\nRFC 5180 IPv6 Benchmarking Methodology May 2008","scope_keywords":["5180","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null}],"search_text":"IETF RFC 5180 The benchmarking methodologies defined in RFC 2544 are IP version\n independent. However, RFC 2544 does not address some of the\n specificities of IPv6. This document provides additional\n benchmarking guidelines, which in conjunction with RFC 2544, lead to\n a more complete and realistic evaluation of the IPv6 performance of\n network interconnect devices. IPv6 transition mechanisms are outside\n the scope of this document.\n\nPopoviciu, et al. Informational [Page 1]\n\f\nRFC 5180 IPv6 Benchmarking Methodology May 2008 5180 key management path nested-reference unchanged"},{"id":"IETF RFC 5209","type":"specification","body":"IETF","designation":"RFC 5209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5209.txt","https://www.rfc-editor.org/rfc/rfc5209.pdf"],"folder":"IETF/RFC-5209","files":{"txt":{"path":"standards/IETF/RFC-5209/RFC-5209.txt","sha256":"63d9ac6a7a9495067db04661422f0c3d5521c37481f98bf4bc85a35ed6d43885"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the problem statement, scope, and protocol\n requirements between the components of the NEA (Network Endpoint\n Assessment) reference model. NEA provides owners of networks (e.g.,\n an enterprise offering remote access) a mechanism to evaluate the\n posture of a system. This may take place during the request for\n network access and/or subsequently at any time while connected to the\n network. The learned posture information can then be applied to a\n variety of compliance-oriented decisions. The posture information is\n frequently useful for detecting systems that are lacking or have\n out-of-date security protection mechanisms such as: anti-virus and\n host-based firewall software. In order to provide context for the\n requirements, a reference model and terminology are introduced.\n\nSangster, et al. Informational [Page 1]\n\f\nRFC 5209 NEA Requirements June 2008","scope_keywords":["5209","attribute","attributes","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null}],"search_text":"IETF RFC 5209 This document defines the problem statement, scope, and protocol\n requirements between the components of the NEA (Network Endpoint\n Assessment) reference model. NEA provides owners of networks (e.g.,\n an enterprise offering remote access) a mechanism to evaluate the\n posture of a system. This may take place during the request for\n network access and/or subsequently at any time while connected to the\n network. The learned posture information can then be applied to a\n variety of compliance-oriented decisions. The posture information is\n frequently useful for detecting systems that are lacking or have\n out-of-date security protection mechanisms such as: anti-virus and\n host-based firewall software. In order to provide context for the\n requirements, a reference model and terminology are introduced.\n\nSangster, et al. Informational [Page 1]\n\f\nRFC 5209 NEA Requirements June 2008 5209 attribute attributes policies trust nested-reference unchanged"},{"id":"IETF RFC 5296","type":"specification","body":"IETF","designation":"RFC 5296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5296.txt","https://www.rfc-editor.org/rfc/rfc5296.pdf"],"folder":"IETF/RFC-5296","files":{"txt":{"path":"standards/IETF/RFC-5296/RFC-5296.txt","sha256":"055052bc5008c46e7b88deebbb7f23f4f56afbc6e865670d912d9c67609ab683"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) is a generic framework\n supporting multiple types of authentication methods. In systems\n where EAP is used for authentication, it is desirable to not repeat\n the entire EAP exchange with another authenticator. This document\n specifies extensions to EAP and the EAP keying hierarchy to support\n an EAP method-independent protocol for efficient re-authentication\n between the peer and an EAP re-authentication server through any\n authenticator. The re-authentication server may be in the home\n network or in the local network to which the peer is connecting.\n\nNarayanan & Dondeti Standards Track [Page 1]\n\f\nRFC 5296 ERP August 2008","scope_keywords":["5296","attribute","attributes","authentication","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null}],"search_text":"IETF RFC 5296 The Extensible Authentication Protocol (EAP) is a generic framework\n supporting multiple types of authentication methods. In systems\n where EAP is used for authentication, it is desirable to not repeat\n the entire EAP exchange with another authenticator. This document\n specifies extensions to EAP and the EAP keying hierarchy to support\n an EAP method-independent protocol for efficient re-authentication\n between the peer and an EAP re-authentication server through any\n authenticator. The re-authentication server may be in the home\n network or in the local network to which the peer is connecting.\n\nNarayanan & Dondeti Standards Track [Page 1]\n\f\nRFC 5296 ERP August 2008 5296 attribute attributes authentication key keys nested-reference unchanged"},{"id":"IETF RFC 5418","type":"specification","body":"IETF","designation":"RFC 5418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5418.txt","https://www.rfc-editor.org/rfc/rfc5418.pdf"],"folder":"IETF/RFC-5418","files":{"txt":{"path":"standards/IETF/RFC-5418/RFC-5418.txt","sha256":"bfb14772b2d076fa613ba8adc9f2419ee521840d3074da63e4453467a8279ff8"}},"tags":["nested-reference","unchanged"],"summary":"Early Wireless Local Area Network (WLAN) deployments feature a \"fat\"\n Access Point (AP), which serves as a stand-alone interface between\n the wired and wireless network segments. However, this model raises\n scaling, mobility, and manageability issues, and the Control and\n Provisioning of Wireless Access Points (CAPWAP) protocol is meant to\n address these issues. CAPWAP effectively splits the fat AP\n functionality into two network elements, and the communication\n channel between these components may traverse potentially hostile\n hops. This document analyzes the security exposure resulting from\n the introduction of CAPWAP and summarizes the associated security\n considerations for IEEE 802.11-based CAPWAP implementations and\n deployments.","scope_keywords":["5418","authentication","authorization","http","license","subject","tls","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null}],"search_text":"IETF RFC 5418 Early Wireless Local Area Network (WLAN) deployments feature a \"fat\"\n Access Point (AP), which serves as a stand-alone interface between\n the wired and wireless network segments. However, this model raises\n scaling, mobility, and manageability issues, and the Control and\n Provisioning of Wireless Access Points (CAPWAP) protocol is meant to\n address these issues. CAPWAP effectively splits the fat AP\n functionality into two network elements, and the communication\n channel between these components may traverse potentially hostile\n hops. This document analyzes the security exposure resulting from\n the introduction of CAPWAP and summarizes the associated security\n considerations for IEEE 802.11-based CAPWAP implementations and\n deployments. 5418 authentication authorization http license subject tls trust tsp nested-reference unchanged"},{"id":"IETF RFC 5433","type":"specification","body":"IETF","designation":"RFC 5433","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5433.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5433.txt","https://www.rfc-editor.org/rfc/rfc5433.pdf"],"folder":"IETF/RFC-5433","files":{"txt":{"path":"standards/IETF/RFC-5433/RFC-5433.txt","sha256":"43745936573f25c861914ecc3de6e0a40625ab3b82138bb1adc1bbd8e95405f1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an Extensible Authentication Protocol (EAP) method\n called EAP Generalized Pre-Shared Key (EAP-GPSK). This method is a\n lightweight shared-key authentication protocol supporting mutual\n authentication and key derivation.\n\nClancy & Tschofenig Standards Track [Page 1]\n\f\nRFC 5433 EAP-GPSK February 2009","scope_keywords":["5433","authentication","encryption","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 5433 This memo defines an Extensible Authentication Protocol (EAP) method\n called EAP Generalized Pre-Shared Key (EAP-GPSK). This method is a\n lightweight shared-key authentication protocol supporting mutual\n authentication and key derivation.\n\nClancy & Tschofenig Standards Track [Page 1]\n\f\nRFC 5433 EAP-GPSK February 2009 5433 authentication encryption http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5501","type":"specification","body":"IETF","designation":"RFC 5501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5501.txt","https://www.rfc-editor.org/rfc/rfc5501.pdf"],"folder":"IETF/RFC-5501","files":{"txt":{"path":"standards/IETF/RFC-5501/RFC-5501.txt","sha256":"94f5b12d22e0a0abf668825a9bc6de43434af184c3bb11e596e8621978e84c3c"}},"tags":["nested-reference","unchanged"],"summary":"This document provides functional requirements for network solutions\n that support multicast over Virtual Private LAN Service (VPLS). It\n specifies requirements both from the end user and service provider\n standpoints. It is intended that potential solutions will use these\n requirements as guidelines.\n\nKamite, et al. Informational [Page 1]\n\f\nRFC 5501 Multicast VPLS Requirements March 2009","scope_keywords":["5501","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null}],"search_text":"IETF RFC 5501 This document provides functional requirements for network solutions\n that support multicast over Virtual Private LAN Service (VPLS). It\n specifies requirements both from the end user and service provider\n standpoints. It is intended that potential solutions will use these\n requirements as guidelines.\n\nKamite, et al. Informational [Page 1]\n\f\nRFC 5501 Multicast VPLS Requirements March 2009 5501 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5607","type":"specification","body":"IETF","designation":"RFC 5607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5607.txt","https://www.rfc-editor.org/rfc/rfc5607.pdf"],"folder":"IETF/RFC-5607","files":{"txt":{"path":"standards/IETF/RFC-5607/RFC-5607.txt","sha256":"3e90736720aee22f8ce3f4cb06245f1badf0d0cbb7c0d26f8bfd4709d7299b22"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Remote Authentication Dial-In User Service\n (RADIUS) attributes for authorizing management access to a Network\n Access Server (NAS). Both local and remote management are supported,\n with granular access rights and management privileges. Specific\n provisions are made for remote management via Framed Management\n protocols and for management access over a secure transport protocol.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["5607","attribute","attributes","authentication","authorization","delivery","http","https","key","keys","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null}],"search_text":"IETF RFC 5607 This document specifies Remote Authentication Dial-In User Service\n (RADIUS) attributes for authorizing management access to a Network\n Access Server (NAS). Both local and remote management are supported,\n with granular access rights and management privileges. Specific\n provisions are made for remote management via Framed Management\n protocols and for management access over a secure transport protocol.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  5607 attribute attributes authentication authorization delivery http https key keys license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5608","type":"specification","body":"IETF","designation":"RFC 5608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5608.txt","https://www.rfc-editor.org/rfc/rfc5608.pdf"],"folder":"IETF/RFC-5608","files":{"txt":{"path":"standards/IETF/RFC-5608/RFC-5608.txt","sha256":"8c3f99cd195c05b4bca8c6d6f260cee8b5173e6304aeafe5aac13ea294d9d7fc"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of a Remote Authentication Dial-In User\n Service (RADIUS) authentication and authorization service with Simple\n Network Management Protocol (SNMP) secure Transport Models to\n authenticate users and authorize creation of secure transport\n sessions. While the recommendations of this memo are generally\n applicable to a broad class of SNMP Transport Models, the examples\n focus on the Secure Shell (SSH) Transport Model.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n docum","scope_keywords":["5608","attribute","attributes","authentication","authorization","credential","credentials","http","key","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5608 This memo describes the use of a Remote Authentication Dial-In User\n Service (RADIUS) authentication and authorization service with Simple\n Network Management Protocol (SNMP) secure Transport Models to\n authenticate users and authorize creation of secure transport\n sessions. While the recommendations of this memo are generally\n applicable to a broad class of SNMP Transport Models, the examples\n focus on the Secure Shell (SSH) Transport Model.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n docum 5608 attribute attributes authentication authorization credential credentials http key license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5687","type":"specification","body":"IETF","designation":"RFC 5687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5687.txt","https://www.rfc-editor.org/rfc/rfc5687.pdf"],"folder":"IETF/RFC-5687","files":{"txt":{"path":"standards/IETF/RFC-5687/RFC-5687.txt","sha256":"639098a48d45f3cae3e86e2266994167642357f5fd1805f6d2bc4b4c970a3a91"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a problem statement, lists requirements, and\n captures design aspects for a GEOPRIV Layer 7 (L7) Location\n Configuration Protocol (LCP). This protocol aims to allow an end\n host to obtain location information, by value or by reference, from a\n Location Information Server (LIS) that is located in the access\n network. The obtained location information can then be used for a\n variety of different protocols and purposes. For example, it can be\n used as input to the Location-to-Service Translation (LoST) Protocol\n or to convey location within the Session Initiation Protocol (SIP) to\n other entities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive","scope_keywords":["5687","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5808","folder":"IETF/RFC-5808","source":"IETF/RFC-5808/RFC-5808.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5687 This document provides a problem statement, lists requirements, and\n captures design aspects for a GEOPRIV Layer 7 (L7) Location\n Configuration Protocol (LCP). This protocol aims to allow an end\n host to obtain location information, by value or by reference, from a\n Location Information Server (LIS) that is located in the access\n network. The obtained location information can then be used for a\n variety of different protocols and purposes. For example, it can be\n used as input to the Location-to-Service Translation (LoST) Protocol\n or to convey location within the Session Initiation Protocol (SIP) to\n other entities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive 5687 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5692","type":"specification","body":"IETF","designation":"RFC 5692","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5692.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5692.txt","https://www.rfc-editor.org/rfc/rfc5692.pdf"],"folder":"IETF/RFC-5692","files":{"txt":{"path":"standards/IETF/RFC-5692/RFC-5692.txt","sha256":"82c86b921563cf1efef3fda1aaf134e3ef826ca551241caea771ead7c6a63197"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the transmission of IPv4 over Ethernet, as\n well as IPv6 over Ethernet, in an access network deploying the IEEE\n 802.16 cellular radio transmission technology. The Ethernet on top\n of IEEE 802.16 is realized by bridging connections that IEEE 802.16\n provides between a base station and its associated subscriber\n stations. Due to the resource constraints of radio transmission\n systems and the limitations of the IEEE 802.16 Media Access Control\n (MAC) functionality for the realization of an Ethernet, the\n transmission of IP over Ethernet over IEEE 802.16 may considerably\n benefit by adding IP-specific support functions in the Ethernet over\n IEEE 802.16 while maintaining full compatibility with standard IP\n over Ethernet behavior.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion an","scope_keywords":["5692","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 5692 This document describes the transmission of IPv4 over Ethernet, as\n well as IPv6 over Ethernet, in an access network deploying the IEEE\n 802.16 cellular radio transmission technology. The Ethernet on top\n of IEEE 802.16 is realized by bridging connections that IEEE 802.16\n provides between a base station and its associated subscriber\n stations. Due to the resource constraints of radio transmission\n systems and the limitations of the IEEE 802.16 Media Access Control\n (MAC) functionality for the realization of an Ethernet, the\n transmission of IP over Ethernet over IEEE 802.16 may considerably\n benefit by adding IP-specific support functions in the Ethernet over\n IEEE 802.16 while maintaining full compatibility with standard IP\n over Ethernet behavior.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion an 5692 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5757","type":"specification","body":"IETF","designation":"RFC 5757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5757.txt","https://www.rfc-editor.org/rfc/rfc5757.pdf"],"folder":"IETF/RFC-5757","files":{"txt":{"path":"standards/IETF/RFC-5757/RFC-5757.txt","sha256":"4d71fb96d9671788e8cc94ca2484139e912adacbfa3b230f0cedc2865ccd2260"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses current mobility extensions to IP-layer\n multicast. It describes problems arising from mobile group\n communication in general, the case of multicast listener mobility,\n and problems for mobile senders using Any Source Multicast and\n Source-Specific Multicast. Characteristic aspects of multicast\n routing and deployment issues for fixed IPv6 networks are summarized.\n Specific properties and interplays with the underlying network access\n are surveyed with respect to the relevant technologies in the\n wireless domain. It outlines the principal approaches to multicast\n mobility, together with a comprehensive exploration of the mobile\n multicast problem and solution space. This document concludes with a\n conceptual road map for initial steps in standardization for use by\n future mobile multicast protocol designers. This document is a\n product of the IP Mobility Optimizat","scope_keywords":["5757","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null}],"search_text":"IETF RFC 5757 This document discusses current mobility extensions to IP-layer\n multicast. It describes problems arising from mobile group\n communication in general, the case of multicast listener mobility,\n and problems for mobile senders using Any Source Multicast and\n Source-Specific Multicast. Characteristic aspects of multicast\n routing and deployment issues for fixed IPv6 networks are summarized.\n Specific properties and interplays with the underlying network access\n are surveyed with respect to the relevant technologies in the\n wireless domain. It outlines the principal approaches to multicast\n mobility, together with a comprehensive exploration of the mobile\n multicast problem and solution space. This document concludes with a\n conceptual road map for initial steps in standardization for use by\n future mobile multicast protocol designers. This document is a\n product of the IP Mobility Optimizat 5757 delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5777","type":"specification","body":"IETF","designation":"RFC 5777","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5777.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5777.txt","https://www.rfc-editor.org/rfc/rfc5777.pdf"],"folder":"IETF/RFC-5777","files":{"txt":{"path":"standards/IETF/RFC-5777/RFC-5777.txt","sha256":"fac6d1f959730137007f1eec4826d6e2bd1f937ecfd26ee31e70796174ee8fc8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a number of Diameter attribute-value pairs\n (AVPs) for traffic classification with actions for filtering and\n Quality of Service (QoS) treatment. These AVPs can be used in\n existing and future Diameter applications where permitted by the\n Augmented Backus-Naur Form (ABNF) specification of the respective\n Diameter command extension policy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rf","scope_keywords":["5777","attribute","attributes","authorization","http","license","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 5777 This document defines a number of Diameter attribute-value pairs\n (AVPs) for traffic classification with actions for filtering and\n Quality of Service (QoS) treatment. These AVPs can be used in\n existing and future Diameter applications where permitted by the\n Augmented Backus-Naur Form (ABNF) specification of the respective\n Diameter command extension policy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rf 5777 attribute attributes authorization http license policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5851","type":"specification","body":"IETF","designation":"RFC 5851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5851.txt","https://www.rfc-editor.org/rfc/rfc5851.pdf"],"folder":"IETF/RFC-5851","files":{"txt":{"path":"standards/IETF/RFC-5851/RFC-5851.txt","sha256":"f771995bfcad0ac4a53e00ef2e21d472b73c0c965f7885e1712fa19ab8b38033"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to define a framework for an Access\n Node Control Mechanism between a Network Access Server (NAS) and an\n Access Node (e.g., a Digital Subscriber Line Access Multiplexer\n (DSLAM)) in a multi-service reference architecture in order to\n perform operations related to service, quality of service, and\n subscribers. The Access Node Control Mechanism will ensure that the\n transmission of the information does not need to go through distinct\n element managers but rather uses a direct device-device\n communication. This allows for performing access-link-related\n operations within those network elements, while avoiding impact on\n the existing Operational Support Systems.\n\n This document first identifies a number of use cases for which the\n Access Node Control Mechanism may be appropriate. It then presents\n the requirements for the Access Node Control Protocol (ANCP) t","scope_keywords":["5851","attribute","attributes","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5851 The purpose of this document is to define a framework for an Access\n Node Control Mechanism between a Network Access Server (NAS) and an\n Access Node (e.g., a Digital Subscriber Line Access Multiplexer\n (DSLAM)) in a multi-service reference architecture in order to\n perform operations related to service, quality of service, and\n subscribers. The Access Node Control Mechanism will ensure that the\n transmission of the information does not need to go through distinct\n element managers but rather uses a direct device-device\n communication. This allows for performing access-link-related\n operations within those network elements, while avoiding impact on\n the existing Operational Support Systems.\n\n This document first identifies a number of use cases for which the\n Access Node Control Mechanism may be appropriate. It then presents\n the requirements for the Access Node Control Protocol (ANCP) t 5851 attribute attributes http identification license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5887","type":"specification","body":"IETF","designation":"RFC 5887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5887.txt","https://www.rfc-editor.org/rfc/rfc5887.pdf"],"folder":"IETF/RFC-5887","files":{"txt":{"path":"standards/IETF/RFC-5887/RFC-5887.txt","sha256":"2742930896f8052b16162a4ede3da6be8e32a1dac55aabe4c2f1b476bcaecbb0"}},"tags":["nested-reference","unchanged"],"summary":"This document reviews the existing mechanisms for site renumbering\n for both IPv4 and IPv6, and it identifies operational issues with\n those mechanisms. It also summarises current technical proposals for\n additional mechanisms. Finally, there is a gap analysis identifying\n possible areas for future work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["5887","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null}],"search_text":"IETF RFC 5887 This document reviews the existing mechanisms for site renumbering\n for both IPv4 and IPv6, and it identifies operational issues with\n those mechanisms. It also summarises current technical proposals for\n additional mechanisms. Finally, there is a gap analysis identifying\n possible areas for future work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 5887 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5997","type":"specification","body":"IETF","designation":"RFC 5997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5997.txt","https://www.rfc-editor.org/rfc/rfc5997.pdf"],"folder":"IETF/RFC-5997","files":{"txt":{"path":"standards/IETF/RFC-5997/RFC-5997.txt","sha256":"443a0642bad5b2bbea208c96e9b40330f753803272bc6430af06579bfe5e458b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, enabling\n clients to query the status of a RADIUS server. This extension\n utilizes the Status-Server (12) Code, which was reserved for\n experimental use in RFC 2865.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine","scope_keywords":["5997","attribute","attributes","authentication","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 5997 This document describes a deployed extension to the Remote\n Authentication Dial In User Service (RADIUS) protocol, enabling\n clients to query the status of a RADIUS server. This extension\n utilizes the Status-Server (12) Code, which was reserved for\n experimental use in RFC 2865.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine 5997 attribute attributes authentication http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6104","type":"specification","body":"IETF","designation":"RFC 6104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6104.txt","https://www.rfc-editor.org/rfc/rfc6104.pdf"],"folder":"IETF/RFC-6104","files":{"txt":{"path":"standards/IETF/RFC-6104/RFC-6104.txt","sha256":"cd17a7c151439cd66819918cddd042f28272bd0feef749c9532df7e354619ee3"}},"tags":["nested-reference","unchanged"],"summary":"When deploying IPv6, whether IPv6-only or dual-stack, routers are\n configured to send IPv6 Router Advertisements (RAs) to convey\n information to nodes that enable them to autoconfigure on the\n network. This information includes the implied default router\n address taken from the observed source address of the RA message, as\n well as on-link prefix information. However, unintended\n misconfigurations by users or administrators, or possibly malicious\n attacks on the network, may lead to bogus RAs being present, which in\n turn can cause operational problems for hosts on the network. In\n this document, we summarise the scenarios in which rogue RAs may be\n observed and present a list of possible solutions to the problem. We\n focus on the unintended causes of rogue RAs in the text. The goal of\n this text is to be Informational, and as such to present a framework\n around which solutions can be pr","scope_keywords":["6104","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6105","folder":"IETF/RFC-6105","source":"IETF/RFC-6105/RFC-6105.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null}],"search_text":"IETF RFC 6104 When deploying IPv6, whether IPv6-only or dual-stack, routers are\n configured to send IPv6 Router Advertisements (RAs) to convey\n information to nodes that enable them to autoconfigure on the\n network. This information includes the implied default router\n address taken from the observed source address of the RA message, as\n well as on-link prefix information. However, unintended\n misconfigurations by users or administrators, or possibly malicious\n attacks on the network, may lead to bogus RAs being present, which in\n turn can cause operational problems for hosts on the network. In\n this document, we summarise the scenarios in which rogue RAs may be\n observed and present a list of possible solutions to the problem. We\n focus on the unintended causes of rogue RAs in the text. The goal of\n this text is to be Informational, and as such to present a framework\n around which solutions can be pr 6104 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6136","type":"specification","body":"IETF","designation":"RFC 6136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6136.txt","https://www.rfc-editor.org/rfc/rfc6136.pdf"],"folder":"IETF/RFC-6136","files":{"txt":{"path":"standards/IETF/RFC-6136/RFC-6136.txt","sha256":"6b74286992e5e1bcc7e03d97df983057b0c705478e343aa5b8e2729420c7846e"}},"tags":["nested-reference","unchanged"],"summary":"This document provides framework and requirements for Layer 2 Virtual\n Private Network (L2VPN) Operations, Administration, and Maintenance\n (OAM). The OAM framework is intended to provide OAM layering across\n L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN)\n tunnels. This document is intended to identify OAM requirements for\n L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual\n Private Wire Service (VPWS), and IP-only LAN Service (IPLS).\n Furthermore, if L2VPN service OAM requirements impose specific\n requirements on PW OAM and/or PSN OAM, those specific PW and/or PSN\n OAM requirements are also identified.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com","scope_keywords":["6136","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null}],"search_text":"IETF RFC 6136 This document provides framework and requirements for Layer 2 Virtual\n Private Network (L2VPN) Operations, Administration, and Maintenance\n (OAM). The OAM framework is intended to provide OAM layering across\n L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN)\n tunnels. This document is intended to identify OAM requirements for\n L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual\n Private Wire Service (VPWS), and IP-only LAN Service (IPLS).\n Furthermore, if L2VPN service OAM requirements impose specific\n requirements on PW OAM and/or PSN OAM, those specific PW and/or PSN\n OAM requirements are also identified.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com 6136 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6221","type":"specification","body":"IETF","designation":"RFC 6221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6221.txt","https://www.rfc-editor.org/rfc/rfc6221.pdf"],"folder":"IETF/RFC-6221","files":{"txt":{"path":"standards/IETF/RFC-6221/RFC-6221.txt","sha256":"cd103ed065a08996294c85857bfa91246f64dde2bf55fa7f2f9c16e4351242bf"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a Lightweight DHCPv6 Relay Agent (LDRA) that\n is used to insert relay agent options in DHCPv6 message exchanges\n identifying client-facing interfaces. The LDRA can be implemented in\n existing access nodes (such as Digital Subscriber Link Access\n Multiplexers (DSLAMs) and Ethernet switches) that do not support IPv6\n control or routing functions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:/","scope_keywords":["6221","http","identification","key","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6221 This document proposes a Lightweight DHCPv6 Relay Agent (LDRA) that\n is used to insert relay agent options in DHCPv6 message exchanges\n identifying client-facing interfaces. The LDRA can be implemented in\n existing access nodes (such as Digital Subscriber Link Access\n Multiplexers (DSLAMs) and Ethernet switches) that do not support IPv6\n control or routing functions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:/ 6221 http identification key license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6329","type":"specification","body":"IETF","designation":"RFC 6329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6329.txt","https://www.rfc-editor.org/rfc/rfc6329.pdf"],"folder":"IETF/RFC-6329","files":{"txt":{"path":"standards/IETF/RFC-6329/RFC-6329.txt","sha256":"42c3fab345d1db06e759657b2fd697b23cb574b3f9f5b7e4aec33b39a7a6d65f"}},"tags":["nested-reference","unchanged"],"summary":"802.1aq Shortest Path Bridging (SPB) has been standardized by the\n IEEE as the next step in the evolution of the various spanning tree\n and registration protocols. 802.1aq allows for true shortest path\n forwarding in a mesh Ethernet network context utilizing multiple\n equal cost paths. This permits it to support much larger Layer 2\n topologies, with faster convergence, and vastly improved use of the\n mesh topology. Combined with this is single point provisioning for\n logical connectivity membership, which includes point-to-point,\n point-to-multipoint, and multipoint-to-multipoint variations. This\n memo documents the IS-IS changes required to support this IEEE\n protocol and provides some context and examples.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the I","scope_keywords":["6329","algorithm","http","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null}],"search_text":"IETF RFC 6329 802.1aq Shortest Path Bridging (SPB) has been standardized by the\n IEEE as the next step in the evolution of the various spanning tree\n and registration protocols. 802.1aq allows for true shortest path\n forwarding in a mesh Ethernet network context utilizing multiple\n equal cost paths. This permits it to support much larger Layer 2\n topologies, with faster convergence, and vastly improved use of the\n mesh topology. Combined with this is single point provisioning for\n logical connectivity membership, which includes point-to-point,\n point-to-multipoint, and multipoint-to-multipoint variations. This\n memo documents the IS-IS changes required to support this IEEE\n protocol and provides some context and examples.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the I 6329 algorithm http license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6391","type":"specification","body":"IETF","designation":"RFC 6391","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6391.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6391.txt","https://www.rfc-editor.org/rfc/rfc6391.pdf"],"folder":"IETF/RFC-6391","files":{"txt":{"path":"standards/IETF/RFC-6391/RFC-6391.txt","sha256":"b10ce90b623d91117eae5a7698665e919b770f6e2d37c6566d8ea518b5215141"}},"tags":["nested-reference","unchanged"],"summary":"Where the payload of a pseudowire comprises a number of distinct\n flows, it can be desirable to carry those flows over the Equal Cost\n Multiple Paths (ECMPs) that exist in the packet switched network.\n Most forwarding engines are able to generate a hash of the MPLS label\n stack and use this mechanism to balance MPLS flows over ECMPs.\n\n This document describes a method of identifying the flows, or flow\n groups, within pseudowires such that Label Switching Routers can\n balance flows at a finer granularity than individual pseudowires.\n The mechanism uses an additional label in the MPLS label stack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering St","scope_keywords":["6391","hash","hashing","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6391 Where the payload of a pseudowire comprises a number of distinct\n flows, it can be desirable to carry those flows over the Equal Cost\n Multiple Paths (ECMPs) that exist in the packet switched network.\n Most forwarding engines are able to generate a hash of the MPLS label\n stack and use this mechanism to balance MPLS flows over ECMPs.\n\n This document describes a method of identifying the flows, or flow\n groups, within pseudowires such that Label Switching Routers can\n balance flows at a finer granularity than individual pseudowires.\n The mechanism uses an additional label in the MPLS label stack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering St 6391 hash hashing http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6439","type":"specification","body":"IETF","designation":"RFC 6439","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6439.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6439.txt","https://www.rfc-editor.org/rfc/rfc6439.pdf"],"folder":"IETF/RFC-6439","files":{"txt":{"path":"standards/IETF/RFC-6439/RFC-6439.txt","sha256":"509d6e33c70f56952af1a83ce7218e07728348d62addcb671235f0f4ad27797a"}},"tags":["nested-reference","unchanged"],"summary":"The IETF TRILL (TRansparent Interconnection of Lots of Links)\n protocol provides least cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topology, safe\n forwarding even during periods of temporary loops, and support for\n multipathing of both unicast and multicast traffic. TRILL\n accomplishes this by using IS-IS (Intermediate System to Intermediate\n System) link state routing and by encapsulating traffic using a\n header that includes a hop count. Devices that implement TRILL are\n called \"RBridges\" (Routing Bridges).\n\n TRILL supports multi-access LAN (Local Area Network) links that can\n have multiple end stations and RBridges attached. Where multiple\n RBridges are attached to a link, native traffic to and from end\n stations on that link is handled by a subset of those RBridges called\n \"Appointed Forwarders\", with the intent that native traffic in ea","scope_keywords":["6439","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 6439 The IETF TRILL (TRansparent Interconnection of Lots of Links)\n protocol provides least cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topology, safe\n forwarding even during periods of temporary loops, and support for\n multipathing of both unicast and multicast traffic. TRILL\n accomplishes this by using IS-IS (Intermediate System to Intermediate\n System) link state routing and by encapsulating traffic using a\n header that includes a hop count. Devices that implement TRILL are\n called \"RBridges\" (Routing Bridges).\n\n TRILL supports multi-access LAN (Local Area Network) links that can\n have multiple end stations and RBridges attached. Where multiple\n RBridges are attached to a link, native traffic to and from end\n stations on that link is handled by a subset of those RBridges called\n \"Appointed Forwarders\", with the intent that native traffic in ea 6439 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6748","type":"specification","body":"IETF","designation":"RFC 6748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6748.txt","https://www.rfc-editor.org/rfc/rfc6748.pdf"],"folder":"IETF/RFC-6748","files":{"txt":{"path":"standards/IETF/RFC-6748/RFC-6748.txt","sha256":"1ca7be74ee286968fe263ec2648866d7f87256b1ccbe362edf7778deecc401c1"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an Architectural description and the Concept\n of Operations of some optional advanced deployment scenarios for the\n Identifier-Locator Network Protocol (ILNP), which is an evolutionary\n enhancement to IP. None of the functions described here is required\n for the use or deployment of ILNP. Instead, it offers descriptions\n of engineering and deployment options that might provide either\n enhanced capability or convenience in administration or management of\n ILNP-based systems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development acti","scope_keywords":["6748","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null}],"search_text":"IETF RFC 6748 This document provides an Architectural description and the Concept\n of Operations of some optional advanced deployment scenarios for the\n Identifier-Locator Network Protocol (ILNP), which is an evolutionary\n enhancement to IP. None of the functions described here is required\n for the use or deployment of ILNP. Instead, it offers descriptions\n of engineering and deployment options that might provide either\n enhanced capability or convenience in administration or management of\n ILNP-based systems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development acti 6748 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6820","type":"specification","body":"IETF","designation":"RFC 6820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6820.txt","https://www.rfc-editor.org/rfc/rfc6820.pdf"],"folder":"IETF/RFC-6820","files":{"txt":{"path":"standards/IETF/RFC-6820/RFC-6820.txt","sha256":"16474fc5f22c183132fc6c2912e979226a1f7f033c0332da7a73c1de06671ecf"}},"tags":["nested-reference","unchanged"],"summary":"This document examines address resolution issues related to the\n scaling of data centers with a very large number of hosts. The scope\n of this document is relatively narrow, focusing on address resolution\n (the Address Resolution Protocol (ARP) in IPv4 and Neighbor Discovery\n (ND) in IPv6) within a data center.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi","scope_keywords":["6820","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null}],"search_text":"IETF RFC 6820 This document examines address resolution issues related to the\n scaling of data centers with a very large number of hosts. The scope\n of this document is relatively narrow, focusing on address resolution\n (the Address Resolution Protocol (ARP) in IPv4 and Neighbor Discovery\n (ND) in IPv6) within a data center.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi 6820 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6905","type":"specification","body":"IETF","designation":"RFC 6905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6905.txt","https://www.rfc-editor.org/rfc/rfc6905.pdf"],"folder":"IETF/RFC-6905","files":{"txt":{"path":"standards/IETF/RFC-6905/RFC-6905.txt","sha256":"8737fad18052245cf7d524bde75ffcd032ac3a310d603a35761e712c24c31a3e"}},"tags":["nested-reference","unchanged"],"summary":"Operations, Administration, and Maintenance (OAM) is a general term\n used to identify functions and toolsets to troubleshoot and monitor\n networks. This document presents OAM requirements applicable to the\n Transparent Interconnection of Lots of Links (TRILL).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc","scope_keywords":["6905","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null}],"search_text":"IETF RFC 6905 Operations, Administration, and Maintenance (OAM) is a general term\n used to identify functions and toolsets to troubleshoot and monitor\n networks. This document presents OAM requirements applicable to the\n Transparent Interconnection of Lots of Links (TRILL).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc 6905 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7030","type":"specification","body":"IETF","designation":"RFC 7030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7030.txt","https://www.rfc-editor.org/rfc/rfc7030.pdf"],"folder":"IETF/RFC-7030","files":{"txt":{"path":"standards/IETF/RFC-7030/RFC-7030.txt","sha256":"61b797f3d0a2e6238bb57be64e1f1f5ecb1f1b464408512f93a0c4cfca94455c"}},"tags":["nested-reference","unchanged"],"summary":"This document profiles certificate enrollment for clients using\n Certificate Management over CMS (CMC) messages over a secure\n transport. This profile, called Enrollment over Secure Transport\n (EST), describes a simple, yet functional, certificate management\n protocol targeting Public Key Infrastructure (PKI) clients that need\n to acquire client certificates and associated Certification Authority\n (CA) certificates. It also supports client-generated public/private\n key pairs as well as key pairs generated by the CA.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in S","scope_keywords":["7030","attribute","attributes","authentication","authorization","certificate","certificates","encryption","http","key","license","management","pki","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7030 This document profiles certificate enrollment for clients using\n Certificate Management over CMS (CMC) messages over a secure\n transport. This profile, called Enrollment over Secure Transport\n (EST), describes a simple, yet functional, certificate management\n protocol targeting Public Key Infrastructure (PKI) clients that need\n to acquire client certificates and associated Certification Authority\n (CA) certificates. It also supports client-generated public/private\n key pairs as well as key pairs generated by the CA.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in S 7030 attribute attributes authentication authorization certificate certificates encryption http key license management pki profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 7067","type":"specification","body":"IETF","designation":"RFC 7067","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7067.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7067.txt","https://www.rfc-editor.org/rfc/rfc7067.pdf"],"folder":"IETF/RFC-7067","files":{"txt":{"path":"standards/IETF/RFC-7067/RFC-7067.txt","sha256":"189b2b12f0d995eea43773c39fc502af0f911825d0028e91ee6db578c904f804"}},"tags":["nested-reference","unchanged"],"summary":"Edge TRILL (Transparent Interconnection of Lots of Links) switches\n currently learn the mapping between MAC (Media Access Control)\n addresses and their egress TRILL switch by observing the data packets\n they ingress or egress or by the TRILL ESADI (End-Station Address\n Distribution Information) protocol. When an ingress TRILL switch\n receives a data frame for a destination address (MAC&Label) that the\n switch does not know, the data frame is flooded within the frame's\n Data Label across the TRILL campus.\n\n This document describes the framework for using directory services to\n assist edge TRILL switches in reducing multi-destination frames,\n particularly unknown unicast frames flooding, and ARP/ND (Address\n Resolution Protocol / Neighbor Discovery), thus improving TRILL\n network scalability and security.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification","scope_keywords":["7067","http","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7067 Edge TRILL (Transparent Interconnection of Lots of Links) switches\n currently learn the mapping between MAC (Media Access Control)\n addresses and their egress TRILL switch by observing the data packets\n they ingress or egress or by the TRILL ESADI (End-Station Address\n Distribution Information) protocol. When an ingress TRILL switch\n receives a data frame for a destination address (MAC&Label) that the\n switch does not know, the data frame is flooded within the frame's\n Data Label across the TRILL campus.\n\n This document describes the framework for using directory services to\n assist edge TRILL switches in reducing multi-destination frames,\n particularly unknown unicast frames flooding, and ARP/ND (Address\n Resolution Protocol / Neighbor Discovery), thus improving TRILL\n network scalability and security.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification 7067 http license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7170","type":"specification","body":"IETF","designation":"RFC 7170","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7170.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7170.txt","https://www.rfc-editor.org/rfc/rfc7170.pdf"],"folder":"IETF/RFC-7170","files":{"txt":{"path":"standards/IETF/RFC-7170/RFC-7170.txt","sha256":"87d7ee10b11956881b5747722c01f46a5b9401efa39f815c4a9cd714ec1d2aeb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Tunnel Extensible Authentication Protocol\n (TEAP) version 1. TEAP is a tunnel-based EAP method that enables\n secure communication between a peer and a server by using the\n Transport Layer Security (TLS) protocol to establish a mutually\n authenticated tunnel. Within the tunnel, TLV objects are used to\n convey authentication-related data between the EAP peer and the EAP\n server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb","scope_keywords":["7170","attribute","attributes","authentication","certificate","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 7170 This document defines the Tunnel Extensible Authentication Protocol\n (TEAP) version 1. TEAP is a tunnel-based EAP method that enables\n secure communication between a peer and a server by using the\n Transport Layer Security (TLS) protocol to establish a mutually\n authenticated tunnel. Within the tunnel, TLV objects are used to\n convey authentication-related data between the EAP peer and the EAP\n server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb 7170 attribute attributes authentication certificate http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7172","type":"specification","body":"IETF","designation":"RFC 7172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7172.txt","https://www.rfc-editor.org/rfc/rfc7172.pdf"],"folder":"IETF/RFC-7172","files":{"txt":{"path":"standards/IETF/RFC-7172/RFC-7172.txt","sha256":"e37725d72c4cf5c53586050f111733cab1ad92ca55701a2a9b05193ed219cccd"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has standardized Transparent Interconnection of Lots of\n Links (TRILL), a protocol for least-cost transparent frame routing in\n multi-hop networks with arbitrary topologies and link technologies,\n using link-state routing and a hop count. The TRILL base protocol\n standard supports the labeling of TRILL Data packets with up to 4K\n IDs. However, there are applications that require a larger number of\n labels providing configurable isolation of data. This document\n updates RFC 6325 by specifying optional extensions to the TRILL base\n protocol to safely accomplish this. These extensions, called fine-\n grained labeling, are primarily intended for use in large data\n centers, that is, those with more than 4K users requiring\n configurable data isolation from each other.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engin","scope_keywords":["7172","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7172 The IETF has standardized Transparent Interconnection of Lots of\n Links (TRILL), a protocol for least-cost transparent frame routing in\n multi-hop networks with arbitrary topologies and link technologies,\n using link-state routing and a hop count. The TRILL base protocol\n standard supports the labeling of TRILL Data packets with up to 4K\n IDs. However, there are applications that require a larger number of\n labels providing configurable isolation of data. This document\n updates RFC 6325 by specifying optional extensions to the TRILL base\n protocol to safely accomplish this. These extensions, called fine-\n grained labeling, are primarily intended for use in large data\n centers, that is, those with more than 4K users requiring\n configurable data isolation from each other.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engin 7172 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7175","type":"specification","body":"IETF","designation":"RFC 7175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7175.txt","https://www.rfc-editor.org/rfc/rfc7175.pdf"],"folder":"IETF/RFC-7175","files":{"txt":{"path":"standards/IETF/RFC-7175/RFC-7175.txt","sha256":"5f56c7e833202e1f81664f36878874c817f72430367ae4b85d07d83802ade74e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies use of the Bidirectional Forwarding Detection\n (BFD) protocol in Routing Bridge (RBridge) campuses based on the\n RBridge Channel extension to the Transparent Interconnection of Lots\n of Links (TRILL) protocol.\n\n BFD is a widely deployed Operations, Administration, and Maintenance\n (OAM) mechanism in IP and MPLS networks, using UDP and Associated\n Channel Header (ACH) encapsulation respectively. This document\n specifies the BFD encapsulation over TRILL.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about","scope_keywords":["7175","authentication","http","key","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7175 This document specifies use of the Bidirectional Forwarding Detection\n (BFD) protocol in Routing Bridge (RBridge) campuses based on the\n RBridge Channel extension to the Transparent Interconnection of Lots\n of Links (TRILL) protocol.\n\n BFD is a widely deployed Operations, Administration, and Maintenance\n (OAM) mechanism in IP and MPLS networks, using UDP and Associated\n Channel Header (ACH) encapsulation respectively. This document\n specifies the BFD encapsulation over TRILL.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about 7175 authentication http key license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7224","type":"specification","body":"IETF","designation":"RFC 7224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7224.txt","https://www.rfc-editor.org/rfc/rfc7224.pdf"],"folder":"IETF/RFC-7224","files":{"txt":{"path":"standards/IETF/RFC-7224/RFC-7224.txt","sha256":"1ee971382bb0730341972b98809074ab5be89e38aec5b10060f18d9bc3e26350"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the initial version of the iana-if-type YANG\n module.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7224.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license","scope_keywords":["7224","http","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 7224 This document defines the initial version of the iana-if-type YANG\n module.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7224.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license 7224 http license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7226","type":"specification","body":"IETF","designation":"RFC 7226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7226.txt","https://www.rfc-editor.org/rfc/rfc7226.pdf"],"folder":"IETF/RFC-7226","files":{"txt":{"path":"standards/IETF/RFC-7226/RFC-7226.txt","sha256":"bb58ddca464c472bd82c10134fb254025d6e8a0c8034a4da05e9ba66dadcb202"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a set of requirements for Advanced Multipath\n in MPLS networks.\n\n Advanced Multipath is a formalization of multipath techniques\n currently in use in IP and MPLS networks and a set of extensions to\n existing multipath techniques.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o","scope_keywords":["7226","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null}],"search_text":"IETF RFC 7226 This document provides a set of requirements for Advanced Multipath\n in MPLS networks.\n\n Advanced Multipath is a formalization of multipath techniques\n currently in use in IP and MPLS networks and a set of extensions to\n existing multipath techniques.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o 7226 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 7276","type":"specification","body":"IETF","designation":"RFC 7276","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7276.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7276.txt","https://www.rfc-editor.org/rfc/rfc7276.pdf"],"folder":"IETF/RFC-7276","files":{"txt":{"path":"standards/IETF/RFC-7276/RFC-7276.txt","sha256":"7a1da14132c0d9177a14051c9b36c87ebbbf56a8abe361162b14e69e427bdfaa"}},"tags":["nested-reference","unchanged"],"summary":"Operations, Administration, and Maintenance (OAM) is a general term\n that refers to a toolset for fault detection and isolation, and for\n performance measurement. Over the years, various OAM tools have been\n defined for various layers in the protocol stack.\n\n This document summarizes some of the OAM tools defined in the IETF in\n the context of IP unicast, MPLS, MPLS Transport Profile (MPLS-TP),\n pseudowires, and Transparent Interconnection of Lots of Links\n (TRILL). This document focuses on tools for detecting and isolating\n failures in networks and for performance monitoring. Control and\n management aspects of OAM are outside the scope of this document.\n Network repair functions such as Fast Reroute (FRR) and protection\n switching, which are often triggered by OAM protocols, are also out\n of the scope of this document.\n\n The target audience of this document includes network equipment\n v","scope_keywords":["7276","http","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null}],"search_text":"IETF RFC 7276 Operations, Administration, and Maintenance (OAM) is a general term\n that refers to a toolset for fault detection and isolation, and for\n performance measurement. Over the years, various OAM tools have been\n defined for various layers in the protocol stack.\n\n This document summarizes some of the OAM tools defined in the IETF in\n the context of IP unicast, MPLS, MPLS Transport Profile (MPLS-TP),\n pseudowires, and Transparent Interconnection of Lots of Links\n (TRILL). This document focuses on tools for detecting and isolating\n failures in networks and for performance monitoring. Control and\n management aspects of OAM are outside the scope of this document.\n Network repair functions such as Fast Reroute (FRR) and protection\n switching, which are often triggered by OAM protocols, are also out\n of the scope of this document.\n\n The target audience of this document includes network equipment\n v 7276 http license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7319","type":"specification","body":"IETF","designation":"RFC 7319","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7319.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7319.txt","https://www.rfc-editor.org/rfc/rfc7319.pdf"],"folder":"IETF/RFC-7319","files":{"txt":{"path":"standards/IETF/RFC-7319/RFC-7319.txt","sha256":"c199a496d0e13277435e3260aaf5ccce3f5d9f15cbcfaa64f1f19f9f21ae77ed"}},"tags":["nested-reference","unchanged"],"summary":"IEEE 802.1 has specified Connectivity Fault Management (CFM)\n Operations, Administration, and Maintenance (OAM) facilities. CFM\n messages are structured with an OpCode field and have provision for\n the inclusion of TLV-structured information. IEEE 802.1 has\n allocated blocks of CFM OpCodes and TLV Types to the IETF. This\n document specifies the IANA considerations for the assignment of\n values from these blocks.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide ","scope_keywords":["7319","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 7319 IEEE 802.1 has specified Connectivity Fault Management (CFM)\n Operations, Administration, and Maintenance (OAM) facilities. CFM\n messages are structured with an OpCode field and have provision for\n the inclusion of TLV-structured information. IEEE 802.1 has\n allocated blocks of CFM OpCodes and TLV Types to the IETF. This\n document specifies the IANA considerations for the assignment of\n values from these blocks.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide  7319 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7322","type":"specification","body":"IETF","designation":"RFC 7322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7322.txt","https://www.rfc-editor.org/rfc/rfc7322.pdf"],"folder":"IETF/RFC-7322","files":{"txt":{"path":"standards/IETF/RFC-7322/RFC-7322.txt","sha256":"2098659cbbd189d9c42ce7bf4922f7d575885ff645811a36aaba61a212d55f46"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the fundamental and unique style conventions\n and editorial policies currently in use for the RFC Series. It\n captures the RFC Editor's basic requirements and offers guidance\n regarding the style and structure of an RFC. Additional guidance is\n captured on a website that reflects the experimental nature of that\n guidance and prepares it for future inclusion in the RFC Style Guide.\n This document obsoletes RFC 2223, \"Instructions to RFC Authors\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a c","scope_keywords":["7322","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7993","folder":"IETF/RFC-7993","source":"IETF/RFC-7993/RFC-7993.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 7322 This document describes the fundamental and unique style conventions\n and editorial policies currently in use for the RFC Series. It\n captures the RFC Editor's basic requirements and offers guidance\n regarding the style and structure of an RFC. Additional guidance is\n captured on a website that reflects the experimental nature of that\n guidance and prepares it for future inclusion in the RFC Style Guide.\n This document obsoletes RFC 2223, \"Instructions to RFC Authors\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a c 7322 http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7348","type":"specification","body":"IETF","designation":"RFC 7348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7348.txt","https://www.rfc-editor.org/rfc/rfc7348.pdf"],"folder":"IETF/RFC-7348","files":{"txt":{"path":"standards/IETF/RFC-7348/RFC-7348.txt","sha256":"731475429b30bf4b29a102a0c9217cb0d3522c34fd546ba7b134fec931e83574"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Virtual eXtensible Local Area Network\n (VXLAN), which is used to address the need for overlay networks\n within virtualized data centers accommodating multiple tenants. The\n scheme and the related protocols can be used in networks for cloud\n service providers and enterprise data centers. This memo documents\n the deployed VXLAN protocol for the benefit of the Internet\n community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 574","scope_keywords":["7348","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 7348 This document describes Virtual eXtensible Local Area Network\n (VXLAN), which is used to address the need for overlay networks\n within virtualized data centers accommodating multiple tenants. The\n scheme and the related protocols can be used in networks for cloud\n service providers and enterprise data centers. This memo documents\n the deployed VXLAN protocol for the benefit of the Internet\n community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 574 7348 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 7356","type":"specification","body":"IETF","designation":"RFC 7356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7356.txt","https://www.rfc-editor.org/rfc/rfc7356.pdf"],"folder":"IETF/RFC-7356","files":{"txt":{"path":"standards/IETF/RFC-7356/RFC-7356.txt","sha256":"ad9ca1ac9fda709d80afa189e0cb865da171cb6c76ad953252d0802df14a08f4"}},"tags":["nested-reference","unchanged"],"summary":"Intermediate System to Intermediate System (IS-IS) provides efficient\n and reliable flooding of information to its peers; however, the\n current flooding scopes are limited to either area scope or domain\n scope. There are existing use cases where support of other flooding\n scopes is desirable. This document defines new Protocol Data Units\n (PDUs) that provide support for new flooding scopes as well as\n additional space for advertising information targeted for the\n currently supported flooding scopes. This document also defines\n extended Type-Length-Values (TLVs) and sub-TLVs that are encoded\n using 16-bit fields for Type and Length.\n\n The protocol extensions defined in this document are not backwards\n compatible with existing implementations and so must be deployed with\n care.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet","scope_keywords":["7356","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7356 Intermediate System to Intermediate System (IS-IS) provides efficient\n and reliable flooding of information to its peers; however, the\n current flooding scopes are limited to either area scope or domain\n scope. There are existing use cases where support of other flooding\n scopes is desirable. This document defines new Protocol Data Units\n (PDUs) that provide support for new flooding scopes as well as\n additional space for advertising information targeted for the\n currently supported flooding scopes. This document also defines\n extended Type-Length-Values (TLVs) and sub-TLVs that are encoded\n using 16-bit fields for Type and Length.\n\n The protocol extensions defined in this document are not backwards\n compatible with existing implementations and so must be deployed with\n care.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet 7356 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7357","type":"specification","body":"IETF","designation":"RFC 7357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7357.txt","https://www.rfc-editor.org/rfc/rfc7357.pdf"],"folder":"IETF/RFC-7357","files":{"txt":{"path":"standards/IETF/RFC-7357/RFC-7357.txt","sha256":"fadafdbdeef1cca8b27ab9d4c6d495c8cd4d5ff4710a813ea4f514f643e66115"}},"tags":["nested-reference","unchanged"],"summary":"The IETF TRILL (Transparent Interconnection of Lots of Links)\n protocol provides least-cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topologies and\n link technologies. TRILL supports multipathing of both unicast and\n multicast traffic. Devices that implement the TRILL protocol are\n called TRILL switches or RBridges (Routing Bridges).\n\n ESADI (End Station Address Distribution Information) is an optional\n protocol by which a TRILL switch can communicate, in a Data Label\n (VLAN or fine-grained label) scoped way, end station address and\n reachability information to TRILL switches participating in ESADI for\n the relevant Data Label. This document updates RFC 6325,\n specifically the documentation of the ESADI protocol, and is not\n backwards compatible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product ","scope_keywords":["7357","authentication","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7357 The IETF TRILL (Transparent Interconnection of Lots of Links)\n protocol provides least-cost pair-wise data forwarding without\n configuration in multi-hop networks with arbitrary topologies and\n link technologies. TRILL supports multipathing of both unicast and\n multicast traffic. Devices that implement the TRILL protocol are\n called TRILL switches or RBridges (Routing Bridges).\n\n ESADI (End Station Address Distribution Information) is an optional\n protocol by which a TRILL switch can communicate, in a Data Label\n (VLAN or fine-grained label) scoped way, end station address and\n reachability information to TRILL switches participating in ESADI for\n the relevant Data Label. This document updates RFC 6325,\n specifically the documentation of the ESADI protocol, and is not\n backwards compatible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product  7357 authentication http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7364","type":"specification","body":"IETF","designation":"RFC 7364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7364.txt","https://www.rfc-editor.org/rfc/rfc7364.pdf"],"folder":"IETF/RFC-7364","files":{"txt":{"path":"standards/IETF/RFC-7364/RFC-7364.txt","sha256":"3c000b8f59877cae682ad44f8ae6a65824383fb85a9f28052a7a3ac75294e57b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes issues associated with providing multi-\n tenancy in large data center networks and how these issues may be\n addressed using an overlay-based network virtualization approach. A\n key multi-tenancy requirement is traffic isolation so that one\n tenant's traffic is not visible to any other tenant. Another\n requirement is address space isolation so that different tenants can\n use the same address space within different virtual networks.\n Traffic and address space isolation is achieved by assigning one or\n more virtual networks to each tenant, where traffic within a virtual\n network can only cross into another virtual network in a controlled\n fashion (e.g., via a configured router and/or a security gateway).\n Additional functionality is required to provision virtual networks,\n associating a virtual machine's network interface(s) with the\n appropriate virtual network and ","scope_keywords":["7364","http","key","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 7364 This document describes issues associated with providing multi-\n tenancy in large data center networks and how these issues may be\n addressed using an overlay-based network virtualization approach. A\n key multi-tenancy requirement is traffic isolation so that one\n tenant's traffic is not visible to any other tenant. Another\n requirement is address space isolation so that different tenants can\n use the same address space within different virtual networks.\n Traffic and address space isolation is achieved by assigning one or\n more virtual networks to each tenant, where traffic within a virtual\n network can only cross into another virtual network in a controlled\n fashion (e.g., via a configured router and/or a security gateway).\n Additional functionality is required to provision virtual networks,\n associating a virtual machine's network interface(s) with the\n appropriate virtual network and  7364 http key license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7365","type":"specification","body":"IETF","designation":"RFC 7365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7365.txt","https://www.rfc-editor.org/rfc/rfc7365.pdf"],"folder":"IETF/RFC-7365","files":{"txt":{"path":"standards/IETF/RFC-7365/RFC-7365.txt","sha256":"1d81d81d350153f4327cf40695a77d7ea194a246ec463a888ee2468e46691250"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for Data Center (DC) Network\n Virtualization over Layer 3 (NVO3) and defines a reference model\n along with logical components required to design a solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7365.\n\nLasserre, et al. Informational [Page 1]\n\f\n","scope_keywords":["7365","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 7365 This document provides a framework for Data Center (DC) Network\n Virtualization over Layer 3 (NVO3) and defines a reference model\n along with logical components required to design a solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7365.\n\nLasserre, et al. Informational [Page 1]\n\f\n 7365 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 7368","type":"specification","body":"IETF","designation":"RFC 7368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7368.txt","https://www.rfc-editor.org/rfc/rfc7368.pdf"],"folder":"IETF/RFC-7368","files":{"txt":{"path":"standards/IETF/RFC-7368/RFC-7368.txt","sha256":"b91ef85764995daa188ca882d7a669118de87a62c12f777ab45c5d844d03f54d"}},"tags":["nested-reference","unchanged"],"summary":"This text describes evolving networking technology within residential\n home networks with increasing numbers of devices and a trend towards\n increased internal routing. The goal of this document is to define a\n general architecture for IPv6-based home networking, describing the\n associated principles, considerations, and requirements. The text\n briefly highlights specific implications of the introduction of IPv6\n for home networking, discusses the elements of the architecture, and\n suggests how standard IPv6 mechanisms and addressing can be employed\n in home networking. The architecture describes the need for specific\n protocol extensions for certain additional functionality. It is\n assumed that the IPv6 home network is not actively managed and runs\n as an IPv6-only or dual-stack network. There are no recommendations\n in this text for the IPv4 part of the network.\n\nStatus of This Memo\n\n ","scope_keywords":["7368","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7368 This text describes evolving networking technology within residential\n home networks with increasing numbers of devices and a trend towards\n increased internal routing. The goal of this document is to define a\n general architecture for IPv6-based home networking, describing the\n associated principles, considerations, and requirements. The text\n briefly highlights specific implications of the introduction of IPv6\n for home networking, discusses the elements of the architecture, and\n suggests how standard IPv6 mechanisms and addressing can be employed\n in home networking. The architecture describes the need for specific\n protocol extensions for certain additional functionality. It is\n assumed that the IPv6 home network is not actively managed and runs\n as an IPv6-only or dual-stack network. There are no recommendations\n in this text for the IPv4 part of the network.\n\nStatus of This Memo\n\n  7368 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7390","type":"specification","body":"IETF","designation":"RFC 7390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7390.txt","https://www.rfc-editor.org/rfc/rfc7390.pdf"],"folder":"IETF/RFC-7390","files":{"txt":{"path":"standards/IETF/RFC-7390/RFC-7390.txt","sha256":"44ef629d22bc46ce1a72f9a952a7b337de7151da37a8314f66380d0e3c802fa8"}},"tags":["nested-reference","unchanged"],"summary":"The Constrained Application Protocol (CoAP) is a specialized web\n transfer protocol for constrained devices and constrained networks.\n It is anticipated that constrained devices will often naturally\n operate in groups (e.g., in a building automation scenario, all\n lights in a given room may need to be switched on/off as a group).\n This specification defines how CoAP should be used in a group\n communication context. An approach for using CoAP on top of IP\n multicast is detailed based on existing CoAP functionality as well as\n new features introduced in this specification. Also, various use\n cases and corresponding protocol flows are provided to illustrate\n important concepts. Finally, guidance is provided for deployment in\n various network topologies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental imple","scope_keywords":["7390","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null}],"search_text":"IETF RFC 7390 The Constrained Application Protocol (CoAP) is a specialized web\n transfer protocol for constrained devices and constrained networks.\n It is anticipated that constrained devices will often naturally\n operate in groups (e.g., in a building automation scenario, all\n lights in a given room may need to be switched on/off as a group).\n This specification defines how CoAP should be used in a group\n communication context. An approach for using CoAP on top of IP\n multicast is detailed based on existing CoAP functionality as well as\n new features introduced in this specification. Also, various use\n cases and corresponding protocol flows are provided to illustrate\n important concepts. Finally, guidance is provided for deployment in\n various network topologies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental imple 7390 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7406","type":"specification","body":"IETF","designation":"RFC 7406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7406.txt","https://www.rfc-editor.org/rfc/rfc7406.pdf"],"folder":"IETF/RFC-7406","files":{"txt":{"path":"standards/IETF/RFC-7406/RFC-7406.txt","sha256":"1bc6dc371293016abba4b626ef74a60f4d1e27e207c6a9be3a6d1283519b4096"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a problem statement, introduces terminology,\n and describes an extension for the base IETF emergency services\n architecture to address cases where an emergency caller is not\n authenticated, has no identifiable service provider, or has no\n remaining credit with which to pay for access to the network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h","scope_keywords":["7406","authentication","authorization","credential","credentials","http","identification","license","profile","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 7406 This document provides a problem statement, introduces terminology,\n and describes an extension for the base IETF emergency services\n architecture to address cases where an emergency caller is not\n authenticated, has no identifiable service provider, or has no\n remaining credit with which to pay for access to the network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h 7406 authentication authorization credential credentials http identification license profile subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 7424","type":"specification","body":"IETF","designation":"RFC 7424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7424.txt","https://www.rfc-editor.org/rfc/rfc7424.pdf"],"folder":"IETF/RFC-7424","files":{"txt":{"path":"standards/IETF/RFC-7424/RFC-7424.txt","sha256":"844384bafd7d607e990a7e5c27d0fd460d2ec57e8fda9567ba72fddeb6e709f3"}},"tags":["nested-reference","unchanged"],"summary":"Demands on networking infrastructure are growing exponentially due to\n bandwidth-hungry applications such as rich media applications and\n inter-data-center communications. In this context, it is important\n to optimally use the bandwidth in wired networks that extensively use\n link aggregation groups and equal-cost multipaths as techniques for\n bandwidth scaling. This document explores some of the mechanisms\n useful for achieving this.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Interne","scope_keywords":["7424","algorithm","algorithms","hash","http","identification","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7424 Demands on networking infrastructure are growing exponentially due to\n bandwidth-hungry applications such as rich media applications and\n inter-data-center communications. In this context, it is important\n to optimally use the bandwidth in wired networks that extensively use\n link aggregation groups and equal-cost multipaths as techniques for\n bandwidth scaling. This document explores some of the mechanisms\n useful for achieving this.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Interne 7424 algorithm algorithms hash http identification license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7432","type":"specification","body":"IETF","designation":"RFC 7432","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7432.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7432.txt","https://www.rfc-editor.org/rfc/rfc7432.pdf"],"folder":"IETF/RFC-7432","files":{"txt":{"path":"standards/IETF/RFC-7432/RFC-7432.txt","sha256":"556956e275a856ad727aa45d493725a4e13f002ffd4e3f2744b3091b886569d0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes procedures for BGP MPLS-based Ethernet VPNs\n (EVPN). The procedures described here meet the requirements\n specified in RFC 7209 -- \"Requirements for Ethernet VPN (EVPN)\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7432.\n\nSajassi, et al. Standards Track [Page 1]\n\f\nRFC 7432 BGP MPLS-Based Ethernet VPN February 2015\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Tr","scope_keywords":["7432","http","identification","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 7432 This document describes procedures for BGP MPLS-based Ethernet VPNs\n (EVPN). The procedures described here meet the requirements\n specified in RFC 7209 -- \"Requirements for Ethernet VPN (EVPN)\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7432.\n\nSajassi, et al. Standards Track [Page 1]\n\f\nRFC 7432 BGP MPLS-Based Ethernet VPN February 2015\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Tr 7432 http identification license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7455","type":"specification","body":"IETF","designation":"RFC 7455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7455.txt","https://www.rfc-editor.org/rfc/rfc7455.pdf"],"folder":"IETF/RFC-7455","files":{"txt":{"path":"standards/IETF/RFC-7455/RFC-7455.txt","sha256":"a7b173135cf481d5f1214a36e22ddeec7fd982439a1fe5aeb607e0295288a35b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Transparent Interconnection of Lots of Links\n (TRILL) Operations, Administration, and Maintenance (OAM) fault\n management. Methods in this document follow the CFM (Connectivity\n Fault Management) framework defined in IEEE 802.1 and reuse OAM tools\n where possible. Additional messages and TLVs are defined for TRILL-\n specific applications or for cases where a different set of\n information is required other than CFM as defined in IEEE 802.1.\n This document updates RFC 6325.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.","scope_keywords":["7455","authentication","http","identification","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7455 This document specifies Transparent Interconnection of Lots of Links\n (TRILL) Operations, Administration, and Maintenance (OAM) fault\n management. Methods in this document follow the CFM (Connectivity\n Fault Management) framework defined in IEEE 802.1 and reuse OAM tools\n where possible. Additional messages and TLVs are defined for TRILL-\n specific applications or for cases where a different set of\n information is required other than CFM as defined in IEEE 802.1.\n This document updates RFC 6325.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741. 7455 authentication http identification license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 7461","type":"specification","body":"IETF","designation":"RFC 7461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7461.txt","https://www.rfc-editor.org/rfc/rfc7461.pdf"],"folder":"IETF/RFC-7461","files":{"txt":{"path":"standards/IETF/RFC-7461/RFC-7461.txt","sha256":"dc080a33f19201f11b1bdb4ca3fd0cce1f4118ea01344cf4affbfb3fad842f55"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a subset of a Management Information Base (MIB)\n for energy management of devices. The module addresses device\n identification, context information, and the energy relationships\n between devices.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7461.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights rese","scope_keywords":["7461","http","identification","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 7461 This document defines a subset of a Management Information Base (MIB)\n for energy management of devices. The module addresses device\n identification, context information, and the energy relationships\n between devices.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7461.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights rese 7461 http identification key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7593","type":"specification","body":"IETF","designation":"RFC 7593","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7593.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7593.txt","https://www.rfc-editor.org/rfc/rfc7593.pdf"],"folder":"IETF/RFC-7593","files":{"txt":{"path":"standards/IETF/RFC-7593/RFC-7593.txt","sha256":"709c11e5028e8d8a95cc2772cb1c3d878a128f72dcca680d3cbe7c442c167ae2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the architecture of the eduroam service for\n federated (wireless) network access in academia. The combination of\n IEEE 802.1X, the Extensible Authentication Protocol (EAP), and RADIUS\n that is used in eduroam provides a secure, scalable, and deployable\n service for roaming network access. The successful deployment of\n eduroam over the last decade in the educational sector may serve as\n an example for other sectors, hence this document. In particular,\n the initial architectural choices and selection of standards are\n described, along with the changes that were prompted by operational\n experience.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n it","scope_keywords":["7593","authentication","authorization","credential","credentials","encryption","http","license","management","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 7593 This document describes the architecture of the eduroam service for\n federated (wireless) network access in academia. The combination of\n IEEE 802.1X, the Extensible Authentication Protocol (EAP), and RADIUS\n that is used in eduroam provides a secure, scalable, and deployable\n service for roaming network access. The successful deployment of\n eduroam over the last decade in the educational sector may serve as\n an example for other sectors, hence this document. In particular,\n the initial architectural choices and selection of standards are\n described, along with the changes that were prompted by operational\n experience.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n it 7593 authentication authorization credential credentials encryption http license management subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8014","type":"specification","body":"IETF","designation":"RFC 8014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8014.txt","https://www.rfc-editor.org/rfc/rfc8014.pdf"],"folder":"IETF/RFC-8014","files":{"txt":{"path":"standards/IETF/RFC-8014/RFC-8014.txt","sha256":"6e85dbac2b8218f9c36472fbbd712eea0438f42b3428388d97dcf804b0a9d964"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a high-level overview architecture for\n building data-center Network Virtualization over Layer 3 (NVO3)\n networks. The architecture is given at a high level, showing the\n major components of an overall system. An important goal is to\n divide the space into individual smaller components that can be\n implemented independently with clear inter-component interfaces and\n interactions. It should be possible to build and implement\n individual components in isolation and have them interoperate with\n other independently implemented components. That way, implementers\n have flexibility in implementing individual components and can\n optimize and innovate within their respective components without\n requiring changes to other components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu","scope_keywords":["8014","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 8014 This document presents a high-level overview architecture for\n building data-center Network Virtualization over Layer 3 (NVO3)\n networks. The architecture is given at a high level, showing the\n major components of an overall system. An important goal is to\n divide the space into individual smaller components that can be\n implemented independently with clear inter-component interfaces and\n interactions. It should be possible to build and implement\n individual components in isolation and have them interoperate with\n other independently implemented components. That way, implementers\n have flexibility in implementing individual components and can\n optimize and innovate within their respective components without\n requiring changes to other components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu 8014 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8033","type":"specification","body":"IETF","designation":"RFC 8033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8033.txt","https://www.rfc-editor.org/rfc/rfc8033.pdf"],"folder":"IETF/RFC-8033","files":{"txt":{"path":"standards/IETF/RFC-8033/RFC-8033.txt","sha256":"2b5544d264fef03d6804fe42dd43178d6ff80171657a582e25c886c25e3bc4b6"}},"tags":["nested-reference","unchanged"],"summary":"Bufferbloat is a phenomenon in which excess buffers in the network\n cause high latency and latency variation. As more and more\n interactive applications (e.g., voice over IP, real-time video\n streaming, and financial transactions) run in the Internet, high\n latency and latency variation degrade application performance. There\n is a pressing need to design intelligent queue management schemes\n that can control latency and latency variation, and hence provide\n desirable quality of service to users.\n\n This document presents a lightweight active queue management design\n called \"PIE\" (Proportional Integral controller Enhanced) that can\n effectively control the average queuing latency to a target value.\n Simulation results, theoretical analysis, and Linux testbed results\n have shown that PIE can ensure low latency and achieve high link\n utilization under various congestion situations. The desig","scope_keywords":["8033","algorithm","algorithms","http","license","management","pid","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8034","folder":"IETF/RFC-8034","source":"IETF/RFC-8034/RFC-8034.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null}],"search_text":"IETF RFC 8033 Bufferbloat is a phenomenon in which excess buffers in the network\n cause high latency and latency variation. As more and more\n interactive applications (e.g., voice over IP, real-time video\n streaming, and financial transactions) run in the Internet, high\n latency and latency variation degrade application performance. There\n is a pressing need to design intelligent queue management schemes\n that can control latency and latency variation, and hence provide\n desirable quality of service to users.\n\n This document presents a lightweight active queue management design\n called \"PIE\" (Proportional Integral controller Enhanced) that can\n effectively control the average queuing latency to a target value.\n Simulation results, theoretical analysis, and Linux testbed results\n have shown that PIE can ensure low latency and achieve high link\n utilization under various congestion situations. The desig 8033 algorithm algorithms http license management pid subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 8034","type":"specification","body":"IETF","designation":"RFC 8034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8034.txt","https://www.rfc-editor.org/rfc/rfc8034.pdf"],"folder":"IETF/RFC-8034","files":{"txt":{"path":"standards/IETF/RFC-8034/RFC-8034.txt","sha256":"dd69b5f218954bb7f2c7e1e4dfcbc4728979bd27becf7b62fec1b68c3feb7c72"}},"tags":["nested-reference","unchanged"],"summary":"Cable modems based on Data-Over-Cable Service Interface\n Specifications (DOCSIS) provide broadband Internet access to over one\n hundred million users worldwide. In some cases, the cable modem\n connection is the bottleneck (lowest speed) link between the customer\n and the Internet. As a result, the impact of buffering and\n bufferbloat in the cable modem can have a significant effect on user\n experience. The CableLabs DOCSIS 3.1 specification introduces\n requirements for cable modems to support an Active Queue Management\n (AQM) algorithm that is intended to alleviate the impact that\n buffering has on latency-sensitive traffic, while preserving bulk\n throughput performance. In addition, the CableLabs DOCSIS 3.0\n specifications have also been amended to contain similar\n requirements. This document describes the requirements on AQM that\n apply to DOCSIS equipment, including a description of t","scope_keywords":["8034","algorithm","algorithms","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null}],"search_text":"IETF RFC 8034 Cable modems based on Data-Over-Cable Service Interface\n Specifications (DOCSIS) provide broadband Internet access to over one\n hundred million users worldwide. In some cases, the cable modem\n connection is the bottleneck (lowest speed) link between the customer\n and the Internet. As a result, the impact of buffering and\n bufferbloat in the cable modem can have a significant effect on user\n experience. The CableLabs DOCSIS 3.1 specification introduces\n requirements for cable modems to support an Active Queue Management\n (AQM) algorithm that is intended to alleviate the impact that\n buffering has on latency-sensitive traffic, while preserving bulk\n throughput performance. In addition, the CableLabs DOCSIS 3.0\n specifications have also been amended to contain similar\n requirements. This document describes the requirements on AQM that\n apply to DOCSIS equipment, including a description of t 8034 algorithm algorithms http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8572","type":"specification","body":"IETF","designation":"RFC 8572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8572.txt","https://www.rfc-editor.org/rfc/rfc8572.pdf"],"folder":"IETF/RFC-8572","files":{"txt":{"path":"standards/IETF/RFC-8572/RFC-8572.txt","sha256":"122ef74dacde0e080ce9c0ade054d472079d0429b8a4a0fe61f905b4a4e956ff"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a technique to securely provision a networking\n device when it is booting in a factory-default state. Variations in\n the solution enable it to be used on both public and private\n networks. The provisioning steps are able to update the boot image,\n commit an initial configuration, and execute arbitrary scripts to\n address auxiliary needs. The updated device is subsequently able to\n establish secure connections with other systems. For instance, a\n device may establish NETCONF (RFC 6241) and/or RESTCONF (RFC 8040)\n connections with deployment-specific network management systems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering","scope_keywords":["8572","certificate","certificates","encryption","http","https","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 8572 This document presents a technique to securely provision a networking\n device when it is booting in a factory-default state. Variations in\n the solution enable it to be used on both public and private\n networks. The provisioning steps are able to update the boot image,\n commit an initial configuration, and execute arbitrary scripts to\n address auxiliary needs. The updated device is subsequently able to\n establish secure connections with other systems. For instance, a\n device may establish NETCONF (RFC 6241) and/or RESTCONF (RFC 8040)\n connections with deployment-specific network management systems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering 8572 certificate certificates encryption http https key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 9190","type":"specification","body":"IETF","designation":"RFC 9190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9190.txt","https://www.rfc-editor.org/rfc/rfc9190.pdf"],"folder":"IETF/RFC-9190","files":{"pdf":{"path":"standards/IETF/RFC-9190/RFC-9190.pdf","sha256":"a5e0cf1ee4905e69481e1365b80dc401cbbfb8ec23dbb51de2e6cabe97060fd4"},"txt":{"path":"standards/IETF/RFC-9190/RFC-9190.txt","sha256":"009cbd6aa418567ddb9f87fbe32092d17bfc4fbe39457521c5e0129c0a2e464e"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides a standard mechanism for support of multiple authentication\n methods. This document specifies the use of EAP-TLS with TLS 1.3\n while remaining backwards compatible with existing implementations of\n EAP-TLS. TLS 1.3 provides significantly improved security and\n privacy, and reduced latency when compared to earlier versions of\n TLS. EAP-TLS with TLS 1.3 (EAP-TLS 1.3) further improves security\n and privacy by always providing forward secrecy, never disclosing the\n peer identity, and by mandating use of revocation checking when\n compared to EAP-TLS with earlier versions of TLS. This document also\n provides guidance on authentication, authorization, and resumption\n for EAP-TLS in general (regardless of the underlying TLS version\n used). This document updates RFC 5216.\n\nStatus of This Memo\n\n This is an Internet Standa","scope_keywords":["9190","algorithm","algorithms","authentication","authorization","certificate","http","https","key","license","ocsp","revocation","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 9190 The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides a standard mechanism for support of multiple authentication\n methods. This document specifies the use of EAP-TLS with TLS 1.3\n while remaining backwards compatible with existing implementations of\n EAP-TLS. TLS 1.3 provides significantly improved security and\n privacy, and reduced latency when compared to earlier versions of\n TLS. EAP-TLS with TLS 1.3 (EAP-TLS 1.3) further improves security\n and privacy by always providing forward secrecy, never disclosing the\n peer identity, and by mandating use of revocation checking when\n compared to EAP-TLS with earlier versions of TLS. This document also\n provides guidance on authentication, authorization, and resumption\n for EAP-TLS in general (regardless of the underlying TLS version\n used). This document updates RFC 5216.\n\nStatus of This Memo\n\n This is an Internet Standa 9190 algorithm algorithms authentication authorization certificate http https key license ocsp revocation subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9608","type":"specification","body":"IETF","designation":"RFC 9608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9608.txt","https://www.rfc-editor.org/rfc/rfc9608.pdf"],"folder":"IETF/RFC-9608","files":{"pdf":{"path":"standards/IETF/RFC-9608/RFC-9608.pdf","sha256":"c67a447853c848d32c3176d022dc9ff4a1b5270e5a694984c633a4aadad15b33"},"txt":{"path":"standards/IETF/RFC-9608/RFC-9608.txt","sha256":"4952984e5b76585753daf6bf7fc83ad891e6fc40488a2df19752fa90c9abb0c5"}},"tags":["nested-reference","unchanged"],"summary":"X.509v3 public key certificates are profiled in RFC 5280. Short-\n lived certificates are seeing greater use in the Internet. The\n Certification Authority (CA) that issues these short-lived\n certificates do not publish revocation information because the\n certificate lifespan that is shorter than the time needed to detect,\n report, and distribute revocation information. Some long-lived\n X.509v3 public key certificates never expire, and they are never\n revoked. This specification defines the noRevAvail certificate\n extension so that a relying party can readily determine that the CA\n does not publish revocation information for the certificate, and it\n updates the certification path validation algorithm defined in RFC\n 5280 so that revocation checking is skipped when the noRevAvail\n certificate extension is present.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This d","scope_keywords":["9608","algorithm","attribute","authentication","certificate","certificates","http","https","key","license","management","ocsp","path","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"}],"search_text":"IETF RFC 9608 X.509v3 public key certificates are profiled in RFC 5280. Short-\n lived certificates are seeing greater use in the Internet. The\n Certification Authority (CA) that issues these short-lived\n certificates do not publish revocation information because the\n certificate lifespan that is shorter than the time needed to detect,\n report, and distribute revocation information. Some long-lived\n X.509v3 public key certificates never expire, and they are never\n revoked. This specification defines the noRevAvail certificate\n extension so that a relying party can readily determine that the CA\n does not publish revocation information for the certificate, and it\n updates the certification path validation algorithm defined in RFC\n 5280 so that revocation checking is skipped when the noRevAvail\n certificate extension is present.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This d 9608 algorithm attribute authentication certificate certificates http https key license management ocsp path profile revocation signature nested-reference unchanged"},{"id":"IEEE IEEE 802.1-2001","type":"specification","body":"IEEE","designation":"IEEE 802.1-2001","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.1-2001.html","download_urls":["https://standards.ieee.org/standard/802.1-2001.html"],"folder":"IEEE/IEEE-802.1-2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null}],"search_text":"IEEE IEEE 802.1-2001 nested-reference unavailable"},{"id":"IEEE IEEE 802.1.","type":"specification","body":"IEEE","designation":"IEEE 802.1.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.1..html","download_urls":["https://standards.ieee.org/standard/802.1..html"],"folder":"IEEE/IEEE-802.1.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null}],"search_text":"IEEE IEEE 802.1. nested-reference unavailable"},{"id":"IEEE IEEE 802.10","type":"specification","body":"IEEE","designation":"IEEE 802.10","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.10.html","download_urls":["https://standards.ieee.org/standard/802.10.html"],"folder":"IEEE/IEEE-802.10","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IEEE IEEE 802.10 nested-reference unavailable"},{"id":"IEEE IEEE 802.10-1992","type":"specification","body":"IEEE","designation":"IEEE 802.10-1992","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.10-1992.html","download_urls":["https://standards.ieee.org/standard/802.10-1992.html"],"folder":"IEEE/IEEE-802.10-1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null}],"search_text":"IEEE IEEE 802.10-1992 nested-reference unavailable"},{"id":"IEEE IEEE 802.10-1998","type":"specification","body":"IEEE","designation":"IEEE 802.10-1998","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.10-1998.html","download_urls":["https://standards.ieee.org/standard/802.10-1998.html"],"folder":"IEEE/IEEE-802.10-1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null}],"search_text":"IEEE IEEE 802.10-1998 nested-reference unavailable"},{"id":"IEEE IEEE 802.11","type":"specification","body":"IEEE","designation":"IEEE 802.11","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11.html","download_urls":["https://standards.ieee.org/standard/802.11.html"],"folder":"IEEE/IEEE-802.11","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3561","folder":"IETF/RFC-3561","source":"IETF/RFC-3561/RFC-3561.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3990","folder":"IETF/RFC-3990","source":"IETF/RFC-3990/RFC-3990.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 802.11 nested-reference unavailable"},{"id":"IETF RFC 2865","type":"specification","body":"IETF","designation":"RFC 2865","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2865.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2865.txt","https://www.rfc-editor.org/rfc/rfc2865.pdf"],"folder":"IETF/RFC-2865","files":{"txt":{"path":"standards/IETF/RFC-2865/RFC-2865.txt","sha256":"f0e29bff65ae4be6bf1511e31b02a8ab4d60d7f852c2d171ecdd8d664d0562d4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server.\n\nImplementation Note\n\n This memo documents the RADIUS protocol. The early deployment of\n RADIUS was done using UDP port number 1645, which conflicts with the\n \"datametrics\" service. The officially assigned port number for\n RADIUS is 1812.\n\nRigney, et al. Standards Track [Page 1]\n\f\nRFC 2865 RADIUS June 2000","scope_keywords":["2865","attribute","attributes","authentication","authorization","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3423","folder":"IETF/RFC-3423","source":"IETF/RFC-3423/RFC-3423.txt","version":null},{"body":"IETF","designation":"RFC 3457","folder":"IETF/RFC-3457","source":"IETF/RFC-3457/RFC-3457.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 2865 This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server.\n\nImplementation Note\n\n This memo documents the RADIUS protocol. The early deployment of\n RADIUS was done using UDP port number 1645, which conflicts with the\n \"datametrics\" service. The officially assigned port number for\n RADIUS is 1812.\n\nRigney, et al. Standards Track [Page 1]\n\f\nRFC 2865 RADIUS June 2000 2865 attribute attributes authentication authorization policies nested-reference unchanged"},{"id":"IETF RFC 3135","type":"specification","body":"IETF","designation":"RFC 3135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3135.txt","https://www.rfc-editor.org/rfc/rfc3135.pdf"],"folder":"IETF/RFC-3135","files":{"txt":{"path":"standards/IETF/RFC-3135/RFC-3135.txt","sha256":"ae404ea1b4183eb605674d2a47cb61fc9f719a919b9edb0c339737f82692be79"}},"tags":["nested-reference","unchanged"],"summary":"This document is a survey of Performance Enhancing Proxies (PEPs)\n often employed to improve degraded TCP performance caused by\n characteristics of specific link environments, for example, in\n satellite, wireless WAN, and wireless LAN environments. Different\n types of Performance Enhancing Proxies are described as well as the\n mechanisms used to improve performance. Emphasis is put on proxies\n operating with TCP. In addition, motivations for their development\n and use are described along with some of the consequences of using\n them, especially in the context of the Internet.","scope_keywords":["3135","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3238","folder":"IETF/RFC-3238","source":"IETF/RFC-3238/RFC-3238.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 3135 This document is a survey of Performance Enhancing Proxies (PEPs)\n often employed to improve degraded TCP performance caused by\n characteristics of specific link environments, for example, in\n satellite, wireless WAN, and wireless LAN environments. Different\n types of Performance Enhancing Proxies are described as well as the\n mechanisms used to improve performance. Emphasis is put on proxies\n operating with TCP. In addition, motivations for their development\n and use are described along with some of the consequences of using\n them, especially in the context of the Internet. 3135 path nested-reference unchanged"},{"id":"IETF RFC 3366","type":"specification","body":"IETF","designation":"RFC 3366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3366.txt","https://www.rfc-editor.org/rfc/rfc3366.pdf"],"folder":"IETF/RFC-3366","files":{"txt":{"path":"standards/IETF/RFC-3366/RFC-3366.txt","sha256":"67f1fae9c8527dc5f104243880e49f9b0af2e0738c86701c0eb491f33e9c4dc7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides advice to the designers of digital\n communication equipment and link-layer protocols employing link-layer\n Automatic Repeat reQuest (ARQ) techniques. This document presumes\n that the designers wish to support Internet protocols, but may be\n unfamiliar with the architecture of the Internet and with the\n implications of their design choices for the performance and\n efficiency of Internet traffic carried over their links.\n\n ARQ is described in a general way that includes its use over a wide\n range of underlying physical media, including cellular wireless,\n wireless LANs, RF links, and other types of channel. This document\n also describes issues relevant to supporting IP traffic over\n physical-layer channels where performance varies, and where link ARQ\n is likely to be used.\n\nFairhurst & Wood Best Current Practice [Page 1]\n\f\nRFC 3366 Advice to Link Designers on Link AR","scope_keywords":["3366","delivery","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3366 This document provides advice to the designers of digital\n communication equipment and link-layer protocols employing link-layer\n Automatic Repeat reQuest (ARQ) techniques. This document presumes\n that the designers wish to support Internet protocols, but may be\n unfamiliar with the architecture of the Internet and with the\n implications of their design choices for the performance and\n efficiency of Internet traffic carried over their links.\n\n ARQ is described in a general way that includes its use over a wide\n range of underlying physical media, including cellular wireless,\n wireless LANs, RF links, and other types of channel. This document\n also describes issues relevant to supporting IP traffic over\n physical-layer channels where performance varies, and where link ARQ\n is likely to be used.\n\nFairhurst & Wood Best Current Practice [Page 1]\n\f\nRFC 3366 Advice to Link Designers on Link AR 3366 delivery management path subject nested-reference unchanged"},{"id":"IETF RFC 3455","type":"specification","body":"IETF","designation":"RFC 3455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3455.txt","https://www.rfc-editor.org/rfc/rfc3455.pdf"],"folder":"IETF/RFC-3455","files":{"txt":{"path":"standards/IETF/RFC-3455/RFC-3455.txt","sha256":"709ea298a8cc409293ed9888c9da8e84634aee09de3aa773294bb7db4c238d15"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of private Session Initiation Protocol\n (SIP) headers (P-headers) used by the 3rd-Generation Partnership\n Project (3GPP), along with their applicability, which is limited to\n particular environments. The P-headers are for a variety of purposes\n within the networks that the partners use, including charging and\n information about the networks a call traverses.","scope_keywords":["3455","key","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null}],"search_text":"IETF RFC 3455 This document describes a set of private Session Initiation Protocol\n (SIP) headers (P-headers) used by the 3rd-Generation Partnership\n Project (3GPP), along with their applicability, which is limited to\n particular environments. The P-headers are for a variety of purposes\n within the networks that the partners use, including charging and\n information about the networks a call traverses. 3455 key registered trust nested-reference unchanged"},{"id":"IETF RFC 3561","type":"specification","body":"IETF","designation":"RFC 3561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3561.txt","https://www.rfc-editor.org/rfc/rfc3561.pdf"],"folder":"IETF/RFC-3561","files":{"txt":{"path":"standards/IETF/RFC-3561/RFC-3561.txt","sha256":"b3294169ed3e0cf87c1acc1d99ac8b428eec279c563d64fb10cc1c902a60d579"}},"tags":["nested-reference","unchanged"],"summary":"The Ad hoc On-Demand Distance Vector (AODV) routing protocol is\n intended for use by mobile nodes in an ad hoc network. It offers\n quick adaptation to dynamic link conditions, low processing and\n memory overhead, low network utilization, and determines unicast\n routes to destinations within the ad hoc network. It uses\n destination sequence numbers to ensure loop freedom at all times\n (even in the face of anomalous delivery of routing control messages),\n avoiding problems (such as \"counting to infinity\") associated with\n classical distance vector protocols.","scope_keywords":["3561","algorithm","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null}],"search_text":"IETF RFC 3561 The Ad hoc On-Demand Distance Vector (AODV) routing protocol is\n intended for use by mobile nodes in an ad hoc network. It offers\n quick adaptation to dynamic link conditions, low processing and\n memory overhead, low network utilization, and determines unicast\n routes to destinations within the ad hoc network. It uses\n destination sequence numbers to ensure loop freedom at all times\n (even in the face of anomalous delivery of routing control messages),\n avoiding problems (such as \"counting to infinity\") associated with\n classical distance vector protocols. 3561 algorithm delivery path nested-reference unchanged"},{"id":"IETF RFC 3684","type":"specification","body":"IETF","designation":"RFC 3684","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3684.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3684.txt","https://www.rfc-editor.org/rfc/rfc3684.pdf"],"folder":"IETF/RFC-3684","files":{"txt":{"path":"standards/IETF/RFC-3684/RFC-3684.txt","sha256":"9e2bb500a471f69fbc5234a72905b2e93edbc540bfe3c7d6fc57df1e8f487d02"}},"tags":["nested-reference","unchanged"],"summary":"Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) is a\n proactive, link-state routing protocol designed for mobile ad-hoc\n networks, which provides hop-by-hop routing along shortest paths to\n each destination. Each node running TBRPF computes a source tree\n (providing paths to all reachable nodes) based on partial topology\n information stored in its topology table, using a modification of\n Dijkstra's algorithm. To minimize overhead, each node reports only\n *part* of its source tree to neighbors. TBRPF uses a combination of\n periodic and differential updates to keep all neighbors informed of\n the reported part of its source tree. Each node also has the option\n to report additional topology information (up to the full topology),\n to provide improved robustness in highly mobile networks. TBRPF\n performs neighbor discovery using \"differential\" HELLO messages which\n report only ","scope_keywords":["3684","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null}],"search_text":"IETF RFC 3684 Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) is a\n proactive, link-state routing protocol designed for mobile ad-hoc\n networks, which provides hop-by-hop routing along shortest paths to\n each destination. Each node running TBRPF computes a source tree\n (providing paths to all reachable nodes) based on partial topology\n information stored in its topology table, using a modification of\n Dijkstra's algorithm. To minimize overhead, each node reports only\n *part* of its source tree to neighbors. TBRPF uses a combination of\n periodic and differential updates to keep all neighbors informed of\n the reported part of its source tree. Each node also has the option\n to report additional topology information (up to the full topology),\n to provide improved robustness in highly mobile networks. TBRPF\n performs neighbor discovery using \"differential\" HELLO messages which\n report only  3684 algorithm path nested-reference unchanged"},{"id":"IETF RFC 3990","type":"specification","body":"IETF","designation":"RFC 3990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3990.txt","https://www.rfc-editor.org/rfc/rfc3990.pdf"],"folder":"IETF/RFC-3990","files":{"txt":{"path":"standards/IETF/RFC-3990/RFC-3990.txt","sha256":"eb47eefa5b88bcc2c4186e82de9c743a20eeeb314c494cefb1b1b89eab71c253"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. O'Hara\nRequest for Comments: 3990 P. Calhoun\nCategory: Informational Airespace\n J. Kempf\n Docomo Labs USA\n February 2005\n\n Configuration and Provisioning for Wireless Access Points (CAPWAP)\n Problem Statement\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes the Configuration and Provisioning for\n Wireless Access Points (CAPWAP) problem statement.\n\n1. Introduction\n\n With the approval of the 802.11 standard by the IEEE in 1997,\n wireless LANs (WLANs) began a slow entry into enterprise networks.\n The limited data rates of the original 802.11 standard, only 1 and 2\n Mbps, limited the widespread adoption of the technology. 802.11\n found wide de","scope_keywords":["3990","authorization","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null}],"search_text":"IETF RFC 3990 Network Working Group B. O'Hara\nRequest for Comments: 3990 P. Calhoun\nCategory: Informational Airespace\n J. Kempf\n Docomo Labs USA\n February 2005\n\n Configuration and Provisioning for Wireless Access Points (CAPWAP)\n Problem Statement\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes the Configuration and Provisioning for\n Wireless Access Points (CAPWAP) problem statement.\n\n1. Introduction\n\n With the approval of the 802.11 standard by the IEEE in 1997,\n wireless LANs (WLANs) began a slow entry into enterprise networks.\n The limited data rates of the original 802.11 standard, only 1 and 2\n Mbps, limited the widespread adoption of the technology. 802.11\n found wide de 3990 authorization delivery management nested-reference unchanged"},{"id":"IETF RFC 4065","type":"specification","body":"IETF","designation":"RFC 4065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4065.txt","https://www.rfc-editor.org/rfc/rfc4065.pdf"],"folder":"IETF/RFC-4065","files":{"txt":{"path":"standards/IETF/RFC-4065/RFC-4065.txt","sha256":"a00d7c8a68b785d0b6cd8ea8c870c07d7ebd8c2a38a52606196fd8a060da587a"}},"tags":["nested-reference","unchanged"],"summary":"The Seamoby Candidate Access Router Discovery (CARD) protocol and the\n Context Transfer Protocol (CXTP) are experimental protocols designed\n to accelerate IP handover between wireless access routers. These\n protocols require IANA allocations for ICMP type and options, Stream\n Control Transmission Protocol (SCTP) Payload Protocol Identifiers,\n port numbers, and registries for certain formatted message options.\n This document contains instructions to IANA about which allocations\n are required for the Seamoby protocols. The ICMP subtype extension\n format for Seamoby has been additionally designed so that it can be\n utilized by other experimental mobility protocols, and the SCTP port\n number is also available for other experimental mobility protocols.\n\nKempf Experimental [Page 1]\n\f\nRFC 4065 Seamoby IANA Allocations July 2005","scope_keywords":["4065","algorithm","authorization","key","policy","profile","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null}],"search_text":"IETF RFC 4065 The Seamoby Candidate Access Router Discovery (CARD) protocol and the\n Context Transfer Protocol (CXTP) are experimental protocols designed\n to accelerate IP handover between wireless access routers. These\n protocols require IANA allocations for ICMP type and options, Stream\n Control Transmission Protocol (SCTP) Payload Protocol Identifiers,\n port numbers, and registries for certain formatted message options.\n This document contains instructions to IANA about which allocations\n are required for the Seamoby protocols. The ICMP subtype extension\n format for Seamoby has been additionally designed so that it can be\n utilized by other experimental mobility protocols, and the SCTP port\n number is also available for other experimental mobility protocols.\n\nKempf Experimental [Page 1]\n\f\nRFC 4065 Seamoby IANA Allocations July 2005 4065 algorithm authorization key policy profile signature nested-reference unchanged"},{"id":"IETF RFC 4086","type":"specification","body":"IETF","designation":"RFC 4086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4086.txt","https://www.rfc-editor.org/rfc/rfc4086.pdf"],"folder":"IETF/RFC-4086","files":{"txt":{"path":"standards/IETF/RFC-4086/RFC-4086.txt","sha256":"d2c111e67e7628c3de41887c79ed87d0ba69ef1310eeb6698bdfb17fb9651589"}},"tags":["nested-reference","unchanged"],"summary":"Security systems are built on strong cryptographic algorithms that\n foil pattern analysis attempts. However, the security of these\n systems is dependent on generating secret quantities for passwords,\n cryptographic keys, and similar quantities. The use of pseudo-random\n processes to generate secret quantities can result in pseudo-\n security. A sophisticated attacker may find it easier to reproduce\n the environment that produced the secret quantities and to search the\n resulting small set of possibilities than to locate the quantities in\n the whole of the potential number space.\n\n Choosing random quantities to foil a resourceful and motivated\n adversary is surprisingly difficult. This document points out many\n pitfalls in using poor entropy sources or traditional pseudo-random\n number generation techniques for generating such quantities. It\n recommends the use of truly random hardware tec","scope_keywords":["4086","algorithm","algorithms","key","keys","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4226","folder":"IETF/RFC-4226","source":"IETF/RFC-4226/RFC-4226.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4401","folder":"IETF/RFC-4401","source":"IETF/RFC-4401/RFC-4401.txt","version":null},{"body":"IETF","designation":"RFC 4449","folder":"IETF/RFC-4449","source":"IETF/RFC-4449/RFC-4449.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4493","folder":"IETF/RFC-4493","source":"IETF/RFC-4493/RFC-4493.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4615","folder":"IETF/RFC-4615","source":"IETF/RFC-4615/RFC-4615.txt","version":null},{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5083","folder":"IETF/RFC-5083","source":"IETF/RFC-5083/RFC-5083.txt","version":null},{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8032","folder":"IETF/RFC-8032","source":"IETF/RFC-8032/RFC-8032.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9021","folder":"IETF/RFC-9021","source":"IETF/RFC-9021/RFC-9021.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 4086 Security systems are built on strong cryptographic algorithms that\n foil pattern analysis attempts. However, the security of these\n systems is dependent on generating secret quantities for passwords,\n cryptographic keys, and similar quantities. The use of pseudo-random\n processes to generate secret quantities can result in pseudo-\n security. A sophisticated attacker may find it easier to reproduce\n the environment that produced the secret quantities and to search the\n resulting small set of possibilities than to locate the quantities in\n the whole of the potential number space.\n\n Choosing random quantities to foil a resourceful and motivated\n adversary is surprisingly difficult. This document points out many\n pitfalls in using poor entropy sources or traditional pseudo-random\n number generation techniques for generating such quantities. It\n recommends the use of truly random hardware tec 4086 algorithm algorithms key keys tls nested-reference unchanged"},{"id":"IETF RFC 4093","type":"specification","body":"IETF","designation":"RFC 4093","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4093.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4093.txt","https://www.rfc-editor.org/rfc/rfc4093.pdf"],"folder":"IETF/RFC-4093","files":{"txt":{"path":"standards/IETF/RFC-4093/RFC-4093.txt","sha256":"544aecb7d07844421cdd821fb1e2b88cbb216a31a9ebc80621c07a7d7d1f73aa"}},"tags":["nested-reference","unchanged"],"summary":"Deploying Mobile-IP v4 in networks that are connected to the Internet\n through a Virtual Private Network (VPN) gateway presents some\n problems that do not currently have well-described solutions. This\n document aims to describe and illustrate these problems, and to\n propose some guidelines for possible solutions.","scope_keywords":["4093","delivery","key","policies","preservation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4093 Deploying Mobile-IP v4 in networks that are connected to the Internet\n through a Virtual Private Network (VPN) gateway presents some\n problems that do not currently have well-described solutions. This\n document aims to describe and illustrate these problems, and to\n propose some guidelines for possible solutions. 4093 delivery key policies preservation trust nested-reference unchanged"},{"id":"IETF RFC 4186","type":"specification","body":"IETF","designation":"RFC 4186","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4186.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4186.txt","https://www.rfc-editor.org/rfc/rfc4186.pdf"],"folder":"IETF/RFC-4186","files":{"txt":{"path":"standards/IETF/RFC-4186/RFC-4186.txt","sha256":"f6eb86de6d7f85a992e3f13f89df5a270c52442b6a980407e0dcd044ff543be1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for authentication and session key distribution using the\n Global System for Mobile Communications (GSM) Subscriber Identity\n Module (SIM). GSM is a second generation mobile network standard.\n The EAP-SIM mechanism specifies enhancements to GSM authentication\n and key agreement whereby multiple authentication triplets can be\n combined to create authentication responses and session keys of\n greater strength than the individual GSM triplets. The mechanism\n also includes network authentication, user anonymity support, result\n indications, and a fast re-authentication procedure.\n\nHaverinen & Salowey Informational [Page 1]\n\f\nRFC 4186 EAP-SIM Authentication January 2006","scope_keywords":["4186","algorithm","algorithms","attribute","attributes","authentication","key","keys","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null}],"search_text":"IETF RFC 4186 This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for authentication and session key distribution using the\n Global System for Mobile Communications (GSM) Subscriber Identity\n Module (SIM). GSM is a second generation mobile network standard.\n The EAP-SIM mechanism specifies enhancements to GSM authentication\n and key agreement whereby multiple authentication triplets can be\n combined to create authentication responses and session keys of\n greater strength than the individual GSM triplets. The mechanism\n also includes network authentication, user anonymity support, result\n indications, and a fast re-authentication procedure.\n\nHaverinen & Salowey Informational [Page 1]\n\f\nRFC 4186 EAP-SIM Authentication January 2006 4186 algorithm algorithms attribute attributes authentication key keys management validation nested-reference unchanged"},{"id":"IETF RFC 4187","type":"specification","body":"IETF","designation":"RFC 4187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4187.txt","https://www.rfc-editor.org/rfc/rfc4187.pdf"],"folder":"IETF/RFC-4187","files":{"txt":{"path":"standards/IETF/RFC-4187/RFC-4187.txt","sha256":"383688f625086ba98517dc6da4c51269b63d11f0bc22253c3302731070fde05e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for authentication and session key distribution that uses\n the Authentication and Key Agreement (AKA) mechanism. AKA is used in\n the 3rd generation mobile networks Universal Mobile\n Telecommunications System (UMTS) and CDMA2000. AKA is based on\n symmetric keys, and typically runs in a Subscriber Identity Module,\n which is a UMTS Subscriber Identity Module, USIM, or a (Removable)\n User Identity Module, (R)UIM, similar to a smart card.\n\n EAP-AKA includes optional identity privacy support, optional result\n indications, and an optional fast re-authentication procedure.\n\nArkko & Haverinen Informational [Page 1]\n\f\nRFC 4187 EAP-AKA Authentication January 2006","scope_keywords":["4187","algorithm","algorithms","attribute","attributes","authentication","key","keys","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 4187 This document specifies an Extensible Authentication Protocol (EAP)\n mechanism for authentication and session key distribution that uses\n the Authentication and Key Agreement (AKA) mechanism. AKA is used in\n the 3rd generation mobile networks Universal Mobile\n Telecommunications System (UMTS) and CDMA2000. AKA is based on\n symmetric keys, and typically runs in a Subscriber Identity Module,\n which is a UMTS Subscriber Identity Module, USIM, or a (Removable)\n User Identity Module, (R)UIM, similar to a smart card.\n\n EAP-AKA includes optional identity privacy support, optional result\n indications, and an optional fast re-authentication procedure.\n\nArkko & Haverinen Informational [Page 1]\n\f\nRFC 4187 EAP-AKA Authentication January 2006 4187 algorithm algorithms attribute attributes authentication key keys management validation nested-reference unchanged"},{"id":"IETF RFC 4282","type":"specification","body":"IETF","designation":"RFC 4282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4282.txt","https://www.rfc-editor.org/rfc/rfc4282.pdf"],"folder":"IETF/RFC-4282","files":{"txt":{"path":"standards/IETF/RFC-4282/RFC-4282.txt","sha256":"7274047459eac68c52416cae94fbc178f786dc7153a9bac3a887fa7c92450a57"}},"tags":["nested-reference","unchanged"],"summary":"In order to provide roaming services, it is necessary to have a\n standardized method for identifying users. This document defines the\n syntax for the Network Access Identifier (NAI), the user identity\n submitted by the client during network authentication. \"Roaming\" may\n be loosely defined as the ability to use any one of multiple Internet\n Service Providers (ISPs), while maintaining a formal, customer-vendor\n relationship with only one. Examples of where roaming capabilities\n might be required include ISP \"confederations\" and ISP-provided\n corporate network access support. This document is a revised version\n of RFC 2486, which originally defined NAIs. Enhancements include\n international character set and privacy support, as well as a number\n of corrections to the original RFC.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 4282 The Network Access Identifier December 2005","scope_keywords":["4282","authentication","key","pid","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 4282 In order to provide roaming services, it is necessary to have a\n standardized method for identifying users. This document defines the\n syntax for the Network Access Identifier (NAI), the user identity\n submitted by the client during network authentication. \"Roaming\" may\n be loosely defined as the ability to use any one of multiple Internet\n Service Providers (ISPs), while maintaining a formal, customer-vendor\n relationship with only one. Examples of where roaming capabilities\n might be required include ISP \"confederations\" and ISP-provided\n corporate network access support. This document is a revised version\n of RFC 2486, which originally defined NAIs. Enhancements include\n international character set and privacy support, as well as a number\n of corrections to the original RFC.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 4282 The Network Access Identifier December 2005 4282 authentication key pid tsp nested-reference unchanged"},{"id":"IETF RFC 4284","type":"specification","body":"IETF","designation":"RFC 4284","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4284.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4284.txt","https://www.rfc-editor.org/rfc/rfc4284.pdf"],"folder":"IETF/RFC-4284","files":{"txt":{"path":"standards/IETF/RFC-4284/RFC-4284.txt","sha256":"d87828f3a99a2f9c0e02216f464da4a30cdca6aef4c3782fbf14fe5d31303300"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) is defined in RFC 3748.\n This document defines a mechanism that allows an access network to\n provide identity selection hints to an EAP peer -- the end of the\n link that responds to the authenticator. The purpose is to assist\n the EAP peer in selecting an appropriate Network Access Identifier\n (NAI). This is useful in situations where the peer does not receive\n a lower-layer indication of what network it is connecting to, or when\n there is no direct roaming relationship between the access network\n and the peer's home network. In the latter case, authentication is\n typically accomplished via a mediating network such as a roaming\n consortium or broker.\n\n The mechanism defined in this document is limited in its scalability.\n It is intended for access networks that have a small to moderate\n number of direct roaming partners.\n\nAdrangi, et al. Infor","scope_keywords":["4284","attribute","attributes","authentication","authorization","credential","credentials","delivery","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null}],"search_text":"IETF RFC 4284 The Extensible Authentication Protocol (EAP) is defined in RFC 3748.\n This document defines a mechanism that allows an access network to\n provide identity selection hints to an EAP peer -- the end of the\n link that responds to the authenticator. The purpose is to assist\n the EAP peer in selecting an appropriate Network Access Identifier\n (NAI). This is useful in situations where the peer does not receive\n a lower-layer indication of what network it is connecting to, or when\n there is no direct roaming relationship between the access network\n and the peer's home network. In the latter case, authentication is\n typically accomplished via a mediating network such as a roaming\n consortium or broker.\n\n The mechanism defined in this document is limited in its scalability.\n It is intended for access networks that have a small to moderate\n number of direct roaming partners.\n\nAdrangi, et al. Infor 4284 attribute attributes authentication authorization credential credentials delivery key path policy nested-reference unchanged"},{"id":"IETF RFC 4305","type":"specification","body":"IETF","designation":"RFC 4305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4305.txt","https://www.rfc-editor.org/rfc/rfc4305.pdf"],"folder":"IETF/RFC-4305","files":{"txt":{"path":"standards/IETF/RFC-4305/RFC-4305.txt","sha256":"9612cbbf23d4d0da1d835f6ffbf1ec59b104489602e018d1fa74e36030485cdb"}},"tags":["nested-reference","unchanged"],"summary":"The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Encapsulating\n Security Payload (ESP) and the Authentication Header (AH) provide two\n mechanisms for protecting data being sent over an IPsec Security\n Association (SA). To ensure interoperability between disparate\n implementations, it is necessary to specify a set of mandatory-to-\n implement algorithms to ensure that there is at least one algorithm\n that all implementations will have available. This document defines\n the current set of mandatory-to-implement algorithms for ESP and AH\n as well as specifying algorithms that should be implemented because\n they may be promoted to mandatory at some future time.\n\nEastlake Standards Track [Page 1]\n\f\nRFC 4305 Cryptographic Algorithms for ESP & AH December 2005","scope_keywords":["4305","algorithm","algorithms","authentication","encryption","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 4305 The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Encapsulating\n Security Payload (ESP) and the Authentication Header (AH) provide two\n mechanisms for protecting data being sent over an IPsec Security\n Association (SA). To ensure interoperability between disparate\n implementations, it is necessary to specify a set of mandatory-to-\n implement algorithms to ensure that there is at least one algorithm\n that all implementations will have available. This document defines\n the current set of mandatory-to-implement algorithms for ESP and AH\n as well as specifying algorithms that should be implemented because\n they may be promoted to mandatory at some future time.\n\nEastlake Standards Track [Page 1]\n\f\nRFC 4305 Cryptographic Algorithms for ESP & AH December 2005 4305 algorithm algorithms authentication encryption key keys subject nested-reference unchanged"},{"id":"IETF RFC 4309","type":"specification","body":"IETF","designation":"RFC 4309","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4309.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4309.txt","https://www.rfc-editor.org/rfc/rfc4309.pdf"],"folder":"IETF/RFC-4309","files":{"txt":{"path":"standards/IETF/RFC-4309/RFC-4309.txt","sha256":"a78a2ff2eca0eb2aaebd351feb984634dbd9c4fd0e0d95e517c7ddb74720fc91"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of Advanced Encryption Standard (AES)\n in Counter with CBC-MAC (CCM) Mode, with an explicit initialization\n vector (IV), as an IPsec Encapsulating Security Payload (ESP)\n mechanism to provide confidentiality, data origin authentication, and\n connectionless integrity.","scope_keywords":["4309","attribute","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 4309 This document describes the use of Advanced Encryption Standard (AES)\n in Counter with CBC-MAC (CCM) Mode, with an explicit initialization\n vector (IV), as an IPsec Encapsulating Security Payload (ESP)\n mechanism to provide confidentiality, data origin authentication, and\n connectionless integrity. 4309 attribute authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 4651","type":"specification","body":"IETF","designation":"RFC 4651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4651.txt","https://www.rfc-editor.org/rfc/rfc4651.pdf"],"folder":"IETF/RFC-4651","files":{"txt":{"path":"standards/IETF/RFC-4651/RFC-4651.txt","sha256":"b16ed3cde16aa933bf3ff26009c4d075e782d9315c62421fe220335c162b3f11"}},"tags":["nested-reference","unchanged"],"summary":"This document describes and evaluates strategies to enhance Mobile\n IPv6 Route Optimization, on the basis of existing proposals, in order\n to motivate and guide further research in this context. This\n document is a product of the IP Mobility Optimizations (MobOpts)\n Research Group.\n\nVogt & Arkko Informational [Page 1]\n\f\nRFC 4651 MIP6 Route Optimization Enhancements February 2007","scope_keywords":["4651","authentication","authorization","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null}],"search_text":"IETF RFC 4651 This document describes and evaluates strategies to enhance Mobile\n IPv6 Route Optimization, on the basis of existing proposals, in order\n to motivate and guide further research in this context. This\n document is a product of the IP Mobility Optimizations (MobOpts)\n Research Group.\n\nVogt & Arkko Informational [Page 1]\n\f\nRFC 4651 MIP6 Route Optimization Enhancements February 2007 4651 authentication authorization key path trust nested-reference unchanged"},{"id":"IETF RFC 4732","type":"specification","body":"IETF","designation":"RFC 4732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4732.txt","https://www.rfc-editor.org/rfc/rfc4732.pdf"],"folder":"IETF/RFC-4732","files":{"txt":{"path":"standards/IETF/RFC-4732/RFC-4732.txt","sha256":"27b3234d711d81f19c004c9387de4741ebd54ed6dd4c4c541587c064d5151eff"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of possible avenues for denial-\n of-service (DoS) attack on Internet systems. The aim is to encourage\n protocol designers and network engineers towards designs that are\n more robust. We discuss partial solutions that reduce the\n effectiveness of attacks, and how some solutions might inadvertently\n open up alternative vulnerabilities.\n\nHandley, et al. Informational [Page 1]\n\f\nRFC 4732 DoS Considerations November 2006","scope_keywords":["4732","authentication","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6386","folder":"IETF/RFC-6386","source":"IETF/RFC-6386/RFC-6386.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 4732 This document provides an overview of possible avenues for denial-\n of-service (DoS) attack on Internet systems. The aim is to encourage\n protocol designers and network engineers towards designs that are\n more robust. We discuss partial solutions that reduce the\n effectiveness of attacks, and how some solutions might inadvertently\n open up alternative vulnerabilities.\n\nHandley, et al. Informational [Page 1]\n\f\nRFC 4732 DoS Considerations November 2006 4732 authentication trust nested-reference unchanged"},{"id":"IETF RFC 4746","type":"specification","body":"IETF","designation":"RFC 4746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4746.txt","https://www.rfc-editor.org/rfc/rfc4746.pdf"],"folder":"IETF/RFC-4746","files":{"txt":{"path":"standards/IETF/RFC-4746/RFC-4746.txt","sha256":"503d8b7f68b395c5072ce546be807223a8fa3b9cb9f290aefebc56a216e82956"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Extensible Authentication Protocol (EAP)\n method called EAP-PAX (Password Authenticated eXchange). This method\n is a lightweight shared-key authentication protocol with optional\n support for key provisioning, key management, identity protection,\n and authenticated data exchange.","scope_keywords":["4746","authentication","certificate","certificates","identification","key","keys","management","pki","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null}],"search_text":"IETF RFC 4746 This document defines an Extensible Authentication Protocol (EAP)\n method called EAP-PAX (Password Authenticated eXchange). This method\n is a lightweight shared-key authentication protocol with optional\n support for key provisioning, key management, identity protection,\n and authenticated data exchange. 4746 authentication certificate certificates identification key keys management pki policies trust nested-reference unchanged"},{"id":"IETF RFC 4764","type":"specification","body":"IETF","designation":"RFC 4764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4764.txt","https://www.rfc-editor.org/rfc/rfc4764.pdf"],"folder":"IETF/RFC-4764","files":{"txt":{"path":"standards/IETF/RFC-4764/RFC-4764.txt","sha256":"c889dfe87390ed1bbcaae5919c6d4421d6546d4328da04d1f7a9b9cc2a128e60"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies EAP-PSK, an Extensible Authentication\n Protocol (EAP) method for mutual authentication and session key\n derivation using a Pre-Shared Key (PSK). EAP-PSK provides a\n protected communication channel when mutual authentication is\n successful for both parties to communicate over. This document\n describes the use of this channel only for protected exchange of\n result indications, but future EAP-PSK extensions may use the channel\n for other purposes. EAP-PSK is designed for authentication over\n insecure networks such as IEEE 802.11.\n\nBersani & Tschofenig Experimental [Page 1]\n\f\nRFC 4764 EAP-PSK January 2007","scope_keywords":["4764","authentication","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null}],"search_text":"IETF RFC 4764 This document specifies EAP-PSK, an Extensible Authentication\n Protocol (EAP) method for mutual authentication and session key\n derivation using a Pre-Shared Key (PSK). EAP-PSK provides a\n protected communication channel when mutual authentication is\n successful for both parties to communicate over. This document\n describes the use of this channel only for protected exchange of\n result indications, but future EAP-PSK extensions may use the channel\n for other purposes. EAP-PSK is designed for authentication over\n insecure networks such as IEEE 802.11.\n\nBersani & Tschofenig Experimental [Page 1]\n\f\nRFC 4764 EAP-PSK January 2007 4764 authentication key trust nested-reference unchanged"},{"id":"IETF RFC 4831","type":"specification","body":"IETF","designation":"RFC 4831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4831.txt","https://www.rfc-editor.org/rfc/rfc4831.pdf"],"folder":"IETF/RFC-4831","files":{"txt":{"path":"standards/IETF/RFC-4831/RFC-4831.txt","sha256":"53b3504108e2b01067de188f81548e4f83c30a7059fec086ee0fdd056570a6a4"}},"tags":["nested-reference","unchanged"],"summary":"In this document, design goals for a network-based localized mobility\n management (NETLMM) protocol are discussed.","scope_keywords":["4831","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null}],"search_text":"IETF RFC 4831 In this document, design goals for a network-based localized mobility\n management (NETLMM) protocol are discussed. 4831 management trust nested-reference unchanged"},{"id":"IETF RFC 5006","type":"specification","body":"IETF","designation":"RFC 5006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5006.txt","https://www.rfc-editor.org/rfc/rfc5006.pdf"],"folder":"IETF/RFC-5006","files":{"txt":{"path":"standards/IETF/RFC-5006/RFC-5006.txt","sha256":"7df20ff5a106a1ffa899e057baa159c57bbfbe977762ecf2985dd40d4631e3bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new IPv6 Router Advertisement option to\n allow IPv6 routers to advertise DNS recursive server addresses to\n IPv6 hosts.","scope_keywords":["5006","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 5006 This document specifies a new IPv6 Router Advertisement option to\n allow IPv6 routers to advertise DNS recursive server addresses to\n IPv6 hosts. 5006 key management nested-reference unchanged"},{"id":"IETF RFC 5169","type":"specification","body":"IETF","designation":"RFC 5169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5169.txt","https://www.rfc-editor.org/rfc/rfc5169.pdf"],"folder":"IETF/RFC-5169","files":{"txt":{"path":"standards/IETF/RFC-5169/RFC-5169.txt","sha256":"477f2a8ba8165227a57c988915c9852b469899f40c260456ea5ca7c1f9d544e8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Handover Keying (HOKEY) re-authentication\n problem statement. The current Extensible Authentication Protocol\n (EAP) keying framework is not designed to support re-authentication\n and handovers without re-executing an EAP method. This often causes\n unacceptable latency in various mobile wireless environments. This\n document details the problem and defines design goals for a generic\n mechanism to reuse derived EAP keying material for handover.\n\nClancy, et al. Informational [Page 1]\n\f\nRFC 5169 HOKEY Re-Auth PS March 2008","scope_keywords":["5169","authentication","authorization","encryption","key","keys","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null}],"search_text":"IETF RFC 5169 This document describes the Handover Keying (HOKEY) re-authentication\n problem statement. The current Extensible Authentication Protocol\n (EAP) keying framework is not designed to support re-authentication\n and handovers without re-executing an EAP method. This often causes\n unacceptable latency in various mobile wireless environments. This\n document details the problem and defines design goals for a generic\n mechanism to reuse derived EAP keying material for handover.\n\nClancy, et al. Informational [Page 1]\n\f\nRFC 5169 HOKEY Re-Auth PS March 2008 5169 authentication authorization encryption key keys management tls nested-reference unchanged"},{"id":"IETF RFC 5181","type":"specification","body":"IETF","designation":"RFC 5181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5181.txt","https://www.rfc-editor.org/rfc/rfc5181.pdf"],"folder":"IETF/RFC-5181","files":{"txt":{"path":"standards/IETF/RFC-5181/RFC-5181.txt","sha256":"2fd6d6d4d1574480537809dfe9658ceedef90afa73f6d9185b558fc94c0c7a12"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a detailed description of IPv6 deployment and\n integration methods and scenarios in wireless broadband access\n networks in coexistence with deployed IPv4 services. In this\n document, we will discuss the main components of IPv6 IEEE 802.16\n access networks and their differences from IPv4 IEEE 802.16 networks\n and how IPv6 is deployed and integrated in each of the IEEE 802.16\n technologies.","scope_keywords":["5181","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5181 This document provides a detailed description of IPv6 deployment and\n integration methods and scenarios in wireless broadband access\n networks in coexistence with deployed IPv4 services. In this\n document, we will discuss the main components of IPv6 IEEE 802.16\n access networks and their differences from IPv4 IEEE 802.16 networks\n and how IPv6 is deployed and integrated in each of the IEEE 802.16\n technologies. 5181 key management nested-reference unchanged"},{"id":"IETF RFC 5184","type":"specification","body":"IETF","designation":"RFC 5184","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5184.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5184.txt","https://www.rfc-editor.org/rfc/rfc5184.pdf"],"folder":"IETF/RFC-5184","files":{"txt":{"path":"standards/IETF/RFC-5184/RFC-5184.txt","sha256":"32147d50db7ce26e51804218e241985297495cb4e9c5a9394b34807450b15a4e"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes unified Layer 2 (L2) abstractions for Layer 3\n (L3)-driven fast handovers. For efficient network communication, it\n is vital for a protocol layer to know or utilize other layers'\n information, such as the form of L2 triggers. However, each protocol\n layer is basically designed independently. Since each protocol layer\n is also implemented independently in current operating systems, it is\n very hard to exchange control information between protocol layers.\n This document defines nine kinds of L2 abstractions in the form of\n \"primitives\" to achieve fast handovers in the network layer as a\n means of solving the problem. This mechanism is called \"L3-driven\n fast handovers\" because the network layer initiates L2 and L3\n handovers by using the primitives. This document is a product of the\n IP Mobility Optimizations (MobOpts) Research Group.\n\nTeraoka, et al. Experimental [P","scope_keywords":["5184","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null}],"search_text":"IETF RFC 5184 This document proposes unified Layer 2 (L2) abstractions for Layer 3\n (L3)-driven fast handovers. For efficient network communication, it\n is vital for a protocol layer to know or utilize other layers'\n information, such as the form of L2 triggers. However, each protocol\n layer is basically designed independently. Since each protocol layer\n is also implemented independently in current operating systems, it is\n very hard to exchange control information between protocol layers.\n This document defines nine kinds of L2 abstractions in the form of\n \"primitives\" to achieve fast handovers in the network layer as a\n means of solving the problem. This mechanism is called \"L3-driven\n fast handovers\" because the network layer initiates L2 and L3\n handovers by using the primitives. This document is a product of the\n IP Mobility Optimizations (MobOpts) Research Group.\n\nTeraoka, et al. Experimental [P 5184 pid nested-reference unchanged"},{"id":"IETF RFC 5193","type":"specification","body":"IETF","designation":"RFC 5193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5193.txt","https://www.rfc-editor.org/rfc/rfc5193.pdf"],"folder":"IETF/RFC-5193","files":{"txt":{"path":"standards/IETF/RFC-5193/RFC-5193.txt","sha256":"78ead18cc3d16232e859a4ef9004887a74476cc8bce26966ae6a584de6c3b890"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the general Protocol for Carrying\n Authentication for Network Access (PANA) framework functional\n elements, high-level call flow, and deployment environments.","scope_keywords":["5193","attribute","attributes","authentication","authorization","credential","credentials","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null}],"search_text":"IETF RFC 5193 This document defines the general Protocol for Carrying\n Authentication for Network Access (PANA) framework functional\n elements, high-level call flow, and deployment environments. 5193 attribute attributes authentication authorization credential credentials key nested-reference unchanged"},{"id":"IETF RFC 5213","type":"specification","body":"IETF","designation":"RFC 5213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5213.txt","https://www.rfc-editor.org/rfc/rfc5213.pdf"],"folder":"IETF/RFC-5213","files":{"txt":{"path":"standards/IETF/RFC-5213/RFC-5213.txt","sha256":"dbbe795eae1ad8a6c0950d7ebc147a766a48887efd9b90ef7a95bd370a3628b8"}},"tags":["nested-reference","unchanged"],"summary":"Network-based mobility management enables IP mobility for a host\n without requiring its participation in any mobility-related\n signaling. The network is responsible for managing IP mobility on\n behalf of the host. The mobility entities in the network are\n responsible for tracking the movements of the host and initiating the\n required mobility signaling on its behalf. This specification\n describes a network-based mobility management protocol and is\n referred to as Proxy Mobile IPv6.\n\nGundavelli, et al. Standards Track [Page 1]\n\f\nRFC 5213 Proxy Mobile IPv6 August 2008","scope_keywords":["5213","authentication","authorization","identification","management","path","policy","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null}],"search_text":"IETF RFC 5213 Network-based mobility management enables IP mobility for a host\n without requiring its participation in any mobility-related\n signaling. The network is responsible for managing IP mobility on\n behalf of the host. The mobility entities in the network are\n responsible for tracking the movements of the host and initiating the\n required mobility signaling on its behalf. This specification\n describes a network-based mobility management protocol and is\n referred to as Proxy Mobile IPv6.\n\nGundavelli, et al. Standards Track [Page 1]\n\f\nRFC 5213 Proxy Mobile IPv6 August 2008 5213 authentication authorization identification management path policy profile timestamp nested-reference unchanged"},{"id":"IETF RFC 5218","type":"specification","body":"IETF","designation":"RFC 5218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5218.txt","https://www.rfc-editor.org/rfc/rfc5218.pdf"],"folder":"IETF/RFC-5218","files":{"txt":{"path":"standards/IETF/RFC-5218/RFC-5218.txt","sha256":"6515a30b344d20732a3d05baed487f2b372edb592eb811a22a2ea9132ba497fd"}},"tags":["nested-reference","unchanged"],"summary":"The Internet community has specified a large number of protocols to\n date, and these protocols have achieved varying degrees of success.\n Based on case studies, this document attempts to ascertain factors\n that contribute to or hinder a protocol's success. It is hoped that\n these observations can serve as guidance for future protocol work.","scope_keywords":["5218","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null}],"search_text":"IETF RFC 5218 The Internet community has specified a large number of protocols to\n date, and these protocols have achieved varying degrees of success.\n Based on case studies, this document attempts to ascertain factors\n that contribute to or hinder a protocol's success. It is hoped that\n these observations can serve as guidance for future protocol work. 5218 http nested-reference unchanged"},{"id":"IETF RFC 5265","type":"specification","body":"IETF","designation":"RFC 5265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5265.txt","https://www.rfc-editor.org/rfc/rfc5265.pdf"],"folder":"IETF/RFC-5265","files":{"txt":{"path":"standards/IETF/RFC-5265/RFC-5265.txt","sha256":"d1328baa0a9ec7b6fb55487863b98008347a32e184e2a71168bc30e461a2ec82"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines a solution for the Mobile IPv4 (MIPv4) and\n IPsec coexistence problem for enterprise users. The solution\n consists of an applicability statement for using Mobile IPv4 and\n IPsec for session mobility in corporate remote access scenarios, and\n a required mechanism for detecting the trusted internal network\n securely.","scope_keywords":["5265","algorithm","encryption","key","management","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5265 This document outlines a solution for the Mobile IPv4 (MIPv4) and\n IPsec coexistence problem for enterprise users. The solution\n consists of an applicability statement for using Mobile IPv4 and\n IPsec for session mobility in corporate remote access scenarios, and\n a required mechanism for detecting the trusted internal network\n securely. 5265 algorithm encryption key management policies trust nested-reference unchanged"},{"id":"IETF RFC 5320","type":"specification","body":"IETF","designation":"RFC 5320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5320.txt","https://www.rfc-editor.org/rfc/rfc5320.pdf"],"folder":"IETF/RFC-5320","files":{"txt":{"path":"standards/IETF/RFC-5320/RFC-5320.txt","sha256":"f142ddfb15043594dfa7daff2d500debf890cd8feef2fbab358681953c7343f5"}},"tags":["nested-reference","unchanged"],"summary":"For the purpose of this document, subnetworks are defined as virtual\n topologies that span connected network regions bounded by\n encapsulating border nodes. These virtual topologies may span\n multiple IP and/or sub-IP layer forwarding hops, and can introduce\n failure modes due to packet duplication and/or links with diverse\n Maximum Transmission Units (MTUs). This document specifies a\n Subnetwork Encapsulation and Adaptation Layer (SEAL) that\n accommodates such virtual topologies over diverse underlying link\n technologies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n d","scope_keywords":["5320","http","identification","license","path","seal","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null}],"search_text":"IETF RFC 5320 For the purpose of this document, subnetworks are defined as virtual\n topologies that span connected network regions bounded by\n encapsulating border nodes. These virtual topologies may span\n multiple IP and/or sub-IP layer forwarding hops, and can introduce\n failure modes due to packet duplication and/or links with diverse\n Maximum Transmission Units (MTUs). This document specifies a\n Subnetwork Encapsulation and Adaptation Layer (SEAL) that\n accommodates such virtual topologies over diverse underlying link\n technologies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n d 5320 http identification license path seal subject trust nested-reference unchanged"},{"id":"IETF RFC 5415","type":"specification","body":"IETF","designation":"RFC 5415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5415.txt","https://www.rfc-editor.org/rfc/rfc5415.pdf"],"folder":"IETF/RFC-5415","files":{"txt":{"path":"standards/IETF/RFC-5415/RFC-5415.txt","sha256":"48e0ebb6efe752602694a25db0a50d9777eeda4a565119d1f17bba0b1f522ed0"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the Control And Provisioning of Wireless\n Access Points (CAPWAP) Protocol, meeting the objectives defined by\n the CAPWAP Working Group in RFC 4564. The CAPWAP protocol is\n designed to be flexible, allowing it to be used for a variety of\n wireless technologies. This document describes the base CAPWAP\n protocol, while separate binding extensions will enable its use with\n additional wireless technologies.","scope_keywords":["5415","authentication","authorization","http","license","subject","timestamp","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5415 This specification defines the Control And Provisioning of Wireless\n Access Points (CAPWAP) Protocol, meeting the objectives defined by\n the CAPWAP Working Group in RFC 4564. The CAPWAP protocol is\n designed to be flexible, allowing it to be used for a variety of\n wireless technologies. This document describes the base CAPWAP\n protocol, while separate binding extensions will enable its use with\n additional wireless technologies. 5415 authentication authorization http license subject timestamp tls trust nested-reference unchanged"},{"id":"IETF RFC 5422","type":"specification","body":"IETF","designation":"RFC 5422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5422.txt","https://www.rfc-editor.org/rfc/rfc5422.pdf"],"folder":"IETF/RFC-5422","files":{"txt":{"path":"standards/IETF/RFC-5422/RFC-5422.txt","sha256":"668942eb7bb7eb06594516a6b1d7bf2819bf3c00f1b1a2415ca34ced934c6627"}},"tags":["nested-reference","unchanged"],"summary":"The Flexible Authentication via Secure Tunneling Extensible\n Authentication Protocol (EAP-FAST) method enables secure\n communication between a peer and a server by using Transport Layer\n Security (TLS) to establish a mutually authenticated tunnel. EAP-\n FAST also enables the provisioning credentials or other information\n through this protected tunnel. This document describes the use of\n EAP-FAST for dynamic provisioning.","scope_keywords":["5422","attribute","attributes","authentication","authorization","certificate","credential","credentials","http","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5422 The Flexible Authentication via Secure Tunneling Extensible\n Authentication Protocol (EAP-FAST) method enables secure\n communication between a peer and a server by using Transport Layer\n Security (TLS) to establish a mutually authenticated tunnel. EAP-\n FAST also enables the provisioning credentials or other information\n through this protected tunnel. This document describes the use of\n EAP-FAST for dynamic provisioning. 5422 attribute attributes authentication authorization certificate credential credentials http key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5481","type":"specification","body":"IETF","designation":"RFC 5481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5481.txt","https://www.rfc-editor.org/rfc/rfc5481.pdf"],"folder":"IETF/RFC-5481","files":{"txt":{"path":"standards/IETF/RFC-5481/RFC-5481.txt","sha256":"69f5fd148c8ff13d1f84bdd8add5f2516badefb91e607d53c913414ac7a256f0"}},"tags":["nested-reference","unchanged"],"summary":"Packet delay variation metrics appear in many different standards\n documents. The metric definition in RFC 3393 has considerable\n flexibility, and it allows multiple formulations of delay variation\n through the specification of different packet selection functions.\n\n Although flexibility provides wide coverage and room for new ideas,\n it can make comparisons of independent implementations more\n difficult. Two different formulations of delay variation have come\n into wide use in the context of active measurements. This memo\n examines a range of circumstances for active measurements of delay\n variation and their uses, and recommends which of the two forms is\n best matched to particular conditions and tasks.","scope_keywords":["5481","http","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 5481 Packet delay variation metrics appear in many different standards\n documents. The metric definition in RFC 3393 has considerable\n flexibility, and it allows multiple formulations of delay variation\n through the specification of different packet selection functions.\n\n Although flexibility provides wide coverage and room for new ideas,\n it can make comparisons of independent implementations more\n difficult. Two different formulations of delay variation have come\n into wide use in the context of active measurements. This memo\n examines a range of circumstances for active measurements of delay\n variation and their uses, and recommends which of the two forms is\n best matched to particular conditions and tasks. 5481 http license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5548","type":"specification","body":"IETF","designation":"RFC 5548","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5548.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5548.txt","https://www.rfc-editor.org/rfc/rfc5548.pdf"],"folder":"IETF/RFC-5548","files":{"txt":{"path":"standards/IETF/RFC-5548/RFC-5548.txt","sha256":"91b5dc718295f9812a5f484e32399cc62bc977ef15fea5fb8eca61cc7ae44545"}},"tags":["nested-reference","unchanged"],"summary":"The application-specific routing requirements for Urban Low-Power and\n Lossy Networks (U-LLNs) are presented in this document. In the near\n future, sensing and actuating nodes will be placed outdoors in urban\n environments so as to improve people's living conditions as well as\n to monitor compliance with increasingly strict environmental laws.\n These field nodes are expected to measure and report a wide gamut of\n data (for example, the data required by applications that perform\n smart-metering or that monitor meteorological, pollution, and allergy\n conditions). The majority of these nodes are expected to communicate\n wirelessly over a variety of links such as IEEE 802.15.4, low-power\n IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited\n radio range and the large number of nodes requires the use of\n suitable routing protocols. The design of such protocols will be\n mainly im","scope_keywords":["5548","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null}],"search_text":"IETF RFC 5548 The application-specific routing requirements for Urban Low-Power and\n Lossy Networks (U-LLNs) are presented in this document. In the near\n future, sensing and actuating nodes will be placed outdoors in urban\n environments so as to improve people's living conditions as well as\n to monitor compliance with increasingly strict environmental laws.\n These field nodes are expected to measure and report a wide gamut of\n data (for example, the data required by applications that perform\n smart-metering or that monitor meteorological, pollution, and allergy\n conditions). The majority of these nodes are expected to communicate\n wirelessly over a variety of links such as IEEE 802.15.4, low-power\n IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited\n radio range and the large number of nodes requires the use of\n suitable routing protocols. The design of such protocols will be\n mainly im 5548 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5558","type":"specification","body":"IETF","designation":"RFC 5558","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5558.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5558.txt","https://www.rfc-editor.org/rfc/rfc5558.pdf"],"folder":"IETF/RFC-5558","files":{"txt":{"path":"standards/IETF/RFC-5558/RFC-5558.txt","sha256":"c5201661de21e7be17e7b5bc416b6654054e300473a28a3e712d752f46295a8e"}},"tags":["nested-reference","unchanged"],"summary":"Enterprise networks connect routers over various link types, and may\n also connect to provider networks and/or the global Internet.\n Enterprise network nodes require a means to automatically provision\n IP addresses/prefixes and support internetworking operation in a wide\n variety of use cases including Small Office, Home Office (SOHO)\n networks, Mobile Ad hoc Networks (MANETs), multi-organizational\n corporate networks and the interdomain core of the global Internet\n itself. This document specifies a Virtual Enterprise Traversal (VET)\n abstraction for autoconfiguration and operation of nodes in\n enterprise networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its di","scope_keywords":["5558","http","identification","license","management","seal","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null}],"search_text":"IETF RFC 5558 Enterprise networks connect routers over various link types, and may\n also connect to provider networks and/or the global Internet.\n Enterprise network nodes require a means to automatically provision\n IP addresses/prefixes and support internetworking operation in a wide\n variety of use cases including Small Office, Home Office (SOHO)\n networks, Mobile Ad hoc Networks (MANETs), multi-organizational\n corporate networks and the interdomain core of the global Internet\n itself. This document specifies a Virtual Enterprise Traversal (VET)\n abstraction for autoconfiguration and operation of nodes in\n enterprise networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its di 5558 http identification license management seal subject trust nested-reference unchanged"},{"id":"IETF RFC 5690","type":"specification","body":"IETF","designation":"RFC 5690","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5690.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5690.txt","https://www.rfc-editor.org/rfc/rfc5690.pdf"],"folder":"IETF/RFC-5690","files":{"txt":{"path":"standards/IETF/RFC-5690/RFC-5690.txt","sha256":"1cf0023e922f6038c254e2ca921b4e21b511667d70e48f3bfecd558c20cd3ee8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a possible congestion control mechanism for\n acknowledgement (ACKs) traffic in TCP. The document specifies an\n end-to-end acknowledgement congestion control mechanism for TCP that\n uses participation from both TCP hosts: the TCP data sender and the\n TCP data receiver. The TCP data sender detects lost or Explicit\n Congestion Notification (ECN)-marked ACK packets, and tells the TCP\n data receiver the ACK Ratio R to use to respond to the congestion on\n the reverse path from the data receiver to the data sender. The TCP\n data receiver sends roughly one ACK packet for every R data packets\n received. This mechanism is based on the acknowledgement congestion\n control in the Datagram Congestion Control Protocol's (DCCP's)\n Congestion Control Identifier (CCID) 2. This acknowledgement\n congestion control mechanism is being specified for further\n evaluation by the network co","scope_keywords":["5690","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null}],"search_text":"IETF RFC 5690 This document describes a possible congestion control mechanism for\n acknowledgement (ACKs) traffic in TCP. The document specifies an\n end-to-end acknowledgement congestion control mechanism for TCP that\n uses participation from both TCP hosts: the TCP data sender and the\n TCP data receiver. The TCP data sender detects lost or Explicit\n Congestion Notification (ECN)-marked ACK packets, and tells the TCP\n data receiver the ACK Ratio R to use to respond to the congestion on\n the reverse path from the data receiver to the data sender. The TCP\n data receiver sends roughly one ACK packet for every R data packets\n received. This mechanism is based on the acknowledgement congestion\n control in the Datagram Congestion Control Protocol's (DCCP's)\n Congestion Control Identifier (CCID) 2. This acknowledgement\n congestion control mechanism is being specified for further\n evaluation by the network co 5690 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5833","type":"specification","body":"IETF","designation":"RFC 5833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5833.txt","https://www.rfc-editor.org/rfc/rfc5833.pdf"],"folder":"IETF/RFC-5833","files":{"txt":{"path":"standards/IETF/RFC-5833/RFC-5833.txt","sha256":"7cbc31aa82d639de51c032a8d4abbd6b8d299703b287f5b8d61a86dcffcb52b7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. In particular, it\n describes the managed objects for modeling the Control And\n Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB\n module is presented as a basis for future work on the SNMP management\n of the CAPWAP protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of th","scope_keywords":["5833","http","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 5833 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. In particular, it\n describes the managed objects for modeling the Control And\n Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB\n module is presented as a basis for future work on the SNMP management\n of the CAPWAP protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of th 5833 http license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5834","type":"specification","body":"IETF","designation":"RFC 5834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5834.txt","https://www.rfc-editor.org/rfc/rfc5834.pdf"],"folder":"IETF/RFC-5834","files":{"txt":{"path":"standards/IETF/RFC-5834/RFC-5834.txt","sha256":"92666f8c5c7d0376a0c8cab7609c06540b856fe19d70de1465e437c7a09a39dd"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. In particular, it\n describes managed objects for modeling the Control And Provisioning\n of Wireless Access Points (CAPWAP) protocol for IEEE 802.11 wireless\n binding. This MIB module is presented as a basis for future work on\n the management of the CAPWAP protocol using the Simple Network\n Management Protocol (SNMP).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan","scope_keywords":["5834","http","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 5834 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. In particular, it\n describes managed objects for modeling the Control And Provisioning\n of Wireless Access Points (CAPWAP) protocol for IEEE 802.11 wireless\n binding. This MIB module is presented as a basis for future work on\n the management of the CAPWAP protocol using the Simple Network\n Management Protocol (SNMP).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan 5834 http license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6077","type":"specification","body":"IETF","designation":"RFC 6077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6077.txt","https://www.rfc-editor.org/rfc/rfc6077.pdf"],"folder":"IETF/RFC-6077","files":{"txt":{"path":"standards/IETF/RFC-6077/RFC-6077.txt","sha256":"2af74c692551ecfc90e2c4178d0c27d507301ec008c4f08480dbc29c59a714b9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes some of the open problems in Internet\n congestion control that are known today. This includes several new\n challenges that are becoming important as the network grows, as well\n as some issues that have been known for many years. These challenges\n are generally considered to be open research topics that may require\n more study or application of innovative techniques before Internet-\n scale solutions can be confidently engineered and deployed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Internet\n Congestion Control Research Gro","scope_keywords":["6077","algorithm","algorithms","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6077 This document describes some of the open problems in Internet\n congestion control that are known today. This includes several new\n challenges that are becoming important as the network grows, as well\n as some issues that have been known for many years. These challenges\n are generally considered to be open research topics that may require\n more study or application of innovative techniques before Internet-\n scale solutions can be confidently engineered and deployed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Internet\n Congestion Control Research Gro 6077 algorithm algorithms http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6225","type":"specification","body":"IETF","designation":"RFC 6225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6225.txt","https://www.rfc-editor.org/rfc/rfc6225.pdf"],"folder":"IETF/RFC-6225","files":{"txt":{"path":"standards/IETF/RFC-6225/RFC-6225.txt","sha256":"9011219694350a64c35a1c14282dcc1d0a00baa2ef6ce3311c19fa1b3a204217"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Dynamic Host Configuration Protocol options\n (both DHCPv4 and DHCPv6) for the coordinate-based geographic location\n of the client. The Location Configuration Information (LCI) includes\n Latitude, Longitude, and Altitude, with resolution or uncertainty\n indicators for each. Separate parameters indicate the reference\n datum for each of these values. This document obsoletes RFC 3825.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["6225","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null}],"search_text":"IETF RFC 6225 This document specifies Dynamic Host Configuration Protocol options\n (both DHCPv4 and DHCPv6) for the coordinate-based geographic location\n of the client. The Location Configuration Information (LCI) includes\n Latitude, Longitude, and Altitude, with resolution or uncertainty\n indicators for each. Separate parameters indicate the reference\n datum for each of these values. This document obsoletes RFC 3825.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 6225 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6443","type":"specification","body":"IETF","designation":"RFC 6443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6443.txt","https://www.rfc-editor.org/rfc/rfc6443.pdf"],"folder":"IETF/RFC-6443","files":{"txt":{"path":"standards/IETF/RFC-6443/RFC-6443.txt","sha256":"e0b1cef96dd08646ea91273ad672754cd8a3c5a3b0ba9b91a81a674a69e30fab"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has standardized various aspects of placing emergency calls.\n This document describes how all of those component parts are used to\n support emergency calls from citizens and visitors to authorities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6443.\n\nCopyright Notice\n\n Copyrig","scope_keywords":["6443","http","license","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 6443 The IETF has standardized various aspects of placing emergency calls.\n This document describes how all of those component parts are used to\n support emergency calls from citizens and visitors to authorities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6443.\n\nCopyright Notice\n\n Copyrig 6443 http license subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 6574","type":"specification","body":"IETF","designation":"RFC 6574","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6574.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6574.txt","https://www.rfc-editor.org/rfc/rfc6574.pdf"],"folder":"IETF/RFC-6574","files":{"txt":{"path":"standards/IETF/RFC-6574/RFC-6574.txt","sha256":"89862c135ba1e21ff13e7cdd032465c49445a6fa1b2bf03caabbbb4e6fd88585"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on 'Interconnecting Smart Objects with the\n Internet'. The workshop took place in Prague on 25 March 2011. The\n main goal of the workshop was to solicit feedback from the wider\n community on their experience with deploying IETF protocols in\n constrained environments. This report summarizes the discussions and\n lists the conclusions and recommendations to the Internet Engineering\n Task Force (IETF) community.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the In","scope_keywords":["6574","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null}],"search_text":"IETF RFC 6574 This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on 'Interconnecting Smart Objects with the\n Internet'. The workshop took place in Prague on 25 March 2011. The\n main goal of the workshop was to solicit feedback from the wider\n community on their experience with deploying IETF protocols in\n constrained environments. This report summarizes the discussions and\n lists the conclusions and recommendations to the Internet Engineering\n Task Force (IETF) community.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the In 6574 http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 6636","type":"specification","body":"IETF","designation":"RFC 6636","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6636.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6636.txt","https://www.rfc-editor.org/rfc/rfc6636.pdf"],"folder":"IETF/RFC-6636","files":{"txt":{"path":"standards/IETF/RFC-6636/RFC-6636.txt","sha256":"7bb3e22753fe027773a5eb3a8b7c8d01dedfab21aa880608470351350e9e44b6"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Group Management Protocol (IGMP) and Multicast Listener\n Discovery (MLD) are the protocols used by hosts and multicast routers\n to exchange their IP multicast group memberships with each other.\n This document describes ways to achieve IGMPv3 and MLDv2 protocol\n optimization for mobility and aims to become a guideline for the\n tuning of IGMPv3/MLDv2 Queries, timers, and counter values.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741","scope_keywords":["6636","http","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 6636 The Internet Group Management Protocol (IGMP) and Multicast Listener\n Discovery (MLD) are the protocols used by hosts and multicast routers\n to exchange their IP multicast group memberships with each other.\n This document describes ways to achieve IGMPv3 and MLDv2 protocol\n optimization for mobility and aims to become a guideline for the\n tuning of IGMPv3/MLDv2 Queries, timers, and counter values.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741 6636 http license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6757","type":"specification","body":"IETF","designation":"RFC 6757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6757.txt","https://www.rfc-editor.org/rfc/rfc6757.pdf"],"folder":"IETF/RFC-6757","files":{"txt":{"path":"standards/IETF/RFC-6757/RFC-6757.txt","sha256":"80a4fadcc4e02e5ac1512431270c3bcf9d9426fa143eaa432589603b28df6be5"}},"tags":["nested-reference","unchanged"],"summary":"The local mobility anchor in a Proxy Mobile IPv6 (PMIPv6) domain is\n able to provide access-network- and access-operator-specific handling\n or policing of the mobile node traffic using information about the\n access network to which the mobile node is attached. This\n specification defines a mechanism and a related mobility option for\n carrying the access network identifier and the access operator\n identification information from the mobile access gateway to the\n local mobility anchor over Proxy Mobile IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 o","scope_keywords":["6757","http","identification","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null}],"search_text":"IETF RFC 6757 The local mobility anchor in a Proxy Mobile IPv6 (PMIPv6) domain is\n able to provide access-network- and access-operator-specific handling\n or policing of the mobile node traffic using information about the\n access network to which the mobile node is attached. This\n specification defines a mechanism and a related mobility option for\n carrying the access network identifier and the access operator\n identification information from the mobile access gateway to the\n local mobility anchor over Proxy Mobile IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 o 6757 http identification license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6770","type":"specification","body":"IETF","designation":"RFC 6770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6770.txt","https://www.rfc-editor.org/rfc/rfc6770.pdf"],"folder":"IETF/RFC-6770","files":{"txt":{"path":"standards/IETF/RFC-6770/RFC-6770.txt","sha256":"9684ad0437f29d58d8a5ca5d8c896bbd5a18a64c185dd8cedc52082f38c71c79"}},"tags":["nested-reference","unchanged"],"summary":"Content Delivery Networks (CDNs) are commonly used for improving the\n End User experience of a content delivery service while keeping cost\n at a reasonable level. This document focuses on use cases that\n correspond to identified industry needs and that are expected to be\n realized once open interfaces and protocols supporting the\n interconnection of CDNs are specified and implemented. This document\n can be used to motivate the definition of the requirements to be\n supported by CDN Interconnection (CDNI) interfaces. It obsoletes RFC\n 3570.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri","scope_keywords":["6770","delivery","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null},{"body":"IETF","designation":"RFC 7337","folder":"IETF/RFC-7337","source":"IETF/RFC-7337/RFC-7337.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 6770 Content Delivery Networks (CDNs) are commonly used for improving the\n End User experience of a content delivery service while keeping cost\n at a reasonable level. This document focuses on use cases that\n correspond to identified industry needs and that are expected to be\n realized once open interfaces and protocols supporting the\n interconnection of CDNs are specified and implemented. This document\n can be used to motivate the definition of the requirements to be\n supported by CDN Interconnection (CDNI) interfaces. It obsoletes RFC\n 3570.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri 6770 delivery http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7217","type":"specification","body":"IETF","designation":"RFC 7217","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7217.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7217.txt","https://www.rfc-editor.org/rfc/rfc7217.pdf"],"folder":"IETF/RFC-7217","files":{"txt":{"path":"standards/IETF/RFC-7217/RFC-7217.txt","sha256":"00c9bbd863d51112268934a456eea2c5d41a8bc9de9d85ee44895ee3965439e0"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for generating IPv6 Interface\n Identifiers to be used with IPv6 Stateless Address Autoconfiguration\n (SLAAC), such that an IPv6 address configured using this method is\n stable within each subnet, but the corresponding Interface Identifier\n changes when the host moves from one network to another. This method\n is meant to be an alternative to generating Interface Identifiers\n based on hardware addresses (e.g., IEEE LAN Media Access Control\n (MAC) addresses), such that the benefits of stable addresses can be\n achieved without sacrificing the security and privacy of users. The\n method specified in this document applies to all prefixes a host may\n be employing, including link-local, global, and unique-local prefixes\n (and their corresponding addresses).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Int","scope_keywords":["7217","algorithm","http","key","license","management","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7217 This document specifies a method for generating IPv6 Interface\n Identifiers to be used with IPv6 Stateless Address Autoconfiguration\n (SLAAC), such that an IPv6 address configured using this method is\n stable within each subnet, but the corresponding Interface Identifier\n changes when the host moves from one network to another. This method\n is meant to be an alternative to generating Interface Identifiers\n based on hardware addresses (e.g., IEEE LAN Media Access Control\n (MAC) addresses), such that the benefits of stable addresses can be\n achieved without sacrificing the security and privacy of users. The\n method specified in this document applies to all prefixes a host may\n be employing, including link-local, global, and unique-local prefixes\n (and their corresponding addresses).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Int 7217 algorithm http key license management signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7278","type":"specification","body":"IETF","designation":"RFC 7278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7278.txt","https://www.rfc-editor.org/rfc/rfc7278.pdf"],"folder":"IETF/RFC-7278","files":{"txt":{"path":"standards/IETF/RFC-7278/RFC-7278.txt","sha256":"8faa2e22840693a6cf9b663bbaf1b02ce23b592255e429c8ae0f1f3c4d0dda6e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes requirements for extending an IPv6 /64 prefix\n from a User Equipment Third Generation Partnership Project (3GPP)\n radio interface to a LAN link and describes two implementation\n examples.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7278.\n\nByrne, et al. Informat","scope_keywords":["7278","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 7278 This document describes requirements for extending an IPv6 /64 prefix\n from a User Equipment Third Generation Partnership Project (3GPP)\n radio interface to a LAN link and describes two implementation\n examples.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7278.\n\nByrne, et al. Informat 7278 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7291","type":"specification","body":"IETF","designation":"RFC 7291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7291.txt","https://www.rfc-editor.org/rfc/rfc7291.pdf"],"folder":"IETF/RFC-7291","files":{"txt":{"path":"standards/IETF/RFC-7291/RFC-7291.txt","sha256":"591959a8c2091b71877cf07a848ca0e8d39de8759cdd2b95ec9ffad9973db378"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies DHCP (IPv4 and IPv6) options to configure\n hosts with Port Control Protocol (PCP) server IP addresses. The use\n of DHCPv4 or DHCPv6 depends on the PCP deployment scenarios. The set\n of deployment scenarios to which DHCPv4 or DHCPv6 can be applied is\n outside the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7291.\n\nCopyright Notice\n\n Copyr","scope_keywords":["7291","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null}],"search_text":"IETF RFC 7291 This document specifies DHCP (IPv4 and IPv6) options to configure\n hosts with Port Control Protocol (PCP) server IP addresses. The use\n of DHCPv4 or DHCPv6 depends on the PCP deployment scenarios. The set\n of deployment scenarios to which DHCPv4 or DHCPv6 can be applied is\n outside the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7291.\n\nCopyright Notice\n\n Copyr 7291 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7452","type":"specification","body":"IETF","designation":"RFC 7452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7452.txt","https://www.rfc-editor.org/rfc/rfc7452.pdf"],"folder":"IETF/RFC-7452","files":{"txt":{"path":"standards/IETF/RFC-7452/RFC-7452.txt","sha256":"3435c4594f94b2e9e29b6de04eab3676fa6913fc77a95a2882d3111acd4b7ddb"}},"tags":["nested-reference","unchanged"],"summary":"The term \"Internet of Things\" (IoT) denotes a trend where a large\n number of embedded devices employ communication services offered by\n Internet protocols. Many of these devices, often called \"smart\n objects\", are not directly operated by humans but exist as components\n in buildings or vehicles, or are spread out in the environment.\n Following the theme \"Everything that can be connected will be\n connected\", engineers and researchers designing smart object networks\n need to decide how to achieve this in practice.\n\n This document offers guidance to engineers designing Internet-\n connected smart objects.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent re","scope_keywords":["7452","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7452 The term \"Internet of Things\" (IoT) denotes a trend where a large\n number of embedded devices employ communication services offered by\n Internet protocols. Many of these devices, often called \"smart\n objects\", are not directly operated by humans but exist as components\n in buildings or vehicles, or are spread out in the environment.\n Following the theme \"Everything that can be connected will be\n connected\", engineers and researchers designing smart object networks\n need to decide how to achieve this in practice.\n\n This document offers guidance to engineers designing Internet-\n connected smart objects.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent re 7452 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7488","type":"specification","body":"IETF","designation":"RFC 7488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7488.txt","https://www.rfc-editor.org/rfc/rfc7488.pdf"],"folder":"IETF/RFC-7488","files":{"txt":{"path":"standards/IETF/RFC-7488/RFC-7488.txt","sha256":"e8eaabaf2453507c98858c99c9cf24ba3e247167697be060ab1c242c48832ee0"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the behavior to be followed by a Port Control\n Protocol (PCP) client to contact its PCP server(s) when one or\n several PCP server IP addresses are configured.\n\n This document updates RFC 6887.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7488.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reser","scope_keywords":["7488","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 7488 This document specifies the behavior to be followed by a Port Control\n Protocol (PCP) client to contact its PCP server(s) when one or\n several PCP server IP addresses are configured.\n\n This document updates RFC 6887.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7488.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reser 7488 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7542","type":"specification","body":"IETF","designation":"RFC 7542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7542.txt","https://www.rfc-editor.org/rfc/rfc7542.pdf"],"folder":"IETF/RFC-7542","files":{"txt":{"path":"standards/IETF/RFC-7542/RFC-7542.txt","sha256":"2044c90abd0b0db121bacdc6febbe9bfd0983d2361a25c8cca0d7bbb5ad4aceb"}},"tags":["nested-reference","unchanged"],"summary":"In order to provide inter-domain authentication services, it is\n necessary to have a standardized method that domains can use to\n identify each other's users. This document defines the syntax for\n the Network Access Identifier (NAI), the user identifier submitted by\n the client prior to accessing resources. This document is a revised\n version of RFC 4282. It addresses issues with international\n character sets and makes a number of other corrections to RFC 4282.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current st","scope_keywords":["7542","authentication","authorization","credential","credentials","http","license","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 7542 In order to provide inter-domain authentication services, it is\n necessary to have a standardized method that domains can use to\n identify each other's users. This document defines the syntax for\n the Network Access Identifier (NAI), the user identifier submitted by\n the client prior to accessing resources. This document is a revised\n version of RFC 4282. It addresses issues with international\n character sets and makes a number of other corrections to RFC 4282.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current st 7542 authentication authorization credential credentials http license subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 7696","type":"specification","body":"IETF","designation":"RFC 7696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7696.txt","https://www.rfc-editor.org/rfc/rfc7696.pdf"],"folder":"IETF/RFC-7696","files":{"txt":{"path":"standards/IETF/RFC-7696/RFC-7696.txt","sha256":"6cbcdc4f02992ff67e184a7eea01b4442ca283a8923959ce75bd9abe58c657cb"}},"tags":["nested-reference","unchanged"],"summary":"Many IETF protocols use cryptographic algorithms to provide\n confidentiality, integrity, authentication, or digital signature.\n Communicating peers must support a common set of cryptographic\n algorithms for these mechanisms to work properly. This memo provides\n guidelines to ensure that protocols have the ability to migrate from\n one mandatory-to-implement algorithm suite to another over time.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may ","scope_keywords":["7696","algorithm","algorithms","authentication","http","key","license","management","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null}],"search_text":"IETF RFC 7696 Many IETF protocols use cryptographic algorithms to provide\n confidentiality, integrity, authentication, or digital signature.\n Communicating peers must support a common set of cryptographic\n algorithms for these mechanisms to work properly. This memo provides\n guidelines to ensure that protocols have the ability to migrate from\n one mandatory-to-implement algorithm suite to another over time.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may  7696 algorithm algorithms authentication http key license management signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7839","type":"specification","body":"IETF","designation":"RFC 7839","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7839.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7839.txt","https://www.rfc-editor.org/rfc/rfc7839.pdf"],"folder":"IETF/RFC-7839","files":{"txt":{"path":"standards/IETF/RFC-7839/RFC-7839.txt","sha256":"82db9a9ad0ac6eb5e85f785e527b01526eb14b26d2d8971ec687321bba6631ee"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the format and mechanism that is to be used\n for encoding Access-Network Identifiers in DHCPv4 and DHCPv6 messages\n by defining new Access-Network-Identifier options and sub-options.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7839.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi","scope_keywords":["7839","http","identification","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null}],"search_text":"IETF RFC 7839 This document specifies the format and mechanism that is to be used\n for encoding Access-Network Identifiers in DHCPv4 and DHCPv6 messages\n by defining new Access-Network-Identifier options and sub-options.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7839.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi 7839 http identification license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7925","type":"specification","body":"IETF","designation":"RFC 7925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7925.txt","https://www.rfc-editor.org/rfc/rfc7925.pdf"],"folder":"IETF/RFC-7925","files":{"txt":{"path":"standards/IETF/RFC-7925/RFC-7925.txt","sha256":"eecea1d9d8c4206a95d9fc7a2001d17b87d73bb7cfc0a98b3ce6da33c505f5e3"}},"tags":["nested-reference","unchanged"],"summary":"A common design pattern in Internet of Things (IoT) deployments is\n the use of a constrained device that collects data via sensors or\n controls actuators for use in home automation, industrial control\n systems, smart cities, and other IoT deployments.\n\n This document defines a Transport Layer Security (TLS) and Datagram\n Transport Layer Security (DTLS) 1.2 profile that offers\n communications security for this data exchange thereby preventing\n eavesdropping, tampering, and message forgery. The lack of\n communication security is a common vulnerability in IoT products that\n can easily be solved by using these well-researched and widely\n deployed Internet security protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public","scope_keywords":["7925","algorithm","authentication","certificate","certificates","credential","hash","http","key","license","profile","profiles","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7925 A common design pattern in Internet of Things (IoT) deployments is\n the use of a constrained device that collects data via sensors or\n controls actuators for use in home automation, industrial control\n systems, smart cities, and other IoT deployments.\n\n This document defines a Transport Layer Security (TLS) and Datagram\n Transport Layer Security (DTLS) 1.2 profile that offers\n communications security for this data exchange thereby preventing\n eavesdropping, tampering, and message forgery. The lack of\n communication security is a common vulnerability in IoT products that\n can easily be solved by using these well-researched and widely\n deployed Internet security protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public 7925 algorithm authentication certificate certificates credential hash http key license profile profiles signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7928","type":"specification","body":"IETF","designation":"RFC 7928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7928.txt","https://www.rfc-editor.org/rfc/rfc7928.pdf"],"folder":"IETF/RFC-7928","files":{"txt":{"path":"standards/IETF/RFC-7928/RFC-7928.txt","sha256":"ae070a4a23b3290398e0c793388f08eb1fdc705f62c8861a384394f85ad4fe2f"}},"tags":["nested-reference","unchanged"],"summary":"Unmanaged large buffers in today's networks have given rise to a slew\n of performance issues. These performance issues can be addressed by\n some form of Active Queue Management (AQM) mechanism, optionally in\n combination with a packet-scheduling scheme such as fair queuing.\n This document describes various criteria for performing\n characterizations of AQM schemes that can be used in lab testing\n during development, prior to deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Intern","scope_keywords":["7928","http","license","management","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null}],"search_text":"IETF RFC 7928 Unmanaged large buffers in today's networks have given rise to a slew\n of performance issues. These performance issues can be addressed by\n some form of Active Queue Management (AQM) mechanism, optionally in\n combination with a packet-scheduling scheme such as fair queuing.\n This document describes various criteria for performing\n characterizations of AQM schemes that can be used in lab testing\n during development, prior to deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Intern 7928 http license management profile profiles subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.11-","type":"specification","body":"IEEE","designation":"IEEE 802.11-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-.html","download_urls":["https://standards.ieee.org/standard/802.11-.html"],"folder":"IEEE/IEEE-802.11-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null}],"search_text":"IEEE IEEE 802.11- nested-reference unavailable"},{"id":"IEEE IEEE 802.11-1997","type":"specification","body":"IEEE","designation":"IEEE 802.11-1997","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-1997.html","download_urls":["https://standards.ieee.org/standard/802.11-1997.html"],"folder":"IEEE/IEEE-802.11-1997","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null}],"search_text":"IEEE IEEE 802.11-1997 nested-reference unavailable"},{"id":"IEEE IEEE 802.11-1999","type":"specification","body":"IEEE","designation":"IEEE 802.11-1999","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-1999.html","download_urls":["https://standards.ieee.org/standard/802.11-1999.html"],"folder":"IEEE/IEEE-802.11-1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null}],"search_text":"IEEE IEEE 802.11-1999 nested-reference unavailable"},{"id":"IEEE IEEE 802.11-2003","type":"specification","body":"IEEE","designation":"IEEE 802.11-2003","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-2003.html","download_urls":["https://standards.ieee.org/standard/802.11-2003.html"],"folder":"IEEE/IEEE-802.11-2003","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null}],"search_text":"IEEE IEEE 802.11-2003 nested-reference unavailable"},{"id":"IEEE IEEE 802.11-2007","type":"specification","body":"IEEE","designation":"IEEE 802.11-2007","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-2007.html","download_urls":["https://standards.ieee.org/standard/802.11-2007.html"],"folder":"IEEE/IEEE-802.11-2007","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null}],"search_text":"IEEE IEEE 802.11-2007 nested-reference unavailable"},{"id":"IETF RFC 6762","type":"specification","body":"IETF","designation":"RFC 6762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6762.txt","https://www.rfc-editor.org/rfc/rfc6762.pdf"],"folder":"IETF/RFC-6762","files":{"txt":{"path":"standards/IETF/RFC-6762/RFC-6762.txt","sha256":"ede39b2b619d188d0920ebb18bfcb20f4301b05923a1435e9f8408f47da74196"}},"tags":["nested-reference","unchanged"],"summary":"As networked devices become smaller, more portable, and more\n ubiquitous, the ability to operate with less configured\n infrastructure is increasingly important. In particular, the ability\n to look up DNS resource record data types (including, but not limited\n to, host names) in the absence of a conventional managed DNS server\n is useful.\n\n Multicast DNS (mDNS) provides the ability to perform DNS-like\n operations on the local link in the absence of any conventional\n Unicast DNS server. In addition, Multicast DNS designates a portion\n of the DNS namespace to be free for local use, without the need to\n pay any annual fee, and without the need to set up delegations or\n otherwise configure a conventional DNS server to answer for those\n names.\n\n The primary benefits of Multicast DNS names are that (i) they require\n little or no administration or configuration to set them up, (ii)\n they work wh","scope_keywords":["6762","hash","http","key","license","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6762 As networked devices become smaller, more portable, and more\n ubiquitous, the ability to operate with less configured\n infrastructure is increasingly important. In particular, the ability\n to look up DNS resource record data types (including, but not limited\n to, host names) in the absence of a conventional managed DNS server\n is useful.\n\n Multicast DNS (mDNS) provides the ability to perform DNS-like\n operations on the local link in the absence of any conventional\n Unicast DNS server. In addition, Multicast DNS designates a portion\n of the DNS namespace to be free for local use, without the need to\n pay any annual fee, and without the need to set up delegations or\n otherwise configure a conventional DNS server to answer for those\n names.\n\n The primary benefits of Multicast DNS names are that (i) they require\n little or no administration or configuration to set them up, (ii)\n they work wh 6762 hash http key license qualified subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.11-2012","type":"specification","body":"IEEE","designation":"IEEE 802.11-2012","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-2012.html","download_urls":["https://standards.ieee.org/standard/802.11-2012.html"],"folder":"IEEE/IEEE-802.11-2012","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 802.11-2012 nested-reference unavailable"},{"id":"IEEE IEEE 802.11-99","type":"specification","body":"IEEE","designation":"IEEE 802.11-99","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11-99.html","download_urls":["https://standards.ieee.org/standard/802.11-99.html"],"folder":"IEEE/IEEE-802.11-99","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null}],"search_text":"IEEE IEEE 802.11-99 nested-reference unavailable"},{"id":"IEEE IEEE 802.11.","type":"specification","body":"IEEE","designation":"IEEE 802.11.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.11..html","download_urls":["https://standards.ieee.org/standard/802.11..html"],"folder":"IEEE/IEEE-802.11.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null}],"search_text":"IEEE IEEE 802.11. nested-reference unavailable"},{"id":"IEEE IEEE 802.12","type":"specification","body":"IEEE","designation":"IEEE 802.12","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.12.html","download_urls":["https://standards.ieee.org/standard/802.12.html"],"folder":"IEEE/IEEE-802.12","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IEEE IEEE 802.12 nested-reference unavailable"},{"id":"IETF RFC 2020","type":"specification","body":"IETF","designation":"RFC 2020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2020.txt","https://www.rfc-editor.org/rfc/rfc2020.pdf"],"folder":"IETF/RFC-2020","files":{"txt":{"path":"standards/IETF/RFC-2020/RFC-2020.txt","sha256":"bf3ccbfd9353fc15061ce178c5035864dfd9aa348ccf8b2622f3bf651568b72d"}},"tags":["nested-reference","unchanged"],"summary":"Syntax Notation One (ASN.1) [1] termed the Structure of Management\n Information (SMI) [2]. In particular, each object type is named by\n an OBJECT IDENTIFIER, an administratively assigned name. The object\n type together with an object instance serves to uniquely identify a\n specific instantiation of the object. For human convenience, we\n often use a textual string, termed the descriptor, to refer to the\n object type.\n\n3. Overview\n\n Instances of these object types represent attributes of an interface\n to an IEEE 802.12 communications medium. At present, IEEE 802.12\n media are identified by one value of the ifType object in the\n Internet-standard MIB:\n\n ieee80212(55)\n\n For this interface, the value of the ifSpecific variable in the MIB-\n II [5] has the OBJECT IDENTIFIER value:\n\n dot12MIB OBJECT IDENTIFIER ::= { transmission 45 }\n\n The values for the ifType object are defined by the IANAifTy","scope_keywords":["2020","attribute","attributes","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null}],"search_text":"IETF RFC 2020 Syntax Notation One (ASN.1) [1] termed the Structure of Management\n Information (SMI) [2]. In particular, each object type is named by\n an OBJECT IDENTIFIER, an administratively assigned name. The object\n type together with an object instance serves to uniquely identify a\n specific instantiation of the object. For human convenience, we\n often use a textual string, termed the descriptor, to refer to the\n object type.\n\n3. Overview\n\n Instances of these object types represent attributes of an interface\n to an IEEE 802.12 communications medium. At present, IEEE 802.12\n media are identified by one value of the ifType object in the\n Internet-standard MIB:\n\n ieee80212(55)\n\n For this interface, the value of the ifSpecific variable in the MIB-\n II [5] has the OBJECT IDENTIFIER value:\n\n dot12MIB OBJECT IDENTIFIER ::= { transmission 45 }\n\n The values for the ifType object are defined by the IANAifTy 2020 attribute attributes http management presentation nested-reference unchanged"},{"id":"IETF RFC 3796","type":"specification","body":"IETF","designation":"RFC 3796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3796.txt","https://www.rfc-editor.org/rfc/rfc3796.pdf"],"folder":"IETF/RFC-3796","files":{"txt":{"path":"standards/IETF/RFC-3796/RFC-3796.txt","sha256":"c9f721019fd2c7e58be69772b99a1125768463ad061f6e8149c90116ec35c084"}},"tags":["nested-reference","unchanged"],"summary":"This document seeks to record all usage of IPv4 addresses in\n currently deployed IETF Operations & Management Area accepted\n standards. In order to successfully transition from an all IPv4\n Internet to an all IPv6 Internet, many interim steps will be taken.\n One of these steps is the evolution of current protocols that have\n IPv4 dependencies. It is hoped that these protocols (and their\n implementations) will be redesigned to be network address\n independent, but failing that will at least dually support IPv4 and\n IPv6. To this end, all Standards (Full, Draft, and Proposed), as\n well as Experimental RFCs, will be surveyed and any dependencies will\n be documented.\n\nNesser II & Bergstrom Informational [Page 1]\n\f\nRFC 3796 IPv4 in the IETF Operations & Management Area June 2004","scope_keywords":["3796","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 3796 This document seeks to record all usage of IPv4 addresses in\n currently deployed IETF Operations & Management Area accepted\n standards. In order to successfully transition from an all IPv4\n Internet to an all IPv6 Internet, many interim steps will be taken.\n One of these steps is the evolution of current protocols that have\n IPv4 dependencies. It is hoped that these protocols (and their\n implementations) will be redesigned to be network address\n independent, but failing that will at least dually support IPv4 and\n IPv6. To this end, all Standards (Full, Draft, and Proposed), as\n well as Experimental RFCs, will be surveyed and any dependencies will\n be documented.\n\nNesser II & Bergstrom Informational [Page 1]\n\f\nRFC 3796 IPv4 in the IETF Operations & Management Area June 2004 3796 management nested-reference unchanged"},{"id":"IEEE IEEE 802.12-1995.","type":"specification","body":"IEEE","designation":"IEEE 802.12-1995.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.12-1995..html","download_urls":["https://standards.ieee.org/standard/802.12-1995..html"],"folder":"IEEE/IEEE-802.12-1995.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null}],"search_text":"IEEE IEEE 802.12-1995. nested-reference unavailable"},{"id":"IEEE IEEE 802.12.","type":"specification","body":"IEEE","designation":"IEEE 802.12.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.12..html","download_urls":["https://standards.ieee.org/standard/802.12..html"],"folder":"IEEE/IEEE-802.12.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null}],"search_text":"IEEE IEEE 802.12. nested-reference unavailable"},{"id":"IEEE IEEE 802.15","type":"specification","body":"IEEE","designation":"IEEE 802.15","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.html","download_urls":["https://standards.ieee.org/standard/802.15.html"],"folder":"IEEE/IEEE-802.15","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null}],"search_text":"IEEE IEEE 802.15 nested-reference unavailable"},{"id":"IETF RFC 4830","type":"specification","body":"IETF","designation":"RFC 4830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4830.txt","https://www.rfc-editor.org/rfc/rfc4830.pdf"],"folder":"IETF/RFC-4830","files":{"txt":{"path":"standards/IETF/RFC-4830/RFC-4830.txt","sha256":"70c286e98b7c13074789db64f8142487fac8efd3e1658603cb51afe0b4d10e4c"}},"tags":["nested-reference","unchanged"],"summary":"Localized mobility management is a well-understood concept in the\n IETF, with a number of solutions already available. This document\n looks at the principal shortcomings of the existing solutions, all of\n which involve the host in mobility management, and makes a case for\n network-based local mobility management.","scope_keywords":["4830","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4832","folder":"IETF/RFC-4832","source":"IETF/RFC-4832/RFC-4832.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null}],"search_text":"IETF RFC 4830 Localized mobility management is a well-understood concept in the\n IETF, with a number of solutions already available. This document\n looks at the principal shortcomings of the existing solutions, all of\n which involve the host in mobility management, and makes a case for\n network-based local mobility management. 4830 management trust nested-reference unchanged"},{"id":"IEEE IEEE 802.15.1","type":"specification","body":"IEEE","designation":"IEEE 802.15.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.1.html","download_urls":["https://standards.ieee.org/standard/802.15.1.html"],"folder":"IEEE/IEEE-802.15.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null}],"search_text":"IEEE IEEE 802.15.1 nested-reference unavailable"},{"id":"IETF RFC 4067","type":"specification","body":"IETF","designation":"RFC 4067","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4067.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4067.txt","https://www.rfc-editor.org/rfc/rfc4067.pdf"],"folder":"IETF/RFC-4067","files":{"txt":{"path":"standards/IETF/RFC-4067/RFC-4067.txt","sha256":"c45b3484bfdad6697069960b77b177e6a79f303d9206e1b9f2ee82258fa6ac47"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the Context Transfer Protocol (CXTP) that\n enables authorized context transfers. Context transfers allow better\n support for node based mobility so that the applications running on\n mobile nodes can operate with minimal disruption. Key objectives are\n to reduce latency and packet losses, and to avoid the re-initiation\n of signaling to and from the mobile node.","scope_keywords":["4067","authorization","key","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 4067 This document presents the Context Transfer Protocol (CXTP) that\n enables authorized context transfers. Context transfers allow better\n support for node based mobility so that the applications running on\n mobile nodes can operate with minimal disruption. Key objectives are\n to reduce latency and packet losses, and to avoid the re-initiation\n of signaling to and from the mobile node. 4067 authorization key presentation profile nested-reference unchanged"},{"id":"IEEE IEEE 802.15.3","type":"specification","body":"IEEE","designation":"IEEE 802.15.3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.3.html","download_urls":["https://standards.ieee.org/standard/802.15.3.html"],"folder":"IEEE/IEEE-802.15.3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null}],"search_text":"IEEE IEEE 802.15.3 nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4","type":"specification","body":"IEEE","designation":"IEEE 802.15.4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4.html","download_urls":["https://standards.ieee.org/standard/802.15.4.html"],"folder":"IEEE/IEEE-802.15.4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null},{"body":"IETF","designation":"RFC 5673","folder":"IETF/RFC-5673","source":"IETF/RFC-5673/RFC-5673.txt","version":null},{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7346","folder":"IETF/RFC-7346","source":"IETF/RFC-7346/RFC-7346.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IEEE IEEE 802.15.4 nested-reference unavailable"},{"id":"IETF RFC 5673","type":"specification","body":"IETF","designation":"RFC 5673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5673.txt","https://www.rfc-editor.org/rfc/rfc5673.pdf"],"folder":"IETF/RFC-5673","files":{"txt":{"path":"standards/IETF/RFC-5673/RFC-5673.txt","sha256":"446677d5158e764a634176f9f640044dd7f2b792d350e7de5e56d4206b28959d"}},"tags":["nested-reference","unchanged"],"summary":"The wide deployment of lower-cost wireless devices will significantly\n improve the productivity and safety of industrial plants while\n increasing the efficiency of plant workers by extending the\n information set available about the plant operations. The aim of\n this document is to analyze the functional requirements for a routing\n protocol used in industrial Low-power and Lossy Networks (LLNs) of\n field devices.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication o","scope_keywords":["5673","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null}],"search_text":"IETF RFC 5673 The wide deployment of lower-cost wireless devices will significantly\n improve the productivity and safety of industrial plants while\n increasing the efficiency of plant workers by extending the\n information set available about the plant operations. The aim of\n this document is to analyze the functional requirements for a routing\n protocol used in industrial Low-power and Lossy Networks (LLNs) of\n field devices.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication o 5673 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5826","type":"specification","body":"IETF","designation":"RFC 5826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5826.txt","https://www.rfc-editor.org/rfc/rfc5826.pdf"],"folder":"IETF/RFC-5826","files":{"txt":{"path":"standards/IETF/RFC-5826/RFC-5826.txt","sha256":"4304c3a1fedceac3f22ac6e14e4d76c296f8d517524ba2a704a935e6701adda8"}},"tags":["nested-reference","unchanged"],"summary":"This document presents requirements specific to home control and\n automation applications for Routing Over Low power and Lossy (ROLL)\n networks. In the near future, many homes will contain high numbers\n of wireless devices for a wide set of purposes. Examples include\n actuators (relay, light dimmer, heating valve), sensors (wall switch,\n water leak, blood pressure), and advanced controllers (radio-\n frequency-based AV remote control, central server for light and heat\n control). Because such devices only cover a limited radio range,\n routing is often required. The aim of this document is to specify\n the routing requirements for networks comprising such constrained\n devices in a home-control and automation environment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Inter","scope_keywords":["5826","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null}],"search_text":"IETF RFC 5826 This document presents requirements specific to home control and\n automation applications for Routing Over Low power and Lossy (ROLL)\n networks. In the near future, many homes will contain high numbers\n of wireless devices for a wide set of purposes. Examples include\n actuators (relay, light dimmer, heating valve), sensors (wall switch,\n water leak, blood pressure), and advanced controllers (radio-\n frequency-based AV remote control, central server for light and heat\n control). Because such devices only cover a limited radio range,\n routing is often required. The aim of this document is to specify\n the routing requirements for networks comprising such constrained\n devices in a home-control and automation environment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Inter 5826 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6282","type":"specification","body":"IETF","designation":"RFC 6282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6282.txt","https://www.rfc-editor.org/rfc/rfc6282.pdf"],"folder":"IETF/RFC-6282","files":{"txt":{"path":"standards/IETF/RFC-6282/RFC-6282.txt","sha256":"a3b46845b7223dff27bb78c1c094caa1a6ffdc1f87ec17b8ff905c4aedc4a7f2"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 4944, \"Transmission of IPv6 Packets over\n IEEE 802.15.4 Networks\". This document specifies an IPv6 header\n compression format for IPv6 packet delivery in Low Power Wireless\n Personal Area Networks (6LoWPANs). The compression format relies on\n shared context to allow compression of arbitrary prefixes. How the\n information is maintained in that shared context is out of scope.\n This document specifies compression of multicast addresses and a\n framework for compressing next headers. UDP header compression is\n specified within this framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further info","scope_keywords":["6282","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 6282 This document updates RFC 4944, \"Transmission of IPv6 Packets over\n IEEE 802.15.4 Networks\". This document specifies an IPv6 header\n compression format for IPv6 packet delivery in Low Power Wireless\n Personal Area Networks (6LoWPANs). The compression format relies on\n shared context to allow compression of arbitrary prefixes. How the\n information is maintained in that shared context is out of scope.\n This document specifies compression of multicast addresses and a\n framework for compressing next headers. UDP header compression is\n specified within this framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further info 6282 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6568","type":"specification","body":"IETF","designation":"RFC 6568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6568.txt","https://www.rfc-editor.org/rfc/rfc6568.pdf"],"folder":"IETF/RFC-6568","files":{"txt":{"path":"standards/IETF/RFC-6568/RFC-6568.txt","sha256":"df295c43e53b246377dd29cedd9a0c7802b20869360f732bcc53af9f2bd120ef"}},"tags":["nested-reference","unchanged"],"summary":"This document investigates potential application scenarios and use\n cases for low-power wireless personal area networks (LoWPANs). This\n document provides dimensions of design space for LoWPAN applications.\n A list of use cases and market domains that may benefit and motivate\n the work currently done in the 6LoWPAN Working Group is provided with\n the characteristics of each dimension. A complete list of practical\n use cases is not the goal of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate f","scope_keywords":["6568","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 6568 This document investigates potential application scenarios and use\n cases for low-power wireless personal area networks (LoWPANs). This\n document provides dimensions of design space for LoWPAN applications.\n A list of use cases and market domains that may benefit and motivate\n the work currently done in the 6LoWPAN Working Group is provided with\n the characteristics of each dimension. A complete list of practical\n use cases is not the goal of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate f 6568 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6606","type":"specification","body":"IETF","designation":"RFC 6606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6606.txt","https://www.rfc-editor.org/rfc/rfc6606.pdf"],"folder":"IETF/RFC-6606","files":{"txt":{"path":"standards/IETF/RFC-6606/RFC-6606.txt","sha256":"00c71facb2bbaeccec987984dc77301d47a2f23c63c528dc150b51598be2e732"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) are\n formed by devices that are compatible with the IEEE 802.15.4\n standard. However, neither the IEEE 802.15.4 standard nor the\n 6LoWPAN format specification defines how mesh topologies could be\n obtained and maintained. Thus, it should be considered how 6LoWPAN\n formation and multi-hop routing could be supported.\n\n This document provides the problem statement and design space for\n 6LoWPAN routing. It defines the routing requirements for 6LoWPANs,\n considering the low-power and other particular characteristics of the\n devices and links. The purpose of this document is not to recommend\n specific solutions but to provide general, layer-agnostic guidelines\n about the design of 6LoWPAN routing that can lead to further analysis\n and protocol design. This document is intended as input to groups\n working on routing protocols releva","scope_keywords":["6606","attribute","attributes","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null}],"search_text":"IETF RFC 6606 IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) are\n formed by devices that are compatible with the IEEE 802.15.4\n standard. However, neither the IEEE 802.15.4 standard nor the\n 6LoWPAN format specification defines how mesh topologies could be\n obtained and maintained. Thus, it should be considered how 6LoWPAN\n formation and multi-hop routing could be supported.\n\n This document provides the problem statement and design space for\n 6LoWPAN routing. It defines the routing requirements for 6LoWPANs,\n considering the low-power and other particular characteristics of the\n devices and links. The purpose of this document is not to recommend\n specific solutions but to provide general, layer-agnostic guidelines\n about the design of 6LoWPAN routing that can lead to further analysis\n and protocol design. This document is intended as input to groups\n working on routing protocols releva 6606 attribute attributes http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6775","type":"specification","body":"IETF","designation":"RFC 6775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6775.txt","https://www.rfc-editor.org/rfc/rfc6775.pdf"],"folder":"IETF/RFC-6775","files":{"txt":{"path":"standards/IETF/RFC-6775/RFC-6775.txt","sha256":"6dd3ce61b64f8bf3ef11d4ad8053186b3cf161b72b9aab2250a6b7b752f7a727"}},"tags":["nested-reference","unchanged"],"summary":"The IETF work in IPv6 over Low-power Wireless Personal Area Network\n (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4. This and other\n similar link technologies have limited or no usage of multicast\n signaling due to energy conservation. In addition, the wireless\n network may not strictly follow the traditional concept of IP subnets\n and IP links. IPv6 Neighbor Discovery was not designed for non-\n transitive wireless links, as its reliance on the traditional IPv6\n link concept and its heavy use of multicast make it inefficient and\n sometimes impractical in a low-power and lossy network. This\n document describes simple optimizations to IPv6 Neighbor Discovery,\n its addressing mechanisms, and duplicate address detection for Low-\n power Wireless Personal Area Networks and similar networks. The\n document thus updates RFC 4944 to specify the use of the\n optimizations defined here.\n\nStatus of ","scope_keywords":["6775","http","license","management","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 6775 The IETF work in IPv6 over Low-power Wireless Personal Area Network\n (6LoWPAN) defines 6LoWPANs such as IEEE 802.15.4. This and other\n similar link technologies have limited or no usage of multicast\n signaling due to energy conservation. In addition, the wireless\n network may not strictly follow the traditional concept of IP subnets\n and IP links. IPv6 Neighbor Discovery was not designed for non-\n transitive wireless links, as its reliance on the traditional IPv6\n link concept and its heavy use of multicast make it inefficient and\n sometimes impractical in a low-power and lossy network. This\n document describes simple optimizations to IPv6 Neighbor Discovery,\n its addressing mechanisms, and duplicate address detection for Low-\n power Wireless Personal Area Networks and similar networks. The\n document thus updates RFC 4944 to specify the use of the\n optimizations defined here.\n\nStatus of  6775 http license management subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6997","type":"specification","body":"IETF","designation":"RFC 6997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6997.txt","https://www.rfc-editor.org/rfc/rfc6997.pdf"],"folder":"IETF/RFC-6997","files":{"txt":{"path":"standards/IETF/RFC-6997/RFC-6997.txt","sha256":"a8f4d134c26dc858d0eaa891ac21e18c4359efe932b725748638414f69b5d12b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a point-to-point route discovery mechanism,\n complementary to the Routing Protocol for Low-power and Lossy\n Networks (RPL) core functionality. This mechanism allows an IPv6\n router to discover \"on demand\" routes to one or more IPv6 routers in\n a Low-power and Lossy Network (LLN) such that the discovered routes\n meet specified metrics constraints.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the ","scope_keywords":["6997","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null}],"search_text":"IETF RFC 6997 This document specifies a point-to-point route discovery mechanism,\n complementary to the Routing Protocol for Low-power and Lossy\n Networks (RPL) core functionality. This mechanism allows an IPv6\n router to discover \"on demand\" routes to one or more IPv6 routers in\n a Low-power and Lossy Network (LLN) such that the discovered routes\n meet specified metrics constraints.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the  6997 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7102","type":"specification","body":"IETF","designation":"RFC 7102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7102.txt","https://www.rfc-editor.org/rfc/rfc7102.pdf"],"folder":"IETF/RFC-7102","files":{"txt":{"path":"standards/IETF/RFC-7102/RFC-7102.txt","sha256":"9bf8e5effbbf65f93b447f58f72a6d407e0dcb61e0f24ce187ed3410d621d462"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a glossary of terminology used in routing\n requirements and solutions for networks referred to as Low-Power and\n Lossy Networks (LLNs). An LLN is typically composed of many embedded\n devices with limited power, memory, and processing resources\n interconnected by a variety of links. There is a wide scope of\n application areas for LLNs, including industrial monitoring, building\n automation (e.g., heating, ventilation, air conditioning, lighting,\n access control, fire), connected home, health care, environmental\n monitoring, urban sensor networks, energy management, assets\n tracking, and refrigeration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re","scope_keywords":["7102","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 7102 This document provides a glossary of terminology used in routing\n requirements and solutions for networks referred to as Low-Power and\n Lossy Networks (LLNs). An LLN is typically composed of many embedded\n devices with limited power, memory, and processing resources\n interconnected by a variety of links. There is a wide scope of\n application areas for LLNs, including industrial monitoring, building\n automation (e.g., heating, ventilation, air conditioning, lighting,\n access control, fire), connected home, health care, environmental\n monitoring, urban sensor networks, energy management, assets\n tracking, and refrigeration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re 7102 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7346","type":"specification","body":"IETF","designation":"RFC 7346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7346.txt","https://www.rfc-editor.org/rfc/rfc7346.pdf"],"folder":"IETF/RFC-7346","files":{"txt":{"path":"standards/IETF/RFC-7346/RFC-7346.txt","sha256":"59d84b87e1c8619ca356e9635d927de9ac8b623d45b67f68d7cacbed283dd707"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the definitions of IPv6 multicast scopes and\n therefore updates RFCs 4007 and 4291.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7346.\n\nDroms Standards Track [Page 1]\n\f\nRFC 7346 IPv6 Multicast Address Scopes August 2014\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is su","scope_keywords":["7346","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 7346 This document updates the definitions of IPv6 multicast scopes and\n therefore updates RFCs 4007 and 4291.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7346.\n\nDroms Standards Track [Page 1]\n\f\nRFC 7346 IPv6 Multicast Address Scopes August 2014\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is su 7346 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7388","type":"specification","body":"IETF","designation":"RFC 7388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7388.txt","https://www.rfc-editor.org/rfc/rfc7388.pdf"],"folder":"IETF/RFC-7388","files":{"txt":{"path":"standards/IETF/RFC-7388/RFC-7388.txt","sha256":"41246166a775b490569624e4681dbe2c679f514b9c5e667f79500103b6bf0332"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it defines objects for managing IPv6 over\n Low-Power Wireless Personal Area Networks (6LoWPANs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7388.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as ","scope_keywords":["7388","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null}],"search_text":"IETF RFC 7388 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it defines objects for managing IPv6 over\n Low-Power Wireless Personal Area Networks (6LoWPANs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7388.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as  7388 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7397","type":"specification","body":"IETF","designation":"RFC 7397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7397.txt","https://www.rfc-editor.org/rfc/rfc7397.pdf"],"folder":"IETF/RFC-7397","files":{"txt":{"path":"standards/IETF/RFC-7397/RFC-7397.txt","sha256":"973f4244f264872ca2f18679e4f28ebb6c6a8947154e18dbb73405ba70412fc2"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a summary of a workshop on 'Smart Object\n Security' that took place in Paris on March 23, 2012. The main goal\n of the workshop was to allow participants to share their thoughts\n about the ability to utilize existing and widely deployed security\n mechanisms for smart objects.\n\n This report summarizes the discussions and lists the conclusions and\n recommendations to the Internet Engineering Task Force (IETF)\n community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Inte","scope_keywords":["7397","authorization","credential","credentials","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null}],"search_text":"IETF RFC 7397 This document provides a summary of a workshop on 'Smart Object\n Security' that took place in Paris on March 23, 2012. The main goal\n of the workshop was to allow participants to share their thoughts\n about the ability to utilize existing and widely deployed security\n mechanisms for smart objects.\n\n This report summarizes the discussions and lists the conclusions and\n recommendations to the Internet Engineering Task Force (IETF)\n community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Inte 7397 authorization credential credentials http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7400","type":"specification","body":"IETF","designation":"RFC 7400","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7400.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7400.txt","https://www.rfc-editor.org/rfc/rfc7400.pdf"],"folder":"IETF/RFC-7400","files":{"txt":{"path":"standards/IETF/RFC-7400/RFC-7400.txt","sha256":"d7e583fb7f5aa839e4c8fc32343b09fec43df95e4659868c52232bc3b63b9be9"}},"tags":["nested-reference","unchanged"],"summary":"RFC 6282 defines header compression in 6LoWPAN packets (where\n \"6LoWPAN\" refers to \"IPv6 over Low-Power Wireless Personal Area\n Network\"). The present document specifies a simple addition that\n enables the compression of generic headers and header-like payloads,\n without a need to define a new header compression scheme for each\n such new header or header-like payload.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:","scope_keywords":["7400","http","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null}],"search_text":"IETF RFC 7400 RFC 6282 defines header compression in 6LoWPAN packets (where\n \"6LoWPAN\" refers to \"IPv6 over Low-Power Wireless Personal Area\n Network\"). The present document specifies a simple addition that\n enables the compression of generic headers and header-like payloads,\n without a need to define a new header compression scheme for each\n such new header or header-like payload.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http: 7400 http key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7428","type":"specification","body":"IETF","designation":"RFC 7428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7428.txt","https://www.rfc-editor.org/rfc/rfc7428.pdf"],"folder":"IETF/RFC-7428","files":{"txt":{"path":"standards/IETF/RFC-7428/RFC-7428.txt","sha256":"21ae7bba6c81f7b40fefa22641be1182f04bafbf781681fa24f54eb35a2a5109"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the frame format for transmission of IPv6\n packets as well as a method of forming IPv6 link-local addresses and\n statelessly autoconfigured IPv6 addresses on ITU-T G.9959 networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7428.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["7428","encryption","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 7428 This document describes the frame format for transmission of IPv6\n packets as well as a method of forming IPv6 link-local addresses and\n statelessly autoconfigured IPv6 addresses on ITU-T G.9959 networks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7428.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  7428 encryption http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7547","type":"specification","body":"IETF","designation":"RFC 7547","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7547.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7547.txt","https://www.rfc-editor.org/rfc/rfc7547.pdf"],"folder":"IETF/RFC-7547","files":{"txt":{"path":"standards/IETF/RFC-7547/RFC-7547.txt","sha256":"4d14422de705894a49c26c7895bd6b99374ff3670cf953130ec8089c41430751"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a problem statement, deployment and management\n topology options, as well as requirements addressing the different\n use cases of the management of networks where constrained devices are\n involved.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7547.\n\nErsue, et al. ","scope_keywords":["7547","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 7547 This document provides a problem statement, deployment and management\n topology options, as well as requirements addressing the different\n use cases of the management of networks where constrained devices are\n involved.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7547.\n\nErsue, et al.  7547 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7548","type":"specification","body":"IETF","designation":"RFC 7548","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7548.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7548.txt","https://www.rfc-editor.org/rfc/rfc7548.pdf"],"folder":"IETF/RFC-7548","files":{"txt":{"path":"standards/IETF/RFC-7548/RFC-7548.txt","sha256":"348c0f9b292c14b586f718ac15f82f5599fb4ef1b67f9212e375dcd2ae1c8273"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses use cases concerning the management of\n networks in which constrained devices are involved. A problem\n statement, deployment options, and the requirements on the networks\n with constrained devices can be found in the companion document on\n \"Management of Networks with Constrained Devices: Problem Statement\n and Requirements\" (RFC 7547).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current stat","scope_keywords":["7548","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null}],"search_text":"IETF RFC 7548 This document discusses use cases concerning the management of\n networks in which constrained devices are involved. A problem\n statement, deployment options, and the requirements on the networks\n with constrained devices can be found in the companion document on\n \"Management of Networks with Constrained Devices: Problem Statement\n and Requirements\" (RFC 7547).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current stat 7548 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7924","type":"specification","body":"IETF","designation":"RFC 7924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7924.txt","https://www.rfc-editor.org/rfc/rfc7924.pdf"],"folder":"IETF/RFC-7924","files":{"txt":{"path":"standards/IETF/RFC-7924/RFC-7924.txt","sha256":"5b820985d3f7295264ac9ad7bdab098f9370c588c05f6597c3fd8321807be155"}},"tags":["nested-reference","unchanged"],"summary":"Transport Layer Security (TLS) handshakes often include fairly static\n information, such as the server certificate and a list of trusted\n certification authorities (CAs). This information can be of\n considerable size, particularly if the server certificate is bundled\n with a complete certificate chain (i.e., the certificates of\n intermediate CAs up to the root CA).\n\n This document defines an extension that allows a TLS client to inform\n a server of cached information, thereby enabling the server to omit\n already available information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard","scope_keywords":["7924","certificate","certificates","hash","http","key","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7924 Transport Layer Security (TLS) handshakes often include fairly static\n information, such as the server certificate and a list of trusted\n certification authorities (CAs). This information can be of\n considerable size, particularly if the server certificate is bundled\n with a complete certificate chain (i.e., the certificates of\n intermediate CAs up to the root CA).\n\n This document defines an extension that allows a TLS client to inform\n a server of cached information, thereby enabling the server to omit\n already available information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard 7924 certificate certificates hash http key license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7959","type":"specification","body":"IETF","designation":"RFC 7959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7959.txt","https://www.rfc-editor.org/rfc/rfc7959.pdf"],"folder":"IETF/RFC-7959","files":{"txt":{"path":"standards/IETF/RFC-7959/RFC-7959.txt","sha256":"0b1e50d6a5d5a3684dcf990e1b25c54d6ea953a544a5c54bfb7103dec0c37da1"}},"tags":["nested-reference","unchanged"],"summary":"The Constrained Application Protocol (CoAP) is a RESTful transfer\n protocol for constrained nodes and networks. Basic CoAP messages\n work well for small payloads from sensors and actuators; however,\n applications will need to transfer larger payloads occasionally --\n for instance, for firmware updates. In contrast to HTTP, where TCP\n does the grunt work of segmenting and resequencing, CoAP is based on\n datagram transports such as UDP or Datagram Transport Layer Security\n (DTLS). These transports only offer fragmentation, which is even\n more problematic in constrained nodes and networks, limiting the\n maximum size of resource representations that can practically be\n transferred.\n\n Instead of relying on IP fragmentation, this specification extends\n basic CoAP with a pair of \"Block\" options for transferring multiple\n blocks of information from a resource representation in multiple\n request-","scope_keywords":["7959","delivery","http","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 7959 The Constrained Application Protocol (CoAP) is a RESTful transfer\n protocol for constrained nodes and networks. Basic CoAP messages\n work well for small payloads from sensors and actuators; however,\n applications will need to transfer larger payloads occasionally --\n for instance, for firmware updates. In contrast to HTTP, where TCP\n does the grunt work of segmenting and resequencing, CoAP is based on\n datagram transports such as UDP or Datagram Transport Layer Security\n (DTLS). These transports only offer fragmentation, which is even\n more problematic in constrained nodes and networks, limiting the\n maximum size of resource representations that can practically be\n transferred.\n\n Instead of relying on IP fragmentation, this specification extends\n basic CoAP with a pair of \"Block\" options for transferring multiple\n blocks of information from a resource representation in multiple\n request- 7959 delivery http license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8428","type":"specification","body":"IETF","designation":"RFC 8428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8428.txt","https://www.rfc-editor.org/rfc/rfc8428.pdf"],"folder":"IETF/RFC-8428","files":{"txt":{"path":"standards/IETF/RFC-8428/RFC-8428.txt","sha256":"643195be834507be9e5a8e4c8c506b8c4523159fcdd09b822963971b34faffa9"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a format for representing simple sensor\n measurements and device parameters in Sensor Measurement Lists\n (SenML). Representations are defined in JavaScript Object Notation\n (JSON), Concise Binary Object Representation (CBOR), Extensible\n Markup Language (XML), and Efficient XML Interchange (EXI), which\n share the common SenML data model. A simple sensor, such as a\n temperature sensor, could use one of these media types in protocols\n such as HTTP or the Constrained Application Protocol (CoAP) to\n transport the measurements of the sensor or to be configured.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group ","scope_keywords":["8428","http","https","identification","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null}],"search_text":"IETF RFC 8428 This specification defines a format for representing simple sensor\n measurements and device parameters in Sensor Measurement Lists\n (SenML). Representations are defined in JavaScript Object Notation\n (JSON), Concise Binary Object Representation (CBOR), Extensible\n Markup Language (XML), and Efficient XML Interchange (EXI), which\n share the common SenML data model. A simple sensor, such as a\n temperature sensor, could use one of these media types in protocols\n such as HTTP or the Constrained Application Protocol (CoAP) to\n transport the measurements of the sensor or to be configured.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group  8428 http https identification license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8613","type":"specification","body":"IETF","designation":"RFC 8613","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8613.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8613.txt","https://www.rfc-editor.org/rfc/rfc8613.pdf"],"folder":"IETF/RFC-8613","files":{"txt":{"path":"standards/IETF/RFC-8613/RFC-8613.txt","sha256":"47fe1119e036f4cccc46c2cf8b68a5747e48c85715155f2bbde97d79a8732e78"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Object Security for Constrained RESTful\n Environments (OSCORE), a method for application-layer protection of\n the Constrained Application Protocol (CoAP), using CBOR Object\n Signing and Encryption (COSE). OSCORE provides end-to-end protection\n between endpoints communicating using CoAP or CoAP-mappable HTTP.\n OSCORE is designed for constrained nodes and networks supporting a\n range of proxy operations, including translation between different\n transport protocols.\n\n Although an optional functionality of CoAP, OSCORE alters CoAP\n options processing and IANA registration. Therefore, this document\n updates RFC 7252.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publ","scope_keywords":["8613","encryption","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null}],"search_text":"IETF RFC 8613 This document defines Object Security for Constrained RESTful\n Environments (OSCORE), a method for application-layer protection of\n the Constrained Application Protocol (CoAP), using CBOR Object\n Signing and Encryption (COSE). OSCORE provides end-to-end protection\n between endpoints communicating using CoAP or CoAP-mappable HTTP.\n OSCORE is designed for constrained nodes and networks supporting a\n range of proxy operations, including translation between different\n transport protocols.\n\n Although an optional functionality of CoAP, OSCORE alters CoAP\n options processing and IANA registration. Therefore, this document\n updates RFC 7252.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publ 8613 encryption http https license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.15.4-","type":"specification","body":"IEEE","designation":"IEEE 802.15.4-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4-.html","download_urls":["https://standards.ieee.org/standard/802.15.4-.html"],"folder":"IEEE/IEEE-802.15.4-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IEEE IEEE 802.15.4- nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4-2003","type":"specification","body":"IEEE","designation":"IEEE 802.15.4-2003","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4-2003.html","download_urls":["https://standards.ieee.org/standard/802.15.4-2003.html"],"folder":"IEEE/IEEE-802.15.4-2003","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null}],"search_text":"IEEE IEEE 802.15.4-2003 nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4-2003.","type":"specification","body":"IEEE","designation":"IEEE 802.15.4-2003.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4-2003..html","download_urls":["https://standards.ieee.org/standard/802.15.4-2003..html"],"folder":"IEEE/IEEE-802.15.4-2003.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null}],"search_text":"IEEE IEEE 802.15.4-2003. nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4-2006","type":"specification","body":"IEEE","designation":"IEEE 802.15.4-2006","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4-2006.html","download_urls":["https://standards.ieee.org/standard/802.15.4-2006.html"],"folder":"IEEE/IEEE-802.15.4-2006","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IEEE IEEE 802.15.4-2006 nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4-2020","type":"specification","body":"IEEE","designation":"IEEE 802.15.4-2020","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4-2020.html","download_urls":["https://standards.ieee.org/standard/802.15.4-2020.html"],"folder":"IEEE/IEEE-802.15.4-2020","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 802.15.4-2020 nested-reference unavailable"},{"id":"IEEE IEEE 802.15.4.","type":"specification","body":"IEEE","designation":"IEEE 802.15.4.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.15.4..html","download_urls":["https://standards.ieee.org/standard/802.15.4..html"],"folder":"IEEE/IEEE-802.15.4.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IEEE IEEE 802.15.4. nested-reference unavailable"},{"id":"IEEE IEEE 802.16","type":"specification","body":"IEEE","designation":"IEEE 802.16","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.16.html","download_urls":["https://standards.ieee.org/standard/802.16.html"],"folder":"IEEE/IEEE-802.16","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IEEE IEEE 802.16 nested-reference unavailable"},{"id":"IETF RFC 5739","type":"specification","body":"IETF","designation":"RFC 5739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5739.txt","https://www.rfc-editor.org/rfc/rfc5739.pdf"],"folder":"IETF/RFC-5739","files":{"txt":{"path":"standards/IETF/RFC-5739/RFC-5739.txt","sha256":"b122b83f01a434aaaa6090476ecc757f522e8f6dabedab2a7f90e8538bf662fe"}},"tags":["nested-reference","unchanged"],"summary":"When Internet Key Exchange Protocol version 2 (IKEv2) is used for\n remote VPN access (client to VPN gateway), the gateway assigns the\n client an IP address from the internal network using IKEv2\n configuration payloads. The configuration payloads specified in RFC\n 4306 work well for IPv4 but make it difficult to use certain features\n of IPv6. This document specifies new configuration attributes for\n IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients,\n enabling all features of IPv6 to be used with the client-gateway\n \"virtual link\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consens","scope_keywords":["5739","attribute","attributes","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null}],"search_text":"IETF RFC 5739 When Internet Key Exchange Protocol version 2 (IKEv2) is used for\n remote VPN access (client to VPN gateway), the gateway assigns the\n client an IP address from the internal network using IKEv2\n configuration payloads. The configuration payloads specified in RFC\n 4306 work well for IPv4 but make it difficult to use certain features\n of IPv6. This document specifies new configuration attributes for\n IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients,\n enabling all features of IPv6 to be used with the client-gateway\n \"virtual link\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consens 5739 attribute attributes authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6036","type":"specification","body":"IETF","designation":"RFC 6036","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6036.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6036.txt","https://www.rfc-editor.org/rfc/rfc6036.pdf"],"folder":"IETF/RFC-6036","files":{"txt":{"path":"standards/IETF/RFC-6036/RFC-6036.txt","sha256":"53bc183f5ef81bdf652f691db067a6c1fbd838101b2cad2e85deb554d9c4ebe2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes practices and plans that are emerging among\n Internet Service Providers for the deployment of IPv6 services. They\n are based on practical experience so far, as well as current plans\n and requirements, reported in a survey of a number of ISPs carried\n out in early 2010. This document identifies a number of technology\n gaps, but it does not make recommendations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informatio","scope_keywords":["6036","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null}],"search_text":"IETF RFC 6036 This document describes practices and plans that are emerging among\n Internet Service Providers for the deployment of IPv6 services. They\n are based on practical experience so far, as well as current plans\n and requirements, reported in a survey of a number of ISPs carried\n out in early 2010. This document identifies a number of technology\n gaps, but it does not make recommendations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informatio 6036 http license management subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.16-","type":"specification","body":"IEEE","designation":"IEEE 802.16-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.16-.html","download_urls":["https://standards.ieee.org/standard/802.16-.html"],"folder":"IEEE/IEEE-802.16-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null}],"search_text":"IEEE IEEE 802.16- nested-reference unavailable"},{"id":"IEEE IEEE 802.16-2004","type":"specification","body":"IEEE","designation":"IEEE 802.16-2004","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.16-2004.html","download_urls":["https://standards.ieee.org/standard/802.16-2004.html"],"folder":"IEEE/IEEE-802.16-2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null}],"search_text":"IEEE IEEE 802.16-2004 nested-reference unavailable"},{"id":"IEEE IEEE 802.16-2009","type":"specification","body":"IEEE","designation":"IEEE 802.16-2009","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.16-2009.html","download_urls":["https://standards.ieee.org/standard/802.16-2009.html"],"folder":"IEEE/IEEE-802.16-2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IEEE IEEE 802.16-2009 nested-reference unavailable"},{"id":"IEEE IEEE 802.16.","type":"specification","body":"IEEE","designation":"IEEE 802.16.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.16..html","download_urls":["https://standards.ieee.org/standard/802.16..html"],"folder":"IEEE/IEEE-802.16.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IEEE IEEE 802.16. nested-reference unavailable"},{"id":"IEEE IEEE 802.2","type":"specification","body":"IEEE","designation":"IEEE 802.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.2.html","download_urls":["https://standards.ieee.org/standard/802.2.html"],"folder":"IEEE/IEEE-802.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1054","folder":"IETF/RFC-1054","source":"IETF/RFC-1054/RFC-1054.txt","version":null},{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1103","folder":"IETF/RFC-1103","source":"IETF/RFC-1103/RFC-1103.txt","version":null},{"body":"IETF","designation":"RFC 1112","folder":"IETF/RFC-1112","source":"IETF/RFC-1112/RFC-1112.txt","version":null},{"body":"IETF","designation":"RFC 1132","folder":"IETF/RFC-1132","source":"IETF/RFC-1132/RFC-1132.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1469","folder":"IETF/RFC-1469","source":"IETF/RFC-1469/RFC-1469.txt","version":null},{"body":"IETF","designation":"RFC 1483","folder":"IETF/RFC-1483","source":"IETF/RFC-1483/RFC-1483.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 935","folder":"IETF/RFC-935","source":"IETF/RFC-935/RFC-935.txt","version":null},{"body":"IETF","designation":"RFC 948","folder":"IETF/RFC-948","source":"IETF/RFC-948/RFC-948.txt","version":null},{"body":"IETF","designation":"RFC 988","folder":"IETF/RFC-988","source":"IETF/RFC-988/RFC-988.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IEEE IEEE 802.2 nested-reference unavailable"},{"id":"IETF RFC 1054","type":"specification","body":"IETF","designation":"RFC 1054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1054.txt","https://www.rfc-editor.org/rfc/rfc1054.pdf"],"folder":"IETF/RFC-1054","files":{"txt":{"path":"standards/IETF/RFC-1054/RFC-1054.txt","sha256":"ccbb9481f8a86344b5c2240157169adecfd4e73fa3f05ffef49f596187deee5c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Deering\nRequest for Comments: 1054 Stanford University\nObsoletes: RFC 988 May 1988\n\n Host Extensions for IP Multicasting\n\n1. STATUS OF THIS MEMO\n\n This memo specifies the extensions required of a host implementation\n of the Internet Protocol (IP) to support multicasting. It is\n proposed as a standard for IP multicasting in the Internet. This\n specification is a major revision of RFC-988; changes from RFC-988\n are listed in an Appendix. Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n IP multicasting is defined as the transmission of an IP datagram to a\n \"host group\", a set of zero or more hosts identified by a single IP\n destination address. A multicast datagram is delivered to all\n members of its destination host group with the same \"best-efforts\"\n reliability as regular unicast IP datagrams, i.e., the datagram is\n not guaranteed to arrive intact at al","scope_keywords":["1054","algorithm","algorithms","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1075","folder":"IETF/RFC-1075","source":"IETF/RFC-1075/RFC-1075.txt","version":null},{"body":"IETF","designation":"RFC 1077","folder":"IETF/RFC-1077","source":"IETF/RFC-1077/RFC-1077.txt","version":null}],"search_text":"IETF RFC 1054 Network Working Group S. Deering\nRequest for Comments: 1054 Stanford University\nObsoletes: RFC 988 May 1988\n\n Host Extensions for IP Multicasting\n\n1. STATUS OF THIS MEMO\n\n This memo specifies the extensions required of a host implementation\n of the Internet Protocol (IP) to support multicasting. It is\n proposed as a standard for IP multicasting in the Internet. This\n specification is a major revision of RFC-988; changes from RFC-988\n are listed in an Appendix. Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n IP multicasting is defined as the transmission of an IP datagram to a\n \"host group\", a set of zero or more hosts identified by a single IP\n destination address. A multicast datagram is delivered to all\n members of its destination host group with the same \"best-efforts\"\n reliability as regular unicast IP datagrams, i.e., the datagram is\n not guaranteed to arrive intact at al 1054 algorithm algorithms delivery management subject nested-reference unchanged"},{"id":"IETF RFC 1112","type":"specification","body":"IETF","designation":"RFC 1112","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1112.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1112.txt","https://www.rfc-editor.org/rfc/rfc1112.pdf"],"folder":"IETF/RFC-1112","files":{"txt":{"path":"standards/IETF/RFC-1112/RFC-1112.txt","sha256":"677f3163f4f495f2cacc95aaf718d465e897b38a6aaf8774bf4f618e04b940f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Deering\nRequest for Comments: 1112 Stanford University\nObsoletes: RFCs 988, 1054 August 1989\n\n Host Extensions for IP Multicasting\n\n1. STATUS OF THIS MEMO\n\n This memo specifies the extensions required of a host implementation\n of the Internet Protocol (IP) to support multicasting. It is the\n recommended standard for IP multicasting in the Internet.\n Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n IP multicasting is the transmission of an IP datagram to a \"host\n group\", a set of zero or more hosts identified by a single IP\n destination address. A multicast datagram is delivered to all\n members of its destination host group with the same \"best-efforts\"\n reliability as regular unicast IP datagrams, i.e., the datagram is\n not guaranteed to arrive intact at all members of the destination\n group or in the same order relative to other datagrams.\n\n The members","scope_keywords":["1112","algorithm","algorithms","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1131","folder":"IETF/RFC-1131","source":"IETF/RFC-1131/RFC-1131.pdf","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1234","folder":"IETF/RFC-1234","source":"IETF/RFC-1234/RFC-1234.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1287","folder":"IETF/RFC-1287","source":"IETF/RFC-1287/RFC-1287.txt","version":null},{"body":"IETF","designation":"RFC 1301","folder":"IETF/RFC-1301","source":"IETF/RFC-1301/RFC-1301.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1469","folder":"IETF/RFC-1469","source":"IETF/RFC-1469/RFC-1469.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1693","folder":"IETF/RFC-1693","source":"IETF/RFC-1693/RFC-1693.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 1769","folder":"IETF/RFC-1769","source":"IETF/RFC-1769/RFC-1769.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2117","folder":"IETF/RFC-2117","source":"IETF/RFC-2117/RFC-2117.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2236","folder":"IETF/RFC-2236","source":"IETF/RFC-2236/RFC-2236.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2362","folder":"IETF/RFC-2362","source":"IETF/RFC-2362/RFC-2362.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2658","folder":"IETF/RFC-2658","source":"IETF/RFC-2658/RFC-2658.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2771","folder":"IETF/RFC-2771","source":"IETF/RFC-2771/RFC-2771.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3208","folder":"IETF/RFC-3208","source":"IETF/RFC-3208/RFC-3208.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 1112 Network Working Group S. Deering\nRequest for Comments: 1112 Stanford University\nObsoletes: RFCs 988, 1054 August 1989\n\n Host Extensions for IP Multicasting\n\n1. STATUS OF THIS MEMO\n\n This memo specifies the extensions required of a host implementation\n of the Internet Protocol (IP) to support multicasting. It is the\n recommended standard for IP multicasting in the Internet.\n Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n IP multicasting is the transmission of an IP datagram to a \"host\n group\", a set of zero or more hosts identified by a single IP\n destination address. A multicast datagram is delivered to all\n members of its destination host group with the same \"best-efforts\"\n reliability as regular unicast IP datagrams, i.e., the datagram is\n not guaranteed to arrive intact at all members of the destination\n group or in the same order relative to other datagrams.\n\n The members 1112 algorithm algorithms delivery management subject nested-reference unchanged"},{"id":"IETF RFC 1377","type":"specification","body":"IETF","designation":"RFC 1377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1377.txt","https://www.rfc-editor.org/rfc/rfc1377.pdf"],"folder":"IETF/RFC-1377","files":{"txt":{"path":"standards/IETF/RFC-1377/RFC-1377.txt","sha256":"72e2830f56beb971d5303503f76d2822207ef44c7b57edceb87846f0f57533b2"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring OSI\n Network Layer Protocols.\n\n This memo is the product of the Point-to-Point Protocol Working Group\n of the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu mailing list.","scope_keywords":["1377","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 1377 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring OSI\n Network Layer Protocols.\n\n This memo is the product of the Point-to-Point Protocol Working Group\n of the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu mailing list. 1377 pid nested-reference unchanged"},{"id":"IETF RFC 1457","type":"specification","body":"IETF","designation":"RFC 1457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1457.txt","https://www.rfc-editor.org/rfc/rfc1457.pdf"],"folder":"IETF/RFC-1457","files":{"txt":{"path":"standards/IETF/RFC-1457/RFC-1457.txt","sha256":"0b08c26a073f02de958e98480235a7c6044629558d72210f27ce7e0210e555fe"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Housley\nRequest for Comments: 1457 Xerox Special Information Systems\n May 1993\n\n Security Label Framework for the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowledgements\n\n The members of the Privacy and Security Research Group and the\n attendees of the invitational Security Labels Workshop (hosted by the\n National Institute of Standards and Technology) helped me organize my\n thoughts on this subject. The ideas of these professionals are\n scattered throughout the memo.\n\n1.0 Introduction\n\n This memo presents a security labeling framework for the Internet.\n The framework is intended to help protocol designers determine what,\n if any, security labeling should be supported by their protocols.\n The framework should also help network a","scope_keywords":["1457","attribute","management","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1457 Network Working Group R. Housley\nRequest for Comments: 1457 Xerox Special Information Systems\n May 1993\n\n Security Label Framework for the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowledgements\n\n The members of the Privacy and Security Research Group and the\n attendees of the invitational Security Labels Workshop (hosted by the\n National Institute of Standards and Technology) helped me organize my\n thoughts on this subject. The ideas of these professionals are\n scattered throughout the memo.\n\n1.0 Introduction\n\n This memo presents a security labeling framework for the Internet.\n The framework is intended to help protocol designers determine what,\n if any, security labeling should be supported by their protocols.\n The framework should also help network a 1457 attribute management path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1469","type":"specification","body":"IETF","designation":"RFC 1469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1469.txt","https://www.rfc-editor.org/rfc/rfc1469.pdf"],"folder":"IETF/RFC-1469","files":{"txt":{"path":"standards/IETF/RFC-1469/RFC-1469.txt","sha256":"70f089006235f14639239395209bf9bdcae582e4fcbef5948ea9a1b42f08f9be"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for the transmission of IP multicast\n datagrams over Token-Ring Local Area Networks. Although an interim\n solution has emerged and is currently being used, it is the intention\n of this document to specify a more efficient means of transmission\n using an assigned Token-Ring functional address.","scope_keywords":["1469"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null}],"search_text":"IETF RFC 1469 This document specifies a method for the transmission of IP multicast\n datagrams over Token-Ring Local Area Networks. Although an interim\n solution has emerged and is currently being used, it is the intention\n of this document to specify a more efficient means of transmission\n using an assigned Token-Ring functional address. 1469 nested-reference unchanged"},{"id":"IETF RFC 1561","type":"specification","body":"IETF","designation":"RFC 1561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1561.txt","https://www.rfc-editor.org/rfc/rfc1561.pdf"],"folder":"IETF/RFC-1561","files":{"txt":{"path":"standards/IETF/RFC-1561/RFC-1561.txt","sha256":"80fb3983340f773d956b07e58ad2d68c39839a89412027ee5dffa468561a565a"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode\n Network Layer Protocol (CLNP, [1]) for use in conjunction with RFC\n 1347, TCP/UDP over Bigger Addresses (TUBA, [2]). It describes the\n use of CLNP to provide the lower-level service expected by\n Transmission Control Protocol (TCP, [3]) and User Datagram Protocol\n (UDP, [4]). CLNP provides essentially the same datagram service as\n Internet Protocol (IP, [5]), but offers a means of conveying bigger\n network addresses (with additional structure, to aid routing).\n\n While the protocols offer nearly the same services, IP and CLNP are\n not identical. This document describes a means of preserving the\n semantics of IP information that is absent from CLNP while preserving\n consistency between the use of CLNP in Internet and OSI environments.\n This maximizes the use of already-deployed CLNP implementations.\n\nAcknowledgments\n\n Ma","scope_keywords":["1561","identification","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1561 This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode\n Network Layer Protocol (CLNP, [1]) for use in conjunction with RFC\n 1347, TCP/UDP over Bigger Addresses (TUBA, [2]). It describes the\n use of CLNP to provide the lower-level service expected by\n Transmission Control Protocol (TCP, [3]) and User Datagram Protocol\n (UDP, [4]). CLNP provides essentially the same datagram service as\n Internet Protocol (IP, [5]), but offers a means of conveying bigger\n network addresses (with additional structure, to aid routing).\n\n While the protocols offer nearly the same services, IP and CLNP are\n not identical. This document describes a means of preserving the\n semantics of IP information that is absent from CLNP while preserving\n consistency between the use of CLNP in Internet and OSI environments.\n This maximizes the use of already-deployed CLNP implementations.\n\nAcknowledgments\n\n Ma 1561 identification profile timestamp nested-reference unchanged"},{"id":"IETF RFC 1683","type":"specification","body":"IETF","designation":"RFC 1683","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1683.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1683.txt","https://www.rfc-editor.org/rfc/rfc1683.pdf"],"folder":"IETF/RFC-1683","files":{"txt":{"path":"standards/IETF/RFC-1683/RFC-1683.txt","sha256":"2dfd7680e11ef042f19fd94f110db1ef04be12953b7f04d1191b0551f8b1bff3"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n1. Executive Summary\n\n The two most commonly cited issues motivating the introduction of\n IPng are address depletion and routing table growth in IPv4. Further\n motivation is the fact that the Internet is witnessing an increasing\n diversity in the protocols and services found in the network. When\n evaluating alternatives for IPng, we should consider how well each\n alternative addresses the problems arising from this diversity. In\n this document, we identify several features that affect a protocol's\n ability to operate in a multiprotocol environment and propose the\n incorporation of these features into IPng.\n\n Our thesis, succinctly st","scope_keywords":["1683","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1683 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n1. Executive Summary\n\n The two most commonly cited issues motivating the introduction of\n IPng are address depletion and routing table growth in IPv4. Further\n motivation is the fact that the Internet is witnessing an increasing\n diversity in the protocols and services found in the network. When\n evaluating alternatives for IPng, we should consider how well each\n alternative addresses the problems arising from this diversity. In\n this document, we identify several features that affect a protocol's\n ability to operate in a multiprotocol environment and propose the\n incorporation of these features into IPng.\n\n Our thesis, succinctly st 1683 risk nested-reference unchanged"},{"id":"IETF RFC 2665","type":"specification","body":"IETF","designation":"RFC 2665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2665.txt","https://www.rfc-editor.org/rfc/rfc2665.pdf"],"folder":"IETF/RFC-2665","files":{"txt":{"path":"standards/IETF/RFC-2665/RFC-2665.txt","sha256":"c0fdbe8dc2dadafbc6cac1376eb94cbbbb6d7e6e20a1c564a0bce40659b9be61"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 2358, \"Definitions of Managed Objects for the\n Ethernet-like Interface Types\". This memo extends that specification\n by including management information useful for the management of 1000\n Mb/s and full-duplex Ethernet interfaces.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflects a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n or new documents might be issue","scope_keywords":["2665","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 2665 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 2358, \"Definitions of Managed Objects for the\n Ethernet-like Interface Types\". This memo extends that specification\n by including management information useful for the management of 1000\n Mb/s and full-duplex Ethernet interfaces.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflects a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n or new documents might be issue 2665 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 3635","type":"specification","body":"IETF","designation":"RFC 3635","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3635.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3635.txt","https://www.rfc-editor.org/rfc/rfc3635.pdf"],"folder":"IETF/RFC-3635","files":{"txt":{"path":"standards/IETF/RFC-3635/RFC-3635.txt","sha256":"a863d05343336da19b3a533c8c24794bbb35bc333d0c75af0869b50a8f97650b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing Ethernet-like\n interfaces. This memo obsoletes RFC 2665. It updates that\n specification by including management information useful for the\n management of 10 Gigabit per second (Gb/s) Ethernet interfaces.","scope_keywords":["3635","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 3635 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing Ethernet-like\n interfaces. This memo obsoletes RFC 2665. It updates that\n specification by including management information useful for the\n management of 10 Gigabit per second (Gb/s) Ethernet interfaces. 3635 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 4044","type":"specification","body":"IETF","designation":"RFC 4044","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4044.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4044.txt","https://www.rfc-editor.org/rfc/rfc4044.pdf"],"folder":"IETF/RFC-4044","files":{"txt":{"path":"standards/IETF/RFC-4044/RFC-4044.txt","sha256":"0e89881bd56f38d28fc81edc44b1297f6f0b476649a63fc546cc79e33427e79f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for information related\n to the Fibre Channel.","scope_keywords":["4044","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4044 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for information related\n to the Fibre Channel. 4044 management nested-reference unchanged"},{"id":"IETF RFC 935","type":"specification","body":"IETF","designation":"RFC 935","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc935.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc935.txt","https://www.rfc-editor.org/rfc/rfc935.pdf"],"folder":"IETF/RFC-935","files":{"txt":{"path":"standards/IETF/RFC-935/RFC-935.txt","sha256":"bcc4a8b36fb26692f34d005bbef5b3ff086b43ae00b340eaae3f5ba3e32819bc"}},"tags":["nested-reference","unchanged"],"summary":"processor. In one case, this is an additive check and in the other\n it is an exclusive-or (or parity) check. Although the additive check\n is slightly more powerful than the exclusive-or, both are relatively\n weak compared to CRC techniques.","scope_keywords":["935"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null}],"search_text":"IETF RFC 935 processor. In one case, this is an additive check and in the other\n it is an exclusive-or (or parity) check. Although the additive check\n is slightly more powerful than the exclusive-or, both are relatively\n weak compared to CRC techniques. 935 nested-reference unchanged"},{"id":"IETF RFC 988","type":"specification","body":"IETF","designation":"RFC 988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc988.txt","https://www.rfc-editor.org/rfc/rfc988.pdf"],"folder":"IETF/RFC-988","files":{"txt":{"path":"standards/IETF/RFC-988/RFC-988.txt","sha256":"d49258829165f645c56c100b75acf8e6692a803dcb233ebd2681726cabde6ff0"}},"tags":["nested-reference","unchanged"],"summary":"hosts. There is at least one multicast agent directly attached to\n every IP network or subnetwork that supports IP multicasting. A host\n requests the creation of new groups, and joins or leaves existing\n groups, by exchanging messages with a neighboring agent.","scope_keywords":["988","algorithm","algorithms","delivery","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1054","folder":"IETF/RFC-1054","source":"IETF/RFC-1054/RFC-1054.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 988 hosts. There is at least one multicast agent directly attached to\n every IP network or subnetwork that supports IP multicasting. A host\n requests the creation of new groups, and joins or leaves existing\n groups, by exchanging messages with a neighboring agent. 988 algorithm algorithms delivery key management subject nested-reference unchanged"},{"id":"IEEE IEEE 802.2-1985","type":"specification","body":"IEEE","designation":"IEEE 802.2-1985","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.2-1985.html","download_urls":["https://standards.ieee.org/standard/802.2-1985.html"],"folder":"IEEE/IEEE-802.2-1985","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null}],"search_text":"IEEE IEEE 802.2-1985 nested-reference unavailable"},{"id":"IEEE IEEE 802.2-1989","type":"specification","body":"IEEE","designation":"IEEE 802.2-1989","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.2-1989.html","download_urls":["https://standards.ieee.org/standard/802.2-1989.html"],"folder":"IEEE/IEEE-802.2-1989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1294","folder":"IETF/RFC-1294","source":"IETF/RFC-1294/RFC-1294.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null}],"search_text":"IEEE IEEE 802.2-1989 nested-reference unavailable"},{"id":"IEEE IEEE 802.2.","type":"specification","body":"IEEE","designation":"IEEE 802.2.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.2..html","download_urls":["https://standards.ieee.org/standard/802.2..html"],"folder":"IEEE/IEEE-802.2.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IEEE IEEE 802.2. nested-reference unavailable"},{"id":"IEEE IEEE 802.21","type":"specification","body":"IEEE","designation":"IEEE 802.21","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.21.html","download_urls":["https://standards.ieee.org/standard/802.21.html"],"folder":"IEEE/IEEE-802.21","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IEEE IEEE 802.21 nested-reference unavailable"},{"id":"IETF RFC 5164","type":"specification","body":"IETF","designation":"RFC 5164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5164.txt","https://www.rfc-editor.org/rfc/rfc5164.pdf"],"folder":"IETF/RFC-5164","files":{"txt":{"path":"standards/IETF/RFC-5164/RFC-5164.txt","sha256":"f42269d85bf8a9c6164dccf78b1c03a3a2d471b7e92f64d21e44873309f58ca0"}},"tags":["nested-reference","unchanged"],"summary":"There are ongoing activities in the networking community to develop\n solutions that aid in IP handover mechanisms between heterogeneous\n wired and wireless access systems including, but not limited to, IEEE\n 802.21. Intelligent access selection, taking into account link-layer\n attributes, requires the delivery of a variety of different\n information types to the terminal from different sources within the\n network and vice-versa. The protocol requirements for this\n signalling have both transport and security issues that must be\n considered. The signalling must not be constrained to specific link\n types, so there is at least a common component to the signalling\n problem, which is within the scope of the IETF. This document\n presents a problem statement for this core problem.\n\nMelia, et al. Informational [Page 1]\n\f\nRFC 5164 Mobility Services Transport March 2008","scope_keywords":["5164","attribute","attributes","delivery","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 5164 There are ongoing activities in the networking community to develop\n solutions that aid in IP handover mechanisms between heterogeneous\n wired and wireless access systems including, but not limited to, IEEE\n 802.21. Intelligent access selection, taking into account link-layer\n attributes, requires the delivery of a variety of different\n information types to the terminal from different sources within the\n network and vice-versa. The protocol requirements for this\n signalling have both transport and security issues that must be\n considered. The signalling must not be constrained to specific link\n types, so there is at least a common component to the signalling\n problem, which is within the scope of the IETF. This document\n presents a problem statement for this core problem.\n\nMelia, et al. Informational [Page 1]\n\f\nRFC 5164 Mobility Services Transport March 2008 5164 attribute attributes delivery key management nested-reference unchanged"},{"id":"IETF RFC 5677","type":"specification","body":"IETF","designation":"RFC 5677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5677.txt","https://www.rfc-editor.org/rfc/rfc5677.pdf"],"folder":"IETF/RFC-5677","files":{"txt":{"path":"standards/IETF/RFC-5677/RFC-5677.txt","sha256":"63bead13a168c8a04e3dc81a403f61f58ef1e55515d8c6cb0f60f698f4580064"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mobility services framework design (MSFD)\n for the IEEE 802.21 Media Independent Handover (MIH) protocol that\n addresses identified issues associated with the transport of MIH\n messages. The document also describes mechanisms for Mobility\n Services (MoS) discovery and transport-layer mechanisms for the\n reliable delivery of MIH messages. This document does not provide\n mechanisms for securing the communication between a mobile node (MN)\n and the Mobility Server. Instead, it is assumed that either lower-\n layer (e.g., link-layer) security mechanisms or overall system-\n specific proprietary security solutions are used.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Stand","scope_keywords":["5677","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 5677 This document describes a mobility services framework design (MSFD)\n for the IEEE 802.21 Media Independent Handover (MIH) protocol that\n addresses identified issues associated with the transport of MIH\n messages. The document also describes mechanisms for Mobility\n Services (MoS) discovery and transport-layer mechanisms for the\n reliable delivery of MIH messages. This document does not provide\n mechanisms for securing the communication between a mobile node (MN)\n and the Mobility Server. Instead, it is assumed that either lower-\n layer (e.g., link-layer) security mechanisms or overall system-\n specific proprietary security solutions are used.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Stand 5677 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5873","type":"specification","body":"IETF","designation":"RFC 5873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5873.txt","https://www.rfc-editor.org/rfc/rfc5873.pdf"],"folder":"IETF/RFC-5873","files":{"txt":{"path":"standards/IETF/RFC-5873/RFC-5873.txt","sha256":"8632c32df983559e092e697190a9bd6ecc3f2f94f1b76787eddfee8192dddc3d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Protocol for Carrying\n Authentication for Network Access (PANA) for proactively establishing\n a PANA Security Association between a PANA Client in one access\n network and a PANA Authentication Agent in another access network to\n which the PANA Client may move.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,","scope_keywords":["5873","authentication","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null}],"search_text":"IETF RFC 5873 This document defines an extension to the Protocol for Carrying\n Authentication for Network Access (PANA) for proactively establishing\n a PANA Security Association between a PANA Client in one access\n network and a PANA Authentication Agent in another access network to\n which the PANA Client may move.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata, 5873 authentication authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6418","type":"specification","body":"IETF","designation":"RFC 6418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6418.txt","https://www.rfc-editor.org/rfc/rfc6418.pdf"],"folder":"IETF/RFC-6418","files":{"txt":{"path":"standards/IETF/RFC-6418/RFC-6418.txt","sha256":"9cbc39908a4a71dbc9950c4574394f5508bc1bf8fd08776364e185b133e67e8f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes issues encountered by a node attached to\n multiple provisioning domains. This node receives configuration\n information from each of its provisioning domains, where some\n configuration objects are global to the node and others are local to\n the interface. Issues such as selecting the wrong interface to send\n traffic happen when conflicting node-scoped configuration objects are\n received and inappropriately used. Moreover, other issues are the\n result of simultaneous attachment to multiple networks, such as\n domain selection or addressing and naming space overlaps, regardless\n of the provisioning mechanism. While multiple provisioning domains\n are typically seen on nodes with multiple interfaces, this document\n also discusses situations involving single-interface nodes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n pub","scope_keywords":["6418","authentication","encryption","http","key","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6419","folder":"IETF/RFC-6419","source":"IETF/RFC-6419/RFC-6419.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null}],"search_text":"IETF RFC 6418 This document describes issues encountered by a node attached to\n multiple provisioning domains. This node receives configuration\n information from each of its provisioning domains, where some\n configuration objects are global to the node and others are local to\n the interface. Issues such as selecting the wrong interface to send\n traffic happen when conflicting node-scoped configuration objects are\n received and inappropriately used. Moreover, other issues are the\n result of simultaneous attachment to multiple networks, such as\n domain selection or addressing and naming space overlaps, regardless\n of the provisioning mechanism. While multiple provisioning domains\n are typically seen on nodes with multiple interfaces, this document\n also discusses situations involving single-interface nodes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n pub 6418 authentication encryption http key license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 8553","type":"specification","body":"IETF","designation":"RFC 8553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8553.txt","https://www.rfc-editor.org/rfc/rfc8553.pdf"],"folder":"IETF/RFC-8553","files":{"txt":{"path":"standards/IETF/RFC-8553/RFC-8553.txt","sha256":"bd2397e9b08ebc0177971d8623c327190835c7e3625caa7575afe234bcadbf13"}},"tags":["nested-reference","unchanged"],"summary":"Using an underscore for a prefix creates a space for constrained\n interoperation of resource records. Original uses of an underscore\n character as a domain node name prefix were specified without the\n benefit of an IANA registry. This produced an entirely uncoordinated\n set of name-creation activities, all drawing from the same namespace.\n A registry for these names has now been defined by RFC 8552.\n However, the existing specifications that use underscored naming need\n to be modified in order to be in line with the new registry. This\n document specifies those changes. The changes preserve existing\n software and operational practice, while adapting the specifications\n for those practices to the newer underscore registry model.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It repre","scope_keywords":["8553","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 8553 Using an underscore for a prefix creates a space for constrained\n interoperation of resource records. Original uses of an underscore\n character as a domain node name prefix were specified without the\n benefit of an IANA registry. This produced an entirely uncoordinated\n set of name-creation activities, all drawing from the same namespace.\n A registry for these names has now been defined by RFC 8552.\n However, the existing specifications that use underscored naming need\n to be modified in order to be in line with the new registry. This\n document specifies those changes. The changes preserve existing\n software and operational practice, while adapting the specifications\n for those practices to the newer underscore registry model.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It repre 8553 http https key license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.21.","type":"specification","body":"IEEE","designation":"IEEE 802.21.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.21..html","download_urls":["https://standards.ieee.org/standard/802.21..html"],"folder":"IEEE/IEEE-802.21.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null}],"search_text":"IEEE IEEE 802.21. nested-reference unavailable"},{"id":"IEEE IEEE 802.22","type":"specification","body":"IEEE","designation":"IEEE 802.22","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.22.html","download_urls":["https://standards.ieee.org/standard/802.22.html"],"folder":"IEEE/IEEE-802.22","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null}],"search_text":"IEEE IEEE 802.22 nested-reference unavailable"},{"id":"IEEE IEEE 802.3","type":"specification","body":"IEEE","designation":"IEEE 802.3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3.html","download_urls":["https://standards.ieee.org/standard/802.3.html"],"folder":"IEEE/IEEE-802.3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1009","folder":"IETF/RFC-1009","source":"IETF/RFC-1009/RFC-1009.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1028","folder":"IETF/RFC-1028","source":"IETF/RFC-1028/RFC-1028.txt","version":null},{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1055","folder":"IETF/RFC-1055","source":"IETF/RFC-1055/RFC-1055.txt","version":null},{"body":"IETF","designation":"RFC 1122","folder":"IETF/RFC-1122","source":"IETF/RFC-1122/RFC-1122.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1369","folder":"IETF/RFC-1369","source":"IETF/RFC-1369/RFC-1369.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null},{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2063","folder":"IETF/RFC-2063","source":"IETF/RFC-2063/RFC-2063.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2285","folder":"IETF/RFC-2285","source":"IETF/RFC-2285/RFC-2285.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 948","folder":"IETF/RFC-948","source":"IETF/RFC-948/RFC-948.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 985","folder":"IETF/RFC-985","source":"IETF/RFC-985/RFC-985.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IEEE IEEE 802.3 nested-reference unavailable"},{"id":"IETF RFC 1000","type":"specification","body":"IETF","designation":"RFC 1000","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1000.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1000.txt","https://www.rfc-editor.org/rfc/rfc1000.pdf"],"folder":"IETF/RFC-1000","files":{"txt":{"path":"standards/IETF/RFC-1000/RFC-1000.txt","sha256":"3dc747b95702955de449d1044fd16c4f6fb21fc0b8835a2e40a6f3ebd645aa81"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1000 J. Postel\n ISI\n August 1987\n\nObsoletes: RFCs 084, 100, 160, 170, 200, 598, 699, 800, 899, 999\n\n THE REQUEST FOR COMMENTS REFERENCE GUIDE\n\nSTATUS OF THIS MEMO\n\n This RFC is a reference guide for the Internet community which\n summarizes of all the Request for Comments issued between April 1969\n and March 1987. This guide also categorizes the RFCs by topic.\n\nINTRODUCTION\n\n This RFC Reference Guide is intended to provide a historical account\n by categorizing and summarizing of the Request for Comments numbers 1\n through 999 issued between the years 1969-1987. These documents have\n been crossed referenced to indicate which RFCs are current, obsolete,\n or revised. Distribution of this memo is unlimited.\n\nTHE ORIGINS OF RFCS - by Stephen D. Crocker\n\n The DDN community now includes hundreds of nodes and thousands of\n users, but once it","scope_keywords":["1000"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null}],"search_text":"IETF RFC 1000 Network Working Group J. Reynolds\nRequest for Comments: 1000 J. Postel\n ISI\n August 1987\n\nObsoletes: RFCs 084, 100, 160, 170, 200, 598, 699, 800, 899, 999\n\n THE REQUEST FOR COMMENTS REFERENCE GUIDE\n\nSTATUS OF THIS MEMO\n\n This RFC is a reference guide for the Internet community which\n summarizes of all the Request for Comments issued between April 1969\n and March 1987. This guide also categorizes the RFCs by topic.\n\nINTRODUCTION\n\n This RFC Reference Guide is intended to provide a historical account\n by categorizing and summarizing of the Request for Comments numbers 1\n through 999 issued between the years 1969-1987. These documents have\n been crossed referenced to indicate which RFCs are current, obsolete,\n or revised. Distribution of this memo is unlimited.\n\nTHE ORIGINS OF RFCS - by Stephen D. Crocker\n\n The DDN community now includes hundreds of nodes and thousands of\n users, but once it 1000 nested-reference unchanged"},{"id":"IETF RFC 1028","type":"specification","body":"IETF","designation":"RFC 1028","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1028.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1028.txt","https://www.rfc-editor.org/rfc/rfc1028.pdf"],"folder":"IETF/RFC-1028","files":{"txt":{"path":"standards/IETF/RFC-1028/RFC-1028.txt","sha256":"4d8e5be3966508d8a851d6c2d4f9c1212d0cd83662ec7c60d2d2e5f9210efb38"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Davin\nRequest for Comments: 1028 Proteon, Inc.\n J. Case\n University of Tennessee at Knoxville\n M. Fedor\n Cornell University\n M. Schoffstall\n Rensselaer Polytechnic Institute\n November 1987\n\n A Simple Gateway Monitoring Protocol\n\n1. Status of this Memo\n\n This document is being distributed to members of the Internet\n community in order to solicit their reactions to the proposals\n contained in it. While the issues discussed may not be directly\n relevant to the research problems of the Internet, they may be\n interesting to a number of researchers and implementors.\n\n This memo defines a simple application-layer protocol by which\n management information for a gateway may be inspected or altered by\n logically remote users.\n\n This proposal is intended only as an interim response to immediate\n gateway monitoring needs while work on more elaborate and robust\n designs proce","scope_keywords":["1028","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1067","folder":"IETF/RFC-1067","source":"IETF/RFC-1067/RFC-1067.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1028 Network Working Group J. Davin\nRequest for Comments: 1028 Proteon, Inc.\n J. Case\n University of Tennessee at Knoxville\n M. Fedor\n Cornell University\n M. Schoffstall\n Rensselaer Polytechnic Institute\n November 1987\n\n A Simple Gateway Monitoring Protocol\n\n1. Status of this Memo\n\n This document is being distributed to members of the Internet\n community in order to solicit their reactions to the proposals\n contained in it. While the issues discussed may not be directly\n relevant to the research problems of the Internet, they may be\n interesting to a number of researchers and implementors.\n\n This memo defines a simple application-layer protocol by which\n management information for a gateway may be inspected or altered by\n logically remote users.\n\n This proposal is intended only as an interim response to immediate\n gateway monitoring needs while work on more elaborate and robust\n designs proce 1028 authentication management nested-reference unchanged"},{"id":"IETF RFC 1055","type":"specification","body":"IETF","designation":"RFC 1055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1055.txt","https://www.rfc-editor.org/rfc/rfc1055.pdf"],"folder":"IETF/RFC-1055","files":{"txt":{"path":"standards/IETF/RFC-1055/RFC-1055.txt","sha256":"8450ae6449617e99ac11099619b54d37c59dcd566f6d95cfacec1abad35fbc87"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Romkey\nRequest for Comments: 1055 June l988\n\n A NONSTANDARD FOR TRANSMISSION OF IP DATAGRAMS OVER SERIAL LINES: SLIP\n\nINTRODUCTION\n\n The TCP/IP protocol family runs over a variety of network media:\n IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines,\n satellite links, and serial lines. There are standard encapsulations\n for IP packets defined for many of these networks, but there is no\n standard for serial lines. SLIP, Serial Line IP, is a currently a de\n facto standard, commonly used for point-to-point serial connections\n running TCP/IP. It is not an Internet standard. Distribution of\n this memo is unlimited.\n\nHISTORY\n\n SLIP has its origins in the 3COM UNET TCP/IP implementation from the\n early 1980's. It is merely a packet framing protocol: SLIP defines a\n sequence of characters that frame IP packets on a serial line, and\n nothing more. It provides ","scope_keywords":["1055","algorithm","algorithms","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1055 Network Working Group J. Romkey\nRequest for Comments: 1055 June l988\n\n A NONSTANDARD FOR TRANSMISSION OF IP DATAGRAMS OVER SERIAL LINES: SLIP\n\nINTRODUCTION\n\n The TCP/IP protocol family runs over a variety of network media:\n IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines,\n satellite links, and serial lines. There are standard encapsulations\n for IP packets defined for many of these networks, but there is no\n standard for serial lines. SLIP, Serial Line IP, is a currently a de\n facto standard, commonly used for point-to-point serial connections\n running TCP/IP. It is not an Internet standard. Distribution of\n this memo is unlimited.\n\nHISTORY\n\n SLIP has its origins in the 3COM UNET TCP/IP implementation from the\n early 1980's. It is merely a packet framing protocol: SLIP defines a\n sequence of characters that frame IP packets on a serial line, and\n nothing more. It provides  1055 algorithm algorithms identification key nested-reference unchanged"},{"id":"IETF RFC 1284","type":"specification","body":"IETF","designation":"RFC 1284","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1284.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1284.txt","https://www.rfc-editor.org/rfc/rfc1284.pdf"],"folder":"IETF/RFC-1284","files":{"txt":{"path":"standards/IETF/RFC-1284/RFC-1284.txt","sha256":"7470036ddbf6b515cb34373ec4860fa3dd22bc02b5cc69e9fd645f39dbc0b8e5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing ethernet-like objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n\nTransmission MIB Working Group [Page 1]\n\f\nRFC 1284 ETHERNET-LIKE OBJECTS December 1991\n\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SN","scope_keywords":["1284","attribute","attributes","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 1284 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing ethernet-like objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n\nTransmission MIB Working Group [Page 1]\n\f\nRFC 1284 ETHERNET-LIKE OBJECTS December 1991\n\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SN 1284 attribute attributes management subject nested-reference unchanged"},{"id":"IETF RFC 1369","type":"specification","body":"IETF","designation":"RFC 1369","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1369.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1369.txt","https://www.rfc-editor.org/rfc/rfc1369.pdf"],"folder":"IETF/RFC-1369","files":{"txt":{"path":"standards/IETF/RFC-1369/RFC-1369.txt","sha256":"8045090d0a30100947fd0f05a777675573458141d04092d69f019489d38ddee9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz\nRequest for Comments: 1369 FTP Software\n October 1992\n\n Implementation Notes and Experience for\n The Internet Ethernet MIB\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. Observations ................................................ 2\n 3. Conclusions ................................................. 3\n 4. Final Action ................................................ 4\n 5. Implementation Data ......................................... 5\n 6. Security Considerations ..................................... 7\n 7. Author's Address ............................................ 7\n\n1. Introduction\n\n The Ethernet MIB Working group has been tasked with the foll","scope_keywords":["1369"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null}],"search_text":"IETF RFC 1369 Network Working Group F. Kastenholz\nRequest for Comments: 1369 FTP Software\n October 1992\n\n Implementation Notes and Experience for\n The Internet Ethernet MIB\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. Observations ................................................ 2\n 3. Conclusions ................................................. 3\n 4. Final Action ................................................ 4\n 5. Implementation Data ......................................... 5\n 6. Security Considerations ..................................... 7\n 7. Author's Address ............................................ 7\n\n1. Introduction\n\n The Ethernet MIB Working group has been tasked with the foll 1369 nested-reference unchanged"},{"id":"IETF RFC 1398","type":"specification","body":"IETF","designation":"RFC 1398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1398.txt","https://www.rfc-editor.org/rfc/rfc1398.pdf"],"folder":"IETF/RFC-1398","files":{"txt":{"path":"standards/IETF/RFC-1398/RFC-1398.txt","sha256":"66daab7952a25f548ad545296f97701e32ff775158e722442e6d23865a6380f8"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing ethernet-like objects.","scope_keywords":["1398","attribute","attributes","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 1398 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing ethernet-like objects. 1398 attribute attributes management subject nested-reference unchanged"},{"id":"IETF RFC 1515","type":"specification","body":"IETF","designation":"RFC 1515","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1515.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1515.txt","https://www.rfc-editor.org/rfc/rfc1515.pdf"],"folder":"IETF/RFC-1515","files":{"txt":{"path":"standards/IETF/RFC-1515/RFC-1515.txt","sha256":"d43f6df1759324ef72748c389e8bd217718351da8ce6779ffc3f590322b17118"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing IEEE 802.3\n Medium Attachment Units (MAUs).","scope_keywords":["1515","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null}],"search_text":"IETF RFC 1515 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing IEEE 802.3\n Medium Attachment Units (MAUs). 1515 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1584","type":"specification","body":"IETF","designation":"RFC 1584","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1584.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1584.txt","https://www.rfc-editor.org/rfc/rfc1584.pdf"],"folder":"IETF/RFC-1584","files":{"pdf":{"path":"standards/IETF/RFC-1584/RFC-1584.pdf","sha256":"fdd8fc9d03fa543d37e10fd258002eb54255b42216ecf632042ca079f9ab0839"},"txt":{"path":"standards/IETF/RFC-1584/RFC-1584.txt","sha256":"0b4c7694b4fb7dcbff92bcffa1495b3ac34be30f26c87c0f74a727008ee45173"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents enhancements to the OSPF protocol enabling the\n routing of IP multicast datagrams. In this proposal, an IP multicast\n packet is routed based both on the packet's source and its multicast\n destination (commonly referred to as source/destination routing). As\n it is routed, the multicast packet follows a shortest path to each\n multicast destination. During packet forwarding, any commonality of\n paths is exploited; when multiple hosts belong to a single multicast\n group, a multicast packet will be replicated only when the paths to\n the separate hosts diverge.\n\n OSPF, a link-state routing protocol, provides a database describing\n the Autonomous System's topology. A new OSPF link state\n advertisement is added describing the location of multicast\n destinations. A multicast packet's path is then calculated by\n building a pruned shortest-path tree rooted at the packet's IP\n so","scope_keywords":["1584","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1587","folder":"IETF/RFC-1587","source":"IETF/RFC-1587/RFC-1587.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1765","folder":"IETF/RFC-1765","source":"IETF/RFC-1765/RFC-1765.txt","version":null},{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 2715","folder":"IETF/RFC-2715","source":"IETF/RFC-2715/RFC-2715.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 1584 This memo documents enhancements to the OSPF protocol enabling the\n routing of IP multicast datagrams. In this proposal, an IP multicast\n packet is routed based both on the packet's source and its multicast\n destination (commonly referred to as source/destination routing). As\n it is routed, the multicast packet follows a shortest path to each\n multicast destination. During packet forwarding, any commonality of\n paths is exploited; when multiple hosts belong to a single multicast\n group, a multicast packet will be replicated only when the paths to\n the separate hosts diverge.\n\n OSPF, a link-state routing protocol, provides a database describing\n the Autonomous System's topology. A new OSPF link state\n advertisement is added describing the location of multicast\n destinations. A multicast packet's path is then calculated by\n building a pruned shortest-path tree rooted at the packet's IP\n so 1584 path nested-reference unchanged"},{"id":"IETF RFC 1623","type":"specification","body":"IETF","designation":"RFC 1623","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1623.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1623.txt","https://www.rfc-editor.org/rfc/rfc1623.pdf"],"folder":"IETF/RFC-1623","files":{"txt":{"path":"standards/IETF/RFC-1623/RFC-1623.txt","sha256":"71d0d1c3862ff2555b68f94516bc4b942bbf5991b957fb89b99227fea709297d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz\nRequest for Comments: 1623 FTP Software, Inc.\nObsoletes: 1398 May 1994\nSTD: 50\nCategory: Standards Track\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ............................................. 1\n 1. The SNMP Network Management Framework ................. 2\n 1.1 Object Definitions ................................... 2\n 2. Change Log ............................................ 2\n 3. Overview ...........................................","scope_keywords":["1623","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null}],"search_text":"IETF RFC 1623 Network Working Group F. Kastenholz\nRequest for Comments: 1623 FTP Software, Inc.\nObsoletes: 1398 May 1994\nSTD: 50\nCategory: Standards Track\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ............................................. 1\n 1. The SNMP Network Management Framework ................. 2\n 1.1 Object Definitions ................................... 2\n 2. Change Log ............................................ 2\n 3. Overview ........................................... 1623 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1643","type":"specification","body":"IETF","designation":"RFC 1643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1643.txt","https://www.rfc-editor.org/rfc/rfc1643.pdf"],"folder":"IETF/RFC-1643","files":{"txt":{"path":"standards/IETF/RFC-1643/RFC-1643.txt","sha256":"eeec3f78ecd439781377d949accd8583c72b546f1bbb80b79e4f135471a1f19e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz\nRequest for Comments: 1643 FTP Software, Inc.\nObsoletes: 1623, 1398 July 1994\nSTD: 50\nCategory: Standards Track\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ............................................. 1\n 1. The SNMP Network Management Framework ................. 2\n 1.1 Object Definitions ................................... 2\n 2. Change Log ............................................ 2\n 3. Overview ....................................","scope_keywords":["1643","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 1643 Network Working Group F. Kastenholz\nRequest for Comments: 1643 FTP Software, Inc.\nObsoletes: 1623, 1398 July 1994\nSTD: 50\nCategory: Standards Track\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ............................................. 1\n 1. The SNMP Network Management Framework ................. 2\n 1.1 Object Definitions ................................... 2\n 2. Change Log ............................................ 2\n 3. Overview .................................... 1643 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1650","type":"specification","body":"IETF","designation":"RFC 1650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1650.txt","https://www.rfc-editor.org/rfc/rfc1650.pdf"],"folder":"IETF/RFC-1650","files":{"txt":{"path":"standards/IETF/RFC-1650/RFC-1650.txt","sha256":"383f4e56559a5776c94432c7f42ad0bf91a60b430610eadee4034061ff42a9a0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz\nRequest for Comments: 1650 FTP Software, Inc.\nCategory: Standards Track August 1994\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. The SNMPv2 Network Management Framework ............... 2\n 2.1 Object Definitions ................................... 2\n 3. Change Log ............................................ 2\n 4. Overview .............................................. 3\n 4.","scope_keywords":["1650","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 1650 Network Working Group F. Kastenholz\nRequest for Comments: 1650 FTP Software, Inc.\nCategory: Standards Track August 1994\n\n Definitions of Managed Objects for\n the Ethernet-like Interface Types using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. The SNMPv2 Network Management Framework ............... 2\n 2.1 Object Definitions ................................... 2\n 3. Change Log ............................................ 2\n 4. Overview .............................................. 3\n 4. 1650 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1705","type":"specification","body":"IETF","designation":"RFC 1705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1705.txt","https://www.rfc-editor.org/rfc/rfc1705.pdf"],"folder":"IETF/RFC-1705","files":{"txt":{"path":"standards/IETF/RFC-1705/RFC-1705.txt","sha256":"209571ac3f713b6177e7571382d098414231abde9b30ade0857e4ec776583fdd"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview\n\n This RFC suggests that a new version of TCP (TCPng), and UDP, be\n developed and deployed. It proposes that a globally unique address\n (TA) be assigned to Transport layer protocol (TCP/UDP). The purpose\n of this TA is to uniquely identify an Internet node without\n specifying any routing information. A new version of TCP, and UDP,\n will need to be developed describing the new header fields and\n formats. This new version of TCP would contain support for high\n bandwidth-delay networks. Support for multiple network layer\n (Internet Protocol) protocols is also possible with this new TCP.\n Assigning an address to TCP/UDP would al","scope_keywords":["1705"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1705 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview\n\n This RFC suggests that a new version of TCP (TCPng), and UDP, be\n developed and deployed. It proposes that a globally unique address\n (TA) be assigned to Transport layer protocol (TCP/UDP). The purpose\n of this TA is to uniquely identify an Internet node without\n specifying any routing information. A new version of TCP, and UDP,\n will need to be developed describing the new header fields and\n formats. This new version of TCP would contain support for high\n bandwidth-delay networks. Support for multiple network layer\n (Internet Protocol) protocols is also possible with this new TCP.\n Assigning an address to TCP/UDP would al 1705 nested-reference unchanged"},{"id":"IETF RFC 1757","type":"specification","body":"IETF","designation":"RFC 1757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1757.txt","https://www.rfc-editor.org/rfc/rfc1757.pdf"],"folder":"IETF/RFC-1757","files":{"txt":{"path":"standards/IETF/RFC-1757/RFC-1757.txt","sha256":"f294a4f1d517c0412ce4dbd3c2dec11dd2984a524cb6ec3bd71b6f3565dbffb9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.","scope_keywords":["1757","attribute","attributes","authorization","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null}],"search_text":"IETF RFC 1757 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices. 1757 attribute attributes authorization management policy nested-reference unchanged"},{"id":"IETF RFC 2021","type":"specification","body":"IETF","designation":"RFC 2021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2021.txt","https://www.rfc-editor.org/rfc/rfc2021.pdf"],"folder":"IETF/RFC-2021","files":{"txt":{"path":"standards/IETF/RFC-2021/RFC-2021.txt","sha256":"b0717681f964aeb11326eb02e3608a1a64b2db2875e6e285107732ee6ed5bb88"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.","scope_keywords":["2021","authorization","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null}],"search_text":"IETF RFC 2021 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices. 2021 authorization management policy nested-reference unchanged"},{"id":"IETF RFC 2063","type":"specification","body":"IETF","designation":"RFC 2063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2063.txt","https://www.rfc-editor.org/rfc/rfc2063.pdf"],"folder":"IETF/RFC-2063","files":{"txt":{"path":"standards/IETF/RFC-2063/RFC-2063.txt","sha256":"6cbf681c8f4fd0a9ddbc87dad83f1d88afcd84877fe1981c175f4950719140bd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for the measurement and\n reporting of network traffic flows, discusses how this relates to an\n overall network traffic flow architecture, and describes how it can\n be used within the Internet. It is intended to provide a starting\n point for the Realtime Traffic Flow Measurement Working Group.","scope_keywords":["2063","attribute","attributes","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2123","folder":"IETF/RFC-2123","source":"IETF/RFC-2123/RFC-2123.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null}],"search_text":"IETF RFC 2063 This document describes an architecture for the measurement and\n reporting of network traffic flows, discusses how this relates to an\n overall network traffic flow architecture, and describes how it can\n be used within the Internet. It is intended to provide a starting\n point for the Realtime Traffic Flow Measurement Working Group. 2063 attribute attributes timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2239","type":"specification","body":"IETF","designation":"RFC 2239","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2239.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2239.txt","https://www.rfc-editor.org/rfc/rfc2239.pdf"],"folder":"IETF/RFC-2239","files":{"txt":{"path":"standards/IETF/RFC-2239/RFC-2239.txt","sha256":"84baf7358140ce2b46583ee9f484e6ec21db026b1850a3a7fa674034ba62e6a2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing 10 and 100 Mb/second\n Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,\n \"10 & 100 Mb/s Management,\" October 26, 1995.\n\n1. The SNMPv2 Network Management Framework\n\n The SNMPv2 Network Management Framework presently consists of three\n major components. They are:\n\n o the SMI, described in RFC 1902 [6] - the mechanisms used\n for describing and naming objects for the purpose of management.\n\n o the MIB-II, STD 17, RFC 1213 [5] - the core set of\n managed objects for the Internet suite of protocols.\n\n o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905 [9] -\n the protocol used for accessing managed information.\n\n Textual conventions are defined in RFC 1903 [7], and conformance\n statements ar","scope_keywords":["2239","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null}],"search_text":"IETF RFC 2239 This memo defines an portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing 10 and 100 Mb/second\n Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,\n \"10 & 100 Mb/s Management,\" October 26, 1995.\n\n1. The SNMPv2 Network Management Framework\n\n The SNMPv2 Network Management Framework presently consists of three\n major components. They are:\n\n o the SMI, described in RFC 1902 [6] - the mechanisms used\n for describing and naming objects for the purpose of management.\n\n o the MIB-II, STD 17, RFC 1213 [5] - the core set of\n managed objects for the Internet suite of protocols.\n\n o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905 [9] -\n the protocol used for accessing managed information.\n\n Textual conventions are defined in RFC 1903 [7], and conformance\n statements ar 2239 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 2358","type":"specification","body":"IETF","designation":"RFC 2358","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2358.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2358.txt","https://www.rfc-editor.org/rfc/rfc2358.pdf"],"folder":"IETF/RFC-2358","files":{"txt":{"path":"standards/IETF/RFC-2358/RFC-2358.txt","sha256":"e8f23d4349e566fb950f55edffe70db26d1b57fbc0282fa9f0d88ac2b34b2b4e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1650 \"Definitions of Managed Objects for the\n Ethernet-like Interface Types using SMIv2\". This memo extends that\n specification by including management information useful for the\n management of 100 Mb/s Ethernet interfaces.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflect a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n or new documents might be issued by th","scope_keywords":["2358","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 2358 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1650 \"Definitions of Managed Objects for the\n Ethernet-like Interface Types using SMIv2\". This memo extends that\n specification by including management information useful for the\n management of 100 Mb/s Ethernet interfaces.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflect a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n or new documents might be issued by th 2358 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 2666","type":"specification","body":"IETF","designation":"RFC 2666","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2666.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2666.txt","https://www.rfc-editor.org/rfc/rfc2666.pdf"],"folder":"IETF/RFC-2666","files":{"txt":{"path":"standards/IETF/RFC-2666/RFC-2666.txt","sha256":"5bd60dd5a49a9fa423fe2df3852e265d9896b44af2281ae4ec271887ad61f7ac"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines OBJECT IDENTIFIER values for use with network\n management protocols in the Internet community. In particular, it\n contains registered OID values for use with the dot3StatsEtherChipSet\n object in the EtherLike-MIB [16]. These registrations have been\n split from [16] into a separate document for maintenance purposes.","scope_keywords":["2666","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"IETF RFC 2666 This memo defines OBJECT IDENTIFIER values for use with network\n management protocols in the Internet community. In particular, it\n contains registered OID values for use with the dot3StatsEtherChipSet\n object in the EtherLike-MIB [16]. These registrations have been\n split from [16] into a separate document for maintenance purposes. 2666 management registered nested-reference unchanged"},{"id":"IETF RFC 2668","type":"specification","body":"IETF","designation":"RFC 2668","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2668.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2668.txt","https://www.rfc-editor.org/rfc/rfc2668.pdf"],"folder":"IETF/RFC-2668","files":{"txt":{"path":"standards/IETF/RFC-2668/RFC-2668.txt","sha256":"cf6904fe8f296d84c58148fb19ec5e5644e7e2cbcfe8c6cc3a7b5835f0fe1feb"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 2239, \"Definitions of Managed Objects for\n IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2\". This memo\n extends that specification by including management information useful\n for the management of 1000 Mb/s MAUs.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflects a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n\nSmith, et al. Standards Track [Page 1]\n\f\nR","scope_keywords":["2668","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null}],"search_text":"IETF RFC 2668 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 2239, \"Definitions of Managed Objects for\n IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2\". This memo\n extends that specification by including management information useful\n for the management of 1000 Mb/s MAUs.\n\n Ethernet technology, as defined by the 802.3 Working Group of the\n IEEE, continues to evolve, with scalable increases in speed, new\n types of cabling and interfaces, and new features. This evolution\n may require changes in the managed objects in order to reflect this\n new functionality. This document, as with other documents issued by\n this working group, reflects a certain stage in the evolution of\n Ethernet technology. In the future, this document might be revised,\n\nSmith, et al. Standards Track [Page 1]\n\f\nR 2668 key management nested-reference unchanged"},{"id":"IETF RFC 2722","type":"specification","body":"IETF","designation":"RFC 2722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2722.txt","https://www.rfc-editor.org/rfc/rfc2722.pdf"],"folder":"IETF/RFC-2722","files":{"txt":{"path":"standards/IETF/RFC-2722/RFC-2722.txt","sha256":"520a6df704c965b7540b5379ca47b92f4a7c33b02d5a084c2cd61e8e0d38ecbe"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a general framework for describing network\n traffic flows, presents an architecture for traffic flow measurement\n and reporting, discusses how this relates to an overall network\n traffic flow architecture and indicates how it can be used within the\n Internet.","scope_keywords":["2722","attribute","attributes","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2723","folder":"IETF/RFC-2723","source":"IETF/RFC-2723/RFC-2723.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null}],"search_text":"IETF RFC 2722 This document provides a general framework for describing network\n traffic flows, presents an architecture for traffic flow measurement\n and reporting, discusses how this relates to an overall network\n traffic flow architecture and indicates how it can be used within the\n Internet. 2722 attribute attributes timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2737","type":"specification","body":"IETF","designation":"RFC 2737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2737.txt","https://www.rfc-editor.org/rfc/rfc2737.pdf"],"folder":"IETF/RFC-2737","files":{"txt":{"path":"standards/IETF/RFC-2737/RFC-2737.txt","sha256":"438a42224e93b1d1af3c494253f2b2ed15d602e1179446e3e2302b4c32a275e5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single SNMP\n agent.","scope_keywords":["2737","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 2737 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single SNMP\n agent. 2737 management nested-reference unchanged"},{"id":"IETF RFC 2819","type":"specification","body":"IETF","designation":"RFC 2819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2819.txt","https://www.rfc-editor.org/rfc/rfc2819.pdf"],"folder":"IETF/RFC-2819","files":{"txt":{"path":"standards/IETF/RFC-2819/RFC-2819.txt","sha256":"d930bc98c81a62d28e55c9dade724289b4c3d320e564c1cbcae9c7fef780f57d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.\n\n This memo obsoletes RFC 1757. This memo extends that specification by\n documenting the RMON MIB in SMIv2 format while remaining semantically\n identical to the existing SMIv1-based MIB.\n\nWaldbusser Standards Track [Page 1]\n\f\nRFC 2819 Remote Network Monitoring MIB May 2000","scope_keywords":["2819","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2819 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.\n\n This memo obsoletes RFC 1757. This memo extends that specification by\n documenting the RMON MIB in SMIv2 format while remaining semantically\n identical to the existing SMIv1-based MIB.\n\nWaldbusser Standards Track [Page 1]\n\f\nRFC 2819 Remote Network Monitoring MIB May 2000 2819 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 2889","type":"specification","body":"IETF","designation":"RFC 2889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2889.txt","https://www.rfc-editor.org/rfc/rfc2889.pdf"],"folder":"IETF/RFC-2889","files":{"txt":{"path":"standards/IETF/RFC-2889/RFC-2889.txt","sha256":"e3ada0688c8d222257d1929b2f799b23a1f0f4960fb5c242253ee9e307e2f546"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Mandeville\nRequest for Comments: 2889 CQOS Inc.\nCategory: Informational J. Perser\n Spirent Communications\n August 2000\n\n Benchmarking Methodology for LAN Switching Devices\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 3. Test setup . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 4. Frame formats and sizes . . . . . . . . . . . . . . . . . . . 3\n 5. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . . 3\n 5.1 Fully meshed throughput, frame loss and forwarding rates 4\n 5.2 Partiall","scope_keywords":["2889","algorithm","hash","hashing","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null}],"search_text":"IETF RFC 2889 Network Working Group R. Mandeville\nRequest for Comments: 2889 CQOS Inc.\nCategory: Informational J. Perser\n Spirent Communications\n August 2000\n\n Benchmarking Methodology for LAN Switching Devices\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 3. Test setup . . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 4. Frame formats and sizes . . . . . . . . . . . . . . . . . . . 3\n 5. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . . 3\n 5.1 Fully meshed throughput, frame loss and forwarding rates 4\n 5.2 Partiall 2889 algorithm hash hashing key signature nested-reference unchanged"},{"id":"IETF RFC 3273","type":"specification","body":"IETF","designation":"RFC 3273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3273.txt","https://www.rfc-editor.org/rfc/rfc3273.pdf"],"folder":"IETF/RFC-3273","files":{"txt":{"path":"standards/IETF/RFC-3273/RFC-3273.txt","sha256":"864254faeaed047676ad49841a2cc0964ae50deba9b08a3b2fcc52eaeee18660"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring (RMON) devices for use on high speed networks. This\n document contains a MIB Module that defines these new objects and\n also contains definitions of some updated objects from the RMON-MIB\n in RFC 2819 and the RMON2-MIB in RFC 2021.","scope_keywords":["3273","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null}],"search_text":"IETF RFC 3273 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring (RMON) devices for use on high speed networks. This\n document contains a MIB Module that defines these new objects and\n also contains definitions of some updated objects from the RMON-MIB\n in RFC 2819 and the RMON2-MIB in RFC 2021. 3273 management nested-reference unchanged"},{"id":"IETF RFC 3636","type":"specification","body":"IETF","designation":"RFC 3636","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3636.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3636.txt","https://www.rfc-editor.org/rfc/rfc3636.pdf"],"folder":"IETF/RFC-3636","files":{"txt":{"path":"standards/IETF/RFC-3636/RFC-3636.txt","sha256":"8a91ab39d2e1057ce96e83fbb87306f95f89e03fe02abab7b77b9db59108a4fe"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 Medium\n Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo\n extends that specification by including management information useful\n for the management of 10 gigabit per second (Gb/s) MAUs. This memo\n also obsoletes RFC 1515.\n\nFlick Standards Track [Page 1]\n\f\nRFC 3636 802.3 MAU MIB September 2003","scope_keywords":["3636","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 3636 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing IEEE 802.3 Medium\n Attachment Units (MAUs). This memo obsoletes RFC 2668. This memo\n extends that specification by including management information useful\n for the management of 10 gigabit per second (Gb/s) MAUs. This memo\n also obsoletes RFC 1515.\n\nFlick Standards Track [Page 1]\n\f\nRFC 3636 802.3 MAU MIB September 2003 3636 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 3637","type":"specification","body":"IETF","designation":"RFC 3637","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3637.txt","https://www.rfc-editor.org/rfc/rfc3637.pdf"],"folder":"IETF/RFC-3637","files":{"txt":{"path":"standards/IETF/RFC-3637/RFC-3637.txt","sha256":"9896864c197ff4de884335ca15e3146e93f841b7450a7c7c2a95db0b47a35609"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP based\n internets. In particular, it defines objects for managing the\n Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).\n\n The MIB module defined in this memo is an extension of the\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Interface MIB and is implemented in conjunction with it and with the\n Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB,\n the Interfaces Group MIB, and the Inverted Stack Table MIB.","scope_keywords":["3637","attribute","attributes","key","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null}],"search_text":"IETF RFC 3637 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP based\n internets. In particular, it defines objects for managing the\n Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).\n\n The MIB module defined in this memo is an extension of the\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Interface MIB and is implemented in conjunction with it and with the\n Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB,\n the Interfaces Group MIB, and the Inverted Stack Table MIB. 3637 attribute attributes key management path presentation nested-reference unchanged"},{"id":"IETF RFC 4133","type":"specification","body":"IETF","designation":"RFC 4133","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4133.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4133.txt","https://www.rfc-editor.org/rfc/rfc4133.pdf"],"folder":"IETF/RFC-4133","files":{"txt":{"path":"standards/IETF/RFC-4133/RFC-4133.txt","sha256":"95e098fb64acf404a8124364e18b518810f3a6936367569cd69da186396daf28"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single SNMP\n agent. This document specifies version 3 of the Entity MIB, which\n obsoletes version 2 (RFC 2737).\n\nBierman & McCloghrie Standards Track [Page 1]\n\f\nRFC 4133 Entity MIB (Version 3) August 2005","scope_keywords":["4133","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 4133 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single SNMP\n agent. This document specifies version 3 of the Entity MIB, which\n obsoletes version 2 (RFC 2737).\n\nBierman & McCloghrie Standards Track [Page 1]\n\f\nRFC 4133 Entity MIB (Version 3) August 2005 4133 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 4181","type":"specification","body":"IETF","designation":"RFC 4181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4181.txt","https://www.rfc-editor.org/rfc/rfc4181.pdf"],"folder":"IETF/RFC-4181","files":{"txt":{"path":"standards/IETF/RFC-4181/RFC-4181.txt","sha256":"32909db7005f2f697e0e8b6b5afbe1ebc0591fa3faed28b19bf6335dc376541d"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides guidelines for authors and reviewers of IETF\n standards-track specifications containing MIB modules. Applicable\n portions may be used as a basis for reviews of other MIB documents.","scope_keywords":["4181","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 4181 This memo provides guidelines for authors and reviewers of IETF\n standards-track specifications containing MIB modules. Applicable\n portions may be used as a basis for reviews of other MIB documents. 4181 key policy nested-reference unchanged"},{"id":"IETF RFC 4502","type":"specification","body":"IETF","designation":"RFC 4502","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4502.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4502.txt","https://www.rfc-editor.org/rfc/rfc4502.pdf"],"folder":"IETF/RFC-4502","files":{"txt":{"path":"standards/IETF/RFC-4502/RFC-4502.txt","sha256":"c4fe41cc1e8a63ee448e6e2263d54ffcd1a607bba2f9f2714f201f66e79cdaf5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing remote\n network monitoring devices.\n\n This document obsoletes RFC 2021, updates RFC 3273, and contains a\n new version of the RMON2-MIB module.\n\nWaldbusser Standards Track [Page 1]\n\f\nRFC 4502 Remote Network Monitoring MIB May 2006","scope_keywords":["4502","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 4502 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing remote\n network monitoring devices.\n\n This document obsoletes RFC 2021, updates RFC 3273, and contains a\n new version of the RMON2-MIB module.\n\nWaldbusser Standards Track [Page 1]\n\f\nRFC 4502 Remote Network Monitoring MIB May 2006 4502 management nested-reference unchanged"},{"id":"IETF RFC 5163","type":"specification","body":"IETF","designation":"RFC 5163","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5163.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5163.txt","https://www.rfc-editor.org/rfc/rfc5163.pdf"],"folder":"IETF/RFC-5163","files":{"txt":{"path":"standards/IETF/RFC-5163/RFC-5163.txt","sha256":"06fef1c95c8a4c93f7c3138a0201d3aec402d98dc071fff836974061596e0f2c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of Extension Headers for the\n Unidirectional Lightweight Encapsulation (ULE), RFC 4326.\n\n The Extension Header formats specified in this document define\n extensions appropriate to both ULE and the Generic Stream\n Encapsulation (GSE) for the second-generation framing structure\n defined by the Digital Video Broadcasting (DVB) family of\n specifications.","scope_keywords":["5163","key","pid","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 5163 This document describes a set of Extension Headers for the\n Unidirectional Lightweight Encapsulation (ULE), RFC 4326.\n\n The Extension Header formats specified in this document define\n extensions appropriate to both ULE and the Generic Stream\n Encapsulation (GSE) for the second-generation framing structure\n defined by the Digital Video Broadcasting (DVB) family of\n specifications. 5163 key pid timestamp nested-reference unchanged"},{"id":"IETF RFC 5982","type":"specification","body":"IETF","designation":"RFC 5982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5982.txt","https://www.rfc-editor.org/rfc/rfc5982.pdf"],"folder":"IETF/RFC-5982","files":{"txt":{"path":"standards/IETF/RFC-5982/RFC-5982.txt","sha256":"56d78ea409cc302cbaaf3e2c779b8781fc20b217629f650848d1e4fd9e4de5d3"}},"tags":["nested-reference","unchanged"],"summary":"Flow-based measurement is a popular method for various network\n monitoring usages. The sharing of flow-based information for\n monitoring applications having different requirements raises some\n open issues in terms of measurement system scalability, flow-based\n measurement flexibility, and export reliability that IP Flow\n Information Export (IPFIX) Mediation may help resolve. This document\n describes some problems related to flow-based measurement that\n network administrators have been facing, and then it describes IPFIX\n Mediation applicability examples along with the problems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo","scope_keywords":["5982","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 5982 Flow-based measurement is a popular method for various network\n monitoring usages. The sharing of flow-based information for\n monitoring applications having different requirements raises some\n open issues in terms of measurement system scalability, flow-based\n measurement flexibility, and export reliability that IP Flow\n Information Export (IPFIX) Mediation may help resolve. This document\n describes some problems related to flow-based measurement that\n network administrators have been facing, and then it describes IPFIX\n Mediation applicability examples along with the problems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo 5982 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6933","type":"specification","body":"IETF","designation":"RFC 6933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6933.txt","https://www.rfc-editor.org/rfc/rfc6933.pdf"],"folder":"IETF/RFC-6933","files":{"txt":{"path":"standards/IETF/RFC-6933/RFC-6933.txt","sha256":"abc183a1bc88af1e9aaeecbfb4a265b2b1f368bfe3d477ca6a117628cd7013fd"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single Simple\n Network Management Protocol (SNMP) agent. This document specifies\n version 4 of the Entity MIB. This memo obsoletes version 3 of the\n Entity MIB module published as RFC 4133.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document","scope_keywords":["6933","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null}],"search_text":"IETF RFC 6933 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n multiple logical and physical entities managed by a single Simple\n Network Management Protocol (SNMP) agent. This document specifies\n version 4 of the Entity MIB. This memo obsoletes version 3 of the\n Entity MIB module published as RFC 4133.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document 6933 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7087","type":"specification","body":"IETF","designation":"RFC 7087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7087.txt","https://www.rfc-editor.org/rfc/rfc7087.pdf"],"folder":"IETF/RFC-7087","files":{"txt":{"path":"standards/IETF/RFC-7087/RFC-7087.txt","sha256":"d24ade1672eeb46b347902417777be5721a3a9f682d1d309fe674afa57facf65"}},"tags":["nested-reference","unchanged"],"summary":"The MPLS Transport Profile (MPLS-TP) is based on a profile of the\n MPLS and Pseudowire (PW) procedures as specified in the MPLS Traffic\n Engineering (MPLS-TE), PW, and Multi-Segment Pseudowire (MS-PW)\n architectures developed by the Internet Engineering Task Force\n (IETF). The International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) has specified a Transport Network\n architecture.\n\n This document provides a thesaurus for the interpretation of MPLS-TP\n terminology within the context of the ITU-T Transport Network\n Recommendations.\n\n It is important to note that MPLS-TP is applicable in a wider set of\n contexts than just Transport Networks. The definitions presented in\n this document do not provide exclusive or complete interpretations of\n MPLS-TP concepts. This document simply allows the MPLS-TP terms to\n be applied within the Transport Network context.\n\nSta","scope_keywords":["7087","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 7087 The MPLS Transport Profile (MPLS-TP) is based on a profile of the\n MPLS and Pseudowire (PW) procedures as specified in the MPLS Traffic\n Engineering (MPLS-TE), PW, and Multi-Segment Pseudowire (MS-PW)\n architectures developed by the Internet Engineering Task Force\n (IETF). The International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) has specified a Transport Network\n architecture.\n\n This document provides a thesaurus for the interpretation of MPLS-TP\n terminology within the context of the ITU-T Transport Network\n Recommendations.\n\n It is important to note that MPLS-TP is applicable in a wider set of\n contexts than just Transport Networks. The definitions presented in\n this document do not provide exclusive or complete interpretations of\n MPLS-TP concepts. This document simply allows the MPLS-TP terms to\n be applied within the Transport Network context.\n\nSta 7087 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 961","type":"specification","body":"IETF","designation":"RFC 961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc961.txt","https://www.rfc-editor.org/rfc/rfc961.pdf"],"folder":"IETF/RFC-961","files":{"txt":{"path":"standards/IETF/RFC-961/RFC-961.txt","sha256":"ca1faa53e8f1a8fe18a0c9ae8e567f884d7406c4fbd95985561df233c709de59"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 961 J. Postel\n ISI\nObsoletes: RFCs 944, 924, 901, 880, 840 December 1985\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been ","scope_keywords":["961","algorithm","algorithms","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null}],"search_text":"IETF RFC 961 Network Working Group J. Reynolds\nRequest for Comments: 961 J. Postel\n ISI\nObsoletes: RFCs 944, 924, 901, 880, 840 December 1985\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been  961 algorithm algorithms subject nested-reference unchanged"},{"id":"IETF RFC 980","type":"specification","body":"IETF","designation":"RFC 980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc980.txt","https://www.rfc-editor.org/rfc/rfc980.pdf"],"folder":"IETF/RFC-980","files":{"txt":{"path":"standards/IETF/RFC-980/RFC-980.txt","sha256":"a9b32c92eeb6b435ddd1f463283022473625d4ad05e8e3bea4866c23142bf9e3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ole Jacobsen (SRI)\nRequest for Comments: 980 Jon Postel (ISI)\n March 1986\n\n Protocol Document Order Information\n\nSTATUS OF THIS MEMO\n\n This RFC indicates how to obtain various protocol documents used in\n the DARPA research community. Included is an overview of the new\n 1985 DDN Protocol Handbook and available sources for obtaining\n related documents (such as, DoD, ISO, and CCITT). Distribution of\n this memo is unlimited.\n\nDOD INTERNET PROTOCOL DOCUMENTS:\n\n How to get the Requests for Comments (RFCs):\n\n RFCs are the working memos of the DARPA research community. The\n subjects may include protocol specifications, interface\n definitions, program descriptions, policy statements, trouble\n reports, algorithms, announcements, and humor. These may range\n from wild ideas and crazy suggestions, to firm specifications.\n\n The normal method for distribution of RFCs is for intere","scope_keywords":["980","algorithm","algorithms","path","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 980 Network Working Group Ole Jacobsen (SRI)\nRequest for Comments: 980 Jon Postel (ISI)\n March 1986\n\n Protocol Document Order Information\n\nSTATUS OF THIS MEMO\n\n This RFC indicates how to obtain various protocol documents used in\n the DARPA research community. Included is an overview of the new\n 1985 DDN Protocol Handbook and available sources for obtaining\n related documents (such as, DoD, ISO, and CCITT). Distribution of\n this memo is unlimited.\n\nDOD INTERNET PROTOCOL DOCUMENTS:\n\n How to get the Requests for Comments (RFCs):\n\n RFCs are the working memos of the DARPA research community. The\n subjects may include protocol specifications, interface\n definitions, program descriptions, policy statements, trouble\n reports, algorithms, announcements, and humor. These may range\n from wild ideas and crazy suggestions, to firm specifications.\n\n The normal method for distribution of RFCs is for intere 980 algorithm algorithms path policy subject nested-reference unchanged"},{"id":"IEEE IEEE 802.3-","type":"specification","body":"IEEE","designation":"IEEE 802.3-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-.html","download_urls":["https://standards.ieee.org/standard/802.3-.html"],"folder":"IEEE/IEEE-802.3-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null}],"search_text":"IEEE IEEE 802.3- nested-reference unavailable"},{"id":"IEEE IEEE 802.3-1985","type":"specification","body":"IEEE","designation":"IEEE 802.3-1985","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-1985.html","download_urls":["https://standards.ieee.org/standard/802.3-1985.html"],"folder":"IEEE/IEEE-802.3-1985","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1020","folder":"IETF/RFC-1020","source":"IETF/RFC-1020/RFC-1020.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null}],"search_text":"IEEE IEEE 802.3-1985 nested-reference unavailable"},{"id":"IETF RFC 1020","type":"specification","body":"IETF","designation":"RFC 1020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1020.txt","https://www.rfc-editor.org/rfc/rfc1020.pdf"],"folder":"IETF/RFC-1020","files":{"txt":{"path":"standards/IETF/RFC-1020/RFC-1020.txt","sha256":"9ce2e59c63cb71e6771ab9fb8e74d8fd75a5ec875b863dcdbfb928efc7177964"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Romano\nRequest for Comments: 1020 M. Stahl\nObsoletes RFCs: 997, 990, 960, 943, SRI\n923, 900, 870, 820, 790, 776, 770, 762, November 1987\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the network numbers used in\n the Internet community. Distribution of this memo is unlimited.\n\nIntroduction\n\n The responsibility for the assignment of IP numbers and ASNs has been\n assumed by Hostmaster at the DDN Network Information Center (NIC).\n The Hostmaster staff are indebted to Dr. Jon Postel and Ms. Joyce\n Reynolds of the Information Sciences Institute at the University of\n Southern California for their ongoing assistance.\n\n This Network Working Group Request for Comments documents the\n currently assigned network numbers and gateway autonomous systems.\n This RFC will be up","scope_keywords":["1020","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null}],"search_text":"IETF RFC 1020 Network Working Group S. Romano\nRequest for Comments: 1020 M. Stahl\nObsoletes RFCs: 997, 990, 960, 943, SRI\n923, 900, 870, 820, 790, 776, 770, 762, November 1987\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the network numbers used in\n the Internet community. Distribution of this memo is unlimited.\n\nIntroduction\n\n The responsibility for the assignment of IP numbers and ASNs has been\n assumed by Hostmaster at the DDN Network Information Center (NIC).\n The Hostmaster staff are indebted to Dr. Jon Postel and Ms. Joyce\n Reynolds of the Information Sciences Institute at the University of\n Southern California for their ongoing assistance.\n\n This Network Working Group Request for Comments documents the\n currently assigned network numbers and gateway autonomous systems.\n This RFC will be up 1020 registered nested-reference unchanged"},{"id":"IETF RFC 1166","type":"specification","body":"IETF","designation":"RFC 1166","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1166.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1166.txt","https://www.rfc-editor.org/rfc/rfc1166.pdf"],"folder":"IETF/RFC-1166","files":{"txt":{"path":"standards/IETF/RFC-1166/RFC-1166.txt","sha256":"fc98e6492e4721aad512f7d7dd911d838b0e02a0e052c6d6c44fe7ac76d02aab"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kirkpatrick\nRequest for Comments: 1166 M. Stahl\nObsoletes RFCs: 1117, 1020, 997, 990, 960, 943, M. Recker\n943, 923, 900, 870, 820, 790, 776, 770, 762, July 1990\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the network numbers and autonomous\n system numbers used in the Internet community. Distribution of this\n memo is unlimited.\n\nTable of Contents\n\n Introduction.................................................... 1\n Network Numbers................................................. 4\n Class A Networks................................................ 7\n Class B Networks................................................ 8\n Class C Networks................................................ 47\n Other Reserved Internet Addresses............................... 100\n Network Totals..","scope_keywords":["1166","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 1166 Network Working Group S. Kirkpatrick\nRequest for Comments: 1166 M. Stahl\nObsoletes RFCs: 1117, 1020, 997, 990, 960, 943, M. Recker\n943, 923, 900, 870, 820, 790, 776, 770, 762, July 1990\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nStatus of this Memo\n\n This memo is a status report on the network numbers and autonomous\n system numbers used in the Internet community. Distribution of this\n memo is unlimited.\n\nTable of Contents\n\n Introduction.................................................... 1\n Network Numbers................................................. 4\n Class A Networks................................................ 7\n Class B Networks................................................ 8\n Class C Networks................................................ 47\n Other Reserved Internet Addresses............................... 100\n Network Totals.. 1166 registered nested-reference unchanged"},{"id":"IEEE IEEE 802.3-1985.","type":"specification","body":"IEEE","designation":"IEEE 802.3-1985.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-1985..html","download_urls":["https://standards.ieee.org/standard/802.3-1985..html"],"folder":"IEEE/IEEE-802.3-1985.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null}],"search_text":"IEEE IEEE 802.3-1985. nested-reference unavailable"},{"id":"IEEE IEEE 802.3-1996","type":"specification","body":"IEEE","designation":"IEEE 802.3-1996","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-1996.html","download_urls":["https://standards.ieee.org/standard/802.3-1996.html"],"folder":"IEEE/IEEE-802.3-1996","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null}],"search_text":"IEEE IEEE 802.3-1996 nested-reference unavailable"},{"id":"IEEE IEEE 802.3-2002","type":"specification","body":"IEEE","designation":"IEEE 802.3-2002","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-2002.html","download_urls":["https://standards.ieee.org/standard/802.3-2002.html"],"folder":"IEEE/IEEE-802.3-2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null}],"search_text":"IEEE IEEE 802.3-2002 nested-reference unavailable"},{"id":"IEEE IEEE 802.3-2005","type":"specification","body":"IEEE","designation":"IEEE 802.3-2005","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-2005.html","download_urls":["https://standards.ieee.org/standard/802.3-2005.html"],"folder":"IEEE/IEEE-802.3-2005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null}],"search_text":"IEEE IEEE 802.3-2005 nested-reference unavailable"},{"id":"IEEE IEEE 802.3-2008","type":"specification","body":"IEEE","designation":"IEEE 802.3-2008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-2008.html","download_urls":["https://standards.ieee.org/standard/802.3-2008.html"],"folder":"IEEE/IEEE-802.3-2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null}],"search_text":"IEEE IEEE 802.3-2008 nested-reference unavailable"},{"id":"IETF RFC 6291","type":"specification","body":"IETF","designation":"RFC 6291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6291.txt","https://www.rfc-editor.org/rfc/rfc6291.pdf"],"folder":"IETF/RFC-6291","files":{"txt":{"path":"standards/IETF/RFC-6291/RFC-6291.txt","sha256":"31936e54acca022ea7068bfd464c8d65bc822ab21f42e16b716f7750088bfba2"}},"tags":["nested-reference","unchanged"],"summary":"At first glance, the acronym \"OAM\" seems to be well-known and well-\n understood. Looking at the acronym a bit more closely reveals a set\n of recurring problems that are revisited time and again.\n\n This document provides a definition of the acronym \"OAM\" (Operations,\n Administration, and Maintenance) for use in all future IETF documents\n that refer to OAM. There are other definitions and acronyms that\n will be discussed while exploring the definition of the constituent\n parts of the \"OAM\" term.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Info","scope_keywords":["6291","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7319","folder":"IETF/RFC-7319","source":"IETF/RFC-7319/RFC-7319.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null}],"search_text":"IETF RFC 6291 At first glance, the acronym \"OAM\" seems to be well-known and well-\n understood. Looking at the acronym a bit more closely reveals a set\n of recurring problems that are revisited time and again.\n\n This document provides a definition of the acronym \"OAM\" (Operations,\n Administration, and Maintenance) for use in all future IETF documents\n that refer to OAM. There are other definitions and acronyms that\n will be discussed while exploring the definition of the constituent\n parts of the \"OAM\" term.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Info 6291 http key license management subject trust nested-reference unchanged"},{"id":"IEEE IEEE 802.3-2012","type":"specification","body":"IEEE","designation":"IEEE 802.3-2012","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-2012.html","download_urls":["https://standards.ieee.org/standard/802.3-2012.html"],"folder":"IEEE/IEEE-802.3-2012","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IEEE IEEE 802.3-2012 nested-reference unavailable"},{"id":"IEEE IEEE 802.3-2015.","type":"specification","body":"IEEE","designation":"IEEE 802.3-2015.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3-2015..html","download_urls":["https://standards.ieee.org/standard/802.3-2015..html"],"folder":"IEEE/IEEE-802.3-2015.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IEEE IEEE 802.3-2015. nested-reference unavailable"},{"id":"IEEE IEEE 802.3.","type":"specification","body":"IEEE","designation":"IEEE 802.3.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.3..html","download_urls":["https://standards.ieee.org/standard/802.3..html"],"folder":"IEEE/IEEE-802.3.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IEEE IEEE 802.3. nested-reference unavailable"},{"id":"IEEE IEEE 802.4","type":"specification","body":"IEEE","designation":"IEEE 802.4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.4.html","download_urls":["https://standards.ieee.org/standard/802.4.html"],"folder":"IEEE/IEEE-802.4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1028","folder":"IETF/RFC-1028","source":"IETF/RFC-1028/RFC-1028.txt","version":null},{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1250","folder":"IETF/RFC-1250","source":"IETF/RFC-1250/RFC-1250.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null}],"search_text":"IEEE IEEE 802.4 nested-reference unavailable"},{"id":"IETF RFC 1239","type":"specification","body":"IETF","designation":"RFC 1239","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1239.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1239.txt","https://www.rfc-editor.org/rfc/rfc1239.pdf"],"folder":"IETF/RFC-1239","files":{"txt":{"path":"standards/IETF/RFC-1239/RFC-1239.txt","sha256":"7a22bb22ab75a5790c8458a25aed7d54327d197a14564a43f06fba884cc7278a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1239 ISI\nUpdates: RFCs 1229, 1230, 1231, 1232, 1233 June 1991\n\n Reassignment of Experimental MIBs to Standard MIBs\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nStatement\n\n In the past, MIBs have been assigned arcs in the experimental MIB\n namespace early in their development and then were not assigned arcs\n in the standard MIB namespace until they reached Full Standard\n status. This practice required vendors to revise their\n implementations when a MIB went from Draft to Full Standard status,\n even though there was probably no substantive tech","scope_keywords":["1239","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1239 Network Working Group J. Reynolds\nRequest for Comments: 1239 ISI\nUpdates: RFCs 1229, 1230, 1231, 1232, 1233 June 1991\n\n Reassignment of Experimental MIBs to Standard MIBs\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nStatement\n\n In the past, MIBs have been assigned arcs in the experimental MIB\n namespace early in their development and then were not assigned arcs\n in the standard MIB namespace until they reached Full Standard\n status. This practice required vendors to revise their\n implementations when a MIB went from Draft to Full Standard status,\n even though there was probably no substantive tech 1239 management nested-reference unchanged"},{"id":"IETF RFC 1716","type":"specification","body":"IETF","designation":"RFC 1716","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1716.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1716.txt","https://www.rfc-editor.org/rfc/rfc1716.pdf"],"folder":"IETF/RFC-1716","files":{"txt":{"path":"standards/IETF/RFC-1716/RFC-1716.txt","sha256":"2538ddfcc88cfe3361ffd305bcc2b76cf256e12792daa95cdbfa8e726a9a0543"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Almquist, Author\nRequest for Comments: 1716 Consultant\nCategory: Informational F. Kastenholz, Editor\n FTP Software, Inc.\n November 1994\n\n Towards Requirements for IP Routers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAlmquist & Kastenholz [Page i]\n\f\nRFC 1716 Towards Requirements for IP Routers November 1994\n\nTable of Contents\n\n0. PREFACE ....................................................... 1\n1. INTRODUCTION .................................................. 2\n1.1 Reading this Document ........................................ 4\n1.1.1 Organization ............................................... 4\n1.1.2 Requirements ............................................... 5\n1.1.3 Compliance .........................................","scope_keywords":["1716","algorithm","algorithms","delivery","management","path","timestamp","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1716 Network Working Group P. Almquist, Author\nRequest for Comments: 1716 Consultant\nCategory: Informational F. Kastenholz, Editor\n FTP Software, Inc.\n November 1994\n\n Towards Requirements for IP Routers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAlmquist & Kastenholz [Page i]\n\f\nRFC 1716 Towards Requirements for IP Routers November 1994\n\nTable of Contents\n\n0. PREFACE ....................................................... 1\n1. INTRODUCTION .................................................. 2\n1.1 Reading this Document ........................................ 4\n1.1.1 Organization ............................................... 4\n1.1.2 Requirements ............................................... 5\n1.1.3 Compliance ......................................... 1716 algorithm algorithms delivery management path timestamp validation nested-reference unchanged"},{"id":"IETF RFC 1812","type":"specification","body":"IETF","designation":"RFC 1812","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1812.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1812.txt","https://www.rfc-editor.org/rfc/rfc1812.pdf"],"folder":"IETF/RFC-1812","files":{"txt":{"path":"standards/IETF/RFC-1812/RFC-1812.txt","sha256":"72c2c27fecd3eef085f978a8c0ee5f364877708bfc0251af1c8437b56ad2f56d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Baker, Editor\nRequest for Comments: 1812 Cisco Systems\nObsoletes: 1716, 1009 June 1995\nCategory: Standards Track\n\n Requirements for IP Version 4 Routers\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nPREFACE\n\n This document is an updated version of RFC 1716, the historical\n Router Requirements document. That RFC preserved the significant\n work that went into the working group, but failed to adequately\n describe current technology for the IESG to consider it a current\n standard.\n\n The current editor had been asked to bring the document up to date,\n so t","scope_keywords":["1812","algorithm","algorithms","management","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1878","folder":"IETF/RFC-1878","source":"IETF/RFC-1878/RFC-1878.txt","version":null},{"body":"IETF","designation":"RFC 1879","folder":"IETF/RFC-1879","source":"IETF/RFC-1879/RFC-1879.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2075","folder":"IETF/RFC-2075","source":"IETF/RFC-2075/RFC-2075.txt","version":null},{"body":"IETF","designation":"RFC 2267","folder":"IETF/RFC-2267","source":"IETF/RFC-2267/RFC-2267.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2453","folder":"IETF/RFC-2453","source":"IETF/RFC-2453/RFC-2453.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2644","folder":"IETF/RFC-2644","source":"IETF/RFC-2644/RFC-2644.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2678","folder":"IETF/RFC-2678","source":"IETF/RFC-2678/RFC-2678.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2827","folder":"IETF/RFC-2827","source":"IETF/RFC-2827/RFC-2827.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3626","folder":"IETF/RFC-3626","source":"IETF/RFC-3626/RFC-3626.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5136","folder":"IETF/RFC-5136","source":"IETF/RFC-5136/RFC-5136.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 1812 Network Working Group F. Baker, Editor\nRequest for Comments: 1812 Cisco Systems\nObsoletes: 1716, 1009 June 1995\nCategory: Standards Track\n\n Requirements for IP Version 4 Routers\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nPREFACE\n\n This document is an updated version of RFC 1716, the historical\n Router Requirements document. That RFC preserved the significant\n work that went into the working group, but failed to adequately\n describe current technology for the IESG to consider it a current\n standard.\n\n The current editor had been asked to bring the document up to date,\n so t 1812 algorithm algorithms management path timestamp nested-reference unchanged"},{"id":"IEEE IEEE 802.5","type":"specification","body":"IEEE","designation":"IEEE 802.5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5.html","download_urls":["https://standards.ieee.org/standard/802.5.html"],"folder":"IEEE/IEEE-802.5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1028","folder":"IETF/RFC-1028","source":"IETF/RFC-1028/RFC-1028.txt","version":null},{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1250","folder":"IETF/RFC-1250","source":"IETF/RFC-1250/RFC-1250.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IEEE IEEE 802.5 nested-reference unavailable"},{"id":"IETF RFC 1229","type":"specification","body":"IETF","designation":"RFC 1229","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1229.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1229.txt","https://www.rfc-editor.org/rfc/rfc1229.pdf"],"folder":"IETF/RFC-1229","files":{"txt":{"path":"standards/IETF/RFC-1229/RFC-1229.txt","sha256":"cb43ae4092989e661a7497f407bbfc2fab6e4609b4f279e8cc2608e3ae12a67b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, it defines managed object\n types as experimental extensions to the generic interfaces structure\n of MIB-II.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n\nSNMP Working Group [Page 1]\n\f\nRFC 1229 Interface MIB Extensions May 1991\n\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n oper","scope_keywords":["1229","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null}],"search_text":"IETF RFC 1229 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, it defines managed object\n types as experimental extensions to the generic interfaces structure\n of MIB-II.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n\nSNMP Working Group [Page 1]\n\f\nRFC 1229 Interface MIB Extensions May 1991\n\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n oper 1229 management subject nested-reference unchanged"},{"id":"IETF RFC 1248","type":"specification","body":"IETF","designation":"RFC 1248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1248.txt","https://www.rfc-editor.org/rfc/rfc1248.pdf"],"folder":"IETF/RFC-1248","files":{"txt":{"path":"standards/IETF/RFC-1248/RFC-1248.txt","sha256":"a06221f8b5d6785d46111f9ad51aca847742cc3ddefa6a3953334df85dfcac48"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, it defines objects for\n managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework per","scope_keywords":["1248","management","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1246","folder":"IETF/RFC-1246","source":"IETF/RFC-1246/RFC-1246.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null}],"search_text":"IETF RFC 1248 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, it defines objects for\n managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework per 1248 management subject validation nested-reference unchanged"},{"id":"IETF RFC 1252","type":"specification","body":"IETF","designation":"RFC 1252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1252.txt","https://www.rfc-editor.org/rfc/rfc1252.pdf"],"folder":"IETF/RFC-1252","files":{"txt":{"path":"standards/IETF/RFC-1252/RFC-1252.txt","sha256":"c68a43daeb5d38fa4827292d17d212f956f4bb4efb0f86dabf51beee0da00b18"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework permits new object","scope_keywords":["1252","management","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null}],"search_text":"IETF RFC 1252 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework permits new object 1252 management subject validation nested-reference unchanged"},{"id":"IETF RFC 1253","type":"specification","body":"IETF","designation":"RFC 1253","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1253.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1253.txt","https://www.rfc-editor.org/rfc/rfc1253.pdf"],"folder":"IETF/RFC-1253","files":{"txt":{"path":"standards/IETF/RFC-1253/RFC-1253.txt","sha256":"eb9603eaaa345577aadc52355f51bd6dfbddba9303023e9d532230a0a52f438f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework permits new object","scope_keywords":["1253","management","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1370","folder":"IETF/RFC-1370","source":"IETF/RFC-1370/RFC-1370.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1586","folder":"IETF/RFC-1586","source":"IETF/RFC-1586/RFC-1586.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null}],"search_text":"IETF RFC 1253 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing OSPF Version 2.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framework permits new object 1253 management subject validation nested-reference unchanged"},{"id":"IETF RFC 1474","type":"specification","body":"IETF","designation":"RFC 1474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1474.txt","https://www.rfc-editor.org/rfc/rfc1474.pdf"],"folder":"IETF/RFC-1474","files":{"txt":{"path":"standards/IETF/RFC-1474/RFC-1474.txt","sha256":"cf7e8f640f19f07324c3b5a2c55eda999c71bb771e359f8fa68fe4142e61fb86"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n bridge Network Control Protocol [10] on subnetwork interfaces using\n the family of Point-to-Point Protocols.","scope_keywords":["1474","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1474 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n bridge Network Control Protocol [10] on subnetwork interfaces using\n the family of Point-to-Point Protocols. 1474 authentication management nested-reference unchanged"},{"id":"IETF RFC 1532","type":"specification","body":"IETF","designation":"RFC 1532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1532.txt","https://www.rfc-editor.org/rfc/rfc1532.pdf"],"folder":"IETF/RFC-1532","files":{"txt":{"path":"standards/IETF/RFC-1532/RFC-1532.txt","sha256":"b217031d2aca9ebaad1fb508380dcdd2314915781e9fc6c8535c16578da983ee"}},"tags":["nested-reference","unchanged"],"summary":"Some aspects of the BOOTP protocol were rather loosely defined in its\n original specification. In particular, only a general description\n was provided for the behavior of \"BOOTP relay agents\" (originally\n called BOOTP forwarding agents\"). The client behavior description\n also suffered in certain ways. This memo attempts to clarify and\n strengthen the specification in these areas.\n\n In addition, new issues have arisen since the original specification\n was written. This memo also attempts to address some of these.","scope_keywords":["1532","delivery","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1534","folder":"IETF/RFC-1534","source":"IETF/RFC-1534/RFC-1534.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null}],"search_text":"IETF RFC 1532 Some aspects of the BOOTP protocol were rather loosely defined in its\n original specification. In particular, only a general description\n was provided for the behavior of \"BOOTP relay agents\" (originally\n called BOOTP forwarding agents\"). The client behavior description\n also suffered in certain ways. This memo attempts to clarify and\n strengthen the specification in these areas.\n\n In addition, new issues have arisen since the original specification\n was written. This memo also attempts to address some of these. 1532 delivery subject nested-reference unchanged"},{"id":"IETF RFC 1542","type":"specification","body":"IETF","designation":"RFC 1542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1542.txt","https://www.rfc-editor.org/rfc/rfc1542.pdf"],"folder":"IETF/RFC-1542","files":{"txt":{"path":"standards/IETF/RFC-1542/RFC-1542.txt","sha256":"791f988d45474c915f8260efdc9676729f0b7264f3af79c5910f3be4a489fdb4"}},"tags":["nested-reference","unchanged"],"summary":"Some aspects of the BOOTP protocol were rather loosely defined in its\n original specification. In particular, only a general description\n was provided for the behavior of \"BOOTP relay agents\" (originally\n called BOOTP forwarding agents\"). The client behavior description\n also suffered in certain ways. This memo attempts to clarify and\n strengthen the specification in these areas. Due to some errors\n introduced into RFC 1532 in the editorial process, this memo is\n reissued as RFC 1542.\n\n In addition, new issues have arisen since the original specification\n was written. This memo also attempts to address some of these.","scope_keywords":["1542","delivery","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null}],"search_text":"IETF RFC 1542 Some aspects of the BOOTP protocol were rather loosely defined in its\n original specification. In particular, only a general description\n was provided for the behavior of \"BOOTP relay agents\" (originally\n called BOOTP forwarding agents\"). The client behavior description\n also suffered in certain ways. This memo attempts to clarify and\n strengthen the specification in these areas. Due to some errors\n introduced into RFC 1532 in the editorial process, this memo is\n reissued as RFC 1542.\n\n In addition, new issues have arisen since the original specification\n was written. This memo also attempts to address some of these. 1542 delivery subject nested-reference unchanged"},{"id":"IETF RFC 1850","type":"specification","body":"IETF","designation":"RFC 1850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1850.txt","https://www.rfc-editor.org/rfc/rfc1850.pdf"],"folder":"IETF/RFC-1850","files":{"txt":{"path":"standards/IETF/RFC-1850/RFC-1850.txt","sha256":"8f94fb0d41ad4775f58a2efb6769d5e60217043c437ed8b64b3ae9e258bf65b3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Open Shortest Path\n First Routing Protocol.","scope_keywords":["1850","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null},{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null}],"search_text":"IETF RFC 1850 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Open Shortest Path\n First Routing Protocol. 1850 management path nested-reference unchanged"},{"id":"IETF RFC 4750","type":"specification","body":"IETF","designation":"RFC 4750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4750.txt","https://www.rfc-editor.org/rfc/rfc4750.pdf"],"folder":"IETF/RFC-4750","files":{"txt":{"path":"standards/IETF/RFC-4750/RFC-4750.txt","sha256":"6ab343f206a98ee3e2a6228a47b054e5e8c129ea4490cf07f0aabcc8eb8102dc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing version 2 of the Open\n Shortest Path First Routing Protocol. Version 2 of the OSPF protocol\n is specific to the IPv4 address family. Version 3 of the OSPF\n protocol is specific to the IPv6 address family.\n\n This memo obsoletes RFC 1850; however, it is designed to be backwards\n compatible. The functional differences between this memo and RFC\n 1850 are explained in Appendix B.\n\nGalecki, et al. Standards Track [Page 1]\n\f\nRFC 4750 OSPFv2 MIB December 2006","scope_keywords":["4750","authentication","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null}],"search_text":"IETF RFC 4750 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing version 2 of the Open\n Shortest Path First Routing Protocol. Version 2 of the OSPF protocol\n is specific to the IPv4 address family. Version 3 of the OSPF\n protocol is specific to the IPv6 address family.\n\n This memo obsoletes RFC 1850; however, it is designed to be backwards\n compatible. The functional differences between this memo and RFC\n 1850 are explained in Appendix B.\n\nGalecki, et al. Standards Track [Page 1]\n\f\nRFC 4750 OSPFv2 MIB December 2006 4750 authentication management path trust nested-reference unchanged"},{"id":"IEEE IEEE 802.5-","type":"specification","body":"IEEE","designation":"IEEE 802.5-","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5-.html","download_urls":["https://standards.ieee.org/standard/802.5-.html"],"folder":"IEEE/IEEE-802.5-","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null}],"search_text":"IEEE IEEE 802.5- nested-reference unavailable"},{"id":"IETF RFC 2475","type":"specification","body":"IETF","designation":"RFC 2475","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2475.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2475.txt","https://www.rfc-editor.org/rfc/rfc2475.pdf"],"folder":"IETF/RFC-2475","files":{"txt":{"path":"standards/IETF/RFC-2475/RFC-2475.txt","sha256":"3d239ebc304b7be7d43f79f813a4cdcd32952e5ad4c5ea4805cc040bca60f475"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an architecture for implementing scalable\n service differentiation in the Internet. This architecture achieves\n scalability by aggregating traffic classification state which is\n conveyed by means of IP-layer packet marking using the DS field\n [DSFIELD]. Packets are classified and marked to receive a particular\n per-hop forwarding behavior on nodes along their path. Sophisticated\n classification, marking, policing, and shaping operations need only\n be implemented at network boundaries or hosts. Network resources are\n allocated to traffic streams by service provisioning policies which\n govern how traffic is marked and conditioned upon entry to a\n differentiated services-capable network, and how that traffic is\n forwarded within that network. A wide variety of services can be\n implemented on top of these building blocks.\n\nBlake, et. al. Informational [Page 1]\n\f\nRFC 247","scope_keywords":["2475","audit","path","policies","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2597","folder":"IETF/RFC-2597","source":"IETF/RFC-2597/RFC-2597.txt","version":null},{"body":"IETF","designation":"RFC 2598","folder":"IETF/RFC-2598","source":"IETF/RFC-2598/RFC-2598.txt","version":null},{"body":"IETF","designation":"RFC 2697","folder":"IETF/RFC-2697","source":"IETF/RFC-2697/RFC-2697.txt","version":null},{"body":"IETF","designation":"RFC 2698","folder":"IETF/RFC-2698","source":"IETF/RFC-2698/RFC-2698.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2836","folder":"IETF/RFC-2836","source":"IETF/RFC-2836/RFC-2836.txt","version":null},{"body":"IETF","designation":"RFC 2859","folder":"IETF/RFC-2859","source":"IETF/RFC-2859/RFC-2859.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2963","folder":"IETF/RFC-2963","source":"IETF/RFC-2963/RFC-2963.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 2996","folder":"IETF/RFC-2996","source":"IETF/RFC-2996/RFC-2996.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3248","folder":"IETF/RFC-3248","source":"IETF/RFC-3248/RFC-3248.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3662","folder":"IETF/RFC-3662","source":"IETF/RFC-3662/RFC-3662.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5594","folder":"IETF/RFC-5594","source":"IETF/RFC-5594/RFC-5594.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6789","folder":"IETF/RFC-6789","source":"IETF/RFC-6789/RFC-6789.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 2475 This document defines an architecture for implementing scalable\n service differentiation in the Internet. This architecture achieves\n scalability by aggregating traffic classification state which is\n conveyed by means of IP-layer packet marking using the DS field\n [DSFIELD]. Packets are classified and marked to receive a particular\n per-hop forwarding behavior on nodes along their path. Sophisticated\n classification, marking, policing, and shaping operations need only\n be implemented at network boundaries or hosts. Network resources are\n allocated to traffic streams by service provisioning policies which\n govern how traffic is marked and conditioned upon entry to a\n differentiated services-capable network, and how that traffic is\n forwarded within that network. A wide variety of services can be\n implemented on top of these building blocks.\n\nBlake, et. al. Informational [Page 1]\n\f\nRFC 247 2475 audit path policies profile profiles nested-reference unchanged"},{"id":"IEEE IEEE 802.5-1985","type":"specification","body":"IEEE","designation":"IEEE 802.5-1985","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5-1985.html","download_urls":["https://standards.ieee.org/standard/802.5-1985.html"],"folder":"IEEE/IEEE-802.5-1985","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1042","folder":"IETF/RFC-1042","source":"IETF/RFC-1042/RFC-1042.txt","version":null}],"search_text":"IEEE IEEE 802.5-1985 nested-reference unavailable"},{"id":"IEEE IEEE 802.5-1988","type":"specification","body":"IEEE","designation":"IEEE 802.5-1988","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5-1988.html","download_urls":["https://standards.ieee.org/standard/802.5-1988.html"],"folder":"IEEE/IEEE-802.5-1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null}],"search_text":"IEEE IEEE 802.5-1988 nested-reference unavailable"},{"id":"IEEE IEEE 802.5-1995","type":"specification","body":"IEEE","designation":"IEEE 802.5-1995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5-1995.html","download_urls":["https://standards.ieee.org/standard/802.5-1995.html"],"folder":"IEEE/IEEE-802.5-1995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null}],"search_text":"IEEE IEEE 802.5-1995 nested-reference unavailable"},{"id":"IEEE IEEE 802.5-1998","type":"specification","body":"IEEE","designation":"IEEE 802.5-1998","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5-1998.html","download_urls":["https://standards.ieee.org/standard/802.5-1998.html"],"folder":"IEEE/IEEE-802.5-1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null}],"search_text":"IEEE IEEE 802.5-1998 nested-reference unavailable"},{"id":"IEEE IEEE 802.5.","type":"specification","body":"IEEE","designation":"IEEE 802.5.","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.5..html","download_urls":["https://standards.ieee.org/standard/802.5..html"],"folder":"IEEE/IEEE-802.5.","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IEEE IEEE 802.5. nested-reference unavailable"},{"id":"IEEE IEEE 802.6","type":"specification","body":"IEEE","designation":"IEEE 802.6","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/802.6.html","download_urls":["https://standards.ieee.org/standard/802.6.html"],"folder":"IEEE/IEEE-802.6","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1077","folder":"IETF/RFC-1077","source":"IETF/RFC-1077/RFC-1077.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null}],"search_text":"IEEE IEEE 802.6 nested-reference unavailable"},{"id":"IETF RFC 1077","type":"specification","body":"IETF","designation":"RFC 1077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1077.txt","https://www.rfc-editor.org/rfc/rfc1077.pdf"],"folder":"IETF/RFC-1077","files":{"txt":{"path":"standards/IETF/RFC-1077/RFC-1077.txt","sha256":"1231c50fb3b54ef5db046f9958f90d517548367723055ed6674e1d3bafee9729"}},"tags":["nested-reference","unchanged"],"summary":"At the request of Maj. Mark Pullen and Maj. Brian Boesch of DARPA, an\n ad-hoc working group was assembled to develop a set of\n recommendations on the research required to achieve a ubiquitous\n high-bandwidth network as discussed in the FCCSET recommendations for\n Phase III.\n\n This report outlines a set of research topics aimed at providing the\n technology base for an interconnected set of networks that can\n provide highbandwidth capabilities. The suggested research focus\n draws upon ongoing research and augments it with basic and applied\n components. The major activities are the development and\n demonstration of a gigabit backbone network, the development and\n demonstration of an interconnected set of networks with gigabit\n throughput and appropriate management techniques, and the development\n and demonstration of the required overall architecture that allows\n users to gain access to suc","scope_keywords":["1077","authentication","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1106","folder":"IETF/RFC-1106","source":"IETF/RFC-1106/RFC-1106.txt","version":null},{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null}],"search_text":"IETF RFC 1077 At the request of Maj. Mark Pullen and Maj. Brian Boesch of DARPA, an\n ad-hoc working group was assembled to develop a set of\n recommendations on the research required to achieve a ubiquitous\n high-bandwidth network as discussed in the FCCSET recommendations for\n Phase III.\n\n This report outlines a set of research topics aimed at providing the\n technology base for an interconnected set of networks that can\n provide highbandwidth capabilities. The suggested research focus\n draws upon ongoing research and augments it with basic and applied\n components. The major activities are the development and\n demonstration of a gigabit backbone network, the development and\n demonstration of an interconnected set of networks with gigabit\n throughput and appropriate management techniques, and the development\n and demonstration of the required overall architecture that allows\n users to gain access to suc 1077 authentication management pid nested-reference unchanged"},{"id":"IEEE IEEE 8021","type":"specification","body":"IEEE","designation":"IEEE 8021","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/8021.html","download_urls":["https://standards.ieee.org/standard/8021.html"],"folder":"IEEE/IEEE-8021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null}],"search_text":"IEEE IEEE 8021 nested-reference unavailable"},{"id":"IEEE IEEE 87","type":"specification","body":"IEEE","designation":"IEEE 87","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/87.html","download_urls":["https://standards.ieee.org/standard/87.html"],"folder":"IEEE/IEEE-87","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null}],"search_text":"IEEE IEEE 87 nested-reference unavailable"},{"id":"IEEE IEEE 90","type":"specification","body":"IEEE","designation":"IEEE 90","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/90.html","download_urls":["https://standards.ieee.org/standard/90.html"],"folder":"IEEE/IEEE-90","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IEEE IEEE 90 nested-reference unavailable"},{"id":"IETF RFC 6294","type":"specification","body":"IETF","designation":"RFC 6294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6294.txt","https://www.rfc-editor.org/rfc/rfc6294.pdf"],"folder":"IETF/RFC-6294","files":{"txt":{"path":"standards/IETF/RFC-6294/RFC-6294.txt","sha256":"f367fec16504390d7b0051b076abde4339b98f61c991c2781853c7a7d3d4a175"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 protocol includes a flow label in every packet header, but\n this field is not used in practice. This paper describes the flow\n label standard and discusses the implementation issues that it\n raises. It then describes various published proposals for using the\n flow label and shows that most of them are inconsistent with the\n standard. Methods to address this problem are briefly reviewed. We\n also question whether the standard should be revised.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any l","scope_keywords":["6294","attribute","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null}],"search_text":"IETF RFC 6294 The IPv6 protocol includes a flow label in every packet header, but\n this field is not used in practice. This paper describes the flow\n label standard and discusses the implementation issues that it\n raises. It then describes various published proposals for using the\n flow label and shows that most of them are inconsistent with the\n standard. Methods to address this problem are briefly reviewed. We\n also question whether the standard should be revised.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any l 6294 attribute http license subject trust nested-reference unchanged"},{"id":"IEEE IEEE 9945-2009","type":"specification","body":"IEEE","designation":"IEEE 9945-2009","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://standards.ieee.org/standard/9945-2009.html","download_urls":["https://standards.ieee.org/standard/9945-2009.html"],"folder":"IEEE/IEEE-9945-2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null}],"search_text":"IEEE IEEE 9945-2009 nested-reference unavailable"},{"id":"IETF RFC 7765","type":"specification","body":"IETF","designation":"RFC 7765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7765.txt","https://www.rfc-editor.org/rfc/rfc7765.pdf"],"folder":"IETF/RFC-7765","files":{"txt":{"path":"standards/IETF/RFC-7765/RFC-7765.txt","sha256":"03a11e7fa13444e7ab1fd411e570e005d8ce4e136de07b302eaec126f02f7968"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a modified sender-side algorithm for managing\n the TCP and Stream Control Transmission Protocol (SCTP)\n retransmission timers that provides faster loss recovery when there\n is a small amount of outstanding data for a connection. The\n modification, RTO Restart (RTOR), allows the transport to restart its\n retransmission timer using a smaller timeout duration, so that the\n effective retransmission timeout (RTO) becomes more aggressive in\n situations where fast retransmit cannot be used. This enables faster\n loss detection and recovery for connections that are short lived or\n application limited.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of t","scope_keywords":["7765","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null}],"search_text":"IETF RFC 7765 This document describes a modified sender-side algorithm for managing\n the TCP and Stream Control Transmission Protocol (SCTP)\n retransmission timers that provides faster loss recovery when there\n is a small amount of outstanding data for a connection. The\n modification, RTO Restart (RTOR), allows the transport to restart its\n retransmission timer using a smaller timeout duration, so that the\n effective retransmission timeout (RTO) becomes more aggressive in\n situations where fast retransmit cannot be used. This enables faster\n loss detection and recovery for connections that are short lived or\n application limited.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of t 7765 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 0001","type":"specification","body":"IETF","designation":"RFC 0001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0001.txt","https://www.rfc-editor.org/rfc/rfc0001.pdf"],"folder":"IETF/RFC-0001","files":{"txt":{"path":"standards/IETF/RFC-0001/RFC-0001.txt","sha256":"a61eb4ac9d40ac189b17214417ae6d29d4edabd86cadd31f44728faed3e600c0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Steve Crocker\nRequest for Comments: 1 UCLA\n 7 April 1969\n\n Title: Host Software\n Author: Steve Crocker\n Installation: UCLA\n Date: 7 April 1969\n Network Working Group Request for Comment: 1\n\nCONTENTS\n\nINTRODUCTION\n\n I. A Summary of the IMP Software\n\n Messages\n\n Links\n\n IMP Transmission and Error Checking\n\n Open Questions on the IMP Software\n\n II. Some Requirements Upon the Host-to-Host Software\n\n Simple Use\n\n Deep Use\n\n Error Checking\n\nIII. The Host Software\n\n Establishment of a Connection\n\n High Volume Transmission\n\n A Summary of Primitives\n\n Error Checking\n\n Closer Interaction\n\n Open Questions\n\nCrocker [Page 1]\n\f\nRFC 1 Host Software 7 April 1969\n\n IV. Initial Experiments\n\n Experiment One\n\n Experiment Two\n\nIntroduction\n\n The software for the ARPA Network exists partly in the IMPs and\n partly in the respective HOSTs. BB&N has specified the software of\n the IMPs and i","scope_keywords":["0001"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null}],"search_text":"IETF RFC 0001 Network Working Group Steve Crocker\nRequest for Comments: 1 UCLA\n 7 April 1969\n\n Title: Host Software\n Author: Steve Crocker\n Installation: UCLA\n Date: 7 April 1969\n Network Working Group Request for Comment: 1\n\nCONTENTS\n\nINTRODUCTION\n\n I. A Summary of the IMP Software\n\n Messages\n\n Links\n\n IMP Transmission and Error Checking\n\n Open Questions on the IMP Software\n\n II. Some Requirements Upon the Host-to-Host Software\n\n Simple Use\n\n Deep Use\n\n Error Checking\n\nIII. The Host Software\n\n Establishment of a Connection\n\n High Volume Transmission\n\n A Summary of Primitives\n\n Error Checking\n\n Closer Interaction\n\n Open Questions\n\nCrocker [Page 1]\n\f\nRFC 1 Host Software 7 April 1969\n\n IV. Initial Experiments\n\n Experiment One\n\n Experiment Two\n\nIntroduction\n\n The software for the ARPA Network exists partly in the IMPs and\n partly in the respective HOSTs. BB&N has specified the software of\n the IMPs and i 0001 nested-reference unchanged"},{"id":"IETF RFC 8890","type":"specification","body":"IETF","designation":"RFC 8890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8890.txt","https://www.rfc-editor.org/rfc/rfc8890.pdf"],"folder":"IETF/RFC-8890","files":{"pdf":{"path":"standards/IETF/RFC-8890/RFC-8890.pdf","sha256":"d7935b539cb1ebd21c2fee196b8011a6a038fcbc1d99d66530dc0bb6b7fce3af"},"txt":{"path":"standards/IETF/RFC-8890/RFC-8890.txt","sha256":"078e90f304a894710fb701ff2d5ae8b7457e5b5a9f013f6a6a89ec526a4761bc"}},"tags":["nested-reference","unchanged"],"summary":"This document explains why the IAB believes that, when there is a\n conflict between the interests of end users of the Internet and other\n parties, IETF decisions should favor end users. It also explores how\n the IETF can more effectively achieve this.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org","scope_keywords":["8890","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 8890 This document explains why the IAB believes that, when there is a\n conflict between the interests of end users of the Internet and other\n parties, IETF decisions should favor end users. It also explores how\n the IETF can more effectively achieve this.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org 8890 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 0003","type":"specification","body":"IETF","designation":"RFC 0003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0003.txt","https://www.rfc-editor.org/rfc/rfc0003.pdf"],"folder":"IETF/RFC-0003","files":{"txt":{"path":"standards/IETF/RFC-0003/RFC-0003.txt","sha256":"fc6b8d93a449fe48d21d5519632b79f4d40a08077e134ed2bd529595485040bd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 4689\nRFC-3 April 1969\n Steve Crocker\n UCLA\n\n DOCUMENTATION CONVENTIONS\n\nThe Network Working Group seems to consist of Steve Carr of Utah, Jeff\nRulifson and Bill Duvall at SRI, and Steve Crocker and Gerard Deloche\nat UCLA. Membership is not closed.\n\nThe Network Working Group (NWG) is concerned with the HOST software, the\nstrategies for using the network, and initial experiments with the network.\n\nDocumentation of the NWG's effort is through notes such as this. Notes\nmay be produced at any site by anybody and included in this series.\n \n\nCONTENT\n\nThe content of a NWG note may be any thought, suggestion, etc. related to\nthe HOST software or other aspect of the network. Notes are encouraged to\nbe timely rather than polished. Philosophical positions without examples\nor other specifics, specific suggestions or implementation techniques\nwithout introductory or background ex","scope_keywords":["0003"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null}],"search_text":"IETF RFC 0003 Network Working Group 4689\nRFC-3 April 1969\n Steve Crocker\n UCLA\n\n DOCUMENTATION CONVENTIONS\n\nThe Network Working Group seems to consist of Steve Carr of Utah, Jeff\nRulifson and Bill Duvall at SRI, and Steve Crocker and Gerard Deloche\nat UCLA. Membership is not closed.\n\nThe Network Working Group (NWG) is concerned with the HOST software, the\nstrategies for using the network, and initial experiments with the network.\n\nDocumentation of the NWG's effort is through notes such as this. Notes\nmay be produced at any site by anybody and included in this series.\n \n\nCONTENT\n\nThe content of a NWG note may be any thought, suggestion, etc. related to\nthe HOST software or other aspect of the network. Notes are encouraged to\nbe timely rather than polished. Philosophical positions without examples\nor other specifics, specific suggestions or implementation techniques\nwithout introductory or background ex 0003 nested-reference unchanged"},{"id":"IETF RFC 5741","type":"specification","body":"IETF","designation":"RFC 5741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5741.txt","https://www.rfc-editor.org/rfc/rfc5741.pdf"],"folder":"IETF/RFC-5741","files":{"txt":{"path":"standards/IETF/RFC-5741/RFC-5741.txt","sha256":"f7dbd96d8642be229574ed6ab00ec0978534550a35970bbae6b119d97f680d19"}},"tags":["nested-reference","unchanged"],"summary":"RFC documents contain a number of fixed elements such as the title\n page header, standard boilerplates, and copyright/IPR statements.\n This document describes them and introduces some updates to reflect\n current usage and requirements of RFC publication. In particular,\n this updated structure is intended to communicate clearly the source\n of RFC creation and review.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it","scope_keywords":["5741","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5457","folder":"IETF/RFC-5457","source":"IETF/RFC-5457/RFC-5457.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5663","folder":"IETF/RFC-5663","source":"IETF/RFC-5663/RFC-5663.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5713","folder":"IETF/RFC-5713","source":"IETF/RFC-5713/RFC-5713.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5719","folder":"IETF/RFC-5719","source":"IETF/RFC-5719/RFC-5719.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5736","folder":"IETF/RFC-5736","source":"IETF/RFC-5736/RFC-5736.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5756","folder":"IETF/RFC-5756","source":"IETF/RFC-5756/RFC-5756.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5759","folder":"IETF/RFC-5759","source":"IETF/RFC-5759/RFC-5759.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5769","folder":"IETF/RFC-5769","source":"IETF/RFC-5769/RFC-5769.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5781","folder":"IETF/RFC-5781","source":"IETF/RFC-5781/RFC-5781.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5808","folder":"IETF/RFC-5808","source":"IETF/RFC-5808/RFC-5808.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5829","folder":"IETF/RFC-5829","source":"IETF/RFC-5829/RFC-5829.txt","version":null},{"body":"IETF","designation":"RFC 5830","folder":"IETF/RFC-5830","source":"IETF/RFC-5830/RFC-5830.txt","version":null},{"body":"IETF","designation":"RFC 5831","folder":"IETF/RFC-5831","source":"IETF/RFC-5831/RFC-5831.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5861","folder":"IETF/RFC-5861","source":"IETF/RFC-5861/RFC-5861.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5867","folder":"IETF/RFC-5867","source":"IETF/RFC-5867/RFC-5867.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5871","folder":"IETF/RFC-5871","source":"IETF/RFC-5871/RFC-5871.txt","version":null},{"body":"IETF","designation":"RFC 5872","folder":"IETF/RFC-5872","source":"IETF/RFC-5872/RFC-5872.txt","version":null},{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5893","folder":"IETF/RFC-5893","source":"IETF/RFC-5893/RFC-5893.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5895","folder":"IETF/RFC-5895","source":"IETF/RFC-5895/RFC-5895.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5932","folder":"IETF/RFC-5932","source":"IETF/RFC-5932/RFC-5932.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5964","folder":"IETF/RFC-5964","source":"IETF/RFC-5964/RFC-5964.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6019","folder":"IETF/RFC-6019","source":"IETF/RFC-6019/RFC-6019.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6085","folder":"IETF/RFC-6085","source":"IETF/RFC-6085/RFC-6085.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6105","folder":"IETF/RFC-6105","source":"IETF/RFC-6105/RFC-6105.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6177","folder":"IETF/RFC-6177","source":"IETF/RFC-6177/RFC-6177.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6188","folder":"IETF/RFC-6188","source":"IETF/RFC-6188/RFC-6188.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6194","folder":"IETF/RFC-6194","source":"IETF/RFC-6194/RFC-6194.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6206","folder":"IETF/RFC-6206","source":"IETF/RFC-6206/RFC-6206.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6212","folder":"IETF/RFC-6212","source":"IETF/RFC-6212/RFC-6212.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6215","folder":"IETF/RFC-6215","source":"IETF/RFC-6215/RFC-6215.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6221","folder":"IETF/RFC-6221","source":"IETF/RFC-6221/RFC-6221.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6229","folder":"IETF/RFC-6229","source":"IETF/RFC-6229/RFC-6229.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6243","folder":"IETF/RFC-6243","source":"IETF/RFC-6243/RFC-6243.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6288","folder":"IETF/RFC-6288","source":"IETF/RFC-6288/RFC-6288.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6351","folder":"IETF/RFC-6351","source":"IETF/RFC-6351/RFC-6351.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6355","folder":"IETF/RFC-6355","source":"IETF/RFC-6355/RFC-6355.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6360","folder":"IETF/RFC-6360","source":"IETF/RFC-6360/RFC-6360.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 6386","folder":"IETF/RFC-6386","source":"IETF/RFC-6386/RFC-6386.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6410","folder":"IETF/RFC-6410","source":"IETF/RFC-6410/RFC-6410.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6419","folder":"IETF/RFC-6419","source":"IETF/RFC-6419/RFC-6419.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6430","folder":"IETF/RFC-6430","source":"IETF/RFC-6430/RFC-6430.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6452","folder":"IETF/RFC-6452","source":"IETF/RFC-6452/RFC-6452.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6552","folder":"IETF/RFC-6552","source":"IETF/RFC-6552/RFC-6552.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 6562","folder":"IETF/RFC-6562","source":"IETF/RFC-6562/RFC-6562.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6564","folder":"IETF/RFC-6564","source":"IETF/RFC-6564/RFC-6564.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6585","folder":"IETF/RFC-6585","source":"IETF/RFC-6585/RFC-6585.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6603","folder":"IETF/RFC-6603","source":"IETF/RFC-6603/RFC-6603.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6644","folder":"IETF/RFC-6644","source":"IETF/RFC-6644/RFC-6644.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6685","folder":"IETF/RFC-6685","source":"IETF/RFC-6685/RFC-6685.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6694","folder":"IETF/RFC-6694","source":"IETF/RFC-6694/RFC-6694.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6713","folder":"IETF/RFC-6713","source":"IETF/RFC-6713/RFC-6713.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6737","folder":"IETF/RFC-6737","source":"IETF/RFC-6737/RFC-6737.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6755","folder":"IETF/RFC-6755","source":"IETF/RFC-6755/RFC-6755.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6789","folder":"IETF/RFC-6789","source":"IETF/RFC-6789/RFC-6789.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6807","folder":"IETF/RFC-6807","source":"IETF/RFC-6807/RFC-6807.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6832","folder":"IETF/RFC-6832","source":"IETF/RFC-6832/RFC-6832.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6834","folder":"IETF/RFC-6834","source":"IETF/RFC-6834/RFC-6834.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6941","folder":"IETF/RFC-6941","source":"IETF/RFC-6941/RFC-6941.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6949","folder":"IETF/RFC-6949","source":"IETF/RFC-6949/RFC-6949.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 6970","folder":"IETF/RFC-6970","source":"IETF/RFC-6970/RFC-6970.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 6982","folder":"IETF/RFC-6982","source":"IETF/RFC-6982/RFC-6982.txt","version":null},{"body":"IETF","designation":"RFC 6983","folder":"IETF/RFC-6983","source":"IETF/RFC-6983/RFC-6983.txt","version":null},{"body":"IETF","designation":"RFC 6985","folder":"IETF/RFC-6985","source":"IETF/RFC-6985/RFC-6985.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null},{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7040","folder":"IETF/RFC-7040","source":"IETF/RFC-7040/RFC-7040.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7083","folder":"IETF/RFC-7083","source":"IETF/RFC-7083/RFC-7083.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7120","folder":"IETF/RFC-7120","source":"IETF/RFC-7120/RFC-7120.txt","version":null},{"body":"IETF","designation":"RFC 7127","folder":"IETF/RFC-7127","source":"IETF/RFC-7127/RFC-7127.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7164","folder":"IETF/RFC-7164","source":"IETF/RFC-7164/RFC-7164.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7218","folder":"IETF/RFC-7218","source":"IETF/RFC-7218/RFC-7218.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7282","folder":"IETF/RFC-7282","source":"IETF/RFC-7282/RFC-7282.txt","version":null},{"body":"IETF","designation":"RFC 7283","folder":"IETF/RFC-7283","source":"IETF/RFC-7283/RFC-7283.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7319","folder":"IETF/RFC-7319","source":"IETF/RFC-7319/RFC-7319.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7335","folder":"IETF/RFC-7335","source":"IETF/RFC-7335/RFC-7335.txt","version":null},{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null},{"body":"IETF","designation":"RFC 7337","folder":"IETF/RFC-7337","source":"IETF/RFC-7337/RFC-7337.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7346","folder":"IETF/RFC-7346","source":"IETF/RFC-7346/RFC-7346.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7366","folder":"IETF/RFC-7366","source":"IETF/RFC-7366/RFC-7366.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7375","folder":"IETF/RFC-7375","source":"IETF/RFC-7375/RFC-7375.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7396","folder":"IETF/RFC-7396","source":"IETF/RFC-7396/RFC-7396.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7405","folder":"IETF/RFC-7405","source":"IETF/RFC-7405/RFC-7405.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7465","folder":"IETF/RFC-7465","source":"IETF/RFC-7465/RFC-7465.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 7498","folder":"IETF/RFC-7498","source":"IETF/RFC-7498/RFC-7498.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null},{"body":"IETF","designation":"RFC 7536","folder":"IETF/RFC-7536","source":"IETF/RFC-7536/RFC-7536.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7539","folder":"IETF/RFC-7539","source":"IETF/RFC-7539/RFC-7539.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7632","folder":"IETF/RFC-7632","source":"IETF/RFC-7632/RFC-7632.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7685","folder":"IETF/RFC-7685","source":"IETF/RFC-7685/RFC-7685.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7693","folder":"IETF/RFC-7693","source":"IETF/RFC-7693/RFC-7693.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7706","folder":"IETF/RFC-7706","source":"IETF/RFC-7706/RFC-7706.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 7748","folder":"IETF/RFC-7748","source":"IETF/RFC-7748/RFC-7748.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 7793","folder":"IETF/RFC-7793","source":"IETF/RFC-7793/RFC-7793.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7830","folder":"IETF/RFC-7830","source":"IETF/RFC-7830/RFC-7830.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null}],"search_text":"IETF RFC 5741 RFC documents contain a number of fixed elements such as the title\n page header, standard boilerplates, and copyright/IPR statements.\n This document describes them and introduces some updates to reflect\n current usage and requirements of RFC publication. In particular,\n this updated structure is intended to communicate clearly the source\n of RFC creation and review.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it 5741 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7841","type":"specification","body":"IETF","designation":"RFC 7841","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7841.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7841.txt","https://www.rfc-editor.org/rfc/rfc7841.pdf"],"folder":"IETF/RFC-7841","files":{"txt":{"path":"standards/IETF/RFC-7841/RFC-7841.txt","sha256":"9d5e0b45a7a3fe095ceec5e05a228dd990553374d99ff9fb622cc77bbd9e5e9f"}},"tags":["nested-reference","unchanged"],"summary":"RFC documents contain a number of fixed elements such as the title\n page header, standard boilerplates, and copyright/IPR statements.\n This document describes them and introduces some updates to reflect\n current usage and requirements of RFC publication. In particular,\n this updated structure is intended to communicate clearly the source\n of RFC creation and review. This document obsoletes RFC 5741, moving\n detailed content to an IAB web page and preparing for more flexible\n output formats.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication ","scope_keywords":["7841","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7872","folder":"IETF/RFC-7872","source":"IETF/RFC-7872/RFC-7872.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 7932","folder":"IETF/RFC-7932","source":"IETF/RFC-7932/RFC-7932.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7993","folder":"IETF/RFC-7993","source":"IETF/RFC-7993/RFC-7993.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8032","folder":"IETF/RFC-8032","source":"IETF/RFC-8032/RFC-8032.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8034","folder":"IETF/RFC-8034","source":"IETF/RFC-8034/RFC-8034.txt","version":null},{"body":"IETF","designation":"RFC 8035","folder":"IETF/RFC-8035","source":"IETF/RFC-8035/RFC-8035.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8073","folder":"IETF/RFC-8073","source":"IETF/RFC-8073/RFC-8073.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8078","folder":"IETF/RFC-8078","source":"IETF/RFC-8078/RFC-8078.txt","version":null},{"body":"IETF","designation":"RFC 8081","folder":"IETF/RFC-8081","source":"IETF/RFC-8081/RFC-8081.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8174","folder":"IETF/RFC-8174","source":"IETF/RFC-8174/RFC-8174.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8235","folder":"IETF/RFC-8235","source":"IETF/RFC-8235/RFC-8235.txt","version":null},{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null},{"body":"IETF","designation":"RFC 8246","folder":"IETF/RFC-8246","source":"IETF/RFC-8246/RFC-8246.txt","version":null},{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8297","folder":"IETF/RFC-8297","source":"IETF/RFC-8297/RFC-8297.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8307","folder":"IETF/RFC-8307","source":"IETF/RFC-8307/RFC-8307.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8391","folder":"IETF/RFC-8391","source":"IETF/RFC-8391/RFC-8391.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8421","folder":"IETF/RFC-8421","source":"IETF/RFC-8421/RFC-8421.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8478","folder":"IETF/RFC-8478","source":"IETF/RFC-8478/RFC-8478.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8903","folder":"IETF/RFC-8903","source":"IETF/RFC-8903/RFC-8903.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8943","folder":"IETF/RFC-8943","source":"IETF/RFC-8943/RFC-8943.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null},{"body":"IETF","designation":"RFC 9021","folder":"IETF/RFC-9021","source":"IETF/RFC-9021/RFC-9021.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9106","folder":"IETF/RFC-9106","source":"IETF/RFC-9106/RFC-9106.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 7841 RFC documents contain a number of fixed elements such as the title\n page header, standard boilerplates, and copyright/IPR statements.\n This document describes them and introduces some updates to reflect\n current usage and requirements of RFC publication. In particular,\n this updated structure is intended to communicate clearly the source\n of RFC creation and review. This document obsoletes RFC 5741, moving\n detailed content to an IAB web page and preparing for more flexible\n output formats.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication  7841 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 0010","type":"specification","body":"IETF","designation":"RFC 0010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0010.txt","https://www.rfc-editor.org/rfc/rfc0010.pdf"],"folder":"IETF/RFC-0010","files":{"txt":{"path":"standards/IETF/RFC-0010/RFC-0010.txt","sha256":"3fd9694cf3fba6f2576b17b4945605215a2fda4b7319d6c1ac60de555e4e4220"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRFC-10 UCLA\n 29 July 1969\n\n DOCUMENTATION CONVENTIONS\n\nThis note is a revision of NWG/RFC #3\n\nThe Network Working Group seems to consist of Steve Carr at Utah, Elmer\nShapiro and Bill English SRI, Steve Crocker at UCLA, John Haefner at\nRAND, Paul Rovner and Jim Curry at Lincoln Labs. Membership is not closed.\n\nThe Network Working Group (NWG) is concerned with the HOST software, the\nstrategies for using the network, and initial experience with the network.\n\nDocumentation of the NWG's effort is through notes such as this. Notes\nmay be produced at any site by anybody and included in this series.\n\nCONTENT\n\nThe content of a NWG note may be any thought, suggestion, etc. related to\nthe HOST software or other aspect of the network. Notes are encouraged to\nbe timely rather than polished. Philosophical positions without examples\nor other specifics, specific suggesti","scope_keywords":["0010"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null}],"search_text":"IETF RFC 0010 Network Working Group S. Crocker\nRFC-10 UCLA\n 29 July 1969\n\n DOCUMENTATION CONVENTIONS\n\nThis note is a revision of NWG/RFC #3\n\nThe Network Working Group seems to consist of Steve Carr at Utah, Elmer\nShapiro and Bill English SRI, Steve Crocker at UCLA, John Haefner at\nRAND, Paul Rovner and Jim Curry at Lincoln Labs. Membership is not closed.\n\nThe Network Working Group (NWG) is concerned with the HOST software, the\nstrategies for using the network, and initial experience with the network.\n\nDocumentation of the NWG's effort is through notes such as this. Notes\nmay be produced at any site by anybody and included in this series.\n\nCONTENT\n\nThe content of a NWG note may be any thought, suggestion, etc. related to\nthe HOST software or other aspect of the network. Notes are encouraged to\nbe timely rather than polished. Philosophical positions without examples\nor other specifics, specific suggesti 0010 nested-reference unchanged"},{"id":"IETF RFC 0020","type":"specification","body":"IETF","designation":"RFC 0020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0020.txt","https://www.rfc-editor.org/rfc/rfc0020.pdf"],"folder":"IETF/RFC-0020","files":{"pdf":{"path":"standards/IETF/RFC-0020/RFC-0020.pdf","sha256":"3de8154cb12e5a52f917ab4bbe7829803eb48c569633abd1faf8a7d456343f46"},"txt":{"path":"standards/IETF/RFC-0020/RFC-0020.txt","sha256":"714d11bfcbc001f98cd8a92291a19e3f670c2236ad02771092e0eea826acd13a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Vint Cerf\nRequest for Comments: 20 UCLA\n October 16, 1969\n\n ASCII format for Network Interchange\n\n For concreteness, we suggest the use of standard 7-bit ASCII embedded\n in an 8 bit byte whose high order bit is always 0. This leads to the\n standard code given on the attached page, copies from USAS X3, 4-\n 1968. This code will be used over HOST-HOST primary connections.\n Break characters will be defined by the receiving remote host, e.g.\n SRI uses \".\" (ASCII X'2E' or 2/14) as the end-of-line character,\n where as UCLA uses X'OD' or 0/13 (carriage return).\n\nUSA Standard Code for Information Interchange\n\n1. Scope\n\n This coded character set is to be used for the general interchange of\n information among information processing systems, communication\n systems, and associated equipment.\n\nCert [Page 1]\n\f\nRFC 20 ASCII format for Network Interchange October 1969\n\n2. Standard C","scope_keywords":["0020","identification","key","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4627","folder":"IETF/RFC-4627","source":"IETF/RFC-4627/RFC-4627.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null}],"search_text":"IETF RFC 0020 Network Working Group Vint Cerf\nRequest for Comments: 20 UCLA\n October 16, 1969\n\n ASCII format for Network Interchange\n\n For concreteness, we suggest the use of standard 7-bit ASCII embedded\n in an 8 bit byte whose high order bit is always 0. This leads to the\n standard code given on the attached page, copies from USAS X3, 4-\n 1968. This code will be used over HOST-HOST primary connections.\n Break characters will be defined by the receiving remote host, e.g.\n SRI uses \".\" (ASCII X'2E' or 2/14) as the end-of-line character,\n where as UCLA uses X'OD' or 0/13 (carriage return).\n\nUSA Standard Code for Information Interchange\n\n1. Scope\n\n This coded character set is to be used for the general interchange of\n information among information processing systems, communication\n systems, and associated equipment.\n\nCert [Page 1]\n\f\nRFC 20 ASCII format for Network Interchange October 1969\n\n2. Standard C 0020 identification key presentation risk nested-reference unchanged"},{"id":"IETF RFC 4627","type":"specification","body":"IETF","designation":"RFC 4627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4627.txt","https://www.rfc-editor.org/rfc/rfc4627.pdf"],"folder":"IETF/RFC-4627","files":{"txt":{"path":"standards/IETF/RFC-4627/RFC-4627.txt","sha256":"a31e840012e96413836c40f31d0506d355f3d9c4853e80d77240b59fff96518d"}},"tags":["nested-reference","unchanged"],"summary":"JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n1. Introduction\n\n JavaScript Object Notation (JSON) is a text format for the\n serialization of structured data. It is derived from the object\n literals of JavaScript, as defined in the ECMAScript Programming\n Language Standard, Third Edition [ECMA].\n\n JSON can represent four primitive types (strings, numbers, booleans,\n and null) and two structured types (objects and arrays).\n\n A string is a sequence of zero or more Unicode characters [UNICODE].\n\n An object is an unordered collection of zero or more name/value\n pairs, where a name is a string and a value is a string, number,\n boolean, null, object, or array.\n\n An a","scope_keywords":["4627","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 4627 JavaScript Object Notation (JSON) is a lightweight, text-based,\n language-independent data interchange format. It was derived from\n the ECMAScript Programming Language Standard. JSON defines a small\n set of formatting rules for the portable representation of structured\n data.\n\n1. Introduction\n\n JavaScript Object Notation (JSON) is a text format for the\n serialization of structured data. It is derived from the object\n literals of JavaScript, as defined in the ECMAScript Programming\n Language Standard, Third Edition [ECMA].\n\n JSON can represent four primitive types (strings, numbers, booleans,\n and null) and two structured types (objects and arrays).\n\n A string is a sequence of zero or more Unicode characters [UNICODE].\n\n An object is an unordered collection of zero or more name/value\n pairs, where a name is a string and a value is a string, number,\n boolean, null, object, or array.\n\n An a 4627 key presentation nested-reference unchanged"},{"id":"IETF RFC 5198","type":"specification","body":"IETF","designation":"RFC 5198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5198.txt","https://www.rfc-editor.org/rfc/rfc5198.pdf"],"folder":"IETF/RFC-5198","files":{"txt":{"path":"standards/IETF/RFC-5198/RFC-5198.txt","sha256":"ebe9a1e6a12697c57b81d236d384695c25103c026a3ed9598da30bf770526fb1"}},"tags":["nested-reference","unchanged"],"summary":"The Internet today is in need of a standardized form for the\n transmission of internationalized \"text\" information, paralleling the\n specifications for the use of ASCII that date from the early days of\n the ARPANET. This document specifies that format, using UTF-8 with\n normalization and specific line-ending sequences.","scope_keywords":["5198","crl","key","policy","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"IETF RFC 5198 The Internet today is in need of a standardized form for the\n transmission of internationalized \"text\" information, paralleling the\n specifications for the use of ASCII that date from the early days of\n the ARPANET. This document specifies that format, using UTF-8 with\n normalization and specific line-ending sequences. 5198 crl key policy profile profiles nested-reference unchanged"},{"id":"IETF RFC 7515","type":"specification","body":"IETF","designation":"RFC 7515","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7515.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7515.txt","https://www.rfc-editor.org/rfc/rfc7515.pdf"],"folder":"IETF/RFC-7515","files":{"txt":{"path":"standards/IETF/RFC-7515/RFC-7515.txt","sha256":"ecbf84674118e62526511c1237e1deaa86aada86d25b247623a2a7e04ae62e40"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"JSON Web Signature (JWS) represents content secured with digital\n signatures or Message Authentication Codes (MACs) using JSON-based\n data structures. Cryptographic algorithms and identifiers for use\n with this specification are described in the separate JSON Web\n Algorithms (JWA) specification and an IANA registry defined by that\n specification. Related encryption capabilities are described in the\n separate JSON Web Encryption (JWE) specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this ","scope_keywords":["7515","algorithm","algorithms","authentication","certificate","encryption","http","identification","key","ledger","license","qualified","registered","seal","signature","signatures"],"parent_legal_regulations":[{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"},{"celex":"32026R0248","eli":"https://data.europa.eu/eli/reg_impl/2026/248/oj/eng","id":"2026-248","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-248/2026-248.md","title":"Formats of advanced electronic signatures and seals"}],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 7515 JSON Web Signature (JWS) represents content secured with digital\n signatures or Message Authentication Codes (MACs) using JSON-based\n data structures. Cryptographic algorithms and identifiers for use\n with this specification are described in the separate JSON Web\n Algorithms (JWA) specification and an IANA registry defined by that\n specification. Related encryption capabilities are described in the\n separate JSON Web Encryption (JWE) specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this  7515 algorithm algorithms authentication certificate encryption http identification key ledger license qualified registered seal signature signatures cited-by-eu-law implementing-regulation nested-reference unchanged 2025-2531 Qualified electronic ledgers 32025R2531 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731 2026-248 Formats of advanced electronic signatures and seals 32026R0248"},{"id":"IETF RFC 7516","type":"specification","body":"IETF","designation":"RFC 7516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7516.txt","https://www.rfc-editor.org/rfc/rfc7516.pdf"],"folder":"IETF/RFC-7516","files":{"txt":{"path":"standards/IETF/RFC-7516/RFC-7516.txt","sha256":"722cfcddc15f58e746891ba4b846853d3711153a774e4dd55ad6db100474a21f"}},"tags":["nested-reference","unchanged"],"summary":"JSON Web Encryption (JWE) represents encrypted content using\n JSON-based data structures. Cryptographic algorithms and identifiers\n for use with this specification are described in the separate JSON\n Web Algorithms (JWA) specification and IANA registries defined by\n that specification. Related digital signature and Message\n Authentication Code (MAC) capabilities are described in the separate\n JSON Web Signature (JWS) specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any err","scope_keywords":["7516","algorithm","algorithms","authentication","certificate","encryption","http","identification","key","license","presentation","registered","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 7516 JSON Web Encryption (JWE) represents encrypted content using\n JSON-based data structures. Cryptographic algorithms and identifiers\n for use with this specification are described in the separate JSON\n Web Algorithms (JWA) specification and IANA registries defined by\n that specification. Related digital signature and Message\n Authentication Code (MAC) capabilities are described in the separate\n JSON Web Signature (JWS) specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any err 7516 algorithm algorithms authentication certificate encryption http identification key license presentation registered signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7517","type":"specification","body":"IETF","designation":"RFC 7517","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7517.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7517.txt","https://www.rfc-editor.org/rfc/rfc7517.pdf"],"folder":"IETF/RFC-7517","files":{"txt":{"path":"standards/IETF/RFC-7517/RFC-7517.txt","sha256":"681c19b92a85068716b7e89c5815aa821bd3f11c755ff1c641b40ae9851bb33c"}},"tags":["nested-reference","unchanged"],"summary":"A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data\n structure that represents a cryptographic key. This specification\n also defines a JWK Set JSON data structure that represents a set of\n JWKs. Cryptographic algorithms and identifiers for use with this\n specification are described in the separate JSON Web Algorithms (JWA)\n specification and IANA registries established by that specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["7517","algorithm","algorithms","certificate","certificates","encryption","http","key","keys","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 7517 A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data\n structure that represents a cryptographic key. This specification\n also defines a JWK Set JSON data structure that represents a set of\n JWKs. Cryptographic algorithms and identifiers for use with this\n specification are described in the separate JSON Web Algorithms (JWA)\n specification and IANA registries established by that specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 7517 algorithm algorithms certificate certificates encryption http key keys license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7518","type":"specification","body":"IETF","designation":"RFC 7518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7518.txt","https://www.rfc-editor.org/rfc/rfc7518.pdf"],"folder":"IETF/RFC-7518","files":{"txt":{"path":"standards/IETF/RFC-7518/RFC-7518.txt","sha256":"9a9ae524b09ea700ad3f189bac115df95ba69af84b26ffdbe3cdfb8d2152b1fc"}},"tags":["nested-reference","unchanged"],"summary":"This specification registers cryptographic algorithms and identifiers\n to be used with the JSON Web Signature (JWS), JSON Web Encryption\n (JWE), and JSON Web Key (JWK) specifications. It defines several\n IANA registries for these identifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7518.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document","scope_keywords":["7518","algorithm","algorithms","authentication","encryption","http","key","keys","license","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 7518 This specification registers cryptographic algorithms and identifiers\n to be used with the JSON Web Signature (JWS), JSON Web Encryption\n (JWE), and JSON Web Key (JWK) specifications. It defines several\n IANA registries for these identifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7518.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document 7518 algorithm algorithms authentication encryption http key keys license management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 7564","type":"specification","body":"IETF","designation":"RFC 7564","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7564.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7564.txt","https://www.rfc-editor.org/rfc/rfc7564.pdf"],"folder":"IETF/RFC-7564","files":{"txt":{"path":"standards/IETF/RFC-7564/RFC-7564.txt","sha256":"189c722e7a42d19783be1bfcbcde1ec17fb01b7ff1d5853a8a111a0fa4d1d9c5"}},"tags":["nested-reference","unchanged"],"summary":"Application protocols using Unicode characters in protocol strings\n need to properly handle such strings in order to enforce\n internationalization rules for strings placed in various protocol\n slots (such as addresses and identifiers) and to perform valid\n comparison operations (e.g., for purposes of authentication or\n authorization). This document defines a framework enabling\n application protocols to perform the preparation, enforcement, and\n comparison of internationalized strings (\"PRECIS\") in a way that\n depends on the properties of Unicode characters and thus is agile\n with respect to versions of Unicode. As a result, this framework\n provides a more sustainable approach to the handling of\n internationalized strings than the previous framework, known as\n Stringprep (RFC 3454). This document obsoletes RFC 3454.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th","scope_keywords":["7564","authentication","authorization","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 7564 Application protocols using Unicode characters in protocol strings\n need to properly handle such strings in order to enforce\n internationalization rules for strings placed in various protocol\n slots (such as addresses and identifiers) and to perform valid\n comparison operations (e.g., for purposes of authentication or\n authorization). This document defines a framework enabling\n application protocols to perform the preparation, enforcement, and\n comparison of internationalized strings (\"PRECIS\") in a way that\n depends on the properties of Unicode characters and thus is agile\n with respect to versions of Unicode. As a result, this framework\n provides a more sustainable approach to the handling of\n internationalized strings than the previous framework, known as\n Stringprep (RFC 3454). This document obsoletes RFC 3454.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th 7564 authentication authorization http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7613","type":"specification","body":"IETF","designation":"RFC 7613","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7613.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7613.txt","https://www.rfc-editor.org/rfc/rfc7613.pdf"],"folder":"IETF/RFC-7613","files":{"txt":{"path":"standards/IETF/RFC-7613/RFC-7613.txt","sha256":"53fd64ec77131206f0dc708925ebbff6345ef481d277dc9e45005fa4bf899e84"}},"tags":["nested-reference","unchanged"],"summary":"This document describes updated methods for handling Unicode strings\n representing usernames and passwords. The previous approach was\n known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454).\n The methods specified in this document provide a more sustainable\n approach to the handling of internationalized usernames and\n passwords. The preparation, enforcement, and comparison of\n internationalized strings (PRECIS) framework, RFC 7564, obsoletes RFC\n 3454, and this document obsoletes RFC 4013.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RF","scope_keywords":["7613","algorithm","authentication","authorization","hash","http","license","preservation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null}],"search_text":"IETF RFC 7613 This document describes updated methods for handling Unicode strings\n representing usernames and passwords. The previous approach was\n known as SASLprep (RFC 4013) and was based on stringprep (RFC 3454).\n The methods specified in this document provide a more sustainable\n approach to the handling of internationalized usernames and\n passwords. The preparation, enforcement, and comparison of\n internationalized strings (PRECIS) framework, RFC 7564, obsoletes RFC\n 3454, and this document obsoletes RFC 4013.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RF 7613 algorithm authentication authorization hash http license preservation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7617","type":"specification","body":"IETF","designation":"RFC 7617","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7617.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7617.txt","https://www.rfc-editor.org/rfc/rfc7617.pdf"],"folder":"IETF/RFC-7617","files":{"txt":{"path":"standards/IETF/RFC-7617/RFC-7617.txt","sha256":"bc941321da9912fbb1bc92ad1820848ddfd3283dbfbc30f26ea2800bdaf541db"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the \"Basic\" Hypertext Transfer Protocol (HTTP)\n authentication scheme, which transmits credentials as user-id/\n password pairs, encoded using Base64.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7617.\n\nReschke Standards Track [Page 1]\n\f\nRFC 7617 'Basic' HTTP Authentication Scheme September 2015\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons ide","scope_keywords":["7617","authentication","credential","credentials","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 7617 This document defines the \"Basic\" Hypertext Transfer Protocol (HTTP)\n authentication scheme, which transmits credentials as user-id/\n password pairs, encoded using Base64.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7617.\n\nReschke Standards Track [Page 1]\n\f\nRFC 7617 'Basic' HTTP Authentication Scheme September 2015\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons ide 7617 authentication credential credentials http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7636","type":"specification","body":"IETF","designation":"RFC 7636","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7636.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7636.txt","https://www.rfc-editor.org/rfc/rfc7636.pdf"],"folder":"IETF/RFC-7636","files":{"txt":{"path":"standards/IETF/RFC-7636/RFC-7636.txt","sha256":"1972e5d81cbaba7066cfd46374207bc2b4546b085ed5dd9b034e79e023e0ca31"}},"tags":["nested-reference","unchanged"],"summary":"OAuth 2.0 public clients utilizing the Authorization Code Grant are\n susceptible to the authorization code interception attack. This\n specification describes the attack as well as a technique to mitigate\n against the threat through the use of Proof Key for Code Exchange\n (PKCE, pronounced \"pixy\").\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7636.\n\nCopyright Notice\n\n Copyright (c) 201","scope_keywords":["7636","authorization","http","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 7636 OAuth 2.0 public clients utilizing the Authorization Code Grant are\n susceptible to the authorization code interception attack. This\n specification describes the attack as well as a technique to mitigate\n against the threat through the use of Proof Key for Code Exchange\n (PKCE, pronounced \"pixy\").\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7636.\n\nCopyright Notice\n\n Copyright (c) 201 7636 authorization http key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7914","type":"specification","body":"IETF","designation":"RFC 7914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7914.txt","https://www.rfc-editor.org/rfc/rfc7914.pdf"],"folder":"IETF/RFC-7914","files":{"txt":{"path":"standards/IETF/RFC-7914/RFC-7914.txt","sha256":"df55932f8b6a5d271f36a634d91a25903724e189ba6c120bf7257cd47f10b197"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the password-based key derivation function\n scrypt. The function derives one or more secret keys from a secret\n string. It is based on memory-hard functions, which offer added\n protection against attacks using custom hardware. The document also\n provides an ASN.1 schema.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it","scope_keywords":["7914","algorithm","algorithms","hash","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 7914 This document specifies the password-based key derivation function\n scrypt. The function derives one or more secret keys from a secret\n string. It is based on memory-hard functions, which offer added\n protection against attacks using custom hardware. The document also\n provides an ASN.1 schema.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it 7914 algorithm algorithms hash http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 7997","type":"specification","body":"IETF","designation":"RFC 7997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7997.txt","https://www.rfc-editor.org/rfc/rfc7997.pdf"],"folder":"IETF/RFC-7997","files":{"pdf":{"path":"standards/IETF/RFC-7997/RFC-7997.pdf","sha256":"58f773f9bf8a1ad479fb6de25decca02ca0504361ea8079b875c9ad88e009460"},"txt":{"path":"standards/IETF/RFC-7997/RFC-7997.txt","sha256":"af9ea2dd25fd2f54b33642e6060924f68f2564371c2d57fc4e9897e7cc7ba48a"}},"tags":["nested-reference","unchanged"],"summary":"In order to support the internationalization of protocols and a more\n diverse Internet community, the RFC Series must evolve to allow for\n the use of non-ASCII characters in RFCs. While English remains the\n required language of the Series, the encoding of future RFCs will be\n in UTF-8, allowing for a broader range of characters than typically\n used in the English language. This document describes the RFC Editor\n requirements and gives guidance regarding the use of non-ASCII\n characters in RFCs.\n\n This document updates RFC 7322. Please view this document in PDF\n form to see the full text.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It repre","scope_keywords":["7997","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"IETF RFC 7997 In order to support the internationalization of protocols and a more\n diverse Internet community, the RFC Series must evolve to allow for\n the use of non-ASCII characters in RFCs. While English remains the\n required language of the Series, the encoding of future RFCs will be\n in UTF-8, allowing for a broader range of characters than typically\n used in the English language. This document describes the RFC Editor\n requirements and gives guidance regarding the use of non-ASCII\n characters in RFCs.\n\n This document updates RFC 7322. Please view this document in PDF\n form to see the full text.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It repre 7997 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8141","type":"specification","body":"IETF","designation":"RFC 8141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8141.txt","https://www.rfc-editor.org/rfc/rfc8141.pdf"],"folder":"IETF/RFC-8141","files":{"txt":{"path":"standards/IETF/RFC-8141/RFC-8141.txt","sha256":"9e3296eaac5641d356f580696894878dddc525124436d1da7005f0748035d41e"}},"tags":["nested-reference","unchanged"],"summary":"A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)\n that is assigned under the \"urn\" URI scheme and a particular URN\n namespace, with the intent that the URN will be a persistent,\n location-independent resource identifier. With regard to URN syntax,\n this document defines the canonical syntax for URNs (in a way that is\n consistent with URI syntax), specifies methods for determining URN-\n equivalence, and discusses URI conformance. With regard to URN\n namespaces, this document specifies a method for defining a URN\n namespace and associating it with a namespace identifier, and it\n describes procedures for registering namespace identifiers with the\n Internet Assigned Numbers Authority (IANA). This document obsoletes\n both RFCs 2141 and 3406.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Fo","scope_keywords":["8141","algorithm","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null}],"search_text":"IETF RFC 8141 A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI)\n that is assigned under the \"urn\" URI scheme and a particular URN\n namespace, with the intent that the URN will be a persistent,\n location-independent resource identifier. With regard to URN syntax,\n this document defines the canonical syntax for URNs (in a way that is\n consistent with URI syntax), specifies methods for determining URN-\n equivalence, and discusses URI conformance. With regard to URN\n namespaces, this document specifies a method for defining a URN\n namespace and associating it with a namespace identifier, and it\n describes procedures for registering namespace identifiers with the\n Internet Assigned Numbers Authority (IANA). This document obsoletes\n both RFCs 2141 and 3406.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Fo 8141 algorithm http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8187","type":"specification","body":"IETF","designation":"RFC 8187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8187.txt","https://www.rfc-editor.org/rfc/rfc8187.pdf"],"folder":"IETF/RFC-8187","files":{"txt":{"path":"standards/IETF/RFC-8187/RFC-8187.txt","sha256":"af50e65257dc16a27fa85e25ef68d49c8fa2a4abc21094a00469462c8cb89b53"}},"tags":["nested-reference","unchanged"],"summary":"By default, header field values in Hypertext Transfer Protocol (HTTP)\n messages cannot easily carry characters outside the US-ASCII coded\n character set. RFC 2231 defines an encoding mechanism for use in\n parameters inside Multipurpose Internet Mail Extensions (MIME) header\n field values. This document specifies an encoding suitable for use\n in HTTP header fields that is compatible with a simplified profile of\n the encoding defined in RFC 2231.\n\n This document obsoletes RFC 5987.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information a","scope_keywords":["8187","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 8187 By default, header field values in Hypertext Transfer Protocol (HTTP)\n messages cannot easily carry characters outside the US-ASCII coded\n character set. RFC 2231 defines an encoding mechanism for use in\n parameters inside Multipurpose Internet Mail Extensions (MIME) header\n field values. This document specifies an encoding suitable for use\n in HTTP header fields that is compatible with a simplified profile of\n the encoding defined in RFC 2231.\n\n This document obsoletes RFC 5987.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information a 8187 http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8264","type":"specification","body":"IETF","designation":"RFC 8264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8264.txt","https://www.rfc-editor.org/rfc/rfc8264.pdf"],"folder":"IETF/RFC-8264","files":{"txt":{"path":"standards/IETF/RFC-8264/RFC-8264.txt","sha256":"8a380eba9971be10b4a9af0ab8579d33939b60b91cf776881f222de112067f3f"}},"tags":["nested-reference","unchanged"],"summary":"Application protocols using Unicode code points in protocol strings\n need to properly handle such strings in order to enforce\n internationalization rules for strings placed in various protocol\n slots (such as addresses and identifiers) and to perform valid\n comparison operations (e.g., for purposes of authentication or\n authorization). This document defines a framework enabling\n application protocols to perform the preparation, enforcement, and\n comparison of internationalized strings (\"PRECIS\") in a way that\n depends on the properties of Unicode code points and thus is more\n agile with respect to versions of Unicode. As a result, this\n framework provides a more sustainable approach to the handling of\n internationalized strings than the previous framework, known as\n Stringprep (RFC 3454). This document obsoletes RFC 7564.\n\nStatus of This Memo\n\n This is an Internet Standards Track documen","scope_keywords":["8264","authentication","authorization","http","https","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 8264 Application protocols using Unicode code points in protocol strings\n need to properly handle such strings in order to enforce\n internationalization rules for strings placed in various protocol\n slots (such as addresses and identifiers) and to perform valid\n comparison operations (e.g., for purposes of authentication or\n authorization). This document defines a framework enabling\n application protocols to perform the preparation, enforcement, and\n comparison of internationalized strings (\"PRECIS\") in a way that\n depends on the properties of Unicode code points and thus is more\n agile with respect to versions of Unicode. As a result, this\n framework provides a more sustainable approach to the handling of\n internationalized strings than the previous framework, known as\n Stringprep (RFC 3454). This document obsoletes RFC 7564.\n\nStatus of This Memo\n\n This is an Internet Standards Track documen 8264 authentication authorization http https license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8265","type":"specification","body":"IETF","designation":"RFC 8265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8265.txt","https://www.rfc-editor.org/rfc/rfc8265.pdf"],"folder":"IETF/RFC-8265","files":{"txt":{"path":"standards/IETF/RFC-8265/RFC-8265.txt","sha256":"ec987e39b242228e870b8d1df836451e19cdb2bd66b1ac105355adeae36ff32f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes updated methods for handling Unicode strings\n representing usernames and passwords. The previous approach was\n known as SASLprep (RFC 4013) and was based on Stringprep (RFC 3454).\n The methods specified in this document provide a more sustainable\n approach to the handling of internationalized usernames and\n passwords. This document obsoletes RFC 7613.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at","scope_keywords":["8265","algorithm","authentication","authorization","hash","http","https","license","preservation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 8265 This document describes updated methods for handling Unicode strings\n representing usernames and passwords. The previous approach was\n known as SASLprep (RFC 4013) and was based on Stringprep (RFC 3454).\n The methods specified in this document provide a more sustainable\n approach to the handling of internationalized usernames and\n passwords. This document obsoletes RFC 7613.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at 8265 algorithm authentication authorization hash http https license preservation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8266","type":"specification","body":"IETF","designation":"RFC 8266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8266.txt","https://www.rfc-editor.org/rfc/rfc8266.pdf"],"folder":"IETF/RFC-8266","files":{"txt":{"path":"standards/IETF/RFC-8266/RFC-8266.txt","sha256":"5ff7c6c0b11dc05932798fcd2a1ee2f2b2fae5279e076461ce07c5617f02d3df"}},"tags":["nested-reference","unchanged"],"summary":"This document describes methods for handling Unicode strings\n representing memorable, human-friendly names (called \"nicknames\",\n \"display names\", or \"petnames\") for people, devices, accounts,\n websites, and other entities. This document obsoletes RFC 7700.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8266.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified a","scope_keywords":["8266","authentication","authorization","http","https","key","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null}],"search_text":"IETF RFC 8266 This document describes methods for handling Unicode strings\n representing memorable, human-friendly names (called \"nicknames\",\n \"display names\", or \"petnames\") for people, devices, accounts,\n websites, and other entities. This document obsoletes RFC 7700.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8266.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified a 8266 authentication authorization http https key license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8322","type":"specification","body":"IETF","designation":"RFC 8322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8322.txt","https://www.rfc-editor.org/rfc/rfc8322.pdf"],"folder":"IETF/RFC-8322","files":{"txt":{"path":"standards/IETF/RFC-8322/RFC-8322.txt","sha256":"6936804b7cc890aeac3714769047f50e8b53c8149f03aa216b74deab2bec008d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a resource-oriented approach for security\n automation information publication, discovery, and sharing. Using\n this approach, producers may publish, share, and exchange\n representations of software descriptors, security incidents, attack\n indicators, software vulnerabilities, configuration checklists, and\n other security automation information as web-addressable resources.\n Furthermore, consumers and other stakeholders may access and search\n this security information as needed, establishing a rapid and\n on-demand information exchange network for restricted internal use or\n public access repositories. This specification extends the Atom\n Publishing Protocol and Atom Syndication Format to transport and\n share security automation resource representations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet En","scope_keywords":["8322","authentication","authorization","holder","http","https","identification","license","pid","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"IETF RFC 8322 This document defines a resource-oriented approach for security\n automation information publication, discovery, and sharing. Using\n this approach, producers may publish, share, and exchange\n representations of software descriptors, security incidents, attack\n indicators, software vulnerabilities, configuration checklists, and\n other security automation information as web-addressable resources.\n Furthermore, consumers and other stakeholders may access and search\n this security information as needed, establishing a rapid and\n on-demand information exchange network for restricted internal use or\n public access repositories. This specification extends the Atom\n Publishing Protocol and Atom Syndication Format to transport and\n share security automation resource representations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet En 8322 authentication authorization holder http https identification license pid presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8915","type":"specification","body":"IETF","designation":"RFC 8915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8915.txt","https://www.rfc-editor.org/rfc/rfc8915.pdf"],"folder":"IETF/RFC-8915","files":{"pdf":{"path":"standards/IETF/RFC-8915/RFC-8915.pdf","sha256":"3ffe98b167ed6e91044c1a1f7cd24dfba5cae31ad862eefa39eb9c87637d5e44"},"txt":{"path":"standards/IETF/RFC-8915/RFC-8915.txt","sha256":"c92a3ce4d1984b4c13f1cdf74d6f76c42b0fd34b2c1b71f5dd4f7d1cc641f57d"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies Network Time Security (NTS), a mechanism for\n using Transport Layer Security (TLS) and Authenticated Encryption\n with Associated Data (AEAD) to provide cryptographic security for the\n client-server mode of the Network Time Protocol (NTP).\n\n NTS is structured as a suite of two loosely coupled sub-protocols.\n The first (NTS Key Establishment (NTS-KE)) handles initial\n authentication and key establishment over TLS. The second (NTS\n Extension Fields for NTPv4) handles encryption and authentication\n during NTP time synchronization via extension fields in the NTP\n packets, and holds all required state only on the client via opaque\n cookies.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has b","scope_keywords":["8915","algorithm","authentication","certificate","certificates","encryption","hash","holder","http","https","key","license","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 8915 This memo specifies Network Time Security (NTS), a mechanism for\n using Transport Layer Security (TLS) and Authenticated Encryption\n with Associated Data (AEAD) to provide cryptographic security for the\n client-server mode of the Network Time Protocol (NTP).\n\n NTS is structured as a suite of two loosely coupled sub-protocols.\n The first (NTS Key Establishment (NTS-KE)) handles initial\n authentication and key establishment over TLS. The second (NTS\n Extension Fields for NTPv4) handles encryption and authentication\n during NTP time synchronization via extension fields in the NTP\n packets, and holds all required state only on the client via opaque\n cookies.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has b 8915 algorithm authentication certificate certificates encryption hash holder http https key license profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9001","type":"specification","body":"IETF","designation":"RFC 9001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9001.txt","https://www.rfc-editor.org/rfc/rfc9001.pdf"],"folder":"IETF/RFC-9001","files":{"pdf":{"path":"standards/IETF/RFC-9001/RFC-9001.pdf","sha256":"1cbf86bfbde67ed62f841af84edc8009a0bf9b7e5571babeee0b83d1a1211a15"},"txt":{"path":"standards/IETF/RFC-9001/RFC-9001.txt","sha256":"3bbaecdf5afd278052a2c48348ce118c4ff8d0cf6b9915549858171b3f98a591"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how Transport Layer Security (TLS) is used to\n secure QUIC.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9001.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.o","scope_keywords":["9001","algorithm","authentication","certificate","delivery","encryption","http","https","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9001 This document describes how Transport Layer Security (TLS) is used to\n secure QUIC.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9001.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.o 9001 algorithm authentication certificate delivery encryption http https key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9277","type":"specification","body":"IETF","designation":"RFC 9277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9277.txt","https://www.rfc-editor.org/rfc/rfc9277.pdf"],"folder":"IETF/RFC-9277","files":{"pdf":{"path":"standards/IETF/RFC-9277/RFC-9277.pdf","sha256":"fa10c5f9fcbde8ef77fd9811e595b0e5d61e31d190f6b1dfe74f3f11928d7e15"},"txt":{"path":"standards/IETF/RFC-9277/RFC-9277.txt","sha256":"bd637eafad9ef940c8f5d029076f70c58af7bde6beb38efee5ba7af3690289f7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a stored (\"file\") format for Concise Binary\n Object Representation (CBOR) data items that is friendly to common\n systems that recognize file types, such as the Unix file(1) command.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9277.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["9277","attestation","certificate","encryption","http","https","identification","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9277 This document defines a stored (\"file\") format for Concise Binary\n Object Representation (CBOR) data items that is friendly to common\n systems that recognize file types, such as the Unix file(1) command.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9277.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  9277 attestation certificate encryption http https identification key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 9396","type":"specification","body":"IETF","designation":"RFC 9396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9396.txt","https://www.rfc-editor.org/rfc/rfc9396.pdf"],"folder":"IETF/RFC-9396","files":{"pdf":{"path":"standards/IETF/RFC-9396/RFC-9396.pdf","sha256":"569a2e22da89f09ddca16fed5673d260498436417ca4cf4b726dedde2ccafd06"},"txt":{"path":"standards/IETF/RFC-9396/RFC-9396.txt","sha256":"d6a8f032d8a585daae1c33a8c7b6e539d199f886ec8cc1c7898436f7f2eed29c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new parameter authorization_details that is\n used to carry fine-grained authorization data in OAuth messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9396.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions","scope_keywords":["9396","authorization","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9396 This document specifies a new parameter authorization_details that is\n used to carry fine-grained authorization data in OAuth messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9396.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions 9396 authorization http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 9458","type":"specification","body":"IETF","designation":"RFC 9458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9458.txt","https://www.rfc-editor.org/rfc/rfc9458.pdf"],"folder":"IETF/RFC-9458","files":{"pdf":{"path":"standards/IETF/RFC-9458/RFC-9458.pdf","sha256":"0bb5759755da6f054187901b24f852e07e62448c6897afeb84cac3b824d1cfd9"},"txt":{"path":"standards/IETF/RFC-9458/RFC-9458.txt","sha256":"55f13cb7b3501e29f9edbbbbd9c8a3e13b84799d609d0e01443f543effa99350"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Oblivious HTTP, a protocol for forwarding\n encrypted HTTP messages. Oblivious HTTP allows a client to make\n multiple requests to an origin server without that server being able\n to link those requests to the client or to identify the requests as\n having come from the same client, while placing only limited trust in\n the nodes used to forward the messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine","scope_keywords":["9458","algorithm","algorithms","attribute","encryption","http","https","identification","key","keys","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 9458 This document describes Oblivious HTTP, a protocol for forwarding\n encrypted HTTP messages. Oblivious HTTP allows a client to make\n multiple requests to an origin server without that server being able\n to link those requests to the client or to identify the requests as\n having come from the same client, while placing only limited trust in\n the nodes used to forward the messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine 9458 algorithm algorithms attribute encryption http https identification key keys license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9499","type":"specification","body":"IETF","designation":"RFC 9499","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9499.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9499.txt","https://www.rfc-editor.org/rfc/rfc9499.pdf"],"folder":"IETF/RFC-9499","files":{"pdf":{"path":"standards/IETF/RFC-9499/RFC-9499.pdf","sha256":"8aab4bc8fb6295fbd030c098b771a9eff9067aba57e50879dca5e8c2ed323e7c"},"txt":{"path":"standards/IETF/RFC-9499/RFC-9499.txt","sha256":"270b62df854911dddd246f6c081952106897983a5e02dfe8b3819d72843d9ab1"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) is defined in literally dozens of\n different RFCs. The terminology used by implementers and developers\n of DNS protocols, and by operators of DNS systems, has changed in the\n decades since the DNS was first defined. This document gives current\n definitions for many of the terms used in the DNS in a single\n document.\n\n This document updates RFC 2308 by clarifying the definitions of\n \"forwarder\" and \"QNAME\". It obsoletes RFC 8499 by adding multiple\n terms and clarifications. Comprehensive lists of changed and new\n definitions can be found in Appendices A and B.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering S","scope_keywords":["9499","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 9499 The Domain Name System (DNS) is defined in literally dozens of\n different RFCs. The terminology used by implementers and developers\n of DNS protocols, and by operators of DNS systems, has changed in the\n decades since the DNS was first defined. This document gives current\n definitions for many of the terms used in the DNS in a single\n document.\n\n This document updates RFC 2308 by clarifying the definitions of\n \"forwarder\" and \"QNAME\". It obsoletes RFC 8499 by adding multiple\n terms and clarifications. Comprehensive lists of changed and new\n definitions can be found in Appendices A and B.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering S 9499 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 9535","type":"specification","body":"IETF","designation":"RFC 9535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9535.txt","https://www.rfc-editor.org/rfc/rfc9535.pdf"],"folder":"IETF/RFC-9535","files":{"pdf":{"path":"standards/IETF/RFC-9535/RFC-9535.pdf","sha256":"6a371b35ff7572a458bc070b85d17e29e705caba38c98342ff9e6c6f07f62d10"},"txt":{"path":"standards/IETF/RFC-9535/RFC-9535.txt","sha256":"bfcb53387d47e3b807bdb695d0a3e136f0c515947289d9c67df354f12ae1fda5"}},"tags":["nested-reference","unchanged"],"summary":"JSONPath defines a string syntax for selecting and extracting JSON\n (RFC 8259) values from within a given JSON value.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9535.\n\nCopyright Notice\n\n Copyright (c) 2024 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF ","scope_keywords":["9535","http","https","key","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null}],"search_text":"IETF RFC 9535 JSONPath defines a string syntax for selecting and extracting JSON\n (RFC 8259) values from within a given JSON value.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9535.\n\nCopyright Notice\n\n Copyright (c) 2024 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF  9535 http https key license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 0021","type":"specification","body":"IETF","designation":"RFC 0021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0021.txt","https://www.rfc-editor.org/rfc/rfc0021.pdf"],"folder":"IETF/RFC-0021","files":{"txt":{"path":"standards/IETF/RFC-0021/RFC-0021.txt","sha256":"2f5e3b43155553ffb14476dd671e75dd4c628f051e9b7dc7284995207b238d76"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 21 UCLA\n October 17, 1969\n\nAt UCLA on October 10, there was a network meeting attended by:\n\n SDC UCLA\n\n John Kreznar Vint Cerf\n Dick Linde Steve Crocker\n Marty Bleier Jon Postel\n Bob Long Michel Elie\n\n UCSB\n\n Ron Stoughton\n Nancy O'Hara\n George Gregg\n\nTopics discussed:\n\n 1. Revisions to BBN memo 1822\n \n 2. Revisions to NWG/RFC 11\n\n 3. Transmission of multiple control messages\n\n1. Changes to BBN Memo No. 1822 (underlined)\n As informally communicated by Dave Wa\n\n p. 11 \"The IMP program can handle up to 63 active transmit links\n and 63 active receive links at a time. If the Host attempts to\n send a message on a new link when 63 active transmit links already\n exist, a \"Link Table Full\" message will be sent from the IMP to\n the Host, and the message will be discarded.\"\n \n p. 11 \"1. Any link that is not used for a period of 26 seconds\n will h","scope_keywords":["0021"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null}],"search_text":"IETF RFC 0021 Network Working Group V. Cerf\nRequest for Comments: 21 UCLA\n October 17, 1969\n\nAt UCLA on October 10, there was a network meeting attended by:\n\n SDC UCLA\n\n John Kreznar Vint Cerf\n Dick Linde Steve Crocker\n Marty Bleier Jon Postel\n Bob Long Michel Elie\n\n UCSB\n\n Ron Stoughton\n Nancy O'Hara\n George Gregg\n\nTopics discussed:\n\n 1. Revisions to BBN memo 1822\n \n 2. Revisions to NWG/RFC 11\n\n 3. Transmission of multiple control messages\n\n1. Changes to BBN Memo No. 1822 (underlined)\n As informally communicated by Dave Wa\n\n p. 11 \"The IMP program can handle up to 63 active transmit links\n and 63 active receive links at a time. If the Host attempts to\n send a message on a new link when 63 active transmit links already\n exist, a \"Link Table Full\" message will be sent from the IMP to\n the Host, and the message will be discarded.\"\n \n p. 11 \"1. Any link that is not used for a period of 26 seconds\n will h 0021 nested-reference unchanged"},{"id":"IETF RFC 4846","type":"specification","body":"IETF","designation":"RFC 4846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4846.txt","https://www.rfc-editor.org/rfc/rfc4846.pdf"],"folder":"IETF/RFC-4846","files":{"txt":{"path":"standards/IETF/RFC-4846/RFC-4846.txt","sha256":"34802f5c4fb01d50d437ac4357db5876c65cd63b047b5eb7c1819f09cbd7f7f1"}},"tags":["nested-reference","unchanged"],"summary":"There is a long-standing tradition in the Internet community,\n predating the Internet Engineering Task Force (IETF) by many years,\n of use of the RFC Series to publish materials that are not rooted in\n the IETF standards process and its review and approval mechanisms.\n These documents, known as \"Independent Submissions\", serve a number\n of important functions for the Internet community, both inside and\n outside of the community of active IETF participants. This document\n discusses the Independent Submission model and some reasons why it is\n important. It then describes editorial and processing norms that can\n be used for Independent Submissions as the community goes forward\n into new relationships between the IETF community and its primary\n technical publisher.\n\nKlensin & Thaler Informational [Page 1]\n\f\nRFC 4846 Independent Submissions July 2007","scope_keywords":["4846","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null}],"search_text":"IETF RFC 4846 There is a long-standing tradition in the Internet community,\n predating the Internet Engineering Task Force (IETF) by many years,\n of use of the RFC Series to publish materials that are not rooted in\n the IETF standards process and its review and approval mechanisms.\n These documents, known as \"Independent Submissions\", serve a number\n of important functions for the Internet community, both inside and\n outside of the community of active IETF participants. This document\n discusses the Independent Submission model and some reasons why it is\n important. It then describes editorial and processing norms that can\n be used for Independent Submissions as the community goes forward\n into new relationships between the IETF community and its primary\n technical publisher.\n\nKlensin & Thaler Informational [Page 1]\n\f\nRFC 4846 Independent Submissions July 2007 4846 trust nested-reference unchanged"},{"id":"IETF RFC 0033","type":"specification","body":"IETF","designation":"RFC 0033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0033.txt","https://www.rfc-editor.org/rfc/rfc0033.pdf"],"folder":"IETF/RFC-0033","files":{"txt":{"path":"standards/IETF/RFC-0033/RFC-0033.txt","sha256":"b938d0318b1001a2567cb76980c892c18bee9a09cd4371a091fd1e7dc5dd4c63"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRequest for Comments: 33 UCLA\n S. Carr\n University of Utah\n V. Cerf\n UCLA\n 12 February 1970\n\n New HOST-HOST Protocol\n\n Attached is a copy of the paper to be presented at the SJCC on the\n HOST-HOST Protocol. It indicates many changes from the old protocol\n in NWG/RFC 11; these changes resulted from the network meeting on\n December 8, 1969. The attached document does not contain enough\n information to write a NCP, and I will send out another memo or so\n shortly. Responses to this memo are solicited, either as NWG/RFC's\n or personal notes to me.\n\n HOST-HOST Communication Protocol\n in the ARPA Network*\n\n by C. Stephen Carr\n University of Utah\n Salt Lake City, Utah\n\n and\n\n by Stephen D. Crocker\n University of California\n Los Angeles, California\n\n and\n\n by Vinton G. Cerf\n University of California\n Los Angeles, California\n\n *This research was sponsored by the Ad","scope_keywords":["0033","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0033 Network Working Group S. Crocker\nRequest for Comments: 33 UCLA\n S. Carr\n University of Utah\n V. Cerf\n UCLA\n 12 February 1970\n\n New HOST-HOST Protocol\n\n Attached is a copy of the paper to be presented at the SJCC on the\n HOST-HOST Protocol. It indicates many changes from the old protocol\n in NWG/RFC 11; these changes resulted from the network meeting on\n December 8, 1969. The attached document does not contain enough\n information to write a NCP, and I will send out another memo or so\n shortly. Responses to this memo are solicited, either as NWG/RFC's\n or personal notes to me.\n\n HOST-HOST Communication Protocol\n in the ARPA Network*\n\n by C. Stephen Carr\n University of Utah\n Salt Lake City, Utah\n\n and\n\n by Stephen D. Crocker\n University of California\n Los Angeles, California\n\n and\n\n by Vinton G. Cerf\n University of California\n Los Angeles, California\n\n *This research was sponsored by the Ad 0033 path nested-reference unchanged"},{"id":"IETF RFC 7605","type":"specification","body":"IETF","designation":"RFC 7605","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7605.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7605.txt","https://www.rfc-editor.org/rfc/rfc7605.pdf"],"folder":"IETF/RFC-7605","files":{"txt":{"path":"standards/IETF/RFC-7605/RFC-7605.txt","sha256":"dfdc6d12716ba0b9dd000c5540be4aac1ce3bbd58fcb09dc69bce629b80e64fa"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations to designers of application\n and service protocols on how to use the transport protocol port\n number space and when to request a port assignment from IANA. It\n provides designer guidance to requesters or users of port numbers on\n how to interact with IANA using the processes defined in RFC 6335;\n thus, this document complements (but does not update) that document.\n It provides guidelines for designers regarding how to interact with\n the IANA processes defined in RFC 6335, thus serving to complement\n (but not update) that document.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG","scope_keywords":["7605","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 7605 This document provides recommendations to designers of application\n and service protocols on how to use the transport protocol port\n number space and when to request a port assignment from IANA. It\n provides designer guidance to requesters or users of port numbers on\n how to interact with IANA using the processes defined in RFC 6335;\n thus, this document complements (but does not update) that document.\n It provides guidelines for designers regarding how to interact with\n the IANA processes defined in RFC 6335, thus serving to complement\n (but not update) that document.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG 7605 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 0037","type":"specification","body":"IETF","designation":"RFC 0037","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0037.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0037.txt","https://www.rfc-editor.org/rfc/rfc0037.pdf"],"folder":"IETF/RFC-0037","files":{"txt":{"path":"standards/IETF/RFC-0037/RFC-0037.txt","sha256":"8187ffa1e705796ea6949e3be100c19d243e666e6a9f158ba991fd2556ba88de"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRequest for Comments: 37 UCLA\n 20 March 1970\n\n Network Meeting Epilogue, etc.\n\nThe Meeting\n-----------\n\n On Tuesday, March 17, 1970, I hosted a Network meeting at UCLA.\n About 25 people attended, including representatives from MIT, LL,\n BBN, Harvard, SRI, Utah, UCSB, SDC, RAND and UCLA. I presented a\n modification of the protocol in NWG/RFC #33; the modifications are\n sketchily documented in NWG/RFC #36. The main modification is the\n facility for dynamic reconnection.\n\n The protocol based on sockets and undistinguished simplex\n connections is quite different from the previous protocol as\n documented in NWG/RFC #11. The impetus for making such changes came\n out of the network meeting on December 8, 1969, at Utah, at which\n time the limitations of a log-in requirement and the inability to\n connect arbitrary processes was seriously challenged. Accordingly,\n ","scope_keywords":["0037"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0037 Network Working Group S. Crocker\nRequest for Comments: 37 UCLA\n 20 March 1970\n\n Network Meeting Epilogue, etc.\n\nThe Meeting\n-----------\n\n On Tuesday, March 17, 1970, I hosted a Network meeting at UCLA.\n About 25 people attended, including representatives from MIT, LL,\n BBN, Harvard, SRI, Utah, UCSB, SDC, RAND and UCLA. I presented a\n modification of the protocol in NWG/RFC #33; the modifications are\n sketchily documented in NWG/RFC #36. The main modification is the\n facility for dynamic reconnection.\n\n The protocol based on sockets and undistinguished simplex\n connections is quite different from the previous protocol as\n documented in NWG/RFC #11. The impetus for making such changes came\n out of the network meeting on December 8, 1969, at Utah, at which\n time the limitations of a log-in requirement and the inability to\n connect arbitrary processes was seriously challenged. Accordingly,\n  0037 nested-reference unchanged"},{"id":"IETF RFC 0038","type":"specification","body":"IETF","designation":"RFC 0038","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0038.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0038.txt","https://www.rfc-editor.org/rfc/rfc0038.pdf"],"folder":"IETF/RFC-0038","files":{"txt":{"path":"standards/IETF/RFC-0038/RFC-0038.txt","sha256":"0d12fcf7ac07b9fe64e92ac538179f3c176878429ffbd59817cc9795ba18c899"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Stephen M. Wolfe\nRequest for Comments: 38 UCLA CCN\n 20 March 1970\n\n Comments on Network Protocol\n from NWG/RFC #36\n\n The proposed protocol does not allow for the possible multiplexing of\n connections over links.\n\n Generally, this presents no problem, but it might cause loading\n restrictions in the future. Two cases where routing multiple\n connections over the same link are apparent:\n\n a) Where a user has several high speed connections, such as\n between processes that transmit files over the network.\n Assigning these connections to the same link limits the\n percentage of network resources that may be used by that\n user. This becomes particularly important when several\n store-and-forward IMP's are used by the network to effect\n the communication.\n b) When two hosts each have their own independent network and\n desire to allow access to the other hosts's network over\n t","scope_keywords":["0038"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0038 Network Working Group Stephen M. Wolfe\nRequest for Comments: 38 UCLA CCN\n 20 March 1970\n\n Comments on Network Protocol\n from NWG/RFC #36\n\n The proposed protocol does not allow for the possible multiplexing of\n connections over links.\n\n Generally, this presents no problem, but it might cause loading\n restrictions in the future. Two cases where routing multiple\n connections over the same link are apparent:\n\n a) Where a user has several high speed connections, such as\n between processes that transmit files over the network.\n Assigning these connections to the same link limits the\n percentage of network resources that may be used by that\n user. This becomes particularly important when several\n store-and-forward IMP's are used by the network to effect\n the communication.\n b) When two hosts each have their own independent network and\n desire to allow access to the other hosts's network over\n t 0038 nested-reference unchanged"},{"id":"IETF RFC 0048","type":"specification","body":"IETF","designation":"RFC 0048","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0048.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0048.txt","https://www.rfc-editor.org/rfc/rfc0048.pdf"],"folder":"IETF/RFC-0048","files":{"txt":{"path":"standards/IETF/RFC-0048/RFC-0048.txt","sha256":"65655cf4f478ec133e96731b905916d48f18de81dc916bd2802b13aa9a06a152"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 48 S. Crocker\n UCLA\n April 21, 1970\n\n A Possible Protocol Plateau\n\nI. Introduction\n\n We have been engaged in two activities since the network meeting of\n March 17, 1970 and, as promised, are reporting our results.\n\n First, we have considered the various modifications suggested from\n all quarters and have formed preferences about each of these. In\n Section II we give our preferences on each issue, together with our\n reasoning.\n\n Second, we have tried to formalize the protocol and algorithms for\n the NCP, we attempted to do this with very little specification of a\n particular implementation. Our attempts to date have been seriously\n incomplete but have led to a better understanding. We include here,\n only a brief sketch of the structure of the NCP. Section III gives\n our assumptions about the environment of the NCP and in Section IV\n th","scope_keywords":["0048","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0048 Network Working Group J. Postel\nRequest for Comments: 48 S. Crocker\n UCLA\n April 21, 1970\n\n A Possible Protocol Plateau\n\nI. Introduction\n\n We have been engaged in two activities since the network meeting of\n March 17, 1970 and, as promised, are reporting our results.\n\n First, we have considered the various modifications suggested from\n all quarters and have formed preferences about each of these. In\n Section II we give our preferences on each issue, together with our\n reasoning.\n\n Second, we have tried to formalize the protocol and algorithms for\n the NCP, we attempted to do this with very little specification of a\n particular implementation. Our attempts to date have been seriously\n incomplete but have led to a better understanding. We include here,\n only a brief sketch of the structure of the NCP. Section III gives\n our assumptions about the environment of the NCP and in Section IV\n th 0048 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 0061","type":"specification","body":"IETF","designation":"RFC 0061","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0061.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0061.txt","https://www.rfc-editor.org/rfc/rfc0061.pdf"],"folder":"IETF/RFC-0061","files":{"txt":{"path":"standards/IETF/RFC-0061/RFC-0061.txt","sha256":"590ea3af32032240f7371d6286db9118c7df4eb07c2505c26242a8c67f471282"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Dave Walden\nRequest for Comments: 61 Bolt Beranek and Newman\n July 17, 1970\n\n A Note on Interprocess Communication\n in a Resource Sharing Computer Network\n\n The attached note is a draft of a study I am still working on. It\n may be of general interest to network participants.\n\nWalden [Page 1]\n\f\nRFC 61 Interprocess Communication in a Computer Network July 1970\n\n Interprocess Communication\n in a\n Resource Sharing Computer Network\n\nINTRODUCTION\n\n \"A resource sharing computer network is defined to be a set of\n autonomous, independent computer systems, interconnected so as to\n permit each computer system to utilize all of the resources of each\n other computer system. That is, a program running in one computer\n system should be able to call on the resources of the other computer\n systems much as it would normally call a subroutine.\" This\n definition of a network and the de","scope_keywords":["0061","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0061 Network Working Group Dave Walden\nRequest for Comments: 61 Bolt Beranek and Newman\n July 17, 1970\n\n A Note on Interprocess Communication\n in a Resource Sharing Computer Network\n\n The attached note is a draft of a study I am still working on. It\n may be of general interest to network participants.\n\nWalden [Page 1]\n\f\nRFC 61 Interprocess Communication in a Computer Network July 1970\n\n Interprocess Communication\n in a\n Resource Sharing Computer Network\n\nINTRODUCTION\n\n \"A resource sharing computer network is defined to be a set of\n autonomous, independent computer systems, interconnected so as to\n permit each computer system to utilize all of the resources of each\n other computer system. That is, a program running in one computer\n system should be able to call on the resources of the other computer\n systems much as it would normally call a subroutine.\" This\n definition of a network and the de 0061 identification nested-reference unchanged"},{"id":"IETF RFC 0076","type":"specification","body":"IETF","designation":"RFC 0076","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0076.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0076.txt","https://www.rfc-editor.org/rfc/rfc0076.pdf"],"folder":"IETF/RFC-0076","files":{"txt":{"path":"standards/IETF/RFC-0076/RFC-0076.txt","sha256":"7639b0ed87d08a131618492c0cc6541dee2fe25816bb76f5d6d36497d6ff5ad2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Bouknight\nRequest for Comments: 76 J. Madden\nNIC 5180 G. Grossman\n University of Illinois\n 28 October 1970\n\n Connection-By-Name: User-Oriented Protocol\n\nI. Introduction\n\n Shortly after the first of the year, 1971, the Center for Advanced\n Computation (CAC) at the University of Illinois will begin to use the\n facilities of the ARPA network. We are the first of a small class of\n network nodes whose chief characteristic is that the node is a port\n to the network only. All computational power for these nodes will be\n taken from other nodes on the network, ILLIAC IV for example.\n\n An important characteristic of most of the users at our Center is a\n lack of sophistication about data communication techniques and\n practices. The user will eventually be in the majority of those\n using the network from all nodes but the problem is ours, almost from\n the start.\n\n In our dis","scope_keywords":["0076","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0076 Network Working Group J. Bouknight\nRequest for Comments: 76 J. Madden\nNIC 5180 G. Grossman\n University of Illinois\n 28 October 1970\n\n Connection-By-Name: User-Oriented Protocol\n\nI. Introduction\n\n Shortly after the first of the year, 1971, the Center for Advanced\n Computation (CAC) at the University of Illinois will begin to use the\n facilities of the ARPA network. We are the first of a small class of\n network nodes whose chief characteristic is that the node is a port\n to the network only. All computational power for these nodes will be\n taken from other nodes on the network, ILLIAC IV for example.\n\n An important characteristic of most of the users at our Center is a\n lack of sophistication about data communication techniques and\n practices. The user will eventually be in the majority of those\n using the network from all nodes but the problem is ours, almost from\n the start.\n\n In our dis 0076 key path nested-reference unchanged"},{"id":"IETF RFC 0097","type":"specification","body":"IETF","designation":"RFC 0097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0097.txt","https://www.rfc-editor.org/rfc/rfc0097.pdf"],"folder":"IETF/RFC-0097","files":{"pdf":{"path":"standards/IETF/RFC-0097/RFC-0097.pdf","sha256":"4713df56f2dc7a08a9729970bf1444f12c0bf28d2eaedf5f3802dd9f5e8bce06"},"txt":{"path":"standards/IETF/RFC-0097/RFC-0097.txt","sha256":"05546ee77c6e4daef960dc97d2f43bb3bf37df7cba7ffcc3b1355d13abbba339"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP NIC 5740\nRequest for Comments #97 John T. Melvin\n Richard W. Watson\n SRI-ARC\n 15 February 1971\n\n A FIRST CUT AT A PROPOSED TELNET PROTOCOL\n\n1 Introduction\n\n This paper describes a first cut at a proposed Telnet protocol.\n Telnet is a process which runs at a user's site and allows him\n to utilize a typewriter-like terminal to gain interactive service\n from a remote server _site over the ARPA Network. This paper was\n motivated by our need to set specifications for a protocol which\n would allow online access to the Network Information Center (NIC).\n The Online System running at the Network Information Center we will\n refer to as NLS(NIC). On thinking about the problem of setting\n specifications for access to the NIC, we have tried to generalize our\n ideas so that they would apply to other systems with characteristics\n similar to ours. We realize that there are other te","scope_keywords":["0097","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0097 NETWORK WORKING GROUP NIC 5740\nRequest for Comments #97 John T. Melvin\n Richard W. Watson\n SRI-ARC\n 15 February 1971\n\n A FIRST CUT AT A PROPOSED TELNET PROTOCOL\n\n1 Introduction\n\n This paper describes a first cut at a proposed Telnet protocol.\n Telnet is a process which runs at a user's site and allows him\n to utilize a typewriter-like terminal to gain interactive service\n from a remote server _site over the ARPA Network. This paper was\n motivated by our need to set specifications for a protocol which\n would allow online access to the Network Information Center (NIC).\n The Online System running at the Network Information Center we will\n refer to as NLS(NIC). On thinking about the problem of setting\n specifications for access to the NIC, we have tried to generalize our\n ideas so that they would apply to other systems with characteristics\n similar to ours. We realize that there are other te 0097 key keys subject nested-reference unchanged"},{"id":"IETF RFC 0137","type":"specification","body":"IETF","designation":"RFC 0137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0137.txt","https://www.rfc-editor.org/rfc/rfc0137.pdf"],"folder":"IETF/RFC-0137","files":{"txt":{"path":"standards/IETF/RFC-0137/RFC-0137.txt","sha256":"588758aa7a1370fe2d7ef65965e638c8147acfa0ae2b2e74b04ff36d2fc11753"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. C. O'Sullivan\nRequest for Comments: 137 Raytheon\nNIC 6714 30 April 1971\n\n TELNET Protocol\n\n This is a request for comment and is being distributed in advance of\n the Atlantic City meetings for review and comment prior to or during\n discussions on TELNET in preparation for issuing an official\n document.\n\n It is also being distributed so that selected installations planning\n to implement early versions of TELNET will have a common basis for\n such implementation.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation. A few recent suggestions by committee members and\n others have been incorporated where even though not thoroughly\n cleared with all members, the chairman felt that they clarified the\n protocol or would tend to simplify implementation but not\n substantially cha","scope_keywords":["0137","driving","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0137 Network Working Group T. C. O'Sullivan\nRequest for Comments: 137 Raytheon\nNIC 6714 30 April 1971\n\n TELNET Protocol\n\n This is a request for comment and is being distributed in advance of\n the Atlantic City meetings for review and comment prior to or during\n discussions on TELNET in preparation for issuing an official\n document.\n\n It is also being distributed so that selected installations planning\n to implement early versions of TELNET will have a common basis for\n such implementation.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation. A few recent suggestions by committee members and\n others have been incorporated where even though not thoroughly\n cleared with all members, the chairman felt that they clarified the\n protocol or would tend to simplify implementation but not\n substantially cha 0137 driving key presentation nested-reference unchanged"},{"id":"IETF RFC 0139","type":"specification","body":"IETF","designation":"RFC 0139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0139.txt","https://www.rfc-editor.org/rfc/rfc0139.pdf"],"folder":"IETF/RFC-0139","files":{"txt":{"path":"standards/IETF/RFC-0139/RFC-0139.txt","sha256":"9baf784906663285d6744e70e9cd7ac2b6205d426e8f357995e9e869f16aa238"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. O'Sullivan\nRequest for Comments: 139 Raytheon\nNIC: 6717 7 May 1971\n\n Discussion of TELNET Protocol\n\n The attached discussion is an extension of RFC 137, NIC #6717, and is\n presented to provide useful background to designers and implementers\n to help them interpret the proposed Protocol and evaluate it in\n preparation for further discussion at the Atlantic City meetings.\n\n While the views in the discussion represent those of various TELNET\n committee members, they should not be interpreted as being the agreed\n view of committee. They are the author's understanding of some of\n the arguments and background to the PROTOCOL proposed in the TELNET\n PROTOCOL recommendations.\n\n * See Footnotes to attached discussion for changes to RFC 137.\n\nDiscussion of TELNET PROTOCOL\n\n The use of a standard, network-wide, intermediate representation of\n terminal code between sites eli","scope_keywords":["0139","key","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0139 Network Working Group T. O'Sullivan\nRequest for Comments: 139 Raytheon\nNIC: 6717 7 May 1971\n\n Discussion of TELNET Protocol\n\n The attached discussion is an extension of RFC 137, NIC #6717, and is\n presented to provide useful background to designers and implementers\n to help them interpret the proposed Protocol and evaluate it in\n preparation for further discussion at the Atlantic City meetings.\n\n While the views in the discussion represent those of various TELNET\n committee members, they should not be interpreted as being the agreed\n view of committee. They are the author's understanding of some of\n the arguments and background to the PROTOCOL proposed in the TELNET\n PROTOCOL recommendations.\n\n * See Footnotes to attached discussion for changes to RFC 137.\n\nDiscussion of TELNET PROTOCOL\n\n The use of a standard, network-wide, intermediate representation of\n terminal code between sites eli 0139 key presentation subject nested-reference unchanged"},{"id":"IETF RFC 0318","type":"specification","body":"IETF","designation":"RFC 0318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0318.txt","https://www.rfc-editor.org/rfc/rfc0318.pdf"],"folder":"IETF/RFC-0318","files":{"txt":{"path":"standards/IETF/RFC-0318/RFC-0318.txt","sha256":"fd9d4e32ee2ab6d63b3c7ba0593662696d8cdf8fc817b799161a922972f362d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 318 UCLA-NMC\nNIC: 9348 April 3, 1972\nReferences: RFC 139, 158, and NIC 7104\n\n Telnet Protocol\n\n At the October 1971 Network Working Group Meeting, I promised to\n promptly produce a document which clearly and succinctly specified\n and explained the Official Telnet Protocol. This document fails to\n meet any part of that promise. This document was not produced\n promptly. This document is neither clear nor succinct. There is NO\n Official Telnet Protocol.\n\n The following pages present my understanding of the ad hoc Telnet\n protocol. There are some who have serious questions about this\n protocol. The proposed changes to the protocol are given in Section\n IV.\n\n Any comments should be promptly directed to me via the Network\n Information Center (Ident = JBP) or by phone (213) 825-2368 or by\n mail.\n\n Jon Postel\n SPADE Group\n 3804 Boelter Hall\n","scope_keywords":["0318","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0318 Network Working Group Jon Postel\nRequest for Comments: 318 UCLA-NMC\nNIC: 9348 April 3, 1972\nReferences: RFC 139, 158, and NIC 7104\n\n Telnet Protocol\n\n At the October 1971 Network Working Group Meeting, I promised to\n promptly produce a document which clearly and succinctly specified\n and explained the Official Telnet Protocol. This document fails to\n meet any part of that promise. This document was not produced\n promptly. This document is neither clear nor succinct. There is NO\n Official Telnet Protocol.\n\n The following pages present my understanding of the ad hoc Telnet\n protocol. There are some who have serious questions about this\n protocol. The proposed changes to the protocol are given in Section\n IV.\n\n Any comments should be promptly directed to me via the Network\n Information Center (Ident = JBP) or by phone (213) 825-2368 or by\n mail.\n\n Jon Postel\n SPADE Group\n 3804 Boelter Hall\n 0318 key keys presentation nested-reference unchanged"},{"id":"IETF RFC 0333","type":"specification","body":"IETF","designation":"RFC 0333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0333.txt","https://www.rfc-editor.org/rfc/rfc0333.pdf"],"folder":"IETF/RFC-0333","files":{"txt":{"path":"standards/IETF/RFC-0333/RFC-0333.txt","sha256":"9f1c6181729bb5c5160d0f2719828200c41f8321aa960a2666fb56e6a78a120d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bob Bressler\nRequest for Comments: 333 MIT/Dynamic Modeling\nNIC # 9926 Dan Murphy\nCategory: C9 (experimentation) BBN/TENEX\nObsoletes: 62 Dave Walden\nUpdates: none BBN/IMP\n 15 May 1972\n\n A PROPOSED EXPERIMENT WITH A MESSAGE SWITCHING PROTOCOL\n\nCONTENTS\n\n Introduction .................................................. 1\n Some Background ............................................... 2\n References .................................................... 3\n MSP Specification ............................................. 4\n Issue ......................................................... 8\n Message Header ................................................ 10\n Examples ...................................................... 15\n TELNET ........................................................ 16\n The Information Operator ...................................... 16\n Unique Port Numbe","scope_keywords":["0333"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0333 Network Working Group Bob Bressler\nRequest for Comments: 333 MIT/Dynamic Modeling\nNIC # 9926 Dan Murphy\nCategory: C9 (experimentation) BBN/TENEX\nObsoletes: 62 Dave Walden\nUpdates: none BBN/IMP\n 15 May 1972\n\n A PROPOSED EXPERIMENT WITH A MESSAGE SWITCHING PROTOCOL\n\nCONTENTS\n\n Introduction .................................................. 1\n Some Background ............................................... 2\n References .................................................... 3\n MSP Specification ............................................. 4\n Issue ......................................................... 8\n Message Header ................................................ 10\n Examples ...................................................... 15\n TELNET ........................................................ 16\n The Information Operator ...................................... 16\n Unique Port Numbe 0333 nested-reference unchanged"},{"id":"IETF RFC 0542","type":"specification","body":"IETF","designation":"RFC 0542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0542.txt","https://www.rfc-editor.org/rfc/rfc0542.pdf"],"folder":"IETF/RFC-0542","files":{"txt":{"path":"standards/IETF/RFC-0542/RFC-0542.txt","sha256":"845f120129b00549c7fa4630d057f32e6a2bf5378d6b809346af4f1d4fadc619"}},"tags":["nested-reference","unchanged"],"summary":"File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\nNancy J. Neigus See Also: RFCs 354, 454, 495\nBolt Beranek and Newman, Inc.\nCambridge, Mass.\n\n File Transfer Protocol for the ARPA Network\f\n\n File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\n PREFACE\n\nThis document is the result of several months discussion via RFC\n(relevant numbers are 430, 448, 454, 463, 468, 478, 480), followed by a\nmeeting of the FTP committee at BBN on March 16, followed by further\ncommunication among committee members. There are a considerable number\nof changes for the last \"official\" version, see RFCs 354, 385, but the\ngross structure remains the same. The places to look for differences\nare (1) in the definitions pf types and modes, (2) in the specification\nof the data connection and data sockets, (3) in the command-reply\nsequences, (4) in the functions dependent on the TELNET protocol (FTP\nhas ","scope_keywords":["0542","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0542 File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\nNancy J. Neigus See Also: RFCs 354, 454, 495\nBolt Beranek and Newman, Inc.\nCambridge, Mass.\n\n File Transfer Protocol for the ARPA Network\f\n\n File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\n PREFACE\n\nThis document is the result of several months discussion via RFC\n(relevant numbers are 430, 448, 454, 463, 468, 478, 480), followed by a\nmeeting of the FTP committee at BBN on March 16, followed by further\ncommunication among committee members. There are a considerable number\nof changes for the last \"official\" version, see RFCs 354, 385, but the\ngross structure remains the same. The places to look for differences\nare (1) in the definitions pf types and modes, (2) in the specification\nof the data connection and data sockets, (3) in the command-reply\nsequences, (4) in the functions dependent on the TELNET protocol (FTP\nhas  0542 path nested-reference unchanged"},{"id":"IETF RFC 0698","type":"specification","body":"IETF","designation":"RFC 0698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0698.txt","https://www.rfc-editor.org/rfc/rfc0698.pdf"],"folder":"IETF/RFC-0698","files":{"txt":{"path":"standards/IETF/RFC-0698/RFC-0698.txt","sha256":"a67d173ac8a5807983f9396ad1f67d0e65f082b08e74b849299c5feb2945c85f"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 698 Jul 1975\nNIC #32964\n\n TELNET EXTENDED ASCII OPTION\n\n1. Command Name and Code.\n\nEXTEND-ASCII 17\n\n2. Command Meanings.\n\nIAC WILL EXTEND-ASCII\n\nThe sender of this command requests Permission to begin\ntransmitting, or confirms that it may now begin transmitting\nextended ASCII, where additional 'control' bits are added to\nnormal ASCII, which are treated sPecially by certain programs on\nthe host computer.\n\nIAC WON'T EXTEND-ASCII\n\nIf the connection is already being operated in extended ASCII\nmode, the sender of this command demands that the receiver begin\ntransmitting data characters in standard NVT ASCII. If the\nconnection is not already being operated in extended ASCII mode,\nThe sender of this command refuses to begin transmitting extended\nASCII.\n\nIAC DO EXTEND-ASCII\n\nThe sender of this command requests that the receiver begin\ntransmitting,or confirms that the receiv","scope_keywords":["0698","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0698 Request for Comments: 698 Jul 1975\nNIC #32964\n\n TELNET EXTENDED ASCII OPTION\n\n1. Command Name and Code.\n\nEXTEND-ASCII 17\n\n2. Command Meanings.\n\nIAC WILL EXTEND-ASCII\n\nThe sender of this command requests Permission to begin\ntransmitting, or confirms that it may now begin transmitting\nextended ASCII, where additional 'control' bits are added to\nnormal ASCII, which are treated sPecially by certain programs on\nthe host computer.\n\nIAC WON'T EXTEND-ASCII\n\nIf the connection is already being operated in extended ASCII\nmode, the sender of this command demands that the receiver begin\ntransmitting data characters in standard NVT ASCII. If the\nconnection is not already being operated in extended ASCII mode,\nThe sender of this command refuses to begin transmitting extended\nASCII.\n\nIAC DO EXTEND-ASCII\n\nThe sender of this command requests that the receiver begin\ntransmitting,or confirms that the receiv 0698 key nested-reference unchanged"},{"id":"IETF RFC 0713","type":"specification","body":"IETF","designation":"RFC 0713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0713.txt","https://www.rfc-editor.org/rfc/rfc0713.pdf"],"folder":"IETF/RFC-0713","files":{"txt":{"path":"standards/IETF/RFC-0713/RFC-0713.txt","sha256":"2c7ec7fe46e6a83ee7613410d28e9052ccbfa4da0f0dad58e965325f038bdaea"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 713 Jack Haverty (JFH@MIT-DMS)\nNIC #34739 Apr 1976\n\nI. ABSTRACT\n\nA mechanism is defined for use by message servers in\ntransferring data between hosts. The mechanism, called the\nMSDTP, is defined in terms of a model of the process as a\ntranslation between two sets of items, the abstract entities\nsuch as 'strings' and 'integers', and the formats used to\nrepresent such data as a byte stream.\n\nA proposed organization of a general data transfer\nmechanism is described, and the manner in which the MSDTP\nwould be used in that environment is presented.\n\n -1-\f\n\nII. REFERENCES\n\nBlack, Edward H., \"The DMS Message Composer\", MIT Project\nMAC, Programming Technology Division Document\nSYS.16.02.\n\nBurchfiel, Jerry D., Leavitt, Elsie M., Shapiro, Sonya and\nStrollo, Theodore R., compilers, \"Tenex Users' Guide\",\nBolt Beranek and Newman, Cambridge, Mass., May 1971,\nrevised January 1975,","scope_keywords":["0713","holder","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 0713 Request for Comments: 713 Jack Haverty (JFH@MIT-DMS)\nNIC #34739 Apr 1976\n\nI. ABSTRACT\n\nA mechanism is defined for use by message servers in\ntransferring data between hosts. The mechanism, called the\nMSDTP, is defined in terms of a model of the process as a\ntranslation between two sets of items, the abstract entities\nsuch as 'strings' and 'integers', and the formats used to\nrepresent such data as a byte stream.\n\nA proposed organization of a general data transfer\nmechanism is described, and the manner in which the MSDTP\nwould be used in that environment is presented.\n\n -1-\f\n\nII. REFERENCES\n\nBlack, Edward H., \"The DMS Message Composer\", MIT Project\nMAC, Programming Technology Division Document\nSYS.16.02.\n\nBurchfiel, Jerry D., Leavitt, Elsie M., Shapiro, Sonya and\nStrollo, Theodore R., compilers, \"Tenex Users' Guide\",\nBolt Beranek and Newman, Cambridge, Mass., May 1971,\nrevised January 1975, 0713 holder presentation risk nested-reference unchanged"},{"id":"IETF RFC 6256","type":"specification","body":"IETF","designation":"RFC 6256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6256.txt","https://www.rfc-editor.org/rfc/rfc6256.pdf"],"folder":"IETF/RFC-6256","files":{"txt":{"path":"standards/IETF/RFC-6256/RFC-6256.txt","sha256":"ccaa2301b0031cc34e9c92f4c4648f135a977a0b0f87d38b394392bc5ab9a19b"}},"tags":["nested-reference","unchanged"],"summary":"Self-Delimiting Numeric Values (SDNVs) have recently been introduced\n as a field type in proposed Delay-Tolerant Networking protocols.\n SDNVs encode an arbitrary-length non-negative integer or arbitrary-\n length bitstring with minimum overhead. They are intended to provide\n protocol flexibility without sacrificing economy and to assist in\n future-proofing protocols under development. This document describes\n formats and algorithms for SDNV encoding and decoding, along with\n notes on implementation and usage. This document is a product of the\n Delay-Tolerant Networking Research Group and has been reviewed by\n that group. No objections to its publication as an RFC were raised.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF p","scope_keywords":["6256","algorithm","algorithms","http","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null}],"search_text":"IETF RFC 6256 Self-Delimiting Numeric Values (SDNVs) have recently been introduced\n as a field type in proposed Delay-Tolerant Networking protocols.\n SDNVs encode an arbitrary-length non-negative integer or arbitrary-\n length bitstring with minimum overhead. They are intended to provide\n protocol flexibility without sacrificing economy and to assist in\n future-proofing protocols under development. This document describes\n formats and algorithms for SDNV encoding and decoding, along with\n notes on implementation and usage. This document is a product of the\n Delay-Tolerant Networking Research Group and has been reviewed by\n that group. No objections to its publication as an RFC were raised.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF p 6256 algorithm algorithms http license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 0733","type":"specification","body":"IETF","designation":"RFC 0733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0733.txt","https://www.rfc-editor.org/rfc/rfc0733.pdf"],"folder":"IETF/RFC-0733","files":{"txt":{"path":"standards/IETF/RFC-0733/RFC-0733.txt","sha256":"07de5642a57636a027cf33346775baf7b19e5075888995f5440c46d3f01bf371"}},"tags":["nested-reference","unchanged"],"summary":"RFC # 733\nNIC # 41952\n\nObsoletes: RFC #561 (NIC #18516)\n RFC #680 (NIC #32116)\n RFC #724 (NIC #37435)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA NETWORK TEXT MESSAGES(1)\n\n 21 November 1977\n\n by\n\n David H. Crocker\n The Rand Corporation\n\n John J. Vittal\n Bolt Beranek and Newman Inc.\n\n Kenneth T. Pogran\n Massachusets Institute of Technology\n\n D. Austin Henderson, Jr.(2)\n Bolt Beranek and Newman Inc.\n\n_________________________________________________________________\n(1)This work was supported by the Defense Advanced Research\nProjects Agency of the Department of Defense, under contract Nos.\nN00014-75-C-0661, MDA903-76-C-0212, and DAHC15-73-C0181.\n\n(2)The authors' postal addresses are: D. Crocker, The Rand\nCorporation, Information Sciences Dept., 1700 Main St., Santa\nMonica, California 90406; J. Vittal & D. A. Henderson, Bolt\nBeranek & Newman, 50 Moulton St., Cambridge, Massachusetts 02138;\nand K. Po","scope_keywords":["0733"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 0733 RFC # 733\nNIC # 41952\n\nObsoletes: RFC #561 (NIC #18516)\n RFC #680 (NIC #32116)\n RFC #724 (NIC #37435)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA NETWORK TEXT MESSAGES(1)\n\n 21 November 1977\n\n by\n\n David H. Crocker\n The Rand Corporation\n\n John J. Vittal\n Bolt Beranek and Newman Inc.\n\n Kenneth T. Pogran\n Massachusets Institute of Technology\n\n D. Austin Henderson, Jr.(2)\n Bolt Beranek and Newman Inc.\n\n_________________________________________________________________\n(1)This work was supported by the Defense Advanced Research\nProjects Agency of the Department of Defense, under contract Nos.\nN00014-75-C-0661, MDA903-76-C-0212, and DAHC15-73-C0181.\n\n(2)The authors' postal addresses are: D. Crocker, The Rand\nCorporation, Information Sciences Dept., 1700 Main St., Santa\nMonica, California 90406; J. Vittal & D. A. Henderson, Bolt\nBeranek & Newman, 50 Moulton St., Cambridge, Massachusetts 02138;\nand K. Po 0733 nested-reference unchanged"},{"id":"IETF RFC 5598","type":"specification","body":"IETF","designation":"RFC 5598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5598.txt","https://www.rfc-editor.org/rfc/rfc5598.pdf"],"folder":"IETF/RFC-5598","files":{"pdf":{"path":"standards/IETF/RFC-5598/RFC-5598.pdf","sha256":"9f4dbed1b7c4dfe4992d74f40445ae6155036937b8f69174d29489b6a2163b55"},"txt":{"path":"standards/IETF/RFC-5598/RFC-5598.txt","sha256":"80702e8e4da554bac8270af89fbf01ca35f43957b659afc475e4b9e3fcc3f87c"}},"tags":["nested-reference","unchanged"],"summary":"Over its thirty-five-year history, Internet Mail has changed\n significantly in scale and complexity, as it has become a global\n infrastructure service. These changes have been evolutionary, rather\n than revolutionary, reflecting a strong desire to preserve both its\n installed base and its usefulness. To collaborate productively on\n this large and complex system, all participants need to work from a\n common view of it and use a common language to describe its\n components and the interactions among them. But the many differences\n in perspective currently make it difficult to know exactly what\n another participant means. To serve as the necessary common frame of\n reference, this document describes the enhanced Internet Mail\n architecture, reflecting the current service.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standar","scope_keywords":["5598","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null}],"search_text":"IETF RFC 5598 Over its thirty-five-year history, Internet Mail has changed\n significantly in scale and complexity, as it has become a global\n infrastructure service. These changes have been evolutionary, rather\n than revolutionary, reflecting a strong desire to preserve both its\n installed base and its usefulness. To collaborate productively on\n this large and complex system, all participants need to work from a\n common view of it and use a common language to describe its\n components and the interactions among them. But the many differences\n in perspective currently make it difficult to know exactly what\n another participant means. To serve as the necessary common frame of\n reference, this document describes the enhanced Internet Mail\n architecture, reflecting the current service.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standar 5598 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 0739","type":"specification","body":"IETF","designation":"RFC 0739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0739.txt","https://www.rfc-editor.org/rfc/rfc0739.pdf"],"folder":"IETF/RFC-0739","files":{"txt":{"path":"standards/IETF/RFC-0739/RFC-0739.txt","sha256":"8a08315f70b9a9c7735c57390e76522379c300790c29c691cf4605f36b815a93"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 739 JBP 11 Nov 77 42341\nAssigned Numbers\n\nNetwork Working Group J. Postel\nRequest for Comments: 739 USC-ISI\nNIC: 42341 11 November 1977\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent and more g","scope_keywords":["0739","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0739 NWG/RFC# 739 JBP 11 Nov 77 42341\nAssigned Numbers\n\nNetwork Working Group J. Postel\nRequest for Comments: 739 USC-ISI\nNIC: 42341 11 November 1977\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent and more g 0739 authentication nested-reference unchanged"},{"id":"IETF RFC 0742","type":"specification","body":"IETF","designation":"RFC 0742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0742.txt","https://www.rfc-editor.org/rfc/rfc0742.pdf"],"folder":"IETF/RFC-0742","files":{"txt":{"path":"standards/IETF/RFC-0742/RFC-0742.txt","sha256":"e242fb7222329d4015b148a30bb4d7eeaf96e0aaa06452cd3169dba9201a016f"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 742 KLH 30-Dec-77 08:31 42758\nNetwork Working Group K. Harrenstien\nRequest for Comments: 742 SRI-KL\nNIC: 42758 30 December 1977\n\n NAME/FINGER\n\nIntroduction\n\n This note describes the Name/Finger protocol. This is a simple\n protocol which provides an interface to the Name and Finger programs\n at several network sites. These programs return a friendly,\n human-oriented status report on either the system at the moment or a\n particular person in depth. Currently only the SAIL (SU-AI), SRI\n (SRI-(KA/KL)), and ITS (MIT-(AI/ML/MC/DMS)) sites support this\n protocol, but there are other systems with similar programs that\n could easily be made servers; there is no required format and the\n protocol consists mostly of specifying a single \"command line\".\n\nTo use via the network:\n\n ICP to socket 117 (octal, 79. decimal) and establish two 8-bit\n connections.\n\n Send a single \"command line\", endin","scope_keywords":["0742","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0742 NWG/RFC# 742 KLH 30-Dec-77 08:31 42758\nNetwork Working Group K. Harrenstien\nRequest for Comments: 742 SRI-KL\nNIC: 42758 30 December 1977\n\n NAME/FINGER\n\nIntroduction\n\n This note describes the Name/Finger protocol. This is a simple\n protocol which provides an interface to the Name and Finger programs\n at several network sites. These programs return a friendly,\n human-oriented status report on either the system at the moment or a\n particular person in depth. Currently only the SAIL (SU-AI), SRI\n (SRI-(KA/KL)), and ITS (MIT-(AI/ML/MC/DMS)) sites support this\n protocol, but there are other systems with similar programs that\n could easily be made servers; there is no required format and the\n protocol consists mostly of specifying a single \"command line\".\n\nTo use via the network:\n\n ICP to socket 117 (octal, 79. decimal) and establish two 8-bit\n connections.\n\n Send a single \"command line\", endin 0742 crl nested-reference unchanged"},{"id":"IETF RFC 0758","type":"specification","body":"IETF","designation":"RFC 0758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0758.txt","https://www.rfc-editor.org/rfc/rfc0758.pdf"],"folder":"IETF/RFC-0758","files":{"txt":{"path":"standards/IETF/RFC-0758/RFC-0758.txt","sha256":"fd65a2580ca5d087a0155c016419f5bd7f8a29222e2caff7df6bf65942499e4e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 758 USC-ISI\nIEN: 117 August 1979\n\nObsoletes RFCs: 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent","scope_keywords":["0758"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0758 Network Working Group J. Postel\nRequest for Comments: 758 USC-ISI\nIEN: 117 August 1979\n\nObsoletes RFCs: 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent 0758 nested-reference unchanged"},{"id":"IETF RFC 0768","type":"specification","body":"IETF","designation":"RFC 0768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0768.txt","https://www.rfc-editor.org/rfc/rfc0768.pdf"],"folder":"IETF/RFC-0768","files":{"txt":{"path":"standards/IETF/RFC-0768/RFC-0768.txt","sha256":"7dc8880e1ecef9c3f9da0db4b876a16e96bfa4f0953cc9d977d414f8f680c2f0"}},"tags":["nested-reference","unchanged"],"summary":"RFC 768 J. Postel\n ISI\n 28 August 1980\n\n User Datagram Protocol\n ----------------------\n\nIntroduction\n------------\n\nThis User Datagram Protocol (UDP) is defined to make available a\ndatagram mode of packet-switched computer communication in the\nenvironment of an interconnected set of computer networks. This\nprotocol assumes that the Internet Protocol (IP) [1] is used as the\nunderlying protocol.\n\nThis protocol provides a procedure for application programs to send\nmessages to other programs with a minimum of protocol mechanism. The\nprotocol is transaction oriented, and delivery and duplicate protection\nare not guaranteed. Applications requiring ordered reliable delivery of\nstreams of data should use the Transmission Control Protocol (TCP) [2].\n\nFormat\n------\n\n \n 0 7 8 15 16 23 24 31 \n +--------+--------+--------+--------+ \n | Source | Destination | \n | Port | Port | \n +--------+--------+---","scope_keywords":["0768","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 0768 RFC 768 J. Postel\n ISI\n 28 August 1980\n\n User Datagram Protocol\n ----------------------\n\nIntroduction\n------------\n\nThis User Datagram Protocol (UDP) is defined to make available a\ndatagram mode of packet-switched computer communication in the\nenvironment of an interconnected set of computer networks. This\nprotocol assumes that the Internet Protocol (IP) [1] is used as the\nunderlying protocol.\n\nThis protocol provides a procedure for application programs to send\nmessages to other programs with a minimum of protocol mechanism. The\nprotocol is transaction oriented, and delivery and duplicate protection\nare not guaranteed. Applications requiring ordered reliable delivery of\nstreams of data should use the Transmission Control Protocol (TCP) [2].\n\nFormat\n------\n\n \n 0 7 8 15 16 23 24 31 \n +--------+--------+--------+--------+ \n | Source | Destination | \n | Port | Port | \n +--------+--------+--- 0768 delivery nested-reference unchanged"},{"id":"IETF RFC 3948","type":"specification","body":"IETF","designation":"RFC 3948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3948.txt","https://www.rfc-editor.org/rfc/rfc3948.pdf"],"folder":"IETF/RFC-3948","files":{"txt":{"path":"standards/IETF/RFC-3948/RFC-3948.txt","sha256":"e37df55098e76e53dc15d681da342a077759f480f953370bff50cf2bba87123c"}},"tags":["nested-reference","unchanged"],"summary":"This protocol specification defines methods to encapsulate and\n decapsulate IP Encapsulating Security Payload (ESP) packets inside\n UDP packets for traversing Network Address Translators. ESP\n encapsulation, as defined in this document, can be used in both IPv4\n and IPv6 scenarios. Whenever negotiated, encapsulation is used with\n Internet Key Exchange (IKE).\n\nHuttunen, et al. Standards Track [Page 1]\n\f\nRFC 3948 UDP Encapsulation of IPsec ESP Packets January 2005","scope_keywords":["3948","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 3948 This protocol specification defines methods to encapsulate and\n decapsulate IP Encapsulating Security Payload (ESP) packets inside\n UDP packets for traversing Network Address Translators. ESP\n encapsulation, as defined in this document, can be used in both IPv4\n and IPv6 scenarios. Whenever negotiated, encapsulation is used with\n Internet Key Exchange (IKE).\n\nHuttunen, et al. Standards Track [Page 1]\n\f\nRFC 3948 UDP Encapsulation of IPsec ESP Packets January 2005 3948 key nested-reference unchanged"},{"id":"IETF RFC 4113","type":"specification","body":"IETF","designation":"RFC 4113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4113.txt","https://www.rfc-editor.org/rfc/rfc4113.pdf"],"folder":"IETF/RFC-4113","files":{"txt":{"path":"standards/IETF/RFC-4113/RFC-4113.txt","sha256":"8387ccefd510e102ccfe0918d1d9572d294afe002710f1d09ff4d5354cc83218"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the User Datagram Protocol (UDP) in an IP version independent\n manner. This memo obsoletes RFCs 2013 and 2454.","scope_keywords":["4113","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null}],"search_text":"IETF RFC 4113 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the User Datagram Protocol (UDP) in an IP version independent\n manner. This memo obsoletes RFCs 2013 and 2454. 4113 identification management nested-reference unchanged"},{"id":"IETF RFC 4787","type":"specification","body":"IETF","designation":"RFC 4787","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4787.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4787.txt","https://www.rfc-editor.org/rfc/rfc4787.pdf"],"folder":"IETF/RFC-4787","files":{"txt":{"path":"standards/IETF/RFC-4787/RFC-4787.txt","sha256":"5db82ec5f0d6b9b0fc0a37ce7d5b40592e4e6f41562ba8fbc55f1daa52648405"}},"tags":["nested-reference","unchanged"],"summary":"This document defines basic terminology for describing different\n types of Network Address Translation (NAT) behavior when handling\n Unicast UDP and also defines a set of requirements that would allow\n many applications, such as multimedia communications or online\n gaming, to work consistently. Developing NATs that meet this set of\n requirements will greatly increase the likelihood that these\n applications will function properly.\n\nAudet & Jennings Best Current Practice [Page 1]\n\f\nRFC 4787 NAT UDP Unicast Requirements January 2007","scope_keywords":["4787","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 4787 This document defines basic terminology for describing different\n types of Network Address Translation (NAT) behavior when handling\n Unicast UDP and also defines a set of requirements that would allow\n many applications, such as multimedia communications or online\n gaming, to work consistently. Developing NATs that meet this set of\n requirements will greatly increase the likelihood that these\n applications will function properly.\n\nAudet & Jennings Best Current Practice [Page 1]\n\f\nRFC 4787 NAT UDP Unicast Requirements January 2007 4787 key trust nested-reference unchanged"},{"id":"IETF RFC 4960","type":"specification","body":"IETF","designation":"RFC 4960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4960.txt","https://www.rfc-editor.org/rfc/rfc4960.pdf"],"folder":"IETF/RFC-4960","files":{"txt":{"path":"standards/IETF/RFC-4960/RFC-4960.txt","sha256":"b99873dae5a67ed1ab8b4f552ef86afbc8783745560130bdbe0efa7c07c76a6c"}},"tags":["nested-reference","unchanged"],"summary":"This document obsoletes RFC 2960 and RFC 3309. It describes the\n Stream Control Transmission Protocol (SCTP). SCTP is designed to\n transport Public Switched Telephone Network (PSTN) signaling messages\n over IP networks, but is capable of broader applications.\n\n SCTP is a reliable transport protocol operating on top of a\n connectionless packet network such as IP. It offers the following\n services to its users:\n\n -- acknowledged error-free non-duplicated transfer of user data,\n\n -- data fragmentation to conform to discovered path MTU size,\n\n -- sequenced delivery of user messages within multiple streams, with\n an option for order-of-arrival delivery of individual user\n messages,\n\n -- optional bundling of multiple user messages into a single SCTP\n packet, and\n\n -- network-level fault tolerance through supporting of multi-homing\n at either or both ends of an association.\n\n The design of SCTP","scope_keywords":["4960","authentication","delivery","key","management","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6737","folder":"IETF/RFC-6737","source":"IETF/RFC-6737/RFC-6737.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 4960 This document obsoletes RFC 2960 and RFC 3309. It describes the\n Stream Control Transmission Protocol (SCTP). SCTP is designed to\n transport Public Switched Telephone Network (PSTN) signaling messages\n over IP networks, but is capable of broader applications.\n\n SCTP is a reliable transport protocol operating on top of a\n connectionless packet network such as IP. It offers the following\n services to its users:\n\n -- acknowledged error-free non-duplicated transfer of user data,\n\n -- data fragmentation to conform to discovered path MTU size,\n\n -- sequenced delivery of user messages within multiple streams, with\n an option for order-of-arrival delivery of individual user\n messages,\n\n -- optional bundling of multiple user messages into a single SCTP\n packet, and\n\n -- network-level fault tolerance through supporting of multi-homing\n at either or both ends of an association.\n\n The design of SCTP 4960 authentication delivery key management path validation nested-reference unchanged"},{"id":"IETF RFC 5201","type":"specification","body":"IETF","designation":"RFC 5201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5201.txt","https://www.rfc-editor.org/rfc/rfc5201.pdf"],"folder":"IETF/RFC-5201","files":{"txt":{"path":"standards/IETF/RFC-5201/RFC-5201.txt","sha256":"8b42d181a8e239713eb8d608c11e8e75829561d994adbd3caa96c6db6e69cef6"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies the details of the Host Identity Protocol (HIP).\n HIP allows consenting hosts to securely establish and maintain shared\n IP-layer state, allowing separation of the identifier and locator\n roles of IP addresses, thereby enabling continuity of communications\n across IP address changes. HIP is based on a Sigma-compliant Diffie-\n Hellman key exchange, using public key identifiers from a new Host\n Identity namespace for mutual peer authentication. The protocol is\n designed to be resistant to denial-of-service (DoS) and man-in-the-\n middle (MitM) attacks. When used together with another suitable\n security protocol, such as the Encapsulated Security Payload (ESP),\n it provides integrity protection and optional encryption for upper-\n layer protocols, such as TCP and UDP.","scope_keywords":["5201","algorithm","algorithms","authentication","certificate","encryption","hash","hashing","key","policies","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5338","folder":"IETF/RFC-5338","source":"IETF/RFC-5338/RFC-5338.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null}],"search_text":"IETF RFC 5201 This memo specifies the details of the Host Identity Protocol (HIP).\n HIP allows consenting hosts to securely establish and maintain shared\n IP-layer state, allowing separation of the identifier and locator\n roles of IP addresses, thereby enabling continuity of communications\n across IP address changes. HIP is based on a Sigma-compliant Diffie-\n Hellman key exchange, using public key identifiers from a new Host\n Identity namespace for mutual peer authentication. The protocol is\n designed to be resistant to denial-of-service (DoS) and man-in-the-\n middle (MitM) attacks. When used together with another suitable\n security protocol, such as the Encapsulated Security Payload (ESP),\n it provides integrity protection and optional encryption for upper-\n layer protocols, such as TCP and UDP. 5201 algorithm algorithms authentication certificate encryption hash hashing key policies presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 5225","type":"specification","body":"IETF","designation":"RFC 5225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5225.txt","https://www.rfc-editor.org/rfc/rfc5225.pdf"],"folder":"IETF/RFC-5225","files":{"txt":{"path":"standards/IETF/RFC-5225/RFC-5225.txt","sha256":"3f53b6cbb4967946a610d34e82933a9d15f444314253d8cfa88e91f47900a658"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies ROHC (Robust Header Compression) profiles\n that efficiently compress RTP/UDP/IP (Real-Time Transport Protocol,\n User Datagram Protocol, Internet Protocol), RTP/UDP-Lite/IP (User\n Datagram Protocol Lite), UDP/IP, UDP-Lite/IP, IP and ESP/IP\n (Encapsulating Security Payload) headers.\n\n This specification defines a second version of the profiles found in\n RFC 3095, RFC 3843 and RFC 4019; it supersedes their definition, but\n does not obsolete them.\n\n The ROHCv2 profiles introduce a number of simplifications to the\n rules and algorithms that govern the behavior of the compression\n endpoints. It also defines robustness mechanisms that may be used by\n a compressor implementation to increase the probability of\n decompression success when packets can be lost and/or reordered on\n the ROHC channel. Finally, the ROHCv2 profiles define their own\n specific set of header formats,","scope_keywords":["5225","algorithm","algorithms","management","profile","profiles","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null}],"search_text":"IETF RFC 5225 This document specifies ROHC (Robust Header Compression) profiles\n that efficiently compress RTP/UDP/IP (Real-Time Transport Protocol,\n User Datagram Protocol, Internet Protocol), RTP/UDP-Lite/IP (User\n Datagram Protocol Lite), UDP/IP, UDP-Lite/IP, IP and ESP/IP\n (Encapsulating Security Payload) headers.\n\n This specification defines a second version of the profiles found in\n RFC 3095, RFC 3843 and RFC 4019; it supersedes their definition, but\n does not obsolete them.\n\n The ROHCv2 profiles introduce a number of simplifications to the\n rules and algorithms that govern the behavior of the compression\n endpoints. It also defines robustness mechanisms that may be used by\n a compressor implementation to increase the probability of\n decompression success when packets can be lost and/or reordered on\n the ROHC channel. Finally, the ROHCv2 profiles define their own\n specific set of header formats, 5225 algorithm algorithms management profile profiles timestamp nested-reference unchanged"},{"id":"IETF RFC 5405","type":"specification","body":"IETF","designation":"RFC 5405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5405.txt","https://www.rfc-editor.org/rfc/rfc5405.pdf"],"folder":"IETF/RFC-5405","files":{"txt":{"path":"standards/IETF/RFC-5405/RFC-5405.txt","sha256":"e45b9858477ef79583c914782f5e877ca099b1474ab93499146cd9108860ac8a"}},"tags":["nested-reference","unchanged"],"summary":"The User Datagram Protocol (UDP) provides a minimal message-passing\n transport that has no inherent congestion control mechanisms.\n Because congestion control is critical to the stable operation of the\n Internet, applications and upper-layer protocols that choose to use\n UDP as an Internet transport must employ mechanisms to prevent\n congestion collapse and to establish some degree of fairness with\n concurrent traffic. This document provides guidelines on the use of\n UDP for the designers of unicast applications and upper-layer\n protocols. Congestion control guidelines are a primary focus, but\n the document also provides guidance on other topics, including\n message sizes, reliability, checksums, and middlebox traversal.\n\nEggert & Fairhurst Best Current Practice [Page 1]\n\f\nRFC 5405 Unicast UDP Usage Guidelines November 2008","scope_keywords":["5405","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5405 The User Datagram Protocol (UDP) provides a minimal message-passing\n transport that has no inherent congestion control mechanisms.\n Because congestion control is critical to the stable operation of the\n Internet, applications and upper-layer protocols that choose to use\n UDP as an Internet transport must employ mechanisms to prevent\n congestion collapse and to establish some degree of fairness with\n concurrent traffic. This document provides guidelines on the use of\n UDP for the designers of unicast applications and upper-layer\n protocols. Congestion control guidelines are a primary focus, but\n the document also provides guidance on other topics, including\n message sizes, reliability, checksums, and middlebox traversal.\n\nEggert & Fairhurst Best Current Practice [Page 1]\n\f\nRFC 5405 Unicast UDP Usage Guidelines November 2008 5405 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5474","type":"specification","body":"IETF","designation":"RFC 5474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5474.txt","https://www.rfc-editor.org/rfc/rfc5474.pdf"],"folder":"IETF/RFC-5474","files":{"txt":{"path":"standards/IETF/RFC-5474/RFC-5474.txt","sha256":"8e25061535af23e8bf58b93ae3592aa5b5f57fc1db55e3b1a76931aee33e13f4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a framework for the PSAMP (Packet SAMPling)\n protocol. The functions of this protocol are to select packets from\n a stream according to a set of standardized Selectors, to form a\n stream of reports on the selected packets, and to export the reports\n to a Collector. This framework details the components of this\n architecture, then describes some generic requirements, motivated by\n the dual aims of ubiquitous deployment and utility of the reports for\n applications. Detailed requirements for selection, reporting, and\n exporting are described, along with configuration requirements of the\n PSAMP functions.","scope_keywords":["5474","hash","hashing","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 5474 This document specifies a framework for the PSAMP (Packet SAMPling)\n protocol. The functions of this protocol are to select packets from\n a stream according to a set of standardized Selectors, to form a\n stream of reports on the selected packets, and to export the reports\n to a Collector. This framework details the components of this\n architecture, then describes some generic requirements, motivated by\n the dual aims of ubiquitous deployment and utility of the reports for\n applications. Detailed requirements for selection, reporting, and\n exporting are described, along with configuration requirements of the\n PSAMP functions. 5474 hash hashing http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5531","type":"specification","body":"IETF","designation":"RFC 5531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5531.txt","https://www.rfc-editor.org/rfc/rfc5531.pdf"],"folder":"IETF/RFC-5531","files":{"txt":{"path":"standards/IETF/RFC-5531/RFC-5531.txt","sha256":"c1e2e05640c66c504871f3591311355a1bc432f75bd481b4ead8332a4fe351ae"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Open Network Computing (ONC) Remote\n Procedure Call (RPC) version 2 protocol as it is currently deployed\n and accepted. This document obsoletes RFC 1831.\n\nThurlow Standards Track [Page 1]\n\f\nRFC 5531 Remote Procedure Call Protocol Version 2 May 2009","scope_keywords":["5531","authentication","http","key","license","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 5531 This document describes the Open Network Computing (ONC) Remote\n Procedure Call (RPC) version 2 protocol as it is currently deployed\n and accepted. This document obsoletes RFC 1831.\n\nThurlow Standards Track [Page 1]\n\f\nRFC 5531 Remote Procedure Call Protocol Version 2 May 2009 5531 authentication http key license policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5626","type":"specification","body":"IETF","designation":"RFC 5626","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5626.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5626.txt","https://www.rfc-editor.org/rfc/rfc5626.pdf"],"folder":"IETF/RFC-5626","files":{"txt":{"path":"standards/IETF/RFC-5626/RFC-5626.txt","sha256":"43ed8a697b3291da4822ab3f7bb4b58d26e6c49dd7b25fe44bee02aa72050e49"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) allows proxy servers to\n initiate TCP connections or to send asynchronous UDP datagrams to\n User Agents in order to deliver requests. However, in a large number\n of real deployments, many practical considerations, such as the\n existence of firewalls and Network Address Translators (NATs) or the\n use of TLS with server-provided certificates, prevent servers from\n connecting to User Agents in this way. This specification defines\n behaviors for User Agents, registrars, and proxy servers that allow\n requests to be delivered on existing connections established by the\n User Agent. It also defines keep-alive behaviors needed to keep NAT\n bindings open and specifies the usage of multiple connections from\n the User Agent to its registrar.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and reque","scope_keywords":["5626","certificate","certificates","crl","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 5626 The Session Initiation Protocol (SIP) allows proxy servers to\n initiate TCP connections or to send asynchronous UDP datagrams to\n User Agents in order to deliver requests. However, in a large number\n of real deployments, many practical considerations, such as the\n existence of firewalls and Network Address Translators (NATs) or the\n use of TLS with server-provided certificates, prevent servers from\n connecting to User Agents in this way. This specification defines\n behaviors for User Agents, registrars, and proxy servers that allow\n requests to be delivered on existing connections established by the\n User Agent. It also defines keep-alive behaviors needed to keep NAT\n bindings open and specifies the usage of multiple connections from\n the User Agent to its registrar.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and reque 5626 certificate certificates crl http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5651","type":"specification","body":"IETF","designation":"RFC 5651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5651.txt","https://www.rfc-editor.org/rfc/rfc5651.pdf"],"folder":"IETF/RFC-5651","files":{"txt":{"path":"standards/IETF/RFC-5651/RFC-5651.txt","sha256":"884727c908d25cc6c22b56cefe138f1a556adc70634f4a573e1c03a748168ab1"}},"tags":["nested-reference","unchanged"],"summary":"The Layered Coding Transport (LCT) Building Block provides transport\n level support for reliable content delivery and stream delivery\n protocols. LCT is specifically designed to support protocols using\n IP multicast, but it also provides support to protocols that use\n unicast. LCT is compatible with congestion control that provides\n multiple rate delivery to receivers and is also compatible with\n coding techniques that provide reliable delivery of content. This\n document obsoletes RFC 3451.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IE","scope_keywords":["5651","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 5651 The Layered Coding Transport (LCT) Building Block provides transport\n level support for reliable content delivery and stream delivery\n protocols. LCT is specifically designed to support protocols using\n IP multicast, but it also provides support to protocols that use\n unicast. LCT is compatible with congestion control that provides\n multiple rate delivery to receivers and is also compatible with\n coding techniques that provide reliable delivery of content. This\n document obsoletes RFC 3451.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IE 5651 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5660","type":"specification","body":"IETF","designation":"RFC 5660","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5660.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5660.txt","https://www.rfc-editor.org/rfc/rfc5660.pdf"],"folder":"IETF/RFC-5660","files":{"txt":{"path":"standards/IETF/RFC-5660/RFC-5660.txt","sha256":"f00fb2479866ea5a8ad8f3231e5b29375895e20c169e63384e7b2179c1ba544a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies, abstractly, how to interface applications\n and transport protocols with IPsec so as to create \"channels\" by\n latching \"connections\" (packet flows) to certain IPsec Security\n Association (SA) parameters for the lifetime of the connections.\n Connection latching is layered on top of IPsec and does not modify\n the underlying IPsec architecture.\n\n Connection latching can be used to protect applications against\n accidentally exposing live packet flows to unintended peers, whether\n as the result of a reconfiguration of IPsec or as the result of using\n weak peer identity to peer address associations. Weak association of\n peer ID and peer addresses is at the core of Better Than Nothing\n Security (BTNS); thus, connection latching can add a significant\n measure of protection to BTNS IPsec nodes.\n\n Finally, the availability of IPsec channels will make it possible to\n use cha","scope_keywords":["5660","authorization","certificate","certificates","credential","credentials","http","key","keys","license","policy","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5660 This document specifies, abstractly, how to interface applications\n and transport protocols with IPsec so as to create \"channels\" by\n latching \"connections\" (packet flows) to certain IPsec Security\n Association (SA) parameters for the lifetime of the connections.\n Connection latching is layered on top of IPsec and does not modify\n the underlying IPsec architecture.\n\n Connection latching can be used to protect applications against\n accidentally exposing live packet flows to unintended peers, whether\n as the result of a reconfiguration of IPsec or as the result of using\n weak peer identity to peer address associations. Weak association of\n peer ID and peer addresses is at the core of Better Than Nothing\n Security (BTNS); thus, connection latching can add a significant\n measure of protection to BTNS IPsec nodes.\n\n Finally, the availability of IPsec channels will make it possible to\n use cha 5660 authorization certificate certificates credential credentials http key keys license policy risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5775","type":"specification","body":"IETF","designation":"RFC 5775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5775.txt","https://www.rfc-editor.org/rfc/rfc5775.pdf"],"folder":"IETF/RFC-5775","files":{"txt":{"path":"standards/IETF/RFC-5775/RFC-5775.txt","sha256":"c979b658a75ffd699826132b13a44c056e28d5df86e2eb0f004447cf718b5609"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Asynchronous Layered Coding (ALC)\n protocol, a massively scalable reliable content delivery protocol.\n Asynchronous Layered Coding combines the Layered Coding Transport\n (LCT) building block, a multiple rate congestion control building\n block and the Forward Error Correction (FEC) building block to\n provide congestion controlled reliable asynchronous delivery of\n content to an unlimited number of concurrent receivers from a single\n sender. This document obsoletes RFC 3450.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC ","scope_keywords":["5775","authentication","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5775 This document describes the Asynchronous Layered Coding (ALC)\n protocol, a massively scalable reliable content delivery protocol.\n Asynchronous Layered Coding combines the Layered Coding Transport\n (LCT) building block, a multiple rate congestion control building\n block and the Forward Error Correction (FEC) building block to\n provide congestion controlled reliable asynchronous delivery of\n content to an unlimited number of concurrent receivers from a single\n sender. This document obsoletes RFC 3450.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC  5775 authentication delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5795","type":"specification","body":"IETF","designation":"RFC 5795","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5795.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5795.txt","https://www.rfc-editor.org/rfc/rfc5795.pdf"],"folder":"IETF/RFC-5795","files":{"txt":{"path":"standards/IETF/RFC-5795/RFC-5795.txt","sha256":"36821e4cf1eec696834a44ab13d36be1e7cc4c18719ae48f0b80afadad14a833"}},"tags":["nested-reference","unchanged"],"summary":"The Robust Header Compression (ROHC) protocol provides an efficient,\n flexible, and future-proof header compression concept. It is\n designed to operate efficiently and robustly over various link\n technologies with different characteristics.\n\n The ROHC framework, along with a set of compression profiles, was\n initially defined in RFC 3095. To improve and simplify the ROHC\n specifications, this document explicitly defines the ROHC framework\n and the profile for uncompressed separately. More specifically, the\n definition of the framework does not modify or update the definition\n of the framework specified by RFC 3095.\n\n This specification obsoletes RFC 4995. It fixes one interoperability\n issue that was erroneously introduced in RFC 4995, and adds some\n minor clarifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Eng","scope_keywords":["5795","algorithm","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 5795 The Robust Header Compression (ROHC) protocol provides an efficient,\n flexible, and future-proof header compression concept. It is\n designed to operate efficiently and robustly over various link\n technologies with different characteristics.\n\n The ROHC framework, along with a set of compression profiles, was\n initially defined in RFC 3095. To improve and simplify the ROHC\n specifications, this document explicitly defines the ROHC framework\n and the profile for uncompressed separately. More specifically, the\n definition of the framework does not modify or update the definition\n of the framework specified by RFC 3095.\n\n This specification obsoletes RFC 4995. It fixes one interoperability\n issue that was erroneously introduced in RFC 4995, and adds some\n minor clarifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Eng 5795 algorithm http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5905","type":"specification","body":"IETF","designation":"RFC 5905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5905.txt","https://www.rfc-editor.org/rfc/rfc5905.pdf"],"folder":"IETF/RFC-5905","files":{"txt":{"path":"standards/IETF/RFC-5905/RFC-5905.txt","sha256":"8b7abd903c60202e2953ee012fefa6916666c3b0c71825c748cdd262024fb268"}},"tags":["nested-reference","unchanged"],"summary":"The Network Time Protocol (NTP) is widely used to synchronize\n computer clocks in the Internet. This document describes NTP version\n 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3),\n described in RFC 1305, as well as previous versions of the protocol.\n NTPv4 includes a modified protocol header to accommodate the Internet\n Protocol version 6 address family. NTPv4 includes fundamental\n improvements in the mitigation and discipline algorithms that extend\n the potential accuracy to the tens of microseconds with modern\n workstations and fast LANs. It includes a dynamic server discovery\n scheme, so that in many cases, specific server configuration is not\n required. It corrects certain errors in the NTPv3 design and\n implementation and includes an optional extension mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product o","scope_keywords":["5905","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6105","folder":"IETF/RFC-6105","source":"IETF/RFC-6105/RFC-6105.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7164","folder":"IETF/RFC-7164","source":"IETF/RFC-7164/RFC-7164.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 5905 The Network Time Protocol (NTP) is widely used to synchronize\n computer clocks in the Internet. This document describes NTP version\n 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3),\n described in RFC 1305, as well as previous versions of the protocol.\n NTPv4 includes a modified protocol header to accommodate the Internet\n Protocol version 6 address family. NTPv4 includes fundamental\n improvements in the mitigation and discipline algorithms that extend\n the potential accuracy to the tens of microseconds with modern\n workstations and fast LANs. It includes a dynamic server discovery\n scheme, so that in many cases, specific server configuration is not\n required. It corrects certain errors in the NTPv3 design and\n implementation and includes an optional extension mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product o 5905 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5936","type":"specification","body":"IETF","designation":"RFC 5936","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5936.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5936.txt","https://www.rfc-editor.org/rfc/rfc5936.pdf"],"folder":"IETF/RFC-5936","files":{"txt":{"path":"standards/IETF/RFC-5936/RFC-5936.txt","sha256":"3bd85bb97ecaf079c725efe76a1f230cbc2902909bb7e7bb5a0ad72d2d244daf"}},"tags":["nested-reference","unchanged"],"summary":"The standard means within the Domain Name System protocol for\n maintaining coherence among a zone's authoritative name servers\n consists of three mechanisms. Authoritative Transfer (AXFR) is one\n of the mechanisms and is defined in RFC 1034 and RFC 1035.\n\n The definition of AXFR has proven insufficient in detail, thereby\n forcing implementations intended to be compliant to make assumptions,\n impeding interoperability. Yet today we have a satisfactory set of\n implementations that do interoperate. This document is a new\n definition of AXFR -- new in the sense that it records an accurate\n definition of an interoperable AXFR mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for public","scope_keywords":["5936","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5936 The standard means within the Domain Name System protocol for\n maintaining coherence among a zone's authoritative name servers\n consists of three mechanisms. Authoritative Transfer (AXFR) is one\n of the mechanisms and is defined in RFC 1034 and RFC 1035.\n\n The definition of AXFR has proven insufficient in detail, thereby\n forcing implementations intended to be compliant to make assumptions,\n impeding interoperability. Yet today we have a satisfactory set of\n implementations that do interoperate. This document is a new\n definition of AXFR -- new in the sense that it records an accurate\n definition of an interoperable AXFR mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for public 5936 authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5966","type":"specification","body":"IETF","designation":"RFC 5966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5966.txt","https://www.rfc-editor.org/rfc/rfc5966.pdf"],"folder":"IETF/RFC-5966","files":{"txt":{"path":"standards/IETF/RFC-5966/RFC-5966.txt","sha256":"0c5340cc08da367bea164188add20f91b8e5effec40c83f328ce2f24c28cfa9d"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the requirements for the support of TCP as a\n transport protocol for DNS implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5966.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documen","scope_keywords":["5966","algorithm","algorithms","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null}],"search_text":"IETF RFC 5966 This document updates the requirements for the support of TCP as a\n transport protocol for DNS implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5966.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documen 5966 algorithm algorithms http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6012","type":"specification","body":"IETF","designation":"RFC 6012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6012.txt","https://www.rfc-editor.org/rfc/rfc6012.pdf"],"folder":"IETF/RFC-6012","files":{"txt":{"path":"standards/IETF/RFC-6012/RFC-6012.txt","sha256":"980c50bf23de3594329c55ddd2ddb6bb9401fba23d16ce64cd1182572df85d9d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the transport of syslog messages over the\n Datagram Transport Layer Security (DTLS) protocol. It provides a\n secure transport for syslog messages in cases where a connectionless\n transport is desired.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6012.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All righ","scope_keywords":["6012","authentication","certificate","http","key","license","policies","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6012 This document describes the transport of syslog messages over the\n Datagram Transport Layer Security (DTLS) protocol. It provides a\n secure transport for syslog messages in cases where a connectionless\n transport is desired.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6012.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All righ 6012 authentication certificate http key license policies subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6056","type":"specification","body":"IETF","designation":"RFC 6056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6056.txt","https://www.rfc-editor.org/rfc/rfc6056.pdf"],"folder":"IETF/RFC-6056","files":{"txt":{"path":"standards/IETF/RFC-6056/RFC-6056.txt","sha256":"2d899269f777944a49b7bcd5373a53284b4b6425a5e957bee90959e976ad26bb"}},"tags":["nested-reference","unchanged"],"summary":"During the last few years, awareness has been raised about a number\n of \"blind\" attacks that can be performed against the Transmission\n Control Protocol (TCP) and similar protocols. The consequences of\n these attacks range from throughput reduction to broken connections\n or data corruption. These attacks rely on the attacker's ability to\n guess or know the five-tuple (Protocol, Source Address, Destination\n Address, Source Port, Destination Port) that identifies the transport\n protocol instance to be attacked. This document describes a number\n of simple and efficient methods for the selection of the client port\n number, such that the possibility of an attacker guessing the exact\n value is reduced. While this is not a replacement for cryptographic\n methods for protecting the transport-protocol instance, the\n aforementioned port selection algorithms provide improved security\n with very litt","scope_keywords":["6056","algorithm","algorithms","hash","http","key","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null}],"search_text":"IETF RFC 6056 During the last few years, awareness has been raised about a number\n of \"blind\" attacks that can be performed against the Transmission\n Control Protocol (TCP) and similar protocols. The consequences of\n these attacks range from throughput reduction to broken connections\n or data corruption. These attacks rely on the attacker's ability to\n guess or know the five-tuple (Protocol, Source Address, Destination\n Address, Source Port, Destination Port) that identifies the transport\n protocol instance to be attacked. This document describes a number\n of simple and efficient methods for the selection of the client port\n number, such that the possibility of an attacker guessing the exact\n value is reduced. While this is not a replacement for cryptographic\n methods for protecting the transport-protocol instance, the\n aforementioned port selection algorithms provide improved security\n with very litt 6056 algorithm algorithms hash http key license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6064","type":"specification","body":"IETF","designation":"RFC 6064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6064.txt","https://www.rfc-editor.org/rfc/rfc6064.pdf"],"folder":"IETF/RFC-6064","files":{"txt":{"path":"standards/IETF/RFC-6064/RFC-6064.txt","sha256":"f996d7e4cb6707708786a99020f06f6e40cd7d72be79a2ff85c7af0b94ea361d"}},"tags":["nested-reference","unchanged"],"summary":"The Packet-switched Streaming Service (PSS) and the Multimedia\n Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session\n Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)\n with some extensions. This document provides information about these\n extensions and registers the RTSP and SDP extensions with IANA.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any erra","scope_keywords":["6064","attribute","attributes","http","license","management","registered","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6064 The Packet-switched Streaming Service (PSS) and the Multimedia\n Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session\n Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)\n with some extensions. This document provides information about these\n extensions and registers the RTSP and SDP extensions with IANA.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any erra 6064 attribute attributes http license management registered subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 6086","type":"specification","body":"IETF","designation":"RFC 6086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6086.txt","https://www.rfc-editor.org/rfc/rfc6086.pdf"],"folder":"IETF/RFC-6086","files":{"txt":{"path":"standards/IETF/RFC-6086/RFC-6086.txt","sha256":"71cee0995848db8250af80d655f09f3a4fd0458fbad6e170164a2e8b58eb6cb7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a method, INFO, for the Session Initiation\n Protocol (SIP), and an Info Package mechanism. This document\n obsoletes RFC 2976. For backward compatibility, this document also\n specifies a \"legacy\" mode of usage of the INFO method that is\n compatible with the usage previously defined in RFC 2976, referred to\n as \"legacy INFO Usage\" in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:","scope_keywords":["6086","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null}],"search_text":"IETF RFC 6086 This document defines a method, INFO, for the Session Initiation\n Protocol (SIP), and an Info Package mechanism. This document\n obsoletes RFC 2976. For backward compatibility, this document also\n specifies a \"legacy\" mode of usage of the INFO method that is\n compatible with the usage previously defined in RFC 2976, referred to\n as \"legacy INFO Usage\" in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http: 6086 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6088","type":"specification","body":"IETF","designation":"RFC 6088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6088.txt","https://www.rfc-editor.org/rfc/rfc6088.pdf"],"folder":"IETF/RFC-6088","files":{"txt":{"path":"standards/IETF/RFC-6088/RFC-6088.txt","sha256":"85d6d136ec2fee4f74d8ea64db318385f7dda2887f95b7f780eda8b82e7ea31a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines binary formats for IPv4 and IPv6 traffic\n selectors to be used in conjunction with flow bindings for Mobile\n IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6088.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions","scope_keywords":["6088","http","identification","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null}],"search_text":"IETF RFC 6088 This document defines binary formats for IPv4 and IPv6 traffic\n selectors to be used in conjunction with flow bindings for Mobile\n IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6088.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions 6088 http identification key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6092","type":"specification","body":"IETF","designation":"RFC 6092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6092.txt","https://www.rfc-editor.org/rfc/rfc6092.pdf"],"folder":"IETF/RFC-6092","files":{"txt":{"path":"standards/IETF/RFC-6092/RFC-6092.txt","sha256":"e51e0445df3734952f3c55cf4cfaf047124dccb2c840db503251e612490301ec"}},"tags":["nested-reference","unchanged"],"summary":"This document identifies a set of recommendations for the makers of\n devices and describes how to provide for \"simple security\"\n capabilities at the perimeter of local-area IPv6 networks in\n Internet-enabled homes and small offices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6092.\n\nC","scope_keywords":["6092","delivery","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 6092 This document identifies a set of recommendations for the makers of\n devices and describes how to provide for \"simple security\"\n capabilities at the perimeter of local-area IPv6 networks in\n Internet-enabled homes and small offices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6092.\n\nC 6092 delivery http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6145","type":"specification","body":"IETF","designation":"RFC 6145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6145.txt","https://www.rfc-editor.org/rfc/rfc6145.pdf"],"folder":"IETF/RFC-6145","files":{"txt":{"path":"standards/IETF/RFC-6145/RFC-6145.txt","sha256":"a28b1fb284976eadd959c345a6803a310cd4f618fcb76f741bbd95b32bbe4d4d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Stateless IP/ICMP Translation Algorithm\n (SIIT), which translates between IPv4 and IPv6 packet headers\n (including ICMP headers). This document obsoletes RFC 2765.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6145.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is s","scope_keywords":["6145","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null}],"search_text":"IETF RFC 6145 This document describes the Stateless IP/ICMP Translation Algorithm\n (SIIT), which translates between IPv4 and IPv6 packet headers\n (including ICMP headers). This document obsoletes RFC 2765.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6145.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is s 6145 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6219","type":"specification","body":"IETF","designation":"RFC 6219","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6219.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6219.txt","https://www.rfc-editor.org/rfc/rfc6219.pdf"],"folder":"IETF/RFC-6219","files":{"txt":{"path":"standards/IETF/RFC-6219/RFC-6219.txt","sha256":"8c686aac858e613e2bf26d0e486e89d1c68db85ef88b19506f8a29bfa7cdb56b"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the China Education and Research Network\n (CERNET)'s IVI translation design and deployment for the IPv4/IPv6\n coexistence and transition.\n\n The IVI is a prefix-specific and stateless address mapping mechanism\n for \"an IPv6 network to the IPv4 Internet\" and \"the IPv4 Internet to\n an IPv6 network\" scenarios. In the IVI design, subsets of the ISP's\n IPv4 addresses are embedded in the ISP's IPv6 addresses, and the\n hosts using these IPv6 addresses can therefore communicate with the\n global IPv6 Internet directly and can communicate with the global\n IPv4 Internet via stateless translators. The communications can\n either be IPv6 initiated or IPv4 initiated. The IVI mechanism\n supports the end-to-end address transparency and incremental\n deployment. The IVI is an early design deployed in the CERNET as a\n reference for the IETF standard documents on IPv4/IPv6 stateless\n tr","scope_keywords":["6219","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 6219 This document presents the China Education and Research Network\n (CERNET)'s IVI translation design and deployment for the IPv4/IPv6\n coexistence and transition.\n\n The IVI is a prefix-specific and stateless address mapping mechanism\n for \"an IPv6 network to the IPv4 Internet\" and \"the IPv4 Internet to\n an IPv6 network\" scenarios. In the IVI design, subsets of the ISP's\n IPv4 addresses are embedded in the ISP's IPv6 addresses, and the\n hosts using these IPv6 addresses can therefore communicate with the\n global IPv6 Internet directly and can communicate with the global\n IPv4 Internet via stateless translators. The communications can\n either be IPv6 initiated or IPv4 initiated. The IVI mechanism\n supports the end-to-end address transparency and incremental\n deployment. The IVI is an early design deployed in the CERNET as a\n reference for the IETF standard documents on IPv4/IPv6 stateless\n tr 6219 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6285","type":"specification","body":"IETF","designation":"RFC 6285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6285.txt","https://www.rfc-editor.org/rfc/rfc6285.pdf"],"folder":"IETF/RFC-6285","files":{"txt":{"path":"standards/IETF/RFC-6285/RFC-6285.txt","sha256":"f6c6bef4c51afb6cdb55a9f15622f8188a75dd1c3a9fe01f19611a59ff9c48d7"}},"tags":["nested-reference","unchanged"],"summary":"When an RTP receiver joins a multicast session, it may need to\n acquire and parse certain Reference Information before it can process\n any data sent in the multicast session. Depending on the join time,\n length of the Reference Information repetition (or appearance)\n interval, size of the Reference Information, and the application and\n transport properties, the time lag before an RTP receiver can\n usefully consume the multicast data, which we refer to as the\n Acquisition Delay, varies and can be large. This is an undesirable\n phenomenon for receivers that frequently switch among different\n multicast sessions, such as video broadcasts.\n\n In this document, we describe a method using the existing RTP and RTP\n Control Protocol (RTCP) machinery that reduces the acquisition delay.\n In this method, an auxiliary unicast RTP session carrying the\n Reference Information to the receiver precedes or ","scope_keywords":["6285","attribute","attributes","encryption","http","key","keys","license","management","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6285 When an RTP receiver joins a multicast session, it may need to\n acquire and parse certain Reference Information before it can process\n any data sent in the multicast session. Depending on the join time,\n length of the Reference Information repetition (or appearance)\n interval, size of the Reference Information, and the application and\n transport properties, the time lag before an RTP receiver can\n usefully consume the multicast data, which we refer to as the\n Acquisition Delay, varies and can be large. This is an undesirable\n phenomenon for receivers that frequently switch among different\n multicast sessions, such as video broadcasts.\n\n In this document, we describe a method using the existing RTP and RTP\n Control Protocol (RTCP) machinery that reduces the acquisition delay.\n In this method, an auxiliary unicast RTP session carrying the\n Reference Information to the receiver precedes or  6285 attribute attributes encryption http key keys license management pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6335","type":"specification","body":"IETF","designation":"RFC 6335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6335.txt","https://www.rfc-editor.org/rfc/rfc6335.pdf"],"folder":"IETF/RFC-6335","files":{"txt":{"path":"standards/IETF/RFC-6335/RFC-6335.txt","sha256":"a78d74017b69a480034b81a8951f05ea35841ae4769ab4fe9787ecc689fb783a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the procedures that the Internet Assigned\n Numbers Authority (IANA) uses when handling assignment and other\n requests related to the Service Name and Transport Protocol Port\n Number registry. It also discusses the rationale and principles\n behind these procedures and how they facilitate the long-term\n sustainability of the registry.\n\n This document updates IANA's procedures by obsoleting the previous\n UDP and TCP port assignment procedures defined in Sections 8 and 9.1\n of the IANA Allocation Guidelines, and it updates the IANA service\n name and port assignment procedures for UDP-Lite, the Datagram\n Congestion Control Protocol (DCCP), and the Stream Control\n Transmission Protocol (SCTP). It also updates the DNS SRV\n specification to clarify what a service name is and how it is\n registered.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.","scope_keywords":["6335","http","key","license","management","registered","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6335 This document defines the procedures that the Internet Assigned\n Numbers Authority (IANA) uses when handling assignment and other\n requests related to the Service Name and Transport Protocol Port\n Number registry. It also discusses the rationale and principles\n behind these procedures and how they facilitate the long-term\n sustainability of the registry.\n\n This document updates IANA's procedures by obsoleting the previous\n UDP and TCP port assignment procedures defined in Sections 8 and 9.1\n of the IANA Allocation Guidelines, and it updates the IANA service\n name and port assignment procedures for UDP-Lite, the Datagram\n Congestion Control Protocol (DCCP), and the Stream Control\n Transmission Protocol (SCTP). It also updates the DNS SRV\n specification to clarify what a service name is and how it is\n registered.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice. 6335 http key license management registered revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6458","type":"specification","body":"IETF","designation":"RFC 6458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6458.txt","https://www.rfc-editor.org/rfc/rfc6458.pdf"],"folder":"IETF/RFC-6458","files":{"txt":{"path":"standards/IETF/RFC-6458/RFC-6458.txt","sha256":"0b9a4439bc778f7ca1d0088fc4757e6fdbae534a18de2e05a9ad380a72bae54f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mapping of the Stream Control Transmission\n Protocol (SCTP) into a sockets API. The benefits of this mapping\n include compatibility for TCP applications, access to new SCTP\n features, and a consolidated error and event notification scheme.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww","scope_keywords":["6458","authentication","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null}],"search_text":"IETF RFC 6458 This document describes a mapping of the Stream Control Transmission\n Protocol (SCTP) into a sockets API. The benefits of this mapping\n include compatibility for TCP applications, access to new SCTP\n features, and a consolidated error and event notification scheme.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww 6458 authentication delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6466","type":"specification","body":"IETF","designation":"RFC 6466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6466.txt","https://www.rfc-editor.org/rfc/rfc6466.pdf"],"folder":"IETF/RFC-6466","files":{"txt":{"path":"standards/IETF/RFC-6466/RFC-6466.txt","sha256":"5cb632f33e5bd5b12957fb4347498f81768a0a77c1836065ef5137e1ccdcb4cc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of the 'image' media type and\n registers it with IANA as a top-level media type for the Session\n Description Protocol (SDP). This media type is primarily used by SDP\n to negotiate and establish T.38 media streams.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6466.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n doc","scope_keywords":["6466","http","key","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 6466 This document describes the usage of the 'image' media type and\n registers it with IANA as a top-level media type for the Session\n Description Protocol (SDP). This media type is primarily used by SDP\n to negotiate and establish T.38 media streams.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6466.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n doc 6466 http key license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6633","type":"specification","body":"IETF","designation":"RFC 6633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6633.txt","https://www.rfc-editor.org/rfc/rfc6633.pdf"],"folder":"IETF/RFC-6633","files":{"txt":{"path":"standards/IETF/RFC-6633/RFC-6633.txt","sha256":"699c82944ee836e11f5e2bbf459c881b3e46ef045fa37384ff1f7649df0059f0"}},"tags":["nested-reference","unchanged"],"summary":"This document formally deprecates the use of ICMP Source Quench\n messages by transport protocols, formally updating RFC 792, RFC 1122,\n and RFC 1812.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6633.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Lega","scope_keywords":["6633","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6633 This document formally deprecates the use of ICMP Source Quench\n messages by transport protocols, formally updating RFC 792, RFC 1122,\n and RFC 1812.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6633.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Lega 6633 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6773","type":"specification","body":"IETF","designation":"RFC 6773","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6773.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6773.txt","https://www.rfc-editor.org/rfc/rfc6773.pdf"],"folder":"IETF/RFC-6773","files":{"txt":{"path":"standards/IETF/RFC-6773/RFC-6773.txt","sha256":"aea86e67458279aa9c3b7e27885061a05b565ac663fed2d173d55311ab5d10fa"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an alternative encapsulation of the Datagram\n Congestion Control Protocol (DCCP), referred to as DCCP-UDP. This\n encapsulation allows DCCP to be carried through the current\n generation of Network Address Translation (NAT) middleboxes without\n modification of those middleboxes. This document also updates the\n Session Description Protocol (SDP) information for DCCP defined in\n RFC 5762.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide","scope_keywords":["6773","algorithm","algorithms","attribute","http","identification","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6773 This document specifies an alternative encapsulation of the Datagram\n Congestion Control Protocol (DCCP), referred to as DCCP-UDP. This\n encapsulation allows DCCP to be carried through the current\n generation of Network Address Translation (NAT) middleboxes without\n modification of those middleboxes. This document also updates the\n Session Description Protocol (SDP) information for DCCP defined in\n RFC 5762.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide 6773 algorithm algorithms attribute http identification key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6830","type":"specification","body":"IETF","designation":"RFC 6830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6830.txt","https://www.rfc-editor.org/rfc/rfc6830.pdf"],"folder":"IETF/RFC-6830","files":{"txt":{"path":"standards/IETF/RFC-6830/RFC-6830.txt","sha256":"531ef0ac7381b50d7d2906fe9ee95be36426d28ac42e374c95b92661731d1ca9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a network-layer-based protocol that enables\n separation of IP addresses into two new numbering spaces: Endpoint\n Identifiers (EIDs) and Routing Locators (RLOCs). No changes are\n required to either host protocol stacks or to the \"core\" of the\n Internet infrastructure. The Locator/ID Separation Protocol (LISP)\n can be incrementally deployed, without a \"flag day\", and offers\n Traffic Engineering, multihoming, and mobility benefits to early\n adopters, even when there are relatively few LISP-capable sites.\n\n Design and development of LISP was largely motivated by the problem\n statement produced by the October 2006 IAB Routing and Addressing\n Workshop.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for t","scope_keywords":["6830","algorithm","hash","hashing","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6832","folder":"IETF/RFC-6832","source":"IETF/RFC-6832/RFC-6832.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6834","folder":"IETF/RFC-6834","source":"IETF/RFC-6834/RFC-6834.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null}],"search_text":"IETF RFC 6830 This document describes a network-layer-based protocol that enables\n separation of IP addresses into two new numbering spaces: Endpoint\n Identifiers (EIDs) and Routing Locators (RLOCs). No changes are\n required to either host protocol stacks or to the \"core\" of the\n Internet infrastructure. The Locator/ID Separation Protocol (LISP)\n can be incrementally deployed, without a \"flag day\", and offers\n Traffic Engineering, multihoming, and mobility benefits to early\n adopters, even when there are relatively few LISP-capable sites.\n\n Design and development of LISP was largely motivated by the problem\n statement produced by the October 2006 IAB Routing and Addressing\n Workshop.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for t 6830 algorithm hash hashing http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6887","type":"specification","body":"IETF","designation":"RFC 6887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6887.txt","https://www.rfc-editor.org/rfc/rfc6887.pdf"],"folder":"IETF/RFC-6887","files":{"txt":{"path":"standards/IETF/RFC-6887/RFC-6887.txt","sha256":"0e58af90ca613ea7ad55f3a17627353667ab7736ff2dfabb0cd73de69e2cbc01"}},"tags":["nested-reference","unchanged"],"summary":"The Port Control Protocol allows an IPv6 or IPv4 host to control how\n incoming IPv6 or IPv4 packets are translated and forwarded by a\n Network Address Translator (NAT) or simple firewall, and also allows\n a host to optimize its outgoing NAT keepalive messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6887.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identifie","scope_keywords":["6887","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6970","folder":"IETF/RFC-6970","source":"IETF/RFC-6970/RFC-6970.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6887 The Port Control Protocol allows an IPv6 or IPv4 host to control how\n incoming IPv6 or IPv4 packets are translated and forwarded by a\n Network Address Translator (NAT) or simple firewall, and also allows\n a host to optimize its outgoing NAT keepalive messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6887.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identifie 6887 http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6936","type":"specification","body":"IETF","designation":"RFC 6936","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6936.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6936.txt","https://www.rfc-editor.org/rfc/rfc6936.pdf"],"folder":"IETF/RFC-6936","files":{"txt":{"path":"standards/IETF/RFC-6936/RFC-6936.txt","sha256":"454c3228edd5a6b03cb6044f164efc86bbf4ea3099e4b0b7d0e17257452e6ca0"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an applicability statement for the use of UDP\n transport checksums with IPv6. It defines recommendations and\n requirements for the use of IPv6 UDP datagrams with a zero UDP\n checksum. It describes the issues and design principles that need to\n be considered when UDP is used with IPv6 to support tunnel\n encapsulations, and it examines the role of the IPv6 UDP transport\n checksum. The document also identifies issues and constraints for\n deployment on network paths that include middleboxes. An appendix\n presents a summary of the trade-offs that were considered in\n evaluating the safety of the update to RFC 2460 that changes the use\n of the UDP checksum with IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n rec","scope_keywords":["6936","algorithm","algorithms","delivery","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 6936 This document provides an applicability statement for the use of UDP\n transport checksums with IPv6. It defines recommendations and\n requirements for the use of IPv6 UDP datagrams with a zero UDP\n checksum. It describes the issues and design principles that need to\n be considered when UDP is used with IPv6 to support tunnel\n encapsulations, and it examines the role of the IPv6 UDP transport\n checksum. The document also identifies issues and constraints for\n deployment on network paths that include middleboxes. An appendix\n presents a summary of the trade-offs that were considered in\n evaluating the safety of the update to RFC 2460 that changes the use\n of the UDP checksum with IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n rec 6936 algorithm algorithms delivery http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6951","type":"specification","body":"IETF","designation":"RFC 6951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6951.txt","https://www.rfc-editor.org/rfc/rfc6951.pdf"],"folder":"IETF/RFC-6951","files":{"txt":{"path":"standards/IETF/RFC-6951/RFC-6951.txt","sha256":"345f68eaf100ba0a8fb7f1609fc2e9a951a208d58dfeabc8a6c7ea1a7d672551"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple method of encapsulating Stream\n Control Transmission Protocol (SCTP) packets into UDP packets and its\n limitations. This allows the usage of SCTP in networks with legacy\n NATs that do not support SCTP. It can also be used to implement SCTP\n on hosts without directly accessing the IP layer, for example,\n implementing it as part of the application without requiring special\n privileges.\n\n Please note that this document only describes the functionality\n required within an SCTP stack to add on UDP encapsulation, providing\n only those mechanisms for two end-hosts to communicate with each\n other over UDP ports. In particular, it does not provide mechanisms\n to determine whether UDP encapsulation is being used by the peer, nor\n the mechanisms for determining which remote UDP port number can be\n used. These functions are out of scope for this document.\n\n This docu","scope_keywords":["6951","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 6951 This document describes a simple method of encapsulating Stream\n Control Transmission Protocol (SCTP) packets into UDP packets and its\n limitations. This allows the usage of SCTP in networks with legacy\n NATs that do not support SCTP. It can also be used to implement SCTP\n on hosts without directly accessing the IP layer, for example,\n implementing it as part of the application without requiring special\n privileges.\n\n Please note that this document only describes the functionality\n required within an SCTP stack to add on UDP encapsulation, providing\n only those mechanisms for two end-hosts to communicate with each\n other over UDP ports. In particular, it does not provide mechanisms\n to determine whether UDP encapsulation is being used by the peer, nor\n the mechanisms for determining which remote UDP port number can be\n used. These functions are out of scope for this document.\n\n This docu 6951 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 7202","type":"specification","body":"IETF","designation":"RFC 7202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7202.txt","https://www.rfc-editor.org/rfc/rfc7202.pdf"],"folder":"IETF/RFC-7202","files":{"txt":{"path":"standards/IETF/RFC-7202/RFC-7202.txt","sha256":"54c2dc6a79a1f365e88df6f3e11c64c0f45c152a3c52bdc46aa7e378c5098c90"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses the problem of securing real-time multimedia\n sessions. It also explains why the Real-time Transport Protocol\n (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a\n single media security mechanism. This is relevant for designers and\n reviewers of future RTP extensions to ensure that appropriate\n security mechanisms are mandated and that any such mechanisms are\n specified in a manner that conforms with the RTP architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate","scope_keywords":["7202","authentication","http","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null}],"search_text":"IETF RFC 7202 This memo discusses the problem of securing real-time multimedia\n sessions. It also explains why the Real-time Transport Protocol\n (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a\n single media security mechanism. This is relevant for designers and\n reviewers of future RTP extensions to ensure that appropriate\n security mechanisms are mandated and that any such mechanisms are\n specified in a manner that conforms with the RTP architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate 7202 authentication http key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7567","type":"specification","body":"IETF","designation":"RFC 7567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7567.txt","https://www.rfc-editor.org/rfc/rfc7567.pdf"],"folder":"IETF/RFC-7567","files":{"txt":{"path":"standards/IETF/RFC-7567/RFC-7567.txt","sha256":"7bf81566611e1d8c8c917d9fa3c8771f50555514a1b9d8320df8428b70f6a621"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents recommendations to the Internet community\n concerning measures to improve and preserve Internet performance. It\n presents a strong recommendation for testing, standardization, and\n widespread deployment of active queue management (AQM) in network\n devices to improve the performance of today's Internet. It also\n urges a concerted effort of research, measurement, and ultimate\n deployment of AQM mechanisms to protect the Internet from flows that\n are not sufficiently responsive to congestion notification.\n\n Based on 15 years of experience and new research, this document\n replaces the recommendations of RFC 2309.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p","scope_keywords":["7567","algorithm","algorithms","http","key","license","management","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8034","folder":"IETF/RFC-8034","source":"IETF/RFC-8034/RFC-8034.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null}],"search_text":"IETF RFC 7567 This memo presents recommendations to the Internet community\n concerning measures to improve and preserve Internet performance. It\n presents a strong recommendation for testing, standardization, and\n widespread deployment of active queue management (AQM) in network\n devices to improve the performance of today's Internet. It also\n urges a concerted effort of research, measurement, and ultimate\n deployment of AQM mechanisms to protect the Internet from flows that\n are not sufficiently responsive to congestion notification.\n\n Based on 15 years of experience and new research, this document\n replaces the recommendations of RFC 2309.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p 7567 algorithm algorithms http key license management path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7604","type":"specification","body":"IETF","designation":"RFC 7604","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7604.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7604.txt","https://www.rfc-editor.org/rfc/rfc7604.pdf"],"folder":"IETF/RFC-7604","files":{"txt":{"path":"standards/IETF/RFC-7604/RFC-7604.txt","sha256":"e259a215d560c6f5a2a71d44a9f9cebd6a886840965c88b7afd47474cb8eaa71"}},"tags":["nested-reference","unchanged"],"summary":"This document describes several Network Address Translator (NAT)\n traversal techniques that were considered to be used for establishing\n the RTP media flows controlled by the Real-Time Streaming Protocol\n (RTSP). Each technique includes a description of how it would be\n used, the security implications of using it, and any other deployment\n considerations it has. There are also discussions on how NAT\n traversal techniques relate to firewalls and how each technique can\n be applied in different use cases. These findings were used when\n selecting the NAT traversal for RTSP 2.0, which is specified in a\n separate document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive","scope_keywords":["7604","http","license","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null}],"search_text":"IETF RFC 7604 This document describes several Network Address Translator (NAT)\n traversal techniques that were considered to be used for establishing\n the RTP media flows controlled by the Real-Time Streaming Protocol\n (RTSP). Each technique includes a description of how it would be\n used, the security implications of using it, and any other deployment\n considerations it has. There are also discussions on how NAT\n traversal techniques relate to firewalls and how each technique can\n be applied in different use cases. These findings were used when\n selecting the NAT traversal for RTSP 2.0, which is specified in a\n separate document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive 7604 http license subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 7657","type":"specification","body":"IETF","designation":"RFC 7657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7657.txt","https://www.rfc-editor.org/rfc/rfc7657.pdf"],"folder":"IETF/RFC-7657","files":{"txt":{"path":"standards/IETF/RFC-7657/RFC-7657.txt","sha256":"e62b9c55f8f42c85480d67306bf69614eeb2093e0668f64e2cee91dd00f0a987"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the interaction between Differentiated Services\n (Diffserv) network quality-of-service (QoS) functionality and real-\n time network communication, including communication based on the\n Real-time Transport Protocol (RTP). Diffserv is based on network\n nodes applying different forwarding treatments to packets whose IP\n headers are marked with different Diffserv Codepoints (DSCPs).\n WebRTC applications, as well as some conferencing applications, have\n begun using the Session Description Protocol (SDP) bundle negotiation\n mechanism to send multiple traffic streams with different QoS\n requirements using the same network 5-tuple. The results of using\n multiple DSCPs to obtain different QoS treatments within a single\n network 5-tuple have transport protocol interactions, particularly\n with congestion control functionality (e.g., reordering). In\n addition, DSCP markings may be","scope_keywords":["7657","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7657 This memo describes the interaction between Differentiated Services\n (Diffserv) network quality-of-service (QoS) functionality and real-\n time network communication, including communication based on the\n Real-time Transport Protocol (RTP). Diffserv is based on network\n nodes applying different forwarding treatments to packets whose IP\n headers are marked with different Diffserv Codepoints (DSCPs).\n WebRTC applications, as well as some conferencing applications, have\n begun using the Session Description Protocol (SDP) bundle negotiation\n mechanism to send multiple traffic streams with different QoS\n requirements using the same network 5-tuple. The results of using\n multiple DSCPs to obtain different QoS treatments within a single\n network 5-tuple have transport protocol interactions, particularly\n with congestion control functionality (e.g., reordering). In\n addition, DSCP markings may be 7657 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7766","type":"specification","body":"IETF","designation":"RFC 7766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7766.txt","https://www.rfc-editor.org/rfc/rfc7766.pdf"],"folder":"IETF/RFC-7766","files":{"txt":{"path":"standards/IETF/RFC-7766/RFC-7766.txt","sha256":"9fbf70d43e5c423c2464eafd724ef164490b4d8e341e5d9b5fe1023402bb404f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirement for support of TCP as a\n transport protocol for DNS implementations and provides guidelines\n towards DNS-over-TCP performance on par with that of DNS-over-UDP.\n This document obsoletes RFC 5966 and therefore updates RFC 1035 and\n RFC 1123.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7766.\n\nDickinson, et al. Standards Track [Page 1]\n\f\nRFC 7766 D","scope_keywords":["7766","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 7766 This document specifies the requirement for support of TCP as a\n transport protocol for DNS implementations and provides guidelines\n towards DNS-over-TCP performance on par with that of DNS-over-UDP.\n This document obsoletes RFC 5966 and therefore updates RFC 1035 and\n RFC 1123.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7766.\n\nDickinson, et al. Standards Track [Page 1]\n\f\nRFC 7766 D 7766 http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7826","type":"specification","body":"IETF","designation":"RFC 7826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7826.txt","https://www.rfc-editor.org/rfc/rfc7826.pdf"],"folder":"IETF/RFC-7826","files":{"txt":{"path":"standards/IETF/RFC-7826/RFC-7826.txt","sha256":"8c4e777cf95f672fbe730712228f4908c7931b785e790520bc7990da6159439f"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum defines the Real-Time Streaming Protocol (RTSP)\n version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326.\n\n RTSP is an application-layer protocol for the setup and control of\n the delivery of data with real-time properties. RTSP provides an\n extensible framework to enable controlled, on-demand delivery of\n real-time data, such as audio and video. Sources of data can include\n both live data feeds and stored clips. This protocol is intended to\n control multiple data delivery sessions; provide a means for choosing\n delivery channels such as UDP, multicast UDP, and TCP; and provide a\n means for choosing delivery mechanisms based upon RTP (RFC 3550).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public","scope_keywords":["7826","attribute","attributes","delivery","http","license","presentation","subject","timestamp","timestamps","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 7826 This memorandum defines the Real-Time Streaming Protocol (RTSP)\n version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326.\n\n RTSP is an application-layer protocol for the setup and control of\n the delivery of data with real-time properties. RTSP provides an\n extensible framework to enable controlled, on-demand delivery of\n real-time data, such as audio and video. Sources of data can include\n both live data feeds and stored clips. This protocol is intended to\n control multiple data delivery sessions; provide a means for choosing\n delivery channels such as UDP, multicast UDP, and TCP; and provide a\n means for choosing delivery mechanisms based upon RTP (RFC 3550).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public 7826 attribute attributes delivery http license presentation subject timestamp timestamps trust tsp nested-reference unchanged"},{"id":"IETF RFC 7915","type":"specification","body":"IETF","designation":"RFC 7915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7915.txt","https://www.rfc-editor.org/rfc/rfc7915.pdf"],"folder":"IETF/RFC-7915","files":{"txt":{"path":"standards/IETF/RFC-7915/RFC-7915.txt","sha256":"a07de7197932df2db7aad7ca609c18153fb167601aae238e7150c1e763a4d056"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Stateless IP/ICMP Translation Algorithm\n (SIIT), which translates between IPv4 and IPv6 packet headers\n (including ICMP headers). This document obsoletes RFC 6145.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7915.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is s","scope_keywords":["7915","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7915 This document describes the Stateless IP/ICMP Translation Algorithm\n (SIIT), which translates between IPv4 and IPv6 packet headers\n (including ICMP headers). This document obsoletes RFC 6145.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7915.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is s 7915 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8085","type":"specification","body":"IETF","designation":"RFC 8085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8085.txt","https://www.rfc-editor.org/rfc/rfc8085.pdf"],"folder":"IETF/RFC-8085","files":{"txt":{"path":"standards/IETF/RFC-8085/RFC-8085.txt","sha256":"9fc8fa172098ef296040c6e3708d56ff5941fdeda3faf4071c58c68059629f3c"}},"tags":["nested-reference","unchanged"],"summary":"The User Datagram Protocol (UDP) provides a minimal message-passing\n transport that has no inherent congestion control mechanisms. This\n document provides guidelines on the use of UDP for the designers of\n applications, tunnels, and other protocols that use UDP. Congestion\n control guidelines are a primary focus, but the document also\n provides guidance on other topics, including message sizes,\n reliability, checksums, middlebox traversal, the use of Explicit\n Congestion Notification (ECN), Differentiated Services Code Points\n (DSCPs), and ports.\n\n Because congestion control is critical to the stable operation of the\n Internet, applications and other protocols that choose to use UDP as\n an Internet transport must employ mechanisms to prevent congestion\n collapse and to establish some degree of fairness with concurrent\n traffic. They may also need to implement additional mechanisms,\n depe","scope_keywords":["8085","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8085 The User Datagram Protocol (UDP) provides a minimal message-passing\n transport that has no inherent congestion control mechanisms. This\n document provides guidelines on the use of UDP for the designers of\n applications, tunnels, and other protocols that use UDP. Congestion\n control guidelines are a primary focus, but the document also\n provides guidance on other topics, including message sizes,\n reliability, checksums, middlebox traversal, the use of Explicit\n Congestion Notification (ECN), Differentiated Services Code Points\n (DSCPs), and ports.\n\n Because congestion control is critical to the stable operation of the\n Internet, applications and other protocols that choose to use UDP as\n an Internet transport must employ mechanisms to prevent congestion\n collapse and to establish some degree of fairness with concurrent\n traffic. They may also need to implement additional mechanisms,\n depe 8085 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8087","type":"specification","body":"IETF","designation":"RFC 8087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8087.txt","https://www.rfc-editor.org/rfc/rfc8087.pdf"],"folder":"IETF/RFC-8087","files":{"txt":{"path":"standards/IETF/RFC-8087/RFC-8087.txt","sha256":"22eee535d4bdcb36ab7be226e7694069aa8baf5331cc2f3a81036e4884621856"}},"tags":["nested-reference","unchanged"],"summary":"The goal of this document is to describe the potential benefits of\n applications using a transport that enables Explicit Congestion\n Notification (ECN). The document outlines the principal gains in\n terms of increased throughput, reduced delay, and other benefits when\n ECN is used over a network path that includes equipment that supports\n Congestion Experienced (CE) marking. It also discusses challenges\n for successful deployment of ECN. It does not propose new algorithms\n to use ECN nor does it describe the details of implementation of ECN\n in endpoint devices (Internet hosts), routers, or other network\n devices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received p","scope_keywords":["8087","algorithm","algorithms","http","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 8087 The goal of this document is to describe the potential benefits of\n applications using a transport that enables Explicit Congestion\n Notification (ECN). The document outlines the principal gains in\n terms of increased throughput, reduced delay, and other benefits when\n ECN is used over a network path that includes equipment that supports\n Congestion Experienced (CE) marking. It also discusses challenges\n for successful deployment of ECN. It does not propose new algorithms\n to use ECN nor does it describe the details of implementation of ECN\n in endpoint devices (Internet hosts), routers, or other network\n devices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received p 8087 algorithm algorithms http license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8323","type":"specification","body":"IETF","designation":"RFC 8323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8323.txt","https://www.rfc-editor.org/rfc/rfc8323.pdf"],"folder":"IETF/RFC-8323","files":{"txt":{"path":"standards/IETF/RFC-8323/RFC-8323.txt","sha256":"8580e89363131387f9fc5ba7ffe664cfb7f66c6232be9cffa3900c7e17f21ed7"}},"tags":["nested-reference","unchanged"],"summary":"The Constrained Application Protocol (CoAP), although inspired by\n HTTP, was designed to use UDP instead of TCP. The message layer of\n CoAP over UDP includes support for reliable delivery, simple\n congestion control, and flow control.\n\n Some environments benefit from the availability of CoAP carried over\n reliable transports such as TCP or Transport Layer Security (TLS).\n This document outlines the changes required to use CoAP over TCP,\n TLS, and WebSockets transports. It also formally updates RFC 7641\n for use with these transports and RFC 7959 to enable the use of\n larger messages over a reliable transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet ","scope_keywords":["8323","delivery","http","https","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 8323 The Constrained Application Protocol (CoAP), although inspired by\n HTTP, was designed to use UDP instead of TCP. The message layer of\n CoAP over UDP includes support for reliable delivery, simple\n congestion control, and flow control.\n\n Some environments benefit from the availability of CoAP carried over\n reliable transports such as TCP or Transport Layer Security (TLS).\n This document outlines the changes required to use CoAP over TCP,\n TLS, and WebSockets transports. It also formally updates RFC 7641\n for use with these transports and RFC 7959 to enable the use of\n larger messages over a reliable transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet  8323 delivery http https license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8612","type":"specification","body":"IETF","designation":"RFC 8612","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8612.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8612.txt","https://www.rfc-editor.org/rfc/rfc8612.pdf"],"folder":"IETF/RFC-8612","files":{"txt":{"path":"standards/IETF/RFC-8612/RFC-8612.txt","sha256":"4a2797e3a2709c94c8ed8e098109c26720b627294fe019a2ee365365c58a1a48"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the requirements for the Distributed Denial-of-\n Service (DDoS) Open Threat Signaling (DOTS) protocols enabling\n coordinated response to DDoS attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8612.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the pers","scope_keywords":["8612","http","https","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8903","folder":"IETF/RFC-8903","source":"IETF/RFC-8903/RFC-8903.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8612 This document defines the requirements for the Distributed Denial-of-\n Service (DDoS) Open Threat Signaling (DOTS) protocols enabling\n coordinated response to DDoS attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8612.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the pers 8612 http https key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8811","type":"specification","body":"IETF","designation":"RFC 8811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8811.txt","https://www.rfc-editor.org/rfc/rfc8811.pdf"],"folder":"IETF/RFC-8811","files":{"pdf":{"path":"standards/IETF/RFC-8811/RFC-8811.pdf","sha256":"45215a097defdd73ef2f01c811461a302bfbbdc992edbeb82c81febcd1f74aa3"},"txt":{"path":"standards/IETF/RFC-8811/RFC-8811.txt","sha256":"ea4b93f2a9e0e76a6cdc0cdcd5c15741b348cc1d1c2f798723027fc2140f5c85"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for establishing and\n maintaining Distributed Denial-of-Service (DDoS) Open Threat\n Signaling (DOTS) within and between domains. The document does not\n specify protocols or protocol extensions, instead focusing on\n defining architectural relationships, components, and concepts used\n in a DOTS deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this documen","scope_keywords":["8811","authentication","authorization","http","https","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8811 This document describes an architecture for establishing and\n maintaining Distributed Denial-of-Service (DDoS) Open Threat\n Signaling (DOTS) within and between domains. The document does not\n specify protocols or protocol extensions, instead focusing on\n defining architectural relationships, components, and concepts used\n in a DOTS deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this documen 8811 authentication authorization http https key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8899","type":"specification","body":"IETF","designation":"RFC 8899","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8899.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8899.txt","https://www.rfc-editor.org/rfc/rfc8899.pdf"],"folder":"IETF/RFC-8899","files":{"pdf":{"path":"standards/IETF/RFC-8899/RFC-8899.pdf","sha256":"da37337ba26fa2fce0d56bb8f53c04cfb2eb45b537d98908c1cb0358823b4a44"},"txt":{"path":"standards/IETF/RFC-8899/RFC-8899.txt","sha256":"174304cb9fc263675a59666cd91d8e3564c25aac858509bbda5d099dcc05f889"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Datagram Packetization Layer Path MTU\n Discovery (DPLPMTUD). This is a robust method for Path MTU Discovery\n (PMTUD) for datagram Packetization Layers (PLs). It allows a PL, or\n a datagram application that uses a PL, to discover whether a network\n path can support the current size of datagram. This can be used to\n detect and reduce the message size when a sender encounters a packet\n black hole. It can also probe a network path to discover whether the\n maximum packet size can be increased. This provides functionality\n for datagram transports that is equivalent to the PLPMTUD\n specification for TCP, specified in RFC 4821, which it updates. It\n also updates the UDP Usage Guidelines to refer to this method for use\n with UDP datagrams and updates SCTP.\n\n The document provides implementation notes for incorporating Datagram\n PMTUD into IETF datagram transports or applic","scope_keywords":["8899","http","https","license","path","policy","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 8899 This document specifies Datagram Packetization Layer Path MTU\n Discovery (DPLPMTUD). This is a robust method for Path MTU Discovery\n (PMTUD) for datagram Packetization Layers (PLs). It allows a PL, or\n a datagram application that uses a PL, to discover whether a network\n path can support the current size of datagram. This can be used to\n detect and reduce the message size when a sender encounters a packet\n black hole. It can also probe a network path to discover whether the\n maximum packet size can be increased. This provides functionality\n for datagram transports that is equivalent to the PLPMTUD\n specification for TCP, specified in RFC 4821, which it updates. It\n also updates the UDP Usage Guidelines to refer to this method for use\n with UDP datagrams and updates SCTP.\n\n The document provides implementation notes for incorporating Datagram\n PMTUD into IETF datagram transports or applic 8899 http https license path policy subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8900","type":"specification","body":"IETF","designation":"RFC 8900","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8900.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8900.txt","https://www.rfc-editor.org/rfc/rfc8900.pdf"],"folder":"IETF/RFC-8900","files":{"pdf":{"path":"standards/IETF/RFC-8900/RFC-8900.pdf","sha256":"773e02d452c32cda61d3db2b895f1046e8ebc0e61c42d93fe79ce84864f692f7"},"txt":{"path":"standards/IETF/RFC-8900/RFC-8900.txt","sha256":"92bb51d4cb7532468b6ae203df0f74d3f1ebb1fa5a416d3963c050c5a0b67856"}},"tags":["nested-reference","unchanged"],"summary":"This document describes IP fragmentation and explains how it\n introduces fragility to Internet communication.\n\n This document also proposes alternatives to IP fragmentation and\n provides recommendations for developers and network operators.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8900.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document autho","scope_keywords":["8900","http","https","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 8900 This document describes IP fragmentation and explains how it\n introduces fragility to Internet communication.\n\n This document also proposes alternatives to IP fragmentation and\n provides recommendations for developers and network operators.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8900.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document autho 8900 http https key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 9000","type":"specification","body":"IETF","designation":"RFC 9000","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9000.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9000.txt","https://www.rfc-editor.org/rfc/rfc9000.pdf"],"folder":"IETF/RFC-9000","files":{"pdf":{"path":"standards/IETF/RFC-9000/RFC-9000.pdf","sha256":"24f411581702fea968f554264a629a80aa5a03a2a959733063391575256edcc7"},"txt":{"path":"standards/IETF/RFC-9000/RFC-9000.txt","sha256":"f88aae47f8b18e102024916e975e919201d8dde689cba79b01079eaedd402e22"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the core of the QUIC transport protocol. QUIC\n provides applications with flow-controlled streams for structured\n communication, low-latency connection establishment, and network path\n migration. QUIC includes security measures that ensure\n confidentiality, integrity, and availability in a range of deployment\n circumstances. Accompanying documents describe the integration of\n TLS for key negotiation, loss detection, and an exemplary congestion\n control algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Informat","scope_keywords":["9000","algorithm","http","https","key","license","path","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9000 This document defines the core of the QUIC transport protocol. QUIC\n provides applications with flow-controlled streams for structured\n communication, low-latency connection establishment, and network path\n migration. QUIC includes security measures that ensure\n confidentiality, integrity, and availability in a range of deployment\n circumstances. Accompanying documents describe the integration of\n TLS for key negotiation, loss detection, and an exemplary congestion\n control algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Informat 9000 algorithm http https key license path subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9147","type":"specification","body":"IETF","designation":"RFC 9147","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9147.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9147.txt","https://www.rfc-editor.org/rfc/rfc9147.pdf"],"folder":"IETF/RFC-9147","files":{"pdf":{"path":"standards/IETF/RFC-9147/RFC-9147.pdf","sha256":"79acbaa5b7d34e4c455033a9dd557496f9bfa033ccc3efde776a994f533c00dd"},"txt":{"path":"standards/IETF/RFC-9147/RFC-9147.txt","sha256":"04e2142333923e36268eb565ec44bdda4db06390114897b819c2f022cb351ebe"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 1.3 of the Datagram Transport Layer\n Security (DTLS) protocol. DTLS 1.3 allows client/server applications\n to communicate over the Internet in a way that is designed to prevent\n eavesdropping, tampering, and message forgery.\n\n The DTLS 1.3 protocol is based on the Transport Layer Security (TLS)\n 1.3 protocol and provides equivalent security guarantees with the\n exception of order protection / non-replayability. Datagram\n semantics of the underlying transport are preserved by the DTLS\n protocol.\n\n This document obsoletes RFC 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further inform","scope_keywords":["9147","encryption","http","https","key","keys","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9147 This document specifies version 1.3 of the Datagram Transport Layer\n Security (DTLS) protocol. DTLS 1.3 allows client/server applications\n to communicate over the Internet in a way that is designed to prevent\n eavesdropping, tampering, and message forgery.\n\n The DTLS 1.3 protocol is based on the Transport Layer Security (TLS)\n 1.3 protocol and provides equivalent security guarantees with the\n exception of order protection / non-replayability. Datagram\n semantics of the underlying transport are preserved by the DTLS\n protocol.\n\n This document obsoletes RFC 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further inform 9147 encryption http https key keys license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 0791","type":"specification","body":"IETF","designation":"RFC 0791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0791.txt","https://www.rfc-editor.org/rfc/rfc0791.pdf"],"folder":"IETF/RFC-0791","files":{"txt":{"path":"standards/IETF/RFC-0791/RFC-0791.txt","sha256":"6cfb387fcecfc1b72f2f69343c5b6951b5d263d708162e2b5c66ab8f394f6265"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 791\n \n \n \n \n \n \n \n INTERNET PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW ..","scope_keywords":["0791","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 0791 RFC: 791\n \n \n \n \n \n \n \n INTERNET PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW .. 0791 key path nested-reference unchanged"},{"id":"IETF RFC 3173","type":"specification","body":"IETF","designation":"RFC 3173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3173.txt","https://www.rfc-editor.org/rfc/rfc3173.pdf"],"folder":"IETF/RFC-3173","files":{"txt":{"path":"standards/IETF/RFC-3173/RFC-3173.txt","sha256":"3eff5aea91aca8e1b7e3da117b62e7796395b5d1b3797589d31abb37f99178c2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol intended to provide lossless\n compression for Internet Protocol datagrams in an Internet\n environment.\n\n1. Introduction\n\n IP payload compression is a protocol to reduce the size of IP\n datagrams. This protocol will increase the overall communication\n performance between a pair of communicating hosts/gateways (\"nodes\")\n by compressing the datagrams, provided the nodes have sufficient\n computation power, through either CPU capacity or a compression\n coprocessor, and the communication is over slow or congested links.\n\n IP payload compression is especially useful when encryption is\n applied to IP datagrams. Encrypting the IP datagram causes the data\n to be random in nature, rendering compression at lower protocol\n layers (e.g., PPP Compression Control Protocol [RFC1962])\n ineffective. If both compression and encryption are required,\n compression must be app","scope_keywords":["3173","algorithm","algorithms","authentication","delivery","encryption","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 3173 This document describes a protocol intended to provide lossless\n compression for Internet Protocol datagrams in an Internet\n environment.\n\n1. Introduction\n\n IP payload compression is a protocol to reduce the size of IP\n datagrams. This protocol will increase the overall communication\n performance between a pair of communicating hosts/gateways (\"nodes\")\n by compressing the datagrams, provided the nodes have sufficient\n computation power, through either CPU capacity or a compression\n coprocessor, and the communication is over slow or congested links.\n\n IP payload compression is especially useful when encryption is\n applied to IP datagrams. Encrypting the IP datagram causes the data\n to be random in nature, rendering compression at lower protocol\n layers (e.g., PPP Compression Control Protocol [RFC1962])\n ineffective. If both compression and encryption are required,\n compression must be app 3173 algorithm algorithms authentication delivery encryption key path policy nested-reference unchanged"},{"id":"IETF RFC 4322","type":"specification","body":"IETF","designation":"RFC 4322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4322.txt","https://www.rfc-editor.org/rfc/rfc4322.pdf"],"folder":"IETF/RFC-4322","files":{"txt":{"path":"standards/IETF/RFC-4322/RFC-4322.txt","sha256":"cca6542b43098fa07428f17cc1c402537150d2840c4e912c30dbd0dcf6fd0b90"}},"tags":["nested-reference","unchanged"],"summary":"This document describes opportunistic encryption (OE) as designed and\n implemented by the Linux FreeS/WAN project. OE uses the Internet Key\n Exchange (IKE) and IPsec protocols. The objective is to allow\n encryption for secure communication without any pre-arrangement\n specific to the pair of systems involved. DNS is used to distribute\n the public keys of each system involved. This is resistant to\n passive attacks. The use of DNS Security (DNSSEC) secures this\n system against active attackers as well.\n\n As a result, the administrative overhead is reduced from the square\n of the number of systems to a linear dependence, and it becomes\n possible to make secure communication the default even when the\n partner is not known in advance.","scope_keywords":["4322","authentication","encryption","http","identification","key","keys","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null}],"search_text":"IETF RFC 4322 This document describes opportunistic encryption (OE) as designed and\n implemented by the Linux FreeS/WAN project. OE uses the Internet Key\n Exchange (IKE) and IPsec protocols. The objective is to allow\n encryption for secure communication without any pre-arrangement\n specific to the pair of systems involved. DNS is used to distribute\n the public keys of each system involved. This is resistant to\n passive attacks. The use of DNS Security (DNSSEC) secures this\n system against active attackers as well.\n\n As a result, the administrative overhead is reduced from the square\n of the number of systems to a linear dependence, and it becomes\n possible to make secure communication the default even when the\n partner is not known in advance. 4322 authentication encryption http identification key keys policy nested-reference unchanged"},{"id":"IETF RFC 4594","type":"specification","body":"IETF","designation":"RFC 4594","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4594.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4594.txt","https://www.rfc-editor.org/rfc/rfc4594.pdf"],"folder":"IETF/RFC-4594","files":{"txt":{"path":"standards/IETF/RFC-4594/RFC-4594.txt","sha256":"73654e93f208f645efc2c3b43c5dafec3dd6685f90a9d88821bb4e250e1fbbf6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes service classes configured with Diffserv and\n recommends how they can be used and how to construct them using\n Differentiated Services Code Points (DSCPs), traffic conditioners,\n Per-Hop Behaviors (PHBs), and Active Queue Management (AQM)\n mechanisms. There is no intrinsic requirement that particular DSCPs,\n traffic conditioners, PHBs, and AQM be used for a certain service\n class, but as a policy and for interoperability it is useful to apply\n them consistently.\n\nBabiarz, et al. Informational [Page 1]\n\f\nRFC 4594 Guidelines for DiffServ Service Classes August 2006","scope_keywords":["4594","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 4594 This document describes service classes configured with Diffserv and\n recommends how they can be used and how to construct them using\n Differentiated Services Code Points (DSCPs), traffic conditioners,\n Per-Hop Behaviors (PHBs), and Active Queue Management (AQM)\n mechanisms. There is no intrinsic requirement that particular DSCPs,\n traffic conditioners, PHBs, and AQM be used for a certain service\n class, but as a policy and for interoperability it is useful to apply\n them consistently.\n\nBabiarz, et al. Informational [Page 1]\n\f\nRFC 4594 Guidelines for DiffServ Service Classes August 2006 4594 key management policy nested-reference unchanged"},{"id":"IETF RFC 4727","type":"specification","body":"IETF","designation":"RFC 4727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4727.txt","https://www.rfc-editor.org/rfc/rfc4727.pdf"],"folder":"IETF/RFC-4727","files":{"txt":{"path":"standards/IETF/RFC-4727/RFC-4727.txt","sha256":"5573aa595fc5fe8fc7fcbc93a7832f24317603982cea8266fccafdb59571a963"}},"tags":["nested-reference","unchanged"],"summary":"When experimenting with or extending protocols, it is often necessary\n to use some sort of protocol number or constant in order to actually\n test or experiment with the new function, even when testing in a\n closed environment. This document reserves some ranges of numbers\n for experimentation purposes in specific protocols where the need to\n support experimentation has been identified, and it describes the\n numbers that have already been reserved by other documents.\n\nFenner Standards Track [Page 1]\n\f\nRFC 4727 Experimental Values in Headers November 2006\n\n1. Introduction\n\n [RFC3692] recommends assigning option numbers for experiments and\n testing. This document documents several such assignments for the\n number spaces whose IANA considerations are documented in [RFC2780].\n This document generally follows the form of [RFC2780].\n\n When using these values, carefully consider the advice in Se","scope_keywords":["4727","path","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5871","folder":"IETF/RFC-5871","source":"IETF/RFC-5871/RFC-5871.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4727 When experimenting with or extending protocols, it is often necessary\n to use some sort of protocol number or constant in order to actually\n test or experiment with the new function, even when testing in a\n closed environment. This document reserves some ranges of numbers\n for experimentation purposes in specific protocols where the need to\n support experimentation has been identified, and it describes the\n numbers that have already been reserved by other documents.\n\nFenner Standards Track [Page 1]\n\f\nRFC 4727 Experimental Values in Headers November 2006\n\n1. Introduction\n\n [RFC3692] recommends assigning option numbers for experiments and\n testing. This document documents several such assignments for the\n number spaces whose IANA considerations are documented in [RFC2780].\n This document generally follows the form of [RFC2780].\n\n When using these values, carefully consider the advice in Se 4727 path policies policy trust nested-reference unchanged"},{"id":"IETF RFC 4821","type":"specification","body":"IETF","designation":"RFC 4821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4821.txt","https://www.rfc-editor.org/rfc/rfc4821.pdf"],"folder":"IETF/RFC-4821","files":{"txt":{"path":"standards/IETF/RFC-4821/RFC-4821.txt","sha256":"30e01d01c750f53b8ba7c6502b5eb50db2429881bf8169fae5caa24947d20348"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a robust method for Path MTU Discovery\n (PMTUD) that relies on TCP or some other Packetization Layer to probe\n an Internet path with progressively larger packets. This method is\n described as an extension to RFC 1191 and RFC 1981, which specify\n ICMP-based Path MTU Discovery for IP versions 4 and 6, respectively.\n\nMathis & Heffner Standards Track [Page 1]\n\f\nRFC 4821 Packetization Layer Path MTU Discovery March 2007","scope_keywords":["4821","algorithm","algorithms","delivery","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4820","folder":"IETF/RFC-4820","source":"IETF/RFC-4820/RFC-4820.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 4821 This document describes a robust method for Path MTU Discovery\n (PMTUD) that relies on TCP or some other Packetization Layer to probe\n an Internet path with progressively larger packets. This method is\n described as an extension to RFC 1191 and RFC 1981, which specify\n ICMP-based Path MTU Discovery for IP versions 4 and 6, respectively.\n\nMathis & Heffner Standards Track [Page 1]\n\f\nRFC 4821 Packetization Layer Path MTU Discovery March 2007 4821 algorithm algorithms delivery key path trust nested-reference unchanged"},{"id":"IETF RFC 4932","type":"specification","body":"IETF","designation":"RFC 4932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4932.txt","https://www.rfc-editor.org/rfc/rfc4932.pdf"],"folder":"IETF/RFC-4932","files":{"txt":{"path":"standards/IETF/RFC-4932/RFC-4932.txt","sha256":"ad52605ba5f38474ecc5614ce06f786fbaf091f1cd5a6465f3806c2e2a212378"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names.\n This document obsoletes RFC 3732.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4932 EPP Host Mapping May 2007","scope_keywords":["4932","attribute","attributes","key","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null}],"search_text":"IETF RFC 4932 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names.\n This document obsoletes RFC 3732.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4932 EPP Host Mapping May 2007 4932 attribute attributes key management subject trust nested-reference unchanged"},{"id":"IETF RFC 4963","type":"specification","body":"IETF","designation":"RFC 4963","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4963.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4963.txt","https://www.rfc-editor.org/rfc/rfc4963.pdf"],"folder":"IETF/RFC-4963","files":{"txt":{"path":"standards/IETF/RFC-4963/RFC-4963.txt","sha256":"85800187c2b65486c62894c62582c3a06082f0e02f3bc1c34872c291427dc847"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Heffner\nRequest for Comments: 4963 M. Mathis\nCategory: Informational B. Chandler\n PSC\n July 2007\n\n IPv4 Reassembly Errors at High Data Rates\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n IPv4 fragmentation is not sufficiently robust for use under some\n conditions in today's Internet. At high data rates, the 16-bit IP\n identification field is not large enough to prevent frequent\n incorrectly assembled IP fragments, and the TCP and UDP checksums are\n insufficient to prevent the resulting corrupted datagrams from being\n delivered to higher protocol layers. This note describes some easily\n reproduced experiments demonstrating the problem, and discusses some\n of the oper","scope_keywords":["4963","algorithm","algorithms","identification","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 4963 Network Working Group J. Heffner\nRequest for Comments: 4963 M. Mathis\nCategory: Informational B. Chandler\n PSC\n July 2007\n\n IPv4 Reassembly Errors at High Data Rates\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n IPv4 fragmentation is not sufficiently robust for use under some\n conditions in today's Internet. At high data rates, the 16-bit IP\n identification field is not large enough to prevent frequent\n incorrectly assembled IP fragments, and the TCP and UDP checksums are\n insufficient to prevent the resulting corrupted datagrams from being\n delivered to higher protocol layers. This note describes some easily\n reproduced experiments demonstrating the problem, and discusses some\n of the oper 4963 algorithm algorithms identification path trust nested-reference unchanged"},{"id":"IETF RFC 4996","type":"specification","body":"IETF","designation":"RFC 4996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4996.txt","https://www.rfc-editor.org/rfc/rfc4996.pdf"],"folder":"IETF/RFC-4996","files":{"txt":{"path":"standards/IETF/RFC-4996/RFC-4996.txt","sha256":"19dffaca436b3f24eccf75d703ea39ff0588d129a836fec0233c488c89ec907e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a ROHC (Robust Header Compression) profile\n for compression of TCP/IP packets. The profile, called ROHC-TCP,\n provides efficient and robust compression of TCP headers, including\n frequently used TCP options such as SACK (Selective Acknowledgments)\n and Timestamps.\n\n ROHC-TCP works well when used over links with significant error rates\n and long round-trip times. For many bandwidth-limited links where\n header compression is essential, such characteristics are common.\n\nPelletier, et al. Standards Track [Page 1]\n\f\nRFC 4996 ROHC-TCP July 2007","scope_keywords":["4996","profile","profiles","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4996 This document specifies a ROHC (Robust Header Compression) profile\n for compression of TCP/IP packets. The profile, called ROHC-TCP,\n provides efficient and robust compression of TCP headers, including\n frequently used TCP options such as SACK (Selective Acknowledgments)\n and Timestamps.\n\n ROHC-TCP works well when used over links with significant error rates\n and long round-trip times. For many bandwidth-limited links where\n header compression is essential, such characteristics are common.\n\nPelletier, et al. Standards Track [Page 1]\n\f\nRFC 4996 ROHC-TCP July 2007 4996 profile profiles timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5082","type":"specification","body":"IETF","designation":"RFC 5082","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5082.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5082.txt","https://www.rfc-editor.org/rfc/rfc5082.pdf"],"folder":"IETF/RFC-5082","files":{"txt":{"path":"standards/IETF/RFC-5082/RFC-5082.txt","sha256":"21869e5983e4103210b98d43ba7b17bfecb699f0b105b0b14b5ab5ff4628a809"}},"tags":["nested-reference","unchanged"],"summary":"The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)\n to verify whether the packet was originated by an adjacent node on a\n connected link has been used in many recent protocols. This document\n generalizes this technique. This document obsoletes Experimental RFC\n 3682.\n\nGill, et al. Standards Track [Page 1]\n\f\nRFC 5082 GTSM October 2007","scope_keywords":["5082","authentication","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5082 The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)\n to verify whether the packet was originated by an adjacent node on a\n connected link has been used in many recent protocols. This document\n generalizes this technique. This document obsoletes Experimental RFC\n 3682.\n\nGill, et al. Standards Track [Page 1]\n\f\nRFC 5082 GTSM October 2007 5082 authentication key path trust nested-reference unchanged"},{"id":"IETF RFC 5237","type":"specification","body":"IETF","designation":"RFC 5237","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5237.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5237.txt","https://www.rfc-editor.org/rfc/rfc5237.pdf"],"folder":"IETF/RFC-5237","files":{"txt":{"path":"standards/IETF/RFC-5237/RFC-5237.txt","sha256":"9a3844d5db613c027b6bdb8e8e24a5cbb966b3834fe10704f579235490d098c0"}},"tags":["nested-reference","unchanged"],"summary":"This document revises the IANA guidelines for allocating new Protocol\n field values in IPv4 header. It modifies the rules specified in RFC\n 2780 by removing the Expert Review option. The change will also\n affect the allocation of Next Header field values in IPv6.\n\n1. Introduction\n\n This document revises the IANA guidelines [RFC2780] for allocating\n new Protocol field values in IPv4 header [RFC0791]. The change will\n also be applicable for IPv6, as the IANA guidelines for IPv6 Next\n Header values [RFC2460] allocation refer to the IPv4 guidelines.\n\n Previously, RFC 2780 allowed such allocations to happen through IESG\n Approval, Standards action, or Expert Review processes\n [RFC2780][RFC2434]. The Expert Review process was specified to be\n used only in the case where a non-disclosure agreement was involved:\n\n IANA allocates values from the IPv4 Protocol name space following\n an Expert Revie","scope_keywords":["5237","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null}],"search_text":"IETF RFC 5237 This document revises the IANA guidelines for allocating new Protocol\n field values in IPv4 header. It modifies the rules specified in RFC\n 2780 by removing the Expert Review option. The change will also\n affect the allocation of Next Header field values in IPv6.\n\n1. Introduction\n\n This document revises the IANA guidelines [RFC2780] for allocating\n new Protocol field values in IPv4 header [RFC0791]. The change will\n also be applicable for IPv6, as the IANA guidelines for IPv6 Next\n Header values [RFC2460] allocation refer to the IPv4 guidelines.\n\n Previously, RFC 2780 allowed such allocations to happen through IESG\n Approval, Standards action, or Expert Review processes\n [RFC2780][RFC2434]. The Expert Review process was specified to be\n used only in the case where a non-disclosure agreement was involved:\n\n IANA allocates values from the IPv4 Protocol name space following\n an Expert Revie 5237 license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5389","type":"specification","body":"IETF","designation":"RFC 5389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5389.txt","https://www.rfc-editor.org/rfc/rfc5389.pdf"],"folder":"IETF/RFC-5389","files":{"txt":{"path":"standards/IETF/RFC-5389/RFC-5389.txt","sha256":"2dc3c8879619d8d63d7cfd4edd68d0df59a31647a5110ebf807e2ca57d84eae3"}},"tags":["nested-reference","unchanged"],"summary":"Session Traversal Utilities for NAT (STUN) is a protocol that serves\n as a tool for other protocols in dealing with Network Address\n Translator (NAT) traversal. It can be used by an endpoint to\n determine the IP address and port allocated to it by a NAT. It can\n also be used to check connectivity between two endpoints, and as a\n keep-alive protocol to maintain NAT bindings. STUN works with many\n existing NATs, and does not require any special behavior from them.\n\n STUN is not a NAT traversal solution by itself. Rather, it is a tool\n to be used in the context of a NAT traversal solution. This is an\n important change from the previous version of this specification (RFC\n 3489), which presented STUN as a complete solution.\n\n This document obsoletes RFC 3489.","scope_keywords":["5389","attribute","attributes","authentication","credential","hash","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5769","folder":"IETF/RFC-5769","source":"IETF/RFC-5769/RFC-5769.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null}],"search_text":"IETF RFC 5389 Session Traversal Utilities for NAT (STUN) is a protocol that serves\n as a tool for other protocols in dealing with Network Address\n Translator (NAT) traversal. It can be used by an endpoint to\n determine the IP address and port allocated to it by a NAT. It can\n also be used to check connectivity between two endpoints, and as a\n keep-alive protocol to maintain NAT bindings. STUN works with many\n existing NATs, and does not require any special behavior from them.\n\n STUN is not a NAT traversal solution by itself. Rather, it is a tool\n to be used in the context of a NAT traversal solution. This is an\n important change from the previous version of this specification (RFC\n 3489), which presented STUN as a complete solution.\n\n This document obsoletes RFC 3489. 5389 attribute attributes authentication credential hash tls nested-reference unchanged"},{"id":"IETF RFC 5477","type":"specification","body":"IETF","designation":"RFC 5477","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5477.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5477.txt","https://www.rfc-editor.org/rfc/rfc5477.pdf"],"folder":"IETF/RFC-5477","files":{"txt":{"path":"standards/IETF/RFC-5477/RFC-5477.txt","sha256":"eaff7fd678b60d62d4847b430028fb030245a90ee1108f0208caee50068a357d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an information model for the Packet SAMPling\n (PSAMP) protocol. It is used by the PSAMP protocol for encoding\n sampled packet data and information related to the Sampling process.\n As the PSAMP protocol is based on the IP Flow Information eXport\n (IPFIX) protocol, this information model is an extension to the IPFIX\n information model.","scope_keywords":["5477","algorithm","hash","http","license","subject","timestamp","timestamps","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null}],"search_text":"IETF RFC 5477 This memo defines an information model for the Packet SAMPling\n (PSAMP) protocol. It is used by the PSAMP protocol for encoding\n sampled packet data and information related to the Sampling process.\n As the PSAMP protocol is based on the IP Flow Information eXport\n (IPFIX) protocol, this information model is an extension to the IPFIX\n information model. 5477 algorithm hash http license subject timestamp timestamps trust tsp nested-reference unchanged"},{"id":"IETF RFC 5720","type":"specification","body":"IETF","designation":"RFC 5720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5720.txt","https://www.rfc-editor.org/rfc/rfc5720.pdf"],"folder":"IETF/RFC-5720","files":{"txt":{"path":"standards/IETF/RFC-5720/RFC-5720.txt","sha256":"5ecd58e12aa570430754f84d540b88f4b492bb865e6d5506abc9f6e8be1a58dc"}},"tags":["nested-reference","unchanged"],"summary":"RANGER is an architectural framework for scalable routing and\n addressing in networks with global enterprise recursion. The term\n \"enterprise network\" within this context extends to a wide variety of\n use cases and deployment scenarios, where an \"enterprise\" can be as\n small as a Small Office, Home Office (SOHO) network, as dynamic as a\n Mobile Ad Hoc Network, as complex as a multi-organizational\n corporation, or as large as the global Internet itself. Such\n networks will require an architected solution for the coordination of\n routing and addressing plans with accommodations for scalability,\n provider-independence, mobility, multihoming, and security. These\n considerations are particularly true for existing deployments, but\n the same principles apply even for clean-slate approaches. The\n RANGER architecture addresses these requirements and provides a\n comprehensive framework for IPv6/IP","scope_keywords":["5720","http","license","management","seal","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null}],"search_text":"IETF RFC 5720 RANGER is an architectural framework for scalable routing and\n addressing in networks with global enterprise recursion. The term\n \"enterprise network\" within this context extends to a wide variety of\n use cases and deployment scenarios, where an \"enterprise\" can be as\n small as a Small Office, Home Office (SOHO) network, as dynamic as a\n Mobile Ad Hoc Network, as complex as a multi-organizational\n corporation, or as large as the global Internet itself. Such\n networks will require an architected solution for the coordination of\n routing and addressing plans with accommodations for scalability,\n provider-independence, mobility, multihoming, and security. These\n considerations are particularly true for existing deployments, but\n the same principles apply even for clean-slate approaches. The\n RANGER architecture addresses these requirements and provides a\n comprehensive framework for IPv6/IP 5720 http license management seal subject trust nested-reference unchanged"},{"id":"IETF RFC 5732","type":"specification","body":"IETF","designation":"RFC 5732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5732.txt","https://www.rfc-editor.org/rfc/rfc5732.pdf"],"folder":"IETF/RFC-5732","files":{"txt":{"path":"standards/IETF/RFC-5732/RFC-5732.txt","sha256":"c4c3934315df478d5c9c4955ffd2b92cc98763ce09c9a12f573694a2a0e61662"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names.\n This document obsoletes RFC 4932.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in ","scope_keywords":["5732","attribute","attributes","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null}],"search_text":"IETF RFC 5732 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names.\n This document obsoletes RFC 4932.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in  5732 attribute attributes http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5734","type":"specification","body":"IETF","designation":"RFC 5734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5734.txt","https://www.rfc-editor.org/rfc/rfc5734.pdf"],"folder":"IETF/RFC-5734","files":{"txt":{"path":"standards/IETF/RFC-5734/RFC-5734.txt","sha256":"00db6489a7343dcfda2a7885931af2b4dad7d1cb9600a124df3dff9aea640fb2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server. This document obsoletes RFC 4934.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re","scope_keywords":["5734","http","key","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5734 This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server. This document obsoletes RFC 4934.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re 5734 http key license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5766","type":"specification","body":"IETF","designation":"RFC 5766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5766.txt","https://www.rfc-editor.org/rfc/rfc5766.pdf"],"folder":"IETF/RFC-5766","files":{"txt":{"path":"standards/IETF/RFC-5766/RFC-5766.txt","sha256":"163fa3748cfa9b4af4aee93e8f86608961b75d8021e9d5ac65611f9e6b17b61d"}},"tags":["nested-reference","unchanged"],"summary":"If a host is located behind a NAT, then in certain situations it can\n be impossible for that host to communicate directly with other hosts\n (peers). In these situations, it is necessary for the host to use\n the services of an intermediate node that acts as a communication\n relay. This specification defines a protocol, called TURN (Traversal\n Using Relays around NAT), that allows the host to control the\n operation of the relay and to exchange packets with its peers using\n the relay. TURN differs from some other relay control protocols in\n that it allows a client to communicate with multiple peers using a\n single relay address.\n\n The TURN protocol was designed to be used as part of the ICE\n (Interactive Connectivity Establishment) approach to NAT traversal,\n though it also can be used without ICE.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pro","scope_keywords":["5766","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null}],"search_text":"IETF RFC 5766 If a host is located behind a NAT, then in certain situations it can\n be impossible for that host to communicate directly with other hosts\n (peers). In these situations, it is necessary for the host to use\n the services of an intermediate node that acts as a communication\n relay. This specification defines a protocol, called TURN (Traversal\n Using Relays around NAT), that allows the host to control the\n operation of the relay and to exchange packets with its peers using\n the relay. TURN differs from some other relay control protocols in\n that it allows a client to communicate with multiple peers using a\n single relay address.\n\n The TURN protocol was designed to be used as part of the ICE\n (Interactive Connectivity Establishment) approach to NAT traversal,\n though it also can be used without ICE.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pro 5766 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5927","type":"specification","body":"IETF","designation":"RFC 5927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5927.txt","https://www.rfc-editor.org/rfc/rfc5927.pdf"],"folder":"IETF/RFC-5927","files":{"txt":{"path":"standards/IETF/RFC-5927/RFC-5927.txt","sha256":"b90bd4a3dbd1dcfb86bf4369a39cb0d50b08bca82d8ecadf0294a63c299c751d"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the use of the Internet Control Message\n Protocol (ICMP) to perform a variety of attacks against the\n Transmission Control Protocol (TCP). Additionally, this document\n describes a number of widely implemented modifications to TCP's\n handling of ICMP error messages that help to mitigate these issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and ","scope_keywords":["5927","http","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 5927 This document discusses the use of the Internet Control Message\n Protocol (ICMP) to perform a variety of attacks against the\n Transmission Control Protocol (TCP). Additionally, this document\n describes a number of widely implemented modifications to TCP's\n handling of ICMP error messages that help to mitigate these issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and  5927 http license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6069","type":"specification","body":"IETF","designation":"RFC 6069","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6069.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6069.txt","https://www.rfc-editor.org/rfc/rfc6069.pdf"],"folder":"IETF/RFC-6069","files":{"txt":{"path":"standards/IETF/RFC-6069/RFC-6069.txt","sha256":"131ca741937f7c52d05944262322cac8c8dbcf712de216929919d64cfdd91ca0"}},"tags":["nested-reference","unchanged"],"summary":"Disruptions in end-to-end path connectivity, which last longer than\n one retransmission timeout, cause suboptimal TCP performance. The\n reason for this performance degradation is that TCP interprets\n segment loss induced by long connectivity disruptions as a sign of\n congestion, resulting in repeated retransmission timer backoffs.\n This, in turn, leads to a delayed detection of the re-establishment\n of the connection since TCP waits for the next retransmission timeout\n before it attempts a retransmission.\n\n This document proposes an algorithm to make TCP more robust to long\n connectivity disruptions (TCP-LCD). It describes how standard ICMP\n messages can be exploited during timeout-based loss recovery to\n disambiguate true congestion loss from non-congestion loss caused by\n connectivity disruptions. Moreover, a reversion strategy of the\n retransmission timer is specified that enables a m","scope_keywords":["6069","algorithm","http","license","path","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6069 Disruptions in end-to-end path connectivity, which last longer than\n one retransmission timeout, cause suboptimal TCP performance. The\n reason for this performance degradation is that TCP interprets\n segment loss induced by long connectivity disruptions as a sign of\n congestion, resulting in repeated retransmission timer backoffs.\n This, in turn, leads to a delayed detection of the re-establishment\n of the connection since TCP waits for the next retransmission timeout\n before it attempts a retransmission.\n\n This document proposes an algorithm to make TCP more robust to long\n connectivity disruptions (TCP-LCD). It describes how standard ICMP\n messages can be exploited during timeout-based loss recovery to\n disambiguate true congestion loss from non-congestion loss caused by\n connectivity disruptions. Moreover, a reversion strategy of the\n retransmission timer is specified that enables a m 6069 algorithm http license path subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 6101","type":"specification","body":"IETF","designation":"RFC 6101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6101.txt","https://www.rfc-editor.org/rfc/rfc6101.pdf"],"folder":"IETF/RFC-6101","files":{"txt":{"path":"standards/IETF/RFC-6101/RFC-6101.txt","sha256":"9571fe931f68204163a8e8a374a104fd1389ff7056f2e9e5d3fac886f7d180bb"}},"tags":["nested-reference","unchanged"],"summary":"This document is published as a historical record of the SSL 3.0\n protocol. The original Abstract follows.\n\n This document specifies version 3.0 of the Secure Sockets Layer (SSL\n 3.0) protocol, a security protocol that provides communications\n privacy over the Internet. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery.\n\nForeword\n\n Although the SSL 3.0 protocol is a widely implemented protocol, a\n pioneer in secure communications protocols, and the basis for\n Transport Layer Security (TLS), it was never formally published by\n the IETF, except in several expired Internet-Drafts. This allowed no\n easy referencing to the protocol. We believe a stable reference to\n the original document should exist and for that reason, this document\n describes what is known as the last published version of the SS","scope_keywords":["6101","attribute","attributes","certificate","http","key","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 6101 This document is published as a historical record of the SSL 3.0\n protocol. The original Abstract follows.\n\n This document specifies version 3.0 of the Secure Sockets Layer (SSL\n 3.0) protocol, a security protocol that provides communications\n privacy over the Internet. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery.\n\nForeword\n\n Although the SSL 3.0 protocol is a widely implemented protocol, a\n pioneer in secure communications protocols, and the basis for\n Transport Layer Security (TLS), it was never formally published by\n the IETF, except in several expired Internet-Drafts. This allowed no\n easy referencing to the protocol. We believe a stable reference to\n the original document should exist and for that reason, this document\n describes what is known as the last published version of the SS 6101 attribute attributes certificate http key license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6250","type":"specification","body":"IETF","designation":"RFC 6250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6250.txt","https://www.rfc-editor.org/rfc/rfc6250.pdf"],"folder":"IETF/RFC-6250","files":{"txt":{"path":"standards/IETF/RFC-6250/RFC-6250.txt","sha256":"d592b2bd89f6f85949b3b5638a45d61f93775711ce459a1f7e6f43f09dd284f9"}},"tags":["nested-reference","unchanged"],"summary":"This RFC attempts to document various aspects of the IP service model\n and how it has evolved over time. In particular, it attempts to\n document the properties of the IP layer as they are seen by upper-\n layer protocols and applications, especially properties that were\n (and, at times, still are) incorrectly perceived to exist as well as\n properties that would cause problems if changed. The discussion of\n these properties is organized around evaluating a set of claims, or\n misconceptions. Finally, this document provides some guidance to\n protocol designers and implementers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for","scope_keywords":["6250","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 6250 This RFC attempts to document various aspects of the IP service model\n and how it has evolved over time. In particular, it attempts to\n document the properties of the IP layer as they are seen by upper-\n layer protocols and applications, especially properties that were\n (and, at times, still are) incorrectly perceived to exist as well as\n properties that would cause problems if changed. The discussion of\n these properties is organized around evaluating a set of claims, or\n misconceptions. Finally, this document provides some guidance to\n protocol designers and implementers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for 6250 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6274","type":"specification","body":"IETF","designation":"RFC 6274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6274.txt","https://www.rfc-editor.org/rfc/rfc6274.pdf"],"folder":"IETF/RFC-6274","files":{"txt":{"path":"standards/IETF/RFC-6274/RFC-6274.txt","sha256":"f2192e38c8aa09b26b2a3d2e012d56c5e0ae4167e587238f3bd969b8f09dd408"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a security assessment of the IETF\n specifications of the Internet Protocol version 4 and of a number of\n mechanisms and policies in use by popular IPv4 implementations. It\n is based on the results of a project carried out by the UK's Centre\n for the Protection of National Infrastructure (CPNI).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to","scope_keywords":["6274","algorithm","delivery","http","identification","license","policies","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null}],"search_text":"IETF RFC 6274 This document contains a security assessment of the IETF\n specifications of the Internet Protocol version 4 and of a number of\n mechanisms and policies in use by popular IPv4 implementations. It\n is based on the results of a project carried out by the UK's Centre\n for the Protection of National Infrastructure (CPNI).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to 6274 algorithm delivery http identification license policies subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6396","type":"specification","body":"IETF","designation":"RFC 6396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6396.txt","https://www.rfc-editor.org/rfc/rfc6396.pdf"],"folder":"IETF/RFC-6396","files":{"txt":{"path":"standards/IETF/RFC-6396/RFC-6396.txt","sha256":"415c96368320e94eaed7dd17d024a83c516beb0ac98653ec80ddcc1921d22ef7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the MRT format for routing information\n export. This format was developed in concert with the Multi-threaded\n Routing Toolkit (MRT) from whence the format takes it name. The\n format can be used to export routing protocol messages, state\n changes, and routing information base contents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6396.\n\nCopyright Notice\n\n Copyri","scope_keywords":["6396","http","license","presentation","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 6396 This document describes the MRT format for routing information\n export. This format was developed in concert with the Multi-threaded\n Routing Toolkit (MRT) from whence the format takes it name. The\n format can be used to export routing protocol messages, state\n changes, and routing information base contents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6396.\n\nCopyright Notice\n\n Copyri 6396 http license presentation subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6491","type":"specification","body":"IETF","designation":"RFC 6491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6491.txt","https://www.rfc-editor.org/rfc/rfc6491.pdf"],"folder":"IETF/RFC-6491","files":{"txt":{"path":"standards/IETF/RFC-6491/RFC-6491.txt","sha256":"eb68bea28b495d28f8e87f5fc179ceb4b56987536d3c8d06bf2fbba3706b5acc"}},"tags":["nested-reference","unchanged"],"summary":"This document provides specific direction to IANA as to the Resource\n Public Key Infrastructure (RPKI) objects it should issue.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6491.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating","scope_keywords":["6491","attestation","attribute","attributes","authorization","certificate","certificates","crl","holder","http","key","license","management","pki","policy","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null}],"search_text":"IETF RFC 6491 This document provides specific direction to IANA as to the Resource\n Public Key Infrastructure (RPKI) objects it should issue.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6491.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating 6491 attestation attribute attributes authorization certificate certificates crl holder http key license management pki policy revocation nested-reference unchanged"},{"id":"IETF RFC 6621","type":"specification","body":"IETF","designation":"RFC 6621","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6621.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6621.txt","https://www.rfc-editor.org/rfc/rfc6621.pdf"],"folder":"IETF/RFC-6621","files":{"txt":{"path":"standards/IETF/RFC-6621/RFC-6621.txt","sha256":"4003c4d49bbd1b450701e24c13f4a1ddbf8834afb249dd96ee5f9f18d64ee4d4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Simplified Multicast Forwarding (SMF)\n mechanism that provides basic Internet Protocol (IP) multicast\n forwarding suitable for limited wireless mesh and mobile ad hoc\n network (MANET) use. It is mainly applicable in situations where\n efficient flooding represents an acceptable engineering design trade-\n off. It defines techniques for multicast duplicate packet detection\n (DPD), to be applied in the forwarding process, for both IPv4 and\n IPv6 protocol use. This document also specifies optional mechanisms\n for using reduced relay sets to achieve more efficient multicast data\n distribution within a mesh topology as compared to Classic Flooding.\n Interactions with other protocols, such as use of information\n provided by concurrently running unicast routing protocols or\n interaction with other multicast protocols, as well as multiple\n deployment approaches are also d","scope_keywords":["6621","algorithm","algorithms","hash","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null}],"search_text":"IETF RFC 6621 This document describes a Simplified Multicast Forwarding (SMF)\n mechanism that provides basic Internet Protocol (IP) multicast\n forwarding suitable for limited wireless mesh and mobile ad hoc\n network (MANET) use. It is mainly applicable in situations where\n efficient flooding represents an acceptable engineering design trade-\n off. It defines techniques for multicast duplicate packet detection\n (DPD), to be applied in the forwarding process, for both IPv4 and\n IPv6 protocol use. This document also specifies optional mechanisms\n for using reduced relay sets to achieve more efficient multicast data\n distribution within a mesh topology as compared to Classic Flooding.\n Interactions with other protocols, such as use of information\n provided by concurrently running unicast routing protocols or\n interaction with other multicast protocols, as well as multiple\n deployment approaches are also d 6621 algorithm algorithms hash http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 6733","type":"specification","body":"IETF","designation":"RFC 6733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6733.txt","https://www.rfc-editor.org/rfc/rfc6733.pdf"],"folder":"IETF/RFC-6733","files":{"txt":{"path":"standards/IETF/RFC-6733/RFC-6733.txt","sha256":"b0117adedd43f9f44e444f64cd7360709c351aa27ea288d9c664c2800da8fa26"}},"tags":["nested-reference","unchanged"],"summary":"The Diameter base protocol is intended to provide an Authentication,\n Authorization, and Accounting (AAA) framework for applications such\n as network access or IP mobility in both local and roaming\n situations. This document specifies the message format, transport,\n error reporting, accounting, and security services used by all\n Diameter applications. The Diameter base protocol as defined in this\n document obsoletes RFC 3588 and RFC 5719, and it must be supported by\n all new Diameter implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC ","scope_keywords":["6733","algorithm","authentication","authorization","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6737","folder":"IETF/RFC-6737","source":"IETF/RFC-6737/RFC-6737.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 6733 The Diameter base protocol is intended to provide an Authentication,\n Authorization, and Accounting (AAA) framework for applications such\n as network access or IP mobility in both local and roaming\n situations. This document specifies the message format, transport,\n error reporting, accounting, and security services used by all\n Diameter applications. The Diameter base protocol as defined in this\n document obsoletes RFC 3588 and RFC 5719, and it must be supported by\n all new Diameter implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC  6733 algorithm authentication authorization http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6846","type":"specification","body":"IETF","designation":"RFC 6846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6846.txt","https://www.rfc-editor.org/rfc/rfc6846.pdf"],"folder":"IETF/RFC-6846","files":{"txt":{"path":"standards/IETF/RFC-6846/RFC-6846.txt","sha256":"16caa76858ac1ad3f8d1f93ca96b4f5097e8d7c349673010711afe12834928b6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a RObust Header Compression (ROHC) profile\n for compression of TCP/IP packets. The profile, called ROHC-TCP,\n provides efficient and robust compression of TCP headers, including\n frequently used TCP options such as selective acknowledgments (SACKs)\n and Timestamps.\n\n ROHC-TCP works well when used over links with significant error rates\n and long round-trip times. For many bandwidth-limited links where\n header compression is essential, such characteristics are common.\n\n This specification obsoletes RFC 4996. It fixes a technical issue\n with the SACK compression and clarifies other compression methods\n used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publicat","scope_keywords":["6846","http","license","profile","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6846 This document specifies a RObust Header Compression (ROHC) profile\n for compression of TCP/IP packets. The profile, called ROHC-TCP,\n provides efficient and robust compression of TCP headers, including\n frequently used TCP options such as selective acknowledgments (SACKs)\n and Timestamps.\n\n ROHC-TCP works well when used over links with significant error rates\n and long round-trip times. For many bandwidth-limited links where\n header compression is essential, such characteristics are common.\n\n This specification obsoletes RFC 4996. It fixes a technical issue\n with the SACK compression and clarifies other compression methods\n used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publicat 6846 http license profile subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7277","type":"specification","body":"IETF","designation":"RFC 7277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7277.txt","https://www.rfc-editor.org/rfc/rfc7277.pdf"],"folder":"IETF/RFC-7277","files":{"txt":{"path":"standards/IETF/RFC-7277/RFC-7277.txt","sha256":"938d908ff06aadb2109992a21be2742cdb197caa904cdfc00d2aebf8a609968f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG data model for management of IP\n implementations. The data model includes configuration data and\n state data.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7277.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisio","scope_keywords":["7277","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null}],"search_text":"IETF RFC 7277 This document defines a YANG data model for management of IP\n implementations. The data model includes configuration data and\n state data.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7277.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisio 7277 http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7325","type":"specification","body":"IETF","designation":"RFC 7325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7325.txt","https://www.rfc-editor.org/rfc/rfc7325.pdf"],"folder":"IETF/RFC-7325","files":{"txt":{"path":"standards/IETF/RFC-7325/RFC-7325.txt","sha256":"ba435b305682f1faabe413090363a96a06a99d76da1f6d6cf58b51955f1d3473"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for implementers regarding MPLS\n forwarding and a basis for evaluations of forwarding implementations.\n Guidelines cover many aspects of MPLS forwarding. Topics are\n highlighted where implementers might otherwise overlook practical\n requirements that are unstated or underemphasized, or that are\n optional for conformance to RFCs but often considered mandatory by\n providers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of","scope_keywords":["7325","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null}],"search_text":"IETF RFC 7325 This document provides guidelines for implementers regarding MPLS\n forwarding and a basis for evaluations of forwarding implementations.\n Guidelines cover many aspects of MPLS forwarding. Topics are\n highlighted where implementers might otherwise overlook practical\n requirements that are unstated or underemphasized, or that are\n optional for conformance to RFCs but often considered mandatory by\n providers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of 7325 delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7450","type":"specification","body":"IETF","designation":"RFC 7450","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7450.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7450.txt","https://www.rfc-editor.org/rfc/rfc7450.pdf"],"folder":"IETF/RFC-7450","files":{"txt":{"path":"standards/IETF/RFC-7450/RFC-7450.txt","sha256":"2626bf3dded4b2b9f5650d394a1afda4c7f2c8bd0dfbd5b99c22d88999428ad6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Automatic Multicast Tunneling (AMT), a\n protocol for delivering multicast traffic from sources in a\n multicast-enabled network to receivers that lack multicast\n connectivity to the source network. The protocol uses UDP\n encapsulation and unicast replication to provide this functionality.\n\n The AMT protocol is specifically designed to support rapid deployment\n by requiring minimal changes to existing network infrastructure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this do","scope_keywords":["7450","http","license","pid","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 7450 This document describes Automatic Multicast Tunneling (AMT), a\n protocol for delivering multicast traffic from sources in a\n multicast-enabled network to receivers that lack multicast\n connectivity to the source network. The protocol uses UDP\n encapsulation and unicast replication to provide this functionality.\n\n The AMT protocol is specifically designed to support rapid deployment\n by requiring minimal changes to existing network infrastructure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this do 7450 http license pid policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7679","type":"specification","body":"IETF","designation":"RFC 7679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7679.txt","https://www.rfc-editor.org/rfc/rfc7679.pdf"],"folder":"IETF/RFC-7679","files":{"txt":{"path":"standards/IETF/RFC-7679/RFC-7679.txt","sha256":"b41933c0150414361962b95b8bd03bd067702ffb744d50516fbecb0ce2fecc11"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a metric for one-way delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IP Performance Metrics (IPPM) Framework document, RFC 2330; the\n reader is assumed to be familiar with that document. This memo makes\n RFC 2679 obsolete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7679.\n\nAlmes, et al. Standards Track [Page 1]\n\f\nRFC 76","scope_keywords":["7679","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 7679 This memo defines a metric for one-way delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IP Performance Metrics (IPPM) Framework document, RFC 2330; the\n reader is assumed to be familiar with that document. This memo makes\n RFC 2679 obsolete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7679.\n\nAlmes, et al. Standards Track [Page 1]\n\f\nRFC 76 7679 http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7680","type":"specification","body":"IETF","designation":"RFC 7680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7680.txt","https://www.rfc-editor.org/rfc/rfc7680.pdf"],"folder":"IETF/RFC-7680","files":{"txt":{"path":"standards/IETF/RFC-7680/RFC-7680.txt","sha256":"f71c66e48c0cbfa5791b66edc75bcff596848dba4cd36e775766669f60ad68b7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a metric for one-way loss of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IP Performance Metrics (IPPM) Framework document, RFC 2330; the\n reader is assumed to be familiar with that document. This memo makes\n RFC 2680 obsolete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7680.\n\nAlmes, et al. Standards Track [Page 1]\n\f\nRFC 768","scope_keywords":["7680","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 7680 This memo defines a metric for one-way loss of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IP Performance Metrics (IPPM) Framework document, RFC 2330; the\n reader is assumed to be familiar with that document. This memo makes\n RFC 2680 obsolete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7680.\n\nAlmes, et al. Standards Track [Page 1]\n\f\nRFC 768 7680 http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7755","type":"specification","body":"IETF","designation":"RFC 7755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7755.txt","https://www.rfc-editor.org/rfc/rfc7755.pdf"],"folder":"IETF/RFC-7755","files":{"txt":{"path":"standards/IETF/RFC-7755/RFC-7755.txt","sha256":"409d09257611a096cfb7c7f3e99fa85c3beaf374b39c1885cc978bc8e0fe2406"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Stateless IP/ICMP Translation\n Algorithm (SIIT) in an IPv6 Internet Data Center (IDC). In this\n deployment model, traffic from legacy IPv4-only clients on the\n Internet is translated to IPv6 upon reaching the IDC operator's\n network infrastructure. From that point on, it may be treated the\n same as traffic from native IPv6 end users. The IPv6 endpoints may\n be numbered using arbitrary (non-IPv4-translatable) IPv6 addresses.\n This facilitates a single-stack IPv6-only network infrastructure, as\n well as efficient utilization of public IPv4 addresses.\n\n The primary audience is IDC operators who are deploying IPv6, running\n out of available IPv4 addresses, and/or feeling that dual stack\n causes undesirable operational complexity.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pur","scope_keywords":["7755","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null}],"search_text":"IETF RFC 7755 This document describes the use of the Stateless IP/ICMP Translation\n Algorithm (SIIT) in an IPv6 Internet Data Center (IDC). In this\n deployment model, traffic from legacy IPv4-only clients on the\n Internet is translated to IPv6 upon reaching the IDC operator's\n network infrastructure. From that point on, it may be treated the\n same as traffic from native IPv6 end users. The IPv6 endpoints may\n be numbered using arbitrary (non-IPv4-translatable) IPv6 addresses.\n This facilitates a single-stack IPv6-only network infrastructure, as\n well as efficient utilization of public IPv4 addresses.\n\n The primary audience is IDC operators who are deploying IPv6, running\n out of available IPv4 addresses, and/or feeling that dual stack\n causes undesirable operational complexity.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pur 7755 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8126","type":"specification","body":"IETF","designation":"RFC 8126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8126.txt","https://www.rfc-editor.org/rfc/rfc8126.pdf"],"folder":"IETF/RFC-8126","files":{"txt":{"path":"standards/IETF/RFC-8126/RFC-8126.txt","sha256":"b8b5cc1e61e78352b5a12c4a92fa0573b3400d49522a448913455a478dd87401"}},"tags":["nested-reference","unchanged"],"summary":"Many protocols make use of points of extensibility that use constants\n to identify various protocol parameters. To ensure that the values\n in these fields do not have conflicting uses and to promote\n interoperability, their allocations are often coordinated by a\n central record keeper. For IETF protocols, that role is filled by\n the Internet Assigned Numbers Authority (IANA).\n\n To make assignments in a given registry prudently, guidance\n describing the conditions under which new values should be assigned,\n as well as when and how modifications to existing values can be made,\n is needed. This document defines a framework for the documentation\n of these guidelines by specification authors, in order to assure that\n the provided guidance for the IANA Considerations is clear and\n addresses the various issues that are likely in the operation of a\n registry.\n\n This is the third edition of this ","scope_keywords":["8126","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8391","folder":"IETF/RFC-8391","source":"IETF/RFC-8391/RFC-8391.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 8126 Many protocols make use of points of extensibility that use constants\n to identify various protocol parameters. To ensure that the values\n in these fields do not have conflicting uses and to promote\n interoperability, their allocations are often coordinated by a\n central record keeper. For IETF protocols, that role is filled by\n the Internet Assigned Numbers Authority (IANA).\n\n To make assignments in a given registry prudently, guidance\n describing the conditions under which new values should be assigned,\n as well as when and how modifications to existing values can be made,\n is needed. This document defines a framework for the documentation\n of these guidelines by specification authors, in order to assure that\n the provided guidance for the IANA Considerations is clear and\n addresses the various issues that are likely in the operation of a\n registry.\n\n This is the third edition of this  8126 http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8200","type":"specification","body":"IETF","designation":"RFC 8200","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8200.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8200.txt","https://www.rfc-editor.org/rfc/rfc8200.pdf"],"folder":"IETF/RFC-8200","files":{"txt":{"path":"standards/IETF/RFC-8200/RFC-8200.txt","sha256":"371ae3f133d562db5d6385e6def4ca9914c4f831be228ea7779fd28799c2f490"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 6 of the Internet Protocol (IPv6).\n It obsoletes RFC 2460.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8200.\n\nDeering & Hinden Standards Track [Page 1]\n\f\nRFC 8200 IPv6 Specification July 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 a","scope_keywords":["8200","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8200 This document specifies version 6 of the Internet Protocol (IPv6).\n It obsoletes RFC 2460.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8200.\n\nDeering & Hinden Standards Track [Page 1]\n\f\nRFC 8200 IPv6 Specification July 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 a 8200 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8261","type":"specification","body":"IETF","designation":"RFC 8261","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8261.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8261.txt","https://www.rfc-editor.org/rfc/rfc8261.pdf"],"folder":"IETF/RFC-8261","files":{"txt":{"path":"standards/IETF/RFC-8261/RFC-8261.txt","sha256":"881cf70aa89eb521588a6b27b74276b0b0478178c146048ace7fcae48c791730"}},"tags":["nested-reference","unchanged"],"summary":"The Stream Control Transmission Protocol (SCTP) is a transport\n protocol originally defined to run on top of the network protocols\n IPv4 or IPv6. This document specifies how SCTP can be used on top of\n the Datagram Transport Layer Security (DTLS) protocol. Using the\n encapsulation method described in this document, SCTP is unaware of\n the protocols being used below DTLS; hence, explicit IP addresses\n cannot be used in the SCTP control chunks. As a consequence, the\n SCTP associations carried over DTLS can only be single-homed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai","scope_keywords":["8261","algorithm","authentication","http","https","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 8261 The Stream Control Transmission Protocol (SCTP) is a transport\n protocol originally defined to run on top of the network protocols\n IPv4 or IPv6. This document specifies how SCTP can be used on top of\n the Datagram Transport Layer Security (DTLS) protocol. Using the\n encapsulation method described in this document, SCTP is unaware of\n the protocols being used below DTLS; hence, explicit IP addresses\n cannot be used in the SCTP control chunks. As a consequence, the\n SCTP associations carried over DTLS can only be single-homed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai 8261 algorithm authentication http https key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8344","type":"specification","body":"IETF","designation":"RFC 8344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8344.txt","https://www.rfc-editor.org/rfc/rfc8344.pdf"],"folder":"IETF/RFC-8344","files":{"txt":{"path":"standards/IETF/RFC-8344/RFC-8344.txt","sha256":"dde6240aaebdf8f61e979f0201e3952bd952f9415b03953f14bc11c70edbcdbc"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG data model for management of IP\n implementations. The data model includes configuration and system\n state.\n\n The YANG data model in this document conforms to the Network\n Management Datastore Architecture defined in RFC 8342.\n\n This document obsoletes RFC 7277.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8344.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF ","scope_keywords":["8344","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 8344 This document defines a YANG data model for management of IP\n implementations. The data model includes configuration and system\n state.\n\n The YANG data model in this document conforms to the Network\n Management Datastore Architecture defined in RFC 8342.\n\n This document obsoletes RFC 7277.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8344.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF  8344 http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8489","type":"specification","body":"IETF","designation":"RFC 8489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8489.txt","https://www.rfc-editor.org/rfc/rfc8489.pdf"],"folder":"IETF/RFC-8489","files":{"txt":{"path":"standards/IETF/RFC-8489/RFC-8489.txt","sha256":"3a1c97ec36576fda83b5f39fbe1d033c6c0b934e2209a29bb21b9ace57ef4289"}},"tags":["nested-reference","unchanged"],"summary":"Session Traversal Utilities for NAT (STUN) is a protocol that serves\n as a tool for other protocols in dealing with NAT traversal. It can\n be used by an endpoint to determine the IP address and port allocated\n to it by a NAT. It can also be used to check connectivity between\n two endpoints and as a keep-alive protocol to maintain NAT bindings.\n STUN works with many existing NATs and does not require any special\n behavior from them.\n\n STUN is not a NAT traversal solution by itself. Rather, it is a tool\n to be used in the context of a NAT traversal solution.\n\n This document obsoletes RFC 5389.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri","scope_keywords":["8489","algorithm","algorithms","attribute","attributes","authentication","credential","hash","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8489 Session Traversal Utilities for NAT (STUN) is a protocol that serves\n as a tool for other protocols in dealing with NAT traversal. It can\n be used by an endpoint to determine the IP address and port allocated\n to it by a NAT. It can also be used to check connectivity between\n two endpoints and as a keep-alive protocol to maintain NAT bindings.\n STUN works with many existing NATs and does not require any special\n behavior from them.\n\n STUN is not a NAT traversal solution by itself. Rather, it is a tool\n to be used in the context of a NAT traversal solution.\n\n This document obsoletes RFC 5389.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri 8489 algorithm algorithms attribute attributes authentication credential hash http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8782","type":"specification","body":"IETF","designation":"RFC 8782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8782.txt","https://www.rfc-editor.org/rfc/rfc8782.pdf"],"folder":"IETF/RFC-8782","files":{"pdf":{"path":"standards/IETF/RFC-8782/RFC-8782.pdf","sha256":"13da67cae4f46deb4a847c8f1f020dc15c767f3758d23e3fe1efab853f6c2c0e"},"txt":{"path":"standards/IETF/RFC-8782/RFC-8782.txt","sha256":"2930505a46c124f8a2c75aae248cde2711646ace5e49b8f87f5414352e10a2ac"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Distributed Denial-of-Service Open Threat\n Signaling (DOTS) signal channel, a protocol for signaling the need\n for protection against Distributed Denial-of-Service (DDoS) attacks\n to a server capable of enabling network traffic mitigation on behalf\n of the requesting client.\n\n A companion document defines the DOTS data channel, a separate\n reliable communication layer for DOTS management and configuration\n purposes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this docum","scope_keywords":["8782","authentication","authorization","http","https","key","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8903","folder":"IETF/RFC-8903","source":"IETF/RFC-8903/RFC-8903.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8782 This document specifies the Distributed Denial-of-Service Open Threat\n Signaling (DOTS) signal channel, a protocol for signaling the need\n for protection against Distributed Denial-of-Service (DDoS) attacks\n to a server capable of enabling network traffic mitigation on behalf\n of the requesting client.\n\n A companion document defines the DOTS data channel, a separate\n reliable communication layer for DOTS management and configuration\n purposes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this docum 8782 authentication authorization http https key license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9132","type":"specification","body":"IETF","designation":"RFC 9132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9132.txt","https://www.rfc-editor.org/rfc/rfc9132.pdf"],"folder":"IETF/RFC-9132","files":{"pdf":{"path":"standards/IETF/RFC-9132/RFC-9132.pdf","sha256":"0da6b1a2296c3c3d1e7792417ae47ee10a0742c95dd5bd324b4d174db531e0a2"},"txt":{"path":"standards/IETF/RFC-9132/RFC-9132.txt","sha256":"95c68785fbfc0dce78ca14da6f0c073802dc3581529970fa2962925f62135222"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Distributed Denial-of-Service Open Threat\n Signaling (DOTS) signal channel, a protocol for signaling the need\n for protection against Distributed Denial-of-Service (DDoS) attacks\n to a server capable of enabling network traffic mitigation on behalf\n of the requesting client.\n\n A companion document defines the DOTS data channel, a separate\n reliable communication layer for DOTS management and configuration\n purposes.\n\n This document obsoletes RFC 8782.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information ab","scope_keywords":["9132","authentication","authorization","http","https","key","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 9132 This document specifies the Distributed Denial-of-Service Open Threat\n Signaling (DOTS) signal channel, a protocol for signaling the need\n for protection against Distributed Denial-of-Service (DDoS) attacks\n to a server capable of enabling network traffic mitigation on behalf\n of the requesting client.\n\n A companion document defines the DOTS data channel, a separate\n reliable communication layer for DOTS management and configuration\n purposes.\n\n This document obsoletes RFC 8782.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information ab 9132 authentication authorization http https key license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9525","type":"specification","body":"IETF","designation":"RFC 9525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9525.txt","https://www.rfc-editor.org/rfc/rfc9525.pdf"],"folder":"IETF/RFC-9525","files":{"pdf":{"path":"standards/IETF/RFC-9525/RFC-9525.pdf","sha256":"2dbecc01ab8c16a49a02e1390e469107abc002d723f07e76c25a9660b9ee55c6"},"txt":{"path":"standards/IETF/RFC-9525/RFC-9525.txt","sha256":"ed8116c2435376dffe37ec2ca688c3a8515e36820852b29e0b6cdfbe92abd2c5"}},"tags":["nested-reference","unchanged"],"summary":"Many application technologies enable secure communication between two\n entities by means of Transport Layer Security (TLS) with Internet\n Public Key Infrastructure using X.509 (PKIX) certificates. This\n document specifies procedures for representing and verifying the\n identity of application services in such interactions.\n\n This document obsoletes RFC 6125.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-","scope_keywords":["9525","authentication","certificate","certificates","credential","credentials","http","https","key","license","path","pki","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9525 Many application technologies enable secure communication between two\n entities by means of Transport Layer Security (TLS) with Internet\n Public Key Infrastructure using X.509 (PKIX) certificates. This\n document specifies procedures for representing and verifying the\n identity of application services in such interactions.\n\n This document obsoletes RFC 6125.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc- 9525 authentication certificate certificates credential credentials http https key license path pki profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 0792","type":"specification","body":"IETF","designation":"RFC 0792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0792.txt","https://www.rfc-editor.org/rfc/rfc0792.pdf"],"folder":"IETF/RFC-0792","files":{"txt":{"path":"standards/IETF/RFC-0792/RFC-0792.txt","sha256":"58714393ded142bacf188d7e8977eef98f4110c4c87ac94595f750df5664c2c6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 792 ISI\n September 1981\nUpdates: RFCs 777, 760\nUpdates: IENs 109, 128\n\n INTERNET CONTROL MESSAGE PROTOCOL\n\n DARPA INTERNET PROGRAM\n PROTOCOL SPECIFICATION\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be imp","scope_keywords":["0792","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 0792 Network Working Group J. Postel\nRequest for Comments: 792 ISI\n September 1981\nUpdates: RFCs 777, 760\nUpdates: IENs 109, 128\n\n INTERNET CONTROL MESSAGE PROTOCOL\n\n DARPA INTERNET PROGRAM\n PROTOCOL SPECIFICATION\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be imp 0792 identification nested-reference unchanged"},{"id":"IETF RFC 4562","type":"specification","body":"IETF","designation":"RFC 4562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4562.txt","https://www.rfc-editor.org/rfc/rfc4562.pdf"],"folder":"IETF/RFC-4562","files":{"txt":{"path":"standards/IETF/RFC-4562/RFC-4562.txt","sha256":"b10c43aad96c7bff3a21225af54d6753929c85d8f00cde37dcdb9a75becfd6fd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to ensure layer-2 separation of\n Local Area Network (LAN) stations accessing an IPv4 gateway over a\n bridged Ethernet segment.\n\n The mechanism - called \"MAC-Forced Forwarding\" - implements an\n Address Resolution Protocol (ARP) proxy function that prohibits\n Ethernet Media Access Control (MAC) address resolution between hosts\n located within the same IPv4 subnet but at different customer\n premises, and in effect directs all upstream traffic to an IPv4\n gateway. The IPv4 gateway provides IP-layer connectivity between\n these same hosts.\n\nMelsen & Blake Informational [Page 1]\n\f\nRFC 4562 MAC-Forced Forwarding June 2006","scope_keywords":["4562","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null}],"search_text":"IETF RFC 4562 This document describes a mechanism to ensure layer-2 separation of\n Local Area Network (LAN) stations accessing an IPv4 gateway over a\n bridged Ethernet segment.\n\n The mechanism - called \"MAC-Forced Forwarding\" - implements an\n Address Resolution Protocol (ARP) proxy function that prohibits\n Ethernet Media Access Control (MAC) address resolution between hosts\n located within the same IPv4 subnet but at different customer\n premises, and in effect directs all upstream traffic to an IPv4\n gateway. The IPv4 gateway provides IP-layer connectivity between\n these same hosts.\n\nMelsen & Blake Informational [Page 1]\n\f\nRFC 4562 MAC-Forced Forwarding June 2006 4562 path nested-reference unchanged"},{"id":"IETF RFC 4884","type":"specification","body":"IETF","designation":"RFC 4884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4884.txt","https://www.rfc-editor.org/rfc/rfc4884.pdf"],"folder":"IETF/RFC-4884","files":{"txt":{"path":"standards/IETF/RFC-4884/RFC-4884.txt","sha256":"2afeccf14f2c84aab67e8882a5b2d5167486782a9d42935557810247abe16f8f"}},"tags":["nested-reference","unchanged"],"summary":"This document redefines selected ICMP messages to support multi-part\n operation. A multi-part ICMP message carries all of the information\n that ICMP messages carried previously, as well as additional\n information that applications may require.\n\n Multi-part messages are supported by an ICMP extension structure.\n The extension structure is situated at the end of the ICMP message.\n It includes an extension header followed by one or more extension\n objects. Each extension object contains an object header and object\n payload. All object headers share a common format.\n\n This document further redefines the above mentioned ICMP messages by\n specifying a length attribute. All of the currently defined ICMP\n messages to which an extension structure can be appended include an\n \"original datagram\" field. The \"original datagram\" field contains\n the initial octets of the datagram that elicited the ICMP","scope_keywords":["4884","attribute","attributes","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 4884 This document redefines selected ICMP messages to support multi-part\n operation. A multi-part ICMP message carries all of the information\n that ICMP messages carried previously, as well as additional\n information that applications may require.\n\n Multi-part messages are supported by an ICMP extension structure.\n The extension structure is situated at the end of the ICMP message.\n It includes an extension header followed by one or more extension\n objects. Each extension object contains an object header and object\n payload. All object headers share a common format.\n\n This document further redefines the above mentioned ICMP messages by\n specifying a length attribute. All of the currently defined ICMP\n messages to which an extension structure can be appended include an\n \"original datagram\" field. The \"original datagram\" field contains\n the initial octets of the datagram that elicited the ICMP 4884 attribute attributes key trust nested-reference unchanged"},{"id":"IETF RFC 5085","type":"specification","body":"IETF","designation":"RFC 5085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5085.txt","https://www.rfc-editor.org/rfc/rfc5085.pdf"],"folder":"IETF/RFC-5085","files":{"txt":{"path":"standards/IETF/RFC-5085/RFC-5085.txt","sha256":"9a76e5c08dac8c7306e681cb034ecf716997f063f838b775cb85ccabd861dd17"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Virtual Circuit Connectivity Verification\n (VCCV), which provides a control channel that is associated with a\n pseudowire (PW), as well as the corresponding operations and\n management functions (such as connectivity verification) to be used\n over that control channel. VCCV applies to all supported access\n circuit and transport types currently defined for PWs.\n\nNadeau & Pignataro Standards Track [Page 1]\n\f\nRFC 5085 PW VCCV December 2007","scope_keywords":["5085","attribute","attributes","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5085 This document describes Virtual Circuit Connectivity Verification\n (VCCV), which provides a control channel that is associated with a\n pseudowire (PW), as well as the corresponding operations and\n management functions (such as connectivity verification) to be used\n over that control channel. VCCV applies to all supported access\n circuit and transport types currently defined for PWs.\n\nNadeau & Pignataro Standards Track [Page 1]\n\f\nRFC 5085 PW VCCV December 2007 5085 attribute attributes management path nested-reference unchanged"},{"id":"IETF RFC 5461","type":"specification","body":"IETF","designation":"RFC 5461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5461.txt","https://www.rfc-editor.org/rfc/rfc5461.pdf"],"folder":"IETF/RFC-5461","files":{"txt":{"path":"standards/IETF/RFC-5461/RFC-5461.txt","sha256":"c66c4784b5246178454a1fcefc1d0491cbe39b36c051c19755bb6847e5695f31"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a non-standard, but widely implemented,\n modification to TCP's handling of ICMP soft error messages that\n rejects pending connection-requests when those error messages are\n received. This behavior reduces the likelihood of long delays\n between connection-establishment attempts that may arise in a number\n of scenarios, including one in which dual-stack nodes that have IPv6\n enabled by default are deployed in IPv4 or mixed IPv4 and IPv6\n environments.\n\nGont Informational [Page 1]\n\f\nRFC 5461 TCP's Reaction to Soft Errors February 2009","scope_keywords":["5461","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 5461 This document describes a non-standard, but widely implemented,\n modification to TCP's handling of ICMP soft error messages that\n rejects pending connection-requests when those error messages are\n received. This behavior reduces the likelihood of long delays\n between connection-establishment attempts that may arise in a number\n of scenarios, including one in which dual-stack nodes that have IPv6\n enabled by default are deployed in IPv4 or mixed IPv4 and IPv6\n environments.\n\nGont Informational [Page 1]\n\f\nRFC 5461 TCP's Reaction to Soft Errors February 2009 5461 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5837","type":"specification","body":"IETF","designation":"RFC 5837","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5837.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5837.txt","https://www.rfc-editor.org/rfc/rfc5837.pdf"],"folder":"IETF/RFC-5837","files":{"txt":{"path":"standards/IETF/RFC-5837/RFC-5837.txt","sha256":"0e9e72b7e8e13c01bb9e8961a82c36748a7e71fc3a8f5af31356a68ab0eddeaf"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a data structure that can be appended to selected\n ICMP messages. The ICMP extension defined herein can be used to\n identify any combination of the following: the IP interface upon\n which a datagram arrived, the sub-IP component of an IP interface\n upon which a datagram arrived, the IP interface through which the\n datagram would have been forwarded had it been forwardable, and the\n IP next hop to which the datagram would have been forwarded.\n\n Devices can use this ICMP extension to identify interfaces and their\n components by any combination of the following: ifIndex, IPv4\n address, IPv6 address, name, and MTU. ICMP-aware devices can use\n these extensions to identify both numbered and unnumbered interfaces.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the c","scope_keywords":["5837","http","identification","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5837 This memo defines a data structure that can be appended to selected\n ICMP messages. The ICMP extension defined herein can be used to\n identify any combination of the following: the IP interface upon\n which a datagram arrived, the sub-IP component of an IP interface\n upon which a datagram arrived, the IP interface through which the\n datagram would have been forwarded had it been forwardable, and the\n IP next hop to which the datagram would have been forwarded.\n\n Devices can use this ICMP extension to identify interfaces and their\n components by any combination of the following: ifIndex, IPv4\n address, IPv6 address, name, and MTU. ICMP-aware devices can use\n these extensions to identify both numbered and unnumbered interfaces.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the c 5837 http identification license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6115","type":"specification","body":"IETF","designation":"RFC 6115","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6115.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6115.txt","https://www.rfc-editor.org/rfc/rfc6115.pdf"],"folder":"IETF/RFC-6115","files":{"txt":{"path":"standards/IETF/RFC-6115/RFC-6115.txt","sha256":"cce828afb943b5b52f85f2f0c0249e5db0d35f991ffda4dffa39b51336b5e8a3"}},"tags":["nested-reference","unchanged"],"summary":"It is commonly recognized that the Internet routing and addressing\n architecture is facing challenges in scalability, multihoming, and\n inter-domain traffic engineering. This document presents, as a\n recommendation of future directions for the IETF, solutions that\n could aid the future scalability of the Internet. To this end, this\n document surveys many of the proposals that were brought forward for\n discussion in this activity, as well as some of the subsequent\n analysis and the architectural recommendation of the chairs. This\n document is a product of the Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results mi","scope_keywords":["6115","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6115 It is commonly recognized that the Internet routing and addressing\n architecture is facing challenges in scalability, multihoming, and\n inter-domain traffic engineering. This document presents, as a\n recommendation of future directions for the IETF, solutions that\n could aid the future scalability of the Internet. To this end, this\n document surveys many of the proposals that were brought forward for\n discussion in this activity, as well as some of the subsequent\n analysis and the architectural recommendation of the chairs. This\n document is a product of the Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results mi 6115 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7588","type":"specification","body":"IETF","designation":"RFC 7588","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7588.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7588.txt","https://www.rfc-editor.org/rfc/rfc7588.pdf"],"folder":"IETF/RFC-7588","files":{"txt":{"path":"standards/IETF/RFC-7588/RFC-7588.txt","sha256":"bf333c989a5c32f308e7a7a5513f1c33eb2503ace98ba981bb60c71f7c3fac78"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how many vendors have solved the Generic Routing\n Encapsulation (GRE) fragmentation problem. The solution described\n herein is configurable. It is widely deployed on the Internet in its\n default configuration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7588.\n\nBoni","scope_keywords":["7588","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7588 This memo describes how many vendors have solved the Generic Routing\n Encapsulation (GRE) fragmentation problem. The solution described\n herein is configurable. It is widely deployed on the Internet in its\n default configuration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7588.\n\nBoni 7588 delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7599","type":"specification","body":"IETF","designation":"RFC 7599","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7599.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7599.txt","https://www.rfc-editor.org/rfc/rfc7599.pdf"],"folder":"IETF/RFC-7599","files":{"txt":{"path":"standards/IETF/RFC-7599/RFC-7599.txt","sha256":"40af8f5c56e69f30aba2f8cea66f113672d183bffa7a476c9f2ea75384817333"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the solution architecture based on \"Mapping\n of Address and Port\" stateless IPv6-IPv4 Network Address Translation\n (NAT64) for providing shared or non-shared IPv4 address connectivity\n to and across an IPv6 network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7599.\n\nLi, et al. Standards Track [Page 1]\n\f\nRFC 7599 MAP-T July 2015\n\nCopyright Notice\n\n Copyright (c","scope_keywords":["7599","algorithm","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 7599 This document specifies the solution architecture based on \"Mapping\n of Address and Port\" stateless IPv6-IPv4 Network Address Translation\n (NAT64) for providing shared or non-shared IPv4 address connectivity\n to and across an IPv6 network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7599.\n\nLi, et al. Standards Track [Page 1]\n\f\nRFC 7599 MAP-T July 2015\n\nCopyright Notice\n\n Copyright (c 7599 algorithm http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7658","type":"specification","body":"IETF","designation":"RFC 7658","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7658.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7658.txt","https://www.rfc-editor.org/rfc/rfc7658.pdf"],"folder":"IETF/RFC-7658","files":{"txt":{"path":"standards/IETF/RFC-7658/RFC-7658.txt","sha256":"312bcc4dafc9ff89173cd0cf2ae339b39f749cfa4cd845611d9592dbea653c54"}},"tags":["nested-reference","unchanged"],"summary":"This memo deprecates MIB module NAT-MIB, a portion of the Management\n Information Base (MIB) previously defined in RFC 4008 for devices\n implementing Network Address Translator (NAT) function. A companion\n document defines a new version, NATV2-MIB, which responds to\n deficiencies found in module NAT-MIB and adds new capabilities.\n\n This document obsoletes RFC 4008. All MIB objects specified in RFC\n 4008 are included in this version unchanged with only the STATUS\n changed to deprecated.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informa","scope_keywords":["7658","algorithm","algorithms","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 7658 This memo deprecates MIB module NAT-MIB, a portion of the Management\n Information Base (MIB) previously defined in RFC 4008 for devices\n implementing Network Address Translator (NAT) function. A companion\n document defines a new version, NATV2-MIB, which responds to\n deficiencies found in module NAT-MIB and adds new capabilities.\n\n This document obsoletes RFC 4008. All MIB objects specified in RFC\n 4008 are included in this version unchanged with only the STATUS\n changed to deprecated.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informa 7658 algorithm algorithms http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8618","type":"specification","body":"IETF","designation":"RFC 8618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8618.txt","https://www.rfc-editor.org/rfc/rfc8618.pdf"],"folder":"IETF/RFC-8618","files":{"txt":{"path":"standards/IETF/RFC-8618/RFC-8618.txt","sha256":"ebb29e0a0ee1c2b0b639d1ec5c9d8dcc2121705adf4a2527f7f0f49e3a8d602b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a data representation for collections of DNS\n messages. The format is designed for efficient storage and\n transmission of large packet captures of DNS traffic; it attempts to\n minimize the size of such packet capture files but retain the full\n DNS message contents along with the most useful transport metadata.\n It is intended to assist with the development of DNS traffic-\n monitoring applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and h","scope_keywords":["8618","algorithm","http","https","license","presentation","signature","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 8618 This document describes a data representation for collections of DNS\n messages. The format is designed for efficient storage and\n transmission of large packet captures of DNS traffic; it attempts to\n minimize the size of such packet capture files but retain the full\n DNS message contents along with the most useful transport metadata.\n It is intended to assist with the development of DNS traffic-\n monitoring applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and h 8618 algorithm http https license presentation signature subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 0793","type":"specification","body":"IETF","designation":"RFC 0793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0793.txt","https://www.rfc-editor.org/rfc/rfc0793.pdf"],"folder":"IETF/RFC-0793","files":{"txt":{"path":"standards/IETF/RFC-0793/RFC-0793.txt","sha256":"e55b1faa35edbeecceb2400233a16ae81897bdf9c31d5b3031e91139e5ea8142"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 793\n \n \n \n \n \n \n \n TRANSMISSION CONTROL PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces .............................................","scope_keywords":["0793"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5513","folder":"IETF/RFC-5513","source":"IETF/RFC-5513/RFC-5513.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7872","folder":"IETF/RFC-7872","source":"IETF/RFC-7872/RFC-7872.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 0793 RFC: 793\n \n \n \n \n \n \n \n TRANSMISSION CONTROL PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces ............................................. 0793 nested-reference unchanged"},{"id":"IETF RFC 4614","type":"specification","body":"IETF","designation":"RFC 4614","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4614.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4614.txt","https://www.rfc-editor.org/rfc/rfc4614.pdf"],"folder":"IETF/RFC-4614","files":{"txt":{"path":"standards/IETF/RFC-4614/RFC-4614.txt","sha256":"aedf6cde7417228e26193fdd31d5f52374ee67ad69b93487096f129490e27961"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a \"roadmap\" to the Requests for Comments (RFC)\n documents relating to the Internet's Transmission Control Protocol\n (TCP). This roadmap provides a brief summary of the documents\n defining TCP and various TCP extensions that have accumulated in the\n RFC series. This serves as a guide and quick reference for both TCP\n implementers and other parties who desire information contained in\n the TCP-related RFCs.\n\nDuke, et al. Informational [Page 1]\n\f\nRFC 4614 TCP Roadmap September 2006","scope_keywords":["4614","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4614 This document contains a \"roadmap\" to the Requests for Comments (RFC)\n documents relating to the Internet's Transmission Control Protocol\n (TCP). This roadmap provides a brief summary of the documents\n defining TCP and various TCP extensions that have accumulated in the\n RFC series. This serves as a guide and quick reference for both TCP\n implementers and other parties who desire information contained in\n the TCP-related RFCs.\n\nDuke, et al. Informational [Page 1]\n\f\nRFC 4614 TCP Roadmap September 2006 4614 key management nested-reference unchanged"},{"id":"IETF RFC 4786","type":"specification","body":"IETF","designation":"RFC 4786","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4786.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4786.txt","https://www.rfc-editor.org/rfc/rfc4786.pdf"],"folder":"IETF/RFC-4786","files":{"txt":{"path":"standards/IETF/RFC-4786/RFC-4786.txt","sha256":"393c7c72a2e9d8675b7b79895e95f1199841eb7de1fd6395640c35dcd9a7588c"}},"tags":["nested-reference","unchanged"],"summary":"As the Internet has grown, and as systems and networked services\n within enterprises have become more pervasive, many services with\n high availability requirements have emerged. These requirements have\n increased the demands on the reliability of the infrastructure on\n which those services rely.\n\n Various techniques have been employed to increase the availability of\n services deployed on the Internet. This document presents commentary\n and recommendations for distribution of services using anycast.\n\nAbley & Lindqvist Best Current Practice [Page 1]\n\f\nRFC 4786 Anycast BCP December 2006","scope_keywords":["4786","identification","management","path","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4786 As the Internet has grown, and as systems and networked services\n within enterprises have become more pervasive, many services with\n high availability requirements have emerged. These requirements have\n increased the demands on the reliability of the infrastructure on\n which those services rely.\n\n Various techniques have been employed to increase the availability of\n services deployed on the Internet. This document presents commentary\n and recommendations for distribution of services using anycast.\n\nAbley & Lindqvist Best Current Practice [Page 1]\n\f\nRFC 4786 Anycast BCP December 2006 4786 identification management path risk trust nested-reference unchanged"},{"id":"IETF RFC 4930","type":"specification","body":"IETF","designation":"RFC 4930","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4930.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4930.txt","https://www.rfc-editor.org/rfc/rfc4930.pdf"],"folder":"IETF/RFC-4930","files":{"txt":{"path":"standards/IETF/RFC-4930/RFC-4930.txt","sha256":"3ce0da2a648ecd76f9483cfa5fca4b4741101103da033cf081db74b25e464639"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration. This document obsoletes RFC 3730.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4930 EPP May 2007","scope_keywords":["4930","authentication","identification","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null}],"search_text":"IETF RFC 4930 This document describes an application layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration. This document obsoletes RFC 3730.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4930 EPP May 2007 4930 authentication identification key management trust nested-reference unchanged"},{"id":"IETF RFC 4934","type":"specification","body":"IETF","designation":"RFC 4934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4934.txt","https://www.rfc-editor.org/rfc/rfc4934.pdf"],"folder":"IETF/RFC-4934","files":{"txt":{"path":"standards/IETF/RFC-4934/RFC-4934.txt","sha256":"f010787e922eea856a5b7855c631bc1a05934f977b17bc45211202ff26890544"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server. This document obsoletes RFC 3734.","scope_keywords":["4934","key","management","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4934 This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server. This document obsoletes RFC 3734. 4934 key management tls trust nested-reference unchanged"},{"id":"IETF RFC 4961","type":"specification","body":"IETF","designation":"RFC 4961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4961.txt","https://www.rfc-editor.org/rfc/rfc4961.pdf"],"folder":"IETF/RFC-4961","files":{"txt":{"path":"standards/IETF/RFC-4961/RFC-4961.txt","sha256":"96746d264f4d9dd4aa410a08905e91bb5897b7784147a55d0da08945862880a3"}},"tags":["nested-reference","unchanged"],"summary":"This document recommends using one UDP port pair for both\n communication directions of bidirectional RTP and RTP Control\n Protocol (RTCP) sessions, commonly called \"symmetric RTP\" and\n \"symmetric RTCP\".","scope_keywords":["4961","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 4961 This document recommends using one UDP port pair for both\n communication directions of bidirectional RTP and RTP Control\n Protocol (RTCP) sessions, commonly called \"symmetric RTP\" and\n \"symmetric RTCP\". 4961 key trust nested-reference unchanged"},{"id":"IETF RFC 4987","type":"specification","body":"IETF","designation":"RFC 4987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4987.txt","https://www.rfc-editor.org/rfc/rfc4987.pdf"],"folder":"IETF/RFC-4987","files":{"txt":{"path":"standards/IETF/RFC-4987/RFC-4987.txt","sha256":"cde4ce998a6c9e34580c27fa5cafdbc4f9b90017b07e0768217bab1b83273d61"}},"tags":["nested-reference","unchanged"],"summary":"This document describes TCP SYN flooding attacks, which have been\n well-known to the community for several years. Various\n countermeasures against these attacks, and the trade-offs of each,\n are described. This document archives explanations of the attack and\n common defense techniques for the benefit of TCP implementers and\n administrators of TCP servers or networks, but does not make any\n standards-level recommendations.","scope_keywords":["4987","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 4987 This document describes TCP SYN flooding attacks, which have been\n well-known to the community for several years. Various\n countermeasures against these attacks, and the trade-offs of each,\n are described. This document archives explanations of the attack and\n common defense techniques for the benefit of TCP implementers and\n administrators of TCP servers or networks, but does not make any\n standards-level recommendations. 4987 trust nested-reference unchanged"},{"id":"IETF RFC 5382","type":"specification","body":"IETF","designation":"RFC 5382","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5382.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5382.txt","https://www.rfc-editor.org/rfc/rfc5382.pdf"],"folder":"IETF/RFC-5382","files":{"txt":{"path":"standards/IETF/RFC-5382/RFC-5382.txt","sha256":"c67083f71f70458d7d5c3b3b74920ef7e30861a739179ea264174c78de6aee14"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of requirements for NATs that handle TCP\n that would allow many applications, such as peer-to-peer applications\n and online games to work consistently. Developing NATs that meet\n this set of requirements will greatly increase the likelihood that\n these applications will function properly.\n\nGuha, et al. Best Current Practice [Page 1]\n\f\nRFC 5382 NAT TCP Requirements October 2008","scope_keywords":["5382","http","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 5382 This document defines a set of requirements for NATs that handle TCP\n that would allow many applications, such as peer-to-peer applications\n and online games to work consistently. Developing NATs that meet\n this set of requirements will greatly increase the likelihood that\n these applications will function properly.\n\nGuha, et al. Best Current Practice [Page 1]\n\f\nRFC 5382 NAT TCP Requirements October 2008 5382 http key management presentation nested-reference unchanged"},{"id":"IETF RFC 5482","type":"specification","body":"IETF","designation":"RFC 5482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5482.txt","https://www.rfc-editor.org/rfc/rfc5482.pdf"],"folder":"IETF/RFC-5482","files":{"txt":{"path":"standards/IETF/RFC-5482/RFC-5482.txt","sha256":"437d9cdc49bf0af4924c0a523e73eedf463d9567448e7867906fdd2c5824a65d"}},"tags":["nested-reference","unchanged"],"summary":"The TCP user timeout controls how long transmitted data may remain\n unacknowledged before a connection is forcefully closed. It is a\n local, per-connection parameter. This document specifies a new TCP\n option -- the TCP User Timeout Option -- that allows one end of a TCP\n connection to advertise its current user timeout value. This\n information provides advice to the other end of the TCP connection to\n adapt its user timeout accordingly. Increasing the user timeouts on\n both ends of a TCP connection allows it to survive extended periods\n without end-to-end connectivity. Decreasing the user timeouts allows\n busy servers to explicitly notify their clients that they will\n maintain the connection state only for a short time without\n connectivity.\n\nEggert & Gont Standards Track [Page 1]\n\f\nRFC 5482 TCP User Timeout Option March 2009","scope_keywords":["5482","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 5482 The TCP user timeout controls how long transmitted data may remain\n unacknowledged before a connection is forcefully closed. It is a\n local, per-connection parameter. This document specifies a new TCP\n option -- the TCP User Timeout Option -- that allows one end of a TCP\n connection to advertise its current user timeout value. This\n information provides advice to the other end of the TCP connection to\n adapt its user timeout accordingly. Increasing the user timeouts on\n both ends of a TCP connection allows it to survive extended periods\n without end-to-end connectivity. Decreasing the user timeouts allows\n busy servers to explicitly notify their clients that they will\n maintain the connection state only for a short time without\n connectivity.\n\nEggert & Gont Standards Track [Page 1]\n\f\nRFC 5482 TCP User Timeout Option March 2009 5482 http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5513","type":"specification","body":"IETF","designation":"RFC 5513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5513.txt","https://www.rfc-editor.org/rfc/rfc5513.pdf"],"folder":"IETF/RFC-5513","files":{"txt":{"path":"standards/IETF/RFC-5513/RFC-5513.txt","sha256":"356f2d7e8daf595cffa3f5330312bcf612ec73eb11a7bc7a55b27f481ffce80b"}},"tags":["nested-reference","unchanged"],"summary":"Three Letter Acronyms (TLAs) are commonly used to identify components\n of networks or protocols as designed or specified within the IETF. A\n common concern is that one acronym may have multiple expansions.\n While this may not have been an issue in the past, network\n convergence means that protocols that did not previously operate\n together are now found in close proximity. This results in\n contention for acronyms, and confusion in interpretation. Such\n confusion has the potential to degrade the performance of the\n Internet as misunderstandings lead to misconfiguration or other\n operating errors.\n\nFarrel Informational [Page 1]\n\f\nRFC 5513 TLAs April 2009\n\n Given the growing use of TLAs and the relatively small number\n available, this document specifies a Badly Construed Proposal (BCP)\n for the management of a registry of TLAs within the IETF, and the\n procedures for the allocation of new T","scope_keywords":["5513","http","license","management","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null}],"search_text":"IETF RFC 5513 Three Letter Acronyms (TLAs) are commonly used to identify components\n of networks or protocols as designed or specified within the IETF. A\n common concern is that one acronym may have multiple expansions.\n While this may not have been an issue in the past, network\n convergence means that protocols that did not previously operate\n together are now found in close proximity. This results in\n contention for acronyms, and confusion in interpretation. Such\n confusion has the potential to degrade the performance of the\n Internet as misunderstandings lead to misconfiguration or other\n operating errors.\n\nFarrel Informational [Page 1]\n\f\nRFC 5513 TLAs April 2009\n\n Given the growing use of TLAs and the relatively small number\n available, this document specifies a Badly Construed Proposal (BCP)\n for the management of a registry of TLAs within the IETF, and the\n procedures for the allocation of new T 5513 http license management pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5575","type":"specification","body":"IETF","designation":"RFC 5575","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5575.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5575.txt","https://www.rfc-editor.org/rfc/rfc5575.pdf"],"folder":"IETF/RFC-5575","files":{"txt":{"path":"standards/IETF/RFC-5575/RFC-5575.txt","sha256":"115ef7f799d515ec2dbacd900f269e227d76a08ec9a1d19b6fda58c8f165877a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Border Gateway Protocol Network Layer\n Reachability Information (BGP NLRI) encoding format that can be used\n to distribute traffic flow specifications. This allows the routing\n system to propagate information regarding more specific components of\n the traffic aggregate defined by an IP destination prefix.\n\n Additionally, it defines two applications of that encoding format:\n one that can be used to automate inter-domain coordination of traffic\n filtering, such as what is required in order to mitigate\n (distributed) denial-of-service attacks, and a second application to\n provide traffic filtering in the context of a BGP/MPLS VPN service.\n\n The information is carried via the BGP, thereby reusing protocol\n algorithms, operational experience, and administrative processes such\n as inter-provider peering agreements.\n\nStatus of This Memo\n\n This document specifies an I","scope_keywords":["5575","algorithm","algorithms","http","key","license","path","policies","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 5575 This document defines a new Border Gateway Protocol Network Layer\n Reachability Information (BGP NLRI) encoding format that can be used\n to distribute traffic flow specifications. This allows the routing\n system to propagate information regarding more specific components of\n the traffic aggregate defined by an IP destination prefix.\n\n Additionally, it defines two applications of that encoding format:\n one that can be used to automate inter-domain coordination of traffic\n filtering, such as what is required in order to mitigate\n (distributed) denial-of-service attacks, and a second application to\n provide traffic filtering in the context of a BGP/MPLS VPN service.\n\n The information is carried via the BGP, thereby reusing protocol\n algorithms, operational experience, and administrative processes such\n as inter-provider peering agreements.\n\nStatus of This Memo\n\n This document specifies an I 5575 algorithm algorithms http key license path policies policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5596","type":"specification","body":"IETF","designation":"RFC 5596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5596.txt","https://www.rfc-editor.org/rfc/rfc5596.pdf"],"folder":"IETF/RFC-5596","files":{"txt":{"path":"standards/IETF/RFC-5596/RFC-5596.txt","sha256":"b0ca9c64d449a81bc079cb05679151594daa3fcab650ba9c1c05d558b874c9d4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an update to the Datagram Congestion Control\n Protocol (DCCP), a connection-oriented and datagram-based transport\n protocol. The update adds support for the DCCP-Listen packet. This\n assists DCCP applications to communicate through middleboxes (e.g., a\n Network Address Port Translator or a DCCP server behind a firewall),\n where peering endpoints need to initiate communication in a near-\n simultaneous manner to establish necessary middlebox state.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust ","scope_keywords":["5596","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null}],"search_text":"IETF RFC 5596 This document specifies an update to the Datagram Congestion Control\n Protocol (DCCP), a connection-oriented and datagram-based transport\n protocol. The update adds support for the DCCP-Listen packet. This\n assists DCCP applications to communicate through middleboxes (e.g., a\n Network Address Port Translator or a DCCP server behind a firewall),\n where peering endpoints need to initiate communication in a near-\n simultaneous manner to establish necessary middlebox state.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust  5596 http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5625","type":"specification","body":"IETF","designation":"RFC 5625","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5625.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5625.txt","https://www.rfc-editor.org/rfc/rfc5625.pdf"],"folder":"IETF/RFC-5625","files":{"txt":{"path":"standards/IETF/RFC-5625/RFC-5625.txt","sha256":"2eb24e4bc70faaddb57fb0786e5e60916b9080c1fd012719722b9a27f91cbade"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for the implementation of DNS\n proxies, as found in broadband gateways and other similar network\n devices.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nBellis Best Current Practice [Page 1]\n\f\nRFC 5625 DNS Proxy Implementation Guidelines August 2009","scope_keywords":["5625","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5625 This document provides guidelines for the implementation of DNS\n proxies, as found in broadband gateways and other similar network\n devices.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nBellis Best Current Practice [Page 1]\n\f\nRFC 5625 DNS Proxy Implementation Guidelines August 2009 5625 authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5730","type":"specification","body":"IETF","designation":"RFC 5730","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5730.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5730.txt","https://www.rfc-editor.org/rfc/rfc5730.pdf"],"folder":"IETF/RFC-5730","files":{"txt":{"path":"standards/IETF/RFC-5730/RFC-5730.txt","sha256":"30e27ceae123ded9312b0da08afc012575fb03c7ee5de85fe4bc521859ce223a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application-layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration. This document obsoletes RFC 4930.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n","scope_keywords":["5730","authentication","http","identification","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5730 This document describes an application-layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration. This document obsoletes RFC 4930.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n 5730 authentication http identification key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5898","type":"specification","body":"IETF","designation":"RFC 5898","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5898.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5898.txt","https://www.rfc-editor.org/rfc/rfc5898.pdf"],"folder":"IETF/RFC-5898","files":{"txt":{"path":"standards/IETF/RFC-5898/RFC-5898.txt","sha256":"0a31de9560c41382e8646ec17eff06e930740bef1aae1f8eefda579c30accf2c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new connectivity precondition for the Session\n Description Protocol (SDP) precondition framework. A connectivity\n precondition can be used to delay session establishment or\n modification until media stream connectivity has been successfully\n verified. The method of verification may vary depending on the type\n of transport used for the media. For unreliable datagram transports\n such as UDP, verification involves probing the stream with data or\n control packets. For reliable connection-oriented transports such as\n TCP, verification can be achieved simply by successful connection\n establishment or by probing the connection with data or control\n packets, depending on the situation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com","scope_keywords":["5898","http","key","license","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 5898 This document defines a new connectivity precondition for the Session\n Description Protocol (SDP) precondition framework. A connectivity\n precondition can be used to delay session establishment or\n modification until media stream connectivity has been successfully\n verified. The method of verification may vary depending on the type\n of transport used for the media. For unreliable datagram transports\n such as UDP, verification involves probing the stream with data or\n control packets. For reliable connection-oriented transports such as\n TCP, verification can be achieved simply by successful connection\n establishment or by probing the connection with data or control\n packets, depending on the situation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com 5898 http key license path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5961","type":"specification","body":"IETF","designation":"RFC 5961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5961.txt","https://www.rfc-editor.org/rfc/rfc5961.pdf"],"folder":"IETF/RFC-5961","files":{"txt":{"path":"standards/IETF/RFC-5961/RFC-5961.txt","sha256":"bba04c91e91f6aa7bd49b491f127bfb3c1280dd22b52f15299d8123f62aab502"}},"tags":["nested-reference","unchanged"],"summary":"TCP has historically been considered to be protected against spoofed\n off-path packet injection attacks by relying on the fact that it is\n difficult to guess the 4-tuple (the source and destination IP\n addresses and the source and destination ports) in combination with\n the 32-bit sequence number(s). A combination of increasing window\n sizes and applications using longer-term connections (e.g., H-323 or\n Border Gateway Protocol (BGP) [RFC4271]) have left modern TCP\n implementations more vulnerable to these types of spoofed packet\n injection attacks.\n\n Many of these long-term TCP applications tend to have predictable IP\n addresses and ports that makes it far easier for the 4-tuple (4-tuple\n is the same as the socket pair mentioned in RFC 793) to be guessed.\n Having guessed the 4-tuple correctly, an attacker can inject a TCP\n segment with the RST bit set, the SYN bit set or data into a TCP","scope_keywords":["5961","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null}],"search_text":"IETF RFC 5961 TCP has historically been considered to be protected against spoofed\n off-path packet injection attacks by relying on the fact that it is\n difficult to guess the 4-tuple (the source and destination IP\n addresses and the source and destination ports) in combination with\n the 32-bit sequence number(s). A combination of increasing window\n sizes and applications using longer-term connections (e.g., H-323 or\n Border Gateway Protocol (BGP) [RFC4271]) have left modern TCP\n implementations more vulnerable to these types of spoofed packet\n injection attacks.\n\n Many of these long-term TCP applications tend to have predictable IP\n addresses and ports that makes it far easier for the 4-tuple (4-tuple\n is the same as the socket pair mentioned in RFC 793) to be guessed.\n Having guessed the 4-tuple correctly, an attacker can inject a TCP\n segment with the RST bit set, the SYN bit set or data into a TCP 5961 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5985","type":"specification","body":"IETF","designation":"RFC 5985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5985.txt","https://www.rfc-editor.org/rfc/rfc5985.pdf"],"folder":"IETF/RFC-5985","files":{"txt":{"path":"standards/IETF/RFC-5985/RFC-5985.txt","sha256":"7378c3cfa430e304d00763044c6e0e6cc9c81801859b16cb39c7152822114da0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Layer 7 Location Configuration Protocol (L7\n LCP) and describes the use of HTTP and HTTP/TLS as transports for the\n L7 LCP. The L7 LCP is used for retrieving location information from\n a server within an access network. It includes options for\n retrieving location information in two forms: by value and by\n reference. The protocol is an extensible application-layer protocol\n that is independent of the session layer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, ","scope_keywords":["5985","attribute","authentication","delivery","http","https","license","pid","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null}],"search_text":"IETF RFC 5985 This document defines a Layer 7 Location Configuration Protocol (L7\n LCP) and describes the use of HTTP and HTTP/TLS as transports for the\n L7 LCP. The L7 LCP is used for retrieving location information from\n a server within an access network. It includes options for\n retrieving location information in two forms: by value and by\n reference. The protocol is an extensible application-layer protocol\n that is independent of the session layer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document,  5985 attribute authentication delivery http https license pid subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6039","type":"specification","body":"IETF","designation":"RFC 6039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6039.txt","https://www.rfc-editor.org/rfc/rfc6039.pdf"],"folder":"IETF/RFC-6039","files":{"txt":{"path":"standards/IETF/RFC-6039/RFC-6039.txt","sha256":"9d2ce048cec0d49e13c526c2d90e6becd683c07d04691e30e032aaeee3dc08f4"}},"tags":["nested-reference","unchanged"],"summary":"Routing protocols have been extended over time to use cryptographic\n mechanisms to ensure that data received from a neighboring router has\n not been modified in transit and actually originated from an\n authorized neighboring router.\n\n The cryptographic mechanisms defined to date and described in this\n document rely on a digest produced with a hash algorithm applied to\n the payload encapsulated in the routing protocol packet.\n\n This document outlines some of the limitations of the current\n mechanism, problems with manual keying of these cryptographic\n algorithms, and possible vectors for the exploitation of these\n limitations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has","scope_keywords":["6039","algorithm","algorithms","authentication","hash","http","key","keys","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null}],"search_text":"IETF RFC 6039 Routing protocols have been extended over time to use cryptographic\n mechanisms to ensure that data received from a neighboring router has\n not been modified in transit and actually originated from an\n authorized neighboring router.\n\n The cryptographic mechanisms defined to date and described in this\n document rely on a digest produced with a hash algorithm applied to\n the payload encapsulated in the routing protocol packet.\n\n This document outlines some of the limitations of the current\n mechanism, problems with manual keying of these cryptographic\n algorithms, and possible vectors for the exploitation of these\n limitations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has 6039 algorithm algorithms authentication hash http key keys license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6083","type":"specification","body":"IETF","designation":"RFC 6083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6083.txt","https://www.rfc-editor.org/rfc/rfc6083.pdf"],"folder":"IETF/RFC-6083","files":{"txt":{"path":"standards/IETF/RFC-6083/RFC-6083.txt","sha256":"55b40b9a938176c2981b037d2ed8d7e7fca28144212422bea243d4120df5d8c0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of the Datagram Transport Layer\n Security (DTLS) protocol over the Stream Control Transmission\n Protocol (SCTP).\n\n DTLS over SCTP provides communications privacy for applications that\n use SCTP as their transport protocol and allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping and detect tampering or message forgery.\n\n Applications using DTLS over SCTP can use almost all transport\n features provided by SCTP and its extensions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section ","scope_keywords":["6083","authentication","delivery","http","key","license","management","path","pid","preservation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6083 This document describes the usage of the Datagram Transport Layer\n Security (DTLS) protocol over the Stream Control Transmission\n Protocol (SCTP).\n\n DTLS over SCTP provides communications privacy for applications that\n use SCTP as their transport protocol and allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping and detect tampering or message forgery.\n\n Applications using DTLS over SCTP can use almost all transport\n features provided by SCTP and its extensions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section  6083 authentication delivery http key license management path pid preservation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6093","type":"specification","body":"IETF","designation":"RFC 6093","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6093.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6093.txt","https://www.rfc-editor.org/rfc/rfc6093.pdf"],"folder":"IETF/RFC-6093","files":{"txt":{"path":"standards/IETF/RFC-6093/RFC-6093.txt","sha256":"b464cc05058563fba89abf95ea23d58efab91513859c822b555850550c44806a"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes how current TCP implementations process TCP\n urgent indications and how the behavior of some widely deployed\n middleboxes affects how end systems process urgent indications. This\n document updates the relevant specifications such that they\n accommodate current practice in processing TCP urgent indications,\n raises awareness about the reliability of TCP urgent indications in\n the Internet, and recommends against the use of urgent indications\n (but provides advice to applications that do).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section","scope_keywords":["6093","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null}],"search_text":"IETF RFC 6093 This document analyzes how current TCP implementations process TCP\n urgent indications and how the behavior of some widely deployed\n middleboxes affects how end systems process urgent indications. This\n document updates the relevant specifications such that they\n accommodate current practice in processing TCP urgent indications,\n raises awareness about the reliability of TCP urgent indications in\n the Internet, and recommends against the use of urgent indications\n (but provides advice to applications that do).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 6093 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6135","type":"specification","body":"IETF","designation":"RFC 6135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6135.txt","https://www.rfc-editor.org/rfc/rfc6135.pdf"],"folder":"IETF/RFC-6135","files":{"txt":{"path":"standards/IETF/RFC-6135/RFC-6135.txt","sha256":"198143f7b9f86bc3c5f4425b00cebe96484c5c2d96905c677b7b6dcacbc50d3c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an alternative connection model for Message\n Session Relay Protocol (MSRP) User Agents (UAs); this model uses the\n connection-oriented media (COMEDIA) mechanism in order to create the\n MSRP transport connection. The model allows MSRP UAs behind Network\n Address Translators (NATs) to negotiate which endpoint initiates the\n establishment of the Transmission Control Protocol (TCP) connection,\n in order for MSRP messages to traverse the NAT.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current stat","scope_keywords":["6135","attribute","attributes","http","key","license","path","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 6135 This document defines an alternative connection model for Message\n Session Relay Protocol (MSRP) User Agents (UAs); this model uses the\n connection-oriented media (COMEDIA) mechanism in order to create the\n MSRP transport connection. The model allows MSRP UAs behind Network\n Address Translators (NATs) to negotiate which endpoint initiates the\n establishment of the Transmission Control Protocol (TCP) connection,\n in order for MSRP messages to traverse the NAT.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current stat 6135 attribute attributes http key license path policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6146","type":"specification","body":"IETF","designation":"RFC 6146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6146.txt","https://www.rfc-editor.org/rfc/rfc6146.pdf"],"folder":"IETF/RFC-6146","files":{"txt":{"path":"standards/IETF/RFC-6146/RFC-6146.txt","sha256":"deaaf6be3e889742e760b136a2d1f85b197ef769871d89765e509d606eee7c64"}},"tags":["nested-reference","unchanged"],"summary":"This document describes stateful NAT64 translation, which allows\n IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or\n ICMP. One or more public IPv4 addresses assigned to a NAT64\n translator are shared among several IPv6-only clients. When stateful\n NAT64 is used in conjunction with DNS64, no changes are usually\n required in the IPv6 client or the IPv4 server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained ","scope_keywords":["6146","algorithm","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6970","folder":"IETF/RFC-6970","source":"IETF/RFC-6970/RFC-6970.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7498","folder":"IETF/RFC-7498","source":"IETF/RFC-7498/RFC-7498.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6146 This document describes stateful NAT64 translation, which allows\n IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or\n ICMP. One or more public IPv4 addresses assigned to a NAT64\n translator are shared among several IPv6-only clients. When stateful\n NAT64 is used in conjunction with DNS64, no changes are usually\n required in the IPv6 client or the IPv4 server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained  6146 algorithm http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6181","type":"specification","body":"IETF","designation":"RFC 6181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6181.txt","https://www.rfc-editor.org/rfc/rfc6181.pdf"],"folder":"IETF/RFC-6181","files":{"txt":{"path":"standards/IETF/RFC-6181/RFC-6181.txt","sha256":"45cf0d8f38f7816c5cc56a127a245e8713bf6df1d5109ed4d8688ab10285ce3e"}},"tags":["nested-reference","unchanged"],"summary":"Multipath TCP (MPTCP for short) describes the extensions proposed for\n TCP so that endpoints of a given TCP connection can use multiple\n paths to exchange data. Such extensions enable the exchange of\n segments using different source-destination address pairs, resulting\n in the capability of using multiple paths in a significant number of\n scenarios. Some level of multihoming and mobility support can be\n achieved through these extensions. However, the support for multiple\n IP addresses per endpoint may have implications on the security of\n the resulting MPTCP. This note includes a threat analysis for MPTCP.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public re","scope_keywords":["6181","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6181 Multipath TCP (MPTCP for short) describes the extensions proposed for\n TCP so that endpoints of a given TCP connection can use multiple\n paths to exchange data. Such extensions enable the exchange of\n segments using different source-destination address pairs, resulting\n in the capability of using multiple paths in a significant number of\n scenarios. Some level of multihoming and mobility support can be\n achieved through these extensions. However, the support for multiple\n IP addresses per endpoint may have implications on the security of\n the resulting MPTCP. This note includes a threat analysis for MPTCP.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public re 6181 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6191","type":"specification","body":"IETF","designation":"RFC 6191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6191.txt","https://www.rfc-editor.org/rfc/rfc6191.pdf"],"folder":"IETF/RFC-6191","files":{"txt":{"path":"standards/IETF/RFC-6191/RFC-6191.txt","sha256":"974f45f076be09e8be66ef8b12e9b5a99ba95b43251502b08539fc53d9347211"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an algorithm for processing incoming SYN\n segments that allows higher connection-establishment rates between\n any two TCP endpoints when a TCP Timestamps option is present in the\n incoming SYN segment. This document only modifies processing of SYN\n segments received for connections in the TIME-WAIT state; processing\n in all other states is unchanged.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http","scope_keywords":["6191","algorithm","algorithms","http","key","license","policy","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6191 This document describes an algorithm for processing incoming SYN\n segments that allows higher connection-establishment rates between\n any two TCP endpoints when a TCP Timestamps option is present in the\n incoming SYN segment. This document only modifies processing of SYN\n segments received for connections in the TIME-WAIT state; processing\n in all other states is unchanged.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http 6191 algorithm algorithms http key license policy subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 6284","type":"specification","body":"IETF","designation":"RFC 6284","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6284.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6284.txt","https://www.rfc-editor.org/rfc/rfc6284.pdf"],"folder":"IETF/RFC-6284","files":{"txt":{"path":"standards/IETF/RFC-6284/RFC-6284.txt","sha256":"b18d4c927cfcb73b61a5bf0c3f508c4e1ec5f2fdddd3af22faeda158a2dcf342"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a port mapping solution that allows RTP\n receivers to choose their own ports for an auxiliary unicast session\n in RTP applications using both unicast and multicast services. The\n solution provides protection against denial-of-service or packet\n amplification attacks that could be used to cause one or more RTP\n packets to be sent to a victim client.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht","scope_keywords":["6284","attribute","attributes","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6284 This document presents a port mapping solution that allows RTP\n receivers to choose their own ports for an auxiliary unicast session\n in RTP applications using both unicast and multicast services. The\n solution provides protection against denial-of-service or packet\n amplification attacks that could be used to cause one or more RTP\n packets to be sent to a victim client.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht 6284 attribute attributes http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6356","type":"specification","body":"IETF","designation":"RFC 6356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6356.txt","https://www.rfc-editor.org/rfc/rfc6356.pdf"],"folder":"IETF/RFC-6356","files":{"txt":{"path":"standards/IETF/RFC-6356/RFC-6356.txt","sha256":"14ce795a3c158564d950396dbdc5bd6108c979b599ff7f24164403269408cbcc"}},"tags":["nested-reference","unchanged"],"summary":"Often endpoints are connected by multiple paths, but communications\n are usually restricted to a single path per connection. Resource\n usage within the network would be more efficient were it possible for\n these multiple paths to be used concurrently. Multipath TCP is a\n proposal to achieve multipath transport in TCP.\n\n New congestion control algorithms are needed for multipath transport\n protocols such as Multipath TCP, as single path algorithms have a\n series of issues in the multipath context. One of the prominent\n problems is that running existing algorithms such as standard TCP\n independently on each path would give the multipath flow more than\n its fair share at a bottleneck link traversed by more than one of its\n subflows. Further, it is desirable that a source with multiple paths\n available will transfer more traffic using the least congested of the\n paths, achieving a property c","scope_keywords":["6356","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6356 Often endpoints are connected by multiple paths, but communications\n are usually restricted to a single path per connection. Resource\n usage within the network would be more efficient were it possible for\n these multiple paths to be used concurrently. Multipath TCP is a\n proposal to achieve multipath transport in TCP.\n\n New congestion control algorithms are needed for multipath transport\n protocols such as Multipath TCP, as single path algorithms have a\n series of issues in the multipath context. One of the prominent\n problems is that running existing algorithms such as standard TCP\n independently on each path would give the multipath flow more than\n its fair share at a bottleneck link traversed by more than one of its\n subflows. Further, it is desirable that a source with multiple paths\n available will transfer more traffic using the least congested of the\n paths, achieving a property c 6356 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6390","type":"specification","body":"IETF","designation":"RFC 6390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6390.txt","https://www.rfc-editor.org/rfc/rfc6390.pdf"],"folder":"IETF/RFC-6390","files":{"txt":{"path":"standards/IETF/RFC-6390/RFC-6390.txt","sha256":"c41670ce2d52571d946e1517c60dcf070f27cedaf3d6d443b0a35c4fee43e699"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework and a process for developing\n Performance Metrics of protocols and applications transported over\n IETF-specified protocols. These metrics can be used to characterize\n traffic on live networks and services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6390.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document autho","scope_keywords":["6390","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 6390 This document describes a framework and a process for developing\n Performance Metrics of protocols and applications transported over\n IETF-specified protocols. These metrics can be used to characterize\n traffic on live networks and services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6390.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document autho 6390 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6429","type":"specification","body":"IETF","designation":"RFC 6429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6429.txt","https://www.rfc-editor.org/rfc/rfc6429.pdf"],"folder":"IETF/RFC-6429","files":{"txt":{"path":"standards/IETF/RFC-6429/RFC-6429.txt","sha256":"f2d371ecfeb49168b72a86e863a88fb3593fa90a2548b07fa2ead6cff68b6fcf"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies the Zero Window Probes (ZWPs) described in\n RFC 1122 (\"Requirements for Internet Hosts -- Communication Layers\").\n In particular, it clarifies the actions that can be taken on\n connections that are experiencing the ZWP condition. Rather than\n making a change to the standard, this document clarifies what has\n been until now a misinterpretation of the standard as specified in\n RFC 1122.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 ","scope_keywords":["6429","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6429 This document clarifies the Zero Window Probes (ZWPs) described in\n RFC 1122 (\"Requirements for Internet Hosts -- Communication Layers\").\n In particular, it clarifies the actions that can be taken on\n connections that are experiencing the ZWP condition. Rather than\n making a change to the standard, this document clarifies what has\n been until now a misinterpretation of the standard as specified in\n RFC 1122.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2  6429 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6528","type":"specification","body":"IETF","designation":"RFC 6528","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6528.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6528.txt","https://www.rfc-editor.org/rfc/rfc6528.pdf"],"folder":"IETF/RFC-6528","files":{"txt":{"path":"standards/IETF/RFC-6528/RFC-6528.txt","sha256":"1de02139d839860eb49ea553acf75e16b93a6326e4b0eda1ef0daa56433b89da"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an algorithm for the generation of TCP\n Initial Sequence Numbers (ISNs), such that the chances of an off-path\n attacker guessing the sequence numbers in use by a target connection\n are reduced. This document revises (and formally obsoletes) RFC\n 1948, and takes the ISN generation algorithm originally proposed in\n that document to Standards Track, formally updating RFC 793.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on","scope_keywords":["6528","algorithm","algorithms","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6528 This document specifies an algorithm for the generation of TCP\n Initial Sequence Numbers (ISNs), such that the chances of an off-path\n attacker guessing the sequence numbers in use by a target connection\n are reduced. This document revises (and formally obsoletes) RFC\n 1948, and takes the ISN generation algorithm originally proposed in\n that document to Standards Track, formally updating RFC 793.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on 6528 algorithm algorithms http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6627","type":"specification","body":"IETF","designation":"RFC 6627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6627.txt","https://www.rfc-editor.org/rfc/rfc6627.pdf"],"folder":"IETF/RFC-6627","files":{"txt":{"path":"standards/IETF/RFC-6627/RFC-6627.txt","sha256":"bbb841a056dfd187a97122fa712a73db486399ee00b5acf5a69550c7729859cf"}},"tags":["nested-reference","unchanged"],"summary":"The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain.\n On every link in the PCN-domain, the overall rate of PCN-traffic is\n metered, and PCN-packets are appropriately marked when certain\n configured rates are exceeded. Egress nodes provide decision points\n with information about the PCN-marks of PCN-packets that allows them\n to take decisions about whether to admit or block a new flow request,\n and to terminate some already admitted flows during serious\n pre-congestion.\n\n The PCN working group explored a number of approaches for encoding\n this pre-congestion information into the IP header. This document\n provides details of those approaches along with an explanation of the\n constraints that apply to any solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it i","scope_keywords":["6627","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null}],"search_text":"IETF RFC 6627 The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain.\n On every link in the PCN-domain, the overall rate of PCN-traffic is\n metered, and PCN-packets are appropriately marked when certain\n configured rates are exceeded. Egress nodes provide decision points\n with information about the PCN-marks of PCN-packets that allows them\n to take decisions about whether to admit or block a new flow request,\n and to terminate some already admitted flows during serious\n pre-congestion.\n\n The PCN working group explored a number of approaches for encoding\n this pre-congestion information into the IP header. This document\n provides details of those approaches along with an explanation of the\n constraints that apply to any solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it i 6627 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6787","type":"specification","body":"IETF","designation":"RFC 6787","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6787.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6787.txt","https://www.rfc-editor.org/rfc/rfc6787.pdf"],"folder":"IETF/RFC-6787","files":{"txt":{"path":"standards/IETF/RFC-6787/RFC-6787.txt","sha256":"cacd4d736705c38af60bbe10dd51122f31affecb3124f052b92852c16e6d327a"}},"tags":["nested-reference","unchanged"],"summary":"The Media Resource Control Protocol Version 2 (MRCPv2) allows client\n hosts to control media service resources such as speech synthesizers,\n recognizers, verifiers, and identifiers residing in servers on the\n network. MRCPv2 is not a \"stand-alone\" protocol -- it relies on\n other protocols, such as the Session Initiation Protocol (SIP), to\n coordinate MRCPv2 clients and servers and manage sessions between\n them, and the Session Description Protocol (SDP) to describe,\n discover, and exchange capabilities. It also depends on SIP and SDP\n to establish the media sessions and associated parameters between the\n media source or sink and the media server. Once this is done, the\n MRCPv2 exchange operates over the control session established above,\n allowing the client to control the media processing resources on the\n speech resource server.\n\nStatus of This Memo\n\n This is an Internet Standards Trac","scope_keywords":["6787","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6787 The Media Resource Control Protocol Version 2 (MRCPv2) allows client\n hosts to control media service resources such as speech synthesizers,\n recognizers, verifiers, and identifiers residing in servers on the\n network. MRCPv2 is not a \"stand-alone\" protocol -- it relies on\n other protocols, such as the Session Initiation Protocol (SIP), to\n coordinate MRCPv2 clients and servers and manage sessions between\n them, and the Session Description Protocol (SDP) to describe,\n discover, and exchange capabilities. It also depends on SIP and SDP\n to establish the media sessions and associated parameters between the\n media source or sink and the media server. Once this is done, the\n MRCPv2 exchange operates over the control session established above,\n allowing the client to control the media processing resources on the\n speech resource server.\n\nStatus of This Memo\n\n This is an Internet Standards Trac 6787 http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6888","type":"specification","body":"IETF","designation":"RFC 6888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6888.txt","https://www.rfc-editor.org/rfc/rfc6888.pdf"],"folder":"IETF/RFC-6888","files":{"txt":{"path":"standards/IETF/RFC-6888/RFC-6888.txt","sha256":"d457f77ec6d4bd0b1921f1a14c5d27dfbb620a7166d1d02864a4dcd13a6b1b91"}},"tags":["nested-reference","unchanged"],"summary":"This document defines common requirements for Carrier-Grade NATs\n (CGNs). It updates RFC 4787.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6888.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ie","scope_keywords":["6888","driving","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6888 This document defines common requirements for Carrier-Grade NATs\n (CGNs). It updates RFC 4787.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6888.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ie 6888 driving http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6921","type":"specification","body":"IETF","designation":"RFC 6921","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6921.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6921.txt","https://www.rfc-editor.org/rfc/rfc6921.pdf"],"folder":"IETF/RFC-6921","files":{"txt":{"path":"standards/IETF/RFC-6921/RFC-6921.txt","sha256":"82ed5b269718c4f5fc1dfe80ef183d5879c412c1ed2e17523745bfe597a90881"}},"tags":["nested-reference","unchanged"],"summary":"We are approaching the time when we will be able to communicate\n faster than the speed of light. It is well known that as we approach\n the speed of light, time slows down. Logically, it is reasonable to\n assume that as we go faster than the speed of light, time will\n reverse. The major consequence of this for Internet protocols is\n that packets will arrive before they are sent. This will have a\n major impact on the way we design Internet protocols. This paper\n outlines some of the issues and suggests some directions for\n additional analysis of these issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implem","scope_keywords":["6921","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null}],"search_text":"IETF RFC 6921 We are approaching the time when we will be able to communicate\n faster than the speed of light. It is well known that as we approach\n the speed of light, time slows down. Logically, it is reasonable to\n assume that as we go faster than the speed of light, time will\n reverse. The major consequence of this for Internet protocols is\n that packets will arrive before they are sent. This will have a\n major impact on the way we design Internet protocols. This paper\n outlines some of the issues and suggests some directions for\n additional analysis of these issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implem 6921 http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6937","type":"specification","body":"IETF","designation":"RFC 6937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6937.txt","https://www.rfc-editor.org/rfc/rfc6937.pdf"],"folder":"IETF/RFC-6937","files":{"txt":{"path":"standards/IETF/RFC-6937/RFC-6937.txt","sha256":"bcdf44e32dcaf86f7e29f0f268228aac0a67159e17ef42063ddc42e55b929bc6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an experimental Proportional Rate Reduction\n (PRR) algorithm as an alternative to the widely deployed Fast\n Recovery and Rate-Halving algorithms. These algorithms determine the\n amount of data sent by TCP during loss recovery. PRR minimizes\n excess window adjustments, and the actual window size at the end of\n recovery will be as close as possible to the ssthresh, as determined\n by the congestion control algorithm.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet E","scope_keywords":["6937","algorithm","algorithms","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 6937 This document describes an experimental Proportional Rate Reduction\n (PRR) algorithm as an alternative to the widely deployed Fast\n Recovery and Rate-Halving algorithms. These algorithms determine the\n amount of data sent by TCP during loss recovery. PRR minimizes\n excess window adjustments, and the actual window size at the end of\n recovery will be as close as possible to the ssthresh, as determined\n by the congestion control algorithm.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet E 6937 algorithm algorithms http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7094","type":"specification","body":"IETF","designation":"RFC 7094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7094.txt","https://www.rfc-editor.org/rfc/rfc7094.pdf"],"folder":"IETF/RFC-7094","files":{"txt":{"path":"standards/IETF/RFC-7094/RFC-7094.txt","sha256":"0a23bfce72e47035f669bfd4607958ed01f9f3f1594b34e3cce44ec9d0a883c5"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses architectural implications of IP anycast and\n provides some historical analysis of anycast use by various IETF\n protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7094.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document ","scope_keywords":["7094","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 7094 This memo discusses architectural implications of IP anycast and\n provides some historical analysis of anycast use by various IETF\n protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7094.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document  7094 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7111","type":"specification","body":"IETF","designation":"RFC 7111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7111.txt","https://www.rfc-editor.org/rfc/rfc7111.pdf"],"folder":"IETF/RFC-7111","files":{"txt":{"path":"standards/IETF/RFC-7111/RFC-7111.txt","sha256":"a9bdc00196c12ef399dfd94e0dd7cb5a17c7fe195e85ad5139b3372b92b62ba3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines URI fragment identifiers for text/csv MIME\n entities. These fragment identifiers make it possible to refer to\n parts of a text/csv MIME entity identified by row, column, or cell.\n Fragment identification can use single items or ranges.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or","scope_keywords":["7111","http","identification","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null}],"search_text":"IETF RFC 7111 This memo defines URI fragment identifiers for text/csv MIME\n entities. These fragment identifiers make it possible to refer to\n parts of a text/csv MIME entity identified by row, column, or cell.\n Fragment identification can use single items or ranges.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or 7111 http identification license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7230","type":"specification","body":"IETF","designation":"RFC 7230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7230.txt","https://www.rfc-editor.org/rfc/rfc7230.pdf"],"folder":"IETF/RFC-7230","files":{"txt":{"path":"standards/IETF/RFC-7230/RFC-7230.txt","sha256":"c7fdc8bebdf1f8195f731592c47f5ea822b489436fd905b01b55ef531fca4120"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document provides an overview of HTTP architecture and\n its associated terminology, defines the \"http\" and \"https\" Uniform\n Resource Identifier (URI) schemes, defines the HTTP/1.1 message\n syntax and parsing requirements, and describes related security\n concerns for implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any err","scope_keywords":["7230","http","https","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7337","folder":"IETF/RFC-7337","source":"IETF/RFC-7337/RFC-7337.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8307","folder":"IETF/RFC-8307","source":"IETF/RFC-8307/RFC-8307.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 7230 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document provides an overview of HTTP architecture and\n its associated terminology, defines the \"http\" and \"https\" Uniform\n Resource Identifier (URI) schemes, defines the HTTP/1.1 message\n syntax and parsing requirements, and describes related security\n concerns for implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any err 7230 http https license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7288","type":"specification","body":"IETF","designation":"RFC 7288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7288.txt","https://www.rfc-editor.org/rfc/rfc7288.pdf"],"folder":"IETF/RFC-7288","files":{"txt":{"path":"standards/IETF/RFC-7288/RFC-7288.txt","sha256":"76a8b3c307676a882329f166b86103c4bf255daaf1843816013aafd4aa6d5831"}},"tags":["nested-reference","unchanged"],"summary":"In today's Internet, the need for firewalls is generally accepted in\n the industry, and indeed firewalls are widely deployed in practice.\n Unlike traditional firewalls that protect network links, host\n firewalls run in end-user systems. Often the result is that software\n may be running and potentially consuming resources, but then\n communication is blocked by a host firewall. It's taken for granted\n that this end state is either desirable or the best that can be\n achieved in practice, rather than (for example) an end state where\n the relevant software is not running or is running in a way that\n would not result in unwanted communication. In this document, we\n explore the issues behind these assumptions and provide suggestions\n on improving the architecture going forward.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informatio","scope_keywords":["7288","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null}],"search_text":"IETF RFC 7288 In today's Internet, the need for firewalls is generally accepted in\n the industry, and indeed firewalls are widely deployed in practice.\n Unlike traditional firewalls that protect network links, host\n firewalls run in end-user systems. Often the result is that software\n may be running and potentially consuming resources, but then\n communication is blocked by a host firewall. It's taken for granted\n that this end state is either desirable or the best that can be\n achieved in practice, rather than (for example) an end state where\n the relevant software is not running or is running in a way that\n would not result in unwanted communication. In this document, we\n explore the issues behind these assumptions and provide suggestions\n on improving the architecture going forward.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informatio 7288 http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7323","type":"specification","body":"IETF","designation":"RFC 7323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7323.txt","https://www.rfc-editor.org/rfc/rfc7323.pdf"],"folder":"IETF/RFC-7323","files":{"txt":{"path":"standards/IETF/RFC-7323/RFC-7323.txt","sha256":"29e07732ea23f4d3e41371be55b767d774b718f054ade161b71f48864f7c2d48"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of TCP extensions to improve\n performance over paths with a large bandwidth * delay product and to\n provide reliable operation over very high-speed paths. It defines\n the TCP Window Scale (WS) option and the TCP Timestamps (TS) option\n and their semantics. The Window Scale option is used to support\n larger receive windows, while the Timestamps option can be used for\n at least two distinct mechanisms, Protection Against Wrapped\n Sequences (PAWS) and Round-Trip Time Measurement (RTTM), that are\n also described herein.\n\n This document obsoletes RFC 1323 and describes changes from it.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet","scope_keywords":["7323","algorithm","http","license","path","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null}],"search_text":"IETF RFC 7323 This document specifies a set of TCP extensions to improve\n performance over paths with a large bandwidth * delay product and to\n provide reliable operation over very high-speed paths. It defines\n the TCP Window Scale (WS) option and the TCP Timestamps (TS) option\n and their semantics. The Window Scale option is used to support\n larger receive windows, while the Timestamps option can be used for\n at least two distinct mechanisms, Protection Against Wrapped\n Sequences (PAWS) and Round-Trip Time Measurement (RTTM), that are\n also described herein.\n\n This document obsoletes RFC 1323 and describes changes from it.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet 7323 algorithm http license path subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7540","type":"specification","body":"IETF","designation":"RFC 7540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7540.txt","https://www.rfc-editor.org/rfc/rfc7540.pdf"],"folder":"IETF/RFC-7540","files":{"txt":{"path":"standards/IETF/RFC-7540/RFC-7540.txt","sha256":"6a67e8d7fdfa7b5272fc55f8fba62b266f932031c7f39e29c52f83e129bc2967"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes an optimized expression of the semantics\n of the Hypertext Transfer Protocol (HTTP), referred to as HTTP\n version 2 (HTTP/2). HTTP/2 enables a more efficient use of network\n resources and a reduced perception of latency by introducing header\n field compression and allowing multiple concurrent exchanges on the\n same connection. It also introduces unsolicited push of\n representations from servers to clients.\n\n This specification is an alternative to, but does not obsolete, the\n HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur","scope_keywords":["7540","http","https","identification","license","management","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8297","folder":"IETF/RFC-8297","source":"IETF/RFC-8297/RFC-8297.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null}],"search_text":"IETF RFC 7540 This specification describes an optimized expression of the semantics\n of the Hypertext Transfer Protocol (HTTP), referred to as HTTP\n version 2 (HTTP/2). HTTP/2 enables a more efficient use of network\n resources and a reduced perception of latency by introducing header\n field compression and allowing multiple concurrent exchanges on the\n same connection. It also introduces unsolicited push of\n representations from servers to clients.\n\n This specification is an alternative to, but does not obsolete, the\n HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur 7540 http https identification license management presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7661","type":"specification","body":"IETF","designation":"RFC 7661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7661.txt","https://www.rfc-editor.org/rfc/rfc7661.pdf"],"folder":"IETF/RFC-7661","files":{"txt":{"path":"standards/IETF/RFC-7661/RFC-7661.txt","sha256":"ffa18c3a0e8abf4e82be343c5543aa2cdeeea8b0aa78cef64fbd3c02dc5bf817"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a mechanism to address issues that arise when\n TCP is used for traffic that exhibits periods where the sending rate\n is limited by the application rather than the congestion window. It\n provides an experimental update to TCP that allows a TCP sender to\n restart quickly following a rate-limited interval. This method is\n expected to benefit applications that send rate-limited traffic using\n TCP while also providing an appropriate response if congestion is\n experienced.\n\n This document also evaluates the Experimental specification of TCP\n Congestion Window Validation (CWV) defined in RFC 2861 and concludes\n that RFC 2861 sought to address important issues but failed to\n deliver a widely used solution. This document therefore reclassifies\n the status of RFC 2861 from Experimental to Historic. This document\n obsoletes RFC 2861.\n\nStatus of This Memo\n\n This document is no","scope_keywords":["7661","http","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 7661 This document provides a mechanism to address issues that arise when\n TCP is used for traffic that exhibits periods where the sending rate\n is limited by the application rather than the congestion window. It\n provides an experimental update to TCP that allows a TCP sender to\n restart quickly following a rate-limited interval. This method is\n expected to benefit applications that send rate-limited traffic using\n TCP while also providing an appropriate response if congestion is\n experienced.\n\n This document also evaluates the Experimental specification of TCP\n Congestion Window Validation (CWV) defined in RFC 2861 and concludes\n that RFC 2861 sought to address important issues but failed to\n deliver a widely used solution. This document therefore reclassifies\n the status of RFC 2861 from Experimental to Historic. This document\n obsoletes RFC 2861.\n\nStatus of This Memo\n\n This document is no 7661 http license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7872","type":"specification","body":"IETF","designation":"RFC 7872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7872.txt","https://www.rfc-editor.org/rfc/rfc7872.pdf"],"folder":"IETF/RFC-7872","files":{"txt":{"path":"standards/IETF/RFC-7872/RFC-7872.txt","sha256":"ba2fddd77e46eaa97a74d8bd8dfb8e774ea49da9e34ca7d368fe7c0cd14168b1"}},"tags":["nested-reference","unchanged"],"summary":"This document presents real-world data regarding the extent to which\n packets with IPv6 Extension Headers (EHs) are dropped in the Internet\n (as originally measured in August 2014 and later in June 2015, with\n similar results) and where in the network such dropping occurs. The\n aforementioned results serve as a problem statement that is expected\n to trigger operational advice on the filtering of IPv6 packets\n carrying IPv6 EHs so that the situation improves over time. This\n document also explains how the results were obtained, such that the\n corresponding measurements can be reproduced by other members of the\n community and repeated over time to observe changes in the handling\n of packets with IPv6 EHs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineerin","scope_keywords":["7872","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7872 This document presents real-world data regarding the extent to which\n packets with IPv6 Extension Headers (EHs) are dropped in the Internet\n (as originally measured in August 2014 and later in June 2015, with\n similar results) and where in the network such dropping occurs. The\n aforementioned results serve as a problem statement that is expected\n to trigger operational advice on the filtering of IPv6 packets\n carrying IPv6 EHs so that the situation improves over time. This\n document also explains how the results were obtained, such that the\n corresponding measurements can be reproduced by other members of the\n community and repeated over time to observe changes in the handling\n of packets with IPv6 EHs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineerin 7872 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7918","type":"specification","body":"IETF","designation":"RFC 7918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7918.txt","https://www.rfc-editor.org/rfc/rfc7918.pdf"],"folder":"IETF/RFC-7918","files":{"txt":{"path":"standards/IETF/RFC-7918/RFC-7918.txt","sha256":"ccacb8e3e223ebd90800ee413eaf8fec9909088fad85850af9961c8ca2447cae"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an optional behavior of Transport Layer\n Security (TLS) client implementations, dubbed \"False Start\". It\n affects only protocol timing, not on-the-wire protocol data, and can\n be implemented unilaterally. A TLS False Start reduces handshake\n latency to one round trip.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma","scope_keywords":["7918","certificate","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7918 This document specifies an optional behavior of Transport Layer\n Security (TLS) client implementations, dubbed \"False Start\". It\n affects only protocol timing, not on-the-wire protocol data, and can\n be implemented unilaterally. A TLS False Start reduces handshake\n latency to one round trip.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma 7918 certificate http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7996","type":"specification","body":"IETF","designation":"RFC 7996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7996.txt","https://www.rfc-editor.org/rfc/rfc7996.pdf"],"folder":"IETF/RFC-7996","files":{"txt":{"path":"standards/IETF/RFC-7996/RFC-7996.txt","sha256":"01fdd56d84368be9371b79d2645d8c066f8b5bb651beefe09bf810ab1d174c13"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies SVG 1.2 RFC -- an SVG profile for use in\n diagrams that may appear in RFCs -- and considers some of the issues\n concerning the creation and use of such diagrams.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7996.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust a","scope_keywords":["7996","attribute","attributes","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null}],"search_text":"IETF RFC 7996 This document specifies SVG 1.2 RFC -- an SVG profile for use in\n diagrams that may appear in RFCs -- and considers some of the issues\n concerning the creation and use of such diagrams.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7996.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust a 7996 attribute attributes http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8257","type":"specification","body":"IETF","designation":"RFC 8257","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8257.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8257.txt","https://www.rfc-editor.org/rfc/rfc8257.pdf"],"folder":"IETF/RFC-8257","files":{"txt":{"path":"standards/IETF/RFC-8257/RFC-8257.txt","sha256":"41fa12484a6c9654ea5e67b455ce7cba217e9b25d325588d6cf4b182aa819845"}},"tags":["nested-reference","unchanged"],"summary":"This Informational RFC describes Data Center TCP (DCTCP): a TCP\n congestion control scheme for data-center traffic. DCTCP extends the\n Explicit Congestion Notification (ECN) processing to estimate the\n fraction of bytes that encounter congestion rather than simply\n detecting that some congestion has occurred. DCTCP then scales the\n TCP congestion window based on this estimate. This method achieves\n high-burst tolerance, low latency, and high throughput with shallow-\n buffered switches. This memo also discusses deployment issues\n related to the coexistence of DCTCP and conventional TCP, discusses\n the lack of a negotiating mechanism between sender and receiver, and\n presents some possible mitigations. This memo documents DCTCP as\n currently implemented by several major operating systems. DCTCP, as\n described in this specification, is applicable to deployments in\n controlled environments l","scope_keywords":["8257","algorithm","http","https","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null}],"search_text":"IETF RFC 8257 This Informational RFC describes Data Center TCP (DCTCP): a TCP\n congestion control scheme for data-center traffic. DCTCP extends the\n Explicit Congestion Notification (ECN) processing to estimate the\n fraction of bytes that encounter congestion rather than simply\n detecting that some congestion has occurred. DCTCP then scales the\n TCP congestion window based on this estimate. This method achieves\n high-burst tolerance, low latency, and high throughput with shallow-\n buffered switches. This memo also discusses deployment issues\n related to the coexistence of DCTCP and conventional TCP, discusses\n the lack of a negotiating mechanism between sender and receiver, and\n presents some possible mitigations. This memo documents DCTCP as\n currently implemented by several major operating systems. DCTCP, as\n described in this specification, is applicable to deployments in\n controlled environments l 8257 algorithm http https license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8314","type":"specification","body":"IETF","designation":"RFC 8314","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8314.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8314.txt","https://www.rfc-editor.org/rfc/rfc8314.pdf"],"folder":"IETF/RFC-8314","files":{"txt":{"path":"standards/IETF/RFC-8314/RFC-8314.txt","sha256":"d626efa01a2176206b81742b77ca8f0d61e4a669f9ae7798e7ae556afc65aae6"}},"tags":["nested-reference","unchanged"],"summary":"This specification outlines current recommendations for the use of\n Transport Layer Security (TLS) to provide confidentiality of email\n traffic between a Mail User Agent (MUA) and a Mail Submission Server\n or Mail Access Server. This document updates RFCs 1939, 2595, 3501,\n 5068, 6186, and 6409.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8314.\n\nCopyright Notice\n\n Copyright (c) 2018","scope_keywords":["8314","authentication","certificate","encryption","http","https","license","registered","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 8314 This specification outlines current recommendations for the use of\n Transport Layer Security (TLS) to provide confidentiality of email\n traffic between a Mail User Agent (MUA) and a Mail Submission Server\n or Mail Access Server. This document updates RFCs 1939, 2595, 3501,\n 5068, 6186, and 6409.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8314.\n\nCopyright Notice\n\n Copyright (c) 2018 8314 authentication certificate encryption http https license registered subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8841","type":"specification","body":"IETF","designation":"RFC 8841","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8841.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8841.txt","https://www.rfc-editor.org/rfc/rfc8841.pdf"],"folder":"IETF/RFC-8841","files":{"pdf":{"path":"standards/IETF/RFC-8841/RFC-8841.pdf","sha256":"d90a7831b46255b93139ebd1d5a6245a2ff1d36ec2364aae2e4698d7b4cdc4c6"},"txt":{"path":"standards/IETF/RFC-8841/RFC-8841.txt","sha256":"c4942cf98aa4ada20c69655e719dc9d353d45a819b06b294adb2cfa8bb2545b2"}},"tags":["nested-reference","unchanged"],"summary":"The Stream Control Transmission Protocol (SCTP) is a transport\n protocol used to establish associations between two endpoints. RFC\n 8261 specifies how SCTP can be used on top of the Datagram Transport\n Layer Security (DTLS) protocol, which is referred to as SCTP-over-\n DTLS.\n\n This specification defines the following new Session Description\n Protocol (SDP) protocol identifiers (proto values): \"UDP/DTLS/SCTP\"\n and \"TCP/DTLS/SCTP\". This specification also specifies how to use\n the new proto values with the SDP offer/answer mechanism for\n negotiating SCTP-over-DTLS associations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG).","scope_keywords":["8841","attribute","attributes","delivery","http","https","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 8841 The Stream Control Transmission Protocol (SCTP) is a transport\n protocol used to establish associations between two endpoints. RFC\n 8261 specifies how SCTP can be used on top of the Datagram Transport\n Layer Security (DTLS) protocol, which is referred to as SCTP-over-\n DTLS.\n\n This specification defines the following new Session Description\n Protocol (SDP) protocol identifiers (proto values): \"UDP/DTLS/SCTP\"\n and \"TCP/DTLS/SCTP\". This specification also specifies how to use\n the new proto values with the SDP offer/answer mechanism for\n negotiating SCTP-over-DTLS associations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). 8841 attribute attributes delivery http https key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8985","type":"specification","body":"IETF","designation":"RFC 8985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8985.txt","https://www.rfc-editor.org/rfc/rfc8985.pdf"],"folder":"IETF/RFC-8985","files":{"pdf":{"path":"standards/IETF/RFC-8985/RFC-8985.pdf","sha256":"73c5d624e32a84e2a00fe6b0ac691287242e38dff0af658b47846cf689897f0a"},"txt":{"path":"standards/IETF/RFC-8985/RFC-8985.txt","sha256":"5b947b1dad18d60ed4550e36e0f474d1678412a413b4664feb5d1428e27d7c5f"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the RACK-TLP loss detection algorithm for TCP.\n RACK-TLP uses per-segment transmit timestamps and selective\n acknowledgments (SACKs) and has two parts. Recent Acknowledgment\n (RACK) starts fast recovery quickly using time-based inferences\n derived from acknowledgment (ACK) feedback, and Tail Loss Probe (TLP)\n leverages RACK and sends a probe packet to trigger ACK feedback to\n avoid retransmission timeout (RTO) events. Compared to the widely\n used duplicate acknowledgment (DupAck) threshold approach, RACK-TLP\n detects losses more efficiently when there are application-limited\n flights of data, lost retransmissions, or data packet reordering\n events. It is intended to be an alternative to the DupAck threshold\n approach.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It ","scope_keywords":["8985","algorithm","algorithms","http","https","license","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 8985 This document presents the RACK-TLP loss detection algorithm for TCP.\n RACK-TLP uses per-segment transmit timestamps and selective\n acknowledgments (SACKs) and has two parts. Recent Acknowledgment\n (RACK) starts fast recovery quickly using time-based inferences\n derived from acknowledgment (ACK) feedback, and Tail Loss Probe (TLP)\n leverages RACK and sends a probe packet to trigger ACK feedback to\n avoid retransmission timeout (RTO) events. Compared to the widely\n used duplicate acknowledgment (DupAck) threshold approach, RACK-TLP\n detects losses more efficiently when there are application-limited\n flights of data, lost retransmissions, or data packet reordering\n events. It is intended to be an alternative to the DupAck threshold\n approach.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It  8985 algorithm algorithms http https license subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 9113","type":"specification","body":"IETF","designation":"RFC 9113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9113.txt","https://www.rfc-editor.org/rfc/rfc9113.pdf"],"folder":"IETF/RFC-9113","files":{"pdf":{"path":"standards/IETF/RFC-9113/RFC-9113.pdf","sha256":"8314f1034854548baf26f9912f79c6207299cb0520b31ed25af64889bd1500bc"},"txt":{"path":"standards/IETF/RFC-9113/RFC-9113.txt","sha256":"a00ef91b64e111a282e77ec66980f5242e77c0bb5e33e0927e3b6757080506de"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes an optimized expression of the semantics\n of the Hypertext Transfer Protocol (HTTP), referred to as HTTP\n version 2 (HTTP/2). HTTP/2 enables a more efficient use of network\n resources and a reduced latency by introducing field compression and\n allowing multiple concurrent exchanges on the same connection.\n\n This document obsoletes RFCs 7540 and 8740.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine","scope_keywords":["9113","http","https","identification","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null}],"search_text":"IETF RFC 9113 This specification describes an optimized expression of the semantics\n of the Hypertext Transfer Protocol (HTTP), referred to as HTTP\n version 2 (HTTP/2). HTTP/2 enables a more efficient use of network\n resources and a reduced latency by introducing field compression and\n allowing multiple concurrent exchanges on the same connection.\n\n This document obsoletes RFCs 7540 and 8740.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine 9113 http https identification license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9114","type":"specification","body":"IETF","designation":"RFC 9114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9114.txt","https://www.rfc-editor.org/rfc/rfc9114.pdf"],"folder":"IETF/RFC-9114","files":{"pdf":{"path":"standards/IETF/RFC-9114/RFC-9114.pdf","sha256":"ecc538dc3d8e9cb3f8d73c3c10189f91bdc7b81f80c570ce658760e5d6f5db84"},"txt":{"path":"standards/IETF/RFC-9114/RFC-9114.txt","sha256":"6b84555c88eeebcf5d2b2e1d9d7b58630abc97ab877b2cf62dee4cd635db34e4"}},"tags":["nested-reference","unchanged"],"summary":"The QUIC transport protocol has several features that are desirable\n in a transport for HTTP, such as stream multiplexing, per-stream flow\n control, and low-latency connection establishment. This document\n describes a mapping of HTTP semantics over QUIC. This document also\n identifies HTTP/2 features that are subsumed by QUIC and describes\n how HTTP/2 extensions can be ported to HTTP/3.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be","scope_keywords":["9114","authentication","delivery","http","https","identification","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 9114 The QUIC transport protocol has several features that are desirable\n in a transport for HTTP, such as stream multiplexing, per-stream flow\n control, and low-latency connection establishment. This document\n describes a mapping of HTTP semantics over QUIC. This document also\n identifies HTTP/2 features that are subsumed by QUIC and describes\n how HTTP/2 extensions can be ported to HTTP/3.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be 9114 authentication delivery http https identification license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 0813","type":"specification","body":"IETF","designation":"RFC 0813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0813.txt","https://www.rfc-editor.org/rfc/rfc0813.pdf"],"folder":"IETF/RFC-0813","files":{"txt":{"path":"standards/IETF/RFC-0813/RFC-0813.txt","sha256":"245a5544849581cf930ecb897aaa93e416b6be5da36cd88239cdafa2ff62fde8"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 813\n\n \n WINDOW AND ACKNOWLEDGEMENT STRATEGY IN TCP\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n This document describes implementation strategies to deal with two\n\nmechanisms in TCP, the window and the acknowledgement. These mechanisms\n\nare described in the specification document, but it is possible, while\n\ncomplying with the specification, to produce implementations which yield\n\nvery bad performance. Happily, the pitfalls possible in window and\n\nacknowledgement strategies are very easy to avoid.\n\n It is a much more difficult exercise to verify the performance of a\n\nspecification than the correctness. Certainly, we have less experience\n\nin this area, and we certainly lack any useful formal technique.\n\nNonetheless, it is important to attempt a specification in this area,\n\nbecause different implementor","scope_keywords":["0813","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null}],"search_text":"IETF RFC 0813 RFC: 813\n\n \n WINDOW AND ACKNOWLEDGEMENT STRATEGY IN TCP\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n This document describes implementation strategies to deal with two\n\nmechanisms in TCP, the window and the acknowledgement. These mechanisms\n\nare described in the specification document, but it is possible, while\n\ncomplying with the specification, to produce implementations which yield\n\nvery bad performance. Happily, the pitfalls possible in window and\n\nacknowledgement strategies are very easy to avoid.\n\n It is a much more difficult exercise to verify the performance of a\n\nspecification than the correctness. Certainly, we have less experience\n\nin this area, and we certainly lack any useful formal technique.\n\nNonetheless, it is important to attempt a specification in this area,\n\nbecause different implementor 0813 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 0814","type":"specification","body":"IETF","designation":"RFC 0814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0814.txt","https://www.rfc-editor.org/rfc/rfc0814.pdf"],"folder":"IETF/RFC-0814","files":{"txt":{"path":"standards/IETF/RFC-0814/RFC-0814.txt","sha256":"6fe70f10aa4df70bcec56bc42935e212a2c06c6e0ce64c578a229c40775afdc5"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 814\n\n NAME, ADDRESSES, PORTS, AND ROUTES\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n It has been said that the principal function of an operating system\n\nis to define a number of different names for the same object, so that it\n\ncan busy itself keeping track of the relationship between all of the\n\ndifferent names. Network protocols seem to have somewhat the same\n\ncharacteristic. In TCP/IP, there are several ways of referring to\n\nthings. At the human visible interface, there are character string\n\n\"names\" to identify networks, hosts, and services. Host names are\n\ntranslated into network \"addresses\", 32-bit values that identify the\n\nnetwork to which a host is attached, and the location of the host on\n\nthat net. Service names are translated into a \"port identifier\", which\n\nin TCP is a 16-bit value. Final","scope_keywords":["0814","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null}],"search_text":"IETF RFC 0814 RFC: 814\n\n NAME, ADDRESSES, PORTS, AND ROUTES\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n It has been said that the principal function of an operating system\n\nis to define a number of different names for the same object, so that it\n\ncan busy itself keeping track of the relationship between all of the\n\ndifferent names. Network protocols seem to have somewhat the same\n\ncharacteristic. In TCP/IP, there are several ways of referring to\n\nthings. At the human visible interface, there are character string\n\n\"names\" to identify networks, hosts, and services. Host names are\n\ntranslated into network \"addresses\", 32-bit values that identify the\n\nnetwork to which a host is attached, and the location of the host on\n\nthat net. Service names are translated into a \"port identifier\", which\n\nin TCP is a 16-bit value. Final 0814 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 0815","type":"specification","body":"IETF","designation":"RFC 0815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0815.txt","https://www.rfc-editor.org/rfc/rfc0815.pdf"],"folder":"IETF/RFC-0815","files":{"txt":{"path":"standards/IETF/RFC-0815/RFC-0815.txt","sha256":"db8097b149042244d0e05e32cbd0718e8e3bf77f70608b4c46e4541abcaea08f"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 815\n\n IP DATAGRAM REASSEMBLY ALGORITHMS\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n One of the mechanisms of IP is fragmentation and reassembly. Under\n\ncertain circumstances, a datagram originally transmitted as a single\n\nunit will arrive at its final destination broken into several fragments.\n\nThe IP layer at the receiving host must accumulate these fragments until\n\nenough have arrived to completely reconstitute the original datagram.\n\nThe specification document for IP gives a complete description of the\n\nreassembly mechanism, and contains several examples. It also provides\n\none possible algorithm for reassembly, based on keeping track of\n\narriving fragments in a vector of bits. This document describes an\n\nalternate approach which should prove more suitable in some machines.\n\n A superficial examina","scope_keywords":["0815","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 0815 RFC: 815\n\n IP DATAGRAM REASSEMBLY ALGORITHMS\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n One of the mechanisms of IP is fragmentation and reassembly. Under\n\ncertain circumstances, a datagram originally transmitted as a single\n\nunit will arrive at its final destination broken into several fragments.\n\nThe IP layer at the receiving host must accumulate these fragments until\n\nenough have arrived to completely reconstitute the original datagram.\n\nThe specification document for IP gives a complete description of the\n\nreassembly mechanism, and contains several examples. It also provides\n\none possible algorithm for reassembly, based on keeping track of\n\narriving fragments in a vector of bits. This document describes an\n\nalternate approach which should prove more suitable in some machines.\n\n A superficial examina 0815 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 0816","type":"specification","body":"IETF","designation":"RFC 0816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0816.txt","https://www.rfc-editor.org/rfc/rfc0816.pdf"],"folder":"IETF/RFC-0816","files":{"txt":{"path":"standards/IETF/RFC-0816/RFC-0816.txt","sha256":"3c00723e94de1abb98313c04c1415e0de3c0ae8721d2a2597043f36bce93504f"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 816\n\n FAULT ISOLATION AND RECOVERY\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Occasionally, a network or a gateway will go down, and the sequence\n\nof hops which the packet takes from source to destination must change.\n\nFault isolation is that action which hosts and gateways collectively\n\ntake to determine that something is wrong; fault recovery is the\n\nidentification and selection of an alternative route which will serve to\n\nreconnect the source to the destination. In fact, the gateways perform\n\nmost of the functions of fault isolation and recovery. There are,\n\nhowever, a few actions which hosts must take if they wish to provide a\n\nreasonable level of service. This document describes the portion of\n\nfault isolation and recovery which is the responsibility of the host.\n\n 2. What Gateways Do\n\n Gatewa","scope_keywords":["0816","algorithm","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null}],"search_text":"IETF RFC 0816 RFC: 816\n\n FAULT ISOLATION AND RECOVERY\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Occasionally, a network or a gateway will go down, and the sequence\n\nof hops which the packet takes from source to destination must change.\n\nFault isolation is that action which hosts and gateways collectively\n\ntake to determine that something is wrong; fault recovery is the\n\nidentification and selection of an alternative route which will serve to\n\nreconnect the source to the destination. In fact, the gateways perform\n\nmost of the functions of fault isolation and recovery. There are,\n\nhowever, a few actions which hosts must take if they wish to provide a\n\nreasonable level of service. This document describes the portion of\n\nfault isolation and recovery which is the responsibility of the host.\n\n 2. What Gateways Do\n\n Gatewa 0816 algorithm identification nested-reference unchanged"},{"id":"IETF RFC 0817","type":"specification","body":"IETF","designation":"RFC 0817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0817.txt","https://www.rfc-editor.org/rfc/rfc0817.pdf"],"folder":"IETF/RFC-0817","files":{"txt":{"path":"standards/IETF/RFC-0817/RFC-0817.txt","sha256":"e615a41efddce03cb66592fd0dd3e0af203a57f8b5b7ca4b7deb82af47d1dbb6"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 817\n\n MODULARITY AND EFFICIENCY IN PROTOCOL IMPLEMENTATION\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Many protocol implementers have made the unpleasant discovery that\n\ntheir packages do not run quite as fast as they had hoped. The blame\n\nfor this widely observed problem has been attributed to a variety of\n\ncauses, ranging from details in the design of the protocol to the\n\nunderlying structure of the host operating system. This RFC will\n\ndiscuss some of the commonly encountered reasons why protocol\n\nimplementations seem to run slowly.\n\n Experience suggests that one of the most important factors in\n\ndetermining the performance of an implementation is the manner in which\n\nthat implementation is modularized and integrated into the host\n\noperating system. For this reason, it is useful to discuss the q","scope_keywords":["0817","attribute","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null}],"search_text":"IETF RFC 0817 RFC: 817\n\n MODULARITY AND EFFICIENCY IN PROTOCOL IMPLEMENTATION\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Many protocol implementers have made the unpleasant discovery that\n\ntheir packages do not run quite as fast as they had hoped. The blame\n\nfor this widely observed problem has been attributed to a variety of\n\ncauses, ranging from details in the design of the protocol to the\n\nunderlying structure of the host operating system. This RFC will\n\ndiscuss some of the commonly encountered reasons why protocol\n\nimplementations seem to run slowly.\n\n Experience suggests that one of the most important factors in\n\ndetermining the performance of an implementation is the manner in which\n\nthat implementation is modularized and integrated into the host\n\noperating system. For this reason, it is useful to discuss the q 0817 attribute management path nested-reference unchanged"},{"id":"IETF RFC 0819","type":"specification","body":"IETF","designation":"RFC 0819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0819.txt","https://www.rfc-editor.org/rfc/rfc0819.pdf"],"folder":"IETF/RFC-0819","files":{"txt":{"path":"standards/IETF/RFC-0819/RFC-0819.txt","sha256":"0e7845df0cb460e2831d916d8df3dd3d385b937540551f176607160672b1689e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Zaw-Sing Su (SRI)\nRequest for Comments: 819 Jon Postel (ISI)\n August 1982\n\n The Domain Naming Convention for Internet User Applications\n\n1. Introduction\n\n For many years, the naming convention \" @ \" has served the\n ARPANET user community for its mail system, and the substring\n \" \" has been used for other applications such as file transfer\n (FTP) and terminal access (Telnet). With the advent of network\n interconnection, this naming convention needs to be generalized to\n accommodate internetworking. A decision has recently been reached to\n replace the simple name field, \" \", by a composite name field,\n \" \" [2]. This note is an attempt to clarify this generalized\n naming convention, the Internet Naming Convention, and to explore the\n implications of its adoption for Internet name service and user\n applications.\n\n The following example illustrates the changes in naming ","scope_keywords":["0819","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 0819 Network Working Group Zaw-Sing Su (SRI)\nRequest for Comments: 819 Jon Postel (ISI)\n August 1982\n\n The Domain Naming Convention for Internet User Applications\n\n1. Introduction\n\n For many years, the naming convention \" @ \" has served the\n ARPANET user community for its mail system, and the substring\n \" \" has been used for other applications such as file transfer\n (FTP) and terminal access (Telnet). With the advent of network\n interconnection, this naming convention needs to be generalized to\n accommodate internetworking. A decision has recently been reached to\n replace the simple name field, \" \", by a composite name field,\n \" \" [2]. This note is an attempt to clarify this generalized\n naming convention, the Internet Naming Convention, and to explore the\n implications of its adoption for Internet name service and user\n applications.\n\n The following example illustrates the changes in naming  0819 presentation subject nested-reference unchanged"},{"id":"IETF RFC 7719","type":"specification","body":"IETF","designation":"RFC 7719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7719.txt","https://www.rfc-editor.org/rfc/rfc7719.pdf"],"folder":"IETF/RFC-7719","files":{"txt":{"path":"standards/IETF/RFC-7719/RFC-7719.txt","sha256":"a29d2fc193afa4801aff7ee2cca038a746f78937d0751f72a04a05c3e837d4de"}},"tags":["nested-reference","unchanged"],"summary":"The DNS is defined in literally dozens of different RFCs. The\n terminology used by implementers and developers of DNS protocols, and\n by operators of DNS systems, has sometimes changed in the decades\n since the DNS was first defined. This document gives current\n definitions for many of the terms used in the DNS in a single\n document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any er","scope_keywords":["7719","http","https","license","path","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7719 The DNS is defined in literally dozens of different RFCs. The\n terminology used by implementers and developers of DNS protocols, and\n by operators of DNS systems, has sometimes changed in the decades\n since the DNS was first defined. This document gives current\n definitions for many of the terms used in the DNS in a single\n document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any er 7719 http https license path qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 8499","type":"specification","body":"IETF","designation":"RFC 8499","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8499.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8499.txt","https://www.rfc-editor.org/rfc/rfc8499.pdf"],"folder":"IETF/RFC-8499","files":{"txt":{"path":"standards/IETF/RFC-8499/RFC-8499.txt","sha256":"61e542c24a23f0c982573a53c390b76ccfbd9a645d613b7f1a35c233f1154e16"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) is defined in literally dozens of\n different RFCs. The terminology used by implementers and developers\n of DNS protocols, and by operators of DNS systems, has sometimes\n changed in the decades since the DNS was first defined. This\n document gives current definitions for many of the terms used in the\n DNS in a single document.\n\n This document obsoletes RFC 7719 and updates RFC 2308.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide fe","scope_keywords":["8499","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 8499 The Domain Name System (DNS) is defined in literally dozens of\n different RFCs. The terminology used by implementers and developers\n of DNS protocols, and by operators of DNS systems, has sometimes\n changed in the decades since the DNS was first defined. This\n document gives current definitions for many of the terms used in the\n DNS in a single document.\n\n This document obsoletes RFC 7719 and updates RFC 2308.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide fe 8499 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 0820","type":"specification","body":"IETF","designation":"RFC 0820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0820.txt","https://www.rfc-editor.org/rfc/rfc0820.pdf"],"folder":"IETF/RFC-0820","files":{"txt":{"path":"standards/IETF/RFC-0820/RFC-0820.txt","sha256":"0a3ac8fc3f7296335859f43648e7cc627c61b20f087968d58d68bc9fd60617ac"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 820 J. Vernon\n January 1983\n\nObsoletes RFCs: 790, 776, 770, 762,\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon, subject to the agreement between\nDARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A\nof this RFC. If you are developing a protocol or application that will\nrequire the use of a link, socket, port, protocol, or network number\nplease contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marin","scope_keywords":["0820","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 0820 Network Working Group J. Postel\nRequest for Comments: 820 J. Vernon\n January 1983\n\nObsoletes RFCs: 790, 776, 770, 762,\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon, subject to the agreement between\nDARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A\nof this RFC. If you are developing a protocol or application that will\nrequire the use of a link, socket, port, protocol, or network number\nplease contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marin 0820 risk subject nested-reference unchanged"},{"id":"IETF RFC 0821","type":"specification","body":"IETF","designation":"RFC 0821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0821.txt","https://www.rfc-editor.org/rfc/rfc0821.pdf"],"folder":"IETF/RFC-0821","files":{"txt":{"path":"standards/IETF/RFC-0821/RFC-0821.txt","sha256":"b7111020e63d77bc84fbcebf8adb0638a1bb0efaeed2e289def743b4fe994882"}},"tags":["nested-reference","unchanged"],"summary":"RFC 821\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1982\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nRFC 821 August 1982\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 11\n 3.5. Opening and Closing ..................................... 13\n 3.6. Relaying .........................","scope_keywords":["0821"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 0821 RFC 821\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1982\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nRFC 821 August 1982\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 11\n 3.5. Opening and Closing ..................................... 13\n 3.6. Relaying ......................... 0821 nested-reference unchanged"},{"id":"IETF RFC 3023","type":"specification","body":"IETF","designation":"RFC 3023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3023.txt","https://www.rfc-editor.org/rfc/rfc3023.pdf"],"folder":"IETF/RFC-3023","files":{"txt":{"path":"standards/IETF/RFC-3023/RFC-3023.txt","sha256":"d49b59e3a4dc8383a2a7607c2f403707bcd8030721164dce2e3f6c53df6ed074"}},"tags":["nested-reference","unchanged"],"summary":"This document standardizes five new media types -- text/xml,\n application/xml, text/xml-external-parsed-entity, application/xml-\n external-parsed-entity, and application/xml-dtd -- for use in\n exchanging network entities that are related to the Extensible Markup\n Language (XML). This document also standardizes a convention (using\n the suffix '+xml') for naming media types outside of these five types\n when those media types represent XML MIME (Multipurpose Internet Mail\n Extensions) entities. XML MIME entities are currently exchanged via\n the HyperText Transfer Protocol on the World Wide Web, are an\n integral part of the WebDAV protocol for remote web authoring, and\n are expected to have utility in many domains.\n\n Major differences from RFC 2376 are (1) the addition of text/xml-\n external-parsed-entity, application/xml-external-parsed-entity, and\n application/xml-dtd, (2) the '+xml' suffi","scope_keywords":["3023"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3902","folder":"IETF/RFC-3902","source":"IETF/RFC-3902/RFC-3902.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4267","folder":"IETF/RFC-4267","source":"IETF/RFC-4267/RFC-4267.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6351","folder":"IETF/RFC-6351","source":"IETF/RFC-6351/RFC-6351.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 3023 This document standardizes five new media types -- text/xml,\n application/xml, text/xml-external-parsed-entity, application/xml-\n external-parsed-entity, and application/xml-dtd -- for use in\n exchanging network entities that are related to the Extensible Markup\n Language (XML). This document also standardizes a convention (using\n the suffix '+xml') for naming media types outside of these five types\n when those media types represent XML MIME (Multipurpose Internet Mail\n Extensions) entities. XML MIME entities are currently exchanged via\n the HyperText Transfer Protocol on the World Wide Web, are an\n integral part of the WebDAV protocol for remote web authoring, and\n are expected to have utility in many domains.\n\n Major differences from RFC 2376 are (1) the addition of text/xml-\n external-parsed-entity, application/xml-external-parsed-entity, and\n application/xml-dtd, (2) the '+xml' suffi 3023 nested-reference unchanged"},{"id":"IETF RFC 5068","type":"specification","body":"IETF","designation":"RFC 5068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5068.txt","https://www.rfc-editor.org/rfc/rfc5068.pdf"],"folder":"IETF/RFC-5068","files":{"txt":{"path":"standards/IETF/RFC-5068/RFC-5068.txt","sha256":"0136f311c6eeca306aaf577af221e615986d1077fc61dba121e7d700d465a09b"}},"tags":["nested-reference","unchanged"],"summary":"Email has become a popular distribution service for a variety of\n socially unacceptable, mass-effect purposes. The most obvious ones\n include spam and worms. This note recommends conventions for the\n operation of email submission and transport services between\n independent operators, such as enterprises and Internet Service\n Providers. Its goal is to improve lines of accountability for\n controlling abusive uses of the Internet mail service. To this end,\n this document offers recommendations for constructive operational\n policies between independent operators of email submission and\n transmission services.\n\n Email authentication technologies are aimed at providing assurances\n and traceability between internetworked networks. In many email\n services, the weakest link in the chain of assurances is initial\n submission of a message. This document offers recommendations for\n constructive opera","scope_keywords":["5068","authentication","authorization","delivery","pid","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null}],"search_text":"IETF RFC 5068 Email has become a popular distribution service for a variety of\n socially unacceptable, mass-effect purposes. The most obvious ones\n include spam and worms. This note recommends conventions for the\n operation of email submission and transport services between\n independent operators, such as enterprises and Internet Service\n Providers. Its goal is to improve lines of accountability for\n controlling abusive uses of the Internet mail service. To this end,\n this document offers recommendations for constructive operational\n policies between independent operators of email submission and\n transmission services.\n\n Email authentication technologies are aimed at providing assurances\n and traceability between internetworked networks. In many email\n services, the weakest link in the chain of assurances is initial\n submission of a message. This document offers recommendations for\n constructive opera 5068 authentication authorization delivery pid policies nested-reference unchanged"},{"id":"IETF RFC 6055","type":"specification","body":"IETF","designation":"RFC 6055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6055.txt","https://www.rfc-editor.org/rfc/rfc6055.pdf"],"folder":"IETF/RFC-6055","files":{"txt":{"path":"standards/IETF/RFC-6055/RFC-6055.txt","sha256":"77dfbbb29f411add3abf5348726a4ea5ad7f2d8db36fd45098d87b80938f5a08"}},"tags":["nested-reference","unchanged"],"summary":"This document explores issues with Internationalized Domain Names\n (IDNs) that result from the use of various encoding schemes such as\n UTF-8 and the ASCII-Compatible Encoding produced by the Punycode\n algorithm. It focuses on the importance of agreeing on a single\n encoding and how complicated the state of affairs ends up being as a\n result of using different encodings today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["6055","algorithm","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6055 This document explores issues with Internationalized Domain Names\n (IDNs) that result from the use of various encoding schemes such as\n UTF-8 and the ASCII-Compatible Encoding produced by the Punycode\n algorithm. It focuses on the importance of agreeing on a single\n encoding and how complicated the state of affairs ends up being as a\n result of using different encodings today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 6055 algorithm http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6530","type":"specification","body":"IETF","designation":"RFC 6530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6530.txt","https://www.rfc-editor.org/rfc/rfc6530.pdf"],"folder":"IETF/RFC-6530","files":{"txt":{"path":"standards/IETF/RFC-6530/RFC-6530.txt","sha256":"a755d85d9963e91c8cde3cfa471d1061c9734eb2dd750d95eb51cd30dc0231f6"}},"tags":["nested-reference","unchanged"],"summary":"Full use of electronic mail throughout the world requires that\n (subject to other constraints) people be able to use close variations\n on their own names (written correctly in their own languages and\n scripts) as mailbox names in email addresses. This document\n introduces a series of specifications that define mechanisms and\n protocol extensions needed to fully support internationalized email\n addresses. These changes include an SMTP extension and extension of\n email header syntax to accommodate UTF-8 data. The document set also\n includes discussion of key assumptions and issues in deploying fully\n internationalized email. This document is a replacement for RFC\n 4952; it reflects additional issues identified since that document\n was published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). ","scope_keywords":["6530","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null}],"search_text":"IETF RFC 6530 Full use of electronic mail throughout the world requires that\n (subject to other constraints) people be able to use close variations\n on their own names (written correctly in their own languages and\n scripts) as mailbox names in email addresses. This document\n introduces a series of specifications that define mechanisms and\n protocol extensions needed to fully support internationalized email\n addresses. These changes include an SMTP extension and extension of\n email header syntax to accommodate UTF-8 data. The document set also\n includes discussion of key assumptions and issues in deploying fully\n internationalized email. This document is a replacement for RFC\n 4952; it reflects additional issues identified since that document\n was published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF).  6530 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 0822","type":"specification","body":"IETF","designation":"RFC 0822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0822.txt","https://www.rfc-editor.org/rfc/rfc0822.pdf"],"folder":"IETF/RFC-0822","files":{"txt":{"path":"standards/IETF/RFC-0822/RFC-0822.txt","sha256":"1e7bc6c75e4c6866c54cbf26ae280b96cac9e87d6293db5a21d7aaf4ffb8bc1a"}},"tags":["nested-reference","unchanged"],"summary":"RFC # 822\n\n Obsoletes: RFC #733 (NIC #41952)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA INTERNET TEXT MESSAGES\n\n August 13, 1982\n\n Revised by\n\n David H. Crocker\n\n Dept. of Electrical Engineering\n University of Delaware, Newark, DE 19711\n Network: DCrocker @ UDel-Relay\n\n\f\n\n \n Standard for ARPA Internet Text Messages\n\n TABLE OF CONTENTS\n\n PREFACE .................................................... ii\n\n 1. INTRODUCTION ........................................... 1\n\n 1.1. Scope ............................................ 1\n 1.2. Communication Framework .......................... 2\n\n 2. NOTATIONAL CONVENTIONS ................................. 3\n\n 3. LEXICAL ANALYSIS OF MESSAGES ........................... 5\n\n 3.1. General Description .............................. 5\n 3.2. Header Field Definitions ......................... 9\n 3.3. Lexical Tokens ................................... 10\n 3.4. Clarific","scope_keywords":["0822","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 0822 RFC # 822\n\n Obsoletes: RFC #733 (NIC #41952)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA INTERNET TEXT MESSAGES\n\n August 13, 1982\n\n Revised by\n\n David H. Crocker\n\n Dept. of Electrical Engineering\n University of Delaware, Newark, DE 19711\n Network: DCrocker @ UDel-Relay\n\n\f\n\n \n Standard for ARPA Internet Text Messages\n\n TABLE OF CONTENTS\n\n PREFACE .................................................... ii\n\n 1. INTRODUCTION ........................................... 1\n\n 1.1. Scope ............................................ 1\n 1.2. Communication Framework .......................... 2\n\n 2. NOTATIONAL CONVENTIONS ................................. 3\n\n 3. LEXICAL ANALYSIS OF MESSAGES ........................... 5\n\n 3.1. General Description .............................. 5\n 3.2. Header Field Definitions ......................... 9\n 3.3. Lexical Tokens ................................... 10\n 3.4. Clarific 0822 delivery presentation nested-reference unchanged"},{"id":"IETF RFC 4250","type":"specification","body":"IETF","designation":"RFC 4250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4250.txt","https://www.rfc-editor.org/rfc/rfc4250.pdf"],"folder":"IETF/RFC-4250","files":{"txt":{"path":"standards/IETF/RFC-4250/RFC-4250.txt","sha256":"eb3a9d7c3e1fae53c038d5ae62a73e62280d1dde8b246129969c95e4d0909341"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the instructions to the IANA and the initial\n state of the IANA assigned numbers for the Secure Shell (SSH)\n protocol. It is intended only for the initialization of the IANA\n registries referenced in the set of SSH documents.","scope_keywords":["4250","algorithm","authentication","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4345","folder":"IETF/RFC-4345","source":"IETF/RFC-4345/RFC-4345.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 4250 This document defines the instructions to the IANA and the initial\n state of the IANA assigned numbers for the Secure Shell (SSH)\n protocol. It is intended only for the initialization of the IANA\n registries referenced in the set of SSH documents. 4250 algorithm authentication encryption key nested-reference unchanged"},{"id":"IETF RFC 4251","type":"specification","body":"IETF","designation":"RFC 4251","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4251.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4251.txt","https://www.rfc-editor.org/rfc/rfc4251.pdf"],"folder":"IETF/RFC-4251","files":{"txt":{"path":"standards/IETF/RFC-4251/RFC-4251.txt","sha256":"23a5052796d29edc2f0ff4f5be557df244544d129cfc26ed51971a6485eff4ef"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Shell (SSH) Protocol is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes the architecture of the SSH protocol, as well as\n the notation and terminology used in SSH protocol documents. It also\n discusses the SSH algorithm naming system that allows local\n extensions. The SSH protocol consists of three major components: The\n Transport Layer Protocol provides server authentication,\n confidentiality, and integrity with perfect forward secrecy. The\n User Authentication Protocol authenticates the client to the server.\n The Connection Protocol multiplexes the encrypted tunnel into several\n logical channels. Details of these protocols are described in\n separate documents.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4251 SSH Protocol Architecture January 2006","scope_keywords":["4251","algorithm","authentication","key","keys","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4345","folder":"IETF/RFC-4345","source":"IETF/RFC-4345/RFC-4345.txt","version":null},{"body":"IETF","designation":"RFC 4419","folder":"IETF/RFC-4419","source":"IETF/RFC-4419/RFC-4419.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null}],"search_text":"IETF RFC 4251 The Secure Shell (SSH) Protocol is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes the architecture of the SSH protocol, as well as\n the notation and terminology used in SSH protocol documents. It also\n discusses the SSH algorithm naming system that allows local\n extensions. The SSH protocol consists of three major components: The\n Transport Layer Protocol provides server authentication,\n confidentiality, and integrity with perfect forward secrecy. The\n User Authentication Protocol authenticates the client to the server.\n The Connection Protocol multiplexes the encrypted tunnel into several\n logical channels. Details of these protocols are described in\n separate documents.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4251 SSH Protocol Architecture January 2006 4251 algorithm authentication key keys policy presentation nested-reference unchanged"},{"id":"IETF RFC 4933","type":"specification","body":"IETF","designation":"RFC 4933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4933.txt","https://www.rfc-editor.org/rfc/rfc4933.pdf"],"folder":"IETF/RFC-4933","files":{"txt":{"path":"standards/IETF/RFC-4933/RFC-4933.txt","sha256":"eba0cbaea4a8cc1cfc4f2abd7eca71f4aaf5e953efdc2b46ddcb532ef21a0c12"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts. This document obsoletes RFC 3733.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4933 EPP Contact Mapping May 2007","scope_keywords":["4933","attribute","attributes","authorization","key","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null}],"search_text":"IETF RFC 4933 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts. This document obsoletes RFC 3733.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4933 EPP Contact Mapping May 2007 4933 attribute attributes authorization key management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5322","type":"specification","body":"IETF","designation":"RFC 5322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5322.txt","https://www.rfc-editor.org/rfc/rfc5322.pdf"],"folder":"IETF/RFC-5322","files":{"txt":{"path":"standards/IETF/RFC-5322/RFC-5322.txt","sha256":"cb459acca15a2aa895863eaeff6f1d5b9c4ca15578ae3e3706f757787a385969"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document specifies the Internet Message Format (IMF), a syntax\n for text messages that are sent between computer users, within the\n framework of \"electronic mail\" messages. This specification is a\n revision of Request For Comments (RFC) 2822, which itself superseded\n Request For Comments (RFC) 822, \"Standard for the Format of ARPA\n Internet Text Messages\", updating it to reflect current practice and\n incorporating incremental changes that were specified in other RFCs.\n\nResnick Standards Track [Page 1]\n\f\nRFC 5322 Internet Message Format October 2008","scope_keywords":["5322","attestation","attestations","attribute","attributes","identification","pid"],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 522-2","folder":"ETSI/EN-319-522-2-V1.2.1","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 522-3","folder":"ETSI/EN-319-522-3-V1.2.1","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 5322 This document specifies the Internet Message Format (IMF), a syntax\n for text messages that are sent between computer users, within the\n framework of \"electronic mail\" messages. This specification is a\n revision of Request For Comments (RFC) 2822, which itself superseded\n Request For Comments (RFC) 822, \"Standard for the Format of ARPA\n Internet Text Messages\", updating it to reflect current practice and\n incorporating incremental changes that were specified in other RFCs.\n\nResnick Standards Track [Page 1]\n\f\nRFC 5322 Internet Message Format October 2008 5322 attestation attestations attribute attributes identification pid cited-by-eu-law implementing-regulation nested-reference unchanged 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 5536","type":"specification","body":"IETF","designation":"RFC 5536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5536.txt","https://www.rfc-editor.org/rfc/rfc5536.pdf"],"folder":"IETF/RFC-5536","files":{"txt":{"path":"standards/IETF/RFC-5536/RFC-5536.txt","sha256":"141e122bd171ba414ed5afecec6073aa2db4e9f90119e2cde362c2c94ccb6733"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax of Netnews articles in the context\n of the Internet Message Format (RFC 5322) and Multipurpose Internet\n Mail Extensions (MIME) (RFC 2045). This document obsoletes RFC 1036,\n providing an updated specification to reflect current practice and\n incorporating incremental changes specified in other documents.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provis","scope_keywords":["5536","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 5536 This document specifies the syntax of Netnews articles in the context\n of the Internet Message Format (RFC 5322) and Multipurpose Internet\n Mail Extensions (MIME) (RFC 2045). This document obsoletes RFC 1036,\n providing an updated specification to reflect current practice and\n incorporating incremental changes specified in other documents.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provis 5536 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5733","type":"specification","body":"IETF","designation":"RFC 5733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5733.txt","https://www.rfc-editor.org/rfc/rfc5733.pdf"],"folder":"IETF/RFC-5733","files":{"txt":{"path":"standards/IETF/RFC-5733/RFC-5733.txt","sha256":"ab14bab1af1a3e6c17da4507b3f1783eebef828f21f49ba4238fbac90504c175"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts. This document obsoletes RFC 4933.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["5733","attribute","attributes","authorization","http","key","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 5733 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts. This document obsoletes RFC 4933.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  5733 attribute attributes authorization http key license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6331","type":"specification","body":"IETF","designation":"RFC 6331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6331.txt","https://www.rfc-editor.org/rfc/rfc6331.pdf"],"folder":"IETF/RFC-6331","files":{"txt":{"path":"standards/IETF/RFC-6331/RFC-6331.txt","sha256":"d8c5f3597adadee9733cce1ea2797d34bd0704c13caeff61409fc1ec91fd61d2"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes problems with the DIGEST-MD5 Simple\n Authentication and Security Layer (SASL) mechanism as specified in\n RFC 2831. It marks DIGEST-MD5 as OBSOLETE in the IANA Registry of\n SASL mechanisms and moves RFC 2831 to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/in","scope_keywords":["6331","authentication","authorization","hash","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null}],"search_text":"IETF RFC 6331 This memo describes problems with the DIGEST-MD5 Simple\n Authentication and Security Layer (SASL) mechanism as specified in\n RFC 2831. It marks DIGEST-MD5 as OBSOLETE in the IANA Registry of\n SASL mechanisms and moves RFC 2831 to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/in 6331 authentication authorization hash http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6854","type":"specification","body":"IETF","designation":"RFC 6854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6854.txt","https://www.rfc-editor.org/rfc/rfc6854.pdf"],"folder":"IETF/RFC-6854","files":{"txt":{"path":"standards/IETF/RFC-6854/RFC-6854.txt","sha256":"9f3dee8d37209eabd4dea53b4458599df96fe01f4ed144b948f6bc57fcc3603c"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Format (RFC 5322) allows \"group\" syntax in some\n email header fields, such as \"To:\" and \"CC:\", but not in \"From:\" or\n \"Sender:\". This document updates RFC 5322 to relax that restriction,\n allowing group syntax in those latter fields, as well as in\n \"Resent-From:\" and \"Resent-Sender:\", in certain situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6854.\n\nCopyr","scope_keywords":["6854","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null}],"search_text":"IETF RFC 6854 The Internet Message Format (RFC 5322) allows \"group\" syntax in some\n email header fields, such as \"To:\" and \"CC:\", but not in \"From:\" or\n \"Sender:\". This document updates RFC 5322 to relax that restriction,\n allowing group syntax in those latter fields, as well as in\n \"Resent-From:\" and \"Resent-Sender:\", in certain situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6854.\n\nCopyr 6854 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9051","type":"specification","body":"IETF","designation":"RFC 9051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9051.txt","https://www.rfc-editor.org/rfc/rfc9051.pdf"],"folder":"IETF/RFC-9051","files":{"pdf":{"path":"standards/IETF/RFC-9051/RFC-9051.pdf","sha256":"125d4729caef8cefd980e7d513ffcd171e8d272acc88d4a6ce47f3071ab1eae1"},"txt":{"path":"standards/IETF/RFC-9051/RFC-9051.txt","sha256":"acf52a50eb748ea21b5ffdcb31c761d3fbba6242d53d4f53c2555de039c5c3cf"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Access Protocol Version 4rev2 (IMAP4rev2) allows\n a client to access and manipulate electronic mail messages on a\n server. IMAP4rev2 permits manipulation of mailboxes (remote message\n folders) in a way that is functionally equivalent to local folders.\n IMAP4rev2 also provides the capability for an offline client to\n resynchronize with the server.\n\n IMAP4rev2 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; removing messages permanently;\n setting and clearing flags; parsing per RFCs 5322, 2045, and 2231;\n searching; and selective fetching of message attributes, texts, and\n portions thereof. Messages in IMAP4rev2 are accessed by the use of\n numbers. These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev2 does not specify a means of posting mail; this function is\n handled by a mail submission p","scope_keywords":["9051","attribute","attributes","http","https","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 9051 The Internet Message Access Protocol Version 4rev2 (IMAP4rev2) allows\n a client to access and manipulate electronic mail messages on a\n server. IMAP4rev2 permits manipulation of mailboxes (remote message\n folders) in a way that is functionally equivalent to local folders.\n IMAP4rev2 also provides the capability for an offline client to\n resynchronize with the server.\n\n IMAP4rev2 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; removing messages permanently;\n setting and clearing flags; parsing per RFCs 5322, 2045, and 2231;\n searching; and selective fetching of message attributes, texts, and\n portions thereof. Messages in IMAP4rev2 are accessed by the use of\n numbers. These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev2 does not specify a means of posting mail; this function is\n handled by a mail submission p 9051 attribute attributes http https license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 0826","type":"specification","body":"IETF","designation":"RFC 0826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0826.txt","https://www.rfc-editor.org/rfc/rfc0826.pdf"],"folder":"IETF/RFC-0826","files":{"txt":{"path":"standards/IETF/RFC-0826/RFC-0826.txt","sha256":"01bc62fe6a37e90f1246ac43e8e145f1322b4ed1474836145c3da93d2bd3c8a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David C. Plummer \nRequest For Comments: 826 (DCP@MIT-MC)\n November 1982\n\n An Ethernet Address Resolution Protocol\n -- or --\n Converting Network Protocol Addresses\n to 48.bit Ethernet Address\n for Transmission on\n Ethernet Hardware\n\n Abstract\n\nThe implementation of protocol P on a sending host S decides,\nthrough protocol P's routing mechanism, that it wants to transmit\nto a target host T located some place on a connected piece of\n10Mbit Ethernet cable. To actually transmit the Ethernet packet\na 48.bit Ethernet address must be generated. The addresses of\nhosts within protocol P are not always compatible with the\ncorresponding Ethernet address (being different lengths or\nvalues). Presented here is a protocol that allows dynamic\ndistribution of the information needed to build tables to\ntranslate an address A in protocol P's address space into a\n48.bit Ethernet address.\n","scope_keywords":["0826"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 0826 Network Working Group David C. Plummer \nRequest For Comments: 826 (DCP@MIT-MC)\n November 1982\n\n An Ethernet Address Resolution Protocol\n -- or --\n Converting Network Protocol Addresses\n to 48.bit Ethernet Address\n for Transmission on\n Ethernet Hardware\n\n Abstract\n\nThe implementation of protocol P on a sending host S decides,\nthrough protocol P's routing mechanism, that it wants to transmit\nto a target host T located some place on a connected piece of\n10Mbit Ethernet cable. To actually transmit the Ethernet packet\na 48.bit Ethernet address must be generated. The addresses of\nhosts within protocol P are not always compatible with the\ncorresponding Ethernet address (being different lengths or\nvalues). Presented here is a protocol that allows dynamic\ndistribution of the information needed to build tables to\ntranslate an address A in protocol P's address space into a\n48.bit Ethernet address.\n 0826 nested-reference unchanged"},{"id":"IETF RFC 6939","type":"specification","body":"IETF","designation":"RFC 6939","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6939.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6939.txt","https://www.rfc-editor.org/rfc/rfc6939.pdf"],"folder":"IETF/RFC-6939","files":{"txt":{"path":"standards/IETF/RFC-6939/RFC-6939.txt","sha256":"f8a831eb75b08fe01b68c6a91628e664f5e96a84c7b27d6f7117ddaab845022b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the format and mechanism that is to be used\n for encoding the client link-layer address in DHCPv6 Relay-Forward\n messages by defining a new DHCPv6 Client Link-Layer Address option.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6939.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["6939","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6939 This document specifies the format and mechanism that is to be used\n for encoding the client link-layer address in DHCPv6 Relay-Forward\n messages by defining a new DHCPv6 Client Link-Layer Address option.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6939.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  6939 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 7513","type":"specification","body":"IETF","designation":"RFC 7513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7513.txt","https://www.rfc-editor.org/rfc/rfc7513.pdf"],"folder":"IETF/RFC-7513","files":{"txt":{"path":"standards/IETF/RFC-7513/RFC-7513.txt","sha256":"10aa8c1c39c5793aa0710acb86d320270361ccd6070f8128d20ef64c8931879d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the procedure for creating a binding between\n a DHCPv4/DHCPv6-assigned IP address and a binding anchor on a Source\n Address Validation Improvement (SAVI) device. The bindings set up by\n this procedure are used to filter packets with forged source IP\n addresses. This mechanism complements BCP 38 (RFC 2827) ingress\n filtering, providing finer-grained source IP address validation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedba","scope_keywords":["7513","attribute","attributes","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7513 This document specifies the procedure for creating a binding between\n a DHCPv4/DHCPv6-assigned IP address and a binding anchor on a Source\n Address Validation Improvement (SAVI) device. The bindings set up by\n this procedure are used to filter packets with forged source IP\n addresses. This mechanism complements BCP 38 (RFC 2827) ingress\n filtering, providing finer-grained source IP address validation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedba 7513 attribute attributes http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 0850","type":"specification","body":"IETF","designation":"RFC 0850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0850.txt","https://www.rfc-editor.org/rfc/rfc0850.pdf"],"folder":"IETF/RFC-0850","files":{"txt":{"path":"standards/IETF/RFC-0850/RFC-0850.txt","sha256":"660c5d88cb473d80ebd768e43cb554386ed96ea4c427099c1c5efb551534bd19"}},"tags":["nested-reference","unchanged"],"summary":"RFC 850 June 1983\n\n Standard for Interchange of USENET Messages\n\n Mark R. Horton\n\n[ This memo is distributed as an RFC only to make this\ninformation easily accessible to researchers in the ARPA\ncommunity. It does not specify an Internet standard. ] \n\n1. Introduction\n\nThis document defines the standard format for interchange\nof Network News articles among USENET sites. It describes\nthe format for articles themselves, and gives partial\nstandards for transmission of news. The news transmission\nis not entirely standardized in order to give a good deal\nof flexibility to the individual hosts to choose\ntransmission hardware and software, whether to batch news,\nand so on.\n\nThere are five sections to this document. Section two\nsection defines the format. Section three defines the\nvalid control messages. Section four specifies some valid\ntransmission methods. Section five describes the overall\nnew","scope_keywords":["0850","algorithm","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null}],"search_text":"IETF RFC 0850 RFC 850 June 1983\n\n Standard for Interchange of USENET Messages\n\n Mark R. Horton\n\n[ This memo is distributed as an RFC only to make this\ninformation easily accessible to researchers in the ARPA\ncommunity. It does not specify an Internet standard. ] \n\n1. Introduction\n\nThis document defines the standard format for interchange\nof Network News articles among USENET sites. It describes\nthe format for articles themselves, and gives partial\nstandards for transmission of news. The news transmission\nis not entirely standardized in order to give a good deal\nof flexibility to the individual hosts to choose\ntransmission hardware and software, whether to batch news,\nand so on.\n\nThere are five sections to this document. Section two\nsection defines the format. Section three defines the\nvalid control messages. Section four specifies some valid\ntransmission methods. Section five describes the overall\nnew 0850 algorithm key path subject nested-reference unchanged"},{"id":"IETF RFC 0854","type":"specification","body":"IETF","designation":"RFC 0854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0854.txt","https://www.rfc-editor.org/rfc/rfc0854.pdf"],"folder":"IETF/RFC-0854","files":{"txt":{"path":"standards/IETF/RFC-0854/RFC-0854.txt","sha256":"f9cb6d4a7d7a67e5a1ac5ae3c2962b1183fb26119632a1617f3c8379820dfb10"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 854 J. Reynolds\n ISI\nObsoletes: NIC 18639 May 1983\n\n TELNET PROTOCOL SPECIFICATION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information.\n\n The TELNET","scope_keywords":["0854","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null}],"search_text":"IETF RFC 0854 Network Working Group J. Postel\nRequest for Comments: 854 J. Reynolds\n ISI\nObsoletes: NIC 18639 May 1983\n\n TELNET PROTOCOL SPECIFICATION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information.\n\n The TELNET 0854 presentation nested-reference unchanged"},{"id":"IETF RFC 5929","type":"specification","body":"IETF","designation":"RFC 5929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5929.txt","https://www.rfc-editor.org/rfc/rfc5929.pdf"],"folder":"IETF/RFC-5929","files":{"txt":{"path":"standards/IETF/RFC-5929/RFC-5929.txt","sha256":"d32604f5d5e2028f09a8e0cf1584b7bb27e75b2e060233cd5387446ac486eab7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines three channel binding types for Transport Layer\n Security (TLS), tls-unique, tls-server-end-point, and tls-unique-for-\n telnet, in accordance with RFC 5056 (On Channel Binding).\n\n Note that based on implementation experience, this document changes\n the original definition of 'tls-unique' channel binding type in the\n channel binding type IANA registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ","scope_keywords":["5929","algorithm","authentication","http","key","license","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 5929 This document defines three channel binding types for Transport Layer\n Security (TLS), tls-unique, tls-server-end-point, and tls-unique-for-\n telnet, in accordance with RFC 5056 (On Channel Binding).\n\n Note that based on implementation experience, this document changes\n the original definition of 'tls-unique' channel binding type in the\n channel binding type IANA registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n  5929 algorithm authentication http key license registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 0868","type":"specification","body":"IETF","designation":"RFC 0868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0868.txt","https://www.rfc-editor.org/rfc/rfc0868.pdf"],"folder":"IETF/RFC-0868","files":{"txt":{"path":"standards/IETF/RFC-0868/RFC-0868.txt","sha256":"42d96cd4e0743f947be4dfe69a507aa1ab23fa0a1846ae9be67164ebba6bc2f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel - ISI\nRequest for Comments: 868 K. Harrenstien - SRI\n May 1983\n\n Time Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Time Protocol are expected\nto adopt and implement this standard.\n\nThis protocol provides a site-independent, machine readable date and\ntime. The Time service sends back to the originating source the time in\nseconds since midnight on January first 1900.\n\nOne motivation arises from the fact that not all systems have a\ndate/time clock, and all are subject to occasional human or machine\nerror. The use of time-servers makes it possible to quickly confirm or\ncorrect a system's idea of the time, by making a brief poll of several\nindependent sites on the network.\n\nThis protocol may be used either above the Transmission Control Protocol\n(TCP) or above the User Datagram Pr","scope_keywords":["0868","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null}],"search_text":"IETF RFC 0868 Network Working Group J. Postel - ISI\nRequest for Comments: 868 K. Harrenstien - SRI\n May 1983\n\n Time Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Time Protocol are expected\nto adopt and implement this standard.\n\nThis protocol provides a site-independent, machine readable date and\ntime. The Time service sends back to the originating source the time in\nseconds since midnight on January first 1900.\n\nOne motivation arises from the fact that not all systems have a\ndate/time clock, and all are subject to occasional human or machine\nerror. The use of time-servers makes it possible to quickly confirm or\ncorrect a system's idea of the time, by making a brief poll of several\nindependent sites on the network.\n\nThis protocol may be used either above the Transmission Control Protocol\n(TCP) or above the User Datagram Pr 0868 subject nested-reference unchanged"},{"id":"IETF RFC 0872","type":"specification","body":"IETF","designation":"RFC 0872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0872.txt","https://www.rfc-editor.org/rfc/rfc0872.pdf"],"folder":"IETF/RFC-0872","files":{"txt":{"path":"standards/IETF/RFC-0872/RFC-0872.txt","sha256":"57b1625fada4a4561285e6b6c848cce422c29fd4724fc169f363e0736617dc51"}},"tags":["nested-reference","unchanged"],"summary":"RFC 872 September 1982\n M82-48\n\n TCP-ON-A-LAN\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n Abstract\n \n\n \n\n The sometimes-held position that the DoD Standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP)\n are inappropriate for use \"on\" a Local Area Network (LAN) is\n shown to be fallacious. The paper is a companion piece to\n M82-47, M82-49, M82-50, and M82-51.\n\n i\f\n \n \n \n \n \"TCP-ON-A-LAN\"\n\n M. A. Padlipsky\n\n Thesis\n\n It is the thesis of this paper that fearing \"TCP-on-a-LAN\"\n is a Woozle which needs slaying. To slay the \"TCP-on-a-LAN\"\n Woozle, we need to know three things: What's a Woozle? What's a\n LAN? What's a TCP?\n\n Woozles\n\n The first is rather straightforward [1]:\n\n One fine winter's day when Piglet was brushing away the\n snow in front of his house, he happened to look up, and\n there was Winnie-the-Pooh. Pooh was walking round and rou","scope_keywords":["0872"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null}],"search_text":"IETF RFC 0872 RFC 872 September 1982\n M82-48\n\n TCP-ON-A-LAN\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n Abstract\n \n\n \n\n The sometimes-held position that the DoD Standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP)\n are inappropriate for use \"on\" a Local Area Network (LAN) is\n shown to be fallacious. The paper is a companion piece to\n M82-47, M82-49, M82-50, and M82-51.\n\n i\f\n \n \n \n \n \"TCP-ON-A-LAN\"\n\n M. A. Padlipsky\n\n Thesis\n\n It is the thesis of this paper that fearing \"TCP-on-a-LAN\"\n is a Woozle which needs slaying. To slay the \"TCP-on-a-LAN\"\n Woozle, we need to know three things: What's a Woozle? What's a\n LAN? What's a TCP?\n\n Woozles\n\n The first is rather straightforward [1]:\n\n One fine winter's day when Piglet was brushing away the\n snow in front of his house, he happened to look up, and\n there was Winnie-the-Pooh. Pooh was walking round and rou 0872 nested-reference unchanged"},{"id":"IETF RFC 0879","type":"specification","body":"IETF","designation":"RFC 0879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0879.txt","https://www.rfc-editor.org/rfc/rfc0879.pdf"],"folder":"IETF/RFC-0879","files":{"txt":{"path":"standards/IETF/RFC-0879/RFC-0879.txt","sha256":"0e8aefe7e1ac9fac0893f21f3c310b07e4936b88e312498b8b01e5613c476c65"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 879 ISI\n November 1983\n\n The TCP Maximum Segment Size\n and Related Topics\n\nThis memo discusses the TCP Maximum Segment Size Option and related\ntopics. The purposes is to clarify some aspects of TCP and its\ninteraction with IP. This memo is a clarification to the TCP\nspecification, and contains information that may be considered as\n\"advice to implementers\".\n\n1. Introduction\n\n This memo discusses the TCP Maximum Segment Size and its relation to\n the IP Maximum Datagram Size. TCP is specified in reference [1]. IP\n is specified in references [2,3].\n\n This discussion is necessary because the current specification of\n this TCP option is ambiguous.\n\n Much of the difficulty with understanding these sizes and their\n relationship has been due to the variable size of the IP and TCP\n headers.\n\n There have been some assumptions made about using ot","scope_keywords":["0879"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null}],"search_text":"IETF RFC 0879 Network Working Group J. Postel\nRequest for Comments: 879 ISI\n November 1983\n\n The TCP Maximum Segment Size\n and Related Topics\n\nThis memo discusses the TCP Maximum Segment Size Option and related\ntopics. The purposes is to clarify some aspects of TCP and its\ninteraction with IP. This memo is a clarification to the TCP\nspecification, and contains information that may be considered as\n\"advice to implementers\".\n\n1. Introduction\n\n This memo discusses the TCP Maximum Segment Size and its relation to\n the IP Maximum Datagram Size. TCP is specified in reference [1]. IP\n is specified in references [2,3].\n\n This discussion is necessary because the current specification of\n this TCP option is ambiguous.\n\n Much of the difficulty with understanding these sizes and their\n relationship has been due to the variable size of the IP and TCP\n headers.\n\n There have been some assumptions made about using ot 0879 nested-reference unchanged"},{"id":"IETF RFC 7597","type":"specification","body":"IETF","designation":"RFC 7597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7597.txt","https://www.rfc-editor.org/rfc/rfc7597.pdf"],"folder":"IETF/RFC-7597","files":{"txt":{"path":"standards/IETF/RFC-7597/RFC-7597.txt","sha256":"e0081fd0b78bfc423ef03d1b7d981ce55ccda09f34853f27b37baf8ddf278cd1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for transporting IPv4 packets\n across an IPv6 network using IP encapsulation. It also describes a\n generic mechanism for mapping between IPv6 addresses and IPv4\n addresses as well as transport-layer ports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7597.\n\nTroan, et al. Standards Track [Page 1]\n\f\nRFC 7597 MAP-E July 2015\n\nCopyright Notice\n\n Copyrig","scope_keywords":["7597","algorithm","delivery","http","license","path","pid","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7597 This document describes a mechanism for transporting IPv4 packets\n across an IPv6 network using IP encapsulation. It also describes a\n generic mechanism for mapping between IPv6 addresses and IPv4\n addresses as well as transport-layer ports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7597.\n\nTroan, et al. Standards Track [Page 1]\n\f\nRFC 7597 MAP-E July 2015\n\nCopyright Notice\n\n Copyrig 7597 algorithm delivery http license path pid presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 0881","type":"specification","body":"IETF","designation":"RFC 0881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0881.txt","https://www.rfc-editor.org/rfc/rfc0881.pdf"],"folder":"IETF/RFC-0881","files":{"txt":{"path":"standards/IETF/RFC-0881/RFC-0881.txt","sha256":"80e3ae65b798c5d0469854a3755fbee67c0888efcf89b8e630b454538ab9feb2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 881 ISI\n November 1983\n\n The Domain Names Plan and Schedule\n\nThis RFC outlines a plan and schedule for the implementation of domain\nstyle names throughout the DDN/ARPA Internet community. The\nintroduction of domain style names will impact all hosts on the DDN/ARPA\nInternet.\n\nThe Plan\n\n Introduction\n\n Domain style names are being introduced in the Internet to allow a\n controlled delegation of the authority and responsibility for\n adding hosts to the system. This also allows a subdivision of the\n task of maintaining information about hosts.\n\n The subdivision will be based on administrative authority or\n organization boundaries (not necessarily network boundaries).\n Certain requirements will be placed on organizations wishing to be\n \"top level\" domains. Initially, all the hosts in the Internet\n will be in the domain \"ARPA\". As soon as is","scope_keywords":["0881","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null}],"search_text":"IETF RFC 0881 Network Working Group J. Postel\nRequest for Comments: 881 ISI\n November 1983\n\n The Domain Names Plan and Schedule\n\nThis RFC outlines a plan and schedule for the implementation of domain\nstyle names throughout the DDN/ARPA Internet community. The\nintroduction of domain style names will impact all hosts on the DDN/ARPA\nInternet.\n\nThe Plan\n\n Introduction\n\n Domain style names are being introduced in the Internet to allow a\n controlled delegation of the authority and responsibility for\n adding hosts to the system. This also allows a subdivision of the\n task of maintaining information about hosts.\n\n The subdivision will be based on administrative authority or\n organization boundaries (not necessarily network boundaries).\n Certain requirements will be placed on organizations wishing to be\n \"top level\" domains. Initially, all the hosts in the Internet\n will be in the domain \"ARPA\". As soon as is 0881 management nested-reference unchanged"},{"id":"IETF RFC 3245","type":"specification","body":"IETF","designation":"RFC 3245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3245.txt","https://www.rfc-editor.org/rfc/rfc3245.pdf"],"folder":"IETF/RFC-3245","files":{"txt":{"path":"standards/IETF/RFC-3245/RFC-3245.txt","sha256":"271cae85b4122d1fd033ed2b100bd3d219b68cdab44aafa0f7dca24a7dbfb247"}},"tags":["nested-reference","unchanged"],"summary":"RFC 2916 assigned responsibility for a number of administrative and\n operational details of Telephone Number Mapping (ENUM) to the IAB.\n It also anticipated that ITU would take responsibility for\n determining the legitimacy and appropriateness of applicants for\n delegation of \"country code\"-level subdomains of the top-level ENUM\n domain. Recently, three memos have been prepared for the ITU-T Study\n Group 2 (SG2) to explain the background of, and reasoning for, the\n relevant decisions. The IAB has also supplied a set of procedural\n instructions to the RIPE NCC for implementation of their part of the\n model. The content of the three memos is provided in this document\n for the information of the IETF community.","scope_keywords":["3245","algorithm","http","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null}],"search_text":"IETF RFC 3245 RFC 2916 assigned responsibility for a number of administrative and\n operational details of Telephone Number Mapping (ENUM) to the IAB.\n It also anticipated that ITU would take responsibility for\n determining the legitimacy and appropriateness of applicants for\n delegation of \"country code\"-level subdomains of the top-level ENUM\n domain. Recently, three memos have been prepared for the ITU-T Study\n Group 2 (SG2) to explain the background of, and reasoning for, the\n relevant decisions. The IAB has also supplied a set of procedural\n instructions to the RIPE NCC for implementation of their part of the\n model. The content of the three memos is provided in this document\n for the information of the IETF community. 3245 algorithm http identification nested-reference unchanged"},{"id":"IETF RFC 0882","type":"specification","body":"IETF","designation":"RFC 0882","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0882.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0882.txt","https://www.rfc-editor.org/rfc/rfc0882.pdf"],"folder":"IETF/RFC-0882","files":{"txt":{"path":"standards/IETF/RFC-0882/RFC-0882.txt","sha256":"70320c14a770d259bc0b218932b6c9a5aca3f209f8535c597724ed2fb270ac7a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 882 ISI\n November 1983\n\n DOMAIN NAMES - CONCEPTS and FACILITIES\n\n +-----------------------------------------------------+\n | |\n | This RFC introduces domain style names, their use |\n | for ARPA Internet mail and host address support, |\n | and the protocols and servers used to implement |\n | domain name facilities. |\n | |\n | This memo describes the conceptual framework of the |\n | domain system and some uses, but it omits many |\n | uses, fields, and implementation details. A |\n | complete specification of formats, timeouts, etc. |\n | is presented in RFC 883, \"Domain Names - |\n | Implementation and Specification\". That RFC |\n | assumes that the reader is familiar with the |\n | concepts discussed in this memo. |\n | |\n +-----------------------------------------------------+\n\nINTRODUCTION\n\n The need for domain names\n\n As applications ","scope_keywords":["0882","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 0882 Network Working Group P. Mockapetris\nRequest for Comments: 882 ISI\n November 1983\n\n DOMAIN NAMES - CONCEPTS and FACILITIES\n\n +-----------------------------------------------------+\n | |\n | This RFC introduces domain style names, their use |\n | for ARPA Internet mail and host address support, |\n | and the protocols and servers used to implement |\n | domain name facilities. |\n | |\n | This memo describes the conceptual framework of the |\n | domain system and some uses, but it omits many |\n | uses, fields, and implementation details. A |\n | complete specification of formats, timeouts, etc. |\n | is presented in RFC 883, \"Domain Names - |\n | Implementation and Specification\". That RFC |\n | assumes that the reader is familiar with the |\n | concepts discussed in this memo. |\n | |\n +-----------------------------------------------------+\n\nINTRODUCTION\n\n The need for domain names\n\n As applications  0882 registered nested-reference unchanged"},{"id":"IETF RFC 6950","type":"specification","body":"IETF","designation":"RFC 6950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6950.txt","https://www.rfc-editor.org/rfc/rfc6950.pdf"],"folder":"IETF/RFC-6950","files":{"txt":{"path":"standards/IETF/RFC-6950/RFC-6950.txt","sha256":"c02a7fdcf75a5343e6c54d3706a17f0a0bf98bc537fcad83a66056ac896d8ae5"}},"tags":["nested-reference","unchanged"],"summary":"A number of Internet applications rely on the Domain Name System\n (DNS) to support their operations. Many applications use the DNS to\n locate services for a domain; some, for example, transform\n identifiers other than domain names into formats that the DNS can\n process, and then fetch application data or service location data\n from the DNS. Proposals incorporating sophisticated application\n behavior using DNS as a substrate have raised questions about the\n role of the DNS as an application platform. This document explores\n the architectural consequences of using the DNS to implement certain\n application features, and it provides guidance to future application\n designers as to the limitations of the DNS as a substrate and the\n situations in which alternative designs should be considered.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publishe","scope_keywords":["6950","algorithm","encryption","http","key","keys","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null}],"search_text":"IETF RFC 6950 A number of Internet applications rely on the Domain Name System\n (DNS) to support their operations. Many applications use the DNS to\n locate services for a domain; some, for example, transform\n identifiers other than domain names into formats that the DNS can\n process, and then fetch application data or service location data\n from the DNS. Proposals incorporating sophisticated application\n behavior using DNS as a substrate have raised questions about the\n role of the DNS as an application platform. This document explores\n the architectural consequences of using the DNS to implement certain\n application features, and it provides guidance to future application\n designers as to the limitations of the DNS as a substrate and the\n situations in which alternative designs should be considered.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publishe 6950 algorithm encryption http key keys license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 0883","type":"specification","body":"IETF","designation":"RFC 0883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0883.txt","https://www.rfc-editor.org/rfc/rfc0883.pdf"],"folder":"IETF/RFC-0883","files":{"txt":{"path":"standards/IETF/RFC-0883/RFC-0883.txt","sha256":"9a69f193b479bf7ccc45a2953e625c057f2bbdb926bf44aab35cff4f2642db77"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 883 ISI\n November 1983\n\n DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION\n\n +-----------------------------------------------------+\n | |\n | This memo discusses the implementation of domain |\n | name servers and resolvers, specifies the format of |\n | transactions, and discusses the use of domain names |\n | in the context of existing mail systems and other |\n | network software. |\n | |\n | This memo assumes that the reader is familiar with |\n | RFC 882, \"Domain Names - Concepts and Facilities\" |\n | which discusses the basic principles of domain |\n | names and their use. |\n | |\n | The algorithms and internal data structures used in |\n | this memo are offered as suggestions rather than |\n | requirements; implementers are free to design their |\n | own structures so long as the same external |\n | behavior is achieved. |\n | |\n +---------","scope_keywords":["0883","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 0883 Network Working Group P. Mockapetris\nRequest for Comments: 883 ISI\n November 1983\n\n DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION\n\n +-----------------------------------------------------+\n | |\n | This memo discusses the implementation of domain |\n | name servers and resolvers, specifies the format of |\n | transactions, and discusses the use of domain names |\n | in the context of existing mail systems and other |\n | network software. |\n | |\n | This memo assumes that the reader is familiar with |\n | RFC 882, \"Domain Names - Concepts and Facilities\" |\n | which discusses the basic principles of domain |\n | names and their use. |\n | |\n | The algorithms and internal data structures used in |\n | this memo are offered as suggestions rather than |\n | requirements; implementers are free to design their |\n | own structures so long as the same external |\n | behavior is achieved. |\n | |\n +--------- 0883 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 0889","type":"specification","body":"IETF","designation":"RFC 0889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0889.txt","https://www.rfc-editor.org/rfc/rfc0889.pdf"],"folder":"IETF/RFC-0889","files":{"txt":{"path":"standards/IETF/RFC-0889/RFC-0889.txt","sha256":"1cf87afaf1c28b1bf3320576e92540334878335451f4ae92b8fdfb03f4611011"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 889 December 1983\n\n Internet Delay Experiments\n\nThis memo reports on some measurement experiments and suggests some possible\nimprovements to the TCP retransmission timeout calculation. This memo is\nboth a status report on the measurements and advice to implementers of TCP.\n\n1. Introduction\n\n This memorandum describes two series of experiments designed to explore\nthe transmission characteristics of the Internet system. One series of\nexperiments was designed to determine the network delays with respect to\npacket length, while the other was designed to assess the effectiveness of the\nTCP retransmission-timeout algorithm specified in the standards documents.\nBoth sets of experiments were conducted during the October - November 1983\ntime frame and used many hosts distributed throughout the Internet system.\n\n The objectives of these experi","scope_keywords":["0889","algorithm","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 0889 Network Working Group D.L. Mills\nRequest for Comments: 889 December 1983\n\n Internet Delay Experiments\n\nThis memo reports on some measurement experiments and suggests some possible\nimprovements to the TCP retransmission timeout calculation. This memo is\nboth a status report on the measurements and advice to implementers of TCP.\n\n1. Introduction\n\n This memorandum describes two series of experiments designed to explore\nthe transmission characteristics of the Internet system. One series of\nexperiments was designed to determine the network delays with respect to\npacket length, while the other was designed to assess the effectiveness of the\nTCP retransmission-timeout algorithm specified in the standards documents.\nBoth sets of experiments were conducted during the October - November 1983\ntime frame and used many hosts distributed throughout the Internet system.\n\n The objectives of these experi 0889 algorithm path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 5783","type":"specification","body":"IETF","designation":"RFC 5783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5783.txt","https://www.rfc-editor.org/rfc/rfc5783.pdf"],"folder":"IETF/RFC-5783","files":{"txt":{"path":"standards/IETF/RFC-5783/RFC-5783.txt","sha256":"1d364919630f5dea5ee7e6d021771ff12728dc5b0b8a73a2e466a7b4fe1ac2ad"}},"tags":["nested-reference","unchanged"],"summary":"This document is an informational snapshot taken by the IRTF's\n Internet Congestion Control Research Group (ICCRG) in October 2008.\n It provides a survey of congestion control topics described by\n documents in the RFC series. This does not modify or update the\n specifications or status of the RFC documents that are discussed. It\n may be used as a reference or starting point for the future work of\n the research group, especially in noting gaps or open issues in the\n current IETF standards.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Internet\n Congest","scope_keywords":["5783","algorithm","algorithms","http","license","management","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 5783 This document is an informational snapshot taken by the IRTF's\n Internet Congestion Control Research Group (ICCRG) in October 2008.\n It provides a survey of congestion control topics described by\n documents in the RFC series. This does not modify or update the\n specifications or status of the RFC documents that are discussed. It\n may be used as a reference or starting point for the future work of\n the research group, especially in noting gaps or open issues in the\n current IETF standards.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Internet\n Congest 5783 algorithm algorithms http license management path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 0894","type":"specification","body":"IETF","designation":"RFC 0894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0894.txt","https://www.rfc-editor.org/rfc/rfc0894.pdf"],"folder":"IETF/RFC-0894","files":{"txt":{"path":"standards/IETF/RFC-0894/RFC-0894.txt","sha256":"be88b9301e53f986aca3a0e55e488d1d79bae3f88fe3f257640397bc089e7035"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Charles Hornig\nRequest for Comments: 894 Symbolics Cambridge Research Center\n April 1984\n\n A Standard for the Transmission of IP Datagrams over Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Ethernet [2]. This RFC specifies a\n standard protocol for the ARPA-Internet community.\n\nIntroduction\n\n This memo applies to the Ethernet (10-megabit/second, 48-bit\n addresses). The procedure for transmission of IP datagrams on the\n Experimental Ethernet (3-megabit/second, 8-bit addresses) is\n described in [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Ethernet frames. The type\n field of the Ethernet frame must contain the value hexadecimal 0800.\n The data field contains the IP header followed immediately by the IP\n data.\n\n The minimum length of the data field of a packet se","scope_keywords":["0894"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 0894 Network Working Group Charles Hornig\nRequest for Comments: 894 Symbolics Cambridge Research Center\n April 1984\n\n A Standard for the Transmission of IP Datagrams over Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Ethernet [2]. This RFC specifies a\n standard protocol for the ARPA-Internet community.\n\nIntroduction\n\n This memo applies to the Ethernet (10-megabit/second, 48-bit\n addresses). The procedure for transmission of IP datagrams on the\n Experimental Ethernet (3-megabit/second, 8-bit addresses) is\n described in [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Ethernet frames. The type\n field of the Ethernet frame must contain the value hexadecimal 0800.\n The data field contains the IP header followed immediately by the IP\n data.\n\n The minimum length of the data field of a packet se 0894 nested-reference unchanged"},{"id":"IETF RFC 4253","type":"specification","body":"IETF","designation":"RFC 4253","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4253.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4253.txt","https://www.rfc-editor.org/rfc/rfc4253.pdf"],"folder":"IETF/RFC-4253","files":{"txt":{"path":"standards/IETF/RFC-4253/RFC-4253.txt","sha256":"b471173305154f6c66facffcf7a4a25fc5c32765cb30542120be6c20a88f1ed3"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Shell (SSH) is a protocol for secure remote login and\n other secure network services over an insecure network.\n\n This document describes the SSH transport layer protocol, which\n typically runs on top of TCP/IP. The protocol can be used as a basis\n for a number of secure network services. It provides strong\n encryption, server authentication, and integrity protection. It may\n also provide compression.\n\n Key exchange method, public key algorithm, symmetric encryption\n algorithm, message authentication algorithm, and hash algorithm are\n all negotiated.\n\n This document also describes the Diffie-Hellman key exchange method\n and the minimal set of algorithms that are needed to implement the\n SSH transport layer protocol.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4253 SSH Transport Layer Protocol January 2006","scope_keywords":["4253","algorithm","algorithms","authentication","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4345","folder":"IETF/RFC-4345","source":"IETF/RFC-4345/RFC-4345.txt","version":null},{"body":"IETF","designation":"RFC 4419","folder":"IETF/RFC-4419","source":"IETF/RFC-4419/RFC-4419.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 4253 The Secure Shell (SSH) is a protocol for secure remote login and\n other secure network services over an insecure network.\n\n This document describes the SSH transport layer protocol, which\n typically runs on top of TCP/IP. The protocol can be used as a basis\n for a number of secure network services. It provides strong\n encryption, server authentication, and integrity protection. It may\n also provide compression.\n\n Key exchange method, public key algorithm, symmetric encryption\n algorithm, message authentication algorithm, and hash algorithm are\n all negotiated.\n\n This document also describes the Diffie-Hellman key exchange method\n and the minimal set of algorithms that are needed to implement the\n SSH transport layer protocol.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4253 SSH Transport Layer Protocol January 2006 4253 algorithm algorithms authentication encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 0896","type":"specification","body":"IETF","designation":"RFC 0896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0896.txt","https://www.rfc-editor.org/rfc/rfc0896.pdf"],"folder":"IETF/RFC-0896","files":{"txt":{"path":"standards/IETF/RFC-0896/RFC-0896.txt","sha256":"9f50ffb6d2557be2727bb0f4ca9b5dec9777b3617c66e47822d2ba28df2dfda3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Nagle\nRequest For Comments: 896 6 January 1984\n Ford Aerospace and Communications Corporation\n\n Congestion Control in IP/TCP Internetworks\n\nThis memo discusses some aspects of congestion control in IP/TCP\nInternetworks. It is intended to stimulate thought and further\ndiscussion of this topic. While some specific suggestions are\nmade for improved congestion control implementation, this memo\ndoes not specify any standards.\n\n Introduction\n\nCongestion control is a recognized problem in complex networks.\nWe have discovered that the Department of Defense's Internet Pro-\ntocol (IP) , a pure datagram protocol, and Transmission Control\nProtocol (TCP), a transport layer protocol, when used together,\nare subject to unusual congestion problems caused by interactions\nbetween the transport and datagram layers. In particular, IP\ngateways are vulnerable to a phenomenon we call","scope_keywords":["0896","algorithm","algorithms","key","path","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null}],"search_text":"IETF RFC 0896 Network Working Group John Nagle\nRequest For Comments: 896 6 January 1984\n Ford Aerospace and Communications Corporation\n\n Congestion Control in IP/TCP Internetworks\n\nThis memo discusses some aspects of congestion control in IP/TCP\nInternetworks. It is intended to stimulate thought and further\ndiscussion of this topic. While some specific suggestions are\nmade for improved congestion control implementation, this memo\ndoes not specify any standards.\n\n Introduction\n\nCongestion control is a recognized problem in complex networks.\nWe have discovered that the Department of Defense's Internet Pro-\ntocol (IP) , a pure datagram protocol, and Transmission Control\nProtocol (TCP), a transport layer protocol, when used together,\nare subject to unusual congestion problems caused by interactions\nbetween the transport and datagram layers. In particular, IP\ngateways are vulnerable to a phenomenon we call 0896 algorithm algorithms key path pid subject nested-reference unchanged"},{"id":"IETF RFC 7560","type":"specification","body":"IETF","designation":"RFC 7560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7560.txt","https://www.rfc-editor.org/rfc/rfc7560.pdf"],"folder":"IETF/RFC-7560","files":{"txt":{"path":"standards/IETF/RFC-7560/RFC-7560.txt","sha256":"20d0f1900816f3c4c6dbb23a4d838245de21da47f0b7d3e7b2e6bae05dceb4ae"}},"tags":["nested-reference","unchanged"],"summary":"Explicit Congestion Notification (ECN) is a mechanism where network\n nodes can mark IP packets, instead of dropping them, to indicate\n congestion to the endpoints. An ECN-capable receiver will feed this\n information back to the sender. ECN is specified for TCP in such a\n way that it can only feed back one congestion signal per Round-Trip\n Time (RTT). In contrast, ECN for other transport protocols, such as\n RTP/UDP and SCTP, is specified with more accurate ECN feedback.\n Recent new TCP mechanisms (like Congestion Exposure (ConEx) or Data\n Center TCP (DCTCP)) need more accurate ECN feedback in the case where\n more than one marking is received in one RTT. This document\n specifies requirements for an update to the TCP protocol to provide\n more accurate ECN feedback.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purpo","scope_keywords":["7560","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 7560 Explicit Congestion Notification (ECN) is a mechanism where network\n nodes can mark IP packets, instead of dropping them, to indicate\n congestion to the endpoints. An ECN-capable receiver will feed this\n information back to the sender. ECN is specified for TCP in such a\n way that it can only feed back one congestion signal per Round-Trip\n Time (RTT). In contrast, ECN for other transport protocols, such as\n RTP/UDP and SCTP, is specified with more accurate ECN feedback.\n Recent new TCP mechanisms (like Congestion Exposure (ConEx) or Data\n Center TCP (DCTCP)) need more accurate ECN feedback in the case where\n more than one marking is received in one RTT. This document\n specifies requirements for an update to the TCP protocol to provide\n more accurate ECN feedback.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purpo 7560 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8289","type":"specification","body":"IETF","designation":"RFC 8289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8289.txt","https://www.rfc-editor.org/rfc/rfc8289.pdf"],"folder":"IETF/RFC-8289","files":{"txt":{"path":"standards/IETF/RFC-8289/RFC-8289.txt","sha256":"22ed146dd28dc113130747014397121447fde30640b9d16542f51755351dddac"}},"tags":["nested-reference","unchanged"],"summary":"This document describes CoDel (Controlled Delay) -- a general\n framework that controls bufferbloat-generated excess delay in modern\n networking environments. CoDel consists of an estimator, a setpoint,\n and a control loop. It requires no configuration in normal Internet\n deployments.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n I","scope_keywords":["8289","http","https","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null}],"search_text":"IETF RFC 8289 This document describes CoDel (Controlled Delay) -- a general\n framework that controls bufferbloat-generated excess delay in modern\n networking environments. CoDel consists of an estimator, a setpoint,\n and a control loop. It requires no configuration in normal Internet\n deployments.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n I 8289 http https license management subject trust nested-reference unchanged"},{"id":"IETF RFC 0903","type":"specification","body":"IETF","designation":"RFC 0903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0903.txt","https://www.rfc-editor.org/rfc/rfc0903.pdf"],"folder":"IETF/RFC-0903","files":{"txt":{"path":"standards/IETF/RFC-0903/RFC-0903.txt","sha256":"74e97a29c12979734d4aec3df5b8d159b0987707338be1e299d90ecc3645b6fa"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Finlayson, Mann, Mogul, Theimer\nRequest for Comments: 903 Stanford University\n June 1984\n\n A Reverse Address Resolution Protocol\n\n Ross Finlayson, Timothy Mann, Jeffrey Mogul, Marvin Theimer\n Computer Science Department\n Stanford University\n June 1984\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically find their\n protocol address (e.g., their Internet Address), when they know only\n their hardware address (e.g., their attached physical network\n address).\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nI. Introduction\n\n Network hosts such as diskless workstations frequently do not know\n their protocol addresses when booted; they often know only their\n hardware interface addresses. To communicate using higher-level\n protocols like IP, they must discover ","scope_keywords":["0903"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 0903 Network Working Group Finlayson, Mann, Mogul, Theimer\nRequest for Comments: 903 Stanford University\n June 1984\n\n A Reverse Address Resolution Protocol\n\n Ross Finlayson, Timothy Mann, Jeffrey Mogul, Marvin Theimer\n Computer Science Department\n Stanford University\n June 1984\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically find their\n protocol address (e.g., their Internet Address), when they know only\n their hardware address (e.g., their attached physical network\n address).\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nI. Introduction\n\n Network hosts such as diskless workstations frequently do not know\n their protocol addresses when booted; they often know only their\n hardware interface addresses. To communicate using higher-level\n protocols like IP, they must discover  0903 nested-reference unchanged"},{"id":"IETF RFC 5735","type":"specification","body":"IETF","designation":"RFC 5735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5735.txt","https://www.rfc-editor.org/rfc/rfc5735.pdf"],"folder":"IETF/RFC-5735","files":{"txt":{"path":"standards/IETF/RFC-5735/RFC-5735.txt","sha256":"db63b2eaec515690a50ce4d8079c4ab8ba495101ee11dae7eed8d95b7aef990d"}},"tags":["nested-reference","unchanged"],"summary":"This document obsoletes RFC 3330. It describes the global and other\n specialized IPv4 address blocks that have been assigned by the\n Internet Assigned Numbers Authority (IANA). It does not address IPv4\n address space assigned to operators and users through the Regional\n Internet Registries, nor does it address IPv4 address space assigned\n directly by IANA prior to the creation of the Regional Internet\n Registries. It also does not address allocations or assignments of\n IPv6 addresses or autonomous system numbers.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2","scope_keywords":["5735","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5736","folder":"IETF/RFC-5736","source":"IETF/RFC-5736/RFC-5736.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5735 This document obsoletes RFC 3330. It describes the global and other\n specialized IPv4 address blocks that have been assigned by the\n Internet Assigned Numbers Authority (IANA). It does not address IPv4\n address space assigned to operators and users through the Regional\n Internet Registries, nor does it address IPv4 address space assigned\n directly by IANA prior to the creation of the Regional Internet\n Registries. It also does not address allocations or assignments of\n IPv6 addresses or autonomous system numbers.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 5735 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6890","type":"specification","body":"IETF","designation":"RFC 6890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6890.txt","https://www.rfc-editor.org/rfc/rfc6890.pdf"],"folder":"IETF/RFC-6890","files":{"txt":{"path":"standards/IETF/RFC-6890/RFC-6890.txt","sha256":"ce738958287c710cb52016741114cbd4ba9c0b01a8db43adac7e0b7daa28dd3c"}},"tags":["nested-reference","unchanged"],"summary":"This memo reiterates the assignment of an IPv4 address block\n (192.0.0.0/24) to IANA. It also instructs IANA to restructure its\n IPv4 and IPv6 Special-Purpose Address Registries. Upon\n restructuring, the aforementioned registries will record all special-\n purpose address blocks, maintaining a common set of information\n regarding each address block.\n\n This memo obsoletes RFCs 4773, 5156, 5735, and 5736.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o","scope_keywords":["6890","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 6890 This memo reiterates the assignment of an IPv4 address block\n (192.0.0.0/24) to IANA. It also instructs IANA to restructure its\n IPv4 and IPv6 Special-Purpose Address Registries. Upon\n restructuring, the aforementioned registries will record all special-\n purpose address blocks, maintaining a common set of information\n regarding each address block.\n\n This memo obsoletes RFCs 4773, 5156, 5735, and 5736.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o 6890 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8190","type":"specification","body":"IETF","designation":"RFC 8190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8190.txt","https://www.rfc-editor.org/rfc/rfc8190.pdf"],"folder":"IETF/RFC-8190","files":{"txt":{"path":"standards/IETF/RFC-8190/RFC-8190.txt","sha256":"8d42ca9621d336b9c425c26109d0475385af6e9018ec203d1595a716dece9581"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates the IANA IPv4 and IPv6 Special-Purpose Address\n Registries to address issues raised by the definition of a \"global\"\n prefix. It also corrects several errors in registry entries to\n ensure the integrity of the IANA Special-Purpose Address Registries.\n\n This memo updates RFC 6890.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8190.\n\nBonica, et al. Best Current Practice [Page","scope_keywords":["8190","http","https","license","pki","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 8190 This memo updates the IANA IPv4 and IPv6 Special-Purpose Address\n Registries to address issues raised by the definition of a \"global\"\n prefix. It also corrects several errors in registry entries to\n ensure the integrity of the IANA Special-Purpose Address Registries.\n\n This memo updates RFC 6890.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8190.\n\nBonica, et al. Best Current Practice [Page 8190 http https license pki subject trust nested-reference unchanged"},{"id":"IETF RFC 0925","type":"specification","body":"IETF","designation":"RFC 0925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0925.txt","https://www.rfc-editor.org/rfc/rfc0925.pdf"],"folder":"IETF/RFC-0925","files":{"txt":{"path":"standards/IETF/RFC-0925/RFC-0925.txt","sha256":"59ecfa95cb97c3f3a13cd75e92cfc0498ea165b8cafcf1f4491766b5793f4857"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 925 ISI\n October 1984\n\n Multi-LAN Address Resolution\n\nSTATUS OF THIS MEMO\n\n This memo is prompted by RFC-917 by Jeffery Mogul on \"Internet\n Subnets\". In that memo, Mogul makes a case for the use of \"explicit\n subnets\" in a multi-LAN environment. In this memo, I attempt to make\n a case for \"transparent subnets\". This RFC suggests a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The problem of treating a set of local area networks (LANs) as one\n Internet network has generated some interest and concern. It is\n inappropriate to give each LAN within an site a distinct Internet\n network number. It is desirable to hide the details of the\n interconnections between the LANs within an site from people,\n gateways, and hosts ou","scope_keywords":["0925"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 0925 Network Working Group J. Postel\nRequest for Comments: 925 ISI\n October 1984\n\n Multi-LAN Address Resolution\n\nSTATUS OF THIS MEMO\n\n This memo is prompted by RFC-917 by Jeffery Mogul on \"Internet\n Subnets\". In that memo, Mogul makes a case for the use of \"explicit\n subnets\" in a multi-LAN environment. In this memo, I attempt to make\n a case for \"transparent subnets\". This RFC suggests a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The problem of treating a set of local area networks (LANs) as one\n Internet network has generated some interest and concern. It is\n inappropriate to give each LAN within an site a distinct Internet\n network number. It is desirable to hide the details of the\n interconnections between the LANs within an site from people,\n gateways, and hosts ou 0925 nested-reference unchanged"},{"id":"IETF RFC 5844","type":"specification","body":"IETF","designation":"RFC 5844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5844.txt","https://www.rfc-editor.org/rfc/rfc5844.pdf"],"folder":"IETF/RFC-5844","files":{"txt":{"path":"standards/IETF/RFC-5844/RFC-5844.txt","sha256":"d99071dfec942916024ebc50fc44f1ebc06a375b949f5e23381b7c5c3aea7077"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies extensions to the Proxy Mobile IPv6 protocol\n for adding IPv4 protocol support. The scope of IPv4 protocol support\n is two-fold: 1) enable IPv4 home address mobility support to the\n mobile node, and 2) allow the mobility entities in the Proxy Mobile\n IPv6 domain to exchange signaling messages over an IPv4 transport\n network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org","scope_keywords":["5844","http","license","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null}],"search_text":"IETF RFC 5844 This document specifies extensions to the Proxy Mobile IPv6 protocol\n for adding IPv4 protocol support. The scope of IPv4 protocol support\n is two-fold: 1) enable IPv4 home address mobility support to the\n mobile node, and 2) allow the mobility entities in the Proxy Mobile\n IPv6 domain to exchange signaling messages over an IPv4 transport\n network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org 5844 http license policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 0927","type":"specification","body":"IETF","designation":"RFC 0927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0927.txt","https://www.rfc-editor.org/rfc/rfc0927.pdf"],"folder":"IETF/RFC-0927","files":{"txt":{"path":"standards/IETF/RFC-0927/RFC-0927.txt","sha256":"8d96e37740c10c1955f71f3614e2c0cf3a79302f5f833fb766cafb0f2a0a8e54"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Brian A. Anderson\nRequest for Comments: 927 BBN\n December 1984\n\n TACACS User Identification Telnet Option\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The following is the description of a TELNET option designed to\n facilitate double login avoidance. It is intended primarily for TAC\n connections to target hosts on behalf of TAC users, but it can be\n used between any two consenting hosts. For example, all hosts at one\n site (e.g., BBN) can use this option to avoid double login when\n TELNETing to one another.\n\n1. Command name and code\n\n TUID 26\n\n2. Command Meanings\n\n IAC WILL TUID\n\n The sender (the TELNET user) proposes to authenticate the user and\n send the identifing UUID; or, the sender (the TELNET user","scope_keywords":["0927","authentication","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null}],"search_text":"IETF RFC 0927 Network Working Group Brian A. Anderson\nRequest for Comments: 927 BBN\n December 1984\n\n TACACS User Identification Telnet Option\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The following is the description of a TELNET option designed to\n facilitate double login avoidance. It is intended primarily for TAC\n connections to target hosts on behalf of TAC users, but it can be\n used between any two consenting hosts. For example, all hosts at one\n site (e.g., BBN) can use this option to avoid double login when\n TELNETing to one another.\n\n1. Command name and code\n\n TUID 26\n\n2. Command Meanings\n\n IAC WILL TUID\n\n The sender (the TELNET user) proposes to authenticate the user and\n send the identifing UUID; or, the sender (the TELNET user 0927 authentication identification nested-reference unchanged"},{"id":"IETF RFC 0950","type":"specification","body":"IETF","designation":"RFC 0950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0950.txt","https://www.rfc-editor.org/rfc/rfc0950.pdf"],"folder":"IETF/RFC-0950","files":{"txt":{"path":"standards/IETF/RFC-0950/RFC-0950.txt","sha256":"59294d6dbdfcb02589d00ba66386261f8c6e714d8b3f3d2e37b39424f5c9a795"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Mogul (Stanford)\nRequest for Comments: 950 J. Postel (ISI)\n August 1985\n\n Internet Standard Subnetting Procedure\n\nStatus Of This Memo\n\n This RFC specifies a protocol for the ARPA-Internet community. If\n subnetting is implemented it is strongly recommended that these\n procedures be followed. Distribution of this memo is unlimited.\n\nOverview\n\n This memo discusses the utility of \"subnets\" of Internet networks,\n which are logically visible sub-sections of a single Internet\n network. For administrative or technical reasons, many organizations\n have chosen to divide one Internet network into several subnets,\n instead of acquiring a set of Internet network numbers. This memo\n specifies procedures for the use of subnets. These procedures are\n for hosts (e.g., workstations). The procedures used in and between\n subnet gateways are not fully described. Important motivation ","scope_keywords":["0950","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null}],"search_text":"IETF RFC 0950 Network Working Group J. Mogul (Stanford)\nRequest for Comments: 950 J. Postel (ISI)\n August 1985\n\n Internet Standard Subnetting Procedure\n\nStatus Of This Memo\n\n This RFC specifies a protocol for the ARPA-Internet community. If\n subnetting is implemented it is strongly recommended that these\n procedures be followed. Distribution of this memo is unlimited.\n\nOverview\n\n This memo discusses the utility of \"subnets\" of Internet networks,\n which are logically visible sub-sections of a single Internet\n network. For administrative or technical reasons, many organizations\n have chosen to divide one Internet network into several subnets,\n instead of acquiring a set of Internet network numbers. This memo\n specifies procedures for the use of subnets. These procedures are\n for hosts (e.g., workstations). The procedures used in and between\n subnet gateways are not fully described. Important motivation  0950 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 5942","type":"specification","body":"IETF","designation":"RFC 5942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5942.txt","https://www.rfc-editor.org/rfc/rfc5942.pdf"],"folder":"IETF/RFC-5942","files":{"txt":{"path":"standards/IETF/RFC-5942/RFC-5942.txt","sha256":"7d2de09f5288c263caf05fac1b8b8c9fbdaf0f15744cb25b88bcd210c772aa36"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 specifies a model of a subnet that is different than the IPv4\n subnet model. The subtlety of the differences has resulted in\n incorrect implementations that do not interoperate. This document\n spells out the most important difference: that an IPv6 address isn't\n automatically associated with an IPv6 on-link prefix. This document\n also updates (partially due to security concerns caused by incorrect\n implementations) a part of the definition of \"on-link\" from RFC 4861.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the","scope_keywords":["5942","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 5942 IPv6 specifies a model of a subnet that is different than the IPv4\n subnet model. The subtlety of the differences has resulted in\n incorrect implementations that do not interoperate. This document\n spells out the most important difference: that an IPv6 address isn't\n automatically associated with an IPv6 on-link prefix. This document\n also updates (partially due to security concerns caused by incorrect\n implementations) a part of the definition of \"on-link\" from RFC 4861.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the 5942 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 0951","type":"specification","body":"IETF","designation":"RFC 0951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0951.txt","https://www.rfc-editor.org/rfc/rfc0951.pdf"],"folder":"IETF/RFC-0951","files":{"txt":{"path":"standards/IETF/RFC-0951/RFC-0951.txt","sha256":"098809562693d95c502d59451fa8cc6a4a2f263448fad077f0af677088cb0c52"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bill Croft (Stanford University)\nRequest for Comments: 951 John Gilmore (Sun Microsystems)\n September 1985\n\n BOOTSTRAP PROTOCOL (BOOTP)\n\n1. Status of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n2. Overview\n\n This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows\n a diskless client machine to discover its own IP address, the address\n of a server host, and the name of a file to be loaded into memory and\n executed. The bootstrap operation can be thought of as consisting of\n TWO PHASES. This RFC describes the first phase, which could be\n labeled 'address determination and bootfile selection'. After this\n address and filename information is obtained, control passes to the\n second phase of the bootstrap where a file tran","scope_keywords":["0951","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null}],"search_text":"IETF RFC 0951 Network Working Group Bill Croft (Stanford University)\nRequest for Comments: 951 John Gilmore (Sun Microsystems)\n September 1985\n\n BOOTSTRAP PROTOCOL (BOOTP)\n\n1. Status of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n2. Overview\n\n This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows\n a diskless client machine to discover its own IP address, the address\n of a server host, and the name of a file to be loaded into memory and\n executed. The bootstrap operation can be thought of as consisting of\n TWO PHASES. This RFC describes the first phase, which could be\n labeled 'address determination and bootfile selection'. After this\n address and filename information is obtained, control passes to the\n second phase of the bootstrap where a file tran 0951 path qualified nested-reference unchanged"},{"id":"IETF RFC 7724","type":"specification","body":"IETF","designation":"RFC 7724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7724.txt","https://www.rfc-editor.org/rfc/rfc7724.pdf"],"folder":"IETF/RFC-7724","files":{"txt":{"path":"standards/IETF/RFC-7724/RFC-7724.txt","sha256":"7841191ee7ec17d374681e14b3e91d1fb7fd416931434e1cd1a2f493eb5addc9"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been\n extended with a Leasequery capability that allows a requestor to\n request information about DHCPv4 bindings (RFC 4388). That mechanism\n is limited to queries for individual bindings. In some situations,\n individual binding queries may not be efficient, or even possible.\n In addition, continuous update of an external requestor with\n Leasequery data is sometimes desired. This document expands on the\n DHCPv4 Leasequery protocol, and allows for active transfer of near\n real-time DHCPv4 binding information data via TCP. This document\n updates RFC 6926, \"DHCPv4 Bulk Leasequery\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo","scope_keywords":["7724","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null}],"search_text":"IETF RFC 7724 The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been\n extended with a Leasequery capability that allows a requestor to\n request information about DHCPv4 bindings (RFC 4388). That mechanism\n is limited to queries for individual bindings. In some situations,\n individual binding queries may not be efficient, or even possible.\n In addition, continuous update of an external requestor with\n Leasequery data is sometimes desired. This document expands on the\n DHCPv4 Leasequery protocol, and allows for active transfer of near\n real-time DHCPv4 binding information data via TCP. This document\n updates RFC 6926, \"DHCPv4 Bulk Leasequery\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo 7724 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 0952","type":"specification","body":"IETF","designation":"RFC 0952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0952.txt","https://www.rfc-editor.org/rfc/rfc0952.pdf"],"folder":"IETF/RFC-0952","files":{"txt":{"path":"standards/IETF/RFC-0952/RFC-0952.txt","sha256":"fbef98b87d31526430b390ac37f9c6935e84233cdd3a30be8f5a007e1d9be593"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 952 M. Stahl (SRI)\n E. Feinler (SRI)\nObsoletes: RFC 810, 608 October 1985\n\n DOD INTERNET HOST TABLE SPECIFICATION\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the format of the Internet\n Host Table. This edition of the specification includes minor\n revisions to RFC-810 which brings it up to date. Distribution of this\n memo is unlimited.\n\nINTRODUCTION\n\n The DoD Host Table is utilized by the DoD Hostname Server maintained\n by the DDN Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) [See RFC-953].\n\nLOCATION OF THE STANDARD DOD ONLINE HOST TABLE\n\n A machine-translatable ASCII text version of the DoD Host Table is\n online in the file NETINFO:HOSTS.TXT on the SRI-NIC host. It can be\n obtained via FTP from your local host by connecting to host\n SRI-NIC.ARPA (26.0.0.73 or 10","scope_keywords":["0952","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 0952 Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 952 M. Stahl (SRI)\n E. Feinler (SRI)\nObsoletes: RFC 810, 608 October 1985\n\n DOD INTERNET HOST TABLE SPECIFICATION\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the format of the Internet\n Host Table. This edition of the specification includes minor\n revisions to RFC-810 which brings it up to date. Distribution of this\n memo is unlimited.\n\nINTRODUCTION\n\n The DoD Host Table is utilized by the DoD Hostname Server maintained\n by the DDN Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) [See RFC-953].\n\nLOCATION OF THE STANDARD DOD ONLINE HOST TABLE\n\n A machine-translatable ASCII text version of the DoD Host Table is\n online in the file NETINFO:HOSTS.TXT on the SRI-NIC host. It can be\n obtained via FTP from your local host by connecting to host\n SRI-NIC.ARPA (26.0.0.73 or 10 0952 key registered nested-reference unchanged"},{"id":"IETF RFC 3986","type":"specification","body":"IETF","designation":"RFC 3986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3986.txt","https://www.rfc-editor.org/rfc/rfc3986.pdf"],"folder":"IETF/RFC-3986","files":{"txt":{"path":"standards/IETF/RFC-3986/RFC-3986.txt","sha256":"3102dae4b68cebe40337730312fcb612297b8928547267e8b3d1ee6002b2d683"}},"tags":["nested-reference","unchanged"],"summary":"A Uniform Resource Identifier (URI) is a compact sequence of\n characters that identifies an abstract or physical resource. This\n specification defines the generic URI syntax and a process for\n resolving URI references that might be in relative form, along with\n guidelines and security considerations for the use of URIs on the\n Internet. The URI syntax defines a grammar that is a superset of all\n valid URIs, allowing an implementation to parse the common components\n of a URI reference without knowing the scheme-specific requirements\n of every possible identifier. This specification does not define a\n generative grammar for URIs; that task is performed by the individual\n specifications of each URI scheme.\n\nBerners-Lee, et al. Standards Track [Page 1]\n\f\nRFC 3986 URI Generic Syntax January 2005","scope_keywords":["3986","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.2.1","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4267","folder":"IETF/RFC-4267","source":"IETF/RFC-4267/RFC-4267.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4437","folder":"IETF/RFC-4437","source":"IETF/RFC-4437/RFC-4437.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4475","folder":"IETF/RFC-4475","source":"IETF/RFC-4475/RFC-4475.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4838","folder":"IETF/RFC-4838","source":"IETF/RFC-4838/RFC-4838.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4946","folder":"IETF/RFC-4946","source":"IETF/RFC-4946/RFC-4946.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5013","folder":"IETF/RFC-5013","source":"IETF/RFC-5013/RFC-5013.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5781","folder":"IETF/RFC-5781","source":"IETF/RFC-5781/RFC-5781.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6694","folder":"IETF/RFC-6694","source":"IETF/RFC-6694/RFC-6694.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6983","folder":"IETF/RFC-6983","source":"IETF/RFC-6983/RFC-6983.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8081","folder":"IETF/RFC-8081","source":"IETF/RFC-8081/RFC-8081.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 3986 A Uniform Resource Identifier (URI) is a compact sequence of\n characters that identifies an abstract or physical resource. This\n specification defines the generic URI syntax and a process for\n resolving URI references that might be in relative form, along with\n guidelines and security considerations for the use of URIs on the\n Internet. The URI syntax defines a grammar that is a superset of all\n valid URIs, allowing an implementation to parse the common components\n of a URI reference without knowing the scheme-specific requirements\n of every possible identifier. This specification does not define a\n generative grammar for URIs; that task is performed by the individual\n specifications of each URI scheme.\n\nBerners-Lee, et al. Standards Track [Page 1]\n\f\nRFC 3986 URI Generic Syntax January 2005 3986 identification path nested-reference unchanged"},{"id":"IETF RFC 4931","type":"specification","body":"IETF","designation":"RFC 4931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4931.txt","https://www.rfc-editor.org/rfc/rfc4931.pdf"],"folder":"IETF/RFC-4931","files":{"txt":{"path":"standards/IETF/RFC-4931/RFC-4931.txt","sha256":"be41eaa46b7114be43da2ddb28362ce6d1aa74e6a6829bfc2111d73b37c2310b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names.\n This document obsoletes RFC 3731.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4931 EPP Domain Name Mapping May 2007","scope_keywords":["4931","attribute","attributes","authorization","management","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null}],"search_text":"IETF RFC 4931 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names.\n This document obsoletes RFC 3731.\n\nHollenbeck Standards Track [Page 1]\n\f\nRFC 4931 EPP Domain Name Mapping May 2007 4931 attribute attributes authorization management qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 5731","type":"specification","body":"IETF","designation":"RFC 5731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5731.txt","https://www.rfc-editor.org/rfc/rfc5731.pdf"],"folder":"IETF/RFC-5731","files":{"txt":{"path":"standards/IETF/RFC-5731/RFC-5731.txt","sha256":"1d73872855e026030255eb82adb68dd9797f867339cc4271c6c0f3b06f6f68cc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names.\n This document obsoletes RFC 4931.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents","scope_keywords":["5731","attribute","attributes","authorization","http","license","management","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5731 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names.\n This document obsoletes RFC 4931.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents 5731 attribute attributes authorization http license management qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 5890","type":"specification","body":"IETF","designation":"RFC 5890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5890.txt","https://www.rfc-editor.org/rfc/rfc5890.pdf"],"folder":"IETF/RFC-5890","files":{"txt":{"path":"standards/IETF/RFC-5890/RFC-5890.txt","sha256":"24d27002e26fedaec6c9f6479547e9d0855d952bc47d6ce1000851efd70b7430"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a collection that, together, describe the\n protocol and usage context for a revision of Internationalized Domain\n Names for Applications (IDNA), superseding the earlier version. It\n describes the document collection and provides definitions and other\n material that are common to the set.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5890.\n\nKlensin Standards Trac","scope_keywords":["5890","algorithm","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5893","folder":"IETF/RFC-5893","source":"IETF/RFC-5893/RFC-5893.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 5890 This document is one of a collection that, together, describe the\n protocol and usage context for a revision of Internationalized Domain\n Names for Applications (IDNA), superseding the earlier version. It\n describes the document collection and provides definitions and other\n material that are common to the set.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5890.\n\nKlensin Standards Trac 5890 algorithm http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5894","type":"specification","body":"IETF","designation":"RFC 5894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5894.txt","https://www.rfc-editor.org/rfc/rfc5894.pdf"],"folder":"IETF/RFC-5894","files":{"txt":{"path":"standards/IETF/RFC-5894/RFC-5894.txt","sha256":"79ada485351cdbe29e3f0f9cb2de89a2b74566f16cbe9aae619a1d88020e7632"}},"tags":["nested-reference","unchanged"],"summary":"Several years have passed since the original protocol for\n Internationalized Domain Names (IDNs) was completed and deployed.\n During that time, a number of issues have arisen, including the need\n to update the system to deal with newer versions of Unicode. Some of\n these issues require tuning of the existing protocols and the tables\n on which they depend. This document provides an overview of a\n revised system and provides explanatory material for its components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candi","scope_keywords":["5894","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5894 Several years have passed since the original protocol for\n Internationalized Domain Names (IDNs) was completed and deployed.\n During that time, a number of issues have arisen, including the need\n to update the system to deal with newer versions of Unicode. Some of\n these issues require tuning of the existing protocols and the tables\n on which they depend. This document provides an overview of a\n revised system and provides explanatory material for its components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candi 5894 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6365","type":"specification","body":"IETF","designation":"RFC 6365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6365.txt","https://www.rfc-editor.org/rfc/rfc6365.pdf"],"folder":"IETF/RFC-6365","files":{"txt":{"path":"standards/IETF/RFC-6365/RFC-6365.txt","sha256":"8988050fe2eb7a9179dd6a61a110a1396dfaa6d81adb7ffa341f1f94040ce54e"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a list of terms used in the IETF when\n discussing internationalization. The purpose is to help frame\n discussions of internationalization in the various areas of the IETF\n and to help introduce the main concepts to IETF participants.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6365.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n","scope_keywords":["6365","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6365 This document provides a list of terms used in the IETF when\n discussing internationalization. The purpose is to help frame\n discussions of internationalization in the various areas of the IETF\n and to help introduce the main concepts to IETF participants.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6365.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n 6365 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6698","type":"specification","body":"IETF","designation":"RFC 6698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6698.txt","https://www.rfc-editor.org/rfc/rfc6698.pdf"],"folder":"IETF/RFC-6698","files":{"txt":{"path":"standards/IETF/RFC-6698/RFC-6698.txt","sha256":"daecd0cdee8d8b8896c8f463c95237d32d42bbe1ecfc1c65a232cb1300d3f668"}},"tags":["nested-reference","unchanged"],"summary":"Encrypted communication on the Internet often uses Transport Layer\n Security (TLS), which depends on third parties to certify the keys\n used. This document improves on that situation by enabling the\n administrators of domain names to specify the keys used in that\n domain's TLS servers. This requires matching improvements in TLS\n client software, but no change in TLS server software.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obt","scope_keywords":["6698","authentication","certificate","certificates","encryption","http","key","keys","license","presentation","risk","signature","signatures","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7218","folder":"IETF/RFC-7218","source":"IETF/RFC-7218/RFC-7218.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 6698 Encrypted communication on the Internet often uses Transport Layer\n Security (TLS), which depends on third parties to certify the keys\n used. This document improves on that situation by enabling the\n administrators of domain names to specify the keys used in that\n domain's TLS servers. This requires matching improvements in TLS\n client software, but no change in TLS server software.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obt 6698 authentication certificate certificates encryption http key keys license presentation risk signature signatures subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6885","type":"specification","body":"IETF","designation":"RFC 6885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6885.txt","https://www.rfc-editor.org/rfc/rfc6885.pdf"],"folder":"IETF/RFC-6885","files":{"txt":{"path":"standards/IETF/RFC-6885/RFC-6885.txt","sha256":"8676ab9a27dc49dc8d5127a54cc6bb7f2f333b6bcf7937aa5ff8f8296051e010"}},"tags":["nested-reference","unchanged"],"summary":"If a protocol expects to compare two strings and is prepared only for\n those strings to be ASCII, then using Unicode code points in those\n strings requires they be prepared somehow. Internationalizing Domain\n Names in Applications (here called IDNA2003) defined and used\n Stringprep and Nameprep. Other protocols subsequently defined\n Stringprep profiles. A new approach different from Stringprep and\n Nameprep is used for a revision of IDNA2003 (called IDNA2008). Other\n Stringprep profiles need to be similarly updated, or a replacement of\n Stringprep needs to be designed. This document outlines the issues\n to be faced by those designing a Stringprep replacement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the conse","scope_keywords":["6885","authentication","certificate","crl","http","identification","key","license","management","pki","policy","preservation","profile","profiles","revocation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 6885 If a protocol expects to compare two strings and is prepared only for\n those strings to be ASCII, then using Unicode code points in those\n strings requires they be prepared somehow. Internationalizing Domain\n Names in Applications (here called IDNA2003) defined and used\n Stringprep and Nameprep. Other protocols subsequently defined\n Stringprep profiles. A new approach different from Stringprep and\n Nameprep is used for a revision of IDNA2003 (called IDNA2008). Other\n Stringprep profiles need to be similarly updated, or a replacement of\n Stringprep needs to be designed. This document outlines the issues\n to be faced by those designing a Stringprep replacement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the conse 6885 authentication certificate crl http identification key license management pki policy preservation profile profiles revocation risk nested-reference unchanged"},{"id":"IETF RFC 7482","type":"specification","body":"IETF","designation":"RFC 7482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7482.txt","https://www.rfc-editor.org/rfc/rfc7482.pdf"],"folder":"IETF/RFC-7482","files":{"txt":{"path":"standards/IETF/RFC-7482/RFC-7482.txt","sha256":"0c9f954855db9bfb8a7f4f12bcd39a370861dde524fa4ee85df56f9b8c492c2f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes uniform patterns to construct HTTP URLs that\n may be used to retrieve registration information from registries\n (including both Regional Internet Registries (RIRs) and Domain Name\n Registries (DNRs)) using \"RESTful\" web access patterns. These\n uniform patterns define the query syntax for the Registration Data\n Access Protocol (RDAP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-e","scope_keywords":["7482","authentication","authorization","http","identification","key","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 7482 This document describes uniform patterns to construct HTTP URLs that\n may be used to retrieve registration information from registries\n (including both Regional Internet Registries (RIRs) and Domain Name\n Registries (DNRs)) using \"RESTful\" web access patterns. These\n uniform patterns define the query syntax for the Registration Data\n Access Protocol (RDAP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-e 7482 authentication authorization http identification key license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8552","type":"specification","body":"IETF","designation":"RFC 8552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8552.txt","https://www.rfc-editor.org/rfc/rfc8552.pdf"],"folder":"IETF/RFC-8552","files":{"txt":{"path":"standards/IETF/RFC-8552/RFC-8552.txt","sha256":"6ce80b1954ecf86a399e93a76ee894224bb057b2fbd9ce8e1f287c9bd954aecd"}},"tags":["nested-reference","unchanged"],"summary":"Formally, any DNS Resource Record (RR) may occur under any domain\n name. However, some services use an operational convention for\n defining specific interpretations of an RRset by locating the records\n in a DNS branch under the parent domain to which the RRset actually\n applies. The top of this subordinate branch is defined by a naming\n convention that uses a reserved node name, which begins with the\n underscore character (e.g., \"_name\"). The underscored naming\n construct defines a semantic scope for DNS record types that are\n associated with the parent domain above the underscored branch. This\n specification explores the nature of this DNS usage and defines the\n \"Underscored and Globally Scoped DNS Node Names\" registry with IANA.\n The purpose of this registry is to avoid collisions resulting from\n the use of the same underscored name for different services.\n\nStatus of This Memo\n\n This m","scope_keywords":["8552","attribute","attributes","http","https","key","keys","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null}],"search_text":"IETF RFC 8552 Formally, any DNS Resource Record (RR) may occur under any domain\n name. However, some services use an operational convention for\n defining specific interpretations of an RRset by locating the records\n in a DNS branch under the parent domain to which the RRset actually\n applies. The top of this subordinate branch is defined by a naming\n convention that uses a reserved node name, which begins with the\n underscore character (e.g., \"_name\"). The underscored naming\n construct defines a semantic scope for DNS record types that are\n associated with the parent domain above the underscored branch. This\n specification explores the nature of this DNS usage and defines the\n \"Underscored and Globally Scoped DNS Node Names\" registry with IANA.\n The purpose of this registry is to avoid collisions resulting from\n the use of the same underscored name for different services.\n\nStatus of This Memo\n\n This m 8552 attribute attributes http https key keys license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 9082","type":"specification","body":"IETF","designation":"RFC 9082","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9082.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9082.txt","https://www.rfc-editor.org/rfc/rfc9082.pdf"],"folder":"IETF/RFC-9082","files":{"pdf":{"path":"standards/IETF/RFC-9082/RFC-9082.pdf","sha256":"8ba6496f21cd591fa34e3940d6a342e196f41372fce625bfcbaed38352c829d1"},"txt":{"path":"standards/IETF/RFC-9082/RFC-9082.txt","sha256":"4958eda636664295f07156ee205e7c277e933edb9b3995fa369c2a97ff9bfc0e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes uniform patterns to construct HTTP URLs that\n may be used to retrieve registration information from registries\n (including both Regional Internet Registries (RIRs) and Domain Name\n Registries (DNRs)) using \"RESTful\" web access patterns. These\n uniform patterns define the query syntax for the Registration Data\n Access Protocol (RDAP). This document obsoletes RFC 7482.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma","scope_keywords":["9082","authentication","authorization","http","https","identification","key","license","management","path","policy","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9082 This document describes uniform patterns to construct HTTP URLs that\n may be used to retrieve registration information from registries\n (including both Regional Internet Registries (RIRs) and Domain Name\n Registries (DNRs)) using \"RESTful\" web access patterns. These\n uniform patterns define the query syntax for the Registration Data\n Access Protocol (RDAP). This document obsoletes RFC 7482.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma 9082 authentication authorization http https identification key license management path policy presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 0954","type":"specification","body":"IETF","designation":"RFC 0954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0954.txt","https://www.rfc-editor.org/rfc/rfc0954.pdf"],"folder":"IETF/RFC-0954","files":{"txt":{"path":"standards/IETF/RFC-0954/RFC-0954.txt","sha256":"f7a84d312f8e2d2b4f3105f32d7849333b41bd60097a2b534aefaae8483fb8c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 954 M. Stahl (SRI)\nObsoletes: RFC 812 E. Feinler (SRI)\n October 1985\n\n NICNAME/WHOIS\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the NICNAME/WHOIS protocol.\n This memo describes the protocol and the service. This is an update\n of RFC 812. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is a TCP transaction based query/response\n server, running on the SRI-NIC machine (26.0.0.73 or 10.0.0.51), that\n provides netwide directory service to internet users. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The server is accessible across\n the Internet from user programs running on local hosts, and it\n delivers the full name, U.S. mailing address, te","scope_keywords":["0954","crl","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 0954 Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 954 M. Stahl (SRI)\nObsoletes: RFC 812 E. Feinler (SRI)\n October 1985\n\n NICNAME/WHOIS\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the NICNAME/WHOIS protocol.\n This memo describes the protocol and the service. This is an update\n of RFC 812. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is a TCP transaction based query/response\n server, running on the SRI-NIC machine (26.0.0.73 or 10.0.0.51), that\n provides netwide directory service to internet users. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The server is accessible across\n the Internet from user programs running on local hosts, and it\n delivers the full name, U.S. mailing address, te 0954 crl registered risk nested-reference unchanged"},{"id":"IETF RFC 0959","type":"specification","body":"IETF","designation":"RFC 0959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0959.txt","https://www.rfc-editor.org/rfc/rfc0959.pdf"],"folder":"IETF/RFC-0959","files":{"txt":{"path":"standards/IETF/RFC-0959/RFC-0959.txt","sha256":"e2eb01566e64c12ed75a0c4bd02231e62f91eebb86f596abc40999d5e8bc5a91"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 959 J. Reynolds\n ISI\nObsoletes RFC: 765 (IEN 149) October 1985\n\n FILE TRANSFER PROTOCOL (FTP)\n\nStatus of this Memo\n\n This memo is the official specification of the File Transfer\n Protocol (FTP). Distribution of this memo is unlimited.\n\n The following new optional commands are included in this edition of\n the specification:\n\n CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU\n (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD\n (Print Directory), and SYST (System).\n\n Note that this specification is compatible with the previous edition.\n\n1. INTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among hosts, and 4) to trans","scope_keywords":["0959","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 0959 Network Working Group J. Postel\nRequest for Comments: 959 J. Reynolds\n ISI\nObsoletes RFC: 765 (IEN 149) October 1985\n\n FILE TRANSFER PROTOCOL (FTP)\n\nStatus of this Memo\n\n This memo is the official specification of the File Transfer\n Protocol (FTP). Distribution of this memo is unlimited.\n\n The following new optional commands are included in this edition of\n the specification:\n\n CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU\n (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD\n (Print Directory), and SYST (System).\n\n Note that this specification is compatible with the previous edition.\n\n1. INTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among hosts, and 4) to trans 0959 path subject nested-reference unchanged"},{"id":"IETF RFC 5694","type":"specification","body":"IETF","designation":"RFC 5694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5694.txt","https://www.rfc-editor.org/rfc/rfc5694.pdf"],"folder":"IETF/RFC-5694","files":{"txt":{"path":"standards/IETF/RFC-5694/RFC-5694.txt","sha256":"bfc3887aac2c28b877a06e8ee257181388ddb35834287f8d608a100d54b5bcc6"}},"tags":["nested-reference","unchanged"],"summary":"In this document, we provide a survey of P2P (Peer-to-Peer) systems.\n The survey includes a definition and several taxonomies of P2P\n systems. This survey also includes a description of which types of\n applications can be built with P2P technologies and examples of P2P\n applications that are currently in use on the Internet. Finally, we\n discuss architectural trade-offs and provide guidelines for deciding\n whether or not a P2P architecture would be suitable to meet the\n requirements of a given application.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating t","scope_keywords":["5694","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 5694 In this document, we provide a survey of P2P (Peer-to-Peer) systems.\n The survey includes a definition and several taxonomies of P2P\n systems. This survey also includes a description of which types of\n applications can be built with P2P technologies and examples of P2P\n applications that are currently in use on the Internet. Finally, we\n discuss architectural trade-offs and provide guidelines for deciding\n whether or not a P2P architecture would be suitable to meet the\n requirements of a given application.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating t 5694 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6022","type":"specification","body":"IETF","designation":"RFC 6022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6022.txt","https://www.rfc-editor.org/rfc/rfc6022.pdf"],"folder":"IETF/RFC-6022","files":{"txt":{"path":"standards/IETF/RFC-6022/RFC-6022.txt","sha256":"fc0382558872efdfcb50d01f426241020910f10b026cafdd420b0afb30c81a0a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Network Configuration Protocol (NETCONF) data\n model to be used to monitor the NETCONF protocol. The monitoring\n data model includes information about NETCONF datastores, sessions,\n locks, and statistics. This data facilitates the management of a\n NETCONF server. This document also defines methods for NETCONF\n clients to discover data models supported by a NETCONF server and\n defines a new NETCONF <get-schema> operation to retrieve them.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current st","scope_keywords":["6022","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 6022 This document defines a Network Configuration Protocol (NETCONF) data\n model to be used to monitor the NETCONF protocol. The monitoring\n data model includes information about NETCONF datastores, sessions,\n locks, and statistics. This data facilitates the management of a\n NETCONF server. This document also defines methods for NETCONF\n clients to discover data models supported by a NETCONF server and\n defines a new NETCONF <get-schema> operation to retrieve them.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current st 6022 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6080","type":"specification","body":"IETF","designation":"RFC 6080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6080.txt","https://www.rfc-editor.org/rfc/rfc6080.pdf"],"folder":"IETF/RFC-6080","files":{"txt":{"path":"standards/IETF/RFC-6080/RFC-6080.txt","sha256":"8e494a5a7c160d74127ff0ba148b01e86f0efe23dd7592f7a2fac43e2d1744e8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a framework to enable configuration of\n Session Initiation Protocol (SIP) user agents (UAs) in SIP\n deployments. The framework provides a means to deliver profile data\n that user agents need to be functional, automatically and with\n minimal or no User and Administrative intervention. The framework\n describes how SIP user agents can discover sources, request profiles,\n and receive notifications related to profile modifications. As part\n of this framework, a new SIP event package is defined for\n notification of profile changes. The framework provides minimal data\n retrieval options to ensure interoperability. The framework does not\n include specification of the profile data within its scope.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of ","scope_keywords":["6080","delivery","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 6080 This document specifies a framework to enable configuration of\n Session Initiation Protocol (SIP) user agents (UAs) in SIP\n deployments. The framework provides a means to deliver profile data\n that user agents need to be functional, automatically and with\n minimal or no User and Administrative intervention. The framework\n describes how SIP user agents can discover sources, request profiles,\n and receive notifications related to profile modifications. As part\n of this framework, a new SIP event package is defined for\n notification of profile changes. The framework provides minimal data\n retrieval options to ensure interoperability. The framework does not\n include specification of the profile data within its scope.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of  6080 delivery http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 0964","type":"specification","body":"IETF","designation":"RFC 0964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0964.txt","https://www.rfc-editor.org/rfc/rfc0964.pdf"],"folder":"IETF/RFC-0964","files":{"txt":{"path":"standards/IETF/RFC-0964/RFC-0964.txt","sha256":"e102129df374c4888e308ec5cc02856d31b7b3127812d9160cb2cc12ed2d49b5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Deepinder P. Sidhu\nRequest for Comments: 964 Thomas P. Blumer\n SDC - A Burroughs Company\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD TRANSMISSION CONTROL PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Transmission Control Protocol (MIL-STD-1778) so\n that one can obtain a reliable implementation of this protocol\n standard. Distribution of this note is unlimited.\n\n Reprinted from: Proc. Protocol Specification, Testing and\n Verification IV, (ed.) Y. Yemini, et al, North-Holland (1984).\n\nABSTRACT\n\n This note points out three errors with the specification of the\n Military Standard Transmission Control Protocol (MIL-STD-1778, dated\n August 1983 [MILS83]). These results are based on an initial\n investigation of this protocol standard. The first problem is that\n data acc","scope_keywords":["0964","delivery","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null}],"search_text":"IETF RFC 0964 Network Working Group Deepinder P. Sidhu\nRequest for Comments: 964 Thomas P. Blumer\n SDC - A Burroughs Company\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD TRANSMISSION CONTROL PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Transmission Control Protocol (MIL-STD-1778) so\n that one can obtain a reliable implementation of this protocol\n standard. Distribution of this note is unlimited.\n\n Reprinted from: Proc. Protocol Specification, Testing and\n Verification IV, (ed.) Y. Yemini, et al, North-Holland (1984).\n\nABSTRACT\n\n This note points out three errors with the specification of the\n Military Standard Transmission Control Protocol (MIL-STD-1778, dated\n August 1983 [MILS83]). These results are based on an initial\n investigation of this protocol standard. The first problem is that\n data acc 0964 delivery management policy nested-reference unchanged"},{"id":"IETF RFC 7806","type":"specification","body":"IETF","designation":"RFC 7806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7806.txt","https://www.rfc-editor.org/rfc/rfc7806.pdf"],"folder":"IETF/RFC-7806","files":{"txt":{"path":"standards/IETF/RFC-7806/RFC-7806.txt","sha256":"a8017d124eb05a2275b711fb65131cfc24a61a58f9bec8e904fcdc8c92ec704d"}},"tags":["nested-reference","unchanged"],"summary":"This note discusses queuing and marking/dropping algorithms. While\n these algorithms may be implemented in a coupled manner, this note\n argues that specifications, measurements, and comparisons should\n decouple the different algorithms and their contributions to system\n behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine","scope_keywords":["7806","algorithm","algorithms","attribute","attributes","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null}],"search_text":"IETF RFC 7806 This note discusses queuing and marking/dropping algorithms. While\n these algorithms may be implemented in a coupled manner, this note\n argues that specifications, measurements, and comparisons should\n decouple the different algorithms and their contributions to system\n behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtaine 7806 algorithm algorithms attribute attributes http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 0974","type":"specification","body":"IETF","designation":"RFC 0974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0974.txt","https://www.rfc-editor.org/rfc/rfc0974.pdf"],"folder":"IETF/RFC-0974","files":{"txt":{"path":"standards/IETF/RFC-0974/RFC-0974.txt","sha256":"318ffff5486dea88b454225d89b513b0a0e86be814657feb09d9e3f9016958a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Craig Partridge\nRequest for Comments: 974 CSNET CIC BBN Laboratories Inc\n January 1986\n\n MAIL ROUTING AND THE DOMAIN SYSTEM\n\nStatus of this Memo\n\n This RFC presents a description of how mail systems on the Internet\n are expected to route messages based on information from the domain\n system described in RFCs 882, 883 and 973. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n The purpose of this memo is to explain how mailers are to decide how\n to route a message addressed to a given Internet domain name. This\n involves a discussion of how mailers interpret MX RRs, which are used\n for message routing. Note that this memo makes no statement about\n how mailers are to deal with MB and MG RRs, which are used for\n interpreting mailbox names.\n\n Under RFC-882 and RFC-883 certain assumptions about mail addresses\n have been changed. Up to now, one could usually assume ","scope_keywords":["0974","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 0974 Network Working Group Craig Partridge\nRequest for Comments: 974 CSNET CIC BBN Laboratories Inc\n January 1986\n\n MAIL ROUTING AND THE DOMAIN SYSTEM\n\nStatus of this Memo\n\n This RFC presents a description of how mail systems on the Internet\n are expected to route messages based on information from the domain\n system described in RFCs 882, 883 and 973. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n The purpose of this memo is to explain how mailers are to decide how\n to route a message addressed to a given Internet domain name. This\n involves a discussion of how mailers interpret MX RRs, which are used\n for message routing. Note that this memo makes no statement about\n how mailers are to deal with MB and MG RRs, which are used for\n interpreting mailbox names.\n\n Under RFC-882 and RFC-883 certain assumptions about mail addresses\n have been changed. Up to now, one could usually assume  0974 pid nested-reference unchanged"},{"id":"IETF RFC 5336","type":"specification","body":"IETF","designation":"RFC 5336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5336.txt","https://www.rfc-editor.org/rfc/rfc5336.pdf"],"folder":"IETF/RFC-5336","files":{"txt":{"path":"standards/IETF/RFC-5336/RFC-5336.txt","sha256":"617399c0bdc965f658f7bad0da9b47a1ffeb2e7bd752cbe86f70aea76fae2fe5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an SMTP extension for transport and delivery\n of email messages with internationalized email addresses or header\n information. Communication with systems that do not implement this\n specification is specified in another document. This document\n updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and\n has some material updating RFC 4952.\n\nYao & Mao Experimental [Page 1]\n\f\nRFC 5336 EAI SMTP Extension September 2008","scope_keywords":["5336","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null}],"search_text":"IETF RFC 5336 This document specifies an SMTP extension for transport and delivery\n of email messages with internationalized email addresses or header\n information. Communication with systems that do not implement this\n specification is specified in another document. This document\n updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and\n has some material updating RFC 4952.\n\nYao & Mao Experimental [Page 1]\n\f\nRFC 5336 EAI SMTP Extension September 2008 5336 delivery key nested-reference unchanged"},{"id":"IETF RFC 0977","type":"specification","body":"IETF","designation":"RFC 0977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0977.txt","https://www.rfc-editor.org/rfc/rfc0977.pdf"],"folder":"IETF/RFC-0977","files":{"txt":{"path":"standards/IETF/RFC-0977/RFC-0977.txt","sha256":"c6c987a0a0d832344d66f07c69f13398705dd23467df205c51a97609f5bc98ae"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Brian Kantor (U.C. San Diego)\nRequest for Comments: 977 Phil Lapsley (U.C. Berkeley)\n February 1986\n\n Network News Transfer Protocol\n \n A Proposed Standard for the Stream-Based\n Transmission of News\n\nStatus of This Memo\n\n NNTP specifies a protocol for the distribution, inquiry, retrieval,\n and posting of news articles using a reliable stream-based\n transmission of news among the ARPA-Internet community. NNTP is\n designed so that news articles are stored in a central database\n allowing a subscriber to select only those items he wishes to read.\n Indexing, cross-referencing, and expiration of aged messages are also\n provided. This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n For many years, the ARPA-Internet community has supported","scope_keywords":["0977","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null}],"search_text":"IETF RFC 0977 Network Working Group Brian Kantor (U.C. San Diego)\nRequest for Comments: 977 Phil Lapsley (U.C. Berkeley)\n February 1986\n\n Network News Transfer Protocol\n \n A Proposed Standard for the Stream-Based\n Transmission of News\n\nStatus of This Memo\n\n NNTP specifies a protocol for the distribution, inquiry, retrieval,\n and posting of news articles using a reliable stream-based\n transmission of news among the ARPA-Internet community. NNTP is\n designed so that news articles are stored in a central database\n allowing a subscriber to select only those items he wishes to read.\n Indexing, cross-referencing, and expiration of aged messages are also\n provided. This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n For many years, the ARPA-Internet community has supported 0977 pid nested-reference unchanged"},{"id":"IETF RFC 0989","type":"specification","body":"IETF","designation":"RFC 0989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc0989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc0989.txt","https://www.rfc-editor.org/rfc/rfc0989.pdf"],"folder":"IETF/RFC-0989","files":{"txt":{"path":"standards/IETF/RFC-0989/RFC-0989.txt","sha256":"9dbf7ba8ff2f2bfe3cb4837d1dffd54798a6cf39f2cb765a68d0b5f876bfce4e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Linn (BBNCC)\nRequest for Comments: 989 IAB Privacy Task Force\n February 1987\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Matt Bishop, Danny Cohen, Tom Daniel, Charles Fox, Morrie\n Gasser, Steve Kent (chairman), John Laws, Steve Lipner, Dan Nessett,\n Mike Padlipsky,","scope_keywords":["0989","attribute","attributes","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null}],"search_text":"IETF RFC 0989 Network Working Group John Linn (BBNCC)\nRequest for Comments: 989 IAB Privacy Task Force\n February 1987\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Matt Bishop, Danny Cohen, Tom Daniel, Charles Fox, Morrie\n Gasser, Steve Kent (chairman), John Laws, Steve Lipner, Dan Nessett,\n Mike Padlipsky, 0989 attribute attributes authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 5585","type":"specification","body":"IETF","designation":"RFC 5585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5585.txt","https://www.rfc-editor.org/rfc/rfc5585.pdf"],"folder":"IETF/RFC-5585","files":{"txt":{"path":"standards/IETF/RFC-5585/RFC-5585.txt","sha256":"a0aa796da01961f96eb346f388f906203a51d421aad0262729d5bf4df08fea57"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of the DomainKeys Identified Mail\n (DKIM) service and describes how it can fit into a messaging service.\n It also describes how DKIM relates to other IETF message signature\n technologies. It is intended for those who are adopting, developing,\n or deploying DKIM. DKIM allows an organization to take\n responsibility for transmitting a message, in a way that can be\n verified by a recipient. The organization can be the author's, the\n originating sending site, an intermediary, or one of their agents. A\n message can contain multiple signatures from the same or different\n organizations involved with the message. DKIM defines a domain-level\n digital signature authentication framework for email, using public-\n key cryptography, with the domain name service as its key server\n technology (RFC 4871). This permits verification of a responsible\n organization, as well ","scope_keywords":["5585","authentication","http","key","keys","license","path","policies","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null}],"search_text":"IETF RFC 5585 This document provides an overview of the DomainKeys Identified Mail\n (DKIM) service and describes how it can fit into a messaging service.\n It also describes how DKIM relates to other IETF message signature\n technologies. It is intended for those who are adopting, developing,\n or deploying DKIM. DKIM allows an organization to take\n responsibility for transmitting a message, in a way that can be\n verified by a recipient. The organization can be the author's, the\n originating sending site, an intermediary, or one of their agents. A\n message can contain multiple signatures from the same or different\n organizations involved with the message. DKIM defines a domain-level\n digital signature authentication framework for email, using public-\n key cryptography, with the domain name service as its key server\n technology (RFC 4871). This permits verification of a responsible\n organization, as well  5585 authentication http key keys license path policies signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 1001","type":"specification","body":"IETF","designation":"RFC 1001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1001.txt","https://www.rfc-editor.org/rfc/rfc1001.pdf"],"folder":"IETF/RFC-1001","files":{"txt":{"path":"standards/IETF/RFC-1001/RFC-1001.txt","sha256":"2ee3780b174cb1d01cd3b96422ddee20d53c1984c74d902d6a606d1d3c0ef11a"}},"tags":["nested-reference","unchanged"],"summary":"This RFC defines a proposed standard protocol to support NetBIOS\nservices in a TCP/IP environment. Both local network and internet\noperation are supported. Various node types are defined to accommodate\nlocal and internet topologies and to allow operation with or without the\nuse of IP broadcast.\n\nThis RFC describes the NetBIOS-over-TCP protocols in a general manner,\nemphasizing the underlying ideas and techniques. Detailed\nspecifications are found in a companion RFC, \"Protocol Standard For a\nNetBIOS Service on a TCP/UDP Transport: Detailed Specifications\".\n\nNetBIOS Working Group [Page 1]\n\f\nRFC 1001 March 1987\n\n SUMMARY OF CONTENTS\n\n1. STATUS OF THIS MEMO 6\n2. ACKNOWLEDGEMENTS 6\n3. INTRODUCTION 7\n4. DESIGN PRINCIPLES 7\n5. OVERVIEW OF NetBIOS 10\n6. NetBIOS FACILITIES SUPPORTED BY THIS STANDARD 15\n7. REQUIRED SUPPORTING SERVICE INTERFACES AND DEFINITIONS 15\n8. RELATED PROTOCOLS AND SERVICES ","scope_keywords":["1001","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1002","folder":"IETF/RFC-1002","source":"IETF/RFC-1002/RFC-1002.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"IETF RFC 1001 This RFC defines a proposed standard protocol to support NetBIOS\nservices in a TCP/IP environment. Both local network and internet\noperation are supported. Various node types are defined to accommodate\nlocal and internet topologies and to allow operation with or without the\nuse of IP broadcast.\n\nThis RFC describes the NetBIOS-over-TCP protocols in a general manner,\nemphasizing the underlying ideas and techniques. Detailed\nspecifications are found in a companion RFC, \"Protocol Standard For a\nNetBIOS Service on a TCP/UDP Transport: Detailed Specifications\".\n\nNetBIOS Working Group [Page 1]\n\f\nRFC 1001 March 1987\n\n SUMMARY OF CONTENTS\n\n1. STATUS OF THIS MEMO 6\n2. ACKNOWLEDGEMENTS 6\n3. INTRODUCTION 7\n4. DESIGN PRINCIPLES 7\n5. OVERVIEW OF NetBIOS 10\n6. NetBIOS FACILITIES SUPPORTED BY THIS STANDARD 15\n7. REQUIRED SUPPORTING SERVICE INTERFACES AND DEFINITIONS 15\n8. RELATED PROTOCOLS AND SERVICES  1001 management presentation nested-reference unchanged"},{"id":"IETF RFC 1002","type":"specification","body":"IETF","designation":"RFC 1002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1002.txt","https://www.rfc-editor.org/rfc/rfc1002.pdf"],"folder":"IETF/RFC-1002","files":{"txt":{"path":"standards/IETF/RFC-1002/RFC-1002.txt","sha256":"af52f2f4df7b6d11358e4a87e673842e7b78203e289dbeccd18906b21a7837b2"}},"tags":["nested-reference","unchanged"],"summary":"This RFC defines a proposed standard protocol to support NetBIOS\nservices in a TCP/IP environment. Both local network and internet\noperation are supported. Various node types are defined to accommodate\nlocal and internet topologies and to allow operation with or without the\nuse of IP broadcast.\n\nThis RFC gives the detailed specifications of the NetBIOS-over-TCP\npackets, protocols, and defined constants and variables. A more general\noverview is found in a companion RFC, \"Protocol Standard For a NetBIOS\nService on a TCP/UDP Transport: Concepts and Methods\".\n\nNetBIOS Working Group [Page 1]\n\f\nRFC 1002 March 1987","scope_keywords":["1002"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"IETF RFC 1002 This RFC defines a proposed standard protocol to support NetBIOS\nservices in a TCP/IP environment. Both local network and internet\noperation are supported. Various node types are defined to accommodate\nlocal and internet topologies and to allow operation with or without the\nuse of IP broadcast.\n\nThis RFC gives the detailed specifications of the NetBIOS-over-TCP\npackets, protocols, and defined constants and variables. A more general\noverview is found in a companion RFC, \"Protocol Standard For a NetBIOS\nService on a TCP/UDP Transport: Concepts and Methods\".\n\nNetBIOS Working Group [Page 1]\n\f\nRFC 1002 March 1987 1002 nested-reference unchanged"},{"id":"IETF RFC 2896","type":"specification","body":"IETF","designation":"RFC 2896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2896.txt","https://www.rfc-editor.org/rfc/rfc2896.pdf"],"folder":"IETF/RFC-2896","files":{"txt":{"path":"standards/IETF/RFC-2896/RFC-2896.txt","sha256":"1c346e3c253988882604a71ece38dd9869c83731f84f6de0d888488fcf648d60"}},"tags":["nested-reference","unchanged"],"summary":"This memo contains various protocol identifier examples, which can be\n used to produce valid protocolDirTable INDEX encodings, as defined by\n the Remote Network Monitoring MIB (Management Information Base)\n Version 2 [RFC2021] and the RMON Protocol Identifier Reference\n [RFC2895].\n\n This document contains protocol identifier macros for well-known\n protocols. A conformant implementation of the RMON-2 MIB [RFC2021]\n can be accomplished without the use of these protocol identifiers,\n and accordingly, this document does not specify any IETF standard.\n It is published to encourage better interoperability between RMON-2\n agent implementations, by providing a great deal of RMON related\n protocol information in one document.\n\n The first version of the RMON Protocol Identifiers Document [RFC2074]\n has been split into a standards-track Reference portion [RFC2895],\n and an \"RMON Protocol Identifier","scope_keywords":["2896","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null}],"search_text":"IETF RFC 2896 This memo contains various protocol identifier examples, which can be\n used to produce valid protocolDirTable INDEX encodings, as defined by\n the Remote Network Monitoring MIB (Management Information Base)\n Version 2 [RFC2021] and the RMON Protocol Identifier Reference\n [RFC2895].\n\n This document contains protocol identifier macros for well-known\n protocols. A conformant implementation of the RMON-2 MIB [RFC2021]\n can be accomplished without the use of these protocol identifiers,\n and accordingly, this document does not specify any IETF standard.\n It is published to encourage better interoperability between RMON-2\n agent implementations, by providing a great deal of RMON related\n protocol information in one document.\n\n The first version of the RMON Protocol Identifiers Document [RFC2074]\n has been split into a standards-track Reference portion [RFC2895],\n and an \"RMON Protocol Identifier 2896 management nested-reference unchanged"},{"id":"IETF RFC 5505","type":"specification","body":"IETF","designation":"RFC 5505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5505.txt","https://www.rfc-editor.org/rfc/rfc5505.pdf"],"folder":"IETF/RFC-5505","files":{"txt":{"path":"standards/IETF/RFC-5505/RFC-5505.txt","sha256":"6447a37fad02d9ffd2dae929b01d47645b7abcb02f6cb768a52bdcb17db516bb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes principles of Internet host configuration.\n It covers issues relating to configuration of Internet-layer\n parameters, as well as parameters affecting higher-layer protocols.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 5505 Principles of Internet Host Configuration May 2009","scope_keywords":["5505","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 5505 This document describes principles of Internet host configuration.\n It covers issues relating to configuration of Internet-layer\n parameters, as well as parameters affecting higher-layer protocols.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 5505 Principles of Internet Host Configuration May 2009 5505 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 1003","type":"specification","body":"IETF","designation":"RFC 1003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1003.txt","https://www.rfc-editor.org/rfc/rfc1003.pdf"],"folder":"IETF/RFC-1003","files":{"txt":{"path":"standards/IETF/RFC-1003/RFC-1003.txt","sha256":"5abbc4fb76f0b03d35190e158bad5d7656fc6b3aa20265136b5b2de94f7d08e1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Alan Katz\nRequest for Comments: 1003 USC/ISI\n March 1987\n\n Issues in Defining an Equations Representation Standard\n\nStatus of This Memo\n\n This memo is intended to identify and explore issues in defining a\n standard for the exchange of mathematical equations. No attempt is\n made at a complete definition and more questions are asked than are\n answered. Questions about the user interface are only addressed to\n the extent that they affect interchange issues. Comments are\n welcome. Distribution of this memo is unlimited.\n\nI. Introduction\n\n Since the early days of the Arpanet, electronic mail has been in\n wide use and many regard it as an essential tool. Numerous mailing\n lists and newsgroups have sprung up over the years, allowing large\n numbers of people all over the world to participate remotely in\n discussions on a variety of topics. More recently, multimedia mail\n sy","scope_keywords":["1003","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null}],"search_text":"IETF RFC 1003 Network Working Group Alan Katz\nRequest for Comments: 1003 USC/ISI\n March 1987\n\n Issues in Defining an Equations Representation Standard\n\nStatus of This Memo\n\n This memo is intended to identify and explore issues in defining a\n standard for the exchange of mathematical equations. No attempt is\n made at a complete definition and more questions are asked than are\n answered. Questions about the user interface are only addressed to\n the extent that they affect interchange issues. Comments are\n welcome. Distribution of this memo is unlimited.\n\nI. Introduction\n\n Since the early days of the Arpanet, electronic mail has been in\n wide use and many regard it as an essential tool. Numerous mailing\n lists and newsgroups have sprung up over the years, allowing large\n numbers of people all over the world to participate remotely in\n discussions on a variety of topics. More recently, multimedia mail\n sy 1003 presentation nested-reference unchanged"},{"id":"IETF RFC 1004","type":"specification","body":"IETF","designation":"RFC 1004","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1004.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1004.txt","https://www.rfc-editor.org/rfc/rfc1004.pdf"],"folder":"IETF/RFC-1004","files":{"txt":{"path":"standards/IETF/RFC-1004/RFC-1004.txt","sha256":"9a28e1591b2234f52cb44512939fdc651c2955dc5627a8233506e6506c62d9cf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 1004 University of Delaware\n April 1987\n\n A Distributed-Protocol Authentication Scheme\n\nStatus of this Memo\n\n The purpose of this RFC is to focus discussion on authentication\n problems in the Internet and possible methods of solution. The\n proposed solutions this document are not intended as standards for\n the Internet at this time. Rather, it is hoped that a general\n consensus will emerge as to the appropriate solution to\n authentication problems, leading eventually to the adoption of\n standards. Distribution of this memo is unlimited.\n\n1. Introduction and Overview\n\n This document suggests mediated access-control and authentication\n procedures suitable for those cases when an association is to be set\n up between multiple users belonging to different trust environments,\n but running distributed protocols like the existing Exterior Ga","scope_keywords":["1004","algorithm","authentication","delivery","encryption","key","keys","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1004 Network Working Group D.L. Mills\nRequest for Comments: 1004 University of Delaware\n April 1987\n\n A Distributed-Protocol Authentication Scheme\n\nStatus of this Memo\n\n The purpose of this RFC is to focus discussion on authentication\n problems in the Internet and possible methods of solution. The\n proposed solutions this document are not intended as standards for\n the Internet at this time. Rather, it is hoped that a general\n consensus will emerge as to the appropriate solution to\n authentication problems, leading eventually to the adoption of\n standards. Distribution of this memo is unlimited.\n\n1. Introduction and Overview\n\n This document suggests mediated access-control and authentication\n procedures suitable for those cases when an association is to be set\n up between multiple users belonging to different trust environments,\n but running distributed protocols like the existing Exterior Ga 1004 algorithm authentication delivery encryption key keys path trust nested-reference unchanged"},{"id":"IETF RFC 3792","type":"specification","body":"IETF","designation":"RFC 3792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3792.txt","https://www.rfc-editor.org/rfc/rfc3792.pdf"],"folder":"IETF/RFC-3792","files":{"txt":{"path":"standards/IETF/RFC-3792/RFC-3792.txt","sha256":"072b0b7a646923a5d98e76befbeb4d6e3889cdef59902bfd2db5f71c8328cc0a"}},"tags":["nested-reference","unchanged"],"summary":"This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Security Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented.","scope_keywords":["3792","attribute","attributes","authentication","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 3792 This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Security Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented. 3792 attribute attributes authentication http key management nested-reference unchanged"},{"id":"IETF RFC 1005","type":"specification","body":"IETF","designation":"RFC 1005","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1005.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1005.txt","https://www.rfc-editor.org/rfc/rfc1005.pdf"],"folder":"IETF/RFC-1005","files":{"txt":{"path":"standards/IETF/RFC-1005/RFC-1005.txt","sha256":"eaf8022772fadb9d11ed7c360fddd55af172559e10cbf47aff9a1e34604b444e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Atul Khanna, Andy Malis\nRequest for Comments: 1005 BBN Communications Corp.\n May 1987\n\n The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)\n\n1. Status of this Memo\n\n This RFC is a proposed specification for the encoding of Class A\n IP addresses for use on ARPANET-style networks such as the Milnet\n and Arpanet, and for enhancements to the ARPANET AHIP Host Access\n Protocol (AHIP; formerly known as 1822). These enhancements\n increase the size of the PSN field, allow ARPANET hosts to use\n logical names to address each other, allow for the communication\n of type-of-service information from the host to the PSN and\n enable the PSN to provide congestion feedback to the host on a\n connection basis. Distribution of this memo is unlimited.\n Comments on this RFC should be sent to the netmail address\n \"ahipe@bbn.com\".\n\nKhanna & Malis [Page 1]\n\f\nRFC 1005 May 1987\n\n Table of ","scope_keywords":["1005","authorization","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1005 Network Working Group Atul Khanna, Andy Malis\nRequest for Comments: 1005 BBN Communications Corp.\n May 1987\n\n The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)\n\n1. Status of this Memo\n\n This RFC is a proposed specification for the encoding of Class A\n IP addresses for use on ARPANET-style networks such as the Milnet\n and Arpanet, and for enhancements to the ARPANET AHIP Host Access\n Protocol (AHIP; formerly known as 1822). These enhancements\n increase the size of the PSN field, allow ARPANET hosts to use\n logical names to address each other, allow for the communication\n of type-of-service information from the host to the PSN and\n enable the PSN to provide congestion feedback to the host on a\n connection basis. Distribution of this memo is unlimited.\n Comments on this RFC should be sent to the netmail address\n \"ahipe@bbn.com\".\n\nKhanna & Malis [Page 1]\n\f\nRFC 1005 May 1987\n\n Table of  1005 authorization policies nested-reference unchanged"},{"id":"IETF RFC 1006","type":"specification","body":"IETF","designation":"RFC 1006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1006.txt","https://www.rfc-editor.org/rfc/rfc1006.pdf"],"folder":"IETF/RFC-1006","files":{"txt":{"path":"standards/IETF/RFC-1006/RFC-1006.txt","sha256":"855adb9556880a3c71fb24c79f174026e763ff02b1ec19d7248a5a2005883f53"}},"tags":["nested-reference","unchanged"],"summary":"M. Rose & D. Cass [Page 1]\n\f\n\nNetwork Working Group Marshall T. Rose, Dwight E. Cass\nRequest for Comments: RFC 1006 Northrop Research and Technology Center\nObsoletes: RFC 983 May 1987\n\n ISO Transport Service on top of the TCP\n Version: 3\n\nStatus of this Memo\n\n This memo specifies a standard for the Internet community. Hosts\n on the Internet that choose to implement ISO transport services\n on top of the TCP are expected to adopt and implement this\n standard. TCP port 102 is reserved for hosts which implement this\n standard. Distribution of this memo is unlimited.\n\n This memo specifies version 3 of the protocol and supersedes\n [RFC983]. Changes between the protocol as described in Request for\n Comments 983 and this memo are minor, but are unfortunately\n incompatible.\n\nM. Rose & D. Cass [Page 1]\n\f\nRFC 1006 May 1987\n\n1. Introduction and Philosophy\n\n The Internet community has a well-develope","scope_keywords":["1006","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1275","folder":"IETF/RFC-1275","source":"IETF/RFC-1275/RFC-1275.txt","version":null},{"body":"IETF","designation":"RFC 1277","folder":"IETF/RFC-1277","source":"IETF/RFC-1277/RFC-1277.txt","version":null},{"body":"IETF","designation":"RFC 1278","folder":"IETF/RFC-1278","source":"IETF/RFC-1278/RFC-1278.txt","version":null},{"body":"IETF","designation":"RFC 1287","folder":"IETF/RFC-1287","source":"IETF/RFC-1287/RFC-1287.txt","version":null},{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1673","folder":"IETF/RFC-1673","source":"IETF/RFC-1673/RFC-1673.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 1006 M. Rose & D. Cass [Page 1]\n\f\n\nNetwork Working Group Marshall T. Rose, Dwight E. Cass\nRequest for Comments: RFC 1006 Northrop Research and Technology Center\nObsoletes: RFC 983 May 1987\n\n ISO Transport Service on top of the TCP\n Version: 3\n\nStatus of this Memo\n\n This memo specifies a standard for the Internet community. Hosts\n on the Internet that choose to implement ISO transport services\n on top of the TCP are expected to adopt and implement this\n standard. TCP port 102 is reserved for hosts which implement this\n standard. Distribution of this memo is unlimited.\n\n This memo specifies version 3 of the protocol and supersedes\n [RFC983]. Changes between the protocol as described in Request for\n Comments 983 and this memo are minor, but are unfortunately\n incompatible.\n\nM. Rose & D. Cass [Page 1]\n\f\nRFC 1006 May 1987\n\n1. Introduction and Philosophy\n\n The Internet community has a well-develope 1006 key path presentation nested-reference unchanged"},{"id":"IETF RFC 1085","type":"specification","body":"IETF","designation":"RFC 1085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1085.txt","https://www.rfc-editor.org/rfc/rfc1085.pdf"],"folder":"IETF/RFC-1085","files":{"txt":{"path":"standards/IETF/RFC-1085/RFC-1085.txt","sha256":"70dc5d51c1d285946476071e0e0fc60aee40147c27b740758e41232b3a997bbd"}},"tags":["nested-reference","unchanged"],"summary":"transfer notation defines the pronunciation of the language.\n\n 3. User data\n\n User data passes through the presentation service interface as\n ASN.1 objects (in a locally defined form). Associated with each\n object is a presentation context identifier. The PCI\n distinguishes the context for which the data is intended. The\n range of values the PCI may take is severely restricted by this\n memo. Exactly one of two contexts must always be used: either the\n value for the ACSE presentation context or the value for the ROSE.\n\n 4. Quality of Service\n\n Quality of service is a collection of \"elements\". Each element\n denotes some characteristics of the communication, e.g., desired\n throughput, and some value in an arbitrary unit of measure. For\n our purposes, only one quality of service element is interpreted,\n \"transport-mapping\". Currently, the \"transport-mapping\" element\n takes on one of two valu","scope_keywords":["1085","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 1085 transfer notation defines the pronunciation of the language.\n\n 3. User data\n\n User data passes through the presentation service interface as\n ASN.1 objects (in a locally defined form). Associated with each\n object is a presentation context identifier. The PCI\n distinguishes the context for which the data is intended. The\n range of values the PCI may take is severely restricted by this\n memo. Exactly one of two contexts must always be used: either the\n value for the ACSE presentation context or the value for the ROSE.\n\n 4. Quality of Service\n\n Quality of service is a collection of \"elements\". Each element\n denotes some characteristics of the communication, e.g., desired\n throughput, and some value in an arbitrary unit of measure. For\n our purposes, only one quality of service element is interpreted,\n \"transport-mapping\". Currently, the \"transport-mapping\" element\n takes on one of two valu 1085 identification management presentation nested-reference unchanged"},{"id":"IETF RFC 1189","type":"specification","body":"IETF","designation":"RFC 1189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1189.txt","https://www.rfc-editor.org/rfc/rfc1189.pdf"],"folder":"IETF/RFC-1189","files":{"txt":{"path":"standards/IETF/RFC-1189/RFC-1189.txt","sha256":"3b1f1c6999539c8c3e07478509a78a9e514d8c76ea12d39d28097e4d54487407"}},"tags":["nested-reference","unchanged"],"summary":"Syntax Notation One (ASN.1) [5, 6], Association Control (ACSE) [7,\n 8], Remote Operations (ROSE) [9, 10], Common Management Information\n Services (CMIS) [11] and Common Management Information Protocol\n (CMIP) [12] with their addenda [32-35]. The specification of a\n lightweight presentation layer protocol is required for use with the\n CMOT section of this profile (see RFC 1085 [13]). The SMI (see RFC\n 1065 [2]), the MIB-I (see RFC 1066 [3]), the MIB-II (see RFC 1156\n [28]), and the OIM-MIB-II (see [29]) are used with this management\n system.\n\n This memo is divided into sections for each of the protocols for\n which implementors' agreements are needed: CMISE, ACSE, ROSE, and,\n for CMOT, the lightweight presentation protocol. The protocol\n profile defined in this memo draws on the technical work of the OSI\n Network Management Forum [14] and the Network Management Special\n Interest Group (NMS","scope_keywords":["1189","management","policies","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1224","folder":"IETF/RFC-1224","source":"IETF/RFC-1224/RFC-1224.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 1189 Syntax Notation One (ASN.1) [5, 6], Association Control (ACSE) [7,\n 8], Remote Operations (ROSE) [9, 10], Common Management Information\n Services (CMIS) [11] and Common Management Information Protocol\n (CMIP) [12] with their addenda [32-35]. The specification of a\n lightweight presentation layer protocol is required for use with the\n CMOT section of this profile (see RFC 1085 [13]). The SMI (see RFC\n 1065 [2]), the MIB-I (see RFC 1066 [3]), the MIB-II (see RFC 1156\n [28]), and the OIM-MIB-II (see [29]) are used with this management\n system.\n\n This memo is divided into sections for each of the protocols for\n which implementors' agreements are needed: CMISE, ACSE, ROSE, and,\n for CMOT, the lightweight presentation protocol. The protocol\n profile defined in this memo draws on the technical work of the OSI\n Network Management Forum [14] and the Network Management Special\n Interest Group (NMS 1189 management policies presentation profile nested-reference unchanged"},{"id":"IETF RFC 1240","type":"specification","body":"IETF","designation":"RFC 1240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1240.txt","https://www.rfc-editor.org/rfc/rfc1240.pdf"],"folder":"IETF/RFC-1240","files":{"txt":{"path":"standards/IETF/RFC-1240/RFC-1240.txt","sha256":"d895c5ecc30880aadf341cf41dba01dcd6af3410d2cd2d7a07613bcfe99d75f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Shue\nRequest for Comments: 1240 Open Software Foundation\n W. Haggerty\n Wang Laboratories, Inc.\n K. Dobbins\n Cabletron Systems, Inc.\n June 1991\n\n OSI Connectionless Transport Services on top of UDP\n Version: 1\n\nStatus of this Memo\n\n This document describes a protocol for running OSI Connectionless\n service on UDP. This RFC specifies an IAB standards track protocol\n for the Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction and Philosophy\n\n The Internet community has a well-developed, mature set of layered\n transport and network protocols, which are quite successful in\n offering both connection-oriented (TCP) and connectionless (UDP)\n transport s","scope_keywords":["1240","authentication","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2556","folder":"IETF/RFC-2556","source":"IETF/RFC-2556/RFC-2556.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null}],"search_text":"IETF RFC 1240 Network Working Group C. Shue\nRequest for Comments: 1240 Open Software Foundation\n W. Haggerty\n Wang Laboratories, Inc.\n K. Dobbins\n Cabletron Systems, Inc.\n June 1991\n\n OSI Connectionless Transport Services on top of UDP\n Version: 1\n\nStatus of this Memo\n\n This document describes a protocol for running OSI Connectionless\n service on UDP. This RFC specifies an IAB standards track protocol\n for the Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction and Philosophy\n\n The Internet community has a well-developed, mature set of layered\n transport and network protocols, which are quite successful in\n offering both connection-oriented (TCP) and connectionless (UDP)\n transport s 1240 authentication presentation nested-reference unchanged"},{"id":"IETF RFC 1275","type":"specification","body":"IETF","designation":"RFC 1275","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1275.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1275.txt","https://www.rfc-editor.org/rfc/rfc1275.pdf"],"folder":"IETF/RFC-1275","files":{"pdf":{"path":"standards/IETF/RFC-1275/RFC-1275.pdf","sha256":"2782523b8bc589c038702c7c600e5d43e9c1e0026f95ce70e056a69bb4f3941b"},"txt":{"path":"standards/IETF/RFC-1275/RFC-1275.txt","sha256":"e6ad716f4d2aa4bb902de05a23dd4256a1e61d696c6c85459935a0563aa1f547"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1275 University College London\n November 1991\n\nReplication Requirements to provide an Internet Directory using X.500\n\nStatus of this Memo\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo\n is unlimited.\nAbstract\n\n This RFCconsiders certain deficiencies of the 1988 X.500\n standard, which need to be addressed before an effective open\n Internet Directory can be established using these protocols and\n services [CCI88]. The only areas considered are primary\n problems, to which solutions must be found before a pilot can be\n deployed. This RFCconcerns itself with deficiencies which can\n only be addressed by use of additional protocol or procedures for\n distributed operation.\n\f\n\nRFC 1275 Replication Requirements November 1991\n\n1 Distributed Operation Ext","scope_keywords":["1275"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1276","folder":"IETF/RFC-1276","source":"IETF/RFC-1276/RFC-1276.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null}],"search_text":"IETF RFC 1275 Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1275 University College London\n November 1991\n\nReplication Requirements to provide an Internet Directory using X.500\n\nStatus of this Memo\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo\n is unlimited.\nAbstract\n\n This RFCconsiders certain deficiencies of the 1988 X.500\n standard, which need to be addressed before an effective open\n Internet Directory can be established using these protocols and\n services [CCI88]. The only areas considered are primary\n problems, to which solutions must be found before a pilot can be\n deployed. This RFCconcerns itself with deficiencies which can\n only be addressed by use of additional protocol or procedures for\n distributed operation.\n\f\n\nRFC 1275 Replication Requirements November 1991\n\n1 Distributed Operation Ext 1275 nested-reference unchanged"},{"id":"IETF RFC 1277","type":"specification","body":"IETF","designation":"RFC 1277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1277.txt","https://www.rfc-editor.org/rfc/rfc1277.pdf"],"folder":"IETF/RFC-1277","files":{"txt":{"path":"standards/IETF/RFC-1277/RFC-1277.txt","sha256":"cc819abd9436d39b5fe30a0b532af38946239e3b30eb16e90eff1a7e6340a932"}},"tags":["nested-reference","unchanged"],"summary":"The OSI Directory specifies an encoding of Presentation Address,\n which utilises OSI Network Addresses as defined in the OSI\n Network Layer standards [CCI88] [ISO87a]. The OSI Directory, and\n any OSI application utilising the OSI Directory must be able use\n these Network Addresses to identify end systems. Currently, OSI\n applications are often run over lower layers other than the OSI\n Network Service. It is neither reasonable nor desirable for\n groups wishing to investigate and use OSI Applications in\n conjunction with the OSI Directory to be dependent on a global\n OSI Network Service. This document defines a new network address\n format, and rules for using some existing network address\n formats. The scope of this document is:\n\n1. Any TCP/IP network supporting COTS using RFC 1006.\n\n2. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is\n not used to provide CONS (i.e., only DT","scope_keywords":["1277","algorithm","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1276","folder":"IETF/RFC-1276","source":"IETF/RFC-1276/RFC-1276.txt","version":null},{"body":"IETF","designation":"RFC 1278","folder":"IETF/RFC-1278","source":"IETF/RFC-1278/RFC-1278.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1277 The OSI Directory specifies an encoding of Presentation Address,\n which utilises OSI Network Addresses as defined in the OSI\n Network Layer standards [CCI88] [ISO87a]. The OSI Directory, and\n any OSI application utilising the OSI Directory must be able use\n these Network Addresses to identify end systems. Currently, OSI\n applications are often run over lower layers other than the OSI\n Network Service. It is neither reasonable nor desirable for\n groups wishing to investigate and use OSI Applications in\n conjunction with the OSI Directory to be dependent on a global\n OSI Network Service. This document defines a new network address\n format, and rules for using some existing network address\n formats. The scope of this document is:\n\n1. Any TCP/IP network supporting COTS using RFC 1006.\n\n2. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is\n not used to provide CONS (i.e., only DT 1277 algorithm presentation nested-reference unchanged"},{"id":"IETF RFC 1278","type":"specification","body":"IETF","designation":"RFC 1278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1278.txt","https://www.rfc-editor.org/rfc/rfc1278.pdf"],"folder":"IETF/RFC-1278","files":{"txt":{"path":"standards/IETF/RFC-1278/RFC-1278.txt","sha256":"9a5e3cbcd9892cd5aca4208a69f3badc90fdb46cbac81377145db2825d5c855e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1278 University College London\n November 1991\n\n A string encoding of Presentation Address\n\nStatus of this Memo\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo\n is unlimited.\n\nAbstract\n There are a number of environments where a simple string encoding\n of Presentation Address is desirable. This specification defines\n such a representation.\n\f\n\nRFC 1278 String encoded P-Address November 1991\n\n1 Introduction\n\nOSI Application Entities use presentation addresses to address other\nApplication Entities. The model for this is defined in [ISO87b].\nPresentation addresses are stored in the OSI Directory using an ASN.1\nrepresentation defined by the OSI Directory [CCI88]. Logically, a\npresentation address consists of:\n\n o A presentation selector\n\n o A sessio","scope_keywords":["1278","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null}],"search_text":"IETF RFC 1278 Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1278 University College London\n November 1991\n\n A string encoding of Presentation Address\n\nStatus of this Memo\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo\n is unlimited.\n\nAbstract\n There are a number of environments where a simple string encoding\n of Presentation Address is desirable. This specification defines\n such a representation.\n\f\n\nRFC 1278 String encoded P-Address November 1991\n\n1 Introduction\n\nOSI Application Entities use presentation addresses to address other\nApplication Entities. The model for this is defined in [ISO87b].\nPresentation addresses are stored in the OSI Directory using an ASN.1\nrepresentation defined by the OSI Directory [CCI88]. Logically, a\npresentation address consists of:\n\n o A presentation selector\n\n o A sessio 1278 pid presentation nested-reference unchanged"},{"id":"IETF RFC 1287","type":"specification","body":"IETF","designation":"RFC 1287","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1287.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1287.txt","https://www.rfc-editor.org/rfc/rfc1287.pdf"],"folder":"IETF/RFC-1287","files":{"txt":{"path":"standards/IETF/RFC-1287/RFC-1287.txt","sha256":"52f7902da9d4112c78af19f77bfa6f71937feac656acc09ad8f61d4df42fe04f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Clark\nRequest for Comments: 1287 MIT\n L. Chapin\n BBN\n V. Cerf\n CNRI\n R. Braden\n ISI\n R. Hobby\n UC Davis\n December 1991\n\n Towards the Future Internet Architecture\n\nStatus of this Memo\n\n This informational RFC discusses important directions for possible\n future evolution of the Internet architecture, and suggests steps\n towards the desired goals. It is offered to the Internet community\n for discussion and comment. This memo provides information for the\n Internet community. It does not specify an Internet standard.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. INTRODUCTION ................................................. 2\n\n 2. ROUTING AND ADDRESSING ....................................... 5\n\n 3. MULTI-PROTOCOL ARCHITECTURES ................................. 9\n\n 4. SECURITY ARCHITECTURE ........................................ 13\n\n 5 TRAFFIC CONT","scope_keywords":["1287","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1335","folder":"IETF/RFC-1335","source":"IETF/RFC-1335/RFC-1335.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1560","folder":"IETF/RFC-1560","source":"IETF/RFC-1560/RFC-1560.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null}],"search_text":"IETF RFC 1287 Network Working Group D. Clark\nRequest for Comments: 1287 MIT\n L. Chapin\n BBN\n V. Cerf\n CNRI\n R. Braden\n ISI\n R. Hobby\n UC Davis\n December 1991\n\n Towards the Future Internet Architecture\n\nStatus of this Memo\n\n This informational RFC discusses important directions for possible\n future evolution of the Internet architecture, and suggests steps\n towards the desired goals. It is offered to the Internet community\n for discussion and comment. This memo provides information for the\n Internet community. It does not specify an Internet standard.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. INTRODUCTION ................................................. 2\n\n 2. ROUTING AND ADDRESSING ....................................... 5\n\n 3. MULTI-PROTOCOL ARCHITECTURES ................................. 9\n\n 4. SECURITY ARCHITECTURE ........................................ 13\n\n 5 TRAFFIC CONT 1287 management policy nested-reference unchanged"},{"id":"IETF RFC 1292","type":"specification","body":"IETF","designation":"RFC 1292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1292.txt","https://www.rfc-editor.org/rfc/rfc1292.pdf"],"folder":"IETF/RFC-1292","files":{"txt":{"path":"standards/IETF/RFC-1292/RFC-1292.txt","sha256":"8c441680da8047cea0bc4f6771156beeda224cf9d76a4b6cbc3245cdf1cfb9bf"}},"tags":["nested-reference","unchanged"],"summary":"The goal of this document is to provide information regarding the\n availability and capability of implementations of X.500. Comments\n and critiques of this document, and new or updated descriptions of\n X.500 implementations are welcome. Send them to the Directory\n Information Services Infrastructure (DISI) Working Group\n (disi@merit.edu) or to the editors.\n\n1. Introduction\n\n This document catalogs currently available implementations of X.500,\n including commercial products and openly available offerings. It\n contains descriptions of Directory System Agents (DSA), Directory\n User Agents (DUA), and DUA client applications. The latter can\n include such applications as browsers, DSA management tools, or\n lightweight DUAs that employ an application-level protocol to\n communicate with a DUA (which then in turn communicates with a DSA)\n to support user service. Section 2 of this document contai","scope_keywords":["1292","attribute","attributes","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1308","folder":"IETF/RFC-1308","source":"IETF/RFC-1308/RFC-1308.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null}],"search_text":"IETF RFC 1292 The goal of this document is to provide information regarding the\n availability and capability of implementations of X.500. Comments\n and critiques of this document, and new or updated descriptions of\n X.500 implementations are welcome. Send them to the Directory\n Information Services Infrastructure (DISI) Working Group\n (disi@merit.edu) or to the editors.\n\n1. Introduction\n\n This document catalogs currently available implementations of X.500,\n including commercial products and openly available offerings. It\n contains descriptions of Directory System Agents (DSA), Directory\n User Agents (DUA), and DUA client applications. The latter can\n include such applications as browsers, DSA management tools, or\n lightweight DUAs that employ an application-level protocol to\n communicate with a DUA (which then in turn communicates with a DSA)\n to support user service. Section 2 of this document contai 1292 attribute attributes key management subject nested-reference unchanged"},{"id":"IETF RFC 1430","type":"specification","body":"IETF","designation":"RFC 1430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1430.txt","https://www.rfc-editor.org/rfc/rfc1430.pdf"],"folder":"IETF/RFC-1430","files":{"txt":{"path":"standards/IETF/RFC-1430/RFC-1430.txt","sha256":"47af68cda49ab5d9161b8e62883f4d11286d37bd34402521645af0b692310899"}},"tags":["nested-reference","unchanged"],"summary":"There are a number of reasons why a new Internet Directory Service is\n required. This document describes an overall strategy for deploying\n a Directory Service on the Internet, based on the OSI X.500 Directory\n Service. It then describes in more detail the initial steps which\n need to be taken in order to achieve these goals, and how work\n already undertaken by Internet Engineering Task Force Working Groups\n (IETF WGs) is working towards these goals.","scope_keywords":["1430","authentication","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null}],"search_text":"IETF RFC 1430 There are a number of reasons why a new Internet Directory Service is\n required. This document describes an overall strategy for deploying\n a Directory Service on the Internet, based on the OSI X.500 Directory\n Service. It then describes in more detail the initial steps which\n need to be taken in order to achieve these goals, and how work\n already undertaken by Internet Engineering Task Force Working Groups\n (IETF WGs) is working towards these goals. 1430 authentication key management presentation nested-reference unchanged"},{"id":"IETF RFC 1465","type":"specification","body":"IETF","designation":"RFC 1465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1465.txt","https://www.rfc-editor.org/rfc/rfc1465.pdf"],"folder":"IETF/RFC-1465","files":{"txt":{"path":"standards/IETF/RFC-1465/RFC-1465.txt","sha256":"4aa38a6b430ae03bc5189b5fb64524caa94b4635a7248fb20b3432a72aad6435"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group U. Eppenberger\nRequest for Comments: 1465 SWITCH\n May 1993\n\n Routing Coordination for X.400 MHS Services\n Within a Multi Protocol / Multi Network Environment\n Table Format V3 for Static Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The usage of the X.400 Message Handling System (MHS) is growing\n rapidly, especially in the commercial world but much interest can\n also be found in the academic and research community. New networks\n and new addresses come into use each and every day. The underlying\n technology for different X.400 networks can vary depending on the","scope_keywords":["1465","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1465 Network Working Group U. Eppenberger\nRequest for Comments: 1465 SWITCH\n May 1993\n\n Routing Coordination for X.400 MHS Services\n Within a Multi Protocol / Multi Network Environment\n Table Format V3 for Static Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The usage of the X.400 Message Handling System (MHS) is growing\n rapidly, especially in the commercial world but much interest can\n also be found in the academic and research community. New networks\n and new addresses come into use each and every day. The underlying\n technology for different X.400 networks can vary depending on the 1465 pid registered nested-reference unchanged"},{"id":"IETF RFC 1649","type":"specification","body":"IETF","designation":"RFC 1649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1649.txt","https://www.rfc-editor.org/rfc/rfc1649.pdf"],"folder":"IETF/RFC-1649","files":{"txt":{"path":"standards/IETF/RFC-1649/RFC-1649.txt","sha256":"bc4c63c715038175dba8beb584844e5a77260958315a1fc64bff5b3ce9b93efc"}},"tags":["nested-reference","unchanged"],"summary":"solution. It is a requirement that all MDs follow the rules and\n policies defined by reference [1].","scope_keywords":["1649","delivery","key","management","path","policies","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1648","folder":"IETF/RFC-1648","source":"IETF/RFC-1648/RFC-1648.txt","version":null}],"search_text":"IETF RFC 1649 solution. It is a requirement that all MDs follow the rules and\n policies defined by reference [1]. 1649 delivery key management path policies profile profiles nested-reference unchanged"},{"id":"IETF RFC 1673","type":"specification","body":"IETF","designation":"RFC 1673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1673.txt","https://www.rfc-editor.org/rfc/rfc1673.pdf"],"folder":"IETF/RFC-1673","files":{"txt":{"path":"standards/IETF/RFC-1673/RFC-1673.txt","sha256":"5e0d4d2a727a6b41f74c4411d476ae350a55db754b8545b8886503c3a12d80b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Skelton\nRequest for Comments: 1673 EPRI\nCategory: Informational August 1994\n\n Electric Power Research Institute Comments on IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The question of the future of the Internet protocol (IP) is an issue\n of national if not international concern. It is critical to the\n building of a National Information Infrastructure, comparable to the\n adoption of basic standards for the industrial era such as railwa","scope_keywords":["1673","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1673 Network Working Group R. Skelton\nRequest for Comments: 1673 EPRI\nCategory: Informational August 1994\n\n Electric Power Research Institute Comments on IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The question of the future of the Internet protocol (IP) is an issue\n of national if not international concern. It is critical to the\n building of a National Information Infrastructure, comparable to the\n adoption of basic standards for the industrial era such as railwa 1673 key management path policy nested-reference unchanged"},{"id":"IETF RFC 1698","type":"specification","body":"IETF","designation":"RFC 1698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1698.txt","https://www.rfc-editor.org/rfc/rfc1698.pdf"],"folder":"IETF/RFC-1698","files":{"txt":{"path":"standards/IETF/RFC-1698/RFC-1698.txt","sha256":"3f9c6586c1d2311b6fd0f535186e59e3333931d21b8c3ac45a81d08817b551f0"}},"tags":["nested-reference","unchanged"],"summary":"This document states particular octet sequences that comprise the OSI\n upper-layer protocols (Session, Presentation and ACSE) when used to\n support applications with \"basic communications requirements\". These\n include OSI application protocols such as X.400 P7 and Directory\n Access Protocol, and \"migrant\" protocols, originally defined for use\n over other transports.\n\n As well as the octet sequences which are the supporting layer headers\n (and trailers) around the application data, this document includes\n some tutorial material on the OSI upper layers.\n\n An implementation that sends the octet sequences given here, and\n interprets the equivalent protocol received, will be able to\n interwork with an implementation based on the base standard, when\n both are being used to support an appropriate application protocol.","scope_keywords":["1698","identification","presentation","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null}],"search_text":"IETF RFC 1698 This document states particular octet sequences that comprise the OSI\n upper-layer protocols (Session, Presentation and ACSE) when used to\n support applications with \"basic communications requirements\". These\n include OSI application protocols such as X.400 P7 and Directory\n Access Protocol, and \"migrant\" protocols, originally defined for use\n over other transports.\n\n As well as the octet sequences which are the supporting layer headers\n (and trailers) around the application data, this document includes\n some tutorial material on the OSI upper layers.\n\n An implementation that sends the octet sequences given here, and\n interprets the equivalent protocol received, will be able to\n interwork with an implementation based on the base standard, when\n both are being used to support an appropriate application protocol. 1698 identification presentation profile profiles nested-reference unchanged"},{"id":"IETF RFC 1801","type":"specification","body":"IETF","designation":"RFC 1801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1801.txt","https://www.rfc-editor.org/rfc/rfc1801.pdf"],"folder":"IETF/RFC-1801","files":{"txt":{"path":"standards/IETF/RFC-1801/RFC-1801.txt","sha256":"1cd5feaf6aa236c0ec79304f5153bd644cf425bda8e6f81d3041b8597cfd8143"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 1801 ISODE Consortium\nCategory: Experimental June 1995\n\n X.400-MHS use of the X.500 Directory to support X.400-MHS Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Introduction 3\n 2 Goals 3\n 3 Approach 5\n 4 Direct vs Indirect Connection 6\n 5 X.400 and RFC 822 8\n 6 Objects 9\n 7 Communities 10\n 8 Routing Trees 11\n 8.1 Routing Tree Definition . . . . . . . 12\n 8.2 The Open Community Routing Tree . . . . . 12\n 8.3 Routing Tree Location . . . . . . . 13\n 8.4 Example Routing Trees . . . . . . . 13\n 8.5 Use of Routing Trees to look up Information . . 13\n 9 Routing Tree Selection 14\n 9.1 Routing Tree Order . .","scope_keywords":["1801","algorithm","attribute","attributes","authentication","delivery","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null},{"body":"IETF","designation":"RFC 1837","folder":"IETF/RFC-1837","source":"IETF/RFC-1837/RFC-1837.txt","version":null},{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2293","folder":"IETF/RFC-2293","source":"IETF/RFC-2293/RFC-2293.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1801 Network Working Group S. Kille\nRequest for Comments: 1801 ISODE Consortium\nCategory: Experimental June 1995\n\n X.400-MHS use of the X.500 Directory to support X.400-MHS Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Introduction 3\n 2 Goals 3\n 3 Approach 5\n 4 Direct vs Indirect Connection 6\n 5 X.400 and RFC 822 8\n 6 Objects 9\n 7 Communities 10\n 8 Routing Trees 11\n 8.1 Routing Tree Definition . . . . . . . 12\n 8.2 The Open Community Routing Tree . . . . . 12\n 8.3 Routing Tree Location . . . . . . . 13\n 8.4 Example Routing Trees . . . . . . . 13\n 8.5 Use of Routing Trees to look up Information . . 13\n 9 Routing Tree Selection 14\n 9.1 Routing Tree Order . . 1801 algorithm attribute attributes authentication delivery path policy nested-reference unchanged"},{"id":"IETF RFC 1859","type":"specification","body":"IETF","designation":"RFC 1859","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1859.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1859.txt","https://www.rfc-editor.org/rfc/rfc1859.pdf"],"folder":"IETF/RFC-1859","files":{"txt":{"path":"standards/IETF/RFC-1859/RFC-1859.txt","sha256":"8e25cfa5f847014ffb0095c30b92e342f4a2b3f182314b69676c5e4ed7549a9d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Pouffary\nRequest For Comments: 1859 Digital Equipment Corporation\nCategory: Informational October 1995\n\n ISO Transport Class 2 Non-use of Explicit Flow Control over TCP\n RFC1006 extension\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction - General recommendations.......................2\n 2. The protocol.................................................3\n 2.1 TCP service as a Network Service - The Primitives...........3\n 2.2 Connection Establishment....................................4\n 2.3 Data Transfer...............................................5\n 2.4 Connection Release..........................................6\n 3. Packet Format................................................6\n 4. DIGITAL D","scope_keywords":["1859"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null}],"search_text":"IETF RFC 1859 Network Working Group Y. Pouffary\nRequest For Comments: 1859 Digital Equipment Corporation\nCategory: Informational October 1995\n\n ISO Transport Class 2 Non-use of Explicit Flow Control over TCP\n RFC1006 extension\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction - General recommendations.......................2\n 2. The protocol.................................................3\n 2.1 TCP service as a Network Service - The Primitives...........3\n 2.2 Connection Establishment....................................4\n 2.3 Data Transfer...............................................5\n 2.4 Connection Release..........................................6\n 3. Packet Format................................................6\n 4. DIGITAL D 1859 nested-reference unchanged"},{"id":"IETF RFC 1888","type":"specification","body":"IETF","designation":"RFC 1888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1888.txt","https://www.rfc-editor.org/rfc/rfc1888.pdf"],"folder":"IETF/RFC-1888","files":{"txt":{"path":"standards/IETF/RFC-1888/RFC-1888.txt","sha256":"4e9ff13ba6b68a444d0735c79bbcbf951b2f06c61dc8dba94ef0c40e15607cc5"}},"tags":["nested-reference","unchanged"],"summary":"This document recommends that network implementors who have planned\n or deployed an OSI NSAP addressing plan, and who wish to deploy or\n transition to IPv6, should redesign a native IPv6 addressing plan to\n meet their needs. However, it also defines a set of mechanisms for\n the support of OSI NSAP addressing in an IPv6 network. These\n mechanisms are the ones that MUST be used if such support is\n required. This document also defines a mapping of IPv6 addresses\n within the OSI address format, should this be required.","scope_keywords":["1888","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1888 This document recommends that network implementors who have planned\n or deployed an OSI NSAP addressing plan, and who wish to deploy or\n transition to IPv6, should redesign a native IPv6 addressing plan to\n meet their needs. However, it also defines a set of mechanisms for\n the support of OSI NSAP addressing in an IPv6 network. These\n mechanisms are the ones that MUST be used if such support is\n required. This document also defines a mapping of IPv6 addresses\n within the OSI address format, should this be required. 1888 profile nested-reference unchanged"},{"id":"IETF RFC 2126","type":"specification","body":"IETF","designation":"RFC 2126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2126.txt","https://www.rfc-editor.org/rfc/rfc2126.pdf"],"folder":"IETF/RFC-2126","files":{"txt":{"path":"standards/IETF/RFC-2126/RFC-2126.txt","sha256":"6fc338c5830fa60f31541cc43d5e1c28f725a42985fa41ae75932dd56a6f1a81"}},"tags":["nested-reference","unchanged"],"summary":"This document is a revision to STD35, RFC1006 written by Marshall T.\n Rose and Dwight E. Cass. Since the release of RFC1006 in May 1987,\n much experience has been gained in using ISO transport services on\n top of TCP. This document refines the protocol and will eventually\n supersede RFC1006.\n\n This document describes the mechanism to allow ISO Transport Services\n to run over TCP over IPv4 or IPv6. It also defines a number of new\n features, which are not provided in RFC1006.\n\n The goal of this version is to minimise the number of changes to\n RFC1006 and ISO 8073 transport protocol definitions, while maximising\n performance, extending its applicability and protecting the installed\n base of RFC1006 users.","scope_keywords":["2126","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2556","folder":"IETF/RFC-2556","source":"IETF/RFC-2556/RFC-2556.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 2126 This document is a revision to STD35, RFC1006 written by Marshall T.\n Rose and Dwight E. Cass. Since the release of RFC1006 in May 1987,\n much experience has been gained in using ISO transport services on\n top of TCP. This document refines the protocol and will eventually\n supersede RFC1006.\n\n This document describes the mechanism to allow ISO Transport Services\n to run over TCP over IPv4 or IPv6. It also defines a number of new\n features, which are not provided in RFC1006.\n\n The goal of this version is to minimise the number of changes to\n RFC1006 and ISO 8073 transport protocol definitions, while maximising\n performance, extending its applicability and protecting the installed\n base of RFC1006 users. 2126 key presentation nested-reference unchanged"},{"id":"IETF RFC 2885","type":"specification","body":"IETF","designation":"RFC 2885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2885.txt","https://www.rfc-editor.org/rfc/rfc2885.pdf"],"folder":"IETF/RFC-2885","files":{"txt":{"path":"standards/IETF/RFC-2885/RFC-2885.txt","sha256":"09c48aec2eca47ce965089f04d31c521bb162d38a35d41aaa99a4a6ead98837e"}},"tags":["nested-reference","unchanged"],"summary":"This document is common text with Recommendation H.248 as\n redetermined in Geneva, February 2000. It must be read in\n conjunction with the Megaco Errata, RFC 2886. A merged document\n presenting the Megaco protocol with the Errata incorporated will be\n available shortly.\n\n The protocol presented in this document meets the requirements for a\n media gateway control protocol as presented in RFC 2805.\n\nCuervo, et al. Standards Track [Page 1]\n\f\nRFC 2885 Megaco Protocol August 2000","scope_keywords":["2885","attribute","attributes","audit"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2886","folder":"IETF/RFC-2886","source":"IETF/RFC-2886/RFC-2886.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null}],"search_text":"IETF RFC 2885 This document is common text with Recommendation H.248 as\n redetermined in Geneva, February 2000. It must be read in\n conjunction with the Megaco Errata, RFC 2886. A merged document\n presenting the Megaco protocol with the Errata incorporated will be\n available shortly.\n\n The protocol presented in this document meets the requirements for a\n media gateway control protocol as presented in RFC 2805.\n\nCuervo, et al. Standards Track [Page 1]\n\f\nRFC 2885 Megaco Protocol August 2000 2885 attribute attributes audit nested-reference unchanged"},{"id":"IETF RFC 3015","type":"specification","body":"IETF","designation":"RFC 3015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3015.txt","https://www.rfc-editor.org/rfc/rfc3015.pdf"],"folder":"IETF/RFC-3015","files":{"txt":{"path":"standards/IETF/RFC-3015/RFC-3015.txt","sha256":"a45a4db137b1f23bb5fab2cfcc527dee071529b2aeb33013e78deffd379ecef9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the protocol used between elements of a\n physically decomposed multimedia gateway, i.e. a Media Gateway and a\n Media Gateway Controller. The document is common text with ITU-T\n Recommendation H.248 and is a result of applying the changes in RFC\n 2886 to the text of RFC 2885.\n\n The protocol presented in this document meets the requirements for a\n media gateway control protocol as presented in RFC 2805.\n\nCuervo, et al. Standards Track [Page 1]\n\f\nRFC 3015 Megaco Protocol Version 1.0 November 2000","scope_keywords":["3015","attribute","attributes","audit"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null}],"search_text":"IETF RFC 3015 This document defines the protocol used between elements of a\n physically decomposed multimedia gateway, i.e. a Media Gateway and a\n Media Gateway Controller. The document is common text with ITU-T\n Recommendation H.248 and is a result of applying the changes in RFC\n 2886 to the text of RFC 2885.\n\n The protocol presented in this document meets the requirements for a\n media gateway control protocol as presented in RFC 2805.\n\nCuervo, et al. Standards Track [Page 1]\n\f\nRFC 3015 Megaco Protocol Version 1.0 November 2000 3015 attribute attributes audit nested-reference unchanged"},{"id":"IETF RFC 3525","type":"specification","body":"IETF","designation":"RFC 3525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3525.txt","https://www.rfc-editor.org/rfc/rfc3525.pdf"],"folder":"IETF/RFC-3525","files":{"txt":{"path":"standards/IETF/RFC-3525/RFC-3525.txt","sha256":"571a351c7271db0ab946a5f5450396ab7f9e82b44b0db463162ae5219438a6a4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the protocol used between elements of a\n physically decomposed multimedia gateway, i.e., a Media Gateway and a\n Media Gateway Controller. The protocol presented in this document\n meets the requirements for a media gateway control protocol as\n presented in RFC 2805.\n\n This document replaces RFC 3015. It is the result of continued\n cooperation between the IETF Megaco Working Group and ITU-T Study\n Group 16. It incorporates the original text of RFC 3015, modified by\n corrections and clarifications discussed on the Megaco\n E-mail list and incorporated into the Study Group 16 Implementor's\n Guide for Recommendation H.248. The present version of this document\n underwent ITU-T Last Call as Recommendation H.248 Amendment 1.\n Because of ITU-T renumbering, it was published by the ITU-T as\n Recommendation H.248.1 (03/2002), Gateway Control Protocol Version 1.\n\n Users of this s","scope_keywords":["3525","attribute","attributes","audit","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5125","folder":"IETF/RFC-5125","source":"IETF/RFC-5125/RFC-5125.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null}],"search_text":"IETF RFC 3525 This document defines the protocol used between elements of a\n physically decomposed multimedia gateway, i.e., a Media Gateway and a\n Media Gateway Controller. The protocol presented in this document\n meets the requirements for a media gateway control protocol as\n presented in RFC 2805.\n\n This document replaces RFC 3015. It is the result of continued\n cooperation between the IETF Megaco Working Group and ITU-T Study\n Group 16. It incorporates the original text of RFC 3015, modified by\n corrections and clarifications discussed on the Megaco\n E-mail list and incorporated into the Study Group 16 Implementor's\n Guide for Recommendation H.248. The present version of this document\n underwent ITU-T Last Call as Recommendation H.248 Amendment 1.\n Because of ITU-T renumbering, it was published by the ITU-T as\n Recommendation H.248.1 (03/2002), Gateway Control Protocol Version 1.\n\n Users of this s 3525 attribute attributes audit http key nested-reference unchanged"},{"id":"IETF RFC 1219","type":"specification","body":"IETF","designation":"RFC 1219","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1219.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1219.txt","https://www.rfc-editor.org/rfc/rfc1219.pdf"],"folder":"IETF/RFC-1219","files":{"txt":{"path":"standards/IETF/RFC-1219/RFC-1219.txt","sha256":"d6a0e0fc714177302bb052a7bb82eb18ddb95510a9df4f7314e9f4816436da32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Tsuchiya\nRequest for Comments: 1219 Bellcore\n April 1991\n\n On the Assignment of Subnet Numbers\n\nStatus Of This Memo\n\n This memo suggests a new procedure for assigning subnet numbers. Use\n of this assignment technique within a network would be a purely local\n matter, and would not effect other networks. Therefore, the use of\n these procedures is entirely discretionary.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nOverview\n\n RFC-950 [2] specifies a procedure for subnetting Internet addresses\n using a bit-mask. While RFC-950 allows the \"ones\" in the subnet mask\n to be non-contiguous, RFC-950 recommends that 1) they be contiguous,\n and 2) that they occupy the most significant bits of the \"host\" part\n of the internet address.\n\n RFC-950 did not specify whether different","scope_keywords":["1219","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3531","folder":"IETF/RFC-3531","source":"IETF/RFC-3531/RFC-3531.txt","version":null}],"search_text":"IETF RFC 1219 Network Working Group P. Tsuchiya\nRequest for Comments: 1219 Bellcore\n April 1991\n\n On the Assignment of Subnet Numbers\n\nStatus Of This Memo\n\n This memo suggests a new procedure for assigning subnet numbers. Use\n of this assignment technique within a network would be a purely local\n matter, and would not effect other networks. Therefore, the use of\n these procedures is entirely discretionary.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nOverview\n\n RFC-950 [2] specifies a procedure for subnetting Internet addresses\n using a bit-mask. While RFC-950 allows the \"ones\" in the subnet mask\n to be non-contiguous, RFC-950 recommends that 1) they be contiguous,\n and 2) that they occupy the most significant bits of the \"host\" part\n of the internet address.\n\n RFC-950 did not specify whether different 1219 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1254","type":"specification","body":"IETF","designation":"RFC 1254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1254.txt","https://www.rfc-editor.org/rfc/rfc1254.pdf"],"folder":"IETF/RFC-1254","files":{"txt":{"path":"standards/IETF/RFC-1254/RFC-1254.txt","sha256":"1f00b3e937099e69e6bfade6d51f712cdf3299fdf7ccff39ae196ef9c6b60a96"}},"tags":["nested-reference","unchanged"],"summary":"The growth of network intensive Internet applications has made\n gateway congestion control a high priority. The IETF Performance and\n Congestion Control Working Group surveyed and reviewed gateway\n congestion control and avoidance approaches. The purpose of this\n paper is to present our review of the congestion control approaches,\n as a way of encouraging new discussion and experimentation. Included\n in the survey are Source Quench, Random Drop, Congestion Indication\n (DEC Bit), and Fair Queueing. The task remains for Internet\n implementors to determine and agree on the most effective mechanisms\n for controlling gateway congestion.\n\n1. Introduction\n\n Internet users regularly encounter congestion, often in mild forms.\n However, severe congestion episodes have been reported also; and\n gateway congestion remains an obstacle for Internet applications such\n as scientific supercomputing data t","scope_keywords":["1254","algorithm","algorithms","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 1254 The growth of network intensive Internet applications has made\n gateway congestion control a high priority. The IETF Performance and\n Congestion Control Working Group surveyed and reviewed gateway\n congestion control and avoidance approaches. The purpose of this\n paper is to present our review of the congestion control approaches,\n as a way of encouraging new discussion and experimentation. Included\n in the survey are Source Quench, Random Drop, Congestion Indication\n (DEC Bit), and Fair Queueing. The task remains for Internet\n implementors to determine and agree on the most effective mechanisms\n for controlling gateway congestion.\n\n1. Introduction\n\n Internet users regularly encounter congestion, often in mild forms.\n However, severe congestion episodes have been reported also; and\n gateway congestion remains an obstacle for Internet applications such\n as scientific supercomputing data t 1254 algorithm algorithms management path policies policy nested-reference unchanged"},{"id":"IETF RFC 1256","type":"specification","body":"IETF","designation":"RFC 1256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1256.txt","https://www.rfc-editor.org/rfc/rfc1256.pdf"],"folder":"IETF/RFC-1256","files":{"txt":{"path":"standards/IETF/RFC-1256/RFC-1256.txt","sha256":"9cafb5adc1acbe46f9136de82e8d3f82da4c87602c97a4fd81c1482e40d8e831"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension of the Internet Control Message\n Protocol (ICMP) to enable hosts attached to multicast or broadcast\n networks to discover the IP addresses of their neighboring routers.","scope_keywords":["1256","qualified","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1370","folder":"IETF/RFC-1370","source":"IETF/RFC-1370/RFC-1370.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1788","folder":"IETF/RFC-1788","source":"IETF/RFC-1788/RFC-1788.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1900","folder":"IETF/RFC-1900","source":"IETF/RFC-1900/RFC-1900.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2281","folder":"IETF/RFC-2281","source":"IETF/RFC-2281/RFC-2281.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 1256 This document specifies an extension of the Internet Control Message\n Protocol (ICMP) to enable hosts attached to multicast or broadcast\n networks to discover the IP addresses of their neighboring routers. 1256 qualified subject validation nested-reference unchanged"},{"id":"IETF RFC 1349","type":"specification","body":"IETF","designation":"RFC 1349","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1349.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1349.txt","https://www.rfc-editor.org/rfc/rfc1349.pdf"],"folder":"IETF/RFC-1349","files":{"txt":{"path":"standards/IETF/RFC-1349/RFC-1349.txt","sha256":"43f56e6e57dd441f48765d55e227d2303447458badacc9b8e442e9481d5f05d9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Almquist\nRequest for Comments: 1349 Consultant\nUpdates: RFCs 1248, 1247, 1195, July 1992\n 1123, 1122, 1060, 791\n\n Type of Service in the Internet Protocol Suite\n\nStatus of This Memo\n\n This document specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nSummary\n\n This memo changes and clarifies some aspects of the semantics of the\n Type of Service octet in the Internet Protocol (IP) header. The\n handling of IP Type of Service by both hosts and routers is specified\n in some detail.\n\n This memo defines a new TOS value for requesting that the network\n minimize the monetary cost of transmitting a datagram. A number of\n","scope_keywords":["1349","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null}],"search_text":"IETF RFC 1349 Network Working Group P. Almquist\nRequest for Comments: 1349 Consultant\nUpdates: RFCs 1248, 1247, 1195, July 1992\n 1123, 1122, 1060, 791\n\n Type of Service in the Internet Protocol Suite\n\nStatus of This Memo\n\n This document specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nSummary\n\n This memo changes and clarifies some aspects of the semantics of the\n Type of Service octet in the Internet Protocol (IP) header. The\n handling of IP Type of Service by both hosts and routers is specified\n in some detail.\n\n This memo defines a new TOS value for requesting that the network\n minimize the monetary cost of transmitting a datagram. A number of\n 1349 path nested-reference unchanged"},{"id":"IETF RFC 1547","type":"specification","body":"IETF","designation":"RFC 1547","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1547.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1547.txt","https://www.rfc-editor.org/rfc/rfc1547.pdf"],"folder":"IETF/RFC-1547","files":{"txt":{"path":"standards/IETF/RFC-1547/RFC-1547.txt","sha256":"a36f3f276793c6086bbf1708638d4d30ccc10518be4aa503df75a543e8ebfed8"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the evaluation criteria for an Internet\n Standard Data Link Layer protocol to be used with point-to-point\n links. Although many industry standard protocols and ad hoc\n protocols already exist for the data link layer, none are both\n complete and sufficiently versatile to be accepted as an Internet\n Standard. In preparation to designing such a protocol, the features\n necessary to qualify a point-to-point protocol as an Internet\n Standard are discussed in detail. An analysis of the strengths and\n weaknesses of several existing protocols on the basis of these\n requirements demonstrates the failure of each to address key issues.\n\n Historical Note: This was the design requirements document dated\n June 1989, which was followed for RFC-1134 through the present.\n It is now published for completeness and future guidance.\n\nPerkins [Page 1]\n\f\nRFC 1547 Point-to-Point Protocol ","scope_keywords":["1547","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1548","folder":"IETF/RFC-1548","source":"IETF/RFC-1548/RFC-1548.txt","version":null},{"body":"IETF","designation":"RFC 1661","folder":"IETF/RFC-1661","source":"IETF/RFC-1661/RFC-1661.txt","version":null}],"search_text":"IETF RFC 1547 This document discusses the evaluation criteria for an Internet\n Standard Data Link Layer protocol to be used with point-to-point\n links. Although many industry standard protocols and ad hoc\n protocols already exist for the data link layer, none are both\n complete and sufficiently versatile to be accepted as an Internet\n Standard. In preparation to designing such a protocol, the features\n necessary to qualify a point-to-point protocol as an Internet\n Standard are discussed in detail. An analysis of the strengths and\n weaknesses of several existing protocols on the basis of these\n requirements demonstrates the failure of each to address key issues.\n\n Historical Note: This was the design requirements document dated\n June 1989, which was followed for RFC-1134 through the present.\n It is now published for completeness and future guidance.\n\nPerkins [Page 1]\n\f\nRFC 1547 Point-to-Point Protocol  1547 key nested-reference unchanged"},{"id":"IETF RFC 1932","type":"specification","body":"IETF","designation":"RFC 1932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1932.txt","https://www.rfc-editor.org/rfc/rfc1932.pdf"],"folder":"IETF/RFC-1932","files":{"txt":{"path":"standards/IETF/RFC-1932/RFC-1932.txt","sha256":"f8a424ce400b7dff374389a811122a4b44c1bc6bd69dceb19c8d9f47258a28b5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Cole\nRequest for Comments: 1932 D. Shur\nCategory: Informational AT&T Bell Laboratories\n C. Villamizar\n ANS\n April 1996\n\n IP over ATM: A Framework Document\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n Abstract\n\n The discussions of the IP over ATM working group over the last\n several years have produced a diverse set of proposals, some of which\n are no longer under active consideration. A categorization is\n provided for the purpose of focusing discussion on the various\n proposals for IP over ATM deemed of primary interest by the IP over\n ATM working group. The intent of this framework is to help clarify\n the differences between proposals and identify common features in\n order to promote convergence to a smaller and more mutua","scope_keywords":["1932","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null}],"search_text":"IETF RFC 1932 Network Working Group R. Cole\nRequest for Comments: 1932 D. Shur\nCategory: Informational AT&T Bell Laboratories\n C. Villamizar\n ANS\n April 1996\n\n IP over ATM: A Framework Document\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n Abstract\n\n The discussions of the IP over ATM working group over the last\n several years have produced a diverse set of proposals, some of which\n are no longer under active consideration. A categorization is\n provided for the purpose of focusing discussion on the various\n proposals for IP over ATM deemed of primary interest by the IP over\n ATM working group. The intent of this framework is to help clarify\n the differences between proposals and identify common features in\n order to promote convergence to a smaller and more mutua 1932 management path nested-reference unchanged"},{"id":"IETF RFC 2080","type":"specification","body":"IETF","designation":"RFC 2080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2080.txt","https://www.rfc-editor.org/rfc/rfc2080.pdf"],"folder":"IETF/RFC-2080","files":{"txt":{"path":"standards/IETF/RFC-2080/RFC-2080.txt","sha256":"cffb9855006db5a0533cea6cb43046d9b8aaebf552c028d8f6cfe10637355720"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a routing protocol for an IPv6 internet. It\n is based on protocols and algorithms currently in wide use in the\n IPv4 Internet.\n\n This specification represents the minimum change to the Routing\n Information Protocol (RIP), as specified in RFC 1058 [1] and RFC 1723\n [2], necessary for operation over IPv6 [3].\n\nAcknowledgements\n\n This document is a modified version of RFC 1058, written by Chuck\n Hedrick [1]. The modifications reflect RIP-2 and IPv6 enhancements,\n but the original wording is his.\n\n We'd like to thank Dennis Ferguson and Thomas Narten for their input.","scope_keywords":["2080","algorithm","algorithms","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2546","folder":"IETF/RFC-2546","source":"IETF/RFC-2546/RFC-2546.txt","version":null},{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null}],"search_text":"IETF RFC 2080 This document specifies a routing protocol for an IPv6 internet. It\n is based on protocols and algorithms currently in wide use in the\n IPv4 Internet.\n\n This specification represents the minimum change to the Routing\n Information Protocol (RIP), as specified in RFC 1058 [1] and RFC 1723\n [2], necessary for operation over IPv6 [3].\n\nAcknowledgements\n\n This document is a modified version of RFC 1058, written by Chuck\n Hedrick [1]. The modifications reflect RIP-2 and IPv6 enhancements,\n but the original wording is his.\n\n We'd like to thank Dennis Ferguson and Thomas Narten for their input. 2080 algorithm algorithms path presentation nested-reference unchanged"},{"id":"IETF RFC 2453","type":"specification","body":"IETF","designation":"RFC 2453","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2453.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2453.txt","https://www.rfc-editor.org/rfc/rfc2453.pdf"],"folder":"IETF/RFC-2453","files":{"txt":{"path":"standards/IETF/RFC-2453/RFC-2453.txt","sha256":"0ea7c77b8883220c13003fe0cc31ee628478864dac5919aada0497bd9e9e2127"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1], to expand the amount of useful\n information carried in RIP messages and to add a measure of security.\n\n A companion document will define the SNMP MIB objects for RIP-2 [2].\n An additional document will define cryptographic security\n improvements for RIP-2 [3].\n\nAcknowledgements\n\n I would like to thank the IETF RIP Working Group for their help in\n improving the RIP-2 protocol. Much of the text for the background\n discussions about distance vector protocols and some of the\n descriptions of the operation of RIP were taken from \"Routing\n Information Protocol\" by C. Hedrick [1]. Some of the final editing on\n the document was done by Scott Bradner.\n\nMalkin Standards Track [Page 1]\n\f\nRFC 2453 RIP Version 2 November 1998","scope_keywords":["2453","algorithm","algorithms","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null}],"search_text":"IETF RFC 2453 This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1], to expand the amount of useful\n information carried in RIP messages and to add a measure of security.\n\n A companion document will define the SNMP MIB objects for RIP-2 [2].\n An additional document will define cryptographic security\n improvements for RIP-2 [3].\n\nAcknowledgements\n\n I would like to thank the IETF RIP Working Group for their help in\n improving the RIP-2 protocol. Much of the text for the background\n discussions about distance vector protocols and some of the\n descriptions of the operation of RIP were taken from \"Routing\n Information Protocol\" by C. Hedrick [1]. Some of the final editing on\n the document was done by Scott Bradner.\n\nMalkin Standards Track [Page 1]\n\f\nRFC 2453 RIP Version 2 November 1998 2453 algorithm algorithms authentication management nested-reference unchanged"},{"id":"IETF RFC 1032","type":"specification","body":"IETF","designation":"RFC 1032","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1032.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1032.txt","https://www.rfc-editor.org/rfc/rfc1032.pdf"],"folder":"IETF/RFC-1032","files":{"txt":{"path":"standards/IETF/RFC-1032/RFC-1032.txt","sha256":"ba6605bbfaf1f1b134e6cc9d2c29403c00009e9d290c4d4e0973699c1eefbc60"}},"tags":["nested-reference","unchanged"],"summary":"for which it was intended.","scope_keywords":["1032","management","policies","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1464","folder":"IETF/RFC-1464","source":"IETF/RFC-1464/RFC-1464.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null}],"search_text":"IETF RFC 1032 for which it was intended. 1032 management policies policy registered nested-reference unchanged"},{"id":"IETF RFC 1081","type":"specification","body":"IETF","designation":"RFC 1081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1081.txt","https://www.rfc-editor.org/rfc/rfc1081.pdf"],"folder":"IETF/RFC-1081","files":{"txt":{"path":"standards/IETF/RFC-1081/RFC-1081.txt","sha256":"786f60c050ae6ca99f6de9fc855d269d102635b5adf58ac267dbf6a1950cfc58"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1081 TWG\n November 1988\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This memo suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\n This memo is based on RFC 918 (since revised as RFC 937). Although\n similar in form to the original Post Office Protocol (POP) proposed\n for the Internet community, the protocol discussed in this memo is\n similar in spirit to the ideas investigated by the MZnet project at\n the University of California, Irvine.\n\n Further, substantial work was done on examining POP in a PC-based\n environment. This work, which resulted in additional functionality\n in this protocol, was performed by the ACIS ","scope_keywords":["1081","authorization","crl","delivery","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null}],"search_text":"IETF RFC 1081 Network Working Group M. Rose\nRequest for Comments: 1081 TWG\n November 1988\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This memo suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\n This memo is based on RFC 918 (since revised as RFC 937). Although\n similar in form to the original Post Office Protocol (POP) proposed\n for the Internet community, the protocol discussed in this memo is\n similar in spirit to the ideas investigated by the MZnet project at\n the University of California, Irvine.\n\n Further, substantial work was done on examining POP in a PC-based\n environment. This work, which resulted in additional functionality\n in this protocol, was performed by the ACIS  1081 authorization crl delivery key trust nested-reference unchanged"},{"id":"IETF RFC 1091","type":"specification","body":"IETF","designation":"RFC 1091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1091.txt","https://www.rfc-editor.org/rfc/rfc1091.pdf"],"folder":"IETF/RFC-1091","files":{"txt":{"path":"standards/IETF/RFC-1091/RFC-1091.txt","sha256":"e73e3b626216dbb48421cd0463ad0a9cad70c9ea6840d632797e3b1f3b711dcb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. VanBokkelen\nRequest for Comments: 1091 FTP Software, Inc.\nObsoletes: RFC 930 February 1989\n\n Telnet Terminal-Type Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that exchange terminal type information within the\n Telnet protocol are expected to adopt and implement this standard.\n\n This standard supersedes RFC 930. A change is made to permit cycling\n through a list of possible terminal types and selecting the most\n appropriate.\n\n Distribution of this memo is unlimited.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation.\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send terminal type information.\n\n IAC DO TERMINAL-TYPE\n\n Sender is willing to receive terminal type information i","scope_keywords":["1091"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1408","folder":"IETF/RFC-1408","source":"IETF/RFC-1408/RFC-1408.txt","version":null},{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1646","folder":"IETF/RFC-1646","source":"IETF/RFC-1646/RFC-1646.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1091 Network Working Group J. VanBokkelen\nRequest for Comments: 1091 FTP Software, Inc.\nObsoletes: RFC 930 February 1989\n\n Telnet Terminal-Type Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that exchange terminal type information within the\n Telnet protocol are expected to adopt and implement this standard.\n\n This standard supersedes RFC 930. A change is made to permit cycling\n through a list of possible terminal types and selecting the most\n appropriate.\n\n Distribution of this memo is unlimited.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation.\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send terminal type information.\n\n IAC DO TERMINAL-TYPE\n\n Sender is willing to receive terminal type information i 1091 nested-reference unchanged"},{"id":"IETF RFC 1101","type":"specification","body":"IETF","designation":"RFC 1101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1101.txt","https://www.rfc-editor.org/rfc/rfc1101.pdf"],"folder":"IETF/RFC-1101","files":{"txt":{"path":"standards/IETF/RFC-1101/RFC-1101.txt","sha256":"972d509dcb4cb6cc2a41315b8a14a2bc520d4098cd318cb8d170de37017e26d3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 1101 ISI\nUpdates: RFCs 1034, 1035 April 1989\n\n DNS Encoding of Network Names and Other Types\n\n1. STATUS OF THIS MEMO\n\n This RFC proposes two extensions to the Domain Name System:\n\n - A specific method for entering and retrieving RRs which map\n between network names and numbers.\n\n - Ideas for a general method for describing mappings between\n arbitrary identifiers and numbers.\n\n The method for mapping between network names and addresses is a\n proposed standard, the ideas for a general method are experimental.\n\n This RFC assumes that the reader is familiar with the DNS [RFC 1034,\n RFC 1035] and its use. The data shown is for pedagogical use and\n does not necessarily reflect the real Internet.\n\n Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n The DNS is extensible and can be used for a virtually unlimited\n number of data t","scope_keywords":["1101","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1279","folder":"IETF/RFC-1279","source":"IETF/RFC-1279/RFC-1279.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null},{"body":"IETF","designation":"RFC 1464","folder":"IETF/RFC-1464","source":"IETF/RFC-1464/RFC-1464.txt","version":null},{"body":"IETF","designation":"RFC 1876","folder":"IETF/RFC-1876","source":"IETF/RFC-1876/RFC-1876.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null}],"search_text":"IETF RFC 1101 Network Working Group P. Mockapetris\nRequest for Comments: 1101 ISI\nUpdates: RFCs 1034, 1035 April 1989\n\n DNS Encoding of Network Names and Other Types\n\n1. STATUS OF THIS MEMO\n\n This RFC proposes two extensions to the Domain Name System:\n\n - A specific method for entering and retrieving RRs which map\n between network names and numbers.\n\n - Ideas for a general method for describing mappings between\n arbitrary identifiers and numbers.\n\n The method for mapping between network names and addresses is a\n proposed standard, the ideas for a general method are experimental.\n\n This RFC assumes that the reader is familiar with the DNS [RFC 1034,\n RFC 1035] and its use. The data shown is for pedagogical use and\n does not necessarily reflect the real Internet.\n\n Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n The DNS is extensible and can be used for a virtually unlimited\n number of data t 1101 presentation nested-reference unchanged"},{"id":"IETF RFC 1131","type":"specification","body":"IETF","designation":"RFC 1131","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1131.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1131.txt","https://www.rfc-editor.org/rfc/rfc1131.pdf"],"folder":"IETF/RFC-1131","files":{"pdf":{"path":"standards/IETF/RFC-1131/RFC-1131.pdf","sha256":"36455c2cd97161622f6ac0f3076665f51f235eae0c3459604d395317ae743dcc"},"txt":{"path":"standards/IETF/RFC-1131/RFC-1131.txt","sha256":"c310f586e28d7afa0037266ad504fd98b11aa367e19421a903aa9559fd3c96c9"}},"tags":["nested-reference","unchanged"],"summary":"RFC-1131 \"The OSPF Specification\"\n\n is available only in PostScript form in the file\n\n RFC1131.PS\n\nTo obtain this file via the NIC's automatic mail server SERVICE, use\nthe Subject line: SEND RFC:RFCnnnn.PS (where nnnn is the number of\nthe RFC you wish to obtain).","scope_keywords":["1131","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1245","folder":"IETF/RFC-1245","source":"IETF/RFC-1245/RFC-1245.txt","version":null},{"body":"IETF","designation":"RFC 1246","folder":"IETF/RFC-1246","source":"IETF/RFC-1246/RFC-1246.txt","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null}],"search_text":"IETF RFC 1131 RFC-1131 \"The OSPF Specification\"\n\n is available only in PostScript form in the file\n\n RFC1131.PS\n\nTo obtain this file via the NIC's automatic mail server SERVICE, use\nthe Subject line: SEND RFC:RFCnnnn.PS (where nnnn is the number of\nthe RFC you wish to obtain). 1131 subject nested-reference unchanged"},{"id":"IETF RFC 1134","type":"specification","body":"IETF","designation":"RFC 1134","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1134.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1134.txt","https://www.rfc-editor.org/rfc/rfc1134.pdf"],"folder":"IETF/RFC-1134","files":{"txt":{"path":"standards/IETF/RFC-1134/RFC-1134.txt","sha256":"9f26d2ae94377ac4d2abd29128ca857b3ff7218d48f4c249686abf6fe1b4c318"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of three\n parts:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. An extensible Link Control Protocol (LCP).\n\n 3. A family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n This document defines the encapsulation scheme, the basic LCP, and an\n NCP for establishing and configuring the Internet Protocol (IP)\n (called the IP Control Protocol, IPCP).\n\n The options and facilities used by the LCP and the IPCP are defined\n in separate documents. Control protocols for configuring and\n utilizing other network-layer protocols besides IP (e.g., DECNET,\n OSI) are expected to be developed as needed.\n\n1. Introduction","scope_keywords":["1134","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null}],"search_text":"IETF RFC 1134 The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of three\n parts:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. An extensible Link Control Protocol (LCP).\n\n 3. A family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n This document defines the encapsulation scheme, the basic LCP, and an\n NCP for establishing and configuring the Internet Protocol (IP)\n (called the IP Control Protocol, IPCP).\n\n The options and facilities used by the LCP and the IPCP are defined\n in separate documents. Control protocols for configuring and\n utilizing other network-layer protocols besides IP (e.g., DECNET,\n OSI) are expected to be developed as needed.\n\n1. Introduction 1134 management nested-reference unchanged"},{"id":"IETF RFC 1207","type":"specification","body":"IETF","designation":"RFC 1207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1207.txt","https://www.rfc-editor.org/rfc/rfc1207.pdf"],"folder":"IETF/RFC-1207","files":{"txt":{"path":"standards/IETF/RFC-1207/RFC-1207.txt","sha256":"e44cb21a92822365c8fa57ddd3cd560172023701a392750a564bb036bb1a9309"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1207 FTP Software, Inc.\nFYI: 7 A. Marine\n SRI\n J. Reynolds\n ISI\n February 1991\n\n FYI on Questions and Answers\n Answers to Commonly asked \"Experienced Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.................................................. 1\n 2. Acknowledgements.............................................. 3\n 3. Questions about the Internet.................................. 3\n 4. Questions About Other Networ","scope_keywords":["1207","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null}],"search_text":"IETF RFC 1207 Network Working Group G. Malkin\nRequest for Comments: 1207 FTP Software, Inc.\nFYI: 7 A. Marine\n SRI\n J. Reynolds\n ISI\n February 1991\n\n FYI on Questions and Answers\n Answers to Commonly asked \"Experienced Internet User\" Questions\n\nStatus of this Memo\n\n This FYI RFC is one of two FYI's called, \"Questions and Answers\"\n (Q/A), produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). The goal is to document the most\n commonly asked questions and answers in the Internet.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.................................................. 1\n 2. Acknowledgements.............................................. 3\n 3. Questions about the Internet.................................. 3\n 4. Questions About Other Networ 1207 management nested-reference unchanged"},{"id":"IETF RFC 1014","type":"specification","body":"IETF","designation":"RFC 1014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1014.txt","https://www.rfc-editor.org/rfc/rfc1014.pdf"],"folder":"IETF/RFC-1014","files":{"txt":{"path":"standards/IETF/RFC-1014/RFC-1014.txt","sha256":"80087f90e4ad6e4ac3254216086d99ab122f9f05ea25bc1305bd45f2663e64fc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1014 June 1987\n\n XDR: External Data Representation Standard\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems, Inc., and others\n are using, one we wish to propose for the Internet's consideration.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n XDR is a standard for the description and encoding of data. It is\n useful for transferring data between different computer\n architectures, and has been used to communicate data between such\n diverse machines as the SUN WORKSTATION*, VAX*, IBM-PC*, and Cray*.\n XDR fits into the ISO presentation layer, and is roughly analogous in\n purpose to X.409, ISO Abstract Syntax Notation. The major difference\n between these two is that XDR uses implicit typing, while X.409 uses\n explicit typing.\n\n XDR uses a language to describe data formats. The language ca","scope_keywords":["1014","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1057","folder":"IETF/RFC-1057","source":"IETF/RFC-1057/RFC-1057.txt","version":null},{"body":"IETF","designation":"RFC 1094","folder":"IETF/RFC-1094","source":"IETF/RFC-1094/RFC-1094.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1790","folder":"IETF/RFC-1790","source":"IETF/RFC-1790/RFC-1790.txt","version":null},{"body":"IETF","designation":"RFC 1813","folder":"IETF/RFC-1813","source":"IETF/RFC-1813/RFC-1813.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 4506","folder":"IETF/RFC-4506","source":"IETF/RFC-4506/RFC-4506.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null}],"search_text":"IETF RFC 1014 Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1014 June 1987\n\n XDR: External Data Representation Standard\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems, Inc., and others\n are using, one we wish to propose for the Internet's consideration.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n XDR is a standard for the description and encoding of data. It is\n useful for transferring data between different computer\n architectures, and has been used to communicate data between such\n diverse machines as the SUN WORKSTATION*, VAX*, IBM-PC*, and Cray*.\n XDR fits into the ISO presentation layer, and is roughly analogous in\n purpose to X.409, ISO Abstract Syntax Notation. The major difference\n between these two is that XDR uses implicit typing, while X.409 uses\n explicit typing.\n\n XDR uses a language to describe data formats. The language ca 1014 presentation nested-reference unchanged"},{"id":"IETF RFC 1057","type":"specification","body":"IETF","designation":"RFC 1057","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1057.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1057.txt","https://www.rfc-editor.org/rfc/rfc1057.pdf"],"folder":"IETF/RFC-1057","files":{"txt":{"path":"standards/IETF/RFC-1057/RFC-1057.txt","sha256":"1afe65c5c8efa3280183191c13e42b15505789fc9cbb86cf0f5cc9a095d95960"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Sun Microsystems, Inc.\nRequest For Comments: 1057 June 1988\nObsoletes: RFC 1050\n\n RPC: Remote Procedure Call\n Protocol Specification\n Version 2\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems and others are\n using, and is one we wish to propose for the Internet's\n consideration. This memo is not an Internet standard at this time.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n This document specifies version two of the message protocol used in\n Sun's Remote Procedure Call (RPC) package. The message protocol is\n specified with the eXternal Data Representation (XDR) language [9].\n This document assumes that the reader is familiar with XDR. It does\n not attempt to justify remote procedure calls systems or describe\n their use. The paper by Birrell and Nelson [1] is recommended as an\n excellent background for the remote procedure ca","scope_keywords":["1057","authentication","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1094","folder":"IETF/RFC-1094","source":"IETF/RFC-1094/RFC-1094.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1790","folder":"IETF/RFC-1790","source":"IETF/RFC-1790/RFC-1790.txt","version":null},{"body":"IETF","designation":"RFC 1813","folder":"IETF/RFC-1813","source":"IETF/RFC-1813/RFC-1813.txt","version":null},{"body":"IETF","designation":"RFC 1981","folder":"IETF/RFC-1981","source":"IETF/RFC-1981/RFC-1981.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1057 Network Working Group Sun Microsystems, Inc.\nRequest For Comments: 1057 June 1988\nObsoletes: RFC 1050\n\n RPC: Remote Procedure Call\n Protocol Specification\n Version 2\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems and others are\n using, and is one we wish to propose for the Internet's\n consideration. This memo is not an Internet standard at this time.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n This document specifies version two of the message protocol used in\n Sun's Remote Procedure Call (RPC) package. The message protocol is\n specified with the eXternal Data Representation (XDR) language [9].\n This document assumes that the reader is familiar with XDR. It does\n not attempt to justify remote procedure calls systems or describe\n their use. The paper by Birrell and Nelson [1] is recommended as an\n excellent background for the remote procedure ca 1057 authentication policies presentation nested-reference unchanged"},{"id":"IETF RFC 1094","type":"specification","body":"IETF","designation":"RFC 1094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1094.txt","https://www.rfc-editor.org/rfc/rfc1094.pdf"],"folder":"IETF/RFC-1094","files":{"txt":{"path":"standards/IETF/RFC-1094/RFC-1094.txt","sha256":"04ffc70a4efab610faec5768d64a1adf6ab4025203424dec0b2b9982d2389c0b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1094 March 1989\n\n NFS: Network File System Protocol Specification\n\nSTATUS OF THIS MEMO\n\n This RFC describes a protocol that Sun Microsystems, Inc., and others\n are using. A new version of the protocol is under development, but\n others may benefit from the descriptions of the current protocol, and\n discussion of some of the design issues. Distribution of this memo\n is unlimited.\n\n1. INTRODUCTION\n\n The Sun Network Filesystem (NFS) protocol provides transparent remote\n access to shared files across networks. The NFS protocol is designed\n to be portable across different machines, operating systems, network\n architectures, and transport protocols. This portability is achieved\n through the use of Remote Procedure Call (RPC) primitives built on\n top of an eXternal Data Representation (XDR). Implementations\n already exist for a v","scope_keywords":["1094","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1813","folder":"IETF/RFC-1813","source":"IETF/RFC-1813/RFC-1813.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null}],"search_text":"IETF RFC 1094 Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1094 March 1989\n\n NFS: Network File System Protocol Specification\n\nSTATUS OF THIS MEMO\n\n This RFC describes a protocol that Sun Microsystems, Inc., and others\n are using. A new version of the protocol is under development, but\n others may benefit from the descriptions of the current protocol, and\n discussion of some of the design issues. Distribution of this memo\n is unlimited.\n\n1. INTRODUCTION\n\n The Sun Network Filesystem (NFS) protocol provides transparent remote\n access to shared files across networks. The NFS protocol is designed\n to be portable across different machines, operating systems, network\n architectures, and transport protocols. This portability is achieved\n through the use of Remote Procedure Call (RPC) primitives built on\n top of an eXternal Data Representation (XDR). Implementations\n already exist for a v 1094 path presentation nested-reference unchanged"},{"id":"IETF RFC 1790","type":"specification","body":"IETF","designation":"RFC 1790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1790.txt","https://www.rfc-editor.org/rfc/rfc1790.pdf"],"folder":"IETF/RFC-1790","files":{"txt":{"path":"standards/IETF/RFC-1790/RFC-1790.txt","sha256":"1e25588071cf16f54b6d4bf79a60d936426197a0eb3f82b48f44852b683594d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1790 Internet Society\nCategory: Informational April 1995\n\n An Agreement between the Internet Society\n and\n Sun Microsystems, Inc.\n in the Matter of ONC RPC and XDR Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nNote:\n\n This RFC is NOT a standard. It is an official public record of an\n agreement between SUN Microsystems and the Internet Society. The\n referenced RFC 1057 dated June 1988 (\"RFC: Remote Procedure Call\n Protocol Specification Version 2) and RFC 1014 dated June 1987 (\"XDR:\n External Data Representation Standard) are not attached to the\n document below, but are incorporated by reference.\n\nPurpose:\n\n This Request for Comments records an agreement between SUN\n Microsystems, Inc. and the Int","scope_keywords":["1790","license","presentation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2339","folder":"IETF/RFC-2339","source":"IETF/RFC-2339/RFC-2339.txt","version":null},{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 1790 Network Working Group V. Cerf\nRequest for Comments: 1790 Internet Society\nCategory: Informational April 1995\n\n An Agreement between the Internet Society\n and\n Sun Microsystems, Inc.\n in the Matter of ONC RPC and XDR Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nNote:\n\n This RFC is NOT a standard. It is an official public record of an\n agreement between SUN Microsystems and the Internet Society. The\n referenced RFC 1057 dated June 1988 (\"RFC: Remote Procedure Call\n Protocol Specification Version 2) and RFC 1014 dated June 1987 (\"XDR:\n External Data Representation Standard) are not attached to the\n document below, but are incorporated by reference.\n\nPurpose:\n\n This Request for Comments records an agreement between SUN\n Microsystems, Inc. and the Int 1790 license presentation signature subject nested-reference unchanged"},{"id":"IETF RFC 1813","type":"specification","body":"IETF","designation":"RFC 1813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1813.txt","https://www.rfc-editor.org/rfc/rfc1813.pdf"],"folder":"IETF/RFC-1813","files":{"txt":{"path":"standards/IETF/RFC-1813/RFC-1813.txt","sha256":"55118e8a8c2ee6031bede635c6d5beba10ef21fe7d23837c7145ca9c85905b20"}},"tags":["nested-reference","unchanged"],"summary":"This paper describes the NFS version 3 protocol. This paper is\n provided so that people can write compatible implementations.","scope_keywords":["1813","attribute","attributes","authentication","path","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null}],"search_text":"IETF RFC 1813 This paper describes the NFS version 3 protocol. This paper is\n provided so that people can write compatible implementations. 1813 attribute attributes authentication path policies presentation nested-reference unchanged"},{"id":"IETF RFC 1831","type":"specification","body":"IETF","designation":"RFC 1831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1831.txt","https://www.rfc-editor.org/rfc/rfc1831.pdf"],"folder":"IETF/RFC-1831","files":{"txt":{"path":"standards/IETF/RFC-1831/RFC-1831.txt","sha256":"0a467f19c479ba3e4f92ba29315fe541806fdd22522510b07db026a37e9e7350"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the ONC Remote Procedure Call (ONC RPC\n Version 2) protocol as it is currently deployed and accepted. \"ONC\"\n stands for \"Open Network Computing\".","scope_keywords":["1831","authentication","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1832","folder":"IETF/RFC-1832","source":"IETF/RFC-1832/RFC-1832.txt","version":null},{"body":"IETF","designation":"RFC 1833","folder":"IETF/RFC-1833","source":"IETF/RFC-1833/RFC-1833.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2188","folder":"IETF/RFC-2188","source":"IETF/RFC-2188/RFC-2188.txt","version":null},{"body":"IETF","designation":"RFC 2203","folder":"IETF/RFC-2203","source":"IETF/RFC-2203/RFC-2203.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null}],"search_text":"IETF RFC 1831 This document describes the ONC Remote Procedure Call (ONC RPC\n Version 2) protocol as it is currently deployed and accepted. \"ONC\"\n stands for \"Open Network Computing\". 1831 authentication presentation nested-reference unchanged"},{"id":"IETF RFC 4506","type":"specification","body":"IETF","designation":"RFC 4506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4506.txt","https://www.rfc-editor.org/rfc/rfc4506.pdf"],"folder":"IETF/RFC-4506","files":{"txt":{"path":"standards/IETF/RFC-4506/RFC-4506.txt","sha256":"fc0eb9ae3a12600589490448e32d2f748b6b734a8c1c2636a78fea752e4796fe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the External Data Representation Standard\n (XDR) protocol as it is currently deployed and accepted. This\n document obsoletes RFC 1832.\n\nEisler Standards Track [Page 1]\n\f\nRFC 4506 XDR: External Data Representation Standard May 2006","scope_keywords":["4506","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5663","folder":"IETF/RFC-5663","source":"IETF/RFC-5663/RFC-5663.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null},{"body":"IETF","designation":"RFC 8391","folder":"IETF/RFC-8391","source":"IETF/RFC-8391/RFC-8391.txt","version":null},{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null}],"search_text":"IETF RFC 4506 This document describes the External Data Representation Standard\n (XDR) protocol as it is currently deployed and accepted. This\n document obsoletes RFC 1832.\n\nEisler Standards Track [Page 1]\n\f\nRFC 4506 XDR: External Data Representation Standard May 2006 4506 presentation nested-reference unchanged"},{"id":"IETF RFC 1016","type":"specification","body":"IETF","designation":"RFC 1016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1016.txt","https://www.rfc-editor.org/rfc/rfc1016.pdf"],"folder":"IETF/RFC-1016","files":{"txt":{"path":"standards/IETF/RFC-1016/RFC-1016.txt","sha256":"a0759f651d58e185e9c14191fcff282e46f31b4c720abbc44b3817a31baee141"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Prue\nRequest for Comments: 1016 J. Postel\n ISI\n July 1987\n\n Something a Host Could Do with Source Quench:\n\n The Source Quench Introduced Delay (SQuID)\n\nStatus of this Memo\n\n This memo is intended to explore the issue of what a host could do\n with a source quench. The proposal is for each source host IP module\n to introduce some delay between datagrams sent to the same\n destination host. This is an \"crazy idea paper\" and discussion is\n essential. Distribution of this memo is unlimited.\n\nIntroduction\n\n A gateway may discard Internet datagrams if it does not have the\n buffer space needed to queue the datagrams for output to the next\n network on the route to the destination network. If a gateway\n discards a datagram, it may send a source quench message to the\n Internet source host of the datagram. A destination host may also\n send a source quench message if datagrams","scope_keywords":["1016","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1016 Network Working Group W. Prue\nRequest for Comments: 1016 J. Postel\n ISI\n July 1987\n\n Something a Host Could Do with Source Quench:\n\n The Source Quench Introduced Delay (SQuID)\n\nStatus of this Memo\n\n This memo is intended to explore the issue of what a host could do\n with a source quench. The proposal is for each source host IP module\n to introduce some delay between datagrams sent to the same\n destination host. This is an \"crazy idea paper\" and discussion is\n essential. Distribution of this memo is unlimited.\n\nIntroduction\n\n A gateway may discard Internet datagrams if it does not have the\n buffer space needed to queue the datagrams for output to the next\n network on the route to the destination network. If a gateway\n discards a datagram, it may send a source quench message to the\n Internet source host of the datagram. A destination host may also\n send a source quench message if datagrams 1016 algorithm nested-reference unchanged"},{"id":"IETF RFC 7414","type":"specification","body":"IETF","designation":"RFC 7414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7414.txt","https://www.rfc-editor.org/rfc/rfc7414.pdf"],"folder":"IETF/RFC-7414","files":{"txt":{"path":"standards/IETF/RFC-7414/RFC-7414.txt","sha256":"fe434f7a7fbd42c977e515a86cf275fb08dc50e961008375c12b91b8364d0723"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a roadmap to the Request for Comments (RFC)\n documents relating to the Internet's Transmission Control Protocol\n (TCP). This roadmap provides a brief summary of the documents\n defining TCP and various TCP extensions that have accumulated in the\n RFC series. This serves as a guide and quick reference for both TCP\n implementers and other parties who desire information contained in\n the TCP-related RFCs.\n\n This document obsoletes RFC 4614.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate","scope_keywords":["7414","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null}],"search_text":"IETF RFC 7414 This document contains a roadmap to the Request for Comments (RFC)\n documents relating to the Internet's Transmission Control Protocol\n (TCP). This roadmap provides a brief summary of the documents\n defining TCP and various TCP extensions that have accumulated in the\n RFC series. This serves as a guide and quick reference for both TCP\n implementers and other parties who desire information contained in\n the TCP-related RFCs.\n\n This document obsoletes RFC 4614.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate 7414 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 1018","type":"specification","body":"IETF","designation":"RFC 1018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1018.txt","https://www.rfc-editor.org/rfc/rfc1018.pdf"],"folder":"IETF/RFC-1018","files":{"txt":{"path":"standards/IETF/RFC-1018/RFC-1018.txt","sha256":"3234f7b2cc5f58317e143beeb75d2c496ff0d015f0a8ceb73eb68f9bdad7f51b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 1018 BBN Labs\n August 1987\n Some Comments on SQuID\n\nStatus of this Memo\n\n This memo is a discussion of some of the ideas expressed in RFC-1016\n on Source Quench. This memo introduces the distinction of the cause\n of congestion in a gateway between the effects of \"Funneling\" and\n \"Mismatch\". It is offered in the same spirit as RFC-1016; to\n stimulate discussion. The opinions offered are personal, not\n corporate, opinions. Distribution of this memo is unlimited.\n\nDiscussion\n\n It appears to me that there are at least two qualitatively different\n types of congestion which may occur at Internet gateways. One form\n of congestion is the result of the merger of several independent data\n streams from diverse sources at a common point in their communication\n path. I'll refer to this as \"Funneling\". The architecture of the\n Internet (apparentl","scope_keywords":["1018","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1018 Network Working Group A. McKenzie\nRequest for Comments: 1018 BBN Labs\n August 1987\n Some Comments on SQuID\n\nStatus of this Memo\n\n This memo is a discussion of some of the ideas expressed in RFC-1016\n on Source Quench. This memo introduces the distinction of the cause\n of congestion in a gateway between the effects of \"Funneling\" and\n \"Mismatch\". It is offered in the same spirit as RFC-1016; to\n stimulate discussion. The opinions offered are personal, not\n corporate, opinions. Distribution of this memo is unlimited.\n\nDiscussion\n\n It appears to me that there are at least two qualitatively different\n types of congestion which may occur at Internet gateways. One form\n of congestion is the result of the merger of several independent data\n streams from diverse sources at a common point in their communication\n path. I'll refer to this as \"Funneling\". The architecture of the\n Internet (apparentl 1018 algorithm path nested-reference unchanged"},{"id":"IETF RFC 102","type":"specification","body":"IETF","designation":"RFC 102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc102.txt","https://www.rfc-editor.org/rfc/rfc102.pdf"],"folder":"IETF/RFC-102","files":{"txt":{"path":"standards/IETF/RFC-102/RFC-102.txt","sha256":"dea960fca87c6dfac1b9deaf3b89a59156089d55e4dc7db7fe3652f5c9d24802"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Steve Crocker, Chairman\nRequest for Comments: 102 at BBN, Cambridge\nNIC#5763 22, 23 February 1971\n\n OUTPUT OF THE HOST/HOST PROTOCOL\n GLITCH CLEANING COMMITTEE\n\n At the NWG meeting in Urbana on 17-19 February 1971, a\n committee was established to look at the Host/Host protocol\n and see what changes were immediately desirable or necessary.\n\n The committee is chaired by Steve Crocker, and has eight\n other members:\n\n Ray Tomlinson BBN (Tenex)\n\n Jim White UCSB\n\n Gary Grossman Illinois\n\n Tom Barkalow Lincoln (TX2)\n\n Will Crowther BBN (IMPs)\n\n Bob Bressler MIT (Dynamic Modeling\n\n Doug McKay IBM (Yorktown)\n\n Dan Murphy BBN (Tenex)\n\n A number of topics were discussed. On some of these topics, a\n consensus was reached on whether or not to recommend a change, and if\n so, what the change should be. On the remaining topics, specific\n alternatives were proposed but no consensus ","scope_keywords":["102","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 114","folder":"IETF/RFC-114","source":"IETF/RFC-114/RFC-114.txt","version":null}],"search_text":"IETF RFC 102 Network Working Group Steve Crocker, Chairman\nRequest for Comments: 102 at BBN, Cambridge\nNIC#5763 22, 23 February 1971\n\n OUTPUT OF THE HOST/HOST PROTOCOL\n GLITCH CLEANING COMMITTEE\n\n At the NWG meeting in Urbana on 17-19 February 1971, a\n committee was established to look at the Host/Host protocol\n and see what changes were immediately desirable or necessary.\n\n The committee is chaired by Steve Crocker, and has eight\n other members:\n\n Ray Tomlinson BBN (Tenex)\n\n Jim White UCSB\n\n Gary Grossman Illinois\n\n Tom Barkalow Lincoln (TX2)\n\n Will Crowther BBN (IMPs)\n\n Bob Bressler MIT (Dynamic Modeling\n\n Doug McKay IBM (Yorktown)\n\n Dan Murphy BBN (Tenex)\n\n A number of topics were discussed. On some of these topics, a\n consensus was reached on whether or not to recommend a change, and if\n so, what the change should be. On the remaining topics, specific\n alternatives were proposed but no consensus  102 algorithm nested-reference unchanged"},{"id":"IETF RFC 114","type":"specification","body":"IETF","designation":"RFC 114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc114.txt","https://www.rfc-editor.org/rfc/rfc114.pdf"],"folder":"IETF/RFC-114","files":{"txt":{"path":"standards/IETF/RFC-114/RFC-114.txt","sha256":"0369cdaab2759cdeb8887e13501e0b15f775c4a1e30ae8f67759b357fa173892"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Bhushan\nRequest for Comments: 114 MIT Project MAC\nNIC: 5823 16 April 1971\n\n A FILE TRANSFER PROTOCOL\n\nI. Introduction\n\n Computer network usage may be divided into two broad categories --\n direct and indirect. Direct usage implies that you, the network\n user, are \"logged\" into a remote host and use it as a local user.\n You interact with the remote system via a terminal (teletypewriter,\n graphics console) or a computer. Differences in terminal\n characteristics are handled by host system programs, in accordance\n with standard protocols (such as TELNET (RFC 97) for teletypewriter\n communications, NETRJS (RFC 88) for remote job entry). You, however,\n have to know the different conventions of remote systems, in order to\n use them.\n\n Indirect usage, by contrast, does not require that you explicitly log\n into a remote system or even know how to \"use\" the remote system. A","scope_keywords":["114","attribute","attributes","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 114 Network Working Group A. Bhushan\nRequest for Comments: 114 MIT Project MAC\nNIC: 5823 16 April 1971\n\n A FILE TRANSFER PROTOCOL\n\nI. Introduction\n\n Computer network usage may be divided into two broad categories --\n direct and indirect. Direct usage implies that you, the network\n user, are \"logged\" into a remote host and use it as a local user.\n You interact with the remote system via a terminal (teletypewriter,\n graphics console) or a computer. Differences in terminal\n characteristics are handled by host system programs, in accordance\n with standard protocols (such as TELNET (RFC 97) for teletypewriter\n communications, NETRJS (RFC 88) for remote job entry). You, however,\n have to know the different conventions of remote systems, in order to\n use them.\n\n Indirect usage, by contrast, does not require that you explicitly log\n into a remote system or even know how to \"use\" the remote system. A 114 attribute attributes path presentation nested-reference unchanged"},{"id":"IETF RFC 1021","type":"specification","body":"IETF","designation":"RFC 1021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1021.txt","https://www.rfc-editor.org/rfc/rfc1021.pdf"],"folder":"IETF/RFC-1021","files":{"txt":{"path":"standards/IETF/RFC-1021/RFC-1021.txt","sha256":"b4e8200f75e882a039ceeead96f44b5355d0fa3b851cfed6d5574ea6d41c5355"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Partridge\nRequest For Comment: 1021 BBN/NNSC\n G. Trewitt\n Stanford\n October 1987\n\n THE HIGH-LEVEL ENTITY MANAGEMENT SYSTEM (HEMS)\n\nSTATUS OF THIS MEMO\n\n An overview of the RFCs which comprise the High-Level Entity\n Management System is provided. This system is experimental, and is\n currently being tested in portions of the Internet. It is hoped that\n this work will help lead to a standard for IP internetwork\n management. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n Until recently, a majority of critical components in IP networks,\n such as gateways, have come from a very small set of vendors. While\n each vendor had their own set of management protocols and mechanisms,\n the collection was small, and a knowledgeable system administrator\n could be expected to learn them all.\n\n Now, however, the number of vendors has grown quite large, and the\n lack of an a","scope_keywords":["1021","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 1021 Network Working Group C. Partridge\nRequest For Comment: 1021 BBN/NNSC\n G. Trewitt\n Stanford\n October 1987\n\n THE HIGH-LEVEL ENTITY MANAGEMENT SYSTEM (HEMS)\n\nSTATUS OF THIS MEMO\n\n An overview of the RFCs which comprise the High-Level Entity\n Management System is provided. This system is experimental, and is\n currently being tested in portions of the Internet. It is hoped that\n this work will help lead to a standard for IP internetwork\n management. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n Until recently, a majority of critical components in IP networks,\n such as gateways, have come from a very small set of vendors. While\n each vendor had their own set of management protocols and mechanisms,\n the collection was small, and a knowledgeable system administrator\n could be expected to learn them all.\n\n Now, however, the number of vendors has grown quite large, and the\n lack of an a 1021 key management nested-reference unchanged"},{"id":"IETF RFC 1023","type":"specification","body":"IETF","designation":"RFC 1023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1023.txt","https://www.rfc-editor.org/rfc/rfc1023.pdf"],"folder":"IETF/RFC-1023","files":{"txt":{"path":"standards/IETF/RFC-1023/RFC-1023.txt","sha256":"b402ecd349ad7ddd56b3df9f3c4553a35d8ccbcfbb074e743dccb78c593cdd22"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Trewitt\nRequest for Comments: 1023 Stanford\n C. Partridge\n BBN/NNSC\n October 1987\n\n HEMS Monitoring and Control Language\n\n This RFC specifies the design of a general-purpose, yet efficient,\n monitoring and control language for managing network entities. The\n data in the entity is modeled as a hierarchy and specific items are\n named by giving the path from the root of the tree. Most items are\n read-only, but some can be \"set\" in order to perform control\n operations. Both requests and responses are represented using the\n ISO ASN.1 data encoding rules.\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is provide a specification for monitoring and\n control of network entities in the Internet. This is an experimental\n specification and is intended for use in testing the ideas presented\n here. No proposals in this memo are intended as standards for the\n Internet at this t","scope_keywords":["1023","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1024","folder":"IETF/RFC-1024","source":"IETF/RFC-1024/RFC-1024.txt","version":null}],"search_text":"IETF RFC 1023 Network Working Group G. Trewitt\nRequest for Comments: 1023 Stanford\n C. Partridge\n BBN/NNSC\n October 1987\n\n HEMS Monitoring and Control Language\n\n This RFC specifies the design of a general-purpose, yet efficient,\n monitoring and control language for managing network entities. The\n data in the entity is modeled as a hierarchy and specific items are\n named by giving the path from the root of the tree. Most items are\n read-only, but some can be \"set\" in order to perform control\n operations. Both requests and responses are represented using the\n ISO ASN.1 data encoding rules.\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is provide a specification for monitoring and\n control of network entities in the Internet. This is an experimental\n specification and is intended for use in testing the ideas presented\n here. No proposals in this memo are intended as standards for the\n Internet at this t 1023 path presentation nested-reference unchanged"},{"id":"IETF RFC 1024","type":"specification","body":"IETF","designation":"RFC 1024","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1024.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1024.txt","https://www.rfc-editor.org/rfc/rfc1024.pdf"],"folder":"IETF/RFC-1024","files":{"txt":{"path":"standards/IETF/RFC-1024/RFC-1024.txt","sha256":"fd56f20e3feae901c863d41ce2ddcc877538cf7f1a2adfe9038165ab61aba143"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C.Partridge\nRequest For Comment: 1024 BBN/NNSC\n G. Trewitt\n Stanford\n October 1987\n\n HEMS VARIABLE DEFINITIONS\n\nSTATUS OF THIS MEMO\n\n This memo assigns instruction codes, defines object formats and\n object semantics for use with the High-Level Monitoring and Control\n Language, defined in RFC-1023.\n\n This memo is provisional and the definitions are subject to change.\n Readers should confirm that they have the most recent version of the\n memo.\n\n The authors assume a working knowledge of the ISO data encoding\n standard, ASN.1, and a general understanding of the IP protocol\n suite.\n\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n In other memos [RFC-1021, RFC-1022] the authors have described a\n general system for monitoring and controlling network entities; this\n system is called the High-Level Entity Management System (HEMS).\n This system permits applications ","scope_keywords":["1024","attribute","attributes","management","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null}],"search_text":"IETF RFC 1024 Network Working Group C.Partridge\nRequest For Comment: 1024 BBN/NNSC\n G. Trewitt\n Stanford\n October 1987\n\n HEMS VARIABLE DEFINITIONS\n\nSTATUS OF THIS MEMO\n\n This memo assigns instruction codes, defines object formats and\n object semantics for use with the High-Level Monitoring and Control\n Language, defined in RFC-1023.\n\n This memo is provisional and the definitions are subject to change.\n Readers should confirm that they have the most recent version of the\n memo.\n\n The authors assume a working knowledge of the ISO data encoding\n standard, ASN.1, and a general understanding of the IP protocol\n suite.\n\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n In other memos [RFC-1021, RFC-1022] the authors have described a\n general system for monitoring and controlling network entities; this\n system is called the High-Level Entity Management System (HEMS).\n This system permits applications  1024 attribute attributes management presentation subject nested-reference unchanged"},{"id":"IETF RFC 1066","type":"specification","body":"IETF","designation":"RFC 1066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1066.txt","https://www.rfc-editor.org/rfc/rfc1066.pdf"],"folder":"IETF/RFC-1066","files":{"txt":{"path":"standards/IETF/RFC-1066/RFC-1066.txt","sha256":"1f125363d0f8b2f6c86913744cce92dd9b194cc1e64242731d9eecc01472ca7c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest For Comments: 1066 M. Rose\n TWG\n August 1988\n\n Management Information Base for Network Management\n of TCP/IP-based internets\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. IAB POLICY STATEMENT .................................. 2\n 3. Introduction .......................................... 2\n 4. Objects ............................................... 5\n 4.1 Object Groups ........................................ 5\n 4.2 Format of Definitions ................................ 6\n 5. Object Definitions .................................... 7\n 5.1 The System Group ..................................... 8\n 5.2 The Interfaces Group ................................. 10\n 5.2.1 The Interfaces Table ............................... 10\n 5.3 The Address Translation Group ........................ 22\n 5.4 The IP Group .......","scope_keywords":["1066","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1065","folder":"IETF/RFC-1065","source":"IETF/RFC-1065/RFC-1065.txt","version":null},{"body":"IETF","designation":"RFC 1067","folder":"IETF/RFC-1067","source":"IETF/RFC-1067/RFC-1067.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1066 Network Working Group K. McCloghrie\nRequest For Comments: 1066 M. Rose\n TWG\n August 1988\n\n Management Information Base for Network Management\n of TCP/IP-based internets\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. IAB POLICY STATEMENT .................................. 2\n 3. Introduction .......................................... 2\n 4. Objects ............................................... 5\n 4.1 Object Groups ........................................ 5\n 4.2 Format of Definitions ................................ 6\n 5. Object Definitions .................................... 7\n 5.1 The System Group ..................................... 8\n 5.2 The Interfaces Group ................................. 10\n 5.2.1 The Interfaces Table ............................... 10\n 5.3 The Address Translation Group ........................ 22\n 5.4 The IP Group ....... 1066 management policy nested-reference unchanged"},{"id":"IETF RFC 1156","type":"specification","body":"IETF","designation":"RFC 1156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1156.txt","https://www.rfc-editor.org/rfc/rfc1156.pdf"],"folder":"IETF/RFC-1156","files":{"txt":{"path":"standards/IETF/RFC-1156/RFC-1156.txt","sha256":"08bcfac236eb9a085ed46c9e6fb38128eac55c4f47f1a8ffed9e470e5b03ba9c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest For Comments: 1156 Hughes LAN Systems\nObsoletes: RFC 1066 M. Rose\n Performance Systems International\n May 1990\n\n Management Information Base for Network Management\n of TCP/IP-based internets\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. IAB Policy Statement .................................. 2\n 3. Introduction .......................................... 2\n 4. Objects ............................................... 6\n 4.1 Object Groups ........................................ 6\n 4.2 Format of Definitions ................................ 7\n 5. Object Definitions .................................... 8\n 5.1 The System Group ..................................... 9\n 5.2 The Interfaces Group ................................. 11\n 5.2.1 The Interfaces Table ............................... 11\n 5.3 The Address Trans","scope_keywords":["1156","identification","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1155","folder":"IETF/RFC-1155","source":"IETF/RFC-1155/RFC-1155.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1161","folder":"IETF/RFC-1161","source":"IETF/RFC-1161/RFC-1161.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1227","folder":"IETF/RFC-1227","source":"IETF/RFC-1227/RFC-1227.txt","version":null},{"body":"IETF","designation":"RFC 1228","folder":"IETF/RFC-1228","source":"IETF/RFC-1228/RFC-1228.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1156 Network Working Group K. McCloghrie\nRequest For Comments: 1156 Hughes LAN Systems\nObsoletes: RFC 1066 M. Rose\n Performance Systems International\n May 1990\n\n Management Information Base for Network Management\n of TCP/IP-based internets\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. IAB Policy Statement .................................. 2\n 3. Introduction .......................................... 2\n 4. Objects ............................................... 6\n 4.1 Object Groups ........................................ 6\n 4.2 Format of Definitions ................................ 7\n 5. Object Definitions .................................... 8\n 5.1 The System Group ..................................... 9\n 5.2 The Interfaces Group ................................. 11\n 5.2.1 The Interfaces Table ............................... 11\n 5.3 The Address Trans 1156 identification management policy nested-reference unchanged"},{"id":"IETF RFC 1026","type":"specification","body":"IETF","designation":"RFC 1026","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1026.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1026.txt","https://www.rfc-editor.org/rfc/rfc1026.pdf"],"folder":"IETF/RFC-1026","files":{"txt":{"path":"standards/IETF/RFC-1026/RFC-1026.txt","sha256":"fd0ce59e0bb44e74a782fda6398eb2a98d9a5604b78e336615000df8baa2f582"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S.E. Kille\nRequest for Comments 1026 University College London\n September 1987\n\n Addendum to RFC 987\n\n (Mapping between X.400 and RFC-822)\n\nStatus of this Memo\n\n This RFC suggest a proposed protocol for the Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\n This document specifies a number of additions and corrections to\n RFC-987, aka Mailgroup Note 19.\n\n The addendum carries equal weight to the original specification,\n which must be used when this mapping is performed on the Internet or\n in the UK Academic Community. This mapping may also be used within\n the RARE community in Europe. This specification may be modified in\n the light of implementation experience, but no substantial changes\n are expected.\n\n1. Errata\n\n - In section 4.6.4, replace \"..\" with \".\".\n\n - In section 4.2.4, replace three re","scope_keywords":["1026","algorithm","attribute","attributes","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 1026 Network Working Group S.E. Kille\nRequest for Comments 1026 University College London\n September 1987\n\n Addendum to RFC 987\n\n (Mapping between X.400 and RFC-822)\n\nStatus of this Memo\n\n This RFC suggest a proposed protocol for the Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\n This document specifies a number of additions and corrections to\n RFC-987, aka Mailgroup Note 19.\n\n The addendum carries equal weight to the original specification,\n which must be used when this mapping is performed on the Internet or\n in the UK Academic Community. This mapping may also be used within\n the RARE community in Europe. This specification may be modified in\n the light of implementation experience, but no substantial changes\n are expected.\n\n1. Errata\n\n - In section 4.6.4, replace \"..\" with \".\".\n\n - In section 4.2.4, replace three re 1026 algorithm attribute attributes preservation nested-reference unchanged"},{"id":"IETF RFC 1138","type":"specification","body":"IETF","designation":"RFC 1138","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1138.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1138.txt","https://www.rfc-editor.org/rfc/rfc1138.pdf"],"folder":"IETF/RFC-1138","files":{"txt":{"path":"standards/IETF/RFC-1138/RFC-1138.txt","sha256":"457b48b83651525d96af680073bf012da39fb4d5f9215afe0befb62ae3fa9c4d"}},"tags":["nested-reference","unchanged"],"summary":"Service [CCITT/ISO88c]. The MT Abstract Service provides the\n following three basic services:\n\n 1. Submission (used by IPMS Origination)\n\n 2. Delivery (used by IPMS Reception)\n\n 3. Administration (used by IPMS Management)\n\n Administration is a local issue, and so does not affect this\n standard. Submission and delivery relate primarily to the MTS\n Message (comprising Envelope and Content), which carries an IPM or\n IPN (or other uninterpreted contents). There is also an Envelope,\n which includes an ID, an originator, and a list of recipients.\n Submission also includes the probe service, which supports the IPMS\n Probe. Delivery also includes Reports, which indicate whether a\n given MTS Message has been delivered or not.\n\n The MTS is REFINED into the MTA (Message Transfer Agent) Service,\n which define the interaction between MTAs, along with the procedures\n for distributed operation. This se","scope_keywords":["1138","delivery","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 1138 Service [CCITT/ISO88c]. The MT Abstract Service provides the\n following three basic services:\n\n 1. Submission (used by IPMS Origination)\n\n 2. Delivery (used by IPMS Reception)\n\n 3. Administration (used by IPMS Management)\n\n Administration is a local issue, and so does not affect this\n standard. Submission and delivery relate primarily to the MTS\n Message (comprising Envelope and Content), which carries an IPM or\n IPN (or other uninterpreted contents). There is also an Envelope,\n which includes an ID, an originator, and a list of recipients.\n Submission also includes the probe service, which supports the IPMS\n Probe. Delivery also includes Reports, which indicate whether a\n given MTS Message has been delivered or not.\n\n The MTS is REFINED into the MTA (Message Transfer Agent) Service,\n which define the interaction between MTAs, along with the procedures\n for distributed operation. This se 1138 delivery management presentation nested-reference unchanged"},{"id":"IETF RFC 1148","type":"specification","body":"IETF","designation":"RFC 1148","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1148.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1148.txt","https://www.rfc-editor.org/rfc/rfc1148.pdf"],"folder":"IETF/RFC-1148","files":{"txt":{"path":"standards/IETF/RFC-1148/RFC-1148.txt","sha256":"b67136298c4bbe343da8b2b39448e47266fb34abe5423fcd738fa5be6df36e9e"}},"tags":["nested-reference","unchanged"],"summary":"Service [CCITT/ISO88c]. The MT Abstract Service provides the\n following three basic services:\n\n 1. Submission (used by IPMS Origination)\n\n 2. Delivery (used by IPMS Reception)\n\n 3. Administration (used by IPMS Management)\n\n Administration is a local issue, and so does not affect this\n standard. Submission and delivery relate primarily to the MTS\n Message (comprising Envelope and Content), which carries an IPM or\n IPN (or other uninterpreted contents). There is also an Envelope,\n which includes an ID, an originator, and a list of recipients.\n Submission also includes the probe service, which supports the IPMS\n Probe. Delivery also includes Reports, which indicate whether a\n given MTS Message has been delivered or not.\n\n The MTS is REFINED into the MTA (Message Transfer Agent) Service,\n which define the interaction between MTAs, along with the procedures\n for distributed operation. This se","scope_keywords":["1148","delivery","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 1148 Service [CCITT/ISO88c]. The MT Abstract Service provides the\n following three basic services:\n\n 1. Submission (used by IPMS Origination)\n\n 2. Delivery (used by IPMS Reception)\n\n 3. Administration (used by IPMS Management)\n\n Administration is a local issue, and so does not affect this\n standard. Submission and delivery relate primarily to the MTS\n Message (comprising Envelope and Content), which carries an IPM or\n IPN (or other uninterpreted contents). There is also an Envelope,\n which includes an ID, an originator, and a list of recipients.\n Submission also includes the probe service, which supports the IPMS\n Probe. Delivery also includes Reports, which indicate whether a\n given MTS Message has been delivered or not.\n\n The MTS is REFINED into the MTA (Message Transfer Agent) Service,\n which define the interaction between MTAs, along with the procedures\n for distributed operation. This se 1148 delivery management presentation nested-reference unchanged"},{"id":"IETF RFC 1327","type":"specification","body":"IETF","designation":"RFC 1327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1327.txt","https://www.rfc-editor.org/rfc/rfc1327.pdf"],"folder":"IETF/RFC-1327","files":{"txt":{"path":"standards/IETF/RFC-1327/RFC-1327.txt","sha256":"a019d2605ec7f307a2a9d2684b79f7b96af02826b0c9ad5bd71e790deecefc96"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of mappings which will enable\n interworking between systems operating the CCITT X.400 1988)\n Recommendations on Message Handling Systems / ISO IEC 10021 Message\n Oriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems\n using the RFC 822 mail protocol [Crocker82a] or protocols derived\n from RFC 822. The approach aims to maximise the services offered\n across the boundary, whilst not requiring unduly complex mappings.\n The mappings should not require any changes to end systems. This\n document is a revision based on RFCs 987, 1026, 1138, and 1148\n [Kille86a,Kille87a] which it obsoletes.\n\n This document specifies a mapping between two protocols. This\n specification should be used when this mapping is performed on the\n DARPA Internet or in the UK Academic Community. This specification\n may be modified in the light of implementation experience, but no","scope_keywords":["1327","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1328","folder":"IETF/RFC-1328","source":"IETF/RFC-1328/RFC-1328.txt","version":null},{"body":"IETF","designation":"RFC 1405","folder":"IETF/RFC-1405","source":"IETF/RFC-1405/RFC-1405.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1496","folder":"IETF/RFC-1496","source":"IETF/RFC-1496/RFC-1496.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1648","folder":"IETF/RFC-1648","source":"IETF/RFC-1648/RFC-1648.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1766","folder":"IETF/RFC-1766","source":"IETF/RFC-1766/RFC-1766.txt","version":null},{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null},{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 1327 This document describes a set of mappings which will enable\n interworking between systems operating the CCITT X.400 1988)\n Recommendations on Message Handling Systems / ISO IEC 10021 Message\n Oriented Text Interchange Systems (MOTIS) [CCITT/ISO88a], and systems\n using the RFC 822 mail protocol [Crocker82a] or protocols derived\n from RFC 822. The approach aims to maximise the services offered\n across the boundary, whilst not requiring unduly complex mappings.\n The mappings should not require any changes to end systems. This\n document is a revision based on RFCs 987, 1026, 1138, and 1148\n [Kille86a,Kille87a] which it obsoletes.\n\n This document specifies a mapping between two protocols. This\n specification should be used when this mapping is performed on the\n DARPA Internet or in the UK Academic Community. This specification\n may be modified in the light of implementation experience, but no 1327 presentation nested-reference unchanged"},{"id":"IETF RFC 1506","type":"specification","body":"IETF","designation":"RFC 1506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1506.txt","https://www.rfc-editor.org/rfc/rfc1506.pdf"],"folder":"IETF/RFC-1506","files":{"txt":{"path":"standards/IETF/RFC-1506/RFC-1506.txt","sha256":"565a814cb6207e8089d18d0735188523169ae8ed879d92e4af433ea3a729d9e4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Houttuin\nRequest for Comments: 1506 RARE Secretariat\nRARE Technical Report: 6 August 1993\n\n A Tutorial on Gatewaying between X.400 and Internet Mail\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n There are many ways in which X.400 and Internet (STD 11, RFC 822)\n mail systems can be interconnected. Addresses and service elements\n can be mapped onto each other in different ways. From the early\n available gateway implementations, one was not necessarily better\n than another, but the sole fact that each handled the mappings in a\n different way led to major interworking problems, especially when a\n message (or address) crossed more than one gateway. The need for one\n global standard on how to implement X.400 - Internet mail gatewaying\n","scope_keywords":["1506","attribute","attributes","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 1506 Network Working Group J. Houttuin\nRequest for Comments: 1506 RARE Secretariat\nRARE Technical Report: 6 August 1993\n\n A Tutorial on Gatewaying between X.400 and Internet Mail\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n There are many ways in which X.400 and Internet (STD 11, RFC 822)\n mail systems can be interconnected. Addresses and service elements\n can be mapped onto each other in different ways. From the early\n available gateway implementations, one was not necessarily better\n than another, but the sole fact that each handled the mappings in a\n different way led to major interworking problems, especially when a\n message (or address) crossed more than one gateway. The need for one\n global standard on how to implement X.400 - Internet mail gatewaying\n 1506 attribute attributes license subject nested-reference unchanged"},{"id":"IETF RFC 2156","type":"specification","body":"IETF","designation":"RFC 2156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2156.txt","https://www.rfc-editor.org/rfc/rfc2156.pdf"],"folder":"IETF/RFC-2156","files":{"txt":{"path":"standards/IETF/RFC-2156/RFC-2156.txt","sha256":"e36a61a8f120b96ccdc36c5009ec8dc7dd2adbd427b0033f5abe0ad77bb0c0b5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 2156 Isode Ltd.\nObsoletes: 987, 1026, 1138, 1148, 1327, 1495 January 1998\nUpdates: 822\nCategory: Standards Track\n\n MIXER (Mime Internet X.400 Enhanced Relay):\n Mapping between X.400 and RFC 822/MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 - Overview ...................................... 3\n 1.1 - X.400 ......................................... 3\n 1.2 - RFC 822 and MIME .............................. 3\n 1.3 - The n","scope_keywords":["2156","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null}],"search_text":"IETF RFC 2156 Network Working Group S. Kille\nRequest for Comments: 2156 Isode Ltd.\nObsoletes: 987, 1026, 1138, 1148, 1327, 1495 January 1998\nUpdates: 822\nCategory: Standards Track\n\n MIXER (Mime Internet X.400 Enhanced Relay):\n Mapping between X.400 and RFC 822/MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 - Overview ...................................... 3\n 1.1 - X.400 ......................................... 3\n 1.2 - RFC 822 and MIME .............................. 3\n 1.3 - The n 2156 presentation nested-reference unchanged"},{"id":"IETF RFC 1027","type":"specification","body":"IETF","designation":"RFC 1027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1027.txt","https://www.rfc-editor.org/rfc/rfc1027.pdf"],"folder":"IETF/RFC-1027","files":{"txt":{"path":"standards/IETF/RFC-1027/RFC-1027.txt","sha256":"76797b13383c6aededd31d91e55392dbb8e91a86fa39451c67a0656228773c5e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Smoot Carl-Mitchell\nRequest for Comments: 1027 Texas Internet Consulting\n John S. Quarterman\n Texas Internet Consulting\n October 1987\n\n Using ARP to Implement Transparent Subnet Gateways\n\nStatus of this Memo\n\n This RFC describes the use of the Ethernet Address Resolution\n Protocol (ARP) by subnet gateways to permit hosts on the connected\n subnets to communicate without being aware of the existence of\n subnets, using the technique of \"Proxy ARP\" [6]. It is based on\n RFC-950 [1], RFC-922 [2], and RFC-826 [3] and is a restricted subset\n of the mechanism of RFC-925 [4]. Distribution of this memo is\n unlimited.\n\nAcknowledgment\n\n The work described in this memo was performed while the authors were\n employed by the Computer Sciences Department of the University of\n Texas at Austin.\n\nIntroduction\n\n The purpose of this memo is to describe in detail the implementation\n of tra","scope_keywords":["1027","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1546","folder":"IETF/RFC-1546","source":"IETF/RFC-1546/RFC-1546.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null}],"search_text":"IETF RFC 1027 Network Working Group Smoot Carl-Mitchell\nRequest for Comments: 1027 Texas Internet Consulting\n John S. Quarterman\n Texas Internet Consulting\n October 1987\n\n Using ARP to Implement Transparent Subnet Gateways\n\nStatus of this Memo\n\n This RFC describes the use of the Ethernet Address Resolution\n Protocol (ARP) by subnet gateways to permit hosts on the connected\n subnets to communicate without being aware of the existence of\n subnets, using the technique of \"Proxy ARP\" [6]. It is based on\n RFC-950 [1], RFC-922 [2], and RFC-826 [3] and is a restricted subset\n of the mechanism of RFC-925 [4]. Distribution of this memo is\n unlimited.\n\nAcknowledgment\n\n The work described in this memo was performed while the authors were\n employed by the Computer Sciences Department of the University of\n Texas at Austin.\n\nIntroduction\n\n The purpose of this memo is to describe in detail the implementation\n of tra 1027 algorithm path nested-reference unchanged"},{"id":"IETF RFC 1546","type":"specification","body":"IETF","designation":"RFC 1546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1546.txt","https://www.rfc-editor.org/rfc/rfc1546.pdf"],"folder":"IETF/RFC-1546","files":{"txt":{"path":"standards/IETF/RFC-1546/RFC-1546.txt","sha256":"47733a94b4e91a13531831890a7c59d74a5fbdffaaf79ef8786c579246ca64b5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Partridge\nRequest for Comments: 1546 T. Mendez\nCategory: Informational W. Milliken\n BBN\n November 1993\n\n Host Anycasting Service\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This RFC describes an internet anycasting service for IP. The\n primary purpose of this memo is to establish the semantics of an\n anycasting service within an IP internet. Insofar as is possible,\n this memo tries to be agnostic about how the service is actually\n provided by the internetwork. This memo describes an experimental\n service and does not propose a protocol. This memo is produced by\n the Internet Research Task Force (IRTF).\n\nMotivation\n\n There are a number of situations in networking where a host,\n application, or user wishes to locat","scope_keywords":["1546","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2526","folder":"IETF/RFC-2526","source":"IETF/RFC-2526/RFC-2526.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3258","folder":"IETF/RFC-3258","source":"IETF/RFC-3258/RFC-3258.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 1546 Network Working Group C. Partridge\nRequest for Comments: 1546 T. Mendez\nCategory: Informational W. Milliken\n BBN\n November 1993\n\n Host Anycasting Service\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This RFC describes an internet anycasting service for IP. The\n primary purpose of this memo is to establish the semantics of an\n anycasting service within an IP internet. Insofar as is possible,\n this memo tries to be agnostic about how the service is actually\n provided by the internetwork. This memo describes an experimental\n service and does not propose a protocol. This memo is produced by\n the Internet Research Task Force (IRTF).\n\nMotivation\n\n There are a number of situations in networking where a host,\n application, or user wishes to locat 1546 delivery key nested-reference unchanged"},{"id":"IETF RFC 1067","type":"specification","body":"IETF","designation":"RFC 1067","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1067.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1067.txt","https://www.rfc-editor.org/rfc/rfc1067.pdf"],"folder":"IETF/RFC-1067","files":{"txt":{"path":"standards/IETF/RFC-1067/RFC-1067.txt","sha256":"61839ecabad6e392a869a3f4755124f45d2ae924b462564ad06fbacd12d6444e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\nRequest for Comments: 1067 University of Tennessee at Knoxville\n M. Fedor\n NYSERNet, Inc.\n M. Schoffstall\n Rensselaer Polytechnic Institute\n J. Davin\n Proteon, Inc.\n August 1988\n\n A Simple Network Management Protocol\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 4\n 3.1 Goals of the Architecture ............................ 4\n 3.2 Elements of the Architecture ......................... 4\n 3.2.1 Scope of Management Information .................... 5\n 3.2.2 Representation of Management Information ........... 5\n 3.2.3 Operations Supported on Management Information ..... 6\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 7\n 3.2.5 Definition of Administrative Relationships ......... 7\n 3.2.6 Form ","scope_keywords":["1067","authentication","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1065","folder":"IETF/RFC-1065","source":"IETF/RFC-1065/RFC-1065.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null}],"search_text":"IETF RFC 1067 Network Working Group J. Case\nRequest for Comments: 1067 University of Tennessee at Knoxville\n M. Fedor\n NYSERNet, Inc.\n M. Schoffstall\n Rensselaer Polytechnic Institute\n J. Davin\n Proteon, Inc.\n August 1988\n\n A Simple Network Management Protocol\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 4\n 3.1 Goals of the Architecture ............................ 4\n 3.2 Elements of the Architecture ......................... 4\n 3.2.1 Scope of Management Information .................... 5\n 3.2.2 Representation of Management Information ........... 5\n 3.2.3 Operations Supported on Management Information ..... 6\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 7\n 3.2.5 Definition of Administrative Relationships ......... 7\n 3.2.6 Form  1067 authentication identification management presentation nested-reference unchanged"},{"id":"IETF RFC 1098","type":"specification","body":"IETF","designation":"RFC 1098","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1098.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1098.txt","https://www.rfc-editor.org/rfc/rfc1098.pdf"],"folder":"IETF/RFC-1098","files":{"txt":{"path":"standards/IETF/RFC-1098/RFC-1098.txt","sha256":"6f7887db214331d5dbf51c1e60c5cc5eb2716679df3c6bc685be4abe971d8081"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\nRequest for Comments: 1098 University of Tennessee at Knoxville\nObsoletes: RFC 1067 M. Fedor\n NYSERNet, Inc.\n M. Schoffstall\n Rensselaer Polytechnic Institute\n C. Davin\n MIT Laboratory for Computer Science\n April 1989\n\n A Simple Network Management Protocol (SNMP)\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 4\n 3.1 Goals of the Architecture ............................ 4\n 3.2 Elements of the Architecture ......................... 4\n 3.2.1 Scope of Management Information .................... 5\n 3.2.2 Representation of Management Information ........... 5\n 3.2.3 Operations Supported on Management Information ..... 6\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 7\n 3.2.5 Definition of Admini","scope_keywords":["1098","authentication","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1228","folder":"IETF/RFC-1228","source":"IETF/RFC-1228/RFC-1228.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1352","folder":"IETF/RFC-1352","source":"IETF/RFC-1352/RFC-1352.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null}],"search_text":"IETF RFC 1098 Network Working Group J. Case\nRequest for Comments: 1098 University of Tennessee at Knoxville\nObsoletes: RFC 1067 M. Fedor\n NYSERNet, Inc.\n M. Schoffstall\n Rensselaer Polytechnic Institute\n C. Davin\n MIT Laboratory for Computer Science\n April 1989\n\n A Simple Network Management Protocol (SNMP)\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 4\n 3.1 Goals of the Architecture ............................ 4\n 3.2 Elements of the Architecture ......................... 4\n 3.2.1 Scope of Management Information .................... 5\n 3.2.2 Representation of Management Information ........... 5\n 3.2.3 Operations Supported on Management Information ..... 6\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 7\n 3.2.5 Definition of Admini 1098 authentication identification management presentation nested-reference unchanged"},{"id":"IETF RFC 1157","type":"specification","body":"IETF","designation":"RFC 1157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1157.txt","https://www.rfc-editor.org/rfc/rfc1157.pdf"],"folder":"IETF/RFC-1157","files":{"txt":{"path":"standards/IETF/RFC-1157/RFC-1157.txt","sha256":"2a4c8547229ec9cb2806c56edb90cbaffb5128b95f4f35a440876927b56caca7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\nRequest for Comments: 1157 SNMP Research\nObsoletes: RFC 1098 M. Fedor\n Performance Systems International\n M. Schoffstall\n Performance Systems International\n J. Davin\n MIT Laboratory for Computer Science\n May 1990\n\n A Simple Network Management Protocol (SNMP)\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 5\n 3.1 Goals of the Architecture ............................ 5\n 3.2 Elements of the Architecture ......................... 5\n 3.2.1 Scope of Management Information .................... 6\n 3.2.2 Representation of Management Information ........... 6\n 3.2.3 Operations Supported on Management Information ..... 7\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 8\n 3.2.5 Definition of Administrat","scope_keywords":["1157","authentication","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1155","folder":"IETF/RFC-1155","source":"IETF/RFC-1155/RFC-1155.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1161","folder":"IETF/RFC-1161","source":"IETF/RFC-1161/RFC-1161.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1187","folder":"IETF/RFC-1187","source":"IETF/RFC-1187/RFC-1187.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1224","folder":"IETF/RFC-1224","source":"IETF/RFC-1224/RFC-1224.txt","version":null},{"body":"IETF","designation":"RFC 1227","folder":"IETF/RFC-1227","source":"IETF/RFC-1227/RFC-1227.txt","version":null},{"body":"IETF","designation":"RFC 1228","folder":"IETF/RFC-1228","source":"IETF/RFC-1228/RFC-1228.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1298","folder":"IETF/RFC-1298","source":"IETF/RFC-1298/RFC-1298.txt","version":null},{"body":"IETF","designation":"RFC 1303","folder":"IETF/RFC-1303","source":"IETF/RFC-1303/RFC-1303.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1352","folder":"IETF/RFC-1352","source":"IETF/RFC-1352/RFC-1352.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1419","folder":"IETF/RFC-1419","source":"IETF/RFC-1419/RFC-1419.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null},{"body":"IETF","designation":"RFC 1450","folder":"IETF/RFC-1450","source":"IETF/RFC-1450/RFC-1450.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1514","folder":"IETF/RFC-1514","source":"IETF/RFC-1514/RFC-1514.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1906","folder":"IETF/RFC-1906","source":"IETF/RFC-1906/RFC-1906.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null}],"search_text":"IETF RFC 1157 Network Working Group J. Case\nRequest for Comments: 1157 SNMP Research\nObsoletes: RFC 1098 M. Fedor\n Performance Systems International\n M. Schoffstall\n Performance Systems International\n J. Davin\n MIT Laboratory for Computer Science\n May 1990\n\n A Simple Network Management Protocol (SNMP)\n\n Table of Contents\n\n 1. Status of this Memo ................................... 2\n 2. Introduction .......................................... 2\n 3. The SNMP Architecture ................................. 5\n 3.1 Goals of the Architecture ............................ 5\n 3.2 Elements of the Architecture ......................... 5\n 3.2.1 Scope of Management Information .................... 6\n 3.2.2 Representation of Management Information ........... 6\n 3.2.3 Operations Supported on Management Information ..... 7\n 3.2.4 Form and Meaning of Protocol Exchanges ............. 8\n 3.2.5 Definition of Administrat 1157 authentication identification management presentation nested-reference unchanged"},{"id":"IETF RFC 103","type":"specification","body":"IETF","designation":"RFC 103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc103.txt","https://www.rfc-editor.org/rfc/rfc103.pdf"],"folder":"IETF/RFC-103","files":{"txt":{"path":"standards/IETF/RFC-103/RFC-103.txt","sha256":"1dd09d9ea4ac5b85df56ea344ffb646399eb82bb4067a43ce8c7b3415c5f417e"}},"tags":["nested-reference","unchanged"],"summary":"NWG RFC 103\n NIC 5764\n\nIMPLEMENTATION OF INTERRUPT KEYS\n\nR B Kalin\nMIT Lincoln Laboratory\n24 Feb 1971\n\n The current protocol specifications contain a serious logical\nerror in the implementation of the program interrupt function. This\npaper discusses the problem and offers a solution that is simple to\nimplement.\n\nTHE PROBLEM\n\n As found on most time-sharing systems the program interrupt key,\nelsewhere known as the break key, or help request button, has two\nfunctions. It suspends temporarily the user process being run, and it\nswitches the keyboard input stream to a dormant supervisory process.\nUnaccepted input typed prior to the interrupt request remains buffered\nfor the suspended user process. Subsequent typing is sent to a\nsupervisory routine.\n\n The current NCP protocol implements only half this function. It\npprovides, through use of INS and INR control messages, for the\nsuspension of a r","scope_keywords":["103","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 114","folder":"IETF/RFC-114","source":"IETF/RFC-114/RFC-114.txt","version":null}],"search_text":"IETF RFC 103 NWG RFC 103\n NIC 5764\n\nIMPLEMENTATION OF INTERRUPT KEYS\n\nR B Kalin\nMIT Lincoln Laboratory\n24 Feb 1971\n\n The current protocol specifications contain a serious logical\nerror in the implementation of the program interrupt function. This\npaper discusses the problem and offers a solution that is simple to\nimplement.\n\nTHE PROBLEM\n\n As found on most time-sharing systems the program interrupt key,\nelsewhere known as the break key, or help request button, has two\nfunctions. It suspends temporarily the user process being run, and it\nswitches the keyboard input stream to a dormant supervisory process.\nUnaccepted input typed prior to the interrupt request remains buffered\nfor the suspended user process. Subsequent typing is sent to a\nsupervisory routine.\n\n The current NCP protocol implements only half this function. It\npprovides, through use of INS and INR control messages, for the\nsuspension of a r 103 key keys nested-reference unchanged"},{"id":"IETF RFC 1030","type":"specification","body":"IETF","designation":"RFC 1030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1030.txt","https://www.rfc-editor.org/rfc/rfc1030.pdf"],"folder":"IETF/RFC-1030","files":{"txt":{"path":"standards/IETF/RFC-1030/RFC-1030.txt","sha256":"6ac848632f646652ad1f50cced139a89728bb54f5ca1aaabce28877556274298"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Lambert\nRequest for Comments: 1030 M.I.T. Laboratory for Computer Science\n November 1987\n\n On Testing the NETBLT Protocol over Divers Networks\n\nSTATUS OF THIS MEMO\n\n This RFC describes the results gathered from testing NETBLT over\n three networks of differing bandwidths and round-trip delays. While\n the results are not complete, the information gathered so far has\n been very promising and supports RFC-998's assertion that that NETBLT\n can provide very high throughput over networks with very different\n characteristics. Distribution of this memo is unlimited.\n\n1. Introduction\n\n NETBLT (NETwork BLock Transfer) is a transport level protocol\n intended for the rapid transfer of a large quantity of data between\n computers. It provides a transfer that is reliable and flow\n controlled, and is designed to provide maximum throughput over a wide\n variety of networks. The NET","scope_keywords":["1030","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1986","folder":"IETF/RFC-1986","source":"IETF/RFC-1986/RFC-1986.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null}],"search_text":"IETF RFC 1030 Network Working Group M. Lambert\nRequest for Comments: 1030 M.I.T. Laboratory for Computer Science\n November 1987\n\n On Testing the NETBLT Protocol over Divers Networks\n\nSTATUS OF THIS MEMO\n\n This RFC describes the results gathered from testing NETBLT over\n three networks of differing bandwidths and round-trip delays. While\n the results are not complete, the information gathered so far has\n been very promising and supports RFC-998's assertion that that NETBLT\n can provide very high throughput over networks with very different\n characteristics. Distribution of this memo is unlimited.\n\n1. Introduction\n\n NETBLT (NETwork BLock Transfer) is a transport level protocol\n intended for the rapid transfer of a large quantity of data between\n computers. It provides a transfer that is reliable and flow\n controlled, and is designed to provide maximum throughput over a wide\n variety of networks. The NET 1030 management path pid nested-reference unchanged"},{"id":"IETF RFC 1986","type":"specification","body":"IETF","designation":"RFC 1986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1986.txt","https://www.rfc-editor.org/rfc/rfc1986.pdf"],"folder":"IETF/RFC-1986","files":{"txt":{"path":"standards/IETF/RFC-1986/RFC-1986.txt","sha256":"23d316e5ff1eeaacad7ee795d799da493110fd63ff1ad1544fabcf94640c5415"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Polites\nRequest for Comments: 1986 W. Wollman\nCategory: Experimental D. Woo\n The MITRE Corporation\n R. Langan\n U.S. ARMY CECOM\n August 1996\n\n Experiments with a Simple File Transfer Protocol for Radio Links\n using Enhanced Trivial File Transfer Protocol (ETFTP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION SECTION\n\n This document is a description of the Enhanced Trivial File Transfer\n Protocol (ETFTP). This protocol is an experimental implementation of\n the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file\n transfer application program. It uses the User Datagram Protocol\n (UDP), RFC 768 [2], as its transport layer. The two pr","scope_keywords":["1986"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1986 Network Working Group W. Polites\nRequest for Comments: 1986 W. Wollman\nCategory: Experimental D. Woo\n The MITRE Corporation\n R. Langan\n U.S. ARMY CECOM\n August 1996\n\n Experiments with a Simple File Transfer Protocol for Radio Links\n using Enhanced Trivial File Transfer Protocol (ETFTP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION SECTION\n\n This document is a description of the Enhanced Trivial File Transfer\n Protocol (ETFTP). This protocol is an experimental implementation of\n the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file\n transfer application program. It uses the User Datagram Protocol\n (UDP), RFC 768 [2], as its transport layer. The two pr 1986 nested-reference unchanged"},{"id":"IETF RFC 2757","type":"specification","body":"IETF","designation":"RFC 2757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2757.txt","https://www.rfc-editor.org/rfc/rfc2757.pdf"],"folder":"IETF/RFC-2757","files":{"txt":{"path":"standards/IETF/RFC-2757/RFC-2757.txt","sha256":"d20b98464d57810730d61f6782e65e6fc43e4c6c6e203e0908ee4d4a1d84641a"}},"tags":["nested-reference","unchanged"],"summary":"In view of the unpredictable and problematic nature of long thin\n networks (for example, wireless WANs), arriving at an optimized\n transport is a daunting task. We have reviewed the existing\n proposals along with future research items. Based on this overview,\n we also recommend mechanisms for implementation in long thin\n networks.\n\n Our goal is to identify a TCP that works for all users, including\n users of long thin networks. We started from the working\n recommendations of the IETF TCP Over Satellite Links (tcpsat) working\n group with this end in mind.\n\n We recognize that not every tcpsat recommendation will be required\n for long thin networks as well, and work toward a set of TCP\n recommendations that are 'benign' in environments that do not require\n them.\n\nMontenegro, et al. Informational [Page 1]\n\f\nRFC 2757 Long Thin Networks January 2000","scope_keywords":["2757","algorithm","algorithms","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2757 In view of the unpredictable and problematic nature of long thin\n networks (for example, wireless WANs), arriving at an optimized\n transport is a daunting task. We have reviewed the existing\n proposals along with future research items. Based on this overview,\n we also recommend mechanisms for implementation in long thin\n networks.\n\n Our goal is to identify a TCP that works for all users, including\n users of long thin networks. We started from the working\n recommendations of the IETF TCP Over Satellite Links (tcpsat) working\n group with this end in mind.\n\n We recognize that not every tcpsat recommendation will be required\n for long thin networks as well, and work toward a set of TCP\n recommendations that are 'benign' in environments that do not require\n them.\n\nMontenegro, et al. Informational [Page 1]\n\f\nRFC 2757 Long Thin Networks January 2000 2757 algorithm algorithms management path nested-reference unchanged"},{"id":"IETF RFC 1031","type":"specification","body":"IETF","designation":"RFC 1031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1031.txt","https://www.rfc-editor.org/rfc/rfc1031.pdf"],"folder":"IETF/RFC-1031","files":{"txt":{"path":"standards/IETF/RFC-1031/RFC-1031.txt","sha256":"b4421b3f35c96e9e365999548e032dc993589297d278a060fa92af115abf5cdc"}},"tags":["nested-reference","unchanged"],"summary":"Networking Working Group W. Lazear\nRequest for Comments: 1031 MITRE\n November 1987\n\n MILNET NAME DOMAIN TRANSITION\n\nSTATUS OF THIS MEMO\n\n This RFC consolidates information necessary for the implementation of\n domain style names throughout the DDN/MILNET Internet community.\n Although no official policy has been published, the introduction of\n domain style names will impact all hosts in the DDN/MILNET Internet.\n The RFC is designed as an aid to implementors and administrators by\n providing 1) an overview of the transition process from host tables\n to domains, 2) a potential timetable for the transition, and 3)\n references to documentation and software relating to the DDN/ARPANET\n domain system. Distribution of this RFC is unlimited.\n\nBACKGROUND\n\n All MILNET hosts are expected to have a way of translating the name\n of any other host into its Internet address. Although the current\n method of","scope_keywords":["1031","management","path","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null}],"search_text":"IETF RFC 1031 Networking Working Group W. Lazear\nRequest for Comments: 1031 MITRE\n November 1987\n\n MILNET NAME DOMAIN TRANSITION\n\nSTATUS OF THIS MEMO\n\n This RFC consolidates information necessary for the implementation of\n domain style names throughout the DDN/MILNET Internet community.\n Although no official policy has been published, the introduction of\n domain style names will impact all hosts in the DDN/MILNET Internet.\n The RFC is designed as an aid to implementors and administrators by\n providing 1) an overview of the transition process from host tables\n to domains, 2) a potential timetable for the transition, and 3)\n references to documentation and software relating to the DDN/ARPANET\n domain system. Distribution of this RFC is unlimited.\n\nBACKGROUND\n\n All MILNET hosts are expected to have a way of translating the name\n of any other host into its Internet address. Although the current\n method of 1031 management path policy registered nested-reference unchanged"},{"id":"IETF RFC 1183","type":"specification","body":"IETF","designation":"RFC 1183","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1183.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1183.txt","https://www.rfc-editor.org/rfc/rfc1183.pdf"],"folder":"IETF/RFC-1183","files":{"txt":{"path":"standards/IETF/RFC-1183/RFC-1183.txt","sha256":"92024f23cf133e81fb98d6cccf08628074176a7dd733e615ce882849557f495c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Everhart\nRequest for Comments: 1183 Transarc\nUpdates: RFCs 1034, 1035 L. Mamakos\n University of Maryland\n R. Ullmann\n Prime Computer\n P. Mockapetris, Editor\n ISI\n October 1990\n\n New DNS RR Definitions\n\nStatus of this Memo\n\n This memo defines five new DNS types for experimental purposes. This\n RFC describes an Experimental Protocol for the Internet community,\n and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction.................................................... 1\n 1. AFS Data Base location....................................... 2\n 2. Responsible Person........................................... 3\n 2.1. Identification of the guilty party......................... 3\n 2.2. The Responsible Person RR.................................. 4\n 3. X.25 and ISDN addresses, Route Binding............","scope_keywords":["1183","identification","key","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null}],"search_text":"IETF RFC 1183 Network Working Group C. Everhart\nRequest for Comments: 1183 Transarc\nUpdates: RFCs 1034, 1035 L. Mamakos\n University of Maryland\n R. Ullmann\n Prime Computer\n P. Mockapetris, Editor\n ISI\n October 1990\n\n New DNS RR Definitions\n\nStatus of this Memo\n\n This memo defines five new DNS types for experimental purposes. This\n RFC describes an Experimental Protocol for the Internet community,\n and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction.................................................... 1\n 1. AFS Data Base location....................................... 2\n 2. Responsible Person........................................... 3\n 2.1. Identification of the guilty party......................... 3\n 2.2. The Responsible Person RR.................................. 4\n 3. X.25 and ISDN addresses, Route Binding............ 1183 identification key presentation registered nested-reference unchanged"},{"id":"IETF RFC 1348","type":"specification","body":"IETF","designation":"RFC 1348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1348.txt","https://www.rfc-editor.org/rfc/rfc1348.pdf"],"folder":"IETF/RFC-1348","files":{"txt":{"path":"standards/IETF/RFC-1348/RFC-1348.txt","sha256":"47d153c9882f1e69f87d583aa151980e7cd0dd2560a5b106229da8c179cf4b19"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Manning\nRequest for Comments: 1348 Rice University\nUpdates: RFCs 1034, 1035 July 1992\n\n DNS NSAP RRs\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ..................................................... 1\n Background ....................................................... 1\n NSAP RR .......................................................... 2\n NSAP-PTR RR ...................................................... 2\n REFERENCES and BIBLIOGRAPHY ...................................... 3\n Security Considerations .......................................... 4\n A","scope_keywords":["1348","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null}],"search_text":"IETF RFC 1348 Network Working Group B. Manning\nRequest for Comments: 1348 Rice University\nUpdates: RFCs 1034, 1035 July 1992\n\n DNS NSAP RRs\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n Introduction ..................................................... 1\n Background ....................................................... 1\n NSAP RR .......................................................... 2\n NSAP-PTR RR ...................................................... 2\n REFERENCES and BIBLIOGRAPHY ...................................... 3\n Security Considerations .......................................... 4\n A 1348 presentation nested-reference unchanged"},{"id":"IETF RFC 1464","type":"specification","body":"IETF","designation":"RFC 1464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1464.txt","https://www.rfc-editor.org/rfc/rfc1464.pdf"],"folder":"IETF/RFC-1464","files":{"txt":{"path":"standards/IETF/RFC-1464/RFC-1464.txt","sha256":"8c6af5118ce8c2ae4efe18a63a31910299052453d2df889592ae06dbf3108a92"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Rosenbaum\nRequest for Comments: 1464 Digital Equipment Corporation\n May 1993\n\n Using the Domain Name System\n To Store Arbitrary String Attributes\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n While the Domain Name System (DNS) [2,3] is generally used to store\n predefined types of information (e.g., addresses of hosts), it is\n possible to use it to store information that has not been previously\n classified.\n\n This paper describes a simple means to associate arbitrary string\n information (ASCII text) with attributes that have not been defined\n by the DNS. It uses DNS TXT r","scope_keywords":["1464","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 1464 Network Working Group R. Rosenbaum\nRequest for Comments: 1464 Digital Equipment Corporation\n May 1993\n\n Using the Domain Name System\n To Store Arbitrary String Attributes\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n While the Domain Name System (DNS) [2,3] is generally used to store\n predefined types of information (e.g., addresses of hosts), it is\n possible to use it to store information that has not been previously\n classified.\n\n This paper describes a simple means to associate arbitrary string\n information (ASCII text) with attributes that have not been defined\n by the DNS. It uses DNS TXT r 1464 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 1480","type":"specification","body":"IETF","designation":"RFC 1480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1480.txt","https://www.rfc-editor.org/rfc/rfc1480.pdf"],"folder":"IETF/RFC-1480","files":{"txt":{"path":"standards/IETF/RFC-1480/RFC-1480.txt","sha256":"b4d216d545899874b1d1c1e4063621d6d878273bbf797c58264aa26a5f6c155b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Cooper\nRequest for Comments: 1480 J. Postel\nObsoletes: 1386 June 1993\n\n The US Domain\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 The Internet Domain Name System......................... 2\n 1.2 Top-Level Domains....................................... 3\n 1.3 The US Domain .......................................... 4\n 2. Naming Structure ............................................ 4\n 2.1 State Codes ............................................ 8\n 2.2 Locality Names.......................................... 8\n 2.3 Schools ................................................ 10\n 2.4 State Agencies.......................................... 15\n 2.5 Federal Agen","scope_keywords":["1480","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null}],"search_text":"IETF RFC 1480 Network Working Group A. Cooper\nRequest for Comments: 1480 J. Postel\nObsoletes: 1386 June 1993\n\n The US Domain\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 The Internet Domain Name System......................... 2\n 1.2 Top-Level Domains....................................... 3\n 1.3 The US Domain .......................................... 4\n 2. Naming Structure ............................................ 4\n 2.1 State Codes ............................................ 8\n 2.2 Locality Names.......................................... 8\n 2.3 Schools ................................................ 10\n 2.4 State Agencies.......................................... 15\n 2.5 Federal Agen 1480 registered nested-reference unchanged"},{"id":"IETF RFC 2052","type":"specification","body":"IETF","designation":"RFC 2052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2052.txt","https://www.rfc-editor.org/rfc/rfc2052.pdf"],"folder":"IETF/RFC-2052","files":{"txt":{"path":"standards/IETF/RFC-2052/RFC-2052.txt","sha256":"ca14367575f98a20a355c6ea6e19a31b4dc47cb2ecdf246cb623f8b7f2d8503c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Gulbrandsen\nRequest for Comments: 2052 Troll Technologies\nUpdates: 1035, 1183 P. Vixie\nCategory: Experimental Vixie Enterprises\n October 1996\n\n A DNS RR for specifying the location of services (DNS SRV)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes a DNS RR which specifies the location of the\n server(s) for a specific protocol and domain (like a more general\n form of MX).\n\nOverview and rationale\n\n Currently, one must either know the exact address of a server to\n contact it, or broadcast a question. This has led to, for example,\n ftp.whatever.com aliases, the SMTP-specific MX RR, and using MAC-\n level broadcasts to locate ","scope_keywords":["2052","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 2052 Network Working Group A. Gulbrandsen\nRequest for Comments: 2052 Troll Technologies\nUpdates: 1035, 1183 P. Vixie\nCategory: Experimental Vixie Enterprises\n October 1996\n\n A DNS RR for specifying the location of services (DNS SRV)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes a DNS RR which specifies the location of the\n server(s) for a specific protocol and domain (like a more general\n form of MX).\n\nOverview and rationale\n\n Currently, one must either know the exact address of a server to\n contact it, or broadcast a question. This has led to, for example,\n ftp.whatever.com aliases, the SMTP-specific MX RR, and using MAC-\n level broadcasts to locate  2052 http nested-reference unchanged"},{"id":"IETF RFC 2065","type":"specification","body":"IETF","designation":"RFC 2065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2065.txt","https://www.rfc-editor.org/rfc/rfc2065.pdf"],"folder":"IETF/RFC-2065","files":{"txt":{"path":"standards/IETF/RFC-2065/RFC-2065.txt","sha256":"46710499fbdb02d9ad7ddfb3279338a073054b1765b36ff8615f96bbd1da5656"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) has become a critical operational part\n of the Internet infrastructure yet it has no strong security\n mechanisms to assure data integrity or authentication. Extensions to\n the DNS are described that provide these services to security aware\n resolvers or applications through the use of cryptographic digital\n signatures. These digital signatures are included in secured zones\n as resource records. Security can still be provided even through\n non-security aware DNS servers in many cases.\n\n The extensions also provide for the storage of authenticated public\n keys in the DNS. This storage of keys can support general public key\n distribution service as well as DNS security. The stored keys enable\n security aware resolvers to learn the authenticating key of zones in\n addition to those for which they are initially configured. Keys\n associated with DNS names can be ret","scope_keywords":["2065","algorithm","algorithms","authentication","key","keys","presentation","signature","signatures","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2137","folder":"IETF/RFC-2137","source":"IETF/RFC-2137/RFC-2137.txt","version":null},{"body":"IETF","designation":"RFC 2154","folder":"IETF/RFC-2154","source":"IETF/RFC-2154/RFC-2154.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2181","folder":"IETF/RFC-2181","source":"IETF/RFC-2181/RFC-2181.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2308","folder":"IETF/RFC-2308","source":"IETF/RFC-2308/RFC-2308.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2412","folder":"IETF/RFC-2412","source":"IETF/RFC-2412/RFC-2412.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2673","folder":"IETF/RFC-2673","source":"IETF/RFC-2673/RFC-2673.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 2065 The Domain Name System (DNS) has become a critical operational part\n of the Internet infrastructure yet it has no strong security\n mechanisms to assure data integrity or authentication. Extensions to\n the DNS are described that provide these services to security aware\n resolvers or applications through the use of cryptographic digital\n signatures. These digital signatures are included in secured zones\n as resource records. Security can still be provided even through\n non-security aware DNS servers in many cases.\n\n The extensions also provide for the storage of authenticated public\n keys in the DNS. This storage of keys can support general public key\n distribution service as well as DNS security. The stored keys enable\n security aware resolvers to learn the authenticating key of zones in\n addition to those for which they are initially configured. Keys\n associated with DNS names can be ret 2065 algorithm algorithms authentication key keys presentation signature signatures tls nested-reference unchanged"},{"id":"IETF RFC 1033","type":"specification","body":"IETF","designation":"RFC 1033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1033.txt","https://www.rfc-editor.org/rfc/rfc1033.pdf"],"folder":"IETF/RFC-1033","files":{"txt":{"path":"standards/IETF/RFC-1033/RFC-1033.txt","sha256":"4bd845af36729d9000c0dd6332fb22e1731b0219c5ae2c53ab0bc830cc06fbb8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Lottor\nRequest For Comments: 1033 SRI International\n November 1987\n\n DOMAIN ADMINISTRATORS OPERATIONS GUIDE\n\nSTATUS OF THIS MEMO\n\n This RFC provides guidelines for domain administrators in operating a\n domain server and maintaining their portion of the hierarchical\n database. Familiarity with the domain system is assumed.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENTS\n\n This memo is a formatted collection of notes and excerpts from the\n references listed at the end of this document. Of particular mention\n are Paul Mockapetris and Kevin Dunlap.\n\nINTRODUCTION\n\n A domain server requires a few files to get started. It will\n normally have some number of boot/startup files (also known as the\n \"safety belt\" files). One section will contain a list of possible\n root servers that the server will use to find the up-to-date list of\n root servers. Another section w","scope_keywords":["1033","qualified","risk","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 1033 Network Working Group M. Lottor\nRequest For Comments: 1033 SRI International\n November 1987\n\n DOMAIN ADMINISTRATORS OPERATIONS GUIDE\n\nSTATUS OF THIS MEMO\n\n This RFC provides guidelines for domain administrators in operating a\n domain server and maintaining their portion of the hierarchical\n database. Familiarity with the domain system is assumed.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENTS\n\n This memo is a formatted collection of notes and excerpts from the\n references listed at the end of this document. Of particular mention\n are Paul Mockapetris and Kevin Dunlap.\n\nINTRODUCTION\n\n A domain server requires a few files to get started. It will\n normally have some number of boot/startup files (also known as the\n \"safety belt\" files). One section will contain a list of possible\n root servers that the server will use to find the up-to-date list of\n root servers. Another section w 1033 qualified risk tls nested-reference unchanged"},{"id":"IETF RFC 1537","type":"specification","body":"IETF","designation":"RFC 1537","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1537.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1537.txt","https://www.rfc-editor.org/rfc/rfc1537.pdf"],"folder":"IETF/RFC-1537","files":{"txt":{"path":"standards/IETF/RFC-1537/RFC-1537.txt","sha256":"2ae488f1f37b2fb86862f40ac75850e6dba0ab1112f700bbe8b17c5f9cb73084"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes errors often found in DNS data files. It points\n out common mistakes system administrators tend to make and why they\n often go unnoticed for long periods of time.","scope_keywords":["1537"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1535","folder":"IETF/RFC-1535","source":"IETF/RFC-1535/RFC-1535.txt","version":null},{"body":"IETF","designation":"RFC 1536","folder":"IETF/RFC-1536","source":"IETF/RFC-1536/RFC-1536.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null}],"search_text":"IETF RFC 1537 This memo describes errors often found in DNS data files. It points\n out common mistakes system administrators tend to make and why they\n often go unnoticed for long periods of time. 1537 nested-reference unchanged"},{"id":"IETF RFC 1664","type":"specification","body":"IETF","designation":"RFC 1664","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1664.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1664.txt","https://www.rfc-editor.org/rfc/rfc1664.pdf"],"folder":"IETF/RFC-1664","files":{"txt":{"path":"standards/IETF/RFC-1664/RFC-1664.txt","sha256":"5c5004ee9cc4a005ce69ad9468e5da9e302dc21ab4e669836df9efb3edf32d60"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines how to store in the Internet Domain Name System the\n mapping information needed by e-mail gateways and other tools to map\n RFC822 domain names into X.400 O/R names and vice versa. Mapping\n information can be managed in a distributed rather than a centralised\n way. Gateways located on Internet hosts can retrieve the mapping\n information querying the DNS instead of having fixed tables which\n need to be centrally updated and distributed. This memo is a joint\n effort of X400 operation working group (x400ops) and RARE Mail and\n Messaging working group (WG-MSG).\n\n1. Introduction\n\n The connectivity between the Internet SMTP mail and other mail\n services, including the Internet X.400 mail and the commercial X.400\n service providers, is assured by the Mail eXchanger (MX) record\n information distributed via the Internet Domain Name System (DNS). A\n number of documents then specif","scope_keywords":["1664","algorithm","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null}],"search_text":"IETF RFC 1664 This memo defines how to store in the Internet Domain Name System the\n mapping information needed by e-mail gateways and other tools to map\n RFC822 domain names into X.400 O/R names and vice versa. Mapping\n information can be managed in a distributed rather than a centralised\n way. Gateways located on Internet hosts can retrieve the mapping\n information querying the DNS instead of having fixed tables which\n need to be centrally updated and distributed. This memo is a joint\n effort of X400 operation working group (x400ops) and RARE Mail and\n Messaging working group (WG-MSG).\n\n1. Introduction\n\n The connectivity between the Internet SMTP mail and other mail\n services, including the Internet X.400 mail and the commercial X.400\n service providers, is assured by the Mail eXchanger (MX) record\n information distributed via the Internet Domain Name System (DNS). A\n number of documents then specif 1664 algorithm management nested-reference unchanged"},{"id":"IETF RFC 1912","type":"specification","body":"IETF","designation":"RFC 1912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1912.txt","https://www.rfc-editor.org/rfc/rfc1912.pdf"],"folder":"IETF/RFC-1912","files":{"txt":{"path":"standards/IETF/RFC-1912/RFC-1912.txt","sha256":"2278c1f213c4ce552f87879b1ff3d94e3733f0a45870adf97efee13cfe5f379f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes errors often found in both the operation of\n Domain Name System (DNS) servers, and in the data that these DNS\n servers contain. This memo tries to summarize current Internet\n requirements as well as common practice in the operation and\n configuration of the DNS. This memo also tries to summarize or\n expand upon issues raised in [RFC 1537].\n\n1. Introduction\n\n Running a nameserver is not a trivial task. There are many things\n that can go wrong, and many decisions have to be made about what data\n to put in the DNS and how to set up servers. This memo attempts to\n address many of the common mistakes and pitfalls that are made in DNS\n data as well as in the operation of nameservers. Discussions are\n also made regarding some other relevant issues such as server or\n resolver bugs, and a few political issues with respect to the\n operation of DNS on the Internet.\n\n2. DNS Data\n","scope_keywords":["1912","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1912 This memo describes errors often found in both the operation of\n Domain Name System (DNS) servers, and in the data that these DNS\n servers contain. This memo tries to summarize current Internet\n requirements as well as common practice in the operation and\n configuration of the DNS. This memo also tries to summarize or\n expand upon issues raised in [RFC 1537].\n\n1. Introduction\n\n Running a nameserver is not a trivial task. There are many things\n that can go wrong, and many decisions have to be made about what data\n to put in the DNS and how to set up servers. This memo attempts to\n address many of the common mistakes and pitfalls that are made in DNS\n data as well as in the operation of nameservers. Discussions are\n also made regarding some other relevant issues such as server or\n resolver bugs, and a few political issues with respect to the\n operation of DNS on the Internet.\n\n2. DNS Data\n 1912 registered nested-reference unchanged"},{"id":"IETF RFC 2142","type":"specification","body":"IETF","designation":"RFC 2142","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2142.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2142.txt","https://www.rfc-editor.org/rfc/rfc2142.pdf"],"folder":"IETF/RFC-2142","files":{"txt":{"path":"standards/IETF/RFC-2142/RFC-2142.txt","sha256":"99a436105faa5a703fff3c4aee7e0d96c917950a170baa6cf8ee10c4b3616241"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker\nRequest for Comments: 2142 Internet Mail Consortium\nCategory: Standards Track May 1997\n\n MAILBOX NAMES FOR\n COMMON SERVICES, ROLES AND FUNCTIONS\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nABSTRACT\n\n This specification enumerates and describes Internet mail addresses\n (mailbox name @ host reference) to be used when contacting personnel\n at an organization. Mailbox names are provided for both operations\n and business functions. Additional mailbox names and aliases are not\n prohibited, but organizations which support email exchanges with the\n ","scope_keywords":["2142","delivery","http","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2369","folder":"IETF/RFC-2369","source":"IETF/RFC-2369/RFC-2369.txt","version":null},{"body":"IETF","designation":"RFC 2489","folder":"IETF/RFC-2489","source":"IETF/RFC-2489/RFC-2489.txt","version":null},{"body":"IETF","designation":"RFC 2635","folder":"IETF/RFC-2635","source":"IETF/RFC-2635/RFC-2635.txt","version":null},{"body":"IETF","designation":"RFC 2939","folder":"IETF/RFC-2939","source":"IETF/RFC-2939/RFC-2939.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null}],"search_text":"IETF RFC 2142 Network Working Group D. Crocker\nRequest for Comments: 2142 Internet Mail Consortium\nCategory: Standards Track May 1997\n\n MAILBOX NAMES FOR\n COMMON SERVICES, ROLES AND FUNCTIONS\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nABSTRACT\n\n This specification enumerates and describes Internet mail addresses\n (mailbox name @ host reference) to be used when contacting personnel\n at an organization. Mailbox names are provided for both operations\n and business functions. Additional mailbox names and aliases are not\n prohibited, but organizations which support email exchanges with the\n  2142 delivery http management path nested-reference unchanged"},{"id":"IETF RFC 2163","type":"specification","body":"IETF","designation":"RFC 2163","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2163.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2163.txt","https://www.rfc-editor.org/rfc/rfc2163.pdf"],"folder":"IETF/RFC-2163","files":{"txt":{"path":"standards/IETF/RFC-2163/RFC-2163.txt","sha256":"8604f13ebbb3c4938c188fed17bd1062cd7d749923eb0a31ca5cc950ecab67c8"}},"tags":["nested-reference","unchanged"],"summary":"This memo is the complete technical specification to store in the\n Internet Domain Name System (DNS) the mapping information (MCGAM)\n needed by MIXER conformant e-mail gateways and other tools to map\n RFC822 domain names into X.400 O/R names and vice versa. Mapping\n information can be managed in a distributed rather than a centralised\n way. Organizations can publish their MIXER mapping or preferred\n gateway routing information using just local resources (their local\n DNS server), avoiding the need for a strong coordination with any\n centralised organization. MIXER conformant gateways and tools located\n on Internet hosts can retrieve the mapping information querying the\n DNS instead of having fixed tables which need to be centrally updated\n and distributed.\n\n This memo obsoletes RFC1664. It includes the changes introduced by\n MIXER specification with respect to RFC1327: the new 'gate1' (O","scope_keywords":["2163","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null}],"search_text":"IETF RFC 2163 This memo is the complete technical specification to store in the\n Internet Domain Name System (DNS) the mapping information (MCGAM)\n needed by MIXER conformant e-mail gateways and other tools to map\n RFC822 domain names into X.400 O/R names and vice versa. Mapping\n information can be managed in a distributed rather than a centralised\n way. Organizations can publish their MIXER mapping or preferred\n gateway routing information using just local resources (their local\n DNS server), avoiding the need for a strong coordination with any\n centralised organization. MIXER conformant gateways and tools located\n on Internet hosts can retrieve the mapping information querying the\n DNS instead of having fixed tables which need to be centrally updated\n and distributed.\n\n This memo obsoletes RFC1664. It includes the changes introduced by\n MIXER specification with respect to RFC1327: the new 'gate1' (O 2163 algorithm nested-reference unchanged"},{"id":"IETF RFC 2535","type":"specification","body":"IETF","designation":"RFC 2535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2535.txt","https://www.rfc-editor.org/rfc/rfc2535.pdf"],"folder":"IETF/RFC-2535","files":{"txt":{"path":"standards/IETF/RFC-2535/RFC-2535.txt","sha256":"70f74879daccb842a383ccf543408df9afe90ff1aa5e36379d7a57d6389ac6a3"}},"tags":["nested-reference","unchanged"],"summary":"Extensions to the Domain Name System (DNS) are described that provide\n data integrity and authentication to security aware resolvers and\n applications through the use of cryptographic digital signatures.\n These digital signatures are included in secured zones as resource\n records. Security can also be provided through non-security aware\n DNS servers in some cases.\n\n The extensions provide for the storage of authenticated public keys\n in the DNS. This storage of keys can support general public key\n distribution services as well as DNS security. The stored keys\n enable security aware resolvers to learn the authenticating key of\n zones in addition to those for which they are initially configured.\n Keys associated with DNS names can be retrieved to support other\n protocols. Provision is made for a variety of key types and\n algorithms.\n\n In addition, the security extensions provide for the op","scope_keywords":["2535","algorithm","algorithms","authentication","key","keys","presentation","signature","signatures","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2536","folder":"IETF/RFC-2536","source":"IETF/RFC-2536/RFC-2536.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2539","folder":"IETF/RFC-2539","source":"IETF/RFC-2539/RFC-2539.txt","version":null},{"body":"IETF","designation":"RFC 2540","folder":"IETF/RFC-2540","source":"IETF/RFC-2540/RFC-2540.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2826","folder":"IETF/RFC-2826","source":"IETF/RFC-2826/RFC-2826.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3225","folder":"IETF/RFC-3225","source":"IETF/RFC-3225/RFC-3225.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3445","folder":"IETF/RFC-3445","source":"IETF/RFC-3445/RFC-3445.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3757","folder":"IETF/RFC-3757","source":"IETF/RFC-3757/RFC-3757.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 2535 Extensions to the Domain Name System (DNS) are described that provide\n data integrity and authentication to security aware resolvers and\n applications through the use of cryptographic digital signatures.\n These digital signatures are included in secured zones as resource\n records. Security can also be provided through non-security aware\n DNS servers in some cases.\n\n The extensions provide for the storage of authenticated public keys\n in the DNS. This storage of keys can support general public key\n distribution services as well as DNS security. The stored keys\n enable security aware resolvers to learn the authenticating key of\n zones in addition to those for which they are initially configured.\n Keys associated with DNS names can be retrieved to support other\n protocols. Provision is made for a variety of key types and\n algorithms.\n\n In addition, the security extensions provide for the op 2535 algorithm algorithms authentication key keys presentation signature signatures tls nested-reference unchanged"},{"id":"IETF RFC 5592","type":"specification","body":"IETF","designation":"RFC 5592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5592.txt","https://www.rfc-editor.org/rfc/rfc5592.pdf"],"folder":"IETF/RFC-5592","files":{"txt":{"path":"standards/IETF/RFC-5592/RFC-5592.txt","sha256":"285a20651196723e0b44f10169ad6bb95c90eaa2faa0f0d11064681c5d65692e"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a Transport Model for the Simple Network\n Management Protocol (SNMP), using the Secure Shell (SSH) protocol.\n\n This memo also defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for monitoring and\n managing the Secure Shell Transport Model for SNMP.","scope_keywords":["5592","algorithm","authentication","authorization","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null}],"search_text":"IETF RFC 5592 This memo describes a Transport Model for the Simple Network\n Management Protocol (SNMP), using the Secure Shell (SSH) protocol.\n\n This memo also defines a portion of the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for monitoring and\n managing the Secure Shell Transport Model for SNMP. 5592 algorithm authentication authorization http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5953","type":"specification","body":"IETF","designation":"RFC 5953","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5953.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5953.txt","https://www.rfc-editor.org/rfc/rfc5953.pdf"],"folder":"IETF/RFC-5953","files":{"txt":{"path":"standards/IETF/RFC-5953/RFC-5953.txt","sha256":"3f63c9ec70af3ffa0a2a7b06a2c5ce44c339f47034b7efdf698d87f7dd325845"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Transport Model for the Simple Network\n Management Protocol (SNMP), that uses either the Transport Layer\n Security protocol or the Datagram Transport Layer Security (DTLS)\n protocol. The TLS and DTLS protocols provide authentication and\n privacy services for SNMP applications. This document describes how\n the TLS Transport Model (TLSTM) implements the needed features of a\n SNMP Transport Subsystem to make this protection possible in an\n interoperable way.\n\n This Transport Model is designed to meet the security and operational\n needs of network administrators. It supports the sending of SNMP\n messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of\n TCP's improved support for larger packet sizes and the DTLS mode\n provides potentially superior operation in environments where a\n connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS\n integrat","scope_keywords":["5953","authentication","authorization","certificate","certificates","credential","http","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5953 This document describes a Transport Model for the Simple Network\n Management Protocol (SNMP), that uses either the Transport Layer\n Security protocol or the Datagram Transport Layer Security (DTLS)\n protocol. The TLS and DTLS protocols provide authentication and\n privacy services for SNMP applications. This document describes how\n the TLS Transport Model (TLSTM) implements the needed features of a\n SNMP Transport Subsystem to make this protection possible in an\n interoperable way.\n\n This Transport Model is designed to meet the security and operational\n needs of network administrators. It supports the sending of SNMP\n messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of\n TCP's improved support for larger packet sizes and the DTLS mode\n provides potentially superior operation in environments where a\n connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS\n integrat 5953 authentication authorization certificate certificates credential http key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6353","type":"specification","body":"IETF","designation":"RFC 6353","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6353.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6353.txt","https://www.rfc-editor.org/rfc/rfc6353.pdf"],"folder":"IETF/RFC-6353","files":{"txt":{"path":"standards/IETF/RFC-6353/RFC-6353.txt","sha256":"da43536089f6bb06ad7dc9d7feb6ead586177f109f13133ae71ddb8e644dcf61"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Transport Model for the Simple Network\n Management Protocol (SNMP), that uses either the Transport Layer\n Security protocol or the Datagram Transport Layer Security (DTLS)\n protocol. The TLS and DTLS protocols provide authentication and\n privacy services for SNMP applications. This document describes how\n the TLS Transport Model (TLSTM) implements the needed features of an\n SNMP Transport Subsystem to make this protection possible in an\n interoperable way.\n\n This Transport Model is designed to meet the security and operational\n needs of network administrators. It supports the sending of SNMP\n messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of\n TCP's improved support for larger packet sizes and the DTLS mode\n provides potentially superior operation in environments where a\n connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS\n integra","scope_keywords":["6353","authentication","authorization","certificate","certificates","credential","http","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6353 This document describes a Transport Model for the Simple Network\n Management Protocol (SNMP), that uses either the Transport Layer\n Security protocol or the Datagram Transport Layer Security (DTLS)\n protocol. The TLS and DTLS protocols provide authentication and\n privacy services for SNMP applications. This document describes how\n the TLS Transport Model (TLSTM) implements the needed features of an\n SNMP Transport Subsystem to make this protection possible in an\n interoperable way.\n\n This Transport Model is designed to meet the security and operational\n needs of network administrators. It supports the sending of SNMP\n messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of\n TCP's improved support for larger packet sizes and the DTLS mode\n provides potentially superior operation in environments where a\n connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS\n integra 6353 authentication authorization certificate certificates credential http key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 1034","type":"specification","body":"IETF","designation":"RFC 1034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1034.txt","https://www.rfc-editor.org/rfc/rfc1034.pdf"],"folder":"IETF/RFC-1034","files":{"txt":{"path":"standards/IETF/RFC-1034/RFC-1034.txt","sha256":"d6b10a71441df879cc2817d23f2dad120c8a5f87e74eba1e4ed4b743a76a891a"}},"tags":["nested-reference","unchanged"],"summary":"database systems.","scope_keywords":["1034","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1107","folder":"IETF/RFC-1107","source":"IETF/RFC-1107/RFC-1107.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1178","folder":"IETF/RFC-1178","source":"IETF/RFC-1178/RFC-1178.txt","version":null},{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1274","folder":"IETF/RFC-1274","source":"IETF/RFC-1274/RFC-1274.txt","version":null},{"body":"IETF","designation":"RFC 1279","folder":"IETF/RFC-1279","source":"IETF/RFC-1279/RFC-1279.txt","version":null},{"body":"IETF","designation":"RFC 1287","folder":"IETF/RFC-1287","source":"IETF/RFC-1287/RFC-1287.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1436","folder":"IETF/RFC-1436","source":"IETF/RFC-1436/RFC-1436.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1464","folder":"IETF/RFC-1464","source":"IETF/RFC-1464/RFC-1464.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 1486","folder":"IETF/RFC-1486","source":"IETF/RFC-1486/RFC-1486.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1535","folder":"IETF/RFC-1535","source":"IETF/RFC-1535/RFC-1535.txt","version":null},{"body":"IETF","designation":"RFC 1536","folder":"IETF/RFC-1536","source":"IETF/RFC-1536/RFC-1536.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1630","folder":"IETF/RFC-1630","source":"IETF/RFC-1630/RFC-1630.txt","version":null},{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null},{"body":"IETF","designation":"RFC 1712","folder":"IETF/RFC-1712","source":"IETF/RFC-1712/RFC-1712.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1788","folder":"IETF/RFC-1788","source":"IETF/RFC-1788/RFC-1788.txt","version":null},{"body":"IETF","designation":"RFC 1798","folder":"IETF/RFC-1798","source":"IETF/RFC-1798/RFC-1798.txt","version":null},{"body":"IETF","designation":"RFC 1876","folder":"IETF/RFC-1876","source":"IETF/RFC-1876/RFC-1876.txt","version":null},{"body":"IETF","designation":"RFC 1877","folder":"IETF/RFC-1877","source":"IETF/RFC-1877/RFC-1877.txt","version":null},{"body":"IETF","designation":"RFC 1886","folder":"IETF/RFC-1886","source":"IETF/RFC-1886/RFC-1886.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 1982","folder":"IETF/RFC-1982","source":"IETF/RFC-1982/RFC-1982.txt","version":null},{"body":"IETF","designation":"RFC 1995","folder":"IETF/RFC-1995","source":"IETF/RFC-1995/RFC-1995.txt","version":null},{"body":"IETF","designation":"RFC 2016","folder":"IETF/RFC-2016","source":"IETF/RFC-2016/RFC-2016.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2137","folder":"IETF/RFC-2137","source":"IETF/RFC-2137/RFC-2137.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2181","folder":"IETF/RFC-2181","source":"IETF/RFC-2181/RFC-2181.txt","version":null},{"body":"IETF","designation":"RFC 2182","folder":"IETF/RFC-2182","source":"IETF/RFC-2182/RFC-2182.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2247","folder":"IETF/RFC-2247","source":"IETF/RFC-2247/RFC-2247.txt","version":null},{"body":"IETF","designation":"RFC 2280","folder":"IETF/RFC-2280","source":"IETF/RFC-2280/RFC-2280.txt","version":null},{"body":"IETF","designation":"RFC 2308","folder":"IETF/RFC-2308","source":"IETF/RFC-2308/RFC-2308.txt","version":null},{"body":"IETF","designation":"RFC 2317","folder":"IETF/RFC-2317","source":"IETF/RFC-2317/RFC-2317.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2536","folder":"IETF/RFC-2536","source":"IETF/RFC-2536/RFC-2536.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2539","folder":"IETF/RFC-2539","source":"IETF/RFC-2539/RFC-2539.txt","version":null},{"body":"IETF","designation":"RFC 2540","folder":"IETF/RFC-2540","source":"IETF/RFC-2540/RFC-2540.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2606","folder":"IETF/RFC-2606","source":"IETF/RFC-2606/RFC-2606.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2826","folder":"IETF/RFC-2826","source":"IETF/RFC-2826/RFC-2826.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3225","folder":"IETF/RFC-3225","source":"IETF/RFC-3225/RFC-3225.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3364","folder":"IETF/RFC-3364","source":"IETF/RFC-3364/RFC-3364.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3492","folder":"IETF/RFC-3492","source":"IETF/RFC-3492/RFC-3492.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4074","folder":"IETF/RFC-4074","source":"IETF/RFC-4074/RFC-4074.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4892","folder":"IETF/RFC-4892","source":"IETF/RFC-4892/RFC-4892.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 1034 database systems. 1034 management pid nested-reference unchanged"},{"id":"IETF RFC 1107","type":"specification","body":"IETF","designation":"RFC 1107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1107.txt","https://www.rfc-editor.org/rfc/rfc1107.pdf"],"folder":"IETF/RFC-1107","files":{"txt":{"path":"standards/IETF/RFC-1107/RFC-1107.txt","sha256":"fa85aedaef14c87e962ee461a747769e9017b4a7ef1828d466e0dd156625ab9b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Sollins\nRequest for Comments: 1107 M.I.T. Laboratory for Computer Science\n July 1989\n\n A Plan for Internet Directory Services\n\n Table of Contents\n\n 1. Introduction 1\n 1.1. The Issues 1\n 1.2. Project Summary 3\n 2. Goals and Requirements for a White Pages Service 6\n 3. Pre-existing Services 9\n 4. Proposed Approach 11\n 4.1. Stage 1: The Field Test 12\n 4.2. Stage 2: Implementation 17\n 4.3. Stage 3: Deployment 17\n 5. Conclusion 18\n\nStatus of this Memo\n\n This memo proposes a program to develop a directory service for the\n Internet. It reports the results of a meeting held in February 1989,\n which was convened to review requirements and options for such a\n service. This proposal is offered for comment, and does not\n represent a committed research activity of the Internet community.\n Activity in this area is anticipated, and comments should be provided\n promptly. Distrib","scope_keywords":["1107","attribute","attributes","delivery","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null}],"search_text":"IETF RFC 1107 Network Working Group K. Sollins\nRequest for Comments: 1107 M.I.T. Laboratory for Computer Science\n July 1989\n\n A Plan for Internet Directory Services\n\n Table of Contents\n\n 1. Introduction 1\n 1.1. The Issues 1\n 1.2. Project Summary 3\n 2. Goals and Requirements for a White Pages Service 6\n 3. Pre-existing Services 9\n 4. Proposed Approach 11\n 4.1. Stage 1: The Field Test 12\n 4.2. Stage 2: Implementation 17\n 4.3. Stage 3: Deployment 17\n 5. Conclusion 18\n\nStatus of this Memo\n\n This memo proposes a program to develop a directory service for the\n Internet. It reports the results of a meeting held in February 1989,\n which was convened to review requirements and options for such a\n service. This proposal is offered for comment, and does not\n represent a committed research activity of the Internet community.\n Activity in this area is anticipated, and comments should be provided\n promptly. Distrib 1107 attribute attributes delivery profile nested-reference unchanged"},{"id":"IETF RFC 1178","type":"specification","body":"IETF","designation":"RFC 1178","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1178.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1178.txt","https://www.rfc-editor.org/rfc/rfc1178.pdf"],"folder":"IETF/RFC-1178","files":{"txt":{"path":"standards/IETF/RFC-1178/RFC-1178.txt","sha256":"f2ccfa51646d5bf69d161585975cb6b0c6b1445aaed3997463ccbc62214a11ab"}},"tags":["nested-reference","unchanged"],"summary":"In order to easily distinguish between multiple computers, we give\n them names. Experience has taught us that it is as easy to choose\n bad names as it is to choose good ones. This essay presents\n guidelines for deciding what makes a name good or bad.\n\n Keywords: domain name system, naming conventions, computer\n administration, computer network management","scope_keywords":["1178","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1359","folder":"IETF/RFC-1359","source":"IETF/RFC-1359/RFC-1359.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null}],"search_text":"IETF RFC 1178 In order to easily distinguish between multiple computers, we give\n them names. Experience has taught us that it is as easy to choose\n bad names as it is to choose good ones. This essay presents\n guidelines for deciding what makes a name good or bad.\n\n Keywords: domain name system, naming conventions, computer\n administration, computer network management 1178 key management nested-reference unchanged"},{"id":"IETF RFC 1274","type":"specification","body":"IETF","designation":"RFC 1274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1274.txt","https://www.rfc-editor.org/rfc/rfc1274.pdf"],"folder":"IETF/RFC-1274","files":{"txt":{"path":"standards/IETF/RFC-1274/RFC-1274.txt","sha256":"9ca83727a602fb706705db748242e4131ee7588d899e0dbc7faacea0892b8a45"}},"tags":["nested-reference","unchanged"],"summary":"This document suggests an X.500 Directory Schema, or Naming\n Architecture, for use in the COSINE and Internet X.500 pilots. The\n schema is independent of any specific implementation. As well as\n indicating support for the standard object classes and attributes, a\n large number of generally useful object classes and attributes are\n also defined. An appendix to this document includes a machine\n processable version of the schema.\n\n This document also proposes a mechanism for allowing the schema to\n evolve in line with emerging requirements. Proformas to support this\n process are included.\n\n Corrections and additions to the schema should be sent to na-\n update@cs.ucl.ac.uk list, as described within.\n\n1. Introduction\n\n Directory Services are a fundamental requirement of both human and\n computer communications' systems. Human users need to be able to\n look up various details about other people","scope_keywords":["1274","attribute","attributes","authentication","presentation","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1279","folder":"IETF/RFC-1279","source":"IETF/RFC-1279/RFC-1279.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1384","folder":"IETF/RFC-1384","source":"IETF/RFC-1384/RFC-1384.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 1804","folder":"IETF/RFC-1804","source":"IETF/RFC-1804/RFC-1804.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3061","folder":"IETF/RFC-3061","source":"IETF/RFC-3061/RFC-3061.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null}],"search_text":"IETF RFC 1274 This document suggests an X.500 Directory Schema, or Naming\n Architecture, for use in the COSINE and Internet X.500 pilots. The\n schema is independent of any specific implementation. As well as\n indicating support for the standard object classes and attributes, a\n large number of generally useful object classes and attributes are\n also defined. An appendix to this document includes a machine\n processable version of the schema.\n\n This document also proposes a mechanism for allowing the schema to\n evolve in line with emerging requirements. Proformas to support this\n process are included.\n\n Corrections and additions to the schema should be sent to na-\n update@cs.ucl.ac.uk list, as described within.\n\n1. Introduction\n\n Directory Services are a fundamental requirement of both human and\n computer communications' systems. Human users need to be able to\n look up various details about other people 1274 attribute attributes authentication presentation qualified nested-reference unchanged"},{"id":"IETF RFC 1279","type":"specification","body":"IETF","designation":"RFC 1279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1279.txt","https://www.rfc-editor.org/rfc/rfc1279.pdf"],"folder":"IETF/RFC-1279","files":{"pdf":{"path":"standards/IETF/RFC-1279/RFC-1279.pdf","sha256":"c29634fa46caa6a5de340c365ee67ce4cd213a1986de28cc1146c412c1be69b7"},"txt":{"path":"standards/IETF/RFC-1279/RFC-1279.txt","sha256":"6473f47c77ce279f89e3e5ff644679d0d7ba29e0b79707cdaf5b927f633d566a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1279 University College London\n November 1991\n\n X.500 and Domains\n\nStatus of this Memo\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are\n requested. Please refer to the current edition of the `IAB\n Official Protocol Standards'' for the standardization state and\n status of this protocol. Distribution of this memo is unlimited.\nAbstract\n\n This RFCconsiders X.500 in relation to Internet and UK Domains.\n A basic model of X.500 providing a higher level and more\n descriptive naming structure is emphasised. In addition, a\n mapping of domains onto X.500 is proposed, which gives a range of\n new management and user facilities over and above those currently\n available. This specification proposes an experimental new\n mechanism to access and manage domain informatio","scope_keywords":["1279","algorithm","attribute","attributes","certificate","certificates","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1274","folder":"IETF/RFC-1274","source":"IETF/RFC-1274/RFC-1274.txt","version":null},{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1384","folder":"IETF/RFC-1384","source":"IETF/RFC-1384/RFC-1384.txt","version":null},{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null}],"search_text":"IETF RFC 1279 Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1279 University College London\n November 1991\n\n X.500 and Domains\n\nStatus of this Memo\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are\n requested. Please refer to the current edition of the `IAB\n Official Protocol Standards'' for the standardization state and\n status of this protocol. Distribution of this memo is unlimited.\nAbstract\n\n This RFCconsiders X.500 in relation to Internet and UK Domains.\n A basic model of X.500 providing a higher level and more\n descriptive naming structure is emphasised. In addition, a\n mapping of domains onto X.500 is proposed, which gives a range of\n new management and user facilities over and above those currently\n available. This specification proposes an experimental new\n mechanism to access and manage domain informatio 1279 algorithm attribute attributes certificate certificates key management registered nested-reference unchanged"},{"id":"IETF RFC 1395","type":"specification","body":"IETF","designation":"RFC 1395","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1395.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1395.txt","https://www.rfc-editor.org/rfc/rfc1395.pdf"],"folder":"IETF/RFC-1395","files":{"txt":{"path":"standards/IETF/RFC-1395/RFC-1395.txt","sha256":"8a5727df1d2e2f68fd5dd483190f35551084e6fafa56c155c88b37ae69119459"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1395 ISI\nObsoletes: 1084, 1048 January 1993\nUpdates: 951\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo is a status report on the vendor information extensions\n used in the Bootstrap Protocol (BOOTP). Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain\n Name, Tag 16 for Swap Server and Tag 17 for Root Path.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represen","scope_keywords":["1395","management","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null}],"search_text":"IETF RFC 1395 Network Working Group J. Reynolds\nRequest for Comments: 1395 ISI\nObsoletes: 1084, 1048 January 1993\nUpdates: 951\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo is a status report on the vendor information extensions\n used in the Bootstrap Protocol (BOOTP). Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain\n Name, Tag 16 for Swap Server and Tag 17 for Root Path.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represen 1395 management path qualified nested-reference unchanged"},{"id":"IETF RFC 1436","type":"specification","body":"IETF","designation":"RFC 1436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1436.txt","https://www.rfc-editor.org/rfc/rfc1436.pdf"],"folder":"IETF/RFC-1436","files":{"txt":{"path":"standards/IETF/RFC-1436/RFC-1436.txt","sha256":"906717c4fc9df322b95be80093aa66b877961743a5ed857d45f63c6de0e39587"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Gopher protocol is designed for distributed document\n search and retrieval. This document describes the protocol, lists\n some of the implementations currently available, and has an overview\n of how to implement new client and server applications. This\n document is adapted from the basic Internet Gopher protocol document\n first issued by the Microcomputer Center at the University of\n Minnesota in 1991.","scope_keywords":["1436","attribute","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1579","folder":"IETF/RFC-1579","source":"IETF/RFC-1579/RFC-1579.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null}],"search_text":"IETF RFC 1436 The Internet Gopher protocol is designed for distributed document\n search and retrieval. This document describes the protocol, lists\n some of the implementations currently available, and has an overview\n of how to implement new client and server applications. This\n document is adapted from the basic Internet Gopher protocol document\n first issued by the Microcomputer Center at the University of\n Minnesota in 1991. 1436 attribute delivery path nested-reference unchanged"},{"id":"IETF RFC 1458","type":"specification","body":"IETF","designation":"RFC 1458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1458.txt","https://www.rfc-editor.org/rfc/rfc1458.pdf"],"folder":"IETF/RFC-1458","files":{"txt":{"path":"standards/IETF/RFC-1458/RFC-1458.txt","sha256":"9db4aff8316cae0d26b8e1782d0dabf7016203b3091078e11a0f9330633b8301"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braudes\nRequest for Comments: 1458 S. Zabele\n TASC\n May 1993\n\n Requirements for Multicast Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n Multicast protocols have been developed over the past several years\n to address issues of group communication. Experience has\n demonstrated that current protocols do not address all of the\n requirements of multicast applications. This memo discusses some of\n these unresolved issues, and provides a high-level design for a new\n multicast transport protocol, group address and membership authority,\n and modifications to existing routing protocols.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. The Image Communication Problem . . . . . . . . . . . . . 2\n ","scope_keywords":["1458","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2357","folder":"IETF/RFC-2357","source":"IETF/RFC-2357/RFC-2357.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null}],"search_text":"IETF RFC 1458 Network Working Group R. Braudes\nRequest for Comments: 1458 S. Zabele\n TASC\n May 1993\n\n Requirements for Multicast Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n Multicast protocols have been developed over the past several years\n to address issues of group communication. Experience has\n demonstrated that current protocols do not address all of the\n requirements of multicast applications. This memo discusses some of\n these unresolved issues, and provides a high-level design for a new\n multicast transport protocol, group address and membership authority,\n and modifications to existing routing protocols.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. The Image Communication Problem . . . . . . . . . . . . . 2\n  1458 management path pid nested-reference unchanged"},{"id":"IETF RFC 1486","type":"specification","body":"IETF","designation":"RFC 1486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1486.txt","https://www.rfc-editor.org/rfc/rfc1486.pdf"],"folder":"IETF/RFC-1486","files":{"txt":{"path":"standards/IETF/RFC-1486/RFC-1486.txt","sha256":"fd5302c723cc66abe3097726bcc70ff5383d5dfc3d59fc2030b6664667469e4d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1486 Dover Beach Consulting, Inc.\n C. Malamud\n Internet Multicasting Service\n July 1993\n\n An Experiment in Remote Printing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 1.1 The Advantage of a General-Purpose Infrastructure..... 2\n 2. Procedure ............................................. 2\n 2.1 Naming, Addressing, and Routing ...................... 3\n 2.2 The application/remote-printing Content-Type ......... 4\n 2.3 Usage Example .","scope_keywords":["1486","algorithm","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1568","folder":"IETF/RFC-1568","source":"IETF/RFC-1568/RFC-1568.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1486 Network Working Group M. Rose\nRequest for Comments: 1486 Dover Beach Consulting, Inc.\n C. Malamud\n Internet Multicasting Service\n July 1993\n\n An Experiment in Remote Printing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 1.1 The Advantage of a General-Purpose Infrastructure..... 2\n 2. Procedure ............................................. 2\n 2.1 Naming, Addressing, and Routing ...................... 3\n 2.2 The application/remote-printing Content-Type ......... 4\n 2.3 Usage Example . 1486 algorithm presentation nested-reference unchanged"},{"id":"IETF RFC 1497","type":"specification","body":"IETF","designation":"RFC 1497","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1497.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1497.txt","https://www.rfc-editor.org/rfc/rfc1497.pdf"],"folder":"IETF/RFC-1497","files":{"txt":{"path":"standards/IETF/RFC-1497/RFC-1497.txt","sha256":"538dff60581b5a899743d595ed2b2577ac0f14bec26f43d4cfd6af7590540c66"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1497 ISI\nObsoletes: 1395, 1084, 1048 August 1993\nUpdates: 951\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo is a status report on the vendor information extensions\n used in the Bootstrap Protocol (BOOTP). Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 18 for Extension Path.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such respons","scope_keywords":["1497","management","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null}],"search_text":"IETF RFC 1497 Network Working Group J. Reynolds\nRequest for Comments: 1497 ISI\nObsoletes: 1395, 1084, 1048 August 1993\nUpdates: 951\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo is a status report on the vendor information extensions\n used in the Bootstrap Protocol (BOOTP). Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 18 for Extension Path.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such respons 1497 management path qualified nested-reference unchanged"},{"id":"IETF RFC 1528","type":"specification","body":"IETF","designation":"RFC 1528","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1528.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1528.txt","https://www.rfc-editor.org/rfc/rfc1528.pdf"],"folder":"IETF/RFC-1528","files":{"txt":{"path":"standards/IETF/RFC-1528/RFC-1528.txt","sha256":"0c73f80112418ce52f6bc384be80adf83bcf81d874587a6c80aef6f9d06c7aa1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Malamud\nRequest for Comments: 1528 Internet Multicasting Service\nObsoletes: 1486 M. Rose\nCategory: Experimental Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n Remote Printing -- Technical Procedures\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"Internet Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 2\n 2. Naming, Addressing, and Routing ....................... 2\n 2.1 Addressing ........................................... 2\n 2.2 Routing ...........................","scope_keywords":["1528","algorithm","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1529","folder":"IETF/RFC-1529","source":"IETF/RFC-1529/RFC-1529.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 2302","folder":"IETF/RFC-2302","source":"IETF/RFC-2302/RFC-2302.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3250","folder":"IETF/RFC-3250","source":"IETF/RFC-3250/RFC-3250.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1528 Network Working Group C. Malamud\nRequest for Comments: 1528 Internet Multicasting Service\nObsoletes: 1486 M. Rose\nCategory: Experimental Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n Remote Printing -- Technical Procedures\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"Internet Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 2\n 2. Naming, Addressing, and Routing ....................... 2\n 2.1 Addressing ........................................... 2\n 2.2 Routing ........................... 1528 algorithm identification presentation nested-reference unchanged"},{"id":"IETF RFC 1530","type":"specification","body":"IETF","designation":"RFC 1530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1530.txt","https://www.rfc-editor.org/rfc/rfc1530.pdf"],"folder":"IETF/RFC-1530","files":{"txt":{"path":"standards/IETF/RFC-1530/RFC-1530.txt","sha256":"d24b134cd7b8470d8a15a28ae0b88fc933224a98586027b87b02dea7504bf232"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Malamud\nRequest for Comments: 1530 Internet Multicasting Service\nCategory: Informational M. Rose\n Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n General Principles and Policy\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document defines the initial principles of operation for the\n tpc.int subdomain, a collection of service listings accessible over\n the Internet infrastructure through an administered namespace\n contained within the Domain Name System [1,2].\n\n This document is informational and applies only to those Internet\n sites that choose to register themselves within the tpc.int\n subdomain. The tpc.int subdomain is organized as a cooperative of\n the sites that provide access","scope_keywords":["1530","key","path","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1529","folder":"IETF/RFC-1529","source":"IETF/RFC-1529/RFC-1529.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 1530 Network Working Group C. Malamud\nRequest for Comments: 1530 Internet Multicasting Service\nCategory: Informational M. Rose\n Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n General Principles and Policy\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document defines the initial principles of operation for the\n tpc.int subdomain, a collection of service listings accessible over\n the Internet infrastructure through an administered namespace\n contained within the Domain Name System [1,2].\n\n This document is informational and applies only to those Internet\n sites that choose to register themselves within the tpc.int\n subdomain. The tpc.int subdomain is organized as a cooperative of\n the sites that provide access 1530 key path policy registered nested-reference unchanged"},{"id":"IETF RFC 1531","type":"specification","body":"IETF","designation":"RFC 1531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1531.txt","https://www.rfc-editor.org/rfc/rfc1531.pdf"],"folder":"IETF/RFC-1531","files":{"txt":{"path":"standards/IETF/RFC-1531/RFC-1531.txt","sha256":"1e560e72171d3badc791bbef012196ee27486cf260313970eab42a4e5b9909bf"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 23], and DHCP participants can interoperate\n with BOOTP participants [9].","scope_keywords":["1531","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1534","folder":"IETF/RFC-1534","source":"IETF/RFC-1534/RFC-1534.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1531 The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 23], and DHCP participants can interoperate\n with BOOTP participants [9]. 1531 policies presentation nested-reference unchanged"},{"id":"IETF RFC 1535","type":"specification","body":"IETF","designation":"RFC 1535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1535.txt","https://www.rfc-editor.org/rfc/rfc1535.pdf"],"folder":"IETF/RFC-1535","files":{"txt":{"path":"standards/IETF/RFC-1535/RFC-1535.txt","sha256":"42a96efbbc108371e51b1c4c37b6670ac3d4d97326b27817fa4e8399bba5c6f6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Gavron\nRequest for Comments: 1535 ACES Research Inc.\nCategory: Informational October 1993\n\n A Security Problem and Proposed Correction\n With Widely Deployed DNS Software\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document discusses a flaw in some of the currently distributed\n name resolver clients. The flaw exposes a security weakness related\n to the search heuristic invoked by these same resolvers when users\n provide a partial domain name, and which is easy to exploit (although\n not by the masses). This document points out the flaw, a case in\n point, and a solution.\n\nBackground\n\n Current Domain Name Server clients are designed to ease the burden of\n remembering IP dotted quad addresses. As such they translate human-\n readabl","scope_keywords":["1535","qualified","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1536","folder":"IETF/RFC-1536","source":"IETF/RFC-1536/RFC-1536.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null}],"search_text":"IETF RFC 1535 Network Working Group E. Gavron\nRequest for Comments: 1535 ACES Research Inc.\nCategory: Informational October 1993\n\n A Security Problem and Proposed Correction\n With Widely Deployed DNS Software\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document discusses a flaw in some of the currently distributed\n name resolver clients. The flaw exposes a security weakness related\n to the search heuristic invoked by these same resolvers when users\n provide a partial domain name, and which is easy to exploit (although\n not by the masses). This document points out the flaw, a case in\n point, and a solution.\n\nBackground\n\n Current Domain Name Server clients are designed to ease the burden of\n remembering IP dotted quad addresses. As such they translate human-\n readabl 1535 qualified registered risk subject nested-reference unchanged"},{"id":"IETF RFC 1536","type":"specification","body":"IETF","designation":"RFC 1536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1536.txt","https://www.rfc-editor.org/rfc/rfc1536.pdf"],"folder":"IETF/RFC-1536","files":{"txt":{"path":"standards/IETF/RFC-1536/RFC-1536.txt","sha256":"5195ddab55052a172153f456778af5655879e75d829ef9ad8bc8e673e7cba5f2"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes common errors seen in DNS implementations and\n suggests some fixes. Where applicable, violations of recommendations\n from STD 13, RFC 1034 and STD 13, RFC 1035 are mentioned. The memo\n also describes, where relevant, the algorithms followed in BIND\n (versions 4.8.3 and 4.9 which the authors referred to) to serve as an\n example.","scope_keywords":["1536","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1535","folder":"IETF/RFC-1535","source":"IETF/RFC-1535/RFC-1535.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 1536 This memo describes common errors seen in DNS implementations and\n suggests some fixes. Where applicable, violations of recommendations\n from STD 13, RFC 1034 and STD 13, RFC 1035 are mentioned. The memo\n also describes, where relevant, the algorithms followed in BIND\n (versions 4.8.3 and 4.9 which the authors referred to) to serve as an\n example. 1536 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 1541","type":"specification","body":"IETF","designation":"RFC 1541","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1541.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1541.txt","https://www.rfc-editor.org/rfc/rfc1541.pdf"],"folder":"IETF/RFC-1541","files":{"txt":{"path":"standards/IETF/RFC-1541/RFC-1541.txt","sha256":"d9a10d6dc7969f2e46df1000c0cf2b8506e31d5bdd3f4f89a4dd222a3603dc0f"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 23], and DHCP participants can interoperate\n with BOOTP participants [9]. Due to some errors introduced into RFC\n 1531 in the editorial process, this memo is reissued as RFC 1541.","scope_keywords":["1541","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1627","folder":"IETF/RFC-1627","source":"IETF/RFC-1627/RFC-1627.txt","version":null},{"body":"IETF","designation":"RFC 1678","folder":"IETF/RFC-1678","source":"IETF/RFC-1678/RFC-1678.txt","version":null},{"body":"IETF","designation":"RFC 1766","folder":"IETF/RFC-1766","source":"IETF/RFC-1766/RFC-1766.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null}],"search_text":"IETF RFC 1541 The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 23], and DHCP participants can interoperate\n with BOOTP participants [9]. Due to some errors introduced into RFC\n 1531 in the editorial process, this memo is reissued as RFC 1541. 1541 policies presentation nested-reference unchanged"},{"id":"IETF RFC 1591","type":"specification","body":"IETF","designation":"RFC 1591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1591.txt","https://www.rfc-editor.org/rfc/rfc1591.pdf"],"folder":"IETF/RFC-1591","files":{"txt":{"path":"standards/IETF/RFC-1591/RFC-1591.txt","sha256":"661c94d7d25a2a6ac7c1231f29f7ad072a6d4b47c79b9444eb22a1a40dbffc88"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1591 ISI\nCategory: Informational March 1994\n\n Domain Name System Structure and Delegation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo provides some information on the structure of the names in\n the Domain Name System (DNS), specifically the top-level domain\n names; and on the administration of domains. The Internet Assigned\n Numbers Authority (IANA) is the overall authority for the IP\n Addresses, the Domain Names, and many other parameters, used in the\n Internet. The day-to-day responsibility for the assignment of IP\n Addresses, Autonomous System Numbers, and most top and second level\n Domain Names are handled by the Internet Registry (IR) and regional\n registries.\n\n2","scope_keywords":["1591","management","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2606","folder":"IETF/RFC-2606","source":"IETF/RFC-2606/RFC-2606.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 1591 Network Working Group J. Postel\nRequest for Comments: 1591 ISI\nCategory: Informational March 1994\n\n Domain Name System Structure and Delegation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo provides some information on the structure of the names in\n the Domain Name System (DNS), specifically the top-level domain\n names; and on the administration of domains. The Internet Assigned\n Numbers Authority (IANA) is the overall authority for the IP\n Addresses, the Domain Names, and many other parameters, used in the\n Internet. The day-to-day responsibility for the assignment of IP\n Addresses, Autonomous System Numbers, and most top and second level\n Domain Names are handled by the Internet Registry (IR) and regional\n registries.\n\n2 1591 management policy registered nested-reference unchanged"},{"id":"IETF RFC 1611","type":"specification","body":"IETF","designation":"RFC 1611","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1611.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1611.txt","https://www.rfc-editor.org/rfc/rfc1611.pdf"],"folder":"IETF/RFC-1611","files":{"txt":{"path":"standards/IETF/RFC-1611/RFC-1611.txt","sha256":"23e4416a90ccc13c4dd4b6d3e6be22d1bcff73bf3f8daf12a16b33528efc0d9e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Austein\nRequest for Comments: 1611 Epilogue Technology Corporation\nCategory: Standards Track J. Saperia\n Digital Equipment Corporation\n May 1994\n\n DNS Server MIB Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 2\n 3.1 Resolvers ........................................","scope_keywords":["1611","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1611 Network Working Group R. Austein\nRequest for Comments: 1611 Epilogue Technology Corporation\nCategory: Standards Track J. Saperia\n Digital Equipment Corporation\n May 1994\n\n DNS Server MIB Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 2\n 3.1 Resolvers ........................................ 1611 key management nested-reference unchanged"},{"id":"IETF RFC 1630","type":"specification","body":"IETF","designation":"RFC 1630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1630.txt","https://www.rfc-editor.org/rfc/rfc1630.pdf"],"folder":"IETF/RFC-1630","files":{"txt":{"path":"standards/IETF/RFC-1630/RFC-1630.txt","sha256":"75886315396874afde4cf0b603972182391075bd68f74cf429648705062efdbd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Berners-Lee\nRequest for Comments: 1630 CERN\nCategory: Informational June 1994\n\n Universal Resource Identifiers in WWW\n\n A Unifying Syntax for the Expression of\n Names and Addresses of Objects on the Network\n as used in the World-Wide Web\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIESG Note:\n\n Note that the work contained in this memo does not describe an\n Internet standard. An Internet standard for general Resource\n Identifiers is under development within the IETF.\n\nIntroduction\n\n This document defines the syntax used by the World-Wide Web\n initiative to encode the names and addresses of objects on the\n Internet. The web is considered to include objects accessed using an\n extendable number of protocols, existing, invented ","scope_keywords":["1630","algorithm","http","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1808","folder":"IETF/RFC-1808","source":"IETF/RFC-1808/RFC-1808.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2141","folder":"IETF/RFC-2141","source":"IETF/RFC-2141/RFC-2141.txt","version":null},{"body":"IETF","designation":"RFC 2169","folder":"IETF/RFC-2169","source":"IETF/RFC-2169/RFC-2169.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null}],"search_text":"IETF RFC 1630 Network Working Group T. Berners-Lee\nRequest for Comments: 1630 CERN\nCategory: Informational June 1994\n\n Universal Resource Identifiers in WWW\n\n A Unifying Syntax for the Expression of\n Names and Addresses of Objects on the Network\n as used in the World-Wide Web\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIESG Note:\n\n Note that the work contained in this memo does not describe an\n Internet standard. An Internet standard for general Resource\n Identifiers is under development within the IETF.\n\nIntroduction\n\n This document defines the syntax used by the World-Wide Web\n initiative to encode the names and addresses of objects on the\n Internet. The web is considered to include objects accessed using an\n extendable number of protocols, existing, invented  1630 algorithm http registered subject nested-reference unchanged"},{"id":"IETF RFC 1637","type":"specification","body":"IETF","designation":"RFC 1637","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1637.txt","https://www.rfc-editor.org/rfc/rfc1637.pdf"],"folder":"IETF/RFC-1637","files":{"txt":{"path":"standards/IETF/RFC-1637/RFC-1637.txt","sha256":"bf2bccef5d10400363b0f0c129a8ce14b692468fb8417a68a7ae21f9be97c9e2"}},"tags":["nested-reference","unchanged"],"summary":"The Internet is moving towards the deployment of an OSI lower layers\n infrastructure. This infrastructure comprises the connectionless\n network protocol (CLNP) and supporting routing protocols. Also\n required as part of this infrastructure is support in the Domain Name\n System (DNS) for mapping between names and NSAP addresses.\n\n This document defines the format of one new Resource Record (RR) for\n the DNS for domain name-to-NSAP mapping. The RR may be used with any\n NSAP address format. This document supercedes RFC 1348.\n\n NSAP-to-name translation is accomplished through use of the PTR RR\n (see STD 13, RFC 1035 for a description of the PTR RR). This paper\n describes how PTR RRs are used to support this translation.\n\nManning & Colella [Page 1]\n\f\nRFC 1637 DNS NSAP RRs June 1994\n\n1. Introduction\n\n The Internet is moving towards the deployment of an OSI lower layers\n infrastructure. This in","scope_keywords":["1637","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null}],"search_text":"IETF RFC 1637 The Internet is moving towards the deployment of an OSI lower layers\n infrastructure. This infrastructure comprises the connectionless\n network protocol (CLNP) and supporting routing protocols. Also\n required as part of this infrastructure is support in the Domain Name\n System (DNS) for mapping between names and NSAP addresses.\n\n This document defines the format of one new Resource Record (RR) for\n the DNS for domain name-to-NSAP mapping. The RR may be used with any\n NSAP address format. This document supercedes RFC 1348.\n\n NSAP-to-name translation is accomplished through use of the PTR RR\n (see STD 13, RFC 1035 for a description of the PTR RR). This paper\n describes how PTR RRs are used to support this translation.\n\nManning & Colella [Page 1]\n\f\nRFC 1637 DNS NSAP RRs June 1994\n\n1. Introduction\n\n The Internet is moving towards the deployment of an OSI lower layers\n infrastructure. This in 1637 presentation registered nested-reference unchanged"},{"id":"IETF RFC 1706","type":"specification","body":"IETF","designation":"RFC 1706","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1706.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1706.txt","https://www.rfc-editor.org/rfc/rfc1706.pdf"],"folder":"IETF/RFC-1706","files":{"txt":{"path":"standards/IETF/RFC-1706/RFC-1706.txt","sha256":"c1e2d82bbeaf2d8745354fc1f50e3a8c699c93f87a25b9fcfcc8bb3129d53024"}},"tags":["nested-reference","unchanged"],"summary":"OSI lower layer protocols, comprising the connectionless network\n protocol (CLNP) and supporting routing protocols, are deployed in\n some parts of the global Internet. Maintenance and debugging of CLNP\n connectivity is greatly aided by support in the Domain Name System\n (DNS) for mapping between names and NSAP addresses.\n\n This document defines the format of one new Resource Record (RR) for\n the DNS for domain name-to-NSAP mapping. The RR may be used with any\n NSAP address format.\n\n NSAP-to-name translation is accomplished through use of the PTR RR\n (see STD 13, RFC 1035 for a description of the PTR RR). This paper\n describes how PTR RRs are used to support this translation.\n\n This document obsoletes RFC 1348 and RFC 1637.\n\nManning & Colella [Page 1]\n\f\nRFC 1706 DNS NSAP RRs October 1994\n\n1. Introduction\n\n OSI lower layer protocols, comprising the connectionless network\n protocol (CLNP) [","scope_keywords":["1706","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null}],"search_text":"IETF RFC 1706 OSI lower layer protocols, comprising the connectionless network\n protocol (CLNP) and supporting routing protocols, are deployed in\n some parts of the global Internet. Maintenance and debugging of CLNP\n connectivity is greatly aided by support in the Domain Name System\n (DNS) for mapping between names and NSAP addresses.\n\n This document defines the format of one new Resource Record (RR) for\n the DNS for domain name-to-NSAP mapping. The RR may be used with any\n NSAP address format.\n\n NSAP-to-name translation is accomplished through use of the PTR RR\n (see STD 13, RFC 1035 for a description of the PTR RR). This paper\n describes how PTR RRs are used to support this translation.\n\n This document obsoletes RFC 1348 and RFC 1637.\n\nManning & Colella [Page 1]\n\f\nRFC 1706 DNS NSAP RRs October 1994\n\n1. Introduction\n\n OSI lower layer protocols, comprising the connectionless network\n protocol (CLNP) [ 1706 presentation registered nested-reference unchanged"},{"id":"IETF RFC 1712","type":"specification","body":"IETF","designation":"RFC 1712","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1712.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1712.txt","https://www.rfc-editor.org/rfc/rfc1712.pdf"],"folder":"IETF/RFC-1712","files":{"txt":{"path":"standards/IETF/RFC-1712/RFC-1712.txt","sha256":"a03d6173fb8cda3bbd567883b03e59db5c105a2a7957d8ab4fe311bbec443889"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format of a new Resource Record (RR) for\n the Domain Naming System (DNS), and reserves a corresponding DNS type\n mnemonic and numerical code. This definition deals with associating\n geographical host location mappings to host names within a domain.\n The data shown in this document is fictitious and does not\n necessarily reflect the real Internet.\n\n1. Introduction\n\n It has been a long standing problem to relate IP numbers to\n geographical locations. The availability of Geographical location\n information has immediate applications in network management. Such\n information can be used to supplement the data already provided by\n utilities such as whois [Har85], traceroute [VJ89], and nslookup\n [UCB89]. The usefulness and functionality of these already widely\n used tools would be greatly enhanced by the provision of reliable\n geographical location information.\n\n The i","scope_keywords":["1712","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null}],"search_text":"IETF RFC 1712 This document defines the format of a new Resource Record (RR) for\n the Domain Naming System (DNS), and reserves a corresponding DNS type\n mnemonic and numerical code. This definition deals with associating\n geographical host location mappings to host names within a domain.\n The data shown in this document is fictitious and does not\n necessarily reflect the real Internet.\n\n1. Introduction\n\n It has been a long standing problem to relate IP numbers to\n geographical locations. The availability of Geographical location\n information has immediate applications in network management. Such\n information can be used to supplement the data already provided by\n utilities such as whois [Har85], traceroute [VJ89], and nslookup\n [UCB89]. The usefulness and functionality of these already widely\n used tools would be greatly enhanced by the provision of reliable\n geographical location information.\n\n The i 1712 management nested-reference unchanged"},{"id":"IETF RFC 1738","type":"specification","body":"IETF","designation":"RFC 1738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1738.txt","https://www.rfc-editor.org/rfc/rfc1738.pdf"],"folder":"IETF/RFC-1738","files":{"txt":{"path":"standards/IETF/RFC-1738/RFC-1738.txt","sha256":"2622f97a21c8b28558e860c2ad53a6f3114ac0cf905eb51aefa38e0629d76b2d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Uniform Resource Locator (URL), the syntax\n and semantics of formalized information for location and access of\n resources via the Internet.\n\n1. Introduction\n\n This document describes the syntax and semantics for a compact string\n representation for a resource available via the Internet. These\n strings are called \"Uniform Resource Locators\" (URLs).\n\n The specification is derived from concepts introduced by the World-\n Wide Web global information initiative, whose use of such objects\n dates from 1990 and is described in \"Universal Resource Identifiers\n in WWW\", RFC 1630. The specification of URLs is designed to meet the\n requirements laid out in \"Functional Requirements for Internet\n Resource Locators\" [12].\n\n This document was written by the URI working group of the Internet\n Engineering Task Force. Comments may be addressed to the editors, or\n to the URI-WG <uri","scope_keywords":["1738","attribute","attributes","http","identification","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 1727","folder":"IETF/RFC-1727","source":"IETF/RFC-1727/RFC-1727.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1808","folder":"IETF/RFC-1808","source":"IETF/RFC-1808/RFC-1808.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null},{"body":"IETF","designation":"RFC 1980","folder":"IETF/RFC-1980","source":"IETF/RFC-1980/RFC-1980.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2016","folder":"IETF/RFC-2016","source":"IETF/RFC-2016/RFC-2016.txt","version":null},{"body":"IETF","designation":"RFC 2017","folder":"IETF/RFC-2017","source":"IETF/RFC-2017/RFC-2017.txt","version":null},{"body":"IETF","designation":"RFC 2056","folder":"IETF/RFC-2056","source":"IETF/RFC-2056/RFC-2056.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2079","folder":"IETF/RFC-2079","source":"IETF/RFC-2079/RFC-2079.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2111","folder":"IETF/RFC-2111","source":"IETF/RFC-2111/RFC-2111.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2186","folder":"IETF/RFC-2186","source":"IETF/RFC-2186/RFC-2186.txt","version":null},{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2193","folder":"IETF/RFC-2193","source":"IETF/RFC-2193/RFC-2193.txt","version":null},{"body":"IETF","designation":"RFC 2221","folder":"IETF/RFC-2221","source":"IETF/RFC-2221/RFC-2221.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2276","folder":"IETF/RFC-2276","source":"IETF/RFC-2276/RFC-2276.txt","version":null},{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2368","folder":"IETF/RFC-2368","source":"IETF/RFC-2368/RFC-2368.txt","version":null},{"body":"IETF","designation":"RFC 2369","folder":"IETF/RFC-2369","source":"IETF/RFC-2369/RFC-2369.txt","version":null},{"body":"IETF","designation":"RFC 2371","folder":"IETF/RFC-2371","source":"IETF/RFC-2371/RFC-2371.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2392","folder":"IETF/RFC-2392","source":"IETF/RFC-2392/RFC-2392.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2511","folder":"IETF/RFC-2511","source":"IETF/RFC-2511/RFC-2511.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2585","folder":"IETF/RFC-2585","source":"IETF/RFC-2585/RFC-2585.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2655","folder":"IETF/RFC-2655","source":"IETF/RFC-2655/RFC-2655.txt","version":null},{"body":"IETF","designation":"RFC 2656","folder":"IETF/RFC-2656","source":"IETF/RFC-2656/RFC-2656.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 1738 This document specifies a Uniform Resource Locator (URL), the syntax\n and semantics of formalized information for location and access of\n resources via the Internet.\n\n1. Introduction\n\n This document describes the syntax and semantics for a compact string\n representation for a resource available via the Internet. These\n strings are called \"Uniform Resource Locators\" (URLs).\n\n The specification is derived from concepts introduced by the World-\n Wide Web global information initiative, whose use of such objects\n dates from 1990 and is described in \"Universal Resource Identifiers\n in WWW\", RFC 1630. The specification of URLs is designed to meet the\n requirements laid out in \"Functional Requirements for Internet\n Resource Locators\" [12].\n\n This document was written by the URI working group of the Internet\n Engineering Task Force. Comments may be addressed to the editors, or\n to the URI-WG <uri 1738 attribute attributes http identification presentation subject nested-reference unchanged"},{"id":"IETF RFC 1739","type":"specification","body":"IETF","designation":"RFC 1739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1739.txt","https://www.rfc-editor.org/rfc/rfc1739.pdf"],"folder":"IETF/RFC-1739","files":{"txt":{"path":"standards/IETF/RFC-1739/RFC-1739.txt","sha256":"01789bbae360c469a9ab75949369816c29c768578c1c394fde0076ffc4f8de51"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Kessler\nRequest for Comments: 1739 S. Shepard\nCategory: Informational Hill Associates, Inc.\n December 1994\n\n A Primer On Internet and TCP/IP Tools\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .................................................. 2\n 2. A Beginner's Guide to TCP/IP-based Utilities and Applications . 2\n 2.1. NSLOOKUP .................................................... 3\n 2.2. PING ........................................................ 5\n 2.3. FINGER ...................................................... 6\n 2.4. TRACEROUTE .................................................. 7\n 2.5. FTP ......................................................... 10\n 2.6. TELNET ...................","scope_keywords":["1739","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1739 Network Working Group G. Kessler\nRequest for Comments: 1739 S. Shepard\nCategory: Informational Hill Associates, Inc.\n December 1994\n\n A Primer On Internet and TCP/IP Tools\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .................................................. 2\n 2. A Beginner's Guide to TCP/IP-based Utilities and Applications . 2\n 2.1. NSLOOKUP .................................................... 3\n 2.2. PING ........................................................ 5\n 2.3. FINGER ...................................................... 6\n 2.4. TRACEROUTE .................................................. 7\n 2.5. FTP ......................................................... 10\n 2.6. TELNET ................... 1739 policy nested-reference unchanged"},{"id":"IETF RFC 1788","type":"specification","body":"IETF","designation":"RFC 1788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1788.txt","https://www.rfc-editor.org/rfc/rfc1788.pdf"],"folder":"IETF/RFC-1788","files":{"txt":{"path":"standards/IETF/RFC-1788/RFC-1788.txt","sha256":"919184e29cd35fc92ad2bd0bf1211ee1584566d2555f073abc5df6b64a2b95ea"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies ICMP messages for learning the Fully\n Qualified Domain Name associated with an IP address.\n\nSimpson [Page 1]\n\f\nRFC 1788 ICMP Domain Name April 1995","scope_keywords":["1788","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null}],"search_text":"IETF RFC 1788 This document specifies ICMP messages for learning the Fully\n Qualified Domain Name associated with an IP address.\n\nSimpson [Page 1]\n\f\nRFC 1788 ICMP Domain Name April 1995 1788 qualified nested-reference unchanged"},{"id":"IETF RFC 1798","type":"specification","body":"IETF","designation":"RFC 1798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1798.txt","https://www.rfc-editor.org/rfc/rfc1798.pdf"],"folder":"IETF/RFC-1798","files":{"txt":{"path":"standards/IETF/RFC-1798/RFC-1798.txt","sha256":"9e9914621e045160b2cddbbc4476754c04ea70853110419f16ce45a7bc375bd9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Young\nRequest for Comments: 1798 ISODE Consortium\nCategory: Standards Track June 1995\n\n Connection-less Lightweight X.500 Directory Access Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nX.500\n\n The protocol described in this document is designed to provide access\n to the Directory while not incurring the resource requirements of the\n Directory Access Protocol (DAP) [3]. In particular, it is aimed at\n avoiding the elapsed time that is associated with connection-oriented\n communication and it facilitates use of the Directory in a manner\n analago","scope_keywords":["1798","attribute","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null}],"search_text":"IETF RFC 1798 Network Working Group A. Young\nRequest for Comments: 1798 ISODE Consortium\nCategory: Standards Track June 1995\n\n Connection-less Lightweight X.500 Directory Access Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nX.500\n\n The protocol described in this document is designed to provide access\n to the Directory while not incurring the resource requirements of the\n Directory Access Protocol (DAP) [3]. In particular, it is aimed at\n avoiding the elapsed time that is associated with connection-oriented\n communication and it facilitates use of the Directory in a manner\n analago 1798 attribute key presentation nested-reference unchanged"},{"id":"IETF RFC 1876","type":"specification","body":"IETF","designation":"RFC 1876","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1876.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1876.txt","https://www.rfc-editor.org/rfc/rfc1876.pdf"],"folder":"IETF/RFC-1876","files":{"txt":{"path":"standards/IETF/RFC-1876/RFC-1876.txt","sha256":"d84c37ecb25b0b380f1c5cc8529b0ead60b0e0b447dfb08a45af4d66da452a91"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new DNS RR type for experimental purposes. This\n RFC describes a mechanism to allow the DNS to carry location\n information about hosts, networks, and subnets. Such information for\n a small subset of hosts is currently contained in the flat-file UUCP\n maps. However, just as the DNS replaced the use of HOSTS.TXT to\n carry host and network address information, it is possible to replace\n the UUCP maps as carriers of location information.\n\n This RFC defines the format of a new Resource Record (RR) for the\n Domain Name System (DNS), and reserves a corresponding DNS type\n mnemonic (LOC) and numerical code (29).\n\n This RFC assumes that the reader is familiar with the DNS [RFC 1034,\n RFC 1035]. The data shown in our examples is for pedagogical use and\n does not necessarily reflect the real Internet.\n\nDavis, et al Experimental [Page 1]\n\f\nRFC 1876 Location Information in the DNS","scope_keywords":["1876","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null}],"search_text":"IETF RFC 1876 This memo defines a new DNS RR type for experimental purposes. This\n RFC describes a mechanism to allow the DNS to carry location\n information about hosts, networks, and subnets. Such information for\n a small subset of hosts is currently contained in the flat-file UUCP\n maps. However, just as the DNS replaced the use of HOSTS.TXT to\n carry host and network address information, it is possible to replace\n the UUCP maps as carriers of location information.\n\n This RFC defines the format of a new Resource Record (RR) for the\n Domain Name System (DNS), and reserves a corresponding DNS type\n mnemonic (LOC) and numerical code (29).\n\n This RFC assumes that the reader is familiar with the DNS [RFC 1034,\n RFC 1035]. The data shown in our examples is for pedagogical use and\n does not necessarily reflect the real Internet.\n\nDavis, et al Experimental [Page 1]\n\f\nRFC 1876 Location Information in the DNS 1876 presentation nested-reference unchanged"},{"id":"IETF RFC 1877","type":"specification","body":"IETF","designation":"RFC 1877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1877.txt","https://www.rfc-editor.org/rfc/rfc1877.pdf"],"folder":"IETF/RFC-1877","files":{"txt":{"path":"standards/IETF/RFC-1877/RFC-1877.txt","sha256":"147d8e1957f0142b3b9d584e25f88206e1e8e675538bcdebf1c7f14672d1efc9"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n network-layer protocols.\n\n This document extends the NCP for establishing and configuring the\n Internet Protocol over PPP [2], defining the negotiation of primary\n and secondary Domain Name System (DNS) [3] and NetBIOS Name Server\n (NBNS) [4] addresses.","scope_keywords":["1877"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2194","folder":"IETF/RFC-2194","source":"IETF/RFC-2194/RFC-2194.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null}],"search_text":"IETF RFC 1877 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n network-layer protocols.\n\n This document extends the NCP for establishing and configuring the\n Internet Protocol over PPP [2], defining the negotiation of primary\n and secondary Domain Name System (DNS) [3] and NetBIOS Name Server\n (NBNS) [4] addresses. 1877 nested-reference unchanged"},{"id":"IETF RFC 1886","type":"specification","body":"IETF","designation":"RFC 1886","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1886.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1886.txt","https://www.rfc-editor.org/rfc/rfc1886.pdf"],"folder":"IETF/RFC-1886","files":{"txt":{"path":"standards/IETF/RFC-1886/RFC-1886.txt","sha256":"8172de1773505fa51f813964d4315466e5753d667de7d17540dfbb8681c328f4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the changes that need to be made to the Domain\n Name System to support hosts running IP version 6 (IPv6). The\n changes include a new resource record type to store an IPv6 address,\n a new domain to support lookups based on an IPv6 address, and updated\n definitions of existing query types that return Internet addresses as\n part of additional section processing. The extensions are designed\n to be compatible with existing applications and, in particular, DNS\n implementations themselves.\n\nThompson & Huitema Standards Track [Page 1]\n\f\nRFC 1886 IPv6 DNS Extensions December 1995\n\n1. INTRODUCTION\n\n Current support for the storage of Internet addresses in the Domain\n Name System (DNS)[1,2] cannot easily be extended to support IPv6\n addresses[3] since applications assume that address queries return\n 32-bit IPv4 addresses only.\n\n To support the storage of IPv6 addresses we defi","scope_keywords":["1886","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 3364","folder":"IETF/RFC-3364","source":"IETF/RFC-3364/RFC-3364.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null}],"search_text":"IETF RFC 1886 This document defines the changes that need to be made to the Domain\n Name System to support hosts running IP version 6 (IPv6). The\n changes include a new resource record type to store an IPv6 address,\n a new domain to support lookups based on an IPv6 address, and updated\n definitions of existing query types that return Internet addresses as\n part of additional section processing. The extensions are designed\n to be compatible with existing applications and, in particular, DNS\n implementations themselves.\n\nThompson & Huitema Standards Track [Page 1]\n\f\nRFC 1886 IPv6 DNS Extensions December 1995\n\n1. INTRODUCTION\n\n Current support for the storage of Internet addresses in the Domain\n Name System (DNS)[1,2] cannot easily be extended to support IPv6\n addresses[3] since applications assume that address queries return\n 32-bit IPv4 addresses only.\n\n To support the storage of IPv6 addresses we defi 1886 presentation nested-reference unchanged"},{"id":"IETF RFC 1889","type":"specification","body":"IETF","designation":"RFC 1889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1889.txt","https://www.rfc-editor.org/rfc/rfc1889.pdf"],"folder":"IETF/RFC-1889","files":{"txt":{"path":"standards/IETF/RFC-1889/RFC-1889.txt","sha256":"2a6fc2dd09ee4be7590e9ea11a211bf45481f1326d33dd60de4cc546ece0cbff"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum describes RTP, the real-time transport protocol. RTP\n provides end-to-end network transport functions suitable for\n applications transmitting real-time data, such as audio, video or\n simulation data, over multicast or unicast network services. RTP does\n not address resource reservation and does not guarantee quality-of-\n service for real-time services. The data transport is augmented by a\n control protocol (RTCP) to allow monitoring of the data delivery in a\n manner scalable to large multicast networks, and to provide minimal\n control and identification functionality. RTP and RTCP are designed\n to be independent of the underlying transport and network layers. The\n protocol supports the use of RTP-level translators and mixers.","scope_keywords":["1889","algorithm","algorithms","authentication","delivery","identification","profile","profiles","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 2029","folder":"IETF/RFC-2029","source":"IETF/RFC-2029/RFC-2029.txt","version":null},{"body":"IETF","designation":"RFC 2032","folder":"IETF/RFC-2032","source":"IETF/RFC-2032/RFC-2032.txt","version":null},{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 2198","folder":"IETF/RFC-2198","source":"IETF/RFC-2198/RFC-2198.txt","version":null},{"body":"IETF","designation":"RFC 2211","folder":"IETF/RFC-2211","source":"IETF/RFC-2211/RFC-2211.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2343","folder":"IETF/RFC-2343","source":"IETF/RFC-2343/RFC-2343.txt","version":null},{"body":"IETF","designation":"RFC 2354","folder":"IETF/RFC-2354","source":"IETF/RFC-2354/RFC-2354.txt","version":null},{"body":"IETF","designation":"RFC 2429","folder":"IETF/RFC-2429","source":"IETF/RFC-2429/RFC-2429.txt","version":null},{"body":"IETF","designation":"RFC 2431","folder":"IETF/RFC-2431","source":"IETF/RFC-2431/RFC-2431.txt","version":null},{"body":"IETF","designation":"RFC 2435","folder":"IETF/RFC-2435","source":"IETF/RFC-2435/RFC-2435.txt","version":null},{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2658","folder":"IETF/RFC-2658","source":"IETF/RFC-2658/RFC-2658.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 2736","folder":"IETF/RFC-2736","source":"IETF/RFC-2736/RFC-2736.txt","version":null},{"body":"IETF","designation":"RFC 2762","folder":"IETF/RFC-2762","source":"IETF/RFC-2762/RFC-2762.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2833","folder":"IETF/RFC-2833","source":"IETF/RFC-2833/RFC-2833.txt","version":null},{"body":"IETF","designation":"RFC 2862","folder":"IETF/RFC-2862","source":"IETF/RFC-2862/RFC-2862.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3009","folder":"IETF/RFC-3009","source":"IETF/RFC-3009/RFC-3009.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3304","folder":"IETF/RFC-3304","source":"IETF/RFC-3304/RFC-3304.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3448","folder":"IETF/RFC-3448","source":"IETF/RFC-3448/RFC-3448.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null}],"search_text":"IETF RFC 1889 This memorandum describes RTP, the real-time transport protocol. RTP\n provides end-to-end network transport functions suitable for\n applications transmitting real-time data, such as audio, video or\n simulation data, over multicast or unicast network services. RTP does\n not address resource reservation and does not guarantee quality-of-\n service for real-time services. The data transport is augmented by a\n control protocol (RTCP) to allow monitoring of the data delivery in a\n manner scalable to large multicast networks, and to provide minimal\n control and identification functionality. RTP and RTCP are designed\n to be independent of the underlying transport and network layers. The\n protocol supports the use of RTP-level translators and mixers. 1889 algorithm algorithms authentication delivery identification profile profiles timestamp nested-reference unchanged"},{"id":"IETF RFC 1911","type":"specification","body":"IETF","designation":"RFC 1911","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1911.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1911.txt","https://www.rfc-editor.org/rfc/rfc1911.pdf"],"folder":"IETF/RFC-1911","files":{"txt":{"path":"standards/IETF/RFC-1911/RFC-1911.txt","sha256":"f4cd0b2b1bf0673415ee013ad5a2e19bd5d45eba29e0b95f32d8cc06a506f01a"}},"tags":["nested-reference","unchanged"],"summary":"A class of special-purpose computers has evolved to provide voice\n messaging services. These machines generally interface to a\n telephone switch and provide call answering and voice messaging\n services. Traditionally, messages sent to a non-local machine are\n transported using analog networking protocols based on DTMF signaling\n and analog voice playback. As the demand for networking increases,\n there is a need for a standard high-quality digital protocol to\n connect these machines. The following document is a profile of the\n Internet standard MIME and ESMTP protocols for use as a digital voice\n networking protocol.\n\n This profile is based on an earlier effort in the Audio Message\n Interchange Specification (AMIS) group to define a voice messaging\n protocol based on X.400 technology. This protocol is intended to\n satisfy the user requirements statement from that earlier work with\n the in","scope_keywords":["1911","delivery","identification","management","pid","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null}],"search_text":"IETF RFC 1911 A class of special-purpose computers has evolved to provide voice\n messaging services. These machines generally interface to a\n telephone switch and provide call answering and voice messaging\n services. Traditionally, messages sent to a non-local machine are\n transported using analog networking protocols based on DTMF signaling\n and analog voice playback. As the demand for networking increases,\n there is a need for a standard high-quality digital protocol to\n connect these machines. The following document is a profile of the\n Internet standard MIME and ESMTP protocols for use as a digital voice\n networking protocol.\n\n This profile is based on an earlier effort in the Audio Message\n Interchange Specification (AMIS) group to define a voice messaging\n protocol based on X.400 technology. This protocol is intended to\n satisfy the user requirements statement from that earlier work with\n the in 1911 delivery identification management pid profile nested-reference unchanged"},{"id":"IETF RFC 1982","type":"specification","body":"IETF","designation":"RFC 1982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1982.txt","https://www.rfc-editor.org/rfc/rfc1982.pdf"],"folder":"IETF/RFC-1982","files":{"txt":{"path":"standards/IETF/RFC-1982/RFC-1982.txt","sha256":"b22fa98e10e66340804f50fe22c7c9299f66dea7ed90cac17800a4bccda7dc15"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines serial number arithmetic, as used in the Domain\n Name System. The DNS has long relied upon serial number arithmetic,\n a concept which has never really been defined, certainly not in an\n IETF document, though which has been widely understood. This memo\n supplies the missing definition. It is intended to update RFC1034\n and RFC1035.\n\n1. Introduction\n\n The serial number field of the SOA resource record is defined in\n RFC1035 as\n\n SERIAL The unsigned 32 bit version number of the original copy of\n the zone. Zone transfers preserve this value. This value\n wraps and should be compared using sequence space\n arithmetic.\n\n RFC1034 uses the same terminology when defining secondary server zone\n consistency procedures.\n\n Unfortunately the term \"sequence space arithmetic\" is not defined in\n either RFC1034 or RFC1035, nor do any of their references provide\n further information.\n\n This","scope_keywords":["1982"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2182","folder":"IETF/RFC-2182","source":"IETF/RFC-2182/RFC-2182.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3081","folder":"IETF/RFC-3081","source":"IETF/RFC-3081/RFC-3081.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null}],"search_text":"IETF RFC 1982 This memo defines serial number arithmetic, as used in the Domain\n Name System. The DNS has long relied upon serial number arithmetic,\n a concept which has never really been defined, certainly not in an\n IETF document, though which has been widely understood. This memo\n supplies the missing definition. It is intended to update RFC1034\n and RFC1035.\n\n1. Introduction\n\n The serial number field of the SOA resource record is defined in\n RFC1035 as\n\n SERIAL The unsigned 32 bit version number of the original copy of\n the zone. Zone transfers preserve this value. This value\n wraps and should be compared using sequence space\n arithmetic.\n\n RFC1034 uses the same terminology when defining secondary server zone\n consistency procedures.\n\n Unfortunately the term \"sequence space arithmetic\" is not defined in\n either RFC1034 or RFC1035, nor do any of their references provide\n further information.\n\n This 1982 nested-reference unchanged"},{"id":"IETF RFC 1995","type":"specification","body":"IETF","designation":"RFC 1995","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1995.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1995.txt","https://www.rfc-editor.org/rfc/rfc1995.pdf"],"folder":"IETF/RFC-1995","files":{"txt":{"path":"standards/IETF/RFC-1995/RFC-1995.txt","sha256":"29be6b1d66801178a702563bb1302751b7745d1fd8bba4d5cc29a05fa3719dd8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Ohta\nRequest for Comments: 1995 Tokyo Institute of Technology\nUpdates: 1035 August 1996\nCategory: Standards Track\n\n Incremental Zone Transfer in DNS\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document proposes extensions to the DNS protocols to provide an\n incremental zone transfer (IXFR) mechanism.\n\n1. Introduction\n\n For rapid propagation of changes to a DNS database [STD13], it is\n necessary to reduce latency by actively notifying servers of the\n change. This is accomplished by the NOTIFY extension of the DNS\n [NOTIFY].\n\n The curr","scope_keywords":["1995","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1996","folder":"IETF/RFC-1996","source":"IETF/RFC-1996/RFC-1996.txt","version":null},{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1995 Network Working Group M. Ohta\nRequest for Comments: 1995 Tokyo Institute of Technology\nUpdates: 1035 August 1996\nCategory: Standards Track\n\n Incremental Zone Transfer in DNS\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document proposes extensions to the DNS protocols to provide an\n incremental zone transfer (IXFR) mechanism.\n\n1. Introduction\n\n For rapid propagation of changes to a DNS database [STD13], it is\n necessary to reduce latency by actively notifying servers of the\n change. This is accomplished by the NOTIFY extension of the DNS\n [NOTIFY].\n\n The curr 1995 pid nested-reference unchanged"},{"id":"IETF RFC 2016","type":"specification","body":"IETF","designation":"RFC 2016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2016.txt","https://www.rfc-editor.org/rfc/rfc2016.pdf"],"folder":"IETF/RFC-2016","files":{"txt":{"path":"standards/IETF/RFC-2016/RFC-2016.txt","sha256":"dfbeb8611a4f82953ba420130f9a77e818d4fdfd85ef7b5372fb7428343632bd"}},"tags":["nested-reference","unchanged"],"summary":"This paper presents an experimental architecture for an agent system\n that provides sophisticated Internet information access and\n management. Not a generalized architecture for active objects that\n roam the Internet, these agents are modeled as extensions of existing\n pieces of the Internet information infrastructure. This experimental\n agent technology focuses on the necessary information structures to\n encapsulate Internet activities into objects that can be activated,\n transformed, and combined into larger structured activities.\n\nAcknowledgements\n\n Several people have shared thoughts and viewpoints that have helped\n shape the thinking behind this work over the past few years. We'd\n like to thank, in particular, Chris Weider, Patrik Faltstrom, Michael\n Mealling, Alan Emtage, and the participants in the IETF URI Working\n Group for many thought-provoking discussions.\n\n Sima Newell provi","scope_keywords":["2016","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2016 This paper presents an experimental architecture for an agent system\n that provides sophisticated Internet information access and\n management. Not a generalized architecture for active objects that\n roam the Internet, these agents are modeled as extensions of existing\n pieces of the Internet information infrastructure. This experimental\n agent technology focuses on the necessary information structures to\n encapsulate Internet activities into objects that can be activated,\n transformed, and combined into larger structured activities.\n\nAcknowledgements\n\n Several people have shared thoughts and viewpoints that have helped\n shape the thinking behind this work over the past few years. We'd\n like to thank, in particular, Chris Weider, Patrik Faltstrom, Michael\n Mealling, Alan Emtage, and the participants in the IETF URI Working\n Group for many thought-provoking discussions.\n\n Sima Newell provi 2016 identification management nested-reference unchanged"},{"id":"IETF RFC 2131","type":"specification","body":"IETF","designation":"RFC 2131","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2131.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2131.txt","https://www.rfc-editor.org/rfc/rfc2131.pdf"],"folder":"IETF/RFC-2131","files":{"txt":{"path":"standards/IETF/RFC-2131/RFC-2131.txt","sha256":"a043b705785b81762505ded4cf71d61392b2b1da2b4ce1e32c13bc984de5f4a5"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCPIP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 21], and DHCP participants can interoperate\n with BOOTP participants [9].","scope_keywords":["2131","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2489","folder":"IETF/RFC-2489","source":"IETF/RFC-2489/RFC-2489.txt","version":null},{"body":"IETF","designation":"RFC 2610","folder":"IETF/RFC-2610","source":"IETF/RFC-2610/RFC-2610.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2937","folder":"IETF/RFC-2937","source":"IETF/RFC-2937/RFC-2937.txt","version":null},{"body":"IETF","designation":"RFC 2939","folder":"IETF/RFC-2939","source":"IETF/RFC-2939/RFC-2939.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3004","folder":"IETF/RFC-3004","source":"IETF/RFC-3004/RFC-3004.txt","version":null},{"body":"IETF","designation":"RFC 3011","folder":"IETF/RFC-3011","source":"IETF/RFC-3011/RFC-3011.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3074","folder":"IETF/RFC-3074","source":"IETF/RFC-3074/RFC-3074.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3203","folder":"IETF/RFC-3203","source":"IETF/RFC-3203/RFC-3203.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3396","folder":"IETF/RFC-3396","source":"IETF/RFC-3396/RFC-3396.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 3993","folder":"IETF/RFC-3993","source":"IETF/RFC-3993/RFC-3993.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4361","folder":"IETF/RFC-4361","source":"IETF/RFC-4361/RFC-4361.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null},{"body":"IETF","designation":"RFC 4580","folder":"IETF/RFC-4580","source":"IETF/RFC-4580/RFC-4580.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 2131 The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCPIP network.\n DHCP is based on the Bootstrap Protocol (BOOTP) [7], adding the\n capability of automatic allocation of reusable network addresses and\n additional configuration options [19]. DHCP captures the behavior of\n BOOTP relay agents [7, 21], and DHCP participants can interoperate\n with BOOTP participants [9]. 2131 policies presentation nested-reference unchanged"},{"id":"IETF RFC 2136","type":"specification","body":"IETF","designation":"RFC 2136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2136.txt","https://www.rfc-editor.org/rfc/rfc2136.pdf"],"folder":"IETF/RFC-2136","files":{"txt":{"path":"standards/IETF/RFC-2136/RFC-2136.txt","sha256":"c6ee9f06e8dd817e260734adadef806a4296ed637d8afabc508f96ae84625bd5"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System was originally designed to support queries of\n a statically configured database. While the data was expected to\n change, the frequency of those changes was expected to be fairly low,\n and all updates were made as external edits to a zone's Master File.\n\n Using this specification of the UPDATE opcode, it is possible to add\n or delete RRs or RRsets from a specified zone. Prerequisites are\n specified separately from update operations, and can specify a\n dependency upon either the previous existence or nonexistence of an\n RRset, or the existence of a single RR.\n\n UPDATE is atomic, i.e., all prerequisites must be satisfied or else\n no update operations will take place. There are no data dependent\n error conditions defined after the prerequisites have been met.\n\n1 - Definitions\n\n This document intentionally gives more definition to the roles of\n \"Master,\" \"Slave,\" and \"P","scope_keywords":["2136"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2137","folder":"IETF/RFC-2137","source":"IETF/RFC-2137/RFC-2137.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5158","folder":"IETF/RFC-5158","source":"IETF/RFC-5158/RFC-5158.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 2136 The Domain Name System was originally designed to support queries of\n a statically configured database. While the data was expected to\n change, the frequency of those changes was expected to be fairly low,\n and all updates were made as external edits to a zone's Master File.\n\n Using this specification of the UPDATE opcode, it is possible to add\n or delete RRs or RRsets from a specified zone. Prerequisites are\n specified separately from update operations, and can specify a\n dependency upon either the previous existence or nonexistence of an\n RRset, or the existence of a single RR.\n\n UPDATE is atomic, i.e., all prerequisites must be satisfied or else\n no update operations will take place. There are no data dependent\n error conditions defined after the prerequisites have been met.\n\n1 - Definitions\n\n This document intentionally gives more definition to the roles of\n \"Master,\" \"Slave,\" and \"P 2136 nested-reference unchanged"},{"id":"IETF RFC 2137","type":"specification","body":"IETF","designation":"RFC 2137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2137.txt","https://www.rfc-editor.org/rfc/rfc2137.pdf"],"folder":"IETF/RFC-2137","files":{"txt":{"path":"standards/IETF/RFC-2137/RFC-2137.txt","sha256":"e791b25db0efa87631694cc23e5ad45aaa1250e7f954058141100f82f4c00d17"}},"tags":["nested-reference","unchanged"],"summary":"Domain Name System (DNS) protocol extensions have been defined to\n authenticate the data in DNS and provide key distribution services\n [RFC2065]. DNS Dynamic Update operations have also been defined\n [RFC2136], but without a detailed description of security for the\n update operation. This memo describes how to use DNSSEC digital\n signatures covering requests and data to secure updates and restrict\n updates to those authorized to perform them as indicated by the\n updater's possession of cryptographic keys.\n\nAcknowledgements\n\n The contributions of the following persons (who are listed in\n alphabetic order) to this memo are gratefully acknowledged:\n\n Olafur Gudmundsson (ogud@tis.com>\n Charlie Kaufman <Charlie_Kaufman@iris.com>\n Stuart Kwan <skwan@microsoft.com>\n Edward Lewis <lewis@tis.com>","scope_keywords":["2137","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null}],"search_text":"IETF RFC 2137 Domain Name System (DNS) protocol extensions have been defined to\n authenticate the data in DNS and provide key distribution services\n [RFC2065]. DNS Dynamic Update operations have also been defined\n [RFC2136], but without a detailed description of security for the\n update operation. This memo describes how to use DNSSEC digital\n signatures covering requests and data to secure updates and restrict\n updates to those authorized to perform them as indicated by the\n updater's possession of cryptographic keys.\n\nAcknowledgements\n\n The contributions of the following persons (who are listed in\n alphabetic order) to this memo are gratefully acknowledged:\n\n Olafur Gudmundsson (ogud@tis.com>\n Charlie Kaufman <Charlie_Kaufman@iris.com>\n Stuart Kwan <skwan@microsoft.com>\n Edward Lewis <lewis@tis.com> 2137 key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2151","type":"specification","body":"IETF","designation":"RFC 2151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2151.txt","https://www.rfc-editor.org/rfc/rfc2151.pdf"],"folder":"IETF/RFC-2151","files":{"txt":{"path":"standards/IETF/RFC-2151/RFC-2151.txt","sha256":"dd194a685fea490195ee9d7f7a4fe68967b6fc2561eb9f72c28e04253034bf2b"}},"tags":["nested-reference","unchanged"],"summary":"This memo is an introductory guide to many of the most commonly-\n available TCP/IP and Internet tools and utilities. It also describes\n discussion lists accessible from the Internet, ways to obtain\n Internet and TCP/IP documents, and some resources that help users\n weave their way through the Internet.","scope_keywords":["2151","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 2151 This memo is an introductory guide to many of the most commonly-\n available TCP/IP and Internet tools and utilities. It also describes\n discussion lists accessible from the Internet, ways to obtain\n Internet and TCP/IP documents, and some resources that help users\n weave their way through the Internet. 2151 policy risk nested-reference unchanged"},{"id":"IETF RFC 2165","type":"specification","body":"IETF","designation":"RFC 2165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2165.txt","https://www.rfc-editor.org/rfc/rfc2165.pdf"],"folder":"IETF/RFC-2165","files":{"txt":{"path":"standards/IETF/RFC-2165/RFC-2165.txt","sha256":"ab38d38b03ddd3a9149d0e530fe5b3a98524d76e8d0c0b047b72d4d027717ae4"}},"tags":["nested-reference","unchanged"],"summary":"The Service Location Protocol provides a scalable framework for the\n discovery and selection of network services. Using this protocol,\n computers using the Internet no longer need so much static\n configuration of network services for network based applications.\n This is especially important as computers become more portable, and\n users less tolerant or able to fulfill the demands of network system\n administration.","scope_keywords":["2165","attribute","attributes","authentication","certificate","certificates","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2610","folder":"IETF/RFC-2610","source":"IETF/RFC-2610/RFC-2610.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2165 The Service Location Protocol provides a scalable framework for the\n discovery and selection of network services. Using this protocol,\n computers using the Internet no longer need so much static\n configuration of network services for network based applications.\n This is especially important as computers become more portable, and\n users less tolerant or able to fulfill the demands of network system\n administration. 2165 attribute attributes authentication certificate certificates presentation nested-reference unchanged"},{"id":"IETF RFC 2167","type":"specification","body":"IETF","designation":"RFC 2167","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2167.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2167.txt","https://www.rfc-editor.org/rfc/rfc2167.pdf"],"folder":"IETF/RFC-2167","files":{"txt":{"path":"standards/IETF/RFC-2167/RFC-2167.txt","sha256":"3a9023f5957a93ce9a732e985a7f562e15e54e545b7217e88f7129f0d3a1b1eb"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes Version 1.5 of the client/server interaction of\n RWhois. RWhois provides a distributed system for the discovery,\n retrieval, and maintenance of directory information. This system is\n primarily hierarchical by design. It allows for the deterministic\n routing of a query based on hierarchical tags, referring the user\n closer to the maintainer of the information. While RWhois can be\n considered a generic directory services protocol, it distinguishes\n itself from other protocols by providing an integrated, hierarchical\n architecture and query routing mechanism.\n\n1. Introduction\n\n Early in the development of the ARPANET, the SRI-NIC established a\n centralized Whois database that provided host and network information\n about the systems connected to the network and the electronic mail\n (email) addresses of the users on those systems [RFC 954]. The\n ARPANET experiment evolved ","scope_keywords":["2167","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null}],"search_text":"IETF RFC 2167 This memo describes Version 1.5 of the client/server interaction of\n RWhois. RWhois provides a distributed system for the discovery,\n retrieval, and maintenance of directory information. This system is\n primarily hierarchical by design. It allows for the deterministic\n routing of a query based on hierarchical tags, referring the user\n closer to the maintainer of the information. While RWhois can be\n considered a generic directory services protocol, it distinguishes\n itself from other protocols by providing an integrated, hierarchical\n architecture and query routing mechanism.\n\n1. Introduction\n\n Early in the development of the ARPANET, the SRI-NIC established a\n centralized Whois database that provided host and network information\n about the systems connected to the network and the electronic mail\n (email) addresses of the users on those systems [RFC 954]. The\n ARPANET experiment evolved  2167 key nested-reference unchanged"},{"id":"IETF RFC 2181","type":"specification","body":"IETF","designation":"RFC 2181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2181.txt","https://www.rfc-editor.org/rfc/rfc2181.pdf"],"folder":"IETF/RFC-2181","files":{"txt":{"path":"standards/IETF/RFC-2181/RFC-2181.txt","sha256":"c00423dc0b34d025e72b977a08c71f4357977e273d22670f29954109ac0f9c70"}},"tags":["nested-reference","unchanged"],"summary":"This document considers some areas that have been identified as\n problems with the specification of the Domain Name System, and\n proposes remedies for the defects identified. Eight separate issues\n are considered:\n\n + IP packet header address usage from multi-homed servers,\n + TTLs in sets of records with the same name, class, and type,\n + correct handling of zone cuts,\n + three minor issues concerning SOA records and their use,\n + the precise definition of the Time to Live (TTL)\n + Use of the TC (truncated) header bit\n + the issue of what is an authoritative, or canonical, name,\n + and the issue of what makes a valid DNS label.\n\n The first six of these are areas where the correct behaviour has been\n somewhat unclear, we seek to rectify that. The other two are already\n adequately specified, however the specifications seem to be sometimes\n ignored. We seek to reinforce the existing specif","scope_keywords":["2181","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2182","folder":"IETF/RFC-2182","source":"IETF/RFC-2182/RFC-2182.txt","version":null},{"body":"IETF","designation":"RFC 2308","folder":"IETF/RFC-2308","source":"IETF/RFC-2308/RFC-2308.txt","version":null},{"body":"IETF","designation":"RFC 2317","folder":"IETF/RFC-2317","source":"IETF/RFC-2317/RFC-2317.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2763","folder":"IETF/RFC-2763","source":"IETF/RFC-2763/RFC-2763.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5301","folder":"IETF/RFC-5301","source":"IETF/RFC-5301/RFC-5301.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 2181 This document considers some areas that have been identified as\n problems with the specification of the Domain Name System, and\n proposes remedies for the defects identified. Eight separate issues\n are considered:\n\n + IP packet header address usage from multi-homed servers,\n + TTLs in sets of records with the same name, class, and type,\n + correct handling of zone cuts,\n + three minor issues concerning SOA records and their use,\n + the precise definition of the Time to Live (TTL)\n + Use of the TC (truncated) header bit\n + the issue of what is an authoritative, or canonical, name,\n + and the issue of what makes a valid DNS label.\n\n The first six of these are areas where the correct behaviour has been\n somewhat unclear, we seek to rectify that. The other two are already\n adequately specified, however the specifications seem to be sometimes\n ignored. We seek to reinforce the existing specif 2181 tls nested-reference unchanged"},{"id":"IETF RFC 2182","type":"specification","body":"IETF","designation":"RFC 2182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2182.txt","https://www.rfc-editor.org/rfc/rfc2182.pdf"],"folder":"IETF/RFC-2182","files":{"txt":{"path":"standards/IETF/RFC-2182/RFC-2182.txt","sha256":"403ecf810d3cdf7d36c934a7d1eb34455e1355889a44023e3a1cb5cf14127854"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System requires that multiple servers exist for every\n delegated domain (zone). This document discusses the selection of\n secondary servers for DNS zones. Both the physical and topological\n location of each server are material considerations when selecting\n secondary servers. The number of servers appropriate for a zone is\n also discussed, and some general secondary server maintenance issues\n considered.\n\nElz, et al. Best Current Practice [Page 1]\n\f\nRFC 2182 Selection and Operation of Secondary DNS Servers July 1997\n\nContents\n\n Abstract ................................................... 1\n 1 Introduction ............................................... 2\n 2 Definitions ................................................ 2\n 3 Secondary Servers .......................................... 3\n 4 Unreachable servers ........................................ 5\n 5 How many secondaries","scope_keywords":["2182","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 3258","folder":"IETF/RFC-3258","source":"IETF/RFC-3258/RFC-3258.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 2182 The Domain Name System requires that multiple servers exist for every\n delegated domain (zone). This document discusses the selection of\n secondary servers for DNS zones. Both the physical and topological\n location of each server are material considerations when selecting\n secondary servers. The number of servers appropriate for a zone is\n also discussed, and some general secondary server maintenance issues\n considered.\n\nElz, et al. Best Current Practice [Page 1]\n\f\nRFC 2182 Selection and Operation of Secondary DNS Servers July 1997\n\nContents\n\n Abstract ................................................... 1\n 1 Introduction ............................................... 2\n 2 Definitions ................................................ 2\n 3 Secondary Servers .......................................... 3\n 4 Unreachable servers ........................................ 5\n 5 How many secondaries 2182 path policy nested-reference unchanged"},{"id":"IETF RFC 2219","type":"specification","body":"IETF","designation":"RFC 2219","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2219.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2219.txt","https://www.rfc-editor.org/rfc/rfc2219.pdf"],"folder":"IETF/RFC-2219","files":{"txt":{"path":"standards/IETF/RFC-2219/RFC-2219.txt","sha256":"52dc32fdeb02171bb1bfab5c8c129822f72b2e67d8ee4de2ec4ae60a1a3db783"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Hamilton\nRequest for Comments: 2219 Loughborough University\nBCP: 17 R. Wright\nCategory: Best Current Practice Lawrence Berkeley Laboratory\n October 1997\n\n Use of DNS Aliases for Network Services\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n It has become a common practice to use symbolic names (usually\n CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to\n refer to network services such as anonymous FTP [RFC-959] servers,\n Gopher [RFC-1436] servers, and most notably World-Wide Web HTTP\n [RFC-1945] servers. This is desirable for a number of reasons. It\n provides a way of moving services from one machine to another\n transparently, and a mechanism by which people or agents may\n p","scope_keywords":["2219","http","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null}],"search_text":"IETF RFC 2219 Network Working Group M. Hamilton\nRequest for Comments: 2219 Loughborough University\nBCP: 17 R. Wright\nCategory: Best Current Practice Lawrence Berkeley Laboratory\n October 1997\n\n Use of DNS Aliases for Network Services\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n It has become a common practice to use symbolic names (usually\n CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to\n refer to network services such as anonymous FTP [RFC-959] servers,\n Gopher [RFC-1436] servers, and most notably World-Wide Web HTTP\n [RFC-1945] servers. This is desirable for a number of reasons. It\n provides a way of moving services from one machine to another\n transparently, and a mechanism by which people or agents may\n p 2219 http registered nested-reference unchanged"},{"id":"IETF RFC 2230","type":"specification","body":"IETF","designation":"RFC 2230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2230.txt","https://www.rfc-editor.org/rfc/rfc2230.pdf"],"folder":"IETF/RFC-2230","files":{"txt":{"path":"standards/IETF/RFC-2230/RFC-2230.txt","sha256":"cc204361f579d09a9ad6202c2216a2407a40fc50d0b265f3468773f5d26d503f"}},"tags":["nested-reference","unchanged"],"summary":"This note describes a mechanism whereby authorisation for one node to\n act as key exchanger for a second node is delegated and made\n available via the Secure DNS. This mechanism is intended to be used\n only with the Secure DNS. It can be used with several security\n services. For example, a system seeking to use IP Security [RFC-\n 1825, RFC-1826, RFC-1827] to protect IP packets for a given\n destination can use this mechanism to determine the set of authorised\n remote key exchanger systems for that destination.\n\n1. INTRODUCTION\n\n The Domain Name System (DNS) is the standard way that Internet nodes\n locate information about addresses, mail exchangers, and other data\n relating to remote Internet nodes. [RFC-1035, RFC-1034] More\n recently, Eastlake and Kaufman have defined standards-track security\n extensions to the DNS. [RFC-2065] These security extensions can be\n used to authenticate signed","scope_keywords":["2230","key","keys","management","path","policies","policy","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null}],"search_text":"IETF RFC 2230 This note describes a mechanism whereby authorisation for one node to\n act as key exchanger for a second node is delegated and made\n available via the Secure DNS. This mechanism is intended to be used\n only with the Secure DNS. It can be used with several security\n services. For example, a system seeking to use IP Security [RFC-\n 1825, RFC-1826, RFC-1827] to protect IP packets for a given\n destination can use this mechanism to determine the set of authorised\n remote key exchanger systems for that destination.\n\n1. INTRODUCTION\n\n The Domain Name System (DNS) is the standard way that Internet nodes\n locate information about addresses, mail exchangers, and other data\n relating to remote Internet nodes. [RFC-1035, RFC-1034] More\n recently, Eastlake and Kaufman have defined standards-track security\n extensions to the DNS. [RFC-2065] These security extensions can be\n used to authenticate signed 2230 key keys management path policies policy qualified subject nested-reference unchanged"},{"id":"IETF RFC 2247","type":"specification","body":"IETF","designation":"RFC 2247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2247.txt","https://www.rfc-editor.org/rfc/rfc2247.pdf"],"folder":"IETF/RFC-2247","files":{"txt":{"path":"standards/IETF/RFC-2247/RFC-2247.txt","sha256":"ed3395e488f08899fc93f828f41f890e210b4612680714cab64d68c1579939f9"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) uses X.500-\n compatible distinguished names [3] for providing unique\n identification of entries.\n\n This document defines an algorithm by which a name registered with\n the Internet Domain Name Service [2] can be represented as an LDAP\n distinguished name.\n\n2. Background\n\n The Domain (Nameserver) System (DNS) provides a hierarchical resource\n labeling system. A name is made up of an ordered set of components,\n each of which are short strings. An example domain name with two\n components would be \"CRITICAL-ANGLE.COM\".\n\nKille, et. al. Standards Track [Page 1]\n\f\nRFC 2247 Using Domains in LDAP/X.500 January 1998\n\n LDAP-based directories provide a more general hierarchical naming\n framework. A primary difference in specification of distinguished\n names from domain names is that each component of an distinguished\n name has an explicit attribute typ","scope_keywords":["2247","algorithm","attribute","attributes","delivery","holder","identification","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null}],"search_text":"IETF RFC 2247 The Lightweight Directory Access Protocol (LDAP) uses X.500-\n compatible distinguished names [3] for providing unique\n identification of entries.\n\n This document defines an algorithm by which a name registered with\n the Internet Domain Name Service [2] can be represented as an LDAP\n distinguished name.\n\n2. Background\n\n The Domain (Nameserver) System (DNS) provides a hierarchical resource\n labeling system. A name is made up of an ordered set of components,\n each of which are short strings. An example domain name with two\n components would be \"CRITICAL-ANGLE.COM\".\n\nKille, et. al. Standards Track [Page 1]\n\f\nRFC 2247 Using Domains in LDAP/X.500 January 1998\n\n LDAP-based directories provide a more general hierarchical naming\n framework. A primary difference in specification of distinguished\n names from domain names is that each component of an distinguished\n name has an explicit attribute typ 2247 algorithm attribute attributes delivery holder identification registered nested-reference unchanged"},{"id":"IETF RFC 2280","type":"specification","body":"IETF","designation":"RFC 2280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2280.txt","https://www.rfc-editor.org/rfc/rfc2280.pdf"],"folder":"IETF/RFC-2280","files":{"txt":{"path":"standards/IETF/RFC-2280/RFC-2280.txt","sha256":"98e0f32290272924d0fea672a83eb185fcd9c012f4dd81c8049b342422785ff1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Alaettinoglu\nRequest for Comments: 2280 USC/Information Sciences Institute\nCategory: Standards Track T. Bates\n Cisco Systems\n E. Gerich\n At Home Network\n D. Karrenberg\n RIPE\n D. Meyer\n University of Oregon\n M. Terpstra\n Bay Networks\n C. Villamizar\n ANS\n January 1998\n\n Routing Policy Specification Language (RPSL)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n Table of Contents\n\n 1 Introduction 2\n 2 RPSL Names, Reserved Words, and Representation 3\n 3 Contact Information ","scope_keywords":["2280","attribute","policies","policy","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null}],"search_text":"IETF RFC 2280 Network Working Group C. Alaettinoglu\nRequest for Comments: 2280 USC/Information Sciences Institute\nCategory: Standards Track T. Bates\n Cisco Systems\n E. Gerich\n At Home Network\n D. Karrenberg\n RIPE\n D. Meyer\n University of Oregon\n M. Terpstra\n Bay Networks\n C. Villamizar\n ANS\n January 1998\n\n Routing Policy Specification Language (RPSL)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n Table of Contents\n\n 1 Introduction 2\n 2 RPSL Names, Reserved Words, and Representation 3\n 3 Contact Information  2280 attribute policies policy presentation registered nested-reference unchanged"},{"id":"IETF RFC 2308","type":"specification","body":"IETF","designation":"RFC 2308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2308.txt","https://www.rfc-editor.org/rfc/rfc2308.pdf"],"folder":"IETF/RFC-2308","files":{"txt":{"path":"standards/IETF/RFC-2308/RFC-2308.txt","sha256":"7fdfca474a92f7dfee13e70998c40c263104087da46cac91944f643562ce3fba"}},"tags":["nested-reference","unchanged"],"summary":"[RFC1034] provided a description of how to cache negative responses.\n It however had a fundamental flaw in that it did not allow a name\n server to hand out those cached responses to other resolvers, thereby\n greatly reducing the effect of the caching. This document addresses\n issues raise in the light of experience and replaces [RFC1034 Section\n 4.3.4].\n\n Negative caching was an optional part of the DNS specification and\n deals with the caching of the non-existence of an RRset [RFC2181] or\n domain name.\n\n Negative caching is useful as it reduces the response time for\n negative answers. It also reduces the number of messages that have\n to be sent between resolvers and name servers hence overall network\n traffic. A large proportion of DNS traffic on the Internet could be\n eliminated if all resolvers implemented negative caching. With this\n in mind negative caching should no longer be seen ","scope_keywords":["2308","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 2308 [RFC1034] provided a description of how to cache negative responses.\n It however had a fundamental flaw in that it did not allow a name\n server to hand out those cached responses to other resolvers, thereby\n greatly reducing the effect of the caching. This document addresses\n issues raise in the light of experience and replaces [RFC1034 Section\n 4.3.4].\n\n Negative caching was an optional part of the DNS specification and\n deals with the caching of the non-existence of an RRset [RFC2181] or\n domain name.\n\n Negative caching is useful as it reduces the response time for\n negative answers. It also reduces the number of messages that have\n to be sent between resolvers and name servers hence overall network\n traffic. A large proportion of DNS traffic on the Internet could be\n eliminated if all resolvers implemented negative caching. With this\n in mind negative caching should no longer be seen  2308 key nested-reference unchanged"},{"id":"IETF RFC 2317","type":"specification","body":"IETF","designation":"RFC 2317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2317.txt","https://www.rfc-editor.org/rfc/rfc2317.pdf"],"folder":"IETF/RFC-2317","files":{"txt":{"path":"standards/IETF/RFC-2317/RFC-2317.txt","sha256":"2e491a78108d652ec1f3233b32726589f696e97ce3568f4ee1e10c80a5e4e68d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Eidnes\nRequest for Comments: 2317 SINTEF RUNIT\nBCP: 20 G. de Groot\nCategory: Best Current Practice Berkeley Software Design, Inc.\n P. Vixie\n Internet Software Consortium\n March 1998\n\n Classless IN-ADDR.ARPA delegation\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Introduction\n\n This document describes a way to do IN-ADDR.ARPA delegation on non-\n octet boundaries for address spaces covering fewer than 256\n addresses. The proposed method should thus remove one of the\n objections to subnet on non-octet boundaries but perhaps more\n significantly, make it possible to assign IP address space in smaller\n chunks than 24-bit","scope_keywords":["2317","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null}],"search_text":"IETF RFC 2317 Network Working Group H. Eidnes\nRequest for Comments: 2317 SINTEF RUNIT\nBCP: 20 G. de Groot\nCategory: Best Current Practice Berkeley Software Design, Inc.\n P. Vixie\n Internet Software Consortium\n March 1998\n\n Classless IN-ADDR.ARPA delegation\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Introduction\n\n This document describes a way to do IN-ADDR.ARPA delegation on non-\n octet boundaries for address spaces covering fewer than 256\n addresses. The proposed method should thus remove one of the\n objections to subnet on non-octet boundaries but perhaps more\n significantly, make it possible to assign IP address space in smaller\n chunks than 24-bit 2317 algorithm nested-reference unchanged"},{"id":"IETF RFC 2396","type":"specification","body":"IETF","designation":"RFC 2396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2396.txt","https://www.rfc-editor.org/rfc/rfc2396.pdf"],"folder":"IETF/RFC-2396","files":{"txt":{"path":"standards/IETF/RFC-2396/RFC-2396.txt","sha256":"67866c0aaa65b29372b4c7ca80ffdfa6caee825088593f4b8b296bff3c05cdc7"}},"tags":["nested-reference","unchanged"],"summary":"A Uniform Resource Identifier (URI) is a compact string of characters\n for identifying an abstract or physical resource. This document\n defines the generic syntax of URI, including both absolute and\n relative forms, and guidelines for their use; it revises and replaces\n the generic definitions in RFC 1738 and RFC 1808.\n\n This document defines a grammar that is a superset of all valid URI,\n such that an implementation can parse the common components of a URI\n reference without knowing the scheme-specific requirements of every\n possible identifier type. This document does not define a generative\n grammar for URI; that task will be performed by the individual\n specifications of each URI scheme.\n\nBerners-Lee, et. al. Standards Track [Page 1]\n\f\nRFC 2396 URI Generic Syntax August 1998\n\n1. Introduction\n\n Uniform Resource Identifiers (URI) provide a simple and extensible\n means for identifying a","scope_keywords":["2396","attribute","attributes","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"IETF","designation":"RFC 2397","folder":"IETF/RFC-2397","source":"IETF/RFC-2397/RFC-2397.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2629","folder":"IETF/RFC-2629","source":"IETF/RFC-2629/RFC-2629.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2717","folder":"IETF/RFC-2717","source":"IETF/RFC-2717/RFC-2717.txt","version":null},{"body":"IETF","designation":"RFC 2718","folder":"IETF/RFC-2718","source":"IETF/RFC-2718/RFC-2718.txt","version":null},{"body":"IETF","designation":"RFC 2732","folder":"IETF/RFC-2732","source":"IETF/RFC-2732/RFC-2732.txt","version":null},{"body":"IETF","designation":"RFC 2756","folder":"IETF/RFC-2756","source":"IETF/RFC-2756/RFC-2756.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2803","folder":"IETF/RFC-2803","source":"IETF/RFC-2803/RFC-2803.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2807","folder":"IETF/RFC-2807","source":"IETF/RFC-2807/RFC-2807.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 2965","folder":"IETF/RFC-2965","source":"IETF/RFC-2965/RFC-2965.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3151","folder":"IETF/RFC-3151","source":"IETF/RFC-3151/RFC-3151.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3368","folder":"IETF/RFC-3368","source":"IETF/RFC-3368/RFC-3368.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3688","folder":"IETF/RFC-3688","source":"IETF/RFC-3688/RFC-3688.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3741","folder":"IETF/RFC-3741","source":"IETF/RFC-3741/RFC-3741.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3902","folder":"IETF/RFC-3902","source":"IETF/RFC-3902/RFC-3902.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5781","folder":"IETF/RFC-5781","source":"IETF/RFC-5781/RFC-5781.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null}],"search_text":"IETF RFC 2396 A Uniform Resource Identifier (URI) is a compact string of characters\n for identifying an abstract or physical resource. This document\n defines the generic syntax of URI, including both absolute and\n relative forms, and guidelines for their use; it revises and replaces\n the generic definitions in RFC 1738 and RFC 1808.\n\n This document defines a grammar that is a superset of all valid URI,\n such that an implementation can parse the common components of a URI\n reference without knowing the scheme-specific requirements of every\n possible identifier type. This document does not define a generative\n grammar for URI; that task will be performed by the individual\n specifications of each URI scheme.\n\nBerners-Lee, et. al. Standards Track [Page 1]\n\f\nRFC 2396 URI Generic Syntax August 1998\n\n1. Introduction\n\n Uniform Resource Identifiers (URI) provide a simple and extensible\n means for identifying a 2396 attribute attributes http presentation nested-reference unchanged"},{"id":"IETF RFC 2421","type":"specification","body":"IETF","designation":"RFC 2421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2421.txt","https://www.rfc-editor.org/rfc/rfc2421.pdf"],"folder":"IETF/RFC-2421","files":{"txt":{"path":"standards/IETF/RFC-2421/RFC-2421.txt","sha256":"921b5e83152662e349400dd207d5a880e1e372fab0540cc0b79e9562f9e12d99"}},"tags":["nested-reference","unchanged"],"summary":"A class of special-purpose computers has evolved to provide voice\n messaging services. These machines generally interface to a\n telephone switch and provide call answering and voice messaging\n services. Traditionally, messages sent to a non-local machine are\n transported using analog networking protocols based on DTMF signaling\n and analog voice playback. As the demand for networking increases,\n there is a need for a standard high-quality digital protocol to\n connect these machines. The following document is a profile of the\n Internet standard MIME and ESMTP protocols for use as a digital voice\n messaging networking protocol. The profile is referred to as VPIM\n (Voice Profile for Internet Mail) in this document.\n\n This profile is based on earlier work in the Audio Message\n Interchange Specification (AMIS) group that defined a voice messaging\n protocol based on X.400 technology. This prof","scope_keywords":["2421","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 2424","folder":"IETF/RFC-2424","source":"IETF/RFC-2424/RFC-2424.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 3803","folder":"IETF/RFC-3803","source":"IETF/RFC-3803/RFC-3803.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null}],"search_text":"IETF RFC 2421 A class of special-purpose computers has evolved to provide voice\n messaging services. These machines generally interface to a\n telephone switch and provide call answering and voice messaging\n services. Traditionally, messages sent to a non-local machine are\n transported using analog networking protocols based on DTMF signaling\n and analog voice playback. As the demand for networking increases,\n there is a need for a standard high-quality digital protocol to\n connect these machines. The following document is a profile of the\n Internet standard MIME and ESMTP protocols for use as a digital voice\n messaging networking protocol. The profile is referred to as VPIM\n (Voice Profile for Internet Mail) in this document.\n\n This profile is based on earlier work in the Audio Message\n Interchange Specification (AMIS) group that defined a voice messaging\n protocol based on X.400 technology. This prof 2421 key management profile profiles nested-reference unchanged"},{"id":"IETF RFC 2459","type":"specification","body":"IETF","designation":"RFC 2459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2459.txt","https://www.rfc-editor.org/rfc/rfc2459.pdf"],"folder":"IETF/RFC-2459","files":{"txt":{"path":"standards/IETF/RFC-2459/RFC-2459.txt","sha256":"d8eab6509ff3f7631b589419844b40f3d733adf116897a7c9e63706d08979895"}},"tags":["nested-reference","unchanged"],"summary":"This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use\n in the Internet. An overview of the approach and model are provided\n as an introduction. The X.509 v3 certificate format is described in\n detail, with additional information regarding the format and\n semantics of Internet name forms (e.g., IP addresses). Standard\n certificate extensions are described and one new Internet-specific\n extension is defined. A required set of certificate extensions is\n specified. The X.509 v2 CRL format is described and a required\n extension set is defined as well. An algorithm for X.509 certificate\n path validation is described. Supplemental information is provided\n describing the format of public keys and digital signatures in X.509\n certificates for common Internet public key encryption algorithms\n (i.e., RSA, DSA, and Diffie-Hellman). ASN.1 modules and examples are\n provided in the appen","scope_keywords":["2459","algorithm","algorithms","attribute","attributes","certificate","certificates","crl","encryption","issuer","key","keys","management","path","pki","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 2528","folder":"IETF/RFC-2528","source":"IETF/RFC-2528/RFC-2528.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2587","folder":"IETF/RFC-2587","source":"IETF/RFC-2587/RFC-2587.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2631","folder":"IETF/RFC-2631","source":"IETF/RFC-2631/RFC-2631.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2875","folder":"IETF/RFC-2875","source":"IETF/RFC-2875/RFC-2875.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"IETF RFC 2459 This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use\n in the Internet. An overview of the approach and model are provided\n as an introduction. The X.509 v3 certificate format is described in\n detail, with additional information regarding the format and\n semantics of Internet name forms (e.g., IP addresses). Standard\n certificate extensions are described and one new Internet-specific\n extension is defined. A required set of certificate extensions is\n specified. The X.509 v2 CRL format is described and a required\n extension set is defined as well. An algorithm for X.509 certificate\n path validation is described. Supplemental information is provided\n describing the format of public keys and digital signatures in X.509\n certificates for common Internet public key encryption algorithms\n (i.e., RSA, DSA, and Diffie-Hellman). ASN.1 modules and examples are\n provided in the appen 2459 algorithm algorithms attribute attributes certificate certificates crl encryption issuer key keys management path pki policies nested-reference unchanged"},{"id":"IETF RFC 2505","type":"specification","body":"IETF","designation":"RFC 2505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2505.txt","https://www.rfc-editor.org/rfc/rfc2505.pdf"],"folder":"IETF/RFC-2505","files":{"txt":{"path":"standards/IETF/RFC-2505/RFC-2505.txt","sha256":"06c44db836a98f0be51266b8828c1c6f098148c9f47a4f344c1363302091db6a"}},"tags":["nested-reference","unchanged"],"summary":"This memo gives a number of implementation recommendations for SMTP,\n [1], MTAs (Mail Transfer Agents, e.g. sendmail, [8]) to make them\n more capable of reducing the impact of spam(*).\n\n The intent is that these recommendations will help clean up the spam\n situation, if applied on enough SMTP MTAs on the Internet, and that\n they should be used as guidelines for the various MTA vendors. We are\n fully aware that this is not the final solution, but if these\n recommendations were included, and used, on all Internet SMTP MTAs,\n things would improve considerably and give time to design a more long\n term solution. The Future Work section suggests some ideas that may\n be part of such a long term solution. It might, though, very well be\n the case that the ultimate solution is social, political, or legal,\n rather than technical in nature.\n\n The implementor should be aware of the increased risk of ","scope_keywords":["2505","qualified","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 2505 This memo gives a number of implementation recommendations for SMTP,\n [1], MTAs (Mail Transfer Agents, e.g. sendmail, [8]) to make them\n more capable of reducing the impact of spam(*).\n\n The intent is that these recommendations will help clean up the spam\n situation, if applied on enough SMTP MTAs on the Internet, and that\n they should be used as guidelines for the various MTA vendors. We are\n fully aware that this is not the final solution, but if these\n recommendations were included, and used, on all Internet SMTP MTAs,\n things would improve considerably and give time to design a more long\n term solution. The Future Work section suggests some ideas that may\n be part of such a long term solution. It might, though, very well be\n the case that the ultimate solution is social, political, or legal,\n rather than technical in nature.\n\n The implementor should be aware of the increased risk of  2505 qualified risk nested-reference unchanged"},{"id":"IETF RFC 2536","type":"specification","body":"IETF","designation":"RFC 2536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2536.txt","https://www.rfc-editor.org/rfc/rfc2536.pdf"],"folder":"IETF/RFC-2536","files":{"txt":{"path":"standards/IETF/RFC-2536/RFC-2536.txt","sha256":"768c15de21907cfd9816436ac186da15d527112c2174b71d5f6727f24ee29032"}},"tags":["nested-reference","unchanged"],"summary":"A standard method for storing US Government Digital Signature\n Algorithm keys and signatures in the Domain Name System is described\n which utilizes DNS KEY and SIG resource records.","scope_keywords":["2536","algorithm","algorithms","authentication","hash","key","keys","policies","policy","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null}],"search_text":"IETF RFC 2536 A standard method for storing US Government Digital Signature\n Algorithm keys and signatures in the Domain Name System is described\n which utilizes DNS KEY and SIG resource records. 2536 algorithm algorithms authentication hash key keys policies policy signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2537","type":"specification","body":"IETF","designation":"RFC 2537","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2537.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2537.txt","https://www.rfc-editor.org/rfc/rfc2537.pdf"],"folder":"IETF/RFC-2537","files":{"txt":{"path":"standards/IETF/RFC-2537/RFC-2537.txt","sha256":"b82776802755360c6ad3b1c58c115bd4a982bcbc8c35a79fb5682c72a3e2bc72"}},"tags":["nested-reference","unchanged"],"summary":"A standard method for storing RSA keys and and RSA/MD5 based\n signatures in the Domain Name System is described which utilizes DNS\n KEY and SIG resource records.","scope_keywords":["2537","algorithm","algorithms","authentication","hash","key","keys","policies","policy","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2536","folder":"IETF/RFC-2536","source":"IETF/RFC-2536/RFC-2536.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null}],"search_text":"IETF RFC 2537 A standard method for storing RSA keys and and RSA/MD5 based\n signatures in the Domain Name System is described which utilizes DNS\n KEY and SIG resource records. 2537 algorithm algorithms authentication hash key keys policies policy signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2538","type":"specification","body":"IETF","designation":"RFC 2538","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2538.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2538.txt","https://www.rfc-editor.org/rfc/rfc2538.pdf"],"folder":"IETF/RFC-2538","files":{"txt":{"path":"standards/IETF/RFC-2538/RFC-2538.txt","sha256":"6274f5d7c1ed8a246be3d9a83dc6bf7d7e956d1ad5eaa8dd709a75ba87af5e42"}},"tags":["nested-reference","unchanged"],"summary":"Cryptographic public key are frequently published and their\n authenticity demonstrated by certificates. A CERT resource record\n (RR) is defined so that such certificates and related certificate\n revocation lists can be stored in the Domain Name System (DNS).","scope_keywords":["2538","algorithm","authorization","certificate","certificates","crl","issuer","key","keys","pki","presentation","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null}],"search_text":"IETF RFC 2538 Cryptographic public key are frequently published and their\n authenticity demonstrated by certificates. A CERT resource record\n (RR) is defined so that such certificates and related certificate\n revocation lists can be stored in the Domain Name System (DNS). 2538 algorithm authorization certificate certificates crl issuer key keys pki presentation profile revocation signature nested-reference unchanged"},{"id":"IETF RFC 2539","type":"specification","body":"IETF","designation":"RFC 2539","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2539.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2539.txt","https://www.rfc-editor.org/rfc/rfc2539.pdf"],"folder":"IETF/RFC-2539","files":{"txt":{"path":"standards/IETF/RFC-2539/RFC-2539.txt","sha256":"53be5bde33ccc3f5443a74bb0a6e64512358b0ce15d5d1a2474ba1ddbe6ee52a"}},"tags":["nested-reference","unchanged"],"summary":"A standard method for storing Diffie-Hellman keys in the Domain Name\n System is described which utilizes DNS KEY resource records.\n\nAcknowledgements\n\n Part of the format for Diffie-Hellman keys and the description\n thereof was taken from a work in progress by:\n\n Ashar Aziz <ashar.aziz@eng.sun.com>\n Tom Markson <markson@incog.com>\n Hemma Prafullchandra <hemma@eng.sun.com>\n\n In addition, the following person provided useful comments that have\n been incorporated:\n\n Ran Atkinson <rja@inet.org>\n Thomas Narten <narten@raleigh.ibm.com>\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2539 Diffie-Hellman Keys in the DNS March 1999","scope_keywords":["2539","algorithm","authentication","key","keys","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null}],"search_text":"IETF RFC 2539 A standard method for storing Diffie-Hellman keys in the Domain Name\n System is described which utilizes DNS KEY resource records.\n\nAcknowledgements\n\n Part of the format for Diffie-Hellman keys and the description\n thereof was taken from a work in progress by:\n\n Ashar Aziz <ashar.aziz@eng.sun.com>\n Tom Markson <markson@incog.com>\n Hemma Prafullchandra <hemma@eng.sun.com>\n\n In addition, the following person provided useful comments that have\n been incorporated:\n\n Ran Atkinson <rja@inet.org>\n Thomas Narten <narten@raleigh.ibm.com>\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2539 Diffie-Hellman Keys in the DNS March 1999 2539 algorithm authentication key keys presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 2540","type":"specification","body":"IETF","designation":"RFC 2540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2540.txt","https://www.rfc-editor.org/rfc/rfc2540.pdf"],"folder":"IETF/RFC-2540","files":{"txt":{"path":"standards/IETF/RFC-2540/RFC-2540.txt","sha256":"e0efdca2c401778b6244132bbf25d6a567bff0c9183e15396bc8d96cc4b893ba"}},"tags":["nested-reference","unchanged"],"summary":"A standard format is defined for representing detached DNS\n information. This is anticipated to be of use for storing\n information retrieved from the Domain Name System (DNS), including\n security information, in archival contexts or contexts not connected\n to the Internet.","scope_keywords":["2540","authentication","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null}],"search_text":"IETF RFC 2540 A standard format is defined for representing detached DNS\n information. This is anticipated to be of use for storing\n information retrieved from the Domain Name System (DNS), including\n security information, in archival contexts or contexts not connected\n to the Internet. 2540 authentication key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2541","type":"specification","body":"IETF","designation":"RFC 2541","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2541.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2541.txt","https://www.rfc-editor.org/rfc/rfc2541.pdf"],"folder":"IETF/RFC-2541","files":{"txt":{"path":"standards/IETF/RFC-2541/RFC-2541.txt","sha256":"94cbc058217de9781de0c39477adc16b0378cd2d64a738ff344fe43e554f1e59"}},"tags":["nested-reference","unchanged"],"summary":"Secure DNS is based on cryptographic techniques. A necessary part of\n the strength of these techniques is careful attention to the\n operational aspects of key and signature generation, lifetime, size,\n and storage. In addition, special attention must be paid to the\n security of the high level zones, particularly the root zone. This\n document discusses these operational aspects for keys and signatures\n used in connection with the KEY and SIG DNS resource records.\n\nAcknowledgments\n\n The contributions and suggestions of the following persons (in\n alphabetic order) are gratefully acknowledged:\n\n John Gilmore\n Olafur Gudmundsson\n Charlie Kaufman\n\nEastlake Informational [Page 1]\n\f\nRFC 2541 DNS Security Operational Considerations March 1999","scope_keywords":["2541","algorithm","algorithms","authentication","encryption","key","keys","policy","risk","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null}],"search_text":"IETF RFC 2541 Secure DNS is based on cryptographic techniques. A necessary part of\n the strength of these techniques is careful attention to the\n operational aspects of key and signature generation, lifetime, size,\n and storage. In addition, special attention must be paid to the\n security of the high level zones, particularly the root zone. This\n document discusses these operational aspects for keys and signatures\n used in connection with the KEY and SIG DNS resource records.\n\nAcknowledgments\n\n The contributions and suggestions of the following persons (in\n alphabetic order) are gratefully acknowledged:\n\n John Gilmore\n Olafur Gudmundsson\n Charlie Kaufman\n\nEastlake Informational [Page 1]\n\f\nRFC 2541 DNS Security Operational Considerations March 1999 2541 algorithm algorithms authentication encryption key keys policy risk signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 2548","type":"specification","body":"IETF","designation":"RFC 2548","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2548.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2548.txt","https://www.rfc-editor.org/rfc/rfc2548.pdf"],"folder":"IETF/RFC-2548","files":{"txt":{"path":"standards/IETF/RFC-2548/RFC-2548.txt","sha256":"9df5930678f2f166b98fadc0c850d8e977b4dbda9c20989d2a5dd462180724e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the set of Microsoft vendor-specific RADIUS\n attributes. These attributes are designed to support Microsoft\n proprietary dial-up protocols and/or provide support for features\n which is not provided by the standard RADIUS attribute set [3]. It\n is expected that this memo will be updated whenever Microsoft defines\n a new vendor-specific attribute, since its primary purpose is to\n provide an open, easily accessible reference for third-parties\n wishing to interoperate with Microsoft products.\n\n1. Specification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [2].\n\n2. Attributes\n\n The following sections describe sub-attributes which may be\n transmitted in one or more RADIUS attributes of type Vendor-Specific\n [3]. More than one sub-attribute MAY be t","scope_keywords":["2548","algorithm","attribute","attributes","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2548 This document describes the set of Microsoft vendor-specific RADIUS\n attributes. These attributes are designed to support Microsoft\n proprietary dial-up protocols and/or provide support for features\n which is not provided by the standard RADIUS attribute set [3]. It\n is expected that this memo will be updated whenever Microsoft defines\n a new vendor-specific attribute, since its primary purpose is to\n provide an open, easily accessible reference for third-parties\n wishing to interoperate with Microsoft products.\n\n1. Specification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [2].\n\n2. Attributes\n\n The following sections describe sub-attributes which may be\n transmitted in one or more RADIUS attributes of type Vendor-Specific\n [3]. More than one sub-attribute MAY be t 2548 algorithm attribute attributes authentication key nested-reference unchanged"},{"id":"IETF RFC 2606","type":"specification","body":"IETF","designation":"RFC 2606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2606.txt","https://www.rfc-editor.org/rfc/rfc2606.pdf"],"folder":"IETF/RFC-2606","files":{"txt":{"path":"standards/IETF/RFC-2606/RFC-2606.txt","sha256":"b6869c8984701701bc2e6973b6ffc750d497f845cc1a65a106e9301590a13ab0"}},"tags":["nested-reference","unchanged"],"summary":"To reduce the likelihood of conflict and confusion, a few top level\n domain names are reserved for use in private testing, as examples in\n documentation, and the like. In addition, a few second level domain\n names reserved for use as examples are documented.","scope_keywords":["2606"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3092","folder":"IETF/RFC-3092","source":"IETF/RFC-3092/RFC-3092.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3849","folder":"IETF/RFC-3849","source":"IETF/RFC-3849/RFC-3849.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 5233","folder":"IETF/RFC-5233","source":"IETF/RFC-5233/RFC-5233.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5398","folder":"IETF/RFC-5398","source":"IETF/RFC-5398/RFC-5398.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 2606 To reduce the likelihood of conflict and confusion, a few top level\n domain names are reserved for use in private testing, as examples in\n documentation, and the like. In addition, a few second level domain\n names reserved for use as examples are documented. 2606 nested-reference unchanged"},{"id":"IETF RFC 2622","type":"specification","body":"IETF","designation":"RFC 2622","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2622.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2622.txt","https://www.rfc-editor.org/rfc/rfc2622.pdf"],"folder":"IETF/RFC-2622","files":{"txt":{"path":"standards/IETF/RFC-2622/RFC-2622.txt","sha256":"e6c45c490e3a50eed6f68be67dc7c876cabd1b96f0a29a109450adc5e4d2e63c"}},"tags":["nested-reference","unchanged"],"summary":"RPSL allows a network operator to be able to specify routing policies\n at various levels in the Internet hierarchy; for example at the\n Autonomous System (AS) level. At the same time, policies can be\n specified with sufficient detail in RPSL so that low level router\n configurations can be generated from them. RPSL is extensible; new\n routing protocols and new protocol features can be introduced at any\n time.\n\nAlaettinoglu, et al. Standards Track [Page 1]\n\f\nRFC 2622 RPSL June 1999","scope_keywords":["2622","attribute","attributes","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2650","folder":"IETF/RFC-2650","source":"IETF/RFC-2650/RFC-2650.txt","version":null},{"body":"IETF","designation":"RFC 2769","folder":"IETF/RFC-2769","source":"IETF/RFC-2769/RFC-2769.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4012","folder":"IETF/RFC-4012","source":"IETF/RFC-4012/RFC-4012.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null}],"search_text":"IETF RFC 2622 RPSL allows a network operator to be able to specify routing policies\n at various levels in the Internet hierarchy; for example at the\n Autonomous System (AS) level. At the same time, policies can be\n specified with sufficient detail in RPSL so that low level router\n configurations can be generated from them. RPSL is extensible; new\n routing protocols and new protocol features can be introduced at any\n time.\n\nAlaettinoglu, et al. Standards Track [Page 1]\n\f\nRFC 2622 RPSL June 1999 2622 attribute attributes policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 2661","type":"specification","body":"IETF","designation":"RFC 2661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2661.txt","https://www.rfc-editor.org/rfc/rfc2661.pdf"],"folder":"IETF/RFC-2661","files":{"txt":{"path":"standards/IETF/RFC-2661/RFC-2661.txt","sha256":"8cb83177d013fb55045616790b19a490d7ff5d3967b4e1430224ca44c90b4aa5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Layer Two Tunneling Protocol (L2TP). STD\n 51, RFC 1661 specifies multi-protocol access via PPP [RFC1661]. L2TP\n facilitates the tunneling of PPP packets across an intervening\n network in a way that is as transparent as possible to both end-users\n and applications.","scope_keywords":["2661","attribute","attributes","authentication","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2809","folder":"IETF/RFC-2809","source":"IETF/RFC-2809/RFC-2809.txt","version":null},{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3070","folder":"IETF/RFC-3070","source":"IETF/RFC-3070/RFC-3070.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3438","folder":"IETF/RFC-3438","source":"IETF/RFC-3438/RFC-3438.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4667","folder":"IETF/RFC-4667","source":"IETF/RFC-4667/RFC-4667.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2661 This document describes the Layer Two Tunneling Protocol (L2TP). STD\n 51, RFC 1661 specifies multi-protocol access via PPP [RFC1661]. L2TP\n facilitates the tunneling of PPP packets across an intervening\n network in a way that is as transparent as possible to both end-users\n and applications. 2661 attribute attributes authentication delivery management nested-reference unchanged"},{"id":"IETF RFC 2672","type":"specification","body":"IETF","designation":"RFC 2672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2672.txt","https://www.rfc-editor.org/rfc/rfc2672.pdf"],"folder":"IETF/RFC-2672","files":{"txt":{"path":"standards/IETF/RFC-2672/RFC-2672.txt","sha256":"b6a060315f521099d78df77e0f2d2f1412226747e93112a7b35da22422ef8951"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2672 Fermilab\nCategory: Standards Track August 1999\n\n Non-Terminal DNS Name Redirection\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines a new DNS Resource Record called \"DNAME\", which\n provides the capability to map an entire subtree of the DNS name\n space to another domain. It differs from the CNAME record which maps\n a single node of the name space.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"S","scope_keywords":["2672","algorithm","algorithms","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5893","folder":"IETF/RFC-5893","source":"IETF/RFC-5893/RFC-5893.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null}],"search_text":"IETF RFC 2672 Network Working Group M. Crawford\nRequest for Comments: 2672 Fermilab\nCategory: Standards Track August 1999\n\n Non-Terminal DNS Name Redirection\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines a new DNS Resource Record called \"DNAME\", which\n provides the capability to map an entire subtree of the DNS name\n space to another domain. It differs from the CNAME record which maps\n a single node of the name space.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"S 2672 algorithm algorithms key subject nested-reference unchanged"},{"id":"IETF RFC 2694","type":"specification","body":"IETF","designation":"RFC 2694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2694.txt","https://www.rfc-editor.org/rfc/rfc2694.pdf"],"folder":"IETF/RFC-2694","files":{"txt":{"path":"standards/IETF/RFC-2694/RFC-2694.txt","sha256":"bd0dbb9822dd39c7bc2114631a3e8cba64b3c7bc06d728d2d9f4917806463277"}},"tags":["nested-reference","unchanged"],"summary":"Domain Name Service (DNS) provides name to address mapping within a\n routing class (ex: IP). Network Address Translators (NATs) attempt to\n provide transparent routing between hosts in disparate address realms\n of the same routing class. Typically, NATs exist at the border of a\n stub domain, hiding private addresses from external addresses. This\n document identifies the need for DNS extensions to NATs and outlines\n how a DNS Application Level Gateway (DNS_ALG) can meet the need.\n DNS_ALG modifies payload transparently to alter address mapping of\n hosts as DNS packets cross one address realm into another. The\n document also illustrates the operation of DNS_ALG with specific\n examples.\n\n1. Introduction\n\n Network Address Translators (NATs) are often used when network's\n internal IP addresses cannot be used outside the network either for\n privacy reasons or because they are invalid for use o","scope_keywords":["2694"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null}],"search_text":"IETF RFC 2694 Domain Name Service (DNS) provides name to address mapping within a\n routing class (ex: IP). Network Address Translators (NATs) attempt to\n provide transparent routing between hosts in disparate address realms\n of the same routing class. Typically, NATs exist at the border of a\n stub domain, hiding private addresses from external addresses. This\n document identifies the need for DNS extensions to NATs and outlines\n how a DNS Application Level Gateway (DNS_ALG) can meet the need.\n DNS_ALG modifies payload transparently to alter address mapping of\n hosts as DNS packets cross one address realm into another. The\n document also illustrates the operation of DNS_ALG with specific\n examples.\n\n1. Introduction\n\n Network Address Translators (NATs) are often used when network's\n internal IP addresses cannot be used outside the network either for\n privacy reasons or because they are invalid for use o 2694 nested-reference unchanged"},{"id":"IETF RFC 2782","type":"specification","body":"IETF","designation":"RFC 2782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2782.txt","https://www.rfc-editor.org/rfc/rfc2782.pdf"],"folder":"IETF/RFC-2782","files":{"txt":{"path":"standards/IETF/RFC-2782/RFC-2782.txt","sha256":"bacc8972b55f30eb47d7bb07662905ba3a3a7cdefb148174d0d9fbbb313735ac"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Gulbrandsen\nRequest for Comments: 2782 Troll Technologies\nObsoletes: 2052 P. Vixie\nCategory: Standards Track Internet Software Consortium\n L. Esibov\n Microsoft Corp.\n February 2000\n\n A DNS RR for specifying the location of services (DNS SRV)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a DNS RR which specifies the location of the\n server(s) for a specific protocol and domain.\n\nOverview and rationale\n\n Currently, one must either know ","scope_keywords":["2782","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3486","folder":"IETF/RFC-3486","source":"IETF/RFC-3486/RFC-3486.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4321","folder":"IETF/RFC-4321","source":"IETF/RFC-4321/RFC-4321.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 2782 Network Working Group A. Gulbrandsen\nRequest for Comments: 2782 Troll Technologies\nObsoletes: 2052 P. Vixie\nCategory: Standards Track Internet Software Consortium\n L. Esibov\n Microsoft Corp.\n February 2000\n\n A DNS RR for specifying the location of services (DNS SRV)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a DNS RR which specifies the location of the\n server(s) for a specific protocol and domain.\n\nOverview and rationale\n\n Currently, one must either know  2782 algorithm key nested-reference unchanged"},{"id":"IETF RFC 2801","type":"specification","body":"IETF","designation":"RFC 2801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2801.txt","https://www.rfc-editor.org/rfc/rfc2801.pdf"],"folder":"IETF/RFC-2801","files":{"txt":{"path":"standards/IETF/RFC-2801/RFC-2801.txt","sha256":"e02543b2ece75551e409f4a244cc74e25d6284cccad4fada50a0f41b73121234"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Open Trading Protocol (IOTP) provides an interoperable\n framework for Internet commerce. It is payment system independent and\n encapsulates payment systems such as SET, Secure Channel\n Credit/Debit, Mondex, CyberCoin, GeldKarte, etc. IOTP is able to\n handle cases where such merchant roles as the shopping site, the\n Payment Handler, the Delivery Handler of goods or services, and the\n provider of customer support are performed by different parties or by\n one party.","scope_keywords":["2801","attribute","attributes","authentication","delivery","signature","signatures","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2807","folder":"IETF/RFC-2807","source":"IETF/RFC-2807/RFC-2807.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2801 The Internet Open Trading Protocol (IOTP) provides an interoperable\n framework for Internet commerce. It is payment system independent and\n encapsulates payment systems such as SET, Secure Channel\n Credit/Debit, Mondex, CyberCoin, GeldKarte, etc. IOTP is able to\n handle cases where such merchant roles as the shopping site, the\n Payment Handler, the Delivery Handler of goods or services, and the\n provider of customer support are performed by different parties or by\n one party. 2801 attribute attributes authentication delivery signature signatures timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2821","type":"specification","body":"IETF","designation":"RFC 2821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2821.txt","https://www.rfc-editor.org/rfc/rfc2821.pdf"],"folder":"IETF/RFC-2821","files":{"txt":{"path":"standards/IETF/RFC-2821/RFC-2821.txt","sha256":"93d6c12135ef648bc6cc1efd371047070505b1d92e7d6923472b12e8c54850fe"}},"tags":["nested-reference","unchanged"],"summary":"This document is a self-contained specification of the basic protocol\n for the Internet electronic mail transport. It consolidates, updates\n and clarifies, but doesn't add new or change existing functionality\n of the following:\n\n - the original SMTP (Simple Mail Transfer Protocol) specification of\n RFC 821 [30],\n\n - domain name system requirements and implications for mail\n transport from RFC 1035 [22] and RFC 974 [27],\n\n - the clarifications and applicability statements in RFC 1123 [2],\n and\n\n - material drawn from the SMTP Extension mechanisms [19].\n\n It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the\n mail transport materials of RFC 1123). However, RFC 821 specifies\n some features that were not in significant use in the Internet by the\n mid-1990s and (in appendices) some additional transport models.\n Those sections are omitted here in the interest of clarity and\n brevit","scope_keywords":["2821","crl","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4686","folder":"IETF/RFC-4686","source":"IETF/RFC-4686/RFC-4686.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5183","folder":"IETF/RFC-5183","source":"IETF/RFC-5183/RFC-5183.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5672","folder":"IETF/RFC-5672","source":"IETF/RFC-5672/RFC-5672.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 2821 This document is a self-contained specification of the basic protocol\n for the Internet electronic mail transport. It consolidates, updates\n and clarifies, but doesn't add new or change existing functionality\n of the following:\n\n - the original SMTP (Simple Mail Transfer Protocol) specification of\n RFC 821 [30],\n\n - domain name system requirements and implications for mail\n transport from RFC 1035 [22] and RFC 974 [27],\n\n - the clarifications and applicability statements in RFC 1123 [2],\n and\n\n - material drawn from the SMTP Extension mechanisms [19].\n\n It obsoletes RFC 821, RFC 974, and updates RFC 1123 (replaces the\n mail transport materials of RFC 1123). However, RFC 821 specifies\n some features that were not in significant use in the Internet by the\n mid-1990s and (in appendices) some additional transport models.\n Those sections are omitted here in the interest of clarity and\n brevit 2821 crl delivery nested-reference unchanged"},{"id":"IETF RFC 2822","type":"specification","body":"IETF","designation":"RFC 2822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2822.txt","https://www.rfc-editor.org/rfc/rfc2822.pdf"],"folder":"IETF/RFC-2822","files":{"txt":{"path":"standards/IETF/RFC-2822/RFC-2822.txt","sha256":"ef3a43abe126d87e800f1bf8cfff25654df584498105a5384a7ab21febb69637"}},"tags":["nested-reference","unchanged"],"summary":"This standard specifies a syntax for text messages that are sent\n between computer users, within the framework of \"electronic mail\"\n messages. This standard supersedes the one specified in Request For\n Comments (RFC) 822, \"Standard for the Format of ARPA Internet Text\n Messages\", updating it to reflect current practice and incorporating\n incremental changes that were specified in other RFCs.","scope_keywords":["2822","delivery","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3431","folder":"IETF/RFC-3431","source":"IETF/RFC-3431/RFC-3431.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3598","folder":"IETF/RFC-3598","source":"IETF/RFC-3598/RFC-3598.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4155","folder":"IETF/RFC-4155","source":"IETF/RFC-4155/RFC-4155.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4475","folder":"IETF/RFC-4475","source":"IETF/RFC-4475/RFC-4475.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4686","folder":"IETF/RFC-4686","source":"IETF/RFC-4686/RFC-4686.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5016","folder":"IETF/RFC-5016","source":"IETF/RFC-5016/RFC-5016.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5233","folder":"IETF/RFC-5233","source":"IETF/RFC-5233/RFC-5233.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 2822 This standard specifies a syntax for text messages that are sent\n between computer users, within the framework of \"electronic mail\"\n messages. This standard supersedes the one specified in Request For\n Comments (RFC) 822, \"Standard for the Format of ARPA Internet Text\n Messages\", updating it to reflect current practice and incorporating\n incremental changes that were specified in other RFCs. 2822 delivery identification nested-reference unchanged"},{"id":"IETF RFC 2825","type":"specification","body":"IETF","designation":"RFC 2825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2825.txt","https://www.rfc-editor.org/rfc/rfc2825.pdf"],"folder":"IETF/RFC-2825","files":{"txt":{"path":"standards/IETF/RFC-2825/RFC-2825.txt","sha256":"9fa3eabb125261b489e4731dddb7d2979219ef0f3fda474f7648cfa873927090"}},"tags":["nested-reference","unchanged"],"summary":"The goals of the work to \"internationalize\" Internet protocols\n include providing all users of the Internet with the capability of\n using their own language and its standard character set to express\n themselves, write names, and to navigate the network. This impacts\n the domain names visible in e-mail addresses and so many of today's\n URLs used to locate information on the World Wide Web, etc. However,\n domain names are used by Internet protocols that are used across\n national boundaries. These services must interoperate worldwide, or\n we risk isolating components of the network from each other along\n locale boundaries. This type of isolation could impede not only\n communications among people, but opportunities of the areas involved\n to participate effectively in e-commerce, distance learning, and\n other activities at an international scale, thereby retarding\n economic development.\n\n The","scope_keywords":["2825","key","management","path","pki","policy","presentation","qualified","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null}],"search_text":"IETF RFC 2825 The goals of the work to \"internationalize\" Internet protocols\n include providing all users of the Internet with the capability of\n using their own language and its standard character set to express\n themselves, write names, and to navigate the network. This impacts\n the domain names visible in e-mail addresses and so many of today's\n URLs used to locate information on the World Wide Web, etc. However,\n domain names are used by Internet protocols that are used across\n national boundaries. These services must interoperate worldwide, or\n we risk isolating components of the network from each other along\n locale boundaries. This type of isolation could impede not only\n communications among people, but opportunities of the areas involved\n to participate effectively in e-commerce, distance learning, and\n other activities at an international scale, thereby retarding\n economic development.\n\n The 2825 key management path pki policy presentation qualified risk nested-reference unchanged"},{"id":"IETF RFC 2826","type":"specification","body":"IETF","designation":"RFC 2826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2826.txt","https://www.rfc-editor.org/rfc/rfc2826.pdf"],"folder":"IETF/RFC-2826","files":{"txt":{"path":"standards/IETF/RFC-2826/RFC-2826.txt","sha256":"e6f16bd2fd91cf8c44bbd5c669f1029eb4867dd1765e7437e4df18df1c099235"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 2826 May 2000\nCategory: Informational\n\n IAB Technical Comment on the Unique DNS Root\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nSummary\n\n To remain a global network, the Internet requires the existence of a\n globally unique public name space. The DNS name space is a\n hierarchical name space derived from a single, globally unique root.\n This is a technical constraint inherent in the design of the DNS.\n Therefore it is not technically feasible for there to be more than\n one root in the public DNS. That one root must be supported by a set\n of coordinated root servers administered by a unique naming\n auth","scope_keywords":["2826","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 3026","folder":"IETF/RFC-3026","source":"IETF/RFC-3026/RFC-3026.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 2826 Network Working Group Internet Architecture Board\nRequest for Comments: 2826 May 2000\nCategory: Informational\n\n IAB Technical Comment on the Unique DNS Root\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nSummary\n\n To remain a global network, the Internet requires the existence of a\n globally unique public name space. The DNS name space is a\n hierarchical name space derived from a single, globally unique root.\n This is a technical constraint inherent in the design of the DNS.\n Therefore it is not technically feasible for there to be more than\n one root in the public DNS. That one root must be supported by a set\n of coordinated root servers administered by a unique naming\n auth 2826 policy nested-reference unchanged"},{"id":"IETF RFC 2845","type":"specification","body":"IETF","designation":"RFC 2845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2845.txt","https://www.rfc-editor.org/rfc/rfc2845.pdf"],"folder":"IETF/RFC-2845","files":{"txt":{"path":"standards/IETF/RFC-2845/RFC-2845.txt","sha256":"e166eae75d43d6e4d6e2ea9d14788e645239196ebbf125f05614c5217e5f6cf3"}},"tags":["nested-reference","unchanged"],"summary":"This protocol allows for transaction level authentication using\n shared secrets and one way hashing. It can be used to authenticate\n dynamic updates as coming from an approved client, or to authenticate\n responses as coming from an approved recursive name server.\n\n No provision has been made here for distributing the shared secrets;\n it is expected that a network administrator will statically configure\n name servers and clients using some out of band mechanism such as\n sneaker-net until a secure automated mechanism for key distribution\n is available.\n\n1 - Introduction","scope_keywords":["2845","algorithm","algorithms","authentication","hash","hashing","key","keys","management","registered","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5001","folder":"IETF/RFC-5001","source":"IETF/RFC-5001/RFC-5001.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 2845 This protocol allows for transaction level authentication using\n shared secrets and one way hashing. It can be used to authenticate\n dynamic updates as coming from an approved client, or to authenticate\n responses as coming from an approved recursive name server.\n\n No provision has been made here for distributing the shared secrets;\n it is expected that a network administrator will statically configure\n name servers and clients using some out of band mechanism such as\n sneaker-net until a secure automated mechanism for key distribution\n is available.\n\n1 - Introduction 2845 algorithm algorithms authentication hash hashing key keys management registered signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2916","type":"specification","body":"IETF","designation":"RFC 2916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2916.txt","https://www.rfc-editor.org/rfc/rfc2916.pdf"],"folder":"IETF/RFC-2916","files":{"txt":{"path":"standards/IETF/RFC-2916/RFC-2916.txt","sha256":"5bdd2c23c984689236c780d1c001908b04c87472a1fce9732503fcdda27710e8"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the use of the Domain Name System (DNS) for\n storage of E.164 numbers. More specifically, how DNS can be used for\n identifying available services connected to one E.164 number.\n Routing of the actual connection using the service selected using\n these methods is not discussed.\n\n1. Introduction\n\n Through transformation of E.164 numbers into DNS names and the use of\n existing DNS services like delegation through NS records, and use of\n NAPTR [1] records in DNS [2] [3], one can look up what services are\n available for a specific domain name in a decentralized way with\n distributed management of the different levels in the lookup process.","scope_keywords":["2916","algorithm","holder","identification","key","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3026","folder":"IETF/RFC-3026","source":"IETF/RFC-3026/RFC-3026.txt","version":null},{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 2916 This document discusses the use of the Domain Name System (DNS) for\n storage of E.164 numbers. More specifically, how DNS can be used for\n identifying available services connected to one E.164 number.\n Routing of the actual connection using the service selected using\n these methods is not discussed.\n\n1. Introduction\n\n Through transformation of E.164 numbers into DNS names and the use of\n existing DNS services like delegation through NS records, and use of\n NAPTR [1] records in DNS [2] [3], one can look up what services are\n available for a specific domain name in a decentralized way with\n distributed management of the different levels in the lookup process. 2916 algorithm holder identification key management policies nested-reference unchanged"},{"id":"IETF RFC 2929","type":"specification","body":"IETF","designation":"RFC 2929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2929.txt","https://www.rfc-editor.org/rfc/rfc2929.pdf"],"folder":"IETF/RFC-2929","files":{"txt":{"path":"standards/IETF/RFC-2929/RFC-2929.txt","sha256":"b0d186f5a6e7f5a491e6f3e8a4664cd88ac4f485d7fe2c5a25b27623830af318"}},"tags":["nested-reference","unchanged"],"summary":"Internet Assigned Number Authority (IANA) parameter assignment\n considerations are given for the allocation of Domain Name System\n (DNS) classes, Resource Record (RR) types, operation codes, error\n codes, etc.","scope_keywords":["2929","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4431","folder":"IETF/RFC-4431","source":"IETF/RFC-4431/RFC-4431.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null}],"search_text":"IETF RFC 2929 Internet Assigned Number Authority (IANA) parameter assignment\n considerations are given for the allocation of Domain Name System\n (DNS) classes, Resource Record (RR) types, operation codes, error\n codes, etc. 2929 http key nested-reference unchanged"},{"id":"IETF RFC 2930","type":"specification","body":"IETF","designation":"RFC 2930","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2930.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2930.txt","https://www.rfc-editor.org/rfc/rfc2930.pdf"],"folder":"IETF/RFC-2930","files":{"txt":{"path":"standards/IETF/RFC-2930/RFC-2930.txt","sha256":"ec4482df1020336bbe65e40ca3a8cc1d78c38a8f6a785a440bd66d6cfb396e92"}},"tags":["nested-reference","unchanged"],"summary":"[RFC 2845] provides a means of authenticating Domain Name System\n (DNS) queries and responses using shared secret keys via the\n Transaction Signature (TSIG) resource record (RR). However, it\n provides no mechanism for setting up such keys other than manual\n exchange. This document describes a Transaction Key (TKEY) RR that\n can be used in a number of different modes to establish shared secret\n keys between a DNS resolver and server.\n\nAcknowledgments\n\n The comments and ideas of the following persons (listed in alphabetic\n order) have been incorporated herein and are gratefully acknowledged:\n\n Olafur Gudmundsson (TIS)\n\n Stuart Kwan (Microsoft)\n\n Ed Lewis (TIS)\n\n Erik Nordmark (SUN)\n\n Brian Wellington (Nominum)\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2930 The DNS TKEY RR September 2000","scope_keywords":["2930","algorithm","authentication","encryption","key","keys","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3445","folder":"IETF/RFC-3445","source":"IETF/RFC-3445/RFC-3445.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 2930 [RFC 2845] provides a means of authenticating Domain Name System\n (DNS) queries and responses using shared secret keys via the\n Transaction Signature (TSIG) resource record (RR). However, it\n provides no mechanism for setting up such keys other than manual\n exchange. This document describes a Transaction Key (TKEY) RR that\n can be used in a number of different modes to establish shared secret\n keys between a DNS resolver and server.\n\nAcknowledgments\n\n The comments and ideas of the following persons (listed in alphabetic\n order) have been incorporated herein and are gratefully acknowledged:\n\n Olafur Gudmundsson (TIS)\n\n Stuart Kwan (Microsoft)\n\n Ed Lewis (TIS)\n\n Erik Nordmark (SUN)\n\n Brian Wellington (Nominum)\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2930 The DNS TKEY RR September 2000 2930 algorithm authentication encryption key keys signature nested-reference unchanged"},{"id":"IETF RFC 3007","type":"specification","body":"IETF","designation":"RFC 3007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3007.txt","https://www.rfc-editor.org/rfc/rfc3007.pdf"],"folder":"IETF/RFC-3007","files":{"txt":{"path":"standards/IETF/RFC-3007/RFC-3007.txt","sha256":"4cf2f1453d491e6baff028ba2a04d6f77badb80fe81d0ea48230113b5ed4e09c"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method for performing secure Domain Name\n System (DNS) dynamic updates. The method described here is intended\n to be flexible and useful while requiring as few changes to the\n protocol as possible. The authentication of the dynamic update\n message is separate from later DNSSEC validation of the data. Secure\n communication based on authenticated requests and transactions is\n used to provide authorization.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1 - Introduction\n\n This document defines a means to secure dynamic updates of the Domain\n Name System (DNS), allowing only authorized sources to make changes\n to a zone's contents. The existing unsecured dynamic update\n operations form the basis for this wor","scope_keywords":["3007","authentication","authorization","encryption","hash","key","keys","policy","signature","signatures","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3445","folder":"IETF/RFC-3445","source":"IETF/RFC-3445/RFC-3445.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3756","folder":"IETF/RFC-3756","source":"IETF/RFC-3756/RFC-3756.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 3007 This document proposes a method for performing secure Domain Name\n System (DNS) dynamic updates. The method described here is intended\n to be flexible and useful while requiring as few changes to the\n protocol as possible. The authentication of the dynamic update\n message is separate from later DNSSEC validation of the data. Secure\n communication based on authenticated requests and transactions is\n used to provide authorization.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1 - Introduction\n\n This document defines a means to secure dynamic updates of the Domain\n Name System (DNS), allowing only authorized sources to make changes\n to a zone's contents. The existing unsecured dynamic update\n operations form the basis for this wor 3007 authentication authorization encryption hash key keys policy signature signatures validation nested-reference unchanged"},{"id":"IETF RFC 3008","type":"specification","body":"IETF","designation":"RFC 3008","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3008.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3008.txt","https://www.rfc-editor.org/rfc/rfc3008.pdf"],"folder":"IETF/RFC-3008","files":{"txt":{"path":"standards/IETF/RFC-3008/RFC-3008.txt","sha256":"58a6406afc011869dc4e161ac6e2a59a99c8086c882381d9491b3ba6c311085c"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a revised model of Domain Name System Security\n (DNSSEC) Signing Authority. The revised model is designed to clarify\n earlier documents and add additional restrictions to simplify the\n secure resolution process. Specifically, this affects the\n authorization of keys to sign sets of records.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1 - Introduction\n\n This document defines additional restrictions on DNSSEC signatures\n (SIG) records relating to their authority to sign associated data.\n The intent is to establish a standard policy followed by a secure\n resolver; this policy can be augmented by local rules. This builds\n upon [RFC2535], updating section 2.3.6 of that document.\n\n The most significant change ","scope_keywords":["3008","algorithm","algorithms","authentication","authorization","key","keys","policy","signature","signatures","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null}],"search_text":"IETF RFC 3008 This document proposes a revised model of Domain Name System Security\n (DNSSEC) Signing Authority. The revised model is designed to clarify\n earlier documents and add additional restrictions to simplify the\n secure resolution process. Specifically, this affects the\n authorization of keys to sign sets of records.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1 - Introduction\n\n This document defines additional restrictions on DNSSEC signatures\n (SIG) records relating to their authority to sign associated data.\n The intent is to establish a standard policy followed by a secure\n resolver; this policy can be augmented by local rules. This builds\n upon [RFC2535], updating section 2.3.6 of that document.\n\n The most significant change  3008 algorithm algorithms authentication authorization key keys policy signature signatures trust validation nested-reference unchanged"},{"id":"IETF RFC 3027","type":"specification","body":"IETF","designation":"RFC 3027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3027.txt","https://www.rfc-editor.org/rfc/rfc3027.pdf"],"folder":"IETF/RFC-3027","files":{"txt":{"path":"standards/IETF/RFC-3027/RFC-3027.txt","sha256":"cdcccf7b5b2a58649c96c489dacd5b5140876ed69cf3c5b143ada993712657c6"}},"tags":["nested-reference","unchanged"],"summary":"Many internet applications can be adversely affected when end nodes\n are not in the same address realm and seek the assistance of an IP\n Network Address Translator (NAT) enroute to bridge the realms. The\n NAT device alone cannot provide the necessary application/protocol\n transparency in all cases and seeks the assistance of Application\n Level Gateways (ALGs) where possible, to provide transparency. The\n purpose of this document is to identify the protocols and\n applications that break with NAT enroute. The document also attempts\n to identify any known workarounds. It is not possible to capture all\n applications that break with NAT in a single document. This document\n attempts to capture as much information as possible, but is by no\n means a comprehensive coverage. We hope the coverage provides\n sufficient clues for applications not covered.","scope_keywords":["3027","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 3027 Many internet applications can be adversely affected when end nodes\n are not in the same address realm and seek the assistance of an IP\n Network Address Translator (NAT) enroute to bridge the realms. The\n NAT device alone cannot provide the necessary application/protocol\n transparency in all cases and seeks the assistance of Application\n Level Gateways (ALGs) where possible, to provide transparency. The\n purpose of this document is to identify the protocols and\n applications that break with NAT enroute. The document also attempts\n to identify any known workarounds. It is not possible to capture all\n applications that break with NAT in a single document. This document\n attempts to capture as much information as possible, but is by no\n means a comprehensive coverage. We hope the coverage provides\n sufficient clues for applications not covered. 3027 tsp nested-reference unchanged"},{"id":"IETF RFC 3088","type":"specification","body":"IETF","designation":"RFC 3088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3088.txt","https://www.rfc-editor.org/rfc/rfc3088.pdf"],"folder":"IETF/RFC-3088","files":{"txt":{"path":"standards/IETF/RFC-3088/RFC-3088.txt","sha256":"d92e264867e56a61253784e5e71ad8831fedab51b511da4879bc25cbd69528fa"}},"tags":["nested-reference","unchanged"],"summary":"The OpenLDAP Project is operating an experimental LDAP (Lightweight\n Directory Access Protocol) referral service known as the \"OpenLDAP\n Root Service\". The automated system generates referrals based upon\n service location information published in DNS SRV RRs (Domain Name\n System location of services resource records). This document\n describes this service.\n\n1. Background\n\n LDAP [RFC2251] directories use a hierarchical naming scheme inherited\n from X.500 [X500]. Traditionally, X.500 deployments have used a\n geo-political naming scheme (e.g., CN=Jane\n Doe,OU=Engineering,O=Example,ST=CA,C=US). However, registration\n infrastructure and location services in many portions of the naming\n hierarchical are inadequate or nonexistent.\n\n The construction of a global directory requires a robust registration\n infrastructure and location service. Use of Internet domain-based\n naming [RFC2247] (e.g., UI","scope_keywords":["3088","algorithm","attribute","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 3088 The OpenLDAP Project is operating an experimental LDAP (Lightweight\n Directory Access Protocol) referral service known as the \"OpenLDAP\n Root Service\". The automated system generates referrals based upon\n service location information published in DNS SRV RRs (Domain Name\n System location of services resource records). This document\n describes this service.\n\n1. Background\n\n LDAP [RFC2251] directories use a hierarchical naming scheme inherited\n from X.500 [X500]. Traditionally, X.500 deployments have used a\n geo-political naming scheme (e.g., CN=Jane\n Doe,OU=Engineering,O=Example,ST=CA,C=US). However, registration\n infrastructure and location services in many portions of the naming\n hierarchical are inadequate or nonexistent.\n\n The construction of a global directory requires a robust registration\n infrastructure and location service. Use of Internet domain-based\n naming [RFC2247] (e.g., UI 3088 algorithm attribute qualified nested-reference unchanged"},{"id":"IETF RFC 3090","type":"specification","body":"IETF","designation":"RFC 3090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3090.txt","https://www.rfc-editor.org/rfc/rfc3090.pdf"],"folder":"IETF/RFC-3090","files":{"txt":{"path":"standards/IETF/RFC-3090/RFC-3090.txt","sha256":"aa5179048bb9618793aaceae84fa9c197f91bd0b53b76749577ade7d5d29eb06"}},"tags":["nested-reference","unchanged"],"summary":"The definition of a secured zone is presented, clarifying and\n updating sections of RFC 2535. RFC 2535 defines a zone to be secured\n based on a per algorithm basis, e.g., a zone can be secured with RSA\n keys, and not secured with DSA keys. This document changes this to\n define a zone to be secured or not secured regardless of the key\n algorithm used (or not used). To further simplify the determination\n of a zone's status, \"experimentally secure\" status is deprecated.\n\n1 Introduction\n\n Whether a DNS zone is \"secured\" or not is a question asked in at\n least four contexts. A zone administrator asks the question when\n configuring a zone to use DNSSEC. A dynamic update server asks the\n question when an update request arrives, which may require DNSSEC\n processing. A delegating zone asks the question of a child zone when\n the parent enters data indicating the status the child. A resolver\n asks ","scope_keywords":["3090","algorithm","key","keys","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3757","folder":"IETF/RFC-3757","source":"IETF/RFC-3757/RFC-3757.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null}],"search_text":"IETF RFC 3090 The definition of a secured zone is presented, clarifying and\n updating sections of RFC 2535. RFC 2535 defines a zone to be secured\n based on a per algorithm basis, e.g., a zone can be secured with RSA\n keys, and not secured with DSA keys. This document changes this to\n define a zone to be secured or not secured regardless of the key\n algorithm used (or not used). To further simplify the determination\n of a zone's status, \"experimentally secure\" status is deprecated.\n\n1 Introduction\n\n Whether a DNS zone is \"secured\" or not is a question asked in at\n least four contexts. A zone administrator asks the question when\n configuring a zone to use DNSSEC. A dynamic update server asks the\n question when an update request arrives, which may require DNSSEC\n processing. A delegating zone asks the question of a child zone when\n the parent enters data indicating the status the child. A resolver\n asks  3090 algorithm key keys signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 3110","type":"specification","body":"IETF","designation":"RFC 3110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3110.txt","https://www.rfc-editor.org/rfc/rfc3110.pdf"],"folder":"IETF/RFC-3110","files":{"txt":{"path":"standards/IETF/RFC-3110/RFC-3110.txt","sha256":"ccb56821a1d9edc9dc5ae14d8e6c6c18836cde0a8785d3847ba0e43c1c397b21"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to produce RSA/SHA1 SIG resource records\n (RRs) in Section 3 and, so as to completely replace RFC 2537,\n describes how to produce RSA KEY RRs in Section 2.\n\n Since the adoption of a Proposed Standard for RSA signatures in the\n DNS (Domain Name Space), advances in hashing have been made. A new\n DNS signature algorithm is defined to make these advances available\n in SIG RRs. The use of the previously specified weaker mechanism is\n deprecated. The algorithm number of the RSA KEY RR is changed to\n correspond to this new SIG algorithm. No other changes are made to\n DNS security.\n\nAcknowledgements\n\n Material and comments from the following have been incorporated and\n are gratefully acknowledged:\n\n Olafur Gudmundsson\n\n The IESG\n\n Charlie Kaufman\n\n Steve Wang\n\nD. Eastlake 3rd Standards Track [Page 1]\n\f\nRFC 3110 RSA SIGs and KEYs in the DNS May 2001","scope_keywords":["3110","algorithm","algorithms","hash","hashing","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 3110 This document describes how to produce RSA/SHA1 SIG resource records\n (RRs) in Section 3 and, so as to completely replace RFC 2537,\n describes how to produce RSA KEY RRs in Section 2.\n\n Since the adoption of a Proposed Standard for RSA signatures in the\n DNS (Domain Name Space), advances in hashing have been made. A new\n DNS signature algorithm is defined to make these advances available\n in SIG RRs. The use of the previously specified weaker mechanism is\n deprecated. The algorithm number of the RSA KEY RR is changed to\n correspond to this new SIG algorithm. No other changes are made to\n DNS security.\n\nAcknowledgements\n\n Material and comments from the following have been incorporated and\n are gratefully acknowledged:\n\n Olafur Gudmundsson\n\n The IESG\n\n Charlie Kaufman\n\n Steve Wang\n\nD. Eastlake 3rd Standards Track [Page 1]\n\f\nRFC 3110 RSA SIGs and KEYs in the DNS May 2001 3110 algorithm algorithms hash hashing key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 3111","type":"specification","body":"IETF","designation":"RFC 3111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3111.txt","https://www.rfc-editor.org/rfc/rfc3111.pdf"],"folder":"IETF/RFC-3111","files":{"txt":{"path":"standards/IETF/RFC-3111/RFC-3111.txt","sha256":"72769dc5cfc688d944c6409bf3fc8f3d6ffa62c12741a9fc0b2fba3f94768f91"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Service Location Protocol Version 2's\n (SLPv2) use over IPv6 networks. Since this protocol relies on UDP\n and TCP, the changes to support its use over IPv6 are minor.\n\n This document does not describe how to use SLPv1 over IPv6 networks.\n There is at the time of this publication no implementation or\n deployment of SLPv1 over IPv6. It is RECOMMENDED that SLPv2 be used\n in general, and specifically on networks which support IPv6.\n\nGuttman Standards Track [Page 1]\n\f\nRFC 3111 Service Location Protocol Modifications for IPv6 May 2001","scope_keywords":["3111","algorithm","attribute","hash","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null}],"search_text":"IETF RFC 3111 This document defines the Service Location Protocol Version 2's\n (SLPv2) use over IPv6 networks. Since this protocol relies on UDP\n and TCP, the changes to support its use over IPv6 are minor.\n\n This document does not describe how to use SLPv1 over IPv6 networks.\n There is at the time of this publication no implementation or\n deployment of SLPv1 over IPv6. It is RECOMMENDED that SLPv2 be used\n in general, and specifically on networks which support IPv6.\n\nGuttman Standards Track [Page 1]\n\f\nRFC 3111 Service Location Protocol Modifications for IPv6 May 2001 3111 algorithm attribute hash key path presentation nested-reference unchanged"},{"id":"IETF RFC 3164","type":"specification","body":"IETF","designation":"RFC 3164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3164.txt","https://www.rfc-editor.org/rfc/rfc3164.pdf"],"folder":"IETF/RFC-3164","files":{"txt":{"path":"standards/IETF/RFC-3164/RFC-3164.txt","sha256":"cbb277a5ceb723d07a4791f3b4fd892424516c76945eb17a7431ac4d024977b2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the observed behavior of the syslog protocol.\n This protocol has been used for the transmission of event\n notification messages across networks for many years. While this\n protocol was originally developed on the University of California\n Berkeley Software Distribution (BSD) TCP/IP system implementations,\n its value to operations and management has led it to be ported to\n many other operating systems as well as being embedded into many\n other networked devices.","scope_keywords":["3164","authentication","delivery","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3164 This document describes the observed behavior of the syslog protocol.\n This protocol has been used for the transmission of event\n notification messages across networks for many years. While this\n protocol was originally developed on the University of California\n Berkeley Software Distribution (BSD) TCP/IP system implementations,\n its value to operations and management has led it to be ported to\n many other operating systems as well as being embedded into many\n other networked devices. 3164 authentication delivery management timestamp nested-reference unchanged"},{"id":"IETF RFC 3172","type":"specification","body":"IETF","designation":"RFC 3172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3172.txt","https://www.rfc-editor.org/rfc/rfc3172.pdf"],"folder":"IETF/RFC-3172","files":{"txt":{"path":"standards/IETF/RFC-3172/RFC-3172.txt","sha256":"28b99f06460065f623adffb6bfd42e712eefb9e5ace7dcac9296fea208156405"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the management and operational requirements for\n the address and routing parameter area (\"arpa\") domain. The \"arpa\"\n domain is used to support a class of infrastructural identifier\n spaces, providing a distributed database that translates elements of\n a structured name space derived from a protocol family to service\n names. The efficient and reliable operation of this DNS space is\n essential to the integrity of operation of various services within\n the Internet. The Internet Architecture Board (IAB) has the\n responsibility, in cooperation with the Internet Corporation for\n Assigned Names and Numbers (ICANN), to manage the \"arpa\" domain.\n This document describes the principles used by the IAB in undertaking\n this role.\n\n1. Introduction\n\n The Domain Name System (DNS) [1] [2] is predominately used to\n translate a structured textual identifier into a protocol-specific\n va","scope_keywords":["3172","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 3172 This memo describes the management and operational requirements for\n the address and routing parameter area (\"arpa\") domain. The \"arpa\"\n domain is used to support a class of infrastructural identifier\n spaces, providing a distributed database that translates elements of\n a structured name space derived from a protocol family to service\n names. The efficient and reliable operation of this DNS space is\n essential to the integrity of operation of various services within\n the Internet. The Internet Architecture Board (IAB) has the\n responsibility, in cooperation with the Internet Corporation for\n Assigned Names and Numbers (ICANN), to manage the \"arpa\" domain.\n This document describes the principles used by the IAB in undertaking\n this role.\n\n1. Introduction\n\n The Domain Name System (DNS) [1] [2] is predominately used to\n translate a structured textual identifier into a protocol-specific\n va 3172 key keys management nested-reference unchanged"},{"id":"IETF RFC 3225","type":"specification","body":"IETF","designation":"RFC 3225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3225.txt","https://www.rfc-editor.org/rfc/rfc3225.pdf"],"folder":"IETF/RFC-3225","files":{"txt":{"path":"standards/IETF/RFC-3225/RFC-3225.txt","sha256":"76c063eb542ebb68070e94a3c5cb70bf942c313463478b072b7cb91e025c1515"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Conrad\nRequest for Comments: 3225 Nominum, Inc.\nCategory: Standards Track December 2001\n\n Indicating Resolver Support of DNSSEC\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n In order to deploy DNSSEC (Domain Name System Security Extensions)\n operationally, DNSSEC aware servers should only perform automatic\n inclusion of DNSSEC RRs when there is an explicit indication that the\n resolver can understand those RRs. This document proposes the use of\n a bit in the","scope_keywords":["3225","authentication","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 3225 Network Working Group D. Conrad\nRequest for Comments: 3225 Nominum, Inc.\nCategory: Standards Track December 2001\n\n Indicating Resolver Support of DNSSEC\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n In order to deploy DNSSEC (Domain Name System Security Extensions)\n operationally, DNSSEC aware servers should only perform automatic\n inclusion of DNSSEC RRs when there is an explicit indication that the\n resolver can understand those RRs. This document proposes the use of\n a bit in the 3225 authentication key signature signatures nested-reference unchanged"},{"id":"IETF RFC 3226","type":"specification","body":"IETF","designation":"RFC 3226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3226.txt","https://www.rfc-editor.org/rfc/rfc3226.pdf"],"folder":"IETF/RFC-3226","files":{"txt":{"path":"standards/IETF/RFC-3226/RFC-3226.txt","sha256":"8798d837a4827b3bda88c7d26920e46df40ac373c4811db0a0ea3cb2bcb2806c"}},"tags":["nested-reference","unchanged"],"summary":"This document mandates support for EDNS0 (Extension Mechanisms for\n DNS) in DNS entities claiming to support either DNS Security\n Extensions or A6 records. This requirement is necessary because\n these new features increase the size of DNS messages. If EDNS0 is\n not supported fall back to TCP will happen, having a detrimental\n impact on query latency and DNS server load. This document updates\n RFC 2535 and RFC 2874, by adding new requirements.\n\n1. Introduction\n\n Familiarity with the DNS [RFC1034, RFC1035], DNS Security Extensions\n [RFC2535], EDNS0 [RFC2671] and A6 [RFC2874] is helpful.\n\n STD 13, RFC 1035 Section 2.3.4 requires that DNS messages over UDP\n have a data payload of 512 octets or less. Most DNS software today\n will not accept larger UDP datagrams. Any answer that requires more\n than 512 octets, results in a partial and sometimes useless reply\n with the Truncation Bit set; in mo","scope_keywords":["3226","authentication","delivery","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null}],"search_text":"IETF RFC 3226 This document mandates support for EDNS0 (Extension Mechanisms for\n DNS) in DNS entities claiming to support either DNS Security\n Extensions or A6 records. This requirement is necessary because\n these new features increase the size of DNS messages. If EDNS0 is\n not supported fall back to TCP will happen, having a detrimental\n impact on query latency and DNS server load. This document updates\n RFC 2535 and RFC 2874, by adding new requirements.\n\n1. Introduction\n\n Familiarity with the DNS [RFC1034, RFC1035], DNS Security Extensions\n [RFC2535], EDNS0 [RFC2671] and A6 [RFC2874] is helpful.\n\n STD 13, RFC 1035 Section 2.3.4 requires that DNS messages over UDP\n have a data payload of 512 octets or less. Most DNS software today\n will not accept larger UDP datagrams. Any answer that requires more\n than 512 octets, results in a partial and sometimes useless reply\n with the Truncation Bit set; in mo 3226 authentication delivery key signature signatures nested-reference unchanged"},{"id":"IETF RFC 3279","type":"specification","body":"IETF","designation":"RFC 3279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3279.txt","https://www.rfc-editor.org/rfc/rfc3279.pdf"],"folder":"IETF/RFC-3279","files":{"txt":{"path":"standards/IETF/RFC-3279/RFC-3279.txt","sha256":"6d3f19f18e17fa1c68da5aaf4021327748fabca840d7300443b77357a1fc1614"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies algorithm identifiers and ASN.1 encoding\n formats for digital signatures and subject public keys used in the\n Internet X.509 Public Key Infrastructure (PKI). Digital signatures\n are used to sign certificates and certificate revocation list (CRLs).\n Certificates include the public key of the named subject.","scope_keywords":["3279","algorithm","algorithms","certificate","certificates","crl","encryption","hash","key","keys","license","pki","profile","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4050","folder":"IETF/RFC-4050","source":"IETF/RFC-4050/RFC-4050.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 3279 This document specifies algorithm identifiers and ASN.1 encoding\n formats for digital signatures and subject public keys used in the\n Internet X.509 Public Key Infrastructure (PKI). Digital signatures\n are used to sign certificates and certificate revocation list (CRLs).\n Certificates include the public key of the named subject. 3279 algorithm algorithms certificate certificates crl encryption hash key keys license pki profile revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 3280","type":"specification","body":"IETF","designation":"RFC 3280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3280.txt","https://www.rfc-editor.org/rfc/rfc3280.pdf"],"folder":"IETF/RFC-3280","files":{"txt":{"path":"standards/IETF/RFC-3280/RFC-3280.txt","sha256":"65a813a366fb71ab237d960af11b50801fbca690ec57c6624d3217f4612823df"}},"tags":["nested-reference","unchanged"],"summary":"This memo profiles the X.509 v3 certificate and X.509 v2 Certificate\n Revocation List (CRL) for use in the Internet. An overview of this\n approach and model are provided as an introduction. The X.509 v3\n certificate format is described in detail, with additional\n information regarding the format and semantics of Internet name\n forms. Standard certificate extensions are described and two\n Internet-specific extensions are defined. A set of required\n certificate extensions is specified. The X.509 v2 CRL format is\n described in detail, and required extensions are defined. An\n algorithm for X.509 certification path validation is described. An\n ASN.1 module and examples are provided in the appendices.","scope_keywords":["3280","algorithm","attribute","attributes","certificate","certificates","crl","issuer","key","management","path","policies","policy","profile","profiles","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4134","folder":"IETF/RFC-4134","source":"IETF/RFC-4134/RFC-4134.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4262","folder":"IETF/RFC-4262","source":"IETF/RFC-4262/RFC-4262.txt","version":null},{"body":"IETF","designation":"RFC 4270","folder":"IETF/RFC-4270","source":"IETF/RFC-4270/RFC-4270.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4534","folder":"IETF/RFC-4534","source":"IETF/RFC-4534/RFC-4534.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4630","folder":"IETF/RFC-4630","source":"IETF/RFC-4630/RFC-4630.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4806","folder":"IETF/RFC-4806","source":"IETF/RFC-4806/RFC-4806.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4810","folder":"IETF/RFC-4810","source":"IETF/RFC-4810/RFC-4810.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 3280 This memo profiles the X.509 v3 certificate and X.509 v2 Certificate\n Revocation List (CRL) for use in the Internet. An overview of this\n approach and model are provided as an introduction. The X.509 v3\n certificate format is described in detail, with additional\n information regarding the format and semantics of Internet name\n forms. Standard certificate extensions are described and two\n Internet-specific extensions are defined. A set of required\n certificate extensions is specified. The X.509 v2 CRL format is\n described in detail, and required extensions are defined. An\n algorithm for X.509 certification path validation is described. An\n ASN.1 module and examples are provided in the appendices. 3280 algorithm attribute attributes certificate certificates crl issuer key management path policies policy profile profiles revocation nested-reference unchanged"},{"id":"IETF RFC 3316","type":"specification","body":"IETF","designation":"RFC 3316","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3316.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3316.txt","https://www.rfc-editor.org/rfc/rfc3316.pdf"],"folder":"IETF/RFC-3316","files":{"txt":{"path":"standards/IETF/RFC-3316/RFC-3316.txt","sha256":"f5c2b1e0a1e7b714b1cee67b7bd86fe7011d86f15fa8935f33eaadbd288664f1"}},"tags":["nested-reference","unchanged"],"summary":"As the deployment of second and third generation cellular networks\n progresses, a large number of cellular hosts are being connected to\n the Internet. Standardization organizations are making Internet\n Protocol version 6 (IPv6) mandatory in their specifications.\n However, the concept of IPv6 covers many aspects and numerous\n specifications. In addition, the characteristics of cellular links\n in terms of bandwidth, cost and delay put special requirements on how\n IPv6 is used. This document considers IPv6 for cellular hosts that\n attach to the General Packet Radio Service (GPRS), or Universal\n Mobile Telecommunications System (UMTS) networks. This document also\n lists basic components of IPv6 functionality and discusses some\n issues relating to the use of these components when operating in\n these networks.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 3316 IPv6 for Some 2G and 3G Cellular Ho","scope_keywords":["3316","algorithm","algorithms","authentication","encryption","hash","hashing","key","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3316 As the deployment of second and third generation cellular networks\n progresses, a large number of cellular hosts are being connected to\n the Internet. Standardization organizations are making Internet\n Protocol version 6 (IPv6) mandatory in their specifications.\n However, the concept of IPv6 covers many aspects and numerous\n specifications. In addition, the characteristics of cellular links\n in terms of bandwidth, cost and delay put special requirements on how\n IPv6 is used. This document considers IPv6 for cellular hosts that\n attach to the General Packet Radio Service (GPRS), or Universal\n Mobile Telecommunications System (UMTS) networks. This document also\n lists basic components of IPv6 functionality and discusses some\n issues relating to the use of these components when operating in\n these networks.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 3316 IPv6 for Some 2G and 3G Cellular Ho 3316 algorithm algorithms authentication encryption hash hashing key management path pid nested-reference unchanged"},{"id":"IETF RFC 3364","type":"specification","body":"IETF","designation":"RFC 3364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3364.txt","https://www.rfc-editor.org/rfc/rfc3364.pdf"],"folder":"IETF/RFC-3364","files":{"txt":{"path":"standards/IETF/RFC-3364/RFC-3364.txt","sha256":"0d5b6a88607c59ffcf2cb0700124a406552f66b2808f96a31d44c2f8092b729b"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has two different proposals on the table for how to do DNS\n support for IPv6, and has thus far failed to reach a clear consensus\n on which approach is better. This note attempts to examine the pros\n and cons of each approach, in the hope of clarifying the debate so\n that we can reach closure and move on.","scope_keywords":["3364","pid","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null}],"search_text":"IETF RFC 3364 The IETF has two different proposals on the table for how to do DNS\n support for IPv6, and has thus far failed to reach a clear consensus\n on which approach is better. This note attempts to examine the pros\n and cons of each approach, in the hope of clarifying the debate so\n that we can reach closure and move on. 3364 pid presentation subject nested-reference unchanged"},{"id":"IETF RFC 3435","type":"specification","body":"IETF","designation":"RFC 3435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3435.txt","https://www.rfc-editor.org/rfc/rfc3435.pdf"],"folder":"IETF/RFC-3435","files":{"txt":{"path":"standards/IETF/RFC-3435/RFC-3435.txt","sha256":"8a72f12bf389e4817ba0eaee2c88e3ab4a17681deb0453b9f7e935689731a62f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application programming interface and a\n corresponding protocol (MGCP) which is used between elements of a\n decomposed multimedia gateway. The decomposed multimedia gateway\n consists of a Call Agent, which contains the call control\n \"intelligence\", and a media gateway which contains the media\n functions, e.g., conversion from TDM voice to Voice over IP.\n\n Media gateways contain endpoints on which the Call Agent can create,\n modify and delete connections in order to establish and control media\n sessions with other multimedia endpoints. Also, the Call Agent can\n instruct the endpoints to detect certain events and generate signals.\n The endpoints automatically communicate changes in service state to\n the Call Agent. Furthermore, the Call Agent can audit endpoints as\n well as the connections on endpoints.\n\nAndreasen & Foster Informational [Page 1]\n\f\nRFC 3435 MGCP 1","scope_keywords":["3435","audit"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null}],"search_text":"IETF RFC 3435 This document describes an application programming interface and a\n corresponding protocol (MGCP) which is used between elements of a\n decomposed multimedia gateway. The decomposed multimedia gateway\n consists of a Call Agent, which contains the call control\n \"intelligence\", and a media gateway which contains the media\n functions, e.g., conversion from TDM voice to Voice over IP.\n\n Media gateways contain endpoints on which the Call Agent can create,\n modify and delete connections in order to establish and control media\n sessions with other multimedia endpoints. Also, the Call Agent can\n instruct the endpoints to detect certain events and generate signals.\n The endpoints automatically communicate changes in service state to\n the Call Agent. Furthermore, the Call Agent can audit endpoints as\n well as the connections on endpoints.\n\nAndreasen & Foster Informational [Page 1]\n\f\nRFC 3435 MGCP 1 3435 audit nested-reference unchanged"},{"id":"IETF RFC 3467","type":"specification","body":"IETF","designation":"RFC 3467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3467.txt","https://www.rfc-editor.org/rfc/rfc3467.pdf"],"folder":"IETF/RFC-3467","files":{"txt":{"path":"standards/IETF/RFC-3467/RFC-3467.txt","sha256":"3debfbdd3c3b930e0b895d9e56aee04c5bd30bea780155b5fa2536d59410564f"}},"tags":["nested-reference","unchanged"],"summary":"This document reviews the original function and purpose of the domain\n name system (DNS). It contrasts that history with some of the\n purposes for which the DNS has recently been applied and some of the\n newer demands being placed upon it or suggested for it. A framework\n for an alternative to placing these additional stresses on the DNS is\n then outlined. This document and that framework are not a proposed\n solution, only a strong suggestion that the time has come to begin\n thinking more broadly about the problems we are encountering and\n possible approaches to solving them.","scope_keywords":["3467","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null}],"search_text":"IETF RFC 3467 This document reviews the original function and purpose of the domain\n name system (DNS). It contrasts that history with some of the\n purposes for which the DNS has recently been applied and some of the\n newer demands being placed upon it or suggested for it. A framework\n for an alternative to placing these additional stresses on the DNS is\n then outlined. This document and that framework are not a proposed\n solution, only a strong suggestion that the time has come to begin\n thinking more broadly about the problems we are encountering and\n possible approaches to solving them. 3467 key nested-reference unchanged"},{"id":"IETF RFC 3490","type":"specification","body":"IETF","designation":"RFC 3490","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3490.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3490.txt","https://www.rfc-editor.org/rfc/rfc3490.pdf"],"folder":"IETF/RFC-3490","files":{"txt":{"path":"standards/IETF/RFC-3490/RFC-3490.txt","sha256":"100dd622f39a205d3353cd2db5eaea570064890cebaf495ddb19ba9135ff0020"}},"tags":["nested-reference","unchanged"],"summary":"Until now, there has been no standard method for domain names to use\n characters outside the ASCII repertoire. This document defines\n internationalized domain names (IDNs) and a mechanism called\n Internationalizing Domain Names in Applications (IDNA) for handling\n them in a standard fashion. IDNs use characters drawn from a large\n repertoire (Unicode), but IDNA allows the non-ASCII characters to be\n represented using only the ASCII characters already allowed in so-\n called host names today. This backward-compatible representation is\n required in existing protocols like DNS, so that IDNs can be\n introduced with no changes to the existing infrastructure. IDNA is\n only meant for processing domain names, not free text.","scope_keywords":["3490","authentication","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3492","folder":"IETF/RFC-3492","source":"IETF/RFC-3492/RFC-3492.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5301","folder":"IETF/RFC-5301","source":"IETF/RFC-5301/RFC-5301.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5672","folder":"IETF/RFC-5672","source":"IETF/RFC-5672/RFC-5672.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null}],"search_text":"IETF RFC 3490 Until now, there has been no standard method for domain names to use\n characters outside the ASCII repertoire. This document defines\n internationalized domain names (IDNs) and a mechanism called\n Internationalizing Domain Names in Applications (IDNA) for handling\n them in a standard fashion. IDNs use characters drawn from a large\n repertoire (Unicode), but IDNA allows the non-ASCII characters to be\n represented using only the ASCII characters already allowed in so-\n called host names today. This backward-compatible representation is\n required in existing protocols like DNS, so that IDNs can be\n introduced with no changes to the existing infrastructure. IDNA is\n only meant for processing domain names, not free text. 3490 authentication presentation nested-reference unchanged"},{"id":"IETF RFC 3491","type":"specification","body":"IETF","designation":"RFC 3491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3491.txt","https://www.rfc-editor.org/rfc/rfc3491.pdf"],"folder":"IETF/RFC-3491","files":{"txt":{"path":"standards/IETF/RFC-3491/RFC-3491.txt","sha256":"bda49563e2d51a8453fa8d408c31f37a5ffebfb028cb377a7f976599d91e9abd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to prepare internationalized domain name\n (IDN) labels in order to increase the likelihood that name input and\n name comparison work in ways that make sense for typical users\n throughout the world. This profile of the stringprep protocol is\n used as part of a suite of on-the-wire protocols for\n internationalizing the Domain Name System (DNS).\n\n1. Introduction\n\n This document specifies processing rules that will allow users to\n enter internationalized domain names (IDNs) into applications and\n have the highest chance of getting the content of the strings\n correct. It is a profile of stringprep [STRINGPREP]. These\n processing rules are only intended for internationalized domain\n names, not for arbitrary text.\n\n This profile defines the following, as required by [STRINGPREP].\n\n - The intended applicability of the profile: internationalized\n domain names processed","scope_keywords":["3491","key","profile","profiles","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3492","folder":"IETF/RFC-3492","source":"IETF/RFC-3492/RFC-3492.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 3491 This document describes how to prepare internationalized domain name\n (IDN) labels in order to increase the likelihood that name input and\n name comparison work in ways that make sense for typical users\n throughout the world. This profile of the stringprep protocol is\n used as part of a suite of on-the-wire protocols for\n internationalizing the Domain Name System (DNS).\n\n1. Introduction\n\n This document specifies processing rules that will allow users to\n enter internationalized domain names (IDNs) into applications and\n have the highest chance of getting the content of the strings\n correct. It is a profile of stringprep [STRINGPREP]. These\n processing rules are only intended for internationalized domain\n names, not for arbitrary text.\n\n This profile defines the following, as required by [STRINGPREP].\n\n - The intended applicability of the profile: internationalized\n domain names processed 3491 key profile profiles registered trust nested-reference unchanged"},{"id":"IETF RFC 3492","type":"specification","body":"IETF","designation":"RFC 3492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3492.txt","https://www.rfc-editor.org/rfc/rfc3492.pdf"],"folder":"IETF/RFC-3492","files":{"txt":{"path":"standards/IETF/RFC-3492/RFC-3492.txt","sha256":"d1848b1b4f01e20708a64f42394e5f4b840141935bed7f09ad7baeb6693b8772"}},"tags":["nested-reference","unchanged"],"summary":"Punycode is a simple and efficient transfer encoding syntax designed\n for use with Internationalized Domain Names in Applications (IDNA).\n It uniquely and reversibly transforms a Unicode string into an ASCII\n string. ASCII characters in the Unicode string are represented\n literally, and non-ASCII characters are represented by ASCII\n characters that are allowed in host name labels (letters, digits, and\n hyphens). This document defines a general algorithm called\n Bootstring that allows a string of basic code points to uniquely\n represent any string of code points drawn from a larger set.\n Punycode is an instance of Bootstring that uses particular parameter\n values specified by this document, appropriate for IDNA.","scope_keywords":["3492","algorithm","algorithms","key","license","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null}],"search_text":"IETF RFC 3492 Punycode is a simple and efficient transfer encoding syntax designed\n for use with Internationalized Domain Names in Applications (IDNA).\n It uniquely and reversibly transforms a Unicode string into an ASCII\n string. ASCII characters in the Unicode string are represented\n literally, and non-ASCII characters are represented by ASCII\n characters that are allowed in host name labels (letters, digits, and\n hyphens). This document defines a general algorithm called\n Bootstring that allows a string of basic code points to uniquely\n represent any string of code points drawn from a larger set.\n Punycode is an instance of Bootstring that uses particular parameter\n values specified by this document, appropriate for IDNA. 3492 algorithm algorithms key license presentation nested-reference unchanged"},{"id":"IETF RFC 3520","type":"specification","body":"IETF","designation":"RFC 3520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3520.txt","https://www.rfc-editor.org/rfc/rfc3520.pdf"],"folder":"IETF/RFC-3520","files":{"txt":{"path":"standards/IETF/RFC-3520/RFC-3520.txt","sha256":"0254ad37e79b5b5cf7a867cc53c320e8ef0aca3985b0260c57ae88ed7e680548"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the representation of a session authorization\n policy element for supporting policy-based per-session authorization\n and admission control. The goal of session authorization is to allow\n the exchange of information between network elements in order to\n authorize the use of resources for a service and to co-ordinate\n actions between the signaling and transport planes. This document\n describes how a process on a system authorizes the reservation of\n resources by a host and then provides that host with a session\n authorization policy element which can be inserted into a resource\n reservation protocol (e.g., the Resource ReSerVation Protocol (RSVP)\n PATH message) to facilitate proper and secure reservation of those\n resources within the network. We describe the encoding of session\n authorization information as a policy element conforming to the\n format of a Policy Dat","scope_keywords":["3520","attribute","attributes","authentication","authorization","certificate","certificates","key","keys","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null}],"search_text":"IETF RFC 3520 This document describes the representation of a session authorization\n policy element for supporting policy-based per-session authorization\n and admission control. The goal of session authorization is to allow\n the exchange of information between network elements in order to\n authorize the use of resources for a service and to co-ordinate\n actions between the signaling and transport planes. This document\n describes how a process on a system authorizes the reservation of\n resources by a host and then provides that host with a session\n authorization policy element which can be inserted into a resource\n reservation protocol (e.g., the Resource ReSerVation Protocol (RSVP)\n PATH message) to facilitate proper and secure reservation of those\n resources within the network. We describe the encoding of session\n authorization information as a policy element conforming to the\n format of a Policy Dat 3520 attribute attributes authentication authorization certificate certificates key keys path policy presentation nested-reference unchanged"},{"id":"IETF RFC 3550","type":"specification","body":"IETF","designation":"RFC 3550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3550.txt","https://www.rfc-editor.org/rfc/rfc3550.pdf"],"folder":"IETF/RFC-3550","files":{"pdf":{"path":"standards/IETF/RFC-3550/RFC-3550.pdf","sha256":"dd7c578c13257d1a01d73596fb350b65eb9c3eeb0fa215e9064f80cf12c819aa"},"txt":{"path":"standards/IETF/RFC-3550/RFC-3550.txt","sha256":"4c210e9434b5b4c029e8536ad8991f3709bc3cbfa0999e951bcb4c2143c539e8"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum describes RTP, the real-time transport protocol. RTP\n provides end-to-end network transport functions suitable for\n applications transmitting real-time data, such as audio, video or\n simulation data, over multicast or unicast network services. RTP\n does not address resource reservation and does not guarantee\n quality-of-service for real-time services. The data transport is\n augmented by a control protocol (RTCP) to allow monitoring of the\n data delivery in a manner scalable to large multicast networks, and\n to provide minimal control and identification functionality. RTP and\n RTCP are designed to be independent of the underlying transport and\n network layers. The protocol supports the use of RTP-level\n translators and mixers.\n\n Most of the text in this memorandum is identical to RFC 1889 which it\n obsoletes. There are no changes in the packet formats on the wire,\n only ch","scope_keywords":["3550","algorithm","algorithms","authentication","delivery","identification","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3556","folder":"IETF/RFC-3556","source":"IETF/RFC-3556/RFC-3556.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5450","folder":"IETF/RFC-5450","source":"IETF/RFC-5450/RFC-5450.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5457","folder":"IETF/RFC-5457","source":"IETF/RFC-5457/RFC-5457.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6188","folder":"IETF/RFC-6188","source":"IETF/RFC-6188/RFC-6188.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6562","folder":"IETF/RFC-6562","source":"IETF/RFC-6562/RFC-6562.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7164","folder":"IETF/RFC-7164","source":"IETF/RFC-7164/RFC-7164.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3550 This memorandum describes RTP, the real-time transport protocol. RTP\n provides end-to-end network transport functions suitable for\n applications transmitting real-time data, such as audio, video or\n simulation data, over multicast or unicast network services. RTP\n does not address resource reservation and does not guarantee\n quality-of-service for real-time services. The data transport is\n augmented by a control protocol (RTCP) to allow monitoring of the\n data delivery in a manner scalable to large multicast networks, and\n to provide minimal control and identification functionality. RTP and\n RTCP are designed to be independent of the underlying transport and\n network layers. The protocol supports the use of RTP-level\n translators and mixers.\n\n Most of the text in this memorandum is identical to RFC 1889 which it\n obsoletes. There are no changes in the packet formats on the wire,\n only ch 3550 algorithm algorithms authentication delivery identification profile profiles nested-reference unchanged"},{"id":"IETF RFC 3568","type":"specification","body":"IETF","designation":"RFC 3568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3568.txt","https://www.rfc-editor.org/rfc/rfc3568.pdf"],"folder":"IETF/RFC-3568","files":{"txt":{"path":"standards/IETF/RFC-3568/RFC-3568.txt","sha256":"fae87c766af7c14dba768bc65e4fe872ede6674cd2b2309ac7f2203c1ded8e4c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a summary of Request-Routing techniques that\n are used to direct client requests to surrogates based on various\n policies and a possible set of metrics. The document covers\n techniques that were commonly used in the industry on or before\n December 2000. In this memo, the term Request-Routing represents\n techniques that is commonly called content routing or content\n redirection. In principle, Request-Routing techniques can be\n classified under: DNS Request-Routing, Transport-layer\n Request-Routing, and Application-layer Request-Routing.","scope_keywords":["3568","delivery","http","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3568 This document presents a summary of Request-Routing techniques that\n are used to direct client requests to surrogates based on various\n policies and a possible set of metrics. The document covers\n techniques that were commonly used in the industry on or before\n December 2000. In this memo, the term Request-Routing represents\n techniques that is commonly called content routing or content\n redirection. In principle, Request-Routing techniques can be\n classified under: DNS Request-Routing, Transport-layer\n Request-Routing, and Application-layer Request-Routing. 3568 delivery http policies nested-reference unchanged"},{"id":"IETF RFC 3596","type":"specification","body":"IETF","designation":"RFC 3596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3596.txt","https://www.rfc-editor.org/rfc/rfc3596.pdf"],"folder":"IETF/RFC-3596","files":{"txt":{"path":"standards/IETF/RFC-3596/RFC-3596.txt","sha256":"2a3d44744086f66a7ba00e7d282dc1f740a3e0b63b4b6f7c763ffc0e61ee1dbb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the changes that need to be made to the Domain\n Name System (DNS) to support hosts running IP version 6 (IPv6). The\n changes include a resource record type to store an IPv6 address, a\n domain to support lookups based on an IPv6 address, and updated\n definitions of existing query types that return Internet addresses as\n part of additional section processing. The extensions are designed\n to be compatible with existing applications and, in particular, DNS\n implementations themselves.","scope_keywords":["3596","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4159","folder":"IETF/RFC-4159","source":"IETF/RFC-4159/RFC-4159.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5158","folder":"IETF/RFC-5158","source":"IETF/RFC-5158/RFC-5158.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null}],"search_text":"IETF RFC 3596 This document defines the changes that need to be made to the Domain\n Name System (DNS) to support hosts running IP version 6 (IPv6). The\n changes include a resource record type to store an IPv6 address, a\n domain to support lookups based on an IPv6 address, and updated\n definitions of existing query types that return Internet addresses as\n part of additional section processing. The extensions are designed\n to be compatible with existing applications and, in particular, DNS\n implementations themselves. 3596 presentation nested-reference unchanged"},{"id":"IETF RFC 3597","type":"specification","body":"IETF","designation":"RFC 3597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3597.txt","https://www.rfc-editor.org/rfc/rfc3597.pdf"],"folder":"IETF/RFC-3597","files":{"txt":{"path":"standards/IETF/RFC-3597/RFC-3597.txt","sha256":"a42d9e3193efabbf4e20507c0fdc40414f0c071b6e616b5469c38bb52ba08017"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Gustafsson\nRequest for Comments: 3597 Nominum Inc.\nCategory: Standards Track September 2003\n\n Handling of Unknown DNS Resource Record (RR) Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n Extending the Domain Name System (DNS) with new Resource Record (RR)\n types currently requires changes to name server software. This\n document specifies the changes necessary to allow future DNS\n implementations to handle new RR types transparently.\n\n1. Introduction\n\n Th","scope_keywords":["3597","hash","key","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 3597 Network Working Group A. Gustafsson\nRequest for Comments: 3597 Nominum Inc.\nCategory: Standards Track September 2003\n\n Handling of Unknown DNS Resource Record (RR) Types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n Extending the Domain Name System (DNS) with new Resource Record (RR)\n types currently requires changes to name server software. This\n document specifies the changes necessary to allow future DNS\n implementations to handle new RR types transparently.\n\n1. Introduction\n\n Th 3597 hash key presentation subject nested-reference unchanged"},{"id":"IETF RFC 3645","type":"specification","body":"IETF","designation":"RFC 3645","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3645.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3645.txt","https://www.rfc-editor.org/rfc/rfc3645.pdf"],"folder":"IETF/RFC-3645","files":{"txt":{"path":"standards/IETF/RFC-3645/RFC-3645.txt","sha256":"18443eba664ecbeff6ac63bf11f260b9e8cb801f60a963b3e89586485fa44efe"}},"tags":["nested-reference","unchanged"],"summary":"The Secret Key Transaction Authentication for DNS (TSIG) protocol\n provides transaction level authentication for DNS. TSIG is\n extensible through the definition of new algorithms. This document\n specifies an algorithm based on the Generic Security Service\n Application Program Interface (GSS-API) (RFC2743). This document\n updates RFC 2845.\n\nKwan, et al. Standards Track [Page 1]\n\f\nRFC 3645 GSS-TSIG October 2003","scope_keywords":["3645","algorithm","algorithms","authentication","authorization","key","management","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 3645 The Secret Key Transaction Authentication for DNS (TSIG) protocol\n provides transaction level authentication for DNS. TSIG is\n extensible through the definition of new algorithms. This document\n specifies an algorithm based on the Generic Security Service\n Application Program Interface (GSS-API) (RFC2743). This document\n updates RFC 2845.\n\nKwan, et al. Standards Track [Page 1]\n\f\nRFC 3645 GSS-TSIG October 2003 3645 algorithm algorithms authentication authorization key management signature signatures nested-reference unchanged"},{"id":"IETF RFC 3646","type":"specification","body":"IETF","designation":"RFC 3646","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3646.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3646.txt","https://www.rfc-editor.org/rfc/rfc3646.pdf"],"folder":"IETF/RFC-3646","files":{"txt":{"path":"standards/IETF/RFC-3646/RFC-3646.txt","sha256":"d96648fe122539da800d23ff128d21e3fc962bdc034d571b1b863ce60a1c6a93"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Dynamic Host Configuration Protocol for IPv6\n (DHCPv6) options for passing a list of available DNS recursive name\n servers and a domain search list to a client.\n\n1. Introduction\n\n This document describes two options for passing configuration\n information related to Domain Name Service (DNS) (RFC 1034 [6] and\n RFC 1035 [1]) in DHCPv6 (RFC 3315 [2]).\n\n2. Terminology\n\n The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be\n interpreted as described in BCP 14, RFC 2119 [3].\n\n Throughout this document, unless otherwise specified, the acronym\n DHCP refers to DHCP for IPv6 (DHCPv6) as specified in RFC 3315.\n\n This document uses terminology specific to IPv6 and DHCP as defined\n in section \"Terminology\" of RFC 3315.\n\nDroms Standards Track [Page 1]\n\f\nRFC 3646 DNS Configuration Options for DHCP","scope_keywords":["3646","authentication","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3646 This document describes Dynamic Host Configuration Protocol for IPv6\n (DHCPv6) options for passing a list of available DNS recursive name\n servers and a domain search list to a client.\n\n1. Introduction\n\n This document describes two options for passing configuration\n information related to Domain Name Service (DNS) (RFC 1034 [6] and\n RFC 1035 [1]) in DHCPv6 (RFC 3315 [2]).\n\n2. Terminology\n\n The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be\n interpreted as described in BCP 14, RFC 2119 [3].\n\n Throughout this document, unless otherwise specified, the acronym\n DHCP refers to DHCP for IPv6 (DHCPv6) as specified in RFC 3315.\n\n This document uses terminology specific to IPv6 and DHCP as defined\n in section \"Terminology\" of RFC 3315.\n\nDroms Standards Track [Page 1]\n\f\nRFC 3646 DNS Configuration Options for DHCP 3646 authentication key presentation nested-reference unchanged"},{"id":"IETF RFC 3650","type":"specification","body":"IETF","designation":"RFC 3650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3650.txt","https://www.rfc-editor.org/rfc/rfc3650.pdf"],"folder":"IETF/RFC-3650","files":{"txt":{"path":"standards/IETF/RFC-3650/RFC-3650.txt","sha256":"a01985cbb8cd3e98bccdfc566ae98ccd8ecadf11802f6d1cd2dd046c11a19cb7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of the Handle System in terms of\n its namespace and service architecture, as well as its relationship\n to other Internet services such as DNS, LDAP/X.500, and URNs. The\n Handle System is a general-purpose global name service that allows\n secured name resolution and administration over networks such as the\n Internet. The Handle System manages handles, which are unique names\n for digital objects and other Internet resources.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 3650 Handle System Overview November 2003","scope_keywords":["3650","http","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null}],"search_text":"IETF RFC 3650 This document provides an overview of the Handle System in terms of\n its namespace and service architecture, as well as its relationship\n to other Internet services such as DNS, LDAP/X.500, and URNs. The\n Handle System is a general-purpose global name service that allows\n secured name resolution and administration over networks such as the\n Internet. The Handle System manages handles, which are unique names\n for digital objects and other Internet resources.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 3650 Handle System Overview November 2003 3650 http key path nested-reference unchanged"},{"id":"IETF RFC 3651","type":"specification","body":"IETF","designation":"RFC 3651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3651.txt","https://www.rfc-editor.org/rfc/rfc3651.pdf"],"folder":"IETF/RFC-3651","files":{"txt":{"path":"standards/IETF/RFC-3651/RFC-3651.txt","sha256":"9f8667c3c530f0a94a2e74b300676931c0770c6a52c242fbe8954717817d82e1"}},"tags":["nested-reference","unchanged"],"summary":"The Handle System is a general-purpose global name service that\n allows secured name resolution and administration over the public\n Internet. This document provides a detailed description of the\n Handle System namespace, and its data, service, and operation models.\n The namespace definition specifies the handle syntax and its semantic\n structure. The data model defines the data structures used by the\n Handle System protocol and any pre-defined data types for carrying\n out the handle service. The service model provides definitions of\n various Handle System components and explains how they work together\n over the network. Finally, the Handle System operation model\n describes its service operation in terms of messages transmitted\n between client and server, and the client authentication process\n based on the Handle System authentication protocol.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 36","scope_keywords":["3651","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null}],"search_text":"IETF RFC 3651 The Handle System is a general-purpose global name service that\n allows secured name resolution and administration over the public\n Internet. This document provides a detailed description of the\n Handle System namespace, and its data, service, and operation models.\n The namespace definition specifies the handle syntax and its semantic\n structure. The data model defines the data structures used by the\n Handle System protocol and any pre-defined data types for carrying\n out the handle service. The service model provides definitions of\n various Handle System components and explains how they work together\n over the network. Finally, the Handle System operation model\n describes its service operation in terms of messages transmitted\n between client and server, and the client authentication process\n based on the Handle System authentication protocol.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 36 3651 authentication nested-reference unchanged"},{"id":"IETF RFC 3675","type":"specification","body":"IETF","designation":"RFC 3675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3675.txt","https://www.rfc-editor.org/rfc/rfc3675.pdf"],"folder":"IETF/RFC-3675","files":{"txt":{"path":"standards/IETF/RFC-3675/RFC-3675.txt","sha256":"e5f19e6c5dba2c90e718b11e983d813045f70880f0627ca016a5a495718840ec"}},"tags":["nested-reference","unchanged"],"summary":"Periodically there are proposals to mandate the use of a special top\n level name or an IP address bit to flag \"adult\" or \"unsafe\" material\n or the like. This document explains why this is an ill considered\n idea from the legal, philosophical, and particularly, the technical\n points of view.","scope_keywords":["3675","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null}],"search_text":"IETF RFC 3675 Periodically there are proposals to mandate the use of a special top\n level name or an IP address bit to flag \"adult\" or \"unsafe\" material\n or the like. This document explains why this is an ill considered\n idea from the legal, philosophical, and particularly, the technical\n points of view. 3675 http nested-reference unchanged"},{"id":"IETF RFC 3732","type":"specification","body":"IETF","designation":"RFC 3732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3732.txt","https://www.rfc-editor.org/rfc/rfc3732.pdf"],"folder":"IETF/RFC-3732","files":{"txt":{"path":"standards/IETF/RFC-3732/RFC-3732.txt","sha256":"af360534d949a95156a79e487f1bb2abca16879ebf2dd7c279f31f54637f7c04"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names.","scope_keywords":["3732","attribute","attributes","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null}],"search_text":"IETF RFC 3732 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet host names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to host names. 3732 attribute attributes key management subject nested-reference unchanged"},{"id":"IETF RFC 3736","type":"specification","body":"IETF","designation":"RFC 3736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3736.txt","https://www.rfc-editor.org/rfc/rfc3736.pdf"],"folder":"IETF/RFC-3736","files":{"txt":{"path":"standards/IETF/RFC-3736/RFC-3736.txt","sha256":"f0fc1e00447366eaa1796a76b99c425ff301822c6085f110da3916beb0a6da7d"}},"tags":["nested-reference","unchanged"],"summary":"Stateless Dynamic Host Configuration Protocol service for IPv6\n (DHCPv6) is used by nodes to obtain configuration information, such\n as the addresses of DNS recursive name servers, that does not require\n the maintenance of any dynamic state for individual clients. A node\n that uses stateless DHCP must have obtained its IPv6 addresses\n through some other mechanism, typically stateless address\n autoconfiguration. This document explains which parts of RFC 3315\n must be implemented in each of the different kinds of DHCP agents so\n that agent can support stateless DHCP.\n\n1. Introduction\n\n Nodes that have obtained IPv6 addresses through some other mechanism,\n such as stateless address autoconfiguration [6] or manual\n configuration, can use stateless DHCP to obtain other configuration\n information such as a list of DNS recursive name servers or SIP\n servers. A stateless DHCP server provides onl","scope_keywords":["3736","authentication","policies","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4076","folder":"IETF/RFC-4076","source":"IETF/RFC-4076/RFC-4076.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4242","folder":"IETF/RFC-4242","source":"IETF/RFC-4242/RFC-4242.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3736 Stateless Dynamic Host Configuration Protocol service for IPv6\n (DHCPv6) is used by nodes to obtain configuration information, such\n as the addresses of DNS recursive name servers, that does not require\n the maintenance of any dynamic state for individual clients. A node\n that uses stateless DHCP must have obtained its IPv6 addresses\n through some other mechanism, typically stateless address\n autoconfiguration. This document explains which parts of RFC 3315\n must be implemented in each of the different kinds of DHCP agents so\n that agent can support stateless DHCP.\n\n1. Introduction\n\n Nodes that have obtained IPv6 addresses through some other mechanism,\n such as stateless address autoconfiguration [6] or manual\n configuration, can use stateless DHCP to obtain other configuration\n information such as a list of DNS recursive name servers or SIP\n servers. A stateless DHCP server provides onl 3736 authentication policies presentation validation nested-reference unchanged"},{"id":"IETF RFC 3743","type":"specification","body":"IETF","designation":"RFC 3743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3743.txt","https://www.rfc-editor.org/rfc/rfc3743.pdf"],"folder":"IETF/RFC-3743","files":{"txt":{"path":"standards/IETF/RFC-3743/RFC-3743.txt","sha256":"334b2193146e5a611dd00e5d88c6a62c306f4e15cfa3df46ef523f98c20bfa97"}},"tags":["nested-reference","unchanged"],"summary":"Achieving internationalized access to domain names raises many\n complex issues. These are associated not only with basic protocol\n design, such as how names are represented on the network, compared,\n and converted to appropriate forms, but also with issues and options\n for deployment, transition, registration, and administration.\n\nKonishi, et al. Informational [Page 1]\n\f\nRFC 3743 JET Guidelines for IDN April 2004\n\n The IETF Standards for Internationalized Domain Names, known as\n \"IDNA\", focuses on access to domain names in a range of scripts that\n is broader in scope than the original ASCII. The development process\n made it clear that use of characters with similar appearances and/or\n interpretations created potential for confusion, as well as\n difficulties in deployment and transition. The conclusion was that,\n while those issues were important, they could best be addressed\n administrat","scope_keywords":["3743","algorithm","policies","policy","profile","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null}],"search_text":"IETF RFC 3743 Achieving internationalized access to domain names raises many\n complex issues. These are associated not only with basic protocol\n design, such as how names are represented on the network, compared,\n and converted to appropriate forms, but also with issues and options\n for deployment, transition, registration, and administration.\n\nKonishi, et al. Informational [Page 1]\n\f\nRFC 3743 JET Guidelines for IDN April 2004\n\n The IETF Standards for Internationalized Domain Names, known as\n \"IDNA\", focuses on access to domain names in a range of scripts that\n is broader in scope than the original ASCII. The development process\n made it clear that use of characters with similar appearances and/or\n interpretations created potential for confusion, as well as\n difficulties in deployment and transition. The conclusion was that,\n while those issues were important, they could best be addressed\n administrat 3743 algorithm policies policy profile risk nested-reference unchanged"},{"id":"IETF RFC 3764","type":"specification","body":"IETF","designation":"RFC 3764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3764.txt","https://www.rfc-editor.org/rfc/rfc3764.pdf"],"folder":"IETF/RFC-3764","files":{"txt":{"path":"standards/IETF/RFC-3764/RFC-3764.txt","sha256":"883b12eb3cf6eec6daa880f8fd8a50a204db1fe60e35714f8ffc805d23f60def"}},"tags":["nested-reference","unchanged"],"summary":"This document registers an Electronic Number (ENUM) service for the\n Session Initiation Protocol (SIP), pursuant to the guidelines in RFC\n 3761. Specifically, this document focuses on provisioning SIP\n addresses-of-record in ENUM.","scope_keywords":["3764","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 3764 This document registers an Electronic Number (ENUM) service for the\n Session Initiation Protocol (SIP), pursuant to the guidelines in RFC\n 3761. Specifically, this document focuses on provisioning SIP\n addresses-of-record in ENUM. 3764 registered nested-reference unchanged"},{"id":"IETF RFC 3795","type":"specification","body":"IETF","designation":"RFC 3795","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3795.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3795.txt","https://www.rfc-editor.org/rfc/rfc3795.pdf"],"folder":"IETF/RFC-3795","files":{"txt":{"path":"standards/IETF/RFC-3795/RFC-3795.txt","sha256":"345847e616d34e3d08d074652a67e7d599fea02885b0d21ad7e9247b9e4afc90"}},"tags":["nested-reference","unchanged"],"summary":"This document describes IPv4 addressing dependencies in an attempt to\n clarify the necessary steps in re-designing and re-implementing\n specifications to become network address independent, or at least, to\n dually support IPv4 and IPv6. This transition requires several\n interim steps, one of them being the evolution of current IPv4\n dependent specifications to a format independent of the type of IP\n addressing schema used. Hence, it is hoped that specifications will\n be re-designed and re-implemented to become network address\n independent, or at least to dually support IPv4 and IPv6.\n\n To achieve that step, it is necessary to survey and document all IPv4\n dependencies experienced by current standards (Full, Draft, and\n Proposed) as well as Experimental RFCs. Hence, this document\n describes IPv4 addressing dependencies that deployed IETF Application\n Area documented Standards may experien","scope_keywords":["3795","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 3795 This document describes IPv4 addressing dependencies in an attempt to\n clarify the necessary steps in re-designing and re-implementing\n specifications to become network address independent, or at least, to\n dually support IPv4 and IPv6. This transition requires several\n interim steps, one of them being the evolution of current IPv4\n dependent specifications to a format independent of the type of IP\n addressing schema used. Hence, it is hoped that specifications will\n be re-designed and re-implemented to become network address\n independent, or at least to dually support IPv4 and IPv6.\n\n To achieve that step, it is necessary to survey and document all IPv4\n dependencies experienced by current standards (Full, Draft, and\n Proposed) as well as Experimental RFCs. Hence, this document\n describes IPv4 addressing dependencies that deployed IETF Application\n Area documented Standards may experien 3795 management nested-reference unchanged"},{"id":"IETF RFC 3801","type":"specification","body":"IETF","designation":"RFC 3801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3801.txt","https://www.rfc-editor.org/rfc/rfc3801.pdf"],"folder":"IETF/RFC-3801","files":{"txt":{"path":"standards/IETF/RFC-3801/RFC-3801.txt","sha256":"09963ba68d8b545c1940d1f683516f72c37d1a01d41bd656624f1a2819eb7d25"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a restricted profile of the Internet\n multimedia messaging protocols for use between voice processing\n server platforms. The profile is referred to as the Voice Profile\n for Internet Mail (VPIM) in this document. These platforms have\n historically been special-purpose computers and often do not have the\n same facilities normally associated with a traditional Internet\n Email-capable computer. As a result, VPIM also specifies additional\n functionality, as it is needed. This profile is intended to specify\n the minimum common set of features to allow interworking between\n conforming systems.\n\n This document obsoletes RFC 2421 and describes version 2 of the\n profile with greater precision. No protocol changes were made in\n this revision. A list of changes from RFC 2421 are noted in Appendix\n F. Appendix A summarizes the protocol profiles of this version of\n VPIM.\n\nVaud","scope_keywords":["3801","delivery","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 3803","folder":"IETF/RFC-3803","source":"IETF/RFC-3803/RFC-3803.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"IETF RFC 3801 This document specifies a restricted profile of the Internet\n multimedia messaging protocols for use between voice processing\n server platforms. The profile is referred to as the Voice Profile\n for Internet Mail (VPIM) in this document. These platforms have\n historically been special-purpose computers and often do not have the\n same facilities normally associated with a traditional Internet\n Email-capable computer. As a result, VPIM also specifies additional\n functionality, as it is needed. This profile is intended to specify\n the minimum common set of features to allow interworking between\n conforming systems.\n\n This document obsoletes RFC 2421 and describes version 2 of the\n profile with greater precision. No protocol changes were made in\n this revision. A list of changes from RFC 2421 are noted in Appendix\n F. Appendix A summarizes the protocol profiles of this version of\n VPIM.\n\nVaud 3801 delivery management profile profiles nested-reference unchanged"},{"id":"IETF RFC 3824","type":"specification","body":"IETF","designation":"RFC 3824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3824.txt","https://www.rfc-editor.org/rfc/rfc3824.pdf"],"folder":"IETF/RFC-3824","files":{"txt":{"path":"standards/IETF/RFC-3824/RFC-3824.txt","sha256":"c692d1faba9c0dd6b421eed2590d872aaaf0b764c499a50dd502b6dd95b1633b"}},"tags":["nested-reference","unchanged"],"summary":"There are a number of contexts in which telephone numbers are\n employed by Session Initiation Protocol (SIP) applications, many of\n which can be addressed by ENUM. Although SIP was one of the primary\n applications for which ENUM was created, there is nevertheless a need\n to define procedures for integrating ENUM with SIP implementations.\n This document illustrates how the two protocols might work in\n concert, and clarifies the authoring and processing of ENUM records\n for SIP applications. It also provides guidelines for instances in\n which ENUM, for whatever reason, cannot be used to resolve a\n telephone number.","scope_keywords":["3824","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null}],"search_text":"IETF RFC 3824 There are a number of contexts in which telephone numbers are\n employed by Session Initiation Protocol (SIP) applications, many of\n which can be addressed by ENUM. Although SIP was one of the primary\n applications for which ENUM was created, there is nevertheless a need\n to define procedures for integrating ENUM with SIP implementations.\n This document illustrates how the two protocols might work in\n concert, and clarifies the authoring and processing of ENUM records\n for SIP applications. It also provides guidelines for instances in\n which ENUM, for whatever reason, cannot be used to resolve a\n telephone number. 3824 key nested-reference unchanged"},{"id":"IETF RFC 3832","type":"specification","body":"IETF","designation":"RFC 3832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3832.txt","https://www.rfc-editor.org/rfc/rfc3832.pdf"],"folder":"IETF/RFC-3832","files":{"txt":{"path":"standards/IETF/RFC-3832/RFC-3832.txt","sha256":"5bf8960a02f1763d46db7812867aead204f07aae6be5045dab3252779000830f"}},"tags":["nested-reference","unchanged"],"summary":"Remote service discovery refers to discovering desired services in\n given remote (i.e., non-local) DNS domains. This document describes\n remote service discovery in the Service Location Protocol (SLP) via\n DNS SRV. It defines the DNS SRV Resource Records for SLP Directory\n Agent services, discusses various issues in using SLP and DNS SRV\n together for remote service discovery, and gives the steps for\n discovering desired services in remote DNS domains.\n\n1. Introduction\n\n This document describes remote service discovery in the Service\n Location Protocol (SLP) [RFC2608] via DNS SRV [RFC2782]. We consider\n remote service discovery as discovering desired services in given\n remote DNS domains, and local service discovery as discovering\n desired services within the local administrative domain.\n\n SLP provides a scalable framework for local service discovery and\n selection. In SLP, User Agents (","scope_keywords":["3832","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 3832 Remote service discovery refers to discovering desired services in\n given remote (i.e., non-local) DNS domains. This document describes\n remote service discovery in the Service Location Protocol (SLP) via\n DNS SRV. It defines the DNS SRV Resource Records for SLP Directory\n Agent services, discusses various issues in using SLP and DNS SRV\n together for remote service discovery, and gives the steps for\n discovering desired services in remote DNS domains.\n\n1. Introduction\n\n This document describes remote service discovery in the Service\n Location Protocol (SLP) [RFC2608] via DNS SRV [RFC2782]. We consider\n remote service discovery as discovering desired services in given\n remote DNS domains, and local service discovery as discovering\n desired services within the local administrative domain.\n\n SLP provides a scalable framework for local service discovery and\n selection. In SLP, User Agents ( 3832 key registered nested-reference unchanged"},{"id":"IETF RFC 3833","type":"specification","body":"IETF","designation":"RFC 3833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3833.txt","https://www.rfc-editor.org/rfc/rfc3833.pdf"],"folder":"IETF/RFC-3833","files":{"txt":{"path":"standards/IETF/RFC-3833/RFC-3833.txt","sha256":"cf91742fee8456127dac921deca98e46b3e9c2b38421f9c8e45a9a31c887a8aa"}},"tags":["nested-reference","unchanged"],"summary":"Although the DNS Security Extensions (DNSSEC) have been under\n development for most of the last decade, the IETF has never written\n down the specific set of threats against which DNSSEC is designed to\n protect. Among other drawbacks, this cart-before-the-horse situation\n has made it difficult to determine whether DNSSEC meets its design\n goals, since its design goals are not well specified. This note\n attempts to document some of the known threats to the DNS, and, in\n doing so, attempts to measure to what extent (if any) DNSSEC is a\n useful tool in defending against these threats.\n\n1. Introduction\n\n The earliest organized work on DNSSEC within the IETF was an open\n design team meeting organized by members of the DNS working group in\n November 1993 at the 28th IETF meeting in Houston. The broad\n outlines of DNSSEC as we know it today are already clear in Jim\n Galvin's summary of the resul","scope_keywords":["3833","authentication","key","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 3833 Although the DNS Security Extensions (DNSSEC) have been under\n development for most of the last decade, the IETF has never written\n down the specific set of threats against which DNSSEC is designed to\n protect. Among other drawbacks, this cart-before-the-horse situation\n has made it difficult to determine whether DNSSEC meets its design\n goals, since its design goals are not well specified. This note\n attempts to document some of the known threats to the DNS, and, in\n doing so, attempts to measure to what extent (if any) DNSSEC is a\n useful tool in defending against these threats.\n\n1. Introduction\n\n The earliest organized work on DNSSEC within the IETF was an open\n design team meeting organized by members of the DNS working group in\n November 1993 at the 28th IETF meeting in Houston. The broad\n outlines of DNSSEC as we know it today are already clear in Jim\n Galvin's summary of the resul 3833 authentication key signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 3845","type":"specification","body":"IETF","designation":"RFC 3845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3845.txt","https://www.rfc-editor.org/rfc/rfc3845.pdf"],"folder":"IETF/RFC-3845","files":{"txt":{"path":"standards/IETF/RFC-3845/RFC-3845.txt","sha256":"99c7843b682a9d3e344b9712703e26206ff797658f215e9156d26bddc0cf0182"}},"tags":["nested-reference","unchanged"],"summary":"This document redefines the wire format of the \"Type Bit Map\" field\n in the DNS NextSECure (NSEC) resource record RDATA format to cover\n the full resource record (RR) type space.","scope_keywords":["3845","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null}],"search_text":"IETF RFC 3845 This document redefines the wire format of the \"Type Bit Map\" field\n in the DNS NextSECure (NSEC) resource record RDATA format to cover\n the full resource record (RR) type space. 3845 key presentation nested-reference unchanged"},{"id":"IETF RFC 3861","type":"specification","body":"IETF","designation":"RFC 3861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3861.txt","https://www.rfc-editor.org/rfc/rfc3861.pdf"],"folder":"IETF/RFC-3861","files":{"txt":{"path":"standards/IETF/RFC-3861/RFC-3861.txt","sha256":"56afa68e14be6effcdeb126e7286c8437efe03dff9cc1e4d60f244eb36da9851"}},"tags":["nested-reference","unchanged"],"summary":"Presence and instant messaging are defined in RFC 2778. The Common\n Profiles for Presence and Instant Messaging define two Universal\n Resource Identifier (URI) schemes: 'im' for INSTANT INBOXes and\n 'pres' for PRESENTITIES. This document provides guidance for\n locating the resources associated with URIs that employ these\n schemes.","scope_keywords":["3861","attribute","attributes","key","profile","profiles","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 3861 Presence and instant messaging are defined in RFC 2778. The Common\n Profiles for Presence and Instant Messaging define two Universal\n Resource Identifier (URI) schemes: 'im' for INSTANT INBOXes and\n 'pres' for PRESENTITIES. This document provides guidance for\n locating the resources associated with URIs that employ these\n schemes. 3861 attribute attributes key profile profiles qualified registered nested-reference unchanged"},{"id":"IETF RFC 3875","type":"specification","body":"IETF","designation":"RFC 3875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3875.txt","https://www.rfc-editor.org/rfc/rfc3875.pdf"],"folder":"IETF/RFC-3875","files":{"pdf":{"path":"standards/IETF/RFC-3875/RFC-3875.pdf","sha256":"39cd1da396077793c710ce9a0e11c66e4cb191b23423119a578b2e08ab51c813"},"txt":{"path":"standards/IETF/RFC-3875/RFC-3875.txt","sha256":"66069863b0d495a8287604548610f68a721ec5d04cd7f7c3a8a673da46e0df19"}},"tags":["nested-reference","unchanged"],"summary":"The Common Gateway Interface (CGI) is a simple interface for running\n external programs, software or gateways under an information server\n in a platform-independent manner. Currently, the supported\n information servers are HTTP servers.\n\n The interface has been in use by the World-Wide Web (WWW) since 1993.\n This specification defines the 'current practice' parameters of the\n 'CGI/1.1' interface developed and documented at the U.S. National\n Centre for Supercomputing Applications. This document also defines\n the use of the CGI/1.1 interface on UNIX(R) and other, similar\n systems.\n\nRobinson & Coar Informational [Page 1]\n\f\nRFC 3875 CGI Version 1.1 October 2004","scope_keywords":["3875","http","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 3875 The Common Gateway Interface (CGI) is a simple interface for running\n external programs, software or gateways under an information server\n in a platform-independent manner. Currently, the supported\n information servers are HTTP servers.\n\n The interface has been in use by the World-Wide Web (WWW) since 1993.\n This specification defines the 'current practice' parameters of the\n 'CGI/1.1' interface developed and documented at the U.S. National\n Centre for Supercomputing Applications. This document also defines\n the use of the CGI/1.1 interface on UNIX(R) and other, similar\n systems.\n\nRobinson & Coar Informational [Page 1]\n\f\nRFC 3875 CGI Version 1.1 October 2004 3875 http identification path nested-reference unchanged"},{"id":"IETF RFC 3901","type":"specification","body":"IETF","designation":"RFC 3901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3901.txt","https://www.rfc-editor.org/rfc/rfc3901.pdf"],"folder":"IETF/RFC-3901","files":{"txt":{"path":"standards/IETF/RFC-3901/RFC-3901.txt","sha256":"47f053e71f0402a77a758e8fee91419f05e1581af1803604cd9de6c6fee67230"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Durand\nRequest for Comments: 3901 SUN Microsystems, Inc.\nBCP: 91 J. Ihren\nCategory: Best Current Practice Autonomica\n September 2004\n\n DNS IPv6 Transport Operational Guidelines\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004).\n\nAbstract\n\n This memo provides guidelines and Best Current Practice for operating\n DNS in a world where queries and responses are carried in a mixed\n environment of IPv4 and IPv6 networks.\n\n1. Introduction to the Problem of Name Space Fragmentation:\n following the referral chain\n\n A resolver that tries to look up a name starts out at the root, and\n follows referrals until it is referred to a name server that is\n authorita","scope_keywords":["3901","policies","policy","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null}],"search_text":"IETF RFC 3901 Network Working Group A. Durand\nRequest for Comments: 3901 SUN Microsystems, Inc.\nBCP: 91 J. Ihren\nCategory: Best Current Practice Autonomica\n September 2004\n\n DNS IPv6 Transport Operational Guidelines\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004).\n\nAbstract\n\n This memo provides guidelines and Best Current Practice for operating\n DNS in a world where queries and responses are carried in a mixed\n environment of IPv4 and IPv6 networks.\n\n1. Introduction to the Problem of Name Space Fragmentation:\n following the referral chain\n\n A resolver that tries to look up a name starts out at the root, and\n follows referrals until it is referred to a name server that is\n authorita 3901 policies policy subject validation nested-reference unchanged"},{"id":"IETF RFC 3971","type":"specification","body":"IETF","designation":"RFC 3971","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3971.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3971.txt","https://www.rfc-editor.org/rfc/rfc3971.pdf"],"folder":"IETF/RFC-3971","files":{"txt":{"path":"standards/IETF/RFC-3971/RFC-3971.txt","sha256":"9484f88120b89ba5ecd32060005935bb5dfe3a03e76656755c2b10b200416620"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover\n other nodes on the link, to determine their link-layer addresses to\n find routers, and to maintain reachability information about the\n paths to active neighbors. If not secured, NDP is vulnerable to\n various attacks. This document specifies security mechanisms for\n NDP. Unlike those in the original NDP specifications, these\n mechanisms do not use IPsec.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 3971 SEcure Neighbor Discovery March 2005","scope_keywords":["3971","authorization","certificate","certificates","management","path","profile","signature","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4016","folder":"IETF/RFC-4016","source":"IETF/RFC-4016/RFC-4016.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4135","folder":"IETF/RFC-4135","source":"IETF/RFC-4135/RFC-4135.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4832","folder":"IETF/RFC-4832","source":"IETF/RFC-4832/RFC-4832.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6105","folder":"IETF/RFC-6105","source":"IETF/RFC-6105/RFC-6105.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 3971 IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover\n other nodes on the link, to determine their link-layer addresses to\n find routers, and to maintain reachability information about the\n paths to active neighbors. If not secured, NDP is vulnerable to\n various attacks. This document specifies security mechanisms for\n NDP. Unlike those in the original NDP specifications, these\n mechanisms do not use IPsec.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 3971 SEcure Neighbor Discovery March 2005 3971 authorization certificate certificates management path profile signature timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4025","type":"specification","body":"IETF","designation":"RFC 4025","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4025.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4025.txt","https://www.rfc-editor.org/rfc/rfc4025.pdf"],"folder":"IETF/RFC-4025","files":{"txt":{"path":"standards/IETF/RFC-4025/RFC-4025.txt","sha256":"296d22a3cd5d8e435dcaba4c5b6cb3124151f38c7f531595ff4ec2bf8b081bf0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new resource record for the Domain Name\n System (DNS). This record may be used to store public keys for use\n in IP security (IPsec) systems. The record also includes provisions\n for indicating what system should be contacted when an IPsec tunnel\n is established with the entity in question.\n\n This record replaces the functionality of the sub-type #4 of the KEY\n Resource Record, which has been obsoleted by RFC 3445.","scope_keywords":["4025","algorithm","key","keys","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4025 This document describes a new resource record for the Domain Name\n System (DNS). This record may be used to store public keys for use\n in IP security (IPsec) systems. The record also includes provisions\n for indicating what system should be contacted when an IPsec tunnel\n is established with the entity in question.\n\n This record replaces the functionality of the sub-type #4 of the KEY\n Resource Record, which has been obsoleted by RFC 3445. 4025 algorithm key keys policy presentation nested-reference unchanged"},{"id":"IETF RFC 4027","type":"specification","body":"IETF","designation":"RFC 4027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4027.txt","https://www.rfc-editor.org/rfc/rfc4027.pdf"],"folder":"IETF/RFC-4027","files":{"txt":{"path":"standards/IETF/RFC-4027/RFC-4027.txt","sha256":"997fd2044b96b936aee8e5800ccf72a2eb4f92534e4bcccf3cc1f4555f3ad559"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the media types application/dns and text/dns\n in accordance with RFC 2048. The application/dns media type is used\n to identify data on the detached Domain Name System (DNS) format\n described in RFC 2540. The text/dns media type is used to identify\n master files as described in RFC 1035.","scope_keywords":["4027","archiving","certificate","certificates","crl","license","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null}],"search_text":"IETF RFC 4027 This document registers the media types application/dns and text/dns\n in accordance with RFC 2048. The application/dns media type is used\n to identify data on the detached Domain Name System (DNS) format\n described in RFC 2540. The text/dns media type is used to identify\n master files as described in RFC 1035. 4027 archiving certificate certificates crl license registered subject nested-reference unchanged"},{"id":"IETF RFC 4033","type":"specification","body":"IETF","designation":"RFC 4033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4033.txt","https://www.rfc-editor.org/rfc/rfc4033.pdf"],"folder":"IETF/RFC-4033","files":{"txt":{"path":"standards/IETF/RFC-4033/RFC-4033.txt","sha256":"b6803149a879dff56cbaffcb8c5a1795d2a2d2facdc3400ebd9937e38724e4cd"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System Security Extensions (DNSSEC) add data origin\n authentication and data integrity to the Domain Name System. This\n document introduces these extensions and describes their capabilities\n and limitations. This document also discusses the services that the\n DNS security extensions do and do not provide. Last, this document\n describes the interrelationships between the documents that\n collectively describe DNSSEC.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4033 DNS Security Introduction and Requirements March 2005","scope_keywords":["4033","authentication","hash","key","keys","policy","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4431","folder":"IETF/RFC-4431","source":"IETF/RFC-4431/RFC-4431.txt","version":null},{"body":"IETF","designation":"RFC 4470","folder":"IETF/RFC-4470","source":"IETF/RFC-4470/RFC-4470.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4509","folder":"IETF/RFC-4509","source":"IETF/RFC-4509/RFC-4509.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4686","folder":"IETF/RFC-4686","source":"IETF/RFC-4686/RFC-4686.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4892","folder":"IETF/RFC-4892","source":"IETF/RFC-4892/RFC-4892.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4955","folder":"IETF/RFC-4955","source":"IETF/RFC-4955/RFC-4955.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 4986","folder":"IETF/RFC-4986","source":"IETF/RFC-4986/RFC-4986.txt","version":null},{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5338","folder":"IETF/RFC-5338","source":"IETF/RFC-5338/RFC-5338.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7706","folder":"IETF/RFC-7706","source":"IETF/RFC-7706/RFC-7706.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4033 The Domain Name System Security Extensions (DNSSEC) add data origin\n authentication and data integrity to the Domain Name System. This\n document introduces these extensions and describes their capabilities\n and limitations. This document also discusses the services that the\n DNS security extensions do and do not provide. Last, this document\n describes the interrelationships between the documents that\n collectively describe DNSSEC.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4033 DNS Security Introduction and Requirements March 2005 4033 authentication hash key keys policy signature trust nested-reference unchanged"},{"id":"IETF RFC 4034","type":"specification","body":"IETF","designation":"RFC 4034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4034.txt","https://www.rfc-editor.org/rfc/rfc4034.pdf"],"folder":"IETF/RFC-4034","files":{"txt":{"path":"standards/IETF/RFC-4034/RFC-4034.txt","sha256":"6c32963b76808ec4e5f1282b5e13c5216df4670d21e1590bf29af4066f49b355"}},"tags":["nested-reference","unchanged"],"summary":"This document is part of a family of documents that describe the DNS\n Security Extensions (DNSSEC). The DNS Security Extensions are a\n collection of resource records and protocol modifications that\n provide source authentication for the DNS. This document defines the\n public key (DNSKEY), delegation signer (DS), resource record digital\n signature (RRSIG), and authenticated denial of existence (NSEC)\n resource records. The purpose and format of each resource record is\n described in detail, and an example of each resource record is given.\n\n This document obsoletes RFC 2535 and incorporates changes from all\n updates to RFC 2535.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4034 DNSSEC Resource Records March 2005","scope_keywords":["4034","algorithm","authentication","key","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4431","folder":"IETF/RFC-4431","source":"IETF/RFC-4431/RFC-4431.txt","version":null},{"body":"IETF","designation":"RFC 4470","folder":"IETF/RFC-4470","source":"IETF/RFC-4470/RFC-4470.txt","version":null},{"body":"IETF","designation":"RFC 4509","folder":"IETF/RFC-4509","source":"IETF/RFC-4509/RFC-4509.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4955","folder":"IETF/RFC-4955","source":"IETF/RFC-4955/RFC-4955.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 4986","folder":"IETF/RFC-4986","source":"IETF/RFC-4986/RFC-4986.txt","version":null},{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null},{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8078","folder":"IETF/RFC-8078","source":"IETF/RFC-8078/RFC-8078.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4034 This document is part of a family of documents that describe the DNS\n Security Extensions (DNSSEC). The DNS Security Extensions are a\n collection of resource records and protocol modifications that\n provide source authentication for the DNS. This document defines the\n public key (DNSKEY), delegation signer (DS), resource record digital\n signature (RRSIG), and authenticated denial of existence (NSEC)\n resource records. The purpose and format of each resource record is\n described in detail, and an example of each resource record is given.\n\n This document obsoletes RFC 2535 and incorporates changes from all\n updates to RFC 2535.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4034 DNSSEC Resource Records March 2005 4034 algorithm authentication key presentation signature nested-reference unchanged"},{"id":"IETF RFC 4035","type":"specification","body":"IETF","designation":"RFC 4035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4035.txt","https://www.rfc-editor.org/rfc/rfc4035.pdf"],"folder":"IETF/RFC-4035","files":{"txt":{"path":"standards/IETF/RFC-4035/RFC-4035.txt","sha256":"8978b120636c69b2080b12768266ec48cd4c0879583310863a62f7c409908084"}},"tags":["nested-reference","unchanged"],"summary":"This document is part of a family of documents that describe the DNS\n Security Extensions (DNSSEC). The DNS Security Extensions are a\n collection of new resource records and protocol modifications that\n add data origin authentication and data integrity to the DNS. This\n document describes the DNSSEC protocol modifications. This document\n defines the concept of a signed zone, along with the requirements for\n serving and resolving by using DNSSEC. These techniques allow a\n security-aware resolver to authenticate both DNS resource records and\n authoritative DNS error indications.\n\n This document obsoletes RFC 2535 and incorporates changes from all\n updates to RFC 2535.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4035 DNSSEC Protocol Modifications March 2005","scope_keywords":["4035","authentication","key","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4431","folder":"IETF/RFC-4431","source":"IETF/RFC-4431/RFC-4431.txt","version":null},{"body":"IETF","designation":"RFC 4470","folder":"IETF/RFC-4470","source":"IETF/RFC-4470/RFC-4470.txt","version":null},{"body":"IETF","designation":"RFC 4509","folder":"IETF/RFC-4509","source":"IETF/RFC-4509/RFC-4509.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4955","folder":"IETF/RFC-4955","source":"IETF/RFC-4955/RFC-4955.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 4986","folder":"IETF/RFC-4986","source":"IETF/RFC-4986/RFC-4986.txt","version":null},{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null},{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4035 This document is part of a family of documents that describe the DNS\n Security Extensions (DNSSEC). The DNS Security Extensions are a\n collection of new resource records and protocol modifications that\n add data origin authentication and data integrity to the DNS. This\n document describes the DNSSEC protocol modifications. This document\n defines the concept of a signed zone, along with the requirements for\n serving and resolving by using DNSSEC. These techniques allow a\n security-aware resolver to authenticate both DNS resource records and\n authoritative DNS error indications.\n\n This document obsoletes RFC 2535 and incorporates changes from all\n updates to RFC 2535.\n\nArends, et al. Standards Track [Page 1]\n\f\nRFC 4035 DNSSEC Protocol Modifications March 2005 4035 authentication key signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 4074","type":"specification","body":"IETF","designation":"RFC 4074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4074.txt","https://www.rfc-editor.org/rfc/rfc4074.pdf"],"folder":"IETF/RFC-4074","files":{"txt":{"path":"standards/IETF/RFC-4074/RFC-4074.txt","sha256":"7ef9605ad85012b5e79bec03cc5ea975ec020679c9596f1c663a83c333d6a4f3"}},"tags":["nested-reference","unchanged"],"summary":"There is some known misbehavior of DNS authoritative servers when\n they are queried for AAAA resource records. Such behavior can block\n IPv4 communication that should actually be available, cause a\n significant delay in name resolution, or even make a denial of\n service attack. This memo describes details of known cases and\n discusses their effects.\n\n1. Introduction\n\n Many existing DNS clients (resolvers) that support IPv6 first search\n for AAAA Resource Records (RRs) of a target host name, and then for A\n RRs of the same name. This fallback mechanism is based on the DNS\n specifications, which if not obeyed by authoritative servers, can\n produce unpleasant results. In some cases, for example, a web\n browser fails to connect to a web server it could otherwise reach.\n In the following sections, this memo describes some typical cases of\n such misbehavior and its (bad) effects.\n\n Note that t","scope_keywords":["4074","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null}],"search_text":"IETF RFC 4074 There is some known misbehavior of DNS authoritative servers when\n they are queried for AAAA resource records. Such behavior can block\n IPv4 communication that should actually be available, cause a\n significant delay in name resolution, or even make a denial of\n service attack. This memo describes details of known cases and\n discusses their effects.\n\n1. Introduction\n\n Many existing DNS clients (resolvers) that support IPv6 first search\n for AAAA Resource Records (RRs) of a target host name, and then for A\n RRs of the same name. This fallback mechanism is based on the DNS\n specifications, which if not obeyed by authoritative servers, can\n produce unpleasant results. In some cases, for example, a web\n browser fails to connect to a web server it could otherwise reach.\n In the following sections, this memo describes some typical cases of\n such misbehavior and its (bad) effects.\n\n Note that t 4074 delivery nested-reference unchanged"},{"id":"IETF RFC 4185","type":"specification","body":"IETF","designation":"RFC 4185","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4185.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4185.txt","https://www.rfc-editor.org/rfc/rfc4185.pdf"],"folder":"IETF/RFC-4185","files":{"txt":{"path":"standards/IETF/RFC-4185/RFC-4185.txt","sha256":"ba34e372b73034055d3510ebb1ff78ce0806f0c8efbc16677abd537842cb5a44"}},"tags":["nested-reference","unchanged"],"summary":"In the context of work on internationalizing the Domain Name System\n (DNS), there have been extensive discussions about \"multilingual\" or\n \"internationalized\" top level domain names (TLDs), especially for\n countries whose predominant language is not written in a Roman-based\n script. This document reviews some of the motivations for such\n domains, several suggestions that have been made to provide needed\n functionality, and the constraints that the DNS imposes. It then\n suggests an alternative, local translation, that may solve a superset\n of the problem while avoiding protocol changes, serious deployment\n delays, and other difficulties. The suggestion utilizes a\n localization technique in applications to permit any TLD to be\n accessed using the vocabulary and characters of any language. It is\n not restricted to language- or country-specific \"multilingual\" TLDs\n in the language(s) and scr","scope_keywords":["4185","key","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null}],"search_text":"IETF RFC 4185 In the context of work on internationalizing the Domain Name System\n (DNS), there have been extensive discussions about \"multilingual\" or\n \"internationalized\" top level domain names (TLDs), especially for\n countries whose predominant language is not written in a Roman-based\n script. This document reviews some of the motivations for such\n domains, several suggestions that have been made to provide needed\n functionality, and the constraints that the DNS imposes. It then\n suggests an alternative, local translation, that may solve a superset\n of the problem while avoiding protocol changes, serious deployment\n delays, and other difficulties. The suggestion utilizes a\n localization technique in applications to permit any TLD to be\n accessed using the vocabulary and characters of any language. It is\n not restricted to language- or country-specific \"multilingual\" TLDs\n in the language(s) and scr 4185 key pid presentation nested-reference unchanged"},{"id":"IETF RFC 4192","type":"specification","body":"IETF","designation":"RFC 4192","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4192.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4192.txt","https://www.rfc-editor.org/rfc/rfc4192.pdf"],"folder":"IETF/RFC-4192","files":{"txt":{"path":"standards/IETF/RFC-4192/RFC-4192.txt","sha256":"1c096ccbfae7121d990438e8d0ae63300fd2053beb161ae942977b0108b78981"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a procedure that can be used to renumber a\n network from one prefix to another. It uses IPv6's intrinsic ability\n to assign multiple addresses to a network interface to provide\n continuity of network service through a \"make-before-break\"\n transition, as well as addresses naming and configuration management\n issues. It also uses other IPv6 features to minimize the effort and\n time required to complete the transition from the old prefix to the\n new prefix.\n\nBaker, et al. Informational [Page 1]\n\f\nRFC 4192 Renumbering IPv6 Networks September 2005","scope_keywords":["4192","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null},{"body":"IETF","designation":"RFC 5142","folder":"IETF/RFC-5142","source":"IETF/RFC-5142/RFC-5142.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null}],"search_text":"IETF RFC 4192 This document describes a procedure that can be used to renumber a\n network from one prefix to another. It uses IPv6's intrinsic ability\n to assign multiple addresses to a network interface to provide\n continuity of network service through a \"make-before-break\"\n transition, as well as addresses naming and configuration management\n issues. It also uses other IPv6 features to minimize the effort and\n time required to complete the transition from the old prefix to the\n new prefix.\n\nBaker, et al. Informational [Page 1]\n\f\nRFC 4192 Renumbering IPv6 Networks September 2005 4192 key management nested-reference unchanged"},{"id":"IETF RFC 4255","type":"specification","body":"IETF","designation":"RFC 4255","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4255.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4255.txt","https://www.rfc-editor.org/rfc/rfc4255.pdf"],"folder":"IETF/RFC-4255","files":{"txt":{"path":"standards/IETF/RFC-4255/RFC-4255.txt","sha256":"c5eff6e6b9375f14cf82b34941d2495a6667f5a5cc6a74c57f619ac57003e5aa"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method of verifying Secure Shell (SSH) host\n keys using Domain Name System Security (DNSSEC). The document\n defines a new DNS resource record that contains a standard SSH key\n fingerprint.","scope_keywords":["4255","algorithm","authentication","key","keys","path","policy","presentation","qualified","signature","signatures","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null}],"search_text":"IETF RFC 4255 This document describes a method of verifying Secure Shell (SSH) host\n keys using Domain Name System Security (DNSSEC). The document\n defines a new DNS resource record that contains a standard SSH key\n fingerprint. 4255 algorithm authentication key keys path policy presentation qualified signature signatures trust validation nested-reference unchanged"},{"id":"IETF RFC 4294","type":"specification","body":"IETF","designation":"RFC 4294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4294.txt","https://www.rfc-editor.org/rfc/rfc4294.pdf"],"folder":"IETF/RFC-4294","files":{"txt":{"path":"standards/IETF/RFC-4294/RFC-4294.txt","sha256":"6372f6d3a0973d41c12618cfc145785aaa374804005ae29b71e5223c7db440d2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines requirements for IPv6 nodes. It is expected\n that IPv6 will be deployed in a wide range of devices and situations.\n Specifying the requirements for IPv6 nodes allows IPv6 to function\n well and interoperate in a large number of situations and\n deployments.","scope_keywords":["4294","algorithm","algorithms","authentication","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 4294 This document defines requirements for IPv6 nodes. It is expected\n that IPv6 will be deployed in a wide range of devices and situations.\n Specifying the requirements for IPv6 nodes allows IPv6 to function\n well and interoperate in a large number of situations and\n deployments. 4294 algorithm algorithms authentication key management path nested-reference unchanged"},{"id":"IETF RFC 4310","type":"specification","body":"IETF","designation":"RFC 4310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4310.txt","https://www.rfc-editor.org/rfc/rfc4310.pdf"],"folder":"IETF/RFC-4310","files":{"txt":{"path":"standards/IETF/RFC-4310/RFC-4310.txt","sha256":"82459fbfb999f54c90fb6b327b87e5a87ee912a8ff697a6d7106fcc9c7f85a01"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n extension mapping for the provisioning and management of Domain Name\n System security extensions (DNSSEC) for domain names stored in a\n shared central repository. Specified in XML, this mapping extends\n the EPP domain name mapping to provide additional features required\n for the provisioning of DNS security extensions.","scope_keywords":["4310","algorithm","attribute","attributes","key","management","presentation","registered","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null}],"search_text":"IETF RFC 4310 This document describes an Extensible Provisioning Protocol (EPP)\n extension mapping for the provisioning and management of Domain Name\n System security extensions (DNSSEC) for domain names stored in a\n shared central repository. Specified in XML, this mapping extends\n the EPP domain name mapping to provide additional features required\n for the provisioning of DNS security extensions. 4310 algorithm attribute attributes key management presentation registered signature nested-reference unchanged"},{"id":"IETF RFC 4343","type":"specification","body":"IETF","designation":"RFC 4343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4343.txt","https://www.rfc-editor.org/rfc/rfc4343.pdf"],"folder":"IETF/RFC-4343","files":{"txt":{"path":"standards/IETF/RFC-4343/RFC-4343.txt","sha256":"bebb8037e4bc6da9ad6691cf2aa2eb955852684c839d8f7dae311683292c1100"}},"tags":["nested-reference","unchanged"],"summary":"Domain Name System (DNS) names are \"case insensitive\". This document\n explains exactly what that means and provides a clear specification\n of the rules. This clarification updates RFCs 1034, 1035, and 2181.","scope_keywords":["4343","key","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 4343 Domain Name System (DNS) names are \"case insensitive\". This document\n explains exactly what that means and provides a clear specification\n of the rules. This clarification updates RFCs 1034, 1035, and 2181. 4343 key preservation nested-reference unchanged"},{"id":"IETF RFC 4367","type":"specification","body":"IETF","designation":"RFC 4367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4367.txt","https://www.rfc-editor.org/rfc/rfc4367.pdf"],"folder":"IETF/RFC-4367","files":{"txt":{"path":"standards/IETF/RFC-4367/RFC-4367.txt","sha256":"224915b1a06a4c5fa68c7184fa7c7435351bf8260e0c4c2f1681c6c5bc2f7d4e"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) provides an essential service on the\n Internet, mapping structured names to a variety of data, usually IP\n addresses. These names appear in email addresses, Uniform Resource\n Identifiers (URIs), and other application-layer identifiers that are\n often rendered to human users. Because of this, there has been a\n strong demand to acquire names that have significance to people,\n through equivalence to registered trademarks, company names, types of\n services, and so on. There is a danger in this trend; the humans and\n automata that consume and use such names will associate specific\n semantics with some names and thereby make assumptions about the\n services that are, or should be, provided by the hosts associated\n with the names. Those assumptions can often be false, resulting in a\n variety of failure conditions. This document discusses this problem\n in more detail ","scope_keywords":["4367","http","management","policy","registered","subject","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 4367 The Domain Name System (DNS) provides an essential service on the\n Internet, mapping structured names to a variety of data, usually IP\n addresses. These names appear in email addresses, Uniform Resource\n Identifiers (URIs), and other application-layer identifiers that are\n often rendered to human users. Because of this, there has been a\n strong demand to acquire names that have significance to people,\n through equivalence to registered trademarks, company names, types of\n services, and so on. There is a danger in this trend; the humans and\n automata that consume and use such names will associate specific\n semantics with some names and thereby make assumptions about the\n services that are, or should be, provided by the hosts associated\n with the names. Those assumptions can often be false, resulting in a\n variety of failure conditions. This document discusses this problem\n in more detail  4367 http management policy registered subject tsp nested-reference unchanged"},{"id":"IETF RFC 4398","type":"specification","body":"IETF","designation":"RFC 4398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4398.txt","https://www.rfc-editor.org/rfc/rfc4398.pdf"],"folder":"IETF/RFC-4398","files":{"txt":{"path":"standards/IETF/RFC-4398/RFC-4398.txt","sha256":"a733bab9434a76c12e64e25e65d697dfed1ce3ed18b09814d8221c2baf73a316"}},"tags":["nested-reference","unchanged"],"summary":"Cryptographic public keys are frequently published, and their\n authenticity is demonstrated by certificates. A CERT resource record\n (RR) is defined so that such certificates and related certificate\n revocation lists can be stored in the Domain Name System (DNS).\n\n This document obsoletes RFC 2538.\n\nJosefsson Standards Track [Page 1]\n\f\nRFC 4398 Storing Certificates in the DNS February 2006","scope_keywords":["4398","algorithm","attribute","authorization","certificate","certificates","crl","issuer","key","keys","pki","presentation","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8078","folder":"IETF/RFC-8078","source":"IETF/RFC-8078/RFC-8078.txt","version":null}],"search_text":"IETF RFC 4398 Cryptographic public keys are frequently published, and their\n authenticity is demonstrated by certificates. A CERT resource record\n (RR) is defined so that such certificates and related certificate\n revocation lists can be stored in the Domain Name System (DNS).\n\n This document obsoletes RFC 2538.\n\nJosefsson Standards Track [Page 1]\n\f\nRFC 4398 Storing Certificates in the DNS February 2006 4398 algorithm attribute authorization certificate certificates crl issuer key keys pki presentation profile revocation signature nested-reference unchanged"},{"id":"IETF RFC 4408","type":"specification","body":"IETF","designation":"RFC 4408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4408.txt","https://www.rfc-editor.org/rfc/rfc4408.pdf"],"folder":"IETF/RFC-4408","files":{"txt":{"path":"standards/IETF/RFC-4408/RFC-4408.txt","sha256":"419579cd26d78d1626276bc31e0e15b629c6d64cc05f2eeef2e606269d3546d6"}},"tags":["nested-reference","unchanged"],"summary":"E-mail on the Internet can be forged in a number of ways. In\n particular, existing protocols place no restriction on what a sending\n host can use as the reverse-path of a message or the domain given on\n the SMTP HELO/EHLO commands. This document describes version 1 of\n the Sender Policy Framework (SPF) protocol, whereby a domain may\n explicitly authorize the hosts that are allowed to use its domain\n name, and a receiving host may check such authorization.","scope_keywords":["4408","authorization","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 4408 E-mail on the Internet can be forged in a number of ways. In\n particular, existing protocols place no restriction on what a sending\n host can use as the reverse-path of a message or the domain given on\n the SMTP HELO/EHLO commands. This document describes version 1 of\n the Sender Policy Framework (SPF) protocol, whereby a domain may\n explicitly authorize the hosts that are allowed to use its domain\n name, and a receiving host may check such authorization. 4408 authorization path policy nested-reference unchanged"},{"id":"IETF RFC 4472","type":"specification","body":"IETF","designation":"RFC 4472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4472.txt","https://www.rfc-editor.org/rfc/rfc4472.pdf"],"folder":"IETF/RFC-4472","files":{"txt":{"path":"standards/IETF/RFC-4472/RFC-4472.txt","sha256":"de466f80d4ae2bab183fdf710540bfa8924932d4dd7010b82cb6dac39c69660f"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents operational considerations and issues with IPv6\n Domain Name System (DNS), including a summary of special IPv6\n addresses, documentation of known DNS implementation misbehavior,\n recommendations and considerations on how to perform DNS naming for\n service provisioning and for DNS resolver IPv6 support,\n considerations for DNS updates for both the forward and reverse\n trees, and miscellaneous issues. This memo is aimed to include a\n summary of information about IPv6 DNS considerations for those who\n have experience with IPv4 DNS.","scope_keywords":["4472"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null}],"search_text":"IETF RFC 4472 This memo presents operational considerations and issues with IPv6\n Domain Name System (DNS), including a summary of special IPv6\n addresses, documentation of known DNS implementation misbehavior,\n recommendations and considerations on how to perform DNS naming for\n service provisioning and for DNS resolver IPv6 support,\n considerations for DNS updates for both the forward and reverse\n trees, and miscellaneous issues. This memo is aimed to include a\n summary of information about IPv6 DNS considerations for those who\n have experience with IPv4 DNS. 4472 nested-reference unchanged"},{"id":"IETF RFC 4501","type":"specification","body":"IETF","designation":"RFC 4501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4501.txt","https://www.rfc-editor.org/rfc/rfc4501.pdf"],"folder":"IETF/RFC-4501","files":{"txt":{"path":"standards/IETF/RFC-4501/RFC-4501.txt","sha256":"dbaa606476f87f28e5eeba4d2fd8c59ca5fcad0aca13463654e40839cd32905a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Uniform Resource Identifiers for Domain Name\n System resources.","scope_keywords":["4501","key","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null}],"search_text":"IETF RFC 4501 This document defines Uniform Resource Identifiers for Domain Name\n System resources. 4501 key presentation registered nested-reference unchanged"},{"id":"IETF RFC 4519","type":"specification","body":"IETF","designation":"RFC 4519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4519.txt","https://www.rfc-editor.org/rfc/rfc4519.pdf"],"folder":"IETF/RFC-4519","files":{"txt":{"path":"standards/IETF/RFC-4519/RFC-4519.txt","sha256":"cd5a4bd06a1c374939cedb607d409be24e18383d948eabd098b88752d4e6ab77"}},"tags":["nested-reference","unchanged"],"summary":"This document is an integral part of the Lightweight Directory Access\n Protocol (LDAP) technical specification. It provides a technical\n specification of attribute types and object classes intended for use\n by LDAP directory clients for many directory services, such as White\n Pages. These objects are widely used as a basis for the schema in\n many LDAP directories. This document does not cover attributes used\n for the administration of directory servers, nor does it include\n directory objects defined for specific uses in other documents.\n\nSciberras Standards Track [Page 1]\n\f\nRFC 4519 LDAP: Schema for User Applications June 2006","scope_keywords":["4519","attribute","attributes","delivery","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.2.1","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"IETF RFC 4519 This document is an integral part of the Lightweight Directory Access\n Protocol (LDAP) technical specification. It provides a technical\n specification of attribute types and object classes intended for use\n by LDAP directory clients for many directory services, such as White\n Pages. These objects are widely used as a basis for the schema in\n many LDAP directories. This document does not cover attributes used\n for the administration of directory servers, nor does it include\n directory objects defined for specific uses in other documents.\n\nSciberras Standards Track [Page 1]\n\f\nRFC 4519 LDAP: Schema for User Applications June 2006 4519 attribute attributes delivery registered nested-reference unchanged"},{"id":"IETF RFC 4524","type":"specification","body":"IETF","designation":"RFC 4524","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4524.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4524.txt","https://www.rfc-editor.org/rfc/rfc4524.pdf"],"folder":"IETF/RFC-4524","files":{"txt":{"path":"standards/IETF/RFC-4524/RFC-4524.txt","sha256":"3e2c263999cf2ca7dee1d0f3e5090636fd9a4b8e402974dfb329d9e4b90fa7e3"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a collection of schema elements for use with\n the Lightweight Directory Access Protocol (LDAP) from the COSINE and\n Internet X.500 pilot projects.\n\n This document obsoletes RFC 1274 and updates RFCs 2247 and 2798.","scope_keywords":["4524","attribute"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null}],"search_text":"IETF RFC 4524 This document provides a collection of schema elements for use with\n the Lightweight Directory Access Protocol (LDAP) from the COSINE and\n Internet X.500 pilot projects.\n\n This document obsoletes RFC 1274 and updates RFCs 2247 and 2798. 4524 attribute nested-reference unchanged"},{"id":"IETF RFC 4566","type":"specification","body":"IETF","designation":"RFC 4566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4566.txt","https://www.rfc-editor.org/rfc/rfc4566.pdf"],"folder":"IETF/RFC-4566","files":{"txt":{"path":"standards/IETF/RFC-4566/RFC-4566.txt","sha256":"3934e9a7476f37489285947e475ef472959391efab7fa4247dcb3233899c1c29"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Session Description Protocol (SDP). SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation.","scope_keywords":["4566","attribute","attributes","encryption","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 4756","folder":"IETF/RFC-4756","source":"IETF/RFC-4756/RFC-4756.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5159","folder":"IETF/RFC-5159","source":"IETF/RFC-5159/RFC-5159.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 4566 This memo defines the Session Description Protocol (SDP). SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation. 4566 attribute attributes encryption key keys presentation nested-reference unchanged"},{"id":"IETF RFC 4592","type":"specification","body":"IETF","designation":"RFC 4592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4592.txt","https://www.rfc-editor.org/rfc/rfc4592.pdf"],"folder":"IETF/RFC-4592","files":{"txt":{"path":"standards/IETF/RFC-4592/RFC-4592.txt","sha256":"69bf6d3d435324a24747807106b5b4050c1f15e9f9fb8e0b67f3ab13d22f98bc"}},"tags":["nested-reference","unchanged"],"summary":"This is an update to the wildcard definition of RFC 1034. The\n interaction with wildcards and CNAME is changed, an error condition\n is removed, and the words defining some concepts central to wildcards\n are changed. The overall goal is not to change wildcards, but to\n refine the definition of RFC 1034.\n\nLewis Standards Track [Page 1]\n\f\nRFC 4592 DNSEXT WCARD July 2006","scope_keywords":["4592","algorithm","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 4592 This is an update to the wildcard definition of RFC 1034. The\n interaction with wildcards and CNAME is changed, an error condition\n is removed, and the words defining some concepts central to wildcards\n are changed. The overall goal is not to change wildcards, but to\n refine the definition of RFC 1034.\n\nLewis Standards Track [Page 1]\n\f\nRFC 4592 DNSEXT WCARD July 2006 4592 algorithm risk nested-reference unchanged"},{"id":"IETF RFC 4620","type":"specification","body":"IETF","designation":"RFC 4620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4620.txt","https://www.rfc-editor.org/rfc/rfc4620.pdf"],"folder":"IETF/RFC-4620","files":{"txt":{"path":"standards/IETF/RFC-4620/RFC-4620.txt","sha256":"e26b5fc10fccb79ce674e93f976cd5a8878389f76cbb4e488cfc893c43f4f74c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for asking an IPv6 node to supply\n certain network information, such as its hostname or fully-qualified\n domain name. IPv6 implementation experience has shown that direct\n queries for a hostname are useful, and a direct query mechanism for\n other information has been found useful in serverless environments\n and for debugging.","scope_keywords":["4620","http","key","management","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null}],"search_text":"IETF RFC 4620 This document describes a protocol for asking an IPv6 node to supply\n certain network information, such as its hostname or fully-qualified\n domain name. IPv6 implementation experience has shown that direct\n queries for a hostname are useful, and a direct query mechanism for\n other information has been found useful in serverless environments\n and for debugging. 4620 http key management qualified subject nested-reference unchanged"},{"id":"IETF RFC 4635","type":"specification","body":"IETF","designation":"RFC 4635","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4635.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4635.txt","https://www.rfc-editor.org/rfc/rfc4635.pdf"],"folder":"IETF/RFC-4635","files":{"txt":{"path":"standards/IETF/RFC-4635/RFC-4635.txt","sha256":"8223e63a958010fdc47ff12eb9bc7bf5da3e69119ab397ea1b1dc9d18a98cd3a"}},"tags":["nested-reference","unchanged"],"summary":"Use of the Domain Name System TSIG resource record requires\n specification of a cryptographic message authentication code.\n Currently, identifiers have been specified only for HMAC MD5 (Hashed\n Message Authentication Code, Message Digest 5) and GSS (Generic\n Security Service) TSIG algorithms. This document standardizes\n identifiers and implementation requirements for additional HMAC SHA\n (Secure Hash Algorithm) TSIG algorithms and standardizes how to\n specify and handle the truncation of HMAC values in TSIG.","scope_keywords":["4635","algorithm","algorithms","authentication","hash","key","policy","registered","signature","signatures","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 4635 Use of the Domain Name System TSIG resource record requires\n specification of a cryptographic message authentication code.\n Currently, identifiers have been specified only for HMAC MD5 (Hashed\n Message Authentication Code, Message Digest 5) and GSS (Generic\n Security Service) TSIG algorithms. This document standardizes\n identifiers and implementation requirements for additional HMAC SHA\n (Secure Hash Algorithm) TSIG algorithms and standardizes how to\n specify and handle the truncation of HMAC values in TSIG. 4635 algorithm algorithms authentication hash key policy registered signature signatures subject tls nested-reference unchanged"},{"id":"IETF RFC 4641","type":"specification","body":"IETF","designation":"RFC 4641","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4641.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4641.txt","https://www.rfc-editor.org/rfc/rfc4641.pdf"],"folder":"IETF/RFC-4641","files":{"txt":{"path":"standards/IETF/RFC-4641/RFC-4641.txt","sha256":"9d41befd1689b3f4c65874c8aec75e83516054f1861a543b08b11bdc78d6465b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of practices for operating the DNS with\n security extensions (DNSSEC). The target audience is zone\n administrators deploying DNSSEC.\n\n The document discusses operational aspects of using keys and\n signatures in the DNS. It discusses issues of key generation, key\n storage, signature generation, key rollover, and related policies.\n\n This document obsoletes RFC 2541, as it covers more operational\n ground and gives more up-to-date requirements with respect to key\n sizes and the new DNSSEC specification.\n\nKolkman & Gieben Informational [Page 1]\n\f\nRFC 4641 DNSSEC Operational Practices September 2006","scope_keywords":["4641","algorithm","algorithms","hash","key","keys","policies","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4641 This document describes a set of practices for operating the DNS with\n security extensions (DNSSEC). The target audience is zone\n administrators deploying DNSSEC.\n\n The document discusses operational aspects of using keys and\n signatures in the DNS. It discusses issues of key generation, key\n storage, signature generation, key rollover, and related policies.\n\n This document obsoletes RFC 2541, as it covers more operational\n ground and gives more up-to-date requirements with respect to key\n sizes and the new DNSSEC specification.\n\nKolkman & Gieben Informational [Page 1]\n\f\nRFC 4641 DNSSEC Operational Practices September 2006 4641 algorithm algorithms hash key keys policies signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 4681","type":"specification","body":"IETF","designation":"RFC 4681","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4681.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4681.txt","https://www.rfc-editor.org/rfc/rfc4681.pdf"],"folder":"IETF/RFC-4681","files":{"txt":{"path":"standards/IETF/RFC-4681/RFC-4681.txt","sha256":"0ef35df7bea096f3d478daafe880c74078939f9ab90919b8e0c83d8ab61cfa61"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a TLS extension that enables clients to send\n generic user mapping hints in a supplemental data handshake message\n defined in RFC 4680. One such mapping hint is defined in an\n informative section, the UpnDomainHint, which may be used by a server\n to locate a user in a directory database. Other mapping hints may be\n defined in other documents in the future.","scope_keywords":["4681","authentication","certificate","credential","credentials","key","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4681 This document specifies a TLS extension that enables clients to send\n generic user mapping hints in a supplemental data handshake message\n defined in RFC 4680. One such mapping hint is defined in an\n informative section, the UpnDomainHint, which may be used by a server\n to locate a user in a directory database. Other mapping hints may be\n defined in other documents in the future. 4681 authentication certificate credential credentials key presentation tls nested-reference unchanged"},{"id":"IETF RFC 4697","type":"specification","body":"IETF","designation":"RFC 4697","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4697.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4697.txt","https://www.rfc-editor.org/rfc/rfc4697.pdf"],"folder":"IETF/RFC-4697","files":{"txt":{"path":"standards/IETF/RFC-4697/RFC-4697.txt","sha256":"695e7bb206ce9f768ab39c864d946d94993b3bc205ddb62557081c47a8a22e7f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes DNS iterative resolver behavior that results in a\n significant query volume sent to the root and top-level domain (TLD)\n name servers. We offer implementation advice to iterative resolver\n developers to alleviate these unnecessary queries. The\n recommendations made in this document are a direct byproduct of\n observation and analysis of abnormal query traffic patterns seen at\n two of the thirteen root name servers and all thirteen com/net TLD\n name servers.","scope_keywords":["4697","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4697 This memo describes DNS iterative resolver behavior that results in a\n significant query volume sent to the root and top-level domain (TLD)\n name servers. We offer implementation advice to iterative resolver\n developers to alleviate these unnecessary queries. The\n recommendations made in this document are a direct byproduct of\n observation and analysis of abnormal query traffic patterns seen at\n two of the thirteen root name servers and all thirteen com/net TLD\n name servers. 4697 algorithm key nested-reference unchanged"},{"id":"IETF RFC 4701","type":"specification","body":"IETF","designation":"RFC 4701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4701.txt","https://www.rfc-editor.org/rfc/rfc4701.pdf"],"folder":"IETF/RFC-4701","files":{"txt":{"path":"standards/IETF/RFC-4701/RFC-4701.txt","sha256":"beb67fbfbb513dcc71d8b4af7f5cf3a07ec2387fb30aa08fef67287e74fa4628"}},"tags":["nested-reference","unchanged"],"summary":"It is possible for Dynamic Host Configuration Protocol (DHCP) clients\n to attempt to update the same DNS Fully Qualified Domain Name (FQDN)\n or to update a DNS FQDN that has been added to the DNS for another\n purpose as they obtain DHCP leases. Whether the DHCP server or the\n clients themselves perform the DNS updates, conflicts can arise. To\n resolve such conflicts, RFC 4703 proposes storing client identifiers\n in the DNS to unambiguously associate domain names with the DHCP\n clients to which they refer. This memo defines a distinct Resource\n Record (RR) type for this purpose for use by DHCP clients and\n servers: the \"DHCID\" RR.\n\nStapp, et al. Standards Track [Page 1]\n\f\nRFC 4701 The DHCID RR October 2006","scope_keywords":["4701","hash","identification","key","presentation","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null}],"search_text":"IETF RFC 4701 It is possible for Dynamic Host Configuration Protocol (DHCP) clients\n to attempt to update the same DNS Fully Qualified Domain Name (FQDN)\n or to update a DNS FQDN that has been added to the DNS for another\n purpose as they obtain DHCP leases. Whether the DHCP server or the\n clients themselves perform the DNS updates, conflicts can arise. To\n resolve such conflicts, RFC 4703 proposes storing client identifiers\n in the DNS to unambiguously associate domain names with the DHCP\n clients to which they refer. This memo defines a distinct Resource\n Record (RR) type for this purpose for use by DHCP clients and\n servers: the \"DHCID\" RR.\n\nStapp, et al. Standards Track [Page 1]\n\f\nRFC 4701 The DHCID RR October 2006 4701 hash identification key presentation qualified nested-reference unchanged"},{"id":"IETF RFC 4702","type":"specification","body":"IETF","designation":"RFC 4702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4702.txt","https://www.rfc-editor.org/rfc/rfc4702.pdf"],"folder":"IETF/RFC-4702","files":{"txt":{"path":"standards/IETF/RFC-4702/RFC-4702.txt","sha256":"061fa042c6ebe7514d4d45dc44c4f9a87c012c0da2a93125849953f4e4d8fdfe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Dynamic Host Configuration Protocol for\n IPv4 (DHCPv4) option that can be used to exchange information about a\n DHCPv4 client's fully qualified domain name and about responsibility\n for updating the DNS RR related to the client's address assignment.\n\nStapp, et al. Standards Track [Page 1]\n\f\nRFC 4702 The DHCP Client FQDN Option October 2006","scope_keywords":["4702","key","policy","qualified","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null}],"search_text":"IETF RFC 4702 This document describes a Dynamic Host Configuration Protocol for\n IPv4 (DHCPv4) option that can be used to exchange information about a\n DHCPv4 client's fully qualified domain name and about responsibility\n for updating the DNS RR related to the client's address assignment.\n\nStapp, et al. Standards Track [Page 1]\n\f\nRFC 4702 The DHCP Client FQDN Option October 2006 4702 key policy qualified tls nested-reference unchanged"},{"id":"IETF RFC 4704","type":"specification","body":"IETF","designation":"RFC 4704","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4704.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4704.txt","https://www.rfc-editor.org/rfc/rfc4704.pdf"],"folder":"IETF/RFC-4704","files":{"txt":{"path":"standards/IETF/RFC-4704/RFC-4704.txt","sha256":"7478df9ab2fb0c4f402fb7521664fef0c07b6c043c1663fc86ab51b6e257b27d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) option that can be used to exchange information about a\n DHCPv6 client's Fully Qualified Domain Name (FQDN) and about\n responsibility for updating DNS resource records (RRs) related to the\n client's address assignments.\n\nVolz Standards Track [Page 1]\n\f\nRFC 4704 The DHCPv6 Client FQDN Option October 2006","scope_keywords":["4704","credential","credentials","key","policies","policy","qualified","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 4704 This document specifies a new Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) option that can be used to exchange information about a\n DHCPv6 client's Fully Qualified Domain Name (FQDN) and about\n responsibility for updating DNS resource records (RRs) related to the\n client's address assignments.\n\nVolz Standards Track [Page 1]\n\f\nRFC 4704 The DHCPv6 Client FQDN Option October 2006 4704 credential credentials key policies policy qualified tls nested-reference unchanged"},{"id":"IETF RFC 4892","type":"specification","body":"IETF","designation":"RFC 4892","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4892.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4892.txt","https://www.rfc-editor.org/rfc/rfc4892.pdf"],"folder":"IETF/RFC-4892","files":{"txt":{"path":"standards/IETF/RFC-4892/RFC-4892.txt","sha256":"1a970e16783e4d86600226eaea05cbee644b66c906ad8ce207ff7164f59dafa4"}},"tags":["nested-reference","unchanged"],"summary":"With the increased use of DNS anycast, load balancing, and other\n mechanisms allowing more than one DNS name server to share a single\n IP address, it is sometimes difficult to tell which of a pool of name\n servers has answered a particular query. A standardized mechanism to\n determine the identity of a name server responding to a particular\n query would be useful, particularly as a diagnostic aid for\n administrators. Existing ad hoc mechanisms for addressing this need\n have some shortcomings, not the least of which is the lack of prior\n analysis of exactly how such a mechanism should be designed and\n deployed. This document describes the existing convention used in\n some widely deployed implementations of the DNS protocol, including\n advantages and disadvantages, and discusses some attributes of an\n improved mechanism.\n\n1. Introduction and Rationale\n\n Identifying which name server is res","scope_keywords":["4892","attribute","attributes","identification","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 4892 With the increased use of DNS anycast, load balancing, and other\n mechanisms allowing more than one DNS name server to share a single\n IP address, it is sometimes difficult to tell which of a pool of name\n servers has answered a particular query. A standardized mechanism to\n determine the identity of a name server responding to a particular\n query would be useful, particularly as a diagnostic aid for\n administrators. Existing ad hoc mechanisms for addressing this need\n have some shortcomings, not the least of which is the lack of prior\n analysis of exactly how such a mechanism should be designed and\n deployed. This document describes the existing convention used in\n some widely deployed implementations of the DNS protocol, including\n advantages and disadvantages, and discusses some attributes of an\n improved mechanism.\n\n1. Introduction and Rationale\n\n Identifying which name server is res 4892 attribute attributes identification path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 4985","type":"specification","body":"IETF","designation":"RFC 4985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4985.txt","https://www.rfc-editor.org/rfc/rfc4985.pdf"],"folder":"IETF/RFC-4985","files":{"txt":{"path":"standards/IETF/RFC-4985/RFC-4985.txt","sha256":"526b212d9fb6ccd588ad1fbb2b91e5d720b137ee65e5147733b8b3c57fb7f862"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new name form for inclusion in the otherName\n field of an X.509 Subject Alternative Name extension that allows a\n certificate subject to be associated with the service name and domain\n name components of a DNS Service Resource Record.","scope_keywords":["4985","authentication","authorization","certificate","certificates","credential","credentials","key","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 4985 This document defines a new name form for inclusion in the otherName\n field of an X.509 Subject Alternative Name extension that allows a\n certificate subject to be associated with the service name and domain\n name components of a DNS Service Resource Record. 4985 authentication authorization certificate certificates credential credentials key policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5155","type":"specification","body":"IETF","designation":"RFC 5155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5155.txt","https://www.rfc-editor.org/rfc/rfc5155.pdf"],"folder":"IETF/RFC-5155","files":{"txt":{"path":"standards/IETF/RFC-5155/RFC-5155.txt","sha256":"c3083458ed7ef69360397a7a6ec44374b245e4e5a03725c834c54908cb7f77ff"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System Security (DNSSEC) Extensions introduced the\n NSEC resource record (RR) for authenticated denial of existence.\n This document introduces an alternative resource record, NSEC3, which\n similarly provides authenticated denial of existence. However, it\n also provides measures against zone enumeration and permits gradual\n expansion of delegation-centric zones.","scope_keywords":["5155","algorithm","algorithms","hash","hashing","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5155 The Domain Name System Security (DNSSEC) Extensions introduced the\n NSEC resource record (RR) for authenticated denial of existence.\n This document introduces an alternative resource record, NSEC3, which\n similarly provides authenticated denial of existence. However, it\n also provides measures against zone enumeration and permits gradual\n expansion of delegation-centric zones. 5155 algorithm algorithms hash hashing presentation nested-reference unchanged"},{"id":"IETF RFC 5205","type":"specification","body":"IETF","designation":"RFC 5205","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5205.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5205.txt","https://www.rfc-editor.org/rfc/rfc5205.pdf"],"folder":"IETF/RFC-5205","files":{"txt":{"path":"standards/IETF/RFC-5205/RFC-5205.txt","sha256":"e2cdf06147495dd5f48929a9afad046a985e7ef5f3b6b01150c1206b5df41304"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new resource record (RR) for the Domain\n Name System (DNS), and how to use it with the Host Identity Protocol\n (HIP). This RR allows a HIP node to store in the DNS its Host\n Identity (HI, the public component of the node public-private key\n pair), Host Identity Tag (HIT, a truncated hash of its public key),\n and the Domain Names of its rendezvous servers (RVSs).\n\nNikander & Laganier Experimental [Page 1]\n\f\nRFC 5205 HIP DNS Extension April 2008","scope_keywords":["5205","algorithm","hash","key","presentation","qualified","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null}],"search_text":"IETF RFC 5205 This document specifies a new resource record (RR) for the Domain\n Name System (DNS), and how to use it with the Host Identity Protocol\n (HIP). This RR allows a HIP node to store in the DNS its Host\n Identity (HI, the public component of the node public-private key\n pair), Host Identity Tag (HIT, a truncated hash of its public key),\n and the Domain Names of its rendezvous servers (RVSs).\n\nNikander & Laganier Experimental [Page 1]\n\f\nRFC 5205 HIP DNS Extension April 2008 5205 algorithm hash key presentation qualified risk nested-reference unchanged"},{"id":"IETF RFC 5280","type":"specification","body":"IETF","designation":"RFC 5280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5280.txt","https://www.rfc-editor.org/rfc/rfc5280.pdf"],"folder":"IETF/RFC-5280","files":{"txt":{"path":"standards/IETF/RFC-5280/RFC-5280.txt","sha256":"a2f2628c0a83b873fc4786abd921f9b2c02395954b655d190bf16b831633345d"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This memo profiles the X.509 v3 certificate and X.509 v2 certificate\n revocation list (CRL) for use in the Internet. An overview of this\n approach and model is provided as an introduction. The X.509 v3\n certificate format is described in detail, with additional\n information regarding the format and semantics of Internet name\n forms. Standard certificate extensions are described and two\n Internet-specific extensions are defined. A set of required\n certificate extensions is specified. The X.509 v2 CRL format is\n described in detail along with standard and Internet-specific\n extensions. An algorithm for X.509 certification path validation is\n described. An ASN.1 module and examples are provided in the\n appendices.\n\nCooper, et al. Standards Track [Page 1]\n\f\nRFC 5280 PKIX Certificate and CRL Profile May 2008","scope_keywords":["5280","accreditation","algorithm","attribute","attributes","certificate","certificates","conformity","crl","issuer","key","management","path","pki","policies","policy"],"parent_legal_regulations":[{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 412-3","folder":"ETSI/EN-319-412-3-V1.3.1","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 411-8","folder":"ETSI/TS-119-411-8-V1.1.1","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5759","folder":"IETF/RFC-5759","source":"IETF/RFC-5759/RFC-5759.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 5280 This memo profiles the X.509 v3 certificate and X.509 v2 certificate\n revocation list (CRL) for use in the Internet. An overview of this\n approach and model is provided as an introduction. The X.509 v3\n certificate format is described in detail, with additional\n information regarding the format and semantics of Internet name\n forms. Standard certificate extensions are described and two\n Internet-specific extensions are defined. A set of required\n certificate extensions is specified. The X.509 v2 CRL format is\n described in detail along with standard and Internet-specific\n extensions. An algorithm for X.509 certification path validation is\n described. An ASN.1 module and examples are provided in the\n appendices.\n\nCooper, et al. Standards Track [Page 1]\n\f\nRFC 5280 PKIX Certificate and CRL Profile May 2008 5280 accreditation algorithm attribute attributes certificate certificates conformity crl issuer key management path pki policies policy cited-by-eu-law implementing-regulation nested-reference unchanged 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"IETF RFC 5295","type":"specification","body":"IETF","designation":"RFC 5295","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5295.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5295.txt","https://www.rfc-editor.org/rfc/rfc5295.pdf"],"folder":"IETF/RFC-5295","files":{"txt":{"path":"standards/IETF/RFC-5295/RFC-5295.txt","sha256":"f9729614858c809364c42f65c661dd11f0afca3b83f28cac5decc8e8596400e9"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) defined the Extended\n Master Session Key (EMSK) generation, but reserved it for unspecified\n future uses. This memo reserves the EMSK for the sole purpose of\n deriving root keys. Root keys are master keys that can be used for\n multiple purposes, identified by usage definitions. This document\n also specifies a mechanism for avoiding conflicts between root keys\n by deriving them in a manner that guarantees cryptographic\n separation. Finally, this document also defines one such root key\n usage: Domain-Specific Root Keys are root keys made available to and\n used within specific key management domains.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 5295 EMSK Root Key Derivation August 2008","scope_keywords":["5295","authentication","authorization","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 5295 The Extensible Authentication Protocol (EAP) defined the Extended\n Master Session Key (EMSK) generation, but reserved it for unspecified\n future uses. This memo reserves the EMSK for the sole purpose of\n deriving root keys. Root keys are master keys that can be used for\n multiple purposes, identified by usage definitions. This document\n also specifies a mechanism for avoiding conflicts between root keys\n by deriving them in a manner that guarantees cryptographic\n separation. Finally, this document also defines one such root key\n usage: Domain-Specific Root Keys are root keys made available to and\n used within specific key management domains.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 5295 EMSK Root Key Derivation August 2008 5295 authentication authorization key keys management nested-reference unchanged"},{"id":"IETF RFC 5358","type":"specification","body":"IETF","designation":"RFC 5358","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5358.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5358.txt","https://www.rfc-editor.org/rfc/rfc5358.pdf"],"folder":"IETF/RFC-5358","files":{"txt":{"path":"standards/IETF/RFC-5358/RFC-5358.txt","sha256":"8a36f76328a6e7c10f262c284d9e594b154f3346a7625b525856cc386a8e1161"}},"tags":["nested-reference","unchanged"],"summary":"This document describes ways to prevent the use of default configured\n recursive nameservers as reflectors in Denial of Service (DoS)\n attacks. It provides recommended configuration as measures to\n mitigate the attack.","scope_keywords":["5358","authorization","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5358 This document describes ways to prevent the use of default configured\n recursive nameservers as reflectors in Denial of Service (DoS)\n attacks. It provides recommended configuration as measures to\n mitigate the attack. 5358 authorization delivery key nested-reference unchanged"},{"id":"IETF RFC 5395","type":"specification","body":"IETF","designation":"RFC 5395","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5395.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5395.txt","https://www.rfc-editor.org/rfc/rfc5395.pdf"],"folder":"IETF/RFC-5395","files":{"txt":{"path":"standards/IETF/RFC-5395/RFC-5395.txt","sha256":"caf342f734483354698e4892f868d52f4a3bdf721608725062be6d741b31a49f"}},"tags":["nested-reference","unchanged"],"summary":"Internet Assigned Number Authority (IANA) parameter assignment\n considerations are specified for the allocation of Domain Name System\n (DNS) resource record types, CLASSes, operation codes, error codes,\n DNS protocol message header bits, and AFSDB resource record subtypes.\n\nEastlake Best Current Practice [Page 1]\n\f\nRFC 5395 DNS IANA Considerations November 2008","scope_keywords":["5395","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null}],"search_text":"IETF RFC 5395 Internet Assigned Number Authority (IANA) parameter assignment\n considerations are specified for the allocation of Domain Name System\n (DNS) resource record types, CLASSes, operation codes, error codes,\n DNS protocol message header bits, and AFSDB resource record subtypes.\n\nEastlake Best Current Practice [Page 1]\n\f\nRFC 5395 DNS IANA Considerations November 2008 5395 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5424","type":"specification","body":"IETF","designation":"RFC 5424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5424.txt","https://www.rfc-editor.org/rfc/rfc5424.pdf"],"folder":"IETF/RFC-5424","files":{"txt":{"path":"standards/IETF/RFC-5424/RFC-5424.txt","sha256":"24d91f90a05d2536730ada929c296f45ae9cd72226e22b6775ad8c04cae37a53"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the syslog protocol, which is used to convey\n event notification messages. This protocol utilizes a layered\n architecture, which allows the use of any number of transport\n protocols for transmission of syslog messages. It also provides a\n message format that allows vendor-specific extensions to be provided\n in a structured way.\n\n This document has been written with the original design goals for\n traditional syslog in mind. The need for a new layered specification\n has arisen because standardization efforts for reliable and secure\n syslog extensions suffer from the lack of a Standards-Track and\n transport-independent RFC. Without this document, each other\n standard needs to define its own syslog packet format and transport\n mechanism, which over time will introduce subtle compatibility\n issues. This document tries to provide a foundation that syslog\n extensions can","scope_keywords":["5424","delivery","http","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null}],"search_text":"IETF RFC 5424 This document describes the syslog protocol, which is used to convey\n event notification messages. This protocol utilizes a layered\n architecture, which allows the use of any number of transport\n protocols for transmission of syslog messages. It also provides a\n message format that allows vendor-specific extensions to be provided\n in a structured way.\n\n This document has been written with the original design goals for\n traditional syslog in mind. The need for a new layered specification\n has arisen because standardization efforts for reliable and secure\n syslog extensions suffer from the lack of a Standards-Track and\n transport-independent RFC. Without this document, each other\n standard needs to define its own syslog packet format and transport\n mechanism, which over time will introduce subtle compatibility\n issues. This document tries to provide a foundation that syslog\n extensions can 5424 delivery http license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5452","type":"specification","body":"IETF","designation":"RFC 5452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5452.txt","https://www.rfc-editor.org/rfc/rfc5452.pdf"],"folder":"IETF/RFC-5452","files":{"txt":{"path":"standards/IETF/RFC-5452/RFC-5452.txt","sha256":"53af0365af1c491204ae27b523699b7732f79cf606ce84fab3b032df7a966c6b"}},"tags":["nested-reference","unchanged"],"summary":"The current Internet climate poses serious threats to the Domain Name\n System. In the interim period before the DNS protocol can be secured\n more fully, measures can already be taken to harden the DNS to make\n 'spoofing' a recursing nameserver many orders of magnitude harder.\n\n Even a cryptographically secured DNS benefits from having the ability\n to discard bogus responses quickly, as this potentially saves large\n amounts of computation.\n\n By describing certain behavior that has previously not been\n standardized, this document sets out how to make the DNS more\n resilient against accepting incorrect responses. This document\n updates RFC 2181.\n\nHubert & van Mook Standards Track [Page 1]\n\f\nRFC 5452 DNS Resilience against Forged Answers January 2009","scope_keywords":["5452","certificate","certificates","http","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null}],"search_text":"IETF RFC 5452 The current Internet climate poses serious threats to the Domain Name\n System. In the interim period before the DNS protocol can be secured\n more fully, measures can already be taken to harden the DNS to make\n 'spoofing' a recursing nameserver many orders of magnitude harder.\n\n Even a cryptographically secured DNS benefits from having the ability\n to discard bogus responses quickly, as this potentially saves large\n amounts of computation.\n\n By describing certain behavior that has previously not been\n standardized, this document sets out how to make the DNS more\n resilient against accepting incorrect responses. This document\n updates RFC 2181.\n\nHubert & van Mook Standards Track [Page 1]\n\f\nRFC 5452 DNS Resilience against Forged Answers January 2009 5452 certificate certificates http key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5706","type":"specification","body":"IETF","designation":"RFC 5706","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5706.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5706.txt","https://www.rfc-editor.org/rfc/rfc5706.pdf"],"folder":"IETF/RFC-5706","files":{"txt":{"path":"standards/IETF/RFC-5706/RFC-5706.txt","sha256":"36da1501df9f384be4352f0ce6d103dd8cfcab460edecc6ac2d61d165325f97f"}},"tags":["nested-reference","unchanged"],"summary":"New protocols or protocol extensions are best designed with due\n consideration of the functionality needed to operate and manage the\n protocols. Retrofitting operations and management is sub-optimal.\n The purpose of this document is to provide guidance to authors and\n reviewers of documents that define new protocols or protocol\n extensions regarding aspects of operations and management that should\n be considered.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication ","scope_keywords":["5706","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 5706 New protocols or protocol extensions are best designed with due\n consideration of the functionality needed to operate and manage the\n protocols. Retrofitting operations and management is sub-optimal.\n The purpose of this document is to provide guidance to authors and\n reviewers of documents that define new protocols or protocol\n extensions regarding aspects of operations and management that should\n be considered.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication  5706 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5729","type":"specification","body":"IETF","designation":"RFC 5729","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5729.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5729.txt","https://www.rfc-editor.org/rfc/rfc5729.pdf"],"folder":"IETF/RFC-5729","files":{"txt":{"path":"standards/IETF/RFC-5729/RFC-5729.txt","sha256":"3a059766b126f2509fb9ec9d59f5b768e4f6d24fdba75f501a87832303cdd636"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the behavior required of Diameter agents\n to route requests when the User-Name Attribute Value Pair contains a\n Network Access Identifier formatted with multiple realms. These\n multi-realm, or \"Decorated\", Network Access Identifiers are used in\n order to force the routing of request messages through a predefined\n list of mediating realms.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the ","scope_keywords":["5729","attribute","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 5729 This specification defines the behavior required of Diameter agents\n to route requests when the User-Name Attribute Value Pair contains a\n Network Access Identifier formatted with multiple realms. These\n multi-realm, or \"Decorated\", Network Access Identifiers are used in\n order to force the routing of request messages through a predefined\n list of mediating realms.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the  5729 attribute authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5782","type":"specification","body":"IETF","designation":"RFC 5782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5782.txt","https://www.rfc-editor.org/rfc/rfc5782.pdf"],"folder":"IETF/RFC-5782","files":{"txt":{"path":"standards/IETF/RFC-5782/RFC-5782.txt","sha256":"c4c45b6a398da9cbc2d031c1b11355f4b60eb82efa6212b38caa48a896065608"}},"tags":["nested-reference","unchanged"],"summary":"The rise of spam and other anti-social behavior on the Internet has\n led to the creation of shared blacklists and whitelists of IP\n addresses or domains. The DNS has become the de-facto standard\n method of distributing these blacklists and whitelists. This memo\n documents the structure and usage of DNS-based blacklists and\n whitelists, and the protocol used to query them.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Anti-Spam\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidat","scope_keywords":["5782","http","key","license","management","policies","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 5782 The rise of spam and other anti-social behavior on the Internet has\n led to the creation of shared blacklists and whitelists of IP\n addresses or domains. The DNS has become the de-facto standard\n method of distributing these blacklists and whitelists. This memo\n documents the structure and usage of DNS-based blacklists and\n whitelists, and the protocol used to query them.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Anti-Spam\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidat 5782 http key license management policies presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5801","type":"specification","body":"IETF","designation":"RFC 5801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5801.txt","https://www.rfc-editor.org/rfc/rfc5801.pdf"],"folder":"IETF/RFC-5801","files":{"txt":{"path":"standards/IETF/RFC-5801/RFC-5801.txt","sha256":"873d2816559f1bb4283502e6d2c0dfdc2bcd4f857b6653a890479622c8ec8721"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use a Generic Security Service\n Application Program Interface (GSS-API) mechanism in the Simple\n Authentication and Security Layer (SASL) framework. This is done by\n defining a new SASL mechanism family, called GS2. This mechanism\n family offers a number of improvements over the previous \"SASL/\n GSSAPI\" mechanism: it is more general, uses fewer messages for the\n authentication phase in some cases, and supports negotiable use of\n channel binding. Only GSS-API mechanisms that support channel\n binding and mutual authentication are supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furthe","scope_keywords":["5801","authentication","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null}],"search_text":"IETF RFC 5801 This document describes how to use a Generic Security Service\n Application Program Interface (GSS-API) mechanism in the Simple\n Authentication and Security Layer (SASL) framework. This is done by\n defining a new SASL mechanism family, called GS2. This mechanism\n family offers a number of improvements over the previous \"SASL/\n GSSAPI\" mechanism: it is more general, uses fewer messages for the\n authentication phase in some cases, and supports negotiable use of\n channel binding. Only GSS-API mechanisms that support channel\n binding and mutual authentication are supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furthe 5801 authentication http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5855","type":"specification","body":"IETF","designation":"RFC 5855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5855.txt","https://www.rfc-editor.org/rfc/rfc5855.pdf"],"folder":"IETF/RFC-5855","files":{"txt":{"path":"standards/IETF/RFC-5855/RFC-5855.txt","sha256":"7624b07d78d5d8ea70c3bffc03c0489e0eb0c27549ee612ffa6797ea947b9471"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a stable naming scheme for the nameservers\n that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS. These\n zones contain data that facilitate reverse mapping (address to name).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5855.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume","scope_keywords":["5855","http","key","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5855 This document specifies a stable naming scheme for the nameservers\n that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS. These\n zones contain data that facilitate reverse mapping (address to name).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5855.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume 5855 http key license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5864","type":"specification","body":"IETF","designation":"RFC 5864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5864.txt","https://www.rfc-editor.org/rfc/rfc5864.pdf"],"folder":"IETF/RFC-5864","files":{"txt":{"path":"standards/IETF/RFC-5864/RFC-5864.txt","sha256":"4e438d41485ed1a4d125d0632cf9397ebf4c40ee23313c61e3ff05c6f3d5c46f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use DNS (Domain Name Service) SRV RRs\n (Resource Records) to locate services for the AFS distributed file\n system and how the priority and weight values of the SRV RR should be\n interpreted in the server ranking system used by AFS. It updates RFC\n 1183 to deprecate the use of the AFSDB RR to locate AFS cell database\n servers and provides guidance for backward compatibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["5864","http","key","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5864 This document specifies how to use DNS (Domain Name Service) SRV RRs\n (Resource Records) to locate services for the AFS distributed file\n system and how the priority and weight values of the SRV RR should be\n interpreted in the server ranking system used by AFS. It updates RFC\n 1183 to deprecate the use of the AFSDB RR to locate AFS cell database\n servers and provides guidance for backward compatibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 5864 http key license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5891","type":"specification","body":"IETF","designation":"RFC 5891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5891.txt","https://www.rfc-editor.org/rfc/rfc5891.pdf"],"folder":"IETF/RFC-5891","files":{"txt":{"path":"standards/IETF/RFC-5891/RFC-5891.txt","sha256":"c9b898f6214c2241b25e4697d6b928ea805099bb136f0e92c48a531490672cda"}},"tags":["nested-reference","unchanged"],"summary":"This document is the revised protocol definition for\n Internationalized Domain Names (IDNs). The rationale for changes,\n the relationship to the older specification, and important\n terminology are provided in other documents. This document specifies\n the protocol mechanism, called Internationalized Domain Names in\n Applications (IDNA), for registering and looking up IDNs in a way\n that does not require changes to the DNS itself. IDNA is only meant\n for processing domain names, not free text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n I","scope_keywords":["5891","http","key","license","qualified","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5893","folder":"IETF/RFC-5893","source":"IETF/RFC-5893/RFC-5893.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5895","folder":"IETF/RFC-5895","source":"IETF/RFC-5895/RFC-5895.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 5891 This document is the revised protocol definition for\n Internationalized Domain Names (IDNs). The rationale for changes,\n the relationship to the older specification, and important\n terminology are provided in other documents. This document specifies\n the protocol mechanism, called Internationalized Domain Names in\n Applications (IDNA), for registering and looking up IDNs in a way\n that does not require changes to the DNS itself. IDNA is only meant\n for processing domain names, not free text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n I 5891 http key license qualified subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5910","type":"specification","body":"IETF","designation":"RFC 5910","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5910.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5910.txt","https://www.rfc-editor.org/rfc/rfc5910.pdf"],"folder":"IETF/RFC-5910","files":{"txt":{"path":"standards/IETF/RFC-5910/RFC-5910.txt","sha256":"faaabe62a8b9f49b3315019f48b53ab16ad78354bffdbeb5a7b86ea771b0f24d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n extension mapping for the provisioning and management of Domain Name\n System security (DNSSEC) extensions for domain names stored in a\n shared central repository. Specified in XML, this mapping extends\n the EPP domain name mapping to provide additional features required\n for the provisioning of DNS security extensions. This document\n obsoletes RFC 4310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how","scope_keywords":["5910","attribute","attributes","http","key","license","management","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 5910 This document describes an Extensible Provisioning Protocol (EPP)\n extension mapping for the provisioning and management of Domain Name\n System security (DNSSEC) extensions for domain names stored in a\n shared central repository. Specified in XML, this mapping extends\n the EPP domain name mapping to provide additional features required\n for the provisioning of DNS security extensions. This document\n obsoletes RFC 4310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how 5910 attribute attributes http key license management signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6106","type":"specification","body":"IETF","designation":"RFC 6106","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6106.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6106.txt","https://www.rfc-editor.org/rfc/rfc6106.pdf"],"folder":"IETF/RFC-6106","files":{"txt":{"path":"standards/IETF/RFC-6106/RFC-6106.txt","sha256":"619a4ee23192a1d80c1f3ef7a0f4defbfd6b3aabca50365c9c0ba41bb8bf0eb1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies IPv6 Router Advertisement options to allow\n IPv6 routers to advertise a list of DNS recursive server addresses\n and a DNS Search List to IPv6 hosts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6106.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 an","scope_keywords":["6106","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 6106 This document specifies IPv6 Router Advertisement options to allow\n IPv6 routers to advertise a list of DNS recursive server addresses\n and a DNS Search List to IPv6 hosts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6106.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 an 6106 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6120","type":"specification","body":"IETF","designation":"RFC 6120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6120.txt","https://www.rfc-editor.org/rfc/rfc6120.pdf"],"folder":"IETF/RFC-6120","files":{"txt":{"path":"standards/IETF/RFC-6120/RFC-6120.txt","sha256":"a64e922cba1b4b69bfc96192e59692efdb296c828800870ffb35c1fb7aad2ee8"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Messaging and Presence Protocol (XMPP) is an\n application profile of the Extensible Markup Language (XML) that\n enables the near-real-time exchange of structured yet extensible data\n between any two or more network entities. This document defines\n XMPP's core protocol methods: setup and teardown of XML streams,\n channel encryption, authentication, error handling, and communication\n primitives for messaging, network availability (\"presence\"), and\n request-response interactions. This document obsoletes RFC 3920.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avail","scope_keywords":["6120","attribute","attributes","authentication","encryption","http","license","policy","profile","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8073","folder":"IETF/RFC-8073","source":"IETF/RFC-8073/RFC-8073.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 6120 The Extensible Messaging and Presence Protocol (XMPP) is an\n application profile of the Extensible Markup Language (XML) that\n enables the near-real-time exchange of structured yet extensible data\n between any two or more network entities. This document defines\n XMPP's core protocol methods: setup and teardown of XML streams,\n channel encryption, authentication, error handling, and communication\n primitives for messaging, network availability (\"presence\"), and\n request-response interactions. This document obsoletes RFC 3920.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avail 6120 attribute attributes authentication encryption http license policy profile qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6125","type":"specification","body":"IETF","designation":"RFC 6125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6125.txt","https://www.rfc-editor.org/rfc/rfc6125.pdf"],"folder":"IETF/RFC-6125","files":{"txt":{"path":"standards/IETF/RFC-6125/RFC-6125.txt","sha256":"ee1f413f420bfa6199302b1a85669243f27076c803a120d55c15198e300d7cf1"}},"tags":["nested-reference","unchanged"],"summary":"Many application technologies enable secure communication between two\n entities by means of Internet Public Key Infrastructure Using X.509\n (PKIX) certificates in the context of Transport Layer Security (TLS).\n This document specifies procedures for representing and verifying the\n identity of application services in such interactions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6125.","scope_keywords":["6125","certificate","certificates","http","key","license","pki","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 6125 Many application technologies enable secure communication between two\n entities by means of Internet Public Key Infrastructure Using X.509\n (PKIX) certificates in the context of Transport Layer Security (TLS).\n This document specifies procedures for representing and verifying the\n identity of application services in such interactions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6125. 6125 certificate certificates http key license pki presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6147","type":"specification","body":"IETF","designation":"RFC 6147","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6147.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6147.txt","https://www.rfc-editor.org/rfc/rfc6147.pdf"],"folder":"IETF/RFC-6147","files":{"txt":{"path":"standards/IETF/RFC-6147/RFC-6147.txt","sha256":"1f84a1d1d05831f92e6e521eae76bb8d1d3e794c17f421dc606711c72a35deed"}},"tags":["nested-reference","unchanged"],"summary":"DNS64 is a mechanism for synthesizing AAAA records from A records.\n DNS64 is used with an IPv6/IPv4 translator to enable client-server\n communication between an IPv6-only client and an IPv4-only server,\n without requiring any changes to either the IPv6 or the IPv4 node,\n for the class of applications that work through NATs. This document\n specifies DNS64, and provides suggestions on how it should be\n deployed in conjunction with IPv6/IPv4 translators.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of th","scope_keywords":["6147","algorithm","http","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 6147 DNS64 is a mechanism for synthesizing AAAA records from A records.\n DNS64 is used with an IPv6/IPv4 translator to enable client-server\n communication between an IPv6-only client and an IPv4-only server,\n without requiring any changes to either the IPv6 or the IPv4 node,\n for the class of applications that work through NATs. This document\n specifies DNS64, and provides suggestions on how it should be\n deployed in conjunction with IPv6/IPv4 translators.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of th 6147 algorithm http license presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6195","type":"specification","body":"IETF","designation":"RFC 6195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6195.txt","https://www.rfc-editor.org/rfc/rfc6195.pdf"],"folder":"IETF/RFC-6195","files":{"txt":{"path":"standards/IETF/RFC-6195/RFC-6195.txt","sha256":"8ec27504650661adda1d87f90c1095e048978d634c463cd3a121afcb3bedcaf0"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Internet Assigned Number Authority (IANA)\n parameter assignment considerations for the allocation of Domain Name\n System (DNS) resource record types, CLASSes, operation codes, error\n codes, DNS protocol message header bits, and AFSDB resource record\n subtypes.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6195.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and th","scope_keywords":["6195","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 6195 This document specifies Internet Assigned Number Authority (IANA)\n parameter assignment considerations for the allocation of Domain Name\n System (DNS) resource record types, CLASSes, operation codes, error\n codes, DNS protocol message header bits, and AFSDB resource record\n subtypes.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6195.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and th 6195 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6265","type":"specification","body":"IETF","designation":"RFC 6265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6265.txt","https://www.rfc-editor.org/rfc/rfc6265.pdf"],"folder":"IETF/RFC-6265","files":{"txt":{"path":"standards/IETF/RFC-6265/RFC-6265.txt","sha256":"dc4177094813e85a44a7897b892b76bc09160b3a03aea44f0f511f3a98f91933"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the HTTP Cookie and Set-Cookie header fields.\n These header fields can be used by HTTP servers to store state\n (called cookies) at HTTP user agents, letting the servers maintain a\n stateful session over the mostly stateless HTTP protocol. Although\n cookies have many historical infelicities that degrade their security\n and privacy, the Cookie and Set-Cookie header fields are widely used\n on the Internet. This document obsoletes RFC 2965.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current statu","scope_keywords":["6265","algorithm","algorithms","attribute","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6265 This document defines the HTTP Cookie and Set-Cookie header fields.\n These header fields can be used by HTTP servers to store state\n (called cookies) at HTTP user agents, letting the servers maintain a\n stateful session over the mostly stateless HTTP protocol. Although\n cookies have many historical infelicities that degrade their security\n and privacy, the Cookie and Set-Cookie header fields are widely used\n on the Internet. This document obsoletes RFC 2965.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current statu 6265 algorithm algorithms attribute http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6303","type":"specification","body":"IETF","designation":"RFC 6303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6303.txt","https://www.rfc-editor.org/rfc/rfc6303.pdf"],"folder":"IETF/RFC-6303","files":{"txt":{"path":"standards/IETF/RFC-6303/RFC-6303.txt","sha256":"4ea46cd9a088993168a0f663bc8623e4e57566e97480f8ea349abe8ab5734c70"}},"tags":["nested-reference","unchanged"],"summary":"Experience with the Domain Name System (DNS) has shown that there are\n a number of DNS zones that all iterative resolvers and recursive\n nameservers should automatically serve, unless configured otherwise.\n RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This\n document extends the practice to cover the IN-ADDR.ARPA zones for RFC\n 1918 address space and other well-known zones with similar\n characteristics.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pro","scope_keywords":["6303","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 7793","folder":"IETF/RFC-7793","source":"IETF/RFC-7793/RFC-7793.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6303 Experience with the Domain Name System (DNS) has shown that there are\n a number of DNS zones that all iterative resolvers and recursive\n nameservers should automatically serve, unless configured otherwise.\n RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This\n document extends the practice to cover the IN-ADDR.ARPA zones for RFC\n 1918 address space and other well-known zones with similar\n characteristics.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pro 6303 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6304","type":"specification","body":"IETF","designation":"RFC 6304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6304.txt","https://www.rfc-editor.org/rfc/rfc6304.pdf"],"folder":"IETF/RFC-6304","files":{"txt":{"path":"standards/IETF/RFC-6304/RFC-6304.txt","sha256":"a1511695efe28f4b453cf360720aa0a3ceaaf5c947ea6b9697f0c3158ceca887"}},"tags":["nested-reference","unchanged"],"summary":"Many sites connected to the Internet make use of IPv4 addresses that\n are not globally unique. Examples are the addresses designated in\n RFC 1918 for private use within individual sites.\n\n Devices in such environments may occasionally originate Domain Name\n System (DNS) queries (so-called \"reverse lookups\") corresponding to\n those private-use addresses. Since the addresses concerned have only\n local significance, it is good practice for site administrators to\n ensure that such queries are answered locally. However, it is not\n uncommon for such queries to follow the normal delegation path in the\n public DNS instead of being answered within the site.\n\n It is not possible for public DNS servers to give useful answers to\n such queries. In addition, due to the wide deployment of private-use\n addresses and the continuing growth of the Internet, the volume of\n such queries is large and growing.","scope_keywords":["6304","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null}],"search_text":"IETF RFC 6304 Many sites connected to the Internet make use of IPv4 addresses that\n are not globally unique. Examples are the addresses designated in\n RFC 1918 for private use within individual sites.\n\n Devices in such environments may occasionally originate Domain Name\n System (DNS) queries (so-called \"reverse lookups\") corresponding to\n those private-use addresses. Since the addresses concerned have only\n local significance, it is good practice for site administrators to\n ensure that such queries are answered locally. However, it is not\n uncommon for such queries to follow the normal delegation path in the\n public DNS instead of being answered within the site.\n\n It is not possible for public DNS servers to give useful answers to\n such queries. In addition, due to the wide deployment of private-use\n addresses and the continuing growth of the Internet, the volume of\n such queries is large and growing. 6304 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6305","type":"specification","body":"IETF","designation":"RFC 6305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6305.txt","https://www.rfc-editor.org/rfc/rfc6305.pdf"],"folder":"IETF/RFC-6305","files":{"txt":{"path":"standards/IETF/RFC-6305/RFC-6305.txt","sha256":"dfad760802184fb8a3fc60a8b8cd5d4006198504d5bb3cfd475b06968c88571b"}},"tags":["nested-reference","unchanged"],"summary":"Many sites connected to the Internet make use of IPv4 addresses that\n are not globally unique. Examples are the addresses designated in\n RFC 1918 for private use within individual sites.\n\n Hosts should never normally send DNS reverse-mapping queries for\n those addresses on the public Internet. However, such queries are\n frequently observed. Authoritative servers are deployed to provide\n authoritative answers to such queries as part of a loosely\n coordinated effort known as the AS112 project.\n\n Since queries sent to AS112 servers are usually not intentional, the\n replies received back from those servers are typically unexpected.\n Unexpected inbound traffic can trigger alarms on intrusion detection\n systems and firewalls, and operators of such systems often mistakenly\n believe that they are being attacked.\n\n This document provides background information and technical advice to\n those firew","scope_keywords":["6305","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null}],"search_text":"IETF RFC 6305 Many sites connected to the Internet make use of IPv4 addresses that\n are not globally unique. Examples are the addresses designated in\n RFC 1918 for private use within individual sites.\n\n Hosts should never normally send DNS reverse-mapping queries for\n those addresses on the public Internet. However, such queries are\n frequently observed. Authoritative servers are deployed to provide\n authoritative answers to such queries as part of a loosely\n coordinated effort known as the AS112 project.\n\n Since queries sent to AS112 servers are usually not intentional, the\n replies received back from those servers are typically unexpected.\n Unexpected inbound traffic can trigger alarms on intrusion detection\n systems and firewalls, and operators of such systems often mistakenly\n believe that they are being attacked.\n\n This document provides background information and technical advice to\n those firew 6305 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6334","type":"specification","body":"IETF","designation":"RFC 6334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6334.txt","https://www.rfc-editor.org/rfc/rfc6334.pdf"],"folder":"IETF/RFC-6334","files":{"txt":{"path":"standards/IETF/RFC-6334/RFC-6334.txt","sha256":"d059f1e4576d85678228e983893bd6930eb82975a5df41bb6f59f595a16d3a50"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a DHCPv6 option that is meant to be used by a\n Dual-Stack Lite Basic Bridging BroadBand (B4) element to discover the\n IPv6 address of its corresponding Address Family Transition Router\n (AFTR).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6334.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights rese","scope_keywords":["6334","http","key","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 7040","folder":"IETF/RFC-7040","source":"IETF/RFC-7040/RFC-7040.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 6334 This document specifies a DHCPv6 option that is meant to be used by a\n Dual-Stack Lite Basic Bridging BroadBand (B4) element to discover the\n IPv6 address of its corresponding Address Family Transition Router\n (AFTR).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6334.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights rese 6334 http key license presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6376","type":"specification","body":"IETF","designation":"RFC 6376","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6376.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6376.txt","https://www.rfc-editor.org/rfc/rfc6376.pdf"],"folder":"IETF/RFC-6376","files":{"txt":{"path":"standards/IETF/RFC-6376/RFC-6376.txt","sha256":"00ae1e26aa19e0b8a6087435a524d23e824e2c31ebd62544dd714923bf8553f0"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) permits a person, role, or\n organization that owns the signing domain to claim some\n responsibility for a message by associating the domain with the\n message. This can be an author's organization, an operational relay,\n or one of their agents. DKIM separates the question of the identity\n of the Signer of the message from the purported author of the\n message. Assertion of responsibility is validated through a\n cryptographic signature and by querying the Signer's domain directly\n to retrieve the appropriate public key. Message transit from author\n to recipient is through relays that typically make no substantive\n change to the message content and thus preserve the DKIM signature.\n\n This memo obsoletes RFC 4871 and RFC 5672.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task For","scope_keywords":["6376","algorithm","algorithms","authentication","hash","http","key","keys","license","management","policy","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6430","folder":"IETF/RFC-6430","source":"IETF/RFC-6430/RFC-6430.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6376 DomainKeys Identified Mail (DKIM) permits a person, role, or\n organization that owns the signing domain to claim some\n responsibility for a message by associating the domain with the\n message. This can be an author's organization, an operational relay,\n or one of their agents. DKIM separates the question of the identity\n of the Signer of the message from the purported author of the\n message. Assertion of responsibility is validated through a\n cryptographic signature and by querying the Signer's domain directly\n to retrieve the appropriate public key. Message transit from author\n to recipient is through relays that typically make no substantive\n change to the message content and thus preserve the DKIM signature.\n\n This memo obsoletes RFC 4871 and RFC 5672.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task For 6376 algorithm algorithms authentication hash http key keys license management policy presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6449","type":"specification","body":"IETF","designation":"RFC 6449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6449.txt","https://www.rfc-editor.org/rfc/rfc6449.pdf"],"folder":"IETF/RFC-6449","files":{"txt":{"path":"standards/IETF/RFC-6449/RFC-6449.txt","sha256":"79dfe51255441309f8ff9f654536285bd93231610feeb6750d52cb1afe0f3f4c"}},"tags":["nested-reference","unchanged"],"summary":"Complaint Feedback Loops similar to those described herein have\n existed for more than a decade, resulting in many de facto standards\n and best practices. This document is an attempt to codify, and thus\n clarify, the ways that both providers and consumers of these feedback\n mechanisms intend to use the feedback, describing some already common\n industry practices.\n\n This document is the result of cooperative efforts within the\n Messaging Anti-Abuse Working Group, a trade organization separate\n from the IETF. The original MAAWG document upon which this document\n is based was published in April, 2010. This document does not\n represent the consensus of the IETF; rather it is being published as\n an Informational RFC to make it widely available to the Internet\n community and simplify reference to this material from IETF work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Tr","scope_keywords":["6449","http","license","management","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null}],"search_text":"IETF RFC 6449 Complaint Feedback Loops similar to those described herein have\n existed for more than a decade, resulting in many de facto standards\n and best practices. This document is an attempt to codify, and thus\n clarify, the ways that both providers and consumers of these feedback\n mechanisms intend to use the feedback, describing some already common\n industry practices.\n\n This document is the result of cooperative efforts within the\n Messaging Anti-Abuse Working Group, a trade organization separate\n from the IETF. The original MAAWG document upon which this document\n is based was published in April, 2010. This document does not\n represent the consensus of the IETF; rather it is being published as\n an Informational RFC to make it widely available to the Internet\n community and simplify reference to this material from IETF work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Tr 6449 http license management policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6604","type":"specification","body":"IETF","designation":"RFC 6604","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6604.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6604.txt","https://www.rfc-editor.org/rfc/rfc6604.pdf"],"folder":"IETF/RFC-6604","files":{"txt":{"path":"standards/IETF/RFC-6604/RFC-6604.txt","sha256":"e59eff0d1319aa00b0a35a2b014ff99719bb68bc9a603bbc0399b006ad30022a"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) has long provided means, such as the\n CNAME (Canonical Name), whereby a DNS query can be redirected to a\n different name. A DNS response header has an RCODE (Response Code)\n field, used for indicating errors, and response status bits. This\n document clarifies, in the case of such redirected queries, how the\n RCODE and status bits correspond to the initial query cycle (where\n the CNAME or the like was detected) and subsequent or final query\n cycles.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information abou","scope_keywords":["6604","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null}],"search_text":"IETF RFC 6604 The Domain Name System (DNS) has long provided means, such as the\n CNAME (Canonical Name), whereby a DNS query can be redirected to a\n different name. A DNS response header has an RCODE (Response Code)\n field, used for indicating errors, and response status bits. This\n document clarifies, in the case of such redirected queries, how the\n RCODE and status bits correspond to the initial query cycle (where\n the CNAME or the like was detected) and subsequent or final query\n cycles.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information abou 6604 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6672","type":"specification","body":"IETF","designation":"RFC 6672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6672.txt","https://www.rfc-editor.org/rfc/rfc6672.pdf"],"folder":"IETF/RFC-6672","files":{"txt":{"path":"standards/IETF/RFC-6672/RFC-6672.txt","sha256":"50cbe190ac838ca006a4642a818c101aaeca623f36fe33e979d1afc92fa11799"}},"tags":["nested-reference","unchanged"],"summary":"The DNAME record provides redirection for a subtree of the domain\n name tree in the DNS. That is, all names that end with a particular\n suffix are redirected to another part of the DNS. This document\n obsoletes the original specification in RFC 2672 as well as updates\n the document on representing IPv6 addresses in DNS (RFC 3363).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6672.\n\nRo","scope_keywords":["6672","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6672 The DNAME record provides redirection for a subtree of the domain\n name tree in the DNS. That is, all names that end with a particular\n suffix are redirected to another part of the DNS. This document\n obsoletes the original specification in RFC 2672 as well as updates\n the document on representing IPv6 addresses in DNS (RFC 3363).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6672.\n\nRo 6672 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6690","type":"specification","body":"IETF","designation":"RFC 6690","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6690.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6690.txt","https://www.rfc-editor.org/rfc/rfc6690.pdf"],"folder":"IETF/RFC-6690","files":{"txt":{"path":"standards/IETF/RFC-6690/RFC-6690.txt","sha256":"ded9aa53ed2b8266d0b296fb9fa5b468a4ef0701849f0faf2540eb236a4c4ced"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines Web Linking using a link format for use by\n constrained web servers to describe hosted resources, their\n attributes, and other relationships between links. Based on the HTTP\n Link Header field defined in RFC 5988, the Constrained RESTful\n Environments (CoRE) Link Format is carried as a payload and is\n assigned an Internet media type. \"RESTful\" refers to the\n Representational State Transfer (REST) architecture. A well-known\n URI is defined as a default entry point for requesting the links\n hosted by a server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard","scope_keywords":["6690","attribute","attributes","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null}],"search_text":"IETF RFC 6690 This specification defines Web Linking using a link format for use by\n constrained web servers to describe hosted resources, their\n attributes, and other relationships between links. Based on the HTTP\n Link Header field defined in RFC 5988, the Constrained RESTful\n Environments (CoRE) Link Format is carried as a payload and is\n assigned an Internet media type. \"RESTful\" refers to the\n Representational State Transfer (REST) architecture. A well-known\n URI is defined as a default entry point for requesting the links\n hosted by a server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standard 6690 attribute attributes http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6742","type":"specification","body":"IETF","designation":"RFC 6742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6742.txt","https://www.rfc-editor.org/rfc/rfc6742.pdf"],"folder":"IETF/RFC-6742","files":{"txt":{"path":"standards/IETF/RFC-6742/RFC-6742.txt","sha256":"2d6a9705bb024de20aa9237a557f829488db1cee69ba7855faa23296ce80e539"}},"tags":["nested-reference","unchanged"],"summary":"This note describes additional optional resource records for use with\n the Domain Name System (DNS). These optional resource records are\n for use with the Identifier-Locator Network Protocol (ILNP). This\n document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publicati","scope_keywords":["6742","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6742 This note describes additional optional resource records for use with\n the Domain Name System (DNS). These optional resource records are\n for use with the Identifier-Locator Network Protocol (ILNP). This\n document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publicati 6742 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6761","type":"specification","body":"IETF","designation":"RFC 6761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6761.txt","https://www.rfc-editor.org/rfc/rfc6761.pdf"],"folder":"IETF/RFC-6761","files":{"txt":{"path":"standards/IETF/RFC-6761/RFC-6761.txt","sha256":"549f6635f34eb0da627568657401f0115e8e33c2ba1ba7e37bf14ab27651339e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes what it means to say that a Domain Name (DNS\n name) is reserved for special use, when reserving such a name is\n appropriate, and the procedure for doing so. It establishes an IANA\n registry for such domain names, and seeds it with entries for some of\n the already established special domain names.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6761.\n\nCopyright Not","scope_keywords":["6761","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null}],"search_text":"IETF RFC 6761 This document describes what it means to say that a Domain Name (DNS\n name) is reserved for special use, when reserving such a name is\n appropriate, and the procedure for doing so. It establishes an IANA\n registry for such domain names, and seeds it with entries for some of\n the already established special domain names.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6761.\n\nCopyright Not 6761 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6781","type":"specification","body":"IETF","designation":"RFC 6781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6781.txt","https://www.rfc-editor.org/rfc/rfc6781.pdf"],"folder":"IETF/RFC-6781","files":{"txt":{"path":"standards/IETF/RFC-6781/RFC-6781.txt","sha256":"ca64c97f753bc68bba1e78048bafa37d4f86dd2432bdd40ebff7b9758a54cf04"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of practices for operating the DNS with\n security extensions (DNSSEC). The target audience is zone\n administrators deploying DNSSEC.\n\n The document discusses operational aspects of using keys and\n signatures in the DNS. It discusses issues of key generation, key\n storage, signature generation, key rollover, and related policies.\n\n This document obsoletes RFC 4641, as it covers more operational\n ground and gives more up-to-date requirements with respect to key\n sizes and the DNSSEC operations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group","scope_keywords":["6781","algorithm","hash","http","key","keys","license","policies","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6781 This document describes a set of practices for operating the DNS with\n security extensions (DNSSEC). The target audience is zone\n administrators deploying DNSSEC.\n\n The document discusses operational aspects of using keys and\n signatures in the DNS. It discusses issues of key generation, key\n storage, signature generation, key rollover, and related policies.\n\n This document obsoletes RFC 4641, as it covers more operational\n ground and gives more up-to-date requirements with respect to key\n sizes and the DNSSEC operations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group 6781 algorithm hash http key keys license policies signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6837","type":"specification","body":"IETF","designation":"RFC 6837","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6837.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6837.txt","https://www.rfc-editor.org/rfc/rfc6837.pdf"],"folder":"IETF/RFC-6837","files":{"txt":{"path":"standards/IETF/RFC-6837/RFC-6837.txt","sha256":"50c24881db4e62908d9c08b3800016aa94f0bec3c9ab53183fc1f4c94ecf056a"}},"tags":["nested-reference","unchanged"],"summary":"The Locator/ID Separation Protocol (LISP) is a protocol to\n encapsulate IP packets in order to allow end sites to route to one\n another without injecting routes from one end of the Internet to\n another. This memo presents an experimental database and a\n discussion of methods to transport the mapping of Endpoint IDs (EIDs)\n to Routing Locators (RLOCs) to routers in a reliable, scalable, and\n secure manner. Our analysis concludes that transport of all EID-to-\n RLOC mappings scales well to at least 10^8 entries.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its","scope_keywords":["6837","http","key","license","pki","risk","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null}],"search_text":"IETF RFC 6837 The Locator/ID Separation Protocol (LISP) is a protocol to\n encapsulate IP packets in order to allow end sites to route to one\n another without injecting routes from one end of the Internet to\n another. This memo presents an experimental database and a\n discussion of methods to transport the mapping of Endpoint IDs (EIDs)\n to Routing Locators (RLOCs) to routers in a reliable, scalable, and\n secure manner. Our analysis concludes that transport of all EID-to-\n RLOC mappings scales well to at least 10^8 entries.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its 6837 http key license pki risk signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6840","type":"specification","body":"IETF","designation":"RFC 6840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6840.txt","https://www.rfc-editor.org/rfc/rfc6840.pdf"],"folder":"IETF/RFC-6840","files":{"txt":{"path":"standards/IETF/RFC-6840/RFC-6840.txt","sha256":"32c2a8c755f37f3467b4ca098fc0283efe53d2648e93c3ae966cfa390a50bfaf"}},"tags":["nested-reference","unchanged"],"summary":"This document is a collection of technical clarifications to the DNS\n Security (DNSSEC) document set. It is meant to serve as a resource\n to implementors as well as a collection of DNSSEC errata that existed\n at the time of writing.\n\n This document updates the core DNSSEC documents (RFC 4033, RFC 4034,\n and RFC 4035) as well as the NSEC3 specification (RFC 5155). It also\n defines NSEC3 and SHA-2 (RFC 4509 and RFC 5702) as core parts of the\n DNSSEC specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current s","scope_keywords":["6840","algorithm","algorithms","hash","http","key","keys","license","policy","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6840 This document is a collection of technical clarifications to the DNS\n Security (DNSSEC) document set. It is meant to serve as a resource\n to implementors as well as a collection of DNSSEC errata that existed\n at the time of writing.\n\n This document updates the core DNSSEC documents (RFC 4033, RFC 4034,\n and RFC 4035) as well as the NSEC3 specification (RFC 5155). It also\n defines NSEC3 and SHA-2 (RFC 4509 and RFC 5702) as core parts of the\n DNSSEC specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current s 6840 algorithm algorithms hash http key keys license policy signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6844","type":"specification","body":"IETF","designation":"RFC 6844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6844.txt","https://www.rfc-editor.org/rfc/rfc6844.pdf"],"folder":"IETF/RFC-6844","files":{"txt":{"path":"standards/IETF/RFC-6844/RFC-6844.txt","sha256":"e46e6205f5a6a0fec4e80e6b47066246db9c17badc66d42f5fb327a61ab7a6c3"}},"tags":["nested-reference","unchanged"],"summary":"The Certification Authority Authorization (CAA) DNS Resource Record\n allows a DNS domain name holder to specify one or more Certification\n Authorities (CAs) authorized to issue certificates for that domain.\n CAA Resource Records allow a public Certification Authority to\n implement additional controls to reduce the risk of unintended\n certificate mis-issue. This document defines the syntax of the CAA\n record and rules for processing CAA records by certificate issuers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr","scope_keywords":["6844","audit","authentication","authorization","certificate","certificates","holder","http","issuer","key","license","pki","policies","policy","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 6844 The Certification Authority Authorization (CAA) DNS Resource Record\n allows a DNS domain name holder to specify one or more Certification\n Authorities (CAs) authorized to issue certificates for that domain.\n CAA Resource Records allow a public Certification Authority to\n implement additional controls to reduce the risk of unintended\n certificate mis-issue. This document defines the syntax of the CAA\n record and rules for processing CAA records by certificate issuers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr 6844 audit authentication authorization certificate certificates holder http issuer key license pki policies policy presentation risk nested-reference unchanged"},{"id":"IETF RFC 6895","type":"specification","body":"IETF","designation":"RFC 6895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6895.txt","https://www.rfc-editor.org/rfc/rfc6895.pdf"],"folder":"IETF/RFC-6895","files":{"txt":{"path":"standards/IETF/RFC-6895/RFC-6895.txt","sha256":"99114ac181572371b14d285ed354863514f5ab7a265e89b49ea5604c7e074759"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Internet Assigned Numbers Authority (IANA)\n parameter assignment considerations for the allocation of Domain Name\n System (DNS) resource record types, CLASSes, operation codes, error\n codes, DNS protocol message header bits, and AFSDB resource record\n subtypes. It obsoletes RFC 6195 and updates RFCs 1183, 2845, 2930,\n and 3597.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i","scope_keywords":["6895","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 6895 This document specifies Internet Assigned Numbers Authority (IANA)\n parameter assignment considerations for the allocation of Domain Name\n System (DNS) resource record types, CLASSes, operation codes, error\n codes, DNS protocol message header bits, and AFSDB resource record\n subtypes. It obsoletes RFC 6195 and updates RFCs 1183, 2845, 2930,\n and 3597.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i 6895 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7050","type":"specification","body":"IETF","designation":"RFC 7050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7050.txt","https://www.rfc-editor.org/rfc/rfc7050.pdf"],"folder":"IETF/RFC-7050","files":{"txt":{"path":"standards/IETF/RFC-7050/RFC-7050.txt","sha256":"88c32f09ea8d72f3b2c724fd0c3aa29845dd146a3e334d401efab9741daa68d1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for detecting the presence of DNS64\n and for learning the IPv6 prefix used for protocol translation on an\n access network. The method depends on the existence of a well-known\n IPv4-only fully qualified domain name \"ipv4only.arpa.\". The\n information learned enables nodes to perform local IPv6 address\n synthesis and to potentially avoid NAT64 on dual-stack and multi-\n interface deployments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h","scope_keywords":["7050","http","key","license","qualified","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 7050 This document describes a method for detecting the presence of DNS64\n and for learning the IPv6 prefix used for protocol translation on an\n access network. The method depends on the existence of a well-known\n IPv4-only fully qualified domain name \"ipv4only.arpa.\". The\n information learned enables nodes to perform local IPv6 address\n synthesis and to potentially avoid NAT64 on dual-stack and multi-\n interface deployments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h 7050 http key license qualified subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7129","type":"specification","body":"IETF","designation":"RFC 7129","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7129.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7129.txt","https://www.rfc-editor.org/rfc/rfc7129.pdf"],"folder":"IETF/RFC-7129","files":{"txt":{"path":"standards/IETF/RFC-7129/RFC-7129.txt","sha256":"23800f740fc993ebf3fc32b62e76dd8afb43f154bb5762395c0f859bb1370012"}},"tags":["nested-reference","unchanged"],"summary":"Authenticated denial of existence allows a resolver to validate that\n a certain domain name does not exist. It is also used to signal that\n a domain name exists but does not have the specific resource record\n (RR) type you were asking for. When returning a negative DNS\n Security Extensions (DNSSEC) response, a name server usually includes\n up to two NSEC records. With NSEC version 3 (NSEC3), this amount is\n three.\n\n This document provides additional background commentary and some\n context for the NSEC and NSEC3 mechanisms used by DNSSEC to provide\n authenticated denial-of-existence responses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no s","scope_keywords":["7129","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7129 Authenticated denial of existence allows a resolver to validate that\n a certain domain name does not exist. It is also used to signal that\n a domain name exists but does not have the specific resource record\n (RR) type you were asking for. When returning a negative DNS\n Security Extensions (DNSSEC) response, a name server usually includes\n up to two NSEC records. With NSEC version 3 (NSEC3), this amount is\n three.\n\n This document provides additional background commentary and some\n context for the NSEC and NSEC3 mechanisms used by DNSSEC to provide\n authenticated denial-of-existence responses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no s 7129 hash http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7208","type":"specification","body":"IETF","designation":"RFC 7208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7208.txt","https://www.rfc-editor.org/rfc/rfc7208.pdf"],"folder":"IETF/RFC-7208","files":{"txt":{"path":"standards/IETF/RFC-7208/RFC-7208.txt","sha256":"3cca3f2551f50d24a7b6423a7451d285df077863dab4bb261080ee87844f2d5b"}},"tags":["nested-reference","unchanged"],"summary":"Email on the Internet can be forged in a number of ways. In\n particular, existing protocols place no restriction on what a sending\n host can use as the \"MAIL FROM\" of a message or the domain given on\n the SMTP HELO/EHLO commands. This document describes version 1 of\n the Sender Policy Framework (SPF) protocol, whereby ADministrative\n Management Domains (ADMDs) can explicitly authorize the hosts that\n are allowed to use their domain names, and a receiving host can check\n such authorization.\n\n This document obsoletes RFC 4408.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avail","scope_keywords":["7208","authorization","http","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 7208 Email on the Internet can be forged in a number of ways. In\n particular, existing protocols place no restriction on what a sending\n host can use as the \"MAIL FROM\" of a message or the domain given on\n the SMTP HELO/EHLO commands. This document describes version 1 of\n the Sender Policy Framework (SPF) protocol, whereby ADministrative\n Management Domains (ADMDs) can explicitly authorize the hosts that\n are allowed to use their domain names, and a receiving host can check\n such authorization.\n\n This document obsoletes RFC 4408.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avail 7208 authorization http key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7566","type":"specification","body":"IETF","designation":"RFC 7566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7566.txt","https://www.rfc-editor.org/rfc/rfc7566.pdf"],"folder":"IETF/RFC-7566","files":{"txt":{"path":"standards/IETF/RFC-7566/RFC-7566.txt","sha256":"4be48da00a781f8e083692a077144584f23fd14c6b28060b1c7603e83b49e336"}},"tags":["nested-reference","unchanged"],"summary":"This document registers an E.164 Number Mapping (ENUM) service for\n 'acct' URIs (Uniform Resource Identifiers).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7566.\n\nCopyright Noti","scope_keywords":["7566","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 7566 This document registers an E.164 Number Mapping (ENUM) service for\n 'acct' URIs (Uniform Resource Identifiers).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7566.\n\nCopyright Noti 7566 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7622","type":"specification","body":"IETF","designation":"RFC 7622","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7622.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7622.txt","https://www.rfc-editor.org/rfc/rfc7622.pdf"],"folder":"IETF/RFC-7622","files":{"txt":{"path":"standards/IETF/RFC-7622/RFC-7622.txt","sha256":"7f3fd4d5399403d7b364d4831a44d54be8752564e38142248d559c2168532b83"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the address format for the Extensible Messaging\n and Presence Protocol (XMPP), including support for code points\n outside the ASCII range. This document obsoletes RFC 6122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7622.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i","scope_keywords":["7622","algorithm","http","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null}],"search_text":"IETF RFC 7622 This document defines the address format for the Extensible Messaging\n and Presence Protocol (XMPP), including support for code points\n outside the ASCII range. This document obsoletes RFC 6122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7622.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i 7622 algorithm http key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7626","type":"specification","body":"IETF","designation":"RFC 7626","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7626.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7626.txt","https://www.rfc-editor.org/rfc/rfc7626.pdf"],"folder":"IETF/RFC-7626","files":{"txt":{"path":"standards/IETF/RFC-7626/RFC-7626.txt","sha256":"5375b899eae4d4b5bf30c44a5cdb80bea4b997a21ee7f6dc1c1919f3c1ad2853"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the privacy issues associated with the use of\n the DNS by Internet users. It is intended to be an analysis of the\n present situation and does not prescribe solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7626.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF ","scope_keywords":["7626","algorithm","encryption","http","identification","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7626 This document describes the privacy issues associated with the use of\n the DNS by Internet users. It is intended to be an analysis of the\n present situation and does not prescribe solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7626.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF  7626 algorithm encryption http identification license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7672","type":"specification","body":"IETF","designation":"RFC 7672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7672.txt","https://www.rfc-editor.org/rfc/rfc7672.pdf"],"folder":"IETF/RFC-7672","files":{"txt":{"path":"standards/IETF/RFC-7672/RFC-7672.txt","sha256":"f42a3a4e0eada0c82195659c8e8b691d9e82bd51399009ed7ce1c173d8163ce7"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a downgrade-resistant protocol for SMTP transport\n security between Message Transfer Agents (MTAs), based on the DNS-\n Based Authentication of Named Entities (DANE) TLSA DNS record.\n Adoption of this protocol enables an incremental transition of the\n Internet email backbone to one using encrypted and authenticated\n Transport Layer Security (TLS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://","scope_keywords":["7672","algorithm","authentication","certificate","delivery","http","key","license","management","pki","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7672 This memo describes a downgrade-resistant protocol for SMTP transport\n security between Message Transfer Agents (MTAs), based on the DNS-\n Based Authentication of Named Entities (DANE) TLSA DNS record.\n Adoption of this protocol enables an incremental transition of the\n Internet email backbone to one using encrypted and authenticated\n Transport Layer Security (TLS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:// 7672 algorithm authentication certificate delivery http key license management pki policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7707","type":"specification","body":"IETF","designation":"RFC 7707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7707.txt","https://www.rfc-editor.org/rfc/rfc7707.pdf"],"folder":"IETF/RFC-7707","files":{"txt":{"path":"standards/IETF/RFC-7707/RFC-7707.txt","sha256":"6b53f080a2c55c319ff915745746147d78906aff11a0daf2ac654b35a95291bf"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 offers a much larger address space than that of its IPv4\n counterpart. An IPv6 subnet of size /64 can (in theory) accommodate\n approximately 1.844 * 10^19 hosts, thus resulting in a much lower\n host density (#hosts/#addresses) than is typical in IPv4 networks,\n where a site typically has 65,000 or fewer unique addresses. As a\n result, it is widely assumed that it would take a tremendous effort\n to perform address-scanning attacks against IPv6 networks; therefore,\n IPv6 address-scanning attacks have been considered unfeasible. This\n document formally obsoletes RFC 5157, which first discussed this\n assumption, by providing further analysis on how traditional address-\n scanning techniques apply to IPv6 networks and exploring some\n additional techniques that can be employed for IPv6 network\n reconnaissance.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specific","scope_keywords":["7707","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7707 IPv6 offers a much larger address space than that of its IPv4\n counterpart. An IPv6 subnet of size /64 can (in theory) accommodate\n approximately 1.844 * 10^19 hosts, thus resulting in a much lower\n host density (#hosts/#addresses) than is typical in IPv4 networks,\n where a site typically has 65,000 or fewer unique addresses. As a\n result, it is widely assumed that it would take a tremendous effort\n to perform address-scanning attacks against IPv6 networks; therefore,\n IPv6 address-scanning attacks have been considered unfeasible. This\n document formally obsoletes RFC 5157, which first discussed this\n assumption, by providing further analysis on how traditional address-\n scanning techniques apply to IPv6 networks and exploring some\n additional techniques that can be employed for IPv6 network\n reconnaissance.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specific 7707 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7712","type":"specification","body":"IETF","designation":"RFC 7712","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7712.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7712.txt","https://www.rfc-editor.org/rfc/rfc7712.pdf"],"folder":"IETF/RFC-7712","files":{"txt":{"path":"standards/IETF/RFC-7712/RFC-7712.txt","sha256":"2aab65e555f1461bb540be174fb786b65de339bcccb596b5f7b0da1a9e00040b"}},"tags":["nested-reference","unchanged"],"summary":"This document improves the security of the Extensible Messaging and\n Presence Protocol (XMPP) in two ways. First, it specifies how to\n establish a strong association between a domain name and an XML\n stream, using the concept of \"prooftypes\". Second, it describes how\n to securely delegate a service domain name (e.g., example.com) to a\n target server hostname (e.g., hosting.example.net); this is\n especially important in multi-tenanted environments where the same\n target server hosts a large number of domains.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2","scope_keywords":["7712","authentication","certificate","http","key","license","pki","profile","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7712 This document improves the security of the Extensible Messaging and\n Presence Protocol (XMPP) in two ways. First, it specifies how to\n establish a strong association between a domain name and an XML\n stream, using the concept of \"prooftypes\". Second, it describes how\n to securely delegate a service domain name (e.g., example.com) to a\n target server hostname (e.g., hosting.example.net); this is\n especially important in multi-tenanted environments where the same\n target server hosts a large number of domains.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 7712 authentication certificate http key license pki profile subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7816","type":"specification","body":"IETF","designation":"RFC 7816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7816.txt","https://www.rfc-editor.org/rfc/rfc7816.pdf"],"folder":"IETF/RFC-7816","files":{"txt":{"path":"standards/IETF/RFC-7816/RFC-7816.txt","sha256":"a35f5b86163f3734f12bd19bdbdda362d1698d74cef820dea33363a8566d18a6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a technique to improve DNS privacy, a\n technique called \"QNAME minimisation\", where the DNS resolver no\n longer sends the full original QNAME to the upstream name server.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["7816","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7816 This document describes a technique to improve DNS privacy, a\n technique called \"QNAME minimisation\", where the DNS resolver no\n longer sends the full original QNAME to the upstream name server.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 7816 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7858","type":"specification","body":"IETF","designation":"RFC 7858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7858.txt","https://www.rfc-editor.org/rfc/rfc7858.pdf"],"folder":"IETF/RFC-7858","files":{"txt":{"path":"standards/IETF/RFC-7858/RFC-7858.txt","sha256":"872e634c8d5ca4219a90147d356570e7d10046ad12d560e7d8b24f3aa340fdf0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of Transport Layer Security (TLS) to\n provide privacy for DNS. Encryption provided by TLS eliminates\n opportunities for eavesdropping and on-path tampering with DNS\n queries in the network, such as discussed in RFC 7626. In addition,\n this document specifies two usage profiles for DNS over TLS and\n provides advice on performance considerations to minimize overhead\n from using TCP and TLS with DNS.\n\n This document focuses on securing stub-to-recursive traffic, as per\n the charter of the DPRIVE Working Group. It does not prevent future\n applications of the protocol to recursive-to-authoritative traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publi","scope_keywords":["7858","authentication","encryption","http","key","license","path","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 7858 This document describes the use of Transport Layer Security (TLS) to\n provide privacy for DNS. Encryption provided by TLS eliminates\n opportunities for eavesdropping and on-path tampering with DNS\n queries in the network, such as discussed in RFC 7626. In addition,\n this document specifies two usage profiles for DNS over TLS and\n provides advice on performance considerations to minimize overhead\n from using TCP and TLS with DNS.\n\n This document focuses on securing stub-to-recursive traffic, as per\n the charter of the DPRIVE Working Group. It does not prevent future\n applications of the protocol to recursive-to-authoritative traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publi 7858 authentication encryption http key license path profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7871","type":"specification","body":"IETF","designation":"RFC 7871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7871.txt","https://www.rfc-editor.org/rfc/rfc7871.pdf"],"folder":"IETF/RFC-7871","files":{"txt":{"path":"standards/IETF/RFC-7871/RFC-7871.txt","sha256":"026ddd80ab863b8a2d194b7b26956c8112f9c9967dc2add8cd0b1d432eb80dae"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extension Mechanisms for DNS (EDNS0)\n option that is in active use to carry information about the network\n that originated a DNS query and the network for which the subsequent\n response can be cached. Since it has some known operational and\n privacy shortcomings, a revision will be worked through the IETF for\n improvement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this ","scope_keywords":["7871","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 7871 This document describes an Extension Mechanisms for DNS (EDNS0)\n option that is in active use to carry information about the network\n that originated a DNS query and the network for which the subsequent\n response can be cached. Since it has some known operational and\n privacy shortcomings, a revision will be worked through the IETF for\n improvement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this  7871 http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7969","type":"specification","body":"IETF","designation":"RFC 7969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7969.txt","https://www.rfc-editor.org/rfc/rfc7969.pdf"],"folder":"IETF/RFC-7969","files":{"txt":{"path":"standards/IETF/RFC-7969/RFC-7969.txt","sha256":"e1de85505a9e7be5ab2febcbe98d2967d1854f1d32edc45b25719928e54ab640"}},"tags":["nested-reference","unchanged"],"summary":"DHCP servers have evolved over the years to provide significant\n functionality beyond that described in the DHCP base specifications.\n One aspect of this functionality is support for context-specific\n configuration information. This memo describes some such features\n and explains their operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on ","scope_keywords":["7969","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7969 DHCP servers have evolved over the years to provide significant\n functionality beyond that described in the DHCP base specifications.\n One aspect of this functionality is support for context-specific\n configuration information. This memo describes some such features\n and explains their operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on  7969 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8006","type":"specification","body":"IETF","designation":"RFC 8006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8006.txt","https://www.rfc-editor.org/rfc/rfc8006.pdf"],"folder":"IETF/RFC-8006","files":{"txt":{"path":"standards/IETF/RFC-8006/RFC-8006.txt","sha256":"24f164c76513f1576c50e6611e5cc6e728f8685aa3e4143e2c9cd7075ea2ae21"}},"tags":["nested-reference","unchanged"],"summary":"The Content Delivery Network Interconnection (CDNI) Metadata\n interface enables interconnected Content Delivery Networks (CDNs) to\n exchange content distribution metadata in order to enable content\n acquisition and delivery. The CDNI Metadata associated with a piece\n of content provides a downstream CDN with sufficient information for\n the downstream CDN to service content requests on behalf of an\n upstream CDN. This document describes both a base set of CDNI\n Metadata and the protocol for exchanging that metadata.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Se","scope_keywords":["8006","authorization","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 8006 The Content Delivery Network Interconnection (CDNI) Metadata\n interface enables interconnected Content Delivery Networks (CDNs) to\n exchange content distribution metadata in order to enable content\n acquisition and delivery. The CDNI Metadata associated with a piece\n of content provides a downstream CDN with sufficient information for\n the downstream CDN to service content requests on behalf of an\n upstream CDN. This document describes both a base set of CDNI\n Metadata and the protocol for exchanging that metadata.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Se 8006 authorization delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8020","type":"specification","body":"IETF","designation":"RFC 8020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8020.txt","https://www.rfc-editor.org/rfc/rfc8020.pdf"],"folder":"IETF/RFC-8020","files":{"txt":{"path":"standards/IETF/RFC-8020/RFC-8020.txt","sha256":"61ea1d261e7907f197ac14afcd8767535a925d2b506aeba4d7d65ab5f0e221cd"}},"tags":["nested-reference","unchanged"],"summary":"This document states clearly that when a DNS resolver receives a\n response with a response code of NXDOMAIN, it means that the domain\n name which is thus denied AND ALL THE NAMES UNDER IT do not exist.\n\n This document clarifies RFC 1034 and modifies a portion of RFC 2308:\n it updates both of them.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8020.\n\nCopyright Notice\n\n Copyright (c) 201","scope_keywords":["8020","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null}],"search_text":"IETF RFC 8020 This document states clearly that when a DNS resolver receives a\n response with a response code of NXDOMAIN, it means that the domain\n name which is thus denied AND ALL THE NAMES UNDER IT do not exist.\n\n This document clarifies RFC 1034 and modifies a portion of RFC 2308:\n it updates both of them.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8020.\n\nCopyright Notice\n\n Copyright (c) 201 8020 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8094","type":"specification","body":"IETF","designation":"RFC 8094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8094.txt","https://www.rfc-editor.org/rfc/rfc8094.pdf"],"folder":"IETF/RFC-8094","files":{"txt":{"path":"standards/IETF/RFC-8094/RFC-8094.txt","sha256":"a4849c77a4eaa161e491cffb80c78ab98c62ceb1b0fb50e0265e8dabe8f1e909"}},"tags":["nested-reference","unchanged"],"summary":"DNS queries and responses are visible to network elements on the path\n between the DNS client and its server. These queries and responses\n can contain privacy-sensitive information, which is valuable to\n protect.\n\n This document proposes the use of Datagram Transport Layer Security\n (DTLS) for DNS, to protect against passive listeners and certain\n active attacks. As latency is critical for DNS, this proposal also\n discusses mechanisms to reduce DTLS round trips and reduce the DTLS\n handshake size. The proposed mechanism runs over port 853.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the","scope_keywords":["8094","authentication","http","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 8094 DNS queries and responses are visible to network elements on the path\n between the DNS client and its server. These queries and responses\n can contain privacy-sensitive information, which is valuable to\n protect.\n\n This document proposes the use of Datagram Transport Layer Security\n (DTLS) for DNS, to protect against passive listeners and certain\n active attacks. As latency is critical for DNS, this proposal also\n discusses mechanisms to reduce DTLS round trips and reduce the DTLS\n handshake size. The proposed mechanism runs over port 853.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the 8094 authentication http key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8109","type":"specification","body":"IETF","designation":"RFC 8109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8109.txt","https://www.rfc-editor.org/rfc/rfc8109.pdf"],"folder":"IETF/RFC-8109","files":{"txt":{"path":"standards/IETF/RFC-8109/RFC-8109.txt","sha256":"935dc691f4186e13e22c9ab5c669384d43082383fb7734f08b43d86577f84220"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the queries that a DNS resolver should emit\n to initialize its cache. The result is that the resolver gets both a\n current NS Resource Record Set (RRset) for the root zone and the\n necessary address information for reaching the root servers.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8109.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identifie","scope_keywords":["8109","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 8109 This document describes the queries that a DNS resolver should emit\n to initialize its cache. The result is that the resolver gets both a\n current NS Resource Record Set (RRset) for the root zone and the\n necessary address information for reaching the root servers.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8109.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identifie 8109 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8490","type":"specification","body":"IETF","designation":"RFC 8490","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8490.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8490.txt","https://www.rfc-editor.org/rfc/rfc8490.pdf"],"folder":"IETF/RFC-8490","files":{"txt":{"path":"standards/IETF/RFC-8490/RFC-8490.txt","sha256":"3d8bb72c3649ba7a085847291b9e0352b6b8289deef63be351ea6444cff54c60"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new DNS OPCODE for DNS Stateful Operations\n (DSO). DSO messages communicate operations within persistent\n stateful sessions using Type Length Value (TLV) syntax. Three TLVs\n are defined that manage session timeouts, termination, and encryption\n padding, and a framework is defined for extensions to enable new\n stateful operations. This document updates RFC 1035 by adding a new\n DNS header OPCODE that has both different message semantics and a new\n result code. This document updates RFC 7766 by redefining a session,\n providing new guidance on connection reuse, and providing a new\n mechanism for handling session idle timeouts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been app","scope_keywords":["8490","encryption","http","https","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 8490 This document defines a new DNS OPCODE for DNS Stateful Operations\n (DSO). DSO messages communicate operations within persistent\n stateful sessions using Type Length Value (TLV) syntax. Three TLVs\n are defined that manage session timeouts, termination, and encryption\n padding, and a framework is defined for extensions to enable new\n stateful operations. This document updates RFC 1035 by adding a new\n DNS header OPCODE that has both different message semantics and a new\n result code. This document updates RFC 7766 by redefining a session,\n providing new guidance on connection reuse, and providing a new\n mechanism for handling session idle timeouts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been app 8490 encryption http https license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8738","type":"specification","body":"IETF","designation":"RFC 8738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8738.txt","https://www.rfc-editor.org/rfc/rfc8738.pdf"],"folder":"IETF/RFC-8738","files":{"pdf":{"path":"standards/IETF/RFC-8738/RFC-8738.pdf","sha256":"7297f3f4398cfbc34f686b3d3b8fdf5370db923faca4870bd1b1e09be0233f61"},"txt":{"path":"standards/IETF/RFC-8738/RFC-8738.txt","sha256":"a2b87cef8c387d7ed497153c2374c268e22ccd465a97cab6978c9987662b4051"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies identifiers and challenges required to enable\n the Automated Certificate Management Environment (ACME) to issue\n certificates for IP addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8738.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and th","scope_keywords":["8738","authorization","certificate","certificates","http","https","key","license","management","policy","presentation","qualified","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 8738 This document specifies identifiers and challenges required to enable\n the Automated Certificate Management Environment (ACME) to issue\n certificates for IP addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8738.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and th 8738 authorization certificate certificates http https key license management policy presentation qualified subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8767","type":"specification","body":"IETF","designation":"RFC 8767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8767.txt","https://www.rfc-editor.org/rfc/rfc8767.pdf"],"folder":"IETF/RFC-8767","files":{"pdf":{"path":"standards/IETF/RFC-8767/RFC-8767.pdf","sha256":"1bad5146bbbe0e2aa6e50bf3433085713936d9586d82ce7d2901434566ea0d29"},"txt":{"path":"standards/IETF/RFC-8767/RFC-8767.txt","sha256":"60841115fa4edc1918ef5cd423ca73c99f9e4e192466729941e55e0537bb6bc4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a method (serve-stale) for recursive resolvers\n to use stale DNS data to avoid outages when authoritative nameservers\n cannot be reached to refresh expired data. One of the motivations\n for serve-stale is to make the DNS more resilient to DoS attacks and\n thereby make them less attractive as an attack vector. This document\n updates the definitions of TTL from RFCs 1034 and 1035 so that data\n can be kept in the cache beyond the TTL expiry; it also updates RFC\n 2181 by interpreting values with the high-order bit set as being\n positive, rather than 0, and suggests a cap of 7 days.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineerin","scope_keywords":["8767","algorithm","algorithms","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null}],"search_text":"IETF RFC 8767 This document defines a method (serve-stale) for recursive resolvers\n to use stale DNS data to avoid outages when authoritative nameservers\n cannot be reached to refresh expired data. One of the motivations\n for serve-stale is to make the DNS more resilient to DoS attacks and\n thereby make them less attractive as an attack vector. This document\n updates the definitions of TTL from RFCs 1034 and 1035 so that data\n can be kept in the cache beyond the TTL expiry; it also updates RFC\n 2181 by interpreting values with the high-order bit set as being\n positive, rather than 0, and suggests a cap of 7 days.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineerin 8767 algorithm algorithms http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8820","type":"specification","body":"IETF","designation":"RFC 8820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8820.txt","https://www.rfc-editor.org/rfc/rfc8820.pdf"],"folder":"IETF/RFC-8820","files":{"pdf":{"path":"standards/IETF/RFC-8820/RFC-8820.pdf","sha256":"cb462490f9cde4ba84ef15c6dfaa3714c71f57d87ae53cac5a46080d5b457768"},"txt":{"path":"standards/IETF/RFC-8820/RFC-8820.txt","sha256":"d4872896c3beae79143cc5f3c085c6992e6c6f9427a94f6295dce2bc4746a12c"}},"tags":["nested-reference","unchanged"],"summary":"Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and\n extensible naming system wherein each scheme's specification may\n further restrict the syntax and semantics of identifiers using that\n scheme.\" In other words, the structure of a URI is defined by its\n scheme. While it is common for schemes to further delegate their\n substructure to the URI's owner, publishing independent standards\n that mandate particular forms of substructure in URIs is often\n problematic.\n\n This document provides guidance on the specification of URI\n substructure in standards.\n\n This document obsoletes RFC 7320 and updates RFC 3986.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication ","scope_keywords":["8820","http","https","license","path","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 8820 Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and\n extensible naming system wherein each scheme's specification may\n further restrict the syntax and semantics of identifiers using that\n scheme.\" In other words, the structure of a URI is defined by its\n scheme. While it is common for schemes to further delegate their\n substructure to the URI's owner, publishing independent standards\n that mandate particular forms of substructure in URIs is often\n problematic.\n\n This document provides guidance on the specification of URI\n substructure in standards.\n\n This document obsoletes RFC 7320 and updates RFC 3986.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication  8820 http https license path signature subject trust nested-reference unchanged"},{"id":"IETF RFC 8866","type":"specification","body":"IETF","designation":"RFC 8866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8866.txt","https://www.rfc-editor.org/rfc/rfc8866.pdf"],"folder":"IETF/RFC-8866","files":{"pdf":{"path":"standards/IETF/RFC-8866/RFC-8866.pdf","sha256":"da3c45b9210124aee53323c8773dfe66c25cdbfc15d7eb659d5cb0fa049bfb07"},"txt":{"path":"standards/IETF/RFC-8866/RFC-8866.txt","sha256":"3af2bc852fd83a2093dd945b01b2c7f1a38d92cd9a56493fd04dbd72dad0d076"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Session Description Protocol (SDP). SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation. This document obsoletes RFC 4566.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8866.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified ","scope_keywords":["8866","attribute","attributes","encryption","http","https","key","keys","license","presentation","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null}],"search_text":"IETF RFC 8866 This memo defines the Session Description Protocol (SDP). SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation. This document obsoletes RFC 4566.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8866.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified  8866 attribute attributes encryption http https key keys license presentation subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 8901","type":"specification","body":"IETF","designation":"RFC 8901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8901.txt","https://www.rfc-editor.org/rfc/rfc8901.pdf"],"folder":"IETF/RFC-8901","files":{"pdf":{"path":"standards/IETF/RFC-8901/RFC-8901.pdf","sha256":"52a030b699a3100911e04aa5841dae2a1a589d19d0e1a26ba8ae65d6ff704e7e"},"txt":{"path":"standards/IETF/RFC-8901/RFC-8901.txt","sha256":"67d095047910b3c9cdb5766e9b1f1473de84a6909fc0ddf783b780e504ee48ab"}},"tags":["nested-reference","unchanged"],"summary":"Many enterprises today employ the service of multiple DNS providers\n to distribute their authoritative DNS service. Deploying DNSSEC in\n such an environment may present some challenges, depending on the\n configuration and feature set in use. In particular, when each DNS\n provider independently signs zone data with their own keys,\n additional key-management mechanisms are necessary. This document\n presents deployment models that accommodate this scenario and\n describes these key-management requirements. These models do not\n require any changes to the behavior of validating resolvers, nor do\n they impose the new key-management requirements on authoritative\n servers not involved in multi-signer configurations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engine","scope_keywords":["8901","algorithm","http","https","key","keys","license","management","path","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 8901 Many enterprises today employ the service of multiple DNS providers\n to distribute their authoritative DNS service. Deploying DNSSEC in\n such an environment may present some challenges, depending on the\n configuration and feature set in use. In particular, when each DNS\n provider independently signs zone data with their own keys,\n additional key-management mechanisms are necessary. This document\n presents deployment models that accommodate this scenario and\n describes these key-management requirements. These models do not\n require any changes to the behavior of validating resolvers, nor do\n they impose the new key-management requirements on authoritative\n servers not involved in multi-signer configurations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engine 8901 algorithm http https key keys license management path signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8945","type":"specification","body":"IETF","designation":"RFC 8945","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8945.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8945.txt","https://www.rfc-editor.org/rfc/rfc8945.pdf"],"folder":"IETF/RFC-8945","files":{"pdf":{"path":"standards/IETF/RFC-8945/RFC-8945.pdf","sha256":"b93746d574b89308d9f227303ac020b595078e04e9558ba859c0e567b5936c54"},"txt":{"path":"standards/IETF/RFC-8945/RFC-8945.txt","sha256":"f225ac6b0c5c0c1e4c9dc97adb0156faccfebbeaef4e84aebc5fdf727079ae62"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for transaction-level\n authentication using shared secrets and one-way hashing. It can be\n used to authenticate dynamic updates to a DNS zone as coming from an\n approved client or to authenticate responses as coming from an\n approved name server.\n\n No recommendation is made here for distributing the shared secrets;\n it is expected that a network administrator will statically configure\n name servers and clients using some out-of-band mechanism.\n\n This document obsoletes RFCs 2845 and 4635.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availab","scope_keywords":["8945","algorithm","algorithms","authentication","hash","hashing","http","https","key","keys","license","management","policy","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null}],"search_text":"IETF RFC 8945 This document describes a protocol for transaction-level\n authentication using shared secrets and one-way hashing. It can be\n used to authenticate dynamic updates to a DNS zone as coming from an\n approved client or to authenticate responses as coming from an\n approved name server.\n\n No recommendation is made here for distributing the shared secrets;\n it is expected that a network administrator will statically configure\n name servers and clients using some out-of-band mechanism.\n\n This document obsoletes RFCs 2845 and 4635.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availab 8945 algorithm algorithms authentication hash hashing http https key keys license management policy signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 8976","type":"specification","body":"IETF","designation":"RFC 8976","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8976.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8976.txt","https://www.rfc-editor.org/rfc/rfc8976.pdf"],"folder":"IETF/RFC-8976","files":{"pdf":{"path":"standards/IETF/RFC-8976/RFC-8976.pdf","sha256":"eb15bd4e0261d093a990ab11f72523a0492d15eac3f6d8d62430a12f453ab4a3"},"txt":{"path":"standards/IETF/RFC-8976/RFC-8976.txt","sha256":"f3a7d09a6331563ed2deab0ab78d565cc0f471ed23719f296557b8e60cc388c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol and new DNS Resource Record that\n provides a cryptographic message digest over DNS zone data at rest.\n The ZONEMD Resource Record conveys the digest data in the zone\n itself. When used in combination with DNSSEC, ZONEMD allows\n recipients to verify the zone contents for data integrity and origin\n authenticity. This provides assurance that received zone data\n matches published data, regardless of how the zone data has been\n transmitted and received. When used without DNSSEC, ZONEMD functions\n as a checksum, guarding only against unintentional changes.\n\n ZONEMD does not replace DNSSEC: DNSSEC protects individual RRsets\n (DNS data with fine granularity), whereas ZONEMD protects a zone's\n data as a whole, whether consumed by authoritative name servers,\n recursive name servers, or any other applications.\n\n As specified herein, ZONEMD is impractical for large","scope_keywords":["8976","algorithm","algorithms","hash","holder","http","https","key","keys","license","policy","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null}],"search_text":"IETF RFC 8976 This document describes a protocol and new DNS Resource Record that\n provides a cryptographic message digest over DNS zone data at rest.\n The ZONEMD Resource Record conveys the digest data in the zone\n itself. When used in combination with DNSSEC, ZONEMD allows\n recipients to verify the zone contents for data integrity and origin\n authenticity. This provides assurance that received zone data\n matches published data, regardless of how the zone data has been\n transmitted and received. When used without DNSSEC, ZONEMD functions\n as a checksum, guarding only against unintentional changes.\n\n ZONEMD does not replace DNSSEC: DNSSEC protects individual RRsets\n (DNS data with fine granularity), whereas ZONEMD protects a zone's\n data as a whole, whether consumed by authoritative name servers,\n recursive name servers, or any other applications.\n\n As specified herein, ZONEMD is impractical for large 8976 algorithm algorithms hash holder http https key keys license policy presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 9076","type":"specification","body":"IETF","designation":"RFC 9076","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9076.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9076.txt","https://www.rfc-editor.org/rfc/rfc9076.pdf"],"folder":"IETF/RFC-9076","files":{"pdf":{"path":"standards/IETF/RFC-9076/RFC-9076.pdf","sha256":"bcf011e7a5ca52e2f92ec97d96064d6fd9e74fa5bd473af23d539eedf2c785a2"},"txt":{"path":"standards/IETF/RFC-9076/RFC-9076.txt","sha256":"72f6af2881db0300033c3ea7d02f37bf0cd3da09b747eda8b22b8032a4878bf0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the privacy issues associated with the use of\n the DNS by Internet users. It provides general observations about\n typical current privacy practices. It is intended to be an analysis\n of the present situation and does not prescribe solutions. This\n document obsoletes RFC 7626.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o","scope_keywords":["9076","algorithm","encryption","http","https","identification","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 9076 This document describes the privacy issues associated with the use of\n the DNS by Internet users. It provides general observations about\n typical current privacy practices. It is intended to be an analysis\n of the present situation and does not prescribe solutions. This\n document obsoletes RFC 7626.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o 9076 algorithm encryption http https identification license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9103","type":"specification","body":"IETF","designation":"RFC 9103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9103.txt","https://www.rfc-editor.org/rfc/rfc9103.pdf"],"folder":"IETF/RFC-9103","files":{"pdf":{"path":"standards/IETF/RFC-9103/RFC-9103.pdf","sha256":"294de650b5ff004cd7f58ef21b579bc43f9860595cd741a34816d357fa6db71d"},"txt":{"path":"standards/IETF/RFC-9103/RFC-9103.txt","sha256":"5f9c24c816272b2ab19be4306e5ff5dfeb925f429b56837b32d5c3605eed0624"}},"tags":["nested-reference","unchanged"],"summary":"DNS zone transfers are transmitted in cleartext, which gives\n attackers the opportunity to collect the content of a zone by\n eavesdropping on network connections. The DNS Transaction Signature\n (TSIG) mechanism is specified to restrict direct zone transfer to\n authorized clients only, but it does not add confidentiality. This\n document specifies the use of TLS, rather than cleartext, to prevent\n zone content collection via passive monitoring of zone transfers: XFR\n over TLS (XoT). Additionally, this specification updates RFC 1995\n and RFC 5936 with respect to efficient use of TCP connections and RFC\n 7766 with respect to the recommended number of connections between a\n client and server for each transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IET","scope_keywords":["9103","authentication","holder","http","https","license","policies","policy","risk","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9103 DNS zone transfers are transmitted in cleartext, which gives\n attackers the opportunity to collect the content of a zone by\n eavesdropping on network connections. The DNS Transaction Signature\n (TSIG) mechanism is specified to restrict direct zone transfer to\n authorized clients only, but it does not add confidentiality. This\n document specifies the use of TLS, rather than cleartext, to prevent\n zone content collection via passive monitoring of zone transfers: XFR\n over TLS (XoT). Additionally, this specification updates RFC 1995\n and RFC 5936 with respect to efficient use of TCP connections and RFC\n 7766 with respect to the recommended number of connections between a\n client and server for each transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IET 9103 authentication holder http https license policies policy risk signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9250","type":"specification","body":"IETF","designation":"RFC 9250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9250.txt","https://www.rfc-editor.org/rfc/rfc9250.pdf"],"folder":"IETF/RFC-9250","files":{"pdf":{"path":"standards/IETF/RFC-9250/RFC-9250.pdf","sha256":"d5ebbaae0e06cbcb6bcc3326cab1ba50b8d30335e0a2a02a848214b48923c5cb"},"txt":{"path":"standards/IETF/RFC-9250/RFC-9250.txt","sha256":"1d153f1188ef5f9c78754896a46e07515d0d49279887744e6a141bf4ec37e0b1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of QUIC to provide transport\n confidentiality for DNS. The encryption provided by QUIC has similar\n properties to those provided by TLS, while QUIC transport eliminates\n the head-of-line blocking issues inherent with TCP and provides more\n efficient packet-loss recovery than UDP. DNS over QUIC (DoQ) has\n privacy properties similar to DNS over TLS (DoT) specified in RFC\n 7858, and latency characteristics similar to classic DNS over UDP.\n This specification describes the use of DoQ as a general-purpose\n transport for DNS and includes the use of DoQ for stub to recursive,\n recursive to authoritative, and zone transfer scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and ha","scope_keywords":["9250","authentication","encryption","http","https","identification","key","license","management","path","profile","profiles","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9250 This document describes the use of QUIC to provide transport\n confidentiality for DNS. The encryption provided by QUIC has similar\n properties to those provided by TLS, while QUIC transport eliminates\n the head-of-line blocking issues inherent with TCP and provides more\n efficient packet-loss recovery than UDP. DNS over QUIC (DoQ) has\n privacy properties similar to DNS over TLS (DoT) specified in RFC\n 7858, and latency characteristics similar to classic DNS over UDP.\n This specification describes the use of DoQ as a general-purpose\n transport for DNS and includes the use of DoQ for stub to recursive,\n recursive to authoritative, and zone transfer scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and ha 9250 authentication encryption http https identification key license management path profile profiles subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9460","type":"specification","body":"IETF","designation":"RFC 9460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9460.txt","https://www.rfc-editor.org/rfc/rfc9460.pdf"],"folder":"IETF/RFC-9460","files":{"pdf":{"path":"standards/IETF/RFC-9460/RFC-9460.pdf","sha256":"34c29033f90102f41285bb31e9583a3c32e219febd814f46fb5f8998287aa6d5"},"txt":{"path":"standards/IETF/RFC-9460/RFC-9460.txt","sha256":"0741d5743b7b4cd54762e53633b597e442b3d8299b80a9d5f2acec6d9beae433"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the \"SVCB\" (\"Service Binding\") and \"HTTPS\"\n DNS resource record (RR) types to facilitate the lookup of\n information needed to make connections to network services, such as\n for HTTP origins. SVCB records allow a service to be provided from\n multiple alternative endpoints, each with associated parameters (such\n as transport protocol configuration), and are extensible to support\n future uses (such as keys for encrypting the TLS ClientHello). They\n also enable aliasing of apex domains, which is not possible with\n CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see\n RFC 9110, \"HTTP Semantics\"). By providing more information to the\n client before it attempts to establish a connection, these records\n offer potential benefits to both performance and privacy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of","scope_keywords":["9460","http","https","key","keys","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9460 This document specifies the \"SVCB\" (\"Service Binding\") and \"HTTPS\"\n DNS resource record (RR) types to facilitate the lookup of\n information needed to make connections to network services, such as\n for HTTP origins. SVCB records allow a service to be provided from\n multiple alternative endpoints, each with associated parameters (such\n as transport protocol configuration), and are extensible to support\n future uses (such as keys for encrypting the TLS ClientHello). They\n also enable aliasing of apex domains, which is not possible with\n CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see\n RFC 9110, \"HTTP Semantics\"). By providing more information to the\n client before it attempts to establish a connection, these records\n offer potential benefits to both performance and privacy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of 9460 http https key keys license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9471","type":"specification","body":"IETF","designation":"RFC 9471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9471.txt","https://www.rfc-editor.org/rfc/rfc9471.pdf"],"folder":"IETF/RFC-9471","files":{"pdf":{"path":"standards/IETF/RFC-9471/RFC-9471.pdf","sha256":"5e36f330c38ce83ba85431cd8809e5f242ef7ee5737147118d863e7ad9bb883a"},"txt":{"path":"standards/IETF/RFC-9471/RFC-9471.txt","sha256":"ce9ba2f7cf5b6d72fe8dc70b48bb46d792b0621f59c763d6a83ee81ca972277e"}},"tags":["nested-reference","unchanged"],"summary":"The DNS uses glue records to allow iterative clients to find the\n addresses of name servers that are contained within a delegated zone.\n Authoritative servers are expected to return all available glue\n records for in-domain name servers in a referral response. If\n message size constraints prevent the inclusion of all glue records\n for in-domain name servers, the server must set the TC (Truncated)\n flag to inform the client that the response is incomplete and that\n the client should use another transport to retrieve the full\n response. This document updates RFC 1034 to clarify correct server\n behavior.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineer","scope_keywords":["9471","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9471 The DNS uses glue records to allow iterative clients to find the\n addresses of name servers that are contained within a delegated zone.\n Authoritative servers are expected to return all available glue\n records for in-domain name servers in a referral response. If\n message size constraints prevent the inclusion of all glue records\n for in-domain name servers, the server must set the TC (Truncated)\n flag to inform the client that the response is incomplete and that\n the client should use another transport to retrieve the full\n response. This document updates RFC 1034 to clarify correct server\n behavior.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineer 9471 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1035","type":"specification","body":"IETF","designation":"RFC 1035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1035.txt","https://www.rfc-editor.org/rfc/rfc1035.pdf"],"folder":"IETF/RFC-1035","files":{"txt":{"path":"standards/IETF/RFC-1035/RFC-1035.txt","sha256":"d14ae809fc9b41bbcae26bb38c937c9515808b944f3252b00de9fe0e95f4fdfb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 1035 ISI\n November 1987\nObsoletes: RFCs 882, 883, 973\n\n DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION\n\n1. STATUS OF THIS MEMO\n\nThis RFC describes the details of the domain system and protocol, and\nassumes that the reader is familiar with the concepts discussed in a\ncompanion RFC, \"Domain Names - Concepts and Facilities\" [RFC-1034].\n\nThe domain system is a mixture of functions and data types which are an\nofficial protocol and functions and data types which are still\nexperimental. Since the domain system is intentionally extensible, new\ndata types and experimental behavior should always be expected in parts\nof the system beyond the official protocol. The official protocol parts\ninclude standard queries, responses and the Internet class RR data\nformats (e.g., host addresses). Since the previous RFC set, several\ndefinitions have ch","scope_keywords":["1035"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1274","folder":"IETF/RFC-1274","source":"IETF/RFC-1274/RFC-1274.txt","version":null},{"body":"IETF","designation":"RFC 1279","folder":"IETF/RFC-1279","source":"IETF/RFC-1279/RFC-1279.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1464","folder":"IETF/RFC-1464","source":"IETF/RFC-1464/RFC-1464.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 1486","folder":"IETF/RFC-1486","source":"IETF/RFC-1486/RFC-1486.txt","version":null},{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1535","folder":"IETF/RFC-1535","source":"IETF/RFC-1535/RFC-1535.txt","version":null},{"body":"IETF","designation":"RFC 1536","folder":"IETF/RFC-1536","source":"IETF/RFC-1536/RFC-1536.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1609","folder":"IETF/RFC-1609","source":"IETF/RFC-1609/RFC-1609.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null},{"body":"IETF","designation":"RFC 1712","folder":"IETF/RFC-1712","source":"IETF/RFC-1712/RFC-1712.txt","version":null},{"body":"IETF","designation":"RFC 1788","folder":"IETF/RFC-1788","source":"IETF/RFC-1788/RFC-1788.txt","version":null},{"body":"IETF","designation":"RFC 1794","folder":"IETF/RFC-1794","source":"IETF/RFC-1794/RFC-1794.txt","version":null},{"body":"IETF","designation":"RFC 1798","folder":"IETF/RFC-1798","source":"IETF/RFC-1798/RFC-1798.txt","version":null},{"body":"IETF","designation":"RFC 1876","folder":"IETF/RFC-1876","source":"IETF/RFC-1876/RFC-1876.txt","version":null},{"body":"IETF","designation":"RFC 1877","folder":"IETF/RFC-1877","source":"IETF/RFC-1877/RFC-1877.txt","version":null},{"body":"IETF","designation":"RFC 1886","folder":"IETF/RFC-1886","source":"IETF/RFC-1886/RFC-1886.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 1982","folder":"IETF/RFC-1982","source":"IETF/RFC-1982/RFC-1982.txt","version":null},{"body":"IETF","designation":"RFC 1995","folder":"IETF/RFC-1995","source":"IETF/RFC-1995/RFC-1995.txt","version":null},{"body":"IETF","designation":"RFC 1996","folder":"IETF/RFC-1996","source":"IETF/RFC-1996/RFC-1996.txt","version":null},{"body":"IETF","designation":"RFC 2016","folder":"IETF/RFC-2016","source":"IETF/RFC-2016/RFC-2016.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2137","folder":"IETF/RFC-2137","source":"IETF/RFC-2137/RFC-2137.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2181","folder":"IETF/RFC-2181","source":"IETF/RFC-2181/RFC-2181.txt","version":null},{"body":"IETF","designation":"RFC 2182","folder":"IETF/RFC-2182","source":"IETF/RFC-2182/RFC-2182.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2240","folder":"IETF/RFC-2240","source":"IETF/RFC-2240/RFC-2240.txt","version":null},{"body":"IETF","designation":"RFC 2308","folder":"IETF/RFC-2308","source":"IETF/RFC-2308/RFC-2308.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2536","folder":"IETF/RFC-2536","source":"IETF/RFC-2536/RFC-2536.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2539","folder":"IETF/RFC-2539","source":"IETF/RFC-2539/RFC-2539.txt","version":null},{"body":"IETF","designation":"RFC 2540","folder":"IETF/RFC-2540","source":"IETF/RFC-2540/RFC-2540.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2606","folder":"IETF/RFC-2606","source":"IETF/RFC-2606/RFC-2606.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2671","folder":"IETF/RFC-2671","source":"IETF/RFC-2671/RFC-2671.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2673","folder":"IETF/RFC-2673","source":"IETF/RFC-2673/RFC-2673.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2826","folder":"IETF/RFC-2826","source":"IETF/RFC-2826/RFC-2826.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3225","folder":"IETF/RFC-3225","source":"IETF/RFC-3225/RFC-3225.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 3375","folder":"IETF/RFC-3375","source":"IETF/RFC-3375/RFC-3375.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3425","folder":"IETF/RFC-3425","source":"IETF/RFC-3425/RFC-3425.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4892","folder":"IETF/RFC-4892","source":"IETF/RFC-4892/RFC-4892.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4955","folder":"IETF/RFC-4955","source":"IETF/RFC-4955/RFC-4955.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7706","folder":"IETF/RFC-7706","source":"IETF/RFC-7706/RFC-7706.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7830","folder":"IETF/RFC-7830","source":"IETF/RFC-7830/RFC-7830.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1035 Network Working Group P. Mockapetris\nRequest for Comments: 1035 ISI\n November 1987\nObsoletes: RFCs 882, 883, 973\n\n DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION\n\n1. STATUS OF THIS MEMO\n\nThis RFC describes the details of the domain system and protocol, and\nassumes that the reader is familiar with the concepts discussed in a\ncompanion RFC, \"Domain Names - Concepts and Facilities\" [RFC-1034].\n\nThe domain system is a mixture of functions and data types which are an\nofficial protocol and functions and data types which are still\nexperimental. Since the domain system is intentionally extensible, new\ndata types and experimental behavior should always be expected in parts\nof the system beyond the official protocol. The official protocol parts\ninclude standard queries, responses and the Internet class RR data\nformats (e.g., host addresses). Since the previous RFC set, several\ndefinitions have ch 1035 nested-reference unchanged"},{"id":"IETF RFC 1609","type":"specification","body":"IETF","designation":"RFC 1609","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1609.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1609.txt","https://www.rfc-editor.org/rfc/rfc1609.pdf"],"folder":"IETF/RFC-1609","files":{"txt":{"path":"standards/IETF/RFC-1609/RFC-1609.txt","sha256":"9a7333c18c265ad6fa6085f756ce34e5fe1d09948ca93cd01313caf9e266f546"}},"tags":["nested-reference","unchanged"],"summary":"There is a need for a framework wherein the infrastructural and\n service related information about communication networks can be made\n accessible from all places and at all times in a reasonably efficient\n manner and with reasonable accuracy. This document presents a model\n in which a communication network with all its related details and\n descriptions can be represented in the X.500 Directory. Schemas of\n objects and their attributes which may be used for this purpose are\n presented. The model envisages physical objects and several logical\n abstractions of the physical objects.\n\nMansfield, Johannsen & Knopper [Page 1]\n\f\nRFC 1609 Charting Networks in the X.500 Directory March 1994","scope_keywords":["1609","attribute","attributes","management","path","pid","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1609 There is a need for a framework wherein the infrastructural and\n service related information about communication networks can be made\n accessible from all places and at all times in a reasonably efficient\n manner and with reasonable accuracy. This document presents a model\n in which a communication network with all its related details and\n descriptions can be represented in the X.500 Directory. Schemas of\n objects and their attributes which may be used for this purpose are\n presented. The model envisages physical objects and several logical\n abstractions of the physical objects.\n\nMansfield, Johannsen & Knopper [Page 1]\n\f\nRFC 1609 Charting Networks in the X.500 Directory March 1994 1609 attribute attributes management path pid policy presentation nested-reference unchanged"},{"id":"IETF RFC 1794","type":"specification","body":"IETF","designation":"RFC 1794","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1794.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1794.txt","https://www.rfc-editor.org/rfc/rfc1794.pdf"],"folder":"IETF/RFC-1794","files":{"txt":{"path":"standards/IETF/RFC-1794/RFC-1794.txt","sha256":"cb6b350c6cf2c9630bb4c8ce51b2270ff1fe4877ae968d5d97c192ca8e148098"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Brisco\nRequest for Comments: 1794 Rutgers University\nCategory: Informational April 1995\n\n DNS Support for Load Balancing\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This RFC is meant to first chronicle a foray into the IETF DNS\n Working Group, discuss other possible alternatives to\n provide/simulate load balancing support for DNS, and to provide an\n ultimate, flexible solution for providing DNS support for balancing\n loads of many types.\n\n2. History\n\n The history of this probably dates back well before my own time - so\n undoubtedly some holes are here. Hopefully they can be filled in by\n other authors.\n\n Initially; \"load balancing\" was intended to permit the Domain Name\n System (DNS) [1] agents to support ","scope_keywords":["1794","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 1794 Network Working Group T. Brisco\nRequest for Comments: 1794 Rutgers University\nCategory: Informational April 1995\n\n DNS Support for Load Balancing\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This RFC is meant to first chronicle a foray into the IETF DNS\n Working Group, discuss other possible alternatives to\n provide/simulate load balancing support for DNS, and to provide an\n ultimate, flexible solution for providing DNS support for balancing\n loads of many types.\n\n2. History\n\n The history of this probably dates back well before my own time - so\n undoubtedly some holes are here. Hopefully they can be filled in by\n other authors.\n\n Initially; \"load balancing\" was intended to permit the Domain Name\n System (DNS) [1] agents to support  1794 pid nested-reference unchanged"},{"id":"IETF RFC 1996","type":"specification","body":"IETF","designation":"RFC 1996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1996.txt","https://www.rfc-editor.org/rfc/rfc1996.pdf"],"folder":"IETF/RFC-1996","files":{"txt":{"path":"standards/IETF/RFC-1996/RFC-1996.txt","sha256":"ae556f395719b0befb6269a25820c7457c747e03a44958407b216e1ef56cc2ae"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the NOTIFY opcode for DNS, by which a master\n server advises a set of slave servers that the master's data has been\n changed and that a query should be initiated to discover the new\n data.\n\n1. Rationale and Scope","scope_keywords":["1996"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1995","folder":"IETF/RFC-1995","source":"IETF/RFC-1995/RFC-1995.txt","version":null},{"body":"IETF","designation":"RFC 2136","folder":"IETF/RFC-2136","source":"IETF/RFC-2136/RFC-2136.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1996 This memo describes the NOTIFY opcode for DNS, by which a master\n server advises a set of slave servers that the master's data has been\n changed and that a query should be initiated to discover the new\n data.\n\n1. Rationale and Scope 1996 nested-reference unchanged"},{"id":"IETF RFC 2074","type":"specification","body":"IETF","designation":"RFC 2074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2074.txt","https://www.rfc-editor.org/rfc/rfc2074.pdf"],"folder":"IETF/RFC-2074","files":{"txt":{"path":"standards/IETF/RFC-2074/RFC-2074.txt","sha256":"27a110d572fa025085c6de07b549ec8575e7b4cfd71ebc63fa40648a68dff45e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Bierman\nRequest for Comments: 2074 Cisco Systems\nCategory: Standards Track R. Iddon\n AXON Networks,Inc.\n January 1997\n\n Remote Network Monitoring MIB Protocol Identifiers\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n1 Introduction .................................................... 3\n2 The SNMP Network Management Framework ........................... 3\n2.1 Object Definitions ............................................ 3\n3 Overview ........................................................ 3\n3.1 Terms ...............................","scope_keywords":["2074","algorithm","algorithms","attribute","attributes","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null}],"search_text":"IETF RFC 2074 Network Working Group A. Bierman\nRequest for Comments: 2074 Cisco Systems\nCategory: Standards Track R. Iddon\n AXON Networks,Inc.\n January 1997\n\n Remote Network Monitoring MIB Protocol Identifiers\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n1 Introduction .................................................... 3\n2 The SNMP Network Management Framework ........................... 3\n2.1 Object Definitions ............................................ 3\n3 Overview ........................................................ 3\n3.1 Terms ............................... 2074 algorithm algorithms attribute attributes http management nested-reference unchanged"},{"id":"IETF RFC 2101","type":"specification","body":"IETF","designation":"RFC 2101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2101.txt","https://www.rfc-editor.org/rfc/rfc2101.pdf"],"folder":"IETF/RFC-2101","files":{"txt":{"path":"standards/IETF/RFC-2101/RFC-2101.txt","sha256":"51c019fefddc906ab86f10f967795db565772b4e97e611f9a069ec608301f5cc"}},"tags":["nested-reference","unchanged"],"summary":"The main purpose of this note is to clarify the current\n interpretation of the 32-bit IP version 4 address space, whose\n significance has changed substantially since it was originally\n defined. A short section on IPv6 addresses mentions the main points\n of similarity with, and difference from, IPv4.","scope_keywords":["2101","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2101 The main purpose of this note is to clarify the current\n interpretation of the 32-bit IP version 4 address space, whose\n significance has changed substantially since it was originally\n defined. A short section on IPv6 addresses mentions the main points\n of similarity with, and difference from, IPv4. 2101 key nested-reference unchanged"},{"id":"IETF RFC 2240","type":"specification","body":"IETF","designation":"RFC 2240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2240.txt","https://www.rfc-editor.org/rfc/rfc2240.pdf"],"folder":"IETF/RFC-2240","files":{"txt":{"path":"standards/IETF/RFC-2240/RFC-2240.txt","sha256":"20aaa38c99366e1c4914d5ca3dd3228dfacd897a9dce0c91ffc671b36bd05cc7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group O. Vaughan\nRequest for Comments: 2240 Vaughan Enterprises\nCategory: Informational November 1997\n\n A Legal Basis for Domain Name Allocation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n\n 2. Overview of the domain space . . . . . . . . . . . . . . . . 2\n\n 3. Possible solutions to name exhaustion . . . . . . . . . . . 3\n\n 4. Proposed creation of new SLDs . . . . . . . . . . . . . . . 3\n 4.1 The world is not flat so why should domains be? . . . . . . 4\n 4.2 The case for legal names . . . . . . . . . . . . . . . . . 4\n 4.3 Allocation of legal SLDs . . . . . . . . . . . . .","scope_keywords":["2240","holder","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null}],"search_text":"IETF RFC 2240 Network Working Group O. Vaughan\nRequest for Comments: 2240 Vaughan Enterprises\nCategory: Informational November 1997\n\n A Legal Basis for Domain Name Allocation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n\n 2. Overview of the domain space . . . . . . . . . . . . . . . . 2\n\n 3. Possible solutions to name exhaustion . . . . . . . . . . . 3\n\n 4. Proposed creation of new SLDs . . . . . . . . . . . . . . . 3\n 4.1 The world is not flat so why should domains be? . . . . . . 4\n 4.2 The case for legal names . . . . . . . . . . . . . . . . . 4\n 4.3 Allocation of legal SLDs . . . . . . . . . . . . . 2240 holder policy registered nested-reference unchanged"},{"id":"IETF RFC 2327","type":"specification","body":"IETF","designation":"RFC 2327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2327.txt","https://www.rfc-editor.org/rfc/rfc2327.pdf"],"folder":"IETF/RFC-2327","files":{"txt":{"path":"standards/IETF/RFC-2327/RFC-2327.txt","sha256":"a063265b3e357e84b9b624da27846af3c6e7643483640e0e39c048218429d5ad"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Session Description Protocol, SDP. SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation.\n\n This document is a product of the Multiparty Multimedia Session\n Control (MMUSIC) working group of the Internet Engineering Task\n Force. Comments are solicited and should be addressed to the working\n group's mailing list at confctrl@isi.edu and/or the authors.\n\n1. Introduction\n\n On the Internet multicast backbone (Mbone), a session directory tool\n is used to advertise multimedia conferences and communicate the\n conference addresses and conference tool-specific information\n necessary for participation. This document defines a session\n description protocol for this purpose, and for general real-time\n multimedia session description purposes. This memo does not descr","scope_keywords":["2327","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 2771","folder":"IETF/RFC-2771","source":"IETF/RFC-2771/RFC-2771.txt","version":null},{"body":"IETF","designation":"RFC 2833","folder":"IETF/RFC-2833","source":"IETF/RFC-2833/RFC-2833.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 3009","folder":"IETF/RFC-3009","source":"IETF/RFC-3009/RFC-3009.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3048","folder":"IETF/RFC-3048","source":"IETF/RFC-3048/RFC-3048.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3362","folder":"IETF/RFC-3362","source":"IETF/RFC-3362/RFC-3362.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3524","folder":"IETF/RFC-3524","source":"IETF/RFC-3524/RFC-3524.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3556","folder":"IETF/RFC-3556","source":"IETF/RFC-3556/RFC-3556.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4091","folder":"IETF/RFC-4091","source":"IETF/RFC-4091/RFC-4091.txt","version":null},{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 2327 This document defines the Session Description Protocol, SDP. SDP is\n intended for describing multimedia sessions for the purposes of\n session announcement, session invitation, and other forms of\n multimedia session initiation.\n\n This document is a product of the Multiparty Multimedia Session\n Control (MMUSIC) working group of the Internet Engineering Task\n Force. Comments are solicited and should be addressed to the working\n group's mailing list at confctrl@isi.edu and/or the authors.\n\n1. Introduction\n\n On the Internet multicast backbone (Mbone), a session directory tool\n is used to advertise multimedia conferences and communicate the\n conference addresses and conference tool-specific information\n necessary for participation. This document defines a session\n description protocol for this purpose, and for general real-time\n multimedia session description purposes. This memo does not descr 2327 key nested-reference unchanged"},{"id":"IETF RFC 2486","type":"specification","body":"IETF","designation":"RFC 2486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2486.txt","https://www.rfc-editor.org/rfc/rfc2486.pdf"],"folder":"IETF/RFC-2486","files":{"txt":{"path":"standards/IETF/RFC-2486/RFC-2486.txt","sha256":"d1aaceb75f0a04139d08b79aa3faf534c93ed8cb8aa297b3d67c7dbe65f32e0c"}},"tags":["nested-reference","unchanged"],"summary":"In order to enhance the interoperability of roaming and tunneling\n services, it is desirable to have a standardized method for\n identifying users. This document proposes syntax for the Network\n Access Identifier (NAI), the userID submitted by the client during\n PPP authentication. It is expected that this will be of interest for\n support of roaming as well as tunneling. \"Roaming capability\" may be\n loosely defined as the ability to use any one of multiple Internet\n service providers (ISPs), while maintaining a formal, customer-vendor\n relationship with only one. Examples of where roaming capabilities\n might be required include ISP \"confederations\" and ISP-provided\n corporate network access support.\n\n2. Introduction\n\n Considerable interest has arisen recently in a set of features that\n fit within the general category of \"roaming capability\" for dialup\n Internet users. Interested parties h","scope_keywords":["2486","authentication","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null}],"search_text":"IETF RFC 2486 In order to enhance the interoperability of roaming and tunneling\n services, it is desirable to have a standardized method for\n identifying users. This document proposes syntax for the Network\n Access Identifier (NAI), the userID submitted by the client during\n PPP authentication. It is expected that this will be of interest for\n support of roaming as well as tunneling. \"Roaming capability\" may be\n loosely defined as the ability to use any one of multiple Internet\n service providers (ISPs), while maintaining a formal, customer-vendor\n relationship with only one. Examples of where roaming capabilities\n might be required include ISP \"confederations\" and ISP-provided\n corporate network access support.\n\n2. Introduction\n\n Considerable interest has arisen recently in a set of features that\n fit within the general category of \"roaming capability\" for dialup\n Internet users. Interested parties h 2486 authentication key pid nested-reference unchanged"},{"id":"IETF RFC 2543","type":"specification","body":"IETF","designation":"RFC 2543","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2543.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2543.txt","https://www.rfc-editor.org/rfc/rfc2543.pdf"],"folder":"IETF/RFC-2543","files":{"txt":{"path":"standards/IETF/RFC-2543/RFC-2543.txt","sha256":"ef3006d940a782c702d44364b845ae828253955ecb5fbfd6d42377223f366a21"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) is an application-layer control\n (signaling) protocol for creating, modifying and terminating sessions\n with one or more participants. These sessions include Internet\n multimedia conferences, Internet telephone calls and multimedia\n distribution. Members in a session can communicate via multicast or\n via a mesh of unicast relations, or a combination of these.\n\nHandley, et al. Standards Track [Page 1]\n\f\nRFC 2543 SIP: Session Initiation Protocol March 1999\n\n SIP invitations used to create sessions carry session descriptions\n which allow participants to agree on a set of compatible media types.\n SIP supports user mobility by proxying and redirecting requests to\n the user's current location. Users can register their current\n location. SIP is not tied to any particular conference control\n protocol. SIP is designed to be independent of the lower-layer\n tra","scope_keywords":["2543","attribute","attributes","authorization","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2824","folder":"IETF/RFC-2824","source":"IETF/RFC-2824/RFC-2824.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2976","folder":"IETF/RFC-2976","source":"IETF/RFC-2976/RFC-2976.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3087","folder":"IETF/RFC-3087","source":"IETF/RFC-3087/RFC-3087.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3262","folder":"IETF/RFC-3262","source":"IETF/RFC-3262/RFC-3262.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3362","folder":"IETF/RFC-3362","source":"IETF/RFC-3362/RFC-3362.txt","version":null},{"body":"IETF","designation":"RFC 3407","folder":"IETF/RFC-3407","source":"IETF/RFC-3407/RFC-3407.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4475","folder":"IETF/RFC-4475","source":"IETF/RFC-4475/RFC-4475.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 2543 The Session Initiation Protocol (SIP) is an application-layer control\n (signaling) protocol for creating, modifying and terminating sessions\n with one or more participants. These sessions include Internet\n multimedia conferences, Internet telephone calls and multimedia\n distribution. Members in a session can communicate via multicast or\n via a mesh of unicast relations, or a combination of these.\n\nHandley, et al. Standards Track [Page 1]\n\f\nRFC 2543 SIP: Session Initiation Protocol March 1999\n\n SIP invitations used to create sessions carry session descriptions\n which allow participants to agree on a set of compatible media types.\n SIP supports user mobility by proxying and redirecting requests to\n the user's current location. Users can register their current\n location. SIP is not tied to any particular conference control\n protocol. SIP is designed to be independent of the lower-layer\n tra 2543 attribute attributes authorization encryption key nested-reference unchanged"},{"id":"IETF RFC 2566","type":"specification","body":"IETF","designation":"RFC 2566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2566.txt","https://www.rfc-editor.org/rfc/rfc2566.pdf"],"folder":"IETF/RFC-2566","files":{"txt":{"path":"standards/IETF/RFC-2566/RFC-2566.txt","sha256":"2bf2cf81e0e5b6c592b82c5bf96d76c1c87a3cdbde4138fcb5b2f3fdb65506b5"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes a\n simplified model consisting of abstract objects, their attributes,\n and their operations that is independent of encoding and transport.\n The model consists of a Printer and a Job object. A Job optionally\n supports multiple documents. IPP 1.0 semantics allow end-users and\n operators to query printer capabilities, submit print jobs, inquire\n about the status of print jobs and printers, and cancel print jobs.\n This document also addresses security, internationalization, and\n directory issues.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and ","scope_keywords":["2566","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null}],"search_text":"IETF RFC 2566 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes a\n simplified model consisting of abstract objects, their attributes,\n and their operations that is independent of encoding and transport.\n The model consists of a Printer and a Job object. A Job optionally\n supports multiple documents. IPP 1.0 semantics allow end-users and\n operators to query printer capabilities, submit print jobs, inquire\n about the status of print jobs and printers, and cancel print jobs.\n This document also addresses security, internationalization, and\n directory issues.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and  2566 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 2611","type":"specification","body":"IETF","designation":"RFC 2611","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2611.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2611.txt","https://www.rfc-editor.org/rfc/rfc2611.pdf"],"folder":"IETF/RFC-2611","files":{"txt":{"path":"standards/IETF/RFC-2611/RFC-2611.txt","sha256":"a34e62721e8c5156101c05bc4eea21e5433167c1ca67cab7fbe3fe93200406e0"}},"tags":["nested-reference","unchanged"],"summary":"The URN WG has defined a syntax for Uniform Resource Names (URNs)\n [RFC2141], as well as some proposed mechanisms for their resolution\n and use in Internet applications ([RFC2168, RFC2169]). The whole\n rests on the concept of individual \"namespaces\" within the URN\n structure. Apart from proof-of-concept namespaces, the use of\n existing identifiers in URNs has been discussed ([RFC2288]), and this\n document lays out general definitions of and mechanisms for\n establishing URN \"namespaces\".","scope_keywords":["2611","identification","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3085","folder":"IETF/RFC-3085","source":"IETF/RFC-3085/RFC-3085.txt","version":null},{"body":"IETF","designation":"RFC 3187","folder":"IETF/RFC-3187","source":"IETF/RFC-3187/RFC-3187.txt","version":null},{"body":"IETF","designation":"RFC 3188","folder":"IETF/RFC-3188","source":"IETF/RFC-3188/RFC-3188.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null}],"search_text":"IETF RFC 2611 The URN WG has defined a syntax for Uniform Resource Names (URNs)\n [RFC2141], as well as some proposed mechanisms for their resolution\n and use in Internet applications ([RFC2168, RFC2169]). The whole\n rests on the concept of individual \"namespaces\" within the URN\n structure. Apart from proof-of-concept namespaces, the use of\n existing identifiers in URNs has been discussed ([RFC2288]), and this\n document lays out general definitions of and mechanisms for\n establishing URN \"namespaces\". 2611 identification key registered nested-reference unchanged"},{"id":"IETF RFC 2671","type":"specification","body":"IETF","designation":"RFC 2671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2671.txt","https://www.rfc-editor.org/rfc/rfc2671.pdf"],"folder":"IETF/RFC-2671","files":{"txt":{"path":"standards/IETF/RFC-2671/RFC-2671.txt","sha256":"895dc73862a016872dc799123be70f058687a05275e1696befde95976cf4a423"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System's wire protocol includes a number of fixed\n fields whose range has been or soon will be exhausted and does not\n allow clients to advertise their capabilities to servers. This\n document describes backward compatible mechanisms for allowing the\n protocol to grow.\n\n1 - Rationale and Scope","scope_keywords":["2671","attribute","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2673","folder":"IETF/RFC-2673","source":"IETF/RFC-2673/RFC-2673.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3225","folder":"IETF/RFC-3225","source":"IETF/RFC-3225/RFC-3225.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5001","folder":"IETF/RFC-5001","source":"IETF/RFC-5001/RFC-5001.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 2671 The Domain Name System's wire protocol includes a number of fixed\n fields whose range has been or soon will be exhausted and does not\n allow clients to advertise their capabilities to servers. This\n document describes backward compatible mechanisms for allowing the\n protocol to grow.\n\n1 - Rationale and Scope 2671 attribute path nested-reference unchanged"},{"id":"IETF RFC 2673","type":"specification","body":"IETF","designation":"RFC 2673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2673.txt","https://www.rfc-editor.org/rfc/rfc2673.pdf"],"folder":"IETF/RFC-2673","files":{"txt":{"path":"standards/IETF/RFC-2673/RFC-2673.txt","sha256":"ea4ab38d66d44b29b43e1e9fd4e60e2e9f257ab2fdfe1c16d7b386a60f20c47f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crawford\nRequest for Comments: 2673 Fermilab\nCategory: Standards Track August 1999\n\n Binary Labels in the Domain Name System\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction and Terminology\n\n This document defines a \"Bit-String Label\" which may appear within\n domain names. This new label type compactly represents a sequence of\n \"One-Bit Labels\" and enables resource records to be stored at any\n bit-boundary in a binary-named section of the domain name tree.","scope_keywords":["2673","key","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null}],"search_text":"IETF RFC 2673 Network Working Group M. Crawford\nRequest for Comments: 2673 Fermilab\nCategory: Standards Track August 1999\n\n Binary Labels in the Domain Name System\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction and Terminology\n\n This document defines a \"Bit-String Label\" which may appear within\n domain names. This new label type compactly represents a sequence of\n \"One-Bit Labels\" and enables resource records to be stored at any\n bit-boundary in a binary-named section of the domain name tree. 2673 key presentation signature nested-reference unchanged"},{"id":"IETF RFC 2806","type":"specification","body":"IETF","designation":"RFC 2806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2806.txt","https://www.rfc-editor.org/rfc/rfc2806.pdf"],"folder":"IETF/RFC-2806","files":{"txt":{"path":"standards/IETF/RFC-2806/RFC-2806.txt","sha256":"c36404711d5b609b463ca865eb7997e391395a86014f69c37e7ca4df4b57703f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies URL (Uniform Resource Locator) schemes \"tel\",\n \"fax\" and \"modem\" for specifying the location of a terminal in the\n phone network and the connection types (modes of operation) that can\n be used to connect to that entity. This specification covers voice\n calls (normal phone calls, answering machines and voice messaging\n systems), facsimile (telefax) calls and data calls, both for POTS and\n digital/mobile subscribers.","scope_keywords":["2806","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null}],"search_text":"IETF RFC 2806 This document specifies URL (Uniform Resource Locator) schemes \"tel\",\n \"fax\" and \"modem\" for specifying the location of a terminal in the\n phone network and the connection types (modes of operation) that can\n be used to connect to that entity. This specification covers voice\n calls (normal phone calls, answering machines and voice messaging\n systems), facsimile (telefax) calls and data calls, both for POTS and\n digital/mobile subscribers. 2806 identification key nested-reference unchanged"},{"id":"IETF RFC 2848","type":"specification","body":"IETF","designation":"RFC 2848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2848.txt","https://www.rfc-editor.org/rfc/rfc2848.pdf"],"folder":"IETF/RFC-2848","files":{"txt":{"path":"standards/IETF/RFC-2848/RFC-2848.txt","sha256":"76acef71f1b7cfbc2a6498a73cec7b1579ac7bb7b3896c212195774ee2313438"}},"tags":["nested-reference","unchanged"],"summary":"This document contains the specification of the PINT Service Protocol\n 1.0, which defines a protocol for invoking certain telephone services\n from an IP network. These services include placing basic calls,\n sending and receiving faxes, and receiving content over the\n telephone. The protocol is specified as a set of enhancements and\n additions to the SIP 2.0 and SDP protocols.","scope_keywords":["2848","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 2848 This document contains the specification of the PINT Service Protocol\n 1.0, which defines a protocol for invoking certain telephone services\n from an IP network. These services include placing basic calls,\n sending and receiving faxes, and receiving content over the\n telephone. The protocol is specified as a set of enhancements and\n additions to the SIP 2.0 and SDP protocols. 2848 attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 2870","type":"specification","body":"IETF","designation":"RFC 2870","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2870.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2870.txt","https://www.rfc-editor.org/rfc/rfc2870.pdf"],"folder":"IETF/RFC-2870","files":{"txt":{"path":"standards/IETF/RFC-2870/RFC-2870.txt","sha256":"0ecdb90389ba0ccc2139da118269a661f16f65987a32fa7e0fcb59c254141b83"}},"tags":["nested-reference","unchanged"],"summary":"As the internet becomes increasingly critical to the world's social\n and economic infrastructure, attention has rightly focused on the\n correct, safe, reliable, and secure operation of the internet\n infrastructure itself. The root domain name servers are seen as a\n crucial part of that technical infrastructure. The primary focus of\n this document is to provide guidelines for operation of the root name\n servers. Other major zone server operators (gTLDs, ccTLDs, major\n zones) may also find it useful. These guidelines are intended to\n meet the perceived societal needs without overly prescribing\n technical details.\n\n1. Background\n\n The resolution of domain names on the internet is critically\n dependent on the proper, safe, and secure operation of the root\n domain name servers. Currently, these dozen or so servers are\n provided and operated by a very competent and trusted group of\n volunteers","scope_keywords":["2870","authentication","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 3258","folder":"IETF/RFC-3258","source":"IETF/RFC-3258/RFC-3258.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null}],"search_text":"IETF RFC 2870 As the internet becomes increasingly critical to the world's social\n and economic infrastructure, attention has rightly focused on the\n correct, safe, reliable, and secure operation of the internet\n infrastructure itself. The root domain name servers are seen as a\n crucial part of that technical infrastructure. The primary focus of\n this document is to provide guidelines for operation of the root name\n servers. Other major zone server operators (gTLDs, ccTLDs, major\n zones) may also find it useful. These guidelines are intended to\n meet the perceived societal needs without overly prescribing\n technical details.\n\n1. Background\n\n The resolution of domain names on the internet is critically\n dependent on the proper, safe, and secure operation of the root\n domain name servers. Currently, these dozen or so servers are\n provided and operated by a very competent and trusted group of\n volunteers 2870 authentication trust validation nested-reference unchanged"},{"id":"IETF RFC 2874","type":"specification","body":"IETF","designation":"RFC 2874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2874.txt","https://www.rfc-editor.org/rfc/rfc2874.pdf"],"folder":"IETF/RFC-2874","files":{"txt":{"path":"standards/IETF/RFC-2874/RFC-2874.txt","sha256":"0b1d677a2840bdda84db0118f15784969b75b75709ed0b027e23cfa8b20c3029"}},"tags":["nested-reference","unchanged"],"summary":"This document defines changes to the Domain Name System to support\n renumberable and aggregatable IPv6 addressing. The changes include a\n new resource record type to store an IPv6 address in a manner which\n expedites network renumbering and updated definitions of existing\n query types that return Internet addresses as part of additional\n section processing.\n\n For lookups keyed on IPv6 addresses (often called reverse lookups),\n this document defines a new zone structure which allows a zone to be\n used without modification for parallel copies of an address space (as\n for a multihomed provider or site) and across network renumbering\n events.\n\nCrawford, et al. Standards Track [Page 1]\n\f\nRFC 2874 IPv6 DNS July 2000","scope_keywords":["2874","key","presentation","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 3364","folder":"IETF/RFC-3364","source":"IETF/RFC-3364/RFC-3364.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null}],"search_text":"IETF RFC 2874 This document defines changes to the Domain Name System to support\n renumberable and aggregatable IPv6 addressing. The changes include a\n new resource record type to store an IPv6 address in a manner which\n expedites network renumbering and updated definitions of existing\n query types that return Internet addresses as part of additional\n section processing.\n\n For lookups keyed on IPv6 addresses (often called reverse lookups),\n this document defines a new zone structure which allows a zone to be\n used without modification for parallel copies of an address space (as\n for a multihomed provider or site) and across network renumbering\n events.\n\nCrawford, et al. Standards Track [Page 1]\n\f\nRFC 2874 IPv6 DNS July 2000 2874 key presentation preservation nested-reference unchanged"},{"id":"IETF RFC 2911","type":"specification","body":"IETF","designation":"RFC 2911","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2911.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2911.txt","https://www.rfc-editor.org/rfc/rfc2911.pdf"],"folder":"IETF/RFC-2911","files":{"txt":{"path":"standards/IETF/RFC-2911/RFC-2911.txt","sha256":"9e213bc45b14ce7fe7b16c219cd694368f72b4b9b8333a9de506b395b281f2fd"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes a\n simplified model consisting of abstract objects, their attributes,\n and their operations that is independent of encoding and transport.\n The model consists of a Printer and a Job object. A Job optionally\n supports multiple documents. IPP 1.1 semantics allow end-users and\n operators to query printer capabilities, submit print jobs, inquire\n about the status of print jobs and printers, cancel, hold, release,\n and restart print jobs. IPP 1.1 semantics allow operators to pause,\n resume, and purge (jobs from) Printer objects. This document also\n addresses security, internationalization, and directory issues.\n\nHastings, et al. ","scope_keywords":["2911","attribute","attributes","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null}],"search_text":"IETF RFC 2911 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes a\n simplified model consisting of abstract objects, their attributes,\n and their operations that is independent of encoding and transport.\n The model consists of a Printer and a Job object. A Job optionally\n supports multiple documents. IPP 1.1 semantics allow end-users and\n operators to query printer capabilities, submit print jobs, inquire\n about the status of print jobs and printers, cancel, hold, release,\n and restart print jobs. IPP 1.1 semantics allow operators to pause,\n resume, and purge (jobs from) Printer objects. This document also\n addresses security, internationalization, and directory issues.\n\nHastings, et al.  2911 attribute attributes http nested-reference unchanged"},{"id":"IETF RFC 2977","type":"specification","body":"IETF","designation":"RFC 2977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2977.txt","https://www.rfc-editor.org/rfc/rfc2977.pdf"],"folder":"IETF/RFC-2977","files":{"txt":{"path":"standards/IETF/RFC-2977/RFC-2977.txt","sha256":"101887e10992caa0cd8d2406eb5c8489b10ea5b20e6634849cd2810b1c839ae6"}},"tags":["nested-reference","unchanged"],"summary":"The Mobile IP and Authentication, Authorization, Accounting (AAA)\n working groups are currently looking at defining the requirements for\n Authentication, Authorization, and Accounting. This document\n contains the requirements which would have to be supported by a AAA\n service to aid in providing Mobile IP services.\n\n1. Introduction\n\n Clients obtain Internet services by negotiating a point of attachment\n to a \"home domain\", generally from an ISP, or other organization from\n which service requests are made, and fulfilled. With the increasing\n popularity of mobile devices, a need has been generated to allow\n users to attach to any domain convenient to their current location.\n In this way, a client needs access to resources being provided by an\n administrative domain different than their home domain (called a\n \"foreign domain\"). The need for service from a foreign domain\n requires, in many m","scope_keywords":["2977","audit","authentication","authorization","credential","credentials","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null}],"search_text":"IETF RFC 2977 The Mobile IP and Authentication, Authorization, Accounting (AAA)\n working groups are currently looking at defining the requirements for\n Authentication, Authorization, and Accounting. This document\n contains the requirements which would have to be supported by a AAA\n service to aid in providing Mobile IP services.\n\n1. Introduction\n\n Clients obtain Internet services by negotiating a point of attachment\n to a \"home domain\", generally from an ISP, or other organization from\n which service requests are made, and fulfilled. With the increasing\n popularity of mobile devices, a need has been generated to allow\n users to attach to any domain convenient to their current location.\n In this way, a client needs access to resources being provided by an\n administrative domain different than their home domain (called a\n \"foreign domain\"). The need for service from a foreign domain\n requires, in many m 2977 audit authentication authorization credential credentials trust nested-reference unchanged"},{"id":"IETF RFC 3266","type":"specification","body":"IETF","designation":"RFC 3266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3266.txt","https://www.rfc-editor.org/rfc/rfc3266.pdf"],"folder":"IETF/RFC-3266","files":{"txt":{"path":"standards/IETF/RFC-3266/RFC-3266.txt","sha256":"1d06c1f0bd5c5290fde2d21ccca955c314139d95f760731a761c72373c25dc1f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Olson\nRequest for Comments: 3266 Microsoft\nUpdates: 2327 G. Camarillo\nCategory: Standards Track Ericsson\n A. B. Roach\n dynamicsoft\n June 2002\n\n Support for IPv6 in Session Description Protocol (SDP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes the use of Internet Protocol Version 6 (IPv6)\n addresses in conjunction with the Session Description Protocol (SDP).\n Specifically, this document clarifies existing text in SDP with\n regards to","scope_keywords":["3266","attribute","attributes","key","presentation","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null}],"search_text":"IETF RFC 3266 Network Working Group S. Olson\nRequest for Comments: 3266 Microsoft\nUpdates: 2327 G. Camarillo\nCategory: Standards Track Ericsson\n A. B. Roach\n dynamicsoft\n June 2002\n\n Support for IPv6 in Session Description Protocol (SDP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes the use of Internet Protocol Version 6 (IPv6)\n addresses in conjunction with the Session Description Protocol (SDP).\n Specifically, this document clarifies existing text in SDP with\n regards to 3266 attribute attributes key presentation qualified nested-reference unchanged"},{"id":"IETF RFC 3319","type":"specification","body":"IETF","designation":"RFC 3319","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3319.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3319.txt","https://www.rfc-editor.org/rfc/rfc3319.pdf"],"folder":"IETF/RFC-3319","files":{"txt":{"path":"standards/IETF/RFC-3319/RFC-3319.txt","sha256":"a681ec27fe15cfabaa8df17e27e44989c7e3d528bd735ba110c1b02991b10ad4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Dynamic Host Configuration Protocol version 6\n (DHCPv6) option that contains a list of domain names or IPv6\n addresses that can be mapped to one or more Session Initiation\n Protocol (SIP) outbound proxy servers. This is one of the many\n methods that a SIP client can use to obtain the addresses of such a\n local SIP server.\n\n1. Terminology\n\n This document uses the DHCP terminology defined in [1].\n\n A SIP server is defined in RFC 3261 [2]. This server MUST be an\n outbound proxy server, as defined in [3]. In the context of this\n document, a SIP server refers to the host the outbound SIP proxy\n server is running on.\n\n A SIP client is defined in RFC 3261 [2]. The client can be a user\n agent client or the client portion of a proxy server. In the context\n of this document, a SIP client refers to the host the SIP client is\n running on.\n\nSchulzrinne & Volz Standards Track [","scope_keywords":["3319","key","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 3319 This document defines a Dynamic Host Configuration Protocol version 6\n (DHCPv6) option that contains a list of domain names or IPv6\n addresses that can be mapped to one or more Session Initiation\n Protocol (SIP) outbound proxy servers. This is one of the many\n methods that a SIP client can use to obtain the addresses of such a\n local SIP server.\n\n1. Terminology\n\n This document uses the DHCP terminology defined in [1].\n\n A SIP server is defined in RFC 3261 [2]. This server MUST be an\n outbound proxy server, as defined in [3]. In the context of this\n document, a SIP server refers to the host the outbound SIP proxy\n server is running on.\n\n A SIP client is defined in RFC 3261 [2]. The client can be a user\n agent client or the client portion of a proxy server. In the context\n of this document, a SIP client refers to the host the SIP client is\n running on.\n\nSchulzrinne & Volz Standards Track [ 3319 key policy presentation nested-reference unchanged"},{"id":"IETF RFC 3361","type":"specification","body":"IETF","designation":"RFC 3361","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3361.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3361.txt","https://www.rfc-editor.org/rfc/rfc3361.pdf"],"folder":"IETF/RFC-3361","files":{"txt":{"path":"standards/IETF/RFC-3361/RFC-3361.txt","sha256":"67f99fdee92d0510fb3484897917e7e636b4ea1f4fda0c5622a057236811a583"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Dynamic Host Configuration Protocol\n (DHCP-for-IPv4) option that contains a list of domain names or IPv4\n addresses that can be mapped to one or more Session Initiation\n Protocol (SIP) outbound proxy servers. This is one of the many\n methods that a SIP client can use to obtain the addresses of such a\n local SIP server.\n\n1. Terminology\n\n DHCP client: A DHCP [1] client is an Internet host that uses\n DHCP to obtain configuration parameters such as a network\n address.\n\n DHCP server: A DHCP server is an Internet host that returns\n configuration parameters to DHCP clients.\n\n SIP server: As defined in RFC 3261 [2]. This server MUST be an\n outbound proxy server, as defined in [3]. In the context of\n this document, a SIP server refers to the host the SIP\n server is running on.\n\n SIP client: As defined in RFC 3261. The client can be a user\n agent client or the client portio","scope_keywords":["3361","key","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null}],"search_text":"IETF RFC 3361 This document defines a Dynamic Host Configuration Protocol\n (DHCP-for-IPv4) option that contains a list of domain names or IPv4\n addresses that can be mapped to one or more Session Initiation\n Protocol (SIP) outbound proxy servers. This is one of the many\n methods that a SIP client can use to obtain the addresses of such a\n local SIP server.\n\n1. Terminology\n\n DHCP client: A DHCP [1] client is an Internet host that uses\n DHCP to obtain configuration parameters such as a network\n address.\n\n DHCP server: A DHCP server is an Internet host that returns\n configuration parameters to DHCP clients.\n\n SIP server: As defined in RFC 3261 [2]. This server MUST be an\n outbound proxy server, as defined in [3]. In the context of\n this document, a SIP server refers to the host the SIP\n server is running on.\n\n SIP client: As defined in RFC 3261. The client can be a user\n agent client or the client portio 3361 key policy qualified nested-reference unchanged"},{"id":"IETF RFC 3363","type":"specification","body":"IETF","designation":"RFC 3363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3363.txt","https://www.rfc-editor.org/rfc/rfc3363.pdf"],"folder":"IETF/RFC-3363","files":{"txt":{"path":"standards/IETF/RFC-3363/RFC-3363.txt","sha256":"0217ac08fada7cc2150d0e6dcefb7ad1c3cda98c93df4a3f64dff6871572f29d"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies and updates the standards status of RFCs that\n define direct and reverse map of IPv6 addresses in DNS. This\n document moves the A6 and Bit label specifications to experimental\n status.\n\n1. Introduction\n\n The IETF had begun the process of standardizing two different address\n formats for IPv6 addresses AAAA [RFC1886] and A6 [RFC2874] and both\n are at proposed standard. This had led to confusion and conflicts on\n which one to deploy. It is important for deployment that any\n confusion in this area be cleared up, as there is a feeling in the\n community that having more than one choice will lead to delays in the\n deployment of IPv6. The goal of this document is to clarify the\n situation.\n\n This document also discusses issues relating to the usage of Binary\n Labels [RFC 2673] to support the reverse mapping of IPv6 addresses.\n\n This document is based on extensive technica","scope_keywords":["3363","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6563","folder":"IETF/RFC-6563","source":"IETF/RFC-6563/RFC-6563.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null}],"search_text":"IETF RFC 3363 This document clarifies and updates the standards status of RFCs that\n define direct and reverse map of IPv6 addresses in DNS. This\n document moves the A6 and Bit label specifications to experimental\n status.\n\n1. Introduction\n\n The IETF had begun the process of standardizing two different address\n formats for IPv6 addresses AAAA [RFC1886] and A6 [RFC2874] and both\n are at proposed standard. This had led to confusion and conflicts on\n which one to deploy. It is important for deployment that any\n confusion in this area be cleared up, as there is a feeling in the\n community that having more than one choice will lead to delays in the\n deployment of IPv6. The goal of this document is to clarify the\n situation.\n\n This document also discusses issues relating to the usage of Binary\n Labels [RFC 2673] to support the reverse mapping of IPv6 addresses.\n\n This document is based on extensive technica 3363 presentation risk nested-reference unchanged"},{"id":"IETF RFC 3375","type":"specification","body":"IETF","designation":"RFC 3375","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3375.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3375.txt","https://www.rfc-editor.org/rfc/rfc3375.pdf"],"folder":"IETF/RFC-3375","files":{"txt":{"path":"standards/IETF/RFC-3375/RFC-3375.txt","sha256":"1d5f3301b40c52d65d99fcef8614f4f896a297e681cd9701941b9b20d9a681c0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes high-level functional and interface\n requirements for a client-server protocol for the registration and\n management of Internet domain names in shared registries. Specific\n technical requirements detailed for protocol design are not presented\n here. Instead, this document focuses on the basic functions and\n interfaces required of a protocol to support multiple registry and\n registrar operational models.\n\nConventions Used In This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].","scope_keywords":["3375","attribute","attributes","authentication","identification","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null}],"search_text":"IETF RFC 3375 This document describes high-level functional and interface\n requirements for a client-server protocol for the registration and\n management of Internet domain names in shared registries. Specific\n technical requirements detailed for protocol design are not presented\n here. Instead, this document focuses on the basic functions and\n interfaces required of a protocol to support multiple registry and\n registrar operational models.\n\nConventions Used In This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119]. 3375 attribute attributes authentication identification key management registered nested-reference unchanged"},{"id":"IETF RFC 3397","type":"specification","body":"IETF","designation":"RFC 3397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3397.txt","https://www.rfc-editor.org/rfc/rfc3397.pdf"],"folder":"IETF/RFC-3397","files":{"txt":{"path":"standards/IETF/RFC-3397/RFC-3397.txt","sha256":"00493047cb4915db7753ab959dc7c1c5311a940c73f54a5cf1223345653a3177"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to specify the domain search list used when resolving hostnames using\n DNS.","scope_keywords":["3397","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null}],"search_text":"IETF RFC 3397 This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to specify the domain search list used when resolving hostnames using\n DNS. 3397 authentication key nested-reference unchanged"},{"id":"IETF RFC 3406","type":"specification","body":"IETF","designation":"RFC 3406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3406.txt","https://www.rfc-editor.org/rfc/rfc3406.pdf"],"folder":"IETF/RFC-3406","files":{"txt":{"path":"standards/IETF/RFC-3406/RFC-3406.txt","sha256":"904af2057b2ae9eecedfa696b870997467457f7ed941bdc046f19a37760d6ad4"}},"tags":["nested-reference","unchanged"],"summary":"This document lays out general definitions of and mechanisms for\n establishing Uniform Resource Names (URN) \"namespaces\". The URN WG\n has defined a syntax for URNs in RFC 2141, as well as some proposed\n mechanisms for their resolution and use in Internet applications in\n RFC 3401 and RFC 3405. The whole rests on the concept of individual\n \"namespaces\" within the URN structure. Apart from proof-of-concept\n namespaces, the use of existing identifiers in URNs has been\n discussed in RFC 2288.","scope_keywords":["3406","identification","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4152","folder":"IETF/RFC-4152","source":"IETF/RFC-4152/RFC-4152.txt","version":null},{"body":"IETF","designation":"RFC 4179","folder":"IETF/RFC-4179","source":"IETF/RFC-4179/RFC-4179.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4854","folder":"IETF/RFC-4854","source":"IETF/RFC-4854/RFC-4854.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 6288","folder":"IETF/RFC-6288","source":"IETF/RFC-6288/RFC-6288.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 3406 This document lays out general definitions of and mechanisms for\n establishing Uniform Resource Names (URN) \"namespaces\". The URN WG\n has defined a syntax for URNs in RFC 2141, as well as some proposed\n mechanisms for their resolution and use in Internet applications in\n RFC 3401 and RFC 3405. The whole rests on the concept of individual\n \"namespaces\" within the URN structure. Apart from proof-of-concept\n namespaces, the use of existing identifiers in URNs has been\n discussed in RFC 2288. 3406 identification key registered nested-reference unchanged"},{"id":"IETF RFC 3425","type":"specification","body":"IETF","designation":"RFC 3425","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3425.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3425.txt","https://www.rfc-editor.org/rfc/rfc3425.pdf"],"folder":"IETF/RFC-3425","files":{"txt":{"path":"standards/IETF/RFC-3425/RFC-3425.txt","sha256":"624c3ebf00211e3e6c64e0ae45a0c483892af76276566f4725742d0915fcd2d1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Lawrence\nRequest for Comments: 3425 Nominum\nUpdates: 1035 November 2002\nCategory: Standards Track\n\n Obsoleting IQUERY\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n The IQUERY method of performing inverse DNS lookups, specified in RFC\n 1035, has not been generally implemented and has usually been\n operationally disabled where it has been implemented. Both reflect a\n general view in the community that the concept was unwise and that\n the widely-used alternate ","scope_keywords":["3425","authentication","authorization","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 3425 Network Working Group D. Lawrence\nRequest for Comments: 3425 Nominum\nUpdates: 1035 November 2002\nCategory: Standards Track\n\n Obsoleting IQUERY\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n The IQUERY method of performing inverse DNS lookups, specified in RFC\n 1035, has not been generally implemented and has usually been\n operationally disabled where it has been implemented. Both reflect a\n general view in the community that the concept was unwise and that\n the widely-used alternate  3425 authentication authorization key policy nested-reference unchanged"},{"id":"IETF RFC 3655","type":"specification","body":"IETF","designation":"RFC 3655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3655.txt","https://www.rfc-editor.org/rfc/rfc3655.pdf"],"folder":"IETF/RFC-3655","files":{"txt":{"path":"standards/IETF/RFC-3655/RFC-3655.txt","sha256":"4ffa37cee9df7224eee3f6e56e9c63847160100000b5631a26c1378781070324"}},"tags":["nested-reference","unchanged"],"summary":"This document alters the specification defined in RFC 2535. Based on\n implementation experience, the Authenticated Data (AD) bit in the DNS\n header is not useful. This document redefines the AD bit such that\n it is only set if all answers or records proving that no answers\n exist in the response has been cryptographically verified or\n otherwise meets the server's local security policy.\n\n1. Introduction\n\n Familiarity with the DNS system [RFC1035] and DNS security extensions\n [RFC2535] is helpful but not necessary.\n\n As specified in RFC 2535 (section 6.1), the AD (Authenticated Data)\n bit indicates in a response that all data included in the answer and\n authority sections of the response have been authenticated by the\n server according to the policies of that server. This is not\n especially useful in practice, since a conformant server SHOULD never\n reply with data that failed its security","scope_keywords":["3655","authentication","key","keys","policies","policy","signature","signatures","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null}],"search_text":"IETF RFC 3655 This document alters the specification defined in RFC 2535. Based on\n implementation experience, the Authenticated Data (AD) bit in the DNS\n header is not useful. This document redefines the AD bit such that\n it is only set if all answers or records proving that no answers\n exist in the response has been cryptographically verified or\n otherwise meets the server's local security policy.\n\n1. Introduction\n\n Familiarity with the DNS system [RFC1035] and DNS security extensions\n [RFC2535] is helpful but not necessary.\n\n As specified in RFC 2535 (section 6.1), the AD (Authenticated Data)\n bit indicates in a response that all data included in the answer and\n authority sections of the response have been authenticated by the\n server according to the policies of that server. This is not\n especially useful in practice, since a conformant server SHOULD never\n reply with data that failed its security 3655 authentication key keys policies policy signature signatures trust validation nested-reference unchanged"},{"id":"IETF RFC 3658","type":"specification","body":"IETF","designation":"RFC 3658","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3658.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3658.txt","https://www.rfc-editor.org/rfc/rfc3658.pdf"],"folder":"IETF/RFC-3658","files":{"txt":{"path":"standards/IETF/RFC-3658/RFC-3658.txt","sha256":"ad164cd1a250a3ed2a37a9a3663587a851688b04fc00e990a9254fe52c53ff67"}},"tags":["nested-reference","unchanged"],"summary":"The delegation signer (DS) resource record (RR) is inserted at a zone\n cut (i.e., a delegation point) to indicate that the delegated zone is\n digitally signed and that the delegated zone recognizes the indicated\n key as a valid zone key for the delegated zone. The DS RR is a\n modification to the DNS Security Extensions definition, motivated by\n operational considerations. The intent is to use this resource\n record as an explicit statement about the delegation, rather than\n relying on inference.\n\n This document defines the DS RR, gives examples of how it is used and\n describes the implications on resolvers. This change is not\n backwards compatible with RFC 2535. This document updates RFC 1035,\n RFC 2535, RFC 3008 and RFC 3090.\n\nGudmundsson Standards Track [Page 1]\n\f\nRFC 3658 Delegation Signer (DS) Resource Record (RR) December 2003","scope_keywords":["3658","http","key","keys","presentation","signature","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3757","folder":"IETF/RFC-3757","source":"IETF/RFC-3757/RFC-3757.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null}],"search_text":"IETF RFC 3658 The delegation signer (DS) resource record (RR) is inserted at a zone\n cut (i.e., a delegation point) to indicate that the delegated zone is\n digitally signed and that the delegated zone recognizes the indicated\n key as a valid zone key for the delegated zone. The DS RR is a\n modification to the DNS Security Extensions definition, motivated by\n operational considerations. The intent is to use this resource\n record as an explicit statement about the delegation, rather than\n relying on inference.\n\n This document defines the DS RR, gives examples of how it is used and\n describes the implications on resolvers. This change is not\n backwards compatible with RFC 2535. This document updates RFC 1035,\n RFC 2535, RFC 3008 and RFC 3090.\n\nGudmundsson Standards Track [Page 1]\n\f\nRFC 3658 Delegation Signer (DS) Resource Record (RR) December 2003 3658 http key keys presentation signature verifiable nested-reference unchanged"},{"id":"IETF RFC 3696","type":"specification","body":"IETF","designation":"RFC 3696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3696.txt","https://www.rfc-editor.org/rfc/rfc3696.pdf"],"folder":"IETF/RFC-3696","files":{"txt":{"path":"standards/IETF/RFC-3696/RFC-3696.txt","sha256":"59ef85b56dae5825647147a234e5f55a515e7ffaa147f6cd7c91cbdcbffdbff5"}},"tags":["nested-reference","unchanged"],"summary":"Many Internet applications have been designed to deduce top-level\n domains (or other domain name labels) from partial information. The\n introduction of new top-level domains, especially non-country-code\n ones, has exposed flaws in some of the methods used by these\n applications. These flaws make it more difficult, or impossible, for\n users of the applications to access the full Internet. This memo\n discusses some of the techniques that have been used and gives some\n guidance for minimizing their negative impact as the domain name\n environment evolves. This document draws summaries of the applicable\n rules together in one place and supplies references to the actual\n standards.\n\nKlensin Informational [Page 1]\n\f\nRFC 3696 Checking and Transformation of Names February 2004","scope_keywords":["3696","http","key","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 3696 Many Internet applications have been designed to deduce top-level\n domains (or other domain name labels) from partial information. The\n introduction of new top-level domains, especially non-country-code\n ones, has exposed flaws in some of the methods used by these\n applications. These flaws make it more difficult, or impossible, for\n users of the applications to access the full Internet. This memo\n discusses some of the techniques that have been used and gives some\n guidance for minimizing their negative impact as the domain name\n environment evolves. This document draws summaries of the applicable\n rules together in one place and supplies references to the actual\n standards.\n\nKlensin Informational [Page 1]\n\f\nRFC 3696 Checking and Transformation of Names February 2004 3696 http key qualified registered nested-reference unchanged"},{"id":"IETF RFC 3707","type":"specification","body":"IETF","designation":"RFC 3707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3707.txt","https://www.rfc-editor.org/rfc/rfc3707.pdf"],"folder":"IETF/RFC-3707","files":{"txt":{"path":"standards/IETF/RFC-3707/RFC-3707.txt","sha256":"ca47d70563059303fb36f41f52490d4ee661a88cfac25d4186a6abc927afbfd6"}},"tags":["nested-reference","unchanged"],"summary":"Internet registries expose administrative and operational data via\n varying directory services. This document defines functional\n requirements for the directory services of domain registries and the\n common base requirements for extending the use of these services for\n other types of Internet registries.","scope_keywords":["3707","authentication","certificate","holder"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null}],"search_text":"IETF RFC 3707 Internet registries expose administrative and operational data via\n varying directory services. This document defines functional\n requirements for the directory services of domain registries and the\n common base requirements for extending the use of these services for\n other types of Internet registries. 3707 authentication certificate holder nested-reference unchanged"},{"id":"IETF RFC 3720","type":"specification","body":"IETF","designation":"RFC 3720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3720.txt","https://www.rfc-editor.org/rfc/rfc3720.pdf"],"folder":"IETF/RFC-3720","files":{"txt":{"path":"standards/IETF/RFC-3720/RFC-3720.txt","sha256":"0c014dbc041bfc2308c1990387aabffdb21050c3ec140c96522c12005b572db3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a transport protocol for Internet Small\n Computer Systems Interface (iSCSI) that works on top of TCP. The\n iSCSI protocol aims to be fully compliant with the standardized SCSI\n architecture model.\n\n SCSI is a popular family of protocols that enable systems to\n communicate with I/O devices, especially storage devices. SCSI\n protocols are request/response application protocols with a common\n standardized architecture model and basic command set, as well as\n standardized command sets for different device classes (disks, tapes,\n media-changers etc.).\n\n As system interconnects move from the classical bus structure to a\n network structure, SCSI has to be mapped to network transport\n protocols. IP networks now meet the performance requirements of fast\n system interconnects and as such are good candidates to \"carry\" SCSI.\n\nSatran, et al. Standards Track [Page 1]\n\f\nRFC 372","scope_keywords":["3720","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3783","folder":"IETF/RFC-3783","source":"IETF/RFC-3783/RFC-3783.txt","version":null},{"body":"IETF","designation":"RFC 3980","folder":"IETF/RFC-3980","source":"IETF/RFC-3980/RFC-3980.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4850","folder":"IETF/RFC-4850","source":"IETF/RFC-4850/RFC-4850.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 3720 This document describes a transport protocol for Internet Small\n Computer Systems Interface (iSCSI) that works on top of TCP. The\n iSCSI protocol aims to be fully compliant with the standardized SCSI\n architecture model.\n\n SCSI is a popular family of protocols that enable systems to\n communicate with I/O devices, especially storage devices. SCSI\n protocols are request/response application protocols with a common\n standardized architecture model and basic command set, as well as\n standardized command sets for different device classes (disks, tapes,\n media-changers etc.).\n\n As system interconnects move from the classical bus structure to a\n network structure, SCSI has to be mapped to network transport\n protocols. IP networks now meet the performance requirements of fast\n system interconnects and as such are good candidates to \"carry\" SCSI.\n\nSatran, et al. Standards Track [Page 1]\n\f\nRFC 372 3720 management qualified nested-reference unchanged"},{"id":"IETF RFC 3920","type":"specification","body":"IETF","designation":"RFC 3920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3920.txt","https://www.rfc-editor.org/rfc/rfc3920.pdf"],"folder":"IETF/RFC-3920","files":{"txt":{"path":"standards/IETF/RFC-3920/RFC-3920.txt","sha256":"7387bd50f08bad9502aefff892194b58e9adda61a58e6a2348b2a773aecc598f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the core features of the Extensible Messaging and\n Presence Protocol (XMPP), a protocol for streaming Extensible Markup\n Language (XML) elements in order to exchange structured information\n in close to real time between any two network endpoints. While XMPP\n provides a generalized, extensible framework for exchanging XML data,\n it is used mainly for the purpose of building instant messaging and\n presence applications that meet the requirements of RFC 2779.\n\nSaint-Andre, Ed. Standards Track [Page 1]\n\f\nRFC 3920 XMPP Core October 2004","scope_keywords":["3920","key","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4854","folder":"IETF/RFC-4854","source":"IETF/RFC-4854/RFC-4854.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3920 This memo defines the core features of the Extensible Messaging and\n Presence Protocol (XMPP), a protocol for streaming Extensible Markup\n Language (XML) elements in order to exchange structured information\n in close to real time between any two network endpoints. While XMPP\n provides a generalized, extensible framework for exchanging XML data,\n it is used mainly for the purpose of building instant messaging and\n presence applications that meet the requirements of RFC 2779.\n\nSaint-Andre, Ed. Standards Track [Page 1]\n\f\nRFC 3920 XMPP Core October 2004 3920 key registered tls nested-reference unchanged"},{"id":"IETF RFC 3974","type":"specification","body":"IETF","designation":"RFC 3974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3974.txt","https://www.rfc-editor.org/rfc/rfc3974.pdf"],"folder":"IETF/RFC-3974","files":{"txt":{"path":"standards/IETF/RFC-3974/RFC-3974.txt","sha256":"7e1b8675549c6eed5859be140d7ee39cb35248602fbf699c7fabe1327198155e"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses SMTP operational experiences in IPv4/v6 dual\n stack environments. As IPv6-capable SMTP servers are deployed, it\n has become apparent that certain configurations of MX records are\n necessary for stable dual-stack (IPv4 and IPv6) SMTP operation. This\n document clarifies the existing problems in the transition period\n between IPv4 SMTP and IPv6 SMTP. It also defines operational\n requirements for stable IPv4/v6 SMTP operation.\n\nNakamura & Hagino Informational [Page 1]\n\f\nRFC 3974 SMTP in Dual Stack Environments January 2005\n\n This document does not define any new protocol.\n\n1. Introduction\n\n Delivery of mail messages to the final mail drop is not always done\n by direct IP communication between the submitter and final receiver,\n and there may be some intermediate hosts that relay the messages. So\n it is difficult to know at message submission (also at receiver side)\n th","scope_keywords":["3974","algorithm","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null}],"search_text":"IETF RFC 3974 This document discusses SMTP operational experiences in IPv4/v6 dual\n stack environments. As IPv6-capable SMTP servers are deployed, it\n has become apparent that certain configurations of MX records are\n necessary for stable dual-stack (IPv4 and IPv6) SMTP operation. This\n document clarifies the existing problems in the transition period\n between IPv4 SMTP and IPv6 SMTP. It also defines operational\n requirements for stable IPv4/v6 SMTP operation.\n\nNakamura & Hagino Informational [Page 1]\n\f\nRFC 3974 SMTP in Dual Stack Environments January 2005\n\n This document does not define any new protocol.\n\n1. Introduction\n\n Delivery of mail messages to the final mail drop is not always done\n by direct IP communication between the submitter and final receiver,\n and there may be some intermediate hosts that relay the messages. So\n it is difficult to know at message submission (also at receiver side)\n th 3974 algorithm delivery nested-reference unchanged"},{"id":"IETF RFC 3982","type":"specification","body":"IETF","designation":"RFC 3982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3982.txt","https://www.rfc-editor.org/rfc/rfc3982.pdf"],"folder":"IETF/RFC-3982","files":{"txt":{"path":"standards/IETF/RFC-3982/RFC-3982.txt","sha256":"886e40fd4c611f1d9158f4625175682f0bf0b8d97ab41cc0666a575a2fca8d61"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Internet Registry Information Service\n (IRIS) registry schema for registered DNS information. The schema\n extends the necessary query and result operations of IRIS to provide\n the functional information service needs for syntaxes and results\n used by domain registries and registrars.","scope_keywords":["3982","attribute","attributes","authentication","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"IETF RFC 3982 This document describes an Internet Registry Information Service\n (IRIS) registry schema for registered DNS information. The schema\n extends the necessary query and result operations of IRIS to provide\n the functional information service needs for syntaxes and results\n used by domain registries and registrars. 3982 attribute attributes authentication key registered nested-reference unchanged"},{"id":"IETF RFC 4120","type":"specification","body":"IETF","designation":"RFC 4120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4120.txt","https://www.rfc-editor.org/rfc/rfc4120.pdf"],"folder":"IETF/RFC-4120","files":{"txt":{"path":"standards/IETF/RFC-4120/RFC-4120.txt","sha256":"368d3cd1a4248e361799e3ebb2dbd124ec4fb14651e2188b77b392b66463f75b"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview and specification of Version 5 of\n the Kerberos protocol, and it obsoletes RFC 1510 to clarify aspects\n of the protocol and its intended use that require more detailed or\n clearer explanation than was provided in RFC 1510. This document is\n intended to provide a detailed description of the protocol, suitable\n for implementation, together with descriptions of the appropriate use\n of protocol messages and fields within those messages.\n\nNeuman, et al. Standards Track [Page 1]\n\f\nRFC 4120 Kerberos V5 July 2005","scope_keywords":["4120","authentication","authorization","encryption","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 4120 This document provides an overview and specification of Version 5 of\n the Kerberos protocol, and it obsoletes RFC 1510 to clarify aspects\n of the protocol and its intended use that require more detailed or\n clearer explanation than was provided in RFC 1510. This document is\n intended to provide a detailed description of the protocol, suitable\n for implementation, together with descriptions of the appropriate use\n of protocol messages and fields within those messages.\n\nNeuman, et al. Standards Track [Page 1]\n\f\nRFC 4120 Kerberos V5 July 2005 4120 authentication authorization encryption key policy nested-reference unchanged"},{"id":"IETF RFC 4151","type":"specification","body":"IETF","designation":"RFC 4151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4151.txt","https://www.rfc-editor.org/rfc/rfc4151.pdf"],"folder":"IETF/RFC-4151","files":{"txt":{"path":"standards/IETF/RFC-4151/RFC-4151.txt","sha256":"4912d5fef874fb5c8834d8d60e0345fede3c93736b6559389dbb82da68a2b5e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"tag\" Uniform Resource Identifier (URI)\n scheme. Tag URIs (also known as \"tags\") are designed to be unique\n across space and time while being tractable to humans. They are\n distinct from most other URIs in that they have no authoritative\n resolution mechanism. A tag may be used purely as an entity\n identifier. Furthermore, using tags has some advantages over the\n common practice of using \"http\" URIs as identifiers for\n non-HTTP-accessible resources.\n\nKindberg & Hawke Informational [Page 1]\n\f\nRFC 4151 Tag URIs October 2005","scope_keywords":["4151","holder","http","identification","key","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null}],"search_text":"IETF RFC 4151 This document describes the \"tag\" Uniform Resource Identifier (URI)\n scheme. Tag URIs (also known as \"tags\") are designed to be unique\n across space and time while being tractable to humans. They are\n distinct from most other URIs in that they have no authoritative\n resolution mechanism. A tag may be used purely as an entity\n identifier. Furthermore, using tags has some advantages over the\n common practice of using \"http\" URIs as identifiers for\n non-HTTP-accessible resources.\n\nKindberg & Hawke Informational [Page 1]\n\f\nRFC 4151 Tag URIs October 2005 4151 holder http identification key qualified registered nested-reference unchanged"},{"id":"IETF RFC 4214","type":"specification","body":"IETF","designation":"RFC 4214","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4214.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4214.txt","https://www.rfc-editor.org/rfc/rfc4214.pdf"],"folder":"IETF/RFC-4214","files":{"txt":{"path":"standards/IETF/RFC-4214/RFC-4214.txt","sha256":"f46cbc094a56a125b8b3c25e63d6539178948bc1d062da5fafb11d698767aa46"}},"tags":["nested-reference","unchanged"],"summary":"The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects\n IPv6 hosts/routers over IPv4 networks. ISATAP views the IPv4 network\n as a link layer for IPv6 and views other nodes on the network as\n potential IPv6 hosts/routers. ISATAP supports an automatic tunneling\n abstraction similar to the Non-Broadcast Multiple Access (NBMA)\n model.\n\nTemplin, et al. Experimental [Page 1]\n\f\nRFC 4214 ISATAP October 2005\n\n1. Introduction\n\n This document specifies a simple mechanism called the Intra-Site\n Automatic Tunnel Addressing Protocol (ISATAP) that connects IPv6\n hosts/routers over IPv4 networks. Dual-stack (IPv6/IPv4) nodes use\n ISATAP to automatically tunnel IPv6 packets in IPv4, i.e., ISATAP\n views the IPv4 network as a link layer for IPv6 and views other nodes\n on the network as potential IPv6 hosts/routers.\n\n ISATAP enables automatic tunneling whether global or private IPv4\n address","scope_keywords":["4214","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4554","folder":"IETF/RFC-4554","source":"IETF/RFC-4554/RFC-4554.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null}],"search_text":"IETF RFC 4214 The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects\n IPv6 hosts/routers over IPv4 networks. ISATAP views the IPv4 network\n as a link layer for IPv6 and views other nodes on the network as\n potential IPv6 hosts/routers. ISATAP supports an automatic tunneling\n abstraction similar to the Non-Broadcast Multiple Access (NBMA)\n model.\n\nTemplin, et al. Experimental [Page 1]\n\f\nRFC 4214 ISATAP October 2005\n\n1. Introduction\n\n This document specifies a simple mechanism called the Intra-Site\n Automatic Tunnel Addressing Protocol (ISATAP) that connects IPv6\n hosts/routers over IPv4 networks. Dual-stack (IPv6/IPv4) nodes use\n ISATAP to automatically tunnel IPv6 packets in IPv4, i.e., ISATAP\n views the IPv4 network as a link layer for IPv6 and views other nodes\n on the network as potential IPv6 hosts/routers.\n\n ISATAP enables automatic tunneling whether global or private IPv4\n address 4214 key trust nested-reference unchanged"},{"id":"IETF RFC 4279","type":"specification","body":"IETF","designation":"RFC 4279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4279.txt","https://www.rfc-editor.org/rfc/rfc4279.pdf"],"folder":"IETF/RFC-4279","files":{"txt":{"path":"standards/IETF/RFC-4279/RFC-4279.txt","sha256":"448e6ccacec7f2430e039d1551a828235c3506228ead65a7a900c2d80efa8656"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies three sets of new ciphersuites for the\n Transport Layer Security (TLS) protocol to support authentication\n based on pre-shared keys (PSKs). These pre-shared keys are symmetric\n keys, shared in advance among the communicating parties. The first\n set of ciphersuites uses only symmetric key operations for\n authentication. The second set uses a Diffie-Hellman exchange\n authenticated with a pre-shared key, and the third set combines\n public key authentication of the server with pre-shared key\n authentication of the client.\n\nEronen & Tschofenig Standards Track [Page 1]\n\f\nRFC 4279 PSK Ciphersuites for TLS December 2005","scope_keywords":["4279","algorithm","algorithms","authentication","certificate","certificates","hash","key","keys","management","pki","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4785","folder":"IETF/RFC-4785","source":"IETF/RFC-4785/RFC-4785.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 4279 This document specifies three sets of new ciphersuites for the\n Transport Layer Security (TLS) protocol to support authentication\n based on pre-shared keys (PSKs). These pre-shared keys are symmetric\n keys, shared in advance among the communicating parties. The first\n set of ciphersuites uses only symmetric key operations for\n authentication. The second set uses a Diffie-Hellman exchange\n authenticated with a pre-shared key, and the third set combines\n public key authentication of the server with pre-shared key\n authentication of the client.\n\nEronen & Tschofenig Standards Track [Page 1]\n\f\nRFC 4279 PSK Ciphersuites for TLS December 2005 4279 algorithm algorithms authentication certificate certificates hash key keys management pki tls nested-reference unchanged"},{"id":"IETF RFC 4280","type":"specification","body":"IETF","designation":"RFC 4280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4280.txt","https://www.rfc-editor.org/rfc/rfc4280.pdf"],"folder":"IETF/RFC-4280","files":{"txt":{"path":"standards/IETF/RFC-4280/RFC-4280.txt","sha256":"f0a6ad3458ae4a7996bf218f9c0443418b6820ae4f11fbe254fae59657e814a8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new options to discover the Broadcast and\n Multicast Service (BCMCS) controller in an IP network. BCMCS is\n being developed for Third generation (3G) cellular telephone\n networks. Users of the service interact with a controller in the\n network via the Mobile Node (MN) to derive information required to\n receive Broadcast and Multicast Service. Dynamic Host Configuration\n Protocol can be used to configure the MN to access a particular\n controller. This document defines the related options and option\n codes.\n\nChowdhury, et al. Standards Track [Page 1]\n\f\nRFC 4280 DHCP Options for BMCS November 2005","scope_keywords":["4280","encryption","http","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 4280 This document defines new options to discover the Broadcast and\n Multicast Service (BCMCS) controller in an IP network. BCMCS is\n being developed for Third generation (3G) cellular telephone\n networks. Users of the service interact with a controller in the\n network via the Mobile Node (MN) to derive information required to\n receive Broadcast and Multicast Service. Dynamic Host Configuration\n Protocol can be used to configure the MN to access a particular\n controller. This document defines the related options and option\n codes.\n\nChowdhury, et al. Standards Track [Page 1]\n\f\nRFC 4280 DHCP Options for BMCS November 2005 4280 encryption http key qualified nested-reference unchanged"},{"id":"IETF RFC 4290","type":"specification","body":"IETF","designation":"RFC 4290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4290.txt","https://www.rfc-editor.org/rfc/rfc4290.pdf"],"folder":"IETF/RFC-4290","files":{"txt":{"path":"standards/IETF/RFC-4290/RFC-4290.txt","sha256":"4604b74e8117324bede0cbe78de9859293690a7f5822f11a1bd351ee71c5ebc8"}},"tags":["nested-reference","unchanged"],"summary":"This document explores the issues in the registration of\n internationalized domain names (IDNs). The basic IDN definition\n allows a very large number of possible characters in domain names,\n and this richness may lead to serious user confusion about similar-\n looking names. To avoid this confusion, the IDN registration process\n must impose rules that disallow some otherwise-valid name\n combinations. This document suggests a set of mechanisms that\n registries might use to define and implement such rules for a broad\n range of languages, including adaptation of methods developed for\n Chinese, Japanese, and Korean domain names.\n\nKlensin Informational [Page 1]\n\f\nRFC 4290 IDN Registration Practices December 2005","scope_keywords":["4290","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 4290 This document explores the issues in the registration of\n internationalized domain names (IDNs). The basic IDN definition\n allows a very large number of possible characters in domain names,\n and this richness may lead to serious user confusion about similar-\n looking names. To avoid this confusion, the IDN registration process\n must impose rules that disallow some otherwise-valid name\n combinations. This document suggests a set of mechanisms that\n registries might use to define and implement such rules for a broad\n range of languages, including adaptation of methods developed for\n Chinese, Japanese, and Korean domain names.\n\nKlensin Informational [Page 1]\n\f\nRFC 4290 IDN Registration Practices December 2005 4290 registered risk nested-reference unchanged"},{"id":"IETF RFC 4347","type":"specification","body":"IETF","designation":"RFC 4347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4347.txt","https://www.rfc-editor.org/rfc/rfc4347.pdf"],"folder":"IETF/RFC-4347","files":{"txt":{"path":"standards/IETF/RFC-4347/RFC-4347.txt","sha256":"28570431d9e211c4a4df76cd34f98d41c6f509272382c6184c9e806d5b6de312"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Version 1.0 of the Datagram Transport Layer\n Security (DTLS) protocol. The DTLS protocol provides communications\n privacy for datagram protocols. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery. The DTLS protocol is\n based on the Transport Layer Security (TLS) protocol and provides\n equivalent security guarantees. Datagram semantics of the underlying\n transport are preserved by the DTLS protocol.","scope_keywords":["4347","delivery","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 4347 This document specifies Version 1.0 of the Datagram Transport Layer\n Security (DTLS) protocol. The DTLS protocol provides communications\n privacy for datagram protocols. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery. The DTLS protocol is\n based on the Transport Layer Security (TLS) protocol and provides\n equivalent security guarantees. Datagram semantics of the underlying\n transport are preserved by the DTLS protocol. 4347 delivery key tls nested-reference unchanged"},{"id":"IETF RFC 4703","type":"specification","body":"IETF","designation":"RFC 4703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4703.txt","https://www.rfc-editor.org/rfc/rfc4703.pdf"],"folder":"IETF/RFC-4703","files":{"txt":{"path":"standards/IETF/RFC-4703/RFC-4703.txt","sha256":"87918bcb6adb28978f7b68b9fa54277c4e974ca9e9a6c5932f346a297a4b1696"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) provides a mechanism\n for host configuration that includes dynamic assignment of IP\n addresses and fully qualified domain names. To maintain accurate\n name-to-IP-address and IP-address-to-name mappings in the DNS, these\n dynamically assigned addresses and fully qualified domain names\n (FQDNs) require updates to the DNS. This document identifies\n situations in which conflicts in the use of fully qualified domain\n names may arise among DHCP clients and servers, and it describes a\n strategy for the use of the DHCID DNS resource record (RR) in\n resolving those conflicts.\n\nStapp & Volz Standards Track [Page 1]\n\f\nRFC 4703 Resolution of FQDN Conflicts October 2006","scope_keywords":["4703","credential","credentials","key","policies","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null}],"search_text":"IETF RFC 4703 The Dynamic Host Configuration Protocol (DHCP) provides a mechanism\n for host configuration that includes dynamic assignment of IP\n addresses and fully qualified domain names. To maintain accurate\n name-to-IP-address and IP-address-to-name mappings in the DNS, these\n dynamically assigned addresses and fully qualified domain names\n (FQDNs) require updates to the DNS. This document identifies\n situations in which conflicts in the use of fully qualified domain\n names may arise among DHCP clients and servers, and it describes a\n strategy for the use of the DHCID DNS resource record (RR) in\n resolving those conflicts.\n\nStapp & Volz Standards Track [Page 1]\n\f\nRFC 4703 Resolution of FQDN Conflicts October 2006 4703 credential credentials key policies policy qualified nested-reference unchanged"},{"id":"IETF RFC 4955","type":"specification","body":"IETF","designation":"RFC 4955","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4955.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4955.txt","https://www.rfc-editor.org/rfc/rfc4955.pdf"],"folder":"IETF/RFC-4955","files":{"txt":{"path":"standards/IETF/RFC-4955/RFC-4955.txt","sha256":"fa6911e4a2e676a3e3ca4f83e8f9cf4084bff231de2124db6622171136baf325"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a methodology for deploying alternate, non-\n backwards-compatible, DNS Security (DNSSEC) methodologies in an\n experimental fashion without disrupting the deployment of standard\n DNSSEC.","scope_keywords":["4955","algorithm","algorithms","authentication","key","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null}],"search_text":"IETF RFC 4955 This document describes a methodology for deploying alternate, non-\n backwards-compatible, DNS Security (DNSSEC) methodologies in an\n experimental fashion without disrupting the deployment of standard\n DNSSEC. 4955 algorithm algorithms authentication key path policy trust nested-reference unchanged"},{"id":"IETF RFC 4956","type":"specification","body":"IETF","designation":"RFC 4956","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4956.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4956.txt","https://www.rfc-editor.org/rfc/rfc4956.pdf"],"folder":"IETF/RFC-4956","files":{"txt":{"path":"standards/IETF/RFC-4956/RFC-4956.txt","sha256":"3e877db0dfd3cfac9cd97c0c737bb710a0ecc3ebdd178dabee5c0061cd80f744"}},"tags":["nested-reference","unchanged"],"summary":"In the DNS security (DNSSEC) extensions, delegations to unsigned\n subzones are cryptographically secured. Maintaining this\n cryptography is not always practical or necessary. This document\n describes an experimental \"Opt-In\" model that allows administrators\n to omit this cryptography and manage the cost of adopting DNSSEC with\n large zones.\n\nArends, et al. Experimental [Page 1]\n\f\nRFC 4956 DNS Security (DNSSEC) Opt-In July 2007","scope_keywords":["4956","algorithm","algorithms","key","pid","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4956 In the DNS security (DNSSEC) extensions, delegations to unsigned\n subzones are cryptographically secured. Maintaining this\n cryptography is not always practical or necessary. This document\n describes an experimental \"Opt-In\" model that allows administrators\n to omit this cryptography and manage the cost of adopting DNSSEC with\n large zones.\n\nArends, et al. Experimental [Page 1]\n\f\nRFC 4956 DNS Security (DNSSEC) Opt-In July 2007 4956 algorithm algorithms key pid trust validation nested-reference unchanged"},{"id":"IETF RFC 4966","type":"specification","body":"IETF","designation":"RFC 4966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4966.txt","https://www.rfc-editor.org/rfc/rfc4966.pdf"],"folder":"IETF/RFC-4966","files":{"txt":{"path":"standards/IETF/RFC-4966/RFC-4966.txt","sha256":"72301eca56bca70239118aea28e6238587f8a943cec5585126d0c2752aff9d8a"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses issues with the specific form of IPv6-IPv4\n protocol translation mechanism implemented by the Network Address\n Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These\n issues are sufficiently serious that recommending RFC 2766 as a\n general purpose transition mechanism is no longer desirable, and this\n document recommends that the IETF should reclassify RFC 2766 from\n Proposed Standard to Historic status.\n\nAoun & Davies Informational [Page 1]\n\f\nRFC 4966 NAT-PT Issues Analysis July 2007","scope_keywords":["4966","algorithm","management","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null}],"search_text":"IETF RFC 4966 This document discusses issues with the specific form of IPv6-IPv4\n protocol translation mechanism implemented by the Network Address\n Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These\n issues are sufficiently serious that recommending RFC 2766 as a\n general purpose transition mechanism is no longer desirable, and this\n document recommends that the IETF should reclassify RFC 2766 from\n Proposed Standard to Historic status.\n\nAoun & Davies Informational [Page 1]\n\f\nRFC 4966 NAT-PT Issues Analysis July 2007 4966 algorithm management qualified trust nested-reference unchanged"},{"id":"IETF RFC 5214","type":"specification","body":"IETF","designation":"RFC 5214","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5214.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5214.txt","https://www.rfc-editor.org/rfc/rfc5214.pdf"],"folder":"IETF/RFC-5214","files":{"txt":{"path":"standards/IETF/RFC-5214/RFC-5214.txt","sha256":"48fc5993e4de6d9e5b8cb1d1416a2b903a337c9671e6b813ab01bdf54066c461"}},"tags":["nested-reference","unchanged"],"summary":"The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects\n dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the\n IPv4 network as a link layer for IPv6 and supports an automatic\n tunneling abstraction similar to the Non-Broadcast Multiple Access\n (NBMA) model.\n\nTemplin, et al. Informational [Page 1]\n\f\nRFC 5214 ISATAP March 2008","scope_keywords":["5214","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 5214 The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects\n dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the\n IPv4 network as a link layer for IPv6 and supports an automatic\n tunneling abstraction similar to the Non-Broadcast Multiple Access\n (NBMA) model.\n\nTemplin, et al. Informational [Page 1]\n\f\nRFC 5214 ISATAP March 2008 5214 key trust nested-reference unchanged"},{"id":"IETF RFC 5223","type":"specification","body":"IETF","designation":"RFC 5223","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5223.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5223.txt","https://www.rfc-editor.org/rfc/rfc5223.pdf"],"folder":"IETF/RFC-5223","files":{"txt":{"path":"standards/IETF/RFC-5223/RFC-5223.txt","sha256":"deb14555e48e65b48b2db8f7df541f76fc208be5d38c8e7a018cff3dacfcf2d3"}},"tags":["nested-reference","unchanged"],"summary":"The Location-to-Service Translation (LoST) Protocol describes an XML-\n based protocol for mapping service identifiers and geospatial or\n civic location information to service contact Uniform Resource\n Locators (URLs). LoST servers can be located anywhere, but a\n placement closer to the end host, e.g., in the access network, is\n desirable. In disaster situations with intermittent network\n connectivity, such a LoST server placement provides benefits\n regarding the resiliency of emergency service communication.\n\n This document describes how a LoST client can discover a LoST server\n using the Dynamic Host Configuration Protocol (DHCP).\n\nSchulzrinne, et al. Standards Track [Page 1]\n\f\nRFC 5223 DHCP-Based LoST Discovery August 2008","scope_keywords":["5223","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5223 The Location-to-Service Translation (LoST) Protocol describes an XML-\n based protocol for mapping service identifiers and geospatial or\n civic location information to service contact Uniform Resource\n Locators (URLs). LoST servers can be located anywhere, but a\n placement closer to the end host, e.g., in the access network, is\n desirable. In disaster situations with intermittent network\n connectivity, such a LoST server placement provides benefits\n regarding the resiliency of emergency service communication.\n\n This document describes how a LoST client can discover a LoST server\n using the Dynamic Host Configuration Protocol (DHCP).\n\nSchulzrinne, et al. Standards Track [Page 1]\n\f\nRFC 5223 DHCP-Based LoST Discovery August 2008 5223 key qualified nested-reference unchanged"},{"id":"IETF RFC 5321","type":"specification","body":"IETF","designation":"RFC 5321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5321.txt","https://www.rfc-editor.org/rfc/rfc5321.pdf"],"folder":"IETF/RFC-5321","files":{"txt":{"path":"standards/IETF/RFC-5321/RFC-5321.txt","sha256":"7d560eddff1b213c17d4e1e5f95005728b2f05bc2b3947f0fcc91717c6707634"}},"tags":["nested-reference","unchanged"],"summary":"This document is a specification of the basic protocol for Internet\n electronic mail transport. It consolidates, updates, and clarifies\n several previous documents, making all or parts of most of them\n obsolete. It covers the SMTP extension mechanisms and best practices\n for the contemporary Internet, but does not provide details about\n particular extensions. Although SMTP was designed as a mail\n transport and delivery protocol, this specification also contains\n information that is important to its use as a \"mail submission\"\n protocol for \"split-UA\" (User Agent) mail reading systems and mobile\n environments.\n\nKlensin Standards Track [Page 1]\n\f\nRFC 5321 SMTP October 2008","scope_keywords":["5321","crl","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5672","folder":"IETF/RFC-5672","source":"IETF/RFC-5672/RFC-5672.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 5321 This document is a specification of the basic protocol for Internet\n electronic mail transport. It consolidates, updates, and clarifies\n several previous documents, making all or parts of most of them\n obsolete. It covers the SMTP extension mechanisms and best practices\n for the contemporary Internet, but does not provide details about\n particular extensions. Although SMTP was designed as a mail\n transport and delivery protocol, this specification also contains\n information that is important to its use as a \"mail submission\"\n protocol for \"split-UA\" (User Agent) mail reading systems and mobile\n environments.\n\nKlensin Standards Track [Page 1]\n\f\nRFC 5321 SMTP October 2008 5321 crl delivery path nested-reference unchanged"},{"id":"IETF RFC 5451","type":"specification","body":"IETF","designation":"RFC 5451","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5451.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5451.txt","https://www.rfc-editor.org/rfc/rfc5451.pdf"],"folder":"IETF/RFC-5451","files":{"txt":{"path":"standards/IETF/RFC-5451/RFC-5451.txt","sha256":"ab9b31afe82a0c74f189e3e78530215699cb0a671f3e2b89f959954f6e5ce131"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new header field for use with electronic mail\n messages to indicate the results of message authentication efforts.\n Any receiver-side software, such as mail filters or Mail User Agents\n (MUAs), may use this message header field to relay that information\n in a convenient way to users or to make sorting and filtering\n decisions.\n\nKucherawy Standards Track [Page 1]\n\f\nRFC 5451 Authentication-Results Header Field April 2009","scope_keywords":["5451","authentication","http","key","keys","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6212","folder":"IETF/RFC-6212","source":"IETF/RFC-6212/RFC-6212.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 5451 This memo defines a new header field for use with electronic mail\n messages to indicate the results of message authentication efforts.\n Any receiver-side software, such as mail filters or Mail User Agents\n (MUAs), may use this message header field to relay that information\n in a convenient way to users or to make sorting and filtering\n decisions.\n\nKucherawy Standards Track [Page 1]\n\f\nRFC 5451 Authentication-Results Header Field April 2009 5451 authentication http key keys license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5507","type":"specification","body":"IETF","designation":"RFC 5507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5507.txt","https://www.rfc-editor.org/rfc/rfc5507.pdf"],"folder":"IETF/RFC-5507","files":{"txt":{"path":"standards/IETF/RFC-5507/RFC-5507.txt","sha256":"f76fed64ab5f816f02017ddd5a90ce84919cbdc2c54392da80b5a68a9224da61"}},"tags":["nested-reference","unchanged"],"summary":"This note discusses how to extend the DNS with new data for a new\n application. DNS extension discussions too often focus on reuse of\n the TXT Resource Record Type. This document lists different\n mechanisms to extend the DNS, and concludes that the use of a new DNS\n Resource Record Type is the best solution.\n\nIAB, et al. Informational [Page 1]\n\f\nRFC 5507 Design Choices When Expanding the DNS April 2009","scope_keywords":["5507","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 5507 This note discusses how to extend the DNS with new data for a new\n application. DNS extension discussions too often focus on reuse of\n the TXT Resource Record Type. This document lists different\n mechanisms to extend the DNS, and concludes that the use of a new DNS\n Resource Record Type is the best solution.\n\nIAB, et al. Informational [Page 1]\n\f\nRFC 5507 Design Choices When Expanding the DNS April 2009 5507 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5518","type":"specification","body":"IETF","designation":"RFC 5518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5518.txt","https://www.rfc-editor.org/rfc/rfc5518.pdf"],"folder":"IETF/RFC-5518","files":{"txt":{"path":"standards/IETF/RFC-5518/RFC-5518.txt","sha256":"6af3f32caf8e2d866ad9e4beb1af11a37509ff5aef3d4eb01056a93bb93725ab"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Vouch By Reference (VBR) protocol. VBR\n is a protocol for adding third-party certification to email. It\n permits independent third parties to certify the owner of a domain\n name that is associated with received mail.\n\nHoffman, et al. Standards Track [Page 1]\n\f\nRFC 5518 VBR April 2009","scope_keywords":["5518","attestation","attestations","http","key","keys","license","path","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 6212","folder":"IETF/RFC-6212","source":"IETF/RFC-6212/RFC-6212.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5518 This document describes the Vouch By Reference (VBR) protocol. VBR\n is a protocol for adding third-party certification to email. It\n permits independent third parties to certify the owner of a domain\n name that is associated with received mail.\n\nHoffman, et al. Standards Track [Page 1]\n\f\nRFC 5518 VBR April 2009 5518 attestation attestations http key keys license path signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5617","type":"specification","body":"IETF","designation":"RFC 5617","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5617.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5617.txt","https://www.rfc-editor.org/rfc/rfc5617.pdf"],"folder":"IETF/RFC-5617","files":{"txt":{"path":"standards/IETF/RFC-5617/RFC-5617.txt","sha256":"507e411eb9826a48e677f257049a0e5d8c0f9f3eb73eab79b6b8c15bbda1edaa"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) defines a domain-level\n authentication framework for email to permit verification of the\n source and contents of messages. This document specifies an adjunct\n mechanism to aid in assessing messages that do not contain a DKIM\n signature for the domain used in the author's address. It defines a\n record that can advertise whether a domain signs its outgoing mail as\n well as how other hosts can access that record.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n docu","scope_keywords":["5617","authentication","http","key","keys","license","policies","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5617 DomainKeys Identified Mail (DKIM) defines a domain-level\n authentication framework for email to permit verification of the\n source and contents of messages. This document specifies an adjunct\n mechanism to aid in assessing messages that do not contain a DKIM\n signature for the domain used in the author's address. It defines a\n record that can advertise whether a domain signs its outgoing mail as\n well as how other hosts can access that record.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n docu 5617 authentication http key keys license policies presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5965","type":"specification","body":"IETF","designation":"RFC 5965","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5965.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5965.txt","https://www.rfc-editor.org/rfc/rfc5965.pdf"],"folder":"IETF/RFC-5965","files":{"txt":{"path":"standards/IETF/RFC-5965/RFC-5965.txt","sha256":"7bae3f53cbe170370cd5a8e25fa95232e75cf1ecb0ef15d9fc1b36995d1ddaeb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extensible format and MIME type that may be\n used by mail operators to report feedback about received email to\n other parties. This format is intended as a machine-readable\n replacement for various existing report formats currently used in\n Internet email.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5965.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and ","scope_keywords":["5965","authentication","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6430","folder":"IETF/RFC-6430","source":"IETF/RFC-6430/RFC-6430.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 5965 This document defines an extensible format and MIME type that may be\n used by mail operators to report feedback about received email to\n other parties. This format is intended as a machine-readable\n replacement for various existing report formats currently used in\n Internet email.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5965.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and  5965 authentication http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5986","type":"specification","body":"IETF","designation":"RFC 5986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5986.txt","https://www.rfc-editor.org/rfc/rfc5986.pdf"],"folder":"IETF/RFC-5986","files":{"txt":{"path":"standards/IETF/RFC-5986/RFC-5986.txt","sha256":"b1958c546d8be956041323ba68a82f3572dc8444382a5aafc5dfe22c51c0ac93"}},"tags":["nested-reference","unchanged"],"summary":"Discovery of the correct Location Information Server (LIS) in the\n local access network is necessary for Devices that wish to acquire\n location information from the network. A method is described for the\n discovery of a LIS in the access network serving a Device. Dynamic\n Host Configuration Protocol (DHCP) options for IP versions 4 and 6\n are defined that specify a domain name. This domain name is then\n used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cu","scope_keywords":["5986","delivery","http","https","key","license","profile","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 5986 Discovery of the correct Location Information Server (LIS) in the\n local access network is necessary for Devices that wish to acquire\n location information from the network. A method is described for the\n discovery of a LIS in the access network serving a Device. Dynamic\n Host Configuration Protocol (DHCP) options for IP versions 4 and 6\n are defined that specify a domain name. This domain name is then\n used as input to a URI-enabled NAPTR (U-NAPTR) resolution process.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cu 5986 delivery http https key license profile registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6108","type":"specification","body":"IETF","designation":"RFC 6108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6108.txt","https://www.rfc-editor.org/rfc/rfc6108.pdf"],"folder":"IETF/RFC-6108","files":{"txt":{"path":"standards/IETF/RFC-6108/RFC-6108.txt","sha256":"b440af599e3e722a3cf98d01a64ef05f5a066ce3bac86d2636e7a8f0460abe9d"}},"tags":["nested-reference","unchanged"],"summary":"The objective of this document is to describe a method of providing\n critical end-user notifications to web browsers, which has been\n deployed by Comcast, an Internet Service Provider (ISP). Such a\n notification system is being used to provide near-immediate\n notifications to customers, such as to warn them that their traffic\n exhibits patterns that are indicative of malware or virus infection.\n There are other proprietary systems that can perform such\n notifications, but those systems utilize Deep Packet Inspection (DPI)\n technology. In contrast to DPI, this document describes a system\n that does not rely upon DPI, and is instead based in open IETF\n standards and open source applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any othe","scope_keywords":["6108","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6108 The objective of this document is to describe a method of providing\n critical end-user notifications to web browsers, which has been\n deployed by Comcast, an Internet Service Provider (ISP). Such a\n notification system is being used to provide near-immediate\n notifications to customers, such as to warn them that their traffic\n exhibits patterns that are indicative of malware or virus infection.\n There are other proprietary systems that can perform such\n notifications, but those systems utilize Deep Packet Inspection (DPI)\n technology. In contrast to DPI, this document describes a system\n that does not rely upon DPI, and is instead based in open IETF\n standards and open source applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any othe 6108 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6122","type":"specification","body":"IETF","designation":"RFC 6122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6122.txt","https://www.rfc-editor.org/rfc/rfc6122.pdf"],"folder":"IETF/RFC-6122","files":{"txt":{"path":"standards/IETF/RFC-6122/RFC-6122.txt","sha256":"1f4f2d9e13f68413303acfe4a9fba8c7e3afc6d6ae2a470cc3735ffb9bd4efb7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format for addresses used in the Extensible\n Messaging and Presence Protocol (XMPP), including support for\n non-ASCII characters. This document updates RFC 3920.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6122.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje","scope_keywords":["6122","http","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null}],"search_text":"IETF RFC 6122 This document defines the format for addresses used in the Extensible\n Messaging and Presence Protocol (XMPP), including support for\n non-ASCII characters. This document updates RFC 3920.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6122.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje 6122 http key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 6406","type":"specification","body":"IETF","designation":"RFC 6406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6406.txt","https://www.rfc-editor.org/rfc/rfc6406.pdf"],"folder":"IETF/RFC-6406","files":{"txt":{"path":"standards/IETF/RFC-6406/RFC-6406.txt","sha256":"5b1c10c459360590a6ae8aa399e6d78ade53d0e7ce46b13c5f80e18301253d4b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a peering architecture for the Session\n Initiation Protocol (SIP) and its functional components and\n interfaces. It also describes the components and the steps necessary\n to establish a session between two SIP Service Provider (SSP) peering\n domains.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht","scope_keywords":["6406","http","key","license","path","subject","tls","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null}],"search_text":"IETF RFC 6406 This document defines a peering architecture for the Session\n Initiation Protocol (SIP) and its functional components and\n interfaces. It also describes the components and the steps necessary\n to establish a session between two SIP Service Provider (SSP) peering\n domains.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht 6406 http key license path subject tls trust tsp nested-reference unchanged"},{"id":"IETF RFC 6408","type":"specification","body":"IETF","designation":"RFC 6408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6408.txt","https://www.rfc-editor.org/rfc/rfc6408.pdf"],"folder":"IETF/RFC-6408","files":{"txt":{"path":"standards/IETF/RFC-6408/RFC-6408.txt","sha256":"194b438df7a698f6286bb1e8cf333d80fa4c22ad3efc2e228f5ece8ec4b8225e"}},"tags":["nested-reference","unchanged"],"summary":"The Diameter base protocol specifies mechanisms whereby a given realm\n may advertise Diameter nodes and the supported transport protocol.\n However, these mechanisms do not reveal the Diameter applications\n that each node supports. A peer outside the realm would have to\n perform a Diameter capability exchange with every node until it\n discovers one that supports the required application. This document\n updates RFC 3588, \"Diameter Base Protocol\", and describes an\n improvement using an extended format for the Straightforward-Naming\n Authority Pointer (S-NAPTR) application service tag that allows for\n discovery of the supported applications without doing Diameter\n capability exchange beforehand.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It","scope_keywords":["6408","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 6408 The Diameter base protocol specifies mechanisms whereby a given realm\n may advertise Diameter nodes and the supported transport protocol.\n However, these mechanisms do not reveal the Diameter applications\n that each node supports. A peer outside the realm would have to\n perform a Diameter capability exchange with every node until it\n discovers one that supports the required application. This document\n updates RFC 3588, \"Diameter Base Protocol\", and describes an\n improvement using an extended format for the Straightforward-Naming\n Authority Pointer (S-NAPTR) application service tag that allows for\n discovery of the supported applications without doing Diameter\n capability exchange beforehand.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It 6408 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6541","type":"specification","body":"IETF","designation":"RFC 6541","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6541.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6541.txt","https://www.rfc-editor.org/rfc/rfc6541.pdf"],"folder":"IETF/RFC-6541","files":{"txt":{"path":"standards/IETF/RFC-6541/RFC-6541.txt","sha256":"092aa7672a9cab8d161c3ece1de721107cc12fa8a1e895bc48b1a99610a5093d"}},"tags":["nested-reference","unchanged"],"summary":"This experimental specification proposes a modification to DomainKeys\n Identified Mail (DKIM) allowing advertisement of third-party\n signature authorizations that are to be interpreted as equivalent to\n a signature added by the administrative domain of the message's\n author.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Informatio","scope_keywords":["6541","authentication","authorization","hash","http","key","keys","license","management","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 6541 This experimental specification proposes a modification to DomainKeys\n Identified Mail (DKIM) allowing advertisement of third-party\n signature authorizations that are to be interpreted as equivalent to\n a signature added by the administrative domain of the message's\n author.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Informatio 6541 authentication authorization hash http key keys license management signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6610","type":"specification","body":"IETF","designation":"RFC 6610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6610.txt","https://www.rfc-editor.org/rfc/rfc6610.pdf"],"folder":"IETF/RFC-6610","files":{"txt":{"path":"standards/IETF/RFC-6610/RFC-6610.txt","sha256":"202fe04d9a001f850ae079bdee2007c39772dee970d26f1cee32973aee846100"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a DHCP-based scheme to enable dynamic discovery\n of Mobile IPv6 home network information. New DHCP options are\n defined that allow a mobile node to request the home agent IP\n address, Fully Qualified Domain Name (FQDN), or home network prefix\n and obtain it via the DHCP response.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6610.\n\nCopyright Notice\n\n Copyright (c)","scope_keywords":["6610","authentication","http","key","license","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 6610 This document defines a DHCP-based scheme to enable dynamic discovery\n of Mobile IPv6 home network information. New DHCP options are\n defined that allow a mobile node to request the home agent IP\n address, Fully Qualified Domain Name (FQDN), or home network prefix\n and obtain it via the DHCP response.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6610.\n\nCopyright Notice\n\n Copyright (c) 6610 authentication http key license qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6647","type":"specification","body":"IETF","designation":"RFC 6647","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6647.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6647.txt","https://www.rfc-editor.org/rfc/rfc6647.pdf"],"folder":"IETF/RFC-6647","files":{"txt":{"path":"standards/IETF/RFC-6647/RFC-6647.txt","sha256":"8a301895c34ca893a07eb1b2f1d7c5b6d18a390f007170ae4430b3dbf344857c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the art of email greylisting, the practice of\n providing temporarily degraded service to unknown email clients as an\n anti-abuse mechanism.\n\n Greylisting is an established mechanism deemed essential to the\n repertoire of current anti-abuse email filtering systems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6647.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Tru","scope_keywords":["6647","attribute","attributes","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 6647 This document describes the art of email greylisting, the practice of\n providing temporarily degraded service to unknown email clients as an\n anti-abuse mechanism.\n\n Greylisting is an established mechanism deemed essential to the\n repertoire of current anti-abuse email filtering systems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6647.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Tru 6647 attribute attributes delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6651","type":"specification","body":"IETF","designation":"RFC 6651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6651.txt","https://www.rfc-editor.org/rfc/rfc6651.pdf"],"folder":"IETF/RFC-6651","files":{"txt":{"path":"standards/IETF/RFC-6651/RFC-6651.txt","sha256":"e69677ba7c2cb8fd1019e99ed57eea6bd0609f8cfcc462384dc19fde601b12d3"}},"tags":["nested-reference","unchanged"],"summary":"This document presents extensions to the DomainKeys Identified Mail\n (DKIM) specification to allow for detailed reporting of message\n authentication failures in an on-demand fashion.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6651.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to","scope_keywords":["6651","algorithm","authentication","http","key","keys","license","management","policy","signature","signatures","subject","trust","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6651 This document presents extensions to the DomainKeys Identified Mail\n (DKIM) specification to allow for detailed reporting of message\n authentication failures in an on-demand fashion.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6651.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to 6651 algorithm authentication http key keys license management policy signature signatures subject trust verifiable nested-reference unchanged"},{"id":"IETF RFC 6686","type":"specification","body":"IETF","designation":"RFC 6686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6686.txt","https://www.rfc-editor.org/rfc/rfc6686.pdf"],"folder":"IETF/RFC-6686","files":{"txt":{"path":"standards/IETF/RFC-6686/RFC-6686.txt","sha256":"6614bb0f2217f65c07a6dd76059461be39697b5bf839792de4b2e2edabcdcfdd"}},"tags":["nested-reference","unchanged"],"summary":"In 2006, the IETF published a suite of protocol documents comprising\n the Sender Policy Framework (SPF) and Sender ID: two proposed email\n authentication protocols. Both of these protocols enable one to\n publish, via the Domain Name System, a policy declaring which mail\n servers were authorized to send email on behalf of the domain name\n being queried. There was concern that the two would conflict in some\n significant operational situations, interfering with message\n delivery.\n\n The IESG required all of these documents (RFC 4405, RFC 4406, RFC\n 4407, and RFC 4408) to be published as Experimental RFCs and\n requested that the community observe deployment and operation of the\n protocols over a period of two years from the date of publication to\n determine a reasonable path forward.\n\n After six years, sufficient experience and evidence have been\n collected that the experiments thus created c","scope_keywords":["6686","authentication","delivery","http","license","path","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 6686 In 2006, the IETF published a suite of protocol documents comprising\n the Sender Policy Framework (SPF) and Sender ID: two proposed email\n authentication protocols. Both of these protocols enable one to\n publish, via the Domain Name System, a policy declaring which mail\n servers were authorized to send email on behalf of the domain name\n being queried. There was concern that the two would conflict in some\n significant operational situations, interfering with message\n delivery.\n\n The IESG required all of these documents (RFC 4405, RFC 4406, RFC\n 4407, and RFC 4408) to be published as Experimental RFCs and\n requested that the community observe deployment and operation of the\n protocols over a period of two years from the date of publication to\n determine a reasonable path forward.\n\n After six years, sufficient experience and evidence have been\n collected that the experiments thus created c 6686 authentication delivery http license path policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6797","type":"specification","body":"IETF","designation":"RFC 6797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6797.txt","https://www.rfc-editor.org/rfc/rfc6797.pdf"],"folder":"IETF/RFC-6797","files":{"txt":{"path":"standards/IETF/RFC-6797/RFC-6797.txt","sha256":"7cefa03f77547532580b7f877b4e6388bb66c20631b624667a0065c14ae3d364"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a mechanism enabling web sites to declare\n themselves accessible only via secure connections and/or for users to\n be able to direct their user agent(s) to interact with given sites\n only over secure connections. This overall policy is referred to as\n HTTP Strict Transport Security (HSTS). The policy is declared by web\n sites via the Strict-Transport-Security HTTP response header field\n and/or by other means, such as user agent configuration, for example.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information ","scope_keywords":["6797","attribute","certificate","certificates","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 6797 This specification defines a mechanism enabling web sites to declare\n themselves accessible only via secure connections and/or for users to\n be able to direct their user agent(s) to interact with given sites\n only over secure connections. This overall policy is referred to as\n HTTP Strict Transport Security (HSTS). The policy is declared by web\n sites via the Strict-Transport-Security HTTP response header field\n and/or by other means, such as user agent configuration, for example.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information  6797 attribute certificate certificates http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6833","type":"specification","body":"IETF","designation":"RFC 6833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6833.txt","https://www.rfc-editor.org/rfc/rfc6833.pdf"],"folder":"IETF/RFC-6833","files":{"txt":{"path":"standards/IETF/RFC-6833/RFC-6833.txt","sha256":"5ffed2142ffecb02ff5b517e1bac540ff4694857c3f7d958edc46f9473bdb81e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Mapping Service for the Locator/ID\n Separation Protocol (LISP), implemented by two new types of LISP-\n speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that\n provides a simplified \"front end\" for one or more Endpoint ID to\n Routing Locator mapping databases.\n\n By using this service interface and communicating with Map-Resolvers\n and Map-Servers, LISP Ingress Tunnel Routers and Egress Tunnel\n Routers are not dependent on the details of mapping database systems,\n which facilitates experimentation with different database designs.\n Since these devices implement the \"edge\" of the LISP infrastructure,\n connect directly to LISP-capable Internet end sites, and comprise the\n bulk of LISP-speaking devices, reducing their implementation and\n operational complexity should also reduce the overall cost and effort\n of deploying LISP.\n\nStatus of This Memo\n\n Th","scope_keywords":["6833","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null}],"search_text":"IETF RFC 6833 This document describes the Mapping Service for the Locator/ID\n Separation Protocol (LISP), implemented by two new types of LISP-\n speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that\n provides a simplified \"front end\" for one or more Endpoint ID to\n Routing Locator mapping databases.\n\n By using this service interface and communicating with Map-Resolvers\n and Map-Servers, LISP Ingress Tunnel Routers and Egress Tunnel\n Routers are not dependent on the details of mapping database systems,\n which facilitates experimentation with different database designs.\n Since these devices implement the \"edge\" of the LISP infrastructure,\n connect directly to LISP-capable Internet end sites, and comprise the\n bulk of LISP-speaking devices, reducing their implementation and\n operational complexity should also reduce the overall cost and effort\n of deploying LISP.\n\nStatus of This Memo\n\n Th 6833 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6891","type":"specification","body":"IETF","designation":"RFC 6891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6891.txt","https://www.rfc-editor.org/rfc/rfc6891.pdf"],"folder":"IETF/RFC-6891","files":{"txt":{"path":"standards/IETF/RFC-6891/RFC-6891.txt","sha256":"626d2d3a8febe5c92fb90a84b0891ec2f6c983a681ab5d06040c75ef2119491f"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System's wire protocol includes a number of fixed\n fields whose range has been or soon will be exhausted and does not\n allow requestors to advertise their capabilities to responders. This\n document describes backward-compatible mechanisms for allowing the\n protocol to grow.\n\n This document updates the Extension Mechanisms for DNS (EDNS(0))\n specification (and obsoletes RFC 2671) based on feedback from\n deployment experience in several implementations. It also obsoletes\n RFC 2673 (\"Binary Labels in the Domain Name System\") and adds\n considerations on the use of extended labels in the DNS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine","scope_keywords":["6891","http","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7830","folder":"IETF/RFC-7830","source":"IETF/RFC-7830/RFC-7830.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6891 The Domain Name System's wire protocol includes a number of fixed\n fields whose range has been or soon will be exhausted and does not\n allow requestors to advertise their capabilities to responders. This\n document describes backward-compatible mechanisms for allowing the\n protocol to grow.\n\n This document updates the Extension Mechanisms for DNS (EDNS(0))\n specification (and obsoletes RFC 2671) based on feedback from\n deployment experience in several implementations. It also obsoletes\n RFC 2673 (\"Binary Labels in the Domain Name System\") and adds\n considerations on the use of extended labels in the DNS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine 6891 http license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6927","type":"specification","body":"IETF","designation":"RFC 6927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6927.txt","https://www.rfc-editor.org/rfc/rfc6927.pdf"],"folder":"IETF/RFC-6927","files":{"txt":{"path":"standards/IETF/RFC-6927/RFC-6927.txt","sha256":"f4eb6a102ce61e64bd49398a42d0e819035c339a45811f2e1f25b834becd3760"}},"tags":["nested-reference","unchanged"],"summary":"Internationalized Domain Names for Applications (IDNA) provides a\n method to map a subset of names written in Unicode into the DNS.\n Because of Unicode decisions, appearance, language and writing system\n conventions, and historical reasons, it often has been asserted that\n there is more than one way to write what competent readers and\n writers think of as the same host name; these different ways of\n writing are often called \"variants\". (The authors note that there\n are many conflicting definitions for the term \"variant\" in the IDNA\n community.) This document surveys the approaches that top-level\n domains have taken to the registration and provisioning of domain\n names that have variants. This document is not a product of the\n IETF, does not propose any method to make variants work \"correctly\",\n and is not an introduction to internationalization or IDNA.\n\nStatus of This Memo\n\n This docume","scope_keywords":["6927","http","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 6927 Internationalized Domain Names for Applications (IDNA) provides a\n method to map a subset of names written in Unicode into the DNS.\n Because of Unicode decisions, appearance, language and writing system\n conventions, and historical reasons, it often has been asserted that\n there is more than one way to write what competent readers and\n writers think of as the same host name; these different ways of\n writing are often called \"variants\". (The authors note that there\n are many conflicting definitions for the term \"variant\" in the IDNA\n community.) This document surveys the approaches that top-level\n domains have taken to the registration and provisioning of domain\n names that have variants. This document is not a product of the\n IETF, does not propose any method to make variants work \"correctly\",\n and is not an introduction to internationalization or IDNA.\n\nStatus of This Memo\n\n This docume 6927 http license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7001","type":"specification","body":"IETF","designation":"RFC 7001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7001.txt","https://www.rfc-editor.org/rfc/rfc7001.pdf"],"folder":"IETF/RFC-7001","files":{"txt":{"path":"standards/IETF/RFC-7001/RFC-7001.txt","sha256":"658621c11610361ea006ab4de9b50c290c077cd169e089f6440cc50f27f4b72e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a message header field called Authentication-\n Results for use with electronic mail messages to indicate the results\n of message authentication efforts. Any receiver-side software, such\n as mail filters or Mail User Agents (MUAs), can use this header field\n to relay that information in a convenient and meaningful way to users\n or to make sorting and filtering decisions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it","scope_keywords":["7001","authentication","http","key","keys","license","policy","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null}],"search_text":"IETF RFC 7001 This document specifies a message header field called Authentication-\n Results for use with electronic mail messages to indicate the results\n of message authentication efforts. Any receiver-side software, such\n as mail filters or Mail User Agents (MUAs), can use this header field\n to relay that information in a convenient and meaningful way to users\n or to make sorting and filtering decisions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it 7001 authentication http key keys license policy registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7070","type":"specification","body":"IETF","designation":"RFC 7070","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7070.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7070.txt","https://www.rfc-editor.org/rfc/rfc7070.pdf"],"folder":"IETF/RFC-7070","files":{"txt":{"path":"standards/IETF/RFC-7070/RFC-7070.txt","sha256":"313fc8f718998e6f0dcc314ee66d51ff594b42851886835c6dd5932021a45fcd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general architecture for a reputation-based\n service, allowing one to request reputation-related data over the\n Internet, where \"reputation\" refers to predictions or expectations\n about an entity or an identifier such as a domain name. The document\n roughly follows the recommendations of RFC 4101 for describing a\n protocol model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edi","scope_keywords":["7070","authentication","delivery","http","key","keys","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null}],"search_text":"IETF RFC 7070 This document describes a general architecture for a reputation-based\n service, allowing one to request reputation-related data over the\n Internet, where \"reputation\" refers to predictions or expectations\n about an entity or an identifier such as a domain name. The document\n roughly follows the recommendations of RFC 4101 for describing a\n protocol model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edi 7070 authentication delivery http key keys license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7344","type":"specification","body":"IETF","designation":"RFC 7344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7344.txt","https://www.rfc-editor.org/rfc/rfc7344.pdf"],"folder":"IETF/RFC-7344","files":{"txt":{"path":"standards/IETF/RFC-7344/RFC-7344.txt","sha256":"7c058d7c6ff79a4a5636d70b55ce4b9ddb5f31c4869a50bb8bed3fb097cc28bc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method to allow DNS Operators to more\n easily update DNSSEC Key Signing Keys using the DNS as a\n communication channel. The technique described is aimed at\n delegations in which it is currently hard to move information from\n the Child to Parent.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n htt","scope_keywords":["7344","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8078","folder":"IETF/RFC-8078","source":"IETF/RFC-8078/RFC-8078.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7344 This document describes a method to allow DNS Operators to more\n easily update DNSSEC Key Signing Keys using the DNS as a\n communication channel. The technique described is aimed at\n delegations in which it is currently hard to move information from\n the Child to Parent.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n htt 7344 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 7489","type":"specification","body":"IETF","designation":"RFC 7489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7489.txt","https://www.rfc-editor.org/rfc/rfc7489.pdf"],"folder":"IETF/RFC-7489","files":{"txt":{"path":"standards/IETF/RFC-7489/RFC-7489.txt","sha256":"1ac7c343cb45cad1b597a0fee05b66c80adcd0e55a2312df8c300762456d9a1b"}},"tags":["nested-reference","unchanged"],"summary":"Domain-based Message Authentication, Reporting, and Conformance\n (DMARC) is a scalable mechanism by which a mail-originating\n organization can express domain-level policies and preferences for\n message validation, disposition, and reporting, that a mail-receiving\n organization can use to improve mail handling.\n\n Originators of Internet Mail need to be able to associate reliable\n and authenticated domain identifiers with messages, communicate\n policies about messages that use those identifiers, and report about\n mail using those identifiers. These abilities have several benefits:\n Receivers can provide feedback to Domain Owners about the use of\n their domains; this feedback can provide valuable insight about the\n management of internal operations and the presence of external domain\n name abuse.\n\n DMARC does not produce or encourage elevated delivery privilege of\n authenticated email. DMAR","scope_keywords":["7489","authentication","delivery","http","key","license","management","policies","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 7489 Domain-based Message Authentication, Reporting, and Conformance\n (DMARC) is a scalable mechanism by which a mail-originating\n organization can express domain-level policies and preferences for\n message validation, disposition, and reporting, that a mail-receiving\n organization can use to improve mail handling.\n\n Originators of Internet Mail need to be able to associate reliable\n and authenticated domain identifiers with messages, communicate\n policies about messages that use those identifiers, and report about\n mail using those identifiers. These abilities have several benefits:\n Receivers can provide feedback to Domain Owners about the use of\n their domains; this feedback can provide valuable insight about the\n management of internal operations and the presence of external domain\n name abuse.\n\n DMARC does not produce or encourage elevated delivery privilege of\n authenticated email. DMAR 7489 authentication delivery http key license management policies policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7553","type":"specification","body":"IETF","designation":"RFC 7553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7553.txt","https://www.rfc-editor.org/rfc/rfc7553.pdf"],"folder":"IETF/RFC-7553","files":{"txt":{"path":"standards/IETF/RFC-7553/RFC-7553.txt","sha256":"11202efe3e5b6a8134444013029d75ac16806d13d7666f246ddb497e0fcce1ee"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the already registered DNS resource record\n (RR) type, called the Uniform Resource Identifier (URI) RR, that is\n used for publishing mappings from hostnames to URIs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7553.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF T","scope_keywords":["7553","algorithm","algorithms","http","key","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 7553 This document describes the already registered DNS resource record\n (RR) type, called the Uniform Resource Identifier (URI) RR, that is\n used for publishing mappings from hostnames to URIs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7553.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF T 7553 algorithm algorithms http key license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7594","type":"specification","body":"IETF","designation":"RFC 7594","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7594.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7594.txt","https://www.rfc-editor.org/rfc/rfc7594.pdf"],"folder":"IETF/RFC-7594","files":{"txt":{"path":"standards/IETF/RFC-7594/RFC-7594.txt","sha256":"76a2b4cf2b2af0131bb81e754287560c8f3259bc700d103c8757b4bbec9c8821"}},"tags":["nested-reference","unchanged"],"summary":"Measuring broadband service on a large scale requires a description\n of the logical architecture and standardisation of the key protocols\n that coordinate interactions between the components. This document\n presents an overall framework for large-scale measurements. It also\n defines terminology for LMAP (Large-Scale Measurement of Broadband\n Performance).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of","scope_keywords":["7594","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 7594 Measuring broadband service on a large scale requires a description\n of the logical architecture and standardisation of the key protocols\n that coordinate interactions between the components. This document\n presents an overall framework for large-scale measurements. It also\n defines terminology for LMAP (Large-Scale Measurement of Broadband\n Performance).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of 7594 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7671","type":"specification","body":"IETF","designation":"RFC 7671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7671.txt","https://www.rfc-editor.org/rfc/rfc7671.pdf"],"folder":"IETF/RFC-7671","files":{"txt":{"path":"standards/IETF/RFC-7671/RFC-7671.txt","sha256":"56547af092d9c7b31e3ec89762329953f513e354f23d556d82161773d41f5037"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies and updates the DNS-Based Authentication of\n Named Entities (DANE) TLSA specification (RFC 6698), based on\n subsequent implementation experience. It also contains guidance for\n implementers, operators, and protocol developers who want to use DANE\n records.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7671.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and t","scope_keywords":["7671","algorithm","authentication","certificate","encryption","http","key","keys","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 7671 This document clarifies and updates the DNS-Based Authentication of\n Named Entities (DANE) TLSA specification (RFC 6698), based on\n subsequent implementation experience. It also contains guidance for\n implementers, operators, and protocol developers who want to use DANE\n records.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7671.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and t 7671 algorithm authentication certificate encryption http key keys license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7706","type":"specification","body":"IETF","designation":"RFC 7706","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7706.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7706.txt","https://www.rfc-editor.org/rfc/rfc7706.pdf"],"folder":"IETF/RFC-7706","files":{"txt":{"path":"standards/IETF/RFC-7706/RFC-7706.txt","sha256":"ebe0f2f66803c7c43846fe4dfd5a54be2977d5debea527489245ad2f74e32e68"}},"tags":["nested-reference","unchanged"],"summary":"Some DNS recursive resolvers have longer-than-desired round-trip\n times to the closest DNS root server. Some DNS recursive resolver\n operators want to prevent snooping of requests sent to DNS root\n servers by third parties. Such resolvers can greatly decrease the\n round-trip time and prevent observation of requests by running a copy\n of the full root zone on a loopback address (such as 127.0.0.1).\n This document shows how to start and maintain such a copy of the root\n zone that does not pose a threat to other users of the DNS, at the\n cost of adding some operational fragility for the operator.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has ","scope_keywords":["7706","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null}],"search_text":"IETF RFC 7706 Some DNS recursive resolvers have longer-than-desired round-trip\n times to the closest DNS root server. Some DNS recursive resolver\n operators want to prevent snooping of requests sent to DNS root\n servers by third parties. Such resolvers can greatly decrease the\n round-trip time and prevent observation of requests by running a copy\n of the full root zone on a loopback address (such as 127.0.0.1).\n This document shows how to start and maintain such a copy of the root\n zone that does not pose a threat to other users of the DNS, at the\n cost of adding some operational fragility for the operator.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has  7706 http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7828","type":"specification","body":"IETF","designation":"RFC 7828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7828.txt","https://www.rfc-editor.org/rfc/rfc7828.pdf"],"folder":"IETF/RFC-7828","files":{"txt":{"path":"standards/IETF/RFC-7828/RFC-7828.txt","sha256":"25afd51c29a08ecf3399d4d7e0854a3fb4178c849d6236b6d0a6d39678e91e21"}},"tags":["nested-reference","unchanged"],"summary":"DNS messages between clients and servers may be received over either\n UDP or TCP. UDP transport involves keeping less state on a busy\n server, but can cause truncation and retries over TCP. Additionally,\n UDP can be exploited for reflection attacks. Using TCP would reduce\n retransmits and amplification. However, clients commonly use TCP\n only for retries and servers typically use idle timeouts on the order\n of seconds.\n\n This document defines an EDNS0 option (\"edns-tcp-keepalive\") that\n allows DNS servers to signal a variable idle timeout. This\n signalling encourages the use of long-lived TCP connections by\n allowing the state associated with TCP transport to be managed\n effectively with minimal impact on the DNS transaction time.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents","scope_keywords":["7828","http","license","management","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 7828 DNS messages between clients and servers may be received over either\n UDP or TCP. UDP transport involves keeping less state on a busy\n server, but can cause truncation and retries over TCP. Additionally,\n UDP can be exploited for reflection attacks. Using TCP would reduce\n retransmits and amplification. However, clients commonly use TCP\n only for retries and servers typically use idle timeouts on the order\n of seconds.\n\n This document defines an EDNS0 option (\"edns-tcp-keepalive\") that\n allows DNS servers to signal a variable idle timeout. This\n signalling encourages the use of long-lived TCP connections by\n allowing the state associated with TCP transport to be managed\n effectively with minimal impact on the DNS transaction time.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents 7828 http license management path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7830","type":"specification","body":"IETF","designation":"RFC 7830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7830.txt","https://www.rfc-editor.org/rfc/rfc7830.pdf"],"folder":"IETF/RFC-7830","files":{"txt":{"path":"standards/IETF/RFC-7830/RFC-7830.txt","sha256":"5d8ff0e9f9d49fa55ae991a44511371eb90155eabd1576a89e59b2c68f270213"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the EDNS(0) \"Padding\" option, which allows\n DNS clients and servers to pad request and response messages by a\n variable number of octets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7830.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF ","scope_keywords":["7830","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 7830 This document specifies the EDNS(0) \"Padding\" option, which allows\n DNS clients and servers to pad request and response messages by a\n variable number of octets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7830.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF  7830 encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7873","type":"specification","body":"IETF","designation":"RFC 7873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7873.txt","https://www.rfc-editor.org/rfc/rfc7873.pdf"],"folder":"IETF/RFC-7873","files":{"txt":{"path":"standards/IETF/RFC-7873/RFC-7873.txt","sha256":"860972823ee8c0748fb5ab6d72ec14bfb802c446c2c0761965d72cd8df7a98b1"}},"tags":["nested-reference","unchanged"],"summary":"DNS Cookies are a lightweight DNS transaction security mechanism that\n provides limited protection to DNS servers and clients against a\n variety of increasingly common denial-of-service and amplification/\n forgery or cache poisoning attacks by off-path attackers. DNS\n Cookies are tolerant of NAT, NAT-PT (Network Address Translation -\n Protocol Translation), and anycast and can be incrementally deployed.\n (Since DNS Cookies are only returned to the IP address from which\n they were originally received, they cannot be used to generally track\n Internet users.)\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information","scope_keywords":["7873","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 7873 DNS Cookies are a lightweight DNS transaction security mechanism that\n provides limited protection to DNS servers and clients against a\n variety of increasingly common denial-of-service and amplification/\n forgery or cache poisoning attacks by off-path attackers. DNS\n Cookies are tolerant of NAT, NAT-PT (Network Address Translation -\n Protocol Translation), and anycast and can be incrementally deployed.\n (Since DNS Cookies are only returned to the IP address from which\n they were originally received, they cannot be used to generally track\n Internet users.)\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information 7873 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7929","type":"specification","body":"IETF","designation":"RFC 7929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7929.txt","https://www.rfc-editor.org/rfc/rfc7929.pdf"],"folder":"IETF/RFC-7929","files":{"txt":{"path":"standards/IETF/RFC-7929/RFC-7929.txt","sha256":"655a0f8b2ddf8dc29d25f497c5a1e9f10c9b8fe1057cbeb079cf35b6ab32828b"}},"tags":["nested-reference","unchanged"],"summary":"OpenPGP is a message format for email (and file) encryption that\n lacks a standardized lookup mechanism to securely obtain OpenPGP\n public keys. DNS-Based Authentication of Named Entities (DANE) is a\n method for publishing public keys in DNS. This document specifies a\n DANE method for publishing and locating OpenPGP public keys in DNS\n for a specific email address using a new OPENPGPKEY DNS resource\n record. Security is provided via Secure DNS, however the OPENPGPKEY\n record is not a replacement for verification of authenticity via the\n \"web of trust\" or manual verification. The OPENPGPKEY record can be\n used to encrypt an email that would otherwise have to be sent\n unencrypted.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Proto","scope_keywords":["7929","authentication","encryption","http","key","keys","license","presentation","revocation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7929 OpenPGP is a message format for email (and file) encryption that\n lacks a standardized lookup mechanism to securely obtain OpenPGP\n public keys. DNS-Based Authentication of Named Entities (DANE) is a\n method for publishing public keys in DNS. This document specifies a\n DANE method for publishing and locating OpenPGP public keys in DNS\n for a specific email address using a new OPENPGPKEY DNS resource\n record. Security is provided via Secure DNS, however the OPENPGPKEY\n record is not a replacement for verification of authenticity via the\n \"web of trust\" or manual verification. The OPENPGPKEY record can be\n used to encrypt an email that would otherwise have to be sent\n unencrypted.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Proto 7929 authentication encryption http key keys license presentation revocation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8145","type":"specification","body":"IETF","designation":"RFC 8145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8145.txt","https://www.rfc-editor.org/rfc/rfc8145.pdf"],"folder":"IETF/RFC-8145","files":{"txt":{"path":"standards/IETF/RFC-8145/RFC-8145.txt","sha256":"b9d4616afaa5f72bb4721fda3123dc38e22023e33aa035bb9a22dc3188329a5d"}},"tags":["nested-reference","unchanged"],"summary":"The DNS Security Extensions (DNSSEC) were developed to provide origin\n authentication and integrity protection for DNS data by using digital\n signatures. These digital signatures can be verified by building a\n chain of trust starting from a trust anchor and proceeding down to a\n particular node in the DNS. This document specifies two different\n ways for validating resolvers to signal to a server which keys are\n referenced in their chain of trust. The data from such signaling\n allow zone administrators to monitor the progress of rollovers in a\n DNSSEC-signed zone.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further info","scope_keywords":["8145","algorithm","authentication","http","key","keys","license","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 8145 The DNS Security Extensions (DNSSEC) were developed to provide origin\n authentication and integrity protection for DNS data by using digital\n signatures. These digital signatures can be verified by building a\n chain of trust starting from a trust anchor and proceeding down to a\n particular node in the DNS. This document specifies two different\n ways for validating resolvers to signal to a server which keys are\n referenced in their chain of trust. The data from such signaling\n allow zone administrators to monitor the progress of rollovers in a\n DNSSEC-signed zone.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further info 8145 algorithm authentication http key keys license signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8156","type":"specification","body":"IETF","designation":"RFC 8156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8156.txt","https://www.rfc-editor.org/rfc/rfc8156.pdf"],"folder":"IETF/RFC-8156","files":{"txt":{"path":"standards/IETF/RFC-8156/RFC-8156.txt","sha256":"70c9ac404e2c4cc37064102cbc9992d8dd562eec08bef620f3ebfb7fab3c901b"}},"tags":["nested-reference","unchanged"],"summary":"DHCPv6 as defined in \"Dynamic Host Configuration Protocol for IPv6\n (DHCPv6)\" (RFC 3315) does not offer server redundancy. This document\n defines a protocol implementation to provide DHCPv6 failover, a\n mechanism for running two servers with the capability for either\n server to take over clients' leases in case of server failure or\n network partition. It meets the requirements for DHCPv6 failover\n detailed in \"DHCPv6 Failover Requirements\" (RFC 7031).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of th","scope_keywords":["8156","algorithm","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 8156 DHCPv6 as defined in \"Dynamic Host Configuration Protocol for IPv6\n (DHCPv6)\" (RFC 3315) does not offer server redundancy. This document\n defines a protocol implementation to provide DHCPv6 failover, a\n mechanism for running two servers with the capability for either\n server to take over clients' leases in case of server failure or\n network partition. It meets the requirements for DHCPv6 failover\n detailed in \"DHCPv6 Failover Requirements\" (RFC 7031).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of th 8156 algorithm http identification license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8427","type":"specification","body":"IETF","designation":"RFC 8427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8427.txt","https://www.rfc-editor.org/rfc/rfc8427.pdf"],"folder":"IETF/RFC-8427","files":{"txt":{"path":"standards/IETF/RFC-8427/RFC-8427.txt","sha256":"e23463533f3232d6821b971b31ea9f6c62eb9a4fe604010383d92d3307e54eab"}},"tags":["nested-reference","unchanged"],"summary":"Some applications use DNS messages, or parts of DNS messages, as\n data. For example, a system that captures DNS queries and responses\n might want to be able to easily search them without having to decode\n the messages each time. Another example is a system that puts\n together DNS queries and responses from message parts. This document\n describes a general format for DNS message data in JSON. Specific\n profiles of the format in this document can be described in other\n documents for specific applications and usage scenarios.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Grou","scope_keywords":["8427","http","https","license","policy","presentation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null}],"search_text":"IETF RFC 8427 Some applications use DNS messages, or parts of DNS messages, as\n data. For example, a system that captures DNS queries and responses\n might want to be able to easily search them without having to decode\n the messages each time. Another example is a system that puts\n together DNS queries and responses from message parts. This document\n describes a general format for DNS message data in JSON. Specific\n profiles of the format in this document can be described in other\n documents for specific applications and usage scenarios.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Grou 8427 http https license policy presentation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8484","type":"specification","body":"IETF","designation":"RFC 8484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8484.txt","https://www.rfc-editor.org/rfc/rfc8484.pdf"],"folder":"IETF/RFC-8484","files":{"txt":{"path":"standards/IETF/RFC-8484/RFC-8484.txt","sha256":"c2cb41fb72bf45935ba7372fef9d83478ed2ecc7f3749ea9a16b52b06ef0f343"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a protocol for sending DNS queries and getting\n DNS responses over HTTPS. Each DNS query-response pair is mapped\n into an HTTP exchange.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8484.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Tr","scope_keywords":["8484","authentication","http","https","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 8484 This document defines a protocol for sending DNS queries and getting\n DNS responses over HTTPS. Each DNS query-response pair is mapped\n into an HTTP exchange.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8484.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Tr 8484 authentication http https key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8806","type":"specification","body":"IETF","designation":"RFC 8806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8806.txt","https://www.rfc-editor.org/rfc/rfc8806.pdf"],"folder":"IETF/RFC-8806","files":{"pdf":{"path":"standards/IETF/RFC-8806/RFC-8806.pdf","sha256":"3cb01a3d01286223ea5bd9a218ab522897abb640960ba490e2f0a53b88ed272e"},"txt":{"path":"standards/IETF/RFC-8806/RFC-8806.txt","sha256":"c9eaa51045e2cca3ed53b15ea8a3faf3dccd27c7fd3f555f0f7e76736c5fa3dc"}},"tags":["nested-reference","unchanged"],"summary":"Some DNS recursive resolvers have longer-than-desired round-trip\n times to the closest DNS root server; those resolvers may have\n difficulty getting responses from the root servers, such as during a\n network attack. Some DNS recursive resolver operators want to\n prevent snooping by third parties of requests sent to DNS root\n servers. In both cases, resolvers can greatly decrease the round-\n trip time and prevent observation of requests by serving a copy of\n the full root zone on the same server, such as on a loopback address\n or in the resolver software. This document shows how to start and\n maintain such a copy of the root zone that does not cause problems\n for other users of the DNS, at the cost of adding some operational\n fragility for the operator.\n\n This document obsoletes RFC 7706.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publish","scope_keywords":["8806","http","https","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 8806 Some DNS recursive resolvers have longer-than-desired round-trip\n times to the closest DNS root server; those resolvers may have\n difficulty getting responses from the root servers, such as during a\n network attack. Some DNS recursive resolver operators want to\n prevent snooping by third parties of requests sent to DNS root\n servers. In both cases, resolvers can greatly decrease the round-\n trip time and prevent observation of requests by serving a copy of\n the full root zone on the same server, such as on a loopback address\n or in the resolver software. This document shows how to start and\n maintain such a copy of the root zone that does not cause problems\n for other users of the DNS, at the cost of adding some operational\n fragility for the operator.\n\n This document obsoletes RFC 7706.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publish 8806 http https license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 1036","type":"specification","body":"IETF","designation":"RFC 1036","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1036.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1036.txt","https://www.rfc-editor.org/rfc/rfc1036.pdf"],"folder":"IETF/RFC-1036","files":{"txt":{"path":"standards/IETF/RFC-1036/RFC-1036.txt","sha256":"712c774b227d9f7d1f9fe8a49e7af58efdc77a68fbd5b9ecd51c574de933d3f6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Horton\nRequest for Comments: 1036 AT&T Bell Laboratories\nObsoletes: RFC-850 R. Adams\n Center for Seismic Studies\n December 1987\n\n Standard for Interchange of USENET Messages\n\nSTATUS OF THIS MEMO\n\n This document defines the standard format for the interchange of\n network News messages among USENET hosts. It updates and replaces\n RFC-850, reflecting version B2.11 of the News program. This memo is\n disributed as an RFC to make this information easily accessible to\n the Internet community. It does not specify an Internet standard.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n This document defines the standard format for the interchange of\n network News messages among USENET hosts. It describes the format\n for messages themselves and gives partial standards for transmission\n of news. The news transmission is not entirely in order to give a\n good deal of","scope_keywords":["1036","algorithm","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1630","folder":"IETF/RFC-1630","source":"IETF/RFC-1630/RFC-1630.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2980","folder":"IETF/RFC-2980","source":"IETF/RFC-2980/RFC-2980.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null}],"search_text":"IETF RFC 1036 Network Working Group M. Horton\nRequest for Comments: 1036 AT&T Bell Laboratories\nObsoletes: RFC-850 R. Adams\n Center for Seismic Studies\n December 1987\n\n Standard for Interchange of USENET Messages\n\nSTATUS OF THIS MEMO\n\n This document defines the standard format for the interchange of\n network News messages among USENET hosts. It updates and replaces\n RFC-850, reflecting version B2.11 of the News program. This memo is\n disributed as an RFC to make this information easily accessible to\n the Internet community. It does not specify an Internet standard.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n This document defines the standard format for the interchange of\n network News messages among USENET hosts. It describes the format\n for messages themselves and gives partial standards for transmission\n of news. The news transmission is not entirely in order to give a\n good deal of 1036 algorithm key path subject nested-reference unchanged"},{"id":"IETF RFC 1468","type":"specification","body":"IETF","designation":"RFC 1468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1468.txt","https://www.rfc-editor.org/rfc/rfc1468.pdf"],"folder":"IETF/RFC-1468","files":{"txt":{"path":"standards/IETF/RFC-1468/RFC-1468.txt","sha256":"0bc3bd35f8c99964d7c0e2dbe3b3a19152d6a7990c2956f52d17b3ee79bfb38a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Murai\nRequest for Comments: 1468 Keio University\n M. Crispin\n Panda Programming\n E. van der Poel\n June 1993\n\n Japanese Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This document describes the encoding used in electronic mail [RFC822]\n and network news [RFC1036] messages in several Japanese networks. It\n was first specified by and used in JUNET [JUNET]. The encoding is now\n also widely used in Japanese IP communities.\n\n The name given to this encoding is \"ISO-2022-JP\", which is intended\n to be used in the \"charset\" parameter field of MIME headers (see\n [MIME1] and [MIME2]).\n\nDescription\n\n The text starts in ASCII [ASCII], and switches to Japanese characters\n through an escape sequence. For","scope_keywords":["1468","crl","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"IETF RFC 1468 Network Working Group J. Murai\nRequest for Comments: 1468 Keio University\n M. Crispin\n Panda Programming\n E. van der Poel\n June 1993\n\n Japanese Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This document describes the encoding used in electronic mail [RFC822]\n and network news [RFC1036] messages in several Japanese networks. It\n was first specified by and used in JUNET [JUNET]. The encoding is now\n also widely used in Japanese IP communities.\n\n The name given to this encoding is \"ISO-2022-JP\", which is intended\n to be used in the \"charset\" parameter field of MIME headers (see\n [MIME1] and [MIME2]).\n\nDescription\n\n The text starts in ASCII [ASCII], and switches to Japanese characters\n through an escape sequence. For 1468 crl registered risk nested-reference unchanged"},{"id":"IETF RFC 1554","type":"specification","body":"IETF","designation":"RFC 1554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1554.txt","https://www.rfc-editor.org/rfc/rfc1554.pdf"],"folder":"IETF/RFC-1554","files":{"txt":{"path":"standards/IETF/RFC-1554/RFC-1554.txt","sha256":"72264d4d6a8b9b708eb2045986cb92653cd3e5e5cbbe1cd59f98ca8eb6fdf8d0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Ohta\nRequest for Comments: 1554 Tokyo Institute of Technology\nCategory: Informational K. Handa\n ETL\n December 1993\n\n ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This memo describes a text encoding scheme: \"ISO-2022-JP-2\", which is\n used experimentally for electronic mail [RFC822] and network news\n [RFC1036] messages in several Japanese networks. The encoding is a\n multilingual extension of \"ISO-2022-JP\", the existing encoding for\n Japanese [2022JP]. The encoding is supported by an Emacs based\n multilingual text editor: MULE [MULE].\n\n The name, \"ISO-2022-JP-2\", is intended to be used in the \"charset\"\n parameter field of MIME headers (see [MIME1] and [MIME2])","scope_keywords":["1554","crl","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1554 Network Working Group M. Ohta\nRequest for Comments: 1554 Tokyo Institute of Technology\nCategory: Informational K. Handa\n ETL\n December 1993\n\n ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This memo describes a text encoding scheme: \"ISO-2022-JP-2\", which is\n used experimentally for electronic mail [RFC822] and network news\n [RFC1036] messages in several Japanese networks. The encoding is a\n multilingual extension of \"ISO-2022-JP\", the existing encoding for\n Japanese [2022JP]. The encoding is supported by an Emacs based\n multilingual text editor: MULE [MULE].\n\n The name, \"ISO-2022-JP-2\", is intended to be used in the \"charset\"\n parameter field of MIME headers (see [MIME1] and [MIME2]) 1554 crl risk nested-reference unchanged"},{"id":"IETF RFC 1580","type":"specification","body":"IETF","designation":"RFC 1580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1580.txt","https://www.rfc-editor.org/rfc/rfc1580.pdf"],"folder":"IETF/RFC-1580","files":{"txt":{"path":"standards/IETF/RFC-1580/RFC-1580.txt","sha256":"6947af1c70c4ecdfdece41d3ac05ac02417ec647e9ec20236320847833d21593"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group EARN Staff\nRequest for Comments: 1580 EARN Association\nFYI: 23 March 1994\nCategory: Informational\n\n Guide to Network Resource Tools\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 2. GOPHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5\n 2.1. What is Gopher . . . . . . . . . . . . . . . . . . . . . . 5\n 2.2. Who can use Gopher . . . . . . . . . . . . . . . . . . . . 6\n 2.3. How to get to Gopher . . . . . . . . . . . . . . . . . . . 6\n 2.3.1. Local clients . . . . . . . . . . . . . . . . . . . . . 6\n 2.3.2. Remote clients . . . . . . . . . . . . . . . . . . . . . 6\n 2.4. Using Gopher . . . . . . . . . . . . . . . . . . . . . . . 7\n 2","scope_keywords":["1580"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null}],"search_text":"IETF RFC 1580 Network Working Group EARN Staff\nRequest for Comments: 1580 EARN Association\nFYI: 23 March 1994\nCategory: Informational\n\n Guide to Network Resource Tools\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 2. GOPHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5\n 2.1. What is Gopher . . . . . . . . . . . . . . . . . . . . . . 5\n 2.2. Who can use Gopher . . . . . . . . . . . . . . . . . . . . 6\n 2.3. How to get to Gopher . . . . . . . . . . . . . . . . . . . 6\n 2.3.1. Local clients . . . . . . . . . . . . . . . . . . . . . 6\n 2.3.2. Remote clients . . . . . . . . . . . . . . . . . . . . . 6\n 2.4. Using Gopher . . . . . . . . . . . . . . . . . . . . . . . 7\n 2 1580 nested-reference unchanged"},{"id":"IETF RFC 1842","type":"specification","body":"IETF","designation":"RFC 1842","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1842.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1842.txt","https://www.rfc-editor.org/rfc/rfc1842.pdf"],"folder":"IETF/RFC-1842","files":{"txt":{"path":"standards/IETF/RFC-1842/RFC-1842.txt","sha256":"31abc4dcc14e481ababea5b7523295874c1a1b32c386dc200fef9f415bd4b93d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the encoding used in electronic mail [RFC822]\n and network news [RFC1036] messages over the Internet. The 7-bit\n representation of GB 2312 Chinese text was specified by Fung Fung Lee\n of Stanford University [Lee89] and implemented in various software\n packages under different platforms (see appendix for a partial list\n of the available software packages that support this encoding\n method). It is further tested and used in the usenet newsgroups\n alt.chinese.text and chinese.* as well as various other network\n forums with considerable success. Future extensions of this encoding\n method can accommodate additional GB character sets and other east\n asian language character sets [Wei94].\n\n The name given to this encoding is \"HZ-GB-2312\", which is intended to\n be used in the \"charset\" parameter field of MIME headers (see [MIME1]\n and [MIME2]).\n\nWei, et al Informational [","scope_keywords":["1842","crl","delivery","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1842 This document describes the encoding used in electronic mail [RFC822]\n and network news [RFC1036] messages over the Internet. The 7-bit\n representation of GB 2312 Chinese text was specified by Fung Fung Lee\n of Stanford University [Lee89] and implemented in various software\n packages under different platforms (see appendix for a partial list\n of the available software packages that support this encoding\n method). It is further tested and used in the usenet newsgroups\n alt.chinese.text and chinese.* as well as various other network\n forums with considerable success. Future extensions of this encoding\n method can accommodate additional GB character sets and other east\n asian language character sets [Wei94].\n\n The name given to this encoding is \"HZ-GB-2312\", which is intended to\n be used in the \"charset\" parameter field of MIME headers (see [MIME1]\n and [MIME2]).\n\nWei, et al Informational [ 1842 crl delivery presentation risk nested-reference unchanged"},{"id":"IETF RFC 1922","type":"specification","body":"IETF","designation":"RFC 1922","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1922.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1922.txt","https://www.rfc-editor.org/rfc/rfc1922.pdf"],"folder":"IETF/RFC-1922","files":{"txt":{"path":"standards/IETF/RFC-1922/RFC-1922.txt","sha256":"91a479722f8f929067d6a45e2674e507b43bb030e3951889164126f57367ebfe"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes methods of transporting Chinese characters in\n Internet services which transport text, such as electronic mail\n [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World\n Wide Web [RFC-1866].","scope_keywords":["1922","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1922 This memo describes methods of transporting Chinese characters in\n Internet services which transport text, such as electronic mail\n [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World\n Wide Web [RFC-1866]. 1922 crl nested-reference unchanged"},{"id":"IETF RFC 1945","type":"specification","body":"IETF","designation":"RFC 1945","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1945.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1945.txt","https://www.rfc-editor.org/rfc/rfc1945.pdf"],"folder":"IETF/RFC-1945","files":{"txt":{"path":"standards/IETF/RFC-1945/RFC-1945.txt","sha256":"a853054a35d956b2885698566b376505406c756c3b318c6bef04dbd900a27fce"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol with the lightness and speed necessary for distributed,\n collaborative, hypermedia information systems. It is a generic,\n stateless, object-oriented protocol which can be used for many tasks,\n such as name servers and distributed object management systems,\n through extension of its request methods (commands). A feature of\n HTTP is the typing of data representation, allowing systems to be\n built independently of the data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification reflects common usage of\n the protocol referred to as \"HTTP/1.0\".","scope_keywords":["1945","authentication","authorization","http","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2069","folder":"IETF/RFC-2069","source":"IETF/RFC-2069/RFC-2069.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2084","folder":"IETF/RFC-2084","source":"IETF/RFC-2084/RFC-2084.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2145","folder":"IETF/RFC-2145","source":"IETF/RFC-2145/RFC-2145.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2169","folder":"IETF/RFC-2169","source":"IETF/RFC-2169/RFC-2169.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 1945 The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol with the lightness and speed necessary for distributed,\n collaborative, hypermedia information systems. It is a generic,\n stateless, object-oriented protocol which can be used for many tasks,\n such as name servers and distributed object management systems,\n through extension of its request methods (commands). A feature of\n HTTP is the typing of data representation, allowing systems to be\n built independently of the data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification reflects common usage of\n the protocol referred to as \"HTTP/1.0\". 1945 authentication authorization http management path presentation nested-reference unchanged"},{"id":"IETF RFC 2068","type":"specification","body":"IETF","designation":"RFC 2068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2068.txt","https://www.rfc-editor.org/rfc/rfc2068.pdf"],"folder":"IETF/RFC-2068","files":{"txt":{"path":"standards/IETF/RFC-2068/RFC-2068.txt","sha256":"d6c4e471389f2d309ab1f90881576542c742f95b115336a346447d052e0477cf"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol for distributed, collaborative, hypermedia information\n systems. It is a generic, stateless, object-oriented protocol which\n can be used for many tasks, such as name servers and distributed\n object management systems, through extension of its request methods.\n A feature of HTTP is the typing and negotiation of data\n representation, allowing systems to be built independently of the\n data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification defines the protocol\n referred to as \"HTTP/1.1\".","scope_keywords":["2068","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2069","folder":"IETF/RFC-2069","source":"IETF/RFC-2069/RFC-2069.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2109","folder":"IETF/RFC-2109","source":"IETF/RFC-2109/RFC-2109.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2145","folder":"IETF/RFC-2145","source":"IETF/RFC-2145/RFC-2145.txt","version":null},{"body":"IETF","designation":"RFC 2169","folder":"IETF/RFC-2169","source":"IETF/RFC-2169/RFC-2169.txt","version":null},{"body":"IETF","designation":"RFC 2186","folder":"IETF/RFC-2186","source":"IETF/RFC-2186/RFC-2186.txt","version":null},{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2194","folder":"IETF/RFC-2194","source":"IETF/RFC-2194/RFC-2194.txt","version":null},{"body":"IETF","designation":"RFC 2227","folder":"IETF/RFC-2227","source":"IETF/RFC-2227/RFC-2227.txt","version":null},{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 2296","folder":"IETF/RFC-2296","source":"IETF/RFC-2296/RFC-2296.txt","version":null},{"body":"IETF","designation":"RFC 2310","folder":"IETF/RFC-2310","source":"IETF/RFC-2310/RFC-2310.txt","version":null},{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2371","folder":"IETF/RFC-2371","source":"IETF/RFC-2371/RFC-2371.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2585","folder":"IETF/RFC-2585","source":"IETF/RFC-2585/RFC-2585.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 2068 The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol for distributed, collaborative, hypermedia information\n systems. It is a generic, stateless, object-oriented protocol which\n can be used for many tasks, such as name servers and distributed\n object management systems, through extension of its request methods.\n A feature of HTTP is the typing and negotiation of data\n representation, allowing systems to be built independently of the\n data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification defines the protocol\n referred to as \"HTTP/1.1\". 2068 http management presentation nested-reference unchanged"},{"id":"IETF RFC 2076","type":"specification","body":"IETF","designation":"RFC 2076","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2076.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2076.txt","https://www.rfc-editor.org/rfc/rfc2076.pdf"],"folder":"IETF/RFC-2076","files":{"txt":{"path":"standards/IETF/RFC-2076/RFC-2076.txt","sha256":"f089d8b57edc1d33af3d1e9be5ac846c667bafab2b28127f3a3032ae89461416"}},"tags":["nested-reference","unchanged"],"summary":"This memo contains a table of commonly occurring headers in headings\n of e-mail messages. The document compiles information from other RFCs\n such as RFC 822, RFC 1036, RFC 1123, RFC 1327, RFC 1496, RFC 1521,\n RFC 1766, RFC 1806, RFC 1864 and RFC 1911. A few commonly occurring\n headers which are not defined in RFCs are also included. For each\n header, the memo gives a short description and a reference to the RFC\n in which the header is defined.","scope_keywords":["2076","attribute","attributes","http","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null}],"search_text":"IETF RFC 2076 This memo contains a table of commonly occurring headers in headings\n of e-mail messages. The document compiles information from other RFCs\n such as RFC 822, RFC 1036, RFC 1123, RFC 1327, RFC 1496, RFC 1521,\n RFC 1766, RFC 1806, RFC 1864 and RFC 1911. A few commonly occurring\n headers which are not defined in RFCs are also included. For each\n header, the memo gives a short description and a reference to the RFC\n in which the header is defined. 2076 attribute attributes http identification nested-reference unchanged"},{"id":"IETF RFC 2110","type":"specification","body":"IETF","designation":"RFC 2110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2110.txt","https://www.rfc-editor.org/rfc/rfc2110.pdf"],"folder":"IETF/RFC-2110","files":{"txt":{"path":"standards/IETF/RFC-2110/RFC-2110.txt","sha256":"ff9b3d260a1f0f88570ba22edb973f91ffdbe4b592c8523e7a03aa2ef678024d"}},"tags":["nested-reference","unchanged"],"summary":"Although HTML [RFC 1866] was designed within the context of MIME,\n more than the specification of HTML as defined in RFC 1866 is needed\n for two electronic mail user agents to be able to interoperate using\n HTML as a document format. These issues include the naming of objects\n that are normally referred to by URIs, and the means of aggregating\n objects that go together. This document describes a set of guidelines\n that will allow conforming mail user agents to be able to send,\n deliver and display these objects, such as HTML objects, that can\n contain links represented by URIs. In order to be able to handle\n inter-linked objects, the document uses the MIME type\n multipart/related and specifies the MIME content-headers \"Content-\n Location\" and \"Content-Base\".","scope_keywords":["2110","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 2110 Although HTML [RFC 1866] was designed within the context of MIME,\n more than the specification of HTML as defined in RFC 1866 is needed\n for two electronic mail user agents to be able to interoperate using\n HTML as a document format. These issues include the naming of objects\n that are normally referred to by URIs, and the means of aggregating\n objects that go together. This document describes a set of guidelines\n that will allow conforming mail user agents to be able to send,\n deliver and display these objects, such as HTML objects, that can\n contain links represented by URIs. In order to be able to handle\n inter-linked objects, the document uses the MIME type\n multipart/related and specifies the MIME content-headers \"Content-\n Location\" and \"Content-Base\". 2110 http nested-reference unchanged"},{"id":"IETF RFC 2557","type":"specification","body":"IETF","designation":"RFC 2557","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2557.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2557.txt","https://www.rfc-editor.org/rfc/rfc2557.pdf"],"folder":"IETF/RFC-2557","files":{"txt":{"path":"standards/IETF/RFC-2557/RFC-2557.txt","sha256":"65b31b58aa2f5e2bab15745d8e0330031a20382a90f097fe0b392bcd9b8cd6c9"}},"tags":["nested-reference","unchanged"],"summary":"HTML [RFC 1866] defines a powerful means of specifying multimedia\n documents. These multimedia documents consist of a text/html root\n resource (object) and other subsidiary resources (image, video clip,\n applet, etc. objects) referenced by Uniform Resource Identifiers\n (URIs) within the text/html root resource. When an HTML multimedia\n document is retrieved by a browser, each of these component resources\n is individually retrieved in real time from a location, and using a\n protocol, specified by each URI.\n\n In order to transfer a complete HTML multimedia document in a single\n e-mail message, it is necessary to: a) aggregate a text/html root\n resource and all of the subsidiary resources it references into a\n single composite message structure, and b) define a means by which\n URIs in the text/html root can reference subsidiary resources within\n that composite message structure.\n\n This docu","scope_keywords":["2557","archiving","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 2557 HTML [RFC 1866] defines a powerful means of specifying multimedia\n documents. These multimedia documents consist of a text/html root\n resource (object) and other subsidiary resources (image, video clip,\n applet, etc. objects) referenced by Uniform Resource Identifiers\n (URIs) within the text/html root resource. When an HTML multimedia\n document is retrieved by a browser, each of these component resources\n is individually retrieved in real time from a location, and using a\n protocol, specified by each URI.\n\n In order to transfer a complete HTML multimedia document in a single\n e-mail message, it is necessary to: a) aggregate a text/html root\n resource and all of the subsidiary resources it references into a\n single composite message structure, and b) define a means by which\n URIs in the text/html root can reference subsidiary resources within\n that composite message structure.\n\n This docu 2557 archiving http presentation nested-reference unchanged"},{"id":"IETF RFC 2616","type":"specification","body":"IETF","designation":"RFC 2616","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2616.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2616.txt","https://www.rfc-editor.org/rfc/rfc2616.pdf"],"folder":"IETF/RFC-2616","files":{"pdf":{"path":"standards/IETF/RFC-2616/RFC-2616.pdf","sha256":"4b992042e3a18f1bb8cebbd0916c66b89b4ab179d75d552a85f48f83a222e631"},"txt":{"path":"standards/IETF/RFC-2616/RFC-2616.txt","sha256":"10211d2885196b97b1c78e1672f3f68ae97c294596ef2b7fd890cbd30a3427bf"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol for distributed, collaborative, hypermedia information\n systems. It is a generic, stateless, protocol which can be used for\n many tasks beyond its use for hypertext, such as name servers and\n distributed object management systems, through extension of its\n request methods, error codes and headers [47]. A feature of HTTP is\n the typing and negotiation of data representation, allowing systems\n to be built independently of the data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification defines the protocol\n referred to as \"HTTP/1.1\", and is an update to RFC 2068 [33].\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 2616 HTTP/1.1 June 1999","scope_keywords":["2616","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2756","folder":"IETF/RFC-2756","source":"IETF/RFC-2756/RFC-2756.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2965","folder":"IETF/RFC-2965","source":"IETF/RFC-2965/RFC-2965.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3143","folder":"IETF/RFC-3143","source":"IETF/RFC-3143/RFC-3143.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3466","folder":"IETF/RFC-3466","source":"IETF/RFC-3466/RFC-3466.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4437","folder":"IETF/RFC-4437","source":"IETF/RFC-4437/RFC-4437.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4758","folder":"IETF/RFC-4758","source":"IETF/RFC-4758/RFC-4758.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4850","folder":"IETF/RFC-4850","source":"IETF/RFC-4850/RFC-4850.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5397","folder":"IETF/RFC-5397","source":"IETF/RFC-5397/RFC-5397.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5861","folder":"IETF/RFC-5861","source":"IETF/RFC-5861/RFC-5861.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6585","folder":"IETF/RFC-6585","source":"IETF/RFC-6585/RFC-6585.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null}],"search_text":"IETF RFC 2616 The Hypertext Transfer Protocol (HTTP) is an application-level\n protocol for distributed, collaborative, hypermedia information\n systems. It is a generic, stateless, protocol which can be used for\n many tasks beyond its use for hypertext, such as name servers and\n distributed object management systems, through extension of its\n request methods, error codes and headers [47]. A feature of HTTP is\n the typing and negotiation of data representation, allowing systems\n to be built independently of the data being transferred.\n\n HTTP has been in use by the World-Wide Web global information\n initiative since 1990. This specification defines the protocol\n referred to as \"HTTP/1.1\", and is an update to RFC 2068 [33].\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 2616 HTTP/1.1 June 1999 2616 http management presentation nested-reference unchanged"},{"id":"IETF RFC 2924","type":"specification","body":"IETF","designation":"RFC 2924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2924.txt","https://www.rfc-editor.org/rfc/rfc2924.pdf"],"folder":"IETF/RFC-2924","files":{"txt":{"path":"standards/IETF/RFC-2924/RFC-2924.txt","sha256":"61e8682872d4432b7f479f4fac336cb6d8465a8acbb8257cf19e7e41895186bf"}},"tags":["nested-reference","unchanged"],"summary":"This document summarises Internet Engineering Task Force (IETF) and\n International Telecommunication Union (ITU-T) documents related to\n Accounting. A classification scheme for the Accounting Attributes in\n the summarised documents is presented. Exchange formats for\n Accounting data records are discussed, as are advantages and\n disadvantages of integrated versus separate record formats and\n transport protocols. This document discusses service definition\n independence, extensibility, and versioning. Compound service\n definition capabilities are described.","scope_keywords":["2924","attribute","attributes","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null}],"search_text":"IETF RFC 2924 This document summarises Internet Engineering Task Force (IETF) and\n International Telecommunication Union (ITU-T) documents related to\n Accounting. A classification scheme for the Accounting Attributes in\n the summarised documents is presented. Exchange formats for\n Accounting data records are discussed, as are advantages and\n disadvantages of integrated versus separate record formats and\n transport protocols. This document discusses service definition\n independence, extensibility, and versioning. Compound service\n definition capabilities are described. 2924 attribute attributes identification management presentation nested-reference unchanged"},{"id":"IETF RFC 2980","type":"specification","body":"IETF","designation":"RFC 2980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2980.txt","https://www.rfc-editor.org/rfc/rfc2980.pdf"],"folder":"IETF/RFC-2980","files":{"txt":{"path":"standards/IETF/RFC-2980/RFC-2980.txt","sha256":"a08a7c72ba79053a53aee51dbdeb4d31a38342418d287f08e20acb2238c13600"}},"tags":["nested-reference","unchanged"],"summary":"In this document, a number of popular extensions to the Network News\n Transfer Protocol (NNTP) protocol defined in RFC 977 are documented\n and discussed. While this document is not intended to serve as a\n standard of any kind, it will hopefully serve as a reference document\n for future implementers of the NNTP protocol. In the role, this\n document would hopefully create the possibility for some level of\n interoperability among implementations that make use of extensions.","scope_keywords":["2980","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4644","folder":"IETF/RFC-4644","source":"IETF/RFC-4644/RFC-4644.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null}],"search_text":"IETF RFC 2980 In this document, a number of popular extensions to the Network News\n Transfer Protocol (NNTP) protocol defined in RFC 977 are documented\n and discussed. While this document is not intended to serve as a\n standard of any kind, it will hopefully serve as a reference document\n for future implementers of the NNTP protocol. In the role, this\n document would hopefully create the possibility for some level of\n interoperability among implementations that make use of extensions. 2980 authentication nested-reference unchanged"},{"id":"IETF RFC 3864","type":"specification","body":"IETF","designation":"RFC 3864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3864.txt","https://www.rfc-editor.org/rfc/rfc3864.pdf"],"folder":"IETF/RFC-3864","files":{"txt":{"path":"standards/IETF/RFC-3864/RFC-3864.txt","sha256":"eccd2d25dc110a55aff23ddc41a9b4e4aa105f567b2806546eeae3a7bd72764d"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines registration procedures for the message\n header fields used by Internet mail, HTTP, Netnews and other\n applications.\n\nKlyne, et al. Best Current Practice [Page 1]\n\f\nRFC 3864 Header Field Registration September 2004","scope_keywords":["3864","http","key","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 3864 This specification defines registration procedures for the message\n header fields used by Internet mail, HTTP, Netnews and other\n applications.\n\nKlyne, et al. Best Current Practice [Page 1]\n\f\nRFC 3864 Header Field Registration September 2004 3864 http key policy subject nested-reference unchanged"},{"id":"IETF RFC 3977","type":"specification","body":"IETF","designation":"RFC 3977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3977.txt","https://www.rfc-editor.org/rfc/rfc3977.pdf"],"folder":"IETF/RFC-3977","files":{"txt":{"path":"standards/IETF/RFC-3977/RFC-3977.txt","sha256":"e9bafe47d8c9b1136f11546162599ee67c233f33955c2972b57a91ecaff1f5f5"}},"tags":["nested-reference","unchanged"],"summary":"The Network News Transfer Protocol (NNTP) has been in use in the\n Internet for a decade, and remains one of the most popular protocols\n (by volume) in use today. This document is a replacement for\n RFC 977, and officially updates the protocol specification. It\n clarifies some vagueness in RFC 977, includes some new base\n functionality, and provides a specific mechanism to add standardized\n extensions to NNTP.","scope_keywords":["3977","authentication","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4644","folder":"IETF/RFC-4644","source":"IETF/RFC-4644/RFC-4644.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 3977 The Network News Transfer Protocol (NNTP) has been in use in the\n Internet for a decade, and remains one of the most popular protocols\n (by volume) in use today. This document is a replacement for\n RFC 977, and officially updates the protocol specification. It\n clarifies some vagueness in RFC 977, includes some new base\n functionality, and provides a specific mechanism to add standardized\n extensions to NNTP. 3977 authentication key validation nested-reference unchanged"},{"id":"IETF RFC 5064","type":"specification","body":"IETF","designation":"RFC 5064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5064.txt","https://www.rfc-editor.org/rfc/rfc5064.pdf"],"folder":"IETF/RFC-5064","files":{"txt":{"path":"standards/IETF/RFC-5064/RFC-5064.txt","sha256":"abd8facfa39761b3d4c75b313ffd6e3d524d7d1710ba22f4a7ff6d96224a8dd2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new email header field, Archived-At:, to provide\n a direct link to the archived form of an individual email message.","scope_keywords":["5064","crl","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null}],"search_text":"IETF RFC 5064 This memo defines a new email header field, Archived-At:, to provide\n a direct link to the archived form of an individual email message. 5064 crl key subject nested-reference unchanged"},{"id":"IETF RFC 5537","type":"specification","body":"IETF","designation":"RFC 5537","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5537.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5537.txt","https://www.rfc-editor.org/rfc/rfc5537.pdf"],"folder":"IETF/RFC-5537","files":{"txt":{"path":"standards/IETF/RFC-5537/RFC-5537.txt","sha256":"d729e7a4e84006d1ada9945e7fa011e3c8f6600700217b7b3230e8d78116683b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the architecture of Netnews systems and\n specifies the correct manipulation and interpretation of Netnews\n articles by software that originates, distributes, stores, and\n displays them. It also specifies the requirements that must be met\n by any protocol used to transport and serve Netnews articles.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IE","scope_keywords":["5537","algorithm","authentication","authorization","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 5537 This document defines the architecture of Netnews systems and\n specifies the correct manipulation and interpretation of Netnews\n articles by software that originates, distributes, stores, and\n displays them. It also specifies the requirements that must be met\n by any protocol used to transport and serve Netnews articles.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IE 5537 algorithm authentication authorization http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 1037","type":"specification","body":"IETF","designation":"RFC 1037","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1037.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1037.txt","https://www.rfc-editor.org/rfc/rfc1037.pdf"],"folder":"IETF/RFC-1037","files":{"txt":{"path":"standards/IETF/RFC-1037/RFC-1037.txt","sha256":"d45ef98e09937015c10f70033011702407b4d12cd7c19c74fe53a129442688a7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Greenberg\nRequest for Comments: 1037 S. Keene\n December 1987\n\n NFILE - A File Access Protocol\n\nSTATUS OF THIS MEMO\n\n This document includes a specification of the NFILE file access\n protocol and its underlying levels of protocol, the Token List\n Transport Layer and Byte Stream with Mark. The goal of this\n specification is to promote discussion of the ideas described here,\n and to encourage designers of future file protocols to take advantage\n of these ideas. A secondary goal is to make the specification\n available to sites that might benefit from implementing NFILE. The\n distribution of this document is unlimited.\n\n TABLE OF CONTENTS\n Page\n 1. INTRODUCTION 3\n\n 2. NFILE PROTOCOL LAYERING 4\n\n 3. OVERVIEW OF AN NFILE SESSION 5\n\n 4. NFILE CONTROL AND DATA CONNECTIONS 6\n\n 5. NFILE FILE OPENING MODES 7\n\n 6. NFILE CHARACTER SET 9\n\n 7. CONVENTIONS USED IN THIS DOCUMENT 1","scope_keywords":["1037","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 3092","folder":"IETF/RFC-3092","source":"IETF/RFC-3092/RFC-3092.txt","version":null}],"search_text":"IETF RFC 1037 Network Working Group B. Greenberg\nRequest for Comments: 1037 S. Keene\n December 1987\n\n NFILE - A File Access Protocol\n\nSTATUS OF THIS MEMO\n\n This document includes a specification of the NFILE file access\n protocol and its underlying levels of protocol, the Token List\n Transport Layer and Byte Stream with Mark. The goal of this\n specification is to promote discussion of the ideas described here,\n and to encourage designers of future file protocols to take advantage\n of these ideas. A secondary goal is to make the specification\n available to sites that might benefit from implementing NFILE. The\n distribution of this document is unlimited.\n\n TABLE OF CONTENTS\n Page\n 1. INTRODUCTION 3\n\n 2. NFILE PROTOCOL LAYERING 4\n\n 3. OVERVIEW OF AN NFILE SESSION 5\n\n 4. NFILE CONTROL AND DATA CONNECTIONS 6\n\n 5. NFILE FILE OPENING MODES 7\n\n 6. NFILE CHARACTER SET 9\n\n 7. CONVENTIONS USED IN THIS DOCUMENT 1 1037 key path presentation nested-reference unchanged"},{"id":"IETF RFC 3092","type":"specification","body":"IETF","designation":"RFC 3092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3092.txt","https://www.rfc-editor.org/rfc/rfc3092.pdf"],"folder":"IETF/RFC-3092","files":{"txt":{"path":"standards/IETF/RFC-3092/RFC-3092.txt","sha256":"fa8d5320dec1c321b7cf0c9a7cd538a5888a043b72944a37f2caa520373ef826"}},"tags":["nested-reference","unchanged"],"summary":"Approximately 212 RFCs so far, starting with RFC 269, contain the\n terms `foo', `bar', or `foobar' as metasyntactic variables without\n any proper explanation or definition. This document rectifies that\n deficiency.","scope_keywords":["3092","key","license","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 3092 Approximately 212 RFCs so far, starting with RFC 269, contain the\n terms `foo', `bar', or `foobar' as metasyntactic variables without\n any proper explanation or definition. This document rectifies that\n deficiency. 3092 key license pid subject nested-reference unchanged"},{"id":"IETF RFC 1038","type":"specification","body":"IETF","designation":"RFC 1038","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1038.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1038.txt","https://www.rfc-editor.org/rfc/rfc1038.pdf"],"folder":"IETF/RFC-1038","files":{"txt":{"path":"standards/IETF/RFC-1038/RFC-1038.txt","sha256":"62be07fd7c6a287c4a407c699f5b870c89d1abbdf0213c3c121b3f82aa622520"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. St. Johns\nRequest for Comments: 1038 IETF\n January 1988\n\n Draft Revised IP Security Option\n\nStatus of this Memo\n\n This RFC is a pre-publication draft of the revised Internet Protocol\n Security Option. This draft reflects the version as approved by\n the Protocol Standards Steering Group. It is provided for\n informational purposes only. The final version of this document will\n be available from Navy Publications and should not differ from\n this document in any major fashion.\n\n This document will be published as a change to the MIL-STD 1777,\n \"Internet Protocol\". Distribution of this memo is unlimited.\n\n9.3.13.1 Internet Options Defined.\n\n The following internet options are defined:\n\n CLASS NUMBER LENGTH DESCRIPTION\n ___ __ __ _________\n\n 0 00000 - End of Option list: This option occupies\n only 1 octet; it has no length octet.\n 0 00001 - No Operation: This option oc","scope_keywords":["1038","accreditation","registered","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1108","folder":"IETF/RFC-1108","source":"IETF/RFC-1108/RFC-1108.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 1038 Network Working Group M. St. Johns\nRequest for Comments: 1038 IETF\n January 1988\n\n Draft Revised IP Security Option\n\nStatus of this Memo\n\n This RFC is a pre-publication draft of the revised Internet Protocol\n Security Option. This draft reflects the version as approved by\n the Protocol Standards Steering Group. It is provided for\n informational purposes only. The final version of this document will\n be available from Navy Publications and should not differ from\n this document in any major fashion.\n\n This document will be published as a change to the MIL-STD 1777,\n \"Internet Protocol\". Distribution of this memo is unlimited.\n\n9.3.13.1 Internet Options Defined.\n\n The following internet options are defined:\n\n CLASS NUMBER LENGTH DESCRIPTION\n ___ __ __ _________\n\n 0 00000 - End of Option list: This option occupies\n only 1 octet; it has no length octet.\n 0 00001 - No Operation: This option oc 1038 accreditation registered timestamp trust nested-reference unchanged"},{"id":"IETF RFC 1108","type":"specification","body":"IETF","designation":"RFC 1108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1108.txt","https://www.rfc-editor.org/rfc/rfc1108.pdf"],"folder":"IETF/RFC-1108","files":{"txt":{"path":"standards/IETF/RFC-1108/RFC-1108.txt","sha256":"f39ade606d2be29cfa6713d34259c99e005cc111adca8a4f487b4ca0b3f3fe1e"}},"tags":["nested-reference","unchanged"],"summary":"This RFC specifies the U.S. Department of Defense Basic Security\n Option and the top-level description of the Extended Security Option\n for use with the Internet Protocol. This RFC obsoletes RFC 1038\n \"Revised IP Security Option\", dated January 1988.\n\n1. DoD Security Options Defined\n\n The following two internet protocol options are defined for use on\n Department of Defense (DoD) common user data networks:\n\n CF CLASS # TYPE LENGTH DESCRIPTION\n\n 1 0 2 130 var. DoD Basic Security: Used to carry the\n classification level and protection\n authority flags.\n\n 1 0 5 133 var. DoD Extended Security: Used to carry\n additional security information as\n required by registered authorities.\n\n CF = Copy on Fragmentation\n\n2. DoD Basic Security Option\n\n This option identifies the U.S. classification level at which the\n datagram is to be protected and the authorities whose protection\n rules apply to each dat","scope_keywords":["1108","accreditation","delivery","presentation","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 1108 This RFC specifies the U.S. Department of Defense Basic Security\n Option and the top-level description of the Extended Security Option\n for use with the Internet Protocol. This RFC obsoletes RFC 1038\n \"Revised IP Security Option\", dated January 1988.\n\n1. DoD Security Options Defined\n\n The following two internet protocol options are defined for use on\n Department of Defense (DoD) common user data networks:\n\n CF CLASS # TYPE LENGTH DESCRIPTION\n\n 1 0 2 130 var. DoD Basic Security: Used to carry the\n classification level and protection\n authority flags.\n\n 1 0 5 133 var. DoD Extended Security: Used to carry\n additional security information as\n required by registered authorities.\n\n CF = Copy on Fragmentation\n\n2. DoD Basic Security Option\n\n This option identifies the U.S. classification level at which the\n datagram is to be protected and the authorities whose protection\n rules apply to each dat 1108 accreditation delivery presentation registered subject nested-reference unchanged"},{"id":"IETF RFC 1040","type":"specification","body":"IETF","designation":"RFC 1040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1040.txt","https://www.rfc-editor.org/rfc/rfc1040.pdf"],"folder":"IETF/RFC-1040","files":{"txt":{"path":"standards/IETF/RFC-1040/RFC-1040.txt","sha256":"f7a2f96e8e9d59fa48d32f689472877481955ba04bb935ba913fd22684601a3b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Linn (BBNCC)\nRequest for Comments: 1040 IAB Privacy Task Force\nObsoletes RFCs: 989 January 1988\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Curt Barker, Matt Bishop, Danny Cohen, Tom Daniel, Charles\n Fox, Morrie Gasser, Steve Kent (chairman), John Laws, Steve Lipner","scope_keywords":["1040","attribute","attributes","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1114","folder":"IETF/RFC-1114","source":"IETF/RFC-1114/RFC-1114.txt","version":null}],"search_text":"IETF RFC 1040 Network Working Group J. Linn (BBNCC)\nRequest for Comments: 1040 IAB Privacy Task Force\nObsoletes RFCs: 989 January 1988\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Curt Barker, Matt Bishop, Danny Cohen, Tom Daniel, Charles\n Fox, Morrie Gasser, Steve Kent (chairman), John Laws, Steve Lipner 1040 attribute attributes authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 1114","type":"specification","body":"IETF","designation":"RFC 1114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1114.txt","https://www.rfc-editor.org/rfc/rfc1114.pdf"],"folder":"IETF/RFC-1114","files":{"txt":{"path":"standards/IETF/RFC-1114/RFC-1114.txt","sha256":"d817834936953f07f8a93aee2ed3578d71de799978f98bd6b837b0bcde82c311"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 1114 BBNCC\n J. Linn\n DEC\n IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part II -- Certificate-Based Key Management\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. We would like to thank the members of the Privacy Task\n Force for their comments and contributions at the meetings which led\n to the preparation of this RFC: David Balenson, Curt Barker, Matt\n Bishop, Morrie Gasser, Russ Housley, Dan Nessett, Mike Padlipsky, Rob\n Shirey, and Steve Wilbur.\n\nTable of Contents\n\n 1. Executive Summa","scope_keywords":["1114","algorithm","algorithms","authentication","certificate","certificates","credential","credentials","encryption","issuer","key","keys","license","management","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1319","folder":"IETF/RFC-1319","source":"IETF/RFC-1319/RFC-1319.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null}],"search_text":"IETF RFC 1114 Network Working Group S. Kent\nRequest for Comments: 1114 BBNCC\n J. Linn\n DEC\n IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part II -- Certificate-Based Key Management\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. We would like to thank the members of the Privacy Task\n Force for their comments and contributions at the meetings which led\n to the preparation of this RFC: David Balenson, Curt Barker, Matt\n Bishop, Morrie Gasser, Russ Housley, Dan Nessett, Mike Padlipsky, Rob\n Shirey, and Steve Wilbur.\n\nTable of Contents\n\n 1. Executive Summa 1114 algorithm algorithms authentication certificate certificates credential credentials encryption issuer key keys license management revocation signature nested-reference unchanged"},{"id":"IETF RFC 1041","type":"specification","body":"IETF","designation":"RFC 1041","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1041.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1041.txt","https://www.rfc-editor.org/rfc/rfc1041.pdf"],"folder":"IETF/RFC-1041","files":{"txt":{"path":"standards/IETF/RFC-1041/RFC-1041.txt","sha256":"f5bc91166a971c53ccc8df509c3d58e89c3d4f6e3b1f91501365bfa836d1aa58"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Rekhter\nRequest For Comments: 1041 T.J. Watson Research Center, IBM\n January 1988\n\n Telnet 3270 Regime Option\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a proposed standard for the Internet community.\n Hosts on the Internet, that want to support 3270 data stream within\n the Telnet protocol, are expected to adopt and implement this\n standard. Distribution of this memo is unlimited.\n\n1. Command Name and Code\n\n 3270-REGIME 29\n\n2. Command Meaning\n\n IAC WILL 3270-REGIME\n\n Sender is willing to send list of supported 3270 Regimes in\n a subsequent sub-negotiation.\n\n IAC WON'T 3270-REGIME\n\n Sender refuses to send the list of supported 3270 Regimes.\n\n IAC DO 3270-REGIME\n\n Sender is willing to receive a list of supported 3270 Regimes in a\n subsequent sub-negotiation.\n\n IAC DON'T 3270-REGIME\n\n Sender refuses to accept the list of supported 3270 Regimes.\n\n IAC SB 3270-REGIME A","scope_keywords":["1041","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1041 Network Working Group J. Rekhter\nRequest For Comments: 1041 T.J. Watson Research Center, IBM\n January 1988\n\n Telnet 3270 Regime Option\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a proposed standard for the Internet community.\n Hosts on the Internet, that want to support 3270 data stream within\n the Telnet protocol, are expected to adopt and implement this\n standard. Distribution of this memo is unlimited.\n\n1. Command Name and Code\n\n 3270-REGIME 29\n\n2. Command Meaning\n\n IAC WILL 3270-REGIME\n\n Sender is willing to send list of supported 3270 Regimes in\n a subsequent sub-negotiation.\n\n IAC WON'T 3270-REGIME\n\n Sender refuses to send the list of supported 3270 Regimes.\n\n IAC DO 3270-REGIME\n\n Sender is willing to receive a list of supported 3270 Regimes in a\n subsequent sub-negotiation.\n\n IAC DON'T 3270-REGIME\n\n Sender refuses to accept the list of supported 3270 Regimes.\n\n IAC SB 3270-REGIME A 1041 key nested-reference unchanged"},{"id":"IETF RFC 1576","type":"specification","body":"IETF","designation":"RFC 1576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1576.txt","https://www.rfc-editor.org/rfc/rfc1576.pdf"],"folder":"IETF/RFC-1576","files":{"txt":{"path":"standards/IETF/RFC-1576/RFC-1576.txt","sha256":"1b6b0662db9cd1a41263a120f82ee06b3c1ebc1a8960d8c4ec22cfe6ec5a39d3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the existing implementation of transferring\n 3270 display terminal data using currently available telnet\n capabilities. The name traditionally associated with this\n implementation is TN3270.\n\n Information is provided to aid in the implementation of TN3270\n servers as well as client terminal emulators.\n\n The following areas pertaining to TN3270 implementations are covered\n in this document:\n\n 1. the telnet options negotiated to transition from a NVT ASCII\n state to a TN3270 state ready to process incoming 3270 data\n stream commands\n\n 2. the method for sending and receiving 3270 data\n\n 3. the method of handling some special keys known as SYSREQ and\n ATTN using current available telnet commands\n\n 4. the events that will transition a TN3270 session back to an NVT\n session","scope_keywords":["1576","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null}],"search_text":"IETF RFC 1576 This document describes the existing implementation of transferring\n 3270 display terminal data using currently available telnet\n capabilities. The name traditionally associated with this\n implementation is TN3270.\n\n Information is provided to aid in the implementation of TN3270\n servers as well as client terminal emulators.\n\n The following areas pertaining to TN3270 implementations are covered\n in this document:\n\n 1. the telnet options negotiated to transition from a NVT ASCII\n state to a TN3270 state ready to process incoming 3270 data\n stream commands\n\n 2. the method for sending and receiving 3270 data\n\n 3. the method of handling some special keys known as SYSREQ and\n ATTN using current available telnet commands\n\n 4. the events that will transition a TN3270 session back to an NVT\n session 1576 key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1647","type":"specification","body":"IETF","designation":"RFC 1647","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1647.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1647.txt","https://www.rfc-editor.org/rfc/rfc1647.pdf"],"folder":"IETF/RFC-1647","files":{"txt":{"path":"standards/IETF/RFC-1647/RFC-1647.txt","sha256":"da840460758646827e35e98d8bea0db35b585daac0ec5b24f1583753db637837"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol that more fully supports 3270\n devices than do the existing tn3270 practices. Specifically, it\n defines a method of emulating both the terminal and printer members\n of the 3270 family of devices via Telnet; it provides for the ability\n of a Telnet client to request that it be assigned a specific device-\n name (also referred to as \"LU name\" or \"network name\"); finally, it\n adds support for a variety of functions such as the ATTN key, the\n SYSREQ key, and SNA response handling.\n\n This protocol would be negotiated and implemented under a new Telnet\n Option and would be unrelated to the Telnet 3270 Regime Option as\n defined in RFC 1041 [1].","scope_keywords":["1647","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null}],"search_text":"IETF RFC 1647 This document describes a protocol that more fully supports 3270\n devices than do the existing tn3270 practices. Specifically, it\n defines a method of emulating both the terminal and printer members\n of the 3270 family of devices via Telnet; it provides for the ability\n of a Telnet client to request that it be assigned a specific device-\n name (also referred to as \"LU name\" or \"network name\"); finally, it\n adds support for a variety of functions such as the ATTN key, the\n SYSREQ key, and SNA response handling.\n\n This protocol would be negotiated and implemented under a new Telnet\n Option and would be unrelated to the Telnet 3270 Regime Option as\n defined in RFC 1041 [1]. 1647 key keys nested-reference unchanged"},{"id":"IETF RFC 2355","type":"specification","body":"IETF","designation":"RFC 2355","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2355.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2355.txt","https://www.rfc-editor.org/rfc/rfc2355.pdf"],"folder":"IETF/RFC-2355","files":{"txt":{"path":"standards/IETF/RFC-2355/RFC-2355.txt","sha256":"82dd6c3b934d1844dd8696142510a20f91de018fe9c4e9e1f86cb5f9ddfe84a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol that more fully supports 3270\n devices than do traditional tn3270 practices. Specifically, it\n defines a method of emulating both the terminal and printer members\n of the 3270 family of devices via Telnet; it provides for the ability\n of a Telnet client to request that it be assigned a specific device-\n name (also referred to as \"LU name\" or \"network name\"); finally, it\n adds support for a variety of functions such as the ATTN key, the\n SYSREQ key, and SNA response handling.\n\n This protocol is negotiated under the TN3270E Telnet Option, and is\n unrelated to the Telnet 3270 Regime Option as defined in RFC 1041\n [1].","scope_keywords":["2355","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2355 This document describes a protocol that more fully supports 3270\n devices than do traditional tn3270 practices. Specifically, it\n defines a method of emulating both the terminal and printer members\n of the 3270 family of devices via Telnet; it provides for the ability\n of a Telnet client to request that it be assigned a specific device-\n name (also referred to as \"LU name\" or \"network name\"); finally, it\n adds support for a variety of functions such as the ATTN key, the\n SYSREQ key, and SNA response handling.\n\n This protocol is negotiated under the TN3270E Telnet Option, and is\n unrelated to the Telnet 3270 Regime Option as defined in RFC 1041\n [1]. 2355 key keys nested-reference unchanged"},{"id":"IETF RFC 4323","type":"specification","body":"IETF","designation":"RFC 4323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4323.txt","https://www.rfc-editor.org/rfc/rfc4323.pdf"],"folder":"IETF/RFC-4323","files":{"txt":{"path":"standards/IETF/RFC-4323/RFC-4323.txt","sha256":"1e51d715f38b73433b4cda4ece0dd9d0c652d4562a30204687894b4e090718c9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a basic set of managed objects for SNMP-based\n management of extended QoS features of Cable Modems (CMs) and Cable\n Modem Termination Systems (CMTSs) conforming to the Data over Cable\n System (DOCSIS) specifications versions 1.1 and 2.0.\n\nPatrick & Murwin Standards Track [Page 1]\n\f\nRFC 4323 IPCDN DOCSIS QoS MIB January 2006","scope_keywords":["4323","attribute","attributes","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null}],"search_text":"IETF RFC 4323 This document defines a basic set of managed objects for SNMP-based\n management of extended QoS features of Cable Modems (CMs) and Cable\n Modem Termination Systems (CMTSs) conforming to the Data over Cable\n System (DOCSIS) specifications versions 1.1 and 2.0.\n\nPatrick & Murwin Standards Track [Page 1]\n\f\nRFC 4323 IPCDN DOCSIS QoS MIB January 2006 4323 attribute attributes management path policy nested-reference unchanged"},{"id":"IETF RFC 1043","type":"specification","body":"IETF","designation":"RFC 1043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1043.txt","https://www.rfc-editor.org/rfc/rfc1043.pdf"],"folder":"IETF/RFC-1043","files":{"txt":{"path":"standards/IETF/RFC-1043/RFC-1043.txt","sha256":"16ad1f282351b32071003d2931f7f2a750699bacabe17797c95c12aac4cf53e5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Yasuda\nRequest for Comments: 1043 T. Thompson\n Defense Intelligence Agency\nUpdates: RFC 732 February 1988\n\n TELNET Data Entry Terminal Option\n DODIIS Implementation\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol on the TELNET Data Entry\n Terminal (DET) Option - DODIIS Implementation for the Internet\n community. It is intended that this specification be compatible with\n the specification of DET Option in RFC-732. Discussion and\n suggestions for improvements are encouraged. Distribution of this\n memo is unlimited.\n\nIntroduction\n\n In the early 1980s, the Defense Intelligence Agency (DIA) undertook\n the tasks of developing a TELNET capability to access full screen\n applications across a packet switching network. This effort was\n successful by implementing Data Entry Terminal (DET) options within\n the TELNET protocol based on RFC 732. These DET options h","scope_keywords":["1043","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1043 Network Working Group A. Yasuda\nRequest for Comments: 1043 T. Thompson\n Defense Intelligence Agency\nUpdates: RFC 732 February 1988\n\n TELNET Data Entry Terminal Option\n DODIIS Implementation\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol on the TELNET Data Entry\n Terminal (DET) Option - DODIIS Implementation for the Internet\n community. It is intended that this specification be compatible with\n the specification of DET Option in RFC-732. Discussion and\n suggestions for improvements are encouraged. Distribution of this\n memo is unlimited.\n\nIntroduction\n\n In the early 1980s, the Defense Intelligence Agency (DIA) undertook\n the tasks of developing a TELNET capability to access full screen\n applications across a packet switching network. This effort was\n successful by implementing Data Entry Terminal (DET) options within\n the TELNET protocol based on RFC 732. These DET options h 1043 key keys nested-reference unchanged"},{"id":"IETF RFC 1044","type":"specification","body":"IETF","designation":"RFC 1044","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1044.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1044.txt","https://www.rfc-editor.org/rfc/rfc1044.pdf"],"folder":"IETF/RFC-1044","files":{"txt":{"path":"standards/IETF/RFC-1044/RFC-1044.txt","sha256":"cfcbbf8e6d969aae1e823c8b7f2a5365a2586bcdc02ccefa9976669eb4ed5d87"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Hardwick\nRequest for Comments: 1044 NSC\n J. Lekashman\n NASA-Ames GE\n February 1988\n\n Internet Protocol on Network Systems HYPERchannel\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\n The intent of this document is to provide a complete discussion of\n the protocols and techniques used to embed DoD standard Internet\n Protocol datagrams (and its associated higher level protocols) on\n Network Systems Corporation's HYPERchannel [1] equipment.\n Distribution of this memo is unlimited.\n\n This document is intended for network planners and implementors who\n are already familiar with the TCP/IP protocol suite and the\n techniques used to carry TCP/IP traffic on common networks such as\n the DDN or Ethernet. No great familiarity with NSC products is\n assumed; an appendix is devoted to a review of NSC technologies and\n protocols.\n\n At the time of this first RFC edition, the cont","scope_keywords":["1044","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 1044 Network Working Group K. Hardwick\nRequest for Comments: 1044 NSC\n J. Lekashman\n NASA-Ames GE\n February 1988\n\n Internet Protocol on Network Systems HYPERchannel\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\n The intent of this document is to provide a complete discussion of\n the protocols and techniques used to embed DoD standard Internet\n Protocol datagrams (and its associated higher level protocols) on\n Network Systems Corporation's HYPERchannel [1] equipment.\n Distribution of this memo is unlimited.\n\n This document is intended for network planners and implementors who\n are already familiar with the TCP/IP protocol suite and the\n techniques used to carry TCP/IP traffic on common networks such as\n the DDN or Ethernet. No great familiarity with NSC products is\n assumed; an appendix is devoted to a review of NSC technologies and\n protocols.\n\n At the time of this first RFC edition, the cont 1044 delivery nested-reference unchanged"},{"id":"IETF RFC 1045","type":"specification","body":"IETF","designation":"RFC 1045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1045.txt","https://www.rfc-editor.org/rfc/rfc1045.pdf"],"folder":"IETF/RFC-1045","files":{"txt":{"path":"standards/IETF/RFC-1045/RFC-1045.txt","sha256":"4492417a8bdf8daa393ca6cda0407c053bad40c83c4ecb8f0e8b2306aa565f02"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David Cheriton\nRequest for Comments: 1045 Stanford University\n February 1988\n\n VMTP: VERSATILE MESSAGE TRANSACTION PROTOCOL\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\nThis RFC describes a protocol proposed as a standard for the Internet\ncommunity. Comments are encouraged. Distribution of this document is\nunlimited.\n\nOVERVIEW\n\nThis memo specifies the Versatile Message Transaction Protocol (VMTP)\n[Version 0.7 of 19-Feb-88], a transport protocol specifically designed\nto support the transaction model of communication, as exemplified by\nremote procedure call (RPC). The full function of VMTP, including\nsupport for security, real-time, asynchronous message exchanges,\nstreaming, multicast and idempotency, provides a rich selection to the\nVMTP user level. Subsettability allows the VMTP module for particular\nclients and servers to be specialized and simplified to the servi","scope_keywords":["1045","authentication","management","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1072","folder":"IETF/RFC-1072","source":"IETF/RFC-1072/RFC-1072.txt","version":null},{"body":"IETF","designation":"RFC 1077","folder":"IETF/RFC-1077","source":"IETF/RFC-1077/RFC-1077.txt","version":null},{"body":"IETF","designation":"RFC 1105","folder":"IETF/RFC-1105","source":"IETF/RFC-1105/RFC-1105.txt","version":null},{"body":"IETF","designation":"RFC 1106","folder":"IETF/RFC-1106","source":"IETF/RFC-1106/RFC-1106.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1263","folder":"IETF/RFC-1263","source":"IETF/RFC-1263/RFC-1263.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 1045 Network Working Group David Cheriton\nRequest for Comments: 1045 Stanford University\n February 1988\n\n VMTP: VERSATILE MESSAGE TRANSACTION PROTOCOL\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\nThis RFC describes a protocol proposed as a standard for the Internet\ncommunity. Comments are encouraged. Distribution of this document is\nunlimited.\n\nOVERVIEW\n\nThis memo specifies the Versatile Message Transaction Protocol (VMTP)\n[Version 0.7 of 19-Feb-88], a transport protocol specifically designed\nto support the transaction model of communication, as exemplified by\nremote procedure call (RPC). The full function of VMTP, including\nsupport for security, real-time, asynchronous message exchanges,\nstreaming, multicast and idempotency, provides a rich selection to the\nVMTP user level. Subsettability allows the VMTP module for particular\nclients and servers to be specialized and simplified to the servi 1045 authentication management presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 1072","type":"specification","body":"IETF","designation":"RFC 1072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1072.txt","https://www.rfc-editor.org/rfc/rfc1072.pdf"],"folder":"IETF/RFC-1072","files":{"txt":{"path":"standards/IETF/RFC-1072/RFC-1072.txt","sha256":"245f4ef0bca4dd8205a3a31f1e946cd8bf6987e5813dd715f838a7d0642103a7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Jacobson\nRequest for Comments: 1072 LBL\n R. Braden\n ISI\n October 1988\n\n TCP Extensions for Long-Delay Paths\n\nStatus of This Memo\n\n This memo proposes a set of extensions to the TCP protocol to provide\n efficient operation over a path with a high bandwidth*delay product.\n These extensions are not proposed as an Internet standard at this\n time. Instead, they are intended as a basis for further\n experimentation and research on transport protocol performance.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n Recent work on TCP performance has shown that TCP can work well over\n a variety of Internet paths, ranging from 800 Mbit/sec I/O channels\n to 300 bit/sec dial-up modems [Jacobson88]. However, there is still\n a fundamental TCP performance bottleneck for one transmission regime:\n paths with high bandwidth and long round-trip delays. The\n significant param","scope_keywords":["1072","algorithm","algorithms","delivery","path","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1106","folder":"IETF/RFC-1106","source":"IETF/RFC-1106/RFC-1106.txt","version":null},{"body":"IETF","designation":"RFC 1185","folder":"IETF/RFC-1185","source":"IETF/RFC-1185/RFC-1185.txt","version":null},{"body":"IETF","designation":"RFC 1263","folder":"IETF/RFC-1263","source":"IETF/RFC-1263/RFC-1263.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1693","folder":"IETF/RFC-1693","source":"IETF/RFC-1693/RFC-1693.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1072 Network Working Group V. Jacobson\nRequest for Comments: 1072 LBL\n R. Braden\n ISI\n October 1988\n\n TCP Extensions for Long-Delay Paths\n\nStatus of This Memo\n\n This memo proposes a set of extensions to the TCP protocol to provide\n efficient operation over a path with a high bandwidth*delay product.\n These extensions are not proposed as an Internet standard at this\n time. Instead, they are intended as a basis for further\n experimentation and research on transport protocol performance.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n Recent work on TCP performance has shown that TCP can work well over\n a variety of Internet paths, ranging from 800 Mbit/sec I/O channels\n to 300 bit/sec dial-up modems [Jacobson88]. However, there is still\n a fundamental TCP performance bottleneck for one transmission regime:\n paths with high bandwidth and long round-trip delays. The\n significant param 1072 algorithm algorithms delivery path subject timestamp nested-reference unchanged"},{"id":"IETF RFC 1105","type":"specification","body":"IETF","designation":"RFC 1105","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1105.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1105.txt","https://www.rfc-editor.org/rfc/rfc1105.pdf"],"folder":"IETF/RFC-1105","files":{"txt":{"path":"standards/IETF/RFC-1105/RFC-1105.txt","sha256":"d2e6d3eb74a4611b0099b56301197a1c2c107e10d9990a14c5e41f54d369aaca"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Lougheed\nRequest for Comments: 1105 cisco Systems\n Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n June 1989\n\n A Border Gateway Protocol (BGP)\n\nStatus of this Memo\n\n This RFC outlines a specific approach for the exchange of network\n reachability information between Autonomous Systems.\n\n At the time of this writing, the Border Gateway Protocol\n implementations exist for cisco routers as well as for the NSFNET\n Nodal Switching Systems. A public domain version for \"gated\" is\n currently being implemented.\n\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol. It is built on experience gained with EGP as\n defined in RFC 904 [1] and EGP usage in the NSFNET Backbone as\n described in RFC 1092 [2] and RFC 1093 [3].\n\n The primary function of a BGP speaking system is to exchange net","scope_keywords":["1105","authentication","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1265","folder":"IETF/RFC-1265","source":"IETF/RFC-1265/RFC-1265.txt","version":null},{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null}],"search_text":"IETF RFC 1105 Network Working Group K. Lougheed\nRequest for Comments: 1105 cisco Systems\n Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n June 1989\n\n A Border Gateway Protocol (BGP)\n\nStatus of this Memo\n\n This RFC outlines a specific approach for the exchange of network\n reachability information between Autonomous Systems.\n\n At the time of this writing, the Border Gateway Protocol\n implementations exist for cisco routers as well as for the NSFNET\n Nodal Switching Systems. A public domain version for \"gated\" is\n currently being implemented.\n\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol. It is built on experience gained with EGP as\n defined in RFC 904 [1] and EGP usage in the NSFNET Backbone as\n described in RFC 1092 [2] and RFC 1093 [3].\n\n The primary function of a BGP speaking system is to exchange net 1105 authentication policy nested-reference unchanged"},{"id":"IETF RFC 1106","type":"specification","body":"IETF","designation":"RFC 1106","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1106.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1106.txt","https://www.rfc-editor.org/rfc/rfc1106.pdf"],"folder":"IETF/RFC-1106","files":{"txt":{"path":"standards/IETF/RFC-1106/RFC-1106.txt","sha256":"b406a33651e822da78e7311f3c598fb5b4d0048749f0e2475e99f4e5cf7fe6b8"}},"tags":["nested-reference","unchanged"],"summary":"Two extensions to the TCP protocol are described in this RFC in order\n to provide a more efficient operation over a network with a high\n bandwidth*delay product. The main issue that still needs to be\n solved is congestion versus noise. This issue is touched on in this\n memo, but further research is still needed on the applicability of\n the extensions in the Internet as a whole infrastructure and not just\n high bandwidth*delay product networks. Even with this outstanding\n issue, this document does describe the use of these options in the\n isolated satellite network environment to help facilitate more\n efficient use of this special medium to help off load bulk data\n transfers from links needed for interactive use.\n\n1. Introduction\n\n Recent work on TCP has shown great performance gains over a variety\n of network paths [1]. However, these changes still do not work well\n over network paths th","scope_keywords":["1106","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1110","folder":"IETF/RFC-1110","source":"IETF/RFC-1110/RFC-1110.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1106 Two extensions to the TCP protocol are described in this RFC in order\n to provide a more efficient operation over a network with a high\n bandwidth*delay product. The main issue that still needs to be\n solved is congestion versus noise. This issue is touched on in this\n memo, but further research is still needed on the applicability of\n the extensions in the Internet as a whole infrastructure and not just\n high bandwidth*delay product networks. Even with this outstanding\n issue, this document does describe the use of these options in the\n isolated satellite network environment to help facilitate more\n efficient use of this special medium to help off load bulk data\n transfers from links needed for interactive use.\n\n1. Introduction\n\n Recent work on TCP has shown great performance gains over a variety\n of network paths [1]. However, these changes still do not work well\n over network paths th 1106 algorithm path nested-reference unchanged"},{"id":"IETF RFC 1190","type":"specification","body":"IETF","designation":"RFC 1190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1190.txt","https://www.rfc-editor.org/rfc/rfc1190.pdf"],"folder":"IETF/RFC-1190","files":{"txt":{"path":"standards/IETF/RFC-1190/RFC-1190.txt","sha256":"5449da3af546b6fda935d8121eda43fba30bd11867f6eda5dd620da620c9ddc4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Internet Stream Protocol, Version 2 (ST-II), an\n IP-layer protocol that provides end-to-end guaranteed service across\n an internet. This specification obsoletes IEN 119 \"ST - A Proposed\n Internet Stream Protocol\" written by Jim Forgie in 1979, the previous\n specification of ST. ST-II is not compatible with Version 1 of the\n protocol, but maintains much of the architecture and philosophy of\n that version. It is intended to fill in some of the areas left\n unaddressed, to make it easier to implement, and to support a wider\n range of applications.\n\nCIP Working Group [Page 1]\n\f\nRFC 1190 Internet Stream Protocol October 1990","scope_keywords":["1190","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1633","folder":"IETF/RFC-1633","source":"IETF/RFC-1633/RFC-1633.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null}],"search_text":"IETF RFC 1190 This memo defines the Internet Stream Protocol, Version 2 (ST-II), an\n IP-layer protocol that provides end-to-end guaranteed service across\n an internet. This specification obsoletes IEN 119 \"ST - A Proposed\n Internet Stream Protocol\" written by Jim Forgie in 1979, the previous\n specification of ST. ST-II is not compatible with Version 1 of the\n protocol, but maintains much of the architecture and philosophy of\n that version. It is intended to fill in some of the areas left\n unaddressed, to make it easier to implement, and to support a wider\n range of applications.\n\nCIP Working Group [Page 1]\n\f\nRFC 1190 Internet Stream Protocol October 1990 1190 timestamp nested-reference unchanged"},{"id":"IETF RFC 1263","type":"specification","body":"IETF","designation":"RFC 1263","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1263.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1263.txt","https://www.rfc-editor.org/rfc/rfc1263.pdf"],"folder":"IETF/RFC-1263","files":{"txt":{"path":"standards/IETF/RFC-1263/RFC-1263.txt","sha256":"a066ba95bae10e25356be705ccee99a01b270f97efe54b82206106ca5eeff666"}},"tags":["nested-reference","unchanged"],"summary":"This RFC comments on recent proposals to extend TCP. It argues that\n the backward compatible extensions proposed in RFC's 1072 and 1185\n should not be pursued, and proposes an alternative way to evolve the\n Internet protocol suite. Its purpose is to stimulate discussion in\n the Internet community.\n\n1. Introduction\n\n The rapid growth of the size, capacity, and complexity of the\n Internet has led to the need to change the existing protocol suite.\n For example, the maximum TCP window size is no longer sufficient to\n efficiently support the high capacity links currently being planned\n and constructed. One is then faced with the choice of either leaving\n the protocol alone and accepting the fact that TCP will run no faster\n on high capacity links than on low capacity links, or changing TCP.\n This is not an isolated incident. We have counted at least eight\n other proposed changes to TCP (some ","scope_keywords":["1263","algorithm","algorithms","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1693","folder":"IETF/RFC-1693","source":"IETF/RFC-1693/RFC-1693.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null}],"search_text":"IETF RFC 1263 This RFC comments on recent proposals to extend TCP. It argues that\n the backward compatible extensions proposed in RFC's 1072 and 1185\n should not be pursued, and proposes an alternative way to evolve the\n Internet protocol suite. Its purpose is to stimulate discussion in\n the Internet community.\n\n1. Introduction\n\n The rapid growth of the size, capacity, and complexity of the\n Internet has led to the need to change the existing protocol suite.\n For example, the maximum TCP window size is no longer sufficient to\n efficiently support the high capacity links currently being planned\n and constructed. One is then faced with the choice of either leaving\n the protocol alone and accepting the fact that TCP will run no faster\n on high capacity links than on low capacity links, or changing TCP.\n This is not an isolated incident. We have counted at least eight\n other proposed changes to TCP (some  1263 algorithm algorithms pid nested-reference unchanged"},{"id":"IETF RFC 1323","type":"specification","body":"IETF","designation":"RFC 1323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1323.txt","https://www.rfc-editor.org/rfc/rfc1323.pdf"],"folder":"IETF/RFC-1323","files":{"txt":{"path":"standards/IETF/RFC-1323/RFC-1323.txt","sha256":"ad1a5cf5f760ac0d7e0e135159e45df4bf148a0b95cdc883a50c45f036ae91ec"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a set of TCP extensions to improve performance\n over large bandwidth*delay product paths and to provide reliable\n operation over very high-speed paths. It defines new TCP options for\n scaled windows and timestamps, which are designed to provide\n compatible interworking with TCP's that do not implement the\n extensions. The timestamps are used for two distinct mechanisms:\n RTTM (Round Trip Time Measurement) and PAWS (Protect Against Wrapped\n Sequences). Selective acknowledgments are not included in this memo.\n\n This memo combines and supersedes RFC-1072 and RFC-1185, adding\n additional clarification and more detailed specification. Appendix C\n summarizes the changes from the earlier RFCs.","scope_keywords":["1323","algorithm","algorithms","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1693","folder":"IETF/RFC-1693","source":"IETF/RFC-1693/RFC-1693.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2147","folder":"IETF/RFC-2147","source":"IETF/RFC-2147/RFC-2147.txt","version":null},{"body":"IETF","designation":"RFC 2385","folder":"IETF/RFC-2385","source":"IETF/RFC-2385/RFC-2385.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2988","folder":"IETF/RFC-2988","source":"IETF/RFC-2988/RFC-2988.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3649","folder":"IETF/RFC-3649","source":"IETF/RFC-3649/RFC-3649.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1323 This memo presents a set of TCP extensions to improve performance\n over large bandwidth*delay product paths and to provide reliable\n operation over very high-speed paths. It defines new TCP options for\n scaled windows and timestamps, which are designed to provide\n compatible interworking with TCP's that do not implement the\n extensions. The timestamps are used for two distinct mechanisms:\n RTTM (Round Trip Time Measurement) and PAWS (Protect Against Wrapped\n Sequences). Selective acknowledgments are not included in this memo.\n\n This memo combines and supersedes RFC-1072 and RFC-1185, adding\n additional clarification and more detailed specification. Appendix C\n summarizes the changes from the earlier RFCs. 1323 algorithm algorithms path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2018","type":"specification","body":"IETF","designation":"RFC 2018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2018.txt","https://www.rfc-editor.org/rfc/rfc2018.pdf"],"folder":"IETF/RFC-2018","files":{"txt":{"path":"standards/IETF/RFC-2018/RFC-2018.txt","sha256":"0cc70b98e47b37c1b88f1f31237a580afa2283c7b79714fcf81da6e9772a9b97"}},"tags":["nested-reference","unchanged"],"summary":"TCP may experience poor performance when multiple packets are lost\n from one window of data. With the limited information available\n from cumulative acknowledgments, a TCP sender can only learn about a\n single lost packet per round trip time. An aggressive sender could\n choose to retransmit packets early, but such retransmitted segments\n may have already been successfully received.\n\n A Selective Acknowledgment (SACK) mechanism, combined with a\n selective repeat retransmission policy, can help to overcome these\n limitations. The receiving TCP sends back SACK packets to the sender\n informing the sender of data that has been received. The sender can\n then retransmit only the missing data segments.\n\n This memo proposes an implementation of SACK and discusses its\n performance and related issues.\n\nAcknowledgements\n\n Much of the text in this document is taken directly from RFC1072 \"TCP\n Extensi","scope_keywords":["2018","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2582","folder":"IETF/RFC-2582","source":"IETF/RFC-2582/RFC-2582.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 2018 TCP may experience poor performance when multiple packets are lost\n from one window of data. With the limited information available\n from cumulative acknowledgments, a TCP sender can only learn about a\n single lost packet per round trip time. An aggressive sender could\n choose to retransmit packets early, but such retransmitted segments\n may have already been successfully received.\n\n A Selective Acknowledgment (SACK) mechanism, combined with a\n selective repeat retransmission policy, can help to overcome these\n limitations. The receiving TCP sends back SACK packets to the sender\n informing the sender of data that has been received. The sender can\n then retransmit only the missing data segments.\n\n This memo proposes an implementation of SACK and discusses its\n performance and related issues.\n\nAcknowledgements\n\n Much of the text in this document is taken directly from RFC1072 \"TCP\n Extensi 2018 path policy nested-reference unchanged"},{"id":"IETF RFC 2375","type":"specification","body":"IETF","designation":"RFC 2375","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2375.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2375.txt","https://www.rfc-editor.org/rfc/rfc2375.pdf"],"folder":"IETF/RFC-2375","files":{"txt":{"path":"standards/IETF/RFC-2375/RFC-2375.txt","sha256":"d9be028b2a6d0aa8c6bdf6cae13f7d684f5e99a31fd4ce798d5c9fc1ead12cc7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 2375 Ipsilon Networks\nCategory: Informational S. Deering\n Cisco\n July 1998\n\n IPv6 Multicast Address Assignments\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document defines the initial assignment of IPv6 multicast\n addresses. It is based on the \"IP Version 6 Addressing Architecture\"\n [ADDARCH] and current IPv4 multicast address assignment found in\n .\n It adapts the IPv4 assignments that are relevant to IPv6 assignments.\n IPv4 assignments that were not relevant were not converted into IPv6\n assignments. Comments are solicited on this conversion.\n\n All other IPv6 multicast addresses are reserved.\n\n","scope_keywords":["2375","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null}],"search_text":"IETF RFC 2375 Network Working Group R. Hinden\nRequest for Comments: 2375 Ipsilon Networks\nCategory: Informational S. Deering\n Cisco\n July 1998\n\n IPv6 Multicast Address Assignments\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document defines the initial assignment of IPv6 multicast\n addresses. It is based on the \"IP Version 6 Addressing Architecture\"\n [ADDARCH] and current IPv4 multicast address assignment found in\n .\n It adapts the IPv4 assignments that are relevant to IPv6 assignments.\n IPv4 assignments that were not relevant were not converted into IPv6\n assignments. Comments are solicited on this conversion.\n\n All other IPv6 multicast addresses are reserved.\n\n 2375 key nested-reference unchanged"},{"id":"IETF RFC 1046","type":"specification","body":"IETF","designation":"RFC 1046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1046.txt","https://www.rfc-editor.org/rfc/rfc1046.pdf"],"folder":"IETF/RFC-1046","files":{"txt":{"path":"standards/IETF/RFC-1046/RFC-1046.txt","sha256":"13cfa57fe18ed6c43fbe85335572575bcb89d8c46fd94c3149b76999f92b8133"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Prue\nRequest for Comments: 1046 J. Postel\n ISI\n February 1988\n\n A Queuing Algorithm to Provide Type-of-Service for IP Links\n\nStatus of this Memo\n\n This memo is intended to explore how Type-of-Service might be\n implemented in the Internet. The proposal describes a method of\n queuing which can provide the different classes of service. The\n technique also prohibits one class of service from consuming\n excessive resources or excluding other classes of service. This is\n an \"idea paper\" and discussion is strongly encouraged. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n The Type-of-Service (TOS) field in IP headers allows one to chose\n from none to all the following service types; low delay, high\n throughput, and high reliability. It also has a portion allowing a\n priority selection from 0-7. To date, there is nothing describing\n what should be done with the","scope_keywords":["1046","algorithm","algorithms","attribute","attributes","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1046 Network Working Group W. Prue\nRequest for Comments: 1046 J. Postel\n ISI\n February 1988\n\n A Queuing Algorithm to Provide Type-of-Service for IP Links\n\nStatus of this Memo\n\n This memo is intended to explore how Type-of-Service might be\n implemented in the Internet. The proposal describes a method of\n queuing which can provide the different classes of service. The\n technique also prohibits one class of service from consuming\n excessive resources or excluding other classes of service. This is\n an \"idea paper\" and discussion is strongly encouraged. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n The Type-of-Service (TOS) field in IP headers allows one to chose\n from none to all the following service types; low delay, high\n throughput, and high reliability. It also has a portion allowing a\n priority selection from 0-7. To date, there is nothing describing\n what should be done with the 1046 algorithm algorithms attribute attributes delivery key path nested-reference unchanged"},{"id":"IETF RFC 1047","type":"specification","body":"IETF","designation":"RFC 1047","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1047.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1047.txt","https://www.rfc-editor.org/rfc/rfc1047.pdf"],"folder":"IETF/RFC-1047","files":{"txt":{"path":"standards/IETF/RFC-1047/RFC-1047.txt","sha256":"8b6963d94505c9245c127116e2bde40ae35c1ecfa4541b37352aa4f3e52ff7e4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Craig Partridge\nRequest for Comments: 1047 CIC at BBN Labs\n February 1988\n\n DUPLICATE MESSAGES AND SMTP\n\nSTATUS OF THIS MEMO\n\n An examination of a synchronization problem in the Simple Mail\n Transfer Protocol (SMTP) is presented. This synchronization problem\n can cause a message to be delivered multiple times. A method for\n avoiding this problem is suggested. Nodding familiarity with the\n SMTP specification, RFC-821, is required. Distribution of this memo\n is unlimited.\n\nINTRODUCTION\n\n Over the past few years, the staff of the CSNET Coordination and\n Information Center (CIC) has often been asked to help determine why a\n single mail message is being delivered multiple times to its\n recipients. In the process of tracing the problems of multiple\n delivery, we have discovered that many duplicate messages are the\n result of a synchronization problem in SMTP. There is a p","scope_keywords":["1047","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null}],"search_text":"IETF RFC 1047 Network Working Group Craig Partridge\nRequest for Comments: 1047 CIC at BBN Labs\n February 1988\n\n DUPLICATE MESSAGES AND SMTP\n\nSTATUS OF THIS MEMO\n\n An examination of a synchronization problem in the Simple Mail\n Transfer Protocol (SMTP) is presented. This synchronization problem\n can cause a message to be delivered multiple times. A method for\n avoiding this problem is suggested. Nodding familiarity with the\n SMTP specification, RFC-821, is required. Distribution of this memo\n is unlimited.\n\nINTRODUCTION\n\n Over the past few years, the staff of the CSNET Coordination and\n Information Center (CIC) has often been asked to help determine why a\n single mail message is being delivered multiple times to its\n recipients. In the process of tracing the problems of multiple\n delivery, we have discovered that many duplicate messages are the\n result of a synchronization problem in SMTP. There is a p 1047 delivery nested-reference unchanged"},{"id":"IETF RFC 1894","type":"specification","body":"IETF","designation":"RFC 1894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1894.txt","https://www.rfc-editor.org/rfc/rfc1894.pdf"],"folder":"IETF/RFC-1894","files":{"txt":{"path":"standards/IETF/RFC-1894/RFC-1894.txt","sha256":"6f429ed9e9eeb7f41f835bbd59168afb3a62791d91f6fa1e37ceca849a725480"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIME content-type that may be used by a message\n transfer agent (MTA) or electronic mail gateway to report the result\n of an attempt to deliver a message to one or more recipients. This\n content-type is intended as a machine-processable replacement for the\n various types of delivery status notifications currently used in\n Internet electronic mail.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as X.400 or the so-called \"LAN-based\"\n systems), the DSN protocol is designed to be useful in a multi-\n protocol messaging environment. To this end, the protocol described\n in this memo provides for the carriage of \"foreign\" addresses and\n error codes, in addition to those normally used in Internet mail.\n Additional attributes may also be defined to support \"tunneling\" of\n foreign notifications through Internet mail.\n\n Any questions, com","scope_keywords":["1894","attribute","attributes","delivery","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1892","folder":"IETF/RFC-1892","source":"IETF/RFC-1892/RFC-1892.txt","version":null},{"body":"IETF","designation":"RFC 1893","folder":"IETF/RFC-1893","source":"IETF/RFC-1893/RFC-1893.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2034","folder":"IETF/RFC-2034","source":"IETF/RFC-2034/RFC-2034.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null}],"search_text":"IETF RFC 1894 This memo defines a MIME content-type that may be used by a message\n transfer agent (MTA) or electronic mail gateway to report the result\n of an attempt to deliver a message to one or more recipients. This\n content-type is intended as a machine-processable replacement for the\n various types of delivery status notifications currently used in\n Internet electronic mail.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as X.400 or the so-called \"LAN-based\"\n systems), the DSN protocol is designed to be useful in a multi-\n protocol messaging environment. To this end, the protocol described\n in this memo provides for the carriage of \"foreign\" addresses and\n error codes, in addition to those normally used in Internet mail.\n Additional attributes may also be defined to support \"tunneling\" of\n foreign notifications through Internet mail.\n\n Any questions, com 1894 attribute attributes delivery subject nested-reference unchanged"},{"id":"IETF RFC 2033","type":"specification","body":"IETF","designation":"RFC 2033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2033.txt","https://www.rfc-editor.org/rfc/rfc2033.pdf"],"folder":"IETF/RFC-2033","files":{"txt":{"path":"standards/IETF/RFC-2033/RFC-2033.txt","sha256":"335b60f0e5269ce8ff774c37b0fb78e7c42928df68d2061d71d51b82697b2773"}},"tags":["nested-reference","unchanged"],"summary":"SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a\n mechanism for transferring mail reliably and efficiently. The design\n of the SMTP protocol effectively requires the server to manage a mail\n delivery queue.\n\n In some limited circumstances, outside the area of mail exchange\n between independent hosts on public networks, it is desirable to\n implement a system where a mail receiver does not manage a queue.\n This document describes the LMTP protocol for transporting mail into\n such systems.\n\n Although LMTP is an alternative protocol to ESMTP, it uses (with a\n few changes) the syntax and semantics of ESMTP. This design permits\n LMTP to utilize the extensions defined for ESMTP. LMTP should be\n used only by specific prior arrangement and configuration, and it\n MUST NOT be used on TCP port 25.","scope_keywords":["2033","delivery","management","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null}],"search_text":"IETF RFC 2033 SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a\n mechanism for transferring mail reliably and efficiently. The design\n of the SMTP protocol effectively requires the server to manage a mail\n delivery queue.\n\n In some limited circumstances, outside the area of mail exchange\n between independent hosts on public networks, it is desirable to\n implement a system where a mail receiver does not manage a queue.\n This document describes the LMTP protocol for transporting mail into\n such systems.\n\n Although LMTP is an alternative protocol to ESMTP, it uses (with a\n few changes) the syntax and semantics of ESMTP. This design permits\n LMTP to utilize the extensions defined for ESMTP. LMTP should be\n used only by specific prior arrangement and configuration, and it\n MUST NOT be used on TCP port 25. 2033 delivery management risk nested-reference unchanged"},{"id":"IETF RFC 3464","type":"specification","body":"IETF","designation":"RFC 3464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3464.txt","https://www.rfc-editor.org/rfc/rfc3464.pdf"],"folder":"IETF/RFC-3464","files":{"txt":{"path":"standards/IETF/RFC-3464/RFC-3464.txt","sha256":"8d213b662d9c40a7a729db598beb1d3f0139b7532b3c9a7be06ef220c84c397c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Multipurpose Internet Mail Extensions (MIME)\n content-type that may be used by a message transfer agent (MTA) or\n electronic mail gateway to report the result of an attempt to deliver\n a message to one or more recipients. This content-type is intended\n as a machine-processable replacement for the various types of\n delivery status notifications currently used in Internet electronic\n mail.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as X.400 or the so-called \"Local Area Network\n (LAN)-based\" systems), the Delivery Status Notification (DSN)\n protocol is designed to be useful in a multi-protocol messaging\n environment. To this end, the protocol described in this memo\n provides for the carriage of \"foreign\" addresses and error codes, in\n addition to those normally used in Internet mail. Additional\n attributes may also be defined","scope_keywords":["3464","attribute","attributes","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3463","folder":"IETF/RFC-3463","source":"IETF/RFC-3463/RFC-3463.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null}],"search_text":"IETF RFC 3464 This memo defines a Multipurpose Internet Mail Extensions (MIME)\n content-type that may be used by a message transfer agent (MTA) or\n electronic mail gateway to report the result of an attempt to deliver\n a message to one or more recipients. This content-type is intended\n as a machine-processable replacement for the various types of\n delivery status notifications currently used in Internet electronic\n mail.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as X.400 or the so-called \"Local Area Network\n (LAN)-based\" systems), the Delivery Status Notification (DSN)\n protocol is designed to be useful in a multi-protocol messaging\n environment. To this end, the protocol described in this memo\n provides for the carriage of \"foreign\" addresses and error codes, in\n addition to those normally used in Internet mail. Additional\n attributes may also be defined 3464 attribute attributes delivery key subject nested-reference unchanged"},{"id":"IETF RFC 1048","type":"specification","body":"IETF","designation":"RFC 1048","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1048.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1048.txt","https://www.rfc-editor.org/rfc/rfc1048.pdf"],"folder":"IETF/RFC-1048","files":{"txt":{"path":"standards/IETF/RFC-1048/RFC-1048.txt","sha256":"b540e9ec937f11630a6f35b92a71c2d3f59c50f7595ff1b3b835130f045486ff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Prindeville\nRequest for Comments: 1048 McGill University\n February 1988\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo proposes an addition to the Bootstrap Protocol (BOOTP).\n Comments and suggestions for improvements are sought. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such responsibility to the user is not plausible and,\n indeed, the solution is to define the resources in uniform terms, and\n to automate their assignment.\n\n The basic Bootstrap Protocol [RFC-951] dealt with the issue of\n assigning an internet address to a client, as well as ","scope_keywords":["1048","management","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null}],"search_text":"IETF RFC 1048 Network Working Group P. Prindeville\nRequest for Comments: 1048 McGill University\n February 1988\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo proposes an addition to the Bootstrap Protocol (BOOTP).\n Comments and suggestions for improvements are sought. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such responsibility to the user is not plausible and,\n indeed, the solution is to define the resources in uniform terms, and\n to automate their assignment.\n\n The basic Bootstrap Protocol [RFC-951] dealt with the issue of\n assigning an internet address to a client, as well as  1048 management qualified registered nested-reference unchanged"},{"id":"IETF RFC 1049","type":"specification","body":"IETF","designation":"RFC 1049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1049.txt","https://www.rfc-editor.org/rfc/rfc1049.pdf"],"folder":"IETF/RFC-1049","files":{"txt":{"path":"standards/IETF/RFC-1049/RFC-1049.txt","sha256":"8e30e9f81e7ffa9ac1e15e20ab46c472985e531ba49f299392f9217b3c564b0e"}},"tags":["nested-reference","unchanged"],"summary":"A standardized Content-type field allows mail reading systems to\n automatically identify the type of a structured message body and to\n process it for display accordingly. The structured message body must\n still conform to the RFC-822 requirements concerning allowable\n characters. A mail reading system need not take any specific action\n upon receiving a message with a valid Content-Type header field. The\n ability to recognize this field and invoke the appropriate display\n process accordingly will, however, improve the readability of\n messages, and allow the exchange of messages containing mathematical\n symbols, or foreign language characters.","scope_keywords":["1049"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 1049 A standardized Content-type field allows mail reading systems to\n automatically identify the type of a structured message body and to\n process it for display accordingly. The structured message body must\n still conform to the RFC-822 requirements concerning allowable\n characters. A mail reading system need not take any specific action\n upon receiving a message with a valid Content-Type header field. The\n ability to recognize this field and invoke the appropriate display\n process accordingly will, however, improve the readability of\n messages, and allow the exchange of messages containing mathematical\n symbols, or foreign language characters. 1049 nested-reference unchanged"},{"id":"IETF RFC 1154","type":"specification","body":"IETF","designation":"RFC 1154","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1154.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1154.txt","https://www.rfc-editor.org/rfc/rfc1154.pdf"],"folder":"IETF/RFC-1154","files":{"txt":{"path":"standards/IETF/RFC-1154/RFC-1154.txt","sha256":"e644251b65d58726db7ff231ccea98e90c7fab302ff5909c0b72301caf727922"}},"tags":["nested-reference","unchanged"],"summary":"was to select a channel on a paper tape loop controlling the printer.","scope_keywords":["1154","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null}],"search_text":"IETF RFC 1154 was to select a channel on a paper tape loop controlling the printer. 1154 key registered nested-reference unchanged"},{"id":"IETF RFC 1341","type":"specification","body":"IETF","designation":"RFC 1341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1341.txt","https://www.rfc-editor.org/rfc/rfc1341.pdf"],"folder":"IETF/RFC-1341","files":{"pdf":{"path":"standards/IETF/RFC-1341/RFC-1341.pdf","sha256":"6c42091034da34a8efc04840513855f1fcecb4486b26ed63fc3b4cebfd1f4336"},"txt":{"path":"standards/IETF/RFC-1341/RFC-1341.txt","sha256":"6489eb63a43ada70c6db1bf5a0af6af71b529b271961537217ec76d1454e3008"}},"tags":["nested-reference","unchanged"],"summary":"RFC 822 defines a message representation protocol which\n specifies considerable detail about message headers, but\n which leaves the message content, or message body, as flat\n ASCII text. This document redefines the format of message\n bodies to allow multi-part textual and non-textual message\n bodies to be represented and exchanged without loss of\n information. This is based on earlier work documented in\n RFC 934 and RFC 1049, but extends and revises that work.\n Because RFC 822 said so little about message bodies, this\n document is largely orthogonal to (rather than a revision\n of) RFC 822.\n\n In particular, this document is designed to provide\n facilities to include multiple objects in a single message,\n to represent body text in character sets other than US-\n ASCII, to represent formatted multi-font text messages, to\n represent non-textual material such as images and audio\n fragments, an","scope_keywords":["1341","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1342","folder":"IETF/RFC-1342","source":"IETF/RFC-1342/RFC-1342.txt","version":null},{"body":"IETF","designation":"RFC 1343","folder":"IETF/RFC-1343","source":"IETF/RFC-1343/RFC-1343.txt","version":null},{"body":"IETF","designation":"RFC 1344","folder":"IETF/RFC-1344","source":"IETF/RFC-1344/RFC-1344.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1425","folder":"IETF/RFC-1425","source":"IETF/RFC-1425/RFC-1425.txt","version":null},{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1437","folder":"IETF/RFC-1437","source":"IETF/RFC-1437/RFC-1437.txt","version":null},{"body":"IETF","designation":"RFC 1440","folder":"IETF/RFC-1440","source":"IETF/RFC-1440/RFC-1440.txt","version":null},{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1486","folder":"IETF/RFC-1486","source":"IETF/RFC-1486/RFC-1486.txt","version":null},{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1496","folder":"IETF/RFC-1496","source":"IETF/RFC-1496/RFC-1496.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1563","folder":"IETF/RFC-1563","source":"IETF/RFC-1563/RFC-1563.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2161","folder":"IETF/RFC-2161","source":"IETF/RFC-2161/RFC-2161.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 1341 RFC 822 defines a message representation protocol which\n specifies considerable detail about message headers, but\n which leaves the message content, or message body, as flat\n ASCII text. This document redefines the format of message\n bodies to allow multi-part textual and non-textual message\n bodies to be represented and exchanged without loss of\n information. This is based on earlier work documented in\n RFC 934 and RFC 1049, but extends and revises that work.\n Because RFC 822 said so little about message bodies, this\n document is largely orthogonal to (rather than a revision\n of) RFC 822.\n\n In particular, this document is designed to provide\n facilities to include multiple objects in a single message,\n to represent body text in character sets other than US-\n ASCII, to represent formatted multi-font text messages, to\n represent non-textual material such as images and audio\n fragments, an 1341 presentation subject nested-reference unchanged"},{"id":"IETF RFC 1521","type":"specification","body":"IETF","designation":"RFC 1521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1521.txt","https://www.rfc-editor.org/rfc/rfc1521.pdf"],"folder":"IETF/RFC-1521","files":{"pdf":{"path":"standards/IETF/RFC-1521/RFC-1521.pdf","sha256":"c46d1e004cc044d72e1c01bbdf396c214c7789b2d6f3d3cb9bb66a3e30d6d5e8"},"txt":{"path":"standards/IETF/RFC-1521/RFC-1521.txt","sha256":"375598a8927c77dafadc81477aca36b144f0f03397865a19d060ca84c371a188"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822 defines a message representation protocol which\n specifies considerable detail about message headers, but which leaves\n the message content, or message body, as flat ASCII text. This\n document redefines the format of message bodies to allow multi-part\n textual and non-textual message bodies to be represented and\n exchanged without loss of information. This is based on earlier work\n documented in RFC 934 and STD 11, RFC 1049, but extends and revises\n that work. Because RFC 822 said so little about message bodies, this\n document is largely orthogonal to (rather than a revision of) RFC\n 822.\n\n In particular, this document is designed to provide facilities to\n include multiple objects in a single message, to represent body text\n in character sets other than US-ASCII, to represent formatted multi-\n font text messages, to represent non-textual material such as images\n and audio","scope_keywords":["1521","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1522","folder":"IETF/RFC-1522","source":"IETF/RFC-1522/RFC-1522.txt","version":null},{"body":"IETF","designation":"RFC 1524","folder":"IETF/RFC-1524","source":"IETF/RFC-1524/RFC-1524.txt","version":null},{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 1557","folder":"IETF/RFC-1557","source":"IETF/RFC-1557/RFC-1557.txt","version":null},{"body":"IETF","designation":"RFC 1563","folder":"IETF/RFC-1563","source":"IETF/RFC-1563/RFC-1563.txt","version":null},{"body":"IETF","designation":"RFC 1568","folder":"IETF/RFC-1568","source":"IETF/RFC-1568/RFC-1568.txt","version":null},{"body":"IETF","designation":"RFC 1590","folder":"IETF/RFC-1590","source":"IETF/RFC-1590/RFC-1590.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1651","folder":"IETF/RFC-1651","source":"IETF/RFC-1651/RFC-1651.txt","version":null},{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1714","folder":"IETF/RFC-1714","source":"IETF/RFC-1714/RFC-1714.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1740","folder":"IETF/RFC-1740","source":"IETF/RFC-1740/RFC-1740.txt","version":null},{"body":"IETF","designation":"RFC 1766","folder":"IETF/RFC-1766","source":"IETF/RFC-1766/RFC-1766.txt","version":null},{"body":"IETF","designation":"RFC 1767","folder":"IETF/RFC-1767","source":"IETF/RFC-1767/RFC-1767.txt","version":null},{"body":"IETF","designation":"RFC 1806","folder":"IETF/RFC-1806","source":"IETF/RFC-1806/RFC-1806.txt","version":null},{"body":"IETF","designation":"RFC 1808","folder":"IETF/RFC-1808","source":"IETF/RFC-1808/RFC-1808.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1830","folder":"IETF/RFC-1830","source":"IETF/RFC-1830/RFC-1830.txt","version":null},{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1847","folder":"IETF/RFC-1847","source":"IETF/RFC-1847/RFC-1847.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1864","folder":"IETF/RFC-1864","source":"IETF/RFC-1864/RFC-1864.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1867","folder":"IETF/RFC-1867","source":"IETF/RFC-1867/RFC-1867.txt","version":null},{"body":"IETF","designation":"RFC 1869","folder":"IETF/RFC-1869","source":"IETF/RFC-1869/RFC-1869.txt","version":null},{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1872","folder":"IETF/RFC-1872","source":"IETF/RFC-1872/RFC-1872.txt","version":null},{"body":"IETF","designation":"RFC 1873","folder":"IETF/RFC-1873","source":"IETF/RFC-1873/RFC-1873.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 1892","folder":"IETF/RFC-1892","source":"IETF/RFC-1892/RFC-1892.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2017","folder":"IETF/RFC-2017","source":"IETF/RFC-2017/RFC-2017.txt","version":null},{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2111","folder":"IETF/RFC-2111","source":"IETF/RFC-2111/RFC-2111.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 1521 STD 11, RFC 822 defines a message representation protocol which\n specifies considerable detail about message headers, but which leaves\n the message content, or message body, as flat ASCII text. This\n document redefines the format of message bodies to allow multi-part\n textual and non-textual message bodies to be represented and\n exchanged without loss of information. This is based on earlier work\n documented in RFC 934 and STD 11, RFC 1049, but extends and revises\n that work. Because RFC 822 said so little about message bodies, this\n document is largely orthogonal to (rather than a revision of) RFC\n 822.\n\n In particular, this document is designed to provide facilities to\n include multiple objects in a single message, to represent body text\n in character sets other than US-ASCII, to represent formatted multi-\n font text messages, to represent non-textual material such as images\n and audio 1521 presentation subject nested-reference unchanged"},{"id":"IETF RFC 2045","type":"specification","body":"IETF","designation":"RFC 2045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2045.txt","https://www.rfc-editor.org/rfc/rfc2045.pdf"],"folder":"IETF/RFC-2045","files":{"txt":{"path":"standards/IETF/RFC-2045/RFC-2045.txt","sha256":"9bb251635dd37fda97dcce6c08dea019432117a0f1e389051d2ecbf7b76350b0"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n This initial document specifies the various head","scope_keywords":["2045","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2077","folder":"IETF/RFC-2077","source":"IETF/RFC-2077/RFC-2077.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2158","folder":"IETF/RFC-2158","source":"IETF/RFC-2158/RFC-2158.txt","version":null},{"body":"IETF","designation":"RFC 2159","folder":"IETF/RFC-2159","source":"IETF/RFC-2159/RFC-2159.txt","version":null},{"body":"IETF","designation":"RFC 2161","folder":"IETF/RFC-2161","source":"IETF/RFC-2161/RFC-2161.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2302","folder":"IETF/RFC-2302","source":"IETF/RFC-2302/RFC-2302.txt","version":null},{"body":"IETF","designation":"RFC 2306","folder":"IETF/RFC-2306","source":"IETF/RFC-2306/RFC-2306.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2392","folder":"IETF/RFC-2392","source":"IETF/RFC-2392/RFC-2392.txt","version":null},{"body":"IETF","designation":"RFC 2397","folder":"IETF/RFC-2397","source":"IETF/RFC-2397/RFC-2397.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 2779","folder":"IETF/RFC-2779","source":"IETF/RFC-2779/RFC-2779.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3250","folder":"IETF/RFC-3250","source":"IETF/RFC-3250/RFC-3250.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3310","folder":"IETF/RFC-3310","source":"IETF/RFC-3310/RFC-3310.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3516","folder":"IETF/RFC-3516","source":"IETF/RFC-3516/RFC-3516.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3839","folder":"IETF/RFC-3839","source":"IETF/RFC-3839/RFC-3839.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4073","folder":"IETF/RFC-4073","source":"IETF/RFC-4073/RFC-4073.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4155","folder":"IETF/RFC-4155","source":"IETF/RFC-4155/RFC-4155.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null}],"search_text":"IETF RFC 2045 STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n This initial document specifies the various head 2045 crl presentation nested-reference unchanged"},{"id":"IETF RFC 2046","type":"specification","body":"IETF","designation":"RFC 2046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2046.txt","https://www.rfc-editor.org/rfc/rfc2046.pdf"],"folder":"IETF/RFC-2046","files":{"txt":{"path":"standards/IETF/RFC-2046/RFC-2046.txt","sha256":"7ac4096b9263e11a704f06892638258ac1ddc0394dd75ffdc171e7b5ba0123e0"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822 defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, but which leaves\n the message content, or message body, as flat US-ASCII text. This\n set of documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n The initial document in this set, RFC 2045,","scope_keywords":["2046","attribute","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2346","folder":"IETF/RFC-2346","source":"IETF/RFC-2346/RFC-2346.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 2424","folder":"IETF/RFC-2424","source":"IETF/RFC-2424/RFC-2424.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3420","folder":"IETF/RFC-3420","source":"IETF/RFC-3420/RFC-3420.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4155","folder":"IETF/RFC-4155","source":"IETF/RFC-4155/RFC-4155.txt","version":null},{"body":"IETF","designation":"RFC 4180","folder":"IETF/RFC-4180","source":"IETF/RFC-4180/RFC-4180.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 2046 STD 11, RFC 822 defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, but which leaves\n the message content, or message body, as flat US-ASCII text. This\n set of documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n The initial document in this set, RFC 2045, 2046 attribute presentation registered nested-reference unchanged"},{"id":"IETF RFC 2047","type":"specification","body":"IETF","designation":"RFC 2047","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2047.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2047.txt","https://www.rfc-editor.org/rfc/rfc2047.pdf"],"folder":"IETF/RFC-2047","files":{"txt":{"path":"standards/IETF/RFC-2047/RFC-2047.txt","sha256":"f3b1356151ae24d616076880115c5ac0c313a88bcbe76d32d0cacf4b5f24f01d"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than US-ASCII,\n\n (2) an extensible set of different formats for non-textual message\n bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n This particular document is the third document in ","scope_keywords":["2047","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2368","folder":"IETF/RFC-2368","source":"IETF/RFC-2368/RFC-2368.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3516","folder":"IETF/RFC-3516","source":"IETF/RFC-3516/RFC-3516.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2047 STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than US-ASCII,\n\n (2) an extensible set of different formats for non-textual message\n bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n This particular document is the third document in  2047 presentation tls nested-reference unchanged"},{"id":"IETF RFC 2048","type":"specification","body":"IETF","designation":"RFC 2048","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2048.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2048.txt","https://www.rfc-editor.org/rfc/rfc2048.pdf"],"folder":"IETF/RFC-2048","files":{"txt":{"path":"standards/IETF/RFC-2048/RFC-2048.txt","sha256":"afd80d65eb2a0bf8cd34ca5c328472938fc863e10c98768a73479060d080708c"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\nFreed, et. al. Best Current Practice [Page 1]\n\f\nR","scope_keywords":["2048","algorithm","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2302","folder":"IETF/RFC-2302","source":"IETF/RFC-2302/RFC-2302.txt","version":null},{"body":"IETF","designation":"RFC 2306","folder":"IETF/RFC-2306","source":"IETF/RFC-2306/RFC-2306.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3009","folder":"IETF/RFC-3009","source":"IETF/RFC-3009/RFC-3009.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3250","folder":"IETF/RFC-3250","source":"IETF/RFC-3250/RFC-3250.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3362","folder":"IETF/RFC-3362","source":"IETF/RFC-3362/RFC-3362.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4155","folder":"IETF/RFC-4155","source":"IETF/RFC-4155/RFC-4155.txt","version":null},{"body":"IETF","designation":"RFC 4180","folder":"IETF/RFC-4180","source":"IETF/RFC-4180/RFC-4180.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null}],"search_text":"IETF RFC 2048 STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\nFreed, et. al. Best Current Practice [Page 1]\n\f\nR 2048 algorithm presentation registered nested-reference unchanged"},{"id":"IETF RFC 2049","type":"specification","body":"IETF","designation":"RFC 2049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2049.txt","https://www.rfc-editor.org/rfc/rfc2049.pdf"],"folder":"IETF/RFC-2049","files":{"txt":{"path":"standards/IETF/RFC-2049/RFC-2049.txt","sha256":"7b3f6345f7c9cfc8f46ec68ef5a651932803b83b475ba6b181d2e9993eab4600"}},"tags":["nested-reference","unchanged"],"summary":"STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n The initial document in this set, RFC 2045, spec","scope_keywords":["2049","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 2049 STD 11, RFC 822, defines a message representation protocol specifying\n considerable detail about US-ASCII message headers, and leaves the\n message content, or message body, as flat US-ASCII text. This set of\n documents, collectively called the Multipurpose Internet Mail\n Extensions, or MIME, redefines the format of messages to allow for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) an extensible set of different formats for non-textual\n message bodies,\n\n (3) multi-part message bodies, and\n\n (4) textual header information in character sets other than\n US-ASCII.\n\n These documents are based on earlier work documented in RFC 934, STD\n 11, and RFC 1049, but extends and revises them. Because RFC 822 said\n so little about message bodies, these documents are largely\n orthogonal to (rather than a revision of) RFC 822.\n\n The initial document in this set, RFC 2045, spec 2049 presentation nested-reference unchanged"},{"id":"IETF RFC 4021","type":"specification","body":"IETF","designation":"RFC 4021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4021.txt","https://www.rfc-editor.org/rfc/rfc4021.pdf"],"folder":"IETF/RFC-4021","files":{"txt":{"path":"standards/IETF/RFC-4021/RFC-4021.txt","sha256":"e3baa32dc2617ebe059e5725ddc69f034f7781a2ab38e3d71b917807190b7b10"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the initial IANA registration for permanent\n mail and MIME message header fields, per RFC 3864.","scope_keywords":["4021","delivery","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null}],"search_text":"IETF RFC 4021 This document defines the initial IANA registration for permanent\n mail and MIME message header fields, per RFC 3864. 4021 delivery key path subject nested-reference unchanged"},{"id":"IETF RFC 1050","type":"specification","body":"IETF","designation":"RFC 1050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1050.txt","https://www.rfc-editor.org/rfc/rfc1050.pdf"],"folder":"IETF/RFC-1050","files":{"txt":{"path":"standards/IETF/RFC-1050/RFC-1050.txt","sha256":"9ef0a8d80ca3a1bbd6f29c37790c2e7d3b8017d146130a1d2e0bd61fc3fa2a8b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1050 April 1988\n\n RPC: Remote Procedure Call\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems and others are\n using and is one we wish to propose for the Internet's consideration.\n This memo is not an Internet standard at this time. Distribution of\n this memo is unlimited.\n\n1. INTRODUCTION\n\n This document specifies a message protocol used in implementing Sun's\n Remote Procedure Call (RPC) package. The message protocol is\n specified with the eXternal Data Representation (XDR) language [9].\n This document assumes that the reader is familiar with XDR. It does\n not attempt to justify RPC or its uses. The paper by Birrell and\n Nelson [1] is recommended as an excellent background to and\n justification of RPC.\n\n2. TERMINOLOGY\n\n This document discusses servers, services, programs,","scope_keywords":["1050","authentication","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1057","folder":"IETF/RFC-1057","source":"IETF/RFC-1057/RFC-1057.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null}],"search_text":"IETF RFC 1050 Network Working Group Sun Microsystems, Inc.\nRequest for Comments: 1050 April 1988\n\n RPC: Remote Procedure Call\n Protocol Specification\n\nSTATUS OF THIS MEMO\n\n This RFC describes a standard that Sun Microsystems and others are\n using and is one we wish to propose for the Internet's consideration.\n This memo is not an Internet standard at this time. Distribution of\n this memo is unlimited.\n\n1. INTRODUCTION\n\n This document specifies a message protocol used in implementing Sun's\n Remote Procedure Call (RPC) package. The message protocol is\n specified with the eXternal Data Representation (XDR) language [9].\n This document assumes that the reader is familiar with XDR. It does\n not attempt to justify RPC or its uses. The paper by Birrell and\n Nelson [1] is recommended as an excellent background to and\n justification of RPC.\n\n2. TERMINOLOGY\n\n This document discusses servers, services, programs, 1050 authentication policy presentation nested-reference unchanged"},{"id":"IETF RFC 1051","type":"specification","body":"IETF","designation":"RFC 1051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1051.txt","https://www.rfc-editor.org/rfc/rfc1051.pdf"],"folder":"IETF/RFC-1051","files":{"txt":{"path":"standards/IETF/RFC-1051/RFC-1051.txt","sha256":"dc14885fa7b998be8876fdaef8855703d0611f9011b4462bd7cd2a690bc697f3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Prindeville\nRequest for Comments: 1051 McGill University\n March 1988\n\n A Standard for the Transmission of IP Datagrams\n and ARP Packets over ARCNET Networks\n\nStatus of this Memo\n\n This RFC specifies a standard protocol for the Internet community.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] and Address Resolution Protocol (ARP) [2] datagrams\n on an ARCNET [3].\n\nAcknowledgements\n\n The author wishes to express thanks to Robert Craig of the McGill\n University Computing Centre and Bruce Hughes of Datapoint Corporation\n for their generous support of facilities and information. I also\n extend my gratitude to the readers of the PCIP mailing list for their\n helpful ideas and comments.\n\nFrame Format\n\n IP and ARP datagrams are transmitted in standard ARCNET packets. As\n required b","scope_keywords":["1051","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1051 Network Working Group P. Prindeville\nRequest for Comments: 1051 McGill University\n March 1988\n\n A Standard for the Transmission of IP Datagrams\n and ARP Packets over ARCNET Networks\n\nStatus of this Memo\n\n This RFC specifies a standard protocol for the Internet community.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] and Address Resolution Protocol (ARP) [2] datagrams\n on an ARCNET [3].\n\nAcknowledgements\n\n The author wishes to express thanks to Robert Craig of the McGill\n University Computing Centre and Bruce Hughes of Datapoint Corporation\n for their generous support of facilities and information. I also\n extend my gratitude to the readers of the PCIP mailing list for their\n helpful ideas and comments.\n\nFrame Format\n\n IP and ARP datagrams are transmitted in standard ARCNET packets. As\n required b 1051 identification nested-reference unchanged"},{"id":"IETF RFC 1201","type":"specification","body":"IETF","designation":"RFC 1201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1201.txt","https://www.rfc-editor.org/rfc/rfc1201.pdf"],"folder":"IETF/RFC-1201","files":{"txt":{"path":"standards/IETF/RFC-1201/RFC-1201.txt","sha256":"4673fe357bd1091c041580986a9c8feaa8f2f6e34fc611fc0959fd7a50419f2e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Provan\nRequest for Comments: 1201 Novell, Inc.\nObsoletes: RFC 1051 February 1991\n\n Transmitting IP Traffic over ARCNET Networks\n\nStatus of this Memo\n\n This memo defines a protocol for the transmission of IP and ARP\n packets over the ARCnet Local Area Network. This RFC specifies an\n IAB standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo specifies a method of encapsulating Internet Protocol (IP)\n [1] and Address Resolution Protocol (ARP) [2] datagrams for\n transmission across ARCNET [3] using the \"ARCNET Packet Header\n Definition Standard\" [4]. This memo offers a replacement for RFC\n 1051. RFC 1051 us","scope_keywords":["1201"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1201 Network Working Group D. Provan\nRequest for Comments: 1201 Novell, Inc.\nObsoletes: RFC 1051 February 1991\n\n Transmitting IP Traffic over ARCNET Networks\n\nStatus of this Memo\n\n This memo defines a protocol for the transmission of IP and ARP\n packets over the ARCnet Local Area Network. This RFC specifies an\n IAB standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This memo specifies a method of encapsulating Internet Protocol (IP)\n [1] and Address Resolution Protocol (ARP) [2] datagrams for\n transmission across ARCNET [3] using the \"ARCNET Packet Header\n Definition Standard\" [4]. This memo offers a replacement for RFC\n 1051. RFC 1051 us 1201 nested-reference unchanged"},{"id":"IETF RFC 1052","type":"specification","body":"IETF","designation":"RFC 1052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1052.txt","https://www.rfc-editor.org/rfc/rfc1052.pdf"],"folder":"IETF/RFC-1052","files":{"txt":{"path":"standards/IETF/RFC-1052/RFC-1052.txt","sha256":"d07f89d116cbd5b5a65f9362ef3fc72e232457679ba336ce4547686f739edfc1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1052 NRI\n April 1988\n\n IAB Recommendations for the Development of\n Internet Network Management Standards\n\nStatus of this Memo\n\n This memo is intended to convey to the Internet community and other\n interested parties the recommendations of the Internet Activities\n Board (IAB) for the development of network management protocols for\n use in the TCP/IP environment. The memo does NOT, in and of itself,\n define or propose an Official Internet Protocol. It does reflect,\n however, the policy of the IAB with respect to further network\n management development in the short and the long term. Distribution\n of this memo is unlimited.\n\nBackground\n\n At the IAB meeting on 21 March 88 in videoconference, the report of\n the Ad Hoc Network Management Review Committee was reviewed. The\n recommendations of the committee were endorsed by the IAB and\n directi","scope_keywords":["1052","management","pid","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1065","folder":"IETF/RFC-1065","source":"IETF/RFC-1065/RFC-1065.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1067","folder":"IETF/RFC-1067","source":"IETF/RFC-1067/RFC-1067.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1155","folder":"IETF/RFC-1155","source":"IETF/RFC-1155/RFC-1155.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 1052 Network Working Group V. Cerf\nRequest for Comments: 1052 NRI\n April 1988\n\n IAB Recommendations for the Development of\n Internet Network Management Standards\n\nStatus of this Memo\n\n This memo is intended to convey to the Internet community and other\n interested parties the recommendations of the Internet Activities\n Board (IAB) for the development of network management protocols for\n use in the TCP/IP environment. The memo does NOT, in and of itself,\n define or propose an Official Internet Protocol. It does reflect,\n however, the policy of the IAB with respect to further network\n management development in the short and the long term. Distribution\n of this memo is unlimited.\n\nBackground\n\n At the IAB meeting on 21 March 88 in videoconference, the report of\n the Ad Hoc Network Management Review Committee was reviewed. The\n recommendations of the committee were endorsed by the IAB and\n directi 1052 management pid policy presentation nested-reference unchanged"},{"id":"IETF RFC 1065","type":"specification","body":"IETF","designation":"RFC 1065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1065.txt","https://www.rfc-editor.org/rfc/rfc1065.pdf"],"folder":"IETF/RFC-1065","files":{"txt":{"path":"standards/IETF/RFC-1065/RFC-1065.txt","sha256":"7dd83386a8a3a3c56dbc12d555d39c565ca2844a01b7526a8e2f4d062e87ee90"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1065 K. McCloghrie\n TWG\n August 1988\n\n Structure and Identification of Management Information\n for TCP/IP-based internets\n\n Table of Contents\n\n1. Status of this Memo ............................................. 1\n2. Introduction .................................................... 2\n3. Structure and Identification of Management Information........... 4\n3.1 Names .......................................................... 4\n3.1.1 DIRECTORY .................................................... 5\n3.1.2 MGMT ......................................................... 6\n3.1.3 EXPERIMENTAL ................................................. 6\n3.1.4 PRIVATE ...................................................... 7\n3.2 Syntax ......................................................... 7\n3.2.1 Primitive Types ............................................","scope_keywords":["1065","identification","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1067","folder":"IETF/RFC-1067","source":"IETF/RFC-1067/RFC-1067.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1109","folder":"IETF/RFC-1109","source":"IETF/RFC-1109/RFC-1109.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1155","folder":"IETF/RFC-1155","source":"IETF/RFC-1155/RFC-1155.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null}],"search_text":"IETF RFC 1065 Network Working Group M. Rose\nRequest for Comments: 1065 K. McCloghrie\n TWG\n August 1988\n\n Structure and Identification of Management Information\n for TCP/IP-based internets\n\n Table of Contents\n\n1. Status of this Memo ............................................. 1\n2. Introduction .................................................... 2\n3. Structure and Identification of Management Information........... 4\n3.1 Names .......................................................... 4\n3.1.1 DIRECTORY .................................................... 5\n3.1.2 MGMT ......................................................... 6\n3.1.3 EXPERIMENTAL ................................................. 6\n3.1.4 PRIVATE ...................................................... 7\n3.2 Syntax ......................................................... 7\n3.2.1 Primitive Types ............................................ 1065 identification management policies policy nested-reference unchanged"},{"id":"IETF RFC 1155","type":"specification","body":"IETF","designation":"RFC 1155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1155.txt","https://www.rfc-editor.org/rfc/rfc1155.pdf"],"folder":"IETF/RFC-1155","files":{"txt":{"path":"standards/IETF/RFC-1155/RFC-1155.txt","sha256":"f38eead109607f99301b3608e189a6dcf3e0fbdc77f55b6e282dda4264698717"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1155 Performance Systems International\nObsoletes: RFC 1065 K. McCloghrie\n Hughes LAN Systems\n May 1990\n\n Structure and Identification of Management Information\n for TCP/IP-based Internets\n\n Table of Contents\n\n1. Status of this Memo ............................................. 1\n2. Introduction .................................................... 2\n3. Structure and Identification of Management Information........... 4\n3.1 Names .......................................................... 4\n3.1.1 Directory .................................................... 5\n3.1.2 Mgmt ......................................................... 6\n3.1.3 Experimental ................................................. 6\n3.1.4 Private ...................................................... 7\n3.2 Syntax ......................................................... 7\n","scope_keywords":["1155","identification","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1161","folder":"IETF/RFC-1161","source":"IETF/RFC-1161/RFC-1161.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1224","folder":"IETF/RFC-1224","source":"IETF/RFC-1224/RFC-1224.txt","version":null},{"body":"IETF","designation":"RFC 1227","folder":"IETF/RFC-1227","source":"IETF/RFC-1227/RFC-1227.txt","version":null},{"body":"IETF","designation":"RFC 1228","folder":"IETF/RFC-1228","source":"IETF/RFC-1228/RFC-1228.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1298","folder":"IETF/RFC-1298","source":"IETF/RFC-1298/RFC-1298.txt","version":null},{"body":"IETF","designation":"RFC 1303","folder":"IETF/RFC-1303","source":"IETF/RFC-1303/RFC-1303.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1333","folder":"IETF/RFC-1333","source":"IETF/RFC-1333/RFC-1333.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1514","folder":"IETF/RFC-1514","source":"IETF/RFC-1514/RFC-1514.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null}],"search_text":"IETF RFC 1155 Network Working Group M. Rose\nRequest for Comments: 1155 Performance Systems International\nObsoletes: RFC 1065 K. McCloghrie\n Hughes LAN Systems\n May 1990\n\n Structure and Identification of Management Information\n for TCP/IP-based Internets\n\n Table of Contents\n\n1. Status of this Memo ............................................. 1\n2. Introduction .................................................... 2\n3. Structure and Identification of Management Information........... 4\n3.1 Names .......................................................... 4\n3.1.1 Directory .................................................... 5\n3.1.2 Mgmt ......................................................... 6\n3.1.3 Experimental ................................................. 6\n3.1.4 Private ...................................................... 7\n3.2 Syntax ......................................................... 7\n 1155 identification management policies policy nested-reference unchanged"},{"id":"IETF RFC 1158","type":"specification","body":"IETF","designation":"RFC 1158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1158.txt","https://www.rfc-editor.org/rfc/rfc1158.pdf"],"folder":"IETF/RFC-1158","files":{"txt":{"path":"standards/IETF/RFC-1158/RFC-1158.txt","sha256":"b5d899187928255ca35bf1ea20852e8b72c3bdff0b40d9be3e80d63fdc640cec"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose, Editor\nRequest for Comments: 1158 Performance Systems International\n May 1990\n\n Management Information Base for Network Management\n of TCP/IP-based internets:\n MIB-II\n\n1. Status of this Memo\n\n This memo defines the second version of the Management Information\n Base (MIB-II) for use with network management protocols in TCP/IP-\n based internets. In particular, together with its companion memos\n which describe the structure of management information (RFC 1155)\n along with the network management protocol (RFC 1157) for TCP/IP-\n based internets, these documents provide a simple, workable\n architecture and system for managing TCP/IP-based internets and in\n particular the Internet community.\n\n This document on MIB-II incorporates all of the technical content of\n RFC 1156 on MIB-I and extends it, without loss of compatibilty.\n However, MIB-I as described in RFC 115","scope_keywords":["1158","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1158 Network Working Group M. Rose, Editor\nRequest for Comments: 1158 Performance Systems International\n May 1990\n\n Management Information Base for Network Management\n of TCP/IP-based internets:\n MIB-II\n\n1. Status of this Memo\n\n This memo defines the second version of the Management Information\n Base (MIB-II) for use with network management protocols in TCP/IP-\n based internets. In particular, together with its companion memos\n which describe the structure of management information (RFC 1155)\n along with the network management protocol (RFC 1157) for TCP/IP-\n based internets, these documents provide a simple, workable\n architecture and system for managing TCP/IP-based internets and in\n particular the Internet community.\n\n This document on MIB-II incorporates all of the technical content of\n RFC 1156 on MIB-I and extends it, without loss of compatibilty.\n However, MIB-I as described in RFC 115 1158 identification management nested-reference unchanged"},{"id":"IETF RFC 1162","type":"specification","body":"IETF","designation":"RFC 1162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1162.txt","https://www.rfc-editor.org/rfc/rfc1162.pdf"],"folder":"IETF/RFC-1162","files":{"txt":{"path":"standards/IETF/RFC-1162/RFC-1162.txt","sha256":"057cea4b98460c2f693a929de55fc004d79916f8eed0a20c8d67cb3417f317ab"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Greg Satz\nRequest for Comments: 1162 cisco Systems, Inc.\n June 1990\n\n Connectionless Network Protocol (ISO 8473)\n and\n End System to Intermediate System (ISO 9542)\n Management Information Base\n\n Table of Contents\n\n 1. Status of this Memo .................................. 1\n 2. Historical Perspective................................ 2\n 3. Objects .............................................. 3\n 3.1 Format of Definitions ............................... 3\n 4. Object Definitions ................................... 4\n 4.1 The CLNP Group ...................................... 5\n 4.1.1 The CLNP Interfaces table ......................... 14\n 4.1.2 The CLNP Routing table ............................ 16\n 4.1.3 The CLNP Address Translation Tables ............... 22\n 4.2 The CLNP Error Group ................................ 30\n 4.3 The ESIS Group ..............................","scope_keywords":["1162","identification","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null}],"search_text":"IETF RFC 1162 Network Working Group Greg Satz\nRequest for Comments: 1162 cisco Systems, Inc.\n June 1990\n\n Connectionless Network Protocol (ISO 8473)\n and\n End System to Intermediate System (ISO 9542)\n Management Information Base\n\n Table of Contents\n\n 1. Status of this Memo .................................. 1\n 2. Historical Perspective................................ 2\n 3. Objects .............................................. 3\n 3.1 Format of Definitions ............................... 3\n 4. Object Definitions ................................... 4\n 4.1 The CLNP Group ...................................... 5\n 4.1.1 The CLNP Interfaces table ......................... 14\n 4.1.2 The CLNP Routing table ............................ 16\n 4.1.3 The CLNP Address Translation Tables ............... 22\n 4.2 The CLNP Error Group ................................ 30\n 4.3 The ESIS Group .............................. 1162 identification management subject nested-reference unchanged"},{"id":"IETF RFC 1212","type":"specification","body":"IETF","designation":"RFC 1212","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1212.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1212.txt","https://www.rfc-editor.org/rfc/rfc1212.pdf"],"folder":"IETF/RFC-1212","files":{"txt":{"path":"standards/IETF/RFC-1212/RFC-1212.txt","sha256":"5992f924c4f3e7e26eacaaa14dd166d5e0f01133da0a1341d815516979a68d25"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a straight-forward approach toward producing\n concise, yet descriptive, MIB modules. It is intended that all\n future MIB modules be written in this format.\n\n2. Historical Perspective\n\n As reported in RFC 1052, IAB Recommendations for the Development of\n Internet Network Management Standards [1], a two-prong strategy for\n network management of TCP/IP-based internets was undertaken. In the\n short-term, the Simple Network Management Protocol (SNMP), defined in\n RFC 1067, was to be used to manage nodes in the Internet community.\n In the long-term, the use of the OSI network management framework was\n to be examined. Two documents were produced to define the management\n information: RFC 1065, which defined the Structure of Management\n Information (SMI), and RFC 1066, which defined the Management\n Information Base (MIB). Both of these documents were designed so as\n to be com","scope_keywords":["1212","identification","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1227","folder":"IETF/RFC-1227","source":"IETF/RFC-1227/RFC-1227.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1255","folder":"IETF/RFC-1255","source":"IETF/RFC-1255/RFC-1255.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1303","folder":"IETF/RFC-1303","source":"IETF/RFC-1303/RFC-1303.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1514","folder":"IETF/RFC-1514","source":"IETF/RFC-1514/RFC-1514.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 1212 This memo describes a straight-forward approach toward producing\n concise, yet descriptive, MIB modules. It is intended that all\n future MIB modules be written in this format.\n\n2. Historical Perspective\n\n As reported in RFC 1052, IAB Recommendations for the Development of\n Internet Network Management Standards [1], a two-prong strategy for\n network management of TCP/IP-based internets was undertaken. In the\n short-term, the Simple Network Management Protocol (SNMP), defined in\n RFC 1067, was to be used to manage nodes in the Internet community.\n In the long-term, the use of the OSI network management framework was\n to be examined. Two documents were produced to define the management\n information: RFC 1065, which defined the Structure of Management\n Information (SMI), and RFC 1066, which defined the Management\n Information Base (MIB). Both of these documents were designed so as\n to be com 1212 identification management presentation nested-reference unchanged"},{"id":"IETF RFC 1213","type":"specification","body":"IETF","designation":"RFC 1213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1213.txt","https://www.rfc-editor.org/rfc/rfc1213.pdf"],"folder":"IETF/RFC-1213","files":{"txt":{"path":"standards/IETF/RFC-1213/RFC-1213.txt","sha256":"88056a4c7c3385ffa9c1bab173342ab4fd98834995269145eb7c2a4b38d80bac"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the second version of the Management Information\n Base (MIB-II) for use with network management protocols in TCP/IP-\n based internets. In particular, together with its companion memos\n which describe the structure of management information (RFC 1155)\n along with the network management protocol (RFC 1157) for TCP/IP-\n based internets, these documents provide a simple, workable\n architecture and system for managing TCP/IP-based internets and in\n particular the Internet community.\n\n2. Introduction\n\n As reported in RFC 1052, IAB Recommendations for the Development of\n Internet Network Management Standards [1], a two-prong strategy for\n network management of TCP/IP-based internets was undertaken. In the\n short-term, the Simple Network Management Protocol (SNMP) was to be\n used to manage nodes in the Internet community. In the long-term,\n the use of the OSI network management","scope_keywords":["1213","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1212","folder":"IETF/RFC-1212","source":"IETF/RFC-1212/RFC-1212.txt","version":null},{"body":"IETF","designation":"RFC 1215","folder":"IETF/RFC-1215","source":"IETF/RFC-1215/RFC-1215.txt","version":null},{"body":"IETF","designation":"RFC 1224","folder":"IETF/RFC-1224","source":"IETF/RFC-1224/RFC-1224.txt","version":null},{"body":"IETF","designation":"RFC 1229","folder":"IETF/RFC-1229","source":"IETF/RFC-1229/RFC-1229.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1232","folder":"IETF/RFC-1232","source":"IETF/RFC-1232/RFC-1232.txt","version":null},{"body":"IETF","designation":"RFC 1233","folder":"IETF/RFC-1233","source":"IETF/RFC-1233/RFC-1233.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1243","folder":"IETF/RFC-1243","source":"IETF/RFC-1243/RFC-1243.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1285","folder":"IETF/RFC-1285","source":"IETF/RFC-1285/RFC-1285.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1289","folder":"IETF/RFC-1289","source":"IETF/RFC-1289/RFC-1289.txt","version":null},{"body":"IETF","designation":"RFC 1303","folder":"IETF/RFC-1303","source":"IETF/RFC-1303/RFC-1303.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1333","folder":"IETF/RFC-1333","source":"IETF/RFC-1333/RFC-1333.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null},{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1450","folder":"IETF/RFC-1450","source":"IETF/RFC-1450/RFC-1450.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1512","folder":"IETF/RFC-1512","source":"IETF/RFC-1512/RFC-1512.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1514","folder":"IETF/RFC-1514","source":"IETF/RFC-1514/RFC-1514.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1566","folder":"IETF/RFC-1566","source":"IETF/RFC-1566/RFC-1566.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1586","folder":"IETF/RFC-1586","source":"IETF/RFC-1586/RFC-1586.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1665","folder":"IETF/RFC-1665","source":"IETF/RFC-1665/RFC-1665.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1696","folder":"IETF/RFC-1696","source":"IETF/RFC-1696/RFC-1696.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2012","folder":"IETF/RFC-2012","source":"IETF/RFC-2012/RFC-2012.txt","version":null},{"body":"IETF","designation":"RFC 2013","folder":"IETF/RFC-2013","source":"IETF/RFC-2013/RFC-2013.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2039","folder":"IETF/RFC-2039","source":"IETF/RFC-2039/RFC-2039.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2206","folder":"IETF/RFC-2206","source":"IETF/RFC-2206/RFC-2206.txt","version":null},{"body":"IETF","designation":"RFC 2213","folder":"IETF/RFC-2213","source":"IETF/RFC-2213/RFC-2213.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2325","folder":"IETF/RFC-2325","source":"IETF/RFC-2325/RFC-2325.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null}],"search_text":"IETF RFC 1213 This memo defines the second version of the Management Information\n Base (MIB-II) for use with network management protocols in TCP/IP-\n based internets. In particular, together with its companion memos\n which describe the structure of management information (RFC 1155)\n along with the network management protocol (RFC 1157) for TCP/IP-\n based internets, these documents provide a simple, workable\n architecture and system for managing TCP/IP-based internets and in\n particular the Internet community.\n\n2. Introduction\n\n As reported in RFC 1052, IAB Recommendations for the Development of\n Internet Network Management Standards [1], a two-prong strategy for\n network management of TCP/IP-based internets was undertaken. In the\n short-term, the Simple Network Management Protocol (SNMP) was to be\n used to manage nodes in the Internet community. In the long-term,\n the use of the OSI network management 1213 identification management nested-reference unchanged"},{"id":"IETF RFC 1215","type":"specification","body":"IETF","designation":"RFC 1215","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1215.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1215.txt","https://www.rfc-editor.org/rfc/rfc1215.pdf"],"folder":"IETF/RFC-1215","files":{"txt":{"path":"standards/IETF/RFC-1215/RFC-1215.txt","sha256":"5c9b44e6607e5fe524635fe7f659bc2bbede3ae31c4e488b374582ce08a33d21"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose, Editor\nRequest for Comments: 1215 Performance Systems International\n March 1991\n\n A Convention for Defining Traps\n for use with the SNMP\n\nStatus of this Memo\n\n This memo suggests a straight-forward approach towards defining traps\n used with the SNMP. Readers should note that the use of traps in the\n Internet-standard network management framework is controversial. As\n such, this memo is being put forward for information purposes.\n Network management practitioners who employ traps are encouraged to\n make use of this document. Practitioners who do not employ traps can\n safely ignore this document.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Historical Perspective ................................ 1\n 2. Defining Traps ..............................","scope_keywords":["1215","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1271","folder":"IETF/RFC-1271","source":"IETF/RFC-1271/RFC-1271.txt","version":null},{"body":"IETF","designation":"RFC 1286","folder":"IETF/RFC-1286","source":"IETF/RFC-1286/RFC-1286.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1315","folder":"IETF/RFC-1315","source":"IETF/RFC-1315/RFC-1315.txt","version":null},{"body":"IETF","designation":"RFC 1316","folder":"IETF/RFC-1316","source":"IETF/RFC-1316/RFC-1316.txt","version":null},{"body":"IETF","designation":"RFC 1317","folder":"IETF/RFC-1317","source":"IETF/RFC-1317/RFC-1317.txt","version":null},{"body":"IETF","designation":"RFC 1318","folder":"IETF/RFC-1318","source":"IETF/RFC-1318/RFC-1318.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1493","folder":"IETF/RFC-1493","source":"IETF/RFC-1493/RFC-1493.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 1525","folder":"IETF/RFC-1525","source":"IETF/RFC-1525/RFC-1525.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2579","folder":"IETF/RFC-2579","source":"IETF/RFC-2579/RFC-2579.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 1215 Network Working Group M. Rose, Editor\nRequest for Comments: 1215 Performance Systems International\n March 1991\n\n A Convention for Defining Traps\n for use with the SNMP\n\nStatus of this Memo\n\n This memo suggests a straight-forward approach towards defining traps\n used with the SNMP. Readers should note that the use of traps in the\n Internet-standard network management framework is controversial. As\n such, this memo is being put forward for information purposes.\n Network management practitioners who employ traps are encouraged to\n make use of this document. Practitioners who do not employ traps can\n safely ignore this document.\n\n This memo provides information for the Internet community. It does\n not specify any standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Historical Perspective ................................ 1\n 2. Defining Traps .............................. 1215 identification management nested-reference unchanged"},{"id":"IETF RFC 1232","type":"specification","body":"IETF","designation":"RFC 1232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1232.txt","https://www.rfc-editor.org/rfc/rfc1232.pdf"],"folder":"IETF/RFC-1232","files":{"txt":{"path":"standards/IETF/RFC-1232/RFC-1232.txt","sha256":"ebdb1ed90875bedf236eb0a1b7443383b5644353980b212d11ec4b0c49119ba7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines MIB objects\n\nTransmission MIB Working Group [Page 1]\n\f\nRFC 1232 DS1 Interface Objects May 1991\n\n for representing DS1 physical interfaces. Implementors should\n consult in addition to this memo the companion document that\n describes that DS3 managed objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC ","scope_keywords":["1232","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1406","folder":"IETF/RFC-1406","source":"IETF/RFC-1406/RFC-1406.txt","version":null}],"search_text":"IETF RFC 1232 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines MIB objects\n\nTransmission MIB Working Group [Page 1]\n\f\nRFC 1232 DS1 Interface Objects May 1991\n\n for representing DS1 physical interfaces. Implementors should\n consult in addition to this memo the companion document that\n describes that DS3 managed objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC  1232 key management subject nested-reference unchanged"},{"id":"IETF RFC 1233","type":"specification","body":"IETF","designation":"RFC 1233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1233.txt","https://www.rfc-editor.org/rfc/rfc1233.pdf"],"folder":"IETF/RFC-1233","files":{"txt":{"path":"standards/IETF/RFC-1233/RFC-1233.txt","sha256":"5f405ab6a68208437b820a3bacc020ce8c40f7051a5cbb90a111aa25ef86e46e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines MIB objects\n for representing DS3 physical interfaces. Implementors should\n consult in addition to this memo the companion document that\n\nSNMP & Transmission MIB Working Groups [Page 1]\n\f\nRFC 1233 DS3 Interface Objects May 1991\n\n describes that DS1 managed objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protoco","scope_keywords":["1233","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1239","folder":"IETF/RFC-1239","source":"IETF/RFC-1239/RFC-1239.txt","version":null},{"body":"IETF","designation":"RFC 1304","folder":"IETF/RFC-1304","source":"IETF/RFC-1304/RFC-1304.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1407","folder":"IETF/RFC-1407","source":"IETF/RFC-1407/RFC-1407.txt","version":null}],"search_text":"IETF RFC 1233 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. In particular, this memo defines MIB objects\n for representing DS3 physical interfaces. Implementors should\n consult in addition to this memo the companion document that\n\nSNMP & Transmission MIB Working Groups [Page 1]\n\f\nRFC 1233 DS3 Interface Objects May 1991\n\n describes that DS1 managed objects.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protoco 1233 key management subject nested-reference unchanged"},{"id":"IETF RFC 1238","type":"specification","body":"IETF","designation":"RFC 1238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1238.txt","https://www.rfc-editor.org/rfc/rfc1238.pdf"],"folder":"IETF/RFC-1238","files":{"txt":{"path":"standards/IETF/RFC-1238/RFC-1238.txt","sha256":"3adf0ab9d6fbe07e6a5f19fe434e06c05b1d78598bfcaeca71afe06225b1d188"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Satz\nRequest for Comments: 1238 cisco Systems, Inc.\nObsoletes: RFC 1162 June 1991\n\n CLNS MIB\n for use with\n Connectionless Network Protocol (ISO 8473)\n and\n End System to Intermediate System (ISO 9542)\n\nStatus of this Memo\n\n This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. This is an Experimental Protocol for the\n Internet community. Discussion and suggestions for improvement are\n requested. Please refer to the current edition of the \"IAB Official\n Protocol Standards\" for the standardization state and status of this\n protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. The Network Management Framework....................... 1\n 2. Objects ............................................... 2\n 2.1 Format of Definitions ..........................","scope_keywords":["1238","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1238 Network Working Group G. Satz\nRequest for Comments: 1238 cisco Systems, Inc.\nObsoletes: RFC 1162 June 1991\n\n CLNS MIB\n for use with\n Connectionless Network Protocol (ISO 8473)\n and\n End System to Intermediate System (ISO 9542)\n\nStatus of this Memo\n\n This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n TCP/IP-based internets. This is an Experimental Protocol for the\n Internet community. Discussion and suggestions for improvement are\n requested. Please refer to the current edition of the \"IAB Official\n Protocol Standards\" for the standardization state and status of this\n protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. The Network Management Framework....................... 1\n 2. Objects ............................................... 2\n 2.1 Format of Definitions .......................... 1238 management subject nested-reference unchanged"},{"id":"IETF RFC 1243","type":"specification","body":"IETF","designation":"RFC 1243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1243.txt","https://www.rfc-editor.org/rfc/rfc1243.pdf"],"folder":"IETF/RFC-1243","files":{"txt":{"path":"standards/IETF/RFC-1243/RFC-1243.txt","sha256":"dadf8e3cc175ab7309834e9d8969bd9cb2a6bfc34e4158715e56fbdcc01d335e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing AppleTalk networks.\n\nAppleTalk-IP Working Group [Page 1]\n\f\nRFC 1243 AppleTalk MIB July 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol use","scope_keywords":["1243","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1419","folder":"IETF/RFC-1419","source":"IETF/RFC-1419/RFC-1419.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1906","folder":"IETF/RFC-1906","source":"IETF/RFC-1906/RFC-1906.txt","version":null}],"search_text":"IETF RFC 1243 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing AppleTalk networks.\n\nAppleTalk-IP Working Group [Page 1]\n\f\nRFC 1243 AppleTalk MIB July 1991\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol use 1243 delivery management subject nested-reference unchanged"},{"id":"IETF RFC 1269","type":"specification","body":"IETF","designation":"RFC 1269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1269.txt","https://www.rfc-editor.org/rfc/rfc1269.pdf"],"folder":"IETF/RFC-1269","files":{"txt":{"path":"standards/IETF/RFC-1269/RFC-1269.txt","sha256":"452323f49807a89f16d837955c6777e4281a3e7c497850a2075bc6f35974b3c7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Border Gateway\n Protocol [11,12].\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framew","scope_keywords":["1269","attribute","attributes","authentication","management","path","pid","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null}],"search_text":"IETF RFC 1269 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Border Gateway\n Protocol [11,12].\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framew 1269 attribute attributes authentication management path pid policy subject nested-reference unchanged"},{"id":"IETF RFC 1270","type":"specification","body":"IETF","designation":"RFC 1270","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1270.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1270.txt","https://www.rfc-editor.org/rfc/rfc1270.pdf"],"folder":"IETF/RFC-1270","files":{"txt":{"path":"standards/IETF/RFC-1270/RFC-1270.txt","sha256":"13a81ad08e51bb19eafeb6fb25ea5df737c7c65b882bfc526434b383ecfdaa6c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz, Editor\nRequest for Comments: 1270 Clearpoint Research Corporation\n October 1991\n\n SNMP Communications Services\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Abstract .............................................. 1\n 2. Introduction .......................................... 1\n 3. Standardization ....................................... 3\n 4. Interoperability ...................................... 3\n 5. To Transport or Not To Transport ...................... 3\n 6. Connection Oriented vs. Connectionless ................ 6\n 7. Which Protocol ........................................ 8\n 8. Security Considerations ............................... 9\n 9. Appendix .............................................. 9\n 10. Ref","scope_keywords":["1270","driving","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1298","folder":"IETF/RFC-1298","source":"IETF/RFC-1298/RFC-1298.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null}],"search_text":"IETF RFC 1270 Network Working Group F. Kastenholz, Editor\nRequest for Comments: 1270 Clearpoint Research Corporation\n October 1991\n\n SNMP Communications Services\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Abstract .............................................. 1\n 2. Introduction .......................................... 1\n 3. Standardization ....................................... 3\n 4. Interoperability ...................................... 3\n 5. To Transport or Not To Transport ...................... 3\n 6. Connection Oriented vs. Connectionless ................ 6\n 7. Which Protocol ........................................ 8\n 8. Security Considerations ............................... 9\n 9. Appendix .............................................. 9\n 10. Ref 1270 driving identification management nested-reference unchanged"},{"id":"IETF RFC 1271","type":"specification","body":"IETF","designation":"RFC 1271","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1271.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1271.txt","https://www.rfc-editor.org/rfc/rfc1271.pdf"],"folder":"IETF/RFC-1271","files":{"txt":{"path":"standards/IETF/RFC-1271/RFC-1271.txt","sha256":"45af9a5ebf8790e83b91aeaacf70e52d862dddbc0f597f0cb534b2bb626f65e3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framewor","scope_keywords":["1271","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1513","folder":"IETF/RFC-1513","source":"IETF/RFC-1513/RFC-1513.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null}],"search_text":"IETF RFC 1271 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing remote network\n monitoring devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212\n defines a more concise description mechanism, which is wholly\n consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for\n the Internet suite of protocols. RFC 1213, defines MIB-II, an\n evolution of MIB-I based on implementation experience and new\n operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network\n access to managed objects.\n\n The Framewor 1271 management subject nested-reference unchanged"},{"id":"IETF RFC 1289","type":"specification","body":"IETF","designation":"RFC 1289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1289.txt","https://www.rfc-editor.org/rfc/rfc1289.pdf"],"folder":"IETF/RFC-1289","files":{"txt":{"path":"standards/IETF/RFC-1289/RFC-1289.txt","sha256":"8ddd8c17df6d8e32e7e6cd812c4c2d201547827c588b8dfc852ba824dba643ac"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of DECnet Phase IV extensions that have been\n created for the Internet MIB. When used in conjunction with the\n structure of management information (RFC 1155), the management\n information base for network management of TCP/IP-based internets\n (RFC 1213) and the Simple Network Management Protocol (RFC 1157), it\n will be possible to provide integrated network management of combined\n TCP/IP and DECnet Phase IV based internets. This document was\n produced by the DECnet Phase IV MIB working group of the Internet\n Engineering Task Force (IETF).\n\n1. Introduction\n\n With the adoption of The Simple Network Management Protocol (RFC\n 1157), the management information base for network management of\n TCP/IP-based internets (RFC 1213), and the structure of management\n information (RFC 1155), by the Internet, and a large number of vendor\n\nDECnet Phase IV MIB Working Group [Page 1]","scope_keywords":["1289","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1559","folder":"IETF/RFC-1559","source":"IETF/RFC-1559/RFC-1559.txt","version":null}],"search_text":"IETF RFC 1289 This memo defines a set of DECnet Phase IV extensions that have been\n created for the Internet MIB. When used in conjunction with the\n structure of management information (RFC 1155), the management\n information base for network management of TCP/IP-based internets\n (RFC 1213) and the Simple Network Management Protocol (RFC 1157), it\n will be possible to provide integrated network management of combined\n TCP/IP and DECnet Phase IV based internets. This document was\n produced by the DECnet Phase IV MIB working group of the Internet\n Engineering Task Force (IETF).\n\n1. Introduction\n\n With the adoption of The Simple Network Management Protocol (RFC\n 1157), the management information base for network management of\n TCP/IP-based internets (RFC 1213), and the structure of management\n information (RFC 1155), by the Internet, and a large number of vendor\n\nDECnet Phase IV MIB Working Group [Page 1] 1289 key management nested-reference unchanged"},{"id":"IETF RFC 1304","type":"specification","body":"IETF","designation":"RFC 1304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1304.txt","https://www.rfc-editor.org/rfc/rfc1304.pdf"],"folder":"IETF/RFC-1304","files":{"txt":{"path":"standards/IETF/RFC-1304/RFC-1304.txt","sha256":"d2bfefa63a08d290e48c841f0d6709c62355046b87597d8e46718d8cc4debd6d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing SIP (SMDS Interface\n Protocol) objects.","scope_keywords":["1304","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1304 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing SIP (SMDS Interface\n Protocol) objects. 1304 management subject nested-reference unchanged"},{"id":"IETF RFC 1315","type":"specification","body":"IETF","designation":"RFC 1315","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1315.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1315.txt","https://www.rfc-editor.org/rfc/rfc1315.pdf"],"folder":"IETF/RFC-1315","files":{"txt":{"path":"standards/IETF/RFC-1315/RFC-1315.txt","sha256":"5718153717d6d65bdaa7c425c43dbf611ee29eac55e42eb2c55a56466a6986cc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Frame Relay.","scope_keywords":["1315","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null}],"search_text":"IETF RFC 1315 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Frame Relay. 1315 management subject nested-reference unchanged"},{"id":"IETF RFC 1316","type":"specification","body":"IETF","designation":"RFC 1316","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1316.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1316.txt","https://www.rfc-editor.org/rfc/rfc1316.pdf"],"folder":"IETF/RFC-1316","files":{"txt":{"path":"standards/IETF/RFC-1316/RFC-1316.txt","sha256":"04bb5b26d5148a2b8bea1faf2693469040293b523dc4d858faad9950cdb5ad78"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for the management of character\n stream devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212 defines a\n more concise description mechanism, which is wholly consistent with\n the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for the\n Internet suite of protocols. RFC 1213, defines MIB-II, an evolution\n of MIB-I based on implementation experience and new operational\n requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network access\n to managed objects.\n\n The Framework","scope_keywords":["1316","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null}],"search_text":"IETF RFC 1316 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for the management of character\n stream devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212 defines a\n more concise description mechanism, which is wholly consistent with\n the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for the\n Internet suite of protocols. RFC 1213, defines MIB-II, an evolution\n of MIB-I based on implementation experience and new operational\n requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network access\n to managed objects.\n\n The Framework 1316 management subject nested-reference unchanged"},{"id":"IETF RFC 1317","type":"specification","body":"IETF","designation":"RFC 1317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1317.txt","https://www.rfc-editor.org/rfc/rfc1317.pdf"],"folder":"IETF/RFC-1317","files":{"txt":{"path":"standards/IETF/RFC-1317/RFC-1317.txt","sha256":"e984c84c921a5b5d28c991f66dee1e7619355ce5c7e37e16726259756b1a3f95"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for the management of RS-232-like\n devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212 defines a\n more concise description mechanism, which is wholly consistent with\n the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for the\n Internet suite of protocols. RFC 1213, defines MIB-II, an evolution\n of MIB-I based on implementation experience and new operational\n requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network access\n to managed objects.\n\n The Framework per","scope_keywords":["1317","attribute","attributes","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1317 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for the management of RS-232-like\n devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists of three\n components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for describing\n and naming objects for the purpose of management. RFC 1212 defines a\n more concise description mechanism, which is wholly consistent with\n the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed objects for the\n Internet suite of protocols. RFC 1213, defines MIB-II, an evolution\n of MIB-I based on implementation experience and new operational\n requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for network access\n to managed objects.\n\n The Framework per 1317 attribute attributes management subject nested-reference unchanged"},{"id":"IETF RFC 1318","type":"specification","body":"IETF","designation":"RFC 1318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1318.txt","https://www.rfc-editor.org/rfc/rfc1318.pdf"],"folder":"IETF/RFC-1318","files":{"txt":{"path":"standards/IETF/RFC-1318/RFC-1318.txt","sha256":"aa11f80e3bfac014e0200cf6d58fd33bb1c50c9a3863006a85037ea982dc660d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for the management of\n parallel-printer-like devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists\n of three components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for\n describing and naming objects for the purpose of management.\n RFC 1212 defines a more concise description mechanism, which\n is wholly consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed\n objects for the Internet suite of protocols. RFC 1213,\n defines MIB-II, an evolution of MIB-I based on\n implementation experience and new operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for\n network access to managed objects.\n\n The Fra","scope_keywords":["1318","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null}],"search_text":"IETF RFC 1318 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for the management of\n parallel-printer-like devices.\n\n2. The Network Management Framework\n\n The Internet-standard Network Management Framework consists\n of three components. They are:\n\n RFC 1155 which defines the SMI, the mechanisms used for\n describing and naming objects for the purpose of management.\n RFC 1212 defines a more concise description mechanism, which\n is wholly consistent with the SMI.\n\n RFC 1156 which defines MIB-I, the core set of managed\n objects for the Internet suite of protocols. RFC 1213,\n defines MIB-II, an evolution of MIB-I based on\n implementation experience and new operational requirements.\n\n RFC 1157 which defines the SNMP, the protocol used for\n network access to managed objects.\n\n The Fra 1318 management subject nested-reference unchanged"},{"id":"IETF RFC 1354","type":"specification","body":"IETF","designation":"RFC 1354","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1354.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1354.txt","https://www.rfc-editor.org/rfc/rfc1354.pdf"],"folder":"IETF/RFC-1354","files":{"txt":{"path":"standards/IETF/RFC-1354/RFC-1354.txt","sha256":"4e592b775abb89f32d902eb368e8c8fa637877762ede781bc1fcd1bb0957ae20"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing routes in the IP\n Internet.\n\n It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be\n deprecated and replaced with this table. This adds the ability to\n set or display multi-path routes, and varying routes by network\n management policy.","scope_keywords":["1354","management","path","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null}],"search_text":"IETF RFC 1354 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing routes in the IP\n Internet.\n\n It is proposed that the ipRouteTable defined by MIB-II (RFC 1213) be\n deprecated and replaced with this table. This adds the ability to\n set or display multi-path routes, and varying routes by network\n management policy. 1354 management path policy subject nested-reference unchanged"},{"id":"IETF RFC 1389","type":"specification","body":"IETF","designation":"RFC 1389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1389.txt","https://www.rfc-editor.org/rfc/rfc1389.pdf"],"folder":"IETF/RFC-1389","files":{"txt":{"path":"standards/IETF/RFC-1389/RFC-1389.txt","sha256":"f51d711d1e8a894a2b4ffe67dd531742a25ccc2a317283924dbf3df6eba7a4df"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing RIP Version 2.","scope_keywords":["1389","management","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1387","folder":"IETF/RFC-1387","source":"IETF/RFC-1387/RFC-1387.txt","version":null},{"body":"IETF","designation":"RFC 1388","folder":"IETF/RFC-1388","source":"IETF/RFC-1388/RFC-1388.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2453","folder":"IETF/RFC-2453","source":"IETF/RFC-2453/RFC-2453.txt","version":null}],"search_text":"IETF RFC 1389 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing RIP Version 2. 1389 management subject validation nested-reference unchanged"},{"id":"IETF RFC 1407","type":"specification","body":"IETF","designation":"RFC 1407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1407.txt","https://www.rfc-editor.org/rfc/rfc1407.pdf"],"folder":"IETF/RFC-1407","files":{"txt":{"path":"standards/IETF/RFC-1407/RFC-1407.txt","sha256":"a14f3428106dfb752d0f4b417fc147e622ea8261d277fdfc83c8f2a9f23d1b05"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing DS3 and E3\n Interfaces. This document is a companion document with Definitions\n of Managed Objects for the DS1 Interface Type.\n\n This document entirely replaces RFC 1233, which contains a\n fundamental error: many objects are encoded as Counters that must be\n encoded as INTEGERs or Gauges. The magnitude of the change required\n is sufficient that virtually every object changed. Therefore, the\n MIB documented in RFC 1233 should not be implemented.","scope_keywords":["1407","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null}],"search_text":"IETF RFC 1407 This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing DS3 and E3\n Interfaces. This document is a companion document with Definitions\n of Managed Objects for the DS1 Interface Type.\n\n This document entirely replaces RFC 1233, which contains a\n fundamental error: many objects are encoded as Counters that must be\n encoded as INTEGERs or Gauges. The magnitude of the change required\n is sufficient that virtually every object changed. Therefore, the\n MIB documented in RFC 1233 should not be implemented. 1407 management subject nested-reference unchanged"},{"id":"IETF RFC 1559","type":"specification","body":"IETF","designation":"RFC 1559","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1559.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1559.txt","https://www.rfc-editor.org/rfc/rfc1559.pdf"],"folder":"IETF/RFC-1559","files":{"txt":{"path":"standards/IETF/RFC-1559/RFC-1559.txt","sha256":"ec10ee6143e3f6f5fc702626046d0dd8178add367628d889e69858260f899512"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Saperia\nRequest for Comments: 1559 Digital Equipment Corporation\nObsoletes: 1289 December 1993\nCategory: Standards Track\n\n DECnet Phase IV MIB Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. The Network Management Framework ............................ 2\n 2.1 Object Definitions ......................................... 2\n 3. Selected Objects ............................................ 3\n 4. Textual Conventions ......................................... ","scope_keywords":["1559","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1559 Network Working Group J. Saperia\nRequest for Comments: 1559 Digital Equipment Corporation\nObsoletes: 1289 December 1993\nCategory: Standards Track\n\n DECnet Phase IV MIB Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. The Network Management Framework ............................ 2\n 2.1 Object Definitions ......................................... 2\n 3. Selected Objects ............................................ 3\n 4. Textual Conventions .........................................  1559 management nested-reference unchanged"},{"id":"IETF RFC 1724","type":"specification","body":"IETF","designation":"RFC 1724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1724.txt","https://www.rfc-editor.org/rfc/rfc1724.pdf"],"folder":"IETF/RFC-1724","files":{"txt":{"path":"standards/IETF/RFC-1724/RFC-1724.txt","sha256":"48df37c8726485d35e8a0a4d80a8f599a3a6745ff9c27619460d680e93ca7da2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing RIP Version 2.\n\nAcknowledgements\n\n The authors would like to thank the IETF ripv2 Working Group for\n their help in improving the RIP-2 MIB extension.","scope_keywords":["1724","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null}],"search_text":"IETF RFC 1724 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing RIP Version 2.\n\nAcknowledgements\n\n The authors would like to thank the IETF ripv2 Working Group for\n their help in improving the RIP-2 MIB extension. 1724 management subject nested-reference unchanged"},{"id":"IETF RFC 1742","type":"specification","body":"IETF","designation":"RFC 1742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1742.txt","https://www.rfc-editor.org/rfc/rfc1742.pdf"],"folder":"IETF/RFC-1742","files":{"txt":{"path":"standards/IETF/RFC-1742/RFC-1742.txt","sha256":"cf174c7918e914533476107ab812e02d8041985f9fae6ae0d41e29c5f5de813f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing AppleTalk networks.\n\n RFC 1243 defines a set of MIB objects for managing the lower layers\n of the AppleTalk protocol stack, up to the Network layer. This memo\n defines additional objects that exist in the AppleTalk portion of the\n MIB. These objects provide for the management of the transport and\n session layers of the AppleTalk protocol stack, as well as extensions\n to the lower layers. This is achieved in an upwardly-compatable\n fashion.","scope_keywords":["1742","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1742 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing AppleTalk networks.\n\n RFC 1243 defines a set of MIB objects for managing the lower layers\n of the AppleTalk protocol stack, up to the Network layer. This memo\n defines additional objects that exist in the AppleTalk portion of the\n MIB. These objects provide for the management of the transport and\n session layers of the AppleTalk protocol stack, as well as extensions\n to the lower layers. This is achieved in an upwardly-compatable\n fashion. 1742 delivery management nested-reference unchanged"},{"id":"IETF RFC 2570","type":"specification","body":"IETF","designation":"RFC 2570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2570.txt","https://www.rfc-editor.org/rfc/rfc2570.pdf"],"folder":"IETF/RFC-2570","files":{"txt":{"path":"standards/IETF/RFC-2570/RFC-2570.txt","sha256":"fb248cc67efaf63225d0d60aaa15474a8b7cc6b08eda4b58da4219dc7d3e7442"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to provide an overview of the third\n version of the Internet-standard Management Framework, termed the\n SNMP version 3 Framework (SNMPv3). This Framework is derived from\n and builds upon both the original Internet-standard Management\n Framework (SNMPv1) and the second Internet-standard Management\n Framework (SNMPv2).\n\n The architecture is designed to be modular to allow the evolution of\n the Framework over time.","scope_keywords":["2570","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 2570 The purpose of this document is to provide an overview of the third\n version of the Internet-standard Management Framework, termed the\n SNMP version 3 Framework (SNMPv3). This Framework is derived from\n and builds upon both the original Internet-standard Management\n Framework (SNMPv1) and the second Internet-standard Management\n Framework (SNMPv2).\n\n The architecture is designed to be modular to allow the evolution of\n the Framework over time. 2570 management nested-reference unchanged"},{"id":"IETF RFC 3410","type":"specification","body":"IETF","designation":"RFC 3410","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3410.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3410.txt","https://www.rfc-editor.org/rfc/rfc3410.pdf"],"folder":"IETF/RFC-3410","files":{"txt":{"path":"standards/IETF/RFC-3410/RFC-3410.txt","sha256":"4d81550bd50bfd70ebb8ce465463ed69bc13cf1c867afa465b2230f95754dae7"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to provide an overview of the third\n version of the Internet-Standard Management Framework, termed the\n SNMP version 3 Framework (SNMPv3). This Framework is derived from\n and builds upon both the original Internet-Standard Management\n Framework (SNMPv1) and the second Internet-Standard Management\n Framework (SNMPv2).\n\n The architecture is designed to be modular to allow the evolution of\n the Framework over time.\n\n The document explains why using SNMPv3 instead of SNMPv1 or SNMPv2 is\n strongly recommended. The document also recommends that RFCs 1157,\n 1441, 1901, 1909 and 1910 be retired by moving them to Historic\n status. This document obsoletes RFC 2570.\n\nCase, et. al. Informational [Page 1]\n\f\nRFC 3410 Applicability Statements for SNMP December 2002","scope_keywords":["3410","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3535","folder":"IETF/RFC-3535","source":"IETF/RFC-3535/RFC-3535.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3595","folder":"IETF/RFC-3595","source":"IETF/RFC-3595/RFC-3595.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null}],"search_text":"IETF RFC 3410 The purpose of this document is to provide an overview of the third\n version of the Internet-Standard Management Framework, termed the\n SNMP version 3 Framework (SNMPv3). This Framework is derived from\n and builds upon both the original Internet-Standard Management\n Framework (SNMPv1) and the second Internet-Standard Management\n Framework (SNMPv2).\n\n The architecture is designed to be modular to allow the evolution of\n the Framework over time.\n\n The document explains why using SNMPv3 instead of SNMPv1 or SNMPv2 is\n strongly recommended. The document also recommends that RFCs 1157,\n 1441, 1901, 1909 and 1910 be retired by moving them to Historic\n status. This document obsoletes RFC 2570.\n\nCase, et. al. Informational [Page 1]\n\f\nRFC 3410 Applicability Statements for SNMP December 2002 3410 key management nested-reference unchanged"},{"id":"IETF RFC 1053","type":"specification","body":"IETF","designation":"RFC 1053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1053.txt","https://www.rfc-editor.org/rfc/rfc1053.pdf"],"folder":"IETF/RFC-1053","files":{"txt":{"path":"standards/IETF/RFC-1053/RFC-1053.txt","sha256":"2526b48e109c592f4c76a57745a3dec140ffc0671272df4a13c59e1f6f3a772e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Levy\nRequest for Comments: 1053 T. Jacobson\n Minnesota Supercomputer Center\n April 1988\n\n Telnet X.3 PAD Option\n\nStatus of this Memo\n\n This RFC proposes a new option to Telnet for the Internet community,\n and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Command name and code\n\n X.3-PAD 30\n\n2. Command meanings\n\n IAC DO X.3-PAD\n\n The issuing telnet requests that its peer perform X.3-PAD\n functions, or accepts an offer to do so.\n\n IAC DON'T X.3-PAD\n\n The issuing telnet demands that its peer not perform or cease\n performing X.3-PAD functions.\n\n IAC WILL X.3-PAD\n\n The issuing telnet offers to perform X.3-PAD functions or confirms\n that it will do so.\n\n IAC WON'T X.3-PAD\n\n The issuing telnet refuses to perform X.3-PAD functions or\n indicates that it is ceasing to handle them.\n\n Typically a server (host) telnet will u","scope_keywords":["1053"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1053 Network Working Group S. Levy\nRequest for Comments: 1053 T. Jacobson\n Minnesota Supercomputer Center\n April 1988\n\n Telnet X.3 PAD Option\n\nStatus of this Memo\n\n This RFC proposes a new option to Telnet for the Internet community,\n and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Command name and code\n\n X.3-PAD 30\n\n2. Command meanings\n\n IAC DO X.3-PAD\n\n The issuing telnet requests that its peer perform X.3-PAD\n functions, or accepts an offer to do so.\n\n IAC DON'T X.3-PAD\n\n The issuing telnet demands that its peer not perform or cease\n performing X.3-PAD functions.\n\n IAC WILL X.3-PAD\n\n The issuing telnet offers to perform X.3-PAD functions or confirms\n that it will do so.\n\n IAC WON'T X.3-PAD\n\n The issuing telnet refuses to perform X.3-PAD functions or\n indicates that it is ceasing to handle them.\n\n Typically a server (host) telnet will u 1053 nested-reference unchanged"},{"id":"IETF RFC 1075","type":"specification","body":"IETF","designation":"RFC 1075","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1075.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1075.txt","https://www.rfc-editor.org/rfc/rfc1075.pdf"],"folder":"IETF/RFC-1075","files":{"txt":{"path":"standards/IETF/RFC-1075/RFC-1075.txt","sha256":"7a4d27a35f5ed199e0a87eea7e209d4d7a7984a91ac91f3896ab643f1caa55e6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Waitzman\nRequest For Comments: 1075 C. Partridge\n BBN STC\n S. Deering\n Stanford University\n November 1988\n\n Distance Vector Multicast Routing Protocol\n\n1. Status of this Memo\n\n This RFC describes a distance-vector-style routing protocol for\n routing multicast datagrams through an internet. It is derived from\n the Routing Information Protocol (RIP) [1], and implements\n multicasting as described in RFC-1054. This is an experimental\n protocol, and its implementation is not recommended at this time.\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n A draft standard for multicasting over IP networks now exists [2],\n but no routing protocols to support internetwork multicasting are\n available. This memo describes an experimental routing protocol,\n named DVMRP, that implements internetwork multicasting. DVMRP\n combines many of the features of RIP [1] with the ","scope_keywords":["1075","algorithm","algorithms","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null}],"search_text":"IETF RFC 1075 Network Working Group D. Waitzman\nRequest For Comments: 1075 C. Partridge\n BBN STC\n S. Deering\n Stanford University\n November 1988\n\n Distance Vector Multicast Routing Protocol\n\n1. Status of this Memo\n\n This RFC describes a distance-vector-style routing protocol for\n routing multicast datagrams through an internet. It is derived from\n the Routing Information Protocol (RIP) [1], and implements\n multicasting as described in RFC-1054. This is an experimental\n protocol, and its implementation is not recommended at this time.\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n A draft standard for multicasting over IP networks now exists [2],\n but no routing protocols to support internetwork multicasting are\n available. This memo describes an experimental routing protocol,\n named DVMRP, that implements internetwork multicasting. DVMRP\n combines many of the features of RIP [1] with the  1075 algorithm algorithms management path nested-reference unchanged"},{"id":"IETF RFC 2341","type":"specification","body":"IETF","designation":"RFC 2341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2341.txt","https://www.rfc-editor.org/rfc/rfc2341.pdf"],"folder":"IETF/RFC-2341","files":{"txt":{"path":"standards/IETF/RFC-2341/RFC-2341.txt","sha256":"85323f6007bdfa43f93640797db6a6f93fa4c0cf03597561591f8ac53cdcff56"}},"tags":["nested-reference","unchanged"],"summary":"Virtual dial-up allows many separate and autonomous protocol domains\n to share common access infrastructure including modems, Access\n Servers, and ISDN routers. Previous RFCs have specified protocols\n for supporting IP dial-up via SLIP [1] and multiprotocol dial-up via\n PPP [2]. This document describes the Layer Two Forwarding protocol\n (L2F) which permits the tunneling of the link layer (i.e., HDLC,\n async HDLC, or SLIP frames) of higher level protocols. Using such\n tunnels, it is possible to divorce the location of the initial dial-\n up server from the location at which the dial-up protocol connection\n is terminated and access to the network provided.","scope_keywords":["2341","authentication","delivery","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2341 Virtual dial-up allows many separate and autonomous protocol domains\n to share common access infrastructure including modems, Access\n Servers, and ISDN routers. Previous RFCs have specified protocols\n for supporting IP dial-up via SLIP [1] and multiprotocol dial-up via\n PPP [2]. This document describes the Layer Two Forwarding protocol\n (L2F) which permits the tunneling of the link layer (i.e., HDLC,\n async HDLC, or SLIP frames) of higher level protocols. Using such\n tunnels, it is possible to divorce the location of the initial dial-\n up server from the location at which the dial-up protocol connection\n is terminated and access to the network provided. 2341 authentication delivery key management registered nested-reference unchanged"},{"id":"IETF RFC 1056","type":"specification","body":"IETF","designation":"RFC 1056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1056.txt","https://www.rfc-editor.org/rfc/rfc1056.pdf"],"folder":"IETF/RFC-1056","files":{"txt":{"path":"standards/IETF/RFC-1056/RFC-1056.txt","sha256":"2360de027aea6b3fabaac80c6975b8fc9ae3a8362f8f4697b529d349838c37ce"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Lambert\nRequest for Comments: 1056 MIT\nObsoletes: RFC-993 June 1988\n\n PCMAIL: A Distributed Mail System for Personal Computers\n\n Table of Contents\n\n 1. Status of this Document 1\n 2. Introduction 2\n 3. Repository architecture 4\n 3.1. Management of user mail state 5\n 3.2. Repository-to-RFC-822 name translation 7\n 4. Communication between repository and client: DMSP 8\n 4.1. DMSP commands 8\n 4.2. DMSP responses 8\n 4.3. DMSP sessions 11\n 4.4. General operations 11\n 4.5. User operations 12\n 4.6. Client operations 13\n 4.7. Mailbox operations 14\n 4.8. Address operations 15\n 4.9. Subscription operations 15\n 4.10. Message operations 16\n 5. Client Architecture 18\n 5.1. Multiple clients 18\n 5.2. Synchronization 18\n 5.3. Batch operation versus interactive operation 20\n 5.4. Message summaries 20\n 6. Typical interactive-style client-repository interaction 21\n 7. A current Pcmai","scope_keywords":["1056","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1064","folder":"IETF/RFC-1064","source":"IETF/RFC-1064/RFC-1064.txt","version":null},{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1733","folder":"IETF/RFC-1733","source":"IETF/RFC-1733/RFC-1733.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null}],"search_text":"IETF RFC 1056 Network Working Group M. Lambert\nRequest for Comments: 1056 MIT\nObsoletes: RFC-993 June 1988\n\n PCMAIL: A Distributed Mail System for Personal Computers\n\n Table of Contents\n\n 1. Status of this Document 1\n 2. Introduction 2\n 3. Repository architecture 4\n 3.1. Management of user mail state 5\n 3.2. Repository-to-RFC-822 name translation 7\n 4. Communication between repository and client: DMSP 8\n 4.1. DMSP commands 8\n 4.2. DMSP responses 8\n 4.3. DMSP sessions 11\n 4.4. General operations 11\n 4.5. User operations 12\n 4.6. Client operations 13\n 4.7. Mailbox operations 14\n 4.8. Address operations 15\n 4.9. Subscription operations 15\n 4.10. Message operations 16\n 5. Client Architecture 18\n 5.1. Multiple clients 18\n 5.2. Synchronization 18\n 5.3. Batch operation versus interactive operation 20\n 5.4. Message summaries 20\n 6. Typical interactive-style client-repository interaction 21\n 7. A current Pcmai 1056 delivery management nested-reference unchanged"},{"id":"IETF RFC 1064","type":"specification","body":"IETF","designation":"RFC 1064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1064.txt","https://www.rfc-editor.org/rfc/rfc1064.pdf"],"folder":"IETF/RFC-1064","files":{"txt":{"path":"standards/IETF/RFC-1064/RFC-1064.txt","sha256":"8d2a462a5cc4ac15a59281d474ab759161e944f6acce0bd70b64add13c4ac619"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 1064 SUMEX-AIM\n July 1988\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically access\n mail from a mailbox server (\"repository\"). This RFC specifies a\n standard for the SUMEX-AIM community and a proposed experimental\n protocol for the Internet community. Discussion and suggestions for\n improvement are requested. Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Interactive Mail Access Protocol, Version 2 (IMAP2)\n is to allow a workstation or similar small machine to access\n electronic mail from a mailbox server. IMAP2 is the protocol used by\n the SUMEX-AIM MM-D (MM Distributed) mail system.\n\n Although different in many ways from POP2 (RFC 937), IMAP2 may be\n thought of as a functional superset of POP2, and the POP2 RFC was\n used as a m","scope_keywords":["1064","delivery","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1064 Network Working Group M. Crispin\nRequest for Comments: 1064 SUMEX-AIM\n July 1988\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically access\n mail from a mailbox server (\"repository\"). This RFC specifies a\n standard for the SUMEX-AIM community and a proposed experimental\n protocol for the Internet community. Discussion and suggestions for\n improvement are requested. Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Interactive Mail Access Protocol, Version 2 (IMAP2)\n is to allow a workstation or similar small machine to access\n electronic mail from a mailbox server. IMAP2 is the protocol used by\n the SUMEX-AIM MM-D (MM Distributed) mail system.\n\n Although different in many ways from POP2 (RFC 937), IMAP2 may be\n thought of as a functional superset of POP2, and the POP2 RFC was\n used as a m 1064 delivery path presentation nested-reference unchanged"},{"id":"IETF RFC 1176","type":"specification","body":"IETF","designation":"RFC 1176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1176.txt","https://www.rfc-editor.org/rfc/rfc1176.pdf"],"folder":"IETF/RFC-1176","files":{"txt":{"path":"standards/IETF/RFC-1176/RFC-1176.txt","sha256":"bd7fb2242f8089f0923c88df5cc283e9e38cf7a276a1e5a579d04c9ee3987c5b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 1176 Washington\nObsoletes: RFC 1064 August 1990\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a method for personal computers and workstations to\n dynamically access mail from a mailbox server (\"repository\"). It\n obosoletes RFC 1064. This RFC specifies an Experimental Protocol for\n the Internet community. Discussion and suggestions for improvement\n are requested. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Interactive Mail Access Protocol, Version 2 (IMAP2)\n is to allow a workstation, personal computer, or similar small\n machine to access electronic mail from a mailbox server. Since the\n distinction between personal computers a","scope_keywords":["1176","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1732","folder":"IETF/RFC-1732","source":"IETF/RFC-1732/RFC-1732.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2062","folder":"IETF/RFC-2062","source":"IETF/RFC-2062/RFC-2062.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1176 Network Working Group M. Crispin\nRequest for Comments: 1176 Washington\nObsoletes: RFC 1064 August 1990\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a method for personal computers and workstations to\n dynamically access mail from a mailbox server (\"repository\"). It\n obosoletes RFC 1064. This RFC specifies an Experimental Protocol for\n the Internet community. Discussion and suggestions for improvement\n are requested. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Interactive Mail Access Protocol, Version 2 (IMAP2)\n is to allow a workstation, personal computer, or similar small\n machine to access electronic mail from a mailbox server. Since the\n distinction between personal computers a 1176 delivery presentation nested-reference unchanged"},{"id":"IETF RFC 1203","type":"specification","body":"IETF","designation":"RFC 1203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1203.txt","https://www.rfc-editor.org/rfc/rfc1203.pdf"],"folder":"IETF/RFC-1203","files":{"txt":{"path":"standards/IETF/RFC-1203/RFC-1203.txt","sha256":"63511fa86d42216c20a556e14c45796f3bce262c22a07bc7f28a7a3dcccc71cb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Rice\nRequest for Comments: 1203 Stanford\nObsoletes: RFC 1064 February 1991\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 3\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to access mail\n dynamically from a mailbox server (\"repository\"). This RFC specifies\n a standard for the SUMEX-AIM community and an Experimental Protocol\n for the Internet community. Discussion and suggestions for\n improvement are requested. Please refer to the current edition of\n the \"IAB Official Protocol Standards\" for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nScope\n\n The following document is a modified version of RFC 1064, the\n definition of the IMAP2 protocol. This RFC has been written\n specifically as a counter proposal to RFC 1176, which itself proposes\n modifications to IMAP2. Sadly, RFC 1176 was made without inter","scope_keywords":["1203","key","keys","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1203 Network Working Group J. Rice\nRequest for Comments: 1203 Stanford\nObsoletes: RFC 1064 February 1991\n\n INTERACTIVE MAIL ACCESS PROTOCOL - VERSION 3\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to access mail\n dynamically from a mailbox server (\"repository\"). This RFC specifies\n a standard for the SUMEX-AIM community and an Experimental Protocol\n for the Internet community. Discussion and suggestions for\n improvement are requested. Please refer to the current edition of\n the \"IAB Official Protocol Standards\" for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nScope\n\n The following document is a modified version of RFC 1064, the\n definition of the IMAP2 protocol. This RFC has been written\n specifically as a counter proposal to RFC 1176, which itself proposes\n modifications to IMAP2. Sadly, RFC 1176 was made without inter 1203 key keys pid nested-reference unchanged"},{"id":"IETF RFC 1733","type":"specification","body":"IETF","designation":"RFC 1733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1733.txt","https://www.rfc-editor.org/rfc/rfc1733.pdf"],"folder":"IETF/RFC-1733","files":{"txt":{"path":"standards/IETF/RFC-1733/RFC-1733.txt","sha256":"eef9b2da51903e57720fed63c47ebc1cb194992f8d861f4b37250d22d8db088f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 1733 University of Washington\nCategory: Informational December 1994\n\n DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nDistributed Electronic Mail Models\n\n There are three fundamental models of client/server email: offline,\n online, and disconnected use. IMAP4 can be used in any one of these\n three models.\n\n The offline model is the most familiar form of client/server email\n today, and is used by protocols such as POP-3 (RFC 1225) and UUCP.\n In this model, a client application periodically connects to a\n server. It downloads all the pending messages to the client machine\n and deletes these from the server. Thereafter, all mail processing\n is local to the c","scope_keywords":["1733"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1733 Network Working Group M. Crispin\nRequest for Comments: 1733 University of Washington\nCategory: Informational December 1994\n\n DISTRIBUTED ELECTRONIC MAIL MODELS IN IMAP4\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nDistributed Electronic Mail Models\n\n There are three fundamental models of client/server email: offline,\n online, and disconnected use. IMAP4 can be used in any one of these\n three models.\n\n The offline model is the most familiar form of client/server email\n today, and is used by protocols such as POP-3 (RFC 1225) and UUCP.\n In this model, a client application periodically connects to a\n server. It downloads all the pending messages to the client machine\n and deletes these from the server. Thereafter, all mail processing\n is local to the c 1733 nested-reference unchanged"},{"id":"IETF RFC 1981","type":"specification","body":"IETF","designation":"RFC 1981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1981.txt","https://www.rfc-editor.org/rfc/rfc1981.pdf"],"folder":"IETF/RFC-1981","files":{"txt":{"path":"standards/IETF/RFC-1981/RFC-1981.txt","sha256":"570ef2603031c4bf7ad2a0d9f301d582795b66cb66dbd1d39b72e3e974f26e21"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Path MTU Discovery for IP version 6. It is\n largely derived from RFC 1191, which describes Path MTU Discovery for\n IP version 4.","scope_keywords":["1981","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2292","folder":"IETF/RFC-2292","source":"IETF/RFC-2292/RFC-2292.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3542","folder":"IETF/RFC-3542","source":"IETF/RFC-3542/RFC-3542.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 1981 This document describes Path MTU Discovery for IP version 6. It is\n largely derived from RFC 1191, which describes Path MTU Discovery for\n IP version 4. 1981 management path nested-reference unchanged"},{"id":"IETF RFC 2307","type":"specification","body":"IETF","designation":"RFC 2307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2307.txt","https://www.rfc-editor.org/rfc/rfc2307.pdf"],"folder":"IETF/RFC-2307","files":{"txt":{"path":"standards/IETF/RFC-2307/RFC-2307.txt","sha256":"b1a142e70fe45a9120fefac7da706ff83d15254b622431dd9e998c577b3eac93"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an experimental mechanism for mapping\n entities related to TCP/IP and the UNIX system into X.500 [X500]\n entries so that they may be resolved with the Lightweight Directory\n Access Protocol [RFC2251]. A set of attribute types and object\n classes are proposed, along with specific guidelines for interpreting\n them.\n\n The intention is to assist the deployment of LDAP as an\n organizational nameservice. No proposed solutions are intended as\n standards for the Internet. Rather, it is hoped that a general\n consensus will emerge as to the appropriate solution to such\n problems, leading eventually to the adoption of standards. The\n proposed mechanism has already been implemented with some success.\n\n1. Background and Motivation\n\n The UNIX (R) operating system, and its derivatives (specifically,\n those which support TCP/IP and conform to the X/Open Single UNIX\n specification","scope_keywords":["2307","attribute","attributes","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 2307 This document describes an experimental mechanism for mapping\n entities related to TCP/IP and the UNIX system into X.500 [X500]\n entries so that they may be resolved with the Lightweight Directory\n Access Protocol [RFC2251]. A set of attribute types and object\n classes are proposed, along with specific guidelines for interpreting\n them.\n\n The intention is to assist the deployment of LDAP as an\n organizational nameservice. No proposed solutions are intended as\n standards for the Internet. Rather, it is hoped that a general\n consensus will emerge as to the appropriate solution to such\n problems, leading eventually to the adoption of standards. The\n proposed mechanism has already been implemented with some success.\n\n1. Background and Motivation\n\n The UNIX (R) operating system, and its derivatives (specifically,\n those which support TCP/IP and conform to the X/Open Single UNIX\n specification 2307 attribute attributes identification key nested-reference unchanged"},{"id":"IETF RFC 2623","type":"specification","body":"IETF","designation":"RFC 2623","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2623.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2623.txt","https://www.rfc-editor.org/rfc/rfc2623.pdf"],"folder":"IETF/RFC-2623","files":{"txt":{"path":"standards/IETF/RFC-2623/RFC-2623.txt","sha256":"81bb428a462dadfcab5a74e286d38bc573236f4f6474bfec875bea08f6ff8728"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum clarifies various security issues involving the NFS\n protocol (Version 2 and Version 3 only) and then describes how the\n Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS\n security flavor protocol and Kerberos V5. This memorandum is\n provided so that people can write compatible implementations.","scope_keywords":["2623","algorithm","authentication","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2623 This memorandum clarifies various security issues involving the NFS\n protocol (Version 2 and Version 3 only) and then describes how the\n Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS\n security flavor protocol and Kerberos V5. This memorandum is\n provided so that people can write compatible implementations. 2623 algorithm authentication key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1058","type":"specification","body":"IETF","designation":"RFC 1058","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1058.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1058.txt","https://www.rfc-editor.org/rfc/rfc1058.pdf"],"folder":"IETF/RFC-1058","files":{"txt":{"path":"standards/IETF/RFC-1058/RFC-1058.txt","sha256":"4e1e3b6bab42be33c95da3e2ad917449bceb21a785f7e4443f3c6f5271980cd9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Hedrick\nRequest for Comments: 1058 Rutgers University\n June 1988\n\n Routing Information Protocol\n\nStatus of this Memo\n\n This RFC describes an existing protocol for exchanging routing\n information among gateways and other hosts. It is intended to be\n used as a basis for developing gateway software for use in the\n Internet community. Distribution of this memo is unlimited.\n\n Table of Contents\n\n 1. Introduction 2\n 1.1. Limitations of the protocol 4\n 1.2. Organization of this document 4\n 2. Distance Vector Algorithms 5\n 2.1. Dealing with changes in topology 11\n 2.2. Preventing instability 12\n 2.2.1. Split horizon 14\n 2.2.2. Triggered updates 15\n 3. Specifications for the protocol 16\n 3.1. Message formats 18\n 3.2. Addressing considerations 20\n 3.3. Timers 23\n 3.4. Input processing 24\n 3.4.1. Request 25\n 3.4.2. Response 26\n 3.5. Output Processing 28\n 3.6. Compatibility ","scope_keywords":["1058","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1075","folder":"IETF/RFC-1075","source":"IETF/RFC-1075/RFC-1075.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1387","folder":"IETF/RFC-1387","source":"IETF/RFC-1387/RFC-1387.txt","version":null},{"body":"IETF","designation":"RFC 1388","folder":"IETF/RFC-1388","source":"IETF/RFC-1388/RFC-1388.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1582","folder":"IETF/RFC-1582","source":"IETF/RFC-1582/RFC-1582.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1923","folder":"IETF/RFC-1923","source":"IETF/RFC-1923/RFC-1923.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2174","folder":"IETF/RFC-2174","source":"IETF/RFC-2174/RFC-2174.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2453","folder":"IETF/RFC-2453","source":"IETF/RFC-2453/RFC-2453.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 1058 Network Working Group C. Hedrick\nRequest for Comments: 1058 Rutgers University\n June 1988\n\n Routing Information Protocol\n\nStatus of this Memo\n\n This RFC describes an existing protocol for exchanging routing\n information among gateways and other hosts. It is intended to be\n used as a basis for developing gateway software for use in the\n Internet community. Distribution of this memo is unlimited.\n\n Table of Contents\n\n 1. Introduction 2\n 1.1. Limitations of the protocol 4\n 1.2. Organization of this document 4\n 2. Distance Vector Algorithms 5\n 2.1. Dealing with changes in topology 11\n 2.2. Preventing instability 12\n 2.2.1. Split horizon 14\n 2.2.2. Triggered updates 15\n 3. Specifications for the protocol 16\n 3.1. Message formats 18\n 3.2. Addressing considerations 20\n 3.3. Timers 23\n 3.4. Input processing 24\n 3.4.1. Request 25\n 3.4.2. Response 26\n 3.5. Output Processing 28\n 3.6. Compatibility  1058 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 1222","type":"specification","body":"IETF","designation":"RFC 1222","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1222.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1222.txt","https://www.rfc-editor.org/rfc/rfc1222.pdf"],"folder":"IETF/RFC-1222","files":{"txt":{"path":"standards/IETF/RFC-1222/RFC-1222.txt","sha256":"52609b77eff46d9a937564bfb5ef7170c60abab4cc9b7e9a9390afcd810b9ee0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H-W. Braun\nRequest for Comments: 1222 San Diego Supercomputer Center\n Y. Rekhter\n IBM T.J. Watson Research Center\n May 1991\n\n Advancing the NSFNET Routing Architecture\n\nStatus of this Memo\n\n This RFC suggests improvements in the NSFNET routing architecture to\n accommodate a more flexible interface to the Backbone clients. This\n memo provides information for the Internet community. It does not\n specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This memo describes the history of NSFNET Backbone routing and\n outlines two suggested phases for further evolution of the Backbone's\n routing interface. The intent is to provide a more flexible\n interface for NSFNET Backbone service subscribers, by providing an\n attachment option that is simpler and lower-cost than the current\n one.\n\nAcknowledgements\n\n The authors would like to thank Scott ","scope_keywords":["1222","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 1222 Network Working Group H-W. Braun\nRequest for Comments: 1222 San Diego Supercomputer Center\n Y. Rekhter\n IBM T.J. Watson Research Center\n May 1991\n\n Advancing the NSFNET Routing Architecture\n\nStatus of this Memo\n\n This RFC suggests improvements in the NSFNET routing architecture to\n accommodate a more flexible interface to the Backbone clients. This\n memo provides information for the Internet community. It does not\n specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This memo describes the history of NSFNET Backbone routing and\n outlines two suggested phases for further evolution of the Backbone's\n routing interface. The intent is to provide a more flexible\n interface for NSFNET Backbone service subscribers, by providing an\n attachment option that is simpler and lower-cost than the current\n one.\n\nAcknowledgements\n\n The authors would like to thank Scott  1222 path pid nested-reference unchanged"},{"id":"IETF RFC 1322","type":"specification","body":"IETF","designation":"RFC 1322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1322.txt","https://www.rfc-editor.org/rfc/rfc1322.pdf"],"folder":"IETF/RFC-1322","files":{"txt":{"path":"standards/IETF/RFC-1322/RFC-1322.txt","sha256":"6d6847f8850a9496b304fb84fcd3588a107fdd653ec5a0953672c78c9f785590"}},"tags":["nested-reference","unchanged"],"summary":"This memo is an informational RFC which outlines one potential\n approach for inter-domain routing in future global internets. The\n focus is on scalability to very large networks and functionality, as\n well as scalability, to support routing in an environment of\n heterogeneous services, requirements, and route selection criteria.\n\n Note: The work of D. Estrin and S. Hotz was supported by the National\n Science Foundation under contract number NCR-9011279, with matching\n funds from GTE Laboratories. The work of Y. Rekhter was supported by\n the Defense Advanced Research Projects Agency, under contract\n DABT63-91-C-0019. Views and conclusions expressed in this paper are\n not necessarily those of the Defense Advanced Research Projects\n Agency and National Science Foundation.","scope_keywords":["1322","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1668","folder":"IETF/RFC-1668","source":"IETF/RFC-1668/RFC-1668.txt","version":null}],"search_text":"IETF RFC 1322 This memo is an informational RFC which outlines one potential\n approach for inter-domain routing in future global internets. The\n focus is on scalability to very large networks and functionality, as\n well as scalability, to support routing in an environment of\n heterogeneous services, requirements, and route selection criteria.\n\n Note: The work of D. Estrin and S. Hotz was supported by the National\n Science Foundation under contract number NCR-9011279, with matching\n funds from GTE Laboratories. The work of Y. Rekhter was supported by\n the Defense Advanced Research Projects Agency, under contract\n DABT63-91-C-0019. Views and conclusions expressed in this paper are\n not necessarily those of the Defense Advanced Research Projects\n Agency and National Science Foundation. 1322 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 1364","type":"specification","body":"IETF","designation":"RFC 1364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1364.txt","https://www.rfc-editor.org/rfc/rfc1364.pdf"],"folder":"IETF/RFC-1364","files":{"txt":{"path":"standards/IETF/RFC-1364/RFC-1364.txt","sha256":"736425941134abb0fe566f1abf8a44afce45355d7d723f4f24eed7cff04d7947"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the various criteria to be used when designing\n Autonomous System Border Routers (ASBR) that will run BGP with other\n ASBRs external to the AS and OSPF as its IGP.","scope_keywords":["1364","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null}],"search_text":"IETF RFC 1364 This memo defines the various criteria to be used when designing\n Autonomous System Border Routers (ASBR) that will run BGP with other\n ASBRs external to the AS and OSPF as its IGP. 1364 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 1387","type":"specification","body":"IETF","designation":"RFC 1387","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1387.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1387.txt","https://www.rfc-editor.org/rfc/rfc1387.pdf"],"folder":"IETF/RFC-1387","files":{"txt":{"path":"standards/IETF/RFC-1387/RFC-1387.txt","sha256":"331e873b458e4a82ddf58387ec3a7051d17f4c966eab0c3dcc869e04a6b22d58"}},"tags":["nested-reference","unchanged"],"summary":"As required by Routing Protocol Criteria (RFC 1264), this report\n documents the key features of the RIP-2 protocol and the current\n implementation experience.\n\nAcknowledgements\n\n The RIP-2 protocol owes much to those who participated in the RIP-2\n Working Group of the Internet Engineering Task Force (IETF). A\n special thanks goes to Fred Baker for his help on the MIB, and to\n Jeffrey Honig for the implementation experience.\n\n1. Protocol Documents\n\n The RIP-2 protocol description is defined in RFC 1388 [1]. This memo\n suggests an update to the \"Routing Information Protocol\" (RFC 1058)\n [3]. The RIP-2 MIB description is defined in RFC 1389 [2].\n\n2. Key Features\n\n While RIP-2 shares the same basic algorithms as RIP-1, it supports\n several new features. They are: routing domains, external route\n tags, subnet masks, next hop addresses, and authentication.","scope_keywords":["1387","algorithm","algorithms","authentication","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1388","folder":"IETF/RFC-1388","source":"IETF/RFC-1388/RFC-1388.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null}],"search_text":"IETF RFC 1387 As required by Routing Protocol Criteria (RFC 1264), this report\n documents the key features of the RIP-2 protocol and the current\n implementation experience.\n\nAcknowledgements\n\n The RIP-2 protocol owes much to those who participated in the RIP-2\n Working Group of the Internet Engineering Task Force (IETF). A\n special thanks goes to Fred Baker for his help on the MIB, and to\n Jeffrey Honig for the implementation experience.\n\n1. Protocol Documents\n\n The RIP-2 protocol description is defined in RFC 1388 [1]. This memo\n suggests an update to the \"Routing Information Protocol\" (RFC 1058)\n [3]. The RIP-2 MIB description is defined in RFC 1389 [2].\n\n2. Key Features\n\n While RIP-2 shares the same basic algorithms as RIP-1, it supports\n several new features. They are: routing domains, external route\n tags, subnet masks, next hop addresses, and authentication. 1387 algorithm algorithms authentication key policies nested-reference unchanged"},{"id":"IETF RFC 1388","type":"specification","body":"IETF","designation":"RFC 1388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1388.txt","https://www.rfc-editor.org/rfc/rfc1388.pdf"],"folder":"IETF/RFC-1388","files":{"txt":{"path":"standards/IETF/RFC-1388/RFC-1388.txt","sha256":"064ba8d8509a61d78236986a235e0456b7a8d1b51780c02a2069b35030430f43"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1], to expand the amount of useful\n information carried in RIP packets and to add a measure of security.\n A companion document will define the SNMP MIB objects for RIP-2 [2].\n\nAcknowledgements\n\n I would like to thank the following for their contributions to this\n document: Fred Baker, Noel Chiappa and Vince Fuller. This memo is a\n product of the RIP-2 Working Group of the Internet Engineering Task\n Force (IETF).","scope_keywords":["1388","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1387","folder":"IETF/RFC-1387","source":"IETF/RFC-1387/RFC-1387.txt","version":null},{"body":"IETF","designation":"RFC 1389","folder":"IETF/RFC-1389","source":"IETF/RFC-1389/RFC-1389.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1582","folder":"IETF/RFC-1582","source":"IETF/RFC-1582/RFC-1582.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null}],"search_text":"IETF RFC 1388 This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1], to expand the amount of useful\n information carried in RIP packets and to add a measure of security.\n A companion document will define the SNMP MIB objects for RIP-2 [2].\n\nAcknowledgements\n\n I would like to thank the following for their contributions to this\n document: Fred Baker, Noel Chiappa and Vince Fuller. This memo is a\n product of the RIP-2 Working Group of the Internet Engineering Task\n Force (IETF). 1388 authentication management nested-reference unchanged"},{"id":"IETF RFC 1403","type":"specification","body":"IETF","designation":"RFC 1403","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1403.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1403.txt","https://www.rfc-editor.org/rfc/rfc1403.pdf"],"folder":"IETF/RFC-1403","files":{"txt":{"path":"standards/IETF/RFC-1403/RFC-1403.txt","sha256":"303490929711c08a0fa1621baf410b61d87fae9bb97e66e071b12b3e1b248cbe"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the various criteria to be used when designing an\n Autonomous System Border Routers (ASBR) that will run BGP with other\n ASBRs external to the AS and OSPF as its IGP. This is a\n republication of RFC 1364 to correct some editorial problems.","scope_keywords":["1403","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null}],"search_text":"IETF RFC 1403 This memo defines the various criteria to be used when designing an\n Autonomous System Border Routers (ASBR) that will run BGP with other\n ASBRs external to the AS and OSPF as its IGP. This is a\n republication of RFC 1364 to correct some editorial problems. 1403 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 1476","type":"specification","body":"IETF","designation":"RFC 1476","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1476.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1476.txt","https://www.rfc-editor.org/rfc/rfc1476.pdf"],"folder":"IETF/RFC-1476","files":{"txt":{"path":"standards/IETF/RFC-1476/RFC-1476.txt","sha256":"293cd5cc13b15dfd9fb65aa6ee0401cdc86d9755ff8cb5bacac50c4a5a105589"}},"tags":["nested-reference","unchanged"],"summary":"This RFC describes an open distance vector routing protocol for use\n at all levels of the internet, from isolated LANs to the major\n routers of an international commercial network provider.","scope_keywords":["1476","algorithm","attribute","attributes","path","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1476 This RFC describes an open distance vector routing protocol for use\n at all levels of the internet, from isolated LANs to the major\n routers of an international commercial network provider. 1476 algorithm attribute attributes path policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 1582","type":"specification","body":"IETF","designation":"RFC 1582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1582.txt","https://www.rfc-editor.org/rfc/rfc1582.pdf"],"folder":"IETF/RFC-1582","files":{"txt":{"path":"standards/IETF/RFC-1582/RFC-1582.txt","sha256":"8c77deaee3dea462d72b671f8859121a6cad10d14aec273a522fd9fad23b1c13"}},"tags":["nested-reference","unchanged"],"summary":"Running routing protocols on connection oriented Public Data\n Networks, for example X.25 packet switched networks or ISDN, can be\n expensive if the standard form of periodic broadcasting of routing\n information is adhered to. The high cost arises because a connection\n has to all practical intents and purposes be kept open to every\n destination to which routing information is to be sent, whether or\n not it is being used to carry user data.\n\n Routing information may also fail to be propagated if the number of\n destinations to which the routing information is to be sent exceeds\n the number of channels available to the router on the Wide Area\n Network (WAN).\n\n This memo defines a generalized modification which can be applied to\n Bellman-Ford (or distance vector) algorithm information broadcasting\n protocols, for example IP RIP, Netware RIP or Netware SAP, which\n overcomes the limitations of ","scope_keywords":["1582","algorithm","delivery","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1582 Running routing protocols on connection oriented Public Data\n Networks, for example X.25 packet switched networks or ISDN, can be\n expensive if the standard form of periodic broadcasting of routing\n information is adhered to. The high cost arises because a connection\n has to all practical intents and purposes be kept open to every\n destination to which routing information is to be sent, whether or\n not it is being used to carry user data.\n\n Routing information may also fail to be propagated if the number of\n destinations to which the routing information is to be sent exceeds\n the number of channels available to the router on the Wide Area\n Network (WAN).\n\n This memo defines a generalized modification which can be applied to\n Bellman-Ford (or distance vector) algorithm information broadcasting\n protocols, for example IP RIP, Netware RIP or Netware SAP, which\n overcomes the limitations of  1582 algorithm delivery pid nested-reference unchanged"},{"id":"IETF RFC 1656","type":"specification","body":"IETF","designation":"RFC 1656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1656.txt","https://www.rfc-editor.org/rfc/rfc1656.pdf"],"folder":"IETF/RFC-1656","files":{"txt":{"path":"standards/IETF/RFC-1656/RFC-1656.txt","sha256":"acb5673b4b3f813bd635a653dc9841e60aa3c2ff160cbe80a6204b0da99b6fb3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Traina\nRequest for Comments: 1656 cisco Systems\nCategory: Informational July 1994\n\n BGP-4 Protocol Document Roadmap and Implementation Experience\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System\n routing protocol. It is built on experience gained with BGP as\n defined in RFC-1267 [2] and BGP usage in the connected Internet as\n described in RFC-1268 [3].\n\n The primary function of a BGP speaking system is to exchange network\n reachability information with other BGP systems. This network\n reachability information includes information on the list of\n Autonomous Systems (ASs) that reachability information traverses.\n This information is sufficient to c","scope_keywords":["1656","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null}],"search_text":"IETF RFC 1656 Network Working Group P. Traina\nRequest for Comments: 1656 cisco Systems\nCategory: Informational July 1994\n\n BGP-4 Protocol Document Roadmap and Implementation Experience\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System\n routing protocol. It is built on experience gained with BGP as\n defined in RFC-1267 [2] and BGP usage in the connected Internet as\n described in RFC-1268 [3].\n\n The primary function of a BGP speaking system is to exchange network\n reachability information with other BGP systems. This network\n reachability information includes information on the list of\n Autonomous Systems (ASs) that reachability information traverses.\n This information is sufficient to c 1656 management path policies policy nested-reference unchanged"},{"id":"IETF RFC 1721","type":"specification","body":"IETF","designation":"RFC 1721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1721.txt","https://www.rfc-editor.org/rfc/rfc1721.pdf"],"folder":"IETF/RFC-1721","files":{"txt":{"path":"standards/IETF/RFC-1721/RFC-1721.txt","sha256":"5f6650ec464df37fcb7d17b24f37e55a65091f92389c943ce75a8057500c1356"}},"tags":["nested-reference","unchanged"],"summary":"As required by Routing Protocol Criteria (RFC 1264), this report\n documents the key features of the RIP-2 protocol and the current\n implementation experience. This report is a prerequisite to\n advancing RIP-2 on the standards track.\n\nAcknowledgements\n\n The RIP-2 protocol owes much to those who participated in the RIP-2\n working group. A special thanks goes to Fred Baker, for his help on\n the MIB, and to Jeffrey Honig, for all his comments.\n\n1. Protocol Documents\n\n The RIP-2 applicability statement is defined in RFC 1722 [1].\n\n The RIP-2 protocol description is defined in RFC 1723 [2]. This memo\n obsoletes RFC 1388, which specifies an update to the \"Routing\n Information Protocol\" RFC 1058 (STD 34).\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo\n obsoletes RFC 1389.\n\n2. Key Features\n\n While RIP-2 shares the same basic algorithms as RIP-1, it supports\n several new feature","scope_keywords":["1721","algorithm","algorithms","authentication","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null}],"search_text":"IETF RFC 1721 As required by Routing Protocol Criteria (RFC 1264), this report\n documents the key features of the RIP-2 protocol and the current\n implementation experience. This report is a prerequisite to\n advancing RIP-2 on the standards track.\n\nAcknowledgements\n\n The RIP-2 protocol owes much to those who participated in the RIP-2\n working group. A special thanks goes to Fred Baker, for his help on\n the MIB, and to Jeffrey Honig, for all his comments.\n\n1. Protocol Documents\n\n The RIP-2 applicability statement is defined in RFC 1722 [1].\n\n The RIP-2 protocol description is defined in RFC 1723 [2]. This memo\n obsoletes RFC 1388, which specifies an update to the \"Routing\n Information Protocol\" RFC 1058 (STD 34).\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo\n obsoletes RFC 1389.\n\n2. Key Features\n\n While RIP-2 shares the same basic algorithms as RIP-1, it supports\n several new feature 1721 algorithm algorithms authentication key registered nested-reference unchanged"},{"id":"IETF RFC 1722","type":"specification","body":"IETF","designation":"RFC 1722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1722.txt","https://www.rfc-editor.org/rfc/rfc1722.pdf"],"folder":"IETF/RFC-1722","files":{"txt":{"path":"standards/IETF/RFC-1722/RFC-1722.txt","sha256":"91f4d792a992f6d86ffbfe269861821ecd8f174a65c61c4cd1e660e940e9d93a"}},"tags":["nested-reference","unchanged"],"summary":"As required by Routing Protocol Criteria (RFC 1264), this report\n defines the applicability of the RIP-2 protocol within the Internet.\n This report is a prerequisite to advancing RIP-2 on the standards\n track.\n\n1. Protocol Documents\n\n The RIP-2 protocol analysis is documented in RFC 1721 [1].\n\n The RIP-2 protocol description is defined in RFC 1723 [2]. This memo\n obsoletes RFC 1388, which specifies an update to the \"Routing\n Information Protocol\" RFC 1058 (STD 34).\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo will\n obsolete RFC 1389.\n\n2. Introduction\n\n This report describes how RIP-2 may be useful within the Internet.\n In essence, the environments in which RIP-2 is the IGP of choice is a\n superset of the environments in which RIP-1, as defined in RFC 1058\n [1], has traditionally been used. It is important to remember that\n RIP-2 is an extension to RIP-1; RIP-2 is not","scope_keywords":["1722","algorithm","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1723","folder":"IETF/RFC-1723","source":"IETF/RFC-1723/RFC-1723.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1722 As required by Routing Protocol Criteria (RFC 1264), this report\n defines the applicability of the RIP-2 protocol within the Internet.\n This report is a prerequisite to advancing RIP-2 on the standards\n track.\n\n1. Protocol Documents\n\n The RIP-2 protocol analysis is documented in RFC 1721 [1].\n\n The RIP-2 protocol description is defined in RFC 1723 [2]. This memo\n obsoletes RFC 1388, which specifies an update to the \"Routing\n Information Protocol\" RFC 1058 (STD 34).\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo will\n obsolete RFC 1389.\n\n2. Introduction\n\n This report describes how RIP-2 may be useful within the Internet.\n In essence, the environments in which RIP-2 is the IGP of choice is a\n superset of the environments in which RIP-1, as defined in RFC 1058\n [1], has traditionally been used. It is important to remember that\n RIP-2 is an extension to RIP-1; RIP-2 is not 1722 algorithm authentication path nested-reference unchanged"},{"id":"IETF RFC 1723","type":"specification","body":"IETF","designation":"RFC 1723","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1723.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1723.txt","https://www.rfc-editor.org/rfc/rfc1723.pdf"],"folder":"IETF/RFC-1723","files":{"txt":{"path":"standards/IETF/RFC-1723/RFC-1723.txt","sha256":"5c5c9c9eaa0966be6e66f2d67793d1a6f4a7f5a66fd01a989bbabf92a3e4bc23"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1,2], to expand the amount of useful\n information carried in RIP messages and to add a measure of security.\n This memo obsoletes RFC 1388, which specifies an update to the\n \"Routing Information Protocol\" STD 34, RFC 1058.\n\n The RIP-2 protocol analysis is documented in RFC 1721 [4].\n\n The RIP-2 applicability statement is document in RFC 1722 [5].\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo\n obsoletes RFC 1389.\n\nAcknowledgements\n\n I would like to thank the IETF ripv2 Working Group for their help in\n improving the RIP-2 protocol.\n\nMalkin [Page 1]\n\f\nRFC 1723 RIP Version 2 November 1994","scope_keywords":["1723","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1724","folder":"IETF/RFC-1724","source":"IETF/RFC-1724/RFC-1724.txt","version":null},{"body":"IETF","designation":"RFC 1923","folder":"IETF/RFC-1923","source":"IETF/RFC-1923/RFC-1923.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2174","folder":"IETF/RFC-2174","source":"IETF/RFC-2174/RFC-2174.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null}],"search_text":"IETF RFC 1723 This document specifies an extension of the Routing Information\n Protocol (RIP), as defined in [1,2], to expand the amount of useful\n information carried in RIP messages and to add a measure of security.\n This memo obsoletes RFC 1388, which specifies an update to the\n \"Routing Information Protocol\" STD 34, RFC 1058.\n\n The RIP-2 protocol analysis is documented in RFC 1721 [4].\n\n The RIP-2 applicability statement is document in RFC 1722 [5].\n\n The RIP-2 MIB description is defined in RFC 1724 [3]. This memo\n obsoletes RFC 1389.\n\nAcknowledgements\n\n I would like to thank the IETF ripv2 Working Group for their help in\n improving the RIP-2 protocol.\n\nMalkin [Page 1]\n\f\nRFC 1723 RIP Version 2 November 1994 1723 authentication management nested-reference unchanged"},{"id":"IETF RFC 1745","type":"specification","body":"IETF","designation":"RFC 1745","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1745.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1745.txt","https://www.rfc-editor.org/rfc/rfc1745.pdf"],"folder":"IETF/RFC-1745","files":{"txt":{"path":"standards/IETF/RFC-1745/RFC-1745.txt","sha256":"d42c7c6e9daae2d946d64ae68fe454c81297f440e3e09a41cc0666ba5a5a72bb"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the various criteria to be used when designing an\n Autonomous System Border Router (ASBR) that will run either BGP4 or\n IDRP for IP with other ASBRs external to the AS and OSPF as its IGP.","scope_keywords":["1745","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1745 This memo defines the various criteria to be used when designing an\n Autonomous System Border Router (ASBR) that will run either BGP4 or\n IDRP for IP with other ASBRs external to the AS and OSPF as its IGP. 1745 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 1923","type":"specification","body":"IETF","designation":"RFC 1923","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1923.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1923.txt","https://www.rfc-editor.org/rfc/rfc1923.pdf"],"folder":"IETF/RFC-1923","files":{"txt":{"path":"standards/IETF/RFC-1923/RFC-1923.txt","sha256":"6aa6d596e814ebf32557ae442a70d24fda40277ce9506dd72e8c4dc4eee57f15"}},"tags":["nested-reference","unchanged"],"summary":"RIP Version 1 [RFC-1058] has been declared an historic document.\n This Applicability statement provides the supporting motivation for\n that declaration. The primary reason, as described below, is the\n Classful nature of RIPv1.","scope_keywords":["1923"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null}],"search_text":"IETF RFC 1923 RIP Version 1 [RFC-1058] has been declared an historic document.\n This Applicability statement provides the supporting motivation for\n that declaration. The primary reason, as described below, is the\n Classful nature of RIPv1. 1923 nested-reference unchanged"},{"id":"IETF RFC 2174","type":"specification","body":"IETF","designation":"RFC 2174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2174.txt","https://www.rfc-editor.org/rfc/rfc2174.pdf"],"folder":"IETF/RFC-2174","files":{"txt":{"path":"standards/IETF/RFC-2174/RFC-2174.txt","sha256":"2a8f80ec2f6782fae6a819f5d653a2ff7791844fd0aa68e5f696af3c23440696"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a MAPOS version 1 extension, SSP (Switch\n Switch Protocol). MAPOS is a multiple access protocol for\n transmission of network-protocol packets, encapsulated in High-Level\n Data Link Control (HDLC) frames, over SONET/SDH. In MAPOS network, a\n SONET switch provides the multiple access capability to end nodes.\n SSP is a protocol of Distance Vector family and provides unicast and\n broadcast/multicast routing for multiple SONET switch environment.\n\n1. Introduction\n\n This document describes an extension to MAPOS version 1, Switch\n Switch Protocol, for routing both unicast and broadcast/multicast\n frames. MAPOS[1], Multiple Access Protocol over SONET (Synchronous\n Optical Network) / SDH (Synchronous Digital Hierarchy) [2][3][4][5],\n is a link layer protocol for transmission of HDLC frames over\n SONET/SDH. A SONET switch provides the multiple access capability to\n each nod","scope_keywords":["2174","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null}],"search_text":"IETF RFC 2174 This document describes a MAPOS version 1 extension, SSP (Switch\n Switch Protocol). MAPOS is a multiple access protocol for\n transmission of network-protocol packets, encapsulated in High-Level\n Data Link Control (HDLC) frames, over SONET/SDH. In MAPOS network, a\n SONET switch provides the multiple access capability to end nodes.\n SSP is a protocol of Distance Vector family and provides unicast and\n broadcast/multicast routing for multiple SONET switch environment.\n\n1. Introduction\n\n This document describes an extension to MAPOS version 1, Switch\n Switch Protocol, for routing both unicast and broadcast/multicast\n frames. MAPOS[1], Multiple Access Protocol over SONET (Synchronous\n Optical Network) / SDH (Synchronous Digital Hierarchy) [2][3][4][5],\n is a link layer protocol for transmission of HDLC frames over\n SONET/SDH. A SONET switch provides the multiple access capability to\n each nod 2174 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 2360","type":"specification","body":"IETF","designation":"RFC 2360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2360.txt","https://www.rfc-editor.org/rfc/rfc2360.pdf"],"folder":"IETF/RFC-2360","files":{"txt":{"path":"standards/IETF/RFC-2360/RFC-2360.txt","sha256":"ec5b6e77f1d1f9bb8cfd3f859129823af2e512379da0df4eee27c5177167f793"}},"tags":["nested-reference","unchanged"],"summary":"This document is a guide for Internet standard writers. It defines\n those characteristics that make standards coherent, unambiguous, and\n easy to interpret. In addition, it singles out usage believed to\n have led to unclear specifications, resulting in non-interoperable\n interpretations in the past. These guidelines are to be used with\n RFC 2223, \"Instructions to RFC Authors\".","scope_keywords":["2360","algorithm","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null}],"search_text":"IETF RFC 2360 This document is a guide for Internet standard writers. It defines\n those characteristics that make standards coherent, unambiguous, and\n easy to interpret. In addition, it singles out usage believed to\n have led to unclear specifications, resulting in non-interoperable\n interpretations in the past. These guidelines are to be used with\n RFC 2223, \"Instructions to RFC Authors\". 2360 algorithm management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 3442","type":"specification","body":"IETF","designation":"RFC 3442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3442.txt","https://www.rfc-editor.org/rfc/rfc3442.pdf"],"folder":"IETF/RFC-3442","files":{"txt":{"path":"standards/IETF/RFC-3442/RFC-3442.txt","sha256":"1601791a4a22d08ebb205b4dab88b034e376bdd4c233fb8458b1daeb371e5a0c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to configure a list of static routes in the client. The network\n destinations in these routes are classless - each routing table entry\n includes a subnet mask.","scope_keywords":["3442","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 3442 This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to configure a list of static routes in the client. The network\n destinations in these routes are classless - each routing table entry\n includes a subnet mask. 3442 algorithm key nested-reference unchanged"},{"id":"IETF RFC 4632","type":"specification","body":"IETF","designation":"RFC 4632","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4632.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4632.txt","https://www.rfc-editor.org/rfc/rfc4632.pdf"],"folder":"IETF/RFC-4632","files":{"txt":{"path":"standards/IETF/RFC-4632/RFC-4632.txt","sha256":"13694a39f586eb2054407780edccdf7c39332e57f067c8008bba4326bfc24fa9"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses the strategy for address assignment of the\n existing 32-bit IPv4 address space with a view toward conserving the\n address space and limiting the growth rate of global routing state.\n This document obsoletes the original Classless Inter-domain Routing\n (CIDR) spec in RFC 1519, with changes made both to clarify the\n concepts it introduced and, after more than twelve years, to update\n the Internet community on the results of deploying the technology\n described.\n\nFuller & Li Best Current Practice [Page 1]\n\f\nRFC 4632 CIDR Address Strategy August 2006","scope_keywords":["4632","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 4632 This memo discusses the strategy for address assignment of the\n existing 32-bit IPv4 address space with a view toward conserving the\n address space and limiting the growth rate of global routing state.\n This document obsoletes the original Classless Inter-domain Routing\n (CIDR) spec in RFC 1519, with changes made both to clarify the\n concepts it introduced and, after more than twelve years, to update\n the Internet community on the results of deploying the technology\n described.\n\nFuller & Li Best Current Practice [Page 1]\n\f\nRFC 4632 CIDR Address Strategy August 2006 4632 pid policy nested-reference unchanged"},{"id":"IETF RFC 1059","type":"specification","body":"IETF","designation":"RFC 1059","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1059.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1059.txt","https://www.rfc-editor.org/rfc/rfc1059.pdf"],"folder":"IETF/RFC-1059","files":{"txt":{"path":"standards/IETF/RFC-1059/RFC-1059.txt","sha256":"74fe74ab8352f53bbd3508bc934cc1d23ba70f3761b327133163822bf1c02075"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Mills\nRequest for Comments: 1059 University of Delaware\n July 1988\n\n Network Time Protocol (Version 1)\n Specification and Implementation\n\nStatus of this Memo\n\n This memo describes the Network Time Protocol (NTP), specifies its\n formal structure and summarizes information useful for its\n implementation. NTP provides the mechanisms to synchronize time and\n coordinate time distribution in a large, diverse internet operating\n at rates from mundane to lightwave. It uses a returnable-time design\n in which a distributed subnet of time servers operating in a self-\n organizing, hierarchical master-slave configuration synchronizes\n logical clocks within the subnet and to national time standards via\n wire or radio. The servers can also redistribute reference time via\n local routing algorithms and time daemons.\n\n The NTP architectures, algorithms and protocols which have evo","scope_keywords":["1059","algorithm","algorithms","delivery","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null}],"search_text":"IETF RFC 1059 Network Working Group D. Mills\nRequest for Comments: 1059 University of Delaware\n July 1988\n\n Network Time Protocol (Version 1)\n Specification and Implementation\n\nStatus of this Memo\n\n This memo describes the Network Time Protocol (NTP), specifies its\n formal structure and summarizes information useful for its\n implementation. NTP provides the mechanisms to synchronize time and\n coordinate time distribution in a large, diverse internet operating\n at rates from mundane to lightwave. It uses a returnable-time design\n in which a distributed subnet of time servers operating in a self-\n organizing, hierarchical master-slave configuration synchronizes\n logical clocks within the subnet and to national time standards via\n wire or radio. The servers can also redistribute reference time via\n local routing algorithms and time daemons.\n\n The NTP architectures, algorithms and protocols which have evo 1059 algorithm algorithms delivery path timestamp nested-reference unchanged"},{"id":"IETF RFC 4330","type":"specification","body":"IETF","designation":"RFC 4330","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4330.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4330.txt","https://www.rfc-editor.org/rfc/rfc4330.pdf"],"folder":"IETF/RFC-4330","files":{"txt":{"path":"standards/IETF/RFC-4330/RFC-4330.txt","sha256":"e0a5344883d62f9ff58a6cf3a44398bda097badd3013236fab47ea7fdc25bc33"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum describes the Simple Network Time Protocol Version 4\n (SNTPv4), which is a subset of the Network Time Protocol (NTP) used\n to synchronize computer clocks in the Internet. SNTPv4 can be used\n when the ultimate performance of a full NTP implementation based on\n RFC 1305 is neither needed nor justified. When operating with\n current and previous NTP and SNTP versions, SNTPv4 requires no\n changes to the specifications or known implementations, but rather\n clarifies certain design features that allow operation in a simple,\n stateless remote-procedure call (RPC) mode with accuracy and\n reliability expectations similar to the UDP/TIME protocol described\n in RFC 868.\n\n This memorandum obsoletes RFC 1769, which describes SNTP Version 3\n (SNTPv3), and RFC 2030, which describes SNTPv4. Its purpose is to\n correct certain inconsistencies in the previous documents and to\n clarify header","scope_keywords":["4330","algorithm","algorithms","authentication","key","management","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 4330 This memorandum describes the Simple Network Time Protocol Version 4\n (SNTPv4), which is a subset of the Network Time Protocol (NTP) used\n to synchronize computer clocks in the Internet. SNTPv4 can be used\n when the ultimate performance of a full NTP implementation based on\n RFC 1305 is neither needed nor justified. When operating with\n current and previous NTP and SNTP versions, SNTPv4 requires no\n changes to the specifications or known implementations, but rather\n clarifies certain design features that allow operation in a simple,\n stateless remote-procedure call (RPC) mode with accuracy and\n reliability expectations similar to the UDP/TIME protocol described\n in RFC 868.\n\n This memorandum obsoletes RFC 1769, which describes SNTP Version 3\n (SNTPv3), and RFC 2030, which describes SNTPv4. Its purpose is to\n correct certain inconsistencies in the previous documents and to\n clarify header 4330 algorithm algorithms authentication key management path timestamp nested-reference unchanged"},{"id":"IETF RFC 1171","type":"specification","body":"IETF","designation":"RFC 1171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1171.txt","https://www.rfc-editor.org/rfc/rfc1171.pdf"],"folder":"IETF/RFC-1171","files":{"txt":{"path":"standards/IETF/RFC-1171/RFC-1171.txt","sha256":"c8ae72951d46cc4914678689a74630e4d7285ddf5629cd086b71d569ec18ec67"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of three\n parts:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. An extensible Link Control Protocol (LCP).\n\n 3. A family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n This document defines the encapsulation scheme, the basic LCP, and an\n NCP for establishing and configuring the Internet Protocol (IP)\n (called the IP Control Protocol, IPCP).\n\n The options and facilities used by the LCP and the IPCP are defined\n in separate documents. Control protocols for configuring and\n utilizing other network-layer protocols besides IP (e.g., DECNET,\n OSI) are expected to be developed as needed.\n\nPerkins [Page i]\n\f\nRFC 1171 Point-to-Point Protocol July 1990","scope_keywords":["1171","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1172","folder":"IETF/RFC-1172","source":"IETF/RFC-1172/RFC-1172.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null}],"search_text":"IETF RFC 1171 The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of three\n parts:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. An extensible Link Control Protocol (LCP).\n\n 3. A family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n This document defines the encapsulation scheme, the basic LCP, and an\n NCP for establishing and configuring the Internet Protocol (IP)\n (called the IP Control Protocol, IPCP).\n\n The options and facilities used by the LCP and the IPCP are defined\n in separate documents. Control protocols for configuring and\n utilizing other network-layer protocols besides IP (e.g., DECNET,\n OSI) are expected to be developed as needed.\n\nPerkins [Page i]\n\f\nRFC 1171 Point-to-Point Protocol July 1990 1171 management nested-reference unchanged"},{"id":"IETF RFC 1172","type":"specification","body":"IETF","designation":"RFC 1172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1172.txt","https://www.rfc-editor.org/rfc/rfc1172.pdf"],"folder":"IETF/RFC-1172","files":{"txt":{"path":"standards/IETF/RFC-1172/RFC-1172.txt","sha256":"348180a0567db40ab038ed7783938ebdbcda00a4b25fb5f18adb983e225309f6"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of\n\n 1) a method for encapsulating datagrams over serial links,\n 2) an extensible Link Control Protocol (LCP), and\n 3) a family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n The PPP encapsulating scheme, the basic LCP, and an NCP for\n controlling and establishing the Internet Protocol (IP) (called the\n IP Control Protocol, IPCP) are defined in The Point-to-Point Protocol\n (PPP) [1].\n\n This document defines the intial options used by the LCP and IPCP. It\n also defines a method of Link Quality Monitoring and a simple\n authentication scheme.\n\nPerkins & Hobby [Page i]\n\f\nRFC 1172 PPP Initial Options July 1990","scope_keywords":["1172","authentication","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1220","folder":"IETF/RFC-1220","source":"IETF/RFC-1220/RFC-1220.txt","version":null},{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1333","folder":"IETF/RFC-1333","source":"IETF/RFC-1333/RFC-1333.txt","version":null},{"body":"IETF","designation":"RFC 1334","folder":"IETF/RFC-1334","source":"IETF/RFC-1334/RFC-1334.txt","version":null}],"search_text":"IETF RFC 1172 The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is composed of\n\n 1) a method for encapsulating datagrams over serial links,\n 2) an extensible Link Control Protocol (LCP), and\n 3) a family of Network Control Protocols (NCP) for establishing\n and configuring different network-layer protocols.\n\n The PPP encapsulating scheme, the basic LCP, and an NCP for\n controlling and establishing the Internet Protocol (IP) (called the\n IP Control Protocol, IPCP) are defined in The Point-to-Point Protocol\n (PPP) [1].\n\n This document defines the intial options used by the LCP and IPCP. It\n also defines a method of Link Quality Monitoring and a simple\n authentication scheme.\n\nPerkins & Hobby [Page i]\n\f\nRFC 1172 PPP Initial Options July 1990 1172 authentication policy nested-reference unchanged"},{"id":"IETF RFC 1224","type":"specification","body":"IETF","designation":"RFC 1224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1224.txt","https://www.rfc-editor.org/rfc/rfc1224.pdf"],"folder":"IETF/RFC-1224","files":{"txt":{"path":"standards/IETF/RFC-1224/RFC-1224.txt","sha256":"10c925ef4beac6bf945f1a4aef12e84597444a8e1f927b25955fe5dc3dd2edfc"}},"tags":["nested-reference","unchanged"],"summary":"This RFC explores mechanisms to prevent a remotely managed entity\n from burdening a manager or network with an unexpected amount of\n network management information, and to ensure delivery of \"important\"\n information. The focus is on controlling the flow of asynchronously\n generated information, and not how the information is generated.","scope_keywords":["1224","delivery","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null}],"search_text":"IETF RFC 1224 This RFC explores mechanisms to prevent a remotely managed entity\n from burdening a manager or network with an unexpected amount of\n network management information, and to ensure delivery of \"important\"\n information. The focus is on controlling the flow of asynchronously\n generated information, and not how the information is generated. 1224 delivery management pid nested-reference unchanged"},{"id":"IETF RFC 1225","type":"specification","body":"IETF","designation":"RFC 1225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1225.txt","https://www.rfc-editor.org/rfc/rfc1225.pdf"],"folder":"IETF/RFC-1225","files":{"txt":{"path":"standards/IETF/RFC-1225/RFC-1225.txt","sha256":"f28245b863aaa5ec200aac666e4811667c8e2f39d39a5b70a7d456a435078a1b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1225 Performance Systems International\nObsoletes: RFC 1081 May 1991\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This memo suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies an IAB\n standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nOverview\n\n This memo is a republication of RFC 1081 which was based on RFC 918\n (since revised as RFC 937). Although similar in form to the original\n Post Office Protocol (POP) proposed for the Internet community, the\n protocol discussed in this memo is similar in spirit to the ideas\n investigated b","scope_keywords":["1225","authorization","crl","delivery","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1339","folder":"IETF/RFC-1339","source":"IETF/RFC-1339/RFC-1339.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1460","folder":"IETF/RFC-1460","source":"IETF/RFC-1460/RFC-1460.txt","version":null},{"body":"IETF","designation":"RFC 1733","folder":"IETF/RFC-1733","source":"IETF/RFC-1733/RFC-1733.txt","version":null}],"search_text":"IETF RFC 1225 Network Working Group M. Rose\nRequest for Comments: 1225 Performance Systems International\nObsoletes: RFC 1081 May 1991\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This memo suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies an IAB\n standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nOverview\n\n This memo is a republication of RFC 1081 which was based on RFC 918\n (since revised as RFC 937). Although similar in form to the original\n Post Office Protocol (POP) proposed for the Internet community, the\n protocol discussed in this memo is similar in spirit to the ideas\n investigated b 1225 authorization crl delivery key trust nested-reference unchanged"},{"id":"IETF RFC 1246","type":"specification","body":"IETF","designation":"RFC 1246","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1246.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1246.txt","https://www.rfc-editor.org/rfc/rfc1246.pdf"],"folder":"IETF/RFC-1246","files":{"pdf":{"path":"standards/IETF/RFC-1246/RFC-1246.pdf","sha256":"49660756cb3275178b242f2de1dde5d48e9440af4f02165953302a2286ce63e0"},"txt":{"path":"standards/IETF/RFC-1246/RFC-1246.txt","sha256":"12fd9d62f777cc3588b0890bd2ec5cf15b24c22eaf93a5623e8f37d9ac7e8373"}},"tags":["nested-reference","unchanged"],"summary":"This is the second of two reports on the OSPF protocol. These reports\nare required by the IAB/IESG in order for an Internet routing protocol\nto advance to Draft Standard Status. OSPF is a TCP/IP routing protocol,\ndesigned to be used internal to an Autonomous System (in other words,\nOSPF is an Interior Gateway Protocol).\n\nOSPF is currently designated as a Proposed Standard. Version 1 of the\nOSPF protocol was published in RFC 1131. Since then OSPF version 2 has\nbeen developed. Version 2 has been documented in RFC 1247. The changes\nbetween version 1 and version 2 of the OSPF protocol are explained in\nAppendix F of RFC 1247. It is OSPF Version 2 that is the subject of this\nreport.\n\nThis report documents experience with OSPF V2. This includes reports on\ninteroperability testing, field experience, simulations and the current\nstate of OSPF implementations. It also presents a summary of the OSPF","scope_keywords":["1246","authentication","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1245","folder":"IETF/RFC-1245","source":"IETF/RFC-1245/RFC-1245.txt","version":null},{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1765","folder":"IETF/RFC-1765","source":"IETF/RFC-1765/RFC-1765.txt","version":null},{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null}],"search_text":"IETF RFC 1246 This is the second of two reports on the OSPF protocol. These reports\nare required by the IAB/IESG in order for an Internet routing protocol\nto advance to Draft Standard Status. OSPF is a TCP/IP routing protocol,\ndesigned to be used internal to an Autonomous System (in other words,\nOSPF is an Interior Gateway Protocol).\n\nOSPF is currently designated as a Proposed Standard. Version 1 of the\nOSPF protocol was published in RFC 1131. Since then OSPF version 2 has\nbeen developed. Version 2 has been documented in RFC 1247. The changes\nbetween version 1 and version 2 of the OSPF protocol are explained in\nAppendix F of RFC 1247. It is OSPF Version 2 that is the subject of this\nreport.\n\nThis report documents experience with OSPF V2. This includes reports on\ninteroperability testing, field experience, simulations and the current\nstate of OSPF implementations. It also presents a summary of the OSPF 1246 authentication management subject nested-reference unchanged"},{"id":"IETF RFC 1247","type":"specification","body":"IETF","designation":"RFC 1247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1247.txt","https://www.rfc-editor.org/rfc/rfc1247.pdf"],"folder":"IETF/RFC-1247","files":{"pdf":{"path":"standards/IETF/RFC-1247/RFC-1247.pdf","sha256":"b8a7af6f87f49e0664a1324c3cf8c486aab7be51bb6ebced8b90a25696ad7cff"},"txt":{"path":"standards/IETF/RFC-1247/RFC-1247.txt","sha256":"1e985f1b68049321e26ec4041f5a0e428313da7a86b96d3c854ad350de18cdad"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents version 2 of the OSPF protocol. OSPF is a link-\nstate based routing protocol. It is designed to be run internal to a\nsingle Autonomous System. Each OSPF router maintains an identical\ndatabase describing the Autonomous System's topology. From this\ndatabase, a routing table is calculated by constructing a shortest-path\ntree.\n\nOSPF recalculates routes quickly in the face of topological changes,\nutilizing a minimum of routing protocol traffic. OSPF provides support\nfor equal-cost multipath. Separate routes can be calculated for each IP\ntype of service. An area routing capability is provided, enabling an\nadditional level of routing protection and a reduction in routing\nprotocol traffic. In addition, all OSPF routing protocol exchanges are\nauthenticated.\n\nVersion 1 of the OSPF protocol was documented in RFC 1131. The\ndifferences between the two versions are explained in App","scope_keywords":["1247","algorithm","authentication","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1245","folder":"IETF/RFC-1245","source":"IETF/RFC-1245/RFC-1245.txt","version":null},{"body":"IETF","designation":"RFC 1246","folder":"IETF/RFC-1246","source":"IETF/RFC-1246/RFC-1246.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1338","folder":"IETF/RFC-1338","source":"IETF/RFC-1338/RFC-1338.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1370","folder":"IETF/RFC-1370","source":"IETF/RFC-1370/RFC-1370.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1519","folder":"IETF/RFC-1519","source":"IETF/RFC-1519/RFC-1519.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 3137","folder":"IETF/RFC-3137","source":"IETF/RFC-3137/RFC-3137.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null}],"search_text":"IETF RFC 1247 This memo documents version 2 of the OSPF protocol. OSPF is a link-\nstate based routing protocol. It is designed to be run internal to a\nsingle Autonomous System. Each OSPF router maintains an identical\ndatabase describing the Autonomous System's topology. From this\ndatabase, a routing table is calculated by constructing a shortest-path\ntree.\n\nOSPF recalculates routes quickly in the face of topological changes,\nutilizing a minimum of routing protocol traffic. OSPF provides support\nfor equal-cost multipath. Separate routes can be calculated for each IP\ntype of service. An area routing capability is provided, enabling an\nadditional level of routing protection and a reduction in routing\nprotocol traffic. In addition, all OSPF routing protocol exchanges are\nauthenticated.\n\nVersion 1 of the OSPF protocol was documented in RFC 1131. The\ndifferences between the two versions are explained in App 1247 algorithm authentication path trust nested-reference unchanged"},{"id":"IETF RFC 1310","type":"specification","body":"IETF","designation":"RFC 1310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1310.txt","https://www.rfc-editor.org/rfc/rfc1310.pdf"],"folder":"IETF/RFC-1310","files":{"txt":{"path":"standards/IETF/RFC-1310/RFC-1310.txt","sha256":"44264425b4e0842abbd1634cd1812246f9ea5e613f0e1143e3eae7611930a5de"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1310 Lyman Chapin, Chair\n March 1992\n\n The Internet Standards Process\n\nStatus of this Memo\n\n This informational memo presents the current procedures for creating\n and documenting Internet Standards. Distribution of this memo is\n unlimited.\n\nTABLE OF CONTENTS\n\n 1. INTRODUCTION ................................................. 2\n 1.1. Internet Standards ....................................... 2\n 1.2. Organization ............................................. 3\n 2. THE INTERNET STANDARDS PROCESS ............................... 4\n 2.1. Introduction ............................................. 4\n 2.2. The Internet Standards Track ............................. 5\n 2.3. Requests for Comments (RFCs) ............................. 5\n 2.4. Internet Drafts .......................................... 6\n 2.5. Internet Assigned Number","scope_keywords":["1310","holder","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1396","folder":"IETF/RFC-1396","source":"IETF/RFC-1396/RFC-1396.txt","version":null},{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1602","folder":"IETF/RFC-1602","source":"IETF/RFC-1602/RFC-1602.txt","version":null},{"body":"IETF","designation":"RFC 1627","folder":"IETF/RFC-1627","source":"IETF/RFC-1627/RFC-1627.txt","version":null},{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 2026","folder":"IETF/RFC-2026","source":"IETF/RFC-2026/RFC-2026.txt","version":null},{"body":"IETF","designation":"RFC 2437","folder":"IETF/RFC-2437","source":"IETF/RFC-2437/RFC-2437.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null}],"search_text":"IETF RFC 1310 Network Working Group Internet Activities Board\nRequest for Comments: 1310 Lyman Chapin, Chair\n March 1992\n\n The Internet Standards Process\n\nStatus of this Memo\n\n This informational memo presents the current procedures for creating\n and documenting Internet Standards. Distribution of this memo is\n unlimited.\n\nTABLE OF CONTENTS\n\n 1. INTRODUCTION ................................................. 2\n 1.1. Internet Standards ....................................... 2\n 1.2. Organization ............................................. 3\n 2. THE INTERNET STANDARDS PROCESS ............................... 4\n 2.1. Introduction ............................................. 4\n 2.2. The Internet Standards Track ............................. 5\n 2.3. Requests for Comments (RFCs) ............................. 5\n 2.4. Internet Drafts .......................................... 6\n 2.5. Internet Assigned Number 1310 holder management policy nested-reference unchanged"},{"id":"IETF RFC 1329","type":"specification","body":"IETF","designation":"RFC 1329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1329.txt","https://www.rfc-editor.org/rfc/rfc1329.pdf"],"folder":"IETF/RFC-1329","files":{"txt":{"path":"standards/IETF/RFC-1329/RFC-1329.txt","sha256":"952b27b2391fce01dafece26d5d68c7e8a15ec9a1f9f0788b4f355379d3e3bd7"}},"tags":["nested-reference","unchanged"],"summary":"In this document an idea is submitted how IP and ARP can be used on\n inhomogeneous FDDI networks (FDDI networks with single MAC and dual\n MAC stations) by introducing a new protocol layer in the protocol\n suite of the dual MAC stations. Thus two dual MAC stations are able\n to do a load splitting across the two rings and use the double\n bandwidth of 200 Mbits/s as single MAC stations. The new layer is an\n extension of layer 3. For the user, the higher layer protocols, IP\n and ARP the property \"dual MAC\" is transparent. No modification is\n required in the protocol suite of single MAC stations and transparent\n bridges.\n\n2. Acknowledgements\n\n This paper is a result of a diploma thesis prepared at the Technical\n University of Munich, Lehrstuhl fuer Kommunikationsnetze, in co-\n operation with the Siemens Nixdorf AG. The author would like to\n thank Jrg Eberspher and Bernhard Edmaier from the un","scope_keywords":["1329","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 1329 In this document an idea is submitted how IP and ARP can be used on\n inhomogeneous FDDI networks (FDDI networks with single MAC and dual\n MAC stations) by introducing a new protocol layer in the protocol\n suite of the dual MAC stations. Thus two dual MAC stations are able\n to do a load splitting across the two rings and use the double\n bandwidth of 200 Mbits/s as single MAC stations. The new layer is an\n extension of layer 3. For the user, the higher layer protocols, IP\n and ARP the property \"dual MAC\" is transparent. No modification is\n required in the protocol suite of single MAC stations and transparent\n bridges.\n\n2. Acknowledgements\n\n This paper is a result of a diploma thesis prepared at the Technical\n University of Munich, Lehrstuhl fuer Kommunikationsnetze, in co-\n operation with the Siemens Nixdorf AG. The author would like to\n thank Jrg Eberspher and Bernhard Edmaier from the un 1329 management path nested-reference unchanged"},{"id":"IETF RFC 1331","type":"specification","body":"IETF","designation":"RFC 1331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1331.txt","https://www.rfc-editor.org/rfc/rfc1331.pdf"],"folder":"IETF/RFC-1331","files":{"txt":{"path":"standards/IETF/RFC-1331/RFC-1331.txt","sha256":"edcb777e3430446be55f36091ae317c55a0f2c4763ae097450342a40ae0a0482"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is comprised of\n three main components:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP encapsulation scheme, together with the\n PPP Link Control Protocol (LCP), an extensible option negotiation\n protocol which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu","scope_keywords":["1331","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1333","folder":"IETF/RFC-1333","source":"IETF/RFC-1333/RFC-1333.txt","version":null},{"body":"IETF","designation":"RFC 1334","folder":"IETF/RFC-1334","source":"IETF/RFC-1334/RFC-1334.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1362","folder":"IETF/RFC-1362","source":"IETF/RFC-1362/RFC-1362.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1548","folder":"IETF/RFC-1548","source":"IETF/RFC-1548/RFC-1548.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null}],"search_text":"IETF RFC 1331 The Point-to-Point Protocol (PPP) provides a method for transmitting\n datagrams over serial point-to-point links. PPP is comprised of\n three main components:\n\n 1. A method for encapsulating datagrams over serial links.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP encapsulation scheme, together with the\n PPP Link Control Protocol (LCP), an extensible option negotiation\n protocol which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu 1331 authentication management nested-reference unchanged"},{"id":"IETF RFC 1332","type":"specification","body":"IETF","designation":"RFC 1332","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1332.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1332.txt","https://www.rfc-editor.org/rfc/rfc1332.pdf"],"folder":"IETF/RFC-1332","files":{"txt":{"path":"standards/IETF/RFC-1332/RFC-1332.txt","sha256":"d22af6b18102f448aa8e52f911269dd17c020c570dd8806299873f30b912a69b"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring the\n Internet Protocol [2] over PPP, and a method to negotiate and use Van\n Jacobson TCP/IP header compression [3] with PPP.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF).\n\nMcGregor [Page i]\n\f\nRFC 1332 PPP IPCP May 1992","scope_keywords":["1332","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1877","folder":"IETF/RFC-1877","source":"IETF/RFC-1877/RFC-1877.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 1332 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring the\n Internet Protocol [2] over PPP, and a method to negotiate and use Van\n Jacobson TCP/IP header compression [3] with PPP.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF).\n\nMcGregor [Page i]\n\f\nRFC 1332 PPP IPCP May 1992 1332 authentication nested-reference unchanged"},{"id":"IETF RFC 1063","type":"specification","body":"IETF","designation":"RFC 1063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1063.txt","https://www.rfc-editor.org/rfc/rfc1063.pdf"],"folder":"IETF/RFC-1063","files":{"txt":{"path":"standards/IETF/RFC-1063/RFC-1063.txt","sha256":"bd6fecbcc56aa812686e8ffbfb21c8eba4bab66a6680e114845f052dcc0f8942"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Mogul\nRequest For Comments: 1063 C. Kent\n DEC\n C. Partridge\n BBN\n K. McCloghrie\n TWG\n July 1988\n\n IP MTU Discovery Options\n\nSTATUS OF THIS MEMO\n\n A pair of IP options that can be used to learn the minimum MTU of a\n path through an internet is described, along with its possible uses.\n This is a proposal for an Experimental protocol. Distribution of\n this memo is unlimited.\n\nINTRODUCTION\n\n Although the Internet Protocol allows gateways to fragment packets\n that are too large to forward, fragmentation is not always desirable.\n It can lead to poor performance or even total communication failure\n in circumstances that are surprisingly common. (For a thorough\n discussion of this issue, see [1]).\n\n A datagram will be fragmented if it is larger than the Maximum\n Transmission Unit (MTU) of some network along the path it follows.\n In order to avoid fragmentation, a host se","scope_keywords":["1063","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 1063 Network Working Group J. Mogul\nRequest For Comments: 1063 C. Kent\n DEC\n C. Partridge\n BBN\n K. McCloghrie\n TWG\n July 1988\n\n IP MTU Discovery Options\n\nSTATUS OF THIS MEMO\n\n A pair of IP options that can be used to learn the minimum MTU of a\n path through an internet is described, along with its possible uses.\n This is a proposal for an Experimental protocol. Distribution of\n this memo is unlimited.\n\nINTRODUCTION\n\n Although the Internet Protocol allows gateways to fragment packets\n that are too large to forward, fragmentation is not always desirable.\n It can lead to poor performance or even total communication failure\n in circumstances that are surprisingly common. (For a thorough\n discussion of this issue, see [1]).\n\n A datagram will be fragmented if it is larger than the Maximum\n Transmission Unit (MTU) of some network along the path it follows.\n In order to avoid fragmentation, a host se 1063 path nested-reference unchanged"},{"id":"IETF RFC 2402","type":"specification","body":"IETF","designation":"RFC 2402","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2402.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2402.txt","https://www.rfc-editor.org/rfc/rfc2402.pdf"],"folder":"IETF/RFC-2402","files":{"txt":{"path":"standards/IETF/RFC-2402/RFC-2402.txt","sha256":"ca686bf294c6dda22c78182c0d5104932fdf16dda6ceabf6469cbe8acfdfcca5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 2402 BBN Corp\nObsoletes: 1826 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n IP Authentication Header\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction......................................................2\n 2. Authentication Header Format......................................3\n 2.1 Next Header...................................................4\n 2.2 Payload Length.........................","scope_keywords":["2402","algorithm","algorithms","audit","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2412","folder":"IETF/RFC-2412","source":"IETF/RFC-2412/RFC-2412.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3756","folder":"IETF/RFC-3756","source":"IETF/RFC-3756/RFC-3756.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 2402 Network Working Group S. Kent\nRequest for Comments: 2402 BBN Corp\nObsoletes: 1826 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n IP Authentication Header\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction......................................................2\n 2. Authentication Header Format......................................3\n 2.1 Next Header...................................................4\n 2.2 Payload Length......................... 2402 algorithm algorithms audit authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 4302","type":"specification","body":"IETF","designation":"RFC 4302","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4302.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4302.txt","https://www.rfc-editor.org/rfc/rfc4302.pdf"],"folder":"IETF/RFC-4302","files":{"txt":{"path":"standards/IETF/RFC-4302/RFC-4302.txt","sha256":"c9de28181a78bb85ec6d1e6bda86da133307310de736632f26aa890e1f08e56b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an updated version of the IP Authentication\n Header (AH), which is designed to provide authentication services in\n IPv4 and IPv6. This document obsoletes RFC 2402 (November 1998).","scope_keywords":["4302","algorithm","algorithms","audit","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4494","folder":"IETF/RFC-4494","source":"IETF/RFC-4494/RFC-4494.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 4302 This document describes an updated version of the IP Authentication\n Header (AH), which is designed to provide authentication services in\n IPv4 and IPv6. This document obsoletes RFC 2402 (November 1998). 4302 algorithm algorithms audit authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 1730","type":"specification","body":"IETF","designation":"RFC 1730","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1730.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1730.txt","https://www.rfc-editor.org/rfc/rfc1730.pdf"],"folder":"IETF/RFC-1730","files":{"txt":{"path":"standards/IETF/RFC-1730/RFC-1730.txt","sha256":"c92f050e2904a13798f9595a108f329c25905de9d64914a39a1d73a76feb5ed6"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Access Protocol, Version 4 (IMAP4) allows a\n client to access and manipulate electronic mail messages on a server.\n IMAP4 permits manipulation of remote message folders, called\n \"mailboxes\", in a way that is functionally equivalent to local\n mailboxes. IMAP4 also provides the capability for an offline client\n to resynchronize with the server (see also [IMAP-DISC]).\n\n IMAP4 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; permanently removing messages;\n setting and clearing flags; RFC 822 and MIME parsing; searching; and\n selective fetching of message attributes, texts, and portions\n thereof. Messages in IMAP4 are accessed by the use of numbers.\n These numbers are either message sequence numbers (relative position\n from 1 to the number of messages in the mailbox) or unique\n identifiers (immutable, strictly ascending value","scope_keywords":["1730","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1731","folder":"IETF/RFC-1731","source":"IETF/RFC-1731/RFC-1731.txt","version":null},{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2062","folder":"IETF/RFC-2062","source":"IETF/RFC-2062/RFC-2062.txt","version":null},{"body":"IETF","designation":"RFC 2086","folder":"IETF/RFC-2086","source":"IETF/RFC-2086/RFC-2086.txt","version":null},{"body":"IETF","designation":"RFC 2087","folder":"IETF/RFC-2087","source":"IETF/RFC-2087/RFC-2087.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1730 The Internet Message Access Protocol, Version 4 (IMAP4) allows a\n client to access and manipulate electronic mail messages on a server.\n IMAP4 permits manipulation of remote message folders, called\n \"mailboxes\", in a way that is functionally equivalent to local\n mailboxes. IMAP4 also provides the capability for an offline client\n to resynchronize with the server (see also [IMAP-DISC]).\n\n IMAP4 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; permanently removing messages;\n setting and clearing flags; RFC 822 and MIME parsing; searching; and\n selective fetching of message attributes, texts, and portions\n thereof. Messages in IMAP4 are accessed by the use of numbers.\n These numbers are either message sequence numbers (relative position\n from 1 to the number of messages in the mailbox) or unique\n identifiers (immutable, strictly ascending value 1730 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 2060","type":"specification","body":"IETF","designation":"RFC 2060","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2060.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2060.txt","https://www.rfc-editor.org/rfc/rfc2060.pdf"],"folder":"IETF/RFC-2060","files":{"txt":{"path":"standards/IETF/RFC-2060/RFC-2060.txt","sha256":"5b818edeff3b943c01dd96241ebdb05278506f7e05d2988e78591efa26af2b67"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)\n allows a client to access and manipulate electronic mail messages on\n a server. IMAP4rev1 permits manipulation of remote message folders,\n called \"mailboxes\", in a way that is functionally equivalent to local\n mailboxes. IMAP4rev1 also provides the capability for an offline\n client to resynchronize with the server (see also [IMAP-DISC]).\n\n IMAP4rev1 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; permanently removing messages;\n setting and clearing flags; [RFC-822] and [MIME-IMB] parsing;\n searching; and selective fetching of message attributes, texts, and\n portions thereof. Messages in IMAP4rev1 are accessed by the use of\n numbers. These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev1 supports a single server. A mechanism for accessing\n configu","scope_keywords":["2060","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2177","folder":"IETF/RFC-2177","source":"IETF/RFC-2177/RFC-2177.txt","version":null},{"body":"IETF","designation":"RFC 2180","folder":"IETF/RFC-2180","source":"IETF/RFC-2180/RFC-2180.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2193","folder":"IETF/RFC-2193","source":"IETF/RFC-2193/RFC-2193.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2221","folder":"IETF/RFC-2221","source":"IETF/RFC-2221/RFC-2221.txt","version":null},{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2245","folder":"IETF/RFC-2245","source":"IETF/RFC-2245/RFC-2245.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2342","folder":"IETF/RFC-2342","source":"IETF/RFC-2342/RFC-2342.txt","version":null},{"body":"IETF","designation":"RFC 2359","folder":"IETF/RFC-2359","source":"IETF/RFC-2359/RFC-2359.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2971","folder":"IETF/RFC-2971","source":"IETF/RFC-2971/RFC-2971.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3348","folder":"IETF/RFC-3348","source":"IETF/RFC-3348/RFC-3348.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2060 The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)\n allows a client to access and manipulate electronic mail messages on\n a server. IMAP4rev1 permits manipulation of remote message folders,\n called \"mailboxes\", in a way that is functionally equivalent to local\n mailboxes. IMAP4rev1 also provides the capability for an offline\n client to resynchronize with the server (see also [IMAP-DISC]).\n\n IMAP4rev1 includes operations for creating, deleting, and renaming\n mailboxes; checking for new messages; permanently removing messages;\n setting and clearing flags; [RFC-822] and [MIME-IMB] parsing;\n searching; and selective fetching of message attributes, texts, and\n portions thereof. Messages in IMAP4rev1 are accessed by the use of\n numbers. These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev1 supports a single server. A mechanism for accessing\n configu 2060 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 2061","type":"specification","body":"IETF","designation":"RFC 2061","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2061.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2061.txt","https://www.rfc-editor.org/rfc/rfc2061.pdf"],"folder":"IETF/RFC-2061","files":{"txt":{"path":"standards/IETF/RFC-2061/RFC-2061.txt","sha256":"7e6f655d99fc23cb77e24c0947786d982dde6828e6b5ec707696715dd8799f3f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 2061 University of Washington\nCategory: Informational December 1996\n\n IMAP4 COMPATIBILITY WITH IMAP2BIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The Internet Message Access Protocol (IMAP) has been through several\n revisions and variants in its 10-year history. Many of these are\n either extinct or extremely rare; in particular, several undocumented\n variants and the variants described in RFC 1064, RFC 1176, and RFC\n 1203 fall into this category.\n\n One variant, IMAP2bis, is at the time of this writing very common and\n has been widely distributed with the Pine mailer. Unfortunately,\n there is no definite document describing IMAP2bis. This document is\n intended to be read along w","scope_keywords":["2061"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2061 Network Working Group M. Crispin\nRequest for Comments: 2061 University of Washington\nCategory: Informational December 1996\n\n IMAP4 COMPATIBILITY WITH IMAP2BIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The Internet Message Access Protocol (IMAP) has been through several\n revisions and variants in its 10-year history. Many of these are\n either extinct or extremely rare; in particular, several undocumented\n variants and the variants described in RFC 1064, RFC 1176, and RFC\n 1203 fall into this category.\n\n One variant, IMAP2bis, is at the time of this writing very common and\n has been widely distributed with the Pine mailer. Unfortunately,\n there is no definite document describing IMAP2bis. This document is\n intended to be read along w 2061 nested-reference unchanged"},{"id":"IETF RFC 3501","type":"specification","body":"IETF","designation":"RFC 3501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3501.txt","https://www.rfc-editor.org/rfc/rfc3501.pdf"],"folder":"IETF/RFC-3501","files":{"txt":{"path":"standards/IETF/RFC-3501/RFC-3501.txt","sha256":"4437974dde85859f2391f32215295e7b20ce157c3bd2adbe7e5b443e990f15cf"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)\n allows a client to access and manipulate electronic mail messages on\n a server. IMAP4rev1 permits manipulation of mailboxes (remote\n message folders) in a way that is functionally equivalent to local\n folders. IMAP4rev1 also provides the capability for an offline\n client to resynchronize with the server.\n\n IMAP4rev1 includes operations for creating, deleting, and renaming\n mailboxes, checking for new messages, permanently removing messages,\n setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching,\n and selective fetching of message attributes, texts, and portions\n thereof. Messages in IMAP4rev1 are accessed by the use of numbers.\n These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev1 supports a single server. A mechanism for accessing\n configuration information to support multipl","scope_keywords":["3501","attribute","attributes","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3503","folder":"IETF/RFC-3503","source":"IETF/RFC-3503/RFC-3503.txt","version":null},{"body":"IETF","designation":"RFC 3516","folder":"IETF/RFC-3516","source":"IETF/RFC-3516/RFC-3516.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3691","folder":"IETF/RFC-3691","source":"IETF/RFC-3691/RFC-3691.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4315","folder":"IETF/RFC-4315","source":"IETF/RFC-4315/RFC-4315.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4686","folder":"IETF/RFC-4686","source":"IETF/RFC-4686/RFC-4686.txt","version":null},{"body":"IETF","designation":"RFC 4731","folder":"IETF/RFC-4731","source":"IETF/RFC-4731/RFC-4731.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5161","folder":"IETF/RFC-5161","source":"IETF/RFC-5161/RFC-5161.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5183","folder":"IETF/RFC-5183","source":"IETF/RFC-5183/RFC-5183.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5232","folder":"IETF/RFC-5232","source":"IETF/RFC-5232/RFC-5232.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3501 The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)\n allows a client to access and manipulate electronic mail messages on\n a server. IMAP4rev1 permits manipulation of mailboxes (remote\n message folders) in a way that is functionally equivalent to local\n folders. IMAP4rev1 also provides the capability for an offline\n client to resynchronize with the server.\n\n IMAP4rev1 includes operations for creating, deleting, and renaming\n mailboxes, checking for new messages, permanently removing messages,\n setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching,\n and selective fetching of message attributes, texts, and portions\n thereof. Messages in IMAP4rev1 are accessed by the use of numbers.\n These numbers are either message sequence numbers or unique\n identifiers.\n\n IMAP4rev1 supports a single server. A mechanism for accessing\n configuration information to support multipl 3501 attribute attributes tls nested-reference unchanged"},{"id":"IETF RFC 1351","type":"specification","body":"IETF","designation":"RFC 1351","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1351.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1351.txt","https://www.rfc-editor.org/rfc/rfc1351.pdf"],"folder":"IETF/RFC-1351","files":{"txt":{"path":"standards/IETF/RFC-1351/RFC-1351.txt","sha256":"bf849702c0635e0ebb09371ddd3362200b9726ea71e0dff864d2f111ae7a70ee"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents an elaboration of the SNMP administrative model\n set forth in [1]. This model provides a unified conceptual basis for\n administering SNMP protocol entities to support\n\n o authentication and integrity,\n\n o privacy,\n\n o access control, and\n\n o the cooperation of multiple protocol entities.\n\n Please send comments to the SNMP Security Developers mailing list\n (snmp-sec-dev@tis.com).\n\n2. Introduction\n\n This memo presents an elaboration of the SNMP administrative model\n set forth in [1]. It describes how the elaborated administrative\n model is applied to realize effective network management in a variety\n of configurations and environments.\n\n The model described here entails the use of distinct identities for\n peers that exchange SNMP messages. Thus, it represents a departure\n from the community-based administrative model set forth in [1]. By\n unambiguously identifying the so","scope_keywords":["1351","authentication","key","management","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1352","folder":"IETF/RFC-1352","source":"IETF/RFC-1352/RFC-1352.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1351 This memo presents an elaboration of the SNMP administrative model\n set forth in [1]. This model provides a unified conceptual basis for\n administering SNMP protocol entities to support\n\n o authentication and integrity,\n\n o privacy,\n\n o access control, and\n\n o the cooperation of multiple protocol entities.\n\n Please send comments to the SNMP Security Developers mailing list\n (snmp-sec-dev@tis.com).\n\n2. Introduction\n\n This memo presents an elaboration of the SNMP administrative model\n set forth in [1]. It describes how the elaborated administrative\n model is applied to realize effective network management in a variety\n of configurations and environments.\n\n The model described here entails the use of distinct identities for\n peers that exchange SNMP messages. Thus, it represents a departure\n from the community-based administrative model set forth in [1]. By\n unambiguously identifying the so 1351 authentication key management policy trust nested-reference unchanged"},{"id":"IETF RFC 5612","type":"specification","body":"IETF","designation":"RFC 5612","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5612.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5612.txt","https://www.rfc-editor.org/rfc/rfc5612.pdf"],"folder":"IETF/RFC-5612","files":{"txt":{"path":"standards/IETF/RFC-5612/RFC-5612.txt","sha256":"3873596de0a25301c226d4cb2480e0ec0f04604fb09ea0ff110440a9988b898b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Enterprise Number (also known as SMI\n Network Management Private Enterprise Code) for use in documentation.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\n1. Introduction\n\n RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578])\n created a subtree (arc) of object identifiers (OIDs) for ide","scope_keywords":["5612","attribute","attributes","authentication","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null}],"search_text":"IETF RFC 5612 This document describes an Enterprise Number (also known as SMI\n Network Management Private Enterprise Code) for use in documentation.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\n1. Introduction\n\n RFC 1065 [RFC1065] (later superceded by [RFC1155] and [RFC2578])\n created a subtree (arc) of object identifiers (OIDs) for ide 5612 attribute attributes authentication http identification license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1704","type":"specification","body":"IETF","designation":"RFC 1704","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1704.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1704.txt","https://www.rfc-editor.org/rfc/rfc1704.pdf"],"folder":"IETF/RFC-1704","files":{"txt":{"path":"standards/IETF/RFC-1704/RFC-1704.txt","sha256":"4ae6c568caba6866576bdb83c3d885e720f21749610a3a98c9f0b5c79cc5ac8f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Haller\nRequest for Comments: 1704 Bell Communications Research\nCategory: Informational R. Atkinson\n Naval Research Laboratory\n October 1994\n\n On Internet Authentication\n\nStatus of this Memo\n\n This document provides information for the Internet community. This\n memo does not specify an Internet standard of any kind. Distribution\n of this memo is unlimited.\n\n1. INTRODUCTION\n\n The authentication requirements of computing systems and network\n protocols vary greatly with their intended use, accessibility, and\n their network connectivity. This document describes a spectrum of\n authentication technologies and provides suggestions to protocol\n developers on what kinds of authentication might be suitable for some\n kinds of protocols and applications used in the Internet. It is\n hoped that this document will provide useful information to\n interested members of the Internet","scope_keywords":["1704","authentication","authorization","certificate","encryption","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1760","folder":"IETF/RFC-1760","source":"IETF/RFC-1760/RFC-1760.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1938","folder":"IETF/RFC-1938","source":"IETF/RFC-1938/RFC-1938.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2945","folder":"IETF/RFC-2945","source":"IETF/RFC-2945/RFC-2945.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null}],"search_text":"IETF RFC 1704 Network Working Group N. Haller\nRequest for Comments: 1704 Bell Communications Research\nCategory: Informational R. Atkinson\n Naval Research Laboratory\n October 1994\n\n On Internet Authentication\n\nStatus of this Memo\n\n This document provides information for the Internet community. This\n memo does not specify an Internet standard of any kind. Distribution\n of this memo is unlimited.\n\n1. INTRODUCTION\n\n The authentication requirements of computing systems and network\n protocols vary greatly with their intended use, accessibility, and\n their network connectivity. This document describes a spectrum of\n authentication technologies and provides suggestions to protocol\n developers on what kinds of authentication might be suitable for some\n kinds of protocols and applications used in the Internet. It is\n hoped that this document will provide useful information to\n interested members of the Internet 1704 authentication authorization certificate encryption key keys subject nested-reference unchanged"},{"id":"IETF RFC 1068","type":"specification","body":"IETF","designation":"RFC 1068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1068.txt","https://www.rfc-editor.org/rfc/rfc1068.pdf"],"folder":"IETF/RFC-1068","files":{"txt":{"path":"standards/IETF/RFC-1068/RFC-1068.txt","sha256":"a2d8f002ccaade5c92e8ed98011554f80f3a5b7324a8902017ae2e6a97e4d6b0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. DeSchon\nRequest for Comments: 1068 R. Braden\n ISI\n August 1988\n\n Background File Transfer Program (BFTP)\n\nStatus of This Memo\n\n This memo describes an Internet background file transfer service that\n is built upon the third-party transfer model of FTP. No new\n protocols are involved. The purpose of this memo is to stimulate\n discussion on new Internet service modes. Distribution of this memo\n is unlimited.\n\n1. Introduction\n\n For a variety of reasons, file transfer in the Internet has generally\n been implemented as an interactive or \"foreground\" service. That is,\n a user runs the appropriate local FTP user interface program as an\n interactive command and requests a file transfer to occur in real\n time. If the transfer should fail to complete for any reason, the\n user must reissue the transfer request. Foreground file transfer is\n relatively simple to implement -- n","scope_keywords":["1068","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1068 Network Working Group A. DeSchon\nRequest for Comments: 1068 R. Braden\n ISI\n August 1988\n\n Background File Transfer Program (BFTP)\n\nStatus of This Memo\n\n This memo describes an Internet background file transfer service that\n is built upon the third-party transfer model of FTP. No new\n protocols are involved. The purpose of this memo is to stimulate\n discussion on new Internet service modes. Distribution of this memo\n is unlimited.\n\n1. Introduction\n\n For a variety of reasons, file transfer in the Internet has generally\n been implemented as an interactive or \"foreground\" service. That is,\n a user runs the appropriate local FTP user interface program as an\n interactive command and requests a file transfer to occur in real\n time. If the transfer should fail to complete for any reason, the\n user must reissue the transfer request. Foreground file transfer is\n relatively simple to implement -- n 1068 delivery key subject nested-reference unchanged"},{"id":"IETF RFC 1069","type":"specification","body":"IETF","designation":"RFC 1069","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1069.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1069.txt","https://www.rfc-editor.org/rfc/rfc1069.pdf"],"folder":"IETF/RFC-1069","files":{"txt":{"path":"standards/IETF/RFC-1069/RFC-1069.txt","sha256":"f6650d2045432a86bc3564747ea3dca5011dbb7d4fcbe1a72cb2577a664a9e27"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Callon\nRequest for Comments: 1069 DEC\nObsoletes: RFC 986 H.W. Braun\n UMich\n February 1989\n\n Guidelines for the use of Internet-IP addresses in the\n ISO Connectionless-Mode Network Protocol\n\nStatus of This Memo\n\n This RFC suggests an addressing scheme for use with the ISO\n Connectionless Network Protocol (CLNP) in the Internet. This is a\n solution to one of the problems inherent in the use of \"ISO-grams\" in\n the Internet. This RFC suggests a proposed protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This memo is a revision of RFC 986. Changes were made in order to\n allow the addressing used in the CLNP in the Internet to be\n potentially useful for routing in the context of new inter- and\n intra-domain routing protocols, and in the context of large numbers\n of networks and rout","scope_keywords":["1069","algorithm","algorithms","pid","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null}],"search_text":"IETF RFC 1069 Network Working Group R. Callon\nRequest for Comments: 1069 DEC\nObsoletes: RFC 986 H.W. Braun\n UMich\n February 1989\n\n Guidelines for the use of Internet-IP addresses in the\n ISO Connectionless-Mode Network Protocol\n\nStatus of This Memo\n\n This RFC suggests an addressing scheme for use with the ISO\n Connectionless Network Protocol (CLNP) in the Internet. This is a\n solution to one of the problems inherent in the use of \"ISO-grams\" in\n the Internet. This RFC suggests a proposed protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This memo is a revision of RFC 986. Changes were made in order to\n allow the addressing used in the CLNP in the Internet to be\n potentially useful for routing in the context of new inter- and\n intra-domain routing protocols, and in the context of large numbers\n of networks and rout 1069 algorithm algorithms pid policy subject nested-reference unchanged"},{"id":"IETF RFC 1070","type":"specification","body":"IETF","designation":"RFC 1070","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1070.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1070.txt","https://www.rfc-editor.org/rfc/rfc1070.pdf"],"folder":"IETF/RFC-1070","files":{"txt":{"path":"standards/IETF/RFC-1070/RFC-1070.txt","sha256":"5a0494ef7df8cc960dc35753f207546daaaae640032e58eab9a89774268fc88f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hagens\nRequest for Comments: 1070 U of Wiscsonsin - Madison\n N. Hall\n U of Wiscsonsin - Madison\n M. Rose\n The Wollongong Group\n February 1989\n\n Use of the Internet as a Subnetwork for\n Experimentation with the OSI Network Layer\n\nStatus of this Memo\n\n This RFC proposes a scenario for experimentation with the\n International Organization for Standardization (ISO) Open Systems\n Interconnection (OSI) network layer protocols over the Internet and\n requests discussion and suggestions for improvements to this\n scenario. This RFC also proposes the creation of an experimental OSI\n internet. To participate in the experimental OSI internet, a system\n must abide by the agreements set forth in this RFC. Distribution of\n this memo is unlimited.\n\nWARNING\n\n The methods proposed in this RFC are suitable ONLY for experimental\n use on a limited scale. These methods are not suitable ","scope_keywords":["1070","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1070 Network Working Group R. Hagens\nRequest for Comments: 1070 U of Wiscsonsin - Madison\n N. Hall\n U of Wiscsonsin - Madison\n M. Rose\n The Wollongong Group\n February 1989\n\n Use of the Internet as a Subnetwork for\n Experimentation with the OSI Network Layer\n\nStatus of this Memo\n\n This RFC proposes a scenario for experimentation with the\n International Organization for Standardization (ISO) Open Systems\n Interconnection (OSI) network layer protocols over the Internet and\n requests discussion and suggestions for improvements to this\n scenario. This RFC also proposes the creation of an experimental OSI\n internet. To participate in the experimental OSI internet, a system\n must abide by the agreements set forth in this RFC. Distribution of\n this memo is unlimited.\n\nWARNING\n\n The methods proposed in this RFC are suitable ONLY for experimental\n use on a limited scale. These methods are not suitable  1070 profile nested-reference unchanged"},{"id":"IETF RFC 107","type":"specification","body":"IETF","designation":"RFC 107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc107.txt","https://www.rfc-editor.org/rfc/rfc107.pdf"],"folder":"IETF/RFC-107","files":{"txt":{"path":"standards/IETF/RFC-107/RFC-107.txt","sha256":"bbac6681c7a05a29d0feba6c2991cd4bdfe320093a20f0458ba8d603648dd533"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRequest for Comments # 107\n\nNIC # 5806\n\n Output of the Host-Host Protocol\n Glitch Cleaning Committee\n\n UCLA\n 23 March 1971\n\n Robert Bressler\n Steve Crocker\n William Crowter\n Gary Grossman\n Ray Tomlinson\n James Withe\n\n [Page 1]\n\f\nIntroduction\n\nThe Host-Host Protocol Glitch Cleaning Committee met for the second\ntime at UCLA on 8, 9 March 1971, after canvassing the network com-\nmunity. [The result of the (slightly larger) committee's first\nmeeting are documented in RFC #102.] The committee agreed on\nseveral modifications to the protocol in Document #1; these modi-\nfications are listed below.\n\nAt each of the meeting, the committee quickly treated all but one\nof the extant topics. At the first meeting, the bulk of time was\nspent considering the interrupt mechanism, and that discussion is\nsummarized in RFC #102. At the second meeting, the committee spent\nalmost all of its","scope_keywords":["107"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0137","folder":"IETF/RFC-0137","source":"IETF/RFC-0137/RFC-0137.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 137","folder":"IETF/RFC-137","source":"IETF/RFC-137/RFC-137.txt","version":null},{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null}],"search_text":"IETF RFC 107 Network Working Group\nRequest for Comments # 107\n\nNIC # 5806\n\n Output of the Host-Host Protocol\n Glitch Cleaning Committee\n\n UCLA\n 23 March 1971\n\n Robert Bressler\n Steve Crocker\n William Crowter\n Gary Grossman\n Ray Tomlinson\n James Withe\n\n [Page 1]\n\f\nIntroduction\n\nThe Host-Host Protocol Glitch Cleaning Committee met for the second\ntime at UCLA on 8, 9 March 1971, after canvassing the network com-\nmunity. [The result of the (slightly larger) committee's first\nmeeting are documented in RFC #102.] The committee agreed on\nseveral modifications to the protocol in Document #1; these modi-\nfications are listed below.\n\nAt each of the meeting, the committee quickly treated all but one\nof the extant topics. At the first meeting, the bulk of time was\nspent considering the interrupt mechanism, and that discussion is\nsummarized in RFC #102. At the second meeting, the committee spent\nalmost all of its 107 nested-reference unchanged"},{"id":"IETF RFC 137","type":"specification","body":"IETF","designation":"RFC 137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc137.txt","https://www.rfc-editor.org/rfc/rfc137.pdf"],"folder":"IETF/RFC-137","files":{"txt":{"path":"standards/IETF/RFC-137/RFC-137.txt","sha256":"588758aa7a1370fe2d7ef65965e638c8147acfa0ae2b2e74b04ff36d2fc11753"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. C. O'Sullivan\nRequest for Comments: 137 Raytheon\nNIC 6714 30 April 1971\n\n TELNET Protocol\n\n This is a request for comment and is being distributed in advance of\n the Atlantic City meetings for review and comment prior to or during\n discussions on TELNET in preparation for issuing an official\n document.\n\n It is also being distributed so that selected installations planning\n to implement early versions of TELNET will have a common basis for\n such implementation.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation. A few recent suggestions by committee members and\n others have been incorporated where even though not thoroughly\n cleared with all members, the chairman felt that they clarified the\n protocol or would tend to simplify implementation but not\n substantially cha","scope_keywords":["137","driving","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0137","folder":"IETF/RFC-0137","source":"IETF/RFC-0137/RFC-0137.txt","version":null},{"body":"IETF","designation":"RFC 0139","folder":"IETF/RFC-0139","source":"IETF/RFC-0139/RFC-0139.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 139","folder":"IETF/RFC-139","source":"IETF/RFC-139/RFC-139.txt","version":null},{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 137 Network Working Group T. C. O'Sullivan\nRequest for Comments: 137 Raytheon\nNIC 6714 30 April 1971\n\n TELNET Protocol\n\n This is a request for comment and is being distributed in advance of\n the Atlantic City meetings for review and comment prior to or during\n discussions on TELNET in preparation for issuing an official\n document.\n\n It is also being distributed so that selected installations planning\n to implement early versions of TELNET will have a common basis for\n such implementation.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation. A few recent suggestions by committee members and\n others have been incorporated where even though not thoroughly\n cleared with all members, the chairman felt that they clarified the\n protocol or would tend to simplify implementation but not\n substantially cha 137 driving key presentation nested-reference unchanged"},{"id":"IETF RFC 158","type":"specification","body":"IETF","designation":"RFC 158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc158.txt","https://www.rfc-editor.org/rfc/rfc158.pdf"],"folder":"IETF/RFC-158","files":{"pdf":{"path":"standards/IETF/RFC-158/RFC-158.pdf","sha256":"2368c01c522e291004788e16984edfce979478c365b2ff0f3edc9b96d27add6f"},"txt":{"path":"standards/IETF/RFC-158/RFC-158.txt","sha256":"7c6e10cd7e9e9b474786416301a7414c3b71baf1e23113ea607047ecb6461fd3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. O'Sullivan\nRequest for Comments: 158 Raytheon\nNIC: 6768 19 May 1971\n\n TELNET Protocol\n\n This request for comment is being circulated by the TELNET committee\n to solicit comments, evaluation, and requests for modification of the\n proposed protocol presented here. Unless comments are received by\n the writer within two weeks of the date of this RFC, they will not be\n considered in the preparation of official TELNET PROTOCOL document.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation.\n\n Readers are referenced to the following previous releases of\n information:\n\n 1. Conventions for Using an IBM 2741 Terminal or a User Console\n for Access to Network Server HOSTS\n Joel Winett, RFC 110 (NIC #5809)\n\n 2. Response to RFD 110\n Wayne Hathaway, RFC 135 (NIC #6712)\n\n 3. Level III ","scope_keywords":["158","driving","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 196","folder":"IETF/RFC-196","source":"IETF/RFC-196/RFC-196.txt","version":null},{"body":"IETF","designation":"RFC 221","folder":"IETF/RFC-221","source":"IETF/RFC-221/RFC-221.txt","version":null}],"search_text":"IETF RFC 158 Network Working Group T. O'Sullivan\nRequest for Comments: 158 Raytheon\nNIC: 6768 19 May 1971\n\n TELNET Protocol\n\n This request for comment is being circulated by the TELNET committee\n to solicit comments, evaluation, and requests for modification of the\n proposed protocol presented here. Unless comments are received by\n the writer within two weeks of the date of this RFC, they will not be\n considered in the preparation of official TELNET PROTOCOL document.\n\n The proposed document is the result of the work of the committee. It\n represents a TELNET protocol felt to be adequate for initial\n implementation.\n\n Readers are referenced to the following previous releases of\n information:\n\n 1. Conventions for Using an IBM 2741 Terminal or a User Console\n for Access to Network Server HOSTS\n Joel Winett, RFC 110 (NIC #5809)\n\n 2. Response to RFD 110\n Wayne Hathaway, RFC 135 (NIC #6712)\n\n 3. Level III  158 driving key presentation nested-reference unchanged"},{"id":"IETF RFC 1573","type":"specification","body":"IETF","designation":"RFC 1573","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1573.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1573.txt","https://www.rfc-editor.org/rfc/rfc1573.pdf"],"folder":"IETF/RFC-1573","files":{"txt":{"path":"standards/IETF/RFC-1573/RFC-1573.txt","sha256":"7f986e9302112ca43c3887c5109bd1cc94673e95d1bd39b1359fba69565d20ff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 1573 Hughes LAN Systems\nObsoletes: 1229 F. Kastenholz\nCategory: Standards Track FTP Software\n January 1994\n\n Evolution of the Interfaces Group of MIB-II\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 3\n 3 Experience with the Interfaces Group ...................... 3\n 3.1 Areas of Clarification/Revision .........","scope_keywords":["1573","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1757","folder":"IETF/RFC-1757","source":"IETF/RFC-1757/RFC-1757.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2325","folder":"IETF/RFC-2325","source":"IETF/RFC-2325/RFC-2325.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null}],"search_text":"IETF RFC 1573 Network Working Group K. McCloghrie\nRequest for Comments: 1573 Hughes LAN Systems\nObsoletes: 1229 F. Kastenholz\nCategory: Standards Track FTP Software\n January 1994\n\n Evolution of the Interfaces Group of MIB-II\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. The SNMPv2 Network Management Framework .................. 2\n 2.1 Object Definitions ...................................... 3\n 3 Experience with the Interfaces Group ...................... 3\n 3.1 Areas of Clarification/Revision ......... 1573 management nested-reference unchanged"},{"id":"IETF RFC 1071","type":"specification","body":"IETF","designation":"RFC 1071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1071.txt","https://www.rfc-editor.org/rfc/rfc1071.pdf"],"folder":"IETF/RFC-1071","files":{"txt":{"path":"standards/IETF/RFC-1071/RFC-1071.txt","sha256":"e10dfd6816447843d47a7f1b990eba756a791a6308fd5b698a6276075a8e4f9b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braden\nRequest for Comments: 1071 ISI\n D. Borman\n Cray Research\n C. Partridge\n BBN Laboratories\n September 1988\n\n Computing the Internet Checksum\n\nStatus of This Memo\n\n This memo summarizes techniques and algorithms for efficiently\n computing the Internet checksum. It is not a standard, but a set of\n useful implementation techniques. Distribution of this memo is\n unlimited.\n\n1. Introduction\n\n This memo discusses methods for efficiently computing the Internet\n checksum that is used by the standard Internet protocols IP, UDP, and\n TCP.\n\n An efficient checksum implementation is critical to good performance.\n As advances in implementation techniques streamline the rest of the\n protocol processing, the checksum computation becomes one of the\n limiting factors on TCP performance, for example. It is usually\n appropriate to carefully hand-craft the checksum routine, expl","scope_keywords":["1071","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1141","folder":"IETF/RFC-1141","source":"IETF/RFC-1141/RFC-1141.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1624","folder":"IETF/RFC-1624","source":"IETF/RFC-1624/RFC-1624.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1071 Network Working Group R. Braden\nRequest for Comments: 1071 ISI\n D. Borman\n Cray Research\n C. Partridge\n BBN Laboratories\n September 1988\n\n Computing the Internet Checksum\n\nStatus of This Memo\n\n This memo summarizes techniques and algorithms for efficiently\n computing the Internet checksum. It is not a standard, but a set of\n useful implementation techniques. Distribution of this memo is\n unlimited.\n\n1. Introduction\n\n This memo discusses methods for efficiently computing the Internet\n checksum that is used by the standard Internet protocols IP, UDP, and\n TCP.\n\n An efficient checksum implementation is critical to good performance.\n As advances in implementation techniques streamline the rest of the\n protocol processing, the checksum computation becomes one of the\n limiting factors on TCP performance, for example. It is usually\n appropriate to carefully hand-craft the checksum routine, expl 1071 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1141","type":"specification","body":"IETF","designation":"RFC 1141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1141.txt","https://www.rfc-editor.org/rfc/rfc1141.pdf"],"folder":"IETF/RFC-1141","files":{"txt":{"path":"standards/IETF/RFC-1141/RFC-1141.txt","sha256":"ebb18b28d8ba90473b16729b56bce7cd25cc0f5a6c9df2bdf291d647039c9e60"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Mallory\nRequest for Comments: 1141 A. Kullberg\nObsoletes: RFC 1071 BBN Communications\n January 1990\n\n Incremental Updating of the Internet Checksum\n\nStatus of this Memo\n\n This memo correctly describes the incremental update procedure for\n use with the standard Internet checksum. It is intended to replace\n the description of Incremental Update in RFC 1071. This is not a\n standard but rather, an implementation technique. Distribution of\n this memo is unlimited.\n\nDescription\n\n In RFC 1071 on pages 4 and 5, there is a description of a method to\n update the IP checksum in the IP header without having to completely\n recompute the checksum. In particular, the RFC recommends the\n following equation for computing the update checksum C' from the\n original checksum C, and the old and new values of byte m:\n\n C' = C + (-m) + m' = C + (m' - m)\n\n While the equation above is cor","scope_keywords":["1141"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1624","folder":"IETF/RFC-1624","source":"IETF/RFC-1624/RFC-1624.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null}],"search_text":"IETF RFC 1141 Network Working Group T. Mallory\nRequest for Comments: 1141 A. Kullberg\nObsoletes: RFC 1071 BBN Communications\n January 1990\n\n Incremental Updating of the Internet Checksum\n\nStatus of this Memo\n\n This memo correctly describes the incremental update procedure for\n use with the standard Internet checksum. It is intended to replace\n the description of Incremental Update in RFC 1071. This is not a\n standard but rather, an implementation technique. Distribution of\n this memo is unlimited.\n\nDescription\n\n In RFC 1071 on pages 4 and 5, there is a description of a method to\n update the IP checksum in the IP header without having to completely\n recompute the checksum. In particular, the RFC recommends the\n following equation for computing the update checksum C' from the\n original checksum C, and the old and new values of byte m:\n\n C' = C + (-m) + m' = C + (m' - m)\n\n While the equation above is cor 1141 nested-reference unchanged"},{"id":"IETF RFC 1624","type":"specification","body":"IETF","designation":"RFC 1624","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1624.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1624.txt","https://www.rfc-editor.org/rfc/rfc1624.pdf"],"folder":"IETF/RFC-1624","files":{"txt":{"path":"standards/IETF/RFC-1624/RFC-1624.txt","sha256":"19a315a6159370669d0c3e70fb48e47a63012c4fda4f12b3d82bfd76f7d00e05"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an updated technique for incremental computation\n of the standard Internet checksum. It updates the method described\n in RFC 1141.","scope_keywords":["1624","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null}],"search_text":"IETF RFC 1624 This memo describes an updated technique for incremental computation\n of the standard Internet checksum. It updates the method described\n in RFC 1141. 1624 key presentation nested-reference unchanged"},{"id":"IETF RFC 1819","type":"specification","body":"IETF","designation":"RFC 1819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1819.txt","https://www.rfc-editor.org/rfc/rfc1819.pdf"],"folder":"IETF/RFC-1819","files":{"txt":{"path":"standards/IETF/RFC-1819/RFC-1819.txt","sha256":"7f116f5cb645f62e8482cc3c02a9ff7c27c28e527dea4269475c039278e73cc4"}},"tags":["nested-reference","unchanged"],"summary":"This memo contains a revised specification of the Internet STream\n Protocol Version 2 (ST2). ST2 is an experimental resource reservation\n protocol intended to provide end-to-end real-time guarantees over an\n internet. It allows applications to build multi-destination simplex\n data streams with a desired quality of service. The revised version\n of ST2 specified in this memo is called ST2+.\n\n This specification is a product of the STream Protocol Working Group\n of the Internet Engineering Task Force.\n\nDelgrossi & Berger, Editors Experimental [Page 1]\n\f\nRFC 1819 ST2+ Protocol Specification August 1995","scope_keywords":["1819","authorization","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 2098","folder":"IETF/RFC-2098","source":"IETF/RFC-2098/RFC-2098.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 5513","folder":"IETF/RFC-5513","source":"IETF/RFC-5513/RFC-5513.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null}],"search_text":"IETF RFC 1819 This memo contains a revised specification of the Internet STream\n Protocol Version 2 (ST2). ST2 is an experimental resource reservation\n protocol intended to provide end-to-end real-time guarantees over an\n internet. It allows applications to build multi-destination simplex\n data streams with a desired quality of service. The revised version\n of ST2 specified in this memo is called ST2+.\n\n This specification is a product of the STream Protocol Working Group\n of the Internet Engineering Task Force.\n\nDelgrossi & Berger, Editors Experimental [Page 1]\n\f\nRFC 1819 ST2+ Protocol Specification August 1995 1819 authorization identification path nested-reference unchanged"},{"id":"IETF RFC 3376","type":"specification","body":"IETF","designation":"RFC 3376","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3376.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3376.txt","https://www.rfc-editor.org/rfc/rfc3376.pdf"],"folder":"IETF/RFC-3376","files":{"txt":{"path":"standards/IETF/RFC-3376/RFC-3376.txt","sha256":"0f28032de6034da1e13d85f2a34ff9f2956c0e7bb9ad9dd3be84c7ddcde780ed"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Version 3 of the Internet Group Management\n Protocol, IGMPv3. IGMP is the protocol used by IPv4 systems to\n report their IP multicast group memberships to neighboring multicast\n routers. Version 3 of IGMP adds support for \"source filtering\", that\n is, the ability for a system to report interest in receiving packets\n *only* from specific source addresses, or from *all but* specific\n source addresses, sent to a particular multicast address. That\n information may be used by multicast routing protocols to avoid\n delivering multicast packets from specific sources to networks where\n there are no interested receivers.\n\n This document obsoletes RFC 2236.\n\nCain, et. al. Standards Track [Page 1]\n\f\nRFC 3376 IGMPv3 October 2002","scope_keywords":["3376","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3678","folder":"IETF/RFC-3678","source":"IETF/RFC-3678/RFC-3678.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 3376 This document specifies Version 3 of the Internet Group Management\n Protocol, IGMPv3. IGMP is the protocol used by IPv4 systems to\n report their IP multicast group memberships to neighboring multicast\n routers. Version 3 of IGMP adds support for \"source filtering\", that\n is, the ability for a system to report interest in receiving packets\n *only* from specific source addresses, or from *all but* specific\n source addresses, sent to a particular multicast address. That\n information may be used by multicast routing protocols to avoid\n delivering multicast packets from specific sources to networks where\n there are no interested receivers.\n\n This document obsoletes RFC 2236.\n\nCain, et. al. Standards Track [Page 1]\n\f\nRFC 3376 IGMPv3 October 2002 3376 key management nested-reference unchanged"},{"id":"IETF RFC 3828","type":"specification","body":"IETF","designation":"RFC 3828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3828.txt","https://www.rfc-editor.org/rfc/rfc3828.pdf"],"folder":"IETF/RFC-3828","files":{"txt":{"path":"standards/IETF/RFC-3828/RFC-3828.txt","sha256":"9c7b45701ca9776d5a8f75a346d0f3638898739aa914276cc0a5f87f7e4cba06"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Lightweight User Datagram Protocol (UDP-\n Lite), which is similar to the User Datagram Protocol (UDP) (RFC\n 768), but can also serve applications in error-prone network\n environments that prefer to have partially damaged payloads delivered\n rather than discarded. If this feature is not used, UDP-Lite is\n semantically identical to UDP.\n\nLarzon, et al. Standards Track [Page 1]\n\f\nRFC 3828 UDP-Lite Protocol July 2004","scope_keywords":["3828","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 3828 This document describes the Lightweight User Datagram Protocol (UDP-\n Lite), which is similar to the User Datagram Protocol (UDP) (RFC\n 768), but can also serve applications in error-prone network\n environments that prefer to have partially damaged payloads delivered\n rather than discarded. If this feature is not used, UDP-Lite is\n semantically identical to UDP.\n\nLarzon, et al. Standards Track [Page 1]\n\f\nRFC 3828 UDP-Lite Protocol July 2004 3828 delivery key nested-reference unchanged"},{"id":"IETF RFC 6296","type":"specification","body":"IETF","designation":"RFC 6296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6296.txt","https://www.rfc-editor.org/rfc/rfc6296.pdf"],"folder":"IETF/RFC-6296","files":{"txt":{"path":"standards/IETF/RFC-6296/RFC-6296.txt","sha256":"7f1379e361fb29c1de16c598eef4c13c99eb062edc14c9833f514037af86de2a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a stateless, transport-agnostic IPv6-to-IPv6\n Network Prefix Translation (NPTv6) function that provides the\n address-independence benefit associated with IPv4-to-IPv4 NAT\n (NAPT44) and provides a 1:1 relationship between addresses in the\n \"inside\" and \"outside\" prefixes, preserving end-to-end reachability\n at the network layer.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidat","scope_keywords":["6296","algorithm","authentication","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6296 This document describes a stateless, transport-agnostic IPv6-to-IPv6\n Network Prefix Translation (NPTv6) function that provides the\n address-independence benefit associated with IPv4-to-IPv4 NAT\n (NAPT44) and provides a 1:1 relationship between addresses in the\n \"inside\" and \"outside\" prefixes, preserving end-to-end reachability\n at the network layer.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidat 6296 algorithm authentication http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1185","type":"specification","body":"IETF","designation":"RFC 1185","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1185.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1185.txt","https://www.rfc-editor.org/rfc/rfc1185.pdf"],"folder":"IETF/RFC-1185","files":{"txt":{"path":"standards/IETF/RFC-1185/RFC-1185.txt","sha256":"e9659897b6aa184a1fe1018c601152f5dd9b3d766fa4c0d7e031d0eea3f6d55d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Jacobson\nRequest for Comments: 1185 LBL\n R. Braden\n ISI\n L. Zhang\n PARC\n October 1990\n\n TCP Extension for High-Speed Paths\n\nStatus of This Memo\n\n This memo describes an Experimental Protocol extension to TCP for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nSummary\n\n This memo describes a small extension to TCP to support reliable\n operation over very high-speed paths, using sender timestamps\n transmitted using the TCP Echo option proposed in RFC-1072.\n\n1. INTRODUCTION\n\n TCP uses positive acknowledgments and retransmissions to provide\n reliable end-to-end delivery over a full-duplex virtual circuit\n called a connection [Postel81]. A connection is def","scope_keywords":["1185","algorithm","delivery","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1263","folder":"IETF/RFC-1263","source":"IETF/RFC-1263/RFC-1263.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null}],"search_text":"IETF RFC 1185 Network Working Group V. Jacobson\nRequest for Comments: 1185 LBL\n R. Braden\n ISI\n L. Zhang\n PARC\n October 1990\n\n TCP Extension for High-Speed Paths\n\nStatus of This Memo\n\n This memo describes an Experimental Protocol extension to TCP for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nSummary\n\n This memo describes a small extension to TCP to support reliable\n operation over very high-speed paths, using sender timestamps\n transmitted using the TCP Echo option proposed in RFC-1072.\n\n1. INTRODUCTION\n\n TCP uses positive acknowledgments and retransmissions to provide\n reliable end-to-end delivery over a full-duplex virtual circuit\n called a connection [Postel81]. A connection is def 1185 algorithm delivery path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 1693","type":"specification","body":"IETF","designation":"RFC 1693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1693.txt","https://www.rfc-editor.org/rfc/rfc1693.pdf"],"folder":"IETF/RFC-1693","files":{"txt":{"path":"standards/IETF/RFC-1693/RFC-1693.txt","sha256":"6f62c6bf0fe250a7342d752116b48415a88d3df7e3a8215532ef1ef92b815093"}},"tags":["nested-reference","unchanged"],"summary":"This RFC introduces a new transport mechanism for TCP based upon\n partial ordering. The aim is to present the concepts of partial\n ordering and promote discussions on its usefulness in network\n communications. Distribution of this memo is unlimited.","scope_keywords":["1693","algorithm","delivery","key","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1693 This RFC introduces a new transport mechanism for TCP based upon\n partial ordering. The aim is to present the concepts of partial\n ordering and promote discussions on its usefulness in network\n communications. Distribution of this memo is unlimited. 1693 algorithm delivery key management profile nested-reference unchanged"},{"id":"IETF RFC 4413","type":"specification","body":"IETF","designation":"RFC 4413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4413.txt","https://www.rfc-editor.org/rfc/rfc4413.pdf"],"folder":"IETF/RFC-4413","files":{"txt":{"path":"standards/IETF/RFC-4413/RFC-4413.txt","sha256":"20bf67cd41051ca51488285ede3afcdff3bc6f9199ba992134c412a8be4c1814"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes TCP/IP field behavior in the context of header\n compression. Header compression is possible because most header\n fields do not vary randomly from packet to packet. Many of the\n fields exhibit static behavior or change in a more or less\n predictable way. When a header compression scheme is designed, it is\n of fundamental importance to understand the behavior of the fields in\n detail. An example of this analysis can be seen in RFC 3095. This\n memo performs a similar role for the compression of TCP/IP headers.\n\nWest & McCann Informational [Page 1]\n\f\nRFC 4413 TCP/IP Field Behavior March 2006","scope_keywords":["4413","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 4413 This memo describes TCP/IP field behavior in the context of header\n compression. Header compression is possible because most header\n fields do not vary randomly from packet to packet. Many of the\n fields exhibit static behavior or change in a more or less\n predictable way. When a header compression scheme is designed, it is\n of fundamental importance to understand the behavior of the fields in\n detail. An example of this analysis can be seen in RFC 3095. This\n memo performs a similar role for the compression of TCP/IP headers.\n\nWest & McCann Informational [Page 1]\n\f\nRFC 4413 TCP/IP Field Behavior March 2006 4413 identification profile nested-reference unchanged"},{"id":"IETF RFC 6247","type":"specification","body":"IETF","designation":"RFC 6247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6247.txt","https://www.rfc-editor.org/rfc/rfc6247.pdf"],"folder":"IETF/RFC-6247","files":{"txt":{"path":"standards/IETF/RFC-6247/RFC-6247.txt","sha256":"12211f91bfd80320926cb27d24effb23d401ef0ce1ebefb02efacd4ca1086d0b"}},"tags":["nested-reference","unchanged"],"summary":"This document reclassifies several TCP extensions that have never\n seen widespread use to Historic status. The affected RFCs are RFC\n 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and\n RFC 1693.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6247.\n\nCopyright Notice\n\n ","scope_keywords":["6247","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6247 This document reclassifies several TCP extensions that have never\n seen widespread use to Historic status. The affected RFCs are RFC\n 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and\n RFC 1693.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6247.\n\nCopyright Notice\n\n  6247 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7413","type":"specification","body":"IETF","designation":"RFC 7413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7413.txt","https://www.rfc-editor.org/rfc/rfc7413.pdf"],"folder":"IETF/RFC-7413","files":{"txt":{"path":"standards/IETF/RFC-7413/RFC-7413.txt","sha256":"ea094553d58f53df919071b597d3dd0ac1ab512e297271a89463101f8bf6eb16"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an experimental TCP mechanism called TCP Fast\n Open (TFO). TFO allows data to be carried in the SYN and SYN-ACK\n packets and consumed by the receiving end during the initial\n connection handshake, and saves up to one full round-trip time (RTT)\n compared to the standard TCP, which requires a three-way handshake\n (3WHS) to complete before data can be exchanged. However, TFO\n deviates from the standard TCP semantics, since the data in the SYN\n could be replayed to an application in some rare circumstances.\n Applications should not use TFO unless they can tolerate this issue,\n as detailed in the Applicability section.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This docu","scope_keywords":["7413","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7413 This document describes an experimental TCP mechanism called TCP Fast\n Open (TFO). TFO allows data to be carried in the SYN and SYN-ACK\n packets and consumed by the receiving end during the initial\n connection handshake, and saves up to one full round-trip time (RTT)\n compared to the standard TCP, which requires a three-way handshake\n (3WHS) to complete before data can be exchanged. However, TFO\n deviates from the standard TCP semantics, since the data in the SYN\n could be replayed to an application in some rare circumstances.\n Applications should not use TFO unless they can tolerate this issue,\n as detailed in the Applicability section.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This docu 7413 http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 1073","type":"specification","body":"IETF","designation":"RFC 1073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1073.txt","https://www.rfc-editor.org/rfc/rfc1073.pdf"],"folder":"IETF/RFC-1073","files":{"txt":{"path":"standards/IETF/RFC-1073/RFC-1073.txt","sha256":"268f69a6a486bea164f8b68513b478cb1c1ab4e3998635e7003b26bd3fbd929d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Waitzman\nRequest For Comments: 1073 BBN STC\n October 1988\n\n Telnet Window Size Option\n\nStatus of this Memo\n\n This RFC describes a proposed Telnet option to allow a client to\n convey window size to a Telnet server. Distribution of this memo is\n unlimited.\n\n1. Command Name and Option Code\n\n Name = NAWS (Negotiate About Window Size)\n\n Code = 31\n\n2. Command Meanings\n\n IAC WILL NAWS\n\n Sent by the Telnet client to suggest that NAWS be used.\n\n IAC WON'T NAWS\n\n Sent by the Telnet client to refuse to use NAWS.\n\n IAC DO NAWS\n\n Sent by the Telnet server to suggest that NAWS be used.\n\n IAC DON'T NAWS\n\n Sent by the Telnet server to refuse to use NAWS.\n\n IAC SB NAWS IAC SE\n\n Sent by the Telnet client to inform the Telnet server of the\n window width and height.\n\n The window size information is conveyed via this option from the\n Telnet client to the Telnet server. The informatio","scope_keywords":["1073"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1073 Network Working Group D. Waitzman\nRequest For Comments: 1073 BBN STC\n October 1988\n\n Telnet Window Size Option\n\nStatus of this Memo\n\n This RFC describes a proposed Telnet option to allow a client to\n convey window size to a Telnet server. Distribution of this memo is\n unlimited.\n\n1. Command Name and Option Code\n\n Name = NAWS (Negotiate About Window Size)\n\n Code = 31\n\n2. Command Meanings\n\n IAC WILL NAWS\n\n Sent by the Telnet client to suggest that NAWS be used.\n\n IAC WON'T NAWS\n\n Sent by the Telnet client to refuse to use NAWS.\n\n IAC DO NAWS\n\n Sent by the Telnet server to suggest that NAWS be used.\n\n IAC DON'T NAWS\n\n Sent by the Telnet server to refuse to use NAWS.\n\n IAC SB NAWS IAC SE\n\n Sent by the Telnet client to inform the Telnet server of the\n window width and height.\n\n The window size information is conveyed via this option from the\n Telnet client to the Telnet server. The informatio 1073 nested-reference unchanged"},{"id":"IETF RFC 1116","type":"specification","body":"IETF","designation":"RFC 1116","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1116.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1116.txt","https://www.rfc-editor.org/rfc/rfc1116.pdf"],"folder":"IETF/RFC-1116","files":{"txt":{"path":"standards/IETF/RFC-1116/RFC-1116.txt","sha256":"005c7bb0ca3ac071d14c1e1738dd06c8ed99ef1ca890adbbf4f951d68634d9c4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Engineering Task Force\nRequest for Comments: 1116 Telnet Linemode Working Group\n D. Borman, Editor\n Cray Research, Inc.\n August 1989\n\n Telnet Linemode Option\n\nStatus of this Memo\n\n This RFC describes a proposed elective standard for the Internet\n community. Hosts on the Internet that support Linemode within the\n Telnet protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\nOverview\n\n Linemode Telnet is a way of doing terminal character processing on\n the client side of a Telnet connection. While in Linemode with\n editing enabled for the local side, network traffic is reduced to a\n couple of packets per command line, rather than a couple of packets\n per character typed. This is very useful for long delay networks,\n because the user has local response time while typing the command\n line, and only incurs the netwo","scope_keywords":["1116"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1143","folder":"IETF/RFC-1143","source":"IETF/RFC-1143/RFC-1143.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null}],"search_text":"IETF RFC 1116 Network Working Group Internet Engineering Task Force\nRequest for Comments: 1116 Telnet Linemode Working Group\n D. Borman, Editor\n Cray Research, Inc.\n August 1989\n\n Telnet Linemode Option\n\nStatus of this Memo\n\n This RFC describes a proposed elective standard for the Internet\n community. Hosts on the Internet that support Linemode within the\n Telnet protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\nOverview\n\n Linemode Telnet is a way of doing terminal character processing on\n the client side of a Telnet connection. While in Linemode with\n editing enabled for the local side, network traffic is reduced to a\n couple of packets per command line, rather than a couple of packets\n per character typed. This is very useful for long delay networks,\n because the user has local response time while typing the command\n line, and only incurs the netwo 1116 nested-reference unchanged"},{"id":"IETF RFC 1184","type":"specification","body":"IETF","designation":"RFC 1184","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1184.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1184.txt","https://www.rfc-editor.org/rfc/rfc1184.pdf"],"folder":"IETF/RFC-1184","files":{"txt":{"path":"standards/IETF/RFC-1184/RFC-1184.txt","sha256":"5960a6e92faadc5bb63a03cc60494debe9a8c2d2b4e90bf35bbfedb5e32a8eb1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Telnet Working Group\nRequest for Comments: 1184 D. Borman, Editor\nObsoletes: RFC 1116 Cray Research, Inc.\n October 1990\n\n Telnet Linemode Option\n\nStatus of this Memo\n\n This memo describes a Draft Standard for the Internet community, and\n requests discussion and suggestions for improvements. This RFC\n specifies an IAB standards track protocol for the Internet community.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nChanges from RFC1116:\n\n Two new mode bits have been added, SOFTTAB and LITECHO. These\n bits allow the server to give the client some advise on how to\n echo tabs and non-printable characters.\n\n Several new special character mappings have been added for cursor\n motion when visual editing is supported. These are: Move cursor\n o","scope_keywords":["1184"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1372","folder":"IETF/RFC-1372","source":"IETF/RFC-1372/RFC-1372.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1184 Network Working Group Telnet Working Group\nRequest for Comments: 1184 D. Borman, Editor\nObsoletes: RFC 1116 Cray Research, Inc.\n October 1990\n\n Telnet Linemode Option\n\nStatus of this Memo\n\n This memo describes a Draft Standard for the Internet community, and\n requests discussion and suggestions for improvements. This RFC\n specifies an IAB standards track protocol for the Internet community.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nChanges from RFC1116:\n\n Two new mode bits have been added, SOFTTAB and LITECHO. These\n bits allow the server to give the client some advise on how to\n echo tabs and non-printable characters.\n\n Several new special character mappings have been added for cursor\n motion when visual editing is supported. These are: Move cursor\n o 1184 nested-reference unchanged"},{"id":"IETF RFC 1585","type":"specification","body":"IETF","designation":"RFC 1585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1585.txt","https://www.rfc-editor.org/rfc/rfc1585.pdf"],"folder":"IETF/RFC-1585","files":{"txt":{"path":"standards/IETF/RFC-1585/RFC-1585.txt","sha256":"955c6ed315f0bc68683dac0a11acd69028b107e26f9e171eee34a7d244824d43"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents how the MOSPF protocol satisfies the requirements\n imposed on Internet routing protocols by \"Internet Engineering Task\n Force internet routing protocol standardization criteria\" ([RFC\n 1264]).\n\n Please send comments to mospf@gated.cornell.edu.\n\n1. Summary of MOSPF features and algorithms\n\n MOSPF is an enhancement of OSPF V2, enabling the routing of IP\n multicast datagrams. OSPF is a link-state (unicast) routing\n protocol, providing a database describing the Autonomous System's\n topology. IP multicast is an extension of LAN multicasting to a\n TCP/IP Internet. IP Multicast permits an IP host to send a single\n datagram (called an IP multicast datagram) that will be delivered to\n multiple destinations. IP multicast datagrams are identified as\n those packets whose destinations are class D IP addresses (i.e.,\n addresses whose first byte lies in the range 224-239 inclusive).","scope_keywords":["1585","algorithm","algorithms","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null}],"search_text":"IETF RFC 1585 This memo documents how the MOSPF protocol satisfies the requirements\n imposed on Internet routing protocols by \"Internet Engineering Task\n Force internet routing protocol standardization criteria\" ([RFC\n 1264]).\n\n Please send comments to mospf@gated.cornell.edu.\n\n1. Summary of MOSPF features and algorithms\n\n MOSPF is an enhancement of OSPF V2, enabling the routing of IP\n multicast datagrams. OSPF is a link-state (unicast) routing\n protocol, providing a database describing the Autonomous System's\n topology. IP multicast is an extension of LAN multicasting to a\n TCP/IP Internet. IP Multicast permits an IP host to send a single\n datagram (called an IP multicast datagram) that will be delivered to\n multiple destinations. IP multicast datagrams are identified as\n those packets whose destinations are class D IP addresses (i.e.,\n addresses whose first byte lies in the range 224-239 inclusive). 1585 algorithm algorithms management path nested-reference unchanged"},{"id":"IETF RFC 2022","type":"specification","body":"IETF","designation":"RFC 2022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2022.txt","https://www.rfc-editor.org/rfc/rfc2022.pdf"],"folder":"IETF/RFC-2022","files":{"txt":{"path":"standards/IETF/RFC-2022/RFC-2022.txt","sha256":"ce96154d86444c76759b12df696cba07519a9392f68038ca7605ef065674d47d"}},"tags":["nested-reference","unchanged"],"summary":"Mapping the connectionless IP multicast service over the connection\n oriented ATM services provided by UNI 3.0/3.1 is a non-trivial task.\n This memo describes a mechanism to support the multicast needs of\n Layer 3 protocols in general, and describes its application to IP\n multicasting in particular.\n\n ATM based IP hosts and routers use a Multicast Address Resolution\n Server (MARS) to support RFC 1112 style Level 2 IP multicast over the\n ATM Forum's UNI 3.0/3.1 point to multipoint connection service.\n Clusters of endpoints share a MARS and use it to track and\n disseminate information identifying the nodes listed as receivers for\n given multicast groups. This allows endpoints to establish and manage\n point to multipoint VCs when transmitting to the group.\n\n The MARS behaviour allows Layer 3 multicasting to be supported using\n either meshes of VCs or ATM level multicast servers. This choice","scope_keywords":["2022","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2098","folder":"IETF/RFC-2098","source":"IETF/RFC-2098/RFC-2098.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2602","folder":"IETF/RFC-2602","source":"IETF/RFC-2602/RFC-2602.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2022 Mapping the connectionless IP multicast service over the connection\n oriented ATM services provided by UNI 3.0/3.1 is a non-trivial task.\n This memo describes a mechanism to support the multicast needs of\n Layer 3 protocols in general, and describes its application to IP\n multicasting in particular.\n\n ATM based IP hosts and routers use a Multicast Address Resolution\n Server (MARS) to support RFC 1112 style Level 2 IP multicast over the\n ATM Forum's UNI 3.0/3.1 point to multipoint connection service.\n Clusters of endpoints share a MARS and use it to track and\n disseminate information identifying the nodes listed as receivers for\n given multicast groups. This allows endpoints to establish and manage\n point to multipoint VCs when transmitting to the group.\n\n The MARS behaviour allows Layer 3 multicasting to be supported using\n either meshes of VCs or ATM level multicast servers. This choice 2022 key management path nested-reference unchanged"},{"id":"IETF RFC 2902","type":"specification","body":"IETF","designation":"RFC 2902","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2902.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2902.txt","https://www.rfc-editor.org/rfc/rfc2902.pdf"],"folder":"IETF/RFC-2902","files":{"txt":{"path":"standards/IETF/RFC-2902/RFC-2902.txt","sha256":"275587ff6ade461615bb81a88a56d558012c200f98b886f190d1afa8ca2e660a"}},"tags":["nested-reference","unchanged"],"summary":"This document is an overview of a Routing workshop held by the\n Internet Architecture Board (IAB) during March 25-27, 1998. The\n major points of discussion are listed, along with some conclusions\n and action items for many of the points of discussion.","scope_keywords":["2902","http","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2902 This document is an overview of a Routing workshop held by the\n Internet Architecture Board (IAB) during March 25-27, 1998. The\n major points of discussion are listed, along with some conclusions\n and action items for many of the points of discussion. 2902 http policy nested-reference unchanged"},{"id":"IETF RFC 2932","type":"specification","body":"IETF","designation":"RFC 2932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2932.txt","https://www.rfc-editor.org/rfc/rfc2932.pdf"],"folder":"IETF/RFC-2932","files":{"txt":{"path":"standards/IETF/RFC-2932/RFC-2932.txt","sha256":"9e9006469df090caa6da2394d45ed48a72642f5a6998f31b9af93491b93904f3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing IP\n Multicast Routing for IPv4, independent of the specific multicast\n routing protocol in use.","scope_keywords":["2932","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null}],"search_text":"IETF RFC 2932 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing IP\n Multicast Routing for IPv4, independent of the specific multicast\n routing protocol in use. 2932 management nested-reference unchanged"},{"id":"IETF RFC 3791","type":"specification","body":"IETF","designation":"RFC 3791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3791.txt","https://www.rfc-editor.org/rfc/rfc3791.pdf"],"folder":"IETF/RFC-3791","files":{"txt":{"path":"standards/IETF/RFC-3791/RFC-3791.txt","sha256":"0b405284dc0a0bd9a725e957152f380139e2de524d34687718dd5ed65f7ca964"}},"tags":["nested-reference","unchanged"],"summary":"This investigation work seeks to document all usage of IPv4 addresses\n in currently deployed IETF Routing Area documented standards. In\n order to successfully transition from an all IPv4 Internet to an all\n IPv6 Internet, many interim steps will be taken. One of these steps\n is the evolution of current protocols that have IPv4 dependencies.\n It is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented.","scope_keywords":["3791","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null}],"search_text":"IETF RFC 3791 This investigation work seeks to document all usage of IPv4 addresses\n in currently deployed IETF Routing Area documented standards. In\n order to successfully transition from an all IPv4 Internet to an all\n IPv6 Internet, many interim steps will be taken. One of these steps\n is the evolution of current protocols that have IPv4 dependencies.\n It is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented. 3791 management policy nested-reference unchanged"},{"id":"IETF RFC 3973","type":"specification","body":"IETF","designation":"RFC 3973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3973.txt","https://www.rfc-editor.org/rfc/rfc3973.pdf"],"folder":"IETF/RFC-3973","files":{"txt":{"path":"standards/IETF/RFC-3973/RFC-3973.txt","sha256":"8b9f94e8036219630d1a5af57bb46d26f860d2f8eb1a9ccaa73287072c827fdf"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Protocol Independent Multicast - Dense Mode\n (PIM-DM). PIM-DM is a multicast routing protocol that uses the\n underlying unicast routing information base to flood multicast\n datagrams to all multicast routers. Prune messages are used to\n prevent future messages from propagating to routers without group\n membership information.\n\nAdams, et al. Experimental [Page 1]\n\f\nRFC 3973 PIM - Dense Mode January 2005","scope_keywords":["3973","algorithm","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5384","folder":"IETF/RFC-5384","source":"IETF/RFC-5384/RFC-5384.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null}],"search_text":"IETF RFC 3973 This document specifies Protocol Independent Multicast - Dense Mode\n (PIM-DM). PIM-DM is a multicast routing protocol that uses the\n underlying unicast routing information base to flood multicast\n datagrams to all multicast routers. Prune messages are used to\n prevent future messages from propagating to routers without group\n membership information.\n\nAdams, et al. Experimental [Page 1]\n\f\nRFC 3973 PIM - Dense Mode January 2005 3973 algorithm authentication nested-reference unchanged"},{"id":"IETF RFC 4607","type":"specification","body":"IETF","designation":"RFC 4607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4607.txt","https://www.rfc-editor.org/rfc/rfc4607.pdf"],"folder":"IETF/RFC-4607","files":{"txt":{"path":"standards/IETF/RFC-4607/RFC-4607.txt","sha256":"e1691ca97702fb9747e1db51a55810c3f82f14a64382a59884a1a511c76c58e0"}},"tags":["nested-reference","unchanged"],"summary":"IP version 4 (IPv4) addresses in the 232/8 (232.0.0.0 to\n 232.255.255.255) range are designated as source-specific multicast\n (SSM) destination addresses and are reserved for use by source-\n specific applications and protocols. For IP version 6 (IPv6), the\n address prefix FF3x::/32 is reserved for source-specific multicast\n use. This document defines an extension to the Internet network\n service that applies to datagrams sent to SSM addresses and defines\n the host and router requirements to support this extension.\n\nHolbrook & Cain Standards Track [Page 1]\n\f\nRFC 4607 Source-Specific Multicast August 2006","scope_keywords":["4607","algorithm","algorithms","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5496","folder":"IETF/RFC-5496","source":"IETF/RFC-5496/RFC-5496.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 4607 IP version 4 (IPv4) addresses in the 232/8 (232.0.0.0 to\n 232.255.255.255) range are designated as source-specific multicast\n (SSM) destination addresses and are reserved for use by source-\n specific applications and protocols. For IP version 6 (IPv6), the\n address prefix FF3x::/32 is reserved for source-specific multicast\n use. This document defines an extension to the Internet network\n service that applies to datagrams sent to SSM addresses and defines\n the host and router requirements to support this extension.\n\nHolbrook & Cain Standards Track [Page 1]\n\f\nRFC 4607 Source-Specific Multicast August 2006 4607 algorithm algorithms delivery path nested-reference unchanged"},{"id":"IETF RFC 1125","type":"specification","body":"IETF","designation":"RFC 1125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1125.txt","https://www.rfc-editor.org/rfc/rfc1125.pdf"],"folder":"IETF/RFC-1125","files":{"pdf":{"path":"standards/IETF/RFC-1125/RFC-1125.pdf","sha256":"4cef094f214e7b2fe3057c80529c2717b94f0497bc4ff76e186ccc14a84841de"},"txt":{"path":"standards/IETF/RFC-1125/RFC-1125.txt","sha256":"6da486dd6455304c31b25bac4c6ad12384c2cb885abd0aed96f7b206d051ab4d"}},"tags":["nested-reference","unchanged"],"summary":"Efforts are now underway to develop a new generation of routing\n protocol that will allow each Administrative Domain (AD) in the\n growing Internet (and internets in general) to independently express\n and enforce policies regarding the flow of packets to, from, and\n through its resources. (FOOTNOTE 1: The material presented here\n incorporates discussions held with members of the IAB Autonomous\n Networks Research Group and the Open Routing Working Group.) This\n document articulates the requirements for policy based routing and\n should be used as input to the functional specification and\n evaluation of proposed protocols.\n\n Two critical assumptions will shape the type of routing mechanism\n that is devised: (1) the topological organization of ADs, and (2) the\n type and variability of policies expressed by ADs. After justifying\n our assumptions regarding AD topology we present a taxonomy, and","scope_keywords":["1125","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null}],"search_text":"IETF RFC 1125 Efforts are now underway to develop a new generation of routing\n protocol that will allow each Administrative Domain (AD) in the\n growing Internet (and internets in general) to independently express\n and enforce policies regarding the flow of packets to, from, and\n through its resources. (FOOTNOTE 1: The material presented here\n incorporates discussions held with members of the IAB Autonomous\n Networks Research Group and the Open Routing Working Group.) This\n document articulates the requirements for policy based routing and\n should be used as input to the functional specification and\n evaluation of proposed protocols.\n\n Two critical assumptions will shape the type of routing mechanism\n that is devised: (1) the topological organization of ADs, and (2) the\n type and variability of policies expressed by ADs. After justifying\n our assumptions regarding AD topology we present a taxonomy, and 1125 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 1078","type":"specification","body":"IETF","designation":"RFC 1078","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1078.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1078.txt","https://www.rfc-editor.org/rfc/rfc1078.pdf"],"folder":"IETF/RFC-1078","files":{"txt":{"path":"standards/IETF/RFC-1078/RFC-1078.txt","sha256":"e2333a4cce84e829bbabfbd5ceb807d8283d44965ab365610c6f84564a2a153e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Lottor\nRequest For Comments: 1078 SRI-NIC\n November 1988\n\n TCP Port Service Multiplexer (TCPMUX)\n\nStatus of this Memo\n\n This RFC proposes an Internet standard which can be used by future\n TCP services instead of using 'well-known ports'. Distribution of\n this memo is unlimited.\n\nOverview\n\n Ports are used in the TCP to name the ends of logical connections\n which carry long term conversations. For the purpose of providing\n services to unknown callers, a service contact port is defined. The\n contact port is sometimes called the \"well-known port\". Standard TCP\n services are assigned unique well-known port numbers in the range of\n 0-255. These ports are of limited number and are typically only\n assigned to official Internet protocols.\n\n This RFC defines a protocol to contact multiple services on a single\n well-known TCP port using a service name instead of a well-know","scope_keywords":["1078","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1078 Network Working Group M. Lottor\nRequest For Comments: 1078 SRI-NIC\n November 1988\n\n TCP Port Service Multiplexer (TCPMUX)\n\nStatus of this Memo\n\n This RFC proposes an Internet standard which can be used by future\n TCP services instead of using 'well-known ports'. Distribution of\n this memo is unlimited.\n\nOverview\n\n Ports are used in the TCP to name the ends of logical connections\n which carry long term conversations. For the purpose of providing\n services to unknown callers, a service contact port is defined. The\n contact port is sometimes called the \"well-known port\". Standard TCP\n services are assigned unique well-known port numbers in the range of\n 0-255. These ports are of limited number and are typically only\n assigned to official Internet protocols.\n\n This RFC defines a protocol to contact multiple services on a single\n well-known TCP port using a service name instead of a well-know 1078 crl nested-reference unchanged"},{"id":"IETF RFC 1079","type":"specification","body":"IETF","designation":"RFC 1079","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1079.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1079.txt","https://www.rfc-editor.org/rfc/rfc1079.pdf"],"folder":"IETF/RFC-1079","files":{"txt":{"path":"standards/IETF/RFC-1079/RFC-1079.txt","sha256":"e03e4aa7ca7f1f91a2f5993ba419980a87ab03e25ee20264ced85401edd0133e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Hedrick\nRequest for Comments: 1079 Rutgers University\n December 1988\n\n Telnet Terminal Speed Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that exchange terminal speed information within the\n Telnet protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\n This standard is modelled on RFC 930 [1], the telnet terminal type\n option. Much of the text of this document is copied from that RFC.\n\nMotivation\n\n Most operating systems have provisions to keep track of the speed\n (bit rate) of directly attached terminals and modems. This\n information is used to control various timing-dependent display\n processes, e.g., the number of padding characters used for delay.\n Some software also has user interfaces that are tuned differently for\n fast and slow terminals. The ","scope_keywords":["1079","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1096","folder":"IETF/RFC-1096","source":"IETF/RFC-1096/RFC-1096.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1079 Network Working Group C. Hedrick\nRequest for Comments: 1079 Rutgers University\n December 1988\n\n Telnet Terminal Speed Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that exchange terminal speed information within the\n Telnet protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\n This standard is modelled on RFC 930 [1], the telnet terminal type\n option. Much of the text of this document is copied from that RFC.\n\nMotivation\n\n Most operating systems have provisions to keep track of the speed\n (bit rate) of directly attached terminals and modems. This\n information is used to control various timing-dependent display\n processes, e.g., the number of padding characters used for delay.\n Some software also has user interfaces that are tuned differently for\n fast and slow terminals. The  1079 presentation nested-reference unchanged"},{"id":"IETF RFC 1096","type":"specification","body":"IETF","designation":"RFC 1096","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1096.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1096.txt","https://www.rfc-editor.org/rfc/rfc1096.pdf"],"folder":"IETF/RFC-1096","files":{"txt":{"path":"standards/IETF/RFC-1096/RFC-1096.txt","sha256":"f6c9e54a44757f86bc27aeb67112848727b73420f258e34d24e9f1d05c9a9d14"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Marcy\nRequest for Comments: 1096 Carnegie Mellon University\n March 1989\n\n Telnet X Display Location Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that transmit the X display location within the Telnet\n protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\n This standard is modelled on RFC 1079 [1], the telnet terminal speed\n option. Much of the text of this document is copied from that RFC.\n\nMotivation\n\n When a user is running the Telnet client under the X window system,\n it is useful for the remote Telnet to know the X display location of\n that client. For example, the user might wish to start other X\n applications from the remote host using the same display location as\n the Telnet client. The purpose of this option is to make this\n information availa","scope_keywords":["1096"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1408","folder":"IETF/RFC-1408","source":"IETF/RFC-1408/RFC-1408.txt","version":null},{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1096 Network Working Group G. Marcy\nRequest for Comments: 1096 Carnegie Mellon University\n March 1989\n\n Telnet X Display Location Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that transmit the X display location within the Telnet\n protocol are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\n This standard is modelled on RFC 1079 [1], the telnet terminal speed\n option. Much of the text of this document is copied from that RFC.\n\nMotivation\n\n When a user is running the Telnet client under the X window system,\n it is useful for the remote Telnet to know the X display location of\n that client. For example, the user might wish to start other X\n applications from the remote host using the same display location as\n the Telnet client. The purpose of this option is to make this\n information availa 1096 nested-reference unchanged"},{"id":"IETF RFC 1080","type":"specification","body":"IETF","designation":"RFC 1080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1080.txt","https://www.rfc-editor.org/rfc/rfc1080.pdf"],"folder":"IETF/RFC-1080","files":{"txt":{"path":"standards/IETF/RFC-1080/RFC-1080.txt","sha256":"05994e81a155f51202c83b3c60bec9765d988a205ae0241e63b76dc13720d201"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Hedrick\nRequest for Comments: 1080 Rutgers University\n November 1988\n\n Telnet Remote Flow Control Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that do remote flow control within the Telnet protocol\n are expected to adopt and implement this standard. Distribution of\n this memo is unlimited.\n\nMotivation\n\n This memo describes a method of remotely toggling flow control\n between a user telnet process and the attached terminal. Only flow\n control of data being transmitted from the telnet process to the\n terminal is considered. Many systems will also allow flow control of\n data from the terminal to the telnet process. However there is\n seldom need to change this behavior repeatedly during the session.\n\n There are two common ways of doing flow control: hardware and\n software. Hardware flow control uses sig","scope_keywords":["1080","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1372","folder":"IETF/RFC-1372","source":"IETF/RFC-1372/RFC-1372.txt","version":null}],"search_text":"IETF RFC 1080 Network Working Group C. Hedrick\nRequest for Comments: 1080 Rutgers University\n November 1988\n\n Telnet Remote Flow Control Option\n\nStatus of This Memo\n\n This RFC specifies a standard for the Internet community. Hosts on\n the Internet that do remote flow control within the Telnet protocol\n are expected to adopt and implement this standard. Distribution of\n this memo is unlimited.\n\nMotivation\n\n This memo describes a method of remotely toggling flow control\n between a user telnet process and the attached terminal. Only flow\n control of data being transmitted from the telnet process to the\n terminal is considered. Many systems will also allow flow control of\n data from the terminal to the telnet process. However there is\n seldom need to change this behavior repeatedly during the session.\n\n There are two common ways of doing flow control: hardware and\n software. Hardware flow control uses sig 1080 path nested-reference unchanged"},{"id":"IETF RFC 1372","type":"specification","body":"IETF","designation":"RFC 1372","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1372.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1372.txt","https://www.rfc-editor.org/rfc/rfc1372.pdf"],"folder":"IETF/RFC-1372","files":{"txt":{"path":"standards/IETF/RFC-1372/RFC-1372.txt","sha256":"99ab228bfd21227ea14e922ead3fac4ae4fa3e271023664ddf72b3a17ae46e3a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Hedrick\nRequest for Comments: 1372 Rutgers University\nObsoletes: RFC 1080 D. Borman\n Cray Research, Inc.\n October 1992\n\n Telnet Remote Flow Control Option\n\nStatus of This Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This document specifies an extended version of the Telnet Remote Flow\n Control Option, RFC 1080, with the addition of the RESTART-ANY and\n RESTART-XON suboptions.\n\n1. Command Names and Codes\n\n TOGGLE-FLOW-CONTROL 33\n OFF 0\n ON 1\n RESTART-ANY 2\n RESTART-XON 3\n\n2. Command Meanings\n\n IAC WILL TOGGLE-FLOW-CONTROL\n\n Sender is willing to enable and disable flow contro","scope_keywords":["1372","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2217","folder":"IETF/RFC-2217","source":"IETF/RFC-2217/RFC-2217.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1372 Network Working Group C. Hedrick\nRequest for Comments: 1372 Rutgers University\nObsoletes: RFC 1080 D. Borman\n Cray Research, Inc.\n October 1992\n\n Telnet Remote Flow Control Option\n\nStatus of This Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This document specifies an extended version of the Telnet Remote Flow\n Control Option, RFC 1080, with the addition of the RESTART-ANY and\n RESTART-XON suboptions.\n\n1. Command Names and Codes\n\n TOGGLE-FLOW-CONTROL 33\n OFF 0\n ON 1\n RESTART-ANY 2\n RESTART-XON 3\n\n2. Command Meanings\n\n IAC WILL TOGGLE-FLOW-CONTROL\n\n Sender is willing to enable and disable flow contro 1372 path nested-reference unchanged"},{"id":"IETF RFC 1084","type":"specification","body":"IETF","designation":"RFC 1084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1084.txt","https://www.rfc-editor.org/rfc/rfc1084.pdf"],"folder":"IETF/RFC-1084","files":{"txt":{"path":"standards/IETF/RFC-1084/RFC-1084.txt","sha256":"b40e8629084f83573fccf21bf25f72c751d8994858cb01e841a6ed16485ca780"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1084 ISI\nObsoletes: 1048 December 1988\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo describes an addition to the Bootstrap Protocol (BOOTP).\n Comments and suggestions for improvements are sought. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 13 for Boot File Size.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such responsibility ","scope_keywords":["1084","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null}],"search_text":"IETF RFC 1084 Network Working Group J. Reynolds\nRequest for Comments: 1084 ISI\nObsoletes: 1048 December 1988\n\n BOOTP Vendor Information Extensions\n\nStatus of this Memo\n\n This memo describes an addition to the Bootstrap Protocol (BOOTP).\n Comments and suggestions for improvements are sought. Distribution\n of this memo is unlimited.\n\nIntroduction\n\n This RFC is a slight revision and extension of RFC-1048 by Philip\n Prindeville, who should be credited with the original work in this\n memo. This memo will be updated as additional tags are are defined.\n This edition introduces Tag 13 for Boot File Size.\n\n As workstations and personal computers proliferate on the Internet,\n the administrative complexity of maintaining a network is increased\n by an order of magnitude. The assignment of local network resources\n to each client represents one such difficulty. In most environments,\n delegating such responsibility  1084 management qualified nested-reference unchanged"},{"id":"IETF RFC 1235","type":"specification","body":"IETF","designation":"RFC 1235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1235.txt","https://www.rfc-editor.org/rfc/rfc1235.pdf"],"folder":"IETF/RFC-1235","files":{"txt":{"path":"standards/IETF/RFC-1235/RFC-1235.txt","sha256":"f7f38fdf1643db7bf0c1ac313bb3b3e440487c6cb2f92dd129420a3def0f933f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Ioannidis\nRequest for Comments: 1235 G. Maguire, Jr.\n Columbia University\n Department of Computer Science\n June 1991\n\n The Coherent File Distribution Protocol\n\nStatus of this Memo\n\n This memo describes the Coherent File Distribution Protocol (CFDP).\n This is an Experimental Protocol for the Internet community.\n Discussion and suggestions for improvement are requested. Please\n refer to the current edition of the \"IAB Official Protocol Standards\"\n for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The Coherent File Distribution Protocol (CFDP) has been designed to\n speed up one-to-many file transfer operations that exhibit traffic\n coherence on media with broadcast capability. Examples of such\n coherent file transfers are identical diskless workstations booting\n simultaneously, software upgrades being","scope_keywords":["1235"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1235 Network Working Group J. Ioannidis\nRequest for Comments: 1235 G. Maguire, Jr.\n Columbia University\n Department of Computer Science\n June 1991\n\n The Coherent File Distribution Protocol\n\nStatus of this Memo\n\n This memo describes the Coherent File Distribution Protocol (CFDP).\n This is an Experimental Protocol for the Internet community.\n Discussion and suggestions for improvement are requested. Please\n refer to the current edition of the \"IAB Official Protocol Standards\"\n for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The Coherent File Distribution Protocol (CFDP) has been designed to\n speed up one-to-many file transfer operations that exhibit traffic\n coherence on media with broadcast capability. Examples of such\n coherent file transfers are identical diskless workstations booting\n simultaneously, software upgrades being 1235 nested-reference unchanged"},{"id":"IETF RFC 1086","type":"specification","body":"IETF","designation":"RFC 1086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1086.txt","https://www.rfc-editor.org/rfc/rfc1086.pdf"],"folder":"IETF/RFC-1086","files":{"txt":{"path":"standards/IETF/RFC-1086/RFC-1086.txt","sha256":"10253dfa3e2bddba397ab161e8e449041cfd6c9b4a8189fb752d6352b8d489d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Onions\nRequest for Comments: 1086 Nottingham\n M. Rose\n TWG\n December 1988\n\n ISO-TP0 bridge between TCP and X.25\n\nStatus of this Memo\n\n This memo proposes a standard for the Internet community. Hosts on\n the Internet that choose to implement ISO TP0 transport connectivity\n between TCP and X.25 based hosts are expected to experiment with this\n proposal. TCP port 146 is reserved for this proposal. Distribution\n of this memo is unlimited and comments are highly encouraged.\n\nIntroduction\n\n This memo specifies a protocol that is used to bridge ISO TP0 packets\n between X.25 and TCP networks. This technique is useful when\n interconnecting a DDN IP internet to an X.25 subnetwork. This is not\n a \"magic bullet\" solution to the DDN/ISO interoperability problem.\n Rather, if one is running higher-layer ISO protocols in both networks\n (namely ISO TP0), then a TP0 bridge can be ","scope_keywords":["1086","authentication","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1086 Network Working Group J. Onions\nRequest for Comments: 1086 Nottingham\n M. Rose\n TWG\n December 1988\n\n ISO-TP0 bridge between TCP and X.25\n\nStatus of this Memo\n\n This memo proposes a standard for the Internet community. Hosts on\n the Internet that choose to implement ISO TP0 transport connectivity\n between TCP and X.25 based hosts are expected to experiment with this\n proposal. TCP port 146 is reserved for this proposal. Distribution\n of this memo is unlimited and comments are highly encouraged.\n\nIntroduction\n\n This memo specifies a protocol that is used to bridge ISO TP0 packets\n between X.25 and TCP networks. This technique is useful when\n interconnecting a DDN IP internet to an X.25 subnetwork. This is not\n a \"magic bullet\" solution to the DDN/ISO interoperability problem.\n Rather, if one is running higher-layer ISO protocols in both networks\n (namely ISO TP0), then a TP0 bridge can be  1086 authentication authorization nested-reference unchanged"},{"id":"IETF RFC 1087","type":"specification","body":"IETF","designation":"RFC 1087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1087.txt","https://www.rfc-editor.org/rfc/rfc1087.pdf"],"folder":"IETF/RFC-1087","files":{"txt":{"path":"standards/IETF/RFC-1087/RFC-1087.txt","sha256":"04bb172324f29e9a3b9c72c32979ea41982f869888110cde6fdf5302ef800535"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1087 January 1989\n\n Ethics and the Internet\n\nStatus of this Memo\n\n This memo is a statement of policy by the Internet Activities Board\n (IAB) concerning the proper use of the resources of the Internet.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n At great human and economic cost, resources drawn from the U.S.\n Government, industry and the academic community have been assembled\n into a collection of interconnected networks called the Internet.\n Begun as a vehicle for experimental network research in the mid-\n 1970's, the Internet has become an important national infrastructure\n supporting an increasingly widespread, multi-disciplinary community\n of researchers ranging, inter alia, from computer scientists and\n electrical engineers to mathematicians, physicists, medical\n researchers, chemists, astronomers and","scope_keywords":["1087","delivery","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1135","folder":"IETF/RFC-1135","source":"IETF/RFC-1135/RFC-1135.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1359","folder":"IETF/RFC-1359","source":"IETF/RFC-1359/RFC-1359.txt","version":null},{"body":"IETF","designation":"RFC 1855","folder":"IETF/RFC-1855","source":"IETF/RFC-1855/RFC-1855.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null}],"search_text":"IETF RFC 1087 Network Working Group Internet Activities Board\nRequest for Comments: 1087 January 1989\n\n Ethics and the Internet\n\nStatus of this Memo\n\n This memo is a statement of policy by the Internet Activities Board\n (IAB) concerning the proper use of the resources of the Internet.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n At great human and economic cost, resources drawn from the U.S.\n Government, industry and the academic community have been assembled\n into a collection of interconnected networks called the Internet.\n Begun as a vehicle for experimental network research in the mid-\n 1970's, the Internet has become an important national infrastructure\n supporting an increasingly widespread, multi-disciplinary community\n of researchers ranging, inter alia, from computer scientists and\n electrical engineers to mathematicians, physicists, medical\n researchers, chemists, astronomers and 1087 delivery policy nested-reference unchanged"},{"id":"IETF RFC 1135","type":"specification","body":"IETF","designation":"RFC 1135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1135.txt","https://www.rfc-editor.org/rfc/rfc1135.pdf"],"folder":"IETF/RFC-1135","files":{"txt":{"path":"standards/IETF/RFC-1135/RFC-1135.txt","sha256":"f30f57d102d82772070eaa099d50c6c0f209822152b6dcb0b62b6e981e6a9490"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 1135 ISI\n December 1989\n\n The Helminthiasis of the Internet\n\nStatus of this Memo\n\n This memo takes a look back at the helminthiasis (infestation with,\n or disease caused by parasitic worms) of the Internet that was\n unleashed the evening of 2 November 1988. This RFC provides\n information about an event that occurred in the life of the Internet.\n This memo does not specify any standard. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n ----- \"The obscure we see eventually, the completely\n apparent takes longer.\" ----- Edward R. Murrow\n\n The helminthiasis of the Internet was a self-replicating program that\n infected VAX computers and SUN-3 workstations running the 4.2 and 4.3\n Berkeley UNIX code. It disrupted the operations of computers by\n accessing known security loopholes in applications closely associated\n with the operatin","scope_keywords":["1135","attribute","delivery","identification","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1135 Network Working Group J. Reynolds\nRequest for Comments: 1135 ISI\n December 1989\n\n The Helminthiasis of the Internet\n\nStatus of this Memo\n\n This memo takes a look back at the helminthiasis (infestation with,\n or disease caused by parasitic worms) of the Internet that was\n unleashed the evening of 2 November 1988. This RFC provides\n information about an event that occurred in the life of the Internet.\n This memo does not specify any standard. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n ----- \"The obscure we see eventually, the completely\n apparent takes longer.\" ----- Edward R. Murrow\n\n The helminthiasis of the Internet was a self-replicating program that\n infected VAX computers and SUN-3 workstations running the 4.2 and 4.3\n Berkeley UNIX code. It disrupted the operations of computers by\n accessing known security loopholes in applications closely associated\n with the operatin 1135 attribute delivery identification key trust nested-reference unchanged"},{"id":"IETF RFC 1244","type":"specification","body":"IETF","designation":"RFC 1244","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1244.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1244.txt","https://www.rfc-editor.org/rfc/rfc1244.pdf"],"folder":"IETF/RFC-1244","files":{"txt":{"path":"standards/IETF/RFC-1244/RFC-1244.txt","sha256":"6e39442e679f0ad24c62d14bf04440c4c84b44a9e9837f03bf71cf161ed4c17e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Holbrook\nRequest for Comments: 1244 CICNet\nFYI: 8 J. Reynolds\n ISI\n Editors\n July 1991\n\n Site Security Handbook\n\nStatus of this Memo\n\n This handbook is the product of the Site Security Policy Handbook\n Working Group (SSPHWG), a combined effort of the Security Area and\n User Services Area of the Internet Engineering Task Force (IETF).\n This FYI RFC provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nContributing Authors\n\n The following are the authors of the Site Security Handbook. Without\n their dedication, this handbook would not have been possible.\n\n Dave Curry (Purdue University), Sean Kirkpatrick (Unisys), Tom\n Longstaff (LLNL), Greg Hollingsworth (Johns Hopkins University),\n Jeffrey Carpenter (University of Pittsburgh), Barbara Fraser (CERT),\n Fred Ostapik (SRI NISC), Allen Stu","scope_keywords":["1244","audit","management","pki","policies","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1281","folder":"IETF/RFC-1281","source":"IETF/RFC-1281/RFC-1281.txt","version":null},{"body":"IETF","designation":"RFC 1359","folder":"IETF/RFC-1359","source":"IETF/RFC-1359/RFC-1359.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null}],"search_text":"IETF RFC 1244 Network Working Group P. Holbrook\nRequest for Comments: 1244 CICNet\nFYI: 8 J. Reynolds\n ISI\n Editors\n July 1991\n\n Site Security Handbook\n\nStatus of this Memo\n\n This handbook is the product of the Site Security Policy Handbook\n Working Group (SSPHWG), a combined effort of the Security Area and\n User Services Area of the Internet Engineering Task Force (IETF).\n This FYI RFC provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nContributing Authors\n\n The following are the authors of the Site Security Handbook. Without\n their dedication, this handbook would not have been possible.\n\n Dave Curry (Purdue University), Sean Kirkpatrick (Unisys), Tom\n Longstaff (LLNL), Greg Hollingsworth (Johns Hopkins University),\n Jeffrey Carpenter (University of Pittsburgh), Barbara Fraser (CERT),\n Fred Ostapik (SRI NISC), Allen Stu 1244 audit management pki policies policy risk nested-reference unchanged"},{"id":"IETF RFC 1359","type":"specification","body":"IETF","designation":"RFC 1359","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1359.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1359.txt","https://www.rfc-editor.org/rfc/rfc1359.pdf"],"folder":"IETF/RFC-1359","files":{"txt":{"path":"standards/IETF/RFC-1359/RFC-1359.txt","sha256":"1e4e896832835020e668b005a6c67d86389fd406b3d305137bfbd6770dffcee9"}},"tags":["nested-reference","unchanged"],"summary":"This FYI RFC outlines the major issues an institution should consider\n in the decision and implementation of a campus connection to the\n Internet.\n\n In order to provide clarity to the reader, some specific information\n has been detailed. In doing so, the document has been directed\n toward U.S. academic institutions that have not yet connected to the\n Internet.\n\n However, the issues for which specific information has been provided\n can be generalized for any organization that wishes to participate in\n the world-wide Internet community. It will be necessary for those\n organizations to obtain the correct and detailed information from\n their local or national IP service providers. In addition, this\n document may be used as an evaluation checklist for organizations\n that are currently connected. Readers are expected to have general\n familiarity with networking concepts and terminology.","scope_keywords":["1359","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null}],"search_text":"IETF RFC 1359 This FYI RFC outlines the major issues an institution should consider\n in the decision and implementation of a campus connection to the\n Internet.\n\n In order to provide clarity to the reader, some specific information\n has been detailed. In doing so, the document has been directed\n toward U.S. academic institutions that have not yet connected to the\n Internet.\n\n However, the issues for which specific information has been provided\n can be generalized for any organization that wishes to participate in\n the world-wide Internet community. It will be necessary for those\n organizations to obtain the correct and detailed information from\n their local or national IP service providers. In addition, this\n document may be used as an evaluation checklist for organizations\n that are currently connected. Readers are expected to have general\n familiarity with networking concepts and terminology. 1359 policy nested-reference unchanged"},{"id":"IETF RFC 1855","type":"specification","body":"IETF","designation":"RFC 1855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1855.txt","https://www.rfc-editor.org/rfc/rfc1855.pdf"],"folder":"IETF/RFC-1855","files":{"txt":{"path":"standards/IETF/RFC-1855/RFC-1855.txt","sha256":"5c4db45d560afaff538513390b5bcae9d4e903dac2b6b7a89660bf7ab6d8ce43"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a minimum set of guidelines for Network\n Etiquette (Netiquette) which organizations may take and adapt for\n their own use. As such, it is deliberately written in a bulleted\n format to make adaptation easier and to make any particular item easy\n (or easier) to find. It also functions as a minimum set of\n guidelines for individuals, both users and administrators. This memo\n is the product of the Responsible Use of the Network (RUN) Working\n Group of the IETF.","scope_keywords":["1855","encryption","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null}],"search_text":"IETF RFC 1855 This document provides a minimum set of guidelines for Network\n Etiquette (Netiquette) which organizations may take and adapt for\n their own use. As such, it is deliberately written in a bulleted\n format to make adaptation easier and to make any particular item easy\n (or easier) to find. It also functions as a minimum set of\n guidelines for individuals, both users and administrators. This memo\n is the product of the Responsible Use of the Network (RUN) Working\n Group of the IETF. 1855 encryption signature subject nested-reference unchanged"},{"id":"IETF RFC 2196","type":"specification","body":"IETF","designation":"RFC 2196","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2196.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2196.txt","https://www.rfc-editor.org/rfc/rfc2196.pdf"],"folder":"IETF/RFC-2196","files":{"txt":{"path":"standards/IETF/RFC-2196/RFC-2196.txt","sha256":"ec4b7ac643ce4865a92c849843c95c281cd77e8805be197c7f19b1431479bdc3"}},"tags":["nested-reference","unchanged"],"summary":"This handbook is a guide to developing computer security policies and\n procedures for sites that have systems on the Internet. The purpose\n of this handbook is to provide practical guidance to administrators\n trying to secure their information and services. The subjects\n covered include policy content and formation, a broad range of\n technical system and network security topics, and security incident\n response.","scope_keywords":["2196","audit","authentication","authorization","management","path","policies","policy","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2350","folder":"IETF/RFC-2350","source":"IETF/RFC-2350/RFC-2350.txt","version":null},{"body":"IETF","designation":"RFC 2504","folder":"IETF/RFC-2504","source":"IETF/RFC-2504/RFC-2504.txt","version":null},{"body":"IETF","designation":"RFC 2635","folder":"IETF/RFC-2635","source":"IETF/RFC-2635/RFC-2635.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null}],"search_text":"IETF RFC 2196 This handbook is a guide to developing computer security policies and\n procedures for sites that have systems on the Internet. The purpose\n of this handbook is to provide practical guidance to administrators\n trying to secure their information and services. The subjects\n covered include policy content and formation, a broad range of\n technical system and network security topics, and security incident\n response. 2196 audit authentication authorization management path policies policy risk subject nested-reference unchanged"},{"id":"IETF RFC 1419","type":"specification","body":"IETF","designation":"RFC 1419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1419.txt","https://www.rfc-editor.org/rfc/rfc1419.pdf"],"folder":"IETF/RFC-1419","files":{"txt":{"path":"standards/IETF/RFC-1419/RFC-1419.txt","sha256":"acc83fc69f3b9981170c44bb2b9aa271e857c5bcd8433c34b7bfd75f0be60d56"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Minshall\nRequest for Comments: 1419 Novell, Inc.\n M. Ritter\n Apple Computer, Inc.\n March 1993\n\n SNMP over AppleTalk\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo describes the method by which the Simple Network Management\n Protocol (SNMP) as specified in [1] can be used over AppleTalk\n protocols [2] instead of the Internet UDP/IP protocol stack. This\n specification is useful for network elements which have AppleTalk\n support but lack TCP/IP support. It should be noted that if a\n network element supports multiple protocol stacks, and UDP is\n availabl","scope_keywords":["1419","attribute","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1419 Network Working Group G. Minshall\nRequest for Comments: 1419 Novell, Inc.\n M. Ritter\n Apple Computer, Inc.\n March 1993\n\n SNMP over AppleTalk\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo describes the method by which the Simple Network Management\n Protocol (SNMP) as specified in [1] can be used over AppleTalk\n protocols [2] instead of the Internet UDP/IP protocol stack. This\n specification is useful for network elements which have AppleTalk\n support but lack TCP/IP support. It should be noted that if a\n network element supports multiple protocol stacks, and UDP is\n availabl 1419 attribute delivery management nested-reference unchanged"},{"id":"IETF RFC 109","type":"specification","body":"IETF","designation":"RFC 109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc109.txt","https://www.rfc-editor.org/rfc/rfc109.pdf"],"folder":"IETF/RFC-109","files":{"pdf":{"path":"standards/IETF/RFC-109/RFC-109.pdf","sha256":"57c96cf7788cb5e18eca5fc26efc34cf566a7c5a5848a9ac793c4618eea8a82f"},"txt":{"path":"standards/IETF/RFC-109/RFC-109.txt","sha256":"eb942d35e46bdc5586ebd95912ac5d594da4263205d47b7fe4073dd7b8610a3f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Winett\nRequest for Comments: 109 MIT Lincoln Laboratory\nNIC: 5805 24 March 1971\n\n Level III Server Protocol for the Lincoln Laboratory\n 360/67 Host\n\nDisclaimer\n\n This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.\n\nIntroduction\n\n The Lincoln Laboratory IBM 360/67 is connected to the ARPA network\n and acts as a serving host providing access to the CP-67 virtual\n machine operating system. Upon completion of the Login procedure,\n users have control of a 360 virtual machine through a virtual 1052\n online console. Attached to the virtual machine is a virtual card\n reader, card punch and line printer, and a number of disk storage\n devices. The 360 virtual machine can be either a virtual 360/67 with\n dynamic address translation ha","scope_keywords":["109","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0137","folder":"IETF/RFC-0137","source":"IETF/RFC-0137/RFC-0137.txt","version":null},{"body":"IETF","designation":"RFC 137","folder":"IETF/RFC-137","source":"IETF/RFC-137/RFC-137.txt","version":null},{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null}],"search_text":"IETF RFC 109 Network Working Group J. Winett\nRequest for Comments: 109 MIT Lincoln Laboratory\nNIC: 5805 24 March 1971\n\n Level III Server Protocol for the Lincoln Laboratory\n 360/67 Host\n\nDisclaimer\n\n This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.\n\nIntroduction\n\n The Lincoln Laboratory IBM 360/67 is connected to the ARPA network\n and acts as a serving host providing access to the CP-67 virtual\n machine operating system. Upon completion of the Login procedure,\n users have control of a 360 virtual machine through a virtual 1052\n online console. Attached to the virtual machine is a virtual card\n reader, card punch and line printer, and a number of disk storage\n devices. The 360 virtual machine can be either a virtual 360/67 with\n dynamic address translation ha 109 key nested-reference unchanged"},{"id":"IETF RFC 1090","type":"specification","body":"IETF","designation":"RFC 1090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1090.txt","https://www.rfc-editor.org/rfc/rfc1090.pdf"],"folder":"IETF/RFC-1090","files":{"txt":{"path":"standards/IETF/RFC-1090/RFC-1090.txt","sha256":"5700c26feccde157068261c5a2b7502e80434421261897cdab4dbc1f8e49eb8c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Ullmann\nRequest for Comments: 1090 Prime Computer, Inc.\n February 1989\n\n SMTP on X.25\n\n1. Status of this Memo\n\n This memo proposes a standard for SMTP on the virtual circuit\n facility provided by the X.25 standard of the CCITT.\n\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n The possibility of using the X.25 virtual circuit (ISO level 3)\n directly for SMTP is mentioned in RFC 821 (\"SIMPLE MAIL TRANSPORT\n PROTOCOL\"), in appendix D. It suggests that \"a reliable end-to-end\n protocol such as TCP be used on top of X.25 connections\". This was\n undoubtedly true considering the general reliability of the PSDNs at\n the time (1981). The service is now (in 1989) reliable enough to\n allow practical direct use of the virtual circuit service.\n\n The procedures given here have proven to be successful in extensive\n production use, involving 24 PSDNs in 22 different c","scope_keywords":["1090","crl","delivery","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null}],"search_text":"IETF RFC 1090 Network Working Group R. Ullmann\nRequest for Comments: 1090 Prime Computer, Inc.\n February 1989\n\n SMTP on X.25\n\n1. Status of this Memo\n\n This memo proposes a standard for SMTP on the virtual circuit\n facility provided by the X.25 standard of the CCITT.\n\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n The possibility of using the X.25 virtual circuit (ISO level 3)\n directly for SMTP is mentioned in RFC 821 (\"SIMPLE MAIL TRANSPORT\n PROTOCOL\"), in appendix D. It suggests that \"a reliable end-to-end\n protocol such as TCP be used on top of X.25 connections\". This was\n undoubtedly true considering the general reliability of the PSDNs at\n the time (1981). The service is now (in 1989) reliable enough to\n allow practical direct use of the virtual circuit service.\n\n The procedures given here have proven to be successful in extensive\n production use, involving 24 PSDNs in 22 different c 1090 crl delivery qualified nested-reference unchanged"},{"id":"IETF RFC 1408","type":"specification","body":"IETF","designation":"RFC 1408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1408.txt","https://www.rfc-editor.org/rfc/rfc1408.pdf"],"folder":"IETF/RFC-1408","files":{"txt":{"path":"standards/IETF/RFC-1408/RFC-1408.txt","sha256":"374b0334dd58529760f52f773c7ca3d10177a2d93f5806261f510e919f75b6e5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman, Editor\nRequest for Comments: 1408 Cray Research, Inc.\n January 1993\n\n Telnet Environment Option\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing environment\n information between a telnet client and server. Use of this\n mechanism enables a telnet user to propagate configuration\n information to a remote host when connecting.\n\n1. Command Names and Codes\n\n ENVIRON 36\n IS 0\n SEND 1\n INFO 2\n\n VAR 0\n VALUE 1\n ESC 2\n USERVAR 3\n\n2. Command Meanings\n\n IAC WILL ENVIRON\n\n The sender of this command is willing to send envir","scope_keywords":["1408","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1571","folder":"IETF/RFC-1571","source":"IETF/RFC-1571/RFC-1571.txt","version":null},{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1408 Network Working Group D. Borman, Editor\nRequest for Comments: 1408 Cray Research, Inc.\n January 1993\n\n Telnet Environment Option\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing environment\n information between a telnet client and server. Use of this\n mechanism enables a telnet user to propagate configuration\n information to a remote host when connecting.\n\n1. Command Names and Codes\n\n ENVIRON 36\n IS 0\n SEND 1\n INFO 2\n\n VAR 0\n VALUE 1\n ESC 2\n USERVAR 3\n\n2. Command Meanings\n\n IAC WILL ENVIRON\n\n The sender of this command is willing to send envir 1408 trust nested-reference unchanged"},{"id":"IETF RFC 1572","type":"specification","body":"IETF","designation":"RFC 1572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1572.txt","https://www.rfc-editor.org/rfc/rfc1572.pdf"],"folder":"IETF/RFC-1572","files":{"txt":{"path":"standards/IETF/RFC-1572/RFC-1572.txt","sha256":"75595aba61a5d7202214ea9c9bb772c449e0e07a3dc1b27a9b8f35adb42ddabc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Alexander, Editor\nRequest for Comments: 1572 Lachman Technology, Inc.\nCategory: Standards Track January 1994\n\n Telnet Environment Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing environment\n information between a telnet client and server. Use of this\n mechanism enables a telnet user to propagate configuration\n information to a remote host when connecting.\n\n This document corrects some errors in [1].\n\n1. Command Names and Codes\n\n NEW-ENVIRON 39\n IS 0\n SEND 1\n INFO 2\n\n VAR 0\n VALUE 1\n ESC 2","scope_keywords":["1572"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1572 Network Working Group S. Alexander, Editor\nRequest for Comments: 1572 Lachman Technology, Inc.\nCategory: Standards Track January 1994\n\n Telnet Environment Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing environment\n information between a telnet client and server. Use of this\n mechanism enables a telnet user to propagate configuration\n information to a remote host when connecting.\n\n This document corrects some errors in [1].\n\n1. Command Names and Codes\n\n NEW-ENVIRON 39\n IS 0\n SEND 1\n INFO 2\n\n VAR 0\n VALUE 1\n ESC 2 1572 nested-reference unchanged"},{"id":"IETF RFC 1646","type":"specification","body":"IETF","designation":"RFC 1646","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1646.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1646.txt","https://www.rfc-editor.org/rfc/rfc1646.pdf"],"folder":"IETF/RFC-1646","files":{"txt":{"path":"standards/IETF/RFC-1646/RFC-1646.txt","sha256":"493bb79cadbc14eda662955e84c69691d01236b5c69af155a7774d0539be9fc5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol extensions to TN3270. There are two\n extensions outlined in this document. The first defines a way by\n which a TN3270 client can request a specific device (LUname) from a\n TN3270 server. The second extension specifies how a TN3270 printer\n device can be requested by a TN3270 client and the manner in which\n the 3270 printer status information can be sent to the TN3270 server.\n Discussions and suggestions for improvements to these enhancements\n should be sent to the TN3270E Working Group mailing list\n TN3270E@list.nih.gov . These extensions will be called TN3287 in this\n document. This information is being provided to members of the\n Internet community that want to support the 3287 data stream within\n the TELNET protocol.\n\n1. INTRODUCTION\n\n The need to communicate with IBM mainframe systems has a number of\n unique requirements associated with it. This docum","scope_keywords":["1646","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null}],"search_text":"IETF RFC 1646 This document describes protocol extensions to TN3270. There are two\n extensions outlined in this document. The first defines a way by\n which a TN3270 client can request a specific device (LUname) from a\n TN3270 server. The second extension specifies how a TN3270 printer\n device can be requested by a TN3270 client and the manner in which\n the 3270 printer status information can be sent to the TN3270 server.\n Discussions and suggestions for improvements to these enhancements\n should be sent to the TN3270E Working Group mailing list\n TN3270E@list.nih.gov . These extensions will be called TN3287 in this\n document. This information is being provided to members of the\n Internet community that want to support the 3287 data stream within\n the TELNET protocol.\n\n1. INTRODUCTION\n\n The need to communicate with IBM mainframe systems has a number of\n unique requirements associated with it. This docum 1646 management nested-reference unchanged"},{"id":"IETF RFC 1092","type":"specification","body":"IETF","designation":"RFC 1092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1092.txt","https://www.rfc-editor.org/rfc/rfc1092.pdf"],"folder":"IETF/RFC-1092","files":{"txt":{"path":"standards/IETF/RFC-1092/RFC-1092.txt","sha256":"b1e2ae4a259aa31fefec512f5945441bd159d767675bf834b143e84e66f73a94"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Rekhter\nRequest for Comments: 1092 T. J. Watson Research Center\n February 1989\n\n EGP and Policy Based Routing in the New NSFNET Backbone\n\nStatus of this Memo\n\n This memo discusses implementation decisions for routing issues in\n the NSFNET, especially in the NSFNET Backbone. Of special concern is\n the restriction of routing information to advertize the best route as\n established by a policy decision. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n The NSFNET backbone routes packets between the Regionals Networks to\n which it is connected, (i.e., the packets arriving at a backbone\n entry node are routed to an exit node). How they travel through the\n network is determined by two components:\n\n the NSFNET backbone routing protocol/algorithm, and\n\n additional information about the externally connected networks.\n\n This paper is concerned with how reachability i","scope_keywords":["1092","algorithm","management","path","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1093","folder":"IETF/RFC-1093","source":"IETF/RFC-1093/RFC-1093.txt","version":null},{"body":"IETF","designation":"RFC 1104","folder":"IETF/RFC-1104","source":"IETF/RFC-1104/RFC-1104.txt","version":null},{"body":"IETF","designation":"RFC 1105","folder":"IETF/RFC-1105","source":"IETF/RFC-1105/RFC-1105.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null}],"search_text":"IETF RFC 1092 Network Working Group J. Rekhter\nRequest for Comments: 1092 T. J. Watson Research Center\n February 1989\n\n EGP and Policy Based Routing in the New NSFNET Backbone\n\nStatus of this Memo\n\n This memo discusses implementation decisions for routing issues in\n the NSFNET, especially in the NSFNET Backbone. Of special concern is\n the restriction of routing information to advertize the best route as\n established by a policy decision. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n The NSFNET backbone routes packets between the Regionals Networks to\n which it is connected, (i.e., the packets arriving at a backbone\n entry node are routed to an exit node). How they travel through the\n network is determined by two components:\n\n the NSFNET backbone routing protocol/algorithm, and\n\n additional information about the externally connected networks.\n\n This paper is concerned with how reachability i 1092 algorithm management path policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 1093","type":"specification","body":"IETF","designation":"RFC 1093","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1093.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1093.txt","https://www.rfc-editor.org/rfc/rfc1093.pdf"],"folder":"IETF/RFC-1093","files":{"txt":{"path":"standards/IETF/RFC-1093/RFC-1093.txt","sha256":"2973687f41917aea8608dfd94ec950ad666e0dee6a63c138957f632f916205f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H.W. Braun\nRequest for Comments: 1093 Merit\n February 1989\n\n The NSFNET Routing Architecture\n\nStatus of this Memo\n\n This document describes the routing architecture for the NSFNET\n centered around the new NSFNET Backbone, with specific emphasis on\n the interface between the backbone and its attached networks.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This document describes the routing architecture for the NSFNET\n centered around the new NSFNET Backbone, with specific emphasis on\n the interface between the backbone and its attached networks. It\n reflects and augments thoughts described in [1], discussions during\n the Internet Engineering Task Force meeting at the San Diego\n Supercomputing Center in March 1988, discussions on mailing lists,\n especially on a backbone/regional network working group mailing list,\n and a final discussion held at the IBM T.","scope_keywords":["1093","algorithm","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1104","folder":"IETF/RFC-1104","source":"IETF/RFC-1104/RFC-1104.txt","version":null},{"body":"IETF","designation":"RFC 1105","folder":"IETF/RFC-1105","source":"IETF/RFC-1105/RFC-1105.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null}],"search_text":"IETF RFC 1093 Network Working Group H.W. Braun\nRequest for Comments: 1093 Merit\n February 1989\n\n The NSFNET Routing Architecture\n\nStatus of this Memo\n\n This document describes the routing architecture for the NSFNET\n centered around the new NSFNET Backbone, with specific emphasis on\n the interface between the backbone and its attached networks.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This document describes the routing architecture for the NSFNET\n centered around the new NSFNET Backbone, with specific emphasis on\n the interface between the backbone and its attached networks. It\n reflects and augments thoughts described in [1], discussions during\n the Internet Engineering Task Force meeting at the San Diego\n Supercomputing Center in March 1988, discussions on mailing lists,\n especially on a backbone/regional network working group mailing list,\n and a final discussion held at the IBM T. 1093 algorithm path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1104","type":"specification","body":"IETF","designation":"RFC 1104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1104.txt","https://www.rfc-editor.org/rfc/rfc1104.pdf"],"folder":"IETF/RFC-1104","files":{"txt":{"path":"standards/IETF/RFC-1104/RFC-1104.txt","sha256":"8e78cc43b6bde8303b86339bd12a19a491cce4c8504503137edef7eeede8278c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H-W. Braun\nRequest for Comments: 1104 Merit/NSFNET\n June 1989\n\n Models of Policy Based Routing\n\n1. Status of this Memo\n\n The purpose of this RFC is to outline a variety of models for policy\n based routing. The relative benefits of the different approaches are\n reviewed. Discussions and comments are explicitly encouraged to move\n toward the best policy based routing model that scales well within a\n large internetworking environment.\n\n Distribution of this memo is unlimited.\n\n2. Acknowledgements\n\n Specific thanks go to Yakov Rekhter (IBM Research), Milo Medin\n (NASA), Susan Hares (Merit/NSFNET), Jessica Yu (Merit/NSFNET) and\n Dave Katz (Merit/NSFNET) for extensively contributing to and\n reviewing this document.\n\n3. Overview\n\n To evaluate the methods and models for policy based routing, it is\n necessary to investigate the context into which the model is to be\n used, as","scope_keywords":["1104","authentication","identification","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null},{"body":"IETF","designation":"RFC 1164","folder":"IETF/RFC-1164","source":"IETF/RFC-1164/RFC-1164.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1268","folder":"IETF/RFC-1268","source":"IETF/RFC-1268/RFC-1268.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1655","folder":"IETF/RFC-1655","source":"IETF/RFC-1655/RFC-1655.txt","version":null},{"body":"IETF","designation":"RFC 1772","folder":"IETF/RFC-1772","source":"IETF/RFC-1772/RFC-1772.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 1104 Network Working Group H-W. Braun\nRequest for Comments: 1104 Merit/NSFNET\n June 1989\n\n Models of Policy Based Routing\n\n1. Status of this Memo\n\n The purpose of this RFC is to outline a variety of models for policy\n based routing. The relative benefits of the different approaches are\n reviewed. Discussions and comments are explicitly encouraged to move\n toward the best policy based routing model that scales well within a\n large internetworking environment.\n\n Distribution of this memo is unlimited.\n\n2. Acknowledgements\n\n Specific thanks go to Yakov Rekhter (IBM Research), Milo Medin\n (NASA), Susan Hares (Merit/NSFNET), Jessica Yu (Merit/NSFNET) and\n Dave Katz (Merit/NSFNET) for extensively contributing to and\n reviewing this document.\n\n3. Overview\n\n To evaluate the methods and models for policy based routing, it is\n necessary to investigate the context into which the model is to be\n used, as 1104 authentication identification path policies policy nested-reference unchanged"},{"id":"IETF RFC 1163","type":"specification","body":"IETF","designation":"RFC 1163","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1163.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1163.txt","https://www.rfc-editor.org/rfc/rfc1163.pdf"],"folder":"IETF/RFC-1163","files":{"txt":{"path":"standards/IETF/RFC-1163/RFC-1163.txt","sha256":"7f47778030ac3e4826dce704a7b609f604962ee11e3eca9c77aec085997757e8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Lougheed\nRequest for Comments: 1163 cisco Systems\nObsoletes: RFC 1105 Y. Rekhter\n T.J. Watson Research Center, IBM Corp\n June 1990\n\n A Border Gateway Protocol (BGP)\n\nStatus of this Memo\n\n This RFC, together with its companion RFC-1164, \"Application of the\n Border Gateway Protocol in the Internet\", define a Proposed Standard\n for an inter-autonomous system routing protocol for the Internet.\n\n This protocol, like any other at this initial stage, may undergo\n modifications before reaching full Internet Standard status as a\n result of deployment experience. Implementers are encouraged to\n track the progress of this or any protocol as it moves through the\n standardization process, and to report their own experience with the\n protocol.\n\n This protocol is being considered by the Interconnectivity Working\n Group (IWG) of the Internet Engineering Task Force (IETF).\n Infor","scope_keywords":["1163","attribute","attributes","authentication","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1164","folder":"IETF/RFC-1164","source":"IETF/RFC-1164/RFC-1164.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1265","folder":"IETF/RFC-1265","source":"IETF/RFC-1265/RFC-1265.txt","version":null},{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1397","folder":"IETF/RFC-1397","source":"IETF/RFC-1397/RFC-1397.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null}],"search_text":"IETF RFC 1163 Network Working Group K. Lougheed\nRequest for Comments: 1163 cisco Systems\nObsoletes: RFC 1105 Y. Rekhter\n T.J. Watson Research Center, IBM Corp\n June 1990\n\n A Border Gateway Protocol (BGP)\n\nStatus of this Memo\n\n This RFC, together with its companion RFC-1164, \"Application of the\n Border Gateway Protocol in the Internet\", define a Proposed Standard\n for an inter-autonomous system routing protocol for the Internet.\n\n This protocol, like any other at this initial stage, may undergo\n modifications before reaching full Internet Standard status as a\n result of deployment experience. Implementers are encouraged to\n track the progress of this or any protocol as it moves through the\n standardization process, and to report their own experience with the\n protocol.\n\n This protocol is being considered by the Interconnectivity Working\n Group (IWG) of the Internet Engineering Task Force (IETF).\n Infor 1163 attribute attributes authentication path policies policy nested-reference unchanged"},{"id":"IETF RFC 1267","type":"specification","body":"IETF","designation":"RFC 1267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1267.txt","https://www.rfc-editor.org/rfc/rfc1267.pdf"],"folder":"IETF/RFC-1267","files":{"txt":{"path":"standards/IETF/RFC-1267/RFC-1267.txt","sha256":"a03c352f646ac46c61ee385c2279357bc6238ec0985737e709dfac53c0715e0c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Lougheed\nRequest for Comments: 1267 cisco Systems\nObsoletes RFCs: 1105, 1163 Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n October 1991\n\n A Border Gateway Protocol 3 (BGP-3)\n\nStatus of this Memo\n\n This memo, together with its companion document, \"Application of the\n Border Gateway Protocol in the Internet\", define an inter-autonomous\n system routing protocol for the Internet. This RFC specifies an IAB\n standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Acknowledgements\n\n We would like to express our thanks to Guy Almes (Rice University),\n Len Bosack (cisco Systems), Jeffrey C. Honig (Cornell Theory Center)\n and all me","scope_keywords":["1267","authentication","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1265","folder":"IETF/RFC-1265","source":"IETF/RFC-1265/RFC-1265.txt","version":null},{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1268","folder":"IETF/RFC-1268","source":"IETF/RFC-1268/RFC-1268.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1338","folder":"IETF/RFC-1338","source":"IETF/RFC-1338/RFC-1338.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1397","folder":"IETF/RFC-1397","source":"IETF/RFC-1397/RFC-1397.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1786","folder":"IETF/RFC-1786","source":"IETF/RFC-1786/RFC-1786.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null}],"search_text":"IETF RFC 1267 Network Working Group K. Lougheed\nRequest for Comments: 1267 cisco Systems\nObsoletes RFCs: 1105, 1163 Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n October 1991\n\n A Border Gateway Protocol 3 (BGP-3)\n\nStatus of this Memo\n\n This memo, together with its companion document, \"Application of the\n Border Gateway Protocol in the Internet\", define an inter-autonomous\n system routing protocol for the Internet. This RFC specifies an IAB\n standards track protocol for the Internet community, and requests\n discussion and suggestions for improvements. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Acknowledgements\n\n We would like to express our thanks to Guy Almes (Rice University),\n Len Bosack (cisco Systems), Jeffrey C. Honig (Cornell Theory Center)\n and all me 1267 authentication path policies policy nested-reference unchanged"},{"id":"IETF RFC 1478","type":"specification","body":"IETF","designation":"RFC 1478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1478.txt","https://www.rfc-editor.org/rfc/rfc1478.pdf"],"folder":"IETF/RFC-1478","files":{"txt":{"path":"standards/IETF/RFC-1478/RFC-1478.txt","sha256":"cd34f9473599819a6ba7cbfae5288f76ce1732a7f4ca42111dca470e6b3b1a09"}},"tags":["nested-reference","unchanged"],"summary":"We present an architecture for inter-domain policy routing (IDPR).\n The objective of IDPR is to construct and maintain routes, between\n source and destination administrative domains, that provide user\n traffic with the requested services within the constraints stipulated\n for the domains transited. The IDPR architecture is designed to\n accommodate an internetwork containing tens of thousands of\n administrative domains with heterogeneous service requirements and\n restrictions.\n\nContributors\n\n The following people have contributed to the IDPR architecture: Bob\n Braden, Lee Breslau, Ross Callon, Noel Chiappa, Dave Clark, Pat\n Clark, Deborah Estrin, Marianne Lepp, Mike Little, Martha Steenstrup,\n Zaw-Sing Su, Paul Tsuchiya, and Gene Tsudik. Yakov Rekhter supplied\n many useful comments on a previous draft of this document.\n\nSteenstrup [Page 1]\n\f\nRFC 1478 IDPR Architecture June 1993","scope_keywords":["1478","authentication","path","policies","policy","registered","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1478 We present an architecture for inter-domain policy routing (IDPR).\n The objective of IDPR is to construct and maintain routes, between\n source and destination administrative domains, that provide user\n traffic with the requested services within the constraints stipulated\n for the domains transited. The IDPR architecture is designed to\n accommodate an internetwork containing tens of thousands of\n administrative domains with heterogeneous service requirements and\n restrictions.\n\nContributors\n\n The following people have contributed to the IDPR architecture: Bob\n Braden, Lee Breslau, Ross Callon, Noel Chiappa, Dave Clark, Pat\n Clark, Deborah Estrin, Marianne Lepp, Mike Little, Martha Steenstrup,\n Zaw-Sing Su, Paul Tsuchiya, and Gene Tsudik. Yakov Rekhter supplied\n many useful comments on a previous draft of this document.\n\nSteenstrup [Page 1]\n\f\nRFC 1478 IDPR Architecture June 1993 1478 authentication path policies policy registered timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 1654","type":"specification","body":"IETF","designation":"RFC 1654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1654.txt","https://www.rfc-editor.org/rfc/rfc1654.pdf"],"folder":"IETF/RFC-1654","files":{"txt":{"path":"standards/IETF/RFC-1654/RFC-1654.txt","sha256":"03a92b3c49fedc9df2e546b19879bfb8b0c84cbdf4fd2032b4f83b2fa8391f25"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1654 T.J. Watson Research Center, IBM Corp.\nCategory: Standards Track T. Li\n cisco Systems\n Editors\n July 1994\n\n A Border Gateway Protocol 4 (BGP-4)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Acknowledgements\n\n This document was originally published as RFC 1267 in October 1991,\n jointly authored by Kirk Lougheed (cisco Systems) and Yakov Rekhter\n (IBM).\n\n We would like to express our thanks to Guy Almes (Rice University),\n Len Bosack (cisco Systems), and Jeffrey C. Honig (Cornell University)\n for their contributions","scope_keywords":["1654","authentication","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1655","folder":"IETF/RFC-1655","source":"IETF/RFC-1655/RFC-1655.txt","version":null},{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2650","folder":"IETF/RFC-2650","source":"IETF/RFC-2650/RFC-2650.txt","version":null}],"search_text":"IETF RFC 1654 Network Working Group Y. Rekhter\nRequest for Comments: 1654 T.J. Watson Research Center, IBM Corp.\nCategory: Standards Track T. Li\n cisco Systems\n Editors\n July 1994\n\n A Border Gateway Protocol 4 (BGP-4)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Acknowledgements\n\n This document was originally published as RFC 1267 in October 1991,\n jointly authored by Kirk Lougheed (cisco Systems) and Yakov Rekhter\n (IBM).\n\n We would like to express our thanks to Guy Almes (Rice University),\n Len Bosack (cisco Systems), and Jeffrey C. Honig (Cornell University)\n for their contributions 1654 authentication path policies policy nested-reference unchanged"},{"id":"IETF RFC 1771","type":"specification","body":"IETF","designation":"RFC 1771","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1771.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1771.txt","https://www.rfc-editor.org/rfc/rfc1771.pdf"],"folder":"IETF/RFC-1771","files":{"txt":{"path":"standards/IETF/RFC-1771/RFC-1771.txt","sha256":"4d471245999e684ec4f06627a0896a4c6c108411428923a7df218d5a13f17d7d"}},"tags":["nested-reference","unchanged"],"summary":"This document, together with its companion document, \"Application of\n the Border Gateway Protocol in the Internet\", define an inter-\n autonomous system routing protocol for the Internet.\n\n1. Acknowledgements\n\n This document was originally published as RFC 1267 in October 1991,\n jointly authored by Kirk Lougheed (cisco Systems) and Yakov Rekhter\n (IBM).\n\n We would like to express our thanks to Guy Almes (ANS), Len Bosack\n (cisco Systems), and Jeffrey C. Honig (Cornell University) for their\n contributions to the earlier version of this document.\n\n We like to explicitly thank Bob Braden (ISI) for the review of the\n earlier version of this document as well as his constructive and\n valuable comments.\n\n We would also like to thank Bob Hinden, Director for Routing of the\n Internet Engineering Steering Group, and the team of reviewers he\n assembled to review the previous version (BGP-2) of this ","scope_keywords":["1771","authentication","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1772","folder":"IETF/RFC-1772","source":"IETF/RFC-1772/RFC-1772.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1863","folder":"IETF/RFC-1863","source":"IETF/RFC-1863/RFC-1863.txt","version":null},{"body":"IETF","designation":"RFC 1965","folder":"IETF/RFC-1965","source":"IETF/RFC-1965/RFC-1965.txt","version":null},{"body":"IETF","designation":"RFC 1966","folder":"IETF/RFC-1966","source":"IETF/RFC-1966/RFC-1966.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1997","folder":"IETF/RFC-1997","source":"IETF/RFC-1997/RFC-1997.txt","version":null},{"body":"IETF","designation":"RFC 1998","folder":"IETF/RFC-1998","source":"IETF/RFC-1998/RFC-1998.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2280","folder":"IETF/RFC-2280","source":"IETF/RFC-2280/RFC-2280.txt","version":null},{"body":"IETF","designation":"RFC 2283","folder":"IETF/RFC-2283","source":"IETF/RFC-2283/RFC-2283.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2796","folder":"IETF/RFC-2796","source":"IETF/RFC-2796/RFC-2796.txt","version":null},{"body":"IETF","designation":"RFC 2842","folder":"IETF/RFC-2842","source":"IETF/RFC-2842/RFC-2842.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2918","folder":"IETF/RFC-2918","source":"IETF/RFC-2918/RFC-2918.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3345","folder":"IETF/RFC-3345","source":"IETF/RFC-3345/RFC-3345.txt","version":null},{"body":"IETF","designation":"RFC 3392","folder":"IETF/RFC-3392","source":"IETF/RFC-3392/RFC-3392.txt","version":null},{"body":"IETF","designation":"RFC 3528","folder":"IETF/RFC-3528","source":"IETF/RFC-3528/RFC-3528.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4384","folder":"IETF/RFC-4384","source":"IETF/RFC-4384/RFC-4384.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null}],"search_text":"IETF RFC 1771 This document, together with its companion document, \"Application of\n the Border Gateway Protocol in the Internet\", define an inter-\n autonomous system routing protocol for the Internet.\n\n1. Acknowledgements\n\n This document was originally published as RFC 1267 in October 1991,\n jointly authored by Kirk Lougheed (cisco Systems) and Yakov Rekhter\n (IBM).\n\n We would like to express our thanks to Guy Almes (ANS), Len Bosack\n (cisco Systems), and Jeffrey C. Honig (Cornell University) for their\n contributions to the earlier version of this document.\n\n We like to explicitly thank Bob Braden (ISI) for the review of the\n earlier version of this document as well as his constructive and\n valuable comments.\n\n We would also like to thank Bob Hinden, Director for Routing of the\n Internet Engineering Steering Group, and the team of reviewers he\n assembled to review the previous version (BGP-2) of this  1771 authentication path policies policy nested-reference unchanged"},{"id":"IETF RFC 4271","type":"specification","body":"IETF","designation":"RFC 4271","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4271.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4271.txt","https://www.rfc-editor.org/rfc/rfc4271.pdf"],"folder":"IETF/RFC-4271","files":{"txt":{"path":"standards/IETF/RFC-4271/RFC-4271.txt","sha256":"98b851146abcd56ecbb398dd1a818bcde2dcac6fde3d901c423d988f86eaab76"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the Border Gateway Protocol (BGP), which is\n an inter-Autonomous System routing protocol.\n\n The primary function of a BGP speaking system is to exchange network\n reachability information with other BGP systems. This network\n reachability information includes information on the list of\n Autonomous Systems (ASes) that reachability information traverses.\n This information is sufficient for constructing a graph of AS\n connectivity for this reachability from which routing loops may be\n pruned, and, at the AS level, some policy decisions may be enforced.\n\n BGP-4 provides a set of mechanisms for supporting Classless Inter-\n Domain Routing (CIDR). These mechanisms include support for\n advertising a set of destinations as an IP prefix, and eliminating\n the concept of network \"class\" within BGP. BGP-4 also introduces\n mechanisms that allow aggregation of routes, including a","scope_keywords":["4271","attribute","attributes","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4724","folder":"IETF/RFC-4724","source":"IETF/RFC-4724/RFC-4724.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null},{"body":"IETF","designation":"RFC 4781","folder":"IETF/RFC-4781","source":"IETF/RFC-4781/RFC-4781.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5701","folder":"IETF/RFC-5701","source":"IETF/RFC-5701/RFC-5701.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 4271 This document discusses the Border Gateway Protocol (BGP), which is\n an inter-Autonomous System routing protocol.\n\n The primary function of a BGP speaking system is to exchange network\n reachability information with other BGP systems. This network\n reachability information includes information on the list of\n Autonomous Systems (ASes) that reachability information traverses.\n This information is sufficient for constructing a graph of AS\n connectivity for this reachability from which routing loops may be\n pruned, and, at the AS level, some policy decisions may be enforced.\n\n BGP-4 provides a set of mechanisms for supporting Classless Inter-\n Domain Routing (CIDR). These mechanisms include support for\n advertising a set of destinations as an IP prefix, and eliminating\n the concept of network \"class\" within BGP. BGP-4 also introduces\n mechanisms that allow aggregation of routes, including a 4271 attribute attributes path policy nested-reference unchanged"},{"id":"IETF RFC 2054","type":"specification","body":"IETF","designation":"RFC 2054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2054.txt","https://www.rfc-editor.org/rfc/rfc2054.pdf"],"folder":"IETF/RFC-2054","files":{"txt":{"path":"standards/IETF/RFC-2054/RFC-2054.txt","sha256":"b3e3320421859624cba4378de82edf299f4751b5bb58b978f0ac6b653bf406bb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a lightweight binding mechanism that allows\n NFS clients to obtain service from WebNFS-enabled servers with a\n minimum of protocol overhead. In removing this overhead, WebNFS\n clients see benefits in faster response to requests, easy transit of\n packet filter firewalls and TCP-based proxies, and better server\n scalability.","scope_keywords":["2054","attribute","attributes","path","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2054 This document describes a lightweight binding mechanism that allows\n NFS clients to obtain service from WebNFS-enabled servers with a\n minimum of protocol overhead. In removing this overhead, WebNFS\n clients see benefits in faster response to requests, easy transit of\n packet filter firewalls and TCP-based proxies, and better server\n scalability. 2054 attribute attributes path presentation registered nested-reference unchanged"},{"id":"IETF RFC 2055","type":"specification","body":"IETF","designation":"RFC 2055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2055.txt","https://www.rfc-editor.org/rfc/rfc2055.pdf"],"folder":"IETF/RFC-2055","files":{"txt":{"path":"standards/IETF/RFC-2055/RFC-2055.txt","sha256":"9784435bdc2daf7f5097d59126216c4c2a8ae1802b236019a6e8cf1a1a850b2f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the specifications for a server of WebNFS\n clients. WebNFS extends the semantics of versions 2 and 3 of the NFS\n protocols to allow clients to obtain filehandles more easily, without\n recourse to the portmap or MOUNT protocols. In removing the need for\n these protocols, WebNFS clients see benefits in faster response to\n requests, easy transit of firewalls and better server scalability\n This description is provided to facilitate compatible implementations\n of WebNFS servers.","scope_keywords":["2055","credential","credentials","path","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2055 This document describes the specifications for a server of WebNFS\n clients. WebNFS extends the semantics of versions 2 and 3 of the NFS\n protocols to allow clients to obtain filehandles more easily, without\n recourse to the portmap or MOUNT protocols. In removing the need for\n these protocols, WebNFS clients see benefits in faster response to\n requests, easy transit of firewalls and better server scalability\n This description is provided to facilitate compatible implementations\n of WebNFS servers. 2055 credential credentials path presentation registered nested-reference unchanged"},{"id":"IETF RFC 2224","type":"specification","body":"IETF","designation":"RFC 2224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2224.txt","https://www.rfc-editor.org/rfc/rfc2224.pdf"],"folder":"IETF/RFC-2224","files":{"txt":{"path":"standards/IETF/RFC-2224/RFC-2224.txt","sha256":"16fca15a33214e22112954b9e5937494e9a5417feeee57d6ccb12ef3fa4fafb8"}},"tags":["nested-reference","unchanged"],"summary":"A new URL scheme, 'nfs' is defined. It is used to refer to files and\n directories on NFS servers using the general URL syntax defined in\n RFC 1738, \"Uniform Resource Locators (URL)\".\n\n This scheme uses the public filehandle and multi-component lookup\n [RFC2054, RFC2055] to access server data with a minimum of protocol\n overhead.\n\n The NFS protocol provides access to shared filesystems across\n networks. It is designed to be machine, operating system, network\n architecture, and transport protocol independent. The protocol\n currently exists in two versions: version 2 [RFC1094] and version 3\n [RFC1813], both built on ONC RPC [RFC1831] at its associated eXternal\n Data Representation (XDR) [RFC1832] and Binding Protocol [RFC1833].","scope_keywords":["2224","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2224 A new URL scheme, 'nfs' is defined. It is used to refer to files and\n directories on NFS servers using the general URL syntax defined in\n RFC 1738, \"Uniform Resource Locators (URL)\".\n\n This scheme uses the public filehandle and multi-component lookup\n [RFC2054, RFC2055] to access server data with a minimum of protocol\n overhead.\n\n The NFS protocol provides access to shared filesystems across\n networks. It is designed to be machine, operating system, network\n architecture, and transport protocol independent. The protocol\n currently exists in two versions: version 2 [RFC1094] and version 3\n [RFC1813], both built on ONC RPC [RFC1831] at its associated eXternal\n Data Representation (XDR) [RFC1832] and Binding Protocol [RFC1833]. 2224 path presentation nested-reference unchanged"},{"id":"IETF RFC 2624","type":"specification","body":"IETF","designation":"RFC 2624","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2624.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2624.txt","https://www.rfc-editor.org/rfc/rfc2624.pdf"],"folder":"IETF/RFC-2624","files":{"txt":{"path":"standards/IETF/RFC-2624/RFC-2624.txt","sha256":"cb4d1a966424dcc26726b4830d97d32337f6c940bdcbefe4250d4026854065ba"}},"tags":["nested-reference","unchanged"],"summary":"The main task of the NFS version 4 working group is to create a\n protocol definition for a distributed file system that focuses on the\n following items: improved access and good performance on the\n Internet, strong security with negotiation built into the protocol,\n better cross-platform interoperability, and designed for protocol\n extensions. NFS version 4 will owe its general design to the\n previous versions of NFS. It is expected, however, that many\n features will be quite different in NFS version 4 than previous\n versions to facilitate the goals of the working group and to address\n areas that NFS version 2 and 3 have not.\n\n This design considerations document is meant to present more detail\n than the working group charter. Specifically, it presents the areas\n that the working group will investigate and consider while developing\n a protocol specification for NFS version 4. Based on th","scope_keywords":["2624","attribute","attributes","authentication","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2624 The main task of the NFS version 4 working group is to create a\n protocol definition for a distributed file system that focuses on the\n following items: improved access and good performance on the\n Internet, strong security with negotiation built into the protocol,\n better cross-platform interoperability, and designed for protocol\n extensions. NFS version 4 will owe its general design to the\n previous versions of NFS. It is expected, however, that many\n features will be quite different in NFS version 4 than previous\n versions to facilitate the goals of the working group and to address\n areas that NFS version 2 and 3 have not.\n\n This design considerations document is meant to present more detail\n than the working group charter. Specifically, it presents the areas\n that the working group will investigate and consider while developing\n a protocol specification for NFS version 4. Based on th 2624 attribute attributes authentication identification key path nested-reference unchanged"},{"id":"IETF RFC 2755","type":"specification","body":"IETF","designation":"RFC 2755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2755.txt","https://www.rfc-editor.org/rfc/rfc2755.pdf"],"folder":"IETF/RFC-2755","files":{"txt":{"path":"standards/IETF/RFC-2755/RFC-2755.txt","sha256":"f78c25c0be856f5e0606d125ecfa0918b808b8d492a28ce3cb4b7d51cf9943a0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for a WebNFS client [RFC2054] to\n negotiate the desired security mechanism with a WebNFS server\n [RFC2055] before the WebNFS client falls back to the MOUNT v3\n protocol [RFC1813]. This document is provided so that people can\n write compatible implementations.","scope_keywords":["2755","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 2755 This document describes a protocol for a WebNFS client [RFC2054] to\n negotiate the desired security mechanism with a WebNFS server\n [RFC2055] before the WebNFS client falls back to the MOUNT v3\n protocol [RFC1813]. This document is provided so that people can\n write compatible implementations. 2755 authentication path nested-reference unchanged"},{"id":"IETF RFC 3010","type":"specification","body":"IETF","designation":"RFC 3010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3010.txt","https://www.rfc-editor.org/rfc/rfc3010.pdf"],"folder":"IETF/RFC-3010","files":{"txt":{"path":"standards/IETF/RFC-3010/RFC-3010.txt","sha256":"3ede3993879f2690a5e2d1d327e0ad6c0c65f66c379bea7ed4756f9489c9aeac"}},"tags":["nested-reference","unchanged"],"summary":"NFS (Network File System) version 4 is a distributed file system\n protocol which owes heritage to NFS protocol versions 2 [RFC1094] and\n 3 [RFC1813]. Unlike earlier versions, the NFS version 4 protocol\n supports traditional file access while integrating support for file\n locking and the mount protocol. In addition, support for strong\n security (and its negotiation), compound operations, client caching,\n and internationalization have been added. Of course, attention has\n been applied to making NFS version 4 operate well in an Internet\n environment.\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nShepler, et al. Standards Track [Page 1]\n\f\nRFC 3010 NFS version 4 Protocol December 2000","scope_keywords":["3010","attribute","attributes","authentication","key","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 3010 NFS (Network File System) version 4 is a distributed file system\n protocol which owes heritage to NFS protocol versions 2 [RFC1094] and\n 3 [RFC1813]. Unlike earlier versions, the NFS version 4 protocol\n supports traditional file access while integrating support for file\n locking and the mount protocol. In addition, support for strong\n security (and its negotiation), compound operations, client caching,\n and internationalization have been added. Of course, attention has\n been applied to making NFS version 4 operate well in an Internet\n environment.\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nShepler, et al. Standards Track [Page 1]\n\f\nRFC 3010 NFS version 4 Protocol December 2000 3010 attribute attributes authentication key policy presentation nested-reference unchanged"},{"id":"IETF RFC 3530","type":"specification","body":"IETF","designation":"RFC 3530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3530.txt","https://www.rfc-editor.org/rfc/rfc3530.pdf"],"folder":"IETF/RFC-3530","files":{"txt":{"path":"standards/IETF/RFC-3530/RFC-3530.txt","sha256":"27533b3f13a8cc855290fc75ed8f6ba88df8f50b6525ece3af74c75e7ac942a7"}},"tags":["nested-reference","unchanged"],"summary":"The Network File System (NFS) version 4 is a distributed filesystem\n protocol which owes heritage to NFS protocol version 2, RFC 1094, and\n version 3, RFC 1813. Unlike earlier versions, the NFS version 4\n protocol supports traditional file access while integrating support\n for file locking and the mount protocol. In addition, support for\n strong security (and its negotiation), compound operations, client\n caching, and internationalization have been added. Of course,\n attention has been applied to making NFS version 4 operate well in an\n Internet environment.\n\n This document replaces RFC 3010 as the definition of the NFS version\n 4 protocol.\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\nShepler, et al. Standards Track [Page 1]","scope_keywords":["3530","attribute","attributes","authentication","key","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4331","folder":"IETF/RFC-4331","source":"IETF/RFC-4331/RFC-4331.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null}],"search_text":"IETF RFC 3530 The Network File System (NFS) version 4 is a distributed filesystem\n protocol which owes heritage to NFS protocol version 2, RFC 1094, and\n version 3, RFC 1813. Unlike earlier versions, the NFS version 4\n protocol supports traditional file access while integrating support\n for file locking and the mount protocol. In addition, support for\n strong security (and its negotiation), compound operations, client\n caching, and internationalization have been added. Of course,\n attention has been applied to making NFS version 4 operate well in an\n Internet environment.\n\n This document replaces RFC 3010 as the definition of the NFS version\n 4 protocol.\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\nShepler, et al. Standards Track [Page 1] 3530 attribute attributes authentication key policy presentation nested-reference unchanged"},{"id":"IETF RFC 5532","type":"specification","body":"IETF","designation":"RFC 5532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5532.txt","https://www.rfc-editor.org/rfc/rfc5532.pdf"],"folder":"IETF/RFC-5532","files":{"txt":{"path":"standards/IETF/RFC-5532/RFC-5532.txt","sha256":"b6dddcd7c08bbff30783739da79370238170be0f9f15ec4669e77c3f3923a651"}},"tags":["nested-reference","unchanged"],"summary":"This document addresses enabling the use of Remote Direct Memory\n Access (RDMA) by the Network File System (NFS) protocols. NFS\n implementations historically incur significant overhead due to data\n copies on end-host systems, as well as other processing overhead.\n This document explores the potential benefits of RDMA to these\n implementations and evaluates the reasons why RDMA is especially\n well-suited to NFS and network file protocols in general.\n\nTalpey & Juszczak Informational [Page 1]\n\f\nRFC 5532 NFS RDMA Problem Statement May 2009","scope_keywords":["5532","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null}],"search_text":"IETF RFC 5532 This document addresses enabling the use of Remote Direct Memory\n Access (RDMA) by the Network File System (NFS) protocols. NFS\n implementations historically incur significant overhead due to data\n copies on end-host systems, as well as other processing overhead.\n This document explores the potential benefits of RDMA to these\n implementations and evaluates the reasons why RDMA is especially\n well-suited to NFS and network file protocols in general.\n\nTalpey & Juszczak Informational [Page 1]\n\f\nRFC 5532 NFS RDMA Problem Statement May 2009 5532 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5666","type":"specification","body":"IETF","designation":"RFC 5666","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5666.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5666.txt","https://www.rfc-editor.org/rfc/rfc5666.pdf"],"folder":"IETF/RFC-5666","files":{"txt":{"path":"standards/IETF/RFC-5666/RFC-5666.txt","sha256":"4bee2ebb502e11e2248e36014102e368235972ac5ab206b0aad12ba51e8f8af1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol providing Remote Direct Memory\n Access (RDMA) as a new transport for Remote Procedure Call (RPC).\n The RDMA transport binding conveys the benefits of efficient, bulk-\n data transport over high-speed networks, while providing for minimal\n change to RPC applications and with no required revision of the\n application RPC protocol, or the RPC protocol itself.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may ","scope_keywords":["5666","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null}],"search_text":"IETF RFC 5666 This document describes a protocol providing Remote Direct Memory\n Access (RDMA) as a new transport for Remote Procedure Call (RPC).\n The RDMA transport binding conveys the benefits of efficient, bulk-\n data transport over high-speed networks, while providing for minimal\n change to RPC applications and with no required revision of the\n application RPC protocol, or the RPC protocol itself.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may  5666 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5667","type":"specification","body":"IETF","designation":"RFC 5667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5667.txt","https://www.rfc-editor.org/rfc/rfc5667.pdf"],"folder":"IETF/RFC-5667","files":{"txt":{"path":"standards/IETF/RFC-5667/RFC-5667.txt","sha256":"eb8e06e26f6b67d9e930e988b45e31c0772ef39969f4182ed9194368b925bb17"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the bindings of the various Network File System\n (NFS) versions to the Remote Direct Memory Access (RDMA) operations\n supported by the RPC/RDMA transport protocol. It describes the use\n of direct data placement by means of server-initiated RDMA operations\n into client-supplied buffers for implementations of NFS versions 2,\n 3, 4, and 4.1 over such an RDMA transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b","scope_keywords":["5667","http","key","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null}],"search_text":"IETF RFC 5667 This document defines the bindings of the various Network File System\n (NFS) versions to the Remote Direct Memory Access (RDMA) operations\n supported by the RPC/RDMA transport protocol. It describes the use\n of direct data placement by means of server-initiated RDMA operations\n into client-supplied buffers for implementations of NFS versions 2,\n 3, 4, and 4.1 over such an RDMA transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b 5667 http key license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7531","type":"specification","body":"IETF","designation":"RFC 7531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7531.txt","https://www.rfc-editor.org/rfc/rfc7531.pdf"],"folder":"IETF/RFC-7531","files":{"txt":{"path":"standards/IETF/RFC-7531/RFC-7531.txt","sha256":"cc37bc438258c16febef4813bb82c810ce458aa38954f7513e56736e034ddd2c"}},"tags":["nested-reference","unchanged"],"summary":"The Network File System (NFS) version 4 protocol is a distributed\n file system protocol that owes its heritage to NFS protocol version 2\n (RFC 1094) and version 3 (RFC 1813). Unlike earlier versions, the\n NFS version 4 protocol supports traditional file access while\n integrating support for file locking and the MOUNT protocol. In\n addition, support for strong security (and its negotiation), COMPOUND\n operations, client caching, and internationalization has been added.\n Of course, attention has been applied to making NFS version 4 operate\n well in an Internet environment.\n\n RFC 7530 formally obsoletes RFC 3530. This document, together with\n RFC 7530, replaces RFC 3530 as the definition of the NFS version 4\n protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus ","scope_keywords":["7531","holder","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 7531 The Network File System (NFS) version 4 protocol is a distributed\n file system protocol that owes its heritage to NFS protocol version 2\n (RFC 1094) and version 3 (RFC 1813). Unlike earlier versions, the\n NFS version 4 protocol supports traditional file access while\n integrating support for file locking and the MOUNT protocol. In\n addition, support for strong security (and its negotiation), COMPOUND\n operations, client caching, and internationalization has been added.\n Of course, attention has been applied to making NFS version 4 operate\n well in an Internet environment.\n\n RFC 7530 formally obsoletes RFC 3530. This document, together with\n RFC 7530, replaces RFC 3530 as the definition of the NFS version 4\n protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus  7531 holder http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1228","type":"specification","body":"IETF","designation":"RFC 1228","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1228.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1228.txt","https://www.rfc-editor.org/rfc/rfc1228.pdf"],"folder":"IETF/RFC-1228","files":{"txt":{"path":"standards/IETF/RFC-1228/RFC-1228.txt","sha256":"de12fa43eaef7fd4a67dcec6253b2a39fdd01a56660a22676c3789c3daf62cb1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Carpenter\nRequest for Comments: 1228 B. Wijnen\n T.J. Watson Research Center, IBM Corp.\n May 1991\n\n SNMP-DPI\n Simple Network Management Protocol\n Distributed Program Interface\n\nStatus of this Memo\n\n This RFC describes a protocol that International Business Machines\n Corporation (IBM) has been implementing in most of its SNMP agents to\n allow dynamic extension of supported MIBs. This is an Experimental\n Protocol for the Internet community. Discussion and suggestions for\n improvement are requested. Please refer to the current edition of\n the \"IAB Official Protocol Standards\" for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nABSTRACT\n\n The Simple Network Management Protocol (SNMP) [1] Distributed Program\n Interface (DPI) is an extension to SNMP agents that permits end-users\n to dynamically add, delete or replace mana","scope_keywords":["1228","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null}],"search_text":"IETF RFC 1228 Network Working Group G. Carpenter\nRequest for Comments: 1228 B. Wijnen\n T.J. Watson Research Center, IBM Corp.\n May 1991\n\n SNMP-DPI\n Simple Network Management Protocol\n Distributed Program Interface\n\nStatus of this Memo\n\n This RFC describes a protocol that International Business Machines\n Corporation (IBM) has been implementing in most of its SNMP agents to\n allow dynamic extension of supported MIBs. This is an Experimental\n Protocol for the Internet community. Discussion and suggestions for\n improvement are requested. Please refer to the current edition of\n the \"IAB Official Protocol Standards\" for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nABSTRACT\n\n The Simple Network Management Protocol (SNMP) [1] Distributed Program\n Interface (DPI) is an extension to SNMP agents that permits end-users\n to dynamically add, delete or replace mana 1228 management registered nested-reference unchanged"},{"id":"IETF RFC 1352","type":"specification","body":"IETF","designation":"RFC 1352","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1352.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1352.txt","https://www.rfc-editor.org/rfc/rfc1352.pdf"],"folder":"IETF/RFC-1352","files":{"txt":{"path":"standards/IETF/RFC-1352/RFC-1352.txt","sha256":"aef43316623afee230b3fe0d5ff6d482fa7ee9182cd885c6f707024e5cfa30e7"}},"tags":["nested-reference","unchanged"],"summary":"The Simple Network Management Protocol (SNMP) specification [1]\n allows for the protection of network management operations by a\n variety of security protocols. The SNMP administrative model\n described in [2] provides a framework for securing SNMP network\n management. In the context of that framework, this memo defines\n protocols to support the following three security services:\n\n o data integrity,\n\n o data origin authentication, and\n\n o data confidentiality.\n\n Please send comments to the SNMP Security Developers mailing list\n (snmp-sec-dev@tis.com).\n\n2. Introduction\n\n In the model described in [2], each SNMP party is, by definition,\n associated with a single authentication protocol. The authentication\n protocol provides a mechanism by which SNMP management communications\n transmitted by the party may be reliably identified as having\n originated from that party. The authentication protoc","scope_keywords":["1352","algorithm","authentication","delivery","encryption","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1334","folder":"IETF/RFC-1334","source":"IETF/RFC-1334/RFC-1334.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1353","folder":"IETF/RFC-1353","source":"IETF/RFC-1353/RFC-1353.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null}],"search_text":"IETF RFC 1352 The Simple Network Management Protocol (SNMP) specification [1]\n allows for the protection of network management operations by a\n variety of security protocols. The SNMP administrative model\n described in [2] provides a framework for securing SNMP network\n management. In the context of that framework, this memo defines\n protocols to support the following three security services:\n\n o data integrity,\n\n o data origin authentication, and\n\n o data confidentiality.\n\n Please send comments to the SNMP Security Developers mailing list\n (snmp-sec-dev@tis.com).\n\n2. Introduction\n\n In the model described in [2], each SNMP party is, by definition,\n associated with a single authentication protocol. The authentication\n protocol provides a mechanism by which SNMP management communications\n transmitted by the party may be reliably identified as having\n originated from that party. The authentication protoc 1352 algorithm authentication delivery encryption key management trust nested-reference unchanged"},{"id":"IETF RFC 110","type":"specification","body":"IETF","designation":"RFC 110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc110.txt","https://www.rfc-editor.org/rfc/rfc110.pdf"],"folder":"IETF/RFC-110","files":{"pdf":{"path":"standards/IETF/RFC-110/RFC-110.pdf","sha256":"ce9569ecda53db9ab7d81b8eebc6846cb3e1b9d8d22e5ca9d49933ae21c6138b"},"txt":{"path":"standards/IETF/RFC-110/RFC-110.txt","sha256":"948a63458fed5ba7e8fb351d194147e5ae63bf9156564b8a7aa8a4398f257811"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Winett\nRequest for Comments: 110 MIT Lincoln Laboratory\nNIC: 5809 25 March 1971\n\n Conventions for Using an IBM 2741 Terminal as a User Console for\n Access to Network Server Hosts\n\n Disclaimer\n\n This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.\n\n TO: NIC\n FROM: Joel M. Winnet (LL)\n SUBJECT: Conventions for Using an IBM 2741 Terminal as a User\n Console for Access to Network Server Hosts\n\n An IBM terminal can be used to key in 92 different codes. These\n include 88 graphics plus the 4 controls SP, BS, HT, and NL. Each of\n these have defined ASCII codes except the cent graphic ([1]) and the\n New Line Control (NL). When the NL character is keyed, the program\n receiving the keyboard input can translate this signal into the\n appr","scope_keywords":["110","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0137","folder":"IETF/RFC-0137","source":"IETF/RFC-0137/RFC-0137.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 137","folder":"IETF/RFC-137","source":"IETF/RFC-137/RFC-137.txt","version":null},{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null}],"search_text":"IETF RFC 110 Network Working Group J. Winett\nRequest for Comments: 110 MIT Lincoln Laboratory\nNIC: 5809 25 March 1971\n\n Conventions for Using an IBM 2741 Terminal as a User Console for\n Access to Network Server Hosts\n\n Disclaimer\n\n This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.\n\n TO: NIC\n FROM: Joel M. Winnet (LL)\n SUBJECT: Conventions for Using an IBM 2741 Terminal as a User\n Console for Access to Network Server Hosts\n\n An IBM terminal can be used to key in 92 different codes. These\n include 88 graphics plus the 4 controls SP, BS, HT, and NL. Each of\n these have defined ASCII codes except the cent graphic ([1]) and the\n New Line Control (NL). When the NL character is keyed, the program\n receiving the keyboard input can translate this signal into the\n appr 110 key subject nested-reference unchanged"},{"id":"IETF RFC 1415","type":"specification","body":"IETF","designation":"RFC 1415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1415.txt","https://www.rfc-editor.org/rfc/rfc1415.pdf"],"folder":"IETF/RFC-1415","files":{"txt":{"path":"standards/IETF/RFC-1415/RFC-1415.txt","sha256":"6706749264d9eed50fe517e7b2cca1c8b15c9acc21994d51f9726a4becb37c6b"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a dual protocol stack application layer gateway\n that performs protocol translation, in an interactive environment,\n between the FTP and FTAM file transfer protocols.\n\n Two key assumptions are made: 1) POSIX file naming conventions and\n hierarchical organization, rather than proprietary conventions are in\n use; and 2) X.500 Directory Services are available.\n\nAcknowledgments\n\n The authors of this RFC would like to express their appreciation to\n the individuals and organizations that participated in the\n implementation of the FTP-FTAM Application Layer Gateway and its\n fielding on the MILNET. Implementation credits go to Mr. John Scott,\n formerly of the MITRE Corporation, while fielding credits are\n extended to James Graham and R. Greg Lavender of Open Networks, Inc.\n (formerly NetWorks One) and Robert Cooney of the Naval Computer and\n Telecommunications Station (NCTS) ","scope_keywords":["1415","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1415 This memo describes a dual protocol stack application layer gateway\n that performs protocol translation, in an interactive environment,\n between the FTP and FTAM file transfer protocols.\n\n Two key assumptions are made: 1) POSIX file naming conventions and\n hierarchical organization, rather than proprietary conventions are in\n use; and 2) X.500 Directory Services are available.\n\nAcknowledgments\n\n The authors of this RFC would like to express their appreciation to\n the individuals and organizations that participated in the\n implementation of the FTP-FTAM Application Layer Gateway and its\n fielding on the MILNET. Implementation credits go to Mr. John Scott,\n formerly of the MITRE Corporation, while fielding credits are\n extended to James Graham and R. Greg Lavender of Open Networks, Inc.\n (formerly NetWorks One) and Robert Cooney of the Naval Computer and\n Telecommunications Station (NCTS)  1415 key management presentation nested-reference unchanged"},{"id":"IETF RFC 1102","type":"specification","body":"IETF","designation":"RFC 1102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1102.txt","https://www.rfc-editor.org/rfc/rfc1102.pdf"],"folder":"IETF/RFC-1102","files":{"txt":{"path":"standards/IETF/RFC-1102/RFC-1102.txt","sha256":"85d7fdbc20296830ede50557d838b4063083f3c8bba9fa9e22aca1b895d65068"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Clark\nRequest for Comments: 1102 M.I.T. Laboratory for Computer Science\n May 1989\n\n Policy Routing in Internet Protocols\n\n1. Status of this Memo\n\n The purpose of this RFC is to focus discussion on particular problems\n in the Internet and possible methods of solution. No proposed\n solutions in this document are intended as standards for the\n Internet. Distribution of this memo is unlimited.\n\n2. Introduction\n\n An integral component of the Internet protocols is the routing\n function, which determines the series of networks and gateways a\n packet will traverse in passing from the source to the destination.\n Although there have been a number of routing protocols used in the\n Internet, they share the idea that one route should be selected out\n of all available routes based on minimizing some measure of the\n route, such as delay. Recently, it has become important to sel","scope_keywords":["1102","algorithm","path","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1104","folder":"IETF/RFC-1104","source":"IETF/RFC-1104/RFC-1104.txt","version":null},{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null},{"body":"IETF","designation":"RFC 1164","folder":"IETF/RFC-1164","source":"IETF/RFC-1164/RFC-1164.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 1102 Network Working Group D. Clark\nRequest for Comments: 1102 M.I.T. Laboratory for Computer Science\n May 1989\n\n Policy Routing in Internet Protocols\n\n1. Status of this Memo\n\n The purpose of this RFC is to focus discussion on particular problems\n in the Internet and possible methods of solution. No proposed\n solutions in this document are intended as standards for the\n Internet. Distribution of this memo is unlimited.\n\n2. Introduction\n\n An integral component of the Internet protocols is the routing\n function, which determines the series of networks and gateways a\n packet will traverse in passing from the source to the destination.\n Although there have been a number of routing protocols used in the\n Internet, they share the idea that one route should be selected out\n of all available routes based on minimizing some measure of the\n route, such as delay. Recently, it has become important to sel 1102 algorithm path policies policy trust nested-reference unchanged"},{"id":"IETF RFC 1164","type":"specification","body":"IETF","designation":"RFC 1164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1164.txt","https://www.rfc-editor.org/rfc/rfc1164.pdf"],"folder":"IETF/RFC-1164","files":{"txt":{"path":"standards/IETF/RFC-1164/RFC-1164.txt","sha256":"edd2c51950a586957b0e81f97f91e7e7a4276bbfd0cbfe4f8c1bca16f14f5d78"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Honig, Cornell Univ. Theory Center\nRequest for Comments: 1164 D. Katz, Merit/NSFNET\n M. Mathis, Pittsburgh Supercomputing Center\n Y. Rekhter, T.J. Watson Research Center, IBM Corp\n J. Yu, Merit/NSFNET\n June 1990\n\n Application of the Border Gateway Protocol in the Internet\n\nStatus of this Memo\n\n This RFC, together with its companion RFC-1163, \"A Border Gateway\n Protocol (BGP)\", define a Proposed Standard for an inter-autonomous\n system routing protocol for the Internet.\n\n This protocol, like any other at this initial stage, may undergo\n modifications before reaching full Internet Standard status as a\n result of deployment experience. Implementers are encouraged to\n track the progress of this or any protocol as it moves through the\n standardization process, and to report their own experience with the\n protocol.\n\n This protocol is being considered by the Interconnec","scope_keywords":["1164","attribute","attributes","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1268","folder":"IETF/RFC-1268","source":"IETF/RFC-1268/RFC-1268.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1655","folder":"IETF/RFC-1655","source":"IETF/RFC-1655/RFC-1655.txt","version":null},{"body":"IETF","designation":"RFC 1772","folder":"IETF/RFC-1772","source":"IETF/RFC-1772/RFC-1772.txt","version":null}],"search_text":"IETF RFC 1164 Network Working Group J. Honig, Cornell Univ. Theory Center\nRequest for Comments: 1164 D. Katz, Merit/NSFNET\n M. Mathis, Pittsburgh Supercomputing Center\n Y. Rekhter, T.J. Watson Research Center, IBM Corp\n J. Yu, Merit/NSFNET\n June 1990\n\n Application of the Border Gateway Protocol in the Internet\n\nStatus of this Memo\n\n This RFC, together with its companion RFC-1163, \"A Border Gateway\n Protocol (BGP)\", define a Proposed Standard for an inter-autonomous\n system routing protocol for the Internet.\n\n This protocol, like any other at this initial stage, may undergo\n modifications before reaching full Internet Standard status as a\n result of deployment experience. Implementers are encouraged to\n track the progress of this or any protocol as it moves through the\n standardization process, and to report their own experience with the\n protocol.\n\n This protocol is being considered by the Interconnec 1164 attribute attributes path policy presentation nested-reference unchanged"},{"id":"IETF RFC 1479","type":"specification","body":"IETF","designation":"RFC 1479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1479.txt","https://www.rfc-editor.org/rfc/rfc1479.pdf"],"folder":"IETF/RFC-1479","files":{"txt":{"path":"standards/IETF/RFC-1479/RFC-1479.txt","sha256":"dffa3a537112832140c59c2058c7cdc04ab670f9afbf630515a6dd84c2374d4d"}},"tags":["nested-reference","unchanged"],"summary":"We present the set of protocols and procedures that constitute\n Inter-Domain Policy Routing (IDPR). IDPR includes the virtual\n gateway protocol, the flooding protocol, the route server query\n protocol, the route generation procedure, the path control protocol,\n and the data message forwarding procedure.\n\nContributors\n\n The following people have contributed to the protocols and procedures\n described in this document: Helen Bowns, Lee Breslau, Ken Carlberg,\n Isidro Castineyra, Deborah Estrin, Tony Li, Mike Little, Katia\n Obraczka, Sam Resheff, Martha Steenstrup, Gene Tsudik, and Robert\n Woodburn.","scope_keywords":["1479","management","path","policies","policy","timestamp","timestamps","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 1992","folder":"IETF/RFC-1992","source":"IETF/RFC-1992/RFC-1992.txt","version":null},{"body":"IETF","designation":"RFC 2154","folder":"IETF/RFC-2154","source":"IETF/RFC-2154/RFC-2154.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1479 We present the set of protocols and procedures that constitute\n Inter-Domain Policy Routing (IDPR). IDPR includes the virtual\n gateway protocol, the flooding protocol, the route server query\n protocol, the route generation procedure, the path control protocol,\n and the data message forwarding procedure.\n\nContributors\n\n The following people have contributed to the protocols and procedures\n described in this document: Helen Bowns, Lee Breslau, Ken Carlberg,\n Isidro Castineyra, Deborah Estrin, Tony Li, Mike Little, Katia\n Obraczka, Sam Resheff, Martha Steenstrup, Gene Tsudik, and Robert\n Woodburn. 1479 management path policies policy timestamp timestamps validation nested-reference unchanged"},{"id":"IETF RFC 2725","type":"specification","body":"IETF","designation":"RFC 2725","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2725.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2725.txt","https://www.rfc-editor.org/rfc/rfc2725.pdf"],"folder":"IETF/RFC-2725","files":{"txt":{"path":"standards/IETF/RFC-2725/RFC-2725.txt","sha256":"31018579afc9b4df24d3f68eba660aec4cfbc4faf723e021cd52955ee5bdf9e7"}},"tags":["nested-reference","unchanged"],"summary":"The RIPE database specifications and RPSL language define languages\n used as the basis for representing information in a routing policy\n system. A repository for routing policy system information is known\n as a routing registry. A routing registry provides a means of\n exchanging information needed to address many issues of importance to\n the operation of the Internet. The implementation and deployment of\n a routing policy system must maintain some degree of integrity to be\n of any operational use. This document addresses the need to assure\n integrity of the data by providing an authentication and\n authorization model.\n\nVillamizar, et al. Standards Track [Page 1]\n\f\nRFC 2725 Routing Policy System Security December 1999","scope_keywords":["2725","attribute","attributes","authentication","authorization","policies","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2726","folder":"IETF/RFC-2726","source":"IETF/RFC-2726/RFC-2726.txt","version":null},{"body":"IETF","designation":"RFC 2769","folder":"IETF/RFC-2769","source":"IETF/RFC-2769/RFC-2769.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4012","folder":"IETF/RFC-4012","source":"IETF/RFC-4012/RFC-4012.txt","version":null},{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null}],"search_text":"IETF RFC 2725 The RIPE database specifications and RPSL language define languages\n used as the basis for representing information in a routing policy\n system. A repository for routing policy system information is known\n as a routing registry. A routing registry provides a means of\n exchanging information needed to address many issues of importance to\n the operation of the Internet. The implementation and deployment of\n a routing policy system must maintain some degree of integrity to be\n of any operational use. This document addresses the need to assure\n integrity of the data by providing an authentication and\n authorization model.\n\nVillamizar, et al. Standards Track [Page 1]\n\f\nRFC 2725 Routing Policy System Security December 1999 2725 attribute attributes authentication authorization policies policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 1268","type":"specification","body":"IETF","designation":"RFC 1268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1268.txt","https://www.rfc-editor.org/rfc/rfc1268.pdf"],"folder":"IETF/RFC-1268","files":{"txt":{"path":"standards/IETF/RFC-1268/RFC-1268.txt","sha256":"fab1b34f78292555dbf7b23ddfcbce1aca2f0c50291ee9b1c6a008df960ea1bf"}},"tags":["nested-reference","unchanged"],"summary":"This document, together with its companion document, \"A Border\n Gateway Protocol (BGP-3)\", define an inter-autonomous system routing\n protocol for the Internet. \"A Border Gateway Protocol (BGP-3)\"\n defines the BGP protocol specification, and this document describes\n the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (iwg@rice.edu).","scope_keywords":["1268","key","path","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1265","folder":"IETF/RFC-1265","source":"IETF/RFC-1265/RFC-1265.txt","version":null},{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1269","folder":"IETF/RFC-1269","source":"IETF/RFC-1269/RFC-1269.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null}],"search_text":"IETF RFC 1268 This document, together with its companion document, \"A Border\n Gateway Protocol (BGP-3)\", define an inter-autonomous system routing\n protocol for the Internet. \"A Border Gateway Protocol (BGP-3)\"\n defines the BGP protocol specification, and this document describes\n the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (iwg@rice.edu). 1268 key path policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 1655","type":"specification","body":"IETF","designation":"RFC 1655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1655.txt","https://www.rfc-editor.org/rfc/rfc1655.pdf"],"folder":"IETF/RFC-1655","files":{"txt":{"path":"standards/IETF/RFC-1655/RFC-1655.txt","sha256":"1dced0d209bf48c64d29a74426b98ba382b49686aa1d06b368de200b6aafd39a"}},"tags":["nested-reference","unchanged"],"summary":"This document, together with its companion document, \"A Border\n Gateway Protocol 4 (BGP-4)\", define an inter-autonomous system\n routing protocol for the Internet. \"A Border Gateway Protocol 4\n (BGP-4)\" defines the BGP protocol specification, and this document\n describes the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (bgp@ans.net).\n\nAcknowledgements\n\n This document was originally published as RFC 1164 in June 1990,\n jointly authored by Jeffrey C. Honig (Cornell University), Dave Katz\n (MERIT), Matt Mathis (PSC), Yakov Rekhter (IBM), and Jessica Yu\n (MERIT).\n\n The following also made key contributions to RFC 1164 -- Guy Almes\n (ANS, then at Rice University), Kirk Lougheed (cisco Systems), Hans-\n Werner Braun (SDSC, then at MERIT), and Sue Hares (MERIT).\n\n We like to explicitly thank Bob Braden (ISI) fo","scope_keywords":["1655","key","path","pid","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null}],"search_text":"IETF RFC 1655 This document, together with its companion document, \"A Border\n Gateway Protocol 4 (BGP-4)\", define an inter-autonomous system\n routing protocol for the Internet. \"A Border Gateway Protocol 4\n (BGP-4)\" defines the BGP protocol specification, and this document\n describes the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (bgp@ans.net).\n\nAcknowledgements\n\n This document was originally published as RFC 1164 in June 1990,\n jointly authored by Jeffrey C. Honig (Cornell University), Dave Katz\n (MERIT), Matt Mathis (PSC), Yakov Rekhter (IBM), and Jessica Yu\n (MERIT).\n\n The following also made key contributions to RFC 1164 -- Guy Almes\n (ANS, then at Rice University), Kirk Lougheed (cisco Systems), Hans-\n Werner Braun (SDSC, then at MERIT), and Sue Hares (MERIT).\n\n We like to explicitly thank Bob Braden (ISI) fo 1655 key path pid policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 1772","type":"specification","body":"IETF","designation":"RFC 1772","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1772.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1772.txt","https://www.rfc-editor.org/rfc/rfc1772.pdf"],"folder":"IETF/RFC-1772","files":{"txt":{"path":"standards/IETF/RFC-1772/RFC-1772.txt","sha256":"4980fed2cb62e3fa1f9fec875859c0b3f79e2f3592ea7c79f661347b191f2e88"}},"tags":["nested-reference","unchanged"],"summary":"This document, together with its companion document, \"A Border\n Gateway Protocol 4 (BGP-4)\", define an inter-autonomous system\n routing protocol for the Internet. \"A Border Gateway Protocol 4\n (BGP-4)\" defines the BGP protocol specification, and this document\n describes the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (bgp@ans.net).\n\nAcknowledgements\n\n This document was originally published as RFC 1164 in June 1990,\n jointly authored by Jeffrey C. Honig (Cornell University), Dave Katz\n (MERIT), Matt Mathis (PSC), Yakov Rekhter (IBM), and Jessica Yu\n (MERIT).\n\n The following also made key contributions to RFC 1164 -- Guy Almes\n (ANS, then at Rice University), Kirk Lougheed (cisco Systems), Hans-\n Werner Braun (SDSC, then at MERIT), and Sue Hares (MERIT).\n\n We like to explicitly thank Bob Braden (ISI) fo","scope_keywords":["1772","key","path","pid","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null}],"search_text":"IETF RFC 1772 This document, together with its companion document, \"A Border\n Gateway Protocol 4 (BGP-4)\", define an inter-autonomous system\n routing protocol for the Internet. \"A Border Gateway Protocol 4\n (BGP-4)\" defines the BGP protocol specification, and this document\n describes the usage of the BGP in the Internet.\n\n Information about the progress of BGP can be monitored and/or\n reported on the BGP mailing list (bgp@ans.net).\n\nAcknowledgements\n\n This document was originally published as RFC 1164 in June 1990,\n jointly authored by Jeffrey C. Honig (Cornell University), Dave Katz\n (MERIT), Matt Mathis (PSC), Yakov Rekhter (IBM), and Jessica Yu\n (MERIT).\n\n The following also made key contributions to RFC 1164 -- Guy Almes\n (ANS, then at Rice University), Kirk Lougheed (cisco Systems), Hans-\n Werner Braun (SDSC, then at MERIT), and Sue Hares (MERIT).\n\n We like to explicitly thank Bob Braden (ISI) fo 1772 key path pid policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 1237","type":"specification","body":"IETF","designation":"RFC 1237","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1237.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1237.txt","https://www.rfc-editor.org/rfc/rfc1237.pdf"],"folder":"IETF/RFC-1237","files":{"pdf":{"path":"standards/IETF/RFC-1237/RFC-1237.pdf","sha256":"5db1c918ee19fc791c72efc8a54c422b292f5a93c1eb2546985d34930a861bf4"},"txt":{"path":"standards/IETF/RFC-1237/RFC-1237.txt","sha256":"96022cf25bd44cf10c985375db810ab47accc13483e9ee8cd10ed4de1a7b4ae0"}},"tags":["nested-reference","unchanged"],"summary":"The Internet is moving towards a multi-protocol environment that\n includes OSI. To support OSI in the Internet, an OSI lower layers\n infrastructure is required. This infrastructure comprises the\n connectionless network protocol (CLNP) and supporting routing\n protocols. Also required as part of this infrastructure are guidelines\n for network service access point (NSAP) address assignment. This paper\n provides guidelines for allocating NSAPs in the Internet.\n \n \n This document provides our current best judgment for the allocation\n of NSAP addresses in the Internet. This is intended to guide initial\n deployment of OSI 8473 (Connectionless Network Layer Protocol) in\n the Internet, as well as to solicit comments. It is expected that\n these guidelines may be further refined and this document updated as a\n result of experience gained during this initial deployment.\n \f\n \n \n \n \n RFC 1237 Guidelin","scope_keywords":["1237"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1277","folder":"IETF/RFC-1277","source":"IETF/RFC-1277/RFC-1277.txt","version":null},{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1518","folder":"IETF/RFC-1518","source":"IETF/RFC-1518/RFC-1518.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null}],"search_text":"IETF RFC 1237 The Internet is moving towards a multi-protocol environment that\n includes OSI. To support OSI in the Internet, an OSI lower layers\n infrastructure is required. This infrastructure comprises the\n connectionless network protocol (CLNP) and supporting routing\n protocols. Also required as part of this infrastructure are guidelines\n for network service access point (NSAP) address assignment. This paper\n provides guidelines for allocating NSAPs in the Internet.\n \n \n This document provides our current best judgment for the allocation\n of NSAP addresses in the Internet. This is intended to guide initial\n deployment of OSI 8473 (Connectionless Network Layer Protocol) in\n the Internet, as well as to solicit comments. It is expected that\n these guidelines may be further refined and this document updated as a\n result of experience gained during this initial deployment.\n \f\n \n \n \n \n RFC 1237 Guidelin 1237 nested-reference unchanged"},{"id":"IETF RFC 1265","type":"specification","body":"IETF","designation":"RFC 1265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1265.txt","https://www.rfc-editor.org/rfc/rfc1265.pdf"],"folder":"IETF/RFC-1265","files":{"txt":{"path":"standards/IETF/RFC-1265/RFC-1265.txt","sha256":"a7472134bbb3f345a7725739665f47f130314d5b6c195a1a065158fe8f0ed42f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter, Editor\nRequest for Comments: 1265 T.J. Watson Research Center, IBM Corp.\n October 1991\n\n BGP Protocol Analysis\n\n1. Status of this Memo.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n2. Introduction.\n\n The purpose of this report is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n the Border Gateway Protocol (BGP). This report summarizes the key\n feature of BGP, and analyzes the protocol with respect to scaling and\n performance. This is the first of two reports on the BGP protocol.\n\n BGP is an inter-autonomous system routing protocol designed for the\n TCP/IP internets. Version 1 of the BGP protocol was published in RFC\n 1105. Since then BGP versions 2 and 3 have been developed. Version 2\n was docume","scope_keywords":["1265","algorithm","algorithms","attribute","attributes","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1265 Network Working Group Y. Rekhter, Editor\nRequest for Comments: 1265 T.J. Watson Research Center, IBM Corp.\n October 1991\n\n BGP Protocol Analysis\n\n1. Status of this Memo.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n2. Introduction.\n\n The purpose of this report is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n the Border Gateway Protocol (BGP). This report summarizes the key\n feature of BGP, and analyzes the protocol with respect to scaling and\n performance. This is the first of two reports on the BGP protocol.\n\n BGP is an inter-autonomous system routing protocol designed for the\n TCP/IP internets. Version 1 of the BGP protocol was published in RFC\n 1105. Since then BGP versions 2 and 3 have been developed. Version 2\n was docume 1265 algorithm algorithms attribute attributes key path policy nested-reference unchanged"},{"id":"IETF RFC 1266","type":"specification","body":"IETF","designation":"RFC 1266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1266.txt","https://www.rfc-editor.org/rfc/rfc1266.pdf"],"folder":"IETF/RFC-1266","files":{"txt":{"path":"standards/IETF/RFC-1266/RFC-1266.txt","sha256":"6e1b3fdad653d7b68c3f561d4f725d1d02e53bdf89a79a36efdd669535dc9add"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter, Editor\nRequest for Comments: 1266 T.J. Watson Research Center, IBM Corp.\n October 1991\n\n Experience with the BGP Protocol\n\n1. Status of this Memo.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n2. Introduction.\n\n The purpose of this memo is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n Border Gateway Protocol (BGP). This report documents experience with\n BGP. This is the second of two reports on the BGP protocol. As\n required by the Internet Activities Board (IAB) and the Internet\n Engineering Steering Group (IESG), the first report will present a\n performance analysis of the BGP protocol.\n\n The remaining sections of this memo document how BGP satisfies\n General Requirements specified in Section","scope_keywords":["1266","attribute","attributes","authentication","management","path","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1266 Network Working Group Y. Rekhter, Editor\nRequest for Comments: 1266 T.J. Watson Research Center, IBM Corp.\n October 1991\n\n Experience with the BGP Protocol\n\n1. Status of this Memo.\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n2. Introduction.\n\n The purpose of this memo is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n Border Gateway Protocol (BGP). This report documents experience with\n BGP. This is the second of two reports on the BGP protocol. As\n required by the Internet Activities Board (IAB) and the Internet\n Engineering Steering Group (IESG), the first report will present a\n performance analysis of the BGP protocol.\n\n The remaining sections of this memo document how BGP satisfies\n General Requirements specified in Section 1266 attribute attributes authentication management path policy signature nested-reference unchanged"},{"id":"IETF RFC 1773","type":"specification","body":"IETF","designation":"RFC 1773","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1773.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1773.txt","https://www.rfc-editor.org/rfc/rfc1773.pdf"],"folder":"IETF/RFC-1773","files":{"txt":{"path":"standards/IETF/RFC-1773/RFC-1773.txt","sha256":"01cdfe871c4f1cad20618d97abfca878c04fdffbc31a48a97bd576498619d290"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Traina\nRequest for Comments: 1773 cisco Systems\nObsoletes: 1656 March 1995\nCategory: Informational\n\n Experience with the BGP-4 protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The purpose of this memo is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n Border Gateway Protocol version 4 (BGP-4). This report documents\n experience with BGP. This is the second of two reports on the BGP\n protocol. As required by the Internet Architecure Board (IAB) and\n the Internet Engineering Steering Group (IESG), the first report will\n present a performance analysis of the BGP protocol.\n\n The remaining sections of this memo document how BGP satisfies\n General Requ","scope_keywords":["1773","attribute","attributes","authentication","management","path","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null}],"search_text":"IETF RFC 1773 Network Working Group P. Traina\nRequest for Comments: 1773 cisco Systems\nObsoletes: 1656 March 1995\nCategory: Informational\n\n Experience with the BGP-4 protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The purpose of this memo is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n Border Gateway Protocol version 4 (BGP-4). This report documents\n experience with BGP. This is the second of two reports on the BGP\n protocol. As required by the Internet Architecure Board (IAB) and\n the Internet Engineering Steering Group (IESG), the first report will\n present a performance analysis of the BGP protocol.\n\n The remaining sections of this memo document how BGP satisfies\n General Requ 1773 attribute attributes authentication management path policy signature nested-reference unchanged"},{"id":"IETF RFC 1774","type":"specification","body":"IETF","designation":"RFC 1774","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1774.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1774.txt","https://www.rfc-editor.org/rfc/rfc1774.pdf"],"folder":"IETF/RFC-1774","files":{"txt":{"path":"standards/IETF/RFC-1774/RFC-1774.txt","sha256":"25e756837792c9911a0fa14d6927e4db1e06735a299b1177826f2b2a29c080f3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Traina, Editor\nRequest for Comments: 1774 cisco Systems\nCategory: Informational March 1995\n\n BGP-4 Protocol Analysis\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The purpose of this report is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n the Border Gateway Protocol version 4 (BGP-4). This report summarizes\n the key features of BGP, and analyzes the protocol with respect to\n scaling and performance. This is the first of two reports on the BGP\n protocol.\n\n BGP-4 is an inter-autonomous system routing protocol designed for\n TCP/IP internets. Version 1 of the BGP protocol was published in RFC\n 1105. Since then BGP versions 2, 3, and 4 have been develope","scope_keywords":["1774","algorithm","algorithms","attribute","attributes","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null}],"search_text":"IETF RFC 1774 Network Working Group P. Traina, Editor\nRequest for Comments: 1774 cisco Systems\nCategory: Informational March 1995\n\n BGP-4 Protocol Analysis\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n The purpose of this report is to document how the requirements for\n advancing a routing protocol to Draft Standard have been satisfied by\n the Border Gateway Protocol version 4 (BGP-4). This report summarizes\n the key features of BGP, and analyzes the protocol with respect to\n scaling and performance. This is the first of two reports on the BGP\n protocol.\n\n BGP-4 is an inter-autonomous system routing protocol designed for\n TCP/IP internets. Version 1 of the BGP protocol was published in RFC\n 1105. Since then BGP versions 2, 3, and 4 have been develope 1774 algorithm algorithms attribute attributes key path policy nested-reference unchanged"},{"id":"IETF RFC 3789","type":"specification","body":"IETF","designation":"RFC 3789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3789.txt","https://www.rfc-editor.org/rfc/rfc3789.pdf"],"folder":"IETF/RFC-3789","files":{"txt":{"path":"standards/IETF/RFC-3789/RFC-3789.txt","sha256":"b45b1343c16ec93a6bd28ecd330125b8727f59b2fabc5b822d397c43ae92a037"}},"tags":["nested-reference","unchanged"],"summary":"This document is a general overview and introduction to the v6ops\n IETF workgroup project of documenting all usage of IPv4 addresses in\n IETF standards track and experimental RFCs. It is broken into seven\n documents conforming to the current IETF areas. It also describes\n the methodology used during documentation, which types of RFCs have\n been documented, and provides a concatenated summary of results.","scope_keywords":["3789","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 3789 This document is a general overview and introduction to the v6ops\n IETF workgroup project of documenting all usage of IPv4 addresses in\n IETF standards track and experimental RFCs. It is broken into seven\n documents conforming to the current IETF areas. It also describes\n the methodology used during documentation, which types of RFCs have\n been documented, and provides a concatenated summary of results. 3789 management nested-reference unchanged"},{"id":"IETF RFC 1110","type":"specification","body":"IETF","designation":"RFC 1110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1110.txt","https://www.rfc-editor.org/rfc/rfc1110.pdf"],"folder":"IETF/RFC-1110","files":{"txt":{"path":"standards/IETF/RFC-1110/RFC-1110.txt","sha256":"695476bf93a97ef135df8d47f3957dec48278475b01a84fc7879517269b4c4a2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 1110 BBN STC\n August 1989\n\n A Problem with the TCP Big Window Option\n\nStatus of this Memo\n\n This memo comments on the TCP Big Window option described in RFC\n 1106. Distribution of this memo is unlimited.\n\nAbstract\n\n The TCP Big Window option discussed in RFC 1106 will not work\n properly in an Internet environment which has both a high bandwidth *\n delay product and the possibility of disordering and duplicating\n packets. In such networks, the window size must not be increased\n without a similar increase in the sequence number space. Therefore,\n a different approach to big windows should be taken in the Internet.\n\nDiscussion\n\n TCP was designed to work in a packet store-and-forward environment\n characterized by the possibility of packet loss, packet disordering,\n and packet duplication. Packet loss can occur, for example, by a\n conges","scope_keywords":["1110","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1185","folder":"IETF/RFC-1185","source":"IETF/RFC-1185/RFC-1185.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1110 Network Working Group A. McKenzie\nRequest for Comments: 1110 BBN STC\n August 1989\n\n A Problem with the TCP Big Window Option\n\nStatus of this Memo\n\n This memo comments on the TCP Big Window option described in RFC\n 1106. Distribution of this memo is unlimited.\n\nAbstract\n\n The TCP Big Window option discussed in RFC 1106 will not work\n properly in an Internet environment which has both a high bandwidth *\n delay product and the possibility of disordering and duplicating\n packets. In such networks, the window size must not be increased\n without a similar increase in the sequence number space. Therefore,\n a different approach to big windows should be taken in the Internet.\n\nDiscussion\n\n TCP was designed to work in a packet store-and-forward environment\n characterized by the possibility of packet loss, packet disordering,\n and packet duplication. Packet loss can occur, for example, by a\n conges 1110 delivery path nested-reference unchanged"},{"id":"IETF RFC 1588","type":"specification","body":"IETF","designation":"RFC 1588","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1588.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1588.txt","https://www.rfc-editor.org/rfc/rfc1588.pdf"],"folder":"IETF/RFC-1588","files":{"txt":{"path":"standards/IETF/RFC-1588/RFC-1588.txt","sha256":"4fb9c69d56065f7fa57fe6a075b7d8f4b12ebfa753b6bab49cc6c52373b44dec"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1588 C. Anderson\nCategory: Informational ISI\n February 1994\n\n WHITE PAGES MEETING REPORT\n\nSTATUS OF THIS MEMO\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nINTRODUCTION\n\n This report describes the results of a meeting held at the November\n IETF (Internet Engineering Task Force) in Houston, TX, on November 2,\n 1993, to discuss the future of and approaches to a white pages\n directory services for the Internet.\n\n As proposed to the National Science Foundation (NSF), USC/Information\n Sciences Institute (ISI) conducted the meeting to discuss the\n viability of the X.500 directory as a practical approach to providing\n white pages service for the Internet in the near future and to\n identify and discuss any alternatives.\n\n An ","scope_keywords":["1588","attribute","attributes","authentication","certificate","certificates","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null}],"search_text":"IETF RFC 1588 Network Working Group J. Postel\nRequest for Comments: 1588 C. Anderson\nCategory: Informational ISI\n February 1994\n\n WHITE PAGES MEETING REPORT\n\nSTATUS OF THIS MEMO\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nINTRODUCTION\n\n This report describes the results of a meeting held at the November\n IETF (Internet Engineering Task Force) in Houston, TX, on November 2,\n 1993, to discuss the future of and approaches to a white pages\n directory services for the Internet.\n\n As proposed to the National Science Foundation (NSF), USC/Information\n Sciences Institute (ISI) conducted the meeting to discuss the\n viability of the X.500 directory as a practical approach to providing\n white pages service for the Internet in the near future and to\n identify and discuss any alternatives.\n\n An  1588 attribute attributes authentication certificate certificates management nested-reference unchanged"},{"id":"IETF RFC 2218","type":"specification","body":"IETF","designation":"RFC 2218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2218.txt","https://www.rfc-editor.org/rfc/rfc2218.pdf"],"folder":"IETF/RFC-2218","files":{"txt":{"path":"standards/IETF/RFC-2218/RFC-2218.txt","sha256":"168e481d99c3649c26e31dbc5c1d76ef223d7253e624f9902449fc47a1be2c32"}},"tags":["nested-reference","unchanged"],"summary":"This work is the result of the IETF Integrated Directory Services\n (IDS) Working Group. The IDS Working Group proposes a standard\n specification for a simple Internet White Pages service by defining a\n common schema for use by the various White Pages servers. This\n schema is independent of specific implementations of the White Pages\n service.\n\n This document specifies the minimum set of core attributes of a White\n Pages entry for an individual and describes how new objects with\n those attributes can be defined and published. It does not describe\n how to represent other objects in the White Pages service. Further,\n it does not address the search sort expectations within a particular\n service.","scope_keywords":["2218","attribute","attributes","certificate","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2218 This work is the result of the IETF Integrated Directory Services\n (IDS) Working Group. The IDS Working Group proposes a standard\n specification for a simple Internet White Pages service by defining a\n common schema for use by the various White Pages servers. This\n schema is independent of specific implementations of the White Pages\n service.\n\n This document specifies the minimum set of core attributes of a White\n Pages entry for an individual and describes how new objects with\n those attributes can be defined and published. It does not describe\n how to represent other objects in the White Pages service. Further,\n it does not address the search sort expectations within a particular\n service. 2218 attribute attributes certificate presentation nested-reference unchanged"},{"id":"IETF RFC 1825","type":"specification","body":"IETF","designation":"RFC 1825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1825.txt","https://www.rfc-editor.org/rfc/rfc1825.pdf"],"folder":"IETF/RFC-1825","files":{"txt":{"path":"standards/IETF/RFC-1825/RFC-1825.txt","sha256":"2334d11403b61276c02c5ab1387d8cc377b84b2e904dead093f084f58c42bae4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Atkinson\nRequest for Comments: 1825 Naval Research Laboratory\nCategory: Standards Track August 1995\n\n Security Architecture for the Internet Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n This memo describes the security mechanisms for IP version 4 (IPv4)\n and IP version 6 (IPv6) and the services that they provide. Each\n security mechanism is specified in a separate document. This\n document also describes key management requirements for systems\n implementing those security mechanisms. This document is not an\n overall Security","scope_keywords":["1825","authentication","encryption","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2207","folder":"IETF/RFC-2207","source":"IETF/RFC-2207/RFC-2207.txt","version":null},{"body":"IETF","designation":"RFC 2243","folder":"IETF/RFC-2243","source":"IETF/RFC-2243/RFC-2243.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2362","folder":"IETF/RFC-2362","source":"IETF/RFC-2362/RFC-2362.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1825 Network Working Group R. Atkinson\nRequest for Comments: 1825 Naval Research Laboratory\nCategory: Standards Track August 1995\n\n Security Architecture for the Internet Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n This memo describes the security mechanisms for IP version 4 (IPv4)\n and IP version 6 (IPv6) and the services that they provide. Each\n security mechanism is specified in a separate document. This\n document also describes key management requirements for systems\n implementing those security mechanisms. This document is not an\n overall Security 1825 authentication encryption key management trust nested-reference unchanged"},{"id":"IETF RFC 1826","type":"specification","body":"IETF","designation":"RFC 1826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1826.txt","https://www.rfc-editor.org/rfc/rfc1826.pdf"],"folder":"IETF/RFC-1826","files":{"txt":{"path":"standards/IETF/RFC-1826/RFC-1826.txt","sha256":"89ebfb8b55ce4737890ec497f1c537ab739b911397a223784346ae7e6d0f0a39"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for providing cryptographic\n authentication for IPv4 and IPv6 datagrams. An Authentication Header\n (AH) is normally inserted after an IP header and before the other\n information being authenticated.\n\n1. INTRODUCTION\n\n The Authentication Header is a mechanism for providing strong\n integrity and authentication for IP datagrams. It might also provide\n non-repudiation, depending on which cryptographic algorithm is used\n and how keying is performed. For example, use of an asymmetric\n digital signature algorithm, such as RSA, could provide non-\n repudiation.\n\n Confidentiality, and protection from traffic analysis are not\n provided by the Authentication Header. Users desiring\n confidentiality should consider using the IP Encapsulating Security\n Protocol (ESP) either in lieu of or in conjunction with the\n Authentication Header [Atk95b]. This document assumes t","scope_keywords":["1826","algorithm","algorithms","authentication","key","keys","management","path","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1971","folder":"IETF/RFC-1971","source":"IETF/RFC-1971/RFC-1971.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2085","folder":"IETF/RFC-2085","source":"IETF/RFC-2085/RFC-2085.txt","version":null},{"body":"IETF","designation":"RFC 2104","folder":"IETF/RFC-2104","source":"IETF/RFC-2104/RFC-2104.txt","version":null},{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2207","folder":"IETF/RFC-2207","source":"IETF/RFC-2207/RFC-2207.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1826 This document describes a mechanism for providing cryptographic\n authentication for IPv4 and IPv6 datagrams. An Authentication Header\n (AH) is normally inserted after an IP header and before the other\n information being authenticated.\n\n1. INTRODUCTION\n\n The Authentication Header is a mechanism for providing strong\n integrity and authentication for IP datagrams. It might also provide\n non-repudiation, depending on which cryptographic algorithm is used\n and how keying is performed. For example, use of an asymmetric\n digital signature algorithm, such as RSA, could provide non-\n repudiation.\n\n Confidentiality, and protection from traffic analysis are not\n provided by the Authentication Header. Users desiring\n confidentiality should consider using the IP Encapsulating Security\n Protocol (ESP) either in lieu of or in conjunction with the\n Authentication Header [Atk95b]. This document assumes t 1826 algorithm algorithms authentication key keys management path signature nested-reference unchanged"},{"id":"IETF RFC 1827","type":"specification","body":"IETF","designation":"RFC 1827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1827.txt","https://www.rfc-editor.org/rfc/rfc1827.pdf"],"folder":"IETF/RFC-1827","files":{"txt":{"path":"standards/IETF/RFC-1827/RFC-1827.txt","sha256":"0368b1b478d97e6710a55e6a392d741198b33c0808750795c4f3b2af9b2810f2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the IP Encapsulating Security Payload (ESP).\n ESP is a mechanism for providing integrity and confidentiality to IP\n datagrams. In some circumstances it can also provide authentication\n to IP datagrams. The mechanism works with both IPv4 and IPv6.\n\n1. INTRODUCTION\n\n ESP is a mechanism for providing integrity and confidentiality to IP\n datagrams. It may also provide authentication, depending on which\n algorithm and algorithm mode are used. Non-repudiation and\n protection from traffic analysis are not provided by ESP. The IP\n Authentication Header (AH) might provide non-repudiation if used with\n certain authentication algorithms [Atk95b]. The IP Authentication\n Header may be used in conjunction with ESP to provide authentication.\n Users desiring integrity and authentication without confidentiality\n should use the IP Authentication Header (AH) instead of ESP. This\n do","scope_keywords":["1827","algorithm","algorithms","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2080","folder":"IETF/RFC-2080","source":"IETF/RFC-2080/RFC-2080.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2207","folder":"IETF/RFC-2207","source":"IETF/RFC-2207/RFC-2207.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1827 This document describes the IP Encapsulating Security Payload (ESP).\n ESP is a mechanism for providing integrity and confidentiality to IP\n datagrams. In some circumstances it can also provide authentication\n to IP datagrams. The mechanism works with both IPv4 and IPv6.\n\n1. INTRODUCTION\n\n ESP is a mechanism for providing integrity and confidentiality to IP\n datagrams. It may also provide authentication, depending on which\n algorithm and algorithm mode are used. Non-repudiation and\n protection from traffic analysis are not provided by ESP. The IP\n Authentication Header (AH) might provide non-repudiation if used with\n certain authentication algorithms [Atk95b]. The IP Authentication\n Header may be used in conjunction with ESP to provide authentication.\n Users desiring integrity and authentication without confidentiality\n should use the IP Authentication Header (AH) instead of ESP. This\n do 1827 algorithm algorithms authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 2401","type":"specification","body":"IETF","designation":"RFC 2401","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2401.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2401.txt","https://www.rfc-editor.org/rfc/rfc2401.pdf"],"folder":"IETF/RFC-2401","files":{"txt":{"path":"standards/IETF/RFC-2401/RFC-2401.txt","sha256":"d5d91e24b5fe2921bb0e4553d0e7384deefb54a5d24c7561edaac7c22f073bf2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 2401 BBN Corp\nObsoletes: 1825 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n Security Architecture for the Internet Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n1. Introduction........................................................3\n 1.1 Summary of Contents of Document..................................3\n 1.2 Audience.........................................................3\n 1.3 Related Docu","scope_keywords":["2401","algorithm","algorithms","attribute","attributes","audit","authentication","delivery","encryption","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2412","folder":"IETF/RFC-2412","source":"IETF/RFC-2412/RFC-2412.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2547","folder":"IETF/RFC-2547","source":"IETF/RFC-2547/RFC-2547.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2628","folder":"IETF/RFC-2628","source":"IETF/RFC-2628/RFC-2628.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3129","folder":"IETF/RFC-3129","source":"IETF/RFC-3129/RFC-3129.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3238","folder":"IETF/RFC-3238","source":"IETF/RFC-3238/RFC-3238.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3386","folder":"IETF/RFC-3386","source":"IETF/RFC-3386/RFC-3386.txt","version":null},{"body":"IETF","designation":"RFC 3423","folder":"IETF/RFC-3423","source":"IETF/RFC-3423/RFC-3423.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3457","folder":"IETF/RFC-3457","source":"IETF/RFC-3457/RFC-3457.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3706","folder":"IETF/RFC-3706","source":"IETF/RFC-3706/RFC-3706.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2401 Network Working Group S. Kent\nRequest for Comments: 2401 BBN Corp\nObsoletes: 1825 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n Security Architecture for the Internet Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n1. Introduction........................................................3\n 1.1 Summary of Contents of Document..................................3\n 1.2 Audience.........................................................3\n 1.3 Related Docu 2401 algorithm algorithms attribute attributes audit authentication delivery encryption key management path policy nested-reference unchanged"},{"id":"IETF RFC 3585","type":"specification","body":"IETF","designation":"RFC 3585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3585.txt","https://www.rfc-editor.org/rfc/rfc3585.pdf"],"folder":"IETF/RFC-3585","files":{"txt":{"path":"standards/IETF/RFC-3585/RFC-3585.txt","sha256":"5fdd6851374da53830e4a54650dfd1708f027d72a271fa4ca1d83bba27c06e6e"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an object-oriented information model of IP\n Security (IPsec) policy designed to facilitate agreement about the\n content and semantics of IPsec policy, and enable derivations of\n task-specific representations of IPsec policy such as storage schema,\n distribution representations, and policy specification languages used\n to configure IPsec-enabled endpoints. The information model\n described in this document models the configuration parameters\n defined by IPSec. The information model also covers the parameters\n found by the Internet Key Exchange protocol (IKE). Other key\n exchange protocols could easily be added to the information model by\n a simple extension. Further extensions can further be added easily\n due to the object-oriented nature of the model.\n\n This information model is based upon the core policy classes as\n defined in the Policy Core Information Model (PCI","scope_keywords":["3585","credential","key","management","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3585 This document presents an object-oriented information model of IP\n Security (IPsec) policy designed to facilitate agreement about the\n content and semantics of IPsec policy, and enable derivations of\n task-specific representations of IPsec policy such as storage schema,\n distribution representations, and policy specification languages used\n to configure IPsec-enabled endpoints. The information model\n described in this document models the configuration parameters\n defined by IPSec. The information model also covers the parameters\n found by the Internet Key Exchange protocol (IKE). Other key\n exchange protocols could easily be added to the information model by\n a simple extension. Further extensions can further be added easily\n due to the object-oriented nature of the model.\n\n This information model is based upon the core policy classes as\n defined in the Policy Core Information Model (PCI 3585 credential key management policy presentation nested-reference unchanged"},{"id":"IETF RFC 4807","type":"specification","body":"IETF","designation":"RFC 4807","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4807.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4807.txt","https://www.rfc-editor.org/rfc/rfc4807.pdf"],"folder":"IETF/RFC-4807","files":{"txt":{"path":"standards/IETF/RFC-4807/RFC-4807.txt","sha256":"aaa2bd18e808d741231b2acfd02847c009a74b374ce2de2f231ac84ffc8519c9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Structure of Management Information Version 2\n (SMIv2) Management Information Base (MIB) module for configuring the\n security policy database of a device implementing the IPsec protocol.\n The policy-based packet filtering and the corresponding execution of\n actions described in this document are of a more general nature than\n for IPsec configuration alone, such as for configuration of a\n firewall. This MIB module is designed to be extensible with other\n enterprise or standards-based defined packet filters and actions.\n\nBaer, et al. Standards Track [Page 1]\n\f\nRFC 4807 IPsec SPD configuration MIB March 2007","scope_keywords":["4807","key","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4807 This document defines a Structure of Management Information Version 2\n (SMIv2) Management Information Base (MIB) module for configuring the\n security policy database of a device implementing the IPsec protocol.\n The policy-based packet filtering and the corresponding execution of\n actions described in this document are of a more general nature than\n for IPsec configuration alone, such as for configuration of a\n firewall. This MIB module is designed to be extensible with other\n enterprise or standards-based defined packet filters and actions.\n\nBaer, et al. Standards Track [Page 1]\n\f\nRFC 4807 IPsec SPD configuration MIB March 2007 4807 key management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 111","type":"specification","body":"IETF","designation":"RFC 111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc111.txt","https://www.rfc-editor.org/rfc/rfc111.pdf"],"folder":"IETF/RFC-111","files":{"txt":{"path":"standards/IETF/RFC-111/RFC-111.txt","sha256":"54abc2af54a4abc319a665f076c7d9bd428324f50d7c9e1dc2d70e4655718e30"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRequest for Comments #111 UCLA\nNIC #5815 31 March 71\n\n Pressure from the Chairman\n\n[Categories: A.5;\n RFC's obsoleted: none;\n RFC's updated: 107]\n\nIt is time to set serious schedules for the implementation of NCP's and\nTelnets. To facilitate matters, John Heafner of Rand has agreed to\nmonitor each site's progress and test its implementation.\n\nNetwork Liaison Contacts are hereby responsible for preparing a schedule\nfor implementation and informing John. Such a schedule must include\ndates of\n\n (a) implementation of an NCP according to the specifications\n in Document #1 as modified by RFC #107;\n\n (b) implementation of a user-Telnet which enables local users to\n login to foreign Hosts;\n\n (c) implementation of a server-Telnet which enables foreign users to\n login on your Host;\n\n (d) documentation of the mechanism for connecting to and logging in\n to your Host;","scope_keywords":["111"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 111 Network Working Group S. Crocker\nRequest for Comments #111 UCLA\nNIC #5815 31 March 71\n\n Pressure from the Chairman\n\n[Categories: A.5;\n RFC's obsoleted: none;\n RFC's updated: 107]\n\nIt is time to set serious schedules for the implementation of NCP's and\nTelnets. To facilitate matters, John Heafner of Rand has agreed to\nmonitor each site's progress and test its implementation.\n\nNetwork Liaison Contacts are hereby responsible for preparing a schedule\nfor implementation and informing John. Such a schedule must include\ndates of\n\n (a) implementation of an NCP according to the specifications\n in Document #1 as modified by RFC #107;\n\n (b) implementation of a user-Telnet which enables local users to\n login to foreign Hosts;\n\n (c) implementation of a server-Telnet which enables foreign users to\n login on your Host;\n\n (d) documentation of the mechanism for connecting to and logging in\n to your Host; 111 nested-reference unchanged"},{"id":"IETF RFC 1111","type":"specification","body":"IETF","designation":"RFC 1111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1111.txt","https://www.rfc-editor.org/rfc/rfc1111.pdf"],"folder":"IETF/RFC-1111","files":{"txt":{"path":"standards/IETF/RFC-1111/RFC-1111.txt","sha256":"656f1ab6565059ff161a9661315eb99899c8fee5b6ab8833a8785a0b5ec12de3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1111 ISI\nObsoletes: 825 August 1989\n\n Request for Comments on Request for Comments\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This RFC specifies a standard for the Internet community. Authors of\n RFCs are expected to adopt and implement this standard. Distribution\n of this memo is unlimited.\n\n1. Introduction\n\n RFCs are distributed online by being stored as public access files,\n and a short message is sent to the distribution list indicating the\n availability of the memo.\n\n The online files are copied by the interested people and printed or\n displayed at their site on their equipment. (An RFC may also be\n returned via email in response to an email query.) This means that\n the format of the online files must meet the constraints of a wide\n variety of printing and display equipment.\n\n2. Format Rules\n\n To meet the distribution c","scope_keywords":["1111","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null}],"search_text":"IETF RFC 1111 Network Working Group J. Postel\nRequest for Comments: 1111 ISI\nObsoletes: 825 August 1989\n\n Request for Comments on Request for Comments\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This RFC specifies a standard for the Internet community. Authors of\n RFCs are expected to adopt and implement this standard. Distribution\n of this memo is unlimited.\n\n1. Introduction\n\n RFCs are distributed online by being stored as public access files,\n and a short message is sent to the distribution list indicating the\n availability of the memo.\n\n The online files are copied by the interested people and printed or\n displayed at their site on their equipment. (An RFC may also be\n returned via email in response to an email query.) This means that\n the format of the online files must meet the constraints of a wide\n variety of printing and display equipment.\n\n2. Format Rules\n\n To meet the distribution c 1111 subject nested-reference unchanged"},{"id":"IETF RFC 1234","type":"specification","body":"IETF","designation":"RFC 1234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1234.txt","https://www.rfc-editor.org/rfc/rfc1234.pdf"],"folder":"IETF/RFC-1234","files":{"txt":{"path":"standards/IETF/RFC-1234/RFC-1234.txt","sha256":"d81a0ee19c887a48c94ff587d4a5f66b9118488ee9b63c5e9af45381bbb1c9a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Provan\nRequest for Comments: 1234 Novell, Inc.\n June 1991\n\n Tunneling IPX Traffic through IP Networks\n\nStatus of this Memo\n\n This memo describes a method of encapsulating IPX datagrams within\n UDP packets so that IPX traffic can travel across an IP internet.\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Internet Packet eXchange protocol (IPX) is the internetwork protocol\n used by Novell's NetWare protocol suite. For the purposes of this\n paper, IPX is functionally equivalent to the Internet Datagram\n Protocol (IDP) from the Xerox Network Systems (XNS) protocol suite\n [1]. This mem","scope_keywords":["1234"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null}],"search_text":"IETF RFC 1234 Network Working Group D. Provan\nRequest for Comments: 1234 Novell, Inc.\n June 1991\n\n Tunneling IPX Traffic through IP Networks\n\nStatus of this Memo\n\n This memo describes a method of encapsulating IPX datagrams within\n UDP packets so that IPX traffic can travel across an IP internet.\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Internet Packet eXchange protocol (IPX) is the internetwork protocol\n used by Novell's NetWare protocol suite. For the purposes of this\n paper, IPX is functionally equivalent to the Internet Datagram\n Protocol (IDP) from the Xerox Network Systems (XNS) protocol suite\n [1]. This mem 1234 nested-reference unchanged"},{"id":"IETF RFC 1301","type":"specification","body":"IETF","designation":"RFC 1301","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1301.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1301.txt","https://www.rfc-editor.org/rfc/rfc1301.pdf"],"folder":"IETF/RFC-1301","files":{"txt":{"path":"standards/IETF/RFC-1301/RFC-1301.txt","sha256":"4a93450b3d55d2b85feb4fe27ae463d2ab825757ba19b933c1196997fff42d92"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Armstrong\nRequest for Comments: 1301 Xerox\n A. Freier\n Apple\n K. Marzullo\n Cornell\n February 1992\n\n Multicast Transport Protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This memo describes a protocol for reliable transport that utilizes\n the multicast capability of applicable lower layer networking\n architectures. The transport definition permits an arbitrary number\n of transport providers to perform realtime collaborations without\n requiring networking clients (aka, applications) to possess detailed\n knowledge of the population or geographical dispersion of the\n participating members. It is not network architectural specific, but\n does implicitly require some form of multicasting (or broadcasting)\n at the data link level, as we","scope_keywords":["1301","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 2357","folder":"IETF/RFC-2357","source":"IETF/RFC-2357/RFC-2357.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1301 Network Working Group S. Armstrong\nRequest for Comments: 1301 Xerox\n A. Freier\n Apple\n K. Marzullo\n Cornell\n February 1992\n\n Multicast Transport Protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This memo describes a protocol for reliable transport that utilizes\n the multicast capability of applicable lower layer networking\n architectures. The transport definition permits an arbitrary number\n of transport providers to perform realtime collaborations without\n requiring networking clients (aka, applications) to possess detailed\n knowledge of the population or geographical dispersion of the\n participating members. It is not network architectural specific, but\n does implicitly require some form of multicasting (or broadcasting)\n at the data link level, as we 1301 delivery key nested-reference unchanged"},{"id":"IETF RFC 1583","type":"specification","body":"IETF","designation":"RFC 1583","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1583.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1583.txt","https://www.rfc-editor.org/rfc/rfc1583.pdf"],"folder":"IETF/RFC-1583","files":{"pdf":{"path":"standards/IETF/RFC-1583/RFC-1583.pdf","sha256":"608f01196b76866b9028e81e668f724d894a5bc1dee8d896e0eb1e5b6beed2fb"},"txt":{"path":"standards/IETF/RFC-1583/RFC-1583.txt","sha256":"4e248256ce8b0df5957bf7e71d3bb44da412c2db60ca48cbc5b397666528a580"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents version 2 of the OSPF protocol. OSPF is a\n link-state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. Separate routes can be calculated\n for each IP Type of Service. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF\n routing protocol exchanges are authenticated.\n\n OSPF Version 2 was originally documented in RFC 1247. The\n differences between RFC 1247 and this memo are explain","scope_keywords":["1583","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1584","folder":"IETF/RFC-1584","source":"IETF/RFC-1584/RFC-1584.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1586","folder":"IETF/RFC-1586","source":"IETF/RFC-1586/RFC-1586.txt","version":null},{"body":"IETF","designation":"RFC 1587","folder":"IETF/RFC-1587","source":"IETF/RFC-1587/RFC-1587.txt","version":null},{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1765","folder":"IETF/RFC-1765","source":"IETF/RFC-1765/RFC-1765.txt","version":null},{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 2154","folder":"IETF/RFC-2154","source":"IETF/RFC-2154/RFC-2154.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2196","folder":"IETF/RFC-2196","source":"IETF/RFC-2196/RFC-2196.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3137","folder":"IETF/RFC-3137","source":"IETF/RFC-3137/RFC-3137.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null}],"search_text":"IETF RFC 1583 This memo documents version 2 of the OSPF protocol. OSPF is a\n link-state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. Separate routes can be calculated\n for each IP Type of Service. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF\n routing protocol exchanges are authenticated.\n\n OSPF Version 2 was originally documented in RFC 1247. The\n differences between RFC 1247 and this memo are explain 1583 path presentation nested-reference unchanged"},{"id":"IETF RFC 1769","type":"specification","body":"IETF","designation":"RFC 1769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1769.txt","https://www.rfc-editor.org/rfc/rfc1769.pdf"],"folder":"IETF/RFC-1769","files":{"txt":{"path":"standards/IETF/RFC-1769/RFC-1769.txt","sha256":"db08fb668a2bea49b2ed95461688fc770e4037dcb5e1a7b2e1d235201e3fead3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Mills\nRequest for Comments: 1769 University of Delaware\nObsoletes: 1361 March 1995\nCategory: Informational\n\n Simple Network Time Protocol (SNTP)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memorandum describes the Simple Network Time Protocol (SNTP),\n which is an adaptation of the Network Time Protocol (NTP) used to\n synchronize computer clocks in the Internet. SNTP can be used when\n the ultimate performance of the full NTP implementation described in\n RFC-1305 is not needed or justified. It can operate in both unicast\n modes (point to point) and broadcast modes (point to multipoint). It\n can also operate in IP multicast mode where this service is\n available. SNTP involves no change to the current or previou","scope_keywords":["1769","algorithm","algorithms","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null}],"search_text":"IETF RFC 1769 Network Working Group D. Mills\nRequest for Comments: 1769 University of Delaware\nObsoletes: 1361 March 1995\nCategory: Informational\n\n Simple Network Time Protocol (SNTP)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memorandum describes the Simple Network Time Protocol (SNTP),\n which is an adaptation of the Network Time Protocol (NTP) used to\n synchronize computer clocks in the Internet. SNTP can be used when\n the ultimate performance of the full NTP implementation described in\n RFC-1305 is not needed or justified. It can operate in both unicast\n modes (point to point) and broadcast modes (point to multipoint). It\n can also operate in IP multicast mode where this service is\n available. SNTP involves no change to the current or previou 1769 algorithm algorithms management path nested-reference unchanged"},{"id":"IETF RFC 1821","type":"specification","body":"IETF","designation":"RFC 1821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1821.txt","https://www.rfc-editor.org/rfc/rfc1821.pdf"],"folder":"IETF/RFC-1821","files":{"txt":{"path":"standards/IETF/RFC-1821/RFC-1821.txt","sha256":"0bd1a52f74729a09b758710e76973ebe24755eddd3dddcbb3d6088ffb56f0bdf"}},"tags":["nested-reference","unchanged"],"summary":"The IETF is currently developing an integrated service model which is\n designed to support real-time services on the Internet.\n Concurrently, the ATM Forum is developing Asynchronous Transfer Mode\n networking which similarly provides real-time networking support. The\n use of ATM in the Internet as a link layer protocol is already\n occurring, and both the IETF and the ATM Forum are producing\n specifications for IP over ATM. The purpose of this paper is to\n provide a clear statement of what issues need to be addressed in\n interfacing the IP integrated services environment with an ATM\n service environment so as to create a seamless interface between the\n two in support of end users desiring real-time networking services.","scope_keywords":["1821","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null}],"search_text":"IETF RFC 1821 The IETF is currently developing an integrated service model which is\n designed to support real-time services on the Internet.\n Concurrently, the ATM Forum is developing Asynchronous Transfer Mode\n networking which similarly provides real-time networking support. The\n use of ATM in the Internet as a link layer protocol is already\n occurring, and both the IETF and the ATM Forum are producing\n specifications for IP over ATM. The purpose of this paper is to\n provide a clear statement of what issues need to be addressed in\n interfacing the IP integrated services environment with an ATM\n service environment so as to create a seamless interface between the\n two in support of end users desiring real-time networking services. 1821 delivery nested-reference unchanged"},{"id":"IETF RFC 1885","type":"specification","body":"IETF","designation":"RFC 1885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1885.txt","https://www.rfc-editor.org/rfc/rfc1885.pdf"],"folder":"IETF/RFC-1885","files":{"txt":{"path":"standards/IETF/RFC-1885/RFC-1885.txt","sha256":"363296c1b121ba59f9acb4accfa8b1e7a8c3702958f38dd63dd7103ba007eca2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of Internet Control Message Protocol\n (ICMP) messages for use with version 6 of the Internet Protocol\n (IPv6). The Internet Group Management Protocol (IGMP) messages\n specified in STD 5, RFC 1112 have been merged into ICMP, for IPv6,\n and are included in this document.\n\nConta & Deering Standards Track [Page 1]\n\f\nRFC 1885 ICMPv6 (ICMP for IPv6) December 1995","scope_keywords":["1885","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1981","folder":"IETF/RFC-1981","source":"IETF/RFC-1981/RFC-1981.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null}],"search_text":"IETF RFC 1885 This document specifies a set of Internet Control Message Protocol\n (ICMP) messages for use with version 6 of the Internet Protocol\n (IPv6). The Internet Group Management Protocol (IGMP) messages\n specified in STD 5, RFC 1112 have been merged into ICMP, for IPv6,\n and are included in this document.\n\nConta & Deering Standards Track [Page 1]\n\f\nRFC 1885 ICMPv6 (ICMP for IPv6) December 1995 1885 management path subject nested-reference unchanged"},{"id":"IETF RFC 2002","type":"specification","body":"IETF","designation":"RFC 2002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2002.txt","https://www.rfc-editor.org/rfc/rfc2002.pdf"],"folder":"IETF/RFC-2002","files":{"txt":{"path":"standards/IETF/RFC-2002/RFC-2002.txt","sha256":"2bbf507d2b9d3b5f754591ce18fcbd443c83f564931f223f942492f95d4718ca"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.","scope_keywords":["2002","authentication","key","management","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2004","folder":"IETF/RFC-2004","source":"IETF/RFC-2004/RFC-2004.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2267","folder":"IETF/RFC-2267","source":"IETF/RFC-2267/RFC-2267.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2644","folder":"IETF/RFC-2644","source":"IETF/RFC-2644/RFC-2644.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2827","folder":"IETF/RFC-2827","source":"IETF/RFC-2827/RFC-2827.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3025","folder":"IETF/RFC-3025","source":"IETF/RFC-3025/RFC-3025.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null},{"body":"IETF","designation":"RFC 3141","folder":"IETF/RFC-3141","source":"IETF/RFC-3141/RFC-3141.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 2002 This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node. 2002 authentication key management timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2030","type":"specification","body":"IETF","designation":"RFC 2030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2030.txt","https://www.rfc-editor.org/rfc/rfc2030.pdf"],"folder":"IETF/RFC-2030","files":{"txt":{"path":"standards/IETF/RFC-2030/RFC-2030.txt","sha256":"a8ab6d00a5e249385742c6d320b06ff795763db5020a63cfe5f94909bceb6467"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Mills\nRequest for Comments: 2030 University of Delaware\nObsoletes: 1769 October 1996\nCategory: Informational\n\n Simple Network Time Protocol (SNTP) Version 4\n for IPv4, IPv6 and OSI\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memorandum describes the Simple Network Time Protocol (SNTP)\n Version 4, which is an adaptation of the Network Time Protocol (NTP)\n used to synchronize computer clocks in the Internet. SNTP can be used\n when the ultimate performance of the full NTP implementation\n described in RFC-1305 is not needed or justified. When operating with\n current and previous NTP and SNTP versions, SNTP Version 4 involves\n no changes to the NTP specification or known implementations, but\n rather a clarificati","scope_keywords":["2030","algorithm","algorithms","authentication","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3643","folder":"IETF/RFC-3643","source":"IETF/RFC-3643/RFC-3643.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4075","folder":"IETF/RFC-4075","source":"IETF/RFC-4075/RFC-4075.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2030 Network Working Group D. Mills\nRequest for Comments: 2030 University of Delaware\nObsoletes: 1769 October 1996\nCategory: Informational\n\n Simple Network Time Protocol (SNTP) Version 4\n for IPv4, IPv6 and OSI\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memorandum describes the Simple Network Time Protocol (SNTP)\n Version 4, which is an adaptation of the Network Time Protocol (NTP)\n used to synchronize computer clocks in the Internet. SNTP can be used\n when the ultimate performance of the full NTP implementation\n described in RFC-1305 is not needed or justified. When operating with\n current and previous NTP and SNTP versions, SNTP Version 4 involves\n no changes to the NTP specification or known implementations, but\n rather a clarificati 2030 algorithm algorithms authentication http path nested-reference unchanged"},{"id":"IETF RFC 2117","type":"specification","body":"IETF","designation":"RFC 2117","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2117.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2117.txt","https://www.rfc-editor.org/rfc/rfc2117.pdf"],"folder":"IETF/RFC-2117","files":{"txt":{"path":"standards/IETF/RFC-2117/RFC-2117.txt","sha256":"48e8bbf197744203198632c0ad3c98291fb96171f247426a7c29bf0a2ced09c4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Estrin\nRequest for Comments: 2117 USC\nCategory: Experimental D. Farinacci\n CISCO\n A. Helmy\n USC\n D. Thaler\n UMICH\n S. Deering\n XEROX\n M. Handley\n UCL\n V. Jacobson\n LBL\n C. Liu\n USC\n P. Sharma\n USC\n L. Wei\n CISCO\n June 1997\n\n Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol\n Specification\n\nStatus of This Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n The author list has been reordered to reflect the involvement in\n detailed editorial work on this specification document. The first\n four authors are the primary editors and are listed alphabetically.\n The rest of the authors, also listed alphabetically, participated in\n all aspects of the archit","scope_keywords":["2117","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null}],"search_text":"IETF RFC 2117 Network Working Group D. Estrin\nRequest for Comments: 2117 USC\nCategory: Experimental D. Farinacci\n CISCO\n A. Helmy\n USC\n D. Thaler\n UMICH\n S. Deering\n XEROX\n M. Handley\n UCL\n V. Jacobson\n LBL\n C. Liu\n USC\n P. Sharma\n USC\n L. Wei\n CISCO\n June 1997\n\n Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol\n Specification\n\nStatus of This Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n The author list has been reordered to reflect the involvement in\n detailed editorial work on this specification document. The first\n four authors are the primary editors and are listed alphabetically.\n The rest of the authors, also listed alphabetically, participated in\n all aspects of the archit 2117 management path nested-reference unchanged"},{"id":"IETF RFC 2178","type":"specification","body":"IETF","designation":"RFC 2178","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2178.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2178.txt","https://www.rfc-editor.org/rfc/rfc2178.pdf"],"folder":"IETF/RFC-2178","files":{"txt":{"path":"standards/IETF/RFC-2178/RFC-2178.txt","sha256":"acf896cc9d02e7f2f75c9ceb28fe1f0e3ec7e3adf446461c283bb4b0f2d2e0dc"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents version 2 of the OSPF protocol. OSPF is a link-\n state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF routing\n protocol exchanges are authenticated.\n\n The differences between this memo and RFC 1583 are explained in\n Appendix G. All differences are backward-compatible in nature.\n Implementations of this memo and of RFC 1583 wi","scope_keywords":["2178","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null}],"search_text":"IETF RFC 2178 This memo documents version 2 of the OSPF protocol. OSPF is a link-\n state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF routing\n protocol exchanges are authenticated.\n\n The differences between this memo and RFC 1583 are explained in\n Appendix G. All differences are backward-compatible in nature.\n Implementations of this memo and of RFC 1583 wi 2178 path presentation nested-reference unchanged"},{"id":"IETF RFC 2236","type":"specification","body":"IETF","designation":"RFC 2236","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2236.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2236.txt","https://www.rfc-editor.org/rfc/rfc2236.pdf"],"folder":"IETF/RFC-2236","files":{"txt":{"path":"standards/IETF/RFC-2236/RFC-2236.txt","sha256":"0c8fc75ffb7251cad7452b31b43333ccbc3a53e0541069c47c571933fca46862"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents IGMPv2, used by IP hosts to report their\n multicast group memberships to routers. It updates STD 5, RFC 1112.\n\n IGMPv2 allows group membership termination to be quickly reported to\n the routing protocol, which is important for high-bandwidth multicast\n groups and/or subnets with highly volatile group membership.\n\n This document is a product of the Inter-Domain Multicast Routing\n working group within the Internet Engineering Task Force. Comments\n are solicited and should be addressed to the working group's mailing\n list at idmr@cs.ucl.ac.uk and/or the author(s).\n\n1. Definitions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC 2119].\n\n2. Introduction\n\n The Internet Group Management Protocol (IGMP) is used by IP hosts to","scope_keywords":["2236","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2362","folder":"IETF/RFC-2362","source":"IETF/RFC-2362/RFC-2362.txt","version":null},{"body":"IETF","designation":"RFC 2435","folder":"IETF/RFC-2435","source":"IETF/RFC-2435/RFC-2435.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2715","folder":"IETF/RFC-2715","source":"IETF/RFC-2715/RFC-2715.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3228","folder":"IETF/RFC-3228","source":"IETF/RFC-3228/RFC-3228.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null}],"search_text":"IETF RFC 2236 This memo documents IGMPv2, used by IP hosts to report their\n multicast group memberships to routers. It updates STD 5, RFC 1112.\n\n IGMPv2 allows group membership termination to be quickly reported to\n the routing protocol, which is important for high-bandwidth multicast\n groups and/or subnets with highly volatile group membership.\n\n This document is a product of the Inter-Domain Multicast Routing\n working group within the Internet Engineering Task Force. Comments\n are solicited and should be addressed to the working group's mailing\n list at idmr@cs.ucl.ac.uk and/or the author(s).\n\n1. Definitions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC 2119].\n\n2. Introduction\n\n The Internet Group Management Protocol (IGMP) is used by IP hosts to 2236 key management nested-reference unchanged"},{"id":"IETF RFC 2250","type":"specification","body":"IETF","designation":"RFC 2250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2250.txt","https://www.rfc-editor.org/rfc/rfc2250.pdf"],"folder":"IETF/RFC-2250","files":{"txt":{"path":"standards/IETF/RFC-2250/RFC-2250.txt","sha256":"8d6cafb0a9f6ab81f968d1d243ed6c73bd606275bd6558fd8f03e9c1c3ae332d"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a packetization scheme for MPEG video and audio\n streams. The scheme proposed can be used to transport such a video\n or audio flow over the transport protocols supported by RTP. Two\n approaches are described. The first is designed to support maximum\n interoperability with MPEG System environments. The second is\n designed to provide maximum compatibility with other RTP-encapsulated\n media streams and future conference control work of the IETF.\n\n This memo is a revision of RFC 2038, an Internet standards track\n protocol. In this revision, the packet loss resilience mechanisms in\n Section 3.4 were extended to include additional picture header\n information required for MPEG2. A new section on security\n considerations for this payload type is added.\n\nHoffman, et. al. Standards Track [Page 1]\n\f\nRFC 2250 RTP Format for MPEG1/MPEG2 Video January 1998\n\n1. Introduction\n\n ISO/IE","scope_keywords":["2250","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2343","folder":"IETF/RFC-2343","source":"IETF/RFC-2343/RFC-2343.txt","version":null},{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2250 This memo describes a packetization scheme for MPEG video and audio\n streams. The scheme proposed can be used to transport such a video\n or audio flow over the transport protocols supported by RTP. Two\n approaches are described. The first is designed to support maximum\n interoperability with MPEG System environments. The second is\n designed to provide maximum compatibility with other RTP-encapsulated\n media streams and future conference control work of the IETF.\n\n This memo is a revision of RFC 2038, an Internet standards track\n protocol. In this revision, the packet loss resilience mechanisms in\n Section 3.4 were extended to include additional picture header\n information required for MPEG2. A new section on security\n considerations for this payload type is added.\n\nHoffman, et. al. Standards Track [Page 1]\n\f\nRFC 2250 RTP Format for MPEG1/MPEG2 Video January 1998\n\n1. Introduction\n\n ISO/IE 2250 presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 2328","type":"specification","body":"IETF","designation":"RFC 2328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2328.txt","https://www.rfc-editor.org/rfc/rfc2328.pdf"],"folder":"IETF/RFC-2328","files":{"txt":{"path":"standards/IETF/RFC-2328/RFC-2328.txt","sha256":"981690e297fbba9e8ef655802552b5529cb17f1ffe790ad2d55706cc522ff50c"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents version 2 of the OSPF protocol. OSPF is a\n link-state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF\n routing protocol exchanges are authenticated.\n\n The differences between this memo and RFC 2178 are explained in\n Appendix G. All differences are backward-compatible in nature.\n\nMoy Standards Track [Page 1]\n\f\nRFC 2328 OSPF Ver","scope_keywords":["2328","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2991","folder":"IETF/RFC-2991","source":"IETF/RFC-2991/RFC-2991.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null},{"body":"IETF","designation":"RFC 3137","folder":"IETF/RFC-3137","source":"IETF/RFC-3137/RFC-3137.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3509","folder":"IETF/RFC-3509","source":"IETF/RFC-3509/RFC-3509.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4136","folder":"IETF/RFC-4136","source":"IETF/RFC-4136/RFC-4136.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4222","folder":"IETF/RFC-4222","source":"IETF/RFC-4222/RFC-4222.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4811","folder":"IETF/RFC-4811","source":"IETF/RFC-4811/RFC-4811.txt","version":null},{"body":"IETF","designation":"RFC 4812","folder":"IETF/RFC-4812","source":"IETF/RFC-4812/RFC-4812.txt","version":null},{"body":"IETF","designation":"RFC 4813","folder":"IETF/RFC-4813","source":"IETF/RFC-4813/RFC-4813.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5243","folder":"IETF/RFC-5243","source":"IETF/RFC-5243/RFC-5243.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 2328 This memo documents version 2 of the OSPF protocol. OSPF is a\n link-state routing protocol. It is designed to be run internal to a\n single Autonomous System. Each OSPF router maintains an identical\n database describing the Autonomous System's topology. From this\n database, a routing table is calculated by constructing a shortest-\n path tree.\n\n OSPF recalculates routes quickly in the face of topological changes,\n utilizing a minimum of routing protocol traffic. OSPF provides\n support for equal-cost multipath. An area routing capability is\n provided, enabling an additional level of routing protection and a\n reduction in routing protocol traffic. In addition, all OSPF\n routing protocol exchanges are authenticated.\n\n The differences between this memo and RFC 2178 are explained in\n Appendix G. All differences are backward-compatible in nature.\n\nMoy Standards Track [Page 1]\n\f\nRFC 2328 OSPF Ver 2328 path presentation nested-reference unchanged"},{"id":"IETF RFC 2362","type":"specification","body":"IETF","designation":"RFC 2362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2362.txt","https://www.rfc-editor.org/rfc/rfc2362.pdf"],"folder":"IETF/RFC-2362","files":{"txt":{"path":"standards/IETF/RFC-2362/RFC-2362.txt","sha256":"9b6fa7209a55166ef7ee9ba721bdc307fe02af6469fb66f6898c9447c22e0057"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Estrin\nRequest for Comments: 2362 USC\nObsoletes: 2117 D. Farinacci\nCategory: Experimental CISCO\n A. Helmy\n USC\n D. Thaler\n UMICH\n S. Deering\n XEROX\n M. Handley\n UCL\n V. Jacobson\n LBL\n C. Liu\n USC\n P. Sharma\n USC\n L. Wei\n CISCO\n June 1998\n\n Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol\n Specification\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nEstrin, et. al. Experimental [Page 1]\n\f\nRFC 2362 PIM-SM June 1998\n\n1 Introduction\n\n This document describes a protocol for efficiently routing to\n multicast groups that may span wide-area (and inter-domain)\n internets. We re","scope_keywords":["2362","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2365","folder":"IETF/RFC-2365","source":"IETF/RFC-2365/RFC-2365.txt","version":null},{"body":"IETF","designation":"RFC 2715","folder":"IETF/RFC-2715","source":"IETF/RFC-2715/RFC-2715.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2991","folder":"IETF/RFC-2991","source":"IETF/RFC-2991/RFC-2991.txt","version":null},{"body":"IETF","designation":"RFC 2992","folder":"IETF/RFC-2992","source":"IETF/RFC-2992/RFC-2992.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 2362 Network Working Group D. Estrin\nRequest for Comments: 2362 USC\nObsoletes: 2117 D. Farinacci\nCategory: Experimental CISCO\n A. Helmy\n USC\n D. Thaler\n UMICH\n S. Deering\n XEROX\n M. Handley\n UCL\n V. Jacobson\n LBL\n C. Liu\n USC\n P. Sharma\n USC\n L. Wei\n CISCO\n June 1998\n\n Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol\n Specification\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nEstrin, et. al. Experimental [Page 1]\n\f\nRFC 2362 PIM-SM June 1998\n\n1 Introduction\n\n This document describes a protocol for efficiently routing to\n multicast groups that may span wide-area (and inter-domain)\n internets. We re 2362 management path nested-reference unchanged"},{"id":"IETF RFC 2588","type":"specification","body":"IETF","designation":"RFC 2588","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2588.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2588.txt","https://www.rfc-editor.org/rfc/rfc2588.pdf"],"folder":"IETF/RFC-2588","files":{"txt":{"path":"standards/IETF/RFC-2588/RFC-2588.txt","sha256":"2cff1271f8d04341e0476121ff0e1801335d688678d70d21c9a3a2b7a9e557ca"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Finlayson\nRequest for Comments: 2588 LIVE.COM\nCategory: Informational May 1999\n\n IP Multicast and Firewalls\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n Many organizations use a firewall computer that acts as a security\n gateway between the public Internet and their private, internal\n 'intranet'. In this document, we discuss the issues surrounding the\n traversal of IP multicast traffic across a firewall, and describe\n possible ways in which a firewall can implement and control this\n traversal. We also explain why some firewall mechanisms - such as\n SOCKS - that were designed specifically for unicast traffic, are less\n appropriate for m","scope_keywords":["2588","delivery","policy","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null}],"search_text":"IETF RFC 2588 Network Working Group R. Finlayson\nRequest for Comments: 2588 LIVE.COM\nCategory: Informational May 1999\n\n IP Multicast and Firewalls\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n Many organizations use a firewall computer that acts as a security\n gateway between the public Internet and their private, internal\n 'intranet'. In this document, we discuss the issues surrounding the\n traversal of IP multicast traffic across a firewall, and describe\n possible ways in which a firewall can implement and control this\n traversal. We also explain why some firewall mechanisms - such as\n SOCKS - that were designed specifically for unicast traffic, are less\n appropriate for m 2588 delivery policy signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2658","type":"specification","body":"IETF","designation":"RFC 2658","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2658.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2658.txt","https://www.rfc-editor.org/rfc/rfc2658.pdf"],"folder":"IETF/RFC-2658","files":{"txt":{"path":"standards/IETF/RFC-2658/RFC-2658.txt","sha256":"3048f9079fe6b6240d081b8ebab1535d052019d900f16c756166610407e81c6f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the RTP payload format for PureVoice(tm)\n Audio. The packet format supports variable interleaving to reduce\n the effect of packet loss on audio quality.\n\n1 Introduction\n\n This document describes how compressed PureVoice audio as produced by\n the Qualcomm PureVoice CODEC [1] may be formatted for use as an RTP\n payload type. A method is provided to interleave the output of the\n compressor to reduce quality degradation due to lost packets.\n Furthermore, the sender may choose various interleave settings based\n on the importance of low end-to-end delay versus greater tolerance\n for lost packets.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [3].\n\n2 Background\n\n The Electronic Industries Association (EIA) & Telecommunicat","scope_keywords":["2658","algorithm","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2658 This document describes the RTP payload format for PureVoice(tm)\n Audio. The packet format supports variable interleaving to reduce\n the effect of packet loss on audio quality.\n\n1 Introduction\n\n This document describes how compressed PureVoice audio as produced by\n the Qualcomm PureVoice CODEC [1] may be formatted for use as an RTP\n payload type. A method is provided to interleave the output of the\n compressor to reduce quality degradation due to lost packets.\n Furthermore, the sender may choose various interleave settings based\n on the importance of low end-to-end delay versus greater tolerance\n for lost packets.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [3].\n\n2 Background\n\n The Electronic Industries Association (EIA) & Telecommunicat 2658 algorithm key timestamp nested-reference unchanged"},{"id":"IETF RFC 2730","type":"specification","body":"IETF","designation":"RFC 2730","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2730.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2730.txt","https://www.rfc-editor.org/rfc/rfc2730.pdf"],"folder":"IETF/RFC-2730","files":{"txt":{"path":"standards/IETF/RFC-2730/RFC-2730.txt","sha256":"e7baf3d97adc1e866862d77ca33eefb49ffc664dcfd4843838ac8d082248a985"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a protocol, Multicast Address Dynamic Client\n Allocation Protocol (MADCAP), that allows hosts to request multicast\n addresses from multicast address allocation servers.\n\n1. Introduction\n\n Multicast Address Dynamic Client Allocation Protocol (MADCAP) is a\n protocol that allows hosts to request multicast address allocation\n services from multicast address allocation servers. This protocol is\n part of the Multicast Address Allocation Architecture being defined\n by the IETF Multicast Address Allocation Working Group. However, it\n may be used separately from the rest of that architecture as\n appropriate.","scope_keywords":["2730","authentication","key","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2770","folder":"IETF/RFC-2770","source":"IETF/RFC-2770/RFC-2770.txt","version":null},{"body":"IETF","designation":"RFC 2771","folder":"IETF/RFC-2771","source":"IETF/RFC-2771/RFC-2771.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2907","folder":"IETF/RFC-2907","source":"IETF/RFC-2907/RFC-2907.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null}],"search_text":"IETF RFC 2730 This document defines a protocol, Multicast Address Dynamic Client\n Allocation Protocol (MADCAP), that allows hosts to request multicast\n addresses from multicast address allocation servers.\n\n1. Introduction\n\n Multicast Address Dynamic Client Allocation Protocol (MADCAP) is a\n protocol that allows hosts to request multicast address allocation\n services from multicast address allocation servers. This protocol is\n part of the Multicast Address Allocation Architecture being defined\n by the IETF Multicast Address Allocation Working Group. However, it\n may be used separately from the rest of that architecture as\n appropriate. 2730 authentication key policies policy nested-reference unchanged"},{"id":"IETF RFC 2765","type":"specification","body":"IETF","designation":"RFC 2765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2765.txt","https://www.rfc-editor.org/rfc/rfc2765.pdf"],"folder":"IETF/RFC-2765","files":{"txt":{"path":"standards/IETF/RFC-2765/RFC-2765.txt","sha256":"a5c30eb6efacfca6a8b13365b35624d74201d047b9e0a2257157401be4ae5d0a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a transition mechanism algorithm in addition\n to the mechanisms already specified in [TRANS-MECH]. The algorithm\n translates between IPv4 and IPv6 packet headers (including ICMP\n headers) in separate translator \"boxes\" in the network without\n requiring any per-connection state in those \"boxes\". This new\n algorithm can be used as part of a solution that allows IPv6 hosts,\n which do not have a permanently assigned IPv4 addresses, to\n communicate with IPv4-only hosts. The document neither specifies\n address assignment nor routing to and from the IPv6 hosts when they\n communicate with the IPv4-only hosts.\n\nAcknowledgements\n\n This document is a product of the NGTRANS working group. Some text\n has been extracted from an old Internet Draft titled \"IPAE: The SIPP\n Interoperability and Transition Mechanism\" authored by R. Gilligan,\n E. Nordmark, and B. Hinden. George Tsirt","scope_keywords":["2765","algorithm","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null}],"search_text":"IETF RFC 2765 This document specifies a transition mechanism algorithm in addition\n to the mechanisms already specified in [TRANS-MECH]. The algorithm\n translates between IPv4 and IPv6 packet headers (including ICMP\n headers) in separate translator \"boxes\" in the network without\n requiring any per-connection state in those \"boxes\". This new\n algorithm can be used as part of a solution that allows IPv6 hosts,\n which do not have a permanently assigned IPv4 addresses, to\n communicate with IPv4-only hosts. The document neither specifies\n address assignment nor routing to and from the IPv6 hosts when they\n communicate with the IPv4-only hosts.\n\nAcknowledgements\n\n This document is a product of the NGTRANS working group. Some text\n has been extracted from an old Internet Draft titled \"IPAE: The SIPP\n Interoperability and Transition Mechanism\" authored by R. Gilligan,\n E. Nordmark, and B. Hinden. George Tsirt 2765 algorithm registered nested-reference unchanged"},{"id":"IETF RFC 2771","type":"specification","body":"IETF","designation":"RFC 2771","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2771.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2771.txt","https://www.rfc-editor.org/rfc/rfc2771.pdf"],"folder":"IETF/RFC-2771","files":{"txt":{"path":"standards/IETF/RFC-2771/RFC-2771.txt","sha256":"653f16fdf444246bc22ca6ac00f1270aa75159a74d3c483cc2cd7f0039d66a3d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"abstract service interface\" for the\n dynamic multicast address allocation service, as seen by\n applications. While it does not describe a concrete API (i.e., for a\n specific programming language), it describes - in abstract terms -\n the semantics of this service, including the guarantees that it makes\n to applications.\n\n Additional documents (not necessarily products of the IETF) would\n describe concrete APIs for this service.\n\n1. Introduction\n\n Applications are the customers of a multicast address allocation\n service, so a definition of this service should include not only the\n inter-node network protocols that are used to implement it, but also\n the 'protocol' that applications use to access the service. While\n APIs (\"application programming interfaces\") for specific programming\n languages (or operating systems) are outside the domain of the IETF,\n it is ap","scope_keywords":["2771"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null}],"search_text":"IETF RFC 2771 This document describes the \"abstract service interface\" for the\n dynamic multicast address allocation service, as seen by\n applications. While it does not describe a concrete API (i.e., for a\n specific programming language), it describes - in abstract terms -\n the semantics of this service, including the guarantees that it makes\n to applications.\n\n Additional documents (not necessarily products of the IETF) would\n describe concrete APIs for this service.\n\n1. Introduction\n\n Applications are the customers of a multicast address allocation\n service, so a definition of this service should include not only the\n inter-node network protocols that are used to implement it, but also\n the 'protocol' that applications use to access the service. While\n APIs (\"application programming interfaces\") for specific programming\n languages (or operating systems) are outside the domain of the IETF,\n it is ap 2771 nested-reference unchanged"},{"id":"IETF RFC 2908","type":"specification","body":"IETF","designation":"RFC 2908","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2908.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2908.txt","https://www.rfc-editor.org/rfc/rfc2908.pdf"],"folder":"IETF/RFC-2908","files":{"txt":{"path":"standards/IETF/RFC-2908/RFC-2908.txt","sha256":"3449bb54d1883dcf44489cdc0153b4fd43ffb1ec8caaad3ac9a1595ff2285b1a"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a multicast address allocation architecture\n (MALLOC) for the Internet. The architecture is modular with three\n layers, comprising a host-server mechanism, an intra-domain server-\n server coordination mechanism, and an inter-domain mechanism.","scope_keywords":["2908"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2907","folder":"IETF/RFC-2907","source":"IETF/RFC-2907/RFC-2907.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null}],"search_text":"IETF RFC 2908 This document proposes a multicast address allocation architecture\n (MALLOC) for the Internet. The architecture is modular with three\n layers, comprising a host-server mechanism, an intra-domain server-\n server coordination mechanism, and an inter-domain mechanism. 2908 nested-reference unchanged"},{"id":"IETF RFC 2909","type":"specification","body":"IETF","designation":"RFC 2909","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2909.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2909.txt","https://www.rfc-editor.org/rfc/rfc2909.pdf"],"folder":"IETF/RFC-2909","files":{"txt":{"path":"standards/IETF/RFC-2909/RFC-2909.txt","sha256":"114ca000e72298afa47290b6c155f0b63d1ab44941f434af62ba3626138868d3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Multicast Address-Set Claim (MASC)\n protocol which can be used for inter-domain multicast address set\n allocation. MASC is used by a node (typically a router) to claim and\n allocate one or more address prefixes to that node's domain. While a\n domain does not necessarily need to allocate an address set for hosts\n in that domain to be able to allocate group addresses, allocating an\n address set to the domain does ensure that inter-domain group-\n specific distribution trees will be locally-rooted, and that traffic\n will be sent outside the domain only when and where external\n receivers exist.\n\nRadoslavov, et al. Experimental [Page 1]\n\f\nRFC 2909 The MASC Protocol September 2000","scope_keywords":["2909"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2909 This document describes the Multicast Address-Set Claim (MASC)\n protocol which can be used for inter-domain multicast address set\n allocation. MASC is used by a node (typically a router) to claim and\n allocate one or more address prefixes to that node's domain. While a\n domain does not necessarily need to allocate an address set for hosts\n in that domain to be able to allocate group addresses, allocating an\n address set to the domain does ensure that inter-domain group-\n specific distribution trees will be locally-rooted, and that traffic\n will be sent outside the domain only when and where external\n receivers exist.\n\nRadoslavov, et al. Experimental [Page 1]\n\f\nRFC 2909 The MASC Protocol September 2000 2909 nested-reference unchanged"},{"id":"IETF RFC 3047","type":"specification","body":"IETF","designation":"RFC 3047","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3047.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3047.txt","https://www.rfc-editor.org/rfc/rfc3047.pdf"],"folder":"IETF/RFC-3047","files":{"txt":{"path":"standards/IETF/RFC-3047/RFC-3047.txt","sha256":"970ef98b994e437690ff9f9601b796d83c89090bd21f74de461af3eb9c097793"}},"tags":["nested-reference","unchanged"],"summary":"International Telecommunication Union (ITU-T) Recommendation G.722.1\n is a wide-band audio codec, which operates at one of two selectable\n bit rates, 24kbit/s or 32kbit/s. This document describes the payload\n format for including G.722.1 generated bit streams within an RTP\n packet. Also included here are the necessary details for the use of\n G.722.1 with MIME and SDP.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [6].\n\n2. Overview of ITU-T Recommendation G.722.1\n\n G.722.1 is a low complexity coder, it compresses 50Hz - 7kHz audio\n signals into one of two bit rates, 24 kbit/s or 32 kbit/s.\n\n The coder may be used for speech, music and other types of audio.\n\n Some of the applications for which this coder","scope_keywords":["3047","algorithm","key","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 3047 International Telecommunication Union (ITU-T) Recommendation G.722.1\n is a wide-band audio codec, which operates at one of two selectable\n bit rates, 24kbit/s or 32kbit/s. This document describes the payload\n format for including G.722.1 generated bit streams within an RTP\n packet. Also included here are the necessary details for the use of\n G.722.1 with MIME and SDP.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [6].\n\n2. Overview of ITU-T Recommendation G.722.1\n\n G.722.1 is a low complexity coder, it compresses 50Hz - 7kHz audio\n signals into one of two bit rates, 24 kbit/s or 32 kbit/s.\n\n The coder may be used for speech, music and other types of audio.\n\n Some of the applications for which this coder 3047 algorithm key profile timestamp nested-reference unchanged"},{"id":"IETF RFC 3170","type":"specification","body":"IETF","designation":"RFC 3170","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3170.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3170.txt","https://www.rfc-editor.org/rfc/rfc3170.pdf"],"folder":"IETF/RFC-3170","files":{"txt":{"path":"standards/IETF/RFC-3170/RFC-3170.txt","sha256":"824c77e07176845f0c315396b041b0b5fb4177472ec81fc1e84b275dc4c0dc62"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the challenges involved with designing and\n implementing multicast applications. It is an introductory guide for\n application developers that highlights the unique considerations of\n multicast applications as compared to unicast applications.\n\n To this end, the document presents a taxonomy of multicast\n application I/O models and examples of the services they can support.\n It then describes the service requirements of these multicast\n applications, and the recent and ongoing efforts to build protocol\n solutions to support these services.","scope_keywords":["3170","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null}],"search_text":"IETF RFC 3170 This document describes the challenges involved with designing and\n implementing multicast applications. It is an introductory guide for\n application developers that highlights the unique considerations of\n multicast applications as compared to unicast applications.\n\n To this end, the document presents a taxonomy of multicast\n application I/O models and examples of the services they can support.\n It then describes the service requirements of these multicast\n applications, and the recent and ongoing efforts to build protocol\n solutions to support these services. 3170 delivery management nested-reference unchanged"},{"id":"IETF RFC 3190","type":"specification","body":"IETF","designation":"RFC 3190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3190.txt","https://www.rfc-editor.org/rfc/rfc3190.pdf"],"folder":"IETF/RFC-3190","files":{"txt":{"path":"standards/IETF/RFC-3190/RFC-3190.txt","sha256":"ba737fcb205a1dfd23cb1906a2cff88d36bb01faa7f61f8a8bbd7e567a35f9f8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a packetization scheme for encapsulating\n 12-bit nonlinear, 20-bit linear, and 24-bit linear audio data streams\n using the Real-time Transport Protocol (RTP). This document also\n specifies the format of a Session Description Protocol (SDP)\n parameter to indicate when audio data is preemphasized before\n sampling. The parameter may be used with other audio payload\n formats, in particular L16 (16-bit linear).\n\n1. Introduction\n\n This document describes the sampling of audio data in 12-bit\n nonlinear, 20-bit linear, and 24-bit linear encodings, and specifies\n the encapsulation of the audio data into the Real-time Transport\n Protocol (RTP), version 2 [1,2]. DAT (digital audio tape) and DV\n (digital video) devices [3,4] use these audio encodings in addition\n to 16-bit linear encoding. The packetization scheme for 16-bit\n linear audio (L16) is already specified [2,5]. Thi","scope_keywords":["3190","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null}],"search_text":"IETF RFC 3190 This document specifies a packetization scheme for encapsulating\n 12-bit nonlinear, 20-bit linear, and 24-bit linear audio data streams\n using the Real-time Transport Protocol (RTP). This document also\n specifies the format of a Session Description Protocol (SDP)\n parameter to indicate when audio data is preemphasized before\n sampling. The parameter may be used with other audio payload\n formats, in particular L16 (16-bit linear).\n\n1. Introduction\n\n This document describes the sampling of audio data in 12-bit\n nonlinear, 20-bit linear, and 24-bit linear encodings, and specifies\n the encapsulation of the audio data into the Real-time Transport\n Protocol (RTP), version 2 [1,2]. DAT (digital audio tape) and DV\n (digital video) devices [3,4] use these audio encodings in addition\n to 16-bit linear encoding. The packetization scheme for 16-bit\n linear audio (L16) is already specified [2,5]. Thi 3190 key profile nested-reference unchanged"},{"id":"IETF RFC 3208","type":"specification","body":"IETF","designation":"RFC 3208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3208.txt","https://www.rfc-editor.org/rfc/rfc3208.pdf"],"folder":"IETF/RFC-3208","files":{"txt":{"path":"standards/IETF/RFC-3208/RFC-3208.txt","sha256":"21dd53c1db57504e300773d46a9e69e4b2c54062a5490a209712d8353f11a5ff"}},"tags":["nested-reference","unchanged"],"summary":"Pragmatic General Multicast (PGM) is a reliable multicast transport\n protocol for applications that require ordered or unordered,\n duplicate-free, multicast data delivery from multiple sources to\n multiple receivers. PGM guarantees that a receiver in the group\n either receives all data packets from transmissions and repairs, or\n is able to detect unrecoverable data packet loss. PGM is\n\nSpeakman, et. al. Experimental [Page 1]\n\f\nRFC 3208 PGM Reliable Transport Protocol December 2001\n\n specifically intended as a workable solution for multicast\n applications with basic reliability requirements. Its central design\n goal is simplicity of operation with due regard for scalability and\n network efficiency.","scope_keywords":["3208","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 3208 Pragmatic General Multicast (PGM) is a reliable multicast transport\n protocol for applications that require ordered or unordered,\n duplicate-free, multicast data delivery from multiple sources to\n multiple receivers. PGM guarantees that a receiver in the group\n either receives all data packets from transmissions and repairs, or\n is able to detect unrecoverable data packet loss. PGM is\n\nSpeakman, et. al. Experimental [Page 1]\n\f\nRFC 3208 PGM Reliable Transport Protocol December 2001\n\n specifically intended as a workable solution for multicast\n applications with basic reliability requirements. Its central design\n goal is simplicity of operation with due regard for scalability and\n network efficiency. 3208 delivery nested-reference unchanged"},{"id":"IETF RFC 3220","type":"specification","body":"IETF","designation":"RFC 3220","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3220.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3220.txt","https://www.rfc-editor.org/rfc/rfc3220.pdf"],"folder":"IETF/RFC-3220","files":{"txt":{"path":"standards/IETF/RFC-3220/RFC-3220.txt","sha256":"f5c5b35182e08c8d152d161ae7ec3dad22d1a39c8771a798f2693532245f5dee"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nContents\n\n 1. Introduction 3\n 1.1. Protocol Requirements . . . . . . . . . . . . . . . . . 4\n 1.2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 1.3. Assumptions . . . . . . . . . . ","scope_keywords":["3220","authentication","key","management","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3220 This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nContents\n\n 1. Introduction 3\n 1.1. Protocol Requirements . . . . . . . . . . . . . . . . . 4\n 1.2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 1.3. Assumptions . . . . . . . . . .  3220 authentication key management timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3344","type":"specification","body":"IETF","designation":"RFC 3344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3344.txt","https://www.rfc-editor.org/rfc/rfc3344.pdf"],"folder":"IETF/RFC-3344","files":{"txt":{"path":"standards/IETF/RFC-3344/RFC-3344.txt","sha256":"628fd7ccdc5eb97a093b38a224050a39d9dfc5e55ed8d19dac1c5b426e8f1b6d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nContents\n\n 1. Introduction 3\n 1.1. Protocol Requirements . . . . . . . . . . . . . . . . . 4\n 1.2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 1.3. Assumptions . . . . . . . . . . ","scope_keywords":["3344","authentication","key","management","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3583","folder":"IETF/RFC-3583","source":"IETF/RFC-3583/RFC-3583.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4636","folder":"IETF/RFC-4636","source":"IETF/RFC-4636/RFC-4636.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3344 This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nContents\n\n 1. Introduction 3\n 1.1. Protocol Requirements . . . . . . . . . . . . . . . . . 4\n 1.2. Goals . . . . . . . . . . . . . . . . . . . . . . . . . 4\n 1.3. Assumptions . . . . . . . . . .  3344 authentication key management timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3450","type":"specification","body":"IETF","designation":"RFC 3450","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3450.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3450.txt","https://www.rfc-editor.org/rfc/rfc3450.pdf"],"folder":"IETF/RFC-3450","files":{"txt":{"path":"standards/IETF/RFC-3450/RFC-3450.txt","sha256":"89242a14a3809ddd4d34a02d7271a65cf3644366edd911d68bb030b636e203c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Asynchronous Layered Coding (ALC)\n protocol, a massively scalable reliable content delivery protocol.\n Asynchronous Layered Coding combines the Layered Coding Transport\n (LCT) building block, a multiple rate congestion control building\n block and the Forward Error Correction (FEC) building block to\n provide congestion controlled reliable asynchronous delivery of\n content to an unlimited number of concurrent receivers from a single\n sender.","scope_keywords":["3450","authentication","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 3450 This document describes the Asynchronous Layered Coding (ALC)\n protocol, a massively scalable reliable content delivery protocol.\n Asynchronous Layered Coding combines the Layered Coding Transport\n (LCT) building block, a multiple rate congestion control building\n block and the Forward Error Correction (FEC) building block to\n provide congestion controlled reliable asynchronous delivery of\n content to an unlimited number of concurrent receivers from a single\n sender. 3450 authentication delivery key nested-reference unchanged"},{"id":"IETF RFC 3451","type":"specification","body":"IETF","designation":"RFC 3451","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3451.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3451.txt","https://www.rfc-editor.org/rfc/rfc3451.pdf"],"folder":"IETF/RFC-3451","files":{"txt":{"path":"standards/IETF/RFC-3451/RFC-3451.txt","sha256":"bc382c254ca2c0873fb5d105ed3dd65a21c71bcc5e7dd2da559f070d8aff6754"}},"tags":["nested-reference","unchanged"],"summary":"Layered Coding Transport (LCT) provides transport level support for\n reliable content delivery and stream delivery protocols. LCT is\n specifically designed to support protocols using IP multicast, but\n also provides support to protocols that use unicast. LCT is\n compatible with congestion control that provides multiple rate\n delivery to receivers and is also compatible with coding techniques\n that provide reliable delivery of content.\n\nLuby, et. al. Experimental [Page 1]\n\f\nRFC 3451 LCT Building Block December 2002","scope_keywords":["3451","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 3451 Layered Coding Transport (LCT) provides transport level support for\n reliable content delivery and stream delivery protocols. LCT is\n specifically designed to support protocols using IP multicast, but\n also provides support to protocols that use unicast. LCT is\n compatible with congestion control that provides multiple rate\n delivery to receivers and is also compatible with coding techniques\n that provide reliable delivery of content.\n\nLuby, et. al. Experimental [Page 1]\n\f\nRFC 3451 LCT Building Block December 2002 3451 delivery key nested-reference unchanged"},{"id":"IETF RFC 3569","type":"specification","body":"IETF","designation":"RFC 3569","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3569.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3569.txt","https://www.rfc-editor.org/rfc/rfc3569.pdf"],"folder":"IETF/RFC-3569","files":{"txt":{"path":"standards/IETF/RFC-3569/RFC-3569.txt","sha256":"8e2fa6fa34cf1c796e3b17faabcb63e68f8498d9ca7373de76ef906532c1cdb3"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to provide an overview of\n Source-Specific Multicast (SSM) and issues related to its deployment.\n It discusses how the SSM service model addresses the challenges faced\n in inter-domain multicast deployment, changes needed to routing\n protocols and applications to deploy SSM and interoperability issues\n with current multicast service models.\n\n1. Introduction\n\n This document provides an overview of the Source-Specific Multicast\n (SSM) service and its deployment using the PIM-SM and IGMP/MLD\n protocols. The network layer service provided by SSM is a \"channel\",\n identified by an SSM destination IP address (G) and a source IP\n address S. An IPv4 address range has been reserved by IANA for use\n by the SSM service. An SSM destination address range already exists\n for IPv6. A source S transmits IP datagrams to an SSM destination\n address G. A receiver can receive ","scope_keywords":["3569","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4608","folder":"IETF/RFC-4608","source":"IETF/RFC-4608/RFC-4608.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 3569 The purpose of this document is to provide an overview of\n Source-Specific Multicast (SSM) and issues related to its deployment.\n It discusses how the SSM service model addresses the challenges faced\n in inter-domain multicast deployment, changes needed to routing\n protocols and applications to deploy SSM and interoperability issues\n with current multicast service models.\n\n1. Introduction\n\n This document provides an overview of the Source-Specific Multicast\n (SSM) service and its deployment using the PIM-SM and IGMP/MLD\n protocols. The network layer service provided by SSM is a \"channel\",\n identified by an SSM destination IP address (G) and a source IP\n address S. An IPv4 address range has been reserved by IANA for use\n by the SSM service. An SSM destination address range already exists\n for IPv6. A source S transmits IP datagrams to an SSM destination\n address G. A receiver can receive  3569 key management path nested-reference unchanged"},{"id":"IETF RFC 3738","type":"specification","body":"IETF","designation":"RFC 3738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3738.txt","https://www.rfc-editor.org/rfc/rfc3738.pdf"],"folder":"IETF/RFC-3738","files":{"txt":{"path":"standards/IETF/RFC-3738/RFC-3738.txt","sha256":"4c7e94f48f1783580673f7a2a4a896db7ee372b955131286b44ba41011b504bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Wave and Equation Based Rate Control (WEBRC),\n which provides rate and congestion control for data delivery. WEBRC\n is specifically designed to support protocols using IP multicast. It\n provides multiple-rate, congestion-controlled delivery to receivers,\n i.e., different receivers joined to the same session may be receiving\n packets at different rates depending on the bandwidths of their\n individual connections to the sender and on competing traffic along\n these connections. WEBRC requires no feedback from receivers to the\n sender, i.e., it is a completely receiver-driven congestion control\n protocol. Thus, it is designed to scale to potentially massive\n numbers of receivers attached to a session from a single sender.\n Furthermore, because each individual receiver adjusts to the\n available bandwidth between the sender and that receiver, there is\n the potential to ","scope_keywords":["3738","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 3738 This document specifies Wave and Equation Based Rate Control (WEBRC),\n which provides rate and congestion control for data delivery. WEBRC\n is specifically designed to support protocols using IP multicast. It\n provides multiple-rate, congestion-controlled delivery to receivers,\n i.e., different receivers joined to the same session may be receiving\n packets at different rates depending on the bandwidths of their\n individual connections to the sender and on competing traffic along\n these connections. WEBRC requires no feedback from receivers to the\n sender, i.e., it is a completely receiver-driven congestion control\n protocol. Thus, it is designed to scale to potentially massive\n numbers of receivers attached to a session from a single sender.\n Furthermore, because each individual receiver adjusts to the\n available bandwidth between the sender and that receiver, there is\n the potential to  3738 delivery nested-reference unchanged"},{"id":"IETF RFC 3918","type":"specification","body":"IETF","designation":"RFC 3918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3918.txt","https://www.rfc-editor.org/rfc/rfc3918.pdf"],"folder":"IETF/RFC-3918","files":{"txt":{"path":"standards/IETF/RFC-3918/RFC-3918.txt","sha256":"3ab9aaf36154b02ff5268b4a2f54c5666ba25fef7b2e0632a2958e3820eedd1c"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to describe methodology specific to\n the benchmarking of multicast IP forwarding devices. It builds upon\n the tenets set forth in RFC 2544, RFC 2432 and other IETF\n Benchmarking Methodology Working Group (BMWG) efforts. This document\n seeks to extend these efforts to the multicast paradigm.\n\n The BMWG produces two major classes of documents: Benchmarking\n Terminology documents and Benchmarking Methodology documents. The\n Terminology documents present the benchmarks and other related terms.\n The Methodology documents define the procedures required to collect\n the benchmarks cited in the corresponding Terminology documents.","scope_keywords":["3918","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null}],"search_text":"IETF RFC 3918 The purpose of this document is to describe methodology specific to\n the benchmarking of multicast IP forwarding devices. It builds upon\n the tenets set forth in RFC 2544, RFC 2432 and other IETF\n Benchmarking Methodology Working Group (BMWG) efforts. This document\n seeks to extend these efforts to the multicast paradigm.\n\n The BMWG produces two major classes of documents: Benchmarking\n Terminology documents and Benchmarking Methodology documents. The\n Terminology documents present the benchmarks and other related terms.\n The Methodology documents define the procedures required to collect\n the benchmarks cited in the corresponding Terminology documents. 3918 key management nested-reference unchanged"},{"id":"IETF RFC 3926","type":"specification","body":"IETF","designation":"RFC 3926","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3926.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3926.txt","https://www.rfc-editor.org/rfc/rfc3926.pdf"],"folder":"IETF/RFC-3926","files":{"txt":{"path":"standards/IETF/RFC-3926/RFC-3926.txt","sha256":"7ac412dbc64d8c3c2914b2880ac97a15b2677aab715f4b9b0e38981fd4e5add7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines FLUTE, a protocol for the unidirectional\n delivery of files over the Internet, which is particularly suited to\n multicast networks. The specification builds on Asynchronous Layered\n Coding, the base protocol designed for massively scalable multicast\n distribution.","scope_keywords":["3926","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 3926 This document defines FLUTE, a protocol for the unidirectional\n delivery of files over the Internet, which is particularly suited to\n multicast networks. The specification builds on Asynchronous Layered\n Coding, the base protocol designed for massively scalable multicast\n distribution. 3926 delivery nested-reference unchanged"},{"id":"IETF RFC 3940","type":"specification","body":"IETF","designation":"RFC 3940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3940.txt","https://www.rfc-editor.org/rfc/rfc3940.pdf"],"folder":"IETF/RFC-3940","files":{"txt":{"path":"standards/IETF/RFC-3940/RFC-3940.txt","sha256":"ab9db957f58b97f9996aecaa784d9097aacb238b7458f47e8036ec5ed59f0f00"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the messages and procedures of the Negative-\n acknowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.\n This protocol is designed to provide end-to-end reliable transport of\n bulk data objects or streams over generic IP multicast routing and\n forwarding services. NORM uses a selective, negative acknowledgment\n mechanism for transport reliability and offers additional protocol\n mechanisms to allow for operation with minimal \"a priori\"\n coordination among senders and receivers. A congestion control\n scheme is specified to allow the NORM protocol to fairly share\n available network bandwidth with other transport protocols such as\n Transmission Control Protocol (TCP). It is capable of operating with\n both reciprocal multicast routing among senders and receivers and\n with asymmetric connectivity (possibly a unicast return path) between\n the senders and receive","scope_keywords":["3940","algorithm","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null}],"search_text":"IETF RFC 3940 This document describes the messages and procedures of the Negative-\n acknowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.\n This protocol is designed to provide end-to-end reliable transport of\n bulk data objects or streams over generic IP multicast routing and\n forwarding services. NORM uses a selective, negative acknowledgment\n mechanism for transport reliability and offers additional protocol\n mechanisms to allow for operation with minimal \"a priori\"\n coordination among senders and receivers. A congestion control\n scheme is specified to allow the NORM protocol to fairly share\n available network bandwidth with other transport protocols such as\n Transmission Control Protocol (TCP). It is capable of operating with\n both reciprocal multicast routing among senders and receivers and\n with asymmetric connectivity (possibly a unicast return path) between\n the senders and receive 3940 algorithm delivery key path nested-reference unchanged"},{"id":"IETF RFC 3941","type":"specification","body":"IETF","designation":"RFC 3941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3941.txt","https://www.rfc-editor.org/rfc/rfc3941.pdf"],"folder":"IETF/RFC-3941","files":{"txt":{"path":"standards/IETF/RFC-3941/RFC-3941.txt","sha256":"d80a2a645738c235f49f1a55c7968bad6a8c934719f8b412ae2751d5c8246529"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the creation of negative-acknowledgment\n (NACK)-oriented reliable multicast (NORM) protocols. The rationale\n for NORM goals and assumptions are presented. Technical challenges\n for NACK-oriented (and in some cases general) reliable multicast\n protocol operation are identified. These goals and challenges are\n resolved into a set of functional \"building blocks\" that address\n different aspects of NORM protocol operation. It is anticipated that\n these building blocks will be useful in generating different\n instantiations of reliable multicast protocols.\n\nAdamson, et al. Experimental [Page 1]\n\f\nRFC 3941 NORM Building Blocks November 2004","scope_keywords":["3941","delivery","driving","identification","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null}],"search_text":"IETF RFC 3941 This document discusses the creation of negative-acknowledgment\n (NACK)-oriented reliable multicast (NORM) protocols. The rationale\n for NORM goals and assumptions are presented. Technical challenges\n for NACK-oriented (and in some cases general) reliable multicast\n protocol operation are identified. These goals and challenges are\n resolved into a set of functional \"building blocks\" that address\n different aspects of NORM protocol operation. It is anticipated that\n these building blocks will be useful in generating different\n instantiations of reliable multicast protocols.\n\nAdamson, et al. Experimental [Page 1]\n\f\nRFC 3941 NORM Building Blocks November 2004 3941 delivery driving identification key policies nested-reference unchanged"},{"id":"IETF RFC 4045","type":"specification","body":"IETF","designation":"RFC 4045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4045.txt","https://www.rfc-editor.org/rfc/rfc4045.pdf"],"folder":"IETF/RFC-4045","files":{"txt":{"path":"standards/IETF/RFC-4045/RFC-4045.txt","sha256":"ef82244545a76ada8cabb3c3bb24942ee4ae42aaa4fea9067e0efa2f02411b58"}},"tags":["nested-reference","unchanged"],"summary":"The Layer Two Tunneling Protocol (L2TP) provides a method for\n tunneling PPP packets. This document describes an extension to L2TP,\n to make efficient use of L2TP tunnels within the context of deploying\n multicast services whose data will have to be conveyed by these\n tunnels.","scope_keywords":["4045","attribute","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null}],"search_text":"IETF RFC 4045 The Layer Two Tunneling Protocol (L2TP) provides a method for\n tunneling PPP packets. This document describes an extension to L2TP,\n to make efficient use of L2TP tunnels within the context of deploying\n multicast services whose data will have to be conveyed by these\n tunnels. 4045 attribute key management nested-reference unchanged"},{"id":"IETF RFC 4286","type":"specification","body":"IETF","designation":"RFC 4286","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4286.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4286.txt","https://www.rfc-editor.org/rfc/rfc4286.pdf"],"folder":"IETF/RFC-4286","files":{"txt":{"path":"standards/IETF/RFC-4286/RFC-4286.txt","sha256":"2885570c13791d3305ecbd05fc846db5d9e8132f0412c74ab24f98cc34093581"}},"tags":["nested-reference","unchanged"],"summary":"The concept of Internet Group Management Protocol (IGMP) and\n Multicast Listener Discovery (MLD) snooping requires the ability to\n identify the location of multicast routers. Since snooping is not\n standardized, there are many mechanisms in use to identify the\n multicast routers. However, this can lead to interoperability issues\n between multicast routers and snooping switches from different\n vendors.\n\n This document introduces a general mechanism that allows for the\n discovery of multicast routers. This new mechanism, Multicast Router\n Discovery (MRD), introduces a standardized means of identifying\n multicast routers without a dependency on particular multicast\n routing protocols.\n\nHaberman, et al. Standards Track [Page 1]\n\f\nRFC 4286 Multicast Router Discovery December 2005","scope_keywords":["4286","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null}],"search_text":"IETF RFC 4286 The concept of Internet Group Management Protocol (IGMP) and\n Multicast Listener Discovery (MLD) snooping requires the ability to\n identify the location of multicast routers. Since snooping is not\n standardized, there are many mechanisms in use to identify the\n multicast routers. However, this can lead to interoperability issues\n between multicast routers and snooping switches from different\n vendors.\n\n This document introduces a general mechanism that allows for the\n discovery of multicast routers. This new mechanism, Multicast Router\n Discovery (MRD), introduces a standardized means of identifying\n multicast routers without a dependency on particular multicast\n routing protocols.\n\nHaberman, et al. Standards Track [Page 1]\n\f\nRFC 4286 Multicast Router Discovery December 2005 4286 key management nested-reference unchanged"},{"id":"IETF RFC 4391","type":"specification","body":"IETF","designation":"RFC 4391","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4391.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4391.txt","https://www.rfc-editor.org/rfc/rfc4391.pdf"],"folder":"IETF/RFC-4391","files":{"txt":{"path":"standards/IETF/RFC-4391/RFC-4391.txt","sha256":"5dc18802b9b793cfd17b7f106f5ae0d9ba6c0dbe35bac5d3904ff68dfa5a66e5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for encapsulating and transmitting\n IPv4/IPv6 and Address Resolution Protocol (ARP) packets over\n InfiniBand (IB). It describes the link-layer address to be used when\n resolving the IP addresses in IP over InfiniBand (IPoIB) subnets.\n The document also describes the mapping from IP multicast addresses\n to InfiniBand multicast addresses. In addition, this document\n defines the setup and configuration of IPoIB links.","scope_keywords":["4391","attribute","attributes","http","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 4391 This document specifies a method for encapsulating and transmitting\n IPv4/IPv6 and Address Resolution Protocol (ARP) packets over\n InfiniBand (IB). It describes the link-layer address to be used when\n resolving the IP addresses in IP over InfiniBand (IPoIB) subnets.\n The document also describes the mapping from IP multicast addresses\n to InfiniBand multicast addresses. In addition, this document\n defines the setup and configuration of IPoIB links. 4391 attribute attributes http key signature nested-reference unchanged"},{"id":"IETF RFC 4392","type":"specification","body":"IETF","designation":"RFC 4392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4392.txt","https://www.rfc-editor.org/rfc/rfc4392.pdf"],"folder":"IETF/RFC-4392","files":{"txt":{"path":"standards/IETF/RFC-4392/RFC-4392.txt","sha256":"38965baedf4d4f71214f5db99e1ca53d127c465f8d4e505a754c9ec28c313407"}},"tags":["nested-reference","unchanged"],"summary":"InfiniBand is a high-speed, channel-based interconnect between\n systems and devices.\n\n This document presents an overview of the InfiniBand architecture.\n It further describes the requirements and guidelines for the\n transmission of IP over InfiniBand. Discussions in this document are\n applicable to both IPv4 and IPv6 unless explicitly specified. The\n encapsulation of IP over InfiniBand and the mechanism for IP address\n resolution on IB fabrics are covered in other documents.","scope_keywords":["4392","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null}],"search_text":"IETF RFC 4392 InfiniBand is a high-speed, channel-based interconnect between\n systems and devices.\n\n This document presents an overview of the InfiniBand architecture.\n It further describes the requirements and guidelines for the\n transmission of IP over InfiniBand. Discussions in this document are\n applicable to both IPv4 and IPv6 unless explicitly specified. The\n encapsulation of IP over InfiniBand and the mechanism for IP address\n resolution on IB fabrics are covered in other documents. 4392 http management nested-reference unchanged"},{"id":"IETF RFC 4570","type":"specification","body":"IETF","designation":"RFC 4570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4570.txt","https://www.rfc-editor.org/rfc/rfc4570.pdf"],"folder":"IETF/RFC-4570","files":{"txt":{"path":"standards/IETF/RFC-4570/RFC-4570.txt","sha256":"87b8a92598198fe53ff938d0f1869bebd51a1194b3ba69525d0005380bb0f1e5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to adapt the Session Description Protocol\n (SDP) to express one or more source addresses as a source filter for\n one or more destination \"connection\" addresses. It defines the\n syntax and semantics for an SDP \"source-filter\" attribute that may\n reference either IPv4 or IPv6 address(es) as either an inclusive or\n exclusive source list for either multicast or unicast destinations.\n In particular, an inclusive source-filter can be used to specify a\n Source-Specific Multicast (SSM) session.\n\n1. Introduction\n\n The Session Description Protocol [SDP] provides a general purpose\n format for describing multimedia sessions in announcements or\n invitations. SDP uses an entirely textual data format (the US-ASCII\n subset of [UTF-8]) to maximize portability among transports. SDP\n does not define a protocol, but only the syntax to describe a\n multimedia session with sufficien","scope_keywords":["4570","attribute","http","key","management","qualified","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4570 This document describes how to adapt the Session Description Protocol\n (SDP) to express one or more source addresses as a source filter for\n one or more destination \"connection\" addresses. It defines the\n syntax and semantics for an SDP \"source-filter\" attribute that may\n reference either IPv4 or IPv6 address(es) as either an inclusive or\n exclusive source list for either multicast or unicast destinations.\n In particular, an inclusive source-filter can be used to specify a\n Source-Specific Multicast (SSM) session.\n\n1. Introduction\n\n The Session Description Protocol [SDP] provides a general purpose\n format for describing multimedia sessions in announcements or\n invitations. SDP uses an entirely textual data format (the US-ASCII\n subset of [UTF-8]) to maximize portability among transports. SDP\n does not define a protocol, but only the syntax to describe a\n multimedia session with sufficien 4570 attribute http key management qualified tsp nested-reference unchanged"},{"id":"IETF RFC 4601","type":"specification","body":"IETF","designation":"RFC 4601","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4601.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4601.txt","https://www.rfc-editor.org/rfc/rfc4601.pdf"],"folder":"IETF/RFC-4601","files":{"pdf":{"path":"standards/IETF/RFC-4601/RFC-4601.pdf","sha256":"e5dc237cf92db8cc423c9d461ea3fe32fb5e756cd8bb3d9e3b20e94ce40b0226"},"txt":{"path":"standards/IETF/RFC-4601/RFC-4601.txt","sha256":"7791373978dd20ca9f27fed89365560f2f4afcfb12e905a2ef10415cdb625298"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Protocol Independent Multicast - Sparse Mode\n (PIM-SM). PIM-SM is a multicast routing protocol that can use the\n underlying unicast routing information base or a separate multicast-\n capable routing information base. It builds unidirectional shared\n trees rooted at a Rendezvous Point (RP) per group, and optionally\n creates shortest-path trees per source.\n\n This document obsoletes RFC 2362, an Experimental version of PIM-SM.\n\nFenner, et al. Standards Track [Page 1]\n\f\nRFC 4601 PIM-SM Specification August 2006","scope_keywords":["4601","authentication","hash","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4608","folder":"IETF/RFC-4608","source":"IETF/RFC-4608/RFC-4608.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4610","folder":"IETF/RFC-4610","source":"IETF/RFC-4610/RFC-4610.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5384","folder":"IETF/RFC-5384","source":"IETF/RFC-5384/RFC-5384.txt","version":null},{"body":"IETF","designation":"RFC 5496","folder":"IETF/RFC-5496","source":"IETF/RFC-5496/RFC-5496.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6807","folder":"IETF/RFC-6807","source":"IETF/RFC-6807/RFC-6807.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 4601 This document specifies Protocol Independent Multicast - Sparse Mode\n (PIM-SM). PIM-SM is a multicast routing protocol that can use the\n underlying unicast routing information base or a separate multicast-\n capable routing information base. It builds unidirectional shared\n trees rooted at a Rendezvous Point (RP) per group, and optionally\n creates shortest-path trees per source.\n\n This document obsoletes RFC 2362, an Experimental version of PIM-SM.\n\nFenner, et al. Standards Track [Page 1]\n\f\nRFC 4601 PIM-SM Specification August 2006 4601 authentication hash path nested-reference unchanged"},{"id":"IETF RFC 4604","type":"specification","body":"IETF","designation":"RFC 4604","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4604.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4604.txt","https://www.rfc-editor.org/rfc/rfc4604.pdf"],"folder":"IETF/RFC-4604","files":{"txt":{"path":"standards/IETF/RFC-4604/RFC-4604.txt","sha256":"12dd51c374945f9ac2084e33aee498e2a46a9b68888dcfcd65e6f1f0c26be463"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Group Management Protocol Version 3 (IGMPv3) and the\n Multicast Listener Discovery Protocol Version 2 (MLDv2) are protocols\n that allow a host to inform its neighboring routers of its desire to\n receive IPv4 and IPv6 multicast transmissions, respectively.\n Source-specific multicast (SSM) is a form of multicast in which a\n receiver is required to specify both the network-layer address of the\n source and the multicast destination address in order to receive the\n multicast transmission. This document defines the notion of an\n \"SSM-aware\" router and host, and clarifies and (in some cases)\n modifies the behavior of IGMPv3 and MLDv2 on SSM-aware routers and\n hosts to accommodate source-specific multicast. This document\n updates the IGMPv3 and MLDv2 specifications.\n\nHolbrook, et al. Standards Track [Page 1]\n\f\nRFC 4604 IGMPv3/MLDv2 for SSM August 2006\n\n1. Introduction\n\n The Internet","scope_keywords":["4604","delivery","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null}],"search_text":"IETF RFC 4604 The Internet Group Management Protocol Version 3 (IGMPv3) and the\n Multicast Listener Discovery Protocol Version 2 (MLDv2) are protocols\n that allow a host to inform its neighboring routers of its desire to\n receive IPv4 and IPv6 multicast transmissions, respectively.\n Source-specific multicast (SSM) is a form of multicast in which a\n receiver is required to specify both the network-layer address of the\n source and the multicast destination address in order to receive the\n multicast transmission. This document defines the notion of an\n \"SSM-aware\" router and host, and clarifies and (in some cases)\n modifies the behavior of IGMPv3 and MLDv2 on SSM-aware routers and\n hosts to accommodate source-specific multicast. This document\n updates the IGMPv3 and MLDv2 specifications.\n\nHolbrook, et al. Standards Track [Page 1]\n\f\nRFC 4604 IGMPv3/MLDv2 for SSM August 2006\n\n1. Introduction\n\n The Internet 4604 delivery key management nested-reference unchanged"},{"id":"IETF RFC 4605","type":"specification","body":"IETF","designation":"RFC 4605","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4605.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4605.txt","https://www.rfc-editor.org/rfc/rfc4605.pdf"],"folder":"IETF/RFC-4605","files":{"txt":{"path":"standards/IETF/RFC-4605/RFC-4605.txt","sha256":"51701bc3131bbc563ca821d0b6fef85c627e7aa044aadae3edd543f19f499678"}},"tags":["nested-reference","unchanged"],"summary":"In certain topologies, it is not necessary to run a multicast routing\n protocol. It is sufficient for a device to learn and proxy group\n membership information and simply forward multicast packets based\n upon that information. This document describes a mechanism for\n forwarding based solely upon Internet Group Management Protocol\n (IGMP) or Multicast Listener Discovery (MLD) membership information.\n\n1. Introduction\n\n This document applies spanning tree multicast routing [MCAST] to an\n Internet Group Management Protocol (IGMP) or Multicast Listener\n Discovery (MLD)-only environment. The topology is limited to a tree,\n since we specify no protocol to build a spanning tree over a more\n complex topology. The root of the tree is assumed to be connected to\n a wider multicast infrastructure.\n\nFenner, et al. Standards Track [Page 1]\n\f\nRFC 4605 IGMP/MLD-Based Multicast Forwarding August 2006","scope_keywords":["4605","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 4605 In certain topologies, it is not necessary to run a multicast routing\n protocol. It is sufficient for a device to learn and proxy group\n membership information and simply forward multicast packets based\n upon that information. This document describes a mechanism for\n forwarding based solely upon Internet Group Management Protocol\n (IGMP) or Multicast Listener Discovery (MLD) membership information.\n\n1. Introduction\n\n This document applies spanning tree multicast routing [MCAST] to an\n Internet Group Management Protocol (IGMP) or Multicast Listener\n Discovery (MLD)-only environment. The topology is limited to a tree,\n since we specify no protocol to build a spanning tree over a more\n complex topology. The root of the tree is assumed to be connected to\n a wider multicast infrastructure.\n\nFenner, et al. Standards Track [Page 1]\n\f\nRFC 4605 IGMP/MLD-Based Multicast Forwarding August 2006 4605 key management nested-reference unchanged"},{"id":"IETF RFC 4609","type":"specification","body":"IETF","designation":"RFC 4609","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4609.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4609.txt","https://www.rfc-editor.org/rfc/rfc4609.pdf"],"folder":"IETF/RFC-4609","files":{"txt":{"path":"standards/IETF/RFC-4609/RFC-4609.txt","sha256":"cced797bacddd994d14e4b847aa81e4ba70ab55128e600b4131e236709268a01"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes security threats for the larger (intra-domain or\n inter-domain) multicast routing infrastructures. Only Protocol\n Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its\n three main operational modes: the traditional Any-Source Multicast\n (ASM) model, the source-specific multicast (SSM) model, and the ASM\n model enhanced by the Embedded Rendezvous Point (Embedded-RP)\n group-to-RP mapping mechanism. This memo also describes enhancements\n to the protocol operations that mitigate the identified threats.\n\nSavola, et al. Informational [Page 1]\n\f\nRFC 4609 PIM-SM Multicast Routing Security August 2006","scope_keywords":["4609","authentication","delivery","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 4609 This memo describes security threats for the larger (intra-domain or\n inter-domain) multicast routing infrastructures. Only Protocol\n Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its\n three main operational modes: the traditional Any-Source Multicast\n (ASM) model, the source-specific multicast (SSM) model, and the ASM\n model enhanced by the Embedded Rendezvous Point (Embedded-RP)\n group-to-RP mapping mechanism. This memo also describes enhancements\n to the protocol operations that mitigate the identified threats.\n\nSavola, et al. Informational [Page 1]\n\f\nRFC 4609 PIM-SM Multicast Routing Security August 2006 4609 authentication delivery management path trust nested-reference unchanged"},{"id":"IETF RFC 4654","type":"specification","body":"IETF","designation":"RFC 4654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4654.txt","https://www.rfc-editor.org/rfc/rfc4654.pdf"],"folder":"IETF/RFC-4654","files":{"txt":{"path":"standards/IETF/RFC-4654/RFC-4654.txt","sha256":"ad4a30af5b471693b9bda051b0da280a92dbd38c7c2a682e20005d0cb4045450"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies TCP-Friendly Multicast Congestion Control\n (TFMCC). TFMCC is a congestion control mechanism for multicast\n transmissions in a best-effort Internet environment. It is a\n single-rate congestion control scheme, where the sending rate is\n adapted to the receiver experiencing the worst network conditions.\n TFMCC is reasonably fair when competing for bandwidth with TCP flows\n and has a relatively low variation of throughput over time, making it\n suitable for applications where a relatively smooth sending rate is\n of importance, such as streaming media.\n\nWidmer & Handley Experimental [Page 1]\n\f\nRFC 4654 TFMCC: Protocol Specification August 2006","scope_keywords":["4654","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 4654 This document specifies TCP-Friendly Multicast Congestion Control\n (TFMCC). TFMCC is a congestion control mechanism for multicast\n transmissions in a best-effort Internet environment. It is a\n single-rate congestion control scheme, where the sending rate is\n adapted to the receiver experiencing the worst network conditions.\n TFMCC is reasonably fair when competing for bandwidth with TCP flows\n and has a relatively low variation of throughput over time, making it\n suitable for applications where a relatively smooth sending rate is\n of importance, such as streaming media.\n\nWidmer & Handley Experimental [Page 1]\n\f\nRFC 4654 TFMCC: Protocol Specification August 2006 4654 path nested-reference unchanged"},{"id":"IETF RFC 4834","type":"specification","body":"IETF","designation":"RFC 4834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4834.txt","https://www.rfc-editor.org/rfc/rfc4834.pdf"],"folder":"IETF/RFC-4834","files":{"txt":{"path":"standards/IETF/RFC-4834/RFC-4834.txt","sha256":"494911a3705d8aebdd58f1bbdea48fd250c4a6cfcb0f746db55f5298fd8ab7fb"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of functional requirements for network\n solutions that allow the deployment of IP multicast within Layer 3\n (L3) Provider-Provisioned Virtual Private Networks (PPVPNs). It\n specifies requirements both from the end user and service provider\n standpoints. It is intended that potential solutions specifying the\n support of IP multicast within such VPNs will use these requirements\n as guidelines.\n\nMorin Informational [Page 1]\n\f\nRFC 4834 L3VPN Mcast Reqs April 2007","scope_keywords":["4834","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null}],"search_text":"IETF RFC 4834 This document presents a set of functional requirements for network\n solutions that allow the deployment of IP multicast within Layer 3\n (L3) Provider-Provisioned Virtual Private Networks (PPVPNs). It\n specifies requirements both from the end user and service provider\n standpoints. It is intended that potential solutions specifying the\n support of IP multicast within such VPNs will use these requirements\n as guidelines.\n\nMorin Informational [Page 1]\n\f\nRFC 4834 L3VPN Mcast Reqs April 2007 4834 key management trust nested-reference unchanged"},{"id":"IETF RFC 5135","type":"specification","body":"IETF","designation":"RFC 5135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5135.txt","https://www.rfc-editor.org/rfc/rfc5135.pdf"],"folder":"IETF/RFC-5135","files":{"txt":{"path":"standards/IETF/RFC-5135/RFC-5135.txt","sha256":"3797b53f0eac363bd3128e2029d95c3c5b23c7b767d8824cce094498f89c2cf6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies requirements for a for a Network Address\n Translator (NAT) and a Network Address Port Translator (NAPT) that\n support Any Source IP Multicast or Source-Specific IP Multicast. An\n IP multicast-capable NAT device that adheres to the requirements of\n this document can optimize the operation of IP multicast applications\n that are generally unaware of IP multicast NAT devices.","scope_keywords":["5135","key","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null}],"search_text":"IETF RFC 5135 This document specifies requirements for a for a Network Address\n Translator (NAT) and a Network Address Port Translator (NAPT) that\n support Any Source IP Multicast or Source-Specific IP Multicast. An\n IP multicast-capable NAT device that adheres to the requirements of\n this document can optimize the operation of IP multicast applications\n that are generally unaware of IP multicast NAT devices. 5135 key management profile nested-reference unchanged"},{"id":"IETF RFC 5374","type":"specification","body":"IETF","designation":"RFC 5374","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5374.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5374.txt","https://www.rfc-editor.org/rfc/rfc5374.pdf"],"folder":"IETF/RFC-5374","files":{"txt":{"path":"standards/IETF/RFC-5374/RFC-5374.txt","sha256":"3e71cebf2c18c386d1dcdfe0bd41f20189564447aa43eecf0b098a63f86dc259"}},"tags":["nested-reference","unchanged"],"summary":"The Security Architecture for the Internet Protocol describes\n security services for traffic at the IP layer. That architecture\n primarily defines services for Internet Protocol (IP) unicast\n packets. This document describes how the IPsec security services are\n applied to IP multicast packets. These extensions are relevant only\n for an IPsec implementation that supports multicast.\n\nWeis, et al. Standards Track [Page 1]\n\f\nRFC 5374 Multicast Extensions to RFC 4301 November 2008","scope_keywords":["5374","algorithm","authentication","authorization","http","key","license","management","policy","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 5374 The Security Architecture for the Internet Protocol describes\n security services for traffic at the IP layer. That architecture\n primarily defines services for Internet Protocol (IP) unicast\n packets. This document describes how the IPsec security services are\n applied to IP multicast packets. These extensions are relevant only\n for an IPsec implementation that supports multicast.\n\nWeis, et al. Standards Track [Page 1]\n\f\nRFC 5374 Multicast Extensions to RFC 4301 November 2008 5374 algorithm authentication authorization http key license management policy preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 5401","type":"specification","body":"IETF","designation":"RFC 5401","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5401.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5401.txt","https://www.rfc-editor.org/rfc/rfc5401.pdf"],"folder":"IETF/RFC-5401","files":{"txt":{"path":"standards/IETF/RFC-5401/RFC-5401.txt","sha256":"7f3ad44ab52778b92733e6afb224c734c907718025ad7663263913bd48964b83"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the creation of reliable multicast protocols\n that utilize negative-acknowledgment (NACK) feedback. The rationale\n for protocol design goals and assumptions are presented. Technical\n challenges for NACK-based (and in some cases general) reliable\n multicast protocol operation are identified. These goals and\n challenges are resolved into a set of functional \"building blocks\"\n that address different aspects of reliable multicast protocol\n operation. It is anticipated that these building blocks will be\n useful in generating different instantiations of reliable multicast\n protocols. This document obsoletes RFC 3941.\n\nAdamson, et al. Standards Track [Page 1]\n\f\nRFC 5401 Multicast NACK BB November 2008","scope_keywords":["5401","delivery","http","identification","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null}],"search_text":"IETF RFC 5401 This document discusses the creation of reliable multicast protocols\n that utilize negative-acknowledgment (NACK) feedback. The rationale\n for protocol design goals and assumptions are presented. Technical\n challenges for NACK-based (and in some cases general) reliable\n multicast protocol operation are identified. These goals and\n challenges are resolved into a set of functional \"building blocks\"\n that address different aspects of reliable multicast protocol\n operation. It is anticipated that these building blocks will be\n useful in generating different instantiations of reliable multicast\n protocols. This document obsoletes RFC 3941.\n\nAdamson, et al. Standards Track [Page 1]\n\f\nRFC 5401 Multicast NACK BB November 2008 5401 delivery http identification license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5740","type":"specification","body":"IETF","designation":"RFC 5740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5740.txt","https://www.rfc-editor.org/rfc/rfc5740.pdf"],"folder":"IETF/RFC-5740","files":{"txt":{"path":"standards/IETF/RFC-5740/RFC-5740.txt","sha256":"b4f5e10000c47ebfe1123d52831b93ed63eae5c01b441a114f94be0a6b2a9975"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the messages and procedures of the Negative-\n ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.\n This protocol can provide end-to-end reliable transport of bulk data\n objects or streams over generic IP multicast routing and forwarding\n services. NORM uses a selective, negative acknowledgment mechanism\n for transport reliability and offers additional protocol mechanisms\n to allow for operation with minimal a priori coordination among\n senders and receivers. A congestion control scheme is specified to\n allow the NORM protocol to fairly share available network bandwidth\n with other transport protocols such as Transmission Control Protocol\n (TCP). It is capable of operating with both reciprocal multicast\n routing among senders and receivers and with asymmetric connectivity\n (possibly a unicast return path) between the senders and receivers.\n The proto","scope_keywords":["5740","algorithm","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5740 This document describes the messages and procedures of the Negative-\n ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol.\n This protocol can provide end-to-end reliable transport of bulk data\n objects or streams over generic IP multicast routing and forwarding\n services. NORM uses a selective, negative acknowledgment mechanism\n for transport reliability and offers additional protocol mechanisms\n to allow for operation with minimal a priori coordination among\n senders and receivers. A congestion control scheme is specified to\n allow the NORM protocol to fairly share available network bandwidth\n with other transport protocols such as Transmission Control Protocol\n (TCP). It is capable of operating with both reciprocal multicast\n routing among senders and receivers and with asymmetric connectivity\n (possibly a unicast return path) between the senders and receivers.\n The proto 5740 algorithm delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5790","type":"specification","body":"IETF","designation":"RFC 5790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5790.txt","https://www.rfc-editor.org/rfc/rfc5790.pdf"],"folder":"IETF/RFC-5790","files":{"txt":{"path":"standards/IETF/RFC-5790/RFC-5790.txt","sha256":"9935bf8a6ad603b96758467b55d944fcf17edbb970be567d1875b4fafe17ad36"}},"tags":["nested-reference","unchanged"],"summary":"This document describes lightweight IGMPv3 and MLDv2 protocols (LW-\n IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of\n IGMPv3 and MLDv2. The interoperability with the full versions and\n the previous versions of IGMP and MLD is also taken into account.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5790.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the person","scope_keywords":["5790","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null}],"search_text":"IETF RFC 5790 This document describes lightweight IGMPv3 and MLDv2 protocols (LW-\n IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of\n IGMPv3 and MLDv2. The interoperability with the full versions and\n the previous versions of IGMP and MLD is also taken into account.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5790.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the person 5790 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5944","type":"specification","body":"IETF","designation":"RFC 5944","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5944.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5944.txt","https://www.rfc-editor.org/rfc/rfc5944.pdf"],"folder":"IETF/RFC-5944","files":{"txt":{"path":"standards/IETF/RFC-5944/RFC-5944.txt","sha256":"88a2b02b0c2223ff56f28b4bd4307da285490f17ff523e7317a385d0a7ae275e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community.","scope_keywords":["5944","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null}],"search_text":"IETF RFC 5944 This document specifies protocol enhancements that allow transparent\n routing of IP datagrams to mobile nodes in the Internet. Each mobile\n node is always identified by its home address, regardless of its\n current point of attachment to the Internet. While situated away\n from its home, a mobile node is also associated with a care-of\n address, which provides information about its current point of\n attachment to the Internet. The protocol provides for registering\n the care-of address with a home agent. The home agent sends\n datagrams destined for the mobile node through a tunnel to the care-\n of address. After arriving at the end of the tunnel, each datagram\n is then delivered to the mobile node.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. 5944 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6679","type":"specification","body":"IETF","designation":"RFC 6679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6679.txt","https://www.rfc-editor.org/rfc/rfc6679.pdf"],"folder":"IETF/RFC-6679","files":{"txt":{"path":"standards/IETF/RFC-6679/RFC-6679.txt","sha256":"ea1f9433eac64d0354a768ab1f4f0df337ed012e444077a82daf182bb3b20735"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies how Explicit Congestion Notification (ECN) can be\n used with the Real-time Transport Protocol (RTP) running over UDP,\n using the RTP Control Protocol (RTCP) as a feedback mechanism. It\n defines a new RTCP Extended Report (XR) block for periodic ECN\n feedback, a new RTCP transport feedback message for timely reporting\n of congestion events, and a Session Traversal Utilities for NAT\n (STUN) extension used in the optional initialisation method using\n Interactive Connectivity Establishment (ICE). Signalling and\n procedures for negotiation of capabilities and initialisation methods\n are also defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Int","scope_keywords":["6679","attribute","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6679 This memo specifies how Explicit Congestion Notification (ECN) can be\n used with the Real-time Transport Protocol (RTP) running over UDP,\n using the RTP Control Protocol (RTCP) as a feedback mechanism. It\n defines a new RTCP Extended Report (XR) block for periodic ECN\n feedback, a new RTCP transport feedback message for timely reporting\n of congestion events, and a Session Traversal Utilities for NAT\n (STUN) extension used in the optional initialisation method using\n Interactive Connectivity Establishment (ICE). Signalling and\n procedures for negotiation of capabilities and initialisation methods\n are also defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Int 6679 attribute http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6726","type":"specification","body":"IETF","designation":"RFC 6726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6726.txt","https://www.rfc-editor.org/rfc/rfc6726.pdf"],"folder":"IETF/RFC-6726","files":{"txt":{"path":"standards/IETF/RFC-6726/RFC-6726.txt","sha256":"a0d6e4b71d7d8cd66f2e242ec7235e38fa0b262532e191bb5c7983fb959ea6d7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines File Delivery over Unidirectional Transport\n (FLUTE), a protocol for the unidirectional delivery of files over the\n Internet, which is particularly suited to multicast networks. The\n specification builds on Asynchronous Layered Coding, the base\n protocol designed for massively scalable multicast distribution.\n This document obsoletes RFC 3926.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w","scope_keywords":["6726","algorithm","algorithms","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 6726 This document defines File Delivery over Unidirectional Transport\n (FLUTE), a protocol for the unidirectional delivery of files over the\n Internet, which is particularly suited to multicast networks. The\n specification builds on Asynchronous Layered Coding, the base\n protocol designed for massively scalable multicast distribution.\n This document obsoletes RFC 3926.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w 6726 algorithm algorithms delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6740","type":"specification","body":"IETF","designation":"RFC 6740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6740.txt","https://www.rfc-editor.org/rfc/rfc6740.pdf"],"folder":"IETF/RFC-6740","files":{"txt":{"path":"standards/IETF/RFC-6740/RFC-6740.txt","sha256":"253c39658b6f37a653653215e0e5f7d1be1b99a8bfa8d262b6945edad3ec6ea8"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an architectural description and the concept\n of operations for the Identifier-Locator Network Protocol (ILNP),\n which is an experimental, evolutionary enhancement to IP. This is a\n product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by the IRSG","scope_keywords":["6740","authentication","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6740 This document provides an architectural description and the concept\n of operations for the Identifier-Locator Network Protocol (ILNP),\n which is an experimental, evolutionary enhancement to IP. This is a\n product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by the IRSG 6740 authentication http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7201","type":"specification","body":"IETF","designation":"RFC 7201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7201.txt","https://www.rfc-editor.org/rfc/rfc7201.pdf"],"folder":"IETF/RFC-7201","files":{"txt":{"path":"standards/IETF/RFC-7201/RFC-7201.txt","sha256":"10fdc6a3761f561c57e353cd523a4041dfd7da59a5b2a91d979c34b246de6f8e"}},"tags":["nested-reference","unchanged"],"summary":"The Real-time Transport Protocol (RTP) is used in a large number of\n different application domains and environments. This heterogeneity\n implies that different security mechanisms are needed to provide\n services such as confidentiality, integrity, and source\n authentication of RTP and RTP Control Protocol (RTCP) packets\n suitable for the various environments. The range of solutions makes\n it difficult for RTP-based application developers to pick the most\n suitable mechanism. This document provides an overview of a number\n of security solutions for RTP and gives guidance for developers on\n how to choose the appropriate security mechanism.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commu","scope_keywords":["7201","authentication","encryption","http","key","keys","license","management","subject","tls","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null}],"search_text":"IETF RFC 7201 The Real-time Transport Protocol (RTP) is used in a large number of\n different application domains and environments. This heterogeneity\n implies that different security mechanisms are needed to provide\n services such as confidentiality, integrity, and source\n authentication of RTP and RTP Control Protocol (RTCP) packets\n suitable for the various environments. The range of solutions makes\n it difficult for RTP-based application developers to pick the most\n suitable mechanism. This document provides an overview of a number\n of security solutions for RTP and gives guidance for developers on\n how to choose the appropriate security mechanism.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commu 7201 authentication encryption http key keys license management subject tls trust tsp nested-reference unchanged"},{"id":"IETF RFC 7667","type":"specification","body":"IETF","designation":"RFC 7667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7667.txt","https://www.rfc-editor.org/rfc/rfc7667.pdf"],"folder":"IETF/RFC-7667","files":{"txt":{"path":"standards/IETF/RFC-7667/RFC-7667.txt","sha256":"6b05966e1b10ff4ba4de23c908414d96da4a3723abe67f27d44a643990ef441b"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses point-to-point and multi-endpoint topologies\n used in environments based on the Real-time Transport Protocol (RTP).\n In particular, centralized topologies commonly employed in the video\n conferencing industry are mapped to the RTP terminology.\n\n This document is updated with additional topologies and replaces RFC\n 5117.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this docume","scope_keywords":["7667","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 7667 This document discusses point-to-point and multi-endpoint topologies\n used in environments based on the Real-time Transport Protocol (RTP).\n In particular, centralized topologies commonly employed in the video\n conferencing industry are mapped to the RTP terminology.\n\n This document is updated with additional topologies and replaces RFC\n 5117.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this docume 7667 http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7761","type":"specification","body":"IETF","designation":"RFC 7761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7761.txt","https://www.rfc-editor.org/rfc/rfc7761.pdf"],"folder":"IETF/RFC-7761","files":{"txt":{"path":"standards/IETF/RFC-7761/RFC-7761.txt","sha256":"290c7221d27103826d09fe2bea3bfb133f84722e56577e0b5dfb26b65f90da16"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Protocol Independent Multicast - Sparse Mode\n (PIM-SM). PIM-SM is a multicast routing protocol that can use the\n underlying unicast routing information base or a separate multicast-\n capable routing information base. It builds unidirectional shared\n trees rooted at a Rendezvous Point (RP) per group, and it optionally\n creates shortest-path trees per source.\n\n This document obsoletes RFC 4601 by replacing it, addresses the\n errata filed against it, removes the optional (*,*,RP), PIM Multicast\n Border Router features and authentication using IPsec that lack\n sufficient deployment experience (see Appendix A), and moves the PIM\n specification to Internet Standard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re","scope_keywords":["7761","authentication","hash","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 7761 This document specifies Protocol Independent Multicast - Sparse Mode\n (PIM-SM). PIM-SM is a multicast routing protocol that can use the\n underlying unicast routing information base or a separate multicast-\n capable routing information base. It builds unidirectional shared\n trees rooted at a Rendezvous Point (RP) per group, and it optionally\n creates shortest-path trees per source.\n\n This document obsoletes RFC 4601 by replacing it, addresses the\n errata filed against it, removes the optional (*,*,RP), PIM Multicast\n Border Router features and authentication using IPsec that lack\n sufficient deployment experience (see Appendix A), and moves the PIM\n specification to Internet Standard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re 7761 authentication hash http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8084","type":"specification","body":"IETF","designation":"RFC 8084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8084.txt","https://www.rfc-editor.org/rfc/rfc8084.pdf"],"folder":"IETF/RFC-8084","files":{"txt":{"path":"standards/IETF/RFC-8084/RFC-8084.txt","sha256":"9bb7be6b1ed6ef77108d9cfbd0b9d8bf27e9a137aabb8183103415f59bd6c275"}},"tags":["nested-reference","unchanged"],"summary":"This document explains what is meant by the term \"network transport\n Circuit Breaker\". It describes the need for Circuit Breakers (CBs)\n for network tunnels and applications when using non-congestion-\n controlled traffic and explains where CBs are, and are not, needed.\n It also defines requirements for building a CB and the expected\n outcomes of using a CB within the Internet.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n h","scope_keywords":["8084","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 8084 This document explains what is meant by the term \"network transport\n Circuit Breaker\". It describes the need for Circuit Breakers (CBs)\n for network tunnels and applications when using non-congestion-\n controlled traffic and explains where CBs are, and are not, needed.\n It also defines requirements for building a CB and the expected\n outcomes of using a CB within the Internet.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n h 8084 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 1113","type":"specification","body":"IETF","designation":"RFC 1113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1113.txt","https://www.rfc-editor.org/rfc/rfc1113.pdf"],"folder":"IETF/RFC-1113","files":{"txt":{"path":"standards/IETF/RFC-1113/RFC-1113.txt","sha256":"d8976ffb278652e5fd4097166dbb91ad73a189dd49ab71d78974d31ad33d9904"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Linn\nRequest for Comments: 1113 DEC\nObsoletes RFCs: 989, 1040 IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I -- Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Curt Barker, Jim Bidzos, Matt Bishop, Danny Cohen, Tom\n Daniel, Charles Fox, Morrie Gasser, Russ Housley, S","scope_keywords":["1113","algorithm","algorithms","authentication","certificate","certificates","encryption","issuer","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1124","folder":"IETF/RFC-1124","source":"IETF/RFC-1124/RFC-1124.pdf","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1319","folder":"IETF/RFC-1319","source":"IETF/RFC-1319/RFC-1319.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null}],"search_text":"IETF RFC 1113 Network Working Group J. Linn\nRequest for Comments: 1113 DEC\nObsoletes RFCs: 989, 1040 IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I -- Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Curt Barker, Jim Bidzos, Matt Bishop, Danny Cohen, Tom\n Daniel, Charles Fox, Morrie Gasser, Russ Housley, S 1113 algorithm algorithms authentication certificate certificates encryption issuer key keys management nested-reference unchanged"},{"id":"IETF RFC 1124","type":"specification","body":"IETF","designation":"RFC 1124","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1124.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1124.txt","https://www.rfc-editor.org/rfc/rfc1124.pdf"],"folder":"IETF/RFC-1124","files":{"pdf":{"path":"standards/IETF/RFC-1124/RFC-1124.pdf","sha256":"a884da9ae569bde63eb1fe4390802828c9a55f81cbd256e82967c629d9f4f196"},"txt":{"path":"standards/IETF/RFC-1124/RFC-1124.txt","sha256":"a1ad24e3b6dd6f9256a59d7c42494a1e4ccd02f7fa5335d5fbf260e2488d3f4b"}},"tags":["nested-reference","unchanged"],"summary":null,"scope_keywords":["1124","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null}],"search_text":"IETF RFC 1124 1124 policy nested-reference unchanged"},{"id":"IETF RFC 1319","type":"specification","body":"IETF","designation":"RFC 1319","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1319.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1319.txt","https://www.rfc-editor.org/rfc/rfc1319.pdf"],"folder":"IETF/RFC-1319","files":{"txt":{"path":"standards/IETF/RFC-1319/RFC-1319.txt","sha256":"af6bf6d3e216f1776db63211dd282801d265a661c91ba3994c9b4d20d03c2aac"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 1319 RSA Laboratories\nUpdates: RFC 1115 April 1992\n\n The MD2 Message-Digest Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n The description of MD2 is based on material prepared by John Linn and\n Ron Rivest. Their permission to incorporate that material is greatly\n appreciated.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD2 Algorithm Description 2\n 4. Summary 4\n References 5\n APPENDIX A - Reference Implementation 5\n Security Considerations 17\n Author's Address 17\n\n1. Executive Summary\n\n This document describes the MD2 message-digest algorithm. The\n algorithm takes as input a message of arbitrary length and produces\n as output a 128-bit \"fingerprint\" or \"m","scope_keywords":["1319","algorithm","algorithms","authentication","certificate","key","license","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2313","folder":"IETF/RFC-2313","source":"IETF/RFC-2313/RFC-2313.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2437","folder":"IETF/RFC-2437","source":"IETF/RFC-2437/RFC-2437.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"IETF RFC 1319 Network Working Group B. Kaliski\nRequest for Comments: 1319 RSA Laboratories\nUpdates: RFC 1115 April 1992\n\n The MD2 Message-Digest Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n The description of MD2 is based on material prepared by John Linn and\n Ron Rivest. Their permission to incorporate that material is greatly\n appreciated.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD2 Algorithm Description 2\n 4. Summary 4\n References 5\n APPENDIX A - Reference Implementation 5\n Security Considerations 17\n Author's Address 17\n\n1. Executive Summary\n\n This document describes the MD2 message-digest algorithm. The\n algorithm takes as input a message of arbitrary length and produces\n as output a 128-bit \"fingerprint\" or \"m 1319 algorithm algorithms authentication certificate key license management signature nested-reference unchanged"},{"id":"IETF RFC 1421","type":"specification","body":"IETF","designation":"RFC 1421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1421.txt","https://www.rfc-editor.org/rfc/rfc1421.pdf"],"folder":"IETF/RFC-1421","files":{"txt":{"path":"standards/IETF/RFC-1421/RFC-1421.txt","sha256":"a31bb54b9850e3d1c474f66bf1d47b6074496afceb9ff2df43fe55e240098643"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Linn\nRequest for Comments: 1421 IAB IRTF PSRG, IETF PEM WG\nObsoletes: 1113 February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encryption and Authentication Procedures\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This document is the outgrowth of a series of meetings of the Privacy\n and Security Research Group (PSRG) of the IRTF and the PEM Working\n Group of the IETF. I would like to thank the members of the PSRG and\n the IETF PEM WG, as well as all participants in discussions on the\n \"pem-dev@tis.com\" mailing list, for the","scope_keywords":["1421","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1864","folder":"IETF/RFC-1864","source":"IETF/RFC-1864/RFC-1864.txt","version":null},{"body":"IETF","designation":"RFC 1875","folder":"IETF/RFC-1875","source":"IETF/RFC-1875/RFC-1875.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2228","folder":"IETF/RFC-2228","source":"IETF/RFC-2228/RFC-2228.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2479","folder":"IETF/RFC-2479","source":"IETF/RFC-2479/RFC-2479.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null}],"search_text":"IETF RFC 1421 Network Working Group J. Linn\nRequest for Comments: 1421 IAB IRTF PSRG, IETF PEM WG\nObsoletes: 1113 February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encryption and Authentication Procedures\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This document is the outgrowth of a series of meetings of the Privacy\n and Security Research Group (PSRG) of the IRTF and the PEM Working\n Group of the IETF. I would like to thank the members of the PSRG and\n the IETF PEM WG, as well as all participants in discussions on the\n \"pem-dev@tis.com\" mailing list, for the 1421 algorithm algorithms attribute attributes authentication certificate certificates encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 1422","type":"specification","body":"IETF","designation":"RFC 1422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1422.txt","https://www.rfc-editor.org/rfc/rfc1422.pdf"],"folder":"IETF/RFC-1422","files":{"txt":{"path":"standards/IETF/RFC-1422/RFC-1422.txt","sha256":"89985ada8536a8d9a3a33937dab03b7443d79c4f5775ada44dec0288fb0ba80e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 1422 BBN\nObsoletes: 1114 IAB IRTF PSRG, IETF PEM\n February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part II: Certificate-Based Key Management\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This memo is the outgrowth of a series of meetings of the Privacy and\n Security Research Group of the Internet Research Task Force (IRTF)\n and the Privacy-Enhanced Electronic Mail Working Group of the\n Internet Engineering Task Force (IETF). I would like to thank the\n members of the PSRG and the PEM WG for their comments and\n c","scope_keywords":["1422","algorithm","algorithms","authentication","certificate","certificates","delivery","identification","key","keys","license","management","policies","policy","registered","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1875","folder":"IETF/RFC-1875","source":"IETF/RFC-1875/RFC-1875.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null}],"search_text":"IETF RFC 1422 Network Working Group S. Kent\nRequest for Comments: 1422 BBN\nObsoletes: 1114 IAB IRTF PSRG, IETF PEM\n February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part II: Certificate-Based Key Management\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This memo is the outgrowth of a series of meetings of the Privacy and\n Security Research Group of the Internet Research Task Force (IRTF)\n and the Privacy-Enhanced Electronic Mail Working Group of the\n Internet Engineering Task Force (IETF). I would like to thank the\n members of the PSRG and the PEM WG for their comments and\n c 1422 algorithm algorithms authentication certificate certificates delivery identification key keys license management policies policy registered signature nested-reference unchanged"},{"id":"IETF RFC 2693","type":"specification","body":"IETF","designation":"RFC 2693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2693.txt","https://www.rfc-editor.org/rfc/rfc2693.pdf"],"folder":"IETF/RFC-2693","files":{"txt":{"path":"standards/IETF/RFC-2693/RFC-2693.txt","sha256":"6822d668195c3d9b391f0c4f2b023341ba0e5a72e59d63c366a520de42c99098"}},"tags":["nested-reference","unchanged"],"summary":"The SPKI Working Group has developed a standard form for digital\n certificates whose main purpose is authorization rather than\n authentication. These structures bind either names or explicit\n authorizations to keys or other objects. The binding to a key can be\n directly to an explicit key, or indirectly through the hash of the\n key or a name for it. The name and authorization structures can be\n used separately or together. We use S-expressions as the standard\n format for these certificates and define a canonical form for those\n S-expressions. As part of this development, a mechanism for deriving\n authorization decisions from a mixture of certificate types was\n developed and is presented in this document.\n\n This document gives the theory behind SPKI certificates and ACLs\n without going into technical detail about those structures or their\n uses.\n\nEllison, et al. Experimental [Page 1]\n\f\nRF","scope_keywords":["2693","attribute","authentication","authorization","certificate","certificates","crl","hash","key","keys","management","path","pki","qualified","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null}],"search_text":"IETF RFC 2693 The SPKI Working Group has developed a standard form for digital\n certificates whose main purpose is authorization rather than\n authentication. These structures bind either names or explicit\n authorizations to keys or other objects. The binding to a key can be\n directly to an explicit key, or indirectly through the hash of the\n key or a name for it. The name and authorization structures can be\n used separately or together. We use S-expressions as the standard\n format for these certificates and define a canonical form for those\n S-expressions. As part of this development, a mechanism for deriving\n authorization decisions from a mixture of certificate types was\n developed and is presented in this document.\n\n This document gives the theory behind SPKI certificates and ACLs\n without going into technical detail about those structures or their\n uses.\n\nEllison, et al. Experimental [Page 1]\n\f\nRF 2693 attribute authentication authorization certificate certificates crl hash key keys management path pki qualified revocation subject nested-reference unchanged"},{"id":"IETF RFC 1115","type":"specification","body":"IETF","designation":"RFC 1115","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1115.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1115.txt","https://www.rfc-editor.org/rfc/rfc1115.pdf"],"folder":"IETF/RFC-1115","files":{"txt":{"path":"standards/IETF/RFC-1115/RFC-1115.txt","sha256":"f5cf7d6a4f0161498911aaece145f312f1e6532c7a687900cc08e2d9821258d5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Linn\nRequest for Comments: 1115 DEC\n IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part III -- Algorithms, Modes, and Identifiers\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvement.\n This RFC provides definitions, references, and citations for\n algorithms, usage modes, and associated identifiers used in RFC-1113\n and RFC-1114 in support of privacy-enhanced electronic mail.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to","scope_keywords":["1115","algorithm","algorithms","authentication","certificate","certificates","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1319","folder":"IETF/RFC-1319","source":"IETF/RFC-1319/RFC-1319.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null}],"search_text":"IETF RFC 1115 Network Working Group J. Linn\nRequest for Comments: 1115 DEC\n IAB Privacy Task Force\n August 1989\n\n Privacy Enhancement for Internet Electronic Mail:\n Part III -- Algorithms, Modes, and Identifiers\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a draft standard elective protocol for the Internet\n community, and requests discussion and suggestions for improvement.\n This RFC provides definitions, references, and citations for\n algorithms, usage modes, and associated identifiers used in RFC-1113\n and RFC-1114 in support of privacy-enhanced electronic mail.\n Distribution of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to 1115 algorithm algorithms authentication certificate certificates encryption key keys nested-reference unchanged"},{"id":"IETF RFC 1423","type":"specification","body":"IETF","designation":"RFC 1423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1423.txt","https://www.rfc-editor.org/rfc/rfc1423.pdf"],"folder":"IETF/RFC-1423","files":{"txt":{"path":"standards/IETF/RFC-1423/RFC-1423.txt","sha256":"ef51a96b6830ae1e4fa1e123bb53096bede87e0f2844546f06c0d4e002f12569"}},"tags":["nested-reference","unchanged"],"summary":"This document provides definitions, formats, references, and\n citations for cryptographic algorithms, usage modes, and associated\n identifiers and parameters used in support of Privacy Enhanced Mail\n (PEM) in the Internet community. It is intended to become one member\n of the set of related PEM RFCs. This document is organized into four\n primary sections, dealing with message encryption algorithms, message\n integrity check algorithms, symmetric key management algorithms, and\n asymmetric key management algorithms (including both asymmetric\n encryption and asymmetric signature algorithms).\n\n Some parts of this material are cited by other documents and it is\n anticipated that some of the material herein may be changed, added,\n or replaced without affecting the citing documents. Therefore,\n algorithm-specific material has been placed into this separate\n document.\n\n Use of other algorithms an","scope_keywords":["1423","algorithm","algorithms","encryption","key","keys","management","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1875","folder":"IETF/RFC-1875","source":"IETF/RFC-1875/RFC-1875.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 1991","folder":"IETF/RFC-1991","source":"IETF/RFC-1991/RFC-1991.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2313","folder":"IETF/RFC-2313","source":"IETF/RFC-2313/RFC-2313.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"IETF RFC 1423 This document provides definitions, formats, references, and\n citations for cryptographic algorithms, usage modes, and associated\n identifiers and parameters used in support of Privacy Enhanced Mail\n (PEM) in the Internet community. It is intended to become one member\n of the set of related PEM RFCs. This document is organized into four\n primary sections, dealing with message encryption algorithms, message\n integrity check algorithms, symmetric key management algorithms, and\n asymmetric key management algorithms (including both asymmetric\n encryption and asymmetric signature algorithms).\n\n Some parts of this material are cited by other documents and it is\n anticipated that some of the material herein may be changed, added,\n or replaced without affecting the citing documents. Therefore,\n algorithm-specific material has been placed into this separate\n document.\n\n Use of other algorithms an 1423 algorithm algorithms encryption key keys management signature signatures nested-reference unchanged"},{"id":"IETF RFC 1143","type":"specification","body":"IETF","designation":"RFC 1143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1143.txt","https://www.rfc-editor.org/rfc/rfc1143.pdf"],"folder":"IETF/RFC-1143","files":{"txt":{"path":"standards/IETF/RFC-1143/RFC-1143.txt","sha256":"4d2ef5878b0b88742c860fc777d6d91ad61580633fe277eae06410a6eee04bdf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Bernstein\nRequest for Comments: 1143 NYU\n February 1990\n\n The Q Method of Implementing TELNET Option Negotiation\n\nStatus of This Memo\n\n This is RFC discusses an implementation approach to option\n negotiation in the Telnet protocol (RFC 854). It does not propose\n any changes to the TELNET protocol. Rather, it discusses the\n implementation of the protocol of one feature, only. This is not a\n protocol specification. This is an experimental method of\n implementing a protocol. This memo is not a recommendation of the\n Telnet Working Group of the Internet Engineering Task Force (IETF).\n This RFC is Copyright 1990, Daniel J. Bernstein. However,\n distribution of this memo in original form is unlimited.\n\n1. Introduction\n\n This RFC amplifies, supplements, and extends the RFC 854 [7] option\n negotiation rules and guidelines, which are insufficient to prevent\n all option neg","scope_keywords":["1143"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1143 Network Working Group D. Bernstein\nRequest for Comments: 1143 NYU\n February 1990\n\n The Q Method of Implementing TELNET Option Negotiation\n\nStatus of This Memo\n\n This is RFC discusses an implementation approach to option\n negotiation in the Telnet protocol (RFC 854). It does not propose\n any changes to the TELNET protocol. Rather, it discusses the\n implementation of the protocol of one feature, only. This is not a\n protocol specification. This is an experimental method of\n implementing a protocol. This memo is not a recommendation of the\n Telnet Working Group of the Internet Engineering Task Force (IETF).\n This RFC is Copyright 1990, Daniel J. Bernstein. However,\n distribution of this memo in original form is unlimited.\n\n1. Introduction\n\n This RFC amplifies, supplements, and extends the RFC 854 [7] option\n negotiation rules and guidelines, which are insufficient to prevent\n all option neg 1143 nested-reference unchanged"},{"id":"IETF RFC 1402","type":"specification","body":"IETF","designation":"RFC 1402","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1402.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1402.txt","https://www.rfc-editor.org/rfc/rfc1402.pdf"],"folder":"IETF/RFC-1402","files":{"txt":{"path":"standards/IETF/RFC-1402/RFC-1402.txt","sha256":"190c80c085ece7f1ddc97403be4650c02a12f32460580cf0d8635ae79312dc9d"}},"tags":["nested-reference","unchanged"],"summary":"A wealth of information exists on the network. In fact, there is so\n much information that you could spend your entire life browsing. This\n paper will present some of the \"gold nuggets\" of information and file\n repositories on the network that could be useful.\n\n The ultimate goal is to make the route to these sources of\n information invisible to you. At present, this is not easy to do. I\n will explain some of the techniques that can be used to make these\n nuggets easier to pick up so that we all can be richer.","scope_keywords":["1402"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1463","folder":"IETF/RFC-1463","source":"IETF/RFC-1463/RFC-1463.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1855","folder":"IETF/RFC-1855","source":"IETF/RFC-1855/RFC-1855.txt","version":null}],"search_text":"IETF RFC 1402 A wealth of information exists on the network. In fact, there is so\n much information that you could spend your entire life browsing. This\n paper will present some of the \"gold nuggets\" of information and file\n repositories on the network that could be useful.\n\n The ultimate goal is to make the route to these sources of\n information invisible to you. At present, this is not easy to do. I\n will explain some of the techniques that can be used to make these\n nuggets easier to pick up so that we all can be richer. 1402 nested-reference unchanged"},{"id":"IETF RFC 1119","type":"specification","body":"IETF","designation":"RFC 1119","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1119.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1119.txt","https://www.rfc-editor.org/rfc/rfc1119.pdf"],"folder":"IETF/RFC-1119","files":{"pdf":{"path":"standards/IETF/RFC-1119/RFC-1119.pdf","sha256":"e738bfad098cb22b10969c0bd19cf6446ca5c17d97caf4aa0d5d7c6c898d34e5"},"txt":{"path":"standards/IETF/RFC-1119/RFC-1119.txt","sha256":"62cc25ff2d02de7844b2ccd954495e5aefba34714f14582470ae8bcf660b7fcc"}},"tags":["nested-reference","unchanged"],"summary":"RFC-1119 \"Network Time Protocol (Version 2) Specification and\n\nImplementation\" is available only in PostScript form in the file\n\nRFC1119.PS","scope_keywords":["1119"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1165","folder":"IETF/RFC-1165","source":"IETF/RFC-1165/RFC-1165.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null}],"search_text":"IETF RFC 1119 RFC-1119 \"Network Time Protocol (Version 2) Specification and\n\nImplementation\" is available only in PostScript form in the file\n\nRFC1119.PS 1119 nested-reference unchanged"},{"id":"IETF RFC 1165","type":"specification","body":"IETF","designation":"RFC 1165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1165.txt","https://www.rfc-editor.org/rfc/rfc1165.pdf"],"folder":"IETF/RFC-1165","files":{"txt":{"path":"standards/IETF/RFC-1165/RFC-1165.txt","sha256":"71646ec1b6ed3efc1dc0a159d198417a1b947bb1add90c8e05d3091e855cfeec"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Crowcroft\nRequest for Comments: 1165 UCL\n J. Onions\n Nottingham University\n June 1990\n\n Network Time Protocol (NTP) over the OSI\n Remote Operations Service\n\nStatus of this Memo\n\n This memo suggests an Experimental Protocol for the OSI and Internet\n communities. Hosts in either community, and in particular those on\n both are encouraged to experiment with this mechanism. Please refer\n to the current edition of the \"IAB Official Protocol Standards\" for\n the standardization state and status of this protocol. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction........................................... 1\n 1.1 Motivation............................................ 1\n 2. Protocol Overview...................................... 2\n 3. Operation of the Protocol.............................. 3\n 4. Network Considerations..............................","scope_keywords":["1165","algorithm","authentication","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1165 Network Working Group J. Crowcroft\nRequest for Comments: 1165 UCL\n J. Onions\n Nottingham University\n June 1990\n\n Network Time Protocol (NTP) over the OSI\n Remote Operations Service\n\nStatus of this Memo\n\n This memo suggests an Experimental Protocol for the OSI and Internet\n communities. Hosts in either community, and in particular those on\n both are encouraged to experiment with this mechanism. Please refer\n to the current edition of the \"IAB Official Protocol Standards\" for\n the standardization state and status of this protocol. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction........................................... 1\n 1.1 Motivation............................................ 1\n 2. Protocol Overview...................................... 2\n 3. Operation of the Protocol.............................. 3\n 4. Network Considerations.............................. 1165 algorithm authentication subject nested-reference unchanged"},{"id":"IETF RFC 1145","type":"specification","body":"IETF","designation":"RFC 1145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1145.txt","https://www.rfc-editor.org/rfc/rfc1145.pdf"],"folder":"IETF/RFC-1145","files":{"txt":{"path":"standards/IETF/RFC-1145/RFC-1145.txt","sha256":"63877cdd9515f246beac26271f7c5f33cf6e625a9a0286ceaf183e4dbc04dc9d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Zweig\nRequest for Comments: 1145 UIUC\n C. Partridge\n BBN\n February 1990\n\n TCP Alternate Checksum Options\n\nStatus of This Memo\n\n This memo suggests a pair of TCP options to allow use of alternate\n data checksum algorithms in the TCP header. The use of these options\n is experimental, and not recommended for production use.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Some members of the networking community have expressed interest in\n using checksum-algorithms with different error detection and\n correction properties than the standard TCP checksum. The option\n described in this memo provides a mechanism to negotiate the use of\n an alternate checksum at connection-establishment time, as well as a\n mechanism to carry additional checksum information for algorithms\n that utilize checksums that are longer than 16 bits.\n\nDefinition of the Options\n\n The TCP A","scope_keywords":["1145","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1146","folder":"IETF/RFC-1146","source":"IETF/RFC-1146/RFC-1146.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1145 Network Working Group J. Zweig\nRequest for Comments: 1145 UIUC\n C. Partridge\n BBN\n February 1990\n\n TCP Alternate Checksum Options\n\nStatus of This Memo\n\n This memo suggests a pair of TCP options to allow use of alternate\n data checksum algorithms in the TCP header. The use of these options\n is experimental, and not recommended for production use.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Some members of the networking community have expressed interest in\n using checksum-algorithms with different error detection and\n correction properties than the standard TCP checksum. The option\n described in this memo provides a mechanism to negotiate the use of\n an alternate checksum at connection-establishment time, as well as a\n mechanism to carry additional checksum information for algorithms\n that utilize checksums that are longer than 16 bits.\n\nDefinition of the Options\n\n The TCP A 1145 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1146","type":"specification","body":"IETF","designation":"RFC 1146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1146.txt","https://www.rfc-editor.org/rfc/rfc1146.pdf"],"folder":"IETF/RFC-1146","files":{"txt":{"path":"standards/IETF/RFC-1146/RFC-1146.txt","sha256":"aeac65d81ef0d3fc24e71201e6b67ce64444aafffc961249a6644a9176b16efc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Zweig\nRequest for Comments: 1146 UIUC\nObsoletes: RFC 1145 C. Partridge\n BBN\n March 1990\n\n TCP Alternate Checksum Options\n\nStatus of This Memo\n\n This memo suggests a pair of TCP options to allow use of alternate\n data checksum algorithms in the TCP header. The use of these options\n is experimental, and not recommended for production use.\n\n Note: This RFC corrects errors introduced in the editing process in\n RFC 1145.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Some members of the networking community have expressed interest in\n using checksum-algorithms with different error detection and\n correction properties than the standard TCP checksum. The option\n described in this memo provides a mechanism to negotiate the use of\n an alternate checksum at connection-establishment time, as well as a\n mechanism to carry additional checksum information for algori","scope_keywords":["1146","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1146 Network Working Group J. Zweig\nRequest for Comments: 1146 UIUC\nObsoletes: RFC 1145 C. Partridge\n BBN\n March 1990\n\n TCP Alternate Checksum Options\n\nStatus of This Memo\n\n This memo suggests a pair of TCP options to allow use of alternate\n data checksum algorithms in the TCP header. The use of these options\n is experimental, and not recommended for production use.\n\n Note: This RFC corrects errors introduced in the editing process in\n RFC 1145.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Some members of the networking community have expressed interest in\n using checksum-algorithms with different error detection and\n correction properties than the standard TCP checksum. The option\n described in this memo provides a mechanism to negotiate the use of\n an alternate checksum at connection-establishment time, as well as a\n mechanism to carry additional checksum information for algori 1146 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1180","type":"specification","body":"IETF","designation":"RFC 1180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1180.txt","https://www.rfc-editor.org/rfc/rfc1180.pdf"],"folder":"IETF/RFC-1180","files":{"txt":{"path":"standards/IETF/RFC-1180/RFC-1180.txt","sha256":"b5a6e523c94d95991d9a8fa12adceafd5e2ade9c3c4963a15657f62b2fb2fb66"}},"tags":["nested-reference","unchanged"],"summary":"computers benefit from the installation of an internet because of the\n interoperability in computers on the market. Generally, when you buy\n a computer, it will interoperate. If the computer does not have\n interoperability, and interoperability can not be added, it occupies\n a rare and special niche in the market.","scope_keywords":["1180","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1180 computers benefit from the installation of an internet because of the\n interoperability in computers on the market. Generally, when you buy\n a computer, it will interoperate. If the computer does not have\n interoperability, and interoperability can not be added, it occupies\n a rare and special niche in the market. 1180 management path pid nested-reference unchanged"},{"id":"IETF RFC 1370","type":"specification","body":"IETF","designation":"RFC 1370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1370.txt","https://www.rfc-editor.org/rfc/rfc1370.pdf"],"folder":"IETF/RFC-1370","files":{"txt":{"path":"standards/IETF/RFC-1370/RFC-1370.txt","sha256":"ab4c84f76320416b468b3c306581fd3beb7ab6db557eb266c508bc558ac3e336"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Architecture Board\nRequest for Comments: 1370 Lyman Chapin, Chair\n October 1992\n\n Applicability Statement for OSPF\n\nStatus of this Memo\n\n This memo is an IAB standards track Applicability Statement for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this specification. Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n Users and vendors have expressed a strong need for IP routers from\n different vendors that can interoperate using a common Interior\n Gateway Protocol (IGP). There is therefore an urgent requirement for\n a high-functionality non-proprietary 'open' IGP that will be\n ubiquitously available from all IP router vendors.\n\n The Open Shortest Path First (OSPF) routing protocol [1] was\n d","scope_keywords":["1370","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1500","folder":"IETF/RFC-1500","source":"IETF/RFC-1500/RFC-1500.txt","version":null},{"body":"IETF","designation":"RFC 1540","folder":"IETF/RFC-1540","source":"IETF/RFC-1540/RFC-1540.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1370 Network Working Group Internet Architecture Board\nRequest for Comments: 1370 Lyman Chapin, Chair\n October 1992\n\n Applicability Statement for OSPF\n\nStatus of this Memo\n\n This memo is an IAB standards track Applicability Statement for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this specification. Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n Users and vendors have expressed a strong need for IP routers from\n different vendors that can interoperate using a common Interior\n Gateway Protocol (IGP). There is therefore an urgent requirement for\n a high-functionality non-proprietary 'open' IGP that will be\n ubiquitously available from all IP router vendors.\n\n The Open Shortest Path First (OSPF) routing protocol [1] was\n d 1370 management path nested-reference unchanged"},{"id":"IETF RFC 1385","type":"specification","body":"IETF","designation":"RFC 1385","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1385.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1385.txt","https://www.rfc-editor.org/rfc/rfc1385.pdf"],"folder":"IETF/RFC-1385","files":{"txt":{"path":"standards/IETF/RFC-1385/RFC-1385.txt","sha256":"62f4ba8e49f9dac3792bcec40c88b638cd4772cc4f668954761dae4518c45c73"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Z. Wang\nRequest for Comments: 1385 University College London\n November 1992\n\n EIP: The Extended Internet Protocol\n A Framework for Maintaining Backward Compatibility\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n The Extended Internet Protocol (EIP) provides a framework for solving\n the problem of address space exhaustion with a new addressing and\n routing scheme, yet maintaining maximum backward compatibility with\n current IP. EIP can substantially reduce the amount of modifications\n needed to the current Internet systems and greatly ease the\n difficulties of transition. This is an \"idea\" paper and discussion is\n strongly encouraged on Big-Internet@munnari.oz.au.\n\nIntroduction\n\n The Internet faces two serious scaling problems: address ex","scope_keywords":["1385","algorithm","algorithms","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null}],"search_text":"IETF RFC 1385 Network Working Group Z. Wang\nRequest for Comments: 1385 University College London\n November 1992\n\n EIP: The Extended Internet Protocol\n A Framework for Maintaining Backward Compatibility\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n The Extended Internet Protocol (EIP) provides a framework for solving\n the problem of address space exhaustion with a new addressing and\n routing scheme, yet maintaining maximum backward compatibility with\n current IP. EIP can substantially reduce the amount of modifications\n needed to the current Internet systems and greatly ease the\n difficulties of transition. This is an \"idea\" paper and discussion is\n strongly encouraged on Big-Internet@munnari.oz.au.\n\nIntroduction\n\n The Internet faces two serious scaling problems: address ex 1385 algorithm algorithms identification nested-reference unchanged"},{"id":"IETF RFC 1433","type":"specification","body":"IETF","designation":"RFC 1433","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1433.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1433.txt","https://www.rfc-editor.org/rfc/rfc1433.pdf"],"folder":"IETF/RFC-1433","files":{"txt":{"path":"standards/IETF/RFC-1433/RFC-1433.txt","sha256":"e0bea7630f2e2ee9ab1c504c8461fb0582d4739148ae7a866ffcde995e7cdc6d"}},"tags":["nested-reference","unchanged"],"summary":"A router with an interface to two IP networks via the same link level\n interface could observe that the two IP networks share the same link\n level network, and could advertise that information to hosts (via\n ICMP Redirects) and routers (via dynamic routing protocols).\n However, a host or router on only one of the IP networks could not\n use that information to communicate directly with hosts and routers\n on the other IP network unless it could resolve IP addresses on the\n \"foreign\" IP network to their corresponding link level addresses.\n Directed ARP is a dynamic address resolution procedure that enables\n hosts and routers to resolve advertised potential next-hop IP\n addresses on foreign IP networks to their associated link level\n addresses.\n\nAcknowledgments\n\n The authors are indebted to Joel Halpern of Network Systems\n Corporation and David O'Leary who provided valuable comments and\n ins","scope_keywords":["1433","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1433 A router with an interface to two IP networks via the same link level\n interface could observe that the two IP networks share the same link\n level network, and could advertise that information to hosts (via\n ICMP Redirects) and routers (via dynamic routing protocols).\n However, a host or router on only one of the IP networks could not\n use that information to communicate directly with hosts and routers\n on the other IP network unless it could resolve IP addresses on the\n \"foreign\" IP network to their corresponding link level addresses.\n Directed ARP is a dynamic address resolution procedure that enables\n hosts and routers to resolve advertised potential next-hop IP\n addresses on foreign IP networks to their associated link level\n addresses.\n\nAcknowledgments\n\n The authors are indebted to Joel Halpern of Network Systems\n Corporation and David O'Leary who provided valuable comments and\n ins 1433 presentation nested-reference unchanged"},{"id":"IETF RFC 1455","type":"specification","body":"IETF","designation":"RFC 1455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1455.txt","https://www.rfc-editor.org/rfc/rfc1455.pdf"],"folder":"IETF/RFC-1455","files":{"txt":{"path":"standards/IETF/RFC-1455/RFC-1455.txt","sha256":"d4bdaab64de4274578d059812d1f0fa65332134993e30e0cd1499e5c56e0ae05"}},"tags":["nested-reference","unchanged"],"summary":"This RFC documents an experimental protocol providing a Type of\n Service (TOS) to request maximum physical link security. This is an\n addition to the types of service enumerated in RFC 1349: Type of\n Service in the Internet Protocol Suite. The new TOS requests the\n network to provide what protection it can against surreptitious\n observation by outside agents of traffic so labeled. The purpose is\n protection against traffic analysis and as an additional possible\n level of data confidentiality. This TOS is consistent with all other\n defined types of service for IP version 4 in that it is based on link\n level characteristics and will not provide any particular guaranteed\n level of service.\n\n1. Nature of Requirement\n\n This Internet Protocol addition addresses two potential security\n requirements: resistance to traffic analysis and confidentiality.\n These are described in the two subsections ","scope_keywords":["1455","encryption","path","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1455 This RFC documents an experimental protocol providing a Type of\n Service (TOS) to request maximum physical link security. This is an\n addition to the types of service enumerated in RFC 1349: Type of\n Service in the Internet Protocol Suite. The new TOS requests the\n network to provide what protection it can against surreptitious\n observation by outside agents of traffic so labeled. The purpose is\n protection against traffic analysis and as an additional possible\n level of data confidentiality. This TOS is consistent with all other\n defined types of service for IP version 4 in that it is based on link\n level characteristics and will not provide any particular guaranteed\n level of service.\n\n1. Nature of Requirement\n\n This Internet Protocol addition addresses two potential security\n requirements: resistance to traffic analysis and confidentiality.\n These are described in the two subsections  1455 encryption path policy subject nested-reference unchanged"},{"id":"IETF RFC 1517","type":"specification","body":"IETF","designation":"RFC 1517","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1517.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1517.txt","https://www.rfc-editor.org/rfc/rfc1517.pdf"],"folder":"IETF/RFC-1517","files":{"txt":{"path":"standards/IETF/RFC-1517/RFC-1517.txt","sha256":"9483d161cbf48725d7941627b93a2ed4689f1a0e3a8663e4213fabdcaf5842a2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Engineering Steering Group\nRequest for Comments: 1517 R. Hinden, Editor\nCategory: Standards Track September 1993\n\n Applicability Statement for the Implementation of\n Classless Inter-Domain Routing (CIDR)\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n As the Internet has evolved and grown in recent years, it has become\n clear that it will soon face several serious scaling problems. These\n include:\n\n - Exhaustion of the class-B network address space. One\n fundamental cause of this problem is the lack of a network\n class of a size that is appro","scope_keywords":["1517","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1517 Network Working Group Internet Engineering Steering Group\nRequest for Comments: 1517 R. Hinden, Editor\nCategory: Standards Track September 1993\n\n Applicability Statement for the Implementation of\n Classless Inter-Domain Routing (CIDR)\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n As the Internet has evolved and grown in recent years, it has become\n clear that it will soon face several serious scaling problems. These\n include:\n\n - Exhaustion of the class-B network address space. One\n fundamental cause of this problem is the lack of a network\n class of a size that is appro 1517 management subject nested-reference unchanged"},{"id":"IETF RFC 1620","type":"specification","body":"IETF","designation":"RFC 1620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1620.txt","https://www.rfc-editor.org/rfc/rfc1620.pdf"],"folder":"IETF/RFC-1620","files":{"txt":{"path":"standards/IETF/RFC-1620/RFC-1620.txt","sha256":"0556ea960d0f5fd2d68c23e779a1d66899ef82cc53c032521950fa57cce2d4e5"}},"tags":["nested-reference","unchanged"],"summary":"The original Internet architecture assumed that each network is\n labeled with a single IP network number. This assumption may be\n violated for shared media, including \"large public data networks\"\n (LPDNs). The architecture still works if this assumption is\n violated, but it does not have a means to prevent multiple host-\n router and router-router hops through the shared medium. This memo\n discusses alternative approaches to extending the Internet\n architecture to eliminate some or all unnecessary hops.","scope_keywords":["1620","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 1937","folder":"IETF/RFC-1937","source":"IETF/RFC-1937/RFC-1937.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null}],"search_text":"IETF RFC 1620 The original Internet architecture assumed that each network is\n labeled with a single IP network number. This assumption may be\n violated for shared media, including \"large public data networks\"\n (LPDNs). The architecture still works if this assumption is\n violated, but it does not have a means to prevent multiple host-\n router and router-router hops through the shared medium. This memo\n discusses alternative approaches to extending the Internet\n architecture to eliminate some or all unnecessary hops. 1620 management nested-reference unchanged"},{"id":"IETF RFC 1626","type":"specification","body":"IETF","designation":"RFC 1626","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1626.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1626.txt","https://www.rfc-editor.org/rfc/rfc1626.pdf"],"folder":"IETF/RFC-1626","files":{"txt":{"path":"standards/IETF/RFC-1626/RFC-1626.txt","sha256":"b952cc27396734d66917b221753f6927be54fccf4fc65de5512d97c212cdd56e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Atkinson\nRequest for Comments: 1626 Naval Research Laboratory\nCategory: Standards Track May 1994\n\n Default IP MTU for use over ATM AAL5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nDefault Value for IP MTU over ATM AAL5\n\n Protocols in wide use throughout the Internet, such as the Network\n File System (NFS), currently use large frame sizes (e.g. 8 KB).\n Empirical evidence with various applications over the Transmission\n Control Protocol (TCP) indicates that larger Maximum Transmission\n Unit (MTU) sizes for the Internet Protocol (IP) tend to give bette","scope_keywords":["1626","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null}],"search_text":"IETF RFC 1626 Network Working Group R. Atkinson\nRequest for Comments: 1626 Naval Research Laboratory\nCategory: Standards Track May 1994\n\n Default IP MTU for use over ATM AAL5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nDefault Value for IP MTU over ATM AAL5\n\n Protocols in wide use throughout the Internet, such as the Network\n File System (NFS), currently use large frame sizes (e.g. 8 KB).\n Empirical evidence with various applications over the Transmission\n Control Protocol (TCP) indicates that larger Maximum Transmission\n Unit (MTU) sizes for the Internet Protocol (IP) tend to give bette 1626 management path nested-reference unchanged"},{"id":"IETF RFC 1755","type":"specification","body":"IETF","designation":"RFC 1755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1755.txt","https://www.rfc-editor.org/rfc/rfc1755.pdf"],"folder":"IETF/RFC-1755","files":{"txt":{"path":"standards/IETF/RFC-1755/RFC-1755.txt","sha256":"04739ad1c27ab5f67aa979011f1b60ebf00a1ccf69b6b0795a4be63cb13b4ab4"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the ATM call control signaling exchanges needed\n to support Classical IP over ATM implementations as described in RFC\n 1577 [LAUB94]. ATM endpoints will incorporate ATM signaling services\n as specified in the ATM Forum User-Network Interface (UNI)\n Specification Version 3.1 [ATMF94]. IP over ATM implementations\n utilize the services of local ATM signaling entities to establish and\n release ATM connections. This memo should be used to define the\n support required by IP over ATM implementations from their local ATM\n signaling entities.\n\n This document is an implementors guide intended to foster\n interoperability among RFC 1577, RFC 1483, and UNI ATM signaling. It\n applies to IP hosts and routers which are also ATM endsystems and\n assumes ATM networks that completely implement the ATM Forum UNI\n Specification Version 3.1. Unless explicitly stated, no distinction\n is made","scope_keywords":["1755"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 1937","folder":"IETF/RFC-1937","source":"IETF/RFC-1937/RFC-1937.txt","version":null},{"body":"IETF","designation":"RFC 2022","folder":"IETF/RFC-2022","source":"IETF/RFC-2022/RFC-2022.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 1755 This memo describes the ATM call control signaling exchanges needed\n to support Classical IP over ATM implementations as described in RFC\n 1577 [LAUB94]. ATM endpoints will incorporate ATM signaling services\n as specified in the ATM Forum User-Network Interface (UNI)\n Specification Version 3.1 [ATMF94]. IP over ATM implementations\n utilize the services of local ATM signaling entities to establish and\n release ATM connections. This memo should be used to define the\n support required by IP over ATM implementations from their local ATM\n signaling entities.\n\n This document is an implementors guide intended to foster\n interoperability among RFC 1577, RFC 1483, and UNI ATM signaling. It\n applies to IP hosts and routers which are also ATM endsystems and\n assumes ATM networks that completely implement the ATM Forum UNI\n Specification Version 3.1. Unless explicitly stated, no distinction\n is made 1755 nested-reference unchanged"},{"id":"IETF RFC 1770","type":"specification","body":"IETF","designation":"RFC 1770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1770.txt","https://www.rfc-editor.org/rfc/rfc1770.pdf"],"folder":"IETF/RFC-1770","files":{"txt":{"path":"standards/IETF/RFC-1770/RFC-1770.txt","sha256":"76d17f340e2867e895bb62817ac59647a4facd9a6d97f2e345c524c6b65d3749"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Graff\nRequest for Comments: 1770 US Army CECOM\nCategory: Informational March 1995\n\n IPv4 Option for Sender Directed Multi-Destination Delivery\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memo defines an IPv4 option to provide a sender directed multi-\n destination delivery mechanism called Selective Directed Broadcast\n Mode (SDBM). The SDBM provides unreliable UDP delivery to a set of\n IP addresses included in the option field of an IPv4 datagram. Data\n reliability if required will be provided by the application layer.\n This approach was developed to support sender directed multi-\n destination delivery to sparsely populated groups with no additional\n control traffic. This approach will find application in the","scope_keywords":["1770","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 1770 Network Working Group C. Graff\nRequest for Comments: 1770 US Army CECOM\nCategory: Informational March 1995\n\n IPv4 Option for Sender Directed Multi-Destination Delivery\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memo defines an IPv4 option to provide a sender directed multi-\n destination delivery mechanism called Selective Directed Broadcast\n Mode (SDBM). The SDBM provides unreliable UDP delivery to a set of\n IP addresses included in the option field of an IPv4 datagram. Data\n reliability if required will be provided by the application layer.\n This approach was developed to support sender directed multi-\n destination delivery to sparsely populated groups with no additional\n control traffic. This approach will find application in the 1770 delivery nested-reference unchanged"},{"id":"IETF RFC 1933","type":"specification","body":"IETF","designation":"RFC 1933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1933.txt","https://www.rfc-editor.org/rfc/rfc1933.pdf"],"folder":"IETF/RFC-1933","files":{"txt":{"path":"standards/IETF/RFC-1933/RFC-1933.txt","sha256":"a12ab039114c2631b4ec0439a48e87bddcb80b69b170a10dc03ce3938c25ee62"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. These mechanisms include\n providing complete implementations of both versions of the Internet\n Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4\n routing infrastructures. They are designed to allow IPv6 nodes to\n maintain complete compatibility with IPv4, which should greatly\n simplify the deployment of IPv6 in the Internet, and facilitate the\n eventual transition of the entire Internet to IPv6.\n\n1. Introduction\n\n The key to a successful IPv6 transition is compatibility with the\n large installed base of IPv4 hosts and routers. Maintaining\n compatibility with IPv4 while deploying IPv6 will streamline the task\n of transitioning the Internet to IPv6. This specification defines a\n set of mechanisms that IPv6 hosts and routers may implement in order\n to be compatible with IPv","scope_keywords":["1933","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2185","folder":"IETF/RFC-2185","source":"IETF/RFC-2185/RFC-2185.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 1933 This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. These mechanisms include\n providing complete implementations of both versions of the Internet\n Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4\n routing infrastructures. They are designed to allow IPv6 nodes to\n maintain complete compatibility with IPv4, which should greatly\n simplify the deployment of IPv6 in the Internet, and facilitate the\n eventual transition of the entire Internet to IPv6.\n\n1. Introduction\n\n The key to a successful IPv6 transition is compatibility with the\n large installed base of IPv4 hosts and routers. Maintaining\n compatibility with IPv4 while deploying IPv6 will streamline the task\n of transitioning the Internet to IPv6. This specification defines a\n set of mechanisms that IPv6 hosts and routers may implement in order\n to be compatible with IPv 1933 key nested-reference unchanged"},{"id":"IETF RFC 1937","type":"specification","body":"IETF","designation":"RFC 1937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1937.txt","https://www.rfc-editor.org/rfc/rfc1937.pdf"],"folder":"IETF/RFC-1937","files":{"txt":{"path":"standards/IETF/RFC-1937/RFC-1937.txt","sha256":"af824a66a714eee9e5fb6d1b618fb510540f404a596bd55a84056573c9150536"}},"tags":["nested-reference","unchanged"],"summary":"The IP architecture assumes that each Data Link subnetwork is labeled\n with a single IP subnet number. A pair of hosts with the same subnet\n number communicate directly (with no routers); a pair of hosts with\n different subnet numbers always communicate through one or more\n routers. As indicated in RFC1620, these assumptions may be too\n restrictive for large data networks, and specifically for networks\n based on switched virtual circuit (SVC) based technologies (e.g. ATM,\n Frame Relay, X.25), as these assumptions impose constraints on\n communication among hosts and routers through a network. The\n restrictions may preclude full utilization of the capabilities\n provided by the underlying SVC-based Data Link subnetwork. This\n document describes extensions to the IP architecture that relaxes\n these constraints, thus enabling the full utilization of the services\n provided by SVC-based Data Li","scope_keywords":["1937","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null}],"search_text":"IETF RFC 1937 The IP architecture assumes that each Data Link subnetwork is labeled\n with a single IP subnet number. A pair of hosts with the same subnet\n number communicate directly (with no routers); a pair of hosts with\n different subnet numbers always communicate through one or more\n routers. As indicated in RFC1620, these assumptions may be too\n restrictive for large data networks, and specifically for networks\n based on switched virtual circuit (SVC) based technologies (e.g. ATM,\n Frame Relay, X.25), as these assumptions impose constraints on\n communication among hosts and routers through a network. The\n restrictions may preclude full utilization of the capabilities\n provided by the underlying SVC-based Data Link subnetwork. This\n document describes extensions to the IP architecture that relaxes\n these constraints, thus enabling the full utilization of the services\n provided by SVC-based Data Li 1937 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 2001","type":"specification","body":"IETF","designation":"RFC 2001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2001.txt","https://www.rfc-editor.org/rfc/rfc2001.pdf"],"folder":"IETF/RFC-2001","files":{"txt":{"path":"standards/IETF/RFC-2001/RFC-2001.txt","sha256":"45ea64be6d218681374b118314679ff449c101452a46bc070600af9c18a21fc6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Stevens\nRequest for Comments: 2001 NOAO\nCategory: Standards Track January 1997\n\n TCP Slow Start, Congestion Avoidance,\n Fast Retransmit, and Fast Recovery Algorithms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n Modern implementations of TCP contain four intertwined algorithms\n that have never been fully documented as Internet standards: slow\n start, congestion avoidance, fast retransmit, and fast recovery. [2]\n and [3] provide some details on these algorithms, [4] provides\n examples of the algorithms in action, and [5] provides the source\n","scope_keywords":["2001","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2309","folder":"IETF/RFC-2309","source":"IETF/RFC-2309/RFC-2309.txt","version":null},{"body":"IETF","designation":"RFC 2357","folder":"IETF/RFC-2357","source":"IETF/RFC-2357/RFC-2357.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2582","folder":"IETF/RFC-2582","source":"IETF/RFC-2582/RFC-2582.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 2001 Network Working Group W. Stevens\nRequest for Comments: 2001 NOAO\nCategory: Standards Track January 1997\n\n TCP Slow Start, Congestion Avoidance,\n Fast Retransmit, and Fast Recovery Algorithms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n Modern implementations of TCP contain four intertwined algorithms\n that have never been fully documented as Internet standards: slow\n start, congestion avoidance, fast retransmit, and fast recovery. [2]\n and [3] provide some details on these algorithms, [4] provides\n examples of the algorithms in action, and [5] provides the source\n 2001 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 2075","type":"specification","body":"IETF","designation":"RFC 2075","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2075.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2075.txt","https://www.rfc-editor.org/rfc/rfc2075.pdf"],"folder":"IETF/RFC-2075","files":{"txt":{"path":"standards/IETF/RFC-2075/RFC-2075.txt","sha256":"6981c9ed8f03c7e2aab0d7d66ab24e32ff9f3a3956cce9b7f22ad95620f0e0c7"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to implement an IP echo host. IP echo hosts\n send back IP datagrams after exchanging the source and destination IP\n addresses. The effect is that datagrams sent to the echo host are\n sent back to the source, as if they originated at the echo host.","scope_keywords":["2075","path","presentation","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2075 This memo describes how to implement an IP echo host. IP echo hosts\n send back IP datagrams after exchanging the source and destination IP\n addresses. The effect is that datagrams sent to the echo host are\n sent back to the source, as if they originated at the echo host. 2075 path presentation timestamp nested-reference unchanged"},{"id":"IETF RFC 2309","type":"specification","body":"IETF","designation":"RFC 2309","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2309.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2309.txt","https://www.rfc-editor.org/rfc/rfc2309.pdf"],"folder":"IETF/RFC-2309","files":{"txt":{"path":"standards/IETF/RFC-2309/RFC-2309.txt","sha256":"41da33d50b5ae16e4955f3017ec639defb804498983d6cc934bb4799f56de1cd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Braden, USC/ISI\nRequest for Comments: 2309 D. Clark, MIT LCS\nCategory: Informational J. Crowcroft, UCL\n B. Davie, Cisco Systems\n S. Deering, Cisco Systems\n D. Estrin, USC\n S. Floyd, LBNL\n V. Jacobson, LBNL\n G. Minshall, Fiberlane\n C. Partridge, BBN\n L. Peterson, University of Arizona\n K. Ramakrishnan, ATT Labs Research\n S. Shenker, Xerox PARC\n J. Wroclawski, MIT LCS\n L. Zhang, UCLA\n April 1998\n\n Recommendations on Queue Management and Congestion Avoidance\n in the Internet\n\nStatus of Memo\n\n This memo provides information for the Internet community. It\n does not specify an Internet standard of any kind. Distribution\n of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This memo presents two recommendations to the Internet community\n concerning measures to improve and preserve Internet performanc","scope_keywords":["2309","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2638","folder":"IETF/RFC-2638","source":"IETF/RFC-2638/RFC-2638.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null}],"search_text":"IETF RFC 2309 Network Working Group B. Braden, USC/ISI\nRequest for Comments: 2309 D. Clark, MIT LCS\nCategory: Informational J. Crowcroft, UCL\n B. Davie, Cisco Systems\n S. Deering, Cisco Systems\n D. Estrin, USC\n S. Floyd, LBNL\n V. Jacobson, LBNL\n G. Minshall, Fiberlane\n C. Partridge, BBN\n L. Peterson, University of Arizona\n K. Ramakrishnan, ATT Labs Research\n S. Shenker, Xerox PARC\n J. Wroclawski, MIT LCS\n L. Zhang, UCLA\n April 1998\n\n Recommendations on Queue Management and Congestion Avoidance\n in the Internet\n\nStatus of Memo\n\n This memo provides information for the Internet community. It\n does not specify an Internet standard of any kind. Distribution\n of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This memo presents two recommendations to the Internet community\n concerning measures to improve and preserve Internet performanc 2309 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 2331","type":"specification","body":"IETF","designation":"RFC 2331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2331.txt","https://www.rfc-editor.org/rfc/rfc2331.pdf"],"folder":"IETF/RFC-2331","files":{"txt":{"path":"standards/IETF/RFC-2331/RFC-2331.txt","sha256":"bbf9a7d710bdf8c2ad7a1ffbb1e8a0eff30e37f884f94052ba387ee23f9a3754"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to efficiently use the ATM call control\n signalling procedures defined in UNI Signalling 4.0 [SIG40] to\n support IP over ATM environments as described in RFC 2225 [LAUB98]\n and in RFC 2332 [LUC98]. Among the new features found in UNI\n Signalling 4.0 are Available Bit Rate signalling and traffic\n parameter negotiation. This memo highlights the features of UNI\n Signalling 4.0 that provide IP entities capabilities for requesting\n ATM service in sites with SVC support, whether it is private ATM or\n publicly provisioned ATM, in which case the SVC support is probably\n configured inside PVPs.\n\n This document is only relevant to IP when used as the well known\n \"best effort\" connectionless service. In particular, this means that\n this document does not pertain to IP in the presence of implemented\n IP Integrated Services. The topic of IP with Integrated Services\n over ATM w","scope_keywords":["2331","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2331 This memo describes how to efficiently use the ATM call control\n signalling procedures defined in UNI Signalling 4.0 [SIG40] to\n support IP over ATM environments as described in RFC 2225 [LAUB98]\n and in RFC 2332 [LUC98]. Among the new features found in UNI\n Signalling 4.0 are Available Bit Rate signalling and traffic\n parameter negotiation. This memo highlights the features of UNI\n Signalling 4.0 that provide IP entities capabilities for requesting\n ATM service in sites with SVC support, whether it is private ATM or\n publicly provisioned ATM, in which case the SVC support is probably\n configured inside PVPs.\n\n This document is only relevant to IP when used as the well known\n \"best effort\" connectionless service. In particular, this means that\n this document does not pertain to IP in the presence of implemented\n IP Integrated Services. The topic of IP with Integrated Services\n over ATM w 2331 key management path nested-reference unchanged"},{"id":"IETF RFC 2414","type":"specification","body":"IETF","designation":"RFC 2414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2414.txt","https://www.rfc-editor.org/rfc/rfc2414.pdf"],"folder":"IETF/RFC-2414","files":{"txt":{"path":"standards/IETF/RFC-2414/RFC-2414.txt","sha256":"715e71b13addb68041a9d8ee0177d0acfb2bdab3d851fadc988663aad31fbef8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an increase in the permitted initial window\n for TCP from one segment to roughly 4K bytes. This document\n discusses the advantages and disadvantages of such a change,\n outlining experimental results that indicate the costs and benefits\n of such a change to TCP.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1. TCP Modification\n\n This document specifies an increase in the permitted upper bound for\n TCP's initial window from one segment to between two and four\n segments. In most cases, this change results in an upper bound on\n the initial window of roughly 4K bytes (although given a large\n segment size, the permitted initial window of two segments could be\n significantly larger than 4K bytes). ","scope_keywords":["2414","http","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2416","folder":"IETF/RFC-2416","source":"IETF/RFC-2416/RFC-2416.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null}],"search_text":"IETF RFC 2414 This document specifies an increase in the permitted initial window\n for TCP from one segment to roughly 4K bytes. This document\n discusses the advantages and disadvantages of such a change,\n outlining experimental results that indicate the costs and benefits\n of such a change to TCP.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1. TCP Modification\n\n This document specifies an increase in the permitted upper bound for\n TCP's initial window from one segment to between two and four\n segments. In most cases, this change results in an upper bound on\n the initial window of roughly 4K bytes (although given a large\n segment size, the permitted initial window of two segments could be\n significantly larger than 4K bytes).  2414 http key path nested-reference unchanged"},{"id":"IETF RFC 2463","type":"specification","body":"IETF","designation":"RFC 2463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2463.txt","https://www.rfc-editor.org/rfc/rfc2463.pdf"],"folder":"IETF/RFC-2463","files":{"txt":{"path":"standards/IETF/RFC-2463/RFC-2463.txt","sha256":"d6c2e63aa72f4b625c90965ca7aecc38321668b0f3409d7b04534d1df046759c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of Internet Control Message Protocol\n (ICMP) messages for use with version 6 of the Internet Protocol\n (IPv6).","scope_keywords":["2463","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null}],"search_text":"IETF RFC 2463 This document specifies a set of Internet Control Message Protocol\n (ICMP) messages for use with version 6 of the Internet Protocol\n (IPv6). 2463 key path subject nested-reference unchanged"},{"id":"IETF RFC 2474","type":"specification","body":"IETF","designation":"RFC 2474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2474.txt","https://www.rfc-editor.org/rfc/rfc2474.pdf"],"folder":"IETF/RFC-2474","files":{"txt":{"path":"standards/IETF/RFC-2474/RFC-2474.txt","sha256":"c490f3e15aa0b85b4117fe31ffbe68f17bf12e68357e8a1651c520ba2589f909"}},"tags":["nested-reference","unchanged"],"summary":"Differentiated services enhancements to the Internet protocol are\n intended to enable scalable service discrimination in the Internet\n without the need for per-flow state and signaling at every hop. A\n variety of services may be built from a small, well-defined set of\n building blocks which are deployed in network nodes. The services\n may be either end-to-end or intra-domain; they include both those\n that can satisfy quantitative performance requirements (e.g., peak\n bandwidth) and those based on relative performance (e.g., \"class\"\n differentiation). Services can be constructed by a combination of:\n\n - setting bits in an IP header field at network boundaries\n (autonomous system boundaries, internal administrative boundaries,\n or hosts),\n - using those bits to determine how packets are forwarded by the\n nodes inside the network, and\n - conditioning the marked packets at network boundaries","scope_keywords":["2474","delivery","management","path","pid","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2597","folder":"IETF/RFC-2597","source":"IETF/RFC-2597/RFC-2597.txt","version":null},{"body":"IETF","designation":"RFC 2598","folder":"IETF/RFC-2598","source":"IETF/RFC-2598/RFC-2598.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2697","folder":"IETF/RFC-2697","source":"IETF/RFC-2697/RFC-2697.txt","version":null},{"body":"IETF","designation":"RFC 2698","folder":"IETF/RFC-2698","source":"IETF/RFC-2698/RFC-2698.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2836","folder":"IETF/RFC-2836","source":"IETF/RFC-2836/RFC-2836.txt","version":null},{"body":"IETF","designation":"RFC 2859","folder":"IETF/RFC-2859","source":"IETF/RFC-2859/RFC-2859.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 2991","folder":"IETF/RFC-2991","source":"IETF/RFC-2991/RFC-2991.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3248","folder":"IETF/RFC-3248","source":"IETF/RFC-3248/RFC-3248.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3662","folder":"IETF/RFC-3662","source":"IETF/RFC-3662/RFC-3662.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3763","folder":"IETF/RFC-3763","source":"IETF/RFC-3763/RFC-3763.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4222","folder":"IETF/RFC-4222","source":"IETF/RFC-4222/RFC-4222.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5594","folder":"IETF/RFC-5594","source":"IETF/RFC-5594/RFC-5594.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IETF RFC 2474 Differentiated services enhancements to the Internet protocol are\n intended to enable scalable service discrimination in the Internet\n without the need for per-flow state and signaling at every hop. A\n variety of services may be built from a small, well-defined set of\n building blocks which are deployed in network nodes. The services\n may be either end-to-end or intra-domain; they include both those\n that can satisfy quantitative performance requirements (e.g., peak\n bandwidth) and those based on relative performance (e.g., \"class\"\n differentiation). Services can be constructed by a combination of:\n\n - setting bits in an IP header field at network boundaries\n (autonomous system boundaries, internal administrative boundaries,\n or hosts),\n - using those bits to determine how packets are forwarded by the\n nodes inside the network, and\n - conditioning the marked packets at network boundaries 2474 delivery management path pid policies policy nested-reference unchanged"},{"id":"IETF RFC 2481","type":"specification","body":"IETF","designation":"RFC 2481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2481.txt","https://www.rfc-editor.org/rfc/rfc2481.pdf"],"folder":"IETF/RFC-2481","files":{"txt":{"path":"standards/IETF/RFC-2481/RFC-2481.txt","sha256":"062ff0678d00bddf2edee3e547d9925593d146048a42e5586e56b0ee2456961f"}},"tags":["nested-reference","unchanged"],"summary":"This note describes a proposed addition of ECN (Explicit Congestion\n Notification) to IP. TCP is currently the dominant transport\n protocol used in the Internet. We begin by describing TCP's use of\n packet drops as an indication of congestion. Next we argue that with\n the addition of active queue management (e.g., RED) to the Internet\n infrastructure, where routers detect congestion before the queue\n overflows, routers are no longer limited to packet drops as an\n indication of congestion. Routers could instead set a Congestion\n Experienced (CE) bit in the packet header of packets from ECN-capable\n transport protocols. We describe when the CE bit would be set in the\n routers, and describe what modifications would be needed to TCP to\n make it ECN-capable. Modifications to other transport protocols\n (e.g., unreliable unicast or multicast, reliable multicast, other\n reliable unicast transpor","scope_keywords":["2481","algorithm","algorithms","delivery","key","management","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2736","folder":"IETF/RFC-2736","source":"IETF/RFC-2736/RFC-2736.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null}],"search_text":"IETF RFC 2481 This note describes a proposed addition of ECN (Explicit Congestion\n Notification) to IP. TCP is currently the dominant transport\n protocol used in the Internet. We begin by describing TCP's use of\n packet drops as an indication of congestion. Next we argue that with\n the addition of active queue management (e.g., RED) to the Internet\n infrastructure, where routers detect congestion before the queue\n overflows, routers are no longer limited to packet drops as an\n indication of congestion. Routers could instead set a Congestion\n Experienced (CE) bit in the packet header of packets from ECN-capable\n transport protocols. We describe when the CE bit would be set in the\n routers, and describe what modifications would be needed to TCP to\n make it ECN-capable. Modifications to other transport protocols\n (e.g., unreliable unicast or multicast, reliable multicast, other\n reliable unicast transpor 2481 algorithm algorithms delivery key management path policies nested-reference unchanged"},{"id":"IETF RFC 2488","type":"specification","body":"IETF","designation":"RFC 2488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2488.txt","https://www.rfc-editor.org/rfc/rfc2488.pdf"],"folder":"IETF/RFC-2488","files":{"txt":{"path":"standards/IETF/RFC-2488/RFC-2488.txt","sha256":"fc953cb901e68415b02a1cd0474666392fc6a4e0f5dc62a5412614578ab6a4c8"}},"tags":["nested-reference","unchanged"],"summary":"The Transmission Control Protocol (TCP) provides reliable delivery of\n data across any network path, including network paths containing\n satellite channels. While TCP works over satellite channels there\n are several IETF standardized mechanisms that enable TCP to more\n effectively utilize the available capacity of the network path. This\n document outlines some of these TCP mitigations. At this time, all\n mitigations discussed in this document are IETF standards track\n mechanisms (or are compliant with IETF standards).\n\n1. Introduction\n\n Satellite channel characteristics may have an effect on the way\n transport protocols, such as the Transmission Control Protocol (TCP)\n [Pos81], behave. When protocols, such as TCP, perform poorly,\n channel utilization is low. While the performance of a transport\n protocol is important, it is not the only consideration when\n constructing a network containi","scope_keywords":["2488","delivery","license","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 2488 The Transmission Control Protocol (TCP) provides reliable delivery of\n data across any network path, including network paths containing\n satellite channels. While TCP works over satellite channels there\n are several IETF standardized mechanisms that enable TCP to more\n effectively utilize the available capacity of the network path. This\n document outlines some of these TCP mitigations. At this time, all\n mitigations discussed in this document are IETF standards track\n mechanisms (or are compliant with IETF standards).\n\n1. Introduction\n\n Satellite channel characteristics may have an effect on the way\n transport protocols, such as the Transmission Control Protocol (TCP)\n [Pos81], behave. When protocols, such as TCP, perform poorly,\n channel utilization is low. While the performance of a transport\n protocol is important, it is not the only consideration when\n constructing a network containi 2488 delivery license path nested-reference unchanged"},{"id":"IETF RFC 2525","type":"specification","body":"IETF","designation":"RFC 2525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2525.txt","https://www.rfc-editor.org/rfc/rfc2525.pdf"],"folder":"IETF/RFC-2525","files":{"txt":{"path":"standards/IETF/RFC-2525/RFC-2525.txt","sha256":"8d0eabdf67d02e7f7fda3da15698c9a9949fa4e7679d0c07fc669d8494593d07"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Paxson\nRequest for Comments: 2525 Editor\nCategory: Informational ACIRI / ICSI\n M. Allman\n NASA Glenn Research Center/Sterling Software\n S. Dawson\n Real-Time Computing Laboratory\n W. Fenner\n Xerox PARC\n J. Griner\n NASA Glenn Research Center\n I. Heavens\n Spider Software Ltd.\n K. Lahey\n NASA Ames Research Center/MRJ\n J. Semke\n Pittsburgh Supercomputing Center\n B. Volz\n Process Software Corporation\n March 1999\n\n Known TCP Implementation Problems\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. INTRODUCTION....................................................2\n 2. KNOWN IMPLEMENTATION PROBLEMS...................................3\n 2.1 No","scope_keywords":["2525","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 3143","folder":"IETF/RFC-3143","source":"IETF/RFC-3143/RFC-3143.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2525 Network Working Group V. Paxson\nRequest for Comments: 2525 Editor\nCategory: Informational ACIRI / ICSI\n M. Allman\n NASA Glenn Research Center/Sterling Software\n S. Dawson\n Real-Time Computing Laboratory\n W. Fenner\n Xerox PARC\n J. Griner\n NASA Glenn Research Center\n I. Heavens\n Spider Software Ltd.\n K. Lahey\n NASA Ames Research Center/MRJ\n J. Semke\n Pittsburgh Supercomputing Center\n B. Volz\n Process Software Corporation\n March 1999\n\n Known TCP Implementation Problems\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. INTRODUCTION....................................................2\n 2. KNOWN IMPLEMENTATION PROBLEMS...................................3\n 2.1 No 2525 management pid nested-reference unchanged"},{"id":"IETF RFC 2555","type":"specification","body":"IETF","designation":"RFC 2555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2555.txt","https://www.rfc-editor.org/rfc/rfc2555.pdf"],"folder":"IETF/RFC-2555","files":{"txt":{"path":"standards/IETF/RFC-2555/RFC-2555.txt","sha256":"19674b8ac509b825fca3a44bd90b1f1eddae8f2851aab28292fc4f7b40931088"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group RFC Editor, et al.\nRequest for Comments: 2555 USC/ISI\nCategory: Informational 7 April 1999\n\n 30 Years of RFCs\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction.................................................. 2\n 2. Reflections................................................... 2\n 3. The First Pebble: Publication of RFC 1........................ 3\n 4. RFCs - The Great Conversation................................. 5\n 5. Reflecting on 30 years of RFCs................................ 9\n 6. Favorite RFCs -- The First 30 Years...........................14\n 7. Security Considerations.......................................15\n 8.","scope_keywords":["2555","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null}],"search_text":"IETF RFC 2555 Network Working Group RFC Editor, et al.\nRequest for Comments: 2555 USC/ISI\nCategory: Informational 7 April 1999\n\n 30 Years of RFCs\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction.................................................. 2\n 2. Reflections................................................... 2\n 3. The First Pebble: Publication of RFC 1........................ 3\n 4. RFCs - The Great Conversation................................. 5\n 5. Reflecting on 30 years of RFCs................................ 9\n 6. Favorite RFCs -- The First 30 Years...........................14\n 7. Security Considerations.......................................15\n 8. 2555 key management nested-reference unchanged"},{"id":"IETF RFC 2581","type":"specification","body":"IETF","designation":"RFC 2581","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2581.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2581.txt","https://www.rfc-editor.org/rfc/rfc2581.pdf"],"folder":"IETF/RFC-2581","files":{"txt":{"path":"standards/IETF/RFC-2581/RFC-2581.txt","sha256":"5ccd4126e2044a897bd88a7eeeaebbd93eebbb87cec3fd862852f6a1ed935d7c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines TCP's four intertwined congestion control\n algorithms: slow start, congestion avoidance, fast retransmit, and\n fast recovery. In addition, the document specifies how TCP should\n begin transmission after a relatively long idle period, as well as\n discussing various acknowledgment generation methods.\n\n1. Introduction\n\n This document specifies four TCP [Pos81] congestion control\n algorithms: slow start, congestion avoidance, fast retransmit and\n fast recovery. These algorithms were devised in [Jac88] and [Jac90].\n Their use with TCP is standardized in [Bra89].\n\n This document is an update of [Ste97]. In addition to specifying the\n congestion control algorithms, this document specifies what TCP\n connections should do after a relatively long idle period, as well as\n specifying and clarifying some of the issues pertaining to TCP ACK\n generation.\n\n Note that [Ste94] provid","scope_keywords":["2581","algorithm","algorithms","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2582","folder":"IETF/RFC-2582","source":"IETF/RFC-2582/RFC-2582.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2861","folder":"IETF/RFC-2861","source":"IETF/RFC-2861/RFC-2861.txt","version":null},{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2988","folder":"IETF/RFC-2988","source":"IETF/RFC-2988/RFC-2988.txt","version":null},{"body":"IETF","designation":"RFC 2991","folder":"IETF/RFC-2991","source":"IETF/RFC-2991/RFC-2991.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3649","folder":"IETF/RFC-3649","source":"IETF/RFC-3649/RFC-3649.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3742","folder":"IETF/RFC-3742","source":"IETF/RFC-3742/RFC-3742.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2581 This document defines TCP's four intertwined congestion control\n algorithms: slow start, congestion avoidance, fast retransmit, and\n fast recovery. In addition, the document specifies how TCP should\n begin transmission after a relatively long idle period, as well as\n discussing various acknowledgment generation methods.\n\n1. Introduction\n\n This document specifies four TCP [Pos81] congestion control\n algorithms: slow start, congestion avoidance, fast retransmit and\n fast recovery. These algorithms were devised in [Jac88] and [Jac90].\n Their use with TCP is standardized in [Bra89].\n\n This document is an update of [Ste97]. In addition to specifying the\n congestion control algorithms, this document specifies what TCP\n connections should do after a relatively long idle period, as well as\n specifying and clarifying some of the issues pertaining to TCP ACK\n generation.\n\n Note that [Ste94] provid 2581 algorithm algorithms key path nested-reference unchanged"},{"id":"IETF RFC 2663","type":"specification","body":"IETF","designation":"RFC 2663","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2663.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2663.txt","https://www.rfc-editor.org/rfc/rfc2663.pdf"],"folder":"IETF/RFC-2663","files":{"txt":{"path":"standards/IETF/RFC-2663/RFC-2663.txt","sha256":"5da63886f46cc12237a23faebfb4f9037eb8da8375837041228f29cd1a251681"}},"tags":["nested-reference","unchanged"],"summary":"Network Address Translation is a method by which IP addresses are\n mapped from one realm to another, in an attempt to provide\n transparent routing to hosts. Traditionally, NAT devices are used to\n connect an isolated address realm with private unregistered addresses\n to an external realm with globally unique registered addresses. This\n document attempts to describe the operation of NAT devices and the\n associated considerations in general, and to define the terminology\n used to identify various flavors of NAT.\n\nSrisuresh & Holdrege Informational [Page 1]\n\f\nRFC 2663 NAT Terminology and Considerations August 1999\n\n1. Introduction and Overview\n\n The need for IP Address translation arises when a network's internal\n IP addresses cannot be used outside the network either because they\n are invalid for use outside, or because the internal addressing must\n be kept private from the external networ","scope_keywords":["2663","key","keys","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4084","folder":"IETF/RFC-4084","source":"IETF/RFC-4084/RFC-4084.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 2663 Network Address Translation is a method by which IP addresses are\n mapped from one realm to another, in an attempt to provide\n transparent routing to hosts. Traditionally, NAT devices are used to\n connect an isolated address realm with private unregistered addresses\n to an external realm with globally unique registered addresses. This\n document attempts to describe the operation of NAT devices and the\n associated considerations in general, and to define the terminology\n used to identify various flavors of NAT.\n\nSrisuresh & Holdrege Informational [Page 1]\n\f\nRFC 2663 NAT Terminology and Considerations August 1999\n\n1. Introduction and Overview\n\n The need for IP Address translation arises when a network's internal\n IP addresses cannot be used outside the network either because they\n are invalid for use outside, or because the internal addressing must\n be kept private from the external networ 2663 key keys registered nested-reference unchanged"},{"id":"IETF RFC 2678","type":"specification","body":"IETF","designation":"RFC 2678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2678.txt","https://www.rfc-editor.org/rfc/rfc2678.pdf"],"folder":"IETF/RFC-2678","files":{"txt":{"path":"standards/IETF/RFC-2678/RFC-2678.txt","sha256":"9d27a03ea230bb1698162391fda8fcd3ca90252d8b21c6cdfaba50c207278d91"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Mahdavi\nRequest for Comments: 2678 Pittsburgh Supercomputing Center\nObsoletes: 2498 V. Paxson\nCategory: Standards Track Lawrence Berkeley National Laboratory\n September 1999\n\n IPPM Metrics for Measuring Connectivity\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n Connectivity is the basic stuff from which the Internet is made.\n Therefore, metrics determining whether pairs of hosts (IP addresses)\n can reach each other must form the base of a measurement ","scope_keywords":["2678"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 2678 Network Working Group J. Mahdavi\nRequest for Comments: 2678 Pittsburgh Supercomputing Center\nObsoletes: 2498 V. Paxson\nCategory: Standards Track Lawrence Berkeley National Laboratory\n September 1999\n\n IPPM Metrics for Measuring Connectivity\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n Connectivity is the basic stuff from which the Internet is made.\n Therefore, metrics determining whether pairs of hosts (IP addresses)\n can reach each other must form the base of a measurement  2678 nested-reference unchanged"},{"id":"IETF RFC 2760","type":"specification","body":"IETF","designation":"RFC 2760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2760.txt","https://www.rfc-editor.org/rfc/rfc2760.pdf"],"folder":"IETF/RFC-2760","files":{"txt":{"path":"standards/IETF/RFC-2760/RFC-2760.txt","sha256":"f6d0207c30b9d83b3f5a563c926662c99c8fa27b746b1bef252d95a43c5d5c40"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines possible TCP enhancements that may allow TCP\n to better utilize the available bandwidth provided by networks\n containing satellite links. The algorithms and mechanisms outlined\n have not been judged to be mature enough to be recommended by the\n IETF. The goal of this document is to educate researchers as to the\n current work and progress being done in TCP research related to\n satellite networks.\n\nAllman, et al. Informational [Page 1]\n\f\nRFC 2760 Ongoing TCP Research Related to Satellites February 2000","scope_keywords":["2760","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2760 This document outlines possible TCP enhancements that may allow TCP\n to better utilize the available bandwidth provided by networks\n containing satellite links. The algorithms and mechanisms outlined\n have not been judged to be mature enough to be recommended by the\n IETF. The goal of this document is to educate researchers as to the\n current work and progress being done in TCP research related to\n satellite networks.\n\nAllman, et al. Informational [Page 1]\n\f\nRFC 2760 Ongoing TCP Research Related to Satellites February 2000 2760 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 2784","type":"specification","body":"IETF","designation":"RFC 2784","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2784.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2784.txt","https://www.rfc-editor.org/rfc/rfc2784.pdf"],"folder":"IETF/RFC-2784","files":{"txt":{"path":"standards/IETF/RFC-2784/RFC-2784.txt","sha256":"dad757f9b5eb51478e768295eb39df4b54c1f299eeb6e5c7bea080eb45556d58"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol for encapsulation of an arbitrary\n network layer protocol over another arbitrary network layer protocol.\n\n1. Introduction\n\n A number of different proposals [RFC1234, RFC1226] currently exist\n for the encapsulation of one protocol over another protocol. Other\n types of encapsulations [RFC1241, RFC1479] have been proposed for\n transporting IP over IP for policy purposes. This memo describes a\n protocol which is very similar to, but is more general than, the\n above proposals. In attempting to be more general, many protocol\n specific nuances have been ignored. The result is that this proposal\n may be less suitable for a situation where a specific \"X over Y\"\n encapsulation has been described. It is the attempt of this protocol\n to provide a simple, general purpose mechanism which reduces the\n problem of encapsulation from its current O(n^2) size to a more\n m","scope_keywords":["2784","algorithm","algorithms","delivery","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5640","folder":"IETF/RFC-5640","source":"IETF/RFC-5640/RFC-5640.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 2784 This document specifies a protocol for encapsulation of an arbitrary\n network layer protocol over another arbitrary network layer protocol.\n\n1. Introduction\n\n A number of different proposals [RFC1234, RFC1226] currently exist\n for the encapsulation of one protocol over another protocol. Other\n types of encapsulations [RFC1241, RFC1479] have been proposed for\n transporting IP over IP for policy purposes. This memo describes a\n protocol which is very similar to, but is more general than, the\n above proposals. In attempting to be more general, many protocol\n specific nuances have been ignored. The result is that this proposal\n may be less suitable for a situation where a specific \"X over Y\"\n encapsulation has been described. It is the attempt of this protocol\n to provide a simple, general purpose mechanism which reduces the\n problem of encapsulation from its current O(n^2) size to a more\n m 2784 algorithm algorithms delivery key policy nested-reference unchanged"},{"id":"IETF RFC 2893","type":"specification","body":"IETF","designation":"RFC 2893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2893.txt","https://www.rfc-editor.org/rfc/rfc2893.pdf"],"folder":"IETF/RFC-2893","files":{"txt":{"path":"standards/IETF/RFC-2893/RFC-2893.txt","sha256":"4090aee7fd9ccab9b01a5a70e4556d165736c157e119fb59aee39d0a2ab04576"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. These mechanisms include\n providing complete implementations of both versions of the Internet\n Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4\n routing infrastructures. They are designed to allow IPv6 nodes to\n maintain complete compatibility with IPv4, which should greatly\n simplify the deployment of IPv6 in the Internet, and facilitate the\n eventual transition of the entire Internet to IPv6. This document\n obsoletes RFC 1933.\n\nGilligan & Nordmark Standards Track [Page 1]\n\f\nRFC 2893 IPv6 Transition Mechanisms August 2000","scope_keywords":["2893","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3089","folder":"IETF/RFC-3089","source":"IETF/RFC-3089/RFC-3089.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2893 This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. These mechanisms include\n providing complete implementations of both versions of the Internet\n Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4\n routing infrastructures. They are designed to allow IPv6 nodes to\n maintain complete compatibility with IPv4, which should greatly\n simplify the deployment of IPv6 in the Internet, and facilitate the\n eventual transition of the entire Internet to IPv6. This document\n obsoletes RFC 1933.\n\nGilligan & Nordmark Standards Track [Page 1]\n\f\nRFC 2893 IPv6 Transition Mechanisms August 2000 2893 key nested-reference unchanged"},{"id":"IETF RFC 2914","type":"specification","body":"IETF","designation":"RFC 2914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2914.txt","https://www.rfc-editor.org/rfc/rfc2914.pdf"],"folder":"IETF/RFC-2914","files":{"txt":{"path":"standards/IETF/RFC-2914/RFC-2914.txt","sha256":"9fcf305067fd0075887028e8975bb8f6b1e451d1e9ba474d7e840c6dec2ddd38"}},"tags":["nested-reference","unchanged"],"summary":"The goal of this document is to explain the need for congestion\n control in the Internet, and to discuss what constitutes correct\n congestion control. One specific goal is to illustrate the dangers\n of neglecting to apply proper congestion control. A second goal is\n to discuss the role of the IETF in standardizing new congestion\n control protocols.\n\n1. Introduction\n\n This document draws heavily from earlier RFCs, in some cases\n reproducing entire sections of the text of earlier documents\n [RFC2309, RFC2357]. We have also borrowed heavily from earlier\n publications addressing the need for end-to-end congestion control\n [FF99].\n\n2. Current standards on congestion control\n\n IETF standards concerning end-to-end congestion control focus either\n on specific protocols (e.g., TCP [RFC2581], reliable multicast\n protocols [RFC2357]) or on the syntax and semantics of communications\n between the end","scope_keywords":["2914","algorithm","algorithms","key","keys","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3347","folder":"IETF/RFC-3347","source":"IETF/RFC-3347/RFC-3347.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 2914 The goal of this document is to explain the need for congestion\n control in the Internet, and to discuss what constitutes correct\n congestion control. One specific goal is to illustrate the dangers\n of neglecting to apply proper congestion control. A second goal is\n to discuss the role of the IETF in standardizing new congestion\n control protocols.\n\n1. Introduction\n\n This document draws heavily from earlier RFCs, in some cases\n reproducing entire sections of the text of earlier documents\n [RFC2309, RFC2357]. We have also borrowed heavily from earlier\n publications addressing the need for end-to-end congestion control\n [FF99].\n\n2. Current standards on congestion control\n\n IETF standards concerning end-to-end congestion control focus either\n on specific protocols (e.g., TCP [RFC2581], reliable multicast\n protocols [RFC2357]) or on the syntax and semantics of communications\n between the end 2914 algorithm algorithms key keys management path nested-reference unchanged"},{"id":"IETF RFC 2923","type":"specification","body":"IETF","designation":"RFC 2923","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2923.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2923.txt","https://www.rfc-editor.org/rfc/rfc2923.pdf"],"folder":"IETF/RFC-2923","files":{"txt":{"path":"standards/IETF/RFC-2923/RFC-2923.txt","sha256":"d71f88438b257d0f735276427afe0fcfa3084d19c9fc1d22036a5bc0d04a19f4"}},"tags":["nested-reference","unchanged"],"summary":"This memo catalogs several known Transmission Control Protocol (TCP)\n implementation problems dealing with Path Maximum Transmission Unit\n Discovery (PMTUD), including the long-standing black hole problem,\n stretch acknowlegements (ACKs) due to confusion between Maximum\n Segment Size (MSS) and segment size, and MSS advertisement based on\n PMTU.\n\n1. Introduction\n\n This memo catalogs several known TCP implementation problems dealing\n with Path MTU Discovery [RFC1191], including the long-standing black\n hole problem, stretch ACKs due to confusion between MSS and segment\n size, and MSS advertisement based on PMTU. The goal in doing so is\n to improve conditions in the existing Internet by enhancing the\n quality of current TCP/IP implementations.\n\n While Path MTU Discovery (PMTUD) can be used with any upper-layer\n protocol, it is most commonly used by TCP; this document does not\n attempt to tr","scope_keywords":["2923","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 2923 This memo catalogs several known Transmission Control Protocol (TCP)\n implementation problems dealing with Path Maximum Transmission Unit\n Discovery (PMTUD), including the long-standing black hole problem,\n stretch acknowlegements (ACKs) due to confusion between Maximum\n Segment Size (MSS) and segment size, and MSS advertisement based on\n PMTU.\n\n1. Introduction\n\n This memo catalogs several known TCP implementation problems dealing\n with Path MTU Discovery [RFC1191], including the long-standing black\n hole problem, stretch ACKs due to confusion between MSS and segment\n size, and MSS advertisement based on PMTU. The goal in doing so is\n to improve conditions in the existing Internet by enhancing the\n quality of current TCP/IP implementations.\n\n While Path MTU Discovery (PMTUD) can be used with any upper-layer\n protocol, it is most commonly used by TCP; this document does not\n attempt to tr 2923 path nested-reference unchanged"},{"id":"IETF RFC 2988","type":"specification","body":"IETF","designation":"RFC 2988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2988.txt","https://www.rfc-editor.org/rfc/rfc2988.pdf"],"folder":"IETF/RFC-2988","files":{"txt":{"path":"standards/IETF/RFC-2988/RFC-2988.txt","sha256":"474ab8c2a7553e4a02f618b9afc78413cdf5e45751a9ff78f4d93dc1b06bb762"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Paxson\nRequest for Comments: 2988 ACIRI\nCategory: Standards Track M. Allman\n NASA GRC/BBN\n November 2000\n\n Computing TCP's Retransmission Timer\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the standard algorithm that Transmission\n Control Protocol (TCP) senders are required to use to compute and\n manage their retransmission timer. It expands on the discussion in\n section 4.2.3.1 of RFC 1122 and upgrades the requirement of\n supporting t","scope_keywords":["2988","algorithm","algorithms","delivery","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3448","folder":"IETF/RFC-3448","source":"IETF/RFC-3448/RFC-3448.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2988 Network Working Group V. Paxson\nRequest for Comments: 2988 ACIRI\nCategory: Standards Track M. Allman\n NASA GRC/BBN\n November 2000\n\n Computing TCP's Retransmission Timer\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the standard algorithm that Transmission\n Control Protocol (TCP) senders are required to use to compute and\n manage their retransmission timer. It expands on the discussion in\n section 4.2.3.1 of RFC 1122 and upgrades the requirement of\n supporting t 2988 algorithm algorithms delivery key timestamp nested-reference unchanged"},{"id":"IETF RFC 3021","type":"specification","body":"IETF","designation":"RFC 3021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3021.txt","https://www.rfc-editor.org/rfc/rfc3021.pdf"],"folder":"IETF/RFC-3021","files":{"txt":{"path":"standards/IETF/RFC-3021/RFC-3021.txt","sha256":"e19bf6ce80f4d5c9f82c2b7c08802bf8a1b8f8f00fea348dffac1142646861e7"}},"tags":["nested-reference","unchanged"],"summary":"With ever-increasing pressure to conserve IP address space on the\n Internet, it makes sense to consider where relatively minor changes\n can be made to fielded practice to improve numbering efficiency. One\n such change, proposed by this document, is to halve the amount of\n address space assigned to point-to-point links (common throughout the\n Internet infrastructure) by allowing the use of 31-bit subnet masks\n in a very limited way.\n\n1. Introduction and Motivation\n\n The perceived problem of a lack of Internet addresses has driven a\n number of changes in address space usage and a number of different\n approaches to solving the problem:\n\n - More stringent address space allocation guidelines, enforced by the\n IANA and the regional address assignment authorities [RFC2050].\n\n - Use of Network Address Translators (NATs), where a small number of\n IANA-compliant addresses are shared by a larger po","scope_keywords":["3021","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null}],"search_text":"IETF RFC 3021 With ever-increasing pressure to conserve IP address space on the\n Internet, it makes sense to consider where relatively minor changes\n can be made to fielded practice to improve numbering efficiency. One\n such change, proposed by this document, is to halve the amount of\n address space assigned to point-to-point links (common throughout the\n Internet infrastructure) by allowing the use of 31-bit subnet masks\n in a very limited way.\n\n1. Introduction and Motivation\n\n The perceived problem of a lack of Internet addresses has driven a\n number of changes in address space usage and a number of different\n approaches to solving the problem:\n\n - More stringent address space allocation guidelines, enforced by the\n IANA and the regional address assignment authorities [RFC2050].\n\n - Use of Network Address Translators (NATs), where a small number of\n IANA-compliant addresses are shared by a larger po 3021 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 3022","type":"specification","body":"IETF","designation":"RFC 3022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3022.txt","https://www.rfc-editor.org/rfc/rfc3022.pdf"],"folder":"IETF/RFC-3022","files":{"txt":{"path":"standards/IETF/RFC-3022/RFC-3022.txt","sha256":"c57fe60c46eff630d4d82eece5bf624ba3ac80f16711e7acdb44a28e01331d86"}},"tags":["nested-reference","unchanged"],"summary":"Basic Network Address Translation or Basic NAT is a method by which\n IP addresses are mapped from one group to another, transparent to end\n users. Network Address Port Translation, or NAPT is a method by\n which many network addresses and their TCP/UDP (Transmission Control\n Protocol/User Datagram Protocol) ports are translated into a single\n network address and its TCP/UDP ports. Together, these two\n operations, referred to as traditional NAT, provide a mechanism to\n connect a realm with private addresses to an external realm with\n globally unique registered addresses.\n\n1. Introduction\n\n The need for IP Address translation arises when a network's internal\n IP addresses cannot be used outside the network either for privacy\n reasons or because they are invalid for use outside the network.\n\n Network topology outside a local domain can change in many ways.\n Customers may change providers, co","scope_keywords":["3022","algorithm","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7498","folder":"IETF/RFC-7498","source":"IETF/RFC-7498/RFC-7498.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 3022 Basic Network Address Translation or Basic NAT is a method by which\n IP addresses are mapped from one group to another, transparent to end\n users. Network Address Port Translation, or NAPT is a method by\n which many network addresses and their TCP/UDP (Transmission Control\n Protocol/User Datagram Protocol) ports are translated into a single\n network address and its TCP/UDP ports. Together, these two\n operations, referred to as traditional NAT, provide a mechanism to\n connect a realm with private addresses to an external realm with\n globally unique registered addresses.\n\n1. Introduction\n\n The need for IP Address translation arises when a network's internal\n IP addresses cannot be used outside the network either for privacy\n reasons or because they are invalid for use outside the network.\n\n Network topology outside a local domain can change in many ways.\n Customers may change providers, co 3022 algorithm key registered nested-reference unchanged"},{"id":"IETF RFC 3081","type":"specification","body":"IETF","designation":"RFC 3081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3081.txt","https://www.rfc-editor.org/rfc/rfc3081.pdf"],"folder":"IETF/RFC-3081","files":{"txt":{"path":"standards/IETF/RFC-3081/RFC-3081.txt","sha256":"96ae4ae73af7243944621c3cf5e08303fc7ae3ad6c9958d92c4c426e6b02e91c"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how a BEEP (Blocks Extensible Exchange Protocol)\n session is mapped onto a single TCP (Transmission Control Protocol)\n connection.","scope_keywords":["3081","crl","delivery","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null}],"search_text":"IETF RFC 3081 This memo describes how a BEEP (Blocks Extensible Exchange Protocol)\n session is mapped onto a single TCP (Transmission Control Protocol)\n connection. 3081 crl delivery key management nested-reference unchanged"},{"id":"IETF RFC 3155","type":"specification","body":"IETF","designation":"RFC 3155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3155.txt","https://www.rfc-editor.org/rfc/rfc3155.pdf"],"folder":"IETF/RFC-3155","files":{"txt":{"path":"standards/IETF/RFC-3155/RFC-3155.txt","sha256":"fc2a3ec7b3968d4b7ae1fc46c0434e5dc16046f08a2e6ba49b72e3716e5bdd50"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the specific TCP mechanisms that are\n problematic in environments with high uncorrected error rates, and\n discusses what can be done to mitigate the problems without\n introducing intermediate devices into the connection.","scope_keywords":["3155","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3155 This document discusses the specific TCP mechanisms that are\n problematic in environments with high uncorrected error rates, and\n discusses what can be done to mitigate the problems without\n introducing intermediate devices into the connection. 3155 path pid nested-reference unchanged"},{"id":"IETF RFC 3168","type":"specification","body":"IETF","designation":"RFC 3168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3168.txt","https://www.rfc-editor.org/rfc/rfc3168.pdf"],"folder":"IETF/RFC-3168","files":{"txt":{"path":"standards/IETF/RFC-3168/RFC-3168.txt","sha256":"35b437f1826b2624d6c5e7af2f047a6ba0a3110cd5559ffbd0cefdc8c3d87b76"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies the incorporation of ECN (Explicit Congestion\n Notification) to TCP and IP, including ECN's use of two bits in the\n IP header.","scope_keywords":["3168","attribute","attributes","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3448","folder":"IETF/RFC-3448","source":"IETF/RFC-3448/RFC-3448.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3540","folder":"IETF/RFC-3540","source":"IETF/RFC-3540/RFC-3540.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6789","folder":"IETF/RFC-6789","source":"IETF/RFC-6789/RFC-6789.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 3168 This memo specifies the incorporation of ECN (Explicit Congestion\n Notification) to TCP and IP, including ECN's use of two bits in the\n IP header. 3168 attribute attributes management path nested-reference unchanged"},{"id":"IETF RFC 3175","type":"specification","body":"IETF","designation":"RFC 3175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3175.txt","https://www.rfc-editor.org/rfc/rfc3175.pdf"],"folder":"IETF/RFC-3175","files":{"txt":{"path":"standards/IETF/RFC-3175/RFC-3175.txt","sha256":"a6b715e7e1df46a511eefc40ebf287021a30184cceb775bc74d620500d5683cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of a single RSVP (Resource\n ReSerVation Protocol) reservation to aggregate other RSVP\n reservations across a transit routing region, in a manner\n conceptually similar to the use of Virtual Paths in an ATM\n (Asynchronous Transfer Mode) network. It proposes a way to\n dynamically create the aggregate reservation, classify the traffic\n for which the aggregate reservation applies, determine how much\n bandwidth is needed to achieve the requirement, and recover the\n bandwidth when the sub-reservations are no longer required. It also\n contains recommendations concerning algorithms and policies for\n predictive reservations.\n\n1. Introduction\n\n A key problem in the design of RSVP version 1 [RSVP] is, as noted in\n its applicability statement, that it lacks facilities for aggregation\n of individual reserved sessions into a common class. The use of such\n aggregation is ","scope_keywords":["3175","algorithm","algorithms","key","path","policies","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 3175 This document describes the use of a single RSVP (Resource\n ReSerVation Protocol) reservation to aggregate other RSVP\n reservations across a transit routing region, in a manner\n conceptually similar to the use of Virtual Paths in an ATM\n (Asynchronous Transfer Mode) network. It proposes a way to\n dynamically create the aggregate reservation, classify the traffic\n for which the aggregate reservation applies, determine how much\n bandwidth is needed to achieve the requirement, and recover the\n bandwidth when the sub-reservations are no longer required. It also\n contains recommendations concerning algorithms and policies for\n predictive reservations.\n\n1. Introduction\n\n A key problem in the design of RSVP version 1 [RSVP] is, as noted in\n its applicability statement, that it lacks facilities for aggregation\n of individual reserved sessions into a common class. The use of such\n aggregation is  3175 algorithm algorithms key path policies tsp nested-reference unchanged"},{"id":"IETF RFC 3260","type":"specification","body":"IETF","designation":"RFC 3260","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3260.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3260.txt","https://www.rfc-editor.org/rfc/rfc3260.pdf"],"folder":"IETF/RFC-3260","files":{"txt":{"path":"standards/IETF/RFC-3260/RFC-3260.txt","sha256":"3ef70642bc35379b99c6f6ce0d440b022517fd6756b8a8b11b2ba17156b47037"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Grossman\nRequest for Comments: 3260 Motorola, Inc.\nUpdates: 2474, 2475, 2597 April 2002\nCategory: Informational\n\n New Terminology and Clarifications for Diffserv\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This memo captures Diffserv working group agreements concerning new\n and improved terminology, and provides minor technical\n clarifications. It is intended to update RFC 2474, RFC 2475 and RFC\n 2597. When RFCs 2474 and 2597 advance on the standards track, and\n RFC 2475 is updated, it is intended that the revisions in this memo\n will be incorporated, and that this memo will be obsoleted by the new\n RFCs.\n\n1. Introduction\n\n As the Diffse","scope_keywords":["3260","management","policy","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5693","folder":"IETF/RFC-5693","source":"IETF/RFC-5693/RFC-5693.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null}],"search_text":"IETF RFC 3260 Network Working Group D. Grossman\nRequest for Comments: 3260 Motorola, Inc.\nUpdates: 2474, 2475, 2597 April 2002\nCategory: Informational\n\n New Terminology and Clarifications for Diffserv\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This memo captures Diffserv working group agreements concerning new\n and improved terminology, and provides minor technical\n clarifications. It is intended to update RFC 2474, RFC 2475 and RFC\n 2597. When RFCs 2474 and 2597 advance on the standards track, and\n RFC 2475 is updated, it is intended that the revisions in this memo\n will be incorporated, and that this memo will be obsoleted by the new\n RFCs.\n\n1. Introduction\n\n As the Diffse 3260 management policy profile profiles nested-reference unchanged"},{"id":"IETF RFC 3360","type":"specification","body":"IETF","designation":"RFC 3360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3360.txt","https://www.rfc-editor.org/rfc/rfc3360.pdf"],"folder":"IETF/RFC-3360","files":{"txt":{"path":"standards/IETF/RFC-3360/RFC-3360.txt","sha256":"0e3b43fae66d1fcbdd0d53f3a2b25115508a826726ced829d9ea0be7be579de3"}},"tags":["nested-reference","unchanged"],"summary":"This document is being written because there are a number of\n firewalls in the Internet that inappropriately reset a TCP connection\n upon receiving certain TCP SYN packets, in particular, packets with\n flags set in the Reserved field of the TCP header. In this document\n we argue that this practice is not conformant with TCP standards, and\n is an inappropriate overloading of the semantics of the TCP reset.\n We also consider the longer-term consequences of this and similar\n actions as obstacles to the evolution of the Internet infrastructure.\n\n1. Introduction\n\n TCP uses the RST (Reset) bit in the TCP header to reset a TCP\n connection. Resets are appropriately sent in response to a\n connection request to a nonexistent connection, for example. The TCP\n receiver of the reset aborts the TCP connection, and notifies the\n application [RFC793, RFC1122, Ste94].\n\n Unfortunately, a number of firewal","scope_keywords":["3360"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3360 This document is being written because there are a number of\n firewalls in the Internet that inappropriately reset a TCP connection\n upon receiving certain TCP SYN packets, in particular, packets with\n flags set in the Reserved field of the TCP header. In this document\n we argue that this practice is not conformant with TCP standards, and\n is an inappropriate overloading of the semantics of the TCP reset.\n We also consider the longer-term consequences of this and similar\n actions as obstacles to the evolution of the Internet infrastructure.\n\n1. Introduction\n\n TCP uses the RST (Reset) bit in the TCP header to reset a TCP\n connection. Resets are appropriately sent in response to a\n connection request to a nonexistent connection, for example. The TCP\n receiver of the reset aborts the TCP connection, and notifies the\n application [RFC793, RFC1122, Ste94].\n\n Unfortunately, a number of firewal 3360 nested-reference unchanged"},{"id":"IETF RFC 3390","type":"specification","body":"IETF","designation":"RFC 3390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3390.txt","https://www.rfc-editor.org/rfc/rfc3390.pdf"],"folder":"IETF/RFC-3390","files":{"txt":{"path":"standards/IETF/RFC-3390/RFC-3390.txt","sha256":"d8a8e34fc773ad95a8e460c90db7c79035e8b187fc56f8236d35e8e26663375e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an optional standard for TCP to increase the\n permitted initial window from one or two segment(s) to roughly 4K\n bytes, replacing RFC 2414. It discusses the advantages and\n disadvantages of the higher initial window, and includes discussion\n of experiments and simulations showing that the higher initial window\n does not lead to congestion collapse. Finally, this document\n provides guidance on implementation issues.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1. TCP Modification\n\n This document obsoletes [RFC2414] and updates [RFC2581] and specifies\n an increase in the permitted upper bound for TCP's initial window\n from one or two segment(s) to between two and four segments. In most\n cases","scope_keywords":["3390","http","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3649","folder":"IETF/RFC-3649","source":"IETF/RFC-3649/RFC-3649.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null}],"search_text":"IETF RFC 3390 This document specifies an optional standard for TCP to increase the\n permitted initial window from one or two segment(s) to roughly 4K\n bytes, replacing RFC 2414. It discusses the advantages and\n disadvantages of the higher initial window, and includes discussion\n of experiments and simulations showing that the higher initial window\n does not lead to congestion collapse. Finally, this document\n provides guidance on implementation issues.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [RFC2119].\n\n1. TCP Modification\n\n This document obsoletes [RFC2414] and updates [RFC2581] and specifies\n an increase in the permitted upper bound for TCP's initial window\n from one or two segment(s) to between two and four segments. In most\n cases 3390 http key path nested-reference unchanged"},{"id":"IETF RFC 3449","type":"specification","body":"IETF","designation":"RFC 3449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3449.txt","https://www.rfc-editor.org/rfc/rfc3449.pdf"],"folder":"IETF/RFC-3449","files":{"txt":{"path":"standards/IETF/RFC-3449/RFC-3449.txt","sha256":"b78bd7a7ab56f16dbd0d9debfed358995343bfbcbe942c62d9e03a3117cb1e0b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes TCP performance problems that arise because\n of asymmetric effects. These problems arise in several access\n networks, including bandwidth-asymmetric networks and packet radio\n subnetworks, for different underlying reasons. However, the end\n result on TCP performance is the same in both cases: performance\n often degrades significantly because of imperfection and variability\n in the ACK feedback from the receiver to the sender.\n\n The document details several mitigations to these effects, which have\n either been proposed or evaluated in the literature, or are currently\n deployed in networks. These solutions use a combination of local\n link-layer techniques, subnetwork, and end-to-end mechanisms,\n consisting of: (i) techniques to manage the channel used for the\n upstream bottleneck link carrying the ACKs, typically using header\n compression or reducing the frequency o","scope_keywords":["3449","algorithm","algorithms","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 3449 This document describes TCP performance problems that arise because\n of asymmetric effects. These problems arise in several access\n networks, including bandwidth-asymmetric networks and packet radio\n subnetworks, for different underlying reasons. However, the end\n result on TCP performance is the same in both cases: performance\n often degrades significantly because of imperfection and variability\n in the ACK feedback from the receiver to the sender.\n\n The document details several mitigations to these effects, which have\n either been proposed or evaluated in the literature, or are currently\n deployed in networks. These solutions use a combination of local\n link-layer techniques, subnetwork, and end-to-end mechanisms,\n consisting of: (i) techniques to manage the channel used for the\n upstream bottleneck link carrying the ACKs, typically using header\n compression or reducing the frequency o 3449 algorithm algorithms management path nested-reference unchanged"},{"id":"IETF RFC 3465","type":"specification","body":"IETF","designation":"RFC 3465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3465.txt","https://www.rfc-editor.org/rfc/rfc3465.pdf"],"folder":"IETF/RFC-3465","files":{"txt":{"path":"standards/IETF/RFC-3465/RFC-3465.txt","sha256":"462f6c2c4989f60964ff715707414043d7b546277650c1225611ab530250dc2f"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a small modification to the way TCP increases\n its congestion window. Rather than the traditional method of\n increasing the congestion window by a constant amount for each\n arriving acknowledgment, the document suggests basing the increase on\n the number of previously unacknowledged bytes each ACK covers. This\n change improves the performance of TCP, as well as closes a security\n hole TCP receivers can use to induce the sender into increasing the\n sending rate too rapidly.\n\nTerminology\n\n Much of the language in this document is taken from [RFC2581].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n1 Introduction\n\n This document proposes a modification to the algorithm for increasing\n TCP's congestion window (cwnd) th","scope_keywords":["3465","algorithm","algorithms","key","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3742","folder":"IETF/RFC-3742","source":"IETF/RFC-3742/RFC-3742.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 3465 This document proposes a small modification to the way TCP increases\n its congestion window. Rather than the traditional method of\n increasing the congestion window by a constant amount for each\n arriving acknowledgment, the document suggests basing the increase on\n the number of previously unacknowledged bytes each ACK covers. This\n change improves the performance of TCP, as well as closes a security\n hole TCP receivers can use to induce the sender into increasing the\n sending rate too rapidly.\n\nTerminology\n\n Much of the language in this document is taken from [RFC2581].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n1 Introduction\n\n This document proposes a modification to the algorithm for increasing\n TCP's congestion window (cwnd) th 3465 algorithm algorithms key path pid nested-reference unchanged"},{"id":"IETF RFC 3481","type":"specification","body":"IETF","designation":"RFC 3481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3481.txt","https://www.rfc-editor.org/rfc/rfc3481.pdf"],"folder":"IETF/RFC-3481","files":{"txt":{"path":"standards/IETF/RFC-3481/RFC-3481.txt","sha256":"8d9e12c698a6ac0da890d21cdbac5d51d5cd8debc82854404289c00b097bbb51"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile for optimizing TCP to adapt so that\n it handles paths including second (2.5G) and third (3G) generation\n wireless networks. It describes the relevant characteristics of 2.5G\n and 3G networks, and specific features of example deployments of such\n networks. It then recommends TCP algorithm choices for nodes known\n to be starting or ending on such paths, and it also discusses open\n issues. The configuration options recommended in this document are\n commonly found in modern TCP stacks, and are widely available\n standards-track mechanisms that the community considers safe for use\n on the general Internet.\n\nInamura, et al. Best Current Practice [Page 1]\n\f\nRFC 3481 TCP over 2.5G/3G February 2003","scope_keywords":["3481","algorithm","key","path","profile","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3481 This document describes a profile for optimizing TCP to adapt so that\n it handles paths including second (2.5G) and third (3G) generation\n wireless networks. It describes the relevant characteristics of 2.5G\n and 3G networks, and specific features of example deployments of such\n networks. It then recommends TCP algorithm choices for nodes known\n to be starting or ending on such paths, and it also discusses open\n issues. The configuration options recommended in this document are\n commonly found in modern TCP stacks, and are widely available\n standards-track mechanisms that the community considers safe for use\n on the general Internet.\n\nInamura, et al. Best Current Practice [Page 1]\n\f\nRFC 3481 TCP over 2.5G/3G February 2003 3481 algorithm key path profile timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3522","type":"specification","body":"IETF","designation":"RFC 3522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3522.txt","https://www.rfc-editor.org/rfc/rfc3522.pdf"],"folder":"IETF/RFC-3522","files":{"txt":{"path":"standards/IETF/RFC-3522/RFC-3522.txt","sha256":"fb682c54bf036b18c9f75f6a6899b3b635b04faf52b324b9482f10961d4ebb6c"}},"tags":["nested-reference","unchanged"],"summary":"The Eifel detection algorithm allows a TCP sender to detect a\n posteriori whether it has entered loss recovery unnecessarily. It\n requires that the TCP Timestamps option defined in RFC 1323 be\n enabled for a connection. The Eifel detection algorithm makes use of\n the fact that the TCP Timestamps option eliminates the retransmission\n ambiguity in TCP. Based on the timestamp of the first acceptable ACK\n that arrives during loss recovery, it decides whether loss recovery\n was entered unnecessarily. The Eifel detection algorithm provides a\n basis for future TCP enhancements. This includes response algorithms\n to back out of loss recovery by restoring a TCP sender's congestion\n control state.\n\nTerminology\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [RFC","scope_keywords":["3522","algorithm","algorithms","key","path","risk","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null}],"search_text":"IETF RFC 3522 The Eifel detection algorithm allows a TCP sender to detect a\n posteriori whether it has entered loss recovery unnecessarily. It\n requires that the TCP Timestamps option defined in RFC 1323 be\n enabled for a connection. The Eifel detection algorithm makes use of\n the fact that the TCP Timestamps option eliminates the retransmission\n ambiguity in TCP. Based on the timestamp of the first acceptable ACK\n that arrives during loss recovery, it decides whether loss recovery\n was entered unnecessarily. The Eifel detection algorithm provides a\n basis for future TCP enhancements. This includes response algorithms\n to back out of loss recovery by restoring a TCP sender's congestion\n control state.\n\nTerminology\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [RFC 3522 algorithm algorithms key path risk timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3884","type":"specification","body":"IETF","designation":"RFC 3884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3884.txt","https://www.rfc-editor.org/rfc/rfc3884.pdf"],"folder":"IETF/RFC-3884","files":{"txt":{"path":"standards/IETF/RFC-3884/RFC-3884.txt","sha256":"70e44ea6d2a63c7a3d7a8c5f1b1821e3ee4292a7adb49c3864b2561c79c13eba"}},"tags":["nested-reference","unchanged"],"summary":"IPsec can secure the links of a multihop network to protect\n communication between trusted components, e.g., for a secure virtual\n network (VN), overlay, or virtual private network (VPN). Virtual\n links established by IPsec tunnel mode can conflict with routing and\n forwarding inside VNs because IP routing depends on references to\n interfaces and next-hop IP addresses. The IPsec tunnel mode\n specification is ambiguous on this issue, so even compliant\n implementations cannot be trusted to avoid conflicts. An alternative\n to tunnel mode uses non-IPsec IPIP encapsulation together with IPsec\n transport mode, which we call IIPtran. IPIP encapsulation occurs as\n a separate initial step, as the result of a forwarding lookup of the\n VN packet. IPsec transport mode processes the resulting (tunneled) IP\n packet with an SA determined through a security association database\n (SAD) match on the tunne","scope_keywords":["3884","key","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3884 IPsec can secure the links of a multihop network to protect\n communication between trusted components, e.g., for a secure virtual\n network (VN), overlay, or virtual private network (VPN). Virtual\n links established by IPsec tunnel mode can conflict with routing and\n forwarding inside VNs because IP routing depends on references to\n interfaces and next-hop IP addresses. The IPsec tunnel mode\n specification is ambiguous on this issue, so even compliant\n implementations cannot be trusted to avoid conflicts. An alternative\n to tunnel mode uses non-IPsec IPIP encapsulation together with IPsec\n transport mode, which we call IIPtran. IPIP encapsulation occurs as\n a separate initial step, as the result of a forwarding lookup of the\n VN packet. IPsec transport mode processes the resulting (tunneled) IP\n packet with an SA determined through a security association database\n (SAD) match on the tunne 3884 key path policy trust nested-reference unchanged"},{"id":"IETF RFC 4172","type":"specification","body":"IETF","designation":"RFC 4172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4172.txt","https://www.rfc-editor.org/rfc/rfc4172.pdf"],"folder":"IETF/RFC-4172","files":{"txt":{"path":"standards/IETF/RFC-4172/RFC-4172.txt","sha256":"0ec698c7847aaba8f4592eeeb57f921478ac0fb5c556ca83a829d511a69e80fa"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an architecture and a gateway-to-gateway\n protocol for the implementation of fibre channel fabric functionality\n over an IP network. This functionality is provided through TCP\n protocols for fibre channel frame transport and the distributed\n fabric services specified by the fibre channel standards. The\n architecture enables internetworking of fibre channel devices through\n gateway-accessed regions with the fault isolation properties of\n autonomous systems and the scalability of the IP network.","scope_keywords":["4172","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4172 This document specifies an architecture and a gateway-to-gateway\n protocol for the implementation of fibre channel fabric functionality\n over an IP network. This functionality is provided through TCP\n protocols for fibre channel frame transport and the distributed\n fabric services specified by the fibre channel standards. The\n architecture enables internetworking of fibre channel devices through\n gateway-accessed regions with the fault isolation properties of\n autonomous systems and the scalability of the IP network. 4172 authentication management nested-reference unchanged"},{"id":"IETF RFC 4293","type":"specification","body":"IETF","designation":"RFC 4293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4293.txt","https://www.rfc-editor.org/rfc/rfc4293.pdf"],"folder":"IETF/RFC-4293","files":{"txt":{"path":"standards/IETF/RFC-4293/RFC-4293.txt","sha256":"88d9bd93fd092b7eeb2db9a9a380d5e07301e58d7ec2d36c90247daf2392deff"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the Internet Protocol (IP) in an IP version independent manner.\n This memo obsoletes RFCs 2011, 2465, and 2466.\n\nRouthier, Ed. Standards Track [Page 1]\n\f\nRFC 4293 IP MIB April 2006","scope_keywords":["4293","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null}],"search_text":"IETF RFC 4293 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the Internet Protocol (IP) in an IP version independent manner.\n This memo obsoletes RFCs 2011, 2465, and 2466.\n\nRouthier, Ed. Standards Track [Page 1]\n\f\nRFC 4293 IP MIB April 2006 4293 management nested-reference unchanged"},{"id":"IETF RFC 4379","type":"specification","body":"IETF","designation":"RFC 4379","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4379.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4379.txt","https://www.rfc-editor.org/rfc/rfc4379.pdf"],"folder":"IETF/RFC-4379","files":{"txt":{"path":"standards/IETF/RFC-4379/RFC-4379.txt","sha256":"ffa783d3a8388ba9e7e28f03a3dc9e23f3133e62bfdd98e6391fe2ad3dd02116"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple and efficient mechanism that can be\n used to detect data plane failures in Multi-Protocol Label Switching\n (MPLS) Label Switched Paths (LSPs). There are two parts to this\n document: information carried in an MPLS \"echo request\" and \"echo\n reply\" for the purposes of fault detection and isolation, and\n mechanisms for reliably sending the echo reply.","scope_keywords":["4379","key","path","qualified","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null}],"search_text":"IETF RFC 4379 This document describes a simple and efficient mechanism that can be\n used to detect data plane failures in Multi-Protocol Label Switching\n (MPLS) Label Switched Paths (LSPs). There are two parts to this\n document: information carried in an MPLS \"echo request\" and \"echo\n reply\" for the purposes of fault detection and isolation, and\n mechanisms for reliably sending the echo reply. 4379 key path qualified validation nested-reference unchanged"},{"id":"IETF RFC 4443","type":"specification","body":"IETF","designation":"RFC 4443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4443.txt","https://www.rfc-editor.org/rfc/rfc4443.pdf"],"folder":"IETF/RFC-4443","files":{"txt":{"path":"standards/IETF/RFC-4443/RFC-4443.txt","sha256":"f20d1de8878e1142000bfeaa3ad1b0540fab7653a395cf7b07e81d2da2f650bf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the format of a set of control messages used\n in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the\n Internet Control Message Protocol for Internet Protocol version 6\n (IPv6).\n\nConta, et al. Standards Track [Page 1]\n\f\nRFC 4443 ICMPv6 (ICMP for IPv6) March 2006","scope_keywords":["4443","authentication","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 4443 This document describes the format of a set of control messages used\n in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the\n Internet Control Message Protocol for Internet Protocol version 6\n (IPv6).\n\nConta, et al. Standards Track [Page 1]\n\f\nRFC 4443 ICMPv6 (ICMP for IPv6) March 2006 4443 authentication key path subject nested-reference unchanged"},{"id":"IETF RFC 4459","type":"specification","body":"IETF","designation":"RFC 4459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4459.txt","https://www.rfc-editor.org/rfc/rfc4459.pdf"],"folder":"IETF/RFC-4459","files":{"txt":{"path":"standards/IETF/RFC-4459/RFC-4459.txt","sha256":"7e56697808c2cb1d366e7a936322798c822315f200eb92f425e6433b33d4747a"}},"tags":["nested-reference","unchanged"],"summary":"Tunneling techniques such as IP-in-IP when deployed in the middle of\n the network, typically between routers, have certain issues regarding\n how large packets can be handled: whether such packets would be\n fragmented and reassembled (and how), whether Path MTU Discovery\n would be used, or how this scenario could be operationally avoided.\n This memo justifies why this is a common, non-trivial problem, and\n goes on to describe the different solutions and their characteristics\n at some length.","scope_keywords":["4459","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 4459 Tunneling techniques such as IP-in-IP when deployed in the middle of\n the network, typically between routers, have certain issues regarding\n how large packets can be handled: whether such packets would be\n fragmented and reassembled (and how), whether Path MTU Discovery\n would be used, or how this scenario could be operationally avoided.\n This memo justifies why this is a common, non-trivial problem, and\n goes on to describe the different solutions and their characteristics\n at some length. 4459 path nested-reference unchanged"},{"id":"IETF RFC 4460","type":"specification","body":"IETF","designation":"RFC 4460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4460.txt","https://www.rfc-editor.org/rfc/rfc4460.pdf"],"folder":"IETF/RFC-4460","files":{"txt":{"path":"standards/IETF/RFC-4460/RFC-4460.txt","sha256":"f4bfd2c90a5a7bfc9bb8ad28a662dde7594a958cae1c8329d98976717fdf09cb"}},"tags":["nested-reference","unchanged"],"summary":"This document is a compilation of issues found during six\n interoperability events and 5 years of experience with implementing,\n testing, and using Stream Control Transmission Protocol (SCTP) along\n with the suggested fixes. This document provides deltas to RFC 2960\n and is organized in a time-based way. The issues are listed in the\n order they were brought up. Because some text is changed several\n times, the last delta in the text is the one that should be applied.\n In addition to the delta, a description of the problem and the\n details of the solution are also provided.","scope_keywords":["4460","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null}],"search_text":"IETF RFC 4460 This document is a compilation of issues found during six\n interoperability events and 5 years of experience with implementing,\n testing, and using Stream Control Transmission Protocol (SCTP) along\n with the suggested fixes. This document provides deltas to RFC 2960\n and is organized in a time-based way. The issues are listed in the\n order they were brought up. Because some text is changed several\n times, the last delta in the text is the one that should be applied.\n In addition to the delta, a description of the problem and the\n details of the solution are also provided. 4460 path nested-reference unchanged"},{"id":"IETF RFC 4653","type":"specification","body":"IETF","designation":"RFC 4653","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4653.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4653.txt","https://www.rfc-editor.org/rfc/rfc4653.pdf"],"folder":"IETF/RFC-4653","files":{"txt":{"path":"standards/IETF/RFC-4653/RFC-4653.txt","sha256":"2259023ea3c162f77234cf913d486d7eecac00a9dccff38e91f262efad29b7c7"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Non-Congestion Robustness (NCR) for TCP. In\n the absence of explicit congestion notification from the network, TCP\n uses loss as an indication of congestion. One of the ways TCP\n detects loss is using the arrival of three duplicate acknowledgments.\n However, this heuristic is not always correct, notably in the case\n when network paths reorder segments (for whatever reason), resulting\n in degraded performance. TCP-NCR is designed to mitigate this\n degraded performance by increasing the number of duplicate\n acknowledgments required to trigger loss recovery, based on the\n current state of the connection, in an effort to better disambiguate\n true segment loss from segment reordering. This document specifies\n the changes to TCP, as well as the costs and benefits of these\n modifications.\n\nBhandarkar, et al. Experimental [Page 1]\n\f\nRFC 4653 Improving the Robustness of TC","scope_keywords":["4653","algorithm","algorithms","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null}],"search_text":"IETF RFC 4653 This document specifies Non-Congestion Robustness (NCR) for TCP. In\n the absence of explicit congestion notification from the network, TCP\n uses loss as an indication of congestion. One of the ways TCP\n detects loss is using the arrival of three duplicate acknowledgments.\n However, this heuristic is not always correct, notably in the case\n when network paths reorder segments (for whatever reason), resulting\n in degraded performance. TCP-NCR is designed to mitigate this\n degraded performance by increasing the number of duplicate\n acknowledgments required to trigger loss recovery, based on the\n current state of the connection, in an effort to better disambiguate\n true segment loss from segment reordering. This document specifies\n the changes to TCP, as well as the costs and benefits of these\n modifications.\n\nBhandarkar, et al. Experimental [Page 1]\n\f\nRFC 4653 Improving the Robustness of TC 4653 algorithm algorithms delivery path nested-reference unchanged"},{"id":"IETF RFC 4943","type":"specification","body":"IETF","designation":"RFC 4943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4943.txt","https://www.rfc-editor.org/rfc/rfc4943.pdf"],"folder":"IETF/RFC-4943","files":{"txt":{"path":"standards/IETF/RFC-4943/RFC-4943.txt","sha256":"dceeb9f2f41cf07d212b72039f609f6a2e469eb3434edc488b127b947ce4d161"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the historical and background information\n behind the removal of the \"on-link assumption\" from the conceptual\n host sending algorithm defined in Neighbor Discovery for IP Version 6\n (IPv6). According to the algorithm as originally described, when a\n host's default router list is empty, the host assumes that all\n destinations are on-link. This is particularly problematic with\n IPv6-capable nodes that do not have off-link IPv6 connectivity (e.g.,\n no default router). This document describes how making this\n assumption causes problems and how these problems outweigh the\n benefits of this part of the conceptual sending algorithm.","scope_keywords":["4943","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 4943 This document describes the historical and background information\n behind the removal of the \"on-link assumption\" from the conceptual\n host sending algorithm defined in Neighbor Discovery for IP Version 6\n (IPv6). According to the algorithm as originally described, when a\n host's default router list is empty, the host assumes that all\n destinations are on-link. This is particularly problematic with\n IPv6-capable nodes that do not have off-link IPv6 connectivity (e.g.,\n no default router). This document describes how making this\n assumption causes problems and how these problems outweigh the\n benefits of this part of the conceptual sending algorithm. 4943 algorithm nested-reference unchanged"},{"id":"IETF RFC 4948","type":"specification","body":"IETF","designation":"RFC 4948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4948.txt","https://www.rfc-editor.org/rfc/rfc4948.pdf"],"folder":"IETF/RFC-4948","files":{"txt":{"path":"standards/IETF/RFC-4948/RFC-4948.txt","sha256":"5b7b4599e6c883bcadc53474210c9236ce767b95b122f0fb001de86885812945"}},"tags":["nested-reference","unchanged"],"summary":"This document reports the outcome of a workshop held by the Internet\n Architecture Board (IAB) on Unwanted Internet Traffic. The workshop\n was held on March 9-10, 2006 at USC/ISI in Marina del Rey, CA, USA.\n The primary goal of the workshop was to foster interchange between\n the operator, standards, and research communities on the topic of\n unwanted traffic, as manifested in, for example, Distributed Denial\n of Service (DDoS) attacks, spam, and phishing, to gain understandings\n on the ultimate sources of these unwanted traffic, and to assess\n their impact and the effectiveness of existing solutions. It was\n also a goal of the workshop to identify engineering and research\n topics that could be undertaken by the IAB, the IETF, the IRTF, and\n the network research and development community at large to develop\n effective countermeasures against the unwanted traffic.\n\nAndersson, et al. Informa","scope_keywords":["4948","driving","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 4948 This document reports the outcome of a workshop held by the Internet\n Architecture Board (IAB) on Unwanted Internet Traffic. The workshop\n was held on March 9-10, 2006 at USC/ISI in Marina del Rey, CA, USA.\n The primary goal of the workshop was to foster interchange between\n the operator, standards, and research communities on the topic of\n unwanted traffic, as manifested in, for example, Distributed Denial\n of Service (DDoS) attacks, spam, and phishing, to gain understandings\n on the ultimate sources of these unwanted traffic, and to assess\n their impact and the effectiveness of existing solutions. It was\n also a goal of the workshop to identify engineering and research\n topics that could be undertaken by the IAB, the IETF, the IRTF, and\n the network research and development community at large to develop\n effective countermeasures against the unwanted traffic.\n\nAndersson, et al. Informa 4948 driving policy trust nested-reference unchanged"},{"id":"IETF RFC 4953","type":"specification","body":"IETF","designation":"RFC 4953","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4953.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4953.txt","https://www.rfc-editor.org/rfc/rfc4953.pdf"],"folder":"IETF/RFC-4953","files":{"txt":{"path":"standards/IETF/RFC-4953/RFC-4953.txt","sha256":"3b4adc4e91dbb706b3878e308e4559523618876b50ea4f1f98e7f89bb70b6d46"}},"tags":["nested-reference","unchanged"],"summary":"Recent analysis of potential attacks on core Internet infrastructure\n indicates an increased vulnerability of TCP connections to spurious\n resets (RSTs), sent with forged IP source addresses (spoofing). TCP\n has always been susceptible to such RST spoofing attacks, which were\n indirectly protected by checking that the RST sequence number was\n inside the current receive window, as well as via the obfuscation of\n TCP endpoint and port numbers. For pairs of well-known endpoints\n often over predictable port pairs, such as BGP or between web servers\n and well-known large-scale caches, increases in the path bandwidth-\n delay product of a connection have sufficiently increased the receive\n window space that off-path third parties can brute-force generate a\n viable RST sequence number. The susceptibility to attack increases\n with the square of the bandwidth, and thus presents a significant\n vuln","scope_keywords":["4953","authentication","certificate","key","path","pid","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null}],"search_text":"IETF RFC 4953 Recent analysis of potential attacks on core Internet infrastructure\n indicates an increased vulnerability of TCP connections to spurious\n resets (RSTs), sent with forged IP source addresses (spoofing). TCP\n has always been susceptible to such RST spoofing attacks, which were\n indirectly protected by checking that the RST sequence number was\n inside the current receive window, as well as via the obfuscation of\n TCP endpoint and port numbers. For pairs of well-known endpoints\n often over predictable port pairs, such as BGP or between web servers\n and well-known large-scale caches, increases in the path bandwidth-\n delay product of a connection have sufficiently increased the receive\n window space that off-path third parties can brute-force generate a\n viable RST sequence number. The susceptibility to attack increases\n with the square of the bandwidth, and thus presents a significant\n vuln 4953 authentication certificate key path pid timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5044","type":"specification","body":"IETF","designation":"RFC 5044","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5044.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5044.txt","https://www.rfc-editor.org/rfc/rfc5044.pdf"],"folder":"IETF/RFC-5044","files":{"txt":{"path":"standards/IETF/RFC-5044/RFC-5044.txt","sha256":"84b06c7ba6943477df897e93b9a89ff2af3d2cc33e61b6674691910deba9e8b7"}},"tags":["nested-reference","unchanged"],"summary":"Marker PDU Aligned Framing (MPA) is designed to work as an\n \"adaptation layer\" between TCP and the Direct Data Placement protocol\n (DDP) as described in RFC 5041. It preserves the reliable, in-order\n delivery of TCP, while adding the preservation of higher-level\n protocol record boundaries that DDP requires. MPA is fully compliant\n with applicable TCP RFCs and can be utilized with existing TCP\n implementations. MPA also supports integrated implementations that\n combine TCP, MPA and DDP to reduce buffering requirements in the\n implementation and improve performance at the system level.\n\nCulley, et al. Standards Track [Page 1]\n\f\nRFC 5044 MPA Framing for TCP October 2007","scope_keywords":["5044","delivery","identification","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5044 Marker PDU Aligned Framing (MPA) is designed to work as an\n \"adaptation layer\" between TCP and the Direct Data Placement protocol\n (DDP) as described in RFC 5041. It preserves the reliable, in-order\n delivery of TCP, while adding the preservation of higher-level\n protocol record boundaries that DDP requires. MPA is fully compliant\n with applicable TCP RFCs and can be utilized with existing TCP\n implementations. MPA also supports integrated implementations that\n combine TCP, MPA and DDP to reduce buffering requirements in the\n implementation and improve performance at the system level.\n\nCulley, et al. Standards Track [Page 1]\n\f\nRFC 5044 MPA Framing for TCP October 2007 5044 delivery identification preservation nested-reference unchanged"},{"id":"IETF RFC 5061","type":"specification","body":"IETF","designation":"RFC 5061","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5061.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5061.txt","https://www.rfc-editor.org/rfc/rfc5061.pdf"],"folder":"IETF/RFC-5061","files":{"txt":{"path":"standards/IETF/RFC-5061/RFC-5061.txt","sha256":"0ff56098eeb34fff7c4eb2b66b3c805cb27e854c05662cf5519b1f4ebb44b0c1"}},"tags":["nested-reference","unchanged"],"summary":"A local host may have multiple points of attachment to the Internet,\n giving it a degree of fault tolerance from hardware failures. Stream\n Control Transmission Protocol (SCTP) (RFC 4960) was developed to take\n full advantage of such a multi-homed host to provide a fast failover\n and association survivability in the face of such hardware failures.\n This document describes an extension to SCTP that will allow an SCTP\n stack to dynamically add an IP address to an SCTP association,\n dynamically delete an IP address from an SCTP association, and to\n request to set the primary address the peer will use when sending to\n an endpoint.\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 5061 SCTP Dynamic Address Reconfiguration September 2007","scope_keywords":["5061","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null}],"search_text":"IETF RFC 5061 A local host may have multiple points of attachment to the Internet,\n giving it a degree of fault tolerance from hardware failures. Stream\n Control Transmission Protocol (SCTP) (RFC 4960) was developed to take\n full advantage of such a multi-homed host to provide a fast failover\n and association survivability in the face of such hardware failures.\n This document describes an extension to SCTP that will allow an SCTP\n stack to dynamically add an IP address to an SCTP association,\n dynamically delete an IP address from an SCTP association, and to\n request to set the primary address the peer will use when sending to\n an endpoint.\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 5061 SCTP Dynamic Address Reconfiguration September 2007 5061 authorization key nested-reference unchanged"},{"id":"IETF RFC 5118","type":"specification","body":"IETF","designation":"RFC 5118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5118.txt","https://www.rfc-editor.org/rfc/rfc5118.pdf"],"folder":"IETF/RFC-5118","files":{"txt":{"path":"standards/IETF/RFC-5118/RFC-5118.txt","sha256":"56a76623496c2b834646b39a89c30aa8d1922fdc9e6a9e463e118a636ae1e55e"}},"tags":["nested-reference","unchanged"],"summary":"This document provides examples of Session Initiation Protocol (SIP)\n test messages designed to exercise and \"torture\" the code of an\n IPv6-enabled SIP implementation.\n\nGurbani, et al. Informational [Page 1]\n\f\nRFC 5118 SIP IPv6 Torture Tests February 2008","scope_keywords":["5118","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null}],"search_text":"IETF RFC 5118 This document provides examples of Session Initiation Protocol (SIP)\n test messages designed to exercise and \"torture\" the code of an\n IPv6-enabled SIP implementation.\n\nGurbani, et al. Informational [Page 1]\n\f\nRFC 5118 SIP IPv6 Torture Tests February 2008 5118 presentation nested-reference unchanged"},{"id":"IETF RFC 5204","type":"specification","body":"IETF","designation":"RFC 5204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5204.txt","https://www.rfc-editor.org/rfc/rfc5204.pdf"],"folder":"IETF/RFC-5204","files":{"txt":{"path":"standards/IETF/RFC-5204/RFC-5204.txt","sha256":"fd0d43eec9228471a1763da02779e97b4c3fbf08951dfb0d157abe9912f2dfb4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a rendezvous extension for the Host Identity\n Protocol (HIP). The rendezvous extension extends HIP and the HIP\n registration extension for initiating communication between HIP nodes\n via HIP rendezvous servers. Rendezvous servers improve reachability\n and operation when HIP nodes are multi-homed or mobile.\n\nLaganier & Eggert Experimental [Page 1]\n\f\nRFC 5204 HIP Rendezvous Extension April 2008","scope_keywords":["5204","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null}],"search_text":"IETF RFC 5204 This document defines a rendezvous extension for the Host Identity\n Protocol (HIP). The rendezvous extension extends HIP and the HIP\n registration extension for initiating communication between HIP nodes\n via HIP rendezvous servers. Rendezvous servers improve reachability\n and operation when HIP nodes are multi-homed or mobile.\n\nLaganier & Eggert Experimental [Page 1]\n\f\nRFC 5204 HIP Rendezvous Extension April 2008 5204 key registered nested-reference unchanged"},{"id":"IETF RFC 5383","type":"specification","body":"IETF","designation":"RFC 5383","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5383.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5383.txt","https://www.rfc-editor.org/rfc/rfc5383.pdf"],"folder":"IETF/RFC-5383","files":{"txt":{"path":"standards/IETF/RFC-5383/RFC-5383.txt","sha256":"46ba1c5fc70954672f250c7760e034d1034d1695bf27ae3b450ca50d08d502c2"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses deployment issues and describes requirements\n for successful deployment of mobile email that are implicit in the\n IETF lemonade documents.","scope_keywords":["5383","http","key","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null}],"search_text":"IETF RFC 5383 This document discusses deployment issues and describes requirements\n for successful deployment of mobile email that are implicit in the\n IETF lemonade documents. 5383 http key profile trust nested-reference unchanged"},{"id":"IETF RFC 5508","type":"specification","body":"IETF","designation":"RFC 5508","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5508.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5508.txt","https://www.rfc-editor.org/rfc/rfc5508.pdf"],"folder":"IETF/RFC-5508","files":{"txt":{"path":"standards/IETF/RFC-5508/RFC-5508.txt","sha256":"89dd10c7b88610cec8c2a605e928822fd3c2e591a81382ed8c1c2ad2e26493d3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the behavioral properties required of the\n Network Address Translator (NAT) devices in conjunction with the\n Internet Control Message Protocol (ICMP). The objective of this memo\n is to make NAT devices more predictable and compatible with diverse\n application protocols that traverse the devices. Companion documents\n provide behavioral recommendations specific to TCP, UDP, and other\n protocols.","scope_keywords":["5508","http","license","policies","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 5508 This document specifies the behavioral properties required of the\n Network Address Translator (NAT) devices in conjunction with the\n Internet Control Message Protocol (ICMP). The objective of this memo\n is to make NAT devices more predictable and compatible with diverse\n application protocols that traverse the devices. Companion documents\n provide behavioral recommendations specific to TCP, UDP, and other\n protocols. 5508 http license policies policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5534","type":"specification","body":"IETF","designation":"RFC 5534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5534.txt","https://www.rfc-editor.org/rfc/rfc5534.pdf"],"folder":"IETF/RFC-5534","files":{"txt":{"path":"standards/IETF/RFC-5534/RFC-5534.txt","sha256":"483e091148c2b872996ec4458fce08bfbeff308a310ec04b75333f52cc8aca37"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how the level 3 multihoming Shim6 protocol\n (Shim6) detects failures between two communicating nodes. It also\n specifies an exploration protocol for switching to another pair of\n interfaces and/or addresses between the same nodes if a failure\n occurs and an operational pair can be found.\n\nArkko & Van Beijnum Standards Track [Page 1]\n\f\nRFC 5534 Failure Detection/Exploration Protocol June 2009","scope_keywords":["5534","http","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null}],"search_text":"IETF RFC 5534 This document specifies how the level 3 multihoming Shim6 protocol\n (Shim6) detects failures between two communicating nodes. It also\n specifies an exploration protocol for switching to another pair of\n interfaces and/or addresses between the same nodes if a failure\n occurs and an operational pair can be found.\n\nArkko & Van Beijnum Standards Track [Page 1]\n\f\nRFC 5534 Failure Detection/Exploration Protocol June 2009 5534 http license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5595","type":"specification","body":"IETF","designation":"RFC 5595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5595.txt","https://www.rfc-editor.org/rfc/rfc5595.pdf"],"folder":"IETF/RFC-5595","files":{"txt":{"path":"standards/IETF/RFC-5595/RFC-5595.txt","sha256":"d9be7d57af48aeb4befcb1202505ff4db7dfdcf2c9ca22641be186d154be8daa"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of Service Codes by the Datagram\n Congestion Control Protocol, RFC 4340. It motivates the setting of a\n Service Code by applications. Service Codes provide a method to\n identify the intended service/application to process a DCCP\n connection request. This provides improved flexibility in the use\n and assignment of port numbers for connection multiplexing. The use\n of a DCCP Service Code can also enable more explicit coordination of\n services with middleboxes (e.g., network address translators and\n firewalls). This document updates the specification provided in RFC\n 4340.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization st","scope_keywords":["5595","hash","http","license","management","profile","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null}],"search_text":"IETF RFC 5595 This document describes the usage of Service Codes by the Datagram\n Congestion Control Protocol, RFC 4340. It motivates the setting of a\n Service Code by applications. Service Codes provide a method to\n identify the intended service/application to process a DCCP\n connection request. This provides improved flexibility in the use\n and assignment of port numbers for connection multiplexing. The use\n of a DCCP Service Code can also enable more explicit coordination of\n services with middleboxes (e.g., network address translators and\n firewalls). This document updates the specification provided in RFC\n 4340.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization st 5595 hash http license management profile registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5681","type":"specification","body":"IETF","designation":"RFC 5681","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5681.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5681.txt","https://www.rfc-editor.org/rfc/rfc5681.pdf"],"folder":"IETF/RFC-5681","files":{"txt":{"path":"standards/IETF/RFC-5681/RFC-5681.txt","sha256":"a2d99a2421d5c57b248394f26ba44fc364aa546680fbf10ff0aa7034dad8b87d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines TCP's four intertwined congestion control\n algorithms: slow start, congestion avoidance, fast retransmit, and\n fast recovery. In addition, the document specifies how TCP should\n begin transmission after a relatively long idle period, as well as\n discussing various acknowledgment generation methods. This document\n obsoletes RFC 2581.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust'","scope_keywords":["5681","algorithm","algorithms","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 5681 This document defines TCP's four intertwined congestion control\n algorithms: slow start, congestion avoidance, fast retransmit, and\n fast recovery. In addition, the document specifies how TCP should\n begin transmission after a relatively long idle period, as well as\n discussing various acknowledgment generation methods. This document\n obsoletes RFC 2581.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust' 5681 algorithm algorithms http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5884","type":"specification","body":"IETF","designation":"RFC 5884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5884.txt","https://www.rfc-editor.org/rfc/rfc5884.pdf"],"folder":"IETF/RFC-5884","files":{"txt":{"path":"standards/IETF/RFC-5884/RFC-5884.txt","sha256":"d089f18784648837377c41f775f8d60ddcaf8e5cc687a3f358facebaf45b3d18"}},"tags":["nested-reference","unchanged"],"summary":"One desirable application of Bidirectional Forwarding Detection (BFD)\n is to detect a Multiprotocol Label Switching (MPLS) Label Switched\n Path (LSP) data plane failure. LSP Ping is an existing mechanism for\n detecting MPLS data plane failures and for verifying the MPLS LSP\n data plane against the control plane. BFD can be used for the\n former, but not for the latter. However, the control plane\n processing required for BFD Control packets is relatively smaller\n than the processing required for LSP Ping messages. A combination of\n LSP Ping and BFD can be used to provide faster data plane failure\n detection and/or make it possible to provide such detection on a\n greater number of LSPs. This document describes the applicability of\n BFD in relation to LSP Ping for this application. It also describes\n procedures for using BFD in this environment.\n\nStatus of This Memo\n\n This is an Internet Sta","scope_keywords":["5884","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5884 One desirable application of Bidirectional Forwarding Detection (BFD)\n is to detect a Multiprotocol Label Switching (MPLS) Label Switched\n Path (LSP) data plane failure. LSP Ping is an existing mechanism for\n detecting MPLS data plane failures and for verifying the MPLS LSP\n data plane against the control plane. BFD can be used for the\n former, but not for the latter. However, the control plane\n processing required for BFD Control packets is relatively smaller\n than the processing required for LSP Ping messages. A combination of\n LSP Ping and BFD can be used to provide faster data plane failure\n detection and/or make it possible to provide such detection on a\n greater number of LSPs. This document describes the applicability of\n BFD in relation to LSP Ping for this application. It also describes\n procedures for using BFD in this environment.\n\nStatus of This Memo\n\n This is an Internet Sta 5884 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5925","type":"specification","body":"IETF","designation":"RFC 5925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5925.txt","https://www.rfc-editor.org/rfc/rfc5925.pdf"],"folder":"IETF/RFC-5925","files":{"txt":{"path":"standards/IETF/RFC-5925/RFC-5925.txt","sha256":"2519e9a740c21ed5a675211104ddd21b9e3888438f7fb7e7887356804ec647e7"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the TCP Authentication Option (TCP-AO), which\n obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO\n specifies the use of stronger Message Authentication Codes (MACs),\n protects against replays even for long-lived TCP connections, and\n provides more details on the association of security with TCP\n connections than TCP MD5. TCP-AO is compatible with either a static\n Master Key Tuple (MKT) configuration or an external, out-of-band MKT\n management mechanism; in either case, TCP-AO also protects\n connections when using the same MKT across repeated instances of a\n connection, using traffic keys derived from the MKT, and coordinates\n MKT changes between endpoints. The result is intended to support\n current infrastructure uses of TCP MD5, such as to protect long-lived\n connections (as used, e.g., in BGP and LDP), and to support a larger\n set of MACs with ","scope_keywords":["5925","algorithm","algorithms","authentication","hash","http","key","keys","license","management","pki","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 5925 This document specifies the TCP Authentication Option (TCP-AO), which\n obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO\n specifies the use of stronger Message Authentication Codes (MACs),\n protects against replays even for long-lived TCP connections, and\n provides more details on the association of security with TCP\n connections than TCP MD5. TCP-AO is compatible with either a static\n Master Key Tuple (MKT) configuration or an external, out-of-band MKT\n management mechanism; in either case, TCP-AO also protects\n connections when using the same MKT across repeated instances of a\n connection, using traffic keys derived from the MKT, and coordinates\n MKT changes between endpoints. The result is intended to support\n current infrastructure uses of TCP MD5, such as to protect long-lived\n connections (as used, e.g., in BGP and LDP), and to support a larger\n set of MACs with  5925 algorithm algorithms authentication hash http key keys license management pki signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5971","type":"specification","body":"IETF","designation":"RFC 5971","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5971.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5971.txt","https://www.rfc-editor.org/rfc/rfc5971.pdf"],"folder":"IETF/RFC-5971","files":{"txt":{"path":"standards/IETF/RFC-5971/RFC-5971.txt","sha256":"a2f395363f2c391db51f78569e5a7438dac48fa32a836c473b556115a161c86a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies protocol stacks for the routing and transport\n of per-flow signalling messages along the path taken by that flow\n through the network. The design uses existing transport and security\n protocols under a common messaging layer, the General Internet\n Signalling Transport (GIST), which provides a common service for\n diverse signalling applications. GIST does not handle signalling\n application state itself, but manages its own internal state and the\n configuration of the underlying transport and security protocols to\n enable the transfer of messages in both directions along the flow\n path. The combination of GIST and the lower layer transport and\n security protocols provides a solution for the base protocol\n component of the \"Next Steps in Signalling\" (NSIS) framework.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publish","scope_keywords":["5971","authentication","http","license","path","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5971 This document specifies protocol stacks for the routing and transport\n of per-flow signalling messages along the path taken by that flow\n through the network. The design uses existing transport and security\n protocols under a common messaging layer, the General Internet\n Signalling Transport (GIST), which provides a common service for\n diverse signalling applications. GIST does not handle signalling\n application state itself, but manages its own internal state and the\n configuration of the underlying transport and security protocols to\n enable the transfer of messages in both directions along the flow\n path. The combination of GIST and the lower layer transport and\n security protocols provides a solution for the base protocol\n component of the \"Next Steps in Signalling\" (NSIS) framework.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publish 5971 authentication http license path pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6013","type":"specification","body":"IETF","designation":"RFC 6013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6013.txt","https://www.rfc-editor.org/rfc/rfc6013.pdf"],"folder":"IETF/RFC-6013","files":{"txt":{"path":"standards/IETF/RFC-6013/RFC-6013.txt","sha256":"f287aa6add91d6c238f4722578680d513ca03eb66d7c0eba0c34acc22e3f7bb5"}},"tags":["nested-reference","unchanged"],"summary":"TCP Cookie Transactions (TCPCT) deter spoofing of connections and\n prevent resource exhaustion, eliminating Responder (server) state\n during the initial handshake. The Initiator (client) has sole\n responsibility for ensuring required delays between connections. The\n cookie exchange may carry data, limited to inhibit amplification and\n reflection denial of service attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor ","scope_keywords":["6013","authentication","http","key","license","pid","signature","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6013 TCP Cookie Transactions (TCPCT) deter spoofing of connections and\n prevent resource exhaustion, eliminating Responder (server) state\n during the initial handshake. The Initiator (client) has sole\n responsibility for ensuring required delays between connections. The\n cookie exchange may carry data, limited to inhibit amplification and\n reflection denial of service attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n document at its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor  6013 authentication http key license pid signature subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 6204","type":"specification","body":"IETF","designation":"RFC 6204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6204.txt","https://www.rfc-editor.org/rfc/rfc6204.pdf"],"folder":"IETF/RFC-6204","files":{"txt":{"path":"standards/IETF/RFC-6204/RFC-6204.txt","sha256":"e20cca0bb60d58390ce82fb9d918f4346eccd187a3f7e9948a3bee5041ce8c6b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies requirements for an IPv6 Customer Edge (CE)\n router. Specifically, the current version of this document focuses\n on the basic provisioning of an IPv6 CE router and the provisioning\n of IPv6 hosts attached to it.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6204.","scope_keywords":["6204","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null}],"search_text":"IETF RFC 6204 This document specifies requirements for an IPv6 Customer Edge (CE)\n router. Specifically, the current version of this document focuses\n on the basic provisioning of an IPv6 CE router and the provisioning\n of IPv6 hosts attached to it.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6204. 6204 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6298","type":"specification","body":"IETF","designation":"RFC 6298","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6298.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6298.txt","https://www.rfc-editor.org/rfc/rfc6298.pdf"],"folder":"IETF/RFC-6298","files":{"txt":{"path":"standards/IETF/RFC-6298/RFC-6298.txt","sha256":"f3a6d937c0a7653bd431fdbbdcd7920f4e9d9cdb6134fa9db7a74b90d215edf6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the standard algorithm that Transmission\n Control Protocol (TCP) senders are required to use to compute and\n manage their retransmission timer. It expands on the discussion in\n Section 4.2.3.1 of RFC 1122 and upgrades the requirement of\n supporting the algorithm from a SHOULD to a MUST. This document\n obsoletes RFC 2988.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/","scope_keywords":["6298","algorithm","algorithms","delivery","http","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 6298 This document defines the standard algorithm that Transmission\n Control Protocol (TCP) senders are required to use to compute and\n manage their retransmission timer. It expands on the discussion in\n Section 4.2.3.1 of RFC 1122 and upgrades the requirement of\n supporting the algorithm from a SHOULD to a MUST. This document\n obsoletes RFC 2988.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/ 6298 algorithm algorithms delivery http key license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6419","type":"specification","body":"IETF","designation":"RFC 6419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6419.txt","https://www.rfc-editor.org/rfc/rfc6419.pdf"],"folder":"IETF/RFC-6419","files":{"txt":{"path":"standards/IETF/RFC-6419/RFC-6419.txt","sha256":"22ef64ec624d81737e825d504a6f6c49f23059bbe9b8793f9aa2180e8611325e"}},"tags":["nested-reference","unchanged"],"summary":"An increasing number of hosts are operating in multiple-interface\n environments. This document summarizes current practices in this\n area and describes in detail how some common operating systems cope\n with challenges that ensue from this context.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i","scope_keywords":["6419","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 6419 An increasing number of hosts are operating in multiple-interface\n environments. This document summarizes current practices in this\n area and describes in detail how some common operating systems cope\n with challenges that ensue from this context.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i 6419 http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6540","type":"specification","body":"IETF","designation":"RFC 6540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6540.txt","https://www.rfc-editor.org/rfc/rfc6540.pdf"],"folder":"IETF/RFC-6540","files":{"txt":{"path":"standards/IETF/RFC-6540/RFC-6540.txt","sha256":"bd31b0a955bf86bf1edfd094f9be22fbb09b6097c6662d4625d845b4afe278ca"}},"tags":["nested-reference","unchanged"],"summary":"Given the global lack of available IPv4 space, and limitations in\n IPv4 extension and transition technologies, this document advises\n that IPv6 support is no longer considered optional. It also cautions\n that there are places in existing IETF documents where the term \"IP\"\n is used in a way that could be misunderstood by implementers as the\n term \"IP\" becomes a generic that can mean IPv4 + IPv6, IPv6-only, or\n IPv4-only, depending on context and application.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of t","scope_keywords":["6540","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 6540 Given the global lack of available IPv4 space, and limitations in\n IPv4 extension and transition technologies, this document advises\n that IPv6 support is no longer considered optional. It also cautions\n that there are places in existing IETF documents where the term \"IP\"\n is used in a way that could be misunderstood by implementers as the\n term \"IP\" becomes a generic that can mean IPv4 + IPv6, IPv6-only, or\n IPv4-only, depending on context and application.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of t 6540 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6691","type":"specification","body":"IETF","designation":"RFC 6691","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6691.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6691.txt","https://www.rfc-editor.org/rfc/rfc6691.pdf"],"folder":"IETF/RFC-6691","files":{"txt":{"path":"standards/IETF/RFC-6691/RFC-6691.txt","sha256":"0b53ce864c12726523911a0b70c9a0637e464ea636d6637df031f3e2f36a69a8"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses what value to use with the TCP Maximum Segment\n Size (MSS) option, and updates RFC 879 and RFC 2385.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6691.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights ","scope_keywords":["6691","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null}],"search_text":"IETF RFC 6691 This memo discusses what value to use with the TCP Maximum Segment\n Size (MSS) option, and updates RFC 879 and RFC 2385.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6691.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights  6691 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6760","type":"specification","body":"IETF","designation":"RFC 6760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6760.txt","https://www.rfc-editor.org/rfc/rfc6760.pdf"],"folder":"IETF/RFC-6760","files":{"txt":{"path":"standards/IETF/RFC-6760/RFC-6760.txt","sha256":"c9d71232635e3d7dbccb92c2dc6407258c94ae319570a17d3ffe6b2800754077"}},"tags":["nested-reference","unchanged"],"summary":"One of the goals of the authors of Multicast DNS (mDNS) and DNS-Based\n Service Discovery (DNS-SD) was to retire AppleTalk and the AppleTalk\n Name Binding Protocol (NBP) and to replace them with an IP-based\n solution. This document presents a brief overview of the\n capabilities of AppleTalk NBP and outlines the properties required of\n an IP-based replacement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status","scope_keywords":["6760","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null}],"search_text":"IETF RFC 6760 One of the goals of the authors of Multicast DNS (mDNS) and DNS-Based\n Service Discovery (DNS-SD) was to retire AppleTalk and the AppleTalk\n Name Binding Protocol (NBP) and to replace them with an IP-based\n solution. This document presents a brief overview of the\n capabilities of AppleTalk NBP and outlines the properties required of\n an IP-based replacement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status 6760 http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6792","type":"specification","body":"IETF","designation":"RFC 6792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6792.txt","https://www.rfc-editor.org/rfc/rfc6792.pdf"],"folder":"IETF/RFC-6792","files":{"txt":{"path":"standards/IETF/RFC-6792/RFC-6792.txt","sha256":"0802608d8179833275add186728bd338fdbc93652014e9d1aa5b843480db95ef"}},"tags":["nested-reference","unchanged"],"summary":"This memo proposes an extensible Real-time Transport Protocol (RTP)\n monitoring framework for extending the RTP Control Protocol (RTCP)\n with a new RTCP Extended Reports (XR) block type to report new\n metrics regarding media transmission or reception quality. In this\n framework, a new XR block should contain a single metric or a small\n number of metrics relevant to a single parameter of interest or\n concern, rather than containing a number of metrics that attempt to\n provide full coverage of all those parameters of concern to a\n specific application. Applications may then \"mix and match\" to\n create a set of blocks that cover their set of concerns. Where\n possible, a specific block should be designed to be reusable across\n more than one application, for example, for all of voice, streaming\n audio, and video.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specifica","scope_keywords":["6792","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 6792 This memo proposes an extensible Real-time Transport Protocol (RTP)\n monitoring framework for extending the RTP Control Protocol (RTCP)\n with a new RTCP Extended Reports (XR) block type to report new\n metrics regarding media transmission or reception quality. In this\n framework, a new XR block should contain a single metric or a small\n number of metrics relevant to a single parameter of interest or\n concern, rather than containing a number of metrics that attempt to\n provide full coverage of all those parameters of concern to a\n specific application. Applications may then \"mix and match\" to\n create a set of blocks that cover their set of concerns. Where\n possible, a specific block should be designed to be reusable across\n more than one application, for example, for all of voice, streaming\n audio, and video.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specifica 6792 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6824","type":"specification","body":"IETF","designation":"RFC 6824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6824.txt","https://www.rfc-editor.org/rfc/rfc6824.pdf"],"folder":"IETF/RFC-6824","files":{"txt":{"path":"standards/IETF/RFC-6824/RFC-6824.txt","sha256":"6b54b4031378c330a1e7250ee8cff3ad49422c4ea814bfb88bccfcc6e7075f5f"}},"tags":["nested-reference","unchanged"],"summary":"TCP/IP communication is currently restricted to a single path per\n connection, yet multiple paths often exist between peers. The\n simultaneous use of these multiple paths for a TCP/IP session would\n improve resource usage within the network and, thus, improve user\n experience through higher throughput and improved resilience to\n network failure.\n\n Multipath TCP provides the ability to simultaneously use multiple\n paths between peers. This document presents a set of extensions to\n traditional TCP to support multipath operation. The protocol offers\n the same type of service to applications as TCP (i.e., reliable\n bytestream), and it provides the components necessary to establish\n and use multiple TCP flows across potentially disjoint paths.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, a","scope_keywords":["6824","authentication","http","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null}],"search_text":"IETF RFC 6824 TCP/IP communication is currently restricted to a single path per\n connection, yet multiple paths often exist between peers. The\n simultaneous use of these multiple paths for a TCP/IP session would\n improve resource usage within the network and, thus, improve user\n experience through higher throughput and improved resilience to\n network failure.\n\n Multipath TCP provides the ability to simultaneously use multiple\n paths between peers. This document presents a set of extensions to\n traditional TCP to support multipath operation. The protocol offers\n the same type of service to applications as TCP (i.e., reliable\n bytestream), and it provides the components necessary to establish\n and use multiple TCP flows across potentially disjoint paths.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, a 6824 authentication http license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6864","type":"specification","body":"IETF","designation":"RFC 6864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6864.txt","https://www.rfc-editor.org/rfc/rfc6864.pdf"],"folder":"IETF/RFC-6864","files":{"txt":{"path":"standards/IETF/RFC-6864/RFC-6864.txt","sha256":"e00ff443857166e5b26deecfdc77a0a1c5ff17fc87a6a8c50b020ce7f4d516d9"}},"tags":["nested-reference","unchanged"],"summary":"The IPv4 Identification (ID) field enables fragmentation and\n reassembly and, as currently specified, is required to be unique\n within the maximum lifetime for all datagrams with a given source\n address/destination address/protocol tuple. If enforced, this\n uniqueness requirement would limit all connections to 6.4 Mbps for\n typical datagram sizes. Because individual connections commonly\n exceed this speed, it is clear that existing systems violate the\n current specification. This document updates the specification of\n the IPv4 ID field in RFCs 791, 1122, and 2003 to more closely reflect\n current practice and to more closely match IPv6 so that the field's\n value is defined only when a datagram is actually fragmented. It\n also discusses the impact of these changes on how datagrams are used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of","scope_keywords":["6864","http","identification","key","license","mdl","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null}],"search_text":"IETF RFC 6864 The IPv4 Identification (ID) field enables fragmentation and\n reassembly and, as currently specified, is required to be unique\n within the maximum lifetime for all datagrams with a given source\n address/destination address/protocol tuple. If enforced, this\n uniqueness requirement would limit all connections to 6.4 Mbps for\n typical datagram sizes. Because individual connections commonly\n exceed this speed, it is clear that existing systems violate the\n current specification. This document updates the specification of\n the IPv4 ID field in RFCs 791, 1122, and 2003 to more closely reflect\n current practice and to more closely match IPv6 so that the field's\n value is defined only when a datagram is actually fragmented. It\n also discusses the impact of these changes on how datagrams are used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of 6864 http identification key license mdl subject trust nested-reference unchanged"},{"id":"IETF RFC 6897","type":"specification","body":"IETF","designation":"RFC 6897","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6897.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6897.txt","https://www.rfc-editor.org/rfc/rfc6897.pdf"],"folder":"IETF/RFC-6897","files":{"txt":{"path":"standards/IETF/RFC-6897/RFC-6897.txt","sha256":"453d85e088ed86b50f0bcf154c00fbe41c5ddd6bb8398e52c0640658503cda10"}},"tags":["nested-reference","unchanged"],"summary":"Multipath TCP (MPTCP) adds the capability of using multiple paths to\n a regular TCP session. Even though it is designed to be totally\n backward compatible to applications, the data transport differs\n compared to regular TCP, and there are several additional degrees of\n freedom that applications may wish to exploit. This document\n summarizes the impact that MPTCP may have on applications, such as\n changes in performance. Furthermore, it discusses compatibility\n issues of MPTCP in combination with non-MPTCP-aware applications.\n Finally, the document describes a basic application interface that is\n a simple extension of TCP's interface for MPTCP-aware applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co","scope_keywords":["6897","algorithm","http","license","management","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6897 Multipath TCP (MPTCP) adds the capability of using multiple paths to\n a regular TCP session. Even though it is designed to be totally\n backward compatible to applications, the data transport differs\n compared to regular TCP, and there are several additional degrees of\n freedom that applications may wish to exploit. This document\n summarizes the impact that MPTCP may have on applications, such as\n changes in performance. Furthermore, it discusses compatibility\n issues of MPTCP in combination with non-MPTCP-aware applications.\n Finally, the document describes a basic application interface that is\n a simple extension of TCP's interface for MPTCP-aware applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co 6897 algorithm http license management path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7084","type":"specification","body":"IETF","designation":"RFC 7084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7084.txt","https://www.rfc-editor.org/rfc/rfc7084.pdf"],"folder":"IETF/RFC-7084","files":{"txt":{"path":"standards/IETF/RFC-7084/RFC-7084.txt","sha256":"3027c196b80729778dd4eccd62f0cffa8181f9bf73d1355bfd710d6def4d8dab"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies requirements for an IPv6 Customer Edge (CE)\n router. Specifically, the current version of this document focuses\n on the basic provisioning of an IPv6 CE router and the provisioning\n of IPv6 hosts attached to it. The document also covers IP transition\n technologies. Two transition technologies in RFC 5969's IPv6 Rapid\n Deployment on IPv4 Infrastructures (6rd) and RFC 6333's Dual-Stack\n Lite (DS-Lite) are covered in the document. The document obsoletes\n RFC 6204.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved b","scope_keywords":["7084","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7084 This document specifies requirements for an IPv6 Customer Edge (CE)\n router. Specifically, the current version of this document focuses\n on the basic provisioning of an IPv6 CE router and the provisioning\n of IPv6 hosts attached to it. The document also covers IP transition\n technologies. Two transition technologies in RFC 5969's IPv6 Rapid\n Deployment on IPv4 Infrastructures (6rd) and RFC 6333's Dual-Stack\n Lite (DS-Lite) are covered in the document. The document obsoletes\n RFC 6204.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved b 7084 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7754","type":"specification","body":"IETF","designation":"RFC 7754","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7754.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7754.txt","https://www.rfc-editor.org/rfc/rfc7754.pdf"],"folder":"IETF/RFC-7754","files":{"txt":{"path":"standards/IETF/RFC-7754/RFC-7754.txt","sha256":"1a66669da169235aa7b62472570ad6735724e81cc502c08747e4ca06e0f70fc0"}},"tags":["nested-reference","unchanged"],"summary":"The Internet is structured to be an open communications medium. This\n openness is one of the key underpinnings of Internet innovation, but\n it can also allow communications that may be viewed as undesirable by\n certain parties. Thus, as the Internet has grown, so have mechanisms\n to limit the extent and impact of abusive or objectionable\n communications. Recently, there has been an increasing emphasis on\n \"blocking\" and \"filtering\", the active prevention of such\n communications. This document examines several technical approaches\n to Internet blocking and filtering in terms of their alignment with\n the overall Internet architecture. When it is possible to do so, the\n approach to blocking and filtering that is most coherent with the\n Internet architecture is to inform endpoints about potentially\n undesirable services, so that the communicants can avoid engaging in\n abusive or objectionabl","scope_keywords":["7754","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 7754 The Internet is structured to be an open communications medium. This\n openness is one of the key underpinnings of Internet innovation, but\n it can also allow communications that may be viewed as undesirable by\n certain parties. Thus, as the Internet has grown, so have mechanisms\n to limit the extent and impact of abusive or objectionable\n communications. Recently, there has been an increasing emphasis on\n \"blocking\" and \"filtering\", the active prevention of such\n communications. This document examines several technical approaches\n to Internet blocking and filtering in terms of their alignment with\n the overall Internet architecture. When it is possible to do so, the\n approach to blocking and filtering that is most coherent with the\n Internet architecture is to inform endpoints about potentially\n undesirable services, so that the communicants can avoid engaging in\n abusive or objectionabl 7754 http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 8201","type":"specification","body":"IETF","designation":"RFC 8201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8201.txt","https://www.rfc-editor.org/rfc/rfc8201.pdf"],"folder":"IETF/RFC-8201","files":{"txt":{"path":"standards/IETF/RFC-8201/RFC-8201.txt","sha256":"96c2ea7ac1bf5810f6b817d4ac372a35f68231d2bd0e2675740f1268eb9ac752"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Path MTU Discovery (PMTUD) for IP version 6.\n It is largely derived from RFC 1191, which describes Path MTU\n Discovery for IP version 4. It obsoletes RFC 1981.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8201.\n\nMcCann, et al. Standards Track [Page 1]\n\f\nRFC 8201 IPv6 Path MTU Discovery July 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons ","scope_keywords":["8201","delivery","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 8201 This document describes Path MTU Discovery (PMTUD) for IP version 6.\n It is largely derived from RFC 1191, which describes Path MTU\n Discovery for IP version 4. It obsoletes RFC 1981.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8201.\n\nMcCann, et al. Standards Track [Page 1]\n\f\nRFC 8201 IPv6 Path MTU Discovery July 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons  8201 delivery http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8250","type":"specification","body":"IETF","designation":"RFC 8250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8250.txt","https://www.rfc-editor.org/rfc/rfc8250.pdf"],"folder":"IETF/RFC-8250","files":{"txt":{"path":"standards/IETF/RFC-8250/RFC-8250.txt","sha256":"e3642401a18d57f85488f98252f6dfc540dce441fcf659367c10d3642074c16e"}},"tags":["nested-reference","unchanged"],"summary":"To assess performance problems, this document describes optional\n headers embedded in each packet that provide sequence numbers and\n timing information as a basis for measurements. Such measurements\n may be interpreted in real time or after the fact. This document\n specifies the Performance and Diagnostic Metrics (PDM) Destination\n Options header. The field limits, calculations, and usage in\n measurement of PDM are included in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this documen","scope_keywords":["8250","http","https","key","license","presentation","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 8250 To assess performance problems, this document describes optional\n headers embedded in each packet that provide sequence numbers and\n timing information as a basis for measurements. Such measurements\n may be interpreted in real time or after the fact. This document\n specifies the Performance and Diagnostic Metrics (PDM) Destination\n Options header. The field limits, calculations, and usage in\n measurement of PDM are included in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this documen 8250 http https key license presentation subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 8783","type":"specification","body":"IETF","designation":"RFC 8783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8783.txt","https://www.rfc-editor.org/rfc/rfc8783.pdf"],"folder":"IETF/RFC-8783","files":{"pdf":{"path":"standards/IETF/RFC-8783/RFC-8783.pdf","sha256":"da2851cffa2bae87349e5b21ffb13978df874e743ee51a9f46f057ee838b9658"},"txt":{"path":"standards/IETF/RFC-8783/RFC-8783.txt","sha256":"fda9862637ca8f5e21e56e83e7ac79cfc14f3242efbb98cb9cd552c64ac2102e"}},"tags":["nested-reference","unchanged"],"summary":"The document specifies a Distributed Denial-of-Service Open Threat\n Signaling (DOTS) data channel used for bulk exchange of data that\n cannot easily or appropriately communicated through the DOTS signal\n channel under attack conditions.\n\n This is a companion document to \"Distributed Denial-of-Service Open\n Threat Signaling (DOTS) Signal Channel Specification\" (RFC 8782).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht","scope_keywords":["8783","http","https","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8903","folder":"IETF/RFC-8903","source":"IETF/RFC-8903/RFC-8903.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8783 The document specifies a Distributed Denial-of-Service Open Threat\n Signaling (DOTS) data channel used for bulk exchange of data that\n cannot easily or appropriately communicated through the DOTS signal\n channel under attack conditions.\n\n This is a companion document to \"Distributed Denial-of-Service Open\n Threat Signaling (DOTS) Signal Channel Specification\" (RFC 8782).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht 8783 http https key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8831","type":"specification","body":"IETF","designation":"RFC 8831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8831.txt","https://www.rfc-editor.org/rfc/rfc8831.pdf"],"folder":"IETF/RFC-8831","files":{"pdf":{"path":"standards/IETF/RFC-8831/RFC-8831.pdf","sha256":"6518eed024a10253ff89a331b43fa5f26ea70be0f365ed9b35f5883cabc5b9ee"},"txt":{"path":"standards/IETF/RFC-8831/RFC-8831.txt","sha256":"86bec13ce9ebb28dfea37ad2ea2ccd771ab7adb9a95668ed8736eee2b028ea5c"}},"tags":["nested-reference","unchanged"],"summary":"The WebRTC framework specifies protocol support for direct,\n interactive, rich communication using audio, video, and data between\n two peers' web browsers. This document specifies the non-media data\n transport aspects of the WebRTC framework. It provides an\n architectural overview of how the Stream Control Transmission\n Protocol (SCTP) is used in the WebRTC context as a generic transport\n service that allows web browsers to exchange generic data from peer\n to peer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the curren","scope_keywords":["8831","authentication","delivery","http","https","key","license","management","policies","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 8831 The WebRTC framework specifies protocol support for direct,\n interactive, rich communication using audio, video, and data between\n two peers' web browsers. This document specifies the non-media data\n transport aspects of the WebRTC framework. It provides an\n architectural overview of how the Stream Control Transmission\n Protocol (SCTP) is used in the WebRTC context as a generic transport\n service that allows web browsers to exchange generic data from peer\n to peer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the curren 8831 authentication delivery http https key license management policies subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8847","type":"specification","body":"IETF","designation":"RFC 8847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8847.txt","https://www.rfc-editor.org/rfc/rfc8847.pdf"],"folder":"IETF/RFC-8847","files":{"pdf":{"path":"standards/IETF/RFC-8847/RFC-8847.pdf","sha256":"216ea7f818c0f143f45cb91cc2bc49eae621527e90dfa43f53eb53020df914b7"},"txt":{"path":"standards/IETF/RFC-8847/RFC-8847.txt","sha256":"82a236d2be604211d63f2f7419d6698886754153ecf9bf0ff38f2b10e24268a3"}},"tags":["nested-reference","unchanged"],"summary":"The Controlling Multiple Streams for Telepresence (CLUE) protocol is\n an application protocol conceived for the description and negotiation\n of a telepresence session. The design of the CLUE protocol takes\n into account the requirements and the framework defined within the\n IETF CLUE Working Group. A companion document, RFC 8848, delves into\n CLUE signaling details as well as the SIP / Session Description\n Protocol (SDP) session establishment phase. CLUE messages flow over\n the CLUE data channel, based on reliable and ordered SCTP-over-DTLS\n transport. (\"SCTP\" stands for \"Stream Control Transmission\n Protocol\".) Message details, together with the behavior of CLUE\n Participants acting as Media Providers and/or Media Consumers, are\n herein discussed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental impleme","scope_keywords":["8847","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null}],"search_text":"IETF RFC 8847 The Controlling Multiple Streams for Telepresence (CLUE) protocol is\n an application protocol conceived for the description and negotiation\n of a telepresence session. The design of the CLUE protocol takes\n into account the requirements and the framework defined within the\n IETF CLUE Working Group. A companion document, RFC 8848, delves into\n CLUE signaling details as well as the SIP / Session Description\n Protocol (SDP) session establishment phase. CLUE messages flow over\n the CLUE data channel, based on reliable and ordered SCTP-over-DTLS\n transport. (\"SCTP\" stands for \"Stream Control Transmission\n Protocol\".) Message details, together with the behavior of CLUE\n Participants acting as Media Providers and/or Media Consumers, are\n herein discussed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental impleme 8847 http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 1123","type":"specification","body":"IETF","designation":"RFC 1123","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1123.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1123.txt","https://www.rfc-editor.org/rfc/rfc1123.pdf"],"folder":"IETF/RFC-1123","files":{"txt":{"path":"standards/IETF/RFC-1123/RFC-1123.txt","sha256":"3d019cc4777d1ead76c212711d56768bde9361312cd209846b62d2e41dd0301d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Engineering Task Force\nRequest for Comments: 1123 R. Braden, Editor\n October 1989\n\n Requirements for Internet Hosts -- Application and Support\n\nStatus of This Memo\n\n This RFC is an official specification for the Internet community. It\n incorporates by reference, amends, corrects, and supplements the\n primary protocol standards documents relating to hosts. Distribution\n of this document is unlimited.\n\nSummary\n\n This RFC is one of a pair that defines and discusses the requirements\n for Internet host software. This RFC covers the application and\n support protocols; its companion RFC-1122 covers the communication\n protocol layers: link layer, IP layer, and transport layer.\n\n Table of Contents\n\n 1. INTRODUCTION ............................................... 5\n 1.1 The Internet Architecture .............................. 6\n 1.2 General Considerations ...........","scope_keywords":["1123","algorithm","algorithms","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1143","folder":"IETF/RFC-1143","source":"IETF/RFC-1143/RFC-1143.txt","version":null},{"body":"IETF","designation":"RFC 1147","folder":"IETF/RFC-1147","source":"IETF/RFC-1147/RFC-1147.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1153","folder":"IETF/RFC-1153","source":"IETF/RFC-1153/RFC-1153.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1350","folder":"IETF/RFC-1350","source":"IETF/RFC-1350/RFC-1350.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1425","folder":"IETF/RFC-1425","source":"IETF/RFC-1425/RFC-1425.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1579","folder":"IETF/RFC-1579","source":"IETF/RFC-1579/RFC-1579.txt","version":null},{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1639","folder":"IETF/RFC-1639","source":"IETF/RFC-1639/RFC-1639.txt","version":null},{"body":"IETF","designation":"RFC 1648","folder":"IETF/RFC-1648","source":"IETF/RFC-1648/RFC-1648.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1651","folder":"IETF/RFC-1651","source":"IETF/RFC-1651/RFC-1651.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1767","folder":"IETF/RFC-1767","source":"IETF/RFC-1767/RFC-1767.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1846","folder":"IETF/RFC-1846","source":"IETF/RFC-1846/RFC-1846.txt","version":null},{"body":"IETF","designation":"RFC 1869","folder":"IETF/RFC-1869","source":"IETF/RFC-1869/RFC-1869.txt","version":null},{"body":"IETF","designation":"RFC 1878","folder":"IETF/RFC-1878","source":"IETF/RFC-1878/RFC-1878.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2069","folder":"IETF/RFC-2069","source":"IETF/RFC-2069/RFC-2069.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2181","folder":"IETF/RFC-2181","source":"IETF/RFC-2181/RFC-2181.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2228","folder":"IETF/RFC-2228","source":"IETF/RFC-2228/RFC-2228.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2542","folder":"IETF/RFC-2542","source":"IETF/RFC-2542/RFC-2542.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2635","folder":"IETF/RFC-2635","source":"IETF/RFC-2635/RFC-2635.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1123 Network Working Group Internet Engineering Task Force\nRequest for Comments: 1123 R. Braden, Editor\n October 1989\n\n Requirements for Internet Hosts -- Application and Support\n\nStatus of This Memo\n\n This RFC is an official specification for the Internet community. It\n incorporates by reference, amends, corrects, and supplements the\n primary protocol standards documents relating to hosts. Distribution\n of this document is unlimited.\n\nSummary\n\n This RFC is one of a pair that defines and discusses the requirements\n for Internet host software. This RFC covers the application and\n support protocols; its companion RFC-1122 covers the communication\n protocol layers: link layer, IP layer, and transport layer.\n\n Table of Contents\n\n 1. INTRODUCTION ............................................... 5\n 1.1 The Internet Architecture .............................. 6\n 1.2 General Considerations ........... 1123 algorithm algorithms key management path nested-reference unchanged"},{"id":"IETF RFC 1153","type":"specification","body":"IETF","designation":"RFC 1153","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1153.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1153.txt","https://www.rfc-editor.org/rfc/rfc1153.pdf"],"folder":"IETF/RFC-1153","files":{"txt":{"path":"standards/IETF/RFC-1153/RFC-1153.txt","sha256":"ae41732ead944225099ad0cffbc3ec8e977aadc82cdc920df076bd88b8a9cf3d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Wancho\nRequest for Comments: 1153 WSMR\n April 1990\n\n Digest Message Format\n\nStatus of this Memo\n\n This memo describes the de facto standard Digest Message Format.\n This is an elective experimental protocol. Distribution of this memo\n is unlimited.\n\nBackground\n\n High traffic volume large mailing lists began to appear on the net in\n the mid-70s. The moderators of those lists developed a digest\n message format to enclose several messages into one composite message\n for redistribution to the mailing list addressees. This format\n reduces the mailer load in proportion to the number of messages\n contained within a digest message, and conserves network bandwidth by\n reducing the size of the headers of the enclosed messages.\n\n This RFC documents the digest message format so that others may\n follow this format in creating (digestifying) and separating\n (undigestifying) dig","scope_keywords":["1153","key","qualified","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1153 Network Working Group F. Wancho\nRequest for Comments: 1153 WSMR\n April 1990\n\n Digest Message Format\n\nStatus of this Memo\n\n This memo describes the de facto standard Digest Message Format.\n This is an elective experimental protocol. Distribution of this memo\n is unlimited.\n\nBackground\n\n High traffic volume large mailing lists began to appear on the net in\n the mid-70s. The moderators of those lists developed a digest\n message format to enclose several messages into one composite message\n for redistribution to the mailing list addressees. This format\n reduces the mailer load in proportion to the number of messages\n contained within a digest message, and conserves network bandwidth by\n reducing the size of the headers of the enclosed messages.\n\n This RFC documents the digest message format so that others may\n follow this format in creating (digestifying) and separating\n (undigestifying) dig 1153 key qualified risk subject nested-reference unchanged"},{"id":"IETF RFC 1350","type":"specification","body":"IETF","designation":"RFC 1350","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1350.txt","https://www.rfc-editor.org/rfc/rfc1350.pdf"],"folder":"IETF/RFC-1350","files":{"txt":{"path":"standards/IETF/RFC-1350/RFC-1350.txt","sha256":"39c9534e5fa6fecd3ac083ffd6256c2cc9a58f9f1058cb2e472d1782040231f9"}},"tags":["nested-reference","unchanged"],"summary":"TFTP is a simple protocol to transfer files, and therefore was named\n the Trivial File Transfer Protocol or TFTP. It has been implemented\n on top of the Internet User Datagram protocol (UDP or Datagram) [2]","scope_keywords":["1350","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1782","folder":"IETF/RFC-1782","source":"IETF/RFC-1782/RFC-1782.txt","version":null},{"body":"IETF","designation":"RFC 1783","folder":"IETF/RFC-1783","source":"IETF/RFC-1783/RFC-1783.txt","version":null},{"body":"IETF","designation":"RFC 1784","folder":"IETF/RFC-1784","source":"IETF/RFC-1784/RFC-1784.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1986","folder":"IETF/RFC-1986","source":"IETF/RFC-1986/RFC-1986.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2090","folder":"IETF/RFC-2090","source":"IETF/RFC-2090/RFC-2090.txt","version":null},{"body":"IETF","designation":"RFC 2347","folder":"IETF/RFC-2347","source":"IETF/RFC-2347/RFC-2347.txt","version":null},{"body":"IETF","designation":"RFC 2348","folder":"IETF/RFC-2348","source":"IETF/RFC-2348/RFC-2348.txt","version":null},{"body":"IETF","designation":"RFC 2349","folder":"IETF/RFC-2349","source":"IETF/RFC-2349/RFC-2349.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null}],"search_text":"IETF RFC 1350 TFTP is a simple protocol to transfer files, and therefore was named\n the Trivial File Transfer Protocol or TFTP. It has been implemented\n on top of the Internet User Datagram protocol (UDP or Datagram) [2] 1350 authentication nested-reference unchanged"},{"id":"IETF RFC 1425","type":"specification","body":"IETF","designation":"RFC 1425","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1425.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1425.txt","https://www.rfc-editor.org/rfc/rfc1425.pdf"],"folder":"IETF/RFC-1425","files":{"txt":{"path":"standards/IETF/RFC-1425/RFC-1425.txt","sha256":"1c28a9e40c0cb2a5c54a9436d7755b548e85ebcf33fec48e59140e40a79b8673"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Standard extensions to the SMTP\n service are registered with the Internet Assigned Numbers Authority\n (IANA). This framework does not require modification of existing\n SMTP clients or servers unless the features of the service extensions\n are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framewo","scope_keywords":["1425","algorithm","delivery","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1830","folder":"IETF/RFC-1830","source":"IETF/RFC-1830/RFC-1830.txt","version":null},{"body":"IETF","designation":"RFC 1854","folder":"IETF/RFC-1854","source":"IETF/RFC-1854/RFC-1854.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1985","folder":"IETF/RFC-1985","source":"IETF/RFC-1985/RFC-1985.txt","version":null},{"body":"IETF","designation":"RFC 2197","folder":"IETF/RFC-2197","source":"IETF/RFC-2197/RFC-2197.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null}],"search_text":"IETF RFC 1425 This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Standard extensions to the SMTP\n service are registered with the Internet Assigned Numbers Authority\n (IANA). This framework does not require modification of existing\n SMTP clients or servers unless the features of the service extensions\n are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framewo 1425 algorithm delivery key management registered nested-reference unchanged"},{"id":"IETF RFC 1579","type":"specification","body":"IETF","designation":"RFC 1579","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1579.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1579.txt","https://www.rfc-editor.org/rfc/rfc1579.pdf"],"folder":"IETF/RFC-1579","files":{"txt":{"path":"standards/IETF/RFC-1579/RFC-1579.txt","sha256":"2a599875ad396f34e6cfda3317977170cef8a7d2a4f2132d83cfe2d65caf3da0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bellovin\nRequest for Comments: 1579 AT&T Bell Laboratories\nCategory: Informational February 1994\n\n Firewall-Friendly FTP\n\nStatus of this Memo\n\n This document provides information for the Internet community. This\n document does not specify an Internet standard of any kind.\n Distribution of this document is unlimited.\n\nAbstract\n\n This memo describes a suggested change to the behavior of FTP client\n programs. No protocol modifications are required, though we outline\n some that might be useful.\n\nOverview and Rational\n\n The FTP protocol [1] uses a secondary TCP connection for actual\n transmission of files. By default, this connection is set up by an\n active open from the FTP server to the FTP client. However, this\n scheme does not work well with packet filter-based firewalls, which\n in general cannot permit incoming calls to random port numbers.\n\n If, on the other han","scope_keywords":["1579","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null}],"search_text":"IETF RFC 1579 Network Working Group S. Bellovin\nRequest for Comments: 1579 AT&T Bell Laboratories\nCategory: Informational February 1994\n\n Firewall-Friendly FTP\n\nStatus of this Memo\n\n This document provides information for the Internet community. This\n document does not specify an Internet standard of any kind.\n Distribution of this document is unlimited.\n\nAbstract\n\n This memo describes a suggested change to the behavior of FTP client\n programs. No protocol modifications are required, though we outline\n some that might be useful.\n\nOverview and Rational\n\n The FTP protocol [1] uses a secondary TCP connection for actual\n transmission of files. By default, this connection is set up by an\n active open from the FTP server to the FTP client. However, this\n scheme does not work well with packet filter-based firewalls, which\n in general cannot permit incoming calls to random port numbers.\n\n If, on the other han 1579 risk nested-reference unchanged"},{"id":"IETF RFC 1639","type":"specification","body":"IETF","designation":"RFC 1639","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1639.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1639.txt","https://www.rfc-editor.org/rfc/rfc1639.pdf"],"folder":"IETF/RFC-1639","files":{"txt":{"path":"standards/IETF/RFC-1639/RFC-1639.txt","sha256":"25c47a364e8c0f810c69627a2017b91688662ad946cc2a454b9c3f630c764145"}},"tags":["nested-reference","unchanged"],"summary":"This paper describes a convention for specifying address families\n other than the default Internet address family in FTP commands and\n replies.","scope_keywords":["1639","authentication","crl","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1682","folder":"IETF/RFC-1682","source":"IETF/RFC-1682/RFC-1682.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 3092","folder":"IETF/RFC-3092","source":"IETF/RFC-3092/RFC-3092.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1639 This paper describes a convention for specifying address families\n other than the default Internet address family in FTP commands and\n replies. 1639 authentication crl key presentation nested-reference unchanged"},{"id":"IETF RFC 1648","type":"specification","body":"IETF","designation":"RFC 1648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1648.txt","https://www.rfc-editor.org/rfc/rfc1648.pdf"],"folder":"IETF/RFC-1648","files":{"txt":{"path":"standards/IETF/RFC-1648/RFC-1648.txt","sha256":"92b1475b40164a44ec105fa3825c1d208dc0e3fd5ca3eff6d9a97d1c65333dcb"}},"tags":["nested-reference","unchanged"],"summary":"Both STD 11, RFC 822 [1] and STD 3, RFC 1123 [2] (Host Requirements)\n require that the email address \"postmaster\" be supported at all\n hosts. This paper extends this concept to X.400 mail domains which\n have registered RFC 1327 mapping rules, and which therefore appear to\n have normal RFC822-style addresses.\n\n1. Postmaster Convention in RFC822\n\n Operating a reliable, large-scale electronic mail (email) network\n requires cooperation between many mail managers and system\n administrators. As noted in RFC 822 [1], often mail or system\n managers need to be able to contact a responsible person at a remote\n host without knowing any specific user name or address at that host.\n For that reason, both RFC 822 and the Internet Host Requirements [2]\n require that the address \"postmaster\" be supported at every Internet\n host.\n\n2. Postmaster Convention and X.400\n\n However, RFC 822 is not the only email","scope_keywords":["1648","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1648 Both STD 11, RFC 822 [1] and STD 3, RFC 1123 [2] (Host Requirements)\n require that the email address \"postmaster\" be supported at all\n hosts. This paper extends this concept to X.400 mail domains which\n have registered RFC 1327 mapping rules, and which therefore appear to\n have normal RFC822-style addresses.\n\n1. Postmaster Convention in RFC822\n\n Operating a reliable, large-scale electronic mail (email) network\n requires cooperation between many mail managers and system\n administrators. As noted in RFC 822 [1], often mail or system\n managers need to be able to contact a responsible person at a remote\n host without knowing any specific user name or address at that host.\n For that reason, both RFC 822 and the Internet Host Requirements [2]\n require that the address \"postmaster\" be supported at every Internet\n host.\n\n2. Postmaster Convention and X.400\n\n However, RFC 822 is not the only email 1648 registered nested-reference unchanged"},{"id":"IETF RFC 1651","type":"specification","body":"IETF","designation":"RFC 1651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1651.txt","https://www.rfc-editor.org/rfc/rfc1651.pdf"],"folder":"IETF/RFC-1651","files":{"txt":{"path":"standards/IETF/RFC-1651/RFC-1651.txt","sha256":"50a2770c03e123f7e826a7f77efecac35ecf132e28f344a076938461914d87e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Standard extensions to the SMTP\n service are registered with the IANA. This framework does not\n require modification of existing SMTP clients or servers unless the\n features of the service extensions are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framework in which all future extensions can\n ","scope_keywords":["1651","algorithm","delivery","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1854","folder":"IETF/RFC-1854","source":"IETF/RFC-1854/RFC-1854.txt","version":null},{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null}],"search_text":"IETF RFC 1651 This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Standard extensions to the SMTP\n service are registered with the IANA. This framework does not\n require modification of existing SMTP clients or servers unless the\n features of the service extensions are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framework in which all future extensions can\n  1651 algorithm delivery key management registered nested-reference unchanged"},{"id":"IETF RFC 1767","type":"specification","body":"IETF","designation":"RFC 1767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1767.txt","https://www.rfc-editor.org/rfc/rfc1767.pdf"],"folder":"IETF/RFC-1767","files":{"txt":{"path":"standards/IETF/RFC-1767/RFC-1767.txt","sha256":"84d88134cfcb15594dddc9130f6418110ef437cd6e4828ff76307075437a65e7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker\nRequest for Comments: 1767 Brandenburg Consulting\nCategory: Standards Track March 1995\n\n MIME Encapsulation of EDI Objects\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction........................................... 1\n 2. Application/EDIFACT specification...................... 2\n 3. Application/EDI-X12 specification...................... 3\n 4. Application/EDI-Consent specification.................. 4\n 5. Sample edi usage in MIME-based email................... 5\n 6. References.....................................","scope_keywords":["1767","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 1767 Network Working Group D. Crocker\nRequest for Comments: 1767 Brandenburg Consulting\nCategory: Standards Track March 1995\n\n MIME Encapsulation of EDI Objects\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction........................................... 1\n 2. Application/EDIFACT specification...................... 2\n 3. Application/EDI-X12 specification...................... 3\n 4. Application/EDI-Consent specification.................. 4\n 5. Sample edi usage in MIME-based email................... 5\n 6. References..................................... 1767 delivery nested-reference unchanged"},{"id":"IETF RFC 1845","type":"specification","body":"IETF","designation":"RFC 1845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1845.txt","https://www.rfc-editor.org/rfc/rfc1845.pdf"],"folder":"IETF/RFC-1845","files":{"txt":{"path":"standards/IETF/RFC-1845/RFC-1845.txt","sha256":"e7f5bfb021479f9eaa338bf902253b210b8728f85307aeb657d5b8b62ca6863b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker\nRequest For Comments: 1845 Brandenburg Consulting\nCategory: Experimental N. Freed\n Innosoft International, Inc.\n A. Cargille, WG Chair\n September 1995\n\n SMTP Service Extension\n for Checkpoint/Restart\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This memo defines an extension to the SMTP service whereby an\n interrupted SMTP transaction can be restarted at a later time without\n having to repeat all of the commands and message content sent prior\n to the interruption.\n\n1. Introduction\n\n Although SMTP is widely and robustly deployed, various extensions\n have been requested by parts of the Internet community. In\n particular, when dealing with","scope_keywords":["1845","key","path","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 1845 Network Working Group D. Crocker\nRequest For Comments: 1845 Brandenburg Consulting\nCategory: Experimental N. Freed\n Innosoft International, Inc.\n A. Cargille, WG Chair\n September 1995\n\n SMTP Service Extension\n for Checkpoint/Restart\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This memo defines an extension to the SMTP service whereby an\n interrupted SMTP transaction can be restarted at a later time without\n having to repeat all of the commands and message content sent prior\n to the interruption.\n\n1. Introduction\n\n Although SMTP is widely and robustly deployed, various extensions\n have been requested by parts of the Internet community. In\n particular, when dealing with 1845 key path tls tsp nested-reference unchanged"},{"id":"IETF RFC 1846","type":"specification","body":"IETF","designation":"RFC 1846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1846.txt","https://www.rfc-editor.org/rfc/rfc1846.pdf"],"folder":"IETF/RFC-1846","files":{"txt":{"path":"standards/IETF/RFC-1846/RFC-1846.txt","sha256":"a49bdeed91e88b09c641b3899c1a2cac00f91df516d34612e4e6ca64c6aea046"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Simple Mail Transfer Protocol (SMTP) [1]\n reply code, 521, which one may use to indicate that an Internet host\n does not accept incoming mail.\n\n1. Motivations\n\n Hosts on the Internet have shifted from large, general-purpose hosts\n to smaller, more specialized hosts. There is an increasing number of\n hosts which are dedicated to specific tasks, such as serving NTP or\n DNS. These dedicated hosts frequently do not provide mail service.\n\n Usually, these mailless hosts do not run an SMTP server.\n Unfortunately, users will occasionally misaddress mail to these\n hosts. Regular SMTP clients attempting to deliver this misaddressed\n mail must treat the lack of an SMTP server on the host as a temporary\n error. They must queue the mail for later delivery, should an SMTP\n server be started at a later time.\n\n This causes the mail to remain queued for days, until it is returned\n","scope_keywords":["1846","delivery","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 1846 This memo defines a new Simple Mail Transfer Protocol (SMTP) [1]\n reply code, 521, which one may use to indicate that an Internet host\n does not accept incoming mail.\n\n1. Motivations\n\n Hosts on the Internet have shifted from large, general-purpose hosts\n to smaller, more specialized hosts. There is an increasing number of\n hosts which are dedicated to specific tasks, such as serving NTP or\n DNS. These dedicated hosts frequently do not provide mail service.\n\n Usually, these mailless hosts do not run an SMTP server.\n Unfortunately, users will occasionally misaddress mail to these\n hosts. Regular SMTP clients attempting to deliver this misaddressed\n mail must treat the lack of an SMTP server on the host as a temporary\n error. They must queue the mail for later delivery, should an SMTP\n server be started at a later time.\n\n This causes the mail to remain queued for days, until it is returned\n 1846 delivery subject nested-reference unchanged"},{"id":"IETF RFC 1869","type":"specification","body":"IETF","designation":"RFC 1869","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1869.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1869.txt","https://www.rfc-editor.org/rfc/rfc1869.pdf"],"folder":"IETF/RFC-1869","files":{"txt":{"path":"standards/IETF/RFC-1869/RFC-1869.txt","sha256":"b250cf1fc2f3e04068c068453a80e15b91b904ebfffc93f9441b006daea786ea"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Extensions to the SMTP service\n are registered with the IANA. This framework does not require\n modification of existing SMTP clients or servers unless the features\n of the service extensions are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framework in which all future extensions can\n be built ","scope_keywords":["1869","algorithm","delivery","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2034","folder":"IETF/RFC-2034","source":"IETF/RFC-2034/RFC-2034.txt","version":null},{"body":"IETF","designation":"RFC 2197","folder":"IETF/RFC-2197","source":"IETF/RFC-2197/RFC-2197.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null},{"body":"IETF","designation":"RFC 2979","folder":"IETF/RFC-2979","source":"IETF/RFC-2979/RFC-2979.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null}],"search_text":"IETF RFC 1869 This memo defines a framework for extending the SMTP service by\n defining a means whereby a server SMTP can inform a client SMTP as to\n the service extensions it supports. Extensions to the SMTP service\n are registered with the IANA. This framework does not require\n modification of existing SMTP clients or servers unless the features\n of the service extensions are to be requested or provided.\n\n2. Introduction\n\n The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable,\n effective basis for the relay function of message transfer agents.\n Although a decade old, SMTP has proven remarkably resilient.\n Nevertheless, the need for a number of protocol extensions has become\n evident. Rather than describing these extensions as separate and\n haphazard entities, this document enhances SMTP in a straightforward\n fashion that provides a framework in which all future extensions can\n be built  1869 algorithm delivery management registered nested-reference unchanged"},{"id":"IETF RFC 1878","type":"specification","body":"IETF","designation":"RFC 1878","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1878.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1878.txt","https://www.rfc-editor.org/rfc/rfc1878.pdf"],"folder":"IETF/RFC-1878","files":{"txt":{"path":"standards/IETF/RFC-1878/RFC-1878.txt","sha256":"2869b124b9258cc11a34527d330e5310519d0cc6182bf0e103b1a65b7856dc3c"}},"tags":["nested-reference","unchanged"],"summary":"This memo clarifies issues surrounding subnetting IP networks by\n providing a standard subnet table. This table includes subnetting\n for Class A, B, and C networks, as well as Network IDs, host ranges\n and IP broadcast addresses with emphasis on Class C subnets.\n\n This memo is intended as an informational companion to Subneting RFC\n [1] and the Hosts Requirements RFC [2].","scope_keywords":["1878","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1878 This memo clarifies issues surrounding subnetting IP networks by\n providing a standard subnet table. This table includes subnetting\n for Class A, B, and C networks, as well as Network IDs, host ranges\n and IP broadcast addresses with emphasis on Class C subnets.\n\n This memo is intended as an informational companion to Subneting RFC\n [1] and the Hosts Requirements RFC [2]. 1878 presentation nested-reference unchanged"},{"id":"IETF RFC 1891","type":"specification","body":"IETF","designation":"RFC 1891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1891.txt","https://www.rfc-editor.org/rfc/rfc1891.pdf"],"folder":"IETF/RFC-1891","files":{"txt":{"path":"standards/IETF/RFC-1891/RFC-1891.txt","sha256":"7685ab3ac625671cdc8fde3e6301dfbd6b9be809d09a01f26f0dc47cba2ba344"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service, which allows an\n SMTP client to specify (a) that delivery status notifications (DSNs)\n should be generated under certain conditions, (b) whether such\n notifications should return the contents of the message, and (c)\n additional information, to be returned with a DSN, that allows the\n sender to identify both the recipient(s) for which the DSN was\n issued, and the transaction in which the original message was sent.\n\n Any questions, comments, and reports of defects or ambiguities in\n this specification may be sent to the mailing list for the NOTARY\n working group of the IETF, using the address\n <notifications@cs.utk.edu>. Requests to subscribe to the mailing\n list should be addressed to <notifications-request@cs.utk.edu>.\n Implementors of this specification are encouraged to subscribe to the\n mailing list, so that they will quickly be info","scope_keywords":["1891","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1892","folder":"IETF/RFC-1892","source":"IETF/RFC-1892/RFC-1892.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null}],"search_text":"IETF RFC 1891 This memo defines an extension to the SMTP service, which allows an\n SMTP client to specify (a) that delivery status notifications (DSNs)\n should be generated under certain conditions, (b) whether such\n notifications should return the contents of the message, and (c)\n additional information, to be returned with a DSN, that allows the\n sender to identify both the recipient(s) for which the DSN was\n issued, and the transaction in which the original message was sent.\n\n Any questions, comments, and reports of defects or ambiguities in\n this specification may be sent to the mailing list for the NOTARY\n working group of the IETF, using the address\n <notifications@cs.utk.edu>. Requests to subscribe to the mailing\n list should be addressed to <notifications-request@cs.utk.edu>.\n Implementors of this specification are encouraged to subscribe to the\n mailing list, so that they will quickly be info 1891 delivery key subject nested-reference unchanged"},{"id":"IETF RFC 2069","type":"specification","body":"IETF","designation":"RFC 2069","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2069.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2069.txt","https://www.rfc-editor.org/rfc/rfc2069.pdf"],"folder":"IETF/RFC-2069","files":{"txt":{"path":"standards/IETF/RFC-2069/RFC-2069.txt","sha256":"b5c2dc373abb3a4d7784ea4ec9a4f05b1ac1fba115ddb54d38a4a4c6b4d29e73"}},"tags":["nested-reference","unchanged"],"summary":"The protocol referred to as \"HTTP/1.0\" includes the specification for\n a Basic Access Authentication scheme. This scheme is not considered\n to be a secure method of user authentication, as the user name and\n password are passed over the network as clear text. A specification\n for a different authentication scheme is needed to address this\n severe limitation. This document provides specification for such a\n scheme, referred to as \"Digest Access Authentication\". Like Basic,\n Digest access authentication verifies that both parties to a\n communication know a shared secret (a password); unlike Basic, this\n verification can be done without sending the password in the clear,\n which is Basic's biggest weakness. As with most other authentication\n protocols, the greatest sources of risks are usually found not in the\n core protocol itself but in policies and procedures surrounding its\n use.\n\nFranks","scope_keywords":["2069","algorithm","authentication","authorization","encryption","http","key","policies","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null}],"search_text":"IETF RFC 2069 The protocol referred to as \"HTTP/1.0\" includes the specification for\n a Basic Access Authentication scheme. This scheme is not considered\n to be a secure method of user authentication, as the user name and\n password are passed over the network as clear text. A specification\n for a different authentication scheme is needed to address this\n severe limitation. This document provides specification for such a\n scheme, referred to as \"Digest Access Authentication\". Like Basic,\n Digest access authentication verifies that both parties to a\n communication know a shared secret (a password); unlike Basic, this\n verification can be done without sending the password in the clear,\n which is Basic's biggest weakness. As with most other authentication\n protocols, the greatest sources of risks are usually found not in the\n core protocol itself but in policies and procedures surrounding its\n use.\n\nFranks 2069 algorithm authentication authorization encryption http key policies presentation risk nested-reference unchanged"},{"id":"IETF RFC 2228","type":"specification","body":"IETF","designation":"RFC 2228","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2228.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2228.txt","https://www.rfc-editor.org/rfc/rfc2228.pdf"],"folder":"IETF/RFC-2228","files":{"txt":{"path":"standards/IETF/RFC-2228/RFC-2228.txt","sha256":"269c97592b7ec2658a007080431082d98d43b2ba6351490214d2354acd08e6ea"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Horowitz\nRequest for Comments: 2228 Cygnus Solutions\nUpdates: 959 S. Lunt\nCategory: Standards Track Bellcore\n October 1997\n\n FTP Security Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n This document defines extensions to the FTP specification STD 9, RFC\n 959, \"FILE TRANSFER PROTOCOL (FTP)\" (October 1985). These extensions\n provide strong authentication, integrity, and confidentiality on both\n the control and data channels with the introduction of n","scope_keywords":["2228","authentication","authorization","encryption","key","keys","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 2773","folder":"IETF/RFC-2773","source":"IETF/RFC-2773/RFC-2773.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null}],"search_text":"IETF RFC 2228 Network Working Group M. Horowitz\nRequest for Comments: 2228 Cygnus Solutions\nUpdates: 959 S. Lunt\nCategory: Standards Track Bellcore\n October 1997\n\n FTP Security Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n This document defines extensions to the FTP specification STD 9, RFC\n 959, \"FILE TRANSFER PROTOCOL (FTP)\" (October 1985). These extensions\n provide strong authentication, integrity, and confidentiality on both\n the control and data channels with the introduction of n 2228 authentication authorization encryption key keys risk nested-reference unchanged"},{"id":"IETF RFC 2298","type":"specification","body":"IETF","designation":"RFC 2298","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2298.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2298.txt","https://www.rfc-editor.org/rfc/rfc2298.pdf"],"folder":"IETF/RFC-2298","files":{"txt":{"path":"standards/IETF/RFC-2298/RFC-2298.txt","sha256":"9625c7d2337bebca3b91cabdf8499dfe4c59724d7fe5ce389f57c8586c667eba"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIME content-type that may be used by a mail user\n agent (UA) or electronic mail gateway to report the disposition of a\n message after it has been sucessfully delivered to a recipient. This\n content-type is intended to be machine-processable. Additional\n message headers are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and often referred to as \"read receipts,\"\n \"acknowledgements,\" or \"receipt notifications.\" The intention is to\n do this while respecting the privacy concerns that have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as","scope_keywords":["2298","attribute","attributes","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2542","folder":"IETF/RFC-2542","source":"IETF/RFC-2542/RFC-2542.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3503","folder":"IETF/RFC-3503","source":"IETF/RFC-3503/RFC-3503.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 2298 This memo defines a MIME content-type that may be used by a mail user\n agent (UA) or electronic mail gateway to report the disposition of a\n message after it has been sucessfully delivered to a recipient. This\n content-type is intended to be machine-processable. Additional\n message headers are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and often referred to as \"read receipts,\"\n \"acknowledgements,\" or \"receipt notifications.\" The intention is to\n do this while respecting the privacy concerns that have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as 2298 attribute attributes delivery key nested-reference unchanged"},{"id":"IETF RFC 2303","type":"specification","body":"IETF","designation":"RFC 2303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2303.txt","https://www.rfc-editor.org/rfc/rfc2303.pdf"],"folder":"IETF/RFC-2303","files":{"txt":{"path":"standards/IETF/RFC-2303/RFC-2303.txt","sha256":"c652b8ebdf15c28f88276bbf62662f8ebcfb963034b09e50f9c9be3d5f6d189c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Allocchio\nRequest for Comments: 2303 GARR-Italy\nCategory: Standards Track March 1998\n\n Minimal PSTN address format in Internet Mail\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG NOTE\n\n This memo describes a simple method of encoding PSTN addresses in the\n local-part of Internet email addresses, along with an extension\n mechanism to allow encoding of additional standard attributes needed\n for email gateways to PSTN-based services.\n\n As with all Internet mail addres","scope_keywords":["2303","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null}],"search_text":"IETF RFC 2303 Network Working Group C. Allocchio\nRequest for Comments: 2303 GARR-Italy\nCategory: Standards Track March 1998\n\n Minimal PSTN address format in Internet Mail\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG NOTE\n\n This memo describes a simple method of encoding PSTN addresses in the\n local-part of Internet email addresses, along with an extension\n mechanism to allow encoding of additional standard attributes needed\n for email gateways to PSTN-based services.\n\n As with all Internet mail addres 2303 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 2304","type":"specification","body":"IETF","designation":"RFC 2304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2304.txt","https://www.rfc-editor.org/rfc/rfc2304.pdf"],"folder":"IETF/RFC-2304","files":{"txt":{"path":"standards/IETF/RFC-2304/RFC-2304.txt","sha256":"6e32618f9aca00765d2332d62927ac386bef5b3c0903fbd3d92edb2402c44668"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Allocchio\nRequest for Comments: 2304 GARR-Italy\nCategory: Standards Track March 1998\n\n Minimal FAX address format in Internet Mail\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG NOTE\n\n This memo describes a simple method of encoding PSTN addresses of\n facsimile devices in the local-part of Internet email addresses.\n\n As with all Internet mail addresses, the left-hand-side (local- part)\n of an address generated according to this specification, is not to be\n interpre","scope_keywords":["2304"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null}],"search_text":"IETF RFC 2304 Network Working Group C. Allocchio\nRequest for Comments: 2304 GARR-Italy\nCategory: Standards Track March 1998\n\n Minimal FAX address format in Internet Mail\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG NOTE\n\n This memo describes a simple method of encoding PSTN addresses of\n facsimile devices in the local-part of Internet email addresses.\n\n As with all Internet mail addresses, the left-hand-side (local- part)\n of an address generated according to this specification, is not to be\n interpre 2304 nested-reference unchanged"},{"id":"IETF RFC 2305","type":"specification","body":"IETF","designation":"RFC 2305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2305.txt","https://www.rfc-editor.org/rfc/rfc2305.pdf"],"folder":"IETF/RFC-2305","files":{"txt":{"path":"standards/IETF/RFC-2305/RFC-2305.txt","sha256":"8fc3f774bb3b8f163a044cef4e5acc090eb6b2683a2c8ac1e34327be0114f1c7"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a message-based facsimile communication\n over the Internet. It describes a minimum set of capabilities,\n taking into account those of typical facsimile devices and PCs that\n can generate facsimile data.\n\nToyoda, et. al. Standards Track [Page 1]\n\f\nRFC 2305 Simple Mode of Facsimile March 1998\n\n A G3Fax device has substantial restrictions due to specifications in\n the standards, such as for timers. This specification defines a\n profile for Internet mail, rather than creating a distinct \"facsimile\n over the Internet\" service. The semantics resulting from the profile\n are designed to be compatible with facsimile operation over the\n general switched telephone network, so that gateways between\n facsimile and Internet mail can operate with very high fidelity.\n\n The reason for developing this capability as an email profile is to\n permit interworking amongst facsimile an","scope_keywords":["2305","delivery","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2542","folder":"IETF/RFC-2542","source":"IETF/RFC-2542/RFC-2542.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null}],"search_text":"IETF RFC 2305 This specification defines a message-based facsimile communication\n over the Internet. It describes a minimum set of capabilities,\n taking into account those of typical facsimile devices and PCs that\n can generate facsimile data.\n\nToyoda, et. al. Standards Track [Page 1]\n\f\nRFC 2305 Simple Mode of Facsimile March 1998\n\n A G3Fax device has substantial restrictions due to specifications in\n the standards, such as for timers. This specification defines a\n profile for Internet mail, rather than creating a distinct \"facsimile\n over the Internet\" service. The semantics resulting from the profile\n are designed to be compatible with facsimile operation over the\n general switched telephone network, so that gateways between\n facsimile and Internet mail can operate with very high fidelity.\n\n The reason for developing this capability as an email profile is to\n permit interworking amongst facsimile an 2305 delivery key profile nested-reference unchanged"},{"id":"IETF RFC 2326","type":"specification","body":"IETF","designation":"RFC 2326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2326.txt","https://www.rfc-editor.org/rfc/rfc2326.pdf"],"folder":"IETF/RFC-2326","files":{"txt":{"path":"standards/IETF/RFC-2326/RFC-2326.txt","sha256":"1b72124761d99b8d4ed72fee82d4a3c4a7c153a368702b8221de02a42da93038"}},"tags":["nested-reference","unchanged"],"summary":"The Real Time Streaming Protocol, or RTSP, is an application-level\n protocol for control over the delivery of data with real-time\n properties. RTSP provides an extensible framework to enable\n controlled, on-demand delivery of real-time data, such as audio and\n video. Sources of data can include both live data feeds and stored\n clips. This protocol is intended to control multiple data delivery\n sessions, provide a means for choosing delivery channels such as UDP,\n multicast UDP and TCP, and provide a means for choosing delivery\n mechanisms based upon RTP (RFC 1889).","scope_keywords":["2326","authorization","delivery","timestamp","timestamps","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3466","folder":"IETF/RFC-3466","source":"IETF/RFC-3466/RFC-3466.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 2326 The Real Time Streaming Protocol, or RTSP, is an application-level\n protocol for control over the delivery of data with real-time\n properties. RTSP provides an extensible framework to enable\n controlled, on-demand delivery of real-time data, such as audio and\n video. Sources of data can include both live data feeds and stored\n clips. This protocol is intended to control multiple data delivery\n sessions, provide a means for choosing delivery channels such as UDP,\n multicast UDP and TCP, and provide a means for choosing delivery\n mechanisms based upon RTP (RFC 1889). 2326 authorization delivery timestamp timestamps tsp nested-reference unchanged"},{"id":"IETF RFC 2442","type":"specification","body":"IETF","designation":"RFC 2442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2442.txt","https://www.rfc-editor.org/rfc/rfc2442.pdf"],"folder":"IETF/RFC-2442","files":{"txt":{"path":"standards/IETF/RFC-2442/RFC-2442.txt","sha256":"c6662ec6a236960e17a4a1f83d910d1b1878af7f8d6bfce5ef11f5b339e1b405"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2442 D. Newman\nCategory: Informational Innosoft\n J. Belissent\n Sun Microsystems\n M. Hoy\n Mainbrace\n November 1998\n\n The\n Batch SMTP\n Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a MIME content type suitable for tunneling an\n ESMTP [RFC-821, RFC-1869] transaction through any MIME-capable\n transport. This type can be used for a variety of purposes,\n including: Extending end-to-end MIME-based security services (e.g.,\n [RFC-1847]) to cover message envelope information as well as message\n content. Making it possible to use specific SMTP extensions such as\n NOTARY [RFC-1891] over unex","scope_keywords":["2442","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 2442 Network Working Group N. Freed\nRequest for Comments: 2442 D. Newman\nCategory: Informational Innosoft\n J. Belissent\n Sun Microsystems\n M. Hoy\n Mainbrace\n November 1998\n\n The\n Batch SMTP\n Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a MIME content type suitable for tunneling an\n ESMTP [RFC-821, RFC-1869] transaction through any MIME-capable\n transport. This type can be used for a variety of purposes,\n including: Extending end-to-end MIME-based security services (e.g.,\n [RFC-1847]) to cover message envelope information as well as message\n content. Making it possible to use specific SMTP extensions such as\n NOTARY [RFC-1891] over unex 2442 crl nested-reference unchanged"},{"id":"IETF RFC 2476","type":"specification","body":"IETF","designation":"RFC 2476","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2476.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2476.txt","https://www.rfc-editor.org/rfc/rfc2476.pdf"],"folder":"IETF/RFC-2476","files":{"txt":{"path":"standards/IETF/RFC-2476/RFC-2476.txt","sha256":"4a96a70a886b9df8d95d1bb77d94b22d66d7d4d0df582e270e1d0528822d25f2"}},"tags":["nested-reference","unchanged"],"summary":"SMTP was defined as a message *transfer* protocol, that is, a means\n to route (if needed) and deliver finished (complete) messages.\n Message Transfer Agents (MTAs) are not supposed to alter the message\n text, except to add 'Received', 'Return-Path', and other header\n fields as required by [SMTP-MTA].\n\n However, SMTP is now also widely used as a message *submission*\n protocol, that is, a means for message user agents (MUAs) to\n introduce new messages into the MTA routing network. The process\n which accepts message submissions from MUAs is termed a Message\n Submission Agent (MSA).\n\n Messages being submitted are in some cases finished (complete)\n messages, and in other cases are unfinished (incomplete) in some\n aspect or other. Unfinished messages need to be completed to ensure\n they conform to [MESSAGE-FORMAT], and later requirements. For\n example, the message may lack a proper 'Date' head","scope_keywords":["2476","authentication","identification","key","path","policies","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4084","folder":"IETF/RFC-4084","source":"IETF/RFC-4084/RFC-4084.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 2476 SMTP was defined as a message *transfer* protocol, that is, a means\n to route (if needed) and deliver finished (complete) messages.\n Message Transfer Agents (MTAs) are not supposed to alter the message\n text, except to add 'Received', 'Return-Path', and other header\n fields as required by [SMTP-MTA].\n\n However, SMTP is now also widely used as a message *submission*\n protocol, that is, a means for message user agents (MUAs) to\n introduce new messages into the MTA routing network. The process\n which accepts message submissions from MUAs is termed a Message\n Submission Agent (MSA).\n\n Messages being submitted are in some cases finished (complete)\n messages, and in other cases are unfinished (incomplete) in some\n aspect or other. Unfinished messages need to be completed to ensure\n they conform to [MESSAGE-FORMAT], and later requirements. For\n example, the message may lack a proper 'Date' head 2476 authentication identification key path policies policy qualified nested-reference unchanged"},{"id":"IETF RFC 2480","type":"specification","body":"IETF","designation":"RFC 2480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2480.txt","https://www.rfc-editor.org/rfc/rfc2480.pdf"],"folder":"IETF/RFC-2480","files":{"txt":{"path":"standards/IETF/RFC-2480/RFC-2480.txt","sha256":"680edb08155f0231391845e782fd68c04c4299a51a20fa5f081d2ff7e58a07d6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2480 Innosoft International, Inc.\nCategory: Standards Track January 1999\n\n Gateways and MIME Security Multiparts\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n This document examines the problems associated with use of MIME\n security multiparts and gateways to non-MIME environments. A set of\n requirements for gateway behavior are defined which provide\n facilities necessary to properly accomodate the transfer of security\n multipa","scope_keywords":["2480","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 2480 Network Working Group N. Freed\nRequest for Comments: 2480 Innosoft International, Inc.\nCategory: Standards Track January 1999\n\n Gateways and MIME Security Multiparts\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n This document examines the problems associated with use of MIME\n security multiparts and gateways to non-MIME environments. A set of\n requirements for gateway behavior are defined which provide\n facilities necessary to properly accomodate the transfer of security\n multipa 2480 key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2542","type":"specification","body":"IETF","designation":"RFC 2542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2542.txt","https://www.rfc-editor.org/rfc/rfc2542.pdf"],"folder":"IETF/RFC-2542","files":{"txt":{"path":"standards/IETF/RFC-2542/RFC-2542.txt","sha256":"f348fe8744a9a5e20c1fcb85f6b822eea9eac3bfcd58c11d74b96593e809bcc9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a number of terms useful for the discussion of\n Internet Fax. In addition, it describes the goals of the Internet Fax\n working group and establishes a baseline of desired functionality\n against which protocols for Internet Fax can be judged. It\n encompasses the goals for all modes of facsimile delivery, including\n 'real-time', 'session', and 'store and forward'. Different levels of\n desirability are indicated throughout the document.","scope_keywords":["2542","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null}],"search_text":"IETF RFC 2542 This document defines a number of terms useful for the discussion of\n Internet Fax. In addition, it describes the goals of the Internet Fax\n working group and establishes a baseline of desired functionality\n against which protocols for Internet Fax can be judged. It\n encompasses the goals for all modes of facsimile delivery, including\n 'real-time', 'session', and 'store and forward'. Different levels of\n desirability are indicated throughout the document. 2542 delivery presentation nested-reference unchanged"},{"id":"IETF RFC 2565","type":"specification","body":"IETF","designation":"RFC 2565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2565.txt","https://www.rfc-editor.org/rfc/rfc2565.pdf"],"folder":"IETF/RFC-2565","files":{"txt":{"path":"standards/IETF/RFC-2565/RFC-2565.txt","sha256":"97078005195703305a2c933956f376dee94c5d72dcdc897c36c286b756f55e81"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document defines the\n rules for encoding IPP operations and IPP attributes into a new\n Internet mime media type called \"application/ipp\". This document\n also defines the rules for transporting over HTTP a message body\n whose Content-Type is \"application/ipp\".\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the\n Internet Printing Protocol [RFC2568]\n Internet Printing Protocol/1.0: Model and Semantics [RFC2566]\n Internet Printing Protocol/1.0: Encoding and Transport (this\n document)\n Internet Printing Protocol/1.0: Implementer's Guide [ip","scope_keywords":["2565","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null}],"search_text":"IETF RFC 2565 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document defines the\n rules for encoding IPP operations and IPP attributes into a new\n Internet mime media type called \"application/ipp\". This document\n also defines the rules for transporting over HTTP a message body\n whose Content-Type is \"application/ipp\".\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the\n Internet Printing Protocol [RFC2568]\n Internet Printing Protocol/1.0: Model and Semantics [RFC2566]\n Internet Printing Protocol/1.0: Encoding and Transport (this\n document)\n Internet Printing Protocol/1.0: Implementer's Guide [ip 2565 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 2635","type":"specification","body":"IETF","designation":"RFC 2635","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2635.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2635.txt","https://www.rfc-editor.org/rfc/rfc2635.pdf"],"folder":"IETF/RFC-2635","files":{"txt":{"path":"standards/IETF/RFC-2635/RFC-2635.txt","sha256":"af47b4d2dc411a0803f21fecb3237f12c7d41834d342f2b413ae51a5d7445649"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Hambridge\nRequest for Comments: 2635 INTEL\nFYI: 35 A. Lunde\nCategory: Informational Northwestern University\n June 1999\n\n DON'T SPEW\n A Set of Guidelines for Mass Unsolicited\n Mailings and Postings (spam*)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document explains why mass unsolicited electronic mail messages\n are harmful in the Internetworking community. It gives a set of\n guidelines for dealing with unsolicited mail for users, for system\n administrators, news administrators, and mailing list managers. It\n also makes suggestions Internet Service Providers might follow.\n\n1. Introduction\n\n The Internet's origins in the Research and","scope_keywords":["2635","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2635 Network Working Group S. Hambridge\nRequest for Comments: 2635 INTEL\nFYI: 35 A. Lunde\nCategory: Informational Northwestern University\n June 1999\n\n DON'T SPEW\n A Set of Guidelines for Mass Unsolicited\n Mailings and Postings (spam*)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document explains why mass unsolicited electronic mail messages\n are harmful in the Internetworking community. It gives a set of\n guidelines for dealing with unsolicited mail for users, for system\n administrators, news administrators, and mailing list managers. It\n also makes suggestions Internet Service Providers might follow.\n\n1. Introduction\n\n The Internet's origins in the Research and 2635 authentication nested-reference unchanged"},{"id":"IETF RFC 2639","type":"specification","body":"IETF","designation":"RFC 2639","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2639.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2639.txt","https://www.rfc-editor.org/rfc/rfc2639.pdf"],"folder":"IETF/RFC-2639","files":{"txt":{"path":"standards/IETF/RFC-2639/RFC-2639.txt","sha256":"3fc9fdcff03e342ab9b080f1629542935c650a6f5370a0bf15123a7e5a31bf0d"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document contains\n information that supplements the IPP Model and Semantics [RFC2566]\n and the IPP Transport and Encoding [RFC2565] documents. It is\n intended to help implementers understand IPP/1.0 and some of the\n considerations that may assist them in the design of their client\n and/or IPP object implementations. For example, a typical order of\n processing requests is given, including error checking. Motivation\n for some of the specification decisions is also included.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the Internet\n Pri","scope_keywords":["2639","algorithm","attribute","attributes","http","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null}],"search_text":"IETF RFC 2639 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document contains\n information that supplements the IPP Model and Semantics [RFC2566]\n and the IPP Transport and Encoding [RFC2565] documents. It is\n intended to help implementers understand IPP/1.0 and some of the\n considerations that may assist them in the design of their client\n and/or IPP object implementations. For example, a typical order of\n processing requests is given, including error checking. Motivation\n for some of the specification decisions is also included.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the Internet\n Pri 2639 algorithm attribute attributes http validation nested-reference unchanged"},{"id":"IETF RFC 2640","type":"specification","body":"IETF","designation":"RFC 2640","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2640.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2640.txt","https://www.rfc-editor.org/rfc/rfc2640.pdf"],"folder":"IETF/RFC-2640","files":{"txt":{"path":"standards/IETF/RFC-2640/RFC-2640.txt","sha256":"310015301839ea07cd1c0988dfb083316a015f9cad59b3b43bb63e02c5537195"}},"tags":["nested-reference","unchanged"],"summary":"The File Transfer Protocol, as defined in RFC 959 [RFC959] and RFC\n 1123 Section 4 [RFC1123], is one of the oldest and widely used\n protocols on the Internet. The protocol's primary character set, 7\n bit ASCII, has served the protocol well through the early growth\n years of the Internet. However, as the Internet becomes more global,\n there is a need to support character sets beyond 7 bit ASCII.\n\n This document addresses the internationalization (I18n) of FTP, which\n includes supporting the multiple character sets and languages found\n throughout the Internet community. This is achieved by extending the\n FTP specification and giving recommendations for proper\n internationalization support.","scope_keywords":["2640","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null}],"search_text":"IETF RFC 2640 The File Transfer Protocol, as defined in RFC 959 [RFC959] and RFC\n 1123 Section 4 [RFC1123], is one of the oldest and widely used\n protocols on the Internet. The protocol's primary character set, 7\n bit ASCII, has served the protocol well through the early growth\n years of the Internet. However, as the Internet becomes more global,\n there is a need to support character sets beyond 7 bit ASCII.\n\n This document addresses the internationalization (I18n) of FTP, which\n includes supporting the multiple character sets and languages found\n throughout the Internet community. This is achieved by extending the\n FTP specification and giving recommendations for proper\n internationalization support. 2640 key path policy nested-reference unchanged"},{"id":"IETF RFC 2812","type":"specification","body":"IETF","designation":"RFC 2812","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2812.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2812.txt","https://www.rfc-editor.org/rfc/rfc2812.pdf"],"folder":"IETF/RFC-2812","files":{"txt":{"path":"standards/IETF/RFC-2812/RFC-2812.txt","sha256":"9337603057716c2e74809e8c57b557ee0bdbfca60cc5c852e240df0e5ba53479"}},"tags":["nested-reference","unchanged"],"summary":"The IRC (Internet Relay Chat) protocol is for use with text based\n conferencing; the simplest client being any socket program capable of\n connecting to the server.\n\n This document defines the Client Protocol, and assumes that the\n reader is familiar with the IRC Architecture [IRC-ARCH].","scope_keywords":["2812","hash","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2810","folder":"IETF/RFC-2810","source":"IETF/RFC-2810/RFC-2810.txt","version":null},{"body":"IETF","designation":"RFC 2811","folder":"IETF/RFC-2811","source":"IETF/RFC-2811/RFC-2811.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null}],"search_text":"IETF RFC 2812 The IRC (Internet Relay Chat) protocol is for use with text based\n conferencing; the simplest client being any socket program capable of\n connecting to the server.\n\n This document defines the Client Protocol, and assumes that the\n reader is familiar with the IRC Architecture [IRC-ARCH]. 2812 hash http nested-reference unchanged"},{"id":"IETF RFC 2846","type":"specification","body":"IETF","designation":"RFC 2846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2846.txt","https://www.rfc-editor.org/rfc/rfc2846.pdf"],"folder":"IETF/RFC-2846","files":{"txt":{"path":"standards/IETF/RFC-2846/RFC-2846.txt","sha256":"bca3f83e03d68535d45417c32392c1da114b0d7a8b94fa9318c8e9398e3d2389"}},"tags":["nested-reference","unchanged"],"summary":"There are numerous applications where there is a need for interaction\n between the GSTN addressing and Internet addressing. This memo\n defines a full syntax for one specific case, where there is a need to\n represent GSTN addresses within Internet e-mail addresses. This full\n syntax is a superset of a minimal syntax which has been defined in\n [1].\n\n1. Introduction\n\n The possible elements composing a \"Global Switched Telephone Network\n (GSTN) address in e-mail\" (also known as the Public Switched\n Telephone Network - PSTN) can vary from a minimum number up to a\n really large and complex collection. As noted the minimal format and\n general address syntax have been defined in [1], along with the\n mechanism needed to define additional address elements. This memo\n uses this extension mechanism to complete the syntax for representing\n GSTN addresses within e-mail addresses and contains the IANA\n","scope_keywords":["2846","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null}],"search_text":"IETF RFC 2846 There are numerous applications where there is a need for interaction\n between the GSTN addressing and Internet addressing. This memo\n defines a full syntax for one specific case, where there is a need to\n represent GSTN addresses within Internet e-mail addresses. This full\n syntax is a superset of a minimal syntax which has been defined in\n [1].\n\n1. Introduction\n\n The possible elements composing a \"Global Switched Telephone Network\n (GSTN) address in e-mail\" (also known as the Public Switched\n Telephone Network - PSTN) can vary from a minimum number up to a\n really large and complex collection. As noted the minimal format and\n general address syntax have been defined in [1], along with the\n mechanism needed to define additional address elements. This memo\n uses this extension mechanism to complete the syntax for representing\n GSTN addresses within e-mail addresses and contains the IANA\n 2846 key registered nested-reference unchanged"},{"id":"IETF RFC 2852","type":"specification","body":"IETF","designation":"RFC 2852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2852.txt","https://www.rfc-editor.org/rfc/rfc2852.pdf"],"folder":"IETF/RFC-2852","files":{"txt":{"path":"standards/IETF/RFC-2852/RFC-2852.txt","sha256":"43cfc32009506a7c42f29cae706c5c408822f8c945c93cda0d082855372da6b7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a mechanism whereby a SMTP client can request, when\n transmitting a message to a SMTP server, that the server deliver the\n message within a prescribed period of time. A client making such a\n request also specifies the message handling which is to occur if the\n message cannot be delivered within the specified time period: either\n the message is to be returned as undeliverable with no further\n processing, or a \"delayed\" delivery status notification (DSN) [6] is\n to be issued.\n\n This extension should not be viewed as a vehicle for requesting\n \"priority\" processing. A receiving SMTP server may assign whatever\n processing priority it wishes to a message transmitted with a Deliver\n By request. A Deliver By request serves to express a message's\n urgency and to provide an additional degree of determinancy in its\n processing. An indication of an urgent message's status within a\n","scope_keywords":["2852","delivery","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 2852 This memo defines a mechanism whereby a SMTP client can request, when\n transmitting a message to a SMTP server, that the server deliver the\n message within a prescribed period of time. A client making such a\n request also specifies the message handling which is to occur if the\n message cannot be delivered within the specified time period: either\n the message is to be returned as undeliverable with no further\n processing, or a \"delayed\" delivery status notification (DSN) [6] is\n to be issued.\n\n This extension should not be viewed as a vehicle for requesting\n \"priority\" processing. A receiving SMTP server may assign whatever\n processing priority it wishes to a message transmitted with a Deliver\n By request. A Deliver By request serves to express a message's\n urgency and to provide an additional degree of determinancy in its\n processing. An indication of an urgent message's status within a\n 2852 delivery key presentation nested-reference unchanged"},{"id":"IETF RFC 2910","type":"specification","body":"IETF","designation":"RFC 2910","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2910.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2910.txt","https://www.rfc-editor.org/rfc/rfc2910.pdf"],"folder":"IETF/RFC-2910","files":{"txt":{"path":"standards/IETF/RFC-2910/RFC-2910.txt","sha256":"a89d7e91fca1d05d04049ee763fef50ad4ca2e32f2c8203cda6f1001457bae64"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document defines the\n rules for encoding IPP operations and IPP attributes into a new\n Internet mime media type called \"application/ipp\". This document\n also defines the rules for transporting over Hypertext Transfer\n Protocol (HTTP) a message body whose Content-Type is\n \"application/ipp\". This document defines a new scheme named 'ipp' for\n identifying IPP printers and jobs.\n\nHerriot, et al. Standards Track [Page 1]\n\f\nRFC 2910 IPP/1.1: Encoding and Transport September 2000\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the Internet\n Pr","scope_keywords":["2910","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null}],"search_text":"IETF RFC 2910 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document defines the\n rules for encoding IPP operations and IPP attributes into a new\n Internet mime media type called \"application/ipp\". This document\n also defines the rules for transporting over Hypertext Transfer\n Protocol (HTTP) a message body whose Content-Type is\n \"application/ipp\". This document defines a new scheme named 'ipp' for\n identifying IPP printers and jobs.\n\nHerriot, et al. Standards Track [Page 1]\n\f\nRFC 2910 IPP/1.1: Encoding and Transport September 2000\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the Internet\n Pr 2910 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 2920","type":"specification","body":"IETF","designation":"RFC 2920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2920.txt","https://www.rfc-editor.org/rfc/rfc2920.pdf"],"folder":"IETF/RFC-2920","files":{"txt":{"path":"standards/IETF/RFC-2920/RFC-2920.txt","sha256":"679ed54a0afd15b7bbe0f84aa8f2fca620be93b3e4b9bfcfe58b436bde6fedcc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service whereby a server can indicate the extent of its\n ability to accept multiple commands in a single Transmission Control\n Protocol (TCP) send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly.\n\n1. Introduction\n\n Although SMTP is widely and robustly deployed, certain extensions may\n nevertheless prove useful. In particular, many parts of the Internet\n make use of high latency network links. SMTP's intrinsic one\n command-one response structure is significantly penalized by high\n latency links, often to the point where the factors contributing to\n overall connection time are dominated by the time spent waiting for\n responses to individual commands (turnaround time).\n\n In the best of all worlds it would be possible to simply deploy SMTP\n client softwar","scope_keywords":["2920","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 2920 This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service whereby a server can indicate the extent of its\n ability to accept multiple commands in a single Transmission Control\n Protocol (TCP) send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly.\n\n1. Introduction\n\n Although SMTP is widely and robustly deployed, certain extensions may\n nevertheless prove useful. In particular, many parts of the Internet\n make use of high latency network links. SMTP's intrinsic one\n command-one response structure is significantly penalized by high\n latency links, often to the point where the factors contributing to\n overall connection time are dominated by the time spent waiting for\n responses to individual commands (turnaround time).\n\n In the best of all worlds it would be possible to simply deploy SMTP\n client softwar 2920 key nested-reference unchanged"},{"id":"IETF RFC 2960","type":"specification","body":"IETF","designation":"RFC 2960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2960.txt","https://www.rfc-editor.org/rfc/rfc2960.pdf"],"folder":"IETF/RFC-2960","files":{"txt":{"path":"standards/IETF/RFC-2960/RFC-2960.txt","sha256":"928b687dbd58cf1d12217a29e3802f406e7fdf6d3316d8f4169b31f412901915"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Stream Control Transmission Protocol\n (SCTP). SCTP is designed to transport PSTN signaling messages over\n IP networks, but is capable of broader applications.\n\n SCTP is a reliable transport protocol operating on top of a\n connectionless packet network such as IP. It offers the following\n services to its users:\n\n -- acknowledged error-free non-duplicated transfer of user data,\n -- data fragmentation to conform to discovered path MTU size,\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 2960 Stream Control Transmission Protocol October 2000\n\n -- sequenced delivery of user messages within multiple streams,\n with an option for order-of-arrival delivery of individual user\n messages,\n -- optional bundling of multiple user messages into a single SCTP\n packet, and\n -- network-level fault tolerance through supporting of multi-\n homing at either or both ends of an assoc","scope_keywords":["2960","authentication","delivery","key","management","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3309","folder":"IETF/RFC-3309","source":"IETF/RFC-3309/RFC-3309.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3423","folder":"IETF/RFC-3423","source":"IETF/RFC-3423/RFC-3423.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3758","folder":"IETF/RFC-3758","source":"IETF/RFC-3758/RFC-3758.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4296","folder":"IETF/RFC-4296","source":"IETF/RFC-4296/RFC-4296.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4820","folder":"IETF/RFC-4820","source":"IETF/RFC-4820/RFC-4820.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4838","folder":"IETF/RFC-4838","source":"IETF/RFC-4838/RFC-4838.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null}],"search_text":"IETF RFC 2960 This document describes the Stream Control Transmission Protocol\n (SCTP). SCTP is designed to transport PSTN signaling messages over\n IP networks, but is capable of broader applications.\n\n SCTP is a reliable transport protocol operating on top of a\n connectionless packet network such as IP. It offers the following\n services to its users:\n\n -- acknowledged error-free non-duplicated transfer of user data,\n -- data fragmentation to conform to discovered path MTU size,\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 2960 Stream Control Transmission Protocol October 2000\n\n -- sequenced delivery of user messages within multiple streams,\n with an option for order-of-arrival delivery of individual user\n messages,\n -- optional bundling of multiple user messages into a single SCTP\n packet, and\n -- network-level fault tolerance through supporting of multi-\n homing at either or both ends of an assoc 2960 authentication delivery key management path validation nested-reference unchanged"},{"id":"IETF RFC 2993","type":"specification","body":"IETF","designation":"RFC 2993","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2993.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2993.txt","https://www.rfc-editor.org/rfc/rfc2993.pdf"],"folder":"IETF/RFC-2993","files":{"txt":{"path":"standards/IETF/RFC-2993/RFC-2993.txt","sha256":"7fc7fe042ab6c603c217a53b2e54363a0ae0fc13f44c6a62c4ac7e244d6c1a45"}},"tags":["nested-reference","unchanged"],"summary":"In light of the growing interest in, and deployment of network\n address translation (NAT) RFC-1631, this paper will discuss some of\n the architectural implications and guidelines for implementations. It\n is assumed the reader is familiar with the address translation\n concepts presented in RFC-1631.","scope_keywords":["2993","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6832","folder":"IETF/RFC-6832","source":"IETF/RFC-6832/RFC-6832.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 2993 In light of the growing interest in, and deployment of network\n address translation (NAT) RFC-1631, this paper will discuss some of\n the architectural implications and guidelines for implementations. It\n is assumed the reader is familiar with the address translation\n concepts presented in RFC-1631. 2993 management path nested-reference unchanged"},{"id":"IETF RFC 3028","type":"specification","body":"IETF","designation":"RFC 3028","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3028.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3028.txt","https://www.rfc-editor.org/rfc/rfc3028.pdf"],"folder":"IETF/RFC-3028","files":{"txt":{"path":"standards/IETF/RFC-3028/RFC-3028.txt","sha256":"a71cb24f5f332f925811b1ce9b2393a504267c4ec6a7c6850c651de1f062314c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a language for filtering e-mail messages at\n time of final delivery. It is designed to be implementable on either\n a mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Message Access Protocol (IMAP) servers, as it has no\n variables, loops, or ability to shell out to external programs.","scope_keywords":["3028","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3431","folder":"IETF/RFC-3431","source":"IETF/RFC-3431/RFC-3431.txt","version":null},{"body":"IETF","designation":"RFC 3598","folder":"IETF/RFC-3598","source":"IETF/RFC-3598/RFC-3598.txt","version":null},{"body":"IETF","designation":"RFC 3685","folder":"IETF/RFC-3685","source":"IETF/RFC-3685/RFC-3685.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3894","folder":"IETF/RFC-3894","source":"IETF/RFC-3894/RFC-3894.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null}],"search_text":"IETF RFC 3028 This document describes a language for filtering e-mail messages at\n time of final delivery. It is designed to be implementable on either\n a mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Message Access Protocol (IMAP) servers, as it has no\n variables, loops, or ability to shell out to external programs. 3028 delivery nested-reference unchanged"},{"id":"IETF RFC 3191","type":"specification","body":"IETF","designation":"RFC 3191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3191.txt","https://www.rfc-editor.org/rfc/rfc3191.pdf"],"folder":"IETF/RFC-3191","files":{"txt":{"path":"standards/IETF/RFC-3191/RFC-3191.txt","sha256":"6573b200f159fc776b799287f5f11acb2d9c12ff8721a52198faca0d6528db25"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a simple method of encoding Global Switched\n Telephone Network (GSTN) addresses (commonly called \"telephone\n numbers\") in the local-part of Internet email addresses, along with\n an extension mechanism to allow encoding of additional standard\n attributes needed for email gateways to GSTN-based services.\n\n1. Introduction\n\n As with all Internet mail addresses, the left-hand-side (local-part)\n of an address generated according to this specification, is not to be\n interpreted except by an MTA that handles messages for the domain\n given in the right-hand-side.\n\n Since the very first e-mail to GSTN services gateway appeared, a\n number of different methods to specify a GSTN address as an e-mail\n address have been used by implementors. Several objectives for this\n methods have been identified, like to enable an e-mail user to access\n GSTN services from his/her e-mail interface","scope_keywords":["3191","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null}],"search_text":"IETF RFC 3191 This memo describes a simple method of encoding Global Switched\n Telephone Network (GSTN) addresses (commonly called \"telephone\n numbers\") in the local-part of Internet email addresses, along with\n an extension mechanism to allow encoding of additional standard\n attributes needed for email gateways to GSTN-based services.\n\n1. Introduction\n\n As with all Internet mail addresses, the left-hand-side (local-part)\n of an address generated according to this specification, is not to be\n interpreted except by an MTA that handles messages for the domain\n given in the right-hand-side.\n\n Since the very first e-mail to GSTN services gateway appeared, a\n number of different methods to specify a GSTN address as an e-mail\n address have been used by implementors. Several objectives for this\n methods have been identified, like to enable an e-mail user to access\n GSTN services from his/her e-mail interface 3191 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 3192","type":"specification","body":"IETF","designation":"RFC 3192","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3192.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3192.txt","https://www.rfc-editor.org/rfc/rfc3192.pdf"],"folder":"IETF/RFC-3192","files":{"txt":{"path":"standards/IETF/RFC-3192/RFC-3192.txt","sha256":"398998b999c52abdced9bfcda4e72615f97d44ed79e61c6501e9d593be81f009"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a simple method of encoding Global Switched\n Telephone Network (GSTN) addresses of facsimile devices in the\n local-part of Internet email addresses.\n\n1. Introduction\n\n As with all Internet mail addresses, the left-hand-side (local-part)\n of an address generated according to this specification, is not to be\n interpreted except by the MTA that is named on the right-hand-side\n (domain).\n\n Since the very first e-mail to fax gateway objects appeared, a number\n of different methods to specify a fax address as an e-mail address\n have been used by implementors. Several objectives for this methods\n have been identified, like to enable an e-mail user to send and\n receive faxes from his/her e-mail interface, to allow some kind of\n \"fax over e-mail service\" transport (possibly reducing the costs of\n GSTN long distance transmissions) while using the existing e-mail\n infrastructure","scope_keywords":["3192"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 3192 This memo describes a simple method of encoding Global Switched\n Telephone Network (GSTN) addresses of facsimile devices in the\n local-part of Internet email addresses.\n\n1. Introduction\n\n As with all Internet mail addresses, the left-hand-side (local-part)\n of an address generated according to this specification, is not to be\n interpreted except by the MTA that is named on the right-hand-side\n (domain).\n\n Since the very first e-mail to fax gateway objects appeared, a number\n of different methods to specify a fax address as an e-mail address\n have been used by implementors. Several objectives for this methods\n have been identified, like to enable an e-mail user to send and\n receive faxes from his/her e-mail interface, to allow some kind of\n \"fax over e-mail service\" transport (possibly reducing the costs of\n GSTN long distance transmissions) while using the existing e-mail\n infrastructure 3192 nested-reference unchanged"},{"id":"IETF RFC 3219","type":"specification","body":"IETF","designation":"RFC 3219","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3219.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3219.txt","https://www.rfc-editor.org/rfc/rfc3219.pdf"],"folder":"IETF/RFC-3219","files":{"txt":{"path":"standards/IETF/RFC-3219/RFC-3219.txt","sha256":"d44d4ef4549b48c6927cc6355d78c33c0bee6b2bf1e94ac633456d0c3732885c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the Telephony Routing over IP (TRIP). TRIP is\n a policy driven inter-administrative domain protocol for advertising\n the reachability of telephony destinations between location servers,\n and for advertising attributes of the routes to those destinations.\n TRIP's operation is independent of any signaling protocol, hence TRIP\n can serve as the telephony routing protocol for any signaling\n protocol.\n\n The Border Gateway Protocol (BGP-4) is used to distribute routing\n information between administrative domains. TRIP is used to\n distribute telephony routing information between telephony\n administrative domains. The similarity between the two protocols is\n obvious, and hence TRIP is modeled after BGP-4.","scope_keywords":["3219","attribute","attributes","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null}],"search_text":"IETF RFC 3219 This document presents the Telephony Routing over IP (TRIP). TRIP is\n a policy driven inter-administrative domain protocol for advertising\n the reachability of telephony destinations between location servers,\n and for advertising attributes of the routes to those destinations.\n TRIP's operation is independent of any signaling protocol, hence TRIP\n can serve as the telephony routing protocol for any signaling\n protocol.\n\n The Border Gateway Protocol (BGP-4) is used to distribute routing\n information between administrative domains. TRIP is used to\n distribute telephony routing information between telephony\n administrative domains. The similarity between the two protocols is\n obvious, and hence TRIP is modeled after BGP-4. 3219 attribute attributes key path policy nested-reference unchanged"},{"id":"IETF RFC 3261","type":"specification","body":"IETF","designation":"RFC 3261","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3261.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3261.txt","https://www.rfc-editor.org/rfc/rfc3261.pdf"],"folder":"IETF/RFC-3261","files":{"txt":{"path":"standards/IETF/RFC-3261/RFC-3261.txt","sha256":"d513777f77fea01a4de9c0a2d9d6713cb53b8231f1b7a2ab56705f8d51b066dc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Session Initiation Protocol (SIP), an\n application-layer control (signaling) protocol for creating,\n modifying, and terminating sessions with one or more participants.\n These sessions include Internet telephone calls, multimedia\n distribution, and multimedia conferences.\n\n SIP invitations used to create sessions carry session descriptions\n that allow participants to agree on a set of compatible media types.\n SIP makes use of elements called proxy servers to help route requests\n to the user's current location, authenticate and authorize users for\n services, implement provider call-routing policies, and provide\n features to users. SIP also provides a registration function that\n allows users to upload their current locations for use by proxy\n servers. SIP runs on top of several different transport protocols.\n\nRosenberg, et. al. Standards Track [Page 1]\n\f\nRFC 3261 SIP","scope_keywords":["3261","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"IETF","designation":"RFC 3262","folder":"IETF/RFC-3262","source":"IETF/RFC-3262/RFC-3262.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3310","folder":"IETF/RFC-3310","source":"IETF/RFC-3310/RFC-3310.txt","version":null},{"body":"IETF","designation":"RFC 3311","folder":"IETF/RFC-3311","source":"IETF/RFC-3311/RFC-3311.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3321","folder":"IETF/RFC-3321","source":"IETF/RFC-3321/RFC-3321.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3324","folder":"IETF/RFC-3324","source":"IETF/RFC-3324/RFC-3324.txt","version":null},{"body":"IETF","designation":"RFC 3325","folder":"IETF/RFC-3325","source":"IETF/RFC-3325/RFC-3325.txt","version":null},{"body":"IETF","designation":"RFC 3326","folder":"IETF/RFC-3326","source":"IETF/RFC-3326/RFC-3326.txt","version":null},{"body":"IETF","designation":"RFC 3327","folder":"IETF/RFC-3327","source":"IETF/RFC-3327/RFC-3327.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3351","folder":"IETF/RFC-3351","source":"IETF/RFC-3351/RFC-3351.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3362","folder":"IETF/RFC-3362","source":"IETF/RFC-3362/RFC-3362.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3427","folder":"IETF/RFC-3427","source":"IETF/RFC-3427/RFC-3427.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3486","folder":"IETF/RFC-3486","source":"IETF/RFC-3486/RFC-3486.txt","version":null},{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3515","folder":"IETF/RFC-3515","source":"IETF/RFC-3515/RFC-3515.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3524","folder":"IETF/RFC-3524","source":"IETF/RFC-3524/RFC-3524.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3574","folder":"IETF/RFC-3574","source":"IETF/RFC-3574/RFC-3574.txt","version":null},{"body":"IETF","designation":"RFC 3578","folder":"IETF/RFC-3578","source":"IETF/RFC-3578/RFC-3578.txt","version":null},{"body":"IETF","designation":"RFC 3581","folder":"IETF/RFC-3581","source":"IETF/RFC-3581/RFC-3581.txt","version":null},{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3608","folder":"IETF/RFC-3608","source":"IETF/RFC-3608/RFC-3608.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3665","folder":"IETF/RFC-3665","source":"IETF/RFC-3665/RFC-3665.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3857","folder":"IETF/RFC-3857","source":"IETF/RFC-3857/RFC-3857.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 3969","folder":"IETF/RFC-3969","source":"IETF/RFC-3969/RFC-3969.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4077","folder":"IETF/RFC-4077","source":"IETF/RFC-4077/RFC-4077.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4091","folder":"IETF/RFC-4091","source":"IETF/RFC-4091/RFC-4091.txt","version":null},{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4245","folder":"IETF/RFC-4245","source":"IETF/RFC-4245/RFC-4245.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4320","folder":"IETF/RFC-4320","source":"IETF/RFC-4320/RFC-4320.txt","version":null},{"body":"IETF","designation":"RFC 4321","folder":"IETF/RFC-4321","source":"IETF/RFC-4321/RFC-4321.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4376","folder":"IETF/RFC-4376","source":"IETF/RFC-4376/RFC-4376.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4453","folder":"IETF/RFC-4453","source":"IETF/RFC-4453/RFC-4453.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4475","folder":"IETF/RFC-4475","source":"IETF/RFC-4475/RFC-4475.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4488","folder":"IETF/RFC-4488","source":"IETF/RFC-4488/RFC-4488.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4759","folder":"IETF/RFC-4759","source":"IETF/RFC-4759/RFC-4759.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 4904","folder":"IETF/RFC-4904","source":"IETF/RFC-4904/RFC-4904.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4967","folder":"IETF/RFC-4967","source":"IETF/RFC-4967/RFC-4967.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5167","folder":"IETF/RFC-5167","source":"IETF/RFC-5167/RFC-5167.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7375","folder":"IETF/RFC-7375","source":"IETF/RFC-7375/RFC-7375.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 3261 This document describes Session Initiation Protocol (SIP), an\n application-layer control (signaling) protocol for creating,\n modifying, and terminating sessions with one or more participants.\n These sessions include Internet telephone calls, multimedia\n distribution, and multimedia conferences.\n\n SIP invitations used to create sessions carry session descriptions\n that allow participants to agree on a set of compatible media types.\n SIP makes use of elements called proxy servers to help route requests\n to the user's current location, authenticate and authorize users for\n services, implement provider call-routing policies, and provide\n features to users. SIP also provides a registration function that\n allows users to upload their current locations for use by proxy\n servers. SIP runs on top of several different transport protocols.\n\nRosenberg, et. al. Standards Track [Page 1]\n\f\nRFC 3261 SIP 3261 policies nested-reference unchanged"},{"id":"IETF RFC 3339","type":"specification","body":"IETF","designation":"RFC 3339","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3339.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3339.txt","https://www.rfc-editor.org/rfc/rfc3339.pdf"],"folder":"IETF/RFC-3339","files":{"txt":{"path":"standards/IETF/RFC-3339/RFC-3339.txt","sha256":"9ab2b8864a85dca73a88f49b0927bc7bc85f596926e4fd1890905777924e700a"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document defines a date and time format for use in Internet\n protocols that is a profile of the ISO 8601 standard for\n representation of dates and times using the Gregorian calendar.","scope_keywords":["3339","key","presentation","profile","qualified","timestamp","timestamps"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5277","folder":"IETF/RFC-5277","source":"IETF/RFC-5277/RFC-5277.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8943","folder":"IETF/RFC-8943","source":"IETF/RFC-8943/RFC-8943.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 3339 This document defines a date and time format for use in Internet\n protocols that is a profile of the ISO 8601 standard for\n representation of dates and times using the Gregorian calendar. 3339 key presentation profile qualified timestamp timestamps cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 3461","type":"specification","body":"IETF","designation":"RFC 3461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3461.txt","https://www.rfc-editor.org/rfc/rfc3461.pdf"],"folder":"IETF/RFC-3461","files":{"txt":{"path":"standards/IETF/RFC-3461/RFC-3461.txt","sha256":"7f9e2050ae8c38962d458bb4ee669100351e981f55a96e41f19cbb574b1c730d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service, which allows an SMTP client to specify (a) that\n Delivery Status Notifications (DSNs) should be generated under\n certain conditions, (b) whether such notifications should return the\n contents of the message, and (c) additional information, to be\n returned with a DSN, that allows the sender to identify both the\n recipient(s) for which the DSN was issued, and the transaction in\n which the original message was sent.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [7].","scope_keywords":["3461","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null}],"search_text":"IETF RFC 3461 This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service, which allows an SMTP client to specify (a) that\n Delivery Status Notifications (DSNs) should be generated under\n certain conditions, (b) whether such notifications should return the\n contents of the message, and (c) additional information, to be\n returned with a DSN, that allows the sender to identify both the\n recipient(s) for which the DSN was issued, and the transaction in\n which the original message was sent.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [7]. 3461 delivery key nested-reference unchanged"},{"id":"IETF RFC 3507","type":"specification","body":"IETF","designation":"RFC 3507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3507.txt","https://www.rfc-editor.org/rfc/rfc3507.pdf"],"folder":"IETF/RFC-3507","files":{"txt":{"path":"standards/IETF/RFC-3507/RFC-3507.txt","sha256":"368926be1e68abc96b879c25702ef192d8161037d626b18da85387236726afda"}},"tags":["nested-reference","unchanged"],"summary":"ICAP, the Internet Content Adaption Protocol, is a protocol aimed at\n providing simple object-based content vectoring for HTTP services.\n ICAP is, in essence, a lightweight protocol for executing a \"remote\n procedure call\" on HTTP messages. It allows ICAP clients to pass\n HTTP messages to ICAP servers for some sort of transformation or\n other processing (\"adaptation\"). The server executes its\n transformation service on messages and sends back responses to the\n client, usually with modified messages. Typically, the adapted\n messages are either HTTP requests or HTTP responses.\n\nElson & Cerpa Informational [Page 1]\n\f\nRFC 3507 ICAP April 2003","scope_keywords":["3507","authentication","encryption","http","policy","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null}],"search_text":"IETF RFC 3507 ICAP, the Internet Content Adaption Protocol, is a protocol aimed at\n providing simple object-based content vectoring for HTTP services.\n ICAP is, in essence, a lightweight protocol for executing a \"remote\n procedure call\" on HTTP messages. It allows ICAP clients to pass\n HTTP messages to ICAP servers for some sort of transformation or\n other processing (\"adaptation\"). The server executes its\n transformation service on messages and sends back responses to the\n client, usually with modified messages. Typically, the adapted\n messages are either HTTP requests or HTTP responses.\n\nElson & Cerpa Informational [Page 1]\n\f\nRFC 3507 ICAP April 2003 3507 authentication encryption http policy validation nested-reference unchanged"},{"id":"IETF RFC 3731","type":"specification","body":"IETF","designation":"RFC 3731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3731.txt","https://www.rfc-editor.org/rfc/rfc3731.pdf"],"folder":"IETF/RFC-3731","files":{"txt":{"path":"standards/IETF/RFC-3731/RFC-3731.txt","sha256":"b244a401baf0b730ea7e1c4a7ee20155d6faef54285e6a8886bd315d7f6d4723"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names.","scope_keywords":["3731","attribute","attributes","authorization","management","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null}],"search_text":"IETF RFC 3731 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of Internet domain names\n stored in a shared central repository. Specified in XML, the mapping\n defines EPP command syntax and semantics as applied to domain names. 3731 attribute attributes authorization management qualified subject nested-reference unchanged"},{"id":"IETF RFC 3868","type":"specification","body":"IETF","designation":"RFC 3868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3868.txt","https://www.rfc-editor.org/rfc/rfc3868.pdf"],"folder":"IETF/RFC-3868","files":{"txt":{"path":"standards/IETF/RFC-3868/RFC-3868.txt","sha256":"33820ed4c06b7dc177345dbaa40678e1fa18bb7bf4d99a47407be49d33b65b22"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a protocol for the transport of any Signalling\n Connection Control Part-User signalling over IP using the Stream\n Control Transmission Protocol. The protocol is designed to be\n modular and symmetric, to allow it to work in diverse architectures,\n such as a Signalling Gateway to IP Signalling Endpoint architecture\n as well as a peer-to-peer IP Signalling Endpoint architecture.\n\nLoughney, et al. Standards Track [Page 1]\n\f\nRFC 3868 SUA October 2004","scope_keywords":["3868","delivery","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3868 This document defines a protocol for the transport of any Signalling\n Connection Control Part-User signalling over IP using the Stream\n Control Transmission Protocol. The protocol is designed to be\n modular and symmetric, to allow it to work in diverse architectures,\n such as a Signalling Gateway to IP Signalling Endpoint architecture\n as well as a peer-to-peer IP Signalling Endpoint architecture.\n\nLoughney, et al. Standards Track [Page 1]\n\f\nRFC 3868 SUA October 2004 3868 delivery key management nested-reference unchanged"},{"id":"IETF RFC 3886","type":"specification","body":"IETF","designation":"RFC 3886","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3886.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3886.txt","https://www.rfc-editor.org/rfc/rfc3886.pdf"],"folder":"IETF/RFC-3886","files":{"txt":{"path":"standards/IETF/RFC-3886/RFC-3886.txt","sha256":"936aa7db35541816ca03d338ff8004ef7fdad9ea9144bd2aa8edd5443cbd2b14"}},"tags":["nested-reference","unchanged"],"summary":"Message Tracking is expected to be used to determine the status of\n undelivered e-mail upon request. Tracking is used in conjunction\n with Delivery Status Notifications (DSN) and Message Disposition\n Notifications (MDN); generally, a message tracking request will be\n issued only when a DSN or MDN has not been received within a\n reasonable timeout period.\n\n This memo defines a MIME content-type for message tracking status in\n the same spirit as RFC 3464, \"An Extensible Message Format for\n Delivery Status Notifications\". It is to be issued upon a request as\n described in \"Message Tracking Query Protocol\". This memo defines\n only the format of the status information. An extension to SMTP to\n label messages for further tracking and request tracking status is\n defined in a separate memo.\n\nAllman Standards Track [Page 1]\n\f\nRFC 3886 Message/Tracking-Status September 2004\n\n1. Introduction\n\n Mess","scope_keywords":["3886","crl","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null}],"search_text":"IETF RFC 3886 Message Tracking is expected to be used to determine the status of\n undelivered e-mail upon request. Tracking is used in conjunction\n with Delivery Status Notifications (DSN) and Message Disposition\n Notifications (MDN); generally, a message tracking request will be\n issued only when a DSN or MDN has not been received within a\n reasonable timeout period.\n\n This memo defines a MIME content-type for message tracking status in\n the same spirit as RFC 3464, \"An Extensible Message Format for\n Delivery Status Notifications\". It is to be issued upon a request as\n described in \"Message Tracking Query Protocol\". This memo defines\n only the format of the status information. An extension to SMTP to\n label messages for further tracking and request tracking status is\n defined in a separate memo.\n\nAllman Standards Track [Page 1]\n\f\nRFC 3886 Message/Tracking-Status September 2004\n\n1. Introduction\n\n Mess 3886 crl delivery key nested-reference unchanged"},{"id":"IETF RFC 3965","type":"specification","body":"IETF","designation":"RFC 3965","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3965.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3965.txt","https://www.rfc-editor.org/rfc/rfc3965.pdf"],"folder":"IETF/RFC-3965","files":{"txt":{"path":"standards/IETF/RFC-3965/RFC-3965.txt","sha256":"1a6d822168eef5fdec566cbba9569f7c487123f259b686f55a4528b08c19dd04"}},"tags":["nested-reference","unchanged"],"summary":"This specification provides for \"simple mode\" carriage of facsimile\n data using Internet mail. Extensions to this document will follow.\n The current specification employs standard protocols and file formats\n such as TCP/IP, Internet mail protocols, Multipurpose Internet Mail\n Extensions (MIME), and Tagged Image File Format (TIFF) for Facsimile.\n It can send images not only to other Internet-aware facsimile devices\n but also to Internet-native systems, such as PCs with common email\n readers which can handle MIME mail and TIFF for Facsimile data. The\n specification facilitates communication among existing facsimile\n devices, Internet mail agents, and the gateways which connect them.\n\n This document is a revision of RFC 2305. There have been no\n technical changes.\n\n1. Introduction\n\n This specification defines message-based facsimile communication over\n the Internet. It describes a minimum s","scope_keywords":["3965","delivery","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 4143","folder":"IETF/RFC-4143","source":"IETF/RFC-4143/RFC-4143.txt","version":null}],"search_text":"IETF RFC 3965 This specification provides for \"simple mode\" carriage of facsimile\n data using Internet mail. Extensions to this document will follow.\n The current specification employs standard protocols and file formats\n such as TCP/IP, Internet mail protocols, Multipurpose Internet Mail\n Extensions (MIME), and Tagged Image File Format (TIFF) for Facsimile.\n It can send images not only to other Internet-aware facsimile devices\n but also to Internet-native systems, such as PCs with common email\n readers which can handle MIME mail and TIFF for Facsimile data. The\n specification facilitates communication among existing facsimile\n devices, Internet mail agents, and the gateways which connect them.\n\n This document is a revision of RFC 2305. There have been no\n technical changes.\n\n1. Introduction\n\n This specification defines message-based facsimile communication over\n the Internet. It describes a minimum s 3965 delivery key profile nested-reference unchanged"},{"id":"IETF RFC 4409","type":"specification","body":"IETF","designation":"RFC 4409","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4409.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4409.txt","https://www.rfc-editor.org/rfc/rfc4409.pdf"],"folder":"IETF/RFC-4409","files":{"txt":{"path":"standards/IETF/RFC-4409/RFC-4409.txt","sha256":"74cb8707f5ac5872c32f3293a34a9ea8fc1fe312c89779d361fa336da23181a5"}},"tags":["nested-reference","unchanged"],"summary":"This memo splits message submission from message relay, allowing each\n service to operate according to its own rules (for security, policy,\n etc.), and specifies what actions are to be taken by a submission\n server.\n\n Message relay and final delivery are unaffected, and continue to use\n SMTP over port 25.\n\n When conforming to this document, message submission uses the\n protocol specified here, normally over port 587.\n\n This separation of function offers a number of benefits, including\n the ability to apply specific security or policy requirements.\n\nGellens & Klensin Standards Track [Page 1]\n\f\nRFC 4409 Message Submission for Mail April 2006","scope_keywords":["4409","authentication","authorization","delivery","identification","path","policies","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 4409 This memo splits message submission from message relay, allowing each\n service to operate according to its own rules (for security, policy,\n etc.), and specifies what actions are to be taken by a submission\n server.\n\n Message relay and final delivery are unaffected, and continue to use\n SMTP over port 25.\n\n When conforming to this document, message submission uses the\n protocol specified here, normally over port 587.\n\n This separation of function offers a number of benefits, including\n the ability to apply specific security or policy requirements.\n\nGellens & Klensin Standards Track [Page 1]\n\f\nRFC 4409 Message Submission for Mail April 2006 4409 authentication authorization delivery identification path policies policy qualified nested-reference unchanged"},{"id":"IETF RFC 4483","type":"specification","body":"IETF","designation":"RFC 4483","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4483.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4483.txt","https://www.rfc-editor.org/rfc/rfc4483.pdf"],"folder":"IETF/RFC-4483","files":{"txt":{"path":"standards/IETF/RFC-4483/RFC-4483.txt","sha256":"0ecb6f1a443afe9e8a1ca0b06fe99b704f24f2b728f12db0788a790103abbd17"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the URL MIME External-Body\n Access-Type to satisfy the content indirection requirements for the\n Session Initiation Protocol (SIP). These extensions are aimed at\n allowing any MIME part in a SIP message to be referred to indirectly\n via a URI.","scope_keywords":["4483","attribute","attributes","hash","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 4483 This document defines an extension to the URL MIME External-Body\n Access-Type to satisfy the content indirection requirements for the\n Session Initiation Protocol (SIP). These extensions are aimed at\n allowing any MIME part in a SIP message to be referred to indirectly\n via a URI. 4483 attribute attributes hash http key nested-reference unchanged"},{"id":"IETF RFC 5031","type":"specification","body":"IETF","designation":"RFC 5031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5031.txt","https://www.rfc-editor.org/rfc/rfc5031.pdf"],"folder":"IETF/RFC-5031","files":{"txt":{"path":"standards/IETF/RFC-5031/RFC-5031.txt","sha256":"3b75fdc5a26b75813f1c84c946248ad7ab9aadca5fabdc45edb335c26ce66d02"}},"tags":["nested-reference","unchanged"],"summary":"The content of many communication services depends on the context,\n such as the user's location. We describe a 'service' URN that allows\n well-known context-dependent services that can be resolved in a\n distributed manner to be identified. Examples include emergency\n services, directory assistance, and call-before-you-dig hot lines.","scope_keywords":["5031","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5031 The content of many communication services depends on the context,\n such as the user's location. We describe a 'service' URN that allows\n well-known context-dependent services that can be resolved in a\n distributed manner to be identified. Examples include emergency\n services, directory assistance, and call-before-you-dig hot lines. 5031 delivery key nested-reference unchanged"},{"id":"IETF RFC 6648","type":"specification","body":"IETF","designation":"RFC 6648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6648.txt","https://www.rfc-editor.org/rfc/rfc6648.pdf"],"folder":"IETF/RFC-6648","files":{"txt":{"path":"standards/IETF/RFC-6648/RFC-6648.txt","sha256":"f826d22153c972b27df0045e95266173953eb10e9274cb296b7bac364185ef88"}},"tags":["nested-reference","unchanged"],"summary":"Historically, designers and implementers of application protocols\n have often distinguished between standardized and unstandardized\n parameters by prefixing the names of unstandardized parameters with\n the string \"X-\" or similar constructs. In practice, that convention\n causes more problems than it solves. Therefore, this document\n deprecates the convention for newly defined parameters with textual\n (as opposed to numerical) names in application protocols.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of th","scope_keywords":["6648","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"IETF RFC 6648 Historically, designers and implementers of application protocols\n have often distinguished between standardized and unstandardized\n parameters by prefixing the names of unstandardized parameters with\n the string \"X-\" or similar constructs. In practice, that convention\n causes more problems than it solves. Therefore, this document\n deprecates the convention for newly defined parameters with textual\n (as opposed to numerical) names in application protocols.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of th 6648 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6912","type":"specification","body":"IETF","designation":"RFC 6912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6912.txt","https://www.rfc-editor.org/rfc/rfc6912.pdf"],"folder":"IETF/RFC-6912","files":{"txt":{"path":"standards/IETF/RFC-6912/RFC-6912.txt","sha256":"73fb03738aa93a9c04a13b1d5ae1ea68508ab6ab0384b5b342051b8b22cd941e"}},"tags":["nested-reference","unchanged"],"summary":"Internationalized Domain Names in Applications (IDNA) makes available\n to DNS zone administrators a very wide range of Unicode code points.\n Most operators of zones should probably not permit registration of\n U-labels using the entire range. This is especially true of zones\n that accept registrations across organizational boundaries, such as\n top-level domains and, most importantly, the root. It is\n unfortunately not possible to generate algorithms to determine\n whether permitting a code point presents a low risk. This memo\n presents a set of principles that can be used to guide the decision\n of whether a Unicode code point may be wisely included in the\n repertoire of permissible code points in a U-label in a zone.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Interne","scope_keywords":["6912","algorithm","algorithms","http","license","policies","presentation","qualified","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 6912 Internationalized Domain Names in Applications (IDNA) makes available\n to DNS zone administrators a very wide range of Unicode code points.\n Most operators of zones should probably not permit registration of\n U-labels using the entire range. This is especially true of zones\n that accept registrations across organizational boundaries, such as\n top-level domains and, most importantly, the root. It is\n unfortunately not possible to generate algorithms to determine\n whether permitting a code point presents a low risk. This memo\n presents a set of principles that can be used to guide the decision\n of whether a Unicode code point may be wisely included in the\n repertoire of permissible code points in a U-label in a zone.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Interne 6912 algorithm algorithms http license policies presentation qualified risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7089","type":"specification","body":"IETF","designation":"RFC 7089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7089.txt","https://www.rfc-editor.org/rfc/rfc7089.pdf"],"folder":"IETF/RFC-7089","files":{"txt":{"path":"standards/IETF/RFC-7089/RFC-7089.txt","sha256":"c3c7b7f2c495dce0fad758dac34dcc1eef3623d13c9ef346e19b30dbbbe801dc"}},"tags":["nested-reference","unchanged"],"summary":"The HTTP-based Memento framework bridges the present and past Web.\n It facilitates obtaining representations of prior states of a given\n resource by introducing datetime negotiation and TimeMaps. Datetime\n negotiation is a variation on content negotiation that leverages the\n given resource's URI and a user agent's preferred datetime. TimeMaps\n are lists that enumerate URIs of resources that encapsulate prior\n states of the given resource. The framework also facilitates\n recognizing a resource that encapsulates a frozen prior state of\n another resource.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementat","scope_keywords":["7089","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null}],"search_text":"IETF RFC 7089 The HTTP-based Memento framework bridges the present and past Web.\n It facilitates obtaining representations of prior states of a given\n resource by introducing datetime negotiation and TimeMaps. Datetime\n negotiation is a variation on content negotiation that leverages the\n given resource's URI and a user agent's preferred datetime. TimeMaps\n are lists that enumerate URIs of resources that encapsulate prior\n states of the given resource. The framework also facilitates\n recognizing a resource that encapsulates a frozen prior state of\n another resource.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementat 7089 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1126","type":"specification","body":"IETF","designation":"RFC 1126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1126.txt","https://www.rfc-editor.org/rfc/rfc1126.pdf"],"folder":"IETF/RFC-1126","files":{"txt":{"path":"standards/IETF/RFC-1126/RFC-1126.txt","sha256":"b40d398cf54528cc48215fac9e11a2084a3e139c64cfb762af8e4a2d3f611fd8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Little\nRequest for Comments: 1126 SAIC\n October 1989\n\n Goals and Functional Requirements for\n Inter-Autonomous System Routing\n\nStatus of this Memo\n\n This document describes the functional requirements for a routing\n protocol to be used between autonomous systems. This document is\n intended as a necessary precursor to the design of a new inter-\n autonomous system routing protocol and specifies requirements for the\n Internet applicable for use with the current DoD IP, the ISO IP, and\n future Internet Protocols. It is intended that these requirements\n will form the basis for the future development of a new inter-\n autonomous systems routing architecture and protocol. This document\n is being circulated to the IETF and Internet community for comment.\n Comments should be sent to: \"open-rout-editor@bbn.com\". This memo\n does not specify a standard. Distribution of this m","scope_keywords":["1126","delivery","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null}],"search_text":"IETF RFC 1126 Network Working Group M. Little\nRequest for Comments: 1126 SAIC\n October 1989\n\n Goals and Functional Requirements for\n Inter-Autonomous System Routing\n\nStatus of this Memo\n\n This document describes the functional requirements for a routing\n protocol to be used between autonomous systems. This document is\n intended as a necessary precursor to the design of a new inter-\n autonomous system routing protocol and specifies requirements for the\n Internet applicable for use with the current DoD IP, the ISO IP, and\n future Internet Protocols. It is intended that these requirements\n will form the basis for the future development of a new inter-\n autonomous systems routing architecture and protocol. This document\n is being circulated to the IETF and Internet community for comment.\n Comments should be sent to: \"open-rout-editor@bbn.com\". This memo\n does not specify a standard. Distribution of this m 1126 delivery policies nested-reference unchanged"},{"id":"IETF RFC 1128","type":"specification","body":"IETF","designation":"RFC 1128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1128.txt","https://www.rfc-editor.org/rfc/rfc1128.pdf"],"folder":"IETF/RFC-1128","files":{"pdf":{"path":"standards/IETF/RFC-1128/RFC-1128.pdf","sha256":"82b21dda67458c6203352a21a69a59ef521e50e2182ff07e3af6d38960669ef1"},"txt":{"path":"standards/IETF/RFC-1128/RFC-1128.txt","sha256":"69a112be70aa9d6d22e0083ab1cb9da56f57cd666bfb54f577a9ddcb3bf1ab29"}},"tags":["nested-reference","unchanged"],"summary":"RFC-1128 \"Measured Performance of the Network Time Protocol in the\nInternet System\"\n\nis available only in PostScript form in the file\n\nRFC1128.PS\n\nTo obtain this file via the NIC's automatic mail server SERVICE, use\nthe Subject line: SEND RFC:RFCnnnn.PS (where nnnn is the number of\nthe RFC you wish to obtain).","scope_keywords":["1128","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1165","folder":"IETF/RFC-1165","source":"IETF/RFC-1165/RFC-1165.txt","version":null},{"body":"IETF","designation":"RFC 1257","folder":"IETF/RFC-1257","source":"IETF/RFC-1257/RFC-1257.txt","version":null}],"search_text":"IETF RFC 1128 RFC-1128 \"Measured Performance of the Network Time Protocol in the\nInternet System\"\n\nis available only in PostScript form in the file\n\nRFC1128.PS\n\nTo obtain this file via the NIC's automatic mail server SERVICE, use\nthe Subject line: SEND RFC:RFCnnnn.PS (where nnnn is the number of\nthe RFC you wish to obtain). 1128 subject nested-reference unchanged"},{"id":"IETF RFC 1257","type":"specification","body":"IETF","designation":"RFC 1257","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1257.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1257.txt","https://www.rfc-editor.org/rfc/rfc1257.pdf"],"folder":"IETF/RFC-1257","files":{"txt":{"path":"standards/IETF/RFC-1257/RFC-1257.txt","sha256":"bee57058852f6c43e525c5feec4ec66843b7d7c0f33156c262bcc681c7c51ea2"}},"tags":["nested-reference","unchanged"],"summary":"This memo argues that jitter control is not required for networks to\n support isochronous applications. A network providing bandwidth and\n bounds delay is sufficient. The implications for gigabit\n internetworking protocols are briefly considered.","scope_keywords":["1257","delivery","key","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null}],"search_text":"IETF RFC 1257 This memo argues that jitter control is not required for networks to\n support isochronous applications. A network providing bandwidth and\n bounds delay is sufficient. The implications for gigabit\n internetworking protocols are briefly considered. 1257 delivery key path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 1129","type":"specification","body":"IETF","designation":"RFC 1129","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1129.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1129.txt","https://www.rfc-editor.org/rfc/rfc1129.pdf"],"folder":"IETF/RFC-1129","files":{"pdf":{"path":"standards/IETF/RFC-1129/RFC-1129.pdf","sha256":"0e5562ecfd47e73cdf582888daba38f377870d0b6673d0c4d54462bd320495e2"},"txt":{"path":"standards/IETF/RFC-1129/RFC-1129.txt","sha256":"31fee73b873cb5669d12bd61ceb3cae03985afd8876d5adf945fe9ed2e894e5d"}},"tags":["nested-reference","unchanged"],"summary":"RFC 1129, \"Internet Time Synchronization: The Network Time Protocol\"\n\nis not available in ASCII format. It is available in PostScript and\nPDF formats in the files: rfc1129.ps and rfc1129.pdf, respectively.","scope_keywords":["1129"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1165","folder":"IETF/RFC-1165","source":"IETF/RFC-1165/RFC-1165.txt","version":null}],"search_text":"IETF RFC 1129 RFC 1129, \"Internet Time Synchronization: The Network Time Protocol\"\n\nis not available in ASCII format. It is available in PostScript and\nPDF formats in the files: rfc1129.ps and rfc1129.pdf, respectively. 1129 nested-reference unchanged"},{"id":"IETF RFC 113","type":"specification","body":"IETF","designation":"RFC 113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc113.txt","https://www.rfc-editor.org/rfc/rfc113.pdf"],"folder":"IETF/RFC-113","files":{"txt":{"path":"standards/IETF/RFC-113/RFC-113.txt","sha256":"3064412c38fdda655f7e74ec57f3f6db58f6255595d85c190ce3492c5a33c84f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 5 April 1971\nRequest for Comments: 113 E. F. Harslem\nNIC 5820 J. F. Heafner\n J. E. White\n\n NETWORK ACTIVITY REPORT: UCSB RAND\n\nUCSB RJE/RJOR\n\n The UCSB Remote Job Entry (RJE) and Remote Job Out- put\nRetrieval (RJOR) Systems described in NWG/RFC #105 have been used and\nvalidated from Rand. The facility is now being used on a limited\nbasis as a production tool by another research group at Rand.\n Access to the UCSB facility from Rand is through the Network\nService Program (NSP). This program is driven by Rand Video-Graphic\nconsoles and allows a console user access to both local file storage\n(at Rand) and to the Network. A small module (UCSBMGR) was added to\nNSP to handle the UCSB RJE and RJOR protocols and data formats.\n In exercising the RJE/RJOR facility over the past two months,\ntypical job sizes included input decks of 800 to 2800 80-character\ncard images and outpu","scope_keywords":["113","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 140","folder":"IETF/RFC-140","source":"IETF/RFC-140/RFC-140.txt","version":null}],"search_text":"IETF RFC 113 Network Working Group 5 April 1971\nRequest for Comments: 113 E. F. Harslem\nNIC 5820 J. F. Heafner\n J. E. White\n\n NETWORK ACTIVITY REPORT: UCSB RAND\n\nUCSB RJE/RJOR\n\n The UCSB Remote Job Entry (RJE) and Remote Job Out- put\nRetrieval (RJOR) Systems described in NWG/RFC #105 have been used and\nvalidated from Rand. The facility is now being used on a limited\nbasis as a production tool by another research group at Rand.\n Access to the UCSB facility from Rand is through the Network\nService Program (NSP). This program is driven by Rand Video-Graphic\nconsoles and allows a console user access to both local file storage\n(at Rand) and to the Network. A small module (UCSBMGR) was added to\nNSP to handle the UCSB RJE and RJOR protocols and data formats.\n In exercising the RJE/RJOR facility over the past two months,\ntypical job sizes included input decks of 800 to 2800 80-character\ncard images and outpu 113 path nested-reference unchanged"},{"id":"IETF RFC 140","type":"specification","body":"IETF","designation":"RFC 140","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc140.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc140.txt","https://www.rfc-editor.org/rfc/rfc140.pdf"],"folder":"IETF/RFC-140","files":{"txt":{"path":"standards/IETF/RFC-140/RFC-140.txt","sha256":"407fb0815bf22670cd8a81ecb174558db87e7354a8bb10bc329d28ee2f133d10"}},"tags":["nested-reference","unchanged"],"summary":"NWG Steve Crocker\nRFC - 140 UCLA\nNIC - 6725 4 May 71\n\n AGENDA FOR THE MAY NWG MEETING\n ------------------------------\n\n The NWG meeting will be from 8 p.m., Sunday, May 16 through\nWednesday evening May 19. All meetings except Sunday night will take\nplace in the Wicker Room of the Dennis Hotel. The Sunday even- ing\nmeeting will take place in the Royal Box Room of the Dennis Hotel.\nEvening meetings will start at 8 p.m. Afternoon meetings at 1:30 p.m.\nand morning meetings at 9 a.m. We will meet Sunday evening, all day\nMonday (three sessions), Tuesday morning and evening and Wednesday\nevening. At times when we are not meeting you are invited to use the\nWicker Room for private meetings or whatever. It is reserved thru\nThursday afternoon.\n\n Below are the topics to be discussed in each meeting and the list\nof relevant RFC numbers which should be read prior to coming.\n\nTIME: Sunday evening\nTITLE","scope_keywords":["140","delivery","management","policies","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 140 NWG Steve Crocker\nRFC - 140 UCLA\nNIC - 6725 4 May 71\n\n AGENDA FOR THE MAY NWG MEETING\n ------------------------------\n\n The NWG meeting will be from 8 p.m., Sunday, May 16 through\nWednesday evening May 19. All meetings except Sunday night will take\nplace in the Wicker Room of the Dennis Hotel. The Sunday even- ing\nmeeting will take place in the Royal Box Room of the Dennis Hotel.\nEvening meetings will start at 8 p.m. Afternoon meetings at 1:30 p.m.\nand morning meetings at 9 a.m. We will meet Sunday evening, all day\nMonday (three sessions), Tuesday morning and evening and Wednesday\nevening. At times when we are not meeting you are invited to use the\nWicker Room for private meetings or whatever. It is reserved thru\nThursday afternoon.\n\n Below are the topics to be discussed in each meeting and the list\nof relevant RFC numbers which should be read prior to coming.\n\nTIME: Sunday evening\nTITLE 140 delivery management policies presentation subject nested-reference unchanged"},{"id":"IETF RFC 1245","type":"specification","body":"IETF","designation":"RFC 1245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1245.txt","https://www.rfc-editor.org/rfc/rfc1245.pdf"],"folder":"IETF/RFC-1245","files":{"pdf":{"path":"standards/IETF/RFC-1245/RFC-1245.pdf","sha256":"a2cc20cb24a5dfe5566d586c073134e2c3dce96d1d779d15ed1aee1a62f06bf5"},"txt":{"path":"standards/IETF/RFC-1245/RFC-1245.txt","sha256":"7ea2c3fe7dde351a32750272212b6a223c3f6e19852932f0c22371369a9278f7"}},"tags":["nested-reference","unchanged"],"summary":"This is the first of two reports on the OSPF protocol. These reports are\nrequired by the IAB/ IESG in order for an Internet routing protocol to\nadvance to Draft Standard Status. OSPF is a TCP/IP routing protocol,\ndesigned to be used internal to an Autonomous System (in other words,\nOSPF is an Interior Gateway Protocol).\n\nVersion 1 of the OSPF protocol was published in RFC 1131. Since then\nOSPF version 2 has been developed. Version 2 has been documented in RFC\n1247. The changes between version 1 and version 2 of the OSPF protocol\nare explained in Appendix F of RFC 1247. It is OSPF Version 2 that is\nthe subject of this report.\n\nThis report attempts to summarize the key features of OSPF V2. It also\nattempts to analyze how the protocol will perform and scale in the\nInternet.","scope_keywords":["1245","algorithm","algorithms","authentication","key","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1765","folder":"IETF/RFC-1765","source":"IETF/RFC-1765/RFC-1765.txt","version":null},{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null}],"search_text":"IETF RFC 1245 This is the first of two reports on the OSPF protocol. These reports are\nrequired by the IAB/ IESG in order for an Internet routing protocol to\nadvance to Draft Standard Status. OSPF is a TCP/IP routing protocol,\ndesigned to be used internal to an Autonomous System (in other words,\nOSPF is an Interior Gateway Protocol).\n\nVersion 1 of the OSPF protocol was published in RFC 1131. Since then\nOSPF version 2 has been developed. Version 2 has been documented in RFC\n1247. The changes between version 1 and version 2 of the OSPF protocol\nare explained in Appendix F of RFC 1247. It is OSPF Version 2 that is\nthe subject of this report.\n\nThis report attempts to summarize the key features of OSPF V2. It also\nattempts to analyze how the protocol will perform and scale in the\nInternet. 1245 algorithm algorithms authentication key management path subject trust nested-reference unchanged"},{"id":"IETF RFC 1371","type":"specification","body":"IETF","designation":"RFC 1371","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1371.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1371.txt","https://www.rfc-editor.org/rfc/rfc1371.pdf"],"folder":"IETF/RFC-1371","files":{"txt":{"path":"standards/IETF/RFC-1371/RFC-1371.txt","sha256":"7880f044b2816b904b5d71a36d5b4f08283d83d08f8aa3845ebbf12c84590094"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents motivation, rationale and other surrounding\n background information leading to the IESG's recommendation to the\n IAB for a single \"common IGP\" for the IP portions of the Internet.\n\n In this memo, the term \"common IGP\" is defined, the need for a common\n IGP is explained, the relation of this issue to other ongoing\n Internet Engineering Task Force (IETF) routing protocol development\n is provided, and the relation of this issue to the goal for multi-\n protocol integration in the Internet is explored.\n\n Finally, a specific IGP is recommended as the \"common IGP\" for IP\n portions of the Internet -- the Open Shortest Path First (OSPF)\n routing protocol.\n\n The goal of this recommendation is for all vendors of Internet IP\n routers to make OSPF available as one of the IGP's provided with\n their routers.\n\nIESG [Page 1]\n\f\nRFC 1371 Choosing a \"Common IGP\" October 1992","scope_keywords":["1371","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1370","folder":"IETF/RFC-1370","source":"IETF/RFC-1370/RFC-1370.txt","version":null}],"search_text":"IETF RFC 1371 This memo presents motivation, rationale and other surrounding\n background information leading to the IESG's recommendation to the\n IAB for a single \"common IGP\" for the IP portions of the Internet.\n\n In this memo, the term \"common IGP\" is defined, the need for a common\n IGP is explained, the relation of this issue to other ongoing\n Internet Engineering Task Force (IETF) routing protocol development\n is provided, and the relation of this issue to the goal for multi-\n protocol integration in the Internet is explored.\n\n Finally, a specific IGP is recommended as the \"common IGP\" for IP\n portions of the Internet -- the Open Shortest Path First (OSPF)\n routing protocol.\n\n The goal of this recommendation is for all vendors of Internet IP\n routers to make OSPF available as one of the IGP's provided with\n their routers.\n\nIESG [Page 1]\n\f\nRFC 1371 Choosing a \"Common IGP\" October 1992 1371 algorithm path nested-reference unchanged"},{"id":"IETF RFC 1136","type":"specification","body":"IETF","designation":"RFC 1136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1136.txt","https://www.rfc-editor.org/rfc/rfc1136.pdf"],"folder":"IETF/RFC-1136","files":{"txt":{"path":"standards/IETF/RFC-1136/RFC-1136.txt","sha256":"ad794606a68480846dc3ae4603af0b5ea113b41b2d737915f3a53838820d48b1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Hares\nRequest for Comments: 1136 D. Katz\n Merit/NSFNET\n December 1989\n\n Administrative Domains and Routing Domains\n A Model for Routing in the Internet\n\n1) Status of this Memo\n\n This RFC proposes a model for describing routing within the Internet.\n The model is an adaptation of the \"OSI Routeing Framework\" [1]. This\n memo does not specify an Internet standard. Comments are welcome.\n Distribution of this memo is unlimited.\n\n2) Acknowledgement\n\n The authors would like to thank Guy Almes of Rice University for his\n contributions and insight.\n\n3) Overview\n\n The \"core\" model of Autonomous Systems [2] formed the basis for the\n routing model used in the Internet. Due to massive growth and\n topology changes, the \"core\" model no longer is in harmony with the\n reality of today's Internet. Indeed, this situation was foreseen at\n the outset:\n\n \"Ultimately, however, the inter","scope_keywords":["1136","algorithm","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null}],"search_text":"IETF RFC 1136 Network Working Group S. Hares\nRequest for Comments: 1136 D. Katz\n Merit/NSFNET\n December 1989\n\n Administrative Domains and Routing Domains\n A Model for Routing in the Internet\n\n1) Status of this Memo\n\n This RFC proposes a model for describing routing within the Internet.\n The model is an adaptation of the \"OSI Routeing Framework\" [1]. This\n memo does not specify an Internet standard. Comments are welcome.\n Distribution of this memo is unlimited.\n\n2) Acknowledgement\n\n The authors would like to thank Guy Almes of Rice University for his\n contributions and insight.\n\n3) Overview\n\n The \"core\" model of Autonomous Systems [2] formed the basis for the\n routing model used in the Internet. Due to massive growth and\n topology changes, the \"core\" model no longer is in harmony with the\n reality of today's Internet. Indeed, this situation was foreseen at\n the outset:\n\n \"Ultimately, however, the inter 1136 algorithm management path trust nested-reference unchanged"},{"id":"IETF RFC 5889","type":"specification","body":"IETF","designation":"RFC 5889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5889.txt","https://www.rfc-editor.org/rfc/rfc5889.pdf"],"folder":"IETF/RFC-5889","files":{"txt":{"path":"standards/IETF/RFC-5889/RFC-5889.txt","sha256":"f52246fdefa1f4222109ca017a9e992930739835718a48b54616769e51096f26"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a model for configuring IP addresses and\n subnet prefixes on the interfaces of routers which connect to links\n with undetermined connectivity properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5889.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the","scope_keywords":["5889","http","license","path","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null}],"search_text":"IETF RFC 5889 This document describes a model for configuring IP addresses and\n subnet prefixes on the interfaces of routers which connect to links\n with undetermined connectivity properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5889.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the 5889 http license path qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 1137","type":"specification","body":"IETF","designation":"RFC 1137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1137.txt","https://www.rfc-editor.org/rfc/rfc1137.pdf"],"folder":"IETF/RFC-1137","files":{"txt":{"path":"standards/IETF/RFC-1137/RFC-1137.txt","sha256":"c3af5b1fc4ed9d10af094d1e9d94484fb58a5b2ad85b88e8d909dba266ff71d8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 1137 University College London\nUpdates: RFC 976 December 1989\n\n Mapping Between Full RFC 822 and RFC 822 with\n Restricted Encoding\n\nStatus of this Memo\n\n This RFC suggests an electronic mail protocol mapping for the\n Internet community and UK Academic Community, and requests discussion\n and suggestions for improvements. This memo does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\n This document describes a set of address mappings which will enable\n interworking between systems operating RFC 822 protocols in a general\n manner, and those environments where transfer of RFC 822 messages\n restricts the character set which can be used in addresses. UUCP\n transfer of RFC 822 messages is an important case of this\n [Crocker82a, Horton86a].\n\nSpecification\n\n This document specifies a mapping between two protocols. Th","scope_keywords":["1137"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 1137 Network Working Group S. Kille\nRequest for Comments: 1137 University College London\nUpdates: RFC 976 December 1989\n\n Mapping Between Full RFC 822 and RFC 822 with\n Restricted Encoding\n\nStatus of this Memo\n\n This RFC suggests an electronic mail protocol mapping for the\n Internet community and UK Academic Community, and requests discussion\n and suggestions for improvements. This memo does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\n This document describes a set of address mappings which will enable\n interworking between systems operating RFC 822 protocols in a general\n manner, and those environments where transfer of RFC 822 messages\n restricts the character set which can be used in addresses. UUCP\n transfer of RFC 822 messages is an important case of this\n [Crocker82a, Horton86a].\n\nSpecification\n\n This document specifies a mapping between two protocols. Th 1137 nested-reference unchanged"},{"id":"IETF RFC 1139","type":"specification","body":"IETF","designation":"RFC 1139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1139.txt","https://www.rfc-editor.org/rfc/rfc1139.pdf"],"folder":"IETF/RFC-1139","files":{"txt":{"path":"standards/IETF/RFC-1139/RFC-1139.txt","sha256":"fedcfc496bc7e99294ee959bc1373cde2d0a44e92c47a0d1f63fe19f89d2d3ae"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an echo function for the connection-less network\n layer protocol. Two mechanisms are introduced that may be used to\n implement the echo function. The first mechanism is recommended as\n an interim solution for the Internet community. The second mechanism\n will be progressed to the ANSI X3S3.3 working group for consideration\n as a work item.\n\n When an ISO standard is adopted that provides functionality similar\n to that described by this memo, then this memo will become obsolete\n and superceded by the ISO standard.\n\n1. Introduction\n\n The OSI Connection-less network layer protocol (ISO 8473) defines a\n means for transmitting and relaying data and error report PDUs\n through an OSI internet. Unfortunately, the world that these packets\n travel through is imperfect. Gateways and links may fail. This memo\n defines an echo function to be used in the debugging and testing of\n the ","scope_keywords":["1139","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1575","folder":"IETF/RFC-1575","source":"IETF/RFC-1575/RFC-1575.txt","version":null}],"search_text":"IETF RFC 1139 This memo defines an echo function for the connection-less network\n layer protocol. Two mechanisms are introduced that may be used to\n implement the echo function. The first mechanism is recommended as\n an interim solution for the Internet community. The second mechanism\n will be progressed to the ANSI X3S3.3 working group for consideration\n as a work item.\n\n When an ISO standard is adopted that provides functionality similar\n to that described by this memo, then this memo will become obsolete\n and superceded by the ISO standard.\n\n1. Introduction\n\n The OSI Connection-less network layer protocol (ISO 8473) defines a\n means for transmitting and relaying data and error report PDUs\n through an OSI internet. Unfortunately, the world that these packets\n travel through is imperfect. Gateways and links may fail. This memo\n defines an echo function to be used in the debugging and testing of\n the  1139 management path nested-reference unchanged"},{"id":"IETF RFC 1575","type":"specification","body":"IETF","designation":"RFC 1575","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1575.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1575.txt","https://www.rfc-editor.org/rfc/rfc1575.pdf"],"folder":"IETF/RFC-1575","files":{"txt":{"path":"standards/IETF/RFC-1575/RFC-1575.txt","sha256":"519897738e4bad2101a6d25fcf669e67aa562fa7fa42c683dd8fcaa3a9d4313b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an echo function for the connection-less network\n layer protocol. The mechanism that is mandated here is in the final\n process of being standardized by ISO as \"Amendment X: Addition of an\n Echo function to ISO 8473\" an integral part of Version 2 of ISO 8473.","scope_keywords":["1575","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1575 This memo defines an echo function for the connection-less network\n layer protocol. The mechanism that is mandated here is in the final\n process of being standardized by ISO as \"Amendment X: Addition of an\n Echo function to ISO 8473\" an integral part of Version 2 of ISO 8473. 1575 management path nested-reference unchanged"},{"id":"IETF RFC 959","type":"specification","body":"IETF","designation":"RFC 959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc959.txt","https://www.rfc-editor.org/rfc/rfc959.pdf"],"folder":"IETF/RFC-959","files":{"txt":{"path":"standards/IETF/RFC-959/RFC-959.txt","sha256":"e2eb01566e64c12ed75a0c4bd02231e62f91eebb86f596abc40999d5e8bc5a91"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 959 J. Reynolds\n ISI\nObsoletes RFC: 765 (IEN 149) October 1985\n\n FILE TRANSFER PROTOCOL (FTP)\n\nStatus of this Memo\n\n This memo is the official specification of the File Transfer\n Protocol (FTP). Distribution of this memo is unlimited.\n\n The following new optional commands are included in this edition of\n the specification:\n\n CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU\n (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD\n (Print Directory), and SYST (System).\n\n Note that this specification is compatible with the previous edition.\n\n1. INTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among hosts, and 4) to trans","scope_keywords":["959","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1204","folder":"IETF/RFC-1204","source":"IETF/RFC-1204/RFC-1204.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1408","folder":"IETF/RFC-1408","source":"IETF/RFC-1408/RFC-1408.txt","version":null},{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null},{"body":"IETF","designation":"RFC 1440","folder":"IETF/RFC-1440","source":"IETF/RFC-1440/RFC-1440.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null},{"body":"IETF","designation":"RFC 1579","folder":"IETF/RFC-1579","source":"IETF/RFC-1579/RFC-1579.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1630","folder":"IETF/RFC-1630","source":"IETF/RFC-1630/RFC-1630.txt","version":null},{"body":"IETF","designation":"RFC 1639","folder":"IETF/RFC-1639","source":"IETF/RFC-1639/RFC-1639.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1919","folder":"IETF/RFC-1919","source":"IETF/RFC-1919/RFC-1919.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2228","folder":"IETF/RFC-2228","source":"IETF/RFC-2228/RFC-2228.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2389","folder":"IETF/RFC-2389","source":"IETF/RFC-2389/RFC-2389.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 2585","folder":"IETF/RFC-2585","source":"IETF/RFC-2585/RFC-2585.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2773","folder":"IETF/RFC-2773","source":"IETF/RFC-2773/RFC-2773.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 959 Network Working Group J. Postel\nRequest for Comments: 959 J. Reynolds\n ISI\nObsoletes RFC: 765 (IEN 149) October 1985\n\n FILE TRANSFER PROTOCOL (FTP)\n\nStatus of this Memo\n\n This memo is the official specification of the File Transfer\n Protocol (FTP). Distribution of this memo is unlimited.\n\n The following new optional commands are included in this edition of\n the specification:\n\n CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU\n (Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD\n (Print Directory), and SYST (System).\n\n Note that this specification is compatible with the previous edition.\n\n1. INTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among hosts, and 4) to trans 959 path subject nested-reference unchanged"},{"id":"IETF RFC 5475","type":"specification","body":"IETF","designation":"RFC 5475","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5475.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5475.txt","https://www.rfc-editor.org/rfc/rfc5475.pdf"],"folder":"IETF/RFC-5475","files":{"txt":{"path":"standards/IETF/RFC-5475/RFC-5475.txt","sha256":"40c8ba4d59c4de81579bb831fc23ac418997d42873c64bbf1e113ddd5fd63464"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Sampling and Filtering techniques for IP\n packet selection. It provides a categorization of schemes and\n defines what parameters are needed to describe the most common\n selection schemes. Furthermore, it shows how techniques can be\n combined to build more elaborate packet Selectors. The document\n provides the basis for the definition of information models for\n configuring selection techniques in Metering Processes and for\n reporting the technique in use to a Collector.","scope_keywords":["5475","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null}],"search_text":"IETF RFC 5475 This document describes Sampling and Filtering techniques for IP\n packet selection. It provides a categorization of schemes and\n defines what parameters are needed to describe the most common\n selection schemes. Furthermore, it shows how techniques can be\n combined to build more elaborate packet Selectors. The document\n provides the basis for the definition of information models for\n configuring selection techniques in Metering Processes and for\n reporting the technique in use to a Collector. 5475 hash http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6727","type":"specification","body":"IETF","designation":"RFC 6727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6727.txt","https://www.rfc-editor.org/rfc/rfc6727.pdf"],"folder":"IETF/RFC-6727","files":{"txt":{"path":"standards/IETF/RFC-6727/RFC-6727.txt","sha256":"b85a3cb06801cf46a25952726f78e9bfc10f9b2ad4dd13729c5cdc6a3e459838"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes extensions to the IPFIX-SELECTOR-MIB\n module. For IP Flow Information eXport (IPFIX) implementations that\n use Packet Sampling (PSAMP) techniques, this memo defines the PSAMP-\n MIB module containing managed objects for providing information on\n applied packet selection functions and their parameters.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curren","scope_keywords":["6727","hash","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null}],"search_text":"IETF RFC 6727 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes extensions to the IPFIX-SELECTOR-MIB\n module. For IP Flow Information eXport (IPFIX) implementations that\n use Packet Sampling (PSAMP) techniques, this memo defines the PSAMP-\n MIB module containing managed objects for providing information on\n applied packet selection functions and their parameters.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curren 6727 hash http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6728","type":"specification","body":"IETF","designation":"RFC 6728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6728.txt","https://www.rfc-editor.org/rfc/rfc6728.pdf"],"folder":"IETF/RFC-6728","files":{"txt":{"path":"standards/IETF/RFC-6728/RFC-6728.txt","sha256":"eb07b1fa90ed0725f15a8fc37fc8f6b43b8ce0a3838080517dc5bd669c90d50c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a data model for the IP Flow Information\n Export (IPFIX) and Packet Sampling (PSAMP) protocols. It is for\n configuring and monitoring Selection Processes, Caches, Exporting\n Processes, and Collecting Processes of IPFIX- and PSAMP-compliant\n Monitoring Devices using the Network Configuration Protocol\n (NETCONF). The data model is defined using UML (Unified Modeling\n Language) class diagrams and formally specified using YANG. The\n configuration data is encoded in Extensible Markup Language (XML).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in","scope_keywords":["6728","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 6728 This document specifies a data model for the IP Flow Information\n Export (IPFIX) and Packet Sampling (PSAMP) protocols. It is for\n configuring and monitoring Selection Processes, Caches, Exporting\n Processes, and Collecting Processes of IPFIX- and PSAMP-compliant\n Monitoring Devices using the Network Configuration Protocol\n (NETCONF). The data model is defined using UML (Unified Modeling\n Language) class diagrams and formally specified using YANG. The\n configuration data is encoded in Extensible Markup Language (XML).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in 6728 http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2966","type":"specification","body":"IETF","designation":"RFC 2966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2966.txt","https://www.rfc-editor.org/rfc/rfc2966.pdf"],"folder":"IETF/RFC-2966","files":{"txt":{"path":"standards/IETF/RFC-2966/RFC-2966.txt","sha256":"62007476e9e62dcfcb12d16e714a2042e96032cfd2b31e9ef61b7940820d2d90"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support optimal routing\n within a two-level domain. The IS-IS protocol is specified in ISO\n 10589, with extensions for supporting IPv4 (Internet Protocol)\n specified in RFC 1195 [2].\n\n This document extends the semantics presented in RFC 1195 so that a\n routing domain running with both level 1 and level 2 Intermediate\n Systems (IS) [routers] can distribute IP prefixes between level 1 and\n level 2 and vice versa. This distribution requires certain\n restrictions to insure that persistent forwarding loops do not form.\n The goal of this domain-wide prefix distribution is to increase the\n granularity of the routing information within the domain.\n\n1. Introduction\n\n An IS-IS routing domain (a.k.a., an autonomous system running IS-IS)\n can be partitioned into multiple level 1 (L1) areas, and","scope_keywords":["2966","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null}],"search_text":"IETF RFC 2966 This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support optimal routing\n within a two-level domain. The IS-IS protocol is specified in ISO\n 10589, with extensions for supporting IPv4 (Internet Protocol)\n specified in RFC 1195 [2].\n\n This document extends the semantics presented in RFC 1195 so that a\n routing domain running with both level 1 and level 2 Intermediate\n Systems (IS) [routers] can distribute IP prefixes between level 1 and\n level 2 and vice versa. This distribution requires certain\n restrictions to insure that persistent forwarding loops do not form.\n The goal of this domain-wide prefix distribution is to increase the\n granularity of the routing information within the domain.\n\n1. Introduction\n\n An IS-IS routing domain (a.k.a., an autonomous system running IS-IS)\n can be partitioned into multiple level 1 (L1) areas, and 2966 path policy nested-reference unchanged"},{"id":"IETF RFC 3358","type":"specification","body":"IETF","designation":"RFC 3358","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3358.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3358.txt","https://www.rfc-editor.org/rfc/rfc3358.pdf"],"folder":"IETF/RFC-3358","files":{"txt":{"path":"standards/IETF/RFC-3358/RFC-3358.txt","sha256":"2461eae903382d3403638898429b731c63406221b072625b38fbe6559670cefe"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Przygienda\nRequest for Comments: 3358 Xebeo\nCategory: Informational August 2002\n\n Optional Checksums in\n Intermediate System to Intermediate System (ISIS)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes an optional extension to the Intermediate\n System to Intermediate System (ISIS) protocol, used today by several\n Internet Service Proviers (ISPs) for routing within their clouds.\n ISIS is an interior gateway routing protocol developed originally by\n OSI and used with IP extensions as Interior Gateway Protocol (IGP).\n ISIS originally does not provide Complete Sequence Numbers Protocol\n Data (CSNP) and Partial Sequence N","scope_keywords":["3358","authentication","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null}],"search_text":"IETF RFC 3358 Network Working Group T. Przygienda\nRequest for Comments: 3358 Xebeo\nCategory: Informational August 2002\n\n Optional Checksums in\n Intermediate System to Intermediate System (ISIS)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes an optional extension to the Intermediate\n System to Intermediate System (ISIS) protocol, used today by several\n Internet Service Proviers (ISPs) for routing within their clouds.\n ISIS is an interior gateway routing protocol developed originally by\n OSI and used with IP extensions as Interior Gateway Protocol (IGP).\n ISIS originally does not provide Complete Sequence Numbers Protocol\n Data (CSNP) and Partial Sequence N 3358 authentication key signature signatures nested-reference unchanged"},{"id":"IETF RFC 3618","type":"specification","body":"IETF","designation":"RFC 3618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3618.txt","https://www.rfc-editor.org/rfc/rfc3618.pdf"],"folder":"IETF/RFC-3618","files":{"txt":{"path":"standards/IETF/RFC-3618/RFC-3618.txt","sha256":"98d1ba600d85cbcb03d376cbc9eb72db1acbae546115f2c8c51152b3ef90e144"}},"tags":["nested-reference","unchanged"],"summary":"The Multicast Source Discovery Protocol (MSDP) describes a mechanism\n to connect multiple IP Version 4 Protocol Independent Multicast\n Sparse-Mode (PIM-SM) domains together. Each PIM-SM domain uses its\n own independent Rendezvous Point (RP) and does not have to depend on\n RPs in other domains. This document reflects existing MSDP\n implementations.","scope_keywords":["3618","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3956","folder":"IETF/RFC-3956","source":"IETF/RFC-3956/RFC-3956.txt","version":null},{"body":"IETF","designation":"RFC 4608","folder":"IETF/RFC-4608","source":"IETF/RFC-4608/RFC-4608.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 3618 The Multicast Source Discovery Protocol (MSDP) describes a mechanism\n to connect multiple IP Version 4 Protocol Independent Multicast\n Sparse-Mode (PIM-SM) domains together. Each PIM-SM domain uses its\n own independent Rendezvous Point (RP) and does not have to depend on\n RPs in other domains. This document reflects existing MSDP\n implementations. 3618 key policy nested-reference unchanged"},{"id":"IETF RFC 3779","type":"specification","body":"IETF","designation":"RFC 3779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3779.txt","https://www.rfc-editor.org/rfc/rfc3779.pdf"],"folder":"IETF/RFC-3779","files":{"txt":{"path":"standards/IETF/RFC-3779/RFC-3779.txt","sha256":"bd40f6d1edbbf7020aaed4a0b377ae89e09b9f7b1bd49694c12bade3c07f4fdd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two X.509 v3 certificate extensions. The first\n binds a list of IP address blocks, or prefixes, to the subject of a\n certificate. The second binds a list of autonomous system\n identifiers to the subject of a certificate. These extensions may be\n used to convey the authorization of the subject to use the IP\n addresses and autonomous system identifiers contained in the\n extensions.","scope_keywords":["3779","algorithm","algorithms","attribute","authorization","certificate","certificates","crl","holder","issuer","key","management","path","policy","profile","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 3779 This document defines two X.509 v3 certificate extensions. The first\n binds a list of IP address blocks, or prefixes, to the subject of a\n certificate. The second binds a list of autonomous system\n identifiers to the subject of a certificate. These extensions may be\n used to convey the authorization of the subject to use the IP\n addresses and autonomous system identifiers contained in the\n extensions. 3779 algorithm algorithms attribute authorization certificate certificates crl holder issuer key management path policy profile revocation nested-reference unchanged"},{"id":"IETF RFC 1144","type":"specification","body":"IETF","designation":"RFC 1144","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1144.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1144.txt","https://www.rfc-editor.org/rfc/rfc1144.pdf"],"folder":"IETF/RFC-1144","files":{"pdf":{"path":"standards/IETF/RFC-1144/RFC-1144.pdf","sha256":"d7aa4299df93ce07e1f967e8935d607f1d9b358e728ff219ec8e65d81cce965d"},"txt":{"path":"standards/IETF/RFC-1144/RFC-1144.txt","sha256":"d00e875eddaa1ac2e22b4a8dbd65e7e1a65131b181ca7bfaaf5eb50166f06554"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Jacobson/1/\n Request for Comments: 1144 LBL\n February 1990\n\n Compressing TCP/IP Headers\n\n for Low-Speed Serial Links\n\n Status of this Memo\n\n This RFC is a proposed elective protocol for the Internet community and\n requests discussion and suggestions for improvement. It describes a\n method for compressing the headers of TCP/IP datagrams to improve\n performance over low speed serial links. The motivation, implementation\n and performance of the method are described. C code for a sample\n implementation is given for reference. Distribution of this memo is\n unlimited.\n\n NOTE: Both ASCII and Postscript versions of this document are available.\n The ASCII version, obviously, lacks all the figures and all the\n information encoded in typographic variation (italics, boldface,\n etc.). Since this information was, in the author's opinion, an\n essential part of the document, the","scope_keywords":["1144","algorithm","authentication","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1553","folder":"IETF/RFC-1553","source":"IETF/RFC-1553/RFC-1553.txt","version":null},{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3096","folder":"IETF/RFC-3096","source":"IETF/RFC-3096/RFC-3096.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1144 Network Working Group V. Jacobson/1/\n Request for Comments: 1144 LBL\n February 1990\n\n Compressing TCP/IP Headers\n\n for Low-Speed Serial Links\n\n Status of this Memo\n\n This RFC is a proposed elective protocol for the Internet community and\n requests discussion and suggestions for improvement. It describes a\n method for compressing the headers of TCP/IP datagrams to improve\n performance over low speed serial links. The motivation, implementation\n and performance of the method are described. C code for a sample\n implementation is given for reference. Distribution of this memo is\n unlimited.\n\n NOTE: Both ASCII and Postscript versions of this document are available.\n The ASCII version, obviously, lacks all the figures and all the\n information encoded in typographic variation (italics, boldface,\n etc.). Since this information was, in the author's opinion, an\n essential part of the document, the 1144 algorithm authentication delivery nested-reference unchanged"},{"id":"IETF RFC 1553","type":"specification","body":"IETF","designation":"RFC 1553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1553.txt","https://www.rfc-editor.org/rfc/rfc1553.pdf"],"folder":"IETF/RFC-1553","files":{"txt":{"path":"standards/IETF/RFC-1553/RFC-1553.txt","sha256":"5d77a4cd2eeacca0ba092102479700ccde92cf21356a4c2ad213fc47d44e0768"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for compressing the headers of IPX\n datagrams (CIPX). With this method, it is possible to\n significantly improve performance over lower speed wide area\n network (WAN) media. For normal IPX packet traffic, CIPX can\n provide a compression ratio of approximately 2:1 including both IPX\n header and data. This method can be used on various type of WAN\n media, including those supporting PPP and X.25.\n\n This memo ia a product of the Point-to-Point Protocol Extensions\n (PPPEXT) Working Group of the IETF. Comments should be sent to\n the authors and the ietf-ppp@ucdavis.edu mailing list.\n\nSpecification of Requirements\n\n In this document, several words are used to signify the requirements\n of the specification. These words are often capitalized.\n\n MUST\n\n This word, or the adjective \"required\", means that the\n definition is an absolute requirement of the specification","scope_keywords":["1553","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null},{"body":"IETF","designation":"RFC 1552","folder":"IETF/RFC-1552","source":"IETF/RFC-1552/RFC-1552.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 1553 This document describes a method for compressing the headers of IPX\n datagrams (CIPX). With this method, it is possible to\n significantly improve performance over lower speed wide area\n network (WAN) media. For normal IPX packet traffic, CIPX can\n provide a compression ratio of approximately 2:1 including both IPX\n header and data. This method can be used on various type of WAN\n media, including those supporting PPP and X.25.\n\n This memo ia a product of the Point-to-Point Protocol Extensions\n (PPPEXT) Working Group of the IETF. Comments should be sent to\n the authors and the ietf-ppp@ucdavis.edu mailing list.\n\nSpecification of Requirements\n\n In this document, several words are used to signify the requirements\n of the specification. These words are often capitalized.\n\n MUST\n\n This word, or the adjective \"required\", means that the\n definition is an absolute requirement of the specification 1553 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1701","type":"specification","body":"IETF","designation":"RFC 1701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1701.txt","https://www.rfc-editor.org/rfc/rfc1701.pdf"],"folder":"IETF/RFC-1701","files":{"txt":{"path":"standards/IETF/RFC-1701/RFC-1701.txt","sha256":"33c184a3ef9d97b3a3ddd59b9401ff8ea41803d2404a4fd70bc839d0cd5a3989"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol for performing encapsulation of an\n arbitrary network layer protocol over another arbitrary network layer\n protocol.","scope_keywords":["1701","algorithm","algorithms","delivery","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1702","folder":"IETF/RFC-1702","source":"IETF/RFC-1702/RFC-1702.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null}],"search_text":"IETF RFC 1701 This document specifies a protocol for performing encapsulation of an\n arbitrary network layer protocol over another arbitrary network layer\n protocol. 1701 algorithm algorithms delivery key policy nested-reference unchanged"},{"id":"IETF RFC 2058","type":"specification","body":"IETF","designation":"RFC 2058","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2058.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2058.txt","https://www.rfc-editor.org/rfc/rfc2058.pdf"],"folder":"IETF/RFC-2058","files":{"txt":{"path":"standards/IETF/RFC-2058/RFC-2058.txt","sha256":"ff92a0f577c0021d3b6a4ad666b06769ab43c17aed9d3ec415798ddd856a42f1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server.","scope_keywords":["2058","attribute","attributes","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2059","folder":"IETF/RFC-2059","source":"IETF/RFC-2059/RFC-2059.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2194","folder":"IETF/RFC-2194","source":"IETF/RFC-2194/RFC-2194.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 2058 This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server. 2058 attribute attributes authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 2138","type":"specification","body":"IETF","designation":"RFC 2138","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2138.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2138.txt","https://www.rfc-editor.org/rfc/rfc2138.pdf"],"folder":"IETF/RFC-2138","files":{"txt":{"path":"standards/IETF/RFC-2138/RFC-2138.txt","sha256":"e6ddbac5026ff99f4d9474066c513771291040935946db6b6f3dfed0f4379354"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server.\n\nImplementation Note\n\n This memo documents the RADIUS protocol. There has been some\n confusion in the assignment of port numbers for this protocol. The\n early deployment of RADIUS was done using the erroneously chosen port\n number 1645, which conflicts with the \"datametrics\" service. The\n officially assigned port number for RADIUS is 1812.","scope_keywords":["2138","attribute","attributes","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2139","folder":"IETF/RFC-2139","source":"IETF/RFC-2139/RFC-2139.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2809","folder":"IETF/RFC-2809","source":"IETF/RFC-2809/RFC-2809.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null}],"search_text":"IETF RFC 2138 This document describes a protocol for carrying authentication,\n authorization, and configuration information between a Network Access\n Server which desires to authenticate its links and a shared\n Authentication Server.\n\nImplementation Note\n\n This memo documents the RADIUS protocol. There has been some\n confusion in the assignment of port numbers for this protocol. The\n early deployment of RADIUS was done using the erroneously chosen port\n number 1645, which conflicts with the \"datametrics\" service. The\n officially assigned port number for RADIUS is 1812. 2138 attribute attributes authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 2290","type":"specification","body":"IETF","designation":"RFC 2290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2290.txt","https://www.rfc-editor.org/rfc/rfc2290.pdf"],"folder":"IETF/RFC-2290","files":{"txt":{"path":"standards/IETF/RFC-2290/RFC-2290.txt","sha256":"fee1eb37322348b361469056f1e972ac78300db2d58874139970f46a78690ea6"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP [RFC 2002] defines media-independent procedures by which a\n Mobile Node can maintain existing transport and application-layer\n connections despite changing its point-of-attachment to the Internet\n and without changing its IP address. PPP [RFC 1661] provides a\n standard method for transporting multi-protocol packets over point-\n to-point links. As currently specified, Mobile IP Foreign Agents\n which support Mobile Node connections via PPP can do so only by first\n assigning unique addresses to those Mobile Nodes, defeating one of\n the primary advantages of Foreign Agents. This documents corrects\n this problem by defining the Mobile-IPv4 Configuration Option to the\n Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this\n option, two peers can communicate their support for Mobile IP during\n the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP\n [RFC 1332], an","scope_keywords":["2290","delivery","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 2290 Mobile IP [RFC 2002] defines media-independent procedures by which a\n Mobile Node can maintain existing transport and application-layer\n connections despite changing its point-of-attachment to the Internet\n and without changing its IP address. PPP [RFC 1661] provides a\n standard method for transporting multi-protocol packets over point-\n to-point links. As currently specified, Mobile IP Foreign Agents\n which support Mobile Node connections via PPP can do so only by first\n assigning unique addresses to those Mobile Nodes, defeating one of\n the primary advantages of Foreign Agents. This documents corrects\n this problem by defining the Mobile-IPv4 Configuration Option to the\n Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this\n option, two peers can communicate their support for Mobile IP during\n the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP\n [RFC 1332], an 2290 delivery key registered nested-reference unchanged"},{"id":"IETF RFC 2507","type":"specification","body":"IETF","designation":"RFC 2507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2507.txt","https://www.rfc-editor.org/rfc/rfc2507.pdf"],"folder":"IETF/RFC-2507","files":{"txt":{"path":"standards/IETF/RFC-2507/RFC-2507.txt","sha256":"b114d3f3099c67f22b2b2e8623b709fbb5c1248653e5166603bc8c050b5f75fe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to compress multiple IP headers and TCP\n and UDP headers per hop over point to point links. The methods can be\n applied to of IPv6 base and extension headers, IPv4 headers, TCP and\n UDP headers, and encapsulated IPv6 and IPv4 headers.\n\n Headers of typical UDP or TCP packets can be compressed down to 4-7\n octets including the 2 octet UDP or TCP checksum. This largely\n removes the negative impact of large IP headers and allows efficient\n use of bandwidth on low and medium speed links.\n\n The compression algorithms are specifically designed to work well\n over links with nontrivial packet-loss rates. Several wireless and\n modem technologies result in such links.","scope_keywords":["2507","algorithm","algorithms","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 2507 This document describes how to compress multiple IP headers and TCP\n and UDP headers per hop over point to point links. The methods can be\n applied to of IPv6 base and extension headers, IPv4 headers, TCP and\n UDP headers, and encapsulated IPv6 and IPv4 headers.\n\n Headers of typical UDP or TCP packets can be compressed down to 4-7\n octets including the 2 octet UDP or TCP checksum. This largely\n removes the negative impact of large IP headers and allows efficient\n use of bandwidth on low and medium speed links.\n\n The compression algorithms are specifically designed to work well\n over links with nontrivial packet-loss rates. Several wireless and\n modem technologies result in such links. 2507 algorithm algorithms authentication nested-reference unchanged"},{"id":"IETF RFC 2508","type":"specification","body":"IETF","designation":"RFC 2508","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2508.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2508.txt","https://www.rfc-editor.org/rfc/rfc2508.pdf"],"folder":"IETF/RFC-2508","files":{"txt":{"path":"standards/IETF/RFC-2508/RFC-2508.txt","sha256":"a72876fe0ea832170752e7d7732d614001be148213e377d543e318929e392668"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for compressing the headers of\n IP/UDP/RTP datagrams to reduce overhead on low-speed serial links.\n In many cases, all three headers can be compressed to 2-4 bytes.\n\n Comments are solicited and should be addressed to the working group\n mailing list rem-conf@es.net and/or the author(s).\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\n1. Introduction\n\n Since the Real-time Transport Protocol was published as an RFC [1],\n there has been growing interest in using RTP as one step to achieve\n interoperability among different implementations of network\n audio/video applications. However, there is also concern that the\n 12-byte RTP header is too large an overhead for 20-byte payloads when\n operating over low speed l","scope_keywords":["2508","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2736","folder":"IETF/RFC-2736","source":"IETF/RFC-2736/RFC-2736.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3096","folder":"IETF/RFC-3096","source":"IETF/RFC-3096/RFC-3096.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null}],"search_text":"IETF RFC 2508 This document describes a method for compressing the headers of\n IP/UDP/RTP datagrams to reduce overhead on low-speed serial links.\n In many cases, all three headers can be compressed to 2-4 bytes.\n\n Comments are solicited and should be addressed to the working group\n mailing list rem-conf@es.net and/or the author(s).\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\n1. Introduction\n\n Since the Real-time Transport Protocol was published as an RFC [1],\n there has been growing interest in using RTP as one step to achieve\n interoperability among different implementations of network\n audio/video applications. However, there is also concern that the\n 12-byte RTP header is too large an overhead for 20-byte payloads when\n operating over low speed l 2508 key path nested-reference unchanged"},{"id":"IETF RFC 2509","type":"specification","body":"IETF","designation":"RFC 2509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2509.txt","https://www.rfc-editor.org/rfc/rfc2509.pdf"],"folder":"IETF/RFC-2509","files":{"txt":{"path":"standards/IETF/RFC-2509/RFC-2509.txt","sha256":"78f3a97140ba54d594b04df63a750b3bf8ae8c08fce0467d0056daecb12f79e9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an option for negotiating the use of header\n compression on IP datagrams transmitted over the Point-to-Point\n Protocol [RFC1661]. It defines extensions to the PPP Control\n Protocols for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression\n may be applied to IPv4 and IPv6 datagrams in combination with TCP,\n UDP and RTP transport protocols as specified in [IPHC] and [CRTP].\n\n1. Introduction\n\n The IP Header Compression (IPHC) defined in [IPHC] may be used for\n compression of both IPv4 and IPv6 datagrams or packets encapsulated\n with multiple IP headers. IPHC is also capable of compressing both\n TCP and UDP transport protocol headers. The IP/UDP/RTP header\n compression defined in [CRTP] fits within the framework defined by\n IPHC so that it may also be applied to both IPv4 and IPv6 packets.\n\n In order to establish compression of IP datagrams sent over a PPP\n link each ","scope_keywords":["2509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2509 This document describes an option for negotiating the use of header\n compression on IP datagrams transmitted over the Point-to-Point\n Protocol [RFC1661]. It defines extensions to the PPP Control\n Protocols for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression\n may be applied to IPv4 and IPv6 datagrams in combination with TCP,\n UDP and RTP transport protocols as specified in [IPHC] and [CRTP].\n\n1. Introduction\n\n The IP Header Compression (IPHC) defined in [IPHC] may be used for\n compression of both IPv4 and IPv6 datagrams or packets encapsulated\n with multiple IP headers. IPHC is also capable of compressing both\n TCP and UDP transport protocol headers. The IP/UDP/RTP header\n compression defined in [CRTP] fits within the framework defined by\n IPHC so that it may also be applied to both IPv4 and IPv6 packets.\n\n In order to establish compression of IP datagrams sent over a PPP\n link each  2509 nested-reference unchanged"},{"id":"IETF RFC 2689","type":"specification","body":"IETF","designation":"RFC 2689","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2689.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2689.txt","https://www.rfc-editor.org/rfc/rfc2689.pdf"],"folder":"IETF/RFC-2689","files":{"txt":{"path":"standards/IETF/RFC-2689/RFC-2689.txt","sha256":"aa60e4f58354da2a9fa3b5b0545398a56874afc301363ed34239ed157107e5e3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for providing integrated\n services over low-bitrate links, such as modem lines, ISDN B-\n channels, and sub-T1 links. It covers only the lower parts of the\n Internet Multimedia Conferencing Architecture [1]; additional\n components required for application services such as Internet\n Telephony (e.g., a session initiation protocol) are outside the scope\n of this document. The main components of the architecture are: a\n real-time encapsulation format for asynchronous and synchronous low-\n bitrate links, a header compression architecture optimized for real-\n time flows, elements of negotiation protocols used between routers\n (or between hosts and routers), and announcement protocols used by\n applications to allow this negotiation to take place.\n\n1. Introduction\n\n As an extension to the \"best-effort\" services the Internet is well-\n known for, additional t","scope_keywords":["2689","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"IETF RFC 2689 This document describes an architecture for providing integrated\n services over low-bitrate links, such as modem lines, ISDN B-\n channels, and sub-T1 links. It covers only the lower parts of the\n Internet Multimedia Conferencing Architecture [1]; additional\n components required for application services such as Internet\n Telephony (e.g., a session initiation protocol) are outside the scope\n of this document. The main components of the architecture are: a\n real-time encapsulation format for asynchronous and synchronous low-\n bitrate links, a header compression architecture optimized for real-\n time flows, elements of negotiation protocols used between routers\n (or between hosts and routers), and announcement protocols used by\n applications to allow this negotiation to take place.\n\n1. Introduction\n\n As an extension to the \"best-effort\" services the Internet is well-\n known for, additional t 2689 path nested-reference unchanged"},{"id":"IETF RFC 2780","type":"specification","body":"IETF","designation":"RFC 2780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2780.txt","https://www.rfc-editor.org/rfc/rfc2780.pdf"],"folder":"IETF/RFC-2780","files":{"txt":{"path":"standards/IETF/RFC-2780/RFC-2780.txt","sha256":"fb432c543189352ce1b360074bc03fdddef6a89bbf113581898364327b3be1e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides guidance for the IANA to use in assigning\n parameters for fields in the IPv4, IPv6, ICMP, UDP and TCP protocol\n headers.\n\n1. Introduction\n\n For many years the Internet Assigned Numbers Authority (IANA)\n (www.iana.org) has allocated parameter values for fields in protocols\n which have been created or are maintained by the Internet Engineering\n Task Force (IETF). Starting a few years ago the IETF began to\n provide the IANA with guidance for the assignment of parameters for\n fields in newly developed protocols. Unfortunately this type of\n guidance was not consistently provided for the fields in protocols\n developed before 1998. This memo attempts to codify existing IANA\n practice used in the assignment of parameters in the specific case of\n some of these protocols. It is expected that additional memos will\n be developed in the future to codify existing practice in other\n ","scope_keywords":["2780"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3228","folder":"IETF/RFC-3228","source":"IETF/RFC-3228/RFC-3228.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3540","folder":"IETF/RFC-3540","source":"IETF/RFC-3540/RFC-3540.txt","version":null},{"body":"IETF","designation":"RFC 3692","folder":"IETF/RFC-3692","source":"IETF/RFC-3692/RFC-3692.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null}],"search_text":"IETF RFC 2780 This memo provides guidance for the IANA to use in assigning\n parameters for fields in the IPv4, IPv6, ICMP, UDP and TCP protocol\n headers.\n\n1. Introduction\n\n For many years the Internet Assigned Numbers Authority (IANA)\n (www.iana.org) has allocated parameter values for fields in protocols\n which have been created or are maintained by the Internet Engineering\n Task Force (IETF). Starting a few years ago the IETF began to\n provide the IANA with guidance for the assignment of parameters for\n fields in newly developed protocols. Unfortunately this type of\n guidance was not consistently provided for the fields in protocols\n developed before 1998. This memo attempts to codify existing IANA\n practice used in the assignment of parameters in the specific case of\n some of these protocols. It is expected that additional memos will\n be developed in the future to codify existing practice in other\n  2780 nested-reference unchanged"},{"id":"IETF RFC 3006","type":"specification","body":"IETF","designation":"RFC 3006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3006.txt","https://www.rfc-editor.org/rfc/rfc3006.pdf"],"folder":"IETF/RFC-3006","files":{"txt":{"path":"standards/IETF/RFC-3006/RFC-3006.txt","sha256":"1ea0e6358a91a898057afb2ccd14032e163991857bfd0f249f17c9a21e67bad8"}},"tags":["nested-reference","unchanged"],"summary":"An Integrated Services (int-serv) router performs admission control\n and resource allocation based on the information contained in a TSpec\n (among other things). As currently defined, TSpecs convey\n information about the data rate (using a token bucket) and range of\n packet sizes of the flow in question. However, the TSpec may not be\n an accurate representation of the resources needed to support the\n reservation if the router is able to compress the data at the link\n level. This specification describes an extension to the TSpec which\n enables a sender of potentially compressible data to provide hints to\n int-serv routers about the compressibility they may obtain. Routers\n which support appropriate compression take advantage of the hint in\n their admission control decisions and resource allocation procedures;\n other routers ignore the hint. An initial application of this\n approach is to n","scope_keywords":["3006","path","presentation","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null}],"search_text":"IETF RFC 3006 An Integrated Services (int-serv) router performs admission control\n and resource allocation based on the information contained in a TSpec\n (among other things). As currently defined, TSpecs convey\n information about the data rate (using a token bucket) and range of\n packet sizes of the flow in question. However, the TSpec may not be\n an accurate representation of the resources needed to support the\n reservation if the router is able to compress the data at the link\n level. This specification describes an extension to the TSpec which\n enables a sender of potentially compressible data to provide hints to\n int-serv routers about the compressibility they may obtain. Routers\n which support appropriate compression take advantage of the hint in\n their admission control decisions and resource allocation procedures;\n other routers ignore the hint. An initial application of this\n approach is to n 3006 path presentation tsp nested-reference unchanged"},{"id":"IETF RFC 3095","type":"specification","body":"IETF","designation":"RFC 3095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3095.txt","https://www.rfc-editor.org/rfc/rfc3095.pdf"],"folder":"IETF/RFC-3095","files":{"txt":{"path":"standards/IETF/RFC-3095/RFC-3095.txt","sha256":"53fb0eee9981bb38393771cf0f1245f130a8558a388ad7446422dd2d30909309"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a highly robust and efficient header\n compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User\n Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP\n (Encapsulating Security Payload) headers.\n\n Existing header compression schemes do not work well when used over\n links with significant error rates and long round-trip times. For\n many bandwidth limited links where header compression is essential,\n such characteristics are common.\n\nBormann, et al. Standards Track [Page 1]\n\f\nRFC 3095 Robust Header Compression July 2001\n\n This is done in a framework designed to be extensible. For example,\n a scheme for compressing TCP/IP headers will be simple to add, and is\n in development. Headers specific to Mobile IPv4 are not subject to\n special treatment, but are expected to be compressed sufficiently\n well by the provided methods for compression of sequences of","scope_keywords":["3095","profile","profiles","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3096","folder":"IETF/RFC-3096","source":"IETF/RFC-3096/RFC-3096.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3243","folder":"IETF/RFC-3243","source":"IETF/RFC-3243/RFC-3243.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3408","folder":"IETF/RFC-3408","source":"IETF/RFC-3408/RFC-3408.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3759","folder":"IETF/RFC-3759","source":"IETF/RFC-3759/RFC-3759.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3843","folder":"IETF/RFC-3843","source":"IETF/RFC-3843/RFC-3843.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4164","folder":"IETF/RFC-4164","source":"IETF/RFC-4164/RFC-4164.txt","version":null},{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5136","folder":"IETF/RFC-5136","source":"IETF/RFC-5136/RFC-5136.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null}],"search_text":"IETF RFC 3095 This document specifies a highly robust and efficient header\n compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User\n Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP\n (Encapsulating Security Payload) headers.\n\n Existing header compression schemes do not work well when used over\n links with significant error rates and long round-trip times. For\n many bandwidth limited links where header compression is essential,\n such characteristics are common.\n\nBormann, et al. Standards Track [Page 1]\n\f\nRFC 3095 Robust Header Compression July 2001\n\n This is done in a framework designed to be extensible. For example,\n a scheme for compressing TCP/IP headers will be simple to add, and is\n in development. Headers specific to Mobile IPv4 are not subject to\n special treatment, but are expected to be compressed sufficiently\n well by the provided methods for compression of sequences of 3095 profile profiles subject timestamp nested-reference unchanged"},{"id":"IETF RFC 3096","type":"specification","body":"IETF","designation":"RFC 3096","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3096.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3096.txt","https://www.rfc-editor.org/rfc/rfc3096.pdf"],"folder":"IETF/RFC-3096","files":{"txt":{"path":"standards/IETF/RFC-3096/RFC-3096.txt","sha256":"df56353a1630cbd6871368579eec3c64b2c375ebb6d95fc66f122ea9ee40c18d"}},"tags":["nested-reference","unchanged"],"summary":"This document contains requirements for robust IP/UDP/RTP (Internet\n Protocol/User Datagram Protocol/Real-Time Transport Protocol) header\n compression to be developed by the ROHC (Robust Header Compression)\n WG. It is based on the ROHC charter, discussions in the WG, the 3GPP\n document \"3GPP TR 23.922\", version 1.0.0 of October 1999, as well as\n contributions from 3G.IP.\n\n1. Introduction\n\n The goal of the ROHC WG is to develop header compression schemes that\n perform well over links with high error rates and long link round\n trip times. The schemes must perform well for cellular links built\n using technologies such as WCDMA, EDGE, and CDMA-2000. However, the\n schemes should also be applicable to other future link technologies\n with high loss and long round trip times.\n\n The following requirements have, more or less arbitrarily, been\n divided into three groups. The first group deals with ","scope_keywords":["3096","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3243","folder":"IETF/RFC-3243","source":"IETF/RFC-3243/RFC-3243.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 3096 This document contains requirements for robust IP/UDP/RTP (Internet\n Protocol/User Datagram Protocol/Real-Time Transport Protocol) header\n compression to be developed by the ROHC (Robust Header Compression)\n WG. It is based on the ROHC charter, discussions in the WG, the 3GPP\n document \"3GPP TR 23.922\", version 1.0.0 of October 1999, as well as\n contributions from 3G.IP.\n\n1. Introduction\n\n The goal of the ROHC WG is to develop header compression schemes that\n perform well over links with high error rates and long link round\n trip times. The schemes must perform well for cellular links built\n using technologies such as WCDMA, EDGE, and CDMA-2000. However, the\n schemes should also be applicable to other future link technologies\n with high loss and long round trip times.\n\n The following requirements have, more or less arbitrarily, been\n divided into three groups. The first group deals with  3096 path nested-reference unchanged"},{"id":"IETF RFC 3150","type":"specification","body":"IETF","designation":"RFC 3150","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3150.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3150.txt","https://www.rfc-editor.org/rfc/rfc3150.pdf"],"folder":"IETF/RFC-3150","files":{"txt":{"path":"standards/IETF/RFC-3150/RFC-3150.txt","sha256":"0d5067025ef102f2c44ac3a6c05a4bb5ebf46475020ced2392d6481855e72c50"}},"tags":["nested-reference","unchanged"],"summary":"This document makes performance-related recommendations for users of\n network paths that traverse \"very low bit-rate\" links.\n\n \"Very low bit-rate\" implies \"slower than we would like\". This\n recommendation may be useful in any network where hosts can saturate\n available bandwidth, but the design space for this recommendation\n explicitly includes connections that traverse 56 Kb/second modem\n links or 4.8 Kb/second wireless access links - both of which are\n widely deployed.\n\n This document discusses general-purpose mechanisms. Where\n application-specific mechanisms can outperform the relevant general-\n purpose mechanism, we point this out and explain why.\n\n This document has some recommendations in common with RFC 2689,\n \"Providing integrated services over low-bitrate links\", especially in\n areas like header compression. This document focuses more on\n traditional data applications for which","scope_keywords":["3150","delivery","path","pid","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3150 This document makes performance-related recommendations for users of\n network paths that traverse \"very low bit-rate\" links.\n\n \"Very low bit-rate\" implies \"slower than we would like\". This\n recommendation may be useful in any network where hosts can saturate\n available bandwidth, but the design space for this recommendation\n explicitly includes connections that traverse 56 Kb/second modem\n links or 4.8 Kb/second wireless access links - both of which are\n widely deployed.\n\n This document discusses general-purpose mechanisms. Where\n application-specific mechanisms can outperform the relevant general-\n purpose mechanism, we point this out and explain why.\n\n This document has some recommendations in common with RFC 2689,\n \"Providing integrated services over low-bitrate links\", especially in\n areas like header compression. This document focuses more on\n traditional data applications for which 3150 delivery path pid timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3229","type":"specification","body":"IETF","designation":"RFC 3229","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3229.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3229.txt","https://www.rfc-editor.org/rfc/rfc3229.pdf"],"folder":"IETF/RFC-3229","files":{"txt":{"path":"standards/IETF/RFC-3229/RFC-3229.txt","sha256":"eb70092bd992dc08b90813b0bea13356348e646ad11f7b70a99937d9af46573e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how delta encoding can be supported as a\n compatible extension to HTTP/1.1.\n\n Many HTTP (Hypertext Transport Protocol) requests cause the retrieval\n of slightly modified instances of resources for which the client\n already has a cache entry. Research has shown that such modifying\n updates are frequent, and that the modifications are typically much\n smaller than the actual entity. In such cases, HTTP would make more\n efficient use of network bandwidth if it could transfer a minimal\n description of the changes, rather than the entire new instance of\n the resource. This is called \"delta encoding.\"\n\nMogul, et al. Standards Track [Page 1]\n\f\nRFC 3229 Delta encoding in HTTP January 2002","scope_keywords":["3229","algorithm","algorithms","http","identification","management","timestamp","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null}],"search_text":"IETF RFC 3229 This document describes how delta encoding can be supported as a\n compatible extension to HTTP/1.1.\n\n Many HTTP (Hypertext Transport Protocol) requests cause the retrieval\n of slightly modified instances of resources for which the client\n already has a cache entry. Research has shown that such modifying\n updates are frequent, and that the modifications are typically much\n smaller than the actual entity. In such cases, HTTP would make more\n efficient use of network bandwidth if it could transfer a minimal\n description of the changes, rather than the entire new instance of\n the resource. This is called \"delta encoding.\"\n\nMogul, et al. Standards Track [Page 1]\n\f\nRFC 3229 Delta encoding in HTTP January 2002 3229 algorithm algorithms http identification management timestamp validation nested-reference unchanged"},{"id":"IETF RFC 3241","type":"specification","body":"IETF","designation":"RFC 3241","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3241.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3241.txt","https://www.rfc-editor.org/rfc/rfc3241.pdf"],"folder":"IETF/RFC-3241","files":{"txt":{"path":"standards/IETF/RFC-3241/RFC-3241.txt","sha256":"20b80191ae53da4bdc1fde599888eed35ff92dbeb7392d50b9d2fd2b4c724a25"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an option for negotiating the use of robust\n header compression (ROHC) on IP datagrams transmitted over the\n Point-to-Point Protocol (PPP). It defines extensions to the PPP\n Control Protocols for IPv4 and IPv6.\n\n1. Introduction\n\n Robust Header Compression (ROHC) as defined in [RFC3095] may be used\n for compression of both IPv4 and IPv6 datagrams or packets\n encapsulated with multiple IP headers. The initial version of ROHC\n focuses on compression of the packet headers in RTP streams, while\n supporting compression of other UDP flows; however, it also defines a\n framework into which further header compression mechanisms can be\n plugged as new profiles. Planned additions to the set of profiles\n supported by ROHC will be capable of compressing TCP transport\n protocol headers as well.\n\n In order to establish compression of IP datagrams sent over a PPP\n link each end of","scope_keywords":["3241","key","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null}],"search_text":"IETF RFC 3241 This document describes an option for negotiating the use of robust\n header compression (ROHC) on IP datagrams transmitted over the\n Point-to-Point Protocol (PPP). It defines extensions to the PPP\n Control Protocols for IPv4 and IPv6.\n\n1. Introduction\n\n Robust Header Compression (ROHC) as defined in [RFC3095] may be used\n for compression of both IPv4 and IPv6 datagrams or packets\n encapsulated with multiple IP headers. The initial version of ROHC\n focuses on compression of the packet headers in RTP streams, while\n supporting compression of other UDP flows; however, it also defines a\n framework into which further header compression mechanisms can be\n plugged as new profiles. Planned additions to the set of profiles\n supported by ROHC will be capable of compressing TCP transport\n protocol headers as well.\n\n In order to establish compression of IP datagrams sent over a PPP\n link each end of 3241 key profile profiles nested-reference unchanged"},{"id":"IETF RFC 3242","type":"specification","body":"IETF","designation":"RFC 3242","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3242.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3242.txt","https://www.rfc-editor.org/rfc/rfc3242.pdf"],"folder":"IETF/RFC-3242","files":{"txt":{"path":"standards/IETF/RFC-3242/RFC-3242.txt","sha256":"29acc8b151f9b6f5e9755ad4a1ade7ef85d8aaafc72150dc610e948de7f9055d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a ROHC (Robust Header Compression) profile for\n compression of IP/UDP/RTP (Internet Protocol/User Datagram\n Protocol/Real-Time Transport Protocol) packets, utilizing\n functionality provided by the lower layers to increase compression\n efficiency by completely eliminating the header for most packets\n during optimal operation. The profile is built as an extension to\n the ROHC RTP profile. It defines additional mechanisms needed in\n ROHC, states requirements on the assisting layer to guarantee\n transparency, and specifies general logic for compression and\n decompression making use of this header-free packet.","scope_keywords":["3242","driving","identification","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3243","folder":"IETF/RFC-3243","source":"IETF/RFC-3243/RFC-3243.txt","version":null},{"body":"IETF","designation":"RFC 3408","folder":"IETF/RFC-3408","source":"IETF/RFC-3408/RFC-3408.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 3242 This document defines a ROHC (Robust Header Compression) profile for\n compression of IP/UDP/RTP (Internet Protocol/User Datagram\n Protocol/Real-Time Transport Protocol) packets, utilizing\n functionality provided by the lower layers to increase compression\n efficiency by completely eliminating the header for most packets\n during optimal operation. The profile is built as an extension to\n the ROHC RTP profile. It defines additional mechanisms needed in\n ROHC, states requirements on the assisting layer to guarantee\n transparency, and specifies general logic for compression and\n decompression making use of this header-free packet. 3242 driving identification path profile profiles nested-reference unchanged"},{"id":"IETF RFC 3544","type":"specification","body":"IETF","designation":"RFC 3544","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3544.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3544.txt","https://www.rfc-editor.org/rfc/rfc3544.pdf"],"folder":"IETF/RFC-3544","files":{"txt":{"path":"standards/IETF/RFC-3544/RFC-3544.txt","sha256":"f337e64995e5c3f86581ce93ada546159a118b745aa4d883ced2a2549f5a1e9f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an option for negotiating the use of header\n compression on IP datagrams transmitted over the Point-to-Point\n Protocol (RFC 1661). It defines extensions to the PPP Control\n Protocols for IPv4 and IPv6 (RFC 1332, RFC 2472). Header compression\n may be applied to IPv4 and IPv6 datagrams in combination with TCP,\n UDP and RTP transport protocols as specified in RFC 2507, RFC 2508\n and RFC 3545.\n\n1. Introduction\n\n The IP Header Compression (IPHC) defined in [RFC2507] may be used for\n compression of both IPv4 and IPv6 datagrams or packets encapsulated\n with multiple IP headers. IPHC is also capable of compressing both\n TCP and UDP transport protocol headers. The IP/UDP/RTP header\n compression defined in [RFC2508] and [RFC3545] fits within the\n framework defined by IPHC so that it may also be applied to both IPv4\n and IPv6 packets.\n\nKoren, et al. Standards Track [Page 1]\n","scope_keywords":["3544"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null}],"search_text":"IETF RFC 3544 This document describes an option for negotiating the use of header\n compression on IP datagrams transmitted over the Point-to-Point\n Protocol (RFC 1661). It defines extensions to the PPP Control\n Protocols for IPv4 and IPv6 (RFC 1332, RFC 2472). Header compression\n may be applied to IPv4 and IPv6 datagrams in combination with TCP,\n UDP and RTP transport protocols as specified in RFC 2507, RFC 2508\n and RFC 3545.\n\n1. Introduction\n\n The IP Header Compression (IPHC) defined in [RFC2507] may be used for\n compression of both IPv4 and IPv6 datagrams or packets encapsulated\n with multiple IP headers. IPHC is also capable of compressing both\n TCP and UDP transport protocol headers. The IP/UDP/RTP header\n compression defined in [RFC2508] and [RFC3545] fits within the\n framework defined by IPHC so that it may also be applied to both IPv4\n and IPv6 packets.\n\nKoren, et al. Standards Track [Page 1]\n 3544 nested-reference unchanged"},{"id":"IETF RFC 4163","type":"specification","body":"IETF","designation":"RFC 4163","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4163.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4163.txt","https://www.rfc-editor.org/rfc/rfc4163.pdf"],"folder":"IETF/RFC-4163","files":{"txt":{"path":"standards/IETF/RFC-4163/RFC-4163.txt","sha256":"66d446ea3d24ca7c7f05406928e231ddc6ecf782ef03cf9dc5de1ce7c913f0b5"}},"tags":["nested-reference","unchanged"],"summary":"This document contains requirements on the TCP/IP header compression\n scheme (profile) to be developed by the RObust Header Compression\n (ROHC) Working Group. The document discusses the scope of TCP\n compression, performance considerations, assumptions about the\n surrounding environment, as well as Intellectual Property Rights\n concerns. The structure of this document is inherited from RFC 3096,\n which defines IP/UDP/RTP requirements for ROHC.","scope_keywords":["4163","algorithm","encryption","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4164","folder":"IETF/RFC-4164","source":"IETF/RFC-4164/RFC-4164.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 4163 This document contains requirements on the TCP/IP header compression\n scheme (profile) to be developed by the RObust Header Compression\n (ROHC) Working Group. The document discusses the scope of TCP\n compression, performance considerations, assumptions about the\n surrounding environment, as well as Intellectual Property Rights\n concerns. The structure of this document is inherited from RFC 3096,\n which defines IP/UDP/RTP requirements for ROHC. 4163 algorithm encryption profile nested-reference unchanged"},{"id":"IETF RFC 4362","type":"specification","body":"IETF","designation":"RFC 4362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4362.txt","https://www.rfc-editor.org/rfc/rfc4362.pdf"],"folder":"IETF/RFC-4362","files":{"txt":{"path":"standards/IETF/RFC-4362/RFC-4362.txt","sha256":"417c805a5fdc701c993c5fe1117db357fbbf500621cf3231c240d870680a32b1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a ROHC (Robust Header Compression) profile for\n compression of IP/UDP/RTP (Internet Protocol/User Datagram\n Protocol/Real-Time Transport Protocol) packets, utilizing\n functionality provided by the lower layers to increase compression\n efficiency by completely eliminating the header for most packets\n during optimal operation. The profile is built as an extension to\n the ROHC RTP profile. It defines additional mechanisms needed in\n ROHC, states requirements on the assisting layer to guarantee\n transparency, and specifies general logic for compression and\n decompression related to the usage of the header-free packet format.\n This document is a replacement for RFC 3242, which it obsoletes.\n\nJonsson, et al. Standards Track [Page 1]\n\f\nRFC 4362 A Link-Layer Assisted ROHC RTP January 2006","scope_keywords":["4362","driving","identification","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null}],"search_text":"IETF RFC 4362 This document defines a ROHC (Robust Header Compression) profile for\n compression of IP/UDP/RTP (Internet Protocol/User Datagram\n Protocol/Real-Time Transport Protocol) packets, utilizing\n functionality provided by the lower layers to increase compression\n efficiency by completely eliminating the header for most packets\n during optimal operation. The profile is built as an extension to\n the ROHC RTP profile. It defines additional mechanisms needed in\n ROHC, states requirements on the assisting layer to guarantee\n transparency, and specifies general logic for compression and\n decompression related to the usage of the header-free packet format.\n This document is a replacement for RFC 3242, which it obsoletes.\n\nJonsson, et al. Standards Track [Page 1]\n\f\nRFC 4362 A Link-Layer Assisted ROHC RTP January 2006 4362 driving identification path profile profiles nested-reference unchanged"},{"id":"IETF RFC 4828","type":"specification","body":"IETF","designation":"RFC 4828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4828.txt","https://www.rfc-editor.org/rfc/rfc4828.pdf"],"folder":"IETF/RFC-4828","files":{"txt":{"path":"standards/IETF/RFC-4828/RFC-4828.txt","sha256":"1ebb9efa2822224799b2e83223f7afbb5beb3962134b42228e723bdfbd5436bd"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a mechanism for further experimentation, but\n not for widespread deployment at this time in the global Internet.\n\n TCP-Friendly Rate Control (TFRC) is a congestion control mechanism\n for unicast flows operating in a best-effort Internet environment\n (RFC 3448). TFRC was intended for applications that use a fixed\n packet size, and was designed to be reasonably fair when competing\n for bandwidth with TCP connections using the same packet size. This\n document proposes TFRC-SP, a Small-Packet (SP) variant of TFRC, that\n is designed for applications that send small packets. The design\n goal for TFRC-SP is to achieve the same bandwidth in bps (bits per\n second) as a TCP flow using packets of up to 1500 bytes. TFRC-SP\n enforces a minimum interval of 10 ms between data packets to prevent\n a single flow from sending small packets arbitrarily frequently.\n\n Flows using TFRC-S","scope_keywords":["4828","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null}],"search_text":"IETF RFC 4828 This document proposes a mechanism for further experimentation, but\n not for widespread deployment at this time in the global Internet.\n\n TCP-Friendly Rate Control (TFRC) is a congestion control mechanism\n for unicast flows operating in a best-effort Internet environment\n (RFC 3448). TFRC was intended for applications that use a fixed\n packet size, and was designed to be reasonably fair when competing\n for bandwidth with TCP connections using the same packet size. This\n document proposes TFRC-SP, a Small-Packet (SP) variant of TFRC, that\n is designed for applications that send small packets. The design\n goal for TFRC-SP is to achieve the same bandwidth in bps (bits per\n second) as a TCP flow using packets of up to 1500 bytes. TFRC-SP\n enforces a minimum interval of 10 ms between data packets to prevent\n a single flow from sending small packets arbitrarily frequently.\n\n Flows using TFRC-S 4828 path trust nested-reference unchanged"},{"id":"IETF RFC 4995","type":"specification","body":"IETF","designation":"RFC 4995","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4995.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4995.txt","https://www.rfc-editor.org/rfc/rfc4995.pdf"],"folder":"IETF/RFC-4995","files":{"txt":{"path":"standards/IETF/RFC-4995/RFC-4995.txt","sha256":"ce937c5a4e820d855381f4748227718a294c1c5f81b44e309cf7a6ec3cb98810"}},"tags":["nested-reference","unchanged"],"summary":"The Robust Header Compression (ROHC) protocol provides an efficient,\n flexible, and future-proof header compression concept. It is\n designed to operate efficiently and robustly over various link\n technologies with different characteristics.\n\n The ROHC framework, along with a set of compression profiles, was\n initially defined in RFC 3095. To improve and simplify the ROHC\n specifications, this document explicitly defines the ROHC framework\n and the profile for uncompressed separately. More specifically, the\n definition of the framework does not modify or update the definition\n of the framework specified by RFC 3095.","scope_keywords":["4995","algorithm","algorithms","profile","profiles","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 4995 The Robust Header Compression (ROHC) protocol provides an efficient,\n flexible, and future-proof header compression concept. It is\n designed to operate efficiently and robustly over various link\n technologies with different characteristics.\n\n The ROHC framework, along with a set of compression profiles, was\n initially defined in RFC 3095. To improve and simplify the ROHC\n specifications, this document explicitly defines the ROHC framework\n and the profile for uncompressed separately. More specifically, the\n definition of the framework does not modify or update the definition\n of the framework specified by RFC 3095. 4995 algorithm algorithms profile profiles trust nested-reference unchanged"},{"id":"IETF RFC 1149","type":"specification","body":"IETF","designation":"RFC 1149","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1149.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1149.txt","https://www.rfc-editor.org/rfc/rfc1149.pdf"],"folder":"IETF/RFC-1149","files":{"txt":{"path":"standards/IETF/RFC-1149/RFC-1149.txt","sha256":"a8660fa4f47bd5e3db1cd5d5baad983d8b6f3f1e8a1a04b8552f3c2ce8f33c18"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Waitzman\nRequest for Comments: 1149 BBN STC\n 1 April 1990\n\n A Standard for the Transmission of IP Datagrams on Avian Carriers\n\nStatus of this Memo\n\n This memo describes an experimental method for the encapsulation of\n IP datagrams in avian carriers. This specification is primarily\n useful in Metropolitan Area Networks. This is an experimental, not\n recommended standard. Distribution of this memo is unlimited.\n\nOverview and Rational\n\n Avian carriers can provide high delay, low throughput, and low\n altitude service. The connection topology is limited to a single\n point-to-point path for each carrier, used with standard carriers,\n but many carriers can be used without significant interference with\n each other, outside of early spring. This is because of the 3D ether\n space available to the carriers, in contrast to the 1D ether used by\n IEEE802.3. The carriers have a","scope_keywords":["1149","audit","delivery","encryption","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1543","folder":"IETF/RFC-1543","source":"IETF/RFC-1543/RFC-1543.txt","version":null},{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 2322","folder":"IETF/RFC-2322","source":"IETF/RFC-2322/RFC-2322.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null}],"search_text":"IETF RFC 1149 Network Working Group D. Waitzman\nRequest for Comments: 1149 BBN STC\n 1 April 1990\n\n A Standard for the Transmission of IP Datagrams on Avian Carriers\n\nStatus of this Memo\n\n This memo describes an experimental method for the encapsulation of\n IP datagrams in avian carriers. This specification is primarily\n useful in Metropolitan Area Networks. This is an experimental, not\n recommended standard. Distribution of this memo is unlimited.\n\nOverview and Rational\n\n Avian carriers can provide high delay, low throughput, and low\n altitude service. The connection topology is limited to a single\n point-to-point path for each carrier, used with standard carriers,\n but many carriers can be used without significant interference with\n each other, outside of early spring. This is because of the 3D ether\n space available to the carriers, in contrast to the 1D ether used by\n IEEE802.3. The carriers have a 1149 audit delivery encryption path nested-reference unchanged"},{"id":"IETF RFC 1543","type":"specification","body":"IETF","designation":"RFC 1543","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1543.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1543.txt","https://www.rfc-editor.org/rfc/rfc1543.pdf"],"folder":"IETF/RFC-1543","files":{"txt":{"path":"standards/IETF/RFC-1543/RFC-1543.txt","sha256":"baf75d89ca703c52ed6c0232ffd7776b7c19a3b2fa32b8cc5dbeefb030e547bb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1543 ISI\nObsoletes: RFCs 1111, 825 October 1993\nCategory: Informational\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3\n 3. Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4\n 3a. ASCII Format Rules . . . . . . . . . . . . . . . . . . . . 4\n 3b. PostScript Format Rules . . . . . . . . . . . . . . . . . . 5\n 4. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 6\n 4a. First Page Heading . . . . . . . . . . . . . . . . . . . . 6\n 4b. Running Header . . . . . . . . . . . . . . . . . . . . . . 7\n 4c. R","scope_keywords":["1543","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1550","folder":"IETF/RFC-1550","source":"IETF/RFC-1550/RFC-1550.txt","version":null},{"body":"IETF","designation":"RFC 1590","folder":"IETF/RFC-1590","source":"IETF/RFC-1590/RFC-1590.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1602","folder":"IETF/RFC-1602","source":"IETF/RFC-1602/RFC-1602.txt","version":null},{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1916","folder":"IETF/RFC-1916","source":"IETF/RFC-1916/RFC-1916.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2026","folder":"IETF/RFC-2026","source":"IETF/RFC-2026/RFC-2026.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null}],"search_text":"IETF RFC 1543 Network Working Group J. Postel\nRequest for Comments: 1543 ISI\nObsoletes: RFCs 1111, 825 October 1993\nCategory: Informational\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3\n 3. Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4\n 3a. ASCII Format Rules . . . . . . . . . . . . . . . . . . . . 4\n 3b. PostScript Format Rules . . . . . . . . . . . . . . . . . . 5\n 4. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 6\n 4a. First Page Heading . . . . . . . . . . . . . . . . . . . . 6\n 4b. Running Header . . . . . . . . . . . . . . . . . . . . . . 7\n 4c. R 1543 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 1818","type":"specification","body":"IETF","designation":"RFC 1818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1818.txt","https://www.rfc-editor.org/rfc/rfc1818.pdf"],"folder":"IETF/RFC-1818","files":{"txt":{"path":"standards/IETF/RFC-1818/RFC-1818.txt","sha256":"985dbd70b0af0406c5f9a87dc14bc8aa694f426903d6b9d1c35ee534be9de039"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 1818 ISI\nBCP: 1 T. Li\nCategory: Best Current Practice cisco Systems\n Y. Rekhter\n cisco Systems\n August 1995\n\n Best Current Practices\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes a new series of documents which describe best\n current practices for the Internet community. Documents in this\n series carry the endorsement of the Internet Engineering Steering\n Group (IESG).\n\nDiscussion\n\n The current IETF process has two types of RFCs: standards track\n documents and other RFCs (e.g., informational, experimental, FYIs)\n [1]. The intent of the standards track documents is clear, and\n culminates in an official Internet Standard [2,3]. Informationa","scope_keywords":["1818","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 3967","folder":"IETF/RFC-3967","source":"IETF/RFC-3967/RFC-3967.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"IETF RFC 1818 Network Working Group J. Postel\nRequest for Comments: 1818 ISI\nBCP: 1 T. Li\nCategory: Best Current Practice cisco Systems\n Y. Rekhter\n cisco Systems\n August 1995\n\n Best Current Practices\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes a new series of documents which describe best\n current practices for the Internet community. Documents in this\n series carry the endorsement of the Internet Engineering Steering\n Group (IESG).\n\nDiscussion\n\n The current IETF process has two types of RFCs: standards track\n documents and other RFCs (e.g., informational, experimental, FYIs)\n [1]. The intent of the standards track documents is clear, and\n culminates in an official Internet Standard [2,3]. Informationa 1818 subject nested-reference unchanged"},{"id":"IETF RFC 2223","type":"specification","body":"IETF","designation":"RFC 2223","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2223.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2223.txt","https://www.rfc-editor.org/rfc/rfc2223.pdf"],"folder":"IETF/RFC-2223","files":{"txt":{"path":"standards/IETF/RFC-2223/RFC-2223.txt","sha256":"5fd0ce0e3a73b471d5a25592bad868011ac86e6fdd1df2426d8c2619c506e687"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 2223 J. Reynolds\nObsoletes: 1543, 1111, 825 ISI\nCategory: Informational October 1997\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3\n 3. Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4\n 3a. ASCII Format Rules . . . . . . . . . . . . . . . . . . . . 5\n 3b. PostScript Format Rules . . . . . . . . . . . . . . . . . . 6\n 4. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 7\n 4a. First Page Heading . . . . . . . . .","scope_keywords":["2223","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 2436","folder":"IETF/RFC-2436","source":"IETF/RFC-2436/RFC-2436.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2629","folder":"IETF/RFC-2629","source":"IETF/RFC-2629/RFC-2629.txt","version":null},{"body":"IETF","designation":"RFC 2717","folder":"IETF/RFC-2717","source":"IETF/RFC-2717/RFC-2717.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3131","folder":"IETF/RFC-3131","source":"IETF/RFC-3131/RFC-3131.txt","version":null},{"body":"IETF","designation":"RFC 3285","folder":"IETF/RFC-3285","source":"IETF/RFC-3285/RFC-3285.txt","version":null},{"body":"IETF","designation":"RFC 3327","folder":"IETF/RFC-3327","source":"IETF/RFC-3327/RFC-3327.txt","version":null},{"body":"IETF","designation":"RFC 3356","folder":"IETF/RFC-3356","source":"IETF/RFC-3356/RFC-3356.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3608","folder":"IETF/RFC-3608","source":"IETF/RFC-3608/RFC-3608.txt","version":null},{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6949","folder":"IETF/RFC-6949","source":"IETF/RFC-6949/RFC-6949.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null}],"search_text":"IETF RFC 2223 Network Working Group J. Postel\nRequest for Comments: 2223 J. Reynolds\nObsoletes: 1543, 1111, 825 ISI\nCategory: Informational October 1997\n\n Instructions to RFC Authors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2\n 2. Editorial Policy . . . . . . . . . . . . . . . . . . . . . . 3\n 3. Format Rules . . . . . . . . . . . . . . . . . . . . . . . . 4\n 3a. ASCII Format Rules . . . . . . . . . . . . . . . . . . . . 5\n 3b. PostScript Format Rules . . . . . . . . . . . . . . . . . . 6\n 4. Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 7\n 4a. First Page Heading . . . . . . . . . 2223 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 2322","type":"specification","body":"IETF","designation":"RFC 2322","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2322.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2322.txt","https://www.rfc-editor.org/rfc/rfc2322.pdf"],"folder":"IETF/RFC-2322","files":{"txt":{"path":"standards/IETF/RFC-2322/RFC-2322.txt","sha256":"08dbda414c9c150494d715303fb28cce595fb40472fd29b30a3d6f70587f591b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. van den Hout\nRequest for Comments: 2322 HvU/HIP-networkteam\nCategory: Informational A. Koopal\n UUnet NL/HIP-networkteam\n R. van Mook\n University of Twente/HIP-networkteam\n 1 April 1998\n\n Management of IP numbers by peg-dhcp\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIntroduction\n\n This RFC describes a protocol to dynamically hand out ip-numbers on\n field networks and small events that don't necessarily have a clear\n organisational body.\n\n It can also provide some fixed additional fields global for all\n clients like netmask and even autoproxyconfigs. It does not depend on\n a particular ip-stack.\n\nHistory of the protocol.\n\n The practice of using peg","scope_keywords":["2322","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"IETF RFC 2322 Network Working Group K. van den Hout\nRequest for Comments: 2322 HvU/HIP-networkteam\nCategory: Informational A. Koopal\n UUnet NL/HIP-networkteam\n R. van Mook\n University of Twente/HIP-networkteam\n 1 April 1998\n\n Management of IP numbers by peg-dhcp\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIntroduction\n\n This RFC describes a protocol to dynamically hand out ip-numbers on\n field networks and small events that don't necessarily have a clear\n organisational body.\n\n It can also provide some fixed additional fields global for all\n clients like netmask and even autoproxyconfigs. It does not depend on\n a particular ip-stack.\n\nHistory of the protocol.\n\n The practice of using peg 2322 http management nested-reference unchanged"},{"id":"IETF RFC 7669","type":"specification","body":"IETF","designation":"RFC 7669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7669.txt","https://www.rfc-editor.org/rfc/rfc7669.pdf"],"folder":"IETF/RFC-7669","files":{"txt":{"path":"standards/IETF/RFC-7669/RFC-7669.txt","sha256":"7e26a3f4eb8d3f8cbf3ad6762c653d1057965abd5845240a4aa5ce93a0684a61"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the way that Digital Object Identifiers\n (DOIs) are assigned to past and future RFCs. The DOI is a widely\n used system that assigns unique identifiers to digital documents that\n can be queried and managed in a consistent fashion.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o","scope_keywords":["7669","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null}],"search_text":"IETF RFC 7669 This document describes the way that Digital Object Identifiers\n (DOIs) are assigned to past and future RFCs. The DOI is a widely\n used system that assigns unique identifiers to digital documents that\n can be queried and managed in a consistent fashion.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o 7669 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 7991","type":"specification","body":"IETF","designation":"RFC 7991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7991.txt","https://www.rfc-editor.org/rfc/rfc7991.pdf"],"folder":"IETF/RFC-7991","files":{"txt":{"path":"standards/IETF/RFC-7991/RFC-7991.txt","sha256":"ae8c75f080f5811d383d83edea7ff798c7689d28acf4bebc318e8e9cc5b45df3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the \"xml2rfc\" version 3 vocabulary: an\n XML-based language used for writing RFCs and Internet-Drafts. It is\n heavily derived from the version 2 vocabulary that is also under\n discussion. This document obsoletes the v2 grammar described in\n RFC 7749.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:","scope_keywords":["7991","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 7991 This document defines the \"xml2rfc\" version 3 vocabulary: an\n XML-based language used for writing RFCs and Internet-Drafts. It is\n heavily derived from the version 2 vocabulary that is also under\n discussion. This document obsoletes the v2 grammar described in\n RFC 7749.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http: 7991 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1150","type":"specification","body":"IETF","designation":"RFC 1150","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1150.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1150.txt","https://www.rfc-editor.org/rfc/rfc1150.pdf"],"folder":"IETF/RFC-1150","files":{"txt":{"path":"standards/IETF/RFC-1150/RFC-1150.txt","sha256":"ed41d1f2c3c37a09c5508b80118eb582e806a8f8724c027d197aacc26982d152"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1150 Proteon\nFYI: 1 J. Reynolds\n ISI\n March 1990\n\n F.Y.I. on F.Y.I.\n\n Introduction to the F.Y.I. Notes\n\nStatus of this Memo\n\n This RFC is the first in a new sub-series of RFCs called FYIs (For\n Your Information). This memo provides information for the Internet\n community. It does not specify any standard. Distribution of this\n memo is unlimited.\n\n1. Introduction\n\n The FYI series of notes is designed to provide Internet users with a\n central repository of information about any topics which relate to\n the Internet. FYIs topics may range from historical memos on \"Why it\n was was done this way\" to answers to commonly asked operational\n questions.\n\n The FYIs are intended for a wide audience. Some FYIs will cater to\n beginners, while others will discuss more advanced topics. An FYI\n may be submitted by anyone who has something to contribute","scope_keywords":["1150","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 6360","folder":"IETF/RFC-6360","source":"IETF/RFC-6360/RFC-6360.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"IETF RFC 1150 Network Working Group G. Malkin\nRequest for Comments: 1150 Proteon\nFYI: 1 J. Reynolds\n ISI\n March 1990\n\n F.Y.I. on F.Y.I.\n\n Introduction to the F.Y.I. Notes\n\nStatus of this Memo\n\n This RFC is the first in a new sub-series of RFCs called FYIs (For\n Your Information). This memo provides information for the Internet\n community. It does not specify any standard. Distribution of this\n memo is unlimited.\n\n1. Introduction\n\n The FYI series of notes is designed to provide Internet users with a\n central repository of information about any topics which relate to\n the Internet. FYIs topics may range from historical memos on \"Why it\n was was done this way\" to answers to commonly asked operational\n questions.\n\n The FYIs are intended for a wide audience. Some FYIs will cater to\n beginners, while others will discuss more advanced topics. An FYI\n may be submitted by anyone who has something to contribute 1150 path subject nested-reference unchanged"},{"id":"IETF RFC 1603","type":"specification","body":"IETF","designation":"RFC 1603","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1603.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1603.txt","https://www.rfc-editor.org/rfc/rfc1603.pdf"],"folder":"IETF/RFC-1603","files":{"txt":{"path":"standards/IETF/RFC-1603/RFC-1603.txt","sha256":"912f590e6c69735eae24421fefdf095b59e12d00798171769b1de82e73db9f08"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Engineering Task Force (IETF) has responsibility for\n developing and reviewing specifications intended as Internet\n Standards. IETF activities are organized into working groups (WGs).\n This document describes the guidelines and procedures for formation\n and operation of IETF working groups. It describes the formal\n relationship between IETF participants WG and the Internet\n Engineering Steering Group (IESG). The basic duties of IETF\n participants, including WG Chair and IESG Area Directors are defined.","scope_keywords":["1603","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1871","folder":"IETF/RFC-1871","source":"IETF/RFC-1871/RFC-1871.txt","version":null},{"body":"IETF","designation":"RFC 2014","folder":"IETF/RFC-2014","source":"IETF/RFC-2014/RFC-2014.txt","version":null},{"body":"IETF","designation":"RFC 2028","folder":"IETF/RFC-2028","source":"IETF/RFC-2028/RFC-2028.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 7282","folder":"IETF/RFC-7282","source":"IETF/RFC-7282/RFC-7282.txt","version":null}],"search_text":"IETF RFC 1603 The Internet Engineering Task Force (IETF) has responsibility for\n developing and reviewing specifications intended as Internet\n Standards. IETF activities are organized into working groups (WGs).\n This document describes the guidelines and procedures for formation\n and operation of IETF working groups. It describes the formal\n relationship between IETF participants WG and the Internet\n Engineering Steering Group (IESG). The basic duties of IETF\n participants, including WG Chair and IESG Area Directors are defined. 1603 management nested-reference unchanged"},{"id":"IETF RFC 6360","type":"specification","body":"IETF","designation":"RFC 6360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6360.txt","https://www.rfc-editor.org/rfc/rfc6360.pdf"],"folder":"IETF/RFC-6360","files":{"txt":{"path":"standards/IETF/RFC-6360/RFC-6360.txt","sha256":"9121a47514c9688a04b328e1d89d3aa31b7dd2be145db64570f6dd12fb00a132"}},"tags":["nested-reference","unchanged"],"summary":"This document concludes the For Your Information (FYI) sub-series of\n RFCs, established by RFC 1150 for use by the IETF User Services Area,\n which no longer exists. The IESG does not intend to make any further\n additions to this RFC sub-series, and this document provides a record\n of this decision. This document also obsoletes RFC 1150 and changes\n the status of RFC 1150 to Historic.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informatio","scope_keywords":["6360","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"IETF RFC 6360 This document concludes the For Your Information (FYI) sub-series of\n RFCs, established by RFC 1150 for use by the IETF User Services Area,\n which no longer exists. The IESG does not intend to make any further\n additions to this RFC sub-series, and this document provides a record\n of this decision. This document also obsoletes RFC 1150 and changes\n the status of RFC 1150 to Historic.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informatio 6360 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 1151","type":"specification","body":"IETF","designation":"RFC 1151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1151.txt","https://www.rfc-editor.org/rfc/rfc1151.pdf"],"folder":"IETF/RFC-1151","files":{"txt":{"path":"standards/IETF/RFC-1151/RFC-1151.txt","sha256":"58be7248bc7ea68e5c2f84a883b38d147367904854e8bccf1970f5409aeb7ffb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Partridge\nRequest for Comments: 1151 BBN Systems and Technologies\nUpdates: RFC 908 R. Hinden\n BBN Communications Corp.\n April 1990\n\n Version 2 of the Reliable Data Protocol (RDP)\n\nStatus of this Memo\n\n This RFC suggests several updates to the specification of the\n Reliable Data Protocol (RDP) in RFC-908 based on experience with the\n protocol. This revised version of the protocol is experimental.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Experiments in 1986 and 1987 turned up some ambiguities and problems\n with the RDP specification. At the time, it was hoped that the\n authors might find the time to revise the entire RDP specification to\n fix these problems, however given the limited demand for RDP\n implementations, the authors were never able to justify the time\n involved in revising the spec. This document lists the changes that\n we believe are a","scope_keywords":["1151","algorithm","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 1151 Network Working Group C. Partridge\nRequest for Comments: 1151 BBN Systems and Technologies\nUpdates: RFC 908 R. Hinden\n BBN Communications Corp.\n April 1990\n\n Version 2 of the Reliable Data Protocol (RDP)\n\nStatus of this Memo\n\n This RFC suggests several updates to the specification of the\n Reliable Data Protocol (RDP) in RFC-908 based on experience with the\n protocol. This revised version of the protocol is experimental.\n\n Distribution of this memo is unlimited.\n\nIntroduction\n\n Experiments in 1986 and 1987 turned up some ambiguities and problems\n with the RDP specification. At the time, it was hoped that the\n authors might find the time to revise the entire RDP specification to\n fix these problems, however given the limited demand for RDP\n implementations, the authors were never able to justify the time\n involved in revising the spec. This document lists the changes that\n we believe are a 1151 algorithm key presentation nested-reference unchanged"},{"id":"IETF RFC 1505","type":"specification","body":"IETF","designation":"RFC 1505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1505.txt","https://www.rfc-editor.org/rfc/rfc1505.pdf"],"folder":"IETF/RFC-1505","files":{"txt":{"path":"standards/IETF/RFC-1505/RFC-1505.txt","sha256":"e3973c6b0b1d7a7d6d15ff1c8a14195398e86674ce2f99a53e4f200158414c26"}},"tags":["nested-reference","unchanged"],"summary":"This document expands upon the elective experimental Encoding header\n field which permits the mailing of multi-part, multi-structured\n messages. It replaces RFC 1154 [1].","scope_keywords":["1505","attribute","attributes","key","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 1505 This document expands upon the elective experimental Encoding header\n field which permits the mailing of multi-part, multi-structured\n messages. It replaces RFC 1154 [1]. 1505 attribute attributes key presentation signature nested-reference unchanged"},{"id":"IETF RFC 1161","type":"specification","body":"IETF","designation":"RFC 1161","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1161.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1161.txt","https://www.rfc-editor.org/rfc/rfc1161.pdf"],"folder":"IETF/RFC-1161","files":{"txt":{"path":"standards/IETF/RFC-1161/RFC-1161.txt","sha256":"bc4551c52968f8a7d7811fa68f732efe824523607f5bbf495b29c25083c3b80c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose, Editor\nRequest for Comments: 1161 Performance Systems International, Inc.\n June 1990\n\n SNMP over OSI\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. Background ............................................ 1\n 2.1 A Digression on User Interfaces ...................... 2\n 2.1.1 Addressing Conventions for UDP-based service ....... 3\n 2.2 A Digression of Layering ............................. 3\n 3. Mapping onto CLTS ..................................... 4\n 3.1 Addressing Conventions ............................... 4\n 3.1.1 Conventions for CLNP-based service ................. 4\n 4. Mapping onto COTS ..................................... 4\n 4.1 Addressing Conventions ............................... 5\n 4.1.1 Conventions for TP4/CLNP-based service ............. 5\n 4.1.2 Conventions for TP0/X.25-based service ............. 6\n 5.","scope_keywords":["1161","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null}],"search_text":"IETF RFC 1161 Network Working Group M. Rose, Editor\nRequest for Comments: 1161 Performance Systems International, Inc.\n June 1990\n\n SNMP over OSI\n\n Table of Contents\n\n 1. Status of this Memo ................................... 1\n 2. Background ............................................ 1\n 2.1 A Digression on User Interfaces ...................... 2\n 2.1.1 Addressing Conventions for UDP-based service ....... 3\n 2.2 A Digression of Layering ............................. 3\n 3. Mapping onto CLTS ..................................... 4\n 3.1 Addressing Conventions ............................... 4\n 3.1.1 Conventions for CLNP-based service ................. 4\n 4. Mapping onto COTS ..................................... 4\n 4.1 Addressing Conventions ............................... 5\n 4.1.1 Conventions for TP4/CLNP-based service ............. 5\n 4.1.2 Conventions for TP0/X.25-based service ............. 6\n 5. 1161 management presentation nested-reference unchanged"},{"id":"IETF RFC 1227","type":"specification","body":"IETF","designation":"RFC 1227","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1227.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1227.txt","https://www.rfc-editor.org/rfc/rfc1227.pdf"],"folder":"IETF/RFC-1227","files":{"txt":{"path":"standards/IETF/RFC-1227/RFC-1227.txt","sha256":"fa2e7a8474ae338c7e919c11b792be35ba8bdf85b5de7622b1fee004aef43661"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1227 Performance Systems International, Inc.\n May 1991\n\n SNMP MUX Protocol and MIB\n\nStatus of this Memo\n\n This memo suggests a mechanism by which a user process may associate\n itself with the local SNMP agent on a host, in order to implement\n portions of the MIB. This mechanism would be local to the host.\n\n This is an Experimental Protocol for the Internet community.\n Discussion and suggestions for improvement are requested. Please\n refer to the current edition of the \"IAB Official Protocol Standards\"\n for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. Architecture .......................................... 2\n 3. Protocol .............................................. 3\n 3.1 Tricky Things ...............","scope_keywords":["1227","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1303","folder":"IETF/RFC-1303","source":"IETF/RFC-1303/RFC-1303.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1227 Network Working Group M. Rose\nRequest for Comments: 1227 Performance Systems International, Inc.\n May 1991\n\n SNMP MUX Protocol and MIB\n\nStatus of this Memo\n\n This memo suggests a mechanism by which a user process may associate\n itself with the local SNMP agent on a host, in order to implement\n portions of the MIB. This mechanism would be local to the host.\n\n This is an Experimental Protocol for the Internet community.\n Discussion and suggestions for improvement are requested. Please\n refer to the current edition of the \"IAB Official Protocol Standards\"\n for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. Architecture .......................................... 2\n 3. Protocol .............................................. 3\n 3.1 Tricky Things ............... 1227 management registered nested-reference unchanged"},{"id":"IETF RFC 1283","type":"specification","body":"IETF","designation":"RFC 1283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1283.txt","https://www.rfc-editor.org/rfc/rfc1283.pdf"],"folder":"IETF/RFC-1283","files":{"txt":{"path":"standards/IETF/RFC-1283/RFC-1283.txt","sha256":"74feddf4ca7ee87f0cc59d77a0e7a8675846a1799528ca979c05df212e18b98e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1283 Dover Beach Consulting, Inc.\nObsoletes: RFC 1161 December 1991\n\n SNMP over OSI\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Background ............................................ 1\n 1.1 A Digression on User Interfaces ...................... 2\n 1.1.1 Addressing Conventions for UDP-based service ....... 3\n 1.2 A Digression of Layering ............................. 3\n 2. Mapping onto CLTS ..................................... 3\n 2.1 Addressing Conventions ............................... 4\n 2.1.1 Conventions for CLNP-based servic","scope_keywords":["1283","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null}],"search_text":"IETF RFC 1283 Network Working Group M. Rose\nRequest for Comments: 1283 Dover Beach Consulting, Inc.\nObsoletes: RFC 1161 December 1991\n\n SNMP over OSI\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Background ............................................ 1\n 1.1 A Digression on User Interfaces ...................... 2\n 1.1.1 Addressing Conventions for UDP-based service ....... 3\n 1.2 A Digression of Layering ............................. 3\n 2. Mapping onto CLTS ..................................... 3\n 2.1 Addressing Conventions ............................... 4\n 2.1.1 Conventions for CLNP-based servic 1283 management presentation nested-reference unchanged"},{"id":"IETF RFC 1298","type":"specification","body":"IETF","designation":"RFC 1298","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1298.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1298.txt","https://www.rfc-editor.org/rfc/rfc1298.pdf"],"folder":"IETF/RFC-1298","files":{"txt":{"path":"standards/IETF/RFC-1298/RFC-1298.txt","sha256":"602f9b9eaa17fc31ca3bbc93bb4c775e896621ee4a65c849a59163bfe2d59bf0"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a convention for encapsulating Simple Network\n Management Protocol (SNMP) [1] packets over the transport mechanism\n provided via the Internetwork Packet Exchange (IPX) protocol [2].\n\nEditor's Note\n\n As stated below and in reference [5], it is strongly advised that for\n interoperability, SNMP be implemented over UDP/IP and not directly on\n media or other protocols (such as IPX).\n\n1. Introduction\n\n The SNMP protocol has been specified as the official network\n management protocol of the Internet. Its widespread acceptance and\n implementation by developers, both inside and outside the Internet\n community, is fostering synergetic growth to a variety of protocols\n and platforms.\n\n This memo addresses the use of SNMP over the IPX protocol, which has\n become quite widespread principally due to the popularity of Novell\n NetWare. Roughly equivalent to UDP in function, IPX provide","scope_keywords":["1298","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null}],"search_text":"IETF RFC 1298 This memo defines a convention for encapsulating Simple Network\n Management Protocol (SNMP) [1] packets over the transport mechanism\n provided via the Internetwork Packet Exchange (IPX) protocol [2].\n\nEditor's Note\n\n As stated below and in reference [5], it is strongly advised that for\n interoperability, SNMP be implemented over UDP/IP and not directly on\n media or other protocols (such as IPX).\n\n1. Introduction\n\n The SNMP protocol has been specified as the official network\n management protocol of the Internet. Its widespread acceptance and\n implementation by developers, both inside and outside the Internet\n community, is fostering synergetic growth to a variety of protocols\n and platforms.\n\n This memo addresses the use of SNMP over the IPX protocol, which has\n become quite widespread principally due to the popularity of Novell\n NetWare. Roughly equivalent to UDP in function, IPX provide 1298 management presentation nested-reference unchanged"},{"id":"IETF RFC 1303","type":"specification","body":"IETF","designation":"RFC 1303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1303.txt","https://www.rfc-editor.org/rfc/rfc1303.pdf"],"folder":"IETF/RFC-1303","files":{"txt":{"path":"standards/IETF/RFC-1303/RFC-1303.txt","sha256":"92c8c3a01e14be5ee6d2877162e9a424819851b767ee5d537d68def21774aad9"}},"tags":["nested-reference","unchanged"],"summary":"This memo suggests a straight-forward approach towards describing\n SNMP-based agents.","scope_keywords":["1303","authorization","management","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null}],"search_text":"IETF RFC 1303 This memo suggests a straight-forward approach towards describing\n SNMP-based agents. 1303 authorization management pid policy nested-reference unchanged"},{"id":"IETF RFC 1333","type":"specification","body":"IETF","designation":"RFC 1333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1333.txt","https://www.rfc-editor.org/rfc/rfc1333.pdf"],"folder":"IETF/RFC-1333","files":{"txt":{"path":"standards/IETF/RFC-1333/RFC-1333.txt","sha256":"a0ba1694ad399afd96e073f0a805876da32b963e8a4bf72ef03032b169e781bf"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, which\n allows negotiation of a Quality Protocol for continuous monitoring of\n the viability of the link.\n\n This document defines a protocol for generating Link-Quality-Reports.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu mailing list.\n\nSimpson [Page i]\n\f\nRFC 1333 PPP Link Quality Monitoring May 1992","scope_keywords":["1333","authentication","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"IETF RFC 1333 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, which\n allows negotiation of a Quality Protocol for continuous monitoring of\n the viability of the link.\n\n This document defines a protocol for generating Link-Quality-Reports.\n\n This RFC is a product of the Point-to-Point Protocol Working Group of\n the Internet Engineering Task Force (IETF). Comments on this memo\n should be submitted to the ietf-ppp@ucdavis.edu mailing list.\n\nSimpson [Page i]\n\f\nRFC 1333 PPP Link Quality Monitoring May 1992 1333 authentication policies policy nested-reference unchanged"},{"id":"IETF RFC 1353","type":"specification","body":"IETF","designation":"RFC 1353","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1353.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1353.txt","https://www.rfc-editor.org/rfc/rfc1353.pdf"],"folder":"IETF/RFC-1353","files":{"txt":{"path":"standards/IETF/RFC-1353/RFC-1353.txt","sha256":"4815c29abfe34794c76aa50890b421403f69058bfaac358c56e5ba77f6951d8a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes a representation of the SNMP parties\n defined in [8] as objects defined according to the Internet Standard\n SMI [1]. These definitions are consistent with the SNMP Security\n protocols set forth in [9].","scope_keywords":["1353","authentication","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1351","folder":"IETF/RFC-1351","source":"IETF/RFC-1351/RFC-1351.txt","version":null},{"body":"IETF","designation":"RFC 1352","folder":"IETF/RFC-1352","source":"IETF/RFC-1352/RFC-1352.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1353 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes a representation of the SNMP parties\n defined in [8] as objects defined according to the Internet Standard\n SMI [1]. These definitions are consistent with the SNMP Security\n protocols set forth in [9]. 1353 authentication management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1381","type":"specification","body":"IETF","designation":"RFC 1381","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1381.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1381.txt","https://www.rfc-editor.org/rfc/rfc1381.pdf"],"folder":"IETF/RFC-1381","files":{"txt":{"path":"standards/IETF/RFC-1381/RFC-1381.txt","sha256":"cca319454c3f6aa647a79d801221ff1ac6c8ea300c9db82559346df7cea869df"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Link Layer of\n X.25, LAPB. The objects defined here, along with the objects in the\n \"SNMP MIB Extension for the Packet Layer of X.25\" [9] and the\n \"Definitions of Managed Objects for RS-232-like Hardware Devices\"\n [8], combine to allow management of an X.25 protocol stack.","scope_keywords":["1381","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1381 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Link Layer of\n X.25, LAPB. The objects defined here, along with the objects in the\n \"SNMP MIB Extension for the Packet Layer of X.25\" [9] and the\n \"Definitions of Managed Objects for RS-232-like Hardware Devices\"\n [8], combine to allow management of an X.25 protocol stack. 1381 management nested-reference unchanged"},{"id":"IETF RFC 1382","type":"specification","body":"IETF","designation":"RFC 1382","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1382.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1382.txt","https://www.rfc-editor.org/rfc/rfc1382.pdf"],"folder":"IETF/RFC-1382","files":{"txt":{"path":"standards/IETF/RFC-1382/RFC-1382.txt","sha256":"30bf749d88b6e204eb7ab4605c7dd82e22b786bb5e1d01622bbbf2eb262e92de"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Packet Layer of\n X.25. The objects defined here, along with the objects in the \"SNMP\n MIB Extension for LAPB\" [9] and the \"Definitions of Managed Objects\n for RS-232-like Hardware Devices\" [8], combine to allow management of\n an X.25 protocol stack.","scope_keywords":["1382","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1742","folder":"IETF/RFC-1742","source":"IETF/RFC-1742/RFC-1742.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1382 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Packet Layer of\n X.25. The objects defined here, along with the objects in the \"SNMP\n MIB Extension for LAPB\" [9] and the \"Definitions of Managed Objects\n for RS-232-like Hardware Devices\" [8], combine to allow management of\n an X.25 protocol stack. 1382 management nested-reference unchanged"},{"id":"IETF RFC 1406","type":"specification","body":"IETF","designation":"RFC 1406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1406.txt","https://www.rfc-editor.org/rfc/rfc1406.pdf"],"folder":"IETF/RFC-1406","files":{"txt":{"path":"standards/IETF/RFC-1406/RFC-1406.txt","sha256":"bd807ce842d2a406f2eff9c4d3752d2df47240390af40933037203aa3412ddae"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing DS1 Interfaces --\n including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.\n\n This document entirely replaces RFC 1232, which contains a\n fundamental error: many objects are encoded as Counters that must be\n encoded as INTEGERs or Gauges. The magnitude of the change required\n is sufficient that virtually every object changed. Therefore, the\n MIB documented in RFC 1232 should not be implemented.","scope_keywords":["1406","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"IETF RFC 1406 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing DS1 Interfaces --\n including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links.\n\n This document entirely replaces RFC 1232, which contains a\n fundamental error: many objects are encoded as Counters that must be\n encoded as INTEGERs or Gauges. The magnitude of the change required\n is sufficient that virtually every object changed. Therefore, the\n MIB documented in RFC 1232 should not be implemented. 1406 management subject nested-reference unchanged"},{"id":"IETF RFC 1414","type":"specification","body":"IETF","designation":"RFC 1414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1414.txt","https://www.rfc-editor.org/rfc/rfc1414.pdf"],"folder":"IETF/RFC-1414","files":{"txt":{"path":"standards/IETF/RFC-1414/RFC-1414.txt","sha256":"078ff42a5e5cfb133acb4af8330d20226d7504d2da4793b6c922c90b565c4b69"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIB for use with identifying the users associated\n with TCP connections. It provides functionality approximately\n equivalent to that provided by the protocol defined in RFC 1413 [1].\n This document is a product of the TCP Client Identity Protocol\n Working Group of the Internet Engineering Task Force (IETF).","scope_keywords":["1414","authorization","identification","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1414 This memo defines a MIB for use with identifying the users associated\n with TCP connections. It provides functionality approximately\n equivalent to that provided by the protocol defined in RFC 1413 [1].\n This document is a product of the TCP Client Identity Protocol\n Working Group of the Internet Engineering Task Force (IETF). 1414 authorization identification management policy nested-reference unchanged"},{"id":"IETF RFC 1418","type":"specification","body":"IETF","designation":"RFC 1418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1418.txt","https://www.rfc-editor.org/rfc/rfc1418.pdf"],"folder":"IETF/RFC-1418","files":{"txt":{"path":"standards/IETF/RFC-1418/RFC-1418.txt","sha256":"e27fee4e5348eefcd9b7f60cc1ebd3eb8e5d87d2d55e72a983d58a85b3064520"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1418 Dover Beach Consulting, Inc.\nObsoletes: 1161, 1283 March 1993\n\n SNMP over OSI\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Background ................................................. 1\n 2. Mapping onto the CLTS ...................................... 2\n 2.1 Well-known Addresses ...................................... 2\n 2.2 Traps ..................................................... 2\n 2.3 Maximum Message Size ...................................... 3\n 3. Acknowledgements ........................................... 3\n 4.","scope_keywords":["1418","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1418 Network Working Group M. Rose\nRequest for Comments: 1418 Dover Beach Consulting, Inc.\nObsoletes: 1161, 1283 March 1993\n\n SNMP over OSI\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Background ................................................. 1\n 2. Mapping onto the CLTS ...................................... 2\n 2.1 Well-known Addresses ...................................... 2\n 2.2 Traps ..................................................... 2\n 2.3 Maximum Message Size ...................................... 3\n 3. Acknowledgements ........................................... 3\n 4. 1418 identification management nested-reference unchanged"},{"id":"IETF RFC 1420","type":"specification","body":"IETF","designation":"RFC 1420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1420.txt","https://www.rfc-editor.org/rfc/rfc1420.pdf"],"folder":"IETF/RFC-1420","files":{"txt":{"path":"standards/IETF/RFC-1420/RFC-1420.txt","sha256":"db0681875e182899d07819caa12303b6b9371108925c0253f5224e4c2259cbff"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a convention for encapsulating Simple Network\n Management Protocol (SNMP) [1] packets over the transport mechanism\n provided via the Internetwork Packet Exchange (IPX) protocol [2].\n\n1. Introduction\n\n The Simple Network Management Protocol (SNMP) as defined in [1] is\n now used as an integral part of the network management framework for\n TCP/IP-based internets. Together with its companion standards, which\n define the Structure of Management Information (SMI) [3,4], and the\n Management Information Base (MIB) [5], the SNMP has received\n widespread deployment in many operational networks running the\n Internet suite of protocols.\n\n The success of SNMP in the TCP/IP environment has led to its\n deployment in non TCP/IP-based internets. This specification\n describes the mapping of SNMP onto the Internetwork Packet Exchange\n (IPX) protocol [2] used in Novell NetWare environm","scope_keywords":["1420","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1419","folder":"IETF/RFC-1419","source":"IETF/RFC-1419/RFC-1419.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1420 This document defines a convention for encapsulating Simple Network\n Management Protocol (SNMP) [1] packets over the transport mechanism\n provided via the Internetwork Packet Exchange (IPX) protocol [2].\n\n1. Introduction\n\n The Simple Network Management Protocol (SNMP) as defined in [1] is\n now used as an integral part of the network management framework for\n TCP/IP-based internets. Together with its companion standards, which\n define the Structure of Management Information (SMI) [3,4], and the\n Management Information Base (MIB) [5], the SNMP has received\n widespread deployment in many operational networks running the\n Internet suite of protocols.\n\n The success of SNMP in the TCP/IP environment has led to its\n deployment in non TCP/IP-based internets. This specification\n describes the mapping of SNMP onto the Internetwork Packet Exchange\n (IPX) protocol [2] used in Novell NetWare environm 1420 identification management nested-reference unchanged"},{"id":"IETF RFC 1441","type":"specification","body":"IETF","designation":"RFC 1441","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1441.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1441.txt","https://www.rfc-editor.org/rfc/rfc1441.pdf"],"folder":"IETF/RFC-1441","files":{"txt":{"path":"standards/IETF/RFC-1441/RFC-1441.txt","sha256":"b08157f65362354cd3bf1cc672dde943e8250a4ad71f935d34fcb7ebce155b4e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1441 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Introduction to version 2 of the\n Internet-standard Network Management Framework\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Components of the SNMPv2 Framework .................... 3\n 2.1 Structure of Management Information ................. 3\n 2.2 Textual Conventions ................................. 4\n 2.3","scope_keywords":["1441","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2206","folder":"IETF/RFC-2206","source":"IETF/RFC-2206/RFC-2206.txt","version":null},{"body":"IETF","designation":"RFC 2213","folder":"IETF/RFC-2213","source":"IETF/RFC-2213/RFC-2213.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1441 Network Working Group J. Case\n Request for Comments: 1441 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Introduction to version 2 of the\n Internet-standard Network Management Framework\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Components of the SNMPv2 Framework .................... 3\n 2.1 Structure of Management Information ................. 3\n 2.2 Textual Conventions ................................. 4\n 2.3 1441 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1444","type":"specification","body":"IETF","designation":"RFC 1444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1444.txt","https://www.rfc-editor.org/rfc/rfc1444.pdf"],"folder":"IETF/RFC-1444","files":{"txt":{"path":"standards/IETF/RFC-1444/RFC-1444.txt","sha256":"cfae47bcb36d44bd425a39bc31c666c6678c4e5bf90e128465c83b180b832c4d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1444 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Conformance Statements\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 The OBJECT-GROUP macro ............................","scope_keywords":["1444","authentication","authorization","management","policies","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null}],"search_text":"IETF RFC 1444 Network Working Group J. Case\n Request for Comments: 1444 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Conformance Statements\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 The OBJECT-GROUP macro ............................ 1444 authentication authorization management policies tsp nested-reference unchanged"},{"id":"IETF RFC 1452","type":"specification","body":"IETF","designation":"RFC 1452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1452.txt","https://www.rfc-editor.org/rfc/rfc1452.pdf"],"folder":"IETF/RFC-1452","files":{"txt":{"path":"standards/IETF/RFC-1452/RFC-1452.txt","sha256":"68b76a3da4c09a431d412c7889f3918dcb01e593839281552f1dcb2bb5fc45ff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1452 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Coexistence between version 1 and version 2 of the\n Internet-standard Network Management Framework\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Management Information ................................ 3\n 2.1 Object Definitions .................................. 3\n 2.2 Trap Definitions .........................","scope_keywords":["1452","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null},{"body":"IETF","designation":"RFC 1592","folder":"IETF/RFC-1592","source":"IETF/RFC-1592/RFC-1592.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1452 Network Working Group J. Case\n Request for Comments: 1452 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Coexistence between version 1 and version 2 of the\n Internet-standard Network Management Framework\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Management Information ................................ 3\n 2.1 Object Definitions .................................. 3\n 2.2 Trap Definitions ......................... 1452 identification management nested-reference unchanged"},{"id":"IETF RFC 1461","type":"specification","body":"IETF","designation":"RFC 1461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1461.txt","https://www.rfc-editor.org/rfc/rfc1461.pdf"],"folder":"IETF/RFC-1461","files":{"txt":{"path":"standards/IETF/RFC-1461/RFC-1461.txt","sha256":"2bf6eb45958f946d2f4a3bd41e4718fe318ff90894d8c2c63ba5e4f652feba96"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Multiprotocol\n Interconnect (including IP) traffic carried over X.25. The objects\n defined here, along with the objects in the \"SNMP MIB extension for\n the Packet Layer of X.25\"[8], \"SNMP MIB extension for LAPB\"[7], and\n the \"Definitions of Managed Objects for RS-232-like Hardware Devices\"\n [6], combine to allow management of the traffic over an X.25 protocol\n stack.","scope_keywords":["1461","algorithm","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1461 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Multiprotocol\n Interconnect (including IP) traffic carried over X.25. The objects\n defined here, along with the objects in the \"SNMP MIB extension for\n the Packet Layer of X.25\"[8], \"SNMP MIB extension for LAPB\"[7], and\n the \"Definitions of Managed Objects for RS-232-like Hardware Devices\"\n [6], combine to allow management of the traffic over an X.25 protocol\n stack. 1461 algorithm identification management nested-reference unchanged"},{"id":"IETF RFC 1471","type":"specification","body":"IETF","designation":"RFC 1471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1471.txt","https://www.rfc-editor.org/rfc/rfc1471.pdf"],"folder":"IETF/RFC-1471","files":{"txt":{"path":"standards/IETF/RFC-1471/RFC-1471.txt","sha256":"826ab1e1f35d66357aa7fec8195da8158f2aef4dcede91c02c39a27386cf4ad4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n Link Control Protocol and Link Quality Monitoring on subnetwork\n interfaces that use the family of Point-to-Point Protocols [8, 9, 10,\n 11, & 12].","scope_keywords":["1471","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null}],"search_text":"IETF RFC 1471 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n Link Control Protocol and Link Quality Monitoring on subnetwork\n interfaces that use the family of Point-to-Point Protocols [8, 9, 10,\n 11, & 12]. 1471 authentication management nested-reference unchanged"},{"id":"IETF RFC 1472","type":"specification","body":"IETF","designation":"RFC 1472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1472.txt","https://www.rfc-editor.org/rfc/rfc1472.pdf"],"folder":"IETF/RFC-1472","files":{"txt":{"path":"standards/IETF/RFC-1472/RFC-1472.txt","sha256":"6022c70e3a4695afe5c37c1826bd5c5ad0e4fe47657809bdd94e6be73c3028e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n Security Protocols on subnetwork interfaces using the family of\n Point-to-Point Protocols [8, 9, 10, 11, & 12].","scope_keywords":["1472","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1472 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the\n Security Protocols on subnetwork interfaces using the family of\n Point-to-Point Protocols [8, 9, 10, 11, & 12]. 1472 authentication management nested-reference unchanged"},{"id":"IETF RFC 1473","type":"specification","body":"IETF","designation":"RFC 1473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1473.txt","https://www.rfc-editor.org/rfc/rfc1473.pdf"],"folder":"IETF/RFC-1473","files":{"txt":{"path":"standards/IETF/RFC-1473/RFC-1473.txt","sha256":"470d05e3f45f80654d805cc5b4e5121db12b9c2c9a3bb1cf3749df376ef98230"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the IP\n Network Control Protocol on subnetwork interfaces using the family of\n Point-to-Point Protocols [8, 9, 10, 11, & 12].","scope_keywords":["1473","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null}],"search_text":"IETF RFC 1473 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it describes managed objects used for managing the IP\n Network Control Protocol on subnetwork interfaces using the family of\n Point-to-Point Protocols [8, 9, 10, 11, & 12]. 1473 authentication management nested-reference unchanged"},{"id":"IETF RFC 1514","type":"specification","body":"IETF","designation":"RFC 1514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1514.txt","https://www.rfc-editor.org/rfc/rfc1514.pdf"],"folder":"IETF/RFC-1514","files":{"txt":{"path":"standards/IETF/RFC-1514/RFC-1514.txt","sha256":"aac610679bb541a253a727ccb6418574f2cca694c542e4d42f16d5e4ddd737a2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIB for use with managing host systems. The term\n \"host\" is construed to mean any computer that communicates with other\n similar computers attached to the internet and that is directly used\n by one or more human beings. Although this MIB does not necessarily\n apply to devices whose primary function is communications services\n (e.g., terminal servers, routers, bridges, monitoring equipment),\n such relevance is not explicitly precluded. This MIB instruments\n attributes common to all internet hosts including, for example, both\n personal computers and systems that run variants of Unix.","scope_keywords":["1514","attribute","attributes","authorization","management","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2039","folder":"IETF/RFC-2039","source":"IETF/RFC-2039/RFC-2039.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null}],"search_text":"IETF RFC 1514 This memo defines a MIB for use with managing host systems. The term\n \"host\" is construed to mean any computer that communicates with other\n similar computers attached to the internet and that is directly used\n by one or more human beings. Although this MIB does not necessarily\n apply to devices whose primary function is communications services\n (e.g., terminal servers, routers, bridges, monitoring equipment),\n such relevance is not explicitly precluded. This MIB instruments\n attributes common to all internet hosts including, for example, both\n personal computers and systems that run variants of Unix. 1514 attribute attributes authorization management policy registered nested-reference unchanged"},{"id":"IETF RFC 1592","type":"specification","body":"IETF","designation":"RFC 1592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1592.txt","https://www.rfc-editor.org/rfc/rfc1592.pdf"],"folder":"IETF/RFC-1592","files":{"txt":{"path":"standards/IETF/RFC-1592/RFC-1592.txt","sha256":"65e3a41b7ef7cefdd7abc640c94270036088a3fe3437ab47b29bad00349b1b7a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Wijnen\nRequest for Comments: 1592 G. Carpenter\nObsoletes: 1228 T.J. Watson Research Center, IBM Corp.\nCategory: Experimental K. Curran\n A. Sehgal\n G. Waters\n Bell Northern Research, Ltd.\n March 1994\n\n Simple Network Management Protocol\n Distributed Protocol Interface\n Version 2.0\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . 3\n 1.2 Summary of Changes . . . . . . . . . . . . . . . . . . . . 4\n 2. THEORY OF OPERATION . . . . . . . . . . . . . . . . . . . . . 5\n 2.1 Connection Establishment and Termination . . . ","scope_keywords":["1592","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1592 Network Working Group B. Wijnen\nRequest for Comments: 1592 G. Carpenter\nObsoletes: 1228 T.J. Watson Research Center, IBM Corp.\nCategory: Experimental K. Curran\n A. Sehgal\n G. Waters\n Bell Northern Research, Ltd.\n March 1994\n\n Simple Network Management Protocol\n Distributed Protocol Interface\n Version 2.0\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . 3\n 1.2 Summary of Changes . . . . . . . . . . . . . . . . . . . . 4\n 2. THEORY OF OPERATION . . . . . . . . . . . . . . . . . . . . . 5\n 2.1 Connection Establishment and Termination . . .  1592 management presentation nested-reference unchanged"},{"id":"IETF RFC 1608","type":"specification","body":"IETF","designation":"RFC 1608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1608.txt","https://www.rfc-editor.org/rfc/rfc1608.pdf"],"folder":"IETF/RFC-1608","files":{"txt":{"path":"standards/IETF/RFC-1608/RFC-1608.txt","sha256":"0a6f27b9dc752d0859d56320fc90166a0e994b478f17a18a6c35d44fbf1bd293"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the objects necessary to include information\n about IP networks and IP numbers in the X.500 Directory. It extends\n the work \"Charting networks in the X.500 Directory\" [1] where a\n general framework is presented for representing networks in the\n Directory by applying it to IP networks. This application of the\n Directory is intended to support the work of IP network assigning\n authorities, NICs, as well as other applications looking for a\n mapping of IP numbers to data of related networks. Furthermore,\n Autonomous Systems and related routing policy information can be\n represented in the Directory along with their relationship to\n networks and organizations.\n\nJohannsen, Mansfield, Kosters & Sataluri [Page 1]\n\f\nRFC 1608 IP Information in the X.500 Directory March 1994","scope_keywords":["1608","attribute","attributes","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1608 This document describes the objects necessary to include information\n about IP networks and IP numbers in the X.500 Directory. It extends\n the work \"Charting networks in the X.500 Directory\" [1] where a\n general framework is presented for representing networks in the\n Directory by applying it to IP networks. This application of the\n Directory is intended to support the work of IP network assigning\n authorities, NICs, as well as other applications looking for a\n mapping of IP numbers to data of related networks. Furthermore,\n Autonomous Systems and related routing policy information can be\n represented in the Directory along with their relationship to\n networks and organizations.\n\nJohannsen, Mansfield, Kosters & Sataluri [Page 1]\n\f\nRFC 1608 IP Information in the X.500 Directory March 1994 1608 attribute attributes policies policy nested-reference unchanged"},{"id":"IETF RFC 1901","type":"specification","body":"IETF","designation":"RFC 1901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1901.txt","https://www.rfc-editor.org/rfc/rfc1901.pdf"],"folder":"IETF/RFC-1901","files":{"txt":{"path":"standards/IETF/RFC-1901/RFC-1901.txt","sha256":"99a2f06b0e96780d8ad8e00e407d7ebb7ac08974ccd176363dc6b995c0f50162"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1901 J. Case\nCategory: Experimental SNMP Research, Inc.\n K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Introduction to Community-based SNMPv2\n\nStatus of this Memo\n\n This document specifies an Experimental protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. Components of the SNMPv2 Framework .......................... 2\n 2.1 Structure of Management Information ........................ 2\n 2.2 Textual Conventions ........................................ 3\n 2.3 Conformance Statements ....................","scope_keywords":["1901","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 1901 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1901 J. Case\nCategory: Experimental SNMP Research, Inc.\n K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Introduction to Community-based SNMPv2\n\nStatus of this Memo\n\n This document specifies an Experimental protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. Components of the SNMPv2 Framework .......................... 2\n 2.1 Structure of Management Information ........................ 2\n 2.2 Textual Conventions ........................................ 3\n 2.3 Conformance Statements .................... 1901 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1904","type":"specification","body":"IETF","designation":"RFC 1904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1904.txt","https://www.rfc-editor.org/rfc/rfc1904.pdf"],"folder":"IETF/RFC-1904","files":{"txt":{"path":"standards/IETF/RFC-1904/RFC-1904.txt","sha256":"2a75a318c8e915b91e7d85d28218e46d41c1d1320ec1b2a9b08791acc841aaf1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1904 J. Case\nObsoletes: 1444 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Conformance Statements for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 3\n 2. Definitions","scope_keywords":["1904","authentication","authorization","management","policies","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null}],"search_text":"IETF RFC 1904 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1904 J. Case\nObsoletes: 1444 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Conformance Statements for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 3\n 2. Definitions 1904 authentication authorization management policies tsp nested-reference unchanged"},{"id":"IETF RFC 1908","type":"specification","body":"IETF","designation":"RFC 1908","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1908.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1908.txt","https://www.rfc-editor.org/rfc/rfc1908.pdf"],"folder":"IETF/RFC-1908","files":{"txt":{"path":"standards/IETF/RFC-1908/RFC-1908.txt","sha256":"a1fabc9b3a1a57c3535039b607c9cda01064da93bf49f3796172b1bcfd1e70b2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1908 J. Case\nObsoletes: 1452 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Coexistence between Version 1 and Version 2 of the\n Internet-standard Network Management Framework\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. Management Information ...................................... 2\n 2.1 ","scope_keywords":["1908","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1906","folder":"IETF/RFC-1906","source":"IETF/RFC-1906/RFC-1906.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null}],"search_text":"IETF RFC 1908 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1908 J. Case\nObsoletes: 1452 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Coexistence between Version 1 and Version 2 of the\n Internet-standard Network Management Framework\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. Management Information ...................................... 2\n 2.1  1908 management nested-reference unchanged"},{"id":"IETF RFC 1909","type":"specification","body":"IETF","designation":"RFC 1909","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1909.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1909.txt","https://www.rfc-editor.org/rfc/rfc1909.pdf"],"folder":"IETF/RFC-1909","files":{"txt":{"path":"standards/IETF/RFC-1909/RFC-1909.txt","sha256":"59ead76c3d7438cce6215ea58ae9e250963e1765c928b0fb681c7b0ed22f6036"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie, Editor\nRequest for Comments: 1909 Cisco Systems, Inc.\nCategory: Experimental February 1996\n\n An Administrative Infrastructure for SNMPv2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. Overview .................................................... 2\n 2.1 Contexts ................................................... 3\n 2.2 Authorization: Access Rights and MIB Views ................. 3\n 2.3 Authentication and Privacy ................................. 4\n 2.4 Access Control ............................................. 5\n 2.5 Security Models .....................","scope_keywords":["1909","authentication","authorization","identification","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null}],"search_text":"IETF RFC 1909 Network Working Group K. McCloghrie, Editor\nRequest for Comments: 1909 Cisco Systems, Inc.\nCategory: Experimental February 1996\n\n An Administrative Infrastructure for SNMPv2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. Overview .................................................... 2\n 2.1 Contexts ................................................... 3\n 2.2 Authorization: Access Rights and MIB Views ................. 3\n 2.3 Authentication and Privacy ................................. 4\n 2.4 Access Control ............................................. 5\n 2.5 Security Models ..................... 1909 authentication authorization identification management policies policy nested-reference unchanged"},{"id":"IETF RFC 2261","type":"specification","body":"IETF","designation":"RFC 2261","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2261.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2261.txt","https://www.rfc-editor.org/rfc/rfc2261.pdf"],"folder":"IETF/RFC-2261","files":{"txt":{"path":"standards/IETF/RFC-2261/RFC-2261.txt","sha256":"3da6f44c9be57f729924190432c6a42082af586c443e20c123f21e4ebf83bf7a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data.","scope_keywords":["2261","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null}],"search_text":"IETF RFC 2261 This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data. 2261 management nested-reference unchanged"},{"id":"IETF RFC 2271","type":"specification","body":"IETF","designation":"RFC 2271","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2271.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2271.txt","https://www.rfc-editor.org/rfc/rfc2271.pdf"],"folder":"IETF/RFC-2271","files":{"txt":{"path":"standards/IETF/RFC-2271/RFC-2271.txt","sha256":"4b2283366a32928a824e1a8ed712505ec5cb608bf13ba2ade8ec9c3f211d5076"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data.","scope_keywords":["2271","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null}],"search_text":"IETF RFC 2271 This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data. 2271 management nested-reference unchanged"},{"id":"IETF RFC 2494","type":"specification","body":"IETF","designation":"RFC 2494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2494.txt","https://www.rfc-editor.org/rfc/rfc2494.pdf"],"folder":"IETF/RFC-2494","files":{"txt":{"path":"standards/IETF/RFC-2494/RFC-2494.txt","sha256":"da750804421d0ebccaf3740084b127005e17020a5f9f5922692b8100bc3b7719"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS0 and DS0\n Bundle interfaces. This document is a companion document with\n Definitions of Managed Objects for the DS1/E1/DS2/E2 (RFC 2495 [17]),\n DS3/E3 (RFC 2496 [18]), and the work in progress, SONET/SDH Interface\n Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.","scope_keywords":["2494","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2494 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS0 and DS0\n Bundle interfaces. This document is a companion document with\n Definitions of Managed Objects for the DS1/E1/DS2/E2 (RFC 2495 [17]),\n DS3/E3 (RFC 2496 [18]), and the work in progress, SONET/SDH Interface\n Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions. 2494 management nested-reference unchanged"},{"id":"IETF RFC 2495","type":"specification","body":"IETF","designation":"RFC 2495","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2495.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2495.txt","https://www.rfc-editor.org/rfc/rfc2495.pdf"],"folder":"IETF/RFC-2495","files":{"txt":{"path":"standards/IETF/RFC-2495/RFC-2495.txt","sha256":"c8265b9f6f178c286b9e8cfbc47e2cece04c7557a5cac5baab9a8b96c5b4853a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, E1, DS2\n and E2 interfaces. This document is a companion document with\n Definitions of Managed Objects for the DS0 (RFC 2494 [30]), DS3/E3\n (RFC 2496 [28]), and the work in progress, SONET/SDH Interface Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.","scope_keywords":["2495","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2493","folder":"IETF/RFC-2493","source":"IETF/RFC-2493/RFC-2493.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"IETF RFC 2495 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, E1, DS2\n and E2 interfaces. This document is a companion document with\n Definitions of Managed Objects for the DS0 (RFC 2494 [30]), DS3/E3\n (RFC 2496 [28]), and the work in progress, SONET/SDH Interface Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions. 2495 management nested-reference unchanged"},{"id":"IETF RFC 2496","type":"specification","body":"IETF","designation":"RFC 2496","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2496.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2496.txt","https://www.rfc-editor.org/rfc/rfc2496.pdf"],"folder":"IETF/RFC-2496","files":{"txt":{"path":"standards/IETF/RFC-2496/RFC-2496.txt","sha256":"da0ef4db72c65af90cc18ebb9703fea80c7e5c1c799f37123e0f62f15e9f9488"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS3 and E3\n interfaces. This document is a companion document with Definitions\n of Managed Objects for the DS0 (RFC 2494 [25]), DS1/E1/DS2/E2 (RFC\n 2495 [17]), and the work in progress SONET/SDH Interface Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.","scope_keywords":["2496","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2493","folder":"IETF/RFC-2493","source":"IETF/RFC-2493/RFC-2493.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null}],"search_text":"IETF RFC 2496 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS3 and E3\n interfaces. This document is a companion document with Definitions\n of Managed Objects for the DS0 (RFC 2494 [25]), DS1/E1/DS2/E2 (RFC\n 2495 [17]), and the work in progress SONET/SDH Interface Types.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions. 2496 management nested-reference unchanged"},{"id":"IETF RFC 2512","type":"specification","body":"IETF","designation":"RFC 2512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2512.txt","https://www.rfc-editor.org/rfc/rfc2512.pdf"],"folder":"IETF/RFC-2512","files":{"txt":{"path":"standards/IETF/RFC-2512/RFC-2512.txt","sha256":"d09cbebeb572a325cf79fe0299d29ab1f250a8f869ca05d2d2ee96cf722991ea"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2512 Cisco Systems, Inc.\nCategory: Standards Track J. Heinanen\n Telia Finland, Inc.\n W. Greene\n MCI Telecommunications Corp.\n A. Prasad\n Cisco Systems, Inc.\n February 1999\n\n Accounting Information for ATM Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ................................................... 1\n 2 The SNMP Network Management Framework .......................... 2\n 3 Overview .........","scope_keywords":["2512","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2512 Network Working Group K. McCloghrie\nRequest for Comments: 2512 Cisco Systems, Inc.\nCategory: Standards Track J. Heinanen\n Telia Finland, Inc.\n W. Greene\n MCI Telecommunications Corp.\n A. Prasad\n Cisco Systems, Inc.\n February 1999\n\n Accounting Information for ATM Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ................................................... 1\n 2 The SNMP Network Management Framework .......................... 2\n 3 Overview ......... 2512 management nested-reference unchanged"},{"id":"IETF RFC 2513","type":"specification","body":"IETF","designation":"RFC 2513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2513.txt","https://www.rfc-editor.org/rfc/rfc2513.pdf"],"folder":"IETF/RFC-2513","files":{"txt":{"path":"standards/IETF/RFC-2513/RFC-2513.txt","sha256":"b01397150e2253f1214c4cf6b327c053ee9dedbe1dd29a8a206bb0e6adc806e3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2513 Cisco Systems, Inc.\nCategory: Standards Track J. Heinanen\n Telia Finland, Inc.\n W. Greene\n MCI Telecommunications Corp.\n A. Prasad\n Cisco Systems, Inc.\n February 1999\n\n Managed Objects for Controlling the Collection\n and Storage of Accounting Information for\n Connection-Oriented Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .................................................... 2\n 2 The SNM","scope_keywords":["2513","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2513 Network Working Group K. McCloghrie\nRequest for Comments: 2513 Cisco Systems, Inc.\nCategory: Standards Track J. Heinanen\n Telia Finland, Inc.\n W. Greene\n MCI Telecommunications Corp.\n A. Prasad\n Cisco Systems, Inc.\n February 1999\n\n Managed Objects for Controlling the Collection\n and Storage of Accounting Information for\n Connection-Oriented Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .................................................... 2\n 2 The SNM 2513 management nested-reference unchanged"},{"id":"IETF RFC 2515","type":"specification","body":"IETF","designation":"RFC 2515","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2515.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2515.txt","https://www.rfc-editor.org/rfc/rfc2515.pdf"],"folder":"IETF/RFC-2515","files":{"txt":{"path":"standards/IETF/RFC-2515/RFC-2515.txt","sha256":"bab9c42780fca2a29c725ca5764541ea9b7200e46a28c427b1364796591cf1af"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing ATM-based\n interfaces, devices, networks and services.\n\n This memo replaces RFC 1695 [24]. Changes relative to RFC 1695 are\n summarized in the MIB module's REVISION clause.\n\n Textual Conventions used in this MIB are defined in [6] and [19].\n\n2. The SNMP Network Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n 0 An overall architecture, described in RFC 2271 [1].\n\n 0 Mechanisms for describing and naming objects and events\n for the purpose of management. The first version of this\n Structure of Management Information (SMI) is called SMIv1 and\n described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC\n 1215 [4]. The second version, called SMIv2","scope_keywords":["2515","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2514","folder":"IETF/RFC-2514","source":"IETF/RFC-2514/RFC-2514.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2515 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing ATM-based\n interfaces, devices, networks and services.\n\n This memo replaces RFC 1695 [24]. Changes relative to RFC 1695 are\n summarized in the MIB module's REVISION clause.\n\n Textual Conventions used in this MIB are defined in [6] and [19].\n\n2. The SNMP Network Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n 0 An overall architecture, described in RFC 2271 [1].\n\n 0 Mechanisms for describing and naming objects and events\n for the purpose of management. The first version of this\n Structure of Management Information (SMI) is called SMIv1 and\n described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC\n 1215 [4]. The second version, called SMIv2 2515 management path nested-reference unchanged"},{"id":"IETF RFC 2558","type":"specification","body":"IETF","designation":"RFC 2558","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2558.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2558.txt","https://www.rfc-editor.org/rfc/rfc2558.pdf"],"folder":"IETF/RFC-2558","files":{"txt":{"path":"standards/IETF/RFC-2558/RFC-2558.txt","sha256":"b535c432b753e06d21bf54a89fa52905450b6abd8e58840fc102a804cf273f19"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This\n document is a companion to the documents that define Managed Objects\n for the DS1/E1/DS2/E2 and DS3/E3 Interface Types [24][25].\n\n Textual Conventions used in this MIB are defined in [6] and [36].\n\n This memo replaces RFC 1595 [30]. Changes relative to RFC 1595 are\n summarized in the MIB module's REVISION clause.","scope_keywords":["2558","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null}],"search_text":"IETF RFC 2558 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This\n document is a companion to the documents that define Managed Objects\n for the DS1/E1/DS2/E2 and DS3/E3 Interface Types [24][25].\n\n Textual Conventions used in this MIB are defined in [6] and [36].\n\n This memo replaces RFC 1595 [30]. Changes relative to RFC 1595 are\n summarized in the MIB module's REVISION clause. 2558 management path nested-reference unchanged"},{"id":"IETF RFC 2564","type":"specification","body":"IETF","designation":"RFC 2564","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2564.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2564.txt","https://www.rfc-editor.org/rfc/rfc2564.pdf"],"folder":"IETF/RFC-2564","files":{"txt":{"path":"standards/IETF/RFC-2564/RFC-2564.txt","sha256":"c740891b345c798b8d898fcf514115c395b0057ae4d77d3afc7f4df82b280c43"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a standards track portion of the Management\n Information Base (MIB) for use with network management protocols in\n the Internet Community. In particular, it defines objects used for\n the management of applications. This MIB complements the System\n Application MIB, providing for the management of applications' common\n attributes which could not typically be observed without the\n cooperation of the software being managed.","scope_keywords":["2564","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null}],"search_text":"IETF RFC 2564 This memo defines a standards track portion of the Management\n Information Base (MIB) for use with network management protocols in\n the Internet Community. In particular, it defines objects used for\n the management of applications. This MIB complements the System\n Application MIB, providing for the management of applications' common\n attributes which could not typically be observed without the\n cooperation of the software being managed. 2564 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 2571","type":"specification","body":"IETF","designation":"RFC 2571","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2571.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2571.txt","https://www.rfc-editor.org/rfc/rfc2571.pdf"],"folder":"IETF/RFC-2571","files":{"txt":{"path":"standards/IETF/RFC-2571/RFC-2571.txt","sha256":"140c9e5a091312577fee686d284a063f117c97b21dc1a2024bd1ae7ba98dc917"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data.","scope_keywords":["2571","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null}],"search_text":"IETF RFC 2571 This document describes an architecture for describing SNMP\n Management Frameworks. The architecture is designed to be modular to\n allow the evolution of the SNMP protocol standards over time. The\n major portions of the architecture are an SNMP engine containing a\n Message Processing Subsystem, a Security Subsystem and an Access\n Control Subsystem, and possibly multiple SNMP applications which\n provide specific functional processing of management data. 2571 management nested-reference unchanged"},{"id":"IETF RFC 2576","type":"specification","body":"IETF","designation":"RFC 2576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2576.txt","https://www.rfc-editor.org/rfc/rfc2576.pdf"],"folder":"IETF/RFC-2576","files":{"txt":{"path":"standards/IETF/RFC-2576/RFC-2576.txt","sha256":"9bb3cd15d231355b6d535cdcff90670133b1f312080b85f84f16e571dcd42eae"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to describe coexistence between\n version 3 of the Internet-standard Network Management Framework,\n (SNMPv3), version 2 of the Internet-standard Network Management\n Framework (SNMPv2), and the original Internet-standard Network\n Management Framework (SNMPv1). This document obsoletes RFC 1908 [13]\n and RFC2089 [14].","scope_keywords":["2576","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null}],"search_text":"IETF RFC 2576 The purpose of this document is to describe coexistence between\n version 3 of the Internet-standard Network Management Framework,\n (SNMPv3), version 2 of the Internet-standard Network Management\n Framework (SNMPv2), and the original Internet-standard Network\n Management Framework (SNMPv1). This document obsoletes RFC 1908 [13]\n and RFC2089 [14]. 2576 key management nested-reference unchanged"},{"id":"IETF RFC 2580","type":"specification","body":"IETF","designation":"RFC 2580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2580.txt","https://www.rfc-editor.org/rfc/rfc2580.pdf"],"folder":"IETF/RFC-2580","files":{"txt":{"path":"standards/IETF/RFC-2580/RFC-2580.txt","sha256":"b5ca6c4466c80125a39d7a5f6274cb7711cd7cffc0b4bf015386ca299f0061d1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Editors of this version:\nRequest for Comments: 2580 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1904 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Conformance Statements for SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction","scope_keywords":["2580","management","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3595","folder":"IETF/RFC-3595","source":"IETF/RFC-3595/RFC-3595.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null}],"search_text":"IETF RFC 2580 Network Working Group Editors of this version:\nRequest for Comments: 2580 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1904 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Conformance Statements for SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction 2580 management tsp nested-reference unchanged"},{"id":"IETF RFC 2591","type":"specification","body":"IETF","designation":"RFC 2591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2591.txt","https://www.rfc-editor.org/rfc/rfc2591.pdf"],"folder":"IETF/RFC-2591","files":{"txt":{"path":"standards/IETF/RFC-2591/RFC-2591.txt","sha256":"6a6f937a9ede770afc1fed4ee739cfe8ed757ecc8df124903828318213190afc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n schedule management operations periodically or at specified dates and\n times.","scope_keywords":["2591","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null}],"search_text":"IETF RFC 2591 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n schedule management operations periodically or at specified dates and\n times. 2591 key management nested-reference unchanged"},{"id":"IETF RFC 2592","type":"specification","body":"IETF","designation":"RFC 2592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2592.txt","https://www.rfc-editor.org/rfc/rfc2592.pdf"],"folder":"IETF/RFC-2592","files":{"txt":{"path":"standards/IETF/RFC-2592/RFC-2592.txt","sha256":"076765c312441434f68d0692f0d0b376ce41e06a1eb8ea176fb4bad0d143b8b5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow the\n delegation of management scripts to distributed managers.","scope_keywords":["2592","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null}],"search_text":"IETF RFC 2592 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow the\n delegation of management scripts to distributed managers. 2592 key management nested-reference unchanged"},{"id":"IETF RFC 2594","type":"specification","body":"IETF","designation":"RFC 2594","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2594.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2594.txt","https://www.rfc-editor.org/rfc/rfc2594.pdf"],"folder":"IETF/RFC-2594","files":{"txt":{"path":"standards/IETF/RFC-2594/RFC-2594.txt","sha256":"a5792bdfc5a8a550ed9be1c5630329d37ccee224fb63fa4ba5b83c8c96df0b03"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet Community.\n In particular it describes a set of objects for managing World Wide\n Web (WWW) services.","scope_keywords":["2594","http","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null}],"search_text":"IETF RFC 2594 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet Community.\n In particular it describes a set of objects for managing World Wide\n Web (WWW) services. 2594 http key management presentation nested-reference unchanged"},{"id":"IETF RFC 2618","type":"specification","body":"IETF","designation":"RFC 2618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2618.txt","https://www.rfc-editor.org/rfc/rfc2618.pdf"],"folder":"IETF/RFC-2618","files":{"txt":{"path":"standards/IETF/RFC-2618/RFC-2618.txt","sha256":"d9e1a4be20257ff116cbc1158ef97c36859f7f1ea2a9e6ba8f4e4e2e040daad3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions which instrument RADIUS\n authentication client functions. These extensions represent a portion\n of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions IP-based management stations can manage RADIUS\n authentication clients.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n authentication clients.\n\n Today a wide range of network devices, including routers and NASes,\n act as RADIUS authentication clients in order to provide\n authentication and authorization services. As a result, the effective\n management of RADIUS authentication clients is of considerable\n importance.\n\nAboba & Zorn Standards Track ","scope_keywords":["2618","authentication","authorization","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null}],"search_text":"IETF RFC 2618 This memo defines a set of extensions which instrument RADIUS\n authentication client functions. These extensions represent a portion\n of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions IP-based management stations can manage RADIUS\n authentication clients.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n authentication clients.\n\n Today a wide range of network devices, including routers and NASes,\n act as RADIUS authentication clients in order to provide\n authentication and authorization services. As a result, the effective\n management of RADIUS authentication clients is of considerable\n importance.\n\nAboba & Zorn Standards Track  2618 authentication authorization management nested-reference unchanged"},{"id":"IETF RFC 2619","type":"specification","body":"IETF","designation":"RFC 2619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2619.txt","https://www.rfc-editor.org/rfc/rfc2619.pdf"],"folder":"IETF/RFC-2619","files":{"txt":{"path":"standards/IETF/RFC-2619/RFC-2619.txt","sha256":"dda260f017c08a32d4eaf639e1c229503f42fcf9c0fce714cdb68641d23b0b97"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions which instrument RADIUS\n authentication server functions. These extensions represent a portion\n of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions IP-based management stations can manage RADIUS\n authentication servers.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n authentication servers.\n\n RADIUS authentication servers are today widely deployed by dialup\n Internet Service Providers, in order to provide authentication\n services. As a result, the effective management of RADIUS\n authentication servers is of considerable importance.\n\nZorn & Aboba Standards Track [Page 1]\n\f\nRFC 2619 RADIUS Aut","scope_keywords":["2619","authentication","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null}],"search_text":"IETF RFC 2619 This memo defines a set of extensions which instrument RADIUS\n authentication server functions. These extensions represent a portion\n of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions IP-based management stations can manage RADIUS\n authentication servers.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n authentication servers.\n\n RADIUS authentication servers are today widely deployed by dialup\n Internet Service Providers, in order to provide authentication\n services. As a result, the effective management of RADIUS\n authentication servers is of considerable importance.\n\nZorn & Aboba Standards Track [Page 1]\n\f\nRFC 2619 RADIUS Aut 2619 authentication identification management nested-reference unchanged"},{"id":"IETF RFC 2620","type":"specification","body":"IETF","designation":"RFC 2620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2620.txt","https://www.rfc-editor.org/rfc/rfc2620.pdf"],"folder":"IETF/RFC-2620","files":{"txt":{"path":"standards/IETF/RFC-2620/RFC-2620.txt","sha256":"650ec7a51ffd1c11aacecf24f55a3b5b7be07d480b1113ebfbbf9781195c8f92"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions which instrument RADIUS\n accounting client functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions IP-based\n management stations can manage RADIUS accounting clients.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n accounting clients.\n\n Today a wide range of network devices, including routers and NASes,\n act as RADIUS accounting clients in order to provide accounting\n services. As a result, the effective management of RADIUS accounting\n clients is of considerable importance.\n\n2. The SNMP Management Framework\n\n The SNMP Management Framework presentl","scope_keywords":["2620","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null}],"search_text":"IETF RFC 2620 This memo defines a set of extensions which instrument RADIUS\n accounting client functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions IP-based\n management stations can manage RADIUS accounting clients.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n accounting clients.\n\n Today a wide range of network devices, including routers and NASes,\n act as RADIUS accounting clients in order to provide accounting\n services. As a result, the effective management of RADIUS accounting\n clients is of considerable importance.\n\n2. The SNMP Management Framework\n\n The SNMP Management Framework presentl 2620 management nested-reference unchanged"},{"id":"IETF RFC 2621","type":"specification","body":"IETF","designation":"RFC 2621","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2621.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2621.txt","https://www.rfc-editor.org/rfc/rfc2621.pdf"],"folder":"IETF/RFC-2621","files":{"txt":{"path":"standards/IETF/RFC-2621/RFC-2621.txt","sha256":"cc6aea2052e5b9d1b11e2f8c4e6189dc36e2876be0207a911f9f8925859ff726"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions which instrument RADIUS\n accounting server functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions IP-based\n management stations can manage RADIUS accounting servers.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n accounting servers.\n\n RADIUS accounting servers are today widely deployed by dialup\n Internet Service Providers, in order to provide accounting services.\n As a result, the effective management of RADIUS accounting servers is\n of considerable importance.\n\n2. The SNMP Management Framework\n\n The SNMP Management Framework presently consists ","scope_keywords":["2621","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null}],"search_text":"IETF RFC 2621 This memo defines a set of extensions which instrument RADIUS\n accounting server functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions IP-based\n management stations can manage RADIUS accounting servers.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing RADIUS\n accounting servers.\n\n RADIUS accounting servers are today widely deployed by dialup\n Internet Service Providers, in order to provide accounting services.\n As a result, the effective management of RADIUS accounting servers is\n of considerable importance.\n\n2. The SNMP Management Framework\n\n The SNMP Management Framework presently consists  2621 identification management nested-reference unchanged"},{"id":"IETF RFC 2662","type":"specification","body":"IETF","designation":"RFC 2662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2662.txt","https://www.rfc-editor.org/rfc/rfc2662.pdf"],"folder":"IETF/RFC-2662","files":{"txt":{"path":"standards/IETF/RFC-2662/RFC-2662.txt","sha256":"87a1a142fc090a310e090b8d90f6f7e6be1c9651d3cf86424724870a0e898439"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a standard SNMP MIB for ADSL lines based on the\n ADSL Forum standard data model [9]. The ADSL standard describes\n ATU-C and ATU-R as two sides of the ADSL line. This MIB covers both\n ATU-C and ATU-R agent's perspectives. Each instance defined in the\n\n MIB represents a single ADSL line.\n\nBathrick & Ly Standards Track [Page 1]\n\f\nRFC 2662 ADSL Line MIB August 1999\n\n It should be noted that the ADSL Forum Network Management Working\n Group provided input towards the content of this document. See the\n Acknowledgement Section for a list of individuals who made this\n document possible.\n\n2. The SNMP Network Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n o An overall architecture, described in RFC 2571 [13].\n\n o Mechanisms for describing and naming objects and events for the\n purpose of management. The first version of thi","scope_keywords":["2662","attribute","attributes","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"IETF RFC 2662 This document defines a standard SNMP MIB for ADSL lines based on the\n ADSL Forum standard data model [9]. The ADSL standard describes\n ATU-C and ATU-R as two sides of the ADSL line. This MIB covers both\n ATU-C and ATU-R agent's perspectives. Each instance defined in the\n\n MIB represents a single ADSL line.\n\nBathrick & Ly Standards Track [Page 1]\n\f\nRFC 2662 ADSL Line MIB August 1999\n\n It should be noted that the ADSL Forum Network Management Working\n Group provided input towards the content of this document. See the\n Acknowledgement Section for a list of individuals who made this\n document possible.\n\n2. The SNMP Network Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n o An overall architecture, described in RFC 2571 [13].\n\n o Mechanisms for describing and naming objects and events for the\n purpose of management. The first version of thi 2662 attribute attributes management profile profiles nested-reference unchanged"},{"id":"IETF RFC 2667","type":"specification","body":"IETF","designation":"RFC 2667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2667.txt","https://www.rfc-editor.org/rfc/rfc2667.pdf"],"folder":"IETF/RFC-2667","files":{"txt":{"path":"standards/IETF/RFC-2667/RFC-2667.txt","sha256":"783c2ab0e28a0ff5b452a15f3212604d5bf60bae86df98434aa4e00f583f3ad3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) for use with\n network management protocols in the Internet community. In\n particular, it describes managed objects used for managing tunnels of\n any type over IPv4 networks. Extension MIBs may be designed for\n managing protocol-specific objects. Likewise, extension MIBs may be\n designed for managing security-specific objects. This MIB does not\n support tunnels over non-IPv4 networks (including IPv6 networks).\n Management of such tunnels may be supported by other MIBs.","scope_keywords":["2667","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null}],"search_text":"IETF RFC 2667 This memo defines a Management Information Base (MIB) for use with\n network management protocols in the Internet community. In\n particular, it describes managed objects used for managing tunnels of\n any type over IPv4 networks. Extension MIBs may be designed for\n managing protocol-specific objects. Likewise, extension MIBs may be\n designed for managing security-specific objects. This MIB does not\n support tunnels over non-IPv4 networks (including IPv6 networks).\n Management of such tunnels may be supported by other MIBs. 2667 management nested-reference unchanged"},{"id":"IETF RFC 2669","type":"specification","body":"IETF","designation":"RFC 2669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2669.txt","https://www.rfc-editor.org/rfc/rfc2669.pdf"],"folder":"IETF/RFC-2669","files":{"txt":{"path":"standards/IETF/RFC-2669/RFC-2669.txt","sha256":"081c9d4507e11ca470ca9f61a60cc9b459053d7ac6ffc0b17f09b58a479d6e47"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem\n Termination Systems.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This memo is a product of the IPCDN working group within the Internet\n Engineering Task Force. Comments are solicited and should be\n addressed to the working group's mailing list at ipcdn@terayon.com\n and/or the author.","scope_keywords":["2669","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null}],"search_text":"IETF RFC 2669 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem\n Termination Systems.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SNMP SMIv2 [5][6][7]. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This memo is a product of the IPCDN working group within the Internet\n Engineering Task Force. Comments are solicited and should be\n addressed to the working group's mailing list at ipcdn@terayon.com\n and/or the author. 2669 management nested-reference unchanged"},{"id":"IETF RFC 2670","type":"specification","body":"IETF","designation":"RFC 2670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2670.txt","https://www.rfc-editor.org/rfc/rfc2670.pdf"],"folder":"IETF/RFC-2670","files":{"txt":{"path":"standards/IETF/RFC-2670/RFC-2670.txt","sha256":"414559f9a4cf64a6ca88870216d4bb061ff8b252d9e634703e8b37304b2db203"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based management of MCNS/DOCSIS compliant Radio Frequency (RF)\n interfaces.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SNMP SMIv2 [5][6][7]. The set of objects are consistent with the\n SNMP framework and existing SNMP standards.\n\n This memo is a product of the IPCDN working group within the Internet\n Engineering Task Force. Comments are solicited and should be\n addressed to the working group's mailing list at ipcdn@terayon.com\n and/or the author.","scope_keywords":["2670","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null}],"search_text":"IETF RFC 2670 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based management of MCNS/DOCSIS compliant Radio Frequency (RF)\n interfaces.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SNMP SMIv2 [5][6][7]. The set of objects are consistent with the\n SNMP framework and existing SNMP standards.\n\n This memo is a product of the IPCDN working group within the Internet\n Engineering Task Force. Comments are solicited and should be\n addressed to the working group's mailing list at ipcdn@terayon.com\n and/or the author. 2670 management nested-reference unchanged"},{"id":"IETF RFC 2741","type":"specification","body":"IETF","designation":"RFC 2741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2741.txt","https://www.rfc-editor.org/rfc/rfc2741.pdf"],"folder":"IETF/RFC-2741","files":{"txt":{"path":"standards/IETF/RFC-2741/RFC-2741.txt","sha256":"68f17cbfc143fa5a996f93410082d09b174cdaebdecec14456f0fffc7233fcb4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a standardized framework for extensible SNMP\n agents. It defines processing entities called master agents and\n subagents, a protocol (AgentX) used to communicate between them, and\n the elements of procedure by which the extensible agent processes\n SNMP protocol messages. This memo obsoletes RFC 2257.","scope_keywords":["2741","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null}],"search_text":"IETF RFC 2741 This memo defines a standardized framework for extensible SNMP\n agents. It defines processing entities called master agents and\n subagents, a protocol (AgentX) used to communicate between them, and\n the elements of procedure by which the extensible agent processes\n SNMP protocol messages. This memo obsoletes RFC 2257. 2741 management presentation nested-reference unchanged"},{"id":"IETF RFC 2786","type":"specification","body":"IETF","designation":"RFC 2786","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2786.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2786.txt","https://www.rfc-editor.org/rfc/rfc2786.pdf"],"folder":"IETF/RFC-2786","files":{"txt":{"path":"standards/IETF/RFC-2786/RFC-2786.txt","sha256":"166325423de20d104283163add1a3d6a51316b1600fe9fb63cc81e24f1a0c324"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n the Internet community. In particular, it defines a textual\n convention for doing Diffie-Helman key agreement key exchanges and a\n set of objects which extend the usmUserTable to permit the use of a\n DH key exchange in addition to the key change method described in\n [12]. In otherwords, this MIB adds the possibility of forward secrecy\n to the USM model. It also defines a set of objects that can be used\n to kick start security on an SNMPv3 agent when the out of band path\n is authenticated, but not necessarily private or confidential.\n\n The KeyChange textual convention described in [12] permits secure key\n changes, but has the property that if a third-party has knowledge of\n the original key (e.g. if the agent was manufactured with a standard\n default key) and c","scope_keywords":["2786","authentication","key","keys","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null}],"search_text":"IETF RFC 2786 This memo defines an experimental portion of the Management\n Information Base (MIB) for use with network management protocols in\n the Internet community. In particular, it defines a textual\n convention for doing Diffie-Helman key agreement key exchanges and a\n set of objects which extend the usmUserTable to permit the use of a\n DH key exchange in addition to the key change method described in\n [12]. In otherwords, this MIB adds the possibility of forward secrecy\n to the USM model. It also defines a set of objects that can be used\n to kick start security on an SNMPv3 agent when the out of band path\n is authenticated, but not necessarily private or confidential.\n\n The KeyChange textual convention described in [12] permits secure key\n changes, but has the property that if a third-party has knowledge of\n the original key (e.g. if the agent was manufactured with a standard\n default key) and c 2786 authentication key keys management path nested-reference unchanged"},{"id":"IETF RFC 2790","type":"specification","body":"IETF","designation":"RFC 2790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2790.txt","https://www.rfc-editor.org/rfc/rfc2790.pdf"],"folder":"IETF/RFC-2790","files":{"txt":{"path":"standards/IETF/RFC-2790/RFC-2790.txt","sha256":"8243d7412aa30c5c975ca15bb222e265f84ecaf590e5327e7c965375bdbcb747"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1514, the \"Host Resources MIB\". This memo\n extends that specification by clarifying changes based on\n implementation and deployment experience and documenting the Host\n Resources MIB in SMIv2 format while remaining semantically identical\n to the existing SMIv1-based MIB.\n\n This memo defines a MIB for use with managing host systems. The term\n \"host\" is construed to mean any computer that communicates with other\n similar computers attached to the internet and that is directly used\n by one or more human beings. Although this MIB does not necessarily\n apply to devices whose primary function is communications services\n (e.g., terminal servers, routers, bridges, monitoring equipment),\n such relevance is not explicitly precluded. Thi","scope_keywords":["2790","attribute","attributes","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null}],"search_text":"IETF RFC 2790 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1514, the \"Host Resources MIB\". This memo\n extends that specification by clarifying changes based on\n implementation and deployment experience and documenting the Host\n Resources MIB in SMIv2 format while remaining semantically identical\n to the existing SMIv1-based MIB.\n\n This memo defines a MIB for use with managing host systems. The term\n \"host\" is construed to mean any computer that communicates with other\n similar computers attached to the internet and that is directly used\n by one or more human beings. Although this MIB does not necessarily\n apply to devices whose primary function is communications services\n (e.g., terminal servers, routers, bridges, monitoring equipment),\n such relevance is not explicitly precluded. Thi 2790 attribute attributes key management registered nested-reference unchanged"},{"id":"IETF RFC 2837","type":"specification","body":"IETF","designation":"RFC 2837","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2837.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2837.txt","https://www.rfc-editor.org/rfc/rfc2837.pdf"],"folder":"IETF/RFC-2837","files":{"txt":{"path":"standards/IETF/RFC-2837/RFC-2837.txt","sha256":"96bf38a92308e2cc410d2cc7ed3606cebe4fcf57a6f24814a4d512b996bae9d3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines the objects for managing the\n operations of the Fabric Element portion of the Fibre Channel\n Standards.","scope_keywords":["2837","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null}],"search_text":"IETF RFC 2837 This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines the objects for managing the\n operations of the Fabric Element portion of the Fibre Channel\n Standards. 2837 management nested-reference unchanged"},{"id":"IETF RFC 2851","type":"specification","body":"IETF","designation":"RFC 2851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2851.txt","https://www.rfc-editor.org/rfc/rfc2851.pdf"],"folder":"IETF/RFC-2851","files":{"txt":{"path":"standards/IETF/RFC-2851/RFC-2851.txt","sha256":"14937bf944baa790a611e57d178d35102a8642a9742b8bc4dccc868718d22d89"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these definitions will be imported and used in MIBs that would\n otherwise define their own representations.\n\n This work is output from the Operations and Management Area \"IPv6MIB\"\n design team.","scope_keywords":["2851","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null}],"search_text":"IETF RFC 2851 This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these definitions will be imported and used in MIBs that would\n otherwise define their own representations.\n\n This work is output from the Operations and Management Area \"IPv6MIB\"\n design team. 2851 key management presentation nested-reference unchanged"},{"id":"IETF RFC 2856","type":"specification","body":"IETF","designation":"RFC 2856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2856.txt","https://www.rfc-editor.org/rfc/rfc2856.pdf"],"folder":"IETF/RFC-2856","files":{"txt":{"path":"standards/IETF/RFC-2856/RFC-2856.txt","sha256":"8801cc0d6bc82822da043e948e1a3c0774dae5e4110b76434172bbc26a2e969d"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies new textual conventions for additional high\n capacity data types, intended for SNMP implementations which already\n support the Counter64 data type. The definitions contained in this\n document represent a short term solution which may be deprecated in\n the future.","scope_keywords":["2856","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 2856 This memo specifies new textual conventions for additional high\n capacity data types, intended for SNMP implementations which already\n support the Counter64 data type. The definitions contained in this\n document represent a short term solution which may be deprecated in\n the future. 2856 management presentation nested-reference unchanged"},{"id":"IETF RFC 2863","type":"specification","body":"IETF","designation":"RFC 2863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2863.txt","https://www.rfc-editor.org/rfc/rfc2863.pdf"],"folder":"IETF/RFC-2863","files":{"txt":{"path":"standards/IETF/RFC-2863/RFC-2863.txt","sha256":"3611f3f0accb11f7aacadc37576cce280bfaf0f4d32df38d4efe86a63bac7d64"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2863 Cisco Systems\nObsoletes: 2233 F. Kastenholz\nCategory: Standards Track Argon Networks\n June 2000\n\n The Interfaces Group MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ................................................. 2\n 2 The SNMP Network Management Framework ........................ 2\n 3 Experience with the Interfaces Group ......................... 3\n 3.1 Clarifications/Revisions .............","scope_keywords":["2863","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3535","folder":"IETF/RFC-3535","source":"IETF/RFC-3535/RFC-3535.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null}],"search_text":"IETF RFC 2863 Network Working Group K. McCloghrie\nRequest for Comments: 2863 Cisco Systems\nObsoletes: 2233 F. Kastenholz\nCategory: Standards Track Argon Networks\n June 2000\n\n The Interfaces Group MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ................................................. 2\n 2 The SNMP Network Management Framework ........................ 2\n 3 Experience with the Interfaces Group ......................... 3\n 3.1 Clarifications/Revisions ............. 2863 key management nested-reference unchanged"},{"id":"IETF RFC 2864","type":"specification","body":"IETF","designation":"RFC 2864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2864.txt","https://www.rfc-editor.org/rfc/rfc2864.pdf"],"folder":"IETF/RFC-2864","files":{"txt":{"path":"standards/IETF/RFC-2864/RFC-2864.txt","sha256":"b189f94d4b88402201828368d83d8fd830906e3873f4d9bdfb4fc72c9b6d02b7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2864 Cisco Systems\nCategory: Standards Track G. Hanson\n ADC Telecommunications\n June 2000\n\n The Inverted Stack Table Extension to the Interfaces Group MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .................................................. 1\n 2 The SNMP Network Management Framework ......................... 1\n 3 Interface Sub-Layers and the ifStackTable ..................... 3\n 4 Definition","scope_keywords":["2864","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null}],"search_text":"IETF RFC 2864 Network Working Group K. McCloghrie\nRequest for Comments: 2864 Cisco Systems\nCategory: Standards Track G. Hanson\n ADC Telecommunications\n June 2000\n\n The Inverted Stack Table Extension to the Interfaces Group MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .................................................. 1\n 2 The SNMP Network Management Framework ......................... 1\n 3 Interface Sub-Layers and the ifStackTable ..................... 3\n 4 Definition 2864 management nested-reference unchanged"},{"id":"IETF RFC 2925","type":"specification","body":"IETF","designation":"RFC 2925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2925.txt","https://www.rfc-editor.org/rfc/rfc2925.pdf"],"folder":"IETF/RFC-2925","files":{"txt":{"path":"standards/IETF/RFC-2925/RFC-2925.txt","sha256":"181880adbdc867df7ae1b6b1df88b92dc2aea5fc14eec3f9abe543cbe3d018da"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines Management Information Bases (MIBs) for performing\n remote ping, traceroute and lookup operations at a remote host. When\n managing a network it is useful to be able to initiate and retrieve\n the results of ping or traceroute operations when performed at a\n remote host. A Lookup capability is defined in order to enable\n resolving of either an IP address to an DNS name or an DNS name to an\n IP address at a remote host.\n\n Currently, there are several enterprise-specific MIBs for performing\n remote ping or traceroute operations. The purpose of this memo is to\n define a standards-based solution to enable interoperability.","scope_keywords":["2925","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null}],"search_text":"IETF RFC 2925 This memo defines Management Information Bases (MIBs) for performing\n remote ping, traceroute and lookup operations at a remote host. When\n managing a network it is useful to be able to initiate and retrieve\n the results of ping or traceroute operations when performed at a\n remote host. A Lookup capability is defined in order to enable\n resolving of either an IP address to an DNS name or an DNS name to an\n IP address at a remote host.\n\n Currently, there are several enterprise-specific MIBs for performing\n remote ping or traceroute operations. The purpose of this memo is to\n define a standards-based solution to enable interoperability. 2925 key management path nested-reference unchanged"},{"id":"IETF RFC 2954","type":"specification","body":"IETF","designation":"RFC 2954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2954.txt","https://www.rfc-editor.org/rfc/rfc2954.pdf"],"folder":"IETF/RFC-2954","files":{"txt":{"path":"standards/IETF/RFC-2954/RFC-2954.txt","sha256":"d64d57c568da9e60008e42414910132ae2064a7a8139c90c2526d335002e7250"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in Transmission\n Control Protocol/Internet Protocol-based (TCP/IP) internets. In\n particular, it defines objects for managing the frame relay service.\n\n This document obsoletes RFC 1604.","scope_keywords":["2954","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2954 This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in Transmission\n Control Protocol/Internet Protocol-based (TCP/IP) internets. In\n particular, it defines objects for managing the frame relay service.\n\n This document obsoletes RFC 1604. 2954 management nested-reference unchanged"},{"id":"IETF RFC 2955","type":"specification","body":"IETF","designation":"RFC 2955","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2955.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2955.txt","https://www.rfc-editor.org/rfc/rfc2955.pdf"],"folder":"IETF/RFC-2955","files":{"txt":{"path":"standards/IETF/RFC-2955/RFC-2955.txt","sha256":"abd1eca64f68d0fa61e15f9e4e08a1526d04f69db72f5ae7c1c51073d91b5d98"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) to configure,\n monitor, and control a service interworking function (IWF) for\n Permanent Virtual Connections (PVC) between Frame Relay and\n Asynchronous Transfer Mode (ATM) technologies.","scope_keywords":["2955","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2955 This memo defines a Management Information Base (MIB) to configure,\n monitor, and control a service interworking function (IWF) for\n Permanent Virtual Connections (PVC) between Frame Relay and\n Asynchronous Transfer Mode (ATM) technologies. 2955 key management nested-reference unchanged"},{"id":"IETF RFC 2959","type":"specification","body":"IETF","designation":"RFC 2959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2959.txt","https://www.rfc-editor.org/rfc/rfc2959.pdf"],"folder":"IETF/RFC-2959","files":{"txt":{"path":"standards/IETF/RFC-2959/RFC-2959.txt","sha256":"0c6cbd82b80603332b17125988299c8832b31ab2dd01a9830cf4c7cb7ed353a2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing Real-Time Transport\n Protocol (RTP) systems (RFC1889).","scope_keywords":["2959","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null}],"search_text":"IETF RFC 2959 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for managing Real-Time Transport\n Protocol (RTP) systems (RFC1889). 2959 key management nested-reference unchanged"},{"id":"IETF RFC 2975","type":"specification","body":"IETF","designation":"RFC 2975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2975.txt","https://www.rfc-editor.org/rfc/rfc2975.pdf"],"folder":"IETF/RFC-2975","files":{"txt":{"path":"standards/IETF/RFC-2975/RFC-2975.txt","sha256":"52789d1616565b3b2731f7114b177817241c25fb34e0c3ff8e2552c9e41b9628"}},"tags":["nested-reference","unchanged"],"summary":"The field of Accounting Management is concerned with the collection\n of resource consumption data for the purposes of capacity and trend\n analysis, cost allocation, auditing, and billing. This document\n describes each of these problems, and discusses the issues involved\n in design of modern accounting systems.\n\n Since accounting applications do not have uniform security and\n reliability requirements, it is not possible to devise a single\n accounting protocol and set of security services that will meet all\n needs. Thus the goal of accounting management is to provide a set of\n tools that can be used to meet the requirements of each application.\n This document describes the currently available tools as well as the\n state of the art in accounting protocol design. A companion\n document, RFC 2924, reviews the state of the art in accounting\n attributes and record formats.\n\nAboba, et al. Informa","scope_keywords":["2975","attribute","attributes","audit","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 2975 The field of Accounting Management is concerned with the collection\n of resource consumption data for the purposes of capacity and trend\n analysis, cost allocation, auditing, and billing. This document\n describes each of these problems, and discusses the issues involved\n in design of modern accounting systems.\n\n Since accounting applications do not have uniform security and\n reliability requirements, it is not possible to devise a single\n accounting protocol and set of security services that will meet all\n needs. Thus the goal of accounting management is to provide a set of\n tools that can be used to meet the requirements of each application.\n This document describes the currently available tools as well as the\n state of the art in accounting protocol design. A companion\n document, RFC 2924, reviews the state of the art in accounting\n attributes and record formats.\n\nAboba, et al. Informa 2975 attribute attributes audit authentication key management nested-reference unchanged"},{"id":"IETF RFC 2981","type":"specification","body":"IETF","designation":"RFC 2981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2981.txt","https://www.rfc-editor.org/rfc/rfc2981.pdf"],"folder":"IETF/RFC-2981","files":{"txt":{"path":"standards/IETF/RFC-2981/RFC-2981.txt","sha256":"ec0c902380f304241193359acf0ddf4ff35ea86e73fe1046b2e6e338cf234405"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects that can be used to\n manage and monitor MIB objects and take action through events.\n\n The Event MIB provides the ability to monitor MIB objects on the\n local system or on a remote system and take simple action when a\n trigger condition is met.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.","scope_keywords":["2981","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2981 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects that can be used to\n manage and monitor MIB objects and take action through events.\n\n The Event MIB provides the ability to monitor MIB objects on the\n local system or on a remote system and take simple action when a\n trigger condition is met.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119. 2981 key management nested-reference unchanged"},{"id":"IETF RFC 2982","type":"specification","body":"IETF","designation":"RFC 2982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2982.txt","https://www.rfc-editor.org/rfc/rfc2982.pdf"],"folder":"IETF/RFC-2982","files":{"txt":{"path":"standards/IETF/RFC-2982/RFC-2982.txt","sha256":"7025b3a7bc69bfd6f796265f31e2683e4e4a22e11e113035075057b442f50bfc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n expressions of MIB objects. The results of these expressions become\n MIB objects usable like any other MIB object, such as for the test\n condition for declaring an event.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.","scope_keywords":["2982","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2982 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing\n expressions of MIB objects. The results of these expressions become\n MIB objects usable like any other MIB object, such as for the test\n condition for declaring an event.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119. 2982 identification key management nested-reference unchanged"},{"id":"IETF RFC 3014","type":"specification","body":"IETF","designation":"RFC 3014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3014.txt","https://www.rfc-editor.org/rfc/rfc3014.pdf"],"folder":"IETF/RFC-3014","files":{"txt":{"path":"standards/IETF/RFC-3014/RFC-3014.txt","sha256":"020d2d4bc0ca103b80acad82f4436084e74540e22d0fe794acbff662fcf27719"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for logging Simple\n Network Management Protocol (SNMP) Notifications.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nKavasseri Standards Track [Page 1]\n\f\nRFC 3014 Notification Log MIB November 2000","scope_keywords":["3014","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4177","folder":"IETF/RFC-4177","source":"IETF/RFC-4177/RFC-4177.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3014 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for logging Simple\n Network Management Protocol (SNMP) Notifications.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nKavasseri Standards Track [Page 1]\n\f\nRFC 3014 Notification Log MIB November 2000 3014 identification key management nested-reference unchanged"},{"id":"IETF RFC 3019","type":"specification","body":"IETF","designation":"RFC 3019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3019.txt","https://www.rfc-editor.org/rfc/rfc3019.pdf"],"folder":"IETF/RFC-3019","files":{"txt":{"path":"standards/IETF/RFC-3019/RFC-3019.txt","sha256":"31d9267ad2d94cf27a423057605a46072d55c6f1481c82825ecb6daca7cb4a14"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Haberman\nRequest for Comments: 3019 Nortel Networks\nCategory: Standards Track R. Worzella\n IBM\n January 2001\n\n IP Version 6 Management Information Base for\n The Multicast Listener Discovery Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in Internet Protocol\n Version 6 internets. Specifically, this document is the MIB module\n that define","scope_keywords":["3019","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null}],"search_text":"IETF RFC 3019 Network Working Group B. Haberman\nRequest for Comments: 3019 Nortel Networks\nCategory: Standards Track R. Worzella\n IBM\n January 2001\n\n IP Version 6 Management Information Base for\n The Multicast Listener Discovery Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in Internet Protocol\n Version 6 internets. Specifically, this document is the MIB module\n that define 3019 key management nested-reference unchanged"},{"id":"IETF RFC 3020","type":"specification","body":"IETF","designation":"RFC 3020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3020.txt","https://www.rfc-editor.org/rfc/rfc3020.pdf"],"folder":"IETF/RFC-3020","files":{"txt":{"path":"standards/IETF/RFC-3020/RFC-3020.txt","sha256":"7bc833c31dac8a2575da4e9c48747655327c42b1d741199de1b37dc1b133c238"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) for monitoring\n and controlling a UNI/NNI Multilink Frame Relay Function as defined\n in Frame Relay Forum FRF.16. This MIB also includes conformance and\n notification information.","scope_keywords":["3020","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null}],"search_text":"IETF RFC 3020 This memo defines a Management Information Base (MIB) for monitoring\n and controlling a UNI/NNI Multilink Frame Relay Function as defined\n in Frame Relay Forum FRF.16. This MIB also includes conformance and\n notification information. 3020 management nested-reference unchanged"},{"id":"IETF RFC 3083","type":"specification","body":"IETF","designation":"RFC 3083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3083.txt","https://www.rfc-editor.org/rfc/rfc3083.pdf"],"folder":"IETF/RFC-3083","files":{"txt":{"path":"standards/IETF/RFC-3083/RFC-3083.txt","sha256":"f9d98aa312e4ebc27b2b003f5603f4ad39af6ecda167a599112c46532302e7a5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based (Simple Network Management Protocol) management of the Baseline\n Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0\n (Data-Over-Cable Service Interface Specifications) compliant Cable\n Modems and Cable Modem Termination Systems. This MIB is defined as\n an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SMIv2 (Structure of Management Information Version 2). The set of\n objects is consistent with the SNMP framework and existing SNMP\n standards.\n\n CableLabs requires the implementation of this MIB in DOCSIS 1.0 cable\n modems that implement the Baseline Privacy Interface, as a\n","scope_keywords":["3083","authentication","authorization","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null}],"search_text":"IETF RFC 3083 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a basic set of managed objects for SNMP-\n based (Simple Network Management Protocol) management of the Baseline\n Privacy Interface (BPI), which provides data privacy for DOCSIS 1.0\n (Data-Over-Cable Service Interface Specifications) compliant Cable\n Modems and Cable Modem Termination Systems. This MIB is defined as\n an extension to the DOCSIS Radio Frequency Interface MIB, RFC 2670.\n\n This memo specifies a MIB module in a manner that is compliant to the\n SMIv2 (Structure of Management Information Version 2). The set of\n objects is consistent with the SNMP framework and existing SNMP\n standards.\n\n CableLabs requires the implementation of this MIB in DOCSIS 1.0 cable\n modems that implement the Baseline Privacy Interface, as a\n 3083 authentication authorization encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 3144","type":"specification","body":"IETF","designation":"RFC 3144","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3144.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3144.txt","https://www.rfc-editor.org/rfc/rfc3144.pdf"],"folder":"IETF/RFC-3144","files":{"txt":{"path":"standards/IETF/RFC-3144/RFC-3144.txt","sha256":"a49c10e2e2a01efe7c1c9d06936f66d5f7113d8c77ec574c2e755393c968a2cc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n The document proposes an extension to the Remote Monitoring MIB with\n a method of sorting the interfaces of a monitored device according to\n values of parameters specific to this interface.","scope_keywords":["3144","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3144 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n The document proposes an extension to the Remote Monitoring MIB with\n a method of sorting the interfaces of a monitored device according to\n values of parameters specific to this interface. 3144 key management nested-reference unchanged"},{"id":"IETF RFC 3165","type":"specification","body":"IETF","designation":"RFC 3165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3165.txt","https://www.rfc-editor.org/rfc/rfc3165.pdf"],"folder":"IETF/RFC-3165","files":{"txt":{"path":"standards/IETF/RFC-3165/RFC-3165.txt","sha256":"77cfd6e7974680e52750222cfe55b7124927ba0c440a8f94d14e21742d351d62"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow the\n delegation of management scripts to distributed managers.\n\nLevi & Schoenwaelder Standards Track [Page 1]\n\f\nRFC 3165 Script MIB August 2001","scope_keywords":["3165","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3165 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow the\n delegation of management scripts to distributed managers.\n\nLevi & Schoenwaelder Standards Track [Page 1]\n\f\nRFC 3165 Script MIB August 2001 3165 key management nested-reference unchanged"},{"id":"IETF RFC 3231","type":"specification","body":"IETF","designation":"RFC 3231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3231.txt","https://www.rfc-editor.org/rfc/rfc3231.pdf"],"folder":"IETF/RFC-3231","files":{"txt":{"path":"standards/IETF/RFC-3231/RFC-3231.txt","sha256":"98e3e9b3f68cd062cfb3b95fe65e7e54532523d9d3cede9853044cbe479d4f41"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n schedule management operations periodically or at specified dates and\n times.\n\n This document obsoletes RFC 2591.","scope_keywords":["3231","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null}],"search_text":"IETF RFC 3231 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n schedule management operations periodically or at specified dates and\n times.\n\n This document obsoletes RFC 2591. 3231 key management nested-reference unchanged"},{"id":"IETF RFC 3276","type":"specification","body":"IETF","designation":"RFC 3276","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3276.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3276.txt","https://www.rfc-editor.org/rfc/rfc3276.pdf"],"folder":"IETF/RFC-3276","files":{"txt":{"path":"standards/IETF/RFC-3276/RFC-3276.txt","sha256":"7972a085a75b666afb4cbe707889caa071b0967f7ff392dc1947eacdb09e8812"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) module for use with network management protocols in the\n Internet community. In particular, it describes objects used for\n managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair\n High-Speed Digital Subscriber Line (SHDSL) interfaces.","scope_keywords":["3276","attribute","attributes","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null}],"search_text":"IETF RFC 3276 This document defines a portion of the Management Information Base\n (MIB) module for use with network management protocols in the\n Internet community. In particular, it describes objects used for\n managing High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair\n High-Speed Digital Subscriber Line (SHDSL) interfaces. 3276 attribute attributes key management profile profiles nested-reference unchanged"},{"id":"IETF RFC 3287","type":"specification","body":"IETF","designation":"RFC 3287","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3287.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3287.txt","https://www.rfc-editor.org/rfc/rfc3287.pdf"],"folder":"IETF/RFC-3287","files":{"txt":{"path":"standards/IETF/RFC-3287/RFC-3287.txt","sha256":"d8b0ad10d8eedd3407877d5cfeea2ce26eafe109c4e293851a308ee2231cd525"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for monitoring\n Differentiated Services (DS) Codepoint usage in packets which contain\n a DS field, utilizing the monitoring framework defined in the RMON-2\n (Remote Network Monitoring Management Version 2) MIB.","scope_keywords":["3287","management","policies","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null}],"search_text":"IETF RFC 3287 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for monitoring\n Differentiated Services (DS) Codepoint usage in packets which contain\n a DS field, utilizing the monitoring framework defined in the RMON-2\n (Remote Network Monitoring Management Version 2) MIB. 3287 management policies profile profiles nested-reference unchanged"},{"id":"IETF RFC 3291","type":"specification","body":"IETF","designation":"RFC 3291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3291.txt","https://www.rfc-editor.org/rfc/rfc3291.pdf"],"folder":"IETF/RFC-3291","files":{"txt":{"path":"standards/IETF/RFC-3291/RFC-3291.txt","sha256":"2c6876372a9c0aa2f825b458822127b94055e4d1e774225378dd561300d1057b"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these textual conventions (TCs) will be imported and used in MIB\n modules that would otherwise define their own representations.\n\n This document obsoletes RFC 2851.\n\nDaniele, et. al. Standards Track [Page 1]\n\f\nRFC 3291 TCs for Internet Network Addresses May 2002","scope_keywords":["3291","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null}],"search_text":"IETF RFC 3291 This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these textual conventions (TCs) will be imported and used in MIB\n modules that would otherwise define their own representations.\n\n This document obsoletes RFC 2851.\n\nDaniele, et. al. Standards Track [Page 1]\n\f\nRFC 3291 TCs for Internet Network Addresses May 2002 3291 key management presentation nested-reference unchanged"},{"id":"IETF RFC 3371","type":"specification","body":"IETF","designation":"RFC 3371","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3371.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3371.txt","https://www.rfc-editor.org/rfc/rfc3371.pdf"],"folder":"IETF/RFC-3371","files":{"txt":{"path":"standards/IETF/RFC-3371/RFC-3371.txt","sha256":"be1d52bf8591fb5d5bb9ca39d2d5495eaf9276614bd3ddfb7cf7a4589b1a816c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing networks using Layer 2\n Tunneling Protocol (L2TP).\n\nCaves, et. al. Standards Track [Page 1]\n\f\nRFC 3371 L2TP Management Information Base August 2002","scope_keywords":["3371","authentication","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null}],"search_text":"IETF RFC 3371 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing networks using Layer 2\n Tunneling Protocol (L2TP).\n\nCaves, et. al. Standards Track [Page 1]\n\f\nRFC 3371 L2TP Management Information Base August 2002 3371 authentication key keys management nested-reference unchanged"},{"id":"IETF RFC 3383","type":"specification","body":"IETF","designation":"RFC 3383","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3383.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3383.txt","https://www.rfc-editor.org/rfc/rfc3383.pdf"],"folder":"IETF/RFC-3383","files":{"txt":{"path":"standards/IETF/RFC-3383/RFC-3383.txt","sha256":"8891415ec4ecabc2e116c6fc3282f2437c3f55e024403031fb4b5d7aca1e3ddb"}},"tags":["nested-reference","unchanged"],"summary":"This document provides procedures for registering extensible elements\n of the Lightweight Directory Access Protocol (LDAP). This document\n also provides guidelines to the Internet Assigned Numbers Authority\n (IANA) describing conditions under which new values can be assigned.\n\n1. Introduction\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an\n extensible protocol. LDAP supports:\n\n - addition of new operations,\n - extension of existing operations, and\n - extensible schema.\n\n This document details procedures for registering values of used to\n unambiguously identify extensible elements of the protocol including:\n\n - LDAP message types;\n - LDAP extended operations and controls;\n - LDAP result codes;\n - LDAP authentication methods;\n - LDAP attribute description options; and\n - Object Identifier descriptors.\n\n These registries are maintained by the Internet Assigned Numbers\n Au","scope_keywords":["3383","attribute","attributes","authentication","http","key","keys","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3674","folder":"IETF/RFC-3674","source":"IETF/RFC-3674/RFC-3674.txt","version":null},{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3771","folder":"IETF/RFC-3771","source":"IETF/RFC-3771/RFC-3771.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null}],"search_text":"IETF RFC 3383 This document provides procedures for registering extensible elements\n of the Lightweight Directory Access Protocol (LDAP). This document\n also provides guidelines to the Internet Assigned Numbers Authority\n (IANA) describing conditions under which new values can be assigned.\n\n1. Introduction\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an\n extensible protocol. LDAP supports:\n\n - addition of new operations,\n - extension of existing operations, and\n - extensible schema.\n\n This document details procedures for registering values of used to\n unambiguously identify extensible elements of the protocol including:\n\n - LDAP message types;\n - LDAP extended operations and controls;\n - LDAP result codes;\n - LDAP authentication methods;\n - LDAP attribute description options; and\n - Object Identifier descriptors.\n\n These registries are maintained by the Internet Assigned Numbers\n Au 3383 attribute attributes authentication http key keys policy registered nested-reference unchanged"},{"id":"IETF RFC 3395","type":"specification","body":"IETF","designation":"RFC 3395","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3395.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3395.txt","https://www.rfc-editor.org/rfc/rfc3395.pdf"],"folder":"IETF/RFC-3395","files":{"txt":{"path":"standards/IETF/RFC-3395/RFC-3395.txt","sha256":"e3886e76b90b5136169df3dd73958b6797ead510eaf21c60a830ddd56442c472"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines extensions to the Protocol Identifier Reference\n document for the identification of application verb information. It\n updates the Protocol Identifier Reference document but does not\n obsolete any portion of that document. In particular, it describes\n the algorithms required to identify protocol operations (verbs)\n within the protocol encapsulations managed with MIBs such as the\n Remote Network Monitoring MIB Version 2, RFC 2021.","scope_keywords":["3395","algorithm","algorithms","http","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null}],"search_text":"IETF RFC 3395 This memo defines extensions to the Protocol Identifier Reference\n document for the identification of application verb information. It\n updates the Protocol Identifier Reference document but does not\n obsolete any portion of that document. In particular, it describes\n the algorithms required to identify protocol operations (verbs)\n within the protocol encapsulations managed with MIBs such as the\n Remote Network Monitoring MIB Version 2, RFC 2021. 3395 algorithm algorithms http identification management nested-reference unchanged"},{"id":"IETF RFC 3411","type":"specification","body":"IETF","designation":"RFC 3411","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3411.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3411.txt","https://www.rfc-editor.org/rfc/rfc3411.pdf"],"folder":"IETF/RFC-3411","files":{"txt":{"path":"standards/IETF/RFC-3411/RFC-3411.txt","sha256":"5cae3a3d7ab2013b5ba9e285e3fc3c9001b7ccba8fafda48bd04b04e0e366016"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for describing Simple Network\n Management Protocol (SNMP) Management Frameworks. The architecture\n is designed to be modular to allow the evolution of the SNMP protocol\n standards over time. The major portions of the architecture are an\n SNMP engine containing a Message Processing Subsystem, a Security\n Subsystem and an Access Control Subsystem, and possibly multiple SNMP\n applications which provide specific functional processing of\n management data. This document obsoletes RFC 2571.","scope_keywords":["3411","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3826","folder":"IETF/RFC-3826","source":"IETF/RFC-3826/RFC-3826.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null}],"search_text":"IETF RFC 3411 This document describes an architecture for describing Simple Network\n Management Protocol (SNMP) Management Frameworks. The architecture\n is designed to be modular to allow the evolution of the SNMP protocol\n standards over time. The major portions of the architecture are an\n SNMP engine containing a Message Processing Subsystem, a Security\n Subsystem and an Access Control Subsystem, and possibly multiple SNMP\n applications which provide specific functional processing of\n management data. This document obsoletes RFC 2571. 3411 management nested-reference unchanged"},{"id":"IETF RFC 3416","type":"specification","body":"IETF","designation":"RFC 3416","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3416.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3416.txt","https://www.rfc-editor.org/rfc/rfc3416.pdf"],"folder":"IETF/RFC-3416","files":{"txt":{"path":"standards/IETF/RFC-3416/RFC-3416.txt","sha256":"e310ccf5a9cbbcb6c47d2fc0b50316889588d85447c7be0d40ddf74be70c8ac8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines version 2 of the protocol operations for the\n Simple Network Management Protocol (SNMP). It defines the syntax and\n elements of procedure for sending, receiving, and processing SNMP\n PDUs. This document obsoletes RFC 1905.\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3416 Protocol Operations for SNMP December 2002","scope_keywords":["3416","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3416 This document defines version 2 of the protocol operations for the\n Simple Network Management Protocol (SNMP). It defines the syntax and\n elements of procedure for sending, receiving, and processing SNMP\n PDUs. This document obsoletes RFC 1905.\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3416 Protocol Operations for SNMP December 2002 3416 management nested-reference unchanged"},{"id":"IETF RFC 3584","type":"specification","body":"IETF","designation":"RFC 3584","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3584.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3584.txt","https://www.rfc-editor.org/rfc/rfc3584.pdf"],"folder":"IETF/RFC-3584","files":{"txt":{"path":"standards/IETF/RFC-3584/RFC-3584.txt","sha256":"010ec4b0a85aa8d6901fac6f8d61e1d6f9a5d999d98a46031b949e42009dad09"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to describe coexistence between\n version 3 of the Internet-standard Network Management Framework,\n (SNMPv3), version 2 of the Internet-standard Network Management\n Framework (SNMPv2), and the original Internet-standard Network\n Management Framework (SNMPv1). This document also describes how to\n convert MIB modules from SMIv1 format to SMIv2 format. This document\n obsoletes RFC 2576.\n\nFrye, et al. Best Current Practice [Page 1]\n\f\nRFC 3584 Coexistence between SNMP versions August 2003","scope_keywords":["3584","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null}],"search_text":"IETF RFC 3584 The purpose of this document is to describe coexistence between\n version 3 of the Internet-standard Network Management Framework,\n (SNMPv3), version 2 of the Internet-standard Network Management\n Framework (SNMPv2), and the original Internet-standard Network\n Management Framework (SNMPv1). This document also describes how to\n convert MIB modules from SMIv1 format to SMIv2 format. This document\n obsoletes RFC 2576.\n\nFrye, et al. Best Current Practice [Page 1]\n\f\nRFC 3584 Coexistence between SNMP versions August 2003 3584 key management nested-reference unchanged"},{"id":"IETF RFC 2578","type":"specification","body":"IETF","designation":"RFC 2578","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2578.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2578.txt","https://www.rfc-editor.org/rfc/rfc2578.pdf"],"folder":"IETF/RFC-2578","files":{"txt":{"path":"standards/IETF/RFC-2578/RFC-2578.txt","sha256":"77ff4095516641cd3cedac996380b8cf442f3a8727a1ea4b27f03f4871d9bdbf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Editors of this version:\nRequest for Comments: 2578 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1902 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Structure of Management Information Version 2 (SMIv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Cont","scope_keywords":["2578","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2579","folder":"IETF/RFC-2579","source":"IETF/RFC-2579/RFC-2579.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3595","folder":"IETF/RFC-3595","source":"IETF/RFC-3595/RFC-3595.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3729","folder":"IETF/RFC-3729","source":"IETF/RFC-3729/RFC-3729.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3826","folder":"IETF/RFC-3826","source":"IETF/RFC-3826/RFC-3826.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null}],"search_text":"IETF RFC 2578 Network Working Group Editors of this version:\nRequest for Comments: 2578 K. McCloghrie\nSTD: 58 Cisco Systems\nObsoletes: 1902 D. Perkins\nCategory: Standards Track SNMPinfo\n J. Schoenwaelder\n TU Braunschweig\n Authors of previous version:\n J. Case\n SNMP Research\n K. McCloghrie\n Cisco Systems\n M. Rose\n First Virtual Holdings\n S. Waldbusser\n International Network Services\n April 1999\n\n Structure of Management Information Version 2 (SMIv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Cont 2578 key management nested-reference unchanged"},{"id":"IETF RFC 1187","type":"specification","body":"IETF","designation":"RFC 1187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1187.txt","https://www.rfc-editor.org/rfc/rfc1187.pdf"],"folder":"IETF/RFC-1187","files":{"txt":{"path":"standards/IETF/RFC-1187/RFC-1187.txt","sha256":"b78b375aec4fc2250199531ccceefd027a360e53285d4815e88942d644302b46"}},"tags":["nested-reference","unchanged"],"summary":"This memo reports an interesting family of algorithms for bulk table\n retrieval using the Simple Network Management Protocol (RFC 1157) [1].\n\nRose, McCloghrie & Davin [Page 1]\n\f\nRFC 1187 Bulk Table Retrieval with the SNMP October 1990\n\n The reader is expected to be familiar with both the Simple Network\n Management Protocol and SNMP's powerful get-next operator. Please\n send comments to: Marshall T. Rose <mrose@psi.com>.\n\n3. Bulk Table Retrieval with the SNMP\n\n Empirical evidence has shown that SNMP's powerful get-next operator is\n effective for table traversal, particularly when the management\n station is interested in well-defined subsets of a particular table.\n There has been some concern that bulk table retrieval can not be\n efficiently accomplished using the powerful get-next operator. Recent\n experience suggests otherwise.\n\n In the simplest case, using the powerful get-next operator","scope_keywords":["1187","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1187 This memo reports an interesting family of algorithms for bulk table\n retrieval using the Simple Network Management Protocol (RFC 1157) [1].\n\nRose, McCloghrie & Davin [Page 1]\n\f\nRFC 1187 Bulk Table Retrieval with the SNMP October 1990\n\n The reader is expected to be familiar with both the Simple Network\n Management Protocol and SNMP's powerful get-next operator. Please\n send comments to: Marshall T. Rose <mrose@psi.com>.\n\n3. Bulk Table Retrieval with the SNMP\n\n Empirical evidence has shown that SNMP's powerful get-next operator is\n effective for table traversal, particularly when the management\n station is interested in well-defined subsets of a particular table.\n There has been some concern that bulk table retrieval can not be\n efficiently accomplished using the powerful get-next operator. Recent\n experience suggests otherwise.\n\n In the simplest case, using the powerful get-next operator 1187 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 1445","type":"specification","body":"IETF","designation":"RFC 1445","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1445.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1445.txt","https://www.rfc-editor.org/rfc/rfc1445.pdf"],"folder":"IETF/RFC-1445","files":{"txt":{"path":"standards/IETF/RFC-1445/RFC-1445.txt","sha256":"bab470774f5a3c657041c82551db1f22ef8e5ba15f0bd4675291839d41cc4a79"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Galvin\n Request for Comments: 1445 Trusted Information Systems\n K. McCloghrie\n Hughes LAN Systems\n April 1993\n\n Administrative Model\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Elements of the Model ................................. 3\n 2.1 SNMPv2 Party ........................................ 3\n 2.2 SNMPv2 Entity ....................................... 6\n 2.3 SNM","scope_keywords":["1445","authentication","authorization","key","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1451","folder":"IETF/RFC-1451","source":"IETF/RFC-1451/RFC-1451.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1566","folder":"IETF/RFC-1566","source":"IETF/RFC-1566/RFC-1566.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1665","folder":"IETF/RFC-1665","source":"IETF/RFC-1665/RFC-1665.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1696","folder":"IETF/RFC-1696","source":"IETF/RFC-1696/RFC-1696.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2206","folder":"IETF/RFC-2206","source":"IETF/RFC-2206/RFC-2206.txt","version":null},{"body":"IETF","designation":"RFC 2213","folder":"IETF/RFC-2213","source":"IETF/RFC-2213/RFC-2213.txt","version":null},{"body":"IETF","designation":"RFC 2325","folder":"IETF/RFC-2325","source":"IETF/RFC-2325/RFC-2325.txt","version":null}],"search_text":"IETF RFC 1445 Network Working Group J. Galvin\n Request for Comments: 1445 Trusted Information Systems\n K. McCloghrie\n Hughes LAN Systems\n April 1993\n\n Administrative Model\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Elements of the Model ................................. 3\n 2.1 SNMPv2 Party ........................................ 3\n 2.2 SNMPv2 Entity ....................................... 6\n 2.3 SNM 1445 authentication authorization key management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 1446","type":"specification","body":"IETF","designation":"RFC 1446","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1446.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1446.txt","https://www.rfc-editor.org/rfc/rfc1446.pdf"],"folder":"IETF/RFC-1446","files":{"txt":{"path":"standards/IETF/RFC-1446/RFC-1446.txt","sha256":"192b5faa6a71c56a2498aad982293dc0e47e2029484ef3520e8387a337d241b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Galvin\n Request for Comments: 1446 Trusted Information Systems\n K. McCloghrie\n Hughes LAN Systems\n April 1993\n\n Security Protocols\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 1.2 Threats ............................................. 4\n 1.3 Goals and Constraints ............................... 5\n 1.4 Security Services ................................... 6\n 1.5 Mecha","scope_keywords":["1446","algorithm","authentication","authorization","encryption","key","management","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null}],"search_text":"IETF RFC 1446 Network Working Group J. Galvin\n Request for Comments: 1446 Trusted Information Systems\n K. McCloghrie\n Hughes LAN Systems\n April 1993\n\n Security Protocols\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 1.2 Threats ............................................. 4\n 1.3 Goals and Constraints ............................... 5\n 1.4 Security Services ................................... 6\n 1.5 Mecha 1446 algorithm authentication authorization encryption key management policies trust nested-reference unchanged"},{"id":"IETF RFC 1448","type":"specification","body":"IETF","designation":"RFC 1448","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1448.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1448.txt","https://www.rfc-editor.org/rfc/rfc1448.pdf"],"folder":"IETF/RFC-1448","files":{"txt":{"path":"standards/IETF/RFC-1448/RFC-1448.txt","sha256":"f861217438cb05da3fd52332d863bb7a64a7d64164d1f3558cdf76604f29dd90"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1448 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Protocol Operations\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Overview .............................................. 3\n 2.1 Roles of Protocol Entities .......................... ","scope_keywords":["1448","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null},{"body":"IETF","designation":"RFC 1450","folder":"IETF/RFC-1450","source":"IETF/RFC-1450/RFC-1450.txt","version":null},{"body":"IETF","designation":"RFC 1451","folder":"IETF/RFC-1451","source":"IETF/RFC-1451/RFC-1451.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1566","folder":"IETF/RFC-1566","source":"IETF/RFC-1566/RFC-1566.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1665","folder":"IETF/RFC-1665","source":"IETF/RFC-1665/RFC-1665.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1696","folder":"IETF/RFC-1696","source":"IETF/RFC-1696/RFC-1696.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2206","folder":"IETF/RFC-2206","source":"IETF/RFC-2206/RFC-2206.txt","version":null},{"body":"IETF","designation":"RFC 2213","folder":"IETF/RFC-2213","source":"IETF/RFC-2213/RFC-2213.txt","version":null},{"body":"IETF","designation":"RFC 2325","folder":"IETF/RFC-2325","source":"IETF/RFC-2325/RFC-2325.txt","version":null}],"search_text":"IETF RFC 1448 Network Working Group J. Case\n Request for Comments: 1448 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Protocol Operations\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Overview .............................................. 3\n 2.1 Roles of Protocol Entities ..........................  1448 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1449","type":"specification","body":"IETF","designation":"RFC 1449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1449.txt","https://www.rfc-editor.org/rfc/rfc1449.pdf"],"folder":"IETF/RFC-1449","files":{"txt":{"path":"standards/IETF/RFC-1449/RFC-1449.txt","sha256":"4dacd50e3de9097b94f99741dfb03126697c9c18f0b98096dce0be5a532732bf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1449 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Transport Mappings\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3 SNMPv2 over UDP ....................................... 7","scope_keywords":["1449","algorithm","authentication","authorization","management","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null}],"search_text":"IETF RFC 1449 Network Working Group J. Case\n Request for Comments: 1449 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Transport Mappings\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3 SNMPv2 over UDP ....................................... 7 1449 algorithm authentication authorization management policies presentation nested-reference unchanged"},{"id":"IETF RFC 1450","type":"specification","body":"IETF","designation":"RFC 1450","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1450.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1450.txt","https://www.rfc-editor.org/rfc/rfc1450.pdf"],"folder":"IETF/RFC-1450","files":{"txt":{"path":"standards/IETF/RFC-1450/RFC-1450.txt","sha256":"39b6587c1576dcfd84666993bf8122a6d4c34c31311b5b7003dfceb657d6d2d0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1450 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Management Information Base\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 The SNMPv2 Statistics Group ..................","scope_keywords":["1450","authentication","authorization","management","policies","timestamp","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null}],"search_text":"IETF RFC 1450 Network Working Group J. Case\n Request for Comments: 1450 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Management Information Base\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 The SNMPv2 Statistics Group .................. 1450 authentication authorization management policies timestamp tsp nested-reference unchanged"},{"id":"IETF RFC 1628","type":"specification","body":"IETF","designation":"RFC 1628","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1628.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1628.txt","https://www.rfc-editor.org/rfc/rfc1628.pdf"],"folder":"IETF/RFC-1628","files":{"txt":{"path":"standards/IETF/RFC-1628/RFC-1628.txt","sha256":"128903c5a37841e94ec0ddc5d5e6957a5351de1c837ae1bd3dd559febd547b97"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case, Editor\nRequest for Comments: 1628 SNMP Research, Incorporated\nCategory: Standards Track May 1994\n\n UPS Management Information Base\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 2\n 4. Definitions ............................................... 3\n 4.1 The Device Identific","scope_keywords":["1628","identification","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null}],"search_text":"IETF RFC 1628 Network Working Group J. Case, Editor\nRequest for Comments: 1628 SNMP Research, Incorporated\nCategory: Standards Track May 1994\n\n UPS Management Information Base\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 2\n 4. Definitions ............................................... 3\n 4.1 The Device Identific 1628 identification management timestamp nested-reference unchanged"},{"id":"IETF RFC 1906","type":"specification","body":"IETF","designation":"RFC 1906","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1906.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1906.txt","https://www.rfc-editor.org/rfc/rfc1906.pdf"],"folder":"IETF/RFC-1906","files":{"txt":{"path":"standards/IETF/RFC-1906/RFC-1906.txt","sha256":"47c00c44665d3801392eb28612fdb807fd72761e6508718468a862069144578b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1906 J. Case\nObsoletes: 1449 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Transport Mappings for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 2\n 2. Definitions ...","scope_keywords":["1906","authentication","authorization","management","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2579","folder":"IETF/RFC-2579","source":"IETF/RFC-2579/RFC-2579.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1906 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1906 J. Case\nObsoletes: 1449 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Transport Mappings for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 2\n 2. Definitions ... 1906 authentication authorization management policies presentation nested-reference unchanged"},{"id":"IETF RFC 1907","type":"specification","body":"IETF","designation":"RFC 1907","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1907.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1907.txt","https://www.rfc-editor.org/rfc/rfc1907.pdf"],"folder":"IETF/RFC-1907","files":{"txt":{"path":"standards/IETF/RFC-1907/RFC-1907.txt","sha256":"055a5edec23ce440527526c9fcacd742c68f9eb0a1896a47bd6445bfe23c3688"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1907 J. Case\nObsoletes: 1450 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Management Information Base\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 2\n 2. Defin","scope_keywords":["1907","authentication","authorization","identification","management","policies","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null}],"search_text":"IETF RFC 1907 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1907 J. Case\nObsoletes: 1450 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Management Information Base\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 A Note on Terminology ...................................... 2\n 2. Defin 1907 authentication authorization identification management policies timestamp nested-reference unchanged"},{"id":"IETF RFC 1910","type":"specification","body":"IETF","designation":"RFC 1910","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1910.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1910.txt","https://www.rfc-editor.org/rfc/rfc1910.pdf"],"folder":"IETF/RFC-1910","files":{"txt":{"path":"standards/IETF/RFC-1910/RFC-1910.txt","sha256":"f2388a743e104e09ac4068ed78414863d10524f022126d7074b11ee78b5ed2dd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Waters, Editor\nRequest for Comments: 1910 Bell-Northern Research Ltd.\nCategory: Experimental February 1996\n\n User-based Security Model for SNMPv2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 Threats .................................................... 3\n 1.2 Goals and Constraints ...................................... 4\n 1.3 Security Services .......................................... 5\n 1.4 Mechanisms ................................................. 5\n 1.4.1 Digest Authentication Protocol ........................... 7\n 1.4.2 Symmetric Encryption Protocol ........","scope_keywords":["1910","algorithm","authentication","authorization","encryption","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null}],"search_text":"IETF RFC 1910 Network Working Group G. Waters, Editor\nRequest for Comments: 1910 Bell-Northern Research Ltd.\nCategory: Experimental February 1996\n\n User-based Security Model for SNMPv2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 Threats .................................................... 3\n 1.2 Goals and Constraints ...................................... 4\n 1.3 Security Services .......................................... 5\n 1.4 Mechanisms ................................................. 5\n 1.4.1 Digest Authentication Protocol ........................... 7\n 1.4.2 Symmetric Encryption Protocol ........ 1910 algorithm authentication authorization encryption key management policies policy nested-reference unchanged"},{"id":"IETF RFC 2006","type":"specification","body":"IETF","designation":"RFC 2006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2006.txt","https://www.rfc-editor.org/rfc/rfc2006.pdf"],"folder":"IETF/RFC-2006","files":{"txt":{"path":"standards/IETF/RFC-2006/RFC-2006.txt","sha256":"e7435a82700f59cc1cf1beb32aa4ec63d07c95716a7682ab867dc17940d60434"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Management Information Base (MIB) for use with\n network management protocols in TCP/IP-based internets. In\n particular, it describes managed objects used for managing the Mobile\n Node, Foreign Agent and Home Agent of the Mobile IP Protocol.","scope_keywords":["2006","delivery","management","registered","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 2006 This memo defines the Management Information Base (MIB) for use with\n network management protocols in TCP/IP-based internets. In\n particular, it describes managed objects used for managing the Mobile\n Node, Foreign Agent and Home Agent of the Mobile IP Protocol. 2006 delivery management registered timestamp nested-reference unchanged"},{"id":"IETF RFC 2037","type":"specification","body":"IETF","designation":"RFC 2037","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2037.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2037.txt","https://www.rfc-editor.org/rfc/rfc2037.pdf"],"folder":"IETF/RFC-2037","files":{"txt":{"path":"standards/IETF/RFC-2037/RFC-2037.txt","sha256":"d38e9cb6958d2561c8addf5d0eed904b66a87b66e3979d679ea8784536ea0c62"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2037 A. Bierman\nCategory: Standards Track Cisco Systems\n October 1996\n\n Entity MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 2\n 2. The SNMP Network Management Framework ..................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 3\n 3.1 Terms .................................................... 4\n 3.2 Relationship to Community Str","scope_keywords":["2037","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null}],"search_text":"IETF RFC 2037 Network Working Group K. McCloghrie\nRequest for Comments: 2037 A. Bierman\nCategory: Standards Track Cisco Systems\n October 1996\n\n Entity MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 2\n 2. The SNMP Network Management Framework ..................... 2\n 2.1 Object Definitions ....................................... 2\n 3. Overview .................................................. 3\n 3.1 Terms .................................................... 4\n 3.2 Relationship to Community Str 2037 management nested-reference unchanged"},{"id":"IETF RFC 2071","type":"specification","body":"IETF","designation":"RFC 2071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2071.txt","https://www.rfc-editor.org/rfc/rfc2071.pdf"],"folder":"IETF/RFC-2071","files":{"txt":{"path":"standards/IETF/RFC-2071/RFC-2071.txt","sha256":"4a909f1c7a99daa34ebfd784299535b40a4d5c255202b9eea5d8fa8a6f36b6c2"}},"tags":["nested-reference","unchanged"],"summary":"The PIER [Procedures for Internet/Enterprise Renumbering] working\n group is compiling a series of documents to assist and instruct\n organizations in their efforts to renumber. However, it is becoming\n apparent that, with the increasing number of new Internet Service\n Providers (ISP's) and organizations getting connected to the Internet\n for the first time, the concept of network renumbering needs to be\n further defined. This document attempts to clearly define the\n concept of network renumbering and discuss some of the more pertinent\n reasons why an organization would have a need to do so.","scope_keywords":["2071","attribute","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 2071 The PIER [Procedures for Internet/Enterprise Renumbering] working\n group is compiling a series of documents to assist and instruct\n organizations in their efforts to renumber. However, it is becoming\n apparent that, with the increasing number of new Internet Service\n Providers (ISP's) and organizations getting connected to the Internet\n for the first time, the concept of network renumbering needs to be\n further defined. This document attempts to clearly define the\n concept of network renumbering and discuss some of the more pertinent\n reasons why an organization would have a need to do so. 2071 attribute management policies policy nested-reference unchanged"},{"id":"IETF RFC 2089","type":"specification","body":"IETF","designation":"RFC 2089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2089.txt","https://www.rfc-editor.org/rfc/rfc2089.pdf"],"folder":"IETF/RFC-2089","files":{"txt":{"path":"standards/IETF/RFC-2089/RFC-2089.txt","sha256":"66cd3b54ec0794289f1eca81a241e6cc92d65db3380d5aa2b55ae1c9272b1a6b"}},"tags":["nested-reference","unchanged"],"summary":"The goal of this memo is to document a common way of mapping an\n SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP\n agent (one that supports both SNMPv1 and SNMPv2).","scope_keywords":["2089","authorization","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null}],"search_text":"IETF RFC 2089 The goal of this memo is to document a common way of mapping an\n SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP\n agent (one that supports both SNMPv1 and SNMPv2). 2089 authorization management nested-reference unchanged"},{"id":"IETF RFC 2096","type":"specification","body":"IETF","designation":"RFC 2096","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2096.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2096.txt","https://www.rfc-editor.org/rfc/rfc2096.pdf"],"folder":"IETF/RFC-2096","files":{"txt":{"path":"standards/IETF/RFC-2096/RFC-2096.txt","sha256":"d373e54a0037ae9a6f8f39fcccb5c1be54e45f89b360ac53bd065785c5570808"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Baker\nRequest for Comments: 2096 Cisco Systems\nObsoletes: 1354 January 1997\nCategory: Standards Track\n\n IP Forwarding Table MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. The SNMP Network Management Framework ................. 2\n 2.1 Object Definitions ................................... 2\n 3. Overview .............................................. 2\n 4. Definitions ........................................... 3\n 5. Acknowledgements .................................","scope_keywords":["2096","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null}],"search_text":"IETF RFC 2096 Network Working Group F. Baker\nRequest for Comments: 2096 Cisco Systems\nObsoletes: 1354 January 1997\nCategory: Standards Track\n\n IP Forwarding Table MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 2. The SNMP Network Management Framework ................. 2\n 2.1 Object Definitions ................................... 2\n 3. Overview .............................................. 2\n 4. Definitions ........................................... 3\n 5. Acknowledgements ................................. 2096 management path policy nested-reference unchanged"},{"id":"IETF RFC 2115","type":"specification","body":"IETF","designation":"RFC 2115","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2115.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2115.txt","https://www.rfc-editor.org/rfc/rfc2115.pdf"],"folder":"IETF/RFC-2115","files":{"txt":{"path":"standards/IETF/RFC-2115/RFC-2115.txt","sha256":"71ebc202184c49c94532b780a8958a3e4db05d79e22204fdcca14a92322970d3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP- based internets.\n In particular, it defines objects for managing Frame Relay interfaces\n on DTEs.","scope_keywords":["2115","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2115 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP- based internets.\n In particular, it defines objects for managing Frame Relay interfaces\n on DTEs. 2115 management nested-reference unchanged"},{"id":"IETF RFC 2127","type":"specification","body":"IETF","designation":"RFC 2127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2127.txt","https://www.rfc-editor.org/rfc/rfc2127.pdf"],"folder":"IETF/RFC-2127","files":{"txt":{"path":"standards/IETF/RFC-2127/RFC-2127.txt","sha256":"dd13219cb0e778ee709839f3cd8306e8db6037a9791a6b62582868ab6a3db45a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a minimal set of managed objects for SNMP-\n based management of ISDN terminal interfaces. ISDN interfaces are\n supported on a variety of equipment (for data and voice) including\n terminal adapters, bridges, hosts, and routers.\n\n This document specifies a MIB module in a manner that is compliant to\n the SNMPv2 SMI. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This document is a product of the ISDN MIB working group within the\n Internet Engineering Task Force. Comments are solicited and should\n be addressed to the working group's mailing list at isdn-\n mib@cisco.com and/or the author.\n\n The current version of this document reflects changes made during the\n last call period and the IE","scope_keywords":["2127","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2127 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a minimal set of managed objects for SNMP-\n based management of ISDN terminal interfaces. ISDN interfaces are\n supported on a variety of equipment (for data and voice) including\n terminal adapters, bridges, hosts, and routers.\n\n This document specifies a MIB module in a manner that is compliant to\n the SNMPv2 SMI. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This document is a product of the ISDN MIB working group within the\n Internet Engineering Task Force. Comments are solicited and should\n be addressed to the working group's mailing list at isdn-\n mib@cisco.com and/or the author.\n\n The current version of this document reflects changes made during the\n last call period and the IE 2127 management pid nested-reference unchanged"},{"id":"IETF RFC 2128","type":"specification","body":"IETF","designation":"RFC 2128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2128.txt","https://www.rfc-editor.org/rfc/rfc2128.pdf"],"folder":"IETF/RFC-2128","files":{"txt":{"path":"standards/IETF/RFC-2128/RFC-2128.txt","sha256":"3059726914e6d7bbad0c15a2dcfd4187ce302e6c61b7e4b0b542f7884f5a4c0d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing demand\n access circuits, including ISDN.\n\n This document specifies a MIB module in a manner that is compliant to\n the SNMPv2 SMI. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This document is a product of the ISDN MIB working group within the\n Internet Engineering Task Force. Comments are solicited and should\n be addressed to the working group's mailing list at isdn-\n mib@cisco.com and/or the author.","scope_keywords":["2128","algorithm","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2128 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing demand\n access circuits, including ISDN.\n\n This document specifies a MIB module in a manner that is compliant to\n the SNMPv2 SMI. The set of objects is consistent with the SNMP\n framework and existing SNMP standards.\n\n This document is a product of the ISDN MIB working group within the\n Internet Engineering Task Force. Comments are solicited and should\n be addressed to the working group's mailing list at isdn-\n mib@cisco.com and/or the author. 2128 algorithm management nested-reference unchanged"},{"id":"IETF RFC 2233","type":"specification","body":"IETF","designation":"RFC 2233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2233.txt","https://www.rfc-editor.org/rfc/rfc2233.pdf"],"folder":"IETF/RFC-2233","files":{"txt":{"path":"standards/IETF/RFC-2233/RFC-2233.txt","sha256":"bc76d0c468c3d53cade29f36fe282fa3033d19cff15e724ab818af8c49dea7e9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\nRequest for Comments: 2233 Cisco Systems\nObsoletes: 1573 F. Kastenholz\nCategory: Standards Track FTP Software\n November 1997\n\n The Interfaces Group MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .............................................. 2\n 2 The SNMP Network Management Framework ..................... 2\n 2.1 Object Definitions ...................................... 3\n 3 Experience with the Interfaces Grou","scope_keywords":["2233","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null}],"search_text":"IETF RFC 2233 Network Working Group K. McCloghrie\nRequest for Comments: 2233 Cisco Systems\nObsoletes: 1573 F. Kastenholz\nCategory: Standards Track FTP Software\n November 1997\n\n The Interfaces Group MIB using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction .............................................. 2\n 2 The SNMP Network Management Framework ..................... 2\n 2.1 Object Definitions ...................................... 3\n 3 Experience with the Interfaces Grou 2233 key management nested-reference unchanged"},{"id":"IETF RFC 2257","type":"specification","body":"IETF","designation":"RFC 2257","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2257.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2257.txt","https://www.rfc-editor.org/rfc/rfc2257.pdf"],"folder":"IETF/RFC-2257","files":{"txt":{"path":"standards/IETF/RFC-2257/RFC-2257.txt","sha256":"0774624257ce9a21e6b63ba6b375d00c32df1af7e6c108d612f1a89759eba981"}},"tags":["nested-reference","unchanged"],"summary":"of exposition, the original Internet-standard","scope_keywords":["2257","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null}],"search_text":"IETF RFC 2257 of exposition, the original Internet-standard 2257 presentation nested-reference unchanged"},{"id":"IETF RFC 2262","type":"specification","body":"IETF","designation":"RFC 2262","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2262.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2262.txt","https://www.rfc-editor.org/rfc/rfc2262.pdf"],"folder":"IETF/RFC-2262","files":{"txt":{"path":"standards/IETF/RFC-2262/RFC-2262.txt","sha256":"d3d7c0fa12dd0c5cc82a9be16ad7372c7bfd880d03c3b669765fdf58308fe330"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2261]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model.","scope_keywords":["2262","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null}],"search_text":"IETF RFC 2262 This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2261]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model. 2262 key management nested-reference unchanged"},{"id":"IETF RFC 2263","type":"specification","body":"IETF","designation":"RFC 2263","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2263.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2263.txt","https://www.rfc-editor.org/rfc/rfc2263.pdf"],"folder":"IETF/RFC-2263","files":{"txt":{"path":"standards/IETF/RFC-2263/RFC-2263.txt","sha256":"c593d193769a096600ee83c32b2d3ec8a51d73f9b9686d700fa7c59da9f4e6c0"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2261]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding.","scope_keywords":["2263","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null}],"search_text":"IETF RFC 2263 This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2261]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding. 2263 identification management nested-reference unchanged"},{"id":"IETF RFC 2272","type":"specification","body":"IETF","designation":"RFC 2272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2272.txt","https://www.rfc-editor.org/rfc/rfc2272.pdf"],"folder":"IETF/RFC-2272","files":{"txt":{"path":"standards/IETF/RFC-2272/RFC-2272.txt","sha256":"2bd9c061d0406900307bf2231448d8b00f466ba21d0d97ec93dc6dd2a844dbb0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2271]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model.","scope_keywords":["2272","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null}],"search_text":"IETF RFC 2272 This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2271]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model. 2272 key management nested-reference unchanged"},{"id":"IETF RFC 2273","type":"specification","body":"IETF","designation":"RFC 2273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2273.txt","https://www.rfc-editor.org/rfc/rfc2273.pdf"],"folder":"IETF/RFC-2273","files":{"txt":{"path":"standards/IETF/RFC-2273/RFC-2273.txt","sha256":"783e9258a7055c09542d32e612f8140cfa29c06fa353152898946d2e288630e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2271]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding.","scope_keywords":["2273","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null}],"search_text":"IETF RFC 2273 This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2271]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding. 2273 identification management nested-reference unchanged"},{"id":"IETF RFC 2465","type":"specification","body":"IETF","designation":"RFC 2465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2465.txt","https://www.rfc-editor.org/rfc/rfc2465.pdf"],"folder":"IETF/RFC-2465","files":{"txt":{"path":"standards/IETF/RFC-2465/RFC-2465.txt","sha256":"515ba7d76e6a3d74e764c4e9a0eb2696a9ae89a5bcf5838016452f0bdb3dfd16"}},"tags":["nested-reference","unchanged"],"summary":"This document is one in the series of documents that provide MIB\n definitions for for IP Version 6. Specifically, the IPv6 MIB textual\n conventions as well as the IPv6 MIB General group is defined in this\n document.\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the IPv6-based\n internets.\n\n This document specifies a MIB module in a manner that is both\n compliant to the SNMPv2 SMI, and semantically identical to the peer\n SNMPv1 definitions.","scope_keywords":["2465","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null}],"search_text":"IETF RFC 2465 This document is one in the series of documents that provide MIB\n definitions for for IP Version 6. Specifically, the IPv6 MIB textual\n conventions as well as the IPv6 MIB General group is defined in this\n document.\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the IPv6-based\n internets.\n\n This document specifies a MIB module in a manner that is both\n compliant to the SNMPv2 SMI, and semantically identical to the peer\n SNMPv1 definitions. 2465 management presentation nested-reference unchanged"},{"id":"IETF RFC 2466","type":"specification","body":"IETF","designation":"RFC 2466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2466.txt","https://www.rfc-editor.org/rfc/rfc2466.pdf"],"folder":"IETF/RFC-2466","files":{"txt":{"path":"standards/IETF/RFC-2466/RFC-2466.txt","sha256":"72e0e3cc65bb7ad27622ef7282f72930acc0c72cf1128ab2e9d0f0e94be4364e"}},"tags":["nested-reference","unchanged"],"summary":"This document is one in the series of documents that define various\n MIB object groups for IPv6. Specifically, the ICMPv6 group is\n defined in this document.\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the IPv6-based\n internets.\n\n This document specifies a MIB module in a manner that is both\n compliant to the SNMPv2 SMI, and semantically identical to the peer\n SNMPv1 definitions.","scope_keywords":["2466","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null}],"search_text":"IETF RFC 2466 This document is one in the series of documents that define various\n MIB object groups for IPv6. Specifically, the ICMPv6 group is\n defined in this document.\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the IPv6-based\n internets.\n\n This document specifies a MIB module in a manner that is both\n compliant to the SNMPv2 SMI, and semantically identical to the peer\n SNMPv1 definitions. 2466 management nested-reference unchanged"},{"id":"IETF RFC 2572","type":"specification","body":"IETF","designation":"RFC 2572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2572.txt","https://www.rfc-editor.org/rfc/rfc2572.pdf"],"folder":"IETF/RFC-2572","files":{"txt":{"path":"standards/IETF/RFC-2572/RFC-2572.txt","sha256":"f93dd7df6f9904c4688b119569733aba0b473d26b855418d439cec2ede1f9850"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2571]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model.","scope_keywords":["2572","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null}],"search_text":"IETF RFC 2572 This document describes the Message Processing and Dispatching for\n SNMP messages within the SNMP architecture [RFC2571]. It defines the\n procedures for dispatching potentially multiple versions of SNMP\n messages to the proper SNMP Message Processing Models, and for\n dispatching PDUs to SNMP applications. This document also describes\n one Message Processing Model - the SNMPv3 Message Processing Model. 2572 key management nested-reference unchanged"},{"id":"IETF RFC 2573","type":"specification","body":"IETF","designation":"RFC 2573","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2573.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2573.txt","https://www.rfc-editor.org/rfc/rfc2573.pdf"],"folder":"IETF/RFC-2573","files":{"txt":{"path":"standards/IETF/RFC-2573/RFC-2573.txt","sha256":"17ec7c03edc5e2c8489f270e035f25fbe175e110611d2c2f8812e814b6946d85"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2571]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding.","scope_keywords":["2573","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null}],"search_text":"IETF RFC 2573 This memo describes five types of SNMP applications which make use of\n an SNMP engine as described in [RFC2571]. The types of application\n described are Command Generators, Command Responders, Notification\n Originators, Notification Receivers, and Proxy Forwarders.\n\n This memo also defines MIB modules for specifying targets of\n management operations, for notification filtering, and for proxy\n forwarding. 2573 identification key management nested-reference unchanged"},{"id":"IETF RFC 2881","type":"specification","body":"IETF","designation":"RFC 2881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2881.txt","https://www.rfc-editor.org/rfc/rfc2881.pdf"],"folder":"IETF/RFC-2881","files":{"txt":{"path":"standards/IETF/RFC-2881/RFC-2881.txt","sha256":"93b443a7e0b13b5d5bf3000d21882aa0819a16d49f02c4cbb30369dac8b814d3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the terminology and gives a model of typical\n Network Access Server (NAS). The purpose of this effort is to set\n the reference space for describing and evaluating NAS service\n protocols, such as RADIUS (RFCs 2865, 2866) [1], [2] and follow-on\n efforts like AAA Working Group, and the Diameter protocol [3]. These\n are protocols for carrying user service information for\n authentication, authorization, accounting, and auditing, between a\n Network Access Server which desires to authenticate its incoming\n calls and a shared authentication server.","scope_keywords":["2881","audit","authentication","authorization","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2881 This document describes the terminology and gives a model of typical\n Network Access Server (NAS). The purpose of this effort is to set\n the reference space for describing and evaluating NAS service\n protocols, such as RADIUS (RFCs 2865, 2866) [1], [2] and follow-on\n efforts like AAA Working Group, and the Diameter protocol [3]. These\n are protocols for carrying user service information for\n authentication, authorization, accounting, and auditing, between a\n Network Access Server which desires to authenticate its incoming\n calls and a shared authentication server. 2881 audit authentication authorization management policy nested-reference unchanged"},{"id":"IETF RFC 2962","type":"specification","body":"IETF","designation":"RFC 2962","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2962.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2962.txt","https://www.rfc-editor.org/rfc/rfc2962.pdf"],"folder":"IETF/RFC-2962","files":{"txt":{"path":"standards/IETF/RFC-2962/RFC-2962.txt","sha256":"ef91187d651571bbf56f2964b47d38f320a176d5ec89b79a299048e2b6a13bd0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the ALG (Application Level Gateway) for the\n SNMP (Simple Network Management Protocol) by which IP (Internet\n Protocol) addresses in the payload of SNMP packets are statically\n mapped from one group to another. The SNMP ALG is a specific case of\n an Application Level Gateway as described in [15].\n\n An SNMP ALG allows network management stations to manage multiple\n networks that use conflicting IP addresses. This can be important in\n environments where there is a need to use SNMP with NAT (Network\n Address Translator) in order to manage several potentially\n overlapping addressing realms.\n\nRaz, et al. Informational [Page 1]\n\f\nRFC 2962 SNMP Payload Address Translation October 2000\n\n This document includes a detailed description of the requirements and\n limitations for an implementation of an SNMP Application Level\n Gateway. It also discusses other approaches to excha","scope_keywords":["2962","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null}],"search_text":"IETF RFC 2962 This document describes the ALG (Application Level Gateway) for the\n SNMP (Simple Network Management Protocol) by which IP (Internet\n Protocol) addresses in the payload of SNMP packets are statically\n mapped from one group to another. The SNMP ALG is a specific case of\n an Application Level Gateway as described in [15].\n\n An SNMP ALG allows network management stations to manage multiple\n networks that use conflicting IP addresses. This can be important in\n environments where there is a need to use SNMP with NAT (Network\n Address Translator) in order to manage several potentially\n overlapping addressing realms.\n\nRaz, et al. Informational [Page 1]\n\f\nRFC 2962 SNMP Payload Address Translation October 2000\n\n This document includes a detailed description of the requirements and\n limitations for an implementation of an SNMP Application Level\n Gateway. It also discusses other approaches to excha 2962 authentication management nested-reference unchanged"},{"id":"IETF RFC 3216","type":"specification","body":"IETF","designation":"RFC 3216","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3216.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3216.txt","https://www.rfc-editor.org/rfc/rfc3216.pdf"],"folder":"IETF/RFC-3216","files":{"txt":{"path":"standards/IETF/RFC-3216/RFC-3216.txt","sha256":"8edf9920a665fa0d5ce80450fb9cfaa1fcc45dbe762bc23891574426689094e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the objectives for a new data definition\n language, suitable for the modeling of network management constructs,\n that can be directly mapped into SNMP and COPS-PR protocol\n operations.\n\n The purpose of this document is to serve as a set of objectives that\n a subsequent language specification should try to address. It\n captures the results of the working group discussions towards\n consensus on the SMIng objectives.","scope_keywords":["3216","attribute","attributes","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 6340","folder":"IETF/RFC-6340","source":"IETF/RFC-6340/RFC-6340.txt","version":null}],"search_text":"IETF RFC 3216 This document describes the objectives for a new data definition\n language, suitable for the modeling of network management constructs,\n that can be directly mapped into SNMP and COPS-PR protocol\n operations.\n\n The purpose of this document is to serve as a set of objectives that\n a subsequent language specification should try to address. It\n captures the results of the working group discussions towards\n consensus on the SMIng objectives. 3216 attribute attributes key management presentation nested-reference unchanged"},{"id":"IETF RFC 3412","type":"specification","body":"IETF","designation":"RFC 3412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3412.txt","https://www.rfc-editor.org/rfc/rfc3412.pdf"],"folder":"IETF/RFC-3412","files":{"txt":{"path":"standards/IETF/RFC-3412/RFC-3412.txt","sha256":"f424f12923974b94a49ad62343c2d18b1bf6134e3916097e75f14590f793002e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Message Processing and Dispatching for\n Simple Network Management Protocol (SNMP) messages within the SNMP\n architecture. It defines the procedures for dispatching potentially\n multiple versions of SNMP messages to the proper SNMP Message\n Processing Models, and for dispatching PDUs to SNMP applications.\n This document also describes one Message Processing Model - the\n SNMPv3 Message Processing Model. This document obsoletes RFC 2572.\n\nCase, et al. Standards Track [Page 1]\n\f\nRFC 3412 Message Processing and Dispatching for SNMP December 2002","scope_keywords":["3412","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null}],"search_text":"IETF RFC 3412 This document describes the Message Processing and Dispatching for\n Simple Network Management Protocol (SNMP) messages within the SNMP\n architecture. It defines the procedures for dispatching potentially\n multiple versions of SNMP messages to the proper SNMP Message\n Processing Models, and for dispatching PDUs to SNMP applications.\n This document also describes one Message Processing Model - the\n SNMPv3 Message Processing Model. This document obsoletes RFC 2572.\n\nCase, et al. Standards Track [Page 1]\n\f\nRFC 3412 Message Processing and Dispatching for SNMP December 2002 3412 key management nested-reference unchanged"},{"id":"IETF RFC 3413","type":"specification","body":"IETF","designation":"RFC 3413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3413.txt","https://www.rfc-editor.org/rfc/rfc3413.pdf"],"folder":"IETF/RFC-3413","files":{"txt":{"path":"standards/IETF/RFC-3413/RFC-3413.txt","sha256":"bfe91c30cc727b4a8ce2138544f225c4a3b9e2b919079ac1d0b52241da7d4ccc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes five types of Simple Network Management\n Protocol (SNMP) applications which make use of an SNMP engine as\n described in STD 62, RFC 3411. The types of application described\n are Command Generators, Command Responders, Notification Originators,\n Notification Receivers, and Proxy Forwarders.\n\n This document also defines Management Information Base (MIB) modules\n for specifying targets of management operations, for notification\n filtering, and for proxy forwarding. This document obsoletes RFC\n 2573.","scope_keywords":["3413","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null}],"search_text":"IETF RFC 3413 This document describes five types of Simple Network Management\n Protocol (SNMP) applications which make use of an SNMP engine as\n described in STD 62, RFC 3411. The types of application described\n are Command Generators, Command Responders, Notification Originators,\n Notification Receivers, and Proxy Forwarders.\n\n This document also defines Management Information Base (MIB) modules\n for specifying targets of management operations, for notification\n filtering, and for proxy forwarding. This document obsoletes RFC\n 2573. 3413 identification key management nested-reference unchanged"},{"id":"IETF RFC 3417","type":"specification","body":"IETF","designation":"RFC 3417","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3417.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3417.txt","https://www.rfc-editor.org/rfc/rfc3417.pdf"],"folder":"IETF/RFC-3417","files":{"txt":{"path":"standards/IETF/RFC-3417/RFC-3417.txt","sha256":"874be9c26a2ae30bb1ae17405ca53fa493dc40a0a8bda98fa659b82985e943c0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the transport of Simple Network Management\n Protocol (SNMP) messages over various protocols. This document\n obsoletes RFC 1906.\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3417 Transport Mappings for SNMP December 2002","scope_keywords":["3417","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3826","folder":"IETF/RFC-3826","source":"IETF/RFC-3826/RFC-3826.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null}],"search_text":"IETF RFC 3417 This document defines the transport of Simple Network Management\n Protocol (SNMP) messages over various protocols. This document\n obsoletes RFC 1906.\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3417 Transport Mappings for SNMP December 2002 3417 key management nested-reference unchanged"},{"id":"IETF RFC 3418","type":"specification","body":"IETF","designation":"RFC 3418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3418.txt","https://www.rfc-editor.org/rfc/rfc3418.pdf"],"folder":"IETF/RFC-3418","files":{"txt":{"path":"standards/IETF/RFC-3418/RFC-3418.txt","sha256":"7f3313e0581b841e25ed6785f97d392e2718c51a137018e9e8c8773df20895bf"}},"tags":["nested-reference","unchanged"],"summary":"This document defines managed objects which describe the behavior of\n a Simple Network Management Protocol (SNMP) entity. This document\n obsoletes RFC 1907, Management Information Base for Version 2 of the\n Simple Network Management Protocol (SNMPv2).\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3418 MIB for SNMP December 2002","scope_keywords":["3418","identification","key","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null}],"search_text":"IETF RFC 3418 This document defines managed objects which describe the behavior of\n a Simple Network Management Protocol (SNMP) entity. This document\n obsoletes RFC 1907, Management Information Base for Version 2 of the\n Simple Network Management Protocol (SNMPv2).\n\nPresuhn, et al. Standards Track [Page 1]\n\f\nRFC 3418 MIB for SNMP December 2002 3418 identification key management timestamp nested-reference unchanged"},{"id":"IETF RFC 3470","type":"specification","body":"IETF","designation":"RFC 3470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3470.txt","https://www.rfc-editor.org/rfc/rfc3470.pdf"],"folder":"IETF/RFC-3470","files":{"txt":{"path":"standards/IETF/RFC-3470/RFC-3470.txt","sha256":"135eefc848f9a19910542c76ec848b9180c349f78595da8b603c97f667e16124"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Markup Language (XML) is a framework for structuring\n data. While it evolved from Standard Generalized Markup Language\n (SGML) -- a markup language primarily focused on structuring\n documents -- XML has evolved to be a widely-used mechanism for\n representing structured data.\n\n There are a wide variety of Internet protocols being developed; many\n have need for a representation for structured data relevant to their\n application. There has been much interest in the use of XML as a\n representation method. This document describes basic XML concepts,\n analyzes various alternatives in the use of XML, and provides\n guidelines for the use of XML within IETF standards-track protocols.","scope_keywords":["3470","attribute","attributes","http","key","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3470 The Extensible Markup Language (XML) is a framework for structuring\n data. While it evolved from Standard Generalized Markup Language\n (SGML) -- a markup language primarily focused on structuring\n documents -- XML has evolved to be a widely-used mechanism for\n representing structured data.\n\n There are a wide variety of Internet protocols being developed; many\n have need for a representation for structured data relevant to their\n application. There has been much interest in the use of XML as a\n representation method. This document describes basic XML concepts,\n analyzes various alternatives in the use of XML, and provides\n guidelines for the use of XML within IETF standards-track protocols. 3470 attribute attributes http key policy presentation nested-reference unchanged"},{"id":"IETF RFC 3877","type":"specification","body":"IETF","designation":"RFC 3877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3877.txt","https://www.rfc-editor.org/rfc/rfc3877.pdf"],"folder":"IETF/RFC-3877","files":{"txt":{"path":"standards/IETF/RFC-3877/RFC-3877.txt","sha256":"b7be76e75208c0d4345dc9d6477769c0c8776771010bd638b19814645c149805"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes management objects used for modelling and\n storing alarms.\n\nChisholm & Romascanu Standards Track [Page 1]\n\f\nRFC 3877 Alarm MIB September 2004","scope_keywords":["3877","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3877 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes management objects used for modelling and\n storing alarms.\n\nChisholm & Romascanu Standards Track [Page 1]\n\f\nRFC 3877 Alarm MIB September 2004 3877 key management nested-reference unchanged"},{"id":"IETF RFC 6110","type":"specification","body":"IETF","designation":"RFC 6110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6110.txt","https://www.rfc-editor.org/rfc/rfc6110.pdf"],"folder":"IETF/RFC-6110","files":{"txt":{"path":"standards/IETF/RFC-6110/RFC-6110.txt","sha256":"c479e67d92775437cf2410217b94bda4917ddab550e416d1a150d3e8327138b6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the mapping rules for translating YANG data\n models into Document Schema Definition Languages (DSDL), a\n coordinated set of XML schema languages standardized as ISO/IEC\n 19757. The following DSDL schema languages are addressed by the\n mapping: Regular Language for XML Next Generation (RELAX NG),\n Schematron, and Schematron and Document Schema Renaming Language\n (DSRL). The mapping takes one or more YANG modules and produces a\n set of DSDL schemas for a selected target document type -- datastore\n content, Network Configuration Protocol (NETCONF) messages, etc.\n Procedures for schema-based validation of such documents are also\n discussed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and","scope_keywords":["6110","http","key","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null}],"search_text":"IETF RFC 6110 This document specifies the mapping rules for translating YANG data\n models into Document Schema Definition Languages (DSDL), a\n coordinated set of XML schema languages standardized as ISO/IEC\n 19757. The following DSDL schema languages are addressed by the\n mapping: Regular Language for XML Next Generation (RELAX NG),\n Schematron, and Schematron and Document Schema Renaming Language\n (DSRL). The mapping takes one or more YANG modules and produces a\n set of DSDL schemas for a selected target document type -- datastore\n content, Network Configuration Protocol (NETCONF) messages, etc.\n Procedures for schema-based validation of such documents are also\n discussed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and 6110 http key license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 1159","type":"specification","body":"IETF","designation":"RFC 1159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1159.txt","https://www.rfc-editor.org/rfc/rfc1159.pdf"],"folder":"IETF/RFC-1159","files":{"txt":{"path":"standards/IETF/RFC-1159/RFC-1159.txt","sha256":"261218e8ad0fc679707e9276a35d3950d16deec363c864a03213cc973f4b35e0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Nelson\nRequest for Comments: 1159 Clarkson University\n June 1990\n\n Message Send Protocol\n\nStatus of this Memo\n\n This RFC suggests an Experimental Protocol for the Internet\n community. Hosts on the Internet that choose to implement a Message\n Send Protocol may experiment with this protocol. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nDiscussion\n\n The Message Send Protocol is used to send a short message to a given\n user on a given terminal on a given host. This is similar to the\n service provided by Unix's write command, which is limited to the\n users on that host. This service is also known on some hosts as\n \"SEND\".\n\n As the Internet grows, more and more people are using hosts that do\n not run TCP/IP at all times. These hosts may","scope_keywords":["1159"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1312","folder":"IETF/RFC-1312","source":"IETF/RFC-1312/RFC-1312.txt","version":null}],"search_text":"IETF RFC 1159 Network Working Group R. Nelson\nRequest for Comments: 1159 Clarkson University\n June 1990\n\n Message Send Protocol\n\nStatus of this Memo\n\n This RFC suggests an Experimental Protocol for the Internet\n community. Hosts on the Internet that choose to implement a Message\n Send Protocol may experiment with this protocol. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nDiscussion\n\n The Message Send Protocol is used to send a short message to a given\n user on a given terminal on a given host. This is similar to the\n service provided by Unix's write command, which is limited to the\n users on that host. This service is also known on some hosts as\n \"SEND\".\n\n As the Internet grows, more and more people are using hosts that do\n not run TCP/IP at all times. These hosts may 1159 nested-reference unchanged"},{"id":"IETF RFC 1312","type":"specification","body":"IETF","designation":"RFC 1312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1312.txt","https://www.rfc-editor.org/rfc/rfc1312.pdf"],"folder":"IETF/RFC-1312","files":{"txt":{"path":"standards/IETF/RFC-1312/RFC-1312.txt","sha256":"9809b6dcb330978c967b90629451325c6b047c74bf8fc7c3b4ddc59bc6b59a73"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Nelson\nRequest for Comments: 1312 Crynwr Software\nObsoletes: RFC 1159 G. Arnold\n Sun Microsystems, Inc.\n April 1992\n\n Message Send Protocol 2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nDiscussion\n\n The Message Send Protocol is used to send a short message to a given\n user on a given terminal on a given host. Unix's write command\n offers a limited form of this service through its host-local write\n command. This service is also known on some hosts as \"SEND\".\n\n As the Internet grows, more and more people are using hosts that do\n not run Internet protocols at all times. These hosts ","scope_keywords":["1312","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1312 Network Working Group R. Nelson\nRequest for Comments: 1312 Crynwr Software\nObsoletes: RFC 1159 G. Arnold\n Sun Microsystems, Inc.\n April 1992\n\n Message Send Protocol 2\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nDiscussion\n\n The Message Send Protocol is used to send a short message to a given\n user on a given terminal on a given host. Unix's write command\n offers a limited form of this service through its host-local write\n command. This service is also known on some hosts as \"SEND\".\n\n As the Internet grows, more and more people are using hosts that do\n not run Internet protocols at all times. These hosts  1312 signature nested-reference unchanged"},{"id":"IETF RFC 116","type":"specification","body":"IETF","designation":"RFC 116","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc116.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc116.txt","https://www.rfc-editor.org/rfc/rfc116.pdf"],"folder":"IETF/RFC-116","files":{"txt":{"path":"standards/IETF/RFC-116/RFC-116.txt","sha256":"7a3262ae8672ee6d7f811c3be5ba30e9271a75767130b9bbfbe1d482e8dfef53"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRequest for Comments #116 12 April 71\nNIC #5825 UCLA\nCategories: A.2\nObsoletes: None\nUpdates: 99\n\n STRUCTURE OF THE MAY NWG MTG.\n\nIn order to use our time in Atlantic City more effectively, I would\nlike to organize the meetings around discussions of advertised topics,\nwith published status reports and position papers. I envision our\ntime being divided into three phases.\n\nPhase one is for status reports from each of the sites and for the\nintroductions of new sites or agencies. Each existing site should\nplan to report on its state of software and hardware development, and\non its use of the network. New sites will introduce themselves and\npresent their plans for attachment to and use of the network. In\naddition, work on the ILLIAC IV, the List machine, and the terminal\nIMP will be reviewed. I will assume that each site needs 5-10 minutes\nunless I am notified","scope_keywords":["116"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 116 Network Working Group S. Crocker\nRequest for Comments #116 12 April 71\nNIC #5825 UCLA\nCategories: A.2\nObsoletes: None\nUpdates: 99\n\n STRUCTURE OF THE MAY NWG MTG.\n\nIn order to use our time in Atlantic City more effectively, I would\nlike to organize the meetings around discussions of advertised topics,\nwith published status reports and position papers. I envision our\ntime being divided into three phases.\n\nPhase one is for status reports from each of the sites and for the\nintroductions of new sites or agencies. Each existing site should\nplan to report on its state of software and hardware development, and\non its use of the network. New sites will introduce themselves and\npresent their plans for attachment to and use of the network. In\naddition, work on the ILLIAC IV, the List machine, and the terminal\nIMP will be reviewed. I will assume that each site needs 5-10 minutes\nunless I am notified 116 nested-reference unchanged"},{"id":"IETF RFC 1397","type":"specification","body":"IETF","designation":"RFC 1397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1397.txt","https://www.rfc-editor.org/rfc/rfc1397.pdf"],"folder":"IETF/RFC-1397","files":{"txt":{"path":"standards/IETF/RFC-1397/RFC-1397.txt","sha256":"7c32569bb0d605d6433ddf6a7b121980c7e72c5c7ff5da17e99e4dce77953034"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Haskin\nRequest for Comments: 1397 Bolt Beranek and Newman, Inc.\n January 1993\n\n Default Route Advertisement In\n BGP2 And BGP3 Versions Of The Border Gateway Protocol\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies the recommendation of the BGP Working Group\n on default route advertisement support in BGP2 [1] and BGP3 [2]\n versions of the Border Gateway Protocol.\n\n This recommendation only applies to BGP2 and BGP3 versions of the\n Border Gateway Protocol since starting with the BGP4 [3] version a\n default route advertisement capability is bui","scope_keywords":["1397","attribute","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 1397 Network Working Group D. Haskin\nRequest for Comments: 1397 Bolt Beranek and Newman, Inc.\n January 1993\n\n Default Route Advertisement In\n BGP2 And BGP3 Versions Of The Border Gateway Protocol\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies the recommendation of the BGP Working Group\n on default route advertisement support in BGP2 [1] and BGP3 [2]\n versions of the Border Gateway Protocol.\n\n This recommendation only applies to BGP2 and BGP3 versions of the\n Border Gateway Protocol since starting with the BGP4 [3] version a\n default route advertisement capability is bui 1397 attribute path policies nested-reference unchanged"},{"id":"IETF RFC 4992","type":"specification","body":"IETF","designation":"RFC 4992","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4992.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4992.txt","https://www.rfc-editor.org/rfc/rfc4992.pdf"],"folder":"IETF/RFC-4992","files":{"txt":{"path":"standards/IETF/RFC-4992/RFC-4992.txt","sha256":"fc6bc497fbd7e7ec4cb4ad6f9dfc1b832115ec2980bc6fea421e5973f7bed6b0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple TCP transfer protocol for the\n Internet Registry Information Service (IRIS). Data is transferred\n between clients and servers using chunks to achieve pipelining.\n\nNewton Standards Track [Page 1]\n\f\nRFC 4992 IRIS XML Pipelining with Chunks August 2007","scope_keywords":["4992","authentication","key","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4991","folder":"IETF/RFC-4991","source":"IETF/RFC-4991/RFC-4991.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4992 This document describes a simple TCP transfer protocol for the\n Internet Registry Information Service (IRIS). Data is transferred\n between clients and servers using chunks to achieve pipelining.\n\nNewton Standards Track [Page 1]\n\f\nRFC 4992 IRIS XML Pipelining with Chunks August 2007 4992 authentication key tls trust nested-reference unchanged"},{"id":"IETF RFC 4993","type":"specification","body":"IETF","designation":"RFC 4993","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4993.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4993.txt","https://www.rfc-editor.org/rfc/rfc4993.pdf"],"folder":"IETF/RFC-4993","files":{"txt":{"path":"standards/IETF/RFC-4993/RFC-4993.txt","sha256":"f1e6b29b1ca713a830daa652a5887101513563a9dd46d08046f456f0f23387e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a lightweight UDP transfer protocol for the\n Internet Registry Information Service (IRIS). This transfer protocol\n uses a single packet for every request and response, and optionally\n employs compression over the contents of the packet.\n\nNewton Standards Track [Page 1]\n\f\nRFC 4993 Lightweight UDP Transfer Protocol for IRIS August 2007","scope_keywords":["4993","algorithm","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4991","folder":"IETF/RFC-4991","source":"IETF/RFC-4991/RFC-4991.txt","version":null}],"search_text":"IETF RFC 4993 This document describes a lightweight UDP transfer protocol for the\n Internet Registry Information Service (IRIS). This transfer protocol\n uses a single packet for every request and response, and optionally\n employs compression over the contents of the packet.\n\nNewton Standards Track [Page 1]\n\f\nRFC 4993 Lightweight UDP Transfer Protocol for IRIS August 2007 4993 algorithm key trust nested-reference unchanged"},{"id":"IETF RFC 5737","type":"specification","body":"IETF","designation":"RFC 5737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5737.txt","https://www.rfc-editor.org/rfc/rfc5737.pdf"],"folder":"IETF/RFC-5737","files":{"txt":{"path":"standards/IETF/RFC-5737/RFC-5737.txt","sha256":"9d16217614a74a9b064eff900e5cd07a525793cf8227dca1267100e880f0c410"}},"tags":["nested-reference","unchanged"],"summary":"Three IPv4 unicast address blocks are reserved for use in examples in\n specifications and other documents. This document describes the use\n of these blocks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5737.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified a","scope_keywords":["5737","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 5737 Three IPv4 unicast address blocks are reserved for use in examples in\n specifications and other documents. This document describes the use\n of these blocks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5737.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified a 5737 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6873","type":"specification","body":"IETF","designation":"RFC 6873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6873.txt","https://www.rfc-editor.org/rfc/rfc6873.pdf"],"folder":"IETF/RFC-6873","files":{"txt":{"path":"standards/IETF/RFC-6873/RFC-6873.txt","sha256":"181d65fd2c60bd8fb8163f87868df0594a18e61f2ffdbf5e4473b5ff1805d5bd"}},"tags":["nested-reference","unchanged"],"summary":"The SIPCLF working group has defined a Common Log Format (CLF)\n framework for Session Initiation Protocol (SIP) servers. This CLF\n mimics the successful event logging format found in well-known web\n servers like Apache and web proxies like Squid. This document\n proposes an indexed text encoding format for the SIP CLF that retains\n the key advantages of a text-based format while significantly\n increasing processing performance over a purely text-based\n implementation. This file format adheres to the SIP CLF information\n model and provides an effective encoding scheme for all mandatory and\n optional fields that appear in a SIP CLF record.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p","scope_keywords":["6873","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null}],"search_text":"IETF RFC 6873 The SIPCLF working group has defined a Common Log Format (CLF)\n framework for Session Initiation Protocol (SIP) servers. This CLF\n mimics the successful event logging format found in well-known web\n servers like Apache and web proxies like Squid. This document\n proposes an indexed text encoding format for the SIP CLF that retains\n the key advantages of a text-based format while significantly\n increasing processing performance over a purely text-based\n implementation. This file format adheres to the SIP CLF information\n model and provides an effective encoding scheme for all mandatory and\n optional fields that appear in a SIP CLF record.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p 6873 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 1169","type":"specification","body":"IETF","designation":"RFC 1169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1169.txt","https://www.rfc-editor.org/rfc/rfc1169.pdf"],"folder":"IETF/RFC-1169","files":{"txt":{"path":"standards/IETF/RFC-1169/RFC-1169.txt","sha256":"6c56587fee28853927db7c68ee6b1389244565315fdd2e615ee7424edad66fbf"}},"tags":["nested-reference","unchanged"],"summary":"The Federal Networking Council (FNC), the Internet Activities Board\n (IAB), and the Internet Engineering Task Force (IETF) have a firm\n commitment to responsible integration of OSI based upon sound network\n planning. This implies that OSI will be added to the Internet\n without sacrificing services now available to existing Internet\n users, and that a multi-protocol environment will exist in the\n Internet for a prolonged period. Planning is underway within the\n Internet community to enable integration of OSI, coexistence of OSI\n with TCP/IP, and interoperability between OSI and TCP/IP.\n\n The U.S. Government OSI Profile (GOSIP) is a necessary tool for\n planning OSI integration. However, as the August 1990 requirement\n date for GOSIP compliance approaches, concern remains as to how GOSIP\n should be applied to near-term network planning.\n\n The intent of this statement is to help explain the ","scope_keywords":["1169","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null}],"search_text":"IETF RFC 1169 The Federal Networking Council (FNC), the Internet Activities Board\n (IAB), and the Internet Engineering Task Force (IETF) have a firm\n commitment to responsible integration of OSI based upon sound network\n planning. This implies that OSI will be added to the Internet\n without sacrificing services now available to existing Internet\n users, and that a multi-protocol environment will exist in the\n Internet for a prolonged period. Planning is underway within the\n Internet community to enable integration of OSI, coexistence of OSI\n with TCP/IP, and interoperability between OSI and TCP/IP.\n\n The U.S. Government OSI Profile (GOSIP) is a necessary tool for\n planning OSI integration. However, as the August 1990 requirement\n date for GOSIP compliance approaches, concern remains as to how GOSIP\n should be applied to near-term network planning.\n\n The intent of this statement is to help explain the  1169 management profile nested-reference unchanged"},{"id":"IETF RFC 1170","type":"specification","body":"IETF","designation":"RFC 1170","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1170.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1170.txt","https://www.rfc-editor.org/rfc/rfc1170.pdf"],"folder":"IETF/RFC-1170","files":{"txt":{"path":"standards/IETF/RFC-1170/RFC-1170.txt","sha256":"66eb5423eed7bc0eae1a9e2cbb8fe2920e67d0741760fc91e3fba3f8e6dbeb44"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Fougner\nRequest for Comments: 1170 Public Key Partners\n January 1991\n\n Public Key Standards and Licenses\n\nStatus of this Memo\n\n This RFC is a public statement by Public Key Partners regarding\n Public Key Standards and Licenses. This memo is for informational\n use only, and does not constitute an Internet standard. Distribution\n of this memo is unlimited.\n\nPublic Key Standards and Licenses\n\n The Massachusetts Institute of Technology and the Board of Trustees\n of the Leland Stanford Junior University have recently granted Public\n Key Partners exclusive sublicensing rights to the following patents\n registered in the United States, and all of their corresponding\n foreign patents:\n\n Cryptographic Apparatus and Method\n (\"Diffie-Hellman\")............................... No. 4,200,770\n\n Public Key Cryptographic Apparatus\n and Method (\"Hellman-Merkle\").................... ","scope_keywords":["1170","key","license","policies","registered","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null}],"search_text":"IETF RFC 1170 Network Working Group R. Fougner\nRequest for Comments: 1170 Public Key Partners\n January 1991\n\n Public Key Standards and Licenses\n\nStatus of this Memo\n\n This RFC is a public statement by Public Key Partners regarding\n Public Key Standards and Licenses. This memo is for informational\n use only, and does not constitute an Internet standard. Distribution\n of this memo is unlimited.\n\nPublic Key Standards and Licenses\n\n The Massachusetts Institute of Technology and the Board of Trustees\n of the Leland Stanford Junior University have recently granted Public\n Key Partners exclusive sublicensing rights to the following patents\n registered in the United States, and all of their corresponding\n foreign patents:\n\n Cryptographic Apparatus and Method\n (\"Diffie-Hellman\")............................... No. 4,200,770\n\n Public Key Cryptographic Apparatus\n and Method (\"Hellman-Merkle\")....................  1170 key license policies registered signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 1424","type":"specification","body":"IETF","designation":"RFC 1424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1424.txt","https://www.rfc-editor.org/rfc/rfc1424.pdf"],"folder":"IETF/RFC-1424","files":{"txt":{"path":"standards/IETF/RFC-1424/RFC-1424.txt","sha256":"b47e25c707ee606213289e3c037484b14c60be13723c5e8a63f52e858debf74c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 1424 RSA Laboratories\n February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part IV: Key Certification and Related Services\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This document is the product of many discussions at RSA Data\n Security, at Trusted Information Systems, and on the mailing list. Contributors include Dave Balenson, Jim\n Bidzos, Pat Cain, Vint Cerf, Pam Cochrane, Steve Dusse, Jeff Fassett,\n Craig Finseth, Jim Galvin, Mike Indovina, Bob Jueneman, Steve Kent,\n John Lowry, Paul McKenney, Jeff Thomp","scope_keywords":["1424","algorithm","certificate","certificates","crl","issuer","key","path","revocation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1875","folder":"IETF/RFC-1875","source":"IETF/RFC-1875/RFC-1875.txt","version":null},{"body":"IETF","designation":"RFC 2314","folder":"IETF/RFC-2314","source":"IETF/RFC-2314/RFC-2314.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null}],"search_text":"IETF RFC 1424 Network Working Group B. Kaliski\nRequest for Comments: 1424 RSA Laboratories\n February 1993\n\n Privacy Enhancement for Internet Electronic Mail:\n Part IV: Key Certification and Related Services\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAcknowledgements\n\n This document is the product of many discussions at RSA Data\n Security, at Trusted Information Systems, and on the mailing list. Contributors include Dave Balenson, Jim\n Bidzos, Pat Cain, Vint Cerf, Pam Cochrane, Steve Dusse, Jeff Fassett,\n Craig Finseth, Jim Galvin, Mike Indovina, Bob Jueneman, Steve Kent,\n John Lowry, Paul McKenney, Jeff Thomp 1424 algorithm certificate certificates crl issuer key path revocation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 1334","type":"specification","body":"IETF","designation":"RFC 1334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1334.txt","https://www.rfc-editor.org/rfc/rfc1334.pdf"],"folder":"IETF/RFC-1334","files":{"txt":{"path":"standards/IETF/RFC-1334/RFC-1334.txt","sha256":"15536b064730d876a3419ba1f5a461853ed98986c10768800cb6c8a11155e6fc"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, which\n allows negotiation of an Authentication Protocol for authenticating\n its peer before allowing Network Layer protocols to transmit over the\n link.\n\n This document defines two protocols for Authentication: the Password\n Authentication Protocol and the Challenge-Handshake Authentication\n Protocol. This memo is the product of the Point-to-Point Protocol\n Working Group of the Internet Engineering Task Force (IETF).\n Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu\n mailing list.","scope_keywords":["1334","algorithm","authentication","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1471","folder":"IETF/RFC-1471","source":"IETF/RFC-1471/RFC-1471.txt","version":null},{"body":"IETF","designation":"RFC 1472","folder":"IETF/RFC-1472","source":"IETF/RFC-1472/RFC-1472.txt","version":null},{"body":"IETF","designation":"RFC 1473","folder":"IETF/RFC-1473","source":"IETF/RFC-1473/RFC-1473.txt","version":null},{"body":"IETF","designation":"RFC 1474","folder":"IETF/RFC-1474","source":"IETF/RFC-1474/RFC-1474.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 1334 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, which\n allows negotiation of an Authentication Protocol for authenticating\n its peer before allowing Network Layer protocols to transmit over the\n link.\n\n This document defines two protocols for Authentication: the Password\n Authentication Protocol and the Challenge-Handshake Authentication\n Protocol. This memo is the product of the Point-to-Point Protocol\n Working Group of the Internet Engineering Task Force (IETF).\n Comments on this memo should be submitted to the ietf-ppp@ucdavis.edu\n mailing list. 1334 algorithm authentication identification nested-reference unchanged"},{"id":"IETF RFC 1173","type":"specification","body":"IETF","designation":"RFC 1173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1173.txt","https://www.rfc-editor.org/rfc/rfc1173.pdf"],"folder":"IETF/RFC-1173","files":{"txt":{"path":"standards/IETF/RFC-1173/RFC-1173.txt","sha256":"8261b7814a2dd4ba2c3e80e440d2825b76812a6ea5bf61fa8e1bfd2d34945e76"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Van Bokkelen\nRequest for Comments: 1173 FTP Software, Inc.\n August 1990\n\n Responsibilities of Host and Network Managers\n A Summary of the \"Oral Tradition\" of the Internet\n\nStatus of this Memo\n\n This informational RFC describes the conventions to be followed by\n those in charge of networks and hosts in the Internet. It is a\n summary of the \"oral tradition\" of the Internet on this subject.\n [RFC Editor's note: This memo is a contribution by the author of his\n view of these conventions. It is expected that this RFC will provide\n a basis for the development of official policies in the future.]\n These conventions may be supplemented or amended by the policies of\n specific local and regional components of the Internet. This RFC\n does not specify a standard, or a policy of the IAB. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n Status of this Memo .......","scope_keywords":["1173","delivery","management","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null}],"search_text":"IETF RFC 1173 Network Working Group J. Van Bokkelen\nRequest for Comments: 1173 FTP Software, Inc.\n August 1990\n\n Responsibilities of Host and Network Managers\n A Summary of the \"Oral Tradition\" of the Internet\n\nStatus of this Memo\n\n This informational RFC describes the conventions to be followed by\n those in charge of networks and hosts in the Internet. It is a\n summary of the \"oral tradition\" of the Internet on this subject.\n [RFC Editor's note: This memo is a contribution by the author of his\n view of these conventions. It is expected that this RFC will provide\n a basis for the development of official policies in the future.]\n These conventions may be supplemented or amended by the policies of\n specific local and regional components of the Internet. This RFC\n does not specify a standard, or a policy of the IAB. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n Status of this Memo ....... 1173 delivery management policies policy subject nested-reference unchanged"},{"id":"IETF RFC 1174","type":"specification","body":"IETF","designation":"RFC 1174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1174.txt","https://www.rfc-editor.org/rfc/rfc1174.pdf"],"folder":"IETF/RFC-1174","files":{"txt":{"path":"standards/IETF/RFC-1174/RFC-1174.txt","sha256":"3cd4969478baaa6cec46d77f44d8c628933df1895e92a7d73ecf4df9739d0d46"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 1174 CNRI\n August 1990\n\n IAB Recommended Policy on Distributing Internet Identifier Assignment\n and\n IAB Recommended Policy Change to Internet \"Connected\" Status\n\nStatus of this Memo\n\n This informational RFC represents the official view of the Internet\n Activities Board (IAB), and describes the recommended policies and\n procedures on distributing Internet identifier assignments and\n dropping the connected status requirement. This RFC does not specify\n a standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Status of this Memo............................................... 1\n Overview.......................................................... 1\n 1. Recommendation about Internet Identifiers..................... 2\n 1.1. Summary..................................................... 2\n 1.2. Introduction........................","scope_keywords":["1174","pid","policies","policy","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1366","folder":"IETF/RFC-1366","source":"IETF/RFC-1366/RFC-1366.txt","version":null},{"body":"IETF","designation":"RFC 1466","folder":"IETF/RFC-1466","source":"IETF/RFC-1466/RFC-1466.txt","version":null},{"body":"IETF","designation":"RFC 1518","folder":"IETF/RFC-1518","source":"IETF/RFC-1518/RFC-1518.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null}],"search_text":"IETF RFC 1174 Network Working Group V. Cerf\nRequest for Comments: 1174 CNRI\n August 1990\n\n IAB Recommended Policy on Distributing Internet Identifier Assignment\n and\n IAB Recommended Policy Change to Internet \"Connected\" Status\n\nStatus of this Memo\n\n This informational RFC represents the official view of the Internet\n Activities Board (IAB), and describes the recommended policies and\n procedures on distributing Internet identifier assignments and\n dropping the connected status requirement. This RFC does not specify\n a standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n Status of this Memo............................................... 1\n Overview.......................................................... 1\n 1. Recommendation about Internet Identifiers..................... 2\n 1.1. Summary..................................................... 2\n 1.2. Introduction........................ 1174 pid policies policy registered subject nested-reference unchanged"},{"id":"IETF RFC 1366","type":"specification","body":"IETF","designation":"RFC 1366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1366.txt","https://www.rfc-editor.org/rfc/rfc1366.pdf"],"folder":"IETF/RFC-1366","files":{"txt":{"path":"standards/IETF/RFC-1366/RFC-1366.txt","sha256":"a5dad2846bf776d0732922af0f33f4b491d904d686514b4020c54c9911626af1"}},"tags":["nested-reference","unchanged"],"summary":"This document has been reviewed by the Federal Engineering Task Force\n (FEPG) on behalf of the Federal Networking Council (FNC), the co-\n chairs of the International Engineering Planning Group (IEPG), and\n the Reseaux IP Europeens (RIPE). There was general consensus by\n those groups to support the recommendations proposed in this document\n for management of the IP address space.","scope_keywords":["1366","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1367","folder":"IETF/RFC-1367","source":"IETF/RFC-1367/RFC-1367.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null}],"search_text":"IETF RFC 1366 This document has been reviewed by the Federal Engineering Task Force\n (FEPG) on behalf of the Federal Networking Council (FNC), the co-\n chairs of the International Engineering Planning Group (IEPG), and\n the Reseaux IP Europeens (RIPE). There was general consensus by\n those groups to support the recommendations proposed in this document\n for management of the IP address space. 1366 management qualified nested-reference unchanged"},{"id":"IETF RFC 1466","type":"specification","body":"IETF","designation":"RFC 1466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1466.txt","https://www.rfc-editor.org/rfc/rfc1466.pdf"],"folder":"IETF/RFC-1466","files":{"txt":{"path":"standards/IETF/RFC-1466/RFC-1466.txt","sha256":"aaf8ee25e662eb0bbb55b52fe522e92f960db4799a520db324de318c6a29ef69"}},"tags":["nested-reference","unchanged"],"summary":"This document has been reviewed by the Federal Engineering Planning\n Group (FEPG) on behalf of the Federal Networking Council (FNC), the\n co-chairs of the Intercontinental Engineering Planning Group (IEPG),\n and the Reseaux IP Europeens (RIPE). There was general consensus by\n those groups to support the recommendations proposed in this document\n for management of the IP address space.","scope_keywords":["1466","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1481","folder":"IETF/RFC-1481","source":"IETF/RFC-1481/RFC-1481.txt","version":null},{"body":"IETF","designation":"RFC 1482","folder":"IETF/RFC-1482","source":"IETF/RFC-1482/RFC-1482.txt","version":null},{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1518","folder":"IETF/RFC-1518","source":"IETF/RFC-1518/RFC-1518.txt","version":null},{"body":"IETF","designation":"RFC 1520","folder":"IETF/RFC-1520","source":"IETF/RFC-1520/RFC-1520.txt","version":null},{"body":"IETF","designation":"RFC 1597","folder":"IETF/RFC-1597","source":"IETF/RFC-1597/RFC-1597.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1814","folder":"IETF/RFC-1814","source":"IETF/RFC-1814/RFC-1814.txt","version":null},{"body":"IETF","designation":"RFC 1918","folder":"IETF/RFC-1918","source":"IETF/RFC-1918/RFC-1918.txt","version":null},{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2073","folder":"IETF/RFC-2073","source":"IETF/RFC-2073/RFC-2073.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null}],"search_text":"IETF RFC 1466 This document has been reviewed by the Federal Engineering Planning\n Group (FEPG) on behalf of the Federal Networking Council (FNC), the\n co-chairs of the Intercontinental Engineering Planning Group (IEPG),\n and the Reseaux IP Europeens (RIPE). There was general consensus by\n those groups to support the recommendations proposed in this document\n for management of the IP address space. 1466 management qualified nested-reference unchanged"},{"id":"IETF RFC 1518","type":"specification","body":"IETF","designation":"RFC 1518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1518.txt","https://www.rfc-editor.org/rfc/rfc1518.pdf"],"folder":"IETF/RFC-1518","files":{"txt":{"path":"standards/IETF/RFC-1518/RFC-1518.txt","sha256":"a49e07d154454923880d0b93c9a8ea5864104c7252a96218be27ebc860a49f6d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1518 T.J. Watson Research Center, IBM Corp.\nCategory: Standards Track T. Li\n cisco Systems\n Editors\n September 1993\n\n An Architecture for IP Address Allocation with CIDR\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This paper provides an architecture and a plan for allocating IP\n addresses in the Internet. This architecture and the plan are\n intended to play an important role in steering the Internet towards\n the Address Assignment and Aggregating Strategy outlined in [1].\n\n The IP address space is a scarce shared r","scope_keywords":["1518","identification","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1519","folder":"IETF/RFC-1519","source":"IETF/RFC-1519/RFC-1519.txt","version":null},{"body":"IETF","designation":"RFC 1520","folder":"IETF/RFC-1520","source":"IETF/RFC-1520/RFC-1520.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1678","folder":"IETF/RFC-1678","source":"IETF/RFC-1678/RFC-1678.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1787","folder":"IETF/RFC-1787","source":"IETF/RFC-1787/RFC-1787.txt","version":null},{"body":"IETF","designation":"RFC 1817","folder":"IETF/RFC-1817","source":"IETF/RFC-1817/RFC-1817.txt","version":null},{"body":"IETF","designation":"RFC 1887","folder":"IETF/RFC-1887","source":"IETF/RFC-1887/RFC-1887.txt","version":null},{"body":"IETF","designation":"RFC 1918","folder":"IETF/RFC-1918","source":"IETF/RFC-1918/RFC-1918.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1518 Network Working Group Y. Rekhter\nRequest for Comments: 1518 T.J. Watson Research Center, IBM Corp.\nCategory: Standards Track T. Li\n cisco Systems\n Editors\n September 1993\n\n An Architecture for IP Address Allocation with CIDR\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This paper provides an architecture and a plan for allocating IP\n addresses in the Internet. This architecture and the plan are\n intended to play an important role in steering the Internet towards\n the Address Assignment and Aggregating Strategy outlined in [1].\n\n The IP address space is a scarce shared r 1518 identification policy registered nested-reference unchanged"},{"id":"IETF RFC 3330","type":"specification","body":"IETF","designation":"RFC 3330","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3330.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3330.txt","https://www.rfc-editor.org/rfc/rfc3330.pdf"],"folder":"IETF/RFC-3330","files":{"txt":{"path":"standards/IETF/RFC-3330/RFC-3330.txt","sha256":"9964b3f5152aac934c926117ec8ce0560cb3ef99a0ab804a2362dd1d47c0d1f1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the global and other specialized IPv4 address\n blocks that have been assigned by the Internet Assigned Numbers\n Authority (IANA). It does not address IPv4 address space assigned to\n operators and users through the Regional Internet Registries. It\n also does not address allocations or assignments of IPv6 addresses or\n autonomous system numbers.\n\n1. Introduction\n\n Throughout its entire history, the Internet has employed a central\n Internet Assigned Numbers Authority (IANA) responsible for the\n allocation and assignment of various identifiers needed for the\n operation of the Internet [RFC1174]. In the case of the IPv4 address\n space, the IANA allocates parts of the address space to Regional\n Internet Registries according to their established needs. These\n Regional Internet Registries are responsible for the assignment of\n IPv4 addresses to operators and users of the ","scope_keywords":["3330","http","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3704","folder":"IETF/RFC-3704","source":"IETF/RFC-3704/RFC-3704.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5635","folder":"IETF/RFC-5635","source":"IETF/RFC-5635/RFC-5635.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null}],"search_text":"IETF RFC 3330 This document describes the global and other specialized IPv4 address\n blocks that have been assigned by the Internet Assigned Numbers\n Authority (IANA). It does not address IPv4 address space assigned to\n operators and users through the Regional Internet Registries. It\n also does not address allocations or assignments of IPv6 addresses or\n autonomous system numbers.\n\n1. Introduction\n\n Throughout its entire history, the Internet has employed a central\n Internet Assigned Numbers Authority (IANA) responsible for the\n allocation and assignment of various identifiers needed for the\n operation of the Internet [RFC1174]. In the case of the IPv4 address\n space, the IANA allocates parts of the address space to Regional\n Internet Registries according to their established needs. These\n Regional Internet Registries are responsible for the assignment of\n IPv4 addresses to operators and users of the  3330 http subject nested-reference unchanged"},{"id":"IETF RFC 1463","type":"specification","body":"IETF","designation":"RFC 1463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1463.txt","https://www.rfc-editor.org/rfc/rfc1463.pdf"],"folder":"IETF/RFC-1463","files":{"txt":{"path":"standards/IETF/RFC-1463/RFC-1463.txt","sha256":"66e10e4915efa13887a52fb3a93299990f60c211c47413e3fc3a7c5fd6e02be4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Hoffman\nRequest for Comments: 1463 Merit Network, Inc.\nFYI: 19 L. Jackson\n NASA\n May 1993\n\n FYI on Introducing the Internet--\n A Short Bibliography of Introductory Internetworking Readings\n for the Network Novice\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This bibliography offers a short list of recent information resources\n that will help the network novice become familiar with the Internet,\n including its associated networks, resources, protocols, and history.\n This FYI RFC includes references to free sources of information\n available on-line as well as traditional publications. A short\n section at the end includes information for accessing the on-line\n files. This FYI is intentionally brief so it can be easily used as a\n handou","scope_keywords":["1463","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1462","folder":"IETF/RFC-1462","source":"IETF/RFC-1462/RFC-1462.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null}],"search_text":"IETF RFC 1463 Network Working Group E. Hoffman\nRequest for Comments: 1463 Merit Network, Inc.\nFYI: 19 L. Jackson\n NASA\n May 1993\n\n FYI on Introducing the Internet--\n A Short Bibliography of Introductory Internetworking Readings\n for the Network Novice\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This bibliography offers a short list of recent information resources\n that will help the network novice become familiar with the Internet,\n including its associated networks, resources, protocols, and history.\n This FYI RFC includes references to free sources of information\n available on-line as well as traditional publications. A short\n section at the end includes information for accessing the on-line\n files. This FYI is intentionally brief so it can be easily used as a\n handou 1463 risk nested-reference unchanged"},{"id":"IETF RFC 1732","type":"specification","body":"IETF","designation":"RFC 1732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1732.txt","https://www.rfc-editor.org/rfc/rfc1732.pdf"],"folder":"IETF/RFC-1732","files":{"txt":{"path":"standards/IETF/RFC-1732/RFC-1732.txt","sha256":"d6f38c870a1e412401570ec51b684f3f2c17229093cd93df1fbeb11c523be1c2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 1732 University of Washington\nCategory: Informational December 1994\n\n IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This is a summary of hints and recommendations to enable an IMAP4\n implementation to interoperate with implementations that conform to\n earlier specifications. None of these hints and recommendations are\n required by the IMAP4 specification; implementors must decide for\n themselves whether they want their implementation to fail if it\n encounters old software.\n\n IMAP4 has been designed to be upwards compatible with earlier\n specifications. For the most part, IMAP4 facilities that were not in\n earlier specifications should be ","scope_keywords":["1732","key","policy","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2061","folder":"IETF/RFC-2061","source":"IETF/RFC-2061/RFC-2061.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1732 Network Working Group M. Crispin\nRequest for Comments: 1732 University of Washington\nCategory: Informational December 1994\n\n IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This is a summary of hints and recommendations to enable an IMAP4\n implementation to interoperate with implementations that conform to\n earlier specifications. None of these hints and recommendations are\n required by the IMAP4 specification; implementors must decide for\n themselves whether they want their implementation to fail if it\n encounters old software.\n\n IMAP4 has been designed to be upwards compatible with earlier\n specifications. For the most part, IMAP4 facilities that were not in\n earlier specifications should be  1732 key policy preservation nested-reference unchanged"},{"id":"IETF RFC 2062","type":"specification","body":"IETF","designation":"RFC 2062","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2062.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2062.txt","https://www.rfc-editor.org/rfc/rfc2062.pdf"],"folder":"IETF/RFC-2062","files":{"txt":{"path":"standards/IETF/RFC-2062/RFC-2062.txt","sha256":"825733f2aaf7423a4bee18dc566e17a8c8e425abb6f1ddee279b6b8f149a1364"}},"tags":["nested-reference","unchanged"],"summary":"This document describes obsolete syntax which may be encountered by\n IMAP4 implementations which deal with older versions of the Internet\n Mail Access Protocol. IMAP4 implementations MAY implement this\n syntax in order to maximize interoperability with older\n implementations.\n\n This document repeats information from earlier documents, most\n notably RFC 1176 and RFC 1730.\n\nObsolete Commands and Fetch Data Items\n\n The following commands are OBSOLETE. It is NOT required to support\n any of these commands or fetch data items in new server\n implementations. These commands are documented here for the benefit\n of implementors who may wish to support them for compatibility with\n old client implementations.\n\n The section headings of these commands are intended to correspond\n with where they would be located in the main document if they were\n not obsoleted.","scope_keywords":["2062","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2062 This document describes obsolete syntax which may be encountered by\n IMAP4 implementations which deal with older versions of the Internet\n Mail Access Protocol. IMAP4 implementations MAY implement this\n syntax in order to maximize interoperability with older\n implementations.\n\n This document repeats information from earlier documents, most\n notably RFC 1176 and RFC 1730.\n\nObsolete Commands and Fetch Data Items\n\n The following commands are OBSOLETE. It is NOT required to support\n any of these commands or fetch data items in new server\n implementations. These commands are documented here for the benefit\n of implementors who may wish to support them for compatibility with\n old client implementations.\n\n The section headings of these commands are intended to correspond\n with where they would be located in the main document if they were\n not obsoleted. 2062 path nested-reference unchanged"},{"id":"IETF RFC 1179","type":"specification","body":"IETF","designation":"RFC 1179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1179.txt","https://www.rfc-editor.org/rfc/rfc1179.pdf"],"folder":"IETF/RFC-1179","files":{"txt":{"path":"standards/IETF/RFC-1179/RFC-1179.txt","sha256":"62a35a81e20b937200b1848126a382d7b3db23c557683612f85fb4517092f7d0"}},"tags":["nested-reference","unchanged"],"summary":"Network Printing Working Group L. McLaughlin III, Editor\nRequest for Comments: 1179 The Wollongong Group\n August 1990\n\n Line Printer Daemon Protocol\n\nStatus of this Memo\n\n This RFC describes an existing print server protocol widely used on\n the Internet for communicating between line printer daemons (both\n clients and servers). This memo is for informational purposes only,\n and does not specify an Internet standard. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n The Berkeley versions of the Unix(tm) operating system provide line\n printer spooling with a collection of programs: lpr (assign to\n queue), lpq (display the queue), lprm (remove from queue), and lpc\n (control the queue). These programs interact with an autonomous\n process called t","scope_keywords":["1179"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null}],"search_text":"IETF RFC 1179 Network Printing Working Group L. McLaughlin III, Editor\nRequest for Comments: 1179 The Wollongong Group\n August 1990\n\n Line Printer Daemon Protocol\n\nStatus of this Memo\n\n This RFC describes an existing print server protocol widely used on\n the Internet for communicating between line printer daemons (both\n clients and servers). This memo is for informational purposes only,\n and does not specify an Internet standard. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n The Berkeley versions of the Unix(tm) operating system provide line\n printer spooling with a collection of programs: lpr (assign to\n queue), lpq (display the queue), lprm (remove from queue), and lpc\n (control the queue). These programs interact with an autonomous\n process called t 1179 nested-reference unchanged"},{"id":"IETF RFC 2567","type":"specification","body":"IETF","designation":"RFC 2567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2567.txt","https://www.rfc-editor.org/rfc/rfc2567.pdf"],"folder":"IETF/RFC-2567","files":{"txt":{"path":"standards/IETF/RFC-2567/RFC-2567.txt","sha256":"ae9754fff28af789d7be879c1affb8e59356cf286f1afadf82dd5c9cce63af46"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document takes a broad\n look at distributed printing functionality, and it enumerates real-\n life scenarios that help to clarify the features that need to be\n included in a printing protocol for the Internet. It identifies\n requirements for three types of users: end users, operators, and\n\nWright Experimental [Page 1]\n\f\nRFC 2567 Internet Printing Design Goals April 1999\n\n administrators. The design goals document calls out a subset of end\n user requirements that are satisfied in IPP/1.0. Operator and\n administrator requirements are out of scope for version 1.0.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Pr","scope_keywords":["2567","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2567 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document takes a broad\n look at distributed printing functionality, and it enumerates real-\n life scenarios that help to clarify the features that need to be\n included in a printing protocol for the Internet. It identifies\n requirements for three types of users: end users, operators, and\n\nWright Experimental [Page 1]\n\f\nRFC 2567 Internet Printing Design Goals April 1999\n\n administrators. The design goals document calls out a subset of end\n user requirements that are satisfied in IPP/1.0. Operator and\n administrator requirements are out of scope for version 1.0.\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Pr 2567 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 2569","type":"specification","body":"IETF","designation":"RFC 2569","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2569.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2569.txt","https://www.rfc-editor.org/rfc/rfc2569.pdf"],"folder":"IETF/RFC-2569","files":{"txt":{"path":"standards/IETF/RFC-2569/RFC-2569.txt","sha256":"389a90b5876caaa3c7c58347ea2112d7a1ec4d55a2fc4af65211b210b743d3f3"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document gives some\n advice to implementers of gateways between IPP and LPD (Line Printer\n Daemon). This document describes the mapping between (1) the commands\n and operands of the 'Line Printer Daemon (LPD) Protocol' specified in\n RFC 1179 and (2) the operations, operation attributes and job\n template attributes of the Internet Printing Protocol/1.0 (IPP). One\n of the purposes of this document is to compare the functionality of\n the two protocols. Another purpose is to facilitate implementation\n of gateways between LPD and IPP.\n\n WARNING: RFC 1179 was not on the IETF standards track. While RFC\n 1179 was intended to record existing practice, ","scope_keywords":["2569","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2569 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document gives some\n advice to implementers of gateways between IPP and LPD (Line Printer\n Daemon). This document describes the mapping between (1) the commands\n and operands of the 'Line Printer Daemon (LPD) Protocol' specified in\n RFC 1179 and (2) the operations, operation attributes and job\n template attributes of the Internet Printing Protocol/1.0 (IPP). One\n of the purposes of this document is to compare the functionality of\n the two protocols. Another purpose is to facilitate implementation\n of gateways between LPD and IPP.\n\n WARNING: RFC 1179 was not on the IETF standards track. While RFC\n 1179 was intended to record existing practice,  2569 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 1713","type":"specification","body":"IETF","designation":"RFC 1713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1713.txt","https://www.rfc-editor.org/rfc/rfc1713.pdf"],"folder":"IETF/RFC-1713","files":{"txt":{"path":"standards/IETF/RFC-1713/RFC-1713.txt","sha256":"2ce6a460c087aae44ea254e90ea6c0ed272c5da409ecbc1777f20545ffd5cd1b"}},"tags":["nested-reference","unchanged"],"summary":"Although widely used (and most of the times unnoticed), DNS (Domain\n Name System) is too much overlooked, in the sense that people,\n especially administrators, tend to ignore possible anomalies as long\n as applications that need name-to-address mapping continue to work.\n This document presents some tools available for domain administrators\n to detect and correct those anomalies.\n\n1. Introduction\n\n Today more than 3,800,000 computers are inter-connected in a global\n Internet [1], comprising several millions of end-users, able to reach\n any of those machines just by naming it. This facility is possible\n thanks to the world widest distributed database, the Domain Name\n System, used to provide distributed applications various services,\n the most notable one being translating names into IP addresses and\n vice-versa. This happens when you do an FTP or Telnet, when your\n gopher client follows a","scope_keywords":["1713","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 1713 Although widely used (and most of the times unnoticed), DNS (Domain\n Name System) is too much overlooked, in the sense that people,\n especially administrators, tend to ignore possible anomalies as long\n as applications that need name-to-address mapping continue to work.\n This document presents some tools available for domain administrators\n to detect and correct those anomalies.\n\n1. Introduction\n\n Today more than 3,800,000 computers are inter-connected in a global\n Internet [1], comprising several millions of end-users, able to reach\n any of those machines just by naming it. This facility is possible\n thanks to the world widest distributed database, the Domain Name\n System, used to provide distributed applications various services,\n the most notable one being translating names into IP addresses and\n vice-versa. This happens when you do an FTP or Telnet, when your\n gopher client follows a 1713 subject nested-reference unchanged"},{"id":"IETF RFC 1186","type":"specification","body":"IETF","designation":"RFC 1186","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1186.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1186.txt","https://www.rfc-editor.org/rfc/rfc1186.pdf"],"folder":"IETF/RFC-1186","files":{"txt":{"path":"standards/IETF/RFC-1186/RFC-1186.txt","sha256":"7282253aa787803b78cbfc117e5f17d1c6d335a87b4513bcd6fe3e4c54635378"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Rivest\nRequest for Comments: 1186 MIT Laboratory for Computer Science\n October 1990\n\n The MD4 Message Digest Algorithm\n\nStatus of this Memo\n\n This RFC is the specification of the MD4 Digest Algorithm. If you\n are going to implement MD4, it is suggested you do it this way. This\n memo is for informational use and does not constitute a standard.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Abstract .................................................... 1\n 2. Terminology and Notation .................................... 2\n 3. MD4 Algorithm Description ................................... 2\n 4. Extensions .................................................. 6\n 5. Summary ..................................................... 7\n 6. Acknowledgements ............................................ 7\n APPENDIX - Reference Implementation ........................","scope_keywords":["1186","algorithm","key","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1320","folder":"IETF/RFC-1320","source":"IETF/RFC-1320/RFC-1320.txt","version":null}],"search_text":"IETF RFC 1186 Network Working Group R. Rivest\nRequest for Comments: 1186 MIT Laboratory for Computer Science\n October 1990\n\n The MD4 Message Digest Algorithm\n\nStatus of this Memo\n\n This RFC is the specification of the MD4 Digest Algorithm. If you\n are going to implement MD4, it is suggested you do it this way. This\n memo is for informational use and does not constitute a standard.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Abstract .................................................... 1\n 2. Terminology and Notation .................................... 2\n 3. MD4 Algorithm Description ................................... 2\n 4. Extensions .................................................. 6\n 5. Summary ..................................................... 7\n 6. Acknowledgements ............................................ 7\n APPENDIX - Reference Implementation ........................ 1186 algorithm key presentation signature nested-reference unchanged"},{"id":"IETF RFC 1320","type":"specification","body":"IETF","designation":"RFC 1320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1320.txt","https://www.rfc-editor.org/rfc/rfc1320.pdf"],"folder":"IETF/RFC-1320","files":{"txt":{"path":"standards/IETF/RFC-1320/RFC-1320.txt","sha256":"f727b15e19ab8ac5036ab7921476e8d8644512190ade32a2e0a2fb9d8a2421c7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Rivest\nRequest for Comments: 1320 MIT Laboratory for Computer Science\nObsoletes: RFC 1186 and RSA Data Security, Inc.\n April 1992\n\n The MD4 Message-Digest Algorithm\n\nStatus of thie Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n We would like to thank Don Coppersmith, Burt Kaliski, Ralph Merkle,\n and Noam Nisan for numerous helpful comments and suggestions.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD4 Algorithm Description 2\n 4. Summary 6\n References 6\n APPENDIX A - Reference Implementation 6\n Security Considerations 20\n Author's Address 20\n\n1. Executive Summary\n\n This document describes the MD4 message-digest algorithm [1]. The\n algorithm takes as input a message of arbitrary length and produces\n as output","scope_keywords":["1320","algorithm","key","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 1321","folder":"IETF/RFC-1321","source":"IETF/RFC-1321/RFC-1321.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 1510","folder":"IETF/RFC-1510","source":"IETF/RFC-1510/RFC-1510.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1760","folder":"IETF/RFC-1760","source":"IETF/RFC-1760/RFC-1760.txt","version":null},{"body":"IETF","designation":"RFC 1938","folder":"IETF/RFC-1938","source":"IETF/RFC-1938/RFC-1938.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2313","folder":"IETF/RFC-2313","source":"IETF/RFC-2313/RFC-2313.txt","version":null},{"body":"IETF","designation":"RFC 2433","folder":"IETF/RFC-2433","source":"IETF/RFC-2433/RFC-2433.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3174","folder":"IETF/RFC-3174","source":"IETF/RFC-3174/RFC-3174.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 1320 Network Working Group R. Rivest\nRequest for Comments: 1320 MIT Laboratory for Computer Science\nObsoletes: RFC 1186 and RSA Data Security, Inc.\n April 1992\n\n The MD4 Message-Digest Algorithm\n\nStatus of thie Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n We would like to thank Don Coppersmith, Burt Kaliski, Ralph Merkle,\n and Noam Nisan for numerous helpful comments and suggestions.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD4 Algorithm Description 2\n 4. Summary 6\n References 6\n APPENDIX A - Reference Implementation 6\n Security Considerations 20\n Author's Address 20\n\n1. Executive Summary\n\n This document describes the MD4 message-digest algorithm [1]. The\n algorithm takes as input a message of arbitrary length and produces\n as output 1320 algorithm key presentation signature nested-reference unchanged"},{"id":"IETF RFC 1633","type":"specification","body":"IETF","designation":"RFC 1633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1633.txt","https://www.rfc-editor.org/rfc/rfc1633.pdf"],"folder":"IETF/RFC-1633","files":{"pdf":{"path":"standards/IETF/RFC-1633/RFC-1633.pdf","sha256":"f36831637285bbc095454c927e51c2f88d95980daf54809416ab48c723249c87"},"txt":{"path":"standards/IETF/RFC-1633/RFC-1633.txt","sha256":"1e971f7d660ed406d3850c60d1bfa11366f87fc9d3aec35299cd2701ba3d9318"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses a proposed extension to the Internet architecture\n and protocols to provide integrated services, i.e., to support real-\n time as well as the current non-real-time service of IP. This\n extension is necessary to meet the growing need for real-time service\n for a variety of new applications, including teleconferencing, remote\n seminars, telescience, and distributed simulation.\n\n This memo represents the direct product of recent work by Dave Clark,\n Scott Shenker, Lixia Zhang, Deborah Estrin, Sugih Jamin, John\n Wroclawski, Shai Herzog, and Bob Braden, and indirectly draws upon\n the work of many others.","scope_keywords":["1633","algorithm","algorithms","delivery","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 2205","folder":"IETF/RFC-2205","source":"IETF/RFC-2205/RFC-2205.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null}],"search_text":"IETF RFC 1633 This memo discusses a proposed extension to the Internet architecture\n and protocols to provide integrated services, i.e., to support real-\n time as well as the current non-real-time service of IP. This\n extension is necessary to meet the growing need for real-time service\n for a variety of new applications, including teleconferencing, remote\n seminars, telescience, and distributed simulation.\n\n This memo represents the direct product of recent work by Dave Clark,\n Scott Shenker, Lixia Zhang, Deborah Estrin, Sugih Jamin, John\n Wroclawski, Shai Herzog, and Bob Braden, and indirectly draws upon\n the work of many others. 1633 algorithm algorithms delivery management subject nested-reference unchanged"},{"id":"IETF RFC 3171","type":"specification","body":"IETF","designation":"RFC 3171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3171.txt","https://www.rfc-editor.org/rfc/rfc3171.pdf"],"folder":"IETF/RFC-3171","files":{"txt":{"path":"standards/IETF/RFC-3171/RFC-3171.txt","sha256":"2c00c2b54b2ba5cb36d08209a6f6e749e29ed8e7e244fcb222e6fb33d71d7e51"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides guidance for the Internet Assigned Numbers\n Authority (IANA) in assigning IPv4 multicast addresses.\n\n1. Introduction\n\n The Internet Assigned Numbers Authority (IANA) (www.iana.org) is\n charged with allocating parameter values for fields in protocols\n which have been designed, created or are maintained by the Internet\n Engineering Task Force (IETF). RFC 2780 [RFC2780] provides the IANA\n guidance in the assignment of parameters for fields in newly\n developed protocols. This memo expands on section 4.4.2 of RFC 2780\n and attempts to codify existing IANA practice used in the assignment\n IPv4 multicast addresses.\n\n The terms \"Specification Required\", \"Expert Review\", \"IESG Approval\",\n \"IETF Consensus\", and \"Standards Action\", are used in this memo to\n refer to the processes described in [RFC2434]. The keywords MUST,\n MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SH","scope_keywords":["3171","algorithm","http","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null}],"search_text":"IETF RFC 3171 This memo provides guidance for the Internet Assigned Numbers\n Authority (IANA) in assigning IPv4 multicast addresses.\n\n1. Introduction\n\n The Internet Assigned Numbers Authority (IANA) (www.iana.org) is\n charged with allocating parameter values for fields in protocols\n which have been designed, created or are maintained by the Internet\n Engineering Task Force (IETF). RFC 2780 [RFC2780] provides the IANA\n guidance in the assignment of parameters for fields in newly\n developed protocols. This memo expands on section 4.4.2 of RFC 2780\n and attempts to codify existing IANA practice used in the assignment\n IPv4 multicast addresses.\n\n The terms \"Specification Required\", \"Expert Review\", \"IESG Approval\",\n \"IETF Consensus\", and \"Standards Action\", are used in this memo to\n refer to the processes described in [RFC2434]. The keywords MUST,\n MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SH 3171 algorithm http key policy nested-reference unchanged"},{"id":"IETF RFC 1435","type":"specification","body":"IETF","designation":"RFC 1435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1435.txt","https://www.rfc-editor.org/rfc/rfc1435.pdf"],"folder":"IETF/RFC-1435","files":{"txt":{"path":"standards/IETF/RFC-1435/RFC-1435.txt","sha256":"5ddf259777ce190caf83862f6a07a27adfee8906bbf9786f229e8286417e6df2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Knowles\nRequest for Comments: 1435 ftp Software\n March 1993\n\n IESG Advice from Experience with Path MTU Discovery\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n In the course of reviewing the MTU Discovery protocol for possible\n elevation to Draft Standard, a specific operational problem was\n uncovered. The problem results from the optional suppression of ICMP\n messages implemented in some routers. This memo outlines a\n modification to this practice to allow the correct functioning of MTU\n Discovery.\n\nAdvice on the Deployment of Path MTU Discovery Protocol\n\n While reviewing the Path MTU Discovery Protocol for Draft Standard\n [RFC1191], the Internet Engineering Steering Group (IESG) became\n aware from the reports of various implementor","scope_keywords":["1435","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null}],"search_text":"IETF RFC 1435 Network Working Group S. Knowles\nRequest for Comments: 1435 ftp Software\n March 1993\n\n IESG Advice from Experience with Path MTU Discovery\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n In the course of reviewing the MTU Discovery protocol for possible\n elevation to Draft Standard, a specific operational problem was\n uncovered. The problem results from the optional suppression of ICMP\n messages implemented in some routers. This memo outlines a\n modification to this practice to allow the correct functioning of MTU\n Discovery.\n\nAdvice on the Deployment of Path MTU Discovery Protocol\n\n While reviewing the Path MTU Discovery Protocol for Draft Standard\n [RFC1191], the Internet Engineering Steering Group (IESG) became\n aware from the reports of various implementor 1435 path nested-reference unchanged"},{"id":"IETF RFC 1853","type":"specification","body":"IETF","designation":"RFC 1853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1853.txt","https://www.rfc-editor.org/rfc/rfc1853.pdf"],"folder":"IETF/RFC-1853","files":{"txt":{"path":"standards/IETF/RFC-1853/RFC-1853.txt","sha256":"9d8d5cda3a7add3723900c1db41b32ce6f0e2def44ea4fb44c9a1cdc77b70ec8"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses implementation techniques for using IP\n Protocol/Payload number 4 Encapsulation for tunneling with IP\n Security and other protocols.","scope_keywords":["1853","identification","management","path","policies","policy","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null}],"search_text":"IETF RFC 1853 This document discusses implementation techniques for using IP\n Protocol/Payload number 4 Encapsulation for tunneling with IP\n Security and other protocols. 1853 identification management path policies policy timestamp nested-reference unchanged"},{"id":"IETF RFC 1883","type":"specification","body":"IETF","designation":"RFC 1883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1883.txt","https://www.rfc-editor.org/rfc/rfc1883.pdf"],"folder":"IETF/RFC-1883","files":{"txt":{"path":"standards/IETF/RFC-1883/RFC-1883.txt","sha256":"c6fef2009d448aa8f902f854b21597cc533a73ec4a451ec927ff3696b0d50895"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 6 of the Internet Protocol (IPv6),\n also sometimes referred to as IP Next Generation or IPng.\n\nDeering & Hinden Standards Track [Page 1]\n\f\nRFC 1883 IPv6 Specification December 1995","scope_keywords":["1883","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1887","folder":"IETF/RFC-1887","source":"IETF/RFC-1887/RFC-1887.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 1924","folder":"IETF/RFC-1924","source":"IETF/RFC-1924/RFC-1924.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 1972","folder":"IETF/RFC-1972","source":"IETF/RFC-1972/RFC-1972.txt","version":null},{"body":"IETF","designation":"RFC 1981","folder":"IETF/RFC-1981","source":"IETF/RFC-1981/RFC-1981.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2133","folder":"IETF/RFC-2133","source":"IETF/RFC-2133/RFC-2133.txt","version":null},{"body":"IETF","designation":"RFC 2147","folder":"IETF/RFC-2147","source":"IETF/RFC-2147/RFC-2147.txt","version":null},{"body":"IETF","designation":"RFC 2292","folder":"IETF/RFC-2292","source":"IETF/RFC-2292/RFC-2292.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 1883 This document specifies version 6 of the Internet Protocol (IPv6),\n also sometimes referred to as IP Next Generation or IPng.\n\nDeering & Hinden Standards Track [Page 1]\n\f\nRFC 1883 IPv6 Specification December 1995 1883 authentication path nested-reference unchanged"},{"id":"IETF RFC 1940","type":"specification","body":"IETF","designation":"RFC 1940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1940.txt","https://www.rfc-editor.org/rfc/rfc1940.pdf"],"folder":"IETF/RFC-1940","files":{"txt":{"path":"standards/IETF/RFC-1940/RFC-1940.txt","sha256":"4852d48c38731419179e35b35ca0f054a9165ac6271132df59eb16e776aa6f5c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Estrin\nRequest for Comments: 1940 USC\nCategory: Informational T. Li\n Y. Rekhter\n cisco Systems\n K. Varadhan\n D. Zappala\n USC\n May 1996\n\n Source Demand Routing:\n Packet Format and Forwarding Specification (Version 1).\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Overview\n\n The purpose of SDRP is to support source-initiated selection of\n routes to complement the route selection provided by existing routing\n protocols for both inter-domain and intra-domain routes. This\n document refers to such source-initiated routes as \"SDRP routes\".\n This document describes the packet format and forwarding procedure\n for SDRP. It also describes procedures for ascertaining feasibility\n of SDRP routes. Other components not described here are","scope_keywords":["1940","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1940 Network Working Group D. Estrin\nRequest for Comments: 1940 USC\nCategory: Informational T. Li\n Y. Rekhter\n cisco Systems\n K. Varadhan\n D. Zappala\n USC\n May 1996\n\n Source Demand Routing:\n Packet Format and Forwarding Specification (Version 1).\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Overview\n\n The purpose of SDRP is to support source-initiated selection of\n routes to complement the route selection provided by existing routing\n protocols for both inter-domain and intra-domain routes. This\n document refers to such source-initiated routes as \"SDRP routes\".\n This document describes the packet format and forwarding procedure\n for SDRP. It also describes procedures for ascertaining feasibility\n of SDRP routes. Other components not described here are 1940 management path nested-reference unchanged"},{"id":"IETF RFC 2003","type":"specification","body":"IETF","designation":"RFC 2003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2003.txt","https://www.rfc-editor.org/rfc/rfc2003.pdf"],"folder":"IETF/RFC-2003","files":{"txt":{"path":"standards/IETF/RFC-2003/RFC-2003.txt","sha256":"f7d1e7c3bd69741088f21596adf4b77330342deb4e47f5f0bf1840d829e199c5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram.\n Encapsulation is suggested as a means to alter the normal IP routing\n for datagrams, by delivering them to an intermediate destination that\n would otherwise not be selected by the (network part of the) IP\n Destination Address field in the original IP header. Encapsulation\n may serve a variety of purposes, such as delivery of a datagram to a\n mobile node using Mobile IP.\n\n1. Introduction\n\n This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram.\n Encapsulation is suggested as a means to alter the normal IP routing\n for datagrams, by delivering them to an intermediate destination that\n would otherwise not be selected based on the (network part of the) IP\n Destination Address field in the original IP heade","scope_keywords":["2003","attribute","attributes","authentication","delivery","identification","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2004","folder":"IETF/RFC-2004","source":"IETF/RFC-2004/RFC-2004.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 2003 This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram.\n Encapsulation is suggested as a means to alter the normal IP routing\n for datagrams, by delivering them to an intermediate destination that\n would otherwise not be selected by the (network part of the) IP\n Destination Address field in the original IP header. Encapsulation\n may serve a variety of purposes, such as delivery of a datagram to a\n mobile node using Mobile IP.\n\n1. Introduction\n\n This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram.\n Encapsulation is suggested as a means to alter the normal IP routing\n for datagrams, by delivering them to an intermediate destination that\n would otherwise not be selected based on the (network part of the) IP\n Destination Address field in the original IP heade 2003 attribute attributes authentication delivery identification policy nested-reference unchanged"},{"id":"IETF RFC 2004","type":"specification","body":"IETF","designation":"RFC 2004","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2004.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2004.txt","https://www.rfc-editor.org/rfc/rfc2004.pdf"],"folder":"IETF/RFC-2004","files":{"txt":{"path":"standards/IETF/RFC-2004/RFC-2004.txt","sha256":"04510e6668bdb95b6a84cd45f5431709893d1b45bcfb94e24d01f74fd066c155"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Perkins\nRequest for Comments: 2004 IBM\nCategory: Standards Track October 1996\n\n Minimal Encapsulation within IP\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram, with less\n overhead than \"conventional\" IP encapsulation that adds a second IP\n header to each encapsulated datagram. Encapsulation is suggested as\n a means to alter the normal IP routing for datagrams, by delivering\n them to an intermediate destination that would o","scope_keywords":["2004","attribute","attributes","delivery","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 2004 Network Working Group C. Perkins\nRequest for Comments: 2004 IBM\nCategory: Standards Track October 1996\n\n Minimal Encapsulation within IP\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a method by which an IP datagram may be\n encapsulated (carried as payload) within an IP datagram, with less\n overhead than \"conventional\" IP encapsulation that adds a second IP\n header to each encapsulated datagram. Encapsulation is suggested as\n a means to alter the normal IP routing for datagrams, by delivering\n them to an intermediate destination that would o 2004 attribute attributes delivery policy nested-reference unchanged"},{"id":"IETF RFC 2343","type":"specification","body":"IETF","designation":"RFC 2343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2343.txt","https://www.rfc-editor.org/rfc/rfc2343.pdf"],"folder":"IETF/RFC-2343","files":{"txt":{"path":"standards/IETF/RFC-2343/RFC-2343.txt","sha256":"48d8ed54118dcaf04c06f9a6921484dc01f42a6a3461fb39db7ce9b452b4e3fc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a payload type for bundled, MPEG-2 encoded\n video and audio data that may be used with RTP, version 2. Bundling\n has some advantages for this payload type particularly when it is\n used for video-on-demand applications. This payload type may be used\n when its advantages are important enough to sacrifice the modularity\n of having separate audio and video streams.\n\n1. Introduction\n\n This document describes a bundled packetization scheme for MPEG-2\n encoded audio and video streams using the Real-time Transport\n Protocol (RTP), version 2 [1].\n\n The MPEG-2 International standard consists of three layers: audio,\n video and systems [2]. The audio and the video layers define the\n syntax and semantics of the corresponding \"elementary streams.\" The\n systems layer supports synchronization and interleaving of multiple\n compressed streams, buffer initialization and management, ","scope_keywords":["2343","identification","management","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2343 This document describes a payload type for bundled, MPEG-2 encoded\n video and audio data that may be used with RTP, version 2. Bundling\n has some advantages for this payload type particularly when it is\n used for video-on-demand applications. This payload type may be used\n when its advantages are important enough to sacrifice the modularity\n of having separate audio and video streams.\n\n1. Introduction\n\n This document describes a bundled packetization scheme for MPEG-2\n encoded audio and video streams using the Real-time Transport\n Protocol (RTP), version 2 [1].\n\n The MPEG-2 International standard consists of three layers: audio,\n video and systems [2]. The audio and the video layers define the\n syntax and semantics of the corresponding \"elementary streams.\" The\n systems layer supports synchronization and interleaving of multiple\n compressed streams, buffer initialization and management,  2343 identification management path timestamp nested-reference unchanged"},{"id":"IETF RFC 2431","type":"specification","body":"IETF","designation":"RFC 2431","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2431.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2431.txt","https://www.rfc-editor.org/rfc/rfc2431.pdf"],"folder":"IETF/RFC-2431","files":{"txt":{"path":"standards/IETF/RFC-2431/RFC-2431.txt","sha256":"eb64527a4f805d3669d1a543494a3f3d56ec54c1d893240eb52f15a7fb702ee7"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the RTP payload format for encapsulating ITU\n Recommendation BT.656-3 video streams in the Real-Time Transport\n Protocol (RTP). Each RTP packet contains all or a portion of one\n scan line as defined by ITU Recommendation BT.601-5, and includes\n fragmentation, decoding and positioning information.\n\n1. Introduction\n\n This document describes a scheme to packetize uncompressed, studio-\n quality video streams as defined by BT.656 for transport using RTP\n [1]. A BT.656 video stream is defined by ITU-R Recommendation\n BT.656-3 [2], as a means of interconnecting digital television\n equipment operating on the 525-line or 625-line standards, and\n complying with the 4:2:2 encoding parameters as defined in ITU-R\n Recommendation BT.601-5 (formerly CCIR-601) [3], Part A.\n\n RTP is defined by the Internet Engineering Task Force (IETF) to\n provide end-to-end network transport func","scope_keywords":["2431","key","path","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2431 This document specifies the RTP payload format for encapsulating ITU\n Recommendation BT.656-3 video streams in the Real-Time Transport\n Protocol (RTP). Each RTP packet contains all or a portion of one\n scan line as defined by ITU Recommendation BT.601-5, and includes\n fragmentation, decoding and positioning information.\n\n1. Introduction\n\n This document describes a scheme to packetize uncompressed, studio-\n quality video streams as defined by BT.656 for transport using RTP\n [1]. A BT.656 video stream is defined by ITU-R Recommendation\n BT.656-3 [2], as a means of interconnecting digital television\n equipment operating on the 525-line or 625-line standards, and\n complying with the 4:2:2 encoding parameters as defined in ITU-R\n Recommendation BT.601-5 (formerly CCIR-601) [3], Part A.\n\n RTP is defined by the Internet Engineering Task Force (IETF) to\n provide end-to-end network transport func 2431 key path presentation profile nested-reference unchanged"},{"id":"IETF RFC 2740","type":"specification","body":"IETF","designation":"RFC 2740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2740.txt","https://www.rfc-editor.org/rfc/rfc2740.pdf"],"folder":"IETF/RFC-2740","files":{"txt":{"path":"standards/IETF/RFC-2740/RFC-2740.txt","sha256":"7a5a3c79db5e70fb328f571d68dbf9b6bdc12de1073a6b2585d9ba157a17b70f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the modifications to OSPF to support version\n 6 of the Internet Protocol (IPv6). The fundamental mechanisms of\n OSPF (flooding, DR election, area support, SPF calculations, etc.)\n remain unchanged. However, some changes have been necessary, either\n due to changes in protocol semantics between IPv4 and IPv6, or simply\n to handle the increased address size of IPv6.\n\n Changes between OSPF for IPv4 and this document include the\n following. Addressing semantics have been removed from OSPF packets\n and the basic LSAs. New LSAs have been created to carry IPv6\n addresses and prefixes. OSPF now runs on a per-link basis, instead of\n on a per-IP-subnet basis. Flooding scope for LSAs has been\n generalized. Authentication has been removed from the OSPF protocol\n itself, instead relying on IPv6's Authentication Header and\n Encapsulating Security Payload.\n\n Most packets in OSPF ","scope_keywords":["2740","authentication","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4222","folder":"IETF/RFC-4222","source":"IETF/RFC-4222/RFC-4222.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5243","folder":"IETF/RFC-5243","source":"IETF/RFC-5243/RFC-5243.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 2740 This document describes the modifications to OSPF to support version\n 6 of the Internet Protocol (IPv6). The fundamental mechanisms of\n OSPF (flooding, DR election, area support, SPF calculations, etc.)\n remain unchanged. However, some changes have been necessary, either\n due to changes in protocol semantics between IPv4 and IPv6, or simply\n to handle the increased address size of IPv6.\n\n Changes between OSPF for IPv4 and this document include the\n following. Addressing semantics have been removed from OSPF packets\n and the basic LSAs. New LSAs have been created to carry IPv6\n addresses and prefixes. OSPF now runs on a per-link basis, instead of\n on a per-IP-subnet basis. Flooding scope for LSAs has been\n generalized. Authentication has been removed from the OSPF protocol\n itself, instead relying on IPv6's Authentication Header and\n Encapsulating Security Payload.\n\n Most packets in OSPF  2740 authentication path presentation nested-reference unchanged"},{"id":"IETF RFC 2979","type":"specification","body":"IETF","designation":"RFC 2979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2979.txt","https://www.rfc-editor.org/rfc/rfc2979.pdf"],"folder":"IETF/RFC-2979","files":{"txt":{"path":"standards/IETF/RFC-2979/RFC-2979.txt","sha256":"5a4aa2525b16f2dcb97da324d5c6257e9706d10946a855a6cdaa484717ff8650"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines behavioral characteristics of and interoperability\n requirements for Internet firewalls. While most of these things may\n seem obvious, current firewall behavior is often either unspecified\n or underspecified and this lack of specificity often causes problems\n in practice. This requirement is intended to be a necessary first\n step in making the behavior of firewalls more consistent across\n implementations and in line with accepted IP protocol practices.\n\n1. Introduction\n\n The Internet is being used for an increasing number of mission\n critical applications. Because of this many sites find isolated\n secure intranets insufficient for their needs, even when those\n intranets are based on and use Internet protocols. Instead they find\n it necessary to provide direct communications paths between the\n sometimes hostile Internet and systems or networks which either deal\n with val","scope_keywords":["2979","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null}],"search_text":"IETF RFC 2979 This memo defines behavioral characteristics of and interoperability\n requirements for Internet firewalls. While most of these things may\n seem obvious, current firewall behavior is often either unspecified\n or underspecified and this lack of specificity often causes problems\n in practice. This requirement is intended to be a necessary first\n step in making the behavior of firewalls more consistent across\n implementations and in line with accepted IP protocol practices.\n\n1. Introduction\n\n The Internet is being used for an increasing number of mission\n critical applications. Because of this many sites find isolated\n secure intranets insufficient for their needs, even when those\n intranets are based on and use Internet protocols. Instead they find\n it necessary to provide direct communications paths between the\n sometimes hostile Internet and systems or networks which either deal\n with val 2979 http path nested-reference unchanged"},{"id":"IETF RFC 3032","type":"specification","body":"IETF","designation":"RFC 3032","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3032.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3032.txt","https://www.rfc-editor.org/rfc/rfc3032.pdf"],"folder":"IETF/RFC-3032","files":{"txt":{"path":"standards/IETF/RFC-3032/RFC-3032.txt","sha256":"c611103bf720c643a40e128159aabb1607eab97977d0f3483d468a620cd86180"}},"tags":["nested-reference","unchanged"],"summary":"\"Multi-Protocol Label Switching (MPLS)\" [1] requires a set of\n procedures for augmenting network layer packets with \"label stacks\",\n thereby turning them into \"labeled packets\". Routers which support\n MPLS are known as \"Label Switching Routers\", or \"LSRs\". In order to\n transmit a labeled packet on a particular data link, an LSR must\n support an encoding technique which, given a label stack and a\n network layer packet, produces a labeled packet. This document\n specifies the encoding to be used by an LSR in order to transmit\n labeled packets on Point-to-Point Protocol (PPP) data links, on LAN\n data links, and possibly on other data links as well. On some data\n links, the label at the top of the stack may be encoded in a\n different manner, but the techniques described here MUST be used to\n encode the remainder of the label stack. This document also\n specifies rules and procedures for proces","scope_keywords":["3032","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3038","folder":"IETF/RFC-3038","source":"IETF/RFC-3038/RFC-3038.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3429","folder":"IETF/RFC-3429","source":"IETF/RFC-3429/RFC-3429.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4182","folder":"IETF/RFC-4182","source":"IETF/RFC-4182/RFC-4182.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5331","folder":"IETF/RFC-5331","source":"IETF/RFC-5331/RFC-5331.txt","version":null},{"body":"IETF","designation":"RFC 5332","folder":"IETF/RFC-5332","source":"IETF/RFC-5332/RFC-5332.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null}],"search_text":"IETF RFC 3032 \"Multi-Protocol Label Switching (MPLS)\" [1] requires a set of\n procedures for augmenting network layer packets with \"label stacks\",\n thereby turning them into \"labeled packets\". Routers which support\n MPLS are known as \"Label Switching Routers\", or \"LSRs\". In order to\n transmit a labeled packet on a particular data link, an LSR must\n support an encoding technique which, given a label stack and a\n network layer packet, produces a labeled packet. This document\n specifies the encoding to be used by an LSR in order to transmit\n labeled packets on Point-to-Point Protocol (PPP) data links, on LAN\n data links, and possibly on other data links as well. On some data\n links, the label at the top of the stack may be encoded in a\n different manner, but the techniques described here MUST be used to\n encode the remainder of the label stack. This document also\n specifies rules and procedures for proces 3032 key path nested-reference unchanged"},{"id":"IETF RFC 3124","type":"specification","body":"IETF","designation":"RFC 3124","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3124.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3124.txt","https://www.rfc-editor.org/rfc/rfc3124.pdf"],"folder":"IETF/RFC-3124","files":{"txt":{"path":"standards/IETF/RFC-3124/RFC-3124.txt","sha256":"69bcac221cd40c58419199444cdad3355c1e79bea808e5d84aeec2b058c66fcc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Congestion Manager (CM), an end-system\n module that:\n\n (i) Enables an ensemble of multiple concurrent streams from a sender\n destined to the same receiver and sharing the same congestion\n properties to perform proper congestion avoidance and control, and\n\n (ii) Allows applications to easily adapt to network congestion.\n\n1. Conventions used in this document:\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [Bradner97].\n\n STREAM\n\n A group of packets that all share the same source and destination\n IP address, IP type-of-service, transport protocol, and source and\n destination transport-layer port numbers.\n\nBalakrishnan, et. al. Standards Track [Page 1]\n\f\nRFC 3124 The Congestion Manager June 2001\n\n MACROFLOW\n\n A group ","scope_keywords":["3124","algorithm","algorithms","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 3124 This document describes the Congestion Manager (CM), an end-system\n module that:\n\n (i) Enables an ensemble of multiple concurrent streams from a sender\n destined to the same receiver and sharing the same congestion\n properties to perform proper congestion avoidance and control, and\n\n (ii) Allows applications to easily adapt to network congestion.\n\n1. Conventions used in this document:\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [Bradner97].\n\n STREAM\n\n A group of packets that all share the same source and destination\n IP address, IP type-of-service, transport protocol, and source and\n destination transport-layer port numbers.\n\nBalakrishnan, et. al. Standards Track [Page 1]\n\f\nRFC 3124 The Congestion Manager June 2001\n\n MACROFLOW\n\n A group  3124 algorithm algorithms key management path subject nested-reference unchanged"},{"id":"IETF RFC 3148","type":"specification","body":"IETF","designation":"RFC 3148","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3148.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3148.txt","https://www.rfc-editor.org/rfc/rfc3148.pdf"],"folder":"IETF/RFC-3148","files":{"txt":{"path":"standards/IETF/RFC-3148/RFC-3148.txt","sha256":"8343f573a2495843ef34523c8f0dbd5ec1107ab3b75d2ab2ca8c8da9891906bc"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for standardizing multiple BTC\n (Bulk Transport Capacity) metrics that parallel the permitted\n transport diversity.\n\n1 Introduction\n\n Bulk Transport Capacity (BTC) is a measure of a network's ability to\n transfer significant quantities of data with a single congestion-\n aware transport connection (e.g., TCP). The intuitive definition of\n BTC is the expected long term average data rate (bits per second) of\n a single ideal TCP implementation over the path in question.\n However, there are many congestion control algorithms (and hence\n transport implementations) permitted by IETF standards. This\n diversity in transport algorithms creates a difficulty for\n standardizing BTC metrics because the allowed diversity is sufficient\n to lead to situations where different implementations will yield\n non-comparable measures -- and potentially fail the formal tests for\n","scope_keywords":["3148","algorithm","algorithms","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5136","folder":"IETF/RFC-5136","source":"IETF/RFC-5136/RFC-5136.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null}],"search_text":"IETF RFC 3148 This document defines a framework for standardizing multiple BTC\n (Bulk Transport Capacity) metrics that parallel the permitted\n transport diversity.\n\n1 Introduction\n\n Bulk Transport Capacity (BTC) is a measure of a network's ability to\n transfer significant quantities of data with a single congestion-\n aware transport connection (e.g., TCP). The intuitive definition of\n BTC is the expected long term average data rate (bits per second) of\n a single ideal TCP implementation over the path in question.\n However, there are many congestion control algorithms (and hence\n transport implementations) permitted by IETF standards. This\n diversity in transport algorithms creates a difficulty for\n standardizing BTC metrics because the allowed diversity is sufficient\n to lead to situations where different implementations will yield\n non-comparable measures -- and potentially fail the formal tests for\n 3148 algorithm algorithms key path nested-reference unchanged"},{"id":"IETF RFC 3209","type":"specification","body":"IETF","designation":"RFC 3209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3209.txt","https://www.rfc-editor.org/rfc/rfc3209.pdf"],"folder":"IETF/RFC-3209","files":{"txt":{"path":"standards/IETF/RFC-3209/RFC-3209.txt","sha256":"a2ebe64e44c276aa217589950f81c146d4f05a4016ac4a15b0fec7242e304159"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of RSVP (Resource Reservation\n Protocol), including all the necessary extensions, to establish\n label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching).\n Since the flow along an LSP is completely identified by the label\n applied at the ingress node of the path, these paths may be treated\n as tunnels. A key application of LSP tunnels is traffic engineering\n with MPLS as specified in RFC 2702.\n\n We propose several additional objects that extend RSVP, allowing the\n establishment of explicitly routed label switched paths using RSVP as\n a signaling protocol. The result is the instantiation of label-\n switched tunnels which can be automatically routed away from network\n failures, congestion, and bottlenecks.\n\nAwduche, et al. Standards Track [Page 1]\n\f\nRFC 3209 Extensions to RSVP for LSP Tunnels December 2001\n\nContents\n\n 1 Introduction ..............","scope_keywords":["3209","attribute","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3210","folder":"IETF/RFC-3210","source":"IETF/RFC-3210/RFC-3210.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3469","folder":"IETF/RFC-3469","source":"IETF/RFC-3469/RFC-3469.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3477","folder":"IETF/RFC-3477","source":"IETF/RFC-3477/RFC-3477.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3936","folder":"IETF/RFC-3936","source":"IETF/RFC-3936/RFC-3936.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 4090","folder":"IETF/RFC-4090","source":"IETF/RFC-4090/RFC-4090.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4657","folder":"IETF/RFC-4657","source":"IETF/RFC-4657/RFC-4657.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 3209 This document describes the use of RSVP (Resource Reservation\n Protocol), including all the necessary extensions, to establish\n label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching).\n Since the flow along an LSP is completely identified by the label\n applied at the ingress node of the path, these paths may be treated\n as tunnels. A key application of LSP tunnels is traffic engineering\n with MPLS as specified in RFC 2702.\n\n We propose several additional objects that extend RSVP, allowing the\n establishment of explicitly routed label switched paths using RSVP as\n a signaling protocol. The result is the instantiation of label-\n switched tunnels which can be automatically routed away from network\n failures, congestion, and bottlenecks.\n\nAwduche, et al. Standards Track [Page 1]\n\f\nRFC 3209 Extensions to RSVP for LSP Tunnels December 2001\n\nContents\n\n 1 Introduction .............. 3209 attribute key path nested-reference unchanged"},{"id":"IETF RFC 3723","type":"specification","body":"IETF","designation":"RFC 3723","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3723.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3723.txt","https://www.rfc-editor.org/rfc/rfc3723.pdf"],"folder":"IETF/RFC-3723","files":{"txt":{"path":"standards/IETF/RFC-3723/RFC-3723.txt","sha256":"b17a405774428e98142e76f23df539c35c204aaa8326967bf261cc45e9fe7696"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how to secure block storage and storage\n discovery protocols running over IP (Internet Protocol) using IPsec\n and IKE (Internet Key Exchange). Threat models and security\n protocols are developed for iSCSI (Internet Protocol Small Computer\n System Interface), iFCP (Internet Fibre Channel Storage Networking)\n and FCIP (Fibre Channel over TCP/IP), as well as the iSNS (Internet\n Storage Name Server) and SLPv2 (Service Location Protocol v2)\n discovery protocols. Performance issues and resource constraints are\n analyzed.","scope_keywords":["3723","authentication","encryption","key","keys","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4850","folder":"IETF/RFC-4850","source":"IETF/RFC-4850/RFC-4850.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 3723 This document discusses how to secure block storage and storage\n discovery protocols running over IP (Internet Protocol) using IPsec\n and IKE (Internet Key Exchange). Threat models and security\n protocols are developed for iSCSI (Internet Protocol Small Computer\n System Interface), iFCP (Internet Fibre Channel Storage Networking)\n and FCIP (Fibre Channel over TCP/IP), as well as the iSNS (Internet\n Storage Name Server) and SLPv2 (Service Location Protocol v2)\n discovery protocols. Performance issues and resource constraints are\n analyzed. 3723 authentication encryption key keys policies nested-reference unchanged"},{"id":"IETF RFC 3985","type":"specification","body":"IETF","designation":"RFC 3985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3985.txt","https://www.rfc-editor.org/rfc/rfc3985.pdf"],"folder":"IETF/RFC-3985","files":{"txt":{"path":"standards/IETF/RFC-3985/RFC-3985.txt","sha256":"89cd241d130532a1211da4f628ba39bbf974507826a9d840f4fa589813f45e21"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for Pseudo Wire Emulation\n Edge-to-Edge (PWE3). It discusses the emulation of services such as\n Frame Relay, ATM, Ethernet, TDM, and SONET/SDH over packet switched\n networks (PSNs) using IP or MPLS. It presents the architectural\n framework for pseudo wires (PWs), defines terminology, and specifies\n the various protocol elements and their functions.","scope_keywords":["3985","attribute","attributes","delivery","management","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4863","folder":"IETF/RFC-4863","source":"IETF/RFC-4863/RFC-4863.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 3985 This document describes an architecture for Pseudo Wire Emulation\n Edge-to-Edge (PWE3). It discusses the emulation of services such as\n Frame Relay, ATM, Ethernet, TDM, and SONET/SDH over packet switched\n networks (PSNs) using IP or MPLS. It presents the architectural\n framework for pseudo wires (PWs), defines terminology, and specifies\n the various protocol elements and their functions. 3985 attribute attributes delivery management path validation nested-reference unchanged"},{"id":"IETF RFC 3988","type":"specification","body":"IETF","designation":"RFC 3988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3988.txt","https://www.rfc-editor.org/rfc/rfc3988.pdf"],"folder":"IETF/RFC-3988","files":{"txt":{"path":"standards/IETF/RFC-3988/RFC-3988.txt","sha256":"1e4d7144d7368781ff4de5c718b0fcd1971396447daeeea50fde54b61d33078a"}},"tags":["nested-reference","unchanged"],"summary":"Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU)\n discovery requires that IP routers have knowledge of the MTU for each\n link to which they are connected. As currently specified, the Label\n Distribution Protocol (LDP) does not have the ability to signal the\n MTU for a Label Switched Path (LSP) to the ingress Label Switching\n Router (LSR). In the absence of this functionality, the MTU for each\n LSP must be statically configured by network operators or by\n equivalent off-line mechanisms.\n\n This document specifies experimental extensions to LDP in support of\n LSP MTU discovery.\n\n1. Introduction\n\n As currently specified in [2], the LDP protocol for MPLS does not\n support signalling of the MTU for LSPs to ingress LSRs. This\n functionality is essential to the proper functioning of RFC 1191 path\n MTU detection [3]. Without knowledge of the MTU for an LSP, edge\n LSRs may trans","scope_keywords":["3988","algorithm","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null}],"search_text":"IETF RFC 3988 Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU)\n discovery requires that IP routers have knowledge of the MTU for each\n link to which they are connected. As currently specified, the Label\n Distribution Protocol (LDP) does not have the ability to signal the\n MTU for a Label Switched Path (LSP) to the ingress Label Switching\n Router (LSR). In the absence of this functionality, the MTU for each\n LSP must be statically configured by network operators or by\n equivalent off-line mechanisms.\n\n This document specifies experimental extensions to LDP in support of\n LSP MTU discovery.\n\n1. Introduction\n\n As currently specified in [2], the LDP protocol for MPLS does not\n support signalling of the MTU for LSPs to ingress LSRs. This\n functionality is essential to the proper functioning of RFC 1191 path\n MTU detection [3]. Without knowledge of the MTU for an LSP, edge\n LSRs may trans 3988 algorithm key path nested-reference unchanged"},{"id":"IETF RFC 4023","type":"specification","body":"IETF","designation":"RFC 4023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4023.txt","https://www.rfc-editor.org/rfc/rfc4023.pdf"],"folder":"IETF/RFC-4023","files":{"txt":{"path":"standards/IETF/RFC-4023/RFC-4023.txt","sha256":"49132cc41b6b0527bb592daa51859b8f98e2c548f53340ee700aa46d51f2d979"}},"tags":["nested-reference","unchanged"],"summary":"Various applications of MPLS make use of label stacks with multiple\n entries. In some cases, it is possible to replace the top label of\n the stack with an IP-based encapsulation, thereby enabling the\n application to run over networks that do not have MPLS enabled in\n their core routers. This document specifies two IP-based\n encapsulations: MPLS-in-IP and MPLS-in-GRE (Generic Routing\n Encapsulation). Each of these is applicable in some circumstances.\n\nWorster, et al. Standards Track [Page 1]\n\f\nRFC 4023 Encapsulating MPLS in IP or GRE March 2005","scope_keywords":["4023","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5332","folder":"IETF/RFC-5332","source":"IETF/RFC-5332/RFC-5332.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null}],"search_text":"IETF RFC 4023 Various applications of MPLS make use of label stacks with multiple\n entries. In some cases, it is possible to replace the top label of\n the stack with an IP-based encapsulation, thereby enabling the\n application to run over networks that do not have MPLS enabled in\n their core routers. This document specifies two IP-based\n encapsulations: MPLS-in-IP and MPLS-in-GRE (Generic Routing\n Encapsulation). Each of these is applicable in some circumstances.\n\nWorster, et al. Standards Track [Page 1]\n\f\nRFC 4023 Encapsulating MPLS in IP or GRE March 2005 4023 key path nested-reference unchanged"},{"id":"IETF RFC 4213","type":"specification","body":"IETF","designation":"RFC 4213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4213.txt","https://www.rfc-editor.org/rfc/rfc4213.pdf"],"folder":"IETF/RFC-4213","files":{"txt":{"path":"standards/IETF/RFC-4213/RFC-4213.txt","sha256":"15128dc2d02188ca9e2e7d1341c56846e7b1030cc850edfbcacf5c2fc35dc1d9"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. Two mechanisms are specified,\n dual stack and configured tunneling. Dual stack implies providing\n complete implementations of both versions of the Internet Protocol\n (IPv4 and IPv6), and configured tunneling provides a means to carry\n IPv6 packets over unmodified IPv4 routing infrastructures.\n\n This document obsoletes RFC 2893.\n\nNordmark & Gilligan Standards Track [Page 1]\n\f\nRFC 4213 Basic IPv6 Transition Mechanisms October 2005","scope_keywords":["4213","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null}],"search_text":"IETF RFC 4213 This document specifies IPv4 compatibility mechanisms that can be\n implemented by IPv6 hosts and routers. Two mechanisms are specified,\n dual stack and configured tunneling. Dual stack implies providing\n complete implementations of both versions of the Internet Protocol\n (IPv4 and IPv6), and configured tunneling provides a means to carry\n IPv6 packets over unmodified IPv4 routing infrastructures.\n\n This document obsoletes RFC 2893.\n\nNordmark & Gilligan Standards Track [Page 1]\n\f\nRFC 4213 Basic IPv6 Transition Mechanisms October 2005 4213 key nested-reference unchanged"},{"id":"IETF RFC 4301","type":"specification","body":"IETF","designation":"RFC 4301","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4301.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4301.txt","https://www.rfc-editor.org/rfc/rfc4301.pdf"],"folder":"IETF/RFC-4301","files":{"txt":{"path":"standards/IETF/RFC-4301/RFC-4301.txt","sha256":"a2411e90515f59665e1059b1bb66d8123bd9e384ccfc8b7ccca65db85d5d7736"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an updated version of the \"Security\n Architecture for IP\", which is designed to provide security services\n for traffic at the IP layer. This document obsoletes RFC 2401\n (November 1998).\n\nDedication\n\n This document is dedicated to the memory of Charlie Lynn, a long-time\n senior colleague at BBN, who made very significant contributions to\n the IPsec documents.\n\nKent & Seo Standards Track [Page 1]\n\f\nRFC 4301 Security Architecture for IP December 2005","scope_keywords":["4301","algorithm","audit","authentication","authorization","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 4301 This document describes an updated version of the \"Security\n Architecture for IP\", which is designed to provide security services\n for traffic at the IP layer. This document obsoletes RFC 2401\n (November 1998).\n\nDedication\n\n This document is dedicated to the memory of Charlie Lynn, a long-time\n senior colleague at BBN, who made very significant contributions to\n the IPsec documents.\n\nKent & Seo Standards Track [Page 1]\n\f\nRFC 4301 Security Architecture for IP December 2005 4301 algorithm audit authentication authorization key management path policy nested-reference unchanged"},{"id":"IETF RFC 4340","type":"specification","body":"IETF","designation":"RFC 4340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4340.txt","https://www.rfc-editor.org/rfc/rfc4340.pdf"],"folder":"IETF/RFC-4340","files":{"txt":{"path":"standards/IETF/RFC-4340/RFC-4340.txt","sha256":"f5a3f2acb375a6383f94aca74f692dbdbc1b1c12da4587f63d75487aa4218b27"}},"tags":["nested-reference","unchanged"],"summary":"The Datagram Congestion Control Protocol (DCCP) is a transport\n protocol that provides bidirectional unicast connections of\n congestion-controlled unreliable datagrams. DCCP is suitable for\n applications that transfer fairly large amounts of data and that can\n benefit from control over the tradeoff between timeliness and\n reliability.","scope_keywords":["4340"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 4340 The Datagram Congestion Control Protocol (DCCP) is a transport\n protocol that provides bidirectional unicast connections of\n congestion-controlled unreliable datagrams. DCCP is suitable for\n applications that transfer fairly large amounts of data and that can\n benefit from control over the tradeoff between timeliness and\n reliability. 4340 nested-reference unchanged"},{"id":"IETF RFC 4623","type":"specification","body":"IETF","designation":"RFC 4623","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4623.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4623.txt","https://www.rfc-editor.org/rfc/rfc4623.pdf"],"folder":"IETF/RFC-4623","files":{"txt":{"path":"standards/IETF/RFC-4623/RFC-4623.txt","sha256":"49f7186f3a8b65a091ad734a9f6cfba7edd60e4bca70061745522c2d76f3009a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a generalized method of performing\n fragmentation for use by Pseudowire Emulation Edge-to-Edge (PWE3)\n protocols and services.\n\nMalis & Townsley Standards Track [Page 1]\n\f\nRFC 4623 PWE3 Fragmentation and Reassembly August 2006","scope_keywords":["4623","attribute","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null}],"search_text":"IETF RFC 4623 This document defines a generalized method of performing\n fragmentation for use by Pseudowire Emulation Edge-to-Edge (PWE3)\n protocols and services.\n\nMalis & Townsley Standards Track [Page 1]\n\f\nRFC 4623 PWE3 Fragmentation and Reassembly August 2006 4623 attribute management path nested-reference unchanged"},{"id":"IETF RFC 4782","type":"specification","body":"IETF","designation":"RFC 4782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4782.txt","https://www.rfc-editor.org/rfc/rfc4782.pdf"],"folder":"IETF/RFC-4782","files":{"txt":{"path":"standards/IETF/RFC-4782/RFC-4782.txt","sha256":"b97912d83baad8ef89549a3c98c74c7ea84faa7841372566a909dc6f522ed8c5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an optional Quick-Start mechanism for\n transport protocols, in cooperation with routers, to determine an\n allowed sending rate at the start and, at times, in the middle of a\n data transfer (e.g., after an idle period). While Quick-Start is\n designed to be used by a range of transport protocols, in this\n document we only specify its use with TCP. Quick-Start is designed\n to allow connections to use higher sending rates when there is\n significant unused bandwidth along the path, and the sender and all\n of the routers along the path approve the Quick-Start Request.\n\n This document describes many paths where Quick-Start Requests would\n not be approved. These paths include all paths containing routers,\n IP tunnels, MPLS paths, and the like that do not support Quick-\n Start. These paths also include paths with routers or middleboxes\n that drop packets containing IP opti","scope_keywords":["4782","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4782 This document specifies an optional Quick-Start mechanism for\n transport protocols, in cooperation with routers, to determine an\n allowed sending rate at the start and, at times, in the middle of a\n data transfer (e.g., after an idle period). While Quick-Start is\n designed to be used by a range of transport protocols, in this\n document we only specify its use with TCP. Quick-Start is designed\n to allow connections to use higher sending rates when there is\n significant unused bandwidth along the path, and the sender and all\n of the routers along the path approve the Quick-Start Request.\n\n This document describes many paths where Quick-Start Requests would\n not be approved. These paths include all paths containing routers,\n IP tunnels, MPLS paths, and the like that do not support Quick-\n Start. These paths also include paths with routers or middleboxes\n that drop packets containing IP opti 4782 path trust nested-reference unchanged"},{"id":"IETF RFC 5340","type":"specification","body":"IETF","designation":"RFC 5340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5340.txt","https://www.rfc-editor.org/rfc/rfc5340.pdf"],"folder":"IETF/RFC-5340","files":{"txt":{"path":"standards/IETF/RFC-5340/RFC-5340.txt","sha256":"ebd26855ec97df248b124eb87308ce9a737cc02767b18c8e8c883b3b1f15251c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the modifications to OSPF to support version\n 6 of the Internet Protocol (IPv6). The fundamental mechanisms of\n OSPF (flooding, Designated Router (DR) election, area support, Short\n Path First (SPF) calculations, etc.) remain unchanged. However, some\n changes have been necessary, either due to changes in protocol\n semantics between IPv4 and IPv6, or simply to handle the increased\n address size of IPv6. These modifications will necessitate\n incrementing the protocol version from version 2 to version 3. OSPF\n for IPv6 is also referred to as OSPF version 3 (OSPFv3).\n\n Changes between OSPF for IPv4, OSPF Version 2, and OSPF for IPv6 as\n described herein include the following. Addressing semantics have\n been removed from OSPF packets and the basic Link State\n Advertisements (LSAs). New LSAs have been created to carry IPv6\n addresses and prefixes. OSPF now runs on a per","scope_keywords":["5340","authentication","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 5340 This document describes the modifications to OSPF to support version\n 6 of the Internet Protocol (IPv6). The fundamental mechanisms of\n OSPF (flooding, Designated Router (DR) election, area support, Short\n Path First (SPF) calculations, etc.) remain unchanged. However, some\n changes have been necessary, either due to changes in protocol\n semantics between IPv4 and IPv6, or simply to handle the increased\n address size of IPv6. These modifications will necessitate\n incrementing the protocol version from version 2 to version 3. OSPF\n for IPv6 is also referred to as OSPF version 3 (OSPFv3).\n\n Changes between OSPF for IPv4, OSPF Version 2, and OSPF for IPv6 as\n described herein include the following. Addressing semantics have\n been removed from OSPF packets and the basic Link State\n Advertisements (LSAs). New LSAs have been created to carry IPv6\n addresses and prefixes. OSPF now runs on a per 5340 authentication path validation nested-reference unchanged"},{"id":"IETF RFC 5426","type":"specification","body":"IETF","designation":"RFC 5426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5426.txt","https://www.rfc-editor.org/rfc/rfc5426.pdf"],"folder":"IETF/RFC-5426","files":{"txt":{"path":"standards/IETF/RFC-5426/RFC-5426.txt","sha256":"e39b8df74e60d463d06fa9301f7347688184ad043e4ff026f9bf7697eae16bf5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the transport for syslog messages over UDP/\n IPv4 or UDP/IPv6. The syslog protocol layered architecture provides\n for support of any number of transport mappings. However, for\n interoperability purposes, syslog protocol implementers are required\n to support this transport mapping.\n\nOkmianski Standards Track [Page 1]\n\f\nRFC 5426 Syslog UDP Transport March 2009","scope_keywords":["5426","authentication","delivery","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5426 This document describes the transport for syslog messages over UDP/\n IPv4 or UDP/IPv6. The syslog protocol layered architecture provides\n for support of any number of transport mappings. However, for\n interoperability purposes, syslog protocol implementers are required\n to support this transport mapping.\n\nOkmianski Standards Track [Page 1]\n\f\nRFC 5426 Syslog UDP Transport March 2009 5426 authentication delivery http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5838","type":"specification","body":"IETF","designation":"RFC 5838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5838.txt","https://www.rfc-editor.org/rfc/rfc5838.pdf"],"folder":"IETF/RFC-5838","files":{"txt":{"path":"standards/IETF/RFC-5838/RFC-5838.txt","sha256":"baab5f181715180383074e5cec988dd0e4472e78c5c30ab574e0d71cd9a6d2f1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for supporting multiple address\n families (AFs) in OSPFv3 using multiple instances. It maps an AF to\n an OSPFv3 instance using the Instance ID field in the OSPFv3 packet\n header. This approach is fairly simple and minimizes extensions to\n OSPFv3 for supporting multiple AFs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5838.\n\nCopyright Notice\n\n Copyr","scope_keywords":["5838","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5838 This document describes a mechanism for supporting multiple address\n families (AFs) in OSPFv3 using multiple instances. It maps an AF to\n an OSPFv3 instance using the Instance ID field in the OSPFv3 packet\n header. This approach is fairly simple and minimizes extensions to\n OSPFv3 for supporting multiple AFs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5838.\n\nCopyright Notice\n\n Copyr 5838 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6189","type":"specification","body":"IETF","designation":"RFC 6189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6189.txt","https://www.rfc-editor.org/rfc/rfc6189.pdf"],"folder":"IETF/RFC-6189","files":{"txt":{"path":"standards/IETF/RFC-6189/RFC-6189.txt","sha256":"dc7bee3d6cc313554917e59c44463a8196e7cb4e4cc5d276eba15520a1637bc7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines ZRTP, a protocol for media path Diffie-Hellman\n exchange to agree on a session key and parameters for establishing\n unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice\n over IP (VoIP) applications. The ZRTP protocol is media path keying\n because it is multiplexed on the same port as RTP and does not\n require support in the signaling protocol. ZRTP does not assume a\n Public Key Infrastructure (PKI) or require the complexity of\n certificates in end devices. For the media session, ZRTP provides\n confidentiality, protection against man-in-the-middle (MiTM) attacks,\n and, in cases where the signaling protocol provides end-to-end\n integrity protection, authentication. ZRTP can utilize a Session\n Description Protocol (SDP) attribute to provide discovery and\n authentication through the signaling channel. To provide best effort\n SRTP, ZRTP utilizes normal R","scope_keywords":["6189","algorithm","attribute","authentication","certificate","certificates","hash","http","key","keys","license","path","pki","profile","profiles","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6562","folder":"IETF/RFC-6562","source":"IETF/RFC-6562/RFC-6562.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6189 This document defines ZRTP, a protocol for media path Diffie-Hellman\n exchange to agree on a session key and parameters for establishing\n unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice\n over IP (VoIP) applications. The ZRTP protocol is media path keying\n because it is multiplexed on the same port as RTP and does not\n require support in the signaling protocol. ZRTP does not assume a\n Public Key Infrastructure (PKI) or require the complexity of\n certificates in end devices. For the media session, ZRTP provides\n confidentiality, protection against man-in-the-middle (MiTM) attacks,\n and, in cases where the signaling protocol provides end-to-end\n integrity protection, authentication. ZRTP can utilize a Session\n Description Protocol (SDP) attribute to provide discovery and\n authentication through the signaling channel. To provide best effort\n SRTP, ZRTP utilizes normal R 6189 algorithm attribute authentication certificate certificates hash http key keys license path pki profile profiles signature nested-reference unchanged"},{"id":"IETF RFC 6269","type":"specification","body":"IETF","designation":"RFC 6269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6269.txt","https://www.rfc-editor.org/rfc/rfc6269.pdf"],"folder":"IETF/RFC-6269","files":{"txt":{"path":"standards/IETF/RFC-6269/RFC-6269.txt","sha256":"fbe3250fb199363c66d64e39f9cf3368837750bfa0c5fa6f360166ada566f624"}},"tags":["nested-reference","unchanged"],"summary":"The completion of IPv4 address allocations from IANA and the Regional\n Internet Registries (RIRs) is causing service providers around the\n world to question how they will continue providing IPv4 connectivity\n service to their subscribers when there are no longer sufficient IPv4\n addresses to allocate them one per subscriber. Several possible\n solutions to this problem are now emerging based around the idea of\n shared IPv4 addressing. These solutions give rise to a number of\n issues, and this memo identifies those common to all such address\n sharing approaches. Such issues include application failures,\n additional service monitoring complexity, new security\n vulnerabilities, and so on. Solution-specific discussions are out of\n scope.\n\n Deploying IPv6 is the only perennial way to ease pressure on the\n public IPv4 address pool without the need for address sharing\n mechanisms that give rise ","scope_keywords":["6269","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 6269 The completion of IPv4 address allocations from IANA and the Regional\n Internet Registries (RIRs) is causing service providers around the\n world to question how they will continue providing IPv4 connectivity\n service to their subscribers when there are no longer sufficient IPv4\n addresses to allocate them one per subscriber. Several possible\n solutions to this problem are now emerging based around the idea of\n shared IPv4 addressing. These solutions give rise to a number of\n issues, and this memo identifies those common to all such address\n sharing approaches. Such issues include application failures,\n additional service monitoring complexity, new security\n vulnerabilities, and so on. Solution-specific discussions are out of\n scope.\n\n Deploying IPv6 is the only perennial way to ease pressure on the\n public IPv4 address pool without the need for address sharing\n mechanisms that give rise  6269 authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6333","type":"specification","body":"IETF","designation":"RFC 6333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6333.txt","https://www.rfc-editor.org/rfc/rfc6333.pdf"],"folder":"IETF/RFC-6333","files":{"txt":{"path":"standards/IETF/RFC-6333/RFC-6333.txt","sha256":"be5a873b828be8b26264bf8b895ee2c849a7869707ca763ad08e14f2b94b95b4"}},"tags":["nested-reference","unchanged"],"summary":"This document revisits the dual-stack model and introduces the Dual-\n Stack Lite technology aimed at better aligning the costs and benefits\n of deploying IPv6 in service provider networks. Dual-Stack Lite\n enables a broadband service provider to share IPv4 addresses among\n customers by combining two well-known technologies: IP in IP (IPv4-\n in-IPv6) and Network Address Translation (NAT).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b","scope_keywords":["6333","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6970","folder":"IETF/RFC-6970","source":"IETF/RFC-6970/RFC-6970.txt","version":null},{"body":"IETF","designation":"RFC 7040","folder":"IETF/RFC-7040","source":"IETF/RFC-7040/RFC-7040.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7335","folder":"IETF/RFC-7335","source":"IETF/RFC-7335/RFC-7335.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 6333 This document revisits the dual-stack model and introduces the Dual-\n Stack Lite technology aimed at better aligning the costs and benefits\n of deploying IPv6 in service provider networks. Dual-Stack Lite\n enables a broadband service provider to share IPv4 addresses among\n customers by combining two well-known technologies: IP in IP (IPv4-\n in-IPv6) and Network Address Translation (NAT).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b 6333 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6346","type":"specification","body":"IETF","designation":"RFC 6346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6346.txt","https://www.rfc-editor.org/rfc/rfc6346.pdf"],"folder":"IETF/RFC-6346","files":{"txt":{"path":"standards/IETF/RFC-6346/RFC-6346.txt","sha256":"0b84502e5a9edb44b7b691a0d349c688bccf25053f0f97ba23b0907b8209ad46"}},"tags":["nested-reference","unchanged"],"summary":"We are facing the exhaustion of the IANA IPv4 free IP address pool.\n Unfortunately, IPv6 is not yet deployed widely enough to fully\n replace IPv4, and it is unrealistic to expect that this is going to\n change before the depletion of IPv4 addresses. Letting hosts\n seamlessly communicate in an IPv4 world without assigning a unique\n globally routable IPv4 address to each of them is a challenging\n problem.\n\n This document proposes an IPv4 address sharing scheme, treating some\n of the port number bits as part of an extended IPv4 address (Address\n plus Port, or A+P). Instead of assigning a single IPv4 address to a\n single customer device, we propose to extend the address field by\n using bits from the port number range in the TCP/UDP header as\n additional endpoint identifiers, thus leaving a reduced range of\n ports available to applications. This means assigning the same IPv4\n address to multip","scope_keywords":["6346","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 6346 We are facing the exhaustion of the IANA IPv4 free IP address pool.\n Unfortunately, IPv6 is not yet deployed widely enough to fully\n replace IPv4, and it is unrealistic to expect that this is going to\n change before the depletion of IPv4 addresses. Letting hosts\n seamlessly communicate in an IPv4 world without assigning a unique\n globally routable IPv4 address to each of them is a challenging\n problem.\n\n This document proposes an IPv4 address sharing scheme, treating some\n of the port number bits as part of an extended IPv4 address (Address\n plus Port, or A+P). Instead of assigning a single IPv4 address to a\n single customer device, we propose to extend the address field by\n using bits from the port number range in the TCP/UDP header as\n additional endpoint identifiers, thus leaving a reduced range of\n ports available to applications. This means assigning the same IPv4\n address to multip 6346 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6347","type":"specification","body":"IETF","designation":"RFC 6347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6347.txt","https://www.rfc-editor.org/rfc/rfc6347.pdf"],"folder":"IETF/RFC-6347","files":{"txt":{"path":"standards/IETF/RFC-6347/RFC-6347.txt","sha256":"16c851f2ee94586e653566cc3276c6c58256f0b54f3331a68784a6d55357104b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 1.2 of the Datagram Transport Layer\n Security (DTLS) protocol. The DTLS protocol provides communications\n privacy for datagram protocols. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery. The DTLS protocol is\n based on the Transport Layer Security (TLS) protocol and provides\n equivalent security guarantees. Datagram semantics of the underlying\n transport are preserved by the DTLS protocol. This document updates\n DTLS 1.0 to work with TLS version 1.2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG)","scope_keywords":["6347","certificate","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7366","folder":"IETF/RFC-7366","source":"IETF/RFC-7366/RFC-7366.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 6347 This document specifies version 1.2 of the Datagram Transport Layer\n Security (DTLS) protocol. The DTLS protocol provides communications\n privacy for datagram protocols. The protocol allows client/server\n applications to communicate in a way that is designed to prevent\n eavesdropping, tampering, or message forgery. The DTLS protocol is\n based on the Transport Layer Security (TLS) protocol and provides\n equivalent security guarantees. Datagram semantics of the underlying\n transport are preserved by the DTLS protocol. This document updates\n DTLS 1.0 to work with TLS version 1.2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG) 6347 certificate http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6349","type":"specification","body":"IETF","designation":"RFC 6349","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6349.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6349.txt","https://www.rfc-editor.org/rfc/rfc6349.pdf"],"folder":"IETF/RFC-6349","files":{"txt":{"path":"standards/IETF/RFC-6349/RFC-6349.txt","sha256":"2877fcf785a87d6952f8b9781cbadada5e8d7d53a15d63ccaed229655e9e9725"}},"tags":["nested-reference","unchanged"],"summary":"This framework describes a practical methodology for measuring end-\n to-end TCP Throughput in a managed IP network. The goal is to\n provide a better indication in regard to user experience. In this\n framework, TCP and IP parameters are specified to optimize TCP\n Throughput.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ","scope_keywords":["6349","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6349 This framework describes a practical methodology for measuring end-\n to-end TCP Throughput in a managed IP network. The goal is to\n provide a better indication in regard to user experience. In this\n framework, TCP and IP parameters are specified to optimize TCP\n Throughput.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n  6349 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8855","type":"specification","body":"IETF","designation":"RFC 8855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8855.txt","https://www.rfc-editor.org/rfc/rfc8855.pdf"],"folder":"IETF/RFC-8855","files":{"pdf":{"path":"standards/IETF/RFC-8855/RFC-8855.pdf","sha256":"fad6e2d0176984f993d628134793057abef3426af8400e28fda33e089c414eb9"},"txt":{"path":"standards/IETF/RFC-8855/RFC-8855.txt","sha256":"88fc4b620d7d3ec004a9b435bee6e1e53a72e6623c6c3c366105027b0ebc6f95"}},"tags":["nested-reference","unchanged"],"summary":"Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols.\n\n This document specifies the Binary Floor Control Protocol (BFCP).\n BFCP is used between floor participants and floor control servers,\n and between floor chairs (i.e., moderators) and floor control\n servers.\n\n This document obsoletes RFC 4582.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information","scope_keywords":["8855","attribute","attributes","authentication","authorization","http","https","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null}],"search_text":"IETF RFC 8855 Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols.\n\n This document specifies the Binary Floor Control Protocol (BFCP).\n BFCP is used between floor participants and floor control servers,\n and between floor chairs (i.e., moderators) and floor control\n servers.\n\n This document obsoletes RFC 4582.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information 8855 attribute attributes authentication authorization http https license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 1193","type":"specification","body":"IETF","designation":"RFC 1193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1193.txt","https://www.rfc-editor.org/rfc/rfc1193.pdf"],"folder":"IETF/RFC-1193","files":{"txt":{"path":"standards/IETF/RFC-1193/RFC-1193.txt","sha256":"5312e916ad33c2903607eb284c1f1cd132f88cfdd509331d99e9c9893c44e86d"}},"tags":["nested-reference","unchanged"],"summary":"A real-time communication service provides its clients with the\n ability to specify their performance requirements and to obtain\n guarantees about the satisfaction of those requirements. In this\n paper, we propose a set of performance specifications that seem\n appropriate for such services; they include various types of delay\n bounds, throughput bounds, and reliability bounds. We also describe\n other requirements and desirable properties from a client's\n viewpoint, and the ways in which each requirement is to be translated\n to make it suitable for lower levels in the protocol hierarchy.\n Finally, we present some examples of requirements specification, and\n discuss some of the possible objections to our approach.\n\n This research has been supported in part by AT&T Bell Laboratories,\n the University of California under a MICRO grant, and the\n International Computer Science Institute. The vi","scope_keywords":["1193","delivery","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1257","folder":"IETF/RFC-1257","source":"IETF/RFC-1257/RFC-1257.txt","version":null}],"search_text":"IETF RFC 1193 A real-time communication service provides its clients with the\n ability to specify their performance requirements and to obtain\n guarantees about the satisfaction of those requirements. In this\n paper, we propose a set of performance specifications that seem\n appropriate for such services; they include various types of delay\n bounds, throughput bounds, and reliability bounds. We also describe\n other requirements and desirable properties from a client's\n viewpoint, and the ways in which each requirement is to be translated\n to make it suitable for lower levels in the protocol hierarchy.\n Finally, we present some examples of requirements specification, and\n discuss some of the possible objections to our approach.\n\n This research has been supported in part by AT&T Bell Laboratories,\n the University of California under a MICRO grant, and the\n International Computer Science Institute. The vi 1193 delivery policies nested-reference unchanged"},{"id":"IETF RFC 1194","type":"specification","body":"IETF","designation":"RFC 1194","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1194.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1194.txt","https://www.rfc-editor.org/rfc/rfc1194.pdf"],"folder":"IETF/RFC-1194","files":{"txt":{"path":"standards/IETF/RFC-1194/RFC-1194.txt","sha256":"61fdc95ea0022c96df6928e679a18a896aa7492128d66601d3e84faba22b6965"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the Finger User Information Protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition.","scope_keywords":["1194","audit","crl","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1196","folder":"IETF/RFC-1196","source":"IETF/RFC-1196/RFC-1196.txt","version":null},{"body":"IETF","designation":"RFC 1200","folder":"IETF/RFC-1200","source":"IETF/RFC-1200/RFC-1200.txt","version":null}],"search_text":"IETF RFC 1194 This memo describes the Finger User Information Protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition. 1194 audit crl policy nested-reference unchanged"},{"id":"IETF RFC 1196","type":"specification","body":"IETF","designation":"RFC 1196","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1196.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1196.txt","https://www.rfc-editor.org/rfc/rfc1196.pdf"],"folder":"IETF/RFC-1196","files":{"txt":{"path":"standards/IETF/RFC-1196/RFC-1196.txt","sha256":"59dc011b531ca2288bf85434f51115b3e7a9732d7c404050561e2b6ff52cb0df"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the Finger User Information Protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition. This edition corrects and clarifies in\n a minor way, RFC 1194.","scope_keywords":["1196","audit","crl","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1288","folder":"IETF/RFC-1288","source":"IETF/RFC-1288/RFC-1288.txt","version":null}],"search_text":"IETF RFC 1196 This memo describes the Finger User Information Protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition. This edition corrects and clarifies in\n a minor way, RFC 1194. 1196 audit crl policy nested-reference unchanged"},{"id":"IETF RFC 1930","type":"specification","body":"IETF","designation":"RFC 1930","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1930.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1930.txt","https://www.rfc-editor.org/rfc/rfc1930.pdf"],"folder":"IETF/RFC-1930","files":{"txt":{"path":"standards/IETF/RFC-1930/RFC-1930.txt","sha256":"fa5db666d5c8bd2a3e0294bbb07ecd47f8270a39d3a0b020e801ada28728a859"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses when it is appropriate to register and utilize an\n Autonomous System (AS), and lists criteria for such. ASes are the\n unit of routing policy in the modern world of exterior routing, and\n are specifically applicable to protocols like EGP (Exterior Gateway\n Protocol, now at historical status; see [EGP]), BGP (Border Gateway\n Protocol, the current de facto standard for inter-AS routing; see\n [BGP-4]), and IDRP (The OSI Inter-Domain Routing Protocol, which the\n Internet is expected to adopt when BGP becomes obsolete; see [IDRP]).\n It should be noted that the IDRP equivalent of an AS is the RDI, or\n Routing Domain Identifier.","scope_keywords":["1930","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2770","folder":"IETF/RFC-2770","source":"IETF/RFC-2770/RFC-2770.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null}],"search_text":"IETF RFC 1930 This memo discusses when it is appropriate to register and utilize an\n Autonomous System (AS), and lists criteria for such. ASes are the\n unit of routing policy in the modern world of exterior routing, and\n are specifically applicable to protocols like EGP (Exterior Gateway\n Protocol, now at historical status; see [EGP]), BGP (Border Gateway\n Protocol, the current de facto standard for inter-AS routing; see\n [BGP-4]), and IDRP (The OSI Inter-Domain Routing Protocol, which the\n Internet is expected to adopt when BGP becomes obsolete; see [IDRP]).\n It should be noted that the IDRP equivalent of an AS is the RDI, or\n Routing Domain Identifier. 1930 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 3359","type":"specification","body":"IETF","designation":"RFC 3359","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3359.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3359.txt","https://www.rfc-editor.org/rfc/rfc3359.pdf"],"folder":"IETF/RFC-3359","files":{"txt":{"path":"standards/IETF/RFC-3359/RFC-3359.txt","sha256":"f7383129f98a9774520546ae7809fab320b0bd6fb4c7190c39e7cca453be1396"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Przygienda\nRequest for Comments: 3359 Xebeo\nCategory: Informational August 2002\n\n Reserved Type, Length and Value (TLV) Codepoints in\n Intermediate System to Intermediate System\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes implementation codepoints within Intermediate\n System to Intermediate System (IS-IS) used today by several ISPs for\n routing within their clouds. IS-IS is an interior gateway routing\n protocol developed originally by OSI and used with IP extensions as\n Interior Gateway Protocol (IGP). This document summarizes all Table,\n Length and Value (TLV) codepoints that are being used by the protocol\n and i","scope_keywords":["3359","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3358","folder":"IETF/RFC-3358","source":"IETF/RFC-3358/RFC-3358.txt","version":null},{"body":"IETF","designation":"RFC 3563","folder":"IETF/RFC-3563","source":"IETF/RFC-3563/RFC-3563.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null}],"search_text":"IETF RFC 3359 Network Working Group T. Przygienda\nRequest for Comments: 3359 Xebeo\nCategory: Informational August 2002\n\n Reserved Type, Length and Value (TLV) Codepoints in\n Intermediate System to Intermediate System\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document describes implementation codepoints within Intermediate\n System to Intermediate System (IS-IS) used today by several ISPs for\n routing within their clouds. IS-IS is an interior gateway routing\n protocol developed originally by OSI and used with IP extensions as\n Interior Gateway Protocol (IGP). This document summarizes all Table,\n Length and Value (TLV) codepoints that are being used by the protocol\n and i 3359 authentication nested-reference unchanged"},{"id":"IETF RFC 3373","type":"specification","body":"IETF","designation":"RFC 3373","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3373.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3373.txt","https://www.rfc-editor.org/rfc/rfc3373.pdf"],"folder":"IETF/RFC-3373","files":{"txt":{"path":"standards/IETF/RFC-3373/RFC-3373.txt","sha256":"54ec4bfdcf18f1093d64e55867dbfa3b3b3f4073e93f6ed53482cd20c059944b"}},"tags":["nested-reference","unchanged"],"summary":"The IS-IS routing protocol (ISO 10589) requires reliable protocols at\n the link layer for point-to-point links. As a result, it does not\n use a three-way handshake when establishing adjacencies on point-to-\n point media. This paper defines a backward-compatible extension to\n the protocol that provides for a three-way handshake. It is fully\n interoperable with systems that do not support the extension.\n\n Additionally, the extension allows the robust operation of more than\n 256 point-to-point links on a single router.\n\n This extension has been implemented by multiple router vendors; this\n paper is provided as information to the Internet community in order\n to allow interoperable implementations to be built by other vendors.\n\n1. Terms\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to b","scope_keywords":["3373","algorithm","key","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null}],"search_text":"IETF RFC 3373 The IS-IS routing protocol (ISO 10589) requires reliable protocols at\n the link layer for point-to-point links. As a result, it does not\n use a three-way handshake when establishing adjacencies on point-to-\n point media. This paper defines a backward-compatible extension to\n the protocol that provides for a three-way handshake. It is fully\n interoperable with systems that do not support the extension.\n\n Additionally, the extension allows the robust operation of more than\n 256 point-to-point links on a single router.\n\n This extension has been implemented by multiple router vendors; this\n paper is provided as information to the Internet community in order\n to allow interoperable implementations to be built by other vendors.\n\n1. Terms\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to b 3373 algorithm key path risk nested-reference unchanged"},{"id":"IETF RFC 3567","type":"specification","body":"IETF","designation":"RFC 3567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3567.txt","https://www.rfc-editor.org/rfc/rfc3567.pdf"],"folder":"IETF/RFC-3567","files":{"txt":{"path":"standards/IETF/RFC-3567/RFC-3567.txt","sha256":"9272c9e720b5d917819f4a3f13f071539540037c32e56dd81805a74602681fab"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the authentication of Intermediate System to\n Intermediate System (IS-IS) Protocol Data Units (PDUs) using the\n Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)\n algorithm as found in RFC 2104. IS-IS is specified in International\n Standards Organization (ISO) 10589, with extensions to support\n Internet Protocol version 4 (IPv4) described in RFC 1195. The base\n specification includes an authentication mechanism that allows for\n multiple authentication algorithms. The base specification only\n specifies the algorithm for cleartext passwords.\n\n This document proposes an extension to that specification that allows\n the use of the HMAC-MD5 authentication algorithm to be used in\n conjunction with the existing authentication mechanisms.\n\n1. Introduction\n\n The IS-IS protocol, as specified in ISO 10589 [1], provides for the\n authentication of Link State PDU","scope_keywords":["3567","algorithm","algorithms","authentication","hash","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null}],"search_text":"IETF RFC 3567 This document describes the authentication of Intermediate System to\n Intermediate System (IS-IS) Protocol Data Units (PDUs) using the\n Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)\n algorithm as found in RFC 2104. IS-IS is specified in International\n Standards Organization (ISO) 10589, with extensions to support\n Internet Protocol version 4 (IPv4) described in RFC 1195. The base\n specification includes an authentication mechanism that allows for\n multiple authentication algorithms. The base specification only\n specifies the algorithm for cleartext passwords.\n\n This document proposes an extension to that specification that allows\n the use of the HMAC-MD5 authentication algorithm to be used in\n conjunction with the existing authentication mechanisms.\n\n1. Introduction\n\n The IS-IS protocol, as specified in ISO 10589 [1], provides for the\n authentication of Link State PDU 3567 algorithm algorithms authentication hash key risk nested-reference unchanged"},{"id":"IETF RFC 3719","type":"specification","body":"IETF","designation":"RFC 3719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3719.txt","https://www.rfc-editor.org/rfc/rfc3719.pdf"],"folder":"IETF/RFC-3719","files":{"txt":{"path":"standards/IETF/RFC-3719/RFC-3719.txt","sha256":"62296f5a45c861687ea6568d4c27d2581d3b54f688b383213682c9bb584699cc"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses a number of differences between the\n Intermediate System to Intermediate System (IS-IS) protocol as\n described in ISO 10589 and the protocol as it is deployed today.\n These differences are discussed as a service to those implementing,\n testing, and deploying the IS-IS Protocol. A companion document\n discusses differences between the protocol described in RFC 1195 and\n the protocol as it is deployed today for routing IP traffic.","scope_keywords":["3719","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null}],"search_text":"IETF RFC 3719 This document discusses a number of differences between the\n Intermediate System to Intermediate System (IS-IS) protocol as\n described in ISO 10589 and the protocol as it is deployed today.\n These differences are discussed as a service to those implementing,\n testing, and deploying the IS-IS Protocol. A companion document\n discusses differences between the protocol described in RFC 1195 and\n the protocol as it is deployed today for routing IP traffic. 3719 key nested-reference unchanged"},{"id":"IETF RFC 3784","type":"specification","body":"IETF","designation":"RFC 3784","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3784.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3784.txt","https://www.rfc-editor.org/rfc/rfc3784.pdf"],"folder":"IETF/RFC-3784","files":{"txt":{"path":"standards/IETF/RFC-3784/RFC-3784.txt","sha256":"4a710cdf5fc710563871f601b2fd554a2d4b00f5ea8ee0004d4a835b8bb26e49"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support Traffic Engineering\n (TE). This document extends the IS-IS protocol by specifying new\n information that an Intermediate System (router) can place in Link\n State Protocol (LSP) Data Units. This information describes\n additional details regarding the state of the network that are useful\n for traffic engineering computations.\n\n1. Introduction\n\n The IS-IS protocol is specified in ISO 10589 [1], with extensions for\n supporting IPv4 specified in RFC 1195 [3]. Each Intermediate System\n (IS) (router) advertises one or more IS-IS Link State Protocol Data\n Units (LSPs) with routing information. Each LSP is composed of a\n fixed header and a number of tuples, each consisting of a Type, a\n Length, and a Value. Such tuples are commonly known as TLVs, and are\n a good way of encoding informa","scope_keywords":["3784","http","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null}],"search_text":"IETF RFC 3784 This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support Traffic Engineering\n (TE). This document extends the IS-IS protocol by specifying new\n information that an Intermediate System (router) can place in Link\n State Protocol (LSP) Data Units. This information describes\n additional details regarding the state of the network that are useful\n for traffic engineering computations.\n\n1. Introduction\n\n The IS-IS protocol is specified in ISO 10589 [1], with extensions for\n supporting IPv4 specified in RFC 1195 [3]. Each Intermediate System\n (IS) (router) advertises one or more IS-IS Link State Protocol Data\n Units (LSPs) with routing information. Each LSP is composed of a\n fixed header and a number of tuples, each consisting of a Type, a\n Length, and a Value. Such tuples are commonly known as TLVs, and are\n a good way of encoding informa 3784 http identification path nested-reference unchanged"},{"id":"IETF RFC 3786","type":"specification","body":"IETF","designation":"RFC 3786","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3786.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3786.txt","https://www.rfc-editor.org/rfc/rfc3786.pdf"],"folder":"IETF/RFC-3786","files":{"txt":{"path":"standards/IETF/RFC-3786/RFC-3786.txt","sha256":"76e3b57a0240a794b5d7f461893fd0010f8b3ef1e7918da0a22ecbb35101fa58"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that allows a system to originate\n more than 256 Link State PDU (LSP) fragments, a limit set by the\n original Intermediate System to Intermediate System (IS-IS) Routing\n protocol, as described in ISO/IEC 10589. This mechanism can be used\n in IP-only, OSI-only, and dual routers.","scope_keywords":["3786","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null}],"search_text":"IETF RFC 3786 This document describes a mechanism that allows a system to originate\n more than 256 Link State PDU (LSP) fragments, a limit set by the\n original Intermediate System to Intermediate System (IS-IS) Routing\n protocol, as described in ISO/IEC 10589. This mechanism can be used\n in IP-only, OSI-only, and dual routers. 3786 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3847","type":"specification","body":"IETF","designation":"RFC 3847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3847.txt","https://www.rfc-editor.org/rfc/rfc3847.pdf"],"folder":"IETF/RFC-3847","files":{"txt":{"path":"standards/IETF/RFC-3847/RFC-3847.txt","sha256":"883ba2d56495dab059ded99b6946fc10305c7908cf0e9e1cd1a56faf4113f04e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for a restarting router to signal\n to its neighbors that it is restarting, allowing them to reestablish\n their adjacencies without cycling through the down state, while still\n correctly initiating database synchronization.\n\n This document additionally describes a mechanism for a restarting\n router to determine when it has achieved LSP database synchronization\n with its neighbors and a mechanism to optimize LSP database\n synchronization, while minimizing transient routing disruption when a\n router starts.\n\nShand & Ginsberg Informational [Page 1]\n\f\nRFC 3847 Restart signaling for IS-IS July 2004","scope_keywords":["3847","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null}],"search_text":"IETF RFC 3847 This document describes a mechanism for a restarting router to signal\n to its neighbors that it is restarting, allowing them to reestablish\n their adjacencies without cycling through the down state, while still\n correctly initiating database synchronization.\n\n This document additionally describes a mechanism for a restarting\n router to determine when it has achieved LSP database synchronization\n with its neighbors and a mechanism to optimize LSP database\n synchronization, while minimizing transient routing disruption when a\n router starts.\n\nShand & Ginsberg Informational [Page 1]\n\f\nRFC 3847 Restart signaling for IS-IS July 2004 3847 key nested-reference unchanged"},{"id":"IETF RFC 4110","type":"specification","body":"IETF","designation":"RFC 4110","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4110.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4110.txt","https://www.rfc-editor.org/rfc/rfc4110.pdf"],"folder":"IETF/RFC-4110","files":{"txt":{"path":"standards/IETF/RFC-4110/RFC-4110.txt","sha256":"481a26e307c354d3dee11fc602efd4bb8163929bdd41d69125199b5d66d0232b"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for Layer 3 Provider-Provisioned\n Virtual Private Networks (PPVPNs). This framework is intended to aid\n in the standardization of protocols and mechanisms for support of\n layer 3 PPVPNs. It is the intent of this document to produce a\n coherent description of the significant technical issues that are\n important in the design of layer 3 PPVPN solutions. Selection of\n specific approaches, making choices regarding engineering tradeoffs,\n and detailed protocol specification, are outside of the scope of this\n framework document.","scope_keywords":["4110","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4110 This document provides a framework for Layer 3 Provider-Provisioned\n Virtual Private Networks (PPVPNs). This framework is intended to aid\n in the standardization of protocols and mechanisms for support of\n layer 3 PPVPNs. It is the intent of this document to produce a\n coherent description of the significant technical issues that are\n important in the design of layer 3 PPVPN solutions. Selection of\n specific approaches, making choices regarding engineering tradeoffs,\n and detailed protocol specification, are outside of the scope of this\n framework document. 4110 authentication management nested-reference unchanged"},{"id":"IETF RFC 4444","type":"specification","body":"IETF","designation":"RFC 4444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4444.txt","https://www.rfc-editor.org/rfc/rfc4444.pdf"],"folder":"IETF/RFC-4444","files":{"txt":{"path":"standards/IETF/RFC-4444/RFC-4444.txt","sha256":"d976a9a39537a2dc8fc8dec81f086da6e141851daf4c1e8b8169fa3d875fcc57"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this document describes a MIB for the Intermediate\n System to Intermediate System (IS-IS) Routing protocol when it is\n used to construct routing tables for IP networks.","scope_keywords":["4444","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4444 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this document describes a MIB for the Intermediate\n System to Intermediate System (IS-IS) Routing protocol when it is\n used to construct routing tables for IP networks. 4444 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 4593","type":"specification","body":"IETF","designation":"RFC 4593","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4593.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4593.txt","https://www.rfc-editor.org/rfc/rfc4593.pdf"],"folder":"IETF/RFC-4593","files":{"txt":{"path":"standards/IETF/RFC-4593/RFC-4593.txt","sha256":"595c1ba155d07262290decb70d73df1b611fe5cc742b7c0a1dfc320368022b73"}},"tags":["nested-reference","unchanged"],"summary":"Routing protocols are subject to attacks that can harm individual\n users or network operations as a whole. This document provides a\n description and a summary of generic threats that affect routing\n protocols in general. This work describes threats, including threat\n sources and capabilities, threat actions, and threat consequences, as\n well as a breakdown of routing functions that might be attacked\n separately.\n\nBarbir, et al. Informational [Page 1]\n\f\nRFC 4593 Generic Threats to Routing Protocols October 2006","scope_keywords":["4593","path","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5668","folder":"IETF/RFC-5668","source":"IETF/RFC-5668/RFC-5668.txt","version":null},{"body":"IETF","designation":"RFC 5701","folder":"IETF/RFC-5701","source":"IETF/RFC-5701/RFC-5701.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null}],"search_text":"IETF RFC 4593 Routing protocols are subject to attacks that can harm individual\n users or network operations as a whole. This document provides a\n description and a summary of generic threats that affect routing\n protocols in general. This work describes threats, including threat\n sources and capabilities, threat actions, and threat consequences, as\n well as a breakdown of routing functions that might be attacked\n separately.\n\nBarbir, et al. Informational [Page 1]\n\f\nRFC 4593 Generic Threats to Routing Protocols October 2006 4593 path risk subject nested-reference unchanged"},{"id":"IETF RFC 4971","type":"specification","body":"IETF","designation":"RFC 4971","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4971.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4971.txt","https://www.rfc-editor.org/rfc/rfc4971.pdf"],"folder":"IETF/RFC-4971","files":{"txt":{"path":"standards/IETF/RFC-4971/RFC-4971.txt","sha256":"5b2841709c366b94fccafc83c9d7e82ccccded2f45557dcfbcd9d4dd3a6e98f6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new optional Intermediate System to\n Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple\n sub-TLVs, which allows a router to announce its capabilities within\n an IS-IS level or the entire routing domain.","scope_keywords":["4971","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null}],"search_text":"IETF RFC 4971 This document defines a new optional Intermediate System to\n Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple\n sub-TLVs, which allows a router to announce its capabilities within\n an IS-IS level or the entire routing domain. 4971 key path trust nested-reference unchanged"},{"id":"IETF RFC 4972","type":"specification","body":"IETF","designation":"RFC 4972","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4972.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4972.txt","https://www.rfc-editor.org/rfc/rfc4972.pdf"],"folder":"IETF/RFC-4972","files":{"txt":{"path":"standards/IETF/RFC-4972/RFC-4972.txt","sha256":"9779fe3e13ee0688f25c9da545327cba7e768a8708801ef6c064d71aea9d2950"}},"tags":["nested-reference","unchanged"],"summary":"The setup of a full mesh of Multi-Protocol Label Switching (MPLS)\n Traffic Engineering (TE) Label Switched Paths (LSP) among a set of\n Label Switch Routers (LSR) is a common deployment scenario of MPLS\n Traffic Engineering either for bandwidth optimization, bandwidth\n guarantees or fast rerouting with MPLS Fast Reroute. Such deployment\n may require the configuration of a potentially large number of TE\n LSPs (on the order of the square of the number of LSRs). This\n document specifies Interior Gateway Protocol (IGP) routing extensions\n for Intermediate System-to-Intermediate System (IS-IS) and Open\n Shortest Path First (OSPF) so as to provide an automatic discovery of\n the set of LSRs members of a mesh in order to automate the creation\n of such mesh of TE LSPs.\n\nVasseur, et al. Standards Track [Page 1]\n\f\nRFC 4972 Discovery of MPLS LSR TE Mesh Membership July 2007","scope_keywords":["4972","key","path","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null}],"search_text":"IETF RFC 4972 The setup of a full mesh of Multi-Protocol Label Switching (MPLS)\n Traffic Engineering (TE) Label Switched Paths (LSP) among a set of\n Label Switch Routers (LSR) is a common deployment scenario of MPLS\n Traffic Engineering either for bandwidth optimization, bandwidth\n guarantees or fast rerouting with MPLS Fast Reroute. Such deployment\n may require the configuration of a potentially large number of TE\n LSPs (on the order of the square of the number of LSRs). This\n document specifies Interior Gateway Protocol (IGP) routing extensions\n for Intermediate System-to-Intermediate System (IS-IS) and Open\n Shortest Path First (OSPF) so as to provide an automatic discovery of\n the set of LSRs members of a mesh in order to automate the creation\n of such mesh of TE LSPs.\n\nVasseur, et al. Standards Track [Page 1]\n\f\nRFC 4972 Discovery of MPLS LSR TE Mesh Membership July 2007 4972 key path risk trust nested-reference unchanged"},{"id":"IETF RFC 5029","type":"specification","body":"IETF","designation":"RFC 5029","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5029.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5029.txt","https://www.rfc-editor.org/rfc/rfc5029.pdf"],"folder":"IETF/RFC-5029","files":{"txt":{"path":"standards/IETF/RFC-5029/RFC-5029.txt","sha256":"46c3f1f0ab1a51698ae5244ec5bf424786822be79a991646074bec3b7d5ae2c7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a sub-TLV called \"Link-attributes\" carried\n within the TLV 22 and used to flood some link characteristics.","scope_keywords":["5029","attribute","attributes","authentication","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null}],"search_text":"IETF RFC 5029 This document defines a sub-TLV called \"Link-attributes\" carried\n within the TLV 22 and used to flood some link characteristics. 5029 attribute attributes authentication key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5073","type":"specification","body":"IETF","designation":"RFC 5073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5073.txt","https://www.rfc-editor.org/rfc/rfc5073.pdf"],"folder":"IETF/RFC-5073","files":{"txt":{"path":"standards/IETF/RFC-5073/RFC-5073.txt","sha256":"429de1139745c296399304baa5de656f1681835ed31aca1dff4b9d41e7840204"}},"tags":["nested-reference","unchanged"],"summary":"It is highly desired, in several cases, to take into account Traffic\n Engineering (TE) node capabilities during Multi Protocol Label\n Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered\n Label Switched Path (TE-LSP) selection, such as, for instance, the\n capability to act as a branch Label Switching Router (LSR) of a\n Point-To-MultiPoint (P2MP) LSP. This requires advertising these\n capabilities within the Interior Gateway Protocol (IGP). For that\n purpose, this document specifies Open Shortest Path First (OSPF) and\n Intermediate System-Intermediate System (IS-IS) traffic engineering\n extensions for the advertisement of control plane and data plane\n traffic engineering node capabilities.\n\nVasseur & Le Roux Standards Track [Page 1]\n\f\nRFC 5073 IGP Ext for Discovery of TE Node Cap December 2007","scope_keywords":["5073","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5073 It is highly desired, in several cases, to take into account Traffic\n Engineering (TE) node capabilities during Multi Protocol Label\n Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered\n Label Switched Path (TE-LSP) selection, such as, for instance, the\n capability to act as a branch Label Switching Router (LSR) of a\n Point-To-MultiPoint (P2MP) LSP. This requires advertising these\n capabilities within the Interior Gateway Protocol (IGP). For that\n purpose, this document specifies Open Shortest Path First (OSPF) and\n Intermediate System-Intermediate System (IS-IS) traffic engineering\n extensions for the advertisement of control plane and data plane\n traffic engineering node capabilities.\n\nVasseur & Le Roux Standards Track [Page 1]\n\f\nRFC 5073 IGP Ext for Discovery of TE Node Cap December 2007 5073 key path nested-reference unchanged"},{"id":"IETF RFC 5120","type":"specification","body":"IETF","designation":"RFC 5120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5120.txt","https://www.rfc-editor.org/rfc/rfc5120.pdf"],"folder":"IETF/RFC-5120","files":{"txt":{"path":"standards/IETF/RFC-5120/RFC-5120.txt","sha256":"1b3994ffc54480ecfa3244071f77970cfe4be16adbdd4d50002016b876007b97"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an optional mechanism within Intermediate\n System to Intermediate Systems (IS-ISs) used today by many ISPs for\n IGP routing within their clouds. This document describes how to run,\n within a single IS-IS domain, a set of independent IP topologies that\n we call Multi-Topologies (MTs). This MT extension can be used for a\n variety of purposes, such as an in-band management network \"on top\"\n of the original IGP topology, maintaining separate IGP routing\n domains for isolated multicast or IPv6 islands within the backbone,\n or forcing a subset of an address space to follow a different\n topology.\n\n1. Introduction\n\n Maintaining multiple MTs for IS-IS [ISO10589] [RFC1195] in a\n backwards-compatible manner necessitates several extensions to the\n packet encoding and additional Shortest Path First (SPF) procedures.\n The problem can be partitioned into the forming of adjacenci","scope_keywords":["5120","algorithm","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 5120 This document describes an optional mechanism within Intermediate\n System to Intermediate Systems (IS-ISs) used today by many ISPs for\n IGP routing within their clouds. This document describes how to run,\n within a single IS-IS domain, a set of independent IP topologies that\n we call Multi-Topologies (MTs). This MT extension can be used for a\n variety of purposes, such as an in-band management network \"on top\"\n of the original IGP topology, maintaining separate IGP routing\n domains for isolated multicast or IPv6 islands within the backbone,\n or forcing a subset of an address space to follow a different\n topology.\n\n1. Introduction\n\n Maintaining multiple MTs for IS-IS [ISO10589] [RFC1195] in a\n backwards-compatible manner necessitates several extensions to the\n packet encoding and additional Shortest Path First (SPF) procedures.\n The problem can be partitioned into the forming of adjacenci 5120 algorithm key management path nested-reference unchanged"},{"id":"IETF RFC 5130","type":"specification","body":"IETF","designation":"RFC 5130","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5130.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5130.txt","https://www.rfc-editor.org/rfc/rfc5130.pdf"],"folder":"IETF/RFC-5130","files":{"txt":{"path":"standards/IETF/RFC-5130/RFC-5130.txt","sha256":"2d0eeacbcb40f7c22374f953fa099b2184c4e720000f6f391dea6de9a544f13e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the IS-IS protocol to add\n operational capabilities that allow for ease of management and\n control over IP prefix distribution within an IS-IS domain. This\n document enhances the IS-IS protocol by extending the information\n that an Intermediate System (IS) router can place in Link State\n Protocol (LSP) Data Units for policy use. This extension will\n provide operators with a mechanism to control IP prefix distribution\n throughout multi-level IS-IS domains.","scope_keywords":["5130","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5130 This document describes an extension to the IS-IS protocol to add\n operational capabilities that allow for ease of management and\n control over IP prefix distribution within an IS-IS domain. This\n document enhances the IS-IS protocol by extending the information\n that an Intermediate System (IS) router can place in Link State\n Protocol (LSP) Data Units for policy use. This extension will\n provide operators with a mechanism to control IP prefix distribution\n throughout multi-level IS-IS domains. 5130 key management path policy nested-reference unchanged"},{"id":"IETF RFC 5283","type":"specification","body":"IETF","designation":"RFC 5283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5283.txt","https://www.rfc-editor.org/rfc/rfc5283.pdf"],"folder":"IETF/RFC-5283","files":{"txt":{"path":"standards/IETF/RFC-5283/RFC-5283.txt","sha256":"2802809680bc28c2a3d726269c95632ebc6c515214ae06dca8f5987bea190e4d"}},"tags":["nested-reference","unchanged"],"summary":"To facilitate the establishment of Label Switched Paths (LSPs) that\n would span multiple IGP areas in a given Autonomous System (AS), this\n document describes a new optional Longest-Match Label Mapping\n Procedure for the Label Distribution Protocol (LDP).\n\n This procedure allows the use of a label if the Forwarding\n Equivalence Class (FEC) Element matches an entry in the Routing\n Information Base (RIB). Matching is defined by an IP longest-match\n search and does not mandate an exact match.","scope_keywords":["5283","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null}],"search_text":"IETF RFC 5283 To facilitate the establishment of Label Switched Paths (LSPs) that\n would span multiple IGP areas in a given Autonomous System (AS), this\n document describes a new optional Longest-Match Label Mapping\n Procedure for the Label Distribution Protocol (LDP).\n\n This procedure allows the use of a label if the Forwarding\n Equivalence Class (FEC) Element matches an entry in the Routing\n Information Base (RIB). Matching is defined by an IP longest-match\n search and does not mandate an exact match. 5283 key path nested-reference unchanged"},{"id":"IETF RFC 5286","type":"specification","body":"IETF","designation":"RFC 5286","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5286.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5286.txt","https://www.rfc-editor.org/rfc/rfc5286.pdf"],"folder":"IETF/RFC-5286","files":{"txt":{"path":"standards/IETF/RFC-5286/RFC-5286.txt","sha256":"7c612d458dbe0e6730ee38b43b75205acd24c967a2ec209cb8f40f5bc2b72c8b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of loop-free alternates to provide\n local protection for unicast traffic in pure IP and MPLS/LDP networks\n in the event of a single failure, whether link, node, or shared risk\n link group (SRLG). The goal of this technology is to reduce the\n packet loss that happens while routers converge after a topology\n change due to a failure. Rapid failure repair is achieved through\n use of precalculated backup next-hops that are loop-free and safe to\n use until the distributed network convergence process completes.\n This simple approach does not require any support from other routers.\n The extent to which this goal can be met by this specification is\n dependent on the topology of the network.\n\nAtlas, et al. Standards Track [Page 1]\n\f\nRFC 5286 IP Fast Reroute: Loop-Free Alternates September 2008","scope_keywords":["5286","attribute","attributes","path","pid","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5286 This document describes the use of loop-free alternates to provide\n local protection for unicast traffic in pure IP and MPLS/LDP networks\n in the event of a single failure, whether link, node, or shared risk\n link group (SRLG). The goal of this technology is to reduce the\n packet loss that happens while routers converge after a topology\n change due to a failure. Rapid failure repair is achieved through\n use of precalculated backup next-hops that are loop-free and safe to\n use until the distributed network convergence process completes.\n This simple approach does not require any support from other routers.\n The extent to which this goal can be met by this specification is\n dependent on the topology of the network.\n\nAtlas, et al. Standards Track [Page 1]\n\f\nRFC 5286 IP Fast Reroute: Loop-Free Alternates September 2008 5286 attribute attributes path pid risk nested-reference unchanged"},{"id":"IETF RFC 5302","type":"specification","body":"IETF","designation":"RFC 5302","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5302.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5302.txt","https://www.rfc-editor.org/rfc/rfc5302.pdf"],"folder":"IETF/RFC-5302","files":{"txt":{"path":"standards/IETF/RFC-5302/RFC-5302.txt","sha256":"94fad30d9725598cae8254071958e2b6e6eded356210a248a845da395b4a17bb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support optimal routing\n within a two-level domain. The IS-IS protocol is specified in ISO\n 10589, with extensions for supporting IPv4 (Internet Protocol)\n specified in RFC 1195. This document replaces RFC 2966.\n\n This document extends the semantics presented in RFC 1195 so that a\n routing domain running with both level 1 and level 2 Intermediate\n Systems (IS) (routers) can distribute IP prefixes between level 1 and\n level 2, and vice versa. This distribution requires certain\n restrictions to ensure that persistent forwarding loops do not form.\n The goal of this domain-wide prefix distribution is to increase the\n granularity of the routing information within the domain.\n\nLi, et al. Standards Track [Page 1]\n\f\nRFC 5302 Domain-wide Prefix Distribution October 2008","scope_keywords":["5302","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null}],"search_text":"IETF RFC 5302 This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support optimal routing\n within a two-level domain. The IS-IS protocol is specified in ISO\n 10589, with extensions for supporting IPv4 (Internet Protocol)\n specified in RFC 1195. This document replaces RFC 2966.\n\n This document extends the semantics presented in RFC 1195 so that a\n routing domain running with both level 1 and level 2 Intermediate\n Systems (IS) (routers) can distribute IP prefixes between level 1 and\n level 2, and vice versa. This distribution requires certain\n restrictions to ensure that persistent forwarding loops do not form.\n The goal of this domain-wide prefix distribution is to increase the\n granularity of the routing information within the domain.\n\nLi, et al. Standards Track [Page 1]\n\f\nRFC 5302 Domain-wide Prefix Distribution October 2008 5302 path nested-reference unchanged"},{"id":"IETF RFC 5303","type":"specification","body":"IETF","designation":"RFC 5303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5303.txt","https://www.rfc-editor.org/rfc/rfc5303.pdf"],"folder":"IETF/RFC-5303","files":{"txt":{"path":"standards/IETF/RFC-5303/RFC-5303.txt","sha256":"e666203dab4af97b5346dc0483aac93ed5803523863f7e469a6ba5a0f20e8c87"}},"tags":["nested-reference","unchanged"],"summary":"The IS-IS routing protocol (Intermediate System to Intermediate\n System, ISO 10589) requires reliable protocols at the link layer for\n point-to-point links. As a result, it does not use a three-way\n handshake when establishing adjacencies on point-to-point media.\n This paper defines a backward-compatible extension to the protocol\n that provides for a three-way handshake. It is fully interoperable\n with systems that do not support the extension.\n\n Additionally, the extension allows the robust operation of more than\n 256 point-to-point links on a single router.\n\n This extension has been implemented by multiple router vendors; this\n paper is provided to the Internet community in order to allow\n interoperable implementations to be built by other vendors.\n\nKatz, et al. Standards Track [Page 1]\n\f\nRFC 5303 Three-Way Handshake for IS-IS October 2008","scope_keywords":["5303","algorithm","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null}],"search_text":"IETF RFC 5303 The IS-IS routing protocol (Intermediate System to Intermediate\n System, ISO 10589) requires reliable protocols at the link layer for\n point-to-point links. As a result, it does not use a three-way\n handshake when establishing adjacencies on point-to-point media.\n This paper defines a backward-compatible extension to the protocol\n that provides for a three-way handshake. It is fully interoperable\n with systems that do not support the extension.\n\n Additionally, the extension allows the robust operation of more than\n 256 point-to-point links on a single router.\n\n This extension has been implemented by multiple router vendors; this\n paper is provided to the Internet community in order to allow\n interoperable implementations to be built by other vendors.\n\nKatz, et al. Standards Track [Page 1]\n\f\nRFC 5303 Three-Way Handshake for IS-IS October 2008 5303 algorithm key path nested-reference unchanged"},{"id":"IETF RFC 5304","type":"specification","body":"IETF","designation":"RFC 5304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5304.txt","https://www.rfc-editor.org/rfc/rfc5304.pdf"],"folder":"IETF/RFC-5304","files":{"txt":{"path":"standards/IETF/RFC-5304/RFC-5304.txt","sha256":"922bbfd5e97ddadd83f4c2d9738ccef847664c1e7807c9be85724babd401920e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the authentication of Intermediate System to\n Intermediate System (IS-IS) Protocol Data Units (PDUs) using the\n Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)\n algorithm as found in RFC 2104. IS-IS is specified in International\n Standards Organization (ISO) 10589, with extensions to support\n Internet Protocol version 4 (IPv4) described in RFC 1195. The base\n specification includes an authentication mechanism that allows for\n multiple authentication algorithms. The base specification only\n specifies the algorithm for cleartext passwords. This document\n replaces RFC 3567.\n\n This document proposes an extension to that specification that allows\n the use of the HMAC-MD5 authentication algorithm to be used in\n conjunction with the existing authentication mechanisms.\n\nLi & Atkinson Standards Track [Page 1]\n\f\nRFC 5304 IS-IS Cryptographic Authentication ","scope_keywords":["5304","algorithm","algorithms","authentication","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5301","folder":"IETF/RFC-5301","source":"IETF/RFC-5301/RFC-5301.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null}],"search_text":"IETF RFC 5304 This document describes the authentication of Intermediate System to\n Intermediate System (IS-IS) Protocol Data Units (PDUs) using the\n Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)\n algorithm as found in RFC 2104. IS-IS is specified in International\n Standards Organization (ISO) 10589, with extensions to support\n Internet Protocol version 4 (IPv4) described in RFC 1195. The base\n specification includes an authentication mechanism that allows for\n multiple authentication algorithms. The base specification only\n specifies the algorithm for cleartext passwords. This document\n replaces RFC 3567.\n\n This document proposes an extension to that specification that allows\n the use of the HMAC-MD5 authentication algorithm to be used in\n conjunction with the existing authentication mechanisms.\n\nLi & Atkinson Standards Track [Page 1]\n\f\nRFC 5304 IS-IS Cryptographic Authentication  5304 algorithm algorithms authentication hash key nested-reference unchanged"},{"id":"IETF RFC 5305","type":"specification","body":"IETF","designation":"RFC 5305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5305.txt","https://www.rfc-editor.org/rfc/rfc5305.pdf"],"folder":"IETF/RFC-5305","files":{"txt":{"path":"standards/IETF/RFC-5305/RFC-5305.txt","sha256":"9189a70982e5d393466e9bd9d0b499b4166fe64c15c5910e24d444922330143f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support Traffic Engineering\n (TE). This document extends the IS-IS protocol by specifying new\n information that an Intermediate System (router) can place in Link\n State Protocol Data Units (LSP). This information describes\n additional details regarding the state of the network that are useful\n for traffic engineering computations.\n\nLi & Smit Standards Track [Page 1]\n\f\nRFC 5305 IS-IS Extensions for Traffic Engineering October 2008","scope_keywords":["5305","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 5305 This document describes extensions to the Intermediate System to\n Intermediate System (IS-IS) protocol to support Traffic Engineering\n (TE). This document extends the IS-IS protocol by specifying new\n information that an Intermediate System (router) can place in Link\n State Protocol Data Units (LSP). This information describes\n additional details regarding the state of the network that are useful\n for traffic engineering computations.\n\nLi & Smit Standards Track [Page 1]\n\f\nRFC 5305 IS-IS Extensions for Traffic Engineering October 2008 5305 identification key nested-reference unchanged"},{"id":"IETF RFC 5306","type":"specification","body":"IETF","designation":"RFC 5306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5306.txt","https://www.rfc-editor.org/rfc/rfc5306.pdf"],"folder":"IETF/RFC-5306","files":{"txt":{"path":"standards/IETF/RFC-5306/RFC-5306.txt","sha256":"3a4d6bba0675ea760031583fd1abd8ac32f33928df9020f957d0cca300256646"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for a restarting router to signal\n to its neighbors that it is restarting, allowing them to reestablish\n their adjacencies without cycling through the down state, while still\n correctly initiating database synchronization.\n\n This document additionally describes a mechanism for a restarting\n router to determine when it has achieved Link State Protocol Data\n Unit (LSP) database synchronization with its neighbors and a\n mechanism to optimize LSP database synchronization, while minimizing\n transient routing disruption when a router starts. This document\n obsoletes RFC 3847.\n\nShand & Ginsberg Standards Track [Page 1]\n\f\nRFC 5306 Restart Signaling for IS-IS October 2008","scope_keywords":["5306","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 5306 This document describes a mechanism for a restarting router to signal\n to its neighbors that it is restarting, allowing them to reestablish\n their adjacencies without cycling through the down state, while still\n correctly initiating database synchronization.\n\n This document additionally describes a mechanism for a restarting\n router to determine when it has achieved Link State Protocol Data\n Unit (LSP) database synchronization with its neighbors and a\n mechanism to optimize LSP database synchronization, while minimizing\n transient routing disruption when a router starts. This document\n obsoletes RFC 3847.\n\nShand & Ginsberg Standards Track [Page 1]\n\f\nRFC 5306 Restart Signaling for IS-IS October 2008 5306 key nested-reference unchanged"},{"id":"IETF RFC 5308","type":"specification","body":"IETF","designation":"RFC 5308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5308.txt","https://www.rfc-editor.org/rfc/rfc5308.pdf"],"folder":"IETF/RFC-5308","files":{"txt":{"path":"standards/IETF/RFC-5308/RFC-5308.txt","sha256":"fd23bf0d1be283d764c833a1eba46c226d249d9c2297f9bdba4b4ff58900be03"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for exchanging IPv6 routing\n information using the IS-IS routing protocol. The described method\n utilizes two new TLVs: a reachability TLV and an interface address\n TLV to distribute the necessary IPv6 information throughout a routing\n domain. Using this method, one can route IPv6 along with IPv4 and\n OSI using a single intra-domain routing protocol.\n\n1. Overview\n\n IS-IS is an extendible intra-domain routing protocol. Each router in\n the routing domain issues an Link State Protocol Data Unit (LSP) that\n contains information pertaining to that router. The LSP contains\n typed variable-length data, often referred to as TLVs (type-length-\n values). We extend the protocol with two new TLVs to carry\n information required to perform IPv6 routing.\n\n In [RFC1195], a method is described to route both OSI and IPv4. We\n utilize this same method with some minor change","scope_keywords":["5308","key","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 5308 This document specifies a method for exchanging IPv6 routing\n information using the IS-IS routing protocol. The described method\n utilizes two new TLVs: a reachability TLV and an interface address\n TLV to distribute the necessary IPv6 information throughout a routing\n domain. Using this method, one can route IPv6 along with IPv4 and\n OSI using a single intra-domain routing protocol.\n\n1. Overview\n\n IS-IS is an extendible intra-domain routing protocol. Each router in\n the routing domain issues an Link State Protocol Data Unit (LSP) that\n contains information pertaining to that router. The LSP contains\n typed variable-length data, often referred to as TLVs (type-length-\n values). We extend the protocol with two new TLVs to carry\n information required to perform IPv6 routing.\n\n In [RFC1195], a method is described to route both OSI and IPv4. We\n utilize this same method with some minor change 5308 key path pid nested-reference unchanged"},{"id":"IETF RFC 5309","type":"specification","body":"IETF","designation":"RFC 5309","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5309.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5309.txt","https://www.rfc-editor.org/rfc/rfc5309.pdf"],"folder":"IETF/RFC-5309","files":{"txt":{"path":"standards/IETF/RFC-5309/RFC-5309.txt","sha256":"472fd87df49513565f6aaa7cc6c56f28159cde9bf15366a2c519998349907f87"}},"tags":["nested-reference","unchanged"],"summary":"The two predominant circuit types used by link state routing\n protocols are point-to-point and broadcast. It is important to\n identify the correct circuit type when forming adjacencies, flooding\n link state database packets, and representing the circuit\n topologically. This document describes a simple mechanism to treat\n the broadcast network as a point-to-point connection from the\n standpoint of IP routing.\n\n1. Introduction\n\n Point-to-point and broadcast are the two predominant circuit types\n used by link state routing protocols such as IS-IS [ISO10589]\n [RFC1195] and OSPF [RFC2328] [RFC5340]. They are treated differently\n with respect to establishing neighbor adjacencies, flooding link\n state information, representing the topology, and calculating the\n Shortest Path First (SPF) and protocol packets. The most important\n differences are that broadcast circuits utilize the concept of a\n d","scope_keywords":["5309","key","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 5309 The two predominant circuit types used by link state routing\n protocols are point-to-point and broadcast. It is important to\n identify the correct circuit type when forming adjacencies, flooding\n link state database packets, and representing the circuit\n topologically. This document describes a simple mechanism to treat\n the broadcast network as a point-to-point connection from the\n standpoint of IP routing.\n\n1. Introduction\n\n Point-to-point and broadcast are the two predominant circuit types\n used by link state routing protocols such as IS-IS [ISO10589]\n [RFC1195] and OSPF [RFC2328] [RFC5340]. They are treated differently\n with respect to establishing neighbor adjacencies, flooding link\n state information, representing the topology, and calculating the\n Shortest Path First (SPF) and protocol packets. The most important\n differences are that broadcast circuits utilize the concept of a\n d 5309 key management path presentation nested-reference unchanged"},{"id":"IETF RFC 5310","type":"specification","body":"IETF","designation":"RFC 5310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5310.txt","https://www.rfc-editor.org/rfc/rfc5310.pdf"],"folder":"IETF/RFC-5310","files":{"txt":{"path":"standards/IETF/RFC-5310/RFC-5310.txt","sha256":"00ee1bd62e1edbb87afb5eb16a851c437ea68b1ee3881792376e9d65a9367dc3"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an extension to Intermediate System to\n Intermediate System (IS-IS) to allow the use of any cryptographic\n authentication algorithm in addition to the already-documented\n authentication schemes, described in the base specification and RFC\n 5304. IS-IS is specified in International Standards Organization\n (ISO) 10589, with extensions to support Internet Protocol version 4\n (IPv4) described in RFC 1195.\n\nBhatia, et al. Standards Track [Page 1]\n\f\nRFC 5310 IS-IS Generic Crypto Authentication February 2009\n\n Although this document has been written specifically for using the\n Hashed Message Authentication Code (HMAC) construct along with the\n Secure Hash Algorithm (SHA) family of cryptographic hash functions,\n the method described in this document is generic and can be used to\n extend IS-IS to support any cryptographic hash function in the\n future.","scope_keywords":["5310","algorithm","authentication","hash","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 5310 This document proposes an extension to Intermediate System to\n Intermediate System (IS-IS) to allow the use of any cryptographic\n authentication algorithm in addition to the already-documented\n authentication schemes, described in the base specification and RFC\n 5304. IS-IS is specified in International Standards Organization\n (ISO) 10589, with extensions to support Internet Protocol version 4\n (IPv4) described in RFC 1195.\n\nBhatia, et al. Standards Track [Page 1]\n\f\nRFC 5310 IS-IS Generic Crypto Authentication February 2009\n\n Although this document has been written specifically for using the\n Hashed Message Authentication Code (HMAC) construct along with the\n Secure Hash Algorithm (SHA) family of cryptographic hash functions,\n the method described in this document is generic and can be used to\n extend IS-IS to support any cryptographic hash function in the\n future. 5310 algorithm authentication hash http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5316","type":"specification","body":"IETF","designation":"RFC 5316","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5316.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5316.txt","https://www.rfc-editor.org/rfc/rfc5316.pdf"],"folder":"IETF/RFC-5316","files":{"txt":{"path":"standards/IETF/RFC-5316/RFC-5316.txt","sha256":"659916309a5d18ac3801278917057c91fefcccc8593377b2a73f56ba7549ccb4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the ISIS (ISIS) protocol to\n support Multiprotocol Label Switching (MPLS) and Generalized MPLS\n (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems\n (ASes). It defines ISIS-TE extensions for the flooding of TE\n information about inter-AS links, which can be used to perform inter-\n AS TE path computation.\n\n No support for flooding information from within one AS to another AS\n is proposed or defined in this document.\n\nChen, et al. Standards Track [Page 1]\n\f\nRFC 5316 ISIS Extensions for Inter-AS TE December 2008","scope_keywords":["5316","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5316 This document describes extensions to the ISIS (ISIS) protocol to\n support Multiprotocol Label Switching (MPLS) and Generalized MPLS\n (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems\n (ASes). It defines ISIS-TE extensions for the flooding of TE\n information about inter-AS links, which can be used to perform inter-\n AS TE path computation.\n\n No support for flooding information from within one AS to another AS\n is proposed or defined in this document.\n\nChen, et al. Standards Track [Page 1]\n\f\nRFC 5316 ISIS Extensions for Inter-AS TE December 2008 5316 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5330","type":"specification","body":"IETF","designation":"RFC 5330","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5330.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5330.txt","https://www.rfc-editor.org/rfc/rfc5330.pdf"],"folder":"IETF/RFC-5330","files":{"txt":{"path":"standards/IETF/RFC-5330/RFC-5330.txt","sha256":"10bba056da54020d567c2798f84bf9c030b67fa891dca559e3c62ccb8e312fae"}},"tags":["nested-reference","unchanged"],"summary":"Several Link-type sub-Type-Length-Values (sub-TLVs) have been defined\n for Open Shortest Path First (OSPF) and Intermediate System to\n Intermediate System (IS-IS) in the context of Multiprotocol Label\n Switching (MPLS) Traffic Engineering (TE), in order to advertise some\n link characteristics such as the available bandwidth, traffic\n engineering metric, administrative group, and so on. By making\n statistical assumptions about the aggregated traffic carried onto a\n set of TE Label Switched Paths (LSPs) signalled with zero bandwidth\n (referred to as \"unconstrained TE LSP\" in this document), algorithms\n can be designed to load balance (existing or newly configured)\n unconstrained TE LSP across a set of equal cost paths. This requires\n knowledge of the number of unconstrained TE LSPs signalled across a\n link. This document specifies a new Link-type Traffic Engineering\n sub-TLV used to advert","scope_keywords":["5330","algorithm","algorithms","key","management","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null}],"search_text":"IETF RFC 5330 Several Link-type sub-Type-Length-Values (sub-TLVs) have been defined\n for Open Shortest Path First (OSPF) and Intermediate System to\n Intermediate System (IS-IS) in the context of Multiprotocol Label\n Switching (MPLS) Traffic Engineering (TE), in order to advertise some\n link characteristics such as the available bandwidth, traffic\n engineering metric, administrative group, and so on. By making\n statistical assumptions about the aggregated traffic carried onto a\n set of TE Label Switched Paths (LSPs) signalled with zero bandwidth\n (referred to as \"unconstrained TE LSP\" in this document), algorithms\n can be designed to load balance (existing or newly configured)\n unconstrained TE LSP across a set of equal cost paths. This requires\n knowledge of the number of unconstrained TE LSPs signalled across a\n link. This document specifies a new Link-type Traffic Engineering\n sub-TLV used to advert 5330 algorithm algorithms key management path risk nested-reference unchanged"},{"id":"IETF RFC 5565","type":"specification","body":"IETF","designation":"RFC 5565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5565.txt","https://www.rfc-editor.org/rfc/rfc5565.pdf"],"folder":"IETF/RFC-5565","files":{"txt":{"path":"standards/IETF/RFC-5565/RFC-5565.txt","sha256":"d759bc197e00dbefb9594cbb382fa1bfa7c37df684074b7d9cf934e1e9205290"}},"tags":["nested-reference","unchanged"],"summary":"The Internet needs to be able to handle both IPv4 and IPv6 packets.\n However, it is expected that some constituent networks of the\n Internet will be \"single-protocol\" networks. One kind of single-\n protocol network can parse only IPv4 packets and can process only\n IPv4 routing information; another kind can parse only IPv6 packets\n and can process only IPv6 routing information. It is nevertheless\n required that either kind of single-protocol network be able to\n provide transit service for the \"other\" protocol. This is done by\n passing the \"other kind\" of routing information from one edge of the\n single-protocol network to the other, and by tunneling the \"other\n kind\" of data packet from one edge to the other. The tunnels are\n known as \"softwires\". This framework document explains how the\n routing information and the data packets of one protocol are passed\n through a single-protocol networ","scope_keywords":["5565","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null}],"search_text":"IETF RFC 5565 The Internet needs to be able to handle both IPv4 and IPv6 packets.\n However, it is expected that some constituent networks of the\n Internet will be \"single-protocol\" networks. One kind of single-\n protocol network can parse only IPv4 packets and can process only\n IPv4 routing information; another kind can parse only IPv6 packets\n and can process only IPv6 routing information. It is nevertheless\n required that either kind of single-protocol network be able to\n provide transit service for the \"other\" protocol. This is done by\n passing the \"other kind\" of routing information from one edge of the\n single-protocol network to the other, and by tunneling the \"other\n kind\" of data packet from one edge to the other. The tunnels are\n known as \"softwires\". This framework document explains how the\n routing information and the data packets of one protocol are passed\n through a single-protocol networ 5565 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5882","type":"specification","body":"IETF","designation":"RFC 5882","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5882.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5882.txt","https://www.rfc-editor.org/rfc/rfc5882.pdf"],"folder":"IETF/RFC-5882","files":{"txt":{"path":"standards/IETF/RFC-5882/RFC-5882.txt","sha256":"d396c82bd18c9ba5d4d186ecdb05658518979b16228cce616371f07a6401e210"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the generic application of the Bidirectional\n Forwarding Detection (BFD) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5882.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (","scope_keywords":["5882","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5882 This document describes the generic application of the Bidirectional\n Forwarding Detection (BFD) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5882.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n ( 5882 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6165","type":"specification","body":"IETF","designation":"RFC 6165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6165.txt","https://www.rfc-editor.org/rfc/rfc6165.pdf"],"folder":"IETF/RFC-6165","files":{"txt":{"path":"standards/IETF/RFC-6165/RFC-6165.txt","sha256":"21859646f310dd6bef4cd0d84c2a2e176862ee77147d0e196274640e55e5ec40"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Intermediate System to Intermediate\n System (IS-IS) extensions necessary to support link state routing for\n any protocols running directly over Layer-2. While supporting this\n concept involves several pieces, this document only describes\n extensions to IS-IS. Furthermore, the Type, Length, Value pairs\n (TLVs) described in this document are generic Layer-2 additions, and\n specific ones as needed are defined in the IS-IS technology-specific\n extensions. We leave it to the systems using these IS-IS extensions\n to explain how the information carried in IS-IS is used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steerin","scope_keywords":["6165","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null}],"search_text":"IETF RFC 6165 This document specifies the Intermediate System to Intermediate\n System (IS-IS) extensions necessary to support link state routing for\n any protocols running directly over Layer-2. While supporting this\n concept involves several pieces, this document only describes\n extensions to IS-IS. Furthermore, the Type, Length, Value pairs\n (TLVs) described in this document are generic Layer-2 additions, and\n specific ones as needed are defined in the IS-IS technology-specific\n extensions. We leave it to the systems using these IS-IS extensions\n to explain how the information carried in IS-IS is used.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steerin 6165 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6213","type":"specification","body":"IETF","designation":"RFC 6213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6213.txt","https://www.rfc-editor.org/rfc/rfc6213.pdf"],"folder":"IETF/RFC-6213","files":{"txt":{"path":"standards/IETF/RFC-6213/RFC-6213.txt","sha256":"3e0a184be259b4bca3e417cb099e4ff28ef8748e66bfe001325dd559218f083f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a type-length-value (TLV) for use in the IS-\n IS routing protocol that allows for the proper use of the\n Bidirectional Forwarding Detection (BFD) protocol. There exist\n certain scenarios in which IS-IS will not react appropriately to a\n BFD-detected forwarding plane failure without use of either this TLV\n or some other method.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o","scope_keywords":["6213","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null}],"search_text":"IETF RFC 6213 This document describes a type-length-value (TLV) for use in the IS-\n IS routing protocol that allows for the proper use of the\n Bidirectional Forwarding Detection (BFD) protocol. There exist\n certain scenarios in which IS-IS will not react appropriately to a\n BFD-detected forwarding plane failure without use of either this TLV\n or some other method.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o 6213 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6326","type":"specification","body":"IETF","designation":"RFC 6326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6326.txt","https://www.rfc-editor.org/rfc/rfc6326.pdf"],"folder":"IETF/RFC-6326","files":{"txt":{"path":"standards/IETF/RFC-6326/RFC-6326.txt","sha256":"f1a578b42131e8fa61b4d1c1fb90e521602e4efb1f1f646609591e56c45345ec"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has standardized the Transparent Interconnection of Lots of\n Links (TRILL) protocol, which provides transparent Layer 2 forwarding\n using encapsulation with a hop count and IS-IS link state routing.\n This document specifies the data formats and code points for the\n IS-IS extensions to support TRILL.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6326.\n\nCopyright Notice\n\n Copyri","scope_keywords":["6326","http","key","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null}],"search_text":"IETF RFC 6326 The IETF has standardized the Transparent Interconnection of Lots of\n Links (TRILL) protocol, which provides transparent Layer 2 forwarding\n using encapsulation with a hop count and IS-IS link state routing.\n This document specifies the data formats and code points for the\n IS-IS extensions to support TRILL.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6326.\n\nCopyright Notice\n\n Copyri 6326 http key license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6327","type":"specification","body":"IETF","designation":"RFC 6327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6327.txt","https://www.rfc-editor.org/rfc/rfc6327.pdf"],"folder":"IETF/RFC-6327","files":{"txt":{"path":"standards/IETF/RFC-6327/RFC-6327.txt","sha256":"344c77bf5c98dba1cba6f468ae198206a3368c076d45c8ae51bbfd3a6df18443"}},"tags":["nested-reference","unchanged"],"summary":"The IETF TRILL (TRansparent Interconnection of Lots of Links)\n protocol provides optimal pair-wise data forwarding without\n configuration, safe forwarding even during periods of temporary\n loops, and support for multipathing of both unicast and multicast\n traffic. TRILL accomplishes this by using IS-IS (Intermediate System\n to Intermediate System) link state routing and by encapsulating\n traffic using a header that includes a hop count. Devices that\n implement TRILL are called Routing Bridges (RBridges).\n\n TRILL supports multi-access LAN (Local Area Network) links that can\n have multiple end stations and RBridges attached. This document\n describes four aspects of the TRILL LAN Hello protocol used on such\n links, particularly adjacency, designated RBridge selection, and MTU\n (Maximum Transmission Unit) and pseudonode procedures, with state\n machines. There is no change for IS-IS point-to-","scope_keywords":["6327","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 6327 The IETF TRILL (TRansparent Interconnection of Lots of Links)\n protocol provides optimal pair-wise data forwarding without\n configuration, safe forwarding even during periods of temporary\n loops, and support for multipathing of both unicast and multicast\n traffic. TRILL accomplishes this by using IS-IS (Intermediate System\n to Intermediate System) link state routing and by encapsulating\n traffic using a header that includes a hop count. Devices that\n implement TRILL are called Routing Bridges (RBridges).\n\n TRILL supports multi-access LAN (Local Area Network) links that can\n have multiple end stations and RBridges attached. This document\n describes four aspects of the TRILL LAN Hello protocol used on such\n links, particularly adjacency, designated RBridge selection, and MTU\n (Maximum Transmission Unit) and pseudonode procedures, with state\n machines. There is no change for IS-IS point-to- 6327 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6518","type":"specification","body":"IETF","designation":"RFC 6518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6518.txt","https://www.rfc-editor.org/rfc/rfc6518.pdf"],"folder":"IETF/RFC-6518","files":{"txt":{"path":"standards/IETF/RFC-6518/RFC-6518.txt","sha256":"7999af0daaf246d7f635038f136b8e334735988a7aecf6643086dc9000a60ba8"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a series concerned with defining a roadmap of\n protocol specification work for the use of modern cryptographic\n mechanisms and algorithms for message authentication in routing\n protocols. In particular, it defines the framework for a key\n management protocol that may be used to create and manage session\n keys for message authentication and integrity.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th","scope_keywords":["6518","algorithm","algorithms","authentication","authorization","http","key","keys","license","management","risk","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 6518 This document is one of a series concerned with defining a roadmap of\n protocol specification work for the use of modern cryptographic\n mechanisms and algorithms for message authentication in routing\n protocols. In particular, it defines the framework for a key\n management protocol that may be used to create and manage session\n keys for message authentication and integrity.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th 6518 algorithm algorithms authentication authorization http key keys license management risk subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6551","type":"specification","body":"IETF","designation":"RFC 6551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6551.txt","https://www.rfc-editor.org/rfc/rfc6551.pdf"],"folder":"IETF/RFC-6551","files":{"txt":{"path":"standards/IETF/RFC-6551/RFC-6551.txt","sha256":"36b4fe78096b5dd9003b7274cfb969c439bae04dabd5efcb30c2488603e51cac"}},"tags":["nested-reference","unchanged"],"summary":"Low-Power and Lossy Networks (LLNs) have unique characteristics\n compared with traditional wired and ad hoc networks that require the\n specification of new routing metrics and constraints. By contrast,\n with typical Interior Gateway Protocol (IGP) routing metrics using\n hop counts or link metrics, this document specifies a set of link and\n node routing metrics and constraints suitable to LLNs to be used by\n the Routing Protocol for Low-Power and Lossy Networks (RPL).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr","scope_keywords":["6551","attribute","attributes","http","key","license","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6552","folder":"IETF/RFC-6552","source":"IETF/RFC-6552/RFC-6552.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null}],"search_text":"IETF RFC 6551 Low-Power and Lossy Networks (LLNs) have unique characteristics\n compared with traditional wired and ad hoc networks that require the\n specification of new routing metrics and constraints. By contrast,\n with typical Interior Gateway Protocol (IGP) routing metrics using\n hop counts or link metrics, this document specifies a set of link and\n node routing metrics and constraints suitable to LLNs to be used by\n the Routing Protocol for Low-Power and Lossy Networks (RPL).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curr 6551 attribute attributes http key license path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 6862","type":"specification","body":"IETF","designation":"RFC 6862","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6862.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6862.txt","https://www.rfc-editor.org/rfc/rfc6862.pdf"],"folder":"IETF/RFC-6862","files":{"txt":{"path":"standards/IETF/RFC-6862/RFC-6862.txt","sha256":"6b522aa13bdb329c9def68e7da927a1c422137f5f8d90ecfd750556109960e25"}},"tags":["nested-reference","unchanged"],"summary":"Different routing protocols employ different mechanisms for securing\n protocol packets on the wire. While most already have some method\n for accomplishing cryptographic message authentication, in many cases\n the existing methods are dated, vulnerable to attack, and employ\n cryptographic algorithms that have been deprecated. The \"Keying and\n Authentication for Routing Protocols\" (KARP) effort aims to overhaul\n and improve these mechanisms. This document does not contain\n protocol specifications. Instead, it defines the areas where\n protocol specification work is needed. This document is a companion\n document to RFC 6518, \"Keying and Authentication for Routing\n Protocols (KARP) Design Guidelines\"; together they form the guidance\n and instruction KARP design teams will use to review and overhaul\n routing protocol transport security.\n\nStatus of This Memo\n\n This document is not an Internet St","scope_keywords":["6862","algorithm","algorithms","authentication","holder","http","key","license","risk","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null}],"search_text":"IETF RFC 6862 Different routing protocols employ different mechanisms for securing\n protocol packets on the wire. While most already have some method\n for accomplishing cryptographic message authentication, in many cases\n the existing methods are dated, vulnerable to attack, and employ\n cryptographic algorithms that have been deprecated. The \"Keying and\n Authentication for Routing Protocols\" (KARP) effort aims to overhaul\n and improve these mechanisms. This document does not contain\n protocol specifications. Instead, it defines the areas where\n protocol specification work is needed. This document is a companion\n document to RFC 6518, \"Keying and Authentication for Routing\n Protocols (KARP) Design Guidelines\"; together they form the guidance\n and instruction KARP design teams will use to review and overhaul\n routing protocol transport security.\n\nStatus of This Memo\n\n This document is not an Internet St 6862 algorithm algorithms authentication holder http key license risk subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7177","type":"specification","body":"IETF","designation":"RFC 7177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7177.txt","https://www.rfc-editor.org/rfc/rfc7177.pdf"],"folder":"IETF/RFC-7177","files":{"txt":{"path":"standards/IETF/RFC-7177/RFC-7177.txt","sha256":"c7902693a1b85ab0985d1df6b9ba4a1a4e72e18d2923d049ff3f42ffa5b321c0"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol supports arbitrary link technologies between TRILL switches,\n including point-to-point links and multi-access Local Area Network\n (LAN) links that can have multiple TRILL switches and end stations\n attached. TRILL uses Intermediate System to Intermediate System\n (IS-IS) routing. This document specifies the establishment,\n reporting, and termination of IS-IS adjacencies between TRILL\n switches, also known as RBridges (Routing Bridges). It also concerns\n four other link-local aspects of TRILL: Designated RBridge (DRB)\n selection, MTU (Maximum Transmission Unit) testing, pseudonode\n creation, and BFD (Bidirectional Forwarding Detection) session\n bootstrapping in connection with adjacency. State diagrams are\n included where appropriate. This document obsoletes RFC 6327 and\n updates RFC 6325.\n\nStatus of This Memo\n\n This i","scope_keywords":["7177","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7177 The IETF Transparent Interconnection of Lots of Links (TRILL)\n protocol supports arbitrary link technologies between TRILL switches,\n including point-to-point links and multi-access Local Area Network\n (LAN) links that can have multiple TRILL switches and end stations\n attached. TRILL uses Intermediate System to Intermediate System\n (IS-IS) routing. This document specifies the establishment,\n reporting, and termination of IS-IS adjacencies between TRILL\n switches, also known as RBridges (Routing Bridges). It also concerns\n four other link-local aspects of TRILL: Designated RBridge (DRB)\n selection, MTU (Maximum Transmission Unit) testing, pseudonode\n creation, and BFD (Bidirectional Forwarding Detection) session\n bootstrapping in connection with adjacency. State diagrams are\n included where appropriate. This document obsoletes RFC 6327 and\n updates RFC 6325.\n\nStatus of This Memo\n\n This i 7177 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7178","type":"specification","body":"IETF","designation":"RFC 7178","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7178.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7178.txt","https://www.rfc-editor.org/rfc/rfc7178.pdf"],"folder":"IETF/RFC-7178","files":{"txt":{"path":"standards/IETF/RFC-7178/RFC-7178.txt","sha256":"b808eaae6d0e82f86ead4d1c173d3f8ff5dc4d20f909dd1c8269255fbcfefc39"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a general channel mechanism for sending\n messages, such as Bidirectional Forwarding Detection (BFD) messages,\n between Routing Bridges (RBridges) and between RBridges and end\n stations in an RBridge campus through extensions to the Transparent\n Interconnection of Lots of Links (TRILL) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7178.\n\nEastlake, et al","scope_keywords":["7178","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 7178 This document specifies a general channel mechanism for sending\n messages, such as Bidirectional Forwarding Detection (BFD) messages,\n between Routing Bridges (RBridges) and between RBridges and end\n stations in an RBridge campus through extensions to the Transparent\n Interconnection of Lots of Links (TRILL) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7178.\n\nEastlake, et al 7178 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 1288","type":"specification","body":"IETF","designation":"RFC 1288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1288.txt","https://www.rfc-editor.org/rfc/rfc1288.pdf"],"folder":"IETF/RFC-1288","files":{"txt":{"path":"standards/IETF/RFC-1288/RFC-1288.txt","sha256":"39421e981f98f342fc314d03cc07f2797f7e092a26d43428897f05b88b22939c"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the Finger user information protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition.\n\n This edition corrects and clarifies RFC 1196.","scope_keywords":["1288","audit","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2458","folder":"IETF/RFC-2458","source":"IETF/RFC-2458/RFC-2458.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1288 This memo describes the Finger user information protocol. This is a\n simple protocol which provides an interface to a remote user\n information program.\n\n Based on RFC 742, a description of the original Finger protocol, this\n memo attempts to clarify the expected communication between the two\n ends of a Finger connection. It also tries not to invalidate the\n many existing implementations or add unnecessary restrictions to the\n original protocol definition.\n\n This edition corrects and clarifies RFC 1196. 1288 audit policy nested-reference unchanged"},{"id":"IETF RFC 1198","type":"specification","body":"IETF","designation":"RFC 1198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1198.txt","https://www.rfc-editor.org/rfc/rfc1198.pdf"],"folder":"IETF/RFC-1198","files":{"txt":{"path":"standards/IETF/RFC-1198/RFC-1198.txt","sha256":"8695d9f8fbfa6c0be97424392dcd5ec8be8658e2671e338ffbc4f4c34c8d4967"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Scheifler\nRequest for Comments: 1198 MIT Laboratory for Computer Science\nFYI: 6 January 1991\n\n FYI on the X Window System\n\nStatus of this Memo\n\n This FYI RFC provides pointers to the published standards of the MIT\n X Consortium. This memo provides information for the Internet\n community. It does not specify any Internet standard. Distribution\n of this memo is unlimited.\n\nThe following documents are standards of the MIT X Consortium:\n\n X Window System Protocol\n X Version 11, Release 4\n Robert W. Scheifler\n\n Xlib - C Language X Interface\n X Version 11, Release 4\n James Gettys, Robert W. Scheifler, Ron Newman\n\n X Toolkit Intrinsics - C Language Interface\n X Version 11, Release 4\n Joel McCormack, Paul Asente, Ralph R. Swick\n\n Bitmap Distribution Format\n Version 2.1\n\n Inter-Client Communication Conventions Manual\n Version 1.0\n David S. H. Rosenthal\n\n Compound Text Enc","scope_keywords":["1198","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null}],"search_text":"IETF RFC 1198 Network Working Group B. Scheifler\nRequest for Comments: 1198 MIT Laboratory for Computer Science\nFYI: 6 January 1991\n\n FYI on the X Window System\n\nStatus of this Memo\n\n This FYI RFC provides pointers to the published standards of the MIT\n X Consortium. This memo provides information for the Internet\n community. It does not specify any Internet standard. Distribution\n of this memo is unlimited.\n\nThe following documents are standards of the MIT X Consortium:\n\n X Window System Protocol\n X Version 11, Release 4\n Robert W. Scheifler\n\n Xlib - C Language X Interface\n X Version 11, Release 4\n James Gettys, Robert W. Scheifler, Ron Newman\n\n X Toolkit Intrinsics - C Language Interface\n X Version 11, Release 4\n Joel McCormack, Paul Asente, Ralph R. Swick\n\n Bitmap Distribution Format\n Version 2.1\n\n Inter-Client Communication Conventions Manual\n Version 1.0\n David S. H. Rosenthal\n\n Compound Text Enc 1198 subject nested-reference unchanged"},{"id":"IETF RFC 2497","type":"specification","body":"IETF","designation":"RFC 2497","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2497.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2497.txt","https://www.rfc-editor.org/rfc/rfc2497.pdf"],"folder":"IETF/RFC-2497","files":{"txt":{"path":"standards/IETF/RFC-2497/RFC-2497.txt","sha256":"e9e3236bcdeeb19e8c7c5be22fc54a0ca4ab9315e15a10beaf15b726030ece55"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group I. Souvatzis\nRequest for Comments: 2497 The NetBSD Project\nSee Also: 1201 January 1999\nCategory: Standards Track\n\n Transmission of IPv6 Packets over ARCnet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo specifies a frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local and statelessly\n autoconfigured addresses on ARCnet networks. It also specifies the\n content of the Source/Target Link-layer Addr","scope_keywords":["2497","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2497 Network Working Group I. Souvatzis\nRequest for Comments: 2497 The NetBSD Project\nSee Also: 1201 January 1999\nCategory: Standards Track\n\n Transmission of IPv6 Packets over ARCnet Networks\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo specifies a frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local and statelessly\n autoconfigured addresses on ARCnet networks. It also specifies the\n content of the Source/Target Link-layer Addr 2497 http key management nested-reference unchanged"},{"id":"IETF RFC 1202","type":"specification","body":"IETF","designation":"RFC 1202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1202.txt","https://www.rfc-editor.org/rfc/rfc1202.pdf"],"folder":"IETF/RFC-1202","files":{"txt":{"path":"standards/IETF/RFC-1202/RFC-1202.txt","sha256":"98f51e7d8af7db71ec91457a4c51d855079b209514982825ea5d180eb7034a9f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1202 Performance Systems International, Inc.\n February 1991\n\n Directory Assistance Service\n\nStatus of this Memo\n\n This document defines a mechanism by which a user-interface may\n access a textual DAP-like interface over a TCP/IP connection. This\n is a local mechanism. This memo provides information for the\n Internet community. It does not specify any standard. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 1.1 An Aside ............................................ 3\n 2. Protocol .............................................. 3\n 2.1 Control Connection .................................. 4\n 2.1.1 Initialization .................................... 4\n 2.1.2 Transactions ...................................... 4\n 2.1.2.1 INTR command ..................................","scope_keywords":["1202"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1249","folder":"IETF/RFC-1249","source":"IETF/RFC-1249/RFC-1249.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1487","folder":"IETF/RFC-1487","source":"IETF/RFC-1487/RFC-1487.txt","version":null},{"body":"IETF","designation":"RFC 1777","folder":"IETF/RFC-1777","source":"IETF/RFC-1777/RFC-1777.txt","version":null}],"search_text":"IETF RFC 1202 Network Working Group M. Rose\nRequest for Comments: 1202 Performance Systems International, Inc.\n February 1991\n\n Directory Assistance Service\n\nStatus of this Memo\n\n This document defines a mechanism by which a user-interface may\n access a textual DAP-like interface over a TCP/IP connection. This\n is a local mechanism. This memo provides information for the\n Internet community. It does not specify any standard. Distribution\n of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .......................................... 1\n 1.1 An Aside ............................................ 3\n 2. Protocol .............................................. 3\n 2.1 Control Connection .................................. 4\n 2.1.1 Initialization .................................... 4\n 2.1.2 Transactions ...................................... 4\n 2.1.2.1 INTR command .................................. 1202 nested-reference unchanged"},{"id":"IETF RFC 1249","type":"specification","body":"IETF","designation":"RFC 1249","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1249.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1249.txt","https://www.rfc-editor.org/rfc/rfc1249.pdf"],"folder":"IETF/RFC-1249","files":{"txt":{"path":"standards/IETF/RFC-1249/RFC-1249.txt","sha256":"9458f4f8c926a049b05e44f1dbb5a574eac1afa23288fbfd0153e962e34e985d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 1249 M. Smith\n B. Beecher\n University of Michigan\n August 1991\n\n DIXIE Protocol Specification\n\nStatus of this Memo\n\n This RFC defines a mechanism by which TCP/UDP based clients can\n access OSI Directory Service without the overhead of the ISO\n transport and presentation protocols required to implement full-blown\n DAP. This memo provides information for the Internet community. It\n does not specify any standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 2\n 1.1 History .................................................. 2\n 2. Protocol .................................................. 2\n 2.1 Header ................................................... 3\n 2.2 Operations ............................................... 4\n 2.2.1 Read ..............................","scope_keywords":["1249","attribute","attributes","authentication","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1487","folder":"IETF/RFC-1487","source":"IETF/RFC-1487/RFC-1487.txt","version":null},{"body":"IETF","designation":"RFC 1777","folder":"IETF/RFC-1777","source":"IETF/RFC-1777/RFC-1777.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1249 Network Working Group T. Howes\nRequest for Comments: 1249 M. Smith\n B. Beecher\n University of Michigan\n August 1991\n\n DIXIE Protocol Specification\n\nStatus of this Memo\n\n This RFC defines a mechanism by which TCP/UDP based clients can\n access OSI Directory Service without the overhead of the ISO\n transport and presentation protocols required to implement full-blown\n DAP. This memo provides information for the Internet community. It\n does not specify any standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 2\n 1.1 History .................................................. 2\n 2. Protocol .................................................. 2\n 2.1 Header ................................................... 3\n 2.2 Operations ............................................... 4\n 2.2.1 Read .............................. 1249 attribute attributes authentication presentation nested-reference unchanged"},{"id":"IETF RFC 1487","type":"specification","body":"IETF","designation":"RFC 1487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1487.txt","https://www.rfc-editor.org/rfc/rfc1487.pdf"],"folder":"IETF/RFC-1487","files":{"txt":{"path":"standards/IETF/RFC-1487/RFC-1487.txt","sha256":"74b168f47524daeba659e5e54bfc6ee7fbbadc55597a137f9f00625caf32039f"}},"tags":["nested-reference","unchanged"],"summary":"The protocol described in this document is designed to provide access\n to the Directory while not incurring the resource requirements of the\n Directory Access Protocol (DAP). This protocol is specifically\n targeted at simple management applications and browser applications\n that provide simple read/write interactive access to the Directory,\n and is intended to be a complement to the DAP itself.\n\n Key aspects of LDAP are:\n\n - Protocol elements are carried directly over TCP or other transport,\n bypassing much of the session/presentation overhead.\n\n - Many protocol data elements are encoding as ordinary strings (e.g.,\n Distinguished Names).\n\n - A lightweight BER encoding is used to encode all protocol elements.\n\n1. History\n\n The tremendous interest in X.500 [1,2] technology in the Internet has\n lead to efforts to reduce the high \"cost of entry\" associated with\n use of the technology, such a","scope_keywords":["1487","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1558","folder":"IETF/RFC-1558","source":"IETF/RFC-1558/RFC-1558.txt","version":null},{"body":"IETF","designation":"RFC 1798","folder":"IETF/RFC-1798","source":"IETF/RFC-1798/RFC-1798.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null}],"search_text":"IETF RFC 1487 The protocol described in this document is designed to provide access\n to the Directory while not incurring the resource requirements of the\n Directory Access Protocol (DAP). This protocol is specifically\n targeted at simple management applications and browser applications\n that provide simple read/write interactive access to the Directory,\n and is intended to be a complement to the DAP itself.\n\n Key aspects of LDAP are:\n\n - Protocol elements are carried directly over TCP or other transport,\n bypassing much of the session/presentation overhead.\n\n - Many protocol data elements are encoding as ordinary strings (e.g.,\n Distinguished Names).\n\n - A lightweight BER encoding is used to encode all protocol elements.\n\n1. History\n\n The tremendous interest in X.500 [1,2] technology in the Internet has\n lead to efforts to reduce the high \"cost of entry\" associated with\n use of the technology, such a 1487 key management presentation nested-reference unchanged"},{"id":"IETF RFC 1777","type":"specification","body":"IETF","designation":"RFC 1777","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1777.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1777.txt","https://www.rfc-editor.org/rfc/rfc1777.pdf"],"folder":"IETF/RFC-1777","files":{"txt":{"path":"standards/IETF/RFC-1777/RFC-1777.txt","sha256":"f7d33313cb771e4659cded644fd0a5ec609dd7738990c6b4bb19c67c88444065"}},"tags":["nested-reference","unchanged"],"summary":"The protocol described in this document is designed to provide access\n to the X.500 Directory while not incurring the resource requirements\n of the Directory Access Protocol (DAP). This protocol is specifically\n targeted at simple management applications and browser applications\n that provide simple read/write interactive access to the X.500\n Directory, and is intended to be a complement to the DAP itself.\n\n Key aspects of LDAP are:\n\n - Protocol elements are carried directly over TCP or other transport,\n bypassing much of the session/presentation overhead.\n\n - Many protocol data elements are encoding as ordinary strings (e.g.,\n Distinguished Names).\n\n - A lightweight BER encoding is used to encode all protocol elements.\n\n1. History\n\n The tremendous interest in X.500 [1,2] technology in the Internet has\n lead to efforts to reduce the high \"cost of entry\" associated with\n use of the techno","scope_keywords":["1777","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 1779","folder":"IETF/RFC-1779","source":"IETF/RFC-1779/RFC-1779.txt","version":null},{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null},{"body":"IETF","designation":"RFC 1960","folder":"IETF/RFC-1960","source":"IETF/RFC-1960/RFC-1960.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2559","folder":"IETF/RFC-2559","source":"IETF/RFC-2559/RFC-2559.txt","version":null},{"body":"IETF","designation":"RFC 2587","folder":"IETF/RFC-2587","source":"IETF/RFC-2587/RFC-2587.txt","version":null},{"body":"IETF","designation":"RFC 2657","folder":"IETF/RFC-2657","source":"IETF/RFC-2657/RFC-2657.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 1777 The protocol described in this document is designed to provide access\n to the X.500 Directory while not incurring the resource requirements\n of the Directory Access Protocol (DAP). This protocol is specifically\n targeted at simple management applications and browser applications\n that provide simple read/write interactive access to the X.500\n Directory, and is intended to be a complement to the DAP itself.\n\n Key aspects of LDAP are:\n\n - Protocol elements are carried directly over TCP or other transport,\n bypassing much of the session/presentation overhead.\n\n - Many protocol data elements are encoding as ordinary strings (e.g.,\n Distinguished Names).\n\n - A lightweight BER encoding is used to encode all protocol elements.\n\n1. History\n\n The tremendous interest in X.500 [1,2] technology in the Internet has\n lead to efforts to reduce the high \"cost of entry\" associated with\n use of the techno 1777 key management presentation nested-reference unchanged"},{"id":"IETF RFC 1204","type":"specification","body":"IETF","designation":"RFC 1204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1204.txt","https://www.rfc-editor.org/rfc/rfc1204.pdf"],"folder":"IETF/RFC-1204","files":{"txt":{"path":"standards/IETF/RFC-1204/RFC-1204.txt","sha256":"4478c262819d5449d382facbc5c4bfa2b11a7e6cfc0cac72fac476b4990c5e72"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Yeh\nRequest for Comments: 1204 D. Lee\n Netix Communications, Inc.\n February 1991\n\n Message Posting Protocol (MPP)\n\nStatus of this Memo\n\n This memo describes a protocol for posting messages from workstations\n (e.g., PCs) to a mail service host. This RFC specifies an\n Experimental Protocol for the Internet community. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. INTRODUCTION\n\n Operating systems for personal computers do not provide a mechanism\n for user authentication. However, such a mechanism is crucial for\n electronic mail system since authenticating message sender's identity\n is important in preventing mail forgery. Hence, adding personal\n computers to an electronic ma","scope_keywords":["1204","authentication","crl","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1204 Network Working Group S. Yeh\nRequest for Comments: 1204 D. Lee\n Netix Communications, Inc.\n February 1991\n\n Message Posting Protocol (MPP)\n\nStatus of this Memo\n\n This memo describes a protocol for posting messages from workstations\n (e.g., PCs) to a mail service host. This RFC specifies an\n Experimental Protocol for the Internet community. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. INTRODUCTION\n\n Operating systems for personal computers do not provide a mechanism\n for user authentication. However, such a mechanism is crucial for\n electronic mail system since authenticating message sender's identity\n is important in preventing mail forgery. Hence, adding personal\n computers to an electronic ma 1204 authentication crl delivery nested-reference unchanged"},{"id":"IETF RFC 1208","type":"specification","body":"IETF","designation":"RFC 1208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1208.txt","https://www.rfc-editor.org/rfc/rfc1208.pdf"],"folder":"IETF/RFC-1208","files":{"txt":{"path":"standards/IETF/RFC-1208/RFC-1208.txt","sha256":"c7d4c902324678385109836d1c4926406075554a22753eb6a57e22211cc17511"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group O. Jacobsen\nRequest for Comments: 1208 D. Lynch\n Interop, Inc.\n March 1991\n\n A Glossary of Networking Terms\n\nStatus of this Memo\n\n This RFC is a glossary adapted from \"The INTEROP Pocket Glossary of\n Networking Terms\" distributed at Interop '90. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nIntroduction\n\n This glossary is adapted from \"The INTEROP Pocket Glossary of\n Networking Terms\" produced to help you understand the many terms--and\n in particular the myriad of acronyms--that can be encountered at the\n INTEROP Tutorials, Conference, and Exhibition.\n\n To keep this document reasonably small we have deliberately omitted\n common computer and communications terms such as disk, modem, byte,\n and VLSI. In addition, the definitions have been kept brief. We\n recommend that yo","scope_keywords":["1208","attribute","attributes","authentication","delivery","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1402","folder":"IETF/RFC-1402","source":"IETF/RFC-1402/RFC-1402.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 1208 Network Working Group O. Jacobsen\nRequest for Comments: 1208 D. Lynch\n Interop, Inc.\n March 1991\n\n A Glossary of Networking Terms\n\nStatus of this Memo\n\n This RFC is a glossary adapted from \"The INTEROP Pocket Glossary of\n Networking Terms\" distributed at Interop '90. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nIntroduction\n\n This glossary is adapted from \"The INTEROP Pocket Glossary of\n Networking Terms\" produced to help you understand the many terms--and\n in particular the myriad of acronyms--that can be encountered at the\n INTEROP Tutorials, Conference, and Exhibition.\n\n To keep this document reasonably small we have deliberately omitted\n common computer and communications terms such as disk, modem, byte,\n and VLSI. In addition, the definitions have been kept brief. We\n recommend that yo 1208 attribute attributes authentication delivery management pid nested-reference unchanged"},{"id":"IETF RFC 3871","type":"specification","body":"IETF","designation":"RFC 3871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3871.txt","https://www.rfc-editor.org/rfc/rfc3871.pdf"],"folder":"IETF/RFC-3871","files":{"txt":{"path":"standards/IETF/RFC-3871/RFC-3871.txt","sha256":"555b061f611ecec852203f124e45803777051459846bd6e733222c5aa10cd4f4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a list of operational security requirements for\n the infrastructure of large Internet Service Provider (ISP) IP\n networks (routers and switches). A framework is defined for\n specifying \"profiles\", which are collections of requirements\n applicable to certain network topology contexts (all, core-only,\n edge-only...). The goal is to provide network operators a clear,\n concise way of communicating their security requirements to vendors.\n\nJones Informational [Page 1]\n\f\nRFC 3871 Operational Security Requirements September 2004","scope_keywords":["3871","algorithm","algorithms","authentication","delivery","management","profile","profiles","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3871 This document defines a list of operational security requirements for\n the infrastructure of large Internet Service Provider (ISP) IP\n networks (routers and switches). A framework is defined for\n specifying \"profiles\", which are collections of requirements\n applicable to certain network topology contexts (all, core-only,\n edge-only...). The goal is to provide network operators a clear,\n concise way of communicating their security requirements to vendors.\n\nJones Informational [Page 1]\n\f\nRFC 3871 Operational Security Requirements September 2004 3871 algorithm algorithms authentication delivery management profile profiles subject timestamp nested-reference unchanged"},{"id":"IETF RFC 1694","type":"specification","body":"IETF","designation":"RFC 1694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1694.txt","https://www.rfc-editor.org/rfc/rfc1694.pdf"],"folder":"IETF/RFC-1694","files":{"txt":{"path":"standards/IETF/RFC-1694/RFC-1694.txt","sha256":"cc44f6dcc7fb75394c933090be4966e6f6bd19291468269a920dd34c8020721b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing objects for SMDS\n access interfaces. This includes the following access protocols:\n\n SIP [13]\n SIP/DXI [18] and [20]\n SIP/FR [19]\n SIP/ATM [24]\n\n This memo replaces RFC 1304 [12], and defines a MIB module which is\n both compliant to the SNMPv2 SMI and semantically-identical to the\n existing RFC 1304-based definitions.\n\n This memo also assumes application of the MIB II Interfaces group as\n defined in [9].","scope_keywords":["1694","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1694 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing objects for SMDS\n access interfaces. This includes the following access protocols:\n\n SIP [13]\n SIP/DXI [18] and [20]\n SIP/FR [19]\n SIP/ATM [24]\n\n This memo replaces RFC 1304 [12], and defines a MIB module which is\n both compliant to the SNMPv2 SMI and semantically-identical to the\n existing RFC 1304-based definitions.\n\n This memo also assumes application of the MIB II Interfaces group as\n defined in [9]. 1694 management subject nested-reference unchanged"},{"id":"IETF RFC 1735","type":"specification","body":"IETF","designation":"RFC 1735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1735.txt","https://www.rfc-editor.org/rfc/rfc1735.pdf"],"folder":"IETF/RFC-1735","files":{"txt":{"path":"standards/IETF/RFC-1735/RFC-1735.txt","sha256":"f2e3969a699d1a29915c3a972c1a30b9337ed9c816ccd2d8246101bb9c02ed63"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Heinanen\nRequest for Comments: 1735 Telecom Finland\nCategory: Experimental R. Govindan\n ISI\n December 1994\n\n NBMA Address Resolution Protocol (NARP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Note that the work contained in this memo does not describe an\n Internet standard. This work represents an early stage in the\n ongoing efforts to resolve direct communication over NBMA subnets.\n It is a suitable experimental protocol for early deployment. It is\n expect that it will be superceded by other work being developed\n within the IETF.\n\nAbstract\n\n This document describes the NBMA Address Resolution Protocol (NARP).\n NARP can be used by a source ","scope_keywords":["1735","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1735 Network Working Group J. Heinanen\nRequest for Comments: 1735 Telecom Finland\nCategory: Experimental R. Govindan\n ISI\n December 1994\n\n NBMA Address Resolution Protocol (NARP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Note that the work contained in this memo does not describe an\n Internet standard. This work represents an early stage in the\n ongoing efforts to resolve direct communication over NBMA subnets.\n It is a suitable experimental protocol for early deployment. It is\n expect that it will be superceded by other work being developed\n within the IETF.\n\nAbstract\n\n This document describes the NBMA Address Resolution Protocol (NARP).\n NARP can be used by a source  1735 policy nested-reference unchanged"},{"id":"IETF RFC 2332","type":"specification","body":"IETF","designation":"RFC 2332","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2332.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2332.txt","https://www.rfc-editor.org/rfc/rfc2332.pdf"],"folder":"IETF/RFC-2332","files":{"txt":{"path":"standards/IETF/RFC-2332/RFC-2332.txt","sha256":"57166a02edd74f22540d5430910375dc44ab85962c3162ff2b7881099dcd3eee"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the NBMA Next Hop Resolution Protocol (NHRP).\n NHRP can be used by a source station (host or router) connected to a\n Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the\n internetworking layer address and NBMA subnetwork addresses of the\n \"NBMA next hop\" towards a destination station. If the destination is\n connected to the NBMA subnetwork, then the NBMA next hop is the\n destination station itself. Otherwise, the NBMA next hop is the\n egress router from the NBMA subnetwork that is \"nearest\" to the\n destination station. NHRP is intended for use in a multiprotocol\n internetworking layer environment over NBMA subnetworks.\n\n Note that while this protocol was developed for use with NBMA\n subnetworks, it is possible, if not likely, that it will be applied\n to BMA subnetworks as well. However, this usage of NHRP is for\n further study.\n\n This document is intende","scope_keywords":["2332","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2335","folder":"IETF/RFC-2335","source":"IETF/RFC-2335/RFC-2335.txt","version":null},{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2603","folder":"IETF/RFC-2603","source":"IETF/RFC-2603/RFC-2603.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 2332 This document describes the NBMA Next Hop Resolution Protocol (NHRP).\n NHRP can be used by a source station (host or router) connected to a\n Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the\n internetworking layer address and NBMA subnetwork addresses of the\n \"NBMA next hop\" towards a destination station. If the destination is\n connected to the NBMA subnetwork, then the NBMA next hop is the\n destination station itself. Otherwise, the NBMA next hop is the\n egress router from the NBMA subnetwork that is \"nearest\" to the\n destination station. NHRP is intended for use in a multiprotocol\n internetworking layer environment over NBMA subnetworks.\n\n Note that while this protocol was developed for use with NBMA\n subnetworks, it is possible, if not likely, that it will be applied\n to BMA subnetworks as well. However, this usage of NHRP is for\n further study.\n\n This document is intende 2332 key path nested-reference unchanged"},{"id":"IETF RFC 2491","type":"specification","body":"IETF","designation":"RFC 2491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2491.txt","https://www.rfc-editor.org/rfc/rfc2491.pdf"],"folder":"IETF/RFC-2491","files":{"txt":{"path":"standards/IETF/RFC-2491/RFC-2491.txt","sha256":"5114a599887f2eb713509fa9f5078e6b3f973792a6f8f3c68dc6894fc16dbf4e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general architecture for IPv6 over NBMA\n networks. It forms the basis for subsidiary companion documents that\n describe details for various specific NBMA technologies (such as ATM\n or Frame Relay). The IPv6 over NBMA architecture allows conventional\n host-side operation of the IPv6 Neighbor Discovery protocol, while\n also supporting the establishment of 'shortcut' NBMA forwarding paths\n when dynamically signaled NBMA links are available. Operations over\n administratively configured Point to Point NBMA links are also\n described.\n\n Dynamic NBMA shortcuts are achieved through the use of IPv6 Neighbor\n Discovery protocol operation within Logical Links, and inter-router\n NHRP for the discovery of off-Link NBMA destinations. Both flow-\n triggered and explicitly source-triggered shortcuts are supported.\n\n1. Introduction.\n\n Non Broadcast Multiple Access (NBMA) networks ","scope_keywords":["2491","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2491 This document describes a general architecture for IPv6 over NBMA\n networks. It forms the basis for subsidiary companion documents that\n describe details for various specific NBMA technologies (such as ATM\n or Frame Relay). The IPv6 over NBMA architecture allows conventional\n host-side operation of the IPv6 Neighbor Discovery protocol, while\n also supporting the establishment of 'shortcut' NBMA forwarding paths\n when dynamically signaled NBMA links are available. Operations over\n administratively configured Point to Point NBMA links are also\n described.\n\n Dynamic NBMA shortcuts are achieved through the use of IPv6 Neighbor\n Discovery protocol operation within Logical Links, and inter-router\n NHRP for the discovery of off-Link NBMA destinations. Both flow-\n triggered and explicitly source-triggered shortcuts are supported.\n\n1. Introduction.\n\n Non Broadcast Multiple Access (NBMA) networks  2491 key management path nested-reference unchanged"},{"id":"IETF RFC 121","type":"specification","body":"IETF","designation":"RFC 121","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc121.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc121.txt","https://www.rfc-editor.org/rfc/rfc121.pdf"],"folder":"IETF/RFC-121","files":{"txt":{"path":"standards/IETF/RFC-121/RFC-121.txt","sha256":"e2d420cf1ed4dcc385eedc504bc01f4d1264ca662d317cf56a238a78add2f910"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Krilanovich\nRequest for Comments: 121 Computer Research Lab, UCSB\nNIC: 5833 21 April 1971\n\n NETWORK ON-LINE OPERATORS\n\nPREFACE\n\n The operators described in this document have been implemented within\n UCSB's On-Line System and make the Network (via the NCP) accessible\n to On-Line System users.\n\n A set of operators is provided to facilitate the use of the Network\n by On-Line System users. The operators are defined on LVL I on\n system 'NET', and serve an an interface between the users and the\n Network Control Program (NCP), which supervises all Network\n operations at this site.\n\n A concept fundamental to On-Line System Network operations is that of\n a completion code variable. Associated with each socket that is not\n in the closed state is a unique variable, called a completion code\n variable. This variable serves two purpose: it identifies the local\n socket referen","scope_keywords":["121","key","keys","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 216","folder":"IETF/RFC-216","source":"IETF/RFC-216/RFC-216.txt","version":null}],"search_text":"IETF RFC 121 Network Working Group M. Krilanovich\nRequest for Comments: 121 Computer Research Lab, UCSB\nNIC: 5833 21 April 1971\n\n NETWORK ON-LINE OPERATORS\n\nPREFACE\n\n The operators described in this document have been implemented within\n UCSB's On-Line System and make the Network (via the NCP) accessible\n to On-Line System users.\n\n A set of operators is provided to facilitate the use of the Network\n by On-Line System users. The operators are defined on LVL I on\n system 'NET', and serve an an interface between the users and the\n Network Control Program (NCP), which supervises all Network\n operations at this site.\n\n A concept fundamental to On-Line System Network operations is that of\n a completion code variable. Associated with each socket that is not\n in the closed state is a unique variable, called a completion code\n variable. This variable serves two purpose: it identifies the local\n socket referen 121 key keys path nested-reference unchanged"},{"id":"IETF RFC 216","type":"specification","body":"IETF","designation":"RFC 216","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc216.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc216.txt","https://www.rfc-editor.org/rfc/rfc216.pdf"],"folder":"IETF/RFC-216","files":{"pdf":{"path":"standards/IETF/RFC-216/RFC-216.pdf","sha256":"cddebf171a03b9c2d8e8b39c8bb8eb7781dbfd288bb1d3e9ccb1d6a843ff704f"},"txt":{"path":"standards/IETF/RFC-216/RFC-216.txt","sha256":"0cd26747f285199072f6f45380499df0c05b1238fb9e78fbfaf4d1d38bf5ba98"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. White\nRequest for Comments: 216 UCSB Computer Research Lab\nCategories: D.3, G.3 September 1971\nNIC: 7546\n\n Telnet Access To UCSB's Online System\n\nContents\n\n I. Motivation .................................................1\n II. Limitations ................................................2\n III. System Documentation .......................................2\n IV. System Access ..............................................3\n V. Software Structure .........................................3\n VI. Virtual OLS Keyboard .......................................4\n VII. NETOLS Commands ...........................................10\n A. HELP ...................................................10\n B. PREFIX .................................................10\n C. SHIFT and UNSHIFT ......................................10\n D. FULLDUPLEX and HALFDUPLEX ..............................1","scope_keywords":["216","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 216 Network Working Group J. White\nRequest for Comments: 216 UCSB Computer Research Lab\nCategories: D.3, G.3 September 1971\nNIC: 7546\n\n Telnet Access To UCSB's Online System\n\nContents\n\n I. Motivation .................................................1\n II. Limitations ................................................2\n III. System Documentation .......................................2\n IV. System Access ..............................................3\n V. Software Structure .........................................3\n VI. Virtual OLS Keyboard .......................................4\n VII. NETOLS Commands ...........................................10\n A. HELP ...................................................10\n B. PREFIX .................................................10\n C. SHIFT and UNSHIFT ......................................10\n D. FULLDUPLEX and HALFDUPLEX ..............................1 216 key keys nested-reference unchanged"},{"id":"IETF RFC 1211","type":"specification","body":"IETF","designation":"RFC 1211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1211.txt","https://www.rfc-editor.org/rfc/rfc1211.pdf"],"folder":"IETF/RFC-1211","files":{"txt":{"path":"standards/IETF/RFC-1211/RFC-1211.txt","sha256":"d9e1d180d944a139158fae5b5f753479901afb74443a04c971c6c4a895e58847"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Westine\nRequest for Comments: 1211 J. Postel\n ISI\n March 1991\n\n Problems with the Maintenance of Large Mailing Lists\n\nStatus of this Memo\n\n This RFC discusses problems with maintaining large mailing lists,\n especially the processing of error reports. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.............................................. 1\n 2. Discussion................................................ 1\n 3. Typical Problems.......................................... 3\n 3.1. Misdirected Error Reports................................. 3\n 3.2. Sublists.................................................. 3\n 3.3. Misdirected Requests...................................... 5\n 3.4. Misdirected Messages...................................... ","scope_keywords":["1211","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null}],"search_text":"IETF RFC 1211 Network Working Group A. Westine\nRequest for Comments: 1211 J. Postel\n ISI\n March 1991\n\n Problems with the Maintenance of Large Mailing Lists\n\nStatus of this Memo\n\n This RFC discusses problems with maintaining large mailing lists,\n especially the processing of error reports. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.............................................. 1\n 2. Discussion................................................ 1\n 3. Typical Problems.......................................... 3\n 3.1. Misdirected Error Reports................................. 3\n 3.2. Sublists.................................................. 3\n 3.3. Misdirected Requests...................................... 5\n 3.4. Misdirected Messages......................................  1211 delivery path nested-reference unchanged"},{"id":"IETF RFC 1255","type":"specification","body":"IETF","designation":"RFC 1255","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1255.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1255.txt","https://www.rfc-editor.org/rfc/rfc1255.pdf"],"folder":"IETF/RFC-1255","files":{"txt":{"path":"standards/IETF/RFC-1255/RFC-1255.txt","sha256":"6484b7bc3b2d85ce15bf1183a49a3c7a3f24bcdec134f16d82e48b57f90affaf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group The North American Directory Forum\nRequest for Comments: 1255 September 1991\nObsoletes: RFC 1218\n\n A Naming Scheme for c=US\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This RFC is a near-verbatim copy of a document, known as NADF-175,\n which has been produced by the North American Directory Forum (NADF).\n The NADF is a collection of organizations which offer, or plan to\n offer, public Directory services in North America, based on the CCITT\n X.500 Recommendations. As a part of its charter, the NADF must reach\n agreement as to how entries are named in the public portions of the\n North American Directory. NADF-175 represents the NADF's agreement\n in this area.\n\nTable of Contents\n\n 1 Introduction .......................................... ","scope_keywords":["1255","attribute","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null}],"search_text":"IETF RFC 1255 Network Working Group The North American Directory Forum\nRequest for Comments: 1255 September 1991\nObsoletes: RFC 1218\n\n A Naming Scheme for c=US\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This RFC is a near-verbatim copy of a document, known as NADF-175,\n which has been produced by the North American Directory Forum (NADF).\n The NADF is a collection of organizations which offer, or plan to\n offer, public Directory services in North America, based on the CCITT\n X.500 Recommendations. As a part of its charter, the NADF must reach\n agreement as to how entries are named in the public portions of the\n North American Directory. NADF-175 represents the NADF's agreement\n in this area.\n\nTable of Contents\n\n 1 Introduction ..........................................  1255 attribute key subject nested-reference unchanged"},{"id":"IETF RFC 1442","type":"specification","body":"IETF","designation":"RFC 1442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1442.txt","https://www.rfc-editor.org/rfc/rfc1442.pdf"],"folder":"IETF/RFC-1442","files":{"txt":{"path":"standards/IETF/RFC-1442/RFC-1442.txt","sha256":"07f4991ffa4a49c2434cbb96102ad41d0daf7066a43fc3d54bf112cade769637"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1442 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Structure of Management Information\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 2 Definitions ........................................... 4\n 3.1 The MODULE-IDENTITY macro ............","scope_keywords":["1442","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1444","folder":"IETF/RFC-1444","source":"IETF/RFC-1444/RFC-1444.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1447","folder":"IETF/RFC-1447","source":"IETF/RFC-1447/RFC-1447.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1450","folder":"IETF/RFC-1450","source":"IETF/RFC-1450/RFC-1450.txt","version":null},{"body":"IETF","designation":"RFC 1451","folder":"IETF/RFC-1451","source":"IETF/RFC-1451/RFC-1451.txt","version":null},{"body":"IETF","designation":"RFC 1452","folder":"IETF/RFC-1452","source":"IETF/RFC-1452/RFC-1452.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1566","folder":"IETF/RFC-1566","source":"IETF/RFC-1566/RFC-1566.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1595","folder":"IETF/RFC-1595","source":"IETF/RFC-1595/RFC-1595.txt","version":null},{"body":"IETF","designation":"RFC 1596","folder":"IETF/RFC-1596","source":"IETF/RFC-1596/RFC-1596.txt","version":null},{"body":"IETF","designation":"RFC 1604","folder":"IETF/RFC-1604","source":"IETF/RFC-1604/RFC-1604.txt","version":null},{"body":"IETF","designation":"RFC 1611","folder":"IETF/RFC-1611","source":"IETF/RFC-1611/RFC-1611.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1628","folder":"IETF/RFC-1628","source":"IETF/RFC-1628/RFC-1628.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 1657","folder":"IETF/RFC-1657","source":"IETF/RFC-1657/RFC-1657.txt","version":null},{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1665","folder":"IETF/RFC-1665","source":"IETF/RFC-1665/RFC-1665.txt","version":null},{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1695","folder":"IETF/RFC-1695","source":"IETF/RFC-1695/RFC-1695.txt","version":null},{"body":"IETF","designation":"RFC 1696","folder":"IETF/RFC-1696","source":"IETF/RFC-1696/RFC-1696.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2325","folder":"IETF/RFC-2325","source":"IETF/RFC-2325/RFC-2325.txt","version":null}],"search_text":"IETF RFC 1442 Network Working Group J. Case\n Request for Comments: 1442 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Structure of Management Information\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 3\n 2 Definitions ........................................... 4\n 3.1 The MODULE-IDENTITY macro ............ 1442 management nested-reference unchanged"},{"id":"IETF RFC 1565","type":"specification","body":"IETF","designation":"RFC 1565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1565.txt","https://www.rfc-editor.org/rfc/rfc1565.pdf"],"folder":"IETF/RFC-1565","files":{"txt":{"path":"standards/IETF/RFC-1565/RFC-1565.txt","sha256":"ac5bd2366b3f275c6c904270acfb3612285c6973138f8bf6d00b6e07fefbcbbf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille, WG Chair\nRequest for Comments: 1565 ISODE Consortium\nCategory: Standards Track N. Freed, Editor\n Innosoft\n January 1994\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................. 2\n 2. The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions .......................................... 3\n 3. Rationale for having a Network Services Monitoring MIB ....... 3\n 3.1 General Relationship to Other MIBs ...............","scope_keywords":["1565","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1566","folder":"IETF/RFC-1566","source":"IETF/RFC-1566/RFC-1566.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1697","folder":"IETF/RFC-1697","source":"IETF/RFC-1697/RFC-1697.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2039","folder":"IETF/RFC-2039","source":"IETF/RFC-2039/RFC-2039.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null}],"search_text":"IETF RFC 1565 Network Working Group S. Kille, WG Chair\nRequest for Comments: 1565 ISODE Consortium\nCategory: Standards Track N. Freed, Editor\n Innosoft\n January 1994\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................. 2\n 2. The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions .......................................... 3\n 3. Rationale for having a Network Services Monitoring MIB ....... 3\n 3.1 General Relationship to Other MIBs ............... 1565 management nested-reference unchanged"},{"id":"IETF RFC 1566","type":"specification","body":"IETF","designation":"RFC 1566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1566.txt","https://www.rfc-editor.org/rfc/rfc1566.pdf"],"folder":"IETF/RFC-1566","files":{"txt":{"path":"standards/IETF/RFC-1566/RFC-1566.txt","sha256":"64c93199350a73dea7a0298c2d7dc2a4311e3225cf8bb0f4b42569a9ff393bf5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille, WG Chair\nRequest for Comments: 1566 ISODE Consortium\nCategory: Standards Track N. Freed, Editor\n Innosoft\n January 1994\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................. 2\n 2. The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions .......................................... 2\n 3. Message Flow Model ........................................... 3\n 4. MTA Objects .................................................. ","scope_keywords":["1566","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2039","folder":"IETF/RFC-2039","source":"IETF/RFC-2039/RFC-2039.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null}],"search_text":"IETF RFC 1566 Network Working Group S. Kille, WG Chair\nRequest for Comments: 1566 ISODE Consortium\nCategory: Standards Track N. Freed, Editor\n Innosoft\n January 1994\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................. 2\n 2. The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions .......................................... 2\n 3. Message Flow Model ........................................... 3\n 4. MTA Objects ..................................................  1566 management nested-reference unchanged"},{"id":"IETF RFC 1567","type":"specification","body":"IETF","designation":"RFC 1567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1567.txt","https://www.rfc-editor.org/rfc/rfc1567.pdf"],"folder":"IETF/RFC-1567","files":{"txt":{"path":"standards/IETF/RFC-1567/RFC-1567.txt","sha256":"248285c4a32b8eba842e604f3cb52fee01a609ff43289c4e1fa3a947210dbcc0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB). It defines the MIB for monitoring Directory System Agents\n (DSA), a component of the OSI Directory. This MIB will be used in\n conjunction with the APPLICATION-MIB for monitoring DSAs.","scope_keywords":["1567","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2039","folder":"IETF/RFC-2039","source":"IETF/RFC-2039/RFC-2039.txt","version":null}],"search_text":"IETF RFC 1567 This document defines a portion of the Management Information Base\n (MIB). It defines the MIB for monitoring Directory System Agents\n (DSA), a component of the OSI Directory. This MIB will be used in\n conjunction with the APPLICATION-MIB for monitoring DSAs. 1567 management timestamp nested-reference unchanged"},{"id":"IETF RFC 1586","type":"specification","body":"IETF","designation":"RFC 1586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1586.txt","https://www.rfc-editor.org/rfc/rfc1586.pdf"],"folder":"IETF/RFC-1586","files":{"txt":{"path":"standards/IETF/RFC-1586/RFC-1586.txt","sha256":"da63b4cdc3cedccc07eddecb2bf7df4fa26edc1a53cd8b79ddb0e71137da5930"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies guidelines for implementors and users of the Open\n Shortest Path First (OSPF) routing protocol to bring about\n improvements in how the protocol runs over frame relay networks. We\n show how to configure frame relay interfaces in a way that obviates\n the \"full-mesh\" connectivity required by current OSPF\n implementations. This allows for simpler, more economic network\n designs. These guidelines do not require any protocol changes; they\n only provide recommendations for how OSPF should be implemented and\n configured to use frame relay networks efficiently.\n\nAcknowledgements\n\n This memo is the result of work done in the OSPF Working Group of the\n IETF. Comments and contributions from several sources, especially\n Fred Baker of ACC, John Moy of Proteon, and Bala Rajagopalan of AT&T\n Bell Laboratories are included in this work.\n\n1. Introduction\n\n A frame relay (FR) network pr","scope_keywords":["1586","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null}],"search_text":"IETF RFC 1586 This memo specifies guidelines for implementors and users of the Open\n Shortest Path First (OSPF) routing protocol to bring about\n improvements in how the protocol runs over frame relay networks. We\n show how to configure frame relay interfaces in a way that obviates\n the \"full-mesh\" connectivity required by current OSPF\n implementations. This allows for simpler, more economic network\n designs. These guidelines do not require any protocol changes; they\n only provide recommendations for how OSPF should be implemented and\n configured to use frame relay networks efficiently.\n\nAcknowledgements\n\n This memo is the result of work done in the OSPF Working Group of the\n IETF. Comments and contributions from several sources, especially\n Fred Baker of ACC, John Moy of Proteon, and Bala Rajagopalan of AT&T\n Bell Laboratories are included in this work.\n\n1. Introduction\n\n A frame relay (FR) network pr 1586 path presentation nested-reference unchanged"},{"id":"IETF RFC 1595","type":"specification","body":"IETF","designation":"RFC 1595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1595.txt","https://www.rfc-editor.org/rfc/rfc1595.pdf"],"folder":"IETF/RFC-1595","files":{"txt":{"path":"standards/IETF/RFC-1595/RFC-1595.txt","sha256":"6159ee1d0e8ede4077542b4e33780bbb1274f92459fee2b781f2cbc9fa819fa8"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) objects. This\n document is a companion document with Definitions of Managed Objects\n for the DS1/E1 and DS3/E3 Interface Types, RFC1406 [14] and RFC1407\n [13].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.","scope_keywords":["1595","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null}],"search_text":"IETF RFC 1595 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) objects. This\n document is a companion document with Definitions of Managed Objects\n for the DS1/E1 and DS3/E3 Interface Types, RFC1406 [14] and RFC1407\n [13].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions. 1595 management path subject nested-reference unchanged"},{"id":"IETF RFC 1596","type":"specification","body":"IETF","designation":"RFC 1596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1596.txt","https://www.rfc-editor.org/rfc/rfc1596.pdf"],"folder":"IETF/RFC-1596","files":{"txt":{"path":"standards/IETF/RFC-1596/RFC-1596.txt","sha256":"2b8d6214f6005bbf2b1adf665efb74f3dba40118cebad0cbfaee8b9aa0096b23"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing the Frame\n Relay Service.","scope_keywords":["1596","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1596 This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing the Frame\n Relay Service. 1596 management nested-reference unchanged"},{"id":"IETF RFC 1604","type":"specification","body":"IETF","designation":"RFC 1604","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1604.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1604.txt","https://www.rfc-editor.org/rfc/rfc1604.pdf"],"folder":"IETF/RFC-1604","files":{"txt":{"path":"standards/IETF/RFC-1604/RFC-1604.txt","sha256":"7514d944a1ab543ac014d6ca4613df2a0578d1f625c2f6c4bc279d2086478e57"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing the Frame\n Relay Service.","scope_keywords":["1604","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null}],"search_text":"IETF RFC 1604 This memo defines an extension to the Management Information Base\n (MIB) for use with network management protocols in TCP/IP-based\n internets. In particular, it defines objects for managing the Frame\n Relay Service. 1604 management nested-reference unchanged"},{"id":"IETF RFC 1657","type":"specification","body":"IETF","designation":"RFC 1657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1657.txt","https://www.rfc-editor.org/rfc/rfc1657.pdf"],"folder":"IETF/RFC-1657","files":{"txt":{"path":"standards/IETF/RFC-1657/RFC-1657.txt","sha256":"560a3dab47f77860a8cc2bbbd006ce3b2ad89aac2f7800305eb638805e29d029"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Willis\nRequest for Comments: 1657 J. Burruss\nCategory: Standards Track Wellfleet Communications Inc.\n J. Chu, Editor\n IBM Corp.\n July 1994\n\n Definitions of Managed Objects for the Fourth Version of the\n Border Gateway Protocol (BGP-4) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Border Gateway Protocol Version 4 or lo","scope_keywords":["1657","attribute","attributes","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1656","folder":"IETF/RFC-1656","source":"IETF/RFC-1656/RFC-1656.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 4273","folder":"IETF/RFC-4273","source":"IETF/RFC-4273/RFC-4273.txt","version":null}],"search_text":"IETF RFC 1657 Network Working Group S. Willis\nRequest for Comments: 1657 J. Burruss\nCategory: Standards Track Wellfleet Communications Inc.\n J. Chu, Editor\n IBM Corp.\n July 1994\n\n Definitions of Managed Objects for the Fourth Version of the\n Border Gateway Protocol (BGP-4) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Border Gateway Protocol Version 4 or lo 1657 attribute attributes management path policy nested-reference unchanged"},{"id":"IETF RFC 1658","type":"specification","body":"IETF","designation":"RFC 1658","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1658.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1658.txt","https://www.rfc-editor.org/rfc/rfc1658.pdf"],"folder":"IETF/RFC-1658","files":{"txt":{"path":"standards/IETF/RFC-1658/RFC-1658.txt","sha256":"62d1a399c028570449c0743eb3a2f03944344aa4a439ddcd6bf7b1ff7e4012d8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Stewart\nRequest for Comments: 1658 Xyplex, Inc.\nObsoletes: 1316 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for Character Stream Devices\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 3\n 3. Overview .................................................... 3\n 3.1 Relationship to Interface MIB ..........","scope_keywords":["1658","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1659","folder":"IETF/RFC-1659","source":"IETF/RFC-1659/RFC-1659.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1658 Network Working Group B. Stewart\nRequest for Comments: 1658 Xyplex, Inc.\nObsoletes: 1316 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for Character Stream Devices\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 3\n 3. Overview .................................................... 3\n 3.1 Relationship to Interface MIB .......... 1658 management nested-reference unchanged"},{"id":"IETF RFC 1659","type":"specification","body":"IETF","designation":"RFC 1659","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1659.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1659.txt","https://www.rfc-editor.org/rfc/rfc1659.pdf"],"folder":"IETF/RFC-1659","files":{"txt":{"path":"standards/IETF/RFC-1659/RFC-1659.txt","sha256":"92e8cb9cef531bc5a90eba7bbd18600d342e7549eb7f8d75fc1896e16fa6029d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Stewart\nRequest for Comments: 1659 Xyplex, Inc.\nObsoletes: 1317 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for RS-232-like Hardware Devices\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. The SNMPv2 Network Management Framework ..................... 1\n 2.1 Object Definitions ......................................... 2\n 3. Overview .................................................... 2\n 3.1 Relationship to Interface MIB ......","scope_keywords":["1659","attribute","attributes","management","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1660","folder":"IETF/RFC-1660","source":"IETF/RFC-1660/RFC-1660.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1659 Network Working Group B. Stewart\nRequest for Comments: 1659 Xyplex, Inc.\nObsoletes: 1317 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for RS-232-like Hardware Devices\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 1\n 2. The SNMPv2 Network Management Framework ..................... 1\n 2.1 Object Definitions ......................................... 2\n 3. Overview .................................................... 2\n 3.1 Relationship to Interface MIB ...... 1659 attribute attributes management tsp nested-reference unchanged"},{"id":"IETF RFC 1660","type":"specification","body":"IETF","designation":"RFC 1660","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1660.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1660.txt","https://www.rfc-editor.org/rfc/rfc1660.pdf"],"folder":"IETF/RFC-1660","files":{"txt":{"path":"standards/IETF/RFC-1660/RFC-1660.txt","sha256":"2e38e5c101943981b5f98ea998ea35983c9fa37356b9139677906f5fa35c8890"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Stewart\nRequest for Comments: 1660 Xyplex, Inc.\nObsoletes: 1318 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for Parallel-printer-like\n Hardware Devices using SMIv2\n\nStatus of this Memo\n\n This document specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. The SNMPv2 Network Management Framework .................... 1\n 2.1 Object Definitions ........................................ 2\n 3. Overview ................................................... 2\n 3.1 Relationship to Interface MIB ..................","scope_keywords":["1660","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1658","folder":"IETF/RFC-1658","source":"IETF/RFC-1658/RFC-1658.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 1660 Network Working Group B. Stewart\nRequest for Comments: 1660 Xyplex, Inc.\nObsoletes: 1318 July 1994\nCategory: Standards Track\n\n Definitions of Managed Objects for Parallel-printer-like\n Hardware Devices using SMIv2\n\nStatus of this Memo\n\n This document specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"IAB\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. The SNMPv2 Network Management Framework .................... 1\n 2.1 Object Definitions ........................................ 2\n 3. Overview ................................................... 2\n 3.1 Relationship to Interface MIB .................. 1660 management nested-reference unchanged"},{"id":"IETF RFC 1665","type":"specification","body":"IETF","designation":"RFC 1665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1665.txt","https://www.rfc-editor.org/rfc/rfc1665.pdf"],"folder":"IETF/RFC-1665","files":{"txt":{"path":"standards/IETF/RFC-1665/RFC-1665.txt","sha256":"de2f1995a11af0c00d14abac2105f21cfd8c5f2005b5cbfd4f9304076e89d17c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Z. Kielczewski\nRequest for Comments: 1665 Eicon Technology Corporation\nCategory: Standards Track D. Kostick\n Bell Communications Research\n K. Shih\n Novell\n Editors\n July 1994\n\n Definitions of Managed Objects\n for SNA NAUs using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 2\n 3. Overview ............................................","scope_keywords":["1665","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1665 Network Working Group Z. Kielczewski\nRequest for Comments: 1665 Eicon Technology Corporation\nCategory: Standards Track D. Kostick\n Bell Communications Research\n K. Shih\n Novell\n Editors\n July 1994\n\n Definitions of Managed Objects\n for SNA NAUs using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 2\n 3. Overview ............................................ 1665 management timestamp nested-reference unchanged"},{"id":"IETF RFC 1695","type":"specification","body":"IETF","designation":"RFC 1695","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1695.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1695.txt","https://www.rfc-editor.org/rfc/rfc1695.pdf"],"folder":"IETF/RFC-1695","files":{"txt":{"path":"standards/IETF/RFC-1695/RFC-1695.txt","sha256":"28be4abc618b740d2b908005a73618f90feffc8b09f29c2187c8afe2972863c3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Ahmed\nRequest for Comments: 1695 K. Tesink\nCategory: Standards Track Editors\n Bell Communications Research\n August 1994\n\n Definitions of Managed Objects\n for ATM Management Version 8.0\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. The SNMPv2 Network Management Framework .................. 2\n 3. Object Definitions ....................................... 2\n 4. ATM Terminology .......................................... 3\n 4.1 VCL/VPL and VCC/VPC .........","scope_keywords":["1695","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1694","folder":"IETF/RFC-1694","source":"IETF/RFC-1694/RFC-1694.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2514","folder":"IETF/RFC-2514","source":"IETF/RFC-2514/RFC-2514.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null}],"search_text":"IETF RFC 1695 Network Working Group M. Ahmed\nRequest for Comments: 1695 K. Tesink\nCategory: Standards Track Editors\n Bell Communications Research\n August 1994\n\n Definitions of Managed Objects\n for ATM Management Version 8.0\n using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. The SNMPv2 Network Management Framework .................. 2\n 3. Object Definitions ....................................... 2\n 4. ATM Terminology .......................................... 3\n 4.1 VCL/VPL and VCC/VPC ......... 1695 management path nested-reference unchanged"},{"id":"IETF RFC 1696","type":"specification","body":"IETF","designation":"RFC 1696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1696.txt","https://www.rfc-editor.org/rfc/rfc1696.pdf"],"folder":"IETF/RFC-1696","files":{"txt":{"path":"standards/IETF/RFC-1696/RFC-1696.txt","sha256":"6724964c321845aee0dcd8bbde2137c984f3b94ab976a152f592694377df7f2c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Barnes\nRequest for Comments: 1696 Xylogics, Inc.\nCategory: Standards Track L. Brown\n Motorola\n R. Royston\n US Robotics, Inc.\n S. Waldbusser\n Carnegie Mellon University\n August 1994\n\n Modem Management Information Base (MIB) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Introduction ................................................. 1\n 2 The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions ......................................... 2\n 3 Definitions ......................................","scope_keywords":["1696","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1696 Network Working Group J. Barnes\nRequest for Comments: 1696 Xylogics, Inc.\nCategory: Standards Track L. Brown\n Motorola\n R. Royston\n US Robotics, Inc.\n S. Waldbusser\n Carnegie Mellon University\n August 1994\n\n Modem Management Information Base (MIB) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Introduction ................................................. 1\n 2 The SNMPv2 Network Management Framework ...................... 2\n 2.1 Object Definitions ......................................... 2\n 3 Definitions ...................................... 1696 management nested-reference unchanged"},{"id":"IETF RFC 1697","type":"specification","body":"IETF","designation":"RFC 1697","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1697.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1697.txt","https://www.rfc-editor.org/rfc/rfc1697.pdf"],"folder":"IETF/RFC-1697","files":{"txt":{"path":"standards/IETF/RFC-1697/RFC-1697.txt","sha256":"bbca60e0ba72e86aafb967b492b740825ce242e367ebfca7b96a52e208c209b8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Brower, Editor\nRequest for Comments: 1697 The ASK Group, INGRES DBMS Development\nCategory: Standards Track B. Purvy, RDBMSMIB Working Group Chair\n Oracle Corporation\n A. Daniel\n Informix Software, Inc.\n M. Sinykin\n J. Smith\n Oracle Corporation\n August 1994\n\n Relational Database Management System (RDBMS)\n Management Information Base (MIB) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Obj","scope_keywords":["1697","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1697 Network Working Group D. Brower, Editor\nRequest for Comments: 1697 The ASK Group, INGRES DBMS Development\nCategory: Standards Track B. Purvy, RDBMSMIB Working Group Chair\n Oracle Corporation\n A. Daniel\n Informix Software, Inc.\n M. Sinykin\n J. Smith\n Oracle Corporation\n August 1994\n\n Relational Database Management System (RDBMS)\n Management Information Base (MIB) using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction .............................................. 1\n 2. The SNMPv2 Network Management Framework ................... 2\n 2.1 Obj 1697 management nested-reference unchanged"},{"id":"IETF RFC 1905","type":"specification","body":"IETF","designation":"RFC 1905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1905.txt","https://www.rfc-editor.org/rfc/rfc1905.pdf"],"folder":"IETF/RFC-1905","files":{"txt":{"path":"standards/IETF/RFC-1905/RFC-1905.txt","sha256":"80b70264d3df12c52892b4f1612dc6708c567443bf76e6230bfc5225756f0358"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1905 J. Case\nObsoletes: 1448 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Protocol Operations\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n A management system contains: several (potentially many) nodes, each\n with a processing entity, termed an agent, which has access to\n management instrumen","scope_keywords":["1905","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1902","folder":"IETF/RFC-1902","source":"IETF/RFC-1902/RFC-1902.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1906","folder":"IETF/RFC-1906","source":"IETF/RFC-1906/RFC-1906.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2578","folder":"IETF/RFC-2578","source":"IETF/RFC-2578/RFC-2578.txt","version":null},{"body":"IETF","designation":"RFC 2580","folder":"IETF/RFC-2580","source":"IETF/RFC-2580/RFC-2580.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null}],"search_text":"IETF RFC 1905 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1905 J. Case\nObsoletes: 1448 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Protocol Operations\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n A management system contains: several (potentially many) nodes, each\n with a processing entity, termed an agent, which has access to\n management instrumen 1905 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 2011","type":"specification","body":"IETF","designation":"RFC 2011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2011.txt","https://www.rfc-editor.org/rfc/rfc2011.pdf"],"folder":"IETF/RFC-2011","files":{"txt":{"path":"standards/IETF/RFC-2011/RFC-2011.txt","sha256":"16d1e3a3468a09b0f222ea022461272f9a05da1393d4c7e31619acc9ae6380bb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2011 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the Internet Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable of Contents","scope_keywords":["2011","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null}],"search_text":"IETF RFC 2011 Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2011 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the Internet Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable of Contents 2011 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 2012","type":"specification","body":"IETF","designation":"RFC 2012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2012.txt","https://www.rfc-editor.org/rfc/rfc2012.pdf"],"folder":"IETF/RFC-2012","files":{"txt":{"path":"standards/IETF/RFC-2012/RFC-2012.txt","sha256":"635c6400e057ac4495628bd834c287cdb0ef687645d6b9178ba0aa5be4653194"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2012 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the Transmission Control Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable","scope_keywords":["2012","algorithm","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2012 Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2012 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the Transmission Control Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable 2012 algorithm authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 2013","type":"specification","body":"IETF","designation":"RFC 2013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2013.txt","https://www.rfc-editor.org/rfc/rfc2013.pdf"],"folder":"IETF/RFC-2013","files":{"txt":{"path":"standards/IETF/RFC-2013/RFC-2013.txt","sha256":"a0cd96ff6f598bfa909cd0bd61a106efee3f3efc0580f34a4f44fc6a7f1ef46f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2013 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the User Datagram Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable of Con","scope_keywords":["2013","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null}],"search_text":"IETF RFC 2013 Network Working Group K. McCloghrie, Editor\nRequest for Comments: 2013 Cisco Systems\nUpdates: 1213 November 1996\nCategory: Standards Track\n\n SNMPv2 Management Information Base\n for the User Datagram Protocol using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIESG Note:\n\n The IP, UDP, and TCP MIB modules currently support only IPv4. These\n three modules use the IpAddress type defined as an OCTET STRING of\n length 4 to represent the IPv4 32-bit internet addresses. (See RFC\n 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6\n internet addresses.\n\nTable of Con 2013 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 2039","type":"specification","body":"IETF","designation":"RFC 2039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2039.txt","https://www.rfc-editor.org/rfc/rfc2039.pdf"],"folder":"IETF/RFC-2039","files":{"txt":{"path":"standards/IETF/RFC-2039/RFC-2039.txt","sha256":"da1c2d2d4fcd839d09fc6814752ae837be844c649430a563c81b59d7793d6c8f"}},"tags":["nested-reference","unchanged"],"summary":"This document was produced at the request of the Network Management\n Area Director following the HTTP-MIB BOF at the 35th IETF meeting to\n report on the applicability of the existing standards track MIBs to\n management of WWW servers.\n\n Requirements for management of a World Wide Web (WWW) server are\n presented. The applicable existing standards track MIBs are then\n examined. Finally, an analysis of the additional groups of MIB\n attributes that are needed to meet the requirements is presented.","scope_keywords":["2039","attribute","attributes","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null}],"search_text":"IETF RFC 2039 This document was produced at the request of the Network Management\n Area Director following the HTTP-MIB BOF at the 35th IETF meeting to\n report on the applicability of the existing standards track MIBs to\n management of WWW servers.\n\n Requirements for management of a World Wide Web (WWW) server are\n presented. The applicable existing standards track MIBs are then\n examined. Finally, an analysis of the additional groups of MIB\n attributes that are needed to meet the requirements is presented. 2039 attribute attributes http management nested-reference unchanged"},{"id":"IETF RFC 2206","type":"specification","body":"IETF","designation":"RFC 2206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2206.txt","https://www.rfc-editor.org/rfc/rfc2206.pdf"],"folder":"IETF/RFC-2206","files":{"txt":{"path":"standards/IETF/RFC-2206/RFC-2206.txt","sha256":"8955efacaf123e7717112636a230caaf477f97c09abeaa3553fe147ea0cb3eae"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Resource\n Reservation Protocol (RSVP) within the interface attributes defined\n in the Integrated Services Model. Thus, the Integrated Services MIB\n is directly relevant to and cross-referenced by this MIB. Comments\n should be made to the RSVP Working Group, rsvp@isi.edu.","scope_keywords":["2206","attribute","attributes","management","path","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2206 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the Resource\n Reservation Protocol (RSVP) within the interface attributes defined\n in the Integrated Services Model. Thus, the Integrated Services MIB\n is directly relevant to and cross-referenced by this MIB. Comments\n should be made to the RSVP Working Group, rsvp@isi.edu. 2206 attribute attributes management path timestamp nested-reference unchanged"},{"id":"IETF RFC 2213","type":"specification","body":"IETF","designation":"RFC 2213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2213.txt","https://www.rfc-editor.org/rfc/rfc2213.pdf"],"folder":"IETF/RFC-2213","files":{"txt":{"path":"standards/IETF/RFC-2213/RFC-2213.txt","sha256":"8f3a0606fea4bbd158cb0d5d88e102c66f463f58cdd30bacbd69df0ad04c67fa"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the the interface\n attributes defined in the Integrated Services Model. Comments should\n be made to the Integrated Services Working Group, int-serv@isi.edu.","scope_keywords":["2213","attribute","attributes","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2213 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the the interface\n attributes defined in the Integrated Services Model. Comments should\n be made to the Integrated Services Working Group, int-serv@isi.edu. 2213 attribute attributes management path nested-reference unchanged"},{"id":"IETF RFC 2320","type":"specification","body":"IETF","designation":"RFC 2320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2320.txt","https://www.rfc-editor.org/rfc/rfc2320.pdf"],"folder":"IETF/RFC-2320","files":{"txt":{"path":"standards/IETF/RFC-2320/RFC-2320.txt","sha256":"420c721515130059ab9540839b02bf9784ea8c87344b30bd0ab6d74508790a28"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this memo is to define the Management Information Base\n (MIB) for supporting Classical IP and ARP over ATM as specified in\n Classical IP and ARP over ATM, refer to reference [3]. Support of an\n ATM interface by an IP layer will require implementation of objects\n from several Management Information Bases (MIBs) as well as their\n enhancement in order to enable usage of ATM transports. It is the\n intent of this MIB to fully adhere to all prerequisite MIBs unless\n explicitly stated. Deviations will be documented in corresponding\n conformance statements. The specification of this MIB will utilize\n the Structure of Management Information (SMI) for Version 2 of the\n Simple Network Management Protocol Version (refer to RFC 1902,\n reference [1]).\n\nGreene, et al. [Page 1]\n\f\nRFC 2320 IP and ARP over ATM (IPOA) MIB April 1998","scope_keywords":["2320","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2320 The purpose of this memo is to define the Management Information Base\n (MIB) for supporting Classical IP and ARP over ATM as specified in\n Classical IP and ARP over ATM, refer to reference [3]. Support of an\n ATM interface by an IP layer will require implementation of objects\n from several Management Information Bases (MIBs) as well as their\n enhancement in order to enable usage of ATM transports. It is the\n intent of this MIB to fully adhere to all prerequisite MIBs unless\n explicitly stated. Deviations will be documented in corresponding\n conformance statements. The specification of this MIB will utilize\n the Structure of Management Information (SMI) for Version 2 of the\n Simple Network Management Protocol Version (refer to RFC 1902,\n reference [1]).\n\nGreene, et al. [Page 1]\n\f\nRFC 2320 IP and ARP over ATM (IPOA) MIB April 1998 2320 key management nested-reference unchanged"},{"id":"IETF RFC 2325","type":"specification","body":"IETF","designation":"RFC 2325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2325.txt","https://www.rfc-editor.org/rfc/rfc2325.pdf"],"folder":"IETF/RFC-2325","files":{"txt":{"path":"standards/IETF/RFC-2325/RFC-2325.txt","sha256":"af2f0e5bc53888b172b1f0ed0392536748835f9763a19135fe176a8547d3b596"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Slavitch\nRequest for Comments: 2325 Loran Technologies Inc.\nCategory: Informational 1 April 1998\n\n Definitions of Managed Objects for Drip-Type Heated Beverage\n Hardware Devices using SMIv2\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. The SNMPv2 Network Management Framework .................... 1\n 2.1 Object Definitions ........................................ 2\n 3. Overview ................................................... 2\n 3.1 Relationship to Interface MIB ............................. 2\n 4. Definitions ................................................ 3\n ","scope_keywords":["2325","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 2325 Network Working Group M. Slavitch\nRequest for Comments: 2325 Loran Technologies Inc.\nCategory: Informational 1 April 1998\n\n Definitions of Managed Objects for Drip-Type Heated Beverage\n Hardware Devices using SMIv2\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. The SNMPv2 Network Management Framework .................... 1\n 2.1 Object Definitions ........................................ 2\n 3. Overview ................................................... 2\n 3.1 Relationship to Interface MIB ............................. 2\n 4. Definitions ................................................ 3\n  2325 management timestamp nested-reference unchanged"},{"id":"IETF RFC 3591","type":"specification","body":"IETF","designation":"RFC 3591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3591.txt","https://www.rfc-editor.org/rfc/rfc3591.pdf"],"folder":"IETF/RFC-3591","files":{"txt":{"path":"standards/IETF/RFC-3591/RFC-3591.txt","sha256":"7e48ca6bf1e5cf101ab68e2b736dad1ffc9fdb9a1ad0d520327d3db12f64e5a2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with Simple Network Management Protocol (SNMP) in TCP/IP-\n based internets. In particular, it defines objects for managing\n Optical Interfaces associated with WavelengthDivision Multiplexing\n systems or characterized by the Optical Transport Network (OTN) in\n accordance with the OTN architecture defined in ITU-T Recommendation\n G.872.\n\n The MIB module defined in this memo can be used for performance\n monitoring and/or configuration of such optical interface.\n\nLam, et al. Standards Track [Page 1]\n\f\nRFC 3591 Optical Interface Type MIB September 2003","scope_keywords":["3591","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null}],"search_text":"IETF RFC 3591 This memo defines a portion of the Management Information Base (MIB)\n for use with Simple Network Management Protocol (SNMP) in TCP/IP-\n based internets. In particular, it defines objects for managing\n Optical Interfaces associated with WavelengthDivision Multiplexing\n systems or characterized by the Optical Transport Network (OTN) in\n accordance with the OTN architecture defined in ITU-T Recommendation\n G.872.\n\n The MIB module defined in this memo can be used for performance\n monitoring and/or configuration of such optical interface.\n\nLam, et al. Standards Track [Page 1]\n\f\nRFC 3591 Optical Interface Type MIB September 2003 3591 management path presentation nested-reference unchanged"},{"id":"IETF RFC 3592","type":"specification","body":"IETF","designation":"RFC 3592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3592.txt","https://www.rfc-editor.org/rfc/rfc3592.pdf"],"folder":"IETF/RFC-3592","files":{"txt":{"path":"standards/IETF/RFC-3592/RFC-3592.txt","sha256":"5104d4f37601270be7bad792291ac9c90dd957461c258233fe63e20da1d378b6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This\n document is a companion to the documents that define Managed Objects\n for the DS1/E1/DS2/E2 and DS3/E3 Interface Types.\n\n This memo replaces RFC 2558. Changes relative to RFC 2558 are\n summarized in the MIB module's REVISION clause.","scope_keywords":["3592","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"IETF RFC 3592 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing Synchronous Optical\n Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This\n document is a companion to the documents that define Managed Objects\n for the DS1/E1/DS2/E2 and DS3/E3 Interface Types.\n\n This memo replaces RFC 2558. Changes relative to RFC 2558 are\n summarized in the MIB module's REVISION clause. 3592 key management path nested-reference unchanged"},{"id":"IETF RFC 3873","type":"specification","body":"IETF","designation":"RFC 3873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3873.txt","https://www.rfc-editor.org/rfc/rfc3873.pdf"],"folder":"IETF/RFC-3873","files":{"txt":{"path":"standards/IETF/RFC-3873/RFC-3873.txt","sha256":"973b2e85198dd037ddd03d748c86edf48883a3ee1fe5a96837244e1990182edf"}},"tags":["nested-reference","unchanged"],"summary":"The Stream Control Transmission Protocol (SCTP) is a reliable\n transport protocol operating on top of a connectionless packet\n network such as IP. It is designed to transport public switched\n telephone network (PSTN) signaling messages over the connectionless\n packet network, but is capable of broader applications.\n\n This memo defines the Management Information Base (MIB) module which\n describes the minimum set of objects needed to manage the\n implementation of the SCTP.","scope_keywords":["3873","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3873 The Stream Control Transmission Protocol (SCTP) is a reliable\n transport protocol operating on top of a connectionless packet\n network such as IP. It is designed to transport public switched\n telephone network (PSTN) signaling messages over the connectionless\n packet network, but is capable of broader applications.\n\n This memo defines the Management Information Base (MIB) module which\n describes the minimum set of objects needed to manage the\n implementation of the SCTP. 3873 key management nested-reference unchanged"},{"id":"IETF RFC 3895","type":"specification","body":"IETF","designation":"RFC 3895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3895.txt","https://www.rfc-editor.org/rfc/rfc3895.pdf"],"folder":"IETF/RFC-3895","files":{"txt":{"path":"standards/IETF/RFC-3895/RFC-3895.txt","sha256":"d9837ccca3a40a63a1cff398b9c394c3bda5ee5f7f0adbf58bc19b225b09d7bd"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, E1, DS2\n and E2 interfaces. This document is a companion to the documents\n that define Managed Objects for the DS0, DS3/E3 and Synchronous\n Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface\n Types. This document obsoletes RFC 2495.\n\nNicklass Standards Track [Page 1]\n\f\nRFC 3895 DS1/E1/DS2/E2 MIB September 2004","scope_keywords":["3895","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"IETF RFC 3895 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, E1, DS2\n and E2 interfaces. This document is a companion to the documents\n that define Managed Objects for the DS0, DS3/E3 and Synchronous\n Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface\n Types. This document obsoletes RFC 2495.\n\nNicklass Standards Track [Page 1]\n\f\nRFC 3895 DS1/E1/DS2/E2 MIB September 2004 3895 management nested-reference unchanged"},{"id":"IETF RFC 3896","type":"specification","body":"IETF","designation":"RFC 3896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3896.txt","https://www.rfc-editor.org/rfc/rfc3896.pdf"],"folder":"IETF/RFC-3896","files":{"txt":{"path":"standards/IETF/RFC-3896/RFC-3896.txt","sha256":"3dc8cbf40ae0f1185ed00ac132a54157386cbcc9b61fda9e4e5a9e7fa5f67d5f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS3 and E3\n interfaces. This document is a companion to the documents that\n define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous\n Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface\n Types. This document obsoletes RFC 2496.","scope_keywords":["3896","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 3896 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS3 and E3\n interfaces. This document is a companion to the documents that\n define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous\n Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface\n Types. This document obsoletes RFC 2496. 3896 management nested-reference unchanged"},{"id":"IETF RFC 4022","type":"specification","body":"IETF","designation":"RFC 4022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4022.txt","https://www.rfc-editor.org/rfc/rfc4022.pdf"],"folder":"IETF/RFC-4022","files":{"txt":{"path":"standards/IETF/RFC-4022/RFC-4022.txt","sha256":"f25fd129e01a2096c9352dd2ea3f4216d05a22b8ea4e03756550cbcbaa9d3eaf"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the Transmission Control Protocol (TCP) in an IP version\n independent manner. This memo obsoletes RFCs 2452 and 2012.","scope_keywords":["4022","algorithm","http","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4022 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for implementations\n of the Transmission Control Protocol (TCP) in an IP version\n independent manner. This memo obsoletes RFCs 2452 and 2012. 4022 algorithm http identification management nested-reference unchanged"},{"id":"IETF RFC 4088","type":"specification","body":"IETF","designation":"RFC 4088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4088.txt","https://www.rfc-editor.org/rfc/rfc4088.pdf"],"folder":"IETF/RFC-4088","files":{"txt":{"path":"standards/IETF/RFC-4088/RFC-4088.txt","sha256":"4058c25c342908d5b16a4d8d3f6401f17a083bd91e3a7ee5b47e17b166b5fb24"}},"tags":["nested-reference","unchanged"],"summary":"The Simple Network Management Protocol (SNMP) and the Internet\n Standard Management Framework are widely used for the management of\n communication devices, creating a need to specify SNMP access\n (including access to SNMP MIB object instances) from non-SNMP\n management environments. For example, when out-of-band IP management\n is used via a separate management interface (e.g., for a device that\n does not support in-band IP access), a uniform way to indicate how to\n contact the device for management is needed. Uniform Resource\n Identifiers (URIs) fit this need well, as they allow a single text\n string to indicate a management access communication endpoint for a\n wide variety of IP-based protocols.\n\n This document defines a URI scheme so that SNMP can be designated as\n the protocol used for management. The scheme also allows a URI to\n designate one or more MIB object instances.\n\nBlack, et ","scope_keywords":["4088","key","keys","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4838","folder":"IETF/RFC-4838","source":"IETF/RFC-4838/RFC-4838.txt","version":null},{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null}],"search_text":"IETF RFC 4088 The Simple Network Management Protocol (SNMP) and the Internet\n Standard Management Framework are widely used for the management of\n communication devices, creating a need to specify SNMP access\n (including access to SNMP MIB object instances) from non-SNMP\n management environments. For example, when out-of-band IP management\n is used via a separate management interface (e.g., for a device that\n does not support in-band IP access), a uniform way to indicate how to\n contact the device for management is needed. Uniform Resource\n Identifiers (URIs) fit this need well, as they allow a single text\n string to indicate a management access communication endpoint for a\n wide variety of IP-based protocols.\n\n This document defines a URI scheme so that SNMP can be designated as\n the protocol used for management. The scheme also allows a URI to\n designate one or more MIB object instances.\n\nBlack, et  4088 key keys management path nested-reference unchanged"},{"id":"IETF RFC 4097","type":"specification","body":"IETF","designation":"RFC 4097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4097.txt","https://www.rfc-editor.org/rfc/rfc4097.pdf"],"folder":"IETF/RFC-4097","files":{"txt":{"path":"standards/IETF/RFC-4097/RFC-4097.txt","sha256":"21ee7c90c95a239f23665b6ca54c9b21d28fe46b00e84c635c384dc571d5eeda"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an evaluation of the applicability of SNMP\n (Simple Network Management Protocol), RSIP (Realm Specific Internet\n Protocol), Megaco, Diameter, and COPS (Common Open Policy Service) as\n the MIDCOM (Middlebox Communications) protocol. A summary of each of\n the proposed protocols against the MIDCOM requirements and the MIDCOM\n framework is provided. Compliancy of each of the protocols against\n each requirement is detailed. A conclusion summarizes how each of\n the protocols fares in the evaluation.","scope_keywords":["4097","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4097 This document provides an evaluation of the applicability of SNMP\n (Simple Network Management Protocol), RSIP (Realm Specific Internet\n Protocol), Megaco, Diameter, and COPS (Common Open Policy Service) as\n the MIDCOM (Middlebox Communications) protocol. A summary of each of\n the proposed protocols against the MIDCOM requirements and the MIDCOM\n framework is provided. Compliancy of each of the protocols against\n each requirement is detailed. A conclusion summarizes how each of\n the protocols fares in the evaluation. 4097 key management policy nested-reference unchanged"},{"id":"IETF RFC 4292","type":"specification","body":"IETF","designation":"RFC 4292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4292.txt","https://www.rfc-editor.org/rfc/rfc4292.pdf"],"folder":"IETF/RFC-4292","files":{"txt":{"path":"standards/IETF/RFC-4292/RFC-4292.txt","sha256":"42eed325204a0daae824ca3fc94060d0e66576f7fe6b47764714824e901b43d6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it describes managed objects related to\n the forwarding of Internet Protocol (IP) packets in an IP version-\n independent manner. This document obsoletes RFC 2096.","scope_keywords":["4292","http","key","management","path","pki"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null}],"search_text":"IETF RFC 4292 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it describes managed objects related to\n the forwarding of Internet Protocol (IP) packets in an IP version-\n independent manner. This document obsoletes RFC 2096. 4292 http key management path pki nested-reference unchanged"},{"id":"IETF RFC 4805","type":"specification","body":"IETF","designation":"RFC 4805","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4805.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4805.txt","https://www.rfc-editor.org/rfc/rfc4805.pdf"],"folder":"IETF/RFC-4805","files":{"txt":{"path":"standards/IETF/RFC-4805/RFC-4805.txt","sha256":"6ef3def6c3a4acd10cd8cbf643b68cdebc8cab10a82f0ac69b873bfbc786d618"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, J1, E1,\n DS2, and E2 interfaces. This document is a companion to the\n documents that define managed objects for the DS0, DS3/E3, and\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Interface Types.\n\n This document obsoletes RFC 3895.\n\nNicklass, Ed. Standards Track [Page 1]\n\f\nRFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007","scope_keywords":["4805","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 4805 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing DS1, J1, E1,\n DS2, and E2 interfaces. This document is a companion to the\n documents that define managed objects for the DS0, DS3/E3, and\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Interface Types.\n\n This document obsoletes RFC 3895.\n\nNicklass, Ed. Standards Track [Page 1]\n\f\nRFC 4805 DS1/J1/E1/DS2/E2 MIB March 2007 4805 key management trust nested-reference unchanged"},{"id":"IETF RFC 6779","type":"specification","body":"IETF","designation":"RFC 6779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6779.txt","https://www.rfc-editor.org/rfc/rfc6779.pdf"],"folder":"IETF/RFC-6779","files":{"txt":{"path":"standards/IETF/RFC-6779/RFC-6779.txt","sha256":"288bfe1d522bcf675c7b31384b7f05fa005f72b64c2a499e8659ebc21d2fae34"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it describes objects for configuring\n parameters of the Neighborhood Discovery Protocol (NHDP) process on a\n router. The MIB module defined in this document, denoted NHDP-MIB,\n also reports state, performance information, and notifications about\n NHDP. This additional state and performance information is useful to\n troubleshoot problems and performance issues during neighbor\n discovery.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet ","scope_keywords":["6779","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 6779 This document defines a portion of the Management Information Base\n (MIB) for use with network management protocols in the Internet\n community. In particular, it describes objects for configuring\n parameters of the Neighborhood Discovery Protocol (NHDP) process on a\n router. The MIB module defined in this document, denoted NHDP-MIB,\n also reports state, performance information, and notifications about\n NHDP. This additional state and performance information is useful to\n troubleshoot problems and performance issues during neighbor\n discovery.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet  6779 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1218","type":"specification","body":"IETF","designation":"RFC 1218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1218.txt","https://www.rfc-editor.org/rfc/rfc1218.pdf"],"folder":"IETF/RFC-1218","files":{"txt":{"path":"standards/IETF/RFC-1218/RFC-1218.txt","sha256":"c8980cc9d5225d8b8b67496334a83ffb837498a4c4e0877a52ab7652ee5aae7e"}},"tags":["nested-reference","unchanged"],"summary":"This is one of a series of documents produced for discussion within\n the North American Directory Forum. Distribution, with attribution,\n is unlimited. This document is being circulated for comment. The\n deadline for comments is July 1, 1991. Comments should be directed\n to the contact given on page 16.\n\n1. Introduction\n\n Computer networks form the infrastructure between the users they\n interconnect. For example, the electronic mail service offered by\n computer networks provides a means for users to collaborate towards\n some common goal. In the simplest cases, this collaboration may be\n solely for the dissemination of information. In other cases, two\n\nNADF [Page 1]\n\f\nRFC 1218 A Naming Scheme for c=US April 1991\n\n users may work on a joint research project, using electronic mail as\n their primary means of communication.\n\n However, networks themselves are built on an underlying naming and\n","scope_keywords":["1218","attribute","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1255","folder":"IETF/RFC-1255","source":"IETF/RFC-1255/RFC-1255.txt","version":null}],"search_text":"IETF RFC 1218 This is one of a series of documents produced for discussion within\n the North American Directory Forum. Distribution, with attribution,\n is unlimited. This document is being circulated for comment. The\n deadline for comments is July 1, 1991. Comments should be directed\n to the contact given on page 16.\n\n1. Introduction\n\n Computer networks form the infrastructure between the users they\n interconnect. For example, the electronic mail service offered by\n computer networks provides a means for users to collaborate towards\n some common goal. In the simplest cases, this collaboration may be\n solely for the dissemination of information. In other cases, two\n\nNADF [Page 1]\n\f\nRFC 1218 A Naming Scheme for c=US April 1991\n\n users may work on a joint research project, using electronic mail as\n their primary means of communication.\n\n However, networks themselves are built on an underlying naming and\n 1218 attribute key subject nested-reference unchanged"},{"id":"IETF RFC 3531","type":"specification","body":"IETF","designation":"RFC 3531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3531.txt","https://www.rfc-editor.org/rfc/rfc3531.pdf"],"folder":"IETF/RFC-3531","files":{"txt":{"path":"standards/IETF/RFC-3531/RFC-3531.txt","sha256":"b1c766768a28fe0fc9a60be32339db7ddbfc74dd5bcc4050c18f7cbfded061f4"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method to manage the assignment of bits of\n an IPv6 address block or range. When an organisation needs to make\n an address plan for its subnets or when an ISP needs to make an\n address plan for its customers, this method enables the organisation\n to postpone the final decision on the number of bits to partition in\n the address space they have. It does it by keeping the bits around\n the borders of the partition to be free as long as possible. This\n scheme is applicable to any bits addressing scheme using bits with\n partitions in the space, but its first intended use is for IPv6. It\n is a generalization of RFC 1219 and can be used for IPv6 assignments.","scope_keywords":["3531","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null}],"search_text":"IETF RFC 3531 This document proposes a method to manage the assignment of bits of\n an IPv6 address block or range. When an organisation needs to make\n an address plan for its subnets or when an ISP needs to make an\n address plan for its customers, this method enables the organisation\n to postpone the final decision on the number of bits to partition in\n the address space they have. It does it by keeping the bits around\n the borders of the partition to be free as long as possible. This\n scheme is applicable to any bits addressing scheme using bits with\n partitions in the space, but its first intended use is for IPv6. It\n is a generalization of RFC 1219 and can be used for IPv6 assignments. 3531 algorithm nested-reference unchanged"},{"id":"IETF RFC 1339","type":"specification","body":"IETF","designation":"RFC 1339","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1339.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1339.txt","https://www.rfc-editor.org/rfc/rfc1339.pdf"],"folder":"IETF/RFC-1339","files":{"txt":{"path":"standards/IETF/RFC-1339/RFC-1339.txt","sha256":"83f3a1e290c267637f9ea440a2edba5ed24e4aeda38f4d15720e743c1ad36770"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Dorner\nRequest for Comments: 1339 P. Resnick\n U. of Illinois at Urbana-Champaign\n June 1992\n\n Remote Mail Checking Protocol\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This RFC defines a protocol to provide a mail checking service to be\n used between a client and server pair. Typically, a small program on\n a client workstation would use the protocol to query a server in\n order to find out whether new mail has arrived for a specified user.\n\nIntent\n\n This RFC defines a simple, low-overhead protocol for checking the\n status of a maildrop on a host. It is primarily intende","scope_keywords":["1339","authentication","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1339 Network Working Group S. Dorner\nRequest for Comments: 1339 P. Resnick\n U. of Illinois at Urbana-Champaign\n June 1992\n\n Remote Mail Checking Protocol\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This RFC defines a protocol to provide a mail checking service to be\n used between a client and server pair. Typically, a small program on\n a client workstation would use the protocol to query a server in\n order to find out whether new mail has arrived for a specified user.\n\nIntent\n\n This RFC defines a simple, low-overhead protocol for checking the\n status of a maildrop on a host. It is primarily intende 1339 authentication validation nested-reference unchanged"},{"id":"IETF RFC 1460","type":"specification","body":"IETF","designation":"RFC 1460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1460.txt","https://www.rfc-editor.org/rfc/rfc1460.pdf"],"folder":"IETF/RFC-1460","files":{"txt":{"path":"standards/IETF/RFC-1460/RFC-1460.txt","sha256":"4179034f5bdc3241d5f2aa206079e3a26b9f80e71d0d5cdc56bc4efa12c755ec"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Rose\nRequest for Comments: 1460 Dover Beach Consulting, Inc.\nObsoletes: 1225 June 1993\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nOverview\n\n This memo is a revision to RFC 1225, a Draft Standard. It makes the\n following changes from that document:\n\n - the RPOP facility is removed;\n\n - the optional APOP facility is added (which is in interoperable,\n operational use in at least three implementations);\n\n - a typo was corrected with respect to the interaction of LAST\n and RSET;\n\n - section numbers were added; and,\n\n - an acknowledgements se","scope_keywords":["1460","authorization","crl","delivery","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1725","folder":"IETF/RFC-1725","source":"IETF/RFC-1725/RFC-1725.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null}],"search_text":"IETF RFC 1460 Network Working Group M. Rose\nRequest for Comments: 1460 Dover Beach Consulting, Inc.\nObsoletes: 1225 June 1993\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nOverview\n\n This memo is a revision to RFC 1225, a Draft Standard. It makes the\n following changes from that document:\n\n - the RPOP facility is removed;\n\n - the optional APOP facility is added (which is in interoperable,\n operational use in at least three implementations);\n\n - a typo was corrected with respect to the interaction of LAST\n and RSET;\n\n - section numbers were added; and,\n\n - an acknowledgements se 1460 authorization crl delivery key trust nested-reference unchanged"},{"id":"IETF RFC 1226","type":"specification","body":"IETF","designation":"RFC 1226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1226.txt","https://www.rfc-editor.org/rfc/rfc1226.pdf"],"folder":"IETF/RFC-1226","files":{"txt":{"path":"standards/IETF/RFC-1226/RFC-1226.txt","sha256":"d9882c8eb100b467bd5455a30a9ee629c50f048023c02c113cdcf5c9cf75e60e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kantor\nRequest for Comments: 1226 Univ. of Calif San Diego\n May 1991\n\n Internet Protocol Encapsulation of AX.25 Frames\n\nStatus of this Memo\n\n This memo describes a method for the encapsulation of AX.25 (the\n Amateur Packet-Radio Link-Layer Protocol) frames within IP packets.\n This technique is an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nThe AX.25 Amateur Packet-Radio Link-Layer Protocol\n\n The AX.25 Amateur Packet-Radio Link-Layer Protocol is described in\n the publication by that name [1], incorporated here by reference.\n\n Each AX.25 packet (\"frame\") is encapsulated in one IP datagram.\n Normally no AX.25 frame will excee","scope_keywords":["1226"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1226 Network Working Group B. Kantor\nRequest for Comments: 1226 Univ. of Calif San Diego\n May 1991\n\n Internet Protocol Encapsulation of AX.25 Frames\n\nStatus of this Memo\n\n This memo describes a method for the encapsulation of AX.25 (the\n Amateur Packet-Radio Link-Layer Protocol) frames within IP packets.\n This technique is an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nThe AX.25 Amateur Packet-Radio Link-Layer Protocol\n\n The AX.25 Amateur Packet-Radio Link-Layer Protocol is described in\n the publication by that name [1], incorporated here by reference.\n\n Each AX.25 packet (\"frame\") is encapsulated in one IP datagram.\n Normally no AX.25 frame will excee 1226 nested-reference unchanged"},{"id":"IETF RFC 6643","type":"specification","body":"IETF","designation":"RFC 6643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6643.txt","https://www.rfc-editor.org/rfc/rfc6643.pdf"],"folder":"IETF/RFC-6643","files":{"txt":{"path":"standards/IETF/RFC-6643/RFC-6643.txt","sha256":"470a6c516f163968e9bdb78a74ed52c74eda393880162db6c238179ea0ec18e3"}},"tags":["nested-reference","unchanged"],"summary":"YANG is a data modeling language used to model configuration and\n state data manipulated by the Network Configuration Protocol\n (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.\n The Structure of Management Information (SMIv2) defines fundamental\n data types, an object model, and the rules for writing and revising\n MIB modules for use with the Simple Network Management Protocol\n (SNMP). This document defines a translation of SMIv2 MIB modules\n into YANG modules, enabling read-only (config false) access to data\n objects defined in SMIv2 MIB modules via NETCONF.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IE","scope_keywords":["6643","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null}],"search_text":"IETF RFC 6643 YANG is a data modeling language used to model configuration and\n state data manipulated by the Network Configuration Protocol\n (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.\n The Structure of Management Information (SMIv2) defines fundamental\n data types, an object model, and the rules for writing and revising\n MIB modules for use with the Simple Network Management Protocol\n (SNMP). This document defines a translation of SMIv2 MIB modules\n into YANG modules, enabling read-only (config false) access to data\n objects defined in SMIv2 MIB modules via NETCONF.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IE 6643 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 123","type":"specification","body":"IETF","designation":"RFC 123","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc123.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc123.txt","https://www.rfc-editor.org/rfc/rfc123.pdf"],"folder":"IETF/RFC-123","files":{"txt":{"path":"standards/IETF/RFC-123/RFC-123.txt","sha256":"627ab3494c85f3e0cc7b7c0838b7dd89d14ab33a7c1003419a8425bad321de74"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Crocker\nRequest for Comments: 123 UCLA\nNIC #5837 20 April 71\nCategories: D.1\nObsoletes: RFCs 66, 80\nUpdates: RFCs 98, 101\n\n A Proferred Official ICP\n\nBy Initial Connection Protocol (ICP), I mean a third level protocol\nwhich is initiated by a user process at one site in order to contact a\nserver process at another site. Typically, the user process will be a\nTelnet and the server process will be a logger, but there may be other\ncases.\n\nIn this RFC, I wish to describe a family of ICPs suitable for\nestablishing one pair of connections (one in each direction) between any\nuser process and any server process, and to propose further a particular\nsubset of this family as the standard ICP for connecting user processes\nto loggers on systems which accept teletype-like devices.\n\nNotation\n\nWe have no standard notation for describing system calls which initiate\nand close connec","scope_keywords":["123","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 165","folder":"IETF/RFC-165","source":"IETF/RFC-165/RFC-165.txt","version":null}],"search_text":"IETF RFC 123 Network Working Group S. Crocker\nRequest for Comments: 123 UCLA\nNIC #5837 20 April 71\nCategories: D.1\nObsoletes: RFCs 66, 80\nUpdates: RFCs 98, 101\n\n A Proferred Official ICP\n\nBy Initial Connection Protocol (ICP), I mean a third level protocol\nwhich is initiated by a user process at one site in order to contact a\nserver process at another site. Typically, the user process will be a\nTelnet and the server process will be a logger, but there may be other\ncases.\n\nIn this RFC, I wish to describe a family of ICPs suitable for\nestablishing one pair of connections (one in each direction) between any\nuser process and any server process, and to propose further a particular\nsubset of this family as the standard ICP for connecting user processes\nto loggers on systems which accept teletype-like devices.\n\nNotation\n\nWe have no standard notation for describing system calls which initiate\nand close connec 123 subject nested-reference unchanged"},{"id":"IETF RFC 165","type":"specification","body":"IETF","designation":"RFC 165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc165.txt","https://www.rfc-editor.org/rfc/rfc165.pdf"],"folder":"IETF/RFC-165","files":{"pdf":{"path":"standards/IETF/RFC-165/RFC-165.pdf","sha256":"aae586207ab9bf7c3b98cfc00d4345e458ebd729cbcea4093206cec36bde6e75"},"txt":{"path":"standards/IETF/RFC-165/RFC-165.txt","sha256":"add13dcd757ff702a6fb9de4397744d4f93e070b92f2395ff3ceed7dbe5e983e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 165 UCLA - NMC\nObsoletes: 123, 143, 145 May 25, 1971\nNIC: 6779\n\n A Preferred Official Initial Connection Protocol*\n\n This document specifies the their level protocol used to connect a\n user process at one site with a server process at another site. In\n one instance, the user process will be a Telnet and the server\n process will be a Logger, but there will be other cases.\n\n This document describes a family of Initial Connection Protocols\n (ICP's) suitable for establishing one pair of connections between any\n user process and any server process, and further to describe the\n parameter values for connecting Telnets and Loggers. The description\n will be at two levels, the third or user level, and the second or NCP\n level.\n\nThird Level Description\n\nNotation\n\n There is no standard notation for describing system calls, which\n initiate and clo","scope_keywords":["165"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 172","folder":"IETF/RFC-172","source":"IETF/RFC-172/RFC-172.txt","version":null},{"body":"IETF","designation":"RFC 264","folder":"IETF/RFC-264","source":"IETF/RFC-264/RFC-264.txt","version":null},{"body":"IETF","designation":"RFC 265","folder":"IETF/RFC-265","source":"IETF/RFC-265/RFC-265.txt","version":null}],"search_text":"IETF RFC 165 Network Working Group J. Postel\nRequest for Comments: 165 UCLA - NMC\nObsoletes: 123, 143, 145 May 25, 1971\nNIC: 6779\n\n A Preferred Official Initial Connection Protocol*\n\n This document specifies the their level protocol used to connect a\n user process at one site with a server process at another site. In\n one instance, the user process will be a Telnet and the server\n process will be a Logger, but there will be other cases.\n\n This document describes a family of Initial Connection Protocols\n (ICP's) suitable for establishing one pair of connections between any\n user process and any server process, and further to describe the\n parameter values for connecting Telnets and Loggers. The description\n will be at two levels, the third or user level, and the second or NCP\n level.\n\nThird Level Description\n\nNotation\n\n There is no standard notation for describing system calls, which\n initiate and clo 165 nested-reference unchanged"},{"id":"IETF RFC 4087","type":"specification","body":"IETF","designation":"RFC 4087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4087.txt","https://www.rfc-editor.org/rfc/rfc4087.pdf"],"folder":"IETF/RFC-4087","files":{"txt":{"path":"standards/IETF/RFC-4087/RFC-4087.txt","sha256":"c543e376d2e563ba1d38817ccde80ccf7b0fab26c658decbf29267251cc0cd2e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) module for use\n with network management protocols in the Internet community. In\n particular, it describes managed objects used for managing tunnels of\n any type over IPv4 and IPv6 networks. Extension MIB modules may be\n designed for managing protocol-specific objects. Likewise, extension\n MIB modules may be designed for managing security-specific objects.\n This MIB module does not support tunnels over non-IP networks.\n Management of such tunnels may be supported by other MIB modules.\n This memo obsoletes RFC 2667.\n\n1. Introduction\n\n Over the past several years, there has been a number of \"tunneling\"\n protocols specified by the IETF (see [RFC1241] for an early\n discussion of the model and examples). This document describes a\n Management Information Base (MIB) module used for managing tunnels of\n any type over IPv4 and IPv6 networks, in","scope_keywords":["4087","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 4087 This memo defines a Management Information Base (MIB) module for use\n with network management protocols in the Internet community. In\n particular, it describes managed objects used for managing tunnels of\n any type over IPv4 and IPv6 networks. Extension MIB modules may be\n designed for managing protocol-specific objects. Likewise, extension\n MIB modules may be designed for managing security-specific objects.\n This MIB module does not support tunnels over non-IP networks.\n Management of such tunnels may be supported by other MIB modules.\n This memo obsoletes RFC 2667.\n\n1. Introduction\n\n Over the past several years, there has been a number of \"tunneling\"\n protocols specified by the IETF (see [RFC1241] for an early\n discussion of the model and examples). This document describes a\n Management Information Base (MIB) module used for managing tunnels of\n any type over IPv4 and IPv6 networks, in 4087 management nested-reference unchanged"},{"id":"IETF RFC 7992","type":"specification","body":"IETF","designation":"RFC 7992","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7992.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7992.txt","https://www.rfc-editor.org/rfc/rfc7992.pdf"],"folder":"IETF/RFC-7992","files":{"txt":{"path":"standards/IETF/RFC-7992/RFC-7992.txt","sha256":"b29c14bc2570c006ad64e24d51481b9c0e3c5c6e994ff789122f27dede82a888"}},"tags":["nested-reference","unchanged"],"summary":"In order to meet the evolving needs of the Internet community, the\n canonical format for RFCs is changing from a plain-text, ASCII-only\n format to an XML format that will, in turn, be rendered into several\n publication formats. This document defines the HTML format that will\n be rendered for an RFC or Internet-Draft.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to p","scope_keywords":["7992","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7993","folder":"IETF/RFC-7993","source":"IETF/RFC-7993/RFC-7993.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null}],"search_text":"IETF RFC 7992 In order to meet the evolving needs of the Internet community, the\n canonical format for RFCs is changing from a plain-text, ASCII-only\n format to an XML format that will, in turn, be rendered into several\n publication formats. This document defines the HTML format that will\n be rendered for an RFC or Internet-Draft.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to p 7992 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1380","type":"specification","body":"IETF","designation":"RFC 1380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1380.txt","https://www.rfc-editor.org/rfc/rfc1380.pdf"],"folder":"IETF/RFC-1380","files":{"txt":{"path":"standards/IETF/RFC-1380/RFC-1380.txt","sha256":"d95f4c555b46460e4adbc0cdd16f893c36df730510bca1fe643d41a401529050"}},"tags":["nested-reference","unchanged"],"summary":"This memo summarizes issues surrounding the routing and addressing\n scaling problems in the IP architecture, and it provides a brief\n background of the ROAD group and related activities in the Internet\n Engineering Task Force (IETF).\n\n It also provides a preliminary report of the Internet Engineering\n Steering Group (IESG) deliberations on how these routing and\n addressing issues should be pursued in the Internet Architecture\n Board (IAB)/IETF.\n\nAcknowledgements\n\n This note draws principally from two sources: the output from the\n ROAD group, as reported at the San Diego IETF meeting, and on\n numerous detailed discussions in the IESG following the San Diego\n IETF meeting. Zheng Wang, Bob Hinden, Kent England, and Bob Smart\n provided input for the \"Criteria For Bigger Internet Addresses\"\n section below. Greg Vaudreuil prepared the final version of the\n bibliography, based on previous bibli","scope_keywords":["1380","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1719","folder":"IETF/RFC-1719","source":"IETF/RFC-1719/RFC-1719.txt","version":null},{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1955","folder":"IETF/RFC-1955","source":"IETF/RFC-1955/RFC-1955.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null}],"search_text":"IETF RFC 1380 This memo summarizes issues surrounding the routing and addressing\n scaling problems in the IP architecture, and it provides a brief\n background of the ROAD group and related activities in the Internet\n Engineering Task Force (IETF).\n\n It also provides a preliminary report of the Internet Engineering\n Steering Group (IESG) deliberations on how these routing and\n addressing issues should be pursued in the Internet Architecture\n Board (IAB)/IETF.\n\nAcknowledgements\n\n This note draws principally from two sources: the output from the\n ROAD group, as reported at the San Diego IETF meeting, and on\n numerous detailed discussions in the IESG following the San Diego\n IETF meeting. Zheng Wang, Bob Hinden, Kent England, and Bob Smart\n provided input for the \"Criteria For Bigger Internet Addresses\"\n section below. Greg Vaudreuil prepared the final version of the\n bibliography, based on previous bibli 1380 pid nested-reference unchanged"},{"id":"IETF RFC 1629","type":"specification","body":"IETF","designation":"RFC 1629","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1629.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1629.txt","https://www.rfc-editor.org/rfc/rfc1629.pdf"],"folder":"IETF/RFC-1629","files":{"txt":{"path":"standards/IETF/RFC-1629/RFC-1629.txt","sha256":"b1268366d56d6eac37c593b07ab52d5e6f8586574af71f767fedbcae20957600"}},"tags":["nested-reference","unchanged"],"summary":"CLNP is currently being deployed in the Internet. This is useful to\n support OSI and DECnet(tm) traffic. In addition, CLNP has been\n proposed as a possible IPng candidate, to provide a long-term\n solution to IP address exhaustion. Required as part of the CLNP\n infrastructure are guidelines for network service access point (NSAP)\n address assignment. This paper provides guidelines for allocating\n NSAP addresses in the Internet.\n\n The guidelines provided in this paper have been the basis for initial\n deployment of CLNP in the Internet, and have proven very valuable\n both as an aid to scaling of CLNP routing, and for address\n administration.\n\nColella, Callon, Gardner & Rekhter [Page 1]\n\f\nRFC 1629 NSAP Guidelines May 1994","scope_keywords":["1629"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null},{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 1629 CLNP is currently being deployed in the Internet. This is useful to\n support OSI and DECnet(tm) traffic. In addition, CLNP has been\n proposed as a possible IPng candidate, to provide a long-term\n solution to IP address exhaustion. Required as part of the CLNP\n infrastructure are guidelines for network service access point (NSAP)\n address assignment. This paper provides guidelines for allocating\n NSAP addresses in the Internet.\n\n The guidelines provided in this paper have been the basis for initial\n deployment of CLNP in the Internet, and have proven very valuable\n both as an aid to scaling of CLNP routing, and for address\n administration.\n\nColella, Callon, Gardner & Rekhter [Page 1]\n\f\nRFC 1629 NSAP Guidelines May 1994 1629 nested-reference unchanged"},{"id":"IETF RFC 2556","type":"specification","body":"IETF","designation":"RFC 2556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2556.txt","https://www.rfc-editor.org/rfc/rfc2556.pdf"],"folder":"IETF/RFC-2556","files":{"txt":{"path":"standards/IETF/RFC-2556/RFC-2556.txt","sha256":"9a71a4c8d892c8f3a5fe7f01f220dbcfaea42214964d2299e56c162f3f18db52"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bradner\nRequest for Comments: 2556 Harvard University\nCategory: Informational March 1999\n\n OSI connectionless transport services on top\n of UDP Applicability Statement for Historic Status\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n RFC 1240, \"OSI connectionless transport services on top of UDP\", was\n published as a Proposed Standard in June 1991 but at this time there\n do not seem to be any implementations which follow RFC 1240. In\n addition there is a growing concern over using UDP-based transport\n protocols in environments where congestion is a possibility.\n\n1. Use of RFC 1240 Technology\n\n A message was sent to the IETF list in October","scope_keywords":["2556","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null}],"search_text":"IETF RFC 2556 Network Working Group S. Bradner\nRequest for Comments: 2556 Harvard University\nCategory: Informational March 1999\n\n OSI connectionless transport services on top\n of UDP Applicability Statement for Historic Status\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n RFC 1240, \"OSI connectionless transport services on top of UDP\", was\n published as a Proposed Standard in June 1991 but at this time there\n do not seem to be any implementations which follow RFC 1240. In\n addition there is a growing concern over using UDP-based transport\n protocols in environments where congestion is a possibility.\n\n1. Use of RFC 1240 Technology\n\n A message was sent to the IETF list in October 2556 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 1241","type":"specification","body":"IETF","designation":"RFC 1241","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1241.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1241.txt","https://www.rfc-editor.org/rfc/rfc1241.pdf"],"folder":"IETF/RFC-1241","files":{"pdf":{"path":"standards/IETF/RFC-1241/RFC-1241.pdf","sha256":"62d14f112d79eb16ccadb0f33b5b6a9132eaa4a58b93a82fc30a20815c65fa9f"},"txt":{"path":"standards/IETF/RFC-1241/RFC-1241.txt","sha256":"c2fc875d77a5babf43f769e8c5d37248d0a13cd8066eed5f7f363a857bf82355"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Woodburn\nRequest for Comments: 1241 SAIC\n D. Mills\n University of Delaware\n July 1991\n\n A Scheme for an Internet Encapsulation Protocol:\n Version 1\n\n1. Status of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n2. Glossary\n\n Clear Datagram -\n The unmodified IP datagram in the User Space before\n Encapsulation.\n\n Clear Header -\n The header portion of the Clear Datagram before\n Encapsulation. This header includes the IP header and\n possibly part or all of the next layer protocol header,\n i.e., the TCP header.\n\n Decapsulation -\n The stripping of the Encapsulation Header and forwarding\n of the Clear ","scope_keywords":["1241","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null}],"search_text":"IETF RFC 1241 Network Working Group R. Woodburn\nRequest for Comments: 1241 SAIC\n D. Mills\n University of Delaware\n July 1991\n\n A Scheme for an Internet Encapsulation Protocol:\n Version 1\n\n1. Status of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n2. Glossary\n\n Clear Datagram -\n The unmodified IP datagram in the User Space before\n Encapsulation.\n\n Clear Header -\n The header portion of the Clear Datagram before\n Encapsulation. This header includes the IP header and\n possibly part or all of the next layer protocol header,\n i.e., the TCP header.\n\n Decapsulation -\n The stripping of the Encapsulation Header and forwarding\n of the Clear  1241 delivery path nested-reference unchanged"},{"id":"IETF RFC 2473","type":"specification","body":"IETF","designation":"RFC 2473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2473.txt","https://www.rfc-editor.org/rfc/rfc2473.pdf"],"folder":"IETF/RFC-2473","files":{"txt":{"path":"standards/IETF/RFC-2473/RFC-2473.txt","sha256":"04a1489dd23d983dafad1d4c480f25e9d1b144fb1c5fe38c560239518e6e2fe9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the model and generic mechanisms for IPv6\n encapsulation of Internet packets, such as IPv6 and IPv4. The model\n and mechanisms can be applied to other protocol packets as well, such\n as AppleTalk, IPX, CLNP, or others.","scope_keywords":["2473","key","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 7040","folder":"IETF/RFC-7040","source":"IETF/RFC-7040/RFC-7040.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 2473 This document defines the model and generic mechanisms for IPv6\n encapsulation of Internet packets, such as IPv6 and IPv4. The model\n and mechanisms can be applied to other protocol packets as well, such\n as AppleTalk, IPX, CLNP, or others. 2473 key path risk nested-reference unchanged"},{"id":"IETF RFC 1242","type":"specification","body":"IETF","designation":"RFC 1242","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1242.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1242.txt","https://www.rfc-editor.org/rfc/rfc1242.pdf"],"folder":"IETF/RFC-1242","files":{"txt":{"path":"standards/IETF/RFC-1242/RFC-1242.txt","sha256":"9d7b1476a79f6b71c3729e26ea6b6b20446aa17d1e7c4834c21260fa74b1cb52"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses and defines a number of terms that are used in\n describing performance benchmarking tests and the results of such\n tests. The terms defined in this memo will be used in additional\n memos to define specific benchmarking tests and the suggested format\n to be used in reporting the results of each of the tests. This memo\n is a product of the Benchmarking Methodology Working Group (BMWG) of\n the Internet Engineering Task Force (IETF).\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This usually involves\n much \"smoke & mirrors\" used to confuse the user. This memo and\n follow-up memos attempt to define a specific set of terminology and\n tests that vendors can use to measure and report the performance\n characteristics of network devices. This will provide the user\n comparable data from diffe","scope_keywords":["1242","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1944","folder":"IETF/RFC-1944","source":"IETF/RFC-1944/RFC-1944.txt","version":null},{"body":"IETF","designation":"RFC 2285","folder":"IETF/RFC-2285","source":"IETF/RFC-2285/RFC-2285.txt","version":null},{"body":"IETF","designation":"RFC 2432","folder":"IETF/RFC-2432","source":"IETF/RFC-2432/RFC-2432.txt","version":null},{"body":"IETF","designation":"RFC 2544","folder":"IETF/RFC-2544","source":"IETF/RFC-2544/RFC-2544.txt","version":null},{"body":"IETF","designation":"RFC 2647","folder":"IETF/RFC-2647","source":"IETF/RFC-2647/RFC-2647.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null}],"search_text":"IETF RFC 1242 This memo discusses and defines a number of terms that are used in\n describing performance benchmarking tests and the results of such\n tests. The terms defined in this memo will be used in additional\n memos to define specific benchmarking tests and the suggested format\n to be used in reporting the results of each of the tests. This memo\n is a product of the Benchmarking Methodology Working Group (BMWG) of\n the Internet Engineering Task Force (IETF).\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This usually involves\n much \"smoke & mirrors\" used to confuse the user. This memo and\n follow-up memos attempt to define a specific set of terminology and\n tests that vendors can use to measure and report the performance\n characteristics of network devices. This will provide the user\n comparable data from diffe 1242 path policy nested-reference unchanged"},{"id":"IETF RFC 1944","type":"specification","body":"IETF","designation":"RFC 1944","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1944.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1944.txt","https://www.rfc-editor.org/rfc/rfc1944.pdf"],"folder":"IETF/RFC-1944","files":{"txt":{"path":"standards/IETF/RFC-1944/RFC-1944.txt","sha256":"f2aeda13cfeae205c13ad270c6ed13a07713d50ea34b949396ba0e028ddb06e0"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of a network\n interconnecting device. In addition to defining the tests this\n document also describes specific formats for reporting the results of\n the tests. Appendix A lists the tests and conditions that we believe\n should be included for specific cases and gives additional\n information about testing practices. Appendix B is a reference\n listing of maximum frame rates to be used with specific frame sizes\n on various media and Appendix C gives some examples of frame formats\n to be used in testing.\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This often involves\n \"smoke & mirrors\" to confuse the potential users of the products.\n\n This document defines a specific set of tests that vendo","scope_keywords":["1944"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2285","folder":"IETF/RFC-2285","source":"IETF/RFC-2285/RFC-2285.txt","version":null},{"body":"IETF","designation":"RFC 2432","folder":"IETF/RFC-2432","source":"IETF/RFC-2432/RFC-2432.txt","version":null},{"body":"IETF","designation":"RFC 2544","folder":"IETF/RFC-2544","source":"IETF/RFC-2544/RFC-2544.txt","version":null}],"search_text":"IETF RFC 1944 This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of a network\n interconnecting device. In addition to defining the tests this\n document also describes specific formats for reporting the results of\n the tests. Appendix A lists the tests and conditions that we believe\n should be included for specific cases and gives additional\n information about testing practices. Appendix B is a reference\n listing of maximum frame rates to be used with specific frame sizes\n on various media and Appendix C gives some examples of frame formats\n to be used in testing.\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This often involves\n \"smoke & mirrors\" to confuse the potential users of the products.\n\n This document defines a specific set of tests that vendo 1944 nested-reference unchanged"},{"id":"IETF RFC 2432","type":"specification","body":"IETF","designation":"RFC 2432","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2432.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2432.txt","https://www.rfc-editor.org/rfc/rfc2432.pdf"],"folder":"IETF/RFC-2432","files":{"txt":{"path":"standards/IETF/RFC-2432/RFC-2432.txt","sha256":"4230568a46a69351a0c7832b871e1f102d5052c5ebff3c1df8e30e6c31352518"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to define terminology specific to the\n benchmarking of multicast IP forwarding devices. It builds upon the\n tenets set forth in RFC 1242, RFC 2285, and other IETF Benchmarking\n Methodology Working Group (BMWG) efforts. This document seeks to\n extend these efforts to the multicast paradigm.\n\n The BMWG produces two major classes of documents: Benchmarking\n Terminology documents and Benchmarking Methodology documents. The\n Terminology documents present the benchmarks and other related terms.\n The Methodology documents define the procedures required to collect\n the benchmarks cited in the corresponding Terminology documents.\n\n1. Introduction\n\n Network forwarding devices are being required to take a single frame\n and support delivery to a number of destinations having membership to\n a particular group. As such, multicast support may place a different\n burden on","scope_keywords":["2432","delivery","path","profile","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null}],"search_text":"IETF RFC 2432 The purpose of this document is to define terminology specific to the\n benchmarking of multicast IP forwarding devices. It builds upon the\n tenets set forth in RFC 1242, RFC 2285, and other IETF Benchmarking\n Methodology Working Group (BMWG) efforts. This document seeks to\n extend these efforts to the multicast paradigm.\n\n The BMWG produces two major classes of documents: Benchmarking\n Terminology documents and Benchmarking Methodology documents. The\n Terminology documents present the benchmarks and other related terms.\n The Methodology documents define the procedures required to collect\n the benchmarks cited in the corresponding Terminology documents.\n\n1. Introduction\n\n Network forwarding devices are being required to take a single frame\n and support delivery to a number of destinations having membership to\n a particular group. As such, multicast support may place a different\n burden on 2432 delivery path profile qualified subject nested-reference unchanged"},{"id":"IETF RFC 2544","type":"specification","body":"IETF","designation":"RFC 2544","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2544.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2544.txt","https://www.rfc-editor.org/rfc/rfc2544.pdf"],"folder":"IETF/RFC-2544","files":{"txt":{"path":"standards/IETF/RFC-2544/RFC-2544.txt","sha256":"7627f4f29f6de93e2f9d7095e5c39105ac2910fcd9b528687cbd0060018bf9e0"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of a network\n interconnecting device. In addition to defining the tests this\n document also describes specific formats for reporting the results of\n the tests. Appendix A lists the tests and conditions that we believe\n should be included for specific cases and gives additional\n information about testing practices. Appendix B is a reference\n listing of maximum frame rates to be used with specific frame sizes\n on various media and Appendix C gives some examples of frame formats\n to be used in testing.\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This often involves\n \"smoke & mirrors\" to confuse the potential users of the products.\n\nBradner & McQuaid Informational [Page 1]\n\f\nRFC 2544 Bench","scope_keywords":["2544"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2647","folder":"IETF/RFC-2647","source":"IETF/RFC-2647/RFC-2647.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6985","folder":"IETF/RFC-6985","source":"IETF/RFC-6985/RFC-6985.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 2544 This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of a network\n interconnecting device. In addition to defining the tests this\n document also describes specific formats for reporting the results of\n the tests. Appendix A lists the tests and conditions that we believe\n should be included for specific cases and gives additional\n information about testing practices. Appendix B is a reference\n listing of maximum frame rates to be used with specific frame sizes\n on various media and Appendix C gives some examples of frame formats\n to be used in testing.\n\n1. Introduction\n\n Vendors often engage in \"specsmanship\" in an attempt to give their\n products a better position in the marketplace. This often involves\n \"smoke & mirrors\" to confuse the potential users of the products.\n\nBradner & McQuaid Informational [Page 1]\n\f\nRFC 2544 Bench 2544 nested-reference unchanged"},{"id":"IETF RFC 2647","type":"specification","body":"IETF","designation":"RFC 2647","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2647.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2647.txt","https://www.rfc-editor.org/rfc/rfc2647.pdf"],"folder":"IETF/RFC-2647","files":{"txt":{"path":"standards/IETF/RFC-2647/RFC-2647.txt","sha256":"153d54a544c4ed6daff8cbd7d9c506ed9f5042ad60685b0761f2d8482400c3af"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Newman\nRequest for Comments: 2647 Data Communications\nCategory: Informational August 1999\n\n Benchmarking Terminology for Firewall Performance\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction...................................................2\n 2. Existing definitions...........................................2\n 3. Term definitions...............................................3\n 3.1 Allowed traffic...............................................3\n 3.2 Application proxy.............................................3\n 3.3 Authentication................................................4\n 3.4 Bit forwarding rate.............","scope_keywords":["2647","authentication","identification","pid","policy","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 4487","folder":"IETF/RFC-4487","source":"IETF/RFC-4487/RFC-4487.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 2647 Network Working Group D. Newman\nRequest for Comments: 2647 Data Communications\nCategory: Informational August 1999\n\n Benchmarking Terminology for Firewall Performance\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction...................................................2\n 2. Existing definitions...........................................2\n 3. Term definitions...............................................3\n 3.1 Allowed traffic...............................................3\n 3.2 Application proxy.............................................3\n 3.3 Authentication................................................4\n 3.4 Bit forwarding rate............. 2647 authentication identification pid policy signature trust nested-reference unchanged"},{"id":"IETF RFC 3511","type":"specification","body":"IETF","designation":"RFC 3511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3511.txt","https://www.rfc-editor.org/rfc/rfc3511.pdf"],"folder":"IETF/RFC-3511","files":{"txt":{"path":"standards/IETF/RFC-3511/RFC-3511.txt","sha256":"409d86d0ec08631435b80ba5a8565c517e991446769890cb5558398a67621590"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of firewalls. In\n addition to defining the tests, this document also describes specific\n formats for reporting the results of the tests.\n\n This document is a product of the Benchmarking Methodology Working\n Group (BMWG) of the Internet Engineering Task Force (IETF).","scope_keywords":["3511","authentication","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 3511 This document discusses and defines a number of tests that may be\n used to describe the performance characteristics of firewalls. In\n addition to defining the tests, this document also describes specific\n formats for reporting the results of the tests.\n\n This document is a product of the Benchmarking Methodology Working\n Group (BMWG) of the Internet Engineering Task Force (IETF). 3511 authentication http nested-reference unchanged"},{"id":"IETF RFC 1281","type":"specification","body":"IETF","designation":"RFC 1281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1281.txt","https://www.rfc-editor.org/rfc/rfc1281.pdf"],"folder":"IETF/RFC-1281","files":{"txt":{"path":"standards/IETF/RFC-1281/RFC-1281.txt","sha256":"5d0a6db1a5cde0c7608453b7a8f8107a1edbb8805e5fffa26f876ce9b2f5f224"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Pethia\nRequest for Comments: 1281 Software Engineering Institute\n S. Crocker\n Trusted Information Systems, Inc.\n B. Fraser\n Software Engineering Institute\n November 1991\n\n Guidelines for the Secure Operation of the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nPreamble\n\n The purpose of this document is to provide a set of guidelines to aid\n in the secure operation of the Internet. During its history, the\n Internet has grown significantly and is now quite diverse. Its\n participants include government institutions and agencies, academic\n and research institutions, commercial network and electronic mail\n carriers, non-profit research centers and an increasing array of\n industrial organizations who are primarily users of the technology.\n D","scope_keywords":["1281","authorization","license","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1281 Network Working Group R. Pethia\nRequest for Comments: 1281 Software Engineering Institute\n S. Crocker\n Trusted Information Systems, Inc.\n B. Fraser\n Software Engineering Institute\n November 1991\n\n Guidelines for the Secure Operation of the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nPreamble\n\n The purpose of this document is to provide a set of guidelines to aid\n in the secure operation of the Internet. During its history, the\n Internet has grown significantly and is now quite diverse. Its\n participants include government institutions and agencies, academic\n and research institutions, commercial network and electronic mail\n carriers, non-profit research centers and an increasing array of\n industrial organizations who are primarily users of the technology.\n D 1281 authorization license management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 1765","type":"specification","body":"IETF","designation":"RFC 1765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1765.txt","https://www.rfc-editor.org/rfc/rfc1765.pdf"],"folder":"IETF/RFC-1765","files":{"txt":{"path":"standards/IETF/RFC-1765/RFC-1765.txt","sha256":"179484ee46a9959f9debff1845cf9e27e9544a1b0715a33717093a8fe0de1aad"}},"tags":["nested-reference","unchanged"],"summary":"Proper operation of the OSPF protocol requires that all OSPF routers\n maintain an identical copy of the OSPF link-state database. However,\n when the size of the link-state database becomes very large, some\n routers may be unable to keep the entire database due to resource\n shortages; we term this \"database overflow\". When database overflow\n is anticipated, the routers with limited resources can be\n accommodated by configuring OSPF stub areas and NSSAs. This memo\n details a way of gracefully handling unanticipated database\n overflows.\n\n This memo is a product of the OSPF Working Group. Please send\n comments to ospf@gated.cornell.edu.","scope_keywords":["1765","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null}],"search_text":"IETF RFC 1765 Proper operation of the OSPF protocol requires that all OSPF routers\n maintain an identical copy of the OSPF link-state database. However,\n when the size of the link-state database becomes very large, some\n routers may be unable to keep the entire database due to resource\n shortages; we term this \"database overflow\". When database overflow\n is anticipated, the routers with limited resources can be\n accommodated by configuring OSPF stub areas and NSSAs. This memo\n details a way of gracefully handling unanticipated database\n overflows.\n\n This memo is a product of the OSPF Working Group. Please send\n comments to ospf@gated.cornell.edu. 1765 management tls nested-reference unchanged"},{"id":"IETF RFC 1793","type":"specification","body":"IETF","designation":"RFC 1793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1793.txt","https://www.rfc-editor.org/rfc/rfc1793.pdf"],"folder":"IETF/RFC-1793","files":{"txt":{"path":"standards/IETF/RFC-1793/RFC-1793.txt","sha256":"c7af3e986c00c7da9f6cefb85f7ce37ed9e96f4645894a2e2cd954b216596da6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines enhancements to the OSPF protocol that allow\n efficient operation over \"demand circuits\". Demand circuits are\n network segments whose costs vary with usage; charges can be based\n both on connect time and on bytes/packets transmitted. Examples of\n demand circuits include ISDN circuits, X.25 SVCs, and dial-up lines.\n The periodic nature of OSPF routing traffic has until now required a\n demand circuit's underlying data-link connection to be constantly\n open, resulting in unwanted usage charges. With the modifications\n described herein, OSPF Hellos and the refresh of OSPF routing\n information are suppressed on demand circuits, allowing the\n underlying data-link connections to be closed when not carrying\n application traffic.\n\n Demand circuits and regular network segments (e.g., leased lines) are\n allowed to be combined in any manner. In other words, there are no\n topologica","scope_keywords":["1793","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4136","folder":"IETF/RFC-4136","source":"IETF/RFC-4136/RFC-4136.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 1793 This memo defines enhancements to the OSPF protocol that allow\n efficient operation over \"demand circuits\". Demand circuits are\n network segments whose costs vary with usage; charges can be based\n both on connect time and on bytes/packets transmitted. Examples of\n demand circuits include ISDN circuits, X.25 SVCs, and dial-up lines.\n The periodic nature of OSPF routing traffic has until now required a\n demand circuit's underlying data-link connection to be constantly\n open, resulting in unwanted usage charges. With the modifications\n described herein, OSPF Hellos and the refresh of OSPF routing\n information are suppressed on demand circuits, allowing the\n underlying data-link connections to be closed when not carrying\n application traffic.\n\n Demand circuits and regular network segments (e.g., leased lines) are\n allowed to be combined in any manner. In other words, there are no\n topologica 1793 algorithm nested-reference unchanged"},{"id":"IETF RFC 2329","type":"specification","body":"IETF","designation":"RFC 2329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2329.txt","https://www.rfc-editor.org/rfc/rfc2329.pdf"],"folder":"IETF/RFC-2329","files":{"txt":{"path":"standards/IETF/RFC-2329/RFC-2329.txt","sha256":"a68e3035ccf2ed12028a700c1187837c773a91a9f9416ff44488fdb2fa5f569f"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents how the requirements for advancing a routing\n protocol to Full Standard, set out in [Ref2], have been met for\n OSPFv2.\n\n Please send comments to ospf@gated.cornell.edu.","scope_keywords":["2329","algorithm","authentication","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null}],"search_text":"IETF RFC 2329 This memo documents how the requirements for advancing a routing\n protocol to Full Standard, set out in [Ref2], have been met for\n OSPFv2.\n\n Please send comments to ospf@gated.cornell.edu. 2329 algorithm authentication key path presentation nested-reference unchanged"},{"id":"IETF RFC 1338","type":"specification","body":"IETF","designation":"RFC 1338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1338.txt","https://www.rfc-editor.org/rfc/rfc1338.pdf"],"folder":"IETF/RFC-1338","files":{"txt":{"path":"standards/IETF/RFC-1338/RFC-1338.txt","sha256":"32f1be85ce0269e68f8779d14da764361227443f783e7e4fda93b005b4e415a8"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses strategies for address assignment of the existing\n IP address space with a view to conserve the address space and stem\n the explosive growth of routing tables in default-route-free routers\n run by transit routing domain providers.","scope_keywords":["1338"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1366","folder":"IETF/RFC-1366","source":"IETF/RFC-1366/RFC-1366.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1383","folder":"IETF/RFC-1383","source":"IETF/RFC-1383/RFC-1383.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1466","folder":"IETF/RFC-1466","source":"IETF/RFC-1466/RFC-1466.txt","version":null},{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1481","folder":"IETF/RFC-1481","source":"IETF/RFC-1481/RFC-1481.txt","version":null},{"body":"IETF","designation":"RFC 1482","folder":"IETF/RFC-1482","source":"IETF/RFC-1482/RFC-1482.txt","version":null},{"body":"IETF","designation":"RFC 1518","folder":"IETF/RFC-1518","source":"IETF/RFC-1518/RFC-1518.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1710","folder":"IETF/RFC-1710","source":"IETF/RFC-1710/RFC-1710.txt","version":null},{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1338 This memo discusses strategies for address assignment of the existing\n IP address space with a view to conserve the address space and stem\n the explosive growth of routing tables in default-route-free routers\n run by transit routing domain providers. 1338 nested-reference unchanged"},{"id":"IETF RFC 1519","type":"specification","body":"IETF","designation":"RFC 1519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1519.txt","https://www.rfc-editor.org/rfc/rfc1519.pdf"],"folder":"IETF/RFC-1519","files":{"txt":{"path":"standards/IETF/RFC-1519/RFC-1519.txt","sha256":"78b260b4b788a0c3fb1aad5ac649ba73a928a5768d729da009d9d7a9e87432af"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses strategies for address assignment of the existing\n IP address space with a view to conserve the address space and stem\n the explosive growth of routing tables in default-route-free routers.","scope_keywords":["1519"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1520","folder":"IETF/RFC-1520","source":"IETF/RFC-1520/RFC-1520.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1631","folder":"IETF/RFC-1631","source":"IETF/RFC-1631/RFC-1631.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1655","folder":"IETF/RFC-1655","source":"IETF/RFC-1655/RFC-1655.txt","version":null},{"body":"IETF","designation":"RFC 1678","folder":"IETF/RFC-1678","source":"IETF/RFC-1678/RFC-1678.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1772","folder":"IETF/RFC-1772","source":"IETF/RFC-1772/RFC-1772.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1787","folder":"IETF/RFC-1787","source":"IETF/RFC-1787/RFC-1787.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1817","folder":"IETF/RFC-1817","source":"IETF/RFC-1817/RFC-1817.txt","version":null},{"body":"IETF","designation":"RFC 1878","folder":"IETF/RFC-1878","source":"IETF/RFC-1878/RFC-1878.txt","version":null},{"body":"IETF","designation":"RFC 1918","folder":"IETF/RFC-1918","source":"IETF/RFC-1918/RFC-1918.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2008","folder":"IETF/RFC-2008","source":"IETF/RFC-2008/RFC-2008.txt","version":null},{"body":"IETF","designation":"RFC 2036","folder":"IETF/RFC-2036","source":"IETF/RFC-2036/RFC-2036.txt","version":null},{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1519 This memo discusses strategies for address assignment of the existing\n IP address space with a view to conserve the address space and stem\n the explosive growth of routing tables in default-route-free routers. 1519 nested-reference unchanged"},{"id":"IETF RFC 3137","type":"specification","body":"IETF","designation":"RFC 3137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3137.txt","https://www.rfc-editor.org/rfc/rfc3137.pdf"],"folder":"IETF/RFC-3137","files":{"txt":{"path":"standards/IETF/RFC-3137/RFC-3137.txt","sha256":"f08d1dfac9176115b0fd3b74eb7c5b358375494d8d22ed5481bf0986712d1283"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Retana\nRequest for Comments: 3137 L. Nguyen\nCategory: Informational R. White\n Cisco Systems\n A. Zinin\n Nexsi Systems\n D. McPherson\n Amber Networks\n June 2001\n\n OSPF Stub Router Advertisement\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo describes a backward-compatible technique that may be used\n by OSPF (Open Shortest Path First) implementations to advertise\n unavailability to forward transit traffic or to lower the preference\n level for the paths through such a router. In some cases, it is\n desirable not to route transit traffic via a specific OSPF router.\n However, OSPF does not specify a standard way to accomplish this.\n\n1. Mo","scope_keywords":["3137","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 6987","folder":"IETF/RFC-6987","source":"IETF/RFC-6987/RFC-6987.txt","version":null}],"search_text":"IETF RFC 3137 Network Working Group A. Retana\nRequest for Comments: 3137 L. Nguyen\nCategory: Informational R. White\n Cisco Systems\n A. Zinin\n Nexsi Systems\n D. McPherson\n Amber Networks\n June 2001\n\n OSPF Stub Router Advertisement\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo describes a backward-compatible technique that may be used\n by OSPF (Open Shortest Path First) implementations to advertise\n unavailability to forward transit traffic or to lower the preference\n level for the paths through such a router. In some cases, it is\n desirable not to route transit traffic via a specific OSPF router.\n However, OSPF does not specify a standard way to accomplish this.\n\n1. Mo 3137 path nested-reference unchanged"},{"id":"IETF RFC 6987","type":"specification","body":"IETF","designation":"RFC 6987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6987.txt","https://www.rfc-editor.org/rfc/rfc6987.pdf"],"folder":"IETF/RFC-6987","files":{"txt":{"path":"standards/IETF/RFC-6987/RFC-6987.txt","sha256":"63b9e453c4e04fe160387cde5b2e2836cd9de49ed04b531d74bcbfc0496e9662"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a backward-compatible technique that may be\n used by OSPF (Open Shortest Path First) implementations to advertise\n a router's unavailability to forward transit traffic or to lower the\n preference level for the paths through such a router.\n\n This document obsoletes RFC 3137.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on","scope_keywords":["6987","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 6987 This document describes a backward-compatible technique that may be\n used by OSPF (Open Shortest Path First) implementations to advertise\n a router's unavailability to forward transit traffic or to lower the\n preference level for the paths through such a router.\n\n This document obsoletes RFC 3137.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on 6987 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 1264","type":"specification","body":"IETF","designation":"RFC 1264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1264.txt","https://www.rfc-editor.org/rfc/rfc1264.pdf"],"folder":"IETF/RFC-1264","files":{"txt":{"path":"standards/IETF/RFC-1264/RFC-1264.txt","sha256":"d6058e59a8f1ac08689262a0f33b7921f738dcd16f4facb51b293c01ca336f31"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 1264 BBN\n October 1991\n\n Internet Engineering Task Force\n Internet Routing Protocol Standardization Criteria\n\nStatus of this Memo\n\n This informational RFC presents procedures for creating and\n documenting Internet standards on routing protocols. These\n procedures have been established by the Internet Activities Board\n (IAB) in consultation with the Internet Engineering Steering Group\n (IESG). Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n The IAB and the IESG have evolved a three-stage Internet\n standardization process. This process is explained in the \"IAB\n Official Protocol Standards\", published as an RFC several times a\n year (the current version is RFC 1250).\n\n In brief, the three stages of Internet standardization are Proposed\n (which requires a well written, openly reviewed specification), Draft\n (which requires Pro","scope_keywords":["1264","algorithm","algorithms","authentication","key","management","pid","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1266","folder":"IETF/RFC-1266","source":"IETF/RFC-1266/RFC-1266.txt","version":null},{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1387","folder":"IETF/RFC-1387","source":"IETF/RFC-1387/RFC-1387.txt","version":null},{"body":"IETF","designation":"RFC 1585","folder":"IETF/RFC-1585","source":"IETF/RFC-1585/RFC-1585.txt","version":null},{"body":"IETF","designation":"RFC 1721","folder":"IETF/RFC-1721","source":"IETF/RFC-1721/RFC-1721.txt","version":null},{"body":"IETF","designation":"RFC 1722","folder":"IETF/RFC-1722","source":"IETF/RFC-1722/RFC-1722.txt","version":null},{"body":"IETF","designation":"RFC 1773","folder":"IETF/RFC-1773","source":"IETF/RFC-1773/RFC-1773.txt","version":null},{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 2005","folder":"IETF/RFC-2005","source":"IETF/RFC-2005/RFC-2005.txt","version":null},{"body":"IETF","designation":"RFC 2329","folder":"IETF/RFC-2329","source":"IETF/RFC-2329/RFC-2329.txt","version":null},{"body":"IETF","designation":"RFC 2357","folder":"IETF/RFC-2357","source":"IETF/RFC-2357/RFC-2357.txt","version":null},{"body":"IETF","designation":"RFC 4794","folder":"IETF/RFC-4794","source":"IETF/RFC-4794/RFC-4794.txt","version":null},{"body":"IETF","designation":"RFC 6982","folder":"IETF/RFC-6982","source":"IETF/RFC-6982/RFC-6982.txt","version":null},{"body":"IETF","designation":"RFC 7120","folder":"IETF/RFC-7120","source":"IETF/RFC-7120/RFC-7120.txt","version":null},{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null}],"search_text":"IETF RFC 1264 Network Working Group R. Hinden\nRequest for Comments: 1264 BBN\n October 1991\n\n Internet Engineering Task Force\n Internet Routing Protocol Standardization Criteria\n\nStatus of this Memo\n\n This informational RFC presents procedures for creating and\n documenting Internet standards on routing protocols. These\n procedures have been established by the Internet Activities Board\n (IAB) in consultation with the Internet Engineering Steering Group\n (IESG). Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n The IAB and the IESG have evolved a three-stage Internet\n standardization process. This process is explained in the \"IAB\n Official Protocol Standards\", published as an RFC several times a\n year (the current version is RFC 1250).\n\n In brief, the three stages of Internet standardization are Proposed\n (which requires a well written, openly reviewed specification), Draft\n (which requires Pro 1264 algorithm algorithms authentication key management pid risk nested-reference unchanged"},{"id":"IETF RFC 2377","type":"specification","body":"IETF","designation":"RFC 2377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2377.txt","https://www.rfc-editor.org/rfc/rfc2377.pdf"],"folder":"IETF/RFC-2377","files":{"txt":{"path":"standards/IETF/RFC-2377/RFC-2377.txt","sha256":"2a7303147fb5f03f395e2df682213c4b13584262d663b11c228c772b556c4930"}},"tags":["nested-reference","unchanged"],"summary":"Application of the conventional X.500 approach to naming has\n heretofore, in the experience of the authors, proven to be an\n obstacle to the wide deployment of directory-enabled applications on\n the Internet. We propose a new directory naming plan that leverages\n the strengths of the most popular and successful Internet naming\n schemes for naming objects in a hierarchical directory. This plan\n can, we believe, by extending the X.500 approach to naming,\n facilitate the creation of an Internet White Pages Service (IWPS) and\n other directory-enabled applications by overcoming the problems\n encountered by those using the conventional X.500 approach.","scope_keywords":["2377","attribute","attributes","identification","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null}],"search_text":"IETF RFC 2377 Application of the conventional X.500 approach to naming has\n heretofore, in the experience of the authors, proven to be an\n obstacle to the wide deployment of directory-enabled applications on\n the Internet. We propose a new directory naming plan that leverages\n the strengths of the most popular and successful Internet naming\n schemes for naming objects in a hierarchical directory. This plan\n can, we believe, by extending the X.500 approach to naming,\n facilitate the creation of an Internet White Pages Service (IWPS) and\n other directory-enabled applications by overcoming the problems\n encountered by those using the conventional X.500 approach. 2377 attribute attributes identification registered nested-reference unchanged"},{"id":"IETF RFC 1900","type":"specification","body":"IETF","designation":"RFC 1900","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1900.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1900.txt","https://www.rfc-editor.org/rfc/rfc1900.pdf"],"folder":"IETF/RFC-1900","files":{"txt":{"path":"standards/IETF/RFC-1900/RFC-1900.txt","sha256":"9b0dd67782e6885cef47d8d0239dea103ab9e87f601db0e07db66ee2c1082340"}},"tags":["nested-reference","unchanged"],"summary":"Renumbering, i.e., changes in the IP addressing information of\n various network components, is likely to become more and more\n widespread and common. The Internet Architecture Board (IAB) would\n like to stress the need to develop and deploy solutions that would\n facilitate such changes.","scope_keywords":["1900","authentication","qualified","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 1900 Renumbering, i.e., changes in the IP addressing information of\n various network components, is likely to become more and more\n widespread and common. The Internet Architecture Board (IAB) would\n like to stress the need to develop and deploy solutions that would\n facilitate such changes. 1900 authentication qualified risk nested-reference unchanged"},{"id":"IETF RFC 2005","type":"specification","body":"IETF","designation":"RFC 2005","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2005.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2005.txt","https://www.rfc-editor.org/rfc/rfc2005.pdf"],"folder":"IETF/RFC-2005","files":{"txt":{"path":"standards/IETF/RFC-2005/RFC-2005.txt","sha256":"7c1622abd10c940dad08c4bbb039231dc5df998c3a1d2b09e86ca35ed18fdd6f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Solomon\nRequest for Comments: 2005 Motorola\nCategory: Standards Track October 1996\n\n Applicability Statement for IP Mobility Support\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n As required by [RFC 1264], this report discusses the applicability of\n Mobile IP to provide host mobility in the Internet. In particular,\n this document describes the key features of Mobile IP and shows how\n the requirements for advancement to Proposed Standard RFC have been\n satisfied.\n\n1. Protocol Overview\n\n Mobile IP provides an efficient, scalable mechanism for","scope_keywords":["2005","algorithm","algorithms","authentication","key","management","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2209","folder":"IETF/RFC-2209","source":"IETF/RFC-2209/RFC-2209.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 2005 Network Working Group J. Solomon\nRequest for Comments: 2005 Motorola\nCategory: Standards Track October 1996\n\n Applicability Statement for IP Mobility Support\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n As required by [RFC 1264], this report discusses the applicability of\n Mobile IP to provide host mobility in the Internet. In particular,\n this document describes the key features of Mobile IP and shows how\n the requirements for advancement to Proposed Standard RFC have been\n satisfied.\n\n1. Protocol Overview\n\n Mobile IP provides an efficient, scalable mechanism for 2005 algorithm algorithms authentication key management path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2281","type":"specification","body":"IETF","designation":"RFC 2281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2281.txt","https://www.rfc-editor.org/rfc/rfc2281.pdf"],"folder":"IETF/RFC-2281","files":{"txt":{"path":"standards/IETF/RFC-2281/RFC-2281.txt","sha256":"743ee61a3f257fca58d7a20e5546cee2b00e6e5ae9d5978f27dc4be0d2df1dad"}},"tags":["nested-reference","unchanged"],"summary":"The memo specifies the Hot Standby Router Protocol (HSRP). The goal\n of the protocol is to allow hosts to appear to use a single router\n and to maintain connectivity even if the actual first hop router they\n are using fails. Multiple routers participate in this protocol and\n in concert create the illusion of a single virtual router. The\n protocol insures that one and only one of the routers is forwarding\n packets on behalf of the virtual router. End hosts forward their\n packets to the virtual router.\n\n The router forwarding packets is known as the active router. A\n standby router is selected to replace the active router should it\n fail. The protocol provides a mechanism for determining active and\n standby routers, using the IP addresses on the participating routers.\n If an active router fails a standby router can take over without a\n major interruption in the host's connectivity. This me","scope_keywords":["2281","license","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null}],"search_text":"IETF RFC 2281 The memo specifies the Hot Standby Router Protocol (HSRP). The goal\n of the protocol is to allow hosts to appear to use a single router\n and to maintain connectivity even if the actual first hop router they\n are using fails. Multiple routers participate in this protocol and\n in concert create the illusion of a single virtual router. The\n protocol insures that one and only one of the routers is forwarding\n packets on behalf of the virtual router. End hosts forward their\n packets to the virtual router.\n\n The router forwarding packets is known as the active router. A\n standby router is selected to replace the active router should it\n fail. The protocol provides a mechanism for determining active and\n standby routers, using the IP addresses on the participating routers.\n If an active router fails a standby router can take over without a\n major interruption in the host's connectivity. This me 2281 license management nested-reference unchanged"},{"id":"IETF RFC 3012","type":"specification","body":"IETF","designation":"RFC 3012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3012.txt","https://www.rfc-editor.org/rfc/rfc3012.pdf"],"folder":"IETF/RFC-3012","files":{"txt":{"path":"standards/IETF/RFC-3012/RFC-3012.txt","sha256":"17a46a293b4ef4bd575fabbaf3747d4c2a8c993b5f33e65dd6225287f4e81e8c"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP, as originally specified, defines an authentication\n extension (the Mobile-Foreign Authentication extension) by which a\n mobile node can authenticate itself to a foreign agent.\n Unfortunately, this extension does not provide ironclad replay\n protection for the foreign agent, and does not allow for the use of\n existing techniques (such as CHAP) for authenticating portable\n computer devices. In this specification, we define extensions for\n the Mobile IP Agent Advertisements and the Registration Request that\n allow a foreign agent to use a challenge/response mechanism to\n authenticate the mobile node.\n\nPerkins & Calhoun Standards Track [Page 1]\n\f\nRFC 3012 Mobile IPv4 Challenge/Response November 2000","scope_keywords":["3012","algorithm","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null}],"search_text":"IETF RFC 3012 Mobile IP, as originally specified, defines an authentication\n extension (the Mobile-Foreign Authentication extension) by which a\n mobile node can authenticate itself to a foreign agent.\n Unfortunately, this extension does not provide ironclad replay\n protection for the foreign agent, and does not allow for the use of\n existing techniques (such as CHAP) for authenticating portable\n computer devices. In this specification, we define extensions for\n the Mobile IP Agent Advertisements and the Registration Request that\n allow a foreign agent to use a challenge/response mechanism to\n authenticate the mobile node.\n\nPerkins & Calhoun Standards Track [Page 1]\n\f\nRFC 3012 Mobile IPv4 Challenge/Response November 2000 3012 algorithm authentication key nested-reference unchanged"},{"id":"IETF RFC 3543","type":"specification","body":"IETF","designation":"RFC 3543","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3543.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3543.txt","https://www.rfc-editor.org/rfc/rfc3543.pdf"],"folder":"IETF/RFC-3543","files":{"txt":{"path":"standards/IETF/RFC-3543/RFC-3543.txt","sha256":"4fc854cd88ee0cf04ab01f5a33cda703db6189accc68db585db2aa13eadbce6f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Mobile IPv4 Registration Revocation mechanism\n whereby a mobility agent involved in providing Mobile IP services to\n a mobile node can notify the other mobility agent providing Mobile IP\n services to the same mobile node of the termination of this\n registration. The mechanism is also usable by a home agent to notify\n a co-located mobile node of the termination of its binding as well.\n Moreover, the mechanism provides for this notification to be\n acknowledged. A signaling mechanism already defined by the Mobile\n IPv4 protocol is leveraged as a way to inform a mobile node of the\n revocation of its binding.","scope_keywords":["3543","policy","registered","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4636","folder":"IETF/RFC-4636","source":"IETF/RFC-4636/RFC-4636.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3543 This document defines a Mobile IPv4 Registration Revocation mechanism\n whereby a mobility agent involved in providing Mobile IP services to\n a mobile node can notify the other mobility agent providing Mobile IP\n services to the same mobile node of the termination of this\n registration. The mechanism is also usable by a home agent to notify\n a co-located mobile node of the termination of its binding as well.\n Moreover, the mechanism provides for this notification to be\n acknowledged. A signaling mechanism already defined by the Mobile\n IPv4 protocol is leveraged as a way to inform a mobile node of the\n revocation of its binding. 3543 policy registered revocation nested-reference unchanged"},{"id":"IETF RFC 4721","type":"specification","body":"IETF","designation":"RFC 4721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4721.txt","https://www.rfc-editor.org/rfc/rfc4721.pdf"],"folder":"IETF/RFC-4721","files":{"txt":{"path":"standards/IETF/RFC-4721/RFC-4721.txt","sha256":"28968ce317ae4186b68be6a962eb3b2752005dd7d7047958562e9707106510cc"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP, as originally specified, defines an authentication\n extension (the Mobile-Foreign Authentication extension) by which a\n mobile node can authenticate itself to a foreign agent.\n Unfortunately, that extension does not provide the foreign agent any\n direct guarantee that the protocol is protected from replays and does\n not allow for the use of existing techniques (such as Challenge\n Handshake Authentication Protocol (CHAP)) for authenticating portable\n computer devices.\n\n In this specification, we define extensions for the Mobile IP Agent\n Advertisements and the Registration Request that allow a foreign\n agent to use a challenge/response mechanism to authenticate the\n mobile node.\n\n Furthermore, this document updates RFC 3344 by including a new\n authentication extension called the Mobile-Authentication,\n Authorization, and Accounting (AAA) Authentication extension. This\n new exte","scope_keywords":["4721","algorithm","authentication","authorization","credential","credentials","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 4721 Mobile IP, as originally specified, defines an authentication\n extension (the Mobile-Foreign Authentication extension) by which a\n mobile node can authenticate itself to a foreign agent.\n Unfortunately, that extension does not provide the foreign agent any\n direct guarantee that the protocol is protected from replays and does\n not allow for the use of existing techniques (such as Challenge\n Handshake Authentication Protocol (CHAP)) for authenticating portable\n computer devices.\n\n In this specification, we define extensions for the Mobile IP Agent\n Advertisements and the Registration Request that allow a foreign\n agent to use a challenge/response mechanism to authenticate the\n mobile node.\n\n Furthermore, this document updates RFC 3344 by including a new\n authentication extension called the Mobile-Authentication,\n Authorization, and Accounting (AAA) Authentication extension. This\n new exte 4721 algorithm authentication authorization credential credentials key trust nested-reference unchanged"},{"id":"IETF RFC 4857","type":"specification","body":"IETF","designation":"RFC 4857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4857.txt","https://www.rfc-editor.org/rfc/rfc4857.pdf"],"folder":"IETF/RFC-4857","files":{"txt":{"path":"standards/IETF/RFC-4857/RFC-4857.txt","sha256":"80c3bd026509215a33516028dda457de3f9e61a6668a171a3155e8c8713ac549"}},"tags":["nested-reference","unchanged"],"summary":"Using Mobile IP, a mobile node registers with its home agent each\n time it changes care-of address. This document describes a new kind\n of \"regional registrations\", i.e., registrations local to the visited\n domain. The regional registrations are performed via a new network\n entity called a Gateway Foreign Agent (GFA) and introduce a layer of\n hierarchy in the visited domain. Regional registrations reduce the\n number of signaling messages to the home network, and reduce the\n signaling delay when a mobile node moves from one foreign agent to\n another within the same visited domain. This document is an optional\n extension to the Mobile IPv4 protocol.","scope_keywords":["4857","authentication","authorization","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 4857 Using Mobile IP, a mobile node registers with its home agent each\n time it changes care-of address. This document describes a new kind\n of \"regional registrations\", i.e., registrations local to the visited\n domain. The regional registrations are performed via a new network\n entity called a Gateway Foreign Agent (GFA) and introduce a layer of\n hierarchy in the visited domain. Regional registrations reduce the\n number of signaling messages to the home network, and reduce the\n signaling delay when a mobile node moves from one foreign agent to\n another within the same visited domain. This document is an optional\n extension to the Mobile IPv4 protocol. 4857 authentication authorization trust nested-reference unchanged"},{"id":"IETF RFC 1258","type":"specification","body":"IETF","designation":"RFC 1258","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1258.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1258.txt","https://www.rfc-editor.org/rfc/rfc1258.pdf"],"folder":"IETF/RFC-1258","files":{"txt":{"path":"standards/IETF/RFC-1258/RFC-1258.txt","sha256":"513424cc614b3046f42ecd745c897b8c0f9f98f85f7bfa388c4fe66f11b15a7b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kantor\nRequest for Comments: 1258 Univ. of Calif San Diego\n September 1991\n\n BSD Rlogin\n\nStatus of this Memo\n\n This memo documents an existing protocol and common implementation\n that is extensively used on the Internet. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nProtocol Description\n\n The rlogin facility provides a remote-echoed, locally flow-controlled\n virtual terminal with proper flushing of output. It is widely used\n between Unix hosts because it provides transport of more of the Unix\n terminal environment semantics than does the Telnet protocol, and\n because on many Unix hosts it can be configured not to require user\n entry of passwords when connections originate from trusted hosts.\n\n The rlogin protocol requires the use of the TCP. The contact port is\n 513.","scope_keywords":["1258","identification","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1282","folder":"IETF/RFC-1282","source":"IETF/RFC-1282/RFC-1282.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null}],"search_text":"IETF RFC 1258 Network Working Group B. Kantor\nRequest for Comments: 1258 Univ. of Calif San Diego\n September 1991\n\n BSD Rlogin\n\nStatus of this Memo\n\n This memo documents an existing protocol and common implementation\n that is extensively used on the Internet. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nProtocol Description\n\n The rlogin facility provides a remote-echoed, locally flow-controlled\n virtual terminal with proper flushing of output. It is widely used\n between Unix hosts because it provides transport of more of the Unix\n terminal environment semantics than does the Telnet protocol, and\n because on many Unix hosts it can be configured not to require user\n entry of passwords when connections originate from trusted hosts.\n\n The rlogin protocol requires the use of the TCP. The contact port is\n 513. 1258 identification trust nested-reference unchanged"},{"id":"IETF RFC 1282","type":"specification","body":"IETF","designation":"RFC 1282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1282.txt","https://www.rfc-editor.org/rfc/rfc1282.pdf"],"folder":"IETF/RFC-1282","files":{"txt":{"path":"standards/IETF/RFC-1282/RFC-1282.txt","sha256":"34779f65e8336ae5dc2253678e06be91385b728637256f035b5f4955b7c3f7ed"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kantor\nRequest for Comments: 1282 Univ. of Calif San Diego\nObsoletes: RFC 1258 December 1991\n\n BSD Rlogin\n\nStatus of this Memo\n\n This memo documents an existing protocol and common implementation\n that is extensively used on the Internet. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nProtocol Description\n\n The rlogin facility provides a remote-echoed, locally flow-controlled\n virtual terminal with proper flushing of output [1]. It is widely\n used between Unix hosts because it provides transport of more of the\n Unix terminal environment semantics than does the Telnet protocol,\n and because on many Unix hosts it can be configured not to require\n user entry of passwords when connections originate from trusted\n hosts.\n\n The rlogin protocol requires the use of the TCP. Th","scope_keywords":["1282","identification","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1280","folder":"IETF/RFC-1280","source":"IETF/RFC-1280/RFC-1280.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null}],"search_text":"IETF RFC 1282 Network Working Group B. Kantor\nRequest for Comments: 1282 Univ. of Calif San Diego\nObsoletes: RFC 1258 December 1991\n\n BSD Rlogin\n\nStatus of this Memo\n\n This memo documents an existing protocol and common implementation\n that is extensively used on the Internet. This memo provides\n information for the Internet community. It does not specify an\n Internet standard. Distribution of this memo is unlimited.\n\nProtocol Description\n\n The rlogin facility provides a remote-echoed, locally flow-controlled\n virtual terminal with proper flushing of output [1]. It is widely\n used between Unix hosts because it provides transport of more of the\n Unix terminal environment semantics than does the Telnet protocol,\n and because on many Unix hosts it can be configured not to require\n user entry of passwords when connections originate from trusted\n hosts.\n\n The rlogin protocol requires the use of the TCP. Th 1282 identification trust nested-reference unchanged"},{"id":"IETF RFC 6709","type":"specification","body":"IETF","designation":"RFC 6709","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6709.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6709.txt","https://www.rfc-editor.org/rfc/rfc6709.pdf"],"folder":"IETF/RFC-6709","files":{"txt":{"path":"standards/IETF/RFC-6709/RFC-6709.txt","sha256":"e71fc567f381cc76d87b35aa0edf950bff69a28d1cb55ab65e7575864588a946"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses architectural issues related to the\n extensibility of Internet protocols, with a focus on design\n considerations. It is intended to assist designers of both base\n protocols and extensions. Case studies are included. A companion\n document, RFC 4775 (BCP 125), discusses procedures relating to the\n extensibility of IETF protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this ","scope_keywords":["6709","http","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 6709 This document discusses architectural issues related to the\n extensibility of Internet protocols, with a focus on design\n considerations. It is intended to assist designers of both base\n protocols and extensions. Case studies are included. A companion\n document, RFC 4775 (BCP 125), discusses procedures relating to the\n extensibility of IETF protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this  6709 http key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 2357","type":"specification","body":"IETF","designation":"RFC 2357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2357.txt","https://www.rfc-editor.org/rfc/rfc2357.pdf"],"folder":"IETF/RFC-2357","files":{"txt":{"path":"standards/IETF/RFC-2357/RFC-2357.txt","sha256":"83189258997723d333015a60214dd200efe72b96622ddd81c7ba92c46b920ea3"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the procedures and criteria for reviewing\n reliable multicast protocols within the Transport Area (TSV) of the\n IETF. Within today's Internet, important applications exist for a\n reliable multicast service. Some examples that are driving reliable\n multicast technology are collaborative workspaces (such as\n whiteboard), data and software distribution, and (more speculatively)\n web caching protocols. Due to the nature of the technical issues, a\n single commonly accepted technical solution that solves all the\n demands for reliable multicast is likely to be infeasible [RMMinutes\n 1997].\n\n A number of reliable multicast protocols have already been developed\n to solve a variety of problems for various types of applications.\n [Floyd97] describes one widely deployed example. How should these\n protocols be treated within the IETF and how should the IETF guide\n the development ","scope_keywords":["2357","delivery","driving"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3048","folder":"IETF/RFC-3048","source":"IETF/RFC-3048/RFC-3048.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 2357 This memo describes the procedures and criteria for reviewing\n reliable multicast protocols within the Transport Area (TSV) of the\n IETF. Within today's Internet, important applications exist for a\n reliable multicast service. Some examples that are driving reliable\n multicast technology are collaborative workspaces (such as\n whiteboard), data and software distribution, and (more speculatively)\n web caching protocols. Due to the nature of the technical issues, a\n single commonly accepted technical solution that solves all the\n demands for reliable multicast is likely to be infeasible [RMMinutes\n 1997].\n\n A number of reliable multicast protocols have already been developed\n to solve a variety of problems for various types of applications.\n [Floyd97] describes one widely deployed example. How should these\n protocols be treated within the IETF and how should the IETF guide\n the development  2357 delivery driving nested-reference unchanged"},{"id":"IETF RFC 4794","type":"specification","body":"IETF","designation":"RFC 4794","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4794.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4794.txt","https://www.rfc-editor.org/rfc/rfc4794.pdf"],"folder":"IETF/RFC-4794","files":{"txt":{"path":"standards/IETF/RFC-4794/RFC-4794.txt","sha256":"ae43aedccab1c638c908a4cd986cb31c8d5b718a110157c642ab5836dbd07056"}},"tags":["nested-reference","unchanged"],"summary":"RFC 1264 was written during what was effectively a completely\n different time in the life of the Internet. It prescribed rules to\n protect the Internet against new routing protocols that may have\n various undesirable properties. In today's Internet, there are so\n many other pressures against deploying unreasonable protocols that we\n believe that existing controls suffice, and the RFC 1264 rules just\n get in the way.\n\nFenner Informational [Page 1]\n\f\nRFC 4794 RFC 1264 Is Obsolete December 2006\n\n1. Introduction\n\n RFC 1264 [RFC1264] describes various rules to be applied when\n publishing routing protocols on the IETF Standards Track, including\n requirements for implementation, MIBs, security, etc. These rules\n were written in an attempt to protect the Internet from incomplete or\n unscalable new protocols.\n\n Today, one of the big problems the IETF faces is timeliness.\n Applying additional rule","scope_keywords":["4794","http","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6982","folder":"IETF/RFC-6982","source":"IETF/RFC-6982/RFC-6982.txt","version":null},{"body":"IETF","designation":"RFC 7120","folder":"IETF/RFC-7120","source":"IETF/RFC-7120/RFC-7120.txt","version":null},{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null}],"search_text":"IETF RFC 4794 RFC 1264 was written during what was effectively a completely\n different time in the life of the Internet. It prescribed rules to\n protect the Internet against new routing protocols that may have\n various undesirable properties. In today's Internet, there are so\n many other pressures against deploying unreasonable protocols that we\n believe that existing controls suffice, and the RFC 1264 rules just\n get in the way.\n\nFenner Informational [Page 1]\n\f\nRFC 4794 RFC 1264 Is Obsolete December 2006\n\n1. Introduction\n\n RFC 1264 [RFC1264] describes various rules to be applied when\n publishing routing protocols on the IETF Standards Track, including\n requirements for implementation, MIBs, security, etc. These rules\n were written in an attempt to protect the Internet from incomplete or\n unscalable new protocols.\n\n Today, one of the big problems the IETF faces is timeliness.\n Applying additional rule 4794 http license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6982","type":"specification","body":"IETF","designation":"RFC 6982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6982.txt","https://www.rfc-editor.org/rfc/rfc6982.pdf"],"folder":"IETF/RFC-6982","files":{"txt":{"path":"standards/IETF/RFC-6982/RFC-6982.txt","sha256":"ce7da2711e674422c6d7805f66982dfb2b341bdcbe4a3293aaba56a470b1c1e5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple process that allows authors of\n Internet-Drafts to record the status of known implementations by\n including an Implementation Status section. This will allow\n reviewers and working groups to assign due consideration to documents\n that have the benefit of running code, which may serve as evidence of\n valuable experimentation and feedback that have made the implemented\n protocols more mature.\n\n The process in this document is offered as an experiment. Authors of\n Internet-Drafts are encouraged to consider using the process for\n their documents, and working groups are invited to think about\n applying the process to all of their protocol specifications. The\n authors of this document intend to collate experiences with this\n experiment and to report them to the community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it ","scope_keywords":["6982","http","license","pid","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7942","folder":"IETF/RFC-7942","source":"IETF/RFC-7942/RFC-7942.txt","version":null}],"search_text":"IETF RFC 6982 This document describes a simple process that allows authors of\n Internet-Drafts to record the status of known implementations by\n including an Implementation Status section. This will allow\n reviewers and working groups to assign due consideration to documents\n that have the benefit of running code, which may serve as evidence of\n valuable experimentation and feedback that have made the implemented\n protocols more mature.\n\n The process in this document is offered as an experiment. Authors of\n Internet-Drafts are encouraged to consider using the process for\n their documents, and working groups are invited to think about\n applying the process to all of their protocol specifications. The\n authors of this document intend to collate experiences with this\n experiment and to report them to the community.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it  6982 http license pid policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7120","type":"specification","body":"IETF","designation":"RFC 7120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7120.txt","https://www.rfc-editor.org/rfc/rfc7120.pdf"],"folder":"IETF/RFC-7120","files":{"txt":{"path":"standards/IETF/RFC-7120/RFC-7120.txt","sha256":"fcf82b829af1b618d7198a00e98d9e38ecfe969d34cfa0b50303850c3e7c5083"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the process for early allocation of code points\n by IANA from registries for which \"Specification Required\", \"RFC\n Required\", \"IETF Review\", or \"Standards Action\" policies apply. This\n process can be used to alleviate the problem where code point\n allocation is needed to facilitate desired or required implementation\n and deployment experience prior to publication of an RFC, which would\n normally trigger code point allocation. The procedures in this\n document are intended to apply only to IETF Stream documents.\n\n This document obsoletes RFC 4020.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). F","scope_keywords":["7120","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null}],"search_text":"IETF RFC 7120 This memo describes the process for early allocation of code points\n by IANA from registries for which \"Specification Required\", \"RFC\n Required\", \"IETF Review\", or \"Standards Action\" policies apply. This\n process can be used to alleviate the problem where code point\n allocation is needed to facilitate desired or required implementation\n and deployment experience prior to publication of an RFC, which would\n normally trigger code point allocation. The procedures in this\n document are intended to apply only to IETF Stream documents.\n\n This document obsoletes RFC 4020.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). F 7120 http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7942","type":"specification","body":"IETF","designation":"RFC 7942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7942.txt","https://www.rfc-editor.org/rfc/rfc7942.pdf"],"folder":"IETF/RFC-7942","files":{"txt":{"path":"standards/IETF/RFC-7942/RFC-7942.txt","sha256":"2359f2b8c4dbb18da6ea9cae4515cdf05dbd7408af13212d2a44399814b53128"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple process that allows authors of\n Internet-Drafts to record the status of known implementations by\n including an Implementation Status section. This will allow\n reviewers and working groups to assign due consideration to documents\n that have the benefit of running code, which may serve as evidence of\n valuable experimentation and feedback that have made the implemented\n protocols more mature.\n\n This process is not mandatory. Authors of Internet-Drafts are\n encouraged to consider using the process for their documents, and\n working groups are invited to think about applying the process to all\n of their protocol specifications. This document obsoletes RFC 6982,\n advancing it to a Best Current Practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It ha","scope_keywords":["7942","http","license","pid","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 7942 This document describes a simple process that allows authors of\n Internet-Drafts to record the status of known implementations by\n including an Implementation Status section. This will allow\n reviewers and working groups to assign due consideration to documents\n that have the benefit of running code, which may serve as evidence of\n valuable experimentation and feedback that have made the implemented\n protocols more mature.\n\n This process is not mandatory. Authors of Internet-Drafts are\n encouraged to consider using the process for their documents, and\n working groups are invited to think about applying the process to all\n of their protocol specifications. This document obsoletes RFC 6982,\n advancing it to a Best Current Practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It ha 7942 http license pid policies subject trust nested-reference unchanged"},{"id":"IETF RFC 1786","type":"specification","body":"IETF","designation":"RFC 1786","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1786.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1786.txt","https://www.rfc-editor.org/rfc/rfc1786.pdf"],"folder":"IETF/RFC-1786","files":{"txt":{"path":"standards/IETF/RFC-1786/RFC-1786.txt","sha256":"48323dcd2ac2448b2a182ac0f80f937aee0903ffd6dd33c49b4e15acddee9f34"}},"tags":["nested-reference","unchanged"],"summary":"This document was originally published as a RIPE document known as\n ripe-181 but is also being published as an Informational RFC to reach\n a larger audience than its original scope. It has received community\n wide interest and acknowledgment throughout the Internet service\n provider community and will be used as the basic starting point for\n future work on Internet Routing Registries and routing policy\n representation. It can also be referred to as ripe-81++. This\n document is an update to the original `ripe-81'[1] proposal for\n representing and storing routing polices within the RIPE database. It\n incorporates several extensions proposed by Merit Inc.[2] and gives\n details of a generalized IP routing policy representation to be used\n by all Internet routing registries. It acts as both tutorial and\n provides details of database objects and attributes that use and make\n up a routing regis","scope_keywords":["1786","attribute","attributes","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1879","folder":"IETF/RFC-1879","source":"IETF/RFC-1879/RFC-1879.txt","version":null},{"body":"IETF","designation":"RFC 2280","folder":"IETF/RFC-2280","source":"IETF/RFC-2280/RFC-2280.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2769","folder":"IETF/RFC-2769","source":"IETF/RFC-2769/RFC-2769.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null}],"search_text":"IETF RFC 1786 This document was originally published as a RIPE document known as\n ripe-181 but is also being published as an Informational RFC to reach\n a larger audience than its original scope. It has received community\n wide interest and acknowledgment throughout the Internet service\n provider community and will be used as the basic starting point for\n future work on Internet Routing Registries and routing policy\n representation. It can also be referred to as ripe-81++. This\n document is an update to the original `ripe-81'[1] proposal for\n representing and storing routing polices within the RIPE database. It\n incorporates several extensions proposed by Merit Inc.[2] and gives\n details of a generalized IP routing policy representation to be used\n by all Internet routing registries. It acts as both tutorial and\n provides details of database objects and attributes that use and make\n up a routing regis 1786 attribute attributes policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 2439","type":"specification","body":"IETF","designation":"RFC 2439","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2439.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2439.txt","https://www.rfc-editor.org/rfc/rfc2439.pdf"],"folder":"IETF/RFC-2439","files":{"txt":{"path":"standards/IETF/RFC-2439/RFC-2439.txt","sha256":"0ada7ffbf7ff82eb215ad6f146c153d1c5fa6cc3b8c705374d52889472bbc2d6"}},"tags":["nested-reference","unchanged"],"summary":"A usage of the BGP routing protocol is described which is capable of\n reducing the routing traffic passed on to routing peers and therefore\n the load on these peers without adversely affecting route convergence\n time for relatively stable routes. This technique has been\n implemented in commercial products supporting BGP. The technique is\n also applicable to IDRP.\n\n The overall goals are:\n\n o to provide a mechanism capable of reducing router processing load\n caused by instability\n\n o in doing so prevent sustained routing oscillations\n\n o to do so without sacrificing route convergence time for generally\n well behaved routes.\n\n This must be accomplished keeping other goals of BGP in mind:\n\n o pack changes into a small number of updates\n\n o preserve consistent routing\n\nVillamizar, et. al. Standards Track [Page 1]\n\f\nRFC 2439 BGP Route Flap Damping November 1998\n\n o minimal addition space and ","scope_keywords":["2439","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 2439 A usage of the BGP routing protocol is described which is capable of\n reducing the routing traffic passed on to routing peers and therefore\n the load on these peers without adversely affecting route convergence\n time for relatively stable routes. This technique has been\n implemented in commercial products supporting BGP. The technique is\n also applicable to IDRP.\n\n The overall goals are:\n\n o to provide a mechanism capable of reducing router processing load\n caused by instability\n\n o in doing so prevent sustained routing oscillations\n\n o to do so without sacrificing route convergence time for generally\n well behaved routes.\n\n This must be accomplished keeping other goals of BGP in mind:\n\n o pack changes into a small number of updates\n\n o preserve consistent routing\n\nVillamizar, et. al. Standards Track [Page 1]\n\f\nRFC 2439 BGP Route Flap Damping November 1998\n\n o minimal addition space and  2439 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 4273","type":"specification","body":"IETF","designation":"RFC 4273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4273.txt","https://www.rfc-editor.org/rfc/rfc4273.pdf"],"folder":"IETF/RFC-4273","files":{"txt":{"path":"standards/IETF/RFC-4273/RFC-4273.txt","sha256":"37f00aaf19f391230e74d1540f0dfdd19d6eacc64e0580d8bec1a1b349a9837e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community\n In particular, it describes managed objects used for managing the\n Border Gateway Protocol Version 4 or lower.\n\n The origin of this memo is from RFC 1269 \"Definitions of Managed\n Objects for the Border Gateway Protocol (Version 3)\", which was\n updated to support BGP-4 in RFC 1657. This memo fixes errors\n introduced when the MIB module was converted to use the SMIv2\n language. This memo also updates references to the current SNMP\n framework documents.\n\n This memo is intended to document deployed implementations of this\n MIB module in a historical context, to provide clarifications of some\n items, and to note errors where the MIB module fails to fully\n represent the BGP protocol. Work is currently in progress to replace\n this MIB module with a new one r","scope_keywords":["4273","attribute","attributes","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null}],"search_text":"IETF RFC 4273 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community\n In particular, it describes managed objects used for managing the\n Border Gateway Protocol Version 4 or lower.\n\n The origin of this memo is from RFC 1269 \"Definitions of Managed\n Objects for the Border Gateway Protocol (Version 3)\", which was\n updated to support BGP-4 in RFC 1657. This memo fixes errors\n introduced when the MIB module was converted to use the SMIv2\n language. This memo also updates references to the current SNMP\n framework documents.\n\n This memo is intended to document deployed implementations of this\n MIB module in a historical context, to provide clarifications of some\n items, and to note errors where the MIB module fails to fully\n represent the BGP protocol. Work is currently in progress to replace\n this MIB module with a new one r 4273 attribute attributes management path policy nested-reference unchanged"},{"id":"IETF RFC 3430","type":"specification","body":"IETF","designation":"RFC 3430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3430.txt","https://www.rfc-editor.org/rfc/rfc3430.pdf"],"folder":"IETF/RFC-3430","files":{"txt":{"path":"standards/IETF/RFC-3430/RFC-3430.txt","sha256":"a7bfa382309cc9c856979f3170ba5693e2ff7c34cc99065a6c2a920c5dfaee87"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a transport mapping for using the Simple Network\n Management Protocol (SNMP) over TCP. The transport mapping can be\n used with any version of SNMP. This document extends the transport\n mappings defined in STD 62, RFC 3417.","scope_keywords":["3430","algorithm","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3430 This memo defines a transport mapping for using the Simple Network\n Management Protocol (SNMP) over TCP. The transport mapping can be\n used with any version of SNMP. This document extends the transport\n mappings defined in STD 62, RFC 3417. 3430 algorithm key management nested-reference unchanged"},{"id":"IETF RFC 1272","type":"specification","body":"IETF","designation":"RFC 1272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1272.txt","https://www.rfc-editor.org/rfc/rfc1272.pdf"],"folder":"IETF/RFC-1272","files":{"txt":{"path":"standards/IETF/RFC-1272/RFC-1272.txt","sha256":"7daa4312ed2e5ae176d216ccabc11004b49248270800cd3e69fb51040906d42e"}},"tags":["nested-reference","unchanged"],"summary":"This document provides background information for the \"Internet\n Accounting Architecture\" and is the first of a three document set:","scope_keywords":["1272","attribute","attributes","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1672","folder":"IETF/RFC-1672","source":"IETF/RFC-1672/RFC-1672.txt","version":null},{"body":"IETF","designation":"RFC 2063","folder":"IETF/RFC-2063","source":"IETF/RFC-2063/RFC-2063.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null}],"search_text":"IETF RFC 1272 This document provides background information for the \"Internet\n Accounting Architecture\" and is the first of a three document set: 1272 attribute attributes management policies policy nested-reference unchanged"},{"id":"IETF RFC 1672","type":"specification","body":"IETF","designation":"RFC 1672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1672.txt","https://www.rfc-editor.org/rfc/rfc1672.pdf"],"folder":"IETF/RFC-1672","files":{"txt":{"path":"standards/IETF/RFC-1672/RFC-1672.txt","sha256":"d70a9a6b94ec904273bd864ccee0f23fc049ff7209c21228f2fcbd2565004406"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Brownlee\nRequest for Comments: 1672 The University of Auckland\nCategory: Informational August 1994\n\n Accounting Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper discusses accounting requirements for IPng. It\n recommends that all IPng packets carry accounting tags, which would\n vary in size. In the simplest case a tag would simply be a voucher\n identifying the party responsible for the packet. At other times tags\n sh","scope_keywords":["1672","encryption","key","keys","management","path","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1672 Network Working Group N. Brownlee\nRequest for Comments: 1672 The University of Auckland\nCategory: Informational August 1994\n\n Accounting Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper discusses accounting requirements for IPng. It\n recommends that all IPng packets carry accounting tags, which would\n vary in size. In the simplest case a tag would simply be a voucher\n identifying the party responsible for the packet. At other times tags\n sh 1672 encryption key keys management path policy signature nested-reference unchanged"},{"id":"IETF RFC 2990","type":"specification","body":"IETF","designation":"RFC 2990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2990.txt","https://www.rfc-editor.org/rfc/rfc2990.pdf"],"folder":"IETF/RFC-2990","files":{"txt":{"path":"standards/IETF/RFC-2990/RFC-2990.txt","sha256":"371a7cbbcf0ea2ee753b646d5b4fc7587882e1432a734427dcf925f627e97685"}},"tags":["nested-reference","unchanged"],"summary":"While there has been significant progress in the definition of\n Quality of Service (QoS) architectures for internet networks, there\n are a number of aspects of QoS that appear to need further\n elaboration as they relate to translating a set of tools into a\n coherent platform for end-to-end service delivery. This document\n highlights the outstanding architectural issues relating to the\n deployment and use of QoS mechanisms within internet networks, noting\n those areas where further standards work may assist with the\n deployment of QoS internets.\n\n This document is the outcome of a collaborative exercise on the part\n of the Internet Architecture Board.","scope_keywords":["2990","delivery","management","policy","profile","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null}],"search_text":"IETF RFC 2990 While there has been significant progress in the definition of\n Quality of Service (QoS) architectures for internet networks, there\n are a number of aspects of QoS that appear to need further\n elaboration as they relate to translating a set of tools into a\n coherent platform for end-to-end service delivery. This document\n highlights the outstanding architectural issues relating to the\n deployment and use of QoS mechanisms within internet networks, noting\n those areas where further standards work may assist with the\n deployment of QoS internets.\n\n This document is the outcome of a collaborative exercise on the part\n of the Internet Architecture Board. 2990 delivery management policy profile qualified nested-reference unchanged"},{"id":"IETF RFC 1309","type":"specification","body":"IETF","designation":"RFC 1309","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1309.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1309.txt","https://www.rfc-editor.org/rfc/rfc1309.pdf"],"folder":"IETF/RFC-1309","files":{"txt":{"path":"standards/IETF/RFC-1309/RFC-1309.txt","sha256":"a7d512518fffd184793d8396dcb4b07b94b22eb0858a55053078fdc37501c5f0"}},"tags":["nested-reference","unchanged"],"summary":"This document is an overview of the X.500 standard for people not\n familiar with the technology. It compares and contrasts Directory\n Services based on X.500 with several of the other Directory services\n currently in use in the Internet. This paper also describes the\n status of the standard and provides references for further\n information on X.500 implementations and technical information.\n\n A primary purpose of this paper is to illustrate the vast\n functionality of the X.500 protocol and to show how it can be used to\n provide a global directory for human use, and can support other\n applications which would benefit from directory services, such as\n main programs.\n\n This FYI RFC is a product of the Directory Information Services\n (pilot) Infrastructure Working Group (DISI). A combined effort of\n the User Services and the OSI Integration Areas of the Internet\n Engineering Task Force (IETF)","scope_keywords":["1309"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1308","folder":"IETF/RFC-1308","source":"IETF/RFC-1308/RFC-1308.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null}],"search_text":"IETF RFC 1309 This document is an overview of the X.500 standard for people not\n familiar with the technology. It compares and contrasts Directory\n Services based on X.500 with several of the other Directory services\n currently in use in the Internet. This paper also describes the\n status of the standard and provides references for further\n information on X.500 implementations and technical information.\n\n A primary purpose of this paper is to illustrate the vast\n functionality of the X.500 protocol and to show how it can be used to\n provide a global directory for human use, and can support other\n applications which would benefit from directory services, such as\n main programs.\n\n This FYI RFC is a product of the Directory Information Services\n (pilot) Infrastructure Working Group (DISI). A combined effort of\n the User Services and the OSI Integration Areas of the Internet\n Engineering Task Force (IETF) 1309 nested-reference unchanged"},{"id":"IETF RFC 1384","type":"specification","body":"IETF","designation":"RFC 1384","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1384.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1384.txt","https://www.rfc-editor.org/rfc/rfc1384.pdf"],"folder":"IETF/RFC-1384","files":{"pdf":{"path":"standards/IETF/RFC-1384/RFC-1384.pdf","sha256":"08f3ee960f0204ecaca15af3870e670a8e68b9db19ee28b29e6c6446556d19dd"},"txt":{"path":"standards/IETF/RFC-1384/RFC-1384.txt","sha256":"8f6d993dafa646557a57c671fb50d67787a67482f9330366feb2245a8ce904b3"}},"tags":["nested-reference","unchanged"],"summary":"Deployment of a Directory will benefit from following certain\n guidelines. This document defines a number of naming guidelines.\n Alignment to these guidelines is recommended for directory pilots.\n\n1 Introduction\n\n As a pre-requisite to this document, it is assumed that the COSINE\n and Internet X.500 Schema is followed [1].\n\n2 DIT structure\n\n The majority of this document is concerned with DIT structure and\n naming for organisations, organisational units and personal entries.\n This section briefly notes three other key issues.","scope_keywords":["1384","attribute","attributes","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null}],"search_text":"IETF RFC 1384 Deployment of a Directory will benefit from following certain\n guidelines. This document defines a number of naming guidelines.\n Alignment to these guidelines is recommended for directory pilots.\n\n1 Introduction\n\n As a pre-requisite to this document, it is assumed that the COSINE\n and Internet X.500 Schema is followed [1].\n\n2 DIT structure\n\n The majority of this document is concerned with DIT structure and\n naming for organisations, organisational units and personal entries.\n This section briefly notes three other key issues. 1384 attribute attributes key registered nested-reference unchanged"},{"id":"IETF RFC 1488","type":"specification","body":"IETF","designation":"RFC 1488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1488.txt","https://www.rfc-editor.org/rfc/rfc1488.pdf"],"folder":"IETF/RFC-1488","files":{"txt":{"path":"standards/IETF/RFC-1488/RFC-1488.txt","sha256":"2e65ab626e7c495b75dd4961888728d2d5823a30e3ca77250c3a06797d8e1841"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) [9] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines the requirements that must be\n satisfied by encoding rules used to render Directory attribute\n syntaxes into a form suitable for use in the LDAP, then goes on to\n define the encoding rules for the standard set of attribute syntaxes\n defined in [1,2] and [3].\n\n1. Attribute Syntax Encoding Requirements\n\n This section defines general requirements for lightweight directory\n protocol attribute syntax encodings. All documents defining attribute\n syntax encodings for use by the lightweight directory protocols are\n expected to conform to these requirements.\n\n The encoding rules defined for a given attribute syntax must produce\n octet strings. To the greatest extent possible, encoded octet\n strings should be usable in their native ","scope_keywords":["1488","attribute","crl","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1487","folder":"IETF/RFC-1487","source":"IETF/RFC-1487/RFC-1487.txt","version":null},{"body":"IETF","designation":"RFC 1558","folder":"IETF/RFC-1558","source":"IETF/RFC-1558/RFC-1558.txt","version":null},{"body":"IETF","designation":"RFC 1777","folder":"IETF/RFC-1777","source":"IETF/RFC-1777/RFC-1777.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null}],"search_text":"IETF RFC 1488 The Lightweight Directory Access Protocol (LDAP) [9] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines the requirements that must be\n satisfied by encoding rules used to render Directory attribute\n syntaxes into a form suitable for use in the LDAP, then goes on to\n define the encoding rules for the standard set of attribute syntaxes\n defined in [1,2] and [3].\n\n1. Attribute Syntax Encoding Requirements\n\n This section defines general requirements for lightweight directory\n protocol attribute syntax encodings. All documents defining attribute\n syntax encodings for use by the lightweight directory protocols are\n expected to conform to these requirements.\n\n The encoding rules defined for a given attribute syntax must produce\n octet strings. To the greatest extent possible, encoded octet\n strings should be usable in their native  1488 attribute crl key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1778","type":"specification","body":"IETF","designation":"RFC 1778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1778.txt","https://www.rfc-editor.org/rfc/rfc1778.pdf"],"folder":"IETF/RFC-1778","files":{"txt":{"path":"standards/IETF/RFC-1778/RFC-1778.txt","sha256":"4acec0105003d6dacc3841ddbe563a203171fe2a3121d7f4cce1eff470b20a24"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) [9] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines the requirements that must be\n satisfied by encoding rules used to render X.500 Directory attribute\n syntaxes into a form suitable for use in the LDAP, then goes on to\n define the encoding rules for the standard set of attribute syntaxes\n defined in [1,2] and [3].\n\n1. Attribute Syntax Encoding Requirements.\n\n This section defines general requirements for lightweight directory\n protocol attribute syntax encodings. All documents defining attribute\n syntax encodings for use by the lightweight directory protocols are\n expected to conform to these requirements.\n\n The encoding rules defined for a given attribute syntax must produce\n octet strings. To the greatest extent possible, encoded octet\n strings should be usable in their ","scope_keywords":["1778","attribute","crl","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null},{"body":"IETF","designation":"RFC 1960","folder":"IETF/RFC-1960","source":"IETF/RFC-1960/RFC-1960.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2559","folder":"IETF/RFC-2559","source":"IETF/RFC-2559/RFC-2559.txt","version":null},{"body":"IETF","designation":"RFC 3001","folder":"IETF/RFC-3001","source":"IETF/RFC-3001/RFC-3001.txt","version":null},{"body":"IETF","designation":"RFC 3061","folder":"IETF/RFC-3061","source":"IETF/RFC-3061/RFC-3061.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null}],"search_text":"IETF RFC 1778 The Lightweight Directory Access Protocol (LDAP) [9] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines the requirements that must be\n satisfied by encoding rules used to render X.500 Directory attribute\n syntaxes into a form suitable for use in the LDAP, then goes on to\n define the encoding rules for the standard set of attribute syntaxes\n defined in [1,2] and [3].\n\n1. Attribute Syntax Encoding Requirements.\n\n This section defines general requirements for lightweight directory\n protocol attribute syntax encodings. All documents defining attribute\n syntax encodings for use by the lightweight directory protocols are\n expected to conform to these requirements.\n\n The encoding rules defined for a given attribute syntax must produce\n octet strings. To the greatest extent possible, encoded octet\n strings should be usable in their  1778 attribute crl key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1804","type":"specification","body":"IETF","designation":"RFC 1804","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1804.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1804.txt","https://www.rfc-editor.org/rfc/rfc1804.pdf"],"folder":"IETF/RFC-1804","files":{"txt":{"path":"standards/IETF/RFC-1804/RFC-1804.txt","sha256":"3fcbf707419e62f4d356d90413d32661f5f8622549c9d540b8b8da1a8954590a"}},"tags":["nested-reference","unchanged"],"summary":"The X.500 directory provides a powerful mechanism for storing and\n retrieving information about objects of interest. To interpret the\n information stored in the directory, the schema must be known to all\n the components of the directory. Presently, there are no means other\n than ftp to distribute schema information across the Internet. This\n is proving to be a severe constraint as the Directory is growing.\n This document presents a solution to the schema distribution problem\n using the existing mechanisms of the directory. A naming scheme for\n naming schema objects and a meta-schema for storing schema objects is\n presented. The procedures for fetching unknown schema from the\n directory at runtime are described.","scope_keywords":["1804","algorithm","attribute","attributes","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1804 The X.500 directory provides a powerful mechanism for storing and\n retrieving information about objects of interest. To interpret the\n information stored in the directory, the schema must be known to all\n the components of the directory. Presently, there are no means other\n than ftp to distribute schema information across the Internet. This\n is proving to be a severe constraint as the Directory is growing.\n This document presents a solution to the schema distribution problem\n using the existing mechanisms of the directory. A naming scheme for\n naming schema objects and a meta-schema for storing schema objects is\n presented. The procedures for fetching unknown schema from the\n directory at runtime are described. 1804 algorithm attribute attributes key management presentation nested-reference unchanged"},{"id":"IETF RFC 2256","type":"specification","body":"IETF","designation":"RFC 2256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2256.txt","https://www.rfc-editor.org/rfc/rfc2256.pdf"],"folder":"IETF/RFC-2256","files":{"txt":{"path":"standards/IETF/RFC-2256/RFC-2256.txt","sha256":"95967670971c7dd6ae1c26ea7a84e807f9dfcc6ab58f64da0f6492fec5de8da3"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of the attribute types and object\n classes defined by the ISO and ITU-T committees in the X.500\n documents, in particular those intended for use by directory clients.\n This is the most widely used schema for LDAP/X.500 directories, and\n many other schema definitions for white pages objects use it as a\n basis. This document does not cover attributes used for the\n administration of X.500 directory servers, nor does it include\n attributes defined by other ISO/ITU-T documents.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\n3. General Issues\n\n This document references syntaxes given in section 6 of this document\n and section 6 of [1]. Matching rules are listed in section 8 of this\n document and section 8 ","scope_keywords":["2256","algorithm","algorithms","attribute","attributes","authentication","delivery","key","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2247","folder":"IETF/RFC-2247","source":"IETF/RFC-2247/RFC-2247.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 2256 This document provides an overview of the attribute types and object\n classes defined by the ISO and ITU-T committees in the X.500\n documents, in particular those intended for use by directory clients.\n This is the most widely used schema for LDAP/X.500 directories, and\n many other schema definitions for white pages objects use it as a\n basis. This document does not cover attributes used for the\n administration of X.500 directory servers, nor does it include\n attributes defined by other ISO/ITU-T documents.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\n3. General Issues\n\n This document references syntaxes given in section 6 of this document\n and section 6 of [1]. Matching rules are listed in section 8 of this\n document and section 8  2256 algorithm algorithms attribute attributes authentication delivery key revocation nested-reference unchanged"},{"id":"IETF RFC 2798","type":"specification","body":"IETF","designation":"RFC 2798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2798.txt","https://www.rfc-editor.org/rfc/rfc2798.pdf"],"folder":"IETF/RFC-2798","files":{"txt":{"path":"standards/IETF/RFC-2798/RFC-2798.txt","sha256":"9914af5bdd50af80828a767749dc15e852161f7e4f14259018b3eb857b46967d"}},"tags":["nested-reference","unchanged"],"summary":"While the X.500 standards define many useful attribute types [X520]\n and object classes [X521], they do not define a person object class\n that meets the requirements found in today's Internet and Intranet\n directory service deployments. We define a new object class called\n inetOrgPerson for use in LDAP and X.500 directory services that\n extends the X.521 standard organizationalPerson class to meet these\n needs.\n\nSmith Informational [Page 1]\n\f\nRFC 2798 The LDAP inetOrgPerson Object Class April 2000","scope_keywords":["2798","attribute","attributes","certificate","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null}],"search_text":"IETF RFC 2798 While the X.500 standards define many useful attribute types [X520]\n and object classes [X521], they do not define a person object class\n that meets the requirements found in today's Internet and Intranet\n directory service deployments. We define a new object class called\n inetOrgPerson for use in LDAP and X.500 directory services that\n extends the X.521 standard organizationalPerson class to meet these\n needs.\n\nSmith Informational [Page 1]\n\f\nRFC 2798 The LDAP inetOrgPerson Object Class April 2000 2798 attribute attributes certificate license nested-reference unchanged"},{"id":"IETF RFC 3017","type":"specification","body":"IETF","designation":"RFC 3017","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3017.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3017.txt","https://www.rfc-editor.org/rfc/rfc3017.pdf"],"folder":"IETF/RFC-3017","files":{"txt":{"path":"standards/IETF/RFC-3017/RFC-3017.txt","sha256":"d4d678027737708adb397592a336685f60441999d8b81e1a639b6b5e41bff2d7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the syntax as well as the semantics of the\n information to be included in the phone book for roaming\n applications. It comprises the information necessary to select the\n most appropriate ISP and to configure the host to get access to the\n network of the provider. The specification consists of a small set of\n required information elements and a variety of possible extensions.\n All data is specified in XML [5] (Extensible Markup Language) syntax\n leading to a concise XML DTD (Document Type Declaration) for the\n phone book.","scope_keywords":["3017","attribute","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null}],"search_text":"IETF RFC 3017 This document defines the syntax as well as the semantics of the\n information to be included in the phone book for roaming\n applications. It comprises the information necessary to select the\n most appropriate ISP and to configure the host to get access to the\n network of the provider. The specification consists of a small set of\n required information elements and a variety of possible extensions.\n All data is specified in XML [5] (Extensible Markup Language) syntax\n leading to a concise XML DTD (Document Type Declaration) for the\n phone book. 3017 attribute delivery nested-reference unchanged"},{"id":"IETF RFC 3061","type":"specification","body":"IETF","designation":"RFC 3061","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3061.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3061.txt","https://www.rfc-editor.org/rfc/rfc3061.pdf"],"folder":"IETF/RFC-3061","files":{"txt":{"path":"standards/IETF/RFC-3061/RFC-3061.txt","sha256":"8d3203e29f00535b6b30482a8b8f235ab26da36d59007e10d65fec354f3decaf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Name (URN) namespace that\n contains Object Identifiers (OIDs). It obsoletes RFC 3001.\n\n1. Introduction\n\n An Object Identifier is a tree of nodes where each node is simply a\n sequence of digits. The rules roughly state that once an entity is\n assigned a node in the Object Identifier (OID) tree, it has sole\n discretion to further subdelegate sub-trees off of that node. Some\n examples of OIDs include:\n\n o 1.3.6.1 - the Internet OID\n o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs\n and such things\n o 1.3.6.1.2.1.27 - The Applications MIB\n o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot\n project to identify X.500 Object Classes. Mostly defined in RFC\n 1274.\n\n This document specifies the \"oid\" URN namespace [2]. This namespace\n is for encoding an Object Identifier as specified in ASN.1 [3] as a\n URI. RFC 3001 [1] ","scope_keywords":["3061","attribute","http","presentation","validation","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 522-2","folder":"ETSI/EN-319-522-2-V1.2.1","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 522-3","folder":"ETSI/EN-319-522-3-V1.2.1","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 4050","folder":"IETF/RFC-4050","source":"IETF/RFC-4050/RFC-4050.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null}],"search_text":"IETF RFC 3061 This document describes a Uniform Resource Name (URN) namespace that\n contains Object Identifiers (OIDs). It obsoletes RFC 3001.\n\n1. Introduction\n\n An Object Identifier is a tree of nodes where each node is simply a\n sequence of digits. The rules roughly state that once an entity is\n assigned a node in the Object Identifier (OID) tree, it has sole\n discretion to further subdelegate sub-trees off of that node. Some\n examples of OIDs include:\n\n o 1.3.6.1 - the Internet OID\n o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs\n and such things\n o 1.3.6.1.2.1.27 - The Applications MIB\n o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot\n project to identify X.500 Object Classes. Mostly defined in RFC\n 1274.\n\n This document specifies the \"oid\" URN namespace [2]. This namespace\n is for encoding an Object Identifier as specified in ASN.1 [3] as a\n URI. RFC 3001 [1]  3061 attribute http presentation validation verifiable nested-reference unchanged"},{"id":"IETF RFC 4517","type":"specification","body":"IETF","designation":"RFC 4517","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4517.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4517.txt","https://www.rfc-editor.org/rfc/rfc4517.pdf"],"folder":"IETF/RFC-4517","files":{"txt":{"path":"standards/IETF/RFC-4517/RFC-4517.txt","sha256":"326d546ce6af5571015f7eb4deedfe0f438f211e0d540580b4dfeacdea20d327"}},"tags":["nested-reference","unchanged"],"summary":"Each attribute stored in a Lightweight Directory Access Protocol\n (LDAP) directory, whose values may be transferred in the LDAP\n protocol, has a defined syntax that constrains the structure and\n format of its values. The comparison semantics for values of a\n syntax are not part of the syntax definition but are instead provided\n through separately defined matching rules. Matching rules specify an\n argument, an assertion value, which also has a defined syntax. This\n document defines a base set of syntaxes and matching rules for use in\n defining attributes for LDAP directories.","scope_keywords":["4517","attribute","attributes","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 4517 Each attribute stored in a Lightweight Directory Access Protocol\n (LDAP) directory, whose values may be transferred in the LDAP\n protocol, has a defined syntax that constrains the structure and\n format of its values. The comparison semantics for values of a\n syntax are not part of the syntax definition but are instead provided\n through separately defined matching rules. Matching rules specify an\n argument, an assertion value, which also has a defined syntax. This\n document defines a base set of syntaxes and matching rules for use in\n defining attributes for LDAP directories. 4517 attribute attributes delivery key nested-reference unchanged"},{"id":"IETF RFC 1276","type":"specification","body":"IETF","designation":"RFC 1276","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1276.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1276.txt","https://www.rfc-editor.org/rfc/rfc1276.pdf"],"folder":"IETF/RFC-1276","files":{"txt":{"path":"standards/IETF/RFC-1276/RFC-1276.txt","sha256":"bb574dc1107f8b5d43b21ce1157f7fbe26dc44189ff3e3dbc7a7ed5395e1a563"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1276 University College London\n November 1991\n\n Replication and Distributed Operations extensions\n to provide an Internet Directory using X.500\n\nStatus of this Memo\n This RFC specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the ``IAB\n Official Protocol Standards'' for the standardization state and\n status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n Some requirements on extensions to X.500 are described in the\n RFC[HK91b], in order to build an Internet Directory using\n X.500(1988). This document specifies a set of solutions to the\n problems raised. These solutions are based on some work done for\n the QUIPU implementation, and demonstrated to be effective in a\n number of directory p","scope_keywords":["1276","attribute","attributes","pid","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 2120","folder":"IETF/RFC-2120","source":"IETF/RFC-2120/RFC-2120.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1276 Network Working Group S.E. Hardcastle-Kille\nRequests for Comments 1276 University College London\n November 1991\n\n Replication and Distributed Operations extensions\n to provide an Internet Directory using X.500\n\nStatus of this Memo\n This RFC specifies an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the ``IAB\n Official Protocol Standards'' for the standardization state and\n status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n Some requirements on extensions to X.500 are described in the\n RFC[HK91b], in order to build an Internet Directory using\n X.500(1988). This document specifies a set of solutions to the\n problems raised. These solutions are based on some work done for\n the QUIPU implementation, and demonstrated to be effective in a\n number of directory p 1276 attribute attributes pid policy presentation nested-reference unchanged"},{"id":"IETF RFC 2120","type":"specification","body":"IETF","designation":"RFC 2120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2120.txt","https://www.rfc-editor.org/rfc/rfc2120.pdf"],"folder":"IETF/RFC-2120","files":{"txt":{"path":"standards/IETF/RFC-2120/RFC-2120.txt","sha256":"ce1b87a171a05c5471008277cd474d3701f6ed77e8df0be38c144059ae551613"}},"tags":["nested-reference","unchanged"],"summary":"The X.500 Standard [X.500 93] has the concept of first level DSAs,\n whose administrators must collectively manage the root naming context\n through bi-lateral agreements or other private means which are\n outside the scope of the X.500 Standard.\n\n The NameFLOW-Paradise X.500 service has an established procedure for\n managing the root naming context, which currently uses Quipu\n proprietary replication mechanisms and a root DSA. The benefits that\n derive from this are twofold:\n\n - firstly it is much easier to co-ordinate the management of the\n root context information, when there is a central point of\n administration,\n\n - secondly the performance of one-level Search operations is\n greatly improved because the Quipu distribution and replication\n mechanism does not have a restriction that exists in the 1988 and\n 1993 X.500 Standard.\n\n The NameFLOW-Paradise project is moving towards 1993 ISO X.","scope_keywords":["2120","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2120 The X.500 Standard [X.500 93] has the concept of first level DSAs,\n whose administrators must collectively manage the root naming context\n through bi-lateral agreements or other private means which are\n outside the scope of the X.500 Standard.\n\n The NameFLOW-Paradise X.500 service has an established procedure for\n managing the root naming context, which currently uses Quipu\n proprietary replication mechanisms and a root DSA. The benefits that\n derive from this are twofold:\n\n - firstly it is much easier to co-ordinate the management of the\n root context information, when there is a central point of\n administration,\n\n - secondly the performance of one-level Search operations is\n greatly improved because the Quipu distribution and replication\n mechanism does not have a restriction that exists in the 1988 and\n 1993 X.500 Standard.\n\n The NameFLOW-Paradise project is moving towards 1993 ISO X. 2120 management subject nested-reference unchanged"},{"id":"IETF RFC 2252","type":"specification","body":"IETF","designation":"RFC 2252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2252.txt","https://www.rfc-editor.org/rfc/rfc2252.pdf"],"folder":"IETF/RFC-2252","files":{"txt":{"path":"standards/IETF/RFC-2252/RFC-2252.txt","sha256":"52d9b58a6d5be1beed328e6dc8aa111b287407bb53420462f6dffd152cd3132c"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) [1] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines a set of syntaxes for LDAPv3, and the\n rules by which attribute values of these syntaxes are represented as\n octet strings for transmission in the LDAP protocol. The syntaxes\n defined in this document are referenced by this and other documents\n that define attribute types. This document also defines the set of\n attribute types which LDAP servers should support.\n\n3. Overview\n\n This document defines the framework for developing schemas for\n directories accessible via the Lightweight Directory Access Protocol.\n\n Schema is the collection of attribute type definitions, object class\n definitions and other information which a server uses to determine\n how to match a filter or attribute value assertion (in a compare\n operation) ag","scope_keywords":["2252","attribute","attributes","authentication","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2589","folder":"IETF/RFC-2589","source":"IETF/RFC-2589/RFC-2589.txt","version":null},{"body":"IETF","designation":"RFC 2596","folder":"IETF/RFC-2596","source":"IETF/RFC-2596/RFC-2596.txt","version":null},{"body":"IETF","designation":"RFC 2657","folder":"IETF/RFC-2657","source":"IETF/RFC-2657/RFC-2657.txt","version":null},{"body":"IETF","designation":"RFC 2739","folder":"IETF/RFC-2739","source":"IETF/RFC-2739/RFC-2739.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2927","folder":"IETF/RFC-2927","source":"IETF/RFC-2927/RFC-2927.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3674","folder":"IETF/RFC-3674","source":"IETF/RFC-3674/RFC-3674.txt","version":null},{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3771","folder":"IETF/RFC-3771","source":"IETF/RFC-3771/RFC-3771.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 2252 The Lightweight Directory Access Protocol (LDAP) [1] requires that\n the contents of AttributeValue fields in protocol elements be octet\n strings. This document defines a set of syntaxes for LDAPv3, and the\n rules by which attribute values of these syntaxes are represented as\n octet strings for transmission in the LDAP protocol. The syntaxes\n defined in this document are referenced by this and other documents\n that define attribute types. This document also defines the set of\n attribute types which LDAP servers should support.\n\n3. Overview\n\n This document defines the framework for developing schemas for\n directories accessible via the Lightweight Directory Access Protocol.\n\n Schema is the collection of attribute type definitions, object class\n definitions and other information which a server uses to determine\n how to match a filter or attribute value assertion (in a compare\n operation) ag 2252 attribute attributes authentication key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1838","type":"specification","body":"IETF","designation":"RFC 1838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1838.txt","https://www.rfc-editor.org/rfc/rfc1838.pdf"],"folder":"IETF/RFC-1838","files":{"txt":{"path":"standards/IETF/RFC-1838/RFC-1838.txt","sha256":"e9f57e8de2de0bb6e309657905f11cf935f65fa859ab0ac9febe2dcb08dea5b0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 1838 ISODE Consortium\nCategory: Experimental August 1995\n\n Use of the X.500 Directory to support mapping between X.400\n and RFC 822 Addresses\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines how to use directory to support the mapping\n between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2].\n\n1. X.400/RFC 822 Mappings\n\n RFC 1327 defines an algorithm for maintaining a global mapping\n between X.400 and RFC 822 addresses directory [2]. RFC 1327 also\n defines a table based mechanism for maintaining this mapping. There\n is substantial benefit to maintaining this mapping within the\n directory. I","scope_keywords":["1838","algorithm","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null}],"search_text":"IETF RFC 1838 Network Working Group S. Kille\nRequest for Comments: 1838 ISODE Consortium\nCategory: Experimental August 1995\n\n Use of the X.500 Directory to support mapping between X.400\n and RFC 822 Addresses\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines how to use directory to support the mapping\n between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2].\n\n1. X.400/RFC 822 Mappings\n\n RFC 1327 defines an algorithm for maintaining a global mapping\n between X.400 and RFC 822 addresses directory [2]. RFC 1327 also\n defines a table based mechanism for maintaining this mapping. There\n is substantial benefit to maintaining this mapping within the\n directory. I 1838 algorithm attribute key nested-reference unchanged"},{"id":"IETF RFC 2164","type":"specification","body":"IETF","designation":"RFC 2164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2164.txt","https://www.rfc-editor.org/rfc/rfc2164.pdf"],"folder":"IETF/RFC-2164","files":{"txt":{"path":"standards/IETF/RFC-2164/RFC-2164.txt","sha256":"5b50d5a912709f012d55e1b5564e28369c4f735d564c2a257db599c3377bb040"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 2164 Isode Ltd.\nObsoletes: 1838 January 1998\nCategory: Standards Track\n\n Use of an X.500/LDAP directory to support MIXER address mapping\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1 MIXER X.400/RFC 822 Mappings\n\n MIXER (RFC 2156) defines an algorithm for use of a set of global\n mapping between X.400 and RFC 822 addresses [4]. This specification\n defines how to represent and maintain these mappings (MIXER\n Conformant Global Address Mapping","scope_keywords":["2164","algorithm","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2164 Network Working Group S. Kille\nRequest for Comments: 2164 Isode Ltd.\nObsoletes: 1838 January 1998\nCategory: Standards Track\n\n Use of an X.500/LDAP directory to support MIXER address mapping\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1 MIXER X.400/RFC 822 Mappings\n\n MIXER (RFC 2156) defines an algorithm for use of a set of global\n mapping between X.400 and RFC 822 addresses [4]. This specification\n defines how to represent and maintain these mappings (MIXER\n Conformant Global Address Mapping 2164 algorithm attribute key nested-reference unchanged"},{"id":"IETF RFC 1335","type":"specification","body":"IETF","designation":"RFC 1335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1335.txt","https://www.rfc-editor.org/rfc/rfc1335.pdf"],"folder":"IETF/RFC-1335","files":{"txt":{"path":"standards/IETF/RFC-1335/RFC-1335.txt","sha256":"0499a2891a000e03a06c4d21b1657895d2487ee9f26d524d6a8e84422c686773"}},"tags":["nested-reference","unchanged"],"summary":"This RFC presents a solution to problem of address space exhaustion\n in the Internet. It proposes a two-tier address structure for the\n Internet. This is an \"idea\" paper and discussion is strongly\n encouraged.","scope_keywords":["1335","algorithm","algorithms","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1366","folder":"IETF/RFC-1366","source":"IETF/RFC-1366/RFC-1366.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1466","folder":"IETF/RFC-1466","source":"IETF/RFC-1466/RFC-1466.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null}],"search_text":"IETF RFC 1335 This RFC presents a solution to problem of address space exhaustion\n in the Internet. It proposes a two-tier address structure for the\n Internet. This is an \"idea\" paper and discussion is strongly\n encouraged. 1335 algorithm algorithms pid nested-reference unchanged"},{"id":"IETF RFC 1475","type":"specification","body":"IETF","designation":"RFC 1475","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1475.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1475.txt","https://www.rfc-editor.org/rfc/rfc1475.pdf"],"folder":"IETF/RFC-1475","files":{"txt":{"path":"standards/IETF/RFC-1475/RFC-1475.txt","sha256":"26191d5169ff24349fa367e98b1a95de3ff5375fb47c3223b3663b7406a78573"}},"tags":["nested-reference","unchanged"],"summary":"The first version of this memo, describing a possible next generation\n of Internet protocols, was written by the present author in the\n summer and fall of 1989, and circulated informally, including to the\n IESG, in December 1989. A further informal note on the addressing,\n called \"Toasternet Part II\", was circulated on the IETF mail list\n during March of 1992.","scope_keywords":["1475"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1475 The first version of this memo, describing a possible next generation\n of Internet protocols, was written by the present author in the\n summer and fall of 1989, and circulated informally, including to the\n IESG, in December 1989. A further informal note on the addressing,\n called \"Toasternet Part II\", was circulated on the IETF mail list\n during March of 1992. 1475 nested-reference unchanged"},{"id":"IETF RFC 1560","type":"specification","body":"IETF","designation":"RFC 1560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1560.txt","https://www.rfc-editor.org/rfc/rfc1560.pdf"],"folder":"IETF/RFC-1560","files":{"txt":{"path":"standards/IETF/RFC-1560/RFC-1560.txt","sha256":"3c1ae24bb660dbcb5cc3f63d8c5fe96f5c374cb9e6567e42add1fcba51dbb64f"}},"tags":["nested-reference","unchanged"],"summary":"This document was prepared by the authors on behalf of the Internet\n Architecture Board (IAB). It is offered by the IAB to stimulate\n discussion.\n\n There has recently been considerable discussion on two topics:\n MultiProtocol approaches in the Internet and the selection of a next\n generation Internet Protocol. This document suggests a strawman\n position for goals and approaches for the IETF/IESG/IAB in these\n areas. It takes the view that these two topics are related, and\n proposes directions for the IETF/IESG/IAB to pursue.\n\n In particular, it recommends that the IETF/IESG/IAB should continue\n to be a force for consensus on a single protocol suite and internet\n layer protocol. The IETF/IESG/IAB should:\n\n - maintain its focus on the TCP/IP protocol suite,\n\n - work to select a single next-generation internet protocol and\n develop mechanisms to aid in transition from the current IPv4,\n and","scope_keywords":["1560","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1560 This document was prepared by the authors on behalf of the Internet\n Architecture Board (IAB). It is offered by the IAB to stimulate\n discussion.\n\n There has recently been considerable discussion on two topics:\n MultiProtocol approaches in the Internet and the selection of a next\n generation Internet Protocol. This document suggests a strawman\n position for goals and approaches for the IETF/IESG/IAB in these\n areas. It takes the view that these two topics are related, and\n proposes directions for the IETF/IESG/IAB to pursue.\n\n In particular, it recommends that the IETF/IESG/IAB should continue\n to be a force for consensus on a single protocol suite and internet\n layer protocol. The IETF/IESG/IAB should:\n\n - maintain its focus on the TCP/IP protocol suite,\n\n - work to select a single next-generation internet protocol and\n develop mechanisms to aid in transition from the current IPv4,\n and 1560 pid nested-reference unchanged"},{"id":"IETF RFC 1726","type":"specification","body":"IETF","designation":"RFC 1726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1726.txt","https://www.rfc-editor.org/rfc/rfc1726.pdf"],"folder":"IETF/RFC-1726","files":{"txt":{"path":"standards/IETF/RFC-1726/RFC-1726.txt","sha256":"b15c99ef715ba9d0d5bd6da6712eacbb9fae581e677b058fa6373ee6794df7fc"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP.","scope_keywords":["1726","algorithm","algorithms","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1810","folder":"IETF/RFC-1810","source":"IETF/RFC-1810/RFC-1810.txt","version":null}],"search_text":"IETF RFC 1726 This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP. 1726 algorithm algorithms management policy nested-reference unchanged"},{"id":"IETF RFC 3221","type":"specification","body":"IETF","designation":"RFC 3221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3221.txt","https://www.rfc-editor.org/rfc/rfc3221.pdf"],"folder":"IETF/RFC-3221","files":{"txt":{"path":"standards/IETF/RFC-3221/RFC-3221.txt","sha256":"38ae092a34ded40608bd9fcade53eb61b9f85ceea8b8e13042e787661d8792a4"}},"tags":["nested-reference","unchanged"],"summary":"This document examines the various longer term trends visible within\n the characteristics of the Internet's BGP table and identifies a\n number of operational practices and protocol factors that contribute\n to these trends. The potential impacts of these practices and\n protocol properties on the scaling properties of the inter-domain\n routing space are examined.\n\n This document is the outcome of a collaborative exercise on the part\n of the Internet Architecture Board.","scope_keywords":["3221","attribute","attributes","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3765","folder":"IETF/RFC-3765","source":"IETF/RFC-3765/RFC-3765.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 3221 This document examines the various longer term trends visible within\n the characteristics of the Internet's BGP table and identifies a\n number of operational practices and protocol factors that contribute\n to these trends. The potential impacts of these practices and\n protocol properties on the scaling properties of the inter-domain\n routing space are examined.\n\n This document is the outcome of a collaborative exercise on the part\n of the Internet Architecture Board. 3221 attribute attributes management path policies policy nested-reference unchanged"},{"id":"IETF RFC 2458","type":"specification","body":"IETF","designation":"RFC 2458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2458.txt","https://www.rfc-editor.org/rfc/rfc2458.pdf"],"folder":"IETF/RFC-2458","files":{"txt":{"path":"standards/IETF/RFC-2458/RFC-2458.txt","sha256":"800935e2f0aea47d16a85505b683f4957863b6eae9e86822e9136172b13ecd7f"}},"tags":["nested-reference","unchanged"],"summary":"This document contains the information relevant to the development of\n the inter-networking interfaces underway in the Public Switched\n Telephone Network (PSTN)/Internet Inter-Networking (PINT) Working\n Group. It addresses technologies, architectures, and several (but by\n no means all) existing pre-PINT implementations of the arrangements\n through which Internet applications can request and enrich PSTN\n telecommunications services. The common denominator of the enriched\n services (a.k.a. PINT services) is that they combine the Internet and\n PSTN services in such a way that the Internet is used for non-voice\n interactions, while the voice (and fax) are carried entirely over the\n PSTN. One key observation is that the pre-PINT implementations, being\n developed independently, do not inter-operate. It is a task of the\n PINT Working Group to define the inter-networking interfaces that\n\nLu, et.","scope_keywords":["2458","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2458 This document contains the information relevant to the development of\n the inter-networking interfaces underway in the Public Switched\n Telephone Network (PSTN)/Internet Inter-Networking (PINT) Working\n Group. It addresses technologies, architectures, and several (but by\n no means all) existing pre-PINT implementations of the arrangements\n through which Internet applications can request and enrich PSTN\n telecommunications services. The common denominator of the enriched\n services (a.k.a. PINT services) is that they combine the Internet and\n PSTN services in such a way that the Internet is used for non-voice\n interactions, while the voice (and fax) are carried entirely over the\n PSTN. One key observation is that the pre-PINT implementations, being\n developed independently, do not inter-operate. It is a task of the\n PINT Working Group to define the inter-networking interfaces that\n\nLu, et. 2458 key nested-reference unchanged"},{"id":"IETF RFC 1308","type":"specification","body":"IETF","designation":"RFC 1308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1308.txt","https://www.rfc-editor.org/rfc/rfc1308.pdf"],"folder":"IETF/RFC-1308","files":{"txt":{"path":"standards/IETF/RFC-1308/RFC-1308.txt","sha256":"6b958236272d08a43de486e5c9c291abd0a4265e8d60b99cf7aa510331d1c50f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Weider\nRequest for Comments: 1308 ANS\nFYI: 13 J. Reynolds\n ISI\n March 1992\n\n Executive Introduction to Directory Services\n Using the X.500 Protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document is an Executive Introduction to Directory Services\n using the X.500 protocol. It briefly discusses the deficiencies in\n currently deployed Internet Directory Services, and then illustrates\n the solutions provided by X.500.\n\n This FYI RFC is a product of the Directory Information Services\n (pilot) Infrastructure Working Group (DISI). A combined effort of\n the User Services and the OSI Integration Areas of the Internet\n Engineering Task Force (IETF).\n\n1. INTRODUCTION\n\n The Internet is growing at a phenomenal rate, with no decelerat","scope_keywords":["1308","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1309","folder":"IETF/RFC-1309","source":"IETF/RFC-1309/RFC-1309.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null}],"search_text":"IETF RFC 1308 Network Working Group C. Weider\nRequest for Comments: 1308 ANS\nFYI: 13 J. Reynolds\n ISI\n March 1992\n\n Executive Introduction to Directory Services\n Using the X.500 Protocol\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document is an Executive Introduction to Directory Services\n using the X.500 protocol. It briefly discusses the deficiencies in\n currently deployed Internet Directory Services, and then illustrates\n the solutions provided by X.500.\n\n This FYI RFC is a product of the Directory Information Services\n (pilot) Infrastructure Working Group (DISI). A combined effort of\n the User Services and the OSI Integration Areas of the Internet\n Engineering Task Force (IETF).\n\n1. INTRODUCTION\n\n The Internet is growing at a phenomenal rate, with no decelerat 1308 registered nested-reference unchanged"},{"id":"IETF RFC 1293","type":"specification","body":"IETF","designation":"RFC 1293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1293.txt","https://www.rfc-editor.org/rfc/rfc1293.pdf"],"folder":"IETF/RFC-1293","files":{"txt":{"path":"standards/IETF/RFC-1293/RFC-1293.txt","sha256":"6b534d88dbab994fc5c93d3bfee1b1e02d599e72a45b820a6ba674f941b7aa15"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes additions to ARP that will allow a station to\n request a protocol address corresponding to a given hardware address.\n Specifically, this applies to Frame Relay stations that may have a\n Data Link Connection Identifier (DLCI), the Frame Relay equivalent of\n a hardware address, associated with an established Permanent Virtual\n Circuit (PVC), but do not know the protocol address of the station on\n the other side of this connection. It will also apply to other\n networks with similar circumstances.\n\n3. Conventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o Must, Will, Shall or Mandatory -- the item is an absolute\n requirement of the specification.\n\n o Should or Recommended -- the item should generally be\n followed for all but exceptional circumstances.\n\n o May or Optional -- the item is truly optional and may be\n foll","scope_keywords":["1293"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1586","folder":"IETF/RFC-1586","source":"IETF/RFC-1586/RFC-1586.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null}],"search_text":"IETF RFC 1293 This memo describes additions to ARP that will allow a station to\n request a protocol address corresponding to a given hardware address.\n Specifically, this applies to Frame Relay stations that may have a\n Data Link Connection Identifier (DLCI), the Frame Relay equivalent of\n a hardware address, associated with an established Permanent Virtual\n Circuit (PVC), but do not know the protocol address of the station on\n the other side of this connection. It will also apply to other\n networks with similar circumstances.\n\n3. Conventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o Must, Will, Shall or Mandatory -- the item is an absolute\n requirement of the specification.\n\n o Should or Recommended -- the item should generally be\n followed for all but exceptional circumstances.\n\n o May or Optional -- the item is truly optional and may be\n foll 1293 nested-reference unchanged"},{"id":"IETF RFC 2390","type":"specification","body":"IETF","designation":"RFC 2390","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2390.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2390.txt","https://www.rfc-editor.org/rfc/rfc2390.pdf"],"folder":"IETF/RFC-2390","files":{"txt":{"path":"standards/IETF/RFC-2390/RFC-2390.txt","sha256":"a21992b07a96ae0bba437f466d5378ac707c245379c1b8e6a616cf1e841bee9b"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes additions to ARP that will allow a station to\n request a protocol address corresponding to a given hardware address.\n Specifically, this applies to Frame Relay stations that may have a\n Data Link Connection Identifier (DLCI), the Frame Relay equivalent of\n a hardware address, associated with an established Permanent Virtual\n Circuit (PVC), but do not know the protocol address of the station on\n the other side of this connection. It will also apply to other\n networks with similar circumstances.\n\n This memo replaces RFC 1293. The changes from RFC 1293 are minor\n changes to formalize the language, the additions of a packet diagram\n and an example in section 7.2, and a new security section.\n\n3. Conventions\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interprete","scope_keywords":["2390","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2390 This memo describes additions to ARP that will allow a station to\n request a protocol address corresponding to a given hardware address.\n Specifically, this applies to Frame Relay stations that may have a\n Data Link Connection Identifier (DLCI), the Frame Relay equivalent of\n a hardware address, associated with an established Permanent Virtual\n Circuit (PVC), but do not know the protocol address of the station on\n the other side of this connection. It will also apply to other\n networks with similar circumstances.\n\n This memo replaces RFC 1293. The changes from RFC 1293 are minor\n changes to formalize the language, the additions of a packet diagram\n and an example in section 7.2, and a new security section.\n\n3. Conventions\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interprete 2390 key nested-reference unchanged"},{"id":"IETF RFC 1362","type":"specification","body":"IETF","designation":"RFC 1362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1362.txt","https://www.rfc-editor.org/rfc/rfc1362.pdf"],"folder":"IETF/RFC-1362","files":{"txt":{"path":"standards/IETF/RFC-1362/RFC-1362.txt","sha256":"bf805e8874087d4e01c60c17b7acffeca3edf9021d905d29cae4537bc35334a1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how Novell IPX operates over various WAN\n media. Specifically, it describes the common \"IPX WAN\" protocol\n Novell uses to exchange necessary router to router information prior\n to exchanging standard IPX routing information and traffic over WAN\n datalinks.","scope_keywords":["1362","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null}],"search_text":"IETF RFC 1362 This document describes how Novell IPX operates over various WAN\n media. Specifically, it describes the common \"IPX WAN\" protocol\n Novell uses to exchange necessary router to router information prior\n to exchanging standard IPX routing information and traffic over WAN\n datalinks. 1362 identification management nested-reference unchanged"},{"id":"IETF RFC 1295","type":"specification","body":"IETF","designation":"RFC 1295","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1295.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1295.txt","https://www.rfc-editor.org/rfc/rfc1295.pdf"],"folder":"IETF/RFC-1295","files":{"txt":{"path":"standards/IETF/RFC-1295/RFC-1295.txt","sha256":"17e1d71828d2c9d8a2d99e65e8fe4342a9291712cd4ba1d6df7f6aeec3f9b535"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group The North American Directory Forum\nRequest for Comments: 1295 January 1992\n\n User Bill of Rights\n for entries and listings\n in the Public Directory\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This RFC is a near-verbatim copy of a document, known as NADF-265,\n which has been produced by the North American Directory Forum (NADF).\n\n User Bill of Rights\n for entries and listings\n in the Public Directory\n\n The mission of the North American Directory Forum is to provide\n interconnected electronic directories which empower users with\n unprecedented access to public information. To address significant\n security and privacy issues, the North American Directory Forum\n introduces the following \"User Bill of Rights\" for entries in the\n Public Dir","scope_keywords":["1295"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1355","folder":"IETF/RFC-1355","source":"IETF/RFC-1355/RFC-1355.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null}],"search_text":"IETF RFC 1295 Network Working Group The North American Directory Forum\nRequest for Comments: 1295 January 1992\n\n User Bill of Rights\n for entries and listings\n in the Public Directory\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This RFC is a near-verbatim copy of a document, known as NADF-265,\n which has been produced by the North American Directory Forum (NADF).\n\n User Bill of Rights\n for entries and listings\n in the Public Directory\n\n The mission of the North American Directory Forum is to provide\n interconnected electronic directories which empower users with\n unprecedented access to public information. To address significant\n security and privacy issues, the North American Directory Forum\n introduces the following \"User Bill of Rights\" for entries in the\n Public Dir 1295 nested-reference unchanged"},{"id":"IETF RFC 1355","type":"specification","body":"IETF","designation":"RFC 1355","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1355.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1355.txt","https://www.rfc-editor.org/rfc/rfc1355.pdf"],"folder":"IETF/RFC-1355","files":{"txt":{"path":"standards/IETF/RFC-1355/RFC-1355.txt","sha256":"3c7f9657f483fe7ede6af7f31ab4561f59615f0c15b2d99af17b86964c6a0ea1"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to consider the privacy and accuracy\n issues that result from many NIC databases being publicly accessible.\n This document considers only generic concerns about such systems; it\n intentionally does not make recommendations for specific databases on\n the Internet. Clearly, it is the responsibility of each NIC to\n determine what procedures should apply for each of its databases.\n The document discusses the obligations a NIC that maintains such a","scope_keywords":["1355","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null}],"search_text":"IETF RFC 1355 The purpose of this document is to consider the privacy and accuracy\n issues that result from many NIC databases being publicly accessible.\n This document considers only generic concerns about such systems; it\n intentionally does not make recommendations for specific databases on\n the Internet. Clearly, it is the responsibility of each NIC to\n determine what procedures should apply for each of its databases.\n The document discusses the obligations a NIC that maintains such a 1355 policy risk nested-reference unchanged"},{"id":"IETF RFC 1305","type":"specification","body":"IETF","designation":"RFC 1305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1305.txt","https://www.rfc-editor.org/rfc/rfc1305.pdf"],"folder":"IETF/RFC-1305","files":{"pdf":{"path":"standards/IETF/RFC-1305/RFC-1305.pdf","sha256":"528e279c741ae6f2c78ee0e1ed9586a5cdb6a55db269a94f4b7546982eefd3c2"},"txt":{"path":"standards/IETF/RFC-1305/RFC-1305.txt","sha256":"60988c658f503f664cd1238febbd4629dd7bfc574567ebb940b75a59f5848119"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Network Time Protocol (NTP), specifies its\nformal structure and summarizes information useful for its\nimplementation. NTP provides the mechanisms to synchronize time and\ncoordinate time distribution in a large, diverse internet operating at\nrates from mundane to lightwave. It uses a returnable-time design in\nwhich a distributed subnet of time servers operating in a self-\norganizing, hierarchical-master-slave configuration synchronizes local\nclocks within the subnet and to national time standards via wire or\nradio. The servers can also redistribute reference time via local\nrouting algorithms and time daemons.\n\nStatus of this Memo\n\nThis RFC specifies an IAB standards track protocol for the Internet\ncommunity and requests discussion and suggestions for improvements.\nPlease refer to the current edition of the <169>IAB Official Protocol\nStandards<170> for the stand","scope_keywords":["1305","algorithm","algorithms","authentication","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1610","folder":"IETF/RFC-1610","source":"IETF/RFC-1610/RFC-1610.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1720","folder":"IETF/RFC-1720","source":"IETF/RFC-1720/RFC-1720.txt","version":null},{"body":"IETF","designation":"RFC 1769","folder":"IETF/RFC-1769","source":"IETF/RFC-1769/RFC-1769.txt","version":null},{"body":"IETF","designation":"RFC 1780","folder":"IETF/RFC-1780","source":"IETF/RFC-1780/RFC-1780.txt","version":null},{"body":"IETF","designation":"RFC 1800","folder":"IETF/RFC-1800","source":"IETF/RFC-1800/RFC-1800.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2330","folder":"IETF/RFC-2330","source":"IETF/RFC-2330/RFC-2330.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2980","folder":"IETF/RFC-2980","source":"IETF/RFC-2980/RFC-2980.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4082","folder":"IETF/RFC-4082","source":"IETF/RFC-4082/RFC-4082.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null}],"search_text":"IETF RFC 1305 This document describes the Network Time Protocol (NTP), specifies its\nformal structure and summarizes information useful for its\nimplementation. NTP provides the mechanisms to synchronize time and\ncoordinate time distribution in a large, diverse internet operating at\nrates from mundane to lightwave. It uses a returnable-time design in\nwhich a distributed subnet of time servers operating in a self-\norganizing, hierarchical-master-slave configuration synchronizes local\nclocks within the subnet and to national time standards via wire or\nradio. The servers can also redistribute reference time via local\nrouting algorithms and time daemons.\n\nStatus of this Memo\n\nThis RFC specifies an IAB standards track protocol for the Internet\ncommunity and requests discussion and suggestions for improvements.\nPlease refer to the current edition of the <169>IAB Official Protocol\nStandards<170> for the stand 1305 algorithm algorithms authentication key path nested-reference unchanged"},{"id":"IETF RFC 2324","type":"specification","body":"IETF","designation":"RFC 2324","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2324.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2324.txt","https://www.rfc-editor.org/rfc/rfc2324.pdf"],"folder":"IETF/RFC-2324","files":{"txt":{"path":"standards/IETF/RFC-2324/RFC-2324.txt","sha256":"b11329c3fd6dbe9dddcb8dd90f18a4bf441858a6b5bfaccae5f91e5c7d2b3596"}},"tags":["nested-reference","unchanged"],"summary":"This document describes HTCPCP, a protocol for controlling,\n monitoring, and diagnosing coffee pots.\n\n1. Rationale and Scope\n\n There is coffee all over the world. Increasingly, in a world in which\n computing is ubiquitous, the computists want to make coffee. Coffee\n brewing is an art, but the distributed intelligence of the web-\n connected world transcends art. Thus, there is a strong, dark, rich\n requirement for a protocol designed espressoly for the brewing of\n coffee. Coffee is brewed using coffee pots. Networked coffee pots\n require a control protocol if they are to be controlled.\n\n Increasingly, home and consumer devices are being connected to the\n Internet. Early networking experiments demonstrated vending devices\n connected to the Internet for status monitoring [COKE]. One of the\n first remotely _operated_ machine to be hooked up to the Internet,\n the Internet Toaster, (controlled","scope_keywords":["2324","holder","http","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2324 This document describes HTCPCP, a protocol for controlling,\n monitoring, and diagnosing coffee pots.\n\n1. Rationale and Scope\n\n There is coffee all over the world. Increasingly, in a world in which\n computing is ubiquitous, the computists want to make coffee. Coffee\n brewing is an art, but the distributed intelligence of the web-\n connected world transcends art. Thus, there is a strong, dark, rich\n requirement for a protocol designed espressoly for the brewing of\n coffee. Coffee is brewed using coffee pots. Networked coffee pots\n require a control protocol if they are to be controlled.\n\n Increasingly, home and consumer devices are being connected to the\n Internet. Early networking experiments demonstrated vending devices\n connected to the Internet for status monitoring [COKE]. One of the\n first remotely _operated_ machine to be hooked up to the Internet,\n the Internet Toaster, (controlled 2324 holder http policy nested-reference unchanged"},{"id":"IETF RFC 2330","type":"specification","body":"IETF","designation":"RFC 2330","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2330.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2330.txt","https://www.rfc-editor.org/rfc/rfc2330.pdf"],"folder":"IETF/RFC-2330","files":{"txt":{"path":"standards/IETF/RFC-2330/RFC-2330.txt","sha256":"bc032cf02d165cdbaa847a07e86136320f1e7e5f2b3e26dc0d97a98701840d3d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Paxson\nRequest for Comments: 2330 Lawrence Berkeley National Lab\nCategory: Informational G. Almes\n Advanced Network & Services\n J. Mahdavi\n M. Mathis\n Pittsburgh Supercomputer Center\n May 1998\n\n Framework for IP Performance Metrics\n\n1. Status of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\n2. Copyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. STATUS OF THIS MEMO.............................................1\n 2. COPYRIGHT NOTICE................................................1\n 3. INTRODUCTION....................................................2\n 4. CRITERIA FOR IP PERFORMANCE METRICS.............................3\n 5. TERMINOLOGY FOR PATHS AND CLOUDS................................4\n 6. F","scope_keywords":["2330","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2678","folder":"IETF/RFC-2678","source":"IETF/RFC-2678/RFC-2678.txt","version":null},{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3357","folder":"IETF/RFC-3357","source":"IETF/RFC-3357/RFC-3357.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3763","folder":"IETF/RFC-3763","source":"IETF/RFC-3763/RFC-3763.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5136","folder":"IETF/RFC-5136","source":"IETF/RFC-5136/RFC-5136.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null}],"search_text":"IETF RFC 2330 Network Working Group V. Paxson\nRequest for Comments: 2330 Lawrence Berkeley National Lab\nCategory: Informational G. Almes\n Advanced Network & Services\n J. Mahdavi\n M. Mathis\n Pittsburgh Supercomputer Center\n May 1998\n\n Framework for IP Performance Metrics\n\n1. Status of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\n2. Copyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. STATUS OF THIS MEMO.............................................1\n 2. COPYRIGHT NOTICE................................................1\n 3. INTRODUCTION....................................................2\n 4. CRITERIA FOR IP PERFORMANCE METRICS.............................3\n 5. TERMINOLOGY FOR PATHS AND CLOUDS................................4\n 6. F 2330 key path nested-reference unchanged"},{"id":"IETF RFC 2679","type":"specification","body":"IETF","designation":"RFC 2679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2679.txt","https://www.rfc-editor.org/rfc/rfc2679.pdf"],"folder":"IETF/RFC-2679","files":{"txt":{"path":"standards/IETF/RFC-2679/RFC-2679.txt","sha256":"910c2351d4d3f8979f42ec7b5f6a33f2deaf09f87286de1f28d7df983dd944a4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Almes\nRequest for Comments: 2679 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A One-way Delay Metric for IPPM\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n2. Introduction\n\n This memo defines a metric for one-way delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IPPM Framework document, RFC 2330 [1]; the reader is assumed to be\n familiar with that document.\n\n This memo","scope_keywords":["2679","key","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3763","folder":"IETF/RFC-3763","source":"IETF/RFC-3763/RFC-3763.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null}],"search_text":"IETF RFC 2679 Network Working Group G. Almes\nRequest for Comments: 2679 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A One-way Delay Metric for IPPM\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n2. Introduction\n\n This memo defines a metric for one-way delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IPPM Framework document, RFC 2330 [1]; the reader is assumed to be\n familiar with that document.\n\n This memo 2679 key path risk nested-reference unchanged"},{"id":"IETF RFC 2681","type":"specification","body":"IETF","designation":"RFC 2681","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2681.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2681.txt","https://www.rfc-editor.org/rfc/rfc2681.pdf"],"folder":"IETF/RFC-2681","files":{"txt":{"path":"standards/IETF/RFC-2681/RFC-2681.txt","sha256":"666e76e6004b8b98c8ed767e49d2cff67ca065864b190f7c6c979569d5b4bcf0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Almes\nRequest for Comments: 2681 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A Round-trip Delay Metric for IPPM\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a metric for round-trip delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IPPM Framework document, RFC 2330 [1], and follows closely the\n corresponding metric for One-way Delay (\"","scope_keywords":["2681","key","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null}],"search_text":"IETF RFC 2681 Network Working Group G. Almes\nRequest for Comments: 2681 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A Round-trip Delay Metric for IPPM\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a metric for round-trip delay of packets across\n Internet paths. It builds on notions introduced and discussed in the\n IPPM Framework document, RFC 2330 [1], and follows closely the\n corresponding metric for One-way Delay (\" 2681 key path risk nested-reference unchanged"},{"id":"IETF RFC 2695","type":"specification","body":"IETF","designation":"RFC 2695","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2695.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2695.txt","https://www.rfc-editor.org/rfc/rfc2695.pdf"],"folder":"IETF/RFC-2695","files":{"txt":{"path":"standards/IETF/RFC-2695/RFC-2695.txt","sha256":"564acd18d7cc5437eb23323351bb628153dc673ecb641c5828a256967a290b84"}},"tags":["nested-reference","unchanged"],"summary":"This document describes two authentication mechanisms created by Sun\n Microsystems that are commonly used in conjunction with the ONC\n Remote Procedure Call (ONC RPC Version 2) protocol.\n\nWARNING\n\n The DH authentication as defined in Section 2 in this document refers\n to the authentication mechanism with flavor AUTH_DH currently\n implemented in ONC RPC. It uses the underlying Diffie-Hellman\n algorithm for key exchange. The DH authentication defined in this\n document is flawed due to the selection of a small prime for the BASE\n field (Section 2.5). To avoid the flaw a new DH authentication\n mechanism could be defined with a larger prime. However, the new DH\n authentication would not be interoperable with the existing DH\n authentication.\n\n As illustrated in [10], a large number of attacks are possible on ONC\n RPC system services that use non-secure authentication mechanisms.\n Other secure ","scope_keywords":["2695","algorithm","authentication","credential","encryption","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null}],"search_text":"IETF RFC 2695 This document describes two authentication mechanisms created by Sun\n Microsystems that are commonly used in conjunction with the ONC\n Remote Procedure Call (ONC RPC Version 2) protocol.\n\nWARNING\n\n The DH authentication as defined in Section 2 in this document refers\n to the authentication mechanism with flavor AUTH_DH currently\n implemented in ONC RPC. It uses the underlying Diffie-Hellman\n algorithm for key exchange. The DH authentication defined in this\n document is flawed due to the selection of a small prime for the BASE\n field (Section 2.5). To avoid the flaw a new DH authentication\n mechanism could be defined with a larger prime. However, the new DH\n authentication would not be interoperable with the existing DH\n authentication.\n\n As illustrated in [10], a large number of attacks are possible on ONC\n RPC system services that use non-secure authentication mechanisms.\n Other secure  2695 algorithm authentication credential encryption key timestamp nested-reference unchanged"},{"id":"IETF RFC 3108","type":"specification","body":"IETF","designation":"RFC 3108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3108.txt","https://www.rfc-editor.org/rfc/rfc3108.pdf"],"folder":"IETF/RFC-3108","files":{"txt":{"path":"standards/IETF/RFC-3108/RFC-3108.txt","sha256":"2d3e8223f9002da2bf2f34f8895b2ed8124f743d9a2f3b6ff6a3cae9b09d28b4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes conventions for using the Session Description\n Protocol (SDP) described in RFC 2327 for controlling ATM Bearer\n Connections, and any associated ATM Adaptation Layer (AAL). The AALs\n addressed are Type 1, Type 2 and Type 5. This list of conventions is\n meant to be exhaustive. Individual applications can use subsets of\n these conventions. Further, these conventions are meant to comply\n strictly with the SDP syntax as defined in RFC 2327.","scope_keywords":["3108","attribute","attributes","key","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3108 This document describes conventions for using the Session Description\n Protocol (SDP) described in RFC 2327 for controlling ATM Bearer\n Connections, and any associated ATM Adaptation Layer (AAL). The AALs\n addressed are Type 1, Type 2 and Type 5. This list of conventions is\n meant to be exhaustive. Individual applications can use subsets of\n these conventions. Further, these conventions are meant to comply\n strictly with the SDP syntax as defined in RFC 2327. 3108 attribute attributes key presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 3118","type":"specification","body":"IETF","designation":"RFC 3118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3118.txt","https://www.rfc-editor.org/rfc/rfc3118.pdf"],"folder":"IETF/RFC-3118","files":{"txt":{"path":"standards/IETF/RFC-3118/RFC-3118.txt","sha256":"23d81251e739d9618b9b7503c0d9848c8d54290c78302cd7f3c5ddb72f9fb4ce"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option through which authorization tickets can be easily\n generated and newly attached hosts with proper authorization can be\n automatically configured from an authenticated DHCP server. DHCP\n provides a framework for passing configuration information to hosts\n on a TCP/IP network. In some situations, network administrators may\n wish to constrain the allocation of addresses to authorized hosts.\n Additionally, some network administrators may wish to provide for\n authentication of the source and contents of DHCP messages.\n\n1. Introduction\n\n DHCP [1] transports protocol stack configuration parameters from\n centrally administered servers to TCP/IP hosts. Among those\n parameters are an IP address. DHCP servers can be configured to\n dynamically allocate addresses from a pool of addresses, eliminating\n a manual step in conf","scope_keywords":["3118","algorithm","audit","authentication","authorization","key","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3203","folder":"IETF/RFC-3203","source":"IETF/RFC-3203/RFC-3203.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3396","folder":"IETF/RFC-3396","source":"IETF/RFC-3396/RFC-3396.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3993","folder":"IETF/RFC-3993","source":"IETF/RFC-3993/RFC-3993.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4361","folder":"IETF/RFC-4361","source":"IETF/RFC-4361/RFC-4361.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null}],"search_text":"IETF RFC 3118 This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option through which authorization tickets can be easily\n generated and newly attached hosts with proper authorization can be\n automatically configured from an authenticated DHCP server. DHCP\n provides a framework for passing configuration information to hosts\n on a TCP/IP network. In some situations, network administrators may\n wish to constrain the allocation of addresses to authorized hosts.\n Additionally, some network administrators may wish to provide for\n authentication of the source and contents of DHCP messages.\n\n1. Introduction\n\n DHCP [1] transports protocol stack configuration parameters from\n centrally administered servers to TCP/IP hosts. Among those\n parameters are an IP address. DHCP servers can be configured to\n dynamically allocate addresses from a pool of addresses, eliminating\n a manual step in conf 3118 algorithm audit authentication authorization key subject timestamp nested-reference unchanged"},{"id":"IETF RFC 3830","type":"specification","body":"IETF","designation":"RFC 3830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3830.txt","https://www.rfc-editor.org/rfc/rfc3830.pdf"],"folder":"IETF/RFC-3830","files":{"txt":{"path":"standards/IETF/RFC-3830/RFC-3830.txt","sha256":"b34ed67aa46d863d74dee691e86b634fb59e7764ab3e24e620bd15889fe40d83"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a key management scheme that can be used for\n real-time applications (both for peer-to-peer communication and group\n communication). In particular, its use to support the Secure Real-\n time Transport Protocol is described in detail.\n\n Security protocols for real-time multimedia applications have started\n to appear. This has brought forward the need for a key management\n solution to support these protocols.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 3830 MIKEY August 2004","scope_keywords":["3830","authorization","certificate","certificates","encryption","hash","key","keys","management","policies","policy","signature","signatures","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4771","folder":"IETF/RFC-4771","source":"IETF/RFC-4771/RFC-4771.txt","version":null},{"body":"IETF","designation":"RFC 4909","folder":"IETF/RFC-4909","source":"IETF/RFC-4909/RFC-4909.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null}],"search_text":"IETF RFC 3830 This document describes a key management scheme that can be used for\n real-time applications (both for peer-to-peer communication and group\n communication). In particular, its use to support the Secure Real-\n time Transport Protocol is described in detail.\n\n Security protocols for real-time multimedia applications have started\n to appear. This has brought forward the need for a key management\n solution to support these protocols.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 3830 MIKEY August 2004 3830 authorization certificate certificates encryption hash key keys management policies policy signature signatures timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 4082","type":"specification","body":"IETF","designation":"RFC 4082","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4082.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4082.txt","https://www.rfc-editor.org/rfc/rfc4082.pdf"],"folder":"IETF/RFC-4082","files":{"txt":{"path":"standards/IETF/RFC-4082/RFC-4082.txt","sha256":"6feec304f8086502f94011f3d00e76edff918946903630856c87c9a7c340ed84"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces Timed Efficient Stream Loss-tolerant\n Authentication (TESLA). TESLA allows all receivers to check the\n integrity and authenticate the source of each packet in multicast or\n broadcast data streams. TESLA requires no trust between receivers,\n uses low-cost operations per packet at both sender and receiver, can\n tolerate any level of loss without retransmissions, and requires no\n per-receiver state at the sender. TESLA can protect receivers\n against denial of service attacks in certain circumstances. Each\n receiver must be loosely time-synchronized with the source in order\n to verify messages, but otherwise receivers do not have to send any\n messages. TESLA alone cannot support non-repudiation of the data\n source to third parties.\n\n This informational document is intended to assist in writing\n standardizable and secure specifications for protocols based on TESLA\n in","scope_keywords":["4082","authentication","key","keys","signature","signatures","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 4082 This document introduces Timed Efficient Stream Loss-tolerant\n Authentication (TESLA). TESLA allows all receivers to check the\n integrity and authenticate the source of each packet in multicast or\n broadcast data streams. TESLA requires no trust between receivers,\n uses low-cost operations per packet at both sender and receiver, can\n tolerate any level of loss without retransmissions, and requires no\n per-receiver state at the sender. TESLA can protect receivers\n against denial of service attacks in certain circumstances. Each\n receiver must be loosely time-synchronized with the source in order\n to verify messages, but otherwise receivers do not have to send any\n messages. TESLA alone cannot support non-repudiation of the data\n source to third parties.\n\n This informational document is intended to assist in writing\n standardizable and secure specifications for protocols based on TESLA\n in 4082 authentication key keys signature signatures tls trust nested-reference unchanged"},{"id":"IETF RFC 4193","type":"specification","body":"IETF","designation":"RFC 4193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4193.txt","https://www.rfc-editor.org/rfc/rfc4193.pdf"],"folder":"IETF/RFC-4193","files":{"txt":{"path":"standards/IETF/RFC-4193/RFC-4193.txt","sha256":"cf5e0f8aba837828ef3e71807d901cee71efd97fd6d2e0c985603c074cdd631a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an IPv6 unicast address format that is globally\n unique and is intended for local communications, usually inside of a\n site. These addresses are not expected to be routable on the global\n Internet.","scope_keywords":["4193","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6177","folder":"IETF/RFC-6177","source":"IETF/RFC-6177/RFC-6177.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 4193 This document defines an IPv6 unicast address format that is globally\n unique and is intended for local communications, usually inside of a\n site. These addresses are not expected to be routable on the global\n Internet. 4193 algorithm key nested-reference unchanged"},{"id":"IETF RFC 4285","type":"specification","body":"IETF","designation":"RFC 4285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4285.txt","https://www.rfc-editor.org/rfc/rfc4285.pdf"],"folder":"IETF/RFC-4285","files":{"txt":{"path":"standards/IETF/RFC-4285/RFC-4285.txt","sha256":"a57a260f19d02d22df343ec6bdde455b23ec77a38687329a070ce608a0b650bd"}},"tags":["nested-reference","unchanged"],"summary":"IPsec is specified as the means of securing signaling messages\n between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6).\n MIPv6 signaling messages that are secured include the Binding Updates\n and Acknowledgement messages used for managing the bindings between a\n Mobile Node and its Home Agent. This document proposes an alternate\n method for securing MIPv6 signaling messages between Mobile Nodes and\n Home Agents. The alternate method defined here consists of a\n MIPv6-specific mobility message authentication option that can be\n added to MIPv6 signaling messages.","scope_keywords":["4285","authentication","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4285 IPsec is specified as the means of securing signaling messages\n between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6).\n MIPv6 signaling messages that are secured include the Binding Updates\n and Acknowledgement messages used for managing the bindings between a\n Mobile Node and its Home Agent. This document proposes an alternate\n method for securing MIPv6 signaling messages between Mobile Nodes and\n Home Agents. The alternate method defined here consists of a\n MIPv6-specific mobility message authentication option that can be\n added to MIPv6 signaling messages. 4285 authentication authorization nested-reference unchanged"},{"id":"IETF RFC 4442","type":"specification","body":"IETF","designation":"RFC 4442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4442.txt","https://www.rfc-editor.org/rfc/rfc4442.pdf"],"folder":"IETF/RFC-4442","files":{"txt":{"path":"standards/IETF/RFC-4442/RFC-4442.txt","sha256":"75dbb8c5aafe866d8823fbc377ff085011140b3e083d291403bca5b7b254ad91"}},"tags":["nested-reference","unchanged"],"summary":"TESLA, the Timed Efficient Stream Loss-tolerant Authentication\n protocol, provides source authentication in multicast scenarios.\n TESLA is an efficient protocol with low communication and computation\n overhead that scales to large numbers of receivers and also tolerates\n packet loss. TESLA is based on loose time synchronization between\n the sender and the receivers. Source authentication is realized in\n TESLA by using Message Authentication Code (MAC) chaining. The use\n of TESLA within the Secure Real-time Transport Protocol (SRTP) has\n been published, targeting multicast authentication in scenarios where\n SRTP is applied to protect the multimedia data. This solution\n assumes that TESLA parameters are made available by out-of-band\n mechanisms.\n\n This document specifies payloads for the Multimedia Internet Keying\n (MIKEY) protocol for bootstrapping TESLA for source authentication of\n secu","scope_keywords":["4442","authentication","certificate","encryption","identification","key","keys","management","policy","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null}],"search_text":"IETF RFC 4442 TESLA, the Timed Efficient Stream Loss-tolerant Authentication\n protocol, provides source authentication in multicast scenarios.\n TESLA is an efficient protocol with low communication and computation\n overhead that scales to large numbers of receivers and also tolerates\n packet loss. TESLA is based on loose time synchronization between\n the sender and the receivers. Source authentication is realized in\n TESLA by using Message Authentication Code (MAC) chaining. The use\n of TESLA within the Secure Real-time Transport Protocol (SRTP) has\n been published, targeting multicast authentication in scenarios where\n SRTP is applied to protect the multimedia data. This solution\n assumes that TESLA parameters are made available by out-of-band\n mechanisms.\n\n This document specifies payloads for the Multimedia Internet Keying\n (MIKEY) protocol for bootstrapping TESLA for source authentication of\n secu 4442 authentication certificate encryption identification key keys management policy validation nested-reference unchanged"},{"id":"IETF RFC 4551","type":"specification","body":"IETF","designation":"RFC 4551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4551.txt","https://www.rfc-editor.org/rfc/rfc4551.pdf"],"folder":"IETF/RFC-4551","files":{"txt":{"path":"standards/IETF/RFC-4551/RFC-4551.txt","sha256":"8bc568979fa26fa7bec6a0f39613f59a6c05db4b7d9ef37c15d6e4fd9df848e7"}},"tags":["nested-reference","unchanged"],"summary":"Often, multiple IMAP (RFC 3501) clients need to coordinate changes to\n a common IMAP mailbox. Examples include different clients working on\n behalf of the same user, and multiple users accessing shared\n mailboxes. These clients need a mechanism to synchronize state\n changes for messages within the mailbox. They must be able to\n guarantee that only one client can change message state (e.g.,\n message flags) at any time. An example of such an application is use\n of an IMAP mailbox as a message queue with multiple dequeueing\n clients.\n\n The Conditional Store facility provides a protected update mechanism\n for message state information that can detect and resolve conflicts\n between multiple writing mail clients.\n\n The Conditional Store facility also allows a client to quickly\n resynchronize mailbox flag changes.\n\n This document defines an extension to IMAP (RFC 3501).\n\nMelnikov & Hole Standar","scope_keywords":["4551"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4731","folder":"IETF/RFC-4731","source":"IETF/RFC-4731/RFC-4731.txt","version":null},{"body":"IETF","designation":"RFC 5161","folder":"IETF/RFC-5161","source":"IETF/RFC-5161/RFC-5161.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null}],"search_text":"IETF RFC 4551 Often, multiple IMAP (RFC 3501) clients need to coordinate changes to\n a common IMAP mailbox. Examples include different clients working on\n behalf of the same user, and multiple users accessing shared\n mailboxes. These clients need a mechanism to synchronize state\n changes for messages within the mailbox. They must be able to\n guarantee that only one client can change message state (e.g.,\n message flags) at any time. An example of such an application is use\n of an IMAP mailbox as a message queue with multiple dequeueing\n clients.\n\n The Conditional Store facility provides a protected update mechanism\n for message state information that can detect and resolve conflicts\n between multiple writing mail clients.\n\n The Conditional Store facility also allows a client to quickly\n resynchronize mailbox flag changes.\n\n This document defines an extension to IMAP (RFC 3501).\n\nMelnikov & Hole Standar 4551 nested-reference unchanged"},{"id":"IETF RFC 4656","type":"specification","body":"IETF","designation":"RFC 4656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4656.txt","https://www.rfc-editor.org/rfc/rfc4656.pdf"],"folder":"IETF/RFC-4656","files":{"txt":{"path":"standards/IETF/RFC-4656/RFC-4656.txt","sha256":"768f1b2b193736c26c0271e2f9ea3e5cd0d05946a6ef5ea29c28378a4d4adbcf"}},"tags":["nested-reference","unchanged"],"summary":"The One-Way Active Measurement Protocol (OWAMP) measures\n unidirectional characteristics such as one-way delay and one-way\n loss. High-precision measurement of these one-way IP performance\n metrics became possible with wider availability of good time sources\n (such as GPS and CDMA). OWAMP enables the interoperability of these\n measurements.","scope_keywords":["4656","algorithm","authentication","encryption","key","keys","path","presentation","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 4656 The One-Way Active Measurement Protocol (OWAMP) measures\n unidirectional characteristics such as one-way delay and one-way\n loss. High-precision measurement of these one-way IP performance\n metrics became possible with wider availability of good time sources\n (such as GPS and CDMA). OWAMP enables the interoperability of these\n measurements. 4656 algorithm authentication encryption key keys path presentation timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 4765","type":"specification","body":"IETF","designation":"RFC 4765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4765.txt","https://www.rfc-editor.org/rfc/rfc4765.pdf"],"folder":"IETF/RFC-4765","files":{"txt":{"path":"standards/IETF/RFC-4765/RFC-4765.txt","sha256":"756b544dda4ab5ab29f5cf0001a880477bbdd207305c8339be94f7d21bc292f2"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of the Intrusion Detection Message Exchange Format\n (IDMEF) is to define data formats and exchange procedures for sharing\n information of interest to intrusion detection and response systems\n and to the management systems that may need to interact with them.\n\n This document describes a data model to represent information\n exported by intrusion detection systems and explains the rationale\n for using this model. An implementation of the data model in the\n Extensible Markup Language (XML) is presented, an XML Document Type\n Definition is developed, and examples are provided.\n\nDebar, et al. Experimental [Page 1]\n\f\nRFC 4765 The IDMEF March 2007","scope_keywords":["4765","attribute","attributes","management","policy","signature","signatures","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4766","folder":"IETF/RFC-4766","source":"IETF/RFC-4766/RFC-4766.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null}],"search_text":"IETF RFC 4765 The purpose of the Intrusion Detection Message Exchange Format\n (IDMEF) is to define data formats and exchange procedures for sharing\n information of interest to intrusion detection and response systems\n and to the management systems that may need to interact with them.\n\n This document describes a data model to represent information\n exported by intrusion detection systems and explains the rationale\n for using this model. An implementation of the data model in the\n Extensible Markup Language (XML) is presented, an XML Document Type\n Definition is developed, and examples are provided.\n\nDebar, et al. Experimental [Page 1]\n\f\nRFC 4765 The IDMEF March 2007 4765 attribute attributes management policy signature signatures timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5101","type":"specification","body":"IETF","designation":"RFC 5101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5101.txt","https://www.rfc-editor.org/rfc/rfc5101.pdf"],"folder":"IETF/RFC-5101","files":{"txt":{"path":"standards/IETF/RFC-5101/RFC-5101.txt","sha256":"52e6e1b19d5ed8ed8c852b49b947ddc0edd3766e3eded714c914bda766280960"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IP Flow Information Export (IPFIX)\n protocol that serves for transmitting IP Traffic Flow information\n over the network. In order to transmit IP Traffic Flow information\n from an Exporting Process to an information Collecting Process, a\n common representation of flow data and a standard means of\n communicating them is required. This document describes how the\n IPFIX Data and Template Records are carried over a number of\n transport protocols from an IPFIX Exporting Process to an IPFIX\n Collecting Process.","scope_keywords":["5101","authentication","key","keys","management","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5103","folder":"IETF/RFC-5103","source":"IETF/RFC-5103/RFC-5103.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5101 This document specifies the IP Flow Information Export (IPFIX)\n protocol that serves for transmitting IP Traffic Flow information\n over the network. In order to transmit IP Traffic Flow information\n from an Exporting Process to an information Collecting Process, a\n common representation of flow data and a standard means of\n communicating them is required. This document describes how the\n IPFIX Data and Template Records are carried over a number of\n transport protocols from an IPFIX Exporting Process to an IPFIX\n Collecting Process. 5101 authentication key keys management presentation tls nested-reference unchanged"},{"id":"IETF RFC 5153","type":"specification","body":"IETF","designation":"RFC 5153","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5153.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5153.txt","https://www.rfc-editor.org/rfc/rfc5153.pdf"],"folder":"IETF/RFC-5153","files":{"txt":{"path":"standards/IETF/RFC-5153/RFC-5153.txt","sha256":"70015436265a7c0862fd7adf224add851459621b839a00c5b3ff37ca0df410b7"}},"tags":["nested-reference","unchanged"],"summary":"The IP Flow Information Export (IPFIX) protocol defines how IP Flow\n information can be exported from routers, measurement probes, or\n other devices. This document provides guidelines for the\n implementation and use of the IPFIX protocol. Several sets of\n guidelines address Template management, transport-specific issues,\n implementation of Exporting and Collecting Processes, and IPFIX\n implementation on middleboxes (such as firewalls, network address\n translators, tunnel endpoints, packet classifiers, etc.).","scope_keywords":["5153","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null}],"search_text":"IETF RFC 5153 The IP Flow Information Export (IPFIX) protocol defines how IP Flow\n information can be exported from routers, measurement probes, or\n other devices. This document provides guidelines for the\n implementation and use of the IPFIX protocol. Several sets of\n guidelines address Template management, transport-specific issues,\n implementation of Exporting and Collecting Processes, and IPFIX\n implementation on middleboxes (such as firewalls, network address\n translators, tunnel endpoints, packet classifiers, etc.). 5153 management tls nested-reference unchanged"},{"id":"IETF RFC 5197","type":"specification","body":"IETF","designation":"RFC 5197","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5197.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5197.txt","https://www.rfc-editor.org/rfc/rfc5197.pdf"],"folder":"IETF/RFC-5197","files":{"txt":{"path":"standards/IETF/RFC-5197/RFC-5197.txt","sha256":"67720e1eb2f057d18bd39d299b0ae731f8bfa3457d0e16207951b4b07acdf6ba"}},"tags":["nested-reference","unchanged"],"summary":"Multimedia Internet Keying (MIKEY) is a key management protocol that\n can be used for real-time applications. In particular, it has been\n defined focusing on the support of the Secure Real-time Transport\n Protocol (SRTP). MIKEY itself is standardized within RFC 3830 and\n defines four key distribution methods. Moreover, it is defined to\n allow extensions of the protocol. As MIKEY becomes more and more\n accepted, extensions to the base protocol arise, especially in terms\n of additional key distribution methods but also in terms of payload\n enhancements.\n\n This document provides an overview about the MIKEY base document in\n general as well as the existing extensions for MIKEY, which have been\n defined or are in the process of definition. It is intended as an\n additional source of information for developers or architects to\n provide more insight in use case scenarios and motivations as well ","scope_keywords":["5197","algorithm","algorithms","authentication","certificate","encryption","key","keys","management","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 5197 Multimedia Internet Keying (MIKEY) is a key management protocol that\n can be used for real-time applications. In particular, it has been\n defined focusing on the support of the Secure Real-time Transport\n Protocol (SRTP). MIKEY itself is standardized within RFC 3830 and\n defines four key distribution methods. Moreover, it is defined to\n allow extensions of the protocol. As MIKEY becomes more and more\n accepted, extensions to the base protocol arise, especially in terms\n of additional key distribution methods but also in terms of payload\n enhancements.\n\n This document provides an overview about the MIKEY base document in\n general as well as the existing extensions for MIKEY, which have been\n defined or are in the process of definition. It is intended as an\n additional source of information for developers or architects to\n provide more insight in use case scenarios and motivations as well  5197 algorithm algorithms authentication certificate encryption key keys management signature signatures nested-reference unchanged"},{"id":"IETF RFC 5580","type":"specification","body":"IETF","designation":"RFC 5580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5580.txt","https://www.rfc-editor.org/rfc/rfc5580.pdf"],"folder":"IETF/RFC-5580","files":{"txt":{"path":"standards/IETF/RFC-5580/RFC-5580.txt","sha256":"474e3b5d30ba1768810a01ce43deaaf8b9031982458856f704dd9f320482eef4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes procedures for conveying access-network\n ownership and location information based on civic and geospatial\n location formats in Remote Authentication Dial-In User Service\n (RADIUS) and Diameter.\n\n The distribution of location information is a privacy-sensitive task.\n Dealing with mechanisms to preserve the user's privacy is important\n and is addressed in this document.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is","scope_keywords":["5580","attribute","attributes","authentication","authorization","delivery","http","key","license","policies","policy","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 5580 This document describes procedures for conveying access-network\n ownership and location information based on civic and geospatial\n location formats in Remote Authentication Dial-In User Service\n (RADIUS) and Diameter.\n\n The distribution of location information is a privacy-sensitive task.\n Dealing with mechanisms to preserve the user's privacy is important\n and is addressed in this document.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is 5580 attribute attributes authentication authorization delivery http key license policies policy profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5776","type":"specification","body":"IETF","designation":"RFC 5776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5776.txt","https://www.rfc-editor.org/rfc/rfc5776.pdf"],"folder":"IETF/RFC-5776","files":{"txt":{"path":"standards/IETF/RFC-5776/RFC-5776.txt","sha256":"1d9f6133435e68a4c65b7f5b0d2c81638c00ff9c6aaa96756538fbe6403ac862"}},"tags":["nested-reference","unchanged"],"summary":"This document details the Timed Efficient Stream Loss-Tolerant\n Authentication (TESLA) packet source authentication and packet\n integrity verification protocol and its integration within the\n Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable\n Multicast (NORM) content delivery protocols. This document only\n considers the authentication/integrity verification of the packets\n generated by the session's sender. The authentication and integrity\n verification of the packets sent by receivers, if any, is out of the\n scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of","scope_keywords":["5776","authentication","delivery","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 5776 This document details the Timed Efficient Stream Loss-Tolerant\n Authentication (TESLA) packet source authentication and packet\n integrity verification protocol and its integration within the\n Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable\n Multicast (NORM) content delivery protocols. This document only\n considers the authentication/integrity verification of the packets\n generated by the session's sender. The authentication and integrity\n verification of the packets sent by receivers, if any, is out of the\n scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of 5776 authentication delivery http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5906","type":"specification","body":"IETF","designation":"RFC 5906","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5906.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5906.txt","https://www.rfc-editor.org/rfc/rfc5906.pdf"],"folder":"IETF/RFC-5906","files":{"txt":{"path":"standards/IETF/RFC-5906/RFC-5906.txt","sha256":"a6c439ca1011e408f7e64c72bfd3e7bc8bbe823b478d4191e215ec97d3da42d9"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the Autokey security model for authenticating\n servers to clients using the Network Time Protocol (NTP) and public\n key cryptography. Its design is based on the premise that IPsec\n schemes cannot be adopted intact, since that would preclude stateless\n servers and severely compromise timekeeping accuracy. In addition,\n Public Key Infrastructure (PKI) schemes presume authenticated time\n values are always available to enforce certificate lifetimes;\n however, cryptographically verified timestamps require interaction\n between the timekeeping and authentication functions.\n\n This memo includes the Autokey requirements analysis, design\n principles, and protocol specification. A detailed description of\n the protocol states, events, and transition functions is included. A\n prototype of the Autokey design based on this memo has been\n implemented, tested, and documented in the NT","scope_keywords":["5906","authentication","certificate","certificates","http","key","license","pki","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null}],"search_text":"IETF RFC 5906 This memo describes the Autokey security model for authenticating\n servers to clients using the Network Time Protocol (NTP) and public\n key cryptography. Its design is based on the premise that IPsec\n schemes cannot be adopted intact, since that would preclude stateless\n servers and severely compromise timekeeping accuracy. In addition,\n Public Key Infrastructure (PKI) schemes presume authenticated time\n values are always available to enforce certificate lifetimes;\n however, cryptographically verified timestamps require interaction\n between the timekeeping and authentication functions.\n\n This memo includes the Autokey requirements analysis, design\n principles, and protocol specification. A detailed description of\n the protocol states, events, and transition functions is included. A\n prototype of the Autokey design based on this memo has been\n implemented, tested, and documented in the NT 5906 authentication certificate certificates http key license pki subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 1306","type":"specification","body":"IETF","designation":"RFC 1306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1306.txt","https://www.rfc-editor.org/rfc/rfc1306.pdf"],"folder":"IETF/RFC-1306","files":{"txt":{"path":"standards/IETF/RFC-1306/RFC-1306.txt","sha256":"cfa1082347bd658af8073f61e296e8394f743f5a09b585210a0aadb112c157eb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Nicholson\nRequest for Comments: 1306 J. Young\n Cray Research, Inc.\n March 1992\n\n Experiences Supporting By-Request Circuit-Switched T3 Networks\n\nStatus of this Memo\n\n This RFC provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This memo describes the experiences of a project team at Cray\n Research, Inc., in implementing support for circuit-switched T3\n services. While the issues discussed may not be directly relevant to\n the research problems of the Internet, they may be interesting to a\n number of researchers and implementers.\n\n Developers at Cray Research, Inc. were presented with an opportunity\n to use a circuit-switched T3 network for wide area networking. They\n devised an architectural model for using this new resource. This\n involves activating the circuit-switched","scope_keywords":["1306","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1307","folder":"IETF/RFC-1307","source":"IETF/RFC-1307/RFC-1307.txt","version":null}],"search_text":"IETF RFC 1306 Network Working Group A. Nicholson\nRequest for Comments: 1306 J. Young\n Cray Research, Inc.\n March 1992\n\n Experiences Supporting By-Request Circuit-Switched T3 Networks\n\nStatus of this Memo\n\n This RFC provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This memo describes the experiences of a project team at Cray\n Research, Inc., in implementing support for circuit-switched T3\n services. While the issues discussed may not be directly relevant to\n the research problems of the Internet, they may be interesting to a\n number of researchers and implementers.\n\n Developers at Cray Research, Inc. were presented with an opportunity\n to use a circuit-switched T3 network for wide area networking. They\n devised an architectural model for using this new resource. This\n involves activating the circuit-switched 1306 path nested-reference unchanged"},{"id":"IETF RFC 1307","type":"specification","body":"IETF","designation":"RFC 1307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1307.txt","https://www.rfc-editor.org/rfc/rfc1307.pdf"],"folder":"IETF/RFC-1307","files":{"txt":{"path":"standards/IETF/RFC-1307/RFC-1307.txt","sha256":"960cfcf87a411db81bd7b68da7bd5b7e3447d9a92f23cc868cd6c5300676ac11"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an experimental protocol developed by a project\n team at Cray Research, Inc., in implementing support for circuit-\n switched T3 services. The protocol is used for the control of\n network connections external to a host, but known to the host. It is\n documented here for the benefit of others who may wish to perform\n further research.\n\n While working with circuit-switched T3 networks, developers at Cray\n Research, Inc., defined a model wherein a host would generate control\n messages for a network switch. This work is described in RFC 1306,\n \"Experiences Supporting By-Request Circuit-Switched T3 Networks\". In\n order to simplify the model it was decided that the inconsistencies\n of switch control should be hidden from the host generating the\n control messages. To that end, a protocol was defined and\n implemented. This RFC documents the Dynamically Switched Link\n Control Pr","scope_keywords":["1307","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1306","folder":"IETF/RFC-1306","source":"IETF/RFC-1306/RFC-1306.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null}],"search_text":"IETF RFC 1307 This memo describes an experimental protocol developed by a project\n team at Cray Research, Inc., in implementing support for circuit-\n switched T3 services. The protocol is used for the control of\n network connections external to a host, but known to the host. It is\n documented here for the benefit of others who may wish to perform\n further research.\n\n While working with circuit-switched T3 networks, developers at Cray\n Research, Inc., defined a model wherein a host would generate control\n messages for a network switch. This work is described in RFC 1306,\n \"Experiences Supporting By-Request Circuit-Switched T3 Networks\". In\n order to simplify the model it was decided that the inconsistencies\n of switch control should be hidden from the host generating the\n control messages. To that end, a protocol was defined and\n implemented. This RFC documents the Dynamically Switched Link\n Control Pr 1307 management path nested-reference unchanged"},{"id":"IETF RFC 1396","type":"specification","body":"IETF","designation":"RFC 1396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1396.txt","https://www.rfc-editor.org/rfc/rfc1396.pdf"],"folder":"IETF/RFC-1396","files":{"txt":{"path":"standards/IETF/RFC-1396/RFC-1396.txt","sha256":"0e1d40d4d964b6a89de95a3025979ad40be80ba7568c87baf97d4100c73a4586"}},"tags":["nested-reference","unchanged"],"summary":"This report provides a summary of the POISED Working Group (WG),\n starting from the events leading to the formation of the WG to the\n end of 1992. Necessarily, this synopsis represents my own\n perception, particularly for the \"prehistory\" period. Quite a few\n people hold strong views about both the overall sequence and specific\n events. My intent here is to convey as neutral a point of view as\n possible.\n\nBackground and Formation of POISED Working Group\n\n The POISED WG resulted from two sequences of activity, both\n intimately related to the growth of the Internet. During 1991, there\n was great concern that the IP address space was being depleted and\n that the routing tables were growing too large. Some change in the\n IP addressing and routing mechanisms seemed inevitable, and it became\n urgent to explore and choose what those changes should be. The ROAD\n Working Group was formed to study","scope_keywords":["1396","key","management","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3933","folder":"IETF/RFC-3933","source":"IETF/RFC-3933/RFC-3933.txt","version":null}],"search_text":"IETF RFC 1396 This report provides a summary of the POISED Working Group (WG),\n starting from the events leading to the formation of the WG to the\n end of 1992. Necessarily, this synopsis represents my own\n perception, particularly for the \"prehistory\" period. Quite a few\n people hold strong views about both the overall sequence and specific\n events. My intent here is to convey as neutral a point of view as\n possible.\n\nBackground and Formation of POISED Working Group\n\n The POISED WG resulted from two sequences of activity, both\n intimately related to the growth of the Internet. During 1991, there\n was great concern that the IP address space was being depleted and\n that the routing tables were growing too large. Some change in the\n IP addressing and routing mechanisms seemed inevitable, and it became\n urgent to explore and choose what those changes should be. The ROAD\n Working Group was formed to study 1396 key management presentation trust nested-reference unchanged"},{"id":"IETF RFC 1602","type":"specification","body":"IETF","designation":"RFC 1602","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1602.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1602.txt","https://www.rfc-editor.org/rfc/rfc1602.pdf"],"folder":"IETF/RFC-1602","files":{"txt":{"path":"standards/IETF/RFC-1602/RFC-1602.txt","sha256":"8ddcc06588f3c5787b674495f619e0217f671a9b36ff3b8aaf8f5318927435a2"}},"tags":["nested-reference","unchanged"],"summary":"This document is a revision of RFC 1310, which defined the official\n procedures for creating and documenting Internet Standards.\n\n This revision (revision 2) includes the following major changes:\n\n (a) The new management structure arising from the POISED Working\n Group is reflected. These changes were agreed to by the IETF\n plenary and by the IAB and IESG in November 1992 and accepted by\n the ISOC Board of Trustees at their December 1992 meeting.\n\n (b) Prototype status is added to the non-standards track maturity\n levels (Section 2.4.1).\n\n (c) The Intellectual Property Rights section is completely revised,\n in accordance with legal advice. Section 5 of this document\n replaces Sections 5 and 6 of RFC-1310. The new section 5 has\n been reviewed by legal counsel to the Internet Society.\n\nIAB - IESG [Page 1]\n\f\nRFC 1602 Internet Standards Process March 1994\n\n (d) An appeals procedure is added ","scope_keywords":["1602","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null},{"body":"IETF","designation":"RFC 1627","folder":"IETF/RFC-1627","source":"IETF/RFC-1627/RFC-1627.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1790","folder":"IETF/RFC-1790","source":"IETF/RFC-1790/RFC-1790.txt","version":null},{"body":"IETF","designation":"RFC 1818","folder":"IETF/RFC-1818","source":"IETF/RFC-1818/RFC-1818.txt","version":null},{"body":"IETF","designation":"RFC 1871","folder":"IETF/RFC-1871","source":"IETF/RFC-1871/RFC-1871.txt","version":null},{"body":"IETF","designation":"RFC 2014","folder":"IETF/RFC-2014","source":"IETF/RFC-2014/RFC-2014.txt","version":null},{"body":"IETF","designation":"RFC 2026","folder":"IETF/RFC-2026","source":"IETF/RFC-2026/RFC-2026.txt","version":null},{"body":"IETF","designation":"RFC 2027","folder":"IETF/RFC-2027","source":"IETF/RFC-2027/RFC-2027.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2282","folder":"IETF/RFC-2282","source":"IETF/RFC-2282/RFC-2282.txt","version":null},{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null}],"search_text":"IETF RFC 1602 This document is a revision of RFC 1310, which defined the official\n procedures for creating and documenting Internet Standards.\n\n This revision (revision 2) includes the following major changes:\n\n (a) The new management structure arising from the POISED Working\n Group is reflected. These changes were agreed to by the IETF\n plenary and by the IAB and IESG in November 1992 and accepted by\n the ISOC Board of Trustees at their December 1992 meeting.\n\n (b) Prototype status is added to the non-standards track maturity\n levels (Section 2.4.1).\n\n (c) The Intellectual Property Rights section is completely revised,\n in accordance with legal advice. Section 5 of this document\n replaces Sections 5 and 6 of RFC-1310. The new section 5 has\n been reviewed by legal counsel to the Internet Society.\n\nIAB - IESG [Page 1]\n\f\nRFC 1602 Internet Standards Process March 1994\n\n (d) An appeals procedure is added  1602 management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 1627","type":"specification","body":"IETF","designation":"RFC 1627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1627.txt","https://www.rfc-editor.org/rfc/rfc1627.pdf"],"folder":"IETF/RFC-1627","files":{"txt":{"path":"standards/IETF/RFC-1627/RFC-1627.txt","sha256":"82b03857434699c383397fb05b72d146adab62e6be02e41888370b5240b7d3d9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Lear\nRequest for Comments: 1627 Silicon Graphics, Inc.\nCategory: Informational E. Fair\n Apple Computer, Inc.\n D. Crocker\n Silicon Graphics, Inc.\n T. Kessler\n Sun Microsystems, Inc.\n July 1994\n\n Network 10 Considered Harmful\n (Some Practices Shouldn't be Codified)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nSUMMARY\n\n Re-use of Internet addresses for private IP networks is the topic of\n the recent RFC 1597 [1]. It reserves a set of IP network numbers,\n for (re-)use by any number of organizations, so long as those\n networks are not routed outside any single, private IP network. RFC\n 1597 departs from the basic architectural rule that IP addresses must\n be globally unique, and it does so without having had the benefit of\n the u","scope_keywords":["1627","authentication","key","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null}],"search_text":"IETF RFC 1627 Network Working Group E. Lear\nRequest for Comments: 1627 Silicon Graphics, Inc.\nCategory: Informational E. Fair\n Apple Computer, Inc.\n D. Crocker\n Silicon Graphics, Inc.\n T. Kessler\n Sun Microsystems, Inc.\n July 1994\n\n Network 10 Considered Harmful\n (Some Practices Shouldn't be Codified)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nSUMMARY\n\n Re-use of Internet addresses for private IP networks is the topic of\n the recent RFC 1597 [1]. It reserves a set of IP network numbers,\n for (re-)use by any number of organizations, so long as those\n networks are not routed outside any single, private IP network. RFC\n 1597 departs from the basic architectural rule that IP addresses must\n be globally unique, and it does so without having had the benefit of\n the u 1627 authentication key policy registered nested-reference unchanged"},{"id":"IETF RFC 2026","type":"specification","body":"IETF","designation":"RFC 2026","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2026.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2026.txt","https://www.rfc-editor.org/rfc/rfc2026.pdf"],"folder":"IETF/RFC-2026","files":{"txt":{"path":"standards/IETF/RFC-2026/RFC-2026.txt","sha256":"517f43032ba8325c82dff006dc0080df0da1754126f74af1c300cf1ef5b1f1ea"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents the process used by the Internet community for\n the standardization of protocols and procedures. It defines the\n stages in the standardization process, the requirements for moving a\n document between stages and the types of documents used during this\n process. It also addresses the intellectual property rights and\n copyright issues associated with the standards process.","scope_keywords":["2026","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2028","folder":"IETF/RFC-2028","source":"IETF/RFC-2028/RFC-2028.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2339","folder":"IETF/RFC-2339","source":"IETF/RFC-2339/RFC-2339.txt","version":null},{"body":"IETF","designation":"RFC 2357","folder":"IETF/RFC-2357","source":"IETF/RFC-2357/RFC-2357.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2436","folder":"IETF/RFC-2436","source":"IETF/RFC-2436/RFC-2436.txt","version":null},{"body":"IETF","designation":"RFC 2438","folder":"IETF/RFC-2438","source":"IETF/RFC-2438/RFC-2438.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2629","folder":"IETF/RFC-2629","source":"IETF/RFC-2629/RFC-2629.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2717","folder":"IETF/RFC-2717","source":"IETF/RFC-2717/RFC-2717.txt","version":null},{"body":"IETF","designation":"RFC 2732","folder":"IETF/RFC-2732","source":"IETF/RFC-2732/RFC-2732.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2795","folder":"IETF/RFC-2795","source":"IETF/RFC-2795/RFC-2795.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2850","folder":"IETF/RFC-2850","source":"IETF/RFC-2850/RFC-2850.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2886","folder":"IETF/RFC-2886","source":"IETF/RFC-2886/RFC-2886.txt","version":null},{"body":"IETF","designation":"RFC 2903","folder":"IETF/RFC-2903","source":"IETF/RFC-2903/RFC-2903.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3068","folder":"IETF/RFC-3068","source":"IETF/RFC-3068/RFC-3068.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3131","folder":"IETF/RFC-3131","source":"IETF/RFC-3131/RFC-3131.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3233","folder":"IETF/RFC-3233","source":"IETF/RFC-3233/RFC-3233.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3304","folder":"IETF/RFC-3304","source":"IETF/RFC-3304/RFC-3304.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3309","folder":"IETF/RFC-3309","source":"IETF/RFC-3309/RFC-3309.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3327","folder":"IETF/RFC-3327","source":"IETF/RFC-3327/RFC-3327.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3347","folder":"IETF/RFC-3347","source":"IETF/RFC-3347/RFC-3347.txt","version":null},{"body":"IETF","designation":"RFC 3356","folder":"IETF/RFC-3356","source":"IETF/RFC-3356/RFC-3356.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null},{"body":"IETF","designation":"RFC 3386","folder":"IETF/RFC-3386","source":"IETF/RFC-3386/RFC-3386.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3407","folder":"IETF/RFC-3407","source":"IETF/RFC-3407/RFC-3407.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3425","folder":"IETF/RFC-3425","source":"IETF/RFC-3425/RFC-3425.txt","version":null},{"body":"IETF","designation":"RFC 3427","folder":"IETF/RFC-3427","source":"IETF/RFC-3427/RFC-3427.txt","version":null},{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3453","folder":"IETF/RFC-3453","source":"IETF/RFC-3453/RFC-3453.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3478","folder":"IETF/RFC-3478","source":"IETF/RFC-3478/RFC-3478.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3531","folder":"IETF/RFC-3531","source":"IETF/RFC-3531/RFC-3531.txt","version":null},{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 3563","folder":"IETF/RFC-3563","source":"IETF/RFC-3563/RFC-3563.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3589","folder":"IETF/RFC-3589","source":"IETF/RFC-3589/RFC-3589.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3643","folder":"IETF/RFC-3643","source":"IETF/RFC-3643/RFC-3643.txt","version":null},{"body":"IETF","designation":"RFC 3667","folder":"IETF/RFC-3667","source":"IETF/RFC-3667/RFC-3667.txt","version":null},{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3683","folder":"IETF/RFC-3683","source":"IETF/RFC-3683/RFC-3683.txt","version":null},{"body":"IETF","designation":"RFC 3690","folder":"IETF/RFC-3690","source":"IETF/RFC-3690/RFC-3690.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 3933","folder":"IETF/RFC-3933","source":"IETF/RFC-3933/RFC-3933.txt","version":null},{"body":"IETF","designation":"RFC 3934","folder":"IETF/RFC-3934","source":"IETF/RFC-3934/RFC-3934.txt","version":null},{"body":"IETF","designation":"RFC 3967","folder":"IETF/RFC-3967","source":"IETF/RFC-3967/RFC-3967.txt","version":null},{"body":"IETF","designation":"RFC 3978","folder":"IETF/RFC-3978","source":"IETF/RFC-3978/RFC-3978.txt","version":null},{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 4052","folder":"IETF/RFC-4052","source":"IETF/RFC-4052/RFC-4052.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4608","folder":"IETF/RFC-4608","source":"IETF/RFC-4608/RFC-4608.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4766","folder":"IETF/RFC-4766","source":"IETF/RFC-4766/RFC-4766.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4794","folder":"IETF/RFC-4794","source":"IETF/RFC-4794/RFC-4794.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4845","folder":"IETF/RFC-4845","source":"IETF/RFC-4845/RFC-4845.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 4897","folder":"IETF/RFC-4897","source":"IETF/RFC-4897/RFC-4897.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5111","folder":"IETF/RFC-5111","source":"IETF/RFC-5111/RFC-5111.txt","version":null},{"body":"IETF","designation":"RFC 5125","folder":"IETF/RFC-5125","source":"IETF/RFC-5125/RFC-5125.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6410","folder":"IETF/RFC-6410","source":"IETF/RFC-6410/RFC-6410.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7127","folder":"IETF/RFC-7127","source":"IETF/RFC-7127/RFC-7127.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 2026 This memo documents the process used by the Internet community for\n the standardization of protocols and procedures. It defines the\n stages in the standardization process, the requirements for moving a\n document between stages and the types of documents used during this\n process. It also addresses the intellectual property rights and\n copyright issues associated with the standards process. 2026 policy nested-reference unchanged"},{"id":"IETF RFC 2437","type":"specification","body":"IETF","designation":"RFC 2437","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2437.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2437.txt","https://www.rfc-editor.org/rfc/rfc2437.pdf"],"folder":"IETF/RFC-2437","files":{"txt":{"path":"standards/IETF/RFC-2437/RFC-2437.txt","sha256":"2713f7fe5742641c2b16d30f802227296faac49227fe7a2b5433dbd67fe31e00"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 2437 J. Staddon\nObsoletes: 2313 RSA Laboratories\nCategory: Informational October 1998\n\n PKCS #1: RSA Cryptography Specifications\n Version 2.0\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction.....................................2\n 1.1 Overview.........................................3\n 2. Notation.........................................3\n 3. Key types........................................5\n 3.1 RSA public key...................................5\n 3.2 RSA private key..................................5\n 4. Data conversion primitives.......................6\n 4.1 I2OSP.......................","scope_keywords":["2437","algorithm","encryption","hash","identification","key","keys","presentation","signature","signatures","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"IETF RFC 2437 Network Working Group B. Kaliski\nRequest for Comments: 2437 J. Staddon\nObsoletes: 2313 RSA Laboratories\nCategory: Informational October 1998\n\n PKCS #1: RSA Cryptography Specifications\n Version 2.0\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction.....................................2\n 1.1 Overview.........................................3\n 2. Notation.........................................3\n 3. Key types........................................5\n 3.1 RSA public key...................................5\n 3.2 RSA private key..................................5\n 4. Data conversion primitives.......................6\n 4.1 I2OSP....................... 2437 algorithm encryption hash identification key keys presentation signature signatures validation nested-reference unchanged"},{"id":"IETF RFC 3710","type":"specification","body":"IETF","designation":"RFC 3710","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3710.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3710.txt","https://www.rfc-editor.org/rfc/rfc3710.pdf"],"folder":"IETF/RFC-3710","files":{"txt":{"path":"standards/IETF/RFC-3710/RFC-3710.txt","sha256":"8d06b3430607011332f6167044dd5dee25819bd0cb539c1659ab08eb657d436e"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides a charter for the Internet Engineering Steering\n Group (IESG), a management function of the Internet Engineering Task\n Force (IETF). It is meant to document the charter of the IESG as it\n is presently understood.\n\n1. Introduction","scope_keywords":["3710","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null}],"search_text":"IETF RFC 3710 This memo provides a charter for the Internet Engineering Steering\n Group (IESG), a management function of the Internet Engineering Task\n Force (IETF). It is meant to document the charter of the IESG as it\n is presently understood.\n\n1. Introduction 3710 management subject nested-reference unchanged"},{"id":"IETF RFC 1311","type":"specification","body":"IETF","designation":"RFC 1311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1311.txt","https://www.rfc-editor.org/rfc/rfc1311.pdf"],"folder":"IETF/RFC-1311","files":{"txt":{"path":"standards/IETF/RFC-1311/RFC-1311.txt","sha256":"3e66ad4e2e2c183ea0e4ae085951283cf92e5fcf8f6382454fe5802eb7aa8ecc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Activities Board\nRequest for Comments: 1311 J. Postel, Editor\n March 1992\n\n Introduction to the STD Notes\n\nStatus of this Memo\n\n This RFC describes a new sub-series of RFCs, called STDs (Standards).\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The STDs are a subseries of notes within the RFC series that are the\n Internet standards. The intent is to identify clearly for the\n Internet community those RFCs which document Internet standards.\n\n2. The Assignment of STD Numbers\n\n There is a need to be very clear about which specifications have\n completed the full process of standardization in the Internet. To do\n this an STD number will be assigned to a specification when it\n reaches the Standard maturity level. Note that specifications may be\n either Technical Specifications (TS) or Applicability Statements\n (AS).\n\n When a specification reaches the","scope_keywords":["1311","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1310","folder":"IETF/RFC-1310","source":"IETF/RFC-1310/RFC-1310.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1602","folder":"IETF/RFC-1602","source":"IETF/RFC-1602/RFC-1602.txt","version":null},{"body":"IETF","designation":"RFC 1603","folder":"IETF/RFC-1603","source":"IETF/RFC-1603/RFC-1603.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 2026","folder":"IETF/RFC-2026","source":"IETF/RFC-2026/RFC-2026.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null}],"search_text":"IETF RFC 1311 Network Working Group Internet Activities Board\nRequest for Comments: 1311 J. Postel, Editor\n March 1992\n\n Introduction to the STD Notes\n\nStatus of this Memo\n\n This RFC describes a new sub-series of RFCs, called STDs (Standards).\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n The STDs are a subseries of notes within the RFC series that are the\n Internet standards. The intent is to identify clearly for the\n Internet community those RFCs which document Internet standards.\n\n2. The Assignment of STD Numbers\n\n There is a need to be very clear about which specifications have\n completed the full process of standardization in the Internet. To do\n this an STD number will be assigned to a specification when it\n reaches the Standard maturity level. Note that specifications may be\n either Technical Specifications (TS) or Applicability Statements\n (AS).\n\n When a specification reaches the 1311 identification subject nested-reference unchanged"},{"id":"IETF RFC 1314","type":"specification","body":"IETF","designation":"RFC 1314","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1314.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1314.txt","https://www.rfc-editor.org/rfc/rfc1314.pdf"],"folder":"IETF/RFC-1314","files":{"txt":{"path":"standards/IETF/RFC-1314/RFC-1314.txt","sha256":"abb6919a4a441f01f7c302876d0bd34c76f4710f029cc204f831e9a0321f9df6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a standard file format for the exchange of\n fax-like black and white images within the Internet. It is a product\n of the Network Fax Working Group of the Internet Engineering Task\n Force (IETF).\n\n The standard is:\n\n ** The file format should be TIFF-B with multi-page files\n supported. Images should be encoded as one TIFF strip\n per page.\n\n ** Images should be compressed using MMR when possible. Images\n may also be MH or MR compressed or uncompressed. If MH or MR\n compression is used, scan lines should be \"byte-aligned\".\n\n ** For maximum interoperability, image resolutions should\n either be 600, 400, or 300 dpi; or else be one of the\n standard Group 3 fax resolutions (98 or 196 dpi\n vertically and 204 dpi horizontally).\n\n Note that this specification is self contained and an implementation\n should be possible without recourse to the TIFF references, and that\n only th","scope_keywords":["1314","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1314 This document defines a standard file format for the exchange of\n fax-like black and white images within the Internet. It is a product\n of the Network Fax Working Group of the Internet Engineering Task\n Force (IETF).\n\n The standard is:\n\n ** The file format should be TIFF-B with multi-page files\n supported. Images should be encoded as one TIFF strip\n per page.\n\n ** Images should be compressed using MMR when possible. Images\n may also be MH or MR compressed or uncompressed. If MH or MR\n compression is used, scan lines should be \"byte-aligned\".\n\n ** For maximum interoperability, image resolutions should\n either be 600, 400, or 300 dpi; or else be one of the\n standard Group 3 fax resolutions (98 or 196 dpi\n vertically and 204 dpi horizontally).\n\n Note that this specification is self contained and an implementation\n should be possible without recourse to the TIFF references, and that\n only th 1314 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 1750","type":"specification","body":"IETF","designation":"RFC 1750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1750.txt","https://www.rfc-editor.org/rfc/rfc1750.pdf"],"folder":"IETF/RFC-1750","files":{"txt":{"path":"standards/IETF/RFC-1750/RFC-1750.txt","sha256":"fec4c0767434a8a322d6d5d0c9f49c42988ce8c159b1a80629d51aa40c2e99aa"}},"tags":["nested-reference","unchanged"],"summary":"Security systems today are built on increasingly strong cryptographic\n algorithms that foil pattern analysis attempts. However, the security\n of these systems is dependent on generating secret quantities for\n passwords, cryptographic keys, and similar quantities. The use of\n pseudo-random processes to generate secret quantities can result in\n pseudo-security. The sophisticated attacker of these security\n systems may find it easier to reproduce the environment that produced\n the secret quantities, searching the resulting small set of\n possibilities, than to locate the quantities in the whole of the\n number space.\n\n Choosing random quantities to foil a resourceful and motivated\n adversary is surprisingly difficult. This paper points out many\n pitfalls in using traditional pseudo-random number generation\n techniques for choosing such quantities. It recommends the use of\n truly random hardwa","scope_keywords":["1750","algorithm","algorithms","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2412","folder":"IETF/RFC-2412","source":"IETF/RFC-2412/RFC-2412.txt","version":null},{"body":"IETF","designation":"RFC 2433","folder":"IETF/RFC-2433","source":"IETF/RFC-2433/RFC-2433.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2536","folder":"IETF/RFC-2536","source":"IETF/RFC-2536/RFC-2536.txt","version":null},{"body":"IETF","designation":"RFC 2541","folder":"IETF/RFC-2541","source":"IETF/RFC-2541/RFC-2541.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2777","folder":"IETF/RFC-2777","source":"IETF/RFC-2777/RFC-2777.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3174","folder":"IETF/RFC-3174","source":"IETF/RFC-3174/RFC-3174.txt","version":null},{"body":"IETF","designation":"RFC 3217","folder":"IETF/RFC-3217","source":"IETF/RFC-3217/RFC-3217.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3766","folder":"IETF/RFC-3766","source":"IETF/RFC-3766/RFC-3766.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null}],"search_text":"IETF RFC 1750 Security systems today are built on increasingly strong cryptographic\n algorithms that foil pattern analysis attempts. However, the security\n of these systems is dependent on generating secret quantities for\n passwords, cryptographic keys, and similar quantities. The use of\n pseudo-random processes to generate secret quantities can result in\n pseudo-security. The sophisticated attacker of these security\n systems may find it easier to reproduce the environment that produced\n the secret quantities, searching the resulting small set of\n possibilities, than to locate the quantities in the whole of the\n number space.\n\n Choosing random quantities to foil a resourceful and motivated\n adversary is surprisingly difficult. This paper points out many\n pitfalls in using traditional pseudo-random number generation\n techniques for choosing such quantities. It recommends the use of\n truly random hardwa 1750 algorithm algorithms key keys nested-reference unchanged"},{"id":"IETF RFC 2246","type":"specification","body":"IETF","designation":"RFC 2246","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2246.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2246.txt","https://www.rfc-editor.org/rfc/rfc2246.pdf"],"folder":"IETF/RFC-2246","files":{"txt":{"path":"standards/IETF/RFC-2246/RFC-2246.txt","sha256":"d6489dc4c87b821146724e00db9a9ed31fb317e3bd628387a8adf50e9033eea1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Version 1.0 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications privacy over\n the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery.","scope_keywords":["2246","attribute","attributes","authentication","certificate","certificates","key","keys","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2628","folder":"IETF/RFC-2628","source":"IETF/RFC-2628/RFC-2628.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2712","folder":"IETF/RFC-2712","source":"IETF/RFC-2712/RFC-2712.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3268","folder":"IETF/RFC-3268","source":"IETF/RFC-3268/RFC-3268.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3423","folder":"IETF/RFC-3423","source":"IETF/RFC-3423/RFC-3423.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4082","folder":"IETF/RFC-4082","source":"IETF/RFC-4082/RFC-4082.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4357","folder":"IETF/RFC-4357","source":"IETF/RFC-4357/RFC-4357.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4680","folder":"IETF/RFC-4680","source":"IETF/RFC-4680/RFC-4680.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5469","folder":"IETF/RFC-5469","source":"IETF/RFC-5469/RFC-5469.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7465","folder":"IETF/RFC-7465","source":"IETF/RFC-7465/RFC-7465.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 2246 This document specifies Version 1.0 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications privacy over\n the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery. 2246 attribute attributes authentication certificate certificates key keys presentation tls nested-reference unchanged"},{"id":"IETF RFC 2313","type":"specification","body":"IETF","designation":"RFC 2313","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2313.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2313.txt","https://www.rfc-editor.org/rfc/rfc2313.pdf"],"folder":"IETF/RFC-2313","files":{"txt":{"path":"standards/IETF/RFC-2313/RFC-2313.txt","sha256":"2d93e9f0f02343a29a8f64ad507e1779f65377319ed4945b6ac3dcb1f74fd69c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 2313 RSA Laboratories East\nCategory: Informational March 1998\n\n PKCS #1: RSA Encryption\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a method for encrypting data using the RSA\n public-key cryptosystem.\n\n1. Scope\n\n This document describes a method for encrypting data using the RSA\n public-key cryptosystem. Its intended use is in the construction of\n digital signatures and digital envelopes, as described in PKCS #7:\n\n o For digital signatures, the content to be signed\n is first reduced to a message digest with a\n message-digest algorithm (such as MD5), and then\n an octet str","scope_keywords":["2313","algorithm","algorithms","authentication","certificate","certificates","encryption","key","keys","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2437","folder":"IETF/RFC-2437","source":"IETF/RFC-2437/RFC-2437.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 3218","folder":"IETF/RFC-3218","source":"IETF/RFC-3218/RFC-3218.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2313 Network Working Group B. Kaliski\nRequest for Comments: 2313 RSA Laboratories East\nCategory: Informational March 1998\n\n PKCS #1: RSA Encryption\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a method for encrypting data using the RSA\n public-key cryptosystem.\n\n1. Scope\n\n This document describes a method for encrypting data using the RSA\n public-key cryptosystem. Its intended use is in the construction of\n digital signatures and digital envelopes, as described in PKCS #7:\n\n o For digital signatures, the content to be signed\n is first reduced to a message digest with a\n message-digest algorithm (such as MD5), and then\n an octet str 2313 algorithm algorithms authentication certificate certificates encryption key keys revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 2315","type":"specification","body":"IETF","designation":"RFC 2315","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2315.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2315.txt","https://www.rfc-editor.org/rfc/rfc2315.pdf"],"folder":"IETF/RFC-2315","files":{"txt":{"path":"standards/IETF/RFC-2315/RFC-2315.txt","sha256":"154610a11c76a8b499d8453c0190d4ff8ee354dd6a203f40d8252840747cb4e0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 2315 RSA Laboratories, East\nCategory: Informational March 1998\n\n PKCS #7: Cryptographic Message Syntax\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a general syntax for data that may have\n cryptography applied to it, such as digital signatures and digital\n envelopes. The syntax admits recursion, so that, for example, one\n envelope can be nested inside another, or one party can sign some\n previously enveloped digital data. It also allows arbitrary\n attributes, such as signing time, to be authenticated along with the\n content of a message, and provides for other attributes s","scope_keywords":["2315","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","crl","encryption","identification","issuer","key","management","policies","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3713","folder":"IETF/RFC-3713","source":"IETF/RFC-3713/RFC-3713.txt","version":null},{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2315 Network Working Group B. Kaliski\nRequest for Comments: 2315 RSA Laboratories, East\nCategory: Informational March 1998\n\n PKCS #7: Cryptographic Message Syntax\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a general syntax for data that may have\n cryptography applied to it, such as digital signatures and digital\n envelopes. The syntax admits recursion, so that, for example, one\n envelope can be nested inside another, or one party can sign some\n previously enveloped digital data. It also allows arbitrary\n attributes, such as signing time, to be authenticated along with the\n content of a message, and provides for other attributes s 2315 algorithm algorithms attribute attributes authentication certificate certificates crl encryption identification issuer key management policies revocation nested-reference unchanged"},{"id":"IETF RFC 2660","type":"specification","body":"IETF","designation":"RFC 2660","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2660.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2660.txt","https://www.rfc-editor.org/rfc/rfc2660.pdf"],"folder":"IETF/RFC-2660","files":{"txt":{"path":"standards/IETF/RFC-2660/RFC-2660.txt","sha256":"7f91c96e56680c8415134a067b8e06cd1dbc080565c04ca5d841e30902b4c694"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a syntax for securing messages sent using the\n Hypertext Transfer Protocol (HTTP), which forms the basis for the\n World Wide Web. Secure HTTP (S-HTTP) provides independently\n applicable security services for transaction confidentiality,\n authenticity/integrity and non-repudiability of origin.\n\n The protocol emphasizes maximum flexibility in choice of key\n management mechanisms, security policies and cryptographic algorithms\n by supporting option negotiation between parties for each\n transaction.","scope_keywords":["2660","algorithm","algorithms","authentication","certificate","encryption","http","key","management","policies","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2659","folder":"IETF/RFC-2659","source":"IETF/RFC-2659/RFC-2659.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null}],"search_text":"IETF RFC 2660 This memo describes a syntax for securing messages sent using the\n Hypertext Transfer Protocol (HTTP), which forms the basis for the\n World Wide Web. Secure HTTP (S-HTTP) provides independently\n applicable security services for transaction confidentiality,\n authenticity/integrity and non-repudiability of origin.\n\n The protocol emphasizes maximum flexibility in choice of key\n management mechanisms, security policies and cryptographic algorithms\n by supporting option negotiation between parties for each\n transaction. 2660 algorithm algorithms authentication certificate encryption http key management policies presentation trust nested-reference unchanged"},{"id":"IETF RFC 2898","type":"specification","body":"IETF","designation":"RFC 2898","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2898.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2898.txt","https://www.rfc-editor.org/rfc/rfc2898.pdf"],"folder":"IETF/RFC-2898","files":{"txt":{"path":"standards/IETF/RFC-2898/RFC-2898.txt","sha256":"9b40d3027d7f49649bb8a3a55dbf49e41fe28c8c56b0db28b39f0fa55fb41f99"}},"tags":["nested-reference","unchanged"],"summary":"This memo represents a republication of PKCS #5 v2.0 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from that specification.\n\n This document provides recommendations for the implementation of\n password-based cryptography, covering key derivation functions,\n encryption schemes, message-authentication schemes, and ASN.1 syntax\n identifying the techniques.\n\n The recommendations are intended for general application within\n computer and communications systems, and as such include a fair\n amount of flexibility. They are particularly intended for the\n protection of sensitive information such as private keys, as in PKCS\n #8 [25]. It is expected that application standards and implementation\n profiles based on these specif","scope_keywords":["2898","authentication","encryption","hash","key","keys","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3211","folder":"IETF/RFC-3211","source":"IETF/RFC-3211/RFC-3211.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3962","folder":"IETF/RFC-3962","source":"IETF/RFC-3962/RFC-3962.txt","version":null},{"body":"IETF","designation":"RFC 4009","folder":"IETF/RFC-4009","source":"IETF/RFC-4009/RFC-4009.txt","version":null},{"body":"IETF","designation":"RFC 4269","folder":"IETF/RFC-4269","source":"IETF/RFC-4269/RFC-4269.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"IETF RFC 2898 This memo represents a republication of PKCS #5 v2.0 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from that specification.\n\n This document provides recommendations for the implementation of\n password-based cryptography, covering key derivation functions,\n encryption schemes, message-authentication schemes, and ASN.1 syntax\n identifying the techniques.\n\n The recommendations are intended for general application within\n computer and communications systems, and as such include a fair\n amount of flexibility. They are particularly intended for the\n protection of sensitive information such as private keys, as in PKCS\n #8 [25]. It is expected that application standards and implementation\n profiles based on these specif 2898 authentication encryption hash key keys profile profiles nested-reference unchanged"},{"id":"IETF RFC 4572","type":"specification","body":"IETF","designation":"RFC 4572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4572.txt","https://www.rfc-editor.org/rfc/rfc4572.pdf"],"folder":"IETF/RFC-4572","files":{"txt":{"path":"standards/IETF/RFC-4572/RFC-4572.txt","sha256":"0560257effa4b6cdb8424ef621afe6d3995428de7b2509f0965101105766c84a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to establish secure connection-oriented\n media transport sessions over the Transport Layer Security (TLS)\n protocol using the Session Description Protocol (SDP). It defines a\n new SDP protocol identifier, 'TCP/TLS'. It also defines the syntax\n and semantics for an SDP 'fingerprint' attribute that identifies the\n certificate that will be presented for the TLS session. This\n mechanism allows media transport over TLS connections to be\n established securely, so long as the integrity of session\n descriptions is assured.\n\n This document extends and updates RFC 4145.\n\nLennox Standards Track [Page 1]\n\f\nRFC 4572 Comedia over TLS in SDP July 2006","scope_keywords":["4572","attribute","authentication","certificate","certificates","hash","identification","key","presentation","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4572 This document specifies how to establish secure connection-oriented\n media transport sessions over the Transport Layer Security (TLS)\n protocol using the Session Description Protocol (SDP). It defines a\n new SDP protocol identifier, 'TCP/TLS'. It also defines the syntax\n and semantics for an SDP 'fingerprint' attribute that identifies the\n certificate that will be presented for the TLS session. This\n mechanism allows media transport over TLS connections to be\n established securely, so long as the integrity of session\n descriptions is assured.\n\n This document extends and updates RFC 4145.\n\nLennox Standards Track [Page 1]\n\f\nRFC 4572 Comedia over TLS in SDP July 2006 4572 attribute authentication certificate certificates hash identification key presentation tls trust nested-reference unchanged"},{"id":"IETF RFC 6149","type":"specification","body":"IETF","designation":"RFC 6149","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6149.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6149.txt","https://www.rfc-editor.org/rfc/rfc6149.pdf"],"folder":"IETF/RFC-6149","files":{"txt":{"path":"standards/IETF/RFC-6149/RFC-6149.txt","sha256":"061cd943c018fe152961015dd0edf9875ed1fd4e652fbca967d134c37e83a950"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) S. Turner\nRequest for Comments: 6149 IECA\nObsoletes: 1319 L. Chen\nCategory: Informational NIST\nISSN: 2070-1721 March 2011\n\n MD2 to Historic Status\n\nAbstract\n\n This document retires MD2 and discusses the reasons for doing so.\n This document moves RFC 1319 to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov","scope_keywords":["6149","algorithm","algorithms","authentication","certificate","crl","encryption","hash","http","key","keys","license","pki","profile","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null}],"search_text":"IETF RFC 6149 Internet Engineering Task Force (IETF) S. Turner\nRequest for Comments: 6149 IECA\nObsoletes: 1319 L. Chen\nCategory: Informational NIST\nISSN: 2070-1721 March 2011\n\n MD2 to Historic Status\n\nAbstract\n\n This document retires MD2 and discusses the reasons for doing so.\n This document moves RFC 1319 to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov 6149 algorithm algorithms authentication certificate crl encryption hash http key keys license pki profile revocation subject nested-reference unchanged"},{"id":"IETF RFC 8018","type":"specification","body":"IETF","designation":"RFC 8018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8018.txt","https://www.rfc-editor.org/rfc/rfc8018.pdf"],"folder":"IETF/RFC-8018","files":{"txt":{"path":"standards/IETF/RFC-8018/RFC-8018.txt","sha256":"cf96b02e68216f618ea33b20b49d476edba9d70f2333597ec516629d22971cda"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations for the implementation of\n password-based cryptography, covering key derivation functions,\n encryption schemes, message authentication schemes, and ASN.1 syntax\n identifying the techniques.\n\n This document represents a republication of PKCS #5 v2.1 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\n This document also obsoletes RFC 2898.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a can","scope_keywords":["8018","authentication","encryption","hash","http","key","keys","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 8018 This document provides recommendations for the implementation of\n password-based cryptography, covering key derivation functions,\n encryption schemes, message authentication schemes, and ASN.1 syntax\n identifying the techniques.\n\n This document represents a republication of PKCS #5 v2.1 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\n This document also obsoletes RFC 2898.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a can 8018 authentication encryption hash http key keys license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 1321","type":"specification","body":"IETF","designation":"RFC 1321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1321.txt","https://www.rfc-editor.org/rfc/rfc1321.pdf"],"folder":"IETF/RFC-1321","files":{"txt":{"path":"standards/IETF/RFC-1321/RFC-1321.txt","sha256":"284a79d148400d9cd2a423211d1103b5cef0fb9256a4cbe6d7ebe5197c3149dd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Rivest\nRequest for Comments: 1321 MIT Laboratory for Computer Science\n and RSA Data Security, Inc.\n April 1992\n\n The MD5 Message-Digest Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n We would like to thank Don Coppersmith, Burt Kaliski, Ralph Merkle,\n David Chaum, and Noam Nisan for numerous helpful comments and\n suggestions.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD5 Algorithm Description 3\n 4. Summary 6\n 5. Differences Between MD4 and MD5 6\n References 7\n APPENDIX A - Reference Implementation 7\n Security Considerations 21\n Author's Address 21\n\n1. Executive Summary\n\n This document describes the MD5 message-digest algorithm. The\n algorithm takes as input a message of arbitrary l","scope_keywords":["1321","algorithm","key","presentation","risk","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 1320","folder":"IETF/RFC-1320","source":"IETF/RFC-1320/RFC-1320.txt","version":null},{"body":"IETF","designation":"RFC 1334","folder":"IETF/RFC-1334","source":"IETF/RFC-1334/RFC-1334.txt","version":null},{"body":"IETF","designation":"RFC 1352","folder":"IETF/RFC-1352","source":"IETF/RFC-1352/RFC-1352.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1460","folder":"IETF/RFC-1460","source":"IETF/RFC-1460/RFC-1460.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 1510","folder":"IETF/RFC-1510","source":"IETF/RFC-1510/RFC-1510.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1725","folder":"IETF/RFC-1725","source":"IETF/RFC-1725/RFC-1725.txt","version":null},{"body":"IETF","designation":"RFC 1750","folder":"IETF/RFC-1750","source":"IETF/RFC-1750/RFC-1750.txt","version":null},{"body":"IETF","designation":"RFC 1810","folder":"IETF/RFC-1810","source":"IETF/RFC-1810/RFC-1810.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 1864","folder":"IETF/RFC-1864","source":"IETF/RFC-1864/RFC-1864.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1910","folder":"IETF/RFC-1910","source":"IETF/RFC-1910/RFC-1910.txt","version":null},{"body":"IETF","designation":"RFC 1938","folder":"IETF/RFC-1938","source":"IETF/RFC-1938/RFC-1938.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 1964","folder":"IETF/RFC-1964","source":"IETF/RFC-1964/RFC-1964.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1994","folder":"IETF/RFC-1994","source":"IETF/RFC-1994/RFC-1994.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2040","folder":"IETF/RFC-2040","source":"IETF/RFC-2040/RFC-2040.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2059","folder":"IETF/RFC-2059","source":"IETF/RFC-2059/RFC-2059.txt","version":null},{"body":"IETF","designation":"RFC 2065","folder":"IETF/RFC-2065","source":"IETF/RFC-2065/RFC-2065.txt","version":null},{"body":"IETF","designation":"RFC 2069","folder":"IETF/RFC-2069","source":"IETF/RFC-2069/RFC-2069.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2085","folder":"IETF/RFC-2085","source":"IETF/RFC-2085/RFC-2085.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2104","folder":"IETF/RFC-2104","source":"IETF/RFC-2104/RFC-2104.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2139","folder":"IETF/RFC-2139","source":"IETF/RFC-2139/RFC-2139.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2202","folder":"IETF/RFC-2202","source":"IETF/RFC-2202/RFC-2202.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2286","folder":"IETF/RFC-2286","source":"IETF/RFC-2286/RFC-2286.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2313","folder":"IETF/RFC-2313","source":"IETF/RFC-2313/RFC-2313.txt","version":null},{"body":"IETF","designation":"RFC 2315","folder":"IETF/RFC-2315","source":"IETF/RFC-2315/RFC-2315.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2385","folder":"IETF/RFC-2385","source":"IETF/RFC-2385/RFC-2385.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2437","folder":"IETF/RFC-2437","source":"IETF/RFC-2437/RFC-2437.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2762","folder":"IETF/RFC-2762","source":"IETF/RFC-2762/RFC-2762.txt","version":null},{"body":"IETF","designation":"RFC 2777","folder":"IETF/RFC-2777","source":"IETF/RFC-2777/RFC-2777.txt","version":null},{"body":"IETF","designation":"RFC 2792","folder":"IETF/RFC-2792","source":"IETF/RFC-2792/RFC-2792.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2803","folder":"IETF/RFC-2803","source":"IETF/RFC-2803/RFC-2803.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 2945","folder":"IETF/RFC-2945","source":"IETF/RFC-2945/RFC-2945.txt","version":null},{"body":"IETF","designation":"RFC 2961","folder":"IETF/RFC-2961","source":"IETF/RFC-2961/RFC-2961.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3174","folder":"IETF/RFC-3174","source":"IETF/RFC-3174/RFC-3174.txt","version":null},{"body":"IETF","designation":"RFC 3188","folder":"IETF/RFC-3188","source":"IETF/RFC-3188/RFC-3188.txt","version":null},{"body":"IETF","designation":"RFC 3208","folder":"IETF/RFC-3208","source":"IETF/RFC-3208/RFC-3208.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3224","folder":"IETF/RFC-3224","source":"IETF/RFC-3224/RFC-3224.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 3967","folder":"IETF/RFC-3967","source":"IETF/RFC-3967/RFC-3967.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 1321 Network Working Group R. Rivest\nRequest for Comments: 1321 MIT Laboratory for Computer Science\n and RSA Data Security, Inc.\n April 1992\n\n The MD5 Message-Digest Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAcknowlegements\n\n We would like to thank Don Coppersmith, Burt Kaliski, Ralph Merkle,\n David Chaum, and Noam Nisan for numerous helpful comments and\n suggestions.\n\nTable of Contents\n\n 1. Executive Summary 1\n 2. Terminology and Notation 2\n 3. MD5 Algorithm Description 3\n 4. Summary 6\n 5. Differences Between MD4 and MD5 6\n References 7\n APPENDIX A - Reference Implementation 7\n Security Considerations 21\n Author's Address 21\n\n1. Executive Summary\n\n This document describes the MD5 message-digest algorithm. The\n algorithm takes as input a message of arbitrary l 1321 algorithm key presentation risk signature nested-reference unchanged"},{"id":"IETF RFC 1510","type":"specification","body":"IETF","designation":"RFC 1510","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1510.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1510.txt","https://www.rfc-editor.org/rfc/rfc1510.pdf"],"folder":"IETF/RFC-1510","files":{"txt":{"path":"standards/IETF/RFC-1510/RFC-1510.txt","sha256":"6908378c22982cfbe8279ad5a4a59a165748f5fab77b2d9a6bef102660e99d72"}},"tags":["nested-reference","unchanged"],"summary":"This document gives an overview and specification of Version 5 of the\n protocol for the Kerberos network authentication system. Version 4,\n described elsewhere [1,2], is presently in production use at MIT's\n Project Athena, and at other Internet sites.\n\nOverview\n\n Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos,\n Moira, and Zephyr are trademarks of the Massachusetts Institute of\n Technology (MIT). No commercial use of these trademarks may be made\n without prior written permission of MIT.\n\n This RFC describes the concepts and model upon which the Kerberos\n network authentication system is based. It also specifies Version 5\n of the Kerberos protocol.\n\n The motivations, goals, assumptions, and rationale behind most design\n decisions are treated cursorily; for Version 4 they are fully\n described in the Kerberos portion of the Athena Technical Plan [1].\n The protocols are under","scope_keywords":["1510","authentication","encryption","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1964","folder":"IETF/RFC-1964","source":"IETF/RFC-1964/RFC-1964.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2230","folder":"IETF/RFC-2230","source":"IETF/RFC-2230/RFC-2230.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2712","folder":"IETF/RFC-2712","source":"IETF/RFC-2712/RFC-2712.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3129","folder":"IETF/RFC-3129","source":"IETF/RFC-3129/RFC-3129.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null}],"search_text":"IETF RFC 1510 This document gives an overview and specification of Version 5 of the\n protocol for the Kerberos network authentication system. Version 4,\n described elsewhere [1,2], is presently in production use at MIT's\n Project Athena, and at other Internet sites.\n\nOverview\n\n Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos,\n Moira, and Zephyr are trademarks of the Massachusetts Institute of\n Technology (MIT). No commercial use of these trademarks may be made\n without prior written permission of MIT.\n\n This RFC describes the concepts and model upon which the Kerberos\n network authentication system is based. It also specifies Version 5\n of the Kerberos protocol.\n\n The motivations, goals, assumptions, and rationale behind most design\n decisions are treated cursorily; for Version 4 they are fully\n described in the Kerberos portion of the Athena Technical Plan [1].\n The protocols are under 1510 authentication encryption key presentation trust nested-reference unchanged"},{"id":"IETF RFC 1760","type":"specification","body":"IETF","designation":"RFC 1760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1760.txt","https://www.rfc-editor.org/rfc/rfc1760.pdf"],"folder":"IETF/RFC-1760","files":{"txt":{"path":"standards/IETF/RFC-1760/RFC-1760.txt","sha256":"47b3a2859d0d8a3c014dfff807bac4b8651e0aebecf62504818964892197b9af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the S/KEY* One-Time Password system as\n released for public use by Bellcore and as described in reference\n [3]. A reference implementation and documentation are available by\n anonymous ftp from ftp.bellcore.com in the directories pub/nmh/...\n\nOverview\n\n One form of attack on computing system connected to the Internet is\n eavesdropping on network connections to obtain login id's and\n passwords of legitimate users. The captured login id and password\n are, at a later time, used gain access to the system. The S/KEY\n One-Time Password system is designed to counter this type of attack,\n called a replay attack.\n\n With the S/KEY system, only a single use password ever crosses the\n network. The user's secret pass-phrase never crosses the network at\n any time, including during login or when executing other commands\n requiring authentication such as the UNIX commands passwd ","scope_keywords":["1760","algorithm","authentication","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1938","folder":"IETF/RFC-1938","source":"IETF/RFC-1938/RFC-1938.txt","version":null},{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2289","folder":"IETF/RFC-2289","source":"IETF/RFC-2289/RFC-2289.txt","version":null},{"body":"IETF","designation":"RFC 2945","folder":"IETF/RFC-2945","source":"IETF/RFC-2945/RFC-2945.txt","version":null},{"body":"IETF","designation":"RFC 4082","folder":"IETF/RFC-4082","source":"IETF/RFC-4082/RFC-4082.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 1760 This document describes the S/KEY* One-Time Password system as\n released for public use by Bellcore and as described in reference\n [3]. A reference implementation and documentation are available by\n anonymous ftp from ftp.bellcore.com in the directories pub/nmh/...\n\nOverview\n\n One form of attack on computing system connected to the Internet is\n eavesdropping on network connections to obtain login id's and\n passwords of legitimate users. The captured login id and password\n are, at a later time, used gain access to the system. The S/KEY\n One-Time Password system is designed to counter this type of attack,\n called a replay attack.\n\n With the S/KEY system, only a single use password ever crosses the\n network. The user's secret pass-phrase never crosses the network at\n any time, including during login or when executing other commands\n requiring authentication such as the UNIX commands passwd  1760 algorithm authentication hash key nested-reference unchanged"},{"id":"IETF RFC 1938","type":"specification","body":"IETF","designation":"RFC 1938","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1938.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1938.txt","https://www.rfc-editor.org/rfc/rfc1938.pdf"],"folder":"IETF/RFC-1938","files":{"txt":{"path":"standards/IETF/RFC-1938/RFC-1938.txt","sha256":"eca05a2043a5cb812ab000faa4d9a7c38aac9e8e374cf1ee4e67704a093dfbb3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a one-time password authentication system\n (OTP). The system provides authentication for system access (login)\n and other applications requiring authentication that is secure\n against passive attacks based on replaying captured reusable\n passwords. OTP evolved from the S/KEY (S/KEY is a trademark of\n Bellcore) One-Time Password System that was released by Bellcore and\n is described in references [3] and [5].","scope_keywords":["1938","algorithm","algorithms","authentication","hash","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2243","folder":"IETF/RFC-2243","source":"IETF/RFC-2243/RFC-2243.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null}],"search_text":"IETF RFC 1938 This document describes a one-time password authentication system\n (OTP). The system provides authentication for system access (login)\n and other applications requiring authentication that is secure\n against passive attacks based on replaying captured reusable\n passwords. OTP evolved from the S/KEY (S/KEY is a trademark of\n Bellcore) One-Time Password System that was released by Bellcore and\n is described in references [3] and [5]. 1938 algorithm algorithms authentication hash key risk nested-reference unchanged"},{"id":"IETF RFC 2289","type":"specification","body":"IETF","designation":"RFC 2289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2289.txt","https://www.rfc-editor.org/rfc/rfc2289.pdf"],"folder":"IETF/RFC-2289","files":{"txt":{"path":"standards/IETF/RFC-2289/RFC-2289.txt","sha256":"17e44129dce720bad390b39e0e41bfeca6963f83aaea7af97b56afd6153513b0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a one-time password authentication system\n (OTP). The system provides authentication for system access (login)\n and other applications requiring authentication that is secure\n against passive attacks based on replaying captured reusable\n passwords. OTP evolved from the S/KEY (S/KEY is a trademark of\n Bellcore) One-Time Password System that was released by Bellcore and\n is described in references [3] and [5].","scope_keywords":["2289","algorithm","algorithms","authentication","hash","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 2289 This document describes a one-time password authentication system\n (OTP). The system provides authentication for system access (login)\n and other applications requiring authentication that is secure\n against passive attacks based on replaying captured reusable\n passwords. OTP evolved from the S/KEY (S/KEY is a trademark of\n Bellcore) One-Time Password System that was released by Bellcore and\n is described in references [3] and [5]. 2289 algorithm algorithms authentication hash key risk nested-reference unchanged"},{"id":"IETF RFC 2433","type":"specification","body":"IETF","designation":"RFC 2433","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2433.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2433.txt","https://www.rfc-editor.org/rfc/rfc2433.pdf"],"folder":"IETF/RFC-2433","files":{"txt":{"path":"standards/IETF/RFC-2433/RFC-2433.txt","sha256":"7ed235c2f3832b11c033ba15bb3088002c63cc5b9a91defebc7d223e36ad753b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Zorn\nRequest for Comments: 2433 S. Cobb\nCategory: Informational Microsoft Corporation\n October 1998\n\n Microsoft PPP CHAP Extensions\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG Note\n\n The protocol described here has significant vulnerabilities. People\n planning on implementing or using this protocol should read section\n 12, \"Security Considerations\".\n\n1. Abstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n networ","scope_keywords":["2433","algorithm","algorithms","authentication","credential","credentials","encryption","hash","hashing","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2433 Network Working Group G. Zorn\nRequest for Comments: 2433 S. Cobb\nCategory: Informational Microsoft Corporation\n October 1998\n\n Microsoft PPP CHAP Extensions\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG Note\n\n The protocol described here has significant vulnerabilities. People\n planning on implementing or using this protocol should read section\n 12, \"Security Considerations\".\n\n1. Abstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n networ 2433 algorithm algorithms authentication credential credentials encryption hash hashing key presentation nested-reference unchanged"},{"id":"IETF RFC 2759","type":"specification","body":"IETF","designation":"RFC 2759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2759.txt","https://www.rfc-editor.org/rfc/rfc2759.pdf"],"folder":"IETF/RFC-2759","files":{"txt":{"path":"standards/IETF/RFC-2759/RFC-2759.txt","sha256":"38cffead32c3b32ff3616c2fce922ca573daaeffbbe4ae0933247eb5802fa1d0"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n network-layer protocols.\n\n This document describes version two of Microsoft's PPP CHAP dialect\n (MS-CHAP-V2). MS-CHAP-V2 is similar to, but incompatible with, MS-\n CHAP version one (MS-CHAP-V1, described in [9]). In particular,\n certain protocol fields have been deleted or reused but with\n different semantics. In addition, MS-CHAP-V2 features mutual\n authentication.\n\n The algorithms used in the generation of various MS-CHAP-V2 protocol\n fields are described in section 8. Negotiation and hash generation\n examples are provided in section 9.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST","scope_keywords":["2759","algorithm","algorithms","authentication","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null}],"search_text":"IETF RFC 2759 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol and a family of Network\n Control Protocols (NCPs) for establishing and configuring different\n network-layer protocols.\n\n This document describes version two of Microsoft's PPP CHAP dialect\n (MS-CHAP-V2). MS-CHAP-V2 is similar to, but incompatible with, MS-\n CHAP version one (MS-CHAP-V1, described in [9]). In particular,\n certain protocol fields have been deleted or reused but with\n different semantics. In addition, MS-CHAP-V2 features mutual\n authentication.\n\n The algorithms used in the generation of various MS-CHAP-V2 protocol\n fields are described in section 8. Negotiation and hash generation\n examples are provided in section 9.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST 2759 algorithm algorithms authentication hash key nested-reference unchanged"},{"id":"IETF RFC 3174","type":"specification","body":"IETF","designation":"RFC 3174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3174.txt","https://www.rfc-editor.org/rfc/rfc3174.pdf"],"folder":"IETF/RFC-3174","files":{"txt":{"path":"standards/IETF/RFC-3174/RFC-3174.txt","sha256":"aa0ca4ef21609e64897980488c5555109266c29cd814fe97680c916566d29332"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to make the SHA-1 (Secure Hash\n Algorithm 1) hash algorithm conveniently available to the Internet\n community. The United States of America has adopted the SHA-1 hash\n algorithm described herein as a Federal Information Processing\n Standard. Most of the text herein was taken by the authors from FIPS\n 180-1. Only the C code implementation is \"original\".\n\nAcknowledgements\n\n Most of the text herein was taken from [FIPS 180-1]. Only the C code\n implementation is \"original\" but its style is similar to the\n previously published MD4 and MD5 RFCs [RFCs 1320, 1321].\n\n The SHA-1 is based on principles similar to those used by Professor\n Ronald L. Rivest of MIT when designing the MD4 message digest\n algorithm [MD4] and is modeled after that algorithm [RFC 1320].\n\n Useful comments from the following, which have been incorporated\n herein, are gratefully acknowledged:\n\n","scope_keywords":["3174","algorithm","hash","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4270","folder":"IETF/RFC-4270","source":"IETF/RFC-4270/RFC-4270.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null}],"search_text":"IETF RFC 3174 The purpose of this document is to make the SHA-1 (Secure Hash\n Algorithm 1) hash algorithm conveniently available to the Internet\n community. The United States of America has adopted the SHA-1 hash\n algorithm described herein as a Federal Information Processing\n Standard. Most of the text herein was taken by the authors from FIPS\n 180-1. Only the C code implementation is \"original\".\n\nAcknowledgements\n\n Most of the text herein was taken from [FIPS 180-1]. Only the C code\n implementation is \"original\" but its style is similar to the\n previously published MD4 and MD5 RFCs [RFCs 1320, 1321].\n\n The SHA-1 is based on principles similar to those used by Professor\n Ronald L. Rivest of MIT when designing the MD4 message digest\n algorithm [MD4] and is modeled after that algorithm [RFC 1320].\n\n Useful comments from the following, which have been incorporated\n herein, are gratefully acknowledged:\n\n 3174 algorithm hash presentation signature nested-reference unchanged"},{"id":"IETF RFC 3961","type":"specification","body":"IETF","designation":"RFC 3961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3961.txt","https://www.rfc-editor.org/rfc/rfc3961.pdf"],"folder":"IETF/RFC-3961","files":{"txt":{"path":"standards/IETF/RFC-3961/RFC-3961.txt","sha256":"1c4d7facc88d6d6d9fa4b2d0b92366e37c8f506455c545762a76fd83ecc7c970"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for defining encryption and\n checksum mechanisms for use with the Kerberos protocol, defining an\n abstraction layer between the Kerberos protocol and related\n protocols, and the actual mechanisms themselves. The document also\n defines several mechanisms. Some are taken from RFC 1510, modified\n in form to fit this new framework and occasionally modified in\n content when the old specification was incorrect. New mechanisms are\n presented here as well. This document does NOT indicate which\n mechanisms may be considered \"required to implement\".","scope_keywords":["3961","algorithm","algorithms","attribute","attributes","encryption","hash","key","keys","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3962","folder":"IETF/RFC-3962","source":"IETF/RFC-3962/RFC-3962.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null}],"search_text":"IETF RFC 3961 This document describes a framework for defining encryption and\n checksum mechanisms for use with the Kerberos protocol, defining an\n abstraction layer between the Kerberos protocol and related\n protocols, and the actual mechanisms themselves. The document also\n defines several mechanisms. Some are taken from RFC 1510, modified\n in form to fit this new framework and occasionally modified in\n content when the old specification was incorrect. New mechanisms are\n presented here as well. This document does NOT indicate which\n mechanisms may be considered \"required to implement\". 3961 algorithm algorithms attribute attributes encryption hash key keys profile profiles nested-reference unchanged"},{"id":"IETF RFC 4757","type":"specification","body":"IETF","designation":"RFC 4757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4757.txt","https://www.rfc-editor.org/rfc/rfc4757.pdf"],"folder":"IETF/RFC-4757","files":{"txt":{"path":"standards/IETF/RFC-4757/RFC-4757.txt","sha256":"4a1d25794f68f4016c3225d0a5d309ca1e154558d76d0aed8fe830333f484b13"}},"tags":["nested-reference","unchanged"],"summary":"The Microsoft Windows 2000 implementation of Kerberos introduces a\n new encryption type based on the RC4 encryption algorithm and using\n an MD5 HMAC for checksum. This is offered as an alternative to using\n the existing DES-based encryption types.\n\n The RC4-HMAC encryption types are used to ease upgrade of existing\n Windows NT environments, provide strong cryptography (128-bit key\n lengths), and provide exportable (meet United States government\n export restriction requirements) encryption. This document describes\n the implementation of those encryption types.","scope_keywords":["4757","algorithm","encryption","hash","key","keys","license","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null}],"search_text":"IETF RFC 4757 The Microsoft Windows 2000 implementation of Kerberos introduces a\n new encryption type based on the RC4 encryption algorithm and using\n an MD5 HMAC for checksum. This is offered as an alternative to using\n the existing DES-based encryption types.\n\n The RC4-HMAC encryption types are used to ease upgrade of existing\n Windows NT environments, provide strong cryptography (128-bit key\n lengths), and provide exportable (meet United States government\n export restriction requirements) encryption. This document describes\n the implementation of those encryption types. 4757 algorithm encryption hash key keys license timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6150","type":"specification","body":"IETF","designation":"RFC 6150","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6150.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6150.txt","https://www.rfc-editor.org/rfc/rfc6150.pdf"],"folder":"IETF/RFC-6150","files":{"txt":{"path":"standards/IETF/RFC-6150/RFC-6150.txt","sha256":"cdbf326c9bf4bfe7885b823de5606c752b405682819be32d6d0deca6a483aa1e"}},"tags":["nested-reference","unchanged"],"summary":"This document retires RFC 1320, which documents the MD4 algorithm,\n and discusses the reasons for doing so. This document moves RFC 1320\n to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6150.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified ","scope_keywords":["6150","algorithm","authentication","encryption","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null}],"search_text":"IETF RFC 6150 This document retires RFC 1320, which documents the MD4 algorithm,\n and discusses the reasons for doing so. This document moves RFC 1320\n to Historic status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6150.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified  6150 algorithm authentication encryption hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 1725","type":"specification","body":"IETF","designation":"RFC 1725","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1725.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1725.txt","https://www.rfc-editor.org/rfc/rfc1725.pdf"],"folder":"IETF/RFC-1725","files":{"txt":{"path":"standards/IETF/RFC-1725/RFC-1725.txt","sha256":"ae149b131d9f5b44424b2561f2acb4540e121b24090a538cc02b56e6abe8155d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 1725 Carnegie Mellon\nObsoletes: 1460 M. Rose\nCategory: Standards Track Dover Beach Consulting, Inc.\n November 1994\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nOverview\n\n This memo is a revision to RFC 1460, a Draft Standard. It makes the\n following changes from that document:\n\n - removed text regarding \"split-UA model\", which didn't add\n anything to the understanding of POP\n\n - clarified syntax of commands, keywords, and arguments\n\n - clarified behavior on broken connection\n\n - explicitl","scope_keywords":["1725","authentication","authorization","crl","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1725 Network Working Group J. Myers\nRequest for Comments: 1725 Carnegie Mellon\nObsoletes: 1460 M. Rose\nCategory: Standards Track Dover Beach Consulting, Inc.\n November 1994\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nOverview\n\n This memo is a revision to RFC 1460, a Draft Standard. It makes the\n following changes from that document:\n\n - removed text regarding \"split-UA model\", which didn't add\n anything to the understanding of POP\n\n - clarified syntax of commands, keywords, and arguments\n\n - clarified behavior on broken connection\n\n - explicitl 1725 authentication authorization crl delivery key nested-reference unchanged"},{"id":"IETF RFC 1810","type":"specification","body":"IETF","designation":"RFC 1810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1810.txt","https://www.rfc-editor.org/rfc/rfc1810.pdf"],"folder":"IETF/RFC-1810","files":{"txt":{"path":"standards/IETF/RFC-1810/RFC-1810.txt","sha256":"633a876676a5a6316d7e034e6538623416e72aa05067d0df8f57c62977b34fe1"}},"tags":["nested-reference","unchanged"],"summary":"MD5 is an authentication algorithm, which has been proposed as the\n default authentication option in IPv6. When enabled, the MD5\n algorithm operates over the entire data packet, including header.\n This RFC addresses how fast MD5 can be implemented in software and\n hardware, and whether it supports currently available IP bandwidth.\n MD5 can be implemented in existing hardware technology at 256 Mbps,\n and in software at 87 Mbps. These rates cannot support current IP\n rates, e.g., 100 Mbps TCP and 130 Mbps UDP over ATM. If MD5 cannot\n support existing network bandwidth using existing technology, it will\n not scale as network speeds increase in the future. This RFC is\n intended to alert the IP community about the performance limitations\n of MD5, and to suggest that alternatives be considered for use in\n high speed IP implementations.","scope_keywords":["1810","algorithm","authentication","hash","hashing"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1828","folder":"IETF/RFC-1828","source":"IETF/RFC-1828/RFC-1828.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3607","folder":"IETF/RFC-3607","source":"IETF/RFC-3607/RFC-3607.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null}],"search_text":"IETF RFC 1810 MD5 is an authentication algorithm, which has been proposed as the\n default authentication option in IPv6. When enabled, the MD5\n algorithm operates over the entire data packet, including header.\n This RFC addresses how fast MD5 can be implemented in software and\n hardware, and whether it supports currently available IP bandwidth.\n MD5 can be implemented in existing hardware technology at 256 Mbps,\n and in software at 87 Mbps. These rates cannot support current IP\n rates, e.g., 100 Mbps TCP and 130 Mbps UDP over ATM. If MD5 cannot\n support existing network bandwidth using existing technology, it will\n not scale as network speeds increase in the future. This RFC is\n intended to alert the IP community about the performance limitations\n of MD5, and to suggest that alternatives be considered for use in\n high speed IP implementations. 1810 algorithm authentication hash hashing nested-reference unchanged"},{"id":"IETF RFC 1828","type":"specification","body":"IETF","designation":"RFC 1828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1828.txt","https://www.rfc-editor.org/rfc/rfc1828.pdf"],"folder":"IETF/RFC-1828","files":{"txt":{"path":"standards/IETF/RFC-1828/RFC-1828.txt","sha256":"c317629b990c912ac8290979b4ed30e4dd3e5a8b51fadb6c37da7ef7496de611"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of keyed MD5 with the IP\n Authentication Header.","scope_keywords":["1828","algorithm","algorithms","authentication","hash","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 2085","folder":"IETF/RFC-2085","source":"IETF/RFC-2085/RFC-2085.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1828 This document describes the use of keyed MD5 with the IP\n Authentication Header. 1828 algorithm algorithms authentication hash key keys management nested-reference unchanged"},{"id":"IETF RFC 1864","type":"specification","body":"IETF","designation":"RFC 1864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1864.txt","https://www.rfc-editor.org/rfc/rfc1864.pdf"],"folder":"IETF/RFC-1864","files":{"txt":{"path":"standards/IETF/RFC-1864/RFC-1864.txt","sha256":"6d13d493caeafb268d79b8a9dc7c443dbe6df1fb439ac8eb72184927f952a887"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies an optional header field, Content-MD5, for use\n with MIME-conformant messages.","scope_keywords":["1864","algorithm","authentication","delivery","encryption"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2069","folder":"IETF/RFC-2069","source":"IETF/RFC-2069/RFC-2069.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 1864 This memo specifies an optional header field, Content-MD5, for use\n with MIME-conformant messages. 1864 algorithm authentication delivery encryption nested-reference unchanged"},{"id":"IETF RFC 1939","type":"specification","body":"IETF","designation":"RFC 1939","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1939.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1939.txt","https://www.rfc-editor.org/rfc/rfc1939.pdf"],"folder":"IETF/RFC-1939","files":{"txt":{"path":"standards/IETF/RFC-1939/RFC-1939.txt","sha256":"1c02e8a3208e33416807597629dfab693354359563d4ae1a9b242374e05886c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 1939 Carnegie Mellon\nSTD: 53 M. Rose\nObsoletes: 1725 Dover Beach Consulting, Inc.\nCategory: Standards Track May 1996\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. A Short Digression .......................................... 2\n 3. Basic Operation ............................................. 3\n 4. The AUTHORIZATION State ..................................... 4\n QUIT Command ..........................","scope_keywords":["1939","authorization","crl","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3206","folder":"IETF/RFC-3206","source":"IETF/RFC-3206/RFC-3206.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4686","folder":"IETF/RFC-4686","source":"IETF/RFC-4686/RFC-4686.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 1939 Network Working Group J. Myers\nRequest for Comments: 1939 Carnegie Mellon\nSTD: 53 M. Rose\nObsoletes: 1725 Dover Beach Consulting, Inc.\nCategory: Standards Track May 1996\n\n Post Office Protocol - Version 3\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. A Short Digression .......................................... 2\n 3. Basic Operation ............................................. 3\n 4. The AUTHORIZATION State ..................................... 4\n QUIT Command .......................... 1939 authorization crl delivery key nested-reference unchanged"},{"id":"IETF RFC 1948","type":"specification","body":"IETF","designation":"RFC 1948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1948.txt","https://www.rfc-editor.org/rfc/rfc1948.pdf"],"folder":"IETF/RFC-1948","files":{"txt":{"path":"standards/IETF/RFC-1948/RFC-1948.txt","sha256":"0d7bab2e6c7449a22d4951cfdba3c30d4e632f766deaf618edb919e3436b654f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bellovin\nRequest for Comments: 1948 AT&T Research\nCategory: Informational May 1996\n\n Defending Against Sequence Number Attacks\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n IP spoofing attacks based on sequence number spoofing have become a\n serious threat on the Internet (CERT Advisory CA-95:01). While\n ubiquitous crypgraphic authentication is the right answer, we propose\n a simple modification to TCP implementations that should be a very\n substantial block to the current wave of attacks.\n\nOverview and Rational\n\n In 1985, Morris [1] described a form of attack based on guessing what\n sequence numbers TCP [2] will use for new connections. Briefly, the\n attacker gags a host trusted by the target, impersonates the IP\n","scope_keywords":["1948","authentication","hash","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1948 Network Working Group S. Bellovin\nRequest for Comments: 1948 AT&T Research\nCategory: Informational May 1996\n\n Defending Against Sequence Number Attacks\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n IP spoofing attacks based on sequence number spoofing have become a\n serious threat on the Internet (CERT Advisory CA-95:01). While\n ubiquitous crypgraphic authentication is the right answer, we propose\n a simple modification to TCP implementations that should be a very\n substantial block to the current wave of attacks.\n\nOverview and Rational\n\n In 1985, Morris [1] described a form of attack based on guessing what\n sequence numbers TCP [2] will use for new connections. Briefly, the\n attacker gags a host trusted by the target, impersonates the IP\n 1948 authentication hash trust nested-reference unchanged"},{"id":"IETF RFC 1949","type":"specification","body":"IETF","designation":"RFC 1949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1949.txt","https://www.rfc-editor.org/rfc/rfc1949.pdf"],"folder":"IETF/RFC-1949","files":{"txt":{"path":"standards/IETF/RFC-1949/RFC-1949.txt","sha256":"e039c7c623ff1d2ad341d7332d3a5398497802f82fb1b38464237215c141b58f"}},"tags":["nested-reference","unchanged"],"summary":"The benefits of multicasting are becoming ever-more apparent, and its\n use much more widespread. This is evident from the growth of the\n MBONE [1]. Providing security services for multicast, such as traffic\n integrity, authentication, and confidentiality, is particularly\n problematic since it requires securely distributing a group (session)\n key to each of a group's receivers. Traditionally, the key\n distribution function has been assigned to a central network entity,\n or Key Distribution Centre (KDC), but this method does not scale for\n wide-area multicasting, where group members may be widely-distributed\n across the internetwork, and a wide-area group may be densely\n populated.\n\n Even more problematic is the scalable distribution of sender-specific\n keys. Sender-specific keys are required if data traffic is to be\n authenticated on a per-sender basis.\n\n This memo provides a scalable sol","scope_keywords":["1949","authentication","authorization","delivery","key","keys","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2189","folder":"IETF/RFC-2189","source":"IETF/RFC-2189/RFC-2189.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2627","folder":"IETF/RFC-2627","source":"IETF/RFC-2627/RFC-2627.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1949 The benefits of multicasting are becoming ever-more apparent, and its\n use much more widespread. This is evident from the growth of the\n MBONE [1]. Providing security services for multicast, such as traffic\n integrity, authentication, and confidentiality, is particularly\n problematic since it requires securely distributing a group (session)\n key to each of a group's receivers. Traditionally, the key\n distribution function has been assigned to a central network entity,\n or Key Distribution Centre (KDC), but this method does not scale for\n wide-area multicasting, where group members may be widely-distributed\n across the internetwork, and a wide-area group may be densely\n populated.\n\n Even more problematic is the scalable distribution of sender-specific\n keys. Sender-specific keys are required if data traffic is to be\n authenticated on a per-sender basis.\n\n This memo provides a scalable sol 1949 authentication authorization delivery key keys path subject nested-reference unchanged"},{"id":"IETF RFC 1964","type":"specification","body":"IETF","designation":"RFC 1964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1964.txt","https://www.rfc-editor.org/rfc/rfc1964.pdf"],"folder":"IETF/RFC-1964","files":{"txt":{"path":"standards/IETF/RFC-1964/RFC-1964.txt","sha256":"69e41874677b4c427be84681fe7e5bd96a545b7e7c7abb683608685fa3f29655"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines protocols, procedures, and conventions to\n be employed by peers implementing the Generic Security Service\n Application Program Interface (as specified in RFCs 1508 and 1509)\n when using Kerberos Version 5 technology (as specified in RFC 1510).\n\nACKNOWLEDGMENTS\n\n Much of the material in this memo is based on working documents\n drafted by John Wray of Digital Equipment Corporation and on\n discussions, implementation activities, and interoperability testing\n involving Marc Horowitz, Ted Ts'o, and John Wray. Particular thanks\n are due to each of these individuals for their contributions towards\n development and availability of GSS-API support within the Kerberos\n Version 5 code base.\n\n1. Token Formats\n\n This section discusses protocol-visible characteristics of the GSS-\n API mechanism to be implemented atop Kerberos V5 security technology\n per RFC-1508 and RFC-1510","scope_keywords":["1964","authorization","encryption","hash","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2479","folder":"IETF/RFC-2479","source":"IETF/RFC-2479/RFC-2479.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4401","folder":"IETF/RFC-4401","source":"IETF/RFC-4401/RFC-4401.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 1964 This specification defines protocols, procedures, and conventions to\n be employed by peers implementing the Generic Security Service\n Application Program Interface (as specified in RFCs 1508 and 1509)\n when using Kerberos Version 5 technology (as specified in RFC 1510).\n\nACKNOWLEDGMENTS\n\n Much of the material in this memo is based on working documents\n drafted by John Wray of Digital Equipment Corporation and on\n discussions, implementation activities, and interoperability testing\n involving Marc Horowitz, Ted Ts'o, and John Wray. Particular thanks\n are due to each of these individuals for their contributions towards\n development and availability of GSS-API support within the Kerberos\n Version 5 code base.\n\n1. Token Formats\n\n This section discusses protocol-visible characteristics of the GSS-\n API mechanism to be implemented atop Kerberos V5 security technology\n per RFC-1508 and RFC-1510 1964 authorization encryption hash key management registered nested-reference unchanged"},{"id":"IETF RFC 1994","type":"specification","body":"IETF","designation":"RFC 1994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1994.txt","https://www.rfc-editor.org/rfc/rfc1994.pdf"],"folder":"IETF/RFC-1994","files":{"txt":{"path":"standards/IETF/RFC-1994/RFC-1994.txt","sha256":"35e682831d96709a6e86ab06c3cb700158e7d347cfa5278315a16e05ec6ab4cc"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n This document defines a method for Authentication using PPP, which\n uses a random Challenge, with a cryptographically hashed Response\n which depends upon the Challenge and a secret key.","scope_keywords":["1994","authentication","hash","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2433","folder":"IETF/RFC-2433","source":"IETF/RFC-2433/RFC-2433.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 1994 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n This document defines a method for Authentication using PPP, which\n uses a random Challenge, with a cryptographically hashed Response\n which depends upon the Challenge and a secret key. 1994 authentication hash identification key nested-reference unchanged"},{"id":"IETF RFC 2025","type":"specification","body":"IETF","designation":"RFC 2025","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2025.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2025.txt","https://www.rfc-editor.org/rfc/rfc2025.pdf"],"folder":"IETF/RFC-2025","files":{"txt":{"path":"standards/IETF/RFC-2025/RFC-2025.txt","sha256":"273cbb24f0ac10aa1fe2195ecfdfc511128c4772146ec58ac565065dd8bec623"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines protocols, procedures, and conventions to\n be employed by peers implementing the Generic Security Service\n Application Program Interface (as specified in RFCs 1508 and 1509)\n when using the Simple Public-Key Mechanism.\n\nBackground\n\n Although the Kerberos Version 5 GSS-API mechanism [KRB5] is becoming\n well-established in many environments, it is important in some\n applications to have a GSS-API mechanism which is based on a public-\n key, rather than a symmetric-key, infrastructure. The mechanism\n described in this document has been proposed to meet this need and to\n provide the following features.\n\n 1) The SPKM allows both unilateral and mutual authentication\n to be accomplished without the use of secure timestamps. This\n enables environments which do not have access to secure time\n to nevertheless have access to secure authentication.\n\n 2) The SPKM uses Algori","scope_keywords":["2025","algorithm","algorithms","authentication","key","management","seal","signature","signatures","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2479","folder":"IETF/RFC-2479","source":"IETF/RFC-2479/RFC-2479.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null}],"search_text":"IETF RFC 2025 This specification defines protocols, procedures, and conventions to\n be employed by peers implementing the Generic Security Service\n Application Program Interface (as specified in RFCs 1508 and 1509)\n when using the Simple Public-Key Mechanism.\n\nBackground\n\n Although the Kerberos Version 5 GSS-API mechanism [KRB5] is becoming\n well-established in many environments, it is important in some\n applications to have a GSS-API mechanism which is based on a public-\n key, rather than a symmetric-key, infrastructure. The mechanism\n described in this document has been proposed to meet this need and to\n provide the following features.\n\n 1) The SPKM allows both unilateral and mutual authentication\n to be accomplished without the use of secure timestamps. This\n enables environments which do not have access to secure time\n to nevertheless have access to secure authentication.\n\n 2) The SPKM uses Algori 2025 algorithm algorithms authentication key management seal signature signatures timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 2040","type":"specification","body":"IETF","designation":"RFC 2040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2040.txt","https://www.rfc-editor.org/rfc/rfc2040.pdf"],"folder":"IETF/RFC-2040","files":{"txt":{"path":"standards/IETF/RFC-2040/RFC-2040.txt","sha256":"b22d1c9602c5847890934399830fd61d9f380e65748b2c0cb3bb2cf1243eff07"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Baldwin\nRequest for Comments: 2040 RSA Data Security, Inc.\nCategory: Informational R. Rivest\n MIT Laboratory for Computer Science\n and RSA Data Security, Inc.\n October 1996\n\n The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAcknowledgments\n\n We would like to thank Steve Dusse, Victor Chang, Tim Mathews, Brett\n Howard, and Burt Kaliski for helpful suggestions.\n\nTable of Contents\n\n 1. Executive Summary ....................... 1\n 2. Overview ................................ 2\n 3. Terminology and Notation ................ 3\n 4. Description of RC5 Keys ................. 4\n 5. Description of RC5 Key Expansion ........ 6\n 6. Description of RC5 Block Cipher ......... 10\n 7. Descripti","scope_keywords":["2040","algorithm","algorithms","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 3962","folder":"IETF/RFC-3962","source":"IETF/RFC-3962/RFC-3962.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"IETF RFC 2040 Network Working Group R. Baldwin\nRequest for Comments: 2040 RSA Data Security, Inc.\nCategory: Informational R. Rivest\n MIT Laboratory for Computer Science\n and RSA Data Security, Inc.\n October 1996\n\n The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAcknowledgments\n\n We would like to thank Steve Dusse, Victor Chang, Tim Mathews, Brett\n Howard, and Burt Kaliski for helpful suggestions.\n\nTable of Contents\n\n 1. Executive Summary ....................... 1\n 2. Overview ................................ 2\n 3. Terminology and Notation ................ 3\n 4. Description of RC5 Keys ................. 4\n 5. Description of RC5 Key Expansion ........ 6\n 6. Description of RC5 Block Cipher ......... 10\n 7. Descripti 2040 algorithm algorithms encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2059","type":"specification","body":"IETF","designation":"RFC 2059","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2059.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2059.txt","https://www.rfc-editor.org/rfc/rfc2059.pdf"],"folder":"IETF/RFC-2059","files":{"txt":{"path":"standards/IETF/RFC-2059/RFC-2059.txt","sha256":"e24aca6dffd780d0fdfcdfdb04867f34103b8d5b1c0919fa4bc8be97593c79de"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server.","scope_keywords":["2059","attribute","attributes","authentication","authorization","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2194","folder":"IETF/RFC-2194","source":"IETF/RFC-2194/RFC-2194.txt","version":null}],"search_text":"IETF RFC 2059 This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server. 2059 attribute attributes authentication authorization delivery key nested-reference unchanged"},{"id":"IETF RFC 2082","type":"specification","body":"IETF","designation":"RFC 2082","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2082.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2082.txt","https://www.rfc-editor.org/rfc/rfc2082.pdf"],"folder":"IETF/RFC-2082","files":{"txt":{"path":"standards/IETF/RFC-2082/RFC-2082.txt","sha256":"6332bce0df466b8151917402d10b181498c4b28b7717de9be74b374143ccf324"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Baker\nRequest for Comments: 2082 R. Atkinson\nCategory: Standards Track Cisco Systems\n January 1997\n\n RIP-2 MD5 Authentication\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Use of Imperatives ........................................... 1\n 2 Introduction ................................................. 2\n 3 Implementation Approach ...................................... 3\n 3.1 RIP-2 PDU Format ........................................... 3\n 3.2 Processing Algorithm ....................................... 5\n 3.2.1 Message Generation ","scope_keywords":["2082","algorithm","algorithms","authentication","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2453","folder":"IETF/RFC-2453","source":"IETF/RFC-2453/RFC-2453.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null}],"search_text":"IETF RFC 2082 Network Working Group F. Baker\nRequest for Comments: 2082 R. Atkinson\nCategory: Standards Track Cisco Systems\n January 1997\n\n RIP-2 MD5 Authentication\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1 Use of Imperatives ........................................... 1\n 2 Introduction ................................................. 2\n 3 Implementation Approach ...................................... 3\n 3.1 RIP-2 PDU Format ........................................... 3\n 3.2 Processing Algorithm ....................................... 5\n 3.2.1 Message Generation  2082 algorithm algorithms authentication key management path nested-reference unchanged"},{"id":"IETF RFC 2085","type":"specification","body":"IETF","designation":"RFC 2085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2085.txt","https://www.rfc-editor.org/rfc/rfc2085.pdf"],"folder":"IETF/RFC-2085","files":{"txt":{"path":"standards/IETF/RFC-2085/RFC-2085.txt","sha256":"caca6600b32ab0e3f65dd73872e18eef713f07096762ebe54681f01f6a1daa25"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a keyed-MD5 transform to be used in\n conjunction with the IP Authentication Header [RFC-1826]. The\n particular transform is based on [HMAC-MD5]. An option is also\n specified to guard against replay attacks.","scope_keywords":["2085","algorithm","authentication","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2202","folder":"IETF/RFC-2202","source":"IETF/RFC-2202/RFC-2202.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2286","folder":"IETF/RFC-2286","source":"IETF/RFC-2286/RFC-2286.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null}],"search_text":"IETF RFC 2085 This document describes a keyed-MD5 transform to be used in\n conjunction with the IP Authentication Header [RFC-1826]. The\n particular transform is based on [HMAC-MD5]. An option is also\n specified to guard against replay attacks. 2085 algorithm authentication hash key keys nested-reference unchanged"},{"id":"IETF RFC 2095","type":"specification","body":"IETF","designation":"RFC 2095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2095.txt","https://www.rfc-editor.org/rfc/rfc2095.pdf"],"folder":"IETF/RFC-2095","files":{"txt":{"path":"standards/IETF/RFC-2095/RFC-2095.txt","sha256":"08d1d3f7a3c96fd9644028e8cae5f9147e37d53a007bd5ab505cc63c5b81e7d2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Klensin\nRequest for Comments: 2095 R. Catoe\nCategory: Standards Track P. Krumviede\n MCI\n January 1997\n\n IMAP/POP AUTHorize Extension for Simple Challenge/Response\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n While IMAP4 supports a number of strong authentication mechanisms as\n described in RFC 1731, it lacks any mechanism that neither passes\n cleartext, reusable passwords across the network nor requires either\n a significant security infrastructure or that the mail server update\n a mail-system-wide user authentication file on each mail acc","scope_keywords":["2095","algorithm","authentication","identification","key","qualified","risk","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2945","folder":"IETF/RFC-2945","source":"IETF/RFC-2945/RFC-2945.txt","version":null}],"search_text":"IETF RFC 2095 Network Working Group J. Klensin\nRequest for Comments: 2095 R. Catoe\nCategory: Standards Track P. Krumviede\n MCI\n January 1997\n\n IMAP/POP AUTHorize Extension for Simple Challenge/Response\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n While IMAP4 supports a number of strong authentication mechanisms as\n described in RFC 1731, it lacks any mechanism that neither passes\n cleartext, reusable passwords across the network nor requires either\n a significant security infrastructure or that the mail server update\n a mail-system-wide user authentication file on each mail acc 2095 algorithm authentication identification key qualified risk timestamp nested-reference unchanged"},{"id":"IETF RFC 2104","type":"specification","body":"IETF","designation":"RFC 2104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2104.txt","https://www.rfc-editor.org/rfc/rfc2104.pdf"],"folder":"IETF/RFC-2104","files":{"txt":{"path":"standards/IETF/RFC-2104/RFC-2104.txt","sha256":"64d5245a9101929025336e470e3737f118704001249d503c85a86e19fe9fbb01"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Krawczyk\nRequest for Comments: 2104 IBM\nCategory: Informational M. Bellare\n UCSD\n R. Canetti\n IBM\n February 1997\n\n HMAC: Keyed-Hashing for Message Authentication\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes HMAC, a mechanism for message authentication\n using cryptographic hash functions. HMAC can be used with any\n iterative cryptographic hash function, e.g., MD5, SHA-1, in\n combination with a secret shared key. The cryptographic strength of\n HMAC depends on the properties of the underlying hash function.\n\n1. Introduction\n\n Providing a way to check the integrity of information transmitted\n over or stored in an unreliable medium is a prime necessity in the\n world of open computing and communi","scope_keywords":["2104","authentication","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2085","folder":"IETF/RFC-2085","source":"IETF/RFC-2085/RFC-2085.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2202","folder":"IETF/RFC-2202","source":"IETF/RFC-2202/RFC-2202.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2286","folder":"IETF/RFC-2286","source":"IETF/RFC-2286/RFC-2286.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2511","folder":"IETF/RFC-2511","source":"IETF/RFC-2511/RFC-2511.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2693","folder":"IETF/RFC-2693","source":"IETF/RFC-2693/RFC-2693.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2756","folder":"IETF/RFC-2756","source":"IETF/RFC-2756/RFC-2756.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2875","folder":"IETF/RFC-2875","source":"IETF/RFC-2875/RFC-2875.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2945","folder":"IETF/RFC-2945","source":"IETF/RFC-2945/RFC-2945.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 3967","folder":"IETF/RFC-3967","source":"IETF/RFC-3967/RFC-3967.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4226","folder":"IETF/RFC-4226","source":"IETF/RFC-4226/RFC-4226.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4231","folder":"IETF/RFC-4231","source":"IETF/RFC-4231/RFC-4231.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4357","folder":"IETF/RFC-4357","source":"IETF/RFC-4357/RFC-4357.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4493","folder":"IETF/RFC-4493","source":"IETF/RFC-4493/RFC-4493.txt","version":null},{"body":"IETF","designation":"RFC 4494","folder":"IETF/RFC-4494","source":"IETF/RFC-4494/RFC-4494.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 4758","folder":"IETF/RFC-4758","source":"IETF/RFC-4758/RFC-4758.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5769","folder":"IETF/RFC-5769","source":"IETF/RFC-5769/RFC-5769.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 2104 Network Working Group H. Krawczyk\nRequest for Comments: 2104 IBM\nCategory: Informational M. Bellare\n UCSD\n R. Canetti\n IBM\n February 1997\n\n HMAC: Keyed-Hashing for Message Authentication\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes HMAC, a mechanism for message authentication\n using cryptographic hash functions. HMAC can be used with any\n iterative cryptographic hash function, e.g., MD5, SHA-1, in\n combination with a secret shared key. The cryptographic strength of\n HMAC depends on the properties of the underlying hash function.\n\n1. Introduction\n\n Providing a way to check the integrity of information transmitted\n over or stored in an unreliable medium is a prime necessity in the\n world of open computing and communi 2104 authentication hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 2107","type":"specification","body":"IETF","designation":"RFC 2107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2107.txt","https://www.rfc-editor.org/rfc/rfc2107.pdf"],"folder":"IETF/RFC-2107","files":{"txt":{"path":"standards/IETF/RFC-2107/RFC-2107.txt","sha256":"0084df52ce46ffafb397ef2ddd8b95a1bf9cf53f4daf87ca36915d3184e84537"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a generic tunnel management protocol that\n allows remote dial-in users to access their home network as if they\n were directly attached to the home network. The user's client\n software uses an address contained in the home network address space\n for the remote access. Packets to and from the home network are\n tunneled by the Network Access Server (NAS) to which the user\n connects and a Home Agent (HA) on the user's home network. This\n allows for the support of access to Virtual Private Networks and also\n allows for the use of protocols other than IP to be carried over the\n tunnel. An example of how the RADIUS (Remote Authentication Dial In\n User Service) can be used to provide the necessary configuration\n information to support this service is also provided.\n\n1. Introduction\n\n The Ascend Tunnel Management Protocol (ATMP) is a protocol currently\n being used in Ascen","scope_keywords":["2107","authentication","delivery","management","path","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null}],"search_text":"IETF RFC 2107 This document specifies a generic tunnel management protocol that\n allows remote dial-in users to access their home network as if they\n were directly attached to the home network. The user's client\n software uses an address contained in the home network address space\n for the remote access. Packets to and from the home network are\n tunneled by the Network Access Server (NAS) to which the user\n connects and a Home Agent (HA) on the user's home network. This\n allows for the support of access to Virtual Private Networks and also\n allows for the use of protocols other than IP to be carried over the\n tunnel. An example of how the RADIUS (Remote Authentication Dial In\n User Service) can be used to provide the necessary configuration\n information to support this service is also provided.\n\n1. Introduction\n\n The Ascend Tunnel Management Protocol (ATMP) is a protocol currently\n being used in Ascen 2107 authentication delivery management path profile registered nested-reference unchanged"},{"id":"IETF RFC 2139","type":"specification","body":"IETF","designation":"RFC 2139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2139.txt","https://www.rfc-editor.org/rfc/rfc2139.pdf"],"folder":"IETF/RFC-2139","files":{"txt":{"path":"standards/IETF/RFC-2139/RFC-2139.txt","sha256":"ae4b68733e6c6e3ce8a96c0d18dad0991b18ec621dbf20b7f61109ba78c522bc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server.\n\nImplementation Note\n\n This memo documents the RADIUS Accounting protocol. There has been\n some confusion in the assignment of port numbers for this protocol.\n The early deployment of RADIUS Accounting was done using the\n erroneously chosen port number 1646, which conflicts with the \"sa-\n msg-port\" service. The officially assigned port number for RADIUS\n Accounting is 1813.","scope_keywords":["2139","attribute","attributes","authentication","authorization","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null}],"search_text":"IETF RFC 2139 This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server.\n\nImplementation Note\n\n This memo documents the RADIUS Accounting protocol. There has been\n some confusion in the assignment of port numbers for this protocol.\n The early deployment of RADIUS Accounting was done using the\n erroneously chosen port number 1646, which conflicts with the \"sa-\n msg-port\" service. The officially assigned port number for RADIUS\n Accounting is 1813. 2139 attribute attributes authentication authorization delivery key nested-reference unchanged"},{"id":"IETF RFC 2195","type":"specification","body":"IETF","designation":"RFC 2195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2195.txt","https://www.rfc-editor.org/rfc/rfc2195.pdf"],"folder":"IETF/RFC-2195","files":{"txt":{"path":"standards/IETF/RFC-2195/RFC-2195.txt","sha256":"d21daaa112d2e067d8f6f6fe2a22b04bc52c736935874940634857a934c6b1cd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Klensin\nRequest for Comments: 2195 R. Catoe\nCategory: Standards Track P. Krumviede\nObsoletes: 2095 MCI\n September 1997\n\n IMAP/POP AUTHorize Extension for Simple Challenge/Response\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n While IMAP4 supports a number of strong authentication mechanisms as\n described in RFC 1731, it lacks any mechanism that neither passes\n cleartext, reusable passwords across the network nor requires either\n a significant security infrastructure or that the mail server update\n a mail-system-wide user authentication file","scope_keywords":["2195","algorithm","authentication","hash","hashing","identification","key","qualified","risk","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2617","folder":"IETF/RFC-2617","source":"IETF/RFC-2617/RFC-2617.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null}],"search_text":"IETF RFC 2195 Network Working Group J. Klensin\nRequest for Comments: 2195 R. Catoe\nCategory: Standards Track P. Krumviede\nObsoletes: 2095 MCI\n September 1997\n\n IMAP/POP AUTHorize Extension for Simple Challenge/Response\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n While IMAP4 supports a number of strong authentication mechanisms as\n described in RFC 1731, it lacks any mechanism that neither passes\n cleartext, reusable passwords across the network nor requires either\n a significant security infrastructure or that the mail server update\n a mail-system-wide user authentication file 2195 algorithm authentication hash hashing identification key qualified risk timestamp nested-reference unchanged"},{"id":"IETF RFC 2202","type":"specification","body":"IETF","designation":"RFC 2202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2202.txt","https://www.rfc-editor.org/rfc/rfc2202.pdf"],"folder":"IETF/RFC-2202","files":{"txt":{"path":"standards/IETF/RFC-2202/RFC-2202.txt","sha256":"c19effeca47e801be304460da3b2fb05f595e2309abceb050e40e024868fe483"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Cheng\nRequest for Comments: 2202 IBM\nCategory: Informational R. Glenn\n NIST\n September 1997\n\n Test Cases for HMAC-MD5 and HMAC-SHA-1\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document provides two sets of test cases for HMAC-MD5 and HMAC-\n SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of\n the HMAC [HMAC] message authentication function using the MD5 [MD5]\n hash function and the SHA-1 [SHA] hash function. Both constructs are\n used by IPSEC [OG,CG] and other protocols to authenticate messages.\n The test cases and results provided in this document are meant to be\n used as a conformance test for HMAC-MD5 and HMAC-SHA-1\n implementations.\n\n1. Introduction\n\n The general method for constructing a","scope_keywords":["2202","algorithm","authentication","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2286","folder":"IETF/RFC-2286","source":"IETF/RFC-2286/RFC-2286.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2511","folder":"IETF/RFC-2511","source":"IETF/RFC-2511/RFC-2511.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4231","folder":"IETF/RFC-4231","source":"IETF/RFC-4231/RFC-4231.txt","version":null},{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null}],"search_text":"IETF RFC 2202 Network Working Group P. Cheng\nRequest for Comments: 2202 IBM\nCategory: Informational R. Glenn\n NIST\n September 1997\n\n Test Cases for HMAC-MD5 and HMAC-SHA-1\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document provides two sets of test cases for HMAC-MD5 and HMAC-\n SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of\n the HMAC [HMAC] message authentication function using the MD5 [MD5]\n hash function and the SHA-1 [SHA] hash function. Both constructs are\n used by IPSEC [OG,CG] and other protocols to authenticate messages.\n The test cases and results provided in this document are meant to be\n used as a conformance test for HMAC-MD5 and HMAC-SHA-1\n implementations.\n\n1. Introduction\n\n The general method for constructing a 2202 algorithm authentication hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 2264","type":"specification","body":"IETF","designation":"RFC 2264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2264.txt","https://www.rfc-editor.org/rfc/rfc2264.pdf"],"folder":"IETF/RFC-2264","files":{"txt":{"path":"standards/IETF/RFC-2264/RFC-2264.txt","sha256":"d9105d3185d64c6c00b7cee54c0a421bc3c84088d5001360521bac620a7b093f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2261]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model.","scope_keywords":["2264","algorithm","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null}],"search_text":"IETF RFC 2264 This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2261]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model. 2264 algorithm authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 2274","type":"specification","body":"IETF","designation":"RFC 2274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2274.txt","https://www.rfc-editor.org/rfc/rfc2274.pdf"],"folder":"IETF/RFC-2274","files":{"txt":{"path":"standards/IETF/RFC-2274/RFC-2274.txt","sha256":"7a252b794c51b18f0d70f080974913eaca22fd2df314554a9e6b41aea7d0065c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2271]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model.","scope_keywords":["2274","algorithm","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null}],"search_text":"IETF RFC 2274 This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2271]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model. 2274 algorithm authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 2286","type":"specification","body":"IETF","designation":"RFC 2286","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2286.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2286.txt","https://www.rfc-editor.org/rfc/rfc2286.pdf"],"folder":"IETF/RFC-2286","files":{"txt":{"path":"standards/IETF/RFC-2286/RFC-2286.txt","sha256":"8e1c7d9d8834e8247653be67a2bbdf8a40b2efc9d01488b3357bfea92944da7d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Kapp\nRequest for Comments: 2286 Reaper Technologies\nCategory: Informational February 1998\n\n Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document provides two sets of test cases for HMAC-RIPEMD160 and\n HMAC-RIPEMD128, respectively. HMAC-RIPEMD160 and HMAC-RIPEMD128 are\n two constructs of the HMAC [HMAC] message authentication function\n using the RIPEMD-160 and RIPEMD-128 [RIPE] hash functions. The test\n cases and results provided in this document are meant to be used as a\n conformance test for HMAC-RIPEMD160 and HMAC-RIPEMD128\n implementations.\n\n1. Introduction\n\n The general method for","scope_keywords":["2286","algorithm","authentication","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null}],"search_text":"IETF RFC 2286 Network Working Group J. Kapp\nRequest for Comments: 2286 Reaper Technologies\nCategory: Informational February 1998\n\n Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document provides two sets of test cases for HMAC-RIPEMD160 and\n HMAC-RIPEMD128, respectively. HMAC-RIPEMD160 and HMAC-RIPEMD128 are\n two constructs of the HMAC [HMAC] message authentication function\n using the RIPEMD-160 and RIPEMD-128 [RIPE] hash functions. The test\n cases and results provided in this document are meant to be used as a\n conformance test for HMAC-RIPEMD160 and HMAC-RIPEMD128\n implementations.\n\n1. Introduction\n\n The general method for 2286 algorithm authentication hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 2311","type":"specification","body":"IETF","designation":"RFC 2311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2311.txt","https://www.rfc-editor.org/rfc/rfc2311.pdf"],"folder":"IETF/RFC-2311","files":{"txt":{"path":"standards/IETF/RFC-2311/RFC-2311.txt","sha256":"2ad3d89874161178994835f8e639da5a51caf61b654c866f40c85f03e48903cd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Dusse\nRequest for Comments: 2311 RSA Data Security\nCategory: Informational P. Hoffman\n Internet Mail Consortium\n B. Ramsdell\n Worldtalk\n L. Lundblade\n Qualcomm\n L. Repka\n Netscape\n March 1998\n\n S/MIME Version 2 Message Specification\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) provides a\n consistent way to send and receive secure MIME data. Based on the\n popular Internet MIME standard, S/MIME provides the following\n cryptographic security services for electronic messaging\n applications: authentication, message integrity and non-repudiation\n of origin (using digital signatures) a","scope_keywords":["2311","algorithm","authentication","certificate","encryption","http","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2311 Network Working Group S. Dusse\nRequest for Comments: 2311 RSA Data Security\nCategory: Informational P. Hoffman\n Internet Mail Consortium\n B. Ramsdell\n Worldtalk\n L. Lundblade\n Qualcomm\n L. Repka\n Netscape\n March 1998\n\n S/MIME Version 2 Message Specification\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) provides a\n consistent way to send and receive secure MIME data. Based on the\n popular Internet MIME standard, S/MIME provides the following\n cryptographic security services for electronic messaging\n applications: authentication, message integrity and non-repudiation\n of origin (using digital signatures) a 2311 algorithm authentication certificate encryption http key signature signatures nested-reference unchanged"},{"id":"IETF RFC 2385","type":"specification","body":"IETF","designation":"RFC 2385","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2385.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2385.txt","https://www.rfc-editor.org/rfc/rfc2385.pdf"],"folder":"IETF/RFC-2385","files":{"txt":{"path":"standards/IETF/RFC-2385/RFC-2385.txt","sha256":"e4579d6535bbb20dd15de5a1be8e2300af6b397177fd1b384d877ee02542f190"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a TCP extension to enhance security for BGP. It\n defines a new TCP option for carrying an MD5 [RFC1321] digest in a\n TCP segment. This digest acts like a signature for that segment,\n incorporating information known only to the connection end points.\n Since BGP uses TCP as its transport, using this option in the way\n described in this paper significantly reduces the danger from certain\n security attacks on BGP.","scope_keywords":["2385","algorithm","key","path","policy","signature","signatures","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2796","folder":"IETF/RFC-2796","source":"IETF/RFC-2796/RFC-2796.txt","version":null},{"body":"IETF","designation":"RFC 2842","folder":"IETF/RFC-2842","source":"IETF/RFC-2842/RFC-2842.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 3392","folder":"IETF/RFC-3392","source":"IETF/RFC-3392/RFC-3392.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4724","folder":"IETF/RFC-4724","source":"IETF/RFC-4724/RFC-4724.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4781","folder":"IETF/RFC-4781","source":"IETF/RFC-4781/RFC-4781.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2385 This memo describes a TCP extension to enhance security for BGP. It\n defines a new TCP option for carrying an MD5 [RFC1321] digest in a\n TCP segment. This digest acts like a signature for that segment,\n incorporating information known only to the connection end points.\n Since BGP uses TCP as its transport, using this option in the way\n described in this paper significantly reduces the danger from certain\n security attacks on BGP. 2385 algorithm key path policy signature signatures timestamp nested-reference unchanged"},{"id":"IETF RFC 2403","type":"specification","body":"IETF","designation":"RFC 2403","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2403.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2403.txt","https://www.rfc-editor.org/rfc/rfc2403.pdf"],"folder":"IETF/RFC-2403","files":{"txt":{"path":"standards/IETF/RFC-2403/RFC-2403.txt","sha256":"c3d1514d351d23e7c53b27573a7e0a7355c0e66295dd49b20b89b957e155b2b3"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the HMAC algorithm [RFC-2104] in\n conjunction with the MD5 algorithm [RFC-1321] as an authentication\n mechanism within the revised IPSEC Encapsulating Security Payload\n [ESP] and the revised IPSEC Authentication Header [AH]. HMAC with MD5\n provides data origin authentication and integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of MD5 [RFC-1321] combined with HMAC\n [RFC-2104] as a keyed authentication mechanism within the context of\n the Encapsulating Security Payload and the Authentication Header.\n The goal of HMAC-MD5-96 is to ensure that the packet is authentic and\n cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authentication as provided by HMAC are depende","scope_keywords":["2403","algorithm","algorithms","authentication","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2403 This memo describes the use of the HMAC algorithm [RFC-2104] in\n conjunction with the MD5 algorithm [RFC-1321] as an authentication\n mechanism within the revised IPSEC Encapsulating Security Payload\n [ESP] and the revised IPSEC Authentication Header [AH]. HMAC with MD5\n provides data origin authentication and integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of MD5 [RFC-1321] combined with HMAC\n [RFC-2104] as a keyed authentication mechanism within the context of\n the Encapsulating Security Payload and the Authentication Header.\n The goal of HMAC-MD5-96 is to ensure that the packet is authentic and\n cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authentication as provided by HMAC are depende 2403 algorithm algorithms authentication hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 2409","type":"specification","body":"IETF","designation":"RFC 2409","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2409.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2409.txt","https://www.rfc-editor.org/rfc/rfc2409.pdf"],"folder":"IETF/RFC-2409","files":{"txt":{"path":"standards/IETF/RFC-2409/RFC-2409.txt","sha256":"5b19aab3886800c3ce7528e0dba4eb05dc6405e03388ed4dd3032fb02f4616d9"}},"tags":["nested-reference","unchanged"],"summary":"ISAKMP ([MSST98]) provides a framework for authentication and key\n exchange but does not define them. ISAKMP is designed to be key\n exchange independant; that is, it is designed to support many\n different key exchanges.\n\n Oakley ([Orm96]) describes a series of key exchanges-- called\n \"modes\"-- and details the services provided by each (e.g. perfect\n forward secrecy for keys, identity protection, and authentication).\n\n SKEME ([SKEME]) describes a versatile key exchange technique which\n provides anonymity, repudiability, and quick key refreshment.\n\n This document describes a protocol using part of Oakley and part of\n SKEME in conjunction with ISAKMP to obtain authenticated keying\n material for use with ISAKMP, and for other security associations\n such as AH and ESP for the IETF IPsec DOI.\n\n2. Discussion\n\n This memo describes a hybrid protocol. The purpose is to negotiate,\n and provide auth","scope_keywords":["2409","authentication","certificate","encryption","hash","identification","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2628","folder":"IETF/RFC-2628","source":"IETF/RFC-2628/RFC-2628.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3051","folder":"IETF/RFC-3051","source":"IETF/RFC-3051/RFC-3051.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3129","folder":"IETF/RFC-3129","source":"IETF/RFC-3129/RFC-3129.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3457","folder":"IETF/RFC-3457","source":"IETF/RFC-3457/RFC-3457.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3526","folder":"IETF/RFC-3526","source":"IETF/RFC-3526/RFC-3526.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3706","folder":"IETF/RFC-3706","source":"IETF/RFC-3706/RFC-3706.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3766","folder":"IETF/RFC-3766","source":"IETF/RFC-3766/RFC-3766.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2409 ISAKMP ([MSST98]) provides a framework for authentication and key\n exchange but does not define them. ISAKMP is designed to be key\n exchange independant; that is, it is designed to support many\n different key exchanges.\n\n Oakley ([Orm96]) describes a series of key exchanges-- called\n \"modes\"-- and details the services provided by each (e.g. perfect\n forward secrecy for keys, identity protection, and authentication).\n\n SKEME ([SKEME]) describes a versatile key exchange technique which\n provides anonymity, repudiability, and quick key refreshment.\n\n This document describes a protocol using part of Oakley and part of\n SKEME in conjunction with ISAKMP to obtain authenticated keying\n material for use with ISAKMP, and for other security associations\n such as AH and ESP for the IETF IPsec DOI.\n\n2. Discussion\n\n This memo describes a hybrid protocol. The purpose is to negotiate,\n and provide auth 2409 authentication certificate encryption hash identification key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2444","type":"specification","body":"IETF","designation":"RFC 2444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2444.txt","https://www.rfc-editor.org/rfc/rfc2444.pdf"],"folder":"IETF/RFC-2444","files":{"txt":{"path":"standards/IETF/RFC-2444/RFC-2444.txt","sha256":"b7ef8ecdf20c9054c71db662f678c7887eba9f2f8f775cec5016714e22f58ac1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Newman\nRequest for Comments: 2444 Innosoft\nUpdates: 2222 October 1998\nCategory: Standards Track\n\n The One-Time-Password SASL Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n OTP [OTP] provides a useful authentication mechanism for situations\n where there is limited client or server trust. Currently, OTP is\n added to protocols in an ad-hoc fashion with heuristic parsing. This\n specification defines an OTP SASL [SASL] mechanism so it can be\n easily and ","scope_keywords":["2444","algorithm","authentication","authorization","hash","key","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null}],"search_text":"IETF RFC 2444 Network Working Group C. Newman\nRequest for Comments: 2444 Innosoft\nUpdates: 2222 October 1998\nCategory: Standards Track\n\n The One-Time-Password SASL Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n OTP [OTP] provides a useful authentication mechanism for situations\n where there is limited client or server trust. Currently, OTP is\n added to protocols in an ad-hoc fashion with heuristic parsing. This\n specification defines an OTP SASL [SASL] mechanism so it can be\n easily and  2444 algorithm authentication authorization hash key profile subject trust nested-reference unchanged"},{"id":"IETF RFC 2574","type":"specification","body":"IETF","designation":"RFC 2574","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2574.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2574.txt","https://www.rfc-editor.org/rfc/rfc2574.pdf"],"folder":"IETF/RFC-2574","files":{"txt":{"path":"standards/IETF/RFC-2574/RFC-2574.txt","sha256":"2425cb7a737fd4434ba46eb4063e1f34433ede6eddce0f8f8e117d254fa7b932"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2571]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model.","scope_keywords":["2574","algorithm","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null}],"search_text":"IETF RFC 2574 This document describes the User-based Security Model (USM) for SNMP\n version 3 for use in the SNMP architecture [RFC2571]. It defines the\n Elements of Procedure for providing SNMP message level security.\n This document also includes a MIB for remotely monitoring/managing\n the configuration parameters for this Security Model. 2574 algorithm authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 2617","type":"specification","body":"IETF","designation":"RFC 2617","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2617.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2617.txt","https://www.rfc-editor.org/rfc/rfc2617.pdf"],"folder":"IETF/RFC-2617","files":{"txt":{"path":"standards/IETF/RFC-2617/RFC-2617.txt","sha256":"cf5492136782d9e9fce492c254ca39e2c93328cf38c4dd006039abb5d8e27ba7"}},"tags":["nested-reference","unchanged"],"summary":"\"HTTP/1.0\", includes the specification for a Basic Access\n Authentication scheme. This scheme is not considered to be a secure\n method of user authentication (unless used in conjunction with some\n external secure system such as SSL [5]), as the user name and\n password are passed over the network as cleartext.\n\n This document also provides the specification for HTTP's\n authentication framework, the original Basic authentication scheme\n and a scheme based on cryptographic hashes, referred to as \"Digest\n Access Authentication\". It is therefore also intended to serve as a\n replacement for RFC 2069 [6]. Some optional elements specified by\n RFC 2069 have been removed from this specification due to problems\n found since its publication; other new elements have been added for\n compatibility, those new elements have been made optional, but are\n strongly recommended.\n\nFranks, et al. Standards Trac","scope_keywords":["2617","attribute","authentication","authorization","hash","http","policies","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3310","folder":"IETF/RFC-3310","source":"IETF/RFC-3310/RFC-3310.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3665","folder":"IETF/RFC-3665","source":"IETF/RFC-3665/RFC-3665.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2617 \"HTTP/1.0\", includes the specification for a Basic Access\n Authentication scheme. This scheme is not considered to be a secure\n method of user authentication (unless used in conjunction with some\n external secure system such as SSL [5]), as the user name and\n password are passed over the network as cleartext.\n\n This document also provides the specification for HTTP's\n authentication framework, the original Basic authentication scheme\n and a scheme based on cryptographic hashes, referred to as \"Digest\n Access Authentication\". It is therefore also intended to serve as a\n replacement for RFC 2069 [6]. Some optional elements specified by\n RFC 2069 have been removed from this specification due to problems\n found since its publication; other new elements have been added for\n compatibility, those new elements have been made optional, but are\n strongly recommended.\n\nFranks, et al. Standards Trac 2617 attribute authentication authorization hash http policies presentation risk nested-reference unchanged"},{"id":"IETF RFC 2630","type":"specification","body":"IETF","designation":"RFC 2630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2630.txt","https://www.rfc-editor.org/rfc/rfc2630.pdf"],"folder":"IETF/RFC-2630","files":{"txt":{"path":"standards/IETF/RFC-2630/RFC-2630.txt","sha256":"92a1785c3f94c00df530eae9b383deca5c622a3a657fee7cc91f90a169fcd276"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Cryptographic Message Syntax. This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary messages.\n\n The Cryptographic Message Syntax is derived from PKCS #7 version 1.5\n as specified in RFC 2315 [PKCS#7]. Wherever possible, backward\n compatibility is preserved; however, changes were necessary to\n accommodate attribute certificate transfer and key agreement\n techniques for key management.\n\nHousley Standards Track [Page 1]\n\f\nRFC 2630 Cryptographic Message Syntax June 1999","scope_keywords":["2630","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","encryption","issuer","key","management","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"},{"body":"IETF","designation":"RFC 2631","folder":"IETF/RFC-2631","source":"IETF/RFC-2631/RFC-2631.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2785","folder":"IETF/RFC-2785","source":"IETF/RFC-2785/RFC-2785.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2876","folder":"IETF/RFC-2876","source":"IETF/RFC-2876/RFC-2876.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3211","folder":"IETF/RFC-3211","source":"IETF/RFC-3211/RFC-3211.txt","version":null},{"body":"IETF","designation":"RFC 3217","folder":"IETF/RFC-3217","source":"IETF/RFC-3217/RFC-3217.txt","version":null},{"body":"IETF","designation":"RFC 3218","folder":"IETF/RFC-3218","source":"IETF/RFC-3218/RFC-3218.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3274","folder":"IETF/RFC-3274","source":"IETF/RFC-3274/RFC-3274.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2630 This document describes the Cryptographic Message Syntax. This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary messages.\n\n The Cryptographic Message Syntax is derived from PKCS #7 version 1.5\n as specified in RFC 2315 [PKCS#7]. Wherever possible, backward\n compatibility is preserved; however, changes were necessary to\n accommodate attribute certificate transfer and key agreement\n techniques for key management.\n\nHousley Standards Track [Page 1]\n\f\nRFC 2630 Cryptographic Message Syntax June 1999 2630 algorithm algorithms attribute attributes authentication certificate certificates encryption issuer key management revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 2633","type":"specification","body":"IETF","designation":"RFC 2633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2633.txt","https://www.rfc-editor.org/rfc/rfc2633.pdf"],"folder":"IETF/RFC-2633","files":{"txt":{"path":"standards/IETF/RFC-2633/RFC-2633.txt","sha256":"0c7a3fab8f9bd3e5929c5cc491659c6bf384a7c1b857a774c442ba67f1942f79"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Ramsdell, Editor\nRequest for Comments: 2633 Worldtalk\nCategory: Standards Track June 1999\n\n S/MIME Version 3 Message Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) provides a\n consistent way to send and receive secure MIME data. Based on the\n popular Internet MIME standard, S/MIME provides the following\n cryptographic security services for electronic messaging\n applications: authentica","scope_keywords":["2633","algorithm","algorithms","authentication","certificate","encryption","http","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2785","folder":"IETF/RFC-2785","source":"IETF/RFC-2785/RFC-2785.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2876","folder":"IETF/RFC-2876","source":"IETF/RFC-2876/RFC-2876.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3274","folder":"IETF/RFC-3274","source":"IETF/RFC-3274/RFC-3274.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 2633 Network Working Group B. Ramsdell, Editor\nRequest for Comments: 2633 Worldtalk\nCategory: Standards Track June 1999\n\n S/MIME Version 3 Message Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) provides a\n consistent way to send and receive secure MIME data. Based on the\n popular Internet MIME standard, S/MIME provides the following\n cryptographic security services for electronic messaging\n applications: authentica 2633 algorithm algorithms authentication certificate encryption http key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2716","type":"specification","body":"IETF","designation":"RFC 2716","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2716.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2716.txt","https://www.rfc-editor.org/rfc/rfc2716.pdf"],"folder":"IETF/RFC-2716","files":{"txt":{"path":"standards/IETF/RFC-2716/RFC-2716.txt","sha256":"e491be4efd5f1db67dc256623f4ec62e77a5561a452f181842a6140946747d61"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol (LCP), which can be\n used to negotiate authentication methods, as well as an Encryption\n Control Protocol (ECP), used to negotiate data encryption over PPP\n links, and a Compression Control Protocol (CCP), used to negotiate\n compression methods. The Extensible Authentication Protocol (EAP) is\n a PPP extension that provides support for additional authentication\n methods within PPP.\n\n Transport Level Security (TLS) provides for mutual authentication,\n integrity-protected ciphersuite negotiation and key exchange between\n two endpoints. This document describes how EAP-TLS, which includes\n support for fragmentation and reassembly, provides for these TLS\n mechanisms within EAP.\n\n2. Introduction\n\n The Extensible ","scope_keywords":["2716","attribute","attributes","authentication","certificate","encryption","http","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null}],"search_text":"IETF RFC 2716 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol (LCP), which can be\n used to negotiate authentication methods, as well as an Encryption\n Control Protocol (ECP), used to negotiate data encryption over PPP\n links, and a Compression Control Protocol (CCP), used to negotiate\n compression methods. The Extensible Authentication Protocol (EAP) is\n a PPP extension that provides support for additional authentication\n methods within PPP.\n\n Transport Level Security (TLS) provides for mutual authentication,\n integrity-protected ciphersuite negotiation and key exchange between\n two endpoints. This document describes how EAP-TLS, which includes\n support for fragmentation and reassembly, provides for these TLS\n mechanisms within EAP.\n\n2. Introduction\n\n The Extensible  2716 attribute attributes authentication certificate encryption http key management tls nested-reference unchanged"},{"id":"IETF RFC 2748","type":"specification","body":"IETF","designation":"RFC 2748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2748.txt","https://www.rfc-editor.org/rfc/rfc2748.pdf"],"folder":"IETF/RFC-2748","files":{"txt":{"path":"standards/IETF/RFC-2748/RFC-2748.txt","sha256":"28642ff242cc68737b46b0175119124be659ff1f6d6e1a173d65d7db2b08cae7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple client/server model for supporting\n policy control over QoS signaling protocols. The model does not make\n any assumptions about the methods of the policy server, but is based\n on the server returning decisions to policy requests. The model is\n designed to be extensible so that other kinds of policy clients may\n be supported in the future. However, this document makes no claims\n that it is the only or the preferred approach for enforcing future\n types of policies.\n\nDurham, et al. Standards Track [Page 1]\n\f\nRFC 2748 COPS January 2000","scope_keywords":["2748","authentication","identification","key","pid","policies","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2749","folder":"IETF/RFC-2749","source":"IETF/RFC-2749/RFC-2749.txt","version":null},{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3139","folder":"IETF/RFC-3139","source":"IETF/RFC-3139/RFC-3139.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3535","folder":"IETF/RFC-3535","source":"IETF/RFC-3535/RFC-3535.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4178","folder":"IETF/RFC-4178","source":"IETF/RFC-4178/RFC-4178.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2748 This document describes a simple client/server model for supporting\n policy control over QoS signaling protocols. The model does not make\n any assumptions about the methods of the policy server, but is based\n on the server returning decisions to policy requests. The model is\n designed to be extensible so that other kinds of policy clients may\n be supported in the future. However, this document makes no claims\n that it is the only or the preferred approach for enforcing future\n types of policies.\n\nDurham, et al. Standards Track [Page 1]\n\f\nRFC 2748 COPS January 2000 2748 authentication identification key pid policies policy tls nested-reference unchanged"},{"id":"IETF RFC 2762","type":"specification","body":"IETF","designation":"RFC 2762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2762.txt","https://www.rfc-editor.org/rfc/rfc2762.pdf"],"folder":"IETF/RFC-2762","files":{"txt":{"path":"standards/IETF/RFC-2762/RFC-2762.txt","sha256":"bf826f40525e688f8f92e7f70957b27e1a678a27ee357aae10b0622e9daabae9"}},"tags":["nested-reference","unchanged"],"summary":"In large multicast groups, the size of the group membership table\n maintained by RTP (Real Time Transport Protocol) participants may\n become unwieldy, particularly for embedded devices with limited\n memory and processing power. This document discusses mechanisms for\n sampling of this group membership table in order to reduce the memory\n requirements. Several mechanisms are proposed, and the performance of\n each is considered.\n\n1 Introduction\n\n RTP, the Real Time Transport Protocol [1], mandates that RTCP packets\n be transmitted from each participant with a period roughly\n proportional to the group size. The group size is obtained by storing\n a table, containing an entry for each unique SSRC seen in RTP and\n RTCP packets. As members leave or time out, entries are deleted, and\n as new members join, entries are added. The table is thus highly\n dynamic.\n\n For large multicast sessions, such a","scope_keywords":["2762","algorithm","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null}],"search_text":"IETF RFC 2762 In large multicast groups, the size of the group membership table\n maintained by RTP (Real Time Transport Protocol) participants may\n become unwieldy, particularly for embedded devices with limited\n memory and processing power. This document discusses mechanisms for\n sampling of this group membership table in order to reduce the memory\n requirements. Several mechanisms are proposed, and the performance of\n each is considered.\n\n1 Introduction\n\n RTP, the Real Time Transport Protocol [1], mandates that RTCP packets\n be transmitted from each participant with a period roughly\n proportional to the group size. The group size is obtained by storing\n a table, containing an entry for each unique SSRC seen in RTP and\n RTCP packets. As members leave or time out, entries are deleted, and\n as new members join, entries are added. The table is thus highly\n dynamic.\n\n For large multicast sessions, such a 2762 algorithm hash key nested-reference unchanged"},{"id":"IETF RFC 2777","type":"specification","body":"IETF","designation":"RFC 2777","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2777.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2777.txt","https://www.rfc-editor.org/rfc/rfc2777.pdf"],"folder":"IETF/RFC-2777","files":{"txt":{"path":"standards/IETF/RFC-2777/RFC-2777.txt","sha256":"0df635e5db3844252e60f1fb3a2a28f43858b22d1e1725f0cf878c3e8fecfdb0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for making random selections in such\n a way that the unbiased nature of the choice is publicly verifiable.\n As an example, the selection of the voting members of the IETF\n Nominations Committee from the pool of eligible volunteers is used.\n Similar techniques would be applicable to other cases.\n\nAcknowledgement\n\n Matt Crawford made major contributions to this document.","scope_keywords":["2777","algorithm","hash","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2727","folder":"IETF/RFC-2727","source":"IETF/RFC-2727/RFC-2727.txt","version":null},{"body":"IETF","designation":"RFC 3777","folder":"IETF/RFC-3777","source":"IETF/RFC-3777/RFC-3777.txt","version":null},{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null}],"search_text":"IETF RFC 2777 This document describes a method for making random selections in such\n a way that the unbiased nature of the choice is publicly verifiable.\n As an example, the selection of the voting members of the IETF\n Nominations Committee from the pool of eligible volunteers is used.\n Similar techniques would be applicable to other cases.\n\nAcknowledgement\n\n Matt Crawford made major contributions to this document. 2777 algorithm hash verifiable nested-reference unchanged"},{"id":"IETF RFC 2792","type":"specification","body":"IETF","designation":"RFC 2792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2792.txt","https://www.rfc-editor.org/rfc/rfc2792.pdf"],"folder":"IETF/RFC-2792","files":{"txt":{"path":"standards/IETF/RFC-2792/RFC-2792.txt","sha256":"6c09697a83562ad58f79890f2f1a3ad1982fed6f57df09ad65345e2d965fcaf8"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes RSA and DSA key and signature encoding, and\n binary key encoding for version 2 of the KeyNote trust-management\n system.\n\n1. Introduction\n\n KeyNote is a simple and flexible trust-management system designed to\n work well for a variety of large- and small-scale Internet-based\n applications. It provides a single, unified language for both local\n policies and credentials. KeyNote policies and credentials, called\n `assertions', contain predicates that describe the trusted actions\n permitted by the holders of specific public keys. KeyNote assertions\n are essentially small, highly-structured programs. A signed\n assertion, which can be sent over an untrusted network, is also\n called a `credential assertion'. Credential assertions, which also\n serve the role of certificates, have the same syntax as policy\n assertions but are also signed by the principal delegating the trust.\n F","scope_keywords":["2792","algorithm","certificate","certificates","credential","credentials","hash","holder","key","keys","management","policies","policy","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null}],"search_text":"IETF RFC 2792 This memo describes RSA and DSA key and signature encoding, and\n binary key encoding for version 2 of the KeyNote trust-management\n system.\n\n1. Introduction\n\n KeyNote is a simple and flexible trust-management system designed to\n work well for a variety of large- and small-scale Internet-based\n applications. It provides a single, unified language for both local\n policies and credentials. KeyNote policies and credentials, called\n `assertions', contain predicates that describe the trusted actions\n permitted by the holders of specific public keys. KeyNote assertions\n are essentially small, highly-structured programs. A signed\n assertion, which can be sent over an untrusted network, is also\n called a `credential assertion'. Credential assertions, which also\n serve the role of certificates, have the same syntax as policy\n assertions but are also signed by the principal delegating the trust.\n F 2792 algorithm certificate certificates credential credentials hash holder key keys management policies policy signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2802","type":"specification","body":"IETF","designation":"RFC 2802","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2802.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2802.txt","https://www.rfc-editor.org/rfc/rfc2802.pdf"],"folder":"IETF/RFC-2802","files":{"txt":{"path":"standards/IETF/RFC-2802/RFC-2802.txt","sha256":"4953d7c058556f7472b3eec17c0b1e871ffc87c31d3c81354d5363158105ef88"}},"tags":["nested-reference","unchanged"],"summary":"A syntax and procedures are described for the computation and\n verification of digital signatures for use within Version 1.0 of the\n Internet Open Trading Protocol (IOTP).\n\nAcknowledgment\n\n This document is based on work originally done on general XML digital\n signatures by:\n\n Richard Brown of GlobeSet, Inc. <rdbrown@GlobeSet.com>\n\n Other contributors to the design of the IOTP DSIG DTD include, in\n alphabetic order:\n\n David Burdett, Commerce One\n Andrew Drapp, Hitachi\n Donald Eastlake 3rd, Motorola, Inc.\n\nDavidson & Kawatsura Informational [Page 1]\n\f\nRFC 2802 Digital Signatures for IOTP April 2000","scope_keywords":["2802","algorithm","algorithms","attribute","attributes","authentication","certificate","hash","issuer","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2807","folder":"IETF/RFC-2807","source":"IETF/RFC-2807/RFC-2807.txt","version":null}],"search_text":"IETF RFC 2802 A syntax and procedures are described for the computation and\n verification of digital signatures for use within Version 1.0 of the\n Internet Open Trading Protocol (IOTP).\n\nAcknowledgment\n\n This document is based on work originally done on general XML digital\n signatures by:\n\n Richard Brown of GlobeSet, Inc. <rdbrown@GlobeSet.com>\n\n Other contributors to the design of the IOTP DSIG DTD include, in\n alphabetic order:\n\n David Burdett, Commerce One\n Andrew Drapp, Hitachi\n Donald Eastlake 3rd, Motorola, Inc.\n\nDavidson & Kawatsura Informational [Page 1]\n\f\nRFC 2802 Digital Signatures for IOTP April 2000 2802 algorithm algorithms attribute attributes authentication certificate hash issuer key signature signatures nested-reference unchanged"},{"id":"IETF RFC 2803","type":"specification","body":"IETF","designation":"RFC 2803","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2803.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2803.txt","https://www.rfc-editor.org/rfc/rfc2803.pdf"],"folder":"IETF/RFC-2803","files":{"txt":{"path":"standards/IETF/RFC-2803/RFC-2803.txt","sha256":"118b00710a22ad5b8b116e3050b268f3bbdbbf5b6cbb326b3d35faaacb9646f6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a clear and unambiguous definition of digest (hash)\n values of the XML objects regardless of the surface string variation\n of XML. This definition can be used for XML digital signature as well\n efficient replication of XML objects.","scope_keywords":["2803","algorithm","algorithms","attribute","attributes","hash","hashing","http","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2807","folder":"IETF/RFC-2807","source":"IETF/RFC-2807/RFC-2807.txt","version":null}],"search_text":"IETF RFC 2803 This memo defines a clear and unambiguous definition of digest (hash)\n values of the XML objects regardless of the surface string variation\n of XML. This definition can be used for XML digital signature as well\n efficient replication of XML objects. 2803 algorithm algorithms attribute attributes hash hashing http signature signatures nested-reference unchanged"},{"id":"IETF RFC 2831","type":"specification","body":"IETF","designation":"RFC 2831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2831.txt","https://www.rfc-editor.org/rfc/rfc2831.pdf"],"folder":"IETF/RFC-2831","files":{"txt":{"path":"standards/IETF/RFC-2831/RFC-2831.txt","sha256":"5ef9584255be4c0556430fc3507e8001df55f909703ccc81a049f77ec45467c4"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines how HTTP Digest Authentication [Digest]\n can be used as a SASL [RFC 2222] mechanism for any protocol that has\n a SASL profile. It is intended both as an improvement over CRAM-MD5\n [RFC 2195] and as a convenient way to support a single authentication\n mechanism for web, mail, LDAP, and other protocols.","scope_keywords":["2831","algorithm","authentication","hash","http","key","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null}],"search_text":"IETF RFC 2831 This specification defines how HTTP Digest Authentication [Digest]\n can be used as a SASL [RFC 2222] mechanism for any protocol that has\n a SASL profile. It is intended both as an improvement over CRAM-MD5\n [RFC 2195] and as a convenient way to support a single authentication\n mechanism for web, mail, LDAP, and other protocols. 2831 algorithm authentication hash http key presentation profile nested-reference unchanged"},{"id":"IETF RFC 2866","type":"specification","body":"IETF","designation":"RFC 2866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2866.txt","https://www.rfc-editor.org/rfc/rfc2866.pdf"],"folder":"IETF/RFC-2866","files":{"txt":{"path":"standards/IETF/RFC-2866/RFC-2866.txt","sha256":"b8d0fbab82c0397de674274822343765ff92a441278a4ac9308d0b087a42b08c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server.\n\nImplementation Note\n\n This memo documents the RADIUS Accounting protocol. The early\n deployment of RADIUS Accounting was done using UDP port number 1646,\n which conflicts with the \"sa-msg-port\" service. The officially\n assigned port number for RADIUS Accounting is 1813.","scope_keywords":["2866","attribute","attributes","authentication","authorization","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2866 This document describes a protocol for carrying accounting\n information between a Network Access Server and a shared Accounting\n Server.\n\nImplementation Note\n\n This memo documents the RADIUS Accounting protocol. The early\n deployment of RADIUS Accounting was done using UDP port number 1646,\n which conflicts with the \"sa-msg-port\" service. The officially\n assigned port number for RADIUS Accounting is 1813. 2866 attribute attributes authentication authorization delivery key nested-reference unchanged"},{"id":"IETF RFC 2938","type":"specification","body":"IETF","designation":"RFC 2938","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2938.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2938.txt","https://www.rfc-editor.org/rfc/rfc2938.pdf"],"folder":"IETF/RFC-2938","files":{"txt":{"path":"standards/IETF/RFC-2938/RFC-2938.txt","sha256":"8456c439131c0097dc13903d02a9ff689f45ae16b8edb3de77ba3cd52ec7355a"}},"tags":["nested-reference","unchanged"],"summary":"In RFC 2533, an expression format is presented for describing media\n feature capabilities as a combination of simple media feature tags.\n\n This document describes an abbreviated format for a composite media\n feature set, based upon a hash of the feature expression describing\n that composite.","scope_keywords":["2938","hash","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null}],"search_text":"IETF RFC 2938 In RFC 2533, an expression format is presented for describing media\n feature capabilities as a combination of simple media feature tags.\n\n This document describes an abbreviated format for a composite media\n feature set, based upon a hash of the feature expression describing\n that composite. 2938 hash presentation nested-reference unchanged"},{"id":"IETF RFC 2945","type":"specification","body":"IETF","designation":"RFC 2945","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2945.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2945.txt","https://www.rfc-editor.org/rfc/rfc2945.pdf"],"folder":"IETF/RFC-2945","files":{"txt":{"path":"standards/IETF/RFC-2945/RFC-2945.txt","sha256":"27eac34c382f3525397fc057bd8017eddebd2beda460056077cc8e8c4020dbc0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a cryptographically strong network\n authentication mechanism known as the Secure Remote Password (SRP)\n protocol. This mechanism is suitable for negotiating secure\n connections using a user-supplied password, while eliminating the\n security problems traditionally associated with reusable passwords.\n This system also performs a secure key exchange in the process of\n authentication, allowing security layers (privacy and/or integrity\n protection) to be enabled during the session. Trusted key servers\n and certificate infrastructures are not required, and clients are not\n required to store or manage any long-term keys. SRP offers both\n security and deployment advantages over existing challenge-response\n techniques, making it an ideal drop-in replacement where secure\n password authentication is needed.\n\n1. Introduction\n\n The lack of a secure authentication mechanism tha","scope_keywords":["2945","algorithm","authentication","certificate","hash","key","keys","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null}],"search_text":"IETF RFC 2945 This document describes a cryptographically strong network\n authentication mechanism known as the Secure Remote Password (SRP)\n protocol. This mechanism is suitable for negotiating secure\n connections using a user-supplied password, while eliminating the\n security problems traditionally associated with reusable passwords.\n This system also performs a secure key exchange in the process of\n authentication, allowing security layers (privacy and/or integrity\n protection) to be enabled during the session. Trusted key servers\n and certificate infrastructures are not required, and clients are not\n required to store or manage any long-term keys. SRP offers both\n security and deployment advantages over existing challenge-response\n techniques, making it an ideal drop-in replacement where secure\n password authentication is needed.\n\n1. Introduction\n\n The lack of a secure authentication mechanism tha 2945 algorithm authentication certificate hash key keys presentation trust nested-reference unchanged"},{"id":"IETF RFC 2961","type":"specification","body":"IETF","designation":"RFC 2961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2961.txt","https://www.rfc-editor.org/rfc/rfc2961.pdf"],"folder":"IETF/RFC-2961","files":{"txt":{"path":"standards/IETF/RFC-2961/RFC-2961.txt","sha256":"cd95a451afced040cd1573b7850b421ea3da07337743fb0c27056bb8d41b99e7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a number of mechanisms that can be used to\n reduce processing overhead requirements of refresh messages,\n eliminate the state synchronization latency incurred when an RSVP\n (Resource ReserVation Protocol) message is lost and, when desired,\n refreshing state without the transmission of whole refresh messages.\n The same extensions also support reliable RSVP message delivery on a\n per hop basis. These extension present no backwards compatibility\n issues.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 2961 RSVP Refresh Overhead Reduction Extensions April 2001","scope_keywords":["2961","algorithm","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3097","folder":"IETF/RFC-3097","source":"IETF/RFC-3097/RFC-3097.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3210","folder":"IETF/RFC-3210","source":"IETF/RFC-3210/RFC-3210.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null}],"search_text":"IETF RFC 2961 This document describes a number of mechanisms that can be used to\n reduce processing overhead requirements of refresh messages,\n eliminate the state synchronization latency incurred when an RSVP\n (Resource ReserVation Protocol) message is lost and, when desired,\n refreshing state without the transmission of whole refresh messages.\n The same extensions also support reliable RSVP message delivery on a\n per hop basis. These extension present no backwards compatibility\n issues.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 2961 RSVP Refresh Overhead Reduction Extensions April 2001 2961 algorithm delivery path nested-reference unchanged"},{"id":"IETF RFC 3036","type":"specification","body":"IETF","designation":"RFC 3036","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3036.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3036.txt","https://www.rfc-editor.org/rfc/rfc3036.pdf"],"folder":"IETF/RFC-3036","files":{"txt":{"path":"standards/IETF/RFC-3036/RFC-3036.txt","sha256":"60721f9c3b568d863ad8cf0365b9fc5aff972f34b59edb39e70624dfb1c65d69"}},"tags":["nested-reference","unchanged"],"summary":"The architecture for Multi Protocol Label Switching (MPLS) is\n described in RFC 3031. A fundamental concept in MPLS is that two\n Label Switching Routers (LSRs) must agree on the meaning of the\n labels used to forward traffic between and through them. This common\n understanding is achieved by using a set of procedures, called a\n label distribution protocol, by which one LSR informs another of\n label bindings it has made. This document defines a set of such\n procedures called LDP (for Label Distribution Protocol) by which LSRs\n distribute labels to support MPLS forwarding along normally routed\n paths.\n\nAndersson, et al. Standards Track [Page 1]\n\f\nRFC 3036 LDP Specification January 2001","scope_keywords":["3036","management","path","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3038","folder":"IETF/RFC-3038","source":"IETF/RFC-3038/RFC-3038.txt","version":null},{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3215","folder":"IETF/RFC-3215","source":"IETF/RFC-3215/RFC-3215.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3478","folder":"IETF/RFC-3478","source":"IETF/RFC-3478/RFC-3478.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null}],"search_text":"IETF RFC 3036 The architecture for Multi Protocol Label Switching (MPLS) is\n described in RFC 3031. A fundamental concept in MPLS is that two\n Label Switching Routers (LSRs) must agree on the meaning of the\n labels used to forward traffic between and through them. This common\n understanding is achieved by using a set of procedures, called a\n label distribution protocol, by which one LSR informs another of\n label bindings it has made. This document defines a set of such\n procedures called LDP (for Label Distribution Protocol) by which LSRs\n distribute labels to support MPLS forwarding along normally routed\n paths.\n\nAndersson, et al. Standards Track [Page 1]\n\f\nRFC 3036 LDP Specification January 2001 3036 management path signature nested-reference unchanged"},{"id":"IETF RFC 3041","type":"specification","body":"IETF","designation":"RFC 3041","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3041.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3041.txt","https://www.rfc-editor.org/rfc/rfc3041.pdf"],"folder":"IETF/RFC-3041","files":{"txt":{"path":"standards/IETF/RFC-3041/RFC-3041.txt","sha256":"805f195c85925e5c84cee8bcda859d260b0076e5846d8e9a83f54a8f40dc0edf"}},"tags":["nested-reference","unchanged"],"summary":"Nodes use IPv6 stateless address autoconfiguration to generate\n addresses without the necessity of a Dynamic Host Configuration\n Protocol (DHCP) server. Addresses are formed by combining network\n prefixes with an interface identifier. On interfaces that contain\n embedded IEEE Identifiers, the interface identifier is typically\n derived from it. On other interface types, the interface identifier\n is generated through other means, for example, via random number\n generation. This document describes an extension to IPv6 stateless\n address autoconfiguration for interfaces whose interface identifier\n is derived from an IEEE identifier. Use of the extension causes\n nodes to generate global-scope addresses from interface identifiers\n that change over time, even in cases where the interface contains an\n embedded IEEE identifier. Changing the interface identifier (and the\n global-scope addresses ge","scope_keywords":["3041"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4177","folder":"IETF/RFC-4177","source":"IETF/RFC-4177/RFC-4177.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 3041 Nodes use IPv6 stateless address autoconfiguration to generate\n addresses without the necessity of a Dynamic Host Configuration\n Protocol (DHCP) server. Addresses are formed by combining network\n prefixes with an interface identifier. On interfaces that contain\n embedded IEEE Identifiers, the interface identifier is typically\n derived from it. On other interface types, the interface identifier\n is generated through other means, for example, via random number\n generation. This document describes an extension to IPv6 stateless\n address autoconfiguration for interfaces whose interface identifier\n is derived from an IEEE identifier. Use of the extension causes\n nodes to generate global-scope addresses from interface identifiers\n that change over time, even in cases where the interface contains an\n embedded IEEE identifier. Changing the interface identifier (and the\n global-scope addresses ge 3041 nested-reference unchanged"},{"id":"IETF RFC 3112","type":"specification","body":"IETF","designation":"RFC 3112","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3112.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3112.txt","https://www.rfc-editor.org/rfc/rfc3112.pdf"],"folder":"IETF/RFC-3112","files":{"txt":{"path":"standards/IETF/RFC-3112/RFC-3112.txt","sha256":"921be15a85c29ac6fc5369ac677ea447e090a38db43b5591bcb98023cde37111"}},"tags":["nested-reference","unchanged"],"summary":"This document describes schema in support of user/password\n authentication in a LDAP (Lightweight Directory Access Protocol)\n directory including the authPassword attribute type. This attribute\n type holds values derived from the user's password(s) (commonly using\n cryptographic strength one-way hash). authPassword is intended to\n used instead of userPassword.\n\n1. Background and Intended Use\n\n The userPassword attribute type [RFC2256] is intended to be used to\n support the LDAP [RFC2251] \"simple\" bind operation. However, values\n of userPassword must be clear text passwords. It is often desirable\n to store values derived from the user's password(s) instead of actual\n passwords.\n\n The authPassword attribute type is intended to be used to store\n information used to implement simple password based authentication.\n The attribute type may be used by LDAP servers to implement the LDAP\n Bind ope","scope_keywords":["3112","algorithm","attribute","attributes","authentication","hash","hashing","key","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null}],"search_text":"IETF RFC 3112 This document describes schema in support of user/password\n authentication in a LDAP (Lightweight Directory Access Protocol)\n directory including the authPassword attribute type. This attribute\n type holds values derived from the user's password(s) (commonly using\n cryptographic strength one-way hash). authPassword is intended to\n used instead of userPassword.\n\n1. Background and Intended Use\n\n The userPassword attribute type [RFC2256] is intended to be used to\n support the LDAP [RFC2251] \"simple\" bind operation. However, values\n of userPassword must be clear text passwords. It is often desirable\n to store values derived from the user's password(s) instead of actual\n passwords.\n\n The authPassword attribute type is intended to be used to store\n information used to implement simple password based authentication.\n The attribute type may be used by LDAP servers to implement the LDAP\n Bind ope 3112 algorithm attribute attributes authentication hash hashing key policies presentation nested-reference unchanged"},{"id":"IETF RFC 3161","type":"specification","body":"IETF","designation":"RFC 3161","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3161.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3161.txt","https://www.rfc-editor.org/rfc/rfc3161.pdf"],"folder":"IETF/RFC-3161","files":{"txt":{"path":"standards/IETF/RFC-3161/RFC-3161.txt","sha256":"39fd17644ff2d654bc83814a78b1c5b5e7517f496741f34ead5064943eb98240"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document describes the format of a request sent to a Time\n Stamping Authority (TSA) and of the response that is returned. It\n also establishes several security-relevant requirements for TSA\n operation, with regards to processing requests to generate responses.\n\n1. Introduction\n\n A time-stamping service supports assertions of proof that a datum\n existed before a particular time. A TSA may be operated as a Trusted\n Third Party (TTP) service, though other operational models may be\n appropriate, e.g., an organization might require a TSA for internal\n time-stamping purposes.\n\n Non-repudiation services [ISONR] require the ability to establish the\n existence of data before specified times. This protocol may be used\n as a building block to support such services. An example of how to\n prove that a digital signature was generated during the validity\n period of a public key certificate is give","scope_keywords":["3161","algorithm","certificate","hash","identification","key","pki","policies","policy","presentation","qualified","revocation","signature","signatures","timestamp","trust"],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 172-4","folder":"ETSI/TS-119-172-4-V1.1.1","source":"ETSI/TS-119-172-4-V1.1.1/TS-119-172-4-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 4049","folder":"IETF/RFC-4049","source":"IETF/RFC-4049/RFC-4049.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4810","folder":"IETF/RFC-4810","source":"IETF/RFC-4810/RFC-4810.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6019","folder":"IETF/RFC-6019","source":"IETF/RFC-6019/RFC-6019.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null}],"search_text":"IETF RFC 3161 This document describes the format of a request sent to a Time\n Stamping Authority (TSA) and of the response that is returned. It\n also establishes several security-relevant requirements for TSA\n operation, with regards to processing requests to generate responses.\n\n1. Introduction\n\n A time-stamping service supports assertions of proof that a datum\n existed before a particular time. A TSA may be operated as a Trusted\n Third Party (TTP) service, though other operational models may be\n appropriate, e.g., an organization might require a TSA for internal\n time-stamping purposes.\n\n Non-repudiation services [ISONR] require the ability to establish the\n existence of data before specified times. This protocol may be used\n as a building block to support such services. An example of how to\n prove that a digital signature was generated during the validity\n period of a public key certificate is give 3161 algorithm certificate hash identification key pki policies policy presentation qualified revocation signature signatures timestamp trust cited-by-eu-law implementing-regulation nested-reference unchanged 2025-1929 Qualified electronic time stamps 32025R1929"},{"id":"IETF RFC 3188","type":"specification","body":"IETF","designation":"RFC 3188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3188.txt","https://www.rfc-editor.org/rfc/rfc3188.pdf"],"folder":"IETF/RFC-3188","files":{"txt":{"path":"standards/IETF/RFC-3188/RFC-3188.txt","sha256":"04e2fe5cf02509bbb8fa217fc7981df6826840656d6d693aaa09983b436e597f"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how national bibliography numbers (persistent\n and unique identifiers assigned by the national libraries) can be\n supported within the URN (Uniform Resource Names) framework and the\n syntax for URNs defined in RFC 2141. Much of the discussion is based\n on the ideas expressed in RFC 2288.\n\n1. Introduction\n\n As part of the validation process for the development of URNs the\n IETF working group agreed that it is important to demonstrate that\n the current URN syntax proposal can accommodate existing identifiers\n from well established namespaces. One such infrastructure for\n assigning and managing names comes from the bibliographic community.\n Bibliographic identifiers function as names for objects that exist\n both in print and, increasingly, in electronic formats. RFC 2288\n [Lynch] investigated the feasibility of using three identifiers\n (ISBN, ISSN and SICI) as URNs.\n","scope_keywords":["3188","archiving","http","identification","policies","preservation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 3188 This document discusses how national bibliography numbers (persistent\n and unique identifiers assigned by the national libraries) can be\n supported within the URN (Uniform Resource Names) framework and the\n syntax for URNs defined in RFC 2141. Much of the discussion is based\n on the ideas expressed in RFC 2288.\n\n1. Introduction\n\n As part of the validation process for the development of URNs the\n IETF working group agreed that it is important to demonstrate that\n the current URN syntax proposal can accommodate existing identifiers\n from well established namespaces. One such infrastructure for\n assigning and managing names comes from the bibliographic community.\n Bibliographic identifiers function as names for objects that exist\n both in print and, increasingly, in electronic formats. RFC 2288\n [Lynch] investigated the feasibility of using three identifiers\n (ISBN, ISSN and SICI) as URNs.\n 3188 archiving http identification policies preservation validation nested-reference unchanged"},{"id":"IETF RFC 3224","type":"specification","body":"IETF","designation":"RFC 3224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3224.txt","https://www.rfc-editor.org/rfc/rfc3224.pdf"],"folder":"IETF/RFC-3224","files":{"txt":{"path":"standards/IETF/RFC-3224/RFC-3224.txt","sha256":"1b5f8490d1251bbdc2ef577f88e7c5210ff119f2d3f569d6dd9807357cb96e40"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how the features of the Service Location\n Protocol, Version 2 allow for vendor extensibility safely, with no\n possibility of collisions. The specification introduces a new SLPv2\n extension: The Vendor Opaque Extension. While proprietary protocol\n extensions are not encouraged by IETF standards, it is important that\n they not hinder interoperability of compliant implementations when\n they are undertaken. This document udpates RFC 2608, \"The Service\n Location Protocol.\"","scope_keywords":["3224","attribute","attributes","authentication","key","management","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 3224 This document specifies how the features of the Service Location\n Protocol, Version 2 allow for vendor extensibility safely, with no\n possibility of collisions. The specification introduces a new SLPv2\n extension: The Vendor Opaque Extension. While proprietary protocol\n extensions are not encouraged by IETF standards, it is important that\n they not hinder interoperability of compliant implementations when\n they are undertaken. This document udpates RFC 2608, \"The Service\n Location Protocol.\" 3224 attribute attributes authentication key management pid registered nested-reference unchanged"},{"id":"IETF RFC 3230","type":"specification","body":"IETF","designation":"RFC 3230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3230.txt","https://www.rfc-editor.org/rfc/rfc3230.pdf"],"folder":"IETF/RFC-3230","files":{"txt":{"path":"standards/IETF/RFC-3230/RFC-3230.txt","sha256":"15f7bb1867dc117c74a620b854ac3fee1e17742324943d3eed62e5a42008581c"}},"tags":["nested-reference","unchanged"],"summary":"HTTP/1.1 defines a Content-MD5 header that allows a server to include\n a digest of the response body. However, this is specifically defined\n to cover the body of the actual message, not the contents of the full\n file (which might be quite different, if the response is a Content-\n Range, or uses a delta encoding). Also, the Content-MD5 is limited\n to one specific digest algorithm; other algorithms, such as SHA-1\n (Secure Hash Standard), may be more appropriate in some\n circumstances. Finally, HTTP/1.1 provides no explicit mechanism by\n which a client may request a digest. This document proposes HTTP\n extensions that solve these problems.","scope_keywords":["3230","algorithm","algorithms","authentication","hash","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null}],"search_text":"IETF RFC 3230 HTTP/1.1 defines a Content-MD5 header that allows a server to include\n a digest of the response body. However, this is specifically defined\n to cover the body of the actual message, not the contents of the full\n file (which might be quite different, if the response is a Content-\n Range, or uses a delta encoding). Also, the Content-MD5 is limited\n to one specific digest algorithm; other algorithms, such as SHA-1\n (Secure Hash Standard), may be more appropriate in some\n circumstances. Finally, HTTP/1.1 provides no explicit mechanism by\n which a client may request a digest. This document proposes HTTP\n extensions that solve these problems. 3230 algorithm algorithms authentication hash http presentation nested-reference unchanged"},{"id":"IETF RFC 3257","type":"specification","body":"IETF","designation":"RFC 3257","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3257.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3257.txt","https://www.rfc-editor.org/rfc/rfc3257.pdf"],"folder":"IETF/RFC-3257","files":{"txt":{"path":"standards/IETF/RFC-3257/RFC-3257.txt","sha256":"5e0af84498e696f5d7fa38540002a57145269d28cbe6800e31c317273b9f4309"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the applicability of the Stream Control\n Transmission Protocol (SCTP). It also contrasts SCTP with the two\n dominant transport protocols, User Datagram Protocol (UDP) &\n Transmission Control Protocol (TCP), and gives some guidelines for\n when best to use SCTP and when not best to use SCTP.","scope_keywords":["3257","delivery","path","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null}],"search_text":"IETF RFC 3257 This document describes the applicability of the Stream Control\n Transmission Protocol (SCTP). It also contrasts SCTP with the two\n dominant transport protocols, User Datagram Protocol (UDP) &\n Transmission Control Protocol (TCP), and gives some guidelines for\n when best to use SCTP and when not best to use SCTP. 3257 delivery path preservation nested-reference unchanged"},{"id":"IETF RFC 3370","type":"specification","body":"IETF","designation":"RFC 3370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3370.txt","https://www.rfc-editor.org/rfc/rfc3370.pdf"],"folder":"IETF/RFC-3370","files":{"txt":{"path":"standards/IETF/RFC-3370/RFC-3370.txt","sha256":"702c366b9360e01d207c220960b538db18685880add3afefbd401a85b136a825"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using several\n cryptographic algorithms with the Cryptographic Message Syntax (CMS).\n The CMS is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message contents.","scope_keywords":["3370","algorithm","algorithms","attribute","authentication","encryption","key","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3370 This document describes the conventions for using several\n cryptographic algorithms with the Cryptographic Message Syntax (CMS).\n The CMS is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message contents. 3370 algorithm algorithms attribute authentication encryption key management signature nested-reference unchanged"},{"id":"IETF RFC 3414","type":"specification","body":"IETF","designation":"RFC 3414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3414.txt","https://www.rfc-editor.org/rfc/rfc3414.pdf"],"folder":"IETF/RFC-3414","files":{"txt":{"path":"standards/IETF/RFC-3414/RFC-3414.txt","sha256":"636ffdf3f44222d4295e52a846075a3fea826604cd8ba88ae8e69d87664cbb5f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the User-based Security Model (USM) for\n Simple Network Management Protocol (SNMP) version 3 for use in the\n SNMP architecture. It defines the Elements of Procedure for\n providing SNMP message level security. This document also includes a\n Management Information Base (MIB) for remotely monitoring/managing\n the configuration parameters for this Security Model. This document\n obsoletes RFC 2574.","scope_keywords":["3414","algorithm","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3826","folder":"IETF/RFC-3826","source":"IETF/RFC-3826/RFC-3826.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null}],"search_text":"IETF RFC 3414 This document describes the User-based Security Model (USM) for\n Simple Network Management Protocol (SNMP) version 3 for use in the\n SNMP architecture. It defines the Elements of Procedure for\n providing SNMP message level security. This document also includes a\n Management Information Base (MIB) for remotely monitoring/managing\n the configuration parameters for this Security Model. This document\n obsoletes RFC 2574. 3414 algorithm authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 3452","type":"specification","body":"IETF","designation":"RFC 3452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3452.txt","https://www.rfc-editor.org/rfc/rfc3452.pdf"],"folder":"IETF/RFC-3452","files":{"txt":{"path":"standards/IETF/RFC-3452/RFC-3452.txt","sha256":"d419d0f81a1011ccd7e6f16f68ba8b7eb66800d2eac37d3a2171d0f47b5ee794"}},"tags":["nested-reference","unchanged"],"summary":"This document generally describes how to use Forward Error Correction\n (FEC) codes to efficiently provide and/or augment reliability for\n data transport. The primary focus of this document is the\n application of FEC codes to one-to-many reliable data transport using\n IP multicast. This document describes what information is needed to\n identify a specific FEC code, what information needs to be\n communicated out-of-band to use the FEC code, and what information is\n needed in data packets to identify the encoding symbols they carry.\n The procedures for specifying FEC codes and registering them with the\n Internet Assigned Numbers Authority (IANA) are also described. This\n document should be read in conjunction with and uses the terminology\n of the companion document titled, \"The Use of Forward Error\n Correction (FEC) in Reliable Multicast\".\n\nLuby, et. al. Experimental [Page 1]\n\f\nRFC 3452 FEC","scope_keywords":["3452","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null}],"search_text":"IETF RFC 3452 This document generally describes how to use Forward Error Correction\n (FEC) codes to efficiently provide and/or augment reliability for\n data transport. The primary focus of this document is the\n application of FEC codes to one-to-many reliable data transport using\n IP multicast. This document describes what information is needed to\n identify a specific FEC code, what information needs to be\n communicated out-of-band to use the FEC code, and what information is\n needed in data packets to identify the encoding symbols they carry.\n The procedures for specifying FEC codes and registering them with the\n Internet Assigned Numbers Authority (IANA) are also described. This\n document should be read in conjunction with and uses the terminology\n of the companion document titled, \"The Use of Forward Error\n Correction (FEC) in Reliable Multicast\".\n\nLuby, et. al. Experimental [Page 1]\n\f\nRFC 3452 FEC 3452 delivery key nested-reference unchanged"},{"id":"IETF RFC 3631","type":"specification","body":"IETF","designation":"RFC 3631","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3631.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3631.txt","https://www.rfc-editor.org/rfc/rfc3631.pdf"],"folder":"IETF/RFC-3631","files":{"txt":{"path":"standards/IETF/RFC-3631/RFC-3631.txt","sha256":"d675ba51948efff12540f51948cca1f3eeed261b0d9f09f6502de7c61e64f13a"}},"tags":["nested-reference","unchanged"],"summary":"Security must be built into Internet Protocols for those protocols to\n offer their services securely. Many security problems can be traced\n to improper implementations. However, even a proper implementation\n will have security problems if the fundamental protocol is itself\n exploitable. Exactly how security should be implemented in a\n protocol will vary, because of the structure of the protocol itself.\n However, there are many protocols for which standard Internet\n security mechanisms, already developed, may be applicable. The\n precise one that is appropriate in any given situation can vary. We\n review a number of different choices, explaining the properties of\n each.\n\n1. Introduction\n\n Internet Security compromises can be divided into several classes,\n ranging from Denial of Service to Host Compromise. Denial of Service\n attacks based on sheer volume of traffic are beyond the scope of t","scope_keywords":["3631","authentication","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null}],"search_text":"IETF RFC 3631 Security must be built into Internet Protocols for those protocols to\n offer their services securely. Many security problems can be traced\n to improper implementations. However, even a proper implementation\n will have security problems if the fundamental protocol is itself\n exploitable. Exactly how security should be implemented in a\n protocol will vary, because of the structure of the protocol itself.\n However, there are many protocols for which standard Internet\n security mechanisms, already developed, may be applicable. The\n precise one that is appropriate in any given situation can vary. We\n review a number of different choices, explaining the properties of\n each.\n\n1. Introduction\n\n Internet Security compromises can be divided into several classes,\n ranging from Denial of Service to Host Compromise. Denial of Service\n attacks based on sheer volume of traffic are beyond the scope of t 3631 authentication management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 3652","type":"specification","body":"IETF","designation":"RFC 3652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3652.txt","https://www.rfc-editor.org/rfc/rfc3652.pdf"],"folder":"IETF/RFC-3652","files":{"txt":{"path":"standards/IETF/RFC-3652/RFC-3652.txt","sha256":"debde9d6ad284ad652c6e6bd4b1c2649c5904296238e0de4c7a1a33c4b1f4f43"}},"tags":["nested-reference","unchanged"],"summary":"The Handle System is a general-purpose global name service that\n allows secured name resolution and administration over the public\n Internet. This document describes the protocol used for client\n software to access the Handle System for both handle resolution and\n administration. The protocol specifies the procedure for a client\n software to locate the responsible handle server of any given handle.\n It also defines the messages exchanged between the client and server\n for any handle operation.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 3652 Handle System Protocol (v2.1) November 2003","scope_keywords":["3652","authentication","credential","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null}],"search_text":"IETF RFC 3652 The Handle System is a general-purpose global name service that\n allows secured name resolution and administration over the public\n Internet. This document describes the protocol used for client\n software to access the Handle System for both handle resolution and\n administration. The protocol specifies the procedure for a client\n software to locate the responsible handle server of any given handle.\n It also defines the messages exchanged between the client and server\n for any handle operation.\n\nSun, et al. Informational [Page 1]\n\f\nRFC 3652 Handle System Protocol (v2.1) November 2003 3652 authentication credential key management nested-reference unchanged"},{"id":"IETF RFC 3797","type":"specification","body":"IETF","designation":"RFC 3797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3797.txt","https://www.rfc-editor.org/rfc/rfc3797.pdf"],"folder":"IETF/RFC-3797","files":{"txt":{"path":"standards/IETF/RFC-3797/RFC-3797.txt","sha256":"ffa63ba05fe243aa95805c2ae0ec43deb2e3293a99129d2181d30e39d70d8ef9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for making random selections in such\n a way that the unbiased nature of the choice is publicly verifiable.\n As an example, the selection of the voting members of the IETF\n Nominations Committee (NomCom) from the pool of eligible volunteers\n is used. Similar techniques would be applicable to other cases.","scope_keywords":["3797","algorithm","hash","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3777","folder":"IETF/RFC-3777","source":"IETF/RFC-3777/RFC-3777.txt","version":null}],"search_text":"IETF RFC 3797 This document describes a method for making random selections in such\n a way that the unbiased nature of the choice is publicly verifiable.\n As an example, the selection of the voting members of the IETF\n Nominations Committee (NomCom) from the pool of eligible volunteers\n is used. Similar techniques would be applicable to other cases. 3797 algorithm hash verifiable nested-reference unchanged"},{"id":"IETF RFC 3967","type":"specification","body":"IETF","designation":"RFC 3967","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3967.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3967.txt","https://www.rfc-editor.org/rfc/rfc3967.pdf"],"folder":"IETF/RFC-3967","files":{"txt":{"path":"standards/IETF/RFC-3967/RFC-3967.txt","sha256":"62afaaaca921b2255f537f0be324b43d554a731287cbb20cbd81d0616b9e6338"}},"tags":["nested-reference","unchanged"],"summary":"IETF procedures generally require that a standards track RFC may not\n have a normative reference to another standards track document at a\n lower maturity level or to a non standards track specification (other\n than specifications from other standards bodies). For example, a\n standards track document may not have a normative reference to an\n informational RFC. Exceptions to this rule are sometimes needed as\n the IETF uses informational RFCs to describe non-IETF standards or\n IETF-specific modes of use of such standards. This document\n clarifies and updates the procedure used in these circumstances.\n\n1. Introduction\n\n The Internet Standards Process [RFC2026] Section 4.2.4 specifies the\n following:\n\n Standards track specifications normally must not depend on other\n standards track specifications which are at a lower maturity level\n or on non standards track specifications other than referen","scope_keywords":["3967","algorithm","algorithms","key","management","profile","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null},{"body":"IETF","designation":"RFC 4897","folder":"IETF/RFC-4897","source":"IETF/RFC-4897/RFC-4897.txt","version":null}],"search_text":"IETF RFC 3967 IETF procedures generally require that a standards track RFC may not\n have a normative reference to another standards track document at a\n lower maturity level or to a non standards track specification (other\n than specifications from other standards bodies). For example, a\n standards track document may not have a normative reference to an\n informational RFC. Exceptions to this rule are sometimes needed as\n the IETF uses informational RFCs to describe non-IETF standards or\n IETF-specific modes of use of such standards. This document\n clarifies and updates the procedure used in these circumstances.\n\n1. Introduction\n\n The Internet Standards Process [RFC2026] Section 4.2.4 specifies the\n following:\n\n Standards track specifications normally must not depend on other\n standards track specifications which are at a lower maturity level\n or on non standards track specifications other than referen 3967 algorithm algorithms key management profile subject nested-reference unchanged"},{"id":"IETF RFC 4051","type":"specification","body":"IETF","designation":"RFC 4051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4051.txt","https://www.rfc-editor.org/rfc/rfc4051.pdf"],"folder":"IETF/RFC-4051","files":{"txt":{"path":"standards/IETF/RFC-4051/RFC-4051.txt","sha256":"4cb72c3ca467d4a82c8e1d046d09eb05cbbe74b249f94fc2a81bcfed9e6eb8e3"}},"tags":["nested-reference","unchanged"],"summary":"A number of Uniform Resource Identifiers (URIs) intended for use with\n XML Digital Signatures, Encryption, and Canonicalization are defined.\n These URIs identify algorithms and types of keying information.","scope_keywords":["4051","algorithm","algorithms","authentication","certificate","certificates","crl","encryption","holder","http","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4050","folder":"IETF/RFC-4050","source":"IETF/RFC-4050/RFC-4050.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 4051 A number of Uniform Resource Identifiers (URIs) intended for use with\n XML Digital Signatures, Encryption, and Canonicalization are defined.\n These URIs identify algorithms and types of keying information. 4051 algorithm algorithms authentication certificate certificates crl encryption holder http key signature signatures nested-reference unchanged"},{"id":"IETF RFC 4230","type":"specification","body":"IETF","designation":"RFC 4230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4230.txt","https://www.rfc-editor.org/rfc/rfc4230.pdf"],"folder":"IETF/RFC-4230","files":{"txt":{"path":"standards/IETF/RFC-4230/RFC-4230.txt","sha256":"3362cba1f85761a2d817ff552d9a714468a2b1fec182ceeb565cc452fc79127d"}},"tags":["nested-reference","unchanged"],"summary":"This document summarizes the security properties of RSVP. The goal\n of this analysis is to benefit from previous work done on RSVP and to\n capture knowledge about past activities.\n\nTschofenig & Graveman Informational [Page 1]\n\f\nRFC 4230 RSVP Security Properties December 2005","scope_keywords":["4230","authentication","authorization","key","management","path","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 4230 This document summarizes the security properties of RSVP. The goal\n of this analysis is to benefit from previous work done on RSVP and to\n capture knowledge about past activities.\n\nTschofenig & Graveman Informational [Page 1]\n\f\nRFC 4230 RSVP Security Properties December 2005 4230 authentication authorization key management path policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 4278","type":"specification","body":"IETF","designation":"RFC 4278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4278.txt","https://www.rfc-editor.org/rfc/rfc4278.pdf"],"folder":"IETF/RFC-4278","files":{"txt":{"path":"standards/IETF/RFC-4278/RFC-4278.txt","sha256":"6587e1311df7333a172ebb710cf7ba009fb3d70d45274d63683b78b83d6ed1cb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bellovin\nRequest for Comments: 4278 AT&T Labs Research\nCategory: Informational A. Zinin\n Alcatel\n January 2006\n\n Standards Maturity Variance Regarding the TCP MD5 Signature Option\n (RFC 2385) and the BGP-4 Specification\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n The IETF Standards Process requires that all normative references for\n a document be at the same or higher level of standardization. RFC\n 2026 section 9.1 allows the IESG to grant a variance to the standard\n practices of the IETF. This document explains why the IESG is\n considering doing so for the revised version of the BGP-4\n specification, which refers normatively to RFC 2385, \"Protection of\n BGP","scope_keywords":["4278","authentication","hash","key","management","path","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 4278 Network Working Group S. Bellovin\nRequest for Comments: 4278 AT&T Labs Research\nCategory: Informational A. Zinin\n Alcatel\n January 2006\n\n Standards Maturity Variance Regarding the TCP MD5 Signature Option\n (RFC 2385) and the BGP-4 Specification\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n The IETF Standards Process requires that all normative references for\n a document be at the same or higher level of standardization. RFC\n 2026 section 9.1 allows the IESG to grant a variance to the standard\n practices of the IETF. This document explains why the IESG is\n considering doing so for the revised version of the BGP-4\n specification, which refers normatively to RFC 2385, \"Protection of\n BGP 4278 authentication hash key management path signature tls nested-reference unchanged"},{"id":"IETF RFC 4306","type":"specification","body":"IETF","designation":"RFC 4306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4306.txt","https://www.rfc-editor.org/rfc/rfc4306.pdf"],"folder":"IETF/RFC-4306","files":{"txt":{"path":"standards/IETF/RFC-4306/RFC-4306.txt","sha256":"0b382cd939281b57d56f36eb44f594a2a8d38ba0f4e01583ac6f4038d6cee7d9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining security associations\n (SAs).\n\n This version of the IKE specification combines the contents of what\n were previously separate documents, including Internet Security\n Association and Key Management Protocol (ISAKMP, RFC 2408), IKE (RFC\n 2409), the Internet Domain of Interpretation (DOI, RFC 2407), Network\n Address Translation (NAT) Traversal, Legacy authentication, and\n remote address acquisition.\n\n Version 2 of IKE does not interoperate with version 1, but it has\n enough of the header format in common that both versions can\n unambiguously run over the same UDP port.\n\nKaufman Standards Track [Page 1]\n\f\nRFC 4306 IKEv2 December 2005","scope_keywords":["4306","algorithm","algorithms","authentication","certificate","identification","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4434","folder":"IETF/RFC-4434","source":"IETF/RFC-4434/RFC-4434.txt","version":null},{"body":"IETF","designation":"RFC 4478","folder":"IETF/RFC-4478","source":"IETF/RFC-4478/RFC-4478.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4615","folder":"IETF/RFC-4615","source":"IETF/RFC-4615/RFC-4615.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4739","folder":"IETF/RFC-4739","source":"IETF/RFC-4739/RFC-4739.txt","version":null},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4806","folder":"IETF/RFC-4806","source":"IETF/RFC-4806/RFC-4806.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4306 This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining security associations\n (SAs).\n\n This version of the IKE specification combines the contents of what\n were previously separate documents, including Internet Security\n Association and Key Management Protocol (ISAKMP, RFC 2408), IKE (RFC\n 2409), the Internet Domain of Interpretation (DOI, RFC 2407), Network\n Address Translation (NAT) Traversal, Legacy authentication, and\n remote address acquisition.\n\n Version 2 of IKE does not interoperate with version 1, but it has\n enough of the header format in common that both versions can\n unambiguously run over the same UDP port.\n\nKaufman Standards Track [Page 1]\n\f\nRFC 4306 IKEv2 December 2005 4306 algorithm algorithms authentication certificate identification key keys management nested-reference unchanged"},{"id":"IETF RFC 4346","type":"specification","body":"IETF","designation":"RFC 4346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4346.txt","https://www.rfc-editor.org/rfc/rfc4346.pdf"],"folder":"IETF/RFC-4346","files":{"txt":{"path":"standards/IETF/RFC-4346/RFC-4346.txt","sha256":"009ff1834b93340a20ff8d71c8b4f5387ea6ca2e6b293691d85cf719eeb922fd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Version 1.1 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications security\n over the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery.\n\nDierks & Rescorla Standards Track [Page 1]\n\f\nRFC 4346 The TLS Protocol April 2006","scope_keywords":["4346","attribute","attributes","authentication","certificate","certificates","key","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4680","folder":"IETF/RFC-4680","source":"IETF/RFC-4680/RFC-4680.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 4785","folder":"IETF/RFC-4785","source":"IETF/RFC-4785/RFC-4785.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5091","folder":"IETF/RFC-5091","source":"IETF/RFC-5091/RFC-5091.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5158","folder":"IETF/RFC-5158","source":"IETF/RFC-5158/RFC-5158.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5469","folder":"IETF/RFC-5469","source":"IETF/RFC-5469/RFC-5469.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7465","folder":"IETF/RFC-7465","source":"IETF/RFC-7465/RFC-7465.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 4346 This document specifies Version 1.1 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications security\n over the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery.\n\nDierks & Rescorla Standards Track [Page 1]\n\f\nRFC 4346 The TLS Protocol April 2006 4346 attribute attributes authentication certificate certificates key presentation tls nested-reference unchanged"},{"id":"IETF RFC 4462","type":"specification","body":"IETF","designation":"RFC 4462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4462.txt","https://www.rfc-editor.org/rfc/rfc4462.pdf"],"folder":"IETF/RFC-4462","files":{"txt":{"path":"standards/IETF/RFC-4462/RFC-4462.txt","sha256":"60fbad0a90ceb004435523948765af39ca6359bfe0cae5295f4a92bd9bd952cc"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Shell protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network.\n\n The Generic Security Service Application Program Interface (GSS-API)\n provides security services to callers in a mechanism-independent\n fashion.\n\n This memo describes methods for using the GSS-API for authentication\n and key exchange in SSH. It defines an SSH user authentication\n method that uses a specified GSS-API mechanism to authenticate a\n user, and a family of SSH key exchange methods that use GSS-API to\n authenticate a Diffie-Hellman key exchange.\n\n This memo also defines a new host public key algorithm that can be\n used when no operations are needed using a host's public key, and a\n new user authentication method that allows an authorization name to\n be used in conjunction with any authentication that has already\n occurred as a side-effect of GSS-AP","scope_keywords":["4462","algorithm","algorithms","authentication","authorization","encryption","key","keys","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null}],"search_text":"IETF RFC 4462 The Secure Shell protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network.\n\n The Generic Security Service Application Program Interface (GSS-API)\n provides security services to callers in a mechanism-independent\n fashion.\n\n This memo describes methods for using the GSS-API for authentication\n and key exchange in SSH. It defines an SSH user authentication\n method that uses a specified GSS-API mechanism to authenticate a\n user, and a family of SSH key exchange methods that use GSS-API to\n authenticate a Diffie-Hellman key exchange.\n\n This memo also defines a new host public key algorithm that can be\n used when no operations are needed using a host's public key, and a\n new user authentication method that allows an authorization name to\n be used in conjunction with any authentication that has already\n occurred as a side-effect of GSS-AP 4462 algorithm algorithms authentication authorization encryption key keys signature nested-reference unchanged"},{"id":"IETF RFC 4595","type":"specification","body":"IETF","designation":"RFC 4595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4595.txt","https://www.rfc-editor.org/rfc/rfc4595.pdf"],"folder":"IETF/RFC-4595","files":{"txt":{"path":"standards/IETF/RFC-4595/RFC-4595.txt","sha256":"69032931fd2d7884404b24b9ab5c63cd876dcf342b6b7325e58eb88d2bc738a7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of IKEv2 to negotiate security\n protocols and transforms for Fibre Channel as part of the Fibre\n Channel Security Association Management Protocol. This usage\n requires that IKEv2 be extended with Fibre-Channel-specific security\n protocols, transforms, and name types. This document specifies these\n IKEv2 extensions and allocates identifiers for them. Using new IKEv2\n identifiers for Fibre Channel security protocols avoids any possible\n confusion between IKEv2 negotiation for IP networks and IKEv2\n negotiation for Fibre Channel.\n\nMaino & Black Informational [Page 1]\n\f\nRFC 4595 IKEv2 in FC-SP July 2006","scope_keywords":["4595","authentication","key","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 4595 This document describes the use of IKEv2 to negotiate security\n protocols and transforms for Fibre Channel as part of the Fibre\n Channel Security Association Management Protocol. This usage\n requires that IKEv2 be extended with Fibre-Channel-specific security\n protocols, transforms, and name types. This document specifies these\n IKEv2 extensions and allocates identifiers for them. Using new IKEv2\n identifiers for Fibre Channel security protocols avoids any possible\n confusion between IKEv2 negotiation for IP networks and IKEv2\n negotiation for Fibre Channel.\n\nMaino & Black Informational [Page 1]\n\f\nRFC 4595 IKEv2 in FC-SP July 2006 4595 authentication key management policies nested-reference unchanged"},{"id":"IETF RFC 4716","type":"specification","body":"IETF","designation":"RFC 4716","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4716.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4716.txt","https://www.rfc-editor.org/rfc/rfc4716.pdf"],"folder":"IETF/RFC-4716","files":{"txt":{"path":"standards/IETF/RFC-4716/RFC-4716.txt","sha256":"ce350bcd39336f532a92e45ea8002ca858992a9e2fe9a68f2acae53cf75b1000"}},"tags":["nested-reference","unchanged"],"summary":"This document formally documents an existing public key file format\n in use for exchanging public keys between different Secure Shell\n (SSH) implementations.\n\n In addition, this document defines a standard textual representation\n for SSH public key fingerprints.","scope_keywords":["4716","authentication","certificate","key","keys","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null}],"search_text":"IETF RFC 4716 This document formally documents an existing public key file format\n in use for exchanging public keys between different Secure Shell\n (SSH) implementations.\n\n In addition, this document defines a standard textual representation\n for SSH public key fingerprints. 4716 authentication certificate key keys presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 4822","type":"specification","body":"IETF","designation":"RFC 4822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4822.txt","https://www.rfc-editor.org/rfc/rfc4822.pdf"],"folder":"IETF/RFC-4822","files":{"txt":{"path":"standards/IETF/RFC-4822/RFC-4822.txt","sha256":"1bd9819f2429149336e40d1a06d9f9e36a453e34705cb1d9555f2d97f410d1a9"}},"tags":["nested-reference","unchanged"],"summary":"This note describes a revision to the RIPv2 Cryptographic\n Authentication mechanism originally specified in RFC 2082. This\n document obsoletes RFC 2082 and updates RFC 2453. This document adds\n details of how the SHA family of hash algorithms can be used with\n RIPv2 Cryptographic Authentication, whereas the original document\n only specified the use of Keyed-MD5. Also, this document clarifies a\n potential issue with an active attack on this mechanism and adds\n significant text to the Security Considerations section.\n\nAtkinson & Fanto Standards Track [Page 1]\n\f\nRFC 4822 RIPv2 Cryptographic Authentication February 2007\n\n1. Introduction\n\n Growth in the Internet has made us aware of the need for improved\n authentication of routing information. RIPv2 provides for\n unauthenticated service (as in classical RIP), or password\n authentication. Both are vulnerable to passive attacks currently\n wides","scope_keywords":["4822","algorithm","algorithms","authentication","hash","hashing","key","keys","management","pid","policy","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null}],"search_text":"IETF RFC 4822 This note describes a revision to the RIPv2 Cryptographic\n Authentication mechanism originally specified in RFC 2082. This\n document obsoletes RFC 2082 and updates RFC 2453. This document adds\n details of how the SHA family of hash algorithms can be used with\n RIPv2 Cryptographic Authentication, whereas the original document\n only specified the use of Keyed-MD5. Also, this document clarifies a\n potential issue with an active attack on this mechanism and adds\n significant text to the Security Considerations section.\n\nAtkinson & Fanto Standards Track [Page 1]\n\f\nRFC 4822 RIPv2 Cryptographic Authentication February 2007\n\n1. Introduction\n\n Growth in the Internet has made us aware of the need for improved\n authentication of routing information. RIPv2 provides for\n unauthenticated service (as in classical RIP), or password\n authentication. Both are vulnerable to passive attacks currently\n wides 4822 algorithm algorithms authentication hash hashing key keys management pid policy risk trust nested-reference unchanged"},{"id":"IETF RFC 4895","type":"specification","body":"IETF","designation":"RFC 4895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4895.txt","https://www.rfc-editor.org/rfc/rfc4895.pdf"],"folder":"IETF/RFC-4895","files":{"txt":{"path":"standards/IETF/RFC-4895/RFC-4895.txt","sha256":"0ab0ee55c0f7e94a62edc07e0ddc53f9231f946cbf8ab2e3a317a74e09f7afd9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new chunk type, several parameters, and\n procedures for the Stream Control Transmission Protocol (SCTP). This\n new chunk type can be used to authenticate SCTP chunks by using\n shared keys between the sender and receiver. The new parameters are\n used to establish the shared keys.\n\nTuexen, et al. Standards Track [Page 1]\n\f\nRFC 4895 SCTP Authentication Chunk August 2007","scope_keywords":["4895","algorithm","authentication","hash","key","keys","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null}],"search_text":"IETF RFC 4895 This document describes a new chunk type, several parameters, and\n procedures for the Stream Control Transmission Protocol (SCTP). This\n new chunk type can be used to authenticate SCTP chunks by using\n shared keys between the sender and receiver. The new parameters are\n used to establish the shared keys.\n\nTuexen, et al. Standards Track [Page 1]\n\f\nRFC 4895 SCTP Authentication Chunk August 2007 4895 algorithm authentication hash key keys tls nested-reference unchanged"},{"id":"IETF RFC 4941","type":"specification","body":"IETF","designation":"RFC 4941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4941.txt","https://www.rfc-editor.org/rfc/rfc4941.pdf"],"folder":"IETF/RFC-4941","files":{"txt":{"path":"standards/IETF/RFC-4941/RFC-4941.txt","sha256":"8149155f2af7c2c14700dac8de6529ac404e8d62bcc94341e4237c76f4d76890"}},"tags":["nested-reference","unchanged"],"summary":"Nodes use IPv6 stateless address autoconfiguration to generate\n addresses using a combination of locally available information and\n information advertised by routers. Addresses are formed by combining\n network prefixes with an interface identifier. On an interface that\n contains an embedded IEEE Identifier, the interface identifier is\n typically derived from it. On other interface types, the interface\n identifier is generated through other means, for example, via random\n number generation. This document describes an extension to IPv6\n stateless address autoconfiguration for interfaces whose interface\n identifier is derived from an IEEE identifier. Use of the extension\n causes nodes to generate global scope addresses from interface\n identifiers that change over time, even in cases where the interface\n contains an embedded IEEE identifier. Changing the interface\n identifier (and the global","scope_keywords":["4941","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 4941 Nodes use IPv6 stateless address autoconfiguration to generate\n addresses using a combination of locally available information and\n information advertised by routers. Addresses are formed by combining\n network prefixes with an interface identifier. On an interface that\n contains an embedded IEEE Identifier, the interface identifier is\n typically derived from it. On other interface types, the interface\n identifier is generated through other means, for example, via random\n number generation. This document describes an extension to IPv6\n stateless address autoconfiguration for interfaces whose interface\n identifier is derived from an IEEE identifier. Use of the extension\n causes nodes to generate global scope addresses from interface\n identifiers that change over time, even in cases where the interface\n contains an embedded IEEE identifier. Changing the interface\n identifier (and the global 4941 algorithm key nested-reference unchanged"},{"id":"IETF RFC 5036","type":"specification","body":"IETF","designation":"RFC 5036","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5036.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5036.txt","https://www.rfc-editor.org/rfc/rfc5036.pdf"],"folder":"IETF/RFC-5036","files":{"txt":{"path":"standards/IETF/RFC-5036/RFC-5036.txt","sha256":"d96eb0c06d0a1ec38c00364f42d1276b735c92bcf21cdbebecb92ef37a35692c"}},"tags":["nested-reference","unchanged"],"summary":"The architecture for Multiprotocol Label Switching (MPLS) is\n described in RFC 3031. A fundamental concept in MPLS is that two\n Label Switching Routers (LSRs) must agree on the meaning of the\n labels used to forward traffic between and through them. This common\n understanding is achieved by using a set of procedures, called a\n label distribution protocol, by which one LSR informs another of\n label bindings it has made. This document defines a set of such\n procedures called LDP (for Label Distribution Protocol) by which LSRs\n distribute labels to support MPLS forwarding along normally routed\n paths.","scope_keywords":["5036","management","path","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5036 The architecture for Multiprotocol Label Switching (MPLS) is\n described in RFC 3031. A fundamental concept in MPLS is that two\n Label Switching Routers (LSRs) must agree on the meaning of the\n labels used to forward traffic between and through them. This common\n understanding is achieved by using a set of procedures, called a\n label distribution protocol, by which one LSR informs another of\n label bindings it has made. This document defines a set of such\n procedures called LDP (for Label Distribution Protocol) by which LSRs\n distribute labels to support MPLS forwarding along normally routed\n paths. 5036 management path signature nested-reference unchanged"},{"id":"IETF RFC 5072","type":"specification","body":"IETF","designation":"RFC 5072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5072.txt","https://www.rfc-editor.org/rfc/rfc5072.pdf"],"folder":"IETF/RFC-5072","files":{"txt":{"path":"standards/IETF/RFC-5072/RFC-5072.txt","sha256":"df57e1e791b783797fc49cf3bb59064f04b75264200b60cb76faa23382649291"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method of\n encapsulating network-layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for sending IPv6 packets over PPP\n links, the NCP for establishing and configuring the IPv6 over PPP,\n and the method for forming IPv6 link-local addresses on PPP links.\n\n It also specifies the conditions for performing Duplicate Address\n Detection on IPv6 global unicast addresses configured for PPP links\n either through stateful or stateless address autoconfiguration.\n\n This document obsoletes RFC 2472.\n\nVarada, et al. Standards Track [Page 1]\n\f\nRFC 5072 IP Version 6 over PPP September 2007","scope_keywords":["5072","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 5072 The Point-to-Point Protocol (PPP) provides a standard method of\n encapsulating network-layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for sending IPv6 packets over PPP\n links, the NCP for establishing and configuring the IPv6 over PPP,\n and the method for forming IPv6 link-local addresses on PPP links.\n\n It also specifies the conditions for performing Duplicate Address\n Detection on IPv6 global unicast addresses configured for PPP links\n either through stateful or stateless address autoconfiguration.\n\n This document obsoletes RFC 2472.\n\nVarada, et al. Standards Track [Page 1]\n\f\nRFC 5072 IP Version 6 over PPP September 2007 5072 authentication key nested-reference unchanged"},{"id":"IETF RFC 5147","type":"specification","body":"IETF","designation":"RFC 5147","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5147.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5147.txt","https://www.rfc-editor.org/rfc/rfc5147.pdf"],"folder":"IETF/RFC-5147","files":{"txt":{"path":"standards/IETF/RFC-5147/RFC-5147.txt","sha256":"c8fff6f21a8c68a15642d00ff0fbb97ae7cd1613ee02c2782ab7671d6b6a24f4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines URI fragment identifiers for text/plain MIME\n entities. These fragment identifiers make it possible to refer to\n parts of a text/plain MIME entity, either identified by character\n position or range, or by line position or range. Fragment\n identifiers may also contain information for integrity checks to make\n them more robust.\n\nWilde & Duerst Standards Track [Page 1]\n\f\nRFC 5147 text/plain Fragment Identifiers April 2008","scope_keywords":["5147","attribute","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null}],"search_text":"IETF RFC 5147 This memo defines URI fragment identifiers for text/plain MIME\n entities. These fragment identifiers make it possible to refer to\n parts of a text/plain MIME entity, either identified by character\n position or range, or by line position or range. Fragment\n identifiers may also contain information for integrity checks to make\n them more robust.\n\nWilde & Duerst Standards Track [Page 1]\n\f\nRFC 5147 text/plain Fragment Identifiers April 2008 5147 attribute identification presentation nested-reference unchanged"},{"id":"IETF RFC 5246","type":"specification","body":"IETF","designation":"RFC 5246","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5246.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5246.txt","https://www.rfc-editor.org/rfc/rfc5246.pdf"],"folder":"IETF/RFC-5246","files":{"txt":{"path":"standards/IETF/RFC-5246/RFC-5246.txt","sha256":"2ebe1b8e651696aeacc8ab3848bedb465505737901ea3b691acf40c392958feb"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Version 1.2 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications security\n over the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery.","scope_keywords":["5246","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","key","presentation","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"},{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5469","folder":"IETF/RFC-5469","source":"IETF/RFC-5469/RFC-5469.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 5932","folder":"IETF/RFC-5932","source":"IETF/RFC-5932/RFC-5932.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7366","folder":"IETF/RFC-7366","source":"IETF/RFC-7366/RFC-7366.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7465","folder":"IETF/RFC-7465","source":"IETF/RFC-7465/RFC-7465.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7685","folder":"IETF/RFC-7685","source":"IETF/RFC-7685/RFC-7685.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 5246 This document specifies Version 1.2 of the Transport Layer Security\n (TLS) protocol. The TLS protocol provides communications security\n over the Internet. The protocol allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping,\n tampering, or message forgery. 5246 algorithm algorithms attribute attributes authentication certificate certificates key presentation signature tls nested-reference unchanged"},{"id":"IETF RFC 5393","type":"specification","body":"IETF","designation":"RFC 5393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5393.txt","https://www.rfc-editor.org/rfc/rfc5393.pdf"],"folder":"IETF/RFC-5393","files":{"txt":{"path":"standards/IETF/RFC-5393/RFC-5393.txt","sha256":"fdf0824bcb6658993a4dd619cc2b7b3a7db4669ece383dd691175b145be2d541"}},"tags":["nested-reference","unchanged"],"summary":"This document normatively updates RFC 3261, the Session Initiation\n Protocol (SIP), to address a security vulnerability identified in SIP\n proxy behavior. This vulnerability enables an attack against SIP\n networks where a small number of legitimate, even authorized, SIP\n requests can stimulate massive amounts of proxy-to-proxy traffic.\n\n This document strengthens loop-detection requirements on SIP proxies\n when they fork requests (that is, forward a request to more than one\n destination). It also corrects and clarifies the description of the\n loop-detection algorithm such proxies are required to implement.\n Additionally, this document defines a Max-Breadth mechanism for\n limiting the number of concurrent branches pursued for any given\n request.\n\nSparks, et al. Standards Track [Page 1]\n\f\nRFC 5393 Amplification Vulnerability in SIP December 2008","scope_keywords":["5393","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 5393 This document normatively updates RFC 3261, the Session Initiation\n Protocol (SIP), to address a security vulnerability identified in SIP\n proxy behavior. This vulnerability enables an attack against SIP\n networks where a small number of legitimate, even authorized, SIP\n requests can stimulate massive amounts of proxy-to-proxy traffic.\n\n This document strengthens loop-detection requirements on SIP proxies\n when they fork requests (that is, forward a request to more than one\n destination). It also corrects and clarifies the description of the\n loop-detection algorithm such proxies are required to implement.\n Additionally, this document defines a Max-Breadth mechanism for\n limiting the number of concurrent branches pursued for any given\n request.\n\nSparks, et al. Standards Track [Page 1]\n\f\nRFC 5393 Amplification Vulnerability in SIP December 2008 5393 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5440","type":"specification","body":"IETF","designation":"RFC 5440","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5440.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5440.txt","https://www.rfc-editor.org/rfc/rfc5440.pdf"],"folder":"IETF/RFC-5440","files":{"txt":{"path":"standards/IETF/RFC-5440/RFC-5440.txt","sha256":"2b7b7c9d2980aecd8c46637ce5f562d320eb4bb9718f3428d5a582ea2c700ae2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Path Computation Element (PCE)\n Communication Protocol (PCEP) for communications between a Path\n Computation Client (PCC) and a PCE, or between two PCEs. Such\n interactions include path computation requests and path computation\n replies as well as notifications of specific states related to the\n use of a PCE in the context of Multiprotocol Label Switching (MPLS)\n and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed\n to be flexible and extensible so as to easily allow for the addition\n of further messages and objects, should further requirements be\n expressed in the future.\n\nVasseur & Le Roux Standards Track [Page 2]\n\f\nRFC 5440 PCEP March 2009","scope_keywords":["5440","http","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 5440 This document specifies the Path Computation Element (PCE)\n Communication Protocol (PCEP) for communications between a Path\n Computation Client (PCC) and a PCE, or between two PCEs. Such\n interactions include path computation requests and path computation\n replies as well as notifications of specific states related to the\n use of a PCE in the context of Multiprotocol Label Switching (MPLS)\n and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed\n to be flexible and extensible so as to easily allow for the addition\n of further messages and objects, should further requirements be\n expressed in the future.\n\nVasseur & Le Roux Standards Track [Page 2]\n\f\nRFC 5440 PCEP March 2009 5440 http license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5456","type":"specification","body":"IETF","designation":"RFC 5456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5456.txt","https://www.rfc-editor.org/rfc/rfc5456.pdf"],"folder":"IETF/RFC-5456","files":{"txt":{"path":"standards/IETF/RFC-5456/RFC-5456.txt","sha256":"1cf2299c5e511d51069206089d674550420bc0df9c6b1daef1725d8316308d30"}},"tags":["nested-reference","unchanged"],"summary":"This document describes IAX, the Inter-Asterisk eXchange protocol, an\n application-layer control and media protocol for creating, modifying,\n and terminating multimedia sessions over Internet Protocol (IP)\n networks. IAX was developed by the open source community for the\n Asterisk Private Branch Exchange (PBX) and is targeted primarily at\n Voice over Internet Protocol (VoIP) call control, but it can be used\n with streaming video or any other type of multimedia.\n\n IAX is an \"all in one\" protocol for handling multimedia in IP\n networks. It combines both control and media services in the same\n protocol. In addition, IAX uses a single UDP data stream on a static\n port greatly simplifying Network Address Translation (NAT) gateway\n traversal, eliminating the need for other protocols to work around\n NAT, and simplifying network and firewall management. IAX employs a\n compact encoding that decre","scope_keywords":["5456","encryption","http","license","management","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5457","folder":"IETF/RFC-5457","source":"IETF/RFC-5457/RFC-5457.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5456 This document describes IAX, the Inter-Asterisk eXchange protocol, an\n application-layer control and media protocol for creating, modifying,\n and terminating multimedia sessions over Internet Protocol (IP)\n networks. IAX was developed by the open source community for the\n Asterisk Private Branch Exchange (PBX) and is targeted primarily at\n Voice over Internet Protocol (VoIP) call control, but it can be used\n with streaming video or any other type of multimedia.\n\n IAX is an \"all in one\" protocol for handling multimedia in IP\n networks. It combines both control and media services in the same\n protocol. In addition, IAX uses a single UDP data stream on a static\n port greatly simplifying Network Address Translation (NAT) gateway\n traversal, eliminating the need for other protocols to work around\n NAT, and simplifying network and firewall management. IAX employs a\n compact encoding that decre 5456 encryption http license management path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5655","type":"specification","body":"IETF","designation":"RFC 5655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5655.txt","https://www.rfc-editor.org/rfc/rfc5655.pdf"],"folder":"IETF/RFC-5655","files":{"txt":{"path":"standards/IETF/RFC-5655/RFC-5655.txt","sha256":"f2c90baf436705b56353d9db68ba10469dec2f065aa071080e20dfeb870bb525"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a file format for the storage of flow data\n based upon the IP Flow Information Export (IPFIX) protocol. It\n proposes a set of requirements for flat-file, binary flow data file\n formats, then specifies the IPFIX File format to meet these\n requirements based upon IPFIX Messages. This IPFIX File format is\n designed to facilitate interoperability and reusability among a wide\n variety of flow storage, processing, and analysis tools.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as t","scope_keywords":["5655","audit","authentication","certificate","encryption","http","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 5655 This document describes a file format for the storage of flow data\n based upon the IP Flow Information Export (IPFIX) protocol. It\n proposes a set of requirements for flat-file, binary flow data file\n formats, then specifies the IPFIX File format to meet these\n requirements based upon IPFIX Messages. This IPFIX File format is\n designed to facilitate interoperability and reusability among a wide\n variety of flow storage, processing, and analysis tools.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as t 5655 audit authentication certificate encryption http license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5880","type":"specification","body":"IETF","designation":"RFC 5880","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5880.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5880.txt","https://www.rfc-editor.org/rfc/rfc5880.pdf"],"folder":"IETF/RFC-5880","files":{"txt":{"path":"standards/IETF/RFC-5880/RFC-5880.txt","sha256":"45a7f8fcc04991c22d9efb1419aee4d9870cf1b7aa4b16a930e66a248146c61d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol intended to detect faults in the\n bidirectional path between two forwarding engines, including\n interfaces, data link(s), and to the extent possible the forwarding\n engines themselves, with potentially very low latency. It operates\n independently of media, data protocols, and routing protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5880.\n\nCopy","scope_keywords":["5880","authentication","http","key","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5880 This document describes a protocol intended to detect faults in the\n bidirectional path between two forwarding engines, including\n interfaces, data link(s), and to the extent possible the forwarding\n engines themselves, with potentially very low latency. It operates\n independently of media, data protocols, and routing protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5880.\n\nCopy 5880 authentication http key license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 5996","type":"specification","body":"IETF","designation":"RFC 5996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5996.txt","https://www.rfc-editor.org/rfc/rfc5996.pdf"],"folder":"IETF/RFC-5996","files":{"txt":{"path":"standards/IETF/RFC-5996/RFC-5996.txt","sha256":"1ba1dffd5eefd6688dddd08d2ea2dfacf6b31cf5d292e15cbc283783c3c3d7ff"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining Security Associations\n (SAs). This document replaces and updates RFC 4306, and includes all\n of the clarifications from RFC 4718.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5996.\n\nKaufman, et al. Stand","scope_keywords":["5996","algorithm","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6568","folder":"IETF/RFC-6568","source":"IETF/RFC-6568/RFC-6568.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 5996 This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining Security Associations\n (SAs). This document replaces and updates RFC 4306, and includes all\n of the clarifications from RFC 4718.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5996.\n\nKaufman, et al. Stand 5996 algorithm authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6151","type":"specification","body":"IETF","designation":"RFC 6151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6151.txt","https://www.rfc-editor.org/rfc/rfc6151.pdf"],"folder":"IETF/RFC-6151","files":{"txt":{"path":"standards/IETF/RFC-6151/RFC-6151.txt","sha256":"4e5599d99a0d335560c0a47a959e91469ee47d49edcd224aa2b7b0b0a6b8588d"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the security considerations for the MD5 message\n digest algorithm. It also updates the security considerations for\n HMAC-MD5.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6151.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n do","scope_keywords":["6151","algorithm","algorithms","authentication","certificate","certificates","hash","http","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7693","folder":"IETF/RFC-7693","source":"IETF/RFC-7693/RFC-7693.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 6151 This document updates the security considerations for the MD5 message\n digest algorithm. It also updates the security considerations for\n HMAC-MD5.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6151.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n do 6151 algorithm algorithms authentication certificate certificates hash http key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6176","type":"specification","body":"IETF","designation":"RFC 6176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6176.txt","https://www.rfc-editor.org/rfc/rfc6176.pdf"],"folder":"IETF/RFC-6176","files":{"txt":{"path":"standards/IETF/RFC-6176/RFC-6176.txt","sha256":"026957e8ee1cbe85ad04a1cf3a0fae1ad71fa001e809c813a63d79d3bd79a3eb"}},"tags":["nested-reference","unchanged"],"summary":"This document requires that when Transport Layer Security (TLS)\n clients and servers establish connections, they never negotiate the\n use of Secure Sockets Layer (SSL) version 2.0. This document updates\n the backward compatibility sections found in the Transport Layer\n Security (TLS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6176.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust ","scope_keywords":["6176","algorithm","algorithms","authentication","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 6176 This document requires that when Transport Layer Security (TLS)\n clients and servers establish connections, they never negotiate the\n use of Secure Sockets Layer (SSL) version 2.0. This document updates\n the backward compatibility sections found in the Transport Layer\n Security (TLS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6176.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust  6176 algorithm algorithms authentication encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6210","type":"specification","body":"IETF","designation":"RFC 6210","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6210.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6210.txt","https://www.rfc-editor.org/rfc/rfc6210.pdf"],"folder":"IETF/RFC-6210","files":{"txt":{"path":"standards/IETF/RFC-6210/RFC-6210.txt","sha256":"0df51d9282d48351062181c6e4aacb6b304502399958b82e3d04b13c3f491def"}},"tags":["nested-reference","unchanged"],"summary":"New hash algorithms are being developed that may include parameters.\n Cryptographic Message Syntax (CMS) has not currently defined any hash\n algorithms with parameters, but anecdotal evidence suggests that\n defining one could cause major problems. This document defines just\n such an algorithm and describes how to use it so that experiments can\n be run to find out how bad including hash parameters will be.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG).","scope_keywords":["6210","algorithm","algorithms","hash","hashing","http","identification","license","path","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null}],"search_text":"IETF RFC 6210 New hash algorithms are being developed that may include parameters.\n Cryptographic Message Syntax (CMS) has not currently defined any hash\n algorithms with parameters, but anecdotal evidence suggests that\n defining one could cause major problems. This document defines just\n such an algorithm and describes how to use it so that experiments can\n be run to find out how bad including hash parameters will be.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). 6210 algorithm algorithms hash hashing http identification license path signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6929","type":"specification","body":"IETF","designation":"RFC 6929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6929.txt","https://www.rfc-editor.org/rfc/rfc6929.pdf"],"folder":"IETF/RFC-6929","files":{"txt":{"path":"standards/IETF/RFC-6929/RFC-6929.txt","sha256":"60b91ebf617adab6dc278dd3e86058a736426b1e6b68b319df1632aa60a5c9e1"}},"tags":["nested-reference","unchanged"],"summary":"The Remote Authentication Dial-In User Service (RADIUS) protocol is\n nearing exhaustion of its current 8-bit Attribute Type space. In\n addition, experience shows a growing need for complex grouping, along\n with attributes that can carry more than 253 octets of data. This\n document defines changes to RADIUS that address all of the above\n problems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i","scope_keywords":["6929","attribute","attributes","audit","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 6929 The Remote Authentication Dial-In User Service (RADIUS) protocol is\n nearing exhaustion of its current 8-bit Attribute Type space. In\n addition, experience shows a growing need for complex grouping, along\n with attributes that can carry more than 253 octets of data. This\n document defines changes to RADIUS that address all of the above\n problems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i 6929 attribute attributes audit authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7292","type":"specification","body":"IETF","designation":"RFC 7292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7292.txt","https://www.rfc-editor.org/rfc/rfc7292.pdf"],"folder":"IETF/RFC-7292","files":{"txt":{"path":"standards/IETF/RFC-7292/RFC-7292.txt","sha256":"168ce6749ac36f9a03c105e29b968ebe6f0d77cefce0200857f1d82d7de6cbad"}},"tags":["nested-reference","unchanged"],"summary":"PKCS #12 v1.1 describes a transfer syntax for personal identity\n information, including private keys, certificates, miscellaneous\n secrets, and extensions. Machines, applications, browsers, Internet\n kiosks, and so on, that support this standard will allow a user to\n import, export, and exercise a single set of personal identity\n information. This standard supports direct transfer of personal\n information under several privacy and integrity modes.\n\n This document represents a republication of PKCS #12 v1.1 from RSA\n Laboratories' Public Key Cryptography Standard (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\nIESG Note\n\n The IESG thanks RSA Laboratories for transferring change control to\n the IETF. Enhancements to this specification that preserve backward\n compatibility are expected in an upcoming IETF Standards Track\n document.\n\nMoriarty, et al. Infor","scope_keywords":["7292","authentication","certificate","certificates","crl","encryption","http","key","keys","license","policies","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"IETF RFC 7292 PKCS #12 v1.1 describes a transfer syntax for personal identity\n information, including private keys, certificates, miscellaneous\n secrets, and extensions. Machines, applications, browsers, Internet\n kiosks, and so on, that support this standard will allow a user to\n import, export, and exercise a single set of personal identity\n information. This standard supports direct transfer of personal\n information under several privacy and integrity modes.\n\n This document represents a republication of PKCS #12 v1.1 from RSA\n Laboratories' Public Key Cryptography Standard (PKCS) series. By\n publishing this RFC, change control is transferred to the IETF.\n\nIESG Note\n\n The IESG thanks RSA Laboratories for transferring change control to\n the IETF. Enhancements to this specification that preserve backward\n compatibility are expected in an upcoming IETF Standards Track\n document.\n\nMoriarty, et al. Infor 7292 authentication certificate certificates crl encryption http key keys license policies signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 7296","type":"specification","body":"IETF","designation":"RFC 7296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7296.txt","https://www.rfc-editor.org/rfc/rfc7296.pdf"],"folder":"IETF/RFC-7296","files":{"txt":{"path":"standards/IETF/RFC-7296/RFC-7296.txt","sha256":"b6c1bf3921e85dd3674f427ffcaded0209e1f9718e8d601e2f918371f46329a1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining Security Associations\n (SAs). This document obsoletes RFC 5996, and includes all of the\n errata for it. It advances IKEv2 to be an Internet Standard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7296.\n\nK","scope_keywords":["7296","algorithm","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7539","folder":"IETF/RFC-7539","source":"IETF/RFC-7539/RFC-7539.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 7296 This document describes version 2 of the Internet Key Exchange (IKE)\n protocol. IKE is a component of IPsec used for performing mutual\n authentication and establishing and maintaining Security Associations\n (SAs). This document obsoletes RFC 5996, and includes all of the\n errata for it. It advances IKEv2 to be an Internet Standard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7296.\n\nK 7296 algorithm authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7568","type":"specification","body":"IETF","designation":"RFC 7568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7568.txt","https://www.rfc-editor.org/rfc/rfc7568.pdf"],"folder":"IETF/RFC-7568","files":{"txt":{"path":"standards/IETF/RFC-7568/RFC-7568.txt","sha256":"84e8adcafd4cde891e258342f9d5c3381f746d0ff40b196a8b83bb0b6a43c7d1"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Sockets Layer version 3.0 (SSLv3), as specified in RFC\n 6101, is not sufficiently secure. This document requires that SSLv3\n not be used. The replacement versions, in particular, Transport\n Layer Security (TLS) 1.2 (RFC 5246), are considerably more secure and\n capable protocols.\n\n This document updates the backward compatibility section of RFC 5246\n and its predecessors to prohibit fallback to SSLv3.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov","scope_keywords":["7568","algorithm","algorithms","authentication","encryption","hash","http","key","license","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7568 The Secure Sockets Layer version 3.0 (SSLv3), as specified in RFC\n 6101, is not sufficiently secure. This document requires that SSLv3\n not be used. The replacement versions, in particular, Transport\n Layer Security (TLS) 1.2 (RFC 5246), are considerably more secure and\n capable protocols.\n\n This document updates the backward compatibility section of RFC 5246\n and its predecessors to prohibit fallback to SSLv3.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov 7568 algorithm algorithms authentication encryption hash http key license signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8122","type":"specification","body":"IETF","designation":"RFC 8122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8122.txt","https://www.rfc-editor.org/rfc/rfc8122.pdf"],"folder":"IETF/RFC-8122","files":{"txt":{"path":"standards/IETF/RFC-8122/RFC-8122.txt","sha256":"ad0b13b65c0ff5d30637774cde870daf57629cf653845b5dd07ca1bfd7c9e06e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to establish secure connection-oriented\n media transport sessions over the Transport Layer Security (TLS)\n protocol using the Session Description Protocol (SDP). It defines\n the SDP protocol identifier, 'TCP/TLS'. It also defines the syntax\n and semantics for an SDP 'fingerprint' attribute that identifies the\n certificate that will be presented for the TLS session. This\n mechanism allows media transport over TLS connections to be\n established securely, so long as the integrity of session\n descriptions is assured.\n\n This document obsoletes RFC 4572 by clarifying the usage of multiple\n fingerprints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b","scope_keywords":["8122","attribute","authentication","certificate","certificates","hash","http","identification","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 8122 This document specifies how to establish secure connection-oriented\n media transport sessions over the Transport Layer Security (TLS)\n protocol using the Session Description Protocol (SDP). It defines\n the SDP protocol identifier, 'TCP/TLS'. It also defines the syntax\n and semantics for an SDP 'fingerprint' attribute that identifies the\n certificate that will be presented for the TLS session. This\n mechanism allows media transport over TLS connections to be\n established securely, so long as the integrity of session\n descriptions is assured.\n\n This document obsoletes RFC 4572 by clarifying the usage of multiple\n fingerprints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b 8122 attribute authentication certificate certificates hash http identification license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8573","type":"specification","body":"IETF","designation":"RFC 8573","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8573.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8573.txt","https://www.rfc-editor.org/rfc/rfc8573.pdf"],"folder":"IETF/RFC-8573","files":{"txt":{"path":"standards/IETF/RFC-8573/RFC-8573.txt","sha256":"acb139faf1cc1af44a9e6eb6757d431b6a54cb5632d6822534c30e88ea1fbfe3"}},"tags":["nested-reference","unchanged"],"summary":"The Network Time Protocol (NTP), as described in RFC 5905, states\n that NTP packets should be authenticated by appending NTP data to a\n 128-bit key and hashing the result with MD5 to obtain a 128-bit tag.\n This document deprecates MD5-based authentication, which is\n considered too weak, and recommends the use of AES-CMAC as described\n in RFC 4493 as a replacement.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://w","scope_keywords":["8573","algorithm","algorithms","authentication","hash","hashing","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null}],"search_text":"IETF RFC 8573 The Network Time Protocol (NTP), as described in RFC 5905, states\n that NTP packets should be authenticated by appending NTP data to a\n 128-bit key and hashing the result with MD5 to obtain a 128-bit tag.\n This document deprecates MD5-based authentication, which is\n considered too weak, and recommends the use of AES-CMAC as described\n in RFC 4493 as a replacement.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://w 8573 algorithm algorithms authentication hash hashing http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1668","type":"specification","body":"IETF","designation":"RFC 1668","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1668.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1668.txt","https://www.rfc-editor.org/rfc/rfc1668.pdf"],"folder":"IETF/RFC-1668","files":{"txt":{"path":"standards/IETF/RFC-1668/RFC-1668.txt","sha256":"09f7535b43248636c9d9b160ed1a4760b82e9fcd349cd4d942db758e73eb84f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Estrin\nRequest for Comments: 1668 USC\nCategory: Informational T. Li\n Cisco Systems\n Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n August 1994\n\n Unified Routing Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n1. IPng Requirements\n\n The following list provides requirements on the IPng from the\n perspective of the Unified Routing Architecture, as describe in RFC\n 1322.\n\n 1. To provide scalable routing, IPng addressing must provide support","scope_keywords":["1668","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1668 Network Working Group D. Estrin\nRequest for Comments: 1668 USC\nCategory: Informational T. Li\n Cisco Systems\n Y. Rekhter\n T.J. Watson Research Center, IBM Corp.\n August 1994\n\n Unified Routing Requirements for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n1. IPng Requirements\n\n The following list provides requirements on the IPng from the\n perspective of the Unified Routing Architecture, as describe in RFC\n 1322.\n\n 1. To provide scalable routing, IPng addressing must provide support 1668 algorithm path nested-reference unchanged"},{"id":"IETF RFC 2147","type":"specification","body":"IETF","designation":"RFC 2147","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2147.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2147.txt","https://www.rfc-editor.org/rfc/rfc2147.pdf"],"folder":"IETF/RFC-2147","files":{"txt":{"path":"standards/IETF/RFC-2147/RFC-2147.txt","sha256":"2a18fbda2b0eae3e7a327bb9e6fd675fe7d10d9a5de92e7db81906129ae3ef98"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman\nRequest for Comments: 2147 Berkeley Software Design, Inc.\nUpdates: 1883 May 1997\nCategory: Standards Track\n\n TCP and UDP over IPv6 Jumbograms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n IPv6 supports datagrams larger than 65535 bytes long, often referred\n to as jumbograms, through use of the Jumbo Payload hop-by-hop option\n [Deering95]. The UDP protocol has a 16-bit length field that keeps\n it from being able to make use of jumbograms, and though TCP does not\n have a length field, both the MSS option and the Urgent field are\n co","scope_keywords":["2147"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null}],"search_text":"IETF RFC 2147 Network Working Group D. Borman\nRequest for Comments: 2147 Berkeley Software Design, Inc.\nUpdates: 1883 May 1997\nCategory: Standards Track\n\n TCP and UDP over IPv6 Jumbograms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n IPv6 supports datagrams larger than 65535 bytes long, often referred\n to as jumbograms, through use of the Jumbo Payload hop-by-hop option\n [Deering95]. The UDP protocol has a 16-bit length field that keeps\n it from being able to make use of jumbograms, and though TCP does not\n have a length field, both the MSS option and the Urgent field are\n co 2147 nested-reference unchanged"},{"id":"IETF RFC 2675","type":"specification","body":"IETF","designation":"RFC 2675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2675.txt","https://www.rfc-editor.org/rfc/rfc2675.pdf"],"folder":"IETF/RFC-2675","files":{"txt":{"path":"standards/IETF/RFC-2675/RFC-2675.txt","sha256":"06a84615bc49ab1b3ffaa5e84a6572235ccd47726ed34fc0118ec799834c0eab"}},"tags":["nested-reference","unchanged"],"summary":"A \"jumbogram\" is an IPv6 packet containing a payload longer than\n 65,535 octets. This document describes the IPv6 Jumbo Payload\n option, which provides the means of specifying such large payload\n lengths. It also describes the changes needed to TCP and UDP to make\n use of jumbograms.\n\n Jumbograms are relevant only to IPv6 nodes that may be attached to\n links with a link MTU greater than 65,575 octets, and need not be\n implemented or understood by IPv6 nodes that do not support\n attachment to links with such large MTUs.\n\n1. Introduction\n\n jumbo (jum'bO),\n\n n., pl. -bos, adj.\n -n.\n 1. a person, animal, or thing very large of its kind.\n -adj.\n 2. very large: the jumbo box of cereal.\n\n [1800-10; orig. uncert.; popularized as the name of a large\n elephant purchased and exhibited by P.T. Barnum in 1882]\n\n -- www.infoplease.com\n\nBorman, et al. Standards Track [Page 1]\n\f\nRFC 2675 IPv6 Jumbograms","scope_keywords":["2675"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IETF RFC 2675 A \"jumbogram\" is an IPv6 packet containing a payload longer than\n 65,535 octets. This document describes the IPv6 Jumbo Payload\n option, which provides the means of specifying such large payload\n lengths. It also describes the changes needed to TCP and UDP to make\n use of jumbograms.\n\n Jumbograms are relevant only to IPv6 nodes that may be attached to\n links with a link MTU greater than 65,575 octets, and need not be\n implemented or understood by IPv6 nodes that do not support\n attachment to links with such large MTUs.\n\n1. Introduction\n\n jumbo (jum'bO),\n\n n., pl. -bos, adj.\n -n.\n 1. a person, animal, or thing very large of its kind.\n -adj.\n 2. very large: the jumbo box of cereal.\n\n [1800-10; orig. uncert.; popularized as the name of a large\n elephant purchased and exhibited by P.T. Barnum in 1882]\n\n -- www.infoplease.com\n\nBorman, et al. Standards Track [Page 1]\n\f\nRFC 2675 IPv6 Jumbograms 2675 nested-reference unchanged"},{"id":"IETF RFC 2775","type":"specification","body":"IETF","designation":"RFC 2775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2775.txt","https://www.rfc-editor.org/rfc/rfc2775.pdf"],"folder":"IETF/RFC-2775","files":{"txt":{"path":"standards/IETF/RFC-2775/RFC-2775.txt","sha256":"23b5143045d828eb23050dea6f2c9a44d48797646cc0db2994fa20e4516dbfb8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the current state of the Internet from the\n architectural viewpoint, concentrating on issues of end-to-end\n connectivity and transparency. It concludes with a summary of some\n major architectural alternatives facing the Internet network layer.\n\n This document was used as input to the IAB workshop on the future of\n the network layer held in July 1999. For this reason, it does not\n claim to be complete and definitive, and it refrains from making\n recommendations.","scope_keywords":["2775","driving","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 2775 This document describes the current state of the Internet from the\n architectural viewpoint, concentrating on issues of end-to-end\n connectivity and transparency. It concludes with a summary of some\n major architectural alternatives facing the Internet network layer.\n\n This document was used as input to the IAB workshop on the future of\n the network layer held in July 1999. For this reason, it does not\n claim to be complete and definitive, and it refrains from making\n recommendations. 2775 driving management subject nested-reference unchanged"},{"id":"IETF RFC 2883","type":"specification","body":"IETF","designation":"RFC 2883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2883.txt","https://www.rfc-editor.org/rfc/rfc2883.pdf"],"folder":"IETF/RFC-2883","files":{"txt":{"path":"standards/IETF/RFC-2883/RFC-2883.txt","sha256":"ce07f710c36920e7c75f60b671b80513f2290b3ba6fe5274ba15b818c1da2f60"}},"tags":["nested-reference","unchanged"],"summary":"This note defines an extension of the Selective Acknowledgement\n (SACK) Option [RFC2018] for TCP. RFC 2018 specified the use of the\n SACK option for acknowledging out-of-sequence data not covered by\n TCP's cumulative acknowledgement field. This note extends RFC 2018\n by specifying the use of the SACK option for acknowledging duplicate\n packets. This note suggests that when duplicate packets are\n received, the first block of the SACK option field can be used to\n report the sequence numbers of the packet that triggered the\n acknowledgement. This extension to the SACK option allows the TCP\n sender to infer the order of packets received at the receiver,\n allowing the sender to infer when it has unnecessarily retransmitted\n a packet. A TCP sender could then use this information for more\n robust operation in an environment of reordered packets [BPS99], ACK\n loss, packet replication, and/or ear","scope_keywords":["2883","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null}],"search_text":"IETF RFC 2883 This note defines an extension of the Selective Acknowledgement\n (SACK) Option [RFC2018] for TCP. RFC 2018 specified the use of the\n SACK option for acknowledging out-of-sequence data not covered by\n TCP's cumulative acknowledgement field. This note extends RFC 2018\n by specifying the use of the SACK option for acknowledging duplicate\n packets. This note suggests that when duplicate packets are\n received, the first block of the SACK option field can be used to\n report the sequence numbers of the packet that triggered the\n acknowledgement. This extension to the SACK option allows the TCP\n sender to infer the order of packets received at the receiver,\n allowing the sender to infer when it has unnecessarily retransmitted\n a packet. A TCP sender could then use this information for more\n robust operation in an environment of reordered packets [BPS99], ACK\n loss, packet replication, and/or ear 2883 key nested-reference unchanged"},{"id":"IETF RFC 3588","type":"specification","body":"IETF","designation":"RFC 3588","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3588.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3588.txt","https://www.rfc-editor.org/rfc/rfc3588.pdf"],"folder":"IETF/RFC-3588","files":{"txt":{"path":"standards/IETF/RFC-3588/RFC-3588.txt","sha256":"fda335e58ef8c00ff594c3f0d99482fc2d8e969d93fe7cdd8ca4a541fe7a615b"}},"tags":["nested-reference","unchanged"],"summary":"The Diameter base protocol is intended to provide an Authentication,\n Authorization and Accounting (AAA) framework for applications such as\n network access or IP mobility. Diameter is also intended to work in\n both local Authentication, Authorization & Accounting and roaming\n situations. This document specifies the message format, transport,\n error reporting, accounting and security services to be used by all\n Diameter applications. The Diameter base application needs to be\n supported by all Diameter implementations.\n\nConventions Used In This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [KEYWORD].\n\nCalhoun, et al. Standards Track [Page 1]\n\f\nRFC 3588 Diameter Based Protocol September 2003","scope_keywords":["3588","algorithm","authentication","authorization","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3589","folder":"IETF/RFC-3589","source":"IETF/RFC-3589/RFC-3589.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5224","folder":"IETF/RFC-5224","source":"IETF/RFC-5224/RFC-5224.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5431","folder":"IETF/RFC-5431","source":"IETF/RFC-5431/RFC-5431.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5516","folder":"IETF/RFC-5516","source":"IETF/RFC-5516/RFC-5516.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5719","folder":"IETF/RFC-5719","source":"IETF/RFC-5719/RFC-5719.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6737","folder":"IETF/RFC-6737","source":"IETF/RFC-6737/RFC-6737.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3588 The Diameter base protocol is intended to provide an Authentication,\n Authorization and Accounting (AAA) framework for applications such as\n network access or IP mobility. Diameter is also intended to work in\n both local Authentication, Authorization & Accounting and roaming\n situations. This document specifies the message format, transport,\n error reporting, accounting and security services to be used by all\n Diameter applications. The Diameter base application needs to be\n supported by all Diameter implementations.\n\nConventions Used In This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [KEYWORD].\n\nCalhoun, et al. Standards Track [Page 1]\n\f\nRFC 3588 Diameter Based Protocol September 2003 3588 algorithm authentication authorization key path nested-reference unchanged"},{"id":"IETF RFC 3649","type":"specification","body":"IETF","designation":"RFC 3649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3649.txt","https://www.rfc-editor.org/rfc/rfc3649.pdf"],"folder":"IETF/RFC-3649","files":{"txt":{"path":"standards/IETF/RFC-3649/RFC-3649.txt","sha256":"d45cb913662abe6f2bdf08bd7157261fe42eadf8eef49fa02bd691d2f52ef423"}},"tags":["nested-reference","unchanged"],"summary":"The proposals in this document are experimental. While they may be\n deployed in the current Internet, they do not represent a consensus\n that this is the best method for high-speed congestion control. In\n particular, we note that alternative experimental proposals are\n likely to be forthcoming, and it is not well understood how the\n proposals in this document will interact with such alternative\n proposals.\n\n This document proposes HighSpeed TCP, a modification to TCP's\n congestion control mechanism for use with TCP connections with large\n congestion windows. The congestion control mechanisms of the current\n Standard TCP constrains the congestion windows that can be achieved\n by TCP in realistic environments. For example, for a Standard TCP\n connection with 1500-byte packets and a 100 ms round-trip time,\n achieving a steady-state throughput of 10 Gbps would require an\n average congestion ","scope_keywords":["3649","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null}],"search_text":"IETF RFC 3649 The proposals in this document are experimental. While they may be\n deployed in the current Internet, they do not represent a consensus\n that this is the best method for high-speed congestion control. In\n particular, we note that alternative experimental proposals are\n likely to be forthcoming, and it is not well understood how the\n proposals in this document will interact with such alternative\n proposals.\n\n This document proposes HighSpeed TCP, a modification to TCP's\n congestion control mechanism for use with TCP connections with large\n congestion windows. The congestion control mechanisms of the current\n Standard TCP constrains the congestion windows that can be achieved\n by TCP in realistic environments. For example, for a Standard TCP\n connection with 1500-byte packets and a 100 ms round-trip time,\n achieving a steady-state throughput of 10 Gbps would require an\n average congestion  3649 path risk nested-reference unchanged"},{"id":"IETF RFC 3708","type":"specification","body":"IETF","designation":"RFC 3708","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3708.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3708.txt","https://www.rfc-editor.org/rfc/rfc3708.pdf"],"folder":"IETF/RFC-3708","files":{"txt":{"path":"standards/IETF/RFC-3708/RFC-3708.txt","sha256":"cf69b16fe0798a236e41e9bc6ce625da21395f96ec6bd22fbccb56487e4ec89f"}},"tags":["nested-reference","unchanged"],"summary":"TCP and Stream Control Transmission Protocol (SCTP) provide\n notification of duplicate segment receipt through Duplicate Selective\n Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number\n (TSN) notification, respectively. This document presents\n conservative methods of using this information to identify\n unnecessary retransmissions for various applications.\n\n1. Introduction\n\n TCP [RFC793] and SCTP [RFC2960] provide notification of duplicate\n segment receipt through duplicate selective acknowledgment (DSACK)\n [RFC2883] and Duplicate TSN notifications, respectively. Using this\n information, a TCP or SCTP sender can generally determine when a\n retransmission was sent in error. This document presents two methods\n for using duplicate notifications. The first method is simple and\n can be used for accounting applications. The second method is a\n conservative algorithm to disambigua","scope_keywords":["3708","algorithm","algorithms","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null}],"search_text":"IETF RFC 3708 TCP and Stream Control Transmission Protocol (SCTP) provide\n notification of duplicate segment receipt through Duplicate Selective\n Acknowledgement (DSACKs) and Duplicate Transmission Sequence Number\n (TSN) notification, respectively. This document presents\n conservative methods of using this information to identify\n unnecessary retransmissions for various applications.\n\n1. Introduction\n\n TCP [RFC793] and SCTP [RFC2960] provide notification of duplicate\n segment receipt through duplicate selective acknowledgment (DSACK)\n [RFC2883] and Duplicate TSN notifications, respectively. Using this\n information, a TCP or SCTP sender can generally determine when a\n retransmission was sent in error. This document presents two methods\n for using duplicate notifications. The first method is simple and\n can be used for accounting applications. The second method is a\n conservative algorithm to disambigua 3708 algorithm algorithms key path nested-reference unchanged"},{"id":"IETF RFC 3782","type":"specification","body":"IETF","designation":"RFC 3782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3782.txt","https://www.rfc-editor.org/rfc/rfc3782.pdf"],"folder":"IETF/RFC-3782","files":{"txt":{"path":"standards/IETF/RFC-3782/RFC-3782.txt","sha256":"649fb2f078a87cdbfec3a730b994c3f3423fee4a0a3a340db395c3717af88f6f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Floyd\nRequest for Comments: 3782 ICSI\nObsoletes: 2582 T. Henderson\nCategory: Standards Track Boeing\n A. Gurtov\n TeliaSonera\n April 2004\n\n The NewReno Modification to TCP's Fast Recovery Algorithm\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004). All Rights Reserved.\n\nAbstract\n\n The purpose of this document is to advance NewReno TCP's Fast\n Retransmit and Fast Recovery algorithms in RFC 2582 from Experimental\n to Standards Track status.\n\n The main change in this document relative to RFC 2582 is ","scope_keywords":["3782","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3782 Network Working Group S. Floyd\nRequest for Comments: 3782 ICSI\nObsoletes: 2582 T. Henderson\nCategory: Standards Track Boeing\n A. Gurtov\n TeliaSonera\n April 2004\n\n The NewReno Modification to TCP's Fast Recovery Algorithm\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004). All Rights Reserved.\n\nAbstract\n\n The purpose of this document is to advance NewReno TCP's Fast\n Retransmit and Fast Recovery algorithms in RFC 2582 from Experimental\n to Standards Track status.\n\n The main change in this document relative to RFC 2582 is  3782 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 4015","type":"specification","body":"IETF","designation":"RFC 4015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4015.txt","https://www.rfc-editor.org/rfc/rfc4015.pdf"],"folder":"IETF/RFC-4015","files":{"txt":{"path":"standards/IETF/RFC-4015/RFC-4015.txt","sha256":"e632526c4401c33b25aca85f8629a9c093c235af329d137024c8d853a9c98333"}},"tags":["nested-reference","unchanged"],"summary":"Based on an appropriate detection algorithm, the Eifel response\n algorithm provides a way for a TCP sender to respond to a detected\n spurious timeout. It adapts the retransmission timer to avoid\n further spurious timeouts and (depending on the detection algorithm)\n can avoid the often unnecessary go-back-N retransmits that would\n otherwise be sent. In addition, the Eifel response algorithm\n restores the congestion control state in such a way that packet\n bursts are avoided.\n\n1. Introduction\n\n The Eifel response algorithm relies on a detection algorithm such as\n the Eifel detection algorithm, defined in [RFC3522]. That document\n contains informative background and motivation context that may be\n useful for implementers of the Eifel response algorithm, but it is\n not necessary to read [RFC3522] in order to implement the Eifel\n response algorithm. Note that alternative response algorithms h","scope_keywords":["4015","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null}],"search_text":"IETF RFC 4015 Based on an appropriate detection algorithm, the Eifel response\n algorithm provides a way for a TCP sender to respond to a detected\n spurious timeout. It adapts the retransmission timer to avoid\n further spurious timeouts and (depending on the detection algorithm)\n can avoid the often unnecessary go-back-N retransmits that would\n otherwise be sent. In addition, the Eifel response algorithm\n restores the congestion control state in such a way that packet\n bursts are avoided.\n\n1. Introduction\n\n The Eifel response algorithm relies on a detection algorithm such as\n the Eifel detection algorithm, defined in [RFC3522]. That document\n contains informative background and motivation context that may be\n useful for implementers of the Eifel response algorithm, but it is\n not necessary to read [RFC3522] in order to implement the Eifel\n response algorithm. Note that alternative response algorithms h 4015 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 4138","type":"specification","body":"IETF","designation":"RFC 4138","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4138.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4138.txt","https://www.rfc-editor.org/rfc/rfc4138.pdf"],"folder":"IETF/RFC-4138","files":{"txt":{"path":"standards/IETF/RFC-4138/RFC-4138.txt","sha256":"5ddc409c0b998b3ae32b58c2c5c8ed3236db796ba3da0b0f2ee9c819551d6a29"}},"tags":["nested-reference","unchanged"],"summary":"Spurious retransmission timeouts cause suboptimal TCP performance\n because they often result in unnecessary retransmission of the last\n window of data. This document describes the F-RTO detection\n algorithm for detecting spurious TCP retransmission timeouts. F-RTO\n is a TCP sender-only algorithm that does not require any TCP options\n to operate. After retransmitting the first unacknowledged segment\n triggered by a timeout, the F-RTO algorithm of the TCP sender\n monitors the incoming acknowledgments to determine whether the\n timeout was spurious. It then decides whether to send new segments\n or retransmit unacknowledged segments. The algorithm effectively\n helps to avoid additional unnecessary retransmissions and thereby\n improves TCP performance in the case of a spurious timeout. The\n F-RTO algorithm can also be applied to the Stream Control\n Transmission Protocol (SCTP).\n\nSarolahti & Ko","scope_keywords":["4138","algorithm","algorithms","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 4138 Spurious retransmission timeouts cause suboptimal TCP performance\n because they often result in unnecessary retransmission of the last\n window of data. This document describes the F-RTO detection\n algorithm for detecting spurious TCP retransmission timeouts. F-RTO\n is a TCP sender-only algorithm that does not require any TCP options\n to operate. After retransmitting the first unacknowledged segment\n triggered by a timeout, the F-RTO algorithm of the TCP sender\n monitors the incoming acknowledgments to determine whether the\n timeout was spurious. It then decides whether to send new segments\n or retransmit unacknowledged segments. The algorithm effectively\n helps to avoid additional unnecessary retransmissions and thereby\n improves TCP performance in the case of a spurious timeout. The\n F-RTO algorithm can also be applied to the Stream Control\n Transmission Protocol (SCTP).\n\nSarolahti & Ko 4138 algorithm algorithms timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 4737","type":"specification","body":"IETF","designation":"RFC 4737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4737.txt","https://www.rfc-editor.org/rfc/rfc4737.pdf"],"folder":"IETF/RFC-4737","files":{"txt":{"path":"standards/IETF/RFC-4737/RFC-4737.txt","sha256":"32641b9f258c76c32663fffb2f49d3a7ad5aeeb5c37fcd52202dd721d35fa6c0"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines metrics to evaluate whether a network has\n maintained packet order on a packet-by-packet basis. It provides\n motivations for the new metrics and discusses the measurement issues,\n including the context information required for all metrics. The memo\n first defines a reordered singleton, and then uses it as the basis\n for sample metrics to quantify the extent of reordering in several\n useful dimensions for network characterization or receiver design.\n Additional metrics quantify the frequency of reordering and the\n distance between separate occurrences. We then define a metric\n oriented toward assessment of reordering effects on TCP. Several\n examples of evaluation using the various sample metrics are included.\n An appendix gives extended definitions for evaluating order with\n packet fragmentation.\n\nMorton, et al. Standards Track [Page 1]\n\f\nRFC 4737 Packet Reordering Metr","scope_keywords":["4737","license","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 4737 This memo defines metrics to evaluate whether a network has\n maintained packet order on a packet-by-packet basis. It provides\n motivations for the new metrics and discusses the measurement issues,\n including the context information required for all metrics. The memo\n first defines a reordered singleton, and then uses it as the basis\n for sample metrics to quantify the extent of reordering in several\n useful dimensions for network characterization or receiver design.\n Additional metrics quantify the frequency of reordering and the\n distance between separate occurrences. We then define a metric\n oriented toward assessment of reordering effects on TCP. Several\n examples of evaluation using the various sample metrics are included.\n An appendix gives extended definitions for evaluating order with\n packet fragmentation.\n\nMorton, et al. Standards Track [Page 1]\n\f\nRFC 4737 Packet Reordering Metr 4737 license path trust nested-reference unchanged"},{"id":"IETF RFC 4808","type":"specification","body":"IETF","designation":"RFC 4808","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4808.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4808.txt","https://www.rfc-editor.org/rfc/rfc4808.pdf"],"folder":"IETF/RFC-4808","files":{"txt":{"path":"standards/IETF/RFC-4808/RFC-4808.txt","sha256":"4814f0727ead342775f8ae6926ccc32e45c3e08f759a2dc6379b09679541d28f"}},"tags":["nested-reference","unchanged"],"summary":"The TCP-MD5 option is most commonly used to secure BGP sessions\n between routers. However, changing the long-term key is difficult,\n since the change needs to be synchronized between different\n organizations. We describe single-ended strategies that will permit\n (mostly) unsynchronized key changes.\n\nBellovin Informational [Page 1]\n\f\nRFC 4808 TCP-MD5 Key Change March 2007\n\n1. Introduction\n\n The TCP-MD5 option [RFC2385] is most commonly used to secure BGP\n sessions between routers. However, changing the long-term key is\n difficult, since the change needs to be synchronized between\n different organizations. Worse yet, if the keys are out of sync, it\n may break the connection between the two routers, rendering repair\n attempts difficult.\n\n The proper solution involves some sort of key management protocol.\n Apart from the complexity of such things, RFC 2385 was not written\n with key changes i","scope_keywords":["4808","algorithm","algorithms","key","keys","management","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null}],"search_text":"IETF RFC 4808 The TCP-MD5 option is most commonly used to secure BGP sessions\n between routers. However, changing the long-term key is difficult,\n since the change needs to be synchronized between different\n organizations. We describe single-ended strategies that will permit\n (mostly) unsynchronized key changes.\n\nBellovin Informational [Page 1]\n\f\nRFC 4808 TCP-MD5 Key Change March 2007\n\n1. Introduction\n\n The TCP-MD5 option [RFC2385] is most commonly used to secure BGP\n sessions between routers. However, changing the long-term key is\n difficult, since the change needs to be synchronized between\n different organizations. Worse yet, if the keys are out of sync, it\n may break the connection between the two routers, rendering repair\n attempts difficult.\n\n The proper solution involves some sort of key management protocol.\n Apart from the complexity of such things, RFC 2385 was not written\n with key changes i 4808 algorithm algorithms key keys management timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5682","type":"specification","body":"IETF","designation":"RFC 5682","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5682.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5682.txt","https://www.rfc-editor.org/rfc/rfc5682.pdf"],"folder":"IETF/RFC-5682","files":{"txt":{"path":"standards/IETF/RFC-5682/RFC-5682.txt","sha256":"9c8a54a1bf0b6fcec456778cf75182af78ffd9daa1dce0bab79143fcc3912484"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to move the F-RTO (Forward\n RTO-Recovery) functionality for TCP in RFC 4138 from\n Experimental to Standards Track status. The F-RTO support for Stream\n Control Transmission Protocol (SCTP) in RFC 4138 remains with\n Experimental status. See Appendix B for the differences between this\n document and RFC 4138.\n\n Spurious retransmission timeouts cause suboptimal TCP performance\n because they often result in unnecessary retransmission of the last\n window of data. This document describes the F-RTO detection\n algorithm for detecting spurious TCP retransmission timeouts. F-RTO\n is a TCP sender-only algorithm that does not require any TCP options\n to operate. After retransmitting the first unacknowledged segment\n triggered by a timeout, the F-RTO algorithm of the TCP sender\n monitors the incoming acknowledgments to determine whether the\n timeout was spurious. It the","scope_keywords":["5682","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 5682 The purpose of this document is to move the F-RTO (Forward\n RTO-Recovery) functionality for TCP in RFC 4138 from\n Experimental to Standards Track status. The F-RTO support for Stream\n Control Transmission Protocol (SCTP) in RFC 4138 remains with\n Experimental status. See Appendix B for the differences between this\n document and RFC 4138.\n\n Spurious retransmission timeouts cause suboptimal TCP performance\n because they often result in unnecessary retransmission of the last\n window of data. This document describes the F-RTO detection\n algorithm for detecting spurious TCP retransmission timeouts. F-RTO\n is a TCP sender-only algorithm that does not require any TCP options\n to operate. After retransmitting the first unacknowledged segment\n triggered by a timeout, the F-RTO algorithm of the TCP sender\n monitors the incoming acknowledgments to determine whether the\n timeout was spurious. It the 5682 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6297","type":"specification","body":"IETF","designation":"RFC 6297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6297.txt","https://www.rfc-editor.org/rfc/rfc6297.pdf"],"folder":"IETF/RFC-6297","files":{"txt":{"path":"standards/IETF/RFC-6297/RFC-6297.txt","sha256":"31d80e828213d44185ac062c233dab39897f50b835f32e020c5055cf60cf8a87"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a survey of transport protocols that are\n designed to have a smaller bandwidth and/or delay impact on standard\n TCP than standard TCP itself when they share a bottleneck with it.\n Such protocols could be used for delay-insensitive \"background\"\n traffic, as they provide what is sometimes called a \"less than\" (or\n \"lower than\") best-effort service.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the cur","scope_keywords":["6297","algorithm","http","key","license","management","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 6297 This document provides a survey of transport protocols that are\n designed to have a smaller bandwidth and/or delay impact on standard\n TCP than standard TCP itself when they share a bottleneck with it.\n Such protocols could be used for delay-insensitive \"background\"\n traffic, as they provide what is sometimes called a \"less than\" (or\n \"lower than\") best-effort service.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the cur 6297 algorithm http key license management path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6582","type":"specification","body":"IETF","designation":"RFC 6582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6582.txt","https://www.rfc-editor.org/rfc/rfc6582.pdf"],"folder":"IETF/RFC-6582","files":{"txt":{"path":"standards/IETF/RFC-6582/RFC-6582.txt","sha256":"98e24aa8b48d4c8b17b4f51ef7126dae030943cd6e15b658ca99f6c6958650eb"}},"tags":["nested-reference","unchanged"],"summary":"RFC 5681 documents the following four intertwined TCP congestion\n control algorithms: slow start, congestion avoidance, fast\n retransmit, and fast recovery. RFC 5681 explicitly allows certain\n modifications of these algorithms, including modifications that use\n the TCP Selective Acknowledgment (SACK) option (RFC 2883), and\n modifications that respond to \"partial acknowledgments\" (ACKs that\n cover new data, but not all the data outstanding when loss was\n detected) in the absence of SACK. This document describes a specific\n algorithm for responding to partial acknowledgments, referred to as\n \"NewReno\". This response to partial acknowledgments was first\n proposed by Janey Hoe. This document obsoletes RFC 3782.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IE","scope_keywords":["6582","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 6582 RFC 5681 documents the following four intertwined TCP congestion\n control algorithms: slow start, congestion avoidance, fast\n retransmit, and fast recovery. RFC 5681 explicitly allows certain\n modifications of these algorithms, including modifications that use\n the TCP Selective Acknowledgment (SACK) option (RFC 2883), and\n modifications that respond to \"partial acknowledgments\" (ACKs that\n cover new data, but not all the data outstanding when loss was\n detected) in the absence of SACK. This document describes a specific\n algorithm for responding to partial acknowledgments, referred to as\n \"NewReno\". This response to partial acknowledgments was first\n proposed by Janey Hoe. This document obsoletes RFC 3782.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IE 6582 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 1326","type":"specification","body":"IETF","designation":"RFC 1326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1326.txt","https://www.rfc-editor.org/rfc/rfc1326.pdf"],"folder":"IETF/RFC-1326","files":{"txt":{"path":"standards/IETF/RFC-1326/RFC-1326.txt","sha256":"433dcc6a8bfcf8bbe5b7241458f497c28029b59577632074415cd285f973d168"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Tsuchiya\nRequest for Comments: 1326 Bellcore\n May 1992\n\n Mutual Encapsulation Considered Dangerous\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This memo describes a packet explosion problem that can occur with\n mutual encapsulation of protocols (A encapsulates B and B\n encapsulates A).\n\nThe Current Environment\n\n In spite of international standardization efforts to the contrary, we\n are these days seeing a plethora of different protocols, both\n standard and proprietary, each designed to fill a technical or\n marketing niche. The end result is that they eventually butt up\n against each other and are expected to interwork in some fashion.\n\n One approach to this interworking is to encapsulate one protocol\n within another. This has resul","scope_keywords":["1326","algorithm","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null}],"search_text":"IETF RFC 1326 Network Working Group P. Tsuchiya\nRequest for Comments: 1326 Bellcore\n May 1992\n\n Mutual Encapsulation Considered Dangerous\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This memo describes a packet explosion problem that can occur with\n mutual encapsulation of protocols (A encapsulates B and B\n encapsulates A).\n\nThe Current Environment\n\n In spite of international standardization efforts to the contrary, we\n are these days seeing a plethora of different protocols, both\n standard and proprietary, each designed to fill a technical or\n marketing niche. The end result is that they eventually butt up\n against each other and are expected to interwork in some fashion.\n\n One approach to this interworking is to encapsulate one protocol\n within another. This has resul 1326 algorithm management path nested-reference unchanged"},{"id":"IETF RFC 1328","type":"specification","body":"IETF","designation":"RFC 1328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1328.txt","https://www.rfc-editor.org/rfc/rfc1328.pdf"],"folder":"IETF/RFC-1328","files":{"txt":{"path":"standards/IETF/RFC-1328/RFC-1328.txt","sha256":"bdb45498552357e09ec2da1ad263a8b89501a4ce7776986d83e47df490f133f6"}},"tags":["nested-reference","unchanged"],"summary":"This document considers issues of downgrading from X.400(1988) to\n X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some\n downgrading rules [MHS88b], but these are not sufficient for\n provision of service in an environment containing both 1984 and 1988\n components. This document defines a number of extensions to this\n annexe.\n\n This specification is not tutorial. COSINE Study 8.2 by J.A.I.\n Craigie gives a useful overview [Cra88].\n\n1. The need to Downgrade\n\n It is expected that X.400(1988) systems will be extensively deployed,\n whilst there is still substantial use of X.400(1984). If 1988\n features are to be used, it it important for there to be a clear\n approach to downgrading. This document specifies an approach to\n downgrading for the Internet and COSINE communities. As 1988 is a\n strict superset of 1984, the mapping is a one-way problem.\n\n2. Avoiding Downgrading\n\n Perhaps the","scope_keywords":["1328","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1496","folder":"IETF/RFC-1496","source":"IETF/RFC-1496/RFC-1496.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1328 This document considers issues of downgrading from X.400(1988) to\n X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some\n downgrading rules [MHS88b], but these are not sufficient for\n provision of service in an environment containing both 1984 and 1988\n components. This document defines a number of extensions to this\n annexe.\n\n This specification is not tutorial. COSINE Study 8.2 by J.A.I.\n Craigie gives a useful overview [Cra88].\n\n1. The need to Downgrade\n\n It is expected that X.400(1988) systems will be extensively deployed,\n whilst there is still substantial use of X.400(1984). If 1988\n features are to be used, it it important for there to be a clear\n approach to downgrading. This document specifies an approach to\n downgrading for the Internet and COSINE communities. As 1988 is a\n strict superset of 1984, the mapping is a one-way problem.\n\n2. Avoiding Downgrading\n\n Perhaps the 1328 attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 1405","type":"specification","body":"IETF","designation":"RFC 1405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1405.txt","https://www.rfc-editor.org/rfc/rfc1405.pdf"],"folder":"IETF/RFC-1405","files":{"txt":{"path":"standards/IETF/RFC-1405/RFC-1405.txt","sha256":"b8584de6275d70148baad072d7ba4bf5d15d1b3f7c4cbb5e8ad051d4573a0dc3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of mappings which will enable inter\n working between systems operating the CCITT X.400 ( 1984 / 1988 )\n Recommendations on Message Handling Systems, and systems running the\n Mail-11 (also known as DECnet mail) protocol. The specifications are\n valid within DECnet Phase IV addressing and routing scheme.\n\n The complete scenario of X.400 / RFC822 / Mail-11 is also considered,\n in order to cover the possible complex cases arising in multiple\n gateway translations.\n\n This document covers mainly the O/R address to DECnet from/to address\n mapping (and vice versa); other mappings are based on RFC 1327 and\n its eventual future updates.\n\n This is a combined effort of COSINE S2.2, the RARE MSG Working Group,\n and the IETF X.400 Ops Working Group.\n\nChapter 1 - Introduction","scope_keywords":["1405","attribute","attributes","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null}],"search_text":"IETF RFC 1405 This document describes a set of mappings which will enable inter\n working between systems operating the CCITT X.400 ( 1984 / 1988 )\n Recommendations on Message Handling Systems, and systems running the\n Mail-11 (also known as DECnet mail) protocol. The specifications are\n valid within DECnet Phase IV addressing and routing scheme.\n\n The complete scenario of X.400 / RFC822 / Mail-11 is also considered,\n in order to cover the possible complex cases arising in multiple\n gateway translations.\n\n This document covers mainly the O/R address to DECnet from/to address\n mapping (and vice versa); other mappings are based on RFC 1327 and\n its eventual future updates.\n\n This is a combined effort of COSINE S2.2, the RARE MSG Working Group,\n and the IETF X.400 Ops Working Group.\n\nChapter 1 - Introduction 1405 attribute attributes presentation subject nested-reference unchanged"},{"id":"IETF RFC 1494","type":"specification","body":"IETF","designation":"RFC 1494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1494.txt","https://www.rfc-editor.org/rfc/rfc1494.pdf"],"folder":"IETF/RFC-1494","files":{"txt":{"path":"standards/IETF/RFC-1494/RFC-1494.txt","sha256":"3e08e90eccfb04b0769763c9731830491a5c756969bfd054c7f2fe20f18b51da"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 1494 SINTEF DELAB\n S. Thompson\n Soft*Switch, Inc.\n August 1993\n\n Equivalences between 1988 X.400 and RFC-822 Message Bodies\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. Equivalence Table Definition ............................. 2\n 3. Generic conversions ...................................... 3\n 3.1. Byte copy .............................................. 3\n 3.2. Text Conversion ........................................ 3\n 3.3. Image Conversion ..........","scope_keywords":["1494","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1496","folder":"IETF/RFC-1496","source":"IETF/RFC-1496/RFC-1496.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2159","folder":"IETF/RFC-2159","source":"IETF/RFC-2159/RFC-2159.txt","version":null},{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1494 Network Working Group H. Alvestrand\nRequest for Comments: 1494 SINTEF DELAB\n S. Thompson\n Soft*Switch, Inc.\n August 1993\n\n Equivalences between 1988 X.400 and RFC-822 Message Bodies\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 2\n 2. Equivalence Table Definition ............................. 2\n 3. Generic conversions ...................................... 3\n 3.1. Byte copy .............................................. 3\n 3.2. Text Conversion ........................................ 3\n 3.3. Image Conversion .......... 1494 presentation registered nested-reference unchanged"},{"id":"IETF RFC 1495","type":"specification","body":"IETF","designation":"RFC 1495","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1495.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1495.txt","https://www.rfc-editor.org/rfc/rfc1495.pdf"],"folder":"IETF/RFC-1495","files":{"txt":{"path":"standards/IETF/RFC-1495/RFC-1495.txt","sha256":"6da613f782aada5092fb5267410237f811075e140e1bfd458c83f97882cde0a9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 1495 SINTEF DELAB\nUpdates: 1327 S. Kille\n ISODE Consortium\n R. Miles\n Soft*Switch, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Thompson\n Soft*Switch, Inc.\n August 1993\n\n Mapping between X.400 and RFC-822 Message Bodies\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. Approach ................................................. 2\n 3. Mapping between X.400 and RFC-822 Message Bodies ......... 3\n 3.1 Mapping from X.400 to RFC-822 ........................... 4","scope_keywords":["1495","algorithm","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2158","folder":"IETF/RFC-2158","source":"IETF/RFC-2158/RFC-2158.txt","version":null},{"body":"IETF","designation":"RFC 2161","folder":"IETF/RFC-2161","source":"IETF/RFC-2161/RFC-2161.txt","version":null},{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null}],"search_text":"IETF RFC 1495 Network Working Group H. Alvestrand\nRequest for Comments: 1495 SINTEF DELAB\nUpdates: 1327 S. Kille\n ISODE Consortium\n R. Miles\n Soft*Switch, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Thompson\n Soft*Switch, Inc.\n August 1993\n\n Mapping between X.400 and RFC-822 Message Bodies\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................. 1\n 2. Approach ................................................. 2\n 3. Mapping between X.400 and RFC-822 Message Bodies ......... 3\n 3.1 Mapping from X.400 to RFC-822 ........................... 4 1495 algorithm registered nested-reference unchanged"},{"id":"IETF RFC 1496","type":"specification","body":"IETF","designation":"RFC 1496","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1496.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1496.txt","https://www.rfc-editor.org/rfc/rfc1496.pdf"],"folder":"IETF/RFC-1496","files":{"txt":{"path":"standards/IETF/RFC-1496/RFC-1496.txt","sha256":"42965687881e208c3b82ef309305eb9b5876ed1f4046ecb195a1e92d39717164"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 1496 SINTEF DELAB\nUpdates: 1328 J. Romaguera\n NetConsult AG\n K. Jordan\n Control Data Systems, Inc.\n August 1993\n\n Rules for Downgrading Messages from X.400/88 to X.400/84 When\n MIME Content-Types are Present in the Messages\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. Basic approach ............................................. 2\n 3. Conversion rules ........................................... 3\n 3.1 EBP conversions to Basic ...........................","scope_keywords":["1496","identification","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null}],"search_text":"IETF RFC 1496 Network Working Group H. Alvestrand\nRequest for Comments: 1496 SINTEF DELAB\nUpdates: 1328 J. Romaguera\n NetConsult AG\n K. Jordan\n Control Data Systems, Inc.\n August 1993\n\n Rules for Downgrading Messages from X.400/88 to X.400/84 When\n MIME Content-Types are Present in the Messages\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ............................................... 1\n 2. Basic approach ............................................. 2\n 3. Conversion rules ........................................... 3\n 3.1 EBP conversions to Basic ........................... 1496 identification path subject nested-reference unchanged"},{"id":"IETF RFC 1766","type":"specification","body":"IETF","designation":"RFC 1766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1766.txt","https://www.rfc-editor.org/rfc/rfc1766.pdf"],"folder":"IETF/RFC-1766","files":{"txt":{"path":"standards/IETF/RFC-1766/RFC-1766.txt","sha256":"2588b2a99bb5f81a4140a25ff44e88660655d72c3ff29fd051be4d68c3452630"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a language tag for use in cases where it is\n desired to indicate the language used in an information object.\n\n It also defines a Content-language: header, for use in the case where\n one desires to indicate the language of something that has RFC-822-\n like headers, like MIME body parts or Web documents, and a new\n parameter to the Multipart/Alternative type, to aid in the usage of\n the Content-Language: header.\n\n1. Introduction\n\n There are a number of languages spoken by human beings in this world.\n\n A great number of these people would prefer to have information\n presented in a language that they understand.\n\n In some contexts, it is possible to have information in more than one\n language, or it might be possible to provide tools for assisting in\n the understanding of a language (like dictionaries).\n\n A prerequisite for any such function is a means of labelling th","scope_keywords":["1766","identification","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1835","folder":"IETF/RFC-1835","source":"IETF/RFC-1835/RFC-1835.txt","version":null},{"body":"IETF","designation":"RFC 1942","folder":"IETF/RFC-1942","source":"IETF/RFC-1942/RFC-1942.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2413","folder":"IETF/RFC-2413","source":"IETF/RFC-2413/RFC-2413.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2596","folder":"IETF/RFC-2596","source":"IETF/RFC-2596/RFC-2596.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2731","folder":"IETF/RFC-2731","source":"IETF/RFC-2731/RFC-2731.txt","version":null},{"body":"IETF","designation":"RFC 2771","folder":"IETF/RFC-2771","source":"IETF/RFC-2771/RFC-2771.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 2987","folder":"IETF/RFC-2987","source":"IETF/RFC-2987/RFC-2987.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null}],"search_text":"IETF RFC 1766 This document describes a language tag for use in cases where it is\n desired to indicate the language used in an information object.\n\n It also defines a Content-language: header, for use in the case where\n one desires to indicate the language of something that has RFC-822-\n like headers, like MIME body parts or Web documents, and a new\n parameter to the Multipart/Alternative type, to aid in the usage of\n the Content-Language: header.\n\n1. Introduction\n\n There are a number of languages spoken by human beings in this world.\n\n A great number of these people would prefer to have information\n presented in a language that they understand.\n\n In some contexts, it is possible to have information in more than one\n language, or it might be possible to provide tools for assisting in\n the understanding of a language (like dictionaries).\n\n A prerequisite for any such function is a means of labelling th 1766 identification presentation registered nested-reference unchanged"},{"id":"IETF RFC 1836","type":"specification","body":"IETF","designation":"RFC 1836","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1836.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1836.txt","https://www.rfc-editor.org/rfc/rfc1836.pdf"],"folder":"IETF/RFC-1836","files":{"txt":{"path":"standards/IETF/RFC-1836/RFC-1836.txt","sha256":"d9fe1063833b2fad6a6e8d7b694c5ae1310eb45cdea811cfbc36c642e6081cf1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 1836 ISODE Consortium\nCategory: Experimental August 1995\n\n Representing the O/R Address hierarchy in the\n X.500 Directory Information Tree\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines a representation of the O/R Address hierarchy\n in the Directory Information Tree [6, 1]. This is useful for a range\n of purposes, including:\n\no Support for MHS Routing [4].\n\no Support for X.400/RFC 822 address mappings [2, 5].\n\n Object Class Mandatory\n ------------ ---------\n mHSCountry M\n aDMD M\n pRMD O\n mHSX121 O\n mHSNumericUserIdentifier O\n mHSOrganization O\n mHSOrganizationalUnit O\n mHSPerson O\n mHSNamedObject ","scope_keywords":["1836","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null}],"search_text":"IETF RFC 1836 Network Working Group S. Kille\nRequest for Comments: 1836 ISODE Consortium\nCategory: Experimental August 1995\n\n Representing the O/R Address hierarchy in the\n X.500 Directory Information Tree\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines a representation of the O/R Address hierarchy\n in the Directory Information Tree [6, 1]. This is useful for a range\n of purposes, including:\n\no Support for MHS Routing [4].\n\no Support for X.400/RFC 822 address mappings [2, 5].\n\n Object Class Mandatory\n ------------ ---------\n mHSCountry M\n aDMD M\n pRMD O\n mHSX121 O\n mHSNumericUserIdentifier O\n mHSOrganization O\n mHSOrganizationalUnit O\n mHSPerson O\n mHSNamedObject  1836 attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 2157","type":"specification","body":"IETF","designation":"RFC 2157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2157.txt","https://www.rfc-editor.org/rfc/rfc2157.pdf"],"folder":"IETF/RFC-2157","files":{"txt":{"path":"standards/IETF/RFC-2157/RFC-2157.txt","sha256":"fb8a9445521b531b1914e2162ce830837573118f90b9515efdca1ac9b54a3b59"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2157 UNINETT\nCategory: Standards Track January 1998\n\n Mapping between X.400 and RFC-822/MIME Message Bodies\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ........................................... 2\n 1.1 Glossary ............................................. 3\n 2 Basic rules for body part conversion ................... 4\n 2.1 Generating the IPM Body from MIME .................... 5\n 2.2 Generating the","scope_keywords":["2157"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null}],"search_text":"IETF RFC 2157 Network Working Group H. Alvestrand\nRequest for Comments: 2157 UNINETT\nCategory: Standards Track January 1998\n\n Mapping between X.400 and RFC-822/MIME Message Bodies\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ........................................... 2\n 1.1 Glossary ............................................. 3\n 2 Basic rules for body part conversion ................... 4\n 2.1 Generating the IPM Body from MIME .................... 5\n 2.2 Generating the 2157 nested-reference unchanged"},{"id":"IETF RFC 2248","type":"specification","body":"IETF","designation":"RFC 2248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2248.txt","https://www.rfc-editor.org/rfc/rfc2248.pdf"],"folder":"IETF/RFC-2248","files":{"txt":{"path":"standards/IETF/RFC-2248/RFC-2248.txt","sha256":"5011177121a3e40ab228c8a2f6ce09f9d84c9455663dccb7ad86fcae218897e1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2248 Innosoft\nObsoletes: 1565 S. Kille\nCategory: Standards Track ISODE Consortium\n January 1998\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n A networked application is a realization of some well defined service\n on one or more host computers that is accessible via some network,\n uses some network for its internal operations, or both.\n\n There are a wide range of networked applications for w","scope_keywords":["2248","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null}],"search_text":"IETF RFC 2248 Network Working Group N. Freed\nRequest for Comments: 2248 Innosoft\nObsoletes: 1565 S. Kille\nCategory: Standards Track ISODE Consortium\n January 1998\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n A networked application is a realization of some well defined service\n on one or more host computers that is accessible via some network,\n uses some network for its internal operations, or both.\n\n There are a wide range of networked applications for w 2248 management nested-reference unchanged"},{"id":"IETF RFC 2249","type":"specification","body":"IETF","designation":"RFC 2249","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2249.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2249.txt","https://www.rfc-editor.org/rfc/rfc2249.pdf"],"folder":"IETF/RFC-2249","files":{"txt":{"path":"standards/IETF/RFC-2249/RFC-2249.txt","sha256":"fa760ff040632bd2971c48937465e4d0662e9a56cefd4d0a7ab088207d956935"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2249 Innosoft\nObsoletes: 1566 S. Kille\nCategory: Standards Track ISODE Consortium\n January 1998\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this memo extends the basic Network Services Monitoring\n MIB [8] to allow monitoring of Message Transfer Agen","scope_keywords":["2249","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null}],"search_text":"IETF RFC 2249 Network Working Group N. Freed\nRequest for Comments: 2249 Innosoft\nObsoletes: 1566 S. Kille\nCategory: Standards Track ISODE Consortium\n January 1998\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this memo extends the basic Network Services Monitoring\n MIB [8] to allow monitoring of Message Transfer Agen 2249 management nested-reference unchanged"},{"id":"IETF RFC 3066","type":"specification","body":"IETF","designation":"RFC 3066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3066.txt","https://www.rfc-editor.org/rfc/rfc3066.pdf"],"folder":"IETF/RFC-3066","files":{"txt":{"path":"standards/IETF/RFC-3066/RFC-3066.txt","sha256":"87e4dc0a85dde4e5161bb63384a69cd43cf5e52aceab46c3a9729c0b91778b24"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a language tag for use in cases where it is\n desired to indicate the language used in an information object, how\n to register values for use in this language tag, and a construct for\n matching such language tags.\n\n1. Introduction\n\n Human beings on our planet have, past and present, used a number of\n languages. There are many reasons why one would want to identify the\n language used when presenting information.\n\n In some contexts, it is possible to have information available in\n more than one language, or it might be possible to provide tools\n (such as dictionaries) to assist in the understanding of a language.\n\n Also, many types of information processing require knowledge of the\n language in which information is expressed in order for that process\n to be performed on the information; for example spell-checking,\n computer-synthesized speech, Braille, or high-qualit","scope_keywords":["3066","http","identification","key","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null}],"search_text":"IETF RFC 3066 This document describes a language tag for use in cases where it is\n desired to indicate the language used in an information object, how\n to register values for use in this language tag, and a construct for\n matching such language tags.\n\n1. Introduction\n\n Human beings on our planet have, past and present, used a number of\n languages. There are many reasons why one would want to identify the\n language used when presenting information.\n\n In some contexts, it is possible to have information available in\n more than one language, or it might be possible to provide tools\n (such as dictionaries) to assist in the understanding of a language.\n\n Also, many types of information processing require knowledge of the\n language in which information is expressed in order for that process\n to be performed on the information; for example spell-checking,\n computer-synthesized speech, Braille, or high-qualit 3066 http identification key presentation registered nested-reference unchanged"},{"id":"IETF RFC 1548","type":"specification","body":"IETF","designation":"RFC 1548","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1548.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1548.txt","https://www.rfc-editor.org/rfc/rfc1548.pdf"],"folder":"IETF/RFC-1548","files":{"txt":{"path":"standards/IETF/RFC-1548/RFC-1548.txt","sha256":"934fe0199bc63466aac02ef13bdac5b89051f39058949303c76276f54c309229"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n is comprised of three main components:\n\n 1. A method for encapsulating multi-protocol datagrams.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP organization and methodology, and the\n PPP encapsulation, together with an extensible option negotiation\n mechanism which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions. The PPP Link Control Protocol (LCP) is described in terms\n of this mechanism.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Eng","scope_keywords":["1548","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1549","folder":"IETF/RFC-1549","source":"IETF/RFC-1549/RFC-1549.txt","version":null},{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null},{"body":"IETF","designation":"RFC 1552","folder":"IETF/RFC-1552","source":"IETF/RFC-1552/RFC-1552.txt","version":null},{"body":"IETF","designation":"RFC 1553","folder":"IETF/RFC-1553","source":"IETF/RFC-1553/RFC-1553.txt","version":null},{"body":"IETF","designation":"RFC 1570","folder":"IETF/RFC-1570","source":"IETF/RFC-1570/RFC-1570.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1598","folder":"IETF/RFC-1598","source":"IETF/RFC-1598/RFC-1598.txt","version":null},{"body":"IETF","designation":"RFC 1618","folder":"IETF/RFC-1618","source":"IETF/RFC-1618/RFC-1618.txt","version":null},{"body":"IETF","designation":"RFC 1619","folder":"IETF/RFC-1619","source":"IETF/RFC-1619/RFC-1619.txt","version":null},{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null}],"search_text":"IETF RFC 1548 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n is comprised of three main components:\n\n 1. A method for encapsulating multi-protocol datagrams.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP organization and methodology, and the\n PPP encapsulation, together with an extensible option negotiation\n mechanism which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions. The PPP Link Control Protocol (LCP) is described in terms\n of this mechanism.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Eng 1548 authentication management nested-reference unchanged"},{"id":"IETF RFC 2072","type":"specification","body":"IETF","designation":"RFC 2072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2072.txt","https://www.rfc-editor.org/rfc/rfc2072.pdf"],"folder":"IETF/RFC-2072","files":{"txt":{"path":"standards/IETF/RFC-2072/RFC-2072.txt","sha256":"9281f1f2e44c159c24963739caec776c5efb1f97334f7c93361b25200924adc0"}},"tags":["nested-reference","unchanged"],"summary":"IP addresses currently used by organizations are likely to undergo\n changes in the near to moderate term. Change can become necessary\n for a variety of reasons, including enterprise reorganization,\n physical moves of equipment, new strategic relationships, changes in\n Internet Service Providers (ISP), new applications, and the needs of\n global Internet connectivity. Good IP address management may in\n general simplify continuing system administration; a good renumbering\n plan is also a good numbering plan. Most actions taken to ease\n future renumbering will ease routine network administration.\n\n Routers are the components that interconnect parts of the IP address\n space identified by unique prefixes. Obviously, they will be\n impacted by renumbering. Other interconnection devices, such as\n bridges, layer 2 switches (i.e., specialized bridges), and ATM\n switches may be affected by renumberi","scope_keywords":["2072","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 2072 IP addresses currently used by organizations are likely to undergo\n changes in the near to moderate term. Change can become necessary\n for a variety of reasons, including enterprise reorganization,\n physical moves of equipment, new strategic relationships, changes in\n Internet Service Providers (ISP), new applications, and the needs of\n global Internet connectivity. Good IP address management may in\n general simplify continuing system administration; a good renumbering\n plan is also a good numbering plan. Most actions taken to ease\n future renumbering will ease routine network administration.\n\n Routers are the components that interconnect parts of the IP address\n space identified by unique prefixes. Obviously, they will be\n impacted by renumbering. Other interconnection devices, such as\n bridges, layer 2 switches (i.e., specialized bridges), and ATM\n switches may be affected by renumberi 2072 management nested-reference unchanged"},{"id":"IETF RFC 3153","type":"specification","body":"IETF","designation":"RFC 3153","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3153.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3153.txt","https://www.rfc-editor.org/rfc/rfc3153.pdf"],"folder":"IETF/RFC-3153","files":{"txt":{"path":"standards/IETF/RFC-3153/RFC-3153.txt","sha256":"e77668e1184f78d146c0ebe730ad985a31bf35faed6678366bc083b1b4c82da3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method to reduce the PPP (Point-to-Point\n Protocol) framing overhead used to transport small packets over slow\n links.\n\n1. Description\n\n The method, PPP Multiplexing, sends multiple PPP encapsulated packets\n in a single PPP frame. As a result, the PPP overhead per packet is\n reduced. PPP encapsulation (for example with PPP in HDLC framing)\n adds several bytes of overhead: a HDLC flag (at least one to separate\n adjacent packets), the Address (0xFF) and Control (0x03) field bytes,\n a two byte PPP Protocol ID, and the two byte CRC field. Even with\n the Address and Control Fields negotiated off and the PPP Protocol ID\n compressed, each PPP encapsulated frame will include four bytes of\n overhead. When PPP frames are tunneled, as in L2TP [1], the L2TP\n overhead per PPP frame is significant.\n\n The key idea is to concatenate multiple PPP encapsulated frames into\n a sing","scope_keywords":["3153","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null}],"search_text":"IETF RFC 3153 This document describes a method to reduce the PPP (Point-to-Point\n Protocol) framing overhead used to transport small packets over slow\n links.\n\n1. Description\n\n The method, PPP Multiplexing, sends multiple PPP encapsulated packets\n in a single PPP frame. As a result, the PPP overhead per packet is\n reduced. PPP encapsulation (for example with PPP in HDLC framing)\n adds several bytes of overhead: a HDLC flag (at least one to separate\n adjacent packets), the Address (0xFF) and Control (0x03) field bytes,\n a two byte PPP Protocol ID, and the two byte CRC field. Even with\n the Address and Control Fields negotiated off and the PPP Protocol ID\n compressed, each PPP encapsulated frame will include four bytes of\n overhead. When PPP frames are tunneled, as in L2TP [1], the L2TP\n overhead per PPP frame is significant.\n\n The key idea is to concatenate multiple PPP encapsulated frames into\n a sing 3153 key pid nested-reference unchanged"},{"id":"IETF RFC 3456","type":"specification","body":"IETF","designation":"RFC 3456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3456.txt","https://www.rfc-editor.org/rfc/rfc3456.pdf"],"folder":"IETF/RFC-3456","files":{"txt":{"path":"standards/IETF/RFC-3456/RFC-3456.txt","sha256":"79e86d7f30f22ec7b3395badc8e54205c220ccfac982ef8506c7766583ca29a9"}},"tags":["nested-reference","unchanged"],"summary":"This memo explores the requirements for host configuration in IPsec\n tunnel mode, and describes how the Dynamic Host Configuration\n Protocol (DHCPv4) may be leveraged for configuration. In many remote\n access scenarios, a mechanism for making the remote host appear to be\n present on the local corporate network is quite useful. This may be\n accomplished by assigning the host a \"virtual\" address from the\n corporate network, and then tunneling traffic via IPsec from the\n host's ISP-assigned address to the corporate security gateway. In\n IPv4, DHCP provides for such remote host configuration.\n\nPatel, et. al. Standards Track [Page 1]\n\f\nRFC 3456 DHCPv4 Config. of IPsec Tunnel Mode January 2003","scope_keywords":["3456","authentication","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3456 This memo explores the requirements for host configuration in IPsec\n tunnel mode, and describes how the Dynamic Host Configuration\n Protocol (DHCPv4) may be leveraged for configuration. In many remote\n access scenarios, a mechanism for making the remote host appear to be\n present on the local corporate network is quite useful. This may be\n accomplished by assigning the host a \"virtual\" address from the\n corporate network, and then tunneling traffic via IPsec from the\n host's ISP-assigned address to the corporate security gateway. In\n IPv4, DHCP provides for such remote host configuration.\n\nPatel, et. al. Standards Track [Page 1]\n\f\nRFC 3456 DHCPv4 Config. of IPsec Tunnel Mode January 2003 3456 authentication key management policy nested-reference unchanged"},{"id":"IETF RFC 5571","type":"specification","body":"IETF","designation":"RFC 5571","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5571.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5571.txt","https://www.rfc-editor.org/rfc/rfc5571.pdf"],"folder":"IETF/RFC-5571","files":{"txt":{"path":"standards/IETF/RFC-5571/RFC-5571.txt","sha256":"5fdacf03d847752fb58821b3618322b0879ee9f20e98c9a50121f58ad646471b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the framework of the Softwire \"Hub and Spoke\"\n solution with the Layer Two Tunneling Protocol version 2 (L2TPv2).\n The implementation details specified in this document should be\n followed to achieve interoperability among different vendor\n implementations.","scope_keywords":["5571","authentication","authorization","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null}],"search_text":"IETF RFC 5571 This document describes the framework of the Softwire \"Hub and Spoke\"\n solution with the Layer Two Tunneling Protocol version 2 (L2TPv2).\n The implementation details specified in this document should be\n followed to achieve interoperability among different vendor\n implementations. 5571 authentication authorization http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 2477","type":"specification","body":"IETF","designation":"RFC 2477","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2477.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2477.txt","https://www.rfc-editor.org/rfc/rfc2477.pdf"],"folder":"IETF/RFC-2477","files":{"txt":{"path":"standards/IETF/RFC-2477/RFC-2477.txt","sha256":"5ee215a20a1a2ccacba1347158cd7dee520818f14aa010cf0c9d6fd68f2b6db0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes requirements for the provisioning of \"roaming\n capability\" for dialup Internet users. \"Roaming capability\" is\n defined as the ability to use multiple Internet service providers\n (ISPs), while maintaining a formal, customer-vendor relationship with\n only one.\n\n2. Introduction\n\n Operational roaming services are currently providing worldwide\n roaming capabilities, and these services continue to grow in\n popularity [1]. Interested parties have included:\n\n Regional Internet Service Providers (ISPs) operating within a\n particular state or province, looking to combine their efforts\n with those of other regional providers to offer services over a\n wider area.\n\n National ISPs wishing to combine their operations with those of\n one or more ISPs in another nation to provide greater coverage in\n a group of countries or on a continent.\n\n Businesses desiring to offer their emplo","scope_keywords":["2477","attribute","attributes","audit","authentication","authorization","key","management","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null}],"search_text":"IETF RFC 2477 This document describes requirements for the provisioning of \"roaming\n capability\" for dialup Internet users. \"Roaming capability\" is\n defined as the ability to use multiple Internet service providers\n (ISPs), while maintaining a formal, customer-vendor relationship with\n only one.\n\n2. Introduction\n\n Operational roaming services are currently providing worldwide\n roaming capabilities, and these services continue to grow in\n popularity [1]. Interested parties have included:\n\n Regional Internet Service Providers (ISPs) operating within a\n particular state or province, looking to combine their efforts\n with those of other regional providers to offer services over a\n wider area.\n\n National ISPs wishing to combine their operations with those of\n one or more ISPs in another nation to provide greater coverage in\n a group of countries or on a continent.\n\n Businesses desiring to offer their emplo 2477 attribute attributes audit authentication authorization key management policy presentation nested-reference unchanged"},{"id":"IETF RFC 2637","type":"specification","body":"IETF","designation":"RFC 2637","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2637.txt","https://www.rfc-editor.org/rfc/rfc2637.pdf"],"folder":"IETF/RFC-2637","files":{"txt":{"path":"standards/IETF/RFC-2637/RFC-2637.txt","sha256":"6d8fdb238fc94b326156308d5dedb20dfb86ddea7a3d9cf0e3c483518b148230"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol which allows the Point to Point\n Protocol (PPP) to be tunneled through an IP network. PPTP does not\n specify any changes to the PPP protocol but rather describes a new\n vehicle for carrying PPP. A client-server architecture is defined in\n order to decouple functions which exist in current Network Access\n Servers (NAS) and support Virtual Private Networks (VPNs). The PPTP\n Network Server (PNS) is envisioned to run on a general purpose\n operating system while the client, referred to as a PPTP Access\n Concentrator (PAC) operates on a dial access platform. PPTP\n specifies a call-control and management protocol which allows the\n server to control access for dial-in circuit switched calls\n originating from a PSTN or ISDN or to initiate outbound circuit-\n\nHamzeh, et al. Informational [Page 1]\n\f\nRFC 2637 Point-to-Point Tunneling Protocol (PPTP) July 1999\n\n swit","scope_keywords":["2637","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2637 This document specifies a protocol which allows the Point to Point\n Protocol (PPP) to be tunneled through an IP network. PPTP does not\n specify any changes to the PPP protocol but rather describes a new\n vehicle for carrying PPP. A client-server architecture is defined in\n order to decouple functions which exist in current Network Access\n Servers (NAS) and support Virtual Private Networks (VPNs). The PPTP\n Network Server (PNS) is envisioned to run on a general purpose\n operating system while the client, referred to as a PPTP Access\n Concentrator (PAC) operates on a dial access platform. PPTP\n specifies a call-control and management protocol which allows the\n server to control access for dial-in circuit switched calls\n originating from a PSTN or ISDN or to initiate outbound circuit-\n\nHamzeh, et al. Informational [Page 1]\n\f\nRFC 2637 Point-to-Point Tunneling Protocol (PPTP) July 1999\n\n swit 2637 key management nested-reference unchanged"},{"id":"IETF RFC 1337","type":"specification","body":"IETF","designation":"RFC 1337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1337.txt","https://www.rfc-editor.org/rfc/rfc1337.pdf"],"folder":"IETF/RFC-1337","files":{"txt":{"path":"standards/IETF/RFC-1337/RFC-1337.txt","sha256":"6f042f91367e83bcf6bd830e35c8bb21d3956826f3b57efbc3d70259b445d476"}},"tags":["nested-reference","unchanged"],"summary":"This note describes some theoretically-possible failure modes for TCP\n connections and discusses possible remedies. In particular, one very\n simple fix is identified.\n\n1. INTRODUCTION\n\n Experiments to validate the recently-proposed TCP extensions [RFC-\n 1323] have led to the discovery of a new class of TCP failures, which\n have been dubbed the \"TIME-WAIT Assassination hazards\". This note\n describes these hazards, gives examples, and discusses possible\n prevention measures.\n\n The failures in question all result from old duplicate segments. In\n brief, the TCP mechanisms to protect against old duplicate segments\n are [RFC-793]:\n\n (1) The 3-way handshake rejects old duplicate initial <SYN>\n segments, avoiding the hazard of replaying a connection.\n\n (2) Sequence numbers are used to reject old duplicate data and ACK\n segments from the current incarnation of a given connection\n (defined by a pa","scope_keywords":["1337","algorithm","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1337 This note describes some theoretically-possible failure modes for TCP\n connections and discusses possible remedies. In particular, one very\n simple fix is identified.\n\n1. INTRODUCTION\n\n Experiments to validate the recently-proposed TCP extensions [RFC-\n 1323] have led to the discovery of a new class of TCP failures, which\n have been dubbed the \"TIME-WAIT Assassination hazards\". This note\n describes these hazards, gives examples, and discusses possible\n prevention measures.\n\n The failures in question all result from old duplicate segments. In\n brief, the TCP mechanisms to protect against old duplicate segments\n are [RFC-793]:\n\n (1) The 3-way handshake rejects old duplicate initial <SYN>\n segments, avoiding the hazard of replaying a connection.\n\n (2) Sequence numbers are used to reject old duplicate data and ACK\n segments from the current incarnation of a given connection\n (defined by a pa 1337 algorithm timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 1383","type":"specification","body":"IETF","designation":"RFC 1383","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1383.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1383.txt","https://www.rfc-editor.org/rfc/rfc1383.pdf"],"folder":"IETF/RFC-1383","files":{"txt":{"path":"standards/IETF/RFC-1383/RFC-1383.txt","sha256":"fde653b41234119cd0ec9ce4d4011bf2df0eb35ea944cfa7e43d3e512d7e78d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Huitema\nRequest for Comments: 1383 INRIA\n December 1992\n\n An Experiment in DNS Based IP Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Routing, scaling and hierarchies ...................... 1\n 2. Routing based on MX records ........................... 2\n 3. Evaluation of DNS routing ............................. 3\n 3.1 Loops and relays ..................................... 4\n 3.2 Performances and scaling ............................. 5\n 3.3 Tunneling or source routing .......................... 6\n 3.4 Choosing a gateway ...............................","scope_keywords":["1383","policies","policy","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1919","folder":"IETF/RFC-1919","source":"IETF/RFC-1919/RFC-1919.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null}],"search_text":"IETF RFC 1383 Network Working Group C. Huitema\nRequest for Comments: 1383 INRIA\n December 1992\n\n An Experiment in DNS Based IP Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Routing, scaling and hierarchies ...................... 1\n 2. Routing based on MX records ........................... 2\n 3. Evaluation of DNS routing ............................. 3\n 3.1 Loops and relays ..................................... 4\n 3.2 Performances and scaling ............................. 5\n 3.3 Tunneling or source routing .......................... 6\n 3.4 Choosing a gateway ............................... 1383 policies policy registered risk nested-reference unchanged"},{"id":"IETF RFC 1467","type":"specification","body":"IETF","designation":"RFC 1467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1467.txt","https://www.rfc-editor.org/rfc/rfc1467.pdf"],"folder":"IETF/RFC-1467","files":{"txt":{"path":"standards/IETF/RFC-1467/RFC-1467.txt","sha256":"f3e870a53b0cc2c27d78dcb5bc231abca8717612b42dd7cd4b804b930237809f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Topolcic\nRequest for Comments: 1467 CNRI\nObsoletes: 1367 August 1993\n\n Status of CIDR Deployment in the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document describes the current status of the development and\n deployment of CIDR technology into the Internet. This document\n replaces RFC 1367, which was a schedule for the deployment of IP\n address space management procedures to support route aggregation.\n Since all the milestones proposed in RFC 1367 except for the delivery\n and installation of CIDR software were met, it does not seem\n appropriate to issue an updated schedule. Rather, this document is\n intended to provide information about how this effort is proceeding,\n which may be of interest to the community.\n\n1. Ba","scope_keywords":["1467","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1467 Network Working Group C. Topolcic\nRequest for Comments: 1467 CNRI\nObsoletes: 1367 August 1993\n\n Status of CIDR Deployment in the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This document describes the current status of the development and\n deployment of CIDR technology into the Internet. This document\n replaces RFC 1367, which was a schedule for the deployment of IP\n address space management procedures to support route aggregation.\n Since all the milestones proposed in RFC 1367 except for the delivery\n and installation of CIDR software were met, it does not seem\n appropriate to issue an updated schedule. Rather, this document is\n intended to provide information about how this effort is proceeding,\n which may be of interest to the community.\n\n1. Ba 1467 delivery management nested-reference unchanged"},{"id":"IETF RFC 1481","type":"specification","body":"IETF","designation":"RFC 1481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1481.txt","https://www.rfc-editor.org/rfc/rfc1481.pdf"],"folder":"IETF/RFC-1481","files":{"txt":{"path":"standards/IETF/RFC-1481/RFC-1481.txt","sha256":"fb8a7bac202eb458579ef36b4460d922ef7cd8025187c2d00d32fc3100f08099"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Huitema, Chair\nRequest for Comments: 1481 Internet Architecture Board\n July 1993\n\n IAB Recommendation for an Intermediate Strategy to\n Address the Issue of Scaling\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nRecommendation\n\n Classless Inter-Domain Routing (CIDR) proposes strategies for address\n assignment of the existing IP address space with a view to conserve\n the address space and stem the explosive growth of routing tables in\n default-route-free routers run by transit routing domain providers\n [1]. CIDR is proposed as an immediate term strategy to extend the\n life of the current 32 bit IP address space. This strategy presumes\n that a suitable long term solution is being addressed within the\n Internet technical community.\n\n The basic compo","scope_keywords":["1481","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1481 Network Working Group C. Huitema, Chair\nRequest for Comments: 1481 Internet Architecture Board\n July 1993\n\n IAB Recommendation for an Intermediate Strategy to\n Address the Issue of Scaling\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nRecommendation\n\n Classless Inter-Domain Routing (CIDR) proposes strategies for address\n assignment of the existing IP address space with a view to conserve\n the address space and stem the explosive growth of routing tables in\n default-route-free routers run by transit routing domain providers\n [1]. CIDR is proposed as an immediate term strategy to extend the\n life of the current 32 bit IP address space. This strategy presumes\n that a suitable long term solution is being addressed within the\n Internet technical community.\n\n The basic compo 1481 management nested-reference unchanged"},{"id":"IETF RFC 1482","type":"specification","body":"IETF","designation":"RFC 1482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1482.txt","https://www.rfc-editor.org/rfc/rfc1482.pdf"],"folder":"IETF/RFC-1482","files":{"txt":{"path":"standards/IETF/RFC-1482/RFC-1482.txt","sha256":"08371cd0d3ffd1b91eeaf6937b30d219b2fe01c4ed086b75ad0e8756e84aac75"}},"tags":["nested-reference","unchanged"],"summary":"This document describes plans for support of route aggregation, as\n specified in the descriptions of Classless Inter-Domain Routing\n (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network\n Service. Mechanisms for exchange of route aggregates between the\n backbone service and regional/midlevel networks are specified.\n Additionally, the memo proposes the implementation of an Aggregate\n Registry which can be used by network service providers to share\n information about the use of aggregation. Finally, the operational\n impact of incorporating CIDR and aggregation is considered, including\n an analysis of how routing table size will be affected. This impact\n analysis will be used to modify the deployment plan, if necessary, to\n maximize operational stability.\n\n1. Introduction\n\n The Internet network service provider community and router vendors\n (as well as the IESG and various I","scope_keywords":["1482","key","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1520","folder":"IETF/RFC-1520","source":"IETF/RFC-1520/RFC-1520.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1482 This document describes plans for support of route aggregation, as\n specified in the descriptions of Classless Inter-Domain Routing\n (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network\n Service. Mechanisms for exchange of route aggregates between the\n backbone service and regional/midlevel networks are specified.\n Additionally, the memo proposes the implementation of an Aggregate\n Registry which can be used by network service providers to share\n information about the use of aggregation. Finally, the operational\n impact of incorporating CIDR and aggregation is considered, including\n an analysis of how routing table size will be affected. This impact\n analysis will be used to modify the deployment plan, if necessary, to\n maximize operational stability.\n\n1. Introduction\n\n The Internet network service provider community and router vendors\n (as well as the IESG and various I 1482 key path policies policy nested-reference unchanged"},{"id":"IETF RFC 1710","type":"specification","body":"IETF","designation":"RFC 1710","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1710.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1710.txt","https://www.rfc-editor.org/rfc/rfc1710.pdf"],"folder":"IETF/RFC-1710","files":{"txt":{"path":"standards/IETF/RFC-1710/RFC-1710.txt","sha256":"acd46fed88986031e4bb517536e0bf229a9c475fabfb0cd4bfd74f5b70fe99ce"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the author and/or the sipp@sunroof.eng.sun.com mailing\n list.\n\n1. Introduction\n\n This white paper presents an overview of the Simple Internet Protocol\n plus (SIPP) which is one of the candidates being considered in the\n Internet Engineering Task Force (IETF) for the next version of the\n Internet Protocol (the current version is usually referred to as\n IPv4). This white paper is not intended to be a detailed\n presentation of all of the features and motivation for SIPP, but is\n intended to give the reader an overview of the proposal. It is also\n not intended that this be an implementation specification, but given\n the simplicity of the central core of SIPP, an implementor familiar","scope_keywords":["1710","authentication","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 1710 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the author and/or the sipp@sunroof.eng.sun.com mailing\n list.\n\n1. Introduction\n\n This white paper presents an overview of the Simple Internet Protocol\n plus (SIPP) which is one of the candidates being considered in the\n Internet Engineering Task Force (IETF) for the next version of the\n Internet Protocol (the current version is usually referred to as\n IPv4). This white paper is not intended to be a detailed\n presentation of all of the features and motivation for SIPP, but is\n intended to give the reader an overview of the proposal. It is also\n not intended that this be an implementation specification, but given\n the simplicity of the central core of SIPP, an implementor familiar 1710 authentication key presentation nested-reference unchanged"},{"id":"IETF RFC 1393","type":"specification","body":"IETF","designation":"RFC 1393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1393.txt","https://www.rfc-editor.org/rfc/rfc1393.pdf"],"folder":"IETF/RFC-1393","files":{"txt":{"path":"standards/IETF/RFC-1393/RFC-1393.txt","sha256":"28b064e2e214e29f32feb98a9aa4d3437b4f4bd688195886536e3c9c6a20f1d4"}},"tags":["nested-reference","unchanged"],"summary":"Traceroute serves as a valuable network debugging tool. The way in\n which it is currently implemented has the advantage of being\n automatically supported by all of the routers. It's two problems are\n the number of packets it generates and the amount of time it takes to\n run.\n\n This document specifies a new IP option and ICMP message type which\n duplicates the functionality of the existing traceroute method while\n generating fewer packets and completing in a shorter time.","scope_keywords":["1393","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 1393 Traceroute serves as a valuable network debugging tool. The way in\n which it is currently implemented has the advantage of being\n automatically supported by all of the routers. It's two problems are\n the number of packets it generates and the amount of time it takes to\n run.\n\n This document specifies a new IP option and ICMP message type which\n duplicates the functionality of the existing traceroute method while\n generating fewer packets and completing in a shorter time. 1393 algorithm path nested-reference unchanged"},{"id":"IETF RFC 1409","type":"specification","body":"IETF","designation":"RFC 1409","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1409.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1409.txt","https://www.rfc-editor.org/rfc/rfc1409.pdf"],"folder":"IETF/RFC-1409","files":{"txt":{"path":"standards/IETF/RFC-1409/RFC-1409.txt","sha256":"871acea9ea614a26dbf7fce99bac3bf0d8c1693f45a5ec3c8569de217428bbfa"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman, Editor\nRequest for Comments: 1409 Cray Research, Inc.\n January 1993\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types\n NULL 0\n KERBEROSV4 1\n KERBEROSV5 2\n SPX 3\n RSA 6\n LOKI 10\n\n Modifiers\n AUTHWHOMASK 1\n AUTHCLIENTTOSERVER 0\n AUTHSERVERTOCLIENT 1\n AUTHHOWMASK 2\n AUTHHOWONEWAY 0\n AUTHHOW_MUTUAL 2\n\n2. Command Meanings\n\n This document makes reference to a \"server\" and a \"client\". For the\n purposes of this document, the \"server\" is the side of the con","scope_keywords":["1409","authentication","authorization","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1416","folder":"IETF/RFC-1416","source":"IETF/RFC-1416/RFC-1416.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1409 Network Working Group D. Borman, Editor\nRequest for Comments: 1409 Cray Research, Inc.\n January 1993\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types\n NULL 0\n KERBEROSV4 1\n KERBEROSV5 2\n SPX 3\n RSA 6\n LOKI 10\n\n Modifiers\n AUTHWHOMASK 1\n AUTHCLIENTTOSERVER 0\n AUTHSERVERTOCLIENT 1\n AUTHHOWMASK 2\n AUTHHOWONEWAY 0\n AUTHHOW_MUTUAL 2\n\n2. Command Meanings\n\n This document makes reference to a \"server\" and a \"client\". For the\n purposes of this document, the \"server\" is the side of the con 1409 authentication authorization registered trust nested-reference unchanged"},{"id":"IETF RFC 1413","type":"specification","body":"IETF","designation":"RFC 1413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1413.txt","https://www.rfc-editor.org/rfc/rfc1413.pdf"],"folder":"IETF/RFC-1413","files":{"txt":{"path":"standards/IETF/RFC-1413/RFC-1413.txt","sha256":"7c929a24780cf355bc1e1cfa5ace7057c629d3d1724be39347748745c664c18a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. St. Johns\nRequest for Comments: 1413 US Department of Defense\nObsoletes: 931 February 1993\n\n Identification Protocol\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n The Identification Protocol (a.k.a., \"ident\", a.k.a., \"the Ident\n Protocol\") provides a means to determine the identity of a user of a\n particular TCP connection. Given a TCP port number pair, it returns\n a character string which identifies the owner of that connection on\n the server's system.\n\n The Identification Protocol was formerly called the Authentication\n Server Protocol. It has been renam","scope_keywords":["1413","audit","authentication","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1414","folder":"IETF/RFC-1414","source":"IETF/RFC-1414/RFC-1414.txt","version":null},{"body":"IETF","designation":"RFC 1459","folder":"IETF/RFC-1459","source":"IETF/RFC-1459/RFC-1459.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1413 Network Working Group M. St. Johns\nRequest for Comments: 1413 US Department of Defense\nObsoletes: 931 February 1993\n\n Identification Protocol\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. INTRODUCTION\n\n The Identification Protocol (a.k.a., \"ident\", a.k.a., \"the Ident\n Protocol\") provides a means to determine the identity of a user of a\n particular TCP connection. Given a TCP port number pair, it returns\n a character string which identifies the owner of that connection on\n the server's system.\n\n The Identification Protocol was formerly called the Authentication\n Server Protocol. It has been renam 1413 audit authentication identification key nested-reference unchanged"},{"id":"IETF RFC 1416","type":"specification","body":"IETF","designation":"RFC 1416","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1416.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1416.txt","https://www.rfc-editor.org/rfc/rfc1416.pdf"],"folder":"IETF/RFC-1416","files":{"txt":{"path":"standards/IETF/RFC-1416/RFC-1416.txt","sha256":"26e06359d0be43b0bfae1d13b5a00a045e7e25a17ed652e5aa8b07c5200f7e6c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman, Editor\nRequest for Comments: 1416 Cray Research, Inc.\nObsoletes: 1409 February 1993\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nNote\n\n This RFC 1416 replaces RFC 1409, which has an important typographical\n error in the example on page 6 (one occurance of \"REPLY\" should be\n \"IS\").\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types\n NULL 0\n KERBEROSV4 1\n KERBEROSV5 2\n SPX 3\n RSA 6\n LOKI 10\n\n Modifiers\n AUTHWHOMASK 1\n AUTHCLIENTTOSERVER 0\n AUTHSERVERTOCLIENT 1\n AUTHHOWMASK 2\n AUTHHOWONEWAY 0\n A","scope_keywords":["1416","authentication","authorization","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2941","folder":"IETF/RFC-2941","source":"IETF/RFC-2941/RFC-2941.txt","version":null}],"search_text":"IETF RFC 1416 Network Working Group D. Borman, Editor\nRequest for Comments: 1416 Cray Research, Inc.\nObsoletes: 1409 February 1993\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\nNote\n\n This RFC 1416 replaces RFC 1409, which has an important typographical\n error in the example on page 6 (one occurance of \"REPLY\" should be\n \"IS\").\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types\n NULL 0\n KERBEROSV4 1\n KERBEROSV5 2\n SPX 3\n RSA 6\n LOKI 10\n\n Modifiers\n AUTHWHOMASK 1\n AUTHCLIENTTOSERVER 0\n AUTHSERVERTOCLIENT 1\n AUTHHOWMASK 2\n AUTHHOWONEWAY 0\n A 1416 authentication authorization registered trust nested-reference unchanged"},{"id":"IETF RFC 1428","type":"specification","body":"IETF","designation":"RFC 1428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1428.txt","https://www.rfc-editor.org/rfc/rfc1428.pdf"],"folder":"IETF/RFC-1428","files":{"txt":{"path":"standards/IETF/RFC-1428/RFC-1428.txt","sha256":"afe331bd95493ca29156ef2a65aa96f73a369cd3c1c03d7a5c44439e1f6d7251"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Vaudreuil\nRequest for Comments: 1428 CNRI\n February 1993\n\n Transition of Internet Mail from\n Just-Send-8\n to 8bit-SMTP/MIME\n\nStatus of this Memo\n\n This RFC provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n Protocols for extending SMTP to pass 8bit characters have been\n defined [3] [4]. These protocols require that messages transported by\n the extended SMTP are to be encoded in MIME [1] [2]. Before work\n began on these protocols, several SMTP implementations adopted ad-hoc\n mechanisms for sending 8bit data. It is desirable for the extended\n SMTP environment and these ad hoc mechanisms interoperate. This\n document outlines the problems in this environment and an approach to\n minimizing the cost of transition from current usage of non-MIME 8bit\n messages to MIME.\n\n1. Termi","scope_keywords":["1428","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null}],"search_text":"IETF RFC 1428 Network Working Group G. Vaudreuil\nRequest for Comments: 1428 CNRI\n February 1993\n\n Transition of Internet Mail from\n Just-Send-8\n to 8bit-SMTP/MIME\n\nStatus of this Memo\n\n This RFC provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n Protocols for extending SMTP to pass 8bit characters have been\n defined [3] [4]. These protocols require that messages transported by\n the extended SMTP are to be encoded in MIME [1] [2]. Before work\n began on these protocols, several SMTP implementations adopted ad-hoc\n mechanisms for sending 8bit data. It is desirable for the extended\n SMTP environment and these ad hoc mechanisms interoperate. This\n document outlines the problems in this environment and an approach to\n minimizing the cost of transition from current usage of non-MIME 8bit\n messages to MIME.\n\n1. Termi 1428 path nested-reference unchanged"},{"id":"IETF RFC 1492","type":"specification","body":"IETF","designation":"RFC 1492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1492.txt","https://www.rfc-editor.org/rfc/rfc1492.pdf"],"folder":"IETF/RFC-1492","files":{"txt":{"path":"standards/IETF/RFC-1492/RFC-1492.txt","sha256":"08f13ef358e810c965ec2251dc77fdee8cb1f939497ffbd0f253e8b2f63f058a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Finseth\nRequest for Comments: 1492 University of Minnesota\n July 1993\n\n An Access Control Protocol, Sometimes Called TACACS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nBackground\n\n There used to be a network called ARPANET. This network consisted of\n end nodes (hosts), routing nodes (IMPs) and links. There were (at\n least) two types of IMPs: those that connected dedicated lines only\n and those that could accept dial up lines. The latter were called\n \"TIPs.\"\n\n People being what they were, there was a desire to control who could\n use the dial up lines. Someone invented a protocol, called \"TACACS\"\n (Terminal Access Controller Access Control System?), which allowed a\n TIP to accept a username and password and send a query to a TACACS\n authenticat","scope_keywords":["1492","algorithm","algorithms","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 1492 Network Working Group C. Finseth\nRequest for Comments: 1492 University of Minnesota\n July 1993\n\n An Access Control Protocol, Sometimes Called TACACS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nBackground\n\n There used to be a network called ARPANET. This network consisted of\n end nodes (hosts), routing nodes (IMPs) and links. There were (at\n least) two types of IMPs: those that connected dedicated lines only\n and those that could accept dial up lines. The latter were called\n \"TIPs.\"\n\n People being what they were, there was a desire to control who could\n use the dial up lines. Someone invented a protocol, called \"TACACS\"\n (Terminal Access Controller Access Control System?), which allowed a\n TIP to accept a username and password and send a query to a TACACS\n authenticat 1492 algorithm algorithms authentication nested-reference unchanged"},{"id":"IETF RFC 1522","type":"specification","body":"IETF","designation":"RFC 1522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1522.txt","https://www.rfc-editor.org/rfc/rfc1522.pdf"],"folder":"IETF/RFC-1522","files":{"txt":{"path":"standards/IETF/RFC-1522/RFC-1522.txt","sha256":"a84d076f5296d04f9572388d9e24372fcaee5df47ba1e3cac3a506b1d086687f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an extension to the message format defined in RFC\n 1521 [1], to allow the representation of character sets other than\n ASCII in RFC 822 (STD 11) message headers. The extensions described\n were designed to be highly compatible with existing Internet mail\n handling software, and to be easily implemented in mail readers that\n support RFC 1521.\n\n1. Introduction\n\n RFC 1521 describes a mechanism for denoting textual body parts which\n are coded in various character sets, as well as methods for encoding\n such body parts as sequences of printable ASCII characters. This\n memo describes similar techniques to allow the encoding of non-ASCII\n text in various portions of a RFC 822 [2] message header, in a manner\n which is unlikely to confuse existing message handling software.\n\n Like the encoding techniques described in RFC 1521, the techniques\n outlined here were designed to allow","scope_keywords":["1522","crl","presentation","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 1557","folder":"IETF/RFC-1557","source":"IETF/RFC-1557/RFC-1557.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1651","folder":"IETF/RFC-1651","source":"IETF/RFC-1651/RFC-1651.txt","version":null},{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 1867","folder":"IETF/RFC-1867","source":"IETF/RFC-1867/RFC-1867.txt","version":null},{"body":"IETF","designation":"RFC 1869","folder":"IETF/RFC-1869","source":"IETF/RFC-1869/RFC-1869.txt","version":null},{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 1522 This memo describes an extension to the message format defined in RFC\n 1521 [1], to allow the representation of character sets other than\n ASCII in RFC 822 (STD 11) message headers. The extensions described\n were designed to be highly compatible with existing Internet mail\n handling software, and to be easily implemented in mail readers that\n support RFC 1521.\n\n1. Introduction\n\n RFC 1521 describes a mechanism for denoting textual body parts which\n are coded in various character sets, as well as methods for encoding\n such body parts as sequences of printable ASCII characters. This\n memo describes similar techniques to allow the encoding of non-ASCII\n text in various portions of a RFC 822 [2] message header, in a manner\n which is unlikely to confuse existing message handling software.\n\n Like the encoding techniques described in RFC 1521, the techniques\n outlined here were designed to allow 1522 crl presentation registered tls nested-reference unchanged"},{"id":"IETF RFC 1552","type":"specification","body":"IETF","designation":"RFC 1552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1552.txt","https://www.rfc-editor.org/rfc/rfc1552.pdf"],"folder":"IETF/RFC-1552","files":{"txt":{"path":"standards/IETF/RFC-1552/RFC-1552.txt","sha256":"90267ed58871f99232b507a3810fa53d264a4baa73f244843b5c9125e2769bcd"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a method for\n transmitting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n The IPX protocol was originally used in Novell's NetWare products\n [3], and is now supported by numerous other vendors. This document\n defines the Network Control Protocol for establishing and configuring\n the IPX protocol over PPP.\n\n This memo is the product of the Point-to-Point Protocol Working Group\n of the IETF. Comments should be submitted to the ietf-\n ppp@ucdavis.edu mailing list.\n\nSimpson [Page 1]\n\f\nRFC 1552 PPP IPXCP December 1993","scope_keywords":["1552"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1551","folder":"IETF/RFC-1551","source":"IETF/RFC-1551/RFC-1551.txt","version":null},{"body":"IETF","designation":"RFC 1553","folder":"IETF/RFC-1553","source":"IETF/RFC-1553/RFC-1553.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1552 The Point-to-Point Protocol (PPP) [1] provides a method for\n transmitting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n The IPX protocol was originally used in Novell's NetWare products\n [3], and is now supported by numerous other vendors. This document\n defines the Network Control Protocol for establishing and configuring\n the IPX protocol over PPP.\n\n This memo is the product of the Point-to-Point Protocol Working Group\n of the IETF. Comments should be submitted to the ietf-\n ppp@ucdavis.edu mailing list.\n\nSimpson [Page 1]\n\f\nRFC 1552 PPP IPXCP December 1993 1552 nested-reference unchanged"},{"id":"IETF RFC 1570","type":"specification","body":"IETF","designation":"RFC 1570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1570.txt","https://www.rfc-editor.org/rfc/rfc1570.pdf"],"folder":"IETF/RFC-1570","files":{"txt":{"path":"standards/IETF/RFC-1570/RFC-1570.txt","sha256":"a9ee4aa2e5bec501568acc07a7b33743de65910e1338c4380c617d9cbe024317"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) for establishing,\n configuring, and testing the data-link connection. This document\n defines several additional LCP features which have been suggested\n over the past few years.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@ucdavis.edu mailing list.","scope_keywords":["1570","identification","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null},{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1969","folder":"IETF/RFC-1969","source":"IETF/RFC-1969/RFC-1969.txt","version":null},{"body":"IETF","designation":"RFC 1977","folder":"IETF/RFC-1977","source":"IETF/RFC-1977/RFC-1977.txt","version":null},{"body":"IETF","designation":"RFC 1979","folder":"IETF/RFC-1979","source":"IETF/RFC-1979/RFC-1979.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 1993","folder":"IETF/RFC-1993","source":"IETF/RFC-1993/RFC-1993.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1570 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol (LCP) for establishing,\n configuring, and testing the data-link connection. This document\n defines several additional LCP features which have been suggested\n over the past few years.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@ucdavis.edu mailing list. 1570 identification license nested-reference unchanged"},{"id":"IETF RFC 1590","type":"specification","body":"IETF","designation":"RFC 1590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1590.txt","https://www.rfc-editor.org/rfc/rfc1590.pdf"],"folder":"IETF/RFC-1590","files":{"txt":{"path":"standards/IETF/RFC-1590/RFC-1590.txt","sha256":"13b9c19c85a17defb795f6570c3212b0cf86d7ec3890f45f83cdcd2cecfc18c2"}},"tags":["nested-reference","unchanged"],"summary":"Several protocols allow the use of data representing different\n \"media\" such as text, images, audio, and video, and within such media\n different encoding styles, such as (in video) jpeg, gif, ief, and\n tiff. The Multimedia Internet Message Extensions (MIME) protocol [1]\n defined several initial types of multimedia data objects, and a\n procedure for registering additional types with the Internet Assigned\n Numbers Authority (IANA). Several questions have been raised about\n the requirements and administrative procedure for registering MIME\n content-type and subtypes, and the use of these Media Types for other\n applications. This document addresses these issues and specifies a\n procedure for the registration of new Media Types (content-\n type/subtypes). It also generalizes the scope of use of these Media\n Types to make it appropriate to use the same registrations and\n specifications with oth","scope_keywords":["1590","identification","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1872","folder":"IETF/RFC-1872","source":"IETF/RFC-1872/RFC-1872.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2017","folder":"IETF/RFC-2017","source":"IETF/RFC-2017/RFC-2017.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null}],"search_text":"IETF RFC 1590 Several protocols allow the use of data representing different\n \"media\" such as text, images, audio, and video, and within such media\n different encoding styles, such as (in video) jpeg, gif, ief, and\n tiff. The Multimedia Internet Message Extensions (MIME) protocol [1]\n defined several initial types of multimedia data objects, and a\n procedure for registering additional types with the Internet Assigned\n Numbers Authority (IANA). Several questions have been raised about\n the requirements and administrative procedure for registering MIME\n content-type and subtypes, and the use of these Media Types for other\n applications. This document addresses these issues and specifies a\n procedure for the registration of new Media Types (content-\n type/subtypes). It also generalizes the scope of use of these Media\n Types to make it appropriate to use the same registrations and\n specifications with oth 1590 identification registered risk subject nested-reference unchanged"},{"id":"IETF RFC 1661","type":"specification","body":"IETF","designation":"RFC 1661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1661.txt","https://www.rfc-editor.org/rfc/rfc1661.pdf"],"folder":"IETF/RFC-1661","files":{"txt":{"path":"standards/IETF/RFC-1661/RFC-1661.txt","sha256":"23f061fcdccf43f3016d3e896213f3f887ff07caa4d408e9125ce55cbdb1434b"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n is comprised of three main components:\n\n 1. A method for encapsulating multi-protocol datagrams.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP organization and methodology, and the\n PPP encapsulation, together with an extensible option negotiation\n mechanism which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions. The PPP Link Control Protocol (LCP) is described in terms\n of this mechanism.","scope_keywords":["1661","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null},{"body":"IETF","designation":"RFC 1663","folder":"IETF/RFC-1663","source":"IETF/RFC-1663/RFC-1663.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1877","folder":"IETF/RFC-1877","source":"IETF/RFC-1877/RFC-1877.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1962","folder":"IETF/RFC-1962","source":"IETF/RFC-1962/RFC-1962.txt","version":null},{"body":"IETF","designation":"RFC 1967","folder":"IETF/RFC-1967","source":"IETF/RFC-1967/RFC-1967.txt","version":null},{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 1969","folder":"IETF/RFC-1969","source":"IETF/RFC-1969/RFC-1969.txt","version":null},{"body":"IETF","designation":"RFC 1973","folder":"IETF/RFC-1973","source":"IETF/RFC-1973/RFC-1973.txt","version":null},{"body":"IETF","designation":"RFC 1974","folder":"IETF/RFC-1974","source":"IETF/RFC-1974/RFC-1974.txt","version":null},{"body":"IETF","designation":"RFC 1977","folder":"IETF/RFC-1977","source":"IETF/RFC-1977/RFC-1977.txt","version":null},{"body":"IETF","designation":"RFC 1979","folder":"IETF/RFC-1979","source":"IETF/RFC-1979/RFC-1979.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 1993","folder":"IETF/RFC-1993","source":"IETF/RFC-1993/RFC-1993.txt","version":null},{"body":"IETF","designation":"RFC 1994","folder":"IETF/RFC-1994","source":"IETF/RFC-1994/RFC-1994.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2023","folder":"IETF/RFC-2023","source":"IETF/RFC-2023/RFC-2023.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2118","folder":"IETF/RFC-2118","source":"IETF/RFC-2118/RFC-2118.txt","version":null},{"body":"IETF","designation":"RFC 2125","folder":"IETF/RFC-2125","source":"IETF/RFC-2125/RFC-2125.txt","version":null},{"body":"IETF","designation":"RFC 2153","folder":"IETF/RFC-2153","source":"IETF/RFC-2153/RFC-2153.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 2420","folder":"IETF/RFC-2420","source":"IETF/RFC-2420/RFC-2420.txt","version":null},{"body":"IETF","designation":"RFC 2433","folder":"IETF/RFC-2433","source":"IETF/RFC-2433/RFC-2433.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2615","folder":"IETF/RFC-2615","source":"IETF/RFC-2615/RFC-2615.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2809","folder":"IETF/RFC-2809","source":"IETF/RFC-2809/RFC-2809.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2886","folder":"IETF/RFC-2886","source":"IETF/RFC-2886/RFC-2886.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3818","folder":"IETF/RFC-3818","source":"IETF/RFC-3818/RFC-3818.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5154","folder":"IETF/RFC-5154","source":"IETF/RFC-5154/RFC-5154.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 1661 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n is comprised of three main components:\n\n 1. A method for encapsulating multi-protocol datagrams.\n\n 2. A Link Control Protocol (LCP) for establishing, configuring,\n and testing the data-link connection.\n\n 3. A family of Network Control Protocols (NCPs) for establishing\n and configuring different network-layer protocols.\n\n This document defines the PPP organization and methodology, and the\n PPP encapsulation, together with an extensible option negotiation\n mechanism which is able to negotiate a rich assortment of\n configuration parameters and provides additional management\n functions. The PPP Link Control Protocol (LCP) is described in terms\n of this mechanism. 1661 authentication management nested-reference unchanged"},{"id":"IETF RFC 1662","type":"specification","body":"IETF","designation":"RFC 1662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1662.txt","https://www.rfc-editor.org/rfc/rfc1662.pdf"],"folder":"IETF/RFC-1662","files":{"txt":{"path":"standards/IETF/RFC-1662/RFC-1662.txt","sha256":"97fc11c5117461af5bdb8f3076f8d2e4d52c81935ab144cd4f50cb41e3aef2c1"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of HDLC-like framing for PPP\n encapsulated packets.","scope_keywords":["1662"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1663","folder":"IETF/RFC-1663","source":"IETF/RFC-1663/RFC-1663.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1967","folder":"IETF/RFC-1967","source":"IETF/RFC-1967/RFC-1967.txt","version":null},{"body":"IETF","designation":"RFC 1973","folder":"IETF/RFC-1973","source":"IETF/RFC-1973/RFC-1973.txt","version":null},{"body":"IETF","designation":"RFC 1977","folder":"IETF/RFC-1977","source":"IETF/RFC-1977/RFC-1977.txt","version":null},{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2615","folder":"IETF/RFC-2615","source":"IETF/RFC-2615/RFC-2615.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 1662 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of HDLC-like framing for PPP\n encapsulated packets. 1662 nested-reference unchanged"},{"id":"IETF RFC 1342","type":"specification","body":"IETF","designation":"RFC 1342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1342.txt","https://www.rfc-editor.org/rfc/rfc1342.pdf"],"folder":"IETF/RFC-1342","files":{"txt":{"path":"standards/IETF/RFC-1342/RFC-1342.txt","sha256":"be3f6457b7e35169ee05c58b8207a0d888ff8d382765c1ba7ecafb07eb270582"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an extension to the message format defined in [1]\n (known to the IETF Mail Extensions Working Group as \"RFC 1341\"), to\n allow the representation of character sets other than ASCII in RFC\n 822 message headers. The extensions described were designed to be\n highly compatible with existing Internet mail handling software, and\n to be easily implemented in mail readers that support RFC 1341.","scope_keywords":["1342","presentation","subject","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1425","folder":"IETF/RFC-1425","source":"IETF/RFC-1425/RFC-1425.txt","version":null},{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null}],"search_text":"IETF RFC 1342 This memo describes an extension to the message format defined in [1]\n (known to the IETF Mail Extensions Working Group as \"RFC 1341\"), to\n allow the representation of character sets other than ASCII in RFC\n 822 message headers. The extensions described were designed to be\n highly compatible with existing Internet mail handling software, and\n to be easily implemented in mail readers that support RFC 1341. 1342 presentation subject tls tsp nested-reference unchanged"},{"id":"IETF RFC 1343","type":"specification","body":"IETF","designation":"RFC 1343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1343.txt","https://www.rfc-editor.org/rfc/rfc1343.pdf"],"folder":"IETF/RFC-1343","files":{"pdf":{"path":"standards/IETF/RFC-1343/RFC-1343.pdf","sha256":"a33a05ac081fd61259cd61cfdf07414d2e2ad1daa38c703381f49f4dc8d9aa58"},"txt":{"path":"standards/IETF/RFC-1343/RFC-1343.txt","sha256":"e9348e4e9aac55f4df877bdb3812df22a296e5f0aac34b1f90419b2481807e8d"}},"tags":["nested-reference","unchanged"],"summary":"This memo suggests a file format to be used to inform\n multiple mail reading user agent programs about the\n locally-installed facilities for handling mail in various\n formats. The mechanism is explicitly designed to work with\n mail systems based Internet mail as defined by RFC's 821,\n 822, 934, 1049, 1113, and the Multipurpose Internet Mail\n Extensions, known as MIME. However, with some extensions it\n could probably be made to work for X.400-based mail systems\n as well. The format and mechanism are proposed in a manner\n that is generally operating-system independent. However,\n certain implementation details will inevitably reflect\n operating system differences, some of which will have to be\n handled in a uniform manner for each operating system. This\n memo makes such situations explicit, and, in an appendix,\n suggests a standard behavior under the UNIX operating\n system.","scope_keywords":["1343","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null}],"search_text":"IETF RFC 1343 This memo suggests a file format to be used to inform\n multiple mail reading user agent programs about the\n locally-installed facilities for handling mail in various\n formats. The mechanism is explicitly designed to work with\n mail systems based Internet mail as defined by RFC's 821,\n 822, 934, 1049, 1113, and the Multipurpose Internet Mail\n Extensions, known as MIME. However, with some extensions it\n could probably be made to work for X.400-based mail systems\n as well. The format and mechanism are proposed in a manner\n that is generally operating-system independent. However,\n certain implementation details will inevitably reflect\n operating system differences, some of which will have to be\n handled in a uniform manner for each operating system. This\n memo makes such situations explicit, and, in an appendix,\n suggests a standard behavior under the UNIX operating\n system. 1343 presentation nested-reference unchanged"},{"id":"IETF RFC 1344","type":"specification","body":"IETF","designation":"RFC 1344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1344.txt","https://www.rfc-editor.org/rfc/rfc1344.pdf"],"folder":"IETF/RFC-1344","files":{"pdf":{"path":"standards/IETF/RFC-1344/RFC-1344.pdf","sha256":"db0792985e0697ba0cff41f00a2bb1303761228ea4f13b1d506af2fa817f09d6"},"txt":{"path":"standards/IETF/RFC-1344/RFC-1344.txt","sha256":"81ef820683a6ac2c3f20db4494296cc5981482020708b8213fef77b814f3b80e"}},"tags":["nested-reference","unchanged"],"summary":"of message transport, does not necessarily mean that it\n should be ignored. In particular, MIME offers several\n features that should be of interest to those responsible for\n message transport services. By exploiting these features,\n transport systems can provide certain additional kinds of\n service that are currently unavailable, and can alleviate a\n few existing problems.","scope_keywords":["1344","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1344 of message transport, does not necessarily mean that it\n should be ignored. In particular, MIME offers several\n features that should be of interest to those responsible for\n message transport services. By exploiting these features,\n transport systems can provide certain additional kinds of\n service that are currently unavailable, and can alleviate a\n few existing problems. 1344 key subject nested-reference unchanged"},{"id":"IETF RFC 1426","type":"specification","body":"IETF","designation":"RFC 1426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1426.txt","https://www.rfc-editor.org/rfc/rfc1426.pdf"],"folder":"IETF/RFC-1426","files":{"txt":{"path":"standards/IETF/RFC-1426/RFC-1426.txt","sha256":"860d14c755c38a3d0b9e2a50bb973b1d9255eea369fde1effe4907ba5cdc121e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Klensin, WG Chair\nRequest for Comments: 1426 United Nations University\n N. Freed, Editor\n Innosoft International, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n E. Stefferud\n Network Management Associates, Inc.\n D. Crocker\n The Branch Office\n February 1993\n\n SMTP Service Extension\n for 8bit-MIMEtransport\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Abstract\n\n This memo defines an extension to the SMTP service whereby an SMTP\n content body containing octets outside of the US ASCII octet range\n (hex 00-7F) may be relayed using SMTP.\n\n2. Introduction\n\n Although SMTP is widel","scope_keywords":["1426","algorithm","crl","delivery","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1830","folder":"IETF/RFC-1830","source":"IETF/RFC-1830/RFC-1830.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null}],"search_text":"IETF RFC 1426 Network Working Group J. Klensin, WG Chair\nRequest for Comments: 1426 United Nations University\n N. Freed, Editor\n Innosoft International, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n E. Stefferud\n Network Management Associates, Inc.\n D. Crocker\n The Branch Office\n February 1993\n\n SMTP Service Extension\n for 8bit-MIMEtransport\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Abstract\n\n This memo defines an extension to the SMTP service whereby an SMTP\n content body containing octets outside of the US ASCII octet range\n (hex 00-7F) may be relayed using SMTP.\n\n2. Introduction\n\n Although SMTP is widel 1426 algorithm crl delivery key management subject nested-reference unchanged"},{"id":"IETF RFC 1437","type":"specification","body":"IETF","designation":"RFC 1437","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1437.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1437.txt","https://www.rfc-editor.org/rfc/rfc1437.pdf"],"folder":"IETF/RFC-1437","files":{"txt":{"path":"standards/IETF/RFC-1437/RFC-1437.txt","sha256":"7ae13869fa212ed31c008440b3897d6480a3f806d110b50296a585fa78a893f0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Borenstein\nRequest for Comments: 1437 Bellcore\n M. Linimon\n Lonesome Dove Computing Services\n 1 April 1993\n\n The Extension of MIME Content-Types to a New Medium\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n A previous document, RFC 1341, defines a format and general framework\n for the representation of a wide variety of data types in Internet\n mail. This document defines one particular type of MIME data, the\n matter-transport/sentient-life-form type. The matter-\n transport/sentient-life-form MIME type is intended to facilitate the\n wider interoperation of electronic mail messages that include entire\n sentient life forms, such as human beings.\n\n Other informally proposed subtypes, such as \"non-sentient-life-form\",\n \"non-sentient-non-l","scope_keywords":["1437","presentation","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null}],"search_text":"IETF RFC 1437 Network Working Group N. Borenstein\nRequest for Comments: 1437 Bellcore\n M. Linimon\n Lonesome Dove Computing Services\n 1 April 1993\n\n The Extension of MIME Content-Types to a New Medium\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n A previous document, RFC 1341, defines a format and general framework\n for the representation of a wide variety of data types in Internet\n mail. This document defines one particular type of MIME data, the\n matter-transport/sentient-life-form type. The matter-\n transport/sentient-life-form MIME type is intended to facilitate the\n wider interoperation of electronic mail messages that include entire\n sentient life forms, such as human beings.\n\n Other informally proposed subtypes, such as \"non-sentient-life-form\",\n \"non-sentient-non-l 1437 presentation risk subject nested-reference unchanged"},{"id":"IETF RFC 1440","type":"specification","body":"IETF","designation":"RFC 1440","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1440.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1440.txt","https://www.rfc-editor.org/rfc/rfc1440.pdf"],"folder":"IETF/RFC-1440","files":{"txt":{"path":"standards/IETF/RFC-1440/RFC-1440.txt","sha256":"d8bf710920356e78bc1df4c1d9ac09665b25006e87fb490384be64c9179561c7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Troth\nRequest for Comments: 1440 Rice University\n July 1993\n\n SIFT/UFT: Sender-Initiated/Unsolicited File Transfer\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This document describes a Sender-Initiated File Transfer (SIFT)\n protocol, also commonly called Unsolicited File Transfer (UFT)\n protocol. The acronyms SIFT and UFT are synonymous throughout this\n document. The term \"unsolicited\" does not imply that the file is\n unwanted, but that the receiver did not initiate the transaction.\n\n Sender-Initiated File Transfer cont","scope_keywords":["1440","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1440 Network Working Group R. Troth\nRequest for Comments: 1440 Rice University\n July 1993\n\n SIFT/UFT: Sender-Initiated/Unsolicited File Transfer\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"IAB Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This document describes a Sender-Initiated File Transfer (SIFT)\n protocol, also commonly called Unsolicited File Transfer (UFT)\n protocol. The acronyms SIFT and UFT are synonymous throughout this\n document. The term \"unsolicited\" does not imply that the file is\n unwanted, but that the receiver did not initiate the transaction.\n\n Sender-Initiated File Transfer cont 1440 presentation nested-reference unchanged"},{"id":"IETF RFC 1563","type":"specification","body":"IETF","designation":"RFC 1563","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1563.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1563.txt","https://www.rfc-editor.org/rfc/rfc1563.pdf"],"folder":"IETF/RFC-1563","files":{"pdf":{"path":"standards/IETF/RFC-1563/RFC-1563.pdf","sha256":"f6f6e3c2950164fda4fc90aab4bd170e2da9281dfb9991533fdbcff592568ca5"},"txt":{"path":"standards/IETF/RFC-1563/RFC-1563.txt","sha256":"7217774e9046f8fce8926ec3faf5fdd00f7117630e4aca8c207f368da6e4a4ff"}},"tags":["nested-reference","unchanged"],"summary":"MIME [RFC-1341, RFC-1521] defines a format and general framework for\n the representation of a wide variety of data types in Internet mail.\n This document defines one particular type of MIME data, the\n text/enriched type, a refinement of the \"text/richtext\" type defined\n in RFC 1341. The text/enriched MIME type is intended to facilitate\n the wider interoperation of simple enriched text across a wide\n variety of hardware and software platforms.","scope_keywords":["1563","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1896","folder":"IETF/RFC-1896","source":"IETF/RFC-1896/RFC-1896.txt","version":null}],"search_text":"IETF RFC 1563 MIME [RFC-1341, RFC-1521] defines a format and general framework for\n the representation of a wide variety of data types in Internet mail.\n This document defines one particular type of MIME data, the\n text/enriched type, a refinement of the \"text/richtext\" type defined\n in RFC 1341. The text/enriched MIME type is intended to facilitate\n the wider interoperation of simple enriched text across a wide\n variety of hardware and software platforms. 1563 crl presentation nested-reference unchanged"},{"id":"IETF RFC 2112","type":"specification","body":"IETF","designation":"RFC 2112","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2112.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2112.txt","https://www.rfc-editor.org/rfc/rfc2112.pdf"],"folder":"IETF/RFC-2112","files":{"txt":{"path":"standards/IETF/RFC-2112/RFC-2112.txt","sha256":"598a5ce954311d83e1b89a8520c49d05ac0f42231e63c6ffb9e116226c38c4b3"}},"tags":["nested-reference","unchanged"],"summary":"The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to ","scope_keywords":["2112","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null}],"search_text":"IETF RFC 2112 The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to  2112 presentation subject nested-reference unchanged"},{"id":"IETF RFC 2161","type":"specification","body":"IETF","designation":"RFC 2161","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2161.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2161.txt","https://www.rfc-editor.org/rfc/rfc2161.pdf"],"folder":"IETF/RFC-2161","files":{"txt":{"path":"standards/IETF/RFC-2161/RFC-2161.txt","sha256":"20fa1fde1ac9b9bd70b17620f45816d72c9171352165a50fa844354dcc2219e9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2161 UNINETT\nCategory: Experimental January 1998\n\n A MIME Body Part for ODA\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n Status of this Memo ........................................ 1\n 1 Introduction .............................................. 1\n 1.1 The Application/ODA MIME content-type ................... 1\n 1.2 ODA - application/oda ................................... 2\n 2 Security Considerations ................................... 3\n 3 References ................................................ 4\n 4 Author's Address ....","scope_keywords":["2161","attribute","identification","key","presentation","profile","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2161 Network Working Group H. Alvestrand\nRequest for Comments: 2161 UNINETT\nCategory: Experimental January 1998\n\n A MIME Body Part for ODA\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n Status of this Memo ........................................ 1\n 1 Introduction .............................................. 1\n 1.1 The Application/ODA MIME content-type ................... 1\n 1.2 ODA - application/oda ................................... 2\n 2 Security Considerations ................................... 3\n 3 References ................................................ 4\n 4 Author's Address .... 2161 attribute identification key presentation profile risk nested-reference unchanged"},{"id":"IETF RFC 5738","type":"specification","body":"IETF","designation":"RFC 5738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5738.txt","https://www.rfc-editor.org/rfc/rfc5738.pdf"],"folder":"IETF/RFC-5738","files":{"txt":{"path":"standards/IETF/RFC-5738/RFC-5738.txt","sha256":"d0cbbaa1941792536ef8c0bd7f479518977fa8c5ea517b06aed71541367de58c"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Internet Message Access Protocol\n version 4rev1 (IMAP4rev1) to support UTF-8 encoded international\n characters in user names, mail addresses, and message headers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb","scope_keywords":["5738","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null}],"search_text":"IETF RFC 5738 This specification extends the Internet Message Access Protocol\n version 4rev1 (IMAP4rev1) to support UTF-8 encoded international\n characters in user names, mail addresses, and message headers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb 5738 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1345","type":"specification","body":"IETF","designation":"RFC 1345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1345.txt","https://www.rfc-editor.org/rfc/rfc1345.pdf"],"folder":"IETF/RFC-1345","files":{"txt":{"path":"standards/IETF/RFC-1345/RFC-1345.txt","sha256":"d1a4b6a3d6514f8ea96b74e49af40edae5c8edfcc1b1e7d9d7caebc9d622e3b0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Simonsen\nRequest for Comments: 1345 Rationel Almen Planlaegning\n June 1992\n\n Character Mnemonics & Character Sets\n\nStatus of the Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This memo lists a selection of characters and their presence in some\n coded character sets. To facilitate the coded character set\n tabulations an unambiguous mnemonic for each character is used, and a\n format for tabulating the coded character sets is defined. The coded\n character sets are given names for easy reference. A family of coded\n character sets called the mnemonic character sets and conversion\n between these coded character set without information loss is\n defined.\n\n The character set names are registered with the Internet Assigned\n Numbers Authority (IANA). Additional","scope_keywords":["1345","identification","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null}],"search_text":"IETF RFC 1345 Network Working Group K. Simonsen\nRequest for Comments: 1345 Rationel Almen Planlaegning\n June 1992\n\n Character Mnemonics & Character Sets\n\nStatus of the Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSummary\n\n This memo lists a selection of characters and their presence in some\n coded character sets. To facilitate the coded character set\n tabulations an unambiguous mnemonic for each character is used, and a\n format for tabulating the coded character sets is defined. The coded\n character sets are given names for easy reference. A family of coded\n character sets called the mnemonic character sets and conversion\n between these coded character set without information loss is\n defined.\n\n The character set names are registered with the Internet Assigned\n Numbers Authority (IANA). Additional 1345 identification presentation registered nested-reference unchanged"},{"id":"IETF RFC 1502","type":"specification","body":"IETF","designation":"RFC 1502","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1502.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1502.txt","https://www.rfc-editor.org/rfc/rfc1502.pdf"],"folder":"IETF/RFC-1502","files":{"txt":{"path":"standards/IETF/RFC-1502/RFC-1502.txt","sha256":"b9e2e1c8e29bbdd24579eb5ea0989a90c484d3e2bc3b05236b0749b3185288a7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 1502 SINTEF DELAB\n August 1993\n\n X.400 Use of Extended Character Sets\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n Since 1988, X.400 has had the capacity for carrying a large number of\n different character sets in a message by using the body part\n \"GeneralText\" defined by ISO/IEC 10021-7.\n\n Since 1992, the Internet also has the means of passing around\n messages containing multiple character sets, by using the mechanism\n defined in RFC-MIME.\n\n This RFC defines a suggested method of using \"GeneralText\" in order\n to harmonize","scope_keywords":["1502","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1502 Network Working Group H. Alvestrand\nRequest for Comments: 1502 SINTEF DELAB\n August 1993\n\n X.400 Use of Extended Character Sets\n\nStatus of this Memo\n\n This RFC specifies an IAB standards track protocol for the Internet\n community, and requests discussion and suggestions for improvements.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n Since 1988, X.400 has had the capacity for carrying a large number of\n different character sets in a message by using the body part\n \"GeneralText\" defined by ISO/IEC 10021-7.\n\n Since 1992, the Internet also has the means of passing around\n messages containing multiple character sets, by using the mechanism\n defined in RFC-MIME.\n\n This RFC defines a suggested method of using \"GeneralText\" in order\n to harmonize 1502 registered nested-reference unchanged"},{"id":"IETF RFC 1815","type":"specification","body":"IETF","designation":"RFC 1815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1815.txt","https://www.rfc-editor.org/rfc/rfc1815.pdf"],"folder":"IETF/RFC-1815","files":{"txt":{"path":"standards/IETF/RFC-1815/RFC-1815.txt","sha256":"9f693fb29bbbc64d2aea04a98b10e53c0440f741f83a3e32cb49c41c8a00fc1f"}},"tags":["nested-reference","unchanged"],"summary":"Though the ISO character set standard of ISO 10646 is specified\n reasonably well about European characters, it is not so useful in an\n fully internationalized environment.\n\n For the practical use of ISO 10646, a lot of external profiling such\n as restriction of characters, restriction of combination of\n characters and addition of language information is necessary.\n\n This memo provides information on such profiling, along with charset\n names to each profiled instance.\n\n Though all the effort is done to make the resulting charset as useful\n 10646 based charset as possible, the result is not so good. So, the\n charsets defined in this memo are only for reference purpose and its\n use for practical purpose is strongly discouraged.","scope_keywords":["1815","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1815 Though the ISO character set standard of ISO 10646 is specified\n reasonably well about European characters, it is not so useful in an\n fully internationalized environment.\n\n For the practical use of ISO 10646, a lot of external profiling such\n as restriction of characters, restriction of combination of\n characters and addition of language information is necessary.\n\n This memo provides information on such profiling, along with charset\n names to each profiled instance.\n\n Though all the effort is done to make the resulting charset as useful\n 10646 based charset as possible, the result is not so good. So, the\n charsets defined in this memo are only for reference purpose and its\n use for practical purpose is strongly discouraged. 1815 profile nested-reference unchanged"},{"id":"IETF RFC 2070","type":"specification","body":"IETF","designation":"RFC 2070","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2070.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2070.txt","https://www.rfc-editor.org/rfc/rfc2070.pdf"],"folder":"IETF/RFC-2070","files":{"txt":{"path":"standards/IETF/RFC-2070/RFC-2070.txt","sha256":"fd30882cc9e84e374bf9fe5ef188fd739c66e9722011cf3eca1bea4980bc5648"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Markup Language (HTML) is a markup language used to\n create hypertext documents that are platform independent. Initially,\n the application of HTML on the World Wide Web was seriously\n restricted by its reliance on the ISO-8859-1 coded character set,\n which is appropriate only for Western European languages. Despite\n this restriction, HTML has been widely used with other languages,\n using other coded character sets or character encodings, at the\n expense of interoperability.\n\n This document is meant to address the issue of the\n internationalization (i18n, i followed by 18 letters followed by n)\n of HTML by extending the specification of HTML and giving additional\n recommendations for proper internationalization support. A foremost\n consideration is to make sure that HTML remains a valid application\n of SGML, while enabling its use with all languages of the world.","scope_keywords":["2070","algorithm","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2310","folder":"IETF/RFC-2310","source":"IETF/RFC-2310/RFC-2310.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null}],"search_text":"IETF RFC 2070 The Hypertext Markup Language (HTML) is a markup language used to\n create hypertext documents that are platform independent. Initially,\n the application of HTML on the World Wide Web was seriously\n restricted by its reliance on the ISO-8859-1 coded character set,\n which is appropriate only for Western European languages. Despite\n this restriction, HTML has been widely used with other languages,\n using other coded character sets or character encodings, at the\n expense of interoperability.\n\n This document is meant to address the issue of the\n internationalization (i18n, i followed by 18 letters followed by n)\n of HTML by extending the specification of HTML and giving additional\n recommendations for proper internationalization support. A foremost\n consideration is to make sure that HTML remains a valid application\n of SGML, while enabling its use with all languages of the world. 2070 algorithm attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 1347","type":"specification","body":"IETF","designation":"RFC 1347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1347.txt","https://www.rfc-editor.org/rfc/rfc1347.pdf"],"folder":"IETF/RFC-1347","files":{"pdf":{"path":"standards/IETF/RFC-1347/RFC-1347.pdf","sha256":"958895346f78e6498edb1a2bf117b0f60e4bef64b4de2411dc79f4ed0950cce4"},"txt":{"path":"standards/IETF/RFC-1347/RFC-1347.txt","sha256":"35afcc6b23c136a033dc7f4f518231fcec92b503d9dfdfa297851a4ee5770304"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ross Callon\n Request for Comments: 1347 DEC\n June 1992\n\n TCP and UDP with Bigger Addresses (TUBA),\n A Simple Proposal for Internet Addressing and Routing\n\n Status of the Memo\n\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this\n memo is unlimited.\n\n 1 Summary\n\n The Internet is approaching a situation in which the current IP\n address space is no longer adequate for global addressing\n and routing. This is causing problems including: (i) Internet\n backbones and regionals are suffering from the need to maintain\n large amounts of routing information which is growing rapidly in\n size (approximately doubling each year); (ii) The Internet is\n running out of IP network numbers to assign. There is an urgent\n need to develop and deploy an approach to addressing and routing\n which solves these problems and ","scope_keywords":["1347","path","pid","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1348","folder":"IETF/RFC-1348","source":"IETF/RFC-1348/RFC-1348.txt","version":null},{"body":"IETF","designation":"RFC 1380","folder":"IETF/RFC-1380","source":"IETF/RFC-1380/RFC-1380.txt","version":null},{"body":"IETF","designation":"RFC 1385","folder":"IETF/RFC-1385","source":"IETF/RFC-1385/RFC-1385.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1347 Network Working Group Ross Callon\n Request for Comments: 1347 DEC\n June 1992\n\n TCP and UDP with Bigger Addresses (TUBA),\n A Simple Proposal for Internet Addressing and Routing\n\n Status of the Memo\n\n This memo provides information for the Internet community. It\n does not specify an Internet standard. Distribution of this\n memo is unlimited.\n\n 1 Summary\n\n The Internet is approaching a situation in which the current IP\n address space is no longer adequate for global addressing\n and routing. This is causing problems including: (i) Internet\n backbones and regionals are suffering from the need to maintain\n large amounts of routing information which is growing rapidly in\n size (approximately doubling each year); (ii) The Internet is\n running out of IP network numbers to assign. There is an urgent\n need to develop and deploy an approach to addressing and routing\n which solves these problems and  1347 path pid risk nested-reference unchanged"},{"id":"IETF RFC 2676","type":"specification","body":"IETF","designation":"RFC 2676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2676.txt","https://www.rfc-editor.org/rfc/rfc2676.pdf"],"folder":"IETF/RFC-2676","files":{"txt":{"path":"standards/IETF/RFC-2676/RFC-2676.txt","sha256":"02d95374171d63e44dfbb5ef7b2950f2cc08672c3c989fa27162c81dcca9b9fa"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes extensions to the OSPF [Moy98] protocol to\n support QoS routes. The focus of this document is on the algorithms\n used to compute QoS routes and on the necessary modifications to OSPF\n to support this function, e.g., the information needed, its format,\n how it is distributed, and how it is used by the QoS path selection\n process. Aspects related to how QoS routes are established and\n managed are also briefly discussed. The goal of this document is to\n identify a framework and possible approaches to allow deployment of\n QoS routing capabilities with the minimum possible impact to the\n existing routing infrastructure.\n\n In addition, experience from an implementation of the proposed\n extensions in the GateD environment [Con], along with performance\n measurements is presented.\n\nApostolopoulos, et al. Experimental [Page 1]\n\f\nRFC 2676 QoS Routing Mechanisms and OSPF Extensio","scope_keywords":["2676","algorithm","algorithms","path","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2702","folder":"IETF/RFC-2702","source":"IETF/RFC-2702/RFC-2702.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null}],"search_text":"IETF RFC 2676 This memo describes extensions to the OSPF [Moy98] protocol to\n support QoS routes. The focus of this document is on the algorithms\n used to compute QoS routes and on the necessary modifications to OSPF\n to support this function, e.g., the information needed, its format,\n how it is distributed, and how it is used by the QoS path selection\n process. Aspects related to how QoS routes are established and\n managed are also briefly discussed. The goal of this document is to\n identify a framework and possible approaches to allow deployment of\n QoS routing capabilities with the minimum possible impact to the\n existing routing infrastructure.\n\n In addition, experience from an implementation of the proposed\n extensions in the GateD environment [Con], along with performance\n measurements is presented.\n\nApostolopoulos, et al. Experimental [Page 1]\n\f\nRFC 2676 QoS Routing Mechanisms and OSPF Extensio 2676 algorithm algorithms path tsp nested-reference unchanged"},{"id":"IETF RFC 2873","type":"specification","body":"IETF","designation":"RFC 2873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2873.txt","https://www.rfc-editor.org/rfc/rfc2873.pdf"],"folder":"IETF/RFC-2873","files":{"txt":{"path":"standards/IETF/RFC-2873/RFC-2873.txt","sha256":"d1d32c030be4258cc7f43de94a49d3da462d0f2b697a4cc5461c0ba103b209eb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group X. Xiao\nRequest for Comments: 2873 Global Crossing\nCategory: Standards Track A. Hannan\n iVMG\n V. Paxson\n ACIRI/ICSI\n E. Crabbe\n Exodus Communications\n June 2000\n\n TCP Processing of the IPv4 Precedence Field\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This memo describes a conflict between TCP [RFC793] and DiffServ\n [RFC2475] on the use of the three leftmost bits in the TOS octet of\n an IPv4 header [RFC791]. In a network that contains DiffServ-capable\n nodes, ","scope_keywords":["2873"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2873 Network Working Group X. Xiao\nRequest for Comments: 2873 Global Crossing\nCategory: Standards Track A. Hannan\n iVMG\n V. Paxson\n ACIRI/ICSI\n E. Crabbe\n Exodus Communications\n June 2000\n\n TCP Processing of the IPv4 Precedence Field\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This memo describes a conflict between TCP [RFC793] and DiffServ\n [RFC2475] on the use of the three leftmost bits in the TOS octet of\n an IPv4 header [RFC791]. In a network that contains DiffServ-capable\n nodes,  2873 nested-reference unchanged"},{"id":"IETF RFC 135","type":"specification","body":"IETF","designation":"RFC 135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc135.txt","https://www.rfc-editor.org/rfc/rfc135.pdf"],"folder":"IETF/RFC-135","files":{"txt":{"path":"standards/IETF/RFC-135/RFC-135.txt","sha256":"8359c7fb84cf9795cc2a9da4c043bf4d9481dcec53c0f5fe3b319122e22308f3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Hathaway\nRequest for Comments: 135 AMES\nNIC: 6712 29 April 1971\nUpdates: 110\n\n Response to NWG/RFC #110\n (Conventions for Using an IBM 2741 Terminal as a User Console for\n Access to Network Server Hosts)\n\n I would like to propose the following conventions to replace the ones\n proposed in RFC #110. The original conventions suffer from lack of\n consideration of the correspondence 2741 and what I feel are\n inconsistencies and considerable difficulty of use. (The 2741\n terminal with correspondence keyboard does not have all of the\n standard characters, notably:\n\n less than \n logical not [1]\n vertical bar |\n\n Thus we must not use any of these characters in our conventions if we\n wish to support the correspondence 2741.)\n\n The dedication of certain characters to special functions involves a\n trade-off: the convenience of having the function as a single key\n versus the ","scope_keywords":["135","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null}],"search_text":"IETF RFC 135 Network Working Group W. Hathaway\nRequest for Comments: 135 AMES\nNIC: 6712 29 April 1971\nUpdates: 110\n\n Response to NWG/RFC #110\n (Conventions for Using an IBM 2741 Terminal as a User Console for\n Access to Network Server Hosts)\n\n I would like to propose the following conventions to replace the ones\n proposed in RFC #110. The original conventions suffer from lack of\n consideration of the correspondence 2741 and what I feel are\n inconsistencies and considerable difficulty of use. (The 2741\n terminal with correspondence keyboard does not have all of the\n standard characters, notably:\n\n less than \n logical not [1]\n vertical bar |\n\n Thus we must not use any of these characters in our conventions if we\n wish to support the correspondence 2741.)\n\n The dedication of certain characters to special functions involves a\n trade-off: the convenience of having the function as a single key\n versus the  135 key keys nested-reference unchanged"},{"id":"IETF RFC 1782","type":"specification","body":"IETF","designation":"RFC 1782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1782.txt","https://www.rfc-editor.org/rfc/rfc1782.pdf"],"folder":"IETF/RFC-1782","files":{"txt":{"path":"standards/IETF/RFC-1782/RFC-1782.txt","sha256":"c6795b4ea78e99340caba5ace2ce6b96cf8d20d3168a45eb5a38875efa58e247"}},"tags":["nested-reference","unchanged"],"summary":"The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. This document describes a simple extension to TFTP to\n allow option negotiation prior to the file transfer.","scope_keywords":["1782"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1783","folder":"IETF/RFC-1783","source":"IETF/RFC-1783/RFC-1783.txt","version":null},{"body":"IETF","designation":"RFC 1784","folder":"IETF/RFC-1784","source":"IETF/RFC-1784/RFC-1784.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2090","folder":"IETF/RFC-2090","source":"IETF/RFC-2090/RFC-2090.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1782 The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. This document describes a simple extension to TFTP to\n allow option negotiation prior to the file transfer. 1782 nested-reference unchanged"},{"id":"IETF RFC 1783","type":"specification","body":"IETF","designation":"RFC 1783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1783.txt","https://www.rfc-editor.org/rfc/rfc1783.pdf"],"folder":"IETF/RFC-1783","files":{"txt":{"path":"standards/IETF/RFC-1783/RFC-1783.txt","sha256":"411c80bad08606017c4c56d4ddd7ae5c1475c2f56a19a0459f00f86a6623979d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1783 Xylogics, Inc.\nUpdates: 1350 A. Harkin\nCategory: Standards Track Hewlett Packard Co.\n March 1995\n\n TFTP Blocksize Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. One of its primary uses is the booting of diskless\n nodes on a Local Area Network. TFTP is used because it is very\n simple to implement in a small node's limited ROM space. However,\n the choice ","scope_keywords":["1783","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1782","folder":"IETF/RFC-1782","source":"IETF/RFC-1782/RFC-1782.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2090","folder":"IETF/RFC-2090","source":"IETF/RFC-2090/RFC-2090.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1783 Network Working Group G. Malkin\nRequest for Comments: 1783 Xylogics, Inc.\nUpdates: 1350 A. Harkin\nCategory: Standards Track Hewlett Packard Co.\n March 1995\n\n TFTP Blocksize Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. One of its primary uses is the booting of diskless\n nodes on a Local Area Network. TFTP is used because it is very\n simple to implement in a small node's limited ROM space. However,\n the choice  1783 path nested-reference unchanged"},{"id":"IETF RFC 1784","type":"specification","body":"IETF","designation":"RFC 1784","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1784.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1784.txt","https://www.rfc-editor.org/rfc/rfc1784.pdf"],"folder":"IETF/RFC-1784","files":{"txt":{"path":"standards/IETF/RFC-1784/RFC-1784.txt","sha256":"51cd8b5b9db963dfc74c16227c4bcac7d4d577d13900a48b8e14168b2cd192ee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Comments: 1784 Xylogics, Inc.\nUpdates: 1350 A. Harkin\nCategory: Standards Track Hewlett Packard Co.\n March 1995\n\n TFTP Timeout Interval and Transfer Size Options\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes two TFTP options. The first allows the client\n and server to negotiate the Timeout Interval. The second allows the\n side receiving the file to","scope_keywords":["1784"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1782","folder":"IETF/RFC-1782","source":"IETF/RFC-1782/RFC-1782.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1784 Network Working Group G. Malkin\nRequest for Comments: 1784 Xylogics, Inc.\nUpdates: 1350 A. Harkin\nCategory: Standards Track Hewlett Packard Co.\n March 1995\n\n TFTP Timeout Interval and Transfer Size Options\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes two TFTP options. The first allows the client\n and server to negotiate the Timeout Interval. The second allows the\n side receiving the file to 1784 nested-reference unchanged"},{"id":"IETF RFC 2090","type":"specification","body":"IETF","designation":"RFC 2090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2090.txt","https://www.rfc-editor.org/rfc/rfc2090.pdf"],"folder":"IETF/RFC-2090","files":{"txt":{"path":"standards/IETF/RFC-2090/RFC-2090.txt","sha256":"5ee164bb2ca5a52096a06542c5c4e03ddd0b19c332459814069ef3c4ab962cd5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Emberson\nRequest for Comments: 2090 Lanworks Technologies Inc.\nCategory: Experimental February 1997\n\n TFTP Multicast Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes a new TFTP option. This new option will allow\n the multiple clients to receive the same file concurrently through\n the use of Multicast packets. The TFTP Option Extension mechanism is\n described in [2].\n\n Often when similar computers are booting remotely they will each\n download the same image file. By ad","scope_keywords":["2090","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2090 Network Working Group A. Emberson\nRequest for Comments: 2090 Lanworks Technologies Inc.\nCategory: Experimental February 1997\n\n TFTP Multicast Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes a new TFTP option. This new option will allow\n the multiple clients to receive the same file concurrently through\n the use of Multicast packets. The TFTP Option Extension mechanism is\n described in [2].\n\n Often when similar computers are booting remotely they will each\n download the same image file. By ad 2090 registered nested-reference unchanged"},{"id":"IETF RFC 2347","type":"specification","body":"IETF","designation":"RFC 2347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2347.txt","https://www.rfc-editor.org/rfc/rfc2347.pdf"],"folder":"IETF/RFC-2347","files":{"txt":{"path":"standards/IETF/RFC-2347/RFC-2347.txt","sha256":"dd858f38246b61dc46863a907e2834567270a92b03660a6bb120dc4a3339fb26"}},"tags":["nested-reference","unchanged"],"summary":"The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. This document describes a simple extension to TFTP to\n allow option negotiation prior to the file transfer.","scope_keywords":["2347"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2348","folder":"IETF/RFC-2348","source":"IETF/RFC-2348/RFC-2348.txt","version":null},{"body":"IETF","designation":"RFC 2349","folder":"IETF/RFC-2349","source":"IETF/RFC-2349/RFC-2349.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 3218","folder":"IETF/RFC-3218","source":"IETF/RFC-3218/RFC-3218.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2347 The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. This document describes a simple extension to TFTP to\n allow option negotiation prior to the file transfer. 2347 nested-reference unchanged"},{"id":"IETF RFC 2348","type":"specification","body":"IETF","designation":"RFC 2348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2348.txt","https://www.rfc-editor.org/rfc/rfc2348.pdf"],"folder":"IETF/RFC-2348","files":{"txt":{"path":"standards/IETF/RFC-2348/RFC-2348.txt","sha256":"fcd1e9959ef7bbacb20e3564c6c93089e77fbef62ea60e453e83d9d540bfac09"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Commments: 2348 Bay Networks\nUpdates: 1350 A. Harkin\nObsoletes: 1783 Hewlett Packard Co.\nCategory: Standards Track May 1998\n\n TFTP Blocksize Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. One of its primary uses is the booting of diskless\n nodes on a Local Area Network. TFTP is used be","scope_keywords":["2348","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2347","folder":"IETF/RFC-2347","source":"IETF/RFC-2347/RFC-2347.txt","version":null},{"body":"IETF","designation":"RFC 3347","folder":"IETF/RFC-3347","source":"IETF/RFC-3347/RFC-3347.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2348 Network Working Group G. Malkin\nRequest for Commments: 2348 Bay Networks\nUpdates: 1350 A. Harkin\nObsoletes: 1783 Hewlett Packard Co.\nCategory: Standards Track May 1998\n\n TFTP Blocksize Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host. One of its primary uses is the booting of diskless\n nodes on a Local Area Network. TFTP is used be 2348 path risk nested-reference unchanged"},{"id":"IETF RFC 2349","type":"specification","body":"IETF","designation":"RFC 2349","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2349.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2349.txt","https://www.rfc-editor.org/rfc/rfc2349.pdf"],"folder":"IETF/RFC-2349","files":{"txt":{"path":"standards/IETF/RFC-2349/RFC-2349.txt","sha256":"327758e6bf9178593bd48771be24682700e07fd682f1a468c0f54751196b4db6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest for Commments: 2349 Bay Networks\nUpdates: 1350 A. Harkin\nObsoletes: 1784 Hewlett Packard Co.\nCategory: Standards Track May 1998\n\n TFTP Timeout Interval and Transfer Size Options\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes two TFTP options. The first allows the client\n","scope_keywords":["2349","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2347","folder":"IETF/RFC-2347","source":"IETF/RFC-2347/RFC-2347.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null}],"search_text":"IETF RFC 2349 Network Working Group G. Malkin\nRequest for Commments: 2349 Bay Networks\nUpdates: 1350 A. Harkin\nObsoletes: 1784 Hewlett Packard Co.\nCategory: Standards Track May 1998\n\n TFTP Timeout Interval and Transfer Size Options\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Trivial File Transfer Protocol [1] is a simple, lock-step, file\n transfer protocol which allows a client to get or put a file onto a\n remote host.\n\n This document describes two TFTP options. The first allows the client\n 2349 risk nested-reference unchanged"},{"id":"IETF RFC 3617","type":"specification","body":"IETF","designation":"RFC 3617","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3617.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3617.txt","https://www.rfc-editor.org/rfc/rfc3617.pdf"],"folder":"IETF/RFC-3617","files":{"txt":{"path":"standards/IETF/RFC-3617/RFC-3617.txt","sha256":"fe8a29e6ee91ed6a6020dca8314f6585884c162c38ce79101499be4c936506e4"}},"tags":["nested-reference","unchanged"],"summary":"The Trivial File Transfer Protocol (TFTP) is a very simple TRIVIAL\n protocol that has been in use on the Internet for quite a long time.\n While this document discourages its continued use, largely due to\n security concerns, we do define a Uniform Resource Identifier (URI)\n scheme, as well as discuss the protocol's applicability.\n\n1. Introduction\n\n The Trivial File Transfer Protocol (TFTP) has been around for quite\n some time. Its common uses are to initially configure devices or to\n load new versions of operating system code [1]. As devices begin to\n adopt use of Uniform Resource Identifiers (URIs) and Uniform Resource\n Locators (URLs), for completeness we specify a way to reference files\n that is still quite common. Use of a URI is a convenient way to\n indicate underlying mechanism, server name or address, and file name.\n\n WHILE WE DEFINE THE TFTP URI TYPE, WE STRONGLY RECOMMEND AGAINST","scope_keywords":["3617","http","license","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null}],"search_text":"IETF RFC 3617 The Trivial File Transfer Protocol (TFTP) is a very simple TRIVIAL\n protocol that has been in use on the Internet for quite a long time.\n While this document discourages its continued use, largely due to\n security concerns, we do define a Uniform Resource Identifier (URI)\n scheme, as well as discuss the protocol's applicability.\n\n1. Introduction\n\n The Trivial File Transfer Protocol (TFTP) has been around for quite\n some time. Its common uses are to initially configure devices or to\n load new versions of operating system code [1]. As devices begin to\n adopt use of Uniform Resource Identifiers (URIs) and Uniform Resource\n Locators (URLs), for completeness we specify a way to reference files\n that is still quite common. Use of a URI is a convenient way to\n indicate underlying mechanism, server name or address, and file name.\n\n WHILE WE DEFINE THE TFTP URI TYPE, WE STRONGLY RECOMMEND AGAINST 3617 http license registered nested-reference unchanged"},{"id":"IETF RFC 4173","type":"specification","body":"IETF","designation":"RFC 4173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4173.txt","https://www.rfc-editor.org/rfc/rfc4173.pdf"],"folder":"IETF/RFC-4173","files":{"txt":{"path":"standards/IETF/RFC-4173/RFC-4173.txt","sha256":"8b1a181f8d20e3ee04e5a19720538f048105a71a09aa0eca71d72533f61775d6"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer System Interface (iSCSI) is a proposed\n transport protocol for Small Computer Systems Interface (SCSI) that\n operates on top of TCP. This memo describes a standard mechanism for\n enabling clients to bootstrap themselves using the iSCSI protocol.\n The goal of this standard is to enable iSCSI boot clients to obtain\n the information to open an iSCSI session with the iSCSI boot server.\n\n1. Introduction\n\n The Small Computer Systems Interface (SCSI) is a popular family of\n protocols for communicating with I/O devices, especially storage\n devices. SCSI can be characterized as a request/response messaging\n protocol with a standard architecture and componentized command sets\n for different device classes.\n\n iSCSI is a proposed transport protocol for SCSI that operates on top\n of TCP. The role of iSCSI is necessitated by the evolution of the\n system interconnect from a shar","scope_keywords":["4173","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4173 Internet Small Computer System Interface (iSCSI) is a proposed\n transport protocol for Small Computer Systems Interface (SCSI) that\n operates on top of TCP. This memo describes a standard mechanism for\n enabling clients to bootstrap themselves using the iSCSI protocol.\n The goal of this standard is to enable iSCSI boot clients to obtain\n the information to open an iSCSI session with the iSCSI boot server.\n\n1. Introduction\n\n The Small Computer Systems Interface (SCSI) is a popular family of\n protocols for communicating with I/O devices, especially storage\n devices. SCSI can be characterized as a request/response messaging\n protocol with a standard architecture and componentized command sets\n for different device classes.\n\n iSCSI is a proposed transport protocol for SCSI that operates on top\n of TCP. The role of iSCSI is necessitated by the evolution of the\n system interconnect from a shar 4173 key nested-reference unchanged"},{"id":"IETF RFC 5970","type":"specification","body":"IETF","designation":"RFC 5970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5970.txt","https://www.rfc-editor.org/rfc/rfc5970.pdf"],"folder":"IETF/RFC-5970","files":{"txt":{"path":"standards/IETF/RFC-5970/RFC-5970.txt","sha256":"6ace722259d01f43f4ec0a5e46683b57bc8ab91a3b3b7b3039b5ade43790550a"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a\n framework for passing configuration information to nodes on a\n network. This document describes new options for DHCPv6 that SHOULD\n be used for booting a node from the network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5970.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n docu","scope_keywords":["5970","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null}],"search_text":"IETF RFC 5970 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a\n framework for passing configuration information to nodes on a\n network. This document describes new options for DHCPv6 that SHOULD\n be used for booting a node from the network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5970.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n docu 5970 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 1447","type":"specification","body":"IETF","designation":"RFC 1447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1447.txt","https://www.rfc-editor.org/rfc/rfc1447.pdf"],"folder":"IETF/RFC-1447","files":{"txt":{"path":"standards/IETF/RFC-1447/RFC-1447.txt","sha256":"068ba1e6967a0efa9ca093ba2e1b3255e55f56b065f0c52ceb65c7a92f95e6f9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. McCloghrie\n Request for Comments: 1447 Hughes LAN Systems\n J. Galvin\n Trusted Information Systems\n April 1993\n\n Party MIB\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 Textual Conventions ................................. 4\n 3.2 Administrative Assignments .......................... 7\n 3.2.1 Initial Part","scope_keywords":["1447","authentication","authorization","management","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1442","folder":"IETF/RFC-1442","source":"IETF/RFC-1442/RFC-1442.txt","version":null},{"body":"IETF","designation":"RFC 1445","folder":"IETF/RFC-1445","source":"IETF/RFC-1445/RFC-1445.txt","version":null},{"body":"IETF","designation":"RFC 1446","folder":"IETF/RFC-1446","source":"IETF/RFC-1446/RFC-1446.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1450","folder":"IETF/RFC-1450","source":"IETF/RFC-1450/RFC-1450.txt","version":null},{"body":"IETF","designation":"RFC 1451","folder":"IETF/RFC-1451","source":"IETF/RFC-1451/RFC-1451.txt","version":null}],"search_text":"IETF RFC 1447 Network Working Group K. McCloghrie\n Request for Comments: 1447 Hughes LAN Systems\n J. Galvin\n Trusted Information Systems\n April 1993\n\n Party MIB\n for version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Definitions ........................................... 3\n 3.1 Textual Conventions ................................. 4\n 3.2 Administrative Assignments .......................... 7\n 3.2.1 Initial Part 1447 authentication authorization management policies trust nested-reference unchanged"},{"id":"IETF RFC 1551","type":"specification","body":"IETF","designation":"RFC 1551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1551.txt","https://www.rfc-editor.org/rfc/rfc1551.pdf"],"folder":"IETF/RFC-1551","files":{"txt":{"path":"standards/IETF/RFC-1551/RFC-1551.txt","sha256":"cc20cd881f4d1a1389247ede5eda906efd95641be927c3d0304494c967c33ceb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how Novell IPX operates over various WAN\n media. Specifically, it describes the common \"IPX WAN\" protocol\n Novell uses to exchange necessary router to router information prior\n to exchanging standard IPX routing information and traffic over WAN\n datalinks. This document supercedes RFC 1362 and adds capability for\n Unnumbered RIP links, On-demand statically routed links and client to\n router connectivity.","scope_keywords":["1551","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1552","folder":"IETF/RFC-1552","source":"IETF/RFC-1552/RFC-1552.txt","version":null},{"body":"IETF","designation":"RFC 1553","folder":"IETF/RFC-1553","source":"IETF/RFC-1553/RFC-1553.txt","version":null}],"search_text":"IETF RFC 1551 This document describes how Novell IPX operates over various WAN\n media. Specifically, it describes the common \"IPX WAN\" protocol\n Novell uses to exchange necessary router to router information prior\n to exchanging standard IPX routing information and traffic over WAN\n datalinks. This document supercedes RFC 1362 and adds capability for\n Unnumbered RIP links, On-demand statically routed links and client to\n router connectivity. 1551 identification management nested-reference unchanged"},{"id":"IETF RFC 1598","type":"specification","body":"IETF","designation":"RFC 1598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1598.txt","https://www.rfc-editor.org/rfc/rfc1598.pdf"],"folder":"IETF/RFC-1598","files":{"txt":{"path":"standards/IETF/RFC-1598/RFC-1598.txt","sha256":"69acfba4ed890a1fb5b9e227bff0a9d092f34116f774b2a378948b09339ecba8"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of X.25 for framing PPP encapsulated\n packets.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for PPP, such as the Link Control\n Protocol, Network-layer Control Protocols, authentication, and\n compression. These capabilities require a point-to-point\n relationship between peers, and are not designed for multi-point or\n multi-access environments.\n\nSimpson [Page i]\n\fRFC 1598 PPP in X.25 March 1994","scope_keywords":["1598","authentication","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1598 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of X.25 for framing PPP encapsulated\n packets.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for PPP, such as the Link Control\n Protocol, Network-layer Control Protocols, authentication, and\n compression. These capabilities require a point-to-point\n relationship between peers, and are not designed for multi-point or\n multi-access environments.\n\nSimpson [Page i]\n\fRFC 1598 PPP in X.25 March 1994 1598 authentication pid presentation nested-reference unchanged"},{"id":"IETF RFC 1357","type":"specification","body":"IETF","designation":"RFC 1357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1357.txt","https://www.rfc-editor.org/rfc/rfc1357.pdf"],"folder":"IETF/RFC-1357","files":{"txt":{"path":"standards/IETF/RFC-1357/RFC-1357.txt","sha256":"cdc3c90d7eae79d54afc1154a2a056725c5f2e6c79f632a5119d1adb189dc51b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a format for E-mailing bibliographic records of\n technical reports. It is intended to accelerate the dissemination\n of information about new Computer Science Technical Reports (CS-TR).","scope_keywords":["1357","crl","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1807","folder":"IETF/RFC-1807","source":"IETF/RFC-1807/RFC-1807.txt","version":null}],"search_text":"IETF RFC 1357 This memo defines a format for E-mailing bibliographic records of\n technical reports. It is intended to accelerate the dissemination\n of information about new Computer Science Technical Reports (CS-TR). 1357 crl key path nested-reference unchanged"},{"id":"IETF RFC 1807","type":"specification","body":"IETF","designation":"RFC 1807","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1807.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1807.txt","https://www.rfc-editor.org/rfc/rfc1807.pdf"],"folder":"IETF/RFC-1807","files":{"txt":{"path":"standards/IETF/RFC-1807/RFC-1807.txt","sha256":"e1cd4e06f52a2ebc2042f4d6e2ef5de57e5133782e0d3baeb80310e5981bce80"}},"tags":["nested-reference","unchanged"],"summary":"This RFC defines a format for bibliographic records describing\n technical reports. This format is used by the Cornell University\n Dienst protocol and the Stanford University SIFT system. The\n original RFC (RFC 1357) was written by D. Cohen, ISI, July 1992.\n This is a revision of RFC 1357. New fields include handle,\n other_access, keyword, and withdraw.","scope_keywords":["1807","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null}],"search_text":"IETF RFC 1807 This RFC defines a format for bibliographic records describing\n technical reports. This format is used by the Cornell University\n Dienst protocol and the Stanford University SIFT system. The\n original RFC (RFC 1357) was written by D. Cohen, ISI, July 1992.\n This is a revision of RFC 1357. New fields include handle,\n other_access, keyword, and withdraw. 1807 crl key nested-reference unchanged"},{"id":"IETF RFC 1358","type":"specification","body":"IETF","designation":"RFC 1358","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1358.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1358.txt","https://www.rfc-editor.org/rfc/rfc1358.pdf"],"folder":"IETF/RFC-1358","files":{"txt":{"path":"standards/IETF/RFC-1358/RFC-1358.txt","sha256":"2c7ee0af46d4ae49c3bb897eed1127afc6a0bb628c2ffef554ab7ee705e01798"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Chapin, Chair\nRequest for Comments: 1358 Internet Architecture Board\n August 1992\n\n Charter of the Internet Architecture Board (IAB)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSection 1.\n\n The Internet Architecture Board (IAB) shall be constituted and shall\n operate as a technical advisory group of the Internet Society. Its\n responsibilities shall include:\n\n (1) Expert and experienced oversight of the architecture of the\n worldwide multiprotocol Internet.\n\n (2) The editorial management and publication of the Request for\n Comments (RFC) document series, which constitutes the\n archival publication series for Internet Standards and\n related contributions by the Internet research and\n engineering community.\n\n (3) The development, review, and app","scope_keywords":["1358","management","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1396","folder":"IETF/RFC-1396","source":"IETF/RFC-1396/RFC-1396.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null}],"search_text":"IETF RFC 1358 Network Working Group L. Chapin, Chair\nRequest for Comments: 1358 Internet Architecture Board\n August 1992\n\n Charter of the Internet Architecture Board (IAB)\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nSection 1.\n\n The Internet Architecture Board (IAB) shall be constituted and shall\n operate as a technical advisory group of the Internet Society. Its\n responsibilities shall include:\n\n (1) Expert and experienced oversight of the architecture of the\n worldwide multiprotocol Internet.\n\n (2) The editorial management and publication of the Request for\n Comments (RFC) document series, which constitutes the\n archival publication series for Internet Standards and\n related contributions by the Internet research and\n engineering community.\n\n (3) The development, review, and app 1358 management policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 4844","type":"specification","body":"IETF","designation":"RFC 4844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4844.txt","https://www.rfc-editor.org/rfc/rfc4844.pdf"],"folder":"IETF/RFC-4844","files":{"txt":{"path":"standards/IETF/RFC-4844/RFC-4844.txt","sha256":"fcecfd19d4d2155de7dab4fe86ba80f4a6dc46b06c9ac671443cd81027a118c0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the framework for an RFC Series and an RFC\n Editor function that incorporate the principles of organized\n community involvement and accountability that has become necessary as\n the Internet technical community has grown, thereby enabling the RFC\n Series to continue to fulfill its mandate.\n\nDaigle & IAB Informational [Page 1]\n\f\nRFC 4844 The RFC Series and RFC Editor July 2007","scope_keywords":["4844","archiving","management","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4845","folder":"IETF/RFC-4845","source":"IETF/RFC-4845/RFC-4845.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5620","folder":"IETF/RFC-5620","source":"IETF/RFC-5620/RFC-5620.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 4844 This document describes the framework for an RFC Series and an RFC\n Editor function that incorporate the principles of organized\n community involvement and accountability that has become necessary as\n the Internet technical community has grown, thereby enabling the RFC\n Series to continue to fulfill its mandate.\n\nDaigle & IAB Informational [Page 1]\n\f\nRFC 4844 The RFC Series and RFC Editor July 2007 4844 archiving management policy trust nested-reference unchanged"},{"id":"IETF RFC 1363","type":"specification","body":"IETF","designation":"RFC 1363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1363.txt","https://www.rfc-editor.org/rfc/rfc1363.pdf"],"folder":"IETF/RFC-1363","files":{"txt":{"path":"standards/IETF/RFC-1363/RFC-1363.txt","sha256":"b8275d6861dd3a4b82ca43cef1047e763b45fee19282288aa7255104067eb3f9"}},"tags":["nested-reference","unchanged"],"summary":"A flow specification (or \"flow spec\") is a data structure used by\n internetwork hosts to request special services of the internetwork,\n often guarantees about how the internetwork will handle some of the\n hosts' traffic. In the future, hosts are expected to have to request\n such services on behalf of distributed applications such as\n multimedia conferencing.\n\n The flow specification defined in this memo is intended for\n information and possible experimentation (i.e., experimental use by\n consenting routers and applications only). This RFC is a product of\n the Internet Research Task Force (IRTF).","scope_keywords":["1363"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1633","folder":"IETF/RFC-1633","source":"IETF/RFC-1633/RFC-1633.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null}],"search_text":"IETF RFC 1363 A flow specification (or \"flow spec\") is a data structure used by\n internetwork hosts to request special services of the internetwork,\n often guarantees about how the internetwork will handle some of the\n hosts' traffic. In the future, hosts are expected to have to request\n such services on behalf of distributed applications such as\n multimedia conferencing.\n\n The flow specification defined in this memo is intended for\n information and possible experimentation (i.e., experimental use by\n consenting routers and applications only). This RFC is a product of\n the Internet Research Task Force (IRTF). 1363 nested-reference unchanged"},{"id":"IETF RFC 1367","type":"specification","body":"IETF","designation":"RFC 1367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1367.txt","https://www.rfc-editor.org/rfc/rfc1367.pdf"],"folder":"IETF/RFC-1367","files":{"txt":{"path":"standards/IETF/RFC-1367/RFC-1367.txt","sha256":"cfa3f47b1d1df8588d3a3f2f547c523a1b246c40beb2ed8c8d077e9d61e1b346"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Topolcic\nRequest for Comments: 1367 CNRI\n October 1992\n\n Schedule for IP Address Space Management Guidelines\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This memo suggests a schedule for the implementation of the IP\n network number allocation plan described in RFC 1366. This schedule\n is meant to support the implementation and deployment of an address\n aggregation mechanism for the Internet by proposing an achievable\n target for which we can all aim. The timely deployment of that\n aggregation mechanism and the IP addressing plan will help the the\n size of the Internet router forwarding tables and management of the\n IP address space. By doing so, it will help the current Internet\n addressing and routing technology operate during","scope_keywords":["1367","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1467","folder":"IETF/RFC-1467","source":"IETF/RFC-1467/RFC-1467.txt","version":null},{"body":"IETF","designation":"RFC 1481","folder":"IETF/RFC-1481","source":"IETF/RFC-1481/RFC-1481.txt","version":null},{"body":"IETF","designation":"RFC 1482","folder":"IETF/RFC-1482","source":"IETF/RFC-1482/RFC-1482.txt","version":null}],"search_text":"IETF RFC 1367 Network Working Group C. Topolcic\nRequest for Comments: 1367 CNRI\n October 1992\n\n Schedule for IP Address Space Management Guidelines\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This memo suggests a schedule for the implementation of the IP\n network number allocation plan described in RFC 1366. This schedule\n is meant to support the implementation and deployment of an address\n aggregation mechanism for the Internet by proposing an achievable\n target for which we can all aim. The timely deployment of that\n aggregation mechanism and the IP addressing plan will help the the\n size of the Internet router forwarding tables and management of the\n IP address space. By doing so, it will help the current Internet\n addressing and routing technology operate during 1367 management nested-reference unchanged"},{"id":"IETF RFC 139","type":"specification","body":"IETF","designation":"RFC 139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc139.txt","https://www.rfc-editor.org/rfc/rfc139.pdf"],"folder":"IETF/RFC-139","files":{"txt":{"path":"standards/IETF/RFC-139/RFC-139.txt","sha256":"9baf784906663285d6744e70e9cd7ac2b6205d426e8f357995e9e869f16aa238"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. O'Sullivan\nRequest for Comments: 139 Raytheon\nNIC: 6717 7 May 1971\n\n Discussion of TELNET Protocol\n\n The attached discussion is an extension of RFC 137, NIC #6717, and is\n presented to provide useful background to designers and implementers\n to help them interpret the proposed Protocol and evaluate it in\n preparation for further discussion at the Atlantic City meetings.\n\n While the views in the discussion represent those of various TELNET\n committee members, they should not be interpreted as being the agreed\n view of committee. They are the author's understanding of some of\n the arguments and background to the PROTOCOL proposed in the TELNET\n PROTOCOL recommendations.\n\n * See Footnotes to attached discussion for changes to RFC 137.\n\nDiscussion of TELNET PROTOCOL\n\n The use of a standard, network-wide, intermediate representation of\n terminal code between sites eli","scope_keywords":["139","key","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0139","folder":"IETF/RFC-0139","source":"IETF/RFC-0139/RFC-0139.txt","version":null},{"body":"IETF","designation":"RFC 0318","folder":"IETF/RFC-0318","source":"IETF/RFC-0318/RFC-0318.txt","version":null},{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null},{"body":"IETF","designation":"RFC 318","folder":"IETF/RFC-318","source":"IETF/RFC-318/RFC-318.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null}],"search_text":"IETF RFC 139 Network Working Group T. O'Sullivan\nRequest for Comments: 139 Raytheon\nNIC: 6717 7 May 1971\n\n Discussion of TELNET Protocol\n\n The attached discussion is an extension of RFC 137, NIC #6717, and is\n presented to provide useful background to designers and implementers\n to help them interpret the proposed Protocol and evaluate it in\n preparation for further discussion at the Atlantic City meetings.\n\n While the views in the discussion represent those of various TELNET\n committee members, they should not be interpreted as being the agreed\n view of committee. They are the author's understanding of some of\n the arguments and background to the PROTOCOL proposed in the TELNET\n PROTOCOL recommendations.\n\n * See Footnotes to attached discussion for changes to RFC 137.\n\nDiscussion of TELNET PROTOCOL\n\n The use of a standard, network-wide, intermediate representation of\n terminal code between sites eli 139 key presentation subject nested-reference unchanged"},{"id":"IETF RFC 2217","type":"specification","body":"IETF","designation":"RFC 2217","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2217.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2217.txt","https://www.rfc-editor.org/rfc/rfc2217.pdf"],"folder":"IETF/RFC-2217","files":{"txt":{"path":"standards/IETF/RFC-2217/RFC-2217.txt","sha256":"25881bf0f2fbe941ccd0ebd52d5fa5886565b04ffacab7023d0cc5e460c4ab60"}},"tags":["nested-reference","unchanged"],"summary":"because it relies on sending XON/XOFF style characters which\n maybe transmitted or received as a normal course of the\n client / remote service session.","scope_keywords":["2217","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2217 because it relies on sending XON/XOFF style characters which\n maybe transmitted or received as a normal course of the\n client / remote service session. 2217 signature nested-reference unchanged"},{"id":"IETF RFC 1378","type":"specification","body":"IETF","designation":"RFC 1378","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1378.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1378.txt","https://www.rfc-editor.org/rfc/rfc1378.pdf"],"folder":"IETF/RFC-1378","files":{"txt":{"path":"standards/IETF/RFC-1378/RFC-1378.txt","sha256":"11cd0ddb9193da0061fcfb1a7f2c4dfd7b8a83d836bee221171672344ffac037"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring the\n AppleTalk Protocol [3] over PPP.\n\n This memo is a joint effort of the AppleTalk-IP Working Group and the\n Point-to-Point Protocol Working Group of the Internet Engineering\n Task Force (IETF). Comments on this memo should be submitted to the\n ietf-ppp@ucdavis.edu mailing list.","scope_keywords":["1378","authentication","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1378 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the NCP for establishing and configuring the\n AppleTalk Protocol [3] over PPP.\n\n This memo is a joint effort of the AppleTalk-IP Working Group and the\n Point-to-Point Protocol Working Group of the Internet Engineering\n Task Force (IETF). Comments on this memo should be submitted to the\n ietf-ppp@ucdavis.edu mailing list. 1378 authentication delivery nested-reference unchanged"},{"id":"IETF RFC 1379","type":"specification","body":"IETF","designation":"RFC 1379","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1379.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1379.txt","https://www.rfc-editor.org/rfc/rfc1379.pdf"],"folder":"IETF/RFC-1379","files":{"txt":{"path":"standards/IETF/RFC-1379/RFC-1379.txt","sha256":"474e14633a237a78eca96aa31b4ab625b633843b0966255f21455c6f444962d4"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses extension of TCP to provide transaction-oriented\n service, without altering its virtual-circuit operation. This\n extension would fill the large gap between connection-oriented TCP\n and datagram-based UDP, allowing TCP to efficiently perform many\n applications for which UDP is currently used. A separate memo\n contains a detailed functional specification for this proposed\n extension.\n\n This work was supported in part by the National Science Foundation\n under Grant Number NCR-8922231.","scope_keywords":["1379","delivery","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1379 This memo discusses extension of TCP to provide transaction-oriented\n service, without altering its virtual-circuit operation. This\n extension would fill the large gap between connection-oriented TCP\n and datagram-based UDP, allowing TCP to efficiently perform many\n applications for which UDP is currently used. A separate memo\n contains a detailed functional specification for this proposed\n extension.\n\n This work was supported in part by the National Science Foundation\n under Grant Number NCR-8922231. 1379 delivery timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 1719","type":"specification","body":"IETF","designation":"RFC 1719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1719.txt","https://www.rfc-editor.org/rfc/rfc1719.pdf"],"folder":"IETF/RFC-1719","files":{"txt":{"path":"standards/IETF/RFC-1719/RFC-1719.txt","sha256":"d35baae611fe0911a310c1600ea082496f0e2cdaf1e1fb187d152212c22ddb76"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP.","scope_keywords":["1719","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1719 This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP. 1719 key policies nested-reference unchanged"},{"id":"IETF RFC 1955","type":"specification","body":"IETF","designation":"RFC 1955","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1955.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1955.txt","https://www.rfc-editor.org/rfc/rfc1955.pdf"],"folder":"IETF/RFC-1955","files":{"txt":{"path":"standards/IETF/RFC-1955/RFC-1955.txt","sha256":"c402925f977b02c9ac34a99a43c53c90f1e6ec17e3683c43c26320a301f0a656"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n This memo describes a proposal made to to the Routing and Addressing\n group [ROAD] January 1992 by Robert Hinden. It was originally sent\n as an email message. It proposes a medium term solution to the\n Internet's routing and addressing problems.","scope_keywords":["1955","algorithm","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null}],"search_text":"IETF RFC 1955 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n This memo describes a proposal made to to the Routing and Addressing\n group [ROAD] January 1992 by Robert Hinden. It was originally sent\n as an email message. It proposes a medium term solution to the\n Internet's routing and addressing problems. 1955 algorithm attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 1919","type":"specification","body":"IETF","designation":"RFC 1919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1919.txt","https://www.rfc-editor.org/rfc/rfc1919.pdf"],"folder":"IETF/RFC-1919","files":{"txt":{"path":"standards/IETF/RFC-1919/RFC-1919.txt","sha256":"7f12470e3448b24a036caf9df1bdbad42cfa84ea272304f9671b9d916d8ed24a"}},"tags":["nested-reference","unchanged"],"summary":"Many modern IP security systems (also called \"firewalls\" in the\n trade) make use of proxy technology to achieve access control. This\n document explains \"classical\" and \"transparent\" proxy techniques and\n attempts to provide rules to help determine when each proxy system\n may be used without causing problems.","scope_keywords":["1919","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 1919 Many modern IP security systems (also called \"firewalls\" in the\n trade) make use of proxy technology to achieve access control. This\n document explains \"classical\" and \"transparent\" proxy techniques and\n attempts to provide rules to help determine when each proxy system\n may be used without causing problems. 1919 subject nested-reference unchanged"},{"id":"IETF RFC 318","type":"specification","body":"IETF","designation":"RFC 318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc318.txt","https://www.rfc-editor.org/rfc/rfc318.pdf"],"folder":"IETF/RFC-318","files":{"txt":{"path":"standards/IETF/RFC-318/RFC-318.txt","sha256":"fd9d4e32ee2ab6d63b3c7ba0593662696d8cdf8fc817b799161a922972f362d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 318 UCLA-NMC\nNIC: 9348 April 3, 1972\nReferences: RFC 139, 158, and NIC 7104\n\n Telnet Protocol\n\n At the October 1971 Network Working Group Meeting, I promised to\n promptly produce a document which clearly and succinctly specified\n and explained the Official Telnet Protocol. This document fails to\n meet any part of that promise. This document was not produced\n promptly. This document is neither clear nor succinct. There is NO\n Official Telnet Protocol.\n\n The following pages present my understanding of the ad hoc Telnet\n protocol. There are some who have serious questions about this\n protocol. The proposed changes to the protocol are given in Section\n IV.\n\n Any comments should be promptly directed to me via the Network\n Information Center (Ident = JBP) or by phone (213) 825-2368 or by\n mail.\n\n Jon Postel\n SPADE Group\n 3804 Boelter Hall\n","scope_keywords":["318","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0318","folder":"IETF/RFC-0318","source":"IETF/RFC-0318/RFC-0318.txt","version":null},{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 2235","folder":"IETF/RFC-2235","source":"IETF/RFC-2235/RFC-2235.txt","version":null},{"body":"IETF","designation":"RFC 435","folder":"IETF/RFC-435","source":"IETF/RFC-435/RFC-435.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null}],"search_text":"IETF RFC 318 Network Working Group Jon Postel\nRequest for Comments: 318 UCLA-NMC\nNIC: 9348 April 3, 1972\nReferences: RFC 139, 158, and NIC 7104\n\n Telnet Protocol\n\n At the October 1971 Network Working Group Meeting, I promised to\n promptly produce a document which clearly and succinctly specified\n and explained the Official Telnet Protocol. This document fails to\n meet any part of that promise. This document was not produced\n promptly. This document is neither clear nor succinct. There is NO\n Official Telnet Protocol.\n\n The following pages present my understanding of the ad hoc Telnet\n protocol. There are some who have serious questions about this\n protocol. The proposed changes to the protocol are given in Section\n IV.\n\n Any comments should be promptly directed to me via the Network\n Information Center (Ident = JBP) or by phone (213) 825-2368 or by\n mail.\n\n Jon Postel\n SPADE Group\n 3804 Boelter Hall\n 318 key keys presentation nested-reference unchanged"},{"id":"IETF RFC 3945","type":"specification","body":"IETF","designation":"RFC 3945","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3945.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3945.txt","https://www.rfc-editor.org/rfc/rfc3945.pdf"],"folder":"IETF/RFC-3945","files":{"txt":{"path":"standards/IETF/RFC-3945/RFC-3945.txt","sha256":"cb36f81c872815e930f270860d7f2bbefa180aedb2b472368740b5c46618bbaf"}},"tags":["nested-reference","unchanged"],"summary":"Future data and transmission networks will consist of elements such\n as routers, switches, Dense Wavelength Division Multiplexing (DWDM)\n systems, Add-Drop Multiplexors (ADMs), photonic cross-connects\n (PXCs), optical cross-connects (OXCs), etc. that will use Generalized\n Multi-Protocol Label Switching (GMPLS) to dynamically provision\n resources and to provide network survivability using protection and\n restoration techniques.\n\n This document describes the architecture of GMPLS. GMPLS extends\n MPLS to encompass time-division (e.g., SONET/SDH, PDH, G.709),\n wavelength (lambdas), and spatial switching (e.g., incoming port or\n fiber to outgoing port or fiber). The focus of GMPLS is on the\n control plane of these various layers since each of them can use\n physically diverse data or forwarding planes. The intention is to\n cover both the signaling and the routing part of that control plane.\n\nM","scope_keywords":["3945","key","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4054","folder":"IETF/RFC-4054","source":"IETF/RFC-4054/RFC-4054.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4427","folder":"IETF/RFC-4427","source":"IETF/RFC-4427/RFC-4427.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 3945 Future data and transmission networks will consist of elements such\n as routers, switches, Dense Wavelength Division Multiplexing (DWDM)\n systems, Add-Drop Multiplexors (ADMs), photonic cross-connects\n (PXCs), optical cross-connects (OXCs), etc. that will use Generalized\n Multi-Protocol Label Switching (GMPLS) to dynamically provision\n resources and to provide network survivability using protection and\n restoration techniques.\n\n This document describes the architecture of GMPLS. GMPLS extends\n MPLS to encompass time-division (e.g., SONET/SDH, PDH, G.709),\n wavelength (lambdas), and spatial switching (e.g., incoming port or\n fiber to outgoing port or fiber). The focus of GMPLS is on the\n control plane of these various layers since each of them can use\n physically diverse data or forwarding planes. The intention is to\n cover both the signaling and the routing part of that control plane.\n\nM 3945 key management pid nested-reference unchanged"},{"id":"IETF RFC 5704","type":"specification","body":"IETF","designation":"RFC 5704","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5704.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5704.txt","https://www.rfc-editor.org/rfc/rfc5704.pdf"],"folder":"IETF/RFC-5704","files":{"txt":{"path":"standards/IETF/RFC-5704/RFC-5704.txt","sha256":"fde121ec1b2955e6d588e737c78b0b97e4aa2a6892ae5dd2474648d1201c2810"}},"tags":["nested-reference","unchanged"],"summary":"This document identifies problems that may result from the absence of\n formal coordination and joint development on protocols of mutual\n interest between standards development organizations (SDOs). Some of\n these problems may cause significant harm to the Internet. The\n document suggests that a robust procedure is required prevent this\n from occurring in the future. The IAB has selected a number of case\n studies, such as Transport MPLS (T-MPLS), as recent examples to\n describe the hazard to the Internet architecture that results from\n uncoordinated adaptation of a protocol.\n\n This experience has resulted in a considerable improvement in the\n relationship between the IETF and the ITU-T. In particular, this was\n achieved via the establishment of the \"Joint working team on\n MPLS-TP\". In addition, the leadership of the two organizations\n agreed to improve inter-organizational working practic","scope_keywords":["5704","http","identification","license","pid","profile","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5704 This document identifies problems that may result from the absence of\n formal coordination and joint development on protocols of mutual\n interest between standards development organizations (SDOs). Some of\n these problems may cause significant harm to the Internet. The\n document suggests that a robust procedure is required prevent this\n from occurring in the future. The IAB has selected a number of case\n studies, such as Transport MPLS (T-MPLS), as recent examples to\n describe the hazard to the Internet architecture that results from\n uncoordinated adaptation of a protocol.\n\n This experience has resulted in a considerable improvement in the\n relationship between the IETF and the ITU-T. In particular, this was\n achieved via the establishment of the \"Joint working team on\n MPLS-TP\". In addition, the leadership of the two organizations\n agreed to improve inter-organizational working practic 5704 http identification license pid profile risk subject trust nested-reference unchanged"},{"id":"IETF RFC 3933","type":"specification","body":"IETF","designation":"RFC 3933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3933.txt","https://www.rfc-editor.org/rfc/rfc3933.pdf"],"folder":"IETF/RFC-3933","files":{"txt":{"path":"standards/IETF/RFC-3933/RFC-3933.txt","sha256":"122cec199516cd92641812d68d1937ff544fdea6d8ff86085ca4ba94de52266b"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has designed process changes over the last ten years in one\n of two ways: announcement by the IESG, sometimes based on informal\n agreements with limited community involvement and awareness, and\n formal use of the same mechanism used for protocol specification.\n The first mechanism has often proven to be too lightweight, the\n second too heavyweight.\n\n This document specifies a middle-ground approach to the system of\n making changes to IETF process, one that relies heavily on a \"propose\n and carry out an experiment, evaluate the experiment, and then\n establish permanent procedures based on operational experience\" model\n rather than those previously attempted.","scope_keywords":["3933"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 5111","folder":"IETF/RFC-5111","source":"IETF/RFC-5111/RFC-5111.txt","version":null},{"body":"IETF","designation":"RFC 6982","folder":"IETF/RFC-6982","source":"IETF/RFC-6982/RFC-6982.txt","version":null}],"search_text":"IETF RFC 3933 The IETF has designed process changes over the last ten years in one\n of two ways: announcement by the IESG, sometimes based on informal\n agreements with limited community involvement and awareness, and\n formal use of the same mechanism used for protocol specification.\n The first mechanism has often proven to be too lightweight, the\n second too heavyweight.\n\n This document specifies a middle-ground approach to the system of\n making changes to IETF process, one that relies heavily on a \"propose\n and carry out an experiment, evaluate the experiment, and then\n establish permanent procedures based on operational experience\" model\n rather than those previously attempted. 3933 nested-reference unchanged"},{"id":"IETF RFC 1400","type":"specification","body":"IETF","designation":"RFC 1400","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1400.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1400.txt","https://www.rfc-editor.org/rfc/rfc1400.pdf"],"folder":"IETF/RFC-1400","files":{"txt":{"path":"standards/IETF/RFC-1400/RFC-1400.txt","sha256":"630f5b56915d488ff1c11a1cf0dfd824b32c4fd61f8c2b9c5079dee498f1a147"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Williamson\nRequest for Comments: 1400 Network Solutions, Inc.\n March 1993\n\n Transition and Modernization\n of the Internet Registration Service\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nDiscussion\n\n As a result of the NREN NIS award by National Science Foundation,\n non-DDN registration services will soon be transferred from the DDN\n NIC to the new Internet Registration Service, which is a part of an\n entity referred to as the InterNIC. References in this document to\n the InterNIC apply to the Registration Services portion only.\n\n Internet registration services are gradually transitioning to the\n InterNIC. We expect that the full transition will be accomplished by\n April 1, 1993. During this transitional period, EMail, Fax, and U.S.\n mail rec","scope_keywords":["1400","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 1400 Network Working Group S. Williamson\nRequest for Comments: 1400 Network Solutions, Inc.\n March 1993\n\n Transition and Modernization\n of the Internet Registration Service\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nDiscussion\n\n As a result of the NREN NIS award by National Science Foundation,\n non-DDN registration services will soon be transferred from the DDN\n NIC to the new Internet Registration Service, which is a part of an\n entity referred to as the InterNIC. References in this document to\n the InterNIC apply to the Registration Services portion only.\n\n Internet registration services are gradually transitioning to the\n InterNIC. We expect that the full transition will be accomplished by\n April 1, 1993. During this transitional period, EMail, Fax, and U.S.\n mail rec 1400 verifiable nested-reference unchanged"},{"id":"IETF RFC 2162","type":"specification","body":"IETF","designation":"RFC 2162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2162.txt","https://www.rfc-editor.org/rfc/rfc2162.pdf"],"folder":"IETF/RFC-2162","files":{"txt":{"path":"standards/IETF/RFC-2162/RFC-2162.txt","sha256":"6c8e3cfb37f9fdfc7f4ed74660bf5dbcd0dd607b211dd72102a0e399c4e791e8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of mappings which will enable inter\n working between systems operating the ISO/IEC 10021 - CCITT (now ITU)\n X.400 Recommendations on Message Handling Systems, and systems\n running the Mail-11 (also known as DECnet mail or VMSmail) protocol.\n The specifications are valid both within DECnet Phase IV and\n DECnet/OSI addressing and routing scheme.\n\n The complete scenario of X.400 / MIME / Mail-11 is also considered,\n in order to cover the possible complex cases arising in multiple\n gateway translations.\n\n This document covers mainly the X.400 O/R address to/from Mail-11\n address mapping and the RFC822 to/from Mail-11 ones; other mappings\n are based on MIXER specifications. Bodypart mappings are not\n specified in this document: MIXER and MIME-MHS specifications can be\n applied to map bodyparts between X.400, MIME and Mail-11, too. In\n fact MIME encoding can be us","scope_keywords":["2162","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2162 This document describes a set of mappings which will enable inter\n working between systems operating the ISO/IEC 10021 - CCITT (now ITU)\n X.400 Recommendations on Message Handling Systems, and systems\n running the Mail-11 (also known as DECnet mail or VMSmail) protocol.\n The specifications are valid both within DECnet Phase IV and\n DECnet/OSI addressing and routing scheme.\n\n The complete scenario of X.400 / MIME / Mail-11 is also considered,\n in order to cover the possible complex cases arising in multiple\n gateway translations.\n\n This document covers mainly the X.400 O/R address to/from Mail-11\n address mapping and the RFC822 to/from Mail-11 ones; other mappings\n are based on MIXER specifications. Bodypart mappings are not\n specified in this document: MIXER and MIME-MHS specifications can be\n applied to map bodyparts between X.400, MIME and Mail-11, too. In\n fact MIME encoding can be us 2162 presentation nested-reference unchanged"},{"id":"IETF RFC 1571","type":"specification","body":"IETF","designation":"RFC 1571","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1571.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1571.txt","https://www.rfc-editor.org/rfc/rfc1571.pdf"],"folder":"IETF/RFC-1571","files":{"txt":{"path":"standards/IETF/RFC-1571/RFC-1571.txt","sha256":"ce67ae2009dd9c429427cdaccd4d472dd828e078a550150bb5d641cbacec5b3d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman\nRequest for Comments: 1571 Cray Research, Inc.\nUpdates: 1408 January 1994\nCategory: Informational\n\n Telnet Environment Option Interoperability Issues\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Overview\n\n RFC 1408 [1], the specification for the Telnet Environment Option,\n specifies definitions for VAR and VALUE that are reversed from the\n BSD implementation of the Telnet Environment option. Since the BSD\n implementation was the reference implementation that the RFC was\n supposed to document, and is the base for many existing\n implementations, there exists an interoperability problem between\n implementations with conflicting definitions for VAR and VALUE.\n\n This document describes a method for allowing implementors","scope_keywords":["1571"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1572","folder":"IETF/RFC-1572","source":"IETF/RFC-1572/RFC-1572.txt","version":null}],"search_text":"IETF RFC 1571 Network Working Group D. Borman\nRequest for Comments: 1571 Cray Research, Inc.\nUpdates: 1408 January 1994\nCategory: Informational\n\n Telnet Environment Option Interoperability Issues\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Overview\n\n RFC 1408 [1], the specification for the Telnet Environment Option,\n specifies definitions for VAR and VALUE that are reversed from the\n BSD implementation of the Telnet Environment option. Since the BSD\n implementation was the reference implementation that the RFC was\n supposed to document, and is the base for many existing\n implementations, there exists an interoperability problem between\n implementations with conflicting definitions for VAR and VALUE.\n\n This document describes a method for allowing implementors 1571 nested-reference unchanged"},{"id":"IETF RFC 141","type":"specification","body":"IETF","designation":"RFC 141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc141.txt","https://www.rfc-editor.org/rfc/rfc141.pdf"],"folder":"IETF/RFC-141","files":{"txt":{"path":"standards/IETF/RFC-141/RFC-141.txt","sha256":"f2ccb290cbb21e65466c8622ed70dce13e06bcaacd8b303ea6de2a30cdf155d0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. F. Harslem\nRequest for Comments: 141 J. F. Haefner\nNIC 6726 Rand\n 29 April 1971\n\n COMMENTS ON RFC 141 (A FILE TRANSFER PROTOCOL)\n\n 1. A file transfer protocol is needed. Bushan's proposal would\n satisfy a particular current need that we have, as well as short-term\n envisioned needs.\n\n 2. Bushan's protocol would apear to be straight-forward in\n implementation, and extensible as claimed.\n\n 3. We would like to see implementations of such protocol be\n accomplished such that the file transfer program has general and\n complete access to the local file storage. That is, it should be\n able to access a file that it did not create. For example, if a\n program or user creates a file at site X (completely independent of\n the file transfer program), it would then be desirable to be able to\n retrieve the file via the file transfer program. This is not a\n requirement of RFC #114","scope_keywords":["141"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 141 Network Working Group E. F. Harslem\nRequest for Comments: 141 J. F. Haefner\nNIC 6726 Rand\n 29 April 1971\n\n COMMENTS ON RFC 141 (A FILE TRANSFER PROTOCOL)\n\n 1. A file transfer protocol is needed. Bushan's proposal would\n satisfy a particular current need that we have, as well as short-term\n envisioned needs.\n\n 2. Bushan's protocol would apear to be straight-forward in\n implementation, and extensible as claimed.\n\n 3. We would like to see implementations of such protocol be\n accomplished such that the file transfer program has general and\n complete access to the local file storage. That is, it should be\n able to access a file that it did not create. For example, if a\n program or user creates a file at site X (completely independent of\n the file transfer program), it would then be desirable to be able to\n retrieve the file via the file transfer program. This is not a\n requirement of RFC #114 141 nested-reference unchanged"},{"id":"IETF RFC 1411","type":"specification","body":"IETF","designation":"RFC 1411","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1411.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1411.txt","https://www.rfc-editor.org/rfc/rfc1411.pdf"],"folder":"IETF/RFC-1411","files":{"txt":{"path":"standards/IETF/RFC-1411/RFC-1411.txt","sha256":"6318529f338c6b3ad0df24f946b03570dcc413c9ad7b0c067001ef7349fcd42a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Borman, Editor\nRequest for Comments: 1411 Cray Research, Inc.\n January 1993\n\n Telnet Authentication: Kerberos Version 4\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n Authentication Types\n\n KERBEROSV4 1\n\n Suboption Commands\n\n AUTH 0\n REJECT 1\n ACCEPT 2\n CHALLENGE 3\n RESPONSE 4\n\n2. Command Meanings\n\n IAC SB AUTHENTICATION IS AUTH IAC SE\n\n This is used to pass the Kerberos ticket to the remote side of the\n connection. The first octet of the \n value is KERBEROSV4, to indicate the usage of Kerberos version 4.\n\n IAC SB AUTHENTICATION REPLY ACCEPT IAC SE\n\n Thi","scope_keywords":["1411","authentication","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2217","folder":"IETF/RFC-2217","source":"IETF/RFC-2217/RFC-2217.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1411 Network Working Group D. Borman, Editor\nRequest for Comments: 1411 Cray Research, Inc.\n January 1993\n\n Telnet Authentication: Kerberos Version 4\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n Authentication Types\n\n KERBEROSV4 1\n\n Suboption Commands\n\n AUTH 0\n REJECT 1\n ACCEPT 2\n CHALLENGE 3\n RESPONSE 4\n\n2. Command Meanings\n\n IAC SB AUTHENTICATION IS AUTH IAC SE\n\n This is used to pass the Kerberos ticket to the remote side of the\n connection. The first octet of the \n value is KERBEROSV4, to indicate the usage of Kerberos version 4.\n\n IAC SB AUTHENTICATION REPLY ACCEPT IAC SE\n\n Thi 1411 authentication encryption key nested-reference unchanged"},{"id":"IETF RFC 1412","type":"specification","body":"IETF","designation":"RFC 1412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1412.txt","https://www.rfc-editor.org/rfc/rfc1412.pdf"],"folder":"IETF/RFC-1412","files":{"txt":{"path":"standards/IETF/RFC-1412/RFC-1412.txt","sha256":"0c4b0deef91902798bd024215f32c0523b7a0e07aab03bf019f5b80f50376f62"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Alagappan\nRequest for Comments: 1412 Digital Equipment Corporation\n January 1993\n\n Telnet Authentication: SPX\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n Authentication Types\n\n SPX 3\n\n Suboption Commands\n\n AUTH 0\n REJECT 1\n ACCEPT 2\n\n2. Command Meanings\n\n IAC SB AUTHENTICATION IS AUTH\n IAC SE\n\n This is used to pass the SPX authentication token to the remote\n side of the connection. (A document which describes the\n authentication token syntax is forthcoming.) The first octet of\n the value is SPX. The second octet is\n a modifier to the SPX authenticatio","scope_keywords":["1412","authentication","authorization","encryption","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2217","folder":"IETF/RFC-2217","source":"IETF/RFC-2217/RFC-2217.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1412 Network Working Group K. Alagappan\nRequest for Comments: 1412 Digital Equipment Corporation\n January 1993\n\n Telnet Authentication: SPX\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. Discussion and suggestions for improvement are requested.\n Please refer to the current edition of the \"IAB Official Protocol\n Standards\" for the standardization state and status of this protocol.\n Distribution of this memo is unlimited.\n\n1. Command Names and Codes\n\n Authentication Types\n\n SPX 3\n\n Suboption Commands\n\n AUTH 0\n REJECT 1\n ACCEPT 2\n\n2. Command Meanings\n\n IAC SB AUTHENTICATION IS AUTH\n IAC SE\n\n This is used to pass the SPX authentication token to the remote\n side of the connection. (A document which describes the\n authentication token syntax is forthcoming.) The first octet of\n the value is SPX. The second octet is\n a modifier to the SPX authenticatio 1412 authentication authorization encryption key trust nested-reference unchanged"},{"id":"IETF RFC 1459","type":"specification","body":"IETF","designation":"RFC 1459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1459.txt","https://www.rfc-editor.org/rfc/rfc1459.pdf"],"folder":"IETF/RFC-1459","files":{"txt":{"path":"standards/IETF/RFC-1459/RFC-1459.txt","sha256":"d1fdc86169252b234b17c2f501c0ba7f512ba697ddf8a13b3da7ee4491a76799"}},"tags":["nested-reference","unchanged"],"summary":"The IRC protocol was developed over the last 4 years since it was\n first implemented as a means for users on a BBS to chat amongst\n themselves. Now it supports a world-wide network of servers and\n clients, and is stringing to cope with growth. Over the past 2 years,\n the average number of users connected to the main IRC network has\n grown by a factor of 10.\n\n The IRC protocol is a text-based protocol, with the simplest client\n being any socket program capable of connecting to the server.","scope_keywords":["1459","authentication","delivery","hash"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2810","folder":"IETF/RFC-2810","source":"IETF/RFC-2810/RFC-2810.txt","version":null},{"body":"IETF","designation":"RFC 2811","folder":"IETF/RFC-2811","source":"IETF/RFC-2811/RFC-2811.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null}],"search_text":"IETF RFC 1459 The IRC protocol was developed over the last 4 years since it was\n first implemented as a means for users on a BBS to chat amongst\n themselves. Now it supports a world-wide network of servers and\n clients, and is stringing to cope with growth. Over the past 2 years,\n the average number of users connected to the main IRC network has\n grown by a factor of 10.\n\n The IRC protocol is a text-based protocol, with the simplest client\n being any socket program capable of connecting to the server. 1459 authentication delivery hash nested-reference unchanged"},{"id":"IETF RFC 2813","type":"specification","body":"IETF","designation":"RFC 2813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2813.txt","https://www.rfc-editor.org/rfc/rfc2813.pdf"],"folder":"IETF/RFC-2813","files":{"txt":{"path":"standards/IETF/RFC-2813/RFC-2813.txt","sha256":"f67d31f2d4a23fda979ace02e3279c9b3d1ab33e279c8a41e1add7ab293991ba"}},"tags":["nested-reference","unchanged"],"summary":"While based on the client-server model, the IRC (Internet Relay Chat)\n protocol allows servers to connect to each other effectively forming\n a network.\n\n This document defines the protocol used by servers to talk to each\n other. It was originally a superset of the client protocol but has\n evolved differently.\n\n First formally documented in May 1993 as part of RFC 1459 [IRC], most\n of the changes brought since then can be found in this document as\n development was focused on making the protocol scale better. Better\n scalability has allowed existing world-wide networks to keep growing\n and reach sizes which defy the old specification.\n\nKalt Informational [Page 1]\n\f\nRFC 2813 Internet Relay Chat: Server Protocol April 2000","scope_keywords":["2813","algorithm","algorithms","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2810","folder":"IETF/RFC-2810","source":"IETF/RFC-2810/RFC-2810.txt","version":null},{"body":"IETF","designation":"RFC 2811","folder":"IETF/RFC-2811","source":"IETF/RFC-2811/RFC-2811.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null}],"search_text":"IETF RFC 2813 While based on the client-server model, the IRC (Internet Relay Chat)\n protocol allows servers to connect to each other effectively forming\n a network.\n\n This document defines the protocol used by servers to talk to each\n other. It was originally a superset of the client protocol but has\n evolved differently.\n\n First formally documented in May 1993 as part of RFC 1459 [IRC], most\n of the changes brought since then can be found in this document as\n development was focused on making the protocol scale better. Better\n scalability has allowed existing world-wide networks to keep growing\n and reach sizes which defy the old specification.\n\nKalt Informational [Page 1]\n\f\nRFC 2813 Internet Relay Chat: Server Protocol April 2000 2813 algorithm algorithms authentication management nested-reference unchanged"},{"id":"IETF RFC 3050","type":"specification","body":"IETF","designation":"RFC 3050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3050.txt","https://www.rfc-editor.org/rfc/rfc3050.pdf"],"folder":"IETF/RFC-3050","files":{"txt":{"path":"standards/IETF/RFC-3050/RFC-3050.txt","sha256":"e7d3f5012eb52f1f501c7cde7fd7210f2a65689bc10cae96fb3c6e16014b839a"}},"tags":["nested-reference","unchanged"],"summary":"In Internet telephony, there must be a means by which new services\n are created and deployed rapidly. In the World Wide Web, the Common\n Gateway Interface (CGI) has served as popular means towards\n programming web services. Due to the similarities between the\n Session Initiation Protocol (SIP) and the Hyper Text Transfer\n Protocol (HTTP), CGI is a good candidate for service creation in a\n SIP environment. This document defines a SIP CGI interface for\n providing SIP services on a SIP server.\n\nIESG Note\n\n The IESG notes that the mechanism specified here depends on the\n Common Gateway Interface. Should this interface change or be\n enhanced changes in this specification may also be necessary or\n appropriate. According to the W3C, the CGI is presently maintained\n by the NCSA Software Development Group. See\n\n http://www.w3c.org/cgi\n\n for additional information on the current state of the CGI i","scope_keywords":["3050","http","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null}],"search_text":"IETF RFC 3050 In Internet telephony, there must be a means by which new services\n are created and deployed rapidly. In the World Wide Web, the Common\n Gateway Interface (CGI) has served as popular means towards\n programming web services. Due to the similarities between the\n Session Initiation Protocol (SIP) and the Hyper Text Transfer\n Protocol (HTTP), CGI is a good candidate for service creation in a\n SIP environment. This document defines a SIP CGI interface for\n providing SIP services on a SIP server.\n\nIESG Note\n\n The IESG notes that the mechanism specified here depends on the\n Common Gateway Interface. Should this interface change or be\n enhanced changes in this specification may also be necessary or\n appropriate. According to the W3C, the CGI is presently maintained\n by the NCSA Software Development Group. See\n\n http://www.w3c.org/cgi\n\n for additional information on the current state of the CGI i 3050 http pid nested-reference unchanged"},{"id":"IETF RFC 3552","type":"specification","body":"IETF","designation":"RFC 3552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3552.txt","https://www.rfc-editor.org/rfc/rfc3552.pdf"],"folder":"IETF/RFC-3552","files":{"txt":{"path":"standards/IETF/RFC-3552/RFC-3552.txt","sha256":"ba07e18bdffd18893e8607398bef42dbdb5f1c5aa0c7dd6891d43ca8a0b19e4f"}},"tags":["nested-reference","unchanged"],"summary":"All RFCs are required to have a Security Considerations section.\n Historically, such sections have been relatively weak. This document\n provides guidelines to RFC authors on how to write a good Security\n Considerations section.","scope_keywords":["3552","authentication","authorization","certificate","certificates","key","keys","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3833","folder":"IETF/RFC-3833","source":"IETF/RFC-3833/RFC-3833.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6386","folder":"IETF/RFC-6386","source":"IETF/RFC-6386/RFC-6386.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 3552 All RFCs are required to have a Security Considerations section.\n Historically, such sections have been relatively weak. This document\n provides guidelines to RFC authors on how to write a good Security\n Considerations section. 3552 authentication authorization certificate certificates key keys path tls nested-reference unchanged"},{"id":"IETF RFC 2941","type":"specification","body":"IETF","designation":"RFC 2941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2941.txt","https://www.rfc-editor.org/rfc/rfc2941.pdf"],"folder":"IETF/RFC-2941","files":{"txt":{"path":"standards/IETF/RFC-2941/RFC-2941.txt","sha256":"aa3a2b5b21dea09a4684a8906c5c0166ec7a279730b4bfff403a32f8211c5bb9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Ts'o, Editor\nRequest for Comments: 2941 VA Linux Systems\nObsoletes: 1416 J. Altman\nCategory: Standards Track Columbia University\n September 2000\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes the authentication option to the telnet [1]\n protocol as a generic method for negotiating an authentication type\n and mode including whether encryption should be used and if\n credentials should be forwarded. While th","scope_keywords":["2941","authentication","authorization","credential","credentials","encryption","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2946","folder":"IETF/RFC-2946","source":"IETF/RFC-2946/RFC-2946.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2941 Network Working Group T. Ts'o, Editor\nRequest for Comments: 2941 VA Linux Systems\nObsoletes: 1416 J. Altman\nCategory: Standards Track Columbia University\n September 2000\n\n Telnet Authentication Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes the authentication option to the telnet [1]\n protocol as a generic method for negotiating an authentication type\n and mode including whether encryption should be used and if\n credentials should be forwarded. While th 2941 authentication authorization credential credentials encryption policy nested-reference unchanged"},{"id":"IETF RFC 1417","type":"specification","body":"IETF","designation":"RFC 1417","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1417.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1417.txt","https://www.rfc-editor.org/rfc/rfc1417.pdf"],"folder":"IETF/RFC-1417","files":{"txt":{"path":"standards/IETF/RFC-1417/RFC-1417.txt","sha256":"783eebee3bccd5bea0911b666ff51440d050e49d252d772d55b659e31dd3852e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group The North American Directory Forum\nRequest for Comments: 1417 February 1993\nObsoletes: 1295, 1255, 1218\n\n NADF Standing Documents:\n A Brief Overview\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ......................................... 1\n 1.1 Document Availability ............................... 3\n 1.1.1 Hardcopy .......................................... 3\n 1.1.2 Anonymous FTP ..................................... 4\n 1.1.3 Electronic Mail ................................... 4\n Security Considerations ................................. 4\n Author's Address ........................................ 4\n\n1. Introduction\n\n The North American Directory Forum (NADF) is a collection of service\n providers which plans to co","scope_keywords":["1417","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1422","folder":"IETF/RFC-1422","source":"IETF/RFC-1422/RFC-1422.txt","version":null},{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 1588","folder":"IETF/RFC-1588","source":"IETF/RFC-1588/RFC-1588.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null}],"search_text":"IETF RFC 1417 Network Working Group The North American Directory Forum\nRequest for Comments: 1417 February 1993\nObsoletes: 1295, 1255, 1218\n\n NADF Standing Documents:\n A Brief Overview\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nTable of Contents\n\n 1. Introduction ......................................... 1\n 1.1 Document Availability ............................... 3\n 1.1.1 Hardcopy .......................................... 3\n 1.1.2 Anonymous FTP ..................................... 4\n 1.1.3 Electronic Mail ................................... 4\n Security Considerations ................................. 4\n Author's Address ........................................ 4\n\n1. Introduction\n\n The North American Directory Forum (NADF) is a collection of service\n providers which plans to co 1417 management policy nested-reference unchanged"},{"id":"IETF RFC 1848","type":"specification","body":"IETF","designation":"RFC 1848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1848.txt","https://www.rfc-editor.org/rfc/rfc1848.pdf"],"folder":"IETF/RFC-1848","files":{"txt":{"path":"standards/IETF/RFC-1848/RFC-1848.txt","sha256":"c2e2a8dce72a8313767c46d76e123d60f86ab8d963f56882217b6815a6f6a9f4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines MIME Object Security Services (MOSS), a\n protocol that uses the multipart/signed and multipart/encrypted\n framework [7] to apply digital signature and encryption services to\n MIME objects. The services are offered through the use of end-to-end\n cryptography between an originator and a recipient at the application\n layer. Asymmetric (public key) cryptography is used in support of\n the digital signature service and encryption key management.\n Symmetric (secret key) cryptography is used in support of the\n encryption service. The procedures are intended to be compatible\n with a wide range of public key management approaches, including both\n ad hoc and certificate-based schemes. Mechanisms are provided to\n support many public key management approaches.","scope_keywords":["1848","authentication","certificate","encryption","issuer","key","keys","management","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1867","folder":"IETF/RFC-1867","source":"IETF/RFC-1867/RFC-1867.txt","version":null},{"body":"IETF","designation":"RFC 2015","folder":"IETF/RFC-2015","source":"IETF/RFC-2015/RFC-2015.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null}],"search_text":"IETF RFC 1848 This document defines MIME Object Security Services (MOSS), a\n protocol that uses the multipart/signed and multipart/encrypted\n framework [7] to apply digital signature and encryption services to\n MIME objects. The services are offered through the use of end-to-end\n cryptography between an originator and a recipient at the application\n layer. Asymmetric (public key) cryptography is used in support of\n the digital signature service and encryption key management.\n Symmetric (secret key) cryptography is used in support of the\n encryption service. The procedures are intended to be compatible\n with a wide range of public key management approaches, including both\n ad hoc and certificate-based schemes. Mechanisms are provided to\n support many public key management approaches. 1848 authentication certificate encryption issuer key keys management signature trust nested-reference unchanged"},{"id":"IETF RFC 1875","type":"specification","body":"IETF","designation":"RFC 1875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1875.txt","https://www.rfc-editor.org/rfc/rfc1875.pdf"],"folder":"IETF/RFC-1875","files":{"txt":{"path":"standards/IETF/RFC-1875/RFC-1875.txt","sha256":"b8c9aa89ac8a81e5f6c9bc77b49d46e9f84e6744a993b06b12f22797eadfa225"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Berge\nRequest for Comments: 1875 Norwegian Computing Center\nCategory: Informational December 1995\n\n UNINETT PCA Policy Statements\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.......................................2\n 2. PCA Identity.......................................2\n 3. UNINETT - a brief overview.........................2\n 4. PCA Scope..........................................2\n 4.1 The certification tree.............................3\n 4.2 Use of Registration Authorities (RAs)..............3\n 5. PCA Security & Privacy.............................3\n 5.1 Security requirements imposed on the PCA...........3\n 5.2 Security requirements imposed on CAs...............4\n 5.3 Security requireme","scope_keywords":["1875","authentication","certificate","certificates","crl","http","identification","key","management","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null}],"search_text":"IETF RFC 1875 Network Working Group N. Berge\nRequest for Comments: 1875 Norwegian Computing Center\nCategory: Informational December 1995\n\n UNINETT PCA Policy Statements\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction.......................................2\n 2. PCA Identity.......................................2\n 3. UNINETT - a brief overview.........................2\n 4. PCA Scope..........................................2\n 4.1 The certification tree.............................3\n 4.2 Use of Registration Authorities (RAs)..............3\n 5. PCA Security & Privacy.............................3\n 5.1 Security requirements imposed on the PCA...........3\n 5.2 Security requirements imposed on CAs...............4\n 5.3 Security requireme 1875 authentication certificate certificates crl http identification key management path policy trust nested-reference unchanged"},{"id":"IETF RFC 2316","type":"specification","body":"IETF","designation":"RFC 2316","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2316.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2316.txt","https://www.rfc-editor.org/rfc/rfc2316.pdf"],"folder":"IETF/RFC-2316","files":{"txt":{"path":"standards/IETF/RFC-2316/RFC-2316.txt","sha256":"06867e94db4a589214007c48cf302c47902807c3bcea0b20b91927ab8f2007d8"}},"tags":["nested-reference","unchanged"],"summary":"On 3-5 March 1997, the IAB held a security architecture workshop at\n Bell Labs in Murray Hill, NJ. We identified the core security\n components of the architecture, and specified several documents that\n need to be written. Most importantly, we agreed that security was\n not optional, and that it needed to be designed in from the\n beginning.","scope_keywords":["2316","authorization","encryption","key","management","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3238","folder":"IETF/RFC-3238","source":"IETF/RFC-3238/RFC-3238.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null}],"search_text":"IETF RFC 2316 On 3-5 March 1997, the IAB held a security architecture workshop at\n Bell Labs in Murray Hill, NJ. We identified the core security\n components of the architecture, and specified several documents that\n need to be written. Most importantly, we agreed that security was\n not optional, and that it needed to be designed in from the\n beginning. 2316 authorization encryption key management policy subject nested-reference unchanged"},{"id":"IETF RFC 2479","type":"specification","body":"IETF","designation":"RFC 2479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2479.txt","https://www.rfc-editor.org/rfc/rfc2479.pdf"],"folder":"IETF/RFC-2479","files":{"txt":{"path":"standards/IETF/RFC-2479/RFC-2479.txt","sha256":"91bcd9b93c6ebb3b08d86b4825d4c916d3b6f22a4dff98669f422d866935014d"}},"tags":["nested-reference","unchanged"],"summary":"The IDUP-GSS-API extends the GSS-API [RFC-2078] for applications\n requiring protection of a generic data unit (such as a file or\n message) in a way which is independent of the protection of any other\n data unit and independent of any concurrent contact with designated\n \"receivers\" of the data unit. Thus, it is suitable for applications\n such as secure electronic mail where data needs to be protected\n without any on-line connection with the intended recipient(s) of that\n data. The protection offered by IDUP includes services such as data\n origin authentication with data integrity, data confidentiality with\n data integrity, and support for non-repudiation services. Subsequent\n to being protected, the data unit can be transferred to the\n recipient(s) - or to an archive - perhaps to be processed\n (\"unprotected\") only days or years later.\n\n Throughout the remainder of this document, the \"unit","scope_keywords":["2479","authentication","credential","credentials","key","management","pid","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"IETF RFC 2479 The IDUP-GSS-API extends the GSS-API [RFC-2078] for applications\n requiring protection of a generic data unit (such as a file or\n message) in a way which is independent of the protection of any other\n data unit and independent of any concurrent contact with designated\n \"receivers\" of the data unit. Thus, it is suitable for applications\n such as secure electronic mail where data needs to be protected\n without any on-line connection with the intended recipient(s) of that\n data. The protection offered by IDUP includes services such as data\n origin authentication with data integrity, data confidentiality with\n data integrity, and support for non-repudiation services. Subsequent\n to being protected, the data unit can be transferred to the\n recipient(s) - or to an archive - perhaps to be processed\n (\"unprotected\") only days or years later.\n\n Throughout the remainder of this document, the \"unit 2479 authentication credential credentials key management pid policy trust nested-reference unchanged"},{"id":"IETF RFC 3548","type":"specification","body":"IETF","designation":"RFC 3548","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3548.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3548.txt","https://www.rfc-editor.org/rfc/rfc3548.pdf"],"folder":"IETF/RFC-3548","files":{"txt":{"path":"standards/IETF/RFC-3548/RFC-3548.txt","sha256":"23006f2d28cca3e6a569bf67c618cdba5333c5e6b21a525b25892060b0fb24b2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the commonly used base 64, base 32, and base\n 16 encoding schemes. It also discusses the use of line-feeds in\n encoded data, use of padding in encoded data, use of non-alphabet\n characters in encoded data, and use of different encoding alphabets.","scope_keywords":["3548","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null}],"search_text":"IETF RFC 3548 This document describes the commonly used base 64, base 32, and base\n 16 encoding schemes. It also discusses the use of line-feeds in\n encoded data, use of padding in encoded data, use of non-alphabet\n characters in encoded data, and use of different encoding alphabets. 3548 crl key nested-reference unchanged"},{"id":"IETF RFC 4648","type":"specification","body":"IETF","designation":"RFC 4648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4648.txt","https://www.rfc-editor.org/rfc/rfc4648.pdf"],"folder":"IETF/RFC-4648","files":{"txt":{"path":"standards/IETF/RFC-4648/RFC-4648.txt","sha256":"84e14418f795d503be5f34bf23ce4ebaa119e9ec7c9f667d8caeb111385b178f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the commonly used base 64, base 32, and base\n 16 encoding schemes. It also discusses the use of line-feeds in\n encoded data, use of padding in encoded data, use of non-alphabet\n characters in encoded data, use of different encoding alphabets, and\n canonical encodings.\n\nJosefsson Standards Track [Page 1]\n\f\nRFC 4648 Base-N Encodings October 2006","scope_keywords":["4648","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 4648 This document describes the commonly used base 64, base 32, and base\n 16 encoding schemes. It also discusses the use of line-feeds in\n encoded data, use of padding in encoded data, use of non-alphabet\n characters in encoded data, use of different encoding alphabets, and\n canonical encodings.\n\nJosefsson Standards Track [Page 1]\n\f\nRFC 4648 Base-N Encodings October 2006 4648 crl key nested-reference unchanged"},{"id":"IETF RFC 4870","type":"specification","body":"IETF","designation":"RFC 4870","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4870.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4870.txt","https://www.rfc-editor.org/rfc/rfc4870.pdf"],"folder":"IETF/RFC-4870","files":{"txt":{"path":"standards/IETF/RFC-4870/RFC-4870.txt","sha256":"cf16e56b5141ec7b76c3f7c0bcd4ae1ec7fbf393700c5c75addcae975ace317a"}},"tags":["nested-reference","unchanged"],"summary":"\"DomainKeys\" creates a domain-level authentication framework for\n email by using public key technology and the DNS to prove the\n provenance and contents of an email.\n\n This document defines a framework for digitally signing email on a\n per-domain basis. The ultimate goal of this framework is to\n unequivocally prove and protect identity while retaining the\n semantics of Internet email as it is known today.\n\n Proof and protection of email identity may assist in the global\n control of \"spam\" and \"phishing\".\n\nDelany Historic [Page 1]\n\f\nRFC 4870 DomainKeys May 2007","scope_keywords":["4870","algorithm","authentication","certificate","delivery","key","keys","management","path","policy","presentation","risk","signature","trust","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 4870 \"DomainKeys\" creates a domain-level authentication framework for\n email by using public key technology and the DNS to prove the\n provenance and contents of an email.\n\n This document defines a framework for digitally signing email on a\n per-domain basis. The ultimate goal of this framework is to\n unequivocally prove and protect identity while retaining the\n semantics of Internet email as it is known today.\n\n Proof and protection of email identity may assist in the global\n control of \"spam\" and \"phishing\".\n\nDelany Historic [Page 1]\n\f\nRFC 4870 DomainKeys May 2007 4870 algorithm authentication certificate delivery key keys management path policy presentation risk signature trust x509 nested-reference unchanged"},{"id":"IETF RFC 5915","type":"specification","body":"IETF","designation":"RFC 5915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5915.txt","https://www.rfc-editor.org/rfc/rfc5915.pdf"],"folder":"IETF/RFC-5915","files":{"txt":{"path":"standards/IETF/RFC-5915/RFC-5915.txt","sha256":"5c7b3b2eb449618a581a0ac89209d5d6acc7c375689b2e91304b5dcd866151dc"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax and semantics for conveying\n Elliptic Curve (EC) private key information. The syntax and\n semantics defined herein are based on similar syntax and semantics\n defined by the Standards for Efficient Cryptography Group (SECG).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-e","scope_keywords":["5915","algorithm","http","key","keys","license","pki","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null}],"search_text":"IETF RFC 5915 This document specifies the syntax and semantics for conveying\n Elliptic Curve (EC) private key information. The syntax and\n semantics defined herein are based on similar syntax and semantics\n defined by the Standards for Efficient Cryptography Group (SECG).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-e 5915 algorithm http key keys license pki presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7468","type":"specification","body":"IETF","designation":"RFC 7468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7468.txt","https://www.rfc-editor.org/rfc/rfc7468.pdf"],"folder":"IETF/RFC-7468","files":{"txt":{"path":"standards/IETF/RFC-7468/RFC-7468.txt","sha256":"0b2c3c2087cc0b099789c90e61c0208e87b25793f0ce40090979e8c734b3d989"}},"tags":["nested-reference","unchanged"],"summary":"This document describes and discusses the textual encodings of the\n Public-Key Infrastructure X.509 (PKIX), Public-Key Cryptography\n Standards (PKCS), and Cryptographic Message Syntax (CMS). The\n textual encodings are well-known, are implemented by several\n applications and libraries, and are widely deployed. This document\n articulates the de facto rules by which existing implementations\n operate and defines them so that future implementations can\n interoperate.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current s","scope_keywords":["7468","attribute","authorization","certificate","certificates","crl","http","key","license","pki","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 7468 This document describes and discusses the textual encodings of the\n Public-Key Infrastructure X.509 (PKIX), Public-Key Cryptography\n Standards (PKCS), and Cryptographic Message Syntax (CMS). The\n textual encodings are well-known, are implemented by several\n applications and libraries, and are widely deployed. This document\n articulates the de facto rules by which existing implementations\n operate and defines them so that future implementations can\n interoperate.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current s 7468 attribute authorization certificate certificates crl http key license pki profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 8555","type":"specification","body":"IETF","designation":"RFC 8555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8555.txt","https://www.rfc-editor.org/rfc/rfc8555.pdf"],"folder":"IETF/RFC-8555","files":{"txt":{"path":"standards/IETF/RFC-8555/RFC-8555.txt","sha256":"a40983bbf91f2bd3a976d1c16520aa4418c02ba6d6f1ddcaf772881f823b2497"}},"tags":["nested-reference","unchanged"],"summary":"Public Key Infrastructure using X.509 (PKIX) certificates are used\n for a number of purposes, the most significant of which is the\n authentication of domain names. Thus, certification authorities\n (CAs) in the Web PKI are trusted to verify that an applicant for a\n certificate legitimately represents the domain name(s) in the\n certificate. As of this writing, this verification is done through a\n collection of ad hoc mechanisms. This document describes a protocol\n that a CA and an applicant can use to automate the process of\n verification and certificate issuance. The protocol also provides\n facilities for other certificate management functions, such as\n certificate revocation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received p","scope_keywords":["8555","authentication","authorization","certificate","certificates","http","https","key","license","management","pki","policy","revocation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"IETF RFC 8555 Public Key Infrastructure using X.509 (PKIX) certificates are used\n for a number of purposes, the most significant of which is the\n authentication of domain names. Thus, certification authorities\n (CAs) in the Web PKI are trusted to verify that an applicant for a\n certificate legitimately represents the domain name(s) in the\n certificate. As of this writing, this verification is done through a\n collection of ad hoc mechanisms. This document describes a protocol\n that a CA and an applicant can use to automate the process of\n verification and certificate issuance. The protocol also provides\n facilities for other certificate management functions, such as\n certificate revocation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received p 8555 authentication authorization certificate certificates http https key license management pki policy revocation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 2408","type":"specification","body":"IETF","designation":"RFC 2408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2408.txt","https://www.rfc-editor.org/rfc/rfc2408.pdf"],"folder":"IETF/RFC-2408","files":{"txt":{"path":"standards/IETF/RFC-2408/RFC-2408.txt","sha256":"631c8992cc395476a524ee33fe00c617966790d293d43030c80b742ec4b9d739"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a protocol utilizing security concepts necessary\n for establishing Security Associations (SA) and cryptographic keys in\n an Internet environment. A Security Association protocol that\n negotiates, establishes, modifies and deletes Security Associations\n and their attributes is required for an evolving Internet, where\n there will be numerous security mechanisms and several options for\n each security mechanism. The key management protocol must be robust\n in order to handle public key generation for the Internet community\n at large and private key requirements for those private networks with\n that requirement. The Internet Security Association and Key\n Management Protocol (ISAKMP) defines the procedures for\n authenticating a communicating peer, creation and management of\n Security Associations, key generation techniques, and threat\n mitigation (e.g. denial of service and ","scope_keywords":["2408","attribute","attributes","authentication","certificate","hash","identification","key","keys","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2628","folder":"IETF/RFC-2628","source":"IETF/RFC-2628/RFC-2628.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2408 This memo describes a protocol utilizing security concepts necessary\n for establishing Security Associations (SA) and cryptographic keys in\n an Internet environment. A Security Association protocol that\n negotiates, establishes, modifies and deletes Security Associations\n and their attributes is required for an evolving Internet, where\n there will be numerous security mechanisms and several options for\n each security mechanism. The key management protocol must be robust\n in order to handle public key generation for the Internet community\n at large and private key requirements for those private networks with\n that requirement. The Internet Security Association and Key\n Management Protocol (ISAKMP) defines the procedures for\n authenticating a communicating peer, creation and management of\n Security Associations, key generation techniques, and threat\n mitigation (e.g. denial of service and  2408 attribute attributes authentication certificate hash identification key keys management signature nested-reference unchanged"},{"id":"IETF RFC 2527","type":"specification","body":"IETF","designation":"RFC 2527","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2527.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2527.txt","https://www.rfc-editor.org/rfc/rfc2527.pdf"],"folder":"IETF/RFC-2527","files":{"txt":{"path":"standards/IETF/RFC-2527/RFC-2527.txt","sha256":"ad6007e2ee4e73b68f12097c2b427bad35d0225e4eb459d1af17d1b1705b7252"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a framework to assist the writers of\n certificate policies or certification practice statements for\n certification authorities and public key infrastructures. In\n particular, the framework provides a comprehensive list of topics\n that potentially (at the writer's discretion) need to be covered in a\n certificate policy definition or a certification practice statement.\n\n1. INTRODUCTION","scope_keywords":["2527","authentication","certificate","certificates","identification","key","keys","path","pki","policies","policy","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2785","folder":"IETF/RFC-2785","source":"IETF/RFC-2785/RFC-2785.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null}],"search_text":"IETF RFC 2527 This document presents a framework to assist the writers of\n certificate policies or certification practice statements for\n certification authorities and public key infrastructures. In\n particular, the framework provides a comprehensive list of topics\n that potentially (at the writer's discretion) need to be covered in a\n certificate policy definition or a certification practice statement.\n\n1. INTRODUCTION 2527 authentication certificate certificates identification key keys path pki policies policy signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 3647","type":"specification","body":"IETF","designation":"RFC 3647","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3647.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3647.txt","https://www.rfc-editor.org/rfc/rfc3647.pdf"],"folder":"IETF/RFC-3647","files":{"txt":{"path":"standards/IETF/RFC-3647/RFC-3647.txt","sha256":"3b6206506862f4b91f6103e86cbcf4634a4530e3827404777e1effe4db342a57"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document presents a framework to assist the writers of\n certificate policies or certification practice statements for\n participants within public key infrastructures, such as certification\n authorities, policy authorities, and communities of interest that\n wish to rely on certificates. In particular, the framework provides\n a comprehensive list of topics that potentially (at the writer's\n discretion) need to be covered in a certificate policy or a\n certification practice statement. This document supersedes RFC 2527.","scope_keywords":["3647","audit","authentication","certificate","certificates","crl","identification","key","management","ocsp","pki","policies","policy","presentation","profile","profiles"],"parent_legal_regulations":[{"celex":"32024R2980","eli":"https://data.europa.eu/eli/reg_impl/2024/2980/oj/eng","id":"2024-2980","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2980/2024-2980.md","title":"Trust framework and electronic notification system"}],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 411-2","folder":"ETSI/EN-319-411-2-V2.6.1","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf","version":"2.6.1"},{"body":"ETSI","designation":"TS 119 411-8","folder":"ETSI/TS-119-411-8-V1.1.1","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 431-1","folder":"ETSI/TS-119-431-1-V1.3.1","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 441","folder":"ETSI/TS-119-441-V1.2.1","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4810","folder":"IETF/RFC-4810","source":"IETF/RFC-4810/RFC-4810.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6841","folder":"IETF/RFC-6841","source":"IETF/RFC-6841/RFC-6841.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 3647 This document presents a framework to assist the writers of\n certificate policies or certification practice statements for\n participants within public key infrastructures, such as certification\n authorities, policy authorities, and communities of interest that\n wish to rely on certificates. In particular, the framework provides\n a comprehensive list of topics that potentially (at the writer's\n discretion) need to be covered in a certificate policy or a\n certification practice statement. This document supersedes RFC 2527. 3647 audit authentication certificate certificates crl identification key management ocsp pki policies policy presentation profile profiles cited-by-eu-law implementing-regulation nested-reference unchanged 2024-2980 Trust framework and electronic notification system 32024R2980"},{"id":"IETF RFC 1890","type":"specification","body":"IETF","designation":"RFC 1890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1890.txt","https://www.rfc-editor.org/rfc/rfc1890.pdf"],"folder":"IETF/RFC-1890","files":{"txt":{"path":"standards/IETF/RFC-1890/RFC-1890.txt","sha256":"24fc46a515c7c59dd1a0183b357e9a3300f8f312388c462668958c19b80d71a4"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a profile for the use of the real-time transport\n protocol (RTP), version 2, and the associated control protocol, RTCP,\n within audio and video multiparticipant conferences with minimal\n control. It provides interpretations of generic fields within the RTP\n specification suitable for audio and video conferences. In\n particular, this document defines a set of default mappings from\n payload type numbers to encodings.\n\n The document also describes how audio and video data may be carried\n within RTP. It defines a set of standard encodings and their names\n when used within RTP. However, the encoding definitions are\n independent of the particular transport mechanism used. The\n descriptions provide pointers to reference implementations and the\n detailed standards. This document is meant as an aid for implementors\n of audio, video and other real-time multimedia applications.\n","scope_keywords":["1890","algorithm","encryption","hash","key","keys","presentation","profile","profiles","registered","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2029","folder":"IETF/RFC-2029","source":"IETF/RFC-2029/RFC-2029.txt","version":null},{"body":"IETF","designation":"RFC 2032","folder":"IETF/RFC-2032","source":"IETF/RFC-2032/RFC-2032.txt","version":null},{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 2198","folder":"IETF/RFC-2198","source":"IETF/RFC-2198/RFC-2198.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2429","folder":"IETF/RFC-2429","source":"IETF/RFC-2429/RFC-2429.txt","version":null},{"body":"IETF","designation":"RFC 2431","folder":"IETF/RFC-2431","source":"IETF/RFC-2431/RFC-2431.txt","version":null},{"body":"IETF","designation":"RFC 2435","folder":"IETF/RFC-2435","source":"IETF/RFC-2435/RFC-2435.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2586","folder":"IETF/RFC-2586","source":"IETF/RFC-2586/RFC-2586.txt","version":null},{"body":"IETF","designation":"RFC 2658","folder":"IETF/RFC-2658","source":"IETF/RFC-2658/RFC-2658.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2833","folder":"IETF/RFC-2833","source":"IETF/RFC-2833/RFC-2833.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null}],"search_text":"IETF RFC 1890 This memo describes a profile for the use of the real-time transport\n protocol (RTP), version 2, and the associated control protocol, RTCP,\n within audio and video multiparticipant conferences with minimal\n control. It provides interpretations of generic fields within the RTP\n specification suitable for audio and video conferences. In\n particular, this document defines a set of default mappings from\n payload type numbers to encodings.\n\n The document also describes how audio and video data may be carried\n within RTP. It defines a set of standard encodings and their names\n when used within RTP. However, the encoding definitions are\n independent of the particular transport mechanism used. The\n descriptions provide pointers to reference implementations and the\n detailed standards. This document is meant as an aid for implementors\n of audio, video and other real-time multimedia applications.\n 1890 algorithm encryption hash key keys presentation profile profiles registered timestamp nested-reference unchanged"},{"id":"IETF RFC 1991","type":"specification","body":"IETF","designation":"RFC 1991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1991.txt","https://www.rfc-editor.org/rfc/rfc1991.pdf"],"folder":"IETF/RFC-1991","files":{"txt":{"path":"standards/IETF/RFC-1991/RFC-1991.txt","sha256":"7c4f77c7a507ffc5e3983cbc7b1e89d5630f626cb7a62a025c1c4c4db973de15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Atkins\nRequest for Comments: 1991 MIT\nCategory: Informational W. Stallings\n Comp-Comm Consulting\n P. Zimmermann\n Boulder Software Engineering\n August 1996\n\n PGP Message Exchange Formats\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction............................................2\n 2. PGP Services............................................2\n 2.1 Digital signature.......................................3\n 2.2 Confidentiality.........................................3\n 2.3 Compression.............................................4\n 2.4 Radix-64 conversion.....................................4\n 2.4.1 ASCII Armor Formats.....................................5\n 3. Data Element Formats...................","scope_keywords":["1991","algorithm","encryption","hash","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2015","folder":"IETF/RFC-2015","source":"IETF/RFC-2015/RFC-2015.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3626","folder":"IETF/RFC-3626","source":"IETF/RFC-3626/RFC-3626.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null}],"search_text":"IETF RFC 1991 Network Working Group D. Atkins\nRequest for Comments: 1991 MIT\nCategory: Informational W. Stallings\n Comp-Comm Consulting\n P. Zimmermann\n Boulder Software Engineering\n August 1996\n\n PGP Message Exchange Formats\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction............................................2\n 2. PGP Services............................................2\n 2.1 Digital signature.......................................3\n 2.2 Confidentiality.........................................3\n 2.3 Compression.............................................4\n 2.4 Radix-64 conversion.....................................4\n 2.4.1 ASCII Armor Formats.....................................5\n 3. Data Element Formats................... 1991 algorithm encryption hash key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 2440","type":"specification","body":"IETF","designation":"RFC 2440","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2440.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2440.txt","https://www.rfc-editor.org/rfc/rfc2440.pdf"],"folder":"IETF/RFC-2440","files":{"txt":{"path":"standards/IETF/RFC-2440/RFC-2440.txt","sha256":"801dcc64b716c0e5df01af135606763edf16696925f95984036f04c8784a6a30"}},"tags":["nested-reference","unchanged"],"summary":"This document is maintained in order to publish all necessary\n information needed to develop interoperable applications based on the\n OpenPGP format. It is not a step-by-step cookbook for writing an\n application. It describes only the format and methods needed to read,\n check, generate, and write conforming packets crossing any network.\n It does not deal with storage and implementation questions. It does,\n\nCallas, et. al. Standards Track [Page 1]\n\f\nRFC 2440 OpenPGP Message Format November 1998\n\n however, discuss implementation issues necessary to avoid security\n flaws.\n\n Open-PGP software uses a combination of strong public-key and\n symmetric cryptography to provide security services for electronic\n communications and data storage. These services include\n confidentiality, key management, authentication, and digital\n signatures. This document specifies the message formats used in\n OpenPGP","scope_keywords":["2440","algorithm","algorithms","authentication","encryption","hash","issuer","key","management","policy","revocation","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null}],"search_text":"IETF RFC 2440 This document is maintained in order to publish all necessary\n information needed to develop interoperable applications based on the\n OpenPGP format. It is not a step-by-step cookbook for writing an\n application. It describes only the format and methods needed to read,\n check, generate, and write conforming packets crossing any network.\n It does not deal with storage and implementation questions. It does,\n\nCallas, et. al. Standards Track [Page 1]\n\f\nRFC 2440 OpenPGP Message Format November 1998\n\n however, discuss implementation issues necessary to avoid security\n flaws.\n\n Open-PGP software uses a combination of strong public-key and\n symmetric cryptography to provide security services for electronic\n communications and data storage. These services include\n confidentiality, key management, authentication, and digital\n signatures. This document specifies the message formats used in\n OpenPGP 2440 algorithm algorithms authentication encryption hash issuer key management policy revocation signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 4880","type":"specification","body":"IETF","designation":"RFC 4880","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4880.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4880.txt","https://www.rfc-editor.org/rfc/rfc4880.pdf"],"folder":"IETF/RFC-4880","files":{"txt":{"path":"standards/IETF/RFC-4880/RFC-4880.txt","sha256":"575dc55f0edea3cb490ad92941e83bd755f674c20619efee0a5a5b721b32bf02"}},"tags":["nested-reference","unchanged"],"summary":"This document is maintained in order to publish all necessary\n information needed to develop interoperable applications based on the\n OpenPGP format. It is not a step-by-step cookbook for writing an\n application. It describes only the format and methods needed to\n read, check, generate, and write conforming packets crossing any\n network. It does not deal with storage and implementation questions.\n It does, however, discuss implementation issues necessary to avoid\n security flaws.\n\n OpenPGP software uses a combination of strong public-key and\n symmetric cryptography to provide security services for electronic\n communications and data storage. These services include\n confidentiality, key management, authentication, and digital\n signatures. This document specifies the message formats used in\n OpenPGP.\n\nCallas, et al Standards Track [Page 1]\n\f\nRFC 4880 OpenPGP Message Format November 2007","scope_keywords":["4880","algorithm","algorithms","authentication","encryption","hash","issuer","key","management","policy","revocation","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 4880 This document is maintained in order to publish all necessary\n information needed to develop interoperable applications based on the\n OpenPGP format. It is not a step-by-step cookbook for writing an\n application. It describes only the format and methods needed to\n read, check, generate, and write conforming packets crossing any\n network. It does not deal with storage and implementation questions.\n It does, however, discuss implementation issues necessary to avoid\n security flaws.\n\n OpenPGP software uses a combination of strong public-key and\n symmetric cryptography to provide security services for electronic\n communications and data storage. These services include\n confidentiality, key management, authentication, and digital\n signatures. This document specifies the message formats used in\n OpenPGP.\n\nCallas, et al Standards Track [Page 1]\n\f\nRFC 4880 OpenPGP Message Format November 2007 4880 algorithm algorithms authentication encryption hash issuer key management policy revocation signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2314","type":"specification","body":"IETF","designation":"RFC 2314","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2314.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2314.txt","https://www.rfc-editor.org/rfc/rfc2314.pdf"],"folder":"IETF/RFC-2314","files":{"txt":{"path":"standards/IETF/RFC-2314/RFC-2314.txt","sha256":"5e6bf00a0ddbada082192b549193d9e4059c0b459ca3c2858377ff17cd12285f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Kaliski\nRequest for Comments: 2314 RSA Laboratories East\nCategory: Informational March 1998\n\n PKCS #10: Certification Request Syntax\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a syntax for certification requests.\n\n1. Scope\n\n A certification request consists of a distinguished name, a public\n key, and optionally a set of attributes, collectively signed by the\n entity requesting certification. Certification requests are sent to a\n certification authority, who transforms the request to an X.509\n public-key certificate, or a PKCS #6 extended certificate. (In what\n form the certification authority returns","scope_keywords":["2314","algorithm","attribute","attributes","authentication","certificate","certificates","crl","encryption","issuer","key","path","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2875","folder":"IETF/RFC-2875","source":"IETF/RFC-2875/RFC-2875.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2314 Network Working Group B. Kaliski\nRequest for Comments: 2314 RSA Laboratories East\nCategory: Informational March 1998\n\n PKCS #10: Certification Request Syntax\n Version 1.5\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nOverview\n\n This document describes a syntax for certification requests.\n\n1. Scope\n\n A certification request consists of a distinguished name, a public\n key, and optionally a set of attributes, collectively signed by the\n entity requesting certification. Certification requests are sent to a\n certification authority, who transforms the request to an X.509\n public-key certificate, or a PKCS #6 extended certificate. (In what\n form the certification authority returns 2314 algorithm attribute attributes authentication certificate certificates crl encryption issuer key path revocation signature nested-reference unchanged"},{"id":"IETF RFC 2986","type":"specification","body":"IETF","designation":"RFC 2986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2986.txt","https://www.rfc-editor.org/rfc/rfc2986.pdf"],"folder":"IETF/RFC-2986","files":{"txt":{"path":"standards/IETF/RFC-2986/RFC-2986.txt","sha256":"9f93627442b9fa03b24336646ffdfb3f33ed8cfd575e6b984fddab5fe88d03c0"}},"tags":["nested-reference","unchanged"],"summary":"This memo represents a republication of PKCS #10 v1.7 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from the PKCS #9 v2.0 or the PKCS #10 v1.7 document.\n\n This memo describes a syntax for certification requests.","scope_keywords":["2986","algorithm","attribute","attributes","certificate","certificates","issuer","key","revocation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 2986 This memo represents a republication of PKCS #10 v1.7 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from the PKCS #9 v2.0 or the PKCS #10 v1.7 document.\n\n This memo describes a syntax for certification requests. 2986 algorithm attribute attributes certificate certificates issuer key revocation signature subject nested-reference unchanged"},{"id":"IETF RFC 1555","type":"specification","body":"IETF","designation":"RFC 1555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1555.txt","https://www.rfc-editor.org/rfc/rfc1555.pdf"],"folder":"IETF/RFC-1555","files":{"txt":{"path":"standards/IETF/RFC-1555/RFC-1555.txt","sha256":"eb2eb286dd956d4281e0166ceeb1ef553886dc156683fff11ff87143bca77986"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Nussbacher\nRequest for Comments: 1555 Israeli Inter-University\nCategory: Informational Computer Center\n Y. Bourvine\n Hebrew University\n December 1993\n\n Hebrew Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes the encoding used in electronic mail [RFC822]\n for transferring Hebrew. The standard devised makes use of MIME\n [RFC1521] and ISO-8859-8.\n\nDescription\n\n All Hebrew text when transferred via e-mail must first be translated\n into ISO-8859-8, and then encoded using either Quoted-Printable\n (preferable) or Base64, as defined in MIME.\n\n The following table provides the four most common Hebrew encodings:\n\n PC IBM PC ISO\n Hebrew 8859-8\n letter 8-bit 7-bit 8","scope_keywords":["1555","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1555 Network Working Group H. Nussbacher\nRequest for Comments: 1555 Israeli Inter-University\nCategory: Informational Computer Center\n Y. Bourvine\n Hebrew University\n December 1993\n\n Hebrew Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes the encoding used in electronic mail [RFC822]\n for transferring Hebrew. The standard devised makes use of MIME\n [RFC1521] and ISO-8859-8.\n\nDescription\n\n All Hebrew text when transferred via e-mail must first be translated\n into ISO-8859-8, and then encoded using either Quoted-Printable\n (preferable) or Base64, as defined in MIME.\n\n The following table provides the four most common Hebrew encodings:\n\n PC IBM PC ISO\n Hebrew 8859-8\n letter 8-bit 7-bit 8 1555 management subject nested-reference unchanged"},{"id":"IETF RFC 1830","type":"specification","body":"IETF","designation":"RFC 1830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1830.txt","https://www.rfc-editor.org/rfc/rfc1830.pdf"],"folder":"IETF/RFC-1830","files":{"txt":{"path":"standards/IETF/RFC-1830/RFC-1830.txt","sha256":"8838f6454a658a7a52dc352e2bb14bbc035d5bd8bc0a7d61280c78beb503230e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines two extensions to the SMTP service. The first\n service enables a SMTP client and server to negotiate the use of an\n alternate DATA command \"BDAT\" for efficiently sending large MIME\n messages. The second extension takes advantage of the BDAT command\n to permit the negotiated sending of unencoded binary data.\n\n2. Introduction\n\n The MIME extensions to the Internet message protocol provides for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. Anticipating the need to more efficiently\n transport the new media made possible with MIME, the SMTP protocol\n has been extended to provide transport for new message types. RFC\n 1426 defines one such extension for the transmission of unencoded 8\n bit MIME messages [8BIT]. This service extension permits the\n receiver SMTP to declare support for 8 bit body parts and the sender\n to request 8 bit","scope_keywords":["1830","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null}],"search_text":"IETF RFC 1830 This memo defines two extensions to the SMTP service. The first\n service enables a SMTP client and server to negotiate the use of an\n alternate DATA command \"BDAT\" for efficiently sending large MIME\n messages. The second extension takes advantage of the BDAT command\n to permit the negotiated sending of unencoded binary data.\n\n2. Introduction\n\n The MIME extensions to the Internet message protocol provides for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. Anticipating the need to more efficiently\n transport the new media made possible with MIME, the SMTP protocol\n has been extended to provide transport for new message types. RFC\n 1426 defines one such extension for the transmission of unencoded 8\n bit MIME messages [8BIT]. This service extension permits the\n receiver SMTP to declare support for 8 bit body parts and the sender\n to request 8 bit 1830 key nested-reference unchanged"},{"id":"IETF RFC 1854","type":"specification","body":"IETF","designation":"RFC 1854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1854.txt","https://www.rfc-editor.org/rfc/rfc1854.pdf"],"folder":"IETF/RFC-1854","files":{"txt":{"path":"standards/IETF/RFC-1854/RFC-1854.txt","sha256":"ea95afef3d77b745b031ae973d57cfbd4bd9868a35194a1dce6660b55c9154be"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby a server\n can indicate the extent of its ability to accept multiple commands in\n a single TCP send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly.","scope_keywords":["1854","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2197","folder":"IETF/RFC-2197","source":"IETF/RFC-2197/RFC-2197.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null}],"search_text":"IETF RFC 1854 This memo defines an extension to the SMTP service whereby a server\n can indicate the extent of its ability to accept multiple commands in\n a single TCP send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly. 1854 key nested-reference unchanged"},{"id":"IETF RFC 1985","type":"specification","body":"IETF","designation":"RFC 1985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1985.txt","https://www.rfc-editor.org/rfc/rfc1985.pdf"],"folder":"IETF/RFC-1985","files":{"txt":{"path":"standards/IETF/RFC-1985/RFC-1985.txt","sha256":"965044cff059b5a9695b09172884a6acd9a504d1b4f882d4c6cb3f63fc311ce1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n start the processing of its queues for messages to go to a given\n host. This extension is meant to be used in startup conditions as\n well as for mail nodes that have transient connections to their\n service providers.\n\n1. Introduction\n\n The TURN command was a valid attempt to address the problem of having\n to start the processing for the mail queue on a remote machine.\n However, the TURN command presents a large security loophole. As\n there is no verification of the remote host name, the TURN command\n could be used by a rogue system to download the mail for a site other\n than itself.\n\n Therefore, this memo introduces the ETRN command. This command uses\n the mechanism defined in [4] to define extensions to the SMTP service\n whereby a client (\"sender-SMTP\"","scope_keywords":["1985","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 1985 This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n start the processing of its queues for messages to go to a given\n host. This extension is meant to be used in startup conditions as\n well as for mail nodes that have transient connections to their\n service providers.\n\n1. Introduction\n\n The TURN command was a valid attempt to address the problem of having\n to start the processing for the mail queue on a remote machine.\n However, the TURN command presents a large security loophole. As\n there is no verification of the remote host name, the TURN command\n could be used by a rogue system to download the mail for a site other\n than itself.\n\n Therefore, this memo introduces the ETRN command. This command uses\n the mechanism defined in [4] to define extensions to the SMTP service\n whereby a client (\"sender-SMTP\" 1985 key qualified nested-reference unchanged"},{"id":"IETF RFC 2197","type":"specification","body":"IETF","designation":"RFC 2197","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2197.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2197.txt","https://www.rfc-editor.org/rfc/rfc2197.pdf"],"folder":"IETF/RFC-2197","files":{"txt":{"path":"standards/IETF/RFC-2197/RFC-2197.txt","sha256":"5a2485b4e840bef2d25bc0b6e7c66cbcce8c02ea546678a86e9d2306bd9f01a0"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby a server\n can indicate the extent of its ability to accept multiple commands in\n a single TCP send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly.\n\n The present document is an updated version of RFC 1854 [3]. Only\n textual and editorial changes have been made; the protocol has not\n changed in any way.\n\n2. Introduction\n\n Although SMTP is widely and robustly deployed, certain extensions may\n nevertheless prove useful. In particular, many parts of the Internet\n make use of high latency network links. SMTP's intrinsic one\n command-one response structure is significantly penalized by high\n latency links, often to the point where the factors contributing to\n overall connection time are dominated by the time spent waiting for\n responses to individual commands (turnaround ti","scope_keywords":["2197","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null}],"search_text":"IETF RFC 2197 This memo defines an extension to the SMTP service whereby a server\n can indicate the extent of its ability to accept multiple commands in\n a single TCP send operation. Using a single TCP send operation for\n multiple commands can improve SMTP performance significantly.\n\n The present document is an updated version of RFC 1854 [3]. Only\n textual and editorial changes have been made; the protocol has not\n changed in any way.\n\n2. Introduction\n\n Although SMTP is widely and robustly deployed, certain extensions may\n nevertheless prove useful. In particular, many parts of the Internet\n make use of high latency network links. SMTP's intrinsic one\n command-one response structure is significantly penalized by high\n latency links, often to the point where the factors contributing to\n overall connection time are dominated by the time spent waiting for\n responses to individual commands (turnaround ti 2197 key nested-reference unchanged"},{"id":"IETF RFC 143","type":"specification","body":"IETF","designation":"RFC 143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc143.txt","https://www.rfc-editor.org/rfc/rfc143.pdf"],"folder":"IETF/RFC-143","files":{"txt":{"path":"standards/IETF/RFC-143/RFC-143.txt","sha256":"3499a4233a5ddcf5223dd248e7bc63d4d063f4f4e31d708e3ef262bcf7873935"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Naylor\nRequest for Comments #143 J. Wong\nNIC #6728 C. Kline\nCategories: D.1, D.3 J. Postel\nObsoletes: None UCLA - NMC\nUpdates: 123, 145 3 May 1971\n\n Regarding Proferred Official ICP\n\nWe should like to comment on a race condition discovered in the ICP as\nproposed in NWG/RFC #123. The problem arises when the server attempts\nto initiate a second connection to the user's receive socket and the\nfirst connection is not yet closed. Using a similar notation to that of\nNWG/RFC #123 the following table illustrates the sequence of events in\nthe proferred and proposed ICP. The last two columns indicate which\nactions must be completed before the current action may be initiated.\nUser and Server are third level programs, and UNCP and SNCP are the\nusers NCP and Servers NCP respectively. Allocates have not been\nincluded since they add nothing to the argument.\n\n Required Predecess","scope_keywords":["143"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 143 Network Working Group W. Naylor\nRequest for Comments #143 J. Wong\nNIC #6728 C. Kline\nCategories: D.1, D.3 J. Postel\nObsoletes: None UCLA - NMC\nUpdates: 123, 145 3 May 1971\n\n Regarding Proferred Official ICP\n\nWe should like to comment on a race condition discovered in the ICP as\nproposed in NWG/RFC #123. The problem arises when the server attempts\nto initiate a second connection to the user's receive socket and the\nfirst connection is not yet closed. Using a similar notation to that of\nNWG/RFC #123 the following table illustrates the sequence of events in\nthe proferred and proposed ICP. The last two columns indicate which\nactions must be completed before the current action may be initiated.\nUser and Server are third level programs, and UNCP and SNCP are the\nusers NCP and Servers NCP respectively. Allocates have not been\nincluded since they add nothing to the argument.\n\n Required Predecess 143 nested-reference unchanged"},{"id":"IETF RFC 1432","type":"specification","body":"IETF","designation":"RFC 1432","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1432.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1432.txt","https://www.rfc-editor.org/rfc/rfc1432.pdf"],"folder":"IETF/RFC-1432","files":{"txt":{"path":"standards/IETF/RFC-1432/RFC-1432.txt","sha256":"719b10cee994b133888a4ccd5ae4d02b0cf29bf28e36658bed230f2fe7b40efb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Quarterman\nRequest for Comments: 1432 MIDS\n March 1993\n\n Recent Internet Books\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This article originally appeared in Volume 2 Number 12, (December\n 1992) of Matrix News, the monthly newsletter of Matrix Information\n and Directory Services, Inc. (MIDS).\n\n1. Which Books\n\n Here is a list of books related to using the Internet, which is the\n global and exponentially growing network of more than a million\n computers that communicate by interactive use of the TCP/IP\n protocols, for the use of millions of users. This article was\n prompted by the recent publication of nine or ten books on the\n Internet in the space of a year (some are so new they aren't even\n published yet). I have also included so","scope_keywords":["1432","path","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1462","folder":"IETF/RFC-1462","source":"IETF/RFC-1462/RFC-1462.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null}],"search_text":"IETF RFC 1432 Network Working Group J. Quarterman\nRequest for Comments: 1432 MIDS\n March 1993\n\n Recent Internet Books\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This article originally appeared in Volume 2 Number 12, (December\n 1992) of Matrix News, the monthly newsletter of Matrix Information\n and Directory Services, Inc. (MIDS).\n\n1. Which Books\n\n Here is a list of books related to using the Internet, which is the\n global and exponentially growing network of more than a million\n computers that communicate by interactive use of the TCP/IP\n protocols, for the use of millions of users. This article was\n prompted by the recent publication of nine or ten books on the\n Internet in the space of a year (some are so new they aren't even\n published yet). I have also included so 1432 path presentation risk nested-reference unchanged"},{"id":"IETF RFC 1462","type":"specification","body":"IETF","designation":"RFC 1462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1462.txt","https://www.rfc-editor.org/rfc/rfc1462.pdf"],"folder":"IETF/RFC-1462","files":{"txt":{"path":"standards/IETF/RFC-1462/RFC-1462.txt","sha256":"5b7138b218b3b68e58e71ed17cd3c4219545380f2621c24d3ec70cddeb76b04f"}},"tags":["nested-reference","unchanged"],"summary":"This FYI RFC answers the question, \"What is the Internet?\" and is\n produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). Containing a modified chapter from Ed\n Krol's 1992 book, \"The Whole Internet User's Guide and Catalog,\" the\n paper covers the Internet's definition, history, administration,\n protocols, financing, and current issues such as growth,\n commercialization, and privatization.","scope_keywords":["1462","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1463","folder":"IETF/RFC-1463","source":"IETF/RFC-1463/RFC-1463.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null}],"search_text":"IETF RFC 1462 This FYI RFC answers the question, \"What is the Internet?\" and is\n produced by the User Services Working Group of the Internet\n Engineering Task Force (IETF). Containing a modified chapter from Ed\n Krol's 1992 book, \"The Whole Internet User's Guide and Catalog,\" the\n paper covers the Internet's definition, history, administration,\n protocols, financing, and current issues such as growth,\n commercialization, and privatization. 1462 policies nested-reference unchanged"},{"id":"IETF RFC 3040","type":"specification","body":"IETF","designation":"RFC 3040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3040.txt","https://www.rfc-editor.org/rfc/rfc3040.pdf"],"folder":"IETF/RFC-3040","files":{"txt":{"path":"standards/IETF/RFC-3040/RFC-3040.txt","sha256":"af4d7988c364baaf754681ab9590be6c3a8a864cb382640ebb26c6bf78f32aae"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies standard terminology and the taxonomy of web\n replication and caching infrastructure as deployed today. It\n introduces standard concepts, and protocols used today within this\n application domain. Currently deployed solutions employing these\n technologies are presented to establish a standard taxonomy. Known\n problems with caching proxies are covered in the document titled\n \"Known HTTP Proxy/Caching Problems\", and are not part of this\n document. This document presents open protocols and points to\n published material for each protocol.","scope_keywords":["3040","authentication","http","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3143","folder":"IETF/RFC-3143","source":"IETF/RFC-3143/RFC-3143.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3238","folder":"IETF/RFC-3238","source":"IETF/RFC-3238/RFC-3238.txt","version":null},{"body":"IETF","designation":"RFC 3466","folder":"IETF/RFC-3466","source":"IETF/RFC-3466/RFC-3466.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 3040 This memo specifies standard terminology and the taxonomy of web\n replication and caching infrastructure as deployed today. It\n introduces standard concepts, and protocols used today within this\n application domain. Currently deployed solutions employing these\n technologies are presented to establish a standard taxonomy. Known\n problems with caching proxies are covered in the document titled\n \"Known HTTP Proxy/Caching Problems\", and are not part of this\n document. This document presents open protocols and points to\n published material for each protocol. 3040 authentication http pid trust nested-reference unchanged"},{"id":"IETF RFC 1451","type":"specification","body":"IETF","designation":"RFC 1451","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1451.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1451.txt","https://www.rfc-editor.org/rfc/rfc1451.pdf"],"folder":"IETF/RFC-1451","files":{"txt":{"path":"standards/IETF/RFC-1451/RFC-1451.txt","sha256":"e02f21d7922a8e44a0cf2a07cfc801b77d51c5b861a2e62d65a1e418f316627b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Case\n Request for Comments: 1451 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Manager-to-Manager\n Management Information Base\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Overview .............................................. 3\n 2.1 A SNMPv2 Entity Acting in a Dual Role ............... 3\n 2.2 Alarms, Events, and Notification","scope_keywords":["1451","authentication","authorization","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1441","folder":"IETF/RFC-1441","source":"IETF/RFC-1441/RFC-1441.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null}],"search_text":"IETF RFC 1451 Network Working Group J. Case\n Request for Comments: 1451 SNMP Research, Inc.\n K. McCloghrie\n Hughes LAN Systems\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n Carnegie Mellon University\n April 1993\n\n Manager-to-Manager\n Management Information Base\n\n Status of this Memo\n\n This RFC specifes an IAB standards track protocol for the\n Internet community, and requests discussion and suggestions\n for improvements. Please refer to the current edition of the\n \"IAB Official Protocol Standards\" for the standardization\n state and status of this protocol. Distribution of this memo\n is unlimited.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 1.1 A Note on Terminology ............................... 2\n 2 Overview .............................................. 3\n 2.1 A SNMPv2 Entity Acting in a Dual Role ............... 3\n 2.2 Alarms, Events, and Notification 1451 authentication authorization management policies nested-reference unchanged"},{"id":"IETF RFC 1454","type":"specification","body":"IETF","designation":"RFC 1454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1454.txt","https://www.rfc-editor.org/rfc/rfc1454.pdf"],"folder":"IETF/RFC-1454","files":{"txt":{"path":"standards/IETF/RFC-1454/RFC-1454.txt","sha256":"d9cf8a8a1f35db220382e52a64a4b2cf1ad5640ac9e43083b5ba4182576aa1c2"}},"tags":["nested-reference","unchanged"],"summary":"This is a slightly edited reprint of RARE Technical Report\n (RTC(93)004).\n\n The following is a brief summary of the characteristics of the three\n main proposals for replacing the current Internet Protocol. It is not\n intended to be exhaustive or definitive (a brief bibliography at the\n end points to sources of more information), but to serve as input to\n the European discussions on these proposals, to be co-ordinated by\n RARE and RIPE. It should be recognised that the proposals are\n themselves \"moving targets\", and in so far as this paper is accurate\n at all, it reflects the position at the 25th IETF meeting in\n Washington, DC. Comments from Ross Callon and Paul Tsuchiya on the\n original draft have been incorporated. Note that for a time the term\n \"IPv7\" was use to mean the eventual next version of IP, but that the\n same term was closely associated with a particilar proposal, so the\n ter","scope_keywords":["1454","policies","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null}],"search_text":"IETF RFC 1454 This is a slightly edited reprint of RARE Technical Report\n (RTC(93)004).\n\n The following is a brief summary of the characteristics of the three\n main proposals for replacing the current Internet Protocol. It is not\n intended to be exhaustive or definitive (a brief bibliography at the\n end points to sources of more information), but to serve as input to\n the European discussions on these proposals, to be co-ordinated by\n RARE and RIPE. It should be recognised that the proposals are\n themselves \"moving targets\", and in so far as this paper is accurate\n at all, it reflects the position at the 25th IETF meeting in\n Washington, DC. Comments from Ross Callon and Paul Tsuchiya on the\n original draft have been incorporated. Note that for a time the term\n \"IPv7\" was use to mean the eventual next version of IP, but that the\n same term was closely associated with a particilar proposal, so the\n ter 1454 policies policy risk nested-reference unchanged"},{"id":"IETF RFC 1456","type":"specification","body":"IETF","designation":"RFC 1456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1456.txt","https://www.rfc-editor.org/rfc/rfc1456.pdf"],"folder":"IETF/RFC-1456","files":{"txt":{"path":"standards/IETF/RFC-1456/RFC-1456.txt","sha256":"4bd921e49d84cf4e265ae8eb201f87fbe9ea596943464605b3010b634bf6f87d"}},"tags":["nested-reference","unchanged"],"summary":"software developers may wish to devise more efficient input schemes,\n but the intent is for all Vietnamese keyboard software to support the\n basic VIQR method to minimize learning time for Vietnamese who will\n already be familiar with the mnemonic method described here.","scope_keywords":["1456","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1456 software developers may wish to devise more efficient input schemes,\n but the intent is for all Vietnamese keyboard software to support the\n basic VIQR method to minimize learning time for Vietnamese who will\n already be familiar with the mnemonic method described here. 1456 key keys presentation nested-reference unchanged"},{"id":"IETF RFC 3272","type":"specification","body":"IETF","designation":"RFC 3272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3272.txt","https://www.rfc-editor.org/rfc/rfc3272.pdf"],"folder":"IETF/RFC-3272","files":{"txt":{"path":"standards/IETF/RFC-3272/RFC-3272.txt","sha256":"421f2062ac32a11ea8a4553df7993f777e862b03a715a5e5702bd0ff1617f71a"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the principles of Traffic Engineering (TE) in the\n Internet. The document is intended to promote better understanding\n of the issues surrounding traffic engineering in IP networks, and to\n provide a common basis for the development of traffic engineering\n capabilities for the Internet. The principles, architectures, and\n methodologies for performance evaluation and performance optimization\n of operational IP networks are discussed throughout this document.","scope_keywords":["3272","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null},{"body":"IETF","designation":"RFC 3386","folder":"IETF/RFC-3386","source":"IETF/RFC-3386/RFC-3386.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null}],"search_text":"IETF RFC 3272 This memo describes the principles of Traffic Engineering (TE) in the\n Internet. The document is intended to promote better understanding\n of the issues surrounding traffic engineering in IP networks, and to\n provide a common basis for the development of traffic engineering\n capabilities for the Internet. The principles, architectures, and\n methodologies for performance evaluation and performance optimization\n of operational IP networks are discussed throughout this document. 3272 management path nested-reference unchanged"},{"id":"IETF RFC 2810","type":"specification","body":"IETF","designation":"RFC 2810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2810.txt","https://www.rfc-editor.org/rfc/rfc2810.pdf"],"folder":"IETF/RFC-2810","files":{"txt":{"path":"standards/IETF/RFC-2810/RFC-2810.txt","sha256":"b00c6ae92ef66b1b2c3a15df86e6e1ab8268bcb40ebbadd388d75531bf6e62f6"}},"tags":["nested-reference","unchanged"],"summary":"The IRC (Internet Relay Chat) protocol is for use with text based\n conferencing. It has been developed since 1989 when it was originally\n implemented as a mean for users on a BBS to chat amongst themselves.\n\n First formally documented in May 1993 by RFC 1459 [IRC], the protocol\n has kept evolving. This document is an update describing the\n architecture of the current IRC protocol and the role of its\n different components. Other documents describe in detail the\n protocol used between the various components defined here.","scope_keywords":["2810","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2811","folder":"IETF/RFC-2811","source":"IETF/RFC-2811/RFC-2811.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null}],"search_text":"IETF RFC 2810 The IRC (Internet Relay Chat) protocol is for use with text based\n conferencing. It has been developed since 1989 when it was originally\n implemented as a mean for users on a BBS to chat amongst themselves.\n\n First formally documented in May 1993 by RFC 1459 [IRC], the protocol\n has kept evolving. This document is an update describing the\n architecture of the current IRC protocol and the role of its\n different components. Other documents describe in detail the\n protocol used between the various components defined here. 2810 delivery management nested-reference unchanged"},{"id":"IETF RFC 2811","type":"specification","body":"IETF","designation":"RFC 2811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2811.txt","https://www.rfc-editor.org/rfc/rfc2811.pdf"],"folder":"IETF/RFC-2811","files":{"txt":{"path":"standards/IETF/RFC-2811/RFC-2811.txt","sha256":"41e2b24141669f0094e78896f5d2c54d26db2cbed8a299cf9b0bb1aca42d3a96"}},"tags":["nested-reference","unchanged"],"summary":"One of the most notable characteristics of the IRC (Internet Relay\n Chat) protocol is to allow for users to be grouped in forums, called\n channels, providing a mean for multiple users to communicate\n together.\n\n There was originally a unique type of channels, but with the years,\n new types appeared either as a response to a need, or for\n experimental purposes.\n\n This document specifies how channels, their characteristics and\n properties are managed by IRC servers.","scope_keywords":["2811","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2810","folder":"IETF/RFC-2810","source":"IETF/RFC-2810/RFC-2810.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null}],"search_text":"IETF RFC 2811 One of the most notable characteristics of the IRC (Internet Relay\n Chat) protocol is to allow for users to be grouped in forums, called\n channels, providing a mean for multiple users to communicate\n together.\n\n There was originally a unique type of channels, but with the years,\n new types appeared either as a response to a need, or for\n experimental purposes.\n\n This document specifies how channels, their characteristics and\n properties are managed by IRC servers. 2811 key management nested-reference unchanged"},{"id":"IETF RFC 3921","type":"specification","body":"IETF","designation":"RFC 3921","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3921.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3921.txt","https://www.rfc-editor.org/rfc/rfc3921.pdf"],"folder":"IETF/RFC-3921","files":{"txt":{"path":"standards/IETF/RFC-3921/RFC-3921.txt","sha256":"0b77384bb7506d66b1ef366391fa89cf843b8796b0bc09fdb56fcd89e47e2e2a"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes extensions to and applications of the core\n features of the Extensible Messaging and Presence Protocol (XMPP)\n that provide the basic instant messaging (IM) and presence\n functionality defined in RFC 2779.\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 3921 XMPP IM October 2004","scope_keywords":["3921","attribute","attributes","key","management","presentation","qualified","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4854","folder":"IETF/RFC-4854","source":"IETF/RFC-4854/RFC-4854.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 3921 This memo describes extensions to and applications of the core\n features of the Extensible Messaging and Presence Protocol (XMPP)\n that provide the basic instant messaging (IM) and presence\n functionality defined in RFC 2779.\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 3921 XMPP IM October 2004 3921 attribute attributes key management presentation qualified tls nested-reference unchanged"},{"id":"IETF RFC 6561","type":"specification","body":"IETF","designation":"RFC 6561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6561.txt","https://www.rfc-editor.org/rfc/rfc6561.pdf"],"folder":"IETF/RFC-6561","files":{"txt":{"path":"standards/IETF/RFC-6561/RFC-6561.txt","sha256":"2e5ca58538e35a8e93682935548ecc8e8e0a60763c3336d90b71abd18106a8c5"}},"tags":["nested-reference","unchanged"],"summary":"This document contains recommendations on how Internet Service\n Providers can use various remediation techniques to manage the\n effects of malicious bot infestations on computers used by their\n subscribers. Internet users with infected computers are exposed to\n risks such as loss of personal data and increased susceptibility to\n online fraud. Such computers can also become inadvertent\n participants in or components of an online crime network, spam\n network, and/or phishing network as well as be used as a part of a\n distributed denial-of-service attack. Mitigating the effects of and\n remediating the installations of malicious bots will make it more\n difficult for botnets to operate and could reduce the level of online\n crime on the Internet in general and/or on a particular Internet\n Service Provider's network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specif","scope_keywords":["6561","http","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6561 This document contains recommendations on how Internet Service\n Providers can use various remediation techniques to manage the\n effects of malicious bot infestations on computers used by their\n subscribers. Internet users with infected computers are exposed to\n risks such as loss of personal data and increased susceptibility to\n online fraud. Such computers can also become inadvertent\n participants in or components of an online crime network, spam\n network, and/or phishing network as well as be used as a part of a\n distributed denial-of-service attack. Mitigating the effects of and\n remediating the installations of malicious bots will make it more\n difficult for botnets to operate and could reduce the level of online\n crime on the Internet in general and/or on a particular Internet\n Service Provider's network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specif 6561 http key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 146","type":"specification","body":"IETF","designation":"RFC 146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc146.txt","https://www.rfc-editor.org/rfc/rfc146.pdf"],"folder":"IETF/RFC-146","files":{"txt":{"path":"standards/IETF/RFC-146/RFC-146.txt","sha256":"2b902457bdba36e34b3e4c4f0933edfa605f2b4a4e9795f5b1faeffb73b997fd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working, Group P.M. Karp, MITRE\nRequest for Comments #146 D.B. McKay, IBM\nNIC 6742 D.C. Wood, MITRE\n 12 May 1971\n\nCategories: D.4, D.7\nObsoletes: none\nUpdates: none\n\n Views on Issues Relevant to Data Sharing\n on Computer Networks\n\nIntroduction\n\nThe formation of a committee to address the problems of achieving\ndata sharing on the ARPA Network, as suggested by Arie Shoshani\n(RFC #140) is desirable at this point of network development. We\nconcur with Shoshani's ideas (presented in an introductory paper\nto the network data sharing meeting, scheduled for Tuesday, May 18)\nand believe that purpose of the committee should be -\n\n a) to classify the issues involved and to propose various\n approaches;\n\n b) to integrate the hitherto independent network activities\n that address problems in the area of data sharing, and;\n\n c) to set up and coordinate appropriate experiments to test\n the servic","scope_keywords":["146","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 173","folder":"IETF/RFC-173","source":"IETF/RFC-173/RFC-173.txt","version":null}],"search_text":"IETF RFC 146 Network Working, Group P.M. Karp, MITRE\nRequest for Comments #146 D.B. McKay, IBM\nNIC 6742 D.C. Wood, MITRE\n 12 May 1971\n\nCategories: D.4, D.7\nObsoletes: none\nUpdates: none\n\n Views on Issues Relevant to Data Sharing\n on Computer Networks\n\nIntroduction\n\nThe formation of a committee to address the problems of achieving\ndata sharing on the ARPA Network, as suggested by Arie Shoshani\n(RFC #140) is desirable at this point of network development. We\nconcur with Shoshani's ideas (presented in an introductory paper\nto the network data sharing meeting, scheduled for Tuesday, May 18)\nand believe that purpose of the committee should be -\n\n a) to classify the issues involved and to propose various\n approaches;\n\n b) to integrate the hitherto independent network activities\n that address problems in the area of data sharing, and;\n\n c) to set up and coordinate appropriate experiments to test\n the servic 146 management nested-reference unchanged"},{"id":"IETF RFC 173","type":"specification","body":"IETF","designation":"RFC 173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc173.txt","https://www.rfc-editor.org/rfc/rfc173.pdf"],"folder":"IETF/RFC-173","files":{"txt":{"path":"standards/IETF/RFC-173/RFC-173.txt","sha256":"9e896921cb626f47d739703a6d23ae4317da18a98e51c0003da7b44a896355f7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. M. Karp - MITRE\nRequest for Comments #173 D. B. McKay - IBM\nNIC 6795 4 June 1971\n\nCategories: D.4, D.7\nObsoletes: None\nUpdates: None\n\n Network Data Management Committee Meeting Announcement\n\nThe data management discussions at the recent NWG meeting resulted in\nthe formation of a Network Data Management Committee to be chaired by\nDoug McKay, IBM. The purpose of the committee, as stated in RFC 146,\nis:\n\n (a) to classify the issues involved and to propose\n various approaches;\n (b) to integrate the hitherto independent network\n activities that address problems in the area of data\n sharing; and\n (c) to set up and coordinate appropriate experiments\n to test the services developed and to evaluate\n alternative approaches.\n\nAn informal meeting was held Wednesday morning, 19 May to estab- lish an\napproach for achieving the above objectives. The attendees were:\n\n Peggy Karp","scope_keywords":["173","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null}],"search_text":"IETF RFC 173 Network Working Group P. M. Karp - MITRE\nRequest for Comments #173 D. B. McKay - IBM\nNIC 6795 4 June 1971\n\nCategories: D.4, D.7\nObsoletes: None\nUpdates: None\n\n Network Data Management Committee Meeting Announcement\n\nThe data management discussions at the recent NWG meeting resulted in\nthe formation of a Network Data Management Committee to be chaired by\nDoug McKay, IBM. The purpose of the committee, as stated in RFC 146,\nis:\n\n (a) to classify the issues involved and to propose\n various approaches;\n (b) to integrate the hitherto independent network\n activities that address problems in the area of data\n sharing; and\n (c) to set up and coordinate appropriate experiments\n to test the services developed and to evaluate\n alternative approaches.\n\nAn informal meeting was held Wednesday morning, 19 May to estab- lish an\napproach for achieving the above objectives. The attendees were:\n\n Peggy Karp 173 management presentation nested-reference unchanged"},{"id":"IETF RFC 1520","type":"specification","body":"IETF","designation":"RFC 1520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1520.txt","https://www.rfc-editor.org/rfc/rfc1520.pdf"],"folder":"IETF/RFC-1520","files":{"txt":{"path":"standards/IETF/RFC-1520/RFC-1520.txt","sha256":"24cb97b08a5b6e4cba5701ed22457b2ee53a352cb4022639e081df83a4dd13a3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1520 T.J. Watson Research Center, IBM Corp.\nCategory: Informational C. Topolcic\n CNRI\n September 1993\n\n Exchanging Routing Information Across Provider Boundaries\n in the CIDR Environment\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n1. Introduction\n\n Classless Inter-Domain Routing (CIDR) has been adopted as a solution\n to the scaling problem in the Internet. The overall CIDR architecture\n is described in [1]. The architecture for IP address assignment with\n CIDR is covered in [2] and [3]. The inter-domain routing protocols\n that are capable of supporting CIDR are covered in [4], [5], and [6].\n\n The purpose of this document is twofold. First, it describes various\n alternatives for exchanging inter-domain routing inf","scope_keywords":["1520"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1520 Network Working Group Y. Rekhter\nRequest for Comments: 1520 T.J. Watson Research Center, IBM Corp.\nCategory: Informational C. Topolcic\n CNRI\n September 1993\n\n Exchanging Routing Information Across Provider Boundaries\n in the CIDR Environment\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\n1. Introduction\n\n Classless Inter-Domain Routing (CIDR) has been adopted as a solution\n to the scaling problem in the Internet. The overall CIDR architecture\n is described in [1]. The architecture for IP address assignment with\n CIDR is covered in [2] and [3]. The inter-domain routing protocols\n that are capable of supporting CIDR are covered in [4], [5], and [6].\n\n The purpose of this document is twofold. First, it describes various\n alternatives for exchanging inter-domain routing inf 1520 nested-reference unchanged"},{"id":"IETF RFC 1597","type":"specification","body":"IETF","designation":"RFC 1597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1597.txt","https://www.rfc-editor.org/rfc/rfc1597.pdf"],"folder":"IETF/RFC-1597","files":{"txt":{"path":"standards/IETF/RFC-1597/RFC-1597.txt","sha256":"48803f5755891450656bc87aaa9802d51a509dfe3c6a33f24a5e8756bbbd05ae"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1597 T.J. Watson Research Center, IBM Corp.\nCategory: Informational B. Moskowitz\n Chrysler Corp.\n D. Karrenberg\n RIPE NCC\n G. de Groot\n RIPE NCC\n March 1994\n\n Address Allocation for Private Internets\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This RFC describes methods to preserve IP address space by not\n allocating globally unique IP addresses to hosts private to an\n enterprise while still permitting full network layer connectivity\n between all hosts inside an enterprise as well as between all public\n hosts of different enterprises. The authors hope, that using these\n methods, significant savings can be made on allocating IP address\n space.\n\n For the purposes of this memo, a","scope_keywords":["1597"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1627","folder":"IETF/RFC-1627","source":"IETF/RFC-1627/RFC-1627.txt","version":null},{"body":"IETF","designation":"RFC 1631","folder":"IETF/RFC-1631","source":"IETF/RFC-1631/RFC-1631.txt","version":null},{"body":"IETF","designation":"RFC 1687","folder":"IETF/RFC-1687","source":"IETF/RFC-1687/RFC-1687.txt","version":null},{"body":"IETF","designation":"RFC 1814","folder":"IETF/RFC-1814","source":"IETF/RFC-1814/RFC-1814.txt","version":null},{"body":"IETF","designation":"RFC 1879","folder":"IETF/RFC-1879","source":"IETF/RFC-1879/RFC-1879.txt","version":null},{"body":"IETF","designation":"RFC 1887","folder":"IETF/RFC-1887","source":"IETF/RFC-1887/RFC-1887.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1919","folder":"IETF/RFC-1919","source":"IETF/RFC-1919/RFC-1919.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2341","folder":"IETF/RFC-2341","source":"IETF/RFC-2341/RFC-2341.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null}],"search_text":"IETF RFC 1597 Network Working Group Y. Rekhter\nRequest for Comments: 1597 T.J. Watson Research Center, IBM Corp.\nCategory: Informational B. Moskowitz\n Chrysler Corp.\n D. Karrenberg\n RIPE NCC\n G. de Groot\n RIPE NCC\n March 1994\n\n Address Allocation for Private Internets\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This RFC describes methods to preserve IP address space by not\n allocating globally unique IP addresses to hosts private to an\n enterprise while still permitting full network layer connectivity\n between all hosts inside an enterprise as well as between all public\n hosts of different enterprises. The authors hope, that using these\n methods, significant savings can be made on allocating IP address\n space.\n\n For the purposes of this memo, a 1597 nested-reference unchanged"},{"id":"IETF RFC 1814","type":"specification","body":"IETF","designation":"RFC 1814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1814.txt","https://www.rfc-editor.org/rfc/rfc1814.pdf"],"folder":"IETF/RFC-1814","files":{"txt":{"path":"standards/IETF/RFC-1814/RFC-1814.txt","sha256":"203ee676c0c8ee9842f9d5bbb955ade50708feb68edef2321983f1fbc849d37d"}},"tags":["nested-reference","unchanged"],"summary":"The IAB suggests that while RFC 1597 establishes reserved IP address\n space for the use of private networks which are isolated and will\n remain isolated from the Internet, any enterprise which anticipates\n external connectivity to the Internet should apply for a globally\n unique address from an Internet registry or service provider.","scope_keywords":["1814","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null}],"search_text":"IETF RFC 1814 The IAB suggests that while RFC 1597 establishes reserved IP address\n space for the use of private networks which are isolated and will\n remain isolated from the Internet, any enterprise which anticipates\n external connectivity to the Internet should apply for a globally\n unique address from an Internet registry or service provider. 1814 management nested-reference unchanged"},{"id":"IETF RFC 1918","type":"specification","body":"IETF","designation":"RFC 1918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1918.txt","https://www.rfc-editor.org/rfc/rfc1918.pdf"],"folder":"IETF/RFC-1918","files":{"txt":{"path":"standards/IETF/RFC-1918/RFC-1918.txt","sha256":"56c43465298772bc4d899923f1785b7b7bf8dd2c9f2f9a53422800ddc5cf9337"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1918 Cisco Systems\nObsoletes: 1627, 1597 B. Moskowitz\nBCP: 5 Chrysler Corp.\nCategory: Best Current Practice D. Karrenberg\n RIPE NCC\n G. J. de Groot\n RIPE NCC\n E. Lear\n Silicon Graphics, Inc.\n February 1996\n\n Address Allocation for Private Internets\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n1. Introduction\n\n For the purposes of this document, an enterprise is an entity\n autonomously operating a network using TCP/IP and in particular\n determining the addressing plan and address assignments within that\n network.\n\n This document describes address allocation for private internets. The\n allocation permits full network layer connectivity among all hosts\n inside an enterprise","scope_keywords":["1918"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2050","folder":"IETF/RFC-2050","source":"IETF/RFC-2050/RFC-2050.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2267","folder":"IETF/RFC-2267","source":"IETF/RFC-2267/RFC-2267.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2647","folder":"IETF/RFC-2647","source":"IETF/RFC-2647/RFC-2647.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2827","folder":"IETF/RFC-2827","source":"IETF/RFC-2827/RFC-2827.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3809","folder":"IETF/RFC-3809","source":"IETF/RFC-3809/RFC-3809.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 3882","folder":"IETF/RFC-3882","source":"IETF/RFC-3882/RFC-3882.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4016","folder":"IETF/RFC-4016","source":"IETF/RFC-4016/RFC-4016.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5635","folder":"IETF/RFC-5635","source":"IETF/RFC-5635/RFC-5635.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6304","folder":"IETF/RFC-6304","source":"IETF/RFC-6304/RFC-6304.txt","version":null},{"body":"IETF","designation":"RFC 6305","folder":"IETF/RFC-6305","source":"IETF/RFC-6305/RFC-6305.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6832","folder":"IETF/RFC-6832","source":"IETF/RFC-6832/RFC-6832.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7793","folder":"IETF/RFC-7793","source":"IETF/RFC-7793/RFC-7793.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 1918 Network Working Group Y. Rekhter\nRequest for Comments: 1918 Cisco Systems\nObsoletes: 1627, 1597 B. Moskowitz\nBCP: 5 Chrysler Corp.\nCategory: Best Current Practice D. Karrenberg\n RIPE NCC\n G. J. de Groot\n RIPE NCC\n E. Lear\n Silicon Graphics, Inc.\n February 1996\n\n Address Allocation for Private Internets\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n1. Introduction\n\n For the purposes of this document, an enterprise is an entity\n autonomously operating a network using TCP/IP and in particular\n determining the addressing plan and address assignments within that\n network.\n\n This document describes address allocation for private internets. The\n allocation permits full network layer connectivity among all hosts\n inside an enterprise 1918 nested-reference unchanged"},{"id":"IETF RFC 2050","type":"specification","body":"IETF","designation":"RFC 2050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2050.txt","https://www.rfc-editor.org/rfc/rfc2050.pdf"],"folder":"IETF/RFC-2050","files":{"txt":{"path":"standards/IETF/RFC-2050/RFC-2050.txt","sha256":"3470816c1f46e1a4bb702b2bd136e90ef2803bb66eb48ec0a378a22bae289d02"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registry system for the distribution of\n globally unique Internet address space and registry operations.\n Particularly this document describes the rules and guidelines\n governing the distribution of this address space.\n\n This document describes the IP assignment policies currently used by\n the Regional Registries to implement the guidelines developed by the\n IANA. The guidelines and these policies are subject to revision at\n the direction of the IANA. The registry working group (IRE WG) will\n be discussing these issues and may provide advice to the IANA about\n possible revisions.\n\n This document replaces RFC 1466, with all the guidelines and\n procedures updated and modified in the light of experience.\n\nHubbard, et. al. Best Current Practice [Page 1]\n\f\nRFC 2050 Internet Registry IP Allocation Guidelines November 1996\n\n This document does not describe private In","scope_keywords":["2050","policies","policy","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null}],"search_text":"IETF RFC 2050 This document describes the registry system for the distribution of\n globally unique Internet address space and registry operations.\n Particularly this document describes the rules and guidelines\n governing the distribution of this address space.\n\n This document describes the IP assignment policies currently used by\n the Regional Registries to implement the guidelines developed by the\n IANA. The guidelines and these policies are subject to revision at\n the direction of the IANA. The registry working group (IRE WG) will\n be discussing these issues and may provide advice to the IANA about\n possible revisions.\n\n This document replaces RFC 1466, with all the guidelines and\n procedures updated and modified in the light of experience.\n\nHubbard, et. al. Best Current Practice [Page 1]\n\f\nRFC 2050 Internet Registry IP Allocation Guidelines November 1996\n\n This document does not describe private In 2050 policies policy presentation subject nested-reference unchanged"},{"id":"IETF RFC 2073","type":"specification","body":"IETF","designation":"RFC 2073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2073.txt","https://www.rfc-editor.org/rfc/rfc2073.pdf"],"folder":"IETF/RFC-2073","files":{"txt":{"path":"standards/IETF/RFC-2073/RFC-2073.txt","sha256":"64bebdf6468b90b3f130eaa79467b06a7fd39ee12ab0c23af4012c2292158a69"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 2073 cisco\nCategory: Standards Track P. Lothberg\n STUPI.AB\n R. Hinden\n Ipsilon Networks\n S. Deering\n Xerox PARC\n J. Postel\n ISI\n Editors\n January 1997\n\n An IPv6 Provider-Based Unicast Address Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n This document defines an IPv6 provider-based unicast address format\n for use in the Internet. The address format defined in this document\n is consistent with the \"IPv6 Addressing Architecture\" [ARCH] and the\n \"An Architecture for IPv6 Unicast Address Allocation\" ","scope_keywords":["2073","algorithm","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 2073 Network Working Group Y. Rekhter\nRequest for Comments: 2073 cisco\nCategory: Standards Track P. Lothberg\n STUPI.AB\n R. Hinden\n Ipsilon Networks\n S. Deering\n Xerox PARC\n J. Postel\n ISI\n Editors\n January 1997\n\n An IPv6 Provider-Based Unicast Address Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1.0 Introduction\n\n This document defines an IPv6 provider-based unicast address format\n for use in the Internet. The address format defined in this document\n is consistent with the \"IPv6 Addressing Architecture\" [ARCH] and the\n \"An Architecture for IPv6 Unicast Address Allocation\"  2073 algorithm management qualified nested-reference unchanged"},{"id":"IETF RFC 1992","type":"specification","body":"IETF","designation":"RFC 1992","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1992.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1992.txt","https://www.rfc-editor.org/rfc/rfc1992.pdf"],"folder":"IETF/RFC-1992","files":{"txt":{"path":"standards/IETF/RFC-1992/RFC-1992.txt","sha256":"ad31654419f1d381f7455d4ea7e7ebf777c51e67ce6e189d80c5f01f87c36981"}},"tags":["nested-reference","unchanged"],"summary":"We present a scalable internetwork routing architecture, called\n Nimrod. The Nimrod architecture is designed to accommodate a dynamic\n internetwork of arbitrary size with heterogeneous service\n requirements and restrictions and to admit incremental deployment\n throughout an internetwork. The key to Nimrod's scalability is its\n ability to represent and manipulate routing-related information at\n multiple levels of abstraction.","scope_keywords":["1992","attribute","attributes","key","path","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1992 We present a scalable internetwork routing architecture, called\n Nimrod. The Nimrod architecture is designed to accommodate a dynamic\n internetwork of arbitrary size with heterogeneous service\n requirements and restrictions and to admit incremental deployment\n throughout an internetwork. The key to Nimrod's scalability is its\n ability to represent and manipulate routing-related information at\n multiple levels of abstraction. 1992 attribute attributes key path policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 2154","type":"specification","body":"IETF","designation":"RFC 2154","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2154.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2154.txt","https://www.rfc-editor.org/rfc/rfc2154.pdf"],"folder":"IETF/RFC-2154","files":{"txt":{"path":"standards/IETF/RFC-2154/RFC-2154.txt","sha256":"71a2a5bfe4ca393bcb4e06330a8c691145fbefe3504b01d097e61e71d35986e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the extensions to OSPF required to add digital\n signature authentication to Link State data, and to provide a\n certification mechanism for router data. Added LSA processing and\n key management is detailed. A method for migration from, or co-\n existence with, standard OSPF V2 is described.","scope_keywords":["2154","algorithm","algorithms","authentication","certificate","hash","key","keys","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null}],"search_text":"IETF RFC 2154 This memo describes the extensions to OSPF required to add digital\n signature authentication to Link State data, and to provide a\n certification mechanism for router data. Added LSA processing and\n key management is detailed. A method for migration from, or co-\n existence with, standard OSPF V2 is described. 2154 algorithm algorithms authentication certificate hash key keys management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 2098","type":"specification","body":"IETF","designation":"RFC 2098","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2098.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2098.txt","https://www.rfc-editor.org/rfc/rfc2098.pdf"],"folder":"IETF/RFC-2098","files":{"txt":{"path":"standards/IETF/RFC-2098/RFC-2098.txt","sha256":"18c83d09dfc746c8e04a63ebd3c14942773236ea71d8737d96397b8d2938d3d9"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a new internetworking architecture which makes\n better use of the property of ATM. IP datagrams are transferred\n along hop-by-hop path via routers, but datagram assembly/disassembly\n and IP header processing are not necessarily carried out at\n individual routers in the proposed architecture. A concept of \"Cell\n Switch Router (CSR)\" is introduced as a new internetworking\n equipment, which has ATM cell switching capabilities in addition to\n conventional IP datagram forwarding. Proposed architecture can\n provide applications with high-throughput and low-latency ATM pipes\n while retaining current router-based internetworking concept. It\n also provides applications with specific QoS/bandwidth by cooperating\n with internetworking level resource reservation protocols such as\n RSVP.\n\n1. Introduction\n\n The Internet is growing both in its size and its traffic volume. In\n additi","scope_keywords":["2098","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null}],"search_text":"IETF RFC 2098 This memo describes a new internetworking architecture which makes\n better use of the property of ATM. IP datagrams are transferred\n along hop-by-hop path via routers, but datagram assembly/disassembly\n and IP header processing are not necessarily carried out at\n individual routers in the proposed architecture. A concept of \"Cell\n Switch Router (CSR)\" is introduced as a new internetworking\n equipment, which has ATM cell switching capabilities in addition to\n conventional IP datagram forwarding. Proposed architecture can\n provide applications with high-throughput and low-latency ATM pipes\n while retaining current router-based internetworking concept. It\n also provides applications with specific QoS/bandwidth by cooperating\n with internetworking level resource reservation protocols such as\n RSVP.\n\n1. Introduction\n\n The Internet is growing both in its size and its traffic volume. In\n additi 2098 path policy nested-reference unchanged"},{"id":"IETF RFC 2212","type":"specification","body":"IETF","designation":"RFC 2212","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2212.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2212.txt","https://www.rfc-editor.org/rfc/rfc2212.pdf"],"folder":"IETF/RFC-2212","files":{"txt":{"path":"standards/IETF/RFC-2212/RFC-2212.txt","sha256":"e3930fa93494b09a8e5645e5d51b5f3be0a702a56b9eb32729d2259a3e03d023"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the network element behavior required to deliver\n a guaranteed service (guaranteed delay and bandwidth) in the\n Internet. Guaranteed service provides firm (mathematically provable)\n bounds on end-to-end datagram queueing delays. This service makes it\n possible to provide a service that guarantees both delay and\n bandwidth. This specification follows the service specification\n template described in [1].","scope_keywords":["2212","delivery","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2638","folder":"IETF/RFC-2638","source":"IETF/RFC-2638/RFC-2638.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 2212 This memo describes the network element behavior required to deliver\n a guaranteed service (guaranteed delay and bandwidth) in the\n Internet. Guaranteed service provides firm (mathematically provable)\n bounds on end-to-end datagram queueing delays. This service makes it\n possible to provide a service that guarantees both delay and\n bandwidth. This specification follows the service specification\n template described in [1]. 2212 delivery key management path subject nested-reference unchanged"},{"id":"IETF RFC 2363","type":"specification","body":"IETF","designation":"RFC 2363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2363.txt","https://www.rfc-editor.org/rfc/rfc2363.pdf"],"folder":"IETF/RFC-2363","files":{"txt":{"path":"standards/IETF/RFC-2363/RFC-2363.txt","sha256":"2c89ba9e86557fa747e043b4cfb658dcb7d3c0f47f6da16b0d4cdbad7ebd272b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Gross\nRequest for Comments: 2363 Lucent Technologies\nCategory: Standards Track M. Kaycee\n Paradyne\n A. Li\n Shasta Networks\n A. Malis\n Ascend Communications\n J. Stephens\n Cayman Systems\n July 1998\n\n PPP Over FUNI\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Frame User Network Interface","scope_keywords":["2363","authentication","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2363 Network Working Group G. Gross\nRequest for Comments: 2363 Lucent Technologies\nCategory: Standards Track M. Kaycee\n Paradyne\n A. Li\n Shasta Networks\n A. Malis\n Ascend Communications\n J. Stephens\n Cayman Systems\n July 1998\n\n PPP Over FUNI\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Frame User Network Interface 2363 authentication delivery key nested-reference unchanged"},{"id":"IETF RFC 2364","type":"specification","body":"IETF","designation":"RFC 2364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2364.txt","https://www.rfc-editor.org/rfc/rfc2364.pdf"],"folder":"IETF/RFC-2364","files":{"txt":{"path":"standards/IETF/RFC-2364/RFC-2364.txt","sha256":"2e30e73ec9b373312999db842035ee8f015d3ba4e75511b9b0d79e02fdfae017"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Gross\nRequest for Comments: 2364 Lucent Technologies\nCategory: Standards Track M. Kaycee\n Paradyne\n A. Lin\n Shasta Networks\n A. Malis\n Ascend Communications\n J. Stephens\n Cayman Systems\n July 1998\n\n PPP Over AAL5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Adaptation Layer 5 (AAL5) f","scope_keywords":["2364","authentication","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null}],"search_text":"IETF RFC 2364 Network Working Group G. Gross\nRequest for Comments: 2364 Lucent Technologies\nCategory: Standards Track M. Kaycee\n Paradyne\n A. Lin\n Shasta Networks\n A. Malis\n Ascend Communications\n J. Stephens\n Cayman Systems\n July 1998\n\n PPP Over AAL5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Adaptation Layer 5 (AAL5) f 2364 authentication delivery key nested-reference unchanged"},{"id":"IETF RFC 2380","type":"specification","body":"IETF","designation":"RFC 2380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2380.txt","https://www.rfc-editor.org/rfc/rfc2380.pdf"],"folder":"IETF/RFC-2380","files":{"txt":{"path":"standards/IETF/RFC-2380/RFC-2380.txt","sha256":"2082d9e38d5b13f1cd35d1914f4c2b039812b9c0757e0470a3dbcaf07610b83a"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents specific implementation requirements for running\n RSVP over ATM switched virtual circuits (SVCs). It presents\n requirements that ensure interoperability between multiple\n implementations and conformance to the RSVP and Integrated Services\n specifications. A separate document [5] provides specific guidelines\n for running over today's ATM networks. The general problem is\n discussed in [9]. Integrated Services to ATM service mappings are\n covered in [6]. The full set of documents present the background and\n information needed to implement Integrated Services and RSVP over\n ATM.","scope_keywords":["2380","identification","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null}],"search_text":"IETF RFC 2380 This memo presents specific implementation requirements for running\n RSVP over ATM switched virtual circuits (SVCs). It presents\n requirements that ensure interoperability between multiple\n implementations and conformance to the RSVP and Integrated Services\n specifications. A separate document [5] provides specific guidelines\n for running over today's ATM networks. The general problem is\n discussed in [9]. Integrated Services to ATM service mappings are\n covered in [6]. The full set of documents present the background and\n information needed to implement Integrated Services and RSVP over\n ATM. 2380 identification key management path nested-reference unchanged"},{"id":"IETF RFC 2381","type":"specification","body":"IETF","designation":"RFC 2381","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2381.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2381.txt","https://www.rfc-editor.org/rfc/rfc2381.pdf"],"folder":"IETF/RFC-2381","files":{"txt":{"path":"standards/IETF/RFC-2381/RFC-2381.txt","sha256":"dff8d740620cbc760353e4e96d99ca905e8e974680bc4a7b3cb6213dc2b5745d"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for mapping service classes, and\n traffic management features and parameters between Internet and ATM\n technologies. The service mappings are useful for providing\n effective interoperation and end-to-end Quality of Service for IP\n Integrated Services networks containing ATM subnetworks.\n\n The discussion and specifications given here support the IP\n integrated services protocols for Guaranteed Service (GS),\n Controlled-Load Service (CLS) and the ATM Forum UNI specification,\n versions 3.0, 3.1 and 4.0. Some discussion of IP best effort service\n over ATM is also included.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [1]. (Note,\n in many cases the use of \"MUST\" or \"REQUIRED\" reflects our\n interpretation of th","scope_keywords":["2381","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2381 This document provides guidelines for mapping service classes, and\n traffic management features and parameters between Internet and ATM\n technologies. The service mappings are useful for providing\n effective interoperation and end-to-end Quality of Service for IP\n Integrated Services networks containing ATM subnetworks.\n\n The discussion and specifications given here support the IP\n integrated services protocols for Guaranteed Service (GS),\n Controlled-Load Service (CLS) and the ATM Forum UNI specification,\n versions 3.0, 3.1 and 4.0. Some discussion of IP best effort service\n over ATM is also included.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [1]. (Note,\n in many cases the use of \"MUST\" or \"REQUIRED\" reflects our\n interpretation of th 2381 key management path nested-reference unchanged"},{"id":"IETF RFC 2382","type":"specification","body":"IETF","designation":"RFC 2382","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2382.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2382.txt","https://www.rfc-editor.org/rfc/rfc2382.pdf"],"folder":"IETF/RFC-2382","files":{"txt":{"path":"standards/IETF/RFC-2382/RFC-2382.txt","sha256":"ecbb0ff8975f9bc635bde32b57972ef6de0e40f89447c2dc5951f14eebf8ef67"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines the issues and framework related to providing\n IP Integrated Services with RSVP over ATM. It provides an overall\n approach to the problem(s) and related issues. These issues and\n problems are to be addressed in further documents from the ISATM\n subgroup of the ISSLL working group.\n\n1. Introduction\n\n The Internet currently has one class of service normally referred to\n as \"best effort.\" This service is typified by first-come, first-\n serve scheduling at each hop in the network. Best effort service has\n worked well for electronic mail, World Wide Web (WWW) access, file\n transfer (e.g. ftp), etc. For real-time traffic such as voice and\n video, the current Internet has performed well only across unloaded\n portions of the network. In order to provide quality real-time\n traffic, new classes of service and a QoS signalling protocol are\n\nCrawley, et. al. Informational [Pag","scope_keywords":["2382","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null}],"search_text":"IETF RFC 2382 This document outlines the issues and framework related to providing\n IP Integrated Services with RSVP over ATM. It provides an overall\n approach to the problem(s) and related issues. These issues and\n problems are to be addressed in further documents from the ISATM\n subgroup of the ISSLL working group.\n\n1. Introduction\n\n The Internet currently has one class of service normally referred to\n as \"best effort.\" This service is typified by first-come, first-\n serve scheduling at each hop in the network. Best effort service has\n worked well for electronic mail, World Wide Web (WWW) access, file\n transfer (e.g. ftp), etc. For real-time traffic such as voice and\n video, the current Internet has performed well only across unloaded\n portions of the network. In order to provide quality real-time\n traffic, new classes of service and a QoS signalling protocol are\n\nCrawley, et. al. Informational [Pag 2382 key management nested-reference unchanged"},{"id":"IETF RFC 2492","type":"specification","body":"IETF","designation":"RFC 2492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2492.txt","https://www.rfc-editor.org/rfc/rfc2492.pdf"],"folder":"IETF/RFC-2492","files":{"txt":{"path":"standards/IETF/RFC-2492/RFC-2492.txt","sha256":"b17830b2264efc3662f89fca8771c32ec67ef678c328eb2a6d7783297d528486"}},"tags":["nested-reference","unchanged"],"summary":"This document is a companion to the ION working group's architecture\n document, \"IPv6 over Non Broadcast Multiple Access (NBMA) networks\".\n It provides specific details on how to apply the IPv6 over NBMA\n architecture to ATM networks. This architecture allows conventional\n host-side operation of the IPv6 Neighbor Discovery protocol, while\n also supporting the establishment of 'shortcut' ATM forwarding paths\n (when using SVCs). Operation over administratively configured Point\n to Point PVCs is also supported.\n\n1. Introduction.\n\n This document is an ATM-specific companion document to the ION\n working group's, \"IPv6 over Non Broadcast Multiple Access (NBMA)\n networks\" specification [1]. Terminology and architectural\n descriptions will not be repeated here.\n\n The use of ATM to provide point to point PVC service, or flexible\n point to point and point to multipoint SVC service, is covered by\n ","scope_keywords":["2492","key","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2492 This document is a companion to the ION working group's architecture\n document, \"IPv6 over Non Broadcast Multiple Access (NBMA) networks\".\n It provides specific details on how to apply the IPv6 over NBMA\n architecture to ATM networks. This architecture allows conventional\n host-side operation of the IPv6 Neighbor Discovery protocol, while\n also supporting the establishment of 'shortcut' ATM forwarding paths\n (when using SVCs). Operation over administratively configured Point\n to Point PVCs is also supported.\n\n1. Introduction.\n\n This document is an ATM-specific companion document to the ION\n working group's, \"IPv6 over Non Broadcast Multiple Access (NBMA)\n networks\" specification [1]. Terminology and architectural\n descriptions will not be repeated here.\n\n The use of ATM to provide point to point PVC service, or flexible\n point to point and point to multipoint SVC service, is covered by\n  2492 key path pid nested-reference unchanged"},{"id":"IETF RFC 1484","type":"specification","body":"IETF","designation":"RFC 1484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1484.txt","https://www.rfc-editor.org/rfc/rfc1484.pdf"],"folder":"IETF/RFC-1484","files":{"txt":{"path":"standards/IETF/RFC-1484/RFC-1484.txt","sha256":"bbd6882baf9be7960210047d75a859046cb6e905ad73a513801c5b809ad3cd28"}},"tags":["nested-reference","unchanged"],"summary":"The OSI Directory has user friendly naming as a goal. A simple\n minded usage of the directory does not achieve this. Two aspects not\n achieved are:\n\n o A user oriented notation\n\n o Guessability\n\n This proposal sets out some conventions for representing names in a\n friendly manner, and shows how this can be used to achieve really\n friendly naming. This then leads to a specification of a format for\n representing names, and to procedures to resolve them. This leads to\n a specification which allows directory names to be communicated\n between humans. The format in this specification is identical to\n that defined in [HK93], and it is intended that these specifications\n are compatible. Please send comments to the author or to the\n discussion group: <osi-ds@CS.UCL.AC.UK>.\n\nHardcastle-Kille [Page 1]\n\f\nRFC 1484 User Friendly Naming July 1993","scope_keywords":["1484","algorithm","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1485","folder":"IETF/RFC-1485","source":"IETF/RFC-1485/RFC-1485.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null}],"search_text":"IETF RFC 1484 The OSI Directory has user friendly naming as a goal. A simple\n minded usage of the directory does not achieve this. Two aspects not\n achieved are:\n\n o A user oriented notation\n\n o Guessability\n\n This proposal sets out some conventions for representing names in a\n friendly manner, and shows how this can be used to achieve really\n friendly naming. This then leads to a specification of a format for\n representing names, and to procedures to resolve them. This leads to\n a specification which allows directory names to be communicated\n between humans. The format in this specification is identical to\n that defined in [HK93], and it is intended that these specifications\n are compatible. Please send comments to the author or to the\n discussion group: <osi-ds@CS.UCL.AC.UK>.\n\nHardcastle-Kille [Page 1]\n\f\nRFC 1484 User Friendly Naming July 1993 1484 algorithm attribute presentation nested-reference unchanged"},{"id":"IETF RFC 1485","type":"specification","body":"IETF","designation":"RFC 1485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1485.txt","https://www.rfc-editor.org/rfc/rfc1485.pdf"],"folder":"IETF/RFC-1485","files":{"txt":{"path":"standards/IETF/RFC-1485/RFC-1485.txt","sha256":"22fbfe6f95895314f5f7e5f4ad228c8ff3ba7e5ec62911d0b4c421d8a9703d3e"}},"tags":["nested-reference","unchanged"],"summary":"The OSI Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1.\n When a distinguished name is communicated between to users not using a\n directory protocol (e.g., in a mail message), there is a need to have\n a user-oriented string representation of distinguished name. This\n specification defines a string format for representing names, which is\n designed to give a clean representation of commonly used names, whilst\n being able to represent any distinguished name. Please send comments\n to the author or to the discussion group <osi-ds@CS.UCL.AC.UK>.","scope_keywords":["1485","attribute","attributes","key","keys","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1484","folder":"IETF/RFC-1484","source":"IETF/RFC-1484/RFC-1484.txt","version":null},{"body":"IETF","designation":"RFC 1487","folder":"IETF/RFC-1487","source":"IETF/RFC-1487/RFC-1487.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1567","folder":"IETF/RFC-1567","source":"IETF/RFC-1567/RFC-1567.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2659","folder":"IETF/RFC-2659","source":"IETF/RFC-2659/RFC-2659.txt","version":null}],"search_text":"IETF RFC 1485 The OSI Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1.\n When a distinguished name is communicated between to users not using a\n directory protocol (e.g., in a mail message), there is a need to have\n a user-oriented string representation of distinguished name. This\n specification defines a string format for representing names, which is\n designed to give a clean representation of commonly used names, whilst\n being able to represent any distinguished name. Please send comments\n to the author or to the discussion group <osi-ds@CS.UCL.AC.UK>. 1485 attribute attributes key keys path presentation nested-reference unchanged"},{"id":"IETF RFC 3494","type":"specification","body":"IETF","designation":"RFC 3494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3494.txt","https://www.rfc-editor.org/rfc/rfc3494.pdf"],"folder":"IETF/RFC-3494","files":{"txt":{"path":"standards/IETF/RFC-3494/RFC-3494.txt","sha256":"9c1bafa5d0398fe35cc9dd75decee5ab7527ecd19c7afde284553eb3020e7f7b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Zeilenga\nRequest for Comments: 3494 OpenLDAP Foundation\nObsoletes: 1484, 1485, 1487, 1488, 1777, March 2003\n 1778, 1779, 1781, 2559\nCategory: Informational\n\n Lightweight Directory Access Protocol version 2 (LDAPv2)\n to Historic Status\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document recommends the retirement of version 2 of the\n Lightweight Directory Access Protocol (LDAPv2) and other dependent\n specifications, and discusses the reasons for doing so. This\n document recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as\n documents they superseded) be moved to Historic status.\n\nLightweight Directory Access Protocol, version 2","scope_keywords":["3494","attribute","authentication","http","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"IETF RFC 3494 Network Working Group K. Zeilenga\nRequest for Comments: 3494 OpenLDAP Foundation\nObsoletes: 1484, 1485, 1487, 1488, 1777, March 2003\n 1778, 1779, 1781, 2559\nCategory: Informational\n\n Lightweight Directory Access Protocol version 2 (LDAPv2)\n to Historic Status\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document recommends the retirement of version 2 of the\n Lightweight Directory Access Protocol (LDAPv2) and other dependent\n specifications, and discusses the reasons for doing so. This\n document recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as\n documents they superseded) be moved to Historic status.\n\nLightweight Directory Access Protocol, version 2 3494 attribute authentication http key keys presentation nested-reference unchanged"},{"id":"IETF RFC 1959","type":"specification","body":"IETF","designation":"RFC 1959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1959.txt","https://www.rfc-editor.org/rfc/rfc1959.pdf"],"folder":"IETF/RFC-1959","files":{"txt":{"path":"standards/IETF/RFC-1959/RFC-1959.txt","sha256":"5e6f0d1ab7f7c326ca368d51cc264e6979f97c7441b944a653a63f89b32b63e2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 1959 M. Smith\nCategory: Standards Track University of Michigan\n June 1996\n\n An LDAP URL Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n LDAP is the Lightweight Directory Access Protocol, defined in [1] and\n [2]. This document describes a format for an LDAP Uniform Resource\n Locator which will allow Internet clients to have direct access to\n the LDAP protocol. While LDAP currently is used only as a front end\n to the X.500 directory, the URL format described here is general\n enough to handle the case of sta","scope_keywords":["1959","attribute","attributes","credential","credentials","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null}],"search_text":"IETF RFC 1959 Network Working Group T. Howes\nRequest for Comments: 1959 M. Smith\nCategory: Standards Track University of Michigan\n June 1996\n\n An LDAP URL Format\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n LDAP is the Lightweight Directory Access Protocol, defined in [1] and\n [2]. This document describes a format for an LDAP Uniform Resource\n Locator which will allow Internet clients to have direct access to\n the LDAP protocol. While LDAP currently is used only as a front end\n to the X.500 directory, the URL format described here is general\n enough to handle the case of sta 1959 attribute attributes credential credentials presentation nested-reference unchanged"},{"id":"IETF RFC 2659","type":"specification","body":"IETF","designation":"RFC 2659","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2659.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2659.txt","https://www.rfc-editor.org/rfc/rfc2659.pdf"],"folder":"IETF/RFC-2659","files":{"txt":{"path":"standards/IETF/RFC-2659/RFC-2659.txt","sha256":"a135cfa22e9cc5704b7a2e74a4d86aa5a1dae94869a6f4ece8615adb22bc4fab"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a syntax for embedding S-HTTP negotiation\n parameters in HTML documents. S-HTTP, as described by RFC 2660,\n contains the concept of negotiation headers which reflect the\n potential receiver of a message's preferences as to which crypto-\n graphic enhancements should be applied to the message. This document\n describes a syntax for binding these negotiation parameters to HTML\n anchors.\n\n 1. Introduction\n\n 2. Anchor Attributes\n\n We define the following new anchor (and form submission) attributes:\n\n DN -- The distinguished name of the principal for whom the\n request should be encrypted when dereferencing the anchor's url.\n This need not be specified, but failure to do so runs the risk\n that the client will be unable to determine the DN and therefore\n will be unable to encrypt. This should be specified in the form\n of RFC1485, using SGML quoting conventions as needed.\n\n NON","scope_keywords":["2659","algorithm","algorithms","attribute","attributes","certificate","certificates","http","risk","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2659 This memo describes a syntax for embedding S-HTTP negotiation\n parameters in HTML documents. S-HTTP, as described by RFC 2660,\n contains the concept of negotiation headers which reflect the\n potential receiver of a message's preferences as to which crypto-\n graphic enhancements should be applied to the message. This document\n describes a syntax for binding these negotiation parameters to HTML\n anchors.\n\n 1. Introduction\n\n 2. Anchor Attributes\n\n We define the following new anchor (and form submission) attributes:\n\n DN -- The distinguished name of the principal for whom the\n request should be encrypted when dereferencing the anchor's url.\n This need not be specified, but failure to do so runs the risk\n that the client will be unable to determine the DN and therefore\n will be unable to encrypt. This should be specified in the form\n of RFC1485, using SGML quoting conventions as needed.\n\n NON 2659 algorithm algorithms attribute attributes certificate certificates http risk signature nested-reference unchanged"},{"id":"IETF RFC 1568","type":"specification","body":"IETF","designation":"RFC 1568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1568.txt","https://www.rfc-editor.org/rfc/rfc1568.pdf"],"folder":"IETF/RFC-1568","files":{"txt":{"path":"standards/IETF/RFC-1568/RFC-1568.txt","sha256":"acc7328a4ec5bd433c6fee54992182cfba9483686e04217ad326498183f74a6e"}},"tags":["nested-reference","unchanged"],"summary":"This RFC suggests a simple way for delivering both alphanumeric and\n numeric pages (one-way) to radio paging terminals. Gateways\n supporting this protocol, as well as SMTP, have been in use for\n several months in one nationwide paging firm. One other paging firm\n is in the process of adopting it.\n\n Earlier versions of this specification were reviewed by IESG members\n and the IETF's \"822 Extensions\" Working Group. They preferred an\n alternate strategy, as discussed under \"Relationship to Other IETF\n Work\", below.\n\n1. Introduction\n\n Beepers are as much a part of computer nerdom as X-terminals\n (perhaps, unfortunately, more). The intent of Simple Network Paging\n Protocol (SNPP) is to provide a standard whereby pages can be\n delivered to individual paging terminals. The most obvious benefit\n is the elimination of the need for modems to produce alphanumeric\n pages, and the added ease of deliv","scope_keywords":["1568","delivery","pid","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"IETF RFC 1568 This RFC suggests a simple way for delivering both alphanumeric and\n numeric pages (one-way) to radio paging terminals. Gateways\n supporting this protocol, as well as SMTP, have been in use for\n several months in one nationwide paging firm. One other paging firm\n is in the process of adopting it.\n\n Earlier versions of this specification were reviewed by IESG members\n and the IETF's \"822 Extensions\" Working Group. They preferred an\n alternate strategy, as discussed under \"Relationship to Other IETF\n Work\", below.\n\n1. Introduction\n\n Beepers are as much a part of computer nerdom as X-terminals\n (perhaps, unfortunately, more). The intent of Simple Network Paging\n Protocol (SNPP) is to provide a standard whereby pages can be\n delivered to individual paging terminals. The most obvious benefit\n is the elimination of the need for modems to produce alphanumeric\n pages, and the added ease of deliv 1568 delivery pid validation nested-reference unchanged"},{"id":"IETF RFC 1558","type":"specification","body":"IETF","designation":"RFC 1558","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1558.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1558.txt","https://www.rfc-editor.org/rfc/rfc1558.pdf"],"folder":"IETF/RFC-1558","files":{"txt":{"path":"standards/IETF/RFC-1558/RFC-1558.txt","sha256":"348a8defc7464b3ea27b52b5dbba7c27ee6dce7558fa8a8785bcd33e0090b647"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 1558 University of Michigan\nCategory: Informational December 1993\n\n A String Representation of LDAP Search Filters\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Lightweight Directory Access Protocol (LDAP) [1] defines a\n network representation of a search filter transmitted to an LDAP\n server. Some applications may find it useful to have a common way of\n representing these search filters in a human-readable form. This\n document defines a human-readable string format for representing LDAP\n search filters.\n\n1. LDAP Search Filter Definition\n\n An LDAP search filter is defined in [1] as follows:\n\n Filter ::= CHOICE {\n and [0] SET OF Filter,\n or [1] SET OF Filter,\n not [2] Filter,\n equalit","scope_keywords":["1558","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null}],"search_text":"IETF RFC 1558 Network Working Group T. Howes\nRequest for Comments: 1558 University of Michigan\nCategory: Informational December 1993\n\n A String Representation of LDAP Search Filters\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Lightweight Directory Access Protocol (LDAP) [1] defines a\n network representation of a search filter transmitted to an LDAP\n server. Some applications may find it useful to have a common way of\n representing these search filters in a human-readable form. This\n document defines a human-readable string format for representing LDAP\n search filters.\n\n1. LDAP Search Filter Definition\n\n An LDAP search filter is defined in [1] as follows:\n\n Filter ::= CHOICE {\n and [0] SET OF Filter,\n or [1] SET OF Filter,\n not [2] Filter,\n equalit 1558 attribute presentation nested-reference unchanged"},{"id":"IETF RFC 1489","type":"specification","body":"IETF","designation":"RFC 1489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1489.txt","https://www.rfc-editor.org/rfc/rfc1489.pdf"],"folder":"IETF/RFC-1489","files":{"txt":{"path":"standards/IETF/RFC-1489/RFC-1489.txt","sha256":"0dcff97f8cd16341d2ce742cc1a0c345b88857e6bca87f3b6fab894644628352"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Chernov\nRequest for Comments: 1489 RELCOM Development Team\n July 1993\n\n Registration of a Cyrillic Character Set\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n Though the proposed character set \"koi8-r\" is not currently an\n international standard, there is very large user community (including\n Relcom Net) supporting it. Factually, \"koi8-r\" is de-facto standard\n for Unix and global network applications in the former Soviet Union.\n This is the reason the Society of Unix User Groups (SUUG) believes\n \"koi8-r\" should be registered.\n\n MIME character set name: koi8-r\n\n Published specification: This standard is unpublished, but based on\n several published standards: GOST 19768-74 (old-koi8), ISO 6937/8\n (not registered) and variations: IN","scope_keywords":["1489","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1489 Network Working Group A. Chernov\nRequest for Comments: 1489 RELCOM Development Team\n July 1993\n\n Registration of a Cyrillic Character Set\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n Though the proposed character set \"koi8-r\" is not currently an\n international standard, there is very large user community (including\n Relcom Net) supporting it. Factually, \"koi8-r\" is de-facto standard\n for Unix and global network applications in the former Soviet Union.\n This is the reason the Society of Unix User Groups (SUUG) believes\n \"koi8-r\" should be registered.\n\n MIME character set name: koi8-r\n\n Published specification: This standard is unpublished, but based on\n several published standards: GOST 19768-74 (old-koi8), ISO 6937/8\n (not registered) and variations: IN 1489 registered nested-reference unchanged"},{"id":"IETF RFC 1973","type":"specification","body":"IETF","designation":"RFC 1973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1973.txt","https://www.rfc-editor.org/rfc/rfc1973.pdf"],"folder":"IETF/RFC-1973","files":{"txt":{"path":"standards/IETF/RFC-1973/RFC-1973.txt","sha256":"004b96e19de66296a9a9cc7226a3940f3e74b30878aa1ef19fc15957358dc03a"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of Frame Relay for framing PPP\n encapsulated packets.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for PPP, such as the Link Control\n\nSimpson Standards Track [Page i]\n\f\nRFC 1973 PPP in Frame Relay June 1996\n\n Protocol, Network-layer Control Protocols, authentication, and\n compression. These capabilities require a point-to-point\n relationship between peers, and are not designed for multi-point or\n multi-access environments.","scope_keywords":["1973","authentication","delivery","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1973 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of Frame Relay for framing PPP\n encapsulated packets.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for PPP, such as the Link Control\n\nSimpson Standards Track [Page i]\n\f\nRFC 1973 PPP in Frame Relay June 1996\n\n Protocol, Network-layer Control Protocols, authentication, and\n compression. These capabilities require a point-to-point\n relationship between peers, and are not designed for multi-point or\n multi-access environments. 1973 authentication delivery pid presentation nested-reference unchanged"},{"id":"IETF RFC 3070","type":"specification","body":"IETF","designation":"RFC 3070","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3070.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3070.txt","https://www.rfc-editor.org/rfc/rfc3070.pdf"],"folder":"IETF/RFC-3070","files":{"txt":{"path":"standards/IETF/RFC-3070/RFC-3070.txt","sha256":"44c4bc8c65d3f47e5ce5d12bf2d1882dc57876db3c32917f1a3adca5f3555e11"}},"tags":["nested-reference","unchanged"],"summary":"Layer Two Tunneling Protocol (L2TP) describes a mechanism to tunnel\n Point-to-Point (PPP) sessions. The protocol has been designed to be\n independent of the media it runs over. The base specification\n describes how it should be implemented to run over the User Datagram\n Protocol (UDP) and the Internet Protocol (IP). This document\n describes how L2TP is implemented over Frame Relay Permanent Virtual\n Circuits (PVCs) and Switched Virtual Circuits (SVCs).\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for L2TP and applies only to the\n use of Frame Relay pont-to-point circuits.","scope_keywords":["3070","identification","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 3070 Layer Two Tunneling Protocol (L2TP) describes a mechanism to tunnel\n Point-to-Point (PPP) sessions. The protocol has been designed to be\n independent of the media it runs over. The base specification\n describes how it should be implemented to run over the User Datagram\n Protocol (UDP) and the Internet Protocol (IP). This document\n describes how L2TP is implemented over Frame Relay Permanent Virtual\n Circuits (PVCs) and Switched Virtual Circuits (SVCs).\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use facilities which are defined for L2TP and applies only to the\n use of Frame Relay pont-to-point circuits. 3070 identification key pid nested-reference unchanged"},{"id":"IETF RFC 2159","type":"specification","body":"IETF","designation":"RFC 2159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2159.txt","https://www.rfc-editor.org/rfc/rfc2159.pdf"],"folder":"IETF/RFC-2159","files":{"txt":{"path":"standards/IETF/RFC-2159/RFC-2159.txt","sha256":"3dbbf99253a81173573a3aa22794b94837bc3fb93770de6b8f6945cf8d4ef084"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2159 UNINETT\nCategory: Standards Track January 1998\n\n A MIME Body Part for FAX\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document contains the definitions, originally contained in RFC\n 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to\n its X.400 representation.\n\n NOTE: At the moment, this format does not seem appropriate for a\n \"general purpose image format for the Internet\", if such a beas","scope_keywords":["2159","algorithm","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2159 Network Working Group H. Alvestrand\nRequest for Comments: 2159 UNINETT\nCategory: Standards Track January 1998\n\n A MIME Body Part for FAX\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document contains the definitions, originally contained in RFC\n 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to\n its X.400 representation.\n\n NOTE: At the moment, this format does not seem appropriate for a\n \"general purpose image format for the Internet\", if such a beas 2159 algorithm presentation nested-reference unchanged"},{"id":"IETF RFC 2160","type":"specification","body":"IETF","designation":"RFC 2160","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2160.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2160.txt","https://www.rfc-editor.org/rfc/rfc2160.pdf"],"folder":"IETF/RFC-2160","files":{"txt":{"path":"standards/IETF/RFC-2160/RFC-2160.txt","sha256":"03739c74c8995c83f15dd0810c48ed4f344b6a46cd673813134247c800442475"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2160 UNINETT\nCategory: Standards Track January 1998\n\n Carrying PostScript in X.400 and MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ............................................ 1\n 2 The PostScript body part ................................ 1\n 3 The PostScript FTBP ..................................... 2\n 4 The Application/PostScript content-type ................. 2\n 5 MIXER conversion ...........","scope_keywords":["2160","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2160 Network Working Group H. Alvestrand\nRequest for Comments: 2160 UNINETT\nCategory: Standards Track January 1998\n\n Carrying PostScript in X.400 and MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1 Introduction ............................................ 1\n 2 The PostScript body part ................................ 1\n 3 The PostScript FTBP ..................................... 2\n 4 The Application/PostScript content-type ................. 2\n 5 MIXER conversion ........... 2160 presentation nested-reference unchanged"},{"id":"IETF RFC 2158","type":"specification","body":"IETF","designation":"RFC 2158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2158.txt","https://www.rfc-editor.org/rfc/rfc2158.pdf"],"folder":"IETF/RFC-2158","files":{"txt":{"path":"standards/IETF/RFC-2158/RFC-2158.txt","sha256":"b6886d92f0481d5938cf6200b71286502a62e71f69fcfba67dda99394742309b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2158 UNINETT\nCategory: Standards Track January 1998\n\n X.400 Image Body Parts\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document contains the body parts defined in RFC 1495 for\n carrying image formats that were originally defined in MIME through\n an X.400 system.\n\n It also documents the OIDs assigned to these data formats as FTAM\n body parts, which allow the MIME types to be converted to FTAM body\n parts; this ","scope_keywords":["2158"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2158 Network Working Group H. Alvestrand\nRequest for Comments: 2158 UNINETT\nCategory: Standards Track January 1998\n\n X.400 Image Body Parts\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document contains the body parts defined in RFC 1495 for\n carrying image formats that were originally defined in MIME through\n an X.400 system.\n\n It also documents the OIDs assigned to these data formats as FTAM\n body parts, which allow the MIME types to be converted to FTAM body\n parts; this  2158 nested-reference unchanged"},{"id":"IETF RFC 1498","type":"specification","body":"IETF","designation":"RFC 1498","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1498.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1498.txt","https://www.rfc-editor.org/rfc/rfc1498.pdf"],"folder":"IETF/RFC-1498","files":{"txt":{"path":"standards/IETF/RFC-1498/RFC-1498.txt","sha256":"57f4d1b31a08b0b08c1d2414506038a6312a609381fbf62bf0b54d10b684658f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Saltzer\nRequest for Comments: 1498 M.I.T. Laboratory for Computer Science\n August 1993\n\n On the Naming and Binding of Network Destinations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This brief paper offers a perspective on the subject of names of\n destinations in data communication networks. It suggests two ideas:\n First, it is helpful to distinguish among four different kinds of\n objects that may be named as the destination of a packet in a\n network. Second, the operating system concept of binding is a useful\n way to describe the relations among the four kinds of objects. To\n illustrate the usefulness of this approach, the paper interprets some\n more subtle and confusing properties of two real-world network\n systems for naming de","scope_keywords":["1498","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1498 Network Working Group J. Saltzer\nRequest for Comments: 1498 M.I.T. Laboratory for Computer Science\n August 1993\n\n On the Naming and Binding of Network Destinations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nAbstract\n\n This brief paper offers a perspective on the subject of names of\n destinations in data communication networks. It suggests two ideas:\n First, it is helpful to distinguish among four different kinds of\n objects that may be named as the destination of a packet in a\n network. Second, the operating system concept of binding is a useful\n way to describe the relations among the four kinds of objects. To\n illustrate the usefulness of this approach, the paper interprets some\n more subtle and confusing properties of two real-world network\n systems for naming de 1498 path subject nested-reference unchanged"},{"id":"IETF RFC 1507","type":"specification","body":"IETF","designation":"RFC 1507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1507.txt","https://www.rfc-editor.org/rfc/rfc1507.pdf"],"folder":"IETF/RFC-1507","files":{"txt":{"path":"standards/IETF/RFC-1507/RFC-1507.txt","sha256":"92c0b7136350ad89f8f5ab3e0f609eaa1898837988d263078fbac91c4a7ee005"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Kaufman\nRequest for Comments: 1507 Digital Equipment Corporation\n September 1993\n\n DASS\n Distributed Authentication Security Service\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"Internet Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 What is DASS? .......................................... 2\n 1.2 Central Concepts ....................................... 4\n 1.3 What This Document Won't Tell You ..................... 11\n 1.4 The Relationship between DASS and ISO Standards ....... 17\n 1.5 An Authentica","scope_keywords":["1507","algorithm","algorithms","authentication","certificate","credential","credentials","key","seal"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1511","folder":"IETF/RFC-1511","source":"IETF/RFC-1511/RFC-1511.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1507 Network Working Group C. Kaufman\nRequest for Comments: 1507 Digital Equipment Corporation\n September 1993\n\n DASS\n Distributed Authentication Security Service\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard. Discussion and\n suggestions for improvement are requested. Please refer to the\n current edition of the \"Internet Official Protocol Standards\" for the\n standardization state and status of this protocol. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 1.1 What is DASS? .......................................... 2\n 1.2 Central Concepts ....................................... 4\n 1.3 What This Document Won't Tell You ..................... 11\n 1.4 The Relationship between DASS and ISO Standards ....... 17\n 1.5 An Authentica 1507 algorithm algorithms authentication certificate credential credentials key seal nested-reference unchanged"},{"id":"IETF RFC 1511","type":"specification","body":"IETF","designation":"RFC 1511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1511.txt","https://www.rfc-editor.org/rfc/rfc1511.pdf"],"folder":"IETF/RFC-1511","files":{"txt":{"path":"standards/IETF/RFC-1511/RFC-1511.txt","sha256":"70affaab01ccd549ad8fc716c15c048dc06418bb1fb4920a2895959290a703a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Linn\nRequest for Comments: 1511 Geer Zolot Associates\n September 1993\n\n Common Authentication Technology Overview\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nOverview\n\n The IETF's Common Authentication Technology (CAT) working group has\n pursued, and continues to pursue, several interrelated activities,\n involving definition of service interfaces as well as protocols. As\n a goal, it has sought to separate security implementation tasks from\n integration of security data elements into caller protocols, enabling\n those tasks to be partitioned and performed separately by\n implementors with different areas of expertise. This strategy is\n intended to provide leverage for the IETF community's security-\n oriented resources (by allowing a single secur","scope_keywords":["1511","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null}],"search_text":"IETF RFC 1511 Network Working Group J. Linn\nRequest for Comments: 1511 Geer Zolot Associates\n September 1993\n\n Common Authentication Technology Overview\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nOverview\n\n The IETF's Common Authentication Technology (CAT) working group has\n pursued, and continues to pursue, several interrelated activities,\n involving definition of service interfaces as well as protocols. As\n a goal, it has sought to separate security implementation tasks from\n integration of security data elements into caller protocols, enabling\n those tasks to be partitioned and performed separately by\n implementors with different areas of expertise. This strategy is\n intended to provide leverage for the IETF community's security-\n oriented resources (by allowing a single secur 1511 authentication key nested-reference unchanged"},{"id":"IETF RFC 2743","type":"specification","body":"IETF","designation":"RFC 2743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2743.txt","https://www.rfc-editor.org/rfc/rfc2743.pdf"],"folder":"IETF/RFC-2743","files":{"txt":{"path":"standards/IETF/RFC-2743/RFC-2743.txt","sha256":"59ca50ca7469d3b5000462810e8c3aea18d12bf34209220bb3daae7c494f3600"}},"tags":["nested-reference","unchanged"],"summary":"The Generic Security Service Application Program Interface (GSS-API),\n Version 2, as defined in [RFC-2078], provides security services to\n callers in a generic fashion, supportable with a range of underlying\n mechanisms and technologies and hence allowing source-level\n portability of applications to different environments. This\n specification defines GSS-API services and primitives at a level\n independent of underlying mechanism and programming language\n environment, and is to be complemented by other, related\n specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to be\n implemented in order to realize GSS-API services atop particular\n security mechanisms\n\n This memo obsoletes [RFC-2078], making specific, incremental changes\n in response to implementation experience and liaison ","scope_keywords":["2743","authentication","credential","credentials","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2744","folder":"IETF/RFC-2744","source":"IETF/RFC-2744/RFC-2744.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4178","folder":"IETF/RFC-4178","source":"IETF/RFC-4178/RFC-4178.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4401","folder":"IETF/RFC-4401","source":"IETF/RFC-4401/RFC-4401.txt","version":null},{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5554","folder":"IETF/RFC-5554","source":"IETF/RFC-5554/RFC-5554.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 2743 The Generic Security Service Application Program Interface (GSS-API),\n Version 2, as defined in [RFC-2078], provides security services to\n callers in a generic fashion, supportable with a range of underlying\n mechanisms and technologies and hence allowing source-level\n portability of applications to different environments. This\n specification defines GSS-API services and primitives at a level\n independent of underlying mechanism and programming language\n environment, and is to be complemented by other, related\n specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to be\n implemented in order to realize GSS-API services atop particular\n security mechanisms\n\n This memo obsoletes [RFC-2078], making specific, incremental changes\n in response to implementation experience and liaison  2743 authentication credential credentials management nested-reference unchanged"},{"id":"IETF RFC 1508","type":"specification","body":"IETF","designation":"RFC 1508","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1508.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1508.txt","https://www.rfc-editor.org/rfc/rfc1508.pdf"],"folder":"IETF/RFC-1508","files":{"txt":{"path":"standards/IETF/RFC-1508/RFC-1508.txt","sha256":"62b0f7817758db1b392eb13c6c0809267310bb0b99afbfefb83cb7d774f9d95a"}},"tags":["nested-reference","unchanged"],"summary":"This Generic Security Service Application Program Interface (GSS-API)\n definition provides security services to callers in a generic\n fashion, supportable with a range of underlying mechanisms and\n technologies and hence allowing source-level portability of\n applications to different environments. This specification defines\n GSS-API services and primitives at a level independent of underlying\n mechanism and programming language environment, and is to be\n complemented by other, related specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to\n be implemented in order to realize GSS-API services atop\n particular security mechanisms","scope_keywords":["1508","authentication","credential","credentials","key","management","seal"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1509","folder":"IETF/RFC-1509","source":"IETF/RFC-1509/RFC-1509.txt","version":null},{"body":"IETF","designation":"RFC 1511","folder":"IETF/RFC-1511","source":"IETF/RFC-1511/RFC-1511.txt","version":null},{"body":"IETF","designation":"RFC 1731","folder":"IETF/RFC-1731","source":"IETF/RFC-1731/RFC-1731.txt","version":null},{"body":"IETF","designation":"RFC 1961","folder":"IETF/RFC-1961","source":"IETF/RFC-1961/RFC-1961.txt","version":null},{"body":"IETF","designation":"RFC 1964","folder":"IETF/RFC-1964","source":"IETF/RFC-1964/RFC-1964.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null}],"search_text":"IETF RFC 1508 This Generic Security Service Application Program Interface (GSS-API)\n definition provides security services to callers in a generic\n fashion, supportable with a range of underlying mechanisms and\n technologies and hence allowing source-level portability of\n applications to different environments. This specification defines\n GSS-API services and primitives at a level independent of underlying\n mechanism and programming language environment, and is to be\n complemented by other, related specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to\n be implemented in order to realize GSS-API services atop\n particular security mechanisms 1508 authentication credential credentials key management seal nested-reference unchanged"},{"id":"IETF RFC 1509","type":"specification","body":"IETF","designation":"RFC 1509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1509.txt","https://www.rfc-editor.org/rfc/rfc1509.pdf"],"folder":"IETF/RFC-1509","files":{"txt":{"path":"standards/IETF/RFC-1509/RFC-1509.txt","sha256":"f12627659cb6d2980979a3dd99df81af2c2b960f25c71e5593fedf822942fa79"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies C language bindings for the Generic Security\n Service Application Program Interface (GSS-API), which is described\n at a language-independent conceptual level in other documents.\n\n The Generic Security Service Application Programming Interface (GSS-\n API) provides security services to its callers, and is intended for\n implementation atop alternative underlying cryptographic mechanisms.\n Typically, GSS-API callers will be application protocols into which\n security enhancements are integrated through invocation of services\n provided by the GSS-API. The GSS-API allows a caller application to\n authenticate a principal identity associated with a peer application,\n to delegate rights to a peer, and to apply security services such as\n confidentiality and integrity on a per-message basis.\n\n1. INTRODUCTION\n\n The Generic Security Service Application Programming Interface [1]","scope_keywords":["1509","authentication","credential","credentials","seal","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1511","folder":"IETF/RFC-1511","source":"IETF/RFC-1511/RFC-1511.txt","version":null},{"body":"IETF","designation":"RFC 1961","folder":"IETF/RFC-1961","source":"IETF/RFC-1961/RFC-1961.txt","version":null},{"body":"IETF","designation":"RFC 1964","folder":"IETF/RFC-1964","source":"IETF/RFC-1964/RFC-1964.txt","version":null},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null}],"search_text":"IETF RFC 1509 This document specifies C language bindings for the Generic Security\n Service Application Program Interface (GSS-API), which is described\n at a language-independent conceptual level in other documents.\n\n The Generic Security Service Application Programming Interface (GSS-\n API) provides security services to its callers, and is intended for\n implementation atop alternative underlying cryptographic mechanisms.\n Typically, GSS-API callers will be application protocols into which\n security enhancements are integrated through invocation of services\n provided by the GSS-API. The GSS-API allows a caller application to\n authenticate a principal identity associated with a peer application,\n to delegate rights to a peer, and to apply security services such as\n confidentiality and integrity on a per-message basis.\n\n1. INTRODUCTION\n\n The Generic Security Service Application Programming Interface [1] 1509 authentication credential credentials seal signature nested-reference unchanged"},{"id":"IETF RFC 1731","type":"specification","body":"IETF","designation":"RFC 1731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1731.txt","https://www.rfc-editor.org/rfc/rfc1731.pdf"],"folder":"IETF/RFC-1731","files":{"txt":{"path":"standards/IETF/RFC-1731/RFC-1731.txt","sha256":"e38837663cae49246bea8be00505c3e9728ab2282be3f0d14aa4770ec64ac82f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 1731 Carnegie Mellon\nCategory: Standards Track December 1994\n\n IMAP4 Authentication Mechanisms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n The Internet Message Access Protocol, Version 4 [IMAP4] contains the\n AUTHENTICATE command, for identifying and authenticating a user to an\n IMAP4 server and for optionally negotiating a protection mechanism\n for subsequent protocol interactions. This document describes\n several authentication mechanisms for use by the IMAP4 AUTHENTICATE\n command.\n\n2. Kerberos version","scope_keywords":["1731","authentication","credential","credentials","key","qualified","seal"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1734","folder":"IETF/RFC-1734","source":"IETF/RFC-1734/RFC-1734.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2980","folder":"IETF/RFC-2980","source":"IETF/RFC-2980/RFC-2980.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1731 Network Working Group J. Myers\nRequest for Comments: 1731 Carnegie Mellon\nCategory: Standards Track December 1994\n\n IMAP4 Authentication Mechanisms\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n The Internet Message Access Protocol, Version 4 [IMAP4] contains the\n AUTHENTICATE command, for identifying and authenticating a user to an\n IMAP4 server and for optionally negotiating a protection mechanism\n for subsequent protocol interactions. This document describes\n several authentication mechanisms for use by the IMAP4 AUTHENTICATE\n command.\n\n2. Kerberos version 1731 authentication credential credentials key qualified seal nested-reference unchanged"},{"id":"IETF RFC 1961","type":"specification","body":"IETF","designation":"RFC 1961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1961.txt","https://www.rfc-editor.org/rfc/rfc1961.pdf"],"folder":"IETF/RFC-1961","files":{"txt":{"path":"standards/IETF/RFC-1961/RFC-1961.txt","sha256":"8a236f76bec2a81a3d265d7124c6235c0d746605b2ce945a9ada62b56c2c2dc7"}},"tags":["nested-reference","unchanged"],"summary":"The protocol specification for SOCKS Version 5 specifies a\n generalized framework for the use of arbitrary authentication\n protocols in the initial SOCKS connection setup. This document\n provides the specification for the SOCKS V5 GSS-API authentication\n protocol, and defines a GSS-API-based encapsulation for provision of\n integrity, authentication and optional confidentiality.","scope_keywords":["1961","authentication","credential","credentials","presentation","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1961 The protocol specification for SOCKS Version 5 specifies a\n generalized framework for the use of arbitrary authentication\n protocols in the initial SOCKS connection setup. This document\n provides the specification for the SOCKS V5 GSS-API authentication\n protocol, and defines a GSS-API-based encapsulation for provision of\n integrity, authentication and optional confidentiality. 1961 authentication credential credentials presentation qualified nested-reference unchanged"},{"id":"IETF RFC 2752","type":"specification","body":"IETF","designation":"RFC 2752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2752.txt","https://www.rfc-editor.org/rfc/rfc2752.pdf"],"folder":"IETF/RFC-2752","files":{"txt":{"path":"standards/IETF/RFC-2752/RFC-2752.txt","sha256":"af3b28b978c2244c9204e8c0a6357b6205b19998a59fe07584571e0399323008"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the representation of identity information in\n POLICY_DATA object [POL-EXT] for supporting policy based admission\n control in RSVP. The goal of identity representation is to allow a\n process on a system to securely identify the owner and the\n application of the communicating process (e.g. user id) and convey\n this information in RSVP messages (PATH or RESV) in a secure manner.\n We describe the encoding of identities as RSVP policy element. We\n describe the processing rules to generate identity policy elements\n for multicast merged flows. Subsequently, we describe representations\n of user identities for Kerberos and Public Key based user\n authentication mechanisms. In summary we describe the use of this\n identity information in an operational setting.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOUL","scope_keywords":["2752","attribute","attributes","authentication","authorization","certificate","credential","credentials","identification","key","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2872","folder":"IETF/RFC-2872","source":"IETF/RFC-2872/RFC-2872.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null}],"search_text":"IETF RFC 2752 This document describes the representation of identity information in\n POLICY_DATA object [POL-EXT] for supporting policy based admission\n control in RSVP. The goal of identity representation is to allow a\n process on a system to securely identify the owner and the\n application of the communicating process (e.g. user id) and convey\n this information in RSVP messages (PATH or RESV) in a secure manner.\n We describe the encoding of identities as RSVP policy element. We\n describe the processing rules to generate identity policy elements\n for multicast merged flows. Subsequently, we describe representations\n of user identities for Kerberos and Public Key based user\n authentication mechanisms. In summary we describe the use of this\n identity information in an operational setting.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOUL 2752 attribute attributes authentication authorization certificate credential credentials identification key path policy presentation nested-reference unchanged"},{"id":"IETF RFC 3182","type":"specification","body":"IETF","designation":"RFC 3182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3182.txt","https://www.rfc-editor.org/rfc/rfc3182.pdf"],"folder":"IETF/RFC-3182","files":{"txt":{"path":"standards/IETF/RFC-3182/RFC-3182.txt","sha256":"a1e165853102a262cc94653799bfbc5a9c52848d3702d16fb159ef67feb38439"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the representation of identity information in\n POLICY_DATA object for supporting policy based admission control in\n the Resource ReSerVation Protocol (RSVP). The goal of identity\n representation is to allow a process on a system to securely identify\n the owner and the application of the communicating process (e.g.,\n user id) and convey this information in RSVP messages (PATH or RESV)\n in a secure manner. We describe the encoding of identities as RSVP\n policy element. We describe the processing rules to generate\n identity policy elements for multicast merged flows. Subsequently,\n we describe representations of user identities for Kerberos and\n Public Key based user authentication mechanisms. In summary, we\n describe the use of this identity information in an operational\n setting.\n\n This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment\n error and a fiel","scope_keywords":["3182","attribute","attributes","authentication","authorization","credential","credentials","identification","key","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null}],"search_text":"IETF RFC 3182 This document describes the representation of identity information in\n POLICY_DATA object for supporting policy based admission control in\n the Resource ReSerVation Protocol (RSVP). The goal of identity\n representation is to allow a process on a system to securely identify\n the owner and the application of the communicating process (e.g.,\n user id) and convey this information in RSVP messages (PATH or RESV)\n in a secure manner. We describe the encoding of identities as RSVP\n policy element. We describe the processing rules to generate\n identity policy elements for multicast merged flows. Subsequently,\n we describe representations of user identities for Kerberos and\n Public Key based user authentication mechanisms. In summary, we\n describe the use of this identity information in an operational\n setting.\n\n This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment\n error and a fiel 3182 attribute attributes authentication authorization credential credentials identification key path policy presentation nested-reference unchanged"},{"id":"IETF RFC 2712","type":"specification","body":"IETF","designation":"RFC 2712","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2712.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2712.txt","https://www.rfc-editor.org/rfc/rfc2712.pdf"],"folder":"IETF/RFC-2712","files":{"txt":{"path":"standards/IETF/RFC-2712/RFC-2712.txt","sha256":"ca268fa2c37d210c103703ac21efd0ed74faf9efb8d097ba9cadee905253de8c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Medvinsky\nRequest for Comments: 2712 Excite\nCategory: Standards Track M. Hur\n CyberSafe Corporation\n October 1999\n\n Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nIESG Note:\n\n The 40-bit ciphersuites defined in this memo are included only for\n the purpose of documenting the fact that those ciphersuite codes have\n already been assigned. 40-bit ciphersuites were designed to comply\n with US-centric, and n","scope_keywords":["2712","algorithm","authentication","certificate","credential","credentials","key","keys","policies","seal","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null}],"search_text":"IETF RFC 2712 Network Working Group A. Medvinsky\nRequest for Comments: 2712 Excite\nCategory: Standards Track M. Hur\n CyberSafe Corporation\n October 1999\n\n Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nIESG Note:\n\n The 40-bit ciphersuites defined in this memo are included only for\n the purpose of documenting the fact that those ciphersuite codes have\n already been assigned. 40-bit ciphersuites were designed to comply\n with US-centric, and n 2712 algorithm authentication certificate credential credentials key keys policies seal tls nested-reference unchanged"},{"id":"IETF RFC 2747","type":"specification","body":"IETF","designation":"RFC 2747","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2747.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2747.txt","https://www.rfc-editor.org/rfc/rfc2747.pdf"],"folder":"IETF/RFC-2747","files":{"txt":{"path":"standards/IETF/RFC-2747/RFC-2747.txt","sha256":"ac62aed7cc2d2c047cc17d4659000767ec77f965e7823ae9a808a9bf31463037"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the format and use of RSVP's INTEGRITY object\n to provide hop-by-hop integrity and authentication of RSVP messages.\n\n1. Introduction\n\n The Resource ReSerVation Protocol RSVP [1] is a protocol for setting\n up distributed state in routers and hosts, and in particular for\n reserving resources to implement integrated service. RSVP allows\n particular users to obtain preferential access to network resources,\n under the control of an admission control mechanism. Permission to\n make a reservation will depend both upon the availability of the\n requested resources along the path of the data, and upon satisfaction\n of policy rules.\n\n To ensure the integrity of this admission control mechanism, RSVP\n requires the ability to protect its messages against corruption and\n spoofing. This document defines a mechanism to protect RSVP message\n integrity hop-by-hop. The proposed schem","scope_keywords":["2747","algorithm","authentication","delivery","hash","hashing","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3097","folder":"IETF/RFC-3097","source":"IETF/RFC-3097/RFC-3097.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 2747 This document describes the format and use of RSVP's INTEGRITY object\n to provide hop-by-hop integrity and authentication of RSVP messages.\n\n1. Introduction\n\n The Resource ReSerVation Protocol RSVP [1] is a protocol for setting\n up distributed state in routers and hosts, and in particular for\n reserving resources to implement integrated service. RSVP allows\n particular users to obtain preferential access to network resources,\n under the control of an admission control mechanism. Permission to\n make a reservation will depend both upon the availability of the\n requested resources along the path of the data, and upon satisfaction\n of policy rules.\n\n To ensure the integrity of this admission control mechanism, RSVP\n requires the ability to protect its messages against corruption and\n spoofing. This document defines a mechanism to protect RSVP message\n integrity hop-by-hop. The proposed schem 2747 algorithm authentication delivery hash hashing key management path policy nested-reference unchanged"},{"id":"IETF RFC 3078","type":"specification","body":"IETF","designation":"RFC 3078","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3078.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3078.txt","https://www.rfc-editor.org/rfc/rfc3078.pdf"],"folder":"IETF/RFC-3078","files":{"txt":{"path":"standards/IETF/RFC-3078/RFC-3078.txt","sha256":"a43211229932022f915b33fd41fdf952a35770904a9938dd1d74627597acf782"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol provides a method to negotiate\n and utilize compression protocols over PPP encapsulated links.\n\n This document describes the use of the Microsoft Point to Point\n Encryption (MPPE) to enhance the confidentiality of PPP-encapsulated\n packets.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [5].\n\n1. Introduction\n\n The Microsoft Point to Point Encryption scheme is a means of\n representing Point to Point Protocol (PPP) packets in an encrypted\n form.\n\n MPPE uses the RSA RC4 [3] algorithm to provide data confidentiality.\n The length of the session key to be used for initializing encryption\n ta","scope_keywords":["3078","algorithm","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null}],"search_text":"IETF RFC 3078 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol provides a method to negotiate\n and utilize compression protocols over PPP encapsulated links.\n\n This document describes the use of the Microsoft Point to Point\n Encryption (MPPE) to enhance the confidentiality of PPP-encapsulated\n packets.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [5].\n\n1. Introduction\n\n The Microsoft Point to Point Encryption scheme is a means of\n representing Point to Point Protocol (PPP) packets in an encrypted\n form.\n\n MPPE uses the RSA RC4 [3] algorithm to provide data confidentiality.\n The length of the session key to be used for initializing encryption\n ta 3078 algorithm encryption key keys nested-reference unchanged"},{"id":"IETF RFC 3127","type":"specification","body":"IETF","designation":"RFC 3127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3127.txt","https://www.rfc-editor.org/rfc/rfc3127.pdf"],"folder":"IETF/RFC-3127","files":{"txt":{"path":"standards/IETF/RFC-3127/RFC-3127.txt","sha256":"5f738038e85c76af6c1c062b7496ac69aafcfa0bcc05181f30b7a8f45d4600cc"}},"tags":["nested-reference","unchanged"],"summary":"This memo represents the process and findings of the Authentication,\n Authorization, and Accounting Working Group (AAA WG) panel evaluating\n protocols proposed against the AAA Network Access Requirements, RFC\n 2989. Due to time constraints of this report, this document is not\n as fully polished as it might have been desired. But it remains\n mostly in this state to document the results as presented.\n\nMitton, et al. Informational [Page 1]\n\f\nRFC 3127 AAA Protocol Evaluation Process June 2001","scope_keywords":["3127","authentication","authorization","http","presentation","qualified","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4657","folder":"IETF/RFC-4657","source":"IETF/RFC-4657/RFC-4657.txt","version":null}],"search_text":"IETF RFC 3127 This memo represents the process and findings of the Authentication,\n Authorization, and Accounting Working Group (AAA WG) panel evaluating\n protocols proposed against the AAA Network Access Requirements, RFC\n 2989. Due to time constraints of this report, this document is not\n as fully polished as it might have been desired. But it remains\n mostly in this state to document the results as presented.\n\nMitton, et al. Informational [Page 1]\n\f\nRFC 3127 AAA Protocol Evaluation Process June 2001 3127 authentication authorization http presentation qualified validation nested-reference unchanged"},{"id":"IETF RFC 3129","type":"specification","body":"IETF","designation":"RFC 3129","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3129.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3129.txt","https://www.rfc-editor.org/rfc/rfc3129.pdf"],"folder":"IETF/RFC-3129","files":{"txt":{"path":"standards/IETF/RFC-3129/RFC-3129.txt","sha256":"4856ca16491ea1bcec438fba8e1e326ac0db974ce8fef0f7a8dc9ac76a587bf7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Thomas\nRequest for Comments: 3129 Cisco Systems\nCategory: Informational June 2001\n\n Requirements for Kerberized Internet Negotiation of Keys\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n The goal of this document is to produce a streamlined, fast, easily\n managed, and cryptographically sound protocol without requiring\n public key.\n\nMotivation\n\n The IPsec working group has defined a number of protocols which\n provide the ability to create and maintain cryptographically secure\n security associations at layer three (i.e., the IP layer). This\n effort has produced two distinct protocols:\n\n 1) a mechanism to encrypt and authenticate IP datagram ","scope_keywords":["3129","authentication","certificate","certificates","credential","credentials","key","keys","pki","policies","policy","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3129 Network Working Group M. Thomas\nRequest for Comments: 3129 Cisco Systems\nCategory: Informational June 2001\n\n Requirements for Kerberized Internet Negotiation of Keys\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n The goal of this document is to produce a streamlined, fast, easily\n managed, and cryptographically sound protocol without requiring\n public key.\n\nMotivation\n\n The IPsec working group has defined a number of protocols which\n provide the ability to create and maintain cryptographically secure\n security associations at layer three (i.e., the IP layer). This\n effort has produced two distinct protocols:\n\n 1) a mechanism to encrypt and authenticate IP datagram  3129 authentication certificate certificates credential credentials key keys pki policies policy signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 3169","type":"specification","body":"IETF","designation":"RFC 3169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3169.txt","https://www.rfc-editor.org/rfc/rfc3169.pdf"],"folder":"IETF/RFC-3169","files":{"txt":{"path":"standards/IETF/RFC-3169/RFC-3169.txt","sha256":"e9f22121f506735431e252cf028638eb506d543b8803e34ac40aac06102d9a87"}},"tags":["nested-reference","unchanged"],"summary":"This document defines requirements for protocols used by Network\n Access Servers (NAS).\n\n1. Requirements language\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\", are to be interpreted as\n described in [KEYWORDS].\n\n2. Introduction\n\n This document defines requirements for protocols used by Network\n Access Servers (NAS). Protocols used by NAS's may be divided into\n four spaces: Access protocols, Network protocols, AAA protocols, and\n Device Management protocols. The primary focus of this document is\n on AAA protocols.\n\n The reference model of a NAS used by this document, and the analysis\n of the functions of a NAS which led to the development of these\n requirements, may be found in [NAS-MODEL].\n\n3. Access Protocol Requirements\n\n There are three basic types of access protocols used by NAS's. First\n are the traditional teleph","scope_keywords":["3169","attribute","audit","authentication","authorization","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 3169 This document defines requirements for protocols used by Network\n Access Servers (NAS).\n\n1. Requirements language\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\", are to be interpreted as\n described in [KEYWORDS].\n\n2. Introduction\n\n This document defines requirements for protocols used by Network\n Access Servers (NAS). Protocols used by NAS's may be divided into\n four spaces: Access protocols, Network protocols, AAA protocols, and\n Device Management protocols. The primary focus of this document is\n on AAA protocols.\n\n The reference model of a NAS used by this document, and the analysis\n of the functions of a NAS which led to the development of these\n requirements, may be found in [NAS-MODEL].\n\n3. Access Protocol Requirements\n\n There are three basic types of access protocols used by NAS's. First\n are the traditional teleph 3169 attribute audit authentication authorization key management presentation nested-reference unchanged"},{"id":"IETF RFC 3281","type":"specification","body":"IETF","designation":"RFC 3281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3281.txt","https://www.rfc-editor.org/rfc/rfc3281.pdf"],"folder":"IETF/RFC-3281","files":{"txt":{"path":"standards/IETF/RFC-3281/RFC-3281.txt","sha256":"200530c3811fdd1aaef31e5dbfaac916bb9b3ccef4710b9c92a34204f7ff06e4"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a profile for the use of X.509 Attribute\n Certificates in Internet Protocols. Attribute certificates may be\n used in a wide range of applications and environments covering a\n broad spectrum of interoperability goals and a broader spectrum of\n operational and assurance requirements. The goal of this document is\n to establish a common baseline for generic applications requiring\n broad interoperability as well as limited special purpose\n requirements. The profile places emphasis on attribute certificate\n support for Internet electronic mail, IPSec, and WWW security\n applications.","scope_keywords":["3281","attribute","attributes","audit","authentication","authorization","certificate","certificates","crl","encryption","holder","issuer","key","pki","profile","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"IETF RFC 3281 This specification defines a profile for the use of X.509 Attribute\n Certificates in Internet Protocols. Attribute certificates may be\n used in a wide range of applications and environments covering a\n broad spectrum of interoperability goals and a broader spectrum of\n operational and assurance requirements. The goal of this document is\n to establish a common baseline for generic applications requiring\n broad interoperability as well as limited special purpose\n requirements. The profile places emphasis on attribute certificate\n support for Internet electronic mail, IPSec, and WWW security\n applications. 3281 attribute attributes audit authentication authorization certificate certificates crl encryption holder issuer key pki profile revocation nested-reference unchanged"},{"id":"IETF RFC 3489","type":"specification","body":"IETF","designation":"RFC 3489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3489.txt","https://www.rfc-editor.org/rfc/rfc3489.pdf"],"folder":"IETF/RFC-3489","files":{"txt":{"path":"standards/IETF/RFC-3489/RFC-3489.txt","sha256":"2d696278006db2708ac0a241a48a93246aaaaa492f579b5b006923c93464898b"}},"tags":["nested-reference","unchanged"],"summary":"Simple Traversal of User Datagram Protocol (UDP) Through Network\n Address Translators (NATs) (STUN) is a lightweight protocol that\n allows applications to discover the presence and types of NATs and\n firewalls between them and the public Internet. It also provides the\n ability for applications to determine the public Internet Protocol\n (IP) addresses allocated to them by the NAT. STUN works with many\n existing NATs, and does not require any special behavior from them.\n As a result, it allows a wide variety of applications to work through\n existing NAT infrastructure.","scope_keywords":["3489","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3581","folder":"IETF/RFC-3581","source":"IETF/RFC-3581/RFC-3581.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3489 Simple Traversal of User Datagram Protocol (UDP) Through Network\n Address Translators (NATs) (STUN) is a lightweight protocol that\n allows applications to discover the presence and types of NATs and\n firewalls between them and the public Internet. It also provides the\n ability for applications to determine the public Internet Protocol\n (IP) addresses allocated to them by the NAT. STUN works with many\n existing NATs, and does not require any special behavior from them.\n As a result, it allows a wide variety of applications to work through\n existing NAT infrastructure. 3489 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 3820","type":"specification","body":"IETF","designation":"RFC 3820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3820.txt","https://www.rfc-editor.org/rfc/rfc3820.pdf"],"folder":"IETF/RFC-3820","files":{"txt":{"path":"standards/IETF/RFC-3820/RFC-3820.txt","sha256":"4a41b3624516675cd50d8a13d616e5289655851bf7912591bb9d2563f0caba40"}},"tags":["nested-reference","unchanged"],"summary":"This document forms a certificate profile for Proxy Certificates,\n based on X.509 Public Key Infrastructure (PKI) certificates as\n defined in RFC 3280, for use in the Internet. The term Proxy\n Certificate is used to describe a certificate that is derived from,\n and signed by, a normal X.509 Public Key End Entity Certificate or by\n another Proxy Certificate for the purpose of providing restricted\n proxying and delegation within a PKI based authentication system.\n\nTuecke, et al. Standards Track [Page 1]\n\f\nRFC 3820 X.509 Proxy Certificate Profile June 2004","scope_keywords":["3820","algorithm","attribute","authentication","certificate","certificates","credential","crl","issuer","key","path","pki","policies","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null}],"search_text":"IETF RFC 3820 This document forms a certificate profile for Proxy Certificates,\n based on X.509 Public Key Infrastructure (PKI) certificates as\n defined in RFC 3280, for use in the Internet. The term Proxy\n Certificate is used to describe a certificate that is derived from,\n and signed by, a normal X.509 Public Key End Entity Certificate or by\n another Proxy Certificate for the purpose of providing restricted\n proxying and delegation within a PKI based authentication system.\n\nTuecke, et al. Standards Track [Page 1]\n\f\nRFC 3820 X.509 Proxy Certificate Profile June 2004 3820 algorithm attribute authentication certificate certificates credential crl issuer key path pki policies profile subject trust nested-reference unchanged"},{"id":"IETF RFC 4101","type":"specification","body":"IETF","designation":"RFC 4101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4101.txt","https://www.rfc-editor.org/rfc/rfc4101.pdf"],"folder":"IETF/RFC-4101","files":{"txt":{"path":"standards/IETF/RFC-4101/RFC-4101.txt","sha256":"b3e26892bb9963f2502a45a4f2721877e983fed3606fc02fab2115cc3a217392"}},"tags":["nested-reference","unchanged"],"summary":"The IETF process depends on peer review. However, IETF documents are\n generally written to be useful for implementors, not reviewers. In\n particular, while great care is generally taken to provide a complete\n description of the state machines and bits on the wire, this level of\n detail tends to get in the way of initial understanding. This\n document describes an approach for providing protocol \"models\" that\n allow reviewers to quickly grasp the essence of a system.\n\n1. Introduction\n\n The IETF process depends on peer review. However, in many cases, the\n documents submitted for publication are extremely difficult to\n review. Because reviewers have only limited amounts of time, this\n leads to extremely long review times, inadequate reviews, or both.\n In our view, a large part of the problem is that most documents fail\n to present an architectural model for how the protocol operates,\n opting","scope_keywords":["4101","authentication","key","path","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 4101 The IETF process depends on peer review. However, IETF documents are\n generally written to be useful for implementors, not reviewers. In\n particular, while great care is generally taken to provide a complete\n description of the state machines and bits on the wire, this level of\n detail tends to get in the way of initial understanding. This\n document describes an approach for providing protocol \"models\" that\n allow reviewers to quickly grasp the essence of a system.\n\n1. Introduction\n\n The IETF process depends on peer review. However, in many cases, the\n documents submitted for publication are extremely difficult to\n review. Because reviewers have only limited amounts of time, this\n leads to extremely long review times, inadequate reviews, or both.\n In our view, a large part of the problem is that most documents fail\n to present an architectural model for how the protocol operates,\n opting 4101 authentication key path presentation trust nested-reference unchanged"},{"id":"IETF RFC 5755","type":"specification","body":"IETF","designation":"RFC 5755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5755.txt","https://www.rfc-editor.org/rfc/rfc5755.pdf"],"folder":"IETF/RFC-5755","files":{"txt":{"path":"standards/IETF/RFC-5755/RFC-5755.txt","sha256":"444553b1e8d7312dd286fe9c4d0a8462ca33f9742c6b8594da287c61490f120a"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a profile for the use of X.509 Attribute\n Certificates in Internet Protocols. Attribute certificates may be\n used in a wide range of applications and environments covering a\n broad spectrum of interoperability goals and a broader spectrum of\n operational and assurance requirements. The goal of this document is\n to establish a common baseline for generic applications requiring\n broad interoperability as well as limited special purpose\n requirements. The profile places emphasis on attribute certificate\n support for Internet electronic mail, IPsec, and WWW security\n applications. This document obsoletes RFC 3281.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p","scope_keywords":["5755","attribute","attributes","audit","authentication","authorization","certificate","certificates","crl","encryption","holder","http","issuer","key","license","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.1.1","source":"ETSI/TS-119-412-6-V1.1.1/TS-119-412-6-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.2.1","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 5755 This specification defines a profile for the use of X.509 Attribute\n Certificates in Internet Protocols. Attribute certificates may be\n used in a wide range of applications and environments covering a\n broad spectrum of interoperability goals and a broader spectrum of\n operational and assurance requirements. The goal of this document is\n to establish a common baseline for generic applications requiring\n broad interoperability as well as limited special purpose\n requirements. The profile places emphasis on attribute certificate\n support for Internet electronic mail, IPsec, and WWW security\n applications. This document obsoletes RFC 3281.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for p 5755 attribute attributes audit authentication authorization certificate certificates crl encryption holder http issuer key license path nested-reference unchanged"},{"id":"IETF RFC 6649","type":"specification","body":"IETF","designation":"RFC 6649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6649.txt","https://www.rfc-editor.org/rfc/rfc6649.pdf"],"folder":"IETF/RFC-6649","files":{"txt":{"path":"standards/IETF/RFC-6649/RFC-6649.txt","sha256":"fad95b07817913ebe8c7736c107129821ccd9100386f05a20c07737492adeb77"}},"tags":["nested-reference","unchanged"],"summary":"The Kerberos 5 network authentication protocol, originally specified\n in RFC 1510, can use the Data Encryption Standard (DES) for\n encryption. Almost 30 years after first publishing DES, the National\n Institute of Standards and Technology (NIST) finally withdrew the\n standard in 2005, reflecting a long-established consensus that DES is\n insufficiently secure. By 2008, commercial hardware costing less\n than USD 15,000 could break DES keys in less than a day on average.\n DES is long past its sell-by date. Accordingly, this document\n updates RFC 1964, RFC 4120, RFC 4121, and RFC 4757 to deprecate the\n use of DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in\n Kerberos. Because RFC 1510 (obsoleted by RFC 4120) supports only\n DES, this document recommends the reclassification of RFC 1510 as\n Historic.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n T","scope_keywords":["6649","algorithm","algorithms","authentication","encryption","hash","http","key","keys","license","seal","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 6649 The Kerberos 5 network authentication protocol, originally specified\n in RFC 1510, can use the Data Encryption Standard (DES) for\n encryption. Almost 30 years after first publishing DES, the National\n Institute of Standards and Technology (NIST) finally withdrew the\n standard in 2005, reflecting a long-established consensus that DES is\n insufficiently secure. By 2008, commercial hardware costing less\n than USD 15,000 could break DES keys in less than a day on average.\n DES is long past its sell-by date. Accordingly, this document\n updates RFC 1964, RFC 4120, RFC 4121, and RFC 4757 to deprecate the\n use of DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in\n Kerberos. Because RFC 1510 (obsoleted by RFC 4120) supports only\n DES, this document recommends the reclassification of RFC 1510 as\n Historic.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n T 6649 algorithm algorithms authentication encryption hash http key keys license seal subject trust nested-reference unchanged"},{"id":"IETF RFC 3737","type":"specification","body":"IETF","designation":"RFC 3737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3737.txt","https://www.rfc-editor.org/rfc/rfc3737.pdf"],"folder":"IETF/RFC-3737","files":{"txt":{"path":"standards/IETF/RFC-3737/RFC-3737.txt","sha256":"712f9c61392707c82668ef3baf76ed19920d29c54c763993cb66da5406eedf94"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Wijnen\nRequest for Comments: 3737 Lucent Technologies\nCategory: Standards Track A. Bierman\n Cisco Systems, Inc.\n April 2004\n\n IANA Guidelines for the Registry of\n Remote Monitoring (RMON) MIB modules\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004). All Rights Reserved.\n\nAbstract\n\n This document defines the procedures for IANA to administer and\n maintain the Object Identifier (OID) tree under the Remote Monitoring\n (rmon) root. This memo also documents the currently assigned values.\n\n1. Introdu","scope_keywords":["3737","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null}],"search_text":"IETF RFC 3737 Network Working Group B. Wijnen\nRequest for Comments: 3737 Lucent Technologies\nCategory: Standards Track A. Bierman\n Cisco Systems, Inc.\n April 2004\n\n IANA Guidelines for the Registry of\n Remote Monitoring (RMON) MIB modules\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004). All Rights Reserved.\n\nAbstract\n\n This document defines the procedures for IANA to administer and\n maintain the Object Identifier (OID) tree under the Remote Monitoring\n (rmon) root. This memo also documents the currently assigned values.\n\n1. Introdu 3737 http key nested-reference unchanged"},{"id":"IETF RFC 2287","type":"specification","body":"IETF","designation":"RFC 2287","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2287.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2287.txt","https://www.rfc-editor.org/rfc/rfc2287.pdf"],"folder":"IETF/RFC-2287","files":{"txt":{"path":"standards/IETF/RFC-2287/RFC-2287.txt","sha256":"8fed4ef0d75cceb22f1b884247c95a8e0760459df748a1cbb44f8551ecb6dec8"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a basic set of managed objects for fault,\n configuration and performance management of applications from a\n systems perspective. More specifically, the managed objects are\n restricted to information that can be determined from the system\n itself and which does not require special instrumentation within the\n applications to make the information available.\n\n This memo does not specify a standard for the Internet community.\n\n2. The SNMPv2 Network Management Framework\n\n The SNMPv2 Network Management Framework consists of the following\n major components:\n\n o RFC 1902 Structure of Management Information for Version\n 2 of the Simple Network Management Protocol (SNMPv2) [2]\n\n o RFC 1903 Textual Conventions for Version 2 of the Sim","scope_keywords":["2287","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2287 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a basic set of managed objects for fault,\n configuration and performance management of applications from a\n systems perspective. More specifically, the managed objects are\n restricted to information that can be determined from the system\n itself and which does not require special instrumentation within the\n applications to make the information available.\n\n This memo does not specify a standard for the Internet community.\n\n2. The SNMPv2 Network Management Framework\n\n The SNMPv2 Network Management Framework consists of the following\n major components:\n\n o RFC 1902 Structure of Management Information for Version\n 2 of the Simple Network Management Protocol (SNMPv2) [2]\n\n o RFC 1903 Textual Conventions for Version 2 of the Sim 2287 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 1678","type":"specification","body":"IETF","designation":"RFC 1678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1678.txt","https://www.rfc-editor.org/rfc/rfc1678.pdf"],"folder":"IETF/RFC-1678","files":{"txt":{"path":"standards/IETF/RFC-1678/RFC-1678.txt","sha256":"34d8494a84e076943bf6ee723ae8c35bb3aa52439fecbac35307ae4e3adb50b2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Britton\nRequest for Comments: 1678 J. Tavs\nCategory: Informational IBM\n August 1994\n\n IPng Requirements of Large Corporate Networks\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list. This draft\n summarizes some of the requirements of large corporate networks for\n the next generation of the Internet protcol suite.\n\nExecutive Overview\n\n As more and more corporations are using TCP/IP for their mission-\n critical applications, they are bringing additional requirements,\n ","scope_keywords":["1678","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1678 Network Working Group E. Britton\nRequest for Comments: 1678 J. Tavs\nCategory: Informational IBM\n August 1994\n\n IPng Requirements of Large Corporate Networks\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list. This draft\n summarizes some of the requirements of large corporate networks for\n the next generation of the Internet protcol suite.\n\nExecutive Overview\n\n As more and more corporations are using TCP/IP for their mission-\n critical applications, they are bringing additional requirements,\n  1678 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 1787","type":"specification","body":"IETF","designation":"RFC 1787","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1787.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1787.txt","https://www.rfc-editor.org/rfc/rfc1787.pdf"],"folder":"IETF/RFC-1787","files":{"txt":{"path":"standards/IETF/RFC-1787/RFC-1787.txt","sha256":"41081aa8dc92a9089fb029151d1ed7ba453a1c0c3dd6c643370c4249e692152d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1787 T.J. Watson Research Center, IBM Corp.\nCategory: Informational April 1995\n\n Routing in a Multi-provider Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was prepared by the author on behalf of the Internet\n Architecture Board (IAB). It is offered by the IAB to stimulate\n discussion.\n\n Over the past few years the Internet has undergone significant\n changes. Among them is the emergence of multiple Network Service\n Providers, where resources that provide Internet-wide IP connectivity\n (routers, links) are controlled by different organizations. This\n document presents some of the issues related to network layer routing\n in a multi-provider Internet, and specificall","scope_keywords":["1787","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 1787 Network Working Group Y. Rekhter\nRequest for Comments: 1787 T.J. Watson Research Center, IBM Corp.\nCategory: Informational April 1995\n\n Routing in a Multi-provider Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was prepared by the author on behalf of the Internet\n Architecture Board (IAB). It is offered by the IAB to stimulate\n discussion.\n\n Over the past few years the Internet has undergone significant\n changes. Among them is the emergence of multiple Network Service\n Providers, where resources that provide Internet-wide IP connectivity\n (routers, links) are controlled by different organizations. This\n document presents some of the issues related to network layer routing\n in a multi-provider Internet, and specificall 1787 path subject nested-reference unchanged"},{"id":"IETF RFC 1817","type":"specification","body":"IETF","designation":"RFC 1817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1817.txt","https://www.rfc-editor.org/rfc/rfc1817.pdf"],"folder":"IETF/RFC-1817","files":{"txt":{"path":"standards/IETF/RFC-1817/RFC-1817.txt","sha256":"ade7d8605f35b6deb2fe7f451e764a07fb6fc87d936ef73c088b9740dec8ec34"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Rekhter\nRequest for Comments: 1817 cisco Systems\nCategory: Informational August 1995\n\n CIDR and Classful Routing\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n Classless Inter-Domain Routing (CIDR) is used in the Internet as the\n primary mechanism to improve scalability of the Internet routing\n system. This document represents the IAB's (Internet Architecture\n Board) evaluation of the current and near term implications of CIDR\n on organizations that use Classful routing technology.\n\nBackground\n\n Classless Inter-Domain Routing (CIDR) ([RFC1518], [RFC1519]) is\n deployed in the Internet as the primary mechanism to improve scaling\n property of the Internet routing system. Essential to CIDR is the\n generalization of the ","scope_keywords":["1817"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 1817 Network Working Group Y. Rekhter\nRequest for Comments: 1817 cisco Systems\nCategory: Informational August 1995\n\n CIDR and Classful Routing\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n Classless Inter-Domain Routing (CIDR) is used in the Internet as the\n primary mechanism to improve scalability of the Internet routing\n system. This document represents the IAB's (Internet Architecture\n Board) evaluation of the current and near term implications of CIDR\n on organizations that use Classful routing technology.\n\nBackground\n\n Classless Inter-Domain Routing (CIDR) ([RFC1518], [RFC1519]) is\n deployed in the Internet as the primary mechanism to improve scaling\n property of the Internet routing system. Essential to CIDR is the\n generalization of the  1817 nested-reference unchanged"},{"id":"IETF RFC 1887","type":"specification","body":"IETF","designation":"RFC 1887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1887.txt","https://www.rfc-editor.org/rfc/rfc1887.pdf"],"folder":"IETF/RFC-1887","files":{"txt":{"path":"standards/IETF/RFC-1887/RFC-1887.txt","sha256":"337fcea5afb865bfd5234a0e72e086d31d35a46062c99aca1ecd3f3ee3606fce"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an architecture for allocating IPv6 [1]\n unicast addresses in the Internet. The overall IPv6 addressing\n architecture is defined in [2]. This document does not go into the\n details of an addressing plan.\n\n1. Scope\n\n The global internet can be modeled as a collection of hosts\n interconnected via transmission and switching facilities. Control\n over the collection of hosts and the transmission and switching\n facilities that compose the networking resources of the global\n internet is not homogeneous, but is distributed among multiple\n administrative authorities. Resources under control of a single\n administration within a contiguous segment of network topology form a\n domain. For the rest of this paper, `domain' and `routing domain'\n will be used interchangeably.\n\n Domains that share their resources with other domains are called\n network service providers (or just prov","scope_keywords":["1887","identification","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1884","folder":"IETF/RFC-1884","source":"IETF/RFC-1884/RFC-1884.txt","version":null},{"body":"IETF","designation":"RFC 2073","folder":"IETF/RFC-2073","source":"IETF/RFC-2073/RFC-2073.txt","version":null}],"search_text":"IETF RFC 1887 This document provides an architecture for allocating IPv6 [1]\n unicast addresses in the Internet. The overall IPv6 addressing\n architecture is defined in [2]. This document does not go into the\n details of an addressing plan.\n\n1. Scope\n\n The global internet can be modeled as a collection of hosts\n interconnected via transmission and switching facilities. Control\n over the collection of hosts and the transmission and switching\n facilities that compose the networking resources of the global\n internet is not homogeneous, but is distributed among multiple\n administrative authorities. Resources under control of a single\n administration within a contiguous segment of network topology form a\n domain. For the rest of this paper, `domain' and `routing domain'\n will be used interchangeably.\n\n Domains that share their resources with other domains are called\n network service providers (or just prov 1887 identification policy registered nested-reference unchanged"},{"id":"IETF RFC 2008","type":"specification","body":"IETF","designation":"RFC 2008","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2008.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2008.txt","https://www.rfc-editor.org/rfc/rfc2008.pdf"],"folder":"IETF/RFC-2008","files":{"txt":{"path":"standards/IETF/RFC-2008/RFC-2008.txt","sha256":"a1d902d3bb65b869eb7d2e5a9ab602125413f3ef73e8c8fbda02f5dbbef9b930"}},"tags":["nested-reference","unchanged"],"summary":"IP unicast address allocation and management are essential\n operational functions for the Public Internet. The exact policies for\n IP unicast address allocation and management continue to be the\n subject of many discussions. Such discussions cannot be pursued in a\n vacuum - the participants must understand the technical issues and\n implications associated with various address allocation and\n management policies.\n\n The purpose of this document is to articulate certain relevant\n fundamental technical issues that must be considered in formulating\n unicast address allocation and management policies for the Public\n Internet, and to provide recommendations with respect to these\n policies.\n\n The major focus of this document is on two possible policies,\n \"address ownership\" and \"address lending,\" and the technical\n implications of these policies for the Public Internet. For the\n organizations th","scope_keywords":["2008","management","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null}],"search_text":"IETF RFC 2008 IP unicast address allocation and management are essential\n operational functions for the Public Internet. The exact policies for\n IP unicast address allocation and management continue to be the\n subject of many discussions. Such discussions cannot be pursued in a\n vacuum - the participants must understand the technical issues and\n implications associated with various address allocation and\n management policies.\n\n The purpose of this document is to articulate certain relevant\n fundamental technical issues that must be considered in formulating\n unicast address allocation and management policies for the Public\n Internet, and to provide recommendations with respect to these\n policies.\n\n The major focus of this document is on two possible policies,\n \"address ownership\" and \"address lending,\" and the technical\n implications of these policies for the Public Internet. For the\n organizations th 2008 management policies policy subject nested-reference unchanged"},{"id":"IETF RFC 2260","type":"specification","body":"IETF","designation":"RFC 2260","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2260.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2260.txt","https://www.rfc-editor.org/rfc/rfc2260.pdf"],"folder":"IETF/RFC-2260","files":{"txt":{"path":"standards/IETF/RFC-2260/RFC-2260.txt","sha256":"57e01e533ececcd6dd55c6b4e78e796766b89436394e0abd5addfe0e33bf631b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes addressing and routing strategies for multi-\n homed enterprises attached to multiple Internet Service Providers\n (ISPs) that are intended to reduce the routing overhead due to these\n enterprises in the global Internet routing system.\n\n3. Motivations\n\n An enterprise may acquire its Internet connectivity from more than\n one Internet Service Provider (ISP) for some of the following\n reasons. Maintaining connectivity via more than one ISP could be\n viewed as a way to make connectivity to the Internet more reliable.\n This way when connectivity through one of the ISPs fails,\n connectivity via the other ISP(s) would enable the enterprise to\n preserve its connectivity to the Internet. In addition to providing\n more reliable connectivity, maintaining connectivity via more than\n one ISP could also allow the enterprise to distribute load among\n multiple connections. For ente","scope_keywords":["2260","driving","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3704","folder":"IETF/RFC-3704","source":"IETF/RFC-3704/RFC-3704.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null}],"search_text":"IETF RFC 2260 This document describes addressing and routing strategies for multi-\n homed enterprises attached to multiple Internet Service Providers\n (ISPs) that are intended to reduce the routing overhead due to these\n enterprises in the global Internet routing system.\n\n3. Motivations\n\n An enterprise may acquire its Internet connectivity from more than\n one Internet Service Provider (ISP) for some of the following\n reasons. Maintaining connectivity via more than one ISP could be\n viewed as a way to make connectivity to the Internet more reliable.\n This way when connectivity through one of the ISPs fails,\n connectivity via the other ISP(s) would enable the enterprise to\n preserve its connectivity to the Internet. In addition to providing\n more reliable connectivity, maintaining connectivity via more than\n one ISP could also allow the enterprise to distribute load among\n multiple connections. For ente 2260 driving policy nested-reference unchanged"},{"id":"IETF RFC 1631","type":"specification","body":"IETF","designation":"RFC 1631","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1631.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1631.txt","https://www.rfc-editor.org/rfc/rfc1631.pdf"],"folder":"IETF/RFC-1631","files":{"txt":{"path":"standards/IETF/RFC-1631/RFC-1631.txt","sha256":"d393680ad43402d7d54df042d43778049e2e6c3bcb453bff4d74f865b8553772"}},"tags":["nested-reference","unchanged"],"summary":"The two most compelling problems facing the IP Internet are IP\n address depletion and scaling in routing. Long-term and short-term\n solutions to these problems are being developed. The short-term\n solution is CIDR (Classless InterDomain Routing). The long-term\n solutions consist of various proposals for new internet protocols\n with larger addresses.\n\n It is possible that CIDR will not be adequate to maintain the IP\n Internet until the long-term solutions are in place. This memo\n proposes another short-term solution, address reuse, that complements\n CIDR or even makes it unnecessary. The address reuse solution is to\n place Network Address Translators (NAT) at the borders of stub\n domains. Each NAT box has a table consisting of pairs of local IP\n addresses and globally unique addresses. The IP addresses inside the\n stub domain are not globally unique. They are reused in other\n domains, thu","scope_keywords":["1631"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2182","folder":"IETF/RFC-2182","source":"IETF/RFC-2182/RFC-2182.txt","version":null},{"body":"IETF","designation":"RFC 2694","folder":"IETF/RFC-2694","source":"IETF/RFC-2694/RFC-2694.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 1631 The two most compelling problems facing the IP Internet are IP\n address depletion and scaling in routing. Long-term and short-term\n solutions to these problems are being developed. The short-term\n solution is CIDR (Classless InterDomain Routing). The long-term\n solutions consist of various proposals for new internet protocols\n with larger addresses.\n\n It is possible that CIDR will not be adequate to maintain the IP\n Internet until the long-term solutions are in place. This memo\n proposes another short-term solution, address reuse, that complements\n CIDR or even makes it unnecessary. The address reuse solution is to\n place Network Address Translators (NAT) at the borders of stub\n domains. Each NAT box has a table consisting of pairs of local IP\n addresses and globally unique addresses. The IP addresses inside the\n stub domain are not globally unique. They are reused in other\n domains, thu 1631 nested-reference unchanged"},{"id":"IETF RFC 2036","type":"specification","body":"IETF","designation":"RFC 2036","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2036.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2036.txt","https://www.rfc-editor.org/rfc/rfc2036.pdf"],"folder":"IETF/RFC-2036","files":{"txt":{"path":"standards/IETF/RFC-2036/RFC-2036.txt","sha256":"d9bfcbd79d9e0fc94a478dd020a11cabbf8fe49f225f87a70ae9578a3304e97d"}},"tags":["nested-reference","unchanged"],"summary":"This document is a commentary on the recommendation that IANA\n commence allocation of the presently unallocated components of the\n Class A address space to registries, for deployment within the\n Internet as class-less address blocks.\n\n The document examines the implications for service providers and end\n clients within this environment. The document notes the major\n conclusion that widespread adoption of class-less routing protocols\n is required, within a relatively rapid timeframe for this\n recommendation to be effective.","scope_keywords":["2036","pid","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null}],"search_text":"IETF RFC 2036 This document is a commentary on the recommendation that IANA\n commence allocation of the presently unallocated components of the\n Class A address space to registries, for deployment within the\n Internet as class-less address blocks.\n\n The document examines the implications for service providers and end\n clients within this environment. The document notes the major\n conclusion that widespread adoption of class-less routing protocols\n is required, within a relatively rapid timeframe for this\n recommendation to be effective. 2036 pid policies nested-reference unchanged"},{"id":"IETF RFC 2450","type":"specification","body":"IETF","designation":"RFC 2450","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2450.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2450.txt","https://www.rfc-editor.org/rfc/rfc2450.pdf"],"folder":"IETF/RFC-2450","files":{"txt":{"path":"standards/IETF/RFC-2450/RFC-2450.txt","sha256":"51aaef9cfbea95cc40cc927d03bd7b5591b0265311825eaf37b679decaae26ba"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 2450 Nokia\nCategory: Informational December 1998\n\n Proposed TLA and NLA Assignment Rules\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document proposes rules for Top-Level Aggregation Identifiers\n (TLA ID) and Next-Level Aggregation Identifiers (NLA ID) as defined\n in [AGGR]. These proposed rules apply to registries allocating TLA\n ID's and to organizations receiving TLA ID's.\n\n This proposal is intended as input from the IPng working group to the\n IANA and Registries. It is not intended for any official IETF\n status. Its content represents the result of extensive discussion\n between the IPng work","scope_keywords":["2450","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3177","folder":"IETF/RFC-3177","source":"IETF/RFC-3177/RFC-3177.txt","version":null}],"search_text":"IETF RFC 2450 Network Working Group R. Hinden\nRequest for Comments: 2450 Nokia\nCategory: Informational December 1998\n\n Proposed TLA and NLA Assignment Rules\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document proposes rules for Top-Level Aggregation Identifiers\n (TLA ID) and Next-Level Aggregation Identifiers (NLA ID) as defined\n in [AGGR]. These proposed rules apply to registries allocating TLA\n ID's and to organizations receiving TLA ID's.\n\n This proposal is intended as input from the IPng working group to the\n IANA and Registries. It is not intended for any official IETF\n status. Its content represents the result of extensive discussion\n between the IPng work 2450 key path nested-reference unchanged"},{"id":"IETF RFC 3582","type":"specification","body":"IETF","designation":"RFC 3582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3582.txt","https://www.rfc-editor.org/rfc/rfc3582.pdf"],"folder":"IETF/RFC-3582","files":{"txt":{"path":"standards/IETF/RFC-3582/RFC-3582.txt","sha256":"f54beb8739957f435a754dc60258663010c7d5196cf0ae5a376bdc9df4ff3328"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines a set of goals for proposed new IPv6 site-\n multihoming architectures. It is recognised that this set of goals\n is ambitious and that some goals may conflict with others. The\n solution or solutions adopted may only be able to satisfy some of the\n goals presented here.\n\n1. Introduction\n\n Site-multihoming, i.e., connecting to more than one IP service\n provider, is an essential component of service for many sites which\n are part of the Internet.\n\n Current IPv4 site-multihoming practices have been added on to the\n CIDR architecture [1], which assumes that routing table entries can\n be aggregated based upon a hierarchy of customers and service\n providers.\n\n However, it appears that this hierarchy is being supplanted by a\n dense mesh of interconnections [6]. Additionally, there has been an\n enormous growth in the number of multihomed sites. For purposes of\n redundancy an","scope_keywords":["3582","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4116","folder":"IETF/RFC-4116","source":"IETF/RFC-4116/RFC-4116.txt","version":null},{"body":"IETF","designation":"RFC 4177","folder":"IETF/RFC-4177","source":"IETF/RFC-4177/RFC-4177.txt","version":null},{"body":"IETF","designation":"RFC 4219","folder":"IETF/RFC-4219","source":"IETF/RFC-4219/RFC-4219.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 3582 This document outlines a set of goals for proposed new IPv6 site-\n multihoming architectures. It is recognised that this set of goals\n is ambitious and that some goals may conflict with others. The\n solution or solutions adopted may only be able to satisfy some of the\n goals presented here.\n\n1. Introduction\n\n Site-multihoming, i.e., connecting to more than one IP service\n provider, is an essential component of service for many sites which\n are part of the Internet.\n\n Current IPv4 site-multihoming practices have been added on to the\n CIDR architecture [1], which assumes that routing table entries can\n be aggregated based upon a hierarchy of customers and service\n providers.\n\n However, it appears that this hierarchy is being supplanted by a\n dense mesh of interconnections [6]. Additionally, there has been an\n enormous growth in the number of multihomed sites. For purposes of\n redundancy an 3582 pid policy nested-reference unchanged"},{"id":"IETF RFC 3814","type":"specification","body":"IETF","designation":"RFC 3814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3814.txt","https://www.rfc-editor.org/rfc/rfc3814.pdf"],"folder":"IETF/RFC-3814","files":{"txt":{"path":"standards/IETF/RFC-3814/RFC-3814.txt","sha256":"4a9784bb90383861fe269f78d8a20e894b759697674be53167a7cbee60dc4b41"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for defining,\n configuring, and monitoring Forwarding Equivalence Class (FEC) to\n Next Hop Label Forwarding Entry (NHLFE) mappings and corresponding\n actions for use with Multiprotocol Label Switching (MPLS).","scope_keywords":["3814","identification","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null}],"search_text":"IETF RFC 3814 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for defining,\n configuring, and monitoring Forwarding Equivalence Class (FEC) to\n Next Hop Label Forwarding Entry (NHLFE) mappings and corresponding\n actions for use with Multiprotocol Label Switching (MPLS). 3814 identification key management path nested-reference unchanged"},{"id":"IETF RFC 4116","type":"specification","body":"IETF","designation":"RFC 4116","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4116.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4116.txt","https://www.rfc-editor.org/rfc/rfc4116.pdf"],"folder":"IETF/RFC-4116","files":{"txt":{"path":"standards/IETF/RFC-4116/RFC-4116.txt","sha256":"242b4dba31f72dfc6ced1501d28876ae67a51ec9fa8cb2dcc2fc767e92552e54"}},"tags":["nested-reference","unchanged"],"summary":"Multihoming is an essential component of service for many Internet\n sites. This document describes some implementation strategies for\n multihoming with IPv4 and enumerates features for comparison with\n other multihoming proposals (particularly those related to IPv6).\n\nAbley, et al. Informational [Page 1]\n\f\nRFC 4116 IPv4 Multihoming July 2005","scope_keywords":["4116","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null}],"search_text":"IETF RFC 4116 Multihoming is an essential component of service for many Internet\n sites. This document describes some implementation strategies for\n multihoming with IPv4 and enumerates features for comparison with\n other multihoming proposals (particularly those related to IPv6).\n\nAbley, et al. Informational [Page 1]\n\f\nRFC 4116 IPv4 Multihoming July 2005 4116 management path policies policy nested-reference unchanged"},{"id":"IETF RFC 4540","type":"specification","body":"IETF","designation":"RFC 4540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4540.txt","https://www.rfc-editor.org/rfc/rfc4540.pdf"],"folder":"IETF/RFC-4540","files":{"txt":{"path":"standards/IETF/RFC-4540/RFC-4540.txt","sha256":"9d105cac0704ad686513667a5a430fb5080b3decd79965c411cf4e3e703a162f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for controlling middleboxes such\n as firewalls and network address translators. It is a fully\n compliant implementation of the Middlebox Communications (MIDCOM)\n semantics described in RFC 3989. Compared to earlier experimental\n versions of the SIMCO protocol, this version (3.0) uses binary\n message encodings in order to reduce resource requirements.\n\nStiemerling, et al. Experimental [Page 1]\n\f\nRFC 4540 NEC's SIMCO Protocol Version 3.0 May 2006","scope_keywords":["4540","attribute","attributes","authentication","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4540 This document describes a protocol for controlling middleboxes such\n as firewalls and network address translators. It is a fully\n compliant implementation of the Middlebox Communications (MIDCOM)\n semantics described in RFC 3989. Compared to earlier experimental\n versions of the SIMCO protocol, this version (3.0) uses binary\n message encodings in order to reduce resource requirements.\n\nStiemerling, et al. Experimental [Page 1]\n\f\nRFC 4540 NEC's SIMCO Protocol Version 3.0 May 2006 4540 attribute attributes authentication policy nested-reference unchanged"},{"id":"IETF RFC 1524","type":"specification","body":"IETF","designation":"RFC 1524","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1524.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1524.txt","https://www.rfc-editor.org/rfc/rfc1524.pdf"],"folder":"IETF/RFC-1524","files":{"txt":{"path":"standards/IETF/RFC-1524/RFC-1524.txt","sha256":"2158f66dbc2dff4488916728152df30b758199940fbf73c3e894f545c10fffa7"}},"tags":["nested-reference","unchanged"],"summary":"This memo suggests a file format to be used to inform multiple mail\n reading user agent programs about the locally-installed facilities\n for handling mail in various formats. The mechanism is explicitly\n designed to work with mail systems based Internet mail as defined by\n RFC's 821 (STD 10), 822 (STD 11), 934, 1049 (STD 11), 1113, and the\n Multipurpose Internet Mail Extensions, known as MIME. However, with\n some extensions it could probably be made to work for X.400-based\n mail systems as well. The format and mechanism are proposed in a\n manner that is generally operating-system independent. However,\n certain implementation details will inevitably reflect operating\n system differences, some of which will have to be handled in a\n uniform manner for each operating system. This memo makes such\n situations explicit, and, in an appendix, suggests a standard\n behavior under the UNIX operating","scope_keywords":["1524","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1872","folder":"IETF/RFC-1872","source":"IETF/RFC-1872/RFC-1872.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null}],"search_text":"IETF RFC 1524 This memo suggests a file format to be used to inform multiple mail\n reading user agent programs about the locally-installed facilities\n for handling mail in various formats. The mechanism is explicitly\n designed to work with mail systems based Internet mail as defined by\n RFC's 821 (STD 10), 822 (STD 11), 934, 1049 (STD 11), 1113, and the\n Multipurpose Internet Mail Extensions, known as MIME. However, with\n some extensions it could probably be made to work for X.400-based\n mail systems as well. The format and mechanism are proposed in a\n manner that is generally operating-system independent. However,\n certain implementation details will inevitably reflect operating\n system differences, some of which will have to be handled in a\n uniform manner for each operating system. This memo makes such\n situations explicit, and, in an appendix, suggests a standard\n behavior under the UNIX operating 1524 presentation nested-reference unchanged"},{"id":"IETF RFC 1556","type":"specification","body":"IETF","designation":"RFC 1556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1556.txt","https://www.rfc-editor.org/rfc/rfc1556.pdf"],"folder":"IETF/RFC-1556","files":{"txt":{"path":"standards/IETF/RFC-1556/RFC-1556.txt","sha256":"0c784f28267a9b9aa8bc7c1a60833e97fe5f0dfed0471d64083714d677910dbf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Nussbacher\nRequest for Comments: 1556 Israeli Inter-University\nCategory: Informational Computer Center\n December 1993\n\n Handling of Bi-directional Texts in MIME\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes the format and syntax of the \"direction\"\n keyword to be used with bi-directional texts in MIME.\n\nDescription\n\n The MIME standards (RFC 1521 and 1522) defined methods for\n transporting non-ASCII data via a standard RFC822 e-mail system.\n Specifically, the Content-type field allows for the inclusion of any\n ISO language such as Arabic (ISO-8859-6) or Hebrew (ISO-8859-8). The\n problem is that the these two languages are read from right to left\n and can have bi-directional data such as mixed ","scope_keywords":["1556","algorithm","algorithms","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null}],"search_text":"IETF RFC 1556 Network Working Group H. Nussbacher\nRequest for Comments: 1556 Israeli Inter-University\nCategory: Informational Computer Center\n December 1993\n\n Handling of Bi-directional Texts in MIME\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes the format and syntax of the \"direction\"\n keyword to be used with bi-directional texts in MIME.\n\nDescription\n\n The MIME standards (RFC 1521 and 1522) defined methods for\n transporting non-ASCII data via a standard RFC822 e-mail system.\n Specifically, the Content-type field allows for the inclusion of any\n ISO language such as Arabic (ISO-8859-6) or Hebrew (ISO-8859-8). The\n problem is that the these two languages are read from right to left\n and can have bi-directional data such as mixed  1556 algorithm algorithms key presentation nested-reference unchanged"},{"id":"IETF RFC 1557","type":"specification","body":"IETF","designation":"RFC 1557","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1557.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1557.txt","https://www.rfc-editor.org/rfc/rfc1557.pdf"],"folder":"IETF/RFC-1557","files":{"txt":{"path":"standards/IETF/RFC-1557/RFC-1557.txt","sha256":"4f5431837d2bfc79def2236121767a78bc66edb4a84f85ff8fa9a16cdac62416"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group U. Choi\nRequest for Comments: 1557 K. Chon\nCategory: Informational KAIST\n H. Park\n Solvit Chosun Media\n December 1993\n\n Korean Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This document describes the encoding method being used to represent\n Korean characters in both header and body part of the Internet mail\n messages [RFC822]. This encoding method was specified in 1991, and\n has since then been used. It has now widely being used in Korean IP\n networks.\n\n This document also describes the name of the encoding method which is\n to be used in order to match the message header and body format of\n MIME [MIME1, MIME2].\n\n This document describes only the encoding method for plain t","scope_keywords":["1557","crl","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 1557 Network Working Group U. Choi\nRequest for Comments: 1557 K. Chon\nCategory: Informational KAIST\n H. Park\n Solvit Chosun Media\n December 1993\n\n Korean Character Encoding for Internet Messages\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n This document describes the encoding method being used to represent\n Korean characters in both header and body part of the Internet mail\n messages [RFC822]. This encoding method was specified in 1991, and\n has since then been used. It has now widely being used in Korean IP\n networks.\n\n This document also describes the name of the encoding method which is\n to be used in order to match the message header and body format of\n MIME [MIME1, MIME2].\n\n This document describes only the encoding method for plain t 1557 crl risk nested-reference unchanged"},{"id":"IETF RFC 1641","type":"specification","body":"IETF","designation":"RFC 1641","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1641.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1641.txt","https://www.rfc-editor.org/rfc/rfc1641.pdf"],"folder":"IETF/RFC-1641","files":{"pdf":{"path":"standards/IETF/RFC-1641/RFC-1641.pdf","sha256":"71078da9c2f350b446e98b083764a6a3f28199c1d0c604699360101d06f5c01f"},"txt":{"path":"standards/IETF/RFC-1641/RFC-1641.txt","sha256":"3b5960fdcc4eaabeb948f6d3bc369251190770d848167e2e680eb5c6226a43c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Goldsmith\nRequest for Comments: 1641 M. Davis\nCategory: Experimental Taligent, Inc.\n July 1994\n\n Using Unicode with MIME\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Distribution of this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E)\n jointly define a 16 bit character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode as a permitted character set nor specifies how it would be\n enco","scope_keywords":["1641","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1641 Network Working Group D. Goldsmith\nRequest for Comments: 1641 M. Davis\nCategory: Experimental Taligent, Inc.\n July 1994\n\n Using Unicode with MIME\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Distribution of this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E)\n jointly define a 16 bit character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode as a permitted character set nor specifies how it would be\n enco 1641 presentation nested-reference unchanged"},{"id":"IETF RFC 1642","type":"specification","body":"IETF","designation":"RFC 1642","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1642.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1642.txt","https://www.rfc-editor.org/rfc/rfc1642.pdf"],"folder":"IETF/RFC-1642","files":{"pdf":{"path":"standards/IETF/RFC-1642/RFC-1642.pdf","sha256":"e2a925107954a984899a9067e909bddaecf320c4a3f1125e3442432dead82f70"},"txt":{"path":"standards/IETF/RFC-1642/RFC-1642.txt","sha256":"537dab66a55291e481fa3a739b42f291c6f38076787295026457c28d254d76e8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Goldsmith\nRequest for Comments: 1642 M. Davis\nCategory: Experimental Taligent, Inc.\n July 1994\n\n UTF-7\n\n A Mail-Safe Transformation Format of Unicode\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Distribution of this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E)\n jointly define a 16 bit character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode as a permitted character set nor sp","scope_keywords":["1642","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null}],"search_text":"IETF RFC 1642 Network Working Group D. Goldsmith\nRequest for Comments: 1642 M. Davis\nCategory: Experimental Taligent, Inc.\n July 1994\n\n UTF-7\n\n A Mail-Safe Transformation Format of Unicode\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Distribution of this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993(E)\n jointly define a 16 bit character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 1521 and RFC 1522) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode as a permitted character set nor sp 1642 presentation nested-reference unchanged"},{"id":"IETF RFC 1652","type":"specification","body":"IETF","designation":"RFC 1652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1652.txt","https://www.rfc-editor.org/rfc/rfc1652.pdf"],"folder":"IETF/RFC-1652","files":{"txt":{"path":"standards/IETF/RFC-1652/RFC-1652.txt","sha256":"87c8566f7ba17b7fd925e22a5eebd845389c26564297c5ccc0a89b8a30d7fac7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Klensin, WG Chair\nRequest for Comments: 1652 MCI\nObsoletes: 1426 N. Freed, Editor\nCategory: Standards Track Innosoft\n M. Rose\n Dover Beach Consulting, Inc.\n E. Stefferud\n Network Management Associates, Inc.\n D. Crocker\n Silicon Graphics, Inc.\n July 1994\n\n SMTP Service Extension for 8bit-MIMEtransport\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo defines an extension to the SMTP service whereby an SMTP\n content body consisting of text containing octets outside of the US-\n ASCII octet range (hex 00-7F) may be relayed using SMTP.\n\n1.","scope_keywords":["1652","algorithm","delivery","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null}],"search_text":"IETF RFC 1652 Network Working Group J. Klensin, WG Chair\nRequest for Comments: 1652 MCI\nObsoletes: 1426 N. Freed, Editor\nCategory: Standards Track Innosoft\n M. Rose\n Dover Beach Consulting, Inc.\n E. Stefferud\n Network Management Associates, Inc.\n D. Crocker\n Silicon Graphics, Inc.\n July 1994\n\n SMTP Service Extension for 8bit-MIMEtransport\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo defines an extension to the SMTP service whereby an SMTP\n content body consisting of text containing octets outside of the US-\n ASCII octet range (hex 00-7F) may be relayed using SMTP.\n\n1. 1652 algorithm delivery key management subject nested-reference unchanged"},{"id":"IETF RFC 1653","type":"specification","body":"IETF","designation":"RFC 1653","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1653.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1653.txt","https://www.rfc-editor.org/rfc/rfc1653.pdf"],"folder":"IETF/RFC-1653","files":{"txt":{"path":"standards/IETF/RFC-1653/RFC-1653.txt","sha256":"c4e10e706b5d2cc023114df14caa71d246111849be13df30aae73177aa148595"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n decline to accept a message (perhaps temporarily) based on the\n client's estimate of the message size.\n\n1. Introduction\n\n The MIME extensions to the Internet message protocol provide for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. One expected result of the use of MIME is that\n SMTP will be expected to carry a much wider range of message sizes\n than was previously the case. This has an impact on the amount of\n resources (e.g., disk space) required by a system acting as a server.\n\n This memo uses the mechanism defined in [5] to define extensions to\n the SMTP service whereby a client (\"sender-SMTP\") may declare the\n size of a particular message to a server (\"receiver-SMTP\"), after\n which the server may indi","scope_keywords":["1653","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null}],"search_text":"IETF RFC 1653 This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n decline to accept a message (perhaps temporarily) based on the\n client's estimate of the message size.\n\n1. Introduction\n\n The MIME extensions to the Internet message protocol provide for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. One expected result of the use of MIME is that\n SMTP will be expected to carry a much wider range of message sizes\n than was previously the case. This has an impact on the amount of\n resources (e.g., disk space) required by a system acting as a server.\n\n This memo uses the mechanism defined in [5] to define extensions to\n the SMTP service whereby a client (\"sender-SMTP\") may declare the\n size of a particular message to a server (\"receiver-SMTP\"), after\n which the server may indi 1653 key presentation nested-reference unchanged"},{"id":"IETF RFC 1714","type":"specification","body":"IETF","designation":"RFC 1714","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1714.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1714.txt","https://www.rfc-editor.org/rfc/rfc1714.pdf"],"folder":"IETF/RFC-1714","files":{"pdf":{"path":"standards/IETF/RFC-1714/RFC-1714.pdf","sha256":"4d40a580637385d4d5aa80aabefdb9f7584dc8e7847b754818e234081ae4d0ed"},"txt":{"path":"standards/IETF/RFC-1714/RFC-1714.txt","sha256":"342c229aee26b650690b5ee58915a19c6bb03715e6816abfd47a2bee8521433e"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes version 1.0 of the client/server interaction of\n RWhois. RWhois provides a distributed system for the display of\n hierarchical information. This system is hierarchical by design,\n allowing for the reduction of a query, and the referral of the user\n closer to the maintainer of the information.","scope_keywords":["1714","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null}],"search_text":"IETF RFC 1714 This memo describes version 1.0 of the client/server interaction of\n RWhois. RWhois provides a distributed system for the display of\n hierarchical information. This system is hierarchical by design,\n allowing for the reduction of a query, and the referral of the user\n closer to the maintainer of the information. 1714 attribute key nested-reference unchanged"},{"id":"IETF RFC 1740","type":"specification","body":"IETF","designation":"RFC 1740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1740.txt","https://www.rfc-editor.org/rfc/rfc1740.pdf"],"folder":"IETF/RFC-1740","files":{"txt":{"path":"standards/IETF/RFC-1740/RFC-1740.txt","sha256":"e2cfcbd49410f9dffae29f4388fb63e92738606156ecafa06bec446cfbaf5f32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Patrik Faltstrom\nRequest for Comments: 1740 Royal Institute of Technology\nCategory: Standards Track Dave Crocker\n Brandenburg Consulting\n Erik E. Fair\n Apple Computer Inc.\n December 1994\n\n MIME Encapsulation of Macintosh files - MacMIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo describes the format to use when sending Apple Macintosh\n files via MIME [BORE93]. The format is compatible with existing\n mechanisms for distributing Macintosh files, while allowing non-\n Macintosh systems access to data in standardized formats.\n\n2. Intro","scope_keywords":["1740","attribute","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1740 Network Working Group Patrik Faltstrom\nRequest for Comments: 1740 Royal Institute of Technology\nCategory: Standards Track Dave Crocker\n Brandenburg Consulting\n Erik E. Fair\n Apple Computer Inc.\n December 1994\n\n MIME Encapsulation of Macintosh files - MacMIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo describes the format to use when sending Apple Macintosh\n files via MIME [BORE93]. The format is compatible with existing\n mechanisms for distributing Macintosh files, while allowing non-\n Macintosh systems access to data in standardized formats.\n\n2. Intro 1740 attribute registered nested-reference unchanged"},{"id":"IETF RFC 1806","type":"specification","body":"IETF","designation":"RFC 1806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1806.txt","https://www.rfc-editor.org/rfc/rfc1806.pdf"],"folder":"IETF/RFC-1806","files":{"txt":{"path":"standards/IETF/RFC-1806/RFC-1806.txt","sha256":"b9013bbc091778a6f1ac3ab528abba232917e463bc7e6254e2f89dca728c59f1"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides a mechanism whereby messages conforming to the\n [RFC 1521] (\"MIME\") specification can convey presentational\n information. It specifies a new \"Content-Disposition\" header,\n optional and valid for any [RFC 1521] entity (\"message\" or \"body\n part\"). Two values for this header are described in this memo; one\n for the ordinary linear presentation of the body part, and another to\n facilitate the use of mail to transfer files. It is expected that\n more values will be defined in the future, and procedures are defined\n for extending this set of values.\n\n This document is intended as an extension to [RFC 1521]. As such, the\n reader is assumed to be familiar with [RFC 1521], and [RFC 822]. The\n information presented herein supplements but does not replace that\n found in those documents.\n\n1. Introduction\n\n [RFC 1521] specifies a standard format for encapsulating multiple\n pieces of","scope_keywords":["1806","path","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1867","folder":"IETF/RFC-1867","source":"IETF/RFC-1867/RFC-1867.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1806 This memo provides a mechanism whereby messages conforming to the\n [RFC 1521] (\"MIME\") specification can convey presentational\n information. It specifies a new \"Content-Disposition\" header,\n optional and valid for any [RFC 1521] entity (\"message\" or \"body\n part\"). Two values for this header are described in this memo; one\n for the ordinary linear presentation of the body part, and another to\n facilitate the use of mail to transfer files. It is expected that\n more values will be defined in the future, and procedures are defined\n for extending this set of values.\n\n This document is intended as an extension to [RFC 1521]. As such, the\n reader is assumed to be familiar with [RFC 1521], and [RFC 822]. The\n information presented herein supplements but does not replace that\n found in those documents.\n\n1. Introduction\n\n [RFC 1521] specifies a standard format for encapsulating multiple\n pieces of 1806 path presentation subject nested-reference unchanged"},{"id":"IETF RFC 1808","type":"specification","body":"IETF","designation":"RFC 1808","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1808.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1808.txt","https://www.rfc-editor.org/rfc/rfc1808.pdf"],"folder":"IETF/RFC-1808","files":{"txt":{"path":"standards/IETF/RFC-1808/RFC-1808.txt","sha256":"ea3895bbf4c7caeccb232f85b71fabd8554b2d93bd5df0260e268426f006657e"}},"tags":["nested-reference","unchanged"],"summary":"A Uniform Resource Locator (URL) is a compact representation of the\n location and access method for a resource available via the Internet.\n When embedded within a base document, a URL in its absolute form may\n contain a great deal of information which is already known from the\n context of that base document's retrieval, including the scheme,\n network location, and parts of the url-path. In situations where the\n base URL is well-defined and known to the parser (human or machine),\n it is useful to be able to embed URL references which inherit that\n context rather than re-specifying it in every instance. This\n document defines the syntax and semantics for such Relative Uniform\n Resource Locators.\n\n1. Introduction\n\n This document describes the syntax and semantics for \"relative\"\n Uniform Resource Locators (relative URLs): a compact representation\n of the location of a resource relative to an","scope_keywords":["1808","http","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2368","folder":"IETF/RFC-2368","source":"IETF/RFC-2368/RFC-2368.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 1808 A Uniform Resource Locator (URL) is a compact representation of the\n location and access method for a resource available via the Internet.\n When embedded within a base document, a URL in its absolute form may\n contain a great deal of information which is already known from the\n context of that base document's retrieval, including the scheme,\n network location, and parts of the url-path. In situations where the\n base URL is well-defined and known to the parser (human or machine),\n it is useful to be able to embed URL references which inherit that\n context rather than re-specifying it in every instance. This\n document defines the syntax and semantics for such Relative Uniform\n Resource Locators.\n\n1. Introduction\n\n This document describes the syntax and semantics for \"relative\"\n Uniform Resource Locators (relative URLs): a compact representation\n of the location of a resource relative to an 1808 http path presentation nested-reference unchanged"},{"id":"IETF RFC 1847","type":"specification","body":"IETF","designation":"RFC 1847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1847.txt","https://www.rfc-editor.org/rfc/rfc1847.pdf"],"folder":"IETF/RFC-1847","files":{"txt":{"path":"standards/IETF/RFC-1847/RFC-1847.txt","sha256":"08cc11e880a7e0ee452649fdc48d8c575d406513ceae45c3d374fd5e7c507828"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework within which security services may\n be applied to MIME body parts. MIME, an acronym for \"Multipurpose\n Internet Mail Extensions\", defines the format of the contents of\n Internet mail messages and provides for multi-part textual and non-\n textual message bodies. The new content types are subtypes of\n multipart: signed and encrypted. Each will contain two body parts:\n one for the protected data and one for the control information\n necessary to remove the protection. The type and contents of the\n control information body parts are determined by the value of the\n protocol parameter of the enclosing multipart/signed or\n multipart/encrypted content type, which is required to be present.","scope_keywords":["1847","algorithm","algorithms","attribute","authentication","encryption","hash","key","management","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 2015","folder":"IETF/RFC-2015","source":"IETF/RFC-2015/RFC-2015.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 1847 This document defines a framework within which security services may\n be applied to MIME body parts. MIME, an acronym for \"Multipurpose\n Internet Mail Extensions\", defines the format of the contents of\n Internet mail messages and provides for multi-part textual and non-\n textual message bodies. The new content types are subtypes of\n multipart: signed and encrypted. Each will contain two body parts:\n one for the protected data and one for the control information\n necessary to remove the protection. The type and contents of the\n control information body parts are determined by the value of the\n protocol parameter of the enclosing multipart/signed or\n multipart/encrypted content type, which is required to be present. 1847 algorithm algorithms attribute authentication encryption hash key management signature trust nested-reference unchanged"},{"id":"IETF RFC 1866","type":"specification","body":"IETF","designation":"RFC 1866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1866.txt","https://www.rfc-editor.org/rfc/rfc1866.pdf"],"folder":"IETF/RFC-1866","files":{"txt":{"path":"standards/IETF/RFC-1866/RFC-1866.txt","sha256":"fb868a2d946c25b621ee8afaa1cbf0e4d609ffc26f88bcd188f9684e9be7152c"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Markup Language (HTML) is a simple markup language used\n to create hypertext documents that are platform independent. HTML\n documents are SGML documents with generic semantics that are\n appropriate for representing information from a wide range of\n domains. HTML markup can represent hypertext news, mail,\n documentation, and hypermedia; menus of options; database query\n results; simple structured documents with in-lined graphics; and\n hypertext views of existing bodies of information.\n\n HTML has been in use by the World Wide Web (WWW) global information\n initiative since 1990. This specification roughly corresponds to the\n capabilities of HTML in common use prior to June 1994. HTML is an\n application of ISO Standard 8879:1986 Information Processing Text and\n Office Systems; Standard Generalized Markup Language (SGML).\n\n The \"text/html\" Internet Media Type (RFC 1590) and MIME","scope_keywords":["1866","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1942","folder":"IETF/RFC-1942","source":"IETF/RFC-1942/RFC-1942.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1980","folder":"IETF/RFC-1980","source":"IETF/RFC-1980/RFC-1980.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2079","folder":"IETF/RFC-2079","source":"IETF/RFC-2079/RFC-2079.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2397","folder":"IETF/RFC-2397","source":"IETF/RFC-2397/RFC-2397.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 1866 The Hypertext Markup Language (HTML) is a simple markup language used\n to create hypertext documents that are platform independent. HTML\n documents are SGML documents with generic semantics that are\n appropriate for representing information from a wide range of\n domains. HTML markup can represent hypertext news, mail,\n documentation, and hypermedia; menus of options; database query\n results; simple structured documents with in-lined graphics; and\n hypertext views of existing bodies of information.\n\n HTML has been in use by the World Wide Web (WWW) global information\n initiative since 1990. This specification roughly corresponds to the\n capabilities of HTML in common use prior to June 1994. HTML is an\n application of ISO Standard 8879:1986 Information Processing Text and\n Office Systems; Standard Generalized Markup Language (SGML).\n\n The \"text/html\" Internet Media Type (RFC 1590) and MIME 1866 attribute presentation nested-reference unchanged"},{"id":"IETF RFC 1867","type":"specification","body":"IETF","designation":"RFC 1867","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1867.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1867.txt","https://www.rfc-editor.org/rfc/rfc1867.pdf"],"folder":"IETF/RFC-1867","files":{"txt":{"path":"standards/IETF/RFC-1867/RFC-1867.txt","sha256":"2392b81ded1fb94f44cda475fb7c4d91dd65ff9aaeb1b150ed7592fb12362fea"}},"tags":["nested-reference","unchanged"],"summary":"Currently, HTML forms allow the producer of the form to request\n information from the user reading the form. These forms have proven\n useful in a wide variety of applications in which input from the user\n is necessary. However, this capability is limited because HTML forms\n don't provide a way to ask the user to submit files of data. Service\n providers who need to get files from the user have had to implement\n custom user applications. (Examples of these custom browsers have\n appeared on the www-talk mailing list.) Since file-upload is a\n feature that will benefit many applications, this proposes an\n extension to HTML to allow information providers to express file\n upload requests uniformly, and a MIME compatible representation for\n file upload responses. This also includes a description of a\n backward compatibility strategy that allows new servers to interact\n with the current HTML user","scope_keywords":["1867","attribute","attributes","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2310","folder":"IETF/RFC-2310","source":"IETF/RFC-2310/RFC-2310.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2586","folder":"IETF/RFC-2586","source":"IETF/RFC-2586/RFC-2586.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null}],"search_text":"IETF RFC 1867 Currently, HTML forms allow the producer of the form to request\n information from the user reading the form. These forms have proven\n useful in a wide variety of applications in which input from the user\n is necessary. However, this capability is limited because HTML forms\n don't provide a way to ask the user to submit files of data. Service\n providers who need to get files from the user have had to implement\n custom user applications. (Examples of these custom browsers have\n appeared on the www-talk mailing list.) Since file-upload is a\n feature that will benefit many applications, this proposes an\n extension to HTML to allow information providers to express file\n upload requests uniformly, and a MIME compatible representation for\n file upload responses. This also includes a description of a\n backward compatibility strategy that allows new servers to interact\n with the current HTML user 1867 attribute attributes http presentation nested-reference unchanged"},{"id":"IETF RFC 1870","type":"specification","body":"IETF","designation":"RFC 1870","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1870.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1870.txt","https://www.rfc-editor.org/rfc/rfc1870.pdf"],"folder":"IETF/RFC-1870","files":{"txt":{"path":"standards/IETF/RFC-1870/RFC-1870.txt","sha256":"7c560c3b4d017beeaf66a9a5c55f6e8449574b33f637c970259e4f54fe6498f9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n decline to accept a message (perhaps temporarily) based on the\n client's estimate of the message size.\n\n2. Introduction\n\n The MIME extensions to the Internet message protocol provide for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. One expected result of the use of MIME is that\n SMTP will be expected to carry a much wider range of message sizes\n than was previously the case. This has an impact on the amount of\n resources (e.g. disk space) required by a system acting as a server.\n\n This memo uses the mechanism defined in [5] to define extensions to\n the SMTP service whereby a client (\"sender-SMTP\") may declare the\n size of a particular message to a server (\"receiver-SMTP\"), after\n which the server may indic","scope_keywords":["1870","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 1870 This memo defines an extension to the SMTP service whereby an SMTP\n client and server may interact to give the server an opportunity to\n decline to accept a message (perhaps temporarily) based on the\n client's estimate of the message size.\n\n2. Introduction\n\n The MIME extensions to the Internet message protocol provide for the\n transmission of many kinds of data which were previously unsupported\n in Internet mail. One expected result of the use of MIME is that\n SMTP will be expected to carry a much wider range of message sizes\n than was previously the case. This has an impact on the amount of\n resources (e.g. disk space) required by a system acting as a server.\n\n This memo uses the mechanism defined in [5] to define extensions to\n the SMTP service whereby a client (\"sender-SMTP\") may declare the\n size of a particular message to a server (\"receiver-SMTP\"), after\n which the server may indic 1870 key presentation nested-reference unchanged"},{"id":"IETF RFC 1872","type":"specification","body":"IETF","designation":"RFC 1872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1872.txt","https://www.rfc-editor.org/rfc/rfc1872.pdf"],"folder":"IETF/RFC-1872","files":{"txt":{"path":"standards/IETF/RFC-1872/RFC-1872.txt","sha256":"37c54ca40734e569f3c2f8609bc0d52976f69d593a3277426651053c61ff7996"}},"tags":["nested-reference","unchanged"],"summary":"The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to ","scope_keywords":["1872","presentation","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null}],"search_text":"IETF RFC 1872 The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to  1872 presentation registered subject nested-reference unchanged"},{"id":"IETF RFC 1873","type":"specification","body":"IETF","designation":"RFC 1873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1873.txt","https://www.rfc-editor.org/rfc/rfc1873.pdf"],"folder":"IETF/RFC-1873","files":{"txt":{"path":"standards/IETF/RFC-1873/RFC-1873.txt","sha256":"f2e5ee066e2c999f79644d94157ae28dea4eb0151512c1b75c6ed5d56bca3581"}},"tags":["nested-reference","unchanged"],"summary":"When using MIME [MIME] to encapsulate a structured object that\n consist of many elements, for example an SGML [SGML] document, a\n single element may occur several times. An encapsulation normally\n maps each of the structured objects elements to a MIME entity. It is\n useful to include elements that occur multiple time exactly once. To\n accomplish that and to preserve the object structure it is desirable\n to unambiguously refer to another body part of the same message.\n\n The existing MIME Content-Type Message/External-Body access-types\n allow a MIME entity (body-part) to refer to an object that is not in\n the message by specifying how to access that object. The Content-ID\n access method described in this document provides the capability to\n refer to an object within the message.\n\n1. Introduction\n\n Consider a MIME multipart entity several of whose body parts contain\n the same data (body) bu","scope_keywords":["1873"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1873 When using MIME [MIME] to encapsulate a structured object that\n consist of many elements, for example an SGML [SGML] document, a\n single element may occur several times. An encapsulation normally\n maps each of the structured objects elements to a MIME entity. It is\n useful to include elements that occur multiple time exactly once. To\n accomplish that and to preserve the object structure it is desirable\n to unambiguously refer to another body part of the same message.\n\n The existing MIME Content-Type Message/External-Body access-types\n allow a MIME entity (body-part) to refer to an object that is not in\n the message by specifying how to access that object. The Content-ID\n access method described in this document provides the capability to\n refer to an object within the message.\n\n1. Introduction\n\n Consider a MIME multipart entity several of whose body parts contain\n the same data (body) bu 1873 nested-reference unchanged"},{"id":"IETF RFC 1874","type":"specification","body":"IETF","designation":"RFC 1874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1874.txt","https://www.rfc-editor.org/rfc/rfc1874.pdf"],"folder":"IETF/RFC-1874","files":{"txt":{"path":"standards/IETF/RFC-1874/RFC-1874.txt","sha256":"05db57c5c21a280cc119347c9995f2118e81b98c067871f7d26fb6b6970acc5e"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes new media sub-types of Text/SGML and\n Application/SGML. These media types can be used in the exchange of\n SGML documents and their entities. Specific details for the exchange\n or encapsulation of groups of related SGML entities using MIME are\n currently being considered by the mimesgml Working Group <sgml-\n internet@ebt.com>.\n\n1. Introduction\n\n A need exists for the transfer the elements of documents constructed\n using the Standard Generalized Markup Language (SGML) [ISO-8879].\n While the specific details of such transfers are being considered\n general agreement exists on the need to register basic media types\n for the SGML entities not covered by existing types.\n\n The Standard Generalized Markup Language (SGML) is used to encode\n document structure and a rigorous description of it is left to [ISO-\n 8879]. The terms used in the present document attempt to be\n consi","scope_keywords":["1874","attribute","presentation","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2111","folder":"IETF/RFC-2111","source":"IETF/RFC-2111/RFC-2111.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null}],"search_text":"IETF RFC 1874 This document proposes new media sub-types of Text/SGML and\n Application/SGML. These media types can be used in the exchange of\n SGML documents and their entities. Specific details for the exchange\n or encapsulation of groups of related SGML entities using MIME are\n currently being considered by the mimesgml Working Group <sgml-\n internet@ebt.com>.\n\n1. Introduction\n\n A need exists for the transfer the elements of documents constructed\n using the Standard Generalized Markup Language (SGML) [ISO-8879].\n While the specific details of such transfers are being considered\n general agreement exists on the need to register basic media types\n for the SGML entities not covered by existing types.\n\n The Standard Generalized Markup Language (SGML) is used to encode\n document structure and a rigorous description of it is left to [ISO-\n 8879]. The terms used in the present document attempt to be\n consi 1874 attribute presentation registered risk nested-reference unchanged"},{"id":"IETF RFC 1892","type":"specification","body":"IETF","designation":"RFC 1892","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1892.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1892.txt","https://www.rfc-editor.org/rfc/rfc1892.pdf"],"folder":"IETF/RFC-1892","files":{"txt":{"path":"standards/IETF/RFC-1892/RFC-1892.txt","sha256":"79a17bd2e9a89063f7b99734363c2ee6604a253606bcef30a720c825f44f2f2c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Vaudreuil\nRequest for Comments: 1892 Octel Network Services\nCategory: Standards Track January 1996\n\n The Multipart/Report Content Type\n for the Reporting of\n Mail System Administrative Messages\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. The Multipart/Report MIME content-type\n\n The Multipart/Report MIME content-type is a general \"family\" or\n \"container\" type for electronic mail reports of any kind. Although\n this memo defines only the use of the Multipart/Report content-type\n with respect to delivery status reports, mail processing programs\n will","scope_keywords":["1892","authentication","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null}],"search_text":"IETF RFC 1892 Network Working Group G. Vaudreuil\nRequest for Comments: 1892 Octel Network Services\nCategory: Standards Track January 1996\n\n The Multipart/Report Content Type\n for the Reporting of\n Mail System Administrative Messages\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. The Multipart/Report MIME content-type\n\n The Multipart/Report MIME content-type is a general \"family\" or\n \"container\" type for electronic mail reports of any kind. Although\n this memo defines only the use of the Multipart/Report content-type\n with respect to delivery status reports, mail processing programs\n will 1892 authentication delivery path nested-reference unchanged"},{"id":"IETF RFC 2017","type":"specification","body":"IETF","designation":"RFC 2017","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2017.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2017.txt","https://www.rfc-editor.org/rfc/rfc2017.pdf"],"folder":"IETF/RFC-2017","files":{"txt":{"path":"standards/IETF/RFC-2017/RFC-2017.txt","sha256":"9b066d4e6e28e7643726be2ee88f0dd2d21b3354f5cdae5f2512409328e1fc68"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new access-type for message/external-body MIME\n parts for Uniform Resource Locators (URLs). URLs provide schemes to\n access external objects via a growing number of protocols, including\n HTTP, Gopher, and TELNET. An initial set of URL schemes are defined\n in RFC 1738.\n\n2. Introduction\n\n The Multipurpose Internet Message Extensions (MIME) define a facility\n whereby an object can contain a reference or pointer to some form of\n data rather than the actual data itself. This facility is embodied in\n the message/external-body media type defined in RFC 1521. Use of\n this facility is growing as a means of conserving bandwidth when\n large objects are sent to large mailing lists.\n\n Each message/external-body reference must specify a mechanism whereby\n the actual data can be retrieved. These mechanisms are called access\n types, and RFC 1521 defines an initial set of access types","scope_keywords":["2017","http","presentation","signature","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null}],"search_text":"IETF RFC 2017 This memo defines a new access-type for message/external-body MIME\n parts for Uniform Resource Locators (URLs). URLs provide schemes to\n access external objects via a growing number of protocols, including\n HTTP, Gopher, and TELNET. An initial set of URL schemes are defined\n in RFC 1738.\n\n2. Introduction\n\n The Multipurpose Internet Message Extensions (MIME) define a facility\n whereby an object can contain a reference or pointer to some form of\n data rather than the actual data itself. This facility is embodied in\n the message/external-body media type defined in RFC 1521. Use of\n this facility is growing as a means of conserving bandwidth when\n large objects are sent to large mailing lists.\n\n Each message/external-body reference must specify a mechanism whereby\n the actual data can be retrieved. These mechanisms are called access\n types, and RFC 1521 defines an initial set of access types 2017 http presentation signature tls tsp nested-reference unchanged"},{"id":"IETF RFC 2044","type":"specification","body":"IETF","designation":"RFC 2044","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2044.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2044.txt","https://www.rfc-editor.org/rfc/rfc2044.pdf"],"folder":"IETF/RFC-2044","files":{"txt":{"path":"standards/IETF/RFC-2044/RFC-2044.txt","sha256":"c729ab5a27ab91a7408ee63ccac8e02e16bd23957f8bd500373d280fd763db07"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Yergeau\nRequest for Comments: 2044 Alis Technologies\nCategory: Informational October 1996\n\n UTF-8, a transformation format of Unicode and ISO 10646\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly\n define a 16 bit character set which encompasses most of the world's\n writing systems. 16-bit characters, however, are not compatible with\n many current applications and protocols, and this has led to the\n development of a few so-called UCS transformation formats (UTF), each\n with different characteristics. UTF-8, the object of this memo, has\n the characteristic of preserving the full US-ASCII range: US-ASCII\n characters are encoded in one octet having the u","scope_keywords":["2044","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null}],"search_text":"IETF RFC 2044 Network Working Group F. Yergeau\nRequest for Comments: 2044 Alis Technologies\nCategory: Informational October 1996\n\n UTF-8, a transformation format of Unicode and ISO 10646\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly\n define a 16 bit character set which encompasses most of the world's\n writing systems. 16-bit characters, however, are not compatible with\n many current applications and protocols, and this has led to the\n development of a few so-called UCS transformation formats (UTF), each\n with different characteristics. UTF-8, the object of this memo, has\n the characteristic of preserving the full US-ASCII range: US-ASCII\n characters are encoded in one octet having the u 2044 algorithm nested-reference unchanged"},{"id":"IETF RFC 2111","type":"specification","body":"IETF","designation":"RFC 2111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2111.txt","https://www.rfc-editor.org/rfc/rfc2111.pdf"],"folder":"IETF/RFC-2111","files":{"txt":{"path":"standards/IETF/RFC-2111/RFC-2111.txt","sha256":"8358abdcbf9207f5e43b38761e7b771245edbaa133d01929efe81d822b56ec5c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Levinson\nRequest for Comments: 2111 XIson, Inc.\nCategory: Standards Track March 1997\n\n Content-ID and Message-ID Uniform Resource Locators\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Uniform Resource Locator (URL) schemes, \"cid:\" and \"mid:\" allow\n references to messages and the body parts of messages. For example,\n within a single multipart message, one HTML body part might include\n embedded references to other parts of the same message.\n\n1. Introduction\n\n The use of [MIME] within email to convey Web pages and their\n associated images","scope_keywords":["2111","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2392","folder":"IETF/RFC-2392","source":"IETF/RFC-2392/RFC-2392.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null}],"search_text":"IETF RFC 2111 Network Working Group E. Levinson\nRequest for Comments: 2111 XIson, Inc.\nCategory: Standards Track March 1997\n\n Content-ID and Message-ID Uniform Resource Locators\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Uniform Resource Locator (URL) schemes, \"cid:\" and \"mid:\" allow\n references to messages and the body parts of messages. For example,\n within a single multipart message, one HTML body part might include\n embedded references to other parts of the same message.\n\n1. Introduction\n\n The use of [MIME] within email to convey Web pages and their\n associated images 2111 subject nested-reference unchanged"},{"id":"IETF RFC 2152","type":"specification","body":"IETF","designation":"RFC 2152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2152.txt","https://www.rfc-editor.org/rfc/rfc2152.pdf"],"folder":"IETF/RFC-2152","files":{"txt":{"path":"standards/IETF/RFC-2152/RFC-2152.txt","sha256":"e6f1fb131889a885c98675777cb0e843cb97b999331c9bc6da7361219c4f13b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Goldsmith\nRequest for Comments: 2152 Apple Computer, Inc.\nObsoletes: RFC 1642 M. Davis\nCategory: Informational Taligent, Inc.\n May 1997\n\n UTF-7\n\n A Mail-Safe Transformation Format of Unicode\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 2.0, and ISO/IEC 10646-1:1993(E) (as\n amended) jointly define a character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 2045 through 2049) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode ","scope_keywords":["2152","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2152 Network Working Group D. Goldsmith\nRequest for Comments: 2152 Apple Computer, Inc.\nObsoletes: RFC 1642 M. Davis\nCategory: Informational Taligent, Inc.\n May 1997\n\n UTF-7\n\n A Mail-Safe Transformation Format of Unicode\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Unicode Standard, version 2.0, and ISO/IEC 10646-1:1993(E) (as\n amended) jointly define a character set (hereafter referred to as\n Unicode) which encompasses most of the world's writing systems.\n However, Internet mail (STD 11, RFC 822) currently supports only 7-\n bit US ASCII as a character set. MIME (RFC 2045 through 2049) extends\n Internet mail to support different media types and character sets,\n and thus could support Unicode in mail messages. MIME neither defines\n Unicode  2152 presentation nested-reference unchanged"},{"id":"IETF RFC 2183","type":"specification","body":"IETF","designation":"RFC 2183","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2183.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2183.txt","https://www.rfc-editor.org/rfc/rfc2183.pdf"],"folder":"IETF/RFC-2183","files":{"txt":{"path":"standards/IETF/RFC-2183/RFC-2183.txt","sha256":"ae813297acfd928d2b8918eb2ee5ca8d73aa5874b568a4051e75f1392f9a7198"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides a mechanism whereby messages conforming to the\n MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC\n 2049] can convey presentational information. It specifies the\n \"Content-Disposition\" header field, which is optional and valid for\n any MIME entity (\"message\" or \"body part\"). Two values for this\n header field are described in this memo; one for the ordinary linear\n presentation of the body part, and another to facilitate the use of\n mail to transfer files. It is expected that more values will be\n defined in the future, and procedures are defined for extending this\n set of values.\n\n This document is intended as an extension to MIME. As such, the\n reader is assumed to be familiar with the MIME specifications, and\n [RFC 822]. The information presented herein supplements but does not\n replace that found in those documents.\n\n This document is a revision to the ","scope_keywords":["2183","attribute","attributes","key","presentation","preservation","subject","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2183 This memo provides a mechanism whereby messages conforming to the\n MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC\n 2049] can convey presentational information. It specifies the\n \"Content-Disposition\" header field, which is optional and valid for\n any MIME entity (\"message\" or \"body part\"). Two values for this\n header field are described in this memo; one for the ordinary linear\n presentation of the body part, and another to facilitate the use of\n mail to transfer files. It is expected that more values will be\n defined in the future, and procedures are defined for extending this\n set of values.\n\n This document is intended as an extension to MIME. As such, the\n reader is assumed to be familiar with the MIME specifications, and\n [RFC 822]. The information presented herein supplements but does not\n replace that found in those documents.\n\n This document is a revision to the  2183 attribute attributes key presentation preservation subject tsp nested-reference unchanged"},{"id":"IETF RFC 2387","type":"specification","body":"IETF","designation":"RFC 2387","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2387.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2387.txt","https://www.rfc-editor.org/rfc/rfc2387.pdf"],"folder":"IETF/RFC-2387","files":{"txt":{"path":"standards/IETF/RFC-2387/RFC-2387.txt","sha256":"b92f065d32e774c1c6cc8d656f5dbf34a71a2714444f2aa7d4e1ad4fa1091aa6"}},"tags":["nested-reference","unchanged"],"summary":"The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to ","scope_keywords":["2387","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2392","folder":"IETF/RFC-2392","source":"IETF/RFC-2392/RFC-2392.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null}],"search_text":"IETF RFC 2387 The Multipart/Related content-type provides a common mechanism for\n representing objects that are aggregates of related MIME body parts.\n This document defines the Multipart/Related content-type and provides\n examples of its use.\n\n1. Introduction\n\n Several applications of MIME, including MIME-PEM, and MIME-Macintosh\n and other proposals, require multiple body parts that make sense only\n in the aggregate. The present approach to these compound objects has\n been to define specific multipart subtypes for each new object. In\n keeping with the MIME philosophy of having one mechanism to achieve\n the same goal for different purposes, this document describes a\n single mechanism for such aggregate or compound objects.\n\n The Multipart/Related content-type addresses the MIME representation\n of compound objects. The object is categorized by a \"type\"\n parameter. Additional parameters are provided to  2387 presentation subject nested-reference unchanged"},{"id":"IETF RFC 1529","type":"specification","body":"IETF","designation":"RFC 1529","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1529.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1529.txt","https://www.rfc-editor.org/rfc/rfc1529.pdf"],"folder":"IETF/RFC-1529","files":{"txt":{"path":"standards/IETF/RFC-1529/RFC-1529.txt","sha256":"471c98fd2aec59603d31673cbdefb9328caa1cc43ad81da393b48ad68593c9eb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Malamud\nRequest for Comments: 1529 Internet Multicasting Service\nObsoletes: 1486 M. Rose\nCategory: Informational Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n Remote Printing -- Administrative Policies\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This document defines the administrative policies for the operation\n of remote printer facilities within the context of the tpc.int\n subdomain. The document describes different approaches to resource\n recovery for remote printer server sites and includes discussions of\n issues pertaining to auditing, security, and denial of access.\n\n The technical procedures for remote printing are defined in [1]. The\n general principles of operation fo","scope_keywords":["1529","audit","authentication","policies","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null}],"search_text":"IETF RFC 1529 Network Working Group C. Malamud\nRequest for Comments: 1529 Internet Multicasting Service\nObsoletes: 1486 M. Rose\nCategory: Informational Dover Beach Consulting, Inc.\n October 1993\n\n Principles of Operation for the TPC.INT Subdomain:\n Remote Printing -- Administrative Policies\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard. Distribution of this memo is\n unlimited.\n\nIntroduction\n\n This document defines the administrative policies for the operation\n of remote printer facilities within the context of the tpc.int\n subdomain. The document describes different approaches to resource\n recovery for remote printer server sites and includes discussions of\n issues pertaining to auditing, security, and denial of access.\n\n The technical procedures for remote printing are defined in [1]. The\n general principles of operation fo 1529 audit authentication policies registered subject nested-reference unchanged"},{"id":"IETF RFC 2302","type":"specification","body":"IETF","designation":"RFC 2302","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2302.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2302.txt","https://www.rfc-editor.org/rfc/rfc2302.pdf"],"folder":"IETF/RFC-2302","files":{"txt":{"path":"standards/IETF/RFC-2302/RFC-2302.txt","sha256":"5397ccedc6ffa4fb5cb129898eb43219cfb3a0156bb3b5e24e84973d9a90aa30"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n image/tiff. The baseline encoding is defined by [TIFF]. This\n document refines an earlier sub-type registration in RFC 1528\n [TPC.INT].\n\n2. TIFF Definition\n\n TIFF (Tag Image File Format) Revision 6.0 is defined in detail by\n Adobe in [TIFF]. The documentation can be obtained from Adobe at:\n\nParsons, et. al. Standards Track [Page 1]\n\f\nRFC 2302 TIFF March 1998\n\n Adobe Developers Association\n Adobe Systems Incorporated\n 345 Park Avenue\n San Jose, CA 95110-2704\n\n Phone: +1-408-536-6000\n Fax: +1-408-537-6000\n\n A copy of this specification can also be found in:\n ftp://ftp.adobe.com/pub/adobe/devrelations/devtechnotes/pdffiles/\n tiff6.pdf\n\n While a brief scope and feature description is provided in this\n section as background information, the reader is directed to the\n original TIFF specification [TIFF] to obtain complete feature an","scope_keywords":["2302","attribute","attributes","identification","profile","profiles","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2301","folder":"IETF/RFC-2301","source":"IETF/RFC-2301/RFC-2301.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2306","folder":"IETF/RFC-2306","source":"IETF/RFC-2306/RFC-2306.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null}],"search_text":"IETF RFC 2302 This document describes the registration of the MIME sub-type\n image/tiff. The baseline encoding is defined by [TIFF]. This\n document refines an earlier sub-type registration in RFC 1528\n [TPC.INT].\n\n2. TIFF Definition\n\n TIFF (Tag Image File Format) Revision 6.0 is defined in detail by\n Adobe in [TIFF]. The documentation can be obtained from Adobe at:\n\nParsons, et. al. Standards Track [Page 1]\n\f\nRFC 2302 TIFF March 1998\n\n Adobe Developers Association\n Adobe Systems Incorporated\n 345 Park Avenue\n San Jose, CA 95110-2704\n\n Phone: +1-408-536-6000\n Fax: +1-408-537-6000\n\n A copy of this specification can also be found in:\n ftp://ftp.adobe.com/pub/adobe/devrelations/devtechnotes/pdffiles/\n tiff6.pdf\n\n While a brief scope and feature description is provided in this\n section as background information, the reader is directed to the\n original TIFF specification [TIFF] to obtain complete feature an 2302 attribute attributes identification profile profiles registered risk subject nested-reference unchanged"},{"id":"IETF RFC 3250","type":"specification","body":"IETF","designation":"RFC 3250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3250.txt","https://www.rfc-editor.org/rfc/rfc3250.pdf"],"folder":"IETF/RFC-3250","files":{"txt":{"path":"standards/IETF/RFC-3250/RFC-3250.txt","sha256":"f5ef206ee18cf94fa48288fe16a33f022644695757d4f5422446b65eda5eb88f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n image/tiff-fx. The encodings are defined by File Format for Internet\n Fax and its extensions.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/tiff-fx. The encodings are defined by File Format for Internet\n Fax [TIFF-FX] and its extensions.\n\n3. Internet Fax Working Group\n\n This document is a product of the IETF Internet Fax Working Group.\n All comments on this document should be forwarded to the email\n distribution list at <ietf-fax@imc.org>.\n\nMcIntyre, et. al. Standards Track [Page 1]\n\f\nRFC 3250 image/tiff-fx September 2002\n\n3. TIFF-FX Definition\n\n TIFF","scope_keywords":["3250","attribute","attributes","key","profile","profiles","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null}],"search_text":"IETF RFC 3250 This document describes the registration of the MIME sub-type\n image/tiff-fx. The encodings are defined by File Format for Internet\n Fax and its extensions.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/tiff-fx. The encodings are defined by File Format for Internet\n Fax [TIFF-FX] and its extensions.\n\n3. Internet Fax Working Group\n\n This document is a product of the IETF Internet Fax Working Group.\n All comments on this document should be forwarded to the email\n distribution list at <ietf-fax@imc.org>.\n\nMcIntyre, et. al. Standards Track [Page 1]\n\f\nRFC 3250 image/tiff-fx September 2002\n\n3. TIFF-FX Definition\n\n TIFF 3250 attribute attributes key profile profiles risk subject nested-reference unchanged"},{"id":"IETF RFC 3302","type":"specification","body":"IETF","designation":"RFC 3302","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3302.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3302.txt","https://www.rfc-editor.org/rfc/rfc3302.pdf"],"folder":"IETF/RFC-3302","files":{"txt":{"path":"standards/IETF/RFC-3302/RFC-3302.txt","sha256":"7a89f5075a9644ca30b2494fc0389a85d59d60c85c4a68626c74a3dca2b35fd6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n image/tiff. This document refines an earlier sub-type registration\n in RFC 1528.\n\n This document obsoletes RFC 2302.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/tiff. The baseline encoding of TIFF (Tag Image File Format) is\n defined by [TIFF].\n\n3. Internet Fax Working Group\n\n This document is a product of the IETF Internet Fax Working Group.\n All comments on this document should be forwarded to the email\n distribution list at <ietf-fax@imc.org>.\n\nParsons & Rafferty Standards Track [Page 1]\n\f\nRFC 3302 image/tiff September 2002\n\n4. TIFF Definition\n\n T","scope_keywords":["3302","attribute","attributes","http","identification","key","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null}],"search_text":"IETF RFC 3302 This document describes the registration of the MIME sub-type\n image/tiff. This document refines an earlier sub-type registration\n in RFC 1528.\n\n This document obsoletes RFC 2302.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/tiff. The baseline encoding of TIFF (Tag Image File Format) is\n defined by [TIFF].\n\n3. Internet Fax Working Group\n\n This document is a product of the IETF Internet Fax Working Group.\n All comments on this document should be forwarded to the email\n distribution list at <ietf-fax@imc.org>.\n\nParsons & Rafferty Standards Track [Page 1]\n\f\nRFC 3302 image/tiff September 2002\n\n4. TIFF Definition\n\n T 3302 attribute attributes http identification key risk subject nested-reference unchanged"},{"id":"IETF RFC 1534","type":"specification","body":"IETF","designation":"RFC 1534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1534.txt","https://www.rfc-editor.org/rfc/rfc1534.pdf"],"folder":"IETF/RFC-1534","files":{"txt":{"path":"standards/IETF/RFC-1534/RFC-1534.txt","sha256":"e82c57f4688aadfb81442959c492788183561d7ec854fec1a27dd844e9b4805e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Droms\nRequest for Comments: 1534 Bucknell University\nCategory: Standards Track October 1993\n\n Interoperation Between DHCP and BOOTP\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n DHCP provides a superset of the functions provided by BOOTP. This\n document describes the interactions between DHCP and BOOTP network\n participants.\n\n1. Introduction\n\n The Dynamic Host Configuration Protocol (DHCP) provides a mechanism\n for transmitting configuration parameters to hosts using the TCP/IP\n protocol suite. The format of DHCP messages is based on the format\n of BOOT","scope_keywords":["1534"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null}],"search_text":"IETF RFC 1534 Network Working Group R. Droms\nRequest for Comments: 1534 Bucknell University\nCategory: Standards Track October 1993\n\n Interoperation Between DHCP and BOOTP\n\nStatus of this Memo\n\n This RFC specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" for the standardization state and status\n of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n DHCP provides a superset of the functions provided by BOOTP. This\n document describes the interactions between DHCP and BOOTP network\n participants.\n\n1. Introduction\n\n The Dynamic Host Configuration Protocol (DHCP) provides a mechanism\n for transmitting configuration parameters to hosts using the TCP/IP\n protocol suite. The format of DHCP messages is based on the format\n of BOOT 1534 nested-reference unchanged"},{"id":"IETF RFC 3527","type":"specification","body":"IETF","designation":"RFC 3527","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3527.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3527.txt","https://www.rfc-editor.org/rfc/rfc3527.pdf"],"folder":"IETF/RFC-3527","files":{"txt":{"path":"standards/IETF/RFC-3527/RFC-3527.txt","sha256":"c07c3b682a7d62630d3095c0f7c15f53a693b1eaecc920fc8b56a71a487b79ff"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the link selection sub-option of the relay-\n agent-information option for the Dynamic Host Configuration Protocol\n (DHCPv4). The giaddr specifies an IP address which determines both a\n subnet, and thereby a link on which a Dynamic Host Configuration\n Protocol (DHCP) client resides as well as an IP address that can be\n used to communicate with the relay agent. The subnet-selection\n option allows the functions of the giaddr to be split so that when\n one entity is performing as a DHCP proxy, it can specify the\n subnet/link from which to allocate an IP address, which is different\n from the IP address with which it desires to communicate with the\n DHCP server. Analogous situations exist where the relay agent needs\n to specify the subnet/link on which a DHCP client resides, which is\n different from an IP address that can be used to communicate with the\n relay agent.\n\n1.","scope_keywords":["3527","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null}],"search_text":"IETF RFC 3527 This document describes the link selection sub-option of the relay-\n agent-information option for the Dynamic Host Configuration Protocol\n (DHCPv4). The giaddr specifies an IP address which determines both a\n subnet, and thereby a link on which a Dynamic Host Configuration\n Protocol (DHCP) client resides as well as an IP address that can be\n used to communicate with the relay agent. The subnet-selection\n option allows the functions of the giaddr to be split so that when\n one entity is performing as a DHCP proxy, it can specify the\n subnet/link from which to allocate an IP address, which is different\n from the IP address with which it desires to communicate with the\n DHCP server. Analogous situations exist where the relay agent needs\n to specify the subnet/link on which a DHCP client resides, which is\n different from an IP address that can be used to communicate with the\n relay agent.\n\n1. 3527 key nested-reference unchanged"},{"id":"IETF RFC 4030","type":"specification","body":"IETF","designation":"RFC 4030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4030.txt","https://www.rfc-editor.org/rfc/rfc4030.pdf"],"folder":"IETF/RFC-4030","files":{"txt":{"path":"standards/IETF/RFC-4030/RFC-4030.txt","sha256":"86ef2c692c1c9b8bbf5d21b00b4de8e82c67463efe62fa249a4e7e4f6c3ed9bd"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) Relay Agent\n Information Option (RFC 3046) conveys information between a DHCP\n Relay Agent and a DHCP server. This specification defines an\n authentication suboption for that option, containing a keyed hash in\n its payload. The suboption supports data integrity and replay\n protection for relayed DHCP messages.\n\nStapp & Lemon Standards Track [Page 1]\n\f\nRFC 4030 Authentication Suboption March 2005","scope_keywords":["4030","algorithm","authentication","hash","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null}],"search_text":"IETF RFC 4030 The Dynamic Host Configuration Protocol (DHCP) Relay Agent\n Information Option (RFC 3046) conveys information between a DHCP\n Relay Agent and a DHCP server. This specification defines an\n authentication suboption for that option, containing a keyed hash in\n its payload. The suboption supports data integrity and replay\n protection for relayed DHCP messages.\n\nStapp & Lemon Standards Track [Page 1]\n\f\nRFC 4030 Authentication Suboption March 2005 4030 algorithm authentication hash key trust nested-reference unchanged"},{"id":"IETF RFC 4388","type":"specification","body":"IETF","designation":"RFC 4388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4388.txt","https://www.rfc-editor.org/rfc/rfc4388.pdf"],"folder":"IETF/RFC-4388","files":{"txt":{"path":"standards/IETF/RFC-4388/RFC-4388.txt","sha256":"3afc0229279ae164bfe8ac0e95469f827dc2df35e1ff2ad681c3ea6191f84eb0"}},"tags":["nested-reference","unchanged"],"summary":"A Dynamic Host Configuration Protocol version 4 (DHCPv4) server is\n the authoritative source of IP addresses that it has provided to\n DHCPv4 clients. Other processes and devices that already make use of\n DHCPv4 may need to access this information. The leasequery protocol\n provides these processes and devices a lightweight way to access IP\n address information.\n\nWoundy & Kinnear Standards Track [Page 1]\n\f\nRFC 4388 DHCP Leasequery February 2006","scope_keywords":["4388"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null}],"search_text":"IETF RFC 4388 A Dynamic Host Configuration Protocol version 4 (DHCPv4) server is\n the authoritative source of IP addresses that it has provided to\n DHCPv4 clients. Other processes and devices that already make use of\n DHCPv4 may need to access this information. The leasequery protocol\n provides these processes and devices a lightweight way to access IP\n address information.\n\nWoundy & Kinnear Standards Track [Page 1]\n\f\nRFC 4388 DHCP Leasequery February 2006 4388 nested-reference unchanged"},{"id":"IETF RFC 6607","type":"specification","body":"IETF","designation":"RFC 6607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6607.txt","https://www.rfc-editor.org/rfc/rfc6607.pdf"],"folder":"IETF/RFC-6607","files":{"txt":{"path":"standards/IETF/RFC-6607/RFC-6607.txt","sha256":"82fede29f151bec916be08d6466fa2b6eba15015dfd02a4bbb0ae4ad6546f186"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a DHCPv4 Virtual Subnet Selection (VSS) option, a\n DHCPv6 VSS option, and the DHCPv4 VSS and VSS-Control sub-options\n carried in the DHCPv4 Relay Agent Information option. These are\n intended for use by DHCP clients, relay agents, and proxy clients in\n situations where VSS information needs to be passed to the DHCP\n server for proper address or prefix allocation to take place.\n\n For the DHCPv4 option and Relay Agent Information sub-options, this\n memo documents and extends existing usage as per RFC 3942. This memo\n updates RFC 3046 regarding details relating to the copying of sub-\n options (see Section 8).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by","scope_keywords":["6607","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null}],"search_text":"IETF RFC 6607 This memo defines a DHCPv4 Virtual Subnet Selection (VSS) option, a\n DHCPv6 VSS option, and the DHCPv4 VSS and VSS-Control sub-options\n carried in the DHCPv4 Relay Agent Information option. These are\n intended for use by DHCP clients, relay agents, and proxy clients in\n situations where VSS information needs to be passed to the DHCP\n server for proper address or prefix allocation to take place.\n\n For the DHCPv4 option and Relay Agent Information sub-options, this\n memo documents and extends existing usage as per RFC 3942. This memo\n updates RFC 3046 regarding details relating to the copying of sub-\n options (see Section 8).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by 6607 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6926","type":"specification","body":"IETF","designation":"RFC 6926","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6926.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6926.txt","https://www.rfc-editor.org/rfc/rfc6926.pdf"],"folder":"IETF/RFC-6926","files":{"txt":{"path":"standards/IETF/RFC-6926/RFC-6926.txt","sha256":"0a1985c7ee48a142d270ff85a0a8f9c181dece6e6beb56133d6b4a4b55a3cc47"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Leasequery\n protocol allows a requestor to request information about DHCPv4\n bindings. This protocol is limited to queries for individual\n bindings. In some situations, individual binding queries may not be\n efficient or even possible. This document extends the DHCPv4\n Leasequery protocol to allow for bulk transfer of DHCPv4 address\n binding data via TCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pro","scope_keywords":["6926","http","license","path","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null}],"search_text":"IETF RFC 6926 The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Leasequery\n protocol allows a requestor to request information about DHCPv4\n bindings. This protocol is limited to queries for individual\n bindings. In some situations, individual binding queries may not be\n efficient or even possible. This document extends the DHCPv4\n Leasequery protocol to allow for bulk transfer of DHCPv4 address\n binding data via TCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pro 6926 http license path pid subject trust nested-reference unchanged"},{"id":"IETF RFC 8213","type":"specification","body":"IETF","designation":"RFC 8213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8213.txt","https://www.rfc-editor.org/rfc/rfc8213.pdf"],"folder":"IETF/RFC-8213","files":{"txt":{"path":"standards/IETF/RFC-8213/RFC-8213.txt","sha256":"7a42be1df08126cea45d422ebf2cd6d2d4368468fda6984a52bba0ab097c0eef"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no\n guidance for how to secure messages exchanged between servers and\n relay agents. The Dynamic Host Configuration Protocol for IPv6\n (DHCPv6) states that IPsec should be used to secure messages\n exchanged between servers and relay agents but does not require\n encryption. With recent concerns about pervasive monitoring and\n other attacks, it is appropriate to require securing relay-to-relay\n and relay-to-server communication for DHCPv6 and relay-to-server\n communication for DHCPv4.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet","scope_keywords":["8213","authentication","encryption","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 8213 The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no\n guidance for how to secure messages exchanged between servers and\n relay agents. The Dynamic Host Configuration Protocol for IPv6\n (DHCPv6) states that IPsec should be used to secure messages\n exchanged between servers and relay agents but does not require\n encryption. With recent concerns about pervasive monitoring and\n other attacks, it is appropriate to require securing relay-to-relay\n and relay-to-server communication for DHCPv6 and relay-to-server\n communication for DHCPv4.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet 8213 authentication encryption http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1550","type":"specification","body":"IETF","designation":"RFC 1550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1550.txt","https://www.rfc-editor.org/rfc/rfc1550.pdf"],"folder":"IETF/RFC-1550","files":{"txt":{"path":"standards/IETF/RFC-1550/RFC-1550.txt","sha256":"7f905691a4f123203107a6b2b590c938ca28865a902c40b38202d979bd2cbc50"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bradner\nRequest for Comments: 1550 Harvard University\nCategory: Informational A. Mankin\n NRL\n December 1993\n\n IP: Next Generation (IPng) White Paper Solicitation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Document Review Process . . . . . . . . . . . . . . . . . . 2\n 3. Document Format Requirement . . . . . . . . . . . . . . . . 2\n 4. Outline for IPng Requirements and Concerns White Papers . . 3\n 5. Engineering considerations . . . . . . . . . . . . . . . . . 3\n 6. Security Considerations . . . . . . . . . . . . . . . . . . 5\n 7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 5\n Appendix A - Formatting Rules (from RFC 15","scope_keywords":["1550"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1667","folder":"IETF/RFC-1667","source":"IETF/RFC-1667/RFC-1667.txt","version":null},{"body":"IETF","designation":"RFC 1668","folder":"IETF/RFC-1668","source":"IETF/RFC-1668/RFC-1668.txt","version":null},{"body":"IETF","designation":"RFC 1669","folder":"IETF/RFC-1669","source":"IETF/RFC-1669/RFC-1669.txt","version":null},{"body":"IETF","designation":"RFC 1670","folder":"IETF/RFC-1670","source":"IETF/RFC-1670/RFC-1670.txt","version":null},{"body":"IETF","designation":"RFC 1671","folder":"IETF/RFC-1671","source":"IETF/RFC-1671/RFC-1671.txt","version":null},{"body":"IETF","designation":"RFC 1672","folder":"IETF/RFC-1672","source":"IETF/RFC-1672/RFC-1672.txt","version":null},{"body":"IETF","designation":"RFC 1673","folder":"IETF/RFC-1673","source":"IETF/RFC-1673/RFC-1673.txt","version":null},{"body":"IETF","designation":"RFC 1674","folder":"IETF/RFC-1674","source":"IETF/RFC-1674/RFC-1674.txt","version":null},{"body":"IETF","designation":"RFC 1675","folder":"IETF/RFC-1675","source":"IETF/RFC-1675/RFC-1675.txt","version":null},{"body":"IETF","designation":"RFC 1676","folder":"IETF/RFC-1676","source":"IETF/RFC-1676/RFC-1676.txt","version":null},{"body":"IETF","designation":"RFC 1677","folder":"IETF/RFC-1677","source":"IETF/RFC-1677/RFC-1677.txt","version":null},{"body":"IETF","designation":"RFC 1678","folder":"IETF/RFC-1678","source":"IETF/RFC-1678/RFC-1678.txt","version":null},{"body":"IETF","designation":"RFC 1679","folder":"IETF/RFC-1679","source":"IETF/RFC-1679/RFC-1679.txt","version":null},{"body":"IETF","designation":"RFC 1680","folder":"IETF/RFC-1680","source":"IETF/RFC-1680/RFC-1680.txt","version":null},{"body":"IETF","designation":"RFC 1681","folder":"IETF/RFC-1681","source":"IETF/RFC-1681/RFC-1681.txt","version":null},{"body":"IETF","designation":"RFC 1682","folder":"IETF/RFC-1682","source":"IETF/RFC-1682/RFC-1682.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1686","folder":"IETF/RFC-1686","source":"IETF/RFC-1686/RFC-1686.txt","version":null},{"body":"IETF","designation":"RFC 1687","folder":"IETF/RFC-1687","source":"IETF/RFC-1687/RFC-1687.txt","version":null},{"body":"IETF","designation":"RFC 1688","folder":"IETF/RFC-1688","source":"IETF/RFC-1688/RFC-1688.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1710","folder":"IETF/RFC-1710","source":"IETF/RFC-1710/RFC-1710.txt","version":null},{"body":"IETF","designation":"RFC 1715","folder":"IETF/RFC-1715","source":"IETF/RFC-1715/RFC-1715.txt","version":null},{"body":"IETF","designation":"RFC 1719","folder":"IETF/RFC-1719","source":"IETF/RFC-1719/RFC-1719.txt","version":null},{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1753","folder":"IETF/RFC-1753","source":"IETF/RFC-1753/RFC-1753.txt","version":null},{"body":"IETF","designation":"RFC 1955","folder":"IETF/RFC-1955","source":"IETF/RFC-1955/RFC-1955.txt","version":null}],"search_text":"IETF RFC 1550 Network Working Group S. Bradner\nRequest for Comments: 1550 Harvard University\nCategory: Informational A. Mankin\n NRL\n December 1993\n\n IP: Next Generation (IPng) White Paper Solicitation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Document Review Process . . . . . . . . . . . . . . . . . . 2\n 3. Document Format Requirement . . . . . . . . . . . . . . . . 2\n 4. Outline for IPng Requirements and Concerns White Papers . . 3\n 5. Engineering considerations . . . . . . . . . . . . . . . . . 3\n 6. Security Considerations . . . . . . . . . . . . . . . . . . 5\n 7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 5\n Appendix A - Formatting Rules (from RFC 15 1550 nested-reference unchanged"},{"id":"IETF RFC 1916","type":"specification","body":"IETF","designation":"RFC 1916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1916.txt","https://www.rfc-editor.org/rfc/rfc1916.pdf"],"folder":"IETF/RFC-1916","files":{"txt":{"path":"standards/IETF/RFC-1916/RFC-1916.txt","sha256":"08a8a32fb59442cbc93c83e44f8ee44af470ed932fecba579c90598afcbbf402"}},"tags":["nested-reference","unchanged"],"summary":"Because of the urgent need for, and substantial difficulty in,\n renumbering IP networks, the PIER working group is compiling a series\n of documents to assist sites in their renumbering efforts. The\n intent of these documents is to provide both educational and\n practical information to the Internet community. To this end the\n working group is soliciting information from organizations that\n already have gone through, or are in the process of going through,\n renumbering efforts. Case studies, tools, and lists of applications\n that require special attention are sought.","scope_keywords":["1916","authentication","http","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 1916 Because of the urgent need for, and substantial difficulty in,\n renumbering IP networks, the PIER working group is compiling a series\n of documents to assist sites in their renumbering efforts. The\n intent of these documents is to provide both educational and\n practical information to the Internet community. To this end the\n working group is soliciting information from organizations that\n already have gone through, or are in the process of going through,\n renumbering efforts. Case studies, tools, and lists of applications\n that require special attention are sought. 1916 authentication http key keys nested-reference unchanged"},{"id":"IETF RFC 2526","type":"specification","body":"IETF","designation":"RFC 2526","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2526.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2526.txt","https://www.rfc-editor.org/rfc/rfc2526.pdf"],"folder":"IETF/RFC-2526","files":{"txt":{"path":"standards/IETF/RFC-2526/RFC-2526.txt","sha256":"b69e1c38da7c45c87824e76433095c2a9f0da417c62c16a78c35f9296c33a94e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Johnson\nRequest for Comments: 2526 Carnegie Mellon University\nCategory: Standards Track S. Deering\n Cisco Systems, Inc.\n March 1999\n\n Reserved IPv6 Subnet Anycast Addresses\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The IP Version 6 addressing architecture defines an \"anycast\" address\n as an IPv6 address that is assigned to one or more network interfaces\n (typically belonging to different nodes), with the property that a\n packet sent to an anycast address","scope_keywords":["2526","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3627","folder":"IETF/RFC-3627","source":"IETF/RFC-3627/RFC-3627.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 2526 Network Working Group D. Johnson\nRequest for Comments: 2526 Carnegie Mellon University\nCategory: Standards Track S. Deering\n Cisco Systems, Inc.\n March 1999\n\n Reserved IPv6 Subnet Anycast Addresses\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The IP Version 6 addressing architecture defines an \"anycast\" address\n as an IPv6 address that is assigned to one or more network interfaces\n (typically belonging to different nodes), with the property that a\n packet sent to an anycast address 2526 key nested-reference unchanged"},{"id":"IETF RFC 3258","type":"specification","body":"IETF","designation":"RFC 3258","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3258.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3258.txt","https://www.rfc-editor.org/rfc/rfc3258.pdf"],"folder":"IETF/RFC-3258","files":{"txt":{"path":"standards/IETF/RFC-3258/RFC-3258.txt","sha256":"348c3780fafc001cc9b8d5d4267e074279538d3f8cd5e57780c43bc57030038e"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a set of practices intended to enable an\n authoritative name server operator to provide access to a single\n named server in multiple locations. The primary motivation for the\n development and deployment of these practices is to increase the\n distribution of Domain Name System (DNS) servers to previously\n under-served areas of the network topology and to reduce the latency\n for DNS query responses in those areas.\n\n1. Introduction\n\n This memo describes a set of practices intended to enable an\n authoritative name server operator to provide access to a single\n named server in multiple locations. The primary motivation for the\n development and deployment of these practices is to increase the\n distribution of DNS servers to previously under-served areas of the\n network topology and to reduce the latency for DNS query responses in\n those areas. This document presumes a one-t","scope_keywords":["3258","authentication","delivery","driving","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4384","folder":"IETF/RFC-4384","source":"IETF/RFC-4384/RFC-4384.txt","version":null},{"body":"IETF","designation":"RFC 4892","folder":"IETF/RFC-4892","source":"IETF/RFC-4892/RFC-4892.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null}],"search_text":"IETF RFC 3258 This memo describes a set of practices intended to enable an\n authoritative name server operator to provide access to a single\n named server in multiple locations. The primary motivation for the\n development and deployment of these practices is to increase the\n distribution of Domain Name System (DNS) servers to previously\n under-served areas of the network topology and to reduce the latency\n for DNS query responses in those areas.\n\n1. Introduction\n\n This memo describes a set of practices intended to enable an\n authoritative name server operator to provide access to a single\n named server in multiple locations. The primary motivation for the\n development and deployment of these practices is to increase the\n distribution of DNS servers to previously under-served areas of the\n network topology and to reduce the latency for DNS query responses in\n those areas. This document presumes a one-t 3258 authentication delivery driving risk nested-reference unchanged"},{"id":"IETF RFC 4339","type":"specification","body":"IETF","designation":"RFC 4339","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4339.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4339.txt","https://www.rfc-editor.org/rfc/rfc4339.pdf"],"folder":"IETF/RFC-4339","files":{"txt":{"path":"standards/IETF/RFC-4339/RFC-4339.txt","sha256":"0faa17b2860bae77ff9d5c683f8c6a10f42ac219f5a1752df0fb5476687e45d0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes three approaches for IPv6 recursive DNS\n server address configuration. It details the operational attributes\n of three solutions: RA option, DHCPv6 option, and well-known anycast\n addresses for recursive DNS servers. Additionally, it suggests the\n deployment scenarios in four kinds of networks (ISP, enterprise,\n 3GPP, and unmanaged networks) considering multi-solution resolution.\n\nJeong Informational [Page 1]\n\f\nRFC 4339 IPv6 Host Configuration of DNS Server February 2006","scope_keywords":["4339","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 4339 This document describes three approaches for IPv6 recursive DNS\n server address configuration. It details the operational attributes\n of three solutions: RA option, DHCPv6 option, and well-known anycast\n addresses for recursive DNS servers. Additionally, it suggests the\n deployment scenarios in four kinds of networks (ISP, enterprise,\n 3GPP, and unmanaged networks) considering multi-solution resolution.\n\nJeong Informational [Page 1]\n\f\nRFC 4339 IPv6 Host Configuration of DNS Server February 2006 4339 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 1549","type":"specification","body":"IETF","designation":"RFC 1549","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1549.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1549.txt","https://www.rfc-editor.org/rfc/rfc1549.pdf"],"folder":"IETF/RFC-1549","files":{"txt":{"path":"standards/IETF/RFC-1549/RFC-1549.txt","sha256":"f97ef361235f858af68ddaf244a53ad3abb0c15feef853dd0c755644214cbfbb"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of HDLC for framing PPP encapsulated\n packets. This document is the product of the Point-to-Point Protocol\n Working Group of the Internet Engineering Task Force (IETF).\n Comments should be submitted to the ietf-ppp@ucdavis.edu mailing\n list.","scope_keywords":["1549","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1570","folder":"IETF/RFC-1570","source":"IETF/RFC-1570/RFC-1570.txt","version":null},{"body":"IETF","designation":"RFC 1598","folder":"IETF/RFC-1598","source":"IETF/RFC-1598/RFC-1598.txt","version":null},{"body":"IETF","designation":"RFC 1618","folder":"IETF/RFC-1618","source":"IETF/RFC-1618/RFC-1618.txt","version":null},{"body":"IETF","designation":"RFC 1619","folder":"IETF/RFC-1619","source":"IETF/RFC-1619/RFC-1619.txt","version":null}],"search_text":"IETF RFC 1549 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of HDLC for framing PPP encapsulated\n packets. This document is the product of the Point-to-Point Protocol\n Working Group of the Internet Engineering Task Force (IETF).\n Comments should be submitted to the ietf-ppp@ucdavis.edu mailing\n list. 1549 pid nested-reference unchanged"},{"id":"IETF RFC 1618","type":"specification","body":"IETF","designation":"RFC 1618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1618.txt","https://www.rfc-editor.org/rfc/rfc1618.pdf"],"folder":"IETF/RFC-1618","files":{"txt":{"path":"standards/IETF/RFC-1618/RFC-1618.txt","sha256":"d4c895176eb5637574c6de680ec32ac39da6a33305ca2cec3392447e697f3cc3"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Integrated Services\n Digital Network (ISDN) switched circuits.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the PPP encapsulation over ISDN point-to-point links. PPP is\n not designed for multi-point or multi-access environments.\n\n \"It is clear that there is never likely to be a single, monolithic,\n worldwide ISDN.\" [3] The goal of this document is to describe a few\n common implementations, chosen from the current wide variety of\n alternatives, in an effort to promote inte","scope_keywords":["1618","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1618 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Integrated Services\n Digital Network (ISDN) switched circuits.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the PPP encapsulation over ISDN point-to-point links. PPP is\n not designed for multi-point or multi-access environments.\n\n \"It is clear that there is never likely to be a single, monolithic,\n worldwide ISDN.\" [3] The goal of this document is to describe a few\n common implementations, chosen from the current wide variety of\n alternatives, in an effort to promote inte 1618 presentation nested-reference unchanged"},{"id":"IETF RFC 1619","type":"specification","body":"IETF","designation":"RFC 1619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1619.txt","https://www.rfc-editor.org/rfc/rfc1619.pdf"],"folder":"IETF/RFC-1619","files":{"txt":{"path":"standards/IETF/RFC-1619/RFC-1619.txt","sha256":"d25a3d86d416ce0a2a0df30817cf6adbc7bb424d33b2e495d42cce55b312b36e"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Synchronous Optical\n Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the PPP encapsulation over high speed private point-to-point\n links, such as intra-campus single-mode fiber which may already be\n installed and unused. Because the PPP encapsulation has relatively\n low overhead, it is anticipated that significantly higher throughput\n can be attained compared to other SONET/SDH payload mappings, at a\n signific","scope_keywords":["1619","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2615","folder":"IETF/RFC-2615","source":"IETF/RFC-2615/RFC-2615.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null}],"search_text":"IETF RFC 1619 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Synchronous Optical\n Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@merit.edu mailing list.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the PPP encapsulation over high speed private point-to-point\n links, such as intra-campus single-mode fiber which may already be\n installed and unused. Because the PPP encapsulation has relatively\n low overhead, it is anticipated that significantly higher throughput\n can be attained compared to other SONET/SDH payload mappings, at a\n signific 1619 path nested-reference unchanged"},{"id":"IETF RFC 155","type":"specification","body":"IETF","designation":"RFC 155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc155.txt","https://www.rfc-editor.org/rfc/rfc155.pdf"],"folder":"IETF/RFC-155","files":{"txt":{"path":"standards/IETF/RFC-155/RFC-155.txt","sha256":"d3573b9bb61c99df7993d94ffa02d98d8dc4d4bfecfdd0c27d705d4b0c27a90f"}},"tags":["nested-reference","unchanged"],"summary":"ARPA NETWORK MAILING LISTS May 1971 RFC 155 NIC 6760\n\n LIST TO RECEIVE RFC'S\n\nNote: This list includes all Network Liaisons and others who should\nreceive initial distribution of formal documents. It supersedes RFC 95,\nand corresponds to Current Directory of Network Participants, NIC 5799.\n\nAMES CCA\n\nJames A. Jeske Richard Winter\nMail Stop 233-10 Computer Corporation of America\nNASA Ames Research Center 565 Technology Square\nMoffett Field, Calif. 94035 Cambridge, Mass. 02139\n\nARC CMU\n\nJohn T. Melvin Harold R. Van Zoeren\nStanford Research Institute Carnegie-Mellon University\nAugmentation Research Center Computer Science Department\n333 Ravenswood Avenue Schenley Park\nMenlo Park, Calif. 94025 Pittsburgh, Pa 15213\n\n HARV\n\nRichard W. Watson Robert Sundberg\nStanford Research Institute Harvard University\nAugmentation Research Center Aiken Computation Laboratory\n333 Ravenswood Avenue 33 Oxford St","scope_keywords":["155"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 168","folder":"IETF/RFC-168","source":"IETF/RFC-168/RFC-168.txt","version":null}],"search_text":"IETF RFC 155 ARPA NETWORK MAILING LISTS May 1971 RFC 155 NIC 6760\n\n LIST TO RECEIVE RFC'S\n\nNote: This list includes all Network Liaisons and others who should\nreceive initial distribution of formal documents. It supersedes RFC 95,\nand corresponds to Current Directory of Network Participants, NIC 5799.\n\nAMES CCA\n\nJames A. Jeske Richard Winter\nMail Stop 233-10 Computer Corporation of America\nNASA Ames Research Center 565 Technology Square\nMoffett Field, Calif. 94035 Cambridge, Mass. 02139\n\nARC CMU\n\nJohn T. Melvin Harold R. Van Zoeren\nStanford Research Institute Carnegie-Mellon University\nAugmentation Research Center Computer Science Department\n333 Ravenswood Avenue Schenley Park\nMenlo Park, Calif. 94025 Pittsburgh, Pa 15213\n\n HARV\n\nRichard W. Watson Robert Sundberg\nStanford Research Institute Harvard University\nAugmentation Research Center Aiken Computation Laboratory\n333 Ravenswood Avenue 33 Oxford St 155 nested-reference unchanged"},{"id":"IETF RFC 168","type":"specification","body":"IETF","designation":"RFC 168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc168.txt","https://www.rfc-editor.org/rfc/rfc168.pdf"],"folder":"IETF/RFC-168","files":{"txt":{"path":"standards/IETF/RFC-168/RFC-168.txt","sha256":"381a42a5204fe8e627b7a8acdca103a3aa0dea15cf68348e53ff54f68f896b03"}},"tags":["nested-reference","unchanged"],"summary":"RFC 168 Arpa Network Mailing Lists 26 May 1971\n\nThe following three lists are those to be used for distribution of\nNetwork documents. List A should be used by sites when they distribute\ntheir own documents. to get RFC's to Liaisons as quickly as possible.\nAll but local mail should be sent Air Mail. Lists B and C will be used\nby NIC in making distribution of copies to non-site Network Participants\nand to Station Agents. These Lists supercede RPC 95 and RFC 155. For\nphone numbers and lists of names by sites see the Current Directory of\nNetwork Participants.\n\n A. Initial Distribution List\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n documents from NIC.\n\nAMES-ILLIAC CASE\n John McConell Dr. Patrick W. Foulk\n NASA Ames Research Center","scope_keywords":["168"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 211","folder":"IETF/RFC-211","source":"IETF/RFC-211/RFC-211.txt","version":null}],"search_text":"IETF RFC 168 RFC 168 Arpa Network Mailing Lists 26 May 1971\n\nThe following three lists are those to be used for distribution of\nNetwork documents. List A should be used by sites when they distribute\ntheir own documents. to get RFC's to Liaisons as quickly as possible.\nAll but local mail should be sent Air Mail. Lists B and C will be used\nby NIC in making distribution of copies to non-site Network Participants\nand to Station Agents. These Lists supercede RPC 95 and RFC 155. For\nphone numbers and lists of names by sites see the Current Directory of\nNetwork Participants.\n\n A. Initial Distribution List\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n documents from NIC.\n\nAMES-ILLIAC CASE\n John McConell Dr. Patrick W. Foulk\n NASA Ames Research Center 168 nested-reference unchanged"},{"id":"IETF RFC 1669","type":"specification","body":"IETF","designation":"RFC 1669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1669.txt","https://www.rfc-editor.org/rfc/rfc1669.pdf"],"folder":"IETF/RFC-1669","files":{"txt":{"path":"standards/IETF/RFC-1669/RFC-1669.txt","sha256":"5e5afa2187a1947e55712a24739af2d40aeb6592894ecf2a2a051e0927a5ab0f"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.","scope_keywords":["1669","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null}],"search_text":"IETF RFC 1669 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list. 1669 delivery nested-reference unchanged"},{"id":"IETF RFC 1670","type":"specification","body":"IETF","designation":"RFC 1670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1670.txt","https://www.rfc-editor.org/rfc/rfc1670.pdf"],"folder":"IETF/RFC-1670","files":{"txt":{"path":"standards/IETF/RFC-1670/RFC-1670.txt","sha256":"6651cf094ee18eca7eafceba2bff9bc4f19ece851b43f377fb5eed52e4159055"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Heagerty\nRequest for Comments: 1670 CERN\nCategory: Informational August 1994\n\n Input to IPng Engineering Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper expresses some personal opinions on IPng engineering\n considerations, based on experience with DECnet Phase V transition.\n It suggests breaking down the IPng decisions and transition tasks\n into smaller parts so they can be tackled early by the relevant\n experts.\n\nTimesca","scope_keywords":["1670","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1670 Network Working Group D. Heagerty\nRequest for Comments: 1670 CERN\nCategory: Informational August 1994\n\n Input to IPng Engineering Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper expresses some personal opinions on IPng engineering\n considerations, based on experience with DECnet Phase V transition.\n It suggests breaking down the IPng decisions and transition tasks\n into smaller parts so they can be tackled early by the relevant\n experts.\n\nTimesca 1670 key management nested-reference unchanged"},{"id":"IETF RFC 1671","type":"specification","body":"IETF","designation":"RFC 1671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1671.txt","https://www.rfc-editor.org/rfc/rfc1671.pdf"],"folder":"IETF/RFC-1671","files":{"txt":{"path":"standards/IETF/RFC-1671/RFC-1671.txt","sha256":"f4beb3b4ef635a0bf4a92776fb40d467d6bf67af19cf3ff9551c6f9b558b96d9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Carpenter\nRequest for Comments: 1671 CERN\nCategory: Informational August 1994\n\n IPng White Paper on Transition and Other Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper outlines some general requirements for IPng in\n selected areas. It identifies the following requirements for stepwise\n transition:\n\n A) Interworking at every stage and every layer.\n B) Header translation considered harmful\n C) Coexistence.\n D) IPv4 to IPng","scope_keywords":["1671","management","path","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1672","folder":"IETF/RFC-1672","source":"IETF/RFC-1672/RFC-1672.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null}],"search_text":"IETF RFC 1671 Network Working Group B. Carpenter\nRequest for Comments: 1671 CERN\nCategory: Informational August 1994\n\n IPng White Paper on Transition and Other Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nSummary\n\n This white paper outlines some general requirements for IPng in\n selected areas. It identifies the following requirements for stepwise\n transition:\n\n A) Interworking at every stage and every layer.\n B) Header translation considered harmful\n C) Coexistence.\n D) IPv4 to IPng 1671 management path policy risk nested-reference unchanged"},{"id":"IETF RFC 1674","type":"specification","body":"IETF","designation":"RFC 1674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1674.txt","https://www.rfc-editor.org/rfc/rfc1674.pdf"],"folder":"IETF/RFC-1674","files":{"txt":{"path":"standards/IETF/RFC-1674/RFC-1674.txt","sha256":"5b0e1042cf7bb8bde17435de0eee9a04543629e00dfe5a3a5cc7b82d485c6fe6"}},"tags":["nested-reference","unchanged"],"summary":"This memo is a response to RFC 1550, \"IP: Next Generation (IPng)\n White Paper Solicitation\". The statements in this paper are intended\n as input to the technical discussions within IETF, and do not\n represent any endorsement or commitment on the part of the cellular\n industry, the Cellular Digital Packet Data (CDPD) consortium of\n service providers or any of its constituent companies.","scope_keywords":["1674","authentication","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1674 This memo is a response to RFC 1550, \"IP: Next Generation (IPng)\n White Paper Solicitation\". The statements in this paper are intended\n as input to the technical discussions within IETF, and do not\n represent any endorsement or commitment on the part of the cellular\n industry, the Cellular Digital Packet Data (CDPD) consortium of\n service providers or any of its constituent companies. 1674 authentication pid policy nested-reference unchanged"},{"id":"IETF RFC 1675","type":"specification","body":"IETF","designation":"RFC 1675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1675.txt","https://www.rfc-editor.org/rfc/rfc1675.pdf"],"folder":"IETF/RFC-1675","files":{"txt":{"path":"standards/IETF/RFC-1675/RFC-1675.txt","sha256":"346566975800969ae40d254f184e3091cd8a5c58492cc0d65008f9e4cb5d87eb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bellovin\nRequest for Comments: 1675 AT&T Bell Laboratories\nCategory: Informational August 1994\n\n Security Concerns for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview and Rationale\n\n A number of the candidates for IPng have some features that are\n somewhat worrisome from a security perspective. While it is not\n necessary that IPng be an improvement over IPv4, it is mandatory that\n it not make things worse. Below, I outline a number of areas of\n conc","scope_keywords":["1675","authentication","encryption","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1675 Network Working Group S. Bellovin\nRequest for Comments: 1675 AT&T Bell Laboratories\nCategory: Informational August 1994\n\n Security Concerns for IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview and Rationale\n\n A number of the candidates for IPng have some features that are\n somewhat worrisome from a security perspective. While it is not\n necessary that IPng be an improvement over IPv4, it is mandatory that\n it not make things worse. Below, I outline a number of areas of\n conc 1675 authentication encryption trust nested-reference unchanged"},{"id":"IETF RFC 1676","type":"specification","body":"IETF","designation":"RFC 1676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1676.txt","https://www.rfc-editor.org/rfc/rfc1676.pdf"],"folder":"IETF/RFC-1676","files":{"txt":{"path":"standards/IETF/RFC-1676/RFC-1676.txt","sha256":"4059fb8df8721e1d1d97d68f3a47ee936d468b0c81130066c19ba97e62d1f518"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Ghiselli\nRequest for Comments: 1676 D. Salomoni\nCategory: Informational C. Vistoli\n INFN/CNAF\n August 1994\n\n INFN Requirements for an IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nOverview\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nAbstract\n\n This white paper is sent by INFN network team, the Italian National\n Institute for nuclear physics, whose network, named INFNet, is a\n nationwide network founded to provide the access to existing national\n and international HEP laboratory and to facilitate communicatio","scope_keywords":["1676","algorithm","key","management","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1676 Network Working Group A. Ghiselli\nRequest for Comments: 1676 D. Salomoni\nCategory: Informational C. Vistoli\n INFN/CNAF\n August 1994\n\n INFN Requirements for an IPng\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nOverview\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nAbstract\n\n This white paper is sent by INFN network team, the Italian National\n Institute for nuclear physics, whose network, named INFNet, is a\n nationwide network founded to provide the access to existing national\n and international HEP laboratory and to facilitate communicatio 1676 algorithm key management pid policy nested-reference unchanged"},{"id":"IETF RFC 1677","type":"specification","body":"IETF","designation":"RFC 1677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1677.txt","https://www.rfc-editor.org/rfc/rfc1677.pdf"],"folder":"IETF/RFC-1677","files":{"txt":{"path":"standards/IETF/RFC-1677/RFC-1677.txt","sha256":"c49aeca69ce489727308f634bb2cf6f473680ffd435d96a92d729d823c0424ae"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The U.S. Navy has several efforts exploring the applicability of\n commercial internetworking technology to tactical RF networks. Some\n these include the NATO Communication System Network Interoperability\n (CSNI) project, the Naval Research Laboratory Data/Voice Integration\n Advanced Technology Demonstration (D/V ATD), and the Navy\n Communication Support System (CSS) architecture development.\n\n Critical requirements have been identified for security, mobility,\n real-time data delivery applications, multicast, and quality-of-\n service and policy based routing. Address scaling for Navy\n application of internet techno","scope_keywords":["1677","delivery","key","management","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 2501","folder":"IETF/RFC-2501","source":"IETF/RFC-2501/RFC-2501.txt","version":null}],"search_text":"IETF RFC 1677 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The U.S. Navy has several efforts exploring the applicability of\n commercial internetworking technology to tactical RF networks. Some\n these include the NATO Communication System Network Interoperability\n (CSNI) project, the Naval Research Laboratory Data/Voice Integration\n Advanced Technology Demonstration (D/V ATD), and the Navy\n Communication Support System (CSS) architecture development.\n\n Critical requirements have been identified for security, mobility,\n real-time data delivery applications, multicast, and quality-of-\n service and policy based routing. Address scaling for Navy\n application of internet techno 1677 delivery key management pid policy nested-reference unchanged"},{"id":"IETF RFC 1679","type":"specification","body":"IETF","designation":"RFC 1679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1679.txt","https://www.rfc-editor.org/rfc/rfc1679.pdf"],"folder":"IETF/RFC-1679","files":{"txt":{"path":"standards/IETF/RFC-1679/RFC-1679.txt","sha256":"1764045732170344063f757203c9fd51160cbe6cb182dad043bed7e69fda0a78"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The Navy's High Performance Network (HPN) working group has studied\n the requirements of mission critical applications on Navy platforms.\n Based on this study, three basic categories of issues for IPng have\n been identified. The assumptions identified include accommodation of\n current functionality, commercial viability, and transitioning. The\n general requirements identified include addressing, integrated\n services architecture, mobility, multicast, and rapid route\n reconfiguration. Finally, the additional considerations identified\n include fault tolerance, policy based routing, security, and time\n synchroniztion","scope_keywords":["1679","identification","key","management","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1679 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n The Navy's High Performance Network (HPN) working group has studied\n the requirements of mission critical applications on Navy platforms.\n Based on this study, three basic categories of issues for IPng have\n been identified. The assumptions identified include accommodation of\n current functionality, commercial viability, and transitioning. The\n general requirements identified include addressing, integrated\n services architecture, mobility, multicast, and rapid route\n reconfiguration. Finally, the additional considerations identified\n include fault tolerance, policy based routing, security, and time\n synchroniztion 1679 identification key management pid policy nested-reference unchanged"},{"id":"IETF RFC 1680","type":"specification","body":"IETF","designation":"RFC 1680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1680.txt","https://www.rfc-editor.org/rfc/rfc1680.pdf"],"folder":"IETF/RFC-1680","files":{"txt":{"path":"standards/IETF/RFC-1680/RFC-1680.txt","sha256":"62566dc94b14687c24459aad8ee8275938168738e781d15bf85de96add5e3ccd"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n This white paper describes engineering considerations for IPng as\n solicited by RFC 1550 [1]. IPng should provide support for existing\n and emerging link technologies that it will be transported over. Link\n technologies like Ethernet simply multiplex traffic from upper layer\n protocols onto a single channel. \"Sophisticated\" link technologies\n like ATM are emerging in the marketplace allowing several virtual\n channels to be established over a single wire (or fiber) potentially\n based on an applications' network performance objectives.\n\n Support for both \"sophisticated\" (ATM) and existing link technologies\n needs to","scope_keywords":["1680"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1680 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nExecutive Summary\n\n This white paper describes engineering considerations for IPng as\n solicited by RFC 1550 [1]. IPng should provide support for existing\n and emerging link technologies that it will be transported over. Link\n technologies like Ethernet simply multiplex traffic from upper layer\n protocols onto a single channel. \"Sophisticated\" link technologies\n like ATM are emerging in the marketplace allowing several virtual\n channels to be established over a single wire (or fiber) potentially\n based on an applications' network performance objectives.\n\n Support for both \"sophisticated\" (ATM) and existing link technologies\n needs to 1680 nested-reference unchanged"},{"id":"IETF RFC 1681","type":"specification","body":"IETF","designation":"RFC 1681","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1681.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1681.txt","https://www.rfc-editor.org/rfc/rfc1681.pdf"],"folder":"IETF/RFC-1681","files":{"txt":{"path":"standards/IETF/RFC-1681/RFC-1681.txt","sha256":"87b9a6c4b6995df5719439227f599f28b423598985497bc2fc2e32f66daaa4d1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bellovin\nRequest for Comments: 1681 AT&T Bell Laboratories\nCategory: Informational August 1994\n\n On Many Addresses per Host\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview and Rational\n\n Currently, most hosts have only one address. With comparatively rare\n exceptions, hosts as hosts -- as opposed to hosts acting as routers\n or PPP servers -- are single-homed. Our address space calculations\n reflect this; we are assuming that we can estimate the size of t","scope_keywords":["1681","algorithm","authentication","policies","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1681 Network Working Group S. Bellovin\nRequest for Comments: 1681 AT&T Bell Laboratories\nCategory: Informational August 1994\n\n On Many Addresses per Host\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview and Rational\n\n Currently, most hosts have only one address. With comparatively rare\n exceptions, hosts as hosts -- as opposed to hosts acting as routers\n or PPP servers -- are single-homed. Our address space calculations\n reflect this; we are assuming that we can estimate the size of t 1681 algorithm authentication policies policy risk nested-reference unchanged"},{"id":"IETF RFC 1682","type":"specification","body":"IETF","designation":"RFC 1682","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1682.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1682.txt","https://www.rfc-editor.org/rfc/rfc1682.pdf"],"folder":"IETF/RFC-1682","files":{"txt":{"path":"standards/IETF/RFC-1682/RFC-1682.txt","sha256":"25f0ecd13a900db205c60a50145b424fcb91b4396afc5a4da24768b9134e31d1"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview\n\n This IPng white paper, IPng BSD Host Implementation Analysis,\n was submitted to the IPng Directorate to provide a BSD host point of\n reference to assist with the engineering considerations during the\n IETF process to select an IPng proposal. The University of\n California Berkeley Software Distribution (BSD) TCP/IP (4.3 + 4.4)\n system implementation on a host is used as a point of reference for\n the paper.\n\n This document only reflects the author's personal analysis based on\n research and implementation experience for IPng, and does not\n represent any product or future product from any host vendor. Nor\n should it be constru","scope_keywords":["1682","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1682 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nOverview\n\n This IPng white paper, IPng BSD Host Implementation Analysis,\n was submitted to the IPng Directorate to provide a BSD host point of\n reference to assist with the engineering considerations during the\n IETF process to select an IPng proposal. The University of\n California Berkeley Software Distribution (BSD) TCP/IP (4.3 + 4.4)\n system implementation on a host is used as a point of reference for\n the paper.\n\n This document only reflects the author's personal analysis based on\n research and implementation experience for IPng, and does not\n represent any product or future product from any host vendor. Nor\n should it be constru 1682 management nested-reference unchanged"},{"id":"IETF RFC 1686","type":"specification","body":"IETF","designation":"RFC 1686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1686.txt","https://www.rfc-editor.org/rfc/rfc1686.pdf"],"folder":"IETF/RFC-1686","files":{"txt":{"path":"standards/IETF/RFC-1686/RFC-1686.txt","sha256":"ba7328fde06e225f818241708767b0b765560b657e7e095552fa99c13c20016d"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. The statements in this\n paper are intended as input to the technical discussions within IETF,\n and do not represent any endorsement or commitment on the part of the\n cable television industry or any of its companies. Comments should\n be submitted to the big-internet@munnari.oz.au mailing list.","scope_keywords":["1686","delivery","driving","management","pid","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1686 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. The statements in this\n paper are intended as input to the technical discussions within IETF,\n and do not represent any endorsement or commitment on the part of the\n cable television industry or any of its companies. Comments should\n be submitted to the big-internet@munnari.oz.au mailing list. 1686 delivery driving management pid policy risk nested-reference unchanged"},{"id":"IETF RFC 1687","type":"specification","body":"IETF","designation":"RFC 1687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1687.txt","https://www.rfc-editor.org/rfc/rfc1687.pdf"],"folder":"IETF/RFC-1687","files":{"txt":{"path":"standards/IETF/RFC-1687/RFC-1687.txt","sha256":"8477d58d2f6f6b437d268949ff309fd1e0080ea1c1f21970b15051f43d64c45e"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nDisclaimer and Acknowledgments\n\n Much of this draft has been adapted from the article \"A User's View\n of IPng\" by Eric Fleischman which was published in the September 1993\n edition of ConneXions Magazine (Volume 7, Number 9, pages 36 - 40).\n The original ConneXions article represented an official position of\n The Boeing Company on IPng issues. This memo is an expansion of that\n original treatment. This version also represents a Boeing corporate\n opinion which we hope will be helpful to the on-going IPng\n discussions. An assumption of this paper is that other Fortune 100\n companies which have non-computing-related products and service","scope_keywords":["1687","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1687 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\nDisclaimer and Acknowledgments\n\n Much of this draft has been adapted from the article \"A User's View\n of IPng\" by Eric Fleischman which was published in the September 1993\n edition of ConneXions Magazine (Volume 7, Number 9, pages 36 - 40).\n The original ConneXions article represented an official position of\n The Boeing Company on IPng issues. This memo is an expansion of that\n original treatment. This version also represents a Boeing corporate\n opinion which we hope will be helpful to the on-going IPng\n discussions. An assumption of this paper is that other Fortune 100\n companies which have non-computing-related products and service 1687 key management nested-reference unchanged"},{"id":"IETF RFC 1688","type":"specification","body":"IETF","designation":"RFC 1688","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1688.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1688.txt","https://www.rfc-editor.org/rfc/rfc1688.pdf"],"folder":"IETF/RFC-1688","files":{"txt":{"path":"standards/IETF/RFC-1688/RFC-1688.txt","sha256":"5d2a87528a3ee0ad96aac54a665db66266e9be45ff8ba8bb037fe7f24f021233"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP.","scope_keywords":["1688","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null}],"search_text":"IETF RFC 1688 This document was submitted to the IPng Area in response to RFC 1550.\n Publication of this document does not imply acceptance by the IPng\n Area of any ideas expressed within. Comments should be submitted to\n the big-internet@munnari.oz.au mailing list. This RFC specifies\n criteria related to mobility for consideration in design and\n selection of the Next Generation of IP. 1688 authentication path nested-reference unchanged"},{"id":"IETF RFC 1753","type":"specification","body":"IETF","designation":"RFC 1753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1753.txt","https://www.rfc-editor.org/rfc/rfc1753.pdf"],"folder":"IETF/RFC-1753","files":{"txt":{"path":"standards/IETF/RFC-1753/RFC-1753.txt","sha256":"fbd4fd47e9adcd2474f9199cf15a6b239a5d63afed9c8d21061540051d54901a"}},"tags":["nested-reference","unchanged"],"summary":"This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n This document presents the requirements that the Nimrod routing and\n addressing architecture has upon the internetwork layer protocol. To\n be most useful to Nimrod, any protocol selected as the IPng should\n satisfy these requirements. Also presented is some background\n information, consisting of i) information about architectural and\n design principles which might apply to the design of a new\n internetworking layer, and ii) some details of the logic and\n reasoning behind particular requirements.\n\n1. Introduction\n\n It is important to note that this document is not \"IPng Requirements\n for Routing\", as other proposed routing and addres","scope_keywords":["1753","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null}],"search_text":"IETF RFC 1753 This document was submitted to the IETF IPng area in response to RFC\n 1550. Publication of this document does not imply acceptance by the\n IPng area of any ideas expressed within. Comments should be\n submitted to the big-internet@munnari.oz.au mailing list.\n\n This document presents the requirements that the Nimrod routing and\n addressing architecture has upon the internetwork layer protocol. To\n be most useful to Nimrod, any protocol selected as the IPng should\n satisfy these requirements. Also presented is some background\n information, consisting of i) information about architectural and\n design principles which might apply to the design of a new\n internetworking layer, and ii) some details of the logic and\n reasoning behind particular requirements.\n\n1. Introduction\n\n It is important to note that this document is not \"IPng Requirements\n for Routing\", as other proposed routing and addres 1753 identification path nested-reference unchanged"},{"id":"IETF RFC 2376","type":"specification","body":"IETF","designation":"RFC 2376","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2376.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2376.txt","https://www.rfc-editor.org/rfc/rfc2376.pdf"],"folder":"IETF/RFC-2376","files":{"txt":{"path":"standards/IETF/RFC-2376/RFC-2376.txt","sha256":"e205b02bb798eac6cd286935a6b8b69a311da4c49d58e777d6ee1a6c5b3bfe69"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes two new media subtypes, text/xml and\n application/xml, for use in exchanging network entities which are\n conforming Extensible Markup Language (XML). XML entities are\n currently exchanged via the HyperText Transfer Protocol on the World\n Wide Web, are an integral part of the WebDAV protocol for remote web\n authoring, and are expected to have utility in many domains.","scope_keywords":["2376","attribute","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 2376 This document proposes two new media subtypes, text/xml and\n application/xml, for use in exchanging network entities which are\n conforming Extensible Markup Language (XML). XML entities are\n currently exchanged via the HyperText Transfer Protocol on the World\n Wide Web, are an integral part of the WebDAV protocol for remote web\n authoring, and are expected to have utility in many domains. 2376 attribute http key nested-reference unchanged"},{"id":"IETF RFC 7303","type":"specification","body":"IETF","designation":"RFC 7303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7303.txt","https://www.rfc-editor.org/rfc/rfc7303.pdf"],"folder":"IETF/RFC-7303","files":{"txt":{"path":"standards/IETF/RFC-7303/RFC-7303.txt","sha256":"d80c0afc29b563fd159567bf4f97829eed81b84a5c85d18a2263e763eb86b005"}},"tags":["nested-reference","unchanged"],"summary":"This specification standardizes three media types -- application/xml,\n application/xml-external-parsed-entity, and application/xml-dtd --\n for use in exchanging network entities that are related to the\n Extensible Markup Language (XML) while defining text/xml and text/\n xml-external-parsed-entity as aliases for the respective application/\n types. This specification also standardizes the '+xml' suffix for\n naming media types outside of these five types when those media types\n represent XML MIME entities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of R","scope_keywords":["7303","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null}],"search_text":"IETF RFC 7303 This specification standardizes three media types -- application/xml,\n application/xml-external-parsed-entity, and application/xml-dtd --\n for use in exchanging network entities that are related to the\n Extensible Markup Language (XML) while defining text/xml and text/\n xml-external-parsed-entity as aliases for the respective application/\n types. This specification also standardizes the '+xml' suffix for\n naming media types outside of these five types when those media types\n represent XML MIME entities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of R 7303 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 1896","type":"specification","body":"IETF","designation":"RFC 1896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1896.txt","https://www.rfc-editor.org/rfc/rfc1896.pdf"],"folder":"IETF/RFC-1896","files":{"txt":{"path":"standards/IETF/RFC-1896/RFC-1896.txt","sha256":"71ea2fee3ce1f1562e30eeaed3a7e89f151044f762b3aad997a0615882eeebdd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Resnick\nRequest for Comments: 1896 QUALCOMM\nObsoletes: 1523, 1563 A. Walker\nCategory: Informational InterCon\n February 1996\n\n The text/enriched MIME Content-type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n MIME [RFC-1521] defines a format and general framework for the\n representation of a wide variety of data types in Internet mail. This\n document defines one particular type of MIME data, the text/enriched\n MIME type. The text/enriched MIME type is intended to facilitate the\n wider interoperation of simple enriched text across a wide variety of\n hardware and software platforms. This document is only a minor\n revision to the text/enriched MIME type that was first described in\n [RFC-1523] and [RFC-1563], and is onl","scope_keywords":["1896","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null}],"search_text":"IETF RFC 1896 Network Working Group P. Resnick\nRequest for Comments: 1896 QUALCOMM\nObsoletes: 1523, 1563 A. Walker\nCategory: Informational InterCon\n February 1996\n\n The text/enriched MIME Content-type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n MIME [RFC-1521] defines a format and general framework for the\n representation of a wide variety of data types in Internet mail. This\n document defines one particular type of MIME data, the text/enriched\n MIME type. The text/enriched MIME type is intended to facilitate the\n wider interoperation of simple enriched text across a wide variety of\n hardware and software platforms. This document is only a minor\n revision to the text/enriched MIME type that was first described in\n [RFC-1523] and [RFC-1563], and is onl 1896 crl presentation nested-reference unchanged"},{"id":"IETF RFC 1969","type":"specification","body":"IETF","designation":"RFC 1969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1969.txt","https://www.rfc-editor.org/rfc/rfc1969.pdf"],"folder":"IETF/RFC-1969","files":{"txt":{"path":"standards/IETF/RFC-1969/RFC-1969.txt","sha256":"7eaa4232f6cadead89170bafd8449d112b79c7dba10fe75a6409bc4762faece1"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the DES\n standard [5, 6] for encrypting PPP encapsulated packets.\n\nAcknowledgements\n\n The authors extend hearty thanks to Fred Baker of Cisco for helpful\n improvements to the clarity of the document.","scope_keywords":["1969","algorithm","authentication","encryption","key","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null}],"search_text":"IETF RFC 1969 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the DES\n standard [5, 6] for encrypting PPP encapsulated packets.\n\nAcknowledgements\n\n The authors extend hearty thanks to Fred Baker of Cisco for helpful\n improvements to the clarity of the document. 1969 algorithm authentication encryption key pid subject nested-reference unchanged"},{"id":"IETF RFC 1977","type":"specification","body":"IETF","designation":"RFC 1977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1977.txt","https://www.rfc-editor.org/rfc/rfc1977.pdf"],"folder":"IETF/RFC-1977","files":{"txt":{"path":"standards/IETF/RFC-1977/RFC-1977.txt","sha256":"5a6a677d301ee6269d3ffe6f14514d73d829965dacde3a9e4873bd171832949b"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Unix Compress compression\n protocol for compressing PPP encapsulated packets.","scope_keywords":["1977","algorithm","license","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1979","folder":"IETF/RFC-1979","source":"IETF/RFC-1979/RFC-1979.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null}],"search_text":"IETF RFC 1977 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Unix Compress compression\n protocol for compressing PPP encapsulated packets. 1977 algorithm license risk nested-reference unchanged"},{"id":"IETF RFC 1979","type":"specification","body":"IETF","designation":"RFC 1979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1979.txt","https://www.rfc-editor.org/rfc/rfc1979.pdf"],"folder":"IETF/RFC-1979","files":{"txt":{"path":"standards/IETF/RFC-1979/RFC-1979.txt","sha256":"f7792cc60f51fcc12fbdf8f044eb7954d1e5cd91a43bdd89d5e6da6a2f02d086"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the PPP Deflate compression\n protocol for compressing PPP encapsulated packets.","scope_keywords":["1979","algorithm","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null}],"search_text":"IETF RFC 1979 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the PPP Deflate compression\n protocol for compressing PPP encapsulated packets. 1979 algorithm subject nested-reference unchanged"},{"id":"IETF RFC 2419","type":"specification","body":"IETF","designation":"RFC 2419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2419.txt","https://www.rfc-editor.org/rfc/rfc2419.pdf"],"folder":"IETF/RFC-2419","files":{"txt":{"path":"standards/IETF/RFC-2419/RFC-2419.txt","sha256":"2908646bea88dd6835a279415c32bc6439fedf6be76bb7db56db84b0f7517f2b"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the DES\n standard [5, 6] for encrypting PPP encapsulated packets.\n\nAcknowledgements\n\n The authors extend hearty thanks to Fred Baker of Cisco, Philip\n Rakity of Flowpoint, and William Simpson of Daydreamer for helpful\n improvements to the clarity and correctness of the document.","scope_keywords":["2419","algorithm","authentication","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2420","folder":"IETF/RFC-2420","source":"IETF/RFC-2420/RFC-2420.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null}],"search_text":"IETF RFC 2419 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the DES\n standard [5, 6] for encrypting PPP encapsulated packets.\n\nAcknowledgements\n\n The authors extend hearty thanks to Fred Baker of Cisco, Philip\n Rakity of Flowpoint, and William Simpson of Daydreamer for helpful\n improvements to the clarity and correctness of the document. 2419 algorithm authentication encryption key nested-reference unchanged"},{"id":"IETF RFC 2484","type":"specification","body":"IETF","designation":"RFC 2484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2484.txt","https://www.rfc-editor.org/rfc/rfc2484.pdf"],"folder":"IETF/RFC-2484","files":{"txt":{"path":"standards/IETF/RFC-2484/RFC-2484.txt","sha256":"025a3d28884750d75dfa2bfae3a671f1f3e5445a0b747a88deca5743c5e953ac"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol (LCP), which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n Both LCP and Authentication Protocol packets may contain text which\n is intended to be human-readable [2,3,4]. This document defines an\n LCP configuration option for the negotiation of character set and\n language usage, as required by RFC 2277 [5].\n\n2. Specification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [6].\n\n3. Additional LCP Configuration Option\n\n The Configuration Option format and basic options are already defi","scope_keywords":["2484","authentication","http","identification","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2484 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n also defines an extensible Link Control Protocol (LCP), which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n Both LCP and Authentication Protocol packets may contain text which\n is intended to be human-readable [2,3,4]. This document defines an\n LCP configuration option for the negotiation of character set and\n language usage, as required by RFC 2277 [5].\n\n2. Specification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\" are to be interpreted as\n described in [6].\n\n3. Additional LCP Configuration Option\n\n The Configuration Option format and basic options are already defi 2484 authentication http identification key policy nested-reference unchanged"},{"id":"IETF RFC 2989","type":"specification","body":"IETF","designation":"RFC 2989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2989.txt","https://www.rfc-editor.org/rfc/rfc2989.pdf"],"folder":"IETF/RFC-2989","files":{"txt":{"path":"standards/IETF/RFC-2989/RFC-2989.txt","sha256":"b281e2120342039d4b9f3a3b8bde7b749b4134fa5154bd9dc35187ccccefa48f"}},"tags":["nested-reference","unchanged"],"summary":"This document represents a summary of Authentication, Authorization,\n Accounting (AAA) protocol requirements for network access. In\n creating this document, inputs were taken from documents produced by\n the Network Access Server Requirements Next Generation (NASREQ),\n Roaming Operations (ROAMOPS), and MOBILEIP working groups, as well as\n from TIA 45.6.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 2989 Network Access AAA Evaluation Criteria November 2000\n\n This document summarizes the requirements collected from those\n sources, separating requirements for authentication, authorization\n and accounting. Details on the requirements are available in the\n original documents.\n\n1. Introduction\n\n This document represents a summary of AAA protocol requirements for\n network access. In creating this documents, inputs were taken from\n documents produced by the NASREQ [3], ROAMOPS [2], and MOBILEIP [5]","scope_keywords":["2989","audit","authentication","authorization","credential","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2989 This document represents a summary of Authentication, Authorization,\n Accounting (AAA) protocol requirements for network access. In\n creating this document, inputs were taken from documents produced by\n the Network Access Server Requirements Next Generation (NASREQ),\n Roaming Operations (ROAMOPS), and MOBILEIP working groups, as well as\n from TIA 45.6.\n\nAboba, et al. Informational [Page 1]\n\f\nRFC 2989 Network Access AAA Evaluation Criteria November 2000\n\n This document summarizes the requirements collected from those\n sources, separating requirements for authentication, authorization\n and accounting. Details on the requirements are available in the\n original documents.\n\n1. Introduction\n\n This document represents a summary of AAA protocol requirements for\n network access. In creating this documents, inputs were taken from\n documents produced by the NASREQ [3], ROAMOPS [2], and MOBILEIP [5] 2989 audit authentication authorization credential key nested-reference unchanged"},{"id":"IETF RFC 1902","type":"specification","body":"IETF","designation":"RFC 1902","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1902.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1902.txt","https://www.rfc-editor.org/rfc/rfc1902.pdf"],"folder":"IETF/RFC-1902","files":{"txt":{"path":"standards/IETF/RFC-1902/RFC-1902.txt","sha256":"ae93227b199b23ea2478e6140b08136d7bbc3980e8b78acfcb90ae132c5f8107"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group SNMPv2 Working Group\nRequest for Comments: 1902 J. Case\nObsoletes: 1442 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Structure of Management Information\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n A management system contains: several (potentially many) nodes, each\n with a processing entity, termed an agent, which has access to\n mana","scope_keywords":["1902","authentication","authorization","management","path","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1901","folder":"IETF/RFC-1901","source":"IETF/RFC-1901/RFC-1901.txt","version":null},{"body":"IETF","designation":"RFC 1903","folder":"IETF/RFC-1903","source":"IETF/RFC-1903/RFC-1903.txt","version":null},{"body":"IETF","designation":"RFC 1904","folder":"IETF/RFC-1904","source":"IETF/RFC-1904/RFC-1904.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1907","folder":"IETF/RFC-1907","source":"IETF/RFC-1907/RFC-1907.txt","version":null},{"body":"IETF","designation":"RFC 1908","folder":"IETF/RFC-1908","source":"IETF/RFC-1908/RFC-1908.txt","version":null},{"body":"IETF","designation":"RFC 1909","folder":"IETF/RFC-1909","source":"IETF/RFC-1909/RFC-1909.txt","version":null},{"body":"IETF","designation":"RFC 2006","folder":"IETF/RFC-2006","source":"IETF/RFC-2006/RFC-2006.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2012","folder":"IETF/RFC-2012","source":"IETF/RFC-2012/RFC-2012.txt","version":null},{"body":"IETF","designation":"RFC 2013","folder":"IETF/RFC-2013","source":"IETF/RFC-2013/RFC-2013.txt","version":null},{"body":"IETF","designation":"RFC 2020","folder":"IETF/RFC-2020","source":"IETF/RFC-2020/RFC-2020.txt","version":null},{"body":"IETF","designation":"RFC 2021","folder":"IETF/RFC-2021","source":"IETF/RFC-2021/RFC-2021.txt","version":null},{"body":"IETF","designation":"RFC 2037","folder":"IETF/RFC-2037","source":"IETF/RFC-2037/RFC-2037.txt","version":null},{"body":"IETF","designation":"RFC 2064","folder":"IETF/RFC-2064","source":"IETF/RFC-2064/RFC-2064.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2089","folder":"IETF/RFC-2089","source":"IETF/RFC-2089/RFC-2089.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2123","folder":"IETF/RFC-2123","source":"IETF/RFC-2123/RFC-2123.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 2458","folder":"IETF/RFC-2458","source":"IETF/RFC-2458/RFC-2458.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2493","folder":"IETF/RFC-2493","source":"IETF/RFC-2493/RFC-2493.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2514","folder":"IETF/RFC-2514","source":"IETF/RFC-2514/RFC-2514.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1902 Network Working Group SNMPv2 Working Group\nRequest for Comments: 1902 J. Case\nObsoletes: 1442 SNMP Research, Inc.\nCategory: Standards Track K. McCloghrie\n Cisco Systems, Inc.\n M. Rose\n Dover Beach Consulting, Inc.\n S. Waldbusser\n International Network Services\n January 1996\n\n Structure of Management Information\n for Version 2 of the\n Simple Network Management Protocol (SNMPv2)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n A management system contains: several (potentially many) nodes, each\n with a processing entity, termed an agent, which has access to\n mana 1902 authentication authorization management path policies presentation nested-reference unchanged"},{"id":"IETF RFC 3049","type":"specification","body":"IETF","designation":"RFC 3049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3049.txt","https://www.rfc-editor.org/rfc/rfc3049.pdf"],"folder":"IETF/RFC-3049","files":{"txt":{"path":"standards/IETF/RFC-3049/RFC-3049.txt","sha256":"9625066b5899a56f7b79ebe1d74d68b9f97bc0f7a04c5407c3ad503ff4501b40"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the implementation of Service Location\n Protocol (SLP) and session balancing with a TN3270E emulator in a\n client server implementation with a TN3270E server.\n\n Application program developer's can locate TN3270E services and load\n balance among those services (3270 host sessions), by using this SLP\n support.","scope_keywords":["3049","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 3049 This document discusses the implementation of Service Location\n Protocol (SLP) and session balancing with a TN3270E emulator in a\n client server implementation with a TN3270E server.\n\n Application program developer's can locate TN3270E services and load\n balance among those services (3270 host sessions), by using this SLP\n support. 3049 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 2428","type":"specification","body":"IETF","designation":"RFC 2428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2428.txt","https://www.rfc-editor.org/rfc/rfc2428.pdf"],"folder":"IETF/RFC-2428","files":{"txt":{"path":"standards/IETF/RFC-2428/RFC-2428.txt","sha256":"d715138b8fa8eeb0aa8bc3a7428ceb65efdd7127b895d50449956835987ab19d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Allman\nRequest for Comments: 2428 NASA Lewis/Sterling Software\nCategory: Standards Track S. Ostermann\n Ohio University\n C. Metz\n The Inner Net\n September 1998\n\n FTP Extensions for IPv6 and NATs\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The specification for the File Transfer Protocol assumes that the\n underlying network protocol uses a 32-bit network address\n (specifically IP version 4). With the deployment of version 6 of the\n Internet Protocol, network","scope_keywords":["2428","holder","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2428 Network Working Group M. Allman\nRequest for Comments: 2428 NASA Lewis/Sterling Software\nCategory: Standards Track S. Ostermann\n Ohio University\n C. Metz\n The Inner Net\n September 1998\n\n FTP Extensions for IPv6 and NATs\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The specification for the File Transfer Protocol assumes that the\n underlying network protocol uses a 32-bit network address\n (specifically IP version 4). With the deployment of version 6 of the\n Internet Protocol, network 2428 holder key presentation nested-reference unchanged"},{"id":"IETF RFC 2577","type":"specification","body":"IETF","designation":"RFC 2577","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2577.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2577.txt","https://www.rfc-editor.org/rfc/rfc2577.pdf"],"folder":"IETF/RFC-2577","files":{"txt":{"path":"standards/IETF/RFC-2577/RFC-2577.txt","sha256":"8d45a14d53f9d6e8c8a74698d3befb9a64ff30fb9eae0b77f5ba8a06574dfbac"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Allman\nRequest for Comments: 2577 NASA Glenn/Sterling Software\nCategory: Informational S. Ostermann\n Ohio University\n May 1999\n\n FTP Security Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The specification for the File Transfer Protocol (FTP) contains a\n number of mechanisms that can be used to compromise network security.\n The FTP specification allows a client to instruct a server to\n transfer files to a third machine. This third-party mechanism, known\n as proxy FTP, causes a well known security problem. The FTP\n specification also allows an unlimited number of attempts at entering\n a user's password. This allows brute forc","scope_keywords":["2577","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null}],"search_text":"IETF RFC 2577 Network Working Group M. Allman\nRequest for Comments: 2577 NASA Glenn/Sterling Software\nCategory: Informational S. Ostermann\n Ohio University\n May 1999\n\n FTP Security Considerations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The specification for the File Transfer Protocol (FTP) contains a\n number of mechanisms that can be used to compromise network security.\n The FTP specification allows a client to instruct a server to\n transfer files to a third machine. This third-party mechanism, known\n as proxy FTP, causes a well known security problem. The FTP\n specification also allows an unlimited number of attempts at entering\n a user's password. This allows brute forc 2577 trust nested-reference unchanged"},{"id":"IETF RFC 3235","type":"specification","body":"IETF","designation":"RFC 3235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3235.txt","https://www.rfc-editor.org/rfc/rfc3235.pdf"],"folder":"IETF/RFC-3235","files":{"txt":{"path":"standards/IETF/RFC-3235/RFC-3235.txt","sha256":"cd8923ea4db30a866901114c3659974ceabd2bcc3c030734fc14553a111b12e3"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses those things that application designers might\n wish to consider when designing new protocols. While many common\n Internet applications will operate cleanly in the presence of Network\n Address Translators, others suffer from a variety of problems when\n crossing these devices. Guidelines are presented herein to help\n ensure new protocols and applications will, to the extent possible,\n be compatible with NAT (Network Address Translation).\n\n1. Introduction\n\n Other documents that describe Network Address Translation (NAT)\n discuss the Terminology and Considerations [RFC2663] and Protocol\n Issues [RFC3022], [RFC3027] or discuss the implications of NAT\n [RFC2993]. All of those relate to various issues with the NAT\n mechanism, effects on protocols and effects upon general Internet\n architecture.\n\n It is the focus of this document to provide recommendations to\n authors of ","scope_keywords":["3235","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 3235 This document discusses those things that application designers might\n wish to consider when designing new protocols. While many common\n Internet applications will operate cleanly in the presence of Network\n Address Translators, others suffer from a variety of problems when\n crossing these devices. Guidelines are presented herein to help\n ensure new protocols and applications will, to the extent possible,\n be compatible with NAT (Network Address Translation).\n\n1. Introduction\n\n Other documents that describe Network Address Translation (NAT)\n discuss the Terminology and Considerations [RFC2663] and Protocol\n Issues [RFC3022], [RFC3027] or discuss the implications of NAT\n [RFC2993]. All of those relate to various issues with the NAT\n mechanism, effects on protocols and effects upon general Internet\n architecture.\n\n It is the focus of this document to provide recommendations to\n authors of  3235 tls nested-reference unchanged"},{"id":"IETF RFC 4217","type":"specification","body":"IETF","designation":"RFC 4217","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4217.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4217.txt","https://www.rfc-editor.org/rfc/rfc4217.pdf"],"folder":"IETF/RFC-4217","files":{"txt":{"path":"standards/IETF/RFC-4217/RFC-4217.txt","sha256":"01f4e42c696060afb3eef7f52bb48ecfef4984b85472cf051112be2e4f45b37c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that can be used by FTP clients\n and servers to implement security and authentication using the TLS\n protocol defined by RFC 2246, \"The TLS Protocol Version 1.0.\", and\n the extensions to the FTP protocol defined by RFC 2228, \"FTP Security\n Extensions\". It describes the subset of the extensions that are\n required and the parameters to be used, discusses some of the policy\n issues that clients and servers will need to take, considers some of\n the implications of those policies, and discusses some expected\n behaviours of implementations to allow interoperation. This document\n is intended to provide TLS support for FTP in a similar way to that\n provided for SMTP in RFC 2487, \"SMTP Service Extension for Secure\n SMTP over Transport Layer Security\", and HTTP in RFC 2817, \"Upgrading\n to TLS Within HTTP/1.1.\".\n\n This specification is in accordance with RFC 959,","scope_keywords":["4217","attribute","attributes","authentication","certificate","certificates","http","policies","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4217 This document describes a mechanism that can be used by FTP clients\n and servers to implement security and authentication using the TLS\n protocol defined by RFC 2246, \"The TLS Protocol Version 1.0.\", and\n the extensions to the FTP protocol defined by RFC 2228, \"FTP Security\n Extensions\". It describes the subset of the extensions that are\n required and the parameters to be used, discusses some of the policy\n issues that clients and servers will need to take, considers some of\n the implications of those policies, and discusses some expected\n behaviours of implementations to allow interoperation. This document\n is intended to provide TLS support for FTP in a similar way to that\n provided for SMTP in RFC 2487, \"SMTP Service Extension for Secure\n SMTP over Transport Layer Security\", and HTTP in RFC 2817, \"Upgrading\n to TLS Within HTTP/1.1.\".\n\n This specification is in accordance with RFC 959, 4217 attribute attributes authentication certificate certificates http policies policy tls nested-reference unchanged"},{"id":"IETF RFC 196","type":"specification","body":"IETF","designation":"RFC 196","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc196.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc196.txt","https://www.rfc-editor.org/rfc/rfc196.pdf"],"folder":"IETF/RFC-196","files":{"txt":{"path":"standards/IETF/RFC-196/RFC-196.txt","sha256":"1b62aa7d122518017dbac32bee3bf7e42b1d69d760ea35d1a2dc625c4abdde2b"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP Richard W. Watson\nRequest for Comments #196 SRI-ARC\nNIC 7141 July 20, 1971\nCategories: A.5, D.7\nObsoletes: none\nUpdates: none\n\n A MAIL BOX PROTOCOL\n\nThe purpose of this protocol is to provide at each site a\nstandard mechanism to receive sequential files for immediate or\ndeferred printing or other uses. The files for deferred printing\nwould probably be stored on intermediate disk files, although\ndetails of how a file is handled, stored, manipulated, or printed\nat a site are not the concern of this protocol.\n\nIt is also assumed that there would be a program at the sending\nsite which sends the file in the format given below with the\noptional control codes when appropriate. This program could\nprobably be accessed as a subcommand of the Telnet program.\n\nThe motivation for developing this protocol is the Network\nInformation Center's (NIC) need to be able to deliver messag","scope_keywords":["196","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 221","folder":"IETF/RFC-221","source":"IETF/RFC-221/RFC-221.txt","version":null}],"search_text":"IETF RFC 196 NETWORK WORKING GROUP Richard W. Watson\nRequest for Comments #196 SRI-ARC\nNIC 7141 July 20, 1971\nCategories: A.5, D.7\nObsoletes: none\nUpdates: none\n\n A MAIL BOX PROTOCOL\n\nThe purpose of this protocol is to provide at each site a\nstandard mechanism to receive sequential files for immediate or\ndeferred printing or other uses. The files for deferred printing\nwould probably be stored on intermediate disk files, although\ndetails of how a file is handled, stored, manipulated, or printed\nat a site are not the concern of this protocol.\n\nIt is also assumed that there would be a program at the sending\nsite which sends the file in the format given below with the\noptional control codes when appropriate. This program could\nprobably be accessed as a subcommand of the Telnet program.\n\nThe motivation for developing this protocol is the Network\nInformation Center's (NIC) need to be able to deliver messag 196 path nested-reference unchanged"},{"id":"IETF RFC 221","type":"specification","body":"IETF","designation":"RFC 221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc221.txt","https://www.rfc-editor.org/rfc/rfc221.pdf"],"folder":"IETF/RFC-221","files":{"txt":{"path":"standards/IETF/RFC-221/RFC-221.txt","sha256":"8b1948777f278e4d692c8b0ef0c0c7c3018e3f116dade6166f21fa508a0f717d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Watson\nRequest for Comments: 221 SRI-ARC\nNIC: 7612 25 August 1971\n\n A Mail Box Protocol, Version-2\n\nINTRODUCTION\n\n Initial reaction to RFC 196, \"A Mail Box Protocol\", NIC (7141,)\n indicates general agreement on the need for such a mechanism. The\n conventions suggested in RFC 196 assumed only the use of the Data\n Transfer Protocol (in NIC 7104) in order to simplify an initial\n implementation. The valid argument, we believe, has been made that\n sites will also implement the File Transfer Protocol and that as much\n as possible the Mail Box Protocol should be a subset of it. This\n version is in answer to this suggestion.\n\n The purpose of a mail box protocol is to provide at each site a\n standard mechanism to receive sequential files for immediate or\n deferred printing or other uses. The files for deferred printing\n would probably be stored in intermediate disk files,","scope_keywords":["221","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 221 Network Working Group R. Watson\nRequest for Comments: 221 SRI-ARC\nNIC: 7612 25 August 1971\n\n A Mail Box Protocol, Version-2\n\nINTRODUCTION\n\n Initial reaction to RFC 196, \"A Mail Box Protocol\", NIC (7141,)\n indicates general agreement on the need for such a mechanism. The\n conventions suggested in RFC 196 assumed only the use of the Data\n Transfer Protocol (in NIC 7104) in order to simplify an initial\n implementation. The valid argument, we believe, has been made that\n sites will also implement the File Transfer Protocol and that as much\n as possible the Mail Box Protocol should be a subset of it. This\n version is in answer to this suggestion.\n\n The purpose of a mail box protocol is to provide at each site a\n standard mechanism to receive sequential files for immediate or\n deferred printing or other uses. The files for deferred printing\n would probably be stored in intermediate disk files, 221 delivery path nested-reference unchanged"},{"id":"IETF RFC 1587","type":"specification","body":"IETF","designation":"RFC 1587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1587.txt","https://www.rfc-editor.org/rfc/rfc1587.pdf"],"folder":"IETF/RFC-1587","files":{"txt":{"path":"standards/IETF/RFC-1587/RFC-1587.txt","sha256":"2ce2ee4a284801e7468b706a3faf77b83a7b6b0f4547032d3251f96da742bec5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new optional type of OSPF area, somewhat\n humorously referred to as a \"not-so-stubby\" area (or NSSA). NSSAs\n are similar to the existing OSPF stub area configuration option but\n have the additional capability of importing AS external routes in a\n limited fashion.\n\nColtun & Fuller [Page 1]\n\f\nRFC 1587 OSPF NSSA Option March 1994","scope_keywords":["1587"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1765","folder":"IETF/RFC-1765","source":"IETF/RFC-1765/RFC-1765.txt","version":null},{"body":"IETF","designation":"RFC 1793","folder":"IETF/RFC-1793","source":"IETF/RFC-1793/RFC-1793.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2370","folder":"IETF/RFC-2370","source":"IETF/RFC-2370/RFC-2370.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null}],"search_text":"IETF RFC 1587 This document describes a new optional type of OSPF area, somewhat\n humorously referred to as a \"not-so-stubby\" area (or NSSA). NSSAs\n are similar to the existing OSPF stub area configuration option but\n have the additional capability of importing AS external routes in a\n limited fashion.\n\nColtun & Fuller [Page 1]\n\f\nRFC 1587 OSPF NSSA Option March 1994 1587 nested-reference unchanged"},{"id":"IETF RFC 4915","type":"specification","body":"IETF","designation":"RFC 4915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4915.txt","https://www.rfc-editor.org/rfc/rfc4915.pdf"],"folder":"IETF/RFC-4915","files":{"txt":{"path":"standards/IETF/RFC-4915/RFC-4915.txt","sha256":"4ded01912fafe1273b24cac78ac2d11329bb148de149321994066ac874ecab5b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to Open Shortest Path First\n (OSPF) in order to define independent IP topologies called Multi-\n Topologies (MTs). The Multi-Topologies extension can be used for\n computing different paths for unicast traffic, multicast traffic,\n different classes of service based on flexible criteria, or an in-\n band network management topology.\n\n An optional extension to exclude selected links from the default\n topology is also described.\n\nPsenak, et al. Standards Track [Page 1]\n\f\nRFC 4915 Multi-Topology (MT) Routing in OSPF June 2007","scope_keywords":["4915","key","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 4915 This document describes an extension to Open Shortest Path First\n (OSPF) in order to define independent IP topologies called Multi-\n Topologies (MTs). The Multi-Topologies extension can be used for\n computing different paths for unicast traffic, multicast traffic,\n different classes of service based on flexible criteria, or an in-\n band network management topology.\n\n An optional extension to exclude selected links from the default\n topology is also described.\n\nPsenak, et al. Standards Track [Page 1]\n\f\nRFC 4915 Multi-Topology (MT) Routing in OSPF June 2007 4915 key management path trust nested-reference unchanged"},{"id":"IETF RFC 2201","type":"specification","body":"IETF","designation":"RFC 2201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2201.txt","https://www.rfc-editor.org/rfc/rfc2201.pdf"],"folder":"IETF/RFC-2201","files":{"txt":{"path":"standards/IETF/RFC-2201/RFC-2201.txt","sha256":"98298853e3d50b2244e1a8cc0e36ce5f21b72524ad1875b1e29558e0e5c791f2"}},"tags":["nested-reference","unchanged"],"summary":"CBT is a multicast routing architecture that builds a single delivery\n tree per group which is shared by all of the group's senders and\n receivers. Most multicast algorithms build one multicast tree per\n sender (subnetwork), the tree being rooted at the sender's\n subnetwork. The primary advantage of the shared tree approach is\n that it typically offers more favourable scaling characteristics than\n all other multicast algorithms.\n\n The CBT protocol [1] is a network layer multicast routing protocol\n that builds and maintains a shared delivery tree for a multicast\n group. The sending and receiving of multicast data by hosts on a\n subnetwork conforms to the traditional IP multicast service model\n [2].\n\n CBT is progressing through the IDMR working group of the IETF. The\n CBT protocol is described in an accompanying document [1]. For this,\n and all IDMR-related documents, see http://www.cs.ucl","scope_keywords":["2201","algorithm","algorithms","delivery","http","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2189","folder":"IETF/RFC-2189","source":"IETF/RFC-2189/RFC-2189.txt","version":null},{"body":"IETF","designation":"RFC 2902","folder":"IETF/RFC-2902","source":"IETF/RFC-2902/RFC-2902.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null}],"search_text":"IETF RFC 2201 CBT is a multicast routing architecture that builds a single delivery\n tree per group which is shared by all of the group's senders and\n receivers. Most multicast algorithms build one multicast tree per\n sender (subnetwork), the tree being rooted at the sender's\n subnetwork. The primary advantage of the shared tree approach is\n that it typically offers more favourable scaling characteristics than\n all other multicast algorithms.\n\n The CBT protocol [1] is a network layer multicast routing protocol\n that builds and maintains a shared delivery tree for a multicast\n group. The sending and receiving of multicast data by hosts on a\n subnetwork conforms to the traditional IP multicast service model\n [2].\n\n CBT is progressing through the IDMR working group of the IETF. The\n CBT protocol is described in an accompanying document [1]. For this,\n and all IDMR-related documents, see http://www.cs.ucl 2201 algorithm algorithms delivery http path pid nested-reference unchanged"},{"id":"IETF RFC 2370","type":"specification","body":"IETF","designation":"RFC 2370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2370.txt","https://www.rfc-editor.org/rfc/rfc2370.pdf"],"folder":"IETF/RFC-2370","files":{"txt":{"path":"standards/IETF/RFC-2370/RFC-2370.txt","sha256":"4d024b56463adb82b0538d36f7770c34ab08c3a80c25246526ef9ebc03cc6ce2"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines enhancements to the OSPF protocol to support a new\n class of link-state advertisements (LSA) called Opaque LSAs. Opaque\n LSAs provide a generalized mechanism to allow for the future\n extensibility of OSPF. Opaque LSAs consist of a standard LSA header\n followed by application-specific information. The information field\n\nColtun Standards Track [Page 1]\n\f\nRFC 2370 The OSPF Opaque LSA Option July 1998\n\n may be used directly by OSPF or by other applications. Standard OSPF\n link-state database flooding mechanisms are used to distribute Opaque\n LSAs to all or some limited portion of the OSPF topology.","scope_keywords":["2370","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3101","folder":"IETF/RFC-3101","source":"IETF/RFC-3101/RFC-3101.txt","version":null},{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 2370 This memo defines enhancements to the OSPF protocol to support a new\n class of link-state advertisements (LSA) called Opaque LSAs. Opaque\n LSAs provide a generalized mechanism to allow for the future\n extensibility of OSPF. Opaque LSAs consist of a standard LSA header\n followed by application-specific information. The information field\n\nColtun Standards Track [Page 1]\n\f\nRFC 2370 The OSPF Opaque LSA Option July 1998\n\n may be used directly by OSPF or by other applications. Standard OSPF\n link-state database flooding mechanisms are used to distribute Opaque\n LSAs to all or some limited portion of the OSPF topology. 2370 management nested-reference unchanged"},{"id":"IETF RFC 2715","type":"specification","body":"IETF","designation":"RFC 2715","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2715.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2715.txt","https://www.rfc-editor.org/rfc/rfc2715.pdf"],"folder":"IETF/RFC-2715","files":{"txt":{"path":"standards/IETF/RFC-2715/RFC-2715.txt","sha256":"b264a5e91c4cc4dc46c09a9f782348c3c3fad0b10e02fc25f457820326f1f42b"}},"tags":["nested-reference","unchanged"],"summary":"The rules described in this document will allow efficient\n interoperation among multiple independent multicast routing domains.\n Specific instantiations of these rules are given for the DVMRP,\n MOSPF, PIM-DM, PIM-SM, and CBT multicast routing protocols, as well\n as for IGMP-only links. Future versions of these protocols, and any\n other multicast routing protocols, may describe their\n interoperability procedure by stating how the rules described herein\n apply to them.\n\n1. Introduction\n\n To allow sources and receivers inside multiple autonomous multicast\n routing domains (or \"regions\") to communicate, the domains must be\n connected by multicast border routers (MBRs). To prevent black holes\n or routing loops among domains, we assume that these domains are\n organized into one of the following topologies:\n\n o A tree (or star) topology (figure 1) with a backbone domain at the\n root, stub domai","scope_keywords":["2715","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null}],"search_text":"IETF RFC 2715 The rules described in this document will allow efficient\n interoperation among multiple independent multicast routing domains.\n Specific instantiations of these rules are given for the DVMRP,\n MOSPF, PIM-DM, PIM-SM, and CBT multicast routing protocols, as well\n as for IGMP-only links. Future versions of these protocols, and any\n other multicast routing protocols, may describe their\n interoperability procedure by stating how the rules described herein\n apply to them.\n\n1. Introduction\n\n To allow sources and receivers inside multiple autonomous multicast\n routing domains (or \"regions\") to communicate, the domains must be\n connected by multicast border routers (MBRs). To prevent black holes\n or routing loops among domains, we assume that these domains are\n organized into one of the following topologies:\n\n o A tree (or star) topology (figure 1) with a backbone domain at the\n root, stub domai 2715 key path nested-reference unchanged"},{"id":"IETF RFC 3101","type":"specification","body":"IETF","designation":"RFC 3101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3101.txt","https://www.rfc-editor.org/rfc/rfc3101.pdf"],"folder":"IETF/RFC-3101","files":{"txt":{"path":"standards/IETF/RFC-3101/RFC-3101.txt","sha256":"a141c67b0fb67a2ccf5cccf5b45e7657827ca0c3995dd2079908ab98e8a17aaf"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents an optional type of Open Shortest Path First\n (OSPF) area that is somewhat humorously referred to as a \"not-so-\n stubby\" area (or NSSA). NSSAs are similar to the existing OSPF stub\n area configuration option but have the additional capability of\n importing AS external routes in a limited fashion.\n\n The OSPF NSSA Option was originally defined in RFC 1587. The\n functional differences between this memo and RFC 1587 are explained\n in Appendix F. All differences, while expanding capability, are\n backward-compatible in nature. Implementations of this memo and of\n RFC 1587 will interoperate.\n\nMurphy Standards Track [Page 1]\n\f\nRFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option January 2003","scope_keywords":["3101","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 3101 This memo documents an optional type of Open Shortest Path First\n (OSPF) area that is somewhat humorously referred to as a \"not-so-\n stubby\" area (or NSSA). NSSAs are similar to the existing OSPF stub\n area configuration option but have the additional capability of\n importing AS external routes in a limited fashion.\n\n The OSPF NSSA Option was originally defined in RFC 1587. The\n functional differences between this memo and RFC 1587 are explained\n in Appendix F. All differences, while expanding capability, are\n backward-compatible in nature. Implementations of this memo and of\n RFC 1587 will interoperate.\n\nMurphy Standards Track [Page 1]\n\f\nRFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option January 2003 3101 path policy nested-reference unchanged"},{"id":"IETF RFC 3353","type":"specification","body":"IETF","designation":"RFC 3353","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3353.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3353.txt","https://www.rfc-editor.org/rfc/rfc3353.pdf"],"folder":"IETF/RFC-3353","files":{"txt":{"path":"standards/IETF/RFC-3353/RFC-3353.txt","sha256":"1fb5d3761fc211a2a648796cd97ed49ea8b92dcd4c86a2133028ddbc76fc7992"}},"tags":["nested-reference","unchanged"],"summary":"This document offers a framework for IP multicast deployment in an\n MPLS environment. Issues arising when MPLS techniques are applied to\n IP multicast are overviewed. The pros and cons of existing IP\n multicast routing protocols in the context of MPLS are described and\n the relation to the different trigger methods and label distribution\n modes are discussed. The consequences of various layer 2 (L2)\n technologies are listed. Both point-to-point and multi-access\n networks are considered.\n\nOoms, et al. Informational [Page 1]\n\f\nRFC 3353 IP Multicast in an MPLS Environment August 2002","scope_keywords":["3353","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null}],"search_text":"IETF RFC 3353 This document offers a framework for IP multicast deployment in an\n MPLS environment. Issues arising when MPLS techniques are applied to\n IP multicast are overviewed. The pros and cons of existing IP\n multicast routing protocols in the context of MPLS are described and\n the relation to the different trigger methods and label distribution\n modes are discussed. The consequences of various layer 2 (L2)\n technologies are listed. Both point-to-point and multi-access\n networks are considered.\n\nOoms, et al. Informational [Page 1]\n\f\nRFC 3353 IP Multicast in an MPLS Environment August 2002 3353 management path nested-reference unchanged"},{"id":"IETF RFC 3913","type":"specification","body":"IETF","designation":"RFC 3913","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3913.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3913.txt","https://www.rfc-editor.org/rfc/rfc3913.pdf"],"folder":"IETF/RFC-3913","files":{"txt":{"path":"standards/IETF/RFC-3913/RFC-3913.txt","sha256":"422359dba82a606369571d69c9f1e28b8bc87405dbad98ee0bd95d5b4c40952a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Border Gateway Multicast Protocol (BGMP),\n a protocol for inter-domain multicast routing. BGMP builds shared\n trees for active multicast groups, and optionally allows receiver\n domains to build source-specific, inter-domain, distribution branches\n where needed. BGMP natively supports \"source-specific multicast\"\n (SSM). To also support \"any-source multicast\" (ASM), BGMP requires\n that each multicast group be associated with a single root (in BGMP\n it is referred to as the root domain). It requires that different\n ranges of the multicast address space are associated (e.g., with\n Unicast-Prefix-Based Multicast addressing) with different domains.\n Each of these domains then becomes the root of the shared domain-\n trees for all groups in its range. Multicast participants will\n generally receive better multicast service if the session initiator's\n address allocator ","scope_keywords":["3913"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null}],"search_text":"IETF RFC 3913 This document describes the Border Gateway Multicast Protocol (BGMP),\n a protocol for inter-domain multicast routing. BGMP builds shared\n trees for active multicast groups, and optionally allows receiver\n domains to build source-specific, inter-domain, distribution branches\n where needed. BGMP natively supports \"source-specific multicast\"\n (SSM). To also support \"any-source multicast\" (ASM), BGMP requires\n that each multicast group be associated with a single root (in BGMP\n it is referred to as the root domain). It requires that different\n ranges of the multicast address space are associated (e.g., with\n Unicast-Prefix-Based Multicast addressing) with different domains.\n Each of these domains then becomes the root of the shared domain-\n trees for all groups in its range. Multicast participants will\n generally receive better multicast service if the session initiator's\n address allocator  3913 nested-reference unchanged"},{"id":"IETF RFC 4940","type":"specification","body":"IETF","designation":"RFC 4940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4940.txt","https://www.rfc-editor.org/rfc/rfc4940.pdf"],"folder":"IETF/RFC-4940","files":{"txt":{"path":"standards/IETF/RFC-4940/RFC-4940.txt","sha256":"9b03ba0c750ed69459aff49ec7bc2b4a3b949f6447950969dca756c049760b2c"}},"tags":["nested-reference","unchanged"],"summary":"This memo creates a number of OSPF registries and provides guidance\n to IANA for assignment of code points within these registries.\n\nKompella & Fenner Best Current Practice [Page 1]\n\f\nRFC 4940 IANA Considerations for OSPF June 2007","scope_keywords":["4940","authentication","key","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 4940 This memo creates a number of OSPF registries and provides guidance\n to IANA for assignment of code points within these registries.\n\nKompella & Fenner Best Current Practice [Page 1]\n\f\nRFC 4940 IANA Considerations for OSPF June 2007 4940 authentication key management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 4973","type":"specification","body":"IETF","designation":"RFC 4973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4973.txt","https://www.rfc-editor.org/rfc/rfc4973.pdf"],"folder":"IETF/RFC-4973","files":{"txt":{"path":"standards/IETF/RFC-4973/RFC-4973.txt","sha256":"d16f19089f8d1c2945368fb68ae55432adb4cf64ad491891b844099970c0057f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines OSPF-xTE, an experimental traffic engineering\n (TE) extension to the link-state routing protocol OSPF. OSPF-xTE\n defines new TE Link State Advertisements (LSAs) to disseminate TE\n metrics within an autonomous System (AS), which may consist of\n multiple areas. When an AS consists of TE and non-TE nodes, OSPF-xTE\n ensures that non-TE nodes in the AS are unaffected by the TE LSAs.\n OSPF-xTE generates a stand-alone TE Link State Database (TE-LSDB),\n distinct from the native OSPF LSDB, for computation of TE circuit\n paths. OSPF-xTE is versatile and extendible to non-packet networks\n such as Synchronous Optical Network (SONET) / Time Division\n Multiplexing (TDM) and optical networks.\n\nIESG Note\n\n The content of this RFC was at one time considered by the IETF, and\n therefore it may resemble a current IETF work in progress or a\n published IETF work. This RFC is not a candid","scope_keywords":["4973","algorithm","algorithms","path","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 4973 This document defines OSPF-xTE, an experimental traffic engineering\n (TE) extension to the link-state routing protocol OSPF. OSPF-xTE\n defines new TE Link State Advertisements (LSAs) to disseminate TE\n metrics within an autonomous System (AS), which may consist of\n multiple areas. When an AS consists of TE and non-TE nodes, OSPF-xTE\n ensures that non-TE nodes in the AS are unaffected by the TE LSAs.\n OSPF-xTE generates a stand-alone TE Link State Database (TE-LSDB),\n distinct from the native OSPF LSDB, for computation of TE circuit\n paths. OSPF-xTE is versatile and extendible to non-packet networks\n such as Synchronous Optical Network (SONET) / Time Division\n Multiplexing (TDM) and optical networks.\n\nIESG Note\n\n The content of this RFC was at one time considered by the IETF, and\n therefore it may resemble a current IETF work in progress or a\n published IETF work. This RFC is not a candid 4973 algorithm algorithms path presentation trust nested-reference unchanged"},{"id":"IETF RFC 5250","type":"specification","body":"IETF","designation":"RFC 5250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5250.txt","https://www.rfc-editor.org/rfc/rfc5250.pdf"],"folder":"IETF/RFC-5250","files":{"txt":{"path":"standards/IETF/RFC-5250/RFC-5250.txt","sha256":"13f55659b588e1cb78428084a0b33aba240a3c249e40af376df4c49092c00a7c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines enhancements to the OSPF protocol to support a\n new class of link state advertisements (LSAs) called Opaque LSAs.\n Opaque LSAs provide a generalized mechanism to allow for the future\n extensibility of OSPF. Opaque LSAs consist of a standard LSA header\n followed by application-specific information. The information field\n may be used directly by OSPF or by other applications. Standard OSPF\n link-state database flooding mechanisms are used to distribute Opaque\n LSAs to all or some limited portion of the OSPF topology.\n\n This document replaces RFC 2370 and adds to it a mechanism to enable\n an OSPF router to validate Autonomous System (AS)-scope Opaque LSAs\n originated outside of the router's OSPF area.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 5250 OSPF Opaque LSA Option July 2008","scope_keywords":["5250","key","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 5250 This document defines enhancements to the OSPF protocol to support a\n new class of link state advertisements (LSAs) called Opaque LSAs.\n Opaque LSAs provide a generalized mechanism to allow for the future\n extensibility of OSPF. Opaque LSAs consist of a standard LSA header\n followed by application-specific information. The information field\n may be used directly by OSPF or by other applications. Standard OSPF\n link-state database flooding mechanisms are used to distribute Opaque\n LSAs to all or some limited portion of the OSPF topology.\n\n This document replaces RFC 2370 and adds to it a mechanism to enable\n an OSPF router to validate Autonomous System (AS)-scope Opaque LSAs\n originated outside of the router's OSPF area.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 5250 OSPF Opaque LSA Option July 2008 5250 key management validation nested-reference unchanged"},{"id":"IETF RFC 159","type":"specification","body":"IETF","designation":"RFC 159","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc159.txt","https://www.rfc-editor.org/rfc/rfc159.pdf"],"folder":"IETF/RFC-159","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 158","folder":"IETF/RFC-158","source":"IETF/RFC-158/RFC-158.txt","version":null}],"search_text":"IETF RFC 159 nested-reference unavailable"},{"id":"IETF RFC 2978","type":"specification","body":"IETF","designation":"RFC 2978","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2978.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2978.txt","https://www.rfc-editor.org/rfc/rfc2978.pdf"],"folder":"IETF/RFC-2978","files":{"txt":{"path":"standards/IETF/RFC-2978/RFC-2978.txt","sha256":"5c8f8a8ada6408241213ed29ade767c9be7c00e5c3a20ad14fe09f6e53b0b984"}},"tags":["nested-reference","unchanged"],"summary":"Multipurpose Internet Mail Extensions (MIME) (RFC-2045, RFC-2046,\n RFC-2047, RFC-2184) and various other Internet protocols are capable\n of using many different charsets. This in turn means that the\n ability to label different charsets is essential.\n\n Note: The charset registration procedure exists solely to associate a\n specific name or names with a given charset and to give an indication\n of whether or not a given charset can be used in MIME text objects.\n In particular, the general applicability and appropriateness of a\n given registered charset to a particular application is a protocol\n issue, not a registration issue, and is not dealt with by this\n registration procedure.\n\n1. Definitions and Notation\n\n The following sections define terms used in this document.","scope_keywords":["2978","presentation","profile","profiles","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2987","folder":"IETF/RFC-2987","source":"IETF/RFC-2987/RFC-2987.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2978 Multipurpose Internet Mail Extensions (MIME) (RFC-2045, RFC-2046,\n RFC-2047, RFC-2184) and various other Internet protocols are capable\n of using many different charsets. This in turn means that the\n ability to label different charsets is essential.\n\n Note: The charset registration procedure exists solely to associate a\n specific name or names with a given charset and to give an indication\n of whether or not a given charset can be used in MIME text objects.\n In particular, the general applicability and appropriateness of a\n given registered charset to a particular application is a protocol\n issue, not a registration issue, and is not dealt with by this\n registration procedure.\n\n1. Definitions and Notation\n\n The following sections define terms used in this document. 2978 presentation profile profiles registered nested-reference unchanged"},{"id":"IETF RFC 9193","type":"specification","body":"IETF","designation":"RFC 9193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9193.txt","https://www.rfc-editor.org/rfc/rfc9193.pdf"],"folder":"IETF/RFC-9193","files":{"pdf":{"path":"standards/IETF/RFC-9193/RFC-9193.pdf","sha256":"b1151ae5a919270b6331b82d6b1f9364bf5a1006de27d7f68fd3f4bc01f94ece"},"txt":{"path":"standards/IETF/RFC-9193/RFC-9193.txt","sha256":"e031d4bf4f1eca56c799788f1433db07b8b54215b43dd62740053a2319c0325c"}},"tags":["nested-reference","unchanged"],"summary":"The Sensor Measurement Lists (SenML) media types support multiple\n types of values, from numbers to text strings and arbitrary binary\n Data Values. In order to facilitate processing of binary Data\n Values, this document specifies a pair of new SenML fields for\n indicating the content format of those binary Data Values, i.e.,\n their Internet media type, including parameters as well as any\n content codings applied.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to pr","scope_keywords":["9193","http","https","key","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9193 The Sensor Measurement Lists (SenML) media types support multiple\n types of values, from numbers to text strings and arbitrary binary\n Data Values. In order to facilitate processing of binary Data\n Values, this document specifies a pair of new SenML fields for\n indicating the content format of those binary Data Values, i.e.,\n their Internet media type, including parameters as well as any\n content codings applied.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to pr 9193 http https key license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 1879","type":"specification","body":"IETF","designation":"RFC 1879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1879.txt","https://www.rfc-editor.org/rfc/rfc1879.pdf"],"folder":"IETF/RFC-1879","files":{"txt":{"path":"standards/IETF/RFC-1879/RFC-1879.txt","sha256":"702408fc5a7ca06316edbcd4edde7b2be68e4ad735814dece5596df3d8157e42"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents some experiences with the RFC 1797 [1] subnet A\n experiment (performed by the Net39 Test Group (see credits)) and\n provides a number of recommendations on future direction for both the\n Internet Registries and the Operations community.","scope_keywords":["1879","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null}],"search_text":"IETF RFC 1879 This memo documents some experiences with the RFC 1797 [1] subnet A\n experiment (performed by the Net39 Test Group (see credits)) and\n provides a number of recommendations on future direction for both the\n Internet Registries and the Operations community. 1879 http path nested-reference unchanged"},{"id":"IETF RFC 1601","type":"specification","body":"IETF","designation":"RFC 1601","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1601.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1601.txt","https://www.rfc-editor.org/rfc/rfc1601.pdf"],"folder":"IETF/RFC-1601","files":{"txt":{"path":"standards/IETF/RFC-1601/RFC-1601.txt","sha256":"7e8e2519beed6e2391ebc9ec9291de7453dd680463ca19bf40f9c8ab30ad5497"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents the composition, selection, roles, and\n organization of the Internet Architecture Board and its subsidiary\n organizations.\n\n1. IAB Membership\n\n The Internet Architecture Board (IAB) shall consist of 13 voting\n members, composed of the IETF chair and 12 full members. The IETF\n chair, who is also the chair of the IESG, may vote on all official\n IAB actions except the approval of IESG members. Ex-officio members\n and a liaison from the IESG may also attend IAB meetings but shall\n have no vote on official actions.\n\n Voting IAB members shall serve for a term of two years, but may serve\n any number of terms.\n\n Members of the IAB shall serve as individuals, and not as\n representatives of any company, agency, or other organization.","scope_keywords":["1601","management","pid","policy","presentation","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1627","folder":"IETF/RFC-1627","source":"IETF/RFC-1627/RFC-1627.txt","version":null},{"body":"IETF","designation":"RFC 2028","folder":"IETF/RFC-2028","source":"IETF/RFC-2028/RFC-2028.txt","version":null},{"body":"IETF","designation":"RFC 2850","folder":"IETF/RFC-2850","source":"IETF/RFC-2850/RFC-2850.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null}],"search_text":"IETF RFC 1601 This memo documents the composition, selection, roles, and\n organization of the Internet Architecture Board and its subsidiary\n organizations.\n\n1. IAB Membership\n\n The Internet Architecture Board (IAB) shall consist of 13 voting\n members, composed of the IETF chair and 12 full members. The IETF\n chair, who is also the chair of the IESG, may vote on all official\n IAB actions except the approval of IESG members. Ex-officio members\n and a liaison from the IESG may also attend IAB meetings but shall\n have no vote on official actions.\n\n Voting IAB members shall serve for a term of two years, but may serve\n any number of terms.\n\n Members of the IAB shall serve as individuals, and not as\n representatives of any company, agency, or other organization. 1601 management pid policy presentation qualified trust nested-reference unchanged"},{"id":"IETF RFC 2028","type":"specification","body":"IETF","designation":"RFC 2028","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2028.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2028.txt","https://www.rfc-editor.org/rfc/rfc2028.pdf"],"folder":"IETF/RFC-2028","files":{"txt":{"path":"standards/IETF/RFC-2028/RFC-2028.txt","sha256":"0f56bb0537abdc944021ffeb3b800d66349c624d82dc030dfe9674b4c3c2f1d7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the individuals and organizations involved in\n the IETF. This includes descriptions of the IESG, the IETF Working\n Groups and the relationship between the IETF and the Internet\n Society.\n\n1. Documents controlling the process","scope_keywords":["2028","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3233","folder":"IETF/RFC-3233","source":"IETF/RFC-3233/RFC-3233.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3667","folder":"IETF/RFC-3667","source":"IETF/RFC-3667/RFC-3667.txt","version":null},{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3978","folder":"IETF/RFC-3978","source":"IETF/RFC-3978/RFC-3978.txt","version":null},{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 2028 This document describes the individuals and organizations involved in\n the IETF. This includes descriptions of the IESG, the IETF Working\n Groups and the relationship between the IETF and the Internet\n Society.\n\n1. Documents controlling the process 2028 key management trust nested-reference unchanged"},{"id":"IETF RFC 2850","type":"specification","body":"IETF","designation":"RFC 2850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2850.txt","https://www.rfc-editor.org/rfc/rfc2850.pdf"],"folder":"IETF/RFC-2850","files":{"txt":{"path":"standards/IETF/RFC-2850/RFC-2850.txt","sha256":"b6f172ff4f33be17b682090cf6cd67706d733bdfdd2006ddf4207ae2c5690eda"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents the composition, selection, roles, and\n organization of the Internet Architecture Board. It replaces RFC\n 1601.","scope_keywords":["2850","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 4052","folder":"IETF/RFC-4052","source":"IETF/RFC-4052/RFC-4052.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 4714","folder":"IETF/RFC-4714","source":"IETF/RFC-4714/RFC-4714.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null}],"search_text":"IETF RFC 2850 This memo documents the composition, selection, roles, and\n organization of the Internet Architecture Board. It replaces RFC\n 1601. 2850 management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1871","type":"specification","body":"IETF","designation":"RFC 1871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1871.txt","https://www.rfc-editor.org/rfc/rfc1871.pdf"],"folder":"IETF/RFC-1871","files":{"txt":{"path":"standards/IETF/RFC-1871/RFC-1871.txt","sha256":"ba24638e1be745c17a92dc153e97302dd48b5cf9907e14610e4247f2229da774"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a modification to the IETF procedures to\n allow an escape from a situation where the existing procedures are\n not working or do not seem to apply. This is a modification to the\n procedures of RFC 1602 and 1603.","scope_keywords":["1871","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null}],"search_text":"IETF RFC 1871 This document describes a modification to the IETF procedures to\n allow an escape from a situation where the existing procedures are\n not working or do not seem to apply. This is a modification to the\n procedures of RFC 1602 and 1603. 1871 subject nested-reference unchanged"},{"id":"IETF RFC 2014","type":"specification","body":"IETF","designation":"RFC 2014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2014.txt","https://www.rfc-editor.org/rfc/rfc2014.pdf"],"folder":"IETF/RFC-2014","files":{"txt":{"path":"standards/IETF/RFC-2014/RFC-2014.txt","sha256":"4875503680a118aee21f3443d59f232e3df2dcb51b2fbd9038f05cbe379bc7ff"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Research Task Force (IRTF) has responsibility for\n organizing groups to investigate research topics related to the\n Internet protocols, applications, and technology. IRTF activities are\n organized into Research Groups. This document describes the\n guidelines and procedures for formation and operation of IRTF\n Research Groups. It describes the relationship between IRTF\n participants, Research Groups, the Internet Research Steering Group\n (IRSG) and the Internet Architecture Board (IAB). The basic duties\n of IRTF participants, including the IRTF Chair, Research Group Chairs\n and IRSG members are defined.\n\n1. INTRODUCTION\n\n This document defines guidelines and procedures for Internet Research\n Task Force (IRTF) Research Groups. The IRTF focuses on longer term\n research issues related to the Internet while the parallel\n organization, the Internet Engineering Task Force (IETF), f","scope_keywords":["2014"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2028","folder":"IETF/RFC-2028","source":"IETF/RFC-2028/RFC-2028.txt","version":null},{"body":"IETF","designation":"RFC 2850","folder":"IETF/RFC-2850","source":"IETF/RFC-2850/RFC-2850.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null}],"search_text":"IETF RFC 2014 The Internet Research Task Force (IRTF) has responsibility for\n organizing groups to investigate research topics related to the\n Internet protocols, applications, and technology. IRTF activities are\n organized into Research Groups. This document describes the\n guidelines and procedures for formation and operation of IRTF\n Research Groups. It describes the relationship between IRTF\n participants, Research Groups, the Internet Research Steering Group\n (IRSG) and the Internet Architecture Board (IAB). The basic duties\n of IRTF participants, including the IRTF Chair, Research Group Chairs\n and IRSG members are defined.\n\n1. INTRODUCTION\n\n This document defines guidelines and procedures for Internet Research\n Task Force (IRTF) Research Groups. The IRTF focuses on longer term\n research issues related to the Internet while the parallel\n organization, the Internet Engineering Task Force (IETF), f 2014 nested-reference unchanged"},{"id":"IETF RFC 2027","type":"specification","body":"IETF","designation":"RFC 2027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2027.txt","https://www.rfc-editor.org/rfc/rfc2027.pdf"],"folder":"IETF/RFC-2027","files":{"txt":{"path":"standards/IETF/RFC-2027/RFC-2027.txt","sha256":"fa5b6d8d0dcc07d429057027695f050697707f492f66b79d36d7b8b398c3abf9"}},"tags":["nested-reference","unchanged"],"summary":"The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled has been exercised four times since its\n formal creation. The evolution of the process has relied principally\n on oral tradition as a means by which the lessons learned could be\n passed on to successive committees. This document is a self-\n consistent, organized compilation of the process as it is known\n today.","scope_keywords":["2027"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2028","folder":"IETF/RFC-2028","source":"IETF/RFC-2028/RFC-2028.txt","version":null},{"body":"IETF","designation":"RFC 2282","folder":"IETF/RFC-2282","source":"IETF/RFC-2282/RFC-2282.txt","version":null},{"body":"IETF","designation":"RFC 3777","folder":"IETF/RFC-3777","source":"IETF/RFC-3777/RFC-3777.txt","version":null}],"search_text":"IETF RFC 2027 The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled has been exercised four times since its\n formal creation. The evolution of the process has relied principally\n on oral tradition as a means by which the lessons learned could be\n passed on to successive committees. This document is a self-\n consistent, organized compilation of the process as it is known\n today. 2027 nested-reference unchanged"},{"id":"IETF RFC 2282","type":"specification","body":"IETF","designation":"RFC 2282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2282.txt","https://www.rfc-editor.org/rfc/rfc2282.pdf"],"folder":"IETF/RFC-2282","files":{"txt":{"path":"standards/IETF/RFC-2282/RFC-2282.txt","sha256":"a05211c95c92a68c1e6f00ccd017054cd982f356167efb803d339194fcbb777b"}},"tags":["nested-reference","unchanged"],"summary":"The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. The evolution of the process\n has relied principally on oral tradition as a means by which the\n lessons learned could be passed on to successive committees. This\n document is a self-consistent, organized compilation of the process\n as it is known today.","scope_keywords":["2282"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 2727","folder":"IETF/RFC-2727","source":"IETF/RFC-2727/RFC-2727.txt","version":null},{"body":"IETF","designation":"RFC 2850","folder":"IETF/RFC-2850","source":"IETF/RFC-2850/RFC-2850.txt","version":null},{"body":"IETF","designation":"RFC 3777","folder":"IETF/RFC-3777","source":"IETF/RFC-3777/RFC-3777.txt","version":null}],"search_text":"IETF RFC 2282 The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. The evolution of the process\n has relied principally on oral tradition as a means by which the\n lessons learned could be passed on to successive committees. This\n document is a self-consistent, organized compilation of the process\n as it is known today. 2282 nested-reference unchanged"},{"id":"IETF RFC 3669","type":"specification","body":"IETF","designation":"RFC 3669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3669.txt","https://www.rfc-editor.org/rfc/rfc3669.pdf"],"folder":"IETF/RFC-3669","files":{"txt":{"path":"standards/IETF/RFC-3669/RFC-3669.txt","sha256":"38125a0de413a26f429b3bff6bd8ca644f0d0b4a804ec8b529c7f180fe6fcfa4"}},"tags":["nested-reference","unchanged"],"summary":"This memo lays out a conceptual framework and rules of thumb useful\n for working groups dealing with Intellectual Property Rights (IPR)\n issues. It documents specific examples of how IPR issues have been\n dealt with in the IETF.","scope_keywords":["3669","license","pki"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null}],"search_text":"IETF RFC 3669 This memo lays out a conceptual framework and rules of thumb useful\n for working groups dealing with Intellectual Property Rights (IPR)\n issues. It documents specific examples of how IPR issues have been\n dealt with in the IETF. 3669 license pki nested-reference unchanged"},{"id":"IETF RFC 6702","type":"specification","body":"IETF","designation":"RFC 6702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6702.txt","https://www.rfc-editor.org/rfc/rfc6702.pdf"],"folder":"IETF/RFC-6702","files":{"txt":{"path":"standards/IETF/RFC-6702/RFC-6702.txt","sha256":"457b6cb1ba64ddc91db18fc84057bdb3283d43674694851bd95984aa4a8d6b53"}},"tags":["nested-reference","unchanged"],"summary":"The disclosure process for intellectual property rights (IPR) in\n documents produced within the IETF stream is essential to the\n accurate development of community consensus. However, this process\n is not always followed by IETF participants. Regardless of the cause\n or motivation, noncompliance with IPR disclosure rules can delay or\n even derail completion of IETF specifications. This document\n describes some strategies for promoting compliance with the IPR\n disclosure rules. These strategies are primarily intended for use by\n area directors, working group chairs, and working group secretaries.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has","scope_keywords":["6702","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 6702 The disclosure process for intellectual property rights (IPR) in\n documents produced within the IETF stream is essential to the\n accurate development of community consensus. However, this process\n is not always followed by IETF participants. Regardless of the cause\n or motivation, noncompliance with IPR disclosure rules can delay or\n even derail completion of IETF specifications. This document\n describes some strategies for promoting compliance with the IPR\n disclosure rules. These strategies are primarily intended for use by\n area directors, working group chairs, and working group secretaries.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has 6702 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2418","type":"specification","body":"IETF","designation":"RFC 2418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2418.txt","https://www.rfc-editor.org/rfc/rfc2418.pdf"],"folder":"IETF/RFC-2418","files":{"txt":{"path":"standards/IETF/RFC-2418/RFC-2418.txt","sha256":"f6ebc087116ebde91b98a287cb3815ca7fe13e6f584b948a18f3e45f910ed3d1"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Engineering Task Force (IETF) has responsibility for\n developing and reviewing specifications intended as Internet\n Standards. IETF activities are organized into working groups (WGs).\n This document describes the guidelines and procedures for formation\n and operation of IETF working groups. It also describes the formal\n relationship between IETF participants WG and the Internet\n Engineering Steering Group (IESG) and the basic duties of IETF\n participants, including WG Chairs, WG participants, and IETF Area\n Directors.","scope_keywords":["2418","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2436","folder":"IETF/RFC-2436","source":"IETF/RFC-2436/RFC-2436.txt","version":null},{"body":"IETF","designation":"RFC 3131","folder":"IETF/RFC-3131","source":"IETF/RFC-3131/RFC-3131.txt","version":null},{"body":"IETF","designation":"RFC 3356","folder":"IETF/RFC-3356","source":"IETF/RFC-3356/RFC-3356.txt","version":null},{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3683","folder":"IETF/RFC-3683","source":"IETF/RFC-3683/RFC-3683.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3934","folder":"IETF/RFC-3934","source":"IETF/RFC-3934/RFC-3934.txt","version":null},{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 5111","folder":"IETF/RFC-5111","source":"IETF/RFC-5111/RFC-5111.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 7282","folder":"IETF/RFC-7282","source":"IETF/RFC-7282/RFC-7282.txt","version":null}],"search_text":"IETF RFC 2418 The Internet Engineering Task Force (IETF) has responsibility for\n developing and reviewing specifications intended as Internet\n Standards. IETF activities are organized into working groups (WGs).\n This document describes the guidelines and procedures for formation\n and operation of IETF working groups. It also describes the formal\n relationship between IETF participants WG and the Internet\n Engineering Steering Group (IESG) and the basic duties of IETF\n participants, including WG Chairs, WG participants, and IETF Area\n Directors. 2418 http management nested-reference unchanged"},{"id":"IETF RFC 7282","type":"specification","body":"IETF","designation":"RFC 7282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7282.txt","https://www.rfc-editor.org/rfc/rfc7282.pdf"],"folder":"IETF/RFC-7282","files":{"txt":{"path":"standards/IETF/RFC-7282/RFC-7282.txt","sha256":"d060ec156f5d0699e2c0afd50ea6678293059feb84f1293c2db7ac67f482ae8d"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has had a long tradition of doing its technical work through\n a consensus process, taking into account the different views among\n IETF participants and coming to (at least rough) consensus on\n technical matters. In particular, the IETF is supposed not to be run\n by a \"majority rule\" philosophy. This is why we engage in rituals\n like \"humming\" instead of voting. However, more and more of our\n actions are now indistinguishable from voting, and quite often we are\n letting the majority win the day without consideration of minority\n concerns. This document explains some features of rough consensus,\n what is not rough consensus, how we have gotten away from it, how we\n might think about it differently, and the things we can do in order\n to really achieve rough consensus.\n\n Note: This document is quite consciously being put forward as\n Informational. It does not propose to change any I","scope_keywords":["7282","http","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 7282 The IETF has had a long tradition of doing its technical work through\n a consensus process, taking into account the different views among\n IETF participants and coming to (at least rough) consensus on\n technical matters. In particular, the IETF is supposed not to be run\n by a \"majority rule\" philosophy. This is why we engage in rituals\n like \"humming\" instead of voting. However, more and more of our\n actions are now indistinguishable from voting, and quite often we are\n letting the majority win the day without consideration of minority\n concerns. This document explains some features of rough consensus,\n what is not rough consensus, how we have gotten away from it, how we\n might think about it differently, and the things we can do in order\n to really achieve rough consensus.\n\n Note: This document is quite consciously being put forward as\n Informational. It does not propose to change any I 7282 http license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2615","type":"specification","body":"IETF","designation":"RFC 2615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2615.txt","https://www.rfc-editor.org/rfc/rfc2615.pdf"],"folder":"IETF/RFC-2615","files":{"txt":{"path":"standards/IETF/RFC-2615/RFC-2615.txt","sha256":"0a70fba977511169b95a213a8969aa52af1fe831e2bbed52f983009ab60be408"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Synchronous Optical\n Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits.\n\n This document replaces and obsoletes RFC 1619. See section 7 for a\n summary of the changes from RFC 1619.","scope_keywords":["2615","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 2615 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n This document describes the use of PPP over Synchronous Optical\n Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits.\n\n This document replaces and obsoletes RFC 1619. See section 7 for a\n summary of the changes from RFC 1619. 2615 key path nested-reference unchanged"},{"id":"IETF RFC 1625","type":"specification","body":"IETF","designation":"RFC 1625","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1625.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1625.txt","https://www.rfc-editor.org/rfc/rfc1625.pdf"],"folder":"IETF/RFC-1625","files":{"txt":{"path":"standards/IETF/RFC-1625/RFC-1625.txt","sha256":"5d262d9d0513db5d418d35ddb44a83d8673fcdbe72b9c2c4a634f80a9c1c217c"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this memo is to initiate a discussion for a migration\n path of the WAIS technology from Z39.50-1988 Information Retrieval\n Service Definitions and Protocol Specification for Library\n Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. The\n purpose of this memo is not to provide a detailed implementation\n specification, but rather to describe the high-level design goals and\n functional assumptions made in the WAIS implementation of Z39.50-\n 1988. WAIS use of Z39.50-1992 and Z39.50-1994 standards will be the\n subject of future RFCs.","scope_keywords":["1625","attribute","attributes","path","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null}],"search_text":"IETF RFC 1625 The purpose of this memo is to initiate a discussion for a migration\n path of the WAIS technology from Z39.50-1988 Information Retrieval\n Service Definitions and Protocol Specification for Library\n Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. The\n purpose of this memo is not to provide a detailed implementation\n specification, but rather to describe the high-level design goals and\n functional assumptions made in the WAIS implementation of Z39.50-\n 1988. WAIS use of Z39.50-1992 and Z39.50-1994 standards will be the\n subject of future RFCs. 1625 attribute attributes path presentation subject nested-reference unchanged"},{"id":"IETF RFC 3439","type":"specification","body":"IETF","designation":"RFC 3439","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3439.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3439.txt","https://www.rfc-editor.org/rfc/rfc3439.pdf"],"folder":"IETF/RFC-3439","files":{"txt":{"path":"standards/IETF/RFC-3439/RFC-3439.txt","sha256":"a1b57366510669a754e1cf5b76122120d1fc565178cc39f8e1e9a73b82dca8ca"}},"tags":["nested-reference","unchanged"],"summary":"This document extends RFC 1958 by outlining some of the philosophical\n guidelines to which architects and designers of Internet backbone\n networks should adhere. We describe the Simplicity Principle, which\n states that complexity is the primary mechanism that impedes\n efficient scaling, and discuss its implications on the architecture,\n design and engineering issues found in large scale Internet\n backbones.","scope_keywords":["3439","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3439 This document extends RFC 1958 by outlining some of the philosophical\n guidelines to which architects and designers of Internet backbone\n networks should adhere. We describe the Simplicity Principle, which\n states that complexity is the primary mechanism that impedes\n efficient scaling, and discuss its implications on the architecture,\n design and engineering issues found in large scale Internet\n backbones. 3439 delivery path nested-reference unchanged"},{"id":"IETF RFC 2141","type":"specification","body":"IETF","designation":"RFC 2141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2141.txt","https://www.rfc-editor.org/rfc/rfc2141.pdf"],"folder":"IETF/RFC-2141","files":{"txt":{"path":"standards/IETF/RFC-2141/RFC-2141.txt","sha256":"41c1a3492ac084942a1d31a0b3f69dc1a11f3390c46d2a374bd3b005b5caecbd"}},"tags":["nested-reference","unchanged"],"summary":"Uniform Resource Names (URNs) are intended to serve as persistent,\n location-independent, resource identifiers. This document sets\n forward the canonical syntax for URNs. A discussion of both existing\n legacy and new namespaces and requirements for URN presentation and\n transmission are presented. Finally, there is a discussion of URN\n equivalence and how to determine it.\n\n1. Introduction\n\n Uniform Resource Names (URNs) are intended to serve as persistent,\n location-independent, resource identifiers and are designed to make\n it easy to map other namespaces (which share the properties of URNs)\n into URN-space. Therefore, the URN syntax provides a means to encode\n character data in a form that can be sent in existing protocols,\n transcribed on most keyboards, etc.\n\n2. Syntax\n\n All URNs have the following syntax (phrases enclosed in quotes are\n REQUIRED):\n\n <URN> ::= \"urn:\" <NID> \":\" <NSS>\n","scope_keywords":["2141","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2169","folder":"IETF/RFC-2169","source":"IETF/RFC-2169/RFC-2169.txt","version":null},{"body":"IETF","designation":"RFC 2276","folder":"IETF/RFC-2276","source":"IETF/RFC-2276/RFC-2276.txt","version":null},{"body":"IETF","designation":"RFC 2288","folder":"IETF/RFC-2288","source":"IETF/RFC-2288/RFC-2288.txt","version":null},{"body":"IETF","designation":"RFC 2371","folder":"IETF/RFC-2371","source":"IETF/RFC-2371/RFC-2371.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2648","folder":"IETF/RFC-2648","source":"IETF/RFC-2648/RFC-2648.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 3001","folder":"IETF/RFC-3001","source":"IETF/RFC-3001/RFC-3001.txt","version":null},{"body":"IETF","designation":"RFC 3043","folder":"IETF/RFC-3043","source":"IETF/RFC-3043/RFC-3043.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3061","folder":"IETF/RFC-3061","source":"IETF/RFC-3061/RFC-3061.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3085","folder":"IETF/RFC-3085","source":"IETF/RFC-3085/RFC-3085.txt","version":null},{"body":"IETF","designation":"RFC 3120","folder":"IETF/RFC-3120","source":"IETF/RFC-3120/RFC-3120.txt","version":null},{"body":"IETF","designation":"RFC 3121","folder":"IETF/RFC-3121","source":"IETF/RFC-3121/RFC-3121.txt","version":null},{"body":"IETF","designation":"RFC 3151","folder":"IETF/RFC-3151","source":"IETF/RFC-3151/RFC-3151.txt","version":null},{"body":"IETF","designation":"RFC 3187","folder":"IETF/RFC-3187","source":"IETF/RFC-3187/RFC-3187.txt","version":null},{"body":"IETF","designation":"RFC 3188","folder":"IETF/RFC-3188","source":"IETF/RFC-3188/RFC-3188.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4179","folder":"IETF/RFC-4179","source":"IETF/RFC-4179/RFC-4179.txt","version":null},{"body":"IETF","designation":"RFC 4195","folder":"IETF/RFC-4195","source":"IETF/RFC-4195/RFC-4195.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4854","folder":"IETF/RFC-4854","source":"IETF/RFC-4854/RFC-4854.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 6288","folder":"IETF/RFC-6288","source":"IETF/RFC-6288/RFC-6288.txt","version":null},{"body":"IETF","designation":"RFC 6755","folder":"IETF/RFC-6755","source":"IETF/RFC-6755/RFC-6755.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 2141 Uniform Resource Names (URNs) are intended to serve as persistent,\n location-independent, resource identifiers. This document sets\n forward the canonical syntax for URNs. A discussion of both existing\n legacy and new namespaces and requirements for URN presentation and\n transmission are presented. Finally, there is a discussion of URN\n equivalence and how to determine it.\n\n1. Introduction\n\n Uniform Resource Names (URNs) are intended to serve as persistent,\n location-independent, resource identifiers and are designed to make\n it easy to map other namespaces (which share the properties of URNs)\n into URN-space. Therefore, the URN syntax provides a means to encode\n character data in a form that can be sent in existing protocols,\n transcribed on most keyboards, etc.\n\n2. Syntax\n\n All URNs have the following syntax (phrases enclosed in quotes are\n REQUIRED):\n\n <URN> ::= \"urn:\" <NID> \":\" <NSS>\n 2141 key presentation nested-reference unchanged"},{"id":"IETF RFC 2169","type":"specification","body":"IETF","designation":"RFC 2169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2169.txt","https://www.rfc-editor.org/rfc/rfc2169.pdf"],"folder":"IETF/RFC-2169","files":{"txt":{"path":"standards/IETF/RFC-2169/RFC-2169.txt","sha256":"c4c3872942c5597be1612390ec024b7ae556ec70a56319cdcbe6bcd891bec7e0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Daniel\nRequest for Comments: 2169 Los Alamos National Laboratory\nCategory: Experimental June 1997\n\n A Trivial Convention for using HTTP in URN Resolution\n\nStatus of this Memo\n===================\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract:\n=========\n\n The Uniform Resource Names Working Group (URN-WG) was formed to\n specify persistent, location-independent names for network accessible\n resources, as well as resolution mechanisms to retrieve the resources\n given such a name. At this time the URN-WG is considering one\n particular resolution mechanism, the NAPTR proposal [1]. That\n proposal specifies how a client may find a \"resolver\" for a URN. A\n resolver is a databas","scope_keywords":["2169","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null}],"search_text":"IETF RFC 2169 Network Working Group R. Daniel\nRequest for Comments: 2169 Los Alamos National Laboratory\nCategory: Experimental June 1997\n\n A Trivial Convention for using HTTP in URN Resolution\n\nStatus of this Memo\n===================\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract:\n=========\n\n The Uniform Resource Names Working Group (URN-WG) was formed to\n specify persistent, location-independent names for network accessible\n resources, as well as resolution mechanisms to retrieve the resources\n given such a name. At this time the URN-WG is considering one\n particular resolution mechanism, the NAPTR proposal [1]. That\n proposal specifies how a client may find a \"resolver\" for a URN. A\n resolver is a databas 2169 http nested-reference unchanged"},{"id":"IETF RFC 2483","type":"specification","body":"IETF","designation":"RFC 2483","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2483.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2483.txt","https://www.rfc-editor.org/rfc/rfc2483.pdf"],"folder":"IETF/RFC-2483","files":{"txt":{"path":"standards/IETF/RFC-2483/RFC-2483.txt","sha256":"80adcc597c6bb300f2240caf6be169b3608cffc41b11ba059fd85965581c8b57"}},"tags":["nested-reference","unchanged"],"summary":"Retrieving the resource identified by a Uniform Resource Identifier\n (URI) [1] is only one of the operations that can be performed on a\n URI. One might also ask for and get a list of other identifiers that\n are aliases for the original URI or a bibliographic description of\n the resource the URI denotes, for example. This applies to both\n Uniform Resource Names (URNs) and Uniform Resource Locators (URLs).\n Uniform Resource Characteristics (URCs) are discussed in this\n document but only as descriptions of resources rather than\n identifiers.\n\n A service in the network providing access to a resource may provide\n one or some of these options, but it need not provide all of them.\n This memo specifies an initial set of these operations that can be\n used to describe the interactions provided by a given access service.\n It also suggests guidelines that should be adhered to when those\n operations ","scope_keywords":["2483","algorithm","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3120","folder":"IETF/RFC-3120","source":"IETF/RFC-3120/RFC-3120.txt","version":null},{"body":"IETF","designation":"RFC 3121","folder":"IETF/RFC-3121","source":"IETF/RFC-3121/RFC-3121.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 2483 Retrieving the resource identified by a Uniform Resource Identifier\n (URI) [1] is only one of the operations that can be performed on a\n URI. One might also ask for and get a list of other identifiers that\n are aliases for the original URI or a bibliographic description of\n the resource the URI denotes, for example. This applies to both\n Uniform Resource Names (URNs) and Uniform Resource Locators (URLs).\n Uniform Resource Characteristics (URCs) are discussed in this\n document but only as descriptions of resources rather than\n identifiers.\n\n A service in the network providing access to a resource may provide\n one or some of these options, but it need not provide all of them.\n This memo specifies an initial set of these operations that can be\n used to describe the interactions provided by a given access service.\n It also suggests guidelines that should be adhered to when those\n operations  2483 algorithm http key nested-reference unchanged"},{"id":"IETF RFC 2506","type":"specification","body":"IETF","designation":"RFC 2506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2506.txt","https://www.rfc-editor.org/rfc/rfc2506.pdf"],"folder":"IETF/RFC-2506","files":{"txt":{"path":"standards/IETF/RFC-2506/RFC-2506.txt","sha256":"63d2c2d62d03efe3c93e9f3d6bf3f1adec7973676f2dfdc4473a07d5d63ca1f7"}},"tags":["nested-reference","unchanged"],"summary":"Recent Internet applications, such as the World Wide Web, tie\n together a great diversity in data formats, client and server\n platforms, and communities. This has created a need for media\n feature descriptions and negotiation mechanisms in order to identify\n and reconcile the form of information to the capabilities and\n preferences of the parties involved.\n\n Extensible media feature identification and negotiation mechanisms\n require a common vocabulary in order to positively identify media\n features. A registration process and authority for media features is\n defined with the intent of sharing this vocabulary between\n communicating parties. In addition, a URI tree is defined to enable\n sharing of media feature definitions without registration.\n\n This document defines a registration procedure which uses the\n Internet Assigned Numbers Authority (IANA) as a central registry for\n the media f","scope_keywords":["2506","http","identification","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2534","folder":"IETF/RFC-2534","source":"IETF/RFC-2534/RFC-2534.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 2987","folder":"IETF/RFC-2987","source":"IETF/RFC-2987/RFC-2987.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null}],"search_text":"IETF RFC 2506 Recent Internet applications, such as the World Wide Web, tie\n together a great diversity in data formats, client and server\n platforms, and communities. This has created a need for media\n feature descriptions and negotiation mechanisms in order to identify\n and reconcile the form of information to the capabilities and\n preferences of the parties involved.\n\n Extensible media feature identification and negotiation mechanisms\n require a common vocabulary in order to positively identify media\n features. A registration process and authority for media features is\n defined with the intent of sharing this vocabulary between\n communicating parties. In addition, a URI tree is defined to enable\n sharing of media feature definitions without registration.\n\n This document defines a registration procedure which uses the\n Internet Assigned Numbers Authority (IANA) as a central registry for\n the media f 2506 http identification registered nested-reference unchanged"},{"id":"IETF RFC 2766","type":"specification","body":"IETF","designation":"RFC 2766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2766.txt","https://www.rfc-editor.org/rfc/rfc2766.pdf"],"folder":"IETF/RFC-2766","files":{"txt":{"path":"standards/IETF/RFC-2766/RFC-2766.txt","sha256":"f4ba85a842933d34ec189f1c6b706ee11b2b9be86816da105bc9f31f86dab419"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an IPv4-to-IPv6 transition mechanism, in\n addition to those already specified in [TRANS]. This solution\n attempts to provide transparent routing, as defined in [NAT-TERM], to\n end-nodes in V6 realm trying to communicate with end-nodes in V4\n realm and vice versa. This is achieved using a combination of Network\n Address Translation and Protocol Translation. The scheme described\n does not mandate dual-stacks (i.e., IPv4 as well as V6 protocol\n support) or special purpose routing requirements (such as requiring\n tunneling support) on end nodes. This scheme is based on a\n combination of address translation theme as described in [NAT-TERM]\n and V6/V4 protocol translation theme as described in [SIIT].\n\nAcknowledgements\n\n Special thanks to Pedro Marques for reviewing an earlier version of\n this memo. Also, many thanks to Alan O'Neill and Martin Tatham, as\n the mechanism ","scope_keywords":["2766"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2956","folder":"IETF/RFC-2956","source":"IETF/RFC-2956/RFC-2956.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null}],"search_text":"IETF RFC 2766 This document specifies an IPv4-to-IPv6 transition mechanism, in\n addition to those already specified in [TRANS]. This solution\n attempts to provide transparent routing, as defined in [NAT-TERM], to\n end-nodes in V6 realm trying to communicate with end-nodes in V4\n realm and vice versa. This is achieved using a combination of Network\n Address Translation and Protocol Translation. The scheme described\n does not mandate dual-stacks (i.e., IPv4 as well as V6 protocol\n support) or special purpose routing requirements (such as requiring\n tunneling support) on end nodes. This scheme is based on a\n combination of address translation theme as described in [NAT-TERM]\n and V6/V4 protocol translation theme as described in [SIIT].\n\nAcknowledgements\n\n Special thanks to Pedro Marques for reviewing an earlier version of\n this memo. Also, many thanks to Alan O'Neill and Martin Tatham, as\n the mechanism  2766 nested-reference unchanged"},{"id":"IETF RFC 2767","type":"specification","body":"IETF","designation":"RFC 2767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2767.txt","https://www.rfc-editor.org/rfc/rfc2767.pdf"],"folder":"IETF/RFC-2767","files":{"txt":{"path":"standards/IETF/RFC-2767/RFC-2767.txt","sha256":"b298a08259c876683796c56530fa49f6401dd2fcbf01dbaeb1a1c26c5ba3978d"}},"tags":["nested-reference","unchanged"],"summary":"In the especially initial stage of the transition from IPv4 to IPv6,\n it is hard to provide a complete set of IPv6 applications. This memo\n proposes a mechanism of dual stack hosts using the technique called\n \"Bump-in-the-Stack\" in the IP security area. The mechanism allows the\n hosts to communicate with other IPv6 hosts using existing IPv4\n applications.\n\n1. Introduction\n\n RFC1933 [TRANS-MECH] specifies transition mechanisms, including dual\n stack and tunneling, for the initial stage. Hosts and routers with\n the transition mechanisms are also developed. But there are few\n applications for IPv6 [IPV6] as compared with IPv4 [IPV4] in which a\n great number of applications are available. In order to advance the\n transition smoothly, it is highly desirable to make the availability\n of IPv6 applications increase to the same level as IPv4.\n Unfortunately, however, this is expected to take a ve","scope_keywords":["2767"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null}],"search_text":"IETF RFC 2767 In the especially initial stage of the transition from IPv4 to IPv6,\n it is hard to provide a complete set of IPv6 applications. This memo\n proposes a mechanism of dual stack hosts using the technique called\n \"Bump-in-the-Stack\" in the IP security area. The mechanism allows the\n hosts to communicate with other IPv6 hosts using existing IPv4\n applications.\n\n1. Introduction\n\n RFC1933 [TRANS-MECH] specifies transition mechanisms, including dual\n stack and tunneling, for the initial stage. Hosts and routers with\n the transition mechanisms are also developed. But there are few\n applications for IPv6 [IPV6] as compared with IPv4 [IPV4] in which a\n great number of applications are available. In order to advance the\n transition smoothly, it is highly desirable to make the availability\n of IPv6 applications increase to the same level as IPv4.\n Unfortunately, however, this is expected to take a ve 2767 nested-reference unchanged"},{"id":"IETF RFC 2205","type":"specification","body":"IETF","designation":"RFC 2205","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2205.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2205.txt","https://www.rfc-editor.org/rfc/rfc2205.pdf"],"folder":"IETF/RFC-2205","files":{"txt":{"path":"standards/IETF/RFC-2205/RFC-2205.txt","sha256":"b106691046f38f466e67d5aaf94ca38aaaafec7a95c6fbfc95897db4b366b849"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes version 1 of RSVP, a resource reservation setup\n protocol designed for an integrated services Internet. RSVP provides\n receiver-initiated setup of resource reservations for multicast or\n unicast data flows, with good scaling and robustness properties.\n\nBraden, Ed., et. al. Standards Track [Page 1]\n\f\nRFC 2205 RSVP September 1997","scope_keywords":["2205","management","path","policy","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2207","folder":"IETF/RFC-2207","source":"IETF/RFC-2207/RFC-2207.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2209","folder":"IETF/RFC-2209","source":"IETF/RFC-2209/RFC-2209.txt","version":null},{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2211","folder":"IETF/RFC-2211","source":"IETF/RFC-2211/RFC-2211.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2430","folder":"IETF/RFC-2430","source":"IETF/RFC-2430/RFC-2430.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2638","folder":"IETF/RFC-2638","source":"IETF/RFC-2638/RFC-2638.txt","version":null},{"body":"IETF","designation":"RFC 2676","folder":"IETF/RFC-2676","source":"IETF/RFC-2676/RFC-2676.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2711","folder":"IETF/RFC-2711","source":"IETF/RFC-2711/RFC-2711.txt","version":null},{"body":"IETF","designation":"RFC 2745","folder":"IETF/RFC-2745","source":"IETF/RFC-2745/RFC-2745.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2749","folder":"IETF/RFC-2749","source":"IETF/RFC-2749/RFC-2749.txt","version":null},{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2872","folder":"IETF/RFC-2872","source":"IETF/RFC-2872/RFC-2872.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2961","folder":"IETF/RFC-2961","source":"IETF/RFC-2961/RFC-2961.txt","version":null},{"body":"IETF","designation":"RFC 2996","folder":"IETF/RFC-2996","source":"IETF/RFC-2996/RFC-2996.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3139","folder":"IETF/RFC-3139","source":"IETF/RFC-3139/RFC-3139.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3210","folder":"IETF/RFC-3210","source":"IETF/RFC-3210/RFC-3210.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3469","folder":"IETF/RFC-3469","source":"IETF/RFC-3469/RFC-3469.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3524","folder":"IETF/RFC-3524","source":"IETF/RFC-3524/RFC-3524.txt","version":null},{"body":"IETF","designation":"RFC 3583","folder":"IETF/RFC-3583","source":"IETF/RFC-3583/RFC-3583.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3726","folder":"IETF/RFC-3726","source":"IETF/RFC-3726/RFC-3726.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3936","folder":"IETF/RFC-3936","source":"IETF/RFC-3936/RFC-3936.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4090","folder":"IETF/RFC-4090","source":"IETF/RFC-4090/RFC-4090.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 2205 This memo describes version 1 of RSVP, a resource reservation setup\n protocol designed for an integrated services Internet. RSVP provides\n receiver-initiated setup of resource reservations for multicast or\n unicast data flows, with good scaling and robustness properties.\n\nBraden, Ed., et. al. Standards Track [Page 1]\n\f\nRFC 2205 RSVP September 1997 2205 management path policy tsp nested-reference unchanged"},{"id":"IETF RFC 3198","type":"specification","body":"IETF","designation":"RFC 3198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3198.txt","https://www.rfc-editor.org/rfc/rfc3198.pdf"],"folder":"IETF/RFC-3198","files":{"txt":{"path":"standards/IETF/RFC-3198/RFC-3198.txt","sha256":"1bbf06068ecdf21bab9aec1a7d0765de41062951adb50e98cdac1155595580ff"}},"tags":["nested-reference","unchanged"],"summary":"This document is a glossary of policy-related terms. It provides\n abbreviations, explanations, and recommendations for use of these\n terms. The document takes the approach and format of RFC 2828, which\n defines an Internet Security Glossary. The intent is to improve the\n comprehensibility and consistency of writing that deals with network\n policy, particularly Internet Standards documents (ISDs).\n\nWesterinen, et al. Informational [Page 1]\n\f\nRFC 3198 Terminology for Policy-Based Management November 2001","scope_keywords":["3198","attribute","authentication","authorization","credential","credentials","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3809","folder":"IETF/RFC-3809","source":"IETF/RFC-3809/RFC-3809.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null}],"search_text":"IETF RFC 3198 This document is a glossary of policy-related terms. It provides\n abbreviations, explanations, and recommendations for use of these\n terms. The document takes the approach and format of RFC 2828, which\n defines an Internet Security Glossary. The intent is to improve the\n comprehensibility and consistency of writing that deals with network\n policy, particularly Internet Standards documents (ISDs).\n\nWesterinen, et al. Informational [Page 1]\n\f\nRFC 3198 Terminology for Policy-Based Management November 2001 3198 attribute authentication authorization credential credentials management policies policy nested-reference unchanged"},{"id":"IETF RFC 3551","type":"specification","body":"IETF","designation":"RFC 3551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3551.txt","https://www.rfc-editor.org/rfc/rfc3551.pdf"],"folder":"IETF/RFC-3551","files":{"pdf":{"path":"standards/IETF/RFC-3551/RFC-3551.pdf","sha256":"f09833577194065c4babd9239af38c2a0a21570326b32b81d208c1178632cdbd"},"txt":{"path":"standards/IETF/RFC-3551/RFC-3551.txt","sha256":"0b1a7fb6582f0e7ab6493f16d897009f0898600e7a9bcc1ee0d155a1c8157e56"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile called \"RTP/AVP\" for the use of the\n real-time transport protocol (RTP), version 2, and the associated\n control protocol, RTCP, within audio and video multiparticipant\n conferences with minimal control. It provides interpretations of\n generic fields within the RTP specification suitable for audio and\n video conferences. In particular, this document defines a set of\n default mappings from payload type numbers to encodings.\n\n This document also describes how audio and video data may be carried\n within RTP. It defines a set of standard encodings and their names\n when used within RTP. The descriptions provide pointers to reference\n implementations and the detailed standards. This document is meant\n as an aid for implementors of audio, video and other real-time\n multimedia applications.\n\n This memorandum obsoletes RFC 1890. It is mostly backwards-\n compatible","scope_keywords":["3551","key","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3556","folder":"IETF/RFC-3556","source":"IETF/RFC-3556/RFC-3556.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3551 This document describes a profile called \"RTP/AVP\" for the use of the\n real-time transport protocol (RTP), version 2, and the associated\n control protocol, RTCP, within audio and video multiparticipant\n conferences with minimal control. It provides interpretations of\n generic fields within the RTP specification suitable for audio and\n video conferences. In particular, this document defines a set of\n default mappings from payload type numbers to encodings.\n\n This document also describes how audio and video data may be carried\n within RTP. It defines a set of standard encodings and their names\n when used within RTP. The descriptions provide pointers to reference\n implementations and the detailed standards. This document is meant\n as an aid for implementors of audio, video and other real-time\n multimedia applications.\n\n This memorandum obsoletes RFC 1890. It is mostly backwards-\n compatible 3551 key profile profiles nested-reference unchanged"},{"id":"IETF RFC 3644","type":"specification","body":"IETF","designation":"RFC 3644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3644.txt","https://www.rfc-editor.org/rfc/rfc3644.pdf"],"folder":"IETF/RFC-3644","files":{"txt":{"path":"standards/IETF/RFC-3644/RFC-3644.txt","sha256":"1926937f181cc3e9d1b3f3ee22cca68f6404c2dbab50523102721f68d89c3c3c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an object-oriented information model for\n representing Quality of Service (QoS) network management policies.\n This document is based on the IETF Policy Core Information Model and\n its extensions. It defines an information model for QoS enforcement\n for differentiated and integrated services using policy. It is\n important to note that this document defines an information model,\n which by definition is independent of any particular data storage\n mechanism and access protocol.\n\nSnir, et al. Standards Track [Page 1]\n\f\nRFC 3644 Policy QoS Information Model November 2003","scope_keywords":["3644","management","policies","policy","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 3644 This document presents an object-oriented information model for\n representing Quality of Service (QoS) network management policies.\n This document is based on the IETF Policy Core Information Model and\n its extensions. It defines an information model for QoS enforcement\n for differentiated and integrated services using policy. It is\n important to note that this document defines an information model,\n which by definition is independent of any particular data storage\n mechanism and access protocol.\n\nSnir, et al. Standards Track [Page 1]\n\f\nRFC 3644 Policy QoS Information Model November 2003 3644 management policies policy profile profiles nested-reference unchanged"},{"id":"IETF RFC 4080","type":"specification","body":"IETF","designation":"RFC 4080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4080.txt","https://www.rfc-editor.org/rfc/rfc4080.pdf"],"folder":"IETF/RFC-4080","files":{"txt":{"path":"standards/IETF/RFC-4080/RFC-4080.txt","sha256":"d6dbe702b23b1e4eca328f9b90cfd0366580c73805e328aabbbae7d1f4ef6e7e"}},"tags":["nested-reference","unchanged"],"summary":"The Next Steps in Signaling (NSIS) working group is considering\n protocols for signaling information about a data flow along its path\n in the network. The NSIS suite of protocols is envisioned to support\n various signaling applications that need to install and/or manipulate\n such state in the network. Based on existing work on signaling\n requirements, this document proposes an architectural framework for\n these signaling protocols.\n\n This document provides a model for the network entities that take\n part in such signaling, and for the relationship between signaling\n and the rest of network operation. We decompose the overall\n signaling protocol suite into a generic (lower) layer, with separate\n upper layers for each specific signaling application.","scope_keywords":["4080","identification","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 4080 The Next Steps in Signaling (NSIS) working group is considering\n protocols for signaling information about a data flow along its path\n in the network. The NSIS suite of protocols is envisioned to support\n various signaling applications that need to install and/or manipulate\n such state in the network. Based on existing work on signaling\n requirements, this document proposes an architectural framework for\n these signaling protocols.\n\n This document provides a model for the network entities that take\n part in such signaling, and for the relationship between signaling\n and the rest of network operation. We decompose the overall\n signaling protocol suite into a generic (lower) layer, with separate\n upper layers for each specific signaling application. 4080 identification management path policy nested-reference unchanged"},{"id":"IETF RFC 4190","type":"specification","body":"IETF","designation":"RFC 4190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4190.txt","https://www.rfc-editor.org/rfc/rfc4190.pdf"],"folder":"IETF/RFC-4190","files":{"txt":{"path":"standards/IETF/RFC-4190/RFC-4190.txt","sha256":"e85c93d92b4bdb16152cac5ba03a0515dbeff706b4132009e3ae0f0b5aa1a62e"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a framework for supporting authorized,\n emergency-related communication within the context of IP telephony.\n We present a series of objectives that reflect a general view of how\n authorized emergency service, in line with the Emergency\n Telecommunications Service (ETS), should be realized within today's\n IP architecture and service models. From these objectives, we\n present a corresponding set of protocols and capabilities, which\n provide a more specific set of recommendations regarding existing\n IETF protocols. Finally, we present two scenarios that act as\n guiding models for the objectives and functions listed in this\n document. These models, coupled with an example of an existing\n service in the Public Switched Telephone Network (PSTN), contribute\n to a constrained solution space.\n\nCarlberg, et al. Informational [Page 1]\n\f\nRFC 4190 IP Telephony Framework Novembe","scope_keywords":["4190","authorization","identification","key","path","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null}],"search_text":"IETF RFC 4190 This document presents a framework for supporting authorized,\n emergency-related communication within the context of IP telephony.\n We present a series of objectives that reflect a general view of how\n authorized emergency service, in line with the Emergency\n Telecommunications Service (ETS), should be realized within today's\n IP architecture and service models. From these objectives, we\n present a corresponding set of protocols and capabilities, which\n provide a more specific set of recommendations regarding existing\n IETF protocols. Finally, we present two scenarios that act as\n guiding models for the objectives and functions listed in this\n document. These models, coupled with an example of an existing\n service in the Public Switched Telephone Network (PSTN), contribute\n to a constrained solution space.\n\nCarlberg, et al. Informational [Page 1]\n\f\nRFC 4190 IP Telephony Framework Novembe 4190 authorization identification key path policy subject nested-reference unchanged"},{"id":"IETF RFC 4542","type":"specification","body":"IETF","designation":"RFC 4542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4542.txt","https://www.rfc-editor.org/rfc/rfc4542.pdf"],"folder":"IETF/RFC-4542","files":{"txt":{"path":"standards/IETF/RFC-4542/RFC-4542.txt","sha256":"fe81ee2190ab5c3a9bb8a03d89ffb325d243bb4e971c55169bc4aee2b090e605"}},"tags":["nested-reference","unchanged"],"summary":"RFCs 3689 and 3690 detail requirements for an Emergency\n Telecommunications Service (ETS), of which an Internet Emergency\n Preparedness Service (IEPS) would be a part. Some of these types of\n services require call preemption; others require call queuing or\n other mechanisms. IEPS requires a Call Admission Control (CAC)\n procedure and a Per Hop Behavior (PHB) for the data that meet the\n needs of this architecture. Such a CAC procedure and PHB is\n appropriate to any service that might use H.323 or SIP to set up\n real-time sessions. The key requirement is to guarantee an elevated\n probability of call completion to an authorized user in time of\n crisis.\n\n This document primarily discusses supporting ETS in the context of\n the US Government and NATO, because it focuses on the Multi-Level\n Precedence and Preemption (MLPP) and Government Emergency\n Telecommunication Service (GETS) standards. Th","scope_keywords":["4542","authentication","authorization","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null}],"search_text":"IETF RFC 4542 RFCs 3689 and 3690 detail requirements for an Emergency\n Telecommunications Service (ETS), of which an Internet Emergency\n Preparedness Service (IEPS) would be a part. Some of these types of\n services require call preemption; others require call queuing or\n other mechanisms. IEPS requires a Call Admission Control (CAC)\n procedure and a Per Hop Behavior (PHB) for the data that meet the\n needs of this architecture. Such a CAC procedure and PHB is\n appropriate to any service that might use H.323 or SIP to set up\n real-time sessions. The key requirement is to guarantee an elevated\n probability of call completion to an authorized user in time of\n crisis.\n\n This document primarily discusses supporting ETS in the context of\n the US Government and NATO, because it focuses on the Multi-Level\n Precedence and Preemption (MLPP) and Government Emergency\n Telecommunication Service (GETS) standards. Th 4542 authentication authorization key policy nested-reference unchanged"},{"id":"IETF RFC 4842","type":"specification","body":"IETF","designation":"RFC 4842","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4842.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4842.txt","https://www.rfc-editor.org/rfc/rfc4842.pdf"],"folder":"IETF/RFC-4842","files":{"txt":{"path":"standards/IETF/RFC-4842/RFC-4842.txt","sha256":"618a44d85553618e065f345b990c6af8de64a6713367e778921da0f452e21034"}},"tags":["nested-reference","unchanged"],"summary":"This document provides encapsulation formats and semantics for\n emulating Synchronous Optical Network/Synchronous Digital Hierarchy\n (SONET/SDH) circuits and services over MPLS.\n\nMalis, et al. Standards Track [Page 1]\n\f\nRFC 4842 SONET/SDH Circuit Emulation April 2007","scope_keywords":["4842","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null}],"search_text":"IETF RFC 4842 This document provides encapsulation formats and semantics for\n emulating Synchronous Optical Network/Synchronous Digital Hierarchy\n (SONET/SDH) circuits and services over MPLS.\n\nMalis, et al. Standards Track [Page 1]\n\f\nRFC 4842 SONET/SDH Circuit Emulation April 2007 4842 key management trust nested-reference unchanged"},{"id":"IETF RFC 5127","type":"specification","body":"IETF","designation":"RFC 5127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5127.txt","https://www.rfc-editor.org/rfc/rfc5127.pdf"],"folder":"IETF/RFC-5127","files":{"txt":{"path":"standards/IETF/RFC-5127/RFC-5127.txt","sha256":"d497c6975fded88d000dc86e30044cd9647d3ba701a67a4a27cfc55535c28702"}},"tags":["nested-reference","unchanged"],"summary":"In the core of a high-capacity network, service differentiation may\n still be needed to support applications' utilization of the network.\n Applications with similar traffic characteristics and performance\n requirements are mapped into Diffserv service classes based on end-\n to-end behavior requirements of the applications. However, some\n network segments may be configured in such a way that a single\n forwarding treatment may satisfy the traffic characteristics and\n performance requirements of two or more service classes. In these\n cases, it may be desirable to aggregate two or more Diffserv service\n classes into a single forwarding treatment. This document provides\n guidelines for the aggregation of Diffserv service classes into\n forwarding treatments.\n\nChan, et al. Informational [Page 1]\n\f\nRFC 5127 Aggregation of Diffserv Service Classes February 2008","scope_keywords":["5127","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 5127 In the core of a high-capacity network, service differentiation may\n still be needed to support applications' utilization of the network.\n Applications with similar traffic characteristics and performance\n requirements are mapped into Diffserv service classes based on end-\n to-end behavior requirements of the applications. However, some\n network segments may be configured in such a way that a single\n forwarding treatment may satisfy the traffic characteristics and\n performance requirements of two or more service classes. In these\n cases, it may be desirable to aggregate two or more Diffserv service\n classes into a single forwarding treatment. This document provides\n guidelines for the aggregation of Diffserv service classes into\n forwarding treatments.\n\nChan, et al. Informational [Page 1]\n\f\nRFC 5127 Aggregation of Diffserv Service Classes February 2008 5127 path nested-reference unchanged"},{"id":"IETF RFC 5559","type":"specification","body":"IETF","designation":"RFC 5559","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5559.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5559.txt","https://www.rfc-editor.org/rfc/rfc5559.pdf"],"folder":"IETF/RFC-5559","files":{"txt":{"path":"standards/IETF/RFC-5559/RFC-5559.txt","sha256":"e8287e7c64826ea8b0e8548d799bb3911683dce862eb7ecd13e4436750c978d9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general architecture for flow admission and\n termination based on pre-congestion information in order to protect\n the quality of service of established, inelastic flows within a\n single Diffserv domain.\n\nEardley Informational [Page 1]\n\f\nRFC 5559 PCN Architecture June 2009","scope_keywords":["5559","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null}],"search_text":"IETF RFC 5559 This document describes a general architecture for flow admission and\n termination based on pre-congestion information in order to protect\n the quality of service of established, inelastic flows within a\n single Diffserv domain.\n\nEardley Informational [Page 1]\n\f\nRFC 5559 PCN Architecture June 2009 5559 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5974","type":"specification","body":"IETF","designation":"RFC 5974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5974.txt","https://www.rfc-editor.org/rfc/rfc5974.pdf"],"folder":"IETF/RFC-5974","files":{"txt":{"path":"standards/IETF/RFC-5974/RFC-5974.txt","sha256":"d6fc9934c310100dfa43945123e37b60eab47642a67a94c87f4408db7db8a4b0"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes the NSIS Signaling Layer Protocol (NSLP)\n for signaling Quality of Service (QoS) reservations in the Internet.\n It is in accordance with the framework and requirements developed in\n NSIS. Together with General Internet Signaling Transport (GIST), it\n provides functionality similar to RSVP and extends it. The QoS NSLP\n is independent of the underlying QoS specification or architecture\n and provides support for different reservation models. It is\n simplified by the elimination of support for multicast flows. This\n specification explains the overall protocol approach, describes the\n design decisions made, and provides examples. It specifies object,\n message formats, and processing rules.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This doc","scope_keywords":["5974","http","identification","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 5974 This specification describes the NSIS Signaling Layer Protocol (NSLP)\n for signaling Quality of Service (QoS) reservations in the Internet.\n It is in accordance with the framework and requirements developed in\n NSIS. Together with General Internet Signaling Transport (GIST), it\n provides functionality similar to RSVP and extends it. The QoS NSLP\n is independent of the underlying QoS specification or architecture\n and provides support for different reservation models. It is\n simplified by the elimination of support for multicast flows. This\n specification explains the overall protocol approach, describes the\n design decisions made, and provides examples. It specifies object,\n message formats, and processing rules.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This doc 5974 http identification license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5977","type":"specification","body":"IETF","designation":"RFC 5977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5977.txt","https://www.rfc-editor.org/rfc/rfc5977.pdf"],"folder":"IETF/RFC-5977","files":{"txt":{"path":"standards/IETF/RFC-5977/RFC-5977.txt","sha256":"b08a895fffaf6ed0277f3cdfcf963f4775feef6509dcd3866626bf2d57196fac"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Next Steps in Signaling (NSIS) Quality-of-\n Service (QoS) Model for networks that use the Resource Management in\n Diffserv (RMD) concept. RMD is a technique for adding admission\n control and preemption function to Differentiated Services (Diffserv)\n networks. The RMD QoS Model allows devices external to the RMD\n network to signal reservation requests to Edge nodes in the RMD\n network. The RMD Ingress Edge nodes classify the incoming flows into\n traffic classes and signals resource requests for the corresponding\n traffic class along the data path to the Egress Edge nodes for each\n flow. Egress nodes reconstitute the original requests and continue\n forwarding them along the data path towards the final destination.\n In addition, RMD defines notification functions to indicate overload\n situations within the domain to the Edge nodes.\n\nStatus of This Memo\n\n This docum","scope_keywords":["5977","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 5977 This document describes a Next Steps in Signaling (NSIS) Quality-of-\n Service (QoS) Model for networks that use the Resource Management in\n Diffserv (RMD) concept. RMD is a technique for adding admission\n control and preemption function to Differentiated Services (Diffserv)\n networks. The RMD QoS Model allows devices external to the RMD\n network to signal reservation requests to Edge nodes in the RMD\n network. The RMD Ingress Edge nodes classify the incoming flows into\n traffic classes and signals resource requests for the corresponding\n traffic class along the data path to the Egress Edge nodes for each\n flow. Egress nodes reconstitute the original requests and continue\n forwarding them along the data path towards the final destination.\n In addition, RMD defines notification functions to indicate overload\n situations within the domain to the Edge nodes.\n\nStatus of This Memo\n\n This docum 5977 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5978","type":"specification","body":"IETF","designation":"RFC 5978","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5978.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5978.txt","https://www.rfc-editor.org/rfc/rfc5978.pdf"],"folder":"IETF/RFC-5978","files":{"txt":{"path":"standards/IETF/RFC-5978/RFC-5978.txt","sha256":"dce5cf496b6e5bfaf04f044e06537b6653e871f315ca2a8a95480385e517f592"}},"tags":["nested-reference","unchanged"],"summary":"This document gives an overview of the Next Steps in Signaling (NSIS)\n framework and protocol suite created by the NSIS Working Group during\n the period of 2001-2010. It also includes suggestions on how the\n industry can make use of the new protocols and how the community can\n exploit the extensibility of both the framework and existing\n protocols to address future signaling needs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information ","scope_keywords":["5978","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null}],"search_text":"IETF RFC 5978 This document gives an overview of the Next Steps in Signaling (NSIS)\n framework and protocol suite created by the NSIS Working Group during\n the period of 2001-2010. It also includes suggestions on how the\n industry can make use of the new protocols and how the community can\n exploit the extensibility of both the framework and existing\n protocols to address future signaling needs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information  5978 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6057","type":"specification","body":"IETF","designation":"RFC 6057","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6057.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6057.txt","https://www.rfc-editor.org/rfc/rfc6057.pdf"],"folder":"IETF/RFC-6057","files":{"txt":{"path":"standards/IETF/RFC-6057/RFC-6057.txt","sha256":"e97ba222afb2487d88d6613a71ac0bfbb4f72dada996679e6566746217e77577"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the congestion management system of Comcast\n Cable, a large cable broadband Internet Service Provider (ISP) in the\n U.S. Comcast completed deployment of this congestion management\n system on December 31, 2008.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6057.\n\n","scope_keywords":["6057","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6789","folder":"IETF/RFC-6789","source":"IETF/RFC-6789/RFC-6789.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null}],"search_text":"IETF RFC 6057 This document describes the congestion management system of Comcast\n Cable, a large cable broadband Internet Service Provider (ISP) in the\n U.S. Comcast completed deployment of this congestion management\n system on December 31, 2008.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6057.\n\n 6057 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1636","type":"specification","body":"IETF","designation":"RFC 1636","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1636.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1636.txt","https://www.rfc-editor.org/rfc/rfc1636.pdf"],"folder":"IETF/RFC-1636","files":{"txt":{"path":"standards/IETF/RFC-1636/RFC-1636.txt","sha256":"4b7f65bfb480e8efb931a7aa35e39f0fefc34ec63c9c2ea43ac3423643960256"}},"tags":["nested-reference","unchanged"],"summary":"This document is a report on an Internet architecture workshop,\n initiated by the IAB and held at USC Information Sciences Institute\n on February 8-10, 1994. This workshop generally focused on security\n issues in the Internet architecture.\n\n This document should be regarded as a set of working notes containing\n ideas about security that were developed by Internet experts in a\n broad spectrum of areas, including routing, mobility, realtime\n service, and provider requirements, as well as security. It contains\n some significant diversity of opinions on some important issues.\n This memo is offered as one input in the process of developing viable\n security mechanisms and procedures for the Internet.\n\nBraden, Clark, Crocker & Huitema [Page 1]\n\f\nRFC 1636 IAB Workshop Report June 1994","scope_keywords":["1636","authentication","authorization","certificate","certificates","credential","credentials","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1821","folder":"IETF/RFC-1821","source":"IETF/RFC-1821/RFC-1821.txt","version":null},{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1826","folder":"IETF/RFC-1826","source":"IETF/RFC-1826/RFC-1826.txt","version":null},{"body":"IETF","designation":"RFC 1949","folder":"IETF/RFC-1949","source":"IETF/RFC-1949/RFC-1949.txt","version":null},{"body":"IETF","designation":"RFC 2082","folder":"IETF/RFC-2082","source":"IETF/RFC-2082/RFC-2082.txt","version":null},{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null}],"search_text":"IETF RFC 1636 This document is a report on an Internet architecture workshop,\n initiated by the IAB and held at USC Information Sciences Institute\n on February 8-10, 1994. This workshop generally focused on security\n issues in the Internet architecture.\n\n This document should be regarded as a set of working notes containing\n ideas about security that were developed by Internet experts in a\n broad spectrum of areas, including routing, mobility, realtime\n service, and provider requirements, as well as security. It contains\n some significant diversity of opinions on some important issues.\n This memo is offered as one input in the process of developing viable\n security mechanisms and procedures for the Internet.\n\nBraden, Clark, Crocker & Huitema [Page 1]\n\f\nRFC 1636 IAB Workshop Report June 1994 1636 authentication authorization certificate certificates credential credentials qualified trust nested-reference unchanged"},{"id":"IETF RFC 2337","type":"specification","body":"IETF","designation":"RFC 2337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2337.txt","https://www.rfc-editor.org/rfc/rfc2337.pdf"],"folder":"IETF/RFC-2337","files":{"txt":{"path":"standards/IETF/RFC-2337/RFC-2337.txt","sha256":"64b08e882e8017998d9d5f960a4eb1b2e2ee704cccb2418312851ba8b63de4b6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how intra-LIS IP multicast can be efficiently\n supported among routers over ATM without using the Multicast Address\n Resolution Server (MARS). The method described here is specific to\n Sparse Mode PIM [PIM-SM], and relies on the explicit join mechanism\n inherent in PIM-SM to notify routers when they should create group\n specific point-to-multipoint VCs.\n\n3. Overall model\n\n This document focuses on forwarding of multicast traffic among PIM-SM\n routers connected to an ATM network. Routers on an ATM network are\n partitioned into Logical IP Subnets, or LISs. This document deals\n with handling multicast within a single LIS. Handling inter-LIS\n multicast traffic, including handling shortcuts, is outside the scope\n of this document. In addition, this document does not address\n forwarding of multicast traffic to or from hosts connected to an ATM\n network.\n\nFarinacci, et. ","scope_keywords":["2337","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"IETF RFC 2337 This document describes how intra-LIS IP multicast can be efficiently\n supported among routers over ATM without using the Multicast Address\n Resolution Server (MARS). The method described here is specific to\n Sparse Mode PIM [PIM-SM], and relies on the explicit join mechanism\n inherent in PIM-SM to notify routers when they should create group\n specific point-to-multipoint VCs.\n\n3. Overall model\n\n This document focuses on forwarding of multicast traffic among PIM-SM\n routers connected to an ATM network. Routers on an ATM network are\n partitioned into Logical IP Subnets, or LISs. This document deals\n with handling multicast within a single LIS. Handling inter-LIS\n multicast traffic, including handling shortcuts, is outside the scope\n of this document. In addition, this document does not address\n forwarding of multicast traffic to or from hosts connected to an ATM\n network.\n\nFarinacci, et.  2337 pid nested-reference unchanged"},{"id":"IETF RFC 164","type":"specification","body":"IETF","designation":"RFC 164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc164.txt","https://www.rfc-editor.org/rfc/rfc164.pdf"],"folder":"IETF/RFC-164","files":{"txt":{"path":"standards/IETF/RFC-164/RFC-164.txt","sha256":"1fd66fc7ef298240a8739d3154bef52d99bec20bbe314b3793aadb5ab834008a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. F. Heafner\nRequest for Comments: 164 Rand\nNIC 6778\n\n MINUTES OF NETWORK WORKING GROUP MEETING\n 5/16 through 5/19/71\n\n Preface\n\n These notes are for reference and recall by those in attendance of\n the NWG meetings. No attempt has been made toward completeness to\n make this an understandable document for those not in attendance.\n\n The notes are ordered chronologically. You may notice discrepancies\n for particular schedules and tasks within the notes; the\n discrepancies represent a revision of those schedules and tasks, thus\n those dates given more recent in time are assumed to apply.\n\n If you detect any gross errors in this report, please make\n corrections via the accepted NIC procedures.\n\n CONTENTS\n\n I. SUNDAY EVENING SESSION (5/10/71) ................. 4\n\n Introduction of Attendees ........................ 4\n Site Status Reports .............................. 6\n\n","scope_keywords":["164","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 173","folder":"IETF/RFC-173","source":"IETF/RFC-173/RFC-173.txt","version":null}],"search_text":"IETF RFC 164 Network Working Group J. F. Heafner\nRequest for Comments: 164 Rand\nNIC 6778\n\n MINUTES OF NETWORK WORKING GROUP MEETING\n 5/16 through 5/19/71\n\n Preface\n\n These notes are for reference and recall by those in attendance of\n the NWG meetings. No attempt has been made toward completeness to\n make this an understandable document for those not in attendance.\n\n The notes are ordered chronologically. You may notice discrepancies\n for particular schedules and tasks within the notes; the\n discrepancies represent a revision of those schedules and tasks, thus\n those dates given more recent in time are assumed to apply.\n\n If you detect any gross errors in this report, please make\n corrections via the accepted NIC procedures.\n\n CONTENTS\n\n I. SUNDAY EVENING SESSION (5/10/71) ................. 4\n\n Introduction of Attendees ........................ 4\n Site Status Reports .............................. 6\n\n 164 management validation nested-reference unchanged"},{"id":"IETF RFC 2279","type":"specification","body":"IETF","designation":"RFC 2279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2279.txt","https://www.rfc-editor.org/rfc/rfc2279.pdf"],"folder":"IETF/RFC-2279","files":{"txt":{"path":"standards/IETF/RFC-2279/RFC-2279.txt","sha256":"e7873c93473ef2e21db92a4702f8e743fe5b70ff9ebef1096896aafe1ab0144d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Yergeau\nRequest for Comments: 2279 Alis Technologies\nObsoletes: 2044 January 1998\nCategory: Standards Track\n\n UTF-8, a transformation format of ISO 10646\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n ISO/IEC 10646-1 defines a multi-octet character set called the\n Universal Character Set (UCS) which encompasses most of the world's\n writing systems. Multi-octet characters, however, are not compatible\n with many current applications and protocols, and this has ","scope_keywords":["2279","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2610","folder":"IETF/RFC-2610","source":"IETF/RFC-2610/RFC-2610.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2718","folder":"IETF/RFC-2718","source":"IETF/RFC-2718/RFC-2718.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2965","folder":"IETF/RFC-2965","source":"IETF/RFC-2965/RFC-2965.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4630","folder":"IETF/RFC-4630","source":"IETF/RFC-4630/RFC-4630.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 2279 Network Working Group F. Yergeau\nRequest for Comments: 2279 Alis Technologies\nObsoletes: 2044 January 1998\nCategory: Standards Track\n\n UTF-8, a transformation format of ISO 10646\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n ISO/IEC 10646-1 defines a multi-octet character set called the\n Universal Character Set (UCS) which encompasses most of the world's\n writing systems. Multi-octet characters, however, are not compatible\n with many current applications and protocols, and this has  2279 algorithm nested-reference unchanged"},{"id":"IETF RFC 1644","type":"specification","body":"IETF","designation":"RFC 1644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1644.txt","https://www.rfc-editor.org/rfc/rfc1644.pdf"],"folder":"IETF/RFC-1644","files":{"txt":{"path":"standards/IETF/RFC-1644/RFC-1644.txt","sha256":"6270a27fd18f8a1b100946067db8aefd0f1969c1e28876409eaa72584a8a0e3f"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies T/TCP, an experimental TCP extension for\n efficient transaction-oriented (request/response) service. This\n backwards-compatible extension could fill the gap between the current\n connection-oriented TCP and the datagram-based UDP.\n\n This work was supported in part by the National Science Foundation\n under Grant Number NCR-8922231.","scope_keywords":["1644","algorithm","algorithms","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6247","folder":"IETF/RFC-6247","source":"IETF/RFC-6247/RFC-6247.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1644 This memo specifies T/TCP, an experimental TCP extension for\n efficient transaction-oriented (request/response) service. This\n backwards-compatible extension could fill the gap between the current\n connection-oriented TCP and the datagram-based UDP.\n\n This work was supported in part by the National Science Foundation\n under Grant Number NCR-8922231. 1644 algorithm algorithms delivery management nested-reference unchanged"},{"id":"IETF RFC 172","type":"specification","body":"IETF","designation":"RFC 172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc172.txt","https://www.rfc-editor.org/rfc/rfc172.pdf"],"folder":"IETF/RFC-172","files":{"txt":{"path":"standards/IETF/RFC-172/RFC-172.txt","sha256":"160564edc3160cd4b1c81768d4e25867085608d200155e915ddcc738332eb394"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 23 June 1971\nRequest for Comments #172 Abhay Bhushan, MIT\nNIC 6794 Bob Braden, UCLA\nCategories: D.4, D.5, and D.7 Will Crowther, BBN\nUpdates: 114 Eric Harslem, Rand\nObsolete: None John Heafner, Rand\n Alex McKenzie, BBN\n John Melvin, SRI\n Bob Sundberg, Harvard\n Dick Watson, SRI\n Jim White, UCSB\n\n THE FILE TRANSFER PROTOCOL\n\n [Page 1]\n\f\nNWG/RFC 172\n\nI. INTRODUCTION\n\n The file transfer protocol (FTP) is a user-level protocol for file\ntransfer between host computers (including terminal IMP's), on the ARPA\ncomputer network. The primary function of FTP is to facilitate transfer\nof files between hosts, and to allow convenient use of storage and file\nhandling capabilities of other hosts. FTP uses the data transfer\nprotocol described in RFC 171 to achieve transfer of data. This paper\nassumes knowledge of RFC 171.\n\n The objectives of FTP are to promote sharing of files (compu","scope_keywords":["172","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 171","folder":"IETF/RFC-171","source":"IETF/RFC-171/RFC-171.txt","version":null},{"body":"IETF","designation":"RFC 265","folder":"IETF/RFC-265","source":"IETF/RFC-265/RFC-265.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 172 Network Working Group 23 June 1971\nRequest for Comments #172 Abhay Bhushan, MIT\nNIC 6794 Bob Braden, UCLA\nCategories: D.4, D.5, and D.7 Will Crowther, BBN\nUpdates: 114 Eric Harslem, Rand\nObsolete: None John Heafner, Rand\n Alex McKenzie, BBN\n John Melvin, SRI\n Bob Sundberg, Harvard\n Dick Watson, SRI\n Jim White, UCSB\n\n THE FILE TRANSFER PROTOCOL\n\n [Page 1]\n\f\nNWG/RFC 172\n\nI. INTRODUCTION\n\n The file transfer protocol (FTP) is a user-level protocol for file\ntransfer between host computers (including terminal IMP's), on the ARPA\ncomputer network. The primary function of FTP is to facilitate transfer\nof files between hosts, and to allow convenient use of storage and file\nhandling capabilities of other hosts. FTP uses the data transfer\nprotocol described in RFC 171 to achieve transfer of data. This paper\nassumes knowledge of RFC 171.\n\n The objectives of FTP are to promote sharing of files (compu 172 path subject nested-reference unchanged"},{"id":"IETF RFC 264","type":"specification","body":"IETF","designation":"RFC 264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc264.txt","https://www.rfc-editor.org/rfc/rfc264.pdf"],"folder":"IETF/RFC-264","files":{"txt":{"path":"standards/IETF/RFC-264/RFC-264.txt","sha256":"476bcb1fc90a56362a00e33acff05da43fc53eb41a745f34ef392ee0f11ce063"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Bhushan\nRequest for Comments: 264 MIT\nNIC: 7812 B. Braden\n UCLA\n W. Crowther\n BBN\n E. Harslem\n J. Heafner\n Rand\n A. McKenzie\n BBN\n J. Melvin\n SRI\n B. Sundberg\n Harvard\n D. Watson\n SRI\n J. White\n UCSB\n 15 November 1971\n\n THE DATA TRANSFER PROTOCOL\n\n This paper is a revision of RFC 171, NIC 6793. The changes to RFC\n 171 are given below. The protocol is then restated for your\n convenience.\n\nCHANGES TO RFC 171\n\n 1) The sequence number field is changed to 16 bits in the error (Type\n B5) transactions, thus resolving the ambiguity in the previous\n specification. In addition, the information separators (Type B4)\n transactions shall also contain a 16-bit sequence number field.\n\n 2) The modes available (Type B3) transactions shall define only the\n modes available for receive, instead of both receive and send. In\n simplex connections modes available transactions should not ","scope_keywords":["264"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 265","folder":"IETF/RFC-265","source":"IETF/RFC-265/RFC-265.txt","version":null},{"body":"IETF","designation":"RFC 354","folder":"IETF/RFC-354","source":"IETF/RFC-354/RFC-354.txt","version":null}],"search_text":"IETF RFC 264 Network Working Group A. Bhushan\nRequest for Comments: 264 MIT\nNIC: 7812 B. Braden\n UCLA\n W. Crowther\n BBN\n E. Harslem\n J. Heafner\n Rand\n A. McKenzie\n BBN\n J. Melvin\n SRI\n B. Sundberg\n Harvard\n D. Watson\n SRI\n J. White\n UCSB\n 15 November 1971\n\n THE DATA TRANSFER PROTOCOL\n\n This paper is a revision of RFC 171, NIC 6793. The changes to RFC\n 171 are given below. The protocol is then restated for your\n convenience.\n\nCHANGES TO RFC 171\n\n 1) The sequence number field is changed to 16 bits in the error (Type\n B5) transactions, thus resolving the ambiguity in the previous\n specification. In addition, the information separators (Type B4)\n transactions shall also contain a 16-bit sequence number field.\n\n 2) The modes available (Type B3) transactions shall define only the\n modes available for receive, instead of both receive and send. In\n simplex connections modes available transactions should not  264 nested-reference unchanged"},{"id":"IETF RFC 265","type":"specification","body":"IETF","designation":"RFC 265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc265.txt","https://www.rfc-editor.org/rfc/rfc265.pdf"],"folder":"IETF/RFC-265","files":{"txt":{"path":"standards/IETF/RFC-265/RFC-265.txt","sha256":"dfe1bcb8a67a2970ab76d5cb83d002430ca5421110efec0c67d9c79aca7c39d9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 17 November 1971\nRequest for Comments #265 Abbay Bhushan, MIT\nNIC 781 Bob Braden, UCLA\nCategories D.4, D.5, and D.7 Will Crowther, BBN\n Eric Narslem, Rand\nObsoletes: 172 John Heafner, Rand\n Alex McKenzie, BBH\n John Melvin, SRI\n Bob Sundberg, Harvard\n Dick Watson, SRI\n Jim White, UOSB\n\n THE FILE TRANSFER PROTOCOL\n\n This Paper is a revision of RF 172, Mic 6794. The changes\nto RFC 172 are given below. The protocol is then restated for\nyour ocnvenience.\n\n CHANGES TO RFC 172\n\n1) Two new file transfer requests have been added. These are\n\n2) The op code assignements in control transactions have been\nchanged to include the above requests.\n\n3) Two new error codes indicating 'incorrect or missing\nindentifier' and 'file already exists' have been added. New error\ncode assignements reflect this change.\n\n4) Editorial changes to clarify specifications.\n\n [Page 1]\n\f\nFile Transfer P","scope_keywords":["265","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 264","folder":"IETF/RFC-264","source":"IETF/RFC-264/RFC-264.txt","version":null},{"body":"IETF","designation":"RFC 294","folder":"IETF/RFC-294","source":"IETF/RFC-294/RFC-294.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 265 Network Working Group 17 November 1971\nRequest for Comments #265 Abbay Bhushan, MIT\nNIC 781 Bob Braden, UCLA\nCategories D.4, D.5, and D.7 Will Crowther, BBN\n Eric Narslem, Rand\nObsoletes: 172 John Heafner, Rand\n Alex McKenzie, BBH\n John Melvin, SRI\n Bob Sundberg, Harvard\n Dick Watson, SRI\n Jim White, UOSB\n\n THE FILE TRANSFER PROTOCOL\n\n This Paper is a revision of RF 172, Mic 6794. The changes\nto RFC 172 are given below. The protocol is then restated for\nyour ocnvenience.\n\n CHANGES TO RFC 172\n\n1) Two new file transfer requests have been added. These are\n\n2) The op code assignements in control transactions have been\nchanged to include the above requests.\n\n3) Two new error codes indicating 'incorrect or missing\nindentifier' and 'file already exists' have been added. New error\ncode assignements reflect this change.\n\n4) Editorial changes to clarify specifications.\n\n [Page 1]\n\f\nFile Transfer P 265 management path subject nested-reference unchanged"},{"id":"IETF RFC 3030","type":"specification","body":"IETF","designation":"RFC 3030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3030.txt","https://www.rfc-editor.org/rfc/rfc3030.pdf"],"folder":"IETF/RFC-3030","files":{"txt":{"path":"standards/IETF/RFC-3030/RFC-3030.txt","sha256":"e21754fb6e2eece84b0754e31e3b997f1a7ec5731ad8c6449010af70ecfc7794"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines two extensions to the SMTP (Simple Mail Transfer\n Protocol) service. The first extension enables a SMTP client and\n server to negotiate the use of an alternative to the DATA command,\n called \"BDAT\", for efficiently sending large MIME (Multipurpose\n Internet Mail Extensions) messages. The second extension takes\n advantage of the BDAT command to permit the negotiated sending of\n MIME messages that employ the binary transfer encoding. This\n document is intended to update and obsolete RFC 1830.\n\nWorking Group Summary\n\n This protocol is not the product of an IETF working group, however\n the specification resulted from discussions within the ESMTP working\n group. The resulting protocol documented in RFC 1830 was classified\n as experimental at that time due to questions about the robustness of\n the Binary Content-Transfer-Encoding deployed in then existent MIME\n implementation","scope_keywords":["3030","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 3030 This memo defines two extensions to the SMTP (Simple Mail Transfer\n Protocol) service. The first extension enables a SMTP client and\n server to negotiate the use of an alternative to the DATA command,\n called \"BDAT\", for efficiently sending large MIME (Multipurpose\n Internet Mail Extensions) messages. The second extension takes\n advantage of the BDAT command to permit the negotiated sending of\n MIME messages that employ the binary transfer encoding. This\n document is intended to update and obsolete RFC 1830.\n\nWorking Group Summary\n\n This protocol is not the product of an IETF working group, however\n the specification resulted from discussions within the ESMTP working\n group. The resulting protocol documented in RFC 1830 was classified\n as experimental at that time due to questions about the robustness of\n the Binary Content-Transfer-Encoding deployed in then existent MIME\n implementation 3030 key nested-reference unchanged"},{"id":"IETF RFC 4468","type":"specification","body":"IETF","designation":"RFC 4468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4468.txt","https://www.rfc-editor.org/rfc/rfc4468.pdf"],"folder":"IETF/RFC-4468","files":{"txt":{"path":"standards/IETF/RFC-4468/RFC-4468.txt","sha256":"68a9f492de79176d7d404d1cda924a0817e5f1da70be9735891893c330eeffa4"}},"tags":["nested-reference","unchanged"],"summary":"The submission profile of Simple Mail Transfer Protocol (SMTP)\n provides a standard way for an email client to submit a complete\n message for delivery. This specification extends the submission\n profile by adding a new BURL command that can be used to fetch\n submission data from an Internet Message Access Protocol (IMAP)\n server. This permits a mail client to inject content from an IMAP\n server into the SMTP infrastructure without downloading it to the\n client and uploading it back to the server.\n\nNewman Standards Track [Page 1]\n\f\nRFC 4468 Message Submission BURL Extension May 2006","scope_keywords":["4468","authentication","credential","credentials","delivery","key","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null}],"search_text":"IETF RFC 4468 The submission profile of Simple Mail Transfer Protocol (SMTP)\n provides a standard way for an email client to submit a complete\n message for delivery. This specification extends the submission\n profile by adding a new BURL command that can be used to fetch\n submission data from an Internet Message Access Protocol (IMAP)\n server. This permits a mail client to inject content from an IMAP\n server into the SMTP infrastructure without downloading it to the\n client and uploading it back to the server.\n\nNewman Standards Track [Page 1]\n\f\nRFC 4468 Message Submission BURL Extension May 2006 4468 authentication credential credentials delivery key profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 4550","type":"specification","body":"IETF","designation":"RFC 4550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4550.txt","https://www.rfc-editor.org/rfc/rfc4550.pdf"],"folder":"IETF/RFC-4550","files":{"txt":{"path":"standards/IETF/RFC-4550/RFC-4550.txt","sha256":"2ffd5daafc30e375cdafcc39f86e39e99e179bb26a713f7b4cb4ebeed70949c5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile (a set of required extensions,\n restrictions, and usage modes) of the IMAP and mail submission\n protocols. This profile allows clients (especially those that are\n constrained in memory, bandwidth, processing power, or other areas)\n to efficiently use IMAP and Submission to access and submit mail.\n This includes the ability to forward received mail without needing to\n download and upload the mail, to optimize submission, and to\n efficiently resynchronize in case of loss of connectivity with the\n server.\n\n The Internet Email to Support Diverse Service Environments (Lemonade)\n profile relies upon extensions to IMAP and Mail Submission protocols;\n specifically, the URLAUTH and CATENATE IMAP protocol (RFC 3501)\n extensions and the BURL extension to the SUBMIT protocol (RFC 4409).\n\nMaes & Melnikov Standards Track [Page 1]\n\f\nRFC 4550 Lemonade Profile June 2006","scope_keywords":["4550","key","profile","risk","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 4550 This document describes a profile (a set of required extensions,\n restrictions, and usage modes) of the IMAP and mail submission\n protocols. This profile allows clients (especially those that are\n constrained in memory, bandwidth, processing power, or other areas)\n to efficiently use IMAP and Submission to access and submit mail.\n This includes the ability to forward received mail without needing to\n download and upload the mail, to optimize submission, and to\n efficiently resynchronize in case of loss of connectivity with the\n server.\n\n The Internet Email to Support Diverse Service Environments (Lemonade)\n profile relies upon extensions to IMAP and Mail Submission protocols;\n specifically, the URLAUTH and CATENATE IMAP protocol (RFC 3501)\n extensions and the BURL extension to the SUBMIT protocol (RFC 4409).\n\nMaes & Melnikov Standards Track [Page 1]\n\f\nRFC 4550 Lemonade Profile June 2006 4550 key profile risk tls trust nested-reference unchanged"},{"id":"IETF RFC 4952","type":"specification","body":"IETF","designation":"RFC 4952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4952.txt","https://www.rfc-editor.org/rfc/rfc4952.pdf"],"folder":"IETF/RFC-4952","files":{"txt":{"path":"standards/IETF/RFC-4952/RFC-4952.txt","sha256":"3d83c9ff88002889b824a9c97dfae8b772323bccfb0716196730ab281471903e"}},"tags":["nested-reference","unchanged"],"summary":"Full use of electronic mail throughout the world requires that people\n be able to use their own names, written correctly in their own\n languages and scripts, as mailbox names in email addresses. This\n document introduces a series of specifications that define mechanisms\n and protocol extensions needed to fully support internationalized\n email addresses. These changes include an SMTP extension and\n extension of email header syntax to accommodate UTF-8 data. The\n document set also includes discussion of key assumptions and issues\n in deploying fully internationalized email.\n\nKlensin & Ko Informational [Page 1]\n\f\nRFC 4952 EAI Framework July 2007","scope_keywords":["4952","delivery","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 4952 Full use of electronic mail throughout the world requires that people\n be able to use their own names, written correctly in their own\n languages and scripts, as mailbox names in email addresses. This\n document introduces a series of specifications that define mechanisms\n and protocol extensions needed to fully support internationalized\n email addresses. These changes include an SMTP extension and\n extension of email header syntax to accommodate UTF-8 data. The\n document set also includes discussion of key assumptions and issues\n in deploying fully internationalized email.\n\nKlensin & Ko Informational [Page 1]\n\f\nRFC 4952 EAI Framework July 2007 4952 delivery key trust nested-reference unchanged"},{"id":"IETF RFC 5335","type":"specification","body":"IETF","designation":"RFC 5335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5335.txt","https://www.rfc-editor.org/rfc/rfc5335.pdf"],"folder":"IETF/RFC-5335","files":{"txt":{"path":"standards/IETF/RFC-5335/RFC-5335.txt","sha256":"371877e3ecd35ff5bb94f84fa97edeec2ea4bb5655064883ab0445731c38f5ef"}},"tags":["nested-reference","unchanged"],"summary":"Full internationalization of electronic mail requires not only the\n capabilities to transmit non-ASCII content, to encode selected\n information in specific header fields, and to use non-ASCII\n characters in envelope addresses. It also requires being able to\n express those addresses and the information based on them in mail\n header fields. This document specifies an experimental variant of\n Internet mail that permits the use of Unicode encoded in UTF-8,\n rather than ASCII, as the base form for Internet email header field.\n This form is permitted in transmission only if authorized by an SMTP\n extension, as specified in an associated specification. This\n specification Updates section 6.4 of RFC 2045 to conform with the\n requirements.\n\nAbel Experimental [Page 1]\n\f\nRFC 5335 I18N Email Headers September 2008","scope_keywords":["5335","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 5335 Full internationalization of electronic mail requires not only the\n capabilities to transmit non-ASCII content, to encode selected\n information in specific header fields, and to use non-ASCII\n characters in envelope addresses. It also requires being able to\n express those addresses and the information based on them in mail\n header fields. This document specifies an experimental variant of\n Internet mail that permits the use of Unicode encoded in UTF-8,\n rather than ASCII, as the base form for Internet email header field.\n This form is permitted in transmission only if authorized by an SMTP\n extension, as specified in an associated specification. This\n specification Updates section 6.4 of RFC 2045 to conform with the\n requirements.\n\nAbel Experimental [Page 1]\n\f\nRFC 5335 I18N Email Headers September 2008 5335 key subject nested-reference unchanged"},{"id":"IETF RFC 5504","type":"specification","body":"IETF","designation":"RFC 5504","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5504.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5504.txt","https://www.rfc-editor.org/rfc/rfc5504.pdf"],"folder":"IETF/RFC-5504","files":{"txt":{"path":"standards/IETF/RFC-5504/RFC-5504.txt","sha256":"a213345b350d124d031b897413f794d0f1ecfda587680ce4f9b6842542de13ff"}},"tags":["nested-reference","unchanged"],"summary":"Traditional mail systems handle only ASCII characters in SMTP\n envelope and mail header fields. The Email Address\n Internationalization (UTF8SMTP) extension allows UTF-8 characters in\n SMTP envelope and mail header fields. To avoid rejecting\n internationalized email messages when a server in the delivery path\n does not support the UTF8SMTP extension, some sort of converting\n mechanism is required. This document describes a downgrading\n mechanism for Email Address Internationalization. Note that this is\n a way to downgrade, not tunnel. There is no associated up-conversion\n mechanism, although internationalized email clients might use\n original internationalized addresses or other data when displaying or\n replying to downgraded messages.\n\nFujiwara & Yoneya Experimental [Page 1]\n\f\nRFC 5504 UTF8SMTP Downgrade March 2009","scope_keywords":["5504","delivery","http","license","path","presentation","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null}],"search_text":"IETF RFC 5504 Traditional mail systems handle only ASCII characters in SMTP\n envelope and mail header fields. The Email Address\n Internationalization (UTF8SMTP) extension allows UTF-8 characters in\n SMTP envelope and mail header fields. To avoid rejecting\n internationalized email messages when a server in the delivery path\n does not support the UTF8SMTP extension, some sort of converting\n mechanism is required. This document describes a downgrading\n mechanism for Email Address Internationalization. Note that this is\n a way to downgrade, not tunnel. There is no associated up-conversion\n mechanism, although internationalized email clients might use\n original internationalized addresses or other data when displaying or\n replying to downgraded messages.\n\nFujiwara & Yoneya Experimental [Page 1]\n\f\nRFC 5504 UTF8SMTP Downgrade March 2009 5504 delivery http license path presentation preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 5550","type":"specification","body":"IETF","designation":"RFC 5550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5550.txt","https://www.rfc-editor.org/rfc/rfc5550.pdf"],"folder":"IETF/RFC-5550","files":{"txt":{"path":"standards/IETF/RFC-5550/RFC-5550.txt","sha256":"6576fe340607aac2af38424c4d2a114dd744b9ae3d1e03d3288f0c4888cd6b51"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile (a set of required extensions,\n restrictions, and usage modes), dubbed Lemonade, of the IMAP, mail\n submission, and Sieve protocols. This profile allows clients\n (especially those that are constrained in memory, bandwidth,\n processing power, or other areas) to efficiently use IMAP and\n Submission to access and submit mail. This includes the ability to\n forward received mail without needing to download and upload the\n mail, to optimize submission, and to efficiently resynchronize in\n case of loss of connectivity with the server.\n\n The Lemonade Profile relies upon several extensions to IMAP, Sieve,\n and Mail Submission protocols. The document also defines a new IMAP\n extension and registers several new IMAP keywords.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and ","scope_keywords":["5550","delivery","encryption","http","key","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null}],"search_text":"IETF RFC 5550 This document describes a profile (a set of required extensions,\n restrictions, and usage modes), dubbed Lemonade, of the IMAP, mail\n submission, and Sieve protocols. This profile allows clients\n (especially those that are constrained in memory, bandwidth,\n processing power, or other areas) to efficiently use IMAP and\n Submission to access and submit mail. This includes the ability to\n forward received mail without needing to download and upload the\n mail, to optimize submission, and to efficiently resynchronize in\n case of loss of connectivity with the server.\n\n The Lemonade Profile relies upon several extensions to IMAP, Sieve,\n and Mail Submission protocols. The document also defines a new IMAP\n extension and registers several new IMAP keywords.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and  5550 delivery encryption http key license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6047","type":"specification","body":"IETF","designation":"RFC 6047","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6047.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6047.txt","https://www.rfc-editor.org/rfc/rfc6047.pdf"],"folder":"IETF/RFC-6047","files":{"txt":{"path":"standards/IETF/RFC-6047/RFC-6047.txt","sha256":"79d66621adbef4ad5cead0a84b4952fe931e935ad12a50adad4694579711d579"}},"tags":["nested-reference","unchanged"],"summary":"This document, \"iCalendar Message-Based Interoperability Protocol\n (iMIP)\", specifies a binding from the iCalendar Transport-independent\n Interoperability Protocol (iTIP) to Internet email-based transports.\n Calendaring entries defined by the iCalendar Object Model (iCalendar)\n are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC\n 2046, RFC 2047, and RFC 2049), and then transported over SMTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f","scope_keywords":["6047","authentication","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 6047 This document, \"iCalendar Message-Based Interoperability Protocol\n (iMIP)\", specifies a binding from the iCalendar Transport-independent\n Interoperability Protocol (iTIP) to Internet email-based transports.\n Calendaring entries defined by the iCalendar Object Model (iCalendar)\n are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC\n 2046, RFC 2047, and RFC 2049), and then transported over SMTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f 6047 authentication authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2650","type":"specification","body":"IETF","designation":"RFC 2650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2650.txt","https://www.rfc-editor.org/rfc/rfc2650.pdf"],"folder":"IETF/RFC-2650","files":{"txt":{"path":"standards/IETF/RFC-2650/RFC-2650.txt","sha256":"3dab2b7006af2019d3e23b2d94999bdc0dcf1e8f91e6ef3d38b955925f441bce"}},"tags":["nested-reference","unchanged"],"summary":"This document is a tutorial on using the Routing Policy Specification\n Language (RPSL) to describe routing policies in the Internet Routing\n Registry (IRR). We explain how to specify various routing policies\n and configurations using RPSL, how to register these policies in the\n IRR, and how to analyze them using the routing policy analysis tools,\n for example to generate vendor specific router configurations.\n\n1 Introduction\n\n This document is a tutorial on RPSL and is targeted towards an\n Internet/Network Service Provider (ISP/NSP) engineer who understands\n Internet routing, but is new to RPSL and to the IRR. Readers are\n referred to the RPSL reference document (RFC 2622) [1] for\n completeness. It is also good to have that document at hand while\n working through this tutorial.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"","scope_keywords":["2650","attribute","attributes","key","path","policies","policy","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null}],"search_text":"IETF RFC 2650 This document is a tutorial on using the Routing Policy Specification\n Language (RPSL) to describe routing policies in the Internet Routing\n Registry (IRR). We explain how to specify various routing policies\n and configurations using RPSL, how to register these policies in the\n IRR, and how to analyze them using the routing policy analysis tools,\n for example to generate vendor specific router configurations.\n\n1 Introduction\n\n This document is a tutorial on RPSL and is targeted towards an\n Internet/Network Service Provider (ISP/NSP) engineer who understands\n Internet routing, but is new to RPSL and to the IRR. Readers are\n referred to the RPSL reference document (RFC 2622) [1] for\n completeness. It is also good to have that document at hand while\n working through this tutorial.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \" 2650 attribute attributes key path policies policy presentation registered nested-reference unchanged"},{"id":"IETF RFC 1663","type":"specification","body":"IETF","designation":"RFC 1663","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1663.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1663.txt","https://www.rfc-editor.org/rfc/rfc1663.pdf"],"folder":"IETF/RFC-1663","files":{"txt":{"path":"standards/IETF/RFC-1663/RFC-1663.txt","sha256":"2e64b1b49b3e021ef25ec2de1bc257338b413e83bb453a619fe83d5ccc27abff"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document defines a method for negotiating and using Numbered-\n Mode, as defined by ISO 7776 [2], to provide a reliable serial link.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@ucdavis.edu mailing list.","scope_keywords":["1663","delivery","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1962","folder":"IETF/RFC-1962","source":"IETF/RFC-1962/RFC-1962.txt","version":null},{"body":"IETF","designation":"RFC 1967","folder":"IETF/RFC-1967","source":"IETF/RFC-1967/RFC-1967.txt","version":null},{"body":"IETF","designation":"RFC 1968","folder":"IETF/RFC-1968","source":"IETF/RFC-1968/RFC-1968.txt","version":null},{"body":"IETF","designation":"RFC 1974","folder":"IETF/RFC-1974","source":"IETF/RFC-1974/RFC-1974.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 1993","folder":"IETF/RFC-1993","source":"IETF/RFC-1993/RFC-1993.txt","version":null},{"body":"IETF","designation":"RFC 2118","folder":"IETF/RFC-2118","source":"IETF/RFC-2118/RFC-2118.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1663 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document defines a method for negotiating and using Numbered-\n Mode, as defined by ISO 7776 [2], to provide a reliable serial link.\n\n This document is the product of the Point-to-Point Protocol Working\n Group of the Internet Engineering Task Force (IETF). Comments should\n be submitted to the ietf-ppp@ucdavis.edu mailing list. 1663 delivery subject nested-reference unchanged"},{"id":"IETF RFC 1967","type":"specification","body":"IETF","designation":"RFC 1967","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1967.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1967.txt","https://www.rfc-editor.org/rfc/rfc1967.pdf"],"folder":"IETF/RFC-1967","files":{"txt":{"path":"standards/IETF/RFC-1967/RFC-1967.txt","sha256":"d8f5af3c71d45da93cc13c1e77dc1e2bd43374b82c4116e0f0ddbf9cb93b44d3"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Stac LZS data compression\n algorithm for compressing PPP encapsulated packets, using a DCP\n header [6]. This protocol is an enhanced version of the non-DCP\n (Option 17) PPP Stac LZS compression protocol [5], and will be\n referred to as the LZS-DCP Compression Protocol.","scope_keywords":["1967","algorithm","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null}],"search_text":"IETF RFC 1967 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Stac LZS data compression\n algorithm for compressing PPP encapsulated packets, using a DCP\n header [6]. This protocol is an enhanced version of the non-DCP\n (Option 17) PPP Stac LZS compression protocol [5], and will be\n referred to as the LZS-DCP Compression Protocol. 1967 algorithm license nested-reference unchanged"},{"id":"IETF RFC 1974","type":"specification","body":"IETF","designation":"RFC 1974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1974.txt","https://www.rfc-editor.org/rfc/rfc1974.pdf"],"folder":"IETF/RFC-1974","files":{"txt":{"path":"standards/IETF/RFC-1974/RFC-1974.txt","sha256":"dfb04c1afe41405b05714ea44df0663a51dad94343c606efff696f5a55689037"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Stac LZS data compression\n algorithm, with single or multiple compression histories, for\n compressing PPP encapsulated packets.","scope_keywords":["1974","algorithm","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1967","folder":"IETF/RFC-1967","source":"IETF/RFC-1967/RFC-1967.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null}],"search_text":"IETF RFC 1974 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Stac LZS data compression\n algorithm, with single or multiple compression histories, for\n compressing PPP encapsulated packets. 1974 algorithm license nested-reference unchanged"},{"id":"IETF RFC 2023","type":"specification","body":"IETF","designation":"RFC 2023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2023.txt","https://www.rfc-editor.org/rfc/rfc2023.pdf"],"folder":"IETF/RFC-2023","files":{"txt":{"path":"standards/IETF/RFC-2023/RFC-2023.txt","sha256":"a17df594f4d05d0eb38225c17762baaf042abd8637bf8d81008c155c296203e1"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for transmission of IP Version 6 [2]\n packets over PPP links as well as the Network Control Protocol (NCP)\n for establishing and configuring the IPv6 over PPP. It also specifies\n the method of forming IPv6 link-local addresses on PPP links.","scope_keywords":["2023","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2509","folder":"IETF/RFC-2509","source":"IETF/RFC-2509/RFC-2509.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null}],"search_text":"IETF RFC 2023 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for transmission of IP Version 6 [2]\n packets over PPP links as well as the Network Control Protocol (NCP)\n for establishing and configuring the IPv6 over PPP. It also specifies\n the method of forming IPv6 link-local addresses on PPP links. 2023 authentication nested-reference unchanged"},{"id":"IETF RFC 2118","type":"specification","body":"IETF","designation":"RFC 2118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2118.txt","https://www.rfc-editor.org/rfc/rfc2118.pdf"],"folder":"IETF/RFC-2118","files":{"txt":{"path":"standards/IETF/RFC-2118/RFC-2118.txt","sha256":"1a1bfeee7fb71d43b7e4d2cc224319658243da9fe93252822c6a0fff7e01d52a"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Microsoft Point to Point\n Compression protocol (also referred to as MPPC in this document) for\n compressing PPP encapsulated packets.","scope_keywords":["2118","algorithm","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null}],"search_text":"IETF RFC 2118 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol [2] provides a method to\n negotiate and utilize compression protocols over PPP encapsulated\n links.\n\n This document describes the use of the Microsoft Point to Point\n Compression protocol (also referred to as MPPC in this document) for\n compressing PPP encapsulated packets. 2118 algorithm license nested-reference unchanged"},{"id":"IETF RFC 2125","type":"specification","body":"IETF","designation":"RFC 2125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2125.txt","https://www.rfc-editor.org/rfc/rfc2125.pdf"],"folder":"IETF/RFC-2125","files":{"txt":{"path":"standards/IETF/RFC-2125/RFC-2125.txt","sha256":"cde2b98ba4c38b5676960902247bd86f7f2d0c035d5bfbbd8b361fa131070a82"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method to manage the dynamic bandwidth\n allocation of implementations supporting the PPP multilink protocol\n [2]. This is done by defining the Bandwidth Allocation Protocol\n (BAP), as well as its associated control protocol, the Bandwidth\n Allocation Control Protocol (BACP). BAP can be used to manage the\n number of links in a multilink bundle. BAP defines datagrams to co-\n ordinate adding and removing individual links in a multilink bundle,\n as well as specifying which peer is responsible for which decisions\n regarding managing bandwidth during a multilink connection.","scope_keywords":["2125","conformity","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2125 This document proposes a method to manage the dynamic bandwidth\n allocation of implementations supporting the PPP multilink protocol\n [2]. This is done by defining the Bandwidth Allocation Protocol\n (BAP), as well as its associated control protocol, the Bandwidth\n Allocation Control Protocol (BACP). BAP can be used to manage the\n number of links in a multilink bundle. BAP defines datagrams to co-\n ordinate adding and removing individual links in a multilink bundle,\n as well as specifying which peer is responsible for which decisions\n regarding managing bandwidth during a multilink connection. 2125 conformity management nested-reference unchanged"},{"id":"IETF RFC 2284","type":"specification","body":"IETF","designation":"RFC 2284","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2284.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2284.txt","https://www.rfc-editor.org/rfc/rfc2284.pdf"],"folder":"IETF/RFC-2284","files":{"txt":{"path":"standards/IETF/RFC-2284/RFC-2284.txt","sha256":"40674deafab633903d2f3b71acce3fd8bbdc8a3c9b80dbeb2f2bda186eee6eb2"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n This document defines the PPP Extensible Authentication Protocol.","scope_keywords":["2284","authentication","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2809","folder":"IETF/RFC-2809","source":"IETF/RFC-2809/RFC-2809.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3374","folder":"IETF/RFC-3374","source":"IETF/RFC-3374/RFC-3374.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 2284 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of an Authentication Protocol for authenticating its peer\n before allowing Network Layer protocols to transmit over the link.\n\n This document defines the PPP Extensible Authentication Protocol. 2284 authentication identification key nested-reference unchanged"},{"id":"IETF RFC 2420","type":"specification","body":"IETF","designation":"RFC 2420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2420.txt","https://www.rfc-editor.org/rfc/rfc2420.pdf"],"folder":"IETF/RFC-2420","files":{"txt":{"path":"standards/IETF/RFC-2420/RFC-2420.txt","sha256":"029e987e357ab661a33f76ef9b61350e89944761b23d3a7ac3bf12c867050707"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the Triple-DES\n standard (3DES) [6] for encrypting PPP encapsulated packets.","scope_keywords":["2420","algorithm","algorithms","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null}],"search_text":"IETF RFC 2420 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Encryption Control Protocol (ECP) [2] provides a method to\n negotiate and utilize encryption protocols over PPP encapsulated\n links.\n\n This document provides specific details for the use of the Triple-DES\n standard (3DES) [6] for encrypting PPP encapsulated packets. 2420 algorithm algorithms encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2460","type":"specification","body":"IETF","designation":"RFC 2460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2460.txt","https://www.rfc-editor.org/rfc/rfc2460.pdf"],"folder":"IETF/RFC-2460","files":{"txt":{"path":"standards/IETF/RFC-2460/RFC-2460.txt","sha256":"e48b421dc2635deef363c91af689576c707abd4ffb1be20ff26c00f785f909f2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 6 of the Internet Protocol (IPv6),\n also sometimes referred to as IP Next Generation or IPng.","scope_keywords":["2460","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 2466","folder":"IETF/RFC-2466","source":"IETF/RFC-2466/RFC-2466.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2526","folder":"IETF/RFC-2526","source":"IETF/RFC-2526/RFC-2526.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2711","folder":"IETF/RFC-2711","source":"IETF/RFC-2711/RFC-2711.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3089","folder":"IETF/RFC-3089","source":"IETF/RFC-3089/RFC-3089.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3221","folder":"IETF/RFC-3221","source":"IETF/RFC-3221/RFC-3221.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 3513","folder":"IETF/RFC-3513","source":"IETF/RFC-3513/RFC-3513.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3542","folder":"IETF/RFC-3542","source":"IETF/RFC-3542/RFC-3542.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3587","folder":"IETF/RFC-3587","source":"IETF/RFC-3587/RFC-3587.txt","version":null},{"body":"IETF","designation":"RFC 3595","folder":"IETF/RFC-3595","source":"IETF/RFC-3595/RFC-3595.txt","version":null},{"body":"IETF","designation":"RFC 3633","folder":"IETF/RFC-3633","source":"IETF/RFC-3633/RFC-3633.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3736","folder":"IETF/RFC-3736","source":"IETF/RFC-3736/RFC-3736.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 3769","folder":"IETF/RFC-3769","source":"IETF/RFC-3769/RFC-3769.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3843","folder":"IETF/RFC-3843","source":"IETF/RFC-3843/RFC-3843.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3901","folder":"IETF/RFC-3901","source":"IETF/RFC-3901/RFC-3901.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5722","folder":"IETF/RFC-5722","source":"IETF/RFC-5722/RFC-5722.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5871","folder":"IETF/RFC-5871","source":"IETF/RFC-5871/RFC-5871.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6540","folder":"IETF/RFC-6540","source":"IETF/RFC-6540/RFC-6540.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6564","folder":"IETF/RFC-6564","source":"IETF/RFC-6564/RFC-6564.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7872","folder":"IETF/RFC-7872","source":"IETF/RFC-7872/RFC-7872.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 2460 This document specifies version 6 of the Internet Protocol (IPv6),\n also sometimes referred to as IP Next Generation or IPng. 2460 authentication path nested-reference unchanged"},{"id":"IETF RFC 2472","type":"specification","body":"IETF","designation":"RFC 2472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2472.txt","https://www.rfc-editor.org/rfc/rfc2472.pdf"],"folder":"IETF/RFC-2472","files":{"txt":{"path":"standards/IETF/RFC-2472/RFC-2472.txt","sha256":"ffd8f86a9e4d24e2d0f27e2149e7482936551e1accfec85f6030d2e7b8f9fffd"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for transmission of IP Version 6 [2]\n packets over PPP links as well as the Network Control Protocol (NCP)\n for establishing and configuring the IPv6 over PPP. It also specifies\n the method of forming IPv6 link-local addresses on PPP links.","scope_keywords":["2472","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null}],"search_text":"IETF RFC 2472 The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines the method for transmission of IP Version 6 [2]\n packets over PPP links as well as the Network Control Protocol (NCP)\n for establishing and configuring the IPv6 over PPP. It also specifies\n the method of forming IPv6 link-local addresses on PPP links. 2472 authentication key nested-reference unchanged"},{"id":"IETF RFC 2516","type":"specification","body":"IETF","designation":"RFC 2516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2516.txt","https://www.rfc-editor.org/rfc/rfc2516.pdf"],"folder":"IETF/RFC-2516","files":{"txt":{"path":"standards/IETF/RFC-2516/RFC-2516.txt","sha256":"e20efb2fd445e50a076e3873daa7fb1b698bc1fc387902bd690c7a38afe77b95"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes how to build PPP sessions and encapsulate PPP\n packets over Ethernet.\n\nApplicability\n\n This specification is intended to provide the facilities which are\n defined for PPP, such as the Link Control Protocol, Network-layer\n Control Protocols, authentication, and more. These capabilities\n require a point-to-point relationship between the peers, and are not\n designed for the multi-point relationships which are available in\n Ethernet and other multi-access environments.\n\n This specification can be used by multiple hosts on a shared,\n Ethernet to open PPP sessions to multiple destinations via one or\n more bridging modems. It is intended to be used with broadband\n remote access technologies that provide a bridged Ethernet topology,\n whe","scope_keywords":["2516","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"IETF RFC 2516 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes how to build PPP sessions and encapsulate PPP\n packets over Ethernet.\n\nApplicability\n\n This specification is intended to provide the facilities which are\n defined for PPP, such as the Link Control Protocol, Network-layer\n Control Protocols, authentication, and more. These capabilities\n require a point-to-point relationship between the peers, and are not\n designed for the multi-point relationships which are available in\n Ethernet and other multi-access environments.\n\n This specification can be used by multiple hosts on a shared,\n Ethernet to open PPP sessions to multiple destinations via one or\n more bridging modems. It is intended to be used with broadband\n remote access technologies that provide a bridged Ethernet topology,\n whe 2516 authentication key nested-reference unchanged"},{"id":"IETF RFC 2686","type":"specification","body":"IETF","designation":"RFC 2686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2686.txt","https://www.rfc-editor.org/rfc/rfc2686.pdf"],"folder":"IETF/RFC-2686","files":{"txt":{"path":"standards/IETF/RFC-2686/RFC-2686.txt","sha256":"eb4115bb6c5546a5c95a90dd9062dcf521727b5f2082c1b3d1d5ff0bc62a11f4"}},"tags":["nested-reference","unchanged"],"summary":"A companion document describes an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1]. The main components of the\n architecture are: a real-time encapsulation format for asynchronous\n and synchronous low-bitrate links, a header compression architecture\n optimized for real-time flows, elements of negotiation protocols used\n between routers (or between hosts and routers), and announcement\n protocols used by applications to allow this negotiation to take\n place.\n\n This document proposes the fragment-oriented solution for the real-\n time encapsulation format part of the architecture. The general\n approach is to start from the PPP Multilink fragmentation protocol\n [2] and provide a small number of extensions to add functionality and\n reduce the overhead.\n\n1. Introduction\n\n As an extension to the \"best-effort\" serv","scope_keywords":["2686","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"IETF RFC 2686 A companion document describes an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1]. The main components of the\n architecture are: a real-time encapsulation format for asynchronous\n and synchronous low-bitrate links, a header compression architecture\n optimized for real-time flows, elements of negotiation protocols used\n between routers (or between hosts and routers), and announcement\n protocols used by applications to allow this negotiation to take\n place.\n\n This document proposes the fragment-oriented solution for the real-\n time encapsulation format part of the architecture. The general\n approach is to start from the PPP Multilink fragmentation protocol\n [2] and provide a small number of extensions to add functionality and\n reduce the overhead.\n\n1. Introduction\n\n As an extension to the \"best-effort\" serv 2686 key pid nested-reference unchanged"},{"id":"IETF RFC 2687","type":"specification","body":"IETF","designation":"RFC 2687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2687.txt","https://www.rfc-editor.org/rfc/rfc2687.pdf"],"folder":"IETF/RFC-2687","files":{"txt":{"path":"standards/IETF/RFC-2687/RFC-2687.txt","sha256":"3050fbbc69041cd0866b95b3a29e966284ffd9ebf28fe43aa65357df88b1899d"}},"tags":["nested-reference","unchanged"],"summary":"A companion document describes an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1]. The main components of the\n architecture are: a real-time encapsulation format for asynchronous\n and synchronous low-bitrate links, a header compression architecture\n optimized for real-time flows, elements of negotiation protocols used\n between routers (or between hosts and routers), and announcement\n protocols used by applications to allow this negotiation to take\n place.\n\n This document proposes the suspend/resume-oriented solution for the\n real-time encapsulation format part of the architecture. The general\n approach is to start from the PPP Multilink fragmentation protocol\n [2] and its multi-class extension [5] and add suspend/resume in a way\n that is as compatible to existing hard- and firmware as possible.\n\n1. Introd","scope_keywords":["2687","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"IETF RFC 2687 A companion document describes an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1]. The main components of the\n architecture are: a real-time encapsulation format for asynchronous\n and synchronous low-bitrate links, a header compression architecture\n optimized for real-time flows, elements of negotiation protocols used\n between routers (or between hosts and routers), and announcement\n protocols used by applications to allow this negotiation to take\n place.\n\n This document proposes the suspend/resume-oriented solution for the\n real-time encapsulation format part of the architecture. The general\n approach is to start from the PPP Multilink fragmentation protocol\n [2] and its multi-class extension [5] and add suspend/resume in a way\n that is as compatible to existing hard- and firmware as possible.\n\n1. Introd 2687 key nested-reference unchanged"},{"id":"IETF RFC 2809","type":"specification","body":"IETF","designation":"RFC 2809","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2809.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2809.txt","https://www.rfc-editor.org/rfc/rfc2809.pdf"],"folder":"IETF/RFC-2809","files":{"txt":{"path":"standards/IETF/RFC-2809/RFC-2809.txt","sha256":"02055c8cd92a04ff78aaa794dc6f8f36e0a21e6b9e07d7eaa20982f5b470771a"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses implementation issues arising in the\n provisioning of compulsory tunneling in dial-up networks using the\n L2TP protocol. This provisioning can be accomplished via the\n integration of RADIUS and tunneling protocols. Implementation issues\n encountered with other tunneling protocols are left to separate\n documents.\n\n1. Terminology\n\n Voluntary Tunneling\n In voluntary tunneling, a tunnel is created by the user,\n typically via use of a tunneling client.\n\n Compulsory Tunneling\n In compulsory tunneling, a tunnel is created without any\n action from the user and without allowing the user any\n choice.\n\n Tunnel Network Server\n This is a server which terminates a tunnel. In L2TP\n terminology, this is known as the L2TP Network Server\n (LNS).\n\nAboba & Zorn Informational [Page 1]\n\f\nRFC 2809 L2TP Compulsory Tunneling via RADIUS April 2000\n\n Network Access Server\n The Network Acces","scope_keywords":["2809","attribute","attributes","authentication","authorization","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null}],"search_text":"IETF RFC 2809 This document discusses implementation issues arising in the\n provisioning of compulsory tunneling in dial-up networks using the\n L2TP protocol. This provisioning can be accomplished via the\n integration of RADIUS and tunneling protocols. Implementation issues\n encountered with other tunneling protocols are left to separate\n documents.\n\n1. Terminology\n\n Voluntary Tunneling\n In voluntary tunneling, a tunnel is created by the user,\n typically via use of a tunneling client.\n\n Compulsory Tunneling\n In compulsory tunneling, a tunnel is created without any\n action from the user and without allowing the user any\n choice.\n\n Tunnel Network Server\n This is a server which terminates a tunnel. In L2TP\n terminology, this is known as the L2TP Network Server\n (LNS).\n\nAboba & Zorn Informational [Page 1]\n\f\nRFC 2809 L2TP Compulsory Tunneling via RADIUS April 2000\n\n Network Access Server\n The Network Acces 2809 attribute attributes authentication authorization key management trust nested-reference unchanged"},{"id":"IETF RFC 2871","type":"specification","body":"IETF","designation":"RFC 2871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2871.txt","https://www.rfc-editor.org/rfc/rfc2871.pdf"],"folder":"IETF/RFC-2871","files":{"txt":{"path":"standards/IETF/RFC-2871/RFC-2871.txt","sha256":"d03d690d0fb8924651f18858b5486d0846f16de5686d23a4fa0df9d52826db82"}},"tags":["nested-reference","unchanged"],"summary":"This document serves as a framework for Telephony Routing over IP\n (TRIP), which supports the discovery and exchange of IP telephony\n gateway routing tables between providers. The document defines the\n problem of telephony routing exchange, and motivates the need for the\n protocol. It presents an architectural framework for TRIP, defines\n terminology, specifies the various protocol elements and their\n functions, overviews the services provided by the protocol, and\n discusses how it fits into the broader context of Internet telephony.","scope_keywords":["2871","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null}],"search_text":"IETF RFC 2871 This document serves as a framework for Telephony Routing over IP\n (TRIP), which supports the discovery and exchange of IP telephony\n gateway routing tables between providers. The document defines the\n problem of telephony routing exchange, and motivates the need for the\n protocol. It presents an architectural framework for TRIP, defines\n terminology, specifies the various protocol elements and their\n functions, overviews the services provided by the protocol, and\n discusses how it fits into the broader context of Internet telephony. 2871 policy nested-reference unchanged"},{"id":"IETF RFC 2886","type":"specification","body":"IETF","designation":"RFC 2886","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2886.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2886.txt","https://www.rfc-editor.org/rfc/rfc2886.pdf"],"folder":"IETF/RFC-2886","files":{"txt":{"path":"standards/IETF/RFC-2886/RFC-2886.txt","sha256":"74943d9f3518c42037d19bc89172e8a1c06037f313af5cacfb06ffabf687b38f"}},"tags":["nested-reference","unchanged"],"summary":"This document records the errors found in the Megaco/H.248 protocol\n document [2], along with the changes proposed in the text of that\n document to resolve them.\n\n2. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [1].\n\n3. Errata\n\n All section numbers are those of the relevant text of [2].\n\n Section: 2 \"References\"\n ----------\n Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661\n (PPP).\n\n Editorial: delete unused reference to Q.724.\n\n Editorial: Leave Recommendations referred to in Annex C undated,\n implying latest issue.\n\n Editorial: add reference to RFC 2805, the Megaco requirements\n document.\n\nTaylor Standards Track [Page 1]\n\f\nRFC 2886 Megaco Errata August 2000\n\n Section: 4 \"Abbreviations\"\n -","scope_keywords":["2886","audit","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null}],"search_text":"IETF RFC 2886 This document records the errors found in the Megaco/H.248 protocol\n document [2], along with the changes proposed in the text of that\n document to resolve them.\n\n2. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [1].\n\n3. Errata\n\n All section numbers are those of the relevant text of [2].\n\n Section: 2 \"References\"\n ----------\n Editorial: Add missing references to I.363.5 (AAL5) and RFC 1661\n (PPP).\n\n Editorial: delete unused reference to Q.724.\n\n Editorial: Leave Recommendations referred to in Annex C undated,\n implying latest issue.\n\n Editorial: add reference to RFC 2805, the Megaco requirements\n document.\n\nTaylor Standards Track [Page 1]\n\f\nRFC 2886 Megaco Errata August 2000\n\n Section: 4 \"Abbreviations\"\n - 2886 audit key nested-reference unchanged"},{"id":"IETF RFC 2983","type":"specification","body":"IETF","designation":"RFC 2983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2983.txt","https://www.rfc-editor.org/rfc/rfc2983.pdf"],"folder":"IETF/RFC-2983","files":{"txt":{"path":"standards/IETF/RFC-2983/RFC-2983.txt","sha256":"8d0c7b459483f01877317fc5e4202aa9a837d140ce09a2d81ac6e453fdd9fbdd"}},"tags":["nested-reference","unchanged"],"summary":"This document considers the interaction of Differentiated Services\n (diffserv) (RFC 2474, RFC 2475) with IP tunnels of various forms.\n The discussion of tunnels in the diffserv architecture (RFC 2475)\n provides insufficient guidance to tunnel designers and implementers.\n This document describes two conceptual models for the interaction of\n diffserv with Internet Protocol (IP) tunnels and employs them to\n explore the resulting configurations and combinations of\n functionality. An important consideration is how and where it is\n appropriate to perform diffserv traffic conditioning in the presence\n of tunnel encapsulation and decapsulation. A few simple mechanisms\n are also proposed that limit the complexity that tunnels would\n otherwise add to the diffserv traffic conditioning model. Security\n considerations for IPSec tunnels limit the possible functionality in\n some circumstances.\n\n1. Conv","scope_keywords":["2983","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 2983 This document considers the interaction of Differentiated Services\n (diffserv) (RFC 2474, RFC 2475) with IP tunnels of various forms.\n The discussion of tunnels in the diffserv architecture (RFC 2475)\n provides insufficient guidance to tunnel designers and implementers.\n This document describes two conceptual models for the interaction of\n diffserv with Internet Protocol (IP) tunnels and employs them to\n explore the resulting configurations and combinations of\n functionality. An important consideration is how and where it is\n appropriate to perform diffserv traffic conditioning in the presence\n of tunnel encapsulation and decapsulation. A few simple mechanisms\n are also proposed that limit the complexity that tunnels would\n otherwise add to the diffserv traffic conditioning model. Security\n considerations for IPSec tunnels limit the possible functionality in\n some circumstances.\n\n1. Conv 2983 management path nested-reference unchanged"},{"id":"IETF RFC 3079","type":"specification","body":"IETF","designation":"RFC 3079","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3079.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3079.txt","https://www.rfc-editor.org/rfc/rfc3079.pdf"],"folder":"IETF/RFC-3079","files":{"txt":{"path":"standards/IETF/RFC-3079/RFC-3079.txt","sha256":"9b3e8f03e9e09b49187ec61d644c8e3d2a7cdbf28bbaf9f7ccb710b79c9243f2"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol provides a method to negotiate\n and utilize compression protocols over PPP encapsulated links.\n\n Microsoft Point to Point Encryption (MPPE) is a means of representing\n PPP packets in an encrypted form. MPPE uses the RSA RC4 algorithm to\n provide data confidentiality. The length of the session key to be\n used for initializing encryption tables can be negotiated. MPPE\n currently supports 40-bit, 56-bit and 128-bit session keys. MPPE\n session keys are changed frequently; the exact frequency depends upon\n the options negotiated, but may be every packet. MPPE is negotiated\n within option 18 in the Compression Control Protocol.\n\n This document describes the method used to derive initial MPPE\n session keys from a variety of cre","scope_keywords":["3079","algorithm","algorithms","authentication","credential","credentials","encryption","hash","hashing","key","keys","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null}],"search_text":"IETF RFC 3079 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n The PPP Compression Control Protocol provides a method to negotiate\n and utilize compression protocols over PPP encapsulated links.\n\n Microsoft Point to Point Encryption (MPPE) is a means of representing\n PPP packets in an encrypted form. MPPE uses the RSA RC4 algorithm to\n provide data confidentiality. The length of the session key to be\n used for initializing encryption tables can be negotiated. MPPE\n currently supports 40-bit, 56-bit and 128-bit session keys. MPPE\n session keys are changed frequently; the exact frequency depends upon\n the options negotiated, but may be every packet. MPPE is negotiated\n within option 18 in the Compression Control Protocol.\n\n This document describes the method used to derive initial MPPE\n session keys from a variety of cre 3079 algorithm algorithms authentication credential credentials encryption hash hashing key keys tls nested-reference unchanged"},{"id":"IETF RFC 3308","type":"specification","body":"IETF","designation":"RFC 3308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3308.txt","https://www.rfc-editor.org/rfc/rfc3308.pdf"],"folder":"IETF/RFC-3308","files":{"txt":{"path":"standards/IETF/RFC-3308/RFC-3308.txt","sha256":"a37895ab79988d29156938d6b093b239cf59de853fb67b403216406453bd06cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes mechanisms which enable the Layer Two\n Tunneling Protocol (L2TP) to negotiate desired Per Hop Behavior (PHB)\n code for the L2TP control connection, as well as individual sessions\n within an L2TP tunnel.\n\n L2TP provides a standard method for tunneling PPP packets. The\n current specification provides no provisions for supporting\n Differentiated Services (diffserv) over the L2TP control connection\n or subsequent data sessions. As a result, no standard mechanism\n currently exists within L2TP to provide L2TP protocol negotiations\n for service discrimination.\n\nCalhoun, et. al. Standards Track [Page 1]\n\f\nRFC 3308 L2TP Diffserv Extension November 2002","scope_keywords":["3308","attribute","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null}],"search_text":"IETF RFC 3308 This document describes mechanisms which enable the Layer Two\n Tunneling Protocol (L2TP) to negotiate desired Per Hop Behavior (PHB)\n code for the L2TP control connection, as well as individual sessions\n within an L2TP tunnel.\n\n L2TP provides a standard method for tunneling PPP packets. The\n current specification provides no provisions for supporting\n Differentiated Services (diffserv) over the L2TP control connection\n or subsequent data sessions. As a result, no standard mechanism\n currently exists within L2TP to provide L2TP protocol negotiations\n for service discrimination.\n\nCalhoun, et. al. Standards Track [Page 1]\n\f\nRFC 3308 L2TP Diffserv Extension November 2002 3308 attribute key policy nested-reference unchanged"},{"id":"IETF RFC 3314","type":"specification","body":"IETF","designation":"RFC 3314","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3314.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3314.txt","https://www.rfc-editor.org/rfc/rfc3314.pdf"],"folder":"IETF/RFC-3314","files":{"txt":{"path":"standards/IETF/RFC-3314/RFC-3314.txt","sha256":"36121a73f27c7c9963fdf567f12df29923be85ca593b84fac853c57f1ee3eb8b"}},"tags":["nested-reference","unchanged"],"summary":"This document contains recommendations from the Internet Engineering\n Task Force (IETF) IPv6 Working Group to the Third Generation\n Partnership Project (3GPP) community regarding the use of IPv6 in the\n 3GPP standards. Specifically, this document recommends that the 3GPP\n specify that multiple prefixes may be assigned to each primary PDP\n context, require that a given prefix must not be assigned to more\n than one primary PDP context, and allow 3GPP nodes to use multiple\n identifiers within those prefixes, including randomly generated\n identifiers.\n\n The IPv6 Working Group supports the use of IPv6 within 3GPP and\n offers these recommendations in a spirit of open cooperation between\n the IPv6 Working Group and the 3GPP community. Since the original\n publication of this document as an Internet-Draft, the 3GPP has\n adopted the primary recommendations of this document.\n\nConventions Used In Th","scope_keywords":["3314","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3574","folder":"IETF/RFC-3574","source":"IETF/RFC-3574/RFC-3574.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 4968","folder":"IETF/RFC-4968","source":"IETF/RFC-4968/RFC-4968.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 3314 This document contains recommendations from the Internet Engineering\n Task Force (IETF) IPv6 Working Group to the Third Generation\n Partnership Project (3GPP) community regarding the use of IPv6 in the\n 3GPP standards. Specifically, this document recommends that the 3GPP\n specify that multiple prefixes may be assigned to each primary PDP\n context, require that a given prefix must not be assigned to more\n than one primary PDP context, and allow 3GPP nodes to use multiple\n identifiers within those prefixes, including randomly generated\n identifiers.\n\n The IPv6 Working Group supports the use of IPv6 within 3GPP and\n offers these recommendations in a spirit of open cooperation between\n the IPv6 Working Group and the 3GPP community. Since the original\n publication of this document as an Internet-Draft, the 3GPP has\n adopted the primary recommendations of this document.\n\nConventions Used In Th 3314 key nested-reference unchanged"},{"id":"IETF RFC 3336","type":"specification","body":"IETF","designation":"RFC 3336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3336.txt","https://www.rfc-editor.org/rfc/rfc3336.pdf"],"folder":"IETF/RFC-3336","files":{"txt":{"path":"standards/IETF/RFC-3336/RFC-3336.txt","sha256":"7ea012f2cb366c3adc178240ba80c02583f2e5e701be6b931b2ecbfcefeda606"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Adaptation Layer 2 (AAL2) for\n framing PPP encapsulated packets.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the facilities which are defined for PPP, such as the Link\n Control Protocol, Network-layer Control Protocols, authentication,\n and compression. These capabilities require a point-to-point\n relationship between the peers, and are not designed for the multi-\n point relationships which are available in ATM and other multi-access\n environments.\n\nThompson, et. al. Standards Track [Page 1]\n\f\nRFC 3336 PPP Over AAL2 December 2002\n\n1. Introduction\n\n PPP over AAL5 [2] describes the encapsulation format and operation of\n PPP when used with the ATM AAL5 adaptation layer. W","scope_keywords":["3336","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null}],"search_text":"IETF RFC 3336 The Point-to-Point Protocol (PPP) provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n This document describes the use of ATM Adaptation Layer 2 (AAL2) for\n framing PPP encapsulated packets.\n\nApplicability\n\n This specification is intended for those implementations which desire\n to use the facilities which are defined for PPP, such as the Link\n Control Protocol, Network-layer Control Protocols, authentication,\n and compression. These capabilities require a point-to-point\n relationship between the peers, and are not designed for the multi-\n point relationships which are available in ATM and other multi-access\n environments.\n\nThompson, et. al. Standards Track [Page 1]\n\f\nRFC 3336 PPP Over AAL2 December 2002\n\n1. Introduction\n\n PPP over AAL5 [2] describes the encapsulation format and operation of\n PPP when used with the ATM AAL5 adaptation layer. W 3336 authentication key management nested-reference unchanged"},{"id":"IETF RFC 3818","type":"specification","body":"IETF","designation":"RFC 3818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3818.txt","https://www.rfc-editor.org/rfc/rfc3818.pdf"],"folder":"IETF/RFC-3818","files":{"txt":{"path":"standards/IETF/RFC-3818/RFC-3818.txt","sha256":"64267bb4ae729a0a7a6f429b844ffa34c58f315d43f57b22136d8a2c90dcc28d"}},"tags":["nested-reference","unchanged"],"summary":"The charter of the Point-to-Point Protocol (PPP) Extensions working\n group (pppext) includes the responsibility to \"actively advance PPP's\n most useful extensions to full standard, while defending against\n further enhancements of questionable value.\" In support of that\n charter, the allocation of PPP protocol and other assigned numbers\n will no longer be \"first come first served.\"","scope_keywords":["3818","algorithm","algorithms","authentication","http","license","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null}],"search_text":"IETF RFC 3818 The charter of the Point-to-Point Protocol (PPP) Extensions working\n group (pppext) includes the responsibility to \"actively advance PPP's\n most useful extensions to full standard, while defending against\n further enhancements of questionable value.\" In support of that\n charter, the allocation of PPP protocol and other assigned numbers\n will no longer be \"first come first served.\" 3818 algorithm algorithms authentication http license policies policy subject nested-reference unchanged"},{"id":"IETF RFC 4618","type":"specification","body":"IETF","designation":"RFC 4618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4618.txt","https://www.rfc-editor.org/rfc/rfc4618.pdf"],"folder":"IETF/RFC-4618","files":{"txt":{"path":"standards/IETF/RFC-4618/RFC-4618.txt","sha256":"1d97970ee6e33fbb52d9f8246c1d1f494da1ace954909b9d0eb8a753e57aeb94"}},"tags":["nested-reference","unchanged"],"summary":"A pseudowire (PW) can be used to carry Point to Point Protocol (PPP)\n or High-Level Data Link Control (HDLC) Protocol Data Units over a\n Multiprotocol Label Switching (MPLS) network without terminating the\n PPP/HDLC protocol. This enables service providers to offer\n \"emulated\" HDLC, or PPP link services over existing MPLS networks.\n This document specifies the encapsulation of PPP/HDLC Packet Data\n Units (PDUs) within a pseudowire.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4618 Transport of PPP/HDLC over MPLS September 2006","scope_keywords":["4618","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null}],"search_text":"IETF RFC 4618 A pseudowire (PW) can be used to carry Point to Point Protocol (PPP)\n or High-Level Data Link Control (HDLC) Protocol Data Units over a\n Multiprotocol Label Switching (MPLS) network without terminating the\n PPP/HDLC protocol. This enables service providers to offer\n \"emulated\" HDLC, or PPP link services over existing MPLS networks.\n This document specifies the encapsulation of PPP/HDLC Packet Data\n Units (PDUs) within a pseudowire.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4618 Transport of PPP/HDLC over MPLS September 2006 4618 key nested-reference unchanged"},{"id":"IETF RFC 4705","type":"specification","body":"IETF","designation":"RFC 4705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4705.txt","https://www.rfc-editor.org/rfc/rfc4705.pdf"],"folder":"IETF/RFC-4705","files":{"txt":{"path":"standards/IETF/RFC-4705/RFC-4705.txt","sha256":"452aba97ff2f539a5f326113b7bc6938344b6528dfbf681d42ad3c41a524a9af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the encryption and key management used by\n GigaBeam as part of the WiFiber(tm) family of radio link products.\n The security solution is documented in the hope that other wireless\n product development efforts will include comparable capabilities.\n\nHousley & Corry Informational [Page 1]\n\f\nRFC 4705 GigaBeam Radio Link Encryption October 2006\n\n1. Introduction\n\n The GigaBeam WiFiber(tm) product family provides a high-speed point-\n to-point radio link. Data rates exceed 1 gigabit/second at a\n distance of about a mile. The transmission beam width is less than\n one degree, which means that attempts to intercept the signal are\n most successful when the attacker is either between the transmitter\n and receiver or the attacker is directly behind the receiver. Since\n interception is possible, some customers require confidentiality and\n integrity protection for the data on the ","scope_keywords":["4705","algorithm","algorithms","authentication","encryption","key","keys","management","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4705 This document describes the encryption and key management used by\n GigaBeam as part of the WiFiber(tm) family of radio link products.\n The security solution is documented in the hope that other wireless\n product development efforts will include comparable capabilities.\n\nHousley & Corry Informational [Page 1]\n\f\nRFC 4705 GigaBeam Radio Link Encryption October 2006\n\n1. Introduction\n\n The GigaBeam WiFiber(tm) product family provides a high-speed point-\n to-point radio link. Data rates exceed 1 gigabit/second at a\n distance of about a mile. The transmission beam width is less than\n one degree, which means that attempts to intercept the signal are\n most successful when the attacker is either between the transmitter\n and receiver or the attacker is directly behind the receiver. Since\n interception is possible, some customers require confidentiality and\n integrity protection for the data on the  4705 algorithm algorithms authentication encryption key keys management signature signatures nested-reference unchanged"},{"id":"IETF RFC 5281","type":"specification","body":"IETF","designation":"RFC 5281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5281.txt","https://www.rfc-editor.org/rfc/rfc5281.pdf"],"folder":"IETF/RFC-5281","files":{"txt":{"path":"standards/IETF/RFC-5281/RFC-5281.txt","sha256":"d0b28f490d96f21647936d3c4e681c504e602fb4d47d8ee761054903a5784afc"}},"tags":["nested-reference","unchanged"],"summary":"EAP-TTLS is an EAP (Extensible Authentication Protocol) method that\n encapsulates a TLS (Transport Layer Security) session, consisting of\n a handshake phase and a data phase. During the handshake phase, the\n server is authenticated to the client (or client and server are\n mutually authenticated) using standard TLS procedures, and keying\n material is generated in order to create a cryptographically secure\n tunnel for information exchange in the subsequent data phase. During\n the data phase, the client is authenticated to the server (or client\n and server are mutually authenticated) using an arbitrary\n authentication mechanism encapsulated within the secure tunnel. The\n encapsulated authentication mechanism may itself be EAP, or it may be\n another authentication protocol such as PAP, CHAP, MS-CHAP, or MS-\n CHAP-V2. Thus, EAP-TTLS allows legacy password-based authentication\n protocols to be","scope_keywords":["5281","authentication","certificate","key","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 5281 EAP-TTLS is an EAP (Extensible Authentication Protocol) method that\n encapsulates a TLS (Transport Layer Security) session, consisting of\n a handshake phase and a data phase. During the handshake phase, the\n server is authenticated to the client (or client and server are\n mutually authenticated) using standard TLS procedures, and keying\n material is generated in order to create a cryptographically secure\n tunnel for information exchange in the subsequent data phase. During\n the data phase, the client is authenticated to the server (or client\n and server are mutually authenticated) using an arbitrary\n authentication mechanism encapsulated within the secure tunnel. The\n encapsulated authentication mechanism may itself be EAP, or it may be\n another authentication protocol such as PAP, CHAP, MS-CHAP, or MS-\n CHAP-V2. Thus, EAP-TTLS allows legacy password-based authentication\n protocols to be 5281 authentication certificate key tls trust validation nested-reference unchanged"},{"id":"IETF RFC 5718","type":"specification","body":"IETF","designation":"RFC 5718","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5718.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5718.txt","https://www.rfc-editor.org/rfc/rfc5718.pdf"],"folder":"IETF/RFC-5718","files":{"txt":{"path":"standards/IETF/RFC-5718/RFC-5718.txt","sha256":"236c2338f61a14b5500ee9f1888c023b09b23dbba2822e02c713f3d4f1d45863"}},"tags":["nested-reference","unchanged"],"summary":"The Generic Associated Channel (G-ACh) has been defined as a\n generalization of the pseudowire (PW) associated control channel to\n enable the realization of a control/communication channel that is\n associated with Multiprotocol Label Switching (MPLS) Label Switched\n Paths (LSPs), MPLS PWs, MPLS LSP segments, and MPLS sections between\n adjacent MPLS-capable devices.\n\n The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS\n architecture that identifies elements of the MPLS toolkit that may be\n combined to build a carrier-grade packet transport network based on\n MPLS packet switching technology.\n\n This document describes how the G-ACh may be used to provide the\n infrastructure that forms part of the Management Communication\n Network (MCN) and a Signaling Communication Network (SCN).\n Collectively, the MCN and SCN may be referred to as the Data\n Communication Network (DCN). This docum","scope_keywords":["5718","delivery","http","license","management","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"IETF RFC 5718 The Generic Associated Channel (G-ACh) has been defined as a\n generalization of the pseudowire (PW) associated control channel to\n enable the realization of a control/communication channel that is\n associated with Multiprotocol Label Switching (MPLS) Label Switched\n Paths (LSPs), MPLS PWs, MPLS LSP segments, and MPLS sections between\n adjacent MPLS-capable devices.\n\n The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS\n architecture that identifies elements of the MPLS toolkit that may be\n combined to build a carrier-grade packet transport network based on\n MPLS packet switching technology.\n\n This document describes how the G-ACh may be used to provide the\n infrastructure that forms part of the Management Communication\n Network (MCN) and a Signaling Communication Network (SCN).\n Collectively, the MCN and SCN may be referred to as the Data\n Communication Network (DCN). This docum 5718 delivery http license management path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 6361","type":"specification","body":"IETF","designation":"RFC 6361","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6361.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6361.txt","https://www.rfc-editor.org/rfc/rfc6361.pdf"],"folder":"IETF/RFC-6361","files":{"txt":{"path":"standards/IETF/RFC-6361/RFC-6361.txt","sha256":"7873fb2ac299bb082e98577bdf691e893fe1f43c9e38194eb3f1154a9e07b953"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) defines a Link Control Protocol\n (LCP) and a method for negotiating the use of multiprotocol traffic\n over point-to-point links. This document describes PPP support for\n the Transparent Interconnection of Lots of Links (TRILL) Protocol,\n allowing direct communication between Routing Bridges (RBridges) via\n PPP links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o","scope_keywords":["6361","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 6361 The Point-to-Point Protocol (PPP) defines a Link Control Protocol\n (LCP) and a method for negotiating the use of multiprotocol traffic\n over point-to-point links. This document describes PPP support for\n the Transparent Interconnection of Lots of Links (TRILL) Protocol,\n allowing direct communication between Routing Bridges (RBridges) via\n PPP links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o 6361 http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6431","type":"specification","body":"IETF","designation":"RFC 6431","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6431.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6431.txt","https://www.rfc-editor.org/rfc/rfc6431.pdf"],"folder":"IETF/RFC-6431","files":{"txt":{"path":"standards/IETF/RFC-6431/RFC-6431.txt","sha256":"c1edb9fb2e78e2ca0df9cfda94b1c8fa8bc908edb787b8e10dc2fb8835c9802a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two Huawei IPCP (IP Control Protocol) options\n used to convey a set of ports. These options can be used in the\n context of port range-based solutions or NAT-based solutions for port\n delegation and forwarding purposes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc643","scope_keywords":["6431","http","https","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null}],"search_text":"IETF RFC 6431 This document defines two Huawei IPCP (IP Control Protocol) options\n used to convey a set of ports. These options can be used in the\n context of port range-based solutions or NAT-based solutions for port\n delegation and forwarding purposes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc643 6431 http https key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6619","type":"specification","body":"IETF","designation":"RFC 6619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6619.txt","https://www.rfc-editor.org/rfc/rfc6619.pdf"],"folder":"IETF/RFC-6619","files":{"txt":{"path":"standards/IETF/RFC-6619/RFC-6619.txt","sha256":"8c86ee5fdf2e465ad24dc4f5ba63da145718c6a3c374947cd6a775f851619a21"}},"tags":["nested-reference","unchanged"],"summary":"This document explains how to employ address translation in networks\n that serve a large number of individual customers without requiring a\n correspondingly large amount of private IPv4 address space.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6619.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docu","scope_keywords":["6619","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 6619 This document explains how to employ address translation in networks\n that serve a large number of individual customers without requiring a\n correspondingly large amount of private IPv4 address space.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6619.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docu 6619 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7066","type":"specification","body":"IETF","designation":"RFC 7066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7066.txt","https://www.rfc-editor.org/rfc/rfc7066.pdf"],"folder":"IETF/RFC-7066","files":{"txt":{"path":"standards/IETF/RFC-7066/RFC-7066.txt","sha256":"13210647d7dfba285bed43f6d8be24df9c37e4f66dc5a7e553cfb812400f3e3d"}},"tags":["nested-reference","unchanged"],"summary":"As the deployment of third and fourth generation cellular networks\n progresses, a large number of cellular hosts are being connected to\n the Internet. Standardization organizations have made the Internet\n Protocol version 6 (IPv6) mandatory in their specifications.\n However, the concept of IPv6 covers many aspects and numerous\n specifications. In addition, the characteristics of cellular links\n in terms of bandwidth, cost, and delay put special requirements on\n how IPv6 is used. This document considers IPv6 for cellular hosts\n that attach to the General Packet Radio Service (GPRS), Universal\n Mobile Telecommunications System (UMTS), or Evolved Packet System\n (EPS) networks (hereafter collectively referred to as Third\n Generation Partnership Project (3GPP) networks). This document also\n lists specific IPv6 functionalities that need to be implemented in\n addition to what is already prescri","scope_keywords":["7066","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null}],"search_text":"IETF RFC 7066 As the deployment of third and fourth generation cellular networks\n progresses, a large number of cellular hosts are being connected to\n the Internet. Standardization organizations have made the Internet\n Protocol version 6 (IPv6) mandatory in their specifications.\n However, the concept of IPv6 covers many aspects and numerous\n specifications. In addition, the characteristics of cellular links\n in terms of bandwidth, cost, and delay put special requirements on\n how IPv6 is used. This document considers IPv6 for cellular hosts\n that attach to the General Packet Radio Service (GPRS), Universal\n Mobile Telecommunications System (UMTS), or Evolved Packet System\n (EPS) networks (hereafter collectively referred to as Third\n Generation Partnership Project (3GPP) networks). This document also\n lists specific IPv6 functionalities that need to be implemented in\n addition to what is already prescri 7066 http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7173","type":"specification","body":"IETF","designation":"RFC 7173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7173.txt","https://www.rfc-editor.org/rfc/rfc7173.pdf"],"folder":"IETF/RFC-7173","files":{"txt":{"path":"standards/IETF/RFC-7173/RFC-7173.txt","sha256":"3409ffefaf2b34918ccbef82ee0eaad8cf32b66112a3ecd4e56e3d35c5958cc8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to interconnect a pair of Transparent\n Interconnection of Lots of Links (TRILL) switch ports using\n pseudowires under existing TRILL and Pseudowire Emulation End-to-End\n (PWE3) standards.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7173.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserv","scope_keywords":["7173","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null}],"search_text":"IETF RFC 7173 This document specifies how to interconnect a pair of Transparent\n Interconnection of Lots of Links (TRILL) switch ports using\n pseudowires under existing TRILL and Pseudowire Emulation End-to-End\n (PWE3) standards.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7173.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserv 7173 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 2171","type":"specification","body":"IETF","designation":"RFC 2171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2171.txt","https://www.rfc-editor.org/rfc/rfc2171.pdf"],"folder":"IETF/RFC-2171","files":{"txt":{"path":"standards/IETF/RFC-2171/RFC-2171.txt","sha256":"ac96ab79c0bf348b3c463cda554720228969ec5be30e3eee28eb6a1a385aefc8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the protocol MAPOS, Multiple Access Protocol\n over SONET/SDH, for transmitting network-protocol datagrams over\n SONET/SDH. It focuses on the core protocol -- other documents listed\n in the bibliography may be referenced in conjunction with this\n document to provide support and services for protocols at higher\n layers.\n\n1. Introduction","scope_keywords":["2171","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2174","folder":"IETF/RFC-2174","source":"IETF/RFC-2174/RFC-2174.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null}],"search_text":"IETF RFC 2171 This document describes the protocol MAPOS, Multiple Access Protocol\n over SONET/SDH, for transmitting network-protocol datagrams over\n SONET/SDH. It focuses on the core protocol -- other documents listed\n in the bibliography may be referenced in conjunction with this\n document to provide support and services for protocols at higher\n layers.\n\n1. Introduction 2171 path nested-reference unchanged"},{"id":"IETF RFC 2175","type":"specification","body":"IETF","designation":"RFC 2175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2175.txt","https://www.rfc-editor.org/rfc/rfc2175.pdf"],"folder":"IETF/RFC-2175","files":{"txt":{"path":"standards/IETF/RFC-2175/RFC-2175.txt","sha256":"d32f06d0b7f2ecd23dcfd0ff5a3ab126b0cff7a5daa7fb9cb43a963aa43a4fcd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the protocol MAPOS 16, Multiple Access\n Protocol over SONET/SDH with 16 Bit Addressing, for transmitting\n network-protocol datagrams over SONET/SDH. The primary difference\n with MAPOS version 1 is that it has 16 bit address field that offers\n significant wide address space. It first describes the major\n differences between MAPOS and MAPOS 16 briefly. Then, it explains the\n header format and its 16 bit address format.\n\n1. Introduction\n\n MAPOS is a multiple access protocol for transmission of High-level\n Datalink Control (HDLC) frames over the Synchronous Optical Network /\n Synchronous Digital Hierarchy(SONET/SDH)[1][2][3][4]. It provides\n multiple access capability to SONET/SDH, an inherently point-to-point\n link.\n\n MAPOS version 1[5] focuses on the frame format compatibility with the\n conventional PPP[6], resulting with its narrow 8 bit address field.\n In contrast","scope_keywords":["2175"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null}],"search_text":"IETF RFC 2175 This document describes the protocol MAPOS 16, Multiple Access\n Protocol over SONET/SDH with 16 Bit Addressing, for transmitting\n network-protocol datagrams over SONET/SDH. The primary difference\n with MAPOS version 1 is that it has 16 bit address field that offers\n significant wide address space. It first describes the major\n differences between MAPOS and MAPOS 16 briefly. Then, it explains the\n header format and its 16 bit address format.\n\n1. Introduction\n\n MAPOS is a multiple access protocol for transmission of High-level\n Datalink Control (HDLC) frames over the Synchronous Optical Network /\n Synchronous Digital Hierarchy(SONET/SDH)[1][2][3][4]. It provides\n multiple access capability to SONET/SDH, an inherently point-to-point\n link.\n\n MAPOS version 1[5] focuses on the frame format compatibility with the\n conventional PPP[6], resulting with its narrow 8 bit address field.\n In contrast 2175 nested-reference unchanged"},{"id":"IETF RFC 3320","type":"specification","body":"IETF","designation":"RFC 3320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3320.txt","https://www.rfc-editor.org/rfc/rfc3320.pdf"],"folder":"IETF/RFC-3320","files":{"txt":{"path":"standards/IETF/RFC-3320/RFC-3320.txt","sha256":"07ed39ec69c282780167ee289c691b1f97cbd6d963b9e452b37791dd3651b26b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Signaling Compression (SigComp), a solution for\n compressing messages generated by application protocols such as the\n Session Initiation Protocol (SIP) (RFC 3261) and the Real Time\n Streaming Protocol (RTSP) (RFC 2326). The architecture and\n prerequisites of SigComp are outlined, along with the format of the\n SigComp message.\n\n Decompression functionality for SigComp is provided by a Universal\n Decompressor Virtual Machine (UDVM) optimized for the task of running\n decompression algorithms. The UDVM can be configured to understand\n the output of many well-known compressors such as DEFLATE (RFC-1951).\n\nPrice, et. al. Standards Track [Page 1]\n\f\nRFC 3320 Signaling Compression (SigComp) January 2003","scope_keywords":["3320","algorithm","algorithms","key","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3321","folder":"IETF/RFC-3321","source":"IETF/RFC-3321/RFC-3321.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3486","folder":"IETF/RFC-3486","source":"IETF/RFC-3486/RFC-3486.txt","version":null},{"body":"IETF","designation":"RFC 4077","folder":"IETF/RFC-4077","source":"IETF/RFC-4077/RFC-4077.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null}],"search_text":"IETF RFC 3320 This document defines Signaling Compression (SigComp), a solution for\n compressing messages generated by application protocols such as the\n Session Initiation Protocol (SIP) (RFC 3261) and the Real Time\n Streaming Protocol (RTSP) (RFC 2326). The architecture and\n prerequisites of SigComp are outlined, along with the format of the\n SigComp message.\n\n Decompression functionality for SigComp is provided by a Universal\n Decompressor Virtual Machine (UDVM) optimized for the task of running\n decompression algorithms. The UDVM can be configured to understand\n the output of many well-known compressors such as DEFLATE (RFC-1951).\n\nPrice, et. al. Standards Track [Page 1]\n\f\nRFC 3320 Signaling Compression (SigComp) January 2003 3320 algorithm algorithms key tsp nested-reference unchanged"},{"id":"IETF RFC 3572","type":"specification","body":"IETF","designation":"RFC 3572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3572.txt","https://www.rfc-editor.org/rfc/rfc3572.pdf"],"folder":"IETF/RFC-3572","files":{"txt":{"path":"standards/IETF/RFC-3572/RFC-3572.txt","sha256":"dfd68fefeeb60cbe96361521b326917ae6a25ea3785e67203e3080fa987e61d7"}},"tags":["nested-reference","unchanged"],"summary":"Multiple Access Protocol over SONET/SDH (MAPOS) is a high-speed\n link-layer protocol that provides multiple access capability over a\n Synchronous Optical NETwork/Synchronous Digital Hierarchy\n (SONET/SDH).\n\n This document specifies the frame format for encapsulating an IPv6\n datagram in a MAPOS frame. It also specifies the method of forming\n IPv6 interface identifiers, the method of detecting duplicate\n addresses, and the format of the Source/Target Link-layer Addresses\n option field used in IPv6 Neighbor Discovery messages.\n\nOgura, et. al. Informational [Page 1]\n\f\nRFC 3572 IPv6 over MAPOS July 2003","scope_keywords":["3572","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 3572 Multiple Access Protocol over SONET/SDH (MAPOS) is a high-speed\n link-layer protocol that provides multiple access capability over a\n Synchronous Optical NETwork/Synchronous Digital Hierarchy\n (SONET/SDH).\n\n This document specifies the frame format for encapsulating an IPv6\n datagram in a MAPOS frame. It also specifies the method of forming\n IPv6 interface identifiers, the method of detecting duplicate\n addresses, and the format of the Source/Target Link-layer Addresses\n option field used in IPv6 Neighbor Discovery messages.\n\nOgura, et. al. Informational [Page 1]\n\f\nRFC 3572 IPv6 over MAPOS July 2003 3572 management nested-reference unchanged"},{"id":"IETF RFC 4207","type":"specification","body":"IETF","designation":"RFC 4207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4207.txt","https://www.rfc-editor.org/rfc/rfc4207.pdf"],"folder":"IETF/RFC-4207","files":{"txt":{"path":"standards/IETF/RFC-4207/RFC-4207.txt","sha256":"de2fb73032f2688c0e098e03b4901f3f66a074ce2221de936e1192a1016d834b"}},"tags":["nested-reference","unchanged"],"summary":"This document details the Synchronous Optical Network\n (SONET)/Synchronous Digital Hierarchy (SDH) technology-specific\n information needed when sending Link Management Protocol (LMP) test\n messages.\n\n1. Introduction\n\n For scalability purposes, multiple physical resources that\n interconnect Label Switching Routers (LSRs) can be combined to form a\n single traffic engineering (TE) link for the purposes of path\n computation and signaling. These resources may represent one or more\n physical links that connect the LSRs, or they may represent a Label\n Switched Path (LSP) if LSP hierarchy [RFC4206] is used. The\n management of TE links is not restricted to in-band messaging, but\n instead can be done using out-of-band techniques.\n\n The Link Management Protocol (LMP) [RFC4204] has been developed as\n part of the Generalized MPLS (GMPLS) protocol suite to manage TE\n links. LMP currently consists of f","scope_keywords":["4207","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null}],"search_text":"IETF RFC 4207 This document details the Synchronous Optical Network\n (SONET)/Synchronous Digital Hierarchy (SDH) technology-specific\n information needed when sending Link Management Protocol (LMP) test\n messages.\n\n1. Introduction\n\n For scalability purposes, multiple physical resources that\n interconnect Label Switching Routers (LSRs) can be combined to form a\n single traffic engineering (TE) link for the purposes of path\n computation and signaling. These resources may represent one or more\n physical links that connect the LSRs, or they may represent a Label\n Switched Path (LSP) if LSP hierarchy [RFC4206] is used. The\n management of TE links is not restricted to in-band messaging, but\n instead can be done using out-of-band techniques.\n\n The Link Management Protocol (LMP) [RFC4204] has been developed as\n part of the Generalized MPLS (GMPLS) protocol suite to manage TE\n links. LMP currently consists of f 4207 key management path nested-reference unchanged"},{"id":"IETF RFC 4815","type":"specification","body":"IETF","designation":"RFC 4815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4815.txt","https://www.rfc-editor.org/rfc/rfc4815.pdf"],"folder":"IETF/RFC-4815","files":{"txt":{"path":"standards/IETF/RFC-4815/RFC-4815.txt","sha256":"841240e06a7abb94d4b64e9de11aa71995dfe03b01646eb58e5f78bf63a839cd"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3095 defines the RObust Header Compression (ROHC) framework and\n profiles for IP (Internet Protocol), UDP (User Datagram Protocol),\n RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security\n Payload). Some parts of the specification are unclear or contain\n errors that may lead to misinterpretations that may impair\n interoperability between different implementations. This document\n provides corrections, additions, and clarifications to RFC 3095; this\n document thus updates RFC 3095. In addition, other clarifications\n related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and\n RFC 4109 (ROHC UDP-Lite profiles) are also provided.\n\nJonsson, et al. Standards Track [Page 1]\n\f\nRFC 4815 Corrections and Clarifications to RFC 3095 February 2007","scope_keywords":["4815","algorithm","key","management","profile","profiles","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 4815 RFC 3095 defines the RObust Header Compression (ROHC) framework and\n profiles for IP (Internet Protocol), UDP (User Datagram Protocol),\n RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security\n Payload). Some parts of the specification are unclear or contain\n errors that may lead to misinterpretations that may impair\n interoperability between different implementations. This document\n provides corrections, additions, and clarifications to RFC 3095; this\n document thus updates RFC 3095. In addition, other clarifications\n related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and\n RFC 4109 (ROHC UDP-Lite profiles) are also provided.\n\nJonsson, et al. Standards Track [Page 1]\n\f\nRFC 4815 Corrections and Clarifications to RFC 3095 February 2007 4815 algorithm key management profile profiles timestamp trust nested-reference unchanged"},{"id":"IETF RFC 1666","type":"specification","body":"IETF","designation":"RFC 1666","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1666.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1666.txt","https://www.rfc-editor.org/rfc/rfc1666.pdf"],"folder":"IETF/RFC-1666","files":{"txt":{"path":"standards/IETF/RFC-1666/RFC-1666.txt","sha256":"e7f971a7b755cd030559703d08400f6927a46e55a5624beef94962ddcb36500b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Z. Kielczewski\nRequest for Comments: 1666 Eicon Technology Corporation\nObsoletes: 1665 D. Kostick\nCategory: Standards Track Bell Communications Research\n K. Shih\n Novell\n Editors\n August 1994\n\n Definitions of Managed Objects\n for SNA NAUs using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 2\n 3. Overview ...........................","scope_keywords":["1666","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1666 Network Working Group Z. Kielczewski\nRequest for Comments: 1666 Eicon Technology Corporation\nObsoletes: 1665 D. Kostick\nCategory: Standards Track Bell Communications Research\n K. Shih\n Novell\n Editors\n August 1994\n\n Definitions of Managed Objects\n for SNA NAUs using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ................................................ 2\n 2. The SNMPv2 Network Management Framework ..................... 2\n 2.1 Object Definitions ......................................... 2\n 3. Overview ........................... 1666 management timestamp nested-reference unchanged"},{"id":"IETF RFC 5211","type":"specification","body":"IETF","designation":"RFC 5211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5211.txt","https://www.rfc-editor.org/rfc/rfc5211.pdf"],"folder":"IETF/RFC-5211","files":{"txt":{"path":"standards/IETF/RFC-5211/RFC-5211.txt","sha256":"62d71edf048211dead87974e2938de5ac39d49ed9a994cfa4d4c334c569abd0e"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides one possible plan for transitioning the Internet\n from a predominantly IPv4-based connectivity model to a predominantly\n IPv6-based connectivity model.","scope_keywords":["5211","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null}],"search_text":"IETF RFC 5211 This memo provides one possible plan for transitioning the Internet\n from a predominantly IPv4-based connectivity model to a predominantly\n IPv6-based connectivity model. 5211 key risk nested-reference unchanged"},{"id":"IETF RFC 167","type":"specification","body":"IETF","designation":"RFC 167","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc167.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc167.txt","https://www.rfc-editor.org/rfc/rfc167.pdf"],"folder":"IETF/RFC-167","files":{"txt":{"path":"standards/IETF/RFC-167/RFC-167.txt","sha256":"e63f286c90fccc598a210bc84ace1a1aa8fab596b9685311230f7125ed0b8424"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\n Request for Comment #167\n NIC #6784\n\n Socket Conventions Reconsidered\n\n Athay Bhushan (MAC)\n Bob Metcalfe (Harvard)\n Joel Winett (LL)\n\n 24 May 1971\n\n Category: C1, C3, C8\n Related RFCs: #147, #129\n Related Functional Documents: #1\n\n [Page 1]\n\f\nRFC 167 Socket Conventions Reconsidered\n\nThe current NCP Protocol says nothing about how hosts should assign\nsocket numbers to process ports, except that the low-order bit is to\nspecify socket gender (i.e., send or receive). Two recent proposals call\nfor additional network-wide conventions on the 32-bit socket-number. The\nfirst proposal asks that a portion of the socket number be reserved for\na network-unique user number for accounting and access control. The\nsecond proposal asks that the high-order 16 bits of the socket number be\nzero to assist smaller hosts in reducing the space required for socket\nnumber tables.\n\nIt is rec","scope_keywords":["167","algorithm","algorithms","attribute","attributes","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 167 Network Working Group\n Request for Comment #167\n NIC #6784\n\n Socket Conventions Reconsidered\n\n Athay Bhushan (MAC)\n Bob Metcalfe (Harvard)\n Joel Winett (LL)\n\n 24 May 1971\n\n Category: C1, C3, C8\n Related RFCs: #147, #129\n Related Functional Documents: #1\n\n [Page 1]\n\f\nRFC 167 Socket Conventions Reconsidered\n\nThe current NCP Protocol says nothing about how hosts should assign\nsocket numbers to process ports, except that the low-order bit is to\nspecify socket gender (i.e., send or receive). Two recent proposals call\nfor additional network-wide conventions on the 32-bit socket-number. The\nfirst proposal asks that a portion of the socket number be reserved for\na network-unique user number for accounting and access control. The\nsecond proposal asks that the high-order 16 bits of the socket number be\nzero to assist smaller hosts in reducing the space required for socket\nnumber tables.\n\nIt is rec 167 algorithm algorithms attribute attributes identification subject nested-reference unchanged"},{"id":"IETF RFC 6555","type":"specification","body":"IETF","designation":"RFC 6555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6555.txt","https://www.rfc-editor.org/rfc/rfc6555.pdf"],"folder":"IETF/RFC-6555","files":{"txt":{"path":"standards/IETF/RFC-6555/RFC-6555.txt","sha256":"67eb9f8ec1481e045f0932be9da2eb84d775b01e9d999031e0b4e45b1cf35381"}},"tags":["nested-reference","unchanged"],"summary":"When a server's IPv4 path and protocol are working, but the server's\n IPv6 path and protocol are not working, a dual-stack client\n application experiences significant connection delay compared to an\n IPv4-only client. This is undesirable because it causes the dual-\n stack client to have a worse user experience. This document\n specifies requirements for algorithms that reduce this user-visible\n delay and provides an algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n ","scope_keywords":["6555","algorithm","algorithms","delivery","http","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null}],"search_text":"IETF RFC 6555 When a server's IPv4 path and protocol are working, but the server's\n IPv6 path and protocol are not working, a dual-stack client\n application experiences significant connection delay compared to an\n IPv4-only client. This is undesirable because it causes the dual-\n stack client to have a worse user experience. This document\n specifies requirements for algorithms that reduce this user-visible\n delay and provides an algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n  6555 algorithm algorithms delivery http key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 2501","type":"specification","body":"IETF","designation":"RFC 2501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2501.txt","https://www.rfc-editor.org/rfc/rfc2501.pdf"],"folder":"IETF/RFC-2501","files":{"txt":{"path":"standards/IETF/RFC-2501/RFC-2501.txt","sha256":"9cf287c75dcfb3d9e0ce7dcb10a7e5cd5455c22af008d6a80e23119a864a306c"}},"tags":["nested-reference","unchanged"],"summary":"This memo first describes the characteristics of Mobile Ad hoc\n Networks (MANETs), and their idiosyncrasies with respect to\n traditional, hardwired packet networks. It then discusses the effect\n these differences have on the design and evaluation of network\n control protocols with an emphasis on routing performance evaluation\n considerations.\n\n1. Introduction\n\n With recent performance advancements in computer and wireless\n communications technologies, advanced mobile wireless computing is\n expected to see increasingly widespread use and application, much of\n which will involve the use of the Internet Protocol (IP) suite. The\n vision of mobile ad hoc networking is to support robust and efficient\n operation in mobile wireless networks by incorporating routing\n functionality into mobile nodes. Such networks are envisioned to\n have dynamic, sometimes rapidly-changing, random, multihop topolo","scope_keywords":["2501","delivery","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 2501 This memo first describes the characteristics of Mobile Ad hoc\n Networks (MANETs), and their idiosyncrasies with respect to\n traditional, hardwired packet networks. It then discusses the effect\n these differences have on the design and evaluation of network\n control protocols with an emphasis on routing performance evaluation\n considerations.\n\n1. Introduction\n\n With recent performance advancements in computer and wireless\n communications technologies, advanced mobile wireless computing is\n expected to see increasingly widespread use and application, much of\n which will involve the use of the Internet Protocol (IP) suite. The\n vision of mobile ad hoc networking is to support robust and efficient\n operation in mobile wireless networks by incorporating routing\n functionality into mobile nodes. Such networks are envisioned to\n have dynamic, sometimes rapidly-changing, random, multihop topolo 2501 delivery management pid nested-reference unchanged"},{"id":"IETF RFC 211","type":"specification","body":"IETF","designation":"RFC 211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc211.txt","https://www.rfc-editor.org/rfc/rfc211.pdf"],"folder":"IETF/RFC-211","files":{"pdf":{"path":"standards/IETF/RFC-211/RFC-211.pdf","sha256":"d7004f16b3760229cf29dfdd44c01b55a4c1fe5c424b79c2af8b14c0b08dbf3b"},"txt":{"path":"standards/IETF/RFC-211/RFC-211.txt","sha256":"7a55576e22408067980459d2c82a8d862f4837e39619f4359909c037ad3b22cb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J.B. North\nRequest for Comments: 211 Stanford Research Institute\nObsoletes: RFC 168 NIC 6785 August 1971\nNIC: 7191\n\n ARPA Network Mailing Lists\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n A distribution list for the Network Graphics Group has been sent to\n members of that Group, and will included in the forthcoming Directory\n of Network Participants.\n\n For phone numbers and lists of name by sites, see the Current\n Directory of Network Participants.\n\nA. Initial Distribution List\n\n Note: this list includes all Network Liaisons and others wh","scope_keywords":["211"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 300","folder":"IETF/RFC-300","source":"IETF/RFC-300/RFC-300.txt","version":null}],"search_text":"IETF RFC 211 Network Working Group J.B. North\nRequest for Comments: 211 Stanford Research Institute\nObsoletes: RFC 168 NIC 6785 August 1971\nNIC: 7191\n\n ARPA Network Mailing Lists\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n A distribution list for the Network Graphics Group has been sent to\n members of that Group, and will included in the forthcoming Directory\n of Network Participants.\n\n For phone numbers and lists of name by sites, see the Current\n Directory of Network Participants.\n\nA. Initial Distribution List\n\n Note: this list includes all Network Liaisons and others wh 211 nested-reference unchanged"},{"id":"IETF RFC 1685","type":"specification","body":"IETF","designation":"RFC 1685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1685.txt","https://www.rfc-editor.org/rfc/rfc1685.pdf"],"folder":"IETF/RFC-1685","files":{"txt":{"path":"standards/IETF/RFC-1685/RFC-1685.txt","sha256":"19355ce0ea0d2e13f268c6ac4f4972711d345f7a02d53bd84ffbfe94b6747aab"}},"tags":["nested-reference","unchanged"],"summary":"An O/R address (specified in clause 18) consists of a set of\n values of attributes taken from the list shown in Table F.1. In\n order to represent visually an address to a human user, and to\n enable the user to enter the address into a user interface, each\n attribute value needs to be associated with the correct attribute\n type. Many of the names of the attribute types shown in Table F.1\n are too long for convenient usage on paper or a screen. There is a\n need for a format which allows attributes to be represented\n concisely, e.g., on a business card.","scope_keywords":["1685","attribute","attributes","delivery","policy","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null}],"search_text":"IETF RFC 1685 An O/R address (specified in clause 18) consists of a set of\n values of attributes taken from the list shown in Table F.1. In\n order to represent visually an address to a human user, and to\n enable the user to enter the address into a user interface, each\n attribute value needs to be associated with the correct attribute\n type. Many of the names of the attribute types shown in Table F.1\n are too long for convenient usage on paper or a screen. There is a\n need for a format which allows attributes to be represented\n concisely, e.g., on a business card. 1685 attribute attributes delivery policy presentation subject nested-reference unchanged"},{"id":"IETF RFC 1692","type":"specification","body":"IETF","designation":"RFC 1692","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1692.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1692.txt","https://www.rfc-editor.org/rfc/rfc1692.pdf"],"folder":"IETF/RFC-1692","files":{"txt":{"path":"standards/IETF/RFC-1692/RFC-1692.txt","sha256":"74d4a23ec1d9b5ffa407034172ad32fb1998015361bd192636541f4e9f2da67f"}},"tags":["nested-reference","unchanged"],"summary":"One of the problems with the use of terminal servers is the large\n number of small packets they can generate. Frequently, most of these\n packets are destined for only one or two hosts. TMux is a protocol\n which allows multiple short transport segments, independent of\n application type, to be combined between a server and host pair.\n\nAcknowledgments\n\n This specification is the result of the merger of two documents: the\n original TMux proposal which was the result of several discussions\n and related initiatives through IETF working groups; and IEN 90 [1]\n originally proposed by Danny Cohen and Jon Postel in May 1979.\n\nApplicability Statement\n\n The TMux protocol is intended to optimize the transmission of large\n numbers of small data packets that are generated in situations where\n many interactive Telnet and Rlogin sessions are connected to a few\n hosts on the network. In these situations, ","scope_keywords":["1692"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 1692 One of the problems with the use of terminal servers is the large\n number of small packets they can generate. Frequently, most of these\n packets are destined for only one or two hosts. TMux is a protocol\n which allows multiple short transport segments, independent of\n application type, to be combined between a server and host pair.\n\nAcknowledgments\n\n This specification is the result of the merger of two documents: the\n original TMux proposal which was the result of several discussions\n and related initiatives through IETF working groups; and IEN 90 [1]\n originally proposed by Danny Cohen and Jon Postel in May 1979.\n\nApplicability Statement\n\n The TMux protocol is intended to optimize the transmission of large\n numbers of small data packets that are generated in situations where\n many interactive Telnet and Rlogin sessions are connected to a few\n hosts on the network. In these situations,  1692 nested-reference unchanged"},{"id":"IETF RFC 3606","type":"specification","body":"IETF","designation":"RFC 3606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3606.txt","https://www.rfc-editor.org/rfc/rfc3606.pdf"],"folder":"IETF/RFC-3606","files":{"txt":{"path":"standards/IETF/RFC-3606/RFC-3606.txt","sha256":"7c561d3f56109a88e5f1feed79ac6e38999d096e9e1eca8ee7026099103ca79f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines objects used for managing ATM-based interfaces,\n devices, and services, in addition to those defined in RFC 2515, the\n ATM-MIB, to provide additional support for the management of ATM\n Switched Virtual Connections (SVCs) and ATM Permanent Virtual\n Connections (PVCs).\n\nLy, et al. Standards Track [Page 1]\n\f\nRFC 3606 Supplemental ATM Managed Objects November 2003","scope_keywords":["3606","management","path","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 3606 This memo defines objects used for managing ATM-based interfaces,\n devices, and services, in addition to those defined in RFC 2515, the\n ATM-MIB, to provide additional support for the management of ATM\n Switched Virtual Connections (SVCs) and ATM Permanent Virtual\n Connections (PVCs).\n\nLy, et al. Standards Track [Page 1]\n\f\nRFC 3606 Supplemental ATM Managed Objects November 2003 3606 management path registered nested-reference unchanged"},{"id":"IETF RFC 2514","type":"specification","body":"IETF","designation":"RFC 2514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2514.txt","https://www.rfc-editor.org/rfc/rfc2514.pdf"],"folder":"IETF/RFC-2514","files":{"txt":{"path":"standards/IETF/RFC-2514/RFC-2514.txt","sha256":"6100fc0abb27dc5aaa20f614792a1a9a577a3b43c39f66eeda714adca8af463f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Noto\nRequest for Comments: 2514 3Com\nCategory: Standards Track E. Spiegel\n Cisco Systems\n K. Tesink\n Bellcore\n Editors\n February 1999\n\n Definitions of Textual Conventions and OBJECT-IDENTITIES\n for ATM Management\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Definitions ........................................... 3\n 3 Acknowledgments ....................................... 17\n 4 Referen","scope_keywords":["2514","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null}],"search_text":"IETF RFC 2514 Network Working Group M. Noto\nRequest for Comments: 2514 3Com\nCategory: Standards Track E. Spiegel\n Cisco Systems\n K. Tesink\n Bellcore\n Editors\n February 1999\n\n Definitions of Textual Conventions and OBJECT-IDENTITIES\n for ATM Management\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n Table of Contents\n\n 1 Introduction .......................................... 2\n 2 Definitions ........................................... 3\n 3 Acknowledgments ....................................... 17\n 4 Referen 2514 key management nested-reference unchanged"},{"id":"IETF RFC 1851","type":"specification","body":"IETF","designation":"RFC 1851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1851.txt","https://www.rfc-editor.org/rfc/rfc1851.pdf"],"folder":"IETF/RFC-1851","files":{"txt":{"path":"standards/IETF/RFC-1851/RFC-1851.txt","sha256":"1490be4231a397cc88dec60254f85ff0f6a26baa690cb2a65d73e5e4df42d178"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Triple DES-CBC security transform for the\n IP Encapsulating Security Payload (ESP).","scope_keywords":["1851","algorithm","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null}],"search_text":"IETF RFC 1851 This document describes the Triple DES-CBC security transform for the\n IP Encapsulating Security Payload (ESP). 1851 algorithm encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 1852","type":"specification","body":"IETF","designation":"RFC 1852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1852.txt","https://www.rfc-editor.org/rfc/rfc1852.pdf"],"folder":"IETF/RFC-1852","files":{"txt":{"path":"standards/IETF/RFC-1852/RFC-1852.txt","sha256":"89afbfab11bf81ff33f2305d981746f22e404b4649bde6fcf60eec73edcb445e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of keyed SHA with the IP\n Authentication Header.","scope_keywords":["1852","algorithm","algorithms","authentication","hash","hashing","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2085","folder":"IETF/RFC-2085","source":"IETF/RFC-2085/RFC-2085.txt","version":null}],"search_text":"IETF RFC 1852 This document describes the use of keyed SHA with the IP\n Authentication Header. 1852 algorithm algorithms authentication hash hashing key keys management nested-reference unchanged"},{"id":"IETF RFC 2066","type":"specification","body":"IETF","designation":"RFC 2066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2066.txt","https://www.rfc-editor.org/rfc/rfc2066.pdf"],"folder":"IETF/RFC-2066","files":{"txt":{"path":"standards/IETF/RFC-2066/RFC-2066.txt","sha256":"02a9619ed6a229614a15e86eb6e2871d9d992787f4bb0f5185acbaf9859599dc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Gellens\nRequest for Comments: 2066 Unisys\nCategory: Experimental January 1997\n\n TELNET CHARSET Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing character set and\n translation information between a TELNET client and server. Use of\n this mechanism enables an application used by a TELNET user to send\n and receive data in the correct character set.\n\n Either side can (subject to option negotiation) at any time request\n that a (new) character set be used.\n\n1. Command Names and Codes\n\n CHARSET.......................42\n\n REQUEST ....................01\n ACCEPTED ...................02\n REJECTED .........","scope_keywords":["2066","issuer","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2066 Network Working Group R. Gellens\nRequest for Comments: 2066 Unisys\nCategory: Experimental January 1997\n\n TELNET CHARSET Option\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document specifies a mechanism for passing character set and\n translation information between a TELNET client and server. Use of\n this mechanism enables an application used by a TELNET user to send\n and receive data in the correct character set.\n\n Either side can (subject to option negotiation) at any time request\n that a (new) character set be used.\n\n1. Command Names and Codes\n\n CHARSET.......................42\n\n REQUEST ....................01\n ACCEPTED ...................02\n REJECTED ......... 2066 issuer registered subject nested-reference unchanged"},{"id":"IETF RFC 2122","type":"specification","body":"IETF","designation":"RFC 2122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2122.txt","https://www.rfc-editor.org/rfc/rfc2122.pdf"],"folder":"IETF/RFC-2122","files":{"txt":{"path":"standards/IETF/RFC-2122/RFC-2122.txt","sha256":"2853092b3d9dec62f51af68f5b4a601dec5542272a7564f47d77363223100ff6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Mavrakis\nRequest for Comments: 2122 Monaco Telematique MC-TEL\nCategory: Standards Track H. Layec\n ETSI\n K. Kartmann\n Telecommunication+Multimedia\n March 1997\n\n VEMMI URL Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1) Abstract\n\n A new URL scheme, \"vemmi\" is defined. It allows VEMMI client software\n and VEMMI terminals to connect to multimedia interactive services\n compliant to the VEMMI standard (Enhanced Man-Machine Interface for\n Videotex and Multimedia/Hypermedia Information Retrieval Services),\n sometimes abbreviated as \"VErsatile M","scope_keywords":["2122","attribute","attributes","http","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2122 Network Working Group D. Mavrakis\nRequest for Comments: 2122 Monaco Telematique MC-TEL\nCategory: Standards Track H. Layec\n ETSI\n K. Kartmann\n Telecommunication+Multimedia\n March 1997\n\n VEMMI URL Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1) Abstract\n\n A new URL scheme, \"vemmi\" is defined. It allows VEMMI client software\n and VEMMI terminals to connect to multimedia interactive services\n compliant to the VEMMI standard (Enhanced Man-Machine Interface for\n Videotex and Multimedia/Hypermedia Information Retrieval Services),\n sometimes abbreviated as \"VErsatile M 2122 attribute attributes http identification presentation nested-reference unchanged"},{"id":"IETF RFC 2189","type":"specification","body":"IETF","designation":"RFC 2189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2189.txt","https://www.rfc-editor.org/rfc/rfc2189.pdf"],"folder":"IETF/RFC-2189","files":{"txt":{"path":"standards/IETF/RFC-2189/RFC-2189.txt","sha256":"6ae2753c8318561e3a693e21c6e0692b52a5bee9216a5b8bdcaa270311d8a8e7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Core Based Tree (CBT version 2) network\n layer multicast routing protocol. CBT builds a shared multicast\n distribution tree per group, and is suited to inter- and intra-domain\n multicast routing.\n\n CBT may use a separate multicast routing table, or it may use that of\n underlying unicast routing, to establish paths between senders and\n receivers. The CBT architecture is described in [1].\n\n This document is progressing through the IDMR working group of the\n IETF. CBT related documents include [1, 5, 6]. For all IDMR-related\n documents, see http://www.cs.ucl.ac.uk/ietf/idmr.","scope_keywords":["2189","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 2715","folder":"IETF/RFC-2715","source":"IETF/RFC-2715/RFC-2715.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null}],"search_text":"IETF RFC 2189 This document describes the Core Based Tree (CBT version 2) network\n layer multicast routing protocol. CBT builds a shared multicast\n distribution tree per group, and is suited to inter- and intra-domain\n multicast routing.\n\n CBT may use a separate multicast routing table, or it may use that of\n underlying unicast routing, to establish paths between senders and\n receivers. The CBT architecture is described in [1].\n\n This document is progressing through the IDMR working group of the\n IETF. CBT related documents include [1, 5, 6]. For all IDMR-related\n documents, see http://www.cs.ucl.ac.uk/ietf/idmr. 2189 http path nested-reference unchanged"},{"id":"IETF RFC 2222","type":"specification","body":"IETF","designation":"RFC 2222","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2222.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2222.txt","https://www.rfc-editor.org/rfc/rfc2222.pdf"],"folder":"IETF/RFC-2222","files":{"txt":{"path":"standards/IETF/RFC-2222/RFC-2222.txt","sha256":"1ec29efa6bee0996e6cb46600bab0865534e07119189dcdf461fb42a72e56b95"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for adding authentication support to\n connection-based protocols. To use this specification, a protocol\n includes a command for identifying and authenticating a user to a\n server and for optionally negotiating protection of subsequent\n protocol interactions. If its use is negotiated, a security layer is\n inserted between the protocol and the connection. This document\n describes how a protocol specifies such a command, defines several\n mechanisms for use by the command, and defines the protocol used for\n carrying a negotiated security layer over the connection.\n\n2. Organization of this Document","scope_keywords":["2222","authentication","authorization","credential","credentials","key","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2245","folder":"IETF/RFC-2245","source":"IETF/RFC-2245/RFC-2245.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null}],"search_text":"IETF RFC 2222 This document describes a method for adding authentication support to\n connection-based protocols. To use this specification, a protocol\n includes a command for identifying and authenticating a user to a\n server and for optionally negotiating protection of subsequent\n protocol interactions. If its use is negotiated, a security layer is\n inserted between the protocol and the connection. This document\n describes how a protocol specifies such a command, defines several\n mechanisms for use by the command, and defines the protocol used for\n carrying a negotiated security layer over the connection.\n\n2. Organization of this Document 2222 authentication authorization credential credentials key profile registered nested-reference unchanged"},{"id":"IETF RFC 2278","type":"specification","body":"IETF","designation":"RFC 2278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2278.txt","https://www.rfc-editor.org/rfc/rfc2278.pdf"],"folder":"IETF/RFC-2278","files":{"txt":{"path":"standards/IETF/RFC-2278/RFC-2278.txt","sha256":"85baba44f9b3344700983ce54452bbc5c9877443234923402ace27b59b727533"}},"tags":["nested-reference","unchanged"],"summary":"MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other\n modern Internet protocols are capable of using many different\n charsets. This in turn means that the ability to label different\n charsets is essential. This registration procedure exists solely to\n associate a specific name or names with a given charset and to give\n an indication of whether or not a given charset can be used in MIME\n text objects. In particular, the general applicability and\n appropriateness of a given registered charset is a protocol issue,\n not a registration issue, and is not dealt with by this registration\n procedure.\n\n2. Definitions and Notation\n\n The following sections define various terms used in this document.","scope_keywords":["2278","presentation","profile","profiles","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null}],"search_text":"IETF RFC 2278 MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other\n modern Internet protocols are capable of using many different\n charsets. This in turn means that the ability to label different\n charsets is essential. This registration procedure exists solely to\n associate a specific name or names with a given charset and to give\n an indication of whether or not a given charset can be used in MIME\n text objects. In particular, the general applicability and\n appropriateness of a given registered charset is a protocol issue,\n not a registration issue, and is not dealt with by this registration\n procedure.\n\n2. Definitions and Notation\n\n The following sections define various terms used in this document. 2278 presentation profile profiles registered tls nested-reference unchanged"},{"id":"IETF RFC 2283","type":"specification","body":"IETF","designation":"RFC 2283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2283.txt","https://www.rfc-editor.org/rfc/rfc2283.pdf"],"folder":"IETF/RFC-2283","files":{"txt":{"path":"standards/IETF/RFC-2283/RFC-2283.txt","sha256":"779bd5d77070d1b2b5ef0852a884782577509274371b5aa21cce5479a69a94a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Bates\nRequest for Comments: 2283 Cisco Systems\nCategory: Standards Track R. Chandra\n Cisco Systems\n D. Katz\n Juniper Networks\n Y. Rekhter\n Cisco Systems\n February 1998\n\n Multiprotocol Extensions for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Abstract\n\n Currently BGP-4 [BGP-4] is capable of carrying routing information\n only for IPv4 [IPv4]. This document defines extensions to BGP-4 to\n enable it to carry routing information for multiple Network Layer\n proto","scope_keywords":["2283","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2545","folder":"IETF/RFC-2545","source":"IETF/RFC-2545/RFC-2545.txt","version":null},{"body":"IETF","designation":"RFC 2546","folder":"IETF/RFC-2546","source":"IETF/RFC-2546/RFC-2546.txt","version":null},{"body":"IETF","designation":"RFC 2547","folder":"IETF/RFC-2547","source":"IETF/RFC-2547/RFC-2547.txt","version":null},{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null}],"search_text":"IETF RFC 2283 Network Working Group T. Bates\nRequest for Comments: 2283 Cisco Systems\nCategory: Standards Track R. Chandra\n Cisco Systems\n D. Katz\n Juniper Networks\n Y. Rekhter\n Cisco Systems\n February 1998\n\n Multiprotocol Extensions for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Abstract\n\n Currently BGP-4 [BGP-4] is capable of carrying routing information\n only for IPv4 [IPv4]. This document defines extensions to BGP-4 to\n enable it to carry routing information for multiple Network Layer\n proto 2283 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 2334","type":"specification","body":"IETF","designation":"RFC 2334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2334.txt","https://www.rfc-editor.org/rfc/rfc2334.pdf"],"folder":"IETF/RFC-2334","files":{"txt":{"path":"standards/IETF/RFC-2334/RFC-2334.txt","sha256":"6f78a03e841c9e269e74ea66494033dd79650daa69a7b2585004c6fc9fd3ab65"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Server Cache Synchronization Protocol\n (SCSP) and is written in terms of SCSP's use within Non Broadcast\n Multiple Access (NBMA) networks; although, a somewhat straight\n forward usage is applicable to BMA networks. SCSP attempts to solve\n the generalized cache synchronization/cache-replication problem for\n distributed protocol entities. However, in this document, SCSP is\n couched in terms of the client/server paradigm in which distributed\n server entities, which are bound to a Server Group (SG) through some\n means, wish to synchronize the contents (or a portion thereof) of\n their caches which contain information about the state of clients\n being served.\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [10].\n\n","scope_keywords":["2334","algorithm","authentication","key","path","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2335","folder":"IETF/RFC-2335","source":"IETF/RFC-2335/RFC-2335.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2334 This document describes the Server Cache Synchronization Protocol\n (SCSP) and is written in terms of SCSP's use within Non Broadcast\n Multiple Access (NBMA) networks; although, a somewhat straight\n forward usage is applicable to BMA networks. SCSP attempts to solve\n the generalized cache synchronization/cache-replication problem for\n distributed protocol entities. However, in this document, SCSP is\n couched in terms of the client/server paradigm in which distributed\n server entities, which are bound to a Server Group (SG) through some\n means, wish to synchronize the contents (or a portion thereof) of\n their caches which contain information about the state of clients\n being served.\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [10].\n\n 2334 algorithm authentication key path pid registered nested-reference unchanged"},{"id":"IETF RFC 2335","type":"specification","body":"IETF","designation":"RFC 2335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2335.txt","https://www.rfc-editor.org/rfc/rfc2335.pdf"],"folder":"IETF/RFC-2335","files":{"txt":{"path":"standards/IETF/RFC-2335/RFC-2335.txt","sha256":"ce743b31f3bf6e690bca676adaa0e4037534f8d3cd89d8173b0e79549ec978b3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for distributing an NHRP service\n within a LIS [1]. This method uses the Server Cache Synchronization\n Protocol (SCSP) [2] to synchronize the client information databases\n held by NHRP Servers (NHSs) within a LIS.\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [4].\n\n NHRP Clients (NHCs) register their existence and reachability\n information with NHRP Servers (NHSs). There may be multiple NHSs in\n a given Logical IP Subnet (LIS). NHCs do not necessarily register\n with all NHSs in a LIS; however, all NHCs need to be able to query at\n least one NHS about any NHC within the LIS. Thus, the contents of\n the NHS databases in a LIS need to be synchronized across the LIS.\n The Server Cache Synchronization Proto","scope_keywords":["2335","key","management","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2335 This document describes a method for distributing an NHRP service\n within a LIS [1]. This method uses the Server Cache Synchronization\n Protocol (SCSP) [2] to synchronize the client information databases\n held by NHRP Servers (NHSs) within a LIS.\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [4].\n\n NHRP Clients (NHCs) register their existence and reachability\n information with NHRP Servers (NHSs). There may be multiple NHSs in\n a given Logical IP Subnet (LIS). NHCs do not necessarily register\n with all NHSs in a LIS; however, all NHCs need to be able to query at\n least one NHS about any NHC within the LIS. Thus, the contents of\n the NHS databases in a LIS need to be synchronized across the LIS.\n The Server Cache Synchronization Proto 2335 key management pid registered nested-reference unchanged"},{"id":"IETF RFC 2365","type":"specification","body":"IETF","designation":"RFC 2365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2365.txt","https://www.rfc-editor.org/rfc/rfc2365.pdf"],"folder":"IETF/RFC-2365","files":{"txt":{"path":"standards/IETF/RFC-2365/RFC-2365.txt","sha256":"20c5764c2cbbfdacc290c53e9b7998e917f15337fec5a9cc4dc13a604b0bc655"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the \"administratively scoped IPv4 multicast\n space\" to be the range 239.0.0.0 to 239.255.255.255. In addition, it\n describes a simple set of semantics for the implementation of\n Administratively Scoped IP Multicast. Finally, it provides a mapping\n between the IPv6 multicast address classes [RFC1884] and IPv4\n multicast address classes.\n\n This memo is a product of the MBONE Deployment Working Group (MBONED)\n in the Operations and Management Area of the Internet Engineering\n Task Force. Submit comments to <mboned@ns.uoregon.edu> or the author.\n\n2. Acknowledgments\n\n Much of this memo is taken from \"Administratively Scoped IP\n Multicast\", Van Jacobson and Steve Deering, presented at the 30th\n IETF, Toronto, Canada, 25 July 1994. Steve Casner, Mark Handley and\n Dave Thaler have also provided insightful comments on earlier\n versions of this document.\n\n3. Introduction\n\n Mo","scope_keywords":["2365","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2770","folder":"IETF/RFC-2770","source":"IETF/RFC-2770/RFC-2770.txt","version":null},{"body":"IETF","designation":"RFC 2771","folder":"IETF/RFC-2771","source":"IETF/RFC-2771/RFC-2771.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2907","folder":"IETF/RFC-2907","source":"IETF/RFC-2907/RFC-2907.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 2365 This document defines the \"administratively scoped IPv4 multicast\n space\" to be the range 239.0.0.0 to 239.255.255.255. In addition, it\n describes a simple set of semantics for the implementation of\n Administratively Scoped IP Multicast. Finally, it provides a mapping\n between the IPv6 multicast address classes [RFC1884] and IPv4\n multicast address classes.\n\n This memo is a product of the MBONE Deployment Working Group (MBONED)\n in the Operations and Management Area of the Internet Engineering\n Task Force. Submit comments to <mboned@ns.uoregon.edu> or the author.\n\n2. Acknowledgments\n\n Much of this memo is taken from \"Administratively Scoped IP\n Multicast\", Van Jacobson and Steve Deering, presented at the 30th\n IETF, Toronto, Canada, 25 July 1994. Steve Casner, Mark Handley and\n Dave Thaler have also provided insightful comments on earlier\n versions of this document.\n\n3. Introduction\n\n Mo 2365 key management path nested-reference unchanged"},{"id":"IETF RFC 2393","type":"specification","body":"IETF","designation":"RFC 2393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2393.txt","https://www.rfc-editor.org/rfc/rfc2393.pdf"],"folder":"IETF/RFC-2393","files":{"txt":{"path":"standards/IETF/RFC-2393/RFC-2393.txt","sha256":"1195144f7e9f669f7364bde33fa1b2c666601a50cfc5b84ec73f7432c77c0979"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol intended to provide lossless\n compression for Internet Protocol datagrams in an Internet\n environment.\n\n1. Introduction\n\n IP payload compression is a protocol to reduce the size of IP\n datagrams. This protocol will increase the overall communication\n performance between a pair of communicating hosts/gateways (\"nodes\")\n by compressing the datagrams, provided the nodes have sufficient\n computation power, through either CPU capacity or a compression\n coprocessor, and the communication is over slow or congested links.\n\n IP payload compression is especially useful when encryption is\n applied to IP datagrams. Encrypting the IP datagram causes the data\n to be random in nature, rendering compression at lower protocol\n layers (e.g., PPP Compression Control Protocol [RFC-1962])\n ineffective. If both compression and encryption are required,\n compression MUST be ap","scope_keywords":["2393","algorithm","algorithms","authentication","delivery","encryption","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2394","folder":"IETF/RFC-2394","source":"IETF/RFC-2394/RFC-2394.txt","version":null},{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3051","folder":"IETF/RFC-3051","source":"IETF/RFC-3051/RFC-3051.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null}],"search_text":"IETF RFC 2393 This document describes a protocol intended to provide lossless\n compression for Internet Protocol datagrams in an Internet\n environment.\n\n1. Introduction\n\n IP payload compression is a protocol to reduce the size of IP\n datagrams. This protocol will increase the overall communication\n performance between a pair of communicating hosts/gateways (\"nodes\")\n by compressing the datagrams, provided the nodes have sufficient\n computation power, through either CPU capacity or a compression\n coprocessor, and the communication is over slow or congested links.\n\n IP payload compression is especially useful when encryption is\n applied to IP datagrams. Encrypting the IP datagram causes the data\n to be random in nature, rendering compression at lower protocol\n layers (e.g., PPP Compression Control Protocol [RFC-1962])\n ineffective. If both compression and encryption are required,\n compression MUST be ap 2393 algorithm algorithms authentication delivery encryption key path policy nested-reference unchanged"},{"id":"IETF RFC 2406","type":"specification","body":"IETF","designation":"RFC 2406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2406.txt","https://www.rfc-editor.org/rfc/rfc2406.pdf"],"folder":"IETF/RFC-2406","files":{"txt":{"path":"standards/IETF/RFC-2406/RFC-2406.txt","sha256":"c0f374ada92b1ccf847c10d50842ba14b626df14cc34345512fee249c83b6f09"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 2406 BBN Corp\nObsoletes: 1827 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n IP Encapsulating Security Payload (ESP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction..................................................2\n 2. Encapsulating Security Payload Packet Format..................3\n 2.1 Security Parameters Index................................4\n 2.2 Sequence Number .....................","scope_keywords":["2406","algorithm","algorithms","audit","authentication","encryption","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2412","folder":"IETF/RFC-2412","source":"IETF/RFC-2412/RFC-2412.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3610","folder":"IETF/RFC-3610","source":"IETF/RFC-3610/RFC-3610.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3884","folder":"IETF/RFC-3884","source":"IETF/RFC-3884/RFC-3884.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 2406 Network Working Group S. Kent\nRequest for Comments: 2406 BBN Corp\nObsoletes: 1827 R. Atkinson\nCategory: Standards Track @Home Network\n November 1998\n\n IP Encapsulating Security Payload (ESP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTable of Contents\n\n 1. Introduction..................................................2\n 2. Encapsulating Security Payload Packet Format..................3\n 2.1 Security Parameters Index................................4\n 2.2 Sequence Number ..................... 2406 algorithm algorithms audit authentication encryption key management subject nested-reference unchanged"},{"id":"IETF RFC 2434","type":"specification","body":"IETF","designation":"RFC 2434","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2434.txt","https://www.rfc-editor.org/rfc/rfc2434.pdf"],"folder":"IETF/RFC-2434","files":{"txt":{"path":"standards/IETF/RFC-2434/RFC-2434.txt","sha256":"98cf146c3f3335ac4b73800af30e9922b7659d4c920385d690f2a1efc093c62b"}},"tags":["nested-reference","unchanged"],"summary":"Many protocols make use of identifiers consisting of constants and\n other well-known values. Even after a protocol has been defined and\n deployment has begun, new values may need to be assigned (e.g., for a\n new option type in DHCP, or a new encryption or authentication\n algorithm for IPSec). To insure that such quantities have consistent\n values and interpretations in different implementations, their\n assignment must be administered by a central authority. For IETF\n protocols, that role is provided by the Internet Assigned Numbers\n Authority (IANA).\n\n In order for the IANA to manage a given name space prudently, it\n needs guidelines describing the conditions under which new values can\n be assigned. If the IANA is expected to play a role in the management\n of a name space, the IANA must be given clear and concise\n instructions describing that role. This document discusses issues\n that sh","scope_keywords":["2434","algorithm","authentication","encryption","key","management","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2489","folder":"IETF/RFC-2489","source":"IETF/RFC-2489/RFC-2489.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2711","folder":"IETF/RFC-2711","source":"IETF/RFC-2711/RFC-2711.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2842","folder":"IETF/RFC-2842","source":"IETF/RFC-2842/RFC-2842.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2929","folder":"IETF/RFC-2929","source":"IETF/RFC-2929/RFC-2929.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2939","folder":"IETF/RFC-2939","source":"IETF/RFC-2939/RFC-2939.txt","version":null},{"body":"IETF","designation":"RFC 2941","folder":"IETF/RFC-2941","source":"IETF/RFC-2941/RFC-2941.txt","version":null},{"body":"IETF","designation":"RFC 2946","folder":"IETF/RFC-2946","source":"IETF/RFC-2946/RFC-2946.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3048","folder":"IETF/RFC-3048","source":"IETF/RFC-3048/RFC-3048.txt","version":null},{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3224","folder":"IETF/RFC-3224","source":"IETF/RFC-3224/RFC-3224.txt","version":null},{"body":"IETF","designation":"RFC 3228","folder":"IETF/RFC-3228","source":"IETF/RFC-3228/RFC-3228.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3310","folder":"IETF/RFC-3310","source":"IETF/RFC-3310/RFC-3310.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3375","folder":"IETF/RFC-3375","source":"IETF/RFC-3375/RFC-3375.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3392","folder":"IETF/RFC-3392","source":"IETF/RFC-3392/RFC-3392.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3427","folder":"IETF/RFC-3427","source":"IETF/RFC-3427/RFC-3427.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3438","folder":"IETF/RFC-3438","source":"IETF/RFC-3438/RFC-3438.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3454","folder":"IETF/RFC-3454","source":"IETF/RFC-3454/RFC-3454.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3477","folder":"IETF/RFC-3477","source":"IETF/RFC-3477/RFC-3477.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3526","folder":"IETF/RFC-3526","source":"IETF/RFC-3526/RFC-3526.txt","version":null},{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3561","folder":"IETF/RFC-3561","source":"IETF/RFC-3561/RFC-3561.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3626","folder":"IETF/RFC-3626","source":"IETF/RFC-3626/RFC-3626.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3643","folder":"IETF/RFC-3643","source":"IETF/RFC-3643/RFC-3643.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3692","folder":"IETF/RFC-3692","source":"IETF/RFC-3692/RFC-3692.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3818","folder":"IETF/RFC-3818","source":"IETF/RFC-3818/RFC-3818.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3932","folder":"IETF/RFC-3932","source":"IETF/RFC-3932/RFC-3932.txt","version":null},{"body":"IETF","designation":"RFC 3936","folder":"IETF/RFC-3936","source":"IETF/RFC-3936/RFC-3936.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 3969","folder":"IETF/RFC-3969","source":"IETF/RFC-3969/RFC-3969.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4020","folder":"IETF/RFC-4020","source":"IETF/RFC-4020/RFC-4020.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4090","folder":"IETF/RFC-4090","source":"IETF/RFC-4090/RFC-4090.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4384","folder":"IETF/RFC-4384","source":"IETF/RFC-4384/RFC-4384.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4581","folder":"IETF/RFC-4581","source":"IETF/RFC-4581/RFC-4581.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4589","folder":"IETF/RFC-4589","source":"IETF/RFC-4589/RFC-4589.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4636","folder":"IETF/RFC-4636","source":"IETF/RFC-4636/RFC-4636.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4680","folder":"IETF/RFC-4680","source":"IETF/RFC-4680/RFC-4680.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4773","folder":"IETF/RFC-4773","source":"IETF/RFC-4773/RFC-4773.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4813","folder":"IETF/RFC-4813","source":"IETF/RFC-4813/RFC-4813.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5159","folder":"IETF/RFC-5159","source":"IETF/RFC-5159/RFC-5159.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5224","folder":"IETF/RFC-5224","source":"IETF/RFC-5224/RFC-5224.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 2434 Many protocols make use of identifiers consisting of constants and\n other well-known values. Even after a protocol has been defined and\n deployment has begun, new values may need to be assigned (e.g., for a\n new option type in DHCP, or a new encryption or authentication\n algorithm for IPSec). To insure that such quantities have consistent\n values and interpretations in different implementations, their\n assignment must be administered by a central authority. For IETF\n protocols, that role is provided by the Internet Assigned Numbers\n Authority (IANA).\n\n In order for the IANA to manage a given name space prudently, it\n needs guidelines describing the conditions under which new values can\n be assigned. If the IANA is expected to play a role in the management\n of a name space, the IANA must be given clear and concise\n instructions describing that role. This document discusses issues\n that sh 2434 algorithm authentication encryption key management policy subject nested-reference unchanged"},{"id":"IETF RFC 2590","type":"specification","body":"IETF","designation":"RFC 2590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2590.txt","https://www.rfc-editor.org/rfc/rfc2590.pdf"],"folder":"IETF/RFC-2590","files":{"txt":{"path":"standards/IETF/RFC-2590/RFC-2590.txt","sha256":"4fba0418395a312a7714e09880e8924eaf4643bc0d8839cc577946ad90c8911a"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes mechanisms for the transmission of IPv6 packets\n over Frame Relay networks.","scope_keywords":["2590","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"IETF RFC 2590 This memo describes mechanisms for the transmission of IPv6 packets\n over Frame Relay networks. 2590 key pid nested-reference unchanged"},{"id":"IETF RFC 2776","type":"specification","body":"IETF","designation":"RFC 2776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2776.txt","https://www.rfc-editor.org/rfc/rfc2776.pdf"],"folder":"IETF/RFC-2776","files":{"txt":{"path":"standards/IETF/RFC-2776/RFC-2776.txt","sha256":"7431ed5cea2b81131632c5551400572a9a9596a26e12e6b985d67f09958babe7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a protocol, the Multicast-Scope Zone\n Announcement Protocol (MZAP), for discovering the multicast\n administrative scope zones that are relevant at a particular\n location. MZAP also provides mechanisms whereby common\n misconfigurations of administrative scope zones can be discovered.","scope_keywords":["2776"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2907","folder":"IETF/RFC-2907","source":"IETF/RFC-2907/RFC-2907.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2776 This document defines a protocol, the Multicast-Scope Zone\n Announcement Protocol (MZAP), for discovering the multicast\n administrative scope zones that are relevant at a particular\n location. MZAP also provides mechanisms whereby common\n misconfigurations of administrative scope zones can be discovered. 2776 nested-reference unchanged"},{"id":"IETF RFC 2858","type":"specification","body":"IETF","designation":"RFC 2858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2858.txt","https://www.rfc-editor.org/rfc/rfc2858.pdf"],"folder":"IETF/RFC-2858","files":{"txt":{"path":"standards/IETF/RFC-2858/RFC-2858.txt","sha256":"bca36a6c07900874867cde510e6f6d3a3403c4fe027578b9d7c39045cae88057"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Bates\nRequest for Comments: 2858 Y. Rekhter\nObsoletes: 2283 Cisco Systems\nCategory: Standards Track R. Chandra\n Redback Networks Inc\n D. Katz\n Juniper Networks\n June 2000\n\n Multiprotocol Extensions for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently BGP-4 [BGP-4] is capable of carrying routing information\n only for IPv4 [IPv4]. This document defines extensions to BGP-4 to\n enable it to carry routing information for multiple Network Layer\n proto","scope_keywords":["2858","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2918","folder":"IETF/RFC-2918","source":"IETF/RFC-2918/RFC-2918.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4724","folder":"IETF/RFC-4724","source":"IETF/RFC-4724/RFC-4724.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null}],"search_text":"IETF RFC 2858 Network Working Group T. Bates\nRequest for Comments: 2858 Y. Rekhter\nObsoletes: 2283 Cisco Systems\nCategory: Standards Track R. Chandra\n Redback Networks Inc\n D. Katz\n Juniper Networks\n June 2000\n\n Multiprotocol Extensions for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently BGP-4 [BGP-4] is capable of carrying routing information\n only for IPv4 [IPv4]. This document defines extensions to BGP-4 to\n enable it to carry routing information for multiple Network Layer\n proto 2858 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 2868","type":"specification","body":"IETF","designation":"RFC 2868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2868.txt","https://www.rfc-editor.org/rfc/rfc2868.pdf"],"folder":"IETF/RFC-2868","files":{"txt":{"path":"standards/IETF/RFC-2868/RFC-2868.txt","sha256":"9e25c6fb25b770d016070eb6f1209a70dd6393ad5e0bfd708753acd8d7642516"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of RADIUS attributes designed to support\n the provision of compulsory tunneling in dial-up networks.\n\n1. Motivation\n\n Many applications of tunneling protocols such as L2TP involve dial-up\n network access. Some, such as the provision of access to corporate\n intranets via the Internet, are characterized by voluntary tunneling:\n the tunnel is created at the request of the user for a specific\n purpose. Other applications involve compulsory tunneling: the tunnel\n is created without any action from the user and without allowing the\n user any choice in the matter. In order to provide this\n functionality, new RADIUS attributes are needed to carry the\n tunneling information from the RADIUS server to the tunnel end\n points; this document defines those attributes. Specific\n recommendations for, and examples of, the application of these\n attributes for L2TP can be found i","scope_keywords":["2868","attribute","attributes","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 3070","folder":"IETF/RFC-3070","source":"IETF/RFC-3070/RFC-3070.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2868 This document defines a set of RADIUS attributes designed to support\n the provision of compulsory tunneling in dial-up networks.\n\n1. Motivation\n\n Many applications of tunneling protocols such as L2TP involve dial-up\n network access. Some, such as the provision of access to corporate\n intranets via the Internet, are characterized by voluntary tunneling:\n the tunnel is created at the request of the user for a specific\n purpose. Other applications involve compulsory tunneling: the tunnel\n is created without any action from the user and without allowing the\n user any choice in the matter. In order to provide this\n functionality, new RADIUS attributes are needed to carry the\n tunneling information from the RADIUS server to the tunnel end\n points; this document defines those attributes. Specific\n recommendations for, and examples of, the application of these\n attributes for L2TP can be found i 2868 attribute attributes authentication key management nested-reference unchanged"},{"id":"IETF RFC 2869","type":"specification","body":"IETF","designation":"RFC 2869","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2869.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2869.txt","https://www.rfc-editor.org/rfc/rfc2869.pdf"],"folder":"IETF/RFC-2869","files":{"txt":{"path":"standards/IETF/RFC-2869/RFC-2869.txt","sha256":"99052a8d3ff02fba3ec913a8856366618f1964c4300605e3054022a80f29deb4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes additional attributes for carrying\n authentication, authorization and accounting information between a\n Network Access Server (NAS) and a shared Accounting Server using the\n Remote Authentication Dial In User Service (RADIUS) protocol\n described in RFC 2865 [1] and RFC 2866 [2].","scope_keywords":["2869","attribute","attributes","authentication","authorization","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2869 This document describes additional attributes for carrying\n authentication, authorization and accounting information between a\n Network Access Server (NAS) and a shared Accounting Server using the\n Remote Authentication Dial In User Service (RADIUS) protocol\n described in RFC 2865 [1] and RFC 2866 [2]. 2869 attribute attributes authentication authorization key timestamp nested-reference unchanged"},{"id":"IETF RFC 3025","type":"specification","body":"IETF","designation":"RFC 3025","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3025.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3025.txt","https://www.rfc-editor.org/rfc/rfc3025.pdf"],"folder":"IETF/RFC-3025","files":{"txt":{"path":"standards/IETF/RFC-3025/RFC-3025.txt","sha256":"a78c3ae690227b0953b5a31a4eebbf0b62a0b5fb7aac67cd5a01d1f73efe70f2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new extensions to Mobile IP. These\n extensions will facilitate equipment vendors and organizations to\n make specific use of these extensions as they see fit for research or\n deployment purposes.\n\n1. Introduction\n\n Current specification of Mobile IP [1] does not allow for\n organizations and vendors to include organization/vendor-specific\n information in the Mobile IP messages. With the imminent wide scale\n deployment of Mobile IP it is useful to have vendor or organization-\n Specific Extensions to support this capability. This document\n defines two extensions that can be used for making organization\n specific extensions by vendors/organizations for their own specific\n purposes.","scope_keywords":["3025","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null}],"search_text":"IETF RFC 3025 This document defines two new extensions to Mobile IP. These\n extensions will facilitate equipment vendors and organizations to\n make specific use of these extensions as they see fit for research or\n deployment purposes.\n\n1. Introduction\n\n Current specification of Mobile IP [1] does not allow for\n organizations and vendors to include organization/vendor-specific\n information in the Mobile IP messages. With the imminent wide scale\n deployment of Mobile IP it is useful to have vendor or organization-\n Specific Extensions to support this capability. This document\n defines two extensions that can be used for making organization\n specific extensions by vendors/organizations for their own specific\n purposes. 3025 key management nested-reference unchanged"},{"id":"IETF RFC 3115","type":"specification","body":"IETF","designation":"RFC 3115","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3115.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3115.txt","https://www.rfc-editor.org/rfc/rfc3115.pdf"],"folder":"IETF/RFC-3115","files":{"txt":{"path":"standards/IETF/RFC-3115/RFC-3115.txt","sha256":"32871458643d39c977fcae6ab62325d1ca24de6e57c8ffc332bf98d82fb07bb5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new extensions to Mobile IP. These\n extensions will facilitate equipment vendors and organizations to\n make specific use of these extensions as they see fit for research or\n deployment purposes.\n\nDommety & Leung Standards Track [Page 1]\n\f\nRFC 3115 Mobile IP Vendor Specific Extensions April 2001\n\n1. Introduction\n\n Current specification of Mobile IP [1] does not allow for\n organizations and vendors to include organization/vendor-specific\n information in the Mobile IP messages. With the imminent wide scale\n deployment of Mobile IP it is useful to have vendor or organization-\n Specific Extensions to support this capability. This document\n defines two extensions that can be used for making organization\n specific extensions by vendors/organizations for their own specific\n purposes.","scope_keywords":["3115","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3115 This document defines two new extensions to Mobile IP. These\n extensions will facilitate equipment vendors and organizations to\n make specific use of these extensions as they see fit for research or\n deployment purposes.\n\nDommety & Leung Standards Track [Page 1]\n\f\nRFC 3115 Mobile IP Vendor Specific Extensions April 2001\n\n1. Introduction\n\n Current specification of Mobile IP [1] does not allow for\n organizations and vendors to include organization/vendor-specific\n information in the Mobile IP messages. With the imminent wide scale\n deployment of Mobile IP it is useful to have vendor or organization-\n Specific Extensions to support this capability. This document\n defines two extensions that can be used for making organization\n specific extensions by vendors/organizations for their own specific\n purposes. 3115 key management nested-reference unchanged"},{"id":"IETF RFC 3122","type":"specification","body":"IETF","designation":"RFC 3122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3122.txt","https://www.rfc-editor.org/rfc/rfc3122.pdf"],"folder":"IETF/RFC-3122","files":{"txt":{"path":"standards/IETF/RFC-3122/RFC-3122.txt","sha256":"6aa6c81075610a614d269ef771e300200e8e3f5f494d56aae83fd7dad2aef0d9"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes extensions to the IPv6 Neighbor Discovery that\n allow a node to determine and advertise an IPv6 address corresponding\n to a given link-layer address. These extensions are called Inverse\n Neighbor Discovery. The Inverse Neighbor Discovery (IND) was\n originally developed for Frame Relay networks, but may also apply to\n other networks with similar behavior.\n\nConta Standards Track [Page 1]\n\f\nRFC 3122 Extensions to IPv6 Neighbor Discovery June 2001","scope_keywords":["3122","authentication","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null}],"search_text":"IETF RFC 3122 This memo describes extensions to the IPv6 Neighbor Discovery that\n allow a node to determine and advertise an IPv6 address corresponding\n to a given link-layer address. These extensions are called Inverse\n Neighbor Discovery. The Inverse Neighbor Discovery (IND) was\n originally developed for Frame Relay networks, but may also apply to\n other networks with similar behavior.\n\nConta Standards Track [Page 1]\n\f\nRFC 3122 Extensions to IPv6 Neighbor Discovery June 2001 3122 authentication key validation nested-reference unchanged"},{"id":"IETF RFC 3232","type":"specification","body":"IETF","designation":"RFC 3232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3232.txt","https://www.rfc-editor.org/rfc/rfc3232.pdf"],"folder":"IETF/RFC-3232","files":{"txt":{"path":"standards/IETF/RFC-3232/RFC-3232.txt","sha256":"d49551669f5caf8d0073de3727fc92480a9dcfc6c2acde59f8eef0eec5f4bfe3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds, Editor\nRequest for Comments: 3232 RFC Editor\nObsoletes: 1700 January 2002\nCategory: Informational\n\n Assigned Numbers: RFC 1700 is Replaced by an On-line Database\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This memo obsoletes RFC 1700 (STD 2) \"Assigned Numbers\", which\n contained an October 1994 snapshot of assigned Internet protocol\n parameters.\n\nDescription\n\n From November 1977 through October 1994, the Internet Assigned\n Numbers Authority (IANA) periodically published tables of the\n Internet protocol parameter assignments in RFCs entitled, \"Assigned\n Numbers\". The most current of these Assigned Numbers RFCs had\n Standard stat","scope_keywords":["3232"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3359","folder":"IETF/RFC-3359","source":"IETF/RFC-3359/RFC-3359.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 3232 Network Working Group J. Reynolds, Editor\nRequest for Comments: 3232 RFC Editor\nObsoletes: 1700 January 2002\nCategory: Informational\n\n Assigned Numbers: RFC 1700 is Replaced by an On-line Database\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This memo obsoletes RFC 1700 (STD 2) \"Assigned Numbers\", which\n contained an October 1994 snapshot of assigned Internet protocol\n parameters.\n\nDescription\n\n From November 1977 through October 1994, the Internet Assigned\n Numbers Authority (IANA) periodically published tables of the\n Internet protocol parameter assignments in RFCs entitled, \"Assigned\n Numbers\". The most current of these Assigned Numbers RFCs had\n Standard stat 3232 nested-reference unchanged"},{"id":"IETF RFC 3309","type":"specification","body":"IETF","designation":"RFC 3309","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3309.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3309.txt","https://www.rfc-editor.org/rfc/rfc3309.pdf"],"folder":"IETF/RFC-3309","files":{"txt":{"path":"standards/IETF/RFC-3309/RFC-3309.txt","sha256":"845ad98eda66159c04e0f7a3e3777465f3c65c66205870ee30c15951c13b4577"}},"tags":["nested-reference","unchanged"],"summary":"Stream Control Transmission Protocol (SCTP) currently uses an Adler-\n 32 checksum. For small packets Adler-32 provides weak detection of\n errors. This document changes that checksum and updates SCTP to use\n a 32 bit CRC checksum.","scope_keywords":["3309","algorithm","key","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null}],"search_text":"IETF RFC 3309 Stream Control Transmission Protocol (SCTP) currently uses an Adler-\n 32 checksum. For small packets Adler-32 provides weak detection of\n errors. This document changes that checksum and updates SCTP to use\n a 32 bit CRC checksum. 3309 algorithm key verifiable nested-reference unchanged"},{"id":"IETF RFC 5226","type":"specification","body":"IETF","designation":"RFC 5226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5226.txt","https://www.rfc-editor.org/rfc/rfc5226.pdf"],"folder":"IETF/RFC-5226","files":{"txt":{"path":"standards/IETF/RFC-5226/RFC-5226.txt","sha256":"6e0ca0a06717a202eafa995ee127054342e300ae3bac75958b8747dd4082490f"}},"tags":["nested-reference","unchanged"],"summary":"Many protocols make use of identifiers consisting of constants and\n other well-known values. Even after a protocol has been defined and\n deployment has begun, new values may need to be assigned (e.g., for a\n new option type in DHCP, or a new encryption or authentication\n transform for IPsec). To ensure that such quantities have consistent\n values and interpretations across all implementations, their\n assignment must be administered by a central authority. For IETF\n protocols, that role is provided by the Internet Assigned Numbers\n Authority (IANA).\n\n In order for IANA to manage a given namespace prudently, it needs\n guidelines describing the conditions under which new values can be\n assigned or when modifications to existing values can be made. If\n IANA is expected to play a role in the management of a namespace,\n IANA must be given clear and concise instructions describing that\n role. T","scope_keywords":["5226","authentication","encryption","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5384","folder":"IETF/RFC-5384","source":"IETF/RFC-5384/RFC-5384.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5431","folder":"IETF/RFC-5431","source":"IETF/RFC-5431/RFC-5431.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5457","folder":"IETF/RFC-5457","source":"IETF/RFC-5457/RFC-5457.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5513","folder":"IETF/RFC-5513","source":"IETF/RFC-5513/RFC-5513.txt","version":null},{"body":"IETF","designation":"RFC 5516","folder":"IETF/RFC-5516","source":"IETF/RFC-5516/RFC-5516.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5668","folder":"IETF/RFC-5668","source":"IETF/RFC-5668/RFC-5668.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5701","folder":"IETF/RFC-5701","source":"IETF/RFC-5701/RFC-5701.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5719","folder":"IETF/RFC-5719","source":"IETF/RFC-5719/RFC-5719.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5736","folder":"IETF/RFC-5736","source":"IETF/RFC-5736/RFC-5736.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5871","folder":"IETF/RFC-5871","source":"IETF/RFC-5871/RFC-5871.txt","version":null},{"body":"IETF","designation":"RFC 5872","folder":"IETF/RFC-5872","source":"IETF/RFC-5872/RFC-5872.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6212","folder":"IETF/RFC-6212","source":"IETF/RFC-6212/RFC-6212.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6685","folder":"IETF/RFC-6685","source":"IETF/RFC-6685/RFC-6685.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6694","folder":"IETF/RFC-6694","source":"IETF/RFC-6694/RFC-6694.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6755","folder":"IETF/RFC-6755","source":"IETF/RFC-6755/RFC-6755.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 7120","folder":"IETF/RFC-7120","source":"IETF/RFC-7120/RFC-7120.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7319","folder":"IETF/RFC-7319","source":"IETF/RFC-7319/RFC-7319.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7346","folder":"IETF/RFC-7346","source":"IETF/RFC-7346/RFC-7346.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 5226 Many protocols make use of identifiers consisting of constants and\n other well-known values. Even after a protocol has been defined and\n deployment has begun, new values may need to be assigned (e.g., for a\n new option type in DHCP, or a new encryption or authentication\n transform for IPsec). To ensure that such quantities have consistent\n values and interpretations across all implementations, their\n assignment must be administered by a central authority. For IETF\n protocols, that role is provided by the Internet Assigned Numbers\n Authority (IANA).\n\n In order for IANA to manage a given namespace prudently, it needs\n guidelines describing the conditions under which new values can be\n assigned or when modifications to existing values can be made. If\n IANA is expected to play a role in the management of a namespace,\n IANA must be given clear and concise instructions describing that\n role. T 5226 authentication encryption key management policy nested-reference unchanged"},{"id":"IETF RFC 5251","type":"specification","body":"IETF","designation":"RFC 5251","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5251.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5251.txt","https://www.rfc-editor.org/rfc/rfc5251.pdf"],"folder":"IETF/RFC-5251","files":{"txt":{"path":"standards/IETF/RFC-5251/RFC-5251.txt","sha256":"3e758796949f17a33921139f8d22b7e836c56d910f96d0641568ed7de386abc6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Basic Mode of Layer 1 VPNs (L1VPNs).\n L1VPN Basic Mode (L1VPN BM) is a port-based VPN. In L1VPN Basic\n Mode, the basic unit of service is a Label Switched Path (LSP)\n between a pair of customer ports within a given VPN port topology.\n This document defines the operational model using either provisioning\n or a VPN auto-discovery mechanism, and the signaling extensions for\n the L1VPN BM.\n\nFedyk, et al. Standards Track [Page 1]\n\f\nRFC 5251 L1VPN Basic Mode July 2008","scope_keywords":["5251","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 5251 This document describes the Basic Mode of Layer 1 VPNs (L1VPNs).\n L1VPN Basic Mode (L1VPN BM) is a port-based VPN. In L1VPN Basic\n Mode, the basic unit of service is a Label Switched Path (LSP)\n between a pair of customer ports within a given VPN port topology.\n This document defines the operational model using either provisioning\n or a VPN auto-discovery mechanism, and the signaling extensions for\n the L1VPN BM.\n\nFedyk, et al. Standards Track [Page 1]\n\f\nRFC 5251 L1VPN Basic Mode July 2008 5251 key path nested-reference unchanged"},{"id":"IETF RFC 8349","type":"specification","body":"IETF","designation":"RFC 8349","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8349.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8349.txt","https://www.rfc-editor.org/rfc/rfc8349.pdf"],"folder":"IETF/RFC-8349","files":{"txt":{"path":"standards/IETF/RFC-8349/RFC-8349.txt","sha256":"e76f1862ee5c797b6cdbf889a1b77b2a5de8e6b333432ee9ed17c2aa6ed107ec"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies three YANG modules and one submodule.\n Together, they form the core routing data model that serves as a\n framework for configuring and managing a routing subsystem. It is\n expected that these modules will be augmented by additional YANG\n modules defining data models for control-plane protocols, route\n filters, and other functions. The core routing data model provides\n common building blocks for such extensions -- routes, Routing\n Information Bases (RIBs), and control-plane protocols.\n\n The YANG modules in this document conform to the Network Management\n Datastore Architecture (NMDA). This document obsoletes RFC 8022.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved f","scope_keywords":["8349","http","https","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 8349 This document specifies three YANG modules and one submodule.\n Together, they form the core routing data model that serves as a\n framework for configuring and managing a routing subsystem. It is\n expected that these modules will be augmented by additional YANG\n modules defining data models for control-plane protocols, route\n filters, and other functions. The core routing data model provides\n common building blocks for such extensions -- routes, Routing\n Information Bases (RIBs), and control-plane protocols.\n\n The YANG modules in this document conform to the Network Management\n Datastore Architecture (NMDA). This document obsoletes RFC 8022.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved f 8349 http https key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1702","type":"specification","body":"IETF","designation":"RFC 1702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1702.txt","https://www.rfc-editor.org/rfc/rfc1702.pdf"],"folder":"IETF/RFC-1702","files":{"txt":{"path":"standards/IETF/RFC-1702/RFC-1702.txt","sha256":"dbcb100d698b4ff6717e9c4a8f3e985a024892b4b09a1caac3f4b89b28a20083"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Hanks\nRequest for Comments: 1702 NetSmiths, Ltd.\nCategory: Informational T. Li\n D. Farinacci\n P. Traina\n cisco Systems\n October 1994\n\n Generic Routing Encapsulation over IPv4 networks\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n In an earlier memo [RFC 1701], we described GRE, a mechanism for\n encapsulating arbitrary packets within an arbitrary transport\n protocol. This is a companion memo which describes the use of GRE\n with IP. This memo addresses the case of using IP as the delivery\n protocol or the payload protocol and the special case of IP as both\n the delivery and payload. This memo also describes using IP\n addresses and autonomous system numbers as part of a GRE source\n route.\n\nIP as a delivery protoco","scope_keywords":["1702","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 2072","folder":"IETF/RFC-2072","source":"IETF/RFC-2072/RFC-2072.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 1702 Network Working Group S. Hanks\nRequest for Comments: 1702 NetSmiths, Ltd.\nCategory: Informational T. Li\n D. Farinacci\n P. Traina\n cisco Systems\n October 1994\n\n Generic Routing Encapsulation over IPv4 networks\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nIntroduction\n\n In an earlier memo [RFC 1701], we described GRE, a mechanism for\n encapsulating arbitrary packets within an arbitrary transport\n protocol. This is a companion memo which describes the use of GRE\n with IP. This memo addresses the case of using IP as the delivery\n protocol or the payload protocol and the special case of IP as both\n the delivery and payload. This memo also describes using IP\n addresses and autonomous system numbers as part of a GRE source\n route.\n\nIP as a delivery protoco 1702 delivery nested-reference unchanged"},{"id":"IETF RFC 2746","type":"specification","body":"IETF","designation":"RFC 2746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2746.txt","https://www.rfc-editor.org/rfc/rfc2746.pdf"],"folder":"IETF/RFC-2746","files":{"txt":{"path":"standards/IETF/RFC-2746/RFC-2746.txt","sha256":"03860dff8182ff085837898bc696dd859940f647339ab76b6289fbe44955d8c2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an approach for providing RSVP protocol\n services over IP tunnels. We briefly describe the problem, the\n characteristics of possible solutions, and the design goals of our\n approach. We then present the details of an implementation which\n meets our design goals.\n\n1. Introduction\n\n IP-in-IP \"tunnels\" have become a widespread mechanism to transport\n datagrams in the Internet. Typically, a tunnel is used to route\n packets through portions of the network which do not directly\n implement the desired service (e.g. IPv6), or to augment and modify\n the behavior of the deployed routing architecture (e.g. multicast\n routing, mobile IP, Virtual Private Net).\n\n Many IP-in-IP tunneling protocols exist today. [IP4INIP4] details a\n method of tunneling using an additional IPv4 header. [MINENC]\n describes a way to reduce the size of the \"inner\" IP header used in\n [IP4INIP4] when t","scope_keywords":["2746","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2745","folder":"IETF/RFC-2745","source":"IETF/RFC-2745/RFC-2745.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null}],"search_text":"IETF RFC 2746 This document describes an approach for providing RSVP protocol\n services over IP tunnels. We briefly describe the problem, the\n characteristics of possible solutions, and the design goals of our\n approach. We then present the details of an implementation which\n meets our design goals.\n\n1. Introduction\n\n IP-in-IP \"tunnels\" have become a widespread mechanism to transport\n datagrams in the Internet. Typically, a tunnel is used to route\n packets through portions of the network which do not directly\n implement the desired service (e.g. IPv6), or to augment and modify\n the behavior of the deployed routing architecture (e.g. multicast\n routing, mobile IP, Virtual Private Net).\n\n Many IP-in-IP tunneling protocols exist today. [IP4INIP4] details a\n method of tunneling using an additional IPv4 header. [MINENC]\n describes a way to reduce the size of the \"inner\" IP header used in\n [IP4INIP4] when t 2746 delivery key path nested-reference unchanged"},{"id":"IETF RFC 2890","type":"specification","body":"IETF","designation":"RFC 2890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2890.txt","https://www.rfc-editor.org/rfc/rfc2890.pdf"],"folder":"IETF/RFC-2890","files":{"txt":{"path":"standards/IETF/RFC-2890/RFC-2890.txt","sha256":"96bdafc03219df215342d9b9d127ba87d7aaf2f2130797035ac3c17f07115455"}},"tags":["nested-reference","unchanged"],"summary":"GRE (Generic Routing Encapsulation) specifies a protocol for\n encapsulation of an arbitrary protocol over another arbitrary network\n layer protocol. This document describes extensions by which two\n fields, Key and Sequence Number, can be optionally carried in the GRE\n Header [1].\n\n1. Introduction\n\n The current specification of Generic Routing Encapsulation [1]\n specifies a protocol for encapsulation of an arbitrary protocol over\n another arbitrary network layer protocol. This document describes\n enhancements by which two fields, Key and Sequence Number, can be\n optionally carried in the GRE Header [1]. The Key field is intended\n to be used for identifying an individual traffic flow within a\n tunnel. The Sequence Number field is used to maintain sequence of\n packets within the GRE Tunnel.","scope_keywords":["2890","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5640","folder":"IETF/RFC-5640","source":"IETF/RFC-5640/RFC-5640.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null}],"search_text":"IETF RFC 2890 GRE (Generic Routing Encapsulation) specifies a protocol for\n encapsulation of an arbitrary protocol over another arbitrary network\n layer protocol. This document describes extensions by which two\n fields, Key and Sequence Number, can be optionally carried in the GRE\n Header [1].\n\n1. Introduction\n\n The current specification of Generic Routing Encapsulation [1]\n specifies a protocol for encapsulation of an arbitrary protocol over\n another arbitrary network layer protocol. This document describes\n enhancements by which two fields, Key and Sequence Number, can be\n optionally carried in the GRE Header [1]. The Key field is intended\n to be used for identifying an individual traffic flow within a\n tunnel. The Sequence Number field is used to maintain sequence of\n packets within the GRE Tunnel. 2890 delivery key nested-reference unchanged"},{"id":"IETF RFC 3519","type":"specification","body":"IETF","designation":"RFC 3519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3519.txt","https://www.rfc-editor.org/rfc/rfc3519.pdf"],"folder":"IETF/RFC-3519","files":{"txt":{"path":"standards/IETF/RFC-3519/RFC-3519.txt","sha256":"10bcd265912e14515bbaa3c18fab6e4ac763d38deaf9d0b905517426baa1cd25"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP's datagram tunnelling is incompatible with Network Address\n Translation (NAT). This document presents extensions to the Mobile\n IP protocol and a tunnelling method which permits mobile nodes using\n Mobile IP to operate in private address networks which are separated\n from the public internet by NAT devices. The NAT traversal is based\n on using the Mobile IP Home Agent UDP port for encapsulated data\n traffic.","scope_keywords":["3519","key","seal"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3519 Mobile IP's datagram tunnelling is incompatible with Network Address\n Translation (NAT). This document presents extensions to the Mobile\n IP protocol and a tunnelling method which permits mobile nodes using\n Mobile IP to operate in private address networks which are separated\n from the public internet by NAT devices. The NAT traversal is based\n on using the Mobile IP Home Agent UDP port for encapsulated data\n traffic. 3519 key seal nested-reference unchanged"},{"id":"IETF RFC 5975","type":"specification","body":"IETF","designation":"RFC 5975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5975.txt","https://www.rfc-editor.org/rfc/rfc5975.pdf"],"folder":"IETF/RFC-5975","files":{"txt":{"path":"standards/IETF/RFC-5975/RFC-5975.txt","sha256":"abdf460acfaf3a243060e14d070a86f920e0e20e83f3f9635fe98c77ede07843"}},"tags":["nested-reference","unchanged"],"summary":"The Quality-of-Service (QoS) NSIS signaling layer protocol (NSLP) is\n used to signal QoS reservations and is independent of a specific QoS\n model (QOSM) such as IntServ or Diffserv. Rather, all information\n specific to a QOSM is encapsulated in a separate object, the QSPEC.\n This document defines a template for the QSPEC including a number of\n QSPEC parameters. The QSPEC parameters provide a common language to\n be reused in several QOSMs and thereby aim to ensure the\n extensibility and interoperability of QoS NSLP. While the base\n protocol is QOSM-agnostic, the parameters that can be carried in the\n QSPEC object are possibly closely coupled to specific models. The\n node initiating the NSIS signaling adds an Initiator QSPEC, which\n indicates the QSPEC parameters that must be interpreted by the\n downstream nodes less the reservation fails, thereby ensuring the\n intention of the NSIS initia","scope_keywords":["5975","http","license","path","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 5975 The Quality-of-Service (QoS) NSIS signaling layer protocol (NSLP) is\n used to signal QoS reservations and is independent of a specific QoS\n model (QOSM) such as IntServ or Diffserv. Rather, all information\n specific to a QOSM is encapsulated in a separate object, the QSPEC.\n This document defines a template for the QSPEC including a number of\n QSPEC parameters. The QSPEC parameters provide a common language to\n be reused in several QOSMs and thereby aim to ensure the\n extensibility and interoperability of QoS NSLP. While the base\n protocol is QOSM-agnostic, the parameters that can be carried in the\n QSPEC object are possibly closely coupled to specific models. The\n node initiating the NSIS signaling adds an Initiator QSPEC, which\n indicates the QSPEC parameters that must be interpreted by the\n downstream nodes less the reservation fails, thereby ensuring the\n intention of the NSIS initia 5975 http license path subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 2595","type":"specification","body":"IETF","designation":"RFC 2595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2595.txt","https://www.rfc-editor.org/rfc/rfc2595.pdf"],"folder":"IETF/RFC-2595","files":{"txt":{"path":"standards/IETF/RFC-2595/RFC-2595.txt","sha256":"5d644cd1053214b5f2a75584efedb16acac07472b099496562fbfe574c2d775b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Newman\nRequest for Comments: 2595 Innosoft\nCategory: Standards Track June 1999\n\n Using TLS with IMAP, POP3 and ACAP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Motivation\n\n The TLS protocol (formerly known as SSL) provides a way to secure an\n application protocol from tampering and eavesdropping. The option of\n using such security is desirable for IMAP, POP and ACAP due to common\n connection eavesdropping and hijacking attacks [AUTH]. Although\n advanced SASL authe","scope_keywords":["2595","authentication","certificate","crl","encryption","key","policy","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2595 Network Working Group C. Newman\nRequest for Comments: 2595 Innosoft\nCategory: Standards Track June 1999\n\n Using TLS with IMAP, POP3 and ACAP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Motivation\n\n The TLS protocol (formerly known as SSL) provides a way to secure an\n application protocol from tampering and eavesdropping. The option of\n using such security is desirable for IMAP, POP and ACAP due to common\n connection eavesdropping and hijacking attacks [AUTH]. Although\n advanced SASL authe 2595 authentication certificate crl encryption key policy subject tls nested-reference unchanged"},{"id":"IETF RFC 4643","type":"specification","body":"IETF","designation":"RFC 4643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4643.txt","https://www.rfc-editor.org/rfc/rfc4643.pdf"],"folder":"IETF/RFC-4643","files":{"txt":{"path":"standards/IETF/RFC-4643/RFC-4643.txt","sha256":"e68fa965e1b50b154ce807edfabe1a35ea97e2d9371cc4832602be69e5507126"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Network News Transfer\n Protocol (NNTP) that allows a client to indicate an authentication\n mechanism to the server, to perform an authentication protocol\n exchange, and optionally to negotiate a security layer for subsequent\n protocol interactions during the remainder of an NNTP session.\n\n This document updates and formalizes the AUTHINFO USER/PASS\n authentication method specified in RFC 2980 and deprecates the\n AUTHINFO SIMPLE and AUTHINFO GENERIC authentication methods.\n Additionally, this document defines a profile of the Simple\n Authentication and Security Layer (SASL) for NNTP.\n\nVinocur, et al. Standards Track [Page 1]\n\f\nRFC 4643 NNTP Authentication October 2006","scope_keywords":["4643","authentication","authorization","encryption","key","policy","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 4643 This document defines an extension to the Network News Transfer\n Protocol (NNTP) that allows a client to indicate an authentication\n mechanism to the server, to perform an authentication protocol\n exchange, and optionally to negotiate a security layer for subsequent\n protocol interactions during the remainder of an NNTP session.\n\n This document updates and formalizes the AUTHINFO USER/PASS\n authentication method specified in RFC 2980 and deprecates the\n AUTHINFO SIMPLE and AUTHINFO GENERIC authentication methods.\n Additionally, this document defines a profile of the Simple\n Authentication and Security Layer (SASL) for NNTP.\n\nVinocur, et al. Standards Track [Page 1]\n\f\nRFC 4643 NNTP Authentication October 2006 4643 authentication authorization encryption key policy profile tls nested-reference unchanged"},{"id":"IETF RFC 5709","type":"specification","body":"IETF","designation":"RFC 5709","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5709.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5709.txt","https://www.rfc-editor.org/rfc/rfc5709.pdf"],"folder":"IETF/RFC-5709","files":{"txt":{"path":"standards/IETF/RFC-5709/RFC-5709.txt","sha256":"07dfeee7b7aaefadcde2c7ef39a2bbe14bd42203b97d02b286db4aafee6212c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the National Institute of Standards and\n Technology (NIST) Secure Hash Standard family of algorithms can be\n used with OSPF version 2's built-in, cryptographic authentication\n mechanism. This updates, but does not supercede, the cryptographic\n authentication mechanism specified in RFC 2328.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relat","scope_keywords":["5709","algorithm","algorithms","authentication","hash","http","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null}],"search_text":"IETF RFC 5709 This document describes how the National Institute of Standards and\n Technology (NIST) Secure Hash Standard family of algorithms can be\n used with OSPF version 2's built-in, cryptographic authentication\n mechanism. This updates, but does not supercede, the cryptographic\n authentication mechanism specified in RFC 2328.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relat 5709 algorithm algorithms authentication hash http key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 171","type":"specification","body":"IETF","designation":"RFC 171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc171.txt","https://www.rfc-editor.org/rfc/rfc171.pdf"],"folder":"IETF/RFC-171","files":{"txt":{"path":"standards/IETF/RFC-171/RFC-171.txt","sha256":"2b5b6e4694174696fc19aef14c361e87dcf3ea67bea04a1173ce7038a0f07251"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Abhay Bhushan\nRequest for Comments: 171 MIT\nNIC 6793 Bob Braden\nCategories: D.4, D.5, and D.7 UCLA\nUpdates: 114 Will Crowther\nObsolete: None Alex McKenzie\n BBN\n Eric Harslem\n John Heafner\n Rand\n John Melvin\n Dick Watson\n SRI\n Bob Sundberg\n HARVARD\n Jim White\n UCSB\n 23 June 1971\n\n THE DATA TRANSFER PROTOCOL\n\nI. INTRODUCTION\n\n A common protocol is desirable for data transfer in such diverse\n applications as remote job entry, file transfer, network mail system,\n graphics, remote program execution, and communication with block data\n terminals (such as printers, card, paper tape, and magnetic tape\n equipment, especially in context of terminal IMPs). Although it\n would be possible to include some or even all of the above\n applications in an all-inclusive file transfer protocol, a separation\n between data transfer and application functions would provide\n flexibility in imp","scope_keywords":["171"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 172","folder":"IETF/RFC-172","source":"IETF/RFC-172/RFC-172.txt","version":null},{"body":"IETF","designation":"RFC 196","folder":"IETF/RFC-196","source":"IETF/RFC-196/RFC-196.txt","version":null},{"body":"IETF","designation":"RFC 264","folder":"IETF/RFC-264","source":"IETF/RFC-264/RFC-264.txt","version":null}],"search_text":"IETF RFC 171 Network Working Group Abhay Bhushan\nRequest for Comments: 171 MIT\nNIC 6793 Bob Braden\nCategories: D.4, D.5, and D.7 UCLA\nUpdates: 114 Will Crowther\nObsolete: None Alex McKenzie\n BBN\n Eric Harslem\n John Heafner\n Rand\n John Melvin\n Dick Watson\n SRI\n Bob Sundberg\n HARVARD\n Jim White\n UCSB\n 23 June 1971\n\n THE DATA TRANSFER PROTOCOL\n\nI. INTRODUCTION\n\n A common protocol is desirable for data transfer in such diverse\n applications as remote job entry, file transfer, network mail system,\n graphics, remote program execution, and communication with block data\n terminals (such as printers, card, paper tape, and magnetic tape\n equipment, especially in context of terminal IMPs). Although it\n would be possible to include some or even all of the above\n applications in an all-inclusive file transfer protocol, a separation\n between data transfer and application functions would provide\n flexibility in imp 171 nested-reference unchanged"},{"id":"IETF RFC 3825","type":"specification","body":"IETF","designation":"RFC 3825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3825.txt","https://www.rfc-editor.org/rfc/rfc3825.pdf"],"folder":"IETF/RFC-3825","files":{"txt":{"path":"standards/IETF/RFC-3825/RFC-3825.txt","sha256":"0fceed7f12f8f3f223690c29594a783586865244f7c42573d9c79f330cea07ba"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Dynamic Host Configuration Protocol Option\n for the coordinate-based geographic location of the client. The\n Location Configuration Information (LCI) includes latitude,\n longitude, and altitude, with resolution indicators for each. The\n reference datum for these values is also included.\n\nPolk, et al. Standards Track [Page 1]\n\f\nRFC 3825 DHCP Option for Coordinate LCI July 2004","scope_keywords":["3825","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null}],"search_text":"IETF RFC 3825 This document specifies a Dynamic Host Configuration Protocol Option\n for the coordinate-based geographic location of the client. The\n Location Configuration Information (LCI) includes latitude,\n longitude, and altitude, with resolution indicators for each. The\n reference datum for these values is also included.\n\nPolk, et al. Standards Track [Page 1]\n\f\nRFC 3825 DHCP Option for Coordinate LCI July 2004 3825 key policy nested-reference unchanged"},{"id":"IETF RFC 3177","type":"specification","body":"IETF","designation":"RFC 3177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3177.txt","https://www.rfc-editor.org/rfc/rfc3177.pdf"],"folder":"IETF/RFC-3177","files":{"txt":{"path":"standards/IETF/RFC-3177/RFC-3177.txt","sha256":"9edcf5c4be34ede656d3608d6b0bfcb5ab0cee8a797c6249ad2b120decedbba7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group IAB\nRequest for Comments: 3177 IESG\nCategory: Informational September 2001\n\n IAB/IESG Recommendations on IPv6 Address Allocations to Sites\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document provides recommendations to the addressing registries\n (APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address\n blocks to end sites. In particular, it recommends the assignment of\n /48 in the general case, /64 when it is known that one and only one\n subnet is needed and /128 when it is absolutely known that one and\n only one device is connecting.\n\n The original recommendations were made in an IAB/IESG statement\n mailed to the registries ","scope_keywords":["3177","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3587","folder":"IETF/RFC-3587","source":"IETF/RFC-3587/RFC-3587.txt","version":null},{"body":"IETF","designation":"RFC 3769","folder":"IETF/RFC-3769","source":"IETF/RFC-3769/RFC-3769.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4692","folder":"IETF/RFC-4692","source":"IETF/RFC-4692/RFC-4692.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6177","folder":"IETF/RFC-6177","source":"IETF/RFC-6177/RFC-6177.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null}],"search_text":"IETF RFC 3177 Network Working Group IAB\nRequest for Comments: 3177 IESG\nCategory: Informational September 2001\n\n IAB/IESG Recommendations on IPv6 Address Allocations to Sites\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document provides recommendations to the addressing registries\n (APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address\n blocks to end sites. In particular, it recommends the assignment of\n /48 in the general case, /64 when it is known that one and only one\n subnet is needed and /128 when it is absolutely known that one and\n only one device is connecting.\n\n The original recommendations were made in an IAB/IESG statement\n mailed to the registries  3177 policies policy nested-reference unchanged"},{"id":"IETF RFC 3194","type":"specification","body":"IETF","designation":"RFC 3194","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3194.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3194.txt","https://www.rfc-editor.org/rfc/rfc3194.pdf"],"folder":"IETF/RFC-3194","files":{"txt":{"path":"standards/IETF/RFC-3194/RFC-3194.txt","sha256":"a3bba6484012a2b5f9b904ef8991d2efb62266890c106de5364ce091b76577b4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Durand\nRequest for Comments: 3194 SUN Microsystems\nUpdates: 1715 C. Huitema\nCategory: Informational Microsoft\n November 2001\n\n The Host-Density Ratio for Address Assignment Efficiency:\n An update on the H ratio\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document provides an update on the \"H ratio\" defined in RFC\n 1715. It defines a new ratio which the authors claim is easier to\n understand.\n\n1. Evaluating the efficiency of address allocation\n\n A naive observer might assume that the number of addressable objects\n in an addressing plan is a linear function of the size of the\n address. If this were true, a telephone numbering plan bas","scope_keywords":["3194","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 4692","folder":"IETF/RFC-4692","source":"IETF/RFC-4692/RFC-4692.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null}],"search_text":"IETF RFC 3194 Network Working Group A. Durand\nRequest for Comments: 3194 SUN Microsystems\nUpdates: 1715 C. Huitema\nCategory: Informational Microsoft\n November 2001\n\n The Host-Density Ratio for Address Assignment Efficiency:\n An update on the H ratio\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document provides an update on the \"H ratio\" defined in RFC\n 1715. It defines a new ratio which the authors claim is easier to\n understand.\n\n1. Evaluating the efficiency of address allocation\n\n A naive observer might assume that the number of addressable objects\n in an addressing plan is a linear function of the size of the\n address. If this were true, a telephone numbering plan bas 3194 policies nested-reference unchanged"},{"id":"IETF RFC 4692","type":"specification","body":"IETF","designation":"RFC 4692","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4692.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4692.txt","https://www.rfc-editor.org/rfc/rfc4692.pdf"],"folder":"IETF/RFC-4692","files":{"txt":{"path":"standards/IETF/RFC-4692/RFC-4692.txt","sha256":"6144ac7e0aae4878c1f38aa06a17986e763de2a159dd9e9c9fc28f778adf375d"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides an analysis of the Host Density metric as it is\n currently used to guide registry allocations of IPv6 unicast address\n blocks. This document contrasts the address efficiency as currently\n adopted in the allocation of IPv4 network addresses and that used by\n the IPv6 protocol. Note that for large allocations there are very\n significant variations in the target efficiency metric between the\n two approaches.","scope_keywords":["4692","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 4692 This memo provides an analysis of the Host Density metric as it is\n currently used to guide registry allocations of IPv6 unicast address\n blocks. This document contrasts the address efficiency as currently\n adopted in the allocation of IPv4 network addresses and that used by\n the IPv6 protocol. Note that for large allocations there are very\n significant variations in the target efficiency metric between the\n two approaches. 4692 policy nested-reference unchanged"},{"id":"IETF RFC 1727","type":"specification","body":"IETF","designation":"RFC 1727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1727.txt","https://www.rfc-editor.org/rfc/rfc1727.pdf"],"folder":"IETF/RFC-1727","files":{"txt":{"path":"standards/IETF/RFC-1727/RFC-1727.txt","sha256":"8feb11caa500f2f251810623a6e4e80980f2c0c4d5761e0b9ca437df403094a7"}},"tags":["nested-reference","unchanged"],"summary":"This paper lays out a vision of how Internet information services\n might be integrated over the next few years, and discusses in some\n detail what steps will be needed to achieve this integration.\n\nAcknowledgments\n\n Thanks to the whole gang of information service wonks who have\n wrangled with us about the future of information services in\n countless bar bofs (in no particular order): Cliff Lynch, Cliff\n Neuman, Alan Emtage, Jim Fullton, Joan Gargano, Mike Schwartz, John\n Kunze, Janet Vratny, Mark McCahill, Tim Berners-Lee, John Curran,\n Jill Foster, and many others. Extra special thanks to George Brett of\n CNIDR and Anders Gillner of RARE, who have given us the opportunity\n to start tying together the networking community and the librarian\n community.\n\n1. Disclaimer\n\n This paper represents only the opinions of its authors; it is not an\n official policy statement of the IIIR Working Group","scope_keywords":["1727","delivery","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1835","folder":"IETF/RFC-1835","source":"IETF/RFC-1835/RFC-1835.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null}],"search_text":"IETF RFC 1727 This paper lays out a vision of how Internet information services\n might be integrated over the next few years, and discusses in some\n detail what steps will be needed to achieve this integration.\n\nAcknowledgments\n\n Thanks to the whole gang of information service wonks who have\n wrangled with us about the future of information services in\n countless bar bofs (in no particular order): Cliff Lynch, Cliff\n Neuman, Alan Emtage, Jim Fullton, Joan Gargano, Mike Schwartz, John\n Kunze, Janet Vratny, Mark McCahill, Tim Berners-Lee, John Curran,\n Jill Foster, and many others. Extra special thanks to George Brett of\n CNIDR and Anders Gillner of RARE, who have given us the opportunity\n to start tying together the networking community and the librarian\n community.\n\n1. Disclaimer\n\n This paper represents only the opinions of its authors; it is not an\n official policy statement of the IIIR Working Group 1727 delivery key policy nested-reference unchanged"},{"id":"IETF RFC 1835","type":"specification","body":"IETF","designation":"RFC 1835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1835.txt","https://www.rfc-editor.org/rfc/rfc1835.pdf"],"folder":"IETF/RFC-1835","files":{"txt":{"path":"standards/IETF/RFC-1835/RFC-1835.txt","sha256":"1dec8a4a565bd7d70c99cfc2a38d0e51e4b38a9d7a0057ed9a63ac71924bbca7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes WHOIS++, an extension to the trivial WHOIS\n service described in RFC 954 to permit WHOIS-like servers to make\n available more structured information to the Internet. We describe\n an extension to the simple WHOIS data model and query protocol and a\n companion extensible, distributed indexing service. A number of\n options have also been added such as the use of multiple languages\n and character sets, more advanced search expressions, structured data\n and a number of other useful features. An optional authentication\n mechanism for protecting all or part of the associated WHOIS++\n information database from unauthorized access is also described.","scope_keywords":["1835","authentication","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1913","folder":"IETF/RFC-1913","source":"IETF/RFC-1913/RFC-1913.txt","version":null},{"body":"IETF","designation":"RFC 1914","folder":"IETF/RFC-1914","source":"IETF/RFC-1914/RFC-1914.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1835 This document describes WHOIS++, an extension to the trivial WHOIS\n service described in RFC 954 to permit WHOIS-like servers to make\n available more structured information to the Internet. We describe\n an extension to the simple WHOIS data model and query protocol and a\n companion extensible, distributed indexing service. A number of\n options have also been added such as the use of multiple languages\n and character sets, more advanced search expressions, structured data\n and a number of other useful features. An optional authentication\n mechanism for protecting all or part of the associated WHOIS++\n information database from unauthorized access is also described. 1835 authentication registered nested-reference unchanged"},{"id":"IETF RFC 2957","type":"specification","body":"IETF","designation":"RFC 2957","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2957.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2957.txt","https://www.rfc-editor.org/rfc/rfc2957.pdf"],"folder":"IETF/RFC-2957","files":{"txt":{"path":"standards/IETF/RFC-2957/RFC-2957.txt","sha256":"015eabac1b4223bc224b669b00945af57cf01ab3c4c76c92bf5df43e7876bf80"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Daigle\nRequest for Comments: 2957 Thinking Cat Enterprises\nCategory: Informational P. Faltstrom\n Cisco Systems Inc.\n October 2000\n\n The application/whoispp-query Content-Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the expression of Whois++ protocol (RFC 1835)\n queries within MIME (Multipurpose Internet Mail Extensions) (RFC\n 2046) media types. The intention of this document, in conjunction\n with RFC 2958 is to enable MIME-enabled mail software, and other\n systems using Internet media types, to carry out Whois++\n transactions.\n\n1. MIME Registration Information\n\n To: iana@isi.edu\n Subject: Registration of MIME me","scope_keywords":["2957","attribute","authentication","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null}],"search_text":"IETF RFC 2957 Network Working Group L. Daigle\nRequest for Comments: 2957 Thinking Cat Enterprises\nCategory: Informational P. Faltstrom\n Cisco Systems Inc.\n October 2000\n\n The application/whoispp-query Content-Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the expression of Whois++ protocol (RFC 1835)\n queries within MIME (Multipurpose Internet Mail Extensions) (RFC\n 2046) media types. The intention of this document, in conjunction\n with RFC 2958 is to enable MIME-enabled mail software, and other\n systems using Internet media types, to carry out Whois++\n transactions.\n\n1. MIME Registration Information\n\n To: iana@isi.edu\n Subject: Registration of MIME me 2957 attribute authentication identification subject nested-reference unchanged"},{"id":"IETF RFC 2958","type":"specification","body":"IETF","designation":"RFC 2958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2958.txt","https://www.rfc-editor.org/rfc/rfc2958.pdf"],"folder":"IETF/RFC-2958","files":{"txt":{"path":"standards/IETF/RFC-2958/RFC-2958.txt","sha256":"549f520e432584392cca83d37df416bfc0829385f6b475f9a12380c57775ae20"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Daigle\nRequest for Comments: 2958 Thinking Cat Enterprises\nCategory: Informational P. Faltstrom\n Cisco Systems Inc.\n October 2000\n\n The application/whoispp-response Content-type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the expression of Whois++ protocol (RFC1835)\n responses within MIME (Multipurpose Internet Mail Extensions)\n (RFC2046) media types. The intention of this document, in\n conjunction with RFC 2957 is to enable MIME-enabled mail software,\n and other systems using Internet media types, to carry out Whois++\n transactions.\n\n1. MIME Registration Information\n\n To: iana@isi.edu Subject: Registration of MIME ","scope_keywords":["2958","attribute","authentication","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null}],"search_text":"IETF RFC 2958 Network Working Group L. Daigle\nRequest for Comments: 2958 Thinking Cat Enterprises\nCategory: Informational P. Faltstrom\n Cisco Systems Inc.\n October 2000\n\n The application/whoispp-response Content-type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines the expression of Whois++ protocol (RFC1835)\n responses within MIME (Multipurpose Internet Mail Extensions)\n (RFC2046) media types. The intention of this document, in\n conjunction with RFC 2957 is to enable MIME-enabled mail software,\n and other systems using Internet media types, to carry out Whois++\n transactions.\n\n1. MIME Registration Information\n\n To: iana@isi.edu Subject: Registration of MIME  2958 attribute authentication identification subject nested-reference unchanged"},{"id":"IETF RFC 1728","type":"specification","body":"IETF","designation":"RFC 1728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1728.txt","https://www.rfc-editor.org/rfc/rfc1728.pdf"],"folder":"IETF/RFC-1728","files":{"txt":{"path":"standards/IETF/RFC-1728/RFC-1728.txt","sha256":"6321fcf31be0dd7e1bb18ad5be360b1e48839b93d002c74fcb6e9c7c231f2732"}},"tags":["nested-reference","unchanged"],"summary":"Although a number of systems have been created in the last several\n years to provide resource location and navigation on the Internet,\n the information contained in these systems must be maintained and\n updated by hand. This paper describes an automatic mechanism, the\n resource transponder, for maintaining resource location information.\n\nAuthor's Note:\n\n This document is being circulated as sort of a research paper;\n consequently there are no protocol specifications or anything of the\n sort. I hope that we can go from here and actually design them if\n there's consensus that they are potentially useful. Once we have some\n idea of the required functionality, we can then go out and\n standardize them.\n\nDisclaimer\n\n This paper represents only the opinions of the author; it does not\n represent the consensus of the IIIR Working Group, although it is\n recognized by them as one legitimate approac","scope_keywords":["1728"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1727","folder":"IETF/RFC-1727","source":"IETF/RFC-1727/RFC-1727.txt","version":null}],"search_text":"IETF RFC 1728 Although a number of systems have been created in the last several\n years to provide resource location and navigation on the Internet,\n the information contained in these systems must be maintained and\n updated by hand. This paper describes an automatic mechanism, the\n resource transponder, for maintaining resource location information.\n\nAuthor's Note:\n\n This document is being circulated as sort of a research paper;\n consequently there are no protocol specifications or anything of the\n sort. I hope that we can go from here and actually design them if\n there's consensus that they are potentially useful. Once we have some\n idea of the required functionality, we can then go out and\n standardize them.\n\nDisclaimer\n\n This paper represents only the opinions of the author; it does not\n represent the consensus of the IIIR Working Group, although it is\n recognized by them as one legitimate approac 1728 nested-reference unchanged"},{"id":"IETF RFC 1729","type":"specification","body":"IETF","designation":"RFC 1729","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1729.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1729.txt","https://www.rfc-editor.org/rfc/rfc1729.pdf"],"folder":"IETF/RFC-1729","files":{"txt":{"path":"standards/IETF/RFC-1729/RFC-1729.txt","sha256":"56aeacaf0bb57f352df94916dbd64f9149623baad6aaf2a531585cb3e52eb84b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Lynch\nRequest for Comments: 1729 University of California\nCategory: Informational Office of the President\n December 1994\n\n Using the Z39.50 Information Retrieval Protocol\n in the Internet Environment\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nSummary\n\n This memo describes an approach to the implementation of the\n ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the\n TCP/IP environment which is currently in wide use by the Z39.50\n implementor community.\n\nIntroduction\n\n Z39.50 is a US national standard defining a protocol for computer-\n to-computer information retrieval that was first adopted in 1988 [1]\n and extensively revised in 1992 [2]. It was developed by the National\n Information Standards Organization (NIS","scope_keywords":["1729","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 1729 Network Working Group C. Lynch\nRequest for Comments: 1729 University of California\nCategory: Informational Office of the President\n December 1994\n\n Using the Z39.50 Information Retrieval Protocol\n in the Internet Environment\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nSummary\n\n This memo describes an approach to the implementation of the\n ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the\n TCP/IP environment which is currently in wide use by the Z39.50\n implementor community.\n\nIntroduction\n\n Z39.50 is a US national standard defining a protocol for computer-\n to-computer information retrieval that was first adopted in 1988 [1]\n and extensively revised in 1992 [2]. It was developed by the National\n Information Standards Organization (NIS 1729 presentation nested-reference unchanged"},{"id":"IETF RFC 2086","type":"specification","body":"IETF","designation":"RFC 2086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2086.txt","https://www.rfc-editor.org/rfc/rfc2086.pdf"],"folder":"IETF/RFC-2086","files":{"txt":{"path":"standards/IETF/RFC-2086/RFC-2086.txt","sha256":"86517ec41106ce386837cd4f32d24ab444931ebaa59bbc1f6298b30bee010c7d"}},"tags":["nested-reference","unchanged"],"summary":"The ACL extension of the Internet Message Access Protocol [IMAP4]\n permits access control lists to be manipulated through the IMAP\n protocol.","scope_keywords":["2086","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 3503","folder":"IETF/RFC-3503","source":"IETF/RFC-3503/RFC-3503.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null}],"search_text":"IETF RFC 2086 The ACL extension of the Internet Message Access Protocol [IMAP4]\n permits access control lists to be manipulated through the IMAP\n protocol. 2086 authentication nested-reference unchanged"},{"id":"IETF RFC 2087","type":"specification","body":"IETF","designation":"RFC 2087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2087.txt","https://www.rfc-editor.org/rfc/rfc2087.pdf"],"folder":"IETF/RFC-2087","files":{"txt":{"path":"standards/IETF/RFC-2087/RFC-2087.txt","sha256":"01ea49d04fdb444bd64c191392e9553ed1dcb028bf672103adf786054da2b458"}},"tags":["nested-reference","unchanged"],"summary":"The QUOTA extension of the Internet Message Access Protocol [IMAP4]\n permits administrative limits on resource usage (quotas) to be\n manipulated through the IMAP protocol.","scope_keywords":["2087"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2087 The QUOTA extension of the Internet Message Access Protocol [IMAP4]\n permits administrative limits on resource usage (quotas) to be\n manipulated through the IMAP protocol. 2087 nested-reference unchanged"},{"id":"IETF RFC 4314","type":"specification","body":"IETF","designation":"RFC 4314","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4314.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4314.txt","https://www.rfc-editor.org/rfc/rfc4314.pdf"],"folder":"IETF/RFC-4314","files":{"txt":{"path":"standards/IETF/RFC-4314/RFC-4314.txt","sha256":"88480c4141ef362ab460fd3eee6a1cbf8fa8d167ad494d162da53d938cb3a25a"}},"tags":["nested-reference","unchanged"],"summary":"The Access Control List (ACL) extension (RFC 2086) of the Internet\n Message Access Protocol (IMAP) permits mailbox access control lists\n to be retrieved and manipulated through the IMAP protocol.\n\n This document is a revision of RFC 2086. It defines several new\n access control rights and clarifies which rights are required for\n different IMAP commands.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 4314 IMAP ACL December 2005","scope_keywords":["4314","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4314 The Access Control List (ACL) extension (RFC 2086) of the Internet\n Message Access Protocol (IMAP) permits mailbox access control lists\n to be retrieved and manipulated through the IMAP protocol.\n\n This document is a revision of RFC 2086. It defines several new\n access control rights and clarifies which rights are required for\n different IMAP commands.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 4314 IMAP ACL December 2005 4314 authentication key management nested-reference unchanged"},{"id":"IETF RFC 1734","type":"specification","body":"IETF","designation":"RFC 1734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1734.txt","https://www.rfc-editor.org/rfc/rfc1734.pdf"],"folder":"IETF/RFC-1734","files":{"txt":{"path":"standards/IETF/RFC-1734/RFC-1734.txt","sha256":"5a1a0ece016e884cdf2af32ddc38adf114ace0ddaa303fc41c43b6fc53e02b07"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 1734 Carnegie Mellon\nCategory: Standards Track December 1994\n\n POP3 AUTHentication command\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This document describes the optional AUTH command, for indicating an\n authentication mechanism to the server, performing an authentication\n protocol exchange, and optionally negotiating a protection mechanism\n for subsequent protocol interactions. The authentication and\n protection mechanisms used by the POP3 AUTH command are those used by\n IMAP4.\n\n2. The AUTH command\n\n A","scope_keywords":["1734","authentication","authorization","crl","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null}],"search_text":"IETF RFC 1734 Network Working Group J. Myers\nRequest for Comments: 1734 Carnegie Mellon\nCategory: Standards Track December 1994\n\n POP3 AUTHentication command\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n This document describes the optional AUTH command, for indicating an\n authentication mechanism to the server, performing an authentication\n protocol exchange, and optionally negotiating a protection mechanism\n for subsequent protocol interactions. The authentication and\n protection mechanisms used by the POP3 AUTH command are those used by\n IMAP4.\n\n2. The AUTH command\n\n A 1734 authentication authorization crl tls nested-reference unchanged"},{"id":"IETF RFC 2192","type":"specification","body":"IETF","designation":"RFC 2192","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2192.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2192.txt","https://www.rfc-editor.org/rfc/rfc2192.pdf"],"folder":"IETF/RFC-2192","files":{"txt":{"path":"standards/IETF/RFC-2192/RFC-2192.txt","sha256":"14ede9372cb2582764f71fe09ebf7ee50110db3c3435a110cb7872e547a422a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Newman\nRequest for Comments: 2192 Innosoft\nCategory: Standards Track September 1997\n\n IMAP URL Scheme\n\nStatus of this memo\n\n This document specifies an Internet standards track protocol for\n the Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is\n unlimited.\n\nAbstract\n\n IMAP [IMAP4] is a rich protocol for accessing remote message\n stores. It provides an ideal mechanism for accessing public\n mailing list archives as well as private and shared message stores.\n This document defines a URL scheme for referencing objects on an\n IMAP server.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document ","scope_keywords":["2192","authentication","credential","credentials","encryption","key","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2193","folder":"IETF/RFC-2193","source":"IETF/RFC-2193/RFC-2193.txt","version":null},{"body":"IETF","designation":"RFC 2221","folder":"IETF/RFC-2221","source":"IETF/RFC-2221/RFC-2221.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2342","folder":"IETF/RFC-2342","source":"IETF/RFC-2342/RFC-2342.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null}],"search_text":"IETF RFC 2192 Network Working Group C. Newman\nRequest for Comments: 2192 Innosoft\nCategory: Standards Track September 1997\n\n IMAP URL Scheme\n\nStatus of this memo\n\n This document specifies an Internet standards track protocol for\n the Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is\n unlimited.\n\nAbstract\n\n IMAP [IMAP4] is a rich protocol for accessing remote message\n stores. It provides an ideal mechanism for accessing public\n mailing list archives as well as private and shared message stores.\n This document defines a URL scheme for referencing objects on an\n IMAP server.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document  2192 authentication credential credentials encryption key policy trust nested-reference unchanged"},{"id":"IETF RFC 4549","type":"specification","body":"IETF","designation":"RFC 4549","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4549.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4549.txt","https://www.rfc-editor.org/rfc/rfc4549.pdf"],"folder":"IETF/RFC-4549","files":{"txt":{"path":"standards/IETF/RFC-4549/RFC-4549.txt","sha256":"c224ccec74b8ea9ffd9921b8937f7070a048f6b36e91492e76709f7ba22096d7"}},"tags":["nested-reference","unchanged"],"summary":"This document attempts to address some of the issues involved in\n building a disconnected IMAP4 client. In particular, it deals with\n the issues of what might be called the \"driver\" portion of the\n synchronization tool: the portion of the code responsible for issuing\n the correct set of IMAP4 commands to synchronize the disconnected\n client in the way that is most likely to make the human who uses the\n disconnected client happy.\n\n This note describes different strategies that can be used by\n disconnected clients and shows how to use IMAP protocol in order to\n minimize the time of the synchronization process.\n\n This note also lists IMAP extensions that a server should implement\n in order to provide better synchronization facilities to disconnected\n clients.\n\nMelnikov Informational [Page 1]\n\f\nRFC 4549 Synch Ops for Disconnected IMAP4 Clients June 2006","scope_keywords":["4549","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4549 This document attempts to address some of the issues involved in\n building a disconnected IMAP4 client. In particular, it deals with\n the issues of what might be called the \"driver\" portion of the\n synchronization tool: the portion of the code responsible for issuing\n the correct set of IMAP4 commands to synchronize the disconnected\n client in the way that is most likely to make the human who uses the\n disconnected client happy.\n\n This note describes different strategies that can be used by\n disconnected clients and shows how to use IMAP protocol in order to\n minimize the time of the synchronization process.\n\n This note also lists IMAP extensions that a server should implement\n in order to provide better synchronization facilities to disconnected\n clients.\n\nMelnikov Informational [Page 1]\n\f\nRFC 4549 Synch Ops for Disconnected IMAP4 Clients June 2006 4549 key nested-reference unchanged"},{"id":"IETF RFC 5256","type":"specification","body":"IETF","designation":"RFC 5256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5256.txt","https://www.rfc-editor.org/rfc/rfc5256.pdf"],"folder":"IETF/RFC-5256","files":{"txt":{"path":"standards/IETF/RFC-5256/RFC-5256.txt","sha256":"716f958ea0f75c31779dcbff14acf246f267549baee71be83931b8fbdc2f18a4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the base-level server-based sorting and\n threading extensions to the IMAP protocol. These extensions provide\n substantial performance improvements for IMAP clients that offer\n sorted and threaded views.\n\n1. Introduction\n\n The SORT and THREAD extensions to the [IMAP] protocol provide a means\n of server-based sorting and threading of messages, without requiring\n that the client download the necessary data to do so itself. This is\n particularly useful for online clients as described in [IMAP-MODELS].\n\n A server that supports the base-level SORT extension indicates this\n with a capability name which starts with \"SORT\". Future, upwards-\n compatible extensions to the SORT extension will all start with\n \"SORT\", indicating support for this base level.\n\n A server that supports the THREAD extension indicates this with one\n or more capability names consisting of \"THREAD=\" fo","scope_keywords":["5256","algorithm","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5256 This document describes the base-level server-based sorting and\n threading extensions to the IMAP protocol. These extensions provide\n substantial performance improvements for IMAP clients that offer\n sorted and threaded views.\n\n1. Introduction\n\n The SORT and THREAD extensions to the [IMAP] protocol provide a means\n of server-based sorting and threading of messages, without requiring\n that the client download the necessary data to do so itself. This is\n particularly useful for online clients as described in [IMAP-MODELS].\n\n A server that supports the base-level SORT extension indicates this\n with a capability name which starts with \"SORT\". Future, upwards-\n compatible extensions to the SORT extension will all start with\n \"SORT\", indicating support for this base level.\n\n A server that supports the THREAD extension indicates this with one\n or more capability names consisting of \"THREAD=\" fo 5256 algorithm key subject nested-reference unchanged"},{"id":"IETF RFC 2384","type":"specification","body":"IETF","designation":"RFC 2384","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2384.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2384.txt","https://www.rfc-editor.org/rfc/rfc2384.pdf"],"folder":"IETF/RFC-2384","files":{"txt":{"path":"standards/IETF/RFC-2384/RFC-2384.txt","sha256":"90a96f75e40ea2927f83d38e5b57914c8f0dd8bff23bfca736f6f517213bdcb1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Gellens\nRequest for Comments: 2384 QUALCOMM, Incorporated\nCategory: Standards Track August 1998\n\n POP URL Scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n [POP3] is a widely-deployed mail access protocol. Many programs\n access POP3 message stores, and thus need POP3 configuration\n information. Since there are multiple configuration elements which\n are required in order to access a mailbox, a single string\n representation is convenient.\n\n A POP3 ma","scope_keywords":["2384","authentication","authorization","credential","credentials","encryption","key","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null}],"search_text":"IETF RFC 2384 Network Working Group R. Gellens\nRequest for Comments: 2384 QUALCOMM, Incorporated\nCategory: Standards Track August 1998\n\n POP URL Scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n [POP3] is a widely-deployed mail access protocol. Many programs\n access POP3 message stores, and thus need POP3 configuration\n information. Since there are multiple configuration elements which\n are required in order to access a mailbox, a single string\n representation is convenient.\n\n A POP3 ma 2384 authentication authorization credential credentials encryption key policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 2449","type":"specification","body":"IETF","designation":"RFC 2449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2449.txt","https://www.rfc-editor.org/rfc/rfc2449.pdf"],"folder":"IETF/RFC-2449","files":{"txt":{"path":"standards/IETF/RFC-2449/RFC-2449.txt","sha256":"036020793acba032093245d9b133545f22f6d6ede2f851a0086319183ddd22ad"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Gellens\nRequest for Comments: 2449 Qualcomm\nUpdates: 1939 C. Newman\nCategory: Standards Track Innosoft\n L. Lundblade\n Qualcomm\n November 1998\n\n POP3 Extension Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG Note\n\n This extension to the POP3 protocol is to be used by a server to\n express policy descisions taken by the server administrator. It is\n not an endorsement of implementations of further POP3 extensions\n generally. It is the general view that the POP","scope_keywords":["2449","crl","key","policy","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 3206","folder":"IETF/RFC-3206","source":"IETF/RFC-3206/RFC-3206.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null}],"search_text":"IETF RFC 2449 Network Working Group R. Gellens\nRequest for Comments: 2449 Qualcomm\nUpdates: 1939 C. Newman\nCategory: Standards Track Innosoft\n L. Lundblade\n Qualcomm\n November 1998\n\n POP3 Extension Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nIESG Note\n\n This extension to the POP3 protocol is to be used by a server to\n express policy descisions taken by the server administrator. It is\n not an endorsement of implementations of further POP3 extensions\n generally. It is the general view that the POP 2449 crl key policy timestamp nested-reference unchanged"},{"id":"IETF RFC 5034","type":"specification","body":"IETF","designation":"RFC 5034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5034.txt","https://www.rfc-editor.org/rfc/rfc5034.pdf"],"folder":"IETF/RFC-5034","files":{"txt":{"path":"standards/IETF/RFC-5034/RFC-5034.txt","sha256":"63cfc08a552add75d9bf22b0d977d40d5a105f67b71ed4c67015fe4670d68d8f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Siemborski\nRequest for Comments: 5034 Google, Inc.\nObsoletes: 1734 A. Menon-Sen\nUpdates: 2449 Oryx Mail Systems GmbH\nCategory: Standards Track July 2007\n\n The Post Office Protocol (POP3)\nSimple Authentication and Security Layer (SASL) Authentication Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document defines a profile of the Simple Authentication and\n Security Layer (SASL) for the Post Office Protocol (POP3). This\n extension allows a POP3 client to indicate an authen","scope_keywords":["5034","authentication","authorization","key","profile","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null}],"search_text":"IETF RFC 5034 Network Working Group R. Siemborski\nRequest for Comments: 5034 Google, Inc.\nObsoletes: 1734 A. Menon-Sen\nUpdates: 2449 Oryx Mail Systems GmbH\nCategory: Standards Track July 2007\n\n The Post Office Protocol (POP3)\nSimple Authentication and Security Layer (SASL) Authentication Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document defines a profile of the Simple Authentication and\n Security Layer (SASL) for the Post Office Protocol (POP3). This\n extension allows a POP3 client to indicate an authen 5034 authentication authorization key profile tls trust nested-reference unchanged"},{"id":"IETF RFC 1736","type":"specification","body":"IETF","designation":"RFC 1736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1736.txt","https://www.rfc-editor.org/rfc/rfc1736.pdf"],"folder":"IETF/RFC-1736","files":{"txt":{"path":"standards/IETF/RFC-1736/RFC-1736.txt","sha256":"e94fc566766bffe5f144eabbc99dfe579fb224e49341f64a3a77182ca0dcdfed"}},"tags":["nested-reference","unchanged"],"summary":"access method might be a software tool, an institution, or a network\n protocol. The parameter package might be service-specific access\n instructions. In order to protect creative development of new\n services, there is an extensible class of services for which no\n parameter package semantics common across services may be assumed.","scope_keywords":["1736","holder","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1808","folder":"IETF/RFC-1808","source":"IETF/RFC-1808/RFC-1808.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2276","folder":"IETF/RFC-2276","source":"IETF/RFC-2276/RFC-2276.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null}],"search_text":"IETF RFC 1736 access method might be a software tool, an institution, or a network\n protocol. The parameter package might be service-specific access\n instructions. In order to protect creative development of new\n services, there is an extensible class of services for which no\n parameter package semantics common across services may be assumed. 1736 holder http nested-reference unchanged"},{"id":"IETF RFC 2276","type":"specification","body":"IETF","designation":"RFC 2276","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2276.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2276.txt","https://www.rfc-editor.org/rfc/rfc2276.pdf"],"folder":"IETF/RFC-2276","files":{"txt":{"path":"standards/IETF/RFC-2276/RFC-2276.txt","sha256":"f1b4f238d8c2fec97f1a07de11fc053f3763bcef06eb8dbe402dbac14cacde9f"}},"tags":["nested-reference","unchanged"],"summary":"This document addresses the issues of the discovery of URN (Uniform\n Resource Name) resolver services that in turn will directly translate\n URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource\n Characteristics). The document falls into three major parts, the\n assumptions underlying the work, the guidelines in order to be a\n viable Resolver Discovery Service or RDS, and a framework for\n designing RDSs. The guidelines fall into three principle areas:\n evolvability, usability, and security and privacy. An RDS that is\n compliant with the framework will not necessarily be compliant with\n the guidelines. Compliance with the guidelines will need to be\n validated separately.","scope_keywords":["2276","identification","management","path","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 2276 This document addresses the issues of the discovery of URN (Uniform\n Resource Name) resolver services that in turn will directly translate\n URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource\n Characteristics). The document falls into three major parts, the\n assumptions underlying the work, the guidelines in order to be a\n viable Resolver Discovery Service or RDS, and a framework for\n designing RDSs. The guidelines fall into three principle areas:\n evolvability, usability, and security and privacy. An RDS that is\n compliant with the framework will not necessarily be compliant with\n the guidelines. Compliance with the guidelines will need to be\n validated separately. 2276 identification management path policy qualified nested-reference unchanged"},{"id":"IETF RFC 1737","type":"specification","body":"IETF","designation":"RFC 1737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1737.txt","https://www.rfc-editor.org/rfc/rfc1737.pdf"],"folder":"IETF/RFC-1737","files":{"txt":{"path":"standards/IETF/RFC-1737/RFC-1737.txt","sha256":"5f639d50b74d6639e7bb892c0c4a88ab0d0b9fb76383fa0dce363deec63bfa6d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Sollins\nRequest for Comments: 1737 MIT/LCS\nCategory: Informational L. Masinter\n Xerox Corporation\n December 1994\n\n Functional Requirements for Uniform Resource Names\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This document specifies a minimum set of requirements for a kind of\n Internet resource identifier known as Uniform Resource Names (URNs).\n URNs fit within a larger Internet information architecture, which in\n turn is composed of, additionally, Uniform Resource Characteristics\n (URCs), and Uniform Resource Locators (URLs). URNs are used for\n identification, URCs for including meta-information, and URLs for\n locating or finding resources. It is provided as a basis for\n evaluating standards for URNs. Th","scope_keywords":["1737","algorithm","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2141","folder":"IETF/RFC-2141","source":"IETF/RFC-2141/RFC-2141.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2276","folder":"IETF/RFC-2276","source":"IETF/RFC-2276/RFC-2276.txt","version":null},{"body":"IETF","designation":"RFC 2288","folder":"IETF/RFC-2288","source":"IETF/RFC-2288/RFC-2288.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 6288","folder":"IETF/RFC-6288","source":"IETF/RFC-6288/RFC-6288.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 1737 Network Working Group K. Sollins\nRequest for Comments: 1737 MIT/LCS\nCategory: Informational L. Masinter\n Xerox Corporation\n December 1994\n\n Functional Requirements for Uniform Resource Names\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\n1. Introduction\n\n This document specifies a minimum set of requirements for a kind of\n Internet resource identifier known as Uniform Resource Names (URNs).\n URNs fit within a larger Internet information architecture, which in\n turn is composed of, additionally, Uniform Resource Characteristics\n (URCs), and Uniform Resource Locators (URLs). URNs are used for\n identification, URCs for including meta-information, and URLs for\n locating or finding resources. It is provided as a basis for\n evaluating standards for URNs. Th 1737 algorithm identification presentation nested-reference unchanged"},{"id":"IETF RFC 2288","type":"specification","body":"IETF","designation":"RFC 2288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2288.txt","https://www.rfc-editor.org/rfc/rfc2288.pdf"],"folder":"IETF/RFC-2288","files":{"txt":{"path":"standards/IETF/RFC-2288/RFC-2288.txt","sha256":"d4e4c7aefd6d372efcea2b2ec493af53617ced3e2c78be210795bd0e89d648c4"}},"tags":["nested-reference","unchanged"],"summary":"A system for Uniform Resource Names (URNs) must be capable of\n supporting identifiers from existing widely-used naming systems.\n This document discusses how three major bibliographic identifiers\n (the ISBN, ISSN and SICI) can be supported within the URN framework\n and the currently proposed syntax for URNs.\n\n1. Introduction\n\n The ongoing work of several IETF working groups, most recently in the\n Uniform Resource Names working group, has culminated the development\n of a syntax for Uniform Resource Names (URNs). The functional\n requirements and overall framework for Uniform Resource Names are\n specified in RFC 1737 [Sollins & Masinter] and the specification for\n the URN syntax is RFC 2141 [Moats].\n\n As part of the validation process for the development of URNs the\n IETF working group has agreed that it is important to demonstrate\n that the current URN syntax proposal can accommodate existi","scope_keywords":["2288","identification","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3187","folder":"IETF/RFC-3187","source":"IETF/RFC-3187/RFC-3187.txt","version":null},{"body":"IETF","designation":"RFC 3188","folder":"IETF/RFC-3188","source":"IETF/RFC-3188/RFC-3188.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null}],"search_text":"IETF RFC 2288 A system for Uniform Resource Names (URNs) must be capable of\n supporting identifiers from existing widely-used naming systems.\n This document discusses how three major bibliographic identifiers\n (the ISBN, ISSN and SICI) can be supported within the URN framework\n and the currently proposed syntax for URNs.\n\n1. Introduction\n\n The ongoing work of several IETF working groups, most recently in the\n Uniform Resource Names working group, has culminated the development\n of a syntax for Uniform Resource Names (URNs). The functional\n requirements and overall framework for Uniform Resource Names are\n specified in RFC 1737 [Sollins & Masinter] and the specification for\n the URN syntax is RFC 2141 [Moats].\n\n As part of the validation process for the development of URNs the\n IETF working group has agreed that it is important to demonstrate\n that the current URN syntax proposal can accommodate existi 2288 identification management validation nested-reference unchanged"},{"id":"IETF RFC 3044","type":"specification","body":"IETF","designation":"RFC 3044","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3044.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3044.txt","https://www.rfc-editor.org/rfc/rfc3044.pdf"],"folder":"IETF/RFC-3044","files":{"txt":{"path":"standards/IETF/RFC-3044/RFC-3044.txt","sha256":"80ca17173ab544cc5ce90e2a3ac802b2e8472a794b52755e1b3b8b12bfa6567c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents how the ISSN - International Standard Serial\n Number - which is a persistent number for unique identification of\n serials widely recognised and used in the bibliographic world, can be\n supported within the Uniform Resource Name (URN) framework as a\n specific URN namespace identifier.\n\n An ISSN URN resolution system using the ISSN identifier as Uniform\n resource Name within an ISN URN Namespace has been developed by the\n ISSN International Centre (ISSN-IC) and is operating as a\n demonstrator to evaluate all requirements to deploy it in an\n operational environment.\n\n This proceeds from concepts and proposals developed in several IETF\n RFCs emphasising the way to implement and to use \"recognised\"\n existing numbering system within the URN framework (RFC 2248, RFC\n 2141, RFC 2611).\n\nRozenfeld Informational [Page 1]\n\f\nRFC 3044 ISSN as URN within an ISSN-URN Namespace Jan","scope_keywords":["3044","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 3044 This document presents how the ISSN - International Standard Serial\n Number - which is a persistent number for unique identification of\n serials widely recognised and used in the bibliographic world, can be\n supported within the Uniform Resource Name (URN) framework as a\n specific URN namespace identifier.\n\n An ISSN URN resolution system using the ISSN identifier as Uniform\n resource Name within an ISN URN Namespace has been developed by the\n ISSN International Centre (ISSN-IC) and is operating as a\n demonstrator to evaluate all requirements to deploy it in an\n operational environment.\n\n This proceeds from concepts and proposals developed in several IETF\n RFCs emphasising the way to implement and to use \"recognised\"\n existing numbering system within the URN framework (RFC 2248, RFC\n 2141, RFC 2611).\n\nRozenfeld Informational [Page 1]\n\f\nRFC 3044 ISSN as URN within an ISSN-URN Namespace Jan 3044 identification key nested-reference unchanged"},{"id":"IETF RFC 3404","type":"specification","body":"IETF","designation":"RFC 3404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3404.txt","https://www.rfc-editor.org/rfc/rfc3404.pdf"],"folder":"IETF/RFC-3404","files":{"txt":{"path":"standards/IETF/RFC-3404/RFC-3404.txt","sha256":"37f8ee9d07487b2ebe10fe04651ffb6d8b895dd4e4a669f83234374c6383f4d1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a specification for taking Uniform Resource\n Identifiers (URI) and locating an authoritative server for\n information about that URI. The method used to locate that\n authoritative server is the Dynamic Delegation Discovery System.\n\n This document is part of a series that is specified in \"Dynamic\n Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS\"\n (RFC 3401). It is very important to note that it is impossible to\n read and understand any document in this series without reading the\n others.","scope_keywords":["3404","algorithm","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 3404 This document describes a specification for taking Uniform Resource\n Identifiers (URI) and locating an authoritative server for\n information about that URI. The method used to locate that\n authoritative server is the Dynamic Delegation Discovery System.\n\n This document is part of a series that is specified in \"Dynamic\n Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS\"\n (RFC 3401). It is very important to note that it is impossible to\n read and understand any document in this series without reading the\n others. 3404 algorithm http key nested-reference unchanged"},{"id":"IETF RFC 6288","type":"specification","body":"IETF","designation":"RFC 6288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6288.txt","https://www.rfc-editor.org/rfc/rfc6288.pdf"],"folder":"IETF/RFC-6288","files":{"txt":{"path":"standards/IETF/RFC-6288/RFC-6288.txt","sha256":"19a91daf0ba4e84b1f485def0f85a34f3ae27ab951de319580d1dd77efa25103"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Namespace Identifier (NID) for Uniform\n Resource Name (URN) Namespace resources published by the Defence\n Geospatial Information Working Group (DGIWG). The DGIWG defines and\n manages resources that utilize this URN name model.\n\n Management activities for these and other resource types are provided\n by the DGIWG Registry System (DRS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current sta","scope_keywords":["6288","http","https","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 6288 This document describes the Namespace Identifier (NID) for Uniform\n Resource Name (URN) Namespace resources published by the Defence\n Geospatial Information Working Group (DGIWG). The DGIWG defines and\n manages resources that utilize this URN name model.\n\n Management activities for these and other resource types are provided\n by the DGIWG Registry System (DRS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current sta 6288 http https license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1980","type":"specification","body":"IETF","designation":"RFC 1980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1980.txt","https://www.rfc-editor.org/rfc/rfc1980.pdf"],"folder":"IETF/RFC-1980","files":{"txt":{"path":"standards/IETF/RFC-1980/RFC-1980.txt","sha256":"53aa9ee7f50b4ed2121f50b4cbe5753996d76c54fa4d2da0425e59e388476aa9"}},"tags":["nested-reference","unchanged"],"summary":"The markup language known as \"HTML/2.0\" provides for image maps.\n Image maps are document elements which allow clicking different areas\n of an image to reference different network resources, as specified by\n Uniform Identifier (URIs). The image map capability in HTML/2.0 is\n limited in several ways, such as the restriction that it only works\n with documents served via the \"HTTP\" protocol, and the lack of a\n viable fallback for users of text-only browsers. This document\n specifies an extension to the HTML language, referred to as \"Client-\n Side Image Maps,\" which resolves these limitations.","scope_keywords":["1980","attribute","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null}],"search_text":"IETF RFC 1980 The markup language known as \"HTML/2.0\" provides for image maps.\n Image maps are document elements which allow clicking different areas\n of an image to reference different network resources, as specified by\n Uniform Identifier (URIs). The image map capability in HTML/2.0 is\n limited in several ways, such as the restriction that it only works\n with documents served via the \"HTTP\" protocol, and the lack of a\n viable fallback for users of text-only browsers. This document\n specifies an extension to the HTML language, referred to as \"Client-\n Side Image Maps,\" which resolves these limitations. 1980 attribute http presentation nested-reference unchanged"},{"id":"IETF RFC 2056","type":"specification","body":"IETF","designation":"RFC 2056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2056.txt","https://www.rfc-editor.org/rfc/rfc2056.pdf"],"folder":"IETF/RFC-2056","files":{"txt":{"path":"standards/IETF/RFC-2056/RFC-2056.txt","sha256":"7a3b3f14a2a567b2d03982f28b235c8df51d12e734f8b2224675070be0771b8d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Denenberg\nRequest for Comments: 2056 Library of Congress\nCategory: Standards Track J. Kunze\n University of California, San Francisco\n D. Lynch\n SilverPlatter Information Ltd.\n Editors\n November 1996\n\n Uniform Resource Locators for Z39.50\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n Z39.50 is an information retrieval protocol that does not fit neatly\n into a retrieval model designed primarily around the stateless fetch\n of data. Instead, it models a general user inquiry as a session-\n oriented, multi-step task, any step of which may ","scope_keywords":["2056","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2056 Network Working Group R. Denenberg\nRequest for Comments: 2056 Library of Congress\nCategory: Standards Track J. Kunze\n University of California, San Francisco\n D. Lynch\n SilverPlatter Information Ltd.\n Editors\n November 1996\n\n Uniform Resource Locators for Z39.50\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n Z39.50 is an information retrieval protocol that does not fit neatly\n into a retrieval model designed primarily around the stateless fetch\n of data. Instead, it models a general user inquiry as a session-\n oriented, multi-step task, any step of which may  2056 attribute presentation nested-reference unchanged"},{"id":"IETF RFC 2079","type":"specification","body":"IETF","designation":"RFC 2079","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2079.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2079.txt","https://www.rfc-editor.org/rfc/rfc2079.pdf"],"folder":"IETF/RFC-2079","files":{"txt":{"path":"standards/IETF/RFC-2079/RFC-2079.txt","sha256":"2e01fe027471c6f8fb381ef2668c99b3255241086483c0105925d05cc1e91c8d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Smith\nRequest for Comments: 2079 Netscape Communications\nCategory: Standards Track January 1997\n\n Definition of an X.500 Attribute Type and an Object Class to Hold\n Uniform Resource Identifiers (URIs)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n Uniform Resource Locators (URLs) are being widely used to specify the\n location of Internet resources. There is an urgent need to be able\n to include URLs in directories that conform to the LDAP and X.500\n information models, and a desire to include other types of Uniform\n Resource Identifiers (URI","scope_keywords":["2079","attribute","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2079 Network Working Group M. Smith\nRequest for Comments: 2079 Netscape Communications\nCategory: Standards Track January 1997\n\n Definition of an X.500 Attribute Type and an Object Class to Hold\n Uniform Resource Identifiers (URIs)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n Uniform Resource Locators (URLs) are being widely used to specify the\n location of Internet resources. There is an urgent need to be able\n to include URLs in directories that conform to the LDAP and X.500\n information models, and a desire to include other types of Uniform\n Resource Identifiers (URI 2079 attribute http nested-reference unchanged"},{"id":"IETF RFC 2186","type":"specification","body":"IETF","designation":"RFC 2186","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2186.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2186.txt","https://www.rfc-editor.org/rfc/rfc2186.pdf"],"folder":"IETF/RFC-2186","files":{"txt":{"path":"standards/IETF/RFC-2186/RFC-2186.txt","sha256":"1a2309dd9ff80b27f8cacb1da694c41d879f874ba51c7e432e8ca29f64d19015"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Wessels\nRequest for Comments: 2186 K. Claffy\nCategory: Informational National Laboratory for Applied\n Network Research/UCSD\n September 1997\n\n Internet Cache Protocol (ICP), version 2\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes version 2 of the Internet Cache Protocol\n (ICPv2) as currently implemented in two World-Wide Web proxy cache\n packages[3,5]. ICP is a lightweight message format used for\n communicating among Web caches. ICP is used to exchange hints about\n the existence of URLs in neighbor caches. Caches exchange ICP\n queries and replies to gather information to use in selecting the\n most appropriate location from which to retrieve an object.\n\n This document describes only the format","scope_keywords":["2186","holder","http","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2187","folder":"IETF/RFC-2187","source":"IETF/RFC-2187/RFC-2187.txt","version":null},{"body":"IETF","designation":"RFC 2227","folder":"IETF/RFC-2227","source":"IETF/RFC-2227/RFC-2227.txt","version":null},{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 2756","folder":"IETF/RFC-2756","source":"IETF/RFC-2756/RFC-2756.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3143","folder":"IETF/RFC-3143","source":"IETF/RFC-3143/RFC-3143.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null}],"search_text":"IETF RFC 2186 Network Working Group D. Wessels\nRequest for Comments: 2186 K. Claffy\nCategory: Informational National Laboratory for Applied\n Network Research/UCSD\n September 1997\n\n Internet Cache Protocol (ICP), version 2\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document describes version 2 of the Internet Cache Protocol\n (ICPv2) as currently implemented in two World-Wide Web proxy cache\n packages[3,5]. ICP is a lightweight message format used for\n communicating among Web caches. ICP is used to exchange hints about\n the existence of URLs in neighbor caches. Caches exchange ICP\n queries and replies to gather information to use in selecting the\n most appropriate location from which to retrieve an object.\n\n This document describes only the format 2186 holder http path trust nested-reference unchanged"},{"id":"IETF RFC 2187","type":"specification","body":"IETF","designation":"RFC 2187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2187.txt","https://www.rfc-editor.org/rfc/rfc2187.pdf"],"folder":"IETF/RFC-2187","files":{"txt":{"path":"standards/IETF/RFC-2187/RFC-2187.txt","sha256":"9feba59a51e8731c01758f063689500cd18f4a9e09101fce263770b824f1c925"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the application of ICPv2 (Internet Cache\n Protocol version 2, RFC2186) to Web caching. ICPv2 is a lightweight\n message format used for communication among Web caches. Several\n independent caching implementations now use ICP[3,5], making it\n important to codify the existing practical uses of ICP for those\n trying to implement, deploy, and extend its use.\n\n ICP queries and replies refer to the existence of URLs (or objects)\n in neighbor caches. Caches exchange ICP messages and use the\n gathered information to select the most appropriate location from\n which to retrieve an object. A companion document (RFC2186)\n describes the format and syntax of the protocol itself. In this\n document we focus on issues of ICP deployment, efficiency, security,\n and interaction with other aspects of Web traffic behavior.","scope_keywords":["2187","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2186","folder":"IETF/RFC-2186","source":"IETF/RFC-2186/RFC-2186.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null}],"search_text":"IETF RFC 2187 This document describes the application of ICPv2 (Internet Cache\n Protocol version 2, RFC2186) to Web caching. ICPv2 is a lightweight\n message format used for communication among Web caches. Several\n independent caching implementations now use ICP[3,5], making it\n important to codify the existing practical uses of ICP for those\n trying to implement, deploy, and extend its use.\n\n ICP queries and replies refer to the existence of URLs (or objects)\n in neighbor caches. Caches exchange ICP messages and use the\n gathered information to select the most appropriate location from\n which to retrieve an object. A companion document (RFC2186)\n describes the format and syntax of the protocol itself. In this\n document we focus on issues of ICP deployment, efficiency, security,\n and interaction with other aspects of Web traffic behavior. 2187 http nested-reference unchanged"},{"id":"IETF RFC 2193","type":"specification","body":"IETF","designation":"RFC 2193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2193.txt","https://www.rfc-editor.org/rfc/rfc2193.pdf"],"folder":"IETF/RFC-2193","files":{"txt":{"path":"standards/IETF/RFC-2193/RFC-2193.txt","sha256":"411cbb94b96b82e2df9ecdf919bf1ec6acf22f760ef5d6aa8a47fd8ae8c7afe8"}},"tags":["nested-reference","unchanged"],"summary":"When dealing with large amounts of users, messages and geographically\n dispersed IMAP4 [RFC-2060] servers, it is often desirable to\n distribute messages amongst different servers within an organization.\n For example an administrator may choose to store user's personal\n mailboxes on a local IMAP4 server, while storing shared mailboxes\n remotely on another server. This type of configuration is common\n when it is uneconomical to store all data centrally due to limited\n bandwidth or disk resources.\n\n Mailbox referrals allow clients to seamlessly access mailboxes that\n are distributed across several IMAP4 servers.\n\n A referral mechanism can provide efficiencies over the alternative\n \"proxy method\", in which the local IMAP4 server contacts the remote\n server on behalf of the client, and then transfers the data from the\n remote server to itself, and then on to the client. The referral\n mechanis","scope_keywords":["2193","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3348","folder":"IETF/RFC-3348","source":"IETF/RFC-3348/RFC-3348.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2193 When dealing with large amounts of users, messages and geographically\n dispersed IMAP4 [RFC-2060] servers, it is often desirable to\n distribute messages amongst different servers within an organization.\n For example an administrator may choose to store user's personal\n mailboxes on a local IMAP4 server, while storing shared mailboxes\n remotely on another server. This type of configuration is common\n when it is uneconomical to store all data centrally due to limited\n bandwidth or disk resources.\n\n Mailbox referrals allow clients to seamlessly access mailboxes that\n are distributed across several IMAP4 servers.\n\n A referral mechanism can provide efficiencies over the alternative\n \"proxy method\", in which the local IMAP4 server contacts the remote\n server on behalf of the client, and then transfers the data from the\n remote server to itself, and then on to the client. The referral\n mechanis 2193 authentication key nested-reference unchanged"},{"id":"IETF RFC 2221","type":"specification","body":"IETF","designation":"RFC 2221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2221.txt","https://www.rfc-editor.org/rfc/rfc2221.pdf"],"folder":"IETF/RFC-2221","files":{"txt":{"path":"standards/IETF/RFC-2221/RFC-2221.txt","sha256":"bb340a5fe05b3a3fa119dc607e6b3e4673bab29a62aa9e0d91878216908fe7b4"}},"tags":["nested-reference","unchanged"],"summary":"When dealing with large amounts of users and many IMAP4 [RFC-2060]\n servers, it is often necessary to move users from one IMAP4 server to\n another. For example, hardware failures or organizational changes\n may dictate such a move.\n\n Login referrals allow clients to transparently connect to an\n alternate IMAP4 server, if their home IMAP4 server has changed.\n\n A referral mechanism can provide efficiencies over the alternative\n 'proxy method', in which the local IMAP4 server contacts the remote\n server on behalf of the client, and then transfers the data from the\n remote server to itself, and then on to the client. The referral\n mechanism's direct client connection to the remote server is often a\n more efficient use of bandwidth, and does not require the local\n server to impersonate the client when authenticating to the remote\n server.\n\n2. Conventions used in this document\n\n In examples, \"C","scope_keywords":["2221","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null}],"search_text":"IETF RFC 2221 When dealing with large amounts of users and many IMAP4 [RFC-2060]\n servers, it is often necessary to move users from one IMAP4 server to\n another. For example, hardware failures or organizational changes\n may dictate such a move.\n\n Login referrals allow clients to transparently connect to an\n alternate IMAP4 server, if their home IMAP4 server has changed.\n\n A referral mechanism can provide efficiencies over the alternative\n 'proxy method', in which the local IMAP4 server contacts the remote\n server on behalf of the client, and then transfers the data from the\n remote server to itself, and then on to the client. The referral\n mechanism's direct client connection to the remote server is often a\n more efficient use of bandwidth, and does not require the local\n server to impersonate the client when authenticating to the remote\n server.\n\n2. Conventions used in this document\n\n In examples, \"C 2221 authentication key nested-reference unchanged"},{"id":"IETF RFC 2244","type":"specification","body":"IETF","designation":"RFC 2244","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2244.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2244.txt","https://www.rfc-editor.org/rfc/rfc2244.pdf"],"folder":"IETF/RFC-2244","files":{"txt":{"path":"standards/IETF/RFC-2244/RFC-2244.txt","sha256":"98746bbeb56acbe61833c65b6ba3d5fb335cca55c6418e0508992ad426f2b185"}},"tags":["nested-reference","unchanged"],"summary":"The Application Configuration Access Protocol (ACAP) is designed to\n support remote storage and access of program option, configuration\n and preference information. The data store model is designed to\n allow a client relatively simple access to interesting data, to allow\n new information to be easily added without server re-configuration,\n and to promote the use of both standardized data and custom or\n proprietary data. Key features include \"inheritance\" which can be\n used to manage default values for configuration settings and access\n control lists which allow interesting personal information to be\n shared and group information to be restricted.\n\nNewman & Myers Standards Track [Page i]\n\f\nRFC 2244 ACAP November 1997","scope_keywords":["2244","attribute","attributes","authentication","key","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3431","folder":"IETF/RFC-3431","source":"IETF/RFC-3431/RFC-3431.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3685","folder":"IETF/RFC-3685","source":"IETF/RFC-3685/RFC-3685.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2244 The Application Configuration Access Protocol (ACAP) is designed to\n support remote storage and access of program option, configuration\n and preference information. The data store model is designed to\n allow a client relatively simple access to interesting data, to allow\n new information to be easily added without server re-configuration,\n and to promote the use of both standardized data and custom or\n proprietary data. Key features include \"inheritance\" which can be\n used to manage default values for configuration settings and access\n control lists which allow interesting personal information to be\n shared and group information to be restricted.\n\nNewman & Myers Standards Track [Page i]\n\f\nRFC 2244 ACAP November 1997 2244 attribute attributes authentication key management validation nested-reference unchanged"},{"id":"IETF RFC 2251","type":"specification","body":"IETF","designation":"RFC 2251","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2251.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2251.txt","https://www.rfc-editor.org/rfc/rfc2251.pdf"],"folder":"IETF/RFC-2251","files":{"txt":{"path":"standards/IETF/RFC-2251/RFC-2251.txt","sha256":"4d0690f4b26823fc11c47bb8fbda06ca2f5fd412c2589bb7e460e8d36966da9b"}},"tags":["nested-reference","unchanged"],"summary":"The protocol described in this document is designed to provide access\n to directories supporting the X.500 models, while not incurring the\n resource requirements of the X.500 Directory Access Protocol (DAP).\n This protocol is specifically targeted at management applications and\n browser applications that provide read/write interactive access to\n directories. When used with a directory supporting the X.500\n protocols, it is intended to be a complement to the X.500 DAP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", and \"MAY\" in this document\n are to be interpreted as described in RFC 2119 [10].\n\n Key aspects of this version of LDAP are:\n\n - All protocol elements of LDAPv2 (RFC 1777) are supported. The\n protocol is carried directly over TCP or other transport, bypassing\n much of the session/presentation overhead of X.500 DAP.\n\n","scope_keywords":["2251","attribute","attributes","authentication","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2589","folder":"IETF/RFC-2589","source":"IETF/RFC-2589/RFC-2589.txt","version":null},{"body":"IETF","designation":"RFC 2596","folder":"IETF/RFC-2596","source":"IETF/RFC-2596/RFC-2596.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2696","folder":"IETF/RFC-2696","source":"IETF/RFC-2696/RFC-2696.txt","version":null},{"body":"IETF","designation":"RFC 2739","folder":"IETF/RFC-2739","source":"IETF/RFC-2739/RFC-2739.txt","version":null},{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2798","folder":"IETF/RFC-2798","source":"IETF/RFC-2798/RFC-2798.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2891","folder":"IETF/RFC-2891","source":"IETF/RFC-2891/RFC-2891.txt","version":null},{"body":"IETF","designation":"RFC 2927","folder":"IETF/RFC-2927","source":"IETF/RFC-2927/RFC-2927.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3771","folder":"IETF/RFC-3771","source":"IETF/RFC-3771/RFC-3771.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null}],"search_text":"IETF RFC 2251 The protocol described in this document is designed to provide access\n to directories supporting the X.500 models, while not incurring the\n resource requirements of the X.500 Directory Access Protocol (DAP).\n This protocol is specifically targeted at management applications and\n browser applications that provide read/write interactive access to\n directories. When used with a directory supporting the X.500\n protocols, it is intended to be a complement to the X.500 DAP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", and \"MAY\" in this document\n are to be interpreted as described in RFC 2119 [10].\n\n Key aspects of this version of LDAP are:\n\n - All protocol elements of LDAPv2 (RFC 1777) are supported. The\n protocol is carried directly over TCP or other transport, bypassing\n much of the session/presentation overhead of X.500 DAP.\n\n 2251 attribute attributes authentication key management presentation nested-reference unchanged"},{"id":"IETF RFC 2255","type":"specification","body":"IETF","designation":"RFC 2255","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2255.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2255.txt","https://www.rfc-editor.org/rfc/rfc2255.pdf"],"folder":"IETF/RFC-2255","files":{"txt":{"path":"standards/IETF/RFC-2255/RFC-2255.txt","sha256":"5839f2e0fbf7add446c24cdf7e69e53e37dfdcc868fff890224da843f72a132e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 2255 M. Smith\nCategory: Standards Track Netscape Communications Corp.\n December 1997\n\n The LDAP URL Format\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nIESG NOTE\n\n This document describes a directory access protocol that provides\n both read and update access. Update access requires secure\n authentication, but this document does not mandate implementation of\n any satisfactory authentication mechanisms.\n\n In accordance with RFC 2026, secti","scope_keywords":["2255","attribute","attributes","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null}],"search_text":"IETF RFC 2255 Network Working Group T. Howes\nRequest for Comments: 2255 M. Smith\nCategory: Standards Track Netscape Communications Corp.\n December 1997\n\n The LDAP URL Format\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nIESG NOTE\n\n This document describes a directory access protocol that provides\n both read and update access. Update access requires secure\n authentication, but this document does not mandate implementation of\n any satisfactory authentication mechanisms.\n\n In accordance with RFC 2026, secti 2255 attribute attributes authentication key nested-reference unchanged"},{"id":"IETF RFC 2291","type":"specification","body":"IETF","designation":"RFC 2291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2291.txt","https://www.rfc-editor.org/rfc/rfc2291.pdf"],"folder":"IETF/RFC-2291","files":{"txt":{"path":"standards/IETF/RFC-2291/RFC-2291.txt","sha256":"86ef06e5623de5541ab36f1c8df98507440e6b974fd88cb68b18c7bcff4f1149"}},"tags":["nested-reference","unchanged"],"summary":"Current World Wide Web (WWW or Web) standards provide simple support\n for applications which allow remote editing of typed data. In\n practice, the existing capabilities of the WWW have proven inadequate\n to support efficient, scalable remote editing free of overwriting\n conflicts. This document presents a list of features in the form of\n requirements for a Web Distributed Authoring and Versioning protocol\n which, if implemented, would improve the efficiency of common remote\n editing operations, provide a locking mechanism to prevent overwrite\n conflicts, improve link management support between non-HTML data\n types, provide a simple attribute-value metadata facility, provide\n for the creation and reading of container data types, and integrate\n versioning into the WWW.\n\n1. Introduction\n\n This document describes functionality which, if incorporated in an\n extension to the existing HTTP prop","scope_keywords":["2291","attribute","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null}],"search_text":"IETF RFC 2291 Current World Wide Web (WWW or Web) standards provide simple support\n for applications which allow remote editing of typed data. In\n practice, the existing capabilities of the WWW have proven inadequate\n to support efficient, scalable remote editing free of overwriting\n conflicts. This document presents a list of features in the form of\n requirements for a Web Distributed Authoring and Versioning protocol\n which, if implemented, would improve the efficiency of common remote\n editing operations, provide a locking mechanism to prevent overwrite\n conflicts, improve link management support between non-HTML data\n types, provide a simple attribute-value metadata facility, provide\n for the creation and reading of container data types, and integrate\n versioning into the WWW.\n\n1. Introduction\n\n This document describes functionality which, if incorporated in an\n extension to the existing HTTP prop 2291 attribute http management presentation nested-reference unchanged"},{"id":"IETF RFC 2368","type":"specification","body":"IETF","designation":"RFC 2368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2368.txt","https://www.rfc-editor.org/rfc/rfc2368.pdf"],"folder":"IETF/RFC-2368","files":{"txt":{"path":"standards/IETF/RFC-2368/RFC-2368.txt","sha256":"ba8ffc4138ae0e1b25bf125068a57d998863be7d77e246b2e5757e33428243cf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman\nRequest for Comments: 2368 Internet Mail Consortium\nUpdates: 1738, 1808 L. Masinter\nCategory: Standards Track Xerox Corporation\n J. Zawinski\n Netscape Communications\n July 1998\n\n The mailto URL scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines the format of Uniform Resource Locators (URL)\n for designating electronic mail addresses. It is one of a suite of\n documents which replace RFC 1738, 'Uniform Resource Locators', and\n RF","scope_keywords":["2368","http","key","keys","profile","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2369","folder":"IETF/RFC-2369","source":"IETF/RFC-2369/RFC-2369.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3696","folder":"IETF/RFC-3696","source":"IETF/RFC-3696/RFC-3696.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5546","folder":"IETF/RFC-5546","source":"IETF/RFC-5546/RFC-5546.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null}],"search_text":"IETF RFC 2368 Network Working Group P. Hoffman\nRequest for Comments: 2368 Internet Mail Consortium\nUpdates: 1738, 1808 L. Masinter\nCategory: Standards Track Xerox Corporation\n J. Zawinski\n Netscape Communications\n July 1998\n\n The mailto URL scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines the format of Uniform Resource Locators (URL)\n for designating electronic mail addresses. It is one of a suite of\n documents which replace RFC 1738, 'Uniform Resource Locators', and\n RF 2368 http key keys profile subject nested-reference unchanged"},{"id":"IETF RFC 2369","type":"specification","body":"IETF","designation":"RFC 2369","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2369.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2369.txt","https://www.rfc-editor.org/rfc/rfc2369.pdf"],"folder":"IETF/RFC-2369","files":{"txt":{"path":"standards/IETF/RFC-2369/RFC-2369.txt","sha256":"659e81dbe0c700870b9ae35c765a70ad8c4c4127506df8c809d6e1393dc1998b"}},"tags":["nested-reference","unchanged"],"summary":"The mailing list command specification header fields are a set of\n structured fields to be added to email messages sent by email\n distribution lists. Each field typically contains a URL (usually\n mailto [RFC2368]) locating the relevant information or performing the\n command directly. The three core header fields described in this\n document are List-Help, List-Subscribe, and List-Unsubscribe.\n\n There are three other header fields described here which, although\n not as widely applicable, will have utility for a sufficient number\n of mailing lists to justify their formalization here. These are\n List-Post, List-Owner and List-Archive.\n\n By including these header fields, list servers can make it possible\n for mail clients to provide automated tools for users to perform list\n functions. This could take the form of a menu item, push button, or\n other user interface element. The intent is to sim","scope_keywords":["2369","http","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null}],"search_text":"IETF RFC 2369 The mailing list command specification header fields are a set of\n structured fields to be added to email messages sent by email\n distribution lists. Each field typically contains a URL (usually\n mailto [RFC2368]) locating the relevant information or performing the\n command directly. The three core header fields described in this\n document are List-Help, List-Subscribe, and List-Unsubscribe.\n\n There are three other header fields described here which, although\n not as widely applicable, will have utility for a sufficient number\n of mailing lists to justify their formalization here. These are\n List-Post, List-Owner and List-Archive.\n\n By including these header fields, list servers can make it possible\n for mail clients to provide automated tools for users to perform list\n functions. This could take the form of a menu item, push button, or\n other user interface element. The intent is to sim 2369 http key subject nested-reference unchanged"},{"id":"IETF RFC 2371","type":"specification","body":"IETF","designation":"RFC 2371","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2371.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2371.txt","https://www.rfc-editor.org/rfc/rfc2371.pdf"],"folder":"IETF/RFC-2371","files":{"txt":{"path":"standards/IETF/RFC-2371/RFC-2371.txt","sha256":"78f04f5387c1f144e1ff1ba83100ab8151e4b1eaa2cd663dcfc433dfc43d8998"}},"tags":["nested-reference","unchanged"],"summary":"In many applications where different nodes cooperate on some work,\n there is a need to guarantee that the work happens atomically. That\n is, each node must reach the same conclusion as to whether the work\n is to be completed, even in the face of failures. This document\n proposes a simple, easily-implemented protocol for achieving this\n end.","scope_keywords":["2371","http","identification","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2372","folder":"IETF/RFC-2372","source":"IETF/RFC-2372/RFC-2372.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2371 In many applications where different nodes cooperate on some work,\n there is a need to guarantee that the work happens atomically. That\n is, each node must reach the same conclusion as to whether the work\n is to be completed, even in the face of failures. This document\n proposes a simple, easily-implemented protocol for achieving this\n end. 2371 http identification presentation subject nested-reference unchanged"},{"id":"IETF RFC 2392","type":"specification","body":"IETF","designation":"RFC 2392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2392.txt","https://www.rfc-editor.org/rfc/rfc2392.pdf"],"folder":"IETF/RFC-2392","files":{"txt":{"path":"standards/IETF/RFC-2392/RFC-2392.txt","sha256":"0094525a768e5ba689477203bb29b88a8fe9fa8dde4309c67347b2e4539f9cd9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Levinson\nRequest for Comments: 2392 August 1998\nObsoletes: 2111\nCategory: Standards Track\n\n Content-ID and Message-ID Uniform Resource Locators\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Uniform Resource Locator (URL) schemes, \"cid:\" and \"mid:\" allow\n references to messages and the body parts of messages. For example,\n within a single multipart message, one HTML body part might include\n embedded references to other parts of the same message.\n\nChanges ","scope_keywords":["2392","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null}],"search_text":"IETF RFC 2392 Network Working Group E. Levinson\nRequest for Comments: 2392 August 1998\nObsoletes: 2111\nCategory: Standards Track\n\n Content-ID and Message-ID Uniform Resource Locators\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n The Uniform Resource Locator (URL) schemes, \"cid:\" and \"mid:\" allow\n references to messages and the body parts of messages. For example,\n within a single multipart message, one HTML body part might include\n embedded references to other parts of the same message.\n\nChanges  2392 subject nested-reference unchanged"},{"id":"IETF RFC 2425","type":"specification","body":"IETF","designation":"RFC 2425","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2425.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2425.txt","https://www.rfc-editor.org/rfc/rfc2425.pdf"],"folder":"IETF/RFC-2425","files":{"txt":{"path":"standards/IETF/RFC-2425/RFC-2425.txt","sha256":"64298fbb942e3ad944aca9380ca3be52a5fc5c0031f6331b917da8a2ad6548a9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a MIME Content-Type for holding directory\n information. The definition is independent of any particular\n directory service or protocol. The text/directory Content-Type is\n defined for holding a variety of directory information, for example,\n name, or email address, or logo. The text/directory Content-Type can\n also be used as the root body part in a multipart/related Content-\n Type for handling more complicated situations, especially those in\n which non-textual information that already has a natural MIME\n representation, for example, a photograph or sound, is to be\n represented.\n\n The text/directory Content-Type defines a general framework and\n format for holding directory information in a simple \"type:value\"\n form. We refer to \"type\" in this context meaning a property or\n attribute with which the value is associated. Mechanisms are defined\n to specify alternate lan","scope_keywords":["2425","attribute","key","presentation","profile","profiles","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2649","folder":"IETF/RFC-2649","source":"IETF/RFC-2649/RFC-2649.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2927","folder":"IETF/RFC-2927","source":"IETF/RFC-2927/RFC-2927.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null}],"search_text":"IETF RFC 2425 This document defines a MIME Content-Type for holding directory\n information. The definition is independent of any particular\n directory service or protocol. The text/directory Content-Type is\n defined for holding a variety of directory information, for example,\n name, or email address, or logo. The text/directory Content-Type can\n also be used as the root body part in a multipart/related Content-\n Type for handling more complicated situations, especially those in\n which non-textual information that already has a natural MIME\n representation, for example, a photograph or sound, is to be\n represented.\n\n The text/directory Content-Type defines a general framework and\n format for holding directory information in a simple \"type:value\"\n form. We refer to \"type\" in this context meaning a property or\n attribute with which the value is associated. Mechanisms are defined\n to specify alternate lan 2425 attribute key presentation profile profiles registered nested-reference unchanged"},{"id":"IETF RFC 2426","type":"specification","body":"IETF","designation":"RFC 2426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2426.txt","https://www.rfc-editor.org/rfc/rfc2426.pdf"],"folder":"IETF/RFC-2426","files":{"txt":{"path":"standards/IETF/RFC-2426/RFC-2426.txt","sha256":"0ba71155462f3456036c0cc8862be36198d3f138ecb8e42d876d3609bf9a6562"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the profile of the MIME Content-Type [MIME-DIR] for\n directory information for a white-pages person object, based on a\n vCard electronic business card. The profile definition is independent\n of any particular directory service or protocol. The profile is\n defined for representing and exchanging a variety of information\n about an individual (e.g., formatted and structured name and delivery\n addresses, email address, multiple telephone numbers, photograph,\n logo, audio clips, etc.). The directory information used by this\n profile is based on the attributes for the person object defined in\n the X.520 and X.521 directory services recommendations. The profile\n also provides the method for including a [VCARD] representation of a\n white-pages directory entry within the MIME Content-Type defined by\n the [MIME-DIR] document.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL","scope_keywords":["2426","attribute","attributes","delivery","identification","key","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2739","folder":"IETF/RFC-2739","source":"IETF/RFC-2739/RFC-2739.txt","version":null},{"body":"IETF","designation":"RFC 2779","folder":"IETF/RFC-2779","source":"IETF/RFC-2779/RFC-2779.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null}],"search_text":"IETF RFC 2426 This memo defines the profile of the MIME Content-Type [MIME-DIR] for\n directory information for a white-pages person object, based on a\n vCard electronic business card. The profile definition is independent\n of any particular directory service or protocol. The profile is\n defined for representing and exchanging a variety of information\n about an individual (e.g., formatted and structured name and delivery\n addresses, email address, multiple telephone numbers, photograph,\n logo, audio clips, etc.). The directory information used by this\n profile is based on the attributes for the person object defined in\n the X.520 and X.521 directory services recommendations. The profile\n also provides the method for including a [VCARD] representation of a\n white-pages directory entry within the MIME Content-Type defined by\n the [MIME-DIR] document.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL 2426 attribute attributes delivery identification key presentation profile nested-reference unchanged"},{"id":"IETF RFC 2445","type":"specification","body":"IETF","designation":"RFC 2445","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2445.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2445.txt","https://www.rfc-editor.org/rfc/rfc2445.pdf"],"folder":"IETF/RFC-2445","files":{"txt":{"path":"standards/IETF/RFC-2445/RFC-2445.txt","sha256":"21bfccbb1f8d658d355b8e530feb2bf15d74e0bd3d988f1733569bce9eeaa828"}},"tags":["nested-reference","unchanged"],"summary":"There is a clear need to provide and deploy interoperable calendaring\n and scheduling services for the Internet. Current group scheduling\n and Personal Information Management (PIM) products are being extended\n for use across the Internet, today, in proprietary ways. This memo\n has been defined to provide the definition of a common format for\n openly exchanging calendaring and scheduling information across the\n Internet.\n\n This memo is formatted as a registration for a MIME media type per\n [RFC 2048]. However, the format in this memo is equally applicable\n for use outside of a MIME message content type.\n\n The proposed media type value is 'text/calendar'. This string would\n label a media type containing calendaring and scheduling information\n encoded as text characters formatted in a manner outlined below.\n\n This MIME media type provides a standard content type for capturing\n calendar even","scope_keywords":["2445","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2446","folder":"IETF/RFC-2446","source":"IETF/RFC-2446/RFC-2446.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2739","folder":"IETF/RFC-2739","source":"IETF/RFC-2739/RFC-2739.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null}],"search_text":"IETF RFC 2445 There is a clear need to provide and deploy interoperable calendaring\n and scheduling services for the Internet. Current group scheduling\n and Personal Information Management (PIM) products are being extended\n for use across the Internet, today, in proprietary ways. This memo\n has been defined to provide the definition of a common format for\n openly exchanging calendaring and scheduling information across the\n Internet.\n\n This memo is formatted as a registration for a MIME media type per\n [RFC 2048]. However, the format in this memo is equally applicable\n for use outside of a MIME message content type.\n\n The proposed media type value is 'text/calendar'. This string would\n label a media type containing calendaring and scheduling information\n encoded as text characters formatted in a manner outlined below.\n\n This MIME media type provides a standard content type for capturing\n calendar even 2445 http management presentation nested-reference unchanged"},{"id":"IETF RFC 2511","type":"specification","body":"IETF","designation":"RFC 2511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2511.txt","https://www.rfc-editor.org/rfc/rfc2511.pdf"],"folder":"IETF/RFC-2511","files":{"txt":{"path":"standards/IETF/RFC-2511/RFC-2511.txt","sha256":"d8cca2200ce0156acaafdf186deff5a18942b19ef033ca643575841b9a50eac3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Certificate Request Message Format\n (CRMF). This syntax is used to convey a request for a certificate to\n a Certification Authority (CA) (possibly via a Registration Authority\n (RA)) for the purposes of X.509 certificate production. The request\n will typically include a public key and associated registration\n information.\n\n The key words \"MUST\", \"REQUIRED\", \"SHOULD\", \"RECOMMENDED\", and \"MAY\"\n in this document (in uppercase, as shown) are to be interpreted as\n described in RFC 2119.\n\n2. Overview\n\n Construction of a certification request involves the following steps:\n\n a) A CertRequest value is constructed. This value may include the\n public key, all or a portion of the end-entity's (EE's) name,\n other requested certificate fields, and additional control\n information related to the registration process.\n\nMyers, et. al. Standards Track [Page 1]\n\f\nRFC 2511 Interne","scope_keywords":["2511","algorithm","attribute","certificate","certificates","delivery","encryption","key","keys","management","pki","policies","policy","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null}],"search_text":"IETF RFC 2511 This document describes the Certificate Request Message Format\n (CRMF). This syntax is used to convey a request for a certificate to\n a Certification Authority (CA) (possibly via a Registration Authority\n (RA)) for the purposes of X.509 certificate production. The request\n will typically include a public key and associated registration\n information.\n\n The key words \"MUST\", \"REQUIRED\", \"SHOULD\", \"RECOMMENDED\", and \"MAY\"\n in this document (in uppercase, as shown) are to be interpreted as\n described in RFC 2119.\n\n2. Overview\n\n Construction of a certification request involves the following steps:\n\n a) A CertRequest value is constructed. This value may include the\n public key, all or a portion of the end-entity's (EE's) name,\n other requested certificate fields, and additional control\n information related to the registration process.\n\nMyers, et. al. Standards Track [Page 1]\n\f\nRFC 2511 Interne 2511 algorithm attribute certificate certificates delivery encryption key keys management pki policies policy signature trust nested-reference unchanged"},{"id":"IETF RFC 2560","type":"specification","body":"IETF","designation":"RFC 2560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2560.txt","https://www.rfc-editor.org/rfc/rfc2560.pdf"],"folder":"IETF/RFC-2560","files":{"txt":{"path":"standards/IETF/RFC-2560/RFC-2560.txt","sha256":"696f222c08e734c4ac324f6b069457d0a6024f5356cac885021eb47527972398"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol useful in determining the current\n status of a digital certificate without requiring CRLs. Additional\n mechanisms addressing PKIX operational requirements are specified in\n separate documents.\n\n An overview of the protocol is provided in section 2. Functional\n requirements are specified in section 4. Details of the protocol are\n in section 5. We cover security issues with the protocol in section\n 6. Appendix A defines OCSP over HTTP, appendix B accumulates ASN.1\n syntactic elements and appendix C specifies the mime types for the\n messages.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document (in uppercase, as shown) are to be interpreted as described\n in [RFC2119].\n\nMyers, et al. Standards Track [Page 1]\n\f\nRFC 2560 PKIX OCSP June 1999\n\n2. Protocol Overview\n\n","scope_keywords":["2560","algorithm","certificate","certificates","crl","hash","http","key","ocsp","pki","revocation","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4806","folder":"IETF/RFC-4806","source":"IETF/RFC-4806/RFC-4806.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 2560 This document specifies a protocol useful in determining the current\n status of a digital certificate without requiring CRLs. Additional\n mechanisms addressing PKIX operational requirements are specified in\n separate documents.\n\n An overview of the protocol is provided in section 2. Functional\n requirements are specified in section 4. Details of the protocol are\n in section 5. We cover security issues with the protocol in section\n 6. Appendix A defines OCSP over HTTP, appendix B accumulates ASN.1\n syntactic elements and appendix C specifies the mime types for the\n messages.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document (in uppercase, as shown) are to be interpreted as described\n in [RFC2119].\n\nMyers, et al. Standards Track [Page 1]\n\f\nRFC 2560 PKIX OCSP June 1999\n\n2. Protocol Overview\n\n 2560 algorithm certificate certificates crl hash http key ocsp pki revocation signature trust nested-reference unchanged"},{"id":"IETF RFC 2585","type":"specification","body":"IETF","designation":"RFC 2585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2585.txt","https://www.rfc-editor.org/rfc/rfc2585.pdf"],"folder":"IETF/RFC-2585","files":{"txt":{"path":"standards/IETF/RFC-2585/RFC-2585.txt","sha256":"98d316b4b32dcba6478c30135f1c7e26fcca1d44e6c207270622110eaa7949d4"}},"tags":["nested-reference","unchanged"],"summary":"The protocol conventions described in this document satisfy some of\n the operational requirements of the Internet Public Key\n Infrastructure (PKI). This document specifies the conventions for\n using the File Transfer Protocol (FTP) and the Hypertext Transfer\n Protocol (HTTP) to obtain certificates and certificate revocation\n lists (CRLs) from PKI repositories. Additional mechanisms addressing\n PKIX operational requirements are specified in separate documents.\n\n1 Introduction\n\n This specification is part of a multi-part standard for the Internet\n Public Key Infrastructure (PKI) using X.509 certificates and\n certificate revocation lists (CRLs). This document specifies the\n conventions for using the File Transfer Protocol (FTP) and the\n Hypertext Transfer Protocol (HTTP) to obtain certificates and CRLs\n from PKI repositories. Additional mechanisms addressing PKI\n repository access are speci","scope_keywords":["2585","certificate","certificates","crl","http","issuer","key","management","pki","revocation","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null}],"search_text":"IETF RFC 2585 The protocol conventions described in this document satisfy some of\n the operational requirements of the Internet Public Key\n Infrastructure (PKI). This document specifies the conventions for\n using the File Transfer Protocol (FTP) and the Hypertext Transfer\n Protocol (HTTP) to obtain certificates and certificate revocation\n lists (CRLs) from PKI repositories. Additional mechanisms addressing\n PKIX operational requirements are specified in separate documents.\n\n1 Introduction\n\n This specification is part of a multi-part standard for the Internet\n Public Key Infrastructure (PKI) using X.509 certificates and\n certificate revocation lists (CRLs). This document specifies the\n conventions for using the File Transfer Protocol (FTP) and the\n Hypertext Transfer Protocol (HTTP) to obtain certificates and CRLs\n from PKI repositories. Additional mechanisms addressing PKI\n repository access are speci 2585 certificate certificates crl http issuer key management pki revocation subject validation nested-reference unchanged"},{"id":"IETF RFC 2655","type":"specification","body":"IETF","designation":"RFC 2655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2655.txt","https://www.rfc-editor.org/rfc/rfc2655.pdf"],"folder":"IETF/RFC-2655","files":{"txt":{"path":"standards/IETF/RFC-2655/RFC-2655.txt","sha256":"be6cee400cf5861fcba073909089604e570e74d17ecd4dce3d4c261f933a93d5"}},"tags":["nested-reference","unchanged"],"summary":"The Common Indexing Protocol (CIP) allows servers to form a referral\n mesh for query handling by defining a mechanism by which cooperating\n servers exchange hints about the searchable indices they maintain.\n The structure and transport of CIP are described in (Ref. 1), as are\n general rules for the definition of index object types. This\n document describes SOIF, the Summary Object Interchange Format, as an\n index object type in the context of the CIP framework. SOIF is a\n machine-readable syntax for transmitting structured summary objects,\n currently used primarily in the context of the World Wide Web.\n\n Query referral has often been dismissed as an ineffective strategy\n for handling searches of Web resources, and Web resources certainly\n present challenges not present in structured directory services like\n Rwhois. In situations where a keyword-based free text search is\n desired, query r","scope_keywords":["2655","attribute","attributes","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2656","folder":"IETF/RFC-2656","source":"IETF/RFC-2656/RFC-2656.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2655 The Common Indexing Protocol (CIP) allows servers to form a referral\n mesh for query handling by defining a mechanism by which cooperating\n servers exchange hints about the searchable indices they maintain.\n The structure and transport of CIP are described in (Ref. 1), as are\n general rules for the definition of index object types. This\n document describes SOIF, the Summary Object Interchange Format, as an\n index object type in the context of the CIP framework. SOIF is a\n machine-readable syntax for transmitting structured summary objects,\n currently used primarily in the context of the World Wide Web.\n\n Query referral has often been dismissed as an ineffective strategy\n for handling searches of Web resources, and Web resources certainly\n present challenges not present in structured directory services like\n Rwhois. In situations where a keyword-based free text search is\n desired, query r 2655 attribute attributes key registered nested-reference unchanged"},{"id":"IETF RFC 2656","type":"specification","body":"IETF","designation":"RFC 2656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2656.txt","https://www.rfc-editor.org/rfc/rfc2656.pdf"],"folder":"IETF/RFC-2656","files":{"txt":{"path":"standards/IETF/RFC-2656/RFC-2656.txt","sha256":"151d1c41081c4cc553abb498eba2609b862a263dd474becb200cda1d4277c3be"}},"tags":["nested-reference","unchanged"],"summary":"The Summary Object Interchange Format [Ref. 1] was first defined by\n the Harvest Project [Ref 2.] in January 1994. SOIF was derived from\n a combination of the Internet Anonymous FTP Archives IETF Working\n Group (IAFA) templates [Ref 3.] and the BibTeX bibliography format\n [Ref 4.]. The combination was originally noted for its advantages of\n providing a convenient and intuitive way for delimiting objects\n within a stream, and setting apart the URL for easy object access or\n invocation, while still preserving compatibility with IAFA templates.\n\n SOIF uses named template types to indicate the attributes which may\n be contained within a particular summary object. Within the context\n of a single application, private agreement on the definition of\n template types has been adequate. As SOIF objects are moved among\n applications, however, the need for standard, well-specified, and\n easily identi","scope_keywords":["2656","attribute","attributes","presentation","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2655","folder":"IETF/RFC-2655","source":"IETF/RFC-2655/RFC-2655.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2656 The Summary Object Interchange Format [Ref. 1] was first defined by\n the Harvest Project [Ref 2.] in January 1994. SOIF was derived from\n a combination of the Internet Anonymous FTP Archives IETF Working\n Group (IAFA) templates [Ref 3.] and the BibTeX bibliography format\n [Ref 4.]. The combination was originally noted for its advantages of\n providing a convenient and intuitive way for delimiting objects\n within a stream, and setting apart the URL for easy object access or\n invocation, while still preserving compatibility with IAFA templates.\n\n SOIF uses named template types to indicate the attributes which may\n be contained within a particular summary object. Within the context\n of a single application, private agreement on the definition of\n template types has been adequate. As SOIF objects are moved among\n applications, however, the need for standard, well-specified, and\n easily identi 2656 attribute attributes presentation registered subject nested-reference unchanged"},{"id":"IETF RFC 2849","type":"specification","body":"IETF","designation":"RFC 2849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2849.txt","https://www.rfc-editor.org/rfc/rfc2849.pdf"],"folder":"IETF/RFC-2849","files":{"txt":{"path":"standards/IETF/RFC-2849/RFC-2849.txt","sha256":"ce2f125a7a765b1cd19ff23e14517ee4148f3ed29a825e3d22a57a3f119acb07"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Good\nRequest for Comments: 2849 iPlanet e-commerce Solutions\nCategory: Standards Track June 2000\n\n The LDAP Data Interchange Format (LDIF) - Technical Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a file format suitable for describing\n directory information or modifications made to directory information.\n The file format, known as LDIF, for LDAP Data Interchange Format, is\n typically used to import and export directory i","scope_keywords":["2849","attribute","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"IETF RFC 2849 Network Working Group G. Good\nRequest for Comments: 2849 iPlanet e-commerce Solutions\nCategory: Standards Track June 2000\n\n The LDAP Data Interchange Format (LDIF) - Technical Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a file format suitable for describing\n directory information or modifications made to directory information.\n The file format, known as LDIF, for LDAP Data Interchange Format, is\n typically used to import and export directory i 2849 attribute key presentation nested-reference unchanged"},{"id":"IETF RFC 3729","type":"specification","body":"IETF","designation":"RFC 3729","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3729.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3729.txt","https://www.rfc-editor.org/rfc/rfc3729.pdf"],"folder":"IETF/RFC-3729","files":{"txt":{"path":"standards/IETF/RFC-3729/RFC-3729.txt","sha256":"897c25721ce280f828be6f83bfe4f070e7300d78bd9f408e75dd7c0ce1f9e68f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for measuring the application\n performance as experienced by end-users.","scope_keywords":["3729","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3729 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for measuring the application\n performance as experienced by end-users. 3729 management registered nested-reference unchanged"},{"id":"IETF RFC 4211","type":"specification","body":"IETF","designation":"RFC 4211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4211.txt","https://www.rfc-editor.org/rfc/rfc4211.pdf"],"folder":"IETF/RFC-4211","files":{"txt":{"path":"standards/IETF/RFC-4211/RFC-4211.txt","sha256":"efd9f0f7cd22bba1f6ba2d3e7bed0897c950ac055bf80c974d546c29823b6f74"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Certificate Request Message Format (CRMF)\n syntax and semantics. This syntax is used to convey a request for a\n certificate to a Certification Authority (CA), possibly via a\n Registration Authority (RA), for the purposes of X.509 certificate\n production. The request will typically include a public key and the\n associated registration information. This document does not define a\n certificate request protocol.\n\nSchaad Standards Track [Page 1]\n\f\nRFC 4211 Internet X.509 CRMF September 2005","scope_keywords":["4211","algorithm","algorithms","certificate","encryption","issuer","key","keys","pki","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null}],"search_text":"IETF RFC 4211 This document describes the Certificate Request Message Format (CRMF)\n syntax and semantics. This syntax is used to convey a request for a\n certificate to a Certification Authority (CA), possibly via a\n Registration Authority (RA), for the purposes of X.509 certificate\n production. The request will typically include a public key and the\n associated registration information. This document does not define a\n certificate request protocol.\n\nSchaad Standards Track [Page 1]\n\f\nRFC 4211 Internet X.509 CRMF September 2005 4211 algorithm algorithms certificate encryption issuer key keys pki signature subject nested-reference unchanged"},{"id":"IETF RFC 4516","type":"specification","body":"IETF","designation":"RFC 4516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4516.txt","https://www.rfc-editor.org/rfc/rfc4516.pdf"],"folder":"IETF/RFC-4516","files":{"txt":{"path":"standards/IETF/RFC-4516/RFC-4516.txt","sha256":"883d712ec48c7cd0993e647e7308d5c47a5c7b63bc967227b0ffd8d585638e4d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a format for a Lightweight Directory Access\n Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL\n describes an LDAP search operation that is used to retrieve\n information from an LDAP directory, or, in the context of an LDAP\n referral or reference, an LDAP URL describes a service where an LDAP\n operation may be progressed.","scope_keywords":["4516","attribute","attributes","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null}],"search_text":"IETF RFC 4516 This document describes a format for a Lightweight Directory Access\n Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL\n describes an LDAP search operation that is used to retrieve\n information from an LDAP directory, or, in the context of an LDAP\n referral or reference, an LDAP URL describes a service where an LDAP\n operation may be progressed. 4516 attribute attributes key subject nested-reference unchanged"},{"id":"IETF RFC 4823","type":"specification","body":"IETF","designation":"RFC 4823","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4823.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4823.txt","https://www.rfc-editor.org/rfc/rfc4823.pdf"],"folder":"IETF/RFC-4823","files":{"txt":{"path":"standards/IETF/RFC-4823/RFC-4823.txt","sha256":"5296208b86975e6eb5fcc471d8d10bafc7d31823c1f390a568d9b9c906d5ba16"}},"tags":["nested-reference","unchanged"],"summary":"This Applicability Statement (AS) describes how to exchange\n structured business data securely using the File Transfer Protocol\n (FTP) for XML, Binary, Electronic Data Interchange (EDI - ANSI X12 or\n UN/EDIFACT), or other data used for business-to-business data\n interchange for which MIME packaging can be accomplished using\n standard MIME content types. Authentication and data confidentiality\n are obtained by using Cryptographic Message Syntax (S/MIME) security\n body parts. Authenticated acknowledgements employ multipart/signed\n replies to the original message.\n\nHarding & Scott Informational [Page 1]\n\f\nRFC 4823 AS3 Data Interchange for EDIINT April 2007","scope_keywords":["4823","authentication","certificate","key","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4823 This Applicability Statement (AS) describes how to exchange\n structured business data securely using the File Transfer Protocol\n (FTP) for XML, Binary, Electronic Data Interchange (EDI - ANSI X12 or\n UN/EDIFACT), or other data used for business-to-business data\n interchange for which MIME packaging can be accomplished using\n standard MIME content types. Authentication and data confidentiality\n are obtained by using Cryptographic Message Syntax (S/MIME) security\n body parts. Authenticated acknowledgements employ multipart/signed\n replies to the original message.\n\nHarding & Scott Informational [Page 1]\n\f\nRFC 4823 AS3 Data Interchange for EDIINT April 2007 4823 authentication certificate key tls trust nested-reference unchanged"},{"id":"IETF RFC 5545","type":"specification","body":"IETF","designation":"RFC 5545","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5545.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5545.txt","https://www.rfc-editor.org/rfc/rfc5545.pdf"],"folder":"IETF/RFC-5545","files":{"txt":{"path":"standards/IETF/RFC-5545/RFC-5545.txt","sha256":"c256f809479d98aa23d71bbd1658b3800ea9f13f41ca56e59c8d2de1b31cbfcb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the iCalendar data format for representing and\nexchanging calendaring and scheduling information such as events,\nto-dos, journal entries, and free/busy information, independent of any\nparticular calendar service or protocol.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect o","scope_keywords":["5545","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5546","folder":"IETF/RFC-5546","source":"IETF/RFC-5546/RFC-5546.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null}],"search_text":"IETF RFC 5545 This document defines the iCalendar data format for representing and\nexchanging calendaring and scheduling information such as events,\nto-dos, journal entries, and free/busy information, independent of any\nparticular calendar service or protocol.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect o 5545 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6350","type":"specification","body":"IETF","designation":"RFC 6350","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6350.txt","https://www.rfc-editor.org/rfc/rfc6350.pdf"],"folder":"IETF/RFC-6350","files":{"txt":{"path":"standards/IETF/RFC-6350/RFC-6350.txt","sha256":"763c63b28fb9050111ee4878ea605e9e61ba2cb9f3c316bbbba936eda0dd1980"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the vCard data format for representing and\n exchanging a variety of information about individuals and other\n entities (e.g., formatted and structured name and delivery addresses,\n email address, multiple telephone numbers, photograph, logo, audio\n clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and\n updates RFC 2739.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edi","scope_keywords":["6350","delivery","http","identification","license","pid","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6351","folder":"IETF/RFC-6351","source":"IETF/RFC-6351/RFC-6351.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 6350 This document defines the vCard data format for representing and\n exchanging a variety of information about individuals and other\n entities (e.g., formatted and structured name and delivery addresses,\n email address, multiple telephone numbers, photograph, logo, audio\n clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and\n updates RFC 2739.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edi 6350 delivery http identification license pid subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 1747","type":"specification","body":"IETF","designation":"RFC 1747","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1747.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1747.txt","https://www.rfc-editor.org/rfc/rfc1747.pdf"],"folder":"IETF/RFC-1747","files":{"txt":{"path":"standards/IETF/RFC-1747/RFC-1747.txt","sha256":"90608377e4c56337278b3d1d14f1f6c2d3b47a92c1d89ca16513dcdb21675d79"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for managing the configuration,\n monitoring and control of data link controls in an SNA environment.\n This draft identifies managed objects for SNA Synchronous Data Link\n Control (SDLC) links only.","scope_keywords":["1747","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1747 This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for managing the configuration,\n monitoring and control of data link controls in an SNA environment.\n This draft identifies managed objects for SNA Synchronous Data Link\n Control (SDLC) links only. 1747 management nested-reference unchanged"},{"id":"IETF RFC 2405","type":"specification","body":"IETF","designation":"RFC 2405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2405.txt","https://www.rfc-editor.org/rfc/rfc2405.pdf"],"folder":"IETF/RFC-2405","files":{"txt":{"path":"standards/IETF/RFC-2405/RFC-2405.txt","sha256":"432337b060051e88986b9fbb09d41d24e40ddd3b10566bfe8ebc52fbf66f4a8b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the DES Cipher algorithm in Cipher\n Block Chaining Mode, with an explicit IV, as a confidentiality\n mechanism within the context of the IPSec Encapsulating Security\n Payload (ESP).\n\n1. Introduction\n\n This document describes the use of the DES Cipher algorithm in Cipher\n Block Chaining Mode as a confidentiality mechanism within the context\n of the Encapsulating Security Payload.\n\n DES is a symmetric block cipher algorithm. The algorithm is described\n in [FIPS-46-2][FIPS-74][FIPS-81]. [Schneier96] provides a general\n description of Cipher Block Chaining Mode, a mode which is applicable\n to several encryption algorithms.\n\n As specified in this memo, DES-CBC is not an authentication\n mechanism. [Although DES-MAC, described in [Schneier96] amongst other\n places, does provide authentication, DES-MAC is not discussed here.]\n\n For further information on how the","scope_keywords":["2405","algorithm","algorithms","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 2405 This document describes the use of the DES Cipher algorithm in Cipher\n Block Chaining Mode, with an explicit IV, as a confidentiality\n mechanism within the context of the IPSec Encapsulating Security\n Payload (ESP).\n\n1. Introduction\n\n This document describes the use of the DES Cipher algorithm in Cipher\n Block Chaining Mode as a confidentiality mechanism within the context\n of the Encapsulating Security Payload.\n\n DES is a symmetric block cipher algorithm. The algorithm is described\n in [FIPS-46-2][FIPS-74][FIPS-81]. [Schneier96] provides a general\n description of Cipher Block Chaining Mode, a mode which is applicable\n to several encryption algorithms.\n\n As specified in this memo, DES-CBC is not an authentication\n mechanism. [Although DES-MAC, described in [Schneier96] amongst other\n places, does provide authentication, DES-MAC is not discussed here.]\n\n For further information on how the 2405 algorithm algorithms authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2411","type":"specification","body":"IETF","designation":"RFC 2411","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2411.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2411.txt","https://www.rfc-editor.org/rfc/rfc2411.pdf"],"folder":"IETF/RFC-2411","files":{"txt":{"path":"standards/IETF/RFC-2411/RFC-2411.txt","sha256":"233b329f2518e76ca27aa1a032c6712fa46c358696c20fe1697be113f57e485f"}},"tags":["nested-reference","unchanged"],"summary":"The IPsec protocol suite is used to provide privacy and\n authentication services at the IP layer. Several documents are used\n to describe this protocol suite. The interrelationship and\n organization of the various documents covering the IPsec protocol are\n discussed here. An explanation of what to find in which document,\n and what to include in new Encryption Algorithm and Authentication\n Algorithm documents are described.","scope_keywords":["2411","algorithm","algorithms","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4494","folder":"IETF/RFC-4494","source":"IETF/RFC-4494/RFC-4494.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 2411 The IPsec protocol suite is used to provide privacy and\n authentication services at the IP layer. Several documents are used\n to describe this protocol suite. The interrelationship and\n organization of the various documents covering the IPsec protocol are\n discussed here. An explanation of what to find in which document,\n and what to include in new Encryption Algorithm and Authentication\n Algorithm documents are described. 2411 algorithm algorithms authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 2412","type":"specification","body":"IETF","designation":"RFC 2412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2412.txt","https://www.rfc-editor.org/rfc/rfc2412.pdf"],"folder":"IETF/RFC-2412","files":{"txt":{"path":"standards/IETF/RFC-2412/RFC-2412.txt","sha256":"52d755b39cdcc5e227fac5d0e61d1e611f592bb3a44148f731c3e95deb00ba9e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol, named OAKLEY, by which two\n authenticated parties can agree on secure and secret keying material.\n The basic mechanism is the Diffie-Hellman key exchange algorithm.\n\n The OAKLEY protocol supports Perfect Forward Secrecy, compatibility\n with the ISAKMP protocol for managing security associations, user-\n defined abstract group structures for use with the Diffie-Hellman\n algorithm, key updates, and incorporation of keys distributed via\n out-of-band mechanisms.\n\n1. INTRODUCTION\n\n Key establishment is the heart of data protection that relies on\n cryptography, and it is an essential component of the packet\n protection mechanisms described in [RFC2401], for example. A\n scalable and secure key distribution mechanism for the Internet is a\n necessity. The goal of this protocol is to provide that mechanism,\n coupled with a great deal of cryptographic strength.\n\n ","scope_keywords":["2412","algorithm","algorithms","authentication","encryption","identification","key","keys","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3526","folder":"IETF/RFC-3526","source":"IETF/RFC-3526/RFC-3526.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2412 This document describes a protocol, named OAKLEY, by which two\n authenticated parties can agree on secure and secret keying material.\n The basic mechanism is the Diffie-Hellman key exchange algorithm.\n\n The OAKLEY protocol supports Perfect Forward Secrecy, compatibility\n with the ISAKMP protocol for managing security associations, user-\n defined abstract group structures for use with the Diffie-Hellman\n algorithm, key updates, and incorporation of keys distributed via\n out-of-band mechanisms.\n\n1. INTRODUCTION\n\n Key establishment is the heart of data protection that relies on\n cryptography, and it is an essential component of the packet\n protection mechanisms described in [RFC2401], for example. A\n scalable and secure key distribution mechanism for the Internet is a\n necessity. The goal of this protocol is to provide that mechanism,\n coupled with a great deal of cryptographic strength.\n\n  2412 algorithm algorithms authentication encryption identification key keys presentation validation nested-reference unchanged"},{"id":"IETF RFC 2857","type":"specification","body":"IETF","designation":"RFC 2857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2857.txt","https://www.rfc-editor.org/rfc/rfc2857.pdf"],"folder":"IETF/RFC-2857","files":{"txt":{"path":"standards/IETF/RFC-2857/RFC-2857.txt","sha256":"770f5c6e9fdea5fedcffae851787280fa9d97f692c05bc0e2c26225290e36614"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the HMAC algorithm [RFC 2104] in\n conjunction with the RIPEMD-160 algorithm [RIPEMD-160] as an\n authentication mechanism within the revised IPSEC Encapsulating\n Security Payload [ESP] and the revised IPSEC Authentication Header\n [AH]. HMAC with RIPEMD-160 provides data origin authentication and\n integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of RIPEMD-160 [RIPEMD-160] combined with\n HMAC [RFC 2104] as a keyed authentication mechanism within the\n context of the Encapsulating Security Payload and the Authentication\n Header. The goal of HMAC-RIPEMD-160-96 is to ensure that the packet\n is authentic and cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authenticatio","scope_keywords":["2857","algorithm","algorithms","authentication","hash","hashing","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 2857 This memo describes the use of the HMAC algorithm [RFC 2104] in\n conjunction with the RIPEMD-160 algorithm [RIPEMD-160] as an\n authentication mechanism within the revised IPSEC Encapsulating\n Security Payload [ESP] and the revised IPSEC Authentication Header\n [AH]. HMAC with RIPEMD-160 provides data origin authentication and\n integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of RIPEMD-160 [RIPEMD-160] combined with\n HMAC [RFC 2104] as a keyed authentication mechanism within the\n context of the Encapsulating Security Payload and the Authentication\n Header. The goal of HMAC-RIPEMD-160-96 is to ensure that the packet\n is authentic and cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authenticatio 2857 algorithm algorithms authentication hash hashing key keys management nested-reference unchanged"},{"id":"IETF RFC 2919","type":"specification","body":"IETF","designation":"RFC 2919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2919.txt","https://www.rfc-editor.org/rfc/rfc2919.pdf"],"folder":"IETF/RFC-2919","files":{"txt":{"path":"standards/IETF/RFC-2919/RFC-2919.txt","sha256":"aa78f55f7182a3d67dabdf861d27cfe0d0d47e5fd3565d71f9ed4a9d95458bb8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Chandhok\nRequest for Comments: 2919 G. Wenger\nCategory: Standards Track QUALCOMM, Inc.\n March 2001\n\n List-Id:\n A Structured Field and Namespace for the\n Identification of Mailing Lists\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n Software that handles electronic mailing list messages (servers and\n user agents) needs a way to reliably identify messages that belong to\n a particular mailing list. With the advent of list management\n headers, it has become even ","scope_keywords":["2919","attribute","delivery","holder","identification","key","management","policy","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null}],"search_text":"IETF RFC 2919 Network Working Group R. Chandhok\nRequest for Comments: 2919 G. Wenger\nCategory: Standards Track QUALCOMM, Inc.\n March 2001\n\n List-Id:\n A Structured Field and Namespace for the\n Identification of Mailing Lists\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n Software that handles electronic mailing list messages (servers and\n user agents) needs a way to reliably identify messages that belong to\n a particular mailing list. With the advent of list management\n headers, it has become even  2919 attribute delivery holder identification key management policy qualified subject nested-reference unchanged"},{"id":"IETF RFC 2951","type":"specification","body":"IETF","designation":"RFC 2951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2951.txt","https://www.rfc-editor.org/rfc/rfc2951.pdf"],"folder":"IETF/RFC-2951","files":{"txt":{"path":"standards/IETF/RFC-2951/RFC-2951.txt","sha256":"a40ec1ca5069fdd9aaa7d2f28b9fe143f46dc58c3d25afbcffc0c0aef4d16f29"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a method to authenticate TELNET using the Key\n Exchange Algorithm (KEA), and encryption of the TELNET stream using\n SKIPJACK. Two encryption modes are specified; one provides data\n integrity and the other does not. The method relies on the TELNET\n Authentication Option.\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n\n Authentication Commands:\n\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types:\n\n KEA_SJ 12\n KEA_SJ_INTEG 13\n\n Modifiers:\n\n AUTH_WHO_MASK 1\n AUTH_CLIENT_TO_SERVER 0\n AUTH_SERVER_TO CLIENT 1\n\nHousley, et al. Informational [Page 1]\n\f\nRFC 2951 TELNET Authentication Using KEA & SKIPJACK September 2000\n\n AUTH_HOW_MASK 2\n AUTH_HOW_ONE_WAY 0\n AUTH_HOW_MUTUAL 2\n\n ENCRYPT_MASK 20\n ENCRYPT_OFF 0\n ENCRYPT_USING_TELOPT 4\n ENCRYPT_AFTER_EXCHANGE 16\n ENCRYPT_RESERVED 20\n\n INI_CRED_FWD_MASK 8\n INI_CRED_FWD_OFF 0\n INI_CRED_FWD_ON 8\n\n Sub-option Commands:\n\n KEA_CERTA","scope_keywords":["2951","algorithm","attribute","attributes","authentication","authorization","certificate","certificates","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null}],"search_text":"IETF RFC 2951 This document defines a method to authenticate TELNET using the Key\n Exchange Algorithm (KEA), and encryption of the TELNET stream using\n SKIPJACK. Two encryption modes are specified; one provides data\n integrity and the other does not. The method relies on the TELNET\n Authentication Option.\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n\n Authentication Commands:\n\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types:\n\n KEA_SJ 12\n KEA_SJ_INTEG 13\n\n Modifiers:\n\n AUTH_WHO_MASK 1\n AUTH_CLIENT_TO_SERVER 0\n AUTH_SERVER_TO CLIENT 1\n\nHousley, et al. Informational [Page 1]\n\f\nRFC 2951 TELNET Authentication Using KEA & SKIPJACK September 2000\n\n AUTH_HOW_MASK 2\n AUTH_HOW_ONE_WAY 0\n AUTH_HOW_MUTUAL 2\n\n ENCRYPT_MASK 20\n ENCRYPT_OFF 0\n ENCRYPT_USING_TELOPT 4\n ENCRYPT_AFTER_EXCHANGE 16\n ENCRYPT_RESERVED 20\n\n INI_CRED_FWD_MASK 8\n INI_CRED_FWD_OFF 0\n INI_CRED_FWD_ON 8\n\n Sub-option Commands:\n\n KEA_CERTA 2951 algorithm attribute attributes authentication authorization certificate certificates encryption key keys nested-reference unchanged"},{"id":"IETF RFC 3217","type":"specification","body":"IETF","designation":"RFC 3217","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3217.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3217.txt","https://www.rfc-editor.org/rfc/rfc3217.pdf"],"folder":"IETF/RFC-3217","files":{"txt":{"path":"standards/IETF/RFC-3217/RFC-3217.txt","sha256":"e188cec693fcdef17b6653e1cf35a9d28d01d52b1207c1ede60480b0231be0ba"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the algorithm for wrapping one Triple-DES key\n with another Triple-DES key and the algorithm for wrapping one RC2\n key with another RC2 key. These key wrap algorithms were originally\n published in section 12.6 of RFC 2630. They are republished since\n these key wrap algorithms have been found to be useful in contexts\n beyond those supported by RFC 2630.\n\n1 Introduction\n\n Management of symmetric cryptographic keys often leads to situations\n where one symmetric key is used to encrypt (or wrap) another. Key\n wrap algorithms are commonly used in two situations. First, key\n agreement algorithms (such as Diffie-Hellman [DH-X9.42]) generate a\n pairwise key-encryption key, and a key wrap algorithm is used to\n encrypt the content-encryption key or a multicast key with the\n pairwise key-encryption key. Second, a key wrap algorithm is used to\n encrypt the content-encryption k","scope_keywords":["3217","algorithm","algorithms","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null}],"search_text":"IETF RFC 3217 This document specifies the algorithm for wrapping one Triple-DES key\n with another Triple-DES key and the algorithm for wrapping one RC2\n key with another RC2 key. These key wrap algorithms were originally\n published in section 12.6 of RFC 2630. They are republished since\n these key wrap algorithms have been found to be useful in contexts\n beyond those supported by RFC 2630.\n\n1 Introduction\n\n Management of symmetric cryptographic keys often leads to situations\n where one symmetric key is used to encrypt (or wrap) another. Key\n wrap algorithms are commonly used in two situations. First, key\n agreement algorithms (such as Diffie-Hellman [DH-X9.42]) generate a\n pairwise key-encryption key, and a key wrap algorithm is used to\n encrypt the content-encryption key or a multicast key with the\n pairwise key-encryption key. Second, a key wrap algorithm is used to\n encrypt the content-encryption k 3217 algorithm algorithms encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 3307","type":"specification","body":"IETF","designation":"RFC 3307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3307.txt","https://www.rfc-editor.org/rfc/rfc3307.pdf"],"folder":"IETF/RFC-3307","files":{"txt":{"path":"standards/IETF/RFC-3307/RFC-3307.txt","sha256":"565c0d1a837b04579ae4618f824dc3ec018d3a0a0ac88c2447dde7ff17060300"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies guidelines that must be implemented by any\n entity responsible for allocating IPv6 multicast addresses. This\n includes, but is not limited to, any documents or entities wishing to\n assign permanent IPv6 multicast addresses, allocate dynamic IPv6\n multicast addresses, and define permanent IPv6 multicast group\n identifiers. The purpose of these guidelines is to reduce the\n probability of IPv6 multicast address collision, not only at the IPv6\n layer, but also at the link-layer of media that encode portions of\n the IP layer address into the MAC layer address.\n\nHaberman Standards Track [Page 1]\n\f\nRFC 3307 IPv6 Multicast Addresses Guidelines August 2002","scope_keywords":["3307","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 3307 This document specifies guidelines that must be implemented by any\n entity responsible for allocating IPv6 multicast addresses. This\n includes, but is not limited to, any documents or entities wishing to\n assign permanent IPv6 multicast addresses, allocate dynamic IPv6\n multicast addresses, and define permanent IPv6 multicast group\n identifiers. The purpose of these guidelines is to reduce the\n probability of IPv6 multicast address collision, not only at the IPv6\n layer, but also at the link-layer of media that encode portions of\n the IP layer address into the MAC layer address.\n\nHaberman Standards Track [Page 1]\n\f\nRFC 3307 IPv6 Multicast Addresses Guidelines August 2002 3307 key nested-reference unchanged"},{"id":"IETF RFC 3369","type":"specification","body":"IETF","designation":"RFC 3369","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3369.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3369.txt","https://www.rfc-editor.org/rfc/rfc3369.pdf"],"folder":"IETF/RFC-3369","files":{"txt":{"path":"standards/IETF/RFC-3369/RFC-3369.txt","sha256":"ebd4dcb52e517ff45dc8d3798b3392c3f33ad7c1a64b2c974a7e7fc19103a3b3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content.","scope_keywords":["3369","algorithm","attribute","attributes","authentication","certificate","certificates","encryption","issuer","key","management","pki","profile","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null}],"search_text":"IETF RFC 3369 This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content. 3369 algorithm attribute attributes authentication certificate certificates encryption issuer key management pki profile revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 3514","type":"specification","body":"IETF","designation":"RFC 3514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3514.txt","https://www.rfc-editor.org/rfc/rfc3514.pdf"],"folder":"IETF/RFC-3514","files":{"txt":{"path":"standards/IETF/RFC-3514/RFC-3514.txt","sha256":"5f97a7c140f6066c83e09dd686504f835a59557658a4289448a38eb177562c65"}},"tags":["nested-reference","unchanged"],"summary":"Firewalls, packet filters, intrusion detection systems, and the like\n often have difficulty distinguishing between packets that have\n malicious intent and those that are merely unusual. We define a\n security flag in the IPv4 header as a means of distinguishing the two\n cases.\n\n1. Introduction\n\n Firewalls [CBR03], packet filters, intrusion detection systems, and\n the like often have difficulty distinguishing between packets that\n have malicious intent and those that are merely unusual. The problem\n is that making such determinations is hard. To solve this problem,\n we define a security flag, known as the \"evil\" bit, in the IPv4\n [RFC791] header. Benign packets have this bit set to 0; those that\n are used for an attack will have the bit set to 1.","scope_keywords":["3514","http","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null}],"search_text":"IETF RFC 3514 Firewalls, packet filters, intrusion detection systems, and the like\n often have difficulty distinguishing between packets that have\n malicious intent and those that are merely unusual. We define a\n security flag in the IPv4 header as a means of distinguishing the two\n cases.\n\n1. Introduction\n\n Firewalls [CBR03], packet filters, intrusion detection systems, and\n the like often have difficulty distinguishing between packets that\n have malicious intent and those that are merely unusual. The problem\n is that making such determinations is hard. To solve this problem,\n we define a security flag, known as the \"evil\" bit, in the IPv4\n [RFC791] header. Benign packets have this bit set to 0; those that\n are used for an attack will have the bit set to 1. 3514 http key signature nested-reference unchanged"},{"id":"IETF RFC 3537","type":"specification","body":"IETF","designation":"RFC 3537","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3537.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3537.txt","https://www.rfc-editor.org/rfc/rfc3537.pdf"],"folder":"IETF/RFC-3537","files":{"txt":{"path":"standards/IETF/RFC-3537/RFC-3537.txt","sha256":"a4c40a31b30f493803831a6457de22f663a72077a7eef5eddbe983b2010132ca"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two methods for wrapping an HMAC (Hashed\n Message Authentication Code) key. The first method defined uses a\n Triple DES (Data Encryption Standard) key to encrypt the HMAC key.\n The second method defined uses an AES (Advanced Encryption Standard)\n key to encrypt the HMAC key. One place that such an algorithm is\n used is for the Authenticated Data type in CMS (Cryptographic Message\n Syntax).\n\n1. Introduction\n\n Standard methods exist for encrypting a Triple-DES (3DES) content-\n encryption key (CEK) with a 3DES key-encryption key (KEK) [3DES-\n WRAP], and for encrypting an AES CEK with an AES KEK [AES-WRAP].\n Triple-DES key wrap imposes parity restrictions, and in both\n instances there are restrictions on the size of the key being wrapped\n that make the encryption of HMAC [HMAC] keying material difficult.\n\n This document specifies a mechanism for the encryption of an HMA","scope_keywords":["3537","algorithm","algorithms","authentication","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null}],"search_text":"IETF RFC 3537 This document defines two methods for wrapping an HMAC (Hashed\n Message Authentication Code) key. The first method defined uses a\n Triple DES (Data Encryption Standard) key to encrypt the HMAC key.\n The second method defined uses an AES (Advanced Encryption Standard)\n key to encrypt the HMAC key. One place that such an algorithm is\n used is for the Authenticated Data type in CMS (Cryptographic Message\n Syntax).\n\n1. Introduction\n\n Standard methods exist for encrypting a Triple-DES (3DES) content-\n encryption key (CEK) with a 3DES key-encryption key (KEK) [3DES-\n WRAP], and for encrypting an AES CEK with an AES KEK [AES-WRAP].\n Triple-DES key wrap imposes parity restrictions, and in both\n instances there are restrictions on the size of the key being wrapped\n that make the encryption of HMAC [HMAC] keying material difficult.\n\n This document specifies a mechanism for the encryption of an HMA 3537 algorithm algorithms authentication encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 3539","type":"specification","body":"IETF","designation":"RFC 3539","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3539.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3539.txt","https://www.rfc-editor.org/rfc/rfc3539.pdf"],"folder":"IETF/RFC-3539","files":{"txt":{"path":"standards/IETF/RFC-3539/RFC-3539.txt","sha256":"390f8376123e999230834728cc3c00afbe6a27b3e7cca6d92f84008f744ada66"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses transport issues that arise within protocols\n for Authentication, Authorization and Accounting (AAA). It also\n provides recommendations on the use of transport by AAA protocols.\n This includes usage of standards-track RFCs as well as experimental\n proposals.","scope_keywords":["3539","algorithm","attribute","audit","authentication","authorization","credential","key","policies","profile","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 3539 This document discusses transport issues that arise within protocols\n for Authentication, Authorization and Accounting (AAA). It also\n provides recommendations on the use of transport by AAA protocols.\n This includes usage of standards-track RFCs as well as experimental\n proposals. 3539 algorithm attribute audit authentication authorization credential key policies profile validation nested-reference unchanged"},{"id":"IETF RFC 3560","type":"specification","body":"IETF","designation":"RFC 3560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3560.txt","https://www.rfc-editor.org/rfc/rfc3560.pdf"],"folder":"IETF/RFC-3560","files":{"txt":{"path":"standards/IETF/RFC-3560/RFC-3560.txt","sha256":"2985a9576da01036d97d1626ff2fdbc1b099bd5661a86e311a2c112127f30bcf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the RSAES-OAEP key\n transport algorithm with the Cryptographic Message Syntax (CMS). The\n CMS specifies the enveloped-data content type, which consists of an\n encrypted content and encrypted content-encryption keys for one or\n more recipients. The RSAES-OAEP key transport algorithm can be used\n to encrypt content-encryption keys for intended recipients.","scope_keywords":["3560","algorithm","algorithms","attribute","certificate","encryption","issuer","key","keys","management","pki","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3560 This document describes the conventions for using the RSAES-OAEP key\n transport algorithm with the Cryptographic Message Syntax (CMS). The\n CMS specifies the enveloped-data content type, which consists of an\n encrypted content and encrypted content-encryption keys for one or\n more recipients. The RSAES-OAEP key transport algorithm can be used\n to encrypt content-encryption keys for intended recipients. 3560 algorithm algorithms attribute certificate encryption issuer key keys management pki profile tls nested-reference unchanged"},{"id":"IETF RFC 3562","type":"specification","body":"IETF","designation":"RFC 3562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3562.txt","https://www.rfc-editor.org/rfc/rfc3562.pdf"],"folder":"IETF/RFC-3562","files":{"txt":{"path":"standards/IETF/RFC-3562/RFC-3562.txt","sha256":"b3886a9a59b7b05cfbfef1ee9d812faf6aaf9c4027b9fef5fd8293b6287e99cc"}},"tags":["nested-reference","unchanged"],"summary":"The TCP MD5 Signature Option (RFC 2385), used predominantly by BGP,\n has seen significant deployment in critical areas of Internet\n infrastructure. The security of this option relies heavily on the\n quality of the keying material used to compute the MD5 signature.\n This document addresses the security requirements of that keying\n material.\n\n1. Introduction\n\n The security of various cryptographic functions lies both in the\n strength of the functions themselves against various forms of attack,\n and also, perhaps more importantly, in the keying material that is\n used with them. While theoretical attacks against the simple MAC\n construction used in RFC 2385 are possible [MDXMAC], the number of\n text-MAC pairs required to mount a forgery make it vastly more\n probable that key-guessing is the main threat against RFC 2385.\n\n We show a quantitative approach to determining the security\n requireme","scope_keywords":["3562","authentication","key","keys","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4278","folder":"IETF/RFC-4278","source":"IETF/RFC-4278/RFC-4278.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null}],"search_text":"IETF RFC 3562 The TCP MD5 Signature Option (RFC 2385), used predominantly by BGP,\n has seen significant deployment in critical areas of Internet\n infrastructure. The security of this option relies heavily on the\n quality of the keying material used to compute the MD5 signature.\n This document addresses the security requirements of that keying\n material.\n\n1. Introduction\n\n The security of various cryptographic functions lies both in the\n strength of the functions themselves against various forms of attack,\n and also, perhaps more importantly, in the keying material that is\n used with them. While theoretical attacks against the simple MAC\n construction used in RFC 2385 are possible [MDXMAC], the number of\n text-MAC pairs required to mount a forgery make it vastly more\n probable that key-guessing is the main threat against RFC 2385.\n\n We show a quantitative approach to determining the security\n requireme 3562 authentication key keys management signature nested-reference unchanged"},{"id":"IETF RFC 3565","type":"specification","body":"IETF","designation":"RFC 3565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3565.txt","https://www.rfc-editor.org/rfc/rfc3565.pdf"],"folder":"IETF/RFC-3565","files":{"txt":{"path":"standards/IETF/RFC-3565/RFC-3565.txt","sha256":"c0d1599fac901f8b1a7480a1ca77715021b76af892970cbca2317fe49905550b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the Advanced\n Encryption Standard (AES) algorithm for encryption with the\n Cryptographic Message Syntax (CMS).\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [MUSTSHOULD].\n\n1. Overview\n\n This document specifies the conventions for using Advanced Encryption\n Standard (AES) content encryption algorithm with the Cryptographic\n Message Syntax [CMS] enveloped-data and encrypted-data content types.\n\n CMS values are generated using ASN.1 [X.208-88], using the Basic\n Encoding Rules (BER) [X.209-88] and the Distinguished Encoding Rules\n (DER) [X.509-88].\n\nSchaad Standards Track [Page 1]\n\f\nRFC 3565 Use of the AES Encryption Algorithm in CMS July 2003","scope_keywords":["3565","algorithm","algorithms","certificate","encryption","issuer","key","keys","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3565 This document specifies the conventions for using the Advanced\n Encryption Standard (AES) algorithm for encryption with the\n Cryptographic Message Syntax (CMS).\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [MUSTSHOULD].\n\n1. Overview\n\n This document specifies the conventions for using Advanced Encryption\n Standard (AES) content encryption algorithm with the Cryptographic\n Message Syntax [CMS] enveloped-data and encrypted-data content types.\n\n CMS values are generated using ASN.1 [X.208-88], using the Basic\n Encoding Rules (BER) [X.209-88] and the Distinguished Encoding Rules\n (DER) [X.509-88].\n\nSchaad Standards Track [Page 1]\n\f\nRFC 3565 Use of the AES Encryption Algorithm in CMS July 2003 3565 algorithm algorithms certificate encryption issuer key keys management subject nested-reference unchanged"},{"id":"IETF RFC 3697","type":"specification","body":"IETF","designation":"RFC 3697","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3697.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3697.txt","https://www.rfc-editor.org/rfc/rfc3697.pdf"],"folder":"IETF/RFC-3697","files":{"txt":{"path":"standards/IETF/RFC-3697/RFC-3697.txt","sha256":"a82a033eee05951bc37a0e6cb1321d91e809ca6ff1ccf65432480bd12d4c37e9"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IPv6 Flow Label field and the minimum\n requirements for IPv6 source nodes labeling flows, IPv6 nodes\n forwarding labeled packets, and flow state establishment methods.\n Even when mentioned as examples of possible uses of the flow\n labeling, more detailed requirements for specific use cases are out\n of scope for this document.\n\n The usage of the Flow Label field enables efficient IPv6 flow\n classification based only on IPv6 main header fields in fixed\n positions.\n\n1. Introduction\n\n A flow is a sequence of packets sent from a particular source to a\n particular unicast, anycast, or multicast destination that the source\n desires to label as a flow. A flow could consist of all packets in a\n specific transport connection or a media stream. However, a flow is\n not necessarily 1:1 mapped to a transport connection.\n\nRajahalme, et al. Standards Track [Page 1]\n\f\nRFC 3697","scope_keywords":["3697","encryption","hash","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null}],"search_text":"IETF RFC 3697 This document specifies the IPv6 Flow Label field and the minimum\n requirements for IPv6 source nodes labeling flows, IPv6 nodes\n forwarding labeled packets, and flow state establishment methods.\n Even when mentioned as examples of possible uses of the flow\n labeling, more detailed requirements for specific use cases are out\n of scope for this document.\n\n The usage of the Flow Label field enables efficient IPv6 flow\n classification based only on IPv6 main header fields in fixed\n positions.\n\n1. Introduction\n\n A flow is a sequence of packets sent from a particular source to a\n particular unicast, anycast, or multicast destination that the source\n desires to label as a flow. A flow could consist of all packets in a\n specific transport connection or a media stream. However, a flow is\n not necessarily 1:1 mapped to a transport connection.\n\nRajahalme, et al. Standards Track [Page 1]\n\f\nRFC 3697 3697 encryption hash key subject nested-reference unchanged"},{"id":"IETF RFC 3711","type":"specification","body":"IETF","designation":"RFC 3711","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3711.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3711.txt","https://www.rfc-editor.org/rfc/rfc3711.pdf"],"folder":"IETF/RFC-3711","files":{"txt":{"path":"standards/IETF/RFC-3711/RFC-3711.txt","sha256":"dc58e15fd6f450cd64eb38105362e52e78701ed995b05bf80ca12bb0c3a9c324"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Secure Real-time Transport Protocol\n (SRTP), a profile of the Real-time Transport Protocol (RTP), which\n can provide confidentiality, message authentication, and replay\n protection to the RTP traffic and to the control traffic for RTP, the\n Real-time Transport Control Protocol (RTCP).","scope_keywords":["3711","algorithm","authentication","encryption","hash","hashing","key","management","profile","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3951","folder":"IETF/RFC-3951","source":"IETF/RFC-3951/RFC-3951.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4534","folder":"IETF/RFC-4534","source":"IETF/RFC-4534/RFC-4534.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4771","folder":"IETF/RFC-4771","source":"IETF/RFC-4771/RFC-4771.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6188","folder":"IETF/RFC-6188","source":"IETF/RFC-6188/RFC-6188.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6562","folder":"IETF/RFC-6562","source":"IETF/RFC-6562/RFC-6562.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3711 This document describes the Secure Real-time Transport Protocol\n (SRTP), a profile of the Real-time Transport Protocol (RTP), which\n can provide confidentiality, message authentication, and replay\n protection to the RTP traffic and to the control traffic for RTP, the\n Real-time Transport Control Protocol (RTCP). 3711 algorithm authentication encryption hash hashing key management profile risk nested-reference unchanged"},{"id":"IETF RFC 3766","type":"specification","body":"IETF","designation":"RFC 3766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3766.txt","https://www.rfc-editor.org/rfc/rfc3766.pdf"],"folder":"IETF/RFC-3766","files":{"txt":{"path":"standards/IETF/RFC-3766/RFC-3766.txt","sha256":"433aab6e88b37b4280a1ebb80deb1467dfcc11cc0b5944c0b15476728310d547"}},"tags":["nested-reference","unchanged"],"summary":"Implementors of systems that use public key cryptography to exchange\n symmetric keys need to make the public keys resistant to some\n predetermined level of attack. That level of attack resistance is\n the strength of the system, and the symmetric keys that are exchanged\n must be at least as strong as the system strength requirements. The\n three quantities, system strength, symmetric key strength, and public\n key strength, must be consistently matched for any network protocol\n usage.\n\n While it is fairly easy to express the system strength requirements\n in terms of a symmetric key length and to choose a cipher that has a\n key length equal to or exceeding that requirement, it is harder to\n choose a public key that has a cryptographic strength meeting a\n symmetric key strength requirement. This document explains how to\n determine the length of an asymmetric key as a function of a\n symmetric ","scope_keywords":["3766","algorithm","algorithms","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 3766 Implementors of systems that use public key cryptography to exchange\n symmetric keys need to make the public keys resistant to some\n predetermined level of attack. That level of attack resistance is\n the strength of the system, and the symmetric keys that are exchanged\n must be at least as strong as the system strength requirements. The\n three quantities, system strength, symmetric key strength, and public\n key strength, must be consistently matched for any network protocol\n usage.\n\n While it is fairly easy to express the system strength requirements\n in terms of a symmetric key length and to choose a cipher that has a\n key length equal to or exceeding that requirement, it is harder to\n choose a public key that has a cryptographic strength meeting a\n symmetric key strength requirement. This document explains how to\n determine the length of an asymmetric key as a function of a\n symmetric  3766 algorithm algorithms encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 3851","type":"specification","body":"IETF","designation":"RFC 3851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3851.txt","https://www.rfc-editor.org/rfc/rfc3851.pdf"],"folder":"IETF/RFC-3851","files":{"txt":{"path":"standards/IETF/RFC-3851/RFC-3851.txt","sha256":"3752e48946be70f5fa7cc514a2f2d6bf013af83dd326924b3918cad2cb4d2b0f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 3.1. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 2633.","scope_keywords":["3851","algorithm","attribute","attributes","authentication","certificate","encryption","http","key","management","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4073","folder":"IETF/RFC-4073","source":"IETF/RFC-4073/RFC-4073.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4134","folder":"IETF/RFC-4134","source":"IETF/RFC-4134/RFC-4134.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4262","folder":"IETF/RFC-4262","source":"IETF/RFC-4262/RFC-4262.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 3851 This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 3.1. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 2633. 3851 algorithm attribute attributes authentication certificate encryption http key management signature signatures nested-reference unchanged"},{"id":"IETF RFC 3852","type":"specification","body":"IETF","designation":"RFC 3852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3852.txt","https://www.rfc-editor.org/rfc/rfc3852.pdf"],"folder":"IETF/RFC-3852","files":{"txt":{"path":"standards/IETF/RFC-3852/RFC-3852.txt","sha256":"1d5415b9e24f83ad7c8d44b8d94ebf7bb563f930f5bf2adbaed6d3740ac47920"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content.","scope_keywords":["3852","algorithm","attribute","attributes","authentication","certificate","certificates","encryption","issuer","key","management","pki","profile","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3874","folder":"IETF/RFC-3874","source":"IETF/RFC-3874/RFC-3874.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4027","folder":"IETF/RFC-4027","source":"IETF/RFC-4027/RFC-4027.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4049","folder":"IETF/RFC-4049","source":"IETF/RFC-4049/RFC-4049.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4073","folder":"IETF/RFC-4073","source":"IETF/RFC-4073/RFC-4073.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4134","folder":"IETF/RFC-4134","source":"IETF/RFC-4134/RFC-4134.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4231","folder":"IETF/RFC-4231","source":"IETF/RFC-4231/RFC-4231.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4534","folder":"IETF/RFC-4534","source":"IETF/RFC-4534/RFC-4534.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4853","folder":"IETF/RFC-4853","source":"IETF/RFC-4853/RFC-4853.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5083","folder":"IETF/RFC-5083","source":"IETF/RFC-5083/RFC-5083.txt","version":null},{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5091","folder":"IETF/RFC-5091","source":"IETF/RFC-5091/RFC-5091.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3852 This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content. 3852 algorithm attribute attributes authentication certificate certificates encryption issuer key management pki profile revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 3885","type":"specification","body":"IETF","designation":"RFC 3885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3885.txt","https://www.rfc-editor.org/rfc/rfc3885.pdf"],"folder":"IETF/RFC-3885","files":{"txt":{"path":"standards/IETF/RFC-3885/RFC-3885.txt","sha256":"d5701fded4e50e1e3bfc957dc7ec3954b2b74e1bf051e8f9cb2faefdd783c1a4"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby a client\n may mark a message for future tracking.\n\n1. Other Documents and Conformance\n\n The model used for Message Tracking is described in [RFC-MTRK-MODEL].\n\n Doing a Message Tracking query is intended as a \"last resort\"\n mechanism. Normally, Delivery Status Notifications (DSNs) [RFC-DSN-\n SMTP] and Message Disposition Notifications (MDNs) [RFC-MDN] would\n provide the primary delivery status. Only if the message is not\n received, or there is no response from either of these mechanisms\n should a Message Tracking query be issued.\n\n The definition of the base64 token is imported from section 6.8 of\n [RFC-MIME]. Formally,\n\n base64 = %x2b / %x2f / %x30-39 / %x41-5a / %x61-7a\n\nAllman & Hansen Standards Track [Page 1]\n\f\nRFC 3885 Message Tracking ESMTP Extension September 2004\n\n The definition of the DIGIT token is imported from [RFC-MS","scope_keywords":["3885","algorithm","delivery","hash","key","path","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 3885 This memo defines an extension to the SMTP service whereby a client\n may mark a message for future tracking.\n\n1. Other Documents and Conformance\n\n The model used for Message Tracking is described in [RFC-MTRK-MODEL].\n\n Doing a Message Tracking query is intended as a \"last resort\"\n mechanism. Normally, Delivery Status Notifications (DSNs) [RFC-DSN-\n SMTP] and Message Disposition Notifications (MDNs) [RFC-MDN] would\n provide the primary delivery status. Only if the message is not\n received, or there is no response from either of these mechanisms\n should a Message Tracking query be issued.\n\n The definition of the base64 token is imported from section 6.8 of\n [RFC-MIME]. Formally,\n\n base64 = %x2b / %x2f / %x30-39 / %x41-5a / %x61-7a\n\nAllman & Hansen Standards Track [Page 1]\n\f\nRFC 3885 Message Tracking ESMTP Extension September 2004\n\n The definition of the DIGIT token is imported from [RFC-MS 3885 algorithm delivery hash key path policy qualified nested-reference unchanged"},{"id":"IETF RFC 3957","type":"specification","body":"IETF","designation":"RFC 3957","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3957.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3957.txt","https://www.rfc-editor.org/rfc/rfc3957.pdf"],"folder":"IETF/RFC-3957","files":{"txt":{"path":"standards/IETF/RFC-3957/RFC-3957.txt","sha256":"47ca49de2e3b5684b5b3c827c944ff2fe59ba85263242154d2781549c824fa05"}},"tags":["nested-reference","unchanged"],"summary":"Authentication, Authorization, and Accounting (AAA) servers, such as\n RADIUS and DIAMETER, are in use within the Internet today to provide\n authentication and authorization services for dial-up computers.\n Mobile IP for IPv4 requires strong authentication between the mobile\n node and its home agent. When the mobile node shares an AAA Security\n Association with its home AAA server, however, it is possible to use\n that AAA Security Association to create derived Mobility Security\n Associations between the mobile node and its home agent, and again\n between the mobile node and the foreign agent currently offering\n connectivity to the mobile node. This document specifies extensions\n to Mobile IP registration messages that can be used to create\n Mobility Security Associations between the mobile node and its home\n agent, and/or between the mobile node and a foreign agent.\n\nPerkins & Calhoun Stan","scope_keywords":["3957","authentication","authorization","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 3957 Authentication, Authorization, and Accounting (AAA) servers, such as\n RADIUS and DIAMETER, are in use within the Internet today to provide\n authentication and authorization services for dial-up computers.\n Mobile IP for IPv4 requires strong authentication between the mobile\n node and its home agent. When the mobile node shares an AAA Security\n Association with its home AAA server, however, it is possible to use\n that AAA Security Association to create derived Mobility Security\n Associations between the mobile node and its home agent, and again\n between the mobile node and the foreign agent currently offering\n connectivity to the mobile node. This document specifies extensions\n to Mobile IP registration messages that can be used to create\n Mobility Security Associations between the mobile node and its home\n agent, and/or between the mobile node and a foreign agent.\n\nPerkins & Calhoun Stan 3957 authentication authorization key keys nested-reference unchanged"},{"id":"IETF RFC 3972","type":"specification","body":"IETF","designation":"RFC 3972","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3972.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3972.txt","https://www.rfc-editor.org/rfc/rfc3972.pdf"],"folder":"IETF/RFC-3972","files":{"txt":{"path":"standards/IETF/RFC-3972/RFC-3972.txt","sha256":"b8b138c39dd9bcfa9dcb9c0fde59449bfac96fd89ec0e5c09395e85b2b16b318"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for binding a public signature key\n to an IPv6 address in the Secure Neighbor Discovery (SEND) protocol.\n Cryptographically Generated Addresses (CGA) are IPv6 addresses for\n which the interface identifier is generated by computing a\n cryptographic one-way hash function from a public key and auxiliary\n parameters. The binding between the public key and the address can\n be verified by re-computing the hash value and by comparing the hash\n with the interface identifier. Messages sent from an IPv6 address\n can be protected by attaching the public key and auxiliary parameters\n and by signing the message with the corresponding private key. The\n protection works without a certification authority or any security\n infrastructure.\n\nAura Standards Track [Page 1]\n\f\nRFC 3972 Cryptographically Generated Addresses March 2005","scope_keywords":["3972","algorithm","algorithms","hash","key","pki","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4581","folder":"IETF/RFC-4581","source":"IETF/RFC-4581/RFC-4581.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6644","folder":"IETF/RFC-6644","source":"IETF/RFC-6644/RFC-6644.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 3972 This document describes a method for binding a public signature key\n to an IPv6 address in the Secure Neighbor Discovery (SEND) protocol.\n Cryptographically Generated Addresses (CGA) are IPv6 addresses for\n which the interface identifier is generated by computing a\n cryptographic one-way hash function from a public key and auxiliary\n parameters. The binding between the public key and the address can\n be verified by re-computing the hash value and by comparing the hash\n with the interface identifier. Messages sent from an IPv6 address\n can be protected by attaching the public key and auxiliary parameters\n and by signing the message with the corresponding private key. The\n protection works without a certification authority or any security\n infrastructure.\n\nAura Standards Track [Page 1]\n\f\nRFC 3972 Cryptographically Generated Addresses March 2005 3972 algorithm algorithms hash key pki signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 4056","type":"specification","body":"IETF","designation":"RFC 4056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4056.txt","https://www.rfc-editor.org/rfc/rfc4056.pdf"],"folder":"IETF/RFC-4056","files":{"txt":{"path":"standards/IETF/RFC-4056/RFC-4056.txt","sha256":"d7940edb5a91b0b343529c611285f2f69a3053689864fe127a74a3a18177faef"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the RSASSA-PSS (RSA\n Probabilistic Signature Scheme) digital signature algorithm with the\n Cryptographic Message Syntax (CMS).\n\n1. Overview\n\n This document specifies the conventions for using the RSA\n Probabilistic Signature Scheme (RSASSA-PSS) [P1v2.1] digital\n signature algorithm with the Cryptographic Message Syntax [CMS]\n signed-data content type.\n\n CMS values are generated using ASN.1 [X.208-88], using the Basic\n Encoding Rules (BER) [X.209-88] and the Distinguished Encoding Rules\n (DER) [X.509-88].\n\n This document is written to be used in conjunction with RFC 4055\n [RSA-ALGS]. All of the ASN.1 structures referenced in this document\n are defined in RFC 4055.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as des","scope_keywords":["4056","algorithm","algorithms","attribute","attributes","certificate","certificates","encryption","hash","key","keys","signature","signatures","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 4056 This document specifies the conventions for using the RSASSA-PSS (RSA\n Probabilistic Signature Scheme) digital signature algorithm with the\n Cryptographic Message Syntax (CMS).\n\n1. Overview\n\n This document specifies the conventions for using the RSA\n Probabilistic Signature Scheme (RSASSA-PSS) [P1v2.1] digital\n signature algorithm with the Cryptographic Message Syntax [CMS]\n signed-data content type.\n\n CMS values are generated using ASN.1 [X.208-88], using the Basic\n Encoding Rules (BER) [X.209-88] and the Distinguished Encoding Rules\n (DER) [X.509-88].\n\n This document is written to be used in conjunction with RFC 4055\n [RSA-ALGS]. All of the ASN.1 structures referenced in this document\n are defined in RFC 4055.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as des 4056 algorithm algorithms attribute attributes certificate certificates encryption hash key keys signature signatures subject validation nested-reference unchanged"},{"id":"IETF RFC 4568","type":"specification","body":"IETF","designation":"RFC 4568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4568.txt","https://www.rfc-editor.org/rfc/rfc4568.pdf"],"folder":"IETF/RFC-4568","files":{"txt":{"path":"standards/IETF/RFC-4568/RFC-4568.txt","sha256":"ffb3f69032ab10547086430929c6d6ea6ebb660c6bd8e6f6d53d7af6dbc3bddd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Session Description Protocol (SDP)\n cryptographic attribute for unicast media streams. The attribute\n describes a cryptographic key and other parameters that serve to\n configure security for a unicast media stream in either a single\n message or a roundtrip exchange. The attribute can be used with a\n variety of SDP media transports, and this document defines how to use\n it for the Secure Real-time Transport Protocol (SRTP) unicast media\n streams. The SDP crypto attribute requires the services of a data\n security protocol to secure the SDP message.","scope_keywords":["4568","attribute","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6188","folder":"IETF/RFC-6188","source":"IETF/RFC-6188/RFC-6188.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 4568 This document defines a Session Description Protocol (SDP)\n cryptographic attribute for unicast media streams. The attribute\n describes a cryptographic key and other parameters that serve to\n configure security for a unicast media stream in either a single\n message or a roundtrip exchange. The attribute can be used with a\n variety of SDP media transports, and this document defines how to use\n it for the Secure Real-time Transport Protocol (SRTP) unicast media\n streams. The SDP crypto attribute requires the services of a data\n security protocol to secure the SDP message. 4568 attribute authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 4650","type":"specification","body":"IETF","designation":"RFC 4650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4650.txt","https://www.rfc-editor.org/rfc/rfc4650.pdf"],"folder":"IETF/RFC-4650","files":{"txt":{"path":"standards/IETF/RFC-4650/RFC-4650.txt","sha256":"93a35c64498960361bce7d4d913d22475999226a2d6ba4fb68b07d3529125456"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a lightweight point-to-point key management\n protocol variant for the multimedia Internet keying (MIKEY) protocol\n MIKEY, as defined in RFC 3830. In particular, this variant deploys\n the classic Diffie-Hellman key agreement protocol for key\n establishment featuring perfect forward secrecy in conjunction with a\n keyed hash message authentication code for achieving mutual\n authentication and message integrity of the key management messages\n exchanged. This protocol addresses the security and performance\n constraints of multimedia key management in MIKEY.\n\nEuchner Standards Track [Page 1]\n\f\nRFC 4650 HMAC-Authenticated Diffie-Hellman for MIKEY September 2006","scope_keywords":["4650","authentication","authorization","certificate","certificates","encryption","hash","key","keys","management","path","policies","revocation","risk","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 4650 This document describes a lightweight point-to-point key management\n protocol variant for the multimedia Internet keying (MIKEY) protocol\n MIKEY, as defined in RFC 3830. In particular, this variant deploys\n the classic Diffie-Hellman key agreement protocol for key\n establishment featuring perfect forward secrecy in conjunction with a\n keyed hash message authentication code for achieving mutual\n authentication and message integrity of the key management messages\n exchanged. This protocol addresses the security and performance\n constraints of multimedia key management in MIKEY.\n\nEuchner Standards Track [Page 1]\n\f\nRFC 4650 HMAC-Authenticated Diffie-Hellman for MIKEY September 2006 4650 authentication authorization certificate certificates encryption hash key keys management path policies revocation risk signature signatures nested-reference unchanged"},{"id":"IETF RFC 2379","type":"specification","body":"IETF","designation":"RFC 2379","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2379.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2379.txt","https://www.rfc-editor.org/rfc/rfc2379.pdf"],"folder":"IETF/RFC-2379","files":{"txt":{"path":"standards/IETF/RFC-2379/RFC-2379.txt","sha256":"5a9f9e39f2e052416e615f0c69991279055bf2c05e44cef77573e62b238589a6"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents specific implementation guidelines for running\n RSVP over ATM switched virtual circuits (SVCs). The general problem\n is discussed in [6]. Implementation requirements are discussed in\n [2]. Integrated Services to ATM service mappings are covered in [3].\n The full set of documents present the background and information\n needed to implement Integrated Services and RSVP over ATM.\n\n1. Introduction\n\n This memo discusses running IP over ATM in an environment where SVCs\n are used to support QoS flows and RSVP is used as the internet level\n QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and\n MPOA methods for supporting IP over ATM. The general issues related\n to running RSVP[4] over ATM have been covered in several papers\n including [6] and other earlier work. This document is intended as a\n companion to [6,2] and as a guide to implementers. The reader should\n ","scope_keywords":["2379","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null}],"search_text":"IETF RFC 2379 This memo presents specific implementation guidelines for running\n RSVP over ATM switched virtual circuits (SVCs). The general problem\n is discussed in [6]. Implementation requirements are discussed in\n [2]. Integrated Services to ATM service mappings are covered in [3].\n The full set of documents present the background and information\n needed to implement Integrated Services and RSVP over ATM.\n\n1. Introduction\n\n This memo discusses running IP over ATM in an environment where SVCs\n are used to support QoS flows and RSVP is used as the internet level\n QoS signaling protocol. It applies when using CLIP/ION, LANE2.0 and\n MPOA methods for supporting IP over ATM. The general issues related\n to running RSVP[4] over ATM have been covered in several papers\n including [6] and other earlier work. This document is intended as a\n companion to [6,2] and as a guide to implementers. The reader should\n  2379 key path nested-reference unchanged"},{"id":"IETF RFC 1756","type":"specification","body":"IETF","designation":"RFC 1756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1756.txt","https://www.rfc-editor.org/rfc/rfc1756.pdf"],"folder":"IETF/RFC-1756","files":{"txt":{"path":"standards/IETF/RFC-1756/RFC-1756.txt","sha256":"1cd411bc34c98684e3736a8349561a6c3eab031a3cce8054eb8e699a9af4e05c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Rinne\nRequest for Comments: 1756 HUT\nCategory: Experimental January 1995\n\n REMOTE WRITE PROTOCOL - VERSION 1.0\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1. Background\n\n It is often convenient to use electronic communication somewhat\n lighter than electronic mail. Sometimes even the use of the talk(1)\n *) program seems like overkill. We like to offer to user something\n like UNIX ) command write(1) *) except that it can also pass\n messages through the network instead of the single host.\n\n There have been few programs offering this kind of service, but they\n have either based on SUN-RPC protocol or used a strictly undocumented\n protocol.\n\n This document d","scope_keywords":["1756","delivery","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1756 Network Working Group T. Rinne\nRequest for Comments: 1756 HUT\nCategory: Experimental January 1995\n\n REMOTE WRITE PROTOCOL - VERSION 1.0\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\n1. Background\n\n It is often convenient to use electronic communication somewhat\n lighter than electronic mail. Sometimes even the use of the talk(1)\n *) program seems like overkill. We like to offer to user something\n like UNIX ) command write(1) *) except that it can also pass\n messages through the network instead of the single host.\n\n There have been few programs offering this kind of service, but they\n have either based on SUN-RPC protocol or used a strictly undocumented\n protocol.\n\n This document d 1756 delivery identification path nested-reference unchanged"},{"id":"IETF RFC 2724","type":"specification","body":"IETF","designation":"RFC 2724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2724.txt","https://www.rfc-editor.org/rfc/rfc2724.pdf"],"folder":"IETF/RFC-2724","files":{"txt":{"path":"standards/IETF/RFC-2724/RFC-2724.txt","sha256":"533775b24214331605a811e460604710347ecc9f9d9e8e3e3d08a801263e9d99"}},"tags":["nested-reference","unchanged"],"summary":"The RTFM Traffic Measurement Architecture provides a general\n framework for describing and measuring network traffic flows. Flows\n are defined in terms of their Address Attribute values and measured\n by a 'Traffic Meter'. This document discusses RTFM flows and the\n attributes which they can have, so as to provide a logical framework\n for extending the architecture by adding new attributes.\n\n Extensions described include Address Attributes such as DSCodePoint,\n SourceASN and DestASN, and Group Attributes such as short-term bit\n rates and turnaround times. Quality of Service parameters for\n Integrated Services are also discussed.","scope_keywords":["2724","algorithm","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2724 The RTFM Traffic Measurement Architecture provides a general\n framework for describing and measuring network traffic flows. Flows\n are defined in terms of their Address Attribute values and measured\n by a 'Traffic Meter'. This document discusses RTFM flows and the\n attributes which they can have, so as to provide a logical framework\n for extending the architecture by adding new attributes.\n\n Extensions described include Address Attributes such as DSCodePoint,\n SourceASN and DestASN, and Group Attributes such as short-term bit\n rates and turnaround times. Quality of Service parameters for\n Integrated Services are also discussed. 2724 algorithm attribute attributes nested-reference unchanged"},{"id":"IETF RFC 2568","type":"specification","body":"IETF","designation":"RFC 2568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2568.txt","https://www.rfc-editor.org/rfc/rfc2568.pdf"],"folder":"IETF/RFC-2568","files":{"txt":{"path":"standards/IETF/RFC-2568/RFC-2568.txt","sha256":"46fa1dab6ce8ede3745ca9eecac8195f7224dbd0c1132d65ca16d37fcb30f2e7"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes IPP\n from a high level view, defines a roadmap for the various documents\n that form the suite of IPP specifications, and gives background and\n rationale for the IETF working group's major decisions.\n\nZilles Experimental [Page 1]\n\f\nRFC 2568 Rationale for IPP April 1999\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the\n Internet Printing Protocol (this document)\n Internet Printing Protocol/1.0: Model and Semantics [RFC2566]\n Internet Printing Protocol/1.0: Encoding and Transport [RFC2565]\n Internet Printing Protocol/1","scope_keywords":["2568","attribute","attributes","authentication","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2568 This document is one of a set of documents, which together describe\n all aspects of a new Internet Printing Protocol (IPP). IPP is an\n application level protocol that can be used for distributed printing\n using Internet tools and technologies. This document describes IPP\n from a high level view, defines a roadmap for the various documents\n that form the suite of IPP specifications, and gives background and\n rationale for the IETF working group's major decisions.\n\nZilles Experimental [Page 1]\n\f\nRFC 2568 Rationale for IPP April 1999\n\n The full set of IPP documents includes:\n\n Design Goals for an Internet Printing Protocol [RFC2567]\n Rationale for the Structure and Model and Protocol for the\n Internet Printing Protocol (this document)\n Internet Printing Protocol/1.0: Model and Semantics [RFC2566]\n Internet Printing Protocol/1.0: Encoding and Transport [RFC2565]\n Internet Printing Protocol/1 2568 attribute attributes authentication http tls nested-reference unchanged"},{"id":"IETF RFC 1762","type":"specification","body":"IETF","designation":"RFC 1762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1762.txt","https://www.rfc-editor.org/rfc/rfc1762.pdf"],"folder":"IETF/RFC-1762","files":{"txt":{"path":"standards/IETF/RFC-1762/RFC-1762.txt","sha256":"6f96106455b7a0cbd3c90f9cd2fddba67220078c249aab9a3855aff36197a5e5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Senum\nRequest for Comments: 1762 DigiBoard\nObsoletes: 1376 March 1995\nCategory: Standards Track\n\n The PPP DECnet Phase IV Control Protocol (DNCP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines th","scope_keywords":["1762","attribute","attributes","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1762 Network Working Group S. Senum\nRequest for Comments: 1762 DigiBoard\nObsoletes: 1376 March 1995\nCategory: Standards Track\n\n The PPP DECnet Phase IV Control Protocol (DNCP)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n The Point-to-Point Protocol (PPP) [1] provides a standard method of\n encapsulating Network Layer protocol information over point-to-point\n links. PPP also defines an extensible Link Control Protocol, and\n proposes a family of Network Control Protocols (NCPs) for\n establishing and configuring different network-layer protocols.\n\n This document defines th 1762 attribute attributes authentication path nested-reference unchanged"},{"id":"IETF RFC 1763","type":"specification","body":"IETF","designation":"RFC 1763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1763.txt","https://www.rfc-editor.org/rfc/rfc1763.pdf"],"folder":"IETF/RFC-1763","files":{"txt":{"path":"standards/IETF/RFC-1763/RFC-1763.txt","sha256":"f9bf03dab6a14a50c113b53903bbea8a17f65b27f7f63eed36d7584e2027c321"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring the Banyan VINES protocol over PPP.","scope_keywords":["1763","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1763 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring the Banyan VINES protocol over PPP. 1763 authentication nested-reference unchanged"},{"id":"IETF RFC 1764","type":"specification","body":"IETF","designation":"RFC 1764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1764.txt","https://www.rfc-editor.org/rfc/rfc1764.pdf"],"folder":"IETF/RFC-1764","files":{"txt":{"path":"standards/IETF/RFC-1764/RFC-1764.txt","sha256":"c2eb15d41207c064ccfa42522c0629c0f7b912e094a5a579315ebf9e6c9ea2b3"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring the Xerox Network Systems (XNS) Internet Datagram\n Protocol (IDP) over PPP.","scope_keywords":["1764","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1764 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocol for establishing\n and configuring the Xerox Network Systems (XNS) Internet Datagram\n Protocol (IDP) over PPP. 1764 authentication nested-reference unchanged"},{"id":"IETF RFC 5148","type":"specification","body":"IETF","designation":"RFC 5148","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5148.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5148.txt","https://www.rfc-editor.org/rfc/rfc5148.pdf"],"folder":"IETF/RFC-5148","files":{"txt":{"path":"standards/IETF/RFC-5148/RFC-5148.txt","sha256":"d09c66dd0060a5684cb639d2c9fc257ed8cb4d7314fc0182c30d9767b5afd36a"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations for jittering (randomly\n modifying timing) of control traffic transmissions in Mobile Ad hoc\n NETwork (MANET) routing protocols to reduce the probability of\n transmission collisions.","scope_keywords":["5148","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null}],"search_text":"IETF RFC 5148 This document provides recommendations for jittering (randomly\n modifying timing) of control traffic transmissions in Mobile Ad hoc\n NETwork (MANET) routing protocols to reduce the probability of\n transmission collisions. 5148 key nested-reference unchanged"},{"id":"IETF RFC 1942","type":"specification","body":"IETF","designation":"RFC 1942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1942.txt","https://www.rfc-editor.org/rfc/rfc1942.pdf"],"folder":"IETF/RFC-1942","files":{"txt":{"path":"standards/IETF/RFC-1942/RFC-1942.txt","sha256":"5479e9b62cd4243e36398d6d0d083a78d4f6b74aa915ed06109eed4f64e5a18b"}},"tags":["nested-reference","unchanged"],"summary":"The HyperText Markup Language (HTML) is a simple markup language used\n to create hypertext documents that are portable from one platform to\n another. HTML documents are SGML documents with generic semantics\n that are appropriate for representing information from a wide range\n of applications. This specification extends HTML to support a wide\n variety of tables. The model is designed to work well with associated\n style sheets, but does not require them. It also supports rendering\n to braille, or speech, and exchange of tabular data with databases\n and spreadsheets. The HTML table model embodies certain aspects of\n the CALS table model, e.g. the ability to group table rows into\n thead, tbody and tfoot sections, plus the ability to specify cell\n alignment compactly for sets of cells according to the context.","scope_keywords":["1942","algorithm","algorithms","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null}],"search_text":"IETF RFC 1942 The HyperText Markup Language (HTML) is a simple markup language used\n to create hypertext documents that are portable from one platform to\n another. HTML documents are SGML documents with generic semantics\n that are appropriate for representing information from a wide range\n of applications. This specification extends HTML to support a wide\n variety of tables. The model is designed to work well with associated\n style sheets, but does not require them. It also supports rendering\n to braille, or speech, and exchange of tabular data with databases\n and spreadsheets. The HTML table model embodies certain aspects of\n the CALS table model, e.g. the ability to group table rows into\n thead, tbody and tfoot sections, plus the ability to specify cell\n alignment compactly for sets of cells according to the context. 1942 algorithm algorithms attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 2184","type":"specification","body":"IETF","designation":"RFC 2184","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2184.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2184.txt","https://www.rfc-editor.org/rfc/rfc2184.pdf"],"folder":"IETF/RFC-2184","files":{"txt":{"path":"standards/IETF/RFC-2184/RFC-2184.txt","sha256":"4a3b1f299f0e2d608e30d5c200398d30f9dbcc4d1b2819837a8b85ec37f9ee06"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines extensions to the RFC 2045 media type and RFC 2183\n disposition parameter value mechanisms to provide\n\n (1) a means to specify parameter values in character sets\n other than US-ASCII,\n\n (2) to specify the language to be used should the value be\n displayed, and\n\n (3) a continuation mechanism for long parameter values to\n avoid problems with header line wrapping.\n\n This memo also defines an extension to the encoded words defined in\n RFC 2047 to allow the specification of the language to be used for\n display as well as the character set.\n\n2. Introduction\n\n The Multipurpose Internet Mail Extensions, or MIME [RFC-2045, RFC-\n 2046, RFC-2047, RFC-2048, RFC-2049], define a message format that\n allows for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) non-textual message bodies,\n\n (3) multi-part message bodies, and\n\nFreed & Moore Standards Track [Page","scope_keywords":["2184","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"IETF RFC 2184 This memo defines extensions to the RFC 2045 media type and RFC 2183\n disposition parameter value mechanisms to provide\n\n (1) a means to specify parameter values in character sets\n other than US-ASCII,\n\n (2) to specify the language to be used should the value be\n displayed, and\n\n (3) a continuation mechanism for long parameter values to\n avoid problems with header line wrapping.\n\n This memo also defines an extension to the encoded words defined in\n RFC 2047 to allow the specification of the language to be used for\n display as well as the character set.\n\n2. Introduction\n\n The Multipurpose Internet Mail Extensions, or MIME [RFC-2045, RFC-\n 2046, RFC-2047, RFC-2048, RFC-2049], define a message format that\n allows for\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n (2) non-textual message bodies,\n\n (3) multi-part message bodies, and\n\nFreed & Moore Standards Track [Page 2184 risk nested-reference unchanged"},{"id":"IETF RFC 2231","type":"specification","body":"IETF","designation":"RFC 2231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2231.txt","https://www.rfc-editor.org/rfc/rfc2231.pdf"],"folder":"IETF/RFC-2231","files":{"txt":{"path":"standards/IETF/RFC-2231/RFC-2231.txt","sha256":"e69cbc8c05097736c5296575e7a2e0cb2a2a09c522640eb40ecc4a9dca56076d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines extensions to the RFC 2045 media type and RFC 2183\n disposition parameter value mechanisms to provide\n\n (1) a means to specify parameter values in character sets\n other than US-ASCII,\n\n (2) to specify the language to be used should the value be\n displayed, and\n\n (3) a continuation mechanism for long parameter values to\n avoid problems with header line wrapping.\n\n This memo also defines an extension to the encoded words defined in\n RFC 2047 to allow the specification of the language to be used for\n display as well as the character set.\n\n2. Introduction\n\n The Multipurpose Internet Mail Extensions, or MIME [RFC-2045, RFC-\n 2046, RFC-2047, RFC-2048, RFC-2049], define a message format that\n allows for:\n\nFreed & Moore Standards Track [Page 1]\n\f\nRFC 2231 MIME Value and Encoded Word Extensions November 1997\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n ","scope_keywords":["2231","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2388","folder":"IETF/RFC-2388","source":"IETF/RFC-2388/RFC-2388.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2231 This memo defines extensions to the RFC 2045 media type and RFC 2183\n disposition parameter value mechanisms to provide\n\n (1) a means to specify parameter values in character sets\n other than US-ASCII,\n\n (2) to specify the language to be used should the value be\n displayed, and\n\n (3) a continuation mechanism for long parameter values to\n avoid problems with header line wrapping.\n\n This memo also defines an extension to the encoded words defined in\n RFC 2047 to allow the specification of the language to be used for\n display as well as the character set.\n\n2. Introduction\n\n The Multipurpose Internet Mail Extensions, or MIME [RFC-2045, RFC-\n 2046, RFC-2047, RFC-2048, RFC-2049], define a message format that\n allows for:\n\nFreed & Moore Standards Track [Page 1]\n\f\nRFC 2231 MIME Value and Encoded Word Extensions November 1997\n\n (1) textual message bodies in character sets other than\n US-ASCII,\n\n  2231 risk nested-reference unchanged"},{"id":"IETF RFC 2277","type":"specification","body":"IETF","designation":"RFC 2277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2277.txt","https://www.rfc-editor.org/rfc/rfc2277.pdf"],"folder":"IETF/RFC-2277","files":{"txt":{"path":"standards/IETF/RFC-2277/RFC-2277.txt","sha256":"667bdee192d22af4259b0cb38148466b559375a4ecbed67c33bf4ccd97d3c39f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Alvestrand\nRequest for Comments: 2277 UNINETT\nBCP: 18 January 1998\nCategory: Best Current Practice\n\n IETF Policy on Character Sets and Languages\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n The Internet is international.\n\n With the international Internet follows an absolute requirement to\n interchange data in a multiplicity of languages, which in turn\n utilize a bewildering number of characters.\n\n This document is the current policies being applied by the Internet\n Engineering Steering Group (IESG) towards the standardization efforts\n in the Internet Engineering Task Force (IETF) in order to help\n In","scope_keywords":["2277","http","policies","policy","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3375","folder":"IETF/RFC-3375","source":"IETF/RFC-3375/RFC-3375.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4766","folder":"IETF/RFC-4766","source":"IETF/RFC-4766/RFC-4766.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5001","folder":"IETF/RFC-5001","source":"IETF/RFC-5001/RFC-5001.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null}],"search_text":"IETF RFC 2277 Network Working Group H. Alvestrand\nRequest for Comments: 2277 UNINETT\nBCP: 18 January 1998\nCategory: Best Current Practice\n\n IETF Policy on Character Sets and Languages\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n The Internet is international.\n\n With the international Internet follows an absolute requirement to\n interchange data in a multiplicity of languages, which in turn\n utilize a bewildering number of characters.\n\n This document is the current policies being applied by the Internet\n Engineering Steering Group (IESG) towards the standardization efforts\n in the Internet Engineering Task Force (IETF) in order to help\n In 2277 http policies policy registered subject nested-reference unchanged"},{"id":"IETF RFC 2413","type":"specification","body":"IETF","designation":"RFC 2413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2413.txt","https://www.rfc-editor.org/rfc/rfc2413.pdf"],"folder":"IETF/RFC-2413","files":{"txt":{"path":"standards/IETF/RFC-2413/RFC-2413.txt","sha256":"cbe1d956a724f6dc95199d6f9ace9e1287e4438a50b387e8c02063b163286a25"}},"tags":["nested-reference","unchanged"],"summary":"The Dublin Core Metadata Workshop Series began in 1995 with an\n invitational workshop which brought together librarians, digital\n library researchers, content experts, and text-markup experts to\n promote better discovery standards for electronic resources. The\n Dublin Core is a 15-element set of descriptors that has emerged from\n this effort in interdisciplinary and international consensus\n building. This is the first of a set of Informational RFCs\n describing the Dublin Core. Its purpose is to introduce the Dublin\n Core and to describe the consensus reached on the semantics of each\n of the 15 elements.\n\n3. Introduction\n\n Finding relevant information on the World Wide Web has become\n increasingly problematic due to the explosive growth of networked\n resources. Current Web indexing evolved rapidly to fill the demand\n for resource discovery tools, but that indexing, while useful, is a\n poo","scope_keywords":["2413","http","key","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2731","folder":"IETF/RFC-2731","source":"IETF/RFC-2731/RFC-2731.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 5013","folder":"IETF/RFC-5013","source":"IETF/RFC-5013/RFC-5013.txt","version":null}],"search_text":"IETF RFC 2413 The Dublin Core Metadata Workshop Series began in 1995 with an\n invitational workshop which brought together librarians, digital\n library researchers, content experts, and text-markup experts to\n promote better discovery standards for electronic resources. The\n Dublin Core is a 15-element set of descriptors that has emerged from\n this effort in interdisciplinary and international consensus\n building. This is the first of a set of Informational RFCs\n describing the Dublin Core. Its purpose is to introduce the Dublin\n Core and to describe the consensus reached on the semantics of each\n of the 15 elements.\n\n3. Introduction\n\n Finding relevant information on the World Wide Web has become\n increasingly problematic due to the explosive growth of networked\n resources. Current Web indexing evolved rapidly to fill the demand\n for resource discovery tools, but that indexing, while useful, is a\n poo 2413 http key pid subject nested-reference unchanged"},{"id":"IETF RFC 2482","type":"specification","body":"IETF","designation":"RFC 2482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2482.txt","https://www.rfc-editor.org/rfc/rfc2482.pdf"],"folder":"IETF/RFC-2482","files":{"txt":{"path":"standards/IETF/RFC-2482/RFC-2482.txt","sha256":"c8ffd88710b476d93300a39937149f78551ef9fdc2a563095f0624a9c7b0bcf2"}},"tags":["nested-reference","unchanged"],"summary":"This document proposed a mechanism for language tagging in [UNICODE]\n plain text. A set of special-use tag characters on Plane 14 of\n [ISO10646] (accessible through UTF-8, UTF-16, and UCS-4 encoding\n forms) are proposed for encoding to enable the spelling out of\n ASCII-based string tags using characters which can be strictly\n separated from ordinary text content characters in ISO10646 (or\n UNICODE).\n\n One tag identification character and one cancel tag character are\n also proposed. In particular, a language tag identification character\n is proposed to identify a language tag string specifically; the\n language tag itself makes use of [RFC1766] language tag strings\n spelled out using the Plane 14 tag characters. Provision of a\n specific, low-overhead mechanism for embedding language tags in plain\n text is aimed at meeting the need of Internet Protocols such as ACAP,\n which require a standa","scope_keywords":["2482","algorithm","algorithms","attribute","attributes","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null}],"search_text":"IETF RFC 2482 This document proposed a mechanism for language tagging in [UNICODE]\n plain text. A set of special-use tag characters on Plane 14 of\n [ISO10646] (accessible through UTF-8, UTF-16, and UCS-4 encoding\n forms) are proposed for encoding to enable the spelling out of\n ASCII-based string tags using characters which can be strictly\n separated from ordinary text content characters in ISO10646 (or\n UNICODE).\n\n One tag identification character and one cancel tag character are\n also proposed. In particular, a language tag identification character\n is proposed to identify a language tag string specifically; the\n language tag itself makes use of [RFC1766] language tag strings\n spelled out using the Plane 14 tag characters. Provision of a\n specific, low-overhead mechanism for embedding language tags in plain\n text is aimed at meeting the need of Internet Protocols such as ACAP,\n which require a standa 2482 algorithm algorithms attribute attributes identification subject nested-reference unchanged"},{"id":"IETF RFC 2510","type":"specification","body":"IETF","designation":"RFC 2510","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2510.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2510.txt","https://www.rfc-editor.org/rfc/rfc2510.pdf"],"folder":"IETF/RFC-2510","files":{"txt":{"path":"standards/IETF/RFC-2510/RFC-2510.txt","sha256":"79a360dc57eaa14e3ae0a149dbc20aefcc3447fd0ab57b03b690e9507e14abf0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Internet X.509 Public Key Infrastructure\n (PKI) Certificate Management Protocols. Protocol messages are defined\n for all relevant aspects of certificate creation and management.\n Note that \"certificate\" in this document refers to an X.509v3\n Certificate as defined in [COR95, X509-AM].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document (in uppercase,\n as shown) are to be interpreted as described in [RFC2119].","scope_keywords":["2510","authentication","certificate","certificates","issuer","key","management","pki","policy","profile","profiles","revocation","subject","trust","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null}],"search_text":"IETF RFC 2510 This document describes the Internet X.509 Public Key Infrastructure\n (PKI) Certificate Management Protocols. Protocol messages are defined\n for all relevant aspects of certificate creation and management.\n Note that \"certificate\" in this document refers to an X.509v3\n Certificate as defined in [COR95, X509-AM].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document (in uppercase,\n as shown) are to be interpreted as described in [RFC2119]. 2510 authentication certificate certificates issuer key management pki policy profile profiles revocation subject trust x509 nested-reference unchanged"},{"id":"IETF RFC 2596","type":"specification","body":"IETF","designation":"RFC 2596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2596.txt","https://www.rfc-editor.org/rfc/rfc2596.pdf"],"folder":"IETF/RFC-2596","files":{"txt":{"path":"standards/IETF/RFC-2596/RFC-2596.txt","sha256":"2cfdfff7fe8e097606a61176cd5160b88b4cd2bf9f4df8bd2cc073cd0e062af2"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol [1] provides a means for\n clients to interrogate and modify information stored in a distributed\n directory system. The information in the directory is maintained as\n attributes [2] of entries. Most of these attributes have syntaxes\n which are human-readable strings, and it is desirable to be able to\n indicate the natural language associated with attribute values.\n\n This document describes how language codes [3] are carried in LDAP\n and are to be interpreted by LDAP servers. All implementations MUST\n be prepared to accept language codes in the LDAP protocols. Servers\n may or may not be capable of storing attributes with language codes\n in the directory. This document does not specify how to determine\n whether particular attributes can or cannot have language codes.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"S","scope_keywords":["2596","attribute","attributes","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null}],"search_text":"IETF RFC 2596 The Lightweight Directory Access Protocol [1] provides a means for\n clients to interrogate and modify information stored in a distributed\n directory system. The information in the directory is maintained as\n attributes [2] of entries. Most of these attributes have syntaxes\n which are human-readable strings, and it is desirable to be able to\n indicate the natural language associated with attribute values.\n\n This document describes how language codes [3] are carried in LDAP\n and are to be interpreted by LDAP servers. All implementations MUST\n be prepared to accept language codes in the LDAP protocols. Servers\n may or may not be capable of storing attributes with language codes\n in the directory. This document does not specify how to determine\n whether particular attributes can or cannot have language codes.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"S 2596 attribute attributes key presentation nested-reference unchanged"},{"id":"IETF RFC 2608","type":"specification","body":"IETF","designation":"RFC 2608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2608.txt","https://www.rfc-editor.org/rfc/rfc2608.pdf"],"folder":"IETF/RFC-2608","files":{"txt":{"path":"standards/IETF/RFC-2608/RFC-2608.txt","sha256":"2fc28b555b01ac23306fb016e88ae132fccd10955286a3b4186a53f06cd838af"}},"tags":["nested-reference","unchanged"],"summary":"The Service Location Protocol provides a scalable framework for the\n discovery and selection of network services. Using this protocol,\n computers using the Internet need little or no static configuration\n of network services for network based applications. This is\n especially important as computers become more portable, and users\n less tolerant or able to fulfill the demands of network system\n administration.","scope_keywords":["2608","attribute","attributes","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2824","folder":"IETF/RFC-2824","source":"IETF/RFC-2824/RFC-2824.txt","version":null},{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3224","folder":"IETF/RFC-3224","source":"IETF/RFC-3224/RFC-3224.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3421","folder":"IETF/RFC-3421","source":"IETF/RFC-3421/RFC-3421.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3528","folder":"IETF/RFC-3528","source":"IETF/RFC-3528/RFC-3528.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 2608 The Service Location Protocol provides a scalable framework for the\n discovery and selection of network services. Using this protocol,\n computers using the Internet need little or no static configuration\n of network services for network based applications. This is\n especially important as computers become more portable, and users\n less tolerant or able to fulfill the demands of network system\n administration. 2608 attribute attributes authentication nested-reference unchanged"},{"id":"IETF RFC 2609","type":"specification","body":"IETF","designation":"RFC 2609","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2609.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2609.txt","https://www.rfc-editor.org/rfc/rfc2609.pdf"],"folder":"IETF/RFC-2609","files":{"txt":{"path":"standards/IETF/RFC-2609/RFC-2609.txt","sha256":"1e4229dc777a2de5f6b2c5b89e41e7b1ffbbe12d083e71131f1a7f458f1aefbd"}},"tags":["nested-reference","unchanged"],"summary":"The \"service:\" URL scheme name is used to define URLs (called\n \"service: URLs\" in this document) that are primarily intended to be\n used by the Service Location Protocol in order to distribute service\n access information. These schemes provide an extensible framework\n for client-based network software to obtain configuration information\n required to make use of network services. When registering a\n service: URL, the URL is accompanied by a set of well-defined\n attributes which define the service. These attributes convey\n configuration information to client software, or service\n characteristics meaningful to end users.\n\n This document describes a formal procedure for defining and\n standardizing new service types and attributes for use with the\n \"service:\" scheme. The formal descriptions of service types and\n attributes are templates that are human and machine understandable.\n They SHOULD ","scope_keywords":["2609","attribute","attributes","identification","key","path","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3224","folder":"IETF/RFC-3224","source":"IETF/RFC-3224/RFC-3224.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null}],"search_text":"IETF RFC 2609 The \"service:\" URL scheme name is used to define URLs (called\n \"service: URLs\" in this document) that are primarily intended to be\n used by the Service Location Protocol in order to distribute service\n access information. These schemes provide an extensible framework\n for client-based network software to obtain configuration information\n required to make use of network services. When registering a\n service: URL, the URL is accompanied by a set of well-defined\n attributes which define the service. These attributes convey\n configuration information to client software, or service\n characteristics meaningful to end users.\n\n This document describes a formal procedure for defining and\n standardizing new service types and attributes for use with the\n \"service:\" scheme. The formal descriptions of service types and\n attributes are templates that are human and machine understandable.\n They SHOULD  2609 attribute attributes identification key path presentation registered nested-reference unchanged"},{"id":"IETF RFC 2614","type":"specification","body":"IETF","designation":"RFC 2614","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2614.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2614.txt","https://www.rfc-editor.org/rfc/rfc2614.pdf"],"folder":"IETF/RFC-2614","files":{"txt":{"path":"standards/IETF/RFC-2614/RFC-2614.txt","sha256":"8e6103cca00c2747e6079bb36506752980b479af9392ade9718267435da9f589"}},"tags":["nested-reference","unchanged"],"summary":"The Service Location Protocol (SLP) provides a new way for clients to\n dynamically discovery network services. With SLP, it is simple to\n offer highly available services that require no user configuration or\n assistance from network administrators prior to use. This document\n describes standardized APIs for SLP in C and Java. The APIs are\n modular and are designed to allow implementations to offer just the\n feature set needed. In addition, standardized file formats for\n configuration and serialized registrations are defined, allowing SLP\n agents to set network and other parameters in a portable way. The\n serialized file format allows legacy services to be registered with\n SLP directory agents in cases where modifying the legacy service\n program code is difficult or impossible, and to portably exchange a\n registration database.","scope_keywords":["2614","attribute","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null}],"search_text":"IETF RFC 2614 The Service Location Protocol (SLP) provides a new way for clients to\n dynamically discovery network services. With SLP, it is simple to\n offer highly available services that require no user configuration or\n assistance from network administrators prior to use. This document\n describes standardized APIs for SLP in C and Java. The APIs are\n modular and are designed to allow implementations to offer just the\n feature set needed. In addition, standardized file formats for\n configuration and serialized registrations are defined, allowing SLP\n agents to set network and other parameters in a portable way. The\n serialized file format allows legacy services to be registered with\n SLP directory agents in cases where modifying the legacy service\n program code is difficult or impossible, and to portably exchange a\n registration database. 2614 attribute management registered nested-reference unchanged"},{"id":"IETF RFC 2731","type":"specification","body":"IETF","designation":"RFC 2731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2731.txt","https://www.rfc-editor.org/rfc/rfc2731.pdf"],"folder":"IETF/RFC-2731","files":{"txt":{"path":"standards/IETF/RFC-2731/RFC-2731.txt","sha256":"f3604dea8353bb051f8f7fbe313bef34ee84e55e28e93673360b950d9801eb0e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Kunze\nRequest for Comments: 2731 Dublin Core\nCategory: Informational Metadata Initiative\n December 1999\n\n Encoding Dublin Core Metadata in HTML\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n The Dublin Core [DC1] is a small set of metadata elements for\n describing information resources. This document explains how these\n elements are expressed using the META and LINK tags of HTML\n [HTML4.0]. A sequence of metadata elements embedded in an HTML file\n is taken to be a description of that file. Examples illustrate\n conventions allowing interoperation with current software that\n indexes, displays, and manipulates metadata, such as [SWISH-E],\n ","scope_keywords":["2731","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5013","folder":"IETF/RFC-5013","source":"IETF/RFC-5013/RFC-5013.txt","version":null}],"search_text":"IETF RFC 2731 Network Working Group J. Kunze\nRequest for Comments: 2731 Dublin Core\nCategory: Informational Metadata Initiative\n December 1999\n\n Encoding Dublin Core Metadata in HTML\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n The Dublin Core [DC1] is a small set of metadata elements for\n describing information resources. This document explains how these\n elements are expressed using the META and LINK tags of HTML\n [HTML4.0]. A sequence of metadata elements embedded in an HTML file\n is taken to be a description of that file. Examples illustrate\n conventions allowing interoperation with current software that\n indexes, displays, and manipulates metadata, such as [SWISH-E],\n  2731 http nested-reference unchanged"},{"id":"IETF RFC 2987","type":"specification","body":"IETF","designation":"RFC 2987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2987.txt","https://www.rfc-editor.org/rfc/rfc2987.pdf"],"folder":"IETF/RFC-2987","files":{"txt":{"path":"standards/IETF/RFC-2987/RFC-2987.txt","sha256":"86144d99b31363020ae59bd31958f898a95fc224737133bc7ef95e9c24364566"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman\nRequest for Comments: 2987 Internet Mail Consortium\nCategory: Standards Track November 2000\n\n Registration of Charset and Languages Media Features Tags\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document contains the registration for two media feature tags:\n \"charset\" and \"language\". These media features allow specification\n of character sets and human languages that can be understood by\n devices and the devices' users. The templates in this ","scope_keywords":["2987","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null}],"search_text":"IETF RFC 2987 Network Working Group P. Hoffman\nRequest for Comments: 2987 Internet Mail Consortium\nCategory: Standards Track November 2000\n\n Registration of Charset and Languages Media Features Tags\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document contains the registration for two media feature tags:\n \"charset\" and \"language\". These media features allow specification\n of character sets and human languages that can be understood by\n devices and the devices' users. The templates in this  2987 identification subject nested-reference unchanged"},{"id":"IETF RFC 3282","type":"specification","body":"IETF","designation":"RFC 3282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3282.txt","https://www.rfc-editor.org/rfc/rfc3282.pdf"],"folder":"IETF/RFC-3282","files":{"txt":{"path":"standards/IETF/RFC-3282/RFC-3282.txt","sha256":"2a7f02a0182ed9623ab081167733f24f423580227f8023856b1a06e2753394c8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a \"Content-language:\" header, for use in cases\n where one desires to indicate the language of something that has RFC\n 822-like headers, like MIME body parts or Web documents, and an\n \"Accept-Language:\" header for use in cases where one wishes to\n indicate one's preferences with regard to language.\n\n1. Introduction\n\n There are a number of languages presently or previously used by human\n beings in this world.\n\n A great number of these people would prefer to have information\n presented in a language which they understand.\n\n In some contexts, it is possible to have information available in\n more than one language, or it might be possible to provide tools\n (such as dictionaries) to assist in the understanding of a language.\n\n In other cases, it may be desirable to use a computer program to\n convert information from one format (such as plaintext) into another\n (such as co","scope_keywords":["3282","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3282 This document defines a \"Content-language:\" header, for use in cases\n where one desires to indicate the language of something that has RFC\n 822-like headers, like MIME body parts or Web documents, and an\n \"Accept-Language:\" header for use in cases where one wishes to\n indicate one's preferences with regard to language.\n\n1. Introduction\n\n There are a number of languages presently or previously used by human\n beings in this world.\n\n A great number of these people would prefer to have information\n presented in a language which they understand.\n\n In some contexts, it is possible to have information available in\n more than one language, or it might be possible to provide tools\n (such as dictionaries) to assist in the understanding of a language.\n\n In other cases, it may be desirable to use a computer program to\n convert information from one format (such as plaintext) into another\n (such as co 3282 http key nested-reference unchanged"},{"id":"IETF RFC 3367","type":"specification","body":"IETF","designation":"RFC 3367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3367.txt","https://www.rfc-editor.org/rfc/rfc3367.pdf"],"folder":"IETF/RFC-3367","files":{"txt":{"path":"standards/IETF/RFC-3367/RFC-3367.txt","sha256":"710a2dc3829f8939614057fa1849c9c9b18ab81cc5d3a00b169812b2c374d3fa"}},"tags":["nested-reference","unchanged"],"summary":"People often refer to things in the real world by a common name or\n phrase, e.g., a trade name, company name, or a book title. These\n names are sometimes easier for people to remember and type than URLs.\n Furthermore, because of the limited syntax of URLs, companies and\n individuals are finding that the ones that might be most reasonable\n for their resources are being used elsewhere and so are unavailable.\n For the purposes of this document, a \"common name\" is a word or a\n phrase, without imposed syntactic structure, that may be associated\n with a resource.\n\n This effort is about the creation of a protocol for client\n applications to communicate with common name resolution services, as\n exemplified in both the browser enhancement and search site\n paradigms. Although the protocol's primary function is resolution,\n it is also intended to address issues of internationalization and\n localiza","scope_keywords":["3367","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3368","folder":"IETF/RFC-3368","source":"IETF/RFC-3368/RFC-3368.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null}],"search_text":"IETF RFC 3367 People often refer to things in the real world by a common name or\n phrase, e.g., a trade name, company name, or a book title. These\n names are sometimes easier for people to remember and type than URLs.\n Furthermore, because of the limited syntax of URLs, companies and\n individuals are finding that the ones that might be most reasonable\n for their resources are being used elsewhere and so are unavailable.\n For the purposes of this document, a \"common name\" is a word or a\n phrase, without imposed syntactic structure, that may be associated\n with a resource.\n\n This effort is about the creation of a protocol for client\n applications to communicate with common name resolution services, as\n exemplified in both the browser enhancement and search site\n paradigms. Although the protocol's primary function is resolution,\n it is also intended to address issues of internationalization and\n localiza 3367 http key nested-reference unchanged"},{"id":"IETF RFC 4645","type":"specification","body":"IETF","designation":"RFC 4645","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4645.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4645.txt","https://www.rfc-editor.org/rfc/rfc4645.pdf"],"folder":"IETF/RFC-4645","files":{"txt":{"path":"standards/IETF/RFC-4645/RFC-4645.txt","sha256":"231648ad814e18ae75f0160da7981781d5b76d3ea2324c6cae77a4193d203495"}},"tags":["nested-reference","unchanged"],"summary":"This memo defined the initial contents of the IANA Language Subtag\n Registry for use in forming tags for the identification of languages.\n Since the contents of this memo only served as a starting point for\n the registry, its actual contents have been removed before\n publication to avoid confusion.","scope_keywords":["4645","identification","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null}],"search_text":"IETF RFC 4645 This memo defined the initial contents of the IANA Language Subtag\n Registry for use in forming tags for the identification of languages.\n Since the contents of this memo only served as a starting point for\n the registry, its actual contents have been removed before\n publication to avoid confusion. 4645 identification registered nested-reference unchanged"},{"id":"IETF RFC 4646","type":"specification","body":"IETF","designation":"RFC 4646","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4646.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4646.txt","https://www.rfc-editor.org/rfc/rfc4646.pdf"],"folder":"IETF/RFC-4646","files":{"txt":{"path":"standards/IETF/RFC-4646/RFC-4646.txt","sha256":"24d7619d08e78959e763558b523d04ad4b5fb275a415992db6dd305129d72384"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the structure, content, construction, and\n semantics of language tags for use in cases where it is desirable to\n indicate the language used in an information object. It also\n describes how to register values for use in language tags and the\n creation of user-defined extensions for private interchange. This\n document, in combination with RFC 4647, replaces RFC 3066, which\n replaced RFC 1766.\n\nPhillips & Davis Best Current Practice [Page 1]\n\f\nRFC 4646 Tags for Identifying Languages September 2006","scope_keywords":["4646","attribute","attributes","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 5013","folder":"IETF/RFC-5013","source":"IETF/RFC-5013/RFC-5013.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null}],"search_text":"IETF RFC 4646 This document describes the structure, content, construction, and\n semantics of language tags for use in cases where it is desirable to\n indicate the language used in an information object. It also\n describes how to register values for use in language tags and the\n creation of user-defined extensions for private interchange. This\n document, in combination with RFC 4647, replaces RFC 3066, which\n replaced RFC 1766.\n\nPhillips & Davis Best Current Practice [Page 1]\n\f\nRFC 4646 Tags for Identifying Languages September 2006 4646 attribute attributes key registered nested-reference unchanged"},{"id":"IETF RFC 4647","type":"specification","body":"IETF","designation":"RFC 4647","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4647.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4647.txt","https://www.rfc-editor.org/rfc/rfc4647.pdf"],"folder":"IETF/RFC-4647","files":{"txt":{"path":"standards/IETF/RFC-4647/RFC-4647.txt","sha256":"999e4e23ca5b8925ac5f154855af0f2948a5d26d14853249c9fc857e469ecb49"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a syntax, called a \"language-range\", for\n specifying items in a user's list of language preferences. It also\n describes different mechanisms for comparing and matching these to\n language tags. Two kinds of matching mechanisms, filtering and\n lookup, are defined. Filtering produces a (potentially empty) set of\n language tags, whereas lookup produces a single language tag.\n Possible applications include language negotiation or content\n selection. This document, in combination with RFC 4646, replaces RFC\n 3066, which replaced RFC 1766.\n\nPhillips & Davis Best Current Practice [Page 1]\n\f\nRFC 4647 Matching of Language Tags September 2006","scope_keywords":["4647","attribute","attributes","http","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 4647 This document describes a syntax, called a \"language-range\", for\n specifying items in a user's list of language preferences. It also\n describes different mechanisms for comparing and matching these to\n language tags. Two kinds of matching mechanisms, filtering and\n lookup, are defined. Filtering produces a (potentially empty) set of\n language tags, whereas lookup produces a single language tag.\n Possible applications include language negotiation or content\n selection. This document, in combination with RFC 4646, replaces RFC\n 3066, which replaced RFC 1766.\n\nPhillips & Davis Best Current Practice [Page 1]\n\f\nRFC 4647 Matching of Language Tags September 2006 4647 attribute attributes http key risk nested-reference unchanged"},{"id":"IETF RFC 5645","type":"specification","body":"IETF","designation":"RFC 5645","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5645.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5645.txt","https://www.rfc-editor.org/rfc/rfc5645.pdf"],"folder":"IETF/RFC-5645","files":{"txt":{"path":"standards/IETF/RFC-5645/RFC-5645.txt","sha256":"5d98f42eccaaa7c318f03825a2d1737a53bd9f872f55bdb9e5758d6485efa7f1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the procedure used to update the IANA Language\n Subtag Registry, in conjunction with the publication of RFC 5646, for\n use in forming tags for identifying languages.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.","scope_keywords":["5645","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"IETF RFC 5645 This memo defines the procedure used to update the IANA Language\n Subtag Registry, in conjunction with the publication of RFC 5646, for\n use in forming tags for identifying languages.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document. 5645 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5646","type":"specification","body":"IETF","designation":"RFC 5646","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5646.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5646.txt","https://www.rfc-editor.org/rfc/rfc5646.pdf"],"folder":"IETF/RFC-5646","files":{"txt":{"path":"standards/IETF/RFC-5646/RFC-5646.txt","sha256":"5d9515f053163c80e7294a84d18217dc83471acc7caa9773da2ac40deeec8228"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the structure, content, construction, and\n semantics of language tags for use in cases where it is desirable to\n indicate the language used in an information object. It also\n describes how to register values for use in language tags and the\n creation of user-defined extensions for private interchange.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully,","scope_keywords":["5646","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 522-3","folder":"ETSI/EN-319-522-3-V1.2.1","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 5646 This document describes the structure, content, construction, and\n semantics of language tags for use in cases where it is desirable to\n indicate the language used in an information object. It also\n describes how to register values for use in language tags and the\n creation of user-defined extensions for private interchange.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, 5646 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 3335","type":"specification","body":"IETF","designation":"RFC 3335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3335.txt","https://www.rfc-editor.org/rfc/rfc3335.pdf"],"folder":"IETF/RFC-3335","files":{"txt":{"path":"standards/IETF/RFC-3335/RFC-3335.txt","sha256":"3a77554099dfadc988bddfb53b0561a28e96b5051b487f63c03de316c5d73e42"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to exchange structured business data\n securely using SMTP transport for Electronic Data Interchange, (EDI -\n either the American Standards Committee X12 or UN/EDIFACT, Electronic\n Data Interchange for Administration, Commerce and Transport), XML or\n other data used for business to business data interchange. The data\n is packaged using standard MIME content-types. Authentication and\n privacy are obtained by using Cryptographic Message Syntax (S/MIME)\n or OpenPGP security body parts. Authenticated acknowledgements make\n use of multipart/signed replies to the original SMTP message.\n\nHarding, et. al. Standards Track [Page 1]\n\f\nRFC 3335 MIME-based Secure EDI September 2002","scope_keywords":["3335","authentication","certificate","encryption","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null}],"search_text":"IETF RFC 3335 This document describes how to exchange structured business data\n securely using SMTP transport for Electronic Data Interchange, (EDI -\n either the American Standards Committee X12 or UN/EDIFACT, Electronic\n Data Interchange for Administration, Commerce and Transport), XML or\n other data used for business to business data interchange. The data\n is packaged using standard MIME content-types. Authentication and\n privacy are obtained by using Cryptographic Message Syntax (S/MIME)\n or OpenPGP security body parts. Authenticated acknowledgements make\n use of multipart/signed replies to the original SMTP message.\n\nHarding, et. al. Standards Track [Page 1]\n\f\nRFC 3335 MIME-based Secure EDI September 2002 3335 authentication certificate encryption key signature nested-reference unchanged"},{"id":"IETF RFC 177","type":"specification","body":"IETF","designation":"RFC 177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc177.txt","https://www.rfc-editor.org/rfc/rfc177.pdf"],"folder":"IETF/RFC-177","files":{"txt":{"path":"standards/IETF/RFC-177/RFC-177.txt","sha256":"fc5f02b4c6028e03b77856968882823f6ad582875765b99a82f06c3019d61b72"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP J. McConnell\nRequest for Comment: 177 Ames Research Center Moffet Field, CA\nObsoletes: none 15 June 1971\nUpdates: 125\nNIC: 7102\n\n A DEVICE INDEPENDENT GRAPHICAL DISPLAY DESCRIPTION\n\n As more nodes are connected to the ARPA network, the types of\n graphical display processors available to users is quite varied. To\n attempt to facilitate the transmission of graphical information over\n the network, a device independent description of a display is\n described. The using host may make any conversions necessary to\n realize the picture on a specific device. It is also possible to\n interpose a form machine as proposed by Heafner and Harslem in RFC\n #94. Some of the items and entities described herein were first\n discussed by Steve Crocker in RFC #86. It is intended that this\n description is to be oriented to a refresh display with point,\n vector, and character drawing capabil","scope_keywords":["177","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 177 NETWORK WORKING GROUP J. McConnell\nRequest for Comment: 177 Ames Research Center Moffet Field, CA\nObsoletes: none 15 June 1971\nUpdates: 125\nNIC: 7102\n\n A DEVICE INDEPENDENT GRAPHICAL DISPLAY DESCRIPTION\n\n As more nodes are connected to the ARPA network, the types of\n graphical display processors available to users is quite varied. To\n attempt to facilitate the transmission of graphical information over\n the network, a device independent description of a display is\n described. The using host may make any conversions necessary to\n realize the picture on a specific device. It is also possible to\n interpose a form machine as proposed by Heafner and Harslem in RFC\n #94. Some of the items and entities described herein were first\n discussed by Steve Crocker in RFC #86. It is intended that this\n description is to be oriented to a refresh display with point,\n vector, and character drawing capabil 177 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 1863","type":"specification","body":"IETF","designation":"RFC 1863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1863.txt","https://www.rfc-editor.org/rfc/rfc1863.pdf"],"folder":"IETF/RFC-1863","files":{"txt":{"path":"standards/IETF/RFC-1863/RFC-1863.txt","sha256":"2f9e84d9b80685ae288249fa7fa073f77e9dbb1282f951c8c1b0af5632cddf26"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use and detailed design of Route Servers\n for dissemination of routing information among BGP/IDRP speaking\n routers.\n\n The intention of the proposed technique is to reduce overhead and\n management complexity of maintaining numerous direct BGP/IDRP\n sessions which otherwise might be required or desired among routers\n within a single routing domain as well as among routers in different\n domains that are connected to a common switched fabric (e.g. an ATM\n cloud).\n\n1. Overview\n\n Current deployments of Exterior Routing protocols, such as the Border\n Gateway Protocol [BGP4] and the adaptation of the ISO Inter-Domain\n Routing Protocol [IDRP], require that all BGP/IDRP routers, which\n participate in inter-domain routing (border routers) and belong to\n the same routing domain, establish a full mesh connectivity with each\n other for purpose of exchanging routing informa","scope_keywords":["1863","attribute","attributes","management","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1966","folder":"IETF/RFC-1966","source":"IETF/RFC-1966/RFC-1966.txt","version":null},{"body":"IETF","designation":"RFC 2796","folder":"IETF/RFC-2796","source":"IETF/RFC-2796/RFC-2796.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4223","folder":"IETF/RFC-4223","source":"IETF/RFC-4223/RFC-4223.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 1863 This document describes the use and detailed design of Route Servers\n for dissemination of routing information among BGP/IDRP speaking\n routers.\n\n The intention of the proposed technique is to reduce overhead and\n management complexity of maintaining numerous direct BGP/IDRP\n sessions which otherwise might be required or desired among routers\n within a single routing domain as well as among routers in different\n domains that are connected to a common switched fabric (e.g. an ATM\n cloud).\n\n1. Overview\n\n Current deployments of Exterior Routing protocols, such as the Border\n Gateway Protocol [BGP4] and the adaptation of the ISO Inter-Domain\n Routing Protocol [IDRP], require that all BGP/IDRP routers, which\n participate in inter-domain routing (border routers) and belong to\n the same routing domain, establish a full mesh connectivity with each\n other for purpose of exchanging routing informa 1863 attribute attributes management path policies nested-reference unchanged"},{"id":"IETF RFC 1965","type":"specification","body":"IETF","designation":"RFC 1965","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1965.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1965.txt","https://www.rfc-editor.org/rfc/rfc1965.pdf"],"folder":"IETF/RFC-1965","files":{"txt":{"path":"standards/IETF/RFC-1965/RFC-1965.txt","sha256":"1f9a24da8d46b06f00a994296c0a9a219c1fb4d18ba84d28a13273b800df8c75"}},"tags":["nested-reference","unchanged"],"summary":"Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP networks.\n\n This document describes an extension to BGP which may be used to\n create a confederation of autonomous systems which is represented as\n one single autonomous system to BGP peers external to the\n confederation.\n\n The intention of this extension is to aid in policy administration\n and reduce the management complexity of maintaining a large\n autonomous system.\n\n The extension this document describes is widely deployed in the\n Internet today.","scope_keywords":["1965","algorithm","attribute","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1966","folder":"IETF/RFC-1966","source":"IETF/RFC-1966/RFC-1966.txt","version":null},{"body":"IETF","designation":"RFC 1997","folder":"IETF/RFC-1997","source":"IETF/RFC-1997/RFC-1997.txt","version":null},{"body":"IETF","designation":"RFC 2796","folder":"IETF/RFC-2796","source":"IETF/RFC-2796/RFC-2796.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 1965 Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP networks.\n\n This document describes an extension to BGP which may be used to\n create a confederation of autonomous systems which is represented as\n one single autonomous system to BGP peers external to the\n confederation.\n\n The intention of this extension is to aid in policy administration\n and reduce the management complexity of maintaining a large\n autonomous system.\n\n The extension this document describes is widely deployed in the\n Internet today. 1965 algorithm attribute management path policy nested-reference unchanged"},{"id":"IETF RFC 1966","type":"specification","body":"IETF","designation":"RFC 1966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1966.txt","https://www.rfc-editor.org/rfc/rfc1966.pdf"],"folder":"IETF/RFC-1966","files":{"txt":{"path":"standards/IETF/RFC-1966/RFC-1966.txt","sha256":"fc000fbfc38511d4ff2a462e22f5234512eeacf81fc48363402b2c03fa990ada"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Bates\nRequest for Comments: 1966 cisco Systems\nCategory: Experimental R. Chandra\n cisco Systems\n June 1996\n\n BGP Route Reflection\n An alternative to full mesh IBGP\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets. BGP deployments are\n configured such that that all BGP speakers within a single AS must be\n fully meshed so that any external routing information must be re-\n distributed to all other routers within that AS. This represents a\n serious scaling problem that has been well documented with several\n alternatives proposed [2,3].\n\n This d","scope_keywords":["1966","attribute","attributes","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2547","folder":"IETF/RFC-2547","source":"IETF/RFC-2547/RFC-2547.txt","version":null},{"body":"IETF","designation":"RFC 2796","folder":"IETF/RFC-2796","source":"IETF/RFC-2796/RFC-2796.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null}],"search_text":"IETF RFC 1966 Network Working Group T. Bates\nRequest for Comments: 1966 cisco Systems\nCategory: Experimental R. Chandra\n cisco Systems\n June 1996\n\n BGP Route Reflection\n An alternative to full mesh IBGP\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets. BGP deployments are\n configured such that that all BGP speakers within a single AS must be\n fully meshed so that any external routing information must be re-\n distributed to all other routers within that AS. This represents a\n serious scaling problem that has been well documented with several\n alternatives proposed [2,3].\n\n This d 1966 attribute attributes management path nested-reference unchanged"},{"id":"IETF RFC 1997","type":"specification","body":"IETF","designation":"RFC 1997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1997.txt","https://www.rfc-editor.org/rfc/rfc1997.pdf"],"folder":"IETF/RFC-1997","files":{"txt":{"path":"standards/IETF/RFC-1997/RFC-1997.txt","sha256":"6ed254768c9b56317a148cad33a4056b56666857f905d58dd73b3688589b237f"}},"tags":["nested-reference","unchanged"],"summary":"Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets.\n\n This document describes an extension to BGP which may be used to pass\n additional information to both neighboring and remote BGP peers.\n\n The intention of the proposed technique is to aid in policy\n administration and reduce the management complexity of maintaining\n the Internet.","scope_keywords":["1997","attribute","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1998","folder":"IETF/RFC-1998","source":"IETF/RFC-1998/RFC-1998.txt","version":null},{"body":"IETF","designation":"RFC 2260","folder":"IETF/RFC-2260","source":"IETF/RFC-2260/RFC-2260.txt","version":null},{"body":"IETF","designation":"RFC 2280","folder":"IETF/RFC-2280","source":"IETF/RFC-2280/RFC-2280.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3704","folder":"IETF/RFC-3704","source":"IETF/RFC-3704/RFC-3704.txt","version":null},{"body":"IETF","designation":"RFC 3765","folder":"IETF/RFC-3765","source":"IETF/RFC-3765/RFC-3765.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4384","folder":"IETF/RFC-4384","source":"IETF/RFC-4384/RFC-4384.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 1997 Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets.\n\n This document describes an extension to BGP which may be used to pass\n additional information to both neighboring and remote BGP peers.\n\n The intention of the proposed technique is to aid in policy\n administration and reduce the management complexity of maintaining\n the Internet. 1997 attribute management path policies policy nested-reference unchanged"},{"id":"IETF RFC 1998","type":"specification","body":"IETF","designation":"RFC 1998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1998.txt","https://www.rfc-editor.org/rfc/rfc1998.pdf"],"folder":"IETF/RFC-1998","files":{"txt":{"path":"standards/IETF/RFC-1998/RFC-1998.txt","sha256":"81280b7ea04c87db20cf34ec288f565decc102e4efc005581a7974101537950c"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an application of the BGP community attribute\n [2] in simplifying the implementation and configuration of routing\n policies in the multi-provider Internet. It shows how the community\n based configuration can be used to replace the AS-based customization\n of the BGP \"LOCAL_PREF\" attribute, a common method used today. Not\n only does the technique presented simplifies configuration and\n management at the provider level, it also represents a paradigm shift\n in that it gives the potential for the customer to control its own\n routing policy with respect to its service provider, as well as\n providing the ability for policy configuration to be done at a prefix\n based granularity rather than the more common AS based granularity.\n\n1. Introduction\n\n In the multi-provider Internet, it is common for a service subscriber\n (i.e., customer) to have more than one service provider, ","scope_keywords":["1998","attribute","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2650","folder":"IETF/RFC-2650","source":"IETF/RFC-2650/RFC-2650.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null}],"search_text":"IETF RFC 1998 This document presents an application of the BGP community attribute\n [2] in simplifying the implementation and configuration of routing\n policies in the multi-provider Internet. It shows how the community\n based configuration can be used to replace the AS-based customization\n of the BGP \"LOCAL_PREF\" attribute, a common method used today. Not\n only does the technique presented simplifies configuration and\n management at the provider level, it also represents a paradigm shift\n in that it gives the potential for the customer to control its own\n routing policy with respect to its service provider, as well as\n providing the ability for policy configuration to be done at a prefix\n based granularity rather than the more common AS based granularity.\n\n1. Introduction\n\n In the multi-provider Internet, it is common for a service subscriber\n (i.e., customer) to have more than one service provider,  1998 attribute management path policies policy nested-reference unchanged"},{"id":"IETF RFC 2545","type":"specification","body":"IETF","designation":"RFC 2545","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2545.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2545.txt","https://www.rfc-editor.org/rfc/rfc2545.pdf"],"folder":"IETF/RFC-2545","files":{"txt":{"path":"standards/IETF/RFC-2545/RFC-2545.txt","sha256":"b0f0706fda1c881ad793810ad22ec3b1577a9df1794837ddb320ec42969c80bc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Marques\nRequest for Comments: 2545 cisco Systems, Inc.\nCategory: Standards Track F. Dupont\n Inria\n March 1999\n\n Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n BGP-4 Multiprotocol Extensions [BGP-MP] defines the format of two BGP\n attributes (MPREACHNLRI and MPUNREACHNLRI) that can be used to\n announce and withdraw the announcement of reachability information.\n This document defines how compli","scope_keywords":["2545","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 2545 Network Working Group P. Marques\nRequest for Comments: 2545 cisco Systems, Inc.\nCategory: Standards Track F. Dupont\n Inria\n March 1999\n\n Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n BGP-4 Multiprotocol Extensions [BGP-MP] defines the format of two BGP\n attributes (MPREACHNLRI and MPUNREACHNLRI) that can be used to\n announce and withdraw the announcement of reachability information.\n This document defines how compli 2545 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 2796","type":"specification","body":"IETF","designation":"RFC 2796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2796.txt","https://www.rfc-editor.org/rfc/rfc2796.pdf"],"folder":"IETF/RFC-2796","files":{"txt":{"path":"standards/IETF/RFC-2796/RFC-2796.txt","sha256":"83734aabc7ee52da9aadc9b8bf48bb01ede5c67bcc79bbe1a15a859ae77c3284"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Bates\nRequest for Comments: 2796 Cisco Systems\nUpdates: 1966 R. Chandra\nCategory: Standards Track E. Chen\n Redback Networks\n April 2000\n\n BGP Route Reflection -\n An Alternative to Full Mesh IBGP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets. Currently in the Internet BGP\n deployments are configured such that that all BGP speakers within a\n single AS ","scope_keywords":["2796","attribute","attributes","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 3345","folder":"IETF/RFC-3345","source":"IETF/RFC-3345/RFC-3345.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4223","folder":"IETF/RFC-4223","source":"IETF/RFC-4223/RFC-4223.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 2796 Network Working Group T. Bates\nRequest for Comments: 2796 Cisco Systems\nUpdates: 1966 R. Chandra\nCategory: Standards Track E. Chen\n Redback Networks\n April 2000\n\n BGP Route Reflection -\n An Alternative to Full Mesh IBGP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Border Gateway Protocol [1] is an inter-autonomous system routing\n protocol designed for TCP/IP internets. Currently in the Internet BGP\n deployments are configured such that that all BGP speakers within a\n single AS  2796 attribute attributes management path nested-reference unchanged"},{"id":"IETF RFC 2842","type":"specification","body":"IETF","designation":"RFC 2842","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2842.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2842.txt","https://www.rfc-editor.org/rfc/rfc2842.pdf"],"folder":"IETF/RFC-2842","files":{"txt":{"path":"standards/IETF/RFC-2842/RFC-2842.txt","sha256":"0cf155bde284545f67762b22af90fd422af4cf0ac0ee1b3bc1bac52774cb831e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Chandra\nRequest for Comments: 2842 Redback Networks Inc.\nCategory: Standards Track J. Scudder\n cisco Systems\n May 2000\n\n Capabilities Advertisement with BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently BGP-4 [BGP-4] requires that when a BGP speaker receives an\n OPEN message with one or more unrecognized Optional Parameters, the\n speaker must terminate BGP peering. This complicates introduction of\n new capabilities in BGP.\n\n This document defines","scope_keywords":["2842","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2918","folder":"IETF/RFC-2918","source":"IETF/RFC-2918/RFC-2918.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3392","folder":"IETF/RFC-3392","source":"IETF/RFC-3392/RFC-3392.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null}],"search_text":"IETF RFC 2842 Network Working Group R. Chandra\nRequest for Comments: 2842 Redback Networks Inc.\nCategory: Standards Track J. Scudder\n cisco Systems\n May 2000\n\n Capabilities Advertisement with BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently BGP-4 [BGP-4] requires that when a BGP speaker receives an\n OPEN message with one or more unrecognized Optional Parameters, the\n speaker must terminate BGP peering. This complicates introduction of\n new capabilities in BGP.\n\n This document defines 2842 policy signature nested-reference unchanged"},{"id":"IETF RFC 2918","type":"specification","body":"IETF","designation":"RFC 2918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2918.txt","https://www.rfc-editor.org/rfc/rfc2918.pdf"],"folder":"IETF/RFC-2918","files":{"txt":{"path":"standards/IETF/RFC-2918/RFC-2918.txt","sha256":"591bb18fd96ff21e1b03fdfb6b75dbd3c21fe158b5788b46af9bfe738c0cff00"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Chen\nRequest for Comments: 2918 Redback Networks\nCategory: Standards Track September 2000\n\n Route Refresh Capability for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines a new Border Gateway Protocol (BGP) capability\n termed 'Route Refresh Capability', which would allow the dynamic\n exchange of route refresh request between BGP speakers and subsequent\n re-advertisement of the respective Adj-RIB-Out. One possible\n application of this ","scope_keywords":["2918","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null}],"search_text":"IETF RFC 2918 Network Working Group E. Chen\nRequest for Comments: 2918 Redback Networks\nCategory: Standards Track September 2000\n\n Route Refresh Capability for BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines a new Border Gateway Protocol (BGP) capability\n termed 'Route Refresh Capability', which would allow the dynamic\n exchange of route refresh request between BGP speakers and subsequent\n re-advertisement of the respective Adj-RIB-Out. One possible\n application of this  2918 policies policy nested-reference unchanged"},{"id":"IETF RFC 3037","type":"specification","body":"IETF","designation":"RFC 3037","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3037.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3037.txt","https://www.rfc-editor.org/rfc/rfc3037.pdf"],"folder":"IETF/RFC-3037","files":{"txt":{"path":"standards/IETF/RFC-3037/RFC-3037.txt","sha256":"073848794721558875c9bfeb06eb4108f3762d0e2fdff2bd8ce501c79c4e7ce2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Thomas\nRequest for Comments: 3037 Cisco Systems, Inc.\nCategory: Informational E. Gray\n Zaffire, Inc.\n January 2001\n\n LDP Applicability\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n Multiprotocol Label Switching (MPLS) is a method for forwarding\n packets that uses short, fixed-length values carried by packets,\n called labels, to determine packet nexthops. A fundamental concept\n in MPLS is that two Label Switching Routers (LSRs) must agree on the\n meaning of the labels used to forward traffic between and through\n them. This common understanding is achieved by using a set of\n procedures, called a label distribution protocol, by which one LSR\n","scope_keywords":["3037","crl","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null}],"search_text":"IETF RFC 3037 Network Working Group B. Thomas\nRequest for Comments: 3037 Cisco Systems, Inc.\nCategory: Informational E. Gray\n Zaffire, Inc.\n January 2001\n\n LDP Applicability\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n Multiprotocol Label Switching (MPLS) is a method for forwarding\n packets that uses short, fixed-length values carried by packets,\n called labels, to determine packet nexthops. A fundamental concept\n in MPLS is that two Label Switching Routers (LSRs) must agree on the\n meaning of the labels used to forward traffic between and through\n them. This common understanding is achieved by using a set of\n procedures, called a label distribution protocol, by which one LSR\n 3037 crl path nested-reference unchanged"},{"id":"IETF RFC 3065","type":"specification","body":"IETF","designation":"RFC 3065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3065.txt","https://www.rfc-editor.org/rfc/rfc3065.pdf"],"folder":"IETF/RFC-3065","files":{"txt":{"path":"standards/IETF/RFC-3065/RFC-3065.txt","sha256":"fd8ad65a5c7fb583e0b99031e7bc188649f70bb1006bcb7acc54f75abb94022d"}},"tags":["nested-reference","unchanged"],"summary":"The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for Transmission Control Protocol/Internet\n Protocol (TCP/IP) networks. BGP requires that all BGP speakers\n within a single autonomous system (AS) must be fully meshed. This\n represents a serious scaling problem that has been well documented in\n a number of proposals.\n\n This document describes an extension to BGP which may be used to\n create a confederation of autonomous systems that is represented as a\n single autonomous system to BGP peers external to the confederation,\n thereby removing the \"full mesh\" requirement. The intention of this\n extension is to aid in policy administration and reduce the\n management complexity of maintaining a large autonomous system.\n\n1. Specification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMME","scope_keywords":["3065","attribute","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3345","folder":"IETF/RFC-3345","source":"IETF/RFC-3345/RFC-3345.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4223","folder":"IETF/RFC-4223","source":"IETF/RFC-4223/RFC-4223.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 3065 The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for Transmission Control Protocol/Internet\n Protocol (TCP/IP) networks. BGP requires that all BGP speakers\n within a single autonomous system (AS) must be fully meshed. This\n represents a serious scaling problem that has been well documented in\n a number of proposals.\n\n This document describes an extension to BGP which may be used to\n create a confederation of autonomous systems that is represented as a\n single autonomous system to BGP peers external to the confederation,\n thereby removing the \"full mesh\" requirement. The intention of this\n extension is to aid in policy administration and reduce the\n management complexity of maintaining a large autonomous system.\n\n1. Specification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMME 3065 attribute key management path policy nested-reference unchanged"},{"id":"IETF RFC 3107","type":"specification","body":"IETF","designation":"RFC 3107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3107.txt","https://www.rfc-editor.org/rfc/rfc3107.pdf"],"folder":"IETF/RFC-3107","files":{"txt":{"path":"standards/IETF/RFC-3107/RFC-3107.txt","sha256":"dc4c88aaef109acafe33bf42aebe36ea50c647b61f62daa2ac3c34ca7b50e88e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the way in which the label mapping\n information for a particular route is piggybacked in the same Border\n Gateway Protocol (BGP) Update message that is used to distribute the\n route itself. When BGP is used to distribute a particular route, it\n can be also be used to distribute a Multiprotocol Label Switching\n (MPLS) label which is mapped to that route.","scope_keywords":["3107","attribute","attributes","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4781","folder":"IETF/RFC-4781","source":"IETF/RFC-4781/RFC-4781.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null}],"search_text":"IETF RFC 3107 This document specifies the way in which the label mapping\n information for a particular route is piggybacked in the same Border\n Gateway Protocol (BGP) Update message that is used to distribute the\n route itself. When BGP is used to distribute a particular route, it\n can be also be used to distribute a Multiprotocol Label Switching\n (MPLS) label which is mapped to that route. 3107 attribute attributes key path nested-reference unchanged"},{"id":"IETF RFC 3345","type":"specification","body":"IETF","designation":"RFC 3345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3345.txt","https://www.rfc-editor.org/rfc/rfc3345.pdf"],"folder":"IETF/RFC-3345","files":{"txt":{"path":"standards/IETF/RFC-3345/RFC-3345.txt","sha256":"83e5b15f5e4290eaa49518c6f2cb94e19ef72468c302041650b8b3985ddd3c12"}},"tags":["nested-reference","unchanged"],"summary":"In particular configurations, the BGP scaling mechanisms defined in\n \"BGP Route Reflection - An Alternative to Full Mesh IBGP\" and\n \"Autonomous System Confederations for BGP\" will introduce persistent\n BGP route oscillation. This document discusses the two types of\n persistent route oscillation that have been identified, describes\n when these conditions will occur, and provides some network design\n guidelines to avoid introducing such occurrences.\n\n1. Introduction\n\n The Border Gateway Protocol (BGP) is an inter-Autonomous System\n routing protocol. The primary function of a BGP speaking system is\n to exchange network reachability information with other BGP systems.\n\n In particular configurations, the BGP [1] scaling mechanisms defined\n in \"BGP Route Reflection - An Alternative to Full Mesh IBGP\" [2] and\n \"Autonomous System Confederations for BGP\" [3] will introduce\n persistent BGP route o","scope_keywords":["3345","attribute","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 3345 In particular configurations, the BGP scaling mechanisms defined in\n \"BGP Route Reflection - An Alternative to Full Mesh IBGP\" and\n \"Autonomous System Confederations for BGP\" will introduce persistent\n BGP route oscillation. This document discusses the two types of\n persistent route oscillation that have been identified, describes\n when these conditions will occur, and provides some network design\n guidelines to avoid introducing such occurrences.\n\n1. Introduction\n\n The Border Gateway Protocol (BGP) is an inter-Autonomous System\n routing protocol. The primary function of a BGP speaking system is\n to exchange network reachability information with other BGP systems.\n\n In particular configurations, the BGP [1] scaling mechanisms defined\n in \"BGP Route Reflection - An Alternative to Full Mesh IBGP\" [2] and\n \"Autonomous System Confederations for BGP\" [3] will introduce\n persistent BGP route o 3345 attribute path policies nested-reference unchanged"},{"id":"IETF RFC 3392","type":"specification","body":"IETF","designation":"RFC 3392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3392.txt","https://www.rfc-editor.org/rfc/rfc3392.pdf"],"folder":"IETF/RFC-3392","files":{"txt":{"path":"standards/IETF/RFC-3392/RFC-3392.txt","sha256":"57dddcb69dd646f7e72f3d505fb2dac9d89acc18f277933907f36d3e4977cc71"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Chandra\nRequest for Comments: 3392 Redback Networks\nObsoletes: 2842 J. Scudder\nCategory: Standards Track Cisco Systems\n November 2002\n\n Capabilities Advertisement with BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines a new Optional Parameter, called Capabilities,\n that is expected to facilitate the introduction of new capabilities\n in the Border Gateway Protocol (BGP) by providing graceful capability\n advertisement without requiring ","scope_keywords":["3392","key","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4724","folder":"IETF/RFC-4724","source":"IETF/RFC-4724/RFC-4724.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null}],"search_text":"IETF RFC 3392 Network Working Group R. Chandra\nRequest for Comments: 3392 Redback Networks\nObsoletes: 2842 J. Scudder\nCategory: Standards Track Cisco Systems\n November 2002\n\n Capabilities Advertisement with BGP-4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines a new Optional Parameter, called Capabilities,\n that is expected to facilitate the introduction of new capabilities\n in the Border Gateway Protocol (BGP) by providing graceful capability\n advertisement without requiring  3392 key policy signature nested-reference unchanged"},{"id":"IETF RFC 3528","type":"specification","body":"IETF","designation":"RFC 3528","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3528.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3528.txt","https://www.rfc-editor.org/rfc/rfc3528.pdf"],"folder":"IETF/RFC-3528","files":{"txt":{"path":"standards/IETF/RFC-3528/RFC-3528.txt","sha256":"d6c0e6e7af2715312ccb5e3ee95c2b1926e779bb8dbe17f4ce08ec9ae8ecd350"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Mesh-enhanced Service Location Protocol\n (mSLP). mSLP enhances the Service Location Protocol (SLP) with a\n scope-based fully-meshed peering Directory Agent (DA) architecture.\n Peer DAs exchange new service registrations in shared scopes via\n anti-entropy and direct forwarding. mSLP improves the reliability\n and consistency of SLP DA services, and simplifies Service Agent (SA)\n registrations in systems with multiple DAs. mSLP is backward\n compatible with SLPv2 and can be deployed incrementally.","scope_keywords":["3528","attribute","key","management","pid","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null}],"search_text":"IETF RFC 3528 This document describes the Mesh-enhanced Service Location Protocol\n (mSLP). mSLP enhances the Service Location Protocol (SLP) with a\n scope-based fully-meshed peering Directory Agent (DA) architecture.\n Peer DAs exchange new service registrations in shared scopes via\n anti-entropy and direct forwarding. mSLP improves the reliability\n and consistency of SLP DA services, and simplifies Service Agent (SA)\n registrations in systems with multiple DAs. mSLP is backward\n compatible with SLPv2 and can be deployed incrementally. 3528 attribute key management pid timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3682","type":"specification","body":"IETF","designation":"RFC 3682","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3682.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3682.txt","https://www.rfc-editor.org/rfc/rfc3682.pdf"],"folder":"IETF/RFC-3682","files":{"txt":{"path":"standards/IETF/RFC-3682/RFC-3682.txt","sha256":"37cc3afa2be836c0baeda6d478ce80a2375dd98f50a2880713920f3111d2b1d5"}},"tags":["nested-reference","unchanged"],"summary":"The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)\n to protect a protocol stack from CPU-utilization based attacks has\n been proposed in many settings (see for example, RFC 2461). This\n document generalizes these techniques for use by other protocols such\n as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP),\n Bidirectional Forwarding Detection, and Label Distribution Protocol\n (LDP) (RFC 3036). While the Generalized TTL Security Mechanism\n (GTSM) is most effective in protecting directly connected protocol\n peers, it can also provide a lower level of protection to multi-hop\n sessions. GTSM is not directly applicable to protocols employing\n flooding mechanisms (e.g., multicast), and use of multi-hop GTSM\n should be considered on a case-by-case basis.","scope_keywords":["3682","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null}],"search_text":"IETF RFC 3682 The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6)\n to protect a protocol stack from CPU-utilization based attacks has\n been proposed in many settings (see for example, RFC 2461). This\n document generalizes these techniques for use by other protocols such\n as BGP (RFC 1771), Multicast Source Discovery Protocol (MSDP),\n Bidirectional Forwarding Detection, and Label Distribution Protocol\n (LDP) (RFC 3036). While the Generalized TTL Security Mechanism\n (GTSM) is most effective in protecting directly connected protocol\n peers, it can also provide a lower level of protection to multi-hop\n sessions. GTSM is not directly applicable to protocols employing\n flooding mechanisms (e.g., multicast), and use of multi-hop GTSM\n should be considered on a case-by-case basis. 3682 key path nested-reference unchanged"},{"id":"IETF RFC 3917","type":"specification","body":"IETF","designation":"RFC 3917","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3917.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3917.txt","https://www.rfc-editor.org/rfc/rfc3917.pdf"],"folder":"IETF/RFC-3917","files":{"txt":{"path":"standards/IETF/RFC-3917/RFC-3917.txt","sha256":"d433f7490e2a049789c30d31a8cf6318883a471f4b4b3817e2f23daaf0f88c66"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines requirements for the export of measured IP flow\n information out of routers, traffic measurement probes, and\n middleboxes.","scope_keywords":["3917","encryption","key","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5103","folder":"IETF/RFC-5103","source":"IETF/RFC-5103/RFC-5103.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 3917 This memo defines requirements for the export of measured IP flow\n information out of routers, traffic measurement probes, and\n middleboxes. 3917 encryption key timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3964","type":"specification","body":"IETF","designation":"RFC 3964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3964.txt","https://www.rfc-editor.org/rfc/rfc3964.pdf"],"folder":"IETF/RFC-3964","files":{"txt":{"path":"standards/IETF/RFC-3964/RFC-3964.txt","sha256":"cc6dd978be15d30d06197ae8bcd77996ccb912081d3ff661c1f746f47bfeace2"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 interim mechanism 6to4 (RFC3056) uses automatic\n IPv6-over-IPv4 tunneling to interconnect IPv6 networks. The\n architecture includes 6to4 routers and 6to4 relay routers, which\n accept and decapsulate IPv4 protocol-41 (\"IPv6-in-IPv4\") traffic from\n any node in the IPv4 internet. This characteristic enables a number\n of security threats, mainly Denial of Service. It also makes it\n easier for nodes to spoof IPv6 addresses. This document discusses\n these issues in more detail and suggests enhancements to alleviate\n the problems.\n\nSavola & Patel Informational [Page 1]\n\f\nRFC 3964 Security Considerations for 6to4 December 2004","scope_keywords":["3964","hash","hashing","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5158","folder":"IETF/RFC-5158","source":"IETF/RFC-5158/RFC-5158.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 3964 The IPv6 interim mechanism 6to4 (RFC3056) uses automatic\n IPv6-over-IPv4 tunneling to interconnect IPv6 networks. The\n architecture includes 6to4 routers and 6to4 relay routers, which\n accept and decapsulate IPv4 protocol-41 (\"IPv6-in-IPv4\") traffic from\n any node in the IPv4 internet. This characteristic enables a number\n of security threats, mainly Denial of Service. It also makes it\n easier for nodes to spoof IPv6 addresses. This document discusses\n these issues in more detail and suggests enhancements to alleviate\n the problems.\n\nSavola & Patel Informational [Page 1]\n\f\nRFC 3964 Security Considerations for 6to4 December 2004 3964 hash hashing key trust nested-reference unchanged"},{"id":"IETF RFC 4001","type":"specification","body":"IETF","designation":"RFC 4001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4001.txt","https://www.rfc-editor.org/rfc/rfc4001.pdf"],"folder":"IETF/RFC-4001","files":{"txt":{"path":"standards/IETF/RFC-4001/RFC-4001.txt","sha256":"b5b990cf15e632b83d4540c9f559e4a6fed87e877d130b647ae8b81e9d579b60"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these textual conventions will be imported and used in MIB\n modules that would otherwise define their own representations.\n\nDaniele, et al. Standards Track [Page 1]\n\f\nRFC 4001 Internet Network Address Conventions February 2005","scope_keywords":["4001","management","pki","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 4001 This MIB module defines textual conventions to represent commonly\n used Internet network layer addressing information. The intent is\n that these textual conventions will be imported and used in MIB\n modules that would otherwise define their own representations.\n\nDaniele, et al. Standards Track [Page 1]\n\f\nRFC 4001 Internet Network Address Conventions February 2005 4001 management pki presentation nested-reference unchanged"},{"id":"IETF RFC 4098","type":"specification","body":"IETF","designation":"RFC 4098","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4098.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4098.txt","https://www.rfc-editor.org/rfc/rfc4098.pdf"],"folder":"IETF/RFC-4098","files":{"txt":{"path":"standards/IETF/RFC-4098/RFC-4098.txt","sha256":"22c6880586d25ef27a4d91befed0deae99ae696edd47b7cf9116313c9fd817ce"}},"tags":["nested-reference","unchanged"],"summary":"This document establishes terminology to standardize the description\n of benchmarking methodology for measuring eBGP convergence in the\n control plane of a single BGP device. Future documents will address\n iBGP convergence, the initiation of forwarding based on converged\n control plane information and multiple interacting BGP devices. This\n terminology is applicable to both IPv4 and IPv6. Illustrative\n examples of each version are included where relevant.\n\nBerkowitz, et al. Informational [Page 1]\n\f\nRFC 4098 Terminology for Benchmarking BGP June 2005","scope_keywords":["4098","authentication","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null}],"search_text":"IETF RFC 4098 This document establishes terminology to standardize the description\n of benchmarking methodology for measuring eBGP convergence in the\n control plane of a single BGP device. Future documents will address\n iBGP convergence, the initiation of forwarding based on converged\n control plane information and multiple interacting BGP devices. This\n terminology is applicable to both IPv4 and IPv6. Illustrative\n examples of each version are included where relevant.\n\nBerkowitz, et al. Informational [Page 1]\n\f\nRFC 4098 Terminology for Benchmarking BGP June 2005 4098 authentication policy nested-reference unchanged"},{"id":"IETF RFC 4216","type":"specification","body":"IETF","designation":"RFC 4216","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4216.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4216.txt","https://www.rfc-editor.org/rfc/rfc4216.pdf"],"folder":"IETF/RFC-4216","files":{"txt":{"path":"standards/IETF/RFC-4216/RFC-4216.txt","sha256":"aab2cee4f31427852cc3f680378821a2c1692b5eddbf8f89568a02e6adaccc6c"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses requirements for the support of inter-AS MPLS\n Traffic Engineering (MPLS TE). Its main objective is to present a\n set of requirements and scenarios which would result in general\n guidelines for the definition, selection, and specification\n development for any technical solution(s) meeting these requirements\n and supporting the scenarios.","scope_keywords":["4216","attribute","key","management","path","policies","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null}],"search_text":"IETF RFC 4216 This document discusses requirements for the support of inter-AS MPLS\n Traffic Engineering (MPLS TE). Its main objective is to present a\n set of requirements and scenarios which would result in general\n guidelines for the definition, selection, and specification\n development for any technical solution(s) meeting these requirements\n and supporting the scenarios. 4216 attribute key management path policies policy risk nested-reference unchanged"},{"id":"IETF RFC 4384","type":"specification","body":"IETF","designation":"RFC 4384","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4384.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4384.txt","https://www.rfc-editor.org/rfc/rfc4384.pdf"],"folder":"IETF/RFC-4384","files":{"txt":{"path":"standards/IETF/RFC-4384/RFC-4384.txt","sha256":"d000a9a58162e2c91721f60e8c6e89b42feb91e2bc79b414ddaf27da84904a55"}},"tags":["nested-reference","unchanged"],"summary":"BGP communities (RFC 1997) are used by service providers for many\n purposes, including tagging of customer, peer, and geographically\n originated routes. Such tagging is typically used to control the\n scope of redistribution of routes within a provider's network and to\n its peers and customers. With the advent of large-scale BGP data\n collection (and associated research), it has become clear that the\n information carried in such communities is essential for a deeper\n understanding of the global routing system. This memo defines\n standard (outbound) communities and their encodings for export to BGP\n route collectors.\n\nMeyer Best Current Practice [Page 1]\n\f\nRFC 4384 BGP Communities for Data Collection February 2006","scope_keywords":["4384","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null}],"search_text":"IETF RFC 4384 BGP communities (RFC 1997) are used by service providers for many\n purposes, including tagging of customer, peer, and geographically\n originated routes. Such tagging is typically used to control the\n scope of redistribution of routes within a provider's network and to\n its peers and customers. With the advent of large-scale BGP data\n collection (and associated research), it has become clear that the\n information carried in such communities is essential for a deeper\n understanding of the global routing system. This memo defines\n standard (outbound) communities and their encodings for export to BGP\n route collectors.\n\nMeyer Best Current Practice [Page 1]\n\f\nRFC 4384 BGP Communities for Data Collection February 2006 4384 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 1775","type":"specification","body":"IETF","designation":"RFC 1775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1775.txt","https://www.rfc-editor.org/rfc/rfc1775.pdf"],"folder":"IETF/RFC-1775","files":{"txt":{"path":"standards/IETF/RFC-1775/RFC-1775.txt","sha256":"102dde14833c22861fe06529724286c967fb0a2f7fe89315e32c74c90a5ed5d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker\nRequest for Comments: 1775 Brandenburg Consulting\nCategory: Informational March 1995\n\n To Be \"On\" the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Internet permits different levels of access for consumers and\n providers of service. The nature of those differences is quite\n important in the capabilities They afford. Hence, it is appropriate\n to provide terminology that distinguishes among the range, so that\n the Internet community can gain some clarity when distinguishing\n whether a user (or an organization) is \"on\" the Internet. This\n document suggests four terms, for distinguishing the major classes of\n access.\n\n1. INTRODUCTION\n\n The Internet is many things to many people. It began as a techn","scope_keywords":["1775"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null}],"search_text":"IETF RFC 1775 Network Working Group D. Crocker\nRequest for Comments: 1775 Brandenburg Consulting\nCategory: Informational March 1995\n\n To Be \"On\" the Internet\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The Internet permits different levels of access for consumers and\n providers of service. The nature of those differences is quite\n important in the capabilities They afford. Hence, it is appropriate\n to provide terminology that distinguishes among the range, so that\n the Internet community can gain some clarity when distinguishing\n whether a user (or an organization) is \"on\" the Internet. This\n document suggests four terms, for distinguishing the major classes of\n access.\n\n1. INTRODUCTION\n\n The Internet is many things to many people. It began as a techn 1775 nested-reference unchanged"},{"id":"IETF RFC 1779","type":"specification","body":"IETF","designation":"RFC 1779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1779.txt","https://www.rfc-editor.org/rfc/rfc1779.pdf"],"folder":"IETF/RFC-1779","files":{"txt":{"path":"standards/IETF/RFC-1779/RFC-1779.txt","sha256":"8b178b7a8a0b0b2660515a252b6bfdf51bdc8e01d80fd7beb57c94d5d6511552"}},"tags":["nested-reference","unchanged"],"summary":"The OSI Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1.\n When a distinguished name is communicated between to users not using\n a directory protocol (e.g., in a mail message), there is a need to\n have a user-oriented string representation of distinguished name.\n This specification defines a string format for representing names,\n which is designed to give a clean representation of commonly used\n names, whilst being able to represent any distinguished name.","scope_keywords":["1779","attribute","attributes","key","keys","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1777","folder":"IETF/RFC-1777","source":"IETF/RFC-1777/RFC-1777.txt","version":null},{"body":"IETF","designation":"RFC 1778","folder":"IETF/RFC-1778","source":"IETF/RFC-1778/RFC-1778.txt","version":null},{"body":"IETF","designation":"RFC 1781","folder":"IETF/RFC-1781","source":"IETF/RFC-1781/RFC-1781.txt","version":null},{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null},{"body":"IETF","designation":"RFC 1959","folder":"IETF/RFC-1959","source":"IETF/RFC-1959/RFC-1959.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2872","folder":"IETF/RFC-2872","source":"IETF/RFC-2872/RFC-2872.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null}],"search_text":"IETF RFC 1779 The OSI Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1.\n When a distinguished name is communicated between to users not using\n a directory protocol (e.g., in a mail message), there is a need to\n have a user-oriented string representation of distinguished name.\n This specification defines a string format for representing names,\n which is designed to give a clean representation of commonly used\n names, whilst being able to represent any distinguished name. 1779 attribute attributes key keys path presentation nested-reference unchanged"},{"id":"IETF RFC 1960","type":"specification","body":"IETF","designation":"RFC 1960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1960.txt","https://www.rfc-editor.org/rfc/rfc1960.pdf"],"folder":"IETF/RFC-1960","files":{"txt":{"path":"standards/IETF/RFC-1960/RFC-1960.txt","sha256":"fec9f152d3f19d910a71364cb83addd1589cd9c204eeec8d48f4419989252a1c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 1960 University of Michigan\nObsoletes: 1558 June 1996\nCategory: Standards Track\n\n A String Representation of LDAP Search Filters\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Lightweight Directory Access Protocol (LDAP) [1] defines a\n network representation of a search filter transmitted to an LDAP\n server. Some applications may find it useful to have a common way of\n representing these search filters in a human-readable form. This\n document defines a human-readable string format for representing LDAP\n sea","scope_keywords":["1960","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null}],"search_text":"IETF RFC 1960 Network Working Group T. Howes\nRequest for Comments: 1960 University of Michigan\nObsoletes: 1558 June 1996\nCategory: Standards Track\n\n A String Representation of LDAP Search Filters\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Lightweight Directory Access Protocol (LDAP) [1] defines a\n network representation of a search filter transmitted to an LDAP\n server. Some applications may find it useful to have a common way of\n representing these search filters in a human-readable form. This\n document defines a human-readable string format for representing LDAP\n sea 1960 attribute presentation nested-reference unchanged"},{"id":"IETF RFC 2559","type":"specification","body":"IETF","designation":"RFC 2559","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2559.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2559.txt","https://www.rfc-editor.org/rfc/rfc2559.pdf"],"folder":"IETF/RFC-2559","files":{"txt":{"path":"standards/IETF/RFC-2559/RFC-2559.txt","sha256":"4ddca887b790b33556d62a3f048d2ba3ead445b21913bb04de8be8a048187921"}},"tags":["nested-reference","unchanged"],"summary":"The protocol described in this document is designed to satisfy some\n of the operational requirements within the Internet X.509 Public Key\n Infrastructure (IPKI). Specifically, this document addresses\n requirements to provide access to Public Key Infrastructure (PKI)\n repositories for the purposes of retrieving PKI information and\n managing that same information. The mechanism described in this\n document is based on the Lightweight Directory Access Protocol (LDAP)\n v2, defined in RFC 1777, defining a profile of that protocol for use\n within the IPKI and updates encodings for certificates and revocation\n lists from RFC 1778. Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents.\n\n The key words 'MUST', 'REQUIRED', 'SHOULD', 'RECOMMENDED', and 'MAY'\n in this document are to be interpreted as described in RFC 2119.\n\n2. Introduction\n\n This specifi","scope_keywords":["2559","attribute","attributes","authentication","certificate","certificates","credential","credentials","crl","issuer","key","management","pki","profile","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2587","folder":"IETF/RFC-2587","source":"IETF/RFC-2587/RFC-2587.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null}],"search_text":"IETF RFC 2559 The protocol described in this document is designed to satisfy some\n of the operational requirements within the Internet X.509 Public Key\n Infrastructure (IPKI). Specifically, this document addresses\n requirements to provide access to Public Key Infrastructure (PKI)\n repositories for the purposes of retrieving PKI information and\n managing that same information. The mechanism described in this\n document is based on the Lightweight Directory Access Protocol (LDAP)\n v2, defined in RFC 1777, defining a profile of that protocol for use\n within the IPKI and updates encodings for certificates and revocation\n lists from RFC 1778. Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents.\n\n The key words 'MUST', 'REQUIRED', 'SHOULD', 'RECOMMENDED', and 'MAY'\n in this document are to be interpreted as described in RFC 2119.\n\n2. Introduction\n\n This specifi 2559 attribute attributes authentication certificate certificates credential credentials crl issuer key management pki profile revocation subject nested-reference unchanged"},{"id":"IETF RFC 2587","type":"specification","body":"IETF","designation":"RFC 2587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2587.txt","https://www.rfc-editor.org/rfc/rfc2587.pdf"],"folder":"IETF/RFC-2587","files":{"txt":{"path":"standards/IETF/RFC-2587/RFC-2587.txt","sha256":"cc431f6ab64f000ed7b1329f73c4e05678ce42a98be79844be1b3b14c686f46f"}},"tags":["nested-reference","unchanged"],"summary":"The schema defined in this document is a minimal schema to support\n PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-\n specific components are specified here. LDAP servers, acting as PKIX\n repositories should support the auxiliary object classes defined in\n this specification and integrate this schema specification with the\n generic and other application-specific schemas as appropriate,\n depending on the services to be supplied by that server.\n\n The key words 'MUST', 'SHALL', 'REQUIRED', 'SHOULD', 'RECOMMENDED',\n and 'MAY' in this document are to be interpreted as described in RFC\n 2119.\n\n2. Introduction\n\n This specification is part of a multi-part standard for development\n of a Public Key Infrastructure (PKI) for the Internet. LDAPv2 is one\n mechanism defined for access to a PKI repository. Other mechanisms,\n such as http, are also defined. If an LDAP server, accessed by","scope_keywords":["2587","attribute","attributes","certificate","certificates","crl","http","issuer","key","pki","policy","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 2587 The schema defined in this document is a minimal schema to support\n PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-\n specific components are specified here. LDAP servers, acting as PKIX\n repositories should support the auxiliary object classes defined in\n this specification and integrate this schema specification with the\n generic and other application-specific schemas as appropriate,\n depending on the services to be supplied by that server.\n\n The key words 'MUST', 'SHALL', 'REQUIRED', 'SHOULD', 'RECOMMENDED',\n and 'MAY' in this document are to be interpreted as described in RFC\n 2119.\n\n2. Introduction\n\n This specification is part of a multi-part standard for development\n of a Public Key Infrastructure (PKI) for the Internet. LDAPv2 is one\n mechanism defined for access to a PKI repository. Other mechanisms,\n such as http, are also defined. If an LDAP server, accessed by 2587 attribute attributes certificate certificates crl http issuer key pki policy revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 2657","type":"specification","body":"IETF","designation":"RFC 2657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2657.txt","https://www.rfc-editor.org/rfc/rfc2657.pdf"],"folder":"IETF/RFC-2657","files":{"txt":{"path":"standards/IETF/RFC-2657/RFC-2657.txt","sha256":"799fb00d3e2e199628cfd13d4c58349b9c2c61933c12bd7fbd6c7083a02d6d12"}},"tags":["nested-reference","unchanged"],"summary":"LDAPv2 clients as implemented according to RFC 1777 [1] have no\n notion on referral. The integration between such a client and an\n Index Mesh, as defined by the Common Indexing Protocol [2], heavily\n depends on referrals and therefore needs to be handled in a special\n way. This document defines one possible way of doing this.\n\n1. Background\n\n During the development of the Common Indexing Protocol (CIP), one of\n the underlying assumptions was that the interaction between clients\n and the Index Mesh Servers [1] would heavily depend on the passing of\n referrals. Protocols like LDAPv2 [2] that lack this functionality\n need to compensate for it by some means. The way chosen in this memo\n is to add more intelligence into the client. There are two reasons\n behind this decision. First, this is not a major enhancement that is\n needed and secondly, that the intelligence when dealing with the\n Inde","scope_keywords":["2657","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2657 LDAPv2 clients as implemented according to RFC 1777 [1] have no\n notion on referral. The integration between such a client and an\n Index Mesh, as defined by the Common Indexing Protocol [2], heavily\n depends on referrals and therefore needs to be handled in a special\n way. This document defines one possible way of doing this.\n\n1. Background\n\n During the development of the Common Indexing Protocol (CIP), one of\n the underlying assumptions was that the interaction between clients\n and the Index Mesh Servers [1] would heavily depend on the passing of\n referrals. Protocols like LDAPv2 [2] that lack this functionality\n need to compensate for it by some means. The way chosen in this memo\n is to add more intelligence into the client. There are two reasons\n behind this decision. First, this is not a major enhancement that is\n needed and secondly, that the intelligence when dealing with the\n Inde 2657 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 4158","type":"specification","body":"IETF","designation":"RFC 4158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4158.txt","https://www.rfc-editor.org/rfc/rfc4158.pdf"],"folder":"IETF/RFC-4158","files":{"txt":{"path":"standards/IETF/RFC-4158/RFC-4158.txt","sha256":"5d67d470a12edf63574c421e43d2d6b86f78e2eb6c79282acb73917f824fb3be"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance and recommendations to developers\n building X.509 public-key certification paths within their\n applications. By following the guidance and recommendations defined\n in this document, an application developer is more likely to develop\n a robust X.509 certificate-enabled application that can build valid\n certification paths across a wide range of PKI environments.","scope_keywords":["4158","algorithm","algorithms","attribute","certificate","certificates","crl","http","issuer","key","path","pki","policies","policy","presentation","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null}],"search_text":"IETF RFC 4158 This document provides guidance and recommendations to developers\n building X.509 public-key certification paths within their\n applications. By following the guidance and recommendations defined\n in this document, an application developer is more likely to develop\n a robust X.509 certificate-enabled application that can build valid\n certification paths across a wide range of PKI environments. 4158 algorithm algorithms attribute certificate certificates crl http issuer key path pki policies policy presentation revocation nested-reference unchanged"},{"id":"IETF RFC 4523","type":"specification","body":"IETF","designation":"RFC 4523","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4523.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4523.txt","https://www.rfc-editor.org/rfc/rfc4523.pdf"],"folder":"IETF/RFC-4523","files":{"txt":{"path":"standards/IETF/RFC-4523/RFC-4523.txt","sha256":"40fc10767fd4957eafebba2ca1f72585d541190723ab53ea9c65dda3beb8000f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes schema for representing X.509 certificates,\n X.521 security information, and related elements in directories\n accessible using the Lightweight Directory Access Protocol (LDAP).\n The LDAP definitions for these X.509 and X.521 schema elements\n replace those provided in RFCs 2252 and 2256.\n\n1. Introduction\n\n This document provides LDAP [RFC4510] schema definitions [RFC4512]\n for a subset of elements specified in X.509 [X.509] and X.521\n [X.521], including attribute types for certificates, cross\n certificate pairs, and certificate revocation lists; matching rules\n to be used with these attribute types; and related object classes.\n LDAP syntax definitions are also provided for associated assertion\n and attribute values.\n\n As the semantics of these elements are as defined in X.509 and X.521,\n knowledge of X.509 and X.521 is necessary to make use of the LDAP\n schema defi","scope_keywords":["4523","algorithm","algorithms","attribute","certificate","certificates","crl","key","pki","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null}],"search_text":"IETF RFC 4523 This document describes schema for representing X.509 certificates,\n X.521 security information, and related elements in directories\n accessible using the Lightweight Directory Access Protocol (LDAP).\n The LDAP definitions for these X.509 and X.521 schema elements\n replace those provided in RFCs 2252 and 2256.\n\n1. Introduction\n\n This document provides LDAP [RFC4510] schema definitions [RFC4512]\n for a subset of elements specified in X.509 [X.509] and X.521\n [X.521], including attribute types for certificates, cross\n certificate pairs, and certificate revocation lists; matching rules\n to be used with these attribute types; and related object classes.\n LDAP syntax definitions are also provided for associated assertion\n and attribute values.\n\n As the semantics of these elements are as defined in X.509 and X.521,\n knowledge of X.509 and X.521 is necessary to make use of the LDAP\n schema defi 4523 algorithm algorithms attribute certificate certificates crl key pki revocation nested-reference unchanged"},{"id":"IETF RFC 3001","type":"specification","body":"IETF","designation":"RFC 3001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3001.txt","https://www.rfc-editor.org/rfc/rfc3001.pdf"],"folder":"IETF/RFC-3001","files":{"txt":{"path":"standards/IETF/RFC-3001/RFC-3001.txt","sha256":"c764df9e11829d420b41f950d3276a8564ec9adedb0a4ee8b8f02ce3b5e0f562"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Names (URN) namespace that\n contains Object Identifiers (OIDs).\n\n1. Introduction\n\n An Object Identifier is a series of digits delimited in some way.\n The rules roughly state that once an entity is assigned an Object\n Identifier (OID) it has sole discretion to further subdelegate off of\n that OID. Some examples of OIDs include:\n\n o 1.3.6.1 - the Internet OID\n o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs\n and such things\n o 1.3.6.1.2.1.27 - The Applications MIB\n o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot\n project to identify X.500 Object Classes. Mostly defined in RFC-\n 1274.\n\n This document specifies the \"oid\" URN namespace [1]. This namespace\n is for encoding an Object Identifier as specified in ASN.1 [2] as a\n URI.\n\n The namespace specification is for a formal namespace.\n\n2. Specification Template\n\n","scope_keywords":["3001","attribute","http","presentation","validation","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3061","folder":"IETF/RFC-3061","source":"IETF/RFC-3061/RFC-3061.txt","version":null}],"search_text":"IETF RFC 3001 This document describes a Uniform Resource Names (URN) namespace that\n contains Object Identifiers (OIDs).\n\n1. Introduction\n\n An Object Identifier is a series of digits delimited in some way.\n The rules roughly state that once an entity is assigned an Object\n Identifier (OID) it has sole discretion to further subdelegate off of\n that OID. Some examples of OIDs include:\n\n o 1.3.6.1 - the Internet OID\n o 1.3.6.1.4.1 - IANA-assigned company OIDs, used for private MIBs\n and such things\n o 1.3.6.1.2.1.27 - The Applications MIB\n o 0.9.2342.19200300.100.4 - Object ID's used in the directory pilot\n project to identify X.500 Object Classes. Mostly defined in RFC-\n 1274.\n\n This document specifies the \"oid\" URN namespace [1]. This namespace\n is for encoding an Object Identifier as specified in ASN.1 [2] as a\n URI.\n\n The namespace specification is for a formal namespace.\n\n2. Specification Template\n\n 3001 attribute http presentation validation verifiable nested-reference unchanged"},{"id":"IETF RFC 1781","type":"specification","body":"IETF","designation":"RFC 1781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1781.txt","https://www.rfc-editor.org/rfc/rfc1781.pdf"],"folder":"IETF/RFC-1781","files":{"txt":{"path":"standards/IETF/RFC-1781/RFC-1781.txt","sha256":"9552a4c3cb3d7d0416cfd4dbb2cacf43ea49296037f9b911e20e7562b5377a34"}},"tags":["nested-reference","unchanged"],"summary":"The OSI Directory has user friendly naming as a goal. A simple\n minded usage of the directory does not achieve this. Two aspects not\n achieved are:\n\n o A user oriented notation\n\n o Guessability\n\n This proposal sets out some conventions for representing names in a\n friendly manner, and shows how this can be used to achieve really\n friendly naming. This then leads to a specification of a standard\n format for representing names, and to procedures to resolve them.\n This leads to a specification which allows directory names to be\n communicated between humans. The format in this specification is\n identical to that defined in [5], and it is intended that these\n specifications are compatible.","scope_keywords":["1781","algorithm","attribute","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1779","folder":"IETF/RFC-1779","source":"IETF/RFC-1779/RFC-1779.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null}],"search_text":"IETF RFC 1781 The OSI Directory has user friendly naming as a goal. A simple\n minded usage of the directory does not achieve this. Two aspects not\n achieved are:\n\n o A user oriented notation\n\n o Guessability\n\n This proposal sets out some conventions for representing names in a\n friendly manner, and shows how this can be used to achieve really\n friendly naming. This then leads to a specification of a standard\n format for representing names, and to procedures to resolve them.\n This leads to a specification which allows directory names to be\n communicated between humans. The format in this specification is\n identical to that defined in [5], and it is intended that these\n specifications are compatible. 1781 algorithm attribute presentation nested-reference unchanged"},{"id":"IETF RFC 2253","type":"specification","body":"IETF","designation":"RFC 2253","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2253.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2253.txt","https://www.rfc-editor.org/rfc/rfc2253.pdf"],"folder":"IETF/RFC-2253","files":{"txt":{"path":"standards/IETF/RFC-2253/RFC-2253.txt","sha256":"45f3ab5d1b52ef29e5b26e6a98936c7fa5f3ec2b316e6059a592b745d1b42eea"}},"tags":["nested-reference","unchanged"],"summary":"The X.500 Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1\n in the X.500 Directory protocols. In the Lightweight Directory\n Access Protocol, a string representation of distinguished names is\n transferred. This specification defines the string format for\n representing names, which is designed to give a clean representation\n of commonly used distinguished names, while being able to represent\n any distinguished name.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\n1. Background\n\n This specification assumes familiarity with X.500 [1], and the\n concept of Distinguished Name. It is important to have a common\n format to be able to unambiguously represent a distinguis","scope_keywords":["2253","algorithm","attribute","authentication","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2247","folder":"IETF/RFC-2247","source":"IETF/RFC-2247/RFC-2247.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2589","folder":"IETF/RFC-2589","source":"IETF/RFC-2589/RFC-2589.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null}],"search_text":"IETF RFC 2253 The X.500 Directory uses distinguished names as the primary keys to\n entries in the directory. Distinguished Names are encoded in ASN.1\n in the X.500 Directory protocols. In the Lightweight Directory\n Access Protocol, a string representation of distinguished names is\n transferred. This specification defines the string format for\n representing names, which is designed to give a clean representation\n of commonly used distinguished names, while being able to represent\n any distinguished name.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\n1. Background\n\n This specification assumes familiarity with X.500 [1], and the\n concept of Distinguished Name. It is important to have a common\n format to be able to unambiguously represent a distinguis 2253 algorithm attribute authentication key keys presentation nested-reference unchanged"},{"id":"IETF RFC 2294","type":"specification","body":"IETF","designation":"RFC 2294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2294.txt","https://www.rfc-editor.org/rfc/rfc2294.pdf"],"folder":"IETF/RFC-2294","files":{"txt":{"path":"standards/IETF/RFC-2294/RFC-2294.txt","sha256":"1550e3b23bd0886be744e13f36c02a852c9f2b6a90fb419383b226849a2eccbb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 2294 Isode Ltd.\nObsoletes: 1836 March 1998\nCategory: Standards Track\n\n Representing the O/R Address hierarchy in the\n X.500 Directory Information Tree\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a representation of the O/R Address hierarchy\n in the Directory Information Tree [6, 1]. This is useful for a range\n of purposes, including:\n\n o Support for MHS Routing [4].\n\n o Support for X.400/RFC 822 address map","scope_keywords":["2294","attribute","attributes","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2294 Network Working Group S. Kille\nRequest for Comments: 2294 Isode Ltd.\nObsoletes: 1836 March 1998\nCategory: Standards Track\n\n Representing the O/R Address hierarchy in the\n X.500 Directory Information Tree\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a representation of the O/R Address hierarchy\n in the Directory Information Tree [6, 1]. This is useful for a range\n of purposes, including:\n\n o Support for MHS Routing [4].\n\n o Support for X.400/RFC 822 address map 2294 attribute attributes presentation nested-reference unchanged"},{"id":"IETF RFC 2872","type":"specification","body":"IETF","designation":"RFC 2872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2872.txt","https://www.rfc-editor.org/rfc/rfc2872.pdf"],"folder":"IETF/RFC-2872","files":{"txt":{"path":"standards/IETF/RFC-2872/RFC-2872.txt","sha256":"f2700295a8ebb3543c835117ec622489d7f5904daedaffb4840cbf48f8feea75"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Bernet\nRequest for Comments: 2872 R. Pabbati\nCategory: Standards Track Microsoft\n June 2000\n\n Application and Sub Application Identity Policy Element for\n Use with RSVP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\nAbstract\n\n RSVP [RFC 220","scope_keywords":["2872","attribute","attributes","authentication","credential","http","identification","key","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2872 Network Working Group Y. Bernet\nRequest for Comments: 2872 R. Pabbati\nCategory: Standards Track Microsoft\n June 2000\n\n Application and Sub Application Identity Policy Element for\n Use with RSVP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\nAbstract\n\n RSVP [RFC 220 2872 attribute attributes authentication credential http identification key policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 4520","type":"specification","body":"IETF","designation":"RFC 4520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4520.txt","https://www.rfc-editor.org/rfc/rfc4520.pdf"],"folder":"IETF/RFC-4520","files":{"txt":{"path":"standards/IETF/RFC-4520/RFC-4520.txt","sha256":"32408c99eba9ac5728ebfbaa208ee2d9f737a47064bc1f6f51d79466b0900b57"}},"tags":["nested-reference","unchanged"],"summary":"This document provides procedures for registering extensible elements\n of the Lightweight Directory Access Protocol (LDAP). The document\n also provides guidelines to the Internet Assigned Numbers Authority\n (IANA) describing conditions under which new values can be assigned.\n\n1. Introduction\n\n The Lightweight Directory Access Protocol [RFC4510] (LDAP) is an\n extensible protocol. LDAP supports:\n\n - the addition of new operations,\n - the extension of existing operations, and\n - the extensible schema.\n\n This document details procedures for registering values used to\n unambiguously identify extensible elements of the protocol, including\n the following:\n\n - LDAP message types\n - LDAP extended operations and controls\n - LDAP result codes\n - LDAP authentication methods\n - LDAP attribute description options\n - Object Identifier descriptors\n\nZeilenga Best Current Practice [Page 1]\n\f\nRFC 4520 IANA","scope_keywords":["4520","attribute","attributes","authentication","http","key","keys","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4520 This document provides procedures for registering extensible elements\n of the Lightweight Directory Access Protocol (LDAP). The document\n also provides guidelines to the Internet Assigned Numbers Authority\n (IANA) describing conditions under which new values can be assigned.\n\n1. Introduction\n\n The Lightweight Directory Access Protocol [RFC4510] (LDAP) is an\n extensible protocol. LDAP supports:\n\n - the addition of new operations,\n - the extension of existing operations, and\n - the extensible schema.\n\n This document details procedures for registering values used to\n unambiguously identify extensible elements of the protocol, including\n the following:\n\n - LDAP message types\n - LDAP extended operations and controls\n - LDAP result codes\n - LDAP authentication methods\n - LDAP attribute description options\n - Object Identifier descriptors\n\nZeilenga Best Current Practice [Page 1]\n\f\nRFC 4520 IANA 4520 attribute attributes authentication http key keys policy registered nested-reference unchanged"},{"id":"IETF RFC 2769","type":"specification","body":"IETF","designation":"RFC 2769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2769.txt","https://www.rfc-editor.org/rfc/rfc2769.pdf"],"folder":"IETF/RFC-2769","files":{"txt":{"path":"standards/IETF/RFC-2769/RFC-2769.txt","sha256":"c9930ff03756d782f17659aae6505028047463eeb2b54a19bb52e4398dd50d7e"}},"tags":["nested-reference","unchanged"],"summary":"The RIPE database specifications and RPSL define languages used as\n the basis for representing information in a routing policy system. A\n repository for routing policy system information is known as a\n routing registry. A routing registry provides a means of exchanging\n information needed to address many issues of importance to the\n operation of the Internet. The implementation and deployment of a\n routing policy system must maintain some degree of integrity to be of\n any use. The Routing Policy System Security RFC [3] addresses the\n need to assure integrity of the data by proposing an authentication\n and authorization model. This document addresses the need to\n distribute data over multiple repositories and delegate authority for\n data subsets to other repositories without compromising the\n authorization model established in Routing Policy System Security\n RFC.\n\nVillamizar, et al. Stand","scope_keywords":["2769","attribute","authentication","authorization","key","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null}],"search_text":"IETF RFC 2769 The RIPE database specifications and RPSL define languages used as\n the basis for representing information in a routing policy system. A\n repository for routing policy system information is known as a\n routing registry. A routing registry provides a means of exchanging\n information needed to address many issues of importance to the\n operation of the Internet. The implementation and deployment of a\n routing policy system must maintain some degree of integrity to be of\n any use. The Routing Policy System Security RFC [3] addresses the\n need to assure integrity of the data by proposing an authentication\n and authorization model. This document addresses the need to\n distribute data over multiple repositories and delegate authority for\n data subsets to other repositories without compromising the\n authorization model established in Routing Policy System Security\n RFC.\n\nVillamizar, et al. Stand 2769 attribute authentication authorization key policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 3013","type":"specification","body":"IETF","designation":"RFC 3013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3013.txt","https://www.rfc-editor.org/rfc/rfc3013.pdf"],"folder":"IETF/RFC-3013","files":{"txt":{"path":"standards/IETF/RFC-3013/RFC-3013.txt","sha256":"0db2a31b759c4a25a1859f3eab5dc9a2a7369e0d11f2a2daf0a0dce59508d0e2"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to express what the engineering\n community as represented by the IETF expects of Internet Service\n Providers (ISPs) with respect to security.\n\n It is not the intent of this document to define a set of requirements\n that would be appropriate for all ISPs, but rather to raise awareness\n among ISPs of the community's expectations, and to provide the\n community with a framework for discussion of security expectations\n with current and prospective service providers.\n\nKillalea Best Current Practice [Page 1]\n\f\nRFC 3013 Recommended ISP Security November 2000","scope_keywords":["3013","http","key","management","policies","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null}],"search_text":"IETF RFC 3013 The purpose of this document is to express what the engineering\n community as represented by the IETF expects of Internet Service\n Providers (ISPs) with respect to security.\n\n It is not the intent of this document to define a set of requirements\n that would be appropriate for all ISPs, but rather to raise awareness\n among ISPs of the community's expectations, and to provide the\n community with a framework for discussion of security expectations\n with current and prospective service providers.\n\nKillalea Best Current Practice [Page 1]\n\f\nRFC 3013 Recommended ISP Security November 2000 3013 http key management policies policy risk nested-reference unchanged"},{"id":"IETF RFC 2339","type":"specification","body":"IETF","designation":"RFC 2339","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2339.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2339.txt","https://www.rfc-editor.org/rfc/rfc2339.pdf"],"folder":"IETF/RFC-2339","files":{"txt":{"path":"standards/IETF/RFC-2339/RFC-2339.txt","sha256":"2d5dd245deae6c588f94b38477f3ea413ab4b0ff63c2a60d7a416c932b4bee90"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group The Internet Society\nRequest for Comments: 2339 Sun Microsystems\nCategory: Informational May 1998\n\n An Agreement Between the Internet Society,\n the IETF, and Sun Microsystems, Inc.\n in the matter of NFS V.4 Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This Request for Comments records an agreement between Sun\n Microsystems, Inc. and the Internet Society to permit the flow of\n Sun's Network File System specifications into the Internet Standards\n process conducted by the Internet Engineering Task Force.\n\nNote:\n\n This RFC is NOT a standard. It is an official public record of an\n agreement between Sun Microsystems and the Internet Soci","scope_keywords":["2339","license","presentation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 2339 Network Working Group The Internet Society\nRequest for Comments: 2339 Sun Microsystems\nCategory: Informational May 1998\n\n An Agreement Between the Internet Society,\n the IETF, and Sun Microsystems, Inc.\n in the matter of NFS V.4 Protocols\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This Request for Comments records an agreement between Sun\n Microsystems, Inc. and the Internet Society to permit the flow of\n Sun's Network File System specifications into the Internet Standards\n process conducted by the Internet Engineering Task Force.\n\nNote:\n\n This RFC is NOT a standard. It is an official public record of an\n agreement between Sun Microsystems and the Internet Soci 2339 license presentation signature subject nested-reference unchanged"},{"id":"IETF RFC 3668","type":"specification","body":"IETF","designation":"RFC 3668","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3668.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3668.txt","https://www.rfc-editor.org/rfc/rfc3668.pdf"],"folder":"IETF/RFC-3668","files":{"txt":{"path":"standards/IETF/RFC-3668/RFC-3668.txt","sha256":"97184ee629a6d5c8ceac994009b5cec892a1197a9288819342ca2e31732874fb"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information about any IPR constraints on a technical proposal as\n possible. The policies are also intended to benefit the Internet\n community and the public at large, while respecting the legitimate\n rights of IPR holders. This memo details the IETF policies\n concerning IPR related to technology worked on within the IETF. It\n also describes the objectives that the policies are designed to meet.\n This memo updates RFC 2026 and, with RFC 3667, replaces Section 10 of\n RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC\n 2028, for all purposes, including reference [2] in RFC 2418.","scope_keywords":["3668","holder","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3667","folder":"IETF/RFC-3667","source":"IETF/RFC-3667/RFC-3667.txt","version":null},{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3933","folder":"IETF/RFC-3933","source":"IETF/RFC-3933/RFC-3933.txt","version":null}],"search_text":"IETF RFC 3668 The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information about any IPR constraints on a technical proposal as\n possible. The policies are also intended to benefit the Internet\n community and the public at large, while respecting the legitimate\n rights of IPR holders. This memo details the IETF policies\n concerning IPR related to technology worked on within the IETF. It\n also describes the objectives that the policies are designed to meet.\n This memo updates RFC 2026 and, with RFC 3667, replaces Section 10 of\n RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC\n 2028, for all purposes, including reference [2] in RFC 2418. 3668 holder policies policy nested-reference unchanged"},{"id":"IETF RFC 3979","type":"specification","body":"IETF","designation":"RFC 3979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3979.txt","https://www.rfc-editor.org/rfc/rfc3979.pdf"],"folder":"IETF/RFC-3979","files":{"txt":{"path":"standards/IETF/RFC-3979/RFC-3979.txt","sha256":"9ed07ffeab7a9f23ed689fccf983c0d8ffa47451aa145e677b841120789cea08"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information about any IPR constraints on a technical proposal as\n possible. The policies are also intended to benefit the Internet\n community and the public at large, while respecting the legitimate\n rights of IPR holders. This memo details the IETF policies\n concerning IPR related to technology worked on within the IETF. It\n also describes the objectives that the policies are designed to meet.\n This memo updates RFC 2026 and, with RFC 3978, replaces Section 10 of\n RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC\n 2028, for all purposes, including reference [2] in RFC 2418.","scope_keywords":["3979","holder","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3978","folder":"IETF/RFC-3978","source":"IETF/RFC-3978/RFC-3978.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4226","folder":"IETF/RFC-4226","source":"IETF/RFC-4226/RFC-4226.txt","version":null},{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4879","folder":"IETF/RFC-4879","source":"IETF/RFC-4879/RFC-4879.txt","version":null},{"body":"IETF","designation":"RFC 4986","folder":"IETF/RFC-4986","source":"IETF/RFC-4986/RFC-4986.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 3979 The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information about any IPR constraints on a technical proposal as\n possible. The policies are also intended to benefit the Internet\n community and the public at large, while respecting the legitimate\n rights of IPR holders. This memo details the IETF policies\n concerning IPR related to technology worked on within the IETF. It\n also describes the objectives that the policies are designed to meet.\n This memo updates RFC 2026 and, with RFC 3978, replaces Section 10 of\n RFC 2026. This memo also updates paragraph 4 of Section 3.2 of RFC\n 2028, for all purposes, including reference [2] in RFC 2418. 3979 holder policies policy nested-reference unchanged"},{"id":"IETF RFC 8179","type":"specification","body":"IETF","designation":"RFC 8179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8179.txt","https://www.rfc-editor.org/rfc/rfc8179.pdf"],"folder":"IETF/RFC-8179","files":{"txt":{"path":"standards/IETF/RFC-8179/RFC-8179.txt","sha256":"d752882f088e71efbcc0519e364752b15cad6da16f8c6e77ea01a3363d3eccff"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information as possible about any IPR constraints on a technical\n proposal as early as possible in the development process. The\n policies are intended to benefit the Internet community and the\n public at large, while respecting the legitimate rights of IPR\n holders. This document sets out the IETF policies concerning IPR\n related to technology worked on within the IETF. It also describes\n the objectives that the policies are designed to meet. This document\n updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026.\n This document also obsoletes RFCs 3979 and 4879.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product ","scope_keywords":["8179","holder","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null}],"search_text":"IETF RFC 8179 The IETF policies about Intellectual Property Rights (IPR), such as\n patent rights, relative to technologies developed in the IETF are\n designed to ensure that IETF working groups and participants have as\n much information as possible about any IPR constraints on a technical\n proposal as early as possible in the development process. The\n policies are intended to benefit the Internet community and the\n public at large, while respecting the legitimate rights of IPR\n holders. This document sets out the IETF policies concerning IPR\n related to technology worked on within the IETF. It also describes\n the objectives that the policies are designed to meet. This document\n updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026.\n This document also obsoletes RFCs 3979 and 4879.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product  8179 holder http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1791","type":"specification","body":"IETF","designation":"RFC 1791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1791.txt","https://www.rfc-editor.org/rfc/rfc1791.pdf"],"folder":"IETF/RFC-1791","files":{"txt":{"path":"standards/IETF/RFC-1791/RFC-1791.txt","sha256":"4cdb1f0c3a3d759f218f3ac0ee1001a45db46b84191c6654d3b6c21372a971aa"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Sung\nRequest for Comments: 1791 Novell, Inc.\nCategory: Experimental April 1995\n\n TCP And UDP Over IPX Networks With Fixed Path MTU\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Internet Engineering Steering Group comment from the Area Director\n for Transport Services: Please note well that this memo is an\n individual product of the author. Implementation experience,\n particularly on the effectiveness of the protocols in dual-stack\n environments, is needed.\n\n1. Introduction\n\n Most of network applications run on some sort of transports. And, if\n one is to let such applications to run over a foreign network\n protocol, the simplest way would be to ","scope_keywords":["1791","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 1791 Network Working Group T. Sung\nRequest for Comments: 1791 Novell, Inc.\nCategory: Experimental April 1995\n\n TCP And UDP Over IPX Networks With Fixed Path MTU\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Internet Engineering Steering Group comment from the Area Director\n for Transport Services: Please note well that this memo is an\n individual product of the author. Implementation experience,\n particularly on the effectiveness of the protocols in dual-stack\n environments, is needed.\n\n1. Introduction\n\n Most of network applications run on some sort of transports. And, if\n one is to let such applications to run over a foreign network\n protocol, the simplest way would be to  1791 http path nested-reference unchanged"},{"id":"IETF RFC 1792","type":"specification","body":"IETF","designation":"RFC 1792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1792.txt","https://www.rfc-editor.org/rfc/rfc1792.pdf"],"folder":"IETF/RFC-1792","files":{"txt":{"path":"standards/IETF/RFC-1792/RFC-1792.txt","sha256":"8a44154c1af341179e00b77478e54d10b0287e5e24345d04e7e28182cbd694d1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Sung\nRequest for Comments: 1792 Novell, Inc.\nCategory: Experimental April 1995\n\n TCP/IPX Connection Mib Specification\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Internet Engineering Steering Group comment from the Area Director\n for Transport Services: Please note well that this memo is an\n individual product of the author. Implementation experience,\n particularly on the effectiveness of the protocols in dual-stack\n environments, is needed.\n\n1. Introduction\n\n Traditionally, TCP and UDP runs over IP. STD 17, RFC 1213 defines\n TCP connection MIB object and UDP listener object assuming just that.\n For TCP and UDP running over IPX, tcpConnTable ","scope_keywords":["1792","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 1792 Network Working Group T. Sung\nRequest for Comments: 1792 Novell, Inc.\nCategory: Experimental April 1995\n\n TCP/IPX Connection Mib Specification\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIESG Note:\n\n Internet Engineering Steering Group comment from the Area Director\n for Transport Services: Please note well that this memo is an\n individual product of the author. Implementation experience,\n particularly on the effectiveness of the protocols in dual-stack\n environments, is needed.\n\n1. Introduction\n\n Traditionally, TCP and UDP runs over IP. STD 17, RFC 1213 defines\n TCP connection MIB object and UDP listener object assuming just that.\n For TCP and UDP running over IPX, tcpConnTable  1792 management nested-reference unchanged"},{"id":"IETF RFC 3623","type":"specification","body":"IETF","designation":"RFC 3623","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3623.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3623.txt","https://www.rfc-editor.org/rfc/rfc3623.pdf"],"folder":"IETF/RFC-3623","files":{"txt":{"path":"standards/IETF/RFC-3623/RFC-3623.txt","sha256":"aad33e21be6a50b967241c75e8aaa3416545c7644e6ed1d9879dffcaa09a4d5e"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents an enhancement to the OSPF routing protocol,\n whereby an OSPF router can stay on the forwarding path even as its\n OSPF software is restarted. This is called \"graceful restart\" or\n \"non-stop forwarding\". A restarting router may not be capable of\n adjusting its forwarding in a timely manner when the network topology\n changes. In order to avoid the possible resulting routing loops, the\n procedure in this memo automatically reverts to a normal OSPF restart\n when such a topology change is detected, or when one or more of the\n restarting router's neighbors do not support the enhancements in this\n memo. Proper network operation during a graceful restart makes\n assumptions upon the operating environment of the restarting router;\n these assumptions are also documented.\n\nMoy, et al. Standards Track [Page 1]\n\f\nRFC 3623 Graceful OSPF Restart November 2003","scope_keywords":["3623","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4811","folder":"IETF/RFC-4811","source":"IETF/RFC-4811/RFC-4811.txt","version":null},{"body":"IETF","designation":"RFC 4812","folder":"IETF/RFC-4812","source":"IETF/RFC-4812/RFC-4812.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 3623 This memo documents an enhancement to the OSPF routing protocol,\n whereby an OSPF router can stay on the forwarding path even as its\n OSPF software is restarted. This is called \"graceful restart\" or\n \"non-stop forwarding\". A restarting router may not be capable of\n adjusting its forwarding in a timely manner when the network topology\n changes. In order to avoid the possible resulting routing loops, the\n procedure in this memo automatically reverts to a normal OSPF restart\n when such a topology change is detected, or when one or more of the\n restarting router's neighbors do not support the enhancements in this\n memo. Proper network operation during a graceful restart makes\n assumptions upon the operating environment of the restarting router;\n these assumptions are also documented.\n\nMoy, et al. Standards Track [Page 1]\n\f\nRFC 3623 Graceful OSPF Restart November 2003 3623 management path subject nested-reference unchanged"},{"id":"IETF RFC 3963","type":"specification","body":"IETF","designation":"RFC 3963","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3963.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3963.txt","https://www.rfc-editor.org/rfc/rfc3963.pdf"],"folder":"IETF/RFC-3963","files":{"txt":{"path":"standards/IETF/RFC-3963/RFC-3963.txt","sha256":"ea1a1eaafd200c6afe68fcb33bccec0eb3f796e9e85bcb575893c57707257d0f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Network Mobility (NEMO) Basic Support\n protocol that enables Mobile Networks to attach to different points\n in the Internet. The protocol is an extension of Mobile IPv6 and\n allows session continuity for every node in the Mobile Network as the\n network moves. It also allows every node in the Mobile Network to be\n reachable while moving around. The Mobile Router, which connects the\n network to the Internet, runs the NEMO Basic Support protocol with\n its Home Agent. The protocol is designed so that network mobility is\n transparent to the nodes inside the Mobile Network.\n\nDevarapalli, et al. Standards Track [Page 1]\n\f\nRFC 3963 NEMO Basic Support Protocol January 2005","scope_keywords":["3963","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 5094","folder":"IETF/RFC-5094","source":"IETF/RFC-5094/RFC-5094.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null}],"search_text":"IETF RFC 3963 This document describes the Network Mobility (NEMO) Basic Support\n protocol that enables Mobile Networks to attach to different points\n in the Internet. The protocol is an extension of Mobile IPv6 and\n allows session continuity for every node in the Mobile Network as the\n network moves. It also allows every node in the Mobile Network to be\n reachable while moving around. The Mobile Router, which connects the\n network to the Internet, runs the NEMO Basic Support protocol with\n its Home Agent. The protocol is designed so that network mobility is\n transparent to the nodes inside the Mobile Network.\n\nDevarapalli, et al. Standards Track [Page 1]\n\f\nRFC 3963 NEMO Basic Support Protocol January 2005 3963 key nested-reference unchanged"},{"id":"IETF RFC 4136","type":"specification","body":"IETF","designation":"RFC 4136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4136.txt","https://www.rfc-editor.org/rfc/rfc4136.pdf"],"folder":"IETF/RFC-4136","files":{"txt":{"path":"standards/IETF/RFC-4136/RFC-4136.txt","sha256":"50344ae27cffa28f42cb30f6f7766fb3090c18805b81697887cae40bfc10d746"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Pillay-Esnault\nRequest for Comments: 4136 Cisco Systems\nCategory: Informational July 2005\n\n OSPF Refresh and Flooding Reduction in Stable Topologies\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes an extension to the OSPF protocol to reduce\n periodic flooding of Link State Advertisements (LSAs) in stable\n topologies.\n\n Current OSPF behavior requires that all LSAs, except DoNotAge LSAs,\n to be refreshed every 30 minutes. This document proposes to\n generalize the use of DoNotAge LSAs in order to reduce protocol\n traffic in stable topologies.\n\n1. Introduction\n\n The explosive growth of IP-based networks has placed focus on the\n scalability of","scope_keywords":["4136","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4222","folder":"IETF/RFC-4222","source":"IETF/RFC-4222/RFC-4222.txt","version":null}],"search_text":"IETF RFC 4136 Network Working Group P. Pillay-Esnault\nRequest for Comments: 4136 Cisco Systems\nCategory: Informational July 2005\n\n OSPF Refresh and Flooding Reduction in Stable Topologies\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes an extension to the OSPF protocol to reduce\n periodic flooding of Link State Advertisements (LSAs) in stable\n topologies.\n\n Current OSPF behavior requires that all LSAs, except DoNotAge LSAs,\n to be refreshed every 30 minutes. This document proposes to\n generalize the use of DoNotAge LSAs in order to reduce protocol\n traffic in stable topologies.\n\n1. Introduction\n\n The explosive growth of IP-based networks has placed focus on the\n scalability of 4136 license subject nested-reference unchanged"},{"id":"IETF RFC 6724","type":"specification","body":"IETF","designation":"RFC 6724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6724.txt","https://www.rfc-editor.org/rfc/rfc6724.pdf"],"folder":"IETF/RFC-6724","files":{"txt":{"path":"standards/IETF/RFC-6724/RFC-6724.txt","sha256":"deab574626b2bc886748401617f29a33cf97927f3690dba2fb183d31315741f6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes two algorithms, one for source address\n selection and one for destination address selection. The algorithms\n specify default behavior for all Internet Protocol version 6 (IPv6)\n implementations. They do not override choices made by applications\n or upper-layer protocols, nor do they preclude the development of\n more advanced mechanisms for address selection. The two algorithms\n share a common context, including an optional mechanism for allowing\n administrators to provide policy that can override the default\n behavior. In dual-stack implementations, the destination address\n selection algorithm can consider both IPv4 and IPv6 addresses --\n depending on the available source addresses, the algorithm might\n prefer IPv6 addresses over IPv4 addresses, or vice versa.\n\n Default address selection as defined in this specification applies to\n all IPv6 nodes, including both h","scope_keywords":["6724","algorithm","algorithms","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8421","folder":"IETF/RFC-8421","source":"IETF/RFC-8421/RFC-8421.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6724 This document describes two algorithms, one for source address\n selection and one for destination address selection. The algorithms\n specify default behavior for all Internet Protocol version 6 (IPv6)\n implementations. They do not override choices made by applications\n or upper-layer protocols, nor do they preclude the development of\n more advanced mechanisms for address selection. The two algorithms\n share a common context, including an optional mechanism for allowing\n administrators to provide policy that can override the default\n behavior. In dual-stack implementations, the destination address\n selection algorithm can consider both IPv4 and IPv6 addresses --\n depending on the available source addresses, the algorithm might\n prefer IPv6 addresses over IPv4 addresses, or vice versa.\n\n Default address selection as defined in this specification applies to\n all IPv6 nodes, including both h 6724 algorithm algorithms http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 1796","type":"specification","body":"IETF","designation":"RFC 1796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1796.txt","https://www.rfc-editor.org/rfc/rfc1796.pdf"],"folder":"IETF/RFC-1796","files":{"txt":{"path":"standards/IETF/RFC-1796/RFC-1796.txt","sha256":"3b8a2c8ea924a57f1144820ff6607d07db92e700b433a28b06abe8386b7dfd75"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Huitema\nRequest for Comments: 1796 INRIA\nCategory: Informational J. Postel\n ISI\n S. Crocker\n CyberCash\n April 1995\n\n Not All RFCs are Standards\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document discusses the relationship of the Request for Comments\n (RFCs) notes to Internet Standards.\n\nNot All RFCs Are Standards\n\n The \"Request for Comments\" (RFC) document series is the official\n publication channel for Internet standards documents and other\n publications of the IESG, IAB, and Internet community. From time to\n time, and about every six months in the last few years, someone\n questions the rationality of publishing both Internet standards and\n informational documents as RFCs. The argument is generally that t","scope_keywords":["1796"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2026","folder":"IETF/RFC-2026","source":"IETF/RFC-2026/RFC-2026.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null}],"search_text":"IETF RFC 1796 Network Working Group C. Huitema\nRequest for Comments: 1796 INRIA\nCategory: Informational J. Postel\n ISI\n S. Crocker\n CyberCash\n April 1995\n\n Not All RFCs are Standards\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document discusses the relationship of the Request for Comments\n (RFCs) notes to Internet Standards.\n\nNot All RFCs Are Standards\n\n The \"Request for Comments\" (RFC) document series is the official\n publication channel for Internet standards documents and other\n publications of the IESG, IAB, and Internet community. From time to\n time, and about every six months in the last few years, someone\n questions the rationality of publishing both Internet standards and\n informational documents as RFCs. The argument is generally that t 1796 nested-reference unchanged"},{"id":"IETF RFC 1797","type":"specification","body":"IETF","designation":"RFC 1797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1797.txt","https://www.rfc-editor.org/rfc/rfc1797.pdf"],"folder":"IETF/RFC-1797","files":{"txt":{"path":"standards/IETF/RFC-1797/RFC-1797.txt","sha256":"9822e8baefbbefb861edeeefa12459f29a0b79b095696c6117dbc57cf57799a1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group IANA\nRequest for Comments: 1797 ISI\nCategory: Experimental April 1995\n\n Class A Subnet Experiment\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nDiscussion\n\n There appears to be some interest in experimenting with subnetting\n the class A addresses.\n\n There is some evidence that not all the routing software in use will\n deal correctly with subnetted class A addresses. It also appears\n that actual use of subnetted class A addresses may be necessary in\n the not too distant future. It is suggested that conducting an\n experiment now to identify and fix any software that does not\n properly handle subnetted class A addresses would be useful and\n important.\n\n To furthe","scope_keywords":["1797","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1879","folder":"IETF/RFC-1879","source":"IETF/RFC-1879/RFC-1879.txt","version":null},{"body":"IETF","designation":"RFC 2770","folder":"IETF/RFC-2770","source":"IETF/RFC-2770/RFC-2770.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1797 Network Working Group IANA\nRequest for Comments: 1797 ISI\nCategory: Experimental April 1995\n\n Class A Subnet Experiment\n\nStatus of this Memo\n\n This document defines an Experimental Protocol for the Internet\n community. This does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nDiscussion\n\n There appears to be some interest in experimenting with subnetting\n the class A addresses.\n\n There is some evidence that not all the routing software in use will\n deal correctly with subnetted class A addresses. It also appears\n that actual use of subnetted class A addresses may be necessary in\n the not too distant future. It is suggested that conducting an\n experiment now to identify and fix any software that does not\n properly handle subnetted class A addresses would be useful and\n important.\n\n To furthe 1797 registered nested-reference unchanged"},{"id":"IETF RFC 2770","type":"specification","body":"IETF","designation":"RFC 2770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2770.txt","https://www.rfc-editor.org/rfc/rfc2770.pdf"],"folder":"IETF/RFC-2770","files":{"txt":{"path":"standards/IETF/RFC-2770/RFC-2770.txt","sha256":"3697ae08e2f52b29aab2f3d0363bf947d474a51676792b9ba9e2a072122ce05d"}},"tags":["nested-reference","unchanged"],"summary":"This describes an experimental policy for use of the class D address\n space using 233/8 as the experimental statically assigned subset of\n the class D address space. This new experimental allocation is in\n addition to those described on [IANA] (e.g. [RFC2365]).\n\n This memo is a product of the Multicast Deployment Working Group\n (MBONED) in the Operations and Management Area of the Internet\n Engineering Task Force. Submit comments to <mboned@ns.uoregon.edu> or\n the authors.\n\n1. Problem Statement\n\n Multicast addresses have traditionally been allocated by a dynamic\n mechanism such as SDR [SAP]. However, many current multicast\n deployment models are not amenable to dynamic allocation. For\n example, many content aggregators require group addresses which are\n fixed on a time scale which is not amenable to allocation by a\n mechanism such as described in [SAP]. Perhaps more seriously, since\n the","scope_keywords":["2770","management","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2908","folder":"IETF/RFC-2908","source":"IETF/RFC-2908/RFC-2908.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null}],"search_text":"IETF RFC 2770 This describes an experimental policy for use of the class D address\n space using 233/8 as the experimental statically assigned subset of\n the class D address space. This new experimental allocation is in\n addition to those described on [IANA] (e.g. [RFC2365]).\n\n This memo is a product of the Multicast Deployment Working Group\n (MBONED) in the Operations and Management Area of the Internet\n Engineering Task Force. Submit comments to <mboned@ns.uoregon.edu> or\n the authors.\n\n1. Problem Statement\n\n Multicast addresses have traditionally been allocated by a dynamic\n mechanism such as SDR [SAP]. However, many current multicast\n deployment models are not amenable to dynamic allocation. For\n example, many content aggregators require group addresses which are\n fixed on a time scale which is not amenable to allocation by a\n mechanism such as described in [SAP]. Perhaps more seriously, since\n the 2770 management policy registered nested-reference unchanged"},{"id":"IETF RFC 3180","type":"specification","body":"IETF","designation":"RFC 3180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3180.txt","https://www.rfc-editor.org/rfc/rfc3180.pdf"],"folder":"IETF/RFC-3180","files":{"txt":{"path":"standards/IETF/RFC-3180/RFC-3180.txt","sha256":"c1636cb21e6f23ede08b33dde8eb9a8b46e9f99b0efd305096d28b2cd4369364"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the policy for the use of 233/8 for statically\n assigned multicast addresses.\n\n1. Introduction\n\n It is envisioned that the primary use of this space will be many-to-\n many applications. This allocation is in addition to those described\n on [IANA] (e.g., [RFC2365]). The IANA has allocated 223/8 as per RFC\n 2770 [RFC2770]. This document obsoletes RFC 2770.\n\n2. Problem Statement\n\n Multicast addresses have traditionally been allocated by a dynamic\n mechanism such as SDR [RFC2974]. However, many current multicast\n deployment models are not amenable to dynamic allocation. For\n example, many content aggregators require group addresses that are\n fixed on a time scale that is not amenable to allocation by a\n mechanism such as described in [RFC2974]. Perhaps more seriously,\n since there is not general consensus by providers, content\n aggregators, or application writers as to ","scope_keywords":["3180","http","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null}],"search_text":"IETF RFC 3180 This document defines the policy for the use of 233/8 for statically\n assigned multicast addresses.\n\n1. Introduction\n\n It is envisioned that the primary use of this space will be many-to-\n many applications. This allocation is in addition to those described\n on [IANA] (e.g., [RFC2365]). The IANA has allocated 223/8 as per RFC\n 2770 [RFC2770]. This document obsoletes RFC 2770.\n\n2. Problem Statement\n\n Multicast addresses have traditionally been allocated by a dynamic\n mechanism such as SDR [RFC2974]. However, many current multicast\n deployment models are not amenable to dynamic allocation. For\n example, many content aggregators require group addresses that are\n fixed on a time scale that is not amenable to allocation by a\n mechanism such as described in [RFC2974]. Perhaps more seriously,\n since there is not general consensus by providers, content\n aggregators, or application writers as to  3180 http policy registered nested-reference unchanged"},{"id":"IETF RFC 1837","type":"specification","body":"IETF","designation":"RFC 1837","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1837.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1837.txt","https://www.rfc-editor.org/rfc/rfc1837.pdf"],"folder":"IETF/RFC-1837","files":{"txt":{"path":"standards/IETF/RFC-1837/RFC-1837.txt","sha256":"9aaa70091b76ad95226d2c161279abcfd404705b535e852f9e5836bd4ebde2f5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 1837 ISODE Consortium\nCategory: Experimental August 1995\n\n Representing Tables and Subtrees in the X.500 Directory\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines techniques for representing two types of\n information mapping in the OSI Directory [1].\n\n 1. Mapping from a key to a value (or set of values), as might be\n done in a table lookup.\n\n 2. Mapping from a distinguished name to an associated value (or\n values), where the values are not defined by the owner of the\n entry. This is achieved by use of a directory subtree.\n\n These techniques were developed for supporting MHS use of Directory\n [2], b","scope_keywords":["1837","attribute","attributes","key","keys","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null}],"search_text":"IETF RFC 1837 Network Working Group S. Kille\nRequest for Comments: 1837 ISODE Consortium\nCategory: Experimental August 1995\n\n Representing Tables and Subtrees in the X.500 Directory\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n This document defines techniques for representing two types of\n information mapping in the OSI Directory [1].\n\n 1. Mapping from a key to a value (or set of values), as might be\n done in a table lookup.\n\n 2. Mapping from a distinguished name to an associated value (or\n values), where the values are not defined by the owner of the\n entry. This is achieved by use of a directory subtree.\n\n These techniques were developed for supporting MHS use of Directory\n [2], b 1837 attribute attributes key keys qualified nested-reference unchanged"},{"id":"IETF RFC 2293","type":"specification","body":"IETF","designation":"RFC 2293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2293.txt","https://www.rfc-editor.org/rfc/rfc2293.pdf"],"folder":"IETF/RFC-2293","files":{"txt":{"path":"standards/IETF/RFC-2293/RFC-2293.txt","sha256":"154a843cf3cd66dccc41e470234daefa7cd45dd3e40cbf06a267a7ae8f900a4c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kille\nRequest for Comments: 2293 Isode Ltd.\nObsoletes: 1837 March 1998\nCategory: Standards Track\n\n Representing Tables and Subtrees in the X.500 Directory\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines techniques for representing two types of\n information mapping in the OSI Directory [1].\n\n 1. Mapping from a key to a value (or set of values), as might\n be done in a table lookup.\n\n 2. Mapping from a distinguished name to an associated\n va","scope_keywords":["2293","attribute","attributes","key","keys","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2293 Network Working Group S. Kille\nRequest for Comments: 2293 Isode Ltd.\nObsoletes: 1837 March 1998\nCategory: Standards Track\n\n Representing Tables and Subtrees in the X.500 Directory\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines techniques for representing two types of\n information mapping in the OSI Directory [1].\n\n 1. Mapping from a key to a value (or set of values), as might\n be done in a table lookup.\n\n 2. Mapping from a distinguished name to an associated\n va 2293 attribute attributes key keys qualified nested-reference unchanged"},{"id":"IETF RFC 2388","type":"specification","body":"IETF","designation":"RFC 2388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2388.txt","https://www.rfc-editor.org/rfc/rfc2388.pdf"],"folder":"IETF/RFC-2388","files":{"txt":{"path":"standards/IETF/RFC-2388/RFC-2388.txt","sha256":"66a62dc9a3c4cf6695597517b300fd118d13cf8252e6f8401bfde7b75c4e1446"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an Internet Media Type, multipart/form-\n data, which can be used by a wide variety of applications and\n transported by a wide variety of protocols as a way of returning a\n set of values as the result of a user filling out a form.\n\n2. Introduction\n\n In many applications, it is possible for a user to be presented with\n a form. The user will fill out the form, including information that\n is typed, generated by user input, or included from files that the\n user has selected. When the form is filled out, the data from the\n form is sent from the user to the receiving application.\n\n The definition of MultiPart/Form-Data is derived from one of those\n applications, originally set out in [RFC1867] and subsequently\n incorporated into [HTML40], where forms are expressed in HTML, and in\n which the form values are sent via HTTP or electronic mail. This\n representation is wide","scope_keywords":["2388","attribute","attributes","encryption","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2854","folder":"IETF/RFC-2854","source":"IETF/RFC-2854/RFC-2854.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null}],"search_text":"IETF RFC 2388 This specification defines an Internet Media Type, multipart/form-\n data, which can be used by a wide variety of applications and\n transported by a wide variety of protocols as a way of returning a\n set of values as the result of a user filling out a form.\n\n2. Introduction\n\n In many applications, it is possible for a user to be presented with\n a form. The user will fill out the form, including information that\n is typed, generated by user input, or included from files that the\n user has selected. When the form is filled out, the data from the\n form is sent from the user to the receiving application.\n\n The definition of MultiPart/Form-Data is derived from one of those\n applications, originally set out in [RFC1867] and subsequently\n incorporated into [HTML40], where forms are expressed in HTML, and in\n which the form values are sent via HTTP or electronic mail. This\n representation is wide 2388 attribute attributes encryption http presentation nested-reference unchanged"},{"id":"IETF RFC 1809","type":"specification","body":"IETF","designation":"RFC 1809","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1809.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1809.txt","https://www.rfc-editor.org/rfc/rfc1809.pdf"],"folder":"IETF/RFC-1809","files":{"txt":{"path":"standards/IETF/RFC-1809/RFC-1809.txt","sha256":"b97262bcb753245d2818f165fbd45ea4c6633c655590101018a615867b77cbc9"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this memo is to distill various opinions and\n suggestions of the End-to-End Research Group regarding the handling\n of Flow Labels into a set of suggestions for IPv6. This memo is for\n information purposes only and is not one of the IPv6 specifications.\n Distribution of this memo is unlimited.","scope_keywords":["1809","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 1809 The purpose of this memo is to distill various opinions and\n suggestions of the End-to-End Research Group regarding the handling\n of Flow Labels into a set of suggestions for IPv6. This memo is for\n information purposes only and is not one of the IPv6 specifications.\n Distribution of this memo is unlimited. 1809 path nested-reference unchanged"},{"id":"IETF RFC 4081","type":"specification","body":"IETF","designation":"RFC 4081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4081.txt","https://www.rfc-editor.org/rfc/rfc4081.pdf"],"folder":"IETF/RFC-4081","files":{"txt":{"path":"standards/IETF/RFC-4081/RFC-4081.txt","sha256":"0cf0c5faea679a06773676269d23cc67a5866999e9703e7c8e379c9f34c8e50f"}},"tags":["nested-reference","unchanged"],"summary":"This threats document provides a detailed analysis of the security\n threats relevant to the Next Steps in Signaling (NSIS) protocol\n suite. It calls attention to, and helps with the understanding of,\n various security considerations in the NSIS Requirements, Framework,\n and Protocol proposals. This document does not describe\n vulnerabilities of specific parts of the NSIS protocol suite.","scope_keywords":["4081","authorization","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 4081 This threats document provides a detailed analysis of the security\n threats relevant to the Next Steps in Signaling (NSIS) protocol\n suite. It calls attention to, and helps with the understanding of,\n various security considerations in the NSIS Requirements, Framework,\n and Protocol proposals. This document does not describe\n vulnerabilities of specific parts of the NSIS protocol suite. 4081 authorization path trust nested-reference unchanged"},{"id":"IETF RFC 3607","type":"specification","body":"IETF","designation":"RFC 3607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3607.txt","https://www.rfc-editor.org/rfc/rfc3607.pdf"],"folder":"IETF/RFC-3607","files":{"txt":{"path":"standards/IETF/RFC-3607/RFC-3607.txt","sha256":"5b0ae98a38c435fcfff90c4c845df6e4b8ad854aa3bd38883f3ff99159a93afd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Leech\nRequest for Comments: 3607 Nortel Networks\nCategory: Informational September 2003\n\n Chinese Lottery Cryptanalysis Revisited:\n The Internet as a Codebreaking Tool\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document revisits the so-called Chinese Lottery\n massively-parallel cryptanalytic attack. It explores Internet-based\n analogues to the Chinese Lottery, and their potentially-serious\n consequences.\n\n1. Introduction\n\n In 1991, Quisquater and Desmedt [DESMEDT91] proposed an esoteric, but\n technically sound, attack against DES or similar ciphers. They\n termed this attack the Chinese Lottery. It was based on a\n massively-parallel","scope_keywords":["3607","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null}],"search_text":"IETF RFC 3607 Network Working Group M. Leech\nRequest for Comments: 3607 Nortel Networks\nCategory: Informational September 2003\n\n Chinese Lottery Cryptanalysis Revisited:\n The Internet as a Codebreaking Tool\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document revisits the so-called Chinese Lottery\n massively-parallel cryptanalytic attack. It explores Internet-based\n analogues to the Chinese Lottery, and their potentially-serious\n consequences.\n\n1. Introduction\n\n In 1991, Quisquater and Desmedt [DESMEDT91] proposed an esoteric, but\n technically sound, attack against DES or similar ciphers. They\n termed this attack the Chinese Lottery. It was based on a\n massively-parallel 3607 key keys nested-reference unchanged"},{"id":"IETF RFC 2267","type":"specification","body":"IETF","designation":"RFC 2267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2267.txt","https://www.rfc-editor.org/rfc/rfc2267.pdf"],"folder":"IETF/RFC-2267","files":{"txt":{"path":"standards/IETF/RFC-2267/RFC-2267.txt","sha256":"1bc4ec459e7a7b7eb87656c3c9ac6c85f8554cc596218ddca9da53828eefc880"}},"tags":["nested-reference","unchanged"],"summary":"Recent occurrences of various Denial of Service (DoS) attacks which\n have employed forged source addresses have proven to be a troublesome\n issue for Internet Service Providers and the Internet community\n overall. This paper discusses a simple, effective, and\n straightforward method for using ingress traffic filtering to\n prohibit DoS attacks which use forged IP addresses to be propagated\n from 'behind' an Internet Service Provider's (ISP) aggregation point.","scope_keywords":["2267"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2644","folder":"IETF/RFC-2644","source":"IETF/RFC-2644/RFC-2644.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null}],"search_text":"IETF RFC 2267 Recent occurrences of various Denial of Service (DoS) attacks which\n have employed forged source addresses have proven to be a troublesome\n issue for Internet Service Providers and the Internet community\n overall. This paper discusses a simple, effective, and\n straightforward method for using ingress traffic filtering to\n prohibit DoS attacks which use forged IP addresses to be propagated\n from 'behind' an Internet Service Provider's (ISP) aggregation point. 2267 nested-reference unchanged"},{"id":"IETF RFC 2644","type":"specification","body":"IETF","designation":"RFC 2644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2644.txt","https://www.rfc-editor.org/rfc/rfc2644.pdf"],"folder":"IETF/RFC-2644","files":{"txt":{"path":"standards/IETF/RFC-2644/RFC-2644.txt","sha256":"aab4831f1d657eacbf81510d2e8c282db55549b72a1222ee8fc3871b390716cb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Senie\nRequest for Comments: 2644 Amaranth Networks Inc.\nUpdates: 1812 August 1999\nBCP: 34\nCategory: Best Current Practice\n\n Changing the Default for Directed Broadcasts in Routers\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n Router Requirements [1] specifies that routers must receive and\n forward directed broadcasts. It also specifies that routers MUST have\n an option to disable this feature, and that this option MUST default\n to permit the receiving and forwarding of directed broadcasts. While\n directed broadcasts have uses, their use on the Internet backbone\n appears to be comprised entirely of mal","scope_keywords":["2644","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 2644 Network Working Group D. Senie\nRequest for Comments: 2644 Amaranth Networks Inc.\nUpdates: 1812 August 1999\nBCP: 34\nCategory: Best Current Practice\n\n Changing the Default for Directed Broadcasts in Routers\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n Router Requirements [1] specifies that routers must receive and\n forward directed broadcasts. It also specifies that routers MUST have\n an option to disable this feature, and that this option MUST default\n to permit the receiving and forwarding of directed broadcasts. While\n directed broadcasts have uses, their use on the Internet backbone\n appears to be comprised entirely of mal 2644 http key nested-reference unchanged"},{"id":"IETF RFC 2827","type":"specification","body":"IETF","designation":"RFC 2827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2827.txt","https://www.rfc-editor.org/rfc/rfc2827.pdf"],"folder":"IETF/RFC-2827","files":{"txt":{"path":"standards/IETF/RFC-2827/RFC-2827.txt","sha256":"6eaa66f058ad3b7b6ddb7010e1a71939e2085b0604d0e1950d43609642135c44"}},"tags":["nested-reference","unchanged"],"summary":"Recent occurrences of various Denial of Service (DoS) attacks which\n have employed forged source addresses have proven to be a troublesome\n issue for Internet Service Providers and the Internet community\n overall. This paper discusses a simple, effective, and\n straightforward method for using ingress traffic filtering to\n prohibit DoS attacks which use forged IP addresses to be propagated\n from 'behind' an Internet Service Provider's (ISP) aggregation point.","scope_keywords":["2827"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3704","folder":"IETF/RFC-3704","source":"IETF/RFC-3704/RFC-3704.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4218","folder":"IETF/RFC-4218","source":"IETF/RFC-4218/RFC-4218.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4732","folder":"IETF/RFC-4732","source":"IETF/RFC-4732/RFC-4732.txt","version":null},{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4832","folder":"IETF/RFC-4832","source":"IETF/RFC-4832/RFC-4832.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8073","folder":"IETF/RFC-8073","source":"IETF/RFC-8073/RFC-8073.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 2827 Recent occurrences of various Denial of Service (DoS) attacks which\n have employed forged source addresses have proven to be a troublesome\n issue for Internet Service Providers and the Internet community\n overall. This paper discusses a simple, effective, and\n straightforward method for using ingress traffic filtering to\n prohibit DoS attacks which use forged IP addresses to be propagated\n from 'behind' an Internet Service Provider's (ISP) aggregation point. 2827 nested-reference unchanged"},{"id":"IETF RFC 3140","type":"specification","body":"IETF","designation":"RFC 3140","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3140.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3140.txt","https://www.rfc-editor.org/rfc/rfc3140.pdf"],"folder":"IETF/RFC-3140","files":{"txt":{"path":"standards/IETF/RFC-3140/RFC-3140.txt","sha256":"c6420914a0ffb5a12471c59e5b9d5c7bf24b440bb97c81c6a10f3c10d9256572"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a 16 bit encoding mechanism for the\n identification of differentiated services Per Hop Behaviors in\n protocol messages. It replaces RFC 2836.","scope_keywords":["3140","identification","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3763","folder":"IETF/RFC-3763","source":"IETF/RFC-3763/RFC-3763.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 3140 This document defines a 16 bit encoding mechanism for the\n identification of differentiated services Per Hop Behaviors in\n protocol messages. It replaces RFC 2836. 3140 identification key management path nested-reference unchanged"},{"id":"IETF RFC 3234","type":"specification","body":"IETF","designation":"RFC 3234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3234.txt","https://www.rfc-editor.org/rfc/rfc3234.pdf"],"folder":"IETF/RFC-3234","files":{"txt":{"path":"standards/IETF/RFC-3234/RFC-3234.txt","sha256":"bd20d7e62e2afe4dfe7c9297e5529cd3472980cb5d9f1e5297483c219f2eee44"}},"tags":["nested-reference","unchanged"],"summary":"This document is intended as part of an IETF discussion about\n \"middleboxes\" - defined as any intermediary box performing functions\n apart from normal, standard functions of an IP router on the data\n path between a source host and destination host. This document\n establishes a catalogue or taxonomy of middleboxes, cites previous\n and current IETF work concerning middleboxes, and attempts to\n identify some preliminary conclusions. It does not, however, claim\n to be definitive.\n\nCarpenter & Brim Informational [Page 1]\n\f\nRFC 3234 Middleboxes: Taxonomy and Issues February 2002","scope_keywords":["3234","http","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3726","folder":"IETF/RFC-3726","source":"IETF/RFC-3726/RFC-3726.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5103","folder":"IETF/RFC-5103","source":"IETF/RFC-5103/RFC-5103.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null}],"search_text":"IETF RFC 3234 This document is intended as part of an IETF discussion about\n \"middleboxes\" - defined as any intermediary box performing functions\n apart from normal, standard functions of an IP router on the data\n path between a source host and destination host. This document\n establishes a catalogue or taxonomy of middleboxes, cites previous\n and current IETF work concerning middleboxes, and attempts to\n identify some preliminary conclusions. It does not, however, claim\n to be definitive.\n\nCarpenter & Brim Informational [Page 1]\n\f\nRFC 3234 Middleboxes: Taxonomy and Issues February 2002 3234 http path qualified nested-reference unchanged"},{"id":"IETF RFC 3484","type":"specification","body":"IETF","designation":"RFC 3484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3484.txt","https://www.rfc-editor.org/rfc/rfc3484.pdf"],"folder":"IETF/RFC-3484","files":{"txt":{"path":"standards/IETF/RFC-3484/RFC-3484.txt","sha256":"1cbfc2ef905a073bdafe265b178e72ab3d1a18b69e3afb5cc5addf62740a8e67"}},"tags":["nested-reference","unchanged"],"summary":"This document describes two algorithms, for source address selection\n and for destination address selection. The algorithms specify\n default behavior for all Internet Protocol version 6 (IPv6)\n implementations. They do not override choices made by applications\n or upper-layer protocols, nor do they preclude the development of\n more advanced mechanisms for address selection. The two algorithms\n share a common context, including an optional mechanism for allowing\n administrators to provide policy that can override the default\n behavior. In dual stack implementations, the destination address\n selection algorithm can consider both IPv4 and IPv6 addresses -\n depending on the available source addresses, the algorithm might\n prefer IPv6 addresses over IPv4 addresses, or vice-versa.\n\n All IPv6 nodes, including both hosts and routers, must implement\n default address selection as defined in this s","scope_keywords":["3484","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4177","folder":"IETF/RFC-4177","source":"IETF/RFC-4177/RFC-4177.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4311","folder":"IETF/RFC-4311","source":"IETF/RFC-4311/RFC-4311.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4943","folder":"IETF/RFC-4943","source":"IETF/RFC-4943/RFC-4943.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5221","folder":"IETF/RFC-5221","source":"IETF/RFC-5221/RFC-5221.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6419","folder":"IETF/RFC-6419","source":"IETF/RFC-6419/RFC-6419.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 3484 This document describes two algorithms, for source address selection\n and for destination address selection. The algorithms specify\n default behavior for all Internet Protocol version 6 (IPv6)\n implementations. They do not override choices made by applications\n or upper-layer protocols, nor do they preclude the development of\n more advanced mechanisms for address selection. The two algorithms\n share a common context, including an optional mechanism for allowing\n administrators to provide policy that can override the default\n behavior. In dual stack implementations, the destination address\n selection algorithm can consider both IPv4 and IPv6 addresses -\n depending on the available source addresses, the algorithm might\n prefer IPv6 addresses over IPv4 addresses, or vice-versa.\n\n All IPv6 nodes, including both hosts and routers, must implement\n default address selection as defined in this s 3484 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 3626","type":"specification","body":"IETF","designation":"RFC 3626","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3626.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3626.txt","https://www.rfc-editor.org/rfc/rfc3626.pdf"],"folder":"IETF/RFC-3626","files":{"txt":{"path":"standards/IETF/RFC-3626/RFC-3626.txt","sha256":"722a7b5838ac29fe71aa48fa91ae619ab1ef8c128a754a84a98d705cefe17580"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Optimized Link State Routing (OLSR)\n protocol for mobile ad hoc networks. The protocol is an optimization\n of the classical link state algorithm tailored to the requirements of\n a mobile wireless LAN. The key concept used in the protocol is that\n of multipoint relays (MPRs). MPRs are selected nodes which forward\n broadcast messages during the flooding process. This technique\n substantially reduces the message overhead as compared to a classical\n flooding mechanism, where every node retransmits each message when it\n receives the first copy of the message. In OLSR, link state\n information is generated only by nodes elected as MPRs. Thus, a\n second optimization is achieved by minimizing the number of control\n messages flooded in the network. As a third optimization, an MPR\n node may chose to report only links between itself and its MPR\n selectors. Hence, as contr","scope_keywords":["3626","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 4919","folder":"IETF/RFC-4919","source":"IETF/RFC-4919/RFC-4919.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5497","folder":"IETF/RFC-5497","source":"IETF/RFC-5497/RFC-5497.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null}],"search_text":"IETF RFC 3626 This document describes the Optimized Link State Routing (OLSR)\n protocol for mobile ad hoc networks. The protocol is an optimization\n of the classical link state algorithm tailored to the requirements of\n a mobile wireless LAN. The key concept used in the protocol is that\n of multipoint relays (MPRs). MPRs are selected nodes which forward\n broadcast messages during the flooding process. This technique\n substantially reduces the message overhead as compared to a classical\n flooding mechanism, where every node retransmits each message when it\n receives the first copy of the message. In OLSR, link state\n information is generated only by nodes elected as MPRs. Thus, a\n second optimization is achieved by minimizing the number of control\n messages flooded in the network. As a third optimization, an MPR\n node may chose to report only links between itself and its MPR\n selectors. Hence, as contr 3626 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3654","type":"specification","body":"IETF","designation":"RFC 3654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3654.txt","https://www.rfc-editor.org/rfc/rfc3654.pdf"],"folder":"IETF/RFC-3654","files":{"txt":{"path":"standards/IETF/RFC-3654/RFC-3654.txt","sha256":"6c167dbf8573e21e84a12979268e8a3fb4aa8e9445a7c4b7d6b3caef330f5028"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces the Forwarding and Control Element\n Separation (ForCES) architecture and defines a set of associated\n terminology. This document also defines a set of architectural,\n modeling, and protocol requirements to logically separate the control\n and data forwarding planes of an IP (IPv4, IPv6, etc.) networking\n device.","scope_keywords":["3654","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null}],"search_text":"IETF RFC 3654 This document introduces the Forwarding and Control Element\n Separation (ForCES) architecture and defines a set of associated\n terminology. This document also defines a set of architectural,\n modeling, and protocol requirements to logically separate the control\n and data forwarding planes of an IP (IPv4, IPv6, etc.) networking\n device. 3654 management path nested-reference unchanged"},{"id":"IETF RFC 4560","type":"specification","body":"IETF","designation":"RFC 4560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4560.txt","https://www.rfc-editor.org/rfc/rfc4560.pdf"],"folder":"IETF/RFC-4560","files":{"txt":{"path":"standards/IETF/RFC-4560/RFC-4560.txt","sha256":"a37145b4af0493dfd083f87abcc1691e1a2bb7b507552007ad5fe3230169bfef"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines Management Information Bases (MIBs) for performing\n ping, traceroute, and lookup operations at a host. When managing a\n network, it is useful to be able to initiate and retrieve the results\n of ping or traceroute operations when they are performed at a remote\n host. A lookup capability is defined in order to enable resolution\n of either an IP address to an DNS name or a DNS name to an IP address\n at a remote host.\n\n Currently, there are several enterprise-specific MIBs for performing\n remote ping or traceroute operations. The purpose of this memo is to\n define a standards-based solution to enable interoperability.\n\nQuittek & White Standards Track [Page 1]\n\f\nRFC 4560 REMOPS MIB June 2006","scope_keywords":["4560","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4560 This memo defines Management Information Bases (MIBs) for performing\n ping, traceroute, and lookup operations at a host. When managing a\n network, it is useful to be able to initiate and retrieve the results\n of ping or traceroute operations when they are performed at a remote\n host. A lookup capability is defined in order to enable resolution\n of either an IP address to an DNS name or a DNS name to an IP address\n at a remote host.\n\n Currently, there are several enterprise-specific MIBs for performing\n remote ping or traceroute operations. The purpose of this memo is to\n define a standards-based solution to enable interoperability.\n\nQuittek & White Standards Track [Page 1]\n\f\nRFC 4560 REMOPS MIB June 2006 4560 key management path nested-reference unchanged"},{"id":"IETF RFC 5136","type":"specification","body":"IETF","designation":"RFC 5136","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5136.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5136.txt","https://www.rfc-editor.org/rfc/rfc5136.pdf"],"folder":"IETF/RFC-5136","files":{"txt":{"path":"standards/IETF/RFC-5136/RFC-5136.txt","sha256":"54ff48c0bd115907eb65e64d165a392ff79b561a95f3fa169a3120e38725f91d"}},"tags":["nested-reference","unchanged"],"summary":"Measuring capacity is a task that sounds simple, but in reality can\n be quite complex. In addition, the lack of a unified nomenclature on\n this subject makes it increasingly difficult to properly build, test,\n and use techniques and tools built around these constructs. This\n document provides definitions for the terms 'Capacity' and 'Available\n Capacity' related to IP traffic traveling between a source and\n destination in an IP network. By doing so, we hope to provide a\n common framework for the discussion and analysis of a diverse set of\n current and future estimation techniques.\n\nChimento & Ishac Informational [Page 1]\n\f\nRFC 5136 Network Capacity February 2008","scope_keywords":["5136","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null}],"search_text":"IETF RFC 5136 Measuring capacity is a task that sounds simple, but in reality can\n be quite complex. In addition, the lack of a unified nomenclature on\n this subject makes it increasingly difficult to properly build, test,\n and use techniques and tools built around these constructs. This\n document provides definitions for the terms 'Capacity' and 'Available\n Capacity' related to IP traffic traveling between a source and\n destination in an IP network. By doing so, we hope to provide a\n common framework for the discussion and analysis of a diverse set of\n current and future estimation techniques.\n\nChimento & Ishac Informational [Page 1]\n\f\nRFC 5136 Network Capacity February 2008 5136 path subject nested-reference unchanged"},{"id":"IETF RFC 5388","type":"specification","body":"IETF","designation":"RFC 5388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5388.txt","https://www.rfc-editor.org/rfc/rfc5388.pdf"],"folder":"IETF/RFC-5388","files":{"txt":{"path":"standards/IETF/RFC-5388/RFC-5388.txt","sha256":"1893ff1c9549b80dd1505f9e70b5e5653a8b2e4843c76a9fff199ad65d02ffa2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a standard way to store the configuration and\n the results of traceroute measurements. This document first\n describes the terminology used in this document and the traceroute\n tool itself; afterwards, the common information model is defined,\n dividing the information elements into two semantically separated\n groups (configuration elements and results elements). Moreover, an\n additional element is defined to relate configuration elements and\n results elements by means of a common unique identifier. On the\n basis of the information model, a data model based on XML is defined\n to store the results of traceroute measurements.\n\nNiccolini, et al. Standards Track [Page 1]\n\f\nRFC 5388 Traceroute Storage Format December 2008","scope_keywords":["5388","http","key","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5388 This document describes a standard way to store the configuration and\n the results of traceroute measurements. This document first\n describes the terminology used in this document and the traceroute\n tool itself; afterwards, the common information model is defined,\n dividing the information elements into two semantically separated\n groups (configuration elements and results elements). Moreover, an\n additional element is defined to relate configuration elements and\n results elements by means of a common unique identifier. On the\n basis of the information model, a data model based on XML is defined\n to store the results of traceroute measurements.\n\nNiccolini, et al. Standards Track [Page 1]\n\f\nRFC 5388 Traceroute Storage Format December 2008 5388 http key license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2216","type":"specification","body":"IETF","designation":"RFC 2216","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2216.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2216.txt","https://www.rfc-editor.org/rfc/rfc2216.pdf"],"folder":"IETF/RFC-2216","files":{"txt":{"path":"standards/IETF/RFC-2216/RFC-2216.txt","sha256":"dfe88f8fe684ccab23a5f9f04af33e9870edceeadbf03e2b3b5dd1e8e5b65469"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for specifying services provided by\n network elements, and available to applications, in an internetwork\n which offers multiple qualities of service. The document first\n provides some necessary context -- including relevant definitions and\n suggested data formats -- and then specifies a \"template\" which\n service specification documents should follow. The specification\n template includes per-element requirements such as the service's\n packet handling behavior, parameters required and made available by\n the service, traffic specification and policing requirements, and\n traffic ordering relationships. It also includes evaluation criteria\n for elements providing the service, and examples of how the service\n might be implemented (by network elements) and used (by\n applications).","scope_keywords":["2216","delivery","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2211","folder":"IETF/RFC-2211","source":"IETF/RFC-2211/RFC-2211.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null}],"search_text":"IETF RFC 2216 This document defines a framework for specifying services provided by\n network elements, and available to applications, in an internetwork\n which offers multiple qualities of service. The document first\n provides some necessary context -- including relevant definitions and\n suggested data formats -- and then specifies a \"template\" which\n service specification documents should follow. The specification\n template includes per-element requirements such as the service's\n packet handling behavior, parameters required and made available by\n the service, traffic specification and policing requirements, and\n traffic ordering relationships. It also includes evaluation criteria\n for elements providing the service, and examples of how the service\n might be implemented (by network elements) and used (by\n applications). 2216 delivery management path presentation nested-reference unchanged"},{"id":"IETF RFC 5771","type":"specification","body":"IETF","designation":"RFC 5771","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5771.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5771.txt","https://www.rfc-editor.org/rfc/rfc5771.pdf"],"folder":"IETF/RFC-5771","files":{"txt":{"path":"standards/IETF/RFC-5771/RFC-5771.txt","sha256":"a41d561a277f09736777f3f2d5bc16407bb5dc066dfe703ed85d91d04d46ba46"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance for the Internet Assigned Numbers\n Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes\n RFC 3171 and RFC 3138 and updates RFC 2780.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5771.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78","scope_keywords":["5771","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5771 This document provides guidance for the Internet Assigned Numbers\n Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes\n RFC 3171 and RFC 3138 and updates RFC 2780.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5771.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 5771 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 1822","type":"specification","body":"IETF","designation":"RFC 1822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1822.txt","https://www.rfc-editor.org/rfc/rfc1822.pdf"],"folder":"IETF/RFC-1822","files":{"txt":{"path":"standards/IETF/RFC-1822/RFC-1822.txt","sha256":"3753baf94e29168087afd8774f591559c959bdb336b2ce28a4fa3701173add45"}},"tags":["nested-reference","unchanged"],"summary":"This Request for Comments records a grant by IBM Corporation to\n permit the conditional free use of one of its patents. This grant is\n made to help facilitate adoption of the Internet Key Management\n Protocol contribution IBM has offered to the IETF. It should be noted\n that the confirmatory license mentioned is optional. The grant is\n made in this RFC and parties have it even if they do not request a\n confirmation from IBM.","scope_keywords":["1822","key","license","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1834","folder":"IETF/RFC-1834","source":"IETF/RFC-1834/RFC-1834.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1822 This Request for Comments records a grant by IBM Corporation to\n permit the conditional free use of one of its patents. This grant is\n made to help facilitate adoption of the Internet Key Management\n Protocol contribution IBM has offered to the IETF. It should be noted\n that the confirmatory license mentioned is optional. The grant is\n made in this RFC and parties have it even if they do not request a\n confirmation from IBM. 1822 key license management nested-reference unchanged"},{"id":"IETF RFC 1834","type":"specification","body":"IETF","designation":"RFC 1834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1834.txt","https://www.rfc-editor.org/rfc/rfc1834.pdf"],"folder":"IETF/RFC-1834","files":{"txt":{"path":"standards/IETF/RFC-1834/RFC-1834.txt","sha256":"bd667a3430b7b142e51f1e27789192b5a743003182775e39b5764c0fb0802f3d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Gargano\nRequest for Comments: 1834 K. Weiss\nCategory: Informational University of California, Davis\n August 1995\n\n Whois and Network Information Lookup Service\n Whois++\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nI. Introduction\n\n As currently defined, NICNAME/WHOIS [HARR85] service is a TCP\n transaction based query/response server, running on a few specific\n central machines, that provides netwide directory service to Internet\n users. The Network Information Center (NIC) maintains the central\n NICNAME database and server, defined in RFC 954, providing online\n look-up of individuals, network organizations, key host machines, and\n other information of interest to users of the Internet. The\n usefulness of this service has lea","scope_keywords":["1834","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null}],"search_text":"IETF RFC 1834 Network Working Group J. Gargano\nRequest for Comments: 1834 K. Weiss\nCategory: Informational University of California, Davis\n August 1995\n\n Whois and Network Information Lookup Service\n Whois++\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nI. Introduction\n\n As currently defined, NICNAME/WHOIS [HARR85] service is a TCP\n transaction based query/response server, running on a few specific\n central machines, that provides netwide directory service to Internet\n users. The Network Information Center (NIC) maintains the central\n NICNAME database and server, defined in RFC 954, providing online\n look-up of individuals, network organizations, key host machines, and\n other information of interest to users of the Internet. The\n usefulness of this service has lea 1834 key registered nested-reference unchanged"},{"id":"IETF RFC 1824","type":"specification","body":"IETF","designation":"RFC 1824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1824.txt","https://www.rfc-editor.org/rfc/rfc1824.pdf"],"folder":"IETF/RFC-1824","files":{"txt":{"path":"standards/IETF/RFC-1824/RFC-1824.txt","sha256":"dc7085098c4413d7437ad4dd1ab4d793ae9180b39a57e1bba96d307e9e861e76"}},"tags":["nested-reference","unchanged"],"summary":"This informational RFC describes the basic mechanisms and functions\n of an identity based system for the secure authenticated exchange of\n cryptographic keys, the generation of signatures, and the authentic\n distribution of public keys.","scope_keywords":["1824","authentication","driving","hash","holder","key","keys","license","management","presentation","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1824 This informational RFC describes the basic mechanisms and functions\n of an identity based system for the secure authenticated exchange of\n cryptographic keys, the generation of signatures, and the authentic\n distribution of public keys. 1824 authentication driving hash holder key keys license management presentation signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2207","type":"specification","body":"IETF","designation":"RFC 2207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2207.txt","https://www.rfc-editor.org/rfc/rfc2207.pdf"],"folder":"IETF/RFC-2207","files":{"txt":{"path":"standards/IETF/RFC-2207/RFC-2207.txt","sha256":"f04fa7e592fdbad4713c255f987cc754cba149343159c8b88629e2847d04a683"}},"tags":["nested-reference","unchanged"],"summary":"This document presents extensions to Version 1 of RSVP. These\n extensions permit support of individual data flows using RFC 1826, IP\n Authentication Header (AH) or RFC 1827, IP Encapsulating Security\n Payload (ESP). RSVP Version 1 as currently specified can support the\n IPSEC protocols, but only on a per address, per protocol basis not on\n a per flow basis. The presented extensions can be used with both\n IPv4 and IPv6.\n\nBerger & O'Malley Standards Track [Page 1]\n\f\nRFC 2207 RSVP Extensions for IPSEC September 1997","scope_keywords":["2207","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2205","folder":"IETF/RFC-2205","source":"IETF/RFC-2205/RFC-2205.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2209","folder":"IETF/RFC-2209","source":"IETF/RFC-2209/RFC-2209.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3936","folder":"IETF/RFC-3936","source":"IETF/RFC-3936/RFC-3936.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 2207 This document presents extensions to Version 1 of RSVP. These\n extensions permit support of individual data flows using RFC 1826, IP\n Authentication Header (AH) or RFC 1827, IP Encapsulating Security\n Payload (ESP). RSVP Version 1 as currently specified can support the\n IPSEC protocols, but only on a per address, per protocol basis not on\n a per flow basis. The presented extensions can be used with both\n IPv4 and IPv6.\n\nBerger & O'Malley Standards Track [Page 1]\n\f\nRFC 2207 RSVP Extensions for IPSEC September 1997 2207 authentication path nested-reference unchanged"},{"id":"IETF RFC 2243","type":"specification","body":"IETF","designation":"RFC 2243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2243.txt","https://www.rfc-editor.org/rfc/rfc2243.pdf"],"folder":"IETF/RFC-2243","files":{"txt":{"path":"standards/IETF/RFC-2243/RFC-2243.txt","sha256":"0c8d93cceba0e54189f86d44269149a760ea768845235609c625a7354cb532f8"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a specification for a type of response to an\n OTP [RFC 1938] challenge that carries explicit indication of the\n response's encoding. Codings for the two mandatory OTP data formats\n using this new type of response are presented.\n\n This document also provides a specification for a response that\n allows an OTP generator to request that a server re-initialize a\n sequence and change parameters such as the secret pass phrase.\n\n1. Conventions, Terms, and Notation\n\n This document specifies the data formats and software behaviors\n needed to use OTP extended responses. The data formats are described\n three ways: using an ad-hoc UNIX manual page style syntax, using\n augmented BNF described in sections two and three of RFC 822, and by\n examples. Should there be any conflict between these descriptions,\n the augmented BNF takes precedence. The software behaviors are\n described i","scope_keywords":["2243","authentication","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null}],"search_text":"IETF RFC 2243 This document provides a specification for a type of response to an\n OTP [RFC 1938] challenge that carries explicit indication of the\n response's encoding. Codings for the two mandatory OTP data formats\n using this new type of response are presented.\n\n This document also provides a specification for a response that\n allows an OTP generator to request that a server re-initialize a\n sequence and change parameters such as the secret pass phrase.\n\n1. Conventions, Terms, and Notation\n\n This document specifies the data formats and software behaviors\n needed to use OTP extended responses. The data formats are described\n three ways: using an ad-hoc UNIX manual page style syntax, using\n augmented BNF described in sections two and three of RFC 822, and by\n examples. Should there be any conflict between these descriptions,\n the augmented BNF takes precedence. The software behaviors are\n described i 2243 authentication tls nested-reference unchanged"},{"id":"IETF RFC 2367","type":"specification","body":"IETF","designation":"RFC 2367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2367.txt","https://www.rfc-editor.org/rfc/rfc2367.pdf"],"folder":"IETF/RFC-2367","files":{"txt":{"path":"standards/IETF/RFC-2367/RFC-2367.txt","sha256":"ffcccb62b4657ca767ea16828d55cdddeaa89d92dd5d0126afcae2fe2cd47d52"}},"tags":["nested-reference","unchanged"],"summary":"A generic key management API that can be used not only for IP\n Security [Atk95a] [Atk95b] [Atk95c] but also for other network\n security services is presented in this document. Version 1 of this\n API was implemented inside 4.4-Lite BSD as part of the U. S. Naval\n Research Laboratory's freely distributable and usable IPv6 and IPsec\n implementation[AMPMC96]. It is documented here for the benefit of\n others who might also adopt and use the API, thus providing increased\n portability of key management applications (e.g. a manual keying\n application, an ISAKMP daemon, a GKMP daemon [HM97a][HM97b], a\n Photuris daemon, or a SKIP certificate discovery protocol daemon).","scope_keywords":["2367","algorithm","algorithms","attribute","attributes","certificate","key","keys","management","policies","policy","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2367 A generic key management API that can be used not only for IP\n Security [Atk95a] [Atk95b] [Atk95c] but also for other network\n security services is presented in this document. Version 1 of this\n API was implemented inside 4.4-Lite BSD as part of the U. S. Naval\n Research Laboratory's freely distributable and usable IPv6 and IPsec\n implementation[AMPMC96]. It is documented here for the benefit of\n others who might also adopt and use the API, thus providing increased\n portability of key management applications (e.g. a manual keying\n application, an ISAKMP daemon, a GKMP daemon [HM97a][HM97b], a\n Photuris daemon, or a SKIP certificate discovery protocol daemon). 2367 algorithm algorithms attribute attributes certificate key keys management policies policy trust tsp nested-reference unchanged"},{"id":"IETF RFC 2753","type":"specification","body":"IETF","designation":"RFC 2753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2753.txt","https://www.rfc-editor.org/rfc/rfc2753.pdf"],"folder":"IETF/RFC-2753","files":{"txt":{"path":"standards/IETF/RFC-2753/RFC-2753.txt","sha256":"3110bb69949737a601fa8047c6feab541dcfe821187fe26c3180ebfffef989c0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Yavatkar\nRequest for Comments: 2753 Intel\nCategory: Informational D. Pendarakis\n IBM\n R. Guerin\n U. Of Pennsylvania\n January 2000\n\n A Framework for Policy-based Admission Control\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\n1. Introduction\n\n The IETF working groups such as Integrated Services (called \"int-\n serv\") and RSVP [1] have developed extensions to the IP architecture\n and the best-effort service model so that applications or end users\n can request specific quality (or levels) of service from an\n internetwork in addition to the current IP best-effort service.\n Recent efforts in the Differentiated Services Working Group are also\n directed at t","scope_keywords":["2753","credential","credentials","identification","path","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2749","folder":"IETF/RFC-2749","source":"IETF/RFC-2749/RFC-2749.txt","version":null},{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2996","folder":"IETF/RFC-2996","source":"IETF/RFC-2996/RFC-2996.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3127","folder":"IETF/RFC-3127","source":"IETF/RFC-3127/RFC-3127.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3753","folder":"IETF/RFC-3753","source":"IETF/RFC-3753/RFC-3753.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2753 Network Working Group R. Yavatkar\nRequest for Comments: 2753 Intel\nCategory: Informational D. Pendarakis\n IBM\n R. Guerin\n U. Of Pennsylvania\n January 2000\n\n A Framework for Policy-based Admission Control\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\n1. Introduction\n\n The IETF working groups such as Integrated Services (called \"int-\n serv\") and RSVP [1] have developed extensions to the IP architecture\n and the best-effort service model so that applications or end users\n can request specific quality (or levels) of service from an\n internetwork in addition to the current IP best-effort service.\n Recent efforts in the Differentiated Services Working Group are also\n directed at t 2753 credential credentials identification path policies policy trust nested-reference unchanged"},{"id":"IETF RFC 2344","type":"specification","body":"IETF","designation":"RFC 2344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2344.txt","https://www.rfc-editor.org/rfc/rfc2344.pdf"],"folder":"IETF/RFC-2344","files":{"txt":{"path":"standards/IETF/RFC-2344/RFC-2344.txt","sha256":"5374cbb7bf73f99d49f258b6be4d8e836c057f291f3a996e298aa75966a12b28"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP uses tunneling from the home agent to the mobile node's\n care-of address, but rarely in the reverse direction. Usually, a\n mobile node sends its packets through a router on the foreign\n network, and assumes that routing is independent of source address.\n When this assumption is not true, it is convenient to establish a\n topologically correct reverse tunnel from the care-of address to the\n home agent.\n\n This document proposes backwards-compatible extensions to Mobile IP\n in order to support topologically correct reverse tunnels. This\n document does not attempt to solve the problems posed by firewalls\n located between the home agent and the mobile node's care-of address.","scope_keywords":["2344","authentication","delivery","encryption","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2827","folder":"IETF/RFC-2827","source":"IETF/RFC-2827/RFC-2827.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3025","folder":"IETF/RFC-3025","source":"IETF/RFC-3025/RFC-3025.txt","version":null},{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null}],"search_text":"IETF RFC 2344 Mobile IP uses tunneling from the home agent to the mobile node's\n care-of address, but rarely in the reverse direction. Usually, a\n mobile node sends its packets through a router on the foreign\n network, and assumes that routing is independent of source address.\n When this assumption is not true, it is convenient to establish a\n topologically correct reverse tunnel from the care-of address to the\n home agent.\n\n This document proposes backwards-compatible extensions to Mobile IP\n in order to support topologically correct reverse tunnels. This\n document does not attempt to solve the problems posed by firewalls\n located between the home agent and the mobile node's care-of address. 2344 authentication delivery encryption key path nested-reference unchanged"},{"id":"IETF RFC 2356","type":"specification","body":"IETF","designation":"RFC 2356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2356.txt","https://www.rfc-editor.org/rfc/rfc2356.pdf"],"folder":"IETF/RFC-2356","files":{"txt":{"path":"standards/IETF/RFC-2356/RFC-2356.txt","sha256":"4e6680e977ed4a8093e17640abc36ed63c3ff2d69b866df7f56f51a62dce8e82"}},"tags":["nested-reference","unchanged"],"summary":"The Mobile IP specification establishes the mechanisms that enable a\n mobile host to maintain and use the same IP address as it changes its\n point of attachment to the network. Mobility implies higher security\n risks than static operation, because the traffic may at times take\n unforeseen network paths with unknown or unpredictable security\n characteristics. The Mobile IP specification makes no provisions for\n securing data traffic. The mechanisms described in this document\n allow a mobile node out on a public sector of the internet to\n negotiate access past a SKIP firewall, and construct a secure channel\n into its home network.\n\n In addition to securing traffic, our mechanisms allow a mobile node\n to roam into regions that (1) impose ingress filtering, and (2) use a\n different address space.","scope_keywords":["2356","authentication","encryption","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3025","folder":"IETF/RFC-3025","source":"IETF/RFC-3025/RFC-3025.txt","version":null},{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 2356 The Mobile IP specification establishes the mechanisms that enable a\n mobile host to maintain and use the same IP address as it changes its\n point of attachment to the network. Mobility implies higher security\n risks than static operation, because the traffic may at times take\n unforeseen network paths with unknown or unpredictable security\n characteristics. The Mobile IP specification makes no provisions for\n securing data traffic. The mechanisms described in this document\n allow a mobile node out on a public sector of the internet to\n negotiate access past a SKIP firewall, and construct a secure channel\n into its home network.\n\n In addition to securing traffic, our mechanisms allow a mobile node\n to roam into regions that (1) impose ingress filtering, and (2) use a\n different address space. 2356 authentication encryption path risk nested-reference unchanged"},{"id":"IETF RFC 2208","type":"specification","body":"IETF","designation":"RFC 2208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2208.txt","https://www.rfc-editor.org/rfc/rfc2208.pdf"],"folder":"IETF/RFC-2208","files":{"txt":{"path":"standards/IETF/RFC-2208/RFC-2208.txt","sha256":"fe24dcd5b2a429ce5c883e1141061f3f3d8c4cd20bd8262d0ae8028622035608"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the applicability of RSVP along with the\n Integrated Services protocols and other components of resource\n reservation and offers guidelines for deployment of resource\n reservation at this time. This document accompanies the first\n submission of RSVP and integrated services specifications onto the\n Internet standards track.\n\nMankin, Ed., et. al. Informational [Page 1]\n\f\nRFC 2208 RSVP Applicability and Deployment September 1997\n\n1. Introduction\n\n RSVP [RFC 2205] is a unicast and multicast signalling protocol,\n designed to install and maintain reservation state information at\n each router along the path of a stream of data. The state handled by\n RSVP is defined by services [RFC 2211] and [RFC 2212] specified by\n the Integrated Services WG. These services and RSVP are being\n introduced to the IETF's standards track jointly. From henceforth,\n the acronym RSVP on its ow","scope_keywords":["2208","algorithm","algorithms","authentication","authorization","key","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null}],"search_text":"IETF RFC 2208 This document describes the applicability of RSVP along with the\n Integrated Services protocols and other components of resource\n reservation and offers guidelines for deployment of resource\n reservation at this time. This document accompanies the first\n submission of RSVP and integrated services specifications onto the\n Internet standards track.\n\nMankin, Ed., et. al. Informational [Page 1]\n\f\nRFC 2208 RSVP Applicability and Deployment September 1997\n\n1. Introduction\n\n RSVP [RFC 2205] is a unicast and multicast signalling protocol,\n designed to install and maintain reservation state information at\n each router along the path of a stream of data. The state handled by\n RSVP is defined by services [RFC 2211] and [RFC 2212] specified by\n the Integrated Services WG. These services and RSVP are being\n introduced to the IETF's standards track jointly. From henceforth,\n the acronym RSVP on its ow 2208 algorithm algorithms authentication authorization key management path policies policy nested-reference unchanged"},{"id":"IETF RFC 3446","type":"specification","body":"IETF","designation":"RFC 3446","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3446.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3446.txt","https://www.rfc-editor.org/rfc/rfc3446.pdf"],"folder":"IETF/RFC-3446","files":{"txt":{"path":"standards/IETF/RFC-3446/RFC-3446.txt","sha256":"24012be3c385fac65061f8a3185f3c0c858df4141389c64c5b724ecd55536be8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to allow for an arbitrary number\n of Rendevous Points (RPs) per group in a single shared-tree Protocol\n Independent Multicast-Sparse Mode (PIM-SM) domain.\n\n1. Introduction\n\n PIM-SM, as defined in RFC 2362, allows for only a single active RP\n per group, and as such the decision of optimal RP placement can\n become problematic for a multi-regional network deploying PIM-SM.\n\n Anycast RP relaxes an important constraint in PIM-SM, namely, that\n there can be only one group to RP mapping can be active at any time.\n The single mapping property has several implications, including\n traffic concentration, lack of scalable register decapsulation (when\n using the shared tree), slow convergence when an active RP fails,\n possible sub-optimal forwarding of multicast packets, and distant RP\n dependencies. These properties of PIM-SM have been demonstrated in\n native cont","scope_keywords":["3446","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3956","folder":"IETF/RFC-3956","source":"IETF/RFC-3956/RFC-3956.txt","version":null},{"body":"IETF","designation":"RFC 4610","folder":"IETF/RFC-4610","source":"IETF/RFC-4610/RFC-4610.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null}],"search_text":"IETF RFC 3446 This document describes a mechanism to allow for an arbitrary number\n of Rendevous Points (RPs) per group in a single shared-tree Protocol\n Independent Multicast-Sparse Mode (PIM-SM) domain.\n\n1. Introduction\n\n PIM-SM, as defined in RFC 2362, allows for only a single active RP\n per group, and as such the decision of optimal RP placement can\n become problematic for a multi-regional network deploying PIM-SM.\n\n Anycast RP relaxes an important constraint in PIM-SM, namely, that\n there can be only one group to RP mapping can be active at any time.\n The single mapping property has several implications, including\n traffic concentration, lack of scalable register decapsulation (when\n using the shared tree), slow convergence when an active RP fails,\n possible sub-optimal forwarding of multicast packets, and distant RP\n dependencies. These properties of PIM-SM have been demonstrated in\n native cont 3446 key path nested-reference unchanged"},{"id":"IETF RFC 1829","type":"specification","body":"IETF","designation":"RFC 1829","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1829.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1829.txt","https://www.rfc-editor.org/rfc/rfc1829.pdf"],"folder":"IETF/RFC-1829","files":{"txt":{"path":"standards/IETF/RFC-1829/RFC-1829.txt","sha256":"08458603039ef8c8c3e6bd7476d6394ff12629c3fd4625502f93edf2273526b5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the DES-CBC security transform for the IP\n Encapsulating Security Payload (ESP).","scope_keywords":["1829","algorithm","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1825","folder":"IETF/RFC-1825","source":"IETF/RFC-1825/RFC-1825.txt","version":null},{"body":"IETF","designation":"RFC 1827","folder":"IETF/RFC-1827","source":"IETF/RFC-1827/RFC-1827.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 1829 This document describes the DES-CBC security transform for the IP\n Encapsulating Security Payload (ESP). 1829 algorithm encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 1832","type":"specification","body":"IETF","designation":"RFC 1832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1832.txt","https://www.rfc-editor.org/rfc/rfc1832.pdf"],"folder":"IETF/RFC-1832","files":{"txt":{"path":"standards/IETF/RFC-1832/RFC-1832.txt","sha256":"0a9719d8b149a155f3fa7a69458b58fc0eac8ad775307ae38fb2f690257ecd6f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the External Data Representation Standard\n (XDR) protocol as it is currently deployed and accepted.","scope_keywords":["1832","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1833","folder":"IETF/RFC-1833","source":"IETF/RFC-1833/RFC-1833.txt","version":null},{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2188","folder":"IETF/RFC-2188","source":"IETF/RFC-2188/RFC-2188.txt","version":null},{"body":"IETF","designation":"RFC 2203","folder":"IETF/RFC-2203","source":"IETF/RFC-2203/RFC-2203.txt","version":null},{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4506","folder":"IETF/RFC-4506","source":"IETF/RFC-4506/RFC-4506.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null}],"search_text":"IETF RFC 1832 This document describes the External Data Representation Standard\n (XDR) protocol as it is currently deployed and accepted. 1832 presentation nested-reference unchanged"},{"id":"IETF RFC 1833","type":"specification","body":"IETF","designation":"RFC 1833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1833.txt","https://www.rfc-editor.org/rfc/rfc1833.pdf"],"folder":"IETF/RFC-1833","files":{"txt":{"path":"standards/IETF/RFC-1833/RFC-1833.txt","sha256":"c2e935c226510504d5685e01218ad2ddb656d5a8aa54105eb41b7d538fc4acba"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the binding protocols used in conjunction\n with the ONC Remote Procedure Call (ONC RPC Version 2) protocols.","scope_keywords":["1833","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2054","folder":"IETF/RFC-2054","source":"IETF/RFC-2054/RFC-2054.txt","version":null},{"body":"IETF","designation":"RFC 2055","folder":"IETF/RFC-2055","source":"IETF/RFC-2055/RFC-2055.txt","version":null},{"body":"IETF","designation":"RFC 2188","folder":"IETF/RFC-2188","source":"IETF/RFC-2188/RFC-2188.txt","version":null},{"body":"IETF","designation":"RFC 2203","folder":"IETF/RFC-2203","source":"IETF/RFC-2203/RFC-2203.txt","version":null},{"body":"IETF","designation":"RFC 2224","folder":"IETF/RFC-2224","source":"IETF/RFC-2224/RFC-2224.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 1833 This document describes the binding protocols used in conjunction\n with the ONC Remote Procedure Call (ONC RPC Version 2) protocols. 1833 identification presentation nested-reference unchanged"},{"id":"IETF RFC 2188","type":"specification","body":"IETF","designation":"RFC 2188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2188.txt","https://www.rfc-editor.org/rfc/rfc2188.pdf"],"folder":"IETF/RFC-2188","files":{"txt":{"path":"standards/IETF/RFC-2188/RFC-2188.txt","sha256":"11a0b3b926b85033ce7878816269a81387f26410275ee2361880ab584fab9222"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the service model, the notation and protocol\n for Efficient Short Remote Operations (ESRO). The ESRO service is\n similar to and is consistent with other Remote Procedure Call\n services. The emphasis of ESRO service definition and the ESRO\n protocol is on efficiency. ESRO is designed specifically with\n wireless network (e.g., CDPD) usage in mind.\n\n ESRO protocol provides reliable connectionless remote operation\n services on top of UDP (or any other non-reliable connectionless\n transport service) with minimum overhead. ESRO protocol supports\n segmentation and reassembly, concatenation and separation as well as\n multiplexing for service users (applications).\n\n ESRO allows for trade-offs between efficiency and reliability by\n specifying both 2-way hand-shake and 3-way hand-shake based protocols.\n\n Encoding mechanisms for presentation of the parameters of remote\n opera","scope_keywords":["2188","authorization","delivery","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null}],"search_text":"IETF RFC 2188 This document specifies the service model, the notation and protocol\n for Efficient Short Remote Operations (ESRO). The ESRO service is\n similar to and is consistent with other Remote Procedure Call\n services. The emphasis of ESRO service definition and the ESRO\n protocol is on efficiency. ESRO is designed specifically with\n wireless network (e.g., CDPD) usage in mind.\n\n ESRO protocol provides reliable connectionless remote operation\n services on top of UDP (or any other non-reliable connectionless\n transport service) with minimum overhead. ESRO protocol supports\n segmentation and reassembly, concatenation and separation as well as\n multiplexing for service users (applications).\n\n ESRO allows for trade-offs between efficiency and reliability by\n specifying both 2-way hand-shake and 3-way hand-shake based protocols.\n\n Encoding mechanisms for presentation of the parameters of remote\n opera 2188 authorization delivery identification presentation nested-reference unchanged"},{"id":"IETF RFC 2203","type":"specification","body":"IETF","designation":"RFC 2203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2203.txt","https://www.rfc-editor.org/rfc/rfc2203.pdf"],"folder":"IETF/RFC-2203","files":{"txt":{"path":"standards/IETF/RFC-2203/RFC-2203.txt","sha256":"1f2b5f8e7993e689831191c27fd5c315a5bca65a9fd0d134e0517d823e106788"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an ONC/RPC security flavor that allows RPC\n protocols to access the Generic Security Services Application\n Programming Interface (referred to henceforth as GSS-API).","scope_keywords":["2203","authentication","credential","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2755","folder":"IETF/RFC-2755","source":"IETF/RFC-2755/RFC-2755.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7531","folder":"IETF/RFC-7531","source":"IETF/RFC-7531/RFC-7531.txt","version":null}],"search_text":"IETF RFC 2203 This memo describes an ONC/RPC security flavor that allows RPC\n protocols to access the Generic Security Services Application\n Programming Interface (referred to henceforth as GSS-API). 2203 authentication credential management registered nested-reference unchanged"},{"id":"IETF RFC 2847","type":"specification","body":"IETF","designation":"RFC 2847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2847.txt","https://www.rfc-editor.org/rfc/rfc2847.pdf"],"folder":"IETF/RFC-2847","files":{"txt":{"path":"standards/IETF/RFC-2847/RFC-2847.txt","sha256":"167ebec5a30fc6ec80534ffb0c5dc8687a63d68237a481b92982883bce4637a5"}},"tags":["nested-reference","unchanged"],"summary":"This memorandum describes a method whereby one can use GSS-API\n [RFC2078] to supply a secure channel between a client and server,\n authenticating the client with a password, and a server with a public\n key certificate. As such, it is analogous to the common low\n infrastructure usage of the Transport Layer Security (TLS) protocol\n [RFC2246].\n\n The method leverages the existing Simple Public Key Mechanism (SPKM)\n [RFC2025], and is specified as a separate GSS-API mechanism (LIPKEY)\n layered above SPKM.","scope_keywords":["2847","algorithm","algorithms","authentication","certificate","http","key","management","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null}],"search_text":"IETF RFC 2847 This memorandum describes a method whereby one can use GSS-API\n [RFC2078] to supply a secure channel between a client and server,\n authenticating the client with a password, and a server with a public\n key certificate. As such, it is analogous to the common low\n infrastructure usage of the Transport Layer Security (TLS) protocol\n [RFC2246].\n\n The method leverages the existing Simple Public Key Mechanism (SPKM)\n [RFC2025], and is specified as a separate GSS-API mechanism (LIPKEY)\n layered above SPKM. 2847 algorithm algorithms authentication certificate http key management tls trust nested-reference unchanged"},{"id":"IETF RFC 3018","type":"specification","body":"IETF","designation":"RFC 3018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3018.txt","https://www.rfc-editor.org/rfc/rfc3018.pdf"],"folder":"IETF/RFC-3018","files":{"txt":{"path":"standards/IETF/RFC-3018/RFC-3018.txt","sha256":"2265f37e24d127a159e48436934869b6aa057fef55b18d27feb234285ce9a67b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Unified Memory Space Protocol (UMSP), which\n gives a capability of immediate access to memory of the remote nodes.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [2].\n\n The following syntax specification uses the augmented Backus-Naur\n Form (ABNF) as described in RFC-2234 [3].","scope_keywords":["3018","identification","key","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 3018 This document specifies Unified Memory Space Protocol (UMSP), which\n gives a capability of immediate access to memory of the remote nodes.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [2].\n\n The following syntax specification uses the augmented Backus-Naur\n Form (ABNF) as described in RFC-2234 [3]. 3018 identification key management profile nested-reference unchanged"},{"id":"IETF RFC 5403","type":"specification","body":"IETF","designation":"RFC 5403","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5403.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5403.txt","https://www.rfc-editor.org/rfc/rfc5403.pdf"],"folder":"IETF/RFC-5403","files":{"txt":{"path":"standards/IETF/RFC-5403/RFC-5403.txt","sha256":"27ee851bca26de5d37972b94a71bc65ecd65deddf501a728c16778d71190f92d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2 of the RPCSEC_GSS protocol.\n Version 2 is the same as version 1 (specified in RFC 2203) except\n that support for channel bindings has been added. RPCSEC_GSS allows\n remote procedure call (RPC) protocols to access the Generic Security\n Services Application Programming Interface (GSS-API).\n\nEisler Standards Track [Page 1]\n\f\nRFC 5403 RPCSEC_GSSv2 February 2009","scope_keywords":["5403","encryption","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 5403 This document describes version 2 of the RPCSEC_GSS protocol.\n Version 2 is the same as version 1 (specified in RFC 2203) except\n that support for channel bindings has been added. RPCSEC_GSS allows\n remote procedure call (RPC) protocols to access the Generic Security\n Services Application Programming Interface (GSS-API).\n\nEisler Standards Track [Page 1]\n\f\nRFC 5403 RPCSEC_GSSv2 February 2009 5403 encryption http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5662","type":"specification","body":"IETF","designation":"RFC 5662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5662.txt","https://www.rfc-editor.org/rfc/rfc5662.pdf"],"folder":"IETF/RFC-5662","files":{"txt":{"path":"standards/IETF/RFC-5662/RFC-5662.txt","sha256":"4aad9353b73e3904875aa2f7834c0a294cdb505609daebd92b7f5b441e32f7c7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides the External Data Representation Standard\n (XDR) description for Network File System version 4 (NFSv4) minor\n version 1.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5662.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro","scope_keywords":["5662","holder","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null}],"search_text":"IETF RFC 5662 This document provides the External Data Representation Standard\n (XDR) description for Network File System version 4 (NFSv4) minor\n version 1.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5662.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro 5662 holder http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2210","type":"specification","body":"IETF","designation":"RFC 2210","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2210.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2210.txt","https://www.rfc-editor.org/rfc/rfc2210.pdf"],"folder":"IETF/RFC-2210","files":{"txt":{"path":"standards/IETF/RFC-2210/RFC-2210.txt","sha256":"90f6b7d5f3917f3cce599e7a5be06f8d0df00ffbac36ae403a4241501a4ed6df"}},"tags":["nested-reference","unchanged"],"summary":"This note describes the use of the RSVP resource reservation protocol\n with the Controlled-Load and Guaranteed QoS control services. The\n RSVP protocol defines several data objects which carry resource\n reservation information but are opaque to RSVP itself. The usage and\n data format of those objects is given here.\n\n1. Introduction\n\n The Internet integrated services framework provides the ability for\n applications to choose among multiple, controlled levels of delivery\n service for their data packets. To support this capability, two\n things are required:\n\n - Individual network elements (subnets and IP routers) along the\n path followed by an application's data packets must support\n mechanisms to control the quality of service delivered to those\n packets.\n\n - A way to communicate the application's requirements to network\n elements along the path and to convey QoS management information\n be","scope_keywords":["2210","authentication","delivery","management","path","policy","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2205","folder":"IETF/RFC-2205","source":"IETF/RFC-2205/RFC-2205.txt","version":null},{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2211","folder":"IETF/RFC-2211","source":"IETF/RFC-2211/RFC-2211.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2724","folder":"IETF/RFC-2724","source":"IETF/RFC-2724/RFC-2724.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null}],"search_text":"IETF RFC 2210 This note describes the use of the RSVP resource reservation protocol\n with the Controlled-Load and Guaranteed QoS control services. The\n RSVP protocol defines several data objects which carry resource\n reservation information but are opaque to RSVP itself. The usage and\n data format of those objects is given here.\n\n1. Introduction\n\n The Internet integrated services framework provides the ability for\n applications to choose among multiple, controlled levels of delivery\n service for their data packets. To support this capability, two\n things are required:\n\n - Individual network elements (subnets and IP routers) along the\n path followed by an application's data packets must support\n mechanisms to control the quality of service delivered to those\n packets.\n\n - A way to communicate the application's requirements to network\n elements along the path and to convey QoS management information\n be 2210 authentication delivery management path policy tsp nested-reference unchanged"},{"id":"IETF RFC 2215","type":"specification","body":"IETF","designation":"RFC 2215","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2215.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2215.txt","https://www.rfc-editor.org/rfc/rfc2215.pdf"],"folder":"IETF/RFC-2215","files":{"txt":{"path":"standards/IETF/RFC-2215/RFC-2215.txt","sha256":"d5f2c9281b82849f7407b1afe83ff3b6b55ca59b9d0ffb565b114031cbfdda87"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of general control and characterization\n parameters for network elements supporting the IETF integrated\n services QoS control framework. General parameters are those with\n common, shared definitions across all QoS control services.\n\n1. Introduction\n\n This memo defines the set of general control and characterization\n parameters used by network elements supporting the integrated\n services framework. \"General\" means that the parameter has a common\n definition and shared meaning across all QoS control services.\n\n Control parameters are used by applications to provide information to\n the network related to QoS control requests. An example is the\n traffic specification (TSpec) generated by application senders and\n receivers.\n\n Characterization parameters are used to discover or characterize the\n QoS management environment along the path of a packet flow requesting\n acti","scope_keywords":["2215","management","path","presentation","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2211","folder":"IETF/RFC-2211","source":"IETF/RFC-2211/RFC-2211.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 2215 This memo defines a set of general control and characterization\n parameters for network elements supporting the IETF integrated\n services QoS control framework. General parameters are those with\n common, shared definitions across all QoS control services.\n\n1. Introduction\n\n This memo defines the set of general control and characterization\n parameters used by network elements supporting the integrated\n services framework. \"General\" means that the parameter has a common\n definition and shared meaning across all QoS control services.\n\n Control parameters are used by applications to provide information to\n the network related to QoS control requests. An example is the\n traffic specification (TSpec) generated by application senders and\n receivers.\n\n Characterization parameters are used to discover or characterize the\n QoS management environment along the path of a packet flow requesting\n acti 2215 management path presentation tsp nested-reference unchanged"},{"id":"IETF RFC 3955","type":"specification","body":"IETF","designation":"RFC 3955","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3955.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3955.txt","https://www.rfc-editor.org/rfc/rfc3955.pdf"],"folder":"IETF/RFC-3955","files":{"txt":{"path":"standards/IETF/RFC-3955/RFC-3955.txt","sha256":"66f841ed90ffa871b6f7e6ba1b2e2de88e268b5af19af2a169e68b3a1d9637cc"}},"tags":["nested-reference","unchanged"],"summary":"This document contains an evaluation of the five candidate protocols\n for an IP Flow Information Export (IPFIX) protocol, based on the\n requirements document produced by the IPFIX Working Group. The\n protocols are characterized and grouped in broad categories, and\n evaluated against specific requirements. Finally, a recommendation\n is made to select the NetFlow v9 protocol as the basis for the IPFIX\n specification.","scope_keywords":["3955","authentication","authorization","key","keys","presentation","timestamp","timestamps","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null}],"search_text":"IETF RFC 3955 This document contains an evaluation of the five candidate protocols\n for an IP Flow Information Export (IPFIX) protocol, based on the\n requirements document produced by the IPFIX Working Group. The\n protocols are characterized and grouped in broad categories, and\n evaluated against specific requirements. Finally, a recommendation\n is made to select the NetFlow v9 protocol as the basis for the IPFIX\n specification. 3955 authentication authorization key keys presentation timestamp timestamps tls nested-reference unchanged"},{"id":"IETF RFC 5665","type":"specification","body":"IETF","designation":"RFC 5665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5665.txt","https://www.rfc-editor.org/rfc/rfc5665.pdf"],"folder":"IETF/RFC-5665","files":{"txt":{"path":"standards/IETF/RFC-5665/RFC-5665.txt","sha256":"44513451970ae260f1ee44bdf24e684f776a54531a4517547ccc7ca7260c3626"}},"tags":["nested-reference","unchanged"],"summary":"This document lists IANA Considerations for Remote Procedure Call\n (RPC) Network Identifiers (netids) and RPC Universal Network\n Addresses (uaddrs). This document updates, but does not replace, RFC\n 1833.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5665.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["5665","http","key","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 5665 This document lists IANA Considerations for Remote Procedure Call\n (RPC) Network Identifiers (netids) and RPC Universal Network\n Addresses (uaddrs). This document updates, but does not replace, RFC\n 1833.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5665.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  5665 http key license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1913","type":"specification","body":"IETF","designation":"RFC 1913","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1913.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1913.txt","https://www.rfc-editor.org/rfc/rfc1913.pdf"],"folder":"IETF/RFC-1913","files":{"txt":{"path":"standards/IETF/RFC-1913/RFC-1913.txt","sha256":"f6fa6ce632dc44c8af2faab77446e35cff8c7675278ab0bab14613dfc5e0dfd6"}},"tags":["nested-reference","unchanged"],"summary":"The authors describe an architecture for indexing in distributed\n databases, and apply this to the WHOIS++ protocol.\n\n1. Purpose:\n\n The WHOIS++ directory service [Deutsch, et al, 1995] is intended to\n provide a simple, extensible directory service predicated on a\n template-based information model and a flexible query language. This\n document describes a general architecture designed for indexing\n distributed databases, and then applys that architecture to link\n together many of these WHOIS++ servers into a distributed, searchable\n wide area directory service.\n\n2. Scope:\n\n This document details a distributed, easily maintained architecture\n for providing a unified index to a large number of distributed\n WHOIS++ servers. This architecture can be used with systems other\n than WHOIS++ to provide a distributed directory service which is also\n searchable.\n\n3. Motivation and Introduction:\n\n It ","scope_keywords":["1913","algorithm","algorithms","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1914","folder":"IETF/RFC-1914","source":"IETF/RFC-1914/RFC-1914.txt","version":null},{"body":"IETF","designation":"RFC 2651","folder":"IETF/RFC-2651","source":"IETF/RFC-2651/RFC-2651.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1913 The authors describe an architecture for indexing in distributed\n databases, and apply this to the WHOIS++ protocol.\n\n1. Purpose:\n\n The WHOIS++ directory service [Deutsch, et al, 1995] is intended to\n provide a simple, extensible directory service predicated on a\n template-based information model and a flexible query language. This\n document describes a general architecture designed for indexing\n distributed databases, and then applys that architecture to link\n together many of these WHOIS++ servers into a distributed, searchable\n wide area directory service.\n\n2. Scope:\n\n This document details a distributed, easily maintained architecture\n for providing a unified index to a large number of distributed\n WHOIS++ servers. This architecture can be used with systems other\n than WHOIS++ to provide a distributed directory service which is also\n searchable.\n\n3. Motivation and Introduction:\n\n It  1913 algorithm algorithms attribute attributes nested-reference unchanged"},{"id":"IETF RFC 1914","type":"specification","body":"IETF","designation":"RFC 1914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1914.txt","https://www.rfc-editor.org/rfc/rfc1914.pdf"],"folder":"IETF/RFC-1914","files":{"txt":{"path":"standards/IETF/RFC-1914/RFC-1914.txt","sha256":"b3088f3d0cb57e71b071580e720a7f57cb32036274a6dc150ec9691a57f5bbbb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Faltstrom\nRequest for Comments: 1914 Bunyip Information Systems, Inc.\nCategory: Standards Track R. Schoultz\n KTHNOC\n C. Weider\n Bunyip Information Systems, Inc.\n February 1996\n\n How to Interact with a Whois++ Mesh\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is\n done by the client, since each server 'refers' the client to the next\n appropriate server(s). The protocol is simple. The client opens a\n connection to a server, sends a query, receives a reply, closes the\n conne","scope_keywords":["1914","algorithm","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1913","folder":"IETF/RFC-1913","source":"IETF/RFC-1913/RFC-1913.txt","version":null},{"body":"IETF","designation":"RFC 2651","folder":"IETF/RFC-2651","source":"IETF/RFC-2651/RFC-2651.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 1914 Network Working Group P. Faltstrom\nRequest for Comments: 1914 Bunyip Information Systems, Inc.\nCategory: Standards Track R. Schoultz\n KTHNOC\n C. Weider\n Bunyip Information Systems, Inc.\n February 1996\n\n How to Interact with a Whois++ Mesh\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is\n done by the client, since each server 'refers' the client to the next\n appropriate server(s). The protocol is simple. The client opens a\n connection to a server, sends a query, receives a reply, closes the\n conne 1914 algorithm pid nested-reference unchanged"},{"id":"IETF RFC 1843","type":"specification","body":"IETF","designation":"RFC 1843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1843.txt","https://www.rfc-editor.org/rfc/rfc1843.pdf"],"folder":"IETF/RFC-1843","files":{"txt":{"path":"standards/IETF/RFC-1843/RFC-1843.txt","sha256":"8ce2714015c4c18255ccd961d9eaa0a24ab31fd18fce61f35d2ad95c4a504113"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Lee\nRequest for Comments: 1843 Stanford University\nCategory: Informational August 1995\n\n HZ - A Data Format for Exchanging Files of\n Arbitrarily Mixed Chinese and ASCII characters\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The content of this memo is identical to an article of the same title\n written by the author on September 4, 1989. In this memo, GB stands\n for GB2312-80. Note that the title is kept only for historical\n reasons. HZ has been widely used for purposes other than \"file\n exchange\".\n\n1. Introduction\n\n Most existing computer systems which can handle a text file of\n arbitrarily mixed Chinese and ASCII characters use 8-bit codes. To\n exchange such text files through electronic mail on ASCII computer\n ","scope_keywords":["1843"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 1843 Network Working Group F. Lee\nRequest for Comments: 1843 Stanford University\nCategory: Informational August 1995\n\n HZ - A Data Format for Exchanging Files of\n Arbitrarily Mixed Chinese and ASCII characters\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The content of this memo is identical to an article of the same title\n written by the author on September 4, 1989. In this memo, GB stands\n for GB2312-80. Note that the title is kept only for historical\n reasons. HZ has been widely used for purposes other than \"file\n exchange\".\n\n1. Introduction\n\n Most existing computer systems which can handle a text file of\n arbitrarily mixed Chinese and ASCII characters use 8-bit codes. To\n exchange such text files through electronic mail on ASCII computer\n  1843 nested-reference unchanged"},{"id":"IETF RFC 6409","type":"specification","body":"IETF","designation":"RFC 6409","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6409.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6409.txt","https://www.rfc-editor.org/rfc/rfc6409.pdf"],"folder":"IETF/RFC-6409","files":{"txt":{"path":"standards/IETF/RFC-6409/RFC-6409.txt","sha256":"66ed4284fbd7bdc47aa1896f2898204111a09f83061cf02ebeb056961fb9cadf"}},"tags":["nested-reference","unchanged"],"summary":"This memo splits message submission from message relay, allowing each\n service to operate according to its own rules (for security, policy,\n etc.), and specifies what actions are to be taken by a submission\n server.\n\n Message relay is unaffected, and continues to use SMTP over port 25.\n\n When conforming to this document, message submission uses the\n protocol specified here, normally over port 587.\n\n This separation of function offers a number of benefits, including\n the ability to apply specific security or policy requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av","scope_keywords":["6409","authentication","authorization","http","identification","license","path","policy","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6409 This memo splits message submission from message relay, allowing each\n service to operate according to its own rules (for security, policy,\n etc.), and specifies what actions are to be taken by a submission\n server.\n\n Message relay is unaffected, and continues to use SMTP over port 25.\n\n When conforming to this document, message submission uses the\n protocol specified here, normally over port 587.\n\n This separation of function offers a number of benefits, including\n the ability to apply specific security or policy requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av 6409 authentication authorization http identification license path policy qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 2015","type":"specification","body":"IETF","designation":"RFC 2015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2015.txt","https://www.rfc-editor.org/rfc/rfc2015.pdf"],"folder":"IETF/RFC-2015","files":{"txt":{"path":"standards/IETF/RFC-2015/RFC-2015.txt","sha256":"88e048c797b685653fca11fa54a114220110deada35ff1a55cef67c8eca73a66"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how Pretty Good Privacy (PGP) can be used to\n provide privacy and authentication using the Multipurpose Internet\n Mail Extensions (MIME) security content types described in RFC1847.\n\n1. Introduction\n\n Previous work on integrating PGP with MIME (including the since\n withdrawn application/pgp content type) has suffered from a number of\n problems, the most significant of which is the inability to recover\n signed message bodies without parsing data structures specific to\n PGP. This work makes use of the elegant solution proposed in\n RFC1847, which defines security multipart formats for MIME. The\n security multiparts clearly separate the signed message body from the\n signature, and have a number of other desirable properties. This\n document is styled after RFC 1848, which defines MIME Object Security\n Services (MOSS) for providing security and authentication.\n\n This do","scope_keywords":["2015","algorithm","authentication","encryption","hash","key","keys","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null}],"search_text":"IETF RFC 2015 This document describes how Pretty Good Privacy (PGP) can be used to\n provide privacy and authentication using the Multipurpose Internet\n Mail Extensions (MIME) security content types described in RFC1847.\n\n1. Introduction\n\n Previous work on integrating PGP with MIME (including the since\n withdrawn application/pgp content type) has suffered from a number of\n problems, the most significant of which is the inability to recover\n signed message bodies without parsing data structures specific to\n PGP. This work makes use of the elegant solution proposed in\n RFC1847, which defines security multipart formats for MIME. The\n security multiparts clearly separate the signed message body from the\n signature, and have a number of other desirable properties. This\n document is styled after RFC 1848, which defines MIME Object Security\n Services (MOSS) for providing security and authentication.\n\n This do 2015 algorithm authentication encryption hash key keys signature nested-reference unchanged"},{"id":"IETF RFC 2447","type":"specification","body":"IETF","designation":"RFC 2447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2447.txt","https://www.rfc-editor.org/rfc/rfc2447.pdf"],"folder":"IETF/RFC-2447","files":{"txt":{"path":"standards/IETF/RFC-2447/RFC-2447.txt","sha256":"30452917338300acc2ee0b4315d1cea32edde9e9a1c6e25665fe9fe259f2ef4b"}},"tags":["nested-reference","unchanged"],"summary":"This document, [iMIP], specifies a binding from the iCalendar\n Transport-independent Interoperability Protocol (iTIP) to Internet\n email-based transports. Calendaring entries defined by the iCalendar\n Object Model [iCAL] are composed using constructs from [RFC-822],\n [RFC-2045], [RFC-2046], [RFC-2047], [RFC-2048] and [RFC-2049].\n\n This document is based on discussions within the Internet Engineering\n Task Force (IETF) Calendaring and Scheduling (CALSCH) working group.\n More information about the IETF CALSCH working group activities can\n be found on the IMC web site at http://www.imc.org, the IETF web site\n at http://www.ietf.org/html.charters/calsch-charter.html. Refer to\n the references within this document for further information on how to\n access these various documents.\n\nDawson, et. al. Standards Track [Page 1]\n\f\nRFC 2447 iMIP November 1998","scope_keywords":["2447","authentication","authorization","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2446","folder":"IETF/RFC-2446","source":"IETF/RFC-2446/RFC-2446.txt","version":null},{"body":"IETF","designation":"RFC 2739","folder":"IETF/RFC-2739","source":"IETF/RFC-2739/RFC-2739.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null}],"search_text":"IETF RFC 2447 This document, [iMIP], specifies a binding from the iCalendar\n Transport-independent Interoperability Protocol (iTIP) to Internet\n email-based transports. Calendaring entries defined by the iCalendar\n Object Model [iCAL] are composed using constructs from [RFC-822],\n [RFC-2045], [RFC-2046], [RFC-2047], [RFC-2048] and [RFC-2049].\n\n This document is based on discussions within the Internet Engineering\n Task Force (IETF) Calendaring and Scheduling (CALSCH) working group.\n More information about the IETF CALSCH working group activities can\n be found on the IMC web site at http://www.imc.org, the IETF web site\n at http://www.ietf.org/html.charters/calsch-charter.html. Refer to\n the references within this document for further information on how to\n access these various documents.\n\nDawson, et. al. Standards Track [Page 1]\n\f\nRFC 2447 iMIP November 1998 2447 authentication authorization http key nested-reference unchanged"},{"id":"IETF RFC 2649","type":"specification","body":"IETF","designation":"RFC 2649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2649.txt","https://www.rfc-editor.org/rfc/rfc2649.pdf"],"folder":"IETF/RFC-2649","files":{"txt":{"path":"standards/IETF/RFC-2649/RFC-2649.txt","sha256":"87b6de04d7ff6a1c9b9aa74a1bc42e4106ff606a965dd91b8612388c3359535a"}},"tags":["nested-reference","unchanged"],"summary":"In many environments clients require the ability to validiate the\n source and integrity of information provided by the directory. This\n document describes an LDAP message control which allows for the\n retrieval of digitally signed information. This document defines an\n LDAP v3 based mechanism for signing directory operations in order to\n create a secure journal of changes that have been made to each\n directory entry. Both client and server based signatures are\n supported. An object class for subsequent retrieval are \"journal\n entries\" is also defined. This document specifies LDAP v3 controls\n that enable this functionality. It also defines an LDAP v3 schema\n that allows for subsequent browsing of the journal information.","scope_keywords":["2649","attribute","attributes","audit","certificate","key","policies","signature","signatures","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2649 In many environments clients require the ability to validiate the\n source and integrity of information provided by the directory. This\n document describes an LDAP message control which allows for the\n retrieval of digitally signed information. This document defines an\n LDAP v3 based mechanism for signing directory operations in order to\n create a secure journal of changes that have been made to each\n directory entry. Both client and server based signatures are\n supported. An object class for subsequent retrieval are \"journal\n entries\" is also defined. This document specifies LDAP v3 controls\n that enable this functionality. It also defines an LDAP v3 schema\n that allows for subsequent browsing of the journal information. 2649 attribute attributes audit certificate key policies signature signatures tls trust nested-reference unchanged"},{"id":"IETF RFC 2653","type":"specification","body":"IETF","designation":"RFC 2653","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2653.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2653.txt","https://www.rfc-editor.org/rfc/rfc2653.pdf"],"folder":"IETF/RFC-2653","files":{"txt":{"path":"standards/IETF/RFC-2653/RFC-2653.txt","sha256":"2da578e9726a77ca45abeeeb24088ebb5f8b8f0126b25c863bb4495f7aa5b062"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies three protocols for transporting CIP\n requests, responses and index objects, utilizing TCP, mail, and HTTP.\n The objects themselves are defined in [CIP-MIME] and the overall CIP\n architecture is defined in [CIP-ARCH].\n\n1. Protocol\n\n In this section, the actual protocol for transmitting CIP index\n objects and maintaining the mesh is presented. While companion\n documents ([CIP-ARCH] and [CIP-MIME]) describe the concepts involved\n and the formats of the CIP MIME objects, this document is the\n authoritative definition of the message formats and transfer\n mechanisms of CIP used over TCP, HTTP and mail.","scope_keywords":["2653","crl","http","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2651","folder":"IETF/RFC-2651","source":"IETF/RFC-2651/RFC-2651.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2653 This document specifies three protocols for transporting CIP\n requests, responses and index objects, utilizing TCP, mail, and HTTP.\n The objects themselves are defined in [CIP-MIME] and the overall CIP\n architecture is defined in [CIP-ARCH].\n\n1. Protocol\n\n In this section, the actual protocol for transmitting CIP index\n objects and maintaining the mesh is presented. While companion\n documents ([CIP-ARCH] and [CIP-MIME]) describe the concepts involved\n and the formats of the CIP MIME objects, this document is the\n authoritative definition of the message formats and transfer\n mechanisms of CIP used over TCP, HTTP and mail. 2653 crl http key registered nested-reference unchanged"},{"id":"IETF RFC 3156","type":"specification","body":"IETF","designation":"RFC 3156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3156.txt","https://www.rfc-editor.org/rfc/rfc3156.pdf"],"folder":"IETF/RFC-3156","files":{"txt":{"path":"standards/IETF/RFC-3156/RFC-3156.txt","sha256":"ca68d1b7755dfea2672aeb7614e9c5153ce3accc296355d147afd243e44c3ae2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the OpenPGP Message Format can be used to\n provide privacy and authentication using the Multipurpose Internet\n Mail Extensions (MIME) security content types described in RFC 1847.\n\n1. Introduction\n\n Work on integrating PGP (Pretty Good Privacy) with MIME [3]\n (including the since withdrawn \"application/pgp\" content type) prior\n to RFC 2015 suffered from a number of problems, the most significant\n of which is the inability to recover signed message bodies without\n parsing data structures specific to PGP. RFC 2015 makes use of the\n elegant solution proposed in RFC 1847, which defines security\n multipart formats for MIME. The security multiparts clearly separate\n the signed message body from the signature, and have a number of\n other desirable properties. This document revises RFC 2015 to adopt\n the integration of PGP and MIME to the needs which emerged during th","scope_keywords":["3156","authentication","delivery","encryption","hash","key","keys","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null}],"search_text":"IETF RFC 3156 This document describes how the OpenPGP Message Format can be used to\n provide privacy and authentication using the Multipurpose Internet\n Mail Extensions (MIME) security content types described in RFC 1847.\n\n1. Introduction\n\n Work on integrating PGP (Pretty Good Privacy) with MIME [3]\n (including the since withdrawn \"application/pgp\" content type) prior\n to RFC 2015 suffered from a number of problems, the most significant\n of which is the inability to recover signed message bodies without\n parsing data structures specific to PGP. RFC 2015 makes use of the\n elegant solution proposed in RFC 1847, which defines security\n multipart formats for MIME. The security multiparts clearly separate\n the signed message body from the signature, and have a number of\n other desirable properties. This document revises RFC 2015 to adopt\n the integration of PGP and MIME to the needs which emerged during th 3156 authentication delivery encryption hash key keys signature nested-reference unchanged"},{"id":"IETF RFC 3459","type":"specification","body":"IETF","designation":"RFC 3459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3459.txt","https://www.rfc-editor.org/rfc/rfc3459.pdf"],"folder":"IETF/RFC-3459","files":{"txt":{"path":"standards/IETF/RFC-3459/RFC-3459.txt","sha256":"7fae6a3f9452003618720310f36cd5133dac74f18e4b8f27cccea325f34cea28"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of a mechanism for identifying body\n parts that a sender deems critical in a multi-part Internet mail\n message. The mechanism described is a parameter to Content-\n Disposition, as described by RFC 3204.\n\n By knowing what parts of a message the sender deems critical, a\n content gateway can intelligently handle multi-part messages when\n providing gateway services to systems of lesser capability. Critical\n content can help a content gateway to decide what parts to forward.\n It can indicate how hard a gateway should try to deliver a body part.\n It can help the gateway to pick body parts that are safe to silently\n delete when a system of lesser capability receives a message. In\n addition, critical content can help the gateway chose the\n notification strategy for the receiving system. Likewise, if the\n sender expects the destination to do some processing on a bo","scope_keywords":["3459","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null}],"search_text":"IETF RFC 3459 This document describes the use of a mechanism for identifying body\n parts that a sender deems critical in a multi-part Internet mail\n message. The mechanism described is a parameter to Content-\n Disposition, as described by RFC 3204.\n\n By knowing what parts of a message the sender deems critical, a\n content gateway can intelligently handle multi-part messages when\n providing gateway services to systems of lesser capability. Critical\n content can help a content gateway to decide what parts to forward.\n It can indicate how hard a gateway should try to deliver a body part.\n It can help the gateway to pick body parts that are safe to silently\n delete when a system of lesser capability receives a message. In\n addition, critical content can help the gateway chose the\n notification strategy for the receiving system. Likewise, if the\n sender expects the destination to do some processing on a bo 3459 delivery key nested-reference unchanged"},{"id":"IETF RFC 3862","type":"specification","body":"IETF","designation":"RFC 3862","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3862.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3862.txt","https://www.rfc-editor.org/rfc/rfc3862.pdf"],"folder":"IETF/RFC-3862","files":{"txt":{"path":"standards/IETF/RFC-3862/RFC-3862.txt","sha256":"cea2e353fcb91b6970e8d53527202fcde02aca05ab56b46018c8f3dc6cff273c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the MIME content type 'Message/CPIM', a message\n format for protocols that conform to the Common Profile for Instant\n Messaging (CPIM) specification.\n\nKlyne & Atkins Standards Track [Page 1]\n\f\nRFC 3862 CPIM: Message Format August 2004","scope_keywords":["3862","encryption","profile","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 3862 This memo defines the MIME content type 'Message/CPIM', a message\n format for protocols that conform to the Common Profile for Instant\n Messaging (CPIM) specification.\n\nKlyne & Atkins Standards Track [Page 1]\n\f\nRFC 3862 CPIM: Message Format August 2004 3862 encryption profile signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 3923","type":"specification","body":"IETF","designation":"RFC 3923","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3923.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3923.txt","https://www.rfc-editor.org/rfc/rfc3923.pdf"],"folder":"IETF/RFC-3923","files":{"txt":{"path":"standards/IETF/RFC-3923/RFC-3923.txt","sha256":"677633f9749ca3be4e3a96ac45d4767ff40c42471cfa4b05513b173d23c89719"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines methods of end-to-end signing and object encryption\n for the Extensible Messaging and Presence Protocol (XMPP).","scope_keywords":["3923","algorithm","algorithms","encryption","key","pid","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 3923 This memo defines methods of end-to-end signing and object encryption\n for the Extensible Messaging and Presence Protocol (XMPP). 3923 algorithm algorithms encryption key pid signature signatures nested-reference unchanged"},{"id":"IETF RFC 4210","type":"specification","body":"IETF","designation":"RFC 4210","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4210.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4210.txt","https://www.rfc-editor.org/rfc/rfc4210.pdf"],"folder":"IETF/RFC-4210","files":{"txt":{"path":"standards/IETF/RFC-4210/RFC-4210.txt","sha256":"64210d97dd49cf49aef3b46155afec8144d3e92c231cf7cc3afbd29f1d62501d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Internet X.509 Public Key Infrastructure\n (PKI) Certificate Management Protocol (CMP). Protocol messages are\n defined for X.509v3 certificate creation and management. CMP\n provides on-line interactions between PKI components, including an\n exchange between a Certification Authority (CA) and a client system.","scope_keywords":["4210","algorithm","authentication","certificate","certificates","crl","encryption","identification","key","keys","management","pki","revocation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 4210 This document describes the Internet X.509 Public Key Infrastructure\n (PKI) Certificate Management Protocol (CMP). Protocol messages are\n defined for X.509v3 certificate creation and management. CMP\n provides on-line interactions between PKI components, including an\n exchange between a Certification Authority (CA) and a client system. 4210 algorithm authentication certificate certificates crl encryption identification key keys management pki revocation signature subject nested-reference unchanged"},{"id":"IETF RFC 4662","type":"specification","body":"IETF","designation":"RFC 4662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4662.txt","https://www.rfc-editor.org/rfc/rfc4662.pdf"],"folder":"IETF/RFC-4662","files":{"txt":{"path":"standards/IETF/RFC-4662/RFC-4662.txt","sha256":"c5a4d310f0243f3e0fab4ff2373a87d55fc3580ff85c6d603a9b70310ccb9801"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an extension to the Session Initiation\n Protocol (SIP)-Specific Event Notification mechanism for subscribing\n to a homogeneous list of resources. Instead of sending a SUBSCRIBE\n for each resource individually, the subscriber can subscribe to an\n entire list and then receive notifications when the state of any of\n the resources in the list changes.\n\nRoach, et al. Standards Track [Page 1]\n\f\nRFC 4662 SIP Event Lists August 2006","scope_keywords":["4662","attribute","attributes","authentication","key","pid","risk","seal","sealing"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null}],"search_text":"IETF RFC 4662 This document presents an extension to the Session Initiation\n Protocol (SIP)-Specific Event Notification mechanism for subscribing\n to a homogeneous list of resources. Instead of sending a SUBSCRIBE\n for each resource individually, the subscriber can subscribe to an\n entire list and then receive notifications when the state of any of\n the resources in the list changes.\n\nRoach, et al. Standards Track [Page 1]\n\f\nRFC 4662 SIP Event Lists August 2006 4662 attribute attributes authentication key pid risk seal sealing nested-reference unchanged"},{"id":"IETF RFC 4871","type":"specification","body":"IETF","designation":"RFC 4871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4871.txt","https://www.rfc-editor.org/rfc/rfc4871.pdf"],"folder":"IETF/RFC-4871","files":{"txt":{"path":"standards/IETF/RFC-4871/RFC-4871.txt","sha256":"b68ad89b758a4e335c260b59fb1e6de295e9e8df941b3ce2ab258d0fbc85662e"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) defines a domain-level\n authentication framework for email using public-key cryptography and\n key server technology to permit verification of the source and\n contents of messages by either Mail Transfer Agents (MTAs) or Mail\n User Agents (MUAs). The ultimate goal of this framework is to permit\n a signing domain to assert responsibility for a message, thus\n protecting message signer identity and the integrity of the messages\n they convey while retaining the functionality of Internet email as it\n is known today. Protection of email identity may assist in the\n global control of \"spam\" and \"phishing\".\n\nAllman, et al. Standards Track [Page 1]\n\f\nRFC 4871 DKIM Signatures May 2007","scope_keywords":["4871","algorithm","algorithms","authentication","delivery","hash","key","keys","management","policy","presentation","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 5016","folder":"IETF/RFC-5016","source":"IETF/RFC-5016/RFC-5016.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5672","folder":"IETF/RFC-5672","source":"IETF/RFC-5672/RFC-5672.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null}],"search_text":"IETF RFC 4871 DomainKeys Identified Mail (DKIM) defines a domain-level\n authentication framework for email using public-key cryptography and\n key server technology to permit verification of the source and\n contents of messages by either Mail Transfer Agents (MTAs) or Mail\n User Agents (MUAs). The ultimate goal of this framework is to permit\n a signing domain to assert responsibility for a message, thus\n protecting message signer identity and the integrity of the messages\n they convey while retaining the functionality of Internet email as it\n is known today. Protection of email identity may assist in the\n global control of \"spam\" and \"phishing\".\n\nAllman, et al. Standards Track [Page 1]\n\f\nRFC 4871 DKIM Signatures May 2007 4871 algorithm algorithms authentication delivery hash key keys management policy presentation signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 5751","type":"specification","body":"IETF","designation":"RFC 5751","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5751.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5751.txt","https://www.rfc-editor.org/rfc/rfc5751.pdf"],"folder":"IETF/RFC-5751","files":{"txt":{"path":"standards/IETF/RFC-5751/RFC-5751.txt","sha256":"86d5e52ba3618a8326a7b8d4eda9038071a0e90d1d58ef35136429b402ff8998"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 3.2. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 3851.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may b","scope_keywords":["5751","algorithm","attribute","attributes","authentication","certificate","encryption","http","key","license","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5756","folder":"IETF/RFC-5756","source":"IETF/RFC-5756/RFC-5756.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 5751 This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 3.2. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 3851.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may b 5751 algorithm attribute attributes authentication certificate encryption http key license management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8551","type":"specification","body":"IETF","designation":"RFC 8551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8551.txt","https://www.rfc-editor.org/rfc/rfc8551.pdf"],"folder":"IETF/RFC-8551","files":{"txt":{"path":"standards/IETF/RFC-8551/RFC-8551.txt","sha256":"dac39f749a08d3422bd78d4e492195067e7bc03f5fc2d0dac515f0d7ed884ae2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 4.0. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 5751.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be","scope_keywords":["8551","algorithm","attribute","attributes","authentication","certificate","encryption","http","https","key","license","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null}],"search_text":"IETF RFC 8551 This document defines Secure/Multipurpose Internet Mail Extensions\n (S/MIME) version 4.0. S/MIME provides a consistent way to send and\n receive secure MIME data. Digital signatures provide authentication,\n message integrity, and non-repudiation with proof of origin.\n Encryption provides data confidentiality. Compression can be used to\n reduce data size. This document obsoletes RFC 5751.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be 8551 algorithm attribute attributes authentication certificate encryption http https key license management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 2894","type":"specification","body":"IETF","designation":"RFC 2894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2894.txt","https://www.rfc-editor.org/rfc/rfc2894.pdf"],"folder":"IETF/RFC-2894","files":{"txt":{"path":"standards/IETF/RFC-2894/RFC-2894.txt","sha256":"084e2a609e4eae4e08ef03299fe0fc6c704ba576cc99cbaac44eadf9f1e55f14"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 Neighbor Discovery and Address Autoconfiguration conveniently\n make initial assignments of address prefixes to hosts. Aside from\n the problem of connection survival across a renumbering event, these\n two mechanisms also simplify the reconfiguration of hosts when the\n set of valid prefixes changes.\n\n This document defines a mechanism called Router Renumbering (\"RR\")\n which allows address prefixes on routers to be configured and\n reconfigured almost as easily as the combination of Neighbor\n Discovery and Address Autoconfiguration works for hosts. It provides\n a means for a network manager to make updates to the prefixes used by\n and advertised by IPv6 routers throughout a site.\n\nCrawford Standards Track [Page 1]\n\f\nRFC 2894 Router Renumbering for IPv6 August 2000","scope_keywords":["2894","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 2894 IPv6 Neighbor Discovery and Address Autoconfiguration conveniently\n make initial assignments of address prefixes to hosts. Aside from\n the problem of connection survival across a renumbering event, these\n two mechanisms also simplify the reconfiguration of hosts when the\n set of valid prefixes changes.\n\n This document defines a mechanism called Router Renumbering (\"RR\")\n which allows address prefixes on routers to be configured and\n reconfigured almost as easily as the combination of Neighbor\n Discovery and Address Autoconfiguration works for hosts. It provides\n a means for a network manager to make updates to the prefixes used by\n and advertised by IPv6 routers throughout a site.\n\nCrawford Standards Track [Page 1]\n\f\nRFC 2894 Router Renumbering for IPv6 August 2000 2894 management policy nested-reference unchanged"},{"id":"IETF RFC 5470","type":"specification","body":"IETF","designation":"RFC 5470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5470.txt","https://www.rfc-editor.org/rfc/rfc5470.pdf"],"folder":"IETF/RFC-5470","files":{"txt":{"path":"standards/IETF/RFC-5470/RFC-5470.txt","sha256":"954fe0fa7a7d553bbbad007041a43b5295afbdc50ce45cb4bff2fe34cd744baf"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the IP Flow Information eXport (IPFIX) architecture\n for the selective monitoring of IP Flows, and for the export of\n measured IP Flow information from an IPFIX Device to a Collector.\n\nSadasivan, et al. Informational [Page 1]\n\f\nRFC 5470 IPFIX Architecture March 2009","scope_keywords":["5470","authentication","encryption","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6985","folder":"IETF/RFC-6985","source":"IETF/RFC-6985/RFC-6985.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null}],"search_text":"IETF RFC 5470 This memo defines the IP Flow Information eXport (IPFIX) architecture\n for the selective monitoring of IP Flows, and for the export of\n measured IP Flow information from an IPFIX Device to a Collector.\n\nSadasivan, et al. Informational [Page 1]\n\f\nRFC 5470 IPFIX Architecture March 2009 5470 authentication encryption http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2487","type":"specification","body":"IETF","designation":"RFC 2487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2487.txt","https://www.rfc-editor.org/rfc/rfc2487.pdf"],"folder":"IETF/RFC-2487","files":{"txt":{"path":"standards/IETF/RFC-2487/RFC-2487.txt","sha256":"e86acec737939c92a564c1fa149794ca0c2791e6cb57b783d4cc8875856a9f34"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the SMTP service that allows\n an SMTP server and client to use transport-layer security to provide\n private, authenticated communication over the Internet. This gives\n SMTP agents the ability to protect some or all of their\n communications from eavesdroppers and attackers.\n\n2. Introduction\n\n SMTP [RFC-821] servers and clients normally communicate in the clear\n over the Internet. In many cases, this communication goes through one\n or more router that is not controlled or trusted by either entity.\n Such an untrusted router might allow a third party to monitor or\n alter the communications between the server and client.\n\n Further, there is often a desire for two SMTP agents to be able to\n authenticate each others' identities. For example, a secure SMTP\n server might only allow communications from other SMTP agents it\n knows, or it might act differently","scope_keywords":["2487","authentication","certificate","delivery","http","key","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null}],"search_text":"IETF RFC 2487 This document describes an extension to the SMTP service that allows\n an SMTP server and client to use transport-layer security to provide\n private, authenticated communication over the Internet. This gives\n SMTP agents the ability to protect some or all of their\n communications from eavesdroppers and attackers.\n\n2. Introduction\n\n SMTP [RFC-821] servers and clients normally communicate in the clear\n over the Internet. In many cases, this communication goes through one\n or more router that is not controlled or trusted by either entity.\n Such an untrusted router might allow a third party to monitor or\n alter the communications between the server and client.\n\n Further, there is often a desire for two SMTP agents to be able to\n authenticate each others' identities. For example, a secure SMTP\n server might only allow communications from other SMTP agents it\n knows, or it might act differently 2487 authentication certificate delivery http key tls trust nested-reference unchanged"},{"id":"IETF RFC 1858","type":"specification","body":"IETF","designation":"RFC 1858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1858.txt","https://www.rfc-editor.org/rfc/rfc1858.pdf"],"folder":"IETF/RFC-1858","files":{"txt":{"path":"standards/IETF/RFC-1858/RFC-1858.txt","sha256":"29f44b2153e734727882799fb476614b8f580c4627329b55966dfc510bcf8005"}},"tags":["nested-reference","unchanged"],"summary":"IP fragmentation can be used to disguise TCP packets from IP filters\n used in routers and hosts. This document describes two methods of\n attack as well as remedies to prevent them.\n\n1. Background\n\n System administrators rely on manufacturers of networking equipment\n to provide them with packet filters; these filters are used for\n keeping attackers from accessing private systems and information,\n while permitting friendly agents to transfer data between private\n nets and the Internet. For this reason, it is important for network\n equipment vendors to anticipate possible attacks against their\n equipment and to implement robust mechanisms to deflect such attacks.\n\n The growth of the global Internet has brought with it an increase in\n \"undesirable elements\" manifested in antisocial behavior. Recent\n months have seen the use of novel attacks on Internet hosts, which\n have in some cases led to","scope_keywords":["1858","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3128","folder":"IETF/RFC-3128","source":"IETF/RFC-3128/RFC-3128.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 5722","folder":"IETF/RFC-5722","source":"IETF/RFC-5722/RFC-5722.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 1858 IP fragmentation can be used to disguise TCP packets from IP filters\n used in routers and hosts. This document describes two methods of\n attack as well as remedies to prevent them.\n\n1. Background\n\n System administrators rely on manufacturers of networking equipment\n to provide them with packet filters; these filters are used for\n keeping attackers from accessing private systems and information,\n while permitting friendly agents to transfer data between private\n nets and the Internet. For this reason, it is important for network\n equipment vendors to anticipate possible attacks against their\n equipment and to implement robust mechanisms to deflect such attacks.\n\n The growth of the global Internet has brought with it an increase in\n \"undesirable elements\" manifested in antisocial behavior. Recent\n months have seen the use of novel attacks on Internet hosts, which\n have in some cases led to 1858 path nested-reference unchanged"},{"id":"IETF RFC 3128","type":"specification","body":"IETF","designation":"RFC 3128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3128.txt","https://www.rfc-editor.org/rfc/rfc3128.pdf"],"folder":"IETF/RFC-3128","files":{"txt":{"path":"standards/IETF/RFC-3128/RFC-3128.txt","sha256":"0e2bb17258b58a467ee5cf93a5b0828c85056f61ebdc67a5bd7d5a8dc00b9ec3"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how RFC 1858 compliant filters can be\n vulnerable to a variant of the \"Tiny Fragment Attack\" described in\n section 3.1 of the RFC. This document describes the attack and\n recommends corrective action.\n\n1. Introduction\n\n RFC 1858 provides an excellent description of a class of attack on\n Internet firewalls and proposes countermeasures. However one of\n these countmeasures, the \"Indirect Method\" (section 3.2.2) is\n vulnerable to a combination of two of the attacks described.\n\n The attack combines the features of the \"Tiny Fragment Attack\"\n (section 3) and the \"Overlapping Fragment Attack\" (section 4).","scope_keywords":["3128","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4459","folder":"IETF/RFC-4459","source":"IETF/RFC-4459/RFC-4459.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 3128 This document discusses how RFC 1858 compliant filters can be\n vulnerable to a variant of the \"Tiny Fragment Attack\" described in\n section 3.1 of the RFC. This document describes the attack and\n recommends corrective action.\n\n1. Introduction\n\n RFC 1858 provides an excellent description of a class of attack on\n Internet firewalls and proposes countermeasures. However one of\n these countmeasures, the \"Indirect Method\" (section 3.2.2) is\n vulnerable to a combination of two of the attacks described.\n\n The attack combines the features of the \"Tiny Fragment Attack\"\n (section 3) and the \"Overlapping Fragment Attack\" (section 4). 3128 policy nested-reference unchanged"},{"id":"IETF RFC 5722","type":"specification","body":"IETF","designation":"RFC 5722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5722.txt","https://www.rfc-editor.org/rfc/rfc5722.pdf"],"folder":"IETF/RFC-5722","files":{"txt":{"path":"standards/IETF/RFC-5722/RFC-5722.txt","sha256":"c92412b441d6abeb820b97d05536fd61c89904131273d8e08ec25be72e2bbb8f"}},"tags":["nested-reference","unchanged"],"summary":"The fragmentation and reassembly algorithm specified in the base IPv6\n specification allows fragments to overlap. This document\n demonstrates the security issues associated with allowing overlapping\n fragments and updates the IPv6 specification to explicitly forbid\n overlapping fragments.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.iet","scope_keywords":["5722","algorithm","http","identification","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 5722 The fragmentation and reassembly algorithm specified in the base IPv6\n specification allows fragments to overlap. This document\n demonstrates the security issues associated with allowing overlapping\n fragments and updates the IPv6 specification to explicitly forbid\n overlapping fragments.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.iet 5722 algorithm http identification key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 4223","type":"specification","body":"IETF","designation":"RFC 4223","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4223.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4223.txt","https://www.rfc-editor.org/rfc/rfc4223.pdf"],"folder":"IETF/RFC-4223","files":{"txt":{"path":"standards/IETF/RFC-4223/RFC-4223.txt","sha256":"25b94ea98c1b2d4c504d24bd2126b0f826751d2ee5e23b995c23879c10629910"}},"tags":["nested-reference","unchanged"],"summary":"This memo reclassifies RFC 1863, A BGP/IDRP Route Server alternative\n to a full mesh routing, to Historic status. This memo also obsoletes\n RFC 1863.\n\n1. Reclassification of RFC 1863 to Historic\n\n RFC 1863 [1] describes the use of route servers as an alternative to\n BGP/IDRP full mesh routing.\n\n In the context of this document, the term \"RFC 1863 route server\" is\n used to refer to a route server as specified in RFC 1863. Other uses\n of the term \"route server\" are outside the scope of this document.\n\n Implementations of RFC 1863 route servers do not exist and are not\n used as an alternative to full mesh routing. Therefore, RFC 1863 is\n reclassified to Historic status.\n\n Current techniques that serve as an alternative to full mesh routing\n include BGP Route Reflectors [2], BGP Confederedations [3], and the\n use of private AS numbers. IDRP for IP has never been standardized\n by the IETF and","scope_keywords":["4223","http","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"IETF RFC 4223 This memo reclassifies RFC 1863, A BGP/IDRP Route Server alternative\n to a full mesh routing, to Historic status. This memo also obsoletes\n RFC 1863.\n\n1. Reclassification of RFC 1863 to Historic\n\n RFC 1863 [1] describes the use of route servers as an alternative to\n BGP/IDRP full mesh routing.\n\n In the context of this document, the term \"RFC 1863 route server\" is\n used to refer to a route server as specified in RFC 1863. Other uses\n of the term \"route server\" are outside the scope of this document.\n\n Implementations of RFC 1863 route servers do not exist and are not\n used as an alternative to full mesh routing. Therefore, RFC 1863 is\n reclassified to Historic status.\n\n Current techniques that serve as an alternative to full mesh routing\n include BGP Route Reflectors [2], BGP Confederedations [3], and the\n use of private AS numbers. IDRP for IP has never been standardized\n by the IETF and 4223 http license subject nested-reference unchanged"},{"id":"IETF RFC 4456","type":"specification","body":"IETF","designation":"RFC 4456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4456.txt","https://www.rfc-editor.org/rfc/rfc4456.pdf"],"folder":"IETF/RFC-4456","files":{"txt":{"path":"standards/IETF/RFC-4456/RFC-4456.txt","sha256":"ac3789dd800e8ae8142a1afe85ca46a206698a180ef2b6e6cb0e761523d191d1"}},"tags":["nested-reference","unchanged"],"summary":"The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for TCP/IP internets. Typically, all BGP\n speakers within a single AS must be fully meshed so that any external\n routing information must be re-distributed to all other routers\n within that Autonomous System (AS). This represents a serious\n scaling problem that has been well documented with several\n alternatives proposed.\n\n This document describes the use and design of a method known as\n \"route reflection\" to alleviate the need for \"full mesh\" Internal BGP\n (IBGP).\n\n This document obsoletes RFC 2796 and RFC 1966.\n\nBates, et al. Standards Track [Page 1]\n\f\nRFC 4456 BGP Route Reflection April 2006","scope_keywords":["4456","attribute","attributes","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 4456 The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for TCP/IP internets. Typically, all BGP\n speakers within a single AS must be fully meshed so that any external\n routing information must be re-distributed to all other routers\n within that Autonomous System (AS). This represents a serious\n scaling problem that has been well documented with several\n alternatives proposed.\n\n This document describes the use and design of a method known as\n \"route reflection\" to alleviate the need for \"full mesh\" Internal BGP\n (IBGP).\n\n This document obsoletes RFC 2796 and RFC 1966.\n\nBates, et al. Standards Track [Page 1]\n\f\nRFC 4456 BGP Route Reflection April 2006 4456 attribute attributes key management path nested-reference unchanged"},{"id":"IETF RFC 5065","type":"specification","body":"IETF","designation":"RFC 5065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5065.txt","https://www.rfc-editor.org/rfc/rfc5065.pdf"],"folder":"IETF/RFC-5065","files":{"txt":{"path":"standards/IETF/RFC-5065/RFC-5065.txt","sha256":"6ab8048b216ce214c430841081498bfb654b44b34e211012d7682d8cbc42c917"}},"tags":["nested-reference","unchanged"],"summary":"The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for Transmission Control Protocol/Internet\n Protocol (TCP/IP) networks. BGP requires that all BGP speakers\n within a single autonomous system (AS) must be fully meshed. This\n represents a serious scaling problem that has been well documented in\n a number of proposals.\n\n This document describes an extension to BGP that may be used to\n create a confederation of autonomous systems that is represented as a\n single autonomous system to BGP peers external to the confederation,\n thereby removing the \"full mesh\" requirement. The intention of this\n extension is to aid in policy administration and reduce the\n management complexity of maintaining a large autonomous system.\n\n This document obsoletes RFC 3065.\n\nTraina, et al. Standards Track [Page 1]\n\f\nRFC 5065 August 2007","scope_keywords":["5065","attribute","key","management","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null}],"search_text":"IETF RFC 5065 The Border Gateway Protocol (BGP) is an inter-autonomous system\n routing protocol designed for Transmission Control Protocol/Internet\n Protocol (TCP/IP) networks. BGP requires that all BGP speakers\n within a single autonomous system (AS) must be fully meshed. This\n represents a serious scaling problem that has been well documented in\n a number of proposals.\n\n This document describes an extension to BGP that may be used to\n create a confederation of autonomous systems that is represented as a\n single autonomous system to BGP peers external to the confederation,\n thereby removing the \"full mesh\" requirement. The intention of this\n extension is to aid in policy administration and reduce the\n management complexity of maintaining a large autonomous system.\n\n This document obsoletes RFC 3065.\n\nTraina, et al. Standards Track [Page 1]\n\f\nRFC 5065 August 2007 5065 attribute key management path policy trust nested-reference unchanged"},{"id":"IETF RFC 2397","type":"specification","body":"IETF","designation":"RFC 2397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2397.txt","https://www.rfc-editor.org/rfc/rfc2397.pdf"],"folder":"IETF/RFC-2397","files":{"txt":{"path":"standards/IETF/RFC-2397/RFC-2397.txt","sha256":"17fe861cb0fea6b96948cf985cfb4df052d9d26c02d804a1a922b862c74657bf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Masinter\nRequest for Comments: 2397 Xerox Corporation\nCategory: Standards Track August 1998\n\n The \"data\" URL scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n A new URL scheme, \"data\", is defined. It allows inclusion of small\n data items as \"immediate\" data, as if it had been included\n externally.\n\n2. Description\n\n Some applications that use URLs also have a need to embed (small)\n media type data directly inline. This document defines a new URL\n scheme","scope_keywords":["2397","attribute","presentation","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 2397 Network Working Group L. Masinter\nRequest for Comments: 2397 Xerox Corporation\nCategory: Standards Track August 1998\n\n The \"data\" URL scheme\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n A new URL scheme, \"data\", is defined. It allows inclusion of small\n data items as \"immediate\" data, as if it had been included\n externally.\n\n2. Description\n\n Some applications that use URLs also have a need to embed (small)\n media type data directly inline. This document defines a new URL\n scheme 2397 attribute presentation tsp nested-reference unchanged"},{"id":"IETF RFC 2646","type":"specification","body":"IETF","designation":"RFC 2646","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2646.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2646.txt","https://www.rfc-editor.org/rfc/rfc2646.pdf"],"folder":"IETF/RFC-2646","files":{"txt":{"path":"standards/IETF/RFC-2646/RFC-2646.txt","sha256":"17745cef025e707f26a478174b8272cad123f1441c27899f8035ef2bdae08597"}},"tags":["nested-reference","unchanged"],"summary":"Interoperability problems have been observed with erroneous labelling\n of paragraph text as Text/Plain, and with various forms of\n \"embarrassing line wrap.\" (See section 3.)\n\n Attempts to deploy new media types, such as Text/Enriched [RICH] and\n Text/HTML [HTML] have suffered from a lack of backwards compatibility\n and an often hostile user reaction at the receiving end.\n\n What is required is a format which is in all significant ways\n Text/Plain, and therefore is quite suitable for display as\n Text/Plain, and yet allows the sender to express to the receiver\n which lines can be considered a logical paragraph, and thus flowed\n (wrapped and joined) as appropriate.\n\n This memo proposes a new parameter to be used with Text/Plain, and,\n in the presence of this parameter, the use of trailing whitespace to\n indicate flowed lines. This results in an encoding which appears as\n normal Text/Plain in","scope_keywords":["2646","crl","encryption","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3803","folder":"IETF/RFC-3803","source":"IETF/RFC-3803/RFC-3803.txt","version":null}],"search_text":"IETF RFC 2646 Interoperability problems have been observed with erroneous labelling\n of paragraph text as Text/Plain, and with various forms of\n \"embarrassing line wrap.\" (See section 3.)\n\n Attempts to deploy new media types, such as Text/Enriched [RICH] and\n Text/HTML [HTML] have suffered from a lack of backwards compatibility\n and an often hostile user reaction at the receiving end.\n\n What is required is a format which is in all significant ways\n Text/Plain, and therefore is quite suitable for display as\n Text/Plain, and yet allows the sender to express to the receiver\n which lines can be considered a logical paragraph, and thus flowed\n (wrapped and joined) as appropriate.\n\n This memo proposes a new parameter to be used with Text/Plain, and,\n in the presence of this parameter, the use of trailing whitespace to\n indicate flowed lines. This results in an encoding which appears as\n normal Text/Plain in 2646 crl encryption key signature signatures nested-reference unchanged"},{"id":"IETF RFC 2854","type":"specification","body":"IETF","designation":"RFC 2854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2854.txt","https://www.rfc-editor.org/rfc/rfc2854.pdf"],"folder":"IETF/RFC-2854","files":{"txt":{"path":"standards/IETF/RFC-2854/RFC-2854.txt","sha256":"c9de3a668e2f7582b9ad4eea49b9494e1e7a0f18772758e9b92073a8c549831b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Connolly\nRequest for Comments: 2854 World Wide Web Consortium (W3C)\nObsoletes: 2070, 1980, 1942, 1867, 1866 L. Masinter\nCategory: Informational AT&T\n June 2000\n\n The 'text/html' Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document summarizes the history of HTML development, and defines\n the \"text/html\" MIME type by pointing to the relevant W3C\n recommendations; it is intended to obsolete the previous IETF\n documents defining HTML, including RFC 1866, RFC 1867, RFC 1980, RFC\n 1942 and RFC 2070, and to remove HTML from IETF Standards Track.\n\n This document was prepared at the request of the W3C HTML working\n group. Please s","scope_keywords":["2854","attribute","http","presentation","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null}],"search_text":"IETF RFC 2854 Network Working Group D. Connolly\nRequest for Comments: 2854 World Wide Web Consortium (W3C)\nObsoletes: 2070, 1980, 1942, 1867, 1866 L. Masinter\nCategory: Informational AT&T\n June 2000\n\n The 'text/html' Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document summarizes the history of HTML development, and defines\n the \"text/html\" MIME type by pointing to the relevant W3C\n recommendations; it is intended to obsolete the previous IETF\n documents defining HTML, including RFC 1866, RFC 1867, RFC 1980, RFC\n 1942 and RFC 2070, and to remove HTML from IETF Standards Track.\n\n This document was prepared at the request of the W3C HTML working\n group. Please s 2854 attribute http presentation profile registered nested-reference unchanged"},{"id":"IETF RFC 2310","type":"specification","body":"IETF","designation":"RFC 2310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2310.txt","https://www.rfc-editor.org/rfc/rfc2310.pdf"],"folder":"IETF/RFC-2310","files":{"txt":{"path":"standards/IETF/RFC-2310/RFC-2310.txt","sha256":"f1f2ee17670096e1e9fd6a02133300fdf36562ae8a843b7152ea7158b1e93fb6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Holtman\nRequest for Comments: 2310 TUE\nCategory: Experimental April 1998\n\n The Safe Response Header Field\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a HTTP response header field called Safe, which\n can be used to indicate that repeating a HTTP request is safe. Such\n an indication will allow user agents to handle retries of some safe\n requests, in particular safe POST requests, in a more user-friendly\n way.\n\n1 Introduction\n\n This document defines a HTTP response header field called Safe, which\n can be used to indicate that repeating a HTTP reques","scope_keywords":["2310","http","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2310 Network Working Group K. Holtman\nRequest for Comments: 2310 TUE\nCategory: Experimental April 1998\n\n The Safe Response Header Field\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document defines a HTTP response header field called Safe, which\n can be used to indicate that repeating a HTTP request is safe. Such\n an indication will allow user agents to handle retries of some safe\n requests, in particular safe POST requests, in a more user-friendly\n way.\n\n1 Introduction\n\n This document defines a HTTP response header field called Safe, which\n can be used to indicate that repeating a HTTP reques 2310 http key risk nested-reference unchanged"},{"id":"IETF RFC 2586","type":"specification","body":"IETF","designation":"RFC 2586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2586.txt","https://www.rfc-editor.org/rfc/rfc2586.pdf"],"folder":"IETF/RFC-2586","files":{"txt":{"path":"standards/IETF/RFC-2586/RFC-2586.txt","sha256":"0357382a2435ccb569a20df625ddeb8b683543dddf3da902a33a88e7800a9d52"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Salsman\nRequest for Comments: 2586 H. Alvestrand\nCategory: Informational UNINETT\n May 1999\n\n The Audio/L16 MIME content type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines the audio/L16 MIME type, a reasonable quality\n audio format for use in Internet applications.\n\n Possible application areas include E-mail, Web served content, file\n upload in Web forms, and more.\n\n2. The need for the Audio/L16 MIME type\n\n The set of IETF standard MIME types for audio is small; it consists\n of only the audio/basic and audio/32kadpcm types, which have a\n sampling rate of 8000 samples/second.\n\n Rates below 11025 may obscure conso","scope_keywords":["2586","presentation","profile","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null}],"search_text":"IETF RFC 2586 Network Working Group J. Salsman\nRequest for Comments: 2586 H. Alvestrand\nCategory: Informational UNINETT\n May 1999\n\n The Audio/L16 MIME content type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines the audio/L16 MIME type, a reasonable quality\n audio format for use in Internet applications.\n\n Possible application areas include E-mail, Web served content, file\n upload in Web forms, and more.\n\n2. The need for the Audio/L16 MIME type\n\n The set of IETF standard MIME types for audio is small; it consists\n of only the audio/basic and audio/32kadpcm types, which have a\n sampling rate of 8000 samples/second.\n\n Rates below 11025 may obscure conso 2586 presentation profile risk nested-reference unchanged"},{"id":"IETF RFC 7578","type":"specification","body":"IETF","designation":"RFC 7578","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7578.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7578.txt","https://www.rfc-editor.org/rfc/rfc7578.pdf"],"folder":"IETF/RFC-7578","files":{"txt":{"path":"standards/IETF/RFC-7578/RFC-7578.txt","sha256":"813277f91c6c65c9047da9e9a8f1f0c19c1fb4bb1aaeea944bcf3bbdcc2eef49"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the multipart/form-data media type, which\n can be used by a wide variety of applications and transported by a\n wide variety of protocols as a way of returning a set of values as\n the result of a user filling out a form. This document obsoletes\n RFC 2388.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7578.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and ","scope_keywords":["7578","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7578 This specification defines the multipart/form-data media type, which\n can be used by a wide variety of applications and transported by a\n wide variety of protocols as a way of returning a set of values as\n the result of a user filling out a form. This document obsoletes\n RFC 2388.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7578.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and  7578 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1868","type":"specification","body":"IETF","designation":"RFC 1868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1868.txt","https://www.rfc-editor.org/rfc/rfc1868.pdf"],"folder":"IETF/RFC-1868","files":{"txt":{"path":"standards/IETF/RFC-1868/RFC-1868.txt","sha256":"6442f7b8f3d166095d18c79fa3cbd4130335e9d29f07adb3bdd2c43294aa560f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Malkin\nRequest For Comments: 1868 Xylogics, Inc.\nCategory: Experimental November 1995\n\n ARP Extension - UNARP\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Address Resolution Protocol allows an IP node to determine the\n hardware (datalink) address of a neighboring node on a broadcast\n network. The protocol depends on timers to age away old ARP entries.\n This document specifies a trivial modification to the ARP mechanism,\n not the packet format, which allows a node to announce that it is\n leaving the network and that all other nodes should modify their ARP\n tables accordingly.\n\nAcknowledgements\n\n Thanks to James Carlson/Xylogics for reviewing","scope_keywords":["1868"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1868 Network Working Group G. Malkin\nRequest For Comments: 1868 Xylogics, Inc.\nCategory: Experimental November 1995\n\n ARP Extension - UNARP\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nAbstract\n\n The Address Resolution Protocol allows an IP node to determine the\n hardware (datalink) address of a neighboring node on a broadcast\n network. The protocol depends on timers to age away old ARP entries.\n This document specifies a trivial modification to the ARP mechanism,\n not the packet format, which allows a node to announce that it is\n leaving the network and that all other nodes should modify their ARP\n tables accordingly.\n\nAcknowledgements\n\n Thanks to James Carlson/Xylogics for reviewing 1868 nested-reference unchanged"},{"id":"IETF RFC 2034","type":"specification","body":"IETF","designation":"RFC 2034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2034.txt","https://www.rfc-editor.org/rfc/rfc2034.pdf"],"folder":"IETF/RFC-2034","files":{"txt":{"path":"standards/IETF/RFC-2034/RFC-2034.txt","sha256":"0d02e1dc311b1c407e6ec36bde160fc411704a9a1ea0714c2d44066c452660d9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: RFC 2034 Innosoft\nCategory: Standards Track October 1996\n\n SMTP Service Extension for\n Returning Enhanced Error Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n This memo defines an extension to the SMTP service [RFC-821, RFC-\n 1869] whereby an SMTP server augments its responses with the enhanced\n mail system status codes defined in RFC 1893. These codes can then\n be used to provide more informative explanations of error conditions,\n especially in the context of the delivery status notifications format\n def","scope_keywords":["2034","crl","delivery","key","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 2034 Network Working Group N. Freed\nRequest for Comments: RFC 2034 Innosoft\nCategory: Standards Track October 1996\n\n SMTP Service Extension for\n Returning Enhanced Error Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n This memo defines an extension to the SMTP service [RFC-821, RFC-\n 1869] whereby an SMTP server augments its responses with the enhanced\n mail system status codes defined in RFC 1893. These codes can then\n be used to provide more informative explanations of error conditions,\n especially in the context of the delivery status notifications format\n def 2034 crl delivery key license subject nested-reference unchanged"},{"id":"IETF RFC 2554","type":"specification","body":"IETF","designation":"RFC 2554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2554.txt","https://www.rfc-editor.org/rfc/rfc2554.pdf"],"folder":"IETF/RFC-2554","files":{"txt":{"path":"standards/IETF/RFC-2554/RFC-2554.txt","sha256":"cd245a2be52406cac94f6d249a9a0bd4c8d02d4dcdf7637c3a0efae10b3799df"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 2554 Netscape Communications\nCategory: Standards Track March 1999\n\n SMTP Service Extension\n for Authentication\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines an SMTP service extension [ESMTP] whereby an\n SMTP client may indicate an authentication mechanism to the server,\n perform an authentication protocol exchange, and optionally negotiate\n a security layer for subsequent protocol interactions. This\n e","scope_keywords":["2554","authentication","crl","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null}],"search_text":"IETF RFC 2554 Network Working Group J. Myers\nRequest for Comments: 2554 Netscape Communications\nCategory: Standards Track March 1999\n\n SMTP Service Extension\n for Authentication\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document defines an SMTP service extension [ESMTP] whereby an\n SMTP client may indicate an authentication mechanism to the server,\n perform an authentication protocol exchange, and optionally negotiate\n a security layer for subsequent protocol interactions. This\n e 2554 authentication crl key profile nested-reference unchanged"},{"id":"IETF RFC 2645","type":"specification","body":"IETF","designation":"RFC 2645","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2645.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2645.txt","https://www.rfc-editor.org/rfc/rfc2645.pdf"],"folder":"IETF/RFC-2645","files":{"txt":{"path":"standards/IETF/RFC-2645/RFC-2645.txt","sha256":"5ba187fe61bbcaa7c3292dad9d315a47b37cfff490b5d7e7912ab235ca75da99"}},"tags":["nested-reference","unchanged"],"summary":"With the spread of low-cost computer systems and Internet\n connectivity, the demand for local mail servers has been rising.\n Many people now want to operate a mail server on a system which has\n\nGellens Standards Track [Page 1]\n\f\nRFC 2645 On-Demand Mail Relay August 1999\n\n only an intermittent connection to a service provider. If the system\n has a static IP address, the ESMTP ETRN command [ETRN] can be used.\n However, systems with dynamic IP addresses (which are very common\n with low-cost connections) have no widely-deployed solution.\n\n This memo proposes a new service, On-Demand Mail Relay (ODMR), which\n is a profile of SMTP [SMTP, ESMTP], providing for a secure,\n extensible, easy to implement approach to the problem.\n\n2. Conventions Used in this Document\n\n Because the client and server roles reverse during the session, to\n avoid confusion, the terms \"customer\" and \"provider\" will be use","scope_keywords":["2645","delivery","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 2645 With the spread of low-cost computer systems and Internet\n connectivity, the demand for local mail servers has been rising.\n Many people now want to operate a mail server on a system which has\n\nGellens Standards Track [Page 1]\n\f\nRFC 2645 On-Demand Mail Relay August 1999\n\n only an intermittent connection to a service provider. If the system\n has a static IP address, the ESMTP ETRN command [ETRN] can be used.\n However, systems with dynamic IP addresses (which are very common\n with low-cost connections) have no widely-deployed solution.\n\n This memo proposes a new service, On-Demand Mail Relay (ODMR), which\n is a profile of SMTP [SMTP, ESMTP], providing for a secure,\n extensible, easy to implement approach to the problem.\n\n2. Conventions Used in this Document\n\n Because the client and server roles reverse during the session, to\n avoid confusion, the terms \"customer\" and \"provider\" will be use 2645 delivery key profile nested-reference unchanged"},{"id":"IETF RFC 3848","type":"specification","body":"IETF","designation":"RFC 3848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3848.txt","https://www.rfc-editor.org/rfc/rfc3848.pdf"],"folder":"IETF/RFC-3848","files":{"txt":{"path":"standards/IETF/RFC-3848/RFC-3848.txt","sha256":"f711332f5f1c7f1f5a1cc1e30801c7ed77bf7087f398a90451fd881476188f2f"}},"tags":["nested-reference","unchanged"],"summary":"This registers seven new mail transmission types (ESMTPA, ESMTPS,\n ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the \"with\" clause of\n a Received header in an Internet message.\n\n1. IANA Considerations\n\n As directed by SMTP [2], IANA maintains a registry [7] of \"WITH\n protocol types\" for use in the \"with\" clause of the Received header\n in an Internet message. This registry presently includes SMTP [6],\n and ESMTP [2]. This specification updates the registry as follows:\n\n o The new keyword \"ESMTPA\" indicates the use of ESMTP when the SMTP\n AUTH [3] extension is also used and authentication is successfully\n achieved.\n\n o The new keyword \"ESMTPS\" indicates the use of ESMTP when STARTTLS\n [1] is also successfully negotiated to provide a strong transport\n encryption layer.\n\n o The new keyword \"ESMTPSA\" indicates the use of ESMTP when both\n STARTTLS and SMTP AUTH are successfully negotiated (t","scope_keywords":["3848","authentication","encryption","http","key","license","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null}],"search_text":"IETF RFC 3848 This registers seven new mail transmission types (ESMTPA, ESMTPS,\n ESMTPSA, LMTP, LMTPA, LMTPS, LMTPSA) for use in the \"with\" clause of\n a Received header in an Internet message.\n\n1. IANA Considerations\n\n As directed by SMTP [2], IANA maintains a registry [7] of \"WITH\n protocol types\" for use in the \"with\" clause of the Received header\n in an Internet message. This registry presently includes SMTP [6],\n and ESMTP [2]. This specification updates the registry as follows:\n\n o The new keyword \"ESMTPA\" indicates the use of ESMTP when the SMTP\n AUTH [3] extension is also used and authentication is successfully\n achieved.\n\n o The new keyword \"ESMTPS\" indicates the use of ESMTP when STARTTLS\n [1] is also successfully negotiated to provide a strong transport\n encryption layer.\n\n o The new keyword \"ESMTPSA\" indicates the use of ESMTP when both\n STARTTLS and SMTP AUTH are successfully negotiated (t 3848 authentication encryption http key license subject tls nested-reference unchanged"},{"id":"IETF RFC 4141","type":"specification","body":"IETF","designation":"RFC 4141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4141.txt","https://www.rfc-editor.org/rfc/rfc4141.pdf"],"folder":"IETF/RFC-4141","files":{"txt":{"path":"standards/IETF/RFC-4141/RFC-4141.txt","sha256":"200a6d050e55710e863a2f2d6fb61de130710a52c00c8ba8353ad99a10b6d619"}},"tags":["nested-reference","unchanged"],"summary":"A message originator sometimes sends content in a form the recipient\n cannot process or would prefer not to process a form of lower quality\n than is preferred. Such content needs to be converted to an\n acceptable form, with the same information or constrained information\n (e.g., changing from color to black and white). In a store-and-\n forward environment, it may be convenient to have this conversion\n performed by an intermediary. This specification integrates two\n ESMTP extensions and three MIME content header fields, which defines\n a cooperative service that permits authorized, accountable content\n form conversion by intermediaries.\n\nToyoda & Crocker Standards Track [Page 1]\n\f\nRFC 4141 SMTP & MIME Extensions for Content Conversion November 2005","scope_keywords":["4141","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 4141 A message originator sometimes sends content in a form the recipient\n cannot process or would prefer not to process a form of lower quality\n than is preferred. Such content needs to be converted to an\n acceptable form, with the same information or constrained information\n (e.g., changing from color to black and white). In a store-and-\n forward environment, it may be convenient to have this conversion\n performed by an intermediary. This specification integrates two\n ESMTP extensions and three MIME content header fields, which defines\n a cooperative service that permits authorized, accountable content\n form conversion by intermediaries.\n\nToyoda & Crocker Standards Track [Page 1]\n\f\nRFC 4141 SMTP & MIME Extensions for Content Conversion November 2005 4141 delivery presentation nested-reference unchanged"},{"id":"IETF RFC 2194","type":"specification","body":"IETF","designation":"RFC 2194","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2194.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2194.txt","https://www.rfc-editor.org/rfc/rfc2194.pdf"],"folder":"IETF/RFC-2194","files":{"txt":{"path":"standards/IETF/RFC-2194/RFC-2194.txt","sha256":"ad563aa3c6d7502d47ebab5c75167142e3f79c8fa044fb8b2d5ddda9acdaec88"}},"tags":["nested-reference","unchanged"],"summary":"This document reviews the design and functionality of existing\n roaming implementations. \"Roaming capability\" may be loosely defined\n as the ability to use any one of multiple Internet service providers\n (ISPs), while maintaining a formal, customer-vendor relationship with\n only one. Examples of cases where roaming capability might be\n required include ISP \"confederations\" and ISP-provided corporate\n network access support.\n\n3. Introduction\n\n Considerable interest has arisen recently in a set of features that\n fit within the general category of \"roaming capability\" for Internet\n users. Interested parties have included:\n\n Regional Internet Service Providers (ISPs) operating within a\n particular state or province, looking to combine their efforts\n with those of other regional providers to offer service over a\n wider area.\n\n National ISPs wishing to combine their operations with those of\n o","scope_keywords":["2194","attribute","attributes","authentication","authorization","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null}],"search_text":"IETF RFC 2194 This document reviews the design and functionality of existing\n roaming implementations. \"Roaming capability\" may be loosely defined\n as the ability to use any one of multiple Internet service providers\n (ISPs), while maintaining a formal, customer-vendor relationship with\n only one. Examples of cases where roaming capability might be\n required include ISP \"confederations\" and ISP-provided corporate\n network access support.\n\n3. Introduction\n\n Considerable interest has arisen recently in a set of features that\n fit within the general category of \"roaming capability\" for Internet\n users. Interested parties have included:\n\n Regional Internet Service Providers (ISPs) operating within a\n particular state or province, looking to combine their efforts\n with those of other regional providers to offer service over a\n wider area.\n\n National ISPs wishing to combine their operations with those of\n o 2194 attribute attributes authentication authorization http management presentation nested-reference unchanged"},{"id":"IETF RFC 1881","type":"specification","body":"IETF","designation":"RFC 1881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1881.txt","https://www.rfc-editor.org/rfc/rfc1881.pdf"],"folder":"IETF/RFC-1881","files":{"txt":{"path":"standards/IETF/RFC-1881/RFC-1881.txt","sha256":"a97e591b28a6ca0f92b25f5364fca6fb482a27908a02292ff6b8cd26b39d3249"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group IAB and IESG\nRequest for Comments: 1881 December 1995\nCategory: Informational\n\n IPv6 Address Allocation Management\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The IPv6 address space will be managed by the IANA for the good of\n the Internet community, with advice from the IAB and the IESG, by\n delegation to the regional registries.\n\nStatement\n\n The IPv6 address space must be managed for the good of the Internet\n community. Good management requires at least a small element of\n central authority over the delegation and allocation of the address\n space.\n\n The Internet community recognizes the Internet Assigned Numbers\n Authority (IANA) as the appropriate entity to have the responsibility\n for the management of the IPv6 ","scope_keywords":["1881","holder","management","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2071","folder":"IETF/RFC-2071","source":"IETF/RFC-2071/RFC-2071.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null}],"search_text":"IETF RFC 1881 Network Working Group IAB and IESG\nRequest for Comments: 1881 December 1995\nCategory: Informational\n\n IPv6 Address Allocation Management\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n The IPv6 address space will be managed by the IANA for the good of\n the Internet community, with advice from the IAB and the IESG, by\n delegation to the regional registries.\n\nStatement\n\n The IPv6 address space must be managed for the good of the Internet\n community. Good management requires at least a small element of\n central authority over the delegation and allocation of the address\n space.\n\n The Internet community recognizes the Internet Assigned Numbers\n Authority (IANA) as the appropriate entity to have the responsibility\n for the management of the IPv6  1881 holder management revocation nested-reference unchanged"},{"id":"IETF RFC 2928","type":"specification","body":"IETF","designation":"RFC 2928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2928.txt","https://www.rfc-editor.org/rfc/rfc2928.pdf"],"folder":"IETF/RFC-2928","files":{"txt":{"path":"standards/IETF/RFC-2928/RFC-2928.txt","sha256":"8692a0e62db5181bf2d7bbf6fb7e2309dab671c7bef5a04add316ccf4dca715b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 2928 Nokia\nCategory: Informational S. Deering\n Cisco\n R. Fink\n LBNL\n T. Hain\n Microsoft\n September 2000\n\n Initial IPv6 Sub-TLA ID Assignments\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines initial assignments of IPv6 Sub-Top-Level\n Aggregation Identifiers (Sub-TLA ID) to the Address Registries. It\n is intended as technical input to the Internet Assigned Numbers\n Authority (IANA) from the Internet Engineering Task Force (IETF)\n Internet Protocol Next Generation (IPNG) and Next Generation\n Transition (NGTRANS) working groups, as an input to the process of\n developing guidelines for the alloca","scope_keywords":["2928","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4773","folder":"IETF/RFC-4773","source":"IETF/RFC-4773/RFC-4773.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null}],"search_text":"IETF RFC 2928 Network Working Group R. Hinden\nRequest for Comments: 2928 Nokia\nCategory: Informational S. Deering\n Cisco\n R. Fink\n LBNL\n T. Hain\n Microsoft\n September 2000\n\n Initial IPv6 Sub-TLA ID Assignments\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document defines initial assignments of IPv6 Sub-Top-Level\n Aggregation Identifiers (Sub-TLA ID) to the Address Registries. It\n is intended as technical input to the Internet Assigned Numbers\n Authority (IANA) from the Internet Engineering Task Force (IETF)\n Internet Protocol Next Generation (IPNG) and Next Generation\n Transition (NGTRANS) working groups, as an input to the process of\n developing guidelines for the alloca 2928 authentication management nested-reference unchanged"},{"id":"IETF RFC 1924","type":"specification","body":"IETF","designation":"RFC 1924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1924.txt","https://www.rfc-editor.org/rfc/rfc1924.pdf"],"folder":"IETF/RFC-1924","files":{"txt":{"path":"standards/IETF/RFC-1924/RFC-1924.txt","sha256":"a7a388e155294a60ab16d857dcbb6bb50fa5c954001398d67ae7c8aa2a63229c"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 addresses, being 128 bits long, need 32 characters to write in\n the general case, if standard hex representation, is used, plus more\n for any punctuation inserted (typically about another 7 characters,\n or 39 characters total). This document specifies a more compact\n representation of IPv6 addresses, which permits encoding in a mere 20\n bytes.\n\n2. Introduction\n\n It is always necessary to be able to write in characters the form of\n an address, though in actual use it is always carried in binary. For\n IP version 4 (IP Classic) the well known dotted quad format is used.\n That is, 10.1.0.23 is one such address. Each decimal integer\n represents a one octet of the 4 octet address, and consequently has a\n value between 0 and 255 (inclusive). The written length of the\n address varies between 7 and 15 bytes.\n\n For IPv6 however, addresses are 16 octets long [IPv6], if the old\n standard form w","scope_keywords":["1924","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null}],"search_text":"IETF RFC 1924 IPv6 addresses, being 128 bits long, need 32 characters to write in\n the general case, if standard hex representation, is used, plus more\n for any punctuation inserted (typically about another 7 characters,\n or 39 characters total). This document specifies a more compact\n representation of IPv6 addresses, which permits encoding in a mere 20\n bytes.\n\n2. Introduction\n\n It is always necessary to be able to write in characters the form of\n an address, though in actual use it is always carried in binary. For\n IP version 4 (IP Classic) the well known dotted quad format is used.\n That is, 10.1.0.23 is one such address. Each decimal integer\n represents a one octet of the 4 octet address, and consequently has a\n value between 0 and 255 (inclusive). The written length of the\n address varies between 7 and 15 bytes.\n\n For IPv6 however, addresses are 16 octets long [IPv6], if the old\n standard form w 1924 presentation nested-reference unchanged"},{"id":"IETF RFC 2292","type":"specification","body":"IETF","designation":"RFC 2292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2292.txt","https://www.rfc-editor.org/rfc/rfc2292.pdf"],"folder":"IETF/RFC-2292","files":{"txt":{"path":"standards/IETF/RFC-2292/RFC-2292.txt","sha256":"1751dd29dae27680240ea66b9ea4d243d75d15f2c295ab56252ec548ea5f5946"}},"tags":["nested-reference","unchanged"],"summary":"Specifications are in progress for changes to the sockets API to\n support IP version 6 [RFC-2133]. These changes are for TCP and UDP-\n based applications and will support most end-user applications in use\n today: Telnet and FTP clients and servers, HTTP clients and servers,\n and the like.\n\n But another class of applications exists that will also be run under\n IPv6. We call these \"advanced\" applications and today this includes\n programs such as Ping, Traceroute, routing daemons, multicast routing\n daemons, router discovery daemons, and the like. The API feature\n typically used by these programs that make them \"advanced\" is a raw\n socket to access ICMPv4, IGMPv4, or IPv4, along with some knowledge\n of the packet header formats used by these protocols. To provide\n portability for applications that use raw sockets under IPv6, some\n standardization is needed for the advanced API features.\n\n T","scope_keywords":["2292","http","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2553","folder":"IETF/RFC-2553","source":"IETF/RFC-2553/RFC-2553.txt","version":null},{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 3542","folder":"IETF/RFC-3542","source":"IETF/RFC-3542/RFC-3542.txt","version":null}],"search_text":"IETF RFC 2292 Specifications are in progress for changes to the sockets API to\n support IP version 6 [RFC-2133]. These changes are for TCP and UDP-\n based applications and will support most end-user applications in use\n today: Telnet and FTP clients and servers, HTTP clients and servers,\n and the like.\n\n But another class of applications exists that will also be run under\n IPv6. We call these \"advanced\" applications and today this includes\n programs such as Ping, Traceroute, routing daemons, multicast routing\n daemons, router discovery daemons, and the like. The API feature\n typically used by these programs that make them \"advanced\" is a raw\n socket to access ICMPv4, IGMPv4, or IPv4, along with some knowledge\n of the packet header formats used by these protocols. To provide\n portability for applications that use raw sockets under IPv6, some\n standardization is needed for the advanced API features.\n\n T 2292 http identification path nested-reference unchanged"},{"id":"IETF RFC 3152","type":"specification","body":"IETF","designation":"RFC 3152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3152.txt","https://www.rfc-editor.org/rfc/rfc3152.pdf"],"folder":"IETF/RFC-3152","files":{"txt":{"path":"standards/IETF/RFC-3152/RFC-3152.txt","sha256":"6c0717f97084e782eff424cf3ffcfaafb97b5ee906e4dfb50ef77908eb4046f1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Bush\nRequest for Comments: 3152 RGnet\nBCP: 49 August 2001\nUpdates: 2874, 2772, 2766, 2553, 1886\nCategory: Best Current Practice\n\n Delegation of IP6.ARPA\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document discusses the need for delegation of the IP6.ARPA DNS\n zone, and specifies a plan for the technical operation thereof.\n\n1. Why IP6.ARPA?\n\n In the IPv6 address space, there is a need for 'reverse mapping' of\n addresses to DNS names analogous to that provided by the IN-ADDR.ARPA\n zone for IPv4.\n\n The IAB recommended that the ARPA top level domain (the name is now\n considered an acronym for \"Address an","scope_keywords":["3152"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3363","folder":"IETF/RFC-3363","source":"IETF/RFC-3363/RFC-3363.txt","version":null},{"body":"IETF","designation":"RFC 3596","folder":"IETF/RFC-3596","source":"IETF/RFC-3596/RFC-3596.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 4159","folder":"IETF/RFC-4159","source":"IETF/RFC-4159/RFC-4159.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null}],"search_text":"IETF RFC 3152 Network Working Group R. Bush\nRequest for Comments: 3152 RGnet\nBCP: 49 August 2001\nUpdates: 2874, 2772, 2766, 2553, 1886\nCategory: Best Current Practice\n\n Delegation of IP6.ARPA\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document discusses the need for delegation of the IP6.ARPA DNS\n zone, and specifies a plan for the technical operation thereof.\n\n1. Why IP6.ARPA?\n\n In the IPv6 address space, there is a need for 'reverse mapping' of\n addresses to DNS names analogous to that provided by the IN-ADDR.ARPA\n zone for IPv4.\n\n The IAB recommended that the ARPA top level domain (the name is now\n considered an acronym for \"Address an 3152 nested-reference unchanged"},{"id":"IETF RFC 6563","type":"specification","body":"IETF","designation":"RFC 6563","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6563.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6563.txt","https://www.rfc-editor.org/rfc/rfc6563.pdf"],"folder":"IETF/RFC-6563","files":{"txt":{"path":"standards/IETF/RFC-6563/RFC-6563.txt","sha256":"2230ddcec7447d3f5218af57ada985d4dcb874f3a8c786a873d56e47c5300212"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a summary of issues related to the use of A6\n records, discusses the current status, and moves RFC 2874 to Historic\n status, providing clarity to implementers and operators.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6563.\n\nCopyright Notice\n\n Copyright (c) 2012","scope_keywords":["6563","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null}],"search_text":"IETF RFC 6563 This document provides a summary of issues related to the use of A6\n records, discusses the current status, and moves RFC 2874 to Historic\n status, providing clarity to implementers and operators.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6563.\n\nCopyright Notice\n\n Copyright (c) 2012 6563 http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 2029","type":"specification","body":"IETF","designation":"RFC 2029","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2029.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2029.txt","https://www.rfc-editor.org/rfc/rfc2029.pdf"],"folder":"IETF/RFC-2029","files":{"txt":{"path":"standards/IETF/RFC-2029/RFC-2029.txt","sha256":"fcbf6925d96f94008a2ea8925e37ca29da4e9bba58ed80d85ae11a7a804bf037"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a packetization scheme for the CellB video\n encoding. The scheme proposed allows applications to transport CellB\n video flows over protocols used by RTP. This document is meant for\n implementors of video applications that want to use RTP and CellB.\n\n1. Introduction\n\n The Cell image compression algorithm is a variable bit-rate video\n coding scheme. It provides \"high\" quality, low bit-rate image\n compression at low computational cost. The bytestream that is\n produced by the Cell encoder consists of instructional codes and\n information about the compressed image.\n\n For futher information on Cell compression technology, refer to [1].\n Currently, there are two versions of the Cell compression technology:\n CellA and CellB. CellA is primarily designed for the encoding of\n stored video intended for local display, and will not be discussed in\n this memo.\n\n CellB, derived from ","scope_keywords":["2029","algorithm","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2029 This memo describes a packetization scheme for the CellB video\n encoding. The scheme proposed allows applications to transport CellB\n video flows over protocols used by RTP. This document is meant for\n implementors of video applications that want to use RTP and CellB.\n\n1. Introduction\n\n The Cell image compression algorithm is a variable bit-rate video\n coding scheme. It provides \"high\" quality, low bit-rate image\n compression at low computational cost. The bytestream that is\n produced by the Cell encoder consists of instructional codes and\n information about the compressed image.\n\n For futher information on Cell compression technology, refer to [1].\n Currently, there are two versions of the Cell compression technology:\n CellA and CellB. CellA is primarily designed for the encoding of\n stored video intended for local display, and will not be discussed in\n this memo.\n\n CellB, derived from  2029 algorithm profile timestamp nested-reference unchanged"},{"id":"IETF RFC 2032","type":"specification","body":"IETF","designation":"RFC 2032","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2032.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2032.txt","https://www.rfc-editor.org/rfc/rfc2032.pdf"],"folder":"IETF/RFC-2032","files":{"txt":{"path":"standards/IETF/RFC-2032/RFC-2032.txt","sha256":"f3692a37e422dee0c2fd8774001f50794cc5918ec77b55ee1f08053eac9d0845"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a scheme to packetize an H.261 video stream for\n transport using the Real-time Transport Protocol, RTP, with any of\n the underlying protocols that carry RTP.\n\n This specification is a product of the Audio/Video Transport working\n group within the Internet Engineering Task Force. Comments are\n solicited and should be addressed to the working group's mailing list\n at rem-conf@es.net and/or the authors.\n\nTurletti & Huitema Standards Track [Page 1]\n\f\nRFC 2032 RTP Payload Format for H.261 Video October 1996\n\n2. Purpose of this document\n\n The ITU-T recommendation H.261 [6] specifies the encodings used by\n ITU-T compliant video-conference codecs. Although these encodings\n were originally specified for fixed data rate ISDN circuits,\n experiments [3],[8] have shown that they can also be used over\n packet-switched networks such as the Internet.\n\n The purpose of this memo is to ","scope_keywords":["2032"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2029","folder":"IETF/RFC-2029","source":"IETF/RFC-2029/RFC-2029.txt","version":null},{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 2429","folder":"IETF/RFC-2429","source":"IETF/RFC-2429/RFC-2429.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null}],"search_text":"IETF RFC 2032 This memo describes a scheme to packetize an H.261 video stream for\n transport using the Real-time Transport Protocol, RTP, with any of\n the underlying protocols that carry RTP.\n\n This specification is a product of the Audio/Video Transport working\n group within the Internet Engineering Task Force. Comments are\n solicited and should be addressed to the working group's mailing list\n at rem-conf@es.net and/or the authors.\n\nTurletti & Huitema Standards Track [Page 1]\n\f\nRFC 2032 RTP Payload Format for H.261 Video October 1996\n\n2. Purpose of this document\n\n The ITU-T recommendation H.261 [6] specifies the encodings used by\n ITU-T compliant video-conference codecs. Although these encodings\n were originally specified for fixed data rate ISDN circuits,\n experiments [3],[8] have shown that they can also be used over\n packet-switched networks such as the Internet.\n\n The purpose of this memo is to  2032 nested-reference unchanged"},{"id":"IETF RFC 2038","type":"specification","body":"IETF","designation":"RFC 2038","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2038.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2038.txt","https://www.rfc-editor.org/rfc/rfc2038.pdf"],"folder":"IETF/RFC-2038","files":{"txt":{"path":"standards/IETF/RFC-2038/RFC-2038.txt","sha256":"a90d203c08826ea88c502239d25a9c75498c2122e1f838d4dda44aa7fd288170"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a packetization scheme for MPEG video and audio\n streams. The scheme proposed can be used to transport such a video\n or audio flow over the transport protocols supported by RTP. Two\n approaches are described. The first is designed to support maximum\n interoperability with MPEG System environments. The second is\n designed to provide maximum compatibility with other RTP-encapsulated\n media streams and future conference control work of the IETF.\n\n1. Introduction\n\n ISO/IEC JTC1/SC29 WG11 (also referred to as the MPEG committee) has\n defined the MPEG1 standard (ISO/IEC 11172)[1] and the MPEG2 standard\n (ISO/IEC 13818)[2]. This memo describes a packetization scheme to\n transport MPEG video and audio streams using the Real-time Transport\n Protocol (RTP), version 2 [3, 4].\n\n The MPEG1 specification is defined in three parts: System, Video and\n Audio. It is designed primarily ","scope_keywords":["2038","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null}],"search_text":"IETF RFC 2038 This memo describes a packetization scheme for MPEG video and audio\n streams. The scheme proposed can be used to transport such a video\n or audio flow over the transport protocols supported by RTP. Two\n approaches are described. The first is designed to support maximum\n interoperability with MPEG System environments. The second is\n designed to provide maximum compatibility with other RTP-encapsulated\n media streams and future conference control work of the IETF.\n\n1. Introduction\n\n ISO/IEC JTC1/SC29 WG11 (also referred to as the MPEG committee) has\n defined the MPEG1 standard (ISO/IEC 11172)[1] and the MPEG2 standard\n (ISO/IEC 13818)[2]. This memo describes a packetization scheme to\n transport MPEG video and audio streams using the Real-time Transport\n Protocol (RTP), version 2 [3, 4].\n\n The MPEG1 specification is defined in three parts: System, Video and\n Audio. It is designed primarily  2038 presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 2190","type":"specification","body":"IETF","designation":"RFC 2190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2190.txt","https://www.rfc-editor.org/rfc/rfc2190.pdf"],"folder":"IETF/RFC-2190","files":{"txt":{"path":"standards/IETF/RFC-2190/RFC-2190.txt","sha256":"4c80dbc5558ddb181eb2646882cbadecddeb09f25685f1fe297d84dcafdc2598"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the payload format for encapsulating an H.263\n bitstream in the Real-Time Transport Protocol (RTP). Three modes are\n defined for the H.263 payload header. An RTP packet can use one of\n the three modes for H.263 video streams depending on the desired\n network packet size and H.263 encoding options employed. The shortest\n H.263 payload header (mode A) supports fragmentation at Group of\n Block (GOB) boundaries. The long H.263 payload headers (mode B and C)\n support fragmentation at Macroblock (MB) boundaries.\n\n1. Introduction\n\n This document describes a scheme to packetize an H.263 video stream\n for transport using RTP [1]. H.263 video stream is defined by ITU-T\n Recommendation H.263 (referred to as H.263 in this document) [4] for\n video coding at very low data rates. RTP is defined by the Internet\n Engineering Task Force (IETF) to provide end-to-end network transpor","scope_keywords":["2190","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2429","folder":"IETF/RFC-2429","source":"IETF/RFC-2429/RFC-2429.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null}],"search_text":"IETF RFC 2190 This document specifies the payload format for encapsulating an H.263\n bitstream in the Real-Time Transport Protocol (RTP). Three modes are\n defined for the H.263 payload header. An RTP packet can use one of\n the three modes for H.263 video streams depending on the desired\n network packet size and H.263 encoding options employed. The shortest\n H.263 payload header (mode A) supports fragmentation at Group of\n Block (GOB) boundaries. The long H.263 payload headers (mode B and C)\n support fragmentation at Macroblock (MB) boundaries.\n\n1. Introduction\n\n This document describes a scheme to packetize an H.263 video stream\n for transport using RTP [1]. H.263 video stream is defined by ITU-T\n Recommendation H.263 (referred to as H.263 in this document) [4] for\n video coding at very low data rates. RTP is defined by the Internet\n Engineering Task Force (IETF) to provide end-to-end network transpor 2190 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 2198","type":"specification","body":"IETF","designation":"RFC 2198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2198.txt","https://www.rfc-editor.org/rfc/rfc2198.pdf"],"folder":"IETF/RFC-2198","files":{"txt":{"path":"standards/IETF/RFC-2198/RFC-2198.txt","sha256":"86c433f7fae8d5bcee1175f459a1afa14a40fc42730d62013df5e811ee739ce4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a payload format for use with the real-time\n transport protocol (RTP), version 2, for encoding redundant audio\n data. The primary motivation for the scheme described herein is the\n development of audio conferencing tools for use with lossy packet\n networks such as the Internet Mbone, although this scheme is not\n limited to such applications.\n\n1 Introduction\n\n If multimedia conferencing is to become widely used by the Internet\n Mbone community, users must perceive the quality to be sufficiently\n good for most applications. We have identified a number of problems\n which impair the quality of conferences, the most significant of\n which is packet loss. This is a persistent problem, particularly\n given the increasing popularity, and therefore increasing load, of\n the Internet. The disruption of speech intelligibility even at low\n loss rates which is currently experienc","scope_keywords":["2198","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2354","folder":"IETF/RFC-2354","source":"IETF/RFC-2354/RFC-2354.txt","version":null},{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 2736","folder":"IETF/RFC-2736","source":"IETF/RFC-2736/RFC-2736.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2833","folder":"IETF/RFC-2833","source":"IETF/RFC-2833/RFC-2833.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 4756","folder":"IETF/RFC-4756","source":"IETF/RFC-4756/RFC-4756.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 2198 This document describes a payload format for use with the real-time\n transport protocol (RTP), version 2, for encoding redundant audio\n data. The primary motivation for the scheme described herein is the\n development of audio conferencing tools for use with lossy packet\n networks such as the Internet Mbone, although this scheme is not\n limited to such applications.\n\n1 Introduction\n\n If multimedia conferencing is to become widely used by the Internet\n Mbone community, users must perceive the quality to be sufficiently\n good for most applications. We have identified a number of problems\n which impair the quality of conferences, the most significant of\n which is packet loss. This is a persistent problem, particularly\n given the increasing popularity, and therefore increasing load, of\n the Internet. The disruption of speech intelligibility even at low\n loss rates which is currently experienc 2198 profile timestamp nested-reference unchanged"},{"id":"IETF RFC 2211","type":"specification","body":"IETF","designation":"RFC 2211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2211.txt","https://www.rfc-editor.org/rfc/rfc2211.pdf"],"folder":"IETF/RFC-2211","files":{"txt":{"path":"standards/IETF/RFC-2211/RFC-2211.txt","sha256":"aa0141d4eff69d4b61eb0081ab9a8dac14b34ca4da9df8e97f64724e26764e00"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Wroclawski\nRequest For Comments: 2211 MIT LCS\nCategory: Standards Track September 1997\n\n Specification of the Controlled-Load Network Element Service\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo specifies the network element behavior required to deliver\n Controlled-Load service in the Internet. Controlled-load service\n provides the client data flow with a quality of service closely\n approximating the QoS that same flow would receive from an unloaded\n network element, but uses capacity (admission) control to assure that\n this serv","scope_keywords":["2211","algorithm","algorithms","delivery","path","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2208","folder":"IETF/RFC-2208","source":"IETF/RFC-2208/RFC-2208.txt","version":null},{"body":"IETF","designation":"RFC 2210","folder":"IETF/RFC-2210","source":"IETF/RFC-2210/RFC-2210.txt","version":null},{"body":"IETF","designation":"RFC 2215","folder":"IETF/RFC-2215","source":"IETF/RFC-2215/RFC-2215.txt","version":null},{"body":"IETF","designation":"RFC 2216","folder":"IETF/RFC-2216","source":"IETF/RFC-2216/RFC-2216.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2638","folder":"IETF/RFC-2638","source":"IETF/RFC-2638/RFC-2638.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2746","folder":"IETF/RFC-2746","source":"IETF/RFC-2746/RFC-2746.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3006","folder":"IETF/RFC-3006","source":"IETF/RFC-3006/RFC-3006.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null}],"search_text":"IETF RFC 2211 Network Working Group J. Wroclawski\nRequest For Comments: 2211 MIT LCS\nCategory: Standards Track September 1997\n\n Specification of the Controlled-Load Network Element Service\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This memo specifies the network element behavior required to deliver\n Controlled-Load service in the Internet. Controlled-load service\n provides the client data flow with a quality of service closely\n approximating the QoS that same flow would receive from an unloaded\n network element, but uses capacity (admission) control to assure that\n this serv 2211 algorithm algorithms delivery path tsp nested-reference unchanged"},{"id":"IETF RFC 2354","type":"specification","body":"IETF","designation":"RFC 2354","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2354.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2354.txt","https://www.rfc-editor.org/rfc/rfc2354.pdf"],"folder":"IETF/RFC-2354","files":{"txt":{"path":"standards/IETF/RFC-2354/RFC-2354.txt","sha256":"7d84cb4880e642192f04290308ca7c7d5dd147dc0e411ec9b10b5e2927196186"}},"tags":["nested-reference","unchanged"],"summary":"This document summarizes a range of possible techniques for the\n repair of continuous media streams subject to packet loss. The\n techniques discussed include redundant transmission, retransmission,\n interleaving and forward error correction. The range of\n applicability of these techniques is noted, together with the\n protocol requirements and dependencies.\n\n1 Introduction\n\n A number of applications have emerged which use RTP/UDP transport to\n deliver continuous media streams. Due to the unreliable nature of\n UDP packet delivery, the quality of the received stream will be\n adversely affected by packet loss. A number of techniques exist by\n which the effects of packet loss may be repaired. These techniques\n have a wide range of applicability and require varying degrees of\n protocol support. In this document, a number of such techniques are\n discussed, and recommendations for their applicab","scope_keywords":["2354","algorithm","delivery","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null}],"search_text":"IETF RFC 2354 This document summarizes a range of possible techniques for the\n repair of continuous media streams subject to packet loss. The\n techniques discussed include redundant transmission, retransmission,\n interleaving and forward error correction. The range of\n applicability of these techniques is noted, together with the\n protocol requirements and dependencies.\n\n1 Introduction\n\n A number of applications have emerged which use RTP/UDP transport to\n deliver continuous media streams. Due to the unreliable nature of\n UDP packet delivery, the quality of the received stream will be\n adversely affected by packet loss. A number of techniques exist by\n which the effects of packet loss may be repaired. These techniques\n have a wide range of applicability and require varying degrees of\n protocol support. In this document, a number of such techniques are\n discussed, and recommendations for their applicab 2354 algorithm delivery subject timestamp nested-reference unchanged"},{"id":"IETF RFC 2429","type":"specification","body":"IETF","designation":"RFC 2429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2429.txt","https://www.rfc-editor.org/rfc/rfc2429.pdf"],"folder":"IETF/RFC-2429","files":{"txt":{"path":"standards/IETF/RFC-2429/RFC-2429.txt","sha256":"8d6c12de824a91137ae8c98b4655493de226c0f9f40764b5246c995bf15884a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRequest for Comments: 2429 C. Bormann\nCategory: Standards Track Univ. Bremen\n L. Cline\n G. Deisher\n T. Gardos\n C. Maciocco\n D. Newell\n Intel\n J. Ott\n Univ. Bremen\n G. Sullivan\n PictureTel\n S. Wenger\n TU Berlin\n C. Zhu\n Intel\n October 1998\n\n RTP Payload Format for the 1998 Version of\n ITU-T Rec. H.263 Video (H.263+)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies an RTP payload header format applicable to\n the transmission of video s","scope_keywords":["2429","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3839","folder":"IETF/RFC-3839","source":"IETF/RFC-3839/RFC-3839.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null}],"search_text":"IETF RFC 2429 Network Working Group\nRequest for Comments: 2429 C. Bormann\nCategory: Standards Track Univ. Bremen\n L. Cline\n G. Deisher\n T. Gardos\n C. Maciocco\n D. Newell\n Intel\n J. Ott\n Univ. Bremen\n G. Sullivan\n PictureTel\n S. Wenger\n TU Berlin\n C. Zhu\n Intel\n October 1998\n\n RTP Payload Format for the 1998 Version of\n ITU-T Rec. H.263 Video (H.263+)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This document specifies an RTP payload header format applicable to\n the transmission of video s 2429 timestamp nested-reference unchanged"},{"id":"IETF RFC 2435","type":"specification","body":"IETF","designation":"RFC 2435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2435.txt","https://www.rfc-editor.org/rfc/rfc2435.pdf"],"folder":"IETF/RFC-2435","files":{"txt":{"path":"standards/IETF/RFC-2435/RFC-2435.txt","sha256":"9893962b86f1b129b822aa482a2bc30a7aafb98de284c138b2489965fe20473d"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the RTP payload format for JPEG video streams.\n The packet format is optimized for real-time video streams where\n codec parameters change rarely from frame to frame.\n\n This document is a product of the Audio-Video Transport working group\n within the Internet Engineering Task Force. Comments are solicited\n and should be addressed to the working group's mailing list at rem-\n conf@es.net and/or the author(s).\n\nChanges from RFC 2035\n\n Most of this memo is identical to RFC 2035. The changes made to the\n protocol are summarized in Appendix D.\n\nBerc, et. al. Standards Track [Page 1]\n\f\nRFC 2435 RTP Payload Format for JPEG October 1998\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [9].\n\n1. Introduction\n\n The Joint Pho","scope_keywords":["2435","algorithm","algorithms","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2435 This memo describes the RTP payload format for JPEG video streams.\n The packet format is optimized for real-time video streams where\n codec parameters change rarely from frame to frame.\n\n This document is a product of the Audio-Video Transport working group\n within the Internet Engineering Task Force. Comments are solicited\n and should be addressed to the working group's mailing list at rem-\n conf@es.net and/or the author(s).\n\nChanges from RFC 2035\n\n Most of this memo is identical to RFC 2035. The changes made to the\n protocol are summarized in Appendix D.\n\nBerc, et. al. Standards Track [Page 1]\n\f\nRFC 2435 RTP Payload Format for JPEG October 1998\n\nKey Words\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [9].\n\n1. Introduction\n\n The Joint Pho 2435 algorithm algorithms attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 2705","type":"specification","body":"IETF","designation":"RFC 2705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2705.txt","https://www.rfc-editor.org/rfc/rfc2705.pdf"],"folder":"IETF/RFC-2705","files":{"txt":{"path":"standards/IETF/RFC-2705/RFC-2705.txt","sha256":"ed82cd7741519eb6542c06e6eb622669a02f6977550b04f169b3a15e2eeddcbf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application programming interface and a\n corresponding protocol (MGCP) for controlling Voice over IP (VoIP)\n Gateways from external call control elements. MGCP assumes a call\n control architecture where the call control \"intelligence\" is outside\n the gateways and handled by external call control elements.\n\n The document is structured in 6 main sections:\n\n * The introduction presents the basic assumptions and the relation\n to other protocols such as H.323, RTSP, SAP or SIP.\n\nArango, et al. Informational [Page 1]\n\f\nRFC 2705 Media Gateway Control Protocol (MGCP) October 1999\n\n * The interface section presents a conceptual overview of the MGCP,\n presenting the naming conventions, the usage of the session\n description protocol SDP, and the procedures that compose MGCP:\n Notifications Request, Notification, Create Connection, Modify\n Connection, Delete Connection, Au","scope_keywords":["2705","attribute","attributes","audit","management","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2871","folder":"IETF/RFC-2871","source":"IETF/RFC-2871/RFC-2871.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3407","folder":"IETF/RFC-3407","source":"IETF/RFC-3407/RFC-3407.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"IETF RFC 2705 This document describes an application programming interface and a\n corresponding protocol (MGCP) for controlling Voice over IP (VoIP)\n Gateways from external call control elements. MGCP assumes a call\n control architecture where the call control \"intelligence\" is outside\n the gateways and handled by external call control elements.\n\n The document is structured in 6 main sections:\n\n * The introduction presents the basic assumptions and the relation\n to other protocols such as H.323, RTSP, SAP or SIP.\n\nArango, et al. Informational [Page 1]\n\f\nRFC 2705 Media Gateway Control Protocol (MGCP) October 1999\n\n * The interface section presents a conceptual overview of the MGCP,\n presenting the naming conventions, the usage of the session\n description protocol SDP, and the procedures that compose MGCP:\n Notifications Request, Notification, Create Connection, Modify\n Connection, Delete Connection, Au 2705 attribute attributes audit management tsp nested-reference unchanged"},{"id":"IETF RFC 2733","type":"specification","body":"IETF","designation":"RFC 2733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2733.txt","https://www.rfc-editor.org/rfc/rfc2733.pdf"],"folder":"IETF/RFC-2733","files":{"txt":{"path":"standards/IETF/RFC-2733/RFC-2733.txt","sha256":"1bb553ddde56293a6ad912215396f8b6b814228ed12e708ad31a162ffbc5224e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a payload format for generic forward error\n correction of media encapsulated in RTP. It is engineered for FEC\n algorithms based on the exclusive-or (parity) operation. The payload\n format allows end systems to transmit using arbitrary block lengths\n and parity schemes. It also allows for the recovery of both the\n payload and critical RTP header fields. Since FEC is sent as a\n separate stream, it is backwards compatible with non-FEC capable\n hosts, so that receivers which do not wish to implement FEC can just\n ignore the extensions.","scope_keywords":["2733","algorithm","algorithms","key","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3009","folder":"IETF/RFC-3009","source":"IETF/RFC-3009/RFC-3009.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null}],"search_text":"IETF RFC 2733 This document specifies a payload format for generic forward error\n correction of media encapsulated in RTP. It is engineered for FEC\n algorithms based on the exclusive-or (parity) operation. The payload\n format allows end systems to transmit using arbitrary block lengths\n and parity schemes. It also allows for the recovery of both the\n payload and critical RTP header fields. Since FEC is sent as a\n separate stream, it is backwards compatible with non-FEC capable\n hosts, so that receivers which do not wish to implement FEC can just\n ignore the extensions. 2733 algorithm algorithms key tsp nested-reference unchanged"},{"id":"IETF RFC 2736","type":"specification","body":"IETF","designation":"RFC 2736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2736.txt","https://www.rfc-editor.org/rfc/rfc2736.pdf"],"folder":"IETF/RFC-2736","files":{"txt":{"path":"standards/IETF/RFC-2736/RFC-2736.txt","sha256":"a08c3818f217a117f6dd15229231f49cc5ccbc7b85556259b72c59f57caeb745"}},"tags":["nested-reference","unchanged"],"summary":"This document provides general guidelines aimed at assisting the\n authors of RTP Payload Format specifications in deciding on good\n formats. These guidelines attempt to capture some of the experience\n gained with RTP as it evolved during its development.\n\n1. Introduction\n\n This document provides general guidelines aimed at assisting the\n authors of RTP [9] Payload Format specifications in deciding on good\n formats. These guidelines attempt to capture some of the experience\n gained with RTP as it evolved during its development.\n\n The principles outlined in this document are applicable to almost all\n data types, but are framed in examples of audio and video codecs for\n clarity.\n\n2. Background\n\n RTP was designed around the concept of Application Level Framing\n (ALF), first described by Clark and Tennenhouse [2]. The key argument\n underlying ALF is that there are many different ways an appli","scope_keywords":["2736","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 2736 This document provides general guidelines aimed at assisting the\n authors of RTP Payload Format specifications in deciding on good\n formats. These guidelines attempt to capture some of the experience\n gained with RTP as it evolved during its development.\n\n1. Introduction\n\n This document provides general guidelines aimed at assisting the\n authors of RTP [9] Payload Format specifications in deciding on good\n formats. These guidelines attempt to capture some of the experience\n gained with RTP as it evolved during its development.\n\n The principles outlined in this document are applicable to almost all\n data types, but are framed in examples of audio and video codecs for\n clarity.\n\n2. Background\n\n RTP was designed around the concept of Application Level Framing\n (ALF), first described by Clark and Tennenhouse [2]. The key argument\n underlying ALF is that there are many different ways an appli 2736 key nested-reference unchanged"},{"id":"IETF RFC 2793","type":"specification","body":"IETF","designation":"RFC 2793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2793.txt","https://www.rfc-editor.org/rfc/rfc2793.pdf"],"folder":"IETF/RFC-2793","files":{"txt":{"path":"standards/IETF/RFC-2793/RFC-2793.txt","sha256":"9aaa9d31f81abf04ad10f19eea7375a32b061092b381f31ac62410f2524d36cb"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to carry text conversation session contents\n in RTP packets. Text conversation session contents are specified in\n ITU-T Recommendation T.140 [1].\n\n Text conversation is used alone or in connection to other\n conversational facilities such as video and voice, to form multimedia\n conversation services.\n\n This RTP payload description contains an optional possibility to\n include redundant text from already transmitted packets in order to\n reduce the risk of text loss caused by packet loss. The redundancy\n coding follows RFC 2198.\n\n1. Introduction\n\n This memo defines a payload type for carrying text conversation\n session contents in RTP packets. Text conversation session contents\n are specified in ITU-T Recommendation T.140 [1]. Text conversation is\n used alone or in connection to other conversational facilities such\n as video and voice, to form multimedia conversation ","scope_keywords":["2793","key","profile","profiles","risk","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null}],"search_text":"IETF RFC 2793 This memo describes how to carry text conversation session contents\n in RTP packets. Text conversation session contents are specified in\n ITU-T Recommendation T.140 [1].\n\n Text conversation is used alone or in connection to other\n conversational facilities such as video and voice, to form multimedia\n conversation services.\n\n This RTP payload description contains an optional possibility to\n include redundant text from already transmitted packets in order to\n reduce the risk of text loss caused by packet loss. The redundancy\n coding follows RFC 2198.\n\n1. Introduction\n\n This memo defines a payload type for carrying text conversation\n session contents in RTP packets. Text conversation session contents\n are specified in ITU-T Recommendation T.140 [1]. Text conversation is\n used alone or in connection to other conversational facilities such\n as video and voice, to form multimedia conversation  2793 key profile profiles risk timestamp nested-reference unchanged"},{"id":"IETF RFC 2833","type":"specification","body":"IETF","designation":"RFC 2833","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2833.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2833.txt","https://www.rfc-editor.org/rfc/rfc2833.pdf"],"folder":"IETF/RFC-2833","files":{"txt":{"path":"standards/IETF/RFC-2833/RFC-2833.txt","sha256":"1c507ef8fab638922ada460d934ba7bbeb09ae2ca4424160b970abb6f9753d1b"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to carry dual-tone multifrequency (DTMF)\n signaling, other tone signals and telephony events in RTP packets.\n\n1 Introduction\n\n This memo defines two payload formats, one for carrying dual-tone\n multifrequency (DTMF) digits, other line and trunk signals (Section\n 3), and a second one for general multi-frequency tones in RTP [1]\n packets (Section 4). Separate RTP payload formats are desirable since\n low-rate voice codecs cannot be guaranteed to reproduce these tone\n signals accurately enough for automatic recognition. Defining\n separate payload formats also permits higher redundancy while\n maintaining a low bit rate.\n\n The payload formats described here may be useful in at least three\n applications: DTMF handling for gateways and end systems, as well as\n \"RTP trunks\". In the first application, the Internet telephony\n gateway detects DTMF on the incoming circuits and","scope_keywords":["2833","algorithm","algorithms","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null}],"search_text":"IETF RFC 2833 This memo describes how to carry dual-tone multifrequency (DTMF)\n signaling, other tone signals and telephony events in RTP packets.\n\n1 Introduction\n\n This memo defines two payload formats, one for carrying dual-tone\n multifrequency (DTMF) digits, other line and trunk signals (Section\n 3), and a second one for general multi-frequency tones in RTP [1]\n packets (Section 4). Separate RTP payload formats are desirable since\n low-rate voice codecs cannot be guaranteed to reproduce these tone\n signals accurately enough for automatic recognition. Defining\n separate payload formats also permits higher redundancy while\n maintaining a low bit rate.\n\n The payload formats described here may be useful in at least three\n applications: DTMF handling for gateways and end systems, as well as\n \"RTP trunks\". In the first application, the Internet telephony\n gateway detects DTMF on the incoming circuits and 2833 algorithm algorithms key path presentation nested-reference unchanged"},{"id":"IETF RFC 2862","type":"specification","body":"IETF","designation":"RFC 2862","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2862.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2862.txt","https://www.rfc-editor.org/rfc/rfc2862.pdf"],"folder":"IETF/RFC-2862","files":{"txt":{"path":"standards/IETF/RFC-2862/RFC-2862.txt","sha256":"03e92f5103d8df3e20533f2f95126609cf77cb2d01a42631a6b70f08a6b13290"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an RTP [1] payload format for transporting\n the coordinates of a dynamic pointer that may be used during a\n presentation. Although a mouse can be used as the pointer, this\n payload format is not intended and may not have all functionalities\n needed to implement a general mouse event transmission mechanism.\n\n1. Introduction\n\n In most presentations, significant information is conveyed through\n the use of viewgraphs and a pointer. This makes accurate transmission\n of them vital in remote conferencing applications. Using regular\n video of a presenter's display for this purpose is problematic\n because, while the viewgraphs require a high spatial resolution, the\n pointer movements need to be sampled and transmitted at a high\n temporal resolution so that the presenter's pointing actions can be\n displayed synchronously with the corresponding audio and video\n signals. In m","scope_keywords":["2862","key","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 2862 This document describes an RTP [1] payload format for transporting\n the coordinates of a dynamic pointer that may be used during a\n presentation. Although a mouse can be used as the pointer, this\n payload format is not intended and may not have all functionalities\n needed to implement a general mouse event transmission mechanism.\n\n1. Introduction\n\n In most presentations, significant information is conveyed through\n the use of viewgraphs and a pointer. This makes accurate transmission\n of them vital in remote conferencing applications. Using regular\n video of a presenter's display for this purpose is problematic\n because, while the viewgraphs require a high spatial resolution, the\n pointer movements need to be sampled and transmitted at a high\n temporal resolution so that the presenter's pointing actions can be\n displayed synchronously with the corresponding audio and video\n signals. In m 2862 key presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 3009","type":"specification","body":"IETF","designation":"RFC 3009","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3009.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3009.txt","https://www.rfc-editor.org/rfc/rfc3009.pdf"],"folder":"IETF/RFC-3009","files":{"txt":{"path":"standards/IETF/RFC-3009/RFC-3009.txt","sha256":"d8c7ea3cd5e0330e91bc981397e5e68d290feee54001136e0c5ef06fea88ba3e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Rosenberg\nRequest for Comments: 3009 dynamicsoft\nCategory: Standards Track H. Schulzrinne\n Columbia U.\n November 2000\n\n Registration of parityfec MIME types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The RTP (Real-time Transport Protocol) payload format for generic\n forward error correction allows RTP participants to improve loss\n resiliency through the use of traditional parity-based channel codes.\n This payload format requires four new MIME types, audio","scope_keywords":["3009","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null}],"search_text":"IETF RFC 3009 Network Working Group J. Rosenberg\nRequest for Comments: 3009 dynamicsoft\nCategory: Standards Track H. Schulzrinne\n Columbia U.\n November 2000\n\n Registration of parityfec MIME types\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The RTP (Real-time Transport Protocol) payload format for generic\n forward error correction allows RTP participants to improve loss\n resiliency through the use of traditional parity-based channel codes.\n This payload format requires four new MIME types, audio 3009 subject nested-reference unchanged"},{"id":"IETF RFC 3016","type":"specification","body":"IETF","designation":"RFC 3016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3016.txt","https://www.rfc-editor.org/rfc/rfc3016.pdf"],"folder":"IETF/RFC-3016","files":{"txt":{"path":"standards/IETF/RFC-3016/RFC-3016.txt","sha256":"7ad5db851b4784e47c06690fed0eead70c721ce79d6d98ee227c11592941d0cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Real-Time Transport Protocol (RTP) payload\n formats for carrying each of MPEG-4 Audio and MPEG-4 Visual\n bitstreams without using MPEG-4 Systems. For the purpose of directly\n mapping MPEG-4 Audio/Visual bitstreams onto RTP packets, it provides\n specifications for the use of RTP header fields and also specifies\n fragmentation rules. It also provides specifications for\n Multipurpose Internet Mail Extensions (MIME) type registrations and\n the use of Session Description Protocol (SDP).\n\n1. Introduction\n\n The RTP payload formats described in this document specify how MPEG-4\n Audio [3][5] and MPEG-4 Visual streams [2][4] are to be fragmented\n and mapped directly onto RTP packets.\n\n These RTP payload formats enable transport of MPEG-4 Audio/Visual\n streams without using the synchronization and stream management\n functionality of MPEG-4 Systems [6]. Such RTP payload forma","scope_keywords":["3016","attribute","management","timestamp","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null}],"search_text":"IETF RFC 3016 This document describes Real-Time Transport Protocol (RTP) payload\n formats for carrying each of MPEG-4 Audio and MPEG-4 Visual\n bitstreams without using MPEG-4 Systems. For the purpose of directly\n mapping MPEG-4 Audio/Visual bitstreams onto RTP packets, it provides\n specifications for the use of RTP header fields and also specifies\n fragmentation rules. It also provides specifications for\n Multipurpose Internet Mail Extensions (MIME) type registrations and\n the use of Session Description Protocol (SDP).\n\n1. Introduction\n\n The RTP payload formats described in this document specify how MPEG-4\n Audio [3][5] and MPEG-4 Visual streams [2][4] are to be fragmented\n and mapped directly onto RTP packets.\n\n These RTP payload formats enable transport of MPEG-4 Audio/Visual\n streams without using the synchronization and stream management\n functionality of MPEG-4 Systems [6]. Such RTP payload forma 3016 attribute management timestamp tsp nested-reference unchanged"},{"id":"IETF RFC 3264","type":"specification","body":"IETF","designation":"RFC 3264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3264.txt","https://www.rfc-editor.org/rfc/rfc3264.pdf"],"folder":"IETF/RFC-3264","files":{"txt":{"path":"standards/IETF/RFC-3264/RFC-3264.txt","sha256":"c1cd87b1310c4bba1c0cd5dc1dbcf94afc294c32981c8630484ca97cc2f0e97c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism by which two entities can make use\n of the Session Description Protocol (SDP) to arrive at a common view\n of a multimedia session between them. In the model, one participant\n offers the other a description of the desired session from their\n perspective, and the other participant answers with the desired\n session from their perspective. This offer/answer model is most\n useful in unicast sessions where information from both participants\n is needed for the complete view of the session. The offer/answer\n model is used by protocols like the Session Initiation Protocol\n (SIP).","scope_keywords":["3264","attribute","attributes","key","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3262","folder":"IETF/RFC-3262","source":"IETF/RFC-3262/RFC-3262.txt","version":null},{"body":"IETF","designation":"RFC 3311","folder":"IETF/RFC-3311","source":"IETF/RFC-3311/RFC-3311.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3665","folder":"IETF/RFC-3665","source":"IETF/RFC-3665/RFC-3665.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4475","folder":"IETF/RFC-4475","source":"IETF/RFC-4475/RFC-4475.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8035","folder":"IETF/RFC-8035","source":"IETF/RFC-8035/RFC-8035.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 3264 This document defines a mechanism by which two entities can make use\n of the Session Description Protocol (SDP) to arrive at a common view\n of a multimedia session between them. In the model, one participant\n offers the other a description of the desired session from their\n perspective, and the other participant answers with the desired\n session from their perspective. This offer/answer model is most\n useful in unicast sessions where information from both participants\n is needed for the complete view of the session. The offer/answer\n model is used by protocols like the Session Initiation Protocol\n (SIP). 3264 attribute attributes key tsp nested-reference unchanged"},{"id":"IETF RFC 3267","type":"specification","body":"IETF","designation":"RFC 3267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3267.txt","https://www.rfc-editor.org/rfc/rfc3267.pdf"],"folder":"IETF/RFC-3267","files":{"txt":{"path":"standards/IETF/RFC-3267/RFC-3267.txt","sha256":"0e59f58975fc02724349e19109b7ee1e4b2463d64ab059c3ae253cd978d9fd65"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a real-time transport protocol (RTP) payload\n format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-\n Rate Wideband (AMR-WB) encoded speech signals. The payload format is\n designed to be able to interoperate with existing AMR and AMR-WB\n transport formats on non-IP networks. In addition, a file format is\n specified for transport of AMR and AMR-WB speech data in storage mode\n applications such as email. Two separate MIME type registrations are\n included, one for AMR and one for AMR-WB, specifying use of both the\n RTP payload format and the storage format.\n\nSjoberg, et. al. Standards Track [Page 1]\n\f\nRFC 3267 RTP Payload Format for AMR and AMR-WB June 2002","scope_keywords":["3267","algorithm","authentication","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3839","folder":"IETF/RFC-3839","source":"IETF/RFC-3839/RFC-3839.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null}],"search_text":"IETF RFC 3267 This document specifies a real-time transport protocol (RTP) payload\n format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-\n Rate Wideband (AMR-WB) encoded speech signals. The payload format is\n designed to be able to interoperate with existing AMR and AMR-WB\n transport formats on non-IP networks. In addition, a file format is\n specified for transport of AMR and AMR-WB speech data in storage mode\n applications such as email. Two separate MIME type registrations are\n included, one for AMR and one for AMR-WB, specifying use of both the\n RTP payload format and the storage format.\n\nSjoberg, et. al. Standards Track [Page 1]\n\f\nRFC 3267 RTP Payload Format for AMR and AMR-WB June 2002 3267 algorithm authentication key validation nested-reference unchanged"},{"id":"IETF RFC 3303","type":"specification","body":"IETF","designation":"RFC 3303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3303.txt","https://www.rfc-editor.org/rfc/rfc3303.pdf"],"folder":"IETF/RFC-3303","files":{"txt":{"path":"standards/IETF/RFC-3303/RFC-3303.txt","sha256":"6ea5db25ce49473d04e5abd0db05ac059c8e725678baf25de913e39ab50f0457"}},"tags":["nested-reference","unchanged"],"summary":"A principal objective of this document is to describe the underlying\n framework of middlebox communications (MIDCOM) to enable complex\n applications through the middleboxes, seamlessly using a trusted\n third party. This document and a companion document on MIDCOM\n requirements ([REQMTS]) have been created as a precursor to\n rechartering the MIDCOM working group.\n\n There are a variety of intermediate devices in the Internet today\n that require application intelligence for their operation. Datagrams\n pertaining to real-time streaming applications, such as SIP and\n H.323, and peer-to-peer applications, such as Napster and NetMeeting,\n cannot be identified by merely examining packet headers. Middleboxes\n implementing Firewall and Network Address Translator services\n typically embed application intelligence within the device for their\n operation. The document specifies an architecture and fra","scope_keywords":["3303","authorization","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3304","folder":"IETF/RFC-3304","source":"IETF/RFC-3304/RFC-3304.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 3303 A principal objective of this document is to describe the underlying\n framework of middlebox communications (MIDCOM) to enable complex\n applications through the middleboxes, seamlessly using a trusted\n third party. This document and a companion document on MIDCOM\n requirements ([REQMTS]) have been created as a precursor to\n rechartering the MIDCOM working group.\n\n There are a variety of intermediate devices in the Internet today\n that require application intelligence for their operation. Datagrams\n pertaining to real-time streaming applications, such as SIP and\n H.323, and peer-to-peer applications, such as Napster and NetMeeting,\n cannot be identified by merely examining packet headers. Middleboxes\n implementing Firewall and Network Address Translator services\n typically embed application intelligence within the device for their\n operation. The document specifies an architecture and fra 3303 authorization path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 3304","type":"specification","body":"IETF","designation":"RFC 3304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3304.txt","https://www.rfc-editor.org/rfc/rfc3304.pdf"],"folder":"IETF/RFC-3304","files":{"txt":{"path":"standards/IETF/RFC-3304/RFC-3304.txt","sha256":"741bea2e2beac1a9eaa3262f3a9cfef29e1ed9559605a0a7e45840aa4d508b8c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements that the Middlebox\n Communication (midcom) protocol must satisfy in order to meet the\n needs of applications wishing to influence the middlebox function.\n These requirements were developed with a specific focus on network\n address translation and firewall middleboxes.\n\n1. Introduction\n\n This document is one of two developed by the Middlebox Communication\n (midcom) working group to address the requirements and framework for\n a protocol between middleboxes and \"midcom agents.\" This document\n presents midcom requirements; [MCFW] presents the context and\n framework. [MCFW] also presents terminology and definitions and\n should be read in tandem with this one.\n\n These requirements were developed by examining the midcom framework\n and extracting requirements, both explicit and implicit, that\n appeared there.\n\nSwale, et al. Informational [Page 1]\n\f\nRFC 33","scope_keywords":["3304","authentication","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null}],"search_text":"IETF RFC 3304 This document specifies the requirements that the Middlebox\n Communication (midcom) protocol must satisfy in order to meet the\n needs of applications wishing to influence the middlebox function.\n These requirements were developed with a specific focus on network\n address translation and firewall middleboxes.\n\n1. Introduction\n\n This document is one of two developed by the Middlebox Communication\n (midcom) working group to address the requirements and framework for\n a protocol between middleboxes and \"midcom agents.\" This document\n presents midcom requirements; [MCFW] presents the context and\n framework. [MCFW] also presents terminology and definitions and\n should be read in tandem with this one.\n\n These requirements were developed by examining the midcom framework\n and extracting requirements, both explicit and implicit, that\n appeared there.\n\nSwale, et al. Informational [Page 1]\n\f\nRFC 33 3304 authentication identification nested-reference unchanged"},{"id":"IETF RFC 3312","type":"specification","body":"IETF","designation":"RFC 3312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3312.txt","https://www.rfc-editor.org/rfc/rfc3312.pdf"],"folder":"IETF/RFC-3312","files":{"pdf":{"path":"standards/IETF/RFC-3312/RFC-3312.pdf","sha256":"55a1c044b5ad5a19e5ae286e46f3c76a4c5c1204e7cf4e93c66fe7f86fba56cf"},"txt":{"path":"standards/IETF/RFC-3312/RFC-3312.txt","sha256":"577090b9beeced1cab4693dd6666ce5a675d262e0c54456c665cc4da1df05354"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a generic framework for preconditions, which\n are extensible through IANA registration. This document also\n discusses how network quality of service can be made a precondition\n for establishment of sessions initiated by the Session Initiation\n Protocol (SIP). These preconditions require that the participant\n reserve network resources before continuing with the session. We do\n not define new quality of service reservation mechanisms; these\n preconditions simply require a participant to use existing resource\n reservation mechanisms before beginning the session.\n\nCamarillo, et. al. Standards Track [Page 1]\n\f\nRFC 3312 Integration of Resource Management and SIP October 2002","scope_keywords":["3312","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 3312 This document defines a generic framework for preconditions, which\n are extensible through IANA registration. This document also\n discusses how network quality of service can be made a precondition\n for establishment of sessions initiated by the Session Initiation\n Protocol (SIP). These preconditions require that the participant\n reserve network resources before continuing with the session. We do\n not define new quality of service reservation mechanisms; these\n preconditions simply require a participant to use existing resource\n reservation mechanisms before beginning the session.\n\nCamarillo, et. al. Standards Track [Page 1]\n\f\nRFC 3312 Integration of Resource Management and SIP October 2002 3312 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 3323","type":"specification","body":"IETF","designation":"RFC 3323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3323.txt","https://www.rfc-editor.org/rfc/rfc3323.pdf"],"folder":"IETF/RFC-3323","files":{"txt":{"path":"standards/IETF/RFC-3323/RFC-3323.txt","sha256":"add46a088e660bbb3239523c46f15637b654c4ca81768f737d222ad97e9189c0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new mechanisms for the Session Initiation\n Protocol (SIP) in support of privacy. Specifically, guidelines are\n provided for the creation of messages that do not divulge personal\n identity information. A new \"privacy service\" logical role for\n intermediaries is defined to answer some privacy requirements that\n user agents cannot satisfy themselves. Finally, means are presented\n by which a user can request particular functions from a privacy\n service.","scope_keywords":["3323","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3325","folder":"IETF/RFC-3325","source":"IETF/RFC-3325/RFC-3325.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 3323 This document defines new mechanisms for the Session Initiation\n Protocol (SIP) in support of privacy. Specifically, guidelines are\n provided for the creation of messages that do not divulge personal\n identity information. A new \"privacy service\" logical role for\n intermediaries is defined to answer some privacy requirements that\n user agents cannot satisfy themselves. Finally, means are presented\n by which a user can request particular functions from a privacy\n service. 3323 key policy nested-reference unchanged"},{"id":"IETF RFC 3388","type":"specification","body":"IETF","designation":"RFC 3388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3388.txt","https://www.rfc-editor.org/rfc/rfc3388.pdf"],"folder":"IETF/RFC-3388","files":{"txt":{"path":"standards/IETF/RFC-3388/RFC-3388.txt","sha256":"fed7e5f0329a2607be4429e39ccc90739657fac04de09359b70ba61efa79ff29"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two Session Description Protocol (SDP)\n attributes: \"group\" and \"mid\". They allow to group together several\n \"m\" lines for two different purposes: for lip synchronization and for\n receiving media from a single flow (several media streams) that are\n encoded in different formats during a particular session, on\n different ports and host interfaces.","scope_keywords":["3388","attribute","attributes","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 4091","folder":"IETF/RFC-4091","source":"IETF/RFC-4091/RFC-4091.txt","version":null},{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4756","folder":"IETF/RFC-4756","source":"IETF/RFC-4756/RFC-4756.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null}],"search_text":"IETF RFC 3388 This document defines two Session Description Protocol (SDP)\n attributes: \"group\" and \"mid\". They allow to group together several\n \"m\" lines for two different purposes: for lip synchronization and for\n receiving media from a single flow (several media streams) that are\n encoded in different formats during a particular session, on\n different ports and host interfaces. 3388 attribute attributes identification key nested-reference unchanged"},{"id":"IETF RFC 3389","type":"specification","body":"IETF","designation":"RFC 3389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3389.txt","https://www.rfc-editor.org/rfc/rfc3389.pdf"],"folder":"IETF/RFC-3389","files":{"txt":{"path":"standards/IETF/RFC-3389/RFC-3389.txt","sha256":"abd69a5eac6c8b27727db958909d283a53d066bd032d425e84a089a8f63142f0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Real-time Transport Protocol (RTP) payload\n format for transporting comfort noise (CN). The CN payload type is\n primarily for use with audio codecs that do not support comfort noise\n as part of the codec itself such as ITU-T Recommendations G.711,\n G.726, G.727, G.728, and G.722.\n\n1. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [7].\n\n2. Introduction\n\n This document describes a RTP [1] payload format for transporting\n comfort noise. The payload format is based on Appendix II of ITU-T\n Recommendation G.711 [8] which defines a comfort noise payload format\n (or bit-stream) for ITU-T G.711 [2] use in packet-based multimedia\n communication systems. The payload format is generic and may","scope_keywords":["3389","algorithm","algorithms","key","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 3389 This document describes a Real-time Transport Protocol (RTP) payload\n format for transporting comfort noise (CN). The CN payload type is\n primarily for use with audio codecs that do not support comfort noise\n as part of the codec itself such as ITU-T Recommendations G.711,\n G.726, G.727, G.728, and G.722.\n\n1. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC-2119 [7].\n\n2. Introduction\n\n This document describes a RTP [1] payload format for transporting\n comfort noise. The payload format is based on Appendix II of ITU-T\n Recommendation G.711 [8] which defines a comfort noise payload format\n (or bit-stream) for ITU-T G.711 [2] use in packet-based multimedia\n communication systems. The payload format is generic and may 3389 algorithm algorithms key presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 3393","type":"specification","body":"IETF","designation":"RFC 3393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3393.txt","https://www.rfc-editor.org/rfc/rfc3393.pdf"],"folder":"IETF/RFC-3393","files":{"txt":{"path":"standards/IETF/RFC-3393/RFC-3393.txt","sha256":"bd9170bd9d9fe7fa6deda27198d90a067d300e4d755b0c2ab5c880016ec72f2c"}},"tags":["nested-reference","unchanged"],"summary":"This document refers to a metric for variation in delay of packets\n across Internet paths. The metric is based on the difference in the\n One-Way-Delay of selected packets. This difference in delay is\n called \"IP Packet Delay Variation (ipdv)\".\n\n The metric is valid for measurements between two hosts both in the\n case that they have synchronized clocks and in the case that they are\n not synchronized. We discuss both in this document.","scope_keywords":["3393","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null}],"search_text":"IETF RFC 3393 This document refers to a metric for variation in delay of packets\n across Internet paths. The metric is based on the difference in the\n One-Way-Delay of selected packets. This difference in delay is\n called \"IP Packet Delay Variation (ipdv)\".\n\n The metric is valid for measurements between two hosts both in the\n case that they have synchronized clocks and in the case that they are\n not synchronized. We discuss both in this document. 3393 delivery key path nested-reference unchanged"},{"id":"IETF RFC 3448","type":"specification","body":"IETF","designation":"RFC 3448","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3448.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3448.txt","https://www.rfc-editor.org/rfc/rfc3448.pdf"],"folder":"IETF/RFC-3448","files":{"txt":{"path":"standards/IETF/RFC-3448/RFC-3448.txt","sha256":"1580f01c80af65ed4566bba1367af52b473c06866212050f77bde179f7bc8a12"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies TCP-Friendly Rate Control (TFRC). TFRC is a\n congestion control mechanism for unicast flows operating in a best-\n effort Internet environment. It is reasonably fair when competing\n for bandwidth with TCP flows, but has a much lower variation of\n throughput over time compared with TCP, making it more suitable for\n applications such as telephony or streaming media where a relatively\n smooth sending rate is of importance.","scope_keywords":["3448","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3649","folder":"IETF/RFC-3649","source":"IETF/RFC-3649/RFC-3649.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 3448 This document specifies TCP-Friendly Rate Control (TFRC). TFRC is a\n congestion control mechanism for unicast flows operating in a best-\n effort Internet environment. It is reasonably fair when competing\n for bandwidth with TCP flows, but has a much lower variation of\n throughput over time compared with TCP, making it more suitable for\n applications such as telephony or streaming media where a relatively\n smooth sending rate is of importance. 3448 key management nested-reference unchanged"},{"id":"IETF RFC 3605","type":"specification","body":"IETF","designation":"RFC 3605","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3605.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3605.txt","https://www.rfc-editor.org/rfc/rfc3605.pdf"],"folder":"IETF/RFC-3605","files":{"txt":{"path":"standards/IETF/RFC-3605/RFC-3605.txt","sha256":"f6ad0ca531004bfb9aa14358c11d5edefcc837725fba2816847c96e41b723134"}},"tags":["nested-reference","unchanged"],"summary":"The Session Description Protocol (SDP) is used to describe the\n parameters of media streams used in multimedia sessions. When a\n session requires multiple ports, SDP assumes that these ports have\n consecutive numbers. However, when the session crosses a network\n address translation device that also uses port mapping, the ordering\n of ports can be destroyed by the translation. To handle this, we\n propose an extension attribute to SDP.\n\n1. Introduction\n\n The session invitation protocol (SIP, [RFC3261]) is often used to\n establish multi-media sessions on the Internet. There are often\n cases today in which one or both ends of the connection are hidden\n behind a network address translation device [RFC2766]. In this case,\n the SDP text must document the IP addresses and UDP ports as they\n appear on the \"public Internet\" side of the NAT. In this memo, we\n will suppose that the host located behi","scope_keywords":["3605","algorithm","attribute","attributes","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3605 The Session Description Protocol (SDP) is used to describe the\n parameters of media streams used in multimedia sessions. When a\n session requires multiple ports, SDP assumes that these ports have\n consecutive numbers. However, when the session crosses a network\n address translation device that also uses port mapping, the ordering\n of ports can be destroyed by the translation. To handle this, we\n propose an extension attribute to SDP.\n\n1. Introduction\n\n The session invitation protocol (SIP, [RFC3261]) is often used to\n establish multi-media sessions on the Internet. There are often\n cases today in which one or both ends of the connection are hidden\n behind a network address translation device [RFC2766]. In this case,\n the SDP text must document the IP addresses and UDP ports as they\n appear on the \"public Internet\" side of the NAT. In this memo, we\n will suppose that the host located behi 3605 algorithm attribute attributes crl key nested-reference unchanged"},{"id":"IETF RFC 4888","type":"specification","body":"IETF","designation":"RFC 4888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4888.txt","https://www.rfc-editor.org/rfc/rfc4888.pdf"],"folder":"IETF/RFC-4888","files":{"txt":{"path":"standards/IETF/RFC-4888/RFC-4888.txt","sha256":"6f2d3eb3193cbd475ece1221cb388a821cc638c8e68394e2de5095e391a23a00"}},"tags":["nested-reference","unchanged"],"summary":"With current Network Mobility (NEMO) Basic Support, all\n communications to and from Mobile Network Nodes must go through the\n bi-directional tunnel established between the Mobile Router and Home\n Agent when the mobile network is away. This sub-optimal routing\n results in various inefficiencies associated with packet delivery,\n such as increased delay and bottleneck links leading to traffic\n congestion, which can ultimately disrupt all communications to and\n from the Mobile Network Nodes. Additionally, with nesting of Mobile\n Networks, these inefficiencies get compounded, and stalemate\n conditions may occur in specific dispositions. This document\n investigates such problems and provides the motivation behind Route\n Optimization (RO) for NEMO.\n\nNg, et al. Informational [Page 1]\n\f\nRFC 4888 NEMO RO Problem Statement July 2007","scope_keywords":["4888","delivery","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null}],"search_text":"IETF RFC 4888 With current Network Mobility (NEMO) Basic Support, all\n communications to and from Mobile Network Nodes must go through the\n bi-directional tunnel established between the Mobile Router and Home\n Agent when the mobile network is away. This sub-optimal routing\n results in various inefficiencies associated with packet delivery,\n such as increased delay and bottleneck links leading to traffic\n congestion, which can ultimately disrupt all communications to and\n from the Mobile Network Nodes. Additionally, with nesting of Mobile\n Networks, these inefficiencies get compounded, and stalemate\n conditions may occur in specific dispositions. This document\n investigates such problems and provides the motivation behind Route\n Optimization (RO) for NEMO.\n\nNg, et al. Informational [Page 1]\n\f\nRFC 4888 NEMO RO Problem Statement July 2007 4888 delivery path policy trust nested-reference unchanged"},{"id":"IETF RFC 5888","type":"specification","body":"IETF","designation":"RFC 5888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5888.txt","https://www.rfc-editor.org/rfc/rfc5888.pdf"],"folder":"IETF/RFC-5888","files":{"txt":{"path":"standards/IETF/RFC-5888/RFC-5888.txt","sha256":"620670094df4a03edc8e6aa61c733754aea8ff66b83cfbdfbf845144ee6b8857"}},"tags":["nested-reference","unchanged"],"summary":"In this specification, we define a framework to group \"m\" lines in\n the Session Description Protocol (SDP) for different purposes. This\n framework uses the \"group\" and \"mid\" SDP attributes, both of which\n are defined in this specification. Additionally, we specify how to\n use the framework for two different purposes: for lip synchronization\n and for receiving a media flow consisting of several media streams on\n different transport addresses. This document obsoletes RFC 3388.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about ","scope_keywords":["5888","attribute","attributes","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5888 In this specification, we define a framework to group \"m\" lines in\n the Session Description Protocol (SDP) for different purposes. This\n framework uses the \"group\" and \"mid\" SDP attributes, both of which\n are defined in this specification. Additionally, we specify how to\n use the framework for two different purposes: for lip synchronization\n and for receiving a media flow consisting of several media streams on\n different transport addresses. This document obsoletes RFC 3388.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about  5888 attribute attributes http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 189","type":"specification","body":"IETF","designation":"RFC 189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc189.txt","https://www.rfc-editor.org/rfc/rfc189.pdf"],"folder":"IETF/RFC-189","files":{"txt":{"path":"standards/IETF/RFC-189/RFC-189.txt","sha256":"e06d55c9a7f5c557ecb6f5f45381925e62ba8b8b28268866efb658b53e7dfbf6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. T. Braden\nRequest for Comments: 189 UCLA/CCN\nObsoletes: RFC 88 (NIC 5668) 15 July 1971\nNIC 7133\nCategory: D\n\n INTERIM NETRJS SPECIFICATIONS\n\n The following document describes the operation and protocol of the\n remote job entry service to CCN's 360 Model 91. The interim protocol\n described here will be implemented as a production service before the\n end of July. Two host sites (Rand and UCLA/NMC) have written user\n processes for the interim NETRJS, based on the attached document.\n Questions on it should be addressed to CCN's Technical Liaison.\n\n It is anticipated that the interim protocol will be superseded in a\n few months by a revised NETRJS, but the changes will be minor. The\n revision will bring the data transfer protocol of NETRJS into\n complete conformity with the proposed Data Transfer Protocol DTP (see\n RFC #171). The present differences between the DTP an","scope_keywords":["189","conformity"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 385","folder":"IETF/RFC-385","source":"IETF/RFC-385/RFC-385.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null}],"search_text":"IETF RFC 189 Network Working Group R. T. Braden\nRequest for Comments: 189 UCLA/CCN\nObsoletes: RFC 88 (NIC 5668) 15 July 1971\nNIC 7133\nCategory: D\n\n INTERIM NETRJS SPECIFICATIONS\n\n The following document describes the operation and protocol of the\n remote job entry service to CCN's 360 Model 91. The interim protocol\n described here will be implemented as a production service before the\n end of July. Two host sites (Rand and UCLA/NMC) have written user\n processes for the interim NETRJS, based on the attached document.\n Questions on it should be addressed to CCN's Technical Liaison.\n\n It is anticipated that the interim protocol will be superseded in a\n few months by a revised NETRJS, but the changes will be minor. The\n revision will bring the data transfer protocol of NETRJS into\n complete conformity with the proposed Data Transfer Protocol DTP (see\n RFC #171). The present differences between the DTP an 189 conformity nested-reference unchanged"},{"id":"IETF RFC 385","type":"specification","body":"IETF","designation":"RFC 385","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc385.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc385.txt","https://www.rfc-editor.org/rfc/rfc385.pdf"],"folder":"IETF/RFC-385","files":{"txt":{"path":"standards/IETF/RFC-385/RFC-385.txt","sha256":"80a748c2cbc6f33c5e49aa22efd73ba62260a9c448857b7cc9d57b2414106cc4"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 385 Abhay K. Bhushan\nNIC 11357 MIT-MAC\nUpdates: RFC 354 August 18, 1972\nRFC 354\n\n COMMENTS ON THE FILE TRANSFER PROTOCOL (RFC 354)\n ------------------------------------------------\n\n The following comments pertain to the File Transfer Protocol, NWG/RFC\n 354. The comments include errata, further discussion, emphasis\n points, and additions to the protocol. I shall incorporate these\n comments into the main protocol document after we have had sufficient\n experience.\n\n 1. Please note the following corrections:\n (i) Page 2, line 15: replace user-FTP by server-FTP.\n (ii) Page 3, line 12: replace III.A by III.C.\n (iii) Page 15, last para, line 1: replace user s by user is.\n (iv) Page 28, line 21: replace CRCRLF by CRLF.\n (v) Page 27, line 10: replace 451,451 by 451.\n (vi) Note that on Page 26, line 15 mode code is S|B|T|H.\n\n 2. The language of RFC 354 reads that it is recommended for\n ho","scope_keywords":["385","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 414","folder":"IETF/RFC-414","source":"IETF/RFC-414/RFC-414.txt","version":null},{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 448","folder":"IETF/RFC-448","source":"IETF/RFC-448/RFC-448.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null},{"body":"IETF","designation":"RFC 686","folder":"IETF/RFC-686","source":"IETF/RFC-686/RFC-686.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 385 NWG/RFC 385 Abhay K. Bhushan\nNIC 11357 MIT-MAC\nUpdates: RFC 354 August 18, 1972\nRFC 354\n\n COMMENTS ON THE FILE TRANSFER PROTOCOL (RFC 354)\n ------------------------------------------------\n\n The following comments pertain to the File Transfer Protocol, NWG/RFC\n 354. The comments include errata, further discussion, emphasis\n points, and additions to the protocol. I shall incorporate these\n comments into the main protocol document after we have had sufficient\n experience.\n\n 1. Please note the following corrections:\n (i) Page 2, line 15: replace user-FTP by server-FTP.\n (ii) Page 3, line 12: replace III.A by III.C.\n (iii) Page 15, last para, line 1: replace user s by user is.\n (iv) Page 28, line 21: replace CRCRLF by CRLF.\n (v) Page 27, line 10: replace 451,451 by 451.\n (vi) Note that on Page 26, line 15 mode code is S|B|T|H.\n\n 2. The language of RFC 354 reads that it is recommended for\n ho 385 crl presentation nested-reference unchanged"},{"id":"IETF RFC 454","type":"specification","body":"IETF","designation":"RFC 454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc454.txt","https://www.rfc-editor.org/rfc/rfc454.pdf"],"folder":"IETF/RFC-454","files":{"txt":{"path":"standards/IETF/RFC-454/RFC-454.txt","sha256":"0f26522db8c81056063302a4f199d7c5ad5aac3100de995b76d63bf59589560c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 454 BBN\nNIC: 14333 16 February 1973\n\n FILE TRANSFER PROTOCOL\n\n Meeting Announcement and a New Proposed Document\n\n Attached is a new proposal for a File Transfer Protocol. The\n document is an extensive update to RFC 354 and, I believe,\n incorporates solutions to most of the objections to RFC 354.\n\n It now seems appropriate to make another attempt to reach final\n agreement on FTP. Accordingly, I am calling a meeting of interested\n parties, to be held at BBN on March 16, for discussion of this and\n other proposals.\n\n This note is directed to the network community at large, rather than\n specifically to the old FTP committee, because I don't believe that\n the FTP committee membership includes all the individuals who have\n contributed to the current state of FTP design. Nevertheless, it is\n intended that the meeting proceed from the curre","scope_keywords":["454","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 2235","folder":"IETF/RFC-2235","source":"IETF/RFC-2235/RFC-2235.txt","version":null},{"body":"IETF","designation":"RFC 448","folder":"IETF/RFC-448","source":"IETF/RFC-448/RFC-448.txt","version":null},{"body":"IETF","designation":"RFC 463","folder":"IETF/RFC-463","source":"IETF/RFC-463/RFC-463.txt","version":null},{"body":"IETF","designation":"RFC 468","folder":"IETF/RFC-468","source":"IETF/RFC-468/RFC-468.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 454 Network Working Group A. McKenzie\nRequest for Comments: 454 BBN\nNIC: 14333 16 February 1973\n\n FILE TRANSFER PROTOCOL\n\n Meeting Announcement and a New Proposed Document\n\n Attached is a new proposal for a File Transfer Protocol. The\n document is an extensive update to RFC 354 and, I believe,\n incorporates solutions to most of the objections to RFC 354.\n\n It now seems appropriate to make another attempt to reach final\n agreement on FTP. Accordingly, I am calling a meeting of interested\n parties, to be held at BBN on March 16, for discussion of this and\n other proposals.\n\n This note is directed to the network community at large, rather than\n specifically to the old FTP committee, because I don't believe that\n the FTP committee membership includes all the individuals who have\n contributed to the current state of FTP design. Nevertheless, it is\n intended that the meeting proceed from the curre 454 path nested-reference unchanged"},{"id":"IETF RFC 739","type":"specification","body":"IETF","designation":"RFC 739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc739.txt","https://www.rfc-editor.org/rfc/rfc739.pdf"],"folder":"IETF/RFC-739","files":{"txt":{"path":"standards/IETF/RFC-739/RFC-739.txt","sha256":"8a08315f70b9a9c7735c57390e76522379c300790c29c691cf4605f36b815a93"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 739 JBP 11 Nov 77 42341\nAssigned Numbers\n\nNetwork Working Group J. Postel\nRequest for Comments: 739 USC-ISI\nNIC: 42341 11 November 1977\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent and more g","scope_keywords":["739","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2204","folder":"IETF/RFC-2204","source":"IETF/RFC-2204/RFC-2204.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 739 NWG/RFC# 739 JBP 11 Nov 77 42341\nAssigned Numbers\n\nNetwork Working Group J. Postel\nRequest for Comments: 739 USC-ISI\nNIC: 42341 11 November 1977\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent and more g 739 authentication nested-reference unchanged"},{"id":"IETF RFC 3714","type":"specification","body":"IETF","designation":"RFC 3714","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3714.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3714.txt","https://www.rfc-editor.org/rfc/rfc3714.pdf"],"folder":"IETF/RFC-3714","files":{"txt":{"path":"standards/IETF/RFC-3714/RFC-3714.txt","sha256":"41e32cb5aa1b51c547147a6aa1731b618e8c0d25b5c4ff30a71316ec4828cb7b"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses IAB concerns about effective end-to-end\n congestion control for best-effort voice traffic in the Internet.\n These concerns have to do with fairness, user quality, and with the\n dangers of congestion collapse. The concerns are particularly\n relevant in light of the absence of a widespread Quality of Service\n (QoS) deployment in the Internet, and the likelihood that this\n situation will not change much in the near term. This document is\n not making any recommendations about deployment paths for Voice over\n Internet Protocol (VoIP) in terms of QoS support, and is not claiming\n that best-effort service can be relied upon to give acceptable\n performance for VoIP. We are merely observing that voice traffic is\n occasionally deployed as best-effort traffic over some links in the\n Internet, that we expect this occasional deployment to continue, and\n that we have concerns a","scope_keywords":["3714","path","pid","pki","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 5033","folder":"IETF/RFC-5033","source":"IETF/RFC-5033/RFC-5033.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null}],"search_text":"IETF RFC 3714 This document discusses IAB concerns about effective end-to-end\n congestion control for best-effort voice traffic in the Internet.\n These concerns have to do with fairness, user quality, and with the\n dangers of congestion collapse. The concerns are particularly\n relevant in light of the absence of a widespread Quality of Service\n (QoS) deployment in the Internet, and the likelihood that this\n situation will not change much in the near term. This document is\n not making any recommendations about deployment paths for Voice over\n Internet Protocol (VoIP) in terms of QoS support, and is not claiming\n that best-effort service can be relied upon to give acceptable\n performance for VoIP. We are merely observing that voice traffic is\n occasionally deployed as best-effort traffic over some links in the\n Internet, that we expect this occasional deployment to continue, and\n that we have concerns a 3714 path pid pki subject nested-reference unchanged"},{"id":"IETF RFC 2532","type":"specification","body":"IETF","designation":"RFC 2532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2532.txt","https://www.rfc-editor.org/rfc/rfc2532.pdf"],"folder":"IETF/RFC-2532","files":{"txt":{"path":"standards/IETF/RFC-2532/RFC-2532.txt","sha256":"64f68fcfa1ccea2f745104d2809d3c21d939556dd8871d7481e84774fd9a7ef7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to \"Simple Mode of Facsimile Using\n Internet Mail\" [RFC2305] and describes additional features, including\n transmission of enhanced document characteristics (higher resolution,\n color) and confirmation of delivery and processing.\n\n These additional features are designed to provide the highest level\n of interoperability with the existing and future standards-compliant\n email infrastructure and mail user agents, while providing a level of\n service that approximates the level currently enjoyed by fax users.\n\n The IETF has been notified of intellectual property rights claimed in\n regard to some or all of the specification contained in this\n document. For more information consult the online list of claimed\n rights in <http://www.ietf.org/ipr.html>.\n\n1. Introduction\n\n This document notes a number of enhancements to the \"Simple Mode of\n Facsimile Using Interne","scope_keywords":["2532","delivery","http","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 4143","folder":"IETF/RFC-4143","source":"IETF/RFC-4143/RFC-4143.txt","version":null}],"search_text":"IETF RFC 2532 This document describes extensions to \"Simple Mode of Facsimile Using\n Internet Mail\" [RFC2305] and describes additional features, including\n transmission of enhanced document characteristics (higher resolution,\n color) and confirmation of delivery and processing.\n\n These additional features are designed to provide the highest level\n of interoperability with the existing and future standards-compliant\n email infrastructure and mail user agents, while providing a level of\n service that approximates the level currently enjoyed by fax users.\n\n The IETF has been notified of intellectual property rights claimed in\n regard to some or all of the specification contained in this\n document. For more information consult the online list of claimed\n rights in <http://www.ietf.org/ipr.html>.\n\n1. Introduction\n\n This document notes a number of enhancements to the \"Simple Mode of\n Facsimile Using Interne 2532 delivery http key path subject nested-reference unchanged"},{"id":"IETF RFC 3249","type":"specification","body":"IETF","designation":"RFC 3249","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3249.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3249.txt","https://www.rfc-editor.org/rfc/rfc3249.pdf"],"folder":"IETF/RFC-3249","files":{"txt":{"path":"standards/IETF/RFC-3249/RFC-3249.txt","sha256":"e1024faff4bcf11c49e4733beac4f25b641cd246c3d05727f3742454ae0c680c"}},"tags":["nested-reference","unchanged"],"summary":"This document is intended for the implementers of software that use\n email to send to facsimiles using RFC 2305 and 2532. This is an\n informational document and its guidelines do not supersede the\n referenced documents.","scope_keywords":["3249","delivery","http","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"IETF RFC 3249 This document is intended for the implementers of software that use\n email to send to facsimiles using RFC 2305 and 2532. This is an\n informational document and its guidelines do not supersede the\n referenced documents. 3249 delivery http profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 3297","type":"specification","body":"IETF","designation":"RFC 3297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3297.txt","https://www.rfc-editor.org/rfc/rfc3297.pdf"],"folder":"IETF/RFC-3297","files":{"txt":{"path":"standards/IETF/RFC-3297/RFC-3297.txt","sha256":"a57866f5276da7a275d9558c323e7080eae5ef7b51806c055d33beaaeba07789"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a content negotiation mechanism for facsimile,\n voice and other messaging services that use Internet email.\n\n Services such as facsimile and voice messaging need to cope with new\n message content formats, yet need to ensure that the content of any\n given message is renderable by the receiving agent. The mechanism\n described here aims to meet these needs in a fashion that is fully\n compatible with the current behaviour and expectations of Internet\n email.","scope_keywords":["3297","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null}],"search_text":"IETF RFC 3297 This memo describes a content negotiation mechanism for facsimile,\n voice and other messaging services that use Internet email.\n\n Services such as facsimile and voice messaging need to cope with new\n message content formats, yet need to ensure that the content of any\n given message is renderable by the receiving agent. The mechanism\n described here aims to meet these needs in a fashion that is fully\n compatible with the current behaviour and expectations of Internet\n email. 3297 delivery nested-reference unchanged"},{"id":"IETF RFC 3462","type":"specification","body":"IETF","designation":"RFC 3462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3462.txt","https://www.rfc-editor.org/rfc/rfc3462.pdf"],"folder":"IETF/RFC-3462","files":{"txt":{"path":"standards/IETF/RFC-3462/RFC-3462.txt","sha256":"b574f40e3821e5e56729d5bb86d74e44c30469da3503ff57bc9898f40c6cb0f3"}},"tags":["nested-reference","unchanged"],"summary":"The Multipart/Report Multipurpose Internet Mail Extensions (MIME)\n content-type is a general \"family\" or \"container\" type for electronic\n mail reports of any kind. Although this memo defines only the use of\n the Multipart/Report content-type with respect to delivery status\n reports, mail processing programs will benefit if a single content-\n type is used to for all kinds of reports.\n\n This document is part of a four document set describing the delivery\n status report service. This collection includes the Simple Mail\n Transfer Protocol (SMTP) extensions to request delivery status\n reports, a MIME content for the reporting of delivery reports, an\n enumeration of extended status codes, and a multipart container for\n the delivery report, the original message, and a human-friendly\n summary of the failure.\n\nVaudreuil Standards Track [Page 1]\n\f\nRFC 3462 Multipart/Report January 2003","scope_keywords":["3462","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null}],"search_text":"IETF RFC 3462 The Multipart/Report Multipurpose Internet Mail Extensions (MIME)\n content-type is a general \"family\" or \"container\" type for electronic\n mail reports of any kind. Although this memo defines only the use of\n the Multipart/Report content-type with respect to delivery status\n reports, mail processing programs will benefit if a single content-\n type is used to for all kinds of reports.\n\n This document is part of a four document set describing the delivery\n status report service. This collection includes the Simple Mail\n Transfer Protocol (SMTP) extensions to request delivery status\n reports, a MIME content for the reporting of delivery reports, an\n enumeration of extended status codes, and a multipart container for\n the delivery report, the original message, and a human-friendly\n summary of the failure.\n\nVaudreuil Standards Track [Page 1]\n\f\nRFC 3462 Multipart/Report January 2003 3462 delivery key path nested-reference unchanged"},{"id":"IETF RFC 6522","type":"specification","body":"IETF","designation":"RFC 6522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6522.txt","https://www.rfc-editor.org/rfc/rfc6522.pdf"],"folder":"IETF/RFC-6522","files":{"txt":{"path":"standards/IETF/RFC-6522/RFC-6522.txt","sha256":"54f519e448093a7b045bea9e9074dfa89bbdf1593fcf7e39ea21ab3d6a03f27b"}},"tags":["nested-reference","unchanged"],"summary":"The multipart/report Multipurpose Internet Mail Extensions (MIME)\n media type is a general \"family\" or \"container\" type for electronic\n mail reports of any kind. Although this memo defines only the use of\n the multipart/report media type with respect to delivery status\n reports, mail processing programs will benefit if a single media type\n is used for all kinds of reports.\n\n This memo obsoletes \"The Multipart/Report Content Type for the\n Reporting of Mail System Administrative Messages\", RFC 3462, and\n marks RFC 3462 and its predecessor as \"Historic\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n ","scope_keywords":["6522","authentication","delivery","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null}],"search_text":"IETF RFC 6522 The multipart/report Multipurpose Internet Mail Extensions (MIME)\n media type is a general \"family\" or \"container\" type for electronic\n mail reports of any kind. Although this memo defines only the use of\n the multipart/report media type with respect to delivery status\n reports, mail processing programs will benefit if a single media type\n is used for all kinds of reports.\n\n This memo obsoletes \"The Multipart/Report Content Type for the\n Reporting of Mail System Administrative Messages\", RFC 3462, and\n marks RFC 3462 and its predecessor as \"Historic\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n  6522 authentication delivery http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 1893","type":"specification","body":"IETF","designation":"RFC 1893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1893.txt","https://www.rfc-editor.org/rfc/rfc1893.pdf"],"folder":"IETF/RFC-1893","files":{"txt":{"path":"standards/IETF/RFC-1893/RFC-1893.txt","sha256":"cd6a3514bbe1ba707ccbe91643b0a2add65c1c537b9b4c3a01399cc541286beb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Vaudreuil\nRequest for Comments: 1893 Octel Network Services\nCategory: Standards Track January 1996\n\n Enhanced Mail System Status Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n There currently is not a standard mechanism for the reporting of mail\n system errors except for the limited set offered by SMTP and the\n system specific text descriptions sent in mail messages. There is a\n pressing need for a rich machine readable status code for use in\n delivery status notifications [DSN]. This document proposes a new\n set of status codes for","scope_keywords":["1893","delivery","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 2034","folder":"IETF/RFC-2034","source":"IETF/RFC-2034/RFC-2034.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3463","folder":"IETF/RFC-3463","source":"IETF/RFC-3463/RFC-3463.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null}],"search_text":"IETF RFC 1893 Network Working Group G. Vaudreuil\nRequest for Comments: 1893 Octel Network Services\nCategory: Standards Track January 1996\n\n Enhanced Mail System Status Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Overview\n\n There currently is not a standard mechanism for the reporting of mail\n system errors except for the limited set offered by SMTP and the\n system specific text descriptions sent in mail messages. There is a\n pressing need for a rich machine readable status code for use in\n delivery status notifications [DSN]. This document proposes a new\n set of status codes for 1893 delivery registered subject nested-reference unchanged"},{"id":"IETF RFC 2530","type":"specification","body":"IETF","designation":"RFC 2530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2530.txt","https://www.rfc-editor.org/rfc/rfc2530.pdf"],"folder":"IETF/RFC-2530","files":{"txt":{"path":"standards/IETF/RFC-2530/RFC-2530.txt","sha256":"1665e6824a55d04f2bc713d8ff425fedd65b8a4f17c793e2c6f156c31dc8a838"}},"tags":["nested-reference","unchanged"],"summary":"There is a need in Internet mail and Internet fax for a recipient to\n indicate the media features it supports so that messages can be\n generated by senders without exceeding the recipient's abilities.\n\n This memo describes a format for generating Message Disposition\n Notifications [RFC2298] and Delivery Status Notifications [RFC1894]\n which contain such information. This information can be used by\n senders to avoid exceeding the recipient's capabilities when sending\n subsequent messages.\n\n2. Introduction\n\n The extensions described in this document can be used in Message\n Disposition Notifications [RFC2298] or Delivery Status Notifications\n [RFC1894], as appropriate for the implementation.\n\n Note that both DSNs and MDNs have drawbacks: DSNs are not available\n between all senders and receivers, and MDNs require the receiver to\n disclose message disposition information (or, if using the \"de","scope_keywords":["2530","crl","delivery","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2530 There is a need in Internet mail and Internet fax for a recipient to\n indicate the media features it supports so that messages can be\n generated by senders without exceeding the recipient's abilities.\n\n This memo describes a format for generating Message Disposition\n Notifications [RFC2298] and Delivery Status Notifications [RFC1894]\n which contain such information. This information can be used by\n senders to avoid exceeding the recipient's capabilities when sending\n subsequent messages.\n\n2. Introduction\n\n The extensions described in this document can be used in Message\n Disposition Notifications [RFC2298] or Delivery Status Notifications\n [RFC1894], as appropriate for the implementation.\n\n Note that both DSNs and MDNs have drawbacks: DSNs are not available\n between all senders and receivers, and MDNs require the receiver to\n disclose message disposition information (or, if using the \"de 2530 crl delivery key registered nested-reference unchanged"},{"id":"IETF RFC 3463","type":"specification","body":"IETF","designation":"RFC 3463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3463.txt","https://www.rfc-editor.org/rfc/rfc3463.pdf"],"folder":"IETF/RFC-3463","files":{"txt":{"path":"standards/IETF/RFC-3463/RFC-3463.txt","sha256":"ccfbf657f4d3ac7c89cca03bd1abed355efe3f4b170162e32a6ff344cebfe851"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of extended status codes for use within\n the mail system for delivery status reports, tracking, and improved\n diagnostics. In combination with other information provided in the\n Delivery Status Notification (DSN) delivery report, these codes\n facilitate media and language independent rendering of message\n delivery status.","scope_keywords":["3463","delivery","key","policy","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 3463 This document defines a set of extended status codes for use within\n the mail system for delivery status reports, tracking, and improved\n diagnostics. In combination with other information provided in the\n Delivery Status Notification (DSN) delivery report, these codes\n facilitate media and language independent rendering of message\n delivery status. 3463 delivery key policy registered subject nested-reference unchanged"},{"id":"IETF RFC 5248","type":"specification","body":"IETF","designation":"RFC 5248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5248.txt","https://www.rfc-editor.org/rfc/rfc5248.pdf"],"folder":"IETF/RFC-5248","files":{"txt":{"path":"standards/IETF/RFC-5248/RFC-5248.txt","sha256":"b5d93474fead6927bcce9d233d7cf9ee8bb597c55c80ae6bc97ead8fd4a1c310"}},"tags":["nested-reference","unchanged"],"summary":"The specification for enhanced mail system status codes, RFC 3463,\n establishes a new code model and lists a collection of status codes.\n While it anticipated that more codes would be added over time, it did\n not provide an explicit mechanism for registering and tracking those\n codes. This document specifies an IANA registry for mail system\n enhanced status codes, and initializes that registry with the codes\n so far established in published standards-track documents, as well as\n other codes that have become established in the industry.","scope_keywords":["5248","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null}],"search_text":"IETF RFC 5248 The specification for enhanced mail system status codes, RFC 3463,\n establishes a new code model and lists a collection of status codes.\n While it anticipated that more codes would be added over time, it did\n not provide an explicit mechanism for registering and tracking those\n codes. This document specifies an IANA registry for mail system\n enhanced status codes, and initializes that registry with the codes\n so far established in published standards-track documents, as well as\n other codes that have become established in the industry. 5248 subject nested-reference unchanged"},{"id":"IETF RFC 3676","type":"specification","body":"IETF","designation":"RFC 3676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3676.txt","https://www.rfc-editor.org/rfc/rfc3676.pdf"],"folder":"IETF/RFC-3676","files":{"txt":{"path":"standards/IETF/RFC-3676/RFC-3676.txt","sha256":"70da6cf9fa29640104feab81161fefcd2bf3ee3dc0f3ce8efd31ccc92db0aacf"}},"tags":["nested-reference","unchanged"],"summary":"This specification establishes two parameters (Format and DelSP) to\n be used with the Text/Plain media type. In the presence of these\n parameters, trailing whitespace is used to indicate flowed lines and\n a canonical quote indicator is used to indicate quoted lines. This\n results in an encoding which appears as normal Text/Plain in older\n implementations, since it is in fact normal Text/Plain, yet provides\n for superior wrapping/flowing, and quoting.\n\n This document supersedes the one specified in RFC 2646, \"The\n Text/Plain Format Parameter\", and adds the DelSp parameter to\n accommodate languages/coded character sets in which ASCII spaces are\n not used or appear rarely.","scope_keywords":["3676","crl","encryption","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null}],"search_text":"IETF RFC 3676 This specification establishes two parameters (Format and DelSP) to\n be used with the Text/Plain media type. In the presence of these\n parameters, trailing whitespace is used to indicate flowed lines and\n a canonical quote indicator is used to indicate quoted lines. This\n results in an encoding which appears as normal Text/Plain in older\n implementations, since it is in fact normal Text/Plain, yet provides\n for superior wrapping/flowing, and quoting.\n\n This document supersedes the one specified in RFC 2646, \"The\n Text/Plain Format Parameter\", and adds the DelSp parameter to\n accommodate languages/coded character sets in which ASCII spaces are\n not used or appear rarely. 3676 crl encryption key signature signatures nested-reference unchanged"},{"id":"IETF RFC 2471","type":"specification","body":"IETF","designation":"RFC 2471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2471.txt","https://www.rfc-editor.org/rfc/rfc2471.pdf"],"folder":"IETF/RFC-2471","files":{"txt":{"path":"standards/IETF/RFC-2471/RFC-2471.txt","sha256":"4b007b72406624172ea474cf6b1ab396ed3aaeca5f2d478858281e334f81a200"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 2471 Nokia\nObsoletes: 1897 R. Fink\nCategory: Experimental LBNL\n J. Postel\n ISI\n December 1998\n\n IPv6 Testing Address Allocation\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document describes an allocation plan for IPv6 addresses to be\n used in testing IPv6 prototype software. These addresses are\n temporary and will be reclaimed in the future. Any IPv6 system using\n these addresses will have to renumber at some time in the future.\n These addresses will not to be routable in the Internet other than\n for IPv6 testing.\n\n The addre","scope_keywords":["2471","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2546","folder":"IETF/RFC-2546","source":"IETF/RFC-2546/RFC-2546.txt","version":null},{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 2928","folder":"IETF/RFC-2928","source":"IETF/RFC-2928/RFC-2928.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null}],"search_text":"IETF RFC 2471 Network Working Group R. Hinden\nRequest for Comments: 2471 Nokia\nObsoletes: 1897 R. Fink\nCategory: Experimental LBNL\n J. Postel\n ISI\n December 1998\n\n IPv6 Testing Address Allocation\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1.0 Introduction\n\n This document describes an allocation plan for IPv6 addresses to be\n used in testing IPv6 prototype software. These addresses are\n temporary and will be reclaimed in the future. Any IPv6 system using\n these addresses will have to renumber at some time in the future.\n These addresses will not to be routable in the Internet other than\n for IPv6 testing.\n\n The addre 2471 authentication key nested-reference unchanged"},{"id":"IETF RFC 3701","type":"specification","body":"IETF","designation":"RFC 3701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3701.txt","https://www.rfc-editor.org/rfc/rfc3701.pdf"],"folder":"IETF/RFC-3701","files":{"txt":{"path":"standards/IETF/RFC-3701/RFC-3701.txt","sha256":"0d77ec21f06c4074ce0613256d773372a102e2c06f0b6a008fe309b8e3d47462"}},"tags":["nested-reference","unchanged"],"summary":"The 6bone was established in 1996 by the IETF as an IPv6 Testbed\n network to enable various IPv6 testing as well as to assist in the\n transitioning of IPv6 into the Internet. It operates under the IPv6\n address allocation 3FFE::/16 from RFC 2471. As IPv6 is beginning its\n production deployment it is appropriate to plan for the phaseout of\n the 6bone. This document establishes a plan for a multi-year\n phaseout of the 6bone and its address allocation on the assumption\n that the IETF is the appropriate place to determine this.\n\n This document obsoletes RFC 2471, \"IPv6 Testing Address Allocation\",\n December, 1998. RFC 2471 will become historic.\n\n1. Introduction\n\n The 6bone IPv6 Testbed network was established in March 1996,\n becoming operational during the summer of 1996 using an IPv6 testing\n address allocation of 5F00::/8 [TEST-OLD] that used the original (and\n now obsolete) provider based","scope_keywords":["3701","holder","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null}],"search_text":"IETF RFC 3701 The 6bone was established in 1996 by the IETF as an IPv6 Testbed\n network to enable various IPv6 testing as well as to assist in the\n transitioning of IPv6 into the Internet. It operates under the IPv6\n address allocation 3FFE::/16 from RFC 2471. As IPv6 is beginning its\n production deployment it is appropriate to plan for the phaseout of\n the 6bone. This document establishes a plan for a multi-year\n phaseout of the 6bone and its address allocation on the assumption\n that the IETF is the appropriate place to determine this.\n\n This document obsoletes RFC 2471, \"IPv6 Testing Address Allocation\",\n December, 1998. RFC 2471 will become historic.\n\n1. Introduction\n\n The 6bone IPv6 Testbed network was established in March 1996,\n becoming operational during the summer of 1996 using an IPv6 testing\n address allocation of 5F00::/8 [TEST-OLD] that used the original (and\n now obsolete) provider based 3701 holder key nested-reference unchanged"},{"id":"IETF RFC 5156","type":"specification","body":"IETF","designation":"RFC 5156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5156.txt","https://www.rfc-editor.org/rfc/rfc5156.pdf"],"folder":"IETF/RFC-5156","files":{"txt":{"path":"standards/IETF/RFC-5156/RFC-5156.txt","sha256":"ad609be74680f8b9102376bf8a62e8b4fc2e89e9f75b7223b3e64f22a8b46aac"}},"tags":["nested-reference","unchanged"],"summary":"This document is a compilation of special IPv6 addresses defined in\n other RFCs. It can be used as a checklist of invalid routing\n prefixes for developing filtering policies for routes and IP packets.\n It does not discuss addresses that are assigned to operators and\n users through the Regional Internet Registries.","scope_keywords":["5156","hash","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null}],"search_text":"IETF RFC 5156 This document is a compilation of special IPv6 addresses defined in\n other RFCs. It can be used as a checklist of invalid routing\n prefixes for developing filtering policies for routes and IP packets.\n It does not discuss addresses that are assigned to operators and\n users through the Regional Internet Registries. 5156 hash policies subject nested-reference unchanged"},{"id":"IETF RFC 2956","type":"specification","body":"IETF","designation":"RFC 2956","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2956.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2956.txt","https://www.rfc-editor.org/rfc/rfc2956.pdf"],"folder":"IETF/RFC-2956","files":{"txt":{"path":"standards/IETF/RFC-2956/RFC-2956.txt","sha256":"a66535ec349efd967fb10aca73362b1379ca7f1081825196724eb0d13d7928b3"}},"tags":["nested-reference","unchanged"],"summary":"This document is an overview of a workshop held by the Internet\n Architecture Board (IAB) on the Internet Network Layer architecture\n hosted by SURFnet in Utrecht, the Netherlands on 7-9 July 1999. The\n goal of the workshop was to understand the state of the network layer\n and its impact on continued growth and usage of the Internet.\n Different technical scenarios for the (foreseeable) future and the\n impact of external influences were studied. This report lists the\n conclusions and recommendations to the Internet Engineering Task\n Force (IETF) community.","scope_keywords":["2956","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null}],"search_text":"IETF RFC 2956 This document is an overview of a workshop held by the Internet\n Architecture Board (IAB) on the Internet Network Layer architecture\n hosted by SURFnet in Utrecht, the Netherlands on 7-9 July 1999. The\n goal of the workshop was to understand the state of the network layer\n and its impact on continued growth and usage of the Internet.\n Different technical scenarios for the (foreseeable) future and the\n impact of external influences were studied. This report lists the\n conclusions and recommendations to the Internet Engineering Task\n Force (IETF) community. 2956 identification nested-reference unchanged"},{"id":"IETF RFC 2123","type":"specification","body":"IETF","designation":"RFC 2123","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2123.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2123.txt","https://www.rfc-editor.org/rfc/rfc2123.pdf"],"folder":"IETF/RFC-2123","files":{"txt":{"path":"standards/IETF/RFC-2123/RFC-2123.txt","sha256":"a45e003ebd96dc3953133e4468b67455a223dba07cd62266f027fccb4ea92cd7"}},"tags":["nested-reference","unchanged"],"summary":"This memo records experiences in implementing and using the Traffic\n Flow Measurement Architecture and Meter MIB. It discusses the\n implementation of NeTraMet (a traffic meter) and NeMaC (a combined\n manager and meter reader), considers the writing of meter rule sets\n and gives some guidance on setting up a traffic flow measurement\n system using NeTraMet.","scope_keywords":["2123","attribute","attributes","hash","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null}],"search_text":"IETF RFC 2123 This memo records experiences in implementing and using the Traffic\n Flow Measurement Architecture and Meter MIB. It discusses the\n implementation of NeTraMet (a traffic meter) and NeMaC (a combined\n manager and meter reader), considers the writing of meter rule sets\n and gives some guidance on setting up a traffic flow measurement\n system using NeTraMet. 2123 attribute attributes hash management nested-reference unchanged"},{"id":"IETF RFC 2265","type":"specification","body":"IETF","designation":"RFC 2265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2265.txt","https://www.rfc-editor.org/rfc/rfc2265.pdf"],"folder":"IETF/RFC-2265","files":{"txt":{"path":"standards/IETF/RFC-2265/RFC-2265.txt","sha256":"387959a8c804b63f7fd08aef09cf5086404efbe0d9d6e4bc77432728c6287c6f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2261]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model.","scope_keywords":["2265","authentication","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2263","folder":"IETF/RFC-2263","source":"IETF/RFC-2263/RFC-2263.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null}],"search_text":"IETF RFC 2265 This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2261]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model. 2265 authentication key management policies policy nested-reference unchanged"},{"id":"IETF RFC 2275","type":"specification","body":"IETF","designation":"RFC 2275","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2275.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2275.txt","https://www.rfc-editor.org/rfc/rfc2275.pdf"],"folder":"IETF/RFC-2275","files":{"txt":{"path":"standards/IETF/RFC-2275/RFC-2275.txt","sha256":"d4d9869f754848836dc2d1ed14ba023bc751363ff428e554537a3c906a1ec3b2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2271]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model.","scope_keywords":["2275","authentication","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2273","folder":"IETF/RFC-2273","source":"IETF/RFC-2273/RFC-2273.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2454","folder":"IETF/RFC-2454","source":"IETF/RFC-2454/RFC-2454.txt","version":null},{"body":"IETF","designation":"RFC 2494","folder":"IETF/RFC-2494","source":"IETF/RFC-2494/RFC-2494.txt","version":null},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 2513","folder":"IETF/RFC-2513","source":"IETF/RFC-2513/RFC-2513.txt","version":null},{"body":"IETF","designation":"RFC 2515","folder":"IETF/RFC-2515","source":"IETF/RFC-2515/RFC-2515.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null}],"search_text":"IETF RFC 2275 This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2271]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model. 2275 authentication key management policies policy nested-reference unchanged"},{"id":"IETF RFC 2452","type":"specification","body":"IETF","designation":"RFC 2452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2452.txt","https://www.rfc-editor.org/rfc/rfc2452.pdf"],"folder":"IETF/RFC-2452","files":{"txt":{"path":"standards/IETF/RFC-2452/RFC-2452.txt","sha256":"4901aa22bf191cc88579d6425f3105c19cf1283c55baf37b6f32ef2b043fd869"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Daniele\nRequest for Comments: 2452 Compaq Computer Corporation\nCategory: Standards Track December 1998\n\n IP Version 6 Management Information Base\n for the Transmission Control Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document is one in the series of documents that define various\n MIB objects for IPv6. Specifically, this document is the MIB module\n which defines managed objects for implementations of the Transmission\n Control Protocol (TCP)","scope_keywords":["2452","authentication","authorization","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2452 Network Working Group M. Daniele\nRequest for Comments: 2452 Compaq Computer Corporation\nCategory: Standards Track December 1998\n\n IP Version 6 Management Information Base\n for the Transmission Control Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document is one in the series of documents that define various\n MIB objects for IPv6. Specifically, this document is the MIB module\n which defines managed objects for implementations of the Transmission\n Control Protocol (TCP) 2452 authentication authorization management policies policy nested-reference unchanged"},{"id":"IETF RFC 2454","type":"specification","body":"IETF","designation":"RFC 2454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2454.txt","https://www.rfc-editor.org/rfc/rfc2454.pdf"],"folder":"IETF/RFC-2454","files":{"txt":{"path":"standards/IETF/RFC-2454/RFC-2454.txt","sha256":"61f6fd006ef5d58dfbd002efaf3661029f3cf3362441518e1ef691879055772c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Daniele\nRequest for Comments: 2454 Compaq Computer Corporation\nCategory: Standards Track December 1998\n\n IP Version 6 Management Information Base\n for the User Datagram Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document is one in the series of documents that define various\n MIB objects for IPv6. Specifically, this document is the MIB module\n which defines managed objects for implementations of the User\n Datagram Protocol (UDP) over IP Versi","scope_keywords":["2454","authentication","authorization","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null}],"search_text":"IETF RFC 2454 Network Working Group M. Daniele\nRequest for Comments: 2454 Compaq Computer Corporation\nCategory: Standards Track December 1998\n\n IP Version 6 Management Information Base\n for the User Datagram Protocol\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This document is one in the series of documents that define various\n MIB objects for IPv6. Specifically, this document is the MIB module\n which defines managed objects for implementations of the User\n Datagram Protocol (UDP) over IP Versi 2454 authentication authorization management policies policy nested-reference unchanged"},{"id":"IETF RFC 2493","type":"specification","body":"IETF","designation":"RFC 2493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2493.txt","https://www.rfc-editor.org/rfc/rfc2493.pdf"],"folder":"IETF/RFC-2493","files":{"txt":{"path":"standards/IETF/RFC-2493/RFC-2493.txt","sha256":"25778d1d66bd22ee1b1bcd99cc711e30c1842464b365ef7186b199dacdf4bf27"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Tesink, Editor\nRequest for Comments: 2493 Bellcore\nCategory: Standards Track January 1999\n\n Textual Conventions for MIB Modules Using Performance History\n Based on 15 Minute Intervals\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a set of Textual Conventions for MIB modules\n which make use of performance history data based on 15 minute\n intervals.\n\n1. Table of Contents\n\n 1 Table of Contents ..................................... 1\n 2 Int","scope_keywords":["2493","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2496","folder":"IETF/RFC-2496","source":"IETF/RFC-2496/RFC-2496.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3593","folder":"IETF/RFC-3593","source":"IETF/RFC-3593/RFC-3593.txt","version":null}],"search_text":"IETF RFC 2493 Network Working Group K. Tesink, Editor\nRequest for Comments: 2493 Bellcore\nCategory: Standards Track January 1999\n\n Textual Conventions for MIB Modules Using Performance History\n Based on 15 Minute Intervals\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a set of Textual Conventions for MIB modules\n which make use of performance history data based on 15 minute\n intervals.\n\n1. Table of Contents\n\n 1 Table of Contents ..................................... 1\n 2 Int 2493 management policy nested-reference unchanged"},{"id":"IETF RFC 2575","type":"specification","body":"IETF","designation":"RFC 2575","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2575.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2575.txt","https://www.rfc-editor.org/rfc/rfc2575.pdf"],"folder":"IETF/RFC-2575","files":{"txt":{"path":"standards/IETF/RFC-2575/RFC-2575.txt","sha256":"76b0d4be9d298ccbac8152735782457b1f8bc07eaab727ea3524a0c9857bff1e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2571]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model.","scope_keywords":["2575","authentication","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2570","folder":"IETF/RFC-2570","source":"IETF/RFC-2570/RFC-2570.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2618","folder":"IETF/RFC-2618","source":"IETF/RFC-2618/RFC-2618.txt","version":null},{"body":"IETF","designation":"RFC 2619","folder":"IETF/RFC-2619","source":"IETF/RFC-2619/RFC-2619.txt","version":null},{"body":"IETF","designation":"RFC 2620","folder":"IETF/RFC-2620","source":"IETF/RFC-2620/RFC-2620.txt","version":null},{"body":"IETF","designation":"RFC 2621","folder":"IETF/RFC-2621","source":"IETF/RFC-2621/RFC-2621.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2666","folder":"IETF/RFC-2666","source":"IETF/RFC-2666/RFC-2666.txt","version":null},{"body":"IETF","designation":"RFC 2667","folder":"IETF/RFC-2667","source":"IETF/RFC-2667/RFC-2667.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2737","folder":"IETF/RFC-2737","source":"IETF/RFC-2737/RFC-2737.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2819","folder":"IETF/RFC-2819","source":"IETF/RFC-2819/RFC-2819.txt","version":null},{"body":"IETF","designation":"RFC 2837","folder":"IETF/RFC-2837","source":"IETF/RFC-2837/RFC-2837.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2856","folder":"IETF/RFC-2856","source":"IETF/RFC-2856/RFC-2856.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2864","folder":"IETF/RFC-2864","source":"IETF/RFC-2864/RFC-2864.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2932","folder":"IETF/RFC-2932","source":"IETF/RFC-2932/RFC-2932.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3020","folder":"IETF/RFC-3020","source":"IETF/RFC-3020/RFC-3020.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null}],"search_text":"IETF RFC 2575 This document describes the View-based Access Control Model for use\n in the SNMP architecture [RFC2571]. It defines the Elements of\n Procedure for controlling access to management information. This\n document also includes a MIB for remotely managing the configuration\n parameters for the View-based Access Control Model. 2575 authentication key management policies policy nested-reference unchanged"},{"id":"IETF RFC 3415","type":"specification","body":"IETF","designation":"RFC 3415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3415.txt","https://www.rfc-editor.org/rfc/rfc3415.pdf"],"folder":"IETF/RFC-3415","files":{"txt":{"path":"standards/IETF/RFC-3415/RFC-3415.txt","sha256":"b1f997fd36eb82c49bcc9a3b6faf64f040272401853d3d1ea8fd5e3cce579da9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the View-based Access Control Model (VACM)\n for use in the Simple Network Management Protocol (SNMP)\n architecture. It defines the Elements of Procedure for controlling\n access to management information. This document also includes a\n Management Information Base (MIB) for remotely managing the\n configuration parameters for the View-based Access Control Model.\n This document obsoletes RFC 2575.\n\nWijnen, et al. Standards Track [Page 1]\n\f\nRFC 3415 VACM for the SNMP December 2002","scope_keywords":["3415","authentication","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3512","folder":"IETF/RFC-3512","source":"IETF/RFC-3512/RFC-3512.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4502","folder":"IETF/RFC-4502","source":"IETF/RFC-4502/RFC-4502.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null}],"search_text":"IETF RFC 3415 This document describes the View-based Access Control Model (VACM)\n for use in the Simple Network Management Protocol (SNMP)\n architecture. It defines the Elements of Procedure for controlling\n access to management information. This document also includes a\n Management Information Base (MIB) for remotely managing the\n configuration parameters for the View-based Access Control Model.\n This document obsoletes RFC 2575.\n\nWijnen, et al. Standards Track [Page 1]\n\f\nRFC 3415 VACM for the SNMP December 2002 3415 authentication key management policies policy nested-reference unchanged"},{"id":"IETF RFC 2422","type":"specification","body":"IETF","designation":"RFC 2422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2422.txt","https://www.rfc-editor.org/rfc/rfc2422.pdf"],"folder":"IETF/RFC-2422","files":{"txt":{"path":"standards/IETF/RFC-2422/RFC-2422.txt","sha256":"0b49248012dd41dd9265696c3f22643b52763c66834b3977c83dac023bb56a82"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n audio/32KADPCM for toll quality audio. This audio encoding is\n defined by the ITU-T in Recommendation G.726. This document refines\n an earlier sub-type registration in RFC 1911.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [REQ].\n\n2. ITU-T Definition\n\n Recommendation G.726 [G726] defines the characteristics that are\n recommended for the conversion of a 64 kbit/s A-law or m-law pulse\n code modulation (PCM) channel at 8000 samples/second to and from a\n 40, 32, 24 or 16 kbit/s channel. The conversion is applied to the PCM\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2422 32 kbit/s ADPCM September 1998\n\n bit stream using an adaptive differential pulse code modulation\n (ADPCM) transc","scope_keywords":["2422","algorithm","key","profile","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null}],"search_text":"IETF RFC 2422 This document describes the registration of the MIME sub-type\n audio/32KADPCM for toll quality audio. This audio encoding is\n defined by the ITU-T in Recommendation G.726. This document refines\n an earlier sub-type registration in RFC 1911.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [REQ].\n\n2. ITU-T Definition\n\n Recommendation G.726 [G726] defines the characteristics that are\n recommended for the conversion of a 64 kbit/s A-law or m-law pulse\n code modulation (PCM) channel at 8000 samples/second to and from a\n 40, 32, 24 or 16 kbit/s channel. The conversion is applied to the PCM\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2422 32 kbit/s ADPCM September 1998\n\n bit stream using an adaptive differential pulse code modulation\n (ADPCM) transc 2422 algorithm key profile risk subject nested-reference unchanged"},{"id":"IETF RFC 2423","type":"specification","body":"IETF","designation":"RFC 2423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2423.txt","https://www.rfc-editor.org/rfc/rfc2423.pdf"],"folder":"IETF/RFC-2423","files":{"txt":{"path":"standards/IETF/RFC-2423/RFC-2423.txt","sha256":"b577d2c96d35f67e3adfd87013d18a471076bd30d765b57ad472becfba8ceae9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n multipart/voice-message for use with the Voice Profile for Internet\n Mail (VPIM). A full description of usage can be found in the VPIM v2\n specification [VPIM2]. This document revises an earlier sub-type\n registration in RFC 1911 [VPIM1].\n\n2. VPIM Scope\n\n The VPIM specification defines a restricted profile of the Internet\n multimedia messaging protocols for use between voice processing\n platforms. These platforms have historically been special-purpose\n computers and often do not have the same facilities normally\n associated with a traditional Internet Email-capable computer. As a\n result, VPIM also specifies additional functionality as it is needed.\n The profile is intended to specify the minimum common set of features\n to allow interworking between compliant systems.\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2423 m","scope_keywords":["2423","identification","key","profile","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null}],"search_text":"IETF RFC 2423 This document describes the registration of the MIME sub-type\n multipart/voice-message for use with the Voice Profile for Internet\n Mail (VPIM). A full description of usage can be found in the VPIM v2\n specification [VPIM2]. This document revises an earlier sub-type\n registration in RFC 1911 [VPIM1].\n\n2. VPIM Scope\n\n The VPIM specification defines a restricted profile of the Internet\n multimedia messaging protocols for use between voice processing\n platforms. These platforms have historically been special-purpose\n computers and often do not have the same facilities normally\n associated with a traditional Internet Email-capable computer. As a\n result, VPIM also specifies additional functionality as it is needed.\n The profile is intended to specify the minimum common set of features\n to allow interworking between compliant systems.\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2423 m 2423 identification key profile subject nested-reference unchanged"},{"id":"IETF RFC 3802","type":"specification","body":"IETF","designation":"RFC 3802","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3802.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3802.txt","https://www.rfc-editor.org/rfc/rfc3802.pdf"],"folder":"IETF/RFC-3802","files":{"txt":{"path":"standards/IETF/RFC-3802/RFC-3802.txt","sha256":"19c0bf46885fa03136a1343ba74b2a52a36c3228b77b346bda707697c6a91b08"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n audio/32KADPCM Adaptive Differential Pulse Code Modulation for toll\n quality audio. This audio encoding is defined by the ITU-T in\n Recommendation G.726.\n\n1. Introduction\n\n This document describes the registration of the MIME sub-type\n audio/32KADPCM for toll quality audio. This audio encoding is\n defined by the ITU-T in Recommendation G.726. This document\n obsoletes an earlier sub-type registration contained in RFC 1911.\n This document also obsoletes RFC 2422.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [REQ].\n\nVaudreuil, et al. Standards Track [Page 1]\n\f\nRFC 3802 32 kbit/s ADPCM June 2004\n\n2. ITU-T Definition\n\n Recommendation G.726 [G726] defines the characteristics that are\n recomm","scope_keywords":["3802","algorithm","key","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null}],"search_text":"IETF RFC 3802 This document describes the registration of the MIME sub-type\n audio/32KADPCM Adaptive Differential Pulse Code Modulation for toll\n quality audio. This audio encoding is defined by the ITU-T in\n Recommendation G.726.\n\n1. Introduction\n\n This document describes the registration of the MIME sub-type\n audio/32KADPCM for toll quality audio. This audio encoding is\n defined by the ITU-T in Recommendation G.726. This document\n obsoletes an earlier sub-type registration contained in RFC 1911.\n This document also obsoletes RFC 2422.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [REQ].\n\nVaudreuil, et al. Standards Track [Page 1]\n\f\nRFC 3802 32 kbit/s ADPCM June 2004\n\n2. ITU-T Definition\n\n Recommendation G.726 [G726] defines the characteristics that are\n recomm 3802 algorithm key risk subject nested-reference unchanged"},{"id":"IETF RFC 2651","type":"specification","body":"IETF","designation":"RFC 2651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2651.txt","https://www.rfc-editor.org/rfc/rfc2651.pdf"],"folder":"IETF/RFC-2651","files":{"txt":{"path":"standards/IETF/RFC-2651/RFC-2651.txt","sha256":"631b4f2ad9772fba0d4fb3a81086cd087f109be1f821a9b25ee8fbe015aab3d8"}},"tags":["nested-reference","unchanged"],"summary":"The Common Indexing Protocol (CIP) is used to pass indexing\n information from server to server in order to facilitate query\n routing. Query routing is the process of redirecting and replicating\n queries through a distributed database system towards servers holding\n the desired results. This document describes the CIP framework,\n including its architecture and the protocol specifics of exchanging\n indices.\n\n1. Introduction","scope_keywords":["2651","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2655","folder":"IETF/RFC-2655","source":"IETF/RFC-2655/RFC-2655.txt","version":null},{"body":"IETF","designation":"RFC 2657","folder":"IETF/RFC-2657","source":"IETF/RFC-2657/RFC-2657.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2651 The Common Indexing Protocol (CIP) is used to pass indexing\n information from server to server in order to facilitate query\n routing. Query routing is the process of redirecting and replicating\n queries through a distributed database system towards servers holding\n the desired results. This document describes the CIP framework,\n including its architecture and the protocol specifics of exchanging\n indices.\n\n1. Introduction 2651 http presentation nested-reference unchanged"},{"id":"IETF RFC 2654","type":"specification","body":"IETF","designation":"RFC 2654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2654.txt","https://www.rfc-editor.org/rfc/rfc2654.pdf"],"folder":"IETF/RFC-2654","files":{"txt":{"path":"standards/IETF/RFC-2654/RFC-2654.txt","sha256":"907289a3165c77e61cc6fd613b43b88950d586e183ade13aeca28f6809052740"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism by which information servers can\n exchange indices of information from their databases by making use of\n the Common Indexing Protocol (CIP). This document defines the\n structure of the index information being exchanged, as well as the\n appropriate meanings for the headers that are defined in the Common\n Indexing Protocol. It is assumed that the structures defined here\n can be used by X.500 DSAs, LDAP servers, Whois++ servers, CSO Ph\n servers and many others.","scope_keywords":["2654","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2657","folder":"IETF/RFC-2657","source":"IETF/RFC-2657/RFC-2657.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2654 This document defines a mechanism by which information servers can\n exchange indices of information from their databases by making use of\n the Common Indexing Protocol (CIP). This document defines the\n structure of the index information being exchanged, as well as the\n appropriate meanings for the headers that are defined in the Common\n Indexing Protocol. It is assumed that the structures defined here\n can be used by X.500 DSAs, LDAP servers, Whois++ servers, CSO Ph\n servers and many others. 2654 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 1915","type":"specification","body":"IETF","designation":"RFC 1915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1915.txt","https://www.rfc-editor.org/rfc/rfc1915.pdf"],"folder":"IETF/RFC-1915","files":{"txt":{"path":"standards/IETF/RFC-1915/RFC-1915.txt","sha256":"0b4e58f64534f11b28a5126a9eca2b5c64d9141b260d29fc90fe3ebc576be646"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Kastenholz\nRequest for Comments: 1915 FTP Software, Inc.\nBCP: 3 February 1996\nCategory: Best Current Practice\n\n Variance for\n The PPP Connection Control Protocol\n and\n The PPP Encryption Control Protocol\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Variance ............................................. 1\n 1.1 The Problem ......................................... 1\n 1.1.1 History ........................................... 1\n 1.1.2 Other Attempted Solutions ......................... 2\n 1.2 Variance to Procedures in RFC 1602 .................. 2\n 1.3 The Solution ........................................ 3\n 1.4 Perceived Benefits .................................. 3\n 1.5 Perceived","scope_keywords":["1915","encryption","holder","license","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null}],"search_text":"IETF RFC 1915 Network Working Group F. Kastenholz\nRequest for Comments: 1915 FTP Software, Inc.\nBCP: 3 February 1996\nCategory: Best Current Practice\n\n Variance for\n The PPP Connection Control Protocol\n and\n The PPP Encryption Control Protocol\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Variance ............................................. 1\n 1.1 The Problem ......................................... 1\n 1.1.1 History ........................................... 1\n 1.1.2 Other Attempted Solutions ......................... 2\n 1.2 Variance to Procedures in RFC 1602 .................. 2\n 1.3 The Solution ........................................ 3\n 1.4 Perceived Benefits .................................. 3\n 1.5 Perceived 1915 encryption holder license risk subject nested-reference unchanged"},{"id":"IETF RFC 2529","type":"specification","body":"IETF","designation":"RFC 2529","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2529.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2529.txt","https://www.rfc-editor.org/rfc/rfc2529.pdf"],"folder":"IETF/RFC-2529","files":{"txt":{"path":"standards/IETF/RFC-2529/RFC-2529.txt","sha256":"009ac1313fe0f94490f61a23f46f0a4c331bddc76f0f4e252ead45cd920cc657"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies the frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local addresses over IPv4\n domains. It also specifies the content of the Source/Target Link-\n layer Address option used in the Router Solicitation, Router\n Advertisement, Neighbor Solicitation, and Neighbor Advertisement and\n Redirect messages, when those messages are transmitted on an IPv4\n multicast network.\n\n The motivation for this method is to allow isolated IPv6 hosts,\n located on a physical link which has no directly connected IPv6\n router, to become fully functional IPv6 hosts by using an IPv4 domain\n that supports IPv4 multicast as their virtual local link. It uses\n IPv4 multicast as a \"virtual Ethernet\".","scope_keywords":["2529","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 2529 This memo specifies the frame format for transmission of IPv6 [IPV6]\n packets and the method of forming IPv6 link-local addresses over IPv4\n domains. It also specifies the content of the Source/Target Link-\n layer Address option used in the Router Solicitation, Router\n Advertisement, Neighbor Solicitation, and Neighbor Advertisement and\n Redirect messages, when those messages are transmitted on an IPv4\n multicast network.\n\n The motivation for this method is to allow isolated IPv6 hosts,\n located on a physical link which has no directly connected IPv6\n router, to become fully functional IPv6 hosts by using an IPv4 domain\n that supports IPv4 multicast as their virtual local link. It uses\n IPv4 multicast as a \"virtual Ethernet\". 2529 identification key nested-reference unchanged"},{"id":"IETF RFC 2709","type":"specification","body":"IETF","designation":"RFC 2709","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2709.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2709.txt","https://www.rfc-editor.org/rfc/rfc2709.pdf"],"folder":"IETF/RFC-2709","files":{"txt":{"path":"standards/IETF/RFC-2709/RFC-2709.txt","sha256":"ba7026aa7dcadfc6b3f1a3659ef144059f384baa43cf80f8e95eff0403f80eab"}},"tags":["nested-reference","unchanged"],"summary":"There are a variety of NAT flavors, as described in [Ref 1]. Of the\n domains supported by NATs, only Realm-Specific IP clients are able to\n pursue end-to-end IPsec secure sessions. However, all flavors of NAT\n are capable of offering tunnel-mode IPsec security to private domain\n hosts peering with nodes in external realm. This document describes a\n security model by which tunnel-mode IPsec security can be architected\n on NAT devices. A section is devoted to describing how security\n policies may be transparently communicated to IKE (for automated KEY\n exchange) during Quick Mode. Also outlined are applications that can\n benefit from the Security Model described.\n\n1. Introduction and Overview\n\n NAT devices provide transparent routing to end hosts trying to\n communicate from disparate address realms, by modifying IP and\n transport headers en-route. This solution works best when the end\n use","scope_keywords":["2709","algorithm","algorithms","attribute","attributes","key","keys","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 2709 There are a variety of NAT flavors, as described in [Ref 1]. Of the\n domains supported by NATs, only Realm-Specific IP clients are able to\n pursue end-to-end IPsec secure sessions. However, all flavors of NAT\n are capable of offering tunnel-mode IPsec security to private domain\n hosts peering with nodes in external realm. This document describes a\n security model by which tunnel-mode IPsec security can be architected\n on NAT devices. A section is devoted to describing how security\n policies may be transparently communicated to IKE (for automated KEY\n exchange) during Quick Mode. Also outlined are applications that can\n benefit from the Security Model described.\n\n1. Introduction and Overview\n\n NAT devices provide transparent routing to end hosts trying to\n communicate from disparate address realms, by modifying IP and\n transport headers en-route. This solution works best when the end\n use 2709 algorithm algorithms attribute attributes key keys policies policy subject nested-reference unchanged"},{"id":"IETF RFC 3024","type":"specification","body":"IETF","designation":"RFC 3024","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3024.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3024.txt","https://www.rfc-editor.org/rfc/rfc3024.pdf"],"folder":"IETF/RFC-3024","files":{"txt":{"path":"standards/IETF/RFC-3024/RFC-3024.txt","sha256":"2d171d35823aaa35a89c9f9dfb50393532ce75a3caa8551c1d83664ec5bcba51"}},"tags":["nested-reference","unchanged"],"summary":"Mobile Internet Protocol (IP) uses tunneling from the home agent to\n the mobile node's care-of address, but rarely in the reverse\n direction. Usually, a mobile node sends its packets through a router\n on the foreign network, and assumes that routing is independent of\n source address. When this assumption is not true, it is convenient\n to establish a topologically correct reverse tunnel from the care-of\n address to the home agent.\n\n This document proposes backwards-compatible extensions to Mobile IP\n to support topologically correct reverse tunnels. This document does\n not attempt to solve the problems posed by firewalls located between\n the home agent and the mobile node's care-of address.\n\n This document obsoletes RFC 2344.\n\nMontenegro Standards Track [Page 1]\n\f\nRFC 3024 Reverse Tunneling for Mobile IP, revised January 2001","scope_keywords":["3024","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null}],"search_text":"IETF RFC 3024 Mobile Internet Protocol (IP) uses tunneling from the home agent to\n the mobile node's care-of address, but rarely in the reverse\n direction. Usually, a mobile node sends its packets through a router\n on the foreign network, and assumes that routing is independent of\n source address. When this assumption is not true, it is convenient\n to establish a topologically correct reverse tunnel from the care-of\n address to the home agent.\n\n This document proposes backwards-compatible extensions to Mobile IP\n to support topologically correct reverse tunnels. This document does\n not attempt to solve the problems posed by firewalls located between\n the home agent and the mobile node's care-of address.\n\n This document obsoletes RFC 2344.\n\nMontenegro Standards Track [Page 1]\n\f\nRFC 3024 Reverse Tunneling for Mobile IP, revised January 2001 3024 delivery key nested-reference unchanged"},{"id":"IETF RFC 3056","type":"specification","body":"IETF","designation":"RFC 3056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3056.txt","https://www.rfc-editor.org/rfc/rfc3056.pdf"],"folder":"IETF/RFC-3056","files":{"txt":{"path":"standards/IETF/RFC-3056/RFC-3056.txt","sha256":"c672c612de45943f713d87565c18296f16e78214476deaba09fc56a37ed0e6d5"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies an optional interim mechanism for IPv6 sites to\n communicate with each other over the IPv4 network without explicit\n tunnel setup, and for them to communicate with native IPv6 domains\n via relay routers. Effectively it treats the wide area IPv4 network\n as a unicast point-to-point link layer. The mechanism is intended as\n a start-up transition tool used during the period of co-existence of\n IPv4 and IPv6. It is not intended as a permanent solution.\n\n The document defines a method for assigning an interim unique IPv6\n address prefix to any site that currently has at least one globally\n unique IPv4 address, and specifies an encapsulation mechanism for\n transmitting IPv6 packets using such a prefix over the global IPv4\n network.\n\n The motivation for this method is to allow isolated IPv6 domains or\n hosts, attached to an IPv4 network which has no native IPv6 support,\n to ","scope_keywords":["3056","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3068","folder":"IETF/RFC-3068","source":"IETF/RFC-3068/RFC-3068.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5158","folder":"IETF/RFC-5158","source":"IETF/RFC-5158/RFC-5158.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6177","folder":"IETF/RFC-6177","source":"IETF/RFC-6177/RFC-6177.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 3056 This memo specifies an optional interim mechanism for IPv6 sites to\n communicate with each other over the IPv4 network without explicit\n tunnel setup, and for them to communicate with native IPv6 domains\n via relay routers. Effectively it treats the wide area IPv4 network\n as a unicast point-to-point link layer. The mechanism is intended as\n a start-up transition tool used during the period of co-existence of\n IPv4 and IPv6. It is not intended as a permanent solution.\n\n The document defines a method for assigning an interim unique IPv6\n address prefix to any site that currently has at least one globally\n unique IPv4 address, and specifies an encapsulation mechanism for\n transmitting IPv6 packets using such a prefix over the global IPv4\n network.\n\n The motivation for this method is to allow isolated IPv6 domains or\n hosts, attached to an IPv4 network which has no native IPv6 support,\n to  3056 key subject nested-reference unchanged"},{"id":"IETF RFC 3102","type":"specification","body":"IETF","designation":"RFC 3102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3102.txt","https://www.rfc-editor.org/rfc/rfc3102.pdf"],"folder":"IETF/RFC-3102","files":{"txt":{"path":"standards/IETF/RFC-3102/RFC-3102.txt","sha256":"c75a22c81af706b28ae5b16e5bf8f4308e8b3551981c89b4c5ef7908bbb9f180"}},"tags":["nested-reference","unchanged"],"summary":"This document examines the general framework of Realm Specific IP\n (RSIP). RSIP is intended as a alternative to NAT in which the end-\n to-end integrity of packets is maintained. We focus on\n implementation issues, deployment scenarios, and interaction with\n other layer-three protocols.\n\nBorella, et al. Experimental [Page 1]\n\f\nRFC 3102 RSIP: Framework October 2001","scope_keywords":["3102","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3235","folder":"IETF/RFC-3235","source":"IETF/RFC-3235/RFC-3235.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 3102 This document examines the general framework of Realm Specific IP\n (RSIP). RSIP is intended as a alternative to NAT in which the end-\n to-end integrity of packets is maintained. We focus on\n implementation issues, deployment scenarios, and interaction with\n other layer-three protocols.\n\nBorella, et al. Experimental [Page 1]\n\f\nRFC 3102 RSIP: Framework October 2001 3102 identification nested-reference unchanged"},{"id":"IETF RFC 3103","type":"specification","body":"IETF","designation":"RFC 3103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3103.txt","https://www.rfc-editor.org/rfc/rfc3103.pdf"],"folder":"IETF/RFC-3103","files":{"txt":{"path":"standards/IETF/RFC-3103/RFC-3103.txt","sha256":"2e4b11b7c81149572fa30499db9740a7999f93001b3a6be47de8bba886e4b2f6"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a protocol with which to implement Realm\n Specific IP (RSIP). The protocol defined herein allows negotiation\n of resources between an RSIP host and gateway, so that the host can\n lease some of the gateway's addressing parameters in order to\n establish a global network presence. This protocol is designed to\n operate on the application layer and to use its own TCP or UDP port.\n In particular, the protocol allows a gateway to allocate addressing\n and control parameters to a host such that a flow policy can be\n enforced at the gateway.\n\nBorella, et al. Experimental [Page 1]\n\f\nRFC 3103 RSIP Protocol Specification October 2001","scope_keywords":["3103","encryption","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 3103 This document presents a protocol with which to implement Realm\n Specific IP (RSIP). The protocol defined herein allows negotiation\n of resources between an RSIP host and gateway, so that the host can\n lease some of the gateway's addressing parameters in order to\n establish a global network presence. This protocol is designed to\n operate on the application layer and to use its own TCP or UDP port.\n In particular, the protocol allows a gateway to allocate addressing\n and control parameters to a host such that a flow policy can be\n enforced at the gateway.\n\nBorella, et al. Experimental [Page 1]\n\f\nRFC 3103 RSIP Protocol Specification October 2001 3103 encryption policy nested-reference unchanged"},{"id":"IETF RFC 3750","type":"specification","body":"IETF","designation":"RFC 3750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3750.txt","https://www.rfc-editor.org/rfc/rfc3750.pdf"],"folder":"IETF/RFC-3750","files":{"txt":{"path":"standards/IETF/RFC-3750/RFC-3750.txt","sha256":"f2e218878c44a4a7cb126a88a4250bb098f52824ed00b5fd831b4fbacf34ebdf"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the scenarios in which IPv6 transition\n mechanisms are to be used in unmanaged networks. In order to\n evaluate the suitability of these mechanisms, we need to define the\n scenarios in which these mechanisms have to be used. One specific\n scope is the \"unmanaged network\", which typically corresponds to a\n home or small office network. The scenarios are specific to a single\n subnet, and are defined in terms of IP connectivity supported by the\n gateway and the Internet Service Provider (ISP). We first examine\n the generic requirements of four classes of applications: local,\n client, peer to peer and server. Then, for each scenario, we infer\n transition requirements by analyzing the needs for smooth migration\n of applications from IPv4 to IPv6.\n\nHuitema, et al. Informational [Page 1]\n\f\nRFC 3750 Unmanaged Networks IPv6 Transition Scenarios April 2004","scope_keywords":["3750","key","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null}],"search_text":"IETF RFC 3750 This document defines the scenarios in which IPv6 transition\n mechanisms are to be used in unmanaged networks. In order to\n evaluate the suitability of these mechanisms, we need to define the\n scenarios in which these mechanisms have to be used. One specific\n scope is the \"unmanaged network\", which typically corresponds to a\n home or small office network. The scenarios are specific to a single\n subnet, and are defined in terms of IP connectivity supported by the\n gateway and the Internet Service Provider (ISP). We first examine\n the generic requirements of four classes of applications: local,\n client, peer to peer and server. Then, for each scenario, we infer\n transition requirements by analyzing the needs for smooth migration\n of applications from IPv4 to IPv6.\n\nHuitema, et al. Informational [Page 1]\n\f\nRFC 3750 Unmanaged Networks IPv6 Transition Scenarios April 2004 3750 key management policies nested-reference unchanged"},{"id":"IETF RFC 3809","type":"specification","body":"IETF","designation":"RFC 3809","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3809.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3809.txt","https://www.rfc-editor.org/rfc/rfc3809.pdf"],"folder":"IETF/RFC-3809","files":{"txt":{"path":"standards/IETF/RFC-3809/RFC-3809.txt","sha256":"6bc61ddd98bc6a664999844a4e9422d13dbdc2dfb75a4ffdf9b1d6a711ff5b3d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes generic requirements for Provider Provisioned\n Virtual Private Networks (PPVPN). The requirements are categorized\n into service requirements, provider requirements and engineering\n requirements. These requirements are not specific to any particular\n type of PPVPN technology, but rather apply to all PPVPN technologies.\n All PPVPN technologies are expected to meet the umbrella set of\n requirements described in this document.\n\nNagarajan Informational [Page 1]\n\f\nRFC 3809 PPVPN June 2004","scope_keywords":["3809","authentication","authorization","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4026","folder":"IETF/RFC-4026","source":"IETF/RFC-4026/RFC-4026.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null}],"search_text":"IETF RFC 3809 This document describes generic requirements for Provider Provisioned\n Virtual Private Networks (PPVPN). The requirements are categorized\n into service requirements, provider requirements and engineering\n requirements. These requirements are not specific to any particular\n type of PPVPN technology, but rather apply to all PPVPN technologies.\n All PPVPN technologies are expected to meet the umbrella set of\n requirements described in this document.\n\nNagarajan Informational [Page 1]\n\f\nRFC 3809 PPVPN June 2004 3809 authentication authorization key management nested-reference unchanged"},{"id":"IETF RFC 3879","type":"specification","body":"IETF","designation":"RFC 3879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3879.txt","https://www.rfc-editor.org/rfc/rfc3879.pdf"],"folder":"IETF/RFC-3879","files":{"txt":{"path":"standards/IETF/RFC-3879/RFC-3879.txt","sha256":"ee8dfd618a760cc1619f2bd5dcebd70f8fdeba51e15c7c4601a8c7129f263334"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the issues surrounding the use of IPv6 site-\n local unicast addresses in their original form, and formally\n deprecates them. This deprecation does not prevent their continued\n use until a replacement has been standardized and implemented.\n\n1. Introduction\n\n For some time, the IPv6 working group has been debating a set of\n issues surrounding the use of \"site local\" addresses. In its meeting\n in March 2003, the group reached a measure of agreement that these\n issues were serious enough to warrant a replacement of site local\n addresses in their original form. Although the consensus was far\n from unanimous, the working group confirmed in its meeting in July\n 2003 the need to document these issues and the consequent decision to\n deprecate IPv6 site-local unicast addresses.\n\n Site-local addresses are defined in the IPv6 addressing architecture\n [RFC3513], especially in ","scope_keywords":["3879","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 3879 This document describes the issues surrounding the use of IPv6 site-\n local unicast addresses in their original form, and formally\n deprecates them. This deprecation does not prevent their continued\n use until a replacement has been standardized and implemented.\n\n1. Introduction\n\n For some time, the IPv6 working group has been debating a set of\n issues surrounding the use of \"site local\" addresses. In its meeting\n in March 2003, the group reached a measure of agreement that these\n issues were serious enough to warrant a replacement of site local\n addresses in their original form. Although the consensus was far\n from unanimous, the working group confirmed in its meeting in July\n 2003 the need to document these issues and the consequent decision to\n deprecate IPv6 site-local unicast addresses.\n\n Site-local addresses are defined in the IPv6 addressing architecture\n [RFC3513], especially in  3879 key management nested-reference unchanged"},{"id":"IETF RFC 3882","type":"specification","body":"IETF","designation":"RFC 3882","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3882.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3882.txt","https://www.rfc-editor.org/rfc/rfc3882.pdf"],"folder":"IETF/RFC-3882","files":{"txt":{"path":"standards/IETF/RFC-3882/RFC-3882.txt","sha256":"b0032a7993a5eb98989f3c598b85cec3f4dd0ccc6adc5e99150dcf2fda2ce772"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an operational technique that uses BGP\n communities to remotely trigger black-holing of a particular\n destination network to block denial-of-service attacks. Black-holing\n can be applied on a selection of routers rather than all BGP-speaking\n routers in the network. The document also describes a sinkhole\n tunnel technique using BGP communities and tunnels to pull traffic\n into a sinkhole router for analysis.","scope_keywords":["3882","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5635","folder":"IETF/RFC-5635","source":"IETF/RFC-5635/RFC-5635.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 3882 This document describes an operational technique that uses BGP\n communities to remotely trigger black-holing of a particular\n destination network to block denial-of-service attacks. Black-holing\n can be applied on a selection of routers rather than all BGP-speaking\n routers in the network. The document also describes a sinkhole\n tunnel technique using BGP communities and tunnels to pull traffic\n into a sinkhole router for analysis. 3882 path policies policy nested-reference unchanged"},{"id":"IETF RFC 4008","type":"specification","body":"IETF","designation":"RFC 4008","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4008.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4008.txt","https://www.rfc-editor.org/rfc/rfc4008.pdf"],"folder":"IETF/RFC-4008","files":{"txt":{"path":"standards/IETF/RFC-4008/RFC-4008.txt","sha256":"c07f7470090e575b6a9e071f499b0a747ce11bd09d0cfa5cc00b44c6e6f78956"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for devices implementing Network Address Translator (NAT) function.\n This MIB module may be used for configuration as well as monitoring\n of a device capable of NAT function.\n\nRohit, et al. Standards Track [Page 1]\n\f\nRFC 4008 NAT MIB March 2005","scope_keywords":["4008","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null}],"search_text":"IETF RFC 4008 This memo defines a portion of the Management Information Base (MIB)\n for devices implementing Network Address Translator (NAT) function.\n This MIB module may be used for configuration as well as monitoring\n of a device capable of NAT function.\n\nRohit, et al. Standards Track [Page 1]\n\f\nRFC 4008 NAT MIB March 2005 4008 key management presentation nested-reference unchanged"},{"id":"IETF RFC 4016","type":"specification","body":"IETF","designation":"RFC 4016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4016.txt","https://www.rfc-editor.org/rfc/rfc4016.pdf"],"folder":"IETF/RFC-4016","files":{"txt":{"path":"standards/IETF/RFC-4016/RFC-4016.txt","sha256":"cf91da73b5370a0fa398eb61d13794f8a561d0e96dda0636258548f9604cac23"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the threats to protocols used to carry\n authentication for network access. The security requirements arising\n from these threats will be used as additional input to the Protocol\n for Carrying Authentication for Network Access (PANA) Working Group\n for designing the IP based network access authentication protocol.","scope_keywords":["4016","authentication","credential","credentials","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null}],"search_text":"IETF RFC 4016 This document discusses the threats to protocols used to carry\n authentication for network access. The security requirements arising\n from these threats will be used as additional input to the Protocol\n for Carrying Authentication for Network Access (PANA) Working Group\n for designing the IP based network access authentication protocol. 4016 authentication credential credentials key path trust nested-reference unchanged"},{"id":"IETF RFC 4031","type":"specification","body":"IETF","designation":"RFC 4031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4031.txt","https://www.rfc-editor.org/rfc/rfc4031.pdf"],"folder":"IETF/RFC-4031","files":{"txt":{"path":"standards/IETF/RFC-4031/RFC-4031.txt","sha256":"7411e9f04ad93ffaec6f148ebd436a686673568d667fda2ec2387ffd1946c292"}},"tags":["nested-reference","unchanged"],"summary":"This document provides requirements for Layer 3 Virtual Private\n Networks (L3VPNs). It identifies requirements applicable to a number\n of individual approaches that a Service Provider may use to provision\n a Virtual Private Network (VPN) service. This document expresses a\n service provider perspective, based upon past experience with IP-\n based service offerings and the ever-evolving needs of the customers\n of such services. Toward this end, it first defines terminology and\n states general requirements. Detailed requirements are expressed\n from a customer perspective as well as that of a service provider.","scope_keywords":["4031","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null}],"search_text":"IETF RFC 4031 This document provides requirements for Layer 3 Virtual Private\n Networks (L3VPNs). It identifies requirements applicable to a number\n of individual approaches that a Service Provider may use to provision\n a Virtual Private Network (VPN) service. This document expresses a\n service provider perspective, based upon past experience with IP-\n based service offerings and the ever-evolving needs of the customers\n of such services. Toward this end, it first defines terminology and\n states general requirements. Detailed requirements are expressed\n from a customer perspective as well as that of a service provider. 4031 authentication management nested-reference unchanged"},{"id":"IETF RFC 4085","type":"specification","body":"IETF","designation":"RFC 4085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4085.txt","https://www.rfc-editor.org/rfc/rfc4085.pdf"],"folder":"IETF/RFC-4085","files":{"txt":{"path":"standards/IETF/RFC-4085/RFC-4085.txt","sha256":"3b5f497cce048cd28519a6be06b4f54728342e9e44a9f9805418d82d0468fef1"}},"tags":["nested-reference","unchanged"],"summary":"This document discourages the practice of embedding references to\n unique, globally-routable IP addresses in Internet hosts, describes\n some of the resulting problems, and considers selected alternatives.\n This document is intended to clarify best current practices in this\n regard.","scope_keywords":["4085","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 4085 This document discourages the practice of embedding references to\n unique, globally-routable IP addresses in Internet hosts, describes\n some of the resulting problems, and considers selected alternatives.\n This document is intended to clarify best current practices in this\n regard. 4085 management nested-reference unchanged"},{"id":"IETF RFC 4111","type":"specification","body":"IETF","designation":"RFC 4111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4111.txt","https://www.rfc-editor.org/rfc/rfc4111.pdf"],"folder":"IETF/RFC-4111","files":{"txt":{"path":"standards/IETF/RFC-4111/RFC-4111.txt","sha256":"c4aa93b5c7e5acbd20f8d0b1eb64e7722489b327d39dca9397e8a6babd37337f"}},"tags":["nested-reference","unchanged"],"summary":"This document addresses security aspects pertaining to Provider-\n Provisioned Virtual Private Networks (PPVPNs). First, it describes\n the security threats in the context of PPVPNs and defensive\n techniques to combat those threats. It considers security issues\n deriving both from malicious behavior of anyone and from negligent or\n incorrect behavior of the providers. It also describes how these\n security attacks should be detected and reported. It then discusses\n possible user requirements for security of a PPVPN service. These\n user requirements translate into corresponding provider requirements.\n In addition, the provider may have additional requirements to make\n its network infrastructure secure to a level that can meet the PPVPN\n customer's expectations. Finally, this document defines a template\n that may be used to describe and analyze the security characteristics\n of a specific PPVP","scope_keywords":["4111","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4111 This document addresses security aspects pertaining to Provider-\n Provisioned Virtual Private Networks (PPVPNs). First, it describes\n the security threats in the context of PPVPNs and defensive\n techniques to combat those threats. It considers security issues\n deriving both from malicious behavior of anyone and from negligent or\n incorrect behavior of the providers. It also describes how these\n security attacks should be detected and reported. It then discusses\n possible user requirements for security of a PPVPN service. These\n user requirements translate into corresponding provider requirements.\n In addition, the provider may have additional requirements to make\n its network infrastructure secure to a level that can meet the PPVPN\n customer's expectations. Finally, this document defines a template\n that may be used to describe and analyze the security characteristics\n of a specific PPVP 4111 authentication nested-reference unchanged"},{"id":"IETF RFC 4364","type":"specification","body":"IETF","designation":"RFC 4364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4364.txt","https://www.rfc-editor.org/rfc/rfc4364.pdf"],"folder":"IETF/RFC-4364","files":{"txt":{"path":"standards/IETF/RFC-4364/RFC-4364.txt","sha256":"33ad683b28ec97c72d3698ee0855ac8d5ec6472008bddb97b3cb8b30be1d8017"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method by which a Service Provider may use\n an IP backbone to provide IP Virtual Private Networks (VPNs) for its\n customers. This method uses a \"peer model\", in which the customers'\n edge routers (CE routers) send their routes to the Service Provider's\n edge routers (PE routers); there is no \"overlay\" visible to the\n customer's routing algorithm, and CE routers at different sites do\n not peer with each other. Data packets are tunneled through the\n backbone, so that the core routers do not need to know the VPN\n routes.\n\n This document obsoletes RFC 2547.\n\nRosen & Rekhter Standards Track [Page 1]\n\f\nRFC 4364 BGP/MPLS IP VPNs February 2006","scope_keywords":["4364","algorithm","attribute","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null}],"search_text":"IETF RFC 4364 This document describes a method by which a Service Provider may use\n an IP backbone to provide IP Virtual Private Networks (VPNs) for its\n customers. This method uses a \"peer model\", in which the customers'\n edge routers (CE routers) send their routes to the Service Provider's\n edge routers (PE routers); there is no \"overlay\" visible to the\n customer's routing algorithm, and CE routers at different sites do\n not peer with each other. Data packets are tunneled through the\n backbone, so that the core routers do not need to know the VPN\n routes.\n\n This document obsoletes RFC 2547.\n\nRosen & Rekhter Standards Track [Page 1]\n\f\nRFC 4364 BGP/MPLS IP VPNs February 2006 4364 algorithm attribute management policy nested-reference unchanged"},{"id":"IETF RFC 4365","type":"specification","body":"IETF","designation":"RFC 4365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4365.txt","https://www.rfc-editor.org/rfc/rfc4365.pdf"],"folder":"IETF/RFC-4365","files":{"txt":{"path":"standards/IETF/RFC-4365/RFC-4365.txt","sha256":"ce931a629c031cf805489d02a741fc34353b1d24aac4e63d485db1b83aa93470"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an Applicability Statement for the Virtual\n Private Network (VPN) solution described in RFC 4364 and other\n documents listed in the References section.","scope_keywords":["4365","algorithm","algorithms","authentication","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null}],"search_text":"IETF RFC 4365 This document provides an Applicability Statement for the Virtual\n Private Network (VPN) solution described in RFC 4364 and other\n documents listed in the References section. 4365 algorithm algorithms authentication management policy nested-reference unchanged"},{"id":"IETF RFC 4380","type":"specification","body":"IETF","designation":"RFC 4380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4380.txt","https://www.rfc-editor.org/rfc/rfc4380.pdf"],"folder":"IETF/RFC-4380","files":{"txt":{"path":"standards/IETF/RFC-4380/RFC-4380.txt","sha256":"fc2d00db57222cfe95aadb5a834192e17ad8fde3af84a009d1eb6fdba59199af"}},"tags":["nested-reference","unchanged"],"summary":"We propose here a service that enables nodes located behind one or\n more IPv4 Network Address Translations (NATs) to obtain IPv6\n connectivity by tunneling packets over UDP; we call this the Teredo\n service. Running the service requires the help of \"Teredo servers\"\n and \"Teredo relays\". The Teredo servers are stateless, and only have\n to manage a small fraction of the traffic between Teredo clients; the\n Teredo relays act as IPv6 routers between the Teredo service and the\n \"native\" IPv6 Internet. The relays can also provide interoperability\n with hosts using other transition mechanisms such as \"6to4\".","scope_keywords":["4380","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8190","folder":"IETF/RFC-8190","source":"IETF/RFC-8190/RFC-8190.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 4380 We propose here a service that enables nodes located behind one or\n more IPv4 Network Address Translations (NATs) to obtain IPv6\n connectivity by tunneling packets over UDP; we call this the Teredo\n service. Running the service requires the help of \"Teredo servers\"\n and \"Teredo relays\". The Teredo servers are stateless, and only have\n to manage a small fraction of the traffic between Teredo clients; the\n Teredo relays act as IPv6 routers between the Teredo service and the\n \"native\" IPv6 Internet. The relays can also provide interoperability\n with hosts using other transition mechanisms such as \"6to4\". 4380 path nested-reference unchanged"},{"id":"IETF RFC 4436","type":"specification","body":"IETF","designation":"RFC 4436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4436.txt","https://www.rfc-editor.org/rfc/rfc4436.pdf"],"folder":"IETF/RFC-4436","files":{"txt":{"path":"standards/IETF/RFC-4436/RFC-4436.txt","sha256":"96260704de9e2d49d1bc21d51c617d4b480a3c6adc68ca00510eebea0abcf46c"}},"tags":["nested-reference","unchanged"],"summary":"The time required to detect movement between networks and to obtain\n (or to continue to use) an IPv4 configuration may be significant as a\n fraction of the total handover latency in moving between points of\n attachment. This document synthesizes, from experience in the\n deployment of hosts supporting ARP, DHCP, and IPv4 Link-Local\n addresses, a set of steps known as Detecting Network Attachment for\n IPv4 (DNAv4), in order to decrease the handover latency in moving\n between points of attachment.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 4436 DNAv4 March 2006","scope_keywords":["4436","risk","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null}],"search_text":"IETF RFC 4436 The time required to detect movement between networks and to obtain\n (or to continue to use) an IPv4 configuration may be significant as a\n fraction of the total handover latency in moving between points of\n attachment. This document synthesizes, from experience in the\n deployment of hosts supporting ARP, DHCP, and IPv4 Link-Local\n addresses, a set of steps known as Detecting Network Attachment for\n IPv4 (DNAv4), in order to decrease the handover latency in moving\n between points of attachment.\n\nAboba, et al. Standards Track [Page 1]\n\f\nRFC 4436 DNAv4 March 2006 4436 risk validation nested-reference unchanged"},{"id":"IETF RFC 4576","type":"specification","body":"IETF","designation":"RFC 4576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4576.txt","https://www.rfc-editor.org/rfc/rfc4576.pdf"],"folder":"IETF/RFC-4576","files":{"txt":{"path":"standards/IETF/RFC-4576/RFC-4576.txt","sha256":"2fa2de2f45cd853c82f72ff1cb3ed20a23a8453b127f48690006f24726e520ea"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a procedure that deals with a particular\n issue that may arise when a Service Provider (SP) provides \"BGP/MPLS\n IP VPN\" service to a customer and the customer uses OSPFv2 to\n advertise its routes to the SP. In this situation, a Customer Edge\n (CE) Router and a Provider Edge (PE) Router are OSPF peers, and\n customer routes are sent via OSPFv2 from the CE to the PE. The\n customer routes are converted into BGP routes, and BGP carries them\n across the backbone to other PE routers. The routes are then\n converted back to OSPF routes sent via OSPF to other CE routers. As\n a result of this conversion, some of the information needed to\n prevent loops may be lost. A procedure is needed to ensure that once\n a route is sent from a PE to a CE, the route will be ignored by any\n PE that receives it back from a CE. This document specifies the\n necessary procedure, using one of th","scope_keywords":["4576","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null}],"search_text":"IETF RFC 4576 This document specifies a procedure that deals with a particular\n issue that may arise when a Service Provider (SP) provides \"BGP/MPLS\n IP VPN\" service to a customer and the customer uses OSPFv2 to\n advertise its routes to the SP. In this situation, a Customer Edge\n (CE) Router and a Provider Edge (PE) Router are OSPF peers, and\n customer routes are sent via OSPFv2 from the CE to the PE. The\n customer routes are converted into BGP routes, and BGP carries them\n across the backbone to other PE routers. The routes are then\n converted back to OSPF routes sent via OSPF to other CE routers. As\n a result of this conversion, some of the information needed to\n prevent loops may be lost. A procedure is needed to ensure that once\n a route is sent from a PE to a CE, the route will be ignored by any\n PE that receives it back from a CE. This document specifies the\n necessary procedure, using one of th 4576 key path nested-reference unchanged"},{"id":"IETF RFC 4843","type":"specification","body":"IETF","designation":"RFC 4843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4843.txt","https://www.rfc-editor.org/rfc/rfc4843.pdf"],"folder":"IETF/RFC-4843","files":{"txt":{"path":"standards/IETF/RFC-4843/RFC-4843.txt","sha256":"88a22df17c5e8a69ebb204d5e78e6862f3772cf0fccd6772aba5f273001ecea2"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces Overlay Routable Cryptographic Hash\n Identifiers (ORCHID) as a new, experimental class of IPv6-address-\n like identifiers. These identifiers are intended to be used as\n endpoint identifiers at applications and Application Programming\n Interfaces (API) and not as identifiers for network location at the\n IP layer, i.e., locators. They are designed to appear as application\n layer entities and at the existing IPv6 APIs, but they should not\n appear in actual IPv6 headers. To make them more like vanilla IPv6\n addresses, they are expected to be routable at an overlay level.\n Consequently, while they are considered non-routable addresses from\n the IPv6 layer point-of-view, all existing IPv6 applications are\n expected to be able to use them in a manner compatible with current\n IPv6 addresses.\n\n This document requests IANA to allocate a temporary prefix out of the\n IPv6 ad","scope_keywords":["4843","hash","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5338","folder":"IETF/RFC-5338","source":"IETF/RFC-5338/RFC-5338.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null}],"search_text":"IETF RFC 4843 This document introduces Overlay Routable Cryptographic Hash\n Identifiers (ORCHID) as a new, experimental class of IPv6-address-\n like identifiers. These identifiers are intended to be used as\n endpoint identifiers at applications and Application Programming\n Interfaces (API) and not as identifiers for network location at the\n IP layer, i.e., locators. They are designed to appear as application\n layer entities and at the existing IPv6 APIs, but they should not\n appear in actual IPv6 headers. To make them more like vanilla IPv6\n addresses, they are expected to be routable at an overlay level.\n Consequently, while they are considered non-routable addresses from\n the IPv6 layer point-of-view, all existing IPv6 applications are\n expected to be able to use them in a manner compatible with current\n IPv6 addresses.\n\n This document requests IANA to allocate a temporary prefix out of the\n IPv6 ad 4843 hash key trust nested-reference unchanged"},{"id":"IETF RFC 4864","type":"specification","body":"IETF","designation":"RFC 4864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4864.txt","https://www.rfc-editor.org/rfc/rfc4864.pdf"],"folder":"IETF/RFC-4864","files":{"txt":{"path":"standards/IETF/RFC-4864/RFC-4864.txt","sha256":"b1d91c59a4358eb417749fdf08daed2ccab9052b4d3426718def58e0b33e2b09"}},"tags":["nested-reference","unchanged"],"summary":"Although there are many perceived benefits to Network Address\n Translation (NAT), its primary benefit of \"amplifying\" available\n address space is not needed in IPv6. In addition to NAT's many\n serious disadvantages, there is a perception that other benefits\n exist, such as a variety of management and security attributes that\n could be useful for an Internet Protocol site. IPv6 was designed\n with the intention of making NAT unnecessary, and this document shows\n how Local Network Protection (LNP) using IPv6 can provide the same or\n more benefits without the need for address translation.\n\nVan de Velde, et al. Informational [Page 1]\n\f\nRFC 4864 Local Network Protection for IPv6 May 2007","scope_keywords":["4864","attribute","attributes","audit","management","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null}],"search_text":"IETF RFC 4864 Although there are many perceived benefits to Network Address\n Translation (NAT), its primary benefit of \"amplifying\" available\n address space is not needed in IPv6. In addition to NAT's many\n serious disadvantages, there is a perception that other benefits\n exist, such as a variety of management and security attributes that\n could be useful for an Internet Protocol site. IPv6 was designed\n with the intention of making NAT unnecessary, and this document shows\n how Local Network Protection (LNP) using IPv6 can provide the same or\n more benefits without the need for address translation.\n\nVan de Velde, et al. Informational [Page 1]\n\f\nRFC 4864 Local Network Protection for IPv6 May 2007 4864 attribute attributes audit management policy trust nested-reference unchanged"},{"id":"IETF RFC 5245","type":"specification","body":"IETF","designation":"RFC 5245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5245.txt","https://www.rfc-editor.org/rfc/rfc5245.pdf"],"folder":"IETF/RFC-5245","files":{"txt":{"path":"standards/IETF/RFC-5245/RFC-5245.txt","sha256":"d0a8b1bc60c63f451cd5f0c170ccc174c44f9f07fe1d0f969579e0aadf571076"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for Network Address Translator\n (NAT) traversal for UDP-based multimedia sessions established with\n the offer/answer model. This protocol is called Interactive\n Connectivity Establishment (ICE). ICE makes use of the Session\n Traversal Utilities for NAT (STUN) protocol and its extension,\n Traversal Using Relay NAT (TURN). ICE can be used by any protocol\n utilizing the offer/answer model, such as the Session Initiation\n Protocol (SIP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cur","scope_keywords":["5245","credential","credentials","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5769","folder":"IETF/RFC-5769","source":"IETF/RFC-5769/RFC-5769.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8421","folder":"IETF/RFC-8421","source":"IETF/RFC-8421/RFC-8421.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 5245 This document describes a protocol for Network Address Translator\n (NAT) traversal for UDP-based multimedia sessions established with\n the offer/answer model. This protocol is called Interactive\n Connectivity Establishment (ICE). ICE makes use of the Session\n Traversal Utilities for NAT (STUN) protocol and its extension,\n Traversal Using Relay NAT (TURN). ICE can be used by any protocol\n utilizing the offer/answer model, such as the Session Initiation\n Protocol (SIP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cur 5245 credential credentials http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5375","type":"specification","body":"IETF","designation":"RFC 5375","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5375.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5375.txt","https://www.rfc-editor.org/rfc/rfc5375.pdf"],"folder":"IETF/RFC-5375","files":{"txt":{"path":"standards/IETF/RFC-5375/RFC-5375.txt","sha256":"d86aee59662560da4bef7cf8abd5dc5055f7f3819c4e10761db9b5a6dbf28df3"}},"tags":["nested-reference","unchanged"],"summary":"One fundamental aspect of any IP communications infrastructure is its\n addressing plan. With its new address architecture and allocation\n policies, the introduction of IPv6 into a network means that network\n designers and operators need to reconsider their existing approaches\n to network addressing. Lack of guidelines on handling this aspect of\n network design could slow down the deployment and integration of\n IPv6. This document aims to provide the information and\n recommendations relevant to planning the addressing aspects of IPv6\n deployments. The document also provides IPv6 addressing case studies\n for both an enterprise and an ISP network.\n\nVan de Velde, et al. Informational [Page 1]\n\f\nRFC 5375 IPv6 Addressing Considerations December 2008","scope_keywords":["5375","http","identification","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null}],"search_text":"IETF RFC 5375 One fundamental aspect of any IP communications infrastructure is its\n addressing plan. With its new address architecture and allocation\n policies, the introduction of IPv6 into a network means that network\n designers and operators need to reconsider their existing approaches\n to network addressing. Lack of guidelines on handling this aspect of\n network design could slow down the deployment and integration of\n IPv6. This document aims to provide the information and\n recommendations relevant to planning the addressing aspects of IPv6\n deployments. The document also provides IPv6 addressing case studies\n for both an enterprise and an ISP network.\n\nVan de Velde, et al. Informational [Page 1]\n\f\nRFC 5375 IPv6 Addressing Considerations December 2008 5375 http identification license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5569","type":"specification","body":"IETF","designation":"RFC 5569","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5569.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5569.txt","https://www.rfc-editor.org/rfc/rfc5569.pdf"],"folder":"IETF/RFC-5569","files":{"txt":{"path":"standards/IETF/RFC-5569/RFC-5569.txt","sha256":"af2fb16486f0ff5db2ed9487f1e3d39db492c4dbc1f390a941742bf583abc2e9"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 rapid deployment on IPv4 infrastructures (6rd) builds upon\n mechanisms of 6to4 to enable a service provider to rapidly deploy\n IPv6 unicast service to IPv4 sites to which it provides customer\n premise equipment. Like 6to4, it utilizes stateless IPv6 in IPv4\n encapsulation in order to transit IPv4-only network infrastructure.\n Unlike 6to4, a 6rd service provider uses an IPv6 prefix of its own in\n place of the fixed 6to4 prefix. A service provider has used this\n mechanism for its own IPv6 \"rapid deployment\": five weeks from first\n exposure to 6rd principles to more than 1,500,000 residential sites\n being provided native IPv6, under the only condition that they\n activate it.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any\n other RFC stream","scope_keywords":["5569","http","license","pid","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5569 IPv6 rapid deployment on IPv4 infrastructures (6rd) builds upon\n mechanisms of 6to4 to enable a service provider to rapidly deploy\n IPv6 unicast service to IPv4 sites to which it provides customer\n premise equipment. Like 6to4, it utilizes stateless IPv6 in IPv4\n encapsulation in order to transit IPv4-only network infrastructure.\n Unlike 6to4, a 6rd service provider uses an IPv6 prefix of its own in\n place of the fixed 6to4 prefix. A service provider has used this\n mechanism for its own IPv6 \"rapid deployment\": five weeks from first\n exposure to 6rd principles to more than 1,500,000 residential sites\n being provided native IPv6, under the only condition that they\n activate it.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any\n other RFC stream 5569 http license pid presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5635","type":"specification","body":"IETF","designation":"RFC 5635","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5635.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5635.txt","https://www.rfc-editor.org/rfc/rfc5635.pdf"],"folder":"IETF/RFC-5635","files":{"txt":{"path":"standards/IETF/RFC-5635/RFC-5635.txt","sha256":"81678e073fa837e1cad66623f531cb57ff037cc49f4b96318671e09fd97936de"}},"tags":["nested-reference","unchanged"],"summary":"Remote Triggered Black Hole (RTBH) filtering is a popular and\n effective technique for the mitigation of denial-of-service attacks.\n This document expands upon destination-based RTBH filtering by\n outlining a method to enable filtering by source address as well.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nKumari & McPhers","scope_keywords":["5635","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null}],"search_text":"IETF RFC 5635 Remote Triggered Black Hole (RTBH) filtering is a popular and\n effective technique for the mitigation of denial-of-service attacks.\n This document expands upon destination-based RTBH filtering by\n outlining a method to enable filtering by source address as well.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nKumari & McPhers 5635 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5845","type":"specification","body":"IETF","designation":"RFC 5845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5845.txt","https://www.rfc-editor.org/rfc/rfc5845.pdf"],"folder":"IETF/RFC-5845","files":{"txt":{"path":"standards/IETF/RFC-5845/RFC-5845.txt","sha256":"ba24b028656693996834679b3a9a5f6b6c0da3f95a6e500123e3dd070d1da5e9"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a new mobility option for allowing the\n mobile access gateway and the local mobility anchor to negotiate\n Generic Routing Encapsulation (GRE) encapsulation mode and exchange\n the downlink and uplink GRE keys that are used for marking the\n downlink and uplink traffic that belong to a specific mobility\n session. In addition, the same mobility option can be used to\n negotiate the GRE encapsulation mode without exchanging the GRE keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current statu","scope_keywords":["5845","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null}],"search_text":"IETF RFC 5845 This specification defines a new mobility option for allowing the\n mobile access gateway and the local mobility anchor to negotiate\n Generic Routing Encapsulation (GRE) encapsulation mode and exchange\n the downlink and uplink GRE keys that are used for marking the\n downlink and uplink traffic that belong to a specific mobility\n session. In addition, the same mobility option can be used to\n negotiate the GRE encapsulation mode without exchanging the GRE keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current statu 5845 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5969","type":"specification","body":"IETF","designation":"RFC 5969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5969.txt","https://www.rfc-editor.org/rfc/rfc5969.pdf"],"folder":"IETF/RFC-5969","files":{"txt":{"path":"standards/IETF/RFC-5969/RFC-5969.txt","sha256":"df210f098cb6fe68d3c2d0dcfc2fe1c5b19b698d18a180fc3fc3c6c909dddac8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an automatic tunneling mechanism tailored to\n advance deployment of IPv6 to end users via a service provider's IPv4\n network infrastructure. Key aspects include automatic IPv6 prefix\n delegation to sites, stateless operation, simple provisioning, and\n service, which is equivalent to native IPv6 at the sites that are\n served by the mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w","scope_keywords":["5969","algorithm","delivery","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null}],"search_text":"IETF RFC 5969 This document specifies an automatic tunneling mechanism tailored to\n advance deployment of IPv6 to end users via a service provider's IPv4\n network infrastructure. Key aspects include automatic IPv6 prefix\n delegation to sites, stateless operation, simple provisioning, and\n service, which is equivalent to native IPv6 at the sites that are\n served by the mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w 5969 algorithm delivery http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 5991","type":"specification","body":"IETF","designation":"RFC 5991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5991.txt","https://www.rfc-editor.org/rfc/rfc5991.pdf"],"folder":"IETF/RFC-5991","files":{"txt":{"path":"standards/IETF/RFC-5991/RFC-5991.txt","sha256":"9fbe234171ba1f180b737b408540811e8a1e15b3b0ec96affa52ef09c5139098"}},"tags":["nested-reference","unchanged"],"summary":"The Teredo protocol defines a set of flags that are embedded in every\n Teredo IPv6 address. This document specifies a set of security\n updates that modify the use of this flags field, but are backward\n compatible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5991.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved","scope_keywords":["5991","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null}],"search_text":"IETF RFC 5991 The Teredo protocol defines a set of flags that are embedded in every\n Teredo IPv6 address. This document specifies a set of security\n updates that modify the use of this flags field, but are backward\n compatible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5991.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved 5991 http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6052","type":"specification","body":"IETF","designation":"RFC 6052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6052.txt","https://www.rfc-editor.org/rfc/rfc6052.pdf"],"folder":"IETF/RFC-6052","files":{"txt":{"path":"standards/IETF/RFC-6052/RFC-6052.txt","sha256":"f64b4695a351fe5f26698d12e8baefc609c30a8c36d259ace79d0f6e087e4bac"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the algorithmic translation of an IPv6\n address to a corresponding IPv4 address, and vice versa, using only\n statically configured information. It defines a well-known prefix\n for use in algorithmic translations, while allowing organizations to\n also use network-specific prefixes when appropriate. Algorithmic\n translation is used in IPv4/IPv6 translators, as well as other types\n of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the c","scope_keywords":["6052","algorithm","algorithms","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6052 This document discusses the algorithmic translation of an IPv6\n address to a corresponding IPv4 address, and vice versa, using only\n statically configured information. It defines a well-known prefix\n for use in algorithmic translations, while allowing organizations to\n also use network-specific prefixes when appropriate. Algorithmic\n translation is used in IPv4/IPv6 translators, as well as other types\n of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the c 6052 algorithm algorithms http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6081","type":"specification","body":"IETF","designation":"RFC 6081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6081.txt","https://www.rfc-editor.org/rfc/rfc6081.pdf"],"folder":"IETF/RFC-6081","files":{"txt":{"path":"standards/IETF/RFC-6081/RFC-6081.txt","sha256":"e65d87191bdf4161ec885fc025369fa6e8fe9c3c776a944c1ccab30923ace72f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of extensions to the Teredo protocol.\n These extensions provide additional capabilities to Teredo, including\n support for more types of Network Address Translations (NATs) and\n support for more efficient communication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6081.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n do","scope_keywords":["6081","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 6081 This document specifies a set of extensions to the Teredo protocol.\n These extensions provide additional capabilities to Teredo, including\n support for more types of Network Address Translations (NATs) and\n support for more efficient communication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6081.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n do 6081 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6127","type":"specification","body":"IETF","designation":"RFC 6127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6127.txt","https://www.rfc-editor.org/rfc/rfc6127.pdf"],"folder":"IETF/RFC-6127","files":{"txt":{"path":"standards/IETF/RFC-6127/RFC-6127.txt","sha256":"d1ddc063dee27472174b7ea2986801cc598ffa354b8b26ff000af4e727445c51"}},"tags":["nested-reference","unchanged"],"summary":"When IPv6 was designed, it was expected that the transition from IPv4\n to IPv6 would occur more smoothly and expeditiously than experience\n has revealed. The growth of the IPv4 Internet and predicted\n depletion of the free pool of IPv4 address blocks on a foreseeable\n horizon has highlighted an urgent need to revisit IPv6 deployment\n models. This document provides an overview of deployment scenarios\n with the goal of helping to understand what types of additional tools\n the industry needs to assist in IPv4 and IPv6 co-existence and\n transition.\n\n This document was originally created as input to the Montreal co-\n existence interim meeting in October 2008, which led to the\n rechartering of the Behave and Softwire working groups to take on new\n IPv4 and IPv6 co-existence work. This document is published as a\n historical record of the thinking at the time, but hopefully will\n also help reade","scope_keywords":["6127","driving","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null}],"search_text":"IETF RFC 6127 When IPv6 was designed, it was expected that the transition from IPv4\n to IPv6 would occur more smoothly and expeditiously than experience\n has revealed. The growth of the IPv4 Internet and predicted\n depletion of the free pool of IPv4 address blocks on a foreseeable\n horizon has highlighted an urgent need to revisit IPv6 deployment\n models. This document provides an overview of deployment scenarios\n with the goal of helping to understand what types of additional tools\n the industry needs to assist in IPv4 and IPv6 co-existence and\n transition.\n\n This document was originally created as input to the Montreal co-\n existence interim meeting in October 2008, which led to the\n rechartering of the Behave and Softwire working groups to take on new\n IPv4 and IPv6 co-existence work. This document is published as a\n historical record of the thinking at the time, but hopefully will\n also help reade 6127 driving http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6144","type":"specification","body":"IETF","designation":"RFC 6144","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6144.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6144.txt","https://www.rfc-editor.org/rfc/rfc6144.pdf"],"folder":"IETF/RFC-6144","files":{"txt":{"path":"standards/IETF/RFC-6144/RFC-6144.txt","sha256":"bf64c5caad1277a008c757964234d00d88d7cd5ee04d6585ce1b1c91bd3d0f22"}},"tags":["nested-reference","unchanged"],"summary":"This note describes a framework for IPv4/IPv6 translation. This is\n in the context of replacing Network Address Translation - Protocol\n Translation (NAT-PT), which was deprecated by RFC 4966, and to enable\n networks to have IPv4 and IPv6 coexist in a somewhat rational manner\n while transitioning to an IPv6 network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to p","scope_keywords":["6144","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 6144 This note describes a framework for IPv4/IPv6 translation. This is\n in the context of replacing Network Address Translation - Protocol\n Translation (NAT-PT), which was deprecated by RFC 4966, and to enable\n networks to have IPv4 and IPv6 coexist in a somewhat rational manner\n while transitioning to an IPv6 network.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to p 6144 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6281","type":"specification","body":"IETF","designation":"RFC 6281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6281.txt","https://www.rfc-editor.org/rfc/rfc6281.pdf"],"folder":"IETF/RFC-6281","files":{"txt":{"path":"standards/IETF/RFC-6281/RFC-6281.txt","sha256":"16ebc38c9892676a868a15da3cc68fc5e809f3b35d1296a41bc589068de697f0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the implementation of Apple Inc.'s Back to My\n Mac (BTMM) service. BTMM provides network connectivity between\n devices so that a user can perform file sharing and screen sharing\n among multiple computers at home, at work, or on the road. The\n implementation of BTMM addresses the issues of single sign-on\n authentication, secure data communication, service discovery, and\n end-to-end connectivity in the face of Network Address Translators\n (NATs) and mobility of devices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n app","scope_keywords":["6281","authentication","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null}],"search_text":"IETF RFC 6281 This document describes the implementation of Apple Inc.'s Back to My\n Mac (BTMM) service. BTMM provides network connectivity between\n devices so that a user can perform file sharing and screen sharing\n among multiple computers at home, at work, or on the road. The\n implementation of BTMM addresses the issues of single sign-on\n authentication, secure data communication, service discovery, and\n end-to-end connectivity in the face of Network Address Translators\n (NATs) and mobility of devices.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n app 6281 authentication delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6324","type":"specification","body":"IETF","designation":"RFC 6324","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6324.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6324.txt","https://www.rfc-editor.org/rfc/rfc6324.pdf"],"folder":"IETF/RFC-6324","files":{"txt":{"path":"standards/IETF/RFC-6324/RFC-6324.txt","sha256":"80cdad669074454f21ed8cb8457a9e86b47e72c015c64c40b77f5d13e2b29510"}},"tags":["nested-reference","unchanged"],"summary":"This document is concerned with security vulnerabilities in IPv6-in-\n IPv4 automatic tunnels. These vulnerabilities allow an attacker to\n take advantage of inconsistencies between the IPv4 routing state and\n the IPv6 routing state. The attack forms a routing loop that can be\n abused as a vehicle for traffic amplification to facilitate denial-\n of-service (DoS) attacks. The first aim of this document is to\n inform on this attack and its root causes. The second aim is to\n present some possible mitigation measures. It should be noted that\n at the time of this writing there are no known reports of malicious\n attacks exploiting these vulnerabilities. Nonetheless, these\n vulnerabilities can be activated by accidental misconfiguration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product ","scope_keywords":["6324","http","license","path","pid","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null}],"search_text":"IETF RFC 6324 This document is concerned with security vulnerabilities in IPv6-in-\n IPv4 automatic tunnels. These vulnerabilities allow an attacker to\n take advantage of inconsistencies between the IPv4 routing state and\n the IPv6 routing state. The attack forms a routing loop that can be\n abused as a vehicle for traffic amplification to facilitate denial-\n of-service (DoS) attacks. The first aim of this document is to\n inform on this attack and its root causes. The second aim is to\n present some possible mitigation measures. It should be noted that\n at the time of this writing there are no known reports of malicious\n attacks exploiting these vulnerabilities. Nonetheless, these\n vulnerabilities can be activated by accidental misconfiguration.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product  6324 http license path pid risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6343","type":"specification","body":"IETF","designation":"RFC 6343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6343.txt","https://www.rfc-editor.org/rfc/rfc6343.pdf"],"folder":"IETF/RFC-6343","files":{"txt":{"path":"standards/IETF/RFC-6343/RFC-6343.txt","sha256":"fb91d77875cb4ba3dd0e8054e3212614279bfe69e76c5fe7464feef77c408552"}},"tags":["nested-reference","unchanged"],"summary":"This document provides advice to network operators about deployment\n of the 6to4 technique for automatic tunneling of IPv6 over IPv4. It\n is principally addressed to Internet Service Providers (ISPs),\n including those that do not yet support IPv6, and to Content\n Providers. Some advice to implementers is also included. The\n intention of the advice is to minimize both user dissatisfaction and\n help-desk calls.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2","scope_keywords":["6343","http","license","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null}],"search_text":"IETF RFC 6343 This document provides advice to network operators about deployment\n of the 6to4 technique for automatic tunneling of IPv6 over IPv4. It\n is principally addressed to Internet Service Providers (ISPs),\n including those that do not yet support IPv6, and to Content\n Providers. Some advice to implementers is also included. The\n intention of the advice is to minimize both user dissatisfaction and\n help-desk calls.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 6343 http license qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6480","type":"specification","body":"IETF","designation":"RFC 6480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6480.txt","https://www.rfc-editor.org/rfc/rfc6480.pdf"],"folder":"IETF/RFC-6480","files":{"txt":{"path":"standards/IETF/RFC-6480/RFC-6480.txt","sha256":"e0e23a18c0e40ed96c4a169b7323c4157230bb9b1b8906aa4871b8a713921e3e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for an infrastructure to\n support improved security of Internet routing. The foundation of\n this architecture is a Resource Public Key Infrastructure (RPKI) that\n represents the allocation hierarchy of IP address space and\n Autonomous System (AS) numbers; and a distributed repository system\n for storing and disseminating the data objects that comprise the\n RPKI, as well as other signed objects necessary for improved routing\n security. As an initial application of this architecture, the\n document describes how a legitimate holder of IP address space can\n explicitly and verifiably authorize one or more ASes to originate\n routes to that address space. Such verifiable authorizations could\n be used, for example, to more securely construct BGP route filters.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n pub","scope_keywords":["6480","attestation","attestations","authorization","certificate","certificates","holder","http","key","license","management","pki","presentation","profile","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 6480 This document describes an architecture for an infrastructure to\n support improved security of Internet routing. The foundation of\n this architecture is a Resource Public Key Infrastructure (RPKI) that\n represents the allocation hierarchy of IP address space and\n Autonomous System (AS) numbers; and a distributed repository system\n for storing and disseminating the data objects that comprise the\n RPKI, as well as other signed objects necessary for improved routing\n security. As an initial application of this architecture, the\n document describes how a legitimate holder of IP address space can\n explicitly and verifiably authorize one or more ASes to originate\n routes to that address space. Such verifiable authorizations could\n be used, for example, to more securely construct BGP route filters.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n pub 6480 attestation attestations authorization certificate certificates holder http key license management pki presentation profile revocation subject nested-reference unchanged"},{"id":"IETF RFC 6535","type":"specification","body":"IETF","designation":"RFC 6535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6535.txt","https://www.rfc-editor.org/rfc/rfc6535.pdf"],"folder":"IETF/RFC-6535","files":{"txt":{"path":"standards/IETF/RFC-6535/RFC-6535.txt","sha256":"fcb37be00cc38a5d020e3d73de2b940c542a3d641f81ba44ea036182739dba5a"}},"tags":["nested-reference","unchanged"],"summary":"Bump-in-the-Host (BIH) is a host-based IPv4 to IPv6 protocol\n translation mechanism that allows a class of IPv4-only applications\n that work through NATs to communicate with IPv6-only peers. The host\n on which applications are running may be connected to IPv6-only or\n dual-stack access networks. BIH hides IPv6 and makes the IPv4-only\n applications think they are talking with IPv4 peers by local\n synthesis of IPv4 addresses. This document obsoletes RFC 2767 and\n RFC 3338.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the ","scope_keywords":["6535","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null}],"search_text":"IETF RFC 6535 Bump-in-the-Host (BIH) is a host-based IPv4 to IPv6 protocol\n translation mechanism that allows a class of IPv4-only applications\n that work through NATs to communicate with IPv6-only peers. The host\n on which applications are running may be connected to IPv6-only or\n dual-stack access networks. BIH hides IPv6 and makes the IPv4-only\n applications think they are talking with IPv4 peers by local\n synthesis of IPv4 addresses. This document obsoletes RFC 2767 and\n RFC 3338.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the  6535 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6598","type":"specification","body":"IETF","designation":"RFC 6598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6598.txt","https://www.rfc-editor.org/rfc/rfc6598.pdf"],"folder":"IETF/RFC-6598","files":{"txt":{"path":"standards/IETF/RFC-6598/RFC-6598.txt","sha256":"b04d16c5c98b89324d35dc6dc783eface0bedf94c14c9e289b646d39ea55c4c0"}},"tags":["nested-reference","unchanged"],"summary":"This document requests the allocation of an IPv4 /10 address block to\n be used as Shared Address Space to accommodate the needs of Carrier-\n Grade NAT (CGN) devices. It is anticipated that Service Providers\n will use this Shared Address Space to number the interfaces that\n connect CGN devices to Customer Premises Equipment (CPE).\n\n Shared Address Space is distinct from RFC 1918 private address space\n because it is intended for use on Service Provider networks.\n However, it may be used in a manner similar to RFC 1918 private\n address space on routing equipment that is able to do address\n translation across router interfaces when the addresses are identical\n on two different interfaces. Details are provided in the text of\n this document.\n\n This document details the allocation of an additional special-use\n IPv4 address block and updates RFC 5735.\n\nStatus of This Memo\n\n This memo documents a","scope_keywords":["6598","http","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7793","folder":"IETF/RFC-7793","source":"IETF/RFC-7793/RFC-7793.txt","version":null}],"search_text":"IETF RFC 6598 This document requests the allocation of an IPv4 /10 address block to\n be used as Shared Address Space to accommodate the needs of Carrier-\n Grade NAT (CGN) devices. It is anticipated that Service Providers\n will use this Shared Address Space to number the interfaces that\n connect CGN devices to Customer Premises Equipment (CPE).\n\n Shared Address Space is distinct from RFC 1918 private address space\n because it is intended for use on Service Provider networks.\n However, it may be used in a manner similar to RFC 1918 private\n address space on routing equipment that is able to do address\n translation across router interfaces when the addresses are identical\n on two different interfaces. Details are provided in the text of\n this document.\n\n This document details the allocation of an additional special-use\n IPv4 address block and updates RFC 5735.\n\nStatus of This Memo\n\n This memo documents a 6598 http key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6666","type":"specification","body":"IETF","designation":"RFC 6666","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6666.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6666.txt","https://www.rfc-editor.org/rfc/rfc6666.pdf"],"folder":"IETF/RFC-6666","files":{"txt":{"path":"standards/IETF/RFC-6666/RFC-6666.txt","sha256":"db6f7606b12f8e2949a78a76cd3b7622f77a7911f50a6a2e1b7c0897fe5a07f4"}},"tags":["nested-reference","unchanged"],"summary":"Remote triggered black hole filtering describes a method of\n mitigating the effects of denial-of-service attacks by selectively\n discarding traffic based on source or destination address. Remote\n triggered black hole routing describes a method of selectively re-\n routing traffic into a sinkhole router (for further analysis) based\n on destination address. This document updates the \"IPv6 Special\n Purpose Address Registry\" by explaining why a unique IPv6 prefix\n should be formally assigned by IANA for the purpose of facilitating\n IPv6 remote triggered black hole filtering and routing.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approve","scope_keywords":["6666","http","key","license","path","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null}],"search_text":"IETF RFC 6666 Remote triggered black hole filtering describes a method of\n mitigating the effects of denial-of-service attacks by selectively\n discarding traffic based on source or destination address. Remote\n triggered black hole routing describes a method of selectively re-\n routing traffic into a sinkhole router (for further analysis) based\n on destination address. This document updates the \"IPv6 Special\n Purpose Address Registry\" by explaining why a unique IPv6 prefix\n should be formally assigned by IANA for the purpose of facilitating\n IPv6 remote triggered black hole filtering and routing.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approve 6666 http key license path policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6791","type":"specification","body":"IETF","designation":"RFC 6791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6791.txt","https://www.rfc-editor.org/rfc/rfc6791.pdf"],"folder":"IETF/RFC-6791","files":{"txt":{"path":"standards/IETF/RFC-6791/RFC-6791.txt","sha256":"db56c1551a8f109090c4174b986412f3afac4381fa6045f20e65713577b3f992"}},"tags":["nested-reference","unchanged"],"summary":"A stateless IPv4/IPv6 translator may receive ICMPv6 packets\n containing non-IPv4-translatable addresses as the source. These\n packets should be passed across the translator as ICMP packets\n directed to the IPv4 destination. This document presents\n recommendations for source address translation in ICMPv6 headers to\n handle such cases.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6791.\n","scope_keywords":["6791","algorithm","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 6791 A stateless IPv4/IPv6 translator may receive ICMPv6 packets\n containing non-IPv4-translatable addresses as the source. These\n packets should be passed across the translator as ICMP packets\n directed to the IPv4 destination. This document presents\n recommendations for source address translation in ICMPv6 headers to\n handle such cases.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6791.\n 6791 algorithm http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6832","type":"specification","body":"IETF","designation":"RFC 6832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6832.txt","https://www.rfc-editor.org/rfc/rfc6832.pdf"],"folder":"IETF/RFC-6832","files":{"txt":{"path":"standards/IETF/RFC-6832/RFC-6832.txt","sha256":"c94f36d57025e2c9c7311e7ccfd732a1625d1d9b108fa2be77467e19762edab2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes techniques for allowing sites running the\n Locator/ID Separation Protocol (LISP) to interoperate with Internet\n sites that may be using either IPv4, IPv6, or both but that are not\n running LISP. A fundamental property of LISP-speaking sites is that\n they use Endpoint Identifiers (EIDs), rather than traditional IP\n addresses, in the source and destination fields of all traffic they\n emit or receive. While EIDs are syntactically identical to IPv4 or\n IPv6 addresses, normally routes to them are not carried in the global\n routing system, so an interoperability mechanism is needed for non-\n LISP-speaking sites to exchange traffic with LISP-speaking sites.\n This document introduces three such mechanisms. The first uses a new\n network element, the LISP Proxy Ingress Tunnel Router (Proxy-ITR), to\n act as an intermediate LISP Ingress Tunnel Router (ITR) for non-LISP-\n spea","scope_keywords":["6832","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6834","folder":"IETF/RFC-6834","source":"IETF/RFC-6834/RFC-6834.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null}],"search_text":"IETF RFC 6832 This document describes techniques for allowing sites running the\n Locator/ID Separation Protocol (LISP) to interoperate with Internet\n sites that may be using either IPv4, IPv6, or both but that are not\n running LISP. A fundamental property of LISP-speaking sites is that\n they use Endpoint Identifiers (EIDs), rather than traditional IP\n addresses, in the source and destination fields of all traffic they\n emit or receive. While EIDs are syntactically identical to IPv4 or\n IPv6 addresses, normally routes to them are not carried in the global\n routing system, so an interoperability mechanism is needed for non-\n LISP-speaking sites to exchange traffic with LISP-speaking sites.\n This document introduces three such mechanisms. The first uses a new\n network element, the LISP Proxy Ingress Tunnel Router (Proxy-ITR), to\n act as an intermediate LISP Ingress Tunnel Router (ITR) for non-LISP-\n spea 6832 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6866","type":"specification","body":"IETF","designation":"RFC 6866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6866.txt","https://www.rfc-editor.org/rfc/rfc6866.pdf"],"folder":"IETF/RFC-6866","files":{"txt":{"path":"standards/IETF/RFC-6866/RFC-6866.txt","sha256":"62d76ee83ee8cb9ef71cfbb3861566e765d75b2b721f2b33792b311d3dbd5247"}},"tags":["nested-reference","unchanged"],"summary":"This document analyses the problems of updating the IPv6 addresses of\n hosts in enterprise networks that, for operational reasons, require\n static addresses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6866.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified ","scope_keywords":["6866","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null}],"search_text":"IETF RFC 6866 This document analyses the problems of updating the IPv6 addresses of\n hosts in enterprise networks that, for operational reasons, require\n static addresses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6866.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified  6866 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6877","type":"specification","body":"IETF","designation":"RFC 6877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6877.txt","https://www.rfc-editor.org/rfc/rfc6877.pdf"],"folder":"IETF/RFC-6877","files":{"txt":{"path":"standards/IETF/RFC-6877/RFC-6877.txt","sha256":"8cf48d86948176ddc36a9ec7496b5e133381a2d091531eac429428efa5660336"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture (464XLAT) for providing\n limited IPv4 connectivity across an IPv6-only network by combining\n existing and well-known stateful protocol translation (as described\n in RFC 6146) in the core and stateless protocol translation (as\n described in RFC 6145) at the edge. 464XLAT is a simple and scalable\n technique to quickly deploy limited IPv4 access service to IPv6-only\n edge networks without encapsulation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of In","scope_keywords":["6877","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7335","folder":"IETF/RFC-7335","source":"IETF/RFC-7335/RFC-7335.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 6877 This document describes an architecture (464XLAT) for providing\n limited IPv4 connectivity across an IPv6-only network by combining\n existing and well-known stateful protocol translation (as described\n in RFC 6146) in the core and stateless protocol translation (as\n described in RFC 6145) at the edge. 464XLAT is a simple and scalable\n technique to quickly deploy limited IPv4 access service to IPv6-only\n edge networks without encapsulation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of In 6877 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6886","type":"specification","body":"IETF","designation":"RFC 6886","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6886.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6886.txt","https://www.rfc-editor.org/rfc/rfc6886.pdf"],"folder":"IETF/RFC-6886","files":{"txt":{"path":"standards/IETF/RFC-6886/RFC-6886.txt","sha256":"6fdc5bed10a2dc1f5cc31b110f93e3696624764cda94116c4c687f5c4d9d9979"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for automating the process of\n creating Network Address Translation (NAT) port mappings. Included\n in the protocol is a method for retrieving the external IPv4 address\n of a NAT gateway, thus allowing a client to make its external IPv4\n address and port known to peers that may wish to communicate with it.\n From 2005 onwards, this protocol was implemented in Apple products\n including Mac OS X, Bonjour for Windows, and AirPort wireless base\n stations. In 2013, NAT Port Mapping Protocol (NAT-PMP) was\n superseded by the IETF Standards Track RFC \"Port Control Protocol\n (PCP)\", which builds on NAT-PMP and uses a compatible packet format,\n but adds a number of significant enhancements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, i","scope_keywords":["6886","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null}],"search_text":"IETF RFC 6886 This document describes a protocol for automating the process of\n creating Network Address Translation (NAT) port mappings. Included\n in the protocol is a method for retrieving the external IPv4 address\n of a NAT gateway, thus allowing a client to make its external IPv4\n address and port known to peers that may wish to communicate with it.\n From 2005 onwards, this protocol was implemented in Apple products\n including Mac OS X, Bonjour for Windows, and AirPort wireless base\n stations. In 2013, NAT Port Mapping Protocol (NAT-PMP) was\n superseded by the IETF Standards Track RFC \"Port Control Protocol\n (PCP)\", which builds on NAT-PMP and uses a compatible packet format,\n but adds a number of significant enhancements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, i 6886 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7022","type":"specification","body":"IETF","designation":"RFC 7022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7022.txt","https://www.rfc-editor.org/rfc/rfc7022.pdf"],"folder":"IETF/RFC-7022","files":{"txt":{"path":"standards/IETF/RFC-7022/RFC-7022.txt","sha256":"c4cf3b9023b71606b37e519d971fd697f12701f010db318db1dd23d9fc0efdb0"}},"tags":["nested-reference","unchanged"],"summary":"The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a\n persistent transport-level identifier for an RTP endpoint. While the\n Synchronization Source (SSRC) identifier of an RTP endpoint may\n change if a collision is detected or when the RTP application is\n restarted, its RTCP CNAME is meant to stay unchanged, so that RTP\n endpoints can be uniquely identified and associated with their RTP\n media streams.\n\n For proper functionality, RTCP CNAMEs should be unique within the\n participants of an RTP session. However, the existing guidelines for\n choosing the RTCP CNAME provided in the RTP standard (RFC 3550) are\n insufficient to achieve this uniqueness. RFC 6222 was published to\n update those guidelines to allow endpoints to choose unique RTCP\n CNAMEs. Unfortunately, later investigations showed that some parts\n of the new algorithms were unnecessarily complicated and/or\n ineffective. This","scope_keywords":["7022","algorithm","algorithms","http","key","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7022 The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a\n persistent transport-level identifier for an RTP endpoint. While the\n Synchronization Source (SSRC) identifier of an RTP endpoint may\n change if a collision is detected or when the RTP application is\n restarted, its RTCP CNAME is meant to stay unchanged, so that RTP\n endpoints can be uniquely identified and associated with their RTP\n media streams.\n\n For proper functionality, RTCP CNAMEs should be unique within the\n participants of an RTP session. However, the existing guidelines for\n choosing the RTCP CNAME provided in the RTP standard (RFC 3550) are\n insufficient to achieve this uniqueness. RFC 6222 was published to\n update those guidelines to allow endpoints to choose unique RTCP\n CNAMEs. Unfortunately, later investigations showed that some parts\n of the new algorithms were unnecessarily complicated and/or\n ineffective. This 7022 algorithm algorithms http key license presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 7239","type":"specification","body":"IETF","designation":"RFC 7239","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7239.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7239.txt","https://www.rfc-editor.org/rfc/rfc7239.pdf"],"folder":"IETF/RFC-7239","files":{"txt":{"path":"standards/IETF/RFC-7239/RFC-7239.txt","sha256":"f15c45c9e079684bc4284d041be63285923962448cb0d8540d54106c68c2a40d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an HTTP extension header field that allows\n proxy components to disclose information lost in the proxying\n process, for example, the originating IP address of a request or IP\n address of the proxy on the user-agent-facing interface. In a path\n of proxying components, this makes it possible to arrange it so that\n each subsequent component will have access to, for example, all IP\n addresses used in the chain of proxied HTTP requests.\n\n This document also specifies guidelines for a proxy administrator to\n anonymize the origin of a request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informati","scope_keywords":["7239","http","identification","license","management","path","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 7239 This document defines an HTTP extension header field that allows\n proxy components to disclose information lost in the proxying\n process, for example, the originating IP address of a request or IP\n address of the proxy on the user-agent-facing interface. In a path\n of proxying components, this makes it possible to arrange it so that\n each subsequent component will have access to, for example, all IP\n addresses used in the chain of proxied HTTP requests.\n\n This document also specifies guidelines for a proxy administrator to\n anonymize the origin of a request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informati 7239 http identification license management path preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 7596","type":"specification","body":"IETF","designation":"RFC 7596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7596.txt","https://www.rfc-editor.org/rfc/rfc7596.pdf"],"folder":"IETF/RFC-7596","files":{"txt":{"path":"standards/IETF/RFC-7596/RFC-7596.txt","sha256":"b8190f294319a521769b6b915d28270c38834697e3528c10f5c8a669e6cfa39a"}},"tags":["nested-reference","unchanged"],"summary":"Dual-Stack Lite (DS-Lite) (RFC 6333) describes an architecture for\n transporting IPv4 packets over an IPv6 network. This document\n specifies an extension to DS-Lite called \"Lightweight 4over6\", which\n moves the Network Address and Port Translation (NAPT) function from\n the centralized DS-Lite tunnel concentrator to the tunnel client\n located in the Customer Premises Equipment (CPE). This removes the\n requirement for a Carrier Grade NAT function in the tunnel\n concentrator and reduces the amount of centralized state that must be\n held to a per-subscriber level. In order to delegate the NAPT\n function and make IPv4 address sharing possible, port-restricted IPv4\n addresses are allocated to the CPEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communit","scope_keywords":["7596","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7596 Dual-Stack Lite (DS-Lite) (RFC 6333) describes an architecture for\n transporting IPv4 packets over an IPv6 network. This document\n specifies an extension to DS-Lite called \"Lightweight 4over6\", which\n moves the Network Address and Port Translation (NAPT) function from\n the centralized DS-Lite tunnel concentrator to the tunnel client\n located in the Customer Premises Equipment (CPE). This removes the\n requirement for a Carrier Grade NAT function in the tunnel\n concentrator and reduces the amount of centralized state that must be\n held to a per-subscriber level. In order to delegate the NAPT\n function and make IPv4 address sharing possible, port-restricted IPv4\n addresses are allocated to the CPEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communit 7596 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7752","type":"specification","body":"IETF","designation":"RFC 7752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7752.txt","https://www.rfc-editor.org/rfc/rfc7752.pdf"],"folder":"IETF/RFC-7752","files":{"txt":{"path":"standards/IETF/RFC-7752/RFC-7752.txt","sha256":"a0dc4b3ca531d9b9b42a67aaa37b5e230b581b4d531d1097b11e26043bccd398"}},"tags":["nested-reference","unchanged"],"summary":"In a number of environments, a component external to a network is\n called upon to perform computations based on the network topology and\n current state of the connections within the network, including\n Traffic Engineering (TE) information. This is information typically\n distributed by IGP routing protocols within the network.\n\n This document describes a mechanism by which link-state and TE\n information can be collected from networks and shared with external\n components using the BGP routing protocol. This is achieved using a\n new BGP Network Layer Reachability Information (NLRI) encoding\n format. The mechanism is applicable to physical and virtual IGP\n links. The mechanism described is subject to policy control.\n\n Applications of this technique include Application-Layer Traffic\n Optimization (ALTO) servers and Path Computation Elements (PCEs).\n\nStatus of This Memo\n\n This is an Internet S","scope_keywords":["7752","attribute","http","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 7752 In a number of environments, a component external to a network is\n called upon to perform computations based on the network topology and\n current state of the connections within the network, including\n Traffic Engineering (TE) information. This is information typically\n distributed by IGP routing protocols within the network.\n\n This document describes a mechanism by which link-state and TE\n information can be collected from networks and shared with external\n components using the BGP routing protocol. This is achieved using a\n new BGP Network Layer Reachability Information (NLRI) encoding\n format. The mechanism is applicable to physical and virtual IGP\n links. The mechanism described is subject to policy control.\n\n Applications of this technique include Application-Layer Traffic\n Optimization (ALTO) servers and Path Computation Elements (PCEs).\n\nStatus of This Memo\n\n This is an Internet S 7752 attribute http license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7793","type":"specification","body":"IETF","designation":"RFC 7793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7793.txt","https://www.rfc-editor.org/rfc/rfc7793.pdf"],"folder":"IETF/RFC-7793","files":{"txt":{"path":"standards/IETF/RFC-7793/RFC-7793.txt","sha256":"3b5ce7ac345843471c78f23a19b2d93dbf17120ff323061aab27e7243c0b5e52"}},"tags":["nested-reference","unchanged"],"summary":"RFC 6598 specifies that \"Reverse DNS queries for Shared Address Space\n addresses [100.64.0.0/10] MUST NOT be forwarded to the global DNS\n infrastructure.\"\n\n This document formally directs IANA to add the associated zones to\n the \"IPv4 Locally-Served DNS Zones Registry\" to prevent such queries\n from accidentally leaking to the global DNS infrastructure.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/","scope_keywords":["7793","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7793 RFC 6598 specifies that \"Reverse DNS queries for Shared Address Space\n addresses [100.64.0.0/10] MUST NOT be forwarded to the global DNS\n infrastructure.\"\n\n This document formally directs IANA to add the associated zones to\n the \"IPv4 Locally-Served DNS Zones Registry\" to prevent such queries\n from accidentally leaking to the global DNS infrastructure.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/ 7793 http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7934","type":"specification","body":"IETF","designation":"RFC 7934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7934.txt","https://www.rfc-editor.org/rfc/rfc7934.pdf"],"folder":"IETF/RFC-7934","files":{"txt":{"path":"standards/IETF/RFC-7934/RFC-7934.txt","sha256":"00e68bf58a3cbb1bddc956ba24319068cdf43a05460b624b398f57ff3d80e6be"}},"tags":["nested-reference","unchanged"],"summary":"This document recommends that networks provide general-purpose end\n hosts with multiple global IPv6 addresses when they attach, and it\n describes the benefits of and the options for doing so.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7934.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subjec","scope_keywords":["7934","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7934 This document recommends that networks provide general-purpose end\n hosts with multiple global IPv6 addresses when they attach, and it\n describes the benefits of and the options for doing so.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7934.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subjec 7934 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8445","type":"specification","body":"IETF","designation":"RFC 8445","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8445.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8445.txt","https://www.rfc-editor.org/rfc/rfc8445.pdf"],"folder":"IETF/RFC-8445","files":{"txt":{"path":"standards/IETF/RFC-8445/RFC-8445.txt","sha256":"60bb913e8c8b2007f284105eef2faa2ea7e359dd4b73d7992557b3b11180065e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for Network Address Translator\n (NAT) traversal for UDP-based communication. This protocol is called\n Interactive Connectivity Establishment (ICE). ICE makes use of the\n Session Traversal Utilities for NAT (STUN) protocol and its\n extension, Traversal Using Relay NAT (TURN).\n\n This document obsoletes RFC 5245.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/in","scope_keywords":["8445","credential","credentials","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8421","folder":"IETF/RFC-8421","source":"IETF/RFC-8421/RFC-8421.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 8445 This document describes a protocol for Network Address Translator\n (NAT) traversal for UDP-based communication. This protocol is called\n Interactive Connectivity Establishment (ICE). ICE makes use of the\n Session Traversal Utilities for NAT (STUN) protocol and its\n extension, Traversal Using Relay NAT (TURN).\n\n This document obsoletes RFC 5245.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/in 8445 credential credentials http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 8828","type":"specification","body":"IETF","designation":"RFC 8828","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8828.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8828.txt","https://www.rfc-editor.org/rfc/rfc8828.pdf"],"folder":"IETF/RFC-8828","files":{"pdf":{"path":"standards/IETF/RFC-8828/RFC-8828.pdf","sha256":"b9db2ac0ed80d640a1f864acdc711998d9f76b6656b8c48742248cdea5038db0"},"txt":{"path":"standards/IETF/RFC-8828/RFC-8828.txt","sha256":"5467ddc37e9cfb71382abe9f7cd4f095b242f26504ca6763d1075451abbbcf01"}},"tags":["nested-reference","unchanged"],"summary":"This document provides information and requirements for how IP\n addresses should be handled by Web Real-Time Communication (WebRTC)\n implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8828.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg","scope_keywords":["8828","http","https","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null}],"search_text":"IETF RFC 8828 This document provides information and requirements for how IP\n addresses should be handled by Web Real-Time Communication (WebRTC)\n implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8828.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg 8828 http https key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8838","type":"specification","body":"IETF","designation":"RFC 8838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8838.txt","https://www.rfc-editor.org/rfc/rfc8838.pdf"],"folder":"IETF/RFC-8838","files":{"pdf":{"path":"standards/IETF/RFC-8838/RFC-8838.pdf","sha256":"a0a389bb7f72cc80f01fb24a4a4508af40e893fe9937ed8fec9ef9ef42863e3c"},"txt":{"path":"standards/IETF/RFC-8838/RFC-8838.txt","sha256":"3e6a19ddb1108f1e0de66c969c1ae1cb4d428f42cdddf0050d45062289ba683d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes \"Trickle ICE\", an extension to the\n Interactive Connectivity Establishment (ICE) protocol that enables\n ICE agents to begin connectivity checks while they are still\n gathering candidates, by incrementally exchanging candidates over\n time instead of all at once. This method can considerably accelerate\n the process of establishing a communication session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained ","scope_keywords":["8838","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null}],"search_text":"IETF RFC 8838 This document describes \"Trickle ICE\", an extension to the\n Interactive Connectivity Establishment (ICE) protocol that enables\n ICE agents to begin connectivity checks while they are still\n gathering candidates, by incrementally exchanging candidates over\n time instead of all at once. This method can considerably accelerate\n the process of establishing a communication session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained  8838 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 1925","type":"specification","body":"IETF","designation":"RFC 1925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1925.txt","https://www.rfc-editor.org/rfc/rfc1925.pdf"],"folder":"IETF/RFC-1925","files":{"txt":{"path":"standards/IETF/RFC-1925/RFC-1925.txt","sha256":"ea19f6e8d45a9fdc72bd7a4c8160c2be1b761cbee0aa84621cd8b6c09c3d5c9c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Callon, Editor\nRequest for Comments: 1925 IOOF\nCategory: Informational 1 April 1996\n\n The Twelve Networking Truths\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memo documents the fundamental truths of networking for the\n Internet community. This memo does not specify a standard, except in\n the sense that all standards must implicitly follow the fundamental\n truths.\n\nAcknowledgements\n\n The truths described in this memo result from extensive study over an\n extended period of time by many people, some of whom did not intend\n to contribute to this work. The editor merely has collected these\n truths, and would like to thank the networking community for\n originally illuminating these truths.\n\n1. Introduction\n\n This","scope_keywords":["1925","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null}],"search_text":"IETF RFC 1925 Network Working Group R. Callon, Editor\nRequest for Comments: 1925 IOOF\nCategory: Informational 1 April 1996\n\n The Twelve Networking Truths\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This memo documents the fundamental truths of networking for the\n Internet community. This memo does not specify a standard, except in\n the sense that all standards must implicitly follow the fundamental\n truths.\n\nAcknowledgements\n\n The truths described in this memo result from extensive study over an\n extended period of time by many people, some of whom did not intend\n to contribute to this work. The editor merely has collected these\n truths, and would like to thank the networking community for\n originally illuminating these truths.\n\n1. Introduction\n\n This 1925 presentation subject nested-reference unchanged"},{"id":"IETF RFC 5968","type":"specification","body":"IETF","designation":"RFC 5968","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5968.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5968.txt","https://www.rfc-editor.org/rfc/rfc5968.pdf"],"folder":"IETF/RFC-5968","files":{"txt":{"path":"standards/IETF/RFC-5968/RFC-5968.txt","sha256":"90a58ce6c4b99407e76552046d182e696f6558e1dffa666229a55481afa80abb"}},"tags":["nested-reference","unchanged"],"summary":"The RTP Control Protocol (RTCP) is used along with the Real-time\n Transport Protocol (RTP) to provide a control channel between media\n senders and receivers. This allows constructing a feedback loop to\n enable application adaptation and monitoring, among other uses. The\n basic reporting mechanisms offered by RTCP are generic, yet quite\n powerful and suffice to cover a range of uses. This document\n provides guidelines on extending RTCP if those basic mechanisms prove\n insufficient.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by th","scope_keywords":["5968","http","license","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 5968 The RTP Control Protocol (RTCP) is used along with the Real-time\n Transport Protocol (RTP) to provide a control channel between media\n senders and receivers. This allows constructing a feedback loop to\n enable application adaptation and monitoring, among other uses. The\n basic reporting mechanisms offered by RTCP are generic, yet quite\n powerful and suffice to cover a range of uses. This document\n provides guidelines on extending RTCP if those basic mechanisms prove\n insufficient.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by th 5968 http license profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6858","type":"specification","body":"IETF","designation":"RFC 6858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6858.txt","https://www.rfc-editor.org/rfc/rfc6858.pdf"],"folder":"IETF/RFC-6858","files":{"txt":{"path":"standards/IETF/RFC-6858/RFC-6858.txt","sha256":"ee2a26d72ca267c1d78124bab97b89f16a3662c02cc0487a7c974ce342772817"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for IMAP and POP servers to serve\n internationalized messages to conventional clients. The\n specification is simple, easy to implement, and provides only\n rudimentary results.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6858.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n T","scope_keywords":["6858","algorithm","http","license","path","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null}],"search_text":"IETF RFC 6858 This document specifies a method for IMAP and POP servers to serve\n internationalized messages to conventional clients. The\n specification is simple, easy to implement, and provides only\n rudimentary results.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6858.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n T 6858 algorithm http license path presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 1928","type":"specification","body":"IETF","designation":"RFC 1928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1928.txt","https://www.rfc-editor.org/rfc/rfc1928.pdf"],"folder":"IETF/RFC-1928","files":{"txt":{"path":"standards/IETF/RFC-1928/RFC-1928.txt","sha256":"ddc2916419a52bedae0fc7d0c051ea513e88c2b930dda27128982fb0c1d6fe2a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Leech\nRequest for Comments: 1928 Bell-Northern Research Ltd\nCategory: Standards Track M. Ganis\n International Business Machines\n Y. Lee\n NEC Systems Laboratory\n R. Kuris\n Unify Corporation\n D. Koblas\n Independent Consultant\n L. Jones\n Hewlett-Packard Company\n March 1996\n\n SOCKS Protocol Version 5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAcknowledgments\n\n This memo describes a protocol that is an evolution of the previous\n version of the protocol, version 4 [1]. This new protocol stems from\n active discussions and prototype implementations. The ke","scope_keywords":["1928","authentication","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1961","folder":"IETF/RFC-1961","source":"IETF/RFC-1961/RFC-1961.txt","version":null},{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 2588","folder":"IETF/RFC-2588","source":"IETF/RFC-2588/RFC-2588.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2979","folder":"IETF/RFC-2979","source":"IETF/RFC-2979/RFC-2979.txt","version":null},{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3089","folder":"IETF/RFC-3089","source":"IETF/RFC-3089/RFC-3089.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 1928 Network Working Group M. Leech\nRequest for Comments: 1928 Bell-Northern Research Ltd\nCategory: Standards Track M. Ganis\n International Business Machines\n Y. Lee\n NEC Systems Laboratory\n R. Kuris\n Unify Corporation\n D. Koblas\n Independent Consultant\n L. Jones\n Hewlett-Packard Company\n March 1996\n\n SOCKS Protocol Version 5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAcknowledgments\n\n This memo describes a protocol that is an evolution of the previous\n version of the protocol, version 4 [1]. This new protocol stems from\n active discussions and prototype implementations. The ke 1928 authentication http key nested-reference unchanged"},{"id":"IETF RFC 3089","type":"specification","body":"IETF","designation":"RFC 3089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3089.txt","https://www.rfc-editor.org/rfc/rfc3089.pdf"],"folder":"IETF/RFC-3089","files":{"txt":{"path":"standards/IETF/RFC-3089/RFC-3089.txt","sha256":"cd823c8df33418c395813c34470c925e90c7d5dfd1a642f08eac3eda2ee64607"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a SOCKS-based IPv6/IPv4 gateway mechanism\n that enables smooth heterogeneous communications between the IPv6\n nodes and IPv4 nodes.\n\n It is based on the SOCKS protocol [SOCKSv5]. By applying the SOCKS\n mechanism to the heterogeneous communications and relaying two\n \"terminated\" IPv4 and IPv6 connections at the \"application layer\"\n (the SOCKS server), the SOCKS-based IPv6/IPv4 gateway mechanism is\n accomplished.\n\n Since it is accomplished without introducing new protocols, it\n provides the same communication environment that is provided by the\n SOCKS mechanism. The same appearance is provided to the\n heterogeneous communications. No conveniences or functionalities of\n current communications are sacrificed.\n\n1. Introduction\n\n The SOCKS-based IPv6/IPv4 gateway mechanism is based on a mechanism\n that relays two \"terminated\" IPv4 and IPv6 connections at the\n \"applicati","scope_keywords":["3089","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 4219","folder":"IETF/RFC-4219","source":"IETF/RFC-4219/RFC-4219.txt","version":null},{"body":"IETF","designation":"RFC 6144","folder":"IETF/RFC-6144","source":"IETF/RFC-6144/RFC-6144.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null}],"search_text":"IETF RFC 3089 This document describes a SOCKS-based IPv6/IPv4 gateway mechanism\n that enables smooth heterogeneous communications between the IPv6\n nodes and IPv4 nodes.\n\n It is based on the SOCKS protocol [SOCKSv5]. By applying the SOCKS\n mechanism to the heterogeneous communications and relaying two\n \"terminated\" IPv4 and IPv6 connections at the \"application layer\"\n (the SOCKS server), the SOCKS-based IPv6/IPv4 gateway mechanism is\n accomplished.\n\n Since it is accomplished without introducing new protocols, it\n provides the same communication environment that is provided by the\n SOCKS mechanism. The same appearance is provided to the\n heterogeneous communications. No conveniences or functionalities of\n current communications are sacrificed.\n\n1. Introduction\n\n The SOCKS-based IPv6/IPv4 gateway mechanism is based on a mechanism\n that relays two \"terminated\" IPv4 and IPv6 connections at the\n \"applicati 3089 authentication nested-reference unchanged"},{"id":"IETF RFC 4887","type":"specification","body":"IETF","designation":"RFC 4887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4887.txt","https://www.rfc-editor.org/rfc/rfc4887.pdf"],"folder":"IETF/RFC-4887","files":{"txt":{"path":"standards/IETF/RFC-4887/RFC-4887.txt","sha256":"26f4ecbd58b5808dfb6218909366e6c31b0797735e6e851378cb9f05c4dd573d"}},"tags":["nested-reference","unchanged"],"summary":"This paper documents some of the usage patterns and the associated\n issues when deploying a Home Network for Network Mobility (NEMO)-\n enabled Mobile Routers, conforming to the NEMO Basic Support. The\n aim here is specifically to provide some examples of organization of\n the Home Network, as they were discussed in NEMO-related mailing\n lists.\n\nThubert, et al. Informational [Page 1]\n\f\nRFC 4887 Home Network Models with NEMO Basic July 2007","scope_keywords":["4887","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 4887 This paper documents some of the usage patterns and the associated\n issues when deploying a Home Network for Network Mobility (NEMO)-\n enabled Mobile Routers, conforming to the NEMO Basic Support. The\n aim here is specifically to provide some examples of organization of\n the Home Network, as they were discussed in NEMO-related mailing\n lists.\n\nThubert, et al. Informational [Page 1]\n\f\nRFC 4887 Home Network Models with NEMO Basic July 2007 4887 key trust nested-reference unchanged"},{"id":"IETF RFC 5128","type":"specification","body":"IETF","designation":"RFC 5128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5128.txt","https://www.rfc-editor.org/rfc/rfc5128.pdf"],"folder":"IETF/RFC-5128","files":{"txt":{"path":"standards/IETF/RFC-5128/RFC-5128.txt","sha256":"bd636ab15aba692b2d1b6fedb582655d00198adcdbd3a9beb5d4179a14065652"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents the various methods known to be in use by\n applications to establish direct communication in the presence of\n Network Address Translators (NATs) at the current time. Although\n this memo is intended to be mainly descriptive, the Security\n Considerations section makes some purely advisory recommendations\n about how to deal with security vulnerabilities the applications\n could inadvertently create when using the methods described. This\n memo covers NAT traversal approaches used by both TCP- and UDP-based\n applications. This memo is not an endorsement of the methods\n described, but merely an attempt to capture them in a document.\n\nSrisuresh, et al. Informational [Page 1]\n\f\nRFC 5128 State of P2P Communication across NATs March 2008","scope_keywords":["5128","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 5128 This memo documents the various methods known to be in use by\n applications to establish direct communication in the presence of\n Network Address Translators (NATs) at the current time. Although\n this memo is intended to be mainly descriptive, the Security\n Considerations section makes some purely advisory recommendations\n about how to deal with security vulnerabilities the applications\n could inadvertently create when using the methods described. This\n memo covers NAT traversal approaches used by both TCP- and UDP-based\n applications. This memo is not an endorsement of the methods\n described, but merely an attempt to capture them in a document.\n\nSrisuresh, et al. Informational [Page 1]\n\f\nRFC 5128 State of P2P Communication across NATs March 2008 5128 authentication nested-reference unchanged"},{"id":"IETF RFC 6455","type":"specification","body":"IETF","designation":"RFC 6455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6455.txt","https://www.rfc-editor.org/rfc/rfc6455.pdf"],"folder":"IETF/RFC-6455","files":{"txt":{"path":"standards/IETF/RFC-6455/RFC-6455.txt","sha256":"765775326aee0ecca9b04bde3fd1f52932d498e33e34e428bd61b8a24da0fa3b"}},"tags":["nested-reference","unchanged"],"summary":"The WebSocket Protocol enables two-way communication between a client\n running untrusted code in a controlled environment to a remote host\n that has opted-in to communications from that code. The security\n model used for this is the origin-based security model commonly used\n by web browsers. The protocol consists of an opening handshake\n followed by basic message framing, layered over TCP. The goal of\n this technology is to provide a mechanism for browser-based\n applications that need two-way communication with servers that does\n not rely on opening multiple HTTP connections (e.g., using\n XMLHttpRequest or <iframe>s and long polling).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for pub","scope_keywords":["6455","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8307","folder":"IETF/RFC-8307","source":"IETF/RFC-8307/RFC-8307.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 6455 The WebSocket Protocol enables two-way communication between a client\n running untrusted code in a controlled environment to a remote host\n that has opted-in to communications from that code. The security\n model used for this is the origin-based security model commonly used\n by web browsers. The protocol consists of an opening handshake\n followed by basic message framing, layered over TCP. The goal of\n this technology is to provide a mechanism for browser-based\n applications that need two-way communication with servers that does\n not rely on opening multiple HTTP connections (e.g., using\n XMLHttpRequest or <iframe>s and long polling).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for pub 6455 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6544","type":"specification","body":"IETF","designation":"RFC 6544","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6544.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6544.txt","https://www.rfc-editor.org/rfc/rfc6544.pdf"],"folder":"IETF/RFC-6544","files":{"txt":{"path":"standards/IETF/RFC-6544/RFC-6544.txt","sha256":"b1c710bdea09fa493d8d37689fa7ede15ace5d7b8245e9f47f54134e3d4c964a"}},"tags":["nested-reference","unchanged"],"summary":"Interactive Connectivity Establishment (ICE) defines a mechanism for\n NAT traversal for multimedia communication protocols based on the\n offer/answer model of session negotiation. ICE works by providing a\n set of candidate transport addresses for each media stream, which are\n then validated with peer-to-peer connectivity checks based on Session\n Traversal Utilities for NAT (STUN). ICE provides a general framework\n for describing candidates but only defines UDP-based media streams.\n This specification extends ICE to TCP-based media, including the\n ability to offer a mix of TCP and UDP-based candidates for a single\n stream.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by t","scope_keywords":["6544","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null}],"search_text":"IETF RFC 6544 Interactive Connectivity Establishment (ICE) defines a mechanism for\n NAT traversal for multimedia communication protocols based on the\n offer/answer model of session negotiation. ICE works by providing a\n set of candidate transport addresses for each media stream, which are\n then validated with peer-to-peer connectivity checks based on Session\n Traversal Utilities for NAT (STUN). ICE provides a general framework\n for describing candidates but only defines UDP-based media streams.\n This specification extends ICE to TCP-based media, including the\n ability to offer a mix of TCP and UDP-based candidates for a single\n stream.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by t 6544 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1929","type":"specification","body":"IETF","designation":"RFC 1929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1929.txt","https://www.rfc-editor.org/rfc/rfc1929.pdf"],"folder":"IETF/RFC-1929","files":{"txt":{"path":"standards/IETF/RFC-1929/RFC-1929.txt","sha256":"b023357f33b42ba1f3ae10b45ebfcc6dd7b6b13eba0743052b08ae3f7ae3581b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Leech\nRequest for Comments: 1929 Bell-Northern Research Ltd\nCategory: Standards Track March 1996\n\n Username/Password Authentication for SOCKS V5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n The protocol specification for SOCKS Version 5 specifies a\n generalized framework for the use of arbitrary authentication\n protocols in the initial socks connection setup. This document\n describes one of those protocols, as it fits into the SOCKS Version 5\n authentication \"subnegotiation\".\n\nNote:\n\n Unless otherwise noted, the decimal numbers appe","scope_keywords":["1929","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2356","folder":"IETF/RFC-2356","source":"IETF/RFC-2356/RFC-2356.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 1929 Network Working Group M. Leech\nRequest for Comments: 1929 Bell-Northern Research Ltd\nCategory: Standards Track March 1996\n\n Username/Password Authentication for SOCKS V5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Introduction\n\n The protocol specification for SOCKS Version 5 specifies a\n generalized framework for the use of arbitrary authentication\n protocols in the initial socks connection setup. This document\n describes one of those protocols, as it fits into the SOCKS Version 5\n authentication \"subnegotiation\".\n\nNote:\n\n Unless otherwise noted, the decimal numbers appe 1929 authentication nested-reference unchanged"},{"id":"IETF RFC 3138","type":"specification","body":"IETF","designation":"RFC 3138","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3138.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3138.txt","https://www.rfc-editor.org/rfc/rfc3138.pdf"],"folder":"IETF/RFC-3138","files":{"txt":{"path":"standards/IETF/RFC-3138/RFC-3138.txt","sha256":"8eba2de2540e11a4f1a9bec409eaf87eab983cd4c756aa019ce5132f32123ed3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Meyer\nRequest for Comments: 3138 Sprint\nCategory: Informational June 2001\n\n Extended Assignments in 233/8\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo provides describes the mapping of the GLOP addresses\n corresponding to the private AS space.\n\n1. Introduction\n\n RFC 2770 [RFC2770] describes an experimental policy for use of the\n class D address space using 233/8. The technique described there\n maps 16 bits of Autonomous System number (AS) into the middle two\n octets of 233/8 to yield a /24. While this technique has been\n successful, the assignments are inefficient in those cases in which a\n /24 is too small or the user doesn't h","scope_keywords":["3138","http","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null}],"search_text":"IETF RFC 3138 Network Working Group D. Meyer\nRequest for Comments: 3138 Sprint\nCategory: Informational June 2001\n\n Extended Assignments in 233/8\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo provides describes the mapping of the GLOP addresses\n corresponding to the private AS space.\n\n1. Introduction\n\n RFC 2770 [RFC2770] describes an experimental policy for use of the\n class D address space using 233/8. The technique described there\n maps 16 bits of Autonomous System number (AS) into the middle two\n octets of 233/8 to yield a /24. While this technique has been\n successful, the assignments are inefficient in those cases in which a\n /24 is too small or the user doesn't h 3138 http key management policy nested-reference unchanged"},{"id":"IETF RFC 6045","type":"specification","body":"IETF","designation":"RFC 6045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6045.txt","https://www.rfc-editor.org/rfc/rfc6045.pdf"],"folder":"IETF/RFC-6045","files":{"txt":{"path":"standards/IETF/RFC-6045/RFC-6045.txt","sha256":"9ee1e8a16a89ae1d4de560fe6c54696b3ee058313bb422411f351c4b47e0e916"}},"tags":["nested-reference","unchanged"],"summary":"Network security incidents, such as system compromises, worms,\n viruses, phishing incidents, and denial of service, typically result\n in the loss of service, data, and resources both human and system.\n Network providers and Computer Security Incident Response Teams need\n to be equipped and ready to assist in communicating and tracing\n security incidents with tools and procedures in place before the\n occurrence of an attack. Real-time Inter-network Defense (RID)\n outlines a proactive inter-network communication method to facilitate\n sharing incident handling data while integrating existing detection,\n tracing, source identification, and mitigation mechanisms for a\n complete incident handling solution. Combining these capabilities in\n a communication system provides a way to achieve higher security\n levels on networks. Policy guidelines for handling incidents are\n recommended and can be ag","scope_keywords":["6045","authentication","authorization","delivery","http","identification","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null}],"search_text":"IETF RFC 6045 Network security incidents, such as system compromises, worms,\n viruses, phishing incidents, and denial of service, typically result\n in the loss of service, data, and resources both human and system.\n Network providers and Computer Security Incident Response Teams need\n to be equipped and ready to assist in communicating and tracing\n security incidents with tools and procedures in place before the\n occurrence of an attack. Real-time Inter-network Defense (RID)\n outlines a proactive inter-network communication method to facilitate\n sharing incident handling data while integrating existing detection,\n tracing, source identification, and mitigation mechanisms for a\n complete incident handling solution. Combining these capabilities in\n a communication system provides a way to achieve higher security\n levels on networks. Policy guidelines for handling incidents are\n recommended and can be ag 6045 authentication authorization delivery http identification key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6545","type":"specification","body":"IETF","designation":"RFC 6545","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6545.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6545.txt","https://www.rfc-editor.org/rfc/rfc6545.pdf"],"folder":"IETF/RFC-6545","files":{"txt":{"path":"standards/IETF/RFC-6545/RFC-6545.txt","sha256":"7733d33fff3394cba622a847a87da3bbc9bcf248e6679cd0e73f73008161674e"}},"tags":["nested-reference","unchanged"],"summary":"Security incidents, such as system compromises, worms, viruses,\n phishing incidents, and denial of service, typically result in the\n loss of service, data, and resources both human and system. Service\n providers and Computer Security Incident Response Teams need to be\n equipped and ready to assist in communicating and tracing security\n incidents with tools and procedures in place before the occurrence of\n an attack. Real-time Inter-network Defense (RID) outlines a\n proactive inter-network communication method to facilitate sharing\n incident-handling data while integrating existing detection, tracing,\n source identification, and mitigation mechanisms for a complete\n incident-handling solution. Combining these capabilities in a\n communication system provides a way to achieve higher security levels\n on networks. Policy guidelines for handling incidents are\n recommended and can be agreed upo","scope_keywords":["6545","authentication","encryption","http","identification","key","license","policies","policy","profile","profiles","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8073","folder":"IETF/RFC-8073","source":"IETF/RFC-8073/RFC-8073.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 6545 Security incidents, such as system compromises, worms, viruses,\n phishing incidents, and denial of service, typically result in the\n loss of service, data, and resources both human and system. Service\n providers and Computer Security Incident Response Teams need to be\n equipped and ready to assist in communicating and tracing security\n incidents with tools and procedures in place before the occurrence of\n an attack. Real-time Inter-network Defense (RID) outlines a\n proactive inter-network communication method to facilitate sharing\n incident-handling data while integrating existing detection, tracing,\n source identification, and mitigation mechanisms for a complete\n incident-handling solution. Combining these capabilities in a\n communication system provides a way to achieve higher security levels\n on networks. Policy guidelines for handling incidents are\n recommended and can be agreed upo 6545 authentication encryption http identification key license policies policy profile profiles signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8007","type":"specification","body":"IETF","designation":"RFC 8007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8007.txt","https://www.rfc-editor.org/rfc/rfc8007.pdf"],"folder":"IETF/RFC-8007","files":{"txt":{"path":"standards/IETF/RFC-8007/RFC-8007.txt","sha256":"6174966f729ea171702a4d3630a78a7d67432e8770f8c9883d7bff8299a5dc8f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the part of the Content Delivery Network\n Interconnection (CDNI) Control interface that allows a CDN to trigger\n activity in an interconnected CDN that is configured to deliver\n content on its behalf. The upstream CDN can use this mechanism to\n request that the downstream CDN pre-position metadata or content or\n to request that it invalidate or purge metadata or content. The\n upstream CDN can monitor the status of activity that it has triggered\n in the downstream CDN.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n I","scope_keywords":["8007","authentication","authorization","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null}],"search_text":"IETF RFC 8007 This document describes the part of the Content Delivery Network\n Interconnection (CDNI) Control interface that allows a CDN to trigger\n activity in an interconnected CDN that is configured to deliver\n content on its behalf. The upstream CDN can use this mechanism to\n request that the downstream CDN pre-position metadata or content or\n to request that it invalidate or purge metadata or content. The\n upstream CDN can monitor the status of activity that it has triggered\n in the downstream CDN.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n I 8007 authentication authorization delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2185","type":"specification","body":"IETF","designation":"RFC 2185","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2185.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2185.txt","https://www.rfc-editor.org/rfc/rfc2185.pdf"],"folder":"IETF/RFC-2185","files":{"txt":{"path":"standards/IETF/RFC-2185/RFC-2185.txt","sha256":"e5c96b8fb543a028d0314e10a698eccaca645c607da77b1d56e8958249aecefc"}},"tags":["nested-reference","unchanged"],"summary":"This document gives an overview of the routing aspects of the IPv6\n transition. It is based on the protocols defined in the document\n \"Transition Mechanisms for IPv6 Hosts and Routers\" [1]. Readers\n should be familiar with the transition mechanisms before reading this\n document.\n\n The proposals contained in this document are based on the work of the\n Ngtrans working group.\n\n1. TERMINOLOGY\n\n This paper uses the following terminology:\n\n node - a protocol module that implements IPv4 or IPv6.\n\n router - a node that forwards packets not explicitly\n addressed to itself.\n\n host - any node that is not a router.\n\n border router - a router that forwards packets across\n routing domain boundaries.\n\n link - a communication facility or medium over which\n nodes can communicate at the link layer, i.e., the layer\n immediately below internet layer.\n\n interface - a node's attachment to a link.\n\n address - ","scope_keywords":["2185","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null}],"search_text":"IETF RFC 2185 This document gives an overview of the routing aspects of the IPv6\n transition. It is based on the protocols defined in the document\n \"Transition Mechanisms for IPv6 Hosts and Routers\" [1]. Readers\n should be familiar with the transition mechanisms before reading this\n document.\n\n The proposals contained in this document are based on the work of the\n Ngtrans working group.\n\n1. TERMINOLOGY\n\n This paper uses the following terminology:\n\n node - a protocol module that implements IPv4 or IPv6.\n\n router - a node that forwards packets not explicitly\n addressed to itself.\n\n host - any node that is not a router.\n\n border router - a router that forwards packets across\n routing domain boundaries.\n\n link - a communication facility or medium over which\n nodes can communicate at the link layer, i.e., the layer\n immediately below internet layer.\n\n interface - a node's attachment to a link.\n\n address -  2185 path nested-reference unchanged"},{"id":"IETF RFC 3053","type":"specification","body":"IETF","designation":"RFC 3053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3053.txt","https://www.rfc-editor.org/rfc/rfc3053.pdf"],"folder":"IETF/RFC-3053","files":{"txt":{"path":"standards/IETF/RFC-3053/RFC-3053.txt","sha256":"8d8bec931a52aee8d736f8b29f64e6538160f585d5e19df23ba361b3e9044e70"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 global Internet as of today uses a lot of tunnels over the\n existing IPv4 infrastructure. Those tunnels are difficult to\n configure and maintain in a large scale environment. The 6bone has\n proven that large sites and Internet Service Providers (ISPs) can do\n it, but this process is too complex for the isolated end user who\n already has an IPv4 connection and would like to enter the IPv6\n world. The motivation for the development of the tunnel broker model\n is to help early IPv6 adopters to hook up to an existing IPv6 network\n (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS\n names. The concept of the tunnel broker was first presented at\n Orlando's IETF in December 1998. Two implementations were\n demonstrated during the Grenoble IPng & NGtrans interim meeting in\n February 1999.\n\n1. Introduction\n\n The growth of IPv6 networks started mainly using the transport","scope_keywords":["3053","http","management","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null}],"search_text":"IETF RFC 3053 The IPv6 global Internet as of today uses a lot of tunnels over the\n existing IPv4 infrastructure. Those tunnels are difficult to\n configure and maintain in a large scale environment. The 6bone has\n proven that large sites and Internet Service Providers (ISPs) can do\n it, but this process is too complex for the isolated end user who\n already has an IPv4 connection and would like to enter the IPv6\n world. The motivation for the development of the tunnel broker model\n is to help early IPv6 adopters to hook up to an existing IPv6 network\n (e.g., the 6bone) and to get stable, permanent IPv6 addresses and DNS\n names. The concept of the tunnel broker was first presented at\n Orlando's IETF in December 1998. Two implementations were\n demonstrated during the Grenoble IPng & NGtrans interim meeting in\n February 1999.\n\n1. Introduction\n\n The growth of IPv6 networks started mainly using the transport 3053 http management policies nested-reference unchanged"},{"id":"IETF RFC 1936","type":"specification","body":"IETF","designation":"RFC 1936","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1936.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1936.txt","https://www.rfc-editor.org/rfc/rfc1936.pdf"],"folder":"IETF/RFC-1936","files":{"txt":{"path":"standards/IETF/RFC-1936/RFC-1936.txt","sha256":"7770647110401b79f7aeda3b7af4f7ae1d2e2b3c20c93dc4410634b20fba6ae8"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a techniques for efficiently implementing the\n Internet Checksum in hardware. It includes PLD code for programming a\n single, low cost part to perform checksumming at 1.26 Gbps.","scope_keywords":["1936","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 1936 This memo presents a techniques for efficiently implementing the\n Internet Checksum in hardware. It includes PLD code for programming a\n single, low cost part to perform checksumming at 1.26 Gbps. 1936 algorithm nested-reference unchanged"},{"id":"IETF RFC 3206","type":"specification","body":"IETF","designation":"RFC 3206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3206.txt","https://www.rfc-editor.org/rfc/rfc3206.pdf"],"folder":"IETF/RFC-3206","files":{"txt":{"path":"standards/IETF/RFC-3206/RFC-3206.txt","sha256":"021d7a7156306aa6bbd1818a34c9aa7f068a7cc539e5dc4d18e0de6f9b202977"}},"tags":["nested-reference","unchanged"],"summary":"This memo proposes two response codes: SYS and AUTH, which enable\n clients to unambiguously determine an optimal response to an\n authentication failure. In addition, a new capability (AUTH-RESP-\n CODE) is defined.","scope_keywords":["3206","authentication","credential","credentials","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null}],"search_text":"IETF RFC 3206 This memo proposes two response codes: SYS and AUTH, which enable\n clients to unambiguously determine an optimal response to an\n authentication failure. In addition, a new capability (AUTH-RESP-\n CODE) is defined. 3206 authentication credential credentials key policy nested-reference unchanged"},{"id":"IETF RFC 3656","type":"specification","body":"IETF","designation":"RFC 3656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3656.txt","https://www.rfc-editor.org/rfc/rfc3656.pdf"],"folder":"IETF/RFC-3656","files":{"txt":{"path":"standards/IETF/RFC-3656/RFC-3656.txt","sha256":"cd9f0ec979cf7b4fdcafccd4123c121d135d845118038d3bd926ff13afb84c73"}},"tags":["nested-reference","unchanged"],"summary":"As the demand for high-performance mail delivery agents increases, it\n becomes apparent that single-machine solutions are inadequate to the\n task, both because of capacity limits and that the failure of the\n single machine means a loss of mail delivery for all users. It is\n preferable to allow many machines to share the responsibility of mail\n delivery.\n\n The Mailbox Update (MUPDATE) protocol allows a group of Internet\n Message Access Protocol (IMAP) or Post Office Protocol - Version 3\n (POP3) servers to function with a unified mailbox namespace. This\n document is intended to serve as a reference guide to that protocol.\n\nSiemborski Experimental [Page 1]\n\f\nRFC 3656 MUPDATE Distributed Mailbox Database Protocol December 2003","scope_keywords":["3656","crl","delivery","key","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3656 As the demand for high-performance mail delivery agents increases, it\n becomes apparent that single-machine solutions are inadequate to the\n task, both because of capacity limits and that the failure of the\n single machine means a loss of mail delivery for all users. It is\n preferable to allow many machines to share the responsibility of mail\n delivery.\n\n The Mailbox Update (MUPDATE) protocol allows a group of Internet\n Message Access Protocol (IMAP) or Post Office Protocol - Version 3\n (POP3) servers to function with a unified mailbox namespace. This\n document is intended to serve as a reference guide to that protocol.\n\nSiemborski Experimental [Page 1]\n\f\nRFC 3656 MUPDATE Distributed Mailbox Database Protocol December 2003 3656 crl delivery key registered tls nested-reference unchanged"},{"id":"IETF RFC 3887","type":"specification","body":"IETF","designation":"RFC 3887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3887.txt","https://www.rfc-editor.org/rfc/rfc3887.pdf"],"folder":"IETF/RFC-3887","files":{"txt":{"path":"standards/IETF/RFC-3887/RFC-3887.txt","sha256":"0b36c19a03be5422060b6f6cc4c20c114939a04b1e21894257fecbe969b6fb21"}},"tags":["nested-reference","unchanged"],"summary":"Customers buying enterprise message systems often ask: Can I track\n the messages? Message tracking is the ability to find out the path\n that a particular message has taken through a messaging system and\n the current routing status of that message. This document describes\n the Message Tracking Query Protocol that is used in conjunction with\n extensions to the ESMTP protocol to provide a complete message\n tracking solution for the Internet.\n\n1. Introduction\n\n The Message Tracking Models and Requirements document\n [RFC-MTRK-MODEL] discusses the models that message tracking solutions\n could follow, along with requirements for a message tracking solution\n that can be used with the Internet-wide message infrastructure. This\n memo and its companions, [RFC-MTRK-ESMTP] and [RFC-MTRK-TSN],\n describe a complete message tracking solution that satisfies those\n requirements. The memo [RFC-MTRK-ESMTP] ","scope_keywords":["3887","crl","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3887 Customers buying enterprise message systems often ask: Can I track\n the messages? Message tracking is the ability to find out the path\n that a particular message has taken through a messaging system and\n the current routing status of that message. This document describes\n the Message Tracking Query Protocol that is used in conjunction with\n extensions to the ESMTP protocol to provide a complete message\n tracking solution for the Internet.\n\n1. Introduction\n\n The Message Tracking Models and Requirements document\n [RFC-MTRK-MODEL] discusses the models that message tracking solutions\n could follow, along with requirements for a message tracking solution\n that can be used with the Internet-wide message infrastructure. This\n memo and its companions, [RFC-MTRK-ESMTP] and [RFC-MTRK-TSN],\n describe a complete message tracking solution that satisfies those\n requirements. The memo [RFC-MTRK-ESMTP]  3887 crl key path nested-reference unchanged"},{"id":"IETF RFC 4686","type":"specification","body":"IETF","designation":"RFC 4686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4686.txt","https://www.rfc-editor.org/rfc/rfc4686.pdf"],"folder":"IETF/RFC-4686","files":{"txt":{"path":"standards/IETF/RFC-4686/RFC-4686.txt","sha256":"ebff643681e4761032ca8271b0a3421b5c1962f0bdc9878642bd499b65cd272f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an analysis of some threats against Internet\n mail that are intended to be addressed by signature-based mail\n authentication, in particular DomainKeys Identified Mail. It\n discusses the nature and location of the bad actors, what their\n capabilities are, and what they intend to accomplish via their\n attacks.\n\nFenton Informational [Page 1]\n\f\nRFC 4686 DKIM Threat Analysis September 2006","scope_keywords":["4686","accreditation","authentication","key","keys","path","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 5016","folder":"IETF/RFC-5016","source":"IETF/RFC-5016/RFC-5016.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null}],"search_text":"IETF RFC 4686 This document provides an analysis of some threats against Internet\n mail that are intended to be addressed by signature-based mail\n authentication, in particular DomainKeys Identified Mail. It\n discusses the nature and location of the bad actors, what their\n capabilities are, and what they intend to accomplish via their\n attacks.\n\nFenton Informational [Page 1]\n\f\nRFC 4686 DKIM Threat Analysis September 2006 4686 accreditation authentication key keys path signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 5423","type":"specification","body":"IETF","designation":"RFC 5423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5423.txt","https://www.rfc-editor.org/rfc/rfc5423.pdf"],"folder":"IETF/RFC-5423","files":{"txt":{"path":"standards/IETF/RFC-5423/RFC-5423.txt","sha256":"efd62b05bae425039778f6871b1edd88944002b1382545e243449d4e18204cc8"}},"tags":["nested-reference","unchanged"],"summary":"One of the missing features in the existing Internet mail and\n messaging standards is a facility for server-to-server and server-to-\n client event notifications related to message store events. As the\n scope of Internet mail expands to support more diverse media (such as\n voice mail) and devices (such as cell phones) and to provide rich\n interactions with other services (such as web portals and legal\n compliance systems), the need for an interoperable notification\n system increases. This document attempts to enumerate the types of\n events that interest real-world consumers of such a system.\n\n This document describes events and event parameters that are useful\n for several cases, including notification to administrative systems\n and end users. This is not intended as a replacement for a message\n access facility such as IMAP.\n\nGellens & Newman Standards Track [Page 1]\n\f\nRFC 5423 Internet M","scope_keywords":["5423","audit","delivery","driving","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null}],"search_text":"IETF RFC 5423 One of the missing features in the existing Internet mail and\n messaging standards is a facility for server-to-server and server-to-\n client event notifications related to message store events. As the\n scope of Internet mail expands to support more diverse media (such as\n voice mail) and devices (such as cell phones) and to provide rich\n interactions with other services (such as web portals and legal\n compliance systems), the need for an interoperable notification\n system increases. This document attempts to enumerate the types of\n events that interest real-world consumers of such a system.\n\n This document describes events and event parameters that are useful\n for several cases, including notification to administrative systems\n and end users. This is not intended as a replacement for a message\n access facility such as IMAP.\n\nGellens & Newman Standards Track [Page 1]\n\f\nRFC 5423 Internet M 5423 audit delivery driving http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5721","type":"specification","body":"IETF","designation":"RFC 5721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5721.txt","https://www.rfc-editor.org/rfc/rfc5721.pdf"],"folder":"IETF/RFC-5721","files":{"txt":{"path":"standards/IETF/RFC-5721/RFC-5721.txt","sha256":"fb00dc5bbfd6852a253420ed0204372214f3cff538df3ac79904d9a02d992415"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Post Office Protocol version 3 (POP3)\n to support un-encoded international characters in user names,\n passwords, mail addresses, message headers, and protocol-level\n textual error strings.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,","scope_keywords":["5721","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null}],"search_text":"IETF RFC 5721 This specification extends the Post Office Protocol version 3 (POP3)\n to support un-encoded international characters in user names,\n passwords, mail addresses, message headers, and protocol-level\n textual error strings.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata, 5721 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6186","type":"specification","body":"IETF","designation":"RFC 6186","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6186.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6186.txt","https://www.rfc-editor.org/rfc/rfc6186.pdf"],"folder":"IETF/RFC-6186","files":{"txt":{"path":"standards/IETF/RFC-6186/RFC-6186.txt","sha256":"5aa0cbe29fa7106f5a41f37b5189cb1c259897f351dc4c304d82b031b297638c"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes how SRV records can be used to locate\n email services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6186.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org","scope_keywords":["6186","authentication","delivery","http","key","license","profile","qualified","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 6186 This specification describes how SRV records can be used to locate\n email services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6186.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org 6186 authentication delivery http key license profile qualified subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6650","type":"specification","body":"IETF","designation":"RFC 6650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6650.txt","https://www.rfc-editor.org/rfc/rfc6650.pdf"],"folder":"IETF/RFC-6650","files":{"txt":{"path":"standards/IETF/RFC-6650/RFC-6650.txt","sha256":"222fbe83913b79f6eebb40219da0249d2fd54c7e5f13889897ef49eda2d179e0"}},"tags":["nested-reference","unchanged"],"summary":"RFC 5965 defines an extensible, machine-readable format intended for\n mail operators to report feedback about received email to other\n parties. This applicability statement describes common methods for\n utilizing this format for reporting both abuse and authentication\n failure events. Mailbox Providers of any size, mail-sending\n entities, and end users can use these methods as a basis to create\n procedures that best suit them. Some related optional mechanisms are\n also discussed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information a","scope_keywords":["6650","authentication","http","key","license","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6650 RFC 5965 defines an extensible, machine-readable format intended for\n mail operators to report feedback about received email to other\n parties. This applicability statement describes common methods for\n utilizing this format for reporting both abuse and authentication\n failure events. Mailbox Providers of any size, mail-sending\n entities, and end users can use these methods as a basis to create\n procedures that best suit them. Some related optional mechanisms are\n also discussed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information a 6650 authentication http key license path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6856","type":"specification","body":"IETF","designation":"RFC 6856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6856.txt","https://www.rfc-editor.org/rfc/rfc6856.pdf"],"folder":"IETF/RFC-6856","files":{"txt":{"path":"standards/IETF/RFC-6856/RFC-6856.txt","sha256":"ebb8b20303bfc7b5277dc0cd692472088a795651e25af33592605c3fcf3af49f"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Post Office Protocol version 3 (POP3)\n to support international strings encoded in UTF-8 in usernames,\n passwords, mail addresses, message headers, and protocol-level text\n strings.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6856.\n\nGellens, et al. Standards Track [Page 1]\n\f\nRFC 6856 POP3 Support for UTF-8 March 2013\n\nCopyright Notice\n\n Copyright (c) 20","scope_keywords":["6856","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null}],"search_text":"IETF RFC 6856 This specification extends the Post Office Protocol version 3 (POP3)\n to support international strings encoded in UTF-8 in usernames,\n passwords, mail addresses, message headers, and protocol-level text\n strings.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6856.\n\nGellens, et al. Standards Track [Page 1]\n\f\nRFC 6856 POP3 Support for UTF-8 March 2013\n\nCopyright Notice\n\n Copyright (c) 20 6856 authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7817","type":"specification","body":"IETF","designation":"RFC 7817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7817.txt","https://www.rfc-editor.org/rfc/rfc7817.pdf"],"folder":"IETF/RFC-7817","files":{"txt":{"path":"standards/IETF/RFC-7817/RFC-7817.txt","sha256":"658ca5af0ef7fd952308032ce1d8d9fb10c50cd7c34f40fffff33f02279e603e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Transport Layer Security (TLS) server\n identity verification procedure for SMTP Submission, IMAP, POP, and\n ManageSieve clients. It replaces Section 2.4 (Server Identity Check)\n of RFC 2595 and updates Section 4.1 (Processing After the STARTTLS\n Command) of RFC 3207, Section 11.1 (STARTTLS Security Considerations)\n of RFC 3501, and Section 2.2.1 (Server Identity Check) of RFC 5804.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provid","scope_keywords":["7817","attribute","certificate","certificates","http","key","license","path","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 7817 This document describes the Transport Layer Security (TLS) server\n identity verification procedure for SMTP Submission, IMAP, POP, and\n ManageSieve clients. It replaces Section 2.4 (Server Identity Check)\n of RFC 2595 and updates Section 4.1 (Processing After the STARTTLS\n Command) of RFC 3207, Section 11.1 (STARTTLS Security Considerations)\n of RFC 3501, and Section 2.2.1 (Server Identity Check) of RFC 5804.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provid 7817 attribute certificate certificates http key license path subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8689","type":"specification","body":"IETF","designation":"RFC 8689","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8689.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8689.txt","https://www.rfc-editor.org/rfc/rfc8689.pdf"],"folder":"IETF/RFC-8689","files":{"pdf":{"path":"standards/IETF/RFC-8689/RFC-8689.pdf","sha256":"f49c05d40c7ec4a9eecff8ecba35b8985e01edb11f5e6567e1eb01a9358fd64e"},"txt":{"path":"standards/IETF/RFC-8689/RFC-8689.txt","sha256":"391d0bc5e980932b7539dd00cb538c7fc00a37935aebdce7c74df98f44d66598"}},"tags":["nested-reference","unchanged"],"summary":"The SMTP STARTTLS option, used in negotiating transport-level\n encryption of SMTP connections, is not as useful from a security\n standpoint as it might be because of its opportunistic nature;\n message delivery is, by default, prioritized over security. This\n document describes an SMTP service extension, REQUIRETLS, and a\n message header field, TLS-Required. If the REQUIRETLS option or TLS-\n Required message header field is used when sending a message, it\n asserts a request on the part of the message sender to override the\n default negotiation of TLS, either by requiring that TLS be\n negotiated when the message is relayed or by requesting that\n recipient-side policy mechanisms such as MTA-STS and DNS-Based\n Authentication of Named Entities (DANE) be ignored when relaying a\n message for which security is unimportant.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th","scope_keywords":["8689","authentication","certificate","delivery","encryption","http","https","key","license","policies","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 8689 The SMTP STARTTLS option, used in negotiating transport-level\n encryption of SMTP connections, is not as useful from a security\n standpoint as it might be because of its opportunistic nature;\n message delivery is, by default, prioritized over security. This\n document describes an SMTP service extension, REQUIRETLS, and a\n message header field, TLS-Required. If the REQUIRETLS option or TLS-\n Required message header field is used when sending a message, it\n asserts a request on the part of the message sender to override the\n default negotiation of TLS, either by requiring that TLS be\n negotiated when the message is relayed or by requesting that\n recipient-side policy mechanisms such as MTA-STS and DNS-Based\n Authentication of Named Entities (DANE) be ignored when relaying a\n message for which security is unimportant.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th 8689 authentication certificate delivery encryption http https key license policies policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9325","type":"specification","body":"IETF","designation":"RFC 9325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9325.txt","https://www.rfc-editor.org/rfc/rfc9325.pdf"],"folder":"IETF/RFC-9325","files":{"pdf":{"path":"standards/IETF/RFC-9325/RFC-9325.pdf","sha256":"695777622697e39cfa8b4481225762917c536e99f4c41672545bd4ce69417fb2"},"txt":{"path":"standards/IETF/RFC-9325/RFC-9325.txt","sha256":"e3475381d056bde1eed65252954cce68250168454387f6799b38660806f215bc"}},"tags":["nested-reference","unchanged"],"summary":"Transport Layer Security (TLS) and Datagram Transport Layer Security\n (DTLS) are used to protect data exchanged over a wide range of\n application protocols and can also form the basis for secure\n transport protocols. Over the years, the industry has witnessed\n several serious attacks on TLS and DTLS, including attacks on the\n most commonly used cipher suites and their modes of operation. This\n document provides the latest recommendations for ensuring the\n security of deployed services that use TLS and DTLS. These\n recommendations are applicable to the majority of use cases.\n\n RFC 7525, an earlier version of the TLS recommendations, was\n published when the industry was transitioning to TLS 1.2. Years\n later, this transition is largely complete, and TLS 1.3 is widely\n available. This document updates the guidance given the new\n environment and obsoletes RFC 7525. In addition, this document","scope_keywords":["9325","algorithm","algorithms","authentication","certificate","encryption","http","https","key","license","revocation","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9325 Transport Layer Security (TLS) and Datagram Transport Layer Security\n (DTLS) are used to protect data exchanged over a wide range of\n application protocols and can also form the basis for secure\n transport protocols. Over the years, the industry has witnessed\n several serious attacks on TLS and DTLS, including attacks on the\n most commonly used cipher suites and their modes of operation. This\n document provides the latest recommendations for ensuring the\n security of deployed services that use TLS and DTLS. These\n recommendations are applicable to the majority of use cases.\n\n RFC 7525, an earlier version of the TLS recommendations, was\n published when the industry was transitioning to TLS 1.2. Years\n later, this transition is largely complete, and TLS 1.3 is widely\n available. This document updates the guidance given the new\n environment and obsoletes RFC 7525. In addition, this document 9325 algorithm algorithms authentication certificate encryption http https key license revocation subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 2084","type":"specification","body":"IETF","designation":"RFC 2084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2084.txt","https://www.rfc-editor.org/rfc/rfc2084.pdf"],"folder":"IETF/RFC-2084","files":{"txt":{"path":"standards/IETF/RFC-2084/RFC-2084.txt","sha256":"4531672726ecaa5410b4293ad9f0c61ea3d4aaf16aee12377f52d2b8a5dd7970"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements for the provision of\n security services to the HyperText Transport Protocol. These\n services include confidentiality, integrity, user authentication, and\n authentication of servers/services, including proxied or gatewayed\n services. Such services may be provided as extensions to HTTP, or as\n an encapsulating security protocol. Secondary requirements include\n ease of integration and support of multiple mechanisms for providing\n these services.\n\n1. Introduction\n\n The use of the HyperText Transport Protocol [1] to provide\n specialized or commercial services and personal or private data\n necessitates the development of secure versions that include privacy\n and authentication services. Such services may be provided as\n extensions to HTTP, or as encapsulating security protocols; for the\n purposes of this document, all such enhancements will be referred ","scope_keywords":["2084","authentication","encryption","http","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2084 This document specifies the requirements for the provision of\n security services to the HyperText Transport Protocol. These\n services include confidentiality, integrity, user authentication, and\n authentication of servers/services, including proxied or gatewayed\n services. Such services may be provided as extensions to HTTP, or as\n an encapsulating security protocol. Secondary requirements include\n ease of integration and support of multiple mechanisms for providing\n these services.\n\n1. Introduction\n\n The use of the HyperText Transport Protocol [1] to provide\n specialized or commercial services and personal or private data\n necessitates the development of secure versions that include privacy\n and authentication services. Such services may be provided as\n extensions to HTTP, or as encapsulating security protocols; for the\n purposes of this document, all such enhancements will be referred  2084 authentication encryption http policies nested-reference unchanged"},{"id":"IETF RFC 2145","type":"specification","body":"IETF","designation":"RFC 2145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2145.txt","https://www.rfc-editor.org/rfc/rfc2145.pdf"],"folder":"IETF/RFC-2145","files":{"txt":{"path":"standards/IETF/RFC-2145/RFC-2145.txt","sha256":"5c670bcd2b4dceb8641820aae4702585541a1ba224aac2703bddcba2ec3f3796"}},"tags":["nested-reference","unchanged"],"summary":"HTTP request and response messages include an HTTP protocol version\n number. Some confusion exists concerning the proper use and\n interpretation of HTTP version numbers, and concerning\n interoperability of HTTP implementations of different protocol\n versions. This document is an attempt to clarify the situation. It\n is not a modification of the intended meaning of the existing\n HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention\n of the authors of those documents, and can be considered definitive\n when there is any ambiguity in those documents concerning HTTP\n version numbers, for all versions of HTTP.\n\nMogul, et. al. Informational [Page 1]\n\f\nRFC 2145 HTTP Version Numbers May 1997","scope_keywords":["2145","algorithm","http","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2145 HTTP request and response messages include an HTTP protocol version\n number. Some confusion exists concerning the proper use and\n interpretation of HTTP version numbers, and concerning\n interoperability of HTTP implementations of different protocol\n versions. This document is an attempt to clarify the situation. It\n is not a modification of the intended meaning of the existing\n HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention\n of the authors of those documents, and can be considered definitive\n when there is any ambiguity in those documents concerning HTTP\n version numbers, for all versions of HTTP.\n\nMogul, et. al. Informational [Page 1]\n\f\nRFC 2145 HTTP Version Numbers May 1997 2145 algorithm http policy nested-reference unchanged"},{"id":"IETF RFC 2295","type":"specification","body":"IETF","designation":"RFC 2295","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2295.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2295.txt","https://www.rfc-editor.org/rfc/rfc2295.pdf"],"folder":"IETF/RFC-2295","files":{"txt":{"path":"standards/IETF/RFC-2295/RFC-2295.txt","sha256":"d1253207d78565f9a65e04fc83c417fd8c87623f5a04dfafe70ae790f6ff65fe"}},"tags":["nested-reference","unchanged"],"summary":"HTTP allows web site authors to put multiple versions of the same\n information under a single URL. Transparent content negotiation is\n an extensible negotiation mechanism, layered on top of HTTP, for\n automatically selecting the best version when the URL is accessed.\n This enables the smooth deployment of new web data formats and markup\n tags.","scope_keywords":["2295","algorithm","algorithms","attribute","http","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2296","folder":"IETF/RFC-2296","source":"IETF/RFC-2296/RFC-2296.txt","version":null},{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2295 HTTP allows web site authors to put multiple versions of the same\n information under a single URL. Transparent content negotiation is\n an extensible negotiation mechanism, layered on top of HTTP, for\n automatically selecting the best version when the URL is accessed.\n This enables the smooth deployment of new web data formats and markup\n tags. 2295 algorithm algorithms attribute http presentation nested-reference unchanged"},{"id":"IETF RFC 2774","type":"specification","body":"IETF","designation":"RFC 2774","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2774.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2774.txt","https://www.rfc-editor.org/rfc/rfc2774.pdf"],"folder":"IETF/RFC-2774","files":{"txt":{"path":"standards/IETF/RFC-2774/RFC-2774.txt","sha256":"1fa12e89fe853cb0949591940c1c11ef0a00c2a8bf5a138e64da181a55306b3f"}},"tags":["nested-reference","unchanged"],"summary":"A wide range of applications have proposed various extensions of the\n HTTP protocol. Current efforts span an enormous range, including\n distributed authoring, collaboration, printing, and remote procedure\n call mechanisms. These HTTP extensions are not coordinated, since\n there has been no standard framework for defining extensions and\n thus, separation of concerns. This document describes a generic\n extension mechanism for HTTP, which is designed to address the\n tension between private agreement and public specification and to\n accommodate extension of applications using HTTP clients, servers,\n and proxies. The proposal associates each extension with a globally\n unique identifier, and uses HTTP header fields to carry the extension\n identifier and related information between the parties involved in\n the extended communication.","scope_keywords":["2774","http","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2774 A wide range of applications have proposed various extensions of the\n HTTP protocol. Current efforts span an enormous range, including\n distributed authoring, collaboration, printing, and remote procedure\n call mechanisms. These HTTP extensions are not coordinated, since\n there has been no standard framework for defining extensions and\n thus, separation of concerns. This document describes a generic\n extension mechanism for HTTP, which is designed to address the\n tension between private agreement and public specification and to\n accommodate extension of applications using HTTP clients, servers,\n and proxies. The proposal associates each extension with a globally\n unique identifier, and uses HTTP header fields to carry the extension\n identifier and related information between the parties involved in\n the extended communication. 2774 http key presentation nested-reference unchanged"},{"id":"IETF RFC 3760","type":"specification","body":"IETF","designation":"RFC 3760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3760.txt","https://www.rfc-editor.org/rfc/rfc3760.pdf"],"folder":"IETF/RFC-3760","files":{"txt":{"path":"standards/IETF/RFC-3760/RFC-3760.txt","sha256":"a88f856c1aad5e5c3b5b9b7c0f4d4988153350b28c56551a028a876eecc58fc0"}},"tags":["nested-reference","unchanged"],"summary":"As the number, and more particularly the number of different types,\n of devices connecting to the Internet increases, credential mobility\n becomes an issue for IETF standardization. This document responds to\n the requirements on protocols for secure exchange of credentials\n listed in RFC 3157, by presenting an abstract protocol framework.","scope_keywords":["3760","attribute","authentication","certificate","certificates","credential","credentials","encryption","hash","key","keys","management","presentation","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null}],"search_text":"IETF RFC 3760 As the number, and more particularly the number of different types,\n of devices connecting to the Internet increases, credential mobility\n becomes an issue for IETF standardization. This document responds to\n the requirements on protocols for secure exchange of credentials\n listed in RFC 3157, by presenting an abstract protocol framework. 3760 attribute authentication certificate certificates credential credentials encryption hash key keys management presentation signature tls nested-reference unchanged"},{"id":"IETF RFC 6202","type":"specification","body":"IETF","designation":"RFC 6202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6202.txt","https://www.rfc-editor.org/rfc/rfc6202.pdf"],"folder":"IETF/RFC-6202","files":{"txt":{"path":"standards/IETF/RFC-6202/RFC-6202.txt","sha256":"281ae32d4746253837fd7baf3b5e930ca99e347efccd451b18c8c56b38d5b405"}},"tags":["nested-reference","unchanged"],"summary":"On today's Internet, the Hypertext Transfer Protocol (HTTP) is often\n used (some would say abused) to enable asynchronous, \"server-\n initiated\" communication from a server to a client as well as\n communication from a client to a server. This document describes\n known issues and best practices related to such \"bidirectional HTTP\"\n applications, focusing on the two most common mechanisms: HTTP long\n polling and HTTP streaming.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standar","scope_keywords":["6202","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null}],"search_text":"IETF RFC 6202 On today's Internet, the Hypertext Transfer Protocol (HTTP) is often\n used (some would say abused) to enable asynchronous, \"server-\n initiated\" communication from a server to a client as well as\n communication from a client to a server. This document describes\n known issues and best practices related to such \"bidirectional HTTP\"\n applications, focusing on the two most common mechanisms: HTTP long\n polling and HTTP streaming.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standar 6202 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7231","type":"specification","body":"IETF","designation":"RFC 7231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7231.txt","https://www.rfc-editor.org/rfc/rfc7231.pdf"],"folder":"IETF/RFC-7231","files":{"txt":{"path":"standards/IETF/RFC-7231/RFC-7231.txt","sha256":"a83d026937f6f7929a0e53f8a9bfec4104285f0f89d6dbabd3927c4208a715b2"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines the semantics of HTTP/1.1 messages,\n as expressed by request methods, request header fields, response\n status codes, and response header fields, along with the payload of\n messages (metadata and body content) and mechanisms for content\n negotiation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to ","scope_keywords":["7231","authentication","credential","credentials","http","identification","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8297","folder":"IETF/RFC-8297","source":"IETF/RFC-8297/RFC-8297.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 7231 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines the semantics of HTTP/1.1 messages,\n as expressed by request methods, request header fields, response\n status codes, and response header fields, along with the payload of\n messages (metadata and body content) and mechanisms for content\n negotiation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to  7231 authentication credential credentials http identification license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7937","type":"specification","body":"IETF","designation":"RFC 7937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7937.txt","https://www.rfc-editor.org/rfc/rfc7937.pdf"],"folder":"IETF/RFC-7937","files":{"txt":{"path":"standards/IETF/RFC-7937/RFC-7937.txt","sha256":"3a15846abd6811af20e3850bc47ca3d166d3b45071a67c27c6be82186cc00b56"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies the Logging interface between a downstream\n Content Distribution Network (dCDN) and an upstream CDN (uCDN) that\n are interconnected as per the CDN Interconnection (CDNI) framework.\n First, it describes a reference model for CDNI logging. Then, it\n specifies the CDNI Logging File format and the actual protocol for\n exchange of CDNI Logging Files.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w","scope_keywords":["7937","authentication","authorization","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 7937 This memo specifies the Logging interface between a downstream\n Content Distribution Network (dCDN) and an upstream CDN (uCDN) that\n are interconnected as per the CDN Interconnection (CDNI) framework.\n First, it describes a reference model for CDNI logging. Then, it\n specifies the CDNI Logging File format and the actual protocol for\n exchange of CDNI Logging Files.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://w 7937 authentication authorization delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8404","type":"specification","body":"IETF","designation":"RFC 8404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8404.txt","https://www.rfc-editor.org/rfc/rfc8404.pdf"],"folder":"IETF/RFC-8404","files":{"txt":{"path":"standards/IETF/RFC-8404/RFC-8404.txt","sha256":"0e8df89c19f0449a43342dbcb2dc555fcbfcc76a02ab4c00536d0c6cd5e4e00b"}},"tags":["nested-reference","unchanged"],"summary":"Pervasive monitoring attacks on the privacy of Internet users are of\n serious concern to both user and operator communities. RFC 7258\n discusses the critical need to protect users' privacy when developing\n IETF specifications and also recognizes that making networks\n unmanageable to mitigate pervasive monitoring is not an acceptable\n outcome: an appropriate balance is needed. This document discusses\n current security and network operations as well as management\n practices that may be impacted by the shift to increased use of\n encryption to help guide protocol development in support of\n manageable and secure networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering ","scope_keywords":["8404","encryption","http","https","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null}],"search_text":"IETF RFC 8404 Pervasive monitoring attacks on the privacy of Internet users are of\n serious concern to both user and operator communities. RFC 7258\n discusses the critical need to protect users' privacy when developing\n IETF specifications and also recognizes that making networks\n unmanageable to mitigate pervasive monitoring is not an acceptable\n outcome: an appropriate balance is needed. This document discusses\n current security and network operations as well as management\n practices that may be impacted by the shift to increased use of\n encryption to help guide protocol development in support of\n manageable and secure networks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering  8404 encryption http https license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9112","type":"specification","body":"IETF","designation":"RFC 9112","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9112.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9112.txt","https://www.rfc-editor.org/rfc/rfc9112.pdf"],"folder":"IETF/RFC-9112","files":{"pdf":{"path":"standards/IETF/RFC-9112/RFC-9112.pdf","sha256":"b260bba790c2da55a7e0795f356fcd9b70743686c55250f0ef1cc993c4d1abac"},"txt":{"path":"standards/IETF/RFC-9112/RFC-9112.txt","sha256":"e4f426bac6206b67fdf9e0da826154f70588db2133a0a86b15cde4ff725d8937"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document specifies the HTTP/1.1 message syntax,\n message parsing, connection management, and related security\n concerns.\n\n This document obsoletes portions of RFC 7230.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9112.\n\nCopyright Not","scope_keywords":["9112","crl","http","https","key","license","management","path","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 9112 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document specifies the HTTP/1.1 message syntax,\n message parsing, connection management, and related security\n concerns.\n\n This document obsoletes portions of RFC 7230.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9112.\n\nCopyright Not 9112 crl http https key license management path risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 4218","type":"specification","body":"IETF","designation":"RFC 4218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4218.txt","https://www.rfc-editor.org/rfc/rfc4218.pdf"],"folder":"IETF/RFC-4218","files":{"txt":{"path":"standards/IETF/RFC-4218/RFC-4218.txt","sha256":"9889bfc9a99448112e4392de58b4b8e2ba172ca08a3d38dff98ae9194820c756"}},"tags":["nested-reference","unchanged"],"summary":"This document lists security threats related to IPv6 multihoming.\n Multihoming can introduce new opportunities to redirect packets to\n different, unintended IP addresses.\n\n The intent is to look at how IPv6 multihoming solutions might make\n the Internet less secure; we examine threats that are inherent to all\n IPv6 multihoming solutions rather than study any specific proposed\n solution. The threats in this document build upon the threats\n discovered and discussed as part of the Mobile IPv6 work.","scope_keywords":["4218","authentication","authorization","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4219","folder":"IETF/RFC-4219","source":"IETF/RFC-4219/RFC-4219.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 4218 This document lists security threats related to IPv6 multihoming.\n Multihoming can introduce new opportunities to redirect packets to\n different, unintended IP addresses.\n\n The intent is to look at how IPv6 multihoming solutions might make\n the Internet less secure; we examine threats that are inherent to all\n IPv6 multihoming solutions rather than study any specific proposed\n solution. The threats in this document build upon the threats\n discovered and discussed as part of the Mobile IPv6 work. 4218 authentication authorization key path tls nested-reference unchanged"},{"id":"IETF RFC 2627","type":"specification","body":"IETF","designation":"RFC 2627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2627.txt","https://www.rfc-editor.org/rfc/rfc2627.pdf"],"folder":"IETF/RFC-2627","files":{"txt":{"path":"standards/IETF/RFC-2627/RFC-2627.txt","sha256":"145ad1486a092890ada16a74bc127c2d349d2283fea15ed6194aa9fdcd81a90f"}},"tags":["nested-reference","unchanged"],"summary":"This report contains a discussion of the difficult problem of key\n management for multicast communication sessions. It focuses on two\n main areas of concern with respect to key management, which are,\n initializing the multicast group with a common net key and rekeying\n the multicast group. A rekey may be necessary upon the compromise of\n a user or for other reasons (e.g., periodic rekey). In particular,\n this report identifies a technique which allows for secure compromise\n recovery, while also being robust against collusion of excluded\n users. This is one important feature of multicast key management\n which has not been addressed in detail by most other multicast key\n management proposals [1,2,4]. The benefits of this proposed\n technique are that it minimizes the number of transmissions required\n to rekey the multicast group and it imposes minimal storage\n requirements on the multicast ","scope_keywords":["2627","attribute","attributes","certificate","certificates","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2887","folder":"IETF/RFC-2887","source":"IETF/RFC-2887/RFC-2887.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null}],"search_text":"IETF RFC 2627 This report contains a discussion of the difficult problem of key\n management for multicast communication sessions. It focuses on two\n main areas of concern with respect to key management, which are,\n initializing the multicast group with a common net key and rekeying\n the multicast group. A rekey may be necessary upon the compromise of\n a user or for other reasons (e.g., periodic rekey). In particular,\n this report identifies a technique which allows for secure compromise\n recovery, while also being robust against collusion of excluded\n users. This is one important feature of multicast key management\n which has not been addressed in detail by most other multicast key\n management proposals [1,2,4]. The benefits of this proposed\n technique are that it minimizes the number of transmissions required\n to rekey the multicast group and it imposes minimal storage\n requirements on the multicast  2627 attribute attributes certificate certificates key keys management nested-reference unchanged"},{"id":"IETF RFC 1950","type":"specification","body":"IETF","designation":"RFC 1950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1950.txt","https://www.rfc-editor.org/rfc/rfc1950.pdf"],"folder":"IETF/RFC-1950","files":{"pdf":{"path":"standards/IETF/RFC-1950/RFC-1950.pdf","sha256":"9e16bebb244f922ed23b235f15d52ed0b701c83c34a1cd8db4c8252c27bf0ffa"},"txt":{"path":"standards/IETF/RFC-1950/RFC-1950.txt","sha256":"8f0475a5c984657bf26277f73df9456c9b97f175084f0c1748f1eb1f0b9b10b9"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a lossless compressed data format. The\n data can be produced or consumed, even for an arbitrarily long\n sequentially presented input data stream, using only an a priori\n bounded amount of intermediate storage. The format presently uses\n the DEFLATE compression method but can be easily extended to use\n other compression methods. It can be implemented readily in a manner\n not covered by patents. This specification also defines the ADLER-32\n checksum (an extension and improvement of the Fletcher checksum),\n used for detection of data corruption, and provides an algorithm for\n computing it.\n\nDeutsch & Gailly Informational [Page 1]\n\f\nRFC 1950 ZLIB Compressed Data Format Specification May 1996","scope_keywords":["1950","algorithm","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3274","folder":"IETF/RFC-3274","source":"IETF/RFC-3274/RFC-3274.txt","version":null},{"body":"IETF","designation":"RFC 3385","folder":"IETF/RFC-3385","source":"IETF/RFC-3385/RFC-3385.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 6713","folder":"IETF/RFC-6713","source":"IETF/RFC-6713/RFC-6713.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 1950 This specification defines a lossless compressed data format. The\n data can be produced or consumed, even for an arbitrarily long\n sequentially presented input data stream, using only an a priori\n bounded amount of intermediate storage. The format presently uses\n the DEFLATE compression method but can be easily extended to use\n other compression methods. It can be implemented readily in a manner\n not covered by patents. This specification also defines the ADLER-32\n checksum (an extension and improvement of the Fletcher checksum),\n used for detection of data corruption, and provides an algorithm for\n computing it.\n\nDeutsch & Gailly Informational [Page 1]\n\f\nRFC 1950 ZLIB Compressed Data Format Specification May 1996 1950 algorithm presentation nested-reference unchanged"},{"id":"IETF RFC 2974","type":"specification","body":"IETF","designation":"RFC 2974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2974.txt","https://www.rfc-editor.org/rfc/rfc2974.pdf"],"folder":"IETF/RFC-2974","files":{"txt":{"path":"standards/IETF/RFC-2974/RFC-2974.txt","sha256":"68bd8c2cbfe2840652f3e52e10a1991cce2da980cb822df7c33056cac45941a9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes version 2 of the multicast session directory\n announcement protocol, Session Announcement Protocol (SAP), and the\n related issues affecting security and scalability that should be\n taken into account by implementors.\n\n1 Introduction\n\n In order to assist the advertisement of multicast multimedia\n conferences and other multicast sessions, and to communicate the\n relevant session setup information to prospective participants, a\n distributed session directory may be used. An instance of such a\n session directory periodically multicasts packets containing a\n description of the session, and these advertisements are received by\n other session directories such that potential remote participants can\n use the session description to start the tools required to\n participate in the session.\n\n This memo describes the issues involved in the multicast announcement\n of session des","scope_keywords":["2974","authentication","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3180","folder":"IETF/RFC-3180","source":"IETF/RFC-3180/RFC-3180.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 2974 This document describes version 2 of the multicast session directory\n announcement protocol, Session Announcement Protocol (SAP), and the\n related issues affecting security and scalability that should be\n taken into account by implementors.\n\n1 Introduction\n\n In order to assist the advertisement of multicast multimedia\n conferences and other multicast sessions, and to communicate the\n relevant session setup information to prospective participants, a\n distributed session directory may be used. An instance of such a\n session directory periodically multicasts packets containing a\n description of the session, and these advertisements are received by\n other session directories such that potential remote participants can\n use the session description to start the tools required to\n participate in the session.\n\n This memo describes the issues involved in the multicast announcement\n of session des 2974 authentication hash key nested-reference unchanged"},{"id":"IETF RFC 3274","type":"specification","body":"IETF","designation":"RFC 3274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3274.txt","https://www.rfc-editor.org/rfc/rfc3274.pdf"],"folder":"IETF/RFC-3274","files":{"txt":{"path":"standards/IETF/RFC-3274/RFC-3274.txt","sha256":"acabfbe001e50fd8dd697193137865ef99a6d394228a327cbd34756efd476fbe"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a format for using compressed data as a\n Cryptographic Message Syntax (CMS) content type. Compressing data\n before transmission provides a number of advantages, including the\n elimination of data redundancy which could help an attacker, speeding\n up processing by reducing the amount of data to be processed by later\n steps (such as signing or encryption), and reducing overall message\n size. Although there have been proposals for adding compression at\n other levels (for example at the MIME or SSL level), these don't\n address the problem of compression of CMS content unless the\n compression is supplied by an external means (for example by\n intermixing MIME and CMS).\n\n1. Introduction\n\n This document describes a compressed data content type for CMS. This\n is implemented as a new ContentInfo type and is an extension to the\n types currently defined in CMS [RFC2630]. CMS im","scope_keywords":["3274","algorithm","algorithms","attribute","encryption","key","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 4073","folder":"IETF/RFC-4073","source":"IETF/RFC-4073/RFC-4073.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3274 This document defines a format for using compressed data as a\n Cryptographic Message Syntax (CMS) content type. Compressing data\n before transmission provides a number of advantages, including the\n elimination of data redundancy which could help an attacker, speeding\n up processing by reducing the amount of data to be processed by later\n steps (such as signing or encryption), and reducing overall message\n size. Although there have been proposals for adding compression at\n other levels (for example at the MIME or SSL level), these don't\n address the problem of compression of CMS content unless the\n compression is supplied by an external means (for example by\n intermixing MIME and CMS).\n\n1. Introduction\n\n This document describes a compressed data content type for CMS. This\n is implemented as a new ContentInfo type and is an extension to the\n types currently defined in CMS [RFC2630]. CMS im 3274 algorithm algorithms attribute encryption key profile trust nested-reference unchanged"},{"id":"IETF RFC 5024","type":"specification","body":"IETF","designation":"RFC 5024","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5024.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5024.txt","https://www.rfc-editor.org/rfc/rfc5024.pdf"],"folder":"IETF/RFC-5024","files":{"txt":{"path":"standards/IETF/RFC-5024/RFC-5024.txt","sha256":"6411a2761da53deb63ba027caaf4e3bb15e883fe418a5f7a7c9f04aa5d5c4fa2"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates the ODETTE File Transfer Protocol, an established\n file transfer protocol facilitating electronic data interchange of\n business data between trading partners, to version 2.\n\n The protocol now supports secure and authenticated communication over\n the Internet using Transport Layer Security, provides file\n encryption, signing, and compression using Cryptographic Message\n Syntax, and provides signed receipts for the acknowledgement of\n received files.\n\n The protocol supports both direct peer-to-peer communication and\n indirect communication via a Value Added Network and may be used with\n TCP/IP, X.25, and ISDN-based networks.\n\nFriend Informational [Page 1]\n\f\nRFC 5024 ODETTE FTP 2 November 2007","scope_keywords":["5024","algorithm","algorithms","certificate","encryption","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5024 This memo updates the ODETTE File Transfer Protocol, an established\n file transfer protocol facilitating electronic data interchange of\n business data between trading partners, to version 2.\n\n The protocol now supports secure and authenticated communication over\n the Internet using Transport Layer Security, provides file\n encryption, signing, and compression using Cryptographic Message\n Syntax, and provides signed receipts for the acknowledgement of\n received files.\n\n The protocol supports both direct peer-to-peer communication and\n indirect communication via a Value Added Network and may be used with\n TCP/IP, X.25, and ISDN-based networks.\n\nFriend Informational [Page 1]\n\f\nRFC 5024 ODETTE FTP 2 November 2007 5024 algorithm algorithms certificate encryption identification profile nested-reference unchanged"},{"id":"IETF RFC 6713","type":"specification","body":"IETF","designation":"RFC 6713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6713.txt","https://www.rfc-editor.org/rfc/rfc6713.pdf"],"folder":"IETF/RFC-6713","files":{"txt":{"path":"standards/IETF/RFC-6713/RFC-6713.txt","sha256":"f7e416c96c0ab9ce6004c75a21fe7f8c006444ddcf4b8f464be8e01fdddb3739"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the 'application/gzip' and 'application/zlib'\n media types for compressed data using the gzip and zlib compression\n formats.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6713.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n doc","scope_keywords":["6713","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null}],"search_text":"IETF RFC 6713 This document defines the 'application/gzip' and 'application/zlib'\n media types for compressed data using the gzip and zlib compression\n formats.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6713.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n doc 6713 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8879","type":"specification","body":"IETF","designation":"RFC 8879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8879.txt","https://www.rfc-editor.org/rfc/rfc8879.pdf"],"folder":"IETF/RFC-8879","files":{"pdf":{"path":"standards/IETF/RFC-8879/RFC-8879.pdf","sha256":"db5909e4d5d79bc7c86ae5fe1f8604231e669b721d70b44368252c39fb22f611"},"txt":{"path":"standards/IETF/RFC-8879/RFC-8879.txt","sha256":"8e30b047e20762ea3de13fb3487d93ee416712b62cab2993900368438c8d20db"}},"tags":["nested-reference","unchanged"],"summary":"In TLS handshakes, certificate chains often take up the majority of\n the bytes transmitted.\n\n This document describes how certificate chains can be compressed to\n reduce the amount of data transmitted and avoid some round trips.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8879.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All","scope_keywords":["8879","algorithm","algorithms","certificate","certificates","http","https","key","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 8879 In TLS handshakes, certificate chains often take up the majority of\n the bytes transmitted.\n\n This document describes how certificate chains can be compressed to\n reduce the amount of data transmitted and avoid some round trips.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8879.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All 8879 algorithm algorithms certificate certificates http https key license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 1951","type":"specification","body":"IETF","designation":"RFC 1951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1951.txt","https://www.rfc-editor.org/rfc/rfc1951.pdf"],"folder":"IETF/RFC-1951","files":{"pdf":{"path":"standards/IETF/RFC-1951/RFC-1951.pdf","sha256":"44ebfc2a0af072f08bc96d68f5f9193ec41332a9e01a46f33b1834d85caced6e"},"txt":{"path":"standards/IETF/RFC-1951/RFC-1951.txt","sha256":"5ebf4b5b7fe1c3a0c0ab9aa3ac8c0f3853a7dc484905e76e03b0b0f301350009"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a lossless compressed data format that\n compresses data using a combination of the LZ77 algorithm and Huffman\n coding, with efficiency comparable to the best currently available\n general-purpose compression methods. The data can be produced or\n consumed, even for an arbitrarily long sequentially presented input\n data stream, using only an a priori bounded amount of intermediate\n storage. The format can be implemented readily in a manner not\n covered by patents.\n\nDeutsch Informational [Page 1]\n\f\nRFC 1951 DEFLATE Compressed Data Format Specification May 1996","scope_keywords":["1951","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2394","folder":"IETF/RFC-2394","source":"IETF/RFC-2394/RFC-2394.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3274","folder":"IETF/RFC-3274","source":"IETF/RFC-3274/RFC-3274.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 6713","folder":"IETF/RFC-6713","source":"IETF/RFC-6713/RFC-6713.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7932","folder":"IETF/RFC-7932","source":"IETF/RFC-7932/RFC-7932.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null}],"search_text":"IETF RFC 1951 This specification defines a lossless compressed data format that\n compresses data using a combination of the LZ77 algorithm and Huffman\n coding, with efficiency comparable to the best currently available\n general-purpose compression methods. The data can be produced or\n consumed, even for an arbitrarily long sequentially presented input\n data stream, using only an a priori bounded amount of intermediate\n storage. The format can be implemented readily in a manner not\n covered by patents.\n\nDeutsch Informational [Page 1]\n\f\nRFC 1951 DEFLATE Compressed Data Format Specification May 1996 1951 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 2394","type":"specification","body":"IETF","designation":"RFC 2394","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2394.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2394.txt","https://www.rfc-editor.org/rfc/rfc2394.pdf"],"folder":"IETF/RFC-2394","files":{"txt":{"path":"standards/IETF/RFC-2394/RFC-2394.txt","sha256":"77f99641f96c1ceaf2fc84040c806954102eb398ea7021a944d1855404588448"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a compression method based on the DEFLATE\n compression algorithm. This document defines the application of the\n DEFLATE algorithm to the IP Payload Compression Protocol.","scope_keywords":["2394","algorithm","algorithms","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2394 This document describes a compression method based on the DEFLATE\n compression algorithm. This document defines the application of the\n DEFLATE algorithm to the IP Payload Compression Protocol. 2394 algorithm algorithms key subject nested-reference unchanged"},{"id":"IETF RFC 3749","type":"specification","body":"IETF","designation":"RFC 3749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3749.txt","https://www.rfc-editor.org/rfc/rfc3749.pdf"],"folder":"IETF/RFC-3749","files":{"txt":{"path":"standards/IETF/RFC-3749/RFC-3749.txt","sha256":"a164fd6b749dd7636ce19c2a3c0d3fd2351fbd2b3731e250f42eec1bd4f185b4"}},"tags":["nested-reference","unchanged"],"summary":"The Transport Layer Security (TLS) protocol (RFC 2246) includes\n features to negotiate selection of a lossless data compression method\n as part of the TLS Handshake Protocol and to then apply the algorithm\n associated with the selected method as part of the TLS Record\n Protocol. TLS defines one standard compression method which\n specifies that data exchanged via the record protocol will not be\n compressed. This document describes an additional compression method\n associated with a lossless data compression algorithm for use with\n TLS, and it describes a method for the specification of additional\n TLS compression methods.","scope_keywords":["3749","algorithm","algorithms","delivery","key","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null}],"search_text":"IETF RFC 3749 The Transport Layer Security (TLS) protocol (RFC 2246) includes\n features to negotiate selection of a lossless data compression method\n as part of the TLS Handshake Protocol and to then apply the algorithm\n associated with the selected method as part of the TLS Record\n Protocol. TLS defines one standard compression method which\n specifies that data exchanged via the record protocol will not be\n compressed. This document describes an additional compression method\n associated with a lossless data compression algorithm for use with\n TLS, and it describes a method for the specification of additional\n TLS compression methods. 3749 algorithm algorithms delivery key presentation tls nested-reference unchanged"},{"id":"IETF RFC 4978","type":"specification","body":"IETF","designation":"RFC 4978","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4978.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4978.txt","https://www.rfc-editor.org/rfc/rfc4978.pdf"],"folder":"IETF/RFC-4978","files":{"txt":{"path":"standards/IETF/RFC-4978/RFC-4978.txt","sha256":"38bb16ae700e114619a2c0ecdb26a285a7ae27141e65aa515920ed72c1519c67"}},"tags":["nested-reference","unchanged"],"summary":"The COMPRESS extension allows an IMAP connection to be effectively\n and efficiently compressed.","scope_keywords":["4978","algorithm","algorithms","authentication","crl","encryption","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null}],"search_text":"IETF RFC 4978 The COMPRESS extension allows an IMAP connection to be effectively\n and efficiently compressed. 4978 algorithm algorithms authentication crl encryption key tls nested-reference unchanged"},{"id":"IETF RFC 7541","type":"specification","body":"IETF","designation":"RFC 7541","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7541.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7541.txt","https://www.rfc-editor.org/rfc/rfc7541.pdf"],"folder":"IETF/RFC-7541","files":{"txt":{"path":"standards/IETF/RFC-7541/RFC-7541.txt","sha256":"2239d7f8fb839b69ae2e928e685559b11376888269f131512197a0e3bacf7f7a"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines HPACK, a compression format for\n efficiently representing HTTP header fields, to be used in HTTP/2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7541.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating ","scope_keywords":["7541","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 7541 This specification defines HPACK, a compression format for\n efficiently representing HTTP header fields, to be used in HTTP/2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7541.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating  7541 http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7932","type":"specification","body":"IETF","designation":"RFC 7932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7932.txt","https://www.rfc-editor.org/rfc/rfc7932.pdf"],"folder":"IETF/RFC-7932","files":{"txt":{"path":"standards/IETF/RFC-7932/RFC-7932.txt","sha256":"394abd1879e016f4eac89512c2acaf92f7b2d67feb8ab58b6b118c213be07146"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a lossless compressed data format that\n compresses data using a combination of the LZ77 algorithm and Huffman\n coding, with efficiency comparable to the best currently available\n general-purpose compression methods.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7932.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identifie","scope_keywords":["7932","algorithm","algorithms","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null}],"search_text":"IETF RFC 7932 This specification defines a lossless compressed data format that\n compresses data using a combination of the LZ77 algorithm and Huffman\n coding, with efficiency comparable to the best currently available\n general-purpose compression methods.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7932.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identifie 7932 algorithm algorithms http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8054","type":"specification","body":"IETF","designation":"RFC 8054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8054.txt","https://www.rfc-editor.org/rfc/rfc8054.pdf"],"folder":"IETF/RFC-8054","files":{"txt":{"path":"standards/IETF/RFC-8054/RFC-8054.txt","sha256":"63f58e6675debaaaa02c7c77ba2907104903ccb9fc9461497fd36ece4a9bdbdb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Network News Transport\n Protocol (NNTP) that allows a connection to be effectively and\n efficiently compressed between an NNTP client and server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8054.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje","scope_keywords":["8054","algorithm","algorithms","authentication","credential","credentials","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 8054 This document defines an extension to the Network News Transport\n Protocol (NNTP) that allows a connection to be effectively and\n efficiently compressed between an NNTP client and server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8054.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje 8054 algorithm algorithms authentication credential credentials encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9204","type":"specification","body":"IETF","designation":"RFC 9204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9204.txt","https://www.rfc-editor.org/rfc/rfc9204.pdf"],"folder":"IETF/RFC-9204","files":{"pdf":{"path":"standards/IETF/RFC-9204/RFC-9204.pdf","sha256":"86a6816f543bc882c3821a20fd8fde28b329bf0771f52579e99bc5ded063283d"},"txt":{"path":"standards/IETF/RFC-9204/RFC-9204.txt","sha256":"926b4d7e9772b5c316fe87a1e160f5ced118101459ede5b13d11bf9a9273c931"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines QPACK: a compression format for\n efficiently representing HTTP fields that is to be used in HTTP/3.\n This is a variation of HPACK compression that seeks to reduce head-\n of-line blocking.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9204.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserv","scope_keywords":["9204","algorithm","delivery","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 9204 This specification defines QPACK: a compression format for\n efficiently representing HTTP fields that is to be used in HTTP/3.\n This is a variation of HPACK compression that seeks to reduce head-\n of-line blocking.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9204.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserv 9204 algorithm delivery http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 1952","type":"specification","body":"IETF","designation":"RFC 1952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1952.txt","https://www.rfc-editor.org/rfc/rfc1952.pdf"],"folder":"IETF/RFC-1952","files":{"pdf":{"path":"standards/IETF/RFC-1952/RFC-1952.pdf","sha256":"bf8f782e9428e136b71de44eb86f2a1968ba7834373bfd7eb4aca3d7e4ce0cb3"},"txt":{"path":"standards/IETF/RFC-1952/RFC-1952.txt","sha256":"164ef0897b4cbec63abf1b57f069f3599bd0fb7c72c2a4dee21bd7e03ec9af67"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a lossless compressed data format that is\n compatible with the widely used GZIP utility. The format includes a\n cyclic redundancy check value for detecting data corruption. The\n format presently uses the DEFLATE method of compression but can be\n easily extended to use other compression methods. The format can be\n implemented readily in a manner not covered by patents.\n\nDeutsch Informational [Page 1]\n\f\nRFC 1952 GZIP File Format Specification May 1996","scope_keywords":["1952","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 6713","folder":"IETF/RFC-6713","source":"IETF/RFC-6713/RFC-6713.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8478","folder":"IETF/RFC-8478","source":"IETF/RFC-8478/RFC-8478.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null}],"search_text":"IETF RFC 1952 This specification defines a lossless compressed data format that is\n compatible with the widely used GZIP utility. The format includes a\n cyclic redundancy check value for detecting data corruption. The\n format presently uses the DEFLATE method of compression but can be\n easily extended to use other compression methods. The format can be\n implemented readily in a manner not covered by patents.\n\nDeutsch Informational [Page 1]\n\f\nRFC 1952 GZIP File Format Specification May 1996 1952 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 8460","type":"specification","body":"IETF","designation":"RFC 8460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8460.txt","https://www.rfc-editor.org/rfc/rfc8460.pdf"],"folder":"IETF/RFC-8460","files":{"txt":{"path":"standards/IETF/RFC-8460/RFC-8460.txt","sha256":"ee9bd333ca729ebeff46432d26e52e11d87f57d035028f0cf349fa1559fbaae3"}},"tags":["nested-reference","unchanged"],"summary":"A number of protocols exist for establishing encrypted channels\n between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS-\n Based Authentication of Named Entities (DANE) TLSA, and MTA Strict\n Transport Security (MTA-STS). These protocols can fail due to\n misconfiguration or active attack, leading to undelivered messages or\n delivery over unencrypted or unauthenticated channels. This document\n describes a reporting mechanism and format by which sending systems\n can share statistics and specific information about potential\n failures with recipient domains. Recipient domains can then use this\n information to both detect potential attacks and diagnose\n unintentional misconfigurations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It h","scope_keywords":["8460","authentication","delivery","encryption","http","https","license","policy","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null}],"search_text":"IETF RFC 8460 A number of protocols exist for establishing encrypted channels\n between SMTP Mail Transfer Agents (MTAs), including STARTTLS, DNS-\n Based Authentication of Named Entities (DANE) TLSA, and MTA Strict\n Transport Security (MTA-STS). These protocols can fail due to\n misconfiguration or active attack, leading to undelivered messages or\n delivery over unencrypted or unauthenticated channels. This document\n describes a reporting mechanism and format by which sending systems\n can share statistics and specific information about potential\n failures with recipient domains. Recipient domains can then use this\n information to both detect potential attacks and diagnose\n unintentional misconfigurations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It h 8460 authentication delivery encryption http https license policy subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8478","type":"specification","body":"IETF","designation":"RFC 8478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8478.txt","https://www.rfc-editor.org/rfc/rfc8478.pdf"],"folder":"IETF/RFC-8478","files":{"txt":{"path":"standards/IETF/RFC-8478/RFC-8478.txt","sha256":"cdb45bf3e239e47c01345e17f3796a6f8e157a280a8aa2609926a48cf69930b0"}},"tags":["nested-reference","unchanged"],"summary":"Zstandard, or \"zstd\" (pronounced \"zee standard\"), is a data\n compression mechanism. This document describes the mechanism and\n registers a media type and content encoding to be used when\n transporting zstd-compressed content via Multipurpose Internet Mail\n Extensions (MIME).\n\n Despite use of the word \"standard\" as part of its name, readers are\n advised that this document is not an Internet Standards Track\n specification; it is being published for informational purposes only.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG","scope_keywords":["8478","algorithm","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null}],"search_text":"IETF RFC 8478 Zstandard, or \"zstd\" (pronounced \"zee standard\"), is a data\n compression mechanism. This document describes the mechanism and\n registers a media type and content encoding to be used when\n transporting zstd-compressed content via Multipurpose Internet Mail\n Extensions (MIME).\n\n Despite use of the word \"standard\" as part of its name, readers are\n advised that this document is not an Internet Standards Track\n specification; it is being published for informational purposes only.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG 8478 algorithm http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 4984","type":"specification","body":"IETF","designation":"RFC 4984","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4984.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4984.txt","https://www.rfc-editor.org/rfc/rfc4984.pdf"],"folder":"IETF/RFC-4984","files":{"txt":{"path":"standards/IETF/RFC-4984/RFC-4984.txt","sha256":"54e6dfe119eb5b2ad12926aa69b5dc2d2377d20c483f32b71e80e59b66d58df0"}},"tags":["nested-reference","unchanged"],"summary":"This document reports the outcome of the Routing and Addressing\n Workshop that was held by the Internet Architecture Board (IAB) on\n October 18-19, 2006, in Amsterdam, Netherlands. The primary goal of\n the workshop was to develop a shared understanding of the problems\n that the large backbone operators are facing regarding the\n scalability of today's Internet routing system. The key workshop\n findings include an analysis of the major factors that are driving\n routing table growth, constraints in router technology, and the\n limitations of today's Internet addressing architecture. It is hoped\n that these findings will serve as input to the IETF community and\n help identify next steps towards effective solutions.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and not of the ","scope_keywords":["4984","driving","key","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null}],"search_text":"IETF RFC 4984 This document reports the outcome of the Routing and Addressing\n Workshop that was held by the Internet Architecture Board (IAB) on\n October 18-19, 2006, in Amsterdam, Netherlands. The primary goal of\n the workshop was to develop a shared understanding of the problems\n that the large backbone operators are facing regarding the\n scalability of today's Internet routing system. The key workshop\n findings include an analysis of the major factors that are driving\n routing table growth, constraints in router technology, and the\n limitations of today's Internet addressing architecture. It is hoped\n that these findings will serve as input to the IETF community and\n help identify next steps towards effective solutions.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and not of the  4984 driving key policy presentation nested-reference unchanged"},{"id":"IETF RFC 1958","type":"specification","body":"IETF","designation":"RFC 1958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1958.txt","https://www.rfc-editor.org/rfc/rfc1958.pdf"],"folder":"IETF/RFC-1958","files":{"txt":{"path":"standards/IETF/RFC-1958/RFC-1958.txt","sha256":"4f93f2eafe9a19240a2f4c1ca9fc8e4712e163d834e0f12b3322d57f7f9cd986"}},"tags":["nested-reference","unchanged"],"summary":"The Internet and its architecture have grown in evolutionary fashion\n from modest beginnings, rather than from a Grand Plan. While this\n process of evolution is one of the main reasons for the technology's\n success, it nevertheless seems useful to record a snapshot of the\n current principles of the Internet architecture. This is intended for\n general guidance and general interest, and is in no way intended to\n be a formal or invariant reference model.","scope_keywords":["1958","authentication","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5338","folder":"IETF/RFC-5338","source":"IETF/RFC-5338/RFC-5338.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 1958 The Internet and its architecture have grown in evolutionary fashion\n from modest beginnings, rather than from a Grand Plan. While this\n process of evolution is one of the main reasons for the technology's\n success, it nevertheless seems useful to record a snapshot of the\n current principles of the Internet architecture. This is intended for\n general guidance and general interest, and is in no way intended to\n be a formal or invariant reference model. 1958 authentication key subject nested-reference unchanged"},{"id":"IETF RFC 2818","type":"specification","body":"IETF","designation":"RFC 2818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2818.txt","https://www.rfc-editor.org/rfc/rfc2818.pdf"],"folder":"IETF/RFC-2818","files":{"txt":{"path":"standards/IETF/RFC-2818/RFC-2818.txt","sha256":"4ef02c2b9185fe7b0af4c8777be460f1e156bc57313b1290c9097f83b9f43916"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to use TLS to secure HTTP connections over\n the Internet. Current practice is to layer HTTP over SSL (the\n predecessor to TLS), distinguishing secured traffic from insecure\n traffic by the use of a different server port. This document\n documents that practice using TLS. A companion document describes a\n method for using HTTP/TLS over the same port as normal HTTP\n [RFC2817].","scope_keywords":["2818","http","identification","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.1.1","source":"ETSI/TS-119-412-6-V1.1.1/TS-119-412-6-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 2818 This memo describes how to use TLS to secure HTTP connections over\n the Internet. Current practice is to layer HTTP over SSL (the\n predecessor to TLS), distinguishing secured traffic from insecure\n traffic by the use of a different server port. This document\n documents that practice using TLS. A companion document describes a\n method for using HTTP/TLS over the same port as normal HTTP\n [RFC2817]. 2818 http identification key tls nested-reference unchanged"},{"id":"IETF RFC 3426","type":"specification","body":"IETF","designation":"RFC 3426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3426.txt","https://www.rfc-editor.org/rfc/rfc3426.pdf"],"folder":"IETF/RFC-3426","files":{"txt":{"path":"standards/IETF/RFC-3426/RFC-3426.txt","sha256":"3fe3dc9864d4ad3e2fc87ea0fd12be39c75cbaae350014bc773fee44508471b3"}},"tags":["nested-reference","unchanged"],"summary":"This document suggests general architectural and policy questions\n that the IETF community has to address when working on new standards\n and protocols. We note that this document contains questions to be\n addressed, as opposed to guidelines or architectural principles to be\n followed.\n\n1. Introduction\n\n This document suggests general architectural and policy questions to\n be addressed in our work in the IETF. This document contains\n questions to be addressed, as opposed to guidelines or architectural\n principles to be followed. These questions are somewhat similar to\n the \"Security Considerations\" currently required in IETF documents\n [RFC2316].\n\n This document is motivated in part by concerns about a growing lack\n of coherence in the overall Internet architecture. We have moved\n from a world of a single, coherent architecture designed by a small\n group of people, to a world of complex, ","scope_keywords":["3426","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null}],"search_text":"IETF RFC 3426 This document suggests general architectural and policy questions\n that the IETF community has to address when working on new standards\n and protocols. We note that this document contains questions to be\n addressed, as opposed to guidelines or architectural principles to be\n followed.\n\n1. Introduction\n\n This document suggests general architectural and policy questions to\n be addressed in our work in the IETF. This document contains\n questions to be addressed, as opposed to guidelines or architectural\n principles to be followed. These questions are somewhat similar to\n the \"Security Considerations\" currently required in IETF documents\n [RFC2316].\n\n This document is motivated in part by concerns about a growing lack\n of coherence in the overall Internet architecture. We have moved\n from a world of a single, coherent architecture designed by a small\n group of people, to a world of complex,  3426 policy nested-reference unchanged"},{"id":"IETF RFC 3724","type":"specification","body":"IETF","designation":"RFC 3724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3724.txt","https://www.rfc-editor.org/rfc/rfc3724.pdf"],"folder":"IETF/RFC-3724","files":{"txt":{"path":"standards/IETF/RFC-3724/RFC-3724.txt","sha256":"44b4e4d5a525e32308e9ee73ded0faee712c7fb1175df8830aa0f5d530a7d2e9"}},"tags":["nested-reference","unchanged"],"summary":"The end-to-end principle is the core architectural guideline of the\n Internet. In this document, we briefly examine the development of\n the end-to-end principle as it has been applied to the Internet\n architecture over the years. We discuss current trends in the\n evolution of the Internet architecture in relation to the end-to-end\n principle, and try to draw some conclusion about the evolution of the\n end-to-end principle, and thus for the Internet architecture which it\n supports, in light of these current trends.","scope_keywords":["3724","delivery","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null}],"search_text":"IETF RFC 3724 The end-to-end principle is the core architectural guideline of the\n Internet. In this document, we briefly examine the development of\n the end-to-end principle as it has been applied to the Internet\n architecture over the years. We discuss current trends in the\n evolution of the Internet architecture in relation to the end-to-end\n principle, and try to draw some conclusion about the evolution of the\n end-to-end principle, and thus for the Internet architecture which it\n supports, in light of these current trends. 3724 delivery encryption key management nested-reference unchanged"},{"id":"IETF RFC 4197","type":"specification","body":"IETF","designation":"RFC 4197","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4197.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4197.txt","https://www.rfc-editor.org/rfc/rfc4197.pdf"],"folder":"IETF/RFC-4197","files":{"txt":{"path":"standards/IETF/RFC-4197/RFC-4197.txt","sha256":"9910310a404e5e478b0665c5370e07dbd2bc5391de8ded9f47b9d28e6bf636e6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the specific requirements for edge-to-edge\n emulation of circuits carrying Time Division Multiplexed (TDM)\n digital signals of the Plesiochronous Digital Hierarchy as well as\n the Synchronous Optical NETwork/Synchronous Digital Hierarchy over\n packet-switched networks. It is aligned to the common architecture\n for Pseudo Wire Emulation Edge-to-Edge (PWE3). It makes references\n to the generic requirements for PWE3 where applicable and complements\n them by defining requirements originating from specifics of TDM\n circuits.\n\nRiegel Informational [Page 1]\n\f\nRFC 4197 PWE3 TDM Requirements October 2005","scope_keywords":["4197","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"IETF RFC 4197 This document defines the specific requirements for edge-to-edge\n emulation of circuits carrying Time Division Multiplexed (TDM)\n digital signals of the Plesiochronous Digital Hierarchy as well as\n the Synchronous Optical NETwork/Synchronous Digital Hierarchy over\n packet-switched networks. It is aligned to the common architecture\n for Pseudo Wire Emulation Edge-to-Edge (PWE3). It makes references\n to the generic requirements for PWE3 where applicable and complements\n them by defining requirements originating from specifics of TDM\n circuits.\n\nRiegel Informational [Page 1]\n\f\nRFC 4197 PWE3 TDM Requirements October 2005 4197 delivery nested-reference unchanged"},{"id":"IETF RFC 4924","type":"specification","body":"IETF","designation":"RFC 4924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4924.txt","https://www.rfc-editor.org/rfc/rfc4924.pdf"],"folder":"IETF/RFC-4924","files":{"txt":{"path":"standards/IETF/RFC-4924/RFC-4924.txt","sha256":"3d9ee6980061857a90b374e4ffc1be91c7640fbe7319391872a9aae26e269a27"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a review of previous IAB statements on\n Internet transparency, as well a discussion of new transparency\n issues. Far from having lessened in relevance, technical\n implications of intentionally or inadvertently impeding network\n transparency play a critical role in the Internet's ability to\n support innovation and global communication. This document provides\n some specific illustrations of those potential impacts.","scope_keywords":["4924","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5902","folder":"IETF/RFC-5902","source":"IETF/RFC-5902/RFC-5902.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 4924 This document provides a review of previous IAB statements on\n Internet transparency, as well a discussion of new transparency\n issues. Far from having lessened in relevance, technical\n implications of intentionally or inadvertently impeding network\n transparency play a critical role in the Internet's ability to\n support innovation and global communication. This document provides\n some specific illustrations of those potential impacts. 4924 trust nested-reference unchanged"},{"id":"IETF RFC 5290","type":"specification","body":"IETF","designation":"RFC 5290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5290.txt","https://www.rfc-editor.org/rfc/rfc5290.pdf"],"folder":"IETF/RFC-5290","files":{"txt":{"path":"standards/IETF/RFC-5290/RFC-5290.txt","sha256":"baa43fe307e1d6ecf5cc1da5bba465b309a38141a2f65372b379cf3340b769d2"}},"tags":["nested-reference","unchanged"],"summary":"This document presents some observations on \"simple best-effort\n traffic\", defined loosely for the purposes of this document as\n Internet traffic that is not covered by Quality of Service (QOS)\n mechanisms, congestion-based pricing, cost-based fairness, admissions\n control, or the like. One observation is that simple best-effort\n traffic serves a useful role in the Internet, and is worth keeping.\n While differential treatment of traffic can clearly be useful, we\n believe such mechanisms are useful as *adjuncts* to simple best-\n effort traffic, not as *replacements* of simple best-effort traffic.\n A second observation is that for simple best-effort traffic, some\n form of rough flow-rate fairness is a useful goal for resource\n allocation, where \"flow-rate fairness\" is defined by the goal of\n equal flow rates for different flows over the same path.\n\nFloyd & Allman Informational [Page 1]\n\f\nR","scope_keywords":["5290","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null}],"search_text":"IETF RFC 5290 This document presents some observations on \"simple best-effort\n traffic\", defined loosely for the purposes of this document as\n Internet traffic that is not covered by Quality of Service (QOS)\n mechanisms, congestion-based pricing, cost-based fairness, admissions\n control, or the like. One observation is that simple best-effort\n traffic serves a useful role in the Internet, and is worth keeping.\n While differential treatment of traffic can clearly be useful, we\n believe such mechanisms are useful as *adjuncts* to simple best-\n effort traffic, not as *replacements* of simple best-effort traffic.\n A second observation is that for simple best-effort traffic, some\n form of rough flow-rate fairness is a useful goal for resource\n allocation, where \"flow-rate fairness\" is defined by the goal of\n equal flow rates for different flows over the same path.\n\nFloyd & Allman Informational [Page 1]\n\f\nR 5290 path nested-reference unchanged"},{"id":"IETF RFC 5338","type":"specification","body":"IETF","designation":"RFC 5338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5338.txt","https://www.rfc-editor.org/rfc/rfc5338.pdf"],"folder":"IETF/RFC-5338","files":{"txt":{"path":"standards/IETF/RFC-5338/RFC-5338.txt","sha256":"9a7e31bec699222a9911e22d4f95bbe671bcb40fc1bd425d52fa079cbfb79f99"}},"tags":["nested-reference","unchanged"],"summary":"This document is an informative overview of how legacy applications\n can be made to work with the Host Identity Protocol (HIP). HIP\n proposes to add a cryptographic name space for network stack names.\n From an application viewpoint, HIP-enabled systems support a new\n address family of host identifiers, but it may be a long time until\n such HIP-aware applications are widely deployed even if host systems\n are upgraded. This informational document discusses implementation\n and Application Programming Interface (API) issues relating to using\n HIP in situations in which the system is HIP-aware but the\n applications are not, and is intended to aid implementors and early\n adopters in thinking about and locally solving systems issues\n regarding the incremental deployment of HIP.\n\nHenderson, et al. Informational [Page 1]\n\f\nRFC 5338 Using HIP with Legacy Applications September 2008","scope_keywords":["5338","hash","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null}],"search_text":"IETF RFC 5338 This document is an informative overview of how legacy applications\n can be made to work with the Host Identity Protocol (HIP). HIP\n proposes to add a cryptographic name space for network stack names.\n From an application viewpoint, HIP-enabled systems support a new\n address family of host identifiers, but it may be a long time until\n such HIP-aware applications are widely deployed even if host systems\n are upgraded. This informational document discusses implementation\n and Application Programming Interface (API) issues relating to using\n HIP in situations in which the system is HIP-aware but the\n applications are not, and is intended to aid implementors and early\n adopters in thinking about and locally solving systems issues\n regarding the incremental deployment of HIP.\n\nHenderson, et al. Informational [Page 1]\n\f\nRFC 5338 Using HIP with Legacy Applications September 2008 5338 hash key management policy nested-reference unchanged"},{"id":"IETF RFC 6550","type":"specification","body":"IETF","designation":"RFC 6550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6550.txt","https://www.rfc-editor.org/rfc/rfc6550.pdf"],"folder":"IETF/RFC-6550","files":{"txt":{"path":"standards/IETF/RFC-6550/RFC-6550.txt","sha256":"2c09f5945d6dbba4b69203a826121150c0cff1748d10f22c5a75060e53f5cb82"}},"tags":["nested-reference","unchanged"],"summary":"Low-Power and Lossy Networks (LLNs) are a class of network in which\n both the routers and their interconnect are constrained. LLN routers\n typically operate with constraints on processing power, memory, and\n energy (battery power). Their interconnects are characterized by\n high loss rates, low data rates, and instability. LLNs are comprised\n of anything from a few dozen to thousands of routers. Supported\n traffic flows include point-to-point (between devices inside the\n LLN), point-to-multipoint (from a central control point to a subset\n of devices inside the LLN), and multipoint-to-point (from devices\n inside the LLN towards a central control point). This document\n specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks\n (RPL), which provides a mechanism whereby multipoint-to-point traffic\n from devices inside the LLN towards a central control point as well\n as point-to-mul","scope_keywords":["6550","algorithm","http","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6552","folder":"IETF/RFC-6552","source":"IETF/RFC-6552/RFC-6552.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7547","folder":"IETF/RFC-7547","source":"IETF/RFC-7547/RFC-7547.txt","version":null}],"search_text":"IETF RFC 6550 Low-Power and Lossy Networks (LLNs) are a class of network in which\n both the routers and their interconnect are constrained. LLN routers\n typically operate with constraints on processing power, memory, and\n energy (battery power). Their interconnects are characterized by\n high loss rates, low data rates, and instability. LLNs are comprised\n of anything from a few dozen to thousands of routers. Supported\n traffic flows include point-to-point (between devices inside the\n LLN), point-to-multipoint (from a central control point to a subset\n of devices inside the LLN), and multipoint-to-point (from devices\n inside the LLN towards a central control point). This document\n specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks\n (RPL), which provides a mechanism whereby multipoint-to-point traffic\n from devices inside the LLN towards a central control point as well\n as point-to-mul 6550 algorithm http license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6620","type":"specification","body":"IETF","designation":"RFC 6620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6620.txt","https://www.rfc-editor.org/rfc/rfc6620.pdf"],"folder":"IETF/RFC-6620","files":{"txt":{"path":"standards/IETF/RFC-6620/RFC-6620.txt","sha256":"f282bb342700d021699c84c898f81b80ec99fc21b5714b034a616a00b8e3b811"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes First-Come, First-Served Source Address\n Validation Improvement (FCFS SAVI), a mechanism that provides source\n address validation for IPv6 networks using the FCFS principle. The\n proposed mechanism is intended to complement ingress filtering\n techniques to help detect and prevent source address spoofing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6620.\n\nNordmark,","scope_keywords":["6620","algorithm","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null}],"search_text":"IETF RFC 6620 This memo describes First-Come, First-Served Source Address\n Validation Improvement (FCFS SAVI), a mechanism that provides source\n address validation for IPv6 networks using the FCFS principle. The\n proposed mechanism is intended to complement ingress filtering\n techniques to help detect and prevent source address spoofing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6620.\n\nNordmark, 6620 algorithm http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 2254","type":"specification","body":"IETF","designation":"RFC 2254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2254.txt","https://www.rfc-editor.org/rfc/rfc2254.pdf"],"folder":"IETF/RFC-2254","files":{"txt":{"path":"standards/IETF/RFC-2254/RFC-2254.txt","sha256":"87a3c211444a730fa7a363ed8ed899457db93ddd4216f10bc837240c500f03c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Howes\nRequest for Comments: 2254 Netscape Communications Corp.\nCategory: Standards Track December 1997\n\n The String Representation of LDAP Search Filters\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nIESG Note\n\n This document describes a directory access protocol that provides\n both read and update access. Update access requires secure\n authentication, but this document does not mandate implementation of\n any satisfactory authentication mechanisms.\n\n In accordance w","scope_keywords":["2254","attribute","attributes","authentication","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null}],"search_text":"IETF RFC 2254 Network Working Group T. Howes\nRequest for Comments: 2254 Netscape Communications Corp.\nCategory: Standards Track December 1997\n\n The String Representation of LDAP Search Filters\n\n1. Status of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nIESG Note\n\n This document describes a directory access protocol that provides\n both read and update access. Update access requires secure\n authentication, but this document does not mandate implementation of\n any satisfactory authentication mechanisms.\n\n In accordance w 2254 attribute attributes authentication presentation nested-reference unchanged"},{"id":"IETF RFC 4515","type":"specification","body":"IETF","designation":"RFC 4515","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4515.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4515.txt","https://www.rfc-editor.org/rfc/rfc4515.pdf"],"folder":"IETF/RFC-4515","files":{"txt":{"path":"standards/IETF/RFC-4515/RFC-4515.txt","sha256":"5b5d3332ca1e49e0b9a21a33bdcf55e6f3b2c5eeeb47457d59391b74c4c7a90d"}},"tags":["nested-reference","unchanged"],"summary":"Lightweight Directory Access Protocol (LDAP) search filters are\n transmitted in the LDAP protocol using a binary representation that\n is appropriate for use on the network. This document defines a\n human-readable string representation of LDAP search filters that is\n appropriate for use in LDAP URLs (RFC 4516) and in other\n applications.","scope_keywords":["4515","attribute","attributes","key","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"IETF RFC 4515 Lightweight Directory Access Protocol (LDAP) search filters are\n transmitted in the LDAP protocol using a binary representation that\n is appropriate for use on the network. This document defines a\n human-readable string representation of LDAP search filters that is\n appropriate for use in LDAP URLs (RFC 4516) and in other\n applications. 4515 attribute attributes key presentation risk nested-reference unchanged"},{"id":"IETF RFC 2395","type":"specification","body":"IETF","designation":"RFC 2395","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2395.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2395.txt","https://www.rfc-editor.org/rfc/rfc2395.pdf"],"folder":"IETF/RFC-2395","files":{"txt":{"path":"standards/IETF/RFC-2395/RFC-2395.txt","sha256":"b59f825b323ebd8680d75a23921b35188a2b92017af456a276180884c45f87dd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a compression method based on the LZS\n compression algorithm. This document defines the application of the\n LZS algorithm to the IP Payload Compression Protocol [IPCOMP].\n [IPCOMP] defines a method for applying lossless compression to the\n payloads of Internet Protocol datagrams.","scope_keywords":["2395","algorithm","algorithms","attribute","attributes","key","license","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 3051","folder":"IETF/RFC-3051","source":"IETF/RFC-3051/RFC-3051.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2395 This document describes a compression method based on the LZS\n compression algorithm. This document defines the application of the\n LZS algorithm to the IP Payload Compression Protocol [IPCOMP].\n [IPCOMP] defines a method for applying lossless compression to the\n payloads of Internet Protocol datagrams. 2395 algorithm algorithms attribute attributes key license tls nested-reference unchanged"},{"id":"IETF RFC 4121","type":"specification","body":"IETF","designation":"RFC 4121","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4121.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4121.txt","https://www.rfc-editor.org/rfc/rfc4121.pdf"],"folder":"IETF/RFC-4121","files":{"txt":{"path":"standards/IETF/RFC-4121/RFC-4121.txt","sha256":"2bdacc59a820b192e8787a46c742ce94719a65994552615ce0c158c3086fbe8f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines protocols, procedures, and conventions to be\n employed by peers implementing the Generic Security Service\n Application Program Interface (GSS-API) when using the Kerberos\n Version 5 mechanism.\n\n RFC 1964 is updated and incremental changes are proposed in response\n to recent developments such as the introduction of Kerberos\n cryptosystem framework. These changes support the inclusion of new\n cryptosystems, by defining new per-message tokens along with their\n encryption and checksum algorithms based on the cryptosystem\n profiles.\n\nZhu, et al. Standards Track [Page 1]\n\f\nRFC 4121 Kerberos Version 5 GSS-API July 2005","scope_keywords":["4121","algorithm","algorithms","encryption","key","keys","profile","profiles","seal","sealing"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 5554","folder":"IETF/RFC-5554","source":"IETF/RFC-5554/RFC-5554.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 4121 This document defines protocols, procedures, and conventions to be\n employed by peers implementing the Generic Security Service\n Application Program Interface (GSS-API) when using the Kerberos\n Version 5 mechanism.\n\n RFC 1964 is updated and incremental changes are proposed in response\n to recent developments such as the introduction of Kerberos\n cryptosystem framework. These changes support the inclusion of new\n cryptosystems, by defining new per-message tokens along with their\n encryption and checksum algorithms based on the cryptosystem\n profiles.\n\nZhu, et al. Standards Track [Page 1]\n\f\nRFC 4121 Kerberos Version 5 GSS-API July 2005 4121 algorithm algorithms encryption key keys profile profiles seal sealing nested-reference unchanged"},{"id":"IETF RFC 4401","type":"specification","body":"IETF","designation":"RFC 4401","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4401.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4401.txt","https://www.rfc-editor.org/rfc/rfc4401.pdf"],"folder":"IETF/RFC-4401","files":{"txt":{"path":"standards/IETF/RFC-4401/RFC-4401.txt","sha256":"d13d8541189f7aa369bcfe348e336a438566461b8805af85ab51d026e6868a42"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Pseudo-Random Function (PRF) extension to the\n Generic Security Service Application Program Interface (GSS-API) for\n keying application protocols given an established GSS-API security\n context. The primary intended use of this function is to key secure\n session layers that do not or cannot use GSS-API per-message message\n integrity check (MIC) and wrap tokens for session protection.","scope_keywords":["4401","authentication","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null}],"search_text":"IETF RFC 4401 This document defines a Pseudo-Random Function (PRF) extension to the\n Generic Security Service Application Program Interface (GSS-API) for\n keying application protocols given an established GSS-API security\n context. The primary intended use of this function is to key secure\n session layers that do not or cannot use GSS-API per-message message\n integrity check (MIC) and wrap tokens for session protection. 4401 authentication key keys nested-reference unchanged"},{"id":"IETF RFC 4430","type":"specification","body":"IETF","designation":"RFC 4430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4430.txt","https://www.rfc-editor.org/rfc/rfc4430.pdf"],"folder":"IETF/RFC-4430","files":{"txt":{"path":"standards/IETF/RFC-4430/RFC-4430.txt","sha256":"7e45d343ae5f7bf36303eced443c731af864697397ecb0342487b8d5d6cac15c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Kerberized Internet Negotiation of Keys\n (KINK) protocol. KINK defines a low-latency, computationally\n inexpensive, easily managed, and cryptographically sound protocol to\n establish and maintain security associations using the Kerberos\n authentication system. KINK reuses the Quick Mode payloads of the\n Internet Key Exchange (IKE), which should lead to substantial reuse\n of existing IKE implementations.","scope_keywords":["4430","authentication","credential","credentials","identification","key","keys","management","pki","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null}],"search_text":"IETF RFC 4430 This document describes the Kerberized Internet Negotiation of Keys\n (KINK) protocol. KINK defines a low-latency, computationally\n inexpensive, easily managed, and cryptographically sound protocol to\n establish and maintain security associations using the Kerberos\n authentication system. KINK reuses the Quick Mode payloads of the\n Internet Key Exchange (IKE), which should lead to substantial reuse\n of existing IKE implementations. 4430 authentication credential credentials identification key keys management pki policy trust nested-reference unchanged"},{"id":"IETF RFC 4752","type":"specification","body":"IETF","designation":"RFC 4752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4752.txt","https://www.rfc-editor.org/rfc/rfc4752.pdf"],"folder":"IETF/RFC-4752","files":{"txt":{"path":"standards/IETF/RFC-4752/RFC-4752.txt","sha256":"3a53db51f45da47a2cdbf960806d22e60999c12d00f86cc54bc92c71c71bd48d"}},"tags":["nested-reference","unchanged"],"summary":"The Simple Authentication and Security Layer (SASL) is a framework\n for adding authentication support to connection-based protocols.\n This document describes the method for using the Generic Security\n Service Application Program Interface (GSS-API) Kerberos V5 in the\n SASL.\n\n This document replaces Section 7.2 of RFC 2222, the definition of the\n \"GSSAPI\" SASL mechanism. This document, together with RFC 4422,\n obsoletes RFC 2222.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 4752 SASL GSSAPI Mechanism November 2006","scope_keywords":["4752","authentication","key","policy","profile","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4752 The Simple Authentication and Security Layer (SASL) is a framework\n for adding authentication support to connection-based protocols.\n This document describes the method for using the Generic Security\n Service Application Program Interface (GSS-API) Kerberos V5 in the\n SASL.\n\n This document replaces Section 7.2 of RFC 2222, the definition of the\n \"GSSAPI\" SASL mechanism. This document, together with RFC 4422,\n obsoletes RFC 2222.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 4752 SASL GSSAPI Mechanism November 2006 4752 authentication key policy profile qualified trust nested-reference unchanged"},{"id":"IETF RFC 5056","type":"specification","body":"IETF","designation":"RFC 5056","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5056.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5056.txt","https://www.rfc-editor.org/rfc/rfc5056.pdf"],"folder":"IETF/RFC-5056","files":{"txt":{"path":"standards/IETF/RFC-5056/RFC-5056.txt","sha256":"decec18daccd159c0fd3141dba122a8c66dbded12d6ac70adf34b75488c25920"}},"tags":["nested-reference","unchanged"],"summary":"The concept of channel binding allows applications to establish that\n the two end-points of a secure channel at one network layer are the\n same as at a higher layer by binding authentication at the higher\n layer to the channel at the lower layer. This allows applications to\n delegate session protection to lower layers, which has various\n performance benefits.\n\n This document discusses and formalizes the concept of channel binding\n to secure channels.\n\nWilliams Standards Track [Page 1]\n\f\nRFC 5056 On Channel Bindings November 2007","scope_keywords":["5056","authentication","http","key","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5554","folder":"IETF/RFC-5554","source":"IETF/RFC-5554/RFC-5554.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null}],"search_text":"IETF RFC 5056 The concept of channel binding allows applications to establish that\n the two end-points of a secure channel at one network layer are the\n same as at a higher layer by binding authentication at the higher\n layer to the channel at the lower layer. This allows applications to\n delegate session protection to lower layers, which has various\n performance benefits.\n\n This document discusses and formalizes the concept of channel binding\n to secure channels.\n\nWilliams Standards Track [Page 1]\n\f\nRFC 5056 On Channel Bindings November 2007 5056 authentication http key tls trust nested-reference unchanged"},{"id":"IETF RFC 5587","type":"specification","body":"IETF","designation":"RFC 5587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5587.txt","https://www.rfc-editor.org/rfc/rfc5587.pdf"],"folder":"IETF/RFC-5587","files":{"txt":{"path":"standards/IETF/RFC-5587/RFC-5587.txt","sha256":"18152393f5d3950ed707d389be09443603a56c920bceca7a1239100dd5e9aaab"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces new application programming interfaces\n (APIs) to the Generic Security Services API (GSS-API) for extended\n mechanism attribute inquiry. These interfaces are primarily intended\n to reduce instances of hardcoding of mechanism identifiers in GSS\n applications.\n\n These interfaces include mechanism attributes and attribute sets, a\n function for inquiring the attributes of a mechanism, a function for\n indicating mechanisms that possess given attributes, and a function\n for displaying mechanism attributes.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyr","scope_keywords":["5587","attribute","attributes","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null}],"search_text":"IETF RFC 5587 This document introduces new application programming interfaces\n (APIs) to the Generic Security Services API (GSS-API) for extended\n mechanism attribute inquiry. These interfaces are primarily intended\n to reduce instances of hardcoding of mechanism identifiers in GSS\n applications.\n\n These interfaces include mechanism attributes and attribute sets, a\n function for inquiring the attributes of a mechanism, a function for\n indicating mechanisms that possess given attributes, and a function\n for displaying mechanism attributes.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyr 5587 attribute attributes authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2547","type":"specification","body":"IETF","designation":"RFC 2547","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2547.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2547.txt","https://www.rfc-editor.org/rfc/rfc2547.pdf"],"folder":"IETF/RFC-2547","files":{"txt":{"path":"standards/IETF/RFC-2547/RFC-2547.txt","sha256":"9263e1a04b8f0b285a22122fb4e6ca6ecde37c4ce74b0a111cc1579e48f07bce"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method by which a Service Provider with an\n IP backbone may provide VPNs (Virtual Private Networks) for its\n customers. MPLS (Multiprotocol Label Switching) is used for\n forwarding packets over the backbone, and BGP (Border Gateway\n Protocol) is used for distributing routes over the backbone. The\n primary goal of this method is to support the outsourcing of IP\n backbone services for enterprise networks. It does so in a manner\n which is simple for the enterprise, while still scalable and flexible\n for the Service Provider, and while allowing the Service Provider to\n add value. These techniques can also be used to provide a VPN which\n itself provides IP service to customers.","scope_keywords":["2547","attribute","attributes","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 4026","folder":"IETF/RFC-4026","source":"IETF/RFC-4026/RFC-4026.txt","version":null},{"body":"IETF","designation":"RFC 4098","folder":"IETF/RFC-4098","source":"IETF/RFC-4098/RFC-4098.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4984","folder":"IETF/RFC-4984","source":"IETF/RFC-4984/RFC-4984.txt","version":null}],"search_text":"IETF RFC 2547 This document describes a method by which a Service Provider with an\n IP backbone may provide VPNs (Virtual Private Networks) for its\n customers. MPLS (Multiprotocol Label Switching) is used for\n forwarding packets over the backbone, and BGP (Border Gateway\n Protocol) is used for distributing routes over the backbone. The\n primary goal of this method is to support the outsourcing of IP\n backbone services for enterprise networks. It does so in a manner\n which is simple for the enterprise, while still scalable and flexible\n for the Service Provider, and while allowing the Service Provider to\n add value. These techniques can also be used to provide a VPN which\n itself provides IP service to customers. 2547 attribute attributes policies policy nested-reference unchanged"},{"id":"IETF RFC 3943","type":"specification","body":"IETF","designation":"RFC 3943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3943.txt","https://www.rfc-editor.org/rfc/rfc3943.pdf"],"folder":"IETF/RFC-3943","files":{"txt":{"path":"standards/IETF/RFC-3943/RFC-3943.txt","sha256":"6b07f6a67c3c4dee91ed113c86ca4f2ffb4ae68e56f30623087d898fb0becc92"}},"tags":["nested-reference","unchanged"],"summary":"The Transport Layer Security (TLS) protocol (RFC 2246) includes\n features to negotiate selection of a lossless data compression method\n as part of the TLS Handshake Protocol and then to apply the algorithm\n associated with the selected method as part of the TLS Record\n Protocol. TLS defines one standard compression method, which\n specifies that data exchanged via the record protocol will not be\n compressed. This document describes an additional compression method\n associated with the Lempel-Ziv-Stac (LZS) lossless data compression\n algorithm for use with TLS. This document also defines the\n application of the LZS algorithm to the TLS Record Protocol.\n\nFriend Informational [Page 1]\n\f\nRFC 3943 TLS Compression Using LZS November 2004","scope_keywords":["3943","algorithm","algorithms","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3943 The Transport Layer Security (TLS) protocol (RFC 2246) includes\n features to negotiate selection of a lossless data compression method\n as part of the TLS Handshake Protocol and then to apply the algorithm\n associated with the selected method as part of the TLS Record\n Protocol. TLS defines one standard compression method, which\n specifies that data exchanged via the record protocol will not be\n compressed. This document describes an additional compression method\n associated with the Lempel-Ziv-Stac (LZS) lossless data compression\n algorithm for use with TLS. This document also defines the\n application of the LZS algorithm to the TLS Record Protocol.\n\nFriend Informational [Page 1]\n\f\nRFC 3943 TLS Compression Using LZS November 2004 3943 algorithm algorithms key path tls nested-reference unchanged"},{"id":"IETF RFC 3542","type":"specification","body":"IETF","designation":"RFC 3542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3542.txt","https://www.rfc-editor.org/rfc/rfc3542.pdf"],"folder":"IETF/RFC-3542","files":{"txt":{"path":"standards/IETF/RFC-3542/RFC-3542.txt","sha256":"c2b3296882ca580c21a96b3b93dd0a2972809db0ebdf9ec7f55a13602e729ce6"}},"tags":["nested-reference","unchanged"],"summary":"This document provides sockets Application Program Interface (API) to\n support \"advanced\" IPv6 applications, as a supplement to a separate\n specification, RFC 3493. The expected applications include Ping,\n Traceroute, routing daemons and the like, which typically use raw\n sockets to access IPv6 or ICMPv6 header fields. This document\n proposes some portable interfaces for applications that use raw\n sockets under IPv6. There are other features of IPv6 that some\n applications will need to access: interface identification\n (specifying the outgoing interface and determining the incoming\n interface), IPv6 extension headers, and path Maximum Transmission\n Unit (MTU) information. This document provides API access to these\n features too. Additionally, some extended interfaces to libraries\n for the \"r\" commands are defined. The extension will provide better\n backward compatibility to existing impl","scope_keywords":["3542","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null}],"search_text":"IETF RFC 3542 This document provides sockets Application Program Interface (API) to\n support \"advanced\" IPv6 applications, as a supplement to a separate\n specification, RFC 3493. The expected applications include Ping,\n Traceroute, routing daemons and the like, which typically use raw\n sockets to access IPv6 or ICMPv6 header fields. This document\n proposes some portable interfaces for applications that use raw\n sockets under IPv6. There are other features of IPv6 that some\n applications will need to access: interface identification\n (specifying the outgoing interface and determining the incoming\n interface), IPv6 extension headers, and path Maximum Transmission\n Unit (MTU) information. This document provides API access to these\n features too. Additionally, some extended interfaces to libraries\n for the \"r\" commands are defined. The extension will provide better\n backward compatibility to existing impl 3542 identification path nested-reference unchanged"},{"id":"IETF RFC 4890","type":"specification","body":"IETF","designation":"RFC 4890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4890.txt","https://www.rfc-editor.org/rfc/rfc4890.pdf"],"folder":"IETF/RFC-4890","files":{"txt":{"path":"standards/IETF/RFC-4890/RFC-4890.txt","sha256":"d95ca8bd14a0a7e139e77d3b29c430b65ff1360c013e3f02185dfbc1d636e7b9"}},"tags":["nested-reference","unchanged"],"summary":"In networks supporting IPv6, the Internet Control Message Protocol\n version 6 (ICMPv6) plays a fundamental role with a large number of\n functions, and a correspondingly large number of message types and\n options. ICMPv6 is essential to the functioning of IPv6, but there\n are a number of security risks associated with uncontrolled\n forwarding of ICMPv6 messages. Filtering strategies designed for the\n corresponding protocol, ICMP, in IPv4 networks are not directly\n applicable, because these strategies are intended to accommodate a\n useful auxiliary protocol that may not be required for correct\n functioning.\n\n This document provides some recommendations for ICMPv6 firewall\n filter configuration that will allow propagation of ICMPv6 messages\n that are needed to maintain the functioning of the network but drop\n messages that are potential security risks.\n\nDavies & Mohacsi Informational [Page ","scope_keywords":["4890","certificate","path","policies","policy","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 4890 In networks supporting IPv6, the Internet Control Message Protocol\n version 6 (ICMPv6) plays a fundamental role with a large number of\n functions, and a correspondingly large number of message types and\n options. ICMPv6 is essential to the functioning of IPv6, but there\n are a number of security risks associated with uncontrolled\n forwarding of ICMPv6 messages. Filtering strategies designed for the\n corresponding protocol, ICMP, in IPv4 networks are not directly\n applicable, because these strategies are intended to accommodate a\n useful auxiliary protocol that may not be required for correct\n functioning.\n\n This document provides some recommendations for ICMPv6 firewall\n filter configuration that will allow propagation of ICMPv6 messages\n that are needed to maintain the functioning of the network but drop\n messages that are potential security risks.\n\nDavies & Mohacsi Informational [Page  4890 certificate path policies policy risk trust nested-reference unchanged"},{"id":"IETF RFC 6180","type":"specification","body":"IETF","designation":"RFC 6180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6180.txt","https://www.rfc-editor.org/rfc/rfc6180.pdf"],"folder":"IETF/RFC-6180","files":{"txt":{"path":"standards/IETF/RFC-6180/RFC-6180.txt","sha256":"e97287bd0e5c3ae90390f57130e297e6869fc26f69bf37d933a5eb268b686dad"}},"tags":["nested-reference","unchanged"],"summary":"The Internet continues to grow beyond the capabilities of IPv4. An\n expansion in the address space is clearly required. With its\n increase in the number of available prefixes and addresses in a\n subnet, and improvements in address management, IPv6 is the only real\n option on the table. Yet, IPv6 deployment requires some effort,\n resources, and expertise. The availability of many different\n deployment models is one reason why expertise is required. This\n document discusses the IPv6 deployment models and migration tools,\n and it recommends ones that have been found to work well in\n operational networks in many common situations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It ha","scope_keywords":["6180","algorithm","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null}],"search_text":"IETF RFC 6180 The Internet continues to grow beyond the capabilities of IPv4. An\n expansion in the address space is clearly required. With its\n increase in the number of available prefixes and addresses in a\n subnet, and improvements in address management, IPv6 is the only real\n option on the table. Yet, IPv6 deployment requires some effort,\n resources, and expertise. The availability of many different\n deployment models is one reason why expertise is required. This\n document discusses the IPv6 deployment models and migration tools,\n and it recommends ones that have been found to work well in\n operational networks in many common situations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It ha 6180 algorithm http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7112","type":"specification","body":"IETF","designation":"RFC 7112","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7112.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7112.txt","https://www.rfc-editor.org/rfc/rfc7112.pdf"],"folder":"IETF/RFC-7112","files":{"txt":{"path":"standards/IETF/RFC-7112/RFC-7112.txt","sha256":"71f6a023f1ec0982d594658b0689d0b36c88840bc340ebc92a65b0d195522255"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 specification allows IPv6 Header Chains of an arbitrary\n size. The specification also allows options that can, in turn,\n extend each of the headers. In those scenarios in which the IPv6\n Header Chain or options are unusually long and packets are\n fragmented, or scenarios in which the fragment size is very small,\n the First Fragment of a packet may fail to include the entire IPv6\n Header Chain. This document discusses the interoperability and\n security problems of such traffic, and updates RFC 2460 such that the\n First Fragment of a packet is required to contain the entire IPv6\n Header Chain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri","scope_keywords":["7112","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 7112 The IPv6 specification allows IPv6 Header Chains of an arbitrary\n size. The specification also allows options that can, in turn,\n extend each of the headers. In those scenarios in which the IPv6\n Header Chain or options are unusually long and packets are\n fragmented, or scenarios in which the fragment size is very small,\n the First Fragment of a packet may fail to include the entire IPv6\n Header Chain. This document discusses the interoperability and\n security problems of such traffic, and updates RFC 2460 such that the\n First Fragment of a packet is required to contain the entire IPv6\n Header Chain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri 7112 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7739","type":"specification","body":"IETF","designation":"RFC 7739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7739.txt","https://www.rfc-editor.org/rfc/rfc7739.pdf"],"folder":"IETF/RFC-7739","files":{"txt":{"path":"standards/IETF/RFC-7739/RFC-7739.txt","sha256":"9311bfe3fd9b65482cb64d3a4114306f4e31d55a037c2e21decbd78a64c8458e"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 specifies the Fragment Header, which is employed for the\n fragmentation and reassembly mechanisms. The Fragment Header\n contains an \"Identification\" field that, together with the IPv6\n Source Address and the IPv6 Destination Address of a packet,\n identifies fragments that correspond to the same original datagram,\n such that they can be reassembled together by the receiving host.\n The only requirement for setting the Identification field is that the\n corresponding value must be different than that employed for any\n other fragmented datagram sent recently with the same Source Address\n and Destination Address. Some implementations use a simple global\n counter for setting the Identification field, thus leading to\n predictable Identification values. This document analyzes the\n security implications of predictable Identification values, and\n provides implementation guidance for setting th","scope_keywords":["7739","algorithm","algorithms","hash","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7739 IPv6 specifies the Fragment Header, which is employed for the\n fragmentation and reassembly mechanisms. The Fragment Header\n contains an \"Identification\" field that, together with the IPv6\n Source Address and the IPv6 Destination Address of a packet,\n identifies fragments that correspond to the same original datagram,\n such that they can be reassembled together by the receiving host.\n The only requirement for setting the Identification field is that the\n corresponding value must be different than that employed for any\n other fragmented datagram sent recently with the same Source Address\n and Destination Address. Some implementations use a simple global\n counter for setting the Identification field, thus leading to\n predictable Identification values. This document analyzes the\n security implications of predictable Identification values, and\n provides implementation guidance for setting th 7739 algorithm algorithms hash http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2931","type":"specification","body":"IETF","designation":"RFC 2931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2931.txt","https://www.rfc-editor.org/rfc/rfc2931.pdf"],"folder":"IETF/RFC-2931","files":{"txt":{"path":"standards/IETF/RFC-2931/RFC-2931.txt","sha256":"54ea400e6041ce271d711ed84eec76ce10a6496e2315c072e04f13cac22df874"}},"tags":["nested-reference","unchanged"],"summary":"Extensions to the Domain Name System (DNS) are described in [RFC\n 2535] that can provide data origin and transaction integrity and\n authentication to security aware resolvers and applications through\n the use of cryptographic digital signatures.\n\n Implementation experience has indicated the need for minor but non-\n interoperable changes in Request and Transaction signature resource\n records ( SIG(0)s ). These changes are documented herein.\n\nAcknowledgments\n\n The contributions and suggestions of the following persons (in\n alphabetic order) to this memo are gratefully acknowledged:\n\n Olafur Gudmundsson\n\n Ed Lewis\n\n Erik Nordmark\n\n Brian Wellington\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2931 DNS SIG(0) September 2000","scope_keywords":["2931","authentication","hash","key","keys","policy","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3445","folder":"IETF/RFC-3445","source":"IETF/RFC-3445/RFC-3445.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null}],"search_text":"IETF RFC 2931 Extensions to the Domain Name System (DNS) are described in [RFC\n 2535] that can provide data origin and transaction integrity and\n authentication to security aware resolvers and applications through\n the use of cryptographic digital signatures.\n\n Implementation experience has indicated the need for minor but non-\n interoperable changes in Request and Transaction signature resource\n records ( SIG(0)s ). These changes are documented herein.\n\nAcknowledgments\n\n The contributions and suggestions of the following persons (in\n alphabetic order) to this memo are gratefully acknowledged:\n\n Olafur Gudmundsson\n\n Ed Lewis\n\n Erik Nordmark\n\n Brian Wellington\n\nEastlake Standards Track [Page 1]\n\f\nRFC 2931 DNS SIG(0) September 2000 2931 authentication hash key keys policy signature signatures nested-reference unchanged"},{"id":"IETF RFC 3080","type":"specification","body":"IETF","designation":"RFC 3080","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3080.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3080.txt","https://www.rfc-editor.org/rfc/rfc3080.pdf"],"folder":"IETF/RFC-3080","files":{"txt":{"path":"standards/IETF/RFC-3080/RFC-3080.txt","sha256":"080d95f8b7ca3fdb6a4f7865f65c6cbc14bb8f8afb01042bf73a94ff0fa6cabe"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a generic application protocol kernel for\n connection-oriented, asynchronous interactions called the BEEP\n (Blocks Extensible Exchange Protocol) core. BEEP permits\n simultaneous and independent exchanges within the context of a single\n application user-identity, supporting both textual and binary\n messages.\n\nRose Standards Track [Page 1]\n\f\nRFC 3080 The BEEP Core March 2001","scope_keywords":["3080","authentication","identification","management","profile","profiles","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3081","folder":"IETF/RFC-3081","source":"IETF/RFC-3081/RFC-3081.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3288","folder":"IETF/RFC-3288","source":"IETF/RFC-3288/RFC-3288.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"IETF RFC 3080 This memo describes a generic application protocol kernel for\n connection-oriented, asynchronous interactions called the BEEP\n (Blocks Extensible Exchange Protocol) core. BEEP permits\n simultaneous and independent exchanges within the context of a single\n application user-identity, supporting both textual and binary\n messages.\n\nRose Standards Track [Page 1]\n\f\nRFC 3080 The BEEP Core March 2001 3080 authentication identification management profile profiles tls nested-reference unchanged"},{"id":"IETF RFC 5973","type":"specification","body":"IETF","designation":"RFC 5973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5973.txt","https://www.rfc-editor.org/rfc/rfc5973.pdf"],"folder":"IETF/RFC-5973","files":{"txt":{"path":"standards/IETF/RFC-5973/RFC-5973.txt","sha256":"05b8ddf3332cb045d8e748458b2a1f216e47bdace06b90fc91e1b1201f080f56"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the NSIS Signaling Layer Protocol (NSLP) for\n Network Address Translators (NATs) and firewalls. This NSLP allows\n hosts to signal on the data path for NATs and firewalls to be\n configured according to the needs of the application data flows. For\n instance, it enables hosts behind NATs to obtain a publicly reachable\n address and hosts behind firewalls to receive data traffic. The\n overall architecture is given by the framework and requirements\n defined by the Next Steps in Signaling (NSIS) working group. The\n network scenarios, the protocol itself, and examples for path-coupled\n signaling are given in this memo.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a","scope_keywords":["5973","authentication","authorization","http","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 5973 This memo defines the NSIS Signaling Layer Protocol (NSLP) for\n Network Address Translators (NATs) and firewalls. This NSLP allows\n hosts to signal on the data path for NATs and firewalls to be\n configured according to the needs of the application data flows. For\n instance, it enables hosts behind NATs to obtain a publicly reachable\n address and hosts behind firewalls to receive data traffic. The\n overall architecture is given by the framework and requirements\n defined by the Next Steps in Signaling (NSIS) working group. The\n network scenarios, the protocol itself, and examples for path-coupled\n signaling are given in this memo.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a 5973 authentication authorization http license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6810","type":"specification","body":"IETF","designation":"RFC 6810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6810.txt","https://www.rfc-editor.org/rfc/rfc6810.pdf"],"folder":"IETF/RFC-6810","files":{"txt":{"path":"standards/IETF/RFC-6810/RFC-6810.txt","sha256":"18ff35b06caff41d18189800802dee0dfdcd9377baebf75727da0bca2a1838ca"}},"tags":["nested-reference","unchanged"],"summary":"In order to verifiably validate the origin Autonomous Systems of BGP\n announcements, routers need a simple but reliable mechanism to\n receive Resource Public Key Infrastructure (RFC 6480) prefix origin\n data from a trusted cache. This document describes a protocol to\n deliver validated prefix origin data to routers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6810.\n\nCopyright Notice\n","scope_keywords":["6810","http","key","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6810 In order to verifiably validate the origin Autonomous Systems of BGP\n announcements, routers need a simple but reliable mechanism to\n receive Resource Public Key Infrastructure (RFC 6480) prefix origin\n data from a trusted cache. This document describes a protocol to\n deliver validated prefix origin data to routers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6810.\n\nCopyright Notice\n 6810 http key license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7641","type":"specification","body":"IETF","designation":"RFC 7641","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7641.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7641.txt","https://www.rfc-editor.org/rfc/rfc7641.pdf"],"folder":"IETF/RFC-7641","files":{"txt":{"path":"standards/IETF/RFC-7641/RFC-7641.txt","sha256":"5f1a4fce0f4754ab0de0f10eed23c4a7ce48fdd657bc4a88712c5b860a1d701f"}},"tags":["nested-reference","unchanged"],"summary":"The Constrained Application Protocol (CoAP) is a RESTful application\n protocol for constrained nodes and networks. The state of a resource\n on a CoAP server can change over time. This document specifies a\n simple protocol extension for CoAP that enables CoAP clients to\n \"observe\" resources, i.e., to retrieve a representation of a resource\n and keep this representation updated by the server over a period of\n time. The protocol follows a best-effort approach for sending new\n representations to clients and provides eventual consistency between\n the state observed by each client and the actual resource state at\n the server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the","scope_keywords":["7641","http","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 7641 The Constrained Application Protocol (CoAP) is a RESTful application\n protocol for constrained nodes and networks. The state of a resource\n on a CoAP server can change over time. This document specifies a\n simple protocol extension for CoAP that enables CoAP clients to\n \"observe\" resources, i.e., to retrieve a representation of a resource\n and keep this representation updated by the server over a period of\n time. The protocol follows a best-effort approach for sending new\n representations to clients and provides eventual consistency between\n the state observed by each client and the actual resource state at\n the server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the 7641 http license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8260","type":"specification","body":"IETF","designation":"RFC 8260","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8260.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8260.txt","https://www.rfc-editor.org/rfc/rfc8260.pdf"],"folder":"IETF/RFC-8260","files":{"txt":{"path":"standards/IETF/RFC-8260/RFC-8260.txt","sha256":"fc7345af5beafa61a0c46341987c3073bb17cee7acde000c90bfba595349af68"}},"tags":["nested-reference","unchanged"],"summary":"The Stream Control Transmission Protocol (SCTP) is a message-oriented\n transport protocol supporting arbitrarily large user messages. This\n document adds a new chunk to SCTP for carrying payload data. This\n allows a sender to interleave different user messages that would\n otherwise result in head-of-line blocking at the sender. The\n interleaving of user messages is required for WebRTC data channels.\n\n Whenever an SCTP sender is allowed to send user data, it may choose\n from multiple outgoing SCTP streams. Multiple ways for performing\n this selection, called stream schedulers, are defined in this\n document. A stream scheduler can choose to either implement, or not\n implement, user message interleaving.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com","scope_keywords":["8260","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null}],"search_text":"IETF RFC 8260 The Stream Control Transmission Protocol (SCTP) is a message-oriented\n transport protocol supporting arbitrarily large user messages. This\n document adds a new chunk to SCTP for carrying payload data. This\n allows a sender to interleave different user messages that would\n otherwise result in head-of-line blocking at the sender. The\n interleaving of user messages is required for WebRTC data channels.\n\n Whenever an SCTP sender is allowed to send user data, it may choose\n from multiple outgoing SCTP streams. Multiple ways for performing\n this selection, called stream schedulers, are defined in this\n document. A stream scheduler can choose to either implement, or not\n implement, user message interleaving.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF com 8260 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 2350","type":"specification","body":"IETF","designation":"RFC 2350","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2350.txt","https://www.rfc-editor.org/rfc/rfc2350.pdf"],"folder":"IETF/RFC-2350","files":{"txt":{"path":"standards/IETF/RFC-2350/RFC-2350.txt","sha256":"24ad7d6d5aeb6612e65b784468e8727d5b98ad056a5bcfb20a3d5cb3b125e806"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to express the general Internet\n community's expectations of Computer Security Incident Response Teams\n (CSIRTs). It is not possible to define a set of requirements that\n would be appropriate for all teams, but it is possible and helpful to\n list and describe the general set of topics and issues which are of\n concern and interest to constituent communities.\n\n CSIRT constituents have a legitimate need and right to fully\n understand the policies and procedures of 'their' Computer Security\n Incident Response Team. One way to support this understanding is to\n supply detailed information which users may consider, in the form of\n a formal template completed by the CSIRT. An outline of such a\n template and a filled in example are provided.","scope_keywords":["2350","authentication","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2350 The purpose of this document is to express the general Internet\n community's expectations of Computer Security Incident Response Teams\n (CSIRTs). It is not possible to define a set of requirements that\n would be appropriate for all teams, but it is possible and helpful to\n list and describe the general set of topics and issues which are of\n concern and interest to constituent communities.\n\n CSIRT constituents have a legitimate need and right to fully\n understand the policies and procedures of 'their' Computer Security\n Incident Response Team. One way to support this understanding is to\n supply detailed information which users may consider, in the form of\n a formal template completed by the CSIRT. An outline of such a\n template and a filled in example are provided. 2350 authentication policies subject nested-reference unchanged"},{"id":"IETF RFC 2504","type":"specification","body":"IETF","designation":"RFC 2504","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2504.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2504.txt","https://www.rfc-editor.org/rfc/rfc2504.pdf"],"folder":"IETF/RFC-2504","files":{"txt":{"path":"standards/IETF/RFC-2504/RFC-2504.txt","sha256":"b7765661fa64f1de55357b6373e52d687c78c40018dc9abaceba506979622ae9"}},"tags":["nested-reference","unchanged"],"summary":"The Users' Security Handbook is the companion to the Site Security\n Handbook (SSH). It is intended to provide users with the information\n they need to help keep their networks and systems secure.","scope_keywords":["2504","encryption","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3053","folder":"IETF/RFC-3053","source":"IETF/RFC-3053/RFC-3053.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2504 The Users' Security Handbook is the companion to the Site Security\n Handbook (SSH). It is intended to provide users with the information\n they need to help keep their networks and systems secure. 2504 encryption policy risk nested-reference unchanged"},{"id":"IETF RFC 1984","type":"specification","body":"IETF","designation":"RFC 1984","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1984.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1984.txt","https://www.rfc-editor.org/rfc/rfc1984.pdf"],"folder":"IETF/RFC-1984","files":{"txt":{"path":"standards/IETF/RFC-1984/RFC-1984.txt","sha256":"966c53b5dddd78948a92d647ff057c9ad252973e4390c929de43274a04246792"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group IAB\nRequest for Comments: 1984 IESG\nCategory: Informational August 1996\n\n IAB and IESG Statement on Cryptographic Technology and the Internet\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nCopyright\n\n (C) Internet Society 1996. Reproduction or translation of the\n complete document, but not of extracts, including this notice, is\n freely permitted.\n\nJuly 24, 1996\n\n The Internet Architecture Board (IAB) and the Internet Engineering\n Steering Group (IESG), the bodies which oversee architecture and\n standards for the Internet, are concerned by the need for increased\n protection of international commercial transactions on the Internet,\n and by the need to offer all Internet users an adequate degree of\n privacy.\n\n Security mechanisms be","scope_keywords":["1984","algorithm","algorithms","authentication","encryption","key","keys","policies","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2804","folder":"IETF/RFC-2804","source":"IETF/RFC-2804/RFC-2804.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 1984 Network Working Group IAB\nRequest for Comments: 1984 IESG\nCategory: Informational August 1996\n\n IAB and IESG Statement on Cryptographic Technology and the Internet\n\nStatus of This Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nCopyright\n\n (C) Internet Society 1996. Reproduction or translation of the\n complete document, but not of extracts, including this notice, is\n freely permitted.\n\nJuly 24, 1996\n\n The Internet Architecture Board (IAB) and the Internet Engineering\n Steering Group (IESG), the bodies which oversee architecture and\n standards for the Internet, are concerned by the need for increased\n protection of international commercial transactions on the Internet,\n and by the need to offer all Internet users an adequate degree of\n privacy.\n\n Security mechanisms be 1984 algorithm algorithms authentication encryption key keys policies signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 2804","type":"specification","body":"IETF","designation":"RFC 2804","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2804.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2804.txt","https://www.rfc-editor.org/rfc/rfc2804.pdf"],"folder":"IETF/RFC-2804","files":{"txt":{"path":"standards/IETF/RFC-2804/RFC-2804.txt","sha256":"f3983013018b14daa3db44709781e6964bc328eb44db86f9b225daca01507752"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group IAB\nRequest for Comments: 2804 IESG\nCategory: Informational May 2000\n\n IETF Policy on Wiretapping\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Internet Engineering Task Force (IETF) has been asked to take a\n position on the inclusion into IETF standards-track documents of\n functionality designed to facilitate wiretapping.\n\n This memo explains what the IETF thinks the question means, why its\n answer is \"no\", and what that answer means.\n\n1. Summary position\n\n The IETF has decided not to consider requirements for wiretapping as\n part of the process for creating and maintaining IETF standards.\n\n It takes this position for the following basic","scope_keywords":["2804","delivery","encryption","http","management","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 2804 Network Working Group IAB\nRequest for Comments: 2804 IESG\nCategory: Informational May 2000\n\n IETF Policy on Wiretapping\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Internet Engineering Task Force (IETF) has been asked to take a\n position on the inclusion into IETF standards-track documents of\n functionality designed to facilitate wiretapping.\n\n This memo explains what the IETF thinks the question means, why its\n answer is \"no\", and what that answer means.\n\n1. Summary position\n\n The IETF has decided not to consider requirements for wiretapping as\n part of the process for creating and maintaining IETF standards.\n\n It takes this position for the following basic 2804 delivery encryption http management policy risk nested-reference unchanged"},{"id":"IETF RFC 7258","type":"specification","body":"IETF","designation":"RFC 7258","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7258.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7258.txt","https://www.rfc-editor.org/rfc/rfc7258.pdf"],"folder":"IETF/RFC-7258","files":{"txt":{"path":"standards/IETF/RFC-7258/RFC-7258.txt","sha256":"7c448b871908ff80083486075fa3ec445b75ff284cfdbdf71cec6240d5cc0619"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) S. Farrell\nRequest for Comments: 7258 Trinity College Dublin\nBCP: 188 H. Tschofenig\nCategory: Best Current Practice ARM Ltd.\nISSN: 2070-1721 May 2014\n\n Pervasive Monitoring Is an Attack\n\nAbstract\n\n Pervasive monitoring is a technical attack that should be mitigated\n in the design of IETF protocols, where possible.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/","scope_keywords":["7258","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7536","folder":"IETF/RFC-7536","source":"IETF/RFC-7536/RFC-7536.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 7258 Internet Engineering Task Force (IETF) S. Farrell\nRequest for Comments: 7258 Trinity College Dublin\nBCP: 188 H. Tschofenig\nCategory: Best Current Practice ARM Ltd.\nISSN: 2070-1721 May 2014\n\n Pervasive Monitoring Is an Attack\n\nAbstract\n\n Pervasive monitoring is a technical attack that should be mitigated\n in the design of IETF protocols, where possible.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/ 7258 http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 1987","type":"specification","body":"IETF","designation":"RFC 1987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1987.txt","https://www.rfc-editor.org/rfc/rfc1987.pdf"],"folder":"IETF/RFC-1987","files":{"txt":{"path":"standards/IETF/RFC-1987/RFC-1987.txt","sha256":"968e1c804a0f31a7c7c29b8c4af641604005d538c9c34014e2cd6012fbfd284e"}},"tags":["nested-reference","unchanged"],"summary":"The General Switch Management Protocol (GSMP), is a general purpose\n protocol to control an ATM switch. GSMP allows a controller to\n establish and release connections across the switch; add and delete\n leaves on a point-to-multipoint connection; manage switch ports;\n request configuration information; and request statistics.\n\nNewman, et. al. Informational [Page 1]\n\f\nRFC 1987 GSMP Protocol Specification August 1996","scope_keywords":["1987","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null}],"search_text":"IETF RFC 1987 The General Switch Management Protocol (GSMP), is a general purpose\n protocol to control an ATM switch. GSMP allows a controller to\n establish and release connections across the switch; add and delete\n leaves on a point-to-multipoint connection; manage switch ports;\n request configuration information; and request statistics.\n\nNewman, et. al. Informational [Page 1]\n\f\nRFC 1987 GSMP Protocol Specification August 1996 1987 management path nested-reference unchanged"},{"id":"IETF RFC 1988","type":"specification","body":"IETF","designation":"RFC 1988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1988.txt","https://www.rfc-editor.org/rfc/rfc1988.pdf"],"folder":"IETF/RFC-1988","files":{"txt":{"path":"standards/IETF/RFC-1988/RFC-1988.txt","sha256":"393b7f641198c57d6369ff81d8a0b7ed2ac4f4cd4966f5b6d59e0dc76ca8d539"}},"tags":["nested-reference","unchanged"],"summary":"This grant is made to help facilitate inclusion of certain patented\n search address technology covering network device mapping in IETF\n standards-track Management Information Base (MIB) modules. HP is\n offering this search address technology to the IETF as a technique\n for mapping network devices. It should be noted that the\n confirmatory license mentioned is optional, since the grant of rights\n is automatic.","scope_keywords":["1988","license","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null}],"search_text":"IETF RFC 1988 This grant is made to help facilitate inclusion of certain patented\n search address technology covering network device mapping in IETF\n standards-track Management Information Base (MIB) modules. HP is\n offering this search address technology to the IETF as a technique\n for mapping network devices. It should be noted that the\n confirmatory license mentioned is optional, since the grant of rights\n is automatic. 1988 license management nested-reference unchanged"},{"id":"IETF RFC 1989","type":"specification","body":"IETF","designation":"RFC 1989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc1989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc1989.txt","https://www.rfc-editor.org/rfc/rfc1989.pdf"],"folder":"IETF/RFC-1989","files":{"txt":{"path":"standards/IETF/RFC-1989/RFC-1989.txt","sha256":"719794dc42c515d952ada2933fc0095a8cce06876f22a00268321f42f04a4a76"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of a Quality Protocol for continuous monitoring of the\n viability of the link.\n\n This document defines a protocol for generating Link-Quality-Reports.","scope_keywords":["1989","authentication","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 1989 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links.\n\n PPP also defines an extensible Link Control Protocol, which allows\n negotiation of a Quality Protocol for continuous monitoring of the\n viability of the link.\n\n This document defines a protocol for generating Link-Quality-Reports. 1989 authentication policies policy nested-reference unchanged"},{"id":"IETF RFC 3337","type":"specification","body":"IETF","designation":"RFC 3337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3337.txt","https://www.rfc-editor.org/rfc/rfc3337.pdf"],"folder":"IETF/RFC-3337","files":{"txt":{"path":"standards/IETF/RFC-3337/RFC-3337.txt","sha256":"6aa7902c09b935fdca607fcc630ef36a375ddf97650dd333eb3c59926ef0f127"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) over Asynchronous Transfer Mode\n (ATM) Adaptation Layer 2 defines the encapsulation that allows a PPP\n session to be transported over an ATM virtual circuit using the ATM\n Adaptation Layer 2 (AAL2) adaptation layer. This document defines a\n set of class extensions to PPP over AAL2 that implement equivalent\n functionality to Multi Class Multi Link PPP over a single ATM virtual\n circuit. Instead of using Multi Link PPP as the basis for\n fragmentation functionality, this document uses the functionality of\n the Segmentation and Reassembly Service Specific Convergence Sublayer\n that is already required as the basic encapsulation format of PPP\n over AAL2.\n\n1. Introduction\n\n Using AAL2 as an adaptation layer for PPP transport over ATM provides\n a bandwidth efficient transport for IP applications that generate\n small packets. An example IP application that gener","scope_keywords":["3337","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null}],"search_text":"IETF RFC 3337 The Point-to-Point Protocol (PPP) over Asynchronous Transfer Mode\n (ATM) Adaptation Layer 2 defines the encapsulation that allows a PPP\n session to be transported over an ATM virtual circuit using the ATM\n Adaptation Layer 2 (AAL2) adaptation layer. This document defines a\n set of class extensions to PPP over AAL2 that implement equivalent\n functionality to Multi Class Multi Link PPP over a single ATM virtual\n circuit. Instead of using Multi Link PPP as the basis for\n fragmentation functionality, this document uses the functionality of\n the Segmentation and Reassembly Service Specific Convergence Sublayer\n that is already required as the basic encapsulation format of PPP\n over AAL2.\n\n1. Introduction\n\n Using AAL2 as an adaptation layer for PPP transport over ATM provides\n a bandwidth efficient transport for IP applications that generate\n small packets. An example IP application that gener 3337 key nested-reference unchanged"},{"id":"IETF RFC 5703","type":"specification","body":"IETF","designation":"RFC 5703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5703.txt","https://www.rfc-editor.org/rfc/rfc5703.pdf"],"folder":"IETF/RFC-5703","files":{"txt":{"path":"standards/IETF/RFC-5703/RFC-5703.txt","sha256":"0eeeffbb3e67520be82e4435ba5cb83e47f07c4ea0751bba23401ac2d0ab7bea"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to the Sieve email filtering\n language to permit analysis and manipulation of the MIME body parts\n of an email message.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe yo","scope_keywords":["5703","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5703 This document defines extensions to the Sieve email filtering\n language to permit analysis and manipulation of the MIME body parts\n of an email message.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe yo 5703 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 4590","type":"specification","body":"IETF","designation":"RFC 4590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4590.txt","https://www.rfc-editor.org/rfc/rfc4590.pdf"],"folder":"IETF/RFC-4590","files":{"txt":{"path":"standards/IETF/RFC-4590/RFC-4590.txt","sha256":"3736aec80467fad7ef1871883e84eead3d862790488a7f8eb587076513b48341"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Remote Authentication\n Dial-In User Service (RADIUS) protocol to enable support of Digest\n Authentication, for use with HTTP-style protocols like the Session\n Initiation Protocol (SIP) and HTTP.","scope_keywords":["4590","algorithm","attribute","attributes","authentication","authorization","credential","encryption","hash","http","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null}],"search_text":"IETF RFC 4590 This document defines an extension to the Remote Authentication\n Dial-In User Service (RADIUS) protocol to enable support of Digest\n Authentication, for use with HTTP-style protocols like the Session\n Initiation Protocol (SIP) and HTTP. 4590 algorithm attribute attributes authentication authorization credential encryption hash http key tls nested-reference unchanged"},{"id":"IETF RFC 5090","type":"specification","body":"IETF","designation":"RFC 5090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5090.txt","https://www.rfc-editor.org/rfc/rfc5090.pdf"],"folder":"IETF/RFC-5090","files":{"txt":{"path":"standards/IETF/RFC-5090/RFC-5090.txt","sha256":"afbb4c237d5e99fc9ad9bfc05a22933fcdda7e291b90d7f808d01847233bd7ae"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Remote Authentication\n Dial-In User Service (RADIUS) protocol to enable support of Digest\n Authentication, for use with HTTP-style protocols like the Session\n Initiation Protocol (SIP) and HTTP.\n\nSterman, et al. Standards Track [Page 1]\n\f\nRFC 5090 RADIUS Extension Digest Authentication February 2008","scope_keywords":["5090","algorithm","attribute","attributes","authentication","authorization","encryption","hash","http","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 5090 This document defines an extension to the Remote Authentication\n Dial-In User Service (RADIUS) protocol to enable support of Digest\n Authentication, for use with HTTP-style protocols like the Session\n Initiation Protocol (SIP) and HTTP.\n\nSterman, et al. Standards Track [Page 1]\n\f\nRFC 5090 RADIUS Extension Digest Authentication February 2008 5090 algorithm attribute attributes authentication authorization encryption hash http key tls nested-reference unchanged"},{"id":"IETF RFC 5619","type":"specification","body":"IETF","designation":"RFC 5619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5619.txt","https://www.rfc-editor.org/rfc/rfc5619.pdf"],"folder":"IETF/RFC-5619","files":{"txt":{"path":"standards/IETF/RFC-5619/RFC-5619.txt","sha256":"03ee7b1dd4d303ba402c65f8924f83932c74646fe32fd54e157ba7944d009a79"}},"tags":["nested-reference","unchanged"],"summary":"This document describes security guidelines for the softwire \"Hubs\n and Spokes\" and \"Mesh\" solutions. Together with discussion of the\n softwire deployment scenarios, the vulnerability to security attacks\n is analyzed to provide security protection mechanisms such as\n authentication, integrity, and confidentiality to the softwire\n control and data packets.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Interne","scope_keywords":["5619","authentication","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null}],"search_text":"IETF RFC 5619 This document describes security guidelines for the softwire \"Hubs\n and Spokes\" and \"Mesh\" solutions. Together with discussion of the\n softwire deployment scenarios, the vulnerability to security attacks\n is analyzed to provide security protection mechanisms such as\n authentication, integrity, and confidentiality to the softwire\n control and data packets.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Interne 5619 authentication http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 3704","type":"specification","body":"IETF","designation":"RFC 3704","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3704.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3704.txt","https://www.rfc-editor.org/rfc/rfc3704.pdf"],"folder":"IETF/RFC-3704","files":{"txt":{"path":"standards/IETF/RFC-3704/RFC-3704.txt","sha256":"79aadfe01455bcb96b1663b0bd299c93649f12e623e20105ee0810839a128f89"}},"tags":["nested-reference","unchanged"],"summary":"BCP 38, RFC 2827, is designed to limit the impact of distributed\n denial of service attacks, by denying traffic with spoofed addresses\n access to the network, and to help ensure that traffic is traceable\n to its correct source network. As a side effect of protecting the\n Internet against such attacks, the network implementing the solution\n also protects itself from this and other attacks, such as spoofed\n management access to networking equipment. There are cases when this\n may create problems, e.g., with multihoming. This document describes\n the current ingress filtering operational mechanisms, examines\n generic issues related to ingress filtering, and delves into the\n effects on multihoming in particular. This memo updates RFC 2827.\n\nBaker & Savola Best Current Practice [Page 1]\n\f\nRFC 3704 Ingress Filtering for Multihomed Networks March 2004","scope_keywords":["3704","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4778","folder":"IETF/RFC-4778","source":"IETF/RFC-4778/RFC-4778.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4948","folder":"IETF/RFC-4948","source":"IETF/RFC-4948/RFC-4948.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5635","folder":"IETF/RFC-5635","source":"IETF/RFC-5635/RFC-5635.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 3704 BCP 38, RFC 2827, is designed to limit the impact of distributed\n denial of service attacks, by denying traffic with spoofed addresses\n access to the network, and to help ensure that traffic is traceable\n to its correct source network. As a side effect of protecting the\n Internet against such attacks, the network implementing the solution\n also protects itself from this and other attacks, such as spoofed\n management access to networking equipment. There are cases when this\n may create problems, e.g., with multihoming. This document describes\n the current ingress filtering operational mechanisms, examines\n generic issues related to ingress filtering, and delves into the\n effects on multihoming in particular. This memo updates RFC 2827.\n\nBaker & Savola Best Current Practice [Page 1]\n\f\nRFC 3704 Ingress Filtering for Multihomed Networks March 2004 3704 management path nested-reference unchanged"},{"id":"IETF RFC 3765","type":"specification","body":"IETF","designation":"RFC 3765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3765.txt","https://www.rfc-editor.org/rfc/rfc3765.pdf"],"folder":"IETF/RFC-3765","files":{"txt":{"path":"standards/IETF/RFC-3765/RFC-3765.txt","sha256":"8bc7910e43baf5cfd4a057ff5d0e16f0a1642b5b46753be5ba7fd2db56470698"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of a scope control Border Gateway\n Protocol (BGP) community. This well-known advisory transitive\n community allows an origin AS to specify the extent to which a\n specific route should be externally propagated. In particular this\n community, NOPEER, allows an origin AS to specify that a route with\n this attribute need not be advertised across bilateral peer\n connections.\n\n1. Introduction\n\n BGP today has a limited number of commonly defined mechanisms that\n allow a route to be propagated across some subset of the routing\n system. The NOEXPORT community allows a BGP speaker to specify that\n redistribution should extend only to the neighbouring AS. Providers\n commonly define a number of communities that allow their neighbours\n to specify how advertised routes should be re-advertised. Current\n operational practice is that such communities are defined on as AS b","scope_keywords":["3765","attribute","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null}],"search_text":"IETF RFC 3765 This document describes the use of a scope control Border Gateway\n Protocol (BGP) community. This well-known advisory transitive\n community allows an origin AS to specify the extent to which a\n specific route should be externally propagated. In particular this\n community, NOPEER, allows an origin AS to specify that a route with\n this attribute need not be advertised across bilateral peer\n connections.\n\n1. Introduction\n\n BGP today has a limited number of commonly defined mechanisms that\n allow a route to be propagated across some subset of the routing\n system. The NOEXPORT community allows a BGP speaker to specify that\n redistribution should extend only to the neighbouring AS. Providers\n commonly define a number of communities that allow their neighbours\n to specify how advertised routes should be re-advertised. Current\n operational practice is that such communities are defined on as AS b 3765 attribute path policy nested-reference unchanged"},{"id":"IETF RFC 4360","type":"specification","body":"IETF","designation":"RFC 4360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4360.txt","https://www.rfc-editor.org/rfc/rfc4360.pdf"],"folder":"IETF/RFC-4360","files":{"txt":{"path":"standards/IETF/RFC-4360/RFC-4360.txt","sha256":"20445ca696e3cba92fbe004ad0fb278b85880eaaad652557151ebb40706bccb4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"extended community\" BGP-4 attribute.\n This attribute provides a mechanism for labeling information carried\n in BGP-4. These labels can be used to control the distribution of\n this information, or for other applications.\n\n1. Introduction\n\n The Extended Community Attribute provides a mechanism for labeling\n information carried in BGP-4 [BGP-4]. It provides two important\n enhancements over the existing BGP Community Attribute [RFC1997]:\n\n - An extended range, ensuring that communities can be assigned for\n a plethora of uses, without fear of overlap.\n\n - The addition of a Type field provides structure for the\n community space.\n\n The addition of structure allows the usage of policy based on the\n application for which the community value will be used. For example,\n one can filter out all communities of a particular type, or allow\n only certain values for a particul","scope_keywords":["4360","attribute","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4384","folder":"IETF/RFC-4384","source":"IETF/RFC-4384/RFC-4384.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4659","folder":"IETF/RFC-4659","source":"IETF/RFC-4659/RFC-4659.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5668","folder":"IETF/RFC-5668","source":"IETF/RFC-5668/RFC-5668.txt","version":null},{"body":"IETF","designation":"RFC 5701","folder":"IETF/RFC-5701","source":"IETF/RFC-5701/RFC-5701.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 4360 This document describes the \"extended community\" BGP-4 attribute.\n This attribute provides a mechanism for labeling information carried\n in BGP-4. These labels can be used to control the distribution of\n this information, or for other applications.\n\n1. Introduction\n\n The Extended Community Attribute provides a mechanism for labeling\n information carried in BGP-4 [BGP-4]. It provides two important\n enhancements over the existing BGP Community Attribute [RFC1997]:\n\n - An extended range, ensuring that communities can be assigned for\n a plethora of uses, without fear of overlap.\n\n - The addition of a Type field provides structure for the\n community space.\n\n The addition of structure allows the usage of policy based on the\n application for which the community value will be used. For example,\n one can filter out all communities of a particular type, or allow\n only certain values for a particul 4360 attribute key policy nested-reference unchanged"},{"id":"IETF RFC 4893","type":"specification","body":"IETF","designation":"RFC 4893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4893.txt","https://www.rfc-editor.org/rfc/rfc4893.pdf"],"folder":"IETF/RFC-4893","files":{"txt":{"path":"standards/IETF/RFC-4893/RFC-4893.txt","sha256":"b67445783940ab20f5cfc939aa565e64739311e23b949a85cec4ea1edde5a1c5"}},"tags":["nested-reference","unchanged"],"summary":"Currently the Autonomous System (AS) number is encoded as a two-octet\n entity in BGP. This document describes extensions to BGP to carry the\n Autonomous System number as a four-octet entity.\n\n1. Introduction\n\n Currently the Autonomous System number is encoded as a two-octet\n entity in BGP [BGP]. To prepare for the anticipated exhaustion of\n the two-octet AS numbers, this document describes extensions to BGP\n to carry the Autonomous System number as a four-octet entity.\n\n More specifically, this document defines a new BGP capability, Four-\n octet AS Number Capability, that can be used by a BGP speaker to\n indicate its support for the four-octet AS numbers. Two new\n attributes, AS4_PATH and AS4_AGGREGATOR, are introduced that can be\n used to propagate four-octet based AS path information across BGP\n speakers that do not support the four-octet AS numbers. This\n document also specifies mecha","scope_keywords":["4893","attribute","attributes","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5668","folder":"IETF/RFC-5668","source":"IETF/RFC-5668/RFC-5668.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null}],"search_text":"IETF RFC 4893 Currently the Autonomous System (AS) number is encoded as a two-octet\n entity in BGP. This document describes extensions to BGP to carry the\n Autonomous System number as a four-octet entity.\n\n1. Introduction\n\n Currently the Autonomous System number is encoded as a two-octet\n entity in BGP [BGP]. To prepare for the anticipated exhaustion of\n the two-octet AS numbers, this document describes extensions to BGP\n to carry the Autonomous System number as a four-octet entity.\n\n More specifically, this document defines a new BGP capability, Four-\n octet AS Number Capability, that can be used by a BGP speaker to\n indicate its support for the four-octet AS numbers. Two new\n attributes, AS4_PATH and AS4_AGGREGATOR, are introduced that can be\n used to propagate four-octet based AS path information across BGP\n speakers that do not support the four-octet AS numbers. This\n document also specifies mecha 4893 attribute attributes key path trust nested-reference unchanged"},{"id":"IETF RFC 6514","type":"specification","body":"IETF","designation":"RFC 6514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6514.txt","https://www.rfc-editor.org/rfc/rfc6514.pdf"],"folder":"IETF/RFC-6514","files":{"txt":{"path":"standards/IETF/RFC-6514/RFC-6514.txt","sha256":"1ce1c62f4fa54b9b5b5ecb1bb8e0be9afa7672a3ac2a934869227513a08061ad"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the BGP encodings and procedures for\n exchanging the information elements required by Multicast in MPLS/BGP\n IP VPNs, as specified in RFC 6513.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6514.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the","scope_keywords":["6514","attribute","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null}],"search_text":"IETF RFC 6514 This document describes the BGP encodings and procedures for\n exchanging the information elements required by Multicast in MPLS/BGP\n IP VPNs, as specified in RFC 6513.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6514.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the 6514 attribute http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6793","type":"specification","body":"IETF","designation":"RFC 6793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6793.txt","https://www.rfc-editor.org/rfc/rfc6793.pdf"],"folder":"IETF/RFC-6793","files":{"txt":{"path":"standards/IETF/RFC-6793/RFC-6793.txt","sha256":"7c9c157b581bc80c88743d851c25f3c489458c8023a462dbdd188e22381a6e16"}},"tags":["nested-reference","unchanged"],"summary":"The Autonomous System number is encoded as a two-octet entity in the\n base BGP specification. This document describes extensions to BGP to\n carry the Autonomous System numbers as four-octet entities. This\n document obsoletes RFC 4893 and updates RFC 4271.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6793.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as ","scope_keywords":["6793","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null}],"search_text":"IETF RFC 6793 The Autonomous System number is encoded as a two-octet entity in the\n base BGP specification. This document describes extensions to BGP to\n carry the Autonomous System numbers as four-octet entities. This\n document obsoletes RFC 4893 and updates RFC 4271.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6793.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as  6793 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7117","type":"specification","body":"IETF","designation":"RFC 7117","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7117.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7117.txt","https://www.rfc-editor.org/rfc/rfc7117.pdf"],"folder":"IETF/RFC-7117","files":{"txt":{"path":"standards/IETF/RFC-7117/RFC-7117.txt","sha256":"ff1e0bd8c4a7b09c8889f93279336b559da6237d68fd5b0df5766d9d368a57c8"}},"tags":["nested-reference","unchanged"],"summary":"RFCs 4761 and 4762 describe a solution for Virtual Private LAN\n Service (VPLS) multicast that relies on the use of point-to-point or\n multipoint-to-point unicast Label Switched Paths (LSPs) for carrying\n multicast traffic. This solution has certain limitations for certain\n VPLS multicast traffic profiles. For example, it may result in\n highly non-optimal bandwidth utilization when a large amount of\n multicast traffic is to be transported.\n\n This document describes solutions for overcoming a subset of the\n limitations of the existing VPLS multicast solution. It describes\n procedures for VPLS multicast that utilize multicast trees in the\n service provider (SP) network. The solution described in this\n document allows sharing of one such multicast tree among multiple\n VPLS instances. Furthermore, the solution described in this document\n allows a single multicast tree in the SP network to car","scope_keywords":["7117","http","license","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 7117 RFCs 4761 and 4762 describe a solution for Virtual Private LAN\n Service (VPLS) multicast that relies on the use of point-to-point or\n multipoint-to-point unicast Label Switched Paths (LSPs) for carrying\n multicast traffic. This solution has certain limitations for certain\n VPLS multicast traffic profiles. For example, it may result in\n highly non-optimal bandwidth utilization when a large amount of\n multicast traffic is to be transported.\n\n This document describes solutions for overcoming a subset of the\n limitations of the existing VPLS multicast solution. It describes\n procedures for VPLS multicast that utilize multicast trees in the\n service provider (SP) network. The solution described in this\n document allows sharing of one such multicast tree among multiple\n VPLS instances. Furthermore, the solution described in this document\n allows a single multicast tree in the SP network to car 7117 http license path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7606","type":"specification","body":"IETF","designation":"RFC 7606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7606.txt","https://www.rfc-editor.org/rfc/rfc7606.pdf"],"folder":"IETF/RFC-7606","files":{"txt":{"path":"standards/IETF/RFC-7606/RFC-7606.txt","sha256":"18c3ef90bc78fc74dfea08ad951c1be097047335a6299a7820d9f8ec30199f58"}},"tags":["nested-reference","unchanged"],"summary":"According to the base BGP specification, a BGP speaker that receives\n an UPDATE message containing a malformed attribute is required to\n reset the session over which the offending attribute was received.\n This behavior is undesirable because a session reset would impact not\n only routes with the offending attribute but also other valid routes\n exchanged over the session. This document partially revises the\n error handling for UPDATE messages and provides guidelines for the\n authors of documents defining new attributes. Finally, it revises\n the error handling procedures for a number of existing attributes.\n\n This document updates error handling for RFCs 1997, 4271, 4360, 4456,\n 4760, 5543, 5701, and 6368.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF ","scope_keywords":["7606","attribute","attributes","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 7606 According to the base BGP specification, a BGP speaker that receives\n an UPDATE message containing a malformed attribute is required to\n reset the session over which the offending attribute was received.\n This behavior is undesirable because a session reset would impact not\n only routes with the offending attribute but also other valid routes\n exchanged over the session. This document partially revises the\n error handling for UPDATE messages and provides guidelines for the\n authors of documents defining new attributes. Finally, it revises\n the error handling procedures for a number of existing attributes.\n\n This document updates error handling for RFCs 1997, 4271, 4360, 4456,\n 4760, 5543, 5701, and 6368.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF  7606 attribute attributes http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 2582","type":"specification","body":"IETF","designation":"RFC 2582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2582.txt","https://www.rfc-editor.org/rfc/rfc2582.pdf"],"folder":"IETF/RFC-2582","files":{"txt":{"path":"standards/IETF/RFC-2582/RFC-2582.txt","sha256":"efd51a46acdd7ae1cc383fa501c4978277ce80cbe0c78d0c33d806ac480525dc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Floyd\nRequest for Comments: 2582 ACIRI\nCategory: Experimental T. Henderson\n U.C. Berkeley\n April 1999\n\n The NewReno Modification to TCP's Fast Recovery Algorithm\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n RFC 2001 [RFC2001] documents the following four intertwined TCP\n congestion control algorithms: Slow Start, Congestion Avoidance, Fast\n Retransmit, and Fast Recovery. RFC 2581 [RFC2581] explicitly allows\n certain modifications of these algorithms, including modifications\n that use the TCP Selective Acknowledgement (SACK) option [MMFR96],\n and modifications that resp","scope_keywords":["2582","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3649","folder":"IETF/RFC-3649","source":"IETF/RFC-3649/RFC-3649.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2582 Network Working Group S. Floyd\nRequest for Comments: 2582 ACIRI\nCategory: Experimental T. Henderson\n U.C. Berkeley\n April 1999\n\n The NewReno Modification to TCP's Fast Recovery Algorithm\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n RFC 2001 [RFC2001] documents the following four intertwined TCP\n congestion control algorithms: Slow Start, Congestion Avoidance, Fast\n Retransmit, and Fast Recovery. RFC 2581 [RFC2581] explicitly allows\n certain modifications of these algorithms, including modifications\n that use the TCP Selective Acknowledgement (SACK) option [MMFR96],\n and modifications that resp 2582 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 2794","type":"specification","body":"IETF","designation":"RFC 2794","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2794.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2794.txt","https://www.rfc-editor.org/rfc/rfc2794.pdf"],"folder":"IETF/RFC-2794","files":{"txt":{"path":"standards/IETF/RFC-2794/RFC-2794.txt","sha256":"12edb3701195e6fc051e9d56f899d347b6579139ed444c2739ef1e3bbbd340b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Calhoun\nRequest for Comments: 2794 Sun Microsystems Laboratories\nUpdates: 2290 C. Perkins\nCategory: Standards Track Nokia Research Center\n March 2000\n\n Mobile IP Network Access Identifier Extension for IPv4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n AAA servers are in use within the Internet today to provide\n authentication and authorization services for dial-up computers.\n Such services are likely to be equally valuable for mobile nodes\n using Mobile IP ","scope_keywords":["2794","authentication","authorization","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null}],"search_text":"IETF RFC 2794 Network Working Group P. Calhoun\nRequest for Comments: 2794 Sun Microsystems Laboratories\nUpdates: 2290 C. Perkins\nCategory: Standards Track Nokia Research Center\n March 2000\n\n Mobile IP Network Access Identifier Extension for IPv4\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n AAA servers are in use within the Internet today to provide\n authentication and authorization services for dial-up computers.\n Such services are likely to be equally valuable for mobile nodes\n using Mobile IP  2794 authentication authorization identification key nested-reference unchanged"},{"id":"IETF RFC 2904","type":"specification","body":"IETF","designation":"RFC 2904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2904.txt","https://www.rfc-editor.org/rfc/rfc2904.pdf"],"folder":"IETF/RFC-2904","files":{"txt":{"path":"standards/IETF/RFC-2904/RFC-2904.txt","sha256":"802ad25d792aa2968c48a7cde189a1aff23f9b59b350d6d4531da876b709a205"}},"tags":["nested-reference","unchanged"],"summary":"This memo serves as the base requirements for Authorization of\n Internet Resources and Services (AIRS). It presents an architectural\n framework for understanding the authorization of Internet resources\n and services and derives requirements for authorization protocols.\n\nVollbrecht, et al. Informational [Page 1]\n\f\nRFC 2904 AAA Authorization Framework August 2000","scope_keywords":["2904","attribute","audit","authentication","authorization","certificate","certificates","delivery","management","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2903","folder":"IETF/RFC-2903","source":"IETF/RFC-2903/RFC-2903.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null}],"search_text":"IETF RFC 2904 This memo serves as the base requirements for Authorization of\n Internet Resources and Services (AIRS). It presents an architectural\n framework for understanding the authorization of Internet resources\n and services and derives requirements for authorization protocols.\n\nVollbrecht, et al. Informational [Page 1]\n\f\nRFC 2904 AAA Authorization Framework August 2000 2904 attribute audit authentication authorization certificate certificates delivery management policy trust nested-reference unchanged"},{"id":"IETF RFC 2905","type":"specification","body":"IETF","designation":"RFC 2905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2905.txt","https://www.rfc-editor.org/rfc/rfc2905.pdf"],"folder":"IETF/RFC-2905","files":{"txt":{"path":"standards/IETF/RFC-2905/RFC-2905.txt","sha256":"86c8eea4efe30fbe8f31202bc9f394f367255d6d7aa0b637260b88109b9bdfb1"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes several examples of applications requiring\n authorization. Each application is described in terms of a\n consistent framework, and specific authorization requirements of each\n application are given. This material was not contributed by the\n working groups responsible for the applications and should not be\n considered prescriptive for how the applications will meet their\n authorization needs. Rather the intent is to explore the fundamental\n needs of a variety of different applications with the view of\n compiling a set of requirements that an authorization protocol will\n need to meet in order to be generally useful.\n\nVollbrecht, et al. Informational [Page 1]\n\f\nRFC 2905 AAA Authorization Application Examples August 2000","scope_keywords":["2905","attribute","authorization","certificate","certificates","identification","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2903","folder":"IETF/RFC-2903","source":"IETF/RFC-2903/RFC-2903.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null}],"search_text":"IETF RFC 2905 This memo describes several examples of applications requiring\n authorization. Each application is described in terms of a\n consistent framework, and specific authorization requirements of each\n application are given. This material was not contributed by the\n working groups responsible for the applications and should not be\n considered prescriptive for how the applications will meet their\n authorization needs. Rather the intent is to explore the fundamental\n needs of a variety of different applications with the view of\n compiling a set of requirements that an authorization protocol will\n need to meet in order to be generally useful.\n\nVollbrecht, et al. Informational [Page 1]\n\f\nRFC 2905 AAA Authorization Application Examples August 2000 2905 attribute authorization certificate certificates identification key trust nested-reference unchanged"},{"id":"IETF RFC 3141","type":"specification","body":"IETF","designation":"RFC 3141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3141.txt","https://www.rfc-editor.org/rfc/rfc3141.pdf"],"folder":"IETF/RFC-3141","files":{"txt":{"path":"standards/IETF/RFC-3141/RFC-3141.txt","sha256":"71986074314f67c0182390945ff14d0d92ba509c17288d359d014c4da8dda298"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies cdma2000 wireless data AAA (Authentication,\n Authorization, Accounting) requirements associated with third\n generation wireless architecture that supports roaming among service\n providers for traditional PPP and Mobile IP services.\n\nHiller, et al. Informational [Page 1]\n\f\nRFC 3141 CDMA2000 Wireless Data Requirements June 2001\n\n1. Introduction\n\n The architecture is designed for use with a cellular network as an\n access medium. Sections 1, 2, present a brief high level review of\n the cdma2000 wireless data architecture. Section 3 presents cdma2000\n AAA requirements.\n\n This document specifies AAA requirements associated with a third\n generation cdma2000 wireless architecture that supports roaming among\n service providers for traditional PPP and Mobile IP services. The\n architecture is designed for use with a cellular network as an access\n medium.\n\n Sections 1 and 2 prese","scope_keywords":["3141","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null}],"search_text":"IETF RFC 3141 This memo specifies cdma2000 wireless data AAA (Authentication,\n Authorization, Accounting) requirements associated with third\n generation wireless architecture that supports roaming among service\n providers for traditional PPP and Mobile IP services.\n\nHiller, et al. Informational [Page 1]\n\f\nRFC 3141 CDMA2000 Wireless Data Requirements June 2001\n\n1. Introduction\n\n The architecture is designed for use with a cellular network as an\n access medium. Sections 1, 2, present a brief high level review of\n the cdma2000 wireless data architecture. Section 3 presents cdma2000\n AAA requirements.\n\n This document specifies AAA requirements associated with a third\n generation cdma2000 wireless architecture that supports roaming among\n service providers for traditional PPP and Mobile IP services. The\n architecture is designed for use with a cellular network as an access\n medium.\n\n Sections 1 and 2 prese 3141 authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 3334","type":"specification","body":"IETF","designation":"RFC 3334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3334.txt","https://www.rfc-editor.org/rfc/rfc3334.pdf"],"folder":"IETF/RFC-3334","files":{"txt":{"path":"standards/IETF/RFC-3334/RFC-3334.txt","sha256":"8b1684925162719b7966c1bdf5433c61d6c646d82cbd5a543ca298b26d55c02b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes policy-based accounting which is an approach\n to provide flexibility to accounting architectures. Accounting\n policies describe the configuration of an accounting architecture in\n a standardized way. They are used to instrument the accounting\n architecture and can be exchanged between Authentication,\n Authorization and Accounting (AAA) entities in order to share\n configuration information.\n\n This document describes building blocks and message sequences for\n policy-based accounting in the generic AAA architecture (RFC 2903).\n Examples are given for the usage of accounting policies in different\n scenarios. It is also shown how accounting components can be\n integrated into the AAA authorization framework (RFC 2904). This\n document does not propose a language for the description of\n accounting policies. Rather, it is assumed that a suitable policy\n language can be cho","scope_keywords":["3334","authentication","authorization","policies","policy","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null}],"search_text":"IETF RFC 3334 This document describes policy-based accounting which is an approach\n to provide flexibility to accounting architectures. Accounting\n policies describe the configuration of an accounting architecture in\n a standardized way. They are used to instrument the accounting\n architecture and can be exchanged between Authentication,\n Authorization and Accounting (AAA) entities in order to share\n configuration information.\n\n This document describes building blocks and message sequences for\n policy-based accounting in the generic AAA architecture (RFC 2903).\n Examples are given for the usage of accounting policies in different\n scenarios. It is also shown how accounting components can be\n integrated into the AAA authorization framework (RFC 2904). This\n document does not propose a language for the description of\n accounting policies. Rather, it is assumed that a suitable policy\n language can be cho 3334 authentication authorization policies policy profile profiles nested-reference unchanged"},{"id":"IETF RFC 5512","type":"specification","body":"IETF","designation":"RFC 5512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5512.txt","https://www.rfc-editor.org/rfc/rfc5512.pdf"],"folder":"IETF/RFC-5512","files":{"txt":{"path":"standards/IETF/RFC-5512/RFC-5512.txt","sha256":"0bf165cded7f88ccc8f78bccc5b9915f0704c59f8e174a5bba77453229e69fd2"}},"tags":["nested-reference","unchanged"],"summary":"In certain situations, transporting a packet from one Border Gateway\n Protocol (BGP) speaker to another (the BGP next hop) requires that\n the packet be encapsulated by the first BGP speaker and decapsulated\n by the second. To support these situations, there needs to be some\n agreement between the two BGP speakers with regard to the\n \"encapsulation information\", i.e., the format of the encapsulation\n header as well as the contents of various fields of the header.\n\n The encapsulation information need not be signaled for all\n encapsulation types. In cases where signaling is required (such as\n Layer Two Tunneling Protocol - Version 3 (L2TPv3) or Generic Routing\n Encapsulation (GRE) with key), this document specifies a method by\n which BGP speakers can signal encapsulation information to each\n other. The signaling is done by sending BGP updates using the\n Encapsulation Subsequent Address Fami","scope_keywords":["5512","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5640","folder":"IETF/RFC-5640","source":"IETF/RFC-5640/RFC-5640.txt","version":null}],"search_text":"IETF RFC 5512 In certain situations, transporting a packet from one Border Gateway\n Protocol (BGP) speaker to another (the BGP next hop) requires that\n the packet be encapsulated by the first BGP speaker and decapsulated\n by the second. To support these situations, there needs to be some\n agreement between the two BGP speakers with regard to the\n \"encapsulation information\", i.e., the format of the encapsulation\n header as well as the contents of various fields of the header.\n\n The encapsulation information need not be signaled for all\n encapsulation types. In cases where signaling is required (such as\n Layer Two Tunneling Protocol - Version 3 (L2TPv3) or Generic Routing\n Encapsulation (GRE) with key), this document specifies a method by\n which BGP speakers can signal encapsulation information to each\n other. The signaling is done by sending BGP updates using the\n Encapsulation Subsequent Address Fami 5512 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5566","type":"specification","body":"IETF","designation":"RFC 5566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5566.txt","https://www.rfc-editor.org/rfc/rfc5566.pdf"],"folder":"IETF/RFC-5566","files":{"txt":{"path":"standards/IETF/RFC-5566/RFC-5566.txt","sha256":"155d0cdaa7a58051aa9382b82b72d9103be51a5aec632acb8e5c7a596ff88674"}},"tags":["nested-reference","unchanged"],"summary":"The BGP Encapsulation Subsequent Address Family Identifier (SAFI)\n provides a method for the dynamic exchange of encapsulation\n information and for the indication of encapsulation protocol types to\n be used for different next hops. Currently, support for Generic\n Routing Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TPv3), and\n IP in IP tunnel types are defined. This document defines support for\n IPsec tunnel types.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 5566 BGP IPsec Tunnel Encapsulation June 2009","scope_keywords":["5566","algorithm","algorithms","attribute","authentication","encryption","http","key","keys","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5566 The BGP Encapsulation Subsequent Address Family Identifier (SAFI)\n provides a method for the dynamic exchange of encapsulation\n information and for the indication of encapsulation protocol types to\n be used for different next hops. Currently, support for Generic\n Routing Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TPv3), and\n IP in IP tunnel types are defined. This document defines support for\n IPsec tunnel types.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 5566 BGP IPsec Tunnel Encapsulation June 2009 5566 algorithm algorithms attribute authentication encryption http key keys license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6040","type":"specification","body":"IETF","designation":"RFC 6040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6040.txt","https://www.rfc-editor.org/rfc/rfc6040.pdf"],"folder":"IETF/RFC-6040","files":{"txt":{"path":"standards/IETF/RFC-6040/RFC-6040.txt","sha256":"7ebf3e9833df42700e3651ae99499a74f1bd803a75c29656c2994900a31a96ca"}},"tags":["nested-reference","unchanged"],"summary":"This document redefines how the explicit congestion notification\n (ECN) field of the IP header should be constructed on entry to and\n exit from any IP-in-IP tunnel. On encapsulation, it updates RFC 3168\n to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301\n IPsec ECN processing. On decapsulation, it updates both RFC 3168 and\n RFC 4301 to add new behaviours for previously unused combinations of\n inner and outer headers. The new rules ensure the ECN field is\n correctly propagated across a tunnel whether it is used to signal one\n or two severity levels of congestion; whereas before, only one\n severity level was supported. Tunnel endpoints can be updated in any\n order without affecting pre-existing uses of the ECN field, thus\n ensuring backward compatibility. Nonetheless, operators wanting to\n support two severity levels (e.g., for pre-congestion notification --\n PCN) can require","scope_keywords":["6040","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 6040 This document redefines how the explicit congestion notification\n (ECN) field of the IP header should be constructed on entry to and\n exit from any IP-in-IP tunnel. On encapsulation, it updates RFC 3168\n to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301\n IPsec ECN processing. On decapsulation, it updates both RFC 3168 and\n RFC 4301 to add new behaviours for previously unused combinations of\n inner and outer headers. The new rules ensure the ECN field is\n correctly propagated across a tunnel whether it is used to signal one\n or two severity levels of congestion; whereas before, only one\n severity level was supported. Tunnel endpoints can be updated in any\n order without affecting pre-existing uses of the ECN field, thus\n ensuring backward compatibility. Nonetheless, operators wanting to\n support two severity levels (e.g., for pre-congestion notification --\n PCN) can require 6040 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6513","type":"specification","body":"IETF","designation":"RFC 6513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6513.txt","https://www.rfc-editor.org/rfc/rfc6513.pdf"],"folder":"IETF/RFC-6513","files":{"txt":{"path":"standards/IETF/RFC-6513/RFC-6513.txt","sha256":"5b32cb710590c6959e36a0ca110c1dd15fd13bd36dfd31a3a6451feb3a601de7"}},"tags":["nested-reference","unchanged"],"summary":"In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual\n Private Network) to travel from one VPN site to another, special\n protocols and procedures must be implemented by the VPN Service\n Provider. These protocols and procedures are specified in this\n document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6513.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the pers","scope_keywords":["6513","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 6513 In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual\n Private Network) to travel from one VPN site to another, special\n protocols and procedures must be implemented by the VPN Service\n Provider. These protocols and procedures are specified in this\n document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6513.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the pers 6513 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6576","type":"specification","body":"IETF","designation":"RFC 6576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6576.txt","https://www.rfc-editor.org/rfc/rfc6576.pdf"],"folder":"IETF/RFC-6576","files":{"txt":{"path":"standards/IETF/RFC-6576/RFC-6576.txt","sha256":"3fc93415d19c09fd8124aeca4d6033d347f4d7e14a14912e63c9fd663961389f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies tests to determine if multiple independent\n instantiations of a performance-metric RFC have implemented the\n specifications in the same way. This is the performance-metric\n equivalent of interoperability, required to advance RFCs along the\n Standards Track. Results from different implementations of metric\n RFCs will be collected under the same underlying network conditions\n and compared using statistical methods. The goal is an evaluation of\n the metric RFC itself to determine whether its definitions are clear\n and unambiguous to implementors and therefore a candidate for\n advancement on the IETF Standards Track. This document is an\n Internet Best Current Practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communi","scope_keywords":["6576","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 6576 This document specifies tests to determine if multiple independent\n instantiations of a performance-metric RFC have implemented the\n specifications in the same way. This is the performance-metric\n equivalent of interoperability, required to advance RFCs along the\n Standards Track. Results from different implementations of metric\n RFCs will be collected under the same underlying network conditions\n and compared using statistical methods. The goal is an evaluation of\n the metric RFC itself to determine whether its definitions are clear\n and unambiguous to implementors and therefore a candidate for\n advancement on the IETF Standards Track. This document is an\n Internet Best Current Practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communi 6576 http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8290","type":"specification","body":"IETF","designation":"RFC 8290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8290.txt","https://www.rfc-editor.org/rfc/rfc8290.pdf"],"folder":"IETF/RFC-8290","files":{"txt":{"path":"standards/IETF/RFC-8290/RFC-8290.txt","sha256":"2cff1a6148764d2b9dd5af8939261dce1e723fb8f6b3af64e96774b51a02a3aa"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents the FQ-CoDel hybrid packet scheduler and Active\n Queue Management (AQM) algorithm, a powerful tool for fighting\n bufferbloat and reducing latency.\n\n FQ-CoDel mixes packets from multiple flows and reduces the impact of\n head-of-line blocking from bursty traffic. It provides isolation for\n low-rate traffic such as DNS, web, and videoconferencing traffic. It\n improves utilisation across the networking fabric, especially for\n bidirectional traffic, by keeping queue lengths short, and it can be\n implemented in a memory- and CPU-efficient fashion across a wide\n range of hardware.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n","scope_keywords":["8290","algorithm","algorithms","hash","http","https","license","management","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null}],"search_text":"IETF RFC 8290 This memo presents the FQ-CoDel hybrid packet scheduler and Active\n Queue Management (AQM) algorithm, a powerful tool for fighting\n bufferbloat and reducing latency.\n\n FQ-CoDel mixes packets from multiple flows and reduces the impact of\n head-of-line blocking from bursty traffic. It provides isolation for\n low-rate traffic such as DNS, web, and videoconferencing traffic. It\n improves utilisation across the networking fabric, especially for\n bidirectional traffic, by keeping queue lengths short, and it can be\n implemented in a memory- and CPU-efficient fashion across a wide\n range of hardware.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n 8290 algorithm algorithms hash http https license management subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5454","type":"specification","body":"IETF","designation":"RFC 5454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5454.txt","https://www.rfc-editor.org/rfc/rfc5454.pdf"],"folder":"IETF/RFC-5454","files":{"txt":{"path":"standards/IETF/RFC-5454/RFC-5454.txt","sha256":"b790639038bf88f1cea24b5711597e42bdd709767754c8c01b6207c2fa40c454"}},"tags":["nested-reference","unchanged"],"summary":"This specification provides IPv6 extensions to the Mobile IPv4\n protocol. The extensions allow a dual-stack node to use IPv4 and\n IPv6 home addresses as well as to move between IPv4 and dual stack\n network infrastructures.\n\nTsirtsis, et al. Standards Track [Page 1]\n\f\nRFC 5454 Dual-Stack Mobile IPv4 March 2009","scope_keywords":["5454","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null}],"search_text":"IETF RFC 5454 This specification provides IPv6 extensions to the Mobile IPv4\n protocol. The extensions allow a dual-stack node to use IPv4 and\n IPv6 home addresses as well as to move between IPv4 and dual stack\n network infrastructures.\n\nTsirtsis, et al. Standards Track [Page 1]\n\f\nRFC 5454 Dual-Stack Mobile IPv4 March 2009 5454 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 2209","type":"specification","body":"IETF","designation":"RFC 2209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2209.txt","https://www.rfc-editor.org/rfc/rfc2209.pdf"],"folder":"IETF/RFC-2209","files":{"txt":{"path":"standards/IETF/RFC-2209/RFC-2209.txt","sha256":"603d66a592a7ce279b0b9cf3546ada2734e4315ace8ed5533c2d8a787818af34"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braden\nRequest For Comments: 2209 ISI\nCategory: Informational L. Zhang\n UCLA\n September 1997\n\n Resource ReSerVation Protocol (RSVP) --\n Version 1 Message Processing Rules\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nAbstract\n\n This memo contains an algorithmic description of the rules used by an\n RSVP implementation for processing messages. It is intended to\n clarify the version 1 RSVP protocol specification.\n\n This memo provides a generic description of the rules for the\n operation of Version 1 of RSVP [RFC 2205]. It is intended to outline\n a set of algorithms that will accomplish the needed function,\n omitting many details.\n\n1. GENERIC DATA STRUCTURES\n\n This memo assumes the generic interface calls defined in [RFC 2005]\n and the ","scope_keywords":["2209","algorithm","algorithms","path","policy","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2207","folder":"IETF/RFC-2207","source":"IETF/RFC-2207/RFC-2207.txt","version":null},{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2748","folder":"IETF/RFC-2748","source":"IETF/RFC-2748/RFC-2748.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 2209 Network Working Group R. Braden\nRequest For Comments: 2209 ISI\nCategory: Informational L. Zhang\n UCLA\n September 1997\n\n Resource ReSerVation Protocol (RSVP) --\n Version 1 Message Processing Rules\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nAbstract\n\n This memo contains an algorithmic description of the rules used by an\n RSVP implementation for processing messages. It is intended to\n clarify the version 1 RSVP protocol specification.\n\n This memo provides a generic description of the rules for the\n operation of Version 1 of RSVP [RFC 2205]. It is intended to outline\n a set of algorithms that will accomplish the needed function,\n omitting many details.\n\n1. GENERIC DATA STRUCTURES\n\n This memo assumes the generic interface calls defined in [RFC 2005]\n and the  2209 algorithm algorithms path policy tsp nested-reference unchanged"},{"id":"IETF RFC 2007","type":"specification","body":"IETF","designation":"RFC 2007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2007.txt","https://www.rfc-editor.org/rfc/rfc2007.pdf"],"folder":"IETF/RFC-2007","files":{"txt":{"path":"standards/IETF/RFC-2007/RFC-2007.txt","sha256":"49289b3b5603fb384c3b6c2b74db74a58012328e96cfe68100c3d4cc741002a6"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to provide a catalogue of quality\n Network Training Materials for use by Internet trainers in training\n their users. By providing such a collection of pointers to useful\n resources, it is hoped that trainers will be relieved of much of the\n load of producing current training materials.","scope_keywords":["2007","pid","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null}],"search_text":"IETF RFC 2007 The purpose of this document is to provide a catalogue of quality\n Network Training Materials for use by Internet trainers in training\n their users. By providing such a collection of pointers to useful\n resources, it is hoped that trainers will be relieved of much of the\n load of producing current training materials. 2007 pid presentation subject nested-reference unchanged"},{"id":"IETF RFC 3547","type":"specification","body":"IETF","designation":"RFC 3547","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3547.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3547.txt","https://www.rfc-editor.org/rfc/rfc3547.pdf"],"folder":"IETF/RFC-3547","files":{"txt":{"path":"standards/IETF/RFC-3547/RFC-3547.txt","sha256":"72467c595abceffc2983e55174f32883e1bf6a28569be3a88394ce8bb94100f3"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an ISAMKP Domain of Interpretation (DOI) for\n group key management to support secure group communications. The\n GDOI manages group security associations, which are used by IPSEC and\n potentially other data security protocols running at the IP or\n application layers. These security associations protect one or more\n key-encrypting keys, traffic-encrypting keys, or data shared by group\n members.","scope_keywords":["3547","algorithm","attribute","attributes","authentication","authorization","hash","identification","key","keys","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null}],"search_text":"IETF RFC 3547 This document presents an ISAMKP Domain of Interpretation (DOI) for\n group key management to support secure group communications. The\n GDOI manages group security associations, which are used by IPSEC and\n potentially other data security protocols running at the IP or\n application layers. These security associations protect one or more\n key-encrypting keys, traffic-encrypting keys, or data shared by group\n members. 3547 algorithm attribute attributes authentication authorization hash identification key keys management signature nested-reference unchanged"},{"id":"IETF RFC 2009","type":"specification","body":"IETF","designation":"RFC 2009","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2009.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2009.txt","https://www.rfc-editor.org/rfc/rfc2009.pdf"],"folder":"IETF/RFC-2009","files":{"txt":{"path":"standards/IETF/RFC-2009/RFC-2009.txt","sha256":"8ad42f759155db00464bdce9ab58696f707ac99f74dcce53ef3b21251c9bf050"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Imielinski\nRequest for Comments: 2009 J. Navas\nCategory: Experimental Rutgers University\n November 1996\n\n GPS-Based Addressing and Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIANA Note:\n\n This document describes a possible experiment with geographic\n addresses. It uses several specific IP addresses and domain names in\n the discussion as concrete examples to aid in understanding the\n concepts. Please note that these addresses and names are not\n registered, assigned, allocated, or delegated to the use suggested\n here.\n\nTable of Contents\n\n 1. Introduction...................................... 2\n 1b. General Architecture...................... 3\n 1c. ","scope_keywords":["2009","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2009 Network Working Group T. Imielinski\nRequest for Comments: 2009 J. Navas\nCategory: Experimental Rutgers University\n November 1996\n\n GPS-Based Addressing and Routing\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nIANA Note:\n\n This document describes a possible experiment with geographic\n addresses. It uses several specific IP addresses and domain names in\n the discussion as concrete examples to aid in understanding the\n concepts. Please note that these addresses and names are not\n registered, assigned, allocated, or delegated to the use suggested\n here.\n\nTable of Contents\n\n 1. Introduction...................................... 2\n 1b. General Architecture...................... 3\n 1c.  2009 management registered nested-reference unchanged"},{"id":"IETF RFC 5743","type":"specification","body":"IETF","designation":"RFC 5743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5743.txt","https://www.rfc-editor.org/rfc/rfc5743.pdf"],"folder":"IETF/RFC-5743","files":{"txt":{"path":"standards/IETF/RFC-5743/RFC-5743.txt","sha256":"f64f7d374f38479809eb476818543ee936fa646c768c1a0dc6eeb9def17b2e4e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the publication stream for RFCs from the Internet\n Research Task Force. Most documents undergoing this process will\n come from IRTF Research Groups, and it is expected that they will be\n published as Informational or Experimental RFCs by the RFC Editor.\n\nStatus of this Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. Documents approved for publication by the IRSG are not a\n candidate for any level of Internet Standard; see Section 2 of RFC\n 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or","scope_keywords":["5743","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null}],"search_text":"IETF RFC 5743 This memo defines the publication stream for RFCs from the Internet\n Research Task Force. Most documents undergoing this process will\n come from IRTF Research Groups, and it is expected that they will be\n published as Informational or Experimental RFCs by the RFC Editor.\n\nStatus of this Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. Documents approved for publication by the IRSG are not a\n candidate for any level of Internet Standard; see Section 2 of RFC\n 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or 5743 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 4954","type":"specification","body":"IETF","designation":"RFC 4954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4954.txt","https://www.rfc-editor.org/rfc/rfc4954.pdf"],"folder":"IETF/RFC-4954","files":{"txt":{"path":"standards/IETF/RFC-4954/RFC-4954.txt","sha256":"6bf118f556749d08d1bfae92cefbdebf6084324ceba262a87af1efbe0e16d50a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Simple Mail Transport Protocol (SMTP)\n extension whereby an SMTP client may indicate an authentication\n mechanism to the server, perform an authentication protocol exchange,\n and optionally negotiate a security layer for subsequent protocol\n interactions during this session. This extension includes a profile\n of the Simple Authentication and Security Layer (SASL) for SMTP.\n\n This document obsoletes RFC 2554.\n\nSiemborski & Melnikov Standards Track [Page 1]\n\f\nRFC 4954 SMTP Service Extension for Authentication July 2007","scope_keywords":["4954","authentication","authorization","delivery","encryption","key","profile","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5248","folder":"IETF/RFC-5248","source":"IETF/RFC-5248/RFC-5248.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null}],"search_text":"IETF RFC 4954 This document defines a Simple Mail Transport Protocol (SMTP)\n extension whereby an SMTP client may indicate an authentication\n mechanism to the server, perform an authentication protocol exchange,\n and optionally negotiate a security layer for subsequent protocol\n interactions during this session. This extension includes a profile\n of the Simple Authentication and Security Layer (SASL) for SMTP.\n\n This document obsoletes RFC 2554.\n\nSiemborski & Melnikov Standards Track [Page 1]\n\f\nRFC 4954 SMTP Service Extension for Authentication July 2007 4954 authentication authorization delivery encryption key profile tls trust nested-reference unchanged"},{"id":"IETF RFC 2884","type":"specification","body":"IETF","designation":"RFC 2884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2884.txt","https://www.rfc-editor.org/rfc/rfc2884.pdf"],"folder":"IETF/RFC-2884","files":{"txt":{"path":"standards/IETF/RFC-2884/RFC-2884.txt","sha256":"63a0136de5df8aaae17f03a94cef3f2c6db52576e2677687e34fa9eb66e86fe0"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a performance study of the Explicit Congestion\n Notification (ECN) mechanism in the TCP/IP protocol using our\n implementation on the Linux Operating System. ECN is an end-to-end\n congestion avoidance mechanism proposed by [6] and incorporated into\n RFC 2481[7]. We study the behavior of ECN for both bulk and\n transactional transfers. Our experiments show that there is\n improvement in throughput over NON ECN (TCP employing any of Reno,\n SACK/FACK or NewReno congestion control) in the case of bulk\n transfers and substantial improvement for transactional transfers.\n\n A more complete pdf version of this document is available at:\n http://www7.nortel.com:8080/CTL/ecnperf.pdf\n\n This memo in its current revision is missing a lot of the visual\n representations and experimental results found in the pdf version.\n\n1. Introduction\n\n In current IP networks, congestion management is l","scope_keywords":["2884","algorithm","algorithms","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2884 This memo presents a performance study of the Explicit Congestion\n Notification (ECN) mechanism in the TCP/IP protocol using our\n implementation on the Linux Operating System. ECN is an end-to-end\n congestion avoidance mechanism proposed by [6] and incorporated into\n RFC 2481[7]. We study the behavior of ECN for both bulk and\n transactional transfers. Our experiments show that there is\n improvement in throughput over NON ECN (TCP employing any of Reno,\n SACK/FACK or NewReno congestion control) in the case of bulk\n transfers and substantial improvement for transactional transfers.\n\n A more complete pdf version of this document is available at:\n http://www7.nortel.com:8080/CTL/ecnperf.pdf\n\n This memo in its current revision is missing a lot of the visual\n representations and experimental results found in the pdf version.\n\n1. Introduction\n\n In current IP networks, congestion management is l 2884 algorithm algorithms http management presentation nested-reference unchanged"},{"id":"IETF RFC 3042","type":"specification","body":"IETF","designation":"RFC 3042","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3042.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3042.txt","https://www.rfc-editor.org/rfc/rfc3042.pdf"],"folder":"IETF/RFC-3042","files":{"txt":{"path":"standards/IETF/RFC-3042/RFC-3042.txt","sha256":"c54bec6090d1cc755d111a6341abb964c07fe15b9fb4e4ef63d096d8cc078439"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a new Transmission Control Protocol (TCP)\n mechanism that can be used to more effectively recover lost segments\n when a connection's congestion window is small, or when a large\n number of segments are lost in a single transmission window. The\n \"Limited Transmit\" algorithm calls for sending a new data segment in\n response to each of the first two duplicate acknowledgments that\n arrive at the sender. Transmitting these segments increases the\n probability that TCP can recover from a single lost segment using the\n fast retransmit algorithm, rather than using a costly retransmission\n timeout. Limited Transmit can be used both in conjunction with, and\n in the absence of, the TCP selective acknowledgment (SACK) mechanism.\n\n1 Introduction\n\n A number of researchers have observed that TCP's loss recovery\n strategies do not work well when the congestion window at a TCP\n sende","scope_keywords":["3042","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null}],"search_text":"IETF RFC 3042 This document proposes a new Transmission Control Protocol (TCP)\n mechanism that can be used to more effectively recover lost segments\n when a connection's congestion window is small, or when a large\n number of segments are lost in a single transmission window. The\n \"Limited Transmit\" algorithm calls for sending a new data segment in\n response to each of the first two duplicate acknowledgments that\n arrive at the sender. Transmitting these segments increases the\n probability that TCP can recover from a single lost segment using the\n fast retransmit algorithm, rather than using a costly retransmission\n timeout. Limited Transmit can be used both in conjunction with, and\n in the absence of, the TCP selective acknowledgment (SACK) mechanism.\n\n1 Introduction\n\n A number of researchers have observed that TCP's loss recovery\n strategies do not work well when the congestion window at a TCP\n sende 3042 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3517","type":"specification","body":"IETF","designation":"RFC 3517","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3517.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3517.txt","https://www.rfc-editor.org/rfc/rfc3517.pdf"],"folder":"IETF/RFC-3517","files":{"txt":{"path":"standards/IETF/RFC-3517/RFC-3517.txt","sha256":"c4f18c5f031cb098c348ab7bbf063d0eb5a8b9fae8a7919a29658d7c9a80ad32"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. The algorithm presented in this document conforms to the\n spirit of the current congestion control specification (RFC 2581),\n but allows TCP senders to recover more effectively when multiple\n segments are lost from a single flight of data.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\nBlanton, et al. Standards Track [Page 1]\n\f\nRFC 3517 SACK-based Loss Recovery for TCP April 2003\n\n1 Introduction\n\n This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. While the TCP SACK ","scope_keywords":["3517","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 3517 This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. The algorithm presented in this document conforms to the\n spirit of the current congestion control specification (RFC 2581),\n but allows TCP senders to recover more effectively when multiple\n segments are lost from a single flight of data.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\nBlanton, et al. Standards Track [Page 1]\n\f\nRFC 3517 SACK-based Loss Recovery for TCP April 2003\n\n1 Introduction\n\n This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. While the TCP SACK  3517 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 4341","type":"specification","body":"IETF","designation":"RFC 4341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4341.txt","https://www.rfc-editor.org/rfc/rfc4341.pdf"],"folder":"IETF/RFC-4341","files":{"txt":{"path":"standards/IETF/RFC-4341/RFC-4341.txt","sha256":"3f8185653c48b135877abd86a4de9828e9f9ab5e3598ee78b00627915ba02528"}},"tags":["nested-reference","unchanged"],"summary":"This document contains the profile for Congestion Control Identifier\n 2 (CCID 2), TCP-like Congestion Control, in the Datagram Congestion\n Control Protocol (DCCP). CCID 2 should be used by senders who would\n like to take advantage of the available bandwidth in an environment\n with rapidly changing conditions, and who are able to adapt to the\n abrupt changes in the congestion window typical of TCP's Additive\n Increase Multiplicative Decrease (AIMD) congestion control.","scope_keywords":["4341","key","pid","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 4341 This document contains the profile for Congestion Control Identifier\n 2 (CCID 2), TCP-like Congestion Control, in the Datagram Congestion\n Control Protocol (DCCP). CCID 2 should be used by senders who would\n like to take advantage of the available bandwidth in an environment\n with rapidly changing conditions, and who are able to adapt to the\n abrupt changes in the congestion window typical of TCP's Additive\n Increase Multiplicative Decrease (AIMD) congestion control. 4341 key pid profile nested-reference unchanged"},{"id":"IETF RFC 5166","type":"specification","body":"IETF","designation":"RFC 5166","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5166.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5166.txt","https://www.rfc-editor.org/rfc/rfc5166.pdf"],"folder":"IETF/RFC-5166","files":{"txt":{"path":"standards/IETF/RFC-5166/RFC-5166.txt","sha256":"107916ddbc60d203f23f39a23527d433148f335892303e6bf8f101bdcf83e04e"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the metrics to be considered in an evaluation\n of new or modified congestion control mechanisms for the Internet.\n These include metrics for the evaluation of new transport protocols,\n of proposed modifications to TCP, of application-level congestion\n control, and of Active Queue Management (AQM) mechanisms in the\n router. This document is the first in a series of documents aimed at\n improving the models that we use in the evaluation of transport\n protocols.\n\n This document is a product of the Transport Modeling Research Group\n (TMRG), and has received detailed feedback from many members of the\n Research Group (RG). As the document tries to make clear, there is\n not necessarily a consensus within the research community (or the\n IETF community, the vendor community, the operations community, or\n any other community) about the metrics that congestion control\n mechan","scope_keywords":["5166","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 5166 This document discusses the metrics to be considered in an evaluation\n of new or modified congestion control mechanisms for the Internet.\n These include metrics for the evaluation of new transport protocols,\n of proposed modifications to TCP, of application-level congestion\n control, and of Active Queue Management (AQM) mechanisms in the\n router. This document is the first in a series of documents aimed at\n improving the models that we use in the evaluation of transport\n protocols.\n\n This document is a product of the Transport Modeling Research Group\n (TMRG), and has received detailed feedback from many members of the\n Research Group (RG). As the document tries to make clear, there is\n not necessarily a consensus within the research community (or the\n IETF community, the vendor community, the operations community, or\n any other community) about the metrics that congestion control\n mechan 5166 management nested-reference unchanged"},{"id":"IETF RFC 5326","type":"specification","body":"IETF","designation":"RFC 5326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5326.txt","https://www.rfc-editor.org/rfc/rfc5326.pdf"],"folder":"IETF/RFC-5326","files":{"txt":{"path":"standards/IETF/RFC-5326/RFC-5326.txt","sha256":"daddb35dac4fdafc8cc0447ce55de8a489624b98d0371cb5a3373417233641b7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Licklider Transmission Protocol (LTP),\n designed to provide retransmission-based reliability over links\n characterized by extremely long message round-trip times (RTTs)\n and/or frequent interruptions in connectivity. Since communication\n across interplanetary space is the most prominent example of this\n sort of environment, LTP is principally aimed at supporting \"long-\n haul\" reliable transmission in interplanetary space, but it has\n applications in other environments as well.\n\n This document is a product of the Delay Tolerant Networking Research\n Group and has been reviewed by that group. No objections to its\n publication as an RFC were raised.\n\nRamadas, et al. Experimental [Page 1]\n\f\nRFC 5326 LTP - Specification September 2008","scope_keywords":["5326","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 5326 This document describes the Licklider Transmission Protocol (LTP),\n designed to provide retransmission-based reliability over links\n characterized by extremely long message round-trip times (RTTs)\n and/or frequent interruptions in connectivity. Since communication\n across interplanetary space is the most prominent example of this\n sort of environment, LTP is principally aimed at supporting \"long-\n haul\" reliable transmission in interplanetary space, but it has\n applications in other environments as well.\n\n This document is a product of the Delay Tolerant Networking Research\n Group and has been reviewed by that group. No objections to its\n publication as an RFC were raised.\n\nRamadas, et al. Experimental [Page 1]\n\f\nRFC 5326 LTP - Specification September 2008 5326 management nested-reference unchanged"},{"id":"IETF RFC 5827","type":"specification","body":"IETF","designation":"RFC 5827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5827.txt","https://www.rfc-editor.org/rfc/rfc5827.pdf"],"folder":"IETF/RFC-5827","files":{"txt":{"path":"standards/IETF/RFC-5827/RFC-5827.txt","sha256":"4469362286bc4dbc9a97a9e89391294629a8be50ed7fbd5b7d1e85756c9295aa"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a new mechanism for TCP and Stream Control\n Transmission Protocol (SCTP) that can be used to recover lost\n segments when a connection's congestion window is small. The \"Early\n Retransmit\" mechanism allows the transport to reduce, in certain\n special circumstances, the number of duplicate acknowledgments\n required to trigger a fast retransmission. This allows the transport\n to use fast retransmit to recover segment losses that would otherwise\n require a lengthy retransmission timeout.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received ","scope_keywords":["5827","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 5827 This document proposes a new mechanism for TCP and Stream Control\n Transmission Protocol (SCTP) that can be used to recover lost\n segments when a connection's congestion window is small. The \"Early\n Retransmit\" mechanism allows the transport to reduce, in certain\n special circumstances, the number of duplicate acknowledgments\n required to trigger a fast retransmission. This allows the transport\n to use fast retransmit to recover segment losses that would otherwise\n require a lengthy retransmission timeout.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received  5827 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6182","type":"specification","body":"IETF","designation":"RFC 6182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6182.txt","https://www.rfc-editor.org/rfc/rfc6182.pdf"],"folder":"IETF/RFC-6182","files":{"txt":{"path":"standards/IETF/RFC-6182/RFC-6182.txt","sha256":"f9287690b697019f7898aa56d0bfd7a31cee41e1d6a7acf00af02075e3e1ada8"}},"tags":["nested-reference","unchanged"],"summary":"Hosts are often connected by multiple paths, but TCP restricts\n communications to a single path per transport connection. Resource\n usage within the network would be more efficient were these multiple\n paths able to be used concurrently. This should enhance user\n experience through improved resilience to network failure and higher\n throughput.\n\n This document outlines architectural guidelines for the development\n of a Multipath Transport Protocol, with references to how these\n architectural components come together in the development of a\n Multipath TCP (MPTCP). This document lists certain high-level design\n decisions that provide foundations for the design of the MPTCP\n protocol, based upon these architectural requirements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of t","scope_keywords":["6182","http","identification","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 6182 Hosts are often connected by multiple paths, but TCP restricts\n communications to a single path per transport connection. Resource\n usage within the network would be more efficient were these multiple\n paths able to be used concurrently. This should enhance user\n experience through improved resilience to network failure and higher\n throughput.\n\n This document outlines architectural guidelines for the development\n of a Multipath Transport Protocol, with references to how these\n architectural components come together in the development of a\n Multipath TCP (MPTCP). This document lists certain high-level design\n decisions that provide foundations for the design of the MPTCP\n protocol, based upon these architectural requirements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of t 6182 http identification key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6675","type":"specification","body":"IETF","designation":"RFC 6675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6675.txt","https://www.rfc-editor.org/rfc/rfc6675.pdf"],"folder":"IETF/RFC-6675","files":{"txt":{"path":"standards/IETF/RFC-6675/RFC-6675.txt","sha256":"ffe2625e663954fa45cde28ee971e5190b01b98b3ddc1e742c18bdab36396a8c"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) E. Blanton\nRequest for Comments: 6675 Purdue University\nObsoletes: 3517 M. Allman\nCategory: Standards Track ICSI\nISSN: 2070-1721 L. Wang\n Juniper Networks\n I. Jarvinen\n M. Kojo\n University of Helsinki\n Y. Nishida\n WIDE Project\n August 2012\n\n A Conservative Loss Recovery Algorithm Based on\n Selective Acknowledgment (SACK) for TCP\n\nAbstract\n\n This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. The algorithm presented in this document conforms to the\n spirit of the current congestion control specification (RFC 5681),\n but allows TCP senders to recover more effectively when multiple\n segments are lost from a single flight of data. This document\n obsoletes RFC 3517 and describes changes from it.\n\nStatus of This Memo\n\n This is an Internet Standards Track docume","scope_keywords":["6675","algorithm","algorithms","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 6675 Internet Engineering Task Force (IETF) E. Blanton\nRequest for Comments: 6675 Purdue University\nObsoletes: 3517 M. Allman\nCategory: Standards Track ICSI\nISSN: 2070-1721 L. Wang\n Juniper Networks\n I. Jarvinen\n M. Kojo\n University of Helsinki\n Y. Nishida\n WIDE Project\n August 2012\n\n A Conservative Loss Recovery Algorithm Based on\n Selective Acknowledgment (SACK) for TCP\n\nAbstract\n\n This document presents a conservative loss recovery algorithm for TCP\n that is based on the use of the selective acknowledgment (SACK) TCP\n option. The algorithm presented in this document conforms to the\n spirit of the current congestion control specification (RFC 5681),\n but allows TCP senders to recover more effectively when multiple\n segments are lost from a single flight of data. This document\n obsoletes RFC 3517 and describes changes from it.\n\nStatus of This Memo\n\n This is an Internet Standards Track docume 6675 algorithm algorithms http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6928","type":"specification","body":"IETF","designation":"RFC 6928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6928.txt","https://www.rfc-editor.org/rfc/rfc6928.pdf"],"folder":"IETF/RFC-6928","files":{"txt":{"path":"standards/IETF/RFC-6928/RFC-6928.txt","sha256":"375392b72f6800dbe6a945def04cfbace0875dc8f2835d8dbc8a73f6089bca52"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an experiment to increase the permitted TCP\n initial window (IW) from between 2 and 4 segments, as specified in\n RFC 3390, to 10 segments with a fallback to the existing\n recommendation when performance issues are detected. It discusses\n the motivation behind the increase, the advantages and disadvantages\n of the higher initial window, and presents results from several\n large-scale experiments showing that the higher initial window\n improves the overall performance of many web services without\n resulting in a congestion collapse. The document closes with a\n discussion of usage and deployment for further experimental purposes\n recommended by the IETF TCP Maintenance and Minor Extensions (TCPM)\n working group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n eval","scope_keywords":["6928","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 6928 This document proposes an experiment to increase the permitted TCP\n initial window (IW) from between 2 and 4 segments, as specified in\n RFC 3390, to 10 segments with a fallback to the existing\n recommendation when performance issues are detected. It discusses\n the motivation behind the increase, the advantages and disadvantages\n of the higher initial window, and presents results from several\n large-scale experiments showing that the higher initial window\n improves the overall performance of many web services without\n resulting in a congestion collapse. The document closes with a\n discussion of usage and deployment for further experimental purposes\n recommended by the IETF TCP Maintenance and Minor Extensions (TCPM)\n working group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n eval 6928 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7713","type":"specification","body":"IETF","designation":"RFC 7713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7713.txt","https://www.rfc-editor.org/rfc/rfc7713.pdf"],"folder":"IETF/RFC-7713","files":{"txt":{"path":"standards/IETF/RFC-7713/RFC-7713.txt","sha256":"61833398d8bc95ece7f6b23b1f05417f1ac29edf8377fa55b9f487308a35982f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an abstract mechanism by which senders inform\n the network about the congestion recently encountered by packets in\n the same flow. Today, network elements at any layer may signal\n congestion to the receiver by dropping packets or by Explicit\n Congestion Notification (ECN) markings, and the receiver passes this\n information back to the sender in transport-layer feedback. The\n mechanism described here enables the sender to also relay this\n congestion information back into the network in-band at the IP layer,\n such that the total amount of congestion from all elements on the\n path is revealed to all IP elements along the path, where it could,\n for example, be used to provide input to traffic management. This\n mechanism is called Congestion Exposure, or ConEx. The companion\n document, \"Congestion Exposure (ConEx) Concepts and Use Cases\"\n (RFC 6789), provides the entry","scope_keywords":["7713","algorithm","algorithms","audit","http","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 7713 This document describes an abstract mechanism by which senders inform\n the network about the congestion recently encountered by packets in\n the same flow. Today, network elements at any layer may signal\n congestion to the receiver by dropping packets or by Explicit\n Congestion Notification (ECN) markings, and the receiver passes this\n information back to the sender in transport-layer feedback. The\n mechanism described here enables the sender to also relay this\n congestion information back into the network in-band at the IP layer,\n such that the total amount of congestion from all elements on the\n path is revealed to all IP elements along the path, where it could,\n for example, be used to provide input to traffic management. This\n mechanism is called Congestion Exposure, or ConEx. The companion\n document, \"Congestion Exposure (ConEx) Concepts and Use Cases\"\n (RFC 6789), provides the entry 7713 algorithm algorithms audit http license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 9002","type":"specification","body":"IETF","designation":"RFC 9002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9002.txt","https://www.rfc-editor.org/rfc/rfc9002.pdf"],"folder":"IETF/RFC-9002","files":{"pdf":{"path":"standards/IETF/RFC-9002/RFC-9002.pdf","sha256":"d01a2adb6a0221ac152d96e2bfe65dc817ef0ee7d2a50c62861414caa3bf8260"},"txt":{"path":"standards/IETF/RFC-9002/RFC-9002.txt","sha256":"3a8a54eea1ad5d1c134a548bf15edfa0e21bfb4106dbd7db3c09cace842099af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes loss detection and congestion control\n mechanisms for QUIC.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9002.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.o","scope_keywords":["9002","algorithm","algorithms","delivery","encryption","http","https","key","keys","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 9002 This document describes loss detection and congestion control\n mechanisms for QUIC.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9002.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.o 9002 algorithm algorithms delivery encryption http https key keys license path subject trust nested-reference unchanged"},{"id":"IETF RFC 3815","type":"specification","body":"IETF","designation":"RFC 3815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3815.txt","https://www.rfc-editor.org/rfc/rfc3815.pdf"],"folder":"IETF/RFC-3815","files":{"txt":{"path":"standards/IETF/RFC-3815/RFC-3815.txt","sha256":"0aae012327c184662b4bf552fe8f3948563063cd6668a3f9662e9c763c28cc57"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for the Multiprotocol\n Label Switching, Label Distribution Protocol (LDP).","scope_keywords":["3815","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null}],"search_text":"IETF RFC 3815 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for the Multiprotocol\n Label Switching, Label Distribution Protocol (LDP). 3815 key management nested-reference unchanged"},{"id":"IETF RFC 4150","type":"specification","body":"IETF","designation":"RFC 4150","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4150.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4150.txt","https://www.rfc-editor.org/rfc/rfc4150.pdf"],"folder":"IETF/RFC-4150","files":{"txt":{"path":"standards/IETF/RFC-4150/RFC-4150.txt","sha256":"08386b8cb6812801381d652e7d1b7183b8cea883b71219e9822e1c707a83033c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for monitoring\n selectable performance metrics and statistics derived from the\n monitoring of network packets and sub-application level transactions.\n The metrics can be defined through reference to existing IETF, ITU,\n and other standards organizations' documents. The monitoring covers\n both passive and active traffic generation sources.\n\nDietz & Cole Standards Track [Page 1]\n\f\nRFC 4150 TPM-MIB August 2005","scope_keywords":["4150","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4150 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for monitoring\n selectable performance metrics and statistics derived from the\n monitoring of network packets and sub-application level transactions.\n The metrics can be defined through reference to existing IETF, ITU,\n and other standards organizations' documents. The monitoring covers\n both passive and active traffic generation sources.\n\nDietz & Cole Standards Track [Page 1]\n\f\nRFC 4150 TPM-MIB August 2005 4150 http key management nested-reference unchanged"},{"id":"IETF RFC 2602","type":"specification","body":"IETF","designation":"RFC 2602","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2602.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2602.txt","https://www.rfc-editor.org/rfc/rfc2602.pdf"],"folder":"IETF/RFC-2602","files":{"txt":{"path":"standards/IETF/RFC-2602/RFC-2602.txt","sha256":"bdafabd19869db8461ad5f487d90e3bfa9de1b8478aa218104fba2fac50c9109"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate MARS servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use MARS [1] is cumbersome\n and error-prone since it requires at least one ATM address to be\n statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use MARS\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the informat","scope_keywords":["2602","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2602 This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate MARS servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use MARS [1] is cumbersome\n and error-prone since it requires at least one ATM address to be\n statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use MARS\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the informat 2602 management nested-reference unchanged"},{"id":"IETF RFC 3916","type":"specification","body":"IETF","designation":"RFC 3916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3916.txt","https://www.rfc-editor.org/rfc/rfc3916.pdf"],"folder":"IETF/RFC-3916","files":{"txt":{"path":"standards/IETF/RFC-3916/RFC-3916.txt","sha256":"72169427139a849a7b83981b05b8aa10aea04cf58f6184337219c5d64d39000c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes base requirements for the Pseudo-Wire\n Emulation Edge to Edge Working Group (PWE3 WG). It provides\n guidelines for other working group documents that will define\n mechanisms for providing pseudo-wire emulation of Ethernet, ATM, and\n Frame Relay. Requirements for pseudo-wire emulation of TDM (i.e.,\n \"synchronous bit streams at rates defined by ITU G.702\") are defined\n in another document. It should be noted that the PWE3 WG\n standardizes mechanisms that can be used to provide PWE3 services,\n but not the services themselves.","scope_keywords":["3916","attribute","attributes","delivery","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4026","folder":"IETF/RFC-4026","source":"IETF/RFC-4026/RFC-4026.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null}],"search_text":"IETF RFC 3916 This document describes base requirements for the Pseudo-Wire\n Emulation Edge to Edge Working Group (PWE3 WG). It provides\n guidelines for other working group documents that will define\n mechanisms for providing pseudo-wire emulation of Ethernet, ATM, and\n Frame Relay. Requirements for pseudo-wire emulation of TDM (i.e.,\n \"synchronous bit streams at rates defined by ITU G.702\") are defined\n in another document. It should be noted that the PWE3 WG\n standardizes mechanisms that can be used to provide PWE3 services,\n but not the services themselves. 3916 attribute attributes delivery management path nested-reference unchanged"},{"id":"IETF RFC 4722","type":"specification","body":"IETF","designation":"RFC 4722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4722.txt","https://www.rfc-editor.org/rfc/rfc4722.pdf"],"folder":"IETF/RFC-4722","files":{"txt":{"path":"standards/IETF/RFC-4722/RFC-4722.txt","sha256":"5c4116a4f385602fab7d1ac47cd5401639b4b9072bf3d8d2ee493c8e518436e4"}},"tags":["nested-reference","unchanged"],"summary":"Media Server Control Markup Language (MSCML) is a markup language\n used in conjunction with SIP to provide advanced conferencing and\n interactive voice response (IVR) functions. MSCML presents an\n application-level control model, as opposed to device-level control\n models. One use of this protocol is for communications between a\n conference focus and mixer in the IETF SIP Conferencing Framework.\n\nVan Dyke, et al. Informational [Page 1]\n\f\nRFC 4722 MSCML November 2006","scope_keywords":["4722","attribute","attributes","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null}],"search_text":"IETF RFC 4722 Media Server Control Markup Language (MSCML) is a markup language\n used in conjunction with SIP to provide advanced conferencing and\n interactive voice response (IVR) functions. MSCML presents an\n application-level control model, as opposed to device-level control\n models. One use of this protocol is for communications between a\n conference focus and mixer in the IETF SIP Conferencing Framework.\n\nVan Dyke, et al. Informational [Page 1]\n\f\nRFC 4722 MSCML November 2006 4722 attribute attributes key keys trust nested-reference unchanged"},{"id":"IETF RFC 4730","type":"specification","body":"IETF","designation":"RFC 4730","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4730.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4730.txt","https://www.rfc-editor.org/rfc/rfc4730.pdf"],"folder":"IETF/RFC-4730","files":{"txt":{"path":"standards/IETF/RFC-4730/RFC-4730.txt","sha256":"4313dfb02ce4dae9097eb5dbfa9db5aa66dc2429db43a347ce8876379e358b11"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a SIP Event Package \"kpml\" that enables\n monitoring of Dual Tone Multi-Frequency (DTMF) signals and uses\n Extensible Markup Language (XML) documents referred to as Key Press\n Markup Language (KPML). The kpml Event Package may be used to\n support applications consistent with the principles defined in the\n document titled \"A Framework for Application Interaction in the\n Session Initiation Protocol (SIP)\". The event package uses SUBSCRIBE\n messages and allows for XML documents that define and describe filter\n specifications for capturing key presses (DTMF Tones) entered at a\n presentation-free User Interface SIP User Agent (UA). The event\n package uses NOTIFY messages and allows for XML documents to report\n the captured key presses (DTMF tones), consistent with the filter\n specifications, to an Application Server. The scope of this package\n is for collecting suppleme","scope_keywords":["4730","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null}],"search_text":"IETF RFC 4730 This document describes a SIP Event Package \"kpml\" that enables\n monitoring of Dual Tone Multi-Frequency (DTMF) signals and uses\n Extensible Markup Language (XML) documents referred to as Key Press\n Markup Language (KPML). The kpml Event Package may be used to\n support applications consistent with the principles defined in the\n document titled \"A Framework for Application Interaction in the\n Session Initiation Protocol (SIP)\". The event package uses SUBSCRIBE\n messages and allows for XML documents that define and describe filter\n specifications for capturing key presses (DTMF Tones) entered at a\n presentation-free User Interface SIP User Agent (UA). The event\n package uses NOTIFY messages and allows for XML documents to report\n the captured key presses (DTMF tones), consistent with the filter\n specifications, to an Application Server. The scope of this package\n is for collecting suppleme 4730 key presentation trust nested-reference unchanged"},{"id":"IETF RFC 2024","type":"specification","body":"IETF","designation":"RFC 2024","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2024.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2024.txt","https://www.rfc-editor.org/rfc/rfc2024.pdf"],"folder":"IETF/RFC-2024","files":{"txt":{"path":"standards/IETF/RFC-2024/RFC-2024.txt","sha256":"355a08531fc4b0fe1b568617c9745f4c3d0f7f6218eb67c482cd564bb9329cf4"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for configuring, monitoring, and\n controlling Data Link Switches (DLSw) [1].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI [2], and semantically identical to the SNMPv1\n definitions [3].","scope_keywords":["2024","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2024 This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for configuring, monitoring, and\n controlling Data Link Switches (DLSw) [1].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI [2], and semantically identical to the SNMPv1\n definitions [3]. 2024 management nested-reference unchanged"},{"id":"IETF RFC 2410","type":"specification","body":"IETF","designation":"RFC 2410","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2410.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2410.txt","https://www.rfc-editor.org/rfc/rfc2410.pdf"],"folder":"IETF/RFC-2410","files":{"txt":{"path":"standards/IETF/RFC-2410/RFC-2410.txt","sha256":"231a6ea9798b78c489126aab83649eb9db9bc069434b46c60e5908b4527a6d1f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the NULL encryption algorithm and its use with the\n IPsec Encapsulating Security Payload (ESP). NULL does nothing to\n alter plaintext data. In fact, NULL, by itself, does nothing. NULL\n provides the means for ESP to provide authentication and integrity\n without confidentiality.\n\n Further information on the other components necessary for ESP\n implementations is provided by [ESP] and [ROAD].\n\n1. Introduction\n\n This memo defines the NULL encryption algorithm and its use with the\n IPsec Encapsulating Security Payload [ESP] to provide authentication\n and integrity without confidentiality.\n\n NULL is a block cipher the origins of which appear to be lost in\n antiquity. Despite rumors that the National Security Agency\n suppressed publication of this algorithm, there is no evidence of\n such action on their part. Rather, recent archaeological evidence\n suggests that the NULL algor","scope_keywords":["2410","algorithm","algorithms","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 2410 This memo defines the NULL encryption algorithm and its use with the\n IPsec Encapsulating Security Payload (ESP). NULL does nothing to\n alter plaintext data. In fact, NULL, by itself, does nothing. NULL\n provides the means for ESP to provide authentication and integrity\n without confidentiality.\n\n Further information on the other components necessary for ESP\n implementations is provided by [ESP] and [ROAD].\n\n1. Introduction\n\n This memo defines the NULL encryption algorithm and its use with the\n IPsec Encapsulating Security Payload [ESP] to provide authentication\n and integrity without confidentiality.\n\n NULL is a block cipher the origins of which appear to be lost in\n antiquity. Despite rumors that the National Security Agency\n suppressed publication of this algorithm, there is no evidence of\n such action on their part. Rather, recent archaeological evidence\n suggests that the NULL algor 2410 algorithm algorithms authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2436","type":"specification","body":"IETF","designation":"RFC 2436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2436.txt","https://www.rfc-editor.org/rfc/rfc2436.pdf"],"folder":"IETF/RFC-2436","files":{"txt":{"path":"standards/IETF/RFC-2436/RFC-2436.txt","sha256":"053d9087666086e081b2762ccac8fdf680f8e52dd9f1340bddbf68cf8f74154d"}},"tags":["nested-reference","unchanged"],"summary":"This Liaison is sent to all ITU-T Study Groups to encourage and aid\n in the understanding of collaboration on standards development\n between the ITU-T and the Internet Society (ISOC) / Internet\n Engineering Task Force (IETF). Feedback to TSAG is encouraged before\n its next meeting in April 1999.\n\nBrett, et. al. Informational [Page 1]\n\f\nRFC 2436 ISOC/IETF - ITU-T Collaboration October 1998","scope_keywords":["2436","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3356","folder":"IETF/RFC-3356","source":"IETF/RFC-3356/RFC-3356.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null}],"search_text":"IETF RFC 2436 This Liaison is sent to all ITU-T Study Groups to encourage and aid\n in the understanding of collaboration on standards development\n between the ITU-T and the Internet Society (ISOC) / Internet\n Engineering Task Force (IETF). Feedback to TSAG is encouraged before\n its next meeting in April 1999.\n\nBrett, et. al. Informational [Page 1]\n\f\nRFC 2436 ISOC/IETF - ITU-T Collaboration October 1998 2436 management presentation nested-reference unchanged"},{"id":"IETF RFC 2438","type":"specification","body":"IETF","designation":"RFC 2438","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2438.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2438.txt","https://www.rfc-editor.org/rfc/rfc2438.pdf"],"folder":"IETF/RFC-2438","files":{"txt":{"path":"standards/IETF/RFC-2438/RFC-2438.txt","sha256":"468c4912cc5b1a76c0c2574ac75cb4c8925869446c22559c00f5da5e0ca8be3e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. O'Dell\nRequest for Comments: 2438 UUNET Technologies\nBCP: 27 H. Alvestrand\nCategory: Best Current Practice Maxware\n B. Wijnen\n IBM T. J. Watson Research\n S. Bradner\n Harvard University\n October 1998\n\n Advancement of MIB specifications on the IETF Standards Track\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Abstract\n\n The Internet Standards Process [1] requires that all IETF Standards\n Track specifications must have \"multiple, independent, and\n interoperable implementations\" before they can be advanced beyond\n Proposed Standard status. This document specifies the process which\n the IESG will use to determine if a MI","scope_keywords":["2438","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2438 Network Working Group M. O'Dell\nRequest for Comments: 2438 UUNET Technologies\nBCP: 27 H. Alvestrand\nCategory: Best Current Practice Maxware\n B. Wijnen\n IBM T. J. Watson Research\n S. Bradner\n Harvard University\n October 1998\n\n Advancement of MIB specifications on the IETF Standards Track\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n2. Abstract\n\n The Internet Standards Process [1] requires that all IETF Standards\n Track specifications must have \"multiple, independent, and\n interoperable implementations\" before they can be advanced beyond\n Proposed Standard status. This document specifies the process which\n the IESG will use to determine if a MI 2438 management nested-reference unchanged"},{"id":"IETF RFC 2629","type":"specification","body":"IETF","designation":"RFC 2629","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2629.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2629.txt","https://www.rfc-editor.org/rfc/rfc2629.pdf"],"folder":"IETF/RFC-2629","files":{"txt":{"path":"standards/IETF/RFC-2629/RFC-2629.txt","sha256":"7461a54a5007057a8e2e0bcc3e53354b3dd2372ddcc58e4ba29159bad5a1e4b6"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a technique for using XML (Extensible Markup\n Language) as a source format for documents in the Internet-Drafts\n (I-Ds) and Request for Comments (RFC) series.\n\nRose Informational [Page 1]\n\f\nRFC 2629 Writing I-Ds and RFCs using XML June 1999","scope_keywords":["2629","attribute"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3934","folder":"IETF/RFC-3934","source":"IETF/RFC-3934/RFC-3934.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 4371","folder":"IETF/RFC-4371","source":"IETF/RFC-4371/RFC-4371.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null}],"search_text":"IETF RFC 2629 This memo presents a technique for using XML (Extensible Markup\n Language) as a source format for documents in the Internet-Drafts\n (I-Ds) and Request for Comments (RFC) series.\n\nRose Informational [Page 1]\n\f\nRFC 2629 Writing I-Ds and RFCs using XML June 1999 2629 attribute nested-reference unchanged"},{"id":"IETF RFC 2680","type":"specification","body":"IETF","designation":"RFC 2680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2680.txt","https://www.rfc-editor.org/rfc/rfc2680.pdf"],"folder":"IETF/RFC-2680","files":{"txt":{"path":"standards/IETF/RFC-2680/RFC-2680.txt","sha256":"b22962c571e4528694b6c6a19bdb7321fa64b0b29e7cc2345fc73a68e574a289"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Almes\nRequest for Comments: 2680 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A One-way Packet Loss Metric for IPPM\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a metric for one-way packet loss across Internet\n paths. It builds on notions introduced and discussed in the IPPM\n Framework document, RFC 2330 [1]; the reader is assumed to be\n familiar with that document.\n\n This memo i","scope_keywords":["2680","key","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3357","folder":"IETF/RFC-3357","source":"IETF/RFC-3357/RFC-3357.txt","version":null},{"body":"IETF","designation":"RFC 3763","folder":"IETF/RFC-3763","source":"IETF/RFC-3763/RFC-3763.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 2680 Network Working Group G. Almes\nRequest for Comments: 2680 S. Kalidindi\nCategory: Standards Track M. Zekauskas\n Advanced Network & Services\n September 1999\n\n A One-way Packet Loss Metric for IPPM\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This memo defines a metric for one-way packet loss across Internet\n paths. It builds on notions introduced and discussed in the IPPM\n Framework document, RFC 2330 [1]; the reader is assumed to be\n familiar with that document.\n\n This memo i 2680 key path risk nested-reference unchanged"},{"id":"IETF RFC 2710","type":"specification","body":"IETF","designation":"RFC 2710","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2710.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2710.txt","https://www.rfc-editor.org/rfc/rfc2710.pdf"],"folder":"IETF/RFC-2710","files":{"txt":{"path":"standards/IETF/RFC-2710/RFC-2710.txt","sha256":"dfa7ad9c99e9fc924024264c988cf7fdbb19fee6b043ab34a37e3604dce1f383"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the protocol used by an IPv6 router to\n discover the presence of multicast listeners (that is, nodes wishing\n to receive multicast packets) on its directly attached links, and to\n discover specifically which multicast addresses are of interest to\n those neighboring nodes. This protocol is referred to as Multicast\n Listener Discovery or MLD. MLD is derived from version 2 of IPv4's\n Internet Group Management Protocol, IGMPv2. One important difference\n to note is that MLD uses ICMPv6 (IP Protocol 58) message types,\n rather than IGMP (IP Protocol 2) message types.\n\n1. Definitions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [KEYWORDS].\n\n2. Introduction\n\n The purpose of Multicast Listener Discovery (MLD) is to enable ea","scope_keywords":["2710","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2711","folder":"IETF/RFC-2711","source":"IETF/RFC-2711/RFC-2711.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3590","folder":"IETF/RFC-3590","source":"IETF/RFC-3590/RFC-3590.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4392","folder":"IETF/RFC-4392","source":"IETF/RFC-4392/RFC-4392.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 2710 This document specifies the protocol used by an IPv6 router to\n discover the presence of multicast listeners (that is, nodes wishing\n to receive multicast packets) on its directly attached links, and to\n discover specifically which multicast addresses are of interest to\n those neighboring nodes. This protocol is referred to as Multicast\n Listener Discovery or MLD. MLD is derived from version 2 of IPv4's\n Internet Group Management Protocol, IGMPv2. One important difference\n to note is that MLD uses ICMPv6 (IP Protocol 58) message types,\n rather than IGMP (IP Protocol 2) message types.\n\n1. Definitions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [KEYWORDS].\n\n2. Introduction\n\n The purpose of Multicast Listener Discovery (MLD) is to enable ea 2710 key management nested-reference unchanged"},{"id":"IETF RFC 2717","type":"specification","body":"IETF","designation":"RFC 2717","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2717.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2717.txt","https://www.rfc-editor.org/rfc/rfc2717.pdf"],"folder":"IETF/RFC-2717","files":{"txt":{"path":"standards/IETF/RFC-2717/RFC-2717.txt","sha256":"73056f8acea2581748fe640abd06073013c3408eb04c2df5f1038d6b3e5dd1e2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the process by which new URL scheme names are\n registered.","scope_keywords":["2717","key","presentation","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2718","folder":"IETF/RFC-2718","source":"IETF/RFC-2718/RFC-2718.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3368","folder":"IETF/RFC-3368","source":"IETF/RFC-3368/RFC-3368.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null}],"search_text":"IETF RFC 2717 This document defines the process by which new URL scheme names are\n registered. 2717 key presentation registered risk nested-reference unchanged"},{"id":"IETF RFC 2732","type":"specification","body":"IETF","designation":"RFC 2732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2732.txt","https://www.rfc-editor.org/rfc/rfc2732.pdf"],"folder":"IETF/RFC-2732","files":{"txt":{"path":"standards/IETF/RFC-2732/RFC-2732.txt","sha256":"dadcad8a716449d06d3ad42f2428c09b68af5424a382185d244d1eeec1a5076e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format for literal IPv6 Addresses in URL's\n for implementation in World Wide Web browsers. This format has been\n implemented in the IPv6 versions of several widely deployed browsers\n including Microsoft Internet Explorer, Mozilla, and Lynx. It is also\n intended to be used in the IPv6 version of the service location\n protocol.\n\n This document incudes an update to the generic syntax for Uniform\n Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax\n for IPv6 addresses and allows the use of \"[\" and \"]\" within a URI\n explicitly for this reserved purpose.\n\n1. Introduction\n\n The textual representation defined for literal IPv6 addresses in\n [ARCH] is not directly compatible with URL's. Both use \":\" and \".\"\n characters as delimiters. This document defines the format for\n literal IPv6 Addresses in URL's for implementation in World Wide Web\n browsers. The go","scope_keywords":["2732","http","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3721","folder":"IETF/RFC-3721","source":"IETF/RFC-3721/RFC-3721.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null}],"search_text":"IETF RFC 2732 This document defines the format for literal IPv6 Addresses in URL's\n for implementation in World Wide Web browsers. This format has been\n implemented in the IPv6 versions of several widely deployed browsers\n including Microsoft Internet Explorer, Mozilla, and Lynx. It is also\n intended to be used in the IPv6 version of the service location\n protocol.\n\n This document incudes an update to the generic syntax for Uniform\n Resource Identifiers defined in RFC 2396 [URL]. It defines a syntax\n for IPv6 addresses and allows the use of \"[\" and \"]\" within a URI\n explicitly for this reserved purpose.\n\n1. Introduction\n\n The textual representation defined for literal IPv6 addresses in\n [ARCH] is not directly compatible with URL's. Both use \":\" and \".\"\n characters as delimiters. This document defines the format for\n literal IPv6 Addresses in URL's for implementation in World Wide Web\n browsers. The go 2732 http key presentation nested-reference unchanged"},{"id":"IETF RFC 2795","type":"specification","body":"IETF","designation":"RFC 2795","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2795.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2795.txt","https://www.rfc-editor.org/rfc/rfc2795.pdf"],"folder":"IETF/RFC-2795","files":{"txt":{"path":"standards/IETF/RFC-2795/RFC-2795.txt","sha256":"99cbe5508cc5a487991128044571442ef4257acc898b0d8b78aff9f0853aa52d"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a protocol suite which supports an infinite\n number of monkeys that sit at an infinite number of typewriters in\n order to determine when they have either produced the entire works of\n William Shakespeare or a good television show. The suite includes\n communications and control protocols for monkeys and the\n organizations that interact with them.","scope_keywords":["2795","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null}],"search_text":"IETF RFC 2795 This memo describes a protocol suite which supports an infinite\n number of monkeys that sit at an infinite number of typewriters in\n order to determine when they have either produced the entire works of\n William Shakespeare or a good television show. The suite includes\n communications and control protocols for monkeys and the\n organizations that interact with them. 2795 key keys management nested-reference unchanged"},{"id":"IETF RFC 2903","type":"specification","body":"IETF","designation":"RFC 2903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2903.txt","https://www.rfc-editor.org/rfc/rfc2903.pdf"],"folder":"IETF/RFC-2903","files":{"txt":{"path":"standards/IETF/RFC-2903/RFC-2903.txt","sha256":"b12f75b0d7b706467cd63c2e8f7982ddd27f627a0534e2803f111f0bf9067218"}},"tags":["nested-reference","unchanged"],"summary":"This memo proposes an Authentication, Authorization, Accounting (AAA)\n architecture that would incorporate a generic AAA server along with\n an application interface to a set of Application Specific Modules\n that could perform application specific AAA functions. A separation\n of AAA functions required in a multi-domain environment is then\n proposed using a layered protocol abstraction. The long term goal is\n to create a generic framework which allows complex authorizations to\n be realized through a network of interconnected AAA servers.\n\nde Laat, et al. Experimental [Page 1]\n\f\nRFC 2903 Generic AAA Architecture August 2000","scope_keywords":["2903","authentication","authorization","management","policy","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3334","folder":"IETF/RFC-3334","source":"IETF/RFC-3334/RFC-3334.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null}],"search_text":"IETF RFC 2903 This memo proposes an Authentication, Authorization, Accounting (AAA)\n architecture that would incorporate a generic AAA server along with\n an application interface to a set of Application Specific Modules\n that could perform application specific AAA functions. A separation\n of AAA functions required in a multi-domain environment is then\n proposed using a layered protocol abstraction. The long term goal is\n to create a generic framework which allows complex authorizations to\n be realized through a network of interconnected AAA servers.\n\nde Laat, et al. Experimental [Page 1]\n\f\nRFC 2903 Generic AAA Architecture August 2000 2903 authentication authorization management policy presentation trust nested-reference unchanged"},{"id":"IETF RFC 3046","type":"specification","body":"IETF","designation":"RFC 3046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3046.txt","https://www.rfc-editor.org/rfc/rfc3046.pdf"],"folder":"IETF/RFC-3046","files":{"txt":{"path":"standards/IETF/RFC-3046/RFC-3046.txt","sha256":"6b343c02d5c495cd1f780a43ab2c4e3b9bca968b82024b9d2fdb90d75b98a5cf"}},"tags":["nested-reference","unchanged"],"summary":"Newer high-speed public Internet access technologies call for a\n high-speed modem to have a local area network (LAN) attachment to one\n or more customer premise hosts. It is advantageous to use the\n Dynamic Host Configuration Protocol (DHCP) as defined in RFC 2131 to\n assign customer premise host IP addresses in this environment.\n However, a number of security and scaling problems arise with such\n \"public\" DHCP use. This document describes a new DHCP option to\n address these issues. This option extends the set of DHCP options as\n defined in RFC 2132.\n\n The new option is called the Relay Agent Information option and is\n inserted by the DHCP relay agent when forwarding client-originated\n DHCP packets to a DHCP server. Servers recognizing the Relay Agent\n Information option may use the information to implement IP address or\n other parameter assignment policies. The DHCP Server echoes the\n o","scope_keywords":["3046","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3679","folder":"IETF/RFC-3679","source":"IETF/RFC-3679/RFC-3679.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null},{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 3993","folder":"IETF/RFC-3993","source":"IETF/RFC-3993/RFC-3993.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4649","folder":"IETF/RFC-4649","source":"IETF/RFC-4649/RFC-4649.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 4994","folder":"IETF/RFC-4994","source":"IETF/RFC-4994/RFC-4994.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6221","folder":"IETF/RFC-6221","source":"IETF/RFC-6221/RFC-6221.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null}],"search_text":"IETF RFC 3046 Newer high-speed public Internet access technologies call for a\n high-speed modem to have a local area network (LAN) attachment to one\n or more customer premise hosts. It is advantageous to use the\n Dynamic Host Configuration Protocol (DHCP) as defined in RFC 2131 to\n assign customer premise host IP addresses in this environment.\n However, a number of security and scaling problems arise with such\n \"public\" DHCP use. This document describes a new DHCP option to\n address these issues. This option extends the set of DHCP options as\n defined in RFC 2132.\n\n The new option is called the Relay Agent Information option and is\n inserted by the DHCP relay agent when forwarding client-originated\n DHCP packets to a DHCP server. Servers recognizing the Relay Agent\n Information option may use the information to implement IP address or\n other parameter assignment policies. The DHCP Server echoes the\n o 3046 policies trust nested-reference unchanged"},{"id":"IETF RFC 3059","type":"specification","body":"IETF","designation":"RFC 3059","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3059.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3059.txt","https://www.rfc-editor.org/rfc/rfc3059.pdf"],"folder":"IETF/RFC-3059","files":{"txt":{"path":"standards/IETF/RFC-3059/RFC-3059.txt","sha256":"d08cacef06a334b6afca755d4c54ea554f38d7414bf02224aa821e602485e04e"}},"tags":["nested-reference","unchanged"],"summary":"The Service Location Protocol, Version 2 (SLPv2) provides a mechanism\n for a service to be discovered in a single exchange of messages.\n This exchange of messages does not presently include any of the\n service's attributes. This document specifies a SLPv2 extension\n which allows a User Agent (UA) to request a service's attributes be\n included as an extension to Service Reply messages. This will\n eliminate the need for multiple round trip messages for a UA to\n acquire all service information.","scope_keywords":["3059","attribute","attributes","authentication","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 3059 The Service Location Protocol, Version 2 (SLPv2) provides a mechanism\n for a service to be discovered in a single exchange of messages.\n This exchange of messages does not presently include any of the\n service's attributes. This document specifies a SLPv2 extension\n which allows a User Agent (UA) to request a service's attributes be\n included as an extension to Service Reply messages. This will\n eliminate the need for multiple round trip messages for a UA to\n acquire all service information. 3059 attribute attributes authentication key signature nested-reference unchanged"},{"id":"IETF RFC 3068","type":"specification","body":"IETF","designation":"RFC 3068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3068.txt","https://www.rfc-editor.org/rfc/rfc3068.pdf"],"folder":"IETF/RFC-3068","files":{"txt":{"path":"standards/IETF/RFC-3068/RFC-3068.txt","sha256":"2dd67379d16fd368260831de61ee8b6bfd589149d9152103588ec8db7fb6f3e5"}},"tags":["nested-reference","unchanged"],"summary":"This memo introduces a \"6to4 anycast address\" in order to simplify\n the configuration of 6to4 routers. It also defines how this address\n will be used by 6to4 relay routers, how the corresponding \"6to4\n anycast prefix\" will be advertised in the IGP and in the EGP. The\n memo documents the reservation by IANA (Internet Assigned Numbers\n Authority) of the \"6to4 relay anycast prefix.\"\n\n1 Introduction\n\n According to [RFC3056], there are two deployment options for a 6to4\n routing domain, depending on whether or not the domain is using an\n IPv6 exterior routing protocol. If a routing protocol is used, then\n the 6to4 routers acquire routes to all existing IPv6 networks through\n the combination of EGP and IGP. If no IPv6 exterior routing protocol\n is used, the 6to4 routers using a given relay router each have a\n default IPv6 route pointing to the relay router. This second case is\n typically used b","scope_keywords":["3068","attribute","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 5569","folder":"IETF/RFC-5569","source":"IETF/RFC-5569/RFC-5569.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 3068 This memo introduces a \"6to4 anycast address\" in order to simplify\n the configuration of 6to4 routers. It also defines how this address\n will be used by 6to4 relay routers, how the corresponding \"6to4\n anycast prefix\" will be advertised in the IGP and in the EGP. The\n memo documents the reservation by IANA (Internet Assigned Numbers\n Authority) of the \"6to4 relay anycast prefix.\"\n\n1 Introduction\n\n According to [RFC3056], there are two deployment options for a 6to4\n routing domain, depending on whether or not the domain is using an\n IPv6 exterior routing protocol. If a routing protocol is used, then\n the 6to4 routers acquire routes to all existing IPv6 networks through\n the combination of EGP and IGP. If no IPv6 exterior routing protocol\n is used, the 6to4 routers using a given relay router each have a\n default IPv6 route pointing to the relay router. This second case is\n typically used b 3068 attribute path nested-reference unchanged"},{"id":"IETF RFC 3131","type":"specification","body":"IETF","designation":"RFC 3131","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3131.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3131.txt","https://www.rfc-editor.org/rfc/rfc3131.pdf"],"folder":"IETF/RFC-3131","files":{"txt":{"path":"standards/IETF/RFC-3131/RFC-3131.txt","sha256":"706428b720fcb63e6723bff7505847a19c9459f3621000e1da1900493244ac2e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the standardization collaboration between\n 3GPP2 and IETF.\n\n1. Conventions used in this document\n\n This document uses significant terminology that is specialized to\n IETF, 3GPP2, or their areas of work. See appendix A for definitions\n of acronyms. The organizational definitions can be found in their\n respective web-sites.\n\n2. Introduction\n\n This document contains a set of principles and guidelines that serves\n as the basis for establishing the collaboration between 3GPP2 and\n IETF, with the objective of securing timely development of technical\n specification that facilitate maximum interoperability with existing\n (fixed and mobile) Internet systems, devices, and protocols.\n\nBradner, et al. Informational [Page 1]\n\f\nRFC 3131 3GPP2-IETF Standardization Collaboration June 2001\n\n Each organization will operate according to their own rules and\n procedures including rule","scope_keywords":["3131","http","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4052","folder":"IETF/RFC-4052","source":"IETF/RFC-4052/RFC-4052.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null}],"search_text":"IETF RFC 3131 This document describes the standardization collaboration between\n 3GPP2 and IETF.\n\n1. Conventions used in this document\n\n This document uses significant terminology that is specialized to\n IETF, 3GPP2, or their areas of work. See appendix A for definitions\n of acronyms. The organizational definitions can be found in their\n respective web-sites.\n\n2. Introduction\n\n This document contains a set of principles and guidelines that serves\n as the basis for establishing the collaboration between 3GPP2 and\n IETF, with the objective of securing timely development of technical\n specification that facilitate maximum interoperability with existing\n (fixed and mobile) Internet systems, devices, and protocols.\n\nBradner, et al. Informational [Page 1]\n\f\nRFC 3131 3GPP2-IETF Standardization Collaboration June 2001\n\n Each organization will operate according to their own rules and\n procedures including rule 3131 http management policies policy nested-reference unchanged"},{"id":"IETF RFC 3157","type":"specification","body":"IETF","designation":"RFC 3157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3157.txt","https://www.rfc-editor.org/rfc/rfc3157.pdf"],"folder":"IETF/RFC-3157","files":{"txt":{"path":"standards/IETF/RFC-3157/RFC-3157.txt","sha256":"e596a7baacdca0b7b4e55e6ba4cc1312e69eebd07e8dfa42def9910afc09f7c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes requirements to be placed on Securely\n Available Credentials (SACRED) protocols.","scope_keywords":["3157","authentication","certificate","credential","credentials","key","keys","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null}],"search_text":"IETF RFC 3157 This document describes requirements to be placed on Securely\n Available Credentials (SACRED) protocols. 3157 authentication certificate credential credentials key keys tls trust nested-reference unchanged"},{"id":"IETF RFC 3214","type":"specification","body":"IETF","designation":"RFC 3214","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3214.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3214.txt","https://www.rfc-editor.org/rfc/rfc3214.pdf"],"folder":"IETF/RFC-3214","files":{"txt":{"path":"standards/IETF/RFC-3214/RFC-3214.txt","sha256":"fb43f56958c2ae076c9771a94b1b4cf64ad7f9cdb7aa12171710dd36e57d755a"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an approach to modify the bandwidth and\n possibly other parameters of an established CR-LSP (Constraint-based\n Routed Label Switched Paths) using CR-LDP (Constraint-based Routed\n Label Distribution Protocol) without service interruption. After a\n CR-LSP is set up, its bandwidth reservation may need to be changed by\n the network operator, due to the new requirements for the traffic\n carried on that CR-LSP. The LSP modification feature can be\n supported by CR-LDP by use of the _modify_value for the _action\n indicator flag_ in the LSPID TLV. This feature has application in\n dynamic network resources management where traffic of different\n priorities and service classes is involved.\n\nAsh, et al. Standards Track [Page 1]\n\f\nRFC 3214 LSP Modification Using CR-LDP January 2002","scope_keywords":["3214","key","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null}],"search_text":"IETF RFC 3214 This document presents an approach to modify the bandwidth and\n possibly other parameters of an established CR-LSP (Constraint-based\n Routed Label Switched Paths) using CR-LDP (Constraint-based Routed\n Label Distribution Protocol) without service interruption. After a\n CR-LSP is set up, its bandwidth reservation may need to be changed by\n the network operator, due to the new requirements for the traffic\n carried on that CR-LSP. The LSP modification feature can be\n supported by CR-LDP by use of the _modify_value for the _action\n indicator flag_ in the LSPID TLV. This feature has application in\n dynamic network resources management where traffic of different\n priorities and service classes is involved.\n\nAsh, et al. Standards Track [Page 1]\n\f\nRFC 3214 LSP Modification Using CR-LDP January 2002 3214 key management path pid nested-reference unchanged"},{"id":"IETF RFC 3233","type":"specification","body":"IETF","designation":"RFC 3233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3233.txt","https://www.rfc-editor.org/rfc/rfc3233.pdf"],"folder":"IETF/RFC-3233","files":{"txt":{"path":"standards/IETF/RFC-3233/RFC-3233.txt","sha256":"098266946e1ffad291acce4a2cf6af019ca59ec28820fbc464c00d5f8f5f2d15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman\nRequest for Comments: 3233 Internet Mail Consortium\nBCP: 58 S. Bradner\nCategory: Best Current Practice Harvard University\n February 2002\n\n Defining the IETF\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document gives a more concrete definition of \"the IETF\" as it\n understood today. Many RFCs refer to \"the IETF\". Many important\n IETF documents speak of the IETF as if it were an already-defined\n entity. However, no IETF document correctly defines what the IETF\n is.\n\n1. Introduction\n\n Many RFCs refer to \"the IETF\". Many important IETF documents speak\n of the IETF as if it were an already-defined e","scope_keywords":["3233","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null}],"search_text":"IETF RFC 3233 Network Working Group P. Hoffman\nRequest for Comments: 3233 Internet Mail Consortium\nBCP: 58 S. Bradner\nCategory: Best Current Practice Harvard University\n February 2002\n\n Defining the IETF\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document gives a more concrete definition of \"the IETF\" as it\n understood today. Many RFCs refer to \"the IETF\". Many important\n IETF documents speak of the IETF as if it were an already-defined\n entity. However, no IETF document correctly defines what the IETF\n is.\n\n1. Introduction\n\n Many RFCs refer to \"the IETF\". Many important IETF documents speak\n of the IETF as if it were an already-defined e 3233 trust nested-reference unchanged"},{"id":"IETF RFC 3237","type":"specification","body":"IETF","designation":"RFC 3237","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3237.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3237.txt","https://www.rfc-editor.org/rfc/rfc3237.pdf"],"folder":"IETF/RFC-3237","files":{"txt":{"path":"standards/IETF/RFC-3237/RFC-3237.txt","sha256":"113b3939c6b89c09da983537ec42add015553d7eb1505ff550cb7d84c27c3336"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a basic set of requirements for reliable server\n pooling.\n\n The goal of Reliable Server Pooling (RSerPool) is to develop an\n architecture and protocols for the management and operation of server\n pools supporting highly reliable applications, and for client access\n mechanisms to a server pool.\n\n1. Introduction","scope_keywords":["3237","algorithm","algorithms","delivery","management","policies","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null}],"search_text":"IETF RFC 3237 This document defines a basic set of requirements for reliable server\n pooling.\n\n The goal of Reliable Server Pooling (RSerPool) is to develop an\n architecture and protocols for the management and operation of server\n pools supporting highly reliable applications, and for client access\n mechanisms to a server pool.\n\n1. Introduction 3237 algorithm algorithms delivery management policies registered nested-reference unchanged"},{"id":"IETF RFC 3253","type":"specification","body":"IETF","designation":"RFC 3253","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3253.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3253.txt","https://www.rfc-editor.org/rfc/rfc3253.pdf"],"folder":"IETF/RFC-3253","files":{"txt":{"path":"standards/IETF/RFC-3253/RFC-3253.txt","sha256":"82b84e08eff50b7688db8919c6344b8402b9282b80e399149f64a422d8716246"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of methods, headers, and resource types\n that define the WebDAV (Web Distributed Authoring and Versioning)\n versioning extensions to the HTTP/1.1 protocol. WebDAV versioning\n will minimize the complexity of clients that are capable of\n interoperating with a variety of versioning repository managers, to\n facilitate widespread deployment of applications capable of utilizing\n the WebDAV Versioning services. WebDAV versioning includes automatic\n versioning for versioning-unaware clients, version history\n management, workspace management, baseline management, activity\n management, and URL namespace versioning.","scope_keywords":["3253","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 4331","folder":"IETF/RFC-4331","source":"IETF/RFC-4331/RFC-4331.txt","version":null},{"body":"IETF","designation":"RFC 4437","folder":"IETF/RFC-4437","source":"IETF/RFC-4437/RFC-4437.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5829","folder":"IETF/RFC-5829","source":"IETF/RFC-5829/RFC-5829.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null}],"search_text":"IETF RFC 3253 This document specifies a set of methods, headers, and resource types\n that define the WebDAV (Web Distributed Authoring and Versioning)\n versioning extensions to the HTTP/1.1 protocol. WebDAV versioning\n will minimize the complexity of clients that are capable of\n interoperating with a variety of versioning repository managers, to\n facilitate widespread deployment of applications capable of utilizing\n the WebDAV Versioning services. WebDAV versioning includes automatic\n versioning for versioning-unaware clients, version history\n management, workspace management, baseline management, activity\n management, and URL namespace versioning. 3253 http management nested-reference unchanged"},{"id":"IETF RFC 3306","type":"specification","body":"IETF","designation":"RFC 3306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3306.txt","https://www.rfc-editor.org/rfc/rfc3306.pdf"],"folder":"IETF/RFC-3306","files":{"txt":{"path":"standards/IETF/RFC-3306/RFC-3306.txt","sha256":"8c240b7c0edd3713c9fe878414515341f70721eee53d5a2cdda80524929cb565"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to the multicast addressing\n architecture of the IP Version 6 protocol. The extension presented\n in this document allows for unicast-prefix-based allocation of\n multicast addresses. By delegating multicast addresses at the same\n time as unicast prefixes, network operators will be able to identify\n their multicast addresses without needing to run an inter-domain\n allocation protocol.","scope_keywords":["3306","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3849","folder":"IETF/RFC-3849","source":"IETF/RFC-3849/RFC-3849.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3956","folder":"IETF/RFC-3956","source":"IETF/RFC-3956/RFC-3956.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null},{"body":"IETF","designation":"RFC 6177","folder":"IETF/RFC-6177","source":"IETF/RFC-6177/RFC-6177.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 3306 This specification defines an extension to the multicast addressing\n architecture of the IP Version 6 protocol. The extension presented\n in this document allows for unicast-prefix-based allocation of\n multicast addresses. By delegating multicast addresses at the same\n time as unicast prefixes, network operators will be able to identify\n their multicast addresses without needing to run an inter-domain\n allocation protocol. 3306 key policy nested-reference unchanged"},{"id":"IETF RFC 3313","type":"specification","body":"IETF","designation":"RFC 3313","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3313.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3313.txt","https://www.rfc-editor.org/rfc/rfc3313.pdf"],"folder":"IETF/RFC-3313","files":{"txt":{"path":"standards/IETF/RFC-3313/RFC-3313.txt","sha256":"12adcd29fe8c544254522eb8e10aa829bf5ad3b06812d1d561434025f3243fa7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the need for Quality of Service (QoS) and\n media authorization and defines a Session Initiation Protocol (SIP)\n extension that can be used to integrate QoS admission control with\n call signaling and help guard against denial of service attacks. The\n use of this extension is only applicable in administrative domains,\n or among federations of administrative domains with previously\n agreed-upon policies, where both the SIP proxy authorizing the QoS,\n and the policy control of the underlying network providing the QoS,\n belong to that administrative domain or federation of domains.\n\nMarshall, Ed. Informational [Page 1]\n\f\nRFC 3313 SIP Extensions for Media Authorization January 2003","scope_keywords":["3313","authorization","encryption","key","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null}],"search_text":"IETF RFC 3313 This document describes the need for Quality of Service (QoS) and\n media authorization and defines a Session Initiation Protocol (SIP)\n extension that can be used to integrate QoS admission control with\n call signaling and help guard against denial of service attacks. The\n use of this extension is only applicable in administrative domains,\n or among federations of administrative domains with previously\n agreed-upon policies, where both the SIP proxy authorizing the QoS,\n and the policy control of the underlying network providing the QoS,\n belong to that administrative domain or federation of domains.\n\nMarshall, Ed. Informational [Page 1]\n\f\nRFC 3313 SIP Extensions for Media Authorization January 2003 3313 authorization encryption key policies policy nested-reference unchanged"},{"id":"IETF RFC 3317","type":"specification","body":"IETF","designation":"RFC 3317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3317.txt","https://www.rfc-editor.org/rfc/rfc3317.pdf"],"folder":"IETF/RFC-3317","files":{"txt":{"path":"standards/IETF/RFC-3317/RFC-3317.txt","sha256":"873734b03e3b910945edf5935ffd5cde5657150de22085902f19d003c829cfe3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Policy Information Base (PIB) for a device\n implementing the Differentiated Services Architecture. The\n provisioning classes defined here provide policy control over\n resources implementing the Differentiated Services Architecture.\n These provisioning classes can be used with other none Differentiated\n Services provisioning classes (defined in other PIBs) to provide for\n a comprehensive policy controlled mapping of service requirement to\n device resource capability and usage.\n\nChan, et al. Informational [Page 1]\n\f\nRFC 3317 DiffServ QoS Policy Information Base March 2003","scope_keywords":["3317","algorithm","algorithms","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null}],"search_text":"IETF RFC 3317 This document describes a Policy Information Base (PIB) for a device\n implementing the Differentiated Services Architecture. The\n provisioning classes defined here provide policy control over\n resources implementing the Differentiated Services Architecture.\n These provisioning classes can be used with other none Differentiated\n Services provisioning classes (defined in other PIBs) to provide for\n a comprehensive policy controlled mapping of service requirement to\n device resource capability and usage.\n\nChan, et al. Informational [Page 1]\n\f\nRFC 3317 DiffServ QoS Policy Information Base March 2003 3317 algorithm algorithms key management path policy nested-reference unchanged"},{"id":"IETF RFC 3327","type":"specification","body":"IETF","designation":"RFC 3327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3327.txt","https://www.rfc-editor.org/rfc/rfc3327.pdf"],"folder":"IETF/RFC-3327","files":{"txt":{"path":"standards/IETF/RFC-3327/RFC-3327.txt","sha256":"4521cf2f0170d842b389c6d7ae9df4682ac4d4cb05a5ab7ebf1bcb9f7bab96aa"}},"tags":["nested-reference","unchanged"],"summary":"The REGISTER function is used in a Session Initiation Protocol (SIP)\n system primarily to associate a temporary contact address with an\n address-of-record. This contact is generally in the form of a\n Uniform Resource Identifier (URI), such as Contact:\n <sip:alice@pc33.atlanta.com> and is generally dynamic and associated\n with the IP address or hostname of the SIP User Agent (UA). The\n problem is that network topology may have one or more SIP proxies\n between the UA and the registrar, such that any request traveling\n from the user's home network to the registered UA must traverse these\n proxies. The REGISTER method does not give us a mechanism to\n discover and record this sequence of proxies in the registrar for\n future use. This document defines an extension header field, \"Path\"\n which provides such a mechanism.\n\nWillis & Hoeneisen Standards Track [Page 1]\n\f\nRFC 3327 Path Extension Heade","scope_keywords":["3327","key","path","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3581","folder":"IETF/RFC-3581","source":"IETF/RFC-3581/RFC-3581.txt","version":null},{"body":"IETF","designation":"RFC 3608","folder":"IETF/RFC-3608","source":"IETF/RFC-3608/RFC-3608.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null}],"search_text":"IETF RFC 3327 The REGISTER function is used in a Session Initiation Protocol (SIP)\n system primarily to associate a temporary contact address with an\n address-of-record. This contact is generally in the form of a\n Uniform Resource Identifier (URI), such as Contact:\n <sip:alice@pc33.atlanta.com> and is generally dynamic and associated\n with the IP address or hostname of the SIP User Agent (UA). The\n problem is that network topology may have one or more SIP proxies\n between the UA and the registrar, such that any request traveling\n from the user's home network to the registered UA must traverse these\n proxies. The REGISTER method does not give us a mechanism to\n discover and record this sequence of proxies in the registrar for\n future use. This document defines an extension header field, \"Path\"\n which provides such a mechanism.\n\nWillis & Hoeneisen Standards Track [Page 1]\n\f\nRFC 3327 Path Extension Heade 3327 key path policy registered nested-reference unchanged"},{"id":"IETF RFC 3347","type":"specification","body":"IETF","designation":"RFC 3347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3347.txt","https://www.rfc-editor.org/rfc/rfc3347.pdf"],"folder":"IETF/RFC-3347","files":{"txt":{"path":"standards/IETF/RFC-3347/RFC-3347.txt","sha256":"a6fb2bac742b07f4ab2133de9e471acdb2c7813bbca25b7ae71e168ab9c3c891"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements iSCSI and its related\n infrastructure should satisfy and the design considerations guiding\n the iSCSI protocol development efforts. In the interest of timely\n adoption of the iSCSI protocol, the IPS group has chosen to focus the\n first version of the protocol to work with the existing SCSI\n architecture and commands, and the existing TCP/IP transport layer.\n Both these protocols are widely-deployed and well-understood. The\n thought is that using these mature protocols will entail a minimum of\n new invention, the most rapid possible adoption, and the greatest\n compatibility with Internet architecture, protocols, and equipment.\n\nConventions used in this document\n\n This document describes the requirements for a protocol design, but\n does not define a protocol standard. Nevertheless, the key words\n \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",","scope_keywords":["3347","authentication","key","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3783","folder":"IETF/RFC-3783","source":"IETF/RFC-3783/RFC-3783.txt","version":null}],"search_text":"IETF RFC 3347 This document specifies the requirements iSCSI and its related\n infrastructure should satisfy and the design considerations guiding\n the iSCSI protocol development efforts. In the interest of timely\n adoption of the iSCSI protocol, the IPS group has chosen to focus the\n first version of the protocol to work with the existing SCSI\n architecture and commands, and the existing TCP/IP transport layer.\n Both these protocols are widely-deployed and well-understood. The\n thought is that using these mature protocols will entail a minimum of\n new invention, the most rapid possible adoption, and the greatest\n compatibility with Internet architecture, protocols, and equipment.\n\nConventions used in this document\n\n This document describes the requirements for a protocol design, but\n does not define a protocol standard. Nevertheless, the key words\n \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\", 3347 authentication key management pid nested-reference unchanged"},{"id":"IETF RFC 3356","type":"specification","body":"IETF","designation":"RFC 3356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3356.txt","https://www.rfc-editor.org/rfc/rfc3356.pdf"],"folder":"IETF/RFC-3356","files":{"txt":{"path":"standards/IETF/RFC-3356/RFC-3356.txt","sha256":"a1c0126a69afcf6ed6a866c7b342a4ee850aa9e2282614ec5a83db7422165854"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance to aid in the understanding of\n collaboration on standards development between the International\n Telecommunication Union -- Telecommunication Standardization Sector\n (ITU-T) and the Internet Society (ISOC) / Internet Engineering Task\n Force (IETF). It is an update of and obsoletes RFC 2436. The\n updates reflect changes in the IETF and ITU-T since RFC 2436 was\n written. The bulk of this document is common text with ITU-T\n Supplement 3 to the ITU-T A-Series Recommendations.\n\n Note: This was approved by ITU-T TSAG on 30 November 2001 as a\n Supplement to the ITU-T A-Series of Recommendations (will be numbered\n as A-Series Supplement 3).","scope_keywords":["3356","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4052","folder":"IETF/RFC-4052","source":"IETF/RFC-4052/RFC-4052.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null}],"search_text":"IETF RFC 3356 This document provides guidance to aid in the understanding of\n collaboration on standards development between the International\n Telecommunication Union -- Telecommunication Standardization Sector\n (ITU-T) and the Internet Society (ISOC) / Internet Engineering Task\n Force (IETF). It is an update of and obsoletes RFC 2436. The\n updates reflect changes in the IETF and ITU-T since RFC 2436 was\n written. The bulk of this document is common text with ITU-T\n Supplement 3 to the ITU-T A-Series Recommendations.\n\n Note: This was approved by ITU-T TSAG on 30 November 2001 as a\n Supplement to the ITU-T A-Series of Recommendations (will be numbered\n as A-Series Supplement 3). 3356 management presentation nested-reference unchanged"},{"id":"IETF RFC 3386","type":"specification","body":"IETF","designation":"RFC 3386","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3386.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3386.txt","https://www.rfc-editor.org/rfc/rfc3386.pdf"],"folder":"IETF/RFC-3386","files":{"txt":{"path":"standards/IETF/RFC-3386/RFC-3386.txt","sha256":"dd610a72285987ad992a97b054c88f1c283e4689b97c474c4b4cdbefb9625a62"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a proposal of the near-term and practical\n requirements for network survivability and hierarchy in current\n service provider environments.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].\n\nLai, et. al. Informational [Page 1]\n\f\nRFC 3386 Hierarchy & Multilayer Survivability November 2002","scope_keywords":["3386","driving","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4427","folder":"IETF/RFC-4427","source":"IETF/RFC-4427/RFC-4427.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 3386 This document presents a proposal of the near-term and practical\n requirements for network survivability and hierarchy in current\n service provider environments.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].\n\nLai, et. al. Informational [Page 1]\n\f\nRFC 3386 Hierarchy & Multilayer Survivability November 2002 3386 driving key path nested-reference unchanged"},{"id":"IETF RFC 3407","type":"specification","body":"IETF","designation":"RFC 3407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3407.txt","https://www.rfc-editor.org/rfc/rfc3407.pdf"],"folder":"IETF/RFC-3407","files":{"txt":{"path":"standards/IETF/RFC-3407/RFC-3407.txt","sha256":"3e378e6e1f0243028aa0839f6dcf2a62fb42a8e7d47c9874bb3bf8b275cc461c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Andreasen\nRequest for Comments: 3407 Cisco Systems\nCategory: Standards Track October 2002\n\n Session Description Protocol (SDP) Simple Capability Declaration\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines a set of Session Description Protocol (SDP)\n attributes that enables SDP to provide a minimal and backwards\n compatible capability declaration mechanism. Such capability\n declarations can be used as input to a subsequent session\n negotia","scope_keywords":["3407","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 3407 Network Working Group F. Andreasen\nRequest for Comments: 3407 Cisco Systems\nCategory: Standards Track October 2002\n\n Session Description Protocol (SDP) Simple Capability Declaration\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines a set of Session Description Protocol (SDP)\n attributes that enables SDP to provide a minimal and backwards\n compatible capability declaration mechanism. Such capability\n declarations can be used as input to a subsequent session\n negotia 3407 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 3427","type":"specification","body":"IETF","designation":"RFC 3427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3427.txt","https://www.rfc-editor.org/rfc/rfc3427.pdf"],"folder":"IETF/RFC-3427","files":{"txt":{"path":"standards/IETF/RFC-3427/RFC-3427.txt","sha256":"0e507e9c3c66f73e9b3f0f1d860ba240e922963a4118c896264a4a866d18095e"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents a process intended to apply architectural\n discipline to the future development of the Session Initiation\n Protocol (SIP). There have been concerns with regards to new SIP\n proposals. Specifically, that the addition of new SIP features can\n be damaging towards security and/or greatly increase the complexity\n of the protocol. The Transport Area directors, along with the SIP\n and Session Initiation Proposal Investigation (SIPPING) working group\n chairs, have provided suggestions for SIP modifications and\n extensions.\n\n1. Terminology\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"SHOULD\",\n and \"SHOULD NOT\", are to be interpreted as described in Keywords [1].\n\nMankin, et. al. Best Current Practice [Page 1]\n\f\nRFC 3427 Change Process for SIP December 2002\n\n2. History and Development\n\n The IETF's Session Initiation Protocol (SIP) [3] was originally\n developed f","scope_keywords":["3427","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3608","folder":"IETF/RFC-3608","source":"IETF/RFC-3608/RFC-3608.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 3969","folder":"IETF/RFC-3969","source":"IETF/RFC-3969/RFC-3969.txt","version":null},{"body":"IETF","designation":"RFC 4053","folder":"IETF/RFC-4053","source":"IETF/RFC-4053/RFC-4053.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 3427 This memo documents a process intended to apply architectural\n discipline to the future development of the Session Initiation\n Protocol (SIP). There have been concerns with regards to new SIP\n proposals. Specifically, that the addition of new SIP features can\n be damaging towards security and/or greatly increase the complexity\n of the protocol. The Transport Area directors, along with the SIP\n and Session Initiation Proposal Investigation (SIPPING) working group\n chairs, have provided suggestions for SIP modifications and\n extensions.\n\n1. Terminology\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"SHOULD\",\n and \"SHOULD NOT\", are to be interpreted as described in Keywords [1].\n\nMankin, et. al. Best Current Practice [Page 1]\n\f\nRFC 3427 Change Process for SIP December 2002\n\n2. History and Development\n\n The IETF's Session Initiation Protocol (SIP) [3] was originally\n developed f 3427 key management nested-reference unchanged"},{"id":"IETF RFC 3434","type":"specification","body":"IETF","designation":"RFC 3434","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3434.txt","https://www.rfc-editor.org/rfc/rfc3434.pdf"],"folder":"IETF/RFC-3434","files":{"txt":{"path":"standards/IETF/RFC-3434/RFC-3434.txt","sha256":"abe33d49f7af9b7341f005d2d047ec21127e1dcba9d11496ebc9b70d9b510059"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for extending the alarm\n thresholding capabilities found in the Remote Monitoring (RMON) MIB\n (RFC 2819), to provide similar threshold monitoring of objects based\n on the Counter64 data type.","scope_keywords":["3434","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3577","folder":"IETF/RFC-3577","source":"IETF/RFC-3577/RFC-3577.txt","version":null},{"body":"IETF","designation":"RFC 3737","folder":"IETF/RFC-3737","source":"IETF/RFC-3737/RFC-3737.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3434 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for extending the alarm\n thresholding capabilities found in the Remote Monitoring (RMON) MIB\n (RFC 2819), to provide similar threshold monitoring of objects based\n on the Counter64 data type. 3434 key management nested-reference unchanged"},{"id":"IETF RFC 3436","type":"specification","body":"IETF","designation":"RFC 3436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3436.txt","https://www.rfc-editor.org/rfc/rfc3436.pdf"],"folder":"IETF/RFC-3436","files":{"txt":{"path":"standards/IETF/RFC-3436/RFC-3436.txt","sha256":"a09a9e9802ecc0790b4a908705c23ba0e2e3250cdbccac636afbb49d7fd758bf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of the Transport Layer Security\n (TLS) protocol, as defined in RFC 2246, over the Stream Control\n Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309.\n\n The user of TLS can take advantage of the features provided by SCTP,\n namely the support of multiple streams to avoid head of line blocking\n and the support of multi-homing to provide network level fault\n tolerance.\n\n Additionally, discussions of extensions of SCTP are also supported,\n meaning especially the support of dynamic reconfiguration of IP-\n addresses.\n\nJungmaier, et al. Standards Track [Page 1]\n\f\nRFC 3436 TLS over SCTP December 2002\n\n1. Introduction","scope_keywords":["3436","delivery","http","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3758","folder":"IETF/RFC-3758","source":"IETF/RFC-3758/RFC-3758.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3436 This document describes the usage of the Transport Layer Security\n (TLS) protocol, as defined in RFC 2246, over the Stream Control\n Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309.\n\n The user of TLS can take advantage of the features provided by SCTP,\n namely the support of multiple streams to avoid head of line blocking\n and the support of multi-homing to provide network level fault\n tolerance.\n\n Additionally, discussions of extensions of SCTP are also supported,\n meaning especially the support of dynamic reconfiguration of IP-\n addresses.\n\nJungmaier, et al. Standards Track [Page 1]\n\f\nRFC 3436 TLS over SCTP December 2002\n\n1. Introduction 3436 delivery http key tls nested-reference unchanged"},{"id":"IETF RFC 3444","type":"specification","body":"IETF","designation":"RFC 3444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3444.txt","https://www.rfc-editor.org/rfc/rfc3444.pdf"],"folder":"IETF/RFC-3444","files":{"txt":{"path":"standards/IETF/RFC-3444/RFC-3444.txt","sha256":"c2f2e05d8b0287a71b65e8537ce2bb0320624393bc088dc91077c81473753ccd"}},"tags":["nested-reference","unchanged"],"summary":"There has been ongoing confusion about the differences between\n Information Models and Data Models for defining managed objects in\n network management. This document explains the differences between\n these terms by analyzing how existing network management model\n specifications (from the IETF and other bodies such as the\n International Telecommunication Union (ITU) or the Distributed\n Management Task Force (DMTF)) fit into the universe of Information\n Models and Data Models.\n\n This memo documents the main results of the 8th workshop of the\n Network Management Research Group (NMRG) of the Internet Research\n Task Force (IRTF) hosted by the University of Texas at Austin.","scope_keywords":["3444","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7632","folder":"IETF/RFC-7632","source":"IETF/RFC-7632/RFC-7632.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"IETF RFC 3444 There has been ongoing confusion about the differences between\n Information Models and Data Models for defining managed objects in\n network management. This document explains the differences between\n these terms by analyzing how existing network management model\n specifications (from the IETF and other bodies such as the\n International Telecommunication Union (ITU) or the Distributed\n Management Task Force (DMTF)) fit into the universe of Information\n Models and Data Models.\n\n This memo documents the main results of the 8th workshop of the\n Network Management Research Group (NMRG) of the Internet Research\n Task Force (IRTF) hosted by the University of Texas at Austin. 3444 key management policy nested-reference unchanged"},{"id":"IETF RFC 3453","type":"specification","body":"IETF","designation":"RFC 3453","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3453.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3453.txt","https://www.rfc-editor.org/rfc/rfc3453.pdf"],"folder":"IETF/RFC-3453","files":{"txt":{"path":"standards/IETF/RFC-3453/RFC-3453.txt","sha256":"c957f3860cb44cf5514a510301caad0ad63b0c0b8ab50c19969c203ec59cac74"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of Forward Error Correction (FEC) codes\n to efficiently provide and/or augment reliability for one-to-many\n reliable data transport using IP multicast. One of the key\n properties of FEC codes in this context is the ability to use the\n same packets containing FEC data to simultaneously repair different\n packet loss patterns at multiple receivers. Different classes of FEC\n codes and some of their basic properties are described and\n terminology relevant to implementing FEC in a reliable multicast\n protocol is introduced. Examples are provided of possible abstract\n formats for packets carrying FEC.\n\nLuby, et. al. Informational [Page 1]\n\f\nRFC 3453 FEC in Reliable Multicast December 2002","scope_keywords":["3453","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 3453 This memo describes the use of Forward Error Correction (FEC) codes\n to efficiently provide and/or augment reliability for one-to-many\n reliable data transport using IP multicast. One of the key\n properties of FEC codes in this context is the ability to use the\n same packets containing FEC data to simultaneously repair different\n packet loss patterns at multiple receivers. Different classes of FEC\n codes and some of their basic properties are described and\n terminology relevant to implementing FEC in a reliable multicast\n protocol is introduced. Examples are provided of possible abstract\n formats for packets carrying FEC.\n\nLuby, et. al. Informational [Page 1]\n\f\nRFC 3453 FEC in Reliable Multicast December 2002 3453 authentication key nested-reference unchanged"},{"id":"IETF RFC 3458","type":"specification","body":"IETF","designation":"RFC 3458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3458.txt","https://www.rfc-editor.org/rfc/rfc3458.pdf"],"folder":"IETF/RFC-3458","files":{"txt":{"path":"standards/IETF/RFC-3458/RFC-3458.txt","sha256":"c4128ceb38f80c0aad16fd270435abb76c75a819f3d520d2c47132bad468d7d1"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a new RFC 2822 message header, \"Message-Context\".\n This header provides information about the context and presentation\n characteristics of a message.\n\n A receiving user agent (UA) may use this information as a hint to\n optimally present the message.\n\nBurger, et al. Standards Track [Page 1]\n\f\nRFC 3458 Message Context for Internet Mail January 2003","scope_keywords":["3458","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 3458 This memo describes a new RFC 2822 message header, \"Message-Context\".\n This header provides information about the context and presentation\n characteristics of a message.\n\n A receiving user agent (UA) may use this information as a hint to\n optimally present the message.\n\nBurger, et al. Standards Track [Page 1]\n\f\nRFC 3458 Message Context for Internet Mail January 2003 3458 key presentation nested-reference unchanged"},{"id":"IETF RFC 3468","type":"specification","body":"IETF","designation":"RFC 3468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3468.txt","https://www.rfc-editor.org/rfc/rfc3468.pdf"],"folder":"IETF/RFC-3468","files":{"txt":{"path":"standards/IETF/RFC-3468/RFC-3468.txt","sha256":"635d5ad6b148db13b2ead4f3050b95bddd05d1ab4e54300b8a427c4fd8a605db"}},"tags":["nested-reference","unchanged"],"summary":"This document documents the consensus reached by the Multiprotocol\n Label Switching (MPLS) Working Group within the IETF to focus its\n efforts on \"Resource Reservation Protocol (RSVP)-TE: Extensions to\n RSVP for Label-Switched Paths (LSP) Tunnels\" (RFC 3209) as the MPLS\n signalling protocol for traffic engineering applications and to\n undertake no new efforts relating to \"Constraint-Based LSP Setup\n using Label Distribution Protocol (LDP)\" (RFC 3212). The\n recommendations of section 6 have been accepted by the IESG.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\nAndersson & Swallow Informational [Page 1]\n\f\nRFC 3468 Decision on MPLS Signaling Protocols February 2003","scope_keywords":["3468","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null}],"search_text":"IETF RFC 3468 This document documents the consensus reached by the Multiprotocol\n Label Switching (MPLS) Working Group within the IETF to focus its\n efforts on \"Resource Reservation Protocol (RSVP)-TE: Extensions to\n RSVP for Label-Switched Paths (LSP) Tunnels\" (RFC 3209) as the MPLS\n signalling protocol for traffic engineering applications and to\n undertake no new efforts relating to \"Constraint-Based LSP Setup\n using Label Distribution Protocol (LDP)\" (RFC 3212). The\n recommendations of section 6 have been accepted by the IESG.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\nAndersson & Swallow Informational [Page 1]\n\f\nRFC 3468 Decision on MPLS Signaling Protocols February 2003 3468 key path nested-reference unchanged"},{"id":"IETF RFC 3471","type":"specification","body":"IETF","designation":"RFC 3471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3471.txt","https://www.rfc-editor.org/rfc/rfc3471.pdf"],"folder":"IETF/RFC-3471","files":{"txt":{"path":"standards/IETF/RFC-3471/RFC-3471.txt","sha256":"41066bf2dfa56e443718b14027d9710801310cd6961e52a98e628fb0baf728cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to Multi-Protocol Label Switching\n (MPLS) signaling required to support Generalized MPLS. Generalized\n MPLS extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a functional description of the extensions. Protocol\n specific formats and mechanisms, and technology specific details are\n specified in separate documents.","scope_keywords":["3471","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3477","folder":"IETF/RFC-3477","source":"IETF/RFC-3477/RFC-3477.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4003","folder":"IETF/RFC-4003","source":"IETF/RFC-4003/RFC-4003.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4139","folder":"IETF/RFC-4139","source":"IETF/RFC-4139/RFC-4139.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 3471 This document describes extensions to Multi-Protocol Label Switching\n (MPLS) signaling required to support Generalized MPLS. Generalized\n MPLS extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a functional description of the extensions. Protocol\n specific formats and mechanisms, and technology specific details are\n specified in separate documents. 3471 identification key path nested-reference unchanged"},{"id":"IETF RFC 3472","type":"specification","body":"IETF","designation":"RFC 3472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3472.txt","https://www.rfc-editor.org/rfc/rfc3472.pdf"],"folder":"IETF/RFC-3472","files":{"txt":{"path":"standards/IETF/RFC-3472/RFC-3472.txt","sha256":"4e7176b3c6007802d133f98526f1be82cb3185a1d0cb65058224d34b5d52f7e2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to Multi-Protocol Label Switching\n (MPLS) Constraint-based Routed Label Distribution Protocol (CR-LDP)\n signaling required to support Generalized MPLS. Generalized MPLS\n extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a CR-LDP specific description of the extensions. A generic\n functional description can be found in separate documents.","scope_keywords":["3472","identification","key","path","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null}],"search_text":"IETF RFC 3472 This document describes extensions to Multi-Protocol Label Switching\n (MPLS) Constraint-based Routed Label Distribution Protocol (CR-LDP)\n signaling required to support Generalized MPLS. Generalized MPLS\n extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a CR-LDP specific description of the extensions. A generic\n functional description can be found in separate documents. 3472 identification key path pid policy nested-reference unchanged"},{"id":"IETF RFC 3473","type":"specification","body":"IETF","designation":"RFC 3473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3473.txt","https://www.rfc-editor.org/rfc/rfc3473.pdf"],"folder":"IETF/RFC-3473","files":{"txt":{"path":"standards/IETF/RFC-3473/RFC-3473.txt","sha256":"cad81be58df4e274da5300a7ee5ed16eaf406d6530576b40bac1b913cf64f636"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to Multi-Protocol Label Switching\n (MPLS) Resource ReserVation Protocol - Traffic Engineering (RSVP-TE)\n signaling required to support Generalized MPLS. Generalized MPLS\n extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a RSVP-TE specific description of the extensions. A generic\n functional description can be found in separate documents.","scope_keywords":["3473","identification","key","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3476","folder":"IETF/RFC-3476","source":"IETF/RFC-3476/RFC-3476.txt","version":null},{"body":"IETF","designation":"RFC 3477","folder":"IETF/RFC-3477","source":"IETF/RFC-3477/RFC-3477.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4003","folder":"IETF/RFC-4003","source":"IETF/RFC-4003/RFC-4003.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4139","folder":"IETF/RFC-4139","source":"IETF/RFC-4139/RFC-4139.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 3473 This document describes extensions to Multi-Protocol Label Switching\n (MPLS) Resource ReserVation Protocol - Traffic Engineering (RSVP-TE)\n signaling required to support Generalized MPLS. Generalized MPLS\n extends the MPLS control plane to encompass time-division (e.g.,\n Synchronous Optical Network and Synchronous Digital Hierarchy,\n SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g.,\n incoming port or fiber to outgoing port or fiber). This document\n presents a RSVP-TE specific description of the extensions. A generic\n functional description can be found in separate documents. 3473 identification key path pid nested-reference unchanged"},{"id":"IETF RFC 3474","type":"specification","body":"IETF","designation":"RFC 3474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3474.txt","https://www.rfc-editor.org/rfc/rfc3474.pdf"],"folder":"IETF/RFC-3474","files":{"txt":{"path":"standards/IETF/RFC-3474/RFC-3474.txt","sha256":"bef469e0146689c10d176f71415b5511cee5f53b84405726a4ebcfec26586680"}},"tags":["nested-reference","unchanged"],"summary":"The Generalized MultiProtocol Label Switching (GMPLS) suite of\n protocol specifications has been defined to provide support for\n different technologies as well as different applications. These\n include support for requesting TDM connections based on Synchronous\n Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) as well as\n Optical Transport Networks (OTNs).\n\n This document concentrates on the signaling aspects of the GMPLS\n suite of protocols, specifically GMPLS signaling using Resource\n Reservation Protocol - Traffic Engineering (RSVP-TE). It proposes\n additional extensions to these signaling protocols to support the\n capabilities of an ASON network.\n\n This document proposes appropriate extensions towards the resolution\n of additional requirements identified and communicated by the ITU-T\n Study Group 15 in support of ITU's ASON standardization effort.\n\nLin & Pendarakis Informati","scope_keywords":["3474","attribute","attributes","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null}],"search_text":"IETF RFC 3474 The Generalized MultiProtocol Label Switching (GMPLS) suite of\n protocol specifications has been defined to provide support for\n different technologies as well as different applications. These\n include support for requesting TDM connections based on Synchronous\n Optical NETwork/Synchronous Digital Hierarchy (SONET/SDH) as well as\n Optical Transport Networks (OTNs).\n\n This document concentrates on the signaling aspects of the GMPLS\n suite of protocols, specifically GMPLS signaling using Resource\n Reservation Protocol - Traffic Engineering (RSVP-TE). It proposes\n additional extensions to these signaling protocols to support the\n capabilities of an ASON network.\n\n This document proposes appropriate extensions towards the resolution\n of additional requirements identified and communicated by the ITU-T\n Study Group 15 in support of ITU's ASON standardization effort.\n\nLin & Pendarakis Informati 3474 attribute attributes key management path policy nested-reference unchanged"},{"id":"IETF RFC 3478","type":"specification","body":"IETF","designation":"RFC 3478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3478.txt","https://www.rfc-editor.org/rfc/rfc3478.pdf"],"folder":"IETF/RFC-3478","files":{"txt":{"path":"standards/IETF/RFC-3478/RFC-3478.txt","sha256":"30332a6eafffef6f836a2324c0e0b7764d1232fa99ee9d992b58868b10cf6ffe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that helps to minimize the\n negative effects on MPLS traffic caused by Label Switching Router's\n (LSR's) control plane restart, specifically by the restart of its\n Label Distribution Protocol (LDP) component, on LSRs that are capable\n of preserving the MPLS forwarding component across the restart.\n\n The mechanism described in this document is applicable to all LSRs,\n both those with the ability to preserve forwarding state during LDP\n restart and those without (although the latter needs to implement\n only a subset of the mechanism described in this document).\n Supporting (a subset of) the mechanism described here by the LSRs\n that can not preserve their MPLS forwarding state across the restart\n would not reduce the negative impact on MPLS traffic caused by their\n control plane restart, but it would minimize the impact if their\n neighbor(s) are capable ","scope_keywords":["3478","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null}],"search_text":"IETF RFC 3478 This document describes a mechanism that helps to minimize the\n negative effects on MPLS traffic caused by Label Switching Router's\n (LSR's) control plane restart, specifically by the restart of its\n Label Distribution Protocol (LDP) component, on LSRs that are capable\n of preserving the MPLS forwarding component across the restart.\n\n The mechanism described in this document is applicable to all LSRs,\n both those with the ability to preserve forwarding state during LDP\n restart and those without (although the latter needs to implement\n only a subset of the mechanism described in this document).\n Supporting (a subset of) the mechanism described here by the LSRs\n that can not preserve their MPLS forwarding state across the restart\n would not reduce the negative impact on MPLS traffic caused by their\n control plane restart, but it would minimize the impact if their\n neighbor(s) are capable  3478 key nested-reference unchanged"},{"id":"IETF RFC 3479","type":"specification","body":"IETF","designation":"RFC 3479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3479.txt","https://www.rfc-editor.org/rfc/rfc3479.pdf"],"folder":"IETF/RFC-3479","files":{"txt":{"path":"standards/IETF/RFC-3479/RFC-3479.txt","sha256":"73bcefe6c9d6ed3ddc5c8be2a2b6669b37733475abde4598a2fc63ad4bb509d4"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol Label Switching (MPLS) systems will be used in core\n networks where system downtime must be kept to an absolute minimum.\n Many MPLS Label Switching Routers (LSRs) may, therefore, exploit\n Fault Tolerant (FT) hardware or software to provide high availability\n of the core networks.\n\n The details of how FT is achieved for the various components of an FT\n LSR, including Label Distribution Protocol (LDP), the switching\n hardware and TCP, are implementation specific. This document\n identifies issues in the LDP specification in RFC 3036, \"LDP\n Specification\", that make it difficult to implement an FT LSR using\n the current LDP protocols, and defines enhancements to the LDP\n specification to ease such FT LSR implementations.\n\nFarrel Standards Track [Page 1]\n\f\nRFC 3479 Fault Tolerance for the LDP February 2003\n\n The issues and extensions described here are equally applicable to\n RFC","scope_keywords":["3479","key","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3478","folder":"IETF/RFC-3478","source":"IETF/RFC-3478/RFC-3478.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null}],"search_text":"IETF RFC 3479 Multiprotocol Label Switching (MPLS) systems will be used in core\n networks where system downtime must be kept to an absolute minimum.\n Many MPLS Label Switching Routers (LSRs) may, therefore, exploit\n Fault Tolerant (FT) hardware or software to provide high availability\n of the core networks.\n\n The details of how FT is achieved for the various components of an FT\n LSR, including Label Distribution Protocol (LDP), the switching\n hardware and TCP, are implementation specific. This document\n identifies issues in the LDP specification in RFC 3036, \"LDP\n Specification\", that make it difficult to implement an FT LSR using\n the current LDP protocols, and defines enhancements to the LDP\n specification to ease such FT LSR implementations.\n\nFarrel Standards Track [Page 1]\n\f\nRFC 3479 Fault Tolerance for the LDP February 2003\n\n The issues and extensions described here are equally applicable to\n RFC 3479 key preservation nested-reference unchanged"},{"id":"IETF RFC 3482","type":"specification","body":"IETF","designation":"RFC 3482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3482.txt","https://www.rfc-editor.org/rfc/rfc3482.pdf"],"folder":"IETF/RFC-3482","files":{"txt":{"path":"standards/IETF/RFC-3482/RFC-3482.txt","sha256":"7bb0cfe7a7b89b6e87a24d3b72b540fb33fa99bdfc26c5610b56469171187be7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of E.164 telephone number\n portability (NP) in the Global Switched Telephone Network (GSTN).\n NP is a regulatory imperative seeking to liberalize local telephony\n service competition, by enabling end-users to retain telephone\n numbers while changing service providers. NP changes the fundamental\n nature of a dialed E.164 number from a hierarchical physical routing\n address to a virtual address, thereby requiring the transparent\n translation of the later to the former. In addition, there are\n various regulatory constraints that establish relevant parameters for\n NP implementation, most of which are not network technology specific.\n Consequently, the implementation of NP behavior consistent with\n applicable regulatory constraints, as well as the need for\n interoperation with the existing GSTN NP implementations, are\n relevant topics for numerous areas of I","scope_keywords":["3482","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null}],"search_text":"IETF RFC 3482 This document provides an overview of E.164 telephone number\n portability (NP) in the Global Switched Telephone Network (GSTN).\n NP is a regulatory imperative seeking to liberalize local telephony\n service competition, by enabling end-users to retain telephone\n numbers while changing service providers. NP changes the fundamental\n nature of a dialed E.164 number from a hierarchical physical routing\n address to a virtual address, thereby requiring the transparent\n translation of the later to the former. In addition, there are\n various regulatory constraints that establish relevant parameters for\n NP implementation, most of which are not network technology specific.\n Consequently, the implementation of NP behavior consistent with\n applicable regulatory constraints, as well as the need for\n interoperation with the existing GSTN NP implementations, are\n relevant topics for numerous areas of I 3482 management nested-reference unchanged"},{"id":"IETF RFC 3563","type":"specification","body":"IETF","designation":"RFC 3563","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3563.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3563.txt","https://www.rfc-editor.org/rfc/rfc3563.pdf"],"folder":"IETF/RFC-3563","files":{"txt":{"path":"standards/IETF/RFC-3563/RFC-3563.txt","sha256":"5cb70a470634f8a5376a3b19d18d9256efe4aa1be20893fde889098d4dd63cb1"}},"tags":["nested-reference","unchanged"],"summary":"This document contains the text of the agreement signed between\n ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative development of\n the IS-IS routing protocol. The agreement includes definitions of\n the related work scopes for the two organizations, request for\n creation and maintenance of an IS-IS registry by IANA, as well as\n collaboration guidelines.\n\nDocument Header\n\n Annexe 1 to Cooperative Agreement Between the Internet Society and\n the International Organization for Standardization / International\n Electrotechnical Commission / Joint Technical Committee 1 / Sub\n Committee 6 (ISO/IEC JTC1/SC6): IS-IS Routing Protocols\n\n Date: 2003-01-28\n\n This annexe records the agreed collaborative process for the further\n development and standardisation of the Intermediate System to\n Intermediate System (IS-IS) intra-domain routing protocol (ISO/IEC\n 10589).\n\n1. Introduction\n\n The IS-IS intra-d","scope_keywords":["3563","algorithm","algorithms","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null}],"search_text":"IETF RFC 3563 This document contains the text of the agreement signed between\n ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative development of\n the IS-IS routing protocol. The agreement includes definitions of\n the related work scopes for the two organizations, request for\n creation and maintenance of an IS-IS registry by IANA, as well as\n collaboration guidelines.\n\nDocument Header\n\n Annexe 1 to Cooperative Agreement Between the Internet Society and\n the International Organization for Standardization / International\n Electrotechnical Commission / Joint Technical Committee 1 / Sub\n Committee 6 (ISO/IEC JTC1/SC6): IS-IS Routing Protocols\n\n Date: 2003-01-28\n\n This annexe records the agreed collaborative process for the further\n development and standardisation of the Intermediate System to\n Intermediate System (IS-IS) intra-domain routing protocol (ISO/IEC\n 10589).\n\n1. Introduction\n\n The IS-IS intra-d 3563 algorithm algorithms management subject nested-reference unchanged"},{"id":"IETF RFC 3566","type":"specification","body":"IETF","designation":"RFC 3566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3566.txt","https://www.rfc-editor.org/rfc/rfc3566.pdf"],"folder":"IETF/RFC-3566","files":{"txt":{"path":"standards/IETF/RFC-3566/RFC-3566.txt","sha256":"fcc296d41cd998bd30d44fe786aa4db836ac2f6a287f8784f9b968428eb47d25"}},"tags":["nested-reference","unchanged"],"summary":"A Message Authentication Code (MAC) is a key-dependent one way hash\n function. One popular way to construct a MAC algorithm is to use a\n block cipher in conjunction with the Cipher-Block-Chaining (CBC) mode\n of operation. The classic CBC-MAC algorithm, while secure for\n messages of a pre-selected fixed length, has been shown to be\n insecure across messages of varying lengths such as the type found in\n typical IP datagrams. This memo specifies the use of AES in CBC mode\n with a set of extensions to overcome this limitation. This new\n algorithm is named AES-XCBC-MAC-96.","scope_keywords":["3566","algorithm","authentication","encryption","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3664","folder":"IETF/RFC-3664","source":"IETF/RFC-3664/RFC-3664.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4434","folder":"IETF/RFC-4434","source":"IETF/RFC-4434/RFC-4434.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 3566 A Message Authentication Code (MAC) is a key-dependent one way hash\n function. One popular way to construct a MAC algorithm is to use a\n block cipher in conjunction with the Cipher-Block-Chaining (CBC) mode\n of operation. The classic CBC-MAC algorithm, while secure for\n messages of a pre-selected fixed length, has been shown to be\n insecure across messages of varying lengths such as the type found in\n typical IP datagrams. This memo specifies the use of AES in CBC mode\n with a set of extensions to overcome this limitation. This new\n algorithm is named AES-XCBC-MAC-96. 3566 algorithm authentication encryption hash key nested-reference unchanged"},{"id":"IETF RFC 3589","type":"specification","body":"IETF","designation":"RFC 3589","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3589.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3589.txt","https://www.rfc-editor.org/rfc/rfc3589.pdf"],"folder":"IETF/RFC-3589","files":{"txt":{"path":"standards/IETF/RFC-3589/RFC-3589.txt","sha256":"0d994aadf67b5352293b828cb88d12d9e6bc524bcaedd594230b01cdf647474e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the IANA's allocation of a block of Diameter\n Command Codes for the Third Generation Partnership Project (3GPP)\n Release 5. This document does not pass judgment on the usage of\n these command codes. Further more, these command codes are for use\n for Release 5. For future releases, these codes cannot be reused,\n but must be allocated according to the Diameter Base specification.","scope_keywords":["3589","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3589 This document describes the IANA's allocation of a block of Diameter\n Command Codes for the Third Generation Partnership Project (3GPP)\n Release 5. This document does not pass judgment on the usage of\n these command codes. Further more, these command codes are for use\n for Release 5. For future releases, these codes cannot be reused,\n but must be allocated according to the Diameter Base specification. 3589 license nested-reference unchanged"},{"id":"IETF RFC 3643","type":"specification","body":"IETF","designation":"RFC 3643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3643.txt","https://www.rfc-editor.org/rfc/rfc3643.pdf"],"folder":"IETF/RFC-3643","files":{"txt":{"path":"standards/IETF/RFC-3643/RFC-3643.txt","sha256":"57dbb01aefbe5095aee25be57096588008e97a589c6e5cb0426470597e0c02e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the common Fibre Channel (FC) frame\n encapsulation format and a procedure for the measurement and\n calculation of frame transit time through the IP network. This\n specification is intended for use by any IETF protocol that\n encapsulates FC frames.\n\nWeber, et al. Standards Track [Page 1]\n\f\nRFC 3643 FC Frame Encapsulation December 2003","scope_keywords":["3643","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null}],"search_text":"IETF RFC 3643 This document describes the common Fibre Channel (FC) frame\n encapsulation format and a procedure for the measurement and\n calculation of frame transit time through the IP network. This\n specification is intended for use by any IETF protocol that\n encapsulates FC frames.\n\nWeber, et al. Standards Track [Page 1]\n\f\nRFC 3643 FC Frame Encapsulation December 2003 3643 key validation nested-reference unchanged"},{"id":"IETF RFC 3667","type":"specification","body":"IETF","designation":"RFC 3667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3667.txt","https://www.rfc-editor.org/rfc/rfc3667.pdf"],"folder":"IETF/RFC-3667","files":{"txt":{"path":"standards/IETF/RFC-3667/RFC-3667.txt","sha256":"f01b0192e5865b77f18f52a2d1afa11cf22b8c06c0d1769d37ecd72e7aa52adc"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n updates RFC 2026, and, with RFC 3668, replaces Section 10 of RFC\n 2026.","scope_keywords":["3667","policies","policy","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3668","folder":"IETF/RFC-3668","source":"IETF/RFC-3668/RFC-3668.txt","version":null},{"body":"IETF","designation":"RFC 3669","folder":"IETF/RFC-3669","source":"IETF/RFC-3669/RFC-3669.txt","version":null},{"body":"IETF","designation":"RFC 3933","folder":"IETF/RFC-3933","source":"IETF/RFC-3933/RFC-3933.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null}],"search_text":"IETF RFC 3667 The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n updates RFC 2026, and, with RFC 3668, replaces Section 10 of RFC\n 2026. 3667 policies policy presentation subject nested-reference unchanged"},{"id":"IETF RFC 3683","type":"specification","body":"IETF","designation":"RFC 3683","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3683.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3683.txt","https://www.rfc-editor.org/rfc/rfc3683.pdf"],"folder":"IETF/RFC-3683","files":{"txt":{"path":"standards/IETF/RFC-3683/RFC-3683.txt","sha256":"78efe3ca5b3857162eab6dd7bbd4d8dbff90832d08f580fa87d284320bfc2159"}},"tags":["nested-reference","unchanged"],"summary":"All self-governing bodies have ways of managing the scope of\n participant interaction. The IETF uses a consensus-driven process\n for developing computer-communications standards in an open fashion.\n An important part of this consensus-driven process is the pervasive\n use of mailing lists for discussion. Notably, in a small number of\n cases, a participant has engaged in a \"denial-of-service\" attack to\n disrupt the consensus-driven process. Regrettably, as these bad\n faith attacks become more common, the IETF needs to establish a\n practice that reduces or eliminates these attacks. This memo\n recommends such a practice for use by the IETF.\n\nRose Best Current Practice [Page 1]\n\f\nRFC 3683 Revocation Practice: IETF Mailing Lists March 2004","scope_keywords":["3683","algorithm","holder","policy","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3934","folder":"IETF/RFC-3934","source":"IETF/RFC-3934/RFC-3934.txt","version":null},{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null}],"search_text":"IETF RFC 3683 All self-governing bodies have ways of managing the scope of\n participant interaction. The IETF uses a consensus-driven process\n for developing computer-communications standards in an open fashion.\n An important part of this consensus-driven process is the pervasive\n use of mailing lists for discussion. Notably, in a small number of\n cases, a participant has engaged in a \"denial-of-service\" attack to\n disrupt the consensus-driven process. Regrettably, as these bad\n faith attacks become more common, the IETF needs to establish a\n practice that reduces or eliminates these attacks. This memo\n recommends such a practice for use by the IETF.\n\nRose Best Current Practice [Page 1]\n\f\nRFC 3683 Revocation Practice: IETF Mailing Lists March 2004 3683 algorithm holder policy revocation subject nested-reference unchanged"},{"id":"IETF RFC 3690","type":"specification","body":"IETF","designation":"RFC 3690","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3690.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3690.txt","https://www.rfc-editor.org/rfc/rfc3690.pdf"],"folder":"IETF/RFC-3690","files":{"txt":{"path":"standards/IETF/RFC-3690/RFC-3690.txt","sha256":"00ace8c6cd116d8b093653f6cc9f8316a65c50cc8ad3d918745b7e5cc20a66b1"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a list of requirements in support of Emergency\n Telecommunications Service (ETS) within the context of IP telephony.\n It is an extension to the general requirements presented in RFC 3689.\n Solutions to these requirements are not presented in this document.\n\n1. Introduction\n\n Effective telecommunications capabilities can be imperative to\n facilitate immediate recovery operations for serious disaster events,\n such as, hurricanes, floods, earthquakes, and terrorist attacks.\n Disasters can happen unexpectedly, at any time or place. Quick\n response for recovery operations requires immediate access to any\n public telecommunications capabilities at hand. These capabilities\n include: conventional telephone, cellular phones, and Internet\n access via online terminals, IP telephones, and wireless Personal\n Digital Assistants (PDAs). The commercial telecommunications\n infrastr","scope_keywords":["3690","attribute","key","management","path","pid","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 3690 This document presents a list of requirements in support of Emergency\n Telecommunications Service (ETS) within the context of IP telephony.\n It is an extension to the general requirements presented in RFC 3689.\n Solutions to these requirements are not presented in this document.\n\n1. Introduction\n\n Effective telecommunications capabilities can be imperative to\n facilitate immediate recovery operations for serious disaster events,\n such as, hurricanes, floods, earthquakes, and terrorist attacks.\n Disasters can happen unexpectedly, at any time or place. Quick\n response for recovery operations requires immediate access to any\n public telecommunications capabilities at hand. These capabilities\n include: conventional telephone, cellular phones, and Internet\n access via online terminals, IP telephones, and wireless Personal\n Digital Assistants (PDAs). The commercial telecommunications\n infrastr 3690 attribute key management path pid policy subject nested-reference unchanged"},{"id":"IETF RFC 3695","type":"specification","body":"IETF","designation":"RFC 3695","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3695.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3695.txt","https://www.rfc-editor.org/rfc/rfc3695.pdf"],"folder":"IETF/RFC-3695","files":{"txt":{"path":"standards/IETF/RFC-3695/RFC-3695.txt","sha256":"d8eec0204dc7da446da0e94b9739ae421418079b729485e0aa93fbed3ec57fe9"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces some Forward Error Correction (FEC) schemes\n that supplement the FEC schemes described in RFC 3452. The primary\n benefits of these additional FEC schemes are that they are designed\n for reliable bulk delivery of large objects using a more compact FEC\n Payload ID, and they can be used to sequentially deliver blocks of an\n object of indeterminate length. Thus, they more flexibly support\n different delivery models with less packet header overhead.\n\n This document also describes the Fully-Specified FEC scheme\n corresponding to FEC Encoding ID 0. This Fully-Specified FEC scheme\n requires no FEC coding and is introduced primarily to allow simple\n interoperability testing between different implementations of\n protocol instantiations that use the FEC building block.","scope_keywords":["3695","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null}],"search_text":"IETF RFC 3695 This document introduces some Forward Error Correction (FEC) schemes\n that supplement the FEC schemes described in RFC 3452. The primary\n benefits of these additional FEC schemes are that they are designed\n for reliable bulk delivery of large objects using a more compact FEC\n Payload ID, and they can be used to sequentially deliver blocks of an\n object of indeterminate length. Thus, they more flexibly support\n different delivery models with less packet header overhead.\n\n This document also describes the Fully-Specified FEC scheme\n corresponding to FEC Encoding ID 0. This Fully-Specified FEC scheme\n requires no FEC coding and is introduced primarily to allow simple\n interoperability testing between different implementations of\n protocol instantiations that use the FEC building block. 3695 delivery key nested-reference unchanged"},{"id":"IETF RFC 3705","type":"specification","body":"IETF","designation":"RFC 3705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3705.txt","https://www.rfc-editor.org/rfc/rfc3705.pdf"],"folder":"IETF/RFC-3705","files":{"txt":{"path":"standards/IETF/RFC-3705/RFC-3705.txt","sha256":"9935f7dadeac33d9fb50a757bd1318211af2885e5c141546293bf9d4fbbfd94b"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of High Capacity Textual Conventions for\n use in MIB modules which require performance history based upon 15\n minute intervals. The Textual Conventions defined in this document\n extend the conventions presented in RFC 3593 to 64 bit resolution\n using the conventions presented in RFC 2856.","scope_keywords":["3705","http","https","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"IETF RFC 3705 This document presents a set of High Capacity Textual Conventions for\n use in MIB modules which require performance history based upon 15\n minute intervals. The Textual Conventions defined in this document\n extend the conventions presented in RFC 3593 to 64 bit resolution\n using the conventions presented in RFC 2856. 3705 http https key management subject nested-reference unchanged"},{"id":"IETF RFC 3716","type":"specification","body":"IETF","designation":"RFC 3716","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3716.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3716.txt","https://www.rfc-editor.org/rfc/rfc3716.pdf"],"folder":"IETF/RFC-3716","files":{"txt":{"path":"standards/IETF/RFC-3716/RFC-3716.txt","sha256":"2b3854de94652c895443caca9252a3d90cf835a65c6cdb58f3330925109f2001"}},"tags":["nested-reference","unchanged"],"summary":"In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB\n Advisory Committee (AdvComm), with a mandate to review the existing\n IETF administrative structure and relationships (RFC Editor, IETF\n Secretariat, IANA) and to propose changes to the IETF management\n process or structure to improve the overall functioning of the IETF.\n The AdvComm mandate did not include the standards process itself.\n\n This memo documents the AdvComm's findings and proposals.","scope_keywords":["3716","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null}],"search_text":"IETF RFC 3716 In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB\n Advisory Committee (AdvComm), with a mandate to review the existing\n IETF administrative structure and relationships (RFC Editor, IETF\n Secretariat, IANA) and to propose changes to the IETF management\n process or structure to improve the overall functioning of the IETF.\n The AdvComm mandate did not include the standards process itself.\n\n This memo documents the AdvComm's findings and proposals. 3716 key management nested-reference unchanged"},{"id":"IETF RFC 3932","type":"specification","body":"IETF","designation":"RFC 3932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3932.txt","https://www.rfc-editor.org/rfc/rfc3932.pdf"],"folder":"IETF/RFC-3932","files":{"txt":{"path":"standards/IETF/RFC-3932/RFC-3932.txt","sha256":"adc70758b8844bf6d9471f4de5e231e4a699cbe78944114767e2d7fd2dbaeb5e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the IESG's procedures for handling documents\n submitted for RFC publication via the RFC Editor, subsequent to the\n changes proposed by the IESG at the Seoul IETF, March 2004.\n\n This document updates procedures described in RFC 2026 and RFC 3710.\n\n1. Introduction and History\n\n There are a number of different methods by which an RFC is published,\n some of which include review in the Internet Engineering Task Force\n (IETF), and some of which include approval by the Internet\n Engineering Steering Group (IESG):\n\n o IETF Working Group (WG) to Standards Track: Includes WG consensus,\n review in the IETF, IETF Last Call, and IESG approval\n\n o IETF WG to Experimental/Informational: Includes WG consensus,\n review in the IETF, and IESG approval\n\n o Area Director (AD) sponsored to Standards Track: Includes review\n in the IETF, IETF Last Call, and IESG approval\n\n o AD Sponsored","scope_keywords":["3932","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4713","folder":"IETF/RFC-4713","source":"IETF/RFC-4713/RFC-4713.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 4981","folder":"IETF/RFC-4981","source":"IETF/RFC-4981/RFC-4981.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5742","folder":"IETF/RFC-5742","source":"IETF/RFC-5742/RFC-5742.txt","version":null}],"search_text":"IETF RFC 3932 This document describes the IESG's procedures for handling documents\n submitted for RFC publication via the RFC Editor, subsequent to the\n changes proposed by the IESG at the Seoul IETF, March 2004.\n\n This document updates procedures described in RFC 2026 and RFC 3710.\n\n1. Introduction and History\n\n There are a number of different methods by which an RFC is published,\n some of which include review in the Internet Engineering Task Force\n (IETF), and some of which include approval by the Internet\n Engineering Steering Group (IESG):\n\n o IETF Working Group (WG) to Standards Track: Includes WG consensus,\n review in the IETF, IETF Last Call, and IESG approval\n\n o IETF WG to Experimental/Informational: Includes WG consensus,\n review in the IETF, and IESG approval\n\n o Area Director (AD) sponsored to Standards Track: Includes review\n in the IETF, IETF Last Call, and IESG approval\n\n o AD Sponsored 3932 path subject nested-reference unchanged"},{"id":"IETF RFC 3934","type":"specification","body":"IETF","designation":"RFC 3934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3934.txt","https://www.rfc-editor.org/rfc/rfc3934.pdf"],"folder":"IETF/RFC-3934","files":{"txt":{"path":"standards/IETF/RFC-3934/RFC-3934.txt","sha256":"f796a76081877d5e3a73c2f367158f0049e33baa386f797c53c19890b2e5b3d2"}},"tags":["nested-reference","unchanged"],"summary":"This document is an update to RFC 2418 that gives WG chairs explicit\n responsibility for managing WG mailing lists. In particular, it\n gives WG chairs the authority to temporarily suspend the mailing list\n posting privileges of disruptive individuals.","scope_keywords":["3934","http","license","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null}],"search_text":"IETF RFC 3934 This document is an update to RFC 2418 that gives WG chairs explicit\n responsibility for managing WG mailing lists. In particular, it\n gives WG chairs the authority to temporarily suspend the mailing list\n posting privileges of disruptive individuals. 3934 http license management subject nested-reference unchanged"},{"id":"IETF RFC 3978","type":"specification","body":"IETF","designation":"RFC 3978","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3978.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3978.txt","https://www.rfc-editor.org/rfc/rfc3978.pdf"],"folder":"IETF/RFC-3978","files":{"txt":{"path":"standards/IETF/RFC-3978/RFC-3978.txt","sha256":"6a90d1a320b7cc722fad8516856e923734cd895bb2cb86284d0991edb7e6d02f"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC\n 2026.","scope_keywords":["3978","policies","policy","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3979","folder":"IETF/RFC-3979","source":"IETF/RFC-3979/RFC-3979.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4663","folder":"IETF/RFC-4663","source":"IETF/RFC-4663/RFC-4663.txt","version":null},{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 4748","folder":"IETF/RFC-4748","source":"IETF/RFC-4748/RFC-4748.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null}],"search_text":"IETF RFC 3978 The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n updates RFC 2026, and, with RFC 3979, replaces Section 10 of RFC\n 2026. 3978 policies policy presentation subject nested-reference unchanged"},{"id":"IETF RFC 4052","type":"specification","body":"IETF","designation":"RFC 4052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4052.txt","https://www.rfc-editor.org/rfc/rfc4052.pdf"],"folder":"IETF/RFC-4052","files":{"txt":{"path":"standards/IETF/RFC-4052/RFC-4052.txt","sha256":"9c79782e1f18c073a77ef3cead0b69162fece5671a871473529e240b54bea468"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the procedures used by the IAB to establish\n and maintain liaison relationships between the IETF and other\n Standards Development Organizations (SDOs), consortia and industry\n fora. This document also discusses the appointment and\n responsibilities of IETF liaison managers and representatives, and\n the expectations of the IAB for organizations with whom liaison\n relationships are established.","scope_keywords":["4052","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4053","folder":"IETF/RFC-4053","source":"IETF/RFC-4053/RFC-4053.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null}],"search_text":"IETF RFC 4052 This document discusses the procedures used by the IAB to establish\n and maintain liaison relationships between the IETF and other\n Standards Development Organizations (SDOs), consortia and industry\n fora. This document also discusses the appointment and\n responsibilities of IETF liaison managers and representatives, and\n the expectations of the IAB for organizations with whom liaison\n relationships are established. 4052 management nested-reference unchanged"},{"id":"IETF RFC 4071","type":"specification","body":"IETF","designation":"RFC 4071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4071.txt","https://www.rfc-editor.org/rfc/rfc4071.pdf"],"folder":"IETF/RFC-4071","files":{"txt":{"path":"standards/IETF/RFC-4071/RFC-4071.txt","sha256":"382aa57e914bbabacf30102e4d3597c07cd1d45369360547a4d77556b2c0a757"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the structure of the IETF Administrative\n Support Activity (IASA) as an activity housed within the Internet\n Society (ISOC). It defines the roles and responsibilities of the\n IETF Administrative Oversight Committee (IAOC), the IETF\n Administrative Director (IAD), and ISOC in the fiscal and\n administrative support of the IETF standards process. It also\n defines the membership and selection rules for the IAOC.","scope_keywords":["4071","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4333","folder":"IETF/RFC-4333","source":"IETF/RFC-4333/RFC-4333.txt","version":null},{"body":"IETF","designation":"RFC 4371","folder":"IETF/RFC-4371","source":"IETF/RFC-4371/RFC-4371.txt","version":null},{"body":"IETF","designation":"RFC 4748","folder":"IETF/RFC-4748","source":"IETF/RFC-4748/RFC-4748.txt","version":null},{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 5377","folder":"IETF/RFC-5377","source":"IETF/RFC-5377/RFC-5377.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null}],"search_text":"IETF RFC 4071 This document describes the structure of the IETF Administrative\n Support Activity (IASA) as an activity housed within the Internet\n Society (ISOC). It defines the roles and responsibilities of the\n IETF Administrative Oversight Committee (IAOC), the IETF\n Administrative Director (IAD), and ISOC in the fiscal and\n administrative support of the IETF standards process. It also\n defines the membership and selection rules for the IAOC. 4071 management policy nested-reference unchanged"},{"id":"IETF RFC 4221","type":"specification","body":"IETF","designation":"RFC 4221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4221.txt","https://www.rfc-editor.org/rfc/rfc4221.pdf"],"folder":"IETF/RFC-4221","files":{"txt":{"path":"standards/IETF/RFC-4221/RFC-4221.txt","sha256":"05be8573f422caf629481986bbac849a61909ed75b55795dd847d1b95851d2ba"}},"tags":["nested-reference","unchanged"],"summary":"A range of Management Information Base (MIB) modules has been\n developed to help model and manage the various aspects of\n Multiprotocol Label Switching (MPLS) networks. These MIB modules are\n defined in separate documents that focus on the specific areas of\n responsibility of the modules that they describe.\n\n This document describes the management architecture for MPLS and\n indicates the interrelationships between the different MIB modules\n used for MPLS network management.","scope_keywords":["4221","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4221 A range of Management Information Base (MIB) modules has been\n developed to help model and manage the various aspects of\n Multiprotocol Label Switching (MPLS) networks. These MIB modules are\n defined in separate documents that focus on the specific areas of\n responsibility of the modules that they describe.\n\n This document describes the management architecture for MPLS and\n indicates the interrelationships between the different MIB modules\n used for MPLS network management. 4221 management nested-reference unchanged"},{"id":"IETF RFC 4288","type":"specification","body":"IETF","designation":"RFC 4288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4288.txt","https://www.rfc-editor.org/rfc/rfc4288.pdf"],"folder":"IETF/RFC-4288","files":{"txt":{"path":"standards/IETF/RFC-4288/RFC-4288.txt","sha256":"752b7a5b52cde6fe4dcefc96bcf7458e637e2ea5b5558d76bf4c11db8bc1d79a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines procedures for the specification and\n registration of media types for use in MIME and other Internet\n protocols.\n\nFreed & Klensin Best Current Practice [Page 1]\n\f\nRFC 4288 Media Type Registration December 2005","scope_keywords":["4288","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4735","folder":"IETF/RFC-4735","source":"IETF/RFC-4735/RFC-4735.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6351","folder":"IETF/RFC-6351","source":"IETF/RFC-6351/RFC-6351.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4288 This document defines procedures for the specification and\n registration of media types for use in MIME and other Internet\n protocols.\n\nFreed & Klensin Best Current Practice [Page 1]\n\f\nRFC 4288 Media Type Registration December 2005 4288 key registered nested-reference unchanged"},{"id":"IETF RFC 4289","type":"specification","body":"IETF","designation":"RFC 4289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4289.txt","https://www.rfc-editor.org/rfc/rfc4289.pdf"],"folder":"IETF/RFC-4289","files":{"txt":{"path":"standards/IETF/RFC-4289/RFC-4289.txt","sha256":"20487597e5c5b74e7d3bfa1eceefc49270c9dc34e32bf4825b19693835ba2e81"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies IANA registration procedures for MIME\n external body access types and content-transfer-encodings.\n\nFreed & Klensin Best Current Practice [Page 1]\n\f\nRFC 4289 MIME Registration December 2005","scope_keywords":["4289","algorithm","algorithms","key","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 4289 This document specifies IANA registration procedures for MIME\n external body access types and content-transfer-encodings.\n\nFreed & Klensin Best Current Practice [Page 1]\n\f\nRFC 4289 MIME Registration December 2005 4289 algorithm algorithms key registered risk subject nested-reference unchanged"},{"id":"IETF RFC 4608","type":"specification","body":"IETF","designation":"RFC 4608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4608.txt","https://www.rfc-editor.org/rfc/rfc4608.pdf"],"folder":"IETF/RFC-4608","files":{"txt":{"path":"standards/IETF/RFC-4608/RFC-4608.txt","sha256":"81363b39eb8db851bf70f49cfcd4ee1525366dbb18e88b978280f97f19ab131a"}},"tags":["nested-reference","unchanged"],"summary":"IP Multicast group addresses in the 232/8 (232.0.0.0 to\n 232.255.255.255) range are designated as source-specific multicast\n destination addresses and are reserved for use by source-specific\n multicast applications and protocols. This document defines\n operational recommendations to ensure source-specific behavior within\n the 232/8 range.","scope_keywords":["4608","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 4608 IP Multicast group addresses in the 232/8 (232.0.0.0 to\n 232.255.255.255) range are designated as source-specific multicast\n destination addresses and are reserved for use by source-specific\n multicast applications and protocols. This document defines\n operational recommendations to ensure source-specific behavior within\n the 232/8 range. 4608 key path policy nested-reference unchanged"},{"id":"IETF RFC 4766","type":"specification","body":"IETF","designation":"RFC 4766","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4766.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4766.txt","https://www.rfc-editor.org/rfc/rfc4766.pdf"],"folder":"IETF/RFC-4766","files":{"txt":{"path":"standards/IETF/RFC-4766/RFC-4766.txt","sha256":"f94d6b3544a0373bd90aac0305735050a798aeac540c3b1c06439f61b918b85c"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of the Intrusion Detection Exchange Format Working Group\n (IDWG) is to define data formats and exchange procedures for sharing\n information of interest to intrusion detection and response systems\n and to the management systems that may need to interact with them.\n This document describes the high-level requirements for such a\n communication mechanism, including the rationale for those\n requirements where clarification is needed. Scenarios are used to\n illustrate some requirements.","scope_keywords":["4766","authentication","identification","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null}],"search_text":"IETF RFC 4766 The purpose of the Intrusion Detection Exchange Format Working Group\n (IDWG) is to define data formats and exchange procedures for sharing\n information of interest to intrusion detection and response systems\n and to the management systems that may need to interact with them.\n This document describes the high-level requirements for such a\n communication mechanism, including the rationale for those\n requirements where clarification is needed. Scenarios are used to\n illustrate some requirements. 4766 authentication identification key management trust nested-reference unchanged"},{"id":"IETF RFC 4775","type":"specification","body":"IETF","designation":"RFC 4775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4775.txt","https://www.rfc-editor.org/rfc/rfc4775.pdf"],"folder":"IETF/RFC-4775","files":{"txt":{"path":"standards/IETF/RFC-4775/RFC-4775.txt","sha256":"b4fb1de6018455d1134b8a9a7f79a08fa16b23e5f113f280c2ca2125867a3909"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses procedural issues related to the\n extensibility of IETF protocols, including when it is reasonable to\n extend IETF protocols with little or no review, and when extensions\n or variations need to be reviewed by the IETF community. Experience\n has shown that extension of protocols without early IETF review can\n carry risk. The document also recommends that major extensions to or\n variations of IETF protocols only take place through normal IETF\n processes or in coordination with the IETF.\n\n This document is directed principally at other Standards Development\n Organizations (SDOs) and vendors considering requirements for\n extensions to IETF protocols. It does not modify formal IETF\n processes.\n\nBradner, et al. Best Current Practice [Page 1]\n\f\nRFC 4775 Procedures for Protocol Extensions December 2006","scope_keywords":["4775","key","path","registered","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 4775 This document discusses procedural issues related to the\n extensibility of IETF protocols, including when it is reasonable to\n extend IETF protocols with little or no review, and when extensions\n or variations need to be reviewed by the IETF community. Experience\n has shown that extension of protocols without early IETF review can\n carry risk. The document also recommends that major extensions to or\n variations of IETF protocols only take place through normal IETF\n processes or in coordination with the IETF.\n\n This document is directed principally at other Standards Development\n Organizations (SDOs) and vendors considering requirements for\n extensions to IETF protocols. It does not modify formal IETF\n processes.\n\nBradner, et al. Best Current Practice [Page 1]\n\f\nRFC 4775 Procedures for Protocol Extensions December 2006 4775 key path registered risk trust nested-reference unchanged"},{"id":"IETF RFC 4845","type":"specification","body":"IETF","designation":"RFC 4845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4845.txt","https://www.rfc-editor.org/rfc/rfc4845.pdf"],"folder":"IETF/RFC-4845","files":{"txt":{"path":"standards/IETF/RFC-4845/RFC-4845.txt","sha256":"63195d443d4273280f0440ec9d195d999b4156fe89e37ec315a2e86bfce184f5"}},"tags":["nested-reference","unchanged"],"summary":"From time to time, the Internet Architecture Board (IAB) publishes\n documents as Requests for Comments (RFCs). This document defines the\n process by which those documents are produced, reviewed, and\n published in the RFC Series.","scope_keywords":["4845","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null}],"search_text":"IETF RFC 4845 From time to time, the Internet Architecture Board (IAB) publishes\n documents as Requests for Comments (RFCs). This document defines the\n process by which those documents are produced, reviewed, and\n published in the RFC Series. 4845 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 4897","type":"specification","body":"IETF","designation":"RFC 4897","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4897.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4897.txt","https://www.rfc-editor.org/rfc/rfc4897.pdf"],"folder":"IETF/RFC-4897","files":{"txt":{"path":"standards/IETF/RFC-4897/RFC-4897.txt","sha256":"eeae70b81607aa5f7879d563294bd60f68bb51fd275019c03bab3184beb1194d"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Engineering Task Force (IETF) and Request for Comments\n (RFC) Editor have a long-standing rule that a document at a given\n maturity level cannot be published until all of the documents that it\n references as normative are at that maturity level or higher. This\n rule has sometimes resulted in very long publication delays for\n documents and some claims that it was a major obstruction to\n advancing documents in maturity level. The IETF agreed on a way to\n bypass this rule with RFC 3967. This document describes a simpler\n procedure for downward references to Standards-Track and Best Current\n Practice (BCP) documents, namely \"note and move on\". The procedure\n in RFC 3967 still applies for downward references to other classes of\n documents. In both cases, annotations should be added to such\n References.\n\nKlensin & Hartman Best Current Practice [Page 1]\n\f\nRFC 4897 Normative Referen","scope_keywords":["4897","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null}],"search_text":"IETF RFC 4897 The Internet Engineering Task Force (IETF) and Request for Comments\n (RFC) Editor have a long-standing rule that a document at a given\n maturity level cannot be published until all of the documents that it\n references as normative are at that maturity level or higher. This\n rule has sometimes resulted in very long publication delays for\n documents and some claims that it was a major obstruction to\n advancing documents in maturity level. The IETF agreed on a way to\n bypass this rule with RFC 3967. This document describes a simpler\n procedure for downward references to Standards-Track and Best Current\n Practice (BCP) documents, namely \"note and move on\". The procedure\n in RFC 3967 still applies for downward references to other classes of\n documents. In both cases, annotations should be added to such\n References.\n\nKlensin & Hartman Best Current Practice [Page 1]\n\f\nRFC 4897 Normative Referen 4897 trust nested-reference unchanged"},{"id":"IETF RFC 4929","type":"specification","body":"IETF","designation":"RFC 4929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4929.txt","https://www.rfc-editor.org/rfc/rfc4929.pdf"],"folder":"IETF/RFC-4929","files":{"txt":{"path":"standards/IETF/RFC-4929/RFC-4929.txt","sha256":"d8765441d36dc0aae03e4facc973878402fded99c21b67400a8e30bfa8e081d1"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for applying or extending the MPLS\n or GMPLS ((G)MPLS) protocol suites and clarifies the IETF's (G)MPLS\n working groups' responsibility for the (G)MPLS protocols. This\n document is directed to multi-vendor fora and Standards Development\n Organizations (SDOs) to provide an understanding of (G)MPLS work in\n the IETF and documents the requisite use of IETF review procedures\n when considering (G)MPLS applications or protocol extensions in their\n work. This document does not modify IETF processes.\n\nAndersson & Farrel Best Current Practice [Page 1]\n\f\nRFC 4929 MPLS and GMPLS Change Process June 2007","scope_keywords":["4929","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 4929 This document provides guidelines for applying or extending the MPLS\n or GMPLS ((G)MPLS) protocol suites and clarifies the IETF's (G)MPLS\n working groups' responsibility for the (G)MPLS protocols. This\n document is directed to multi-vendor fora and Standards Development\n Organizations (SDOs) to provide an understanding of (G)MPLS work in\n the IETF and documents the requisite use of IETF review procedures\n when considering (G)MPLS applications or protocol extensions in their\n work. This document does not modify IETF processes.\n\nAndersson & Farrel Best Current Practice [Page 1]\n\f\nRFC 4929 MPLS and GMPLS Change Process June 2007 4929 trust nested-reference unchanged"},{"id":"IETF RFC 5111","type":"specification","body":"IETF","designation":"RFC 5111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5111.txt","https://www.rfc-editor.org/rfc/rfc5111.pdf"],"folder":"IETF/RFC-5111","files":{"txt":{"path":"standards/IETF/RFC-5111/RFC-5111.txt","sha256":"f465f39457009e7466ad770136f72e8ce24360d5b4736593a2a757a318304fbe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an RFC 3933 experiment in the Working Group\n formation process, known as the Exploratory Group. Exploratory\n Groups may be created as the first step toward Working Group\n formation, or as an intermediate step between a Birds of a Feather\n (BOF) session and Working Group creation. Exploratory Groups are\n focused on completion of prerequisites for Working Group formation,\n and as a result they have a short life-time, with limited\n opportunities for milestone extension.","scope_keywords":["5111","key","pid","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null}],"search_text":"IETF RFC 5111 This document describes an RFC 3933 experiment in the Working Group\n formation process, known as the Exploratory Group. Exploratory\n Groups may be created as the first step toward Working Group\n formation, or as an intermediate step between a Birds of a Feather\n (BOF) session and Working Group creation. Exploratory Groups are\n focused on completion of prerequisites for Working Group formation,\n and as a result they have a short life-time, with limited\n opportunities for milestone extension. 5111 key pid risk nested-reference unchanged"},{"id":"IETF RFC 5125","type":"specification","body":"IETF","designation":"RFC 5125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5125.txt","https://www.rfc-editor.org/rfc/rfc5125.pdf"],"folder":"IETF/RFC-5125","files":{"txt":{"path":"standards/IETF/RFC-5125/RFC-5125.txt","sha256":"36261c80d448ba62600f1ea45df3d663c836c14e7dc7f0a7c5d0fef9755eb18d"}},"tags":["nested-reference","unchanged"],"summary":"This document reclassifies RFC 3525, Gateway Control Protocol Version\n 1, to Historic Status. This memo also obsoletes RFC 3525.\n\n1. Introduction\n\n The purpose of this document is to reclassify RFC 3525, Gateway\n Control Protocol Version 1, to Historic Status.\n\n2. Reclassification of RFC 3525 to Historic\n\n The protocol defined by RFC 3525 [RFC3525] was developed jointly by\n the IETF Megaco Working Group and ITU-T Study Group 16. The ITU-T\n published ITU-T Recommendation H.248.1 (originally H.248) with the\n same contents as RFC 3525. Since that initial development, the ITU-T\n has taken ownership of the protocol and has continued to work on it.\n The protocol as originally defined in RFC 3525 underwent a series of\n corrections and clarifications. H.248.1 version 1 [h248v1] was\n republished in March, 2002, incorporating all changes agreed upon up\n to that date. Since then, further correction","scope_keywords":["5125","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null}],"search_text":"IETF RFC 5125 This document reclassifies RFC 3525, Gateway Control Protocol Version\n 1, to Historic Status. This memo also obsoletes RFC 3525.\n\n1. Introduction\n\n The purpose of this document is to reclassify RFC 3525, Gateway\n Control Protocol Version 1, to Historic Status.\n\n2. Reclassification of RFC 3525 to Historic\n\n The protocol defined by RFC 3525 [RFC3525] was developed jointly by\n the IETF Megaco Working Group and ITU-T Study Group 16. The ITU-T\n published ITU-T Recommendation H.248.1 (originally H.248) with the\n same contents as RFC 3525. Since that initial development, the ITU-T\n has taken ownership of the protocol and has continued to work on it.\n The protocol as originally defined in RFC 3525 underwent a series of\n corrections and clarifications. H.248.1 version 1 [h248v1] was\n republished in March, 2002, incorporating all changes agreed upon up\n to that date. Since then, further correction 5125 http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5378","type":"specification","body":"IETF","designation":"RFC 5378","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5378.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5378.txt","https://www.rfc-editor.org/rfc/rfc5378.pdf"],"folder":"IETF/RFC-5378","files":{"txt":{"path":"standards/IETF/RFC-5378/RFC-5378.txt","sha256":"5022d32a7923d2baf80837e131d0c70334c7cdc6484ccb4e931fcad819cc4f74"}},"tags":["nested-reference","unchanged"],"summary":"The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces\n Section 10 of RFC 2026.\n\nBradner & Contreras Best Current Practice [Page 1]\n\f\nRFC 5378 RFC 3978-incoming November 2008","scope_keywords":["5378","http","license","policies","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5377","folder":"IETF/RFC-5377","source":"IETF/RFC-5377/RFC-5377.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 5378 The IETF policies about rights in Contributions to the IETF are\n designed to ensure that such Contributions can be made available to\n the IETF and Internet communities while permitting the authors to\n retain as many rights as possible. This memo details the IETF\n policies on rights in Contributions to the IETF. It also describes\n the objectives that the policies are designed to meet. This memo\n obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, replaces\n Section 10 of RFC 2026.\n\nBradner & Contreras Best Current Practice [Page 1]\n\f\nRFC 5378 RFC 3978-incoming November 2008 5378 http license policies policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5657","type":"specification","body":"IETF","designation":"RFC 5657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5657.txt","https://www.rfc-editor.org/rfc/rfc5657.pdf"],"folder":"IETF/RFC-5657","files":{"txt":{"path":"standards/IETF/RFC-5657/RFC-5657.txt","sha256":"7907e39549d0048573590084a49fb9cd155c26103b04b09f133e052e4a24994a"}},"tags":["nested-reference","unchanged"],"summary":"Advancing a protocol to Draft Standard requires documentation of the\n interoperation and implementation of the protocol. Historic reports\n have varied widely in form and level of content and there is little\n guidance available to new report preparers. This document updates\n the existing processes and provides more detail on what is\n appropriate in an interoperability and implementation report.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on t","scope_keywords":["5657","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6410","folder":"IETF/RFC-6410","source":"IETF/RFC-6410/RFC-6410.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null}],"search_text":"IETF RFC 5657 Advancing a protocol to Draft Standard requires documentation of the\n interoperation and implementation of the protocol. Historic reports\n have varied widely in form and level of content and there is little\n guidance available to new report preparers. This document updates\n the existing processes and provides more detail on what is\n appropriate in an interoperability and implementation report.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on t 5657 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5727","type":"specification","body":"IETF","designation":"RFC 5727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5727.txt","https://www.rfc-editor.org/rfc/rfc5727.pdf"],"folder":"IETF/RFC-5727","files":{"txt":{"path":"standards/IETF/RFC-5727/RFC-5727.txt","sha256":"4a8ae81b5536e9132772b4acd14704f81d6a2a5a3ee19486f6a9ee5116b933a4"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents a process intended to organize the future\n development of the Session Initiation Protocol (SIP) and related work\n in the Real-time Applications and Infrastructure (RAI) Area. As the\n environments in which SIP is deployed grow more numerous and diverse,\n modifying or extending SIP in certain ways may threaten the\n interoperability and security of the protocol; however, the IETF\n process must also cater to the realities of existing deployments and\n serve the needs of the implementers working with SIP. This document\n therefore defines the functions of two long-lived working groups in\n the RAI Area that are, respectively, responsible for the maintenance\n of the core SIP specifications and the development of new efforts to\n extend and apply work in this space. This document obsoletes RFC\n 3427.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n","scope_keywords":["5727","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null}],"search_text":"IETF RFC 5727 This memo documents a process intended to organize the future\n development of the Session Initiation Protocol (SIP) and related work\n in the Real-time Applications and Infrastructure (RAI) Area. As the\n environments in which SIP is deployed grow more numerous and diverse,\n modifying or extending SIP in certain ways may threaten the\n interoperability and security of the protocol; however, the IETF\n process must also cater to the realities of existing deployments and\n serve the needs of the implementers working with SIP. This document\n therefore defines the functions of two long-lived working groups in\n the RAI Area that are, respectively, responsible for the maintenance\n of the core SIP specifications and the development of new efforts to\n extend and apply work in this space. This document obsoletes RFC\n 3427.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n 5727 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5742","type":"specification","body":"IETF","designation":"RFC 5742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5742.txt","https://www.rfc-editor.org/rfc/rfc5742.pdf"],"folder":"IETF/RFC-5742","files":{"txt":{"path":"standards/IETF/RFC-5742/RFC-5742.txt","sha256":"ee1657c5153f6804230fc5622afe583696f1329f8d3ae804e5fd9e1a869c3103"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the procedures used by the IESG for handling\n documents submitted for RFC publication from the Independent\n Submission and IRTF streams.\n\n This document updates procedures described in RFC 2026 and RFC 3710.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at http://www.rfc-\n editor.org/info/rfc5742.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All r","scope_keywords":["5742","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 5742 This document describes the procedures used by the IESG for handling\n documents submitted for RFC publication from the Independent\n Submission and IRTF streams.\n\n This document updates procedures described in RFC 2026 and RFC 3710.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at http://www.rfc-\n editor.org/info/rfc5742.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All r 5742 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5744","type":"specification","body":"IETF","designation":"RFC 5744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5744.txt","https://www.rfc-editor.org/rfc/rfc5744.pdf"],"folder":"IETF/RFC-5744","files":{"txt":{"path":"standards/IETF/RFC-5744/RFC-5744.txt","sha256":"fc42be996002aaf2062324e34192842c71a3e17207899178ba4597a06125a3cc"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the procedures by which authors of RFC\n Independent Submission documents grant the community \"incoming\"\n rights for copying and using the text. It also specifies the\n \"outgoing\" rights the community grants to readers and users of those\n documents, and it requests that the IETF Trust manage the outgoing\n rights to effect this result.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully","scope_keywords":["5744","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null}],"search_text":"IETF RFC 5744 This document specifies the procedures by which authors of RFC\n Independent Submission documents grant the community \"incoming\"\n rights for copying and using the text. It also specifies the\n \"outgoing\" rights the community grants to readers and users of those\n documents, and it requests that the IETF Trust manage the outgoing\n rights to effect this result.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully 5744 http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5988","type":"specification","body":"IETF","designation":"RFC 5988","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5988.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5988.txt","https://www.rfc-editor.org/rfc/rfc5988.pdf"],"folder":"IETF/RFC-5988","files":{"txt":{"path":"standards/IETF/RFC-5988/RFC-5988.txt","sha256":"c48657057de93fe894b0573f292af4024495e336fb253373e56856e6d0426681"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies relation types for Web links, and defines a\n registry for them. It also defines the use of such links in HTTP\n headers with the Link header field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5988.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and ","scope_keywords":["5988","attribute","attributes","http","key","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 5988 This document specifies relation types for Web links, and defines a\n registry for them. It also defines the use of such links in HTTP\n headers with the Link header field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5988.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and  5988 attribute attributes http key license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6014","type":"specification","body":"IETF","designation":"RFC 6014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6014.txt","https://www.rfc-editor.org/rfc/rfc6014.pdf"],"folder":"IETF/RFC-6014","files":{"txt":{"path":"standards/IETF/RFC-6014/RFC-6014.txt","sha256":"30374fffc4336885388df1ab84c17582d46ed9150a72f10c51cad7ea10956582"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how DNSSEC cryptographic algorithm\n identifiers in the IANA registries are allocated. It changes the\n requirement from \"standard required\" to \"RFC Required\". It does not\n change the list of algorithms that are recommended or required for\n DNSSEC implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6014.\n\nHoffman Standards Track [Page 1]\n\f\nRFC 6014 DNSS","scope_keywords":["6014","algorithm","algorithms","http","license","registered","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 6014 This document specifies how DNSSEC cryptographic algorithm\n identifiers in the IANA registries are allocated. It changes the\n requirement from \"standard required\" to \"RFC Required\". It does not\n change the list of algorithms that are recommended or required for\n DNSSEC implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6014.\n\nHoffman Standards Track [Page 1]\n\f\nRFC 6014 DNSS 6014 algorithm algorithms http license registered signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6071","type":"specification","body":"IETF","designation":"RFC 6071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6071.txt","https://www.rfc-editor.org/rfc/rfc6071.pdf"],"folder":"IETF/RFC-6071","files":{"txt":{"path":"standards/IETF/RFC-6071/RFC-6071.txt","sha256":"2d0c52420f92ec68785f83f1dba3aad7e23091b84d10df4625c92b7528b1b034"}},"tags":["nested-reference","unchanged"],"summary":"Over the past few years, the number of RFCs that define and use IPsec\n and Internet Key Exchange (IKE) has greatly proliferated. This is\n complicated by the fact that these RFCs originate from numerous IETF\n working groups: the original IPsec WG, its various spin-offs, and\n other WGs that use IPsec and/or IKE to protect their protocols'\n traffic.\n\n This document is a snapshot of IPsec- and IKE-related RFCs. It\n includes a brief description of each RFC, along with background\n information explaining the motivation and context of IPsec's\n outgrowths and extensions. It obsoletes RFC 2411, the previous \"IP\n Security Document Roadmap.\"\n\n The obsoleted IPsec roadmap (RFC 2411) briefly described the\n interrelationship of the various classes of base IPsec documents.\n The major focus of RFC 2411 was to specify the recommended contents\n of documents specifying additional encryption and authenticati","scope_keywords":["6071","algorithm","algorithms","authentication","certificate","encryption","http","key","keys","license","management","path","pki","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null}],"search_text":"IETF RFC 6071 Over the past few years, the number of RFCs that define and use IPsec\n and Internet Key Exchange (IKE) has greatly proliferated. This is\n complicated by the fact that these RFCs originate from numerous IETF\n working groups: the original IPsec WG, its various spin-offs, and\n other WGs that use IPsec and/or IKE to protect their protocols'\n traffic.\n\n This document is a snapshot of IPsec- and IKE-related RFCs. It\n includes a brief description of each RFC, along with background\n information explaining the motivation and context of IPsec's\n outgrowths and extensions. It obsoletes RFC 2411, the previous \"IP\n Security Document Roadmap.\"\n\n The obsoleted IPsec roadmap (RFC 2411) briefly described the\n interrelationship of the various classes of base IPsec documents.\n The major focus of RFC 2411 was to specify the recommended contents\n of documents specifying additional encryption and authenticati 6071 algorithm algorithms authentication certificate encryption http key keys license management path pki policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6118","type":"specification","body":"IETF","designation":"RFC 6118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6118.txt","https://www.rfc-editor.org/rfc/rfc6118.pdf"],"folder":"IETF/RFC-6118","files":{"txt":{"path":"standards/IETF/RFC-6118/RFC-6118.txt","sha256":"82ba5411df1e86546710a26b564055ed97d2e928c39ea9f343099e4f97bdac9a"}},"tags":["nested-reference","unchanged"],"summary":"This document revises all Enumservices that were IANA registered\n under the now obsolete specification of the Enumservice registry\n defined in RFC 3761.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6118.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's L","scope_keywords":["6118","http","https","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 6118 This document revises all Enumservices that were IANA registered\n under the now obsolete specification of the Enumservice registry\n defined in RFC 3761.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6118.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's L 6118 http https license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6121","type":"specification","body":"IETF","designation":"RFC 6121","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6121.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6121.txt","https://www.rfc-editor.org/rfc/rfc6121.pdf"],"folder":"IETF/RFC-6121","files":{"txt":{"path":"standards/IETF/RFC-6121/RFC-6121.txt","sha256":"f3eda13791fe2f1f1f7c9b3993aaf6e0082dff30037c225080ca8da34d74c414"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to core features of the Extensible\n Messaging and Presence Protocol (XMPP) that provide basic instant\n messaging (IM) and presence functionality in conformance with the\n requirements in RFC 2779. This document obsoletes RFC 3921.\n\nStatus of this Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6121.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identif","scope_keywords":["6121","attribute","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null}],"search_text":"IETF RFC 6121 This document defines extensions to core features of the Extensible\n Messaging and Presence Protocol (XMPP) that provide basic instant\n messaging (IM) and presence functionality in conformance with the\n requirements in RFC 2779. This document obsoletes RFC 3921.\n\nStatus of this Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6121.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identif 6121 attribute http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6410","type":"specification","body":"IETF","designation":"RFC 6410","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6410.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6410.txt","https://www.rfc-editor.org/rfc/rfc6410.pdf"],"folder":"IETF/RFC-6410","files":{"txt":{"path":"standards/IETF/RFC-6410/RFC-6410.txt","sha256":"68d0e639b86fff94493f169133fc2615eb10d74ec0d1cd290d32f159c09cd7e5"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the Internet Engineering Task Force (IETF)\n Standards Process defined in RFC 2026. Primarily, it reduces the\n Standards Process from three Standards Track maturity levels to two.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6410.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["6410","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7127","folder":"IETF/RFC-7127","source":"IETF/RFC-7127/RFC-7127.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 6410 This document updates the Internet Engineering Task Force (IETF)\n Standards Process defined in RFC 2026. Primarily, it reduces the\n Standards Process from three Standards Track maturity levels to two.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6410.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  6410 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6484","type":"specification","body":"IETF","designation":"RFC 6484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6484.txt","https://www.rfc-editor.org/rfc/rfc6484.pdf"],"folder":"IETF/RFC-6484","files":{"txt":{"path":"standards/IETF/RFC-6484/RFC-6484.txt","sha256":"151c490b4825e1c73de0b040f7f676d643053ce53e02e46af243f1f6406bba59"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the certificate policy for a Public Key\n Infrastructure (PKI) used to support attestations about Internet\n Number Resource (INR) holdings. Each organization that distributes\n IP addresses or Autonomous System (AS) numbers to an organization\n will, in parallel, issue a (public key) certificate reflecting this\n distribution. These certificates will enable verification that the\n resources indicated in the certificate have been distributed to the\n holder of the associated private key and that this organization is\n the current, unique holder of these resources.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering ","scope_keywords":["6484","attestation","attestations","authentication","certificate","certificates","holder","http","identification","key","license","pki","policy","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null}],"search_text":"IETF RFC 6484 This document describes the certificate policy for a Public Key\n Infrastructure (PKI) used to support attestations about Internet\n Number Resource (INR) holdings. Each organization that distributes\n IP addresses or Autonomous System (AS) numbers to an organization\n will, in parallel, issue a (public key) certificate reflecting this\n distribution. These certificates will enable verification that the\n resources indicated in the certificate have been distributed to the\n holder of the associated private key and that this organization is\n the current, unique holder of these resources.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering  6484 attestation attestations authentication certificate certificates holder http identification key license pki policy revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6701","type":"specification","body":"IETF","designation":"RFC 6701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6701.txt","https://www.rfc-editor.org/rfc/rfc6701.pdf"],"folder":"IETF/RFC-6701","files":{"txt":{"path":"standards/IETF/RFC-6701/RFC-6701.txt","sha256":"726cf4542cc4b4ff49546928eb82949a225ce50521a0e6d855d85331f3d3cf3d"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has developed and documented policies that govern the\n behavior of all IETF participants with respect to Intellectual\n Property Rights (IPR) about which they might reasonably be aware.\n\n The IETF takes conformance to these IPR policies very seriously.\n However, there has been some ambiguity as to what the appropriate\n sanctions are for the violation of these policies, and how and by\n whom those sanctions are to be applied.\n\n This document discusses these issues and provides a suite of\n potential actions that can be taken within the IETF community in\n cases related to patents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr","scope_keywords":["6701","http","license","policies","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 6701 The IETF has developed and documented policies that govern the\n behavior of all IETF participants with respect to Intellectual\n Property Rights (IPR) about which they might reasonably be aware.\n\n The IETF takes conformance to these IPR policies very seriously.\n However, there has been some ambiguity as to what the appropriate\n sanctions are for the violation of these policies, and how and by\n whom those sanctions are to be applied.\n\n This document discusses these issues and provides a suite of\n potential actions that can be taken within the IETF community in\n cases related to patents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr 6701 http license policies policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6808","type":"specification","body":"IETF","designation":"RFC 6808","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6808.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6808.txt","https://www.rfc-editor.org/rfc/rfc6808.pdf"],"folder":"IETF/RFC-6808","files":{"txt":{"path":"standards/IETF/RFC-6808/RFC-6808.txt","sha256":"4fef35131b9b6369394c458e3b00dcf6f9636a1619479b3e749c7a8b285a38e2"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides the supporting test plan and results to advance\n RFC 2679 on one-way delay metrics along the Standards Track,\n following the process in RFC 6576. Observing that the metric\n definitions themselves should be the primary focus rather than the\n implementations of metrics, this memo describes the test procedures\n to evaluate specific metric requirement clauses to determine if the\n requirement has been interpreted and implemented as intended. Two\n completely independent implementations have been tested against the\n key specifications of RFC 2679. This memo also provides direct input\n for development of a revision of RFC 2679.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF comm","scope_keywords":["6808","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null}],"search_text":"IETF RFC 6808 This memo provides the supporting test plan and results to advance\n RFC 2679 on one-way delay metrics along the Standards Track,\n following the process in RFC 6576. Observing that the metric\n definitions themselves should be the primary focus rather than the\n implementations of metrics, this memo describes the test procedures\n to evaluate specific metric requirement clauses to determine if the\n requirement has been interpreted and implemented as intended. Two\n completely independent implementations have been tested against the\n key specifications of RFC 2679. This memo also provides direct input\n for development of a revision of RFC 2679.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF comm 6808 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6838","type":"specification","body":"IETF","designation":"RFC 6838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6838.txt","https://www.rfc-editor.org/rfc/rfc6838.pdf"],"folder":"IETF/RFC-6838","files":{"txt":{"path":"standards/IETF/RFC-6838/RFC-6838.txt","sha256":"b08ccba7e5116e61085f2e1fe447d90eee785fb0efaa448a4b4ef6ea48b03b80"}},"tags":["nested-reference","unchanged"],"summary":"This document defines procedures for the specification and\n registration of media types for use in HTTP, MIME, and other Internet\n protocols.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6838.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions","scope_keywords":["6838","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8081","folder":"IETF/RFC-8081","source":"IETF/RFC-8081/RFC-8081.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 6838 This document defines procedures for the specification and\n registration of media types for use in HTTP, MIME, and other Internet\n protocols.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6838.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions 6838 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7063","type":"specification","body":"IETF","designation":"RFC 7063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7063.txt","https://www.rfc-editor.org/rfc/rfc7063.pdf"],"folder":"IETF/RFC-7063","files":{"txt":{"path":"standards/IETF/RFC-7063/RFC-7063.txt","sha256":"c338cb0fe246db621a3e699e1efd21fe1e71d846adbf0309aff93de0dfd227ac"}},"tags":["nested-reference","unchanged"],"summary":"This document provides supporting documentation to advance the IETF\n stream's Protocol Independent Multicast - Sparse Mode (PIM-SM)\n protocol from Proposed Standard to Internet Standard.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7063.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trus","scope_keywords":["7063","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 7063 This document provides supporting documentation to advance the IETF\n stream's Protocol Independent Multicast - Sparse Mode (PIM-SM)\n protocol from Proposed Standard to Internet Standard.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7063.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trus 7063 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7127","type":"specification","body":"IETF","designation":"RFC 7127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7127.txt","https://www.rfc-editor.org/rfc/rfc7127.pdf"],"folder":"IETF/RFC-7127","files":{"txt":{"path":"standards/IETF/RFC-7127/RFC-7127.txt","sha256":"42058b3a6f47d58860ef64178641746a57f237d80b9ba586659e78746e6d5d84"}},"tags":["nested-reference","unchanged"],"summary":"RFC 2026 describes the review performed by the Internet Engineering\n Steering Group (IESG) on IETF Proposed Standard RFCs and\n characterizes the maturity level of those documents. This document\n updates RFC 2026 by providing a current and more accurate\n characterization of Proposed Standards.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Further information on BCPs is\n available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7127.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This","scope_keywords":["7127","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null}],"search_text":"IETF RFC 7127 RFC 2026 describes the review performed by the Internet Engineering\n Steering Group (IESG) on IETF Proposed Standard RFCs and\n characterizes the maturity level of those documents. This document\n updates RFC 2026 by providing a current and more accurate\n characterization of Proposed Standards.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Further information on BCPs is\n available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7127.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This 7127 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7290","type":"specification","body":"IETF","designation":"RFC 7290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7290.txt","https://www.rfc-editor.org/rfc/rfc7290.pdf"],"folder":"IETF/RFC-7290","files":{"txt":{"path":"standards/IETF/RFC-7290/RFC-7290.txt","sha256":"acfa7fdddb92438a4a38648238f5c9d89c3b7c0f0f2a6996f4d7fd4df7bd4689"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides the supporting test plan and results to advance\n RFC 2680, a performance metric RFC defining one-way packet loss\n metrics, along the Standards Track. Observing that the metric\n definitions themselves should be the primary focus rather than the\n implementations of metrics, this memo describes the test procedures\n to evaluate specific metric requirement clauses to determine if the\n requirement has been interpreted and implemented as intended. Two\n completely independent implementations have been tested against the\n key specifications of RFC 2680.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b","scope_keywords":["7290","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 7290 This memo provides the supporting test plan and results to advance\n RFC 2680, a performance metric RFC defining one-way packet loss\n metrics, along the Standards Track. Observing that the metric\n definitions themselves should be the primary focus rather than the\n implementations of metrics, this memo describes the test procedures\n to evaluate specific metric requirement clauses to determine if the\n requirement has been interpreted and implemented as intended. Two\n completely independent implementations have been tested against the\n key specifications of RFC 2680.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b 7290 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7525","type":"specification","body":"IETF","designation":"RFC 7525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7525.txt","https://www.rfc-editor.org/rfc/rfc7525.pdf"],"folder":"IETF/RFC-7525","files":{"txt":{"path":"standards/IETF/RFC-7525/RFC-7525.txt","sha256":"728e0c3fd07d4307f02c22971c285f6f9c0a03334136ca5ed32f2a54d52ed7d2"}},"tags":["nested-reference","unchanged"],"summary":"Transport Layer Security (TLS) and Datagram Transport Layer Security\n (DTLS) are widely used to protect data exchanged over application\n protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the\n last few years, several serious attacks on TLS have emerged,\n including attacks on its most commonly used cipher suites and their\n modes of operation. This document provides recommendations for\n improving the security of deployed services that use TLS and DTLS.\n The recommendations are applicable to the majority of use cases.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available ","scope_keywords":["7525","algorithm","algorithms","authentication","certificate","encryption","http","key","license","revocation","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7830","folder":"IETF/RFC-7830","source":"IETF/RFC-7830/RFC-7830.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7525 Transport Layer Security (TLS) and Datagram Transport Layer Security\n (DTLS) are widely used to protect data exchanged over application\n protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the\n last few years, several serious attacks on TLS have emerged,\n including attacks on its most commonly used cipher suites and their\n modes of operation. This document provides recommendations for\n improving the security of deployed services that use TLS and DTLS.\n The recommendations are applicable to the majority of use cases.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available  7525 algorithm algorithms authentication certificate encryption http key license revocation subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 7749","type":"specification","body":"IETF","designation":"RFC 7749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7749.txt","https://www.rfc-editor.org/rfc/rfc7749.pdf"],"folder":"IETF/RFC-7749","files":{"txt":{"path":"standards/IETF/RFC-7749/RFC-7749.txt","sha256":"f5f58c356c923732fe76e12d30bc82684184d89fbb7211d9377254efcf96ed97"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the \"xml2rfc\" version 2 vocabulary: an XML-\n based language used for writing RFCs and Internet-Drafts.\n\n Version 2 represents the state of the vocabulary (as implemented by\n several tools and as used by the RFC Editor) around 2014.\n\n This document obsoletes RFC 2629.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be ","scope_keywords":["7749","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null}],"search_text":"IETF RFC 7749 This document defines the \"xml2rfc\" version 2 vocabulary: an XML-\n based language used for writing RFCs and Internet-Drafts.\n\n Version 2 represents the state of the vocabulary (as implemented by\n several tools and as used by the RFC Editor) around 2014.\n\n This document obsoletes RFC 2629.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be  7749 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8407","type":"specification","body":"IETF","designation":"RFC 8407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8407.txt","https://www.rfc-editor.org/rfc/rfc8407.pdf"],"folder":"IETF/RFC-8407","files":{"txt":{"path":"standards/IETF/RFC-8407/RFC-8407.txt","sha256":"da70ce8d308c91ab18304eddb27741ae49ae4d2cc9d79a7b342c74ad91018a1a"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides guidelines for authors and reviewers of\n specifications containing YANG modules. Recommendations and\n procedures are defined, which are intended to increase\n interoperability and usability of Network Configuration Protocol\n (NETCONF) and RESTCONF protocol implementations that utilize YANG\n modules. This document obsoletes RFC 6087.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/i","scope_keywords":["8407","http","https","key","license","management","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 8407 This memo provides guidelines for authors and reviewers of\n specifications containing YANG modules. Recommendations and\n procedures are defined, which are intended to increase\n interoperability and usability of Network Configuration Protocol\n (NETCONF) and RESTCONF protocol implementations that utilize YANG\n modules. This document obsoletes RFC 6087.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/i 8407 http https key license management path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8615","type":"specification","body":"IETF","designation":"RFC 8615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8615.txt","https://www.rfc-editor.org/rfc/rfc8615.pdf"],"folder":"IETF/RFC-8615","files":{"txt":{"path":"standards/IETF/RFC-8615/RFC-8615.txt","sha256":"02d45caeb86c00197d30428472102bb558881fa61937804330c1242a0be5b5dc"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a path prefix for \"well-known locations\",\n \"/.well-known/\", in selected Uniform Resource Identifier (URI)\n schemes.\n\n In doing so, it obsoletes RFC 5785 and updates the URI schemes\n defined in RFC 7230 to reserve that space. It also updates RFC 7595\n to track URI schemes that support well-known URIs in their registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc861","scope_keywords":["8615","http","https","key","license","path","policy","registered","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8615 This memo defines a path prefix for \"well-known locations\",\n \"/.well-known/\", in selected Uniform Resource Identifier (URI)\n schemes.\n\n In doing so, it obsoletes RFC 5785 and updates the URI schemes\n defined in RFC 7230 to reserve that space. It also updates RFC 7595\n to track URI schemes that support well-known URIs in their registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc861 8615 http https key license path policy registered risk subject trust nested-reference unchanged"},{"id":"IETF RFC 3777","type":"specification","body":"IETF","designation":"RFC 3777","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3777.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3777.txt","https://www.rfc-editor.org/rfc/rfc3777.pdf"],"folder":"IETF/RFC-3777","files":{"txt":{"path":"standards/IETF/RFC-3777/RFC-3777.txt","sha256":"c07d8e0a99a0002a41c78d2f469a1ae8a26e5ca7a837a7ec418390823546056f"}},"tags":["nested-reference","unchanged"],"summary":"The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. This document is a self-\n consistent, organized compilation of the process as it was known at\n the time of publication.","scope_keywords":["3777","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3797","folder":"IETF/RFC-3797","source":"IETF/RFC-3797/RFC-3797.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null}],"search_text":"IETF RFC 3777 The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. This document is a self-\n consistent, organized compilation of the process as it was known at\n the time of publication. 3777 trust nested-reference unchanged"},{"id":"IETF RFC 3060","type":"specification","body":"IETF","designation":"RFC 3060","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3060.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3060.txt","https://www.rfc-editor.org/rfc/rfc3060.pdf"],"folder":"IETF/RFC-3060","files":{"txt":{"path":"standards/IETF/RFC-3060/RFC-3060.txt","sha256":"5063be92bc6b2e65c1726b6da5a75091a585f7a3095c32b6f2ab910d1ef82258"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the object-oriented information model for\n representing policy information developed jointly in the IETF Policy\n Framework WG and as extensions to the Common Information Model (CIM)\n activity in the Distributed Management Task Force (DMTF). This model\n defines two hierarchies of object classes: structural classes\n representing policy information and control of policies, and\n association classes that indicate how instances of the structural\n classes are related to each other. Subsequent documents will define\n mappings of this information model to various concrete\n implementations, for example, to a directory that uses LDAPv3 as its\n access protocol.","scope_keywords":["3060","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3535","folder":"IETF/RFC-3535","source":"IETF/RFC-3535/RFC-3535.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 3060 This document presents the object-oriented information model for\n representing policy information developed jointly in the IETF Policy\n Framework WG and as extensions to the Common Information Model (CIM)\n activity in the Distributed Management Task Force (DMTF). This model\n defines two hierarchies of object classes: structural classes\n representing policy information and control of policies, and\n association classes that indicate how instances of the structural\n classes are related to each other. Subsequent documents will define\n mappings of this information model to various concrete\n implementations, for example, to a directory that uses LDAPv3 as its\n access protocol. 3060 key management policies policy nested-reference unchanged"},{"id":"IETF RFC 3476","type":"specification","body":"IETF","designation":"RFC 3476","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3476.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3476.txt","https://www.rfc-editor.org/rfc/rfc3476.pdf"],"folder":"IETF/RFC-3476","files":{"txt":{"path":"standards/IETF/RFC-3476/RFC-3476.txt","sha256":"b6dd847abe37953b7b108e09b6e2d92cab801585a11fb28427f024098549ae8d"}},"tags":["nested-reference","unchanged"],"summary":"The Optical Interworking Forum (OIF) has defined extensions to the\n Label Distribution Protocol (LDP) and the Resource ReSerVation\n Protocol (RSVP) for optical User Network Interface (UNI) signaling.\n These extensions consist of a set of new data objects and error\n codes. This document describes these extensions.\n\n1. Introduction\n\n The OIF UNI signaling specification is described in [8]. This\n specification utilizes IETF protocol standards as well as IETF work\n in progress. Specifically, the following IETF specifications are\n used:\n\n o Label distribution protocol (LDP) [6]\n o Resource reservation protocol (RSVP) [5]\n o GMPLS signaling and GMPLS extensions for SONET/SDH [4]\n o GMPLS RSVP-TE and CR-LDP extensions [2, 3]\n\n The aim of the OIF UNI specification is the maximal re-use of IETF\n protocol definitions. A few extensions to IETF protocols, however,\n have been defined to serve UNI-spe","scope_keywords":["3476"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null}],"search_text":"IETF RFC 3476 The Optical Interworking Forum (OIF) has defined extensions to the\n Label Distribution Protocol (LDP) and the Resource ReSerVation\n Protocol (RSVP) for optical User Network Interface (UNI) signaling.\n These extensions consist of a set of new data objects and error\n codes. This document describes these extensions.\n\n1. Introduction\n\n The OIF UNI signaling specification is described in [8]. This\n specification utilizes IETF protocol standards as well as IETF work\n in progress. Specifically, the following IETF specifications are\n used:\n\n o Label distribution protocol (LDP) [6]\n o Resource reservation protocol (RSVP) [5]\n o GMPLS signaling and GMPLS extensions for SONET/SDH [4]\n o GMPLS RSVP-TE and CR-LDP extensions [2, 3]\n\n The aim of the OIF UNI specification is the maximal re-use of IETF\n protocol definitions. A few extensions to IETF protocols, however,\n have been defined to serve UNI-spe 3476 nested-reference unchanged"},{"id":"IETF RFC 3498","type":"specification","body":"IETF","designation":"RFC 3498","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3498.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3498.txt","https://www.rfc-editor.org/rfc/rfc3498.pdf"],"folder":"IETF/RFC-3498","files":{"txt":{"path":"standards/IETF/RFC-3498/RFC-3498.txt","sha256":"3edd00e0fd7e09768ff20771fcc573f0e0f61e075d4dce8d6884b5e206a75603"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for managing networks using\n Synchronous Optical Network (SONET) linear Automatic Protection\n Switching (APS) architectures.","scope_keywords":["3498","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null}],"search_text":"IETF RFC 3498 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular, it defines objects for managing networks using\n Synchronous Optical Network (SONET) linear Automatic Protection\n Switching (APS) architectures. 3498 management nested-reference unchanged"},{"id":"IETF RFC 3546","type":"specification","body":"IETF","designation":"RFC 3546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3546.txt","https://www.rfc-editor.org/rfc/rfc3546.pdf"],"folder":"IETF/RFC-3546","files":{"txt":{"path":"standards/IETF/RFC-3546/RFC-3546.txt","sha256":"11c18d90e5e7153ed3653cd7f3b5248c3153c5f905b7d7fb06f8a809a10c4dd8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions that may be used to add\n functionality to Transport Layer Security (TLS). It provides both\n generic extension mechanisms for the TLS handshake client and server\n hellos, and specific extensions using these generic mechanisms.\n\n The extensions may be used by TLS clients and servers. The\n extensions are backwards compatible - communication is possible\n between TLS 1.0 clients that support the extensions and TLS 1.0\n servers that do not support the extensions, and vice versa.\n\nConventions used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [KEYWORDS].\n\nBlake-Wilson, et. al. Standards Track [Page 1]\n\f\nRFC 3546 TLS Extensions June 2003","scope_keywords":["3546","certificate","crl","key","keys","ocsp","revocation","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3546 This document describes extensions that may be used to add\n functionality to Transport Layer Security (TLS). It provides both\n generic extension mechanisms for the TLS handshake client and server\n hellos, and specific extensions using these generic mechanisms.\n\n The extensions may be used by TLS clients and servers. The\n extensions are backwards compatible - communication is possible\n between TLS 1.0 clients that support the extensions and TLS 1.0\n servers that do not support the extensions, and vice versa.\n\nConventions used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [KEYWORDS].\n\nBlake-Wilson, et. al. Standards Track [Page 1]\n\f\nRFC 3546 TLS Extensions June 2003 3546 certificate crl key keys ocsp revocation tls trust nested-reference unchanged"},{"id":"IETF RFC 3641","type":"specification","body":"IETF","designation":"RFC 3641","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3641.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3641.txt","https://www.rfc-editor.org/rfc/rfc3641.pdf"],"folder":"IETF/RFC-3641","files":{"txt":{"path":"standards/IETF/RFC-3641/RFC-3641.txt","sha256":"b75496324244796c626691c6924b3fcd1a1cd7355626e3070cf06c72830845f9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of Abstract Syntax Notation One (ASN.1)\n encoding rules, called the Generic String Encoding Rules (GSER), that\n produce a human readable text encoding for values of any given ASN.1\n data type.","scope_keywords":["3641","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 3641 This document defines a set of Abstract Syntax Notation One (ASN.1)\n encoding rules, called the Generic String Encoding Rules (GSER), that\n produce a human readable text encoding for values of any given ASN.1\n data type. 3641 attribute key nested-reference unchanged"},{"id":"IETF RFC 3642","type":"specification","body":"IETF","designation":"RFC 3642","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3642.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3642.txt","https://www.rfc-editor.org/rfc/rfc3642.pdf"],"folder":"IETF/RFC-3642","files":{"txt":{"path":"standards/IETF/RFC-3642/RFC-3642.txt","sha256":"e49188446c7d6793017e3036aade36f7bfdf8ccbfcdb5298d7415a9c2eddf187"}},"tags":["nested-reference","unchanged"],"summary":"The Generic String Encoding Rules (GSER) describe a human readable\n text encoding for an Abstract Syntax Notation One (ASN.1) value of\n any ASN.1 type. Specifications making use of GSER may wish to\n provide an equivalent Augmented Backus-Naur Form (ABNF) description\n of the GSER encoding for a particular ASN.1 type as a convenience for\n implementors. This document supports such specifications by\n providing equivalent ABNF for the GSER encodings for ASN.1 types that\n commonly occur in Lightweight Directory Access Protocol (LDAP)\n syntaxes.","scope_keywords":["3642","attribute","identification","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 3642 The Generic String Encoding Rules (GSER) describe a human readable\n text encoding for an Abstract Syntax Notation One (ASN.1) value of\n any ASN.1 type. Specifications making use of GSER may wish to\n provide an equivalent Augmented Backus-Naur Form (ABNF) description\n of the GSER encoding for a particular ASN.1 type as a convenience for\n implementors. This document supports such specifications by\n providing equivalent ABNF for the GSER encodings for ASN.1 types that\n commonly occur in Lightweight Directory Access Protocol (LDAP)\n syntaxes. 3642 attribute identification key presentation nested-reference unchanged"},{"id":"IETF RFC 3703","type":"specification","body":"IETF","designation":"RFC 3703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3703.txt","https://www.rfc-editor.org/rfc/rfc3703.pdf"],"folder":"IETF/RFC-3703","files":{"txt":{"path":"standards/IETF/RFC-3703/RFC-3703.txt","sha256":"0a07b7a918cd57c2a644dc38280d0b817299c320489d9c5924b4954d25fc7dcb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mapping of the Policy Core Information Model\n to a form that can be implemented in a directory that uses\n Lightweight Directory Access Protocol (LDAP) as its access protocol.\n This model defines two hierarchies of object classes: structural\n classes representing information for representing and controlling\n policy data as specified in RFC 3060, and relationship classes that\n indicate how instances of the structural classes are related to each\n other. Classes are also added to the LDAP schema to improve the\n performance of a client's interactions with an LDAP server when the\n client is retrieving large amounts of policy-related information.\n These classes exist only to optimize LDAP retrievals: there are no\n classes in the information model that correspond to them.","scope_keywords":["3703","attribute","attributes","key","keys","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null}],"search_text":"IETF RFC 3703 This document defines a mapping of the Policy Core Information Model\n to a form that can be implemented in a directory that uses\n Lightweight Directory Access Protocol (LDAP) as its access protocol.\n This model defines two hierarchies of object classes: structural\n classes representing information for representing and controlling\n policy data as specified in RFC 3060, and relationship classes that\n indicate how instances of the structural classes are related to each\n other. Classes are also added to the LDAP schema to improve the\n performance of a client's interactions with an LDAP server when the\n client is retrieving large amounts of policy-related information.\n These classes exist only to optimize LDAP retrievals: there are no\n classes in the information model that correspond to them. 3703 attribute attributes key keys management policies policy nested-reference unchanged"},{"id":"IETF RFC 3555","type":"specification","body":"IETF","designation":"RFC 3555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3555.txt","https://www.rfc-editor.org/rfc/rfc3555.pdf"],"folder":"IETF/RFC-3555","files":{"txt":{"path":"standards/IETF/RFC-3555/RFC-3555.txt","sha256":"837786e3d84be6623516e14f6ad02496aca6e398724e9edcd737f1f199db3c1b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the procedure to register RTP Payload Formats\n as audio, video or other MIME subtype names. This is useful in a\n text-based format or control protocol to identify the type of an RTP\n transmission. This document also registers all the RTP payload\n formats defined in the RTP Profile for Audio and Video Conferences as\n MIME subtypes. Some of these may also be used for transfer modes\n other than RTP.","scope_keywords":["3555","http","identification","key","profile","registered","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null}],"search_text":"IETF RFC 3555 This document defines the procedure to register RTP Payload Formats\n as audio, video or other MIME subtype names. This is useful in a\n text-based format or control protocol to identify the type of an RTP\n transmission. This document also registers all the RTP payload\n formats defined in the RTP Profile for Audio and Video Conferences as\n MIME subtypes. Some of these may also be used for transfer modes\n other than RTP. 3555 http identification key profile registered timestamp nested-reference unchanged"},{"id":"IETF RFC 203","type":"specification","body":"IETF","designation":"RFC 203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc203.txt","https://www.rfc-editor.org/rfc/rfc203.pdf"],"folder":"IETF/RFC-203","files":{"txt":{"path":"standards/IETF/RFC-203/RFC-203.txt","sha256":"6deeaddab994de4ad43cbeccf39d86f31a790fc056426564c499ac394a8e562f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Kalin\nRequest for Comments: 203 MIT Lincoln Lab\nNIC: 7168 10 August 1971\n\n Achieving Reliable Communication\n\n 'This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.'\n\nABSTRACT\n\n A non-standard protocol, suitable for either second or third level\n use, is proposed with the intent of providing error resistant and\n highly reliable communication channels. Errors introduced by message\n garbling, message loss, and message pickup are considered. Measures\n for increasing throughput are also discussed.\n\nAIMS AND LIMITATIONS\n\n It is not our intent to propose the design of a perfect communication\n channel, rather it is our contention that in the real world there can\n be no perfect channels and that no amount of protocol can insure the\n e","scope_keywords":["203"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 203 Network Working Group R. Kalin\nRequest for Comments: 203 MIT Lincoln Lab\nNIC: 7168 10 August 1971\n\n Achieving Reliable Communication\n\n 'This material has not been reviewed for public release and is\n intended only for use with the ARPA network. It should not be quoted\n or cited in any publication not related to the ARPA network.'\n\nABSTRACT\n\n A non-standard protocol, suitable for either second or third level\n use, is proposed with the intent of providing error resistant and\n highly reliable communication channels. Errors introduced by message\n garbling, message loss, and message pickup are considered. Measures\n for increasing throughput are also discussed.\n\nAIMS AND LIMITATIONS\n\n It is not our intent to propose the design of a perfect communication\n channel, rather it is our contention that in the real world there can\n be no perfect channels and that no amount of protocol can insure the\n e 203 nested-reference unchanged"},{"id":"IETF RFC 4075","type":"specification","body":"IETF","designation":"RFC 4075","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4075.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4075.txt","https://www.rfc-editor.org/rfc/rfc4075.pdf"],"folder":"IETF/RFC-4075","files":{"txt":{"path":"standards/IETF/RFC-4075/RFC-4075.txt","sha256":"07a7151c4aba3e3286911e9f64e799a58da19af32ee3cb8e40b123863ca934fb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Kalusivalingam\nRequest for Comments: 4075 Cisco Systems (India) Private Limited\nCategory: Standards Track May 2005\n\n Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a new DHCPv6 option for passing a list of\n Simple Network Time Protocol (SNTP) server addresses to a client.\n\n1. Introduction\n\n This document describes a new option, called the SNTP [3] servers\n option, for passing information a","scope_keywords":["4075","algorithm","algorithms","authentication","certificate","certificates","key","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 4075 Network Working Group V. Kalusivalingam\nRequest for Comments: 4075 Cisco Systems (India) Private Limited\nCategory: Standards Track May 2005\n\n Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a new DHCPv6 option for passing a list of\n Simple Network Time Protocol (SNTP) server addresses to a client.\n\n1. Introduction\n\n This document describes a new option, called the SNTP [3] servers\n option, for passing information a 4075 algorithm algorithms authentication certificate certificates key license subject nested-reference unchanged"},{"id":"IETF RFC 2031","type":"specification","body":"IETF","designation":"RFC 2031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2031.txt","https://www.rfc-editor.org/rfc/rfc2031.pdf"],"folder":"IETF/RFC-2031","files":{"txt":{"path":"standards/IETF/RFC-2031/RFC-2031.txt","sha256":"85970608118b3317e9ed57b11357391c2629a6cd4ca1d29c31a008a273270a61"}},"tags":["nested-reference","unchanged"],"summary":"This memo summarises the issues on IETF - ISOC relationships as the\n have been discussed by the Poised Working Group. The purpose of the\n document is to gauge consensus on these issues. And to allow further\n discussions where necessary.","scope_keywords":["2031","driving","policies","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null}],"search_text":"IETF RFC 2031 This memo summarises the issues on IETF - ISOC relationships as the\n have been discussed by the Poised Working Group. The purpose of the\n document is to gauge consensus on these issues. And to allow further\n discussions where necessary. 2031 driving policies risk trust nested-reference unchanged"},{"id":"IETF RFC 4585","type":"specification","body":"IETF","designation":"RFC 4585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4585.txt","https://www.rfc-editor.org/rfc/rfc4585.pdf"],"folder":"IETF/RFC-4585","files":{"txt":{"path":"standards/IETF/RFC-4585/RFC-4585.txt","sha256":"5889ac58b83680fe9cc4c602840f336e352d711d663dbf349f06257b8992bdd5"}},"tags":["nested-reference","unchanged"],"summary":"Real-time media streams that use RTP are, to some degree, resilient\n against packet losses. Receivers may use the base mechanisms of the\n Real-time Transport Control Protocol (RTCP) to report packet\n reception statistics and thus allow a sender to adapt its\n transmission behavior in the mid-term. This is the sole means for\n feedback and feedback-based error repair (besides a few codec-\n specific mechanisms). This document defines an extension to the\n Audio-visual Profile (AVP) that enables receivers to provide,\n statistically, more immediate feedback to the senders and thus allows\n for short-term adaptation and efficient feedback-based repair\n mechanisms to be implemented. This early feedback profile (AVPF)\n maintains the AVP bandwidth constraints for RTCP and preserves\n scalability to large groups.\n\nOtt, et al. Standards Track [Page 1]\n\f\nRFC 4585 RTP/AVPF July 2006","scope_keywords":["4585","algorithm","algorithms","attribute","attributes","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4585 Real-time media streams that use RTP are, to some degree, resilient\n against packet losses. Receivers may use the base mechanisms of the\n Real-time Transport Control Protocol (RTCP) to report packet\n reception statistics and thus allow a sender to adapt its\n transmission behavior in the mid-term. This is the sole means for\n feedback and feedback-based error repair (besides a few codec-\n specific mechanisms). This document defines an extension to the\n Audio-visual Profile (AVP) that enables receivers to provide,\n statistically, more immediate feedback to the senders and thus allows\n for short-term adaptation and efficient feedback-based repair\n mechanisms to be implemented. This early feedback profile (AVPF)\n maintains the AVP bandwidth constraints for RTCP and preserves\n scalability to large groups.\n\nOtt, et al. Standards Track [Page 1]\n\f\nRFC 4585 RTP/AVPF July 2006 4585 algorithm algorithms attribute attributes identification profile nested-reference unchanged"},{"id":"IETF RFC 4587","type":"specification","body":"IETF","designation":"RFC 4587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4587.txt","https://www.rfc-editor.org/rfc/rfc4587.pdf"],"folder":"IETF/RFC-4587","files":{"txt":{"path":"standards/IETF/RFC-4587/RFC-4587.txt","sha256":"3ffc2a5dbf37b429b7fed483c78204fde49c76e42af94cfe263c8032cf5e6091"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a scheme to packetize an H.261 video stream for\n transport using the Real-time Transport Protocol, RTP, with any of\n the underlying protocols that carry RTP.\n\n The memo also describes the syntax and semantics of the Session\n Description Protocol (SDP) parameters needed to support the H.261\n video codec. A media type registration is included for this payload\n format.\n\n This specification obsoletes RFC 2032.\n\nEven Standards Track [Page 1]\n\f\nRFC 4587 H.261 RTP payload format August 2006","scope_keywords":["4587","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null}],"search_text":"IETF RFC 4587 This memo describes a scheme to packetize an H.261 video stream for\n transport using the Real-time Transport Protocol, RTP, with any of\n the underlying protocols that carry RTP.\n\n The memo also describes the syntax and semantics of the Session\n Description Protocol (SDP) parameters needed to support the H.261\n video codec. A media type registration is included for this payload\n format.\n\n This specification obsoletes RFC 2032.\n\nEven Standards Track [Page 1]\n\f\nRFC 4587 H.261 RTP payload format August 2006 4587 key registered nested-reference unchanged"},{"id":"IETF RFC 4629","type":"specification","body":"IETF","designation":"RFC 4629","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4629.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4629.txt","https://www.rfc-editor.org/rfc/rfc4629.pdf"],"folder":"IETF/RFC-4629","files":{"txt":{"path":"standards/IETF/RFC-4629/RFC-4629.txt","sha256":"6e4b8856af26fe57bd44239de319bb9a4d5f9ed42ecdce90623fc52d77cae2a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a scheme to packetize an H.263 video stream\n for transport using the Real-time Transport Protocol (RTP) with any\n of the underlying protocols that carry RTP.\n\n The document also describes the syntax and semantics of the Session\n Description Protocol (SDP) parameters needed to support the H.263\n video codec.\n\n The document obsoletes RFC 2429 and updates the H263-1998 and\n H263-2000 media type in RFC 3555.\n\nOtt, et al. Standards Track [Page 1]\n\f\nRFC 4629 H.263 RTP Payload Format January 2007","scope_keywords":["4629","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null}],"search_text":"IETF RFC 4629 This document describes a scheme to packetize an H.263 video stream\n for transport using the Real-time Transport Protocol (RTP) with any\n of the underlying protocols that carry RTP.\n\n The document also describes the syntax and semantics of the Session\n Description Protocol (SDP) parameters needed to support the H.263\n video codec.\n\n The document obsoletes RFC 2429 and updates the H263-1998 and\n H263-2000 media type in RFC 3555.\n\nOtt, et al. Standards Track [Page 1]\n\f\nRFC 4629 H.263 RTP Payload Format January 2007 4629 key trust nested-reference unchanged"},{"id":"IETF RFC 5104","type":"specification","body":"IETF","designation":"RFC 5104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5104.txt","https://www.rfc-editor.org/rfc/rfc5104.pdf"],"folder":"IETF/RFC-5104","files":{"txt":{"path":"standards/IETF/RFC-5104/RFC-5104.txt","sha256":"a41abdb27c1fcd0074f5501227b87f02597b4c7269ee9726989e7a3f7a708448"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a few extensions to the messages defined in\n the Audio-Visual Profile with Feedback (AVPF). They are helpful\n primarily in conversational multimedia scenarios where centralized\n multipoint functionalities are in use. However, some are also usable\n in smaller multicast environments and point-to-point calls.\n\n The extensions discussed are messages related to the ITU-T Rec. H.271\n Video Back Channel, Full Intra Request, Temporary Maximum Media\n Stream Bit Rate, and Temporal-Spatial Trade-off.\n\nWenger, et al. Standards Track [Page 1]\n\f\nRFC 5104 Codec Control Messages in AVPF February 2008","scope_keywords":["5104","algorithm","attribute","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5104 This document specifies a few extensions to the messages defined in\n the Audio-Visual Profile with Feedback (AVPF). They are helpful\n primarily in conversational multimedia scenarios where centralized\n multipoint functionalities are in use. However, some are also usable\n in smaller multicast environments and point-to-point calls.\n\n The extensions discussed are messages related to the ITU-T Rec. H.271\n Video Back Channel, Full Intra Request, Temporary Maximum Media\n Stream Bit Rate, and Temporal-Spatial Trade-off.\n\nWenger, et al. Standards Track [Page 1]\n\f\nRFC 5104 Codec Control Messages in AVPF February 2008 5104 algorithm attribute path profile nested-reference unchanged"},{"id":"IETF RFC 5761","type":"specification","body":"IETF","designation":"RFC 5761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5761.txt","https://www.rfc-editor.org/rfc/rfc5761.pdf"],"folder":"IETF/RFC-5761","files":{"txt":{"path":"standards/IETF/RFC-5761/RFC-5761.txt","sha256":"8b062daf82519f1278a80ff5eb347b201656c79369a487018c80ad03ea47612a"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses issues that arise when multiplexing RTP data\n packets and RTP Control Protocol (RTCP) packets on a single UDP port.\n It updates RFC 3550 and RFC 3551 to describe when such multiplexing\n is and is not appropriate, and it explains how the Session\n Description Protocol (SDP) can be used to signal multiplexed\n sessions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5761","scope_keywords":["5761","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8035","folder":"IETF/RFC-8035","source":"IETF/RFC-8035/RFC-8035.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5761 This memo discusses issues that arise when multiplexing RTP data\n packets and RTP Control Protocol (RTCP) packets on a single UDP port.\n It updates RFC 3550 and RFC 3551 to describe when such multiplexing\n is and is not appropriate, and it explains how the Session\n Description Protocol (SDP) can be used to signal multiplexed\n sessions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5761 5761 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5429","type":"specification","body":"IETF","designation":"RFC 5429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5429.txt","https://www.rfc-editor.org/rfc/rfc5429.pdf"],"folder":"IETF/RFC-5429","files":{"txt":{"path":"standards/IETF/RFC-5429/RFC-5429.txt","sha256":"65018bfee062e39baf291c44c61484ad5e45051363e276d7cca87925d2d6ef86"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates the definition of the Sieve mail filtering language\n \"reject\" extension, originally defined in RFC 3028.\n\n A \"Joe-job\" is a spam run forged to appear as though it came from an\n innocent party, who is then generally flooded by automated bounces,\n Message Disposition Notifications (MDNs), and personal messages with\n\nStone Standards Track [Page 1]\n\f\nRFC 5429 Sieve Extension: Reject March 2009\n\n complaints. The original Sieve \"reject\" action defined in RFC 3028\n required use of MDNs for rejecting messages, thus contributing to the\n flood of Joe-job spam to victims of Joe-jobs.\n\n This memo updates the definition of the \"reject\" action to allow\n messages to be refused during the SMTP transaction, and defines the\n \"ereject\" action to require messages to be refused during the SMTP\n transaction, if possible.\n\n The \"ereject\" action is intended to replace the \"reject\" action\n wher","scope_keywords":["5429","delivery","http","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"IETF RFC 5429 This memo updates the definition of the Sieve mail filtering language\n \"reject\" extension, originally defined in RFC 3028.\n\n A \"Joe-job\" is a spam run forged to appear as though it came from an\n innocent party, who is then generally flooded by automated bounces,\n Message Disposition Notifications (MDNs), and personal messages with\n\nStone Standards Track [Page 1]\n\f\nRFC 5429 Sieve Extension: Reject March 2009\n\n complaints. The original Sieve \"reject\" action defined in RFC 3028\n required use of MDNs for rejecting messages, thus contributing to the\n flood of Joe-job spam to victims of Joe-jobs.\n\n This memo updates the definition of the \"reject\" action to allow\n messages to be refused during the SMTP transaction, and defines the\n \"ereject\" action to require messages to be refused during the SMTP\n transaction, if possible.\n\n The \"ereject\" action is intended to replace the \"reject\" action\n wher 5429 delivery http key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6531","type":"specification","body":"IETF","designation":"RFC 6531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6531.txt","https://www.rfc-editor.org/rfc/rfc6531.pdf"],"folder":"IETF/RFC-6531","files":{"txt":{"path":"standards/IETF/RFC-6531/RFC-6531.txt","sha256":"4f48303f7b7659d0b3149730b51a03d59799a95b4d2ca7d913533f97b9db4b40"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an SMTP extension for transport and delivery\n of email messages with internationalized email addresses or header\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6531.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg","scope_keywords":["6531","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null}],"search_text":"IETF RFC 6531 This document specifies an SMTP extension for transport and delivery\n of email messages with internationalized email addresses or header\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6531.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg 6531 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 3207","type":"specification","body":"IETF","designation":"RFC 3207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3207.txt","https://www.rfc-editor.org/rfc/rfc3207.pdf"],"folder":"IETF/RFC-3207","files":{"txt":{"path":"standards/IETF/RFC-3207/RFC-3207.txt","sha256":"b004a203791a1ca664d39a49d73369f88f5f3870486a6639e3f833df2118e4ac"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the SMTP (Simple Mail\n Transfer Protocol) service that allows an SMTP server and client to\n use TLS (Transport Layer Security) to provide private, authenticated\n communication over the Internet. This gives SMTP agents the ability\n to protect some or all of their communications from eavesdroppers and\n attackers.\n\n1. Introduction\n\n SMTP [RFC2821] servers and clients normally communicate in the clear\n over the Internet. In many cases, this communication goes through\n one or more router that is not controlled or trusted by either\n entity. Such an untrusted router might allow a third party to\n monitor or alter the communications between the server and client.\n\n Further, there is often a desire for two SMTP agents to be able to\n authenticate each others' identities. For example, a secure SMTP\n server might only allow communications from other SMTP agents","scope_keywords":["3207","authentication","certificate","delivery","encryption","http","key","policy","tls","trust","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6394","folder":"IETF/RFC-6394","source":"IETF/RFC-6394/RFC-6394.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 7435","folder":"IETF/RFC-7435","source":"IETF/RFC-7435/RFC-7435.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null}],"search_text":"IETF RFC 3207 This document describes an extension to the SMTP (Simple Mail\n Transfer Protocol) service that allows an SMTP server and client to\n use TLS (Transport Layer Security) to provide private, authenticated\n communication over the Internet. This gives SMTP agents the ability\n to protect some or all of their communications from eavesdroppers and\n attackers.\n\n1. Introduction\n\n SMTP [RFC2821] servers and clients normally communicate in the clear\n over the Internet. In many cases, this communication goes through\n one or more router that is not controlled or trusted by either\n entity. Such an untrusted router might allow a third party to\n monitor or alter the communications between the server and client.\n\n Further, there is often a desire for two SMTP agents to be able to\n authenticate each others' identities. For example, a secure SMTP\n server might only allow communications from other SMTP agents 3207 authentication certificate delivery encryption http key policy tls trust verifiable nested-reference unchanged"},{"id":"IETF RFC 2035","type":"specification","body":"IETF","designation":"RFC 2035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2035.txt","https://www.rfc-editor.org/rfc/rfc2035.pdf"],"folder":"IETF/RFC-2035","files":{"txt":{"path":"standards/IETF/RFC-2035/RFC-2035.txt","sha256":"1dc069154f2893b2a8ce688b67b829450d6926d25cf346d3d6bdb7718ae6764d"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the RTP payload format for JPEG video streams.\n The packet format is optimized for real-time video streams where\n codec parameters change rarely from frame to frame.\n\n This document is a product of the Audio-Video Transport working group\n within the Internet Engineering Task Force. Comments are solicited\n and should be addressed to the working group's mailing list at rem-\n conf@es.net and/or the author(s).\n\n1. Introduction\n\n The Joint Photographic Experts Group (JPEG) standard [1,2,3] defines\n a family of compression algorithms for continuous-tone, still images.\n This still image compression standard can be applied to video by\n compressing each frame of video as an independent still image and\n transmitting them in series. Video coded in this fashion is often\n called Motion-JPEG.\n\n We first give an overview of JPEG and then describe the specific\n subset of JPEG that is","scope_keywords":["2035","algorithm","algorithms","attribute","attributes","delivery","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2435","folder":"IETF/RFC-2435","source":"IETF/RFC-2435/RFC-2435.txt","version":null}],"search_text":"IETF RFC 2035 This memo describes the RTP payload format for JPEG video streams.\n The packet format is optimized for real-time video streams where\n codec parameters change rarely from frame to frame.\n\n This document is a product of the Audio-Video Transport working group\n within the Internet Engineering Task Force. Comments are solicited\n and should be addressed to the working group's mailing list at rem-\n conf@es.net and/or the author(s).\n\n1. Introduction\n\n The Joint Photographic Experts Group (JPEG) standard [1,2,3] defines\n a family of compression algorithms for continuous-tone, still images.\n This still image compression standard can be applied to video by\n compressing each frame of video as an independent still image and\n transmitting them in series. Video coded in this fashion is often\n called Motion-JPEG.\n\n We first give an overview of JPEG and then describe the specific\n subset of JPEG that is 2035 algorithm algorithms attribute attributes delivery timestamp nested-reference unchanged"},{"id":"IETF RFC 2451","type":"specification","body":"IETF","designation":"RFC 2451","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2451.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2451.txt","https://www.rfc-editor.org/rfc/rfc2451.pdf"],"folder":"IETF/RFC-2451","files":{"txt":{"path":"standards/IETF/RFC-2451/RFC-2451.txt","sha256":"26eec284895bb3b17bb24fda8600d99d834193a1d68e3bc0fb6ae2b58349d538"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use CBC-mode cipher algorithms with\n the IPSec ESP (Encapsulating Security Payload) Protocol. It not only\n clearly states how to use certain cipher algorithms, but also how to\n use all CBC-mode cipher algorithms.","scope_keywords":["2451","algorithm","algorithms","key","keys","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 2451 This document describes how to use CBC-mode cipher algorithms with\n the IPSec ESP (Encapsulating Security Payload) Protocol. It not only\n clearly states how to use certain cipher algorithms, but also how to\n use all CBC-mode cipher algorithms. 2451 algorithm algorithms key keys license nested-reference unchanged"},{"id":"IETF RFC 3962","type":"specification","body":"IETF","designation":"RFC 3962","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3962.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3962.txt","https://www.rfc-editor.org/rfc/rfc3962.pdf"],"folder":"IETF/RFC-3962","files":{"txt":{"path":"standards/IETF/RFC-3962/RFC-3962.txt","sha256":"1a6bf9edff650f92e8c5f85a450335c168545169bfdd51977393d15a6932f1f0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Raeburn\nRequest for Comments: 3962 MIT\nCategory: Standards Track February 2005\n\n Advanced Encryption Standard (AES) Encryption for Kerberos 5\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The United States National Institute of Standards and Technology\n (NIST) has chosen a new Advanced Encryption Standard (AES), which is\n significantly faster and (it is believed) more secure than the old\n Data Encryption Standard (DES) algorithm. This document is a\n specification for the additio","scope_keywords":["3962","algorithm","authentication","encryption","key","keys","presentation","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 3962 Network Working Group K. Raeburn\nRequest for Comments: 3962 MIT\nCategory: Standards Track February 2005\n\n Advanced Encryption Standard (AES) Encryption for Kerberos 5\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The United States National Institute of Standards and Technology\n (NIST) has chosen a new Advanced Encryption Standard (AES), which is\n significantly faster and (it is believed) more secure than the old\n Data Encryption Standard (DES) algorithm. This document is a\n specification for the additio 3962 algorithm authentication encryption key keys presentation profile timestamp nested-reference unchanged"},{"id":"IETF RFC 2043","type":"specification","body":"IETF","designation":"RFC 2043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2043.txt","https://www.rfc-editor.org/rfc/rfc2043.pdf"],"folder":"IETF/RFC-2043","files":{"txt":{"path":"standards/IETF/RFC-2043/RFC-2043.txt","sha256":"eb19ed940df5310e0e873f66e67d0711ce2ce853cf8b599b657ee36cd1111df0"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocols for establishing\n and configuring Systems Network Architecture (SNA) over PPP and SNA\n over LLC 802.2 over PPP.","scope_keywords":["2043","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2043 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n This document defines the Network Control Protocols for establishing\n and configuring Systems Network Architecture (SNA) over PPP and SNA\n over LLC 802.2 over PPP. 2043 path nested-reference unchanged"},{"id":"IETF RFC 2683","type":"specification","body":"IETF","designation":"RFC 2683","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2683.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2683.txt","https://www.rfc-editor.org/rfc/rfc2683.pdf"],"folder":"IETF/RFC-2683","files":{"txt":{"path":"standards/IETF/RFC-2683/RFC-2683.txt","sha256":"6a6f6e88af9e26bbee153d4f6925502463df8389bf6acb18be4c64500926fc8c"}},"tags":["nested-reference","unchanged"],"summary":"The IMAP4 specification [RFC-2060] describes a rich protocol for use\n in building clients and servers for storage, retrieval, and\n manipulation of electronic mail. Because the protocol is so rich and\n has so many implementation choices, there are often trade-offs that\n must be made and issues that must be considered when designing such\n clients and servers. This document attempts to outline these issues\n and to make recommendations in order to make the end products as\n interoperable as possible.\n\n2. Conventions used in this document\n\n In examples, \"C:\" indicates lines sent by a client that is connected\n to a server. \"S:\" indicates lines sent by the server to the client.\n\n The words \"must\", \"must not\", \"should\", \"should not\", and \"may\" are\n used with specific meaning in this document; since their meaning is\n somewhat different from that specified in RFC 2119, we do not put\n them in all ca","scope_keywords":["2683"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2683 The IMAP4 specification [RFC-2060] describes a rich protocol for use\n in building clients and servers for storage, retrieval, and\n manipulation of electronic mail. Because the protocol is so rich and\n has so many implementation choices, there are often trade-offs that\n must be made and issues that must be considered when designing such\n clients and servers. This document attempts to outline these issues\n and to make recommendations in order to make the end products as\n interoperable as possible.\n\n2. Conventions used in this document\n\n In examples, \"C:\" indicates lines sent by a client that is connected\n to a server. \"S:\" indicates lines sent by the server to the client.\n\n The words \"must\", \"must not\", \"should\", \"should not\", and \"may\" are\n used with specific meaning in this document; since their meaning is\n somewhat different from that specified in RFC 2119, we do not put\n them in all ca 2683 nested-reference unchanged"},{"id":"IETF RFC 3162","type":"specification","body":"IETF","designation":"RFC 3162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3162.txt","https://www.rfc-editor.org/rfc/rfc3162.pdf"],"folder":"IETF/RFC-3162","files":{"txt":{"path":"standards/IETF/RFC-3162/RFC-3162.txt","sha256":"82092f73c803d44115a8add56a91bde83b95977e144dc0da1f0bafc1951e8c03"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the operation of RADIUS (Remote\n Authentication Dial In User Service) when run over IPv6 as well as\n the RADIUS attributes used to support IPv6 network access.\n\n1. Introduction\n\n This document specifies the operation of RADIUS [4]-[8] over IPv6\n [13] as well as the RADIUS attributes used to support IPv6 network\n access.\n\n Note that a NAS sending a RADIUS Access-Request may not know a-priori\n whether the host will be using IPv4, IPv6, or both. For example,\n within PPP, IPv6CP [11] occurs after LCP, so that address assignment\n will not occur until after RADIUS authentication and authorization\n has completed.\n\n Therefore it is presumed that the IPv6 attributes described in this\n document MAY be sent along with IPv4-related attributes within the\n same RADIUS message and that the NAS will decide which attributes to\n use. The NAS SHOULD only allocate addresses and prefi","scope_keywords":["3162","attribute","attributes","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3633","folder":"IETF/RFC-3633","source":"IETF/RFC-3633/RFC-3633.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3162 This document specifies the operation of RADIUS (Remote\n Authentication Dial In User Service) when run over IPv6 as well as\n the RADIUS attributes used to support IPv6 network access.\n\n1. Introduction\n\n This document specifies the operation of RADIUS [4]-[8] over IPv6\n [13] as well as the RADIUS attributes used to support IPv6 network\n access.\n\n Note that a NAS sending a RADIUS Access-Request may not know a-priori\n whether the host will be using IPv4, IPv6, or both. For example,\n within PPP, IPv6CP [11] occurs after LCP, so that address assignment\n will not occur until after RADIUS authentication and authorization\n has completed.\n\n Therefore it is presumed that the IPv6 attributes described in this\n document MAY be sent along with IPv4-related attributes within the\n same RADIUS message and that the NAS will decide which attributes to\n use. The NAS SHOULD only allocate addresses and prefi 3162 attribute attributes authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 2077","type":"specification","body":"IETF","designation":"RFC 2077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2077.txt","https://www.rfc-editor.org/rfc/rfc2077.pdf"],"folder":"IETF/RFC-2077","files":{"txt":{"path":"standards/IETF/RFC-2077/RFC-2077.txt","sha256":"f9f7c8cf2cb8bf3f19afc3d4459548be73400d966ed092fad72773b62f32c271"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Nelson\nRequest for Comments: 2077 LLNL\nCategory: Standards Track C. Parks\n NIST\n Mitra\n WorldMaker\n January 1997\n\n The Model Primary Content Type for\n Multipurpose Internet Mail Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n The purpose of this memo is to propose an update to Internet RFC 2045\n to include a new primary content-type to be known as \"model\". RFC\n 2045 [1] describes mechanisms for specifying and describing the\n format of Internet Message Bodies via content-type/subtype pairs. We\n believe that \"model\" defines a fun","scope_keywords":["2077","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2077 Network Working Group S. Nelson\nRequest for Comments: 2077 LLNL\nCategory: Standards Track C. Parks\n NIST\n Mitra\n WorldMaker\n January 1997\n\n The Model Primary Content Type for\n Multipurpose Internet Mail Extensions\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nIntroduction\n\n The purpose of this memo is to propose an update to Internet RFC 2045\n to include a new primary content-type to be known as \"model\". RFC\n 2045 [1] describes mechanisms for specifying and describing the\n format of Internet Message Bodies via content-type/subtype pairs. We\n believe that \"model\" defines a fun 2077 key presentation nested-reference unchanged"},{"id":"IETF RFC 2306","type":"specification","body":"IETF","designation":"RFC 2306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2306.txt","https://www.rfc-editor.org/rfc/rfc2306.pdf"],"folder":"IETF/RFC-2306","files":{"txt":{"path":"standards/IETF/RFC-2306/RFC-2306.txt","sha256":"71bdc119e945bb1c9c595856a3b7b854edeeb49d4b316737c079595375fa1f7e"}},"tags":["nested-reference","unchanged"],"summary":"This document references the Tag Image File Format (TIFF) to define\n the F profile of TIFF for facsimile (TIFF-F) as a file format that\n may be used for the storage and interchange of facsimile images.\n\n2. TIFF Definition\n\n TIFF (Tag Image File Format) Revision 6.0 is defined in detail within\n [TIFF].\n\n A brief review of concepts used in TIFF is included in this document\n as background information, but the reader is directed to the original\n TIFF specification [TIFF] to obtain specific technical details.\n\nParsons & Rafferty Informational [Page 1]\n\f\nRFC 2306 TIFF-F Profile March 1998","scope_keywords":["2306","attribute","attributes","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2301","folder":"IETF/RFC-2301","source":"IETF/RFC-2301/RFC-2301.txt","version":null},{"body":"IETF","designation":"RFC 2302","folder":"IETF/RFC-2302","source":"IETF/RFC-2302/RFC-2302.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null}],"search_text":"IETF RFC 2306 This document references the Tag Image File Format (TIFF) to define\n the F profile of TIFF for facsimile (TIFF-F) as a file format that\n may be used for the storage and interchange of facsimile images.\n\n2. TIFF Definition\n\n TIFF (Tag Image File Format) Revision 6.0 is defined in detail within\n [TIFF].\n\n A brief review of concepts used in TIFF is included in this document\n as background information, but the reader is directed to the original\n TIFF specification [TIFF] to obtain specific technical details.\n\nParsons & Rafferty Informational [Page 1]\n\f\nRFC 2306 TIFF-F Profile March 1998 2306 attribute attributes key profile nested-reference unchanged"},{"id":"IETF RFC 2703","type":"specification","body":"IETF","designation":"RFC 2703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2703.txt","https://www.rfc-editor.org/rfc/rfc2703.pdf"],"folder":"IETF/RFC-2703","files":{"txt":{"path":"standards/IETF/RFC-2703/RFC-2703.txt","sha256":"c542f5b40bb956bee88bcaff97649fa6effe95d4acd61b5a28f6c6d1aaf8f9b2"}},"tags":["nested-reference","unchanged"],"summary":"A number of Internet application protocols have a need to provide\n content negotiation for the resources with which they interact. MIME\n media types [1,2] provide a standard method for handling one major\n axis of variation, but resources also vary in ways which cannot be\n expressed using currently available MIME headers.\n\n This memo sets out terminology, an abstract framework and goals for\n protocol-independent content negotiation, and identifies some\n technical issues which may need to be addressed.\n\n The abstract framework does not attempt to specify the content\n negotiation process, but gives an indication of the anticipated scope\n and form of any such specification. The goals set out the desired\n properties of a content negotiation mechanism.","scope_keywords":["2703","attribute","http","identification","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null}],"search_text":"IETF RFC 2703 A number of Internet application protocols have a need to provide\n content negotiation for the resources with which they interact. MIME\n media types [1,2] provide a standard method for handling one major\n axis of variation, but resources also vary in ways which cannot be\n expressed using currently available MIME headers.\n\n This memo sets out terminology, an abstract framework and goals for\n protocol-independent content negotiation, and identifies some\n technical issues which may need to be addressed.\n\n The abstract framework does not attempt to specify the content\n negotiation process, but gives an indication of the anticipated scope\n and form of any such specification. The goals set out the desired\n properties of a content negotiation mechanism. 2703 attribute http identification presentation nested-reference unchanged"},{"id":"IETF RFC 2779","type":"specification","body":"IETF","designation":"RFC 2779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2779.txt","https://www.rfc-editor.org/rfc/rfc2779.pdf"],"folder":"IETF/RFC-2779","files":{"txt":{"path":"standards/IETF/RFC-2779/RFC-2779.txt","sha256":"bb45530c259d4aa2e20471f36e9a680c8a311dc2dee203aab9e189e94b05e459"}},"tags":["nested-reference","unchanged"],"summary":"Presence and Instant Messaging have recently emerged as a new medium\n of communications over the Internet. Presence is a means for\n finding, retrieving, and subscribing to changes in the presence\n information (e.g. \"online\" or \"offline\") of other users. Instant\n messaging is a means for sending small, simple messages that are\n delivered immediately to online users.\n\n Applications of presence and instant messaging currently use\n independent, non-standard and non-interoperable protocols developed\n by various vendors. The goal of the Instant Messaging and Presence\n Protocol (IMPP) Working Group is to define a standard protocol so\n that independently developed applications of instant messaging and/or\n presence can interoperate across the Internet. This document defines\n a minimal set of requirements that IMPP must meet.\n\nDay, et al. Informational [Page 1]\n\f\nRFC 2779 Instant Messaging/Presenc","scope_keywords":["2779","authentication","delivery","encryption","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null}],"search_text":"IETF RFC 2779 Presence and Instant Messaging have recently emerged as a new medium\n of communications over the Internet. Presence is a means for\n finding, retrieving, and subscribing to changes in the presence\n information (e.g. \"online\" or \"offline\") of other users. Instant\n messaging is a means for sending small, simple messages that are\n delivered immediately to online users.\n\n Applications of presence and instant messaging currently use\n independent, non-standard and non-interoperable protocols developed\n by various vendors. The goal of the Instant Messaging and Presence\n Protocol (IMPP) Working Group is to define a standard protocol so\n that independently developed applications of instant messaging and/or\n presence can interoperate across the Internet. This document defines\n a minimal set of requirements that IMPP must meet.\n\nDay, et al. Informational [Page 1]\n\f\nRFC 2779 Instant Messaging/Presenc 2779 authentication delivery encryption policies nested-reference unchanged"},{"id":"IETF RFC 2781","type":"specification","body":"IETF","designation":"RFC 2781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2781.txt","https://www.rfc-editor.org/rfc/rfc2781.pdf"],"folder":"IETF/RFC-2781","files":{"txt":{"path":"standards/IETF/RFC-2781/RFC-2781.txt","sha256":"e3fed703a962e1e8a1740fef500d1908df3eca2d80de8bad012835f0ae75b502"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman\nRequest for Comments: 2781 Internet Mail Consortium\nCategory: Informational F. Yergeau\n Alis Technologies\n February 2000\n\n UTF-16, an encoding of ISO 10646\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\n1. Introduction\n\n This document describes the UTF-16 encoding of Unicode/ISO-10646,\n addresses the issues of serializing UTF-16 as an octet stream for\n transmission over the Internet, discusses MIME charset naming as\n described in [CHARSET-REG], and contains the registration for three\n MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE\n (little-endian), and UTF-16.\n\n1.1 Background and motivation\n\n The Unicode Standard [UNICODE] and ","scope_keywords":["2781","algorithm","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2803","folder":"IETF/RFC-2803","source":"IETF/RFC-2803/RFC-2803.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null}],"search_text":"IETF RFC 2781 Network Working Group P. Hoffman\nRequest for Comments: 2781 Internet Mail Consortium\nCategory: Informational F. Yergeau\n Alis Technologies\n February 2000\n\n UTF-16, an encoding of ISO 10646\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\n1. Introduction\n\n This document describes the UTF-16 encoding of Unicode/ISO-10646,\n addresses the issues of serializing UTF-16 as an octet stream for\n transmission over the Internet, discusses MIME charset naming as\n described in [CHARSET-REG], and contains the registration for three\n MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE\n (little-endian), and UTF-16.\n\n1.1 Background and motivation\n\n The Unicode Standard [UNICODE] and  2781 algorithm key policy nested-reference unchanged"},{"id":"IETF RFC 2912","type":"specification","body":"IETF","designation":"RFC 2912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2912.txt","https://www.rfc-editor.org/rfc/rfc2912.pdf"],"folder":"IETF/RFC-2912","files":{"txt":{"path":"standards/IETF/RFC-2912/RFC-2912.txt","sha256":"d1f9542e3168cae1785dff4358cd0b0b631401dfddc5d7697f4dbd7418066ad7"}},"tags":["nested-reference","unchanged"],"summary":"In \"A Syntax for Describing Media Feature Sets\", an expression format\n is presented for describing media feature capabilities using simple\n media feature tags.\n\n This memo defines a Multipurpose Internet Mail Extensions (MIME)\n 'Content-features:' header that can be used to annotate a MIME\n message part using this expression format, and indicates some ways it\n might be used.\n\nKlyne Standards Track [Page 1]\n\f\nRFC 2912 Indicating Media Features for MIME Content September 2000","scope_keywords":["2912","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3236","folder":"IETF/RFC-3236","source":"IETF/RFC-3236/RFC-3236.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null}],"search_text":"IETF RFC 2912 In \"A Syntax for Describing Media Feature Sets\", an expression format\n is presented for describing media feature capabilities using simple\n media feature tags.\n\n This memo defines a Multipurpose Internet Mail Extensions (MIME)\n 'Content-features:' header that can be used to annotate a MIME\n message part using this expression format, and indicates some ways it\n might be used.\n\nKlyne Standards Track [Page 1]\n\f\nRFC 2912 Indicating Media Features for MIME Content September 2000 2912 registered nested-reference unchanged"},{"id":"IETF RFC 2913","type":"specification","body":"IETF","designation":"RFC 2913","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2913.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2913.txt","https://www.rfc-editor.org/rfc/rfc2913.pdf"],"folder":"IETF/RFC-2913","files":{"txt":{"path":"standards/IETF/RFC-2913/RFC-2913.txt","sha256":"720796e64ba4867a1c2dc27c7ef9835ef6645d1121881c6557eaf396bf87dd3a"}},"tags":["nested-reference","unchanged"],"summary":"In \"A Syntax for Describing Media Feature Sets\", an expression format\n is presented for describing media feature capabilities using simple\n media feature tags.\n\n This memo defines a media feature tag whose value is a Multipurpose\n Internet Mail Extensions (MIME) content type. This allows the\n construction of feature expressions that take account of the MIME\n content type of the corresponding data.","scope_keywords":["2913","http","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null}],"search_text":"IETF RFC 2913 In \"A Syntax for Describing Media Feature Sets\", an expression format\n is presented for describing media feature capabilities using simple\n media feature tags.\n\n This memo defines a media feature tag whose value is a Multipurpose\n Internet Mail Extensions (MIME) content type. This allows the\n construction of feature expressions that take account of the MIME\n content type of the corresponding data. 2913 http registered nested-reference unchanged"},{"id":"IETF RFC 3126","type":"specification","body":"IETF","designation":"RFC 3126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3126.txt","https://www.rfc-editor.org/rfc/rfc3126.pdf"],"folder":"IETF/RFC-3126","files":{"txt":{"path":"standards/IETF/RFC-3126/RFC-3126.txt","sha256":"0a54413db0c75ac43de085599c6ff426fad92e3eecc9b5f24397a4095882be2e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format of an electronic signature that can\n remain valid over long periods. This includes evidence as to its\n validity even if the signer or verifying party later attempts to deny\n (i.e., repudiates the validity of the signature).\n\n The format can be considered as an extension to RFC 2630 and RFC\n 2634, where, when appropriate additional signed and unsigned\n attributes have been defined.\n\n The contents of this Informational RFC is technically equivalent to\n ETSI TS 101 733 V.1.2.2. The ETSI TS is under the ETSI Copyright (C).\n Individual copies of this ETSI deliverable can be downloaded from\n http://www.etsi.org\n\nPinkas, et al. Informational [Page 1]\n\f\nRFC 3126 Electronic Signature Formats September 2001","scope_keywords":["3126","algorithm","algorithms","attribute","attributes","certificate","certificates","crl","http","key","policy","revocation","signature","signatures","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"IETF RFC 3126 This document defines the format of an electronic signature that can\n remain valid over long periods. This includes evidence as to its\n validity even if the signer or verifying party later attempts to deny\n (i.e., repudiates the validity of the signature).\n\n The format can be considered as an extension to RFC 2630 and RFC\n 2634, where, when appropriate additional signed and unsigned\n attributes have been defined.\n\n The contents of this Informational RFC is technically equivalent to\n ETSI TS 101 733 V.1.2.2. The ETSI TS is under the ETSI Copyright (C).\n Individual copies of this ETSI deliverable can be downloaded from\n http://www.etsi.org\n\nPinkas, et al. Informational [Page 1]\n\f\nRFC 3126 Electronic Signature Formats September 2001 3126 algorithm algorithms attribute attributes certificate certificates crl http key policy revocation signature signatures validation nested-reference unchanged"},{"id":"IETF RFC 3204","type":"specification","body":"IETF","designation":"RFC 3204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3204.txt","https://www.rfc-editor.org/rfc/rfc3204.pdf"],"folder":"IETF/RFC-3204","files":{"txt":{"path":"standards/IETF/RFC-3204/RFC-3204.txt","sha256":"05d7ec1d50abd1749767107c293932a3b8fb7b52e4c019264a77bc431467b4a0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes MIME types for application/ISUP and\n application/QSIG objects for use in SIP applications, according to\n the rules defined in RFC 2048. These types can be used to identify\n ISUP and QSIG objects within a SIP message such as INVITE or INFO, as\n might be implemented when using SIP in an environment where part of\n the call involves interworking to the PSTN.\n\n1. Introduction\n\n ISUP (ISDN User part) defined in the ITU-T recommendations Q.761-4 is\n a signaling protocol used between telephony switches. There are\n configurations in which ISUP-encoded signaling information needs to\n be transported between SIP entities as part of the payload of SIP\n messages, where the preservation of ISUP data is necessary for the\n proper operation of PSTN features.\n\nZimmerer, et al. Standards Track [Page 1]\n\f\nRFC 3204 ISUP and QSIG MIME Objects December 2001\n\n QSIG is the analogous signal","scope_keywords":["3204","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null}],"search_text":"IETF RFC 3204 This document describes MIME types for application/ISUP and\n application/QSIG objects for use in SIP applications, according to\n the rules defined in RFC 2048. These types can be used to identify\n ISUP and QSIG objects within a SIP message such as INVITE or INFO, as\n might be implemented when using SIP in an environment where part of\n the call involves interworking to the PSTN.\n\n1. Introduction\n\n ISUP (ISDN User part) defined in the ITU-T recommendations Q.761-4 is\n a signaling protocol used between telephony switches. There are\n configurations in which ISUP-encoded signaling information needs to\n be transported between SIP entities as part of the payload of SIP\n messages, where the preservation of ISUP data is necessary for the\n proper operation of PSTN features.\n\nZimmerer, et al. Standards Track [Page 1]\n\f\nRFC 3204 ISUP and QSIG MIME Objects December 2001\n\n QSIG is the analogous signal 3204 preservation nested-reference unchanged"},{"id":"IETF RFC 3288","type":"specification","body":"IETF","designation":"RFC 3288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3288.txt","https://www.rfc-editor.org/rfc/rfc3288.pdf"],"folder":"IETF/RFC-3288","files":{"txt":{"path":"standards/IETF/RFC-3288/RFC-3288.txt","sha256":"b4fc7599817c4fe5cf40877c63f1bd8deaa55e868bbb0fcbf8727dcb236e56c4"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies a Simple Object Access Protocol (SOAP) binding to\n the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding\n describes how SOAP messages are transmitted in the network.\n\n The SOAP is an XML-based (extensible markup language) messaging\n protocol used to implement a wide variety of distributed messaging\n models. It defines a message format and describes a variety of\n message patterns, including, but not limited to, RPC, asynchronous\n event notification, unacknowledged messages, and forwarding via SOAP\n intermediaries.\n\nO'Tuathail & Rose Standards Track [Page 1]\n\f\nRFC 3288 Using SOAP in BEEP June 2002","scope_keywords":["3288","attribute","http","identification","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null}],"search_text":"IETF RFC 3288 This memo specifies a Simple Object Access Protocol (SOAP) binding to\n the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding\n describes how SOAP messages are transmitted in the network.\n\n The SOAP is an XML-based (extensible markup language) messaging\n protocol used to implement a wide variety of distributed messaging\n models. It defines a message format and describes a variety of\n message patterns, including, but not limited to, RPC, asynchronous\n event notification, unacknowledged messages, and forwarding via SOAP\n intermediaries.\n\nO'Tuathail & Rose Standards Track [Page 1]\n\f\nRFC 3288 Using SOAP in BEEP June 2002 3288 attribute http identification path profile nested-reference unchanged"},{"id":"IETF RFC 3310","type":"specification","body":"IETF","designation":"RFC 3310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3310.txt","https://www.rfc-editor.org/rfc/rfc3310.pdf"],"folder":"IETF/RFC-3310","files":{"txt":{"path":"standards/IETF/RFC-3310/RFC-3310.txt","sha256":"64cd930886d672e829c105b6e903cb195c488179fe98f7e2c374e2b050d27fc9"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies an Authentication and Key Agreement (AKA) based\n one-time password generation mechanism for Hypertext Transfer\n Protocol (HTTP) Digest access authentication. The HTTP\n Authentication Framework includes two authentication schemes: Basic\n and Digest. Both schemes employ a shared secret based mechanism for\n access authentication. The AKA mechanism performs user\n authentication and session key distribution in Universal Mobile\n Telecommunications System (UMTS) networks. AKA is a challenge-\n response based mechanism that uses symmetric cryptography.\n\nNiemi, et. al. Informational [Page 1]\n\f\nRFC 3310 HTTP Digest Authentication Using AKA September 2002","scope_keywords":["3310","algorithm","algorithms","authentication","credential","credentials","encryption","hash","http","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null}],"search_text":"IETF RFC 3310 This memo specifies an Authentication and Key Agreement (AKA) based\n one-time password generation mechanism for Hypertext Transfer\n Protocol (HTTP) Digest access authentication. The HTTP\n Authentication Framework includes two authentication schemes: Basic\n and Digest. Both schemes employ a shared secret based mechanism for\n access authentication. The AKA mechanism performs user\n authentication and session key distribution in Universal Mobile\n Telecommunications System (UMTS) networks. AKA is a challenge-\n response based mechanism that uses symmetric cryptography.\n\nNiemi, et. al. Informational [Page 1]\n\f\nRFC 3310 HTTP Digest Authentication Using AKA September 2002 3310 algorithm algorithms authentication credential credentials encryption hash http identification key nested-reference unchanged"},{"id":"IETF RFC 3502","type":"specification","body":"IETF","designation":"RFC 3502","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3502.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3502.txt","https://www.rfc-editor.org/rfc/rfc3502.pdf"],"folder":"IETF/RFC-3502","files":{"txt":{"path":"standards/IETF/RFC-3502/RFC-3502.txt","sha256":"a724f7727ec12296542b88491743cafe42fbce0954b063adc743043abde06378"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the multiappending extension to the Internet\n Message Access Protocol (IMAP) (RFC 3501). This extension provides\n substantial performance improvements for IMAP clients which upload\n multiple messages at a time to a mailbox on the server.\n\n A server which supports this extension indicates this with a\n capability name of \"MULTIAPPEND\".\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"MAY\", and \"OPTIONAL\" in this document are to\n be interpreted as described in [KEYWORDS].","scope_keywords":["3502","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4315","folder":"IETF/RFC-4315","source":"IETF/RFC-4315/RFC-4315.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3502 This document describes the multiappending extension to the Internet\n Message Access Protocol (IMAP) (RFC 3501). This extension provides\n substantial performance improvements for IMAP clients which upload\n multiple messages at a time to a mailbox on the server.\n\n A server which supports this extension indicates this with a\n capability name of \"MULTIAPPEND\".\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"MAY\", and \"OPTIONAL\" in this document are to\n be interpreted as described in [KEYWORDS]. 3502 key subject nested-reference unchanged"},{"id":"IETF RFC 3516","type":"specification","body":"IETF","designation":"RFC 3516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3516.txt","https://www.rfc-editor.org/rfc/rfc3516.pdf"],"folder":"IETF/RFC-3516","files":{"txt":{"path":"standards/IETF/RFC-3516/RFC-3516.txt","sha256":"53b70a42caba0863cdd4e054a097acd6a073261eef5c2f0585670e318c35bc00"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the Binary extension to the Internet Message Access\n Protocol (IMAP4). It provides a mechanism for IMAP4 clients and\n servers to exchange message body data without using a MIME content-\n transfer-encoding.\n\n1. Conventions Used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document are to be interpreted as described in [KEYWORD].\n\n The abbreviation \"CTE\" means content-transfer-encoding.\n\n2. Introduction\n\n The MIME extensions to Internet messaging allow for the transmission\n of non-textual (binary) message content [MIME-IMB]. Since the\n traditional transports for messaging are not always capable of\n passing binary data transparently, MIME provides encoding schemes\n that allow binary content to be transmitted over transports that are\n not otherwise able to do so.\n\n The overhead of MIME-encoding this content can be considera","scope_keywords":["3516","algorithm","crl","identification","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3516 This memo defines the Binary extension to the Internet Message Access\n Protocol (IMAP4). It provides a mechanism for IMAP4 clients and\n servers to exchange message body data without using a MIME content-\n transfer-encoding.\n\n1. Conventions Used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document are to be interpreted as described in [KEYWORD].\n\n The abbreviation \"CTE\" means content-transfer-encoding.\n\n2. Introduction\n\n The MIME extensions to Internet messaging allow for the transmission\n of non-textual (binary) message content [MIME-IMB]. Since the\n traditional transports for messaging are not always capable of\n passing binary data transparently, MIME provides encoding schemes\n that allow binary content to be transmitted over transports that are\n not otherwise able to do so.\n\n The overhead of MIME-encoding this content can be considera 3516 algorithm crl identification key presentation nested-reference unchanged"},{"id":"IETF RFC 3536","type":"specification","body":"IETF","designation":"RFC 3536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3536.txt","https://www.rfc-editor.org/rfc/rfc3536.pdf"],"folder":"IETF/RFC-3536","files":{"txt":{"path":"standards/IETF/RFC-3536/RFC-3536.txt","sha256":"16e7b66ad11a1ae159fbf70d2f595d6b927a6cbfc7a3a8f7af85a89b0e89cbcd"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a glossary of terms used in the IETF when\n discussing internationalization. The purpose is to help frame\n discussions of internationalization in the various areas of the IETF\n and to help introduce the main concepts to IETF participants.","scope_keywords":["3536","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"IETF RFC 3536 This document provides a glossary of terms used in the IETF when\n discussing internationalization. The purpose is to help frame\n discussions of internationalization in the various areas of the IETF\n and to help introduce the main concepts to IETF participants. 3536 subject nested-reference unchanged"},{"id":"IETF RFC 3629","type":"specification","body":"IETF","designation":"RFC 3629","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3629.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3629.txt","https://www.rfc-editor.org/rfc/rfc3629.pdf"],"folder":"IETF/RFC-3629","files":{"txt":{"path":"standards/IETF/RFC-3629/RFC-3629.txt","sha256":"a2a3a39457d30420c812f87a38cc2b9194832f6982ef17e619de7d816879d6a6"}},"tags":["nested-reference","unchanged"],"summary":"ISO/IEC 10646-1 defines a large character set called the Universal\n Character Set (UCS) which encompasses most of the world's writing\n systems. The originally proposed encodings of the UCS, however, were\n not compatible with many current applications and protocols, and this\n has led to the development of UTF-8, the object of this memo. UTF-8\n has the characteristic of preserving the full US-ASCII range,\n providing compatibility with file systems, parsers and other software\n that rely on US-ASCII values but are transparent to other values.\n This memo obsoletes and replaces RFC 2279.","scope_keywords":["3629","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5051","folder":"IETF/RFC-5051","source":"IETF/RFC-5051/RFC-5051.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null}],"search_text":"IETF RFC 3629 ISO/IEC 10646-1 defines a large character set called the Universal\n Character Set (UCS) which encompasses most of the world's writing\n systems. The originally proposed encodings of the UCS, however, were\n not compatible with many current applications and protocols, and this\n has led to the development of UTF-8, the object of this memo. UTF-8\n has the characteristic of preserving the full US-ASCII range,\n providing compatibility with file systems, parsers and other software\n that rely on US-ASCII values but are transparent to other values.\n This memo obsoletes and replaces RFC 2279. 3629 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3798","type":"specification","body":"IETF","designation":"RFC 3798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3798.txt","https://www.rfc-editor.org/rfc/rfc3798.pdf"],"folder":"IETF/RFC-3798","files":{"txt":{"path":"standards/IETF/RFC-3798/RFC-3798.txt","sha256":"e3f41ae826f0c4d73596b191c5a75ecd2908e3f78af00fa1d1d278908312a6d1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIME content-type that may be used by a mail user\n agent (MUA) or electronic mail gateway to report the disposition of a\n message after it has been successfully delivered to a recipient.\n This content-type is intended to be machine-processable. Additional\n message headers are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and often referred to as \"read receipts,\"\n \"acknowledgements\", or \"receipt notifications.\" The intention is to\n do this while respecting privacy concerns, which have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as","scope_keywords":["3798","attribute","attributes","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"IETF RFC 3798 This memo defines a MIME content-type that may be used by a mail user\n agent (MUA) or electronic mail gateway to report the disposition of a\n message after it has been successfully delivered to a recipient.\n This content-type is intended to be machine-processable. Additional\n message headers are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and often referred to as \"read receipts,\"\n \"acknowledgements\", or \"receipt notifications.\" The intention is to\n do this while respecting privacy concerns, which have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging systems (such as 3798 attribute attributes delivery key nested-reference unchanged"},{"id":"IETF RFC 3834","type":"specification","body":"IETF","designation":"RFC 3834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3834.txt","https://www.rfc-editor.org/rfc/rfc3834.pdf"],"folder":"IETF/RFC-3834","files":{"txt":{"path":"standards/IETF/RFC-3834/RFC-3834.txt","sha256":"e8ac97cceb6205dd2a722b05fb6b1c1dd1dff0996287af2f513a2d90bb643820"}},"tags":["nested-reference","unchanged"],"summary":"This memo makes recommendations for software that automatically\n responds to incoming electronic mail messages, including \"out of the\n office\" or \"vacation\" response generators, mail filtering software,\n email-based information services, and other automatic responders.\n The purpose of these recommendations is to discourage undesirable\n behavior which is caused or aggravated by such software, to encourage\n uniform behavior (where appropriate) among automatic mail responders,\n and to clear up some sources of confusion among implementors of\n automatic email responders.\n\n1. Introduction\n\n Many programs which automatically respond to email are currently in\n use. Although these programs vary widely in their function, several\n problems with this class of programs have been observed, including:\n significant numbers of useless or unwanted response and responses\n sent to inappropriate addresses, a","scope_keywords":["3834","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null}],"search_text":"IETF RFC 3834 This memo makes recommendations for software that automatically\n responds to incoming electronic mail messages, including \"out of the\n office\" or \"vacation\" response generators, mail filtering software,\n email-based information services, and other automatic responders.\n The purpose of these recommendations is to discourage undesirable\n behavior which is caused or aggravated by such software, to encourage\n uniform behavior (where appropriate) among automatic mail responders,\n and to clear up some sources of confusion among implementors of\n automatic email responders.\n\n1. Introduction\n\n Many programs which automatically respond to email are currently in\n use. Although these programs vary widely in their function, several\n problems with this class of programs have been observed, including:\n significant numbers of useless or unwanted response and responses\n sent to inappropriate addresses, a 3834 delivery key subject nested-reference unchanged"},{"id":"IETF RFC 3839","type":"specification","body":"IETF","designation":"RFC 3839","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3839.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3839.txt","https://www.rfc-editor.org/rfc/rfc3839.pdf"],"folder":"IETF/RFC-3839","files":{"txt":{"path":"standards/IETF/RFC-3839/RFC-3839.txt","sha256":"cda109997c24e46efba9be3434c2411cfd924f06ca83f8404d7c3db5625f32b2"}},"tags":["nested-reference","unchanged"],"summary":"This document serves to register and document the standard MIME types\n associated with the 3GPP multimedia file format, which is part of the\n family based on the ISO Media File Format.\n\n1. Introduction\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n The third-generation partnership project (3GPP) for third-generation\n cellular telephony has defined a standard file format to contain\n audio/visual sequences which may be downloaded to cellular phones\n [3GPP]. At the time of writing, the 3GPP file format (3GP) can\n contain H.263 or MPEG-4 video, and AMR Narrow-band speech, AMR wide-\n band speech, or AAC audio, and 3GPP timed text.\n\n Within the file, as with all files in the 'ISO' family, there is an\n intrinsic file-type box","scope_keywords":["3839","authentication","encryption","http","identification","key","presentation","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null}],"search_text":"IETF RFC 3839 This document serves to register and document the standard MIME types\n associated with the 3GPP multimedia file format, which is part of the\n family based on the ISO Media File Format.\n\n1. Introduction\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n The third-generation partnership project (3GPP) for third-generation\n cellular telephony has defined a standard file format to contain\n audio/visual sequences which may be downloaded to cellular phones\n [3GPP]. At the time of writing, the 3GPP file format (3GP) can\n contain H.263 or MPEG-4 video, and AMR Narrow-band speech, AMR wide-\n band speech, or AAC audio, and 3GPP timed text.\n\n Within the file, as with all files in the 'ISO' family, there is an\n intrinsic file-type box 3839 authentication encryption http identification key presentation risk subject nested-reference unchanged"},{"id":"IETF RFC 3863","type":"specification","body":"IETF","designation":"RFC 3863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3863.txt","https://www.rfc-editor.org/rfc/rfc3863.pdf"],"folder":"IETF/RFC-3863","files":{"txt":{"path":"standards/IETF/RFC-3863/RFC-3863.txt","sha256":"b39126eb25230333c453e62fceb865754bc2f939641763e598f11e87e7c9997f"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies the Common Profile for Presence (CPP) Presence\n Information Data Format (PIDF) as a common presence data format for\n CPP-compliant Presence protocols, and also defines a new media type\n \"application/pidf+xml\" to represent the XML MIME entity for PIDF.\n\nTable of Content\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1.1. Terminology and Conventions. . . . . . . . . . . . . . . 3\n 2. Design Decisions . . . . . . . . . . . . . . . . . . . . . . . 3\n 2.1. Minimal Model. . . . . . . . . . . . . . . . . . . . . . 3\n 2.2. Added Features . . . . . . . . . . . . . . . . . . . . . 4\n 2.3. XML Encoding Decision. . . . . . . . . . . . . . . . . . 5\n 3. Overview of Presence Information Data Format . . . . . . . . . 5\n 3.1. The 'application/pidf+xml' Content Type. . . . . . . . . 5\n 3.2. Presence Information Contents. . . . . . . . . . . . . . 5\n 4. XML-enco","scope_keywords":["3863","key","pid","profile","profiles","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null}],"search_text":"IETF RFC 3863 This memo specifies the Common Profile for Presence (CPP) Presence\n Information Data Format (PIDF) as a common presence data format for\n CPP-compliant Presence protocols, and also defines a new media type\n \"application/pidf+xml\" to represent the XML MIME entity for PIDF.\n\nTable of Content\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2\n 1.1. Terminology and Conventions. . . . . . . . . . . . . . . 3\n 2. Design Decisions . . . . . . . . . . . . . . . . . . . . . . . 3\n 2.1. Minimal Model. . . . . . . . . . . . . . . . . . . . . . 3\n 2.2. Added Features . . . . . . . . . . . . . . . . . . . . . 4\n 2.3. XML Encoding Decision. . . . . . . . . . . . . . . . . . 5\n 3. Overview of Presence Information Data Format . . . . . . . . . 5\n 3.1. The 'application/pidf+xml' Content Type. . . . . . . . . 5\n 3.2. Presence Information Contents. . . . . . . . . . . . . . 5\n 4. XML-enco 3863 key pid profile profiles timestamp nested-reference unchanged"},{"id":"IETF RFC 3892","type":"specification","body":"IETF","designation":"RFC 3892","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3892.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3892.txt","https://www.rfc-editor.org/rfc/rfc3892.pdf"],"folder":"IETF/RFC-3892","files":{"txt":{"path":"standards/IETF/RFC-3892/RFC-3892.txt","sha256":"c704dd5949fb151788a218cef8f0021db49be73642f0f5e1eed27937841e3fde"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) REFER method provides a\n mechanism where one party (the referrer) gives a second party (the\n referee) an arbitrary URI to reference. If that URI is a SIP URI,\n the referee will send a SIP request, often an INVITE, to that URI\n (the refer target). This document extends the REFER method, allowing\n the referrer to provide information about the REFER request to the\n refer target using the referee as an intermediary. This information\n includes the identity of the referrer and the URI to which the\n referrer referred. The mechanism utilizes S/MIME to help protect\n this information from a malicious intermediary. This protection is\n optional, but a recipient may refuse to accept a request unless it is\n present.\n\nSparks Standards Track [Page 1]\n\f\nRFC 3892 The SIP Referred-By Mechanism September 2004","scope_keywords":["3892","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null}],"search_text":"IETF RFC 3892 The Session Initiation Protocol (SIP) REFER method provides a\n mechanism where one party (the referrer) gives a second party (the\n referee) an arbitrary URI to reference. If that URI is a SIP URI,\n the referee will send a SIP request, often an INVITE, to that URI\n (the refer target). This document extends the REFER method, allowing\n the referrer to provide information about the REFER request to the\n refer target using the referee as an intermediary. This information\n includes the identity of the referrer and the URI to which the\n referrer referred. The mechanism utilizes S/MIME to help protect\n this information from a malicious intermediary. This protection is\n optional, but a recipient may refuse to accept a request unless it is\n present.\n\nSparks Standards Track [Page 1]\n\f\nRFC 3892 The SIP Referred-By Mechanism September 2004 3892 key nested-reference unchanged"},{"id":"IETF RFC 3922","type":"specification","body":"IETF","designation":"RFC 3922","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3922.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3922.txt","https://www.rfc-editor.org/rfc/rfc3922.pdf"],"folder":"IETF/RFC-3922","files":{"txt":{"path":"standards/IETF/RFC-3922/RFC-3922.txt","sha256":"b00a93ca5109e273c110935c62271aa7462e85f266a1ee9f4d5622071f59add1"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a mapping between the Extensible Messaging and\n Presence Protocol (XMPP) and the Common Presence and Instant\n Messaging (CPIM) specifications.","scope_keywords":["3922","attribute","attributes","key","pid","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 3922 This memo describes a mapping between the Extensible Messaging and\n Presence Protocol (XMPP) and the Common Presence and Instant\n Messaging (CPIM) specifications. 3922 attribute attributes key pid profile nested-reference unchanged"},{"id":"IETF RFC 3987","type":"specification","body":"IETF","designation":"RFC 3987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3987.txt","https://www.rfc-editor.org/rfc/rfc3987.pdf"],"folder":"IETF/RFC-3987","files":{"txt":{"path":"standards/IETF/RFC-3987/RFC-3987.txt","sha256":"7cc9e3c4e61ea326130d29d959b723209fe3a6c75cdcfb5badbd315d96cd7878"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new protocol element, the Internationalized\n Resource Identifier (IRI), as a complement to the Uniform Resource\n Identifier (URI). An IRI is a sequence of characters from the\n Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to\n URIs is defined, which means that IRIs can be used instead of URIs,\n where appropriate, to identify resources.\n\n The approach of defining a new protocol element was chosen instead of\n extending or changing the definition of URIs. This was done in order\n to allow a clear distinction and to avoid incompatibilities with\n existing software. Guidelines are provided for the use and\n deployment of IRIs in various protocols, formats, and software\n components that currently deal with URIs.","scope_keywords":["3987","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4946","folder":"IETF/RFC-4946","source":"IETF/RFC-4946/RFC-4946.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 3987 This document defines a new protocol element, the Internationalized\n Resource Identifier (IRI), as a complement to the Uniform Resource\n Identifier (URI). An IRI is a sequence of characters from the\n Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to\n URIs is defined, which means that IRIs can be used instead of URIs,\n where appropriate, to identify resources.\n\n The approach of defining a new protocol element was chosen instead of\n extending or changing the definition of URIs. This was done in order\n to allow a clear distinction and to avoid incompatibilities with\n existing software. Guidelines are provided for the use and\n deployment of IRIs in various protocols, formats, and software\n components that currently deal with URIs. 3987 presentation nested-reference unchanged"},{"id":"IETF RFC 4040","type":"specification","body":"IETF","designation":"RFC 4040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4040.txt","https://www.rfc-editor.org/rfc/rfc4040.pdf"],"folder":"IETF/RFC-4040","files":{"txt":{"path":"standards/IETF/RFC-4040/RFC-4040.txt","sha256":"d1465e5b7bd7523474c91db8e9f748edbff2b39af56d84c52df2f99fc2571dde"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to carry 64 kbit/s channel data\n transparently in RTP packets, using a pseudo-codec called\n \"Clearmode\". It also serves as registration for a related MIME type\n called \"audio/clearmode\".\n\n \"Clearmode\" is a basic feature of VoIP Media Gateways.","scope_keywords":["4040","key","path","profile","registered","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null}],"search_text":"IETF RFC 4040 This document describes how to carry 64 kbit/s channel data\n transparently in RTP packets, using a pseudo-codec called\n \"Clearmode\". It also serves as registration for a related MIME type\n called \"audio/clearmode\".\n\n \"Clearmode\" is a basic feature of VoIP Media Gateways. 4040 key path profile registered subject timestamp nested-reference unchanged"},{"id":"IETF RFC 4073","type":"specification","body":"IETF","designation":"RFC 4073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4073.txt","https://www.rfc-editor.org/rfc/rfc4073.pdf"],"folder":"IETF/RFC-4073","files":{"txt":{"path":"standards/IETF/RFC-4073/RFC-4073.txt","sha256":"c47e7ce1521a61cc0bcb3811f106a82574130540b975410ee8d762a530fc8a6b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a convention for using the Cryptographic\n Message Syntax (CMS) to protect a content collection. If desired,\n attributes can be associated with the content.\n\n1. Introduction\n\n This document describes a convention for using the Cryptographic\n Message Syntax (CMS) [CMS] to protect a content collection. The\n content-collection content type is used to transfer one or more\n contents, each identified by a content type. If desired, the\n content-with-attributes content type can be used to associate\n arbitrary attributes with the content.\n\n The convention described in this document is not needed when CMS is\n used with MIME [MSG]. MIME multipart [MIME] provides a\n straightforward and widely deployed mechanism for carrying more than\n one content item, each associated with a MIME type.\n\n However, CMS is not always used with MIME. Sometimes CMS is used in\n an exclusively ASN.1 ","scope_keywords":["4073","attribute","attributes","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null}],"search_text":"IETF RFC 4073 This document describes a convention for using the Cryptographic\n Message Syntax (CMS) to protect a content collection. If desired,\n attributes can be associated with the content.\n\n1. Introduction\n\n This document describes a convention for using the Cryptographic\n Message Syntax (CMS) [CMS] to protect a content collection. The\n content-collection content type is used to transfer one or more\n contents, each identified by a content type. If desired, the\n content-with-attributes content type can be used to associate\n arbitrary attributes with the content.\n\n The convention described in this document is not needed when CMS is\n used with MIME [MSG]. MIME multipart [MIME] provides a\n straightforward and widely deployed mechanism for carrying more than\n one content item, each associated with a MIME type.\n\n However, CMS is not always used with MIME. Sometimes CMS is used in\n an exclusively ASN.1  4073 attribute attributes key signature signatures nested-reference unchanged"},{"id":"IETF RFC 4102","type":"specification","body":"IETF","designation":"RFC 4102","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4102.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4102.txt","https://www.rfc-editor.org/rfc/rfc4102.pdf"],"folder":"IETF/RFC-4102","files":{"txt":{"path":"standards/IETF/RFC-4102/RFC-4102.txt","sha256":"a61c59ec399354f3391876c813d4985afbd26ff7fcaeebc9f3bad01e3a1ea154"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Jones\nRequest for Comments: 4102 Cisco Systems, Inc.\nCategory: Standards Track June 2005\n\n Registration of the text/red MIME Sub-Type\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document defines the text/red MIME sub-type. \"Red\" is short for\n redundant. The actual RTP packetization for this MIME type is\n specified in RFC 2198.\n\n1. Introduction\n\n Text is an important component of any multimedia communication\n system. Like audio, the transport of text can benefit from the u","scope_keywords":["4102","attribute","attributes","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null}],"search_text":"IETF RFC 4102 Network Working Group P. Jones\nRequest for Comments: 4102 Cisco Systems, Inc.\nCategory: Standards Track June 2005\n\n Registration of the text/red MIME Sub-Type\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document defines the text/red MIME sub-type. \"Red\" is short for\n redundant. The actual RTP packetization for this MIME type is\n specified in RFC 2198.\n\n1. Introduction\n\n Text is an important component of any multimedia communication\n system. Like audio, the transport of text can benefit from the u 4102 attribute attributes key registered nested-reference unchanged"},{"id":"IETF RFC 4155","type":"specification","body":"IETF","designation":"RFC 4155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4155.txt","https://www.rfc-editor.org/rfc/rfc4155.pdf"],"folder":"IETF/RFC-4155","files":{"txt":{"path":"standards/IETF/RFC-4155/RFC-4155.txt","sha256":"41dcdacf425e68ad861e0e2a123bbad198ff281798c23f8c54fe426c5f77a06f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Hall\nRequest for Comments: 4155 September 2005\nCategory: Informational\n\n The application/mbox Media Type\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This memo requests that the application/mbox media type be authorized\n for allocation by the IESG, according to the terms specified in RFC\n 2048. This memo also defines a default format for the mbox database,\n which must be supported by all conformant implementations.\n\n1. Background and Overview\n\n UNIX-like operating systems have historically made widespread use of\n \"mbox\" database files for a variety of local email purposes. In the\n common case, mbox files store linear sequences of one or more\n electronic mail ","scope_keywords":["4155","archiving","attribute","attributes","http","key","management","path","subject","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 4155 Network Working Group E. Hall\nRequest for Comments: 4155 September 2005\nCategory: Informational\n\n The application/mbox Media Type\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This memo requests that the application/mbox media type be authorized\n for allocation by the IESG, according to the terms specified in RFC\n 2048. This memo also defines a default format for the mbox database,\n which must be supported by all conformant implementations.\n\n1. Background and Overview\n\n UNIX-like operating systems have historically made widespread use of\n \"mbox\" database files for a variety of local email purposes. In the\n common case, mbox files store linear sequences of one or more\n electronic mail  4155 archiving attribute attributes http key management path subject timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 4169","type":"specification","body":"IETF","designation":"RFC 4169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4169.txt","https://www.rfc-editor.org/rfc/rfc4169.pdf"],"folder":"IETF/RFC-4169","files":{"txt":{"path":"standards/IETF/RFC-4169/RFC-4169.txt","sha256":"953c53fb525682f6b149491e876f1759db86c6be53acee7c7f24ef15d1a9a679"}},"tags":["nested-reference","unchanged"],"summary":"HTTP Digest, as specified in RFC 2617, is known to be vulnerable to\n man-in-the-middle attacks if the client fails to authenticate the\n server in TLS, or if the same passwords are used for authentication\n in some other context without TLS. This is a general problem that\n exists not just with HTTP Digest, but also with other IETF protocols\n that use tunneled authentication. This document specifies version 2\n of the HTTP Digest AKA algorithm (RFC 3310). This algorithm can be\n implemented in a way that it is resistant to the man-in-the-middle\n attack.\n\nTorvinen Informational [Page 1]\n\f\nRFC 4169 HTTP Digest AKAv2 November 2005","scope_keywords":["4169","algorithm","algorithms","authentication","certificate","certificates","credential","credentials","http","key","keys","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4169 HTTP Digest, as specified in RFC 2617, is known to be vulnerable to\n man-in-the-middle attacks if the client fails to authenticate the\n server in TLS, or if the same passwords are used for authentication\n in some other context without TLS. This is a general problem that\n exists not just with HTTP Digest, but also with other IETF protocols\n that use tunneled authentication. This document specifies version 2\n of the HTTP Digest AKA algorithm (RFC 3310). This algorithm can be\n implemented in a way that it is resistant to the man-in-the-middle\n attack.\n\nTorvinen Informational [Page 1]\n\f\nRFC 4169 HTTP Digest AKAv2 November 2005 4169 algorithm algorithms authentication certificate certificates credential credentials http key keys registered tls nested-reference unchanged"},{"id":"IETF RFC 4227","type":"specification","body":"IETF","designation":"RFC 4227","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4227.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4227.txt","https://www.rfc-editor.org/rfc/rfc4227.pdf"],"folder":"IETF/RFC-4227","files":{"txt":{"path":"standards/IETF/RFC-4227/RFC-4227.txt","sha256":"e9b07f037731d49b7a8739c97679b9561c959cfbcfbcc15c82d3fdb31debc770"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies a Simple Object Access Protocol (SOAP) binding to\n the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding\n describes how SOAP messages are transmitted in the network.\n\n The SOAP is an XML-based (eXtensible Markup Language) messaging\n protocol used to implement a wide variety of distributed messaging\n models. It defines a message format and describes a variety of\n message patterns, including, but not limited to, Remote Procedure\n Calling (RPC), asynchronous event notification, unacknowledged\n messages, and forwarding via SOAP intermediaries.\n\nO'Tuathail & Rose Standards Track [Page 1]\n\f\nRFC 4227 Using SOAP in BEEP January 2006","scope_keywords":["4227","attribute","http","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 4227 This memo specifies a Simple Object Access Protocol (SOAP) binding to\n the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding\n describes how SOAP messages are transmitted in the network.\n\n The SOAP is an XML-based (eXtensible Markup Language) messaging\n protocol used to implement a wide variety of distributed messaging\n models. It defines a message format and describes a variety of\n message patterns, including, but not limited to, Remote Procedure\n Calling (RPC), asynchronous event notification, unacknowledged\n messages, and forwarding via SOAP intermediaries.\n\nO'Tuathail & Rose Standards Track [Page 1]\n\f\nRFC 4227 Using SOAP in BEEP January 2006 4227 attribute http identification profile nested-reference unchanged"},{"id":"IETF RFC 4240","type":"specification","body":"IETF","designation":"RFC 4240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4240.txt","https://www.rfc-editor.org/rfc/rfc4240.pdf"],"folder":"IETF/RFC-4240","files":{"txt":{"path":"standards/IETF/RFC-4240/RFC-4240.txt","sha256":"c31eba1454507f7410f010597fcb9ec3244b0d794fea3e8ab91885a22e38b532"}},"tags":["nested-reference","unchanged"],"summary":"In SIP-based networks, there is a need to provide basic network media\n services. Such services include network announcements, user\n interaction, and conferencing services. These services are basic\n building blocks, from which one can construct interesting\n applications. In order to have interoperability between servers\n offering these building blocks (also known as Media Servers) and\n application developers, one needs to be able to locate and invoke\n such services in a well defined manner.\n\n This document describes a mechanism for providing an interoperable\n interface between Application Servers, which provide application\n services to SIP-based networks, and Media Servers, which provide the\n basic media processing building blocks.\n\nBurger, et al. Informational [Page 1]\n\f\nRFC 4240 SIP Media Services December 2005","scope_keywords":["4240","authentication","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 4240 In SIP-based networks, there is a need to provide basic network media\n services. Such services include network announcements, user\n interaction, and conferencing services. These services are basic\n building blocks, from which one can construct interesting\n applications. In order to have interoperability between servers\n offering these building blocks (also known as Media Servers) and\n application developers, one needs to be able to locate and invoke\n such services in a well defined manner.\n\n This document describes a mechanism for providing an interoperable\n interface between Application Servers, which provide application\n services to SIP-based networks, and Media Servers, which provide the\n basic media processing building blocks.\n\nBurger, et al. Informational [Page 1]\n\f\nRFC 4240 SIP Media Services December 2005 4240 authentication key policy nested-reference unchanged"},{"id":"IETF RFC 4469","type":"specification","body":"IETF","designation":"RFC 4469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4469.txt","https://www.rfc-editor.org/rfc/rfc4469.pdf"],"folder":"IETF/RFC-4469","files":{"txt":{"path":"standards/IETF/RFC-4469/RFC-4469.txt","sha256":"e9e64f2e344e60bc091b1760c4aa01bac0c481c4aaf6c9ec6d888768a22953d2"}},"tags":["nested-reference","unchanged"],"summary":"The CATENATE extension to the Internet Message Access Protocol (IMAP)\n extends the APPEND command to allow clients to create messages on the\n IMAP server that may contain a combination of new data along with\n parts of (or entire) messages already on the server. Using this\n extension, the client can catenate parts of an already existing\n message onto a new message without having to first download the data\n and then upload it back to the server.\n\nResnick Standards Track [Page 1]\n\f\nRFC 4469 IMAP CATENATE Extension April 2006\n\n1. Introduction\n\n The CATENATE extension to the Internet Message Access Protocol (IMAP)\n [1] allows the client to create a message on the server that can\n include the text of messages (or parts of messages) that already\n exist on the server without having to FETCH them and APPEND them back\n to the server. The CATENATE extension extends the APPEND command so\n that, inst","scope_keywords":["4469"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null}],"search_text":"IETF RFC 4469 The CATENATE extension to the Internet Message Access Protocol (IMAP)\n extends the APPEND command to allow clients to create messages on the\n IMAP server that may contain a combination of new data along with\n parts of (or entire) messages already on the server. Using this\n extension, the client can catenate parts of an already existing\n message onto a new message without having to first download the data\n and then upload it back to the server.\n\nResnick Standards Track [Page 1]\n\f\nRFC 4469 IMAP CATENATE Extension April 2006\n\n1. Introduction\n\n The CATENATE extension to the Internet Message Access Protocol (IMAP)\n [1] allows the client to create a message on the server that can\n include the text of messages (or parts of messages) that already\n exist on the server without having to FETCH them and APPEND them back\n to the server. The CATENATE extension extends the APPEND command so\n that, inst 4469 nested-reference unchanged"},{"id":"IETF RFC 4743","type":"specification","body":"IETF","designation":"RFC 4743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4743.txt","https://www.rfc-editor.org/rfc/rfc4743.pdf"],"folder":"IETF/RFC-4743","files":{"txt":{"path":"standards/IETF/RFC-4743/RFC-4743.txt","sha256":"9b765b9f7a486b2015146df77f3bd2f69b273db8039cf5f0007945abaf7f327a"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) is applicable to a wide\n range of devices in a variety of environments. Web Services is one\n such environment and is presently characterized by the use of the\n Simple Object Access Protocol (SOAP). NETCONF finds many benefits in\n this environment: from the reuse of existing standards, to ease of\n software development, to integration with deployed systems. Herein,\n we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible\n Protocol (BEEP) bindings for NETCONF.\n\nGoddard Standards Track [Page 1]\n\f\nRFC 4743 NETCONF over SOAP December 2006","scope_keywords":["4743","authentication","http","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4743 The Network Configuration Protocol (NETCONF) is applicable to a wide\n range of devices in a variety of environments. Web Services is one\n such environment and is presently characterized by the use of the\n Simple Object Access Protocol (SOAP). NETCONF finds many benefits in\n this environment: from the reuse of existing standards, to ease of\n software development, to integration with deployed systems. Herein,\n we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible\n Protocol (BEEP) bindings for NETCONF.\n\nGoddard Standards Track [Page 1]\n\f\nRFC 4743 NETCONF over SOAP December 2006 4743 authentication http key management trust nested-reference unchanged"},{"id":"IETF RFC 4790","type":"specification","body":"IETF","designation":"RFC 4790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4790.txt","https://www.rfc-editor.org/rfc/rfc4790.pdf"],"folder":"IETF/RFC-4790","files":{"txt":{"path":"standards/IETF/RFC-4790/RFC-4790.txt","sha256":"c51f2bed0b2165621d5085786dd0c13fdcd23c85e3af52f6648a9d97ae0929b9"}},"tags":["nested-reference","unchanged"],"summary":"Many Internet application protocols include string-based lookup,\n searching, or sorting operations. However, the problem space for\n searching and sorting international strings is large, not fully\n explored, and is outside the area of expertise for the Internet\n Engineering Task Force (IETF). Rather than attempt to solve such a\n large problem, this specification creates an abstraction framework so\n that application protocols can precisely identify a comparison\n function, and the repertoire of comparison functions can be extended\n in the future.\n\nNewman, et al. Standards Track [Page 1]\n\f\nRFC 4790 Collation Registry March 2007","scope_keywords":["4790","algorithm","attribute","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 5051","folder":"IETF/RFC-5051","source":"IETF/RFC-5051/RFC-5051.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5235","folder":"IETF/RFC-5235","source":"IETF/RFC-5235/RFC-5235.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 4790 Many Internet application protocols include string-based lookup,\n searching, or sorting operations. However, the problem space for\n searching and sorting international strings is large, not fully\n explored, and is outside the area of expertise for the Internet\n Engineering Task Force (IETF). Rather than attempt to solve such a\n large problem, this specification creates an abstraction framework so\n that application protocols can precisely identify a comparison\n function, and the repertoire of comparison functions can be extended\n in the future.\n\nNewman, et al. Standards Track [Page 1]\n\f\nRFC 4790 Collation Registry March 2007 4790 algorithm attribute key keys trust nested-reference unchanged"},{"id":"IETF RFC 4855","type":"specification","body":"IETF","designation":"RFC 4855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4855.txt","https://www.rfc-editor.org/rfc/rfc4855.pdf"],"folder":"IETF/RFC-4855","files":{"txt":{"path":"standards/IETF/RFC-4855/RFC-4855.txt","sha256":"c8e1bf053cf93dc60027be4d851dee8b60375a1953c7c1323d8e3c33491b0e11"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the procedure to register RTP payload formats\n as audio, video, or other media subtype names. This is useful in a\n text-based format description or control protocol to identify the\n type of an RTP transmission.","scope_keywords":["4855","http","key","registered","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 4855 This document specifies the procedure to register RTP payload formats\n as audio, video, or other media subtype names. This is useful in a\n text-based format description or control protocol to identify the\n type of an RTP transmission. 4855 http key registered timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4975","type":"specification","body":"IETF","designation":"RFC 4975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4975.txt","https://www.rfc-editor.org/rfc/rfc4975.pdf"],"folder":"IETF/RFC-4975","files":{"txt":{"path":"standards/IETF/RFC-4975/RFC-4975.txt","sha256":"d54fc710b770bca55935b99af3adcb854e79d1dfca40ffef774216a489b20e3b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Message Session Relay Protocol, a\n protocol for transmitting a series of related instant messages in the\n context of a session. Message sessions are treated like any other\n media stream when set up via a rendezvous or session creation\n protocol such as the Session Initiation Protocol.\n\nCampbell, et al. Standards Track [Page 1]\n\f\nRFC 4975 MSRP September 2007","scope_keywords":["4975","attribute","attributes","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4975 This document describes the Message Session Relay Protocol, a\n protocol for transmitting a series of related instant messages in the\n context of a session. Message sessions are treated like any other\n media stream when set up via a rendezvous or session creation\n protocol such as the Session Initiation Protocol.\n\nCampbell, et al. Standards Track [Page 1]\n\f\nRFC 4975 MSRP September 2007 4975 attribute attributes key path tls nested-reference unchanged"},{"id":"IETF RFC 4976","type":"specification","body":"IETF","designation":"RFC 4976","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4976.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4976.txt","https://www.rfc-editor.org/rfc/rfc4976.pdf"],"folder":"IETF/RFC-4976","files":{"txt":{"path":"standards/IETF/RFC-4976/RFC-4976.txt","sha256":"fcba9db59f586b0ac77ee507ce3f795fe6ab61619e3f928bc5b61168e8195047"}},"tags":["nested-reference","unchanged"],"summary":"Two separate models for conveying instant messages have been defined.\n Page-mode messages stand alone and are not part of a Session\n Initiation Protocol (SIP) session, whereas session-mode messages are\n set up as part of a session using SIP. The Message Session Relay\n Protocol (MSRP) is a protocol for near real-time, peer-to-peer\n exchanges of binary content without intermediaries, which is designed\n to be signaled using a separate rendezvous protocol such as SIP.\n This document introduces the notion of message relay intermediaries\n to MSRP and describes the extensions necessary to use them.\n\nJennings, et al. Standards Track [Page 1]\n\f\nRFC 4976 MSRP Relays September 2007","scope_keywords":["4976","authentication","authorization","credential","credentials","delivery","http","key","path","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4976 Two separate models for conveying instant messages have been defined.\n Page-mode messages stand alone and are not part of a Session\n Initiation Protocol (SIP) session, whereas session-mode messages are\n set up as part of a session using SIP. The Message Session Relay\n Protocol (MSRP) is a protocol for near real-time, peer-to-peer\n exchanges of binary content without intermediaries, which is designed\n to be signaled using a separate rendezvous protocol such as SIP.\n This document introduces the notion of message relay intermediaries\n to MSRP and describes the extensions necessary to use them.\n\nJennings, et al. Standards Track [Page 1]\n\f\nRFC 4976 MSRP Relays September 2007 4976 authentication authorization credential credentials delivery http key path policy tls nested-reference unchanged"},{"id":"IETF RFC 5092","type":"specification","body":"IETF","designation":"RFC 5092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5092.txt","https://www.rfc-editor.org/rfc/rfc5092.pdf"],"folder":"IETF/RFC-5092","files":{"txt":{"path":"standards/IETF/RFC-5092/RFC-5092.txt","sha256":"2f0ba28122359f90599c2e9740d5aff33bb58f795fe0754e121494b299369f12"}},"tags":["nested-reference","unchanged"],"summary":"IMAP (RFC 3501) is a rich protocol for accessing remote message\n stores. It provides an ideal mechanism for accessing public mailing\n list archives as well as private and shared message stores. This\n document defines a URL scheme for referencing objects on an IMAP\n server.\n\n This document obsoletes RFC 2192. It also updates RFC 4467.\n\nMelnikov & Newman Standards Track [Page 1]\n\f\nRFC 5092 IMAP URL Scheme November 2007","scope_keywords":["5092","authentication","authorization","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5092 IMAP (RFC 3501) is a rich protocol for accessing remote message\n stores. It provides an ideal mechanism for accessing public mailing\n list archives as well as private and shared message stores. This\n document defines a URL scheme for referencing objects on an IMAP\n server.\n\n This document obsoletes RFC 2192. It also updates RFC 4467.\n\nMelnikov & Newman Standards Track [Page 1]\n\f\nRFC 5092 IMAP URL Scheme November 2007 5092 authentication authorization key path nested-reference unchanged"},{"id":"IETF RFC 5173","type":"specification","body":"IETF","designation":"RFC 5173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5173.txt","https://www.rfc-editor.org/rfc/rfc5173.pdf"],"folder":"IETF/RFC-5173","files":{"txt":{"path":"standards/IETF/RFC-5173/RFC-5173.txt","sha256":"6127830c657e4721c2bc6f06b027e93424f7a73402e354aab74841885ae450b8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new command for the \"Sieve\" email filtering\n language that tests for the occurrence of one or more strings in the\n body of an email message.\n\nDegener & Guenther Standards Track [Page 1]\n\f\nRFC 5173 Sieve Email Filtering: Body Extension April 2008\n\n1. Introduction\n\n The \"body\" test checks for the occurrence of one or more strings in\n the body of an email message. Such a test was initially discussed\n for the [SIEVE] base document, but was subsequently removed because\n it was thought to be too costly to implement.\n\n Nevertheless, several server vendors have implemented some form of\n the \"body\" test.\n\n This document reintroduces the \"body\" test as an extension, and\n specifies its syntax and semantics.\n\n2. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" ","scope_keywords":["5173","crl","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null}],"search_text":"IETF RFC 5173 This document defines a new command for the \"Sieve\" email filtering\n language that tests for the occurrence of one or more strings in the\n body of an email message.\n\nDegener & Guenther Standards Track [Page 1]\n\f\nRFC 5173 Sieve Email Filtering: Body Extension April 2008\n\n1. Introduction\n\n The \"body\" test checks for the occurrence of one or more strings in\n the body of an email message. Such a test was initially discussed\n for the [SIEVE] base document, but was subsequently removed because\n it was thought to be too costly to implement.\n\n Nevertheless, several server vendors have implemented some form of\n the \"body\" test.\n\n This document reintroduces the \"body\" test as an extension, and\n specifies its syntax and semantics.\n\n2. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\"  5173 crl key subject nested-reference unchanged"},{"id":"IETF RFC 5228","type":"specification","body":"IETF","designation":"RFC 5228","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5228.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5228.txt","https://www.rfc-editor.org/rfc/rfc5228.pdf"],"folder":"IETF/RFC-5228","files":{"txt":{"path":"standards/IETF/RFC-5228/RFC-5228.txt","sha256":"ffee094c9c6df0da69971b1fb058715d31e484f8b3410f4cb5539a075e1a1dc6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a language for filtering email messages at\n time of final delivery. It is designed to be implementable on either\n a mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Message Access Protocol (IMAP) servers, as the base language\n has no variables, loops, or ability to shell out to external\n programs.\n\nGuenther & Showalter Standards Track [Page 1]\n\f\nRFC 5228 Sieve: An Email Filtering Language January 2008","scope_keywords":["5228","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5183","folder":"IETF/RFC-5183","source":"IETF/RFC-5183/RFC-5183.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5232","folder":"IETF/RFC-5232","source":"IETF/RFC-5232/RFC-5232.txt","version":null},{"body":"IETF","designation":"RFC 5233","folder":"IETF/RFC-5233","source":"IETF/RFC-5233/RFC-5233.txt","version":null},{"body":"IETF","designation":"RFC 5235","folder":"IETF/RFC-5235","source":"IETF/RFC-5235/RFC-5235.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null}],"search_text":"IETF RFC 5228 This document describes a language for filtering email messages at\n time of final delivery. It is designed to be implementable on either\n a mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Message Access Protocol (IMAP) servers, as the base language\n has no variables, loops, or ability to shell out to external\n programs.\n\nGuenther & Showalter Standards Track [Page 1]\n\f\nRFC 5228 Sieve: An Email Filtering Language January 2008 5228 delivery nested-reference unchanged"},{"id":"IETF RFC 5230","type":"specification","body":"IETF","designation":"RFC 5230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5230.txt","https://www.rfc-editor.org/rfc/rfc5230.pdf"],"folder":"IETF/RFC-5230","files":{"txt":{"path":"standards/IETF/RFC-5230/RFC-5230.txt","sha256":"854f0445eb2eb1094902f8f8d595fb45a35bd3834af0f7b05ef84227122e7f96"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the Sieve email filtering\n language for an autoresponder similar to that of the Unix \"vacation\"\n command for replying to messages. Various safety features are\n included to prevent problems such as message loops.\n\nShowalter & Freed Standards Track [Page 1]\n\f\nRFC 5230 Sieve: Vacation Extension January 2008","scope_keywords":["5230","delivery","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5442","folder":"IETF/RFC-5442","source":"IETF/RFC-5442/RFC-5442.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5230 This document describes an extension to the Sieve email filtering\n language for an autoresponder similar to that of the Unix \"vacation\"\n command for replying to messages. Various safety features are\n included to prevent problems such as message loops.\n\nShowalter & Freed Standards Track [Page 1]\n\f\nRFC 5230 Sieve: Vacation Extension January 2008 5230 delivery key path subject nested-reference unchanged"},{"id":"IETF RFC 5255","type":"specification","body":"IETF","designation":"RFC 5255","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5255.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5255.txt","https://www.rfc-editor.org/rfc/rfc5255.pdf"],"folder":"IETF/RFC-5255","files":{"txt":{"path":"standards/IETF/RFC-5255/RFC-5255.txt","sha256":"5d5f5330b127a3d4c560666f4d7a49b647f6ce05a355b1d72e212e9f70111764"}},"tags":["nested-reference","unchanged"],"summary":"Internet Message Access Protocol (IMAP) version 4rev1 has basic\n support for non-ASCII characters in mailbox names and search\n substrings. It also supports non-ASCII message headers and content\n encoded as specified by Multipurpose Internet Mail Extensions (MIME).\n This specification defines a collection of IMAP extensions that\n improve international support including language negotiation for\n international error text, translations for namespace prefixes, and\n comparator negotiation for search, sort, and thread.\n\nNewman, et al. Standards Track [Page 1]\n\f\nRFC 5255 IMAP Internationalization June 2008","scope_keywords":["5255","authentication","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5255 Internet Message Access Protocol (IMAP) version 4rev1 has basic\n support for non-ASCII characters in mailbox names and search\n substrings. It also supports non-ASCII message headers and content\n encoded as specified by Multipurpose Internet Mail Extensions (MIME).\n This specification defines a collection of IMAP extensions that\n improve international support including language negotiation for\n international error text, translations for namespace prefixes, and\n comparator negotiation for search, sort, and thread.\n\nNewman, et al. Standards Track [Page 1]\n\f\nRFC 5255 IMAP Internationalization June 2008 5255 authentication key tls nested-reference unchanged"},{"id":"IETF RFC 5337","type":"specification","body":"IETF","designation":"RFC 5337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5337.txt","https://www.rfc-editor.org/rfc/rfc5337.pdf"],"folder":"IETF/RFC-5337","files":{"txt":{"path":"standards/IETF/RFC-5337/RFC-5337.txt","sha256":"a4c9a94826036b7ebac5a2de680f939ab44354d6fb46b173acc284a9c004ec6a"}},"tags":["nested-reference","unchanged"],"summary":"Delivery status notifications (DSNs) are critical to the correct\n operation of an email system. However, the existing Draft Standards\n (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text\n in the machine-readable portions of the protocol. This specification\n adds a new address type for international email addresses so an\n original recipient address with non-US-ASCII characters can be\n correctly preserved even after downgrading. This also provides\n updated content return media types for delivery status notifications\n and message disposition notifications to support use of the new\n address type.\n\n This document experimentally extends RFC 3461, RFC 3464, and RFC\n 3798.\n\nNewman & Melnikov Experimental [Page 1]\n\f\nRFC 5337 Internationalized DSN and MDNs September 2008","scope_keywords":["5337","delivery","key","presentation","preservation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null}],"search_text":"IETF RFC 5337 Delivery status notifications (DSNs) are critical to the correct\n operation of an email system. However, the existing Draft Standards\n (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text\n in the machine-readable portions of the protocol. This specification\n adds a new address type for international email addresses so an\n original recipient address with non-US-ASCII characters can be\n correctly preserved even after downgrading. This also provides\n updated content return media types for delivery status notifications\n and message disposition notifications to support use of the new\n address type.\n\n This document experimentally extends RFC 3461, RFC 3464, and RFC\n 3798.\n\nNewman & Melnikov Experimental [Page 1]\n\f\nRFC 5337 Internationalized DSN and MDNs September 2008 5337 delivery key presentation preservation tls nested-reference unchanged"},{"id":"IETF RFC 5408","type":"specification","body":"IETF","designation":"RFC 5408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5408.txt","https://www.rfc-editor.org/rfc/rfc5408.pdf"],"folder":"IETF/RFC-5408","files":{"txt":{"path":"standards/IETF/RFC-5408/RFC-5408.txt","sha256":"753b7f79c2d5ce869a981c9650284111efb70742be9acbeb9680fd2d7c269862"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the security architecture required to\n implement identity-based encryption, a public-key encryption\n technology that uses a user's identity as a public key. It also\n defines data structures that can be used to implement the technology.\n\nAppenzeller, et al. Informational [Page 1]\n\f\nRFC 5408 IBE Architecture January 2009","scope_keywords":["5408","authentication","encryption","http","key","keys","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null}],"search_text":"IETF RFC 5408 This document describes the security architecture required to\n implement identity-based encryption, a public-key encryption\n technology that uses a user's identity as a public key. It also\n defines data structures that can be used to implement the technology.\n\nAppenzeller, et al. Informational [Page 1]\n\f\nRFC 5408 IBE Architecture January 2009 5408 authentication encryption http key keys license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5547","type":"specification","body":"IETF","designation":"RFC 5547","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5547.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5547.txt","https://www.rfc-editor.org/rfc/rfc5547.pdf"],"folder":"IETF/RFC-5547","files":{"txt":{"path":"standards/IETF/RFC-5547/RFC-5547.txt","sha256":"1cd12eb69b9beeb6bef2ca6c41890d2dc78e2b5d95ad264e7161b893f6f50a4a"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a mechanism to negotiate the transfer of one\n or more files between two endpoints by using the Session Description\n Protocol (SDP) offer/answer model specified in RFC 3264. SDP is\n extended to describe the attributes of the files to be transferred.\n The offerer can describe either the files it wants to send or the\n files it would like to receive. The answerer can either accept or\n reject the offer separately for each individual file. The transfer\n of one or more files is initiated after a successful negotiation.\n The Message Session Relay Protocol (MSRP) is defined as the default\n mechanism to actually carry the files between the endpoints. The\n conventions on how to use MSRP for file transfer are also provided in\n this document.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 5547 SDP Offer/Answer for File Transfer May 2009","scope_keywords":["5547","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 5547 This document provides a mechanism to negotiate the transfer of one\n or more files between two endpoints by using the Session Description\n Protocol (SDP) offer/answer model specified in RFC 3264. SDP is\n extended to describe the attributes of the files to be transferred.\n The offerer can describe either the files it wants to send or the\n files it would like to receive. The answerer can either accept or\n reject the offer separately for each individual file. The transfer\n of one or more files is initiated after a successful negotiation.\n The Message Session Relay Protocol (MSRP) is defined as the default\n mechanism to actually carry the files between the endpoints. The\n conventions on how to use MSRP for file transfer are also provided in\n this document.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 5547 SDP Offer/Answer for File Transfer May 2009 5547 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5621","type":"specification","body":"IETF","designation":"RFC 5621","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5621.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5621.txt","https://www.rfc-editor.org/rfc/rfc5621.pdf"],"folder":"IETF/RFC-5621","files":{"txt":{"path":"standards/IETF/RFC-5621/RFC-5621.txt","sha256":"bdf786873b6685b98d672bcd2eb0bc95d7b6968db9f1bb10c723e3099ad5eaaf"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how message bodies are handled in SIP.\n Additionally, this document specifies SIP user agent support for MIME\n (Multipurpose Internet Mail Extensions) in message bodies.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these ","scope_keywords":["5621","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5621 This document specifies how message bodies are handled in SIP.\n Additionally, this document specifies SIP user agent support for MIME\n (Multipurpose Internet Mail Extensions) in message bodies.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these  5621 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5825","type":"specification","body":"IETF","designation":"RFC 5825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5825.txt","https://www.rfc-editor.org/rfc/rfc5825.pdf"],"folder":"IETF/RFC-5825","files":{"txt":{"path":"standards/IETF/RFC-5825/RFC-5825.txt","sha256":"305f9b81a4cbd709281c05ba02d5f0cd1ac4e43f0a0bdd5dd5155f56d1b94146"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for displaying downgraded messages\n that originally contained internationalized email addresses or\n internationalized header fields.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at","scope_keywords":["5825","delivery","http","key","license","path","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 5825 This document describes a method for displaying downgraded messages\n that originally contained internationalized email addresses or\n internationalized header fields.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at 5825 delivery http key license path preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 5849","type":"specification","body":"IETF","designation":"RFC 5849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5849.txt","https://www.rfc-editor.org/rfc/rfc5849.pdf"],"folder":"IETF/RFC-5849","files":{"txt":{"path":"standards/IETF/RFC-5849/RFC-5849.txt","sha256":"89e6fca18e4028c8b684e9b53a113acfdd0e5267a6c52f29e295a88eeea31441"}},"tags":["nested-reference","unchanged"],"summary":"OAuth provides a method for clients to access server resources on\n behalf of a resource owner (such as a different client or an end-\n user). It also provides a process for end-users to authorize third-\n party access to their server resources without sharing their\n credentials (typically, a username and password pair), using user-\n agent redirections.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this","scope_keywords":["5849","authentication","authorization","credential","credentials","http","license","signature","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null}],"search_text":"IETF RFC 5849 OAuth provides a method for clients to access server resources on\n behalf of a resource owner (such as a different client or an end-\n user). It also provides a process for end-users to authorize third-\n party access to their server resources without sharing their\n credentials (typically, a username and password pair), using user-\n agent redirections.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this 5849 authentication authorization credential credentials http license signature subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5987","type":"specification","body":"IETF","designation":"RFC 5987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5987.txt","https://www.rfc-editor.org/rfc/rfc5987.pdf"],"folder":"IETF/RFC-5987","files":{"txt":{"path":"standards/IETF/RFC-5987/RFC-5987.txt","sha256":"2353eac192b65aa1c37a25bb38b364989355334034a60246f7369b817ab5aded"}},"tags":["nested-reference","unchanged"],"summary":"By default, message header field parameters in Hypertext Transfer\n Protocol (HTTP) messages cannot carry characters outside the ISO-\n 8859-1 character set. RFC 2231 defines an encoding mechanism for use\n in Multipurpose Internet Mail Extensions (MIME) headers. This\n document specifies an encoding suitable for use in HTTP header fields\n that is compatible with a profile of the encoding defined in RFC\n 2231.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f","scope_keywords":["5987","attribute","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null}],"search_text":"IETF RFC 5987 By default, message header field parameters in Hypertext Transfer\n Protocol (HTTP) messages cannot carry characters outside the ISO-\n 8859-1 character set. RFC 2231 defines an encoding mechanism for use\n in Multipurpose Internet Mail Extensions (MIME) headers. This\n document specifies an encoding suitable for use in HTTP header fields\n that is compatible with a profile of the encoding defined in RFC\n 2231.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f 5987 attribute http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6068","type":"specification","body":"IETF","designation":"RFC 6068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6068.txt","https://www.rfc-editor.org/rfc/rfc6068.pdf"],"folder":"IETF/RFC-6068","files":{"txt":{"path":"standards/IETF/RFC-6068/RFC-6068.txt","sha256":"a450492a89d30689c0a73e26e1a1d7bccf761405b23c15567f0cf9db575984af"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format of Uniform Resource Identifiers\n (URIs) to identify resources that are reached using Internet mail.\n It adds better internationalization and compatibility with\n Internationalized Resource Identifiers (IRIs; RFC 3987) to the\n previous syntax of 'mailto' URIs (RFC 2368).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6068.\n\nDuerst, et al. Standards Track [","scope_keywords":["6068","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 6068 This document defines the format of Uniform Resource Identifiers\n (URIs) to identify resources that are reached using Internet mail.\n It adds better internationalization and compatibility with\n Internationalized Resource Identifiers (IRIs; RFC 3987) to the\n previous syntax of 'mailto' URIs (RFC 2368).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6068.\n\nDuerst, et al. Standards Track [ 6068 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6152","type":"specification","body":"IETF","designation":"RFC 6152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6152.txt","https://www.rfc-editor.org/rfc/rfc6152.pdf"],"folder":"IETF/RFC-6152","files":{"txt":{"path":"standards/IETF/RFC-6152/RFC-6152.txt","sha256":"f3bb53c64929a09984fc2c34daaf3ea4d4e8e90e771decf3c2453ed6c9035ad7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the SMTP service whereby an SMTP\n content body consisting of text containing octets outside of the\n US-ASCII octet range (hex 00-7F) may be relayed using SMTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6152.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is","scope_keywords":["6152","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 6152 This memo defines an extension to the SMTP service whereby an SMTP\n content body consisting of text containing octets outside of the\n US-ASCII octet range (hex 00-7F) may be relayed using SMTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6152.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is 6152 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6230","type":"specification","body":"IETF","designation":"RFC 6230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6230.txt","https://www.rfc-editor.org/rfc/rfc6230.pdf"],"folder":"IETF/RFC-6230","files":{"txt":{"path":"standards/IETF/RFC-6230/RFC-6230.txt","sha256":"c42974a328062df6ad3cbc17f670241443efcf64e74bf4c90ad5a396e9aa62c9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework and protocol for application\n deployment where the application programming logic and media\n processing are distributed. This implies that application\n programming logic can seamlessly gain access to appropriate resources\n that are not co-located on the same physical network entity. The\n framework uses the Session Initiation Protocol (SIP) to establish an\n application-level control mechanism between application servers and\n associated external servers such as media servers.\n\n The motivation for the creation of this framework is to provide an\n interface suitable to meet the requirements of a centralized\n conference system, where the conference system can be distributed, as\n defined by the XCON working group in the IETF. It is not, however,\n limited to this scope.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pr","scope_keywords":["6230","attribute","attributes","audit","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6230 This document describes a framework and protocol for application\n deployment where the application programming logic and media\n processing are distributed. This implies that application\n programming logic can seamlessly gain access to appropriate resources\n that are not co-located on the same physical network entity. The\n framework uses the Session Initiation Protocol (SIP) to establish an\n application-level control mechanism between application servers and\n associated external servers such as media servers.\n\n The motivation for the creation of this framework is to provide an\n interface suitable to meet the requirements of a centralized\n conference system, where the conference system can be distributed, as\n defined by the XCON working group in the IETF. It is not, however,\n limited to this scope.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pr 6230 attribute attributes audit http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6377","type":"specification","body":"IETF","designation":"RFC 6377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6377.txt","https://www.rfc-editor.org/rfc/rfc6377.pdf"],"folder":"IETF/RFC-6377","files":{"txt":{"path":"standards/IETF/RFC-6377/RFC-6377.txt","sha256":"f9d2f3e3f84efd15402105d8e55ee624e117638ab88b2bbae5620d414083542d"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) allows an ADministrative Management\n Domain (ADMD) to assume some responsibility for a message. Based on\n deployment experience with DKIM, this document provides guidance for\n the use of DKIM with scenarios that include Mailing List Managers\n (MLMs).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6377.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and th","scope_keywords":["6377","authentication","delivery","http","key","keys","license","management","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null}],"search_text":"IETF RFC 6377 DomainKeys Identified Mail (DKIM) allows an ADministrative Management\n Domain (ADMD) to assume some responsibility for a message. Based on\n deployment experience with DKIM, this document provides guidance for\n the use of DKIM with scenarios that include Mailing List Managers\n (MLMs).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6377.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and th 6377 authentication delivery http key keys license management signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6532","type":"specification","body":"IETF","designation":"RFC 6532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6532.txt","https://www.rfc-editor.org/rfc/rfc6532.pdf"],"folder":"IETF/RFC-6532","files":{"txt":{"path":"standards/IETF/RFC-6532/RFC-6532.txt","sha256":"154317842bdd99e2030117a808d2d74039932d1c1c3d4b014cc865069066c6cb"}},"tags":["nested-reference","unchanged"],"summary":"Internet mail was originally limited to 7-bit ASCII. MIME added\n support for the use of 8-bit character sets in body parts, and also\n defined an encoded-word construct so other character sets could be\n used in certain header field values. However, full\n internationalization of electronic mail requires additional\n enhancements to allow the use of Unicode, including characters\n outside the ASCII repertoire, in mail addresses as well as direct use\n of Unicode in header fields like \"From:\", \"To:\", and \"Subject:\",\n without requiring the use of complex encoded-word constructs. This\n document specifies an enhancement to the Internet Message Format and\n to MIME that allows use of Unicode in mail addresses and most header\n field content.\n\n This specification updates Section 6.4 of RFC 2045 to eliminate the\n restriction prohibiting the use of non-identity content-transfer-\n encodings on subtypes o","scope_keywords":["6532","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6532 Internet mail was originally limited to 7-bit ASCII. MIME added\n support for the use of 8-bit character sets in body parts, and also\n defined an encoded-word construct so other character sets could be\n used in certain header field values. However, full\n internationalization of electronic mail requires additional\n enhancements to allow the use of Unicode, including characters\n outside the ASCII repertoire, in mail addresses as well as direct use\n of Unicode in header fields like \"From:\", \"To:\", and \"Subject:\",\n without requiring the use of complex encoded-word constructs. This\n document specifies an enhancement to the Internet Message Format and\n to MIME that allows use of Unicode in mail addresses and most header\n field content.\n\n This specification updates Section 6.4 of RFC 2045 to eliminate the\n restriction prohibiting the use of non-identity content-transfer-\n encodings on subtypes o 6532 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6533","type":"specification","body":"IETF","designation":"RFC 6533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6533.txt","https://www.rfc-editor.org/rfc/rfc6533.pdf"],"folder":"IETF/RFC-6533","files":{"txt":{"path":"standards/IETF/RFC-6533/RFC-6533.txt","sha256":"9b852463bef94f202e9b53205212263c7fa5a932f40ee514f29f0c4ed27f7659"}},"tags":["nested-reference","unchanged"],"summary":"Delivery status notifications (DSNs) are critical to the correct\n operation of an email system. However, the existing Draft Standards\n (RFC 3461, RFC 3464, RFC 6522) are presently limited to ASCII text in\n the machine-readable portions of the protocol. This specification\n adds a new address type for international email addresses so an\n original recipient address with non-ASCII characters can be correctly\n preserved even after downgrading. This also provides updated content\n return media types for delivery status notifications and message\n disposition notifications to support use of the new address type.\n\n This document extends RFC 3461, RFC 3464, RFC 3798, and RFC 6522.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public ","scope_keywords":["6533","delivery","http","key","license","presentation","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null}],"search_text":"IETF RFC 6533 Delivery status notifications (DSNs) are critical to the correct\n operation of an email system. However, the existing Draft Standards\n (RFC 3461, RFC 3464, RFC 6522) are presently limited to ASCII text in\n the machine-readable portions of the protocol. This specification\n adds a new address type for international email addresses so an\n original recipient address with non-ASCII characters can be correctly\n preserved even after downgrading. This also provides updated content\n return media types for delivery status notifications and message\n disposition notifications to support use of the new address type.\n\n This document extends RFC 3461, RFC 3464, RFC 3798, and RFC 6522.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public  6533 delivery http key license presentation preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 6591","type":"specification","body":"IETF","designation":"RFC 6591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6591.txt","https://www.rfc-editor.org/rfc/rfc6591.pdf"],"folder":"IETF/RFC-6591","files":{"txt":{"path":"standards/IETF/RFC-6591/RFC-6591.txt","sha256":"1403eda43981567701bb61757c2accf8d21abccca7956182274a46b6edcfc593"}},"tags":["nested-reference","unchanged"],"summary":"This memo registers an extension report type for the Abuse Reporting\n Format (ARF), affecting multiple registries, for use in generating\n receipt-time reports about messages that fail one or more email\n message authentication checks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6591.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors.","scope_keywords":["6591","authentication","authorization","http","key","keys","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6591 This memo registers an extension report type for the Abuse Reporting\n Format (ARF), affecting multiple registries, for use in generating\n receipt-time reports about messages that fail one or more email\n message authentication checks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6591.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. 6591 authentication authorization http key keys license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6652","type":"specification","body":"IETF","designation":"RFC 6652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6652.txt","https://www.rfc-editor.org/rfc/rfc6652.pdf"],"folder":"IETF/RFC-6652","files":{"txt":{"path":"standards/IETF/RFC-6652/RFC-6652.txt","sha256":"f8a0ee527a62884f4dbd13b46db7fc0751f94702c3fd51844d05e5d428c531b0"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents extensions to the Abuse Reporting Format (ARF) and\n Sender Policy Framework (SPF) specifications to allow for detailed\n reporting of message authentication failures in an on-demand fashion.\n\n This memo updates RFC 4408 by providing an IANA registry for SPF\n modifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6652.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trus","scope_keywords":["6652","algorithm","authentication","http","key","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6652 This memo presents extensions to the Abuse Reporting Format (ARF) and\n Sender Policy Framework (SPF) specifications to allow for detailed\n reporting of message authentication failures in an on-demand fashion.\n\n This memo updates RFC 4408 by providing an IANA registry for SPF\n modifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6652.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trus 6652 algorithm authentication http key license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6839","type":"specification","body":"IETF","designation":"RFC 6839","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6839.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6839.txt","https://www.rfc-editor.org/rfc/rfc6839.pdf"],"folder":"IETF/RFC-6839","files":{"txt":{"path":"standards/IETF/RFC-6839/RFC-6839.txt","sha256":"f754a5e85371359a1b6609427ab9a759dc012af7f656a8741fdac4942abf8c13"}},"tags":["nested-reference","unchanged"],"summary":"A content media type name sometimes includes partitioned meta-\n information distinguished by a structured syntax to permit noting an\n attribute of the media as a suffix to the name. This document\n defines several structured syntax suffixes for use with media type\n registrations. In particular, it defines and registers the \"+json\",\n \"+ber\", \"+der\", \"+fastinfoset\", \"+wbxml\" and \"+zip\" structured syntax\n suffixes, and provides a media type structured syntax suffix\n registration form for the \"+xml\" structured syntax suffix.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (","scope_keywords":["6839","attribute","http","identification","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 6839 A content media type name sometimes includes partitioned meta-\n information distinguished by a structured syntax to permit noting an\n attribute of the media as a suffix to the name. This document\n defines several structured syntax suffixes for use with media type\n registrations. In particular, it defines and registers the \"+json\",\n \"+ber\", \"+der\", \"+fastinfoset\", \"+wbxml\" and \"+zip\" structured syntax\n suffixes, and provides a media type structured syntax suffix\n registration form for the \"+xml\" structured syntax suffix.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group ( 6839 attribute http identification key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6857","type":"specification","body":"IETF","designation":"RFC 6857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6857.txt","https://www.rfc-editor.org/rfc/rfc6857.pdf"],"folder":"IETF/RFC-6857","files":{"txt":{"path":"standards/IETF/RFC-6857/RFC-6857.txt","sha256":"c3958fe0f7820d557ffb8d3987af5b834202258d6e267616fab3850befa761de"}},"tags":["nested-reference","unchanged"],"summary":"The Email Address Internationalization (SMTPUTF8) extension to SMTP\n allows Unicode characters encoded in UTF-8 and outside the ASCII\n repertoire in mail header fields. Upgraded POP and IMAP servers\n support internationalized messages. If a POP or IMAP client does not\n support Email Address Internationalization, a POP or IMAP server\n cannot deliver internationalized messages to the client and cannot\n remove the message. To avoid that situation, this document describes\n a mechanism for converting internationalized messages into the\n traditional message format. As part of the conversion process,\n message elements that require internationalized treatment are recoded\n or removed, and receivers are able to recognize that they received\n messages containing such elements, even if they cannot process the\n internationalized elements.\n\nStatus of This Memo\n\n This is an Internet Standards Track docu","scope_keywords":["6857","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null}],"search_text":"IETF RFC 6857 The Email Address Internationalization (SMTPUTF8) extension to SMTP\n allows Unicode characters encoded in UTF-8 and outside the ASCII\n repertoire in mail header fields. Upgraded POP and IMAP servers\n support internationalized messages. If a POP or IMAP client does not\n support Email Address Internationalization, a POP or IMAP server\n cannot deliver internationalized messages to the client and cannot\n remove the message. To avoid that situation, this document describes\n a mechanism for converting internationalized messages into the\n traditional message format. As part of the conversion process,\n message elements that require internationalized treatment are recoded\n or removed, and receivers are able to recognize that they received\n messages containing such elements, even if they cannot process the\n internationalized elements.\n\nStatus of This Memo\n\n This is an Internet Standards Track docu 6857 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6920","type":"specification","body":"IETF","designation":"RFC 6920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6920.txt","https://www.rfc-editor.org/rfc/rfc6920.pdf"],"folder":"IETF/RFC-6920","files":{"txt":{"path":"standards/IETF/RFC-6920/RFC-6920.txt","sha256":"f1cfd3e68b44b91c9ee68c914b37c0d9ea0984f507c58bc5a6d07f23ac058677"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of ways to identify a thing (a digital\n object in this case) using the output from a hash function. It\n specifies a new URI scheme for this purpose, a way to map these to\n HTTP URLs, and binary and human-speakable formats for these names.\n The various formats are designed to support, but not require, a\n strong link to the referenced object, such that the referenced object\n may be authenticated to the same degree as the reference to it. The\n reason for this work is to standardise current uses of hash outputs\n in URLs and to support new information-centric applications and other\n uses of hash outputs in protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo","scope_keywords":["6920","algorithm","attribute","certificate","certificates","crl","hash","http","key","license","presentation","revocation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null}],"search_text":"IETF RFC 6920 This document defines a set of ways to identify a thing (a digital\n object in this case) using the output from a hash function. It\n specifies a new URI scheme for this purpose, a way to map these to\n HTTP URLs, and binary and human-speakable formats for these names.\n The various formats are designed to support, but not require, a\n strong link to the referenced object, such that the referenced object\n may be authenticated to the same degree as the reference to it. The\n reason for this work is to standardise current uses of hash outputs\n in URLs and to support new information-centric applications and other\n uses of hash outputs in protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved fo 6920 algorithm attribute certificate certificates crl hash http key license presentation revocation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7071","type":"specification","body":"IETF","designation":"RFC 7071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7071.txt","https://www.rfc-editor.org/rfc/rfc7071.pdf"],"folder":"IETF/RFC-7071","files":{"txt":{"path":"standards/IETF/RFC-7071/RFC-7071.txt","sha256":"769f134e5d57fb4199a9d1784a7ab062fcda11981bfa6296be5d2fadc8102bf4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the format of reputation response data\n (\"reputons\"), the media type for packaging it, and definition of a\n registry for the names of reputation applications and response sets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7071.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume","scope_keywords":["7071","attribute","attributes","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 7071 This document defines the format of reputation response data\n (\"reputons\"), the media type for packaging it, and definition of a\n registry for the names of reputation applications and response sets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7071.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume 7071 attribute attributes http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7072","type":"specification","body":"IETF","designation":"RFC 7072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7072.txt","https://www.rfc-editor.org/rfc/rfc7072.pdf"],"folder":"IETF/RFC-7072","files":{"txt":{"path":"standards/IETF/RFC-7072/RFC-7072.txt","sha256":"7e0b6c4bcd7ce03ca5656de22ca974c30eb7f7737985c520ac1adc97b3674c55"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism to conduct queries for reputation\n information over the HyperText Transfer Protocol (HTTP) using\n JavaScript Object Notation (JSON) as the payload meta-format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7072.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is","scope_keywords":["7072","attribute","attributes","http","key","license","registered","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null}],"search_text":"IETF RFC 7072 This document defines a mechanism to conduct queries for reputation\n information over the HyperText Transfer Protocol (HTTP) using\n JavaScript Object Notation (JSON) as the payload meta-format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7072.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is 7072 attribute attributes http key license registered subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 8098","type":"specification","body":"IETF","designation":"RFC 8098","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8098.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8098.txt","https://www.rfc-editor.org/rfc/rfc8098.pdf"],"folder":"IETF/RFC-8098","files":{"txt":{"path":"standards/IETF/RFC-8098/RFC-8098.txt","sha256":"3cf52c2a77826e0ee3dd5a2d57b9d069d2f5b5a46f480f6c46e1d1c1066cea33"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a MIME content type that may be used by a Mail User\n Agent (MUA) or electronic mail gateway to report the disposition of a\n message after it has been successfully delivered to a recipient.\n This content type is intended to be machine processable. Additional\n message header fields are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and are often referred to as \"read receipts,\"\n \"acknowledgements,\" or \"receipt notifications.\" The intention is to\n do this while respecting privacy concerns, which have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging system","scope_keywords":["8098","attribute","attributes","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 8098 This memo defines a MIME content type that may be used by a Mail User\n Agent (MUA) or electronic mail gateway to report the disposition of a\n message after it has been successfully delivered to a recipient.\n This content type is intended to be machine processable. Additional\n message header fields are also defined to permit Message Disposition\n Notifications (MDNs) to be requested by the sender of a message. The\n purpose is to extend Internet Mail to support functionality often\n found in other messaging systems, such as X.400 and the proprietary\n \"LAN-based\" systems, and are often referred to as \"read receipts,\"\n \"acknowledgements,\" or \"receipt notifications.\" The intention is to\n do this while respecting privacy concerns, which have often been\n expressed when such functions have been discussed in the past.\n\n Because many messages are sent between the Internet and other\n messaging system 8098 attribute attributes delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2346","type":"specification","body":"IETF","designation":"RFC 2346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2346.txt","https://www.rfc-editor.org/rfc/rfc2346.pdf"],"folder":"IETF/RFC-2346","files":{"txt":{"path":"standards/IETF/RFC-2346/RFC-2346.txt","sha256":"60672c35d5a26da7c37b2eee75881f44fedb04e70be8b2f7de229853aeba8089"}},"tags":["nested-reference","unchanged"],"summary":"Certain text formats, for example Postscript (MIME-Type:\n application/postscript; file extension .ps) and Portable Document\n Format (MIME-Type: application/pdf; file extension .pdf) specify\n exactly the page layout of the printed document. The commonly used\n paper format is different in North America and the rest of the world.\n North America uses the 'Letter' format, while the rest of the world\n mostly uses the ISO-standard 'A4' format. This means that documents\n formatted on one continent may not be easily printable on another\n continent. This memo gives advice on how to produce documents which\n are equally well printable with the Letter and the A4 formats. By\n using the advice in this document, you can put up a document on the\n Internet, which recipients can print without problem both in and\n outside North America.\n\n A very short summary of the advice in this document: If you are using","scope_keywords":["2346"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"IETF RFC 2346 Certain text formats, for example Postscript (MIME-Type:\n application/postscript; file extension .ps) and Portable Document\n Format (MIME-Type: application/pdf; file extension .pdf) specify\n exactly the page layout of the printed document. The commonly used\n paper format is different in North America and the rest of the world.\n North America uses the 'Letter' format, while the rest of the world\n mostly uses the ISO-standard 'A4' format. This means that documents\n formatted on one continent may not be easily printable on another\n continent. This memo gives advice on how to produce documents which\n are equally well printable with the Letter and the A4 formats. By\n using the advice in this document, you can put up a document on the\n Internet, which recipients can print without problem both in and\n outside North America.\n\n A very short summary of the advice in this document: If you are using 2346 nested-reference unchanged"},{"id":"IETF RFC 2424","type":"specification","body":"IETF","designation":"RFC 2424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2424.txt","https://www.rfc-editor.org/rfc/rfc2424.pdf"],"folder":"IETF/RFC-2424","files":{"txt":{"path":"standards/IETF/RFC-2424/RFC-2424.txt","sha256":"776e03ee0cd19de98d926043a2f2f5e5cb89b361d4ced59af61e5b7edbcc45a6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*). The length of time is represented in seconds\n without any units indication.\n\n2. Content-Duration Header Field\n\n Time varying media contents, for example, a spoken voice message or a\n video clip, have an inherent time duration. Many audio and video\n encodings may include their duration as header information or may\n allow accurate calculation based on the byte length of the data.\n However, it may be useful to present the time duration of the content\n in a MIME header to allow its simple determination without dealing\n with the actual content.\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2424 Content-Duration September 1998\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MA","scope_keywords":["2424","identification","key","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3803","folder":"IETF/RFC-3803","source":"IETF/RFC-3803/RFC-3803.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 2424 This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*). The length of time is represented in seconds\n without any units indication.\n\n2. Content-Duration Header Field\n\n Time varying media contents, for example, a spoken voice message or a\n video clip, have an inherent time duration. Many audio and video\n encodings may include their duration as header information or may\n allow accurate calculation based on the byte length of the data.\n However, it may be useful to present the time duration of the content\n in a MIME header to allow its simple determination without dealing\n with the actual content.\n\nVaudreuil & Parsons Standards Track [Page 1]\n\f\nRFC 2424 Content-Duration September 1998\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MA 2424 identification key profile trust nested-reference unchanged"},{"id":"IETF RFC 2652","type":"specification","body":"IETF","designation":"RFC 2652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2652.txt","https://www.rfc-editor.org/rfc/rfc2652.pdf"],"folder":"IETF/RFC-2652","files":{"txt":{"path":"standards/IETF/RFC-2652/RFC-2652.txt","sha256":"8cc8d5691537d99705872e8f40300b0a81133a5192cd25d4959d98c6223f85e1"}},"tags":["nested-reference","unchanged"],"summary":"The Common Indexing Protocol (CIP) is used to pass indexing\n information from server to server in order to facilitate query\n routing. The protocol is comprised of several MIME objects being\n passed from server to server. This document describes the definitions\n of those objects as well as the methods and requirements needed to\n define a new index type.\n\n1. Introduction\n\n The Common Indexing Protocol (CIP) is used to pass indexes between\n servers that combine multiple indexes and/or route queries based on\n those indexes. The overall framework for the protocol is specified in\n the CIP Framework document [FRAMEWORK]. This document should be read\n within the context of that document as there are fundamental concepts\n contained in the framework that are not fully explained here.\n\n Since there are several different ways to index a given database\n there will be multiple types of indexes to pass","scope_keywords":["2652","audit","authentication","key","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2651","folder":"IETF/RFC-2651","source":"IETF/RFC-2651/RFC-2651.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2652 The Common Indexing Protocol (CIP) is used to pass indexing\n information from server to server in order to facilitate query\n routing. The protocol is comprised of several MIME objects being\n passed from server to server. This document describes the definitions\n of those objects as well as the methods and requirements needed to\n define a new index type.\n\n1. Introduction\n\n The Common Indexing Protocol (CIP) is used to pass indexes between\n servers that combine multiple indexes and/or route queries based on\n those indexes. The overall framework for the protocol is specified in\n the CIP Framework document [FRAMEWORK]. This document should be read\n within the context of that document as there are fundamental concepts\n contained in the framework that are not fully explained here.\n\n Since there are several different ways to index a given database\n there will be multiple types of indexes to pass 2652 audit authentication key policy trust nested-reference unchanged"},{"id":"IETF RFC 3195","type":"specification","body":"IETF","designation":"RFC 3195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3195.txt","https://www.rfc-editor.org/rfc/rfc3195.pdf"],"folder":"IETF/RFC-3195","files":{"txt":{"path":"standards/IETF/RFC-3195/RFC-3195.txt","sha256":"345fe7d1505fc76659c9a828744e49a7810c914223ac1dea3b3aa711278cdb9e"}},"tags":["nested-reference","unchanged"],"summary":"The BSD Syslog Protocol describes a number of service options related\n to propagating event messages. This memo describes two mappings of\n the syslog protocol to TCP connections, both useful for reliable\n delivery of event messages. The first provides a trivial mapping\n maximizing backward compatibility. The second provides a more\n complete mapping. Both provide a degree of robustness and security\n in message delivery that is unavailable to the usual UDP-based syslog\n protocol, by providing encryption and authentication over a\n connection-oriented protocol.\n\nNew & Rose Standards Track [Page 1]\n\f\nRFC 3195 Reliable Delivery for syslog November 2001","scope_keywords":["3195","authentication","delivery","encryption","identification","key","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3195 The BSD Syslog Protocol describes a number of service options related\n to propagating event messages. This memo describes two mappings of\n the syslog protocol to TCP connections, both useful for reliable\n delivery of event messages. The first provides a trivial mapping\n maximizing backward compatibility. The second provides a more\n complete mapping. Both provide a degree of robustness and security\n in message delivery that is unavailable to the usual UDP-based syslog\n protocol, by providing encryption and authentication over a\n connection-oriented protocol.\n\nNew & Rose Standards Track [Page 1]\n\f\nRFC 3195 Reliable Delivery for syslog November 2001 3195 authentication delivery encryption identification key path profile profiles nested-reference unchanged"},{"id":"IETF RFC 3205","type":"specification","body":"IETF","designation":"RFC 3205","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3205.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3205.txt","https://www.rfc-editor.org/rfc/rfc3205.pdf"],"folder":"IETF/RFC-3205","files":{"txt":{"path":"standards/IETF/RFC-3205/RFC-3205.txt","sha256":"8e4e36aeebd60a3e74028a253bac312db1fd0946db824eb121c9e71f0b48c424"}},"tags":["nested-reference","unchanged"],"summary":"Recently there has been widespread interest in using Hypertext\n Transfer Protocol (HTTP) as a substrate for other applications-level\n protocols. This document recommends technical particulars of such\n use, including use of default ports, URL schemes, and HTTP security\n mechanisms.\n\n1. Introduction\n\n Recently there has been widespread interest in using Hypertext\n Transfer Protocol (HTTP) [1] as a substrate for other applications-\n level protocols. Various reasons cited for this interest have\n included:\n\n o familiarity and mindshare,\n\n o compatibility with widely deployed browsers,\n\n o ability to reuse existing servers and client libraries,\n\n o ease of prototyping servers using CGI scripts and similar\n extension mechanisms,\n\n o ability to use existing security mechanisms such as HTTP digest\n authentication [2] and SSL or TLS [3],\n\n o the ability of HTTP to traverse firewalls, and\n\n o cases","scope_keywords":["3205","authentication","certificate","http","key","keys","profile","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 3205 Recently there has been widespread interest in using Hypertext\n Transfer Protocol (HTTP) as a substrate for other applications-level\n protocols. This document recommends technical particulars of such\n use, including use of default ports, URL schemes, and HTTP security\n mechanisms.\n\n1. Introduction\n\n Recently there has been widespread interest in using Hypertext\n Transfer Protocol (HTTP) [1] as a substrate for other applications-\n level protocols. Various reasons cited for this interest have\n included:\n\n o familiarity and mindshare,\n\n o compatibility with widely deployed browsers,\n\n o ability to reuse existing servers and client libraries,\n\n o ease of prototyping servers using CGI scripts and similar\n extension mechanisms,\n\n o ability to use existing security mechanisms such as HTTP digest\n authentication [2] and SSL or TLS [3],\n\n o the ability of HTTP to traverse firewalls, and\n\n o cases 3205 authentication certificate http key keys profile tls trust nested-reference unchanged"},{"id":"IETF RFC 3236","type":"specification","body":"IETF","designation":"RFC 3236","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3236.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3236.txt","https://www.rfc-editor.org/rfc/rfc3236.pdf"],"folder":"IETF/RFC-3236","files":{"txt":{"path":"standards/IETF/RFC-3236/RFC-3236.txt","sha256":"278fa81a017b316833ed5064a38bf1d1fb647f178729b71b11960a297f73d88f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Baker\nRequest for Comments: 3236 Planetfred, Inc.\nCategory: Informational P. Stark\n Ericsson Mobile Communications\n January 2002\n\n The 'application/xhtml+xml' Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines the 'application/xhtml+xml' MIME media type for\n XHTML based markup languages; it is not intended to obsolete any\n previous IETF documents, in particular RFC 2854 which registers\n 'text/html'.\n\n1. Introduction\n\n In 1998, the W3C HTML working group began work on reformulating HTML\n in terms of XML 1.0 [XML] and XML Namespaces [XMLNS]. The first part\n of that work concluded in January 2000 with the publicati","scope_keywords":["3236","attribute","http","identification","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null}],"search_text":"IETF RFC 3236 Network Working Group M. Baker\nRequest for Comments: 3236 Planetfred, Inc.\nCategory: Informational P. Stark\n Ericsson Mobile Communications\n January 2002\n\n The 'application/xhtml+xml' Media Type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines the 'application/xhtml+xml' MIME media type for\n XHTML based markup languages; it is not intended to obsolete any\n previous IETF documents, in particular RFC 2854 which registers\n 'text/html'.\n\n1. Introduction\n\n In 1998, the W3C HTML working group began work on reformulating HTML\n in terms of XML 1.0 [XML] and XML Namespaces [XMLNS]. The first part\n of that work concluded in January 2000 with the publicati 3236 attribute http identification profile registered nested-reference unchanged"},{"id":"IETF RFC 3398","type":"specification","body":"IETF","designation":"RFC 3398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3398.txt","https://www.rfc-editor.org/rfc/rfc3398.pdf"],"folder":"IETF/RFC-3398","files":{"txt":{"path":"standards/IETF/RFC-3398/RFC-3398.txt","sha256":"58fcfd58ac1eb24ee6cc3fe1f1cde95c30841dc616ab3c36b22caa34bd1f15c8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a way to perform the mapping between two\n signaling protocols: the Session Initiation Protocol (SIP) and the\n Integrated Services Digital Network (ISDN) User Part (ISUP) of\n Signaling System No. 7 (SS7). This mechanism might be implemented\n when using SIP in an environment where part of the call involves\n interworking with the Public Switched Telephone Network (PSTN).","scope_keywords":["3398"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3578","folder":"IETF/RFC-3578","source":"IETF/RFC-3578/RFC-3578.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 3398 This document describes a way to perform the mapping between two\n signaling protocols: the Session Initiation Protocol (SIP) and the\n Integrated Services Digital Network (ISDN) User Part (ISUP) of\n Signaling System No. 7 (SS7). This mechanism might be implemented\n when using SIP in an environment where part of the call involves\n interworking with the Public Switched Telephone Network (PSTN). 3398 nested-reference unchanged"},{"id":"IETF RFC 3420","type":"specification","body":"IETF","designation":"RFC 3420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3420.txt","https://www.rfc-editor.org/rfc/rfc3420.pdf"],"folder":"IETF/RFC-3420","files":{"txt":{"path":"standards/IETF/RFC-3420/RFC-3420.txt","sha256":"e5c9075ebb075d830412c546ef8e71ee36b1a926fa63e167923fe7f309235c59"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the message/sipfrag Multipurpose Internet\n Mail Extensions (MIME) media type. This type is similar to\n message/sip, but allows certain subsets of well formed Session\n Initiation Protocol (SIP) messages to be represented instead of\n requiring a complete SIP message. In addition to end-to-end security\n uses, message/sipfrag is used with the REFER method to convey\n information about the status of a referenced request.","scope_keywords":["3420","crl","key","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3515","folder":"IETF/RFC-3515","source":"IETF/RFC-3515/RFC-3515.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null}],"search_text":"IETF RFC 3420 This document registers the message/sipfrag Multipurpose Internet\n Mail Extensions (MIME) media type. This type is similar to\n message/sip, but allows certain subsets of well formed Session\n Initiation Protocol (SIP) messages to be represented instead of\n requiring a complete SIP message. In addition to end-to-end security\n uses, message/sipfrag is used with the REFER method to convey\n information about the status of a referenced request. 3420 crl key presentation subject nested-reference unchanged"},{"id":"IETF RFC 3842","type":"specification","body":"IETF","designation":"RFC 3842","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3842.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3842.txt","https://www.rfc-editor.org/rfc/rfc3842.pdf"],"folder":"IETF/RFC-3842","files":{"txt":{"path":"standards/IETF/RFC-3842/RFC-3842.txt","sha256":"93518f310fde3673e9f63f79485403e77fd2458c1fb51ddc86a5bfaea7e1885c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Session Initiation Protocol (SIP) event\n package to carry message waiting status and message summaries from a\n messaging system to an interested User Agent.\n\nMahy Standards Track [Page 1]\n\f\nRFC 3842 SIP Message Waiting August 2004","scope_keywords":["3842","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null}],"search_text":"IETF RFC 3842 This document describes a Session Initiation Protocol (SIP) event\n package to carry message waiting status and message summaries from a\n messaging system to an interested User Agent.\n\nMahy Standards Track [Page 1]\n\f\nRFC 3842 SIP Message Waiting August 2004 3842 key registered nested-reference unchanged"},{"id":"IETF RFC 4180","type":"specification","body":"IETF","designation":"RFC 4180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4180.txt","https://www.rfc-editor.org/rfc/rfc4180.pdf"],"folder":"IETF/RFC-4180","files":{"txt":{"path":"standards/IETF/RFC-4180/RFC-4180.txt","sha256":"5d9ec035aa40c0108362cb767c9e2d08c30f7225cb2a4715f484cb13c29b5f21"}},"tags":["nested-reference","unchanged"],"summary":"This RFC documents the format used for Comma-Separated Values (CSV)\n files and registers the associated MIME type \"text/csv\".","scope_keywords":["4180","crl","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null}],"search_text":"IETF RFC 4180 This RFC documents the format used for Comma-Separated Values (CSV)\n files and registers the associated MIME type \"text/csv\". 4180 crl registered risk subject nested-reference unchanged"},{"id":"IETF RFC 4463","type":"specification","body":"IETF","designation":"RFC 4463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4463.txt","https://www.rfc-editor.org/rfc/rfc4463.pdf"],"folder":"IETF/RFC-4463","files":{"txt":{"path":"standards/IETF/RFC-4463/RFC-4463.txt","sha256":"5c9b1d72ec1d88197cf37d24cb06cb0f6313cd0a2a7c8490fae19cec89e2f4ef"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Media Resource Control Protocol (MRCP) that\n was developed jointly by Cisco Systems, Inc., Nuance Communications,\n and Speechworks, Inc. It is published as an RFC as input for further\n IETF development in this area.\n\n MRCP controls media service resources like speech synthesizers,\n recognizers, signal generators, signal detectors, fax servers, etc.,\n over a network. This protocol is designed to work with streaming\n protocols like RTSP (Real Time Streaming Protocol) or SIP (Session\n Initiation Protocol), which help establish control connections to\n external media streaming devices, and media delivery mechanisms like\n RTP (Real Time Protocol).","scope_keywords":["4463","delivery","registered","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null}],"search_text":"IETF RFC 4463 This document describes a Media Resource Control Protocol (MRCP) that\n was developed jointly by Cisco Systems, Inc., Nuance Communications,\n and Speechworks, Inc. It is published as an RFC as input for further\n IETF development in this area.\n\n MRCP controls media service resources like speech synthesizers,\n recognizers, signal generators, signal detectors, fax servers, etc.,\n over a network. This protocol is designed to work with streaming\n protocols like RTSP (Real Time Streaming Protocol) or SIP (Session\n Initiation Protocol), which help establish control connections to\n external media streaming devices, and media delivery mechanisms like\n RTP (Real Time Protocol). 4463 delivery registered tsp nested-reference unchanged"},{"id":"IETF RFC 4622","type":"specification","body":"IETF","designation":"RFC 4622","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4622.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4622.txt","https://www.rfc-editor.org/rfc/rfc4622.pdf"],"folder":"IETF/RFC-4622","files":{"txt":{"path":"standards/IETF/RFC-4622/RFC-4622.txt","sha256":"af4dd8dc101bd2cb5f58bc10022e40fadf669d024280d3b5d00201fbbe76e5a9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the use of Internationalized Resource\n Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in\n identifying or interacting with entities that can communicate via the\n Extensible Messaging and Presence Protocol (XMPP).\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 4622 XMPP IRIs/URIs July 2006","scope_keywords":["4622","attribute","http","identification","key","management","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null}],"search_text":"IETF RFC 4622 This document defines the use of Internationalized Resource\n Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in\n identifying or interacting with entities that can communicate via the\n Extensible Messaging and Presence Protocol (XMPP).\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 4622 XMPP IRIs/URIs July 2006 4622 attribute http identification key management path profile profiles nested-reference unchanged"},{"id":"IETF RFC 5122","type":"specification","body":"IETF","designation":"RFC 5122","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5122.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5122.txt","https://www.rfc-editor.org/rfc/rfc5122.pdf"],"folder":"IETF/RFC-5122","files":{"txt":{"path":"standards/IETF/RFC-5122/RFC-5122.txt","sha256":"adab382be15de09c731fbfd78812c7f8f43ce13f03dbcc352034e53b96b1e5f3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the use of Internationalized Resource\n Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in\n identifying or interacting with entities that can communicate via the\n Extensible Messaging and Presence Protocol (XMPP).\n\n This document obsoletes RFC 4622.\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 5122 XMPP IRIs/URIs February 2008","scope_keywords":["5122","attribute","http","key","management","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 5122 This document defines the use of Internationalized Resource\n Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in\n identifying or interacting with entities that can communicate via the\n Extensible Messaging and Presence Protocol (XMPP).\n\n This document obsoletes RFC 4622.\n\nSaint-Andre Standards Track [Page 1]\n\f\nRFC 5122 XMPP IRIs/URIs February 2008 5122 attribute http key management path profile profiles nested-reference unchanged"},{"id":"IETF RFC 6072","type":"specification","body":"IETF","designation":"RFC 6072","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6072.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6072.txt","https://www.rfc-editor.org/rfc/rfc6072.pdf"],"folder":"IETF/RFC-6072","files":{"txt":{"path":"standards/IETF/RFC-6072/RFC-6072.txt","sha256":"60e5ee16af10571664b5463d59f57d9f04616f7f929c4e7886666103a837ee8c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a credential service that allows Session\n Initiation Protocol (SIP) User Agents (UAs) to use a SIP event\n package to discover the certificates of other users. This mechanism\n allows User Agents that want to contact a given Address-of-Record\n (AOR) to retrieve that AOR's certificate by subscribing to the\n credential service, which returns an authenticated response\n containing that certificate. The credential service also allows\n users to store and retrieve their own certificates and private keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in ","scope_keywords":["6072","algorithm","authentication","certificate","certificates","credential","credentials","encryption","http","key","keys","license","management","profile","profiles","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null}],"search_text":"IETF RFC 6072 This document defines a credential service that allows Session\n Initiation Protocol (SIP) User Agents (UAs) to use a SIP event\n package to discover the certificates of other users. This mechanism\n allows User Agents that want to contact a given Address-of-Record\n (AOR) to retrieve that AOR's certificate by subscribing to the\n credential service, which returns an authenticated response\n containing that certificate. The credential service also allows\n users to store and retrieve their own certificates and private keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in  6072 algorithm authentication certificate certificates credential credentials encryption http key keys license management profile profiles revocation nested-reference unchanged"},{"id":"IETF RFC 6266","type":"specification","body":"IETF","designation":"RFC 6266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6266.txt","https://www.rfc-editor.org/rfc/rfc6266.pdf"],"folder":"IETF/RFC-6266","files":{"txt":{"path":"standards/IETF/RFC-6266/RFC-6266.txt","sha256":"2887d464e7a2a15877aba5d54b2e8e0c06c32294c44c9d95eb8940069ab43d33"}},"tags":["nested-reference","unchanged"],"summary":"RFC 2616 defines the Content-Disposition response header field, but\n points out that it is not part of the HTTP/1.1 Standard. This\n specification takes over the definition and registration of Content-\n Disposition, as used in HTTP, and clarifies internationalization\n aspects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6266.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the p","scope_keywords":["6266","http","key","license","profile","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null}],"search_text":"IETF RFC 6266 RFC 2616 defines the Content-Disposition response header field, but\n points out that it is not part of the HTTP/1.1 Standard. This\n specification takes over the definition and registration of Content-\n Disposition, as used in HTTP, and clarifies internationalization\n aspects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6266.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the p 6266 http key license profile risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6657","type":"specification","body":"IETF","designation":"RFC 6657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6657.txt","https://www.rfc-editor.org/rfc/rfc6657.pdf"],"folder":"IETF/RFC-6657","files":{"txt":{"path":"standards/IETF/RFC-6657/RFC-6657.txt","sha256":"34ac5be5f475756e14df79495d646a75f8b046c76422a7237e044728cbc5ca8d"}},"tags":["nested-reference","unchanged"],"summary":"This document changes RFC 2046 rules regarding default \"charset\"\n parameter values for \"text/*\" media types to better align with common\n usage by existing clients and servers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6657.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78","scope_keywords":["6657","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null}],"search_text":"IETF RFC 6657 This document changes RFC 2046 rules regarding default \"charset\"\n parameter values for \"text/*\" media types to better align with common\n usage by existing clients and servers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6657.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 6657 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7233","type":"specification","body":"IETF","designation":"RFC 7233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7233.txt","https://www.rfc-editor.org/rfc/rfc7233.pdf"],"folder":"IETF/RFC-7233","files":{"txt":{"path":"standards/IETF/RFC-7233/RFC-7233.txt","sha256":"da3d69c64efad7c05bed9b92a7ccd3444d2d47702e7415af56b0beedd6883592"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines range requests and the rules for\n constructing and combining responses to those requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7233.\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 7233 HTTP/1.1 Range Requests","scope_keywords":["7233","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7233 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines range requests and the rules for\n constructing and combining responses to those requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7233.\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 7233 HTTP/1.1 Range Requests 7233 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8040","type":"specification","body":"IETF","designation":"RFC 8040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8040.txt","https://www.rfc-editor.org/rfc/rfc8040.pdf"],"folder":"IETF/RFC-8040","files":{"txt":{"path":"standards/IETF/RFC-8040/RFC-8040.txt","sha256":"ab4b8cf15065cf34a6dd982dbaaf8db794fca90cdba795de452d8384a4b7e15c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an HTTP-based protocol that provides a\n programmatic interface for accessing data defined in YANG, using the\n datastore concepts defined in the Network Configuration Protocol\n (NETCONF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8040.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n","scope_keywords":["8040","certificate","certificates","http","https","license","subject","timestamp","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null}],"search_text":"IETF RFC 8040 This document describes an HTTP-based protocol that provides a\n programmatic interface for accessing data defined in YANG, using the\n datastore concepts defined in the Network Configuration Protocol\n (NETCONF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8040.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n 8040 certificate certificates http https license subject timestamp trust validation nested-reference unchanged"},{"id":"IETF RFC 8225","type":"specification","body":"IETF","designation":"RFC 8225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8225.txt","https://www.rfc-editor.org/rfc/rfc8225.pdf"],"folder":"IETF/RFC-8225","files":{"txt":{"path":"standards/IETF/RFC-8225/RFC-8225.txt","sha256":"389fc4ad87bfc8da8f7f7a74b68869e4895d5065123bdd889697259bfcf2d2bd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a method for creating and validating a token\n that cryptographically verifies an originating identity or, more\n generally, a URI or telephone number representing the originator of\n personal communications. The Personal Assertion Token, PASSporT, is\n cryptographically signed to protect the integrity of the identity of\n the originator and to verify the assertion of the identity\n information at the destination. The cryptographic signature is\n defined with the intention that it can confidently verify the\n originating persona even when the signature is sent to the\n destination party over an insecure channel. PASSporT is particularly\n useful for many personal-communications applications over IP networks\n and other multi-hop interconnection scenarios where the originating\n and destination parties may not have a direct trusted relationship.\n\nStatus of This Memo\n\n This is an","scope_keywords":["8225","algorithm","encryption","http","https","key","license","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null}],"search_text":"IETF RFC 8225 This document defines a method for creating and validating a token\n that cryptographically verifies an originating identity or, more\n generally, a URI or telephone number representing the originator of\n personal communications. The Personal Assertion Token, PASSporT, is\n cryptographically signed to protect the integrity of the identity of\n the originator and to verify the assertion of the identity\n information at the destination. The cryptographic signature is\n defined with the intention that it can confidently verify the\n originating persona even when the signature is sent to the\n destination party over an insecure channel. PASSporT is particularly\n useful for many personal-communications applications over IP networks\n and other multi-hop interconnection scenarios where the originating\n and destination parties may not have a direct trusted relationship.\n\nStatus of This Memo\n\n This is an 8225 algorithm encryption http https key license signature subject trust nested-reference unchanged"},{"id":"IETF RFC 8226","type":"specification","body":"IETF","designation":"RFC 8226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8226.txt","https://www.rfc-editor.org/rfc/rfc8226.pdf"],"folder":"IETF/RFC-8226","files":{"txt":{"path":"standards/IETF/RFC-8226/RFC-8226.txt","sha256":"e8260e0c41e3ffba9076d1182538ccc5598caa2468b5669cd9b850ff83282f51"}},"tags":["nested-reference","unchanged"],"summary":"In order to prevent the impersonation of telephone numbers on the\n Internet, some kind of credential system needs to exist that\n cryptographically asserts authority over telephone numbers. This\n document describes the use of certificates in establishing authority\n over telephone numbers, as a component of a broader architecture for\n managing telephone numbers as identities in protocols like SIP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on ","scope_keywords":["8226","attribute","attributes","authentication","authorization","certificate","certificates","credential","credentials","http","https","key","keys","license","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 8226 In order to prevent the impersonation of telephone numbers on the\n Internet, some kind of credential system needs to exist that\n cryptographically asserts authority over telephone numbers. This\n document describes the use of certificates in establishing authority\n over telephone numbers, as a component of a broader architecture for\n managing telephone numbers as identities in protocols like SIP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on  8226 attribute attributes authentication authorization certificate certificates credential credentials http https key keys license revocation signature nested-reference unchanged"},{"id":"IETF RFC 8288","type":"specification","body":"IETF","designation":"RFC 8288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8288.txt","https://www.rfc-editor.org/rfc/rfc8288.pdf"],"folder":"IETF/RFC-8288","files":{"txt":{"path":"standards/IETF/RFC-8288/RFC-8288.txt","sha256":"820f624e0b0884af5c732e8087a65182452e49f2f49cd784ad7c30e16a4fc35d"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a model for the relationships between\n resources on the Web (\"links\") and the type of those relationships\n (\"link relation types\").\n\n It also defines the serialisation of such links in HTTP headers with\n the Link header field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8288.\n\nNottingham Standards Track [Page 1]\n\f\nRFC 8288 Web Linking October 2017\n\nCopyrig","scope_keywords":["8288","algorithm","algorithms","attribute","attributes","http","https","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null}],"search_text":"IETF RFC 8288 This specification defines a model for the relationships between\n resources on the Web (\"links\") and the type of those relationships\n (\"link relation types\").\n\n It also defines the serialisation of such links in HTTP headers with\n the Link header field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8288.\n\nNottingham Standards Track [Page 1]\n\f\nRFC 8288 Web Linking October 2017\n\nCopyrig 8288 algorithm algorithms attribute attributes http https key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8417","type":"specification","body":"IETF","designation":"RFC 8417","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8417.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8417.txt","https://www.rfc-editor.org/rfc/rfc8417.pdf"],"folder":"IETF/RFC-8417","files":{"txt":{"path":"standards/IETF/RFC-8417/RFC-8417.txt","sha256":"9ce7bf95b852f223a1c8c677d4c817b536f382a65ecc66bbe2b4f896a320d5c5"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the Security Event Token (SET) data\n structure. A SET describes statements of fact from the perspective\n of an issuer about a subject. These statements of fact represent an\n event that occurred directly to or about a security subject, for\n example, a statement about the issuance or revocation of a token on\n behalf of a subject. This specification is intended to enable\n representing security- and identity-related events. A SET is a JSON\n Web Token (JWT), which can be optionally signed and/or encrypted.\n SETs can be distributed via protocols such as HTTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IE","scope_keywords":["8417","delivery","encryption","http","https","issuer","license","profile","profiles","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null}],"search_text":"IETF RFC 8417 This specification defines the Security Event Token (SET) data\n structure. A SET describes statements of fact from the perspective\n of an issuer about a subject. These statements of fact represent an\n event that occurred directly to or about a security subject, for\n example, a statement about the issuance or revocation of a token on\n behalf of a subject. This specification is intended to enable\n representing security- and identity-related events. A SET is a JSON\n Web Token (JWT), which can be optionally signed and/or encrypted.\n SETs can be distributed via protocols such as HTTP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IE 8417 delivery encryption http https issuer license profile profiles revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 9068","type":"specification","body":"IETF","designation":"RFC 9068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9068.txt","https://www.rfc-editor.org/rfc/rfc9068.pdf"],"folder":"IETF/RFC-9068","files":{"pdf":{"path":"standards/IETF/RFC-9068/RFC-9068.pdf","sha256":"9c19b25210d0fb6a230d8e737dc6561f7f8b1bf20db4f615229176eca51d0fc2"},"txt":{"path":"standards/IETF/RFC-9068/RFC-9068.txt","sha256":"68d3ff3910c0f2340fd7b93b430e00053da845b6eebe095ebef0c8bfda5e14c5"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a profile for issuing OAuth 2.0 access\n tokens in JSON Web Token (JWT) format. Authorization servers and\n resource servers from different vendors can leverage this profile to\n issue and consume access tokens in an interoperable manner.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9068.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identi","scope_keywords":["9068","algorithm","algorithms","authentication","authorization","http","https","key","license","profile","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 9068 This specification defines a profile for issuing OAuth 2.0 access\n tokens in JSON Web Token (JWT) format. Authorization servers and\n resource servers from different vendors can leverage this profile to\n issue and consume access tokens in an interoperable manner.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9068.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identi 9068 algorithm algorithms authentication authorization http https key license profile signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 9101","type":"specification","body":"IETF","designation":"RFC 9101","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9101.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9101.txt","https://www.rfc-editor.org/rfc/rfc9101.pdf"],"folder":"IETF/RFC-9101","files":{"pdf":{"path":"standards/IETF/RFC-9101/RFC-9101.pdf","sha256":"4d7cbcc7959549c23e6bdd2a17e3b8ccd175660ef64d68be55865b4ec60e489e"},"txt":{"path":"standards/IETF/RFC-9101/RFC-9101.txt","sha256":"a1400b5b8d27cfabb127325458a88415f83bb04b2ff9e6facbe50b8ef4ea2b60"}},"tags":["nested-reference","unchanged"],"summary":"The authorization request in OAuth 2.0 described in RFC 6749 utilizes\n query parameter serialization, which means that authorization request\n parameters are encoded in the URI of the request and sent through\n user agents such as web browsers. While it is easy to implement, it\n means that a) the communication through the user agents is not\n integrity protected and thus, the parameters can be tainted, b) the\n source of the communication is not authenticated, and c) the\n communication through the user agents can be monitored. Because of\n these weaknesses, several attacks to the protocol have now been put\n forward.\n\n This document introduces the ability to send request parameters in a\n JSON Web Token (JWT) instead, which allows the request to be signed\n with JSON Web Signature (JWS) and encrypted with JSON Web Encryption\n (JWE) so that the integrity, source authentication, and\n confidentiali","scope_keywords":["9101","algorithm","algorithms","authentication","authorization","encryption","http","https","license","risk","signature","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 9101 The authorization request in OAuth 2.0 described in RFC 6749 utilizes\n query parameter serialization, which means that authorization request\n parameters are encoded in the URI of the request and sent through\n user agents such as web browsers. While it is easy to implement, it\n means that a) the communication through the user agents is not\n integrity protected and thus, the parameters can be tainted, b) the\n source of the communication is not authenticated, and c) the\n communication through the user agents can be monitored. Because of\n these weaknesses, several attacks to the protocol have now been put\n forward.\n\n This document introduces the ability to send request parameters in a\n JSON Web Token (JWT) instead, which allows the request to be signed\n with JSON Web Signature (JWS) and encrypted with JSON Web Encryption\n (JWE) so that the integrity, source authentication, and\n confidentiali 9101 algorithm algorithms authentication authorization encryption http https license risk signature subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9449","type":"specification","body":"IETF","designation":"RFC 9449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9449.txt","https://www.rfc-editor.org/rfc/rfc9449.pdf"],"folder":"IETF/RFC-9449","files":{"pdf":{"path":"standards/IETF/RFC-9449/RFC-9449.pdf","sha256":"7e2cd3cee8eac23309db119e723769bd391801db0479bffafe05c1285a10defd"},"txt":{"path":"standards/IETF/RFC-9449/RFC-9449.txt","sha256":"3842c58e1f6043389416023b9bb8d765048266024982fbbd90640e05943f4e13"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for sender-constraining OAuth 2.0\n tokens via a proof-of-possession mechanism on the application level.\n This mechanism allows for the detection of replay attacks with access\n and refresh tokens.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9449.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. ","scope_keywords":["9449","algorithm","algorithms","authentication","authorization","credential","credentials","hash","http","https","key","keys","license","signature","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9449 This document describes a mechanism for sender-constraining OAuth 2.0\n tokens via a proof-of-possession mechanism on the application level.\n This mechanism allows for the detection of replay attacks with access\n and refresh tokens.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9449.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors.  9449 algorithm algorithms authentication authorization credential credentials hash http https key keys license signature subject tls nested-reference unchanged"},{"id":"IETF RFC 9876","type":"specification","body":"IETF","designation":"RFC 9876","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9876.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9876.txt","https://www.rfc-editor.org/rfc/rfc9876.pdf"],"folder":"IETF/RFC-9876","files":{"pdf":{"path":"standards/IETF/RFC-9876/RFC-9876.pdf","sha256":"200311ac1048cb1dcb874dfd6fb97279015726fefded2ac863bb52b73ae8941a"},"txt":{"path":"standards/IETF/RFC-9876/RFC-9876.txt","sha256":"137ca2c2827b4a535386dcdd9e6d4c18f281f43f9b80bc59694c1b96e72c4ace"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 7252 by modifying the registration\n procedures for the \"CoAP Content-Formats\" IANA registry, within the\n \"Constrained RESTful Environments (CoRE) Parameters\" registry group.\n This document also introduces a new column, \"Media Type\", to the\n registry. Furthermore, this document reserves Content-Format\n identifiers 64998 and 64999 for use in documentation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain","scope_keywords":["9876","http","https","key","license","registered","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9876 This document updates RFC 7252 by modifying the registration\n procedures for the \"CoAP Content-Formats\" IANA registry, within the\n \"Constrained RESTful Environments (CoRE) Parameters\" registry group.\n This document also introduces a new column, \"Media Type\", to the\n registry. Furthermore, this document reserves Content-Format\n identifiers 64998 and 64999 for use in documentation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain 9876 http https key license registered risk subject trust nested-reference unchanged"},{"id":"IETF SD-JWT","type":"specification","body":"IETF","designation":"SD-JWT","version":null,"title":"Selective Disclosure for JWTs (RFC 9901)","purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9901.txt","https://www.rfc-editor.org/rfc/rfc9901.pdf"],"folder":"IETF/SD-JWT","files":{"pdf":{"path":"standards/IETF/SD-JWT/SD-JWT.pdf","sha256":"13dcdb9e1a2cf9036af52947fd546044b1d4ae5af0e81c18624951dda7ab5463"},"txt":{"path":"standards/IETF/SD-JWT/SD-JWT.txt","sha256":"fd4cb79184162fa7ef95f4f63abab8ee6d03c9a04c19b8f83758946464b284eb"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification defines a mechanism for the selective disclosure\n of individual elements of a JSON data structure used as the payload\n of a JSON Web Signature (JWS). The primary use case is the selective\n disclosure of JSON Web Token (JWT) claims.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9901.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified as the\n","scope_keywords":["jwt","algorithm","credential","credentials","hash","hashing","holder","http","https","issuer","key","license","management","presentation","signature","signatures"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS13","folder":"ARF/TS13","source":"ARF/TS13/TS13-V1.0.1.md","version":null},{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF SD-JWT Selective Disclosure for JWTs (RFC 9901) This specification defines a mechanism for the selective disclosure\n of individual elements of a JSON data structure used as the payload\n of a JSON Web Signature (JWS). The primary use case is the selective\n disclosure of JSON Web Token (JWT) claims.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9901.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified as the\n jwt algorithm credential credentials hash hashing holder http https issuer key license management presentation signature signatures cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 4356","type":"specification","body":"IETF","designation":"RFC 4356","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4356.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4356.txt","https://www.rfc-editor.org/rfc/rfc4356.pdf"],"folder":"IETF/RFC-4356","files":{"txt":{"path":"standards/IETF/RFC-4356/RFC-4356.txt","sha256":"b95fa1e320676cc6794b30ab046b617d5c31953ca0fabc68a203de9749ec49ce"}},"tags":["nested-reference","unchanged"],"summary":"The cellular telephone industry has defined a service known as the\n Multimedia Messaging Service (MMS). This service uses formats and\n protocols that are similar to, but differ in key ways from, those\n used in Internet mail.\n\n One important difference between MMS and Internet Mail is that MMS\n uses headers that start with \"X-Mms-\" to carry a variety of user\n agent- and server-related information elements.\n\n This document specifies how to exchange messages between these two\n services, including mapping information elements as used in MMS\n X-Mms-* headers as well as delivery and disposition reports, to and\n from that used in SMTP and Internet message headers.\n\nGellens Standards Track [Page 1]\n\f\nRFC 4356 Mapping Between MMS and Internet Mail January 2006","scope_keywords":["4356","delivery","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 4356 The cellular telephone industry has defined a service known as the\n Multimedia Messaging Service (MMS). This service uses formats and\n protocols that are similar to, but differ in key ways from, those\n used in Internet mail.\n\n One important difference between MMS and Internet Mail is that MMS\n uses headers that start with \"X-Mms-\" to carry a variety of user\n agent- and server-related information elements.\n\n This document specifies how to exchange messages between these two\n services, including mapping information elements as used in MMS\n X-Mms-* headers as well as delivery and disposition reports, to and\n from that used in SMTP and Internet message headers.\n\nGellens Standards Track [Page 1]\n\f\nRFC 4356 Mapping Between MMS and Internet Mail January 2006 4356 delivery key profile nested-reference unchanged"},{"id":"IETF RFC 5259","type":"specification","body":"IETF","designation":"RFC 5259","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5259.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5259.txt","https://www.rfc-editor.org/rfc/rfc5259.pdf"],"folder":"IETF/RFC-5259","files":{"txt":{"path":"standards/IETF/RFC-5259/RFC-5259.txt","sha256":"9da13b1a5697dba8e99a5a71d9a5b4c091064b16a1d37f7c27b1cbd1be42ec17"}},"tags":["nested-reference","unchanged"],"summary":"CONVERT defines extensions to IMAP allowing clients to request\n adaptation and/or transcoding of attachments. Clients can specify\n the conversion details or allow servers to decide based on knowledge\n of client capabilities, on user or administrator preferences, or on\n server settings.\n\nMelnikov & Coates Standards Track [Page 1]\n\f\nRFC 5259 IMAP CONVERT extension July 2008","scope_keywords":["5259","key","registered","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null}],"search_text":"IETF RFC 5259 CONVERT defines extensions to IMAP allowing clients to request\n adaptation and/or transcoding of attachments. Clients can specify\n the conversion details or allow servers to decide based on knowledge\n of client capabilities, on user or administrator preferences, or on\n server settings.\n\nMelnikov & Coates Standards Track [Page 1]\n\f\nRFC 5259 IMAP CONVERT extension July 2008 5259 key registered signature signatures nested-reference unchanged"},{"id":"IETF RFC 5293","type":"specification","body":"IETF","designation":"RFC 5293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5293.txt","https://www.rfc-editor.org/rfc/rfc5293.pdf"],"folder":"IETF/RFC-5293","files":{"txt":{"path":"standards/IETF/RFC-5293/RFC-5293.txt","sha256":"cd39f86d3c7d7fbdf6997776b55387539ef61efb7587f7abd4e269c66cf58f37"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new actions for the \"Sieve\" email filtering\n language that add and delete email header fields.\n\n1. Introduction\n\n Email header fields are a flexible and easy-to-understand means of\n communication between email processors. This extension enables sieve\n scripts to interact with other components that consume or produce\n header fields by allowing the script to delete and add header fields.\n\n2. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [KEYWORDS].\n\n Conventions for notations are as in Section 1.1 of [SIEVE], including\n use of the \"Usage:\" label for the definition of action and tagged\n arguments syntax.\n\n The term \"header field\" is used here as in [IMAIL] to mean a logical\n line of an email ","scope_keywords":["5293","crl","key","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5293 This document defines two new actions for the \"Sieve\" email filtering\n language that add and delete email header fields.\n\n1. Introduction\n\n Email header fields are a flexible and easy-to-understand means of\n communication between email processors. This extension enables sieve\n scripts to interact with other components that consume or produce\n header fields by allowing the script to delete and add header fields.\n\n2. Conventions Used in This Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [KEYWORDS].\n\n Conventions for notations are as in Section 1.1 of [SIEVE], including\n use of the \"Usage:\" label for the definition of action and tagged\n arguments syntax.\n\n The term \"header field\" is used here as in [IMAIL] to mean a logical\n line of an email  5293 crl key policy subject nested-reference unchanged"},{"id":"IETF RFC 7234","type":"specification","body":"IETF","designation":"RFC 7234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7234.txt","https://www.rfc-editor.org/rfc/rfc7234.pdf"],"folder":"IETF/RFC-7234","files":{"txt":{"path":"standards/IETF/RFC-7234/RFC-7234.txt","sha256":"1d084238ae6692d1e3322fa0850dbb9596812332d92b76d9a815c5ed9b600dea"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP caches and the associated header\n fields that control cache behavior or indicate cacheable response\n messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7234.\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 72","scope_keywords":["7234","http","key","keys","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8246","folder":"IETF/RFC-8246","source":"IETF/RFC-8246/RFC-8246.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 7234 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP caches and the associated header\n fields that control cache behavior or indicate cacheable response\n messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7234.\n\nFielding, et al. Standards Track [Page 1]\n\f\nRFC 72 7234 http key keys license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 3362","type":"specification","body":"IETF","designation":"RFC 3362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3362.txt","https://www.rfc-editor.org/rfc/rfc3362.pdf"],"folder":"IETF/RFC-3362","files":{"txt":{"path":"standards/IETF/RFC-3362/RFC-3362.txt","sha256":"65cdb1a67b2b864b69950de8eb013f8186dea944a06be838145bf7d16b3109d4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of the MIME sub-type\n image/t38. The encoding is defined by ITU Recommendation T.38 and is\n intended for use as an Session Description Protocol (SDP) media\n descriptor.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/t38. The encoding is defined by [T.38] and is intended for use\n as an SDP media descriptor.\n\n3. T.38 Definition\n\n ITU-T Recommendation T.38 [T.38] describes the technical features\n necessary to transfer facsimile documents in real-time between two\n standard Group 3 facsimile terminals over the Internet or other\n networks using IP protocols. The Recommen","scope_keywords":["3362","http","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null}],"search_text":"IETF RFC 3362 This document describes the registration of the MIME sub-type\n image/t38. The encoding is defined by ITU Recommendation T.38 and is\n intended for use as an Session Description Protocol (SDP) media\n descriptor.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [REQ].\n\n2. Overview\n\n This document describes the registration of the MIME sub-type\n image/t38. The encoding is defined by [T.38] and is intended for use\n as an SDP media descriptor.\n\n3. T.38 Definition\n\n ITU-T Recommendation T.38 [T.38] describes the technical features\n necessary to transfer facsimile documents in real-time between two\n standard Group 3 facsimile terminals over the Internet or other\n networks using IP protocols. The Recommen 3362 http key subject nested-reference unchanged"},{"id":"IETF RFC 3405","type":"specification","body":"IETF","designation":"RFC 3405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3405.txt","https://www.rfc-editor.org/rfc/rfc3405.pdf"],"folder":"IETF/RFC-3405","files":{"txt":{"path":"standards/IETF/RFC-3405/RFC-3405.txt","sha256":"948b47bce431014c1cf10f6641dae148e82a6eab11b15af181b0e516c2dd189f"}},"tags":["nested-reference","unchanged"],"summary":"This document is fifth in a series that is completely specified in\n \"Dynamic Delegation Discovery System (DDDS) Part One: The\n Comprehensive DDDS\" (RFC 3401). It is very important to note that it\n is impossible to read and understand any document in this series\n without reading the others.","scope_keywords":["3405","algorithm","holder","http","key","policies","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3401","folder":"IETF/RFC-3401","source":"IETF/RFC-3401/RFC-3401.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null}],"search_text":"IETF RFC 3405 This document is fifth in a series that is completely specified in\n \"Dynamic Delegation Discovery System (DDDS) Part One: The\n Comprehensive DDDS\" (RFC 3401). It is very important to note that it\n is impossible to read and understand any document in this series\n without reading the others. 3405 algorithm holder http key policies registered nested-reference unchanged"},{"id":"IETF RFC 3640","type":"specification","body":"IETF","designation":"RFC 3640","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3640.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3640.txt","https://www.rfc-editor.org/rfc/rfc3640.pdf"],"folder":"IETF/RFC-3640","files":{"txt":{"path":"standards/IETF/RFC-3640/RFC-3640.txt","sha256":"64ad95a0c3aca15d835f3caa82c26c4e695b420e00fa32dadf6f8951ff7a4059"}},"tags":["nested-reference","unchanged"],"summary":"The Motion Picture Experts Group (MPEG) Committee (ISO/IEC JTC1/SC29\n WG11) is a working group in ISO that produced the MPEG-4 standard.\n MPEG defines tools to compress content such as audio-visual\n information into elementary streams. This specification defines a\n simple, but generic RTP payload format for transport of any non-\n multiplexed MPEG-4 elementary stream.","scope_keywords":["3640","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 3640 The Motion Picture Experts Group (MPEG) Committee (ISO/IEC JTC1/SC29\n WG11) is a working group in ISO that produced the MPEG-4 standard.\n MPEG defines tools to compress content such as audio-visual\n information into elementary streams. This specification defines a\n simple, but generic RTP payload format for transport of any non-\n multiplexed MPEG-4 elementary stream. 3640 key management nested-reference unchanged"},{"id":"IETF RFC 3778","type":"specification","body":"IETF","designation":"RFC 3778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3778.txt","https://www.rfc-editor.org/rfc/rfc3778.pdf"],"folder":"IETF/RFC-3778","files":{"txt":{"path":"standards/IETF/RFC-3778/RFC-3778.txt","sha256":"abdbbe16df556e0938449d6fc40a7178652524998ad78710030f1666bb39a447"}},"tags":["nested-reference","unchanged"],"summary":"PDF, the 'Portable Document Format', is a general document\n representation language that has been in use for document exchange on\n the Internet since 1993. This document provides an overview of the\n PDF format, explains the mechanisms for digital signatures and\n encryption within PDF files, and updates the media type registration\n of 'application/pdf'.","scope_keywords":["3778","encryption","http","key","management","presentation","preservation","profile","registered","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"IETF RFC 3778 PDF, the 'Portable Document Format', is a general document\n representation language that has been in use for document exchange on\n the Internet since 1993. This document provides an overview of the\n PDF format, explains the mechanisms for digital signatures and\n encryption within PDF files, and updates the media type registration\n of 'application/pdf'. 3778 encryption http key management presentation preservation profile registered signature signatures nested-reference unchanged"},{"id":"IETF RFC 4145","type":"specification","body":"IETF","designation":"RFC 4145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4145.txt","https://www.rfc-editor.org/rfc/rfc4145.pdf"],"folder":"IETF/RFC-4145","files":{"txt":{"path":"standards/IETF/RFC-4145/RFC-4145.txt","sha256":"8901b7e981d259943af3dff406cafe053f8d0b94a9553a7d8b0d2aaba9e0c625"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to express media transport over TCP using\n the Session Description Protocol (SDP). It defines the SDP 'TCP'\n protocol identifier, the SDP 'setup' attribute, which describes the\n connection setup procedure, and the SDP 'connection' attribute, which\n handles connection reestablishment.\n\nYon & Camarillo Standards Track [Page 1]\n\f\nRFC 4145 Connection-Oriented Media September 2005","scope_keywords":["4145","attribute","attributes","crl","http","key","management","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4145 This document describes how to express media transport over TCP using\n the Session Description Protocol (SDP). It defines the SDP 'TCP'\n protocol identifier, the SDP 'setup' attribute, which describes the\n connection setup procedure, and the SDP 'connection' attribute, which\n handles connection reestablishment.\n\nYon & Camarillo Standards Track [Page 1]\n\f\nRFC 4145 Connection-Oriented Media September 2005 4145 attribute attributes crl http key management tsp nested-reference unchanged"},{"id":"IETF RFC 2051","type":"specification","body":"IETF","designation":"RFC 2051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2051.txt","https://www.rfc-editor.org/rfc/rfc2051.pdf"],"folder":"IETF/RFC-2051","files":{"txt":{"path":"standards/IETF/RFC-2051/RFC-2051.txt","sha256":"8274a14bc5d08120a062c8eae2ac0fab759d985455e40a9b8ae497988879635e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Allen\nRequest for Comments: 2051 Wall Data Inc.\nCategory: Standards Track B. Clouston\n Z. Kielczewski\n Cisco Systems\n W. Kwan\n Jupiter Technology Inc.\n B. Moore\n IBM\n October 1996\n\n Definitions of Managed Objects for APPC using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ........................................... 1\n 2. The SNMP Network Management Framework .................. 1\n 3. Overview ............................................... 2\n 3.1 APPC MIB structure ...................................... 4\n 4. ","scope_keywords":["2051","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2051 Network Working Group M. Allen\nRequest for Comments: 2051 Wall Data Inc.\nCategory: Standards Track B. Clouston\n Z. Kielczewski\n Cisco Systems\n W. Kwan\n Jupiter Technology Inc.\n B. Moore\n IBM\n October 1996\n\n Definitions of Managed Objects for APPC using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction ........................................... 1\n 2. The SNMP Network Management Framework .................. 1\n 3. Overview ............................................... 2\n 3.1 APPC MIB structure ...................................... 4\n 4.  2051 management nested-reference unchanged"},{"id":"IETF RFC 3104","type":"specification","body":"IETF","designation":"RFC 3104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3104.txt","https://www.rfc-editor.org/rfc/rfc3104.pdf"],"folder":"IETF/RFC-3104","files":{"txt":{"path":"standards/IETF/RFC-3104/RFC-3104.txt","sha256":"9ab0ff06553b09fff40324a27ba034f5f8a519843939626d4f6c429ea525c140"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes mechanisms that enable Realm Specific IP\n (RSIP) to handle end-to-end IPsec (IP Security).\n\nMontenegro & Borella Experimental [Page 1]\n\f\nRFC 3104 RSIP Support for End-to-end IPsec October 2001","scope_keywords":["3104","authentication","encryption","identification","key","keys","policy","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null}],"search_text":"IETF RFC 3104 This document proposes mechanisms that enable Realm Specific IP\n (RSIP) to handle end-to-end IPsec (IP Security).\n\nMontenegro & Borella Experimental [Page 1]\n\f\nRFC 3104 RSIP Support for End-to-end IPsec October 2001 3104 authentication encryption identification key keys policy signature signatures nested-reference unchanged"},{"id":"IETF RFC 3105","type":"specification","body":"IETF","designation":"RFC 3105","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3105.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3105.txt","https://www.rfc-editor.org/rfc/rfc3105.pdf"],"folder":"IETF/RFC-3105","files":{"txt":{"path":"standards/IETF/RFC-3105/RFC-3105.txt","sha256":"d598804042240bd85bb5ead95e5e713cd0b185c4d452a47de86fc1d4a030cbae"}},"tags":["nested-reference","unchanged"],"summary":"This document contains an SLP service type template that describes\n the advertisements made by RSIP servers for their services. Service\n Location Protocol (SLP) is an IETF standards track protocol\n specifically designed to allow clients to find servers offering\n particular services. Since RSIP (Realm Specific IP) clients require\n a mechanism to discover RSIP servers, SLP is a natural match for a\n solution. The service type template is the basis for an Internet\n Assigned Numbers Authority (IANA) standard definition of the\n advertisements offered by RSIP servers, an important step toward\n interoperability.\n\nKempf & Montenegro Experimental [Page 1]\n\f\nRFC 3105 Finding an RSIP Server with SLP October 2001","scope_keywords":["3105","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null}],"search_text":"IETF RFC 3105 This document contains an SLP service type template that describes\n the advertisements made by RSIP servers for their services. Service\n Location Protocol (SLP) is an IETF standards track protocol\n specifically designed to allow clients to find servers offering\n particular services. Since RSIP (Realm Specific IP) clients require\n a mechanism to discover RSIP servers, SLP is a natural match for a\n solution. The service type template is the basis for an Internet\n Assigned Numbers Authority (IANA) standard definition of the\n advertisements offered by RSIP servers, an important step toward\n interoperability.\n\nKempf & Montenegro Experimental [Page 1]\n\f\nRFC 3105 Finding an RSIP Server with SLP October 2001 3105 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 206","type":"specification","body":"IETF","designation":"RFC 206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc206.txt","https://www.rfc-editor.org/rfc/rfc206.pdf"],"folder":"IETF/RFC-206","files":{"pdf":{"path":"standards/IETF/RFC-206/RFC-206.pdf","sha256":"16f57afc391bde545af3e7df6015630aac71f5262b102291233a146a91d0656b"},"txt":{"path":"standards/IETF/RFC-206/RFC-206.txt","sha256":"318d4587f642ea857268939c1ff710e0a50efb1d8e4542d174316a8b074902fe"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. White\nRequest for Comments: 206 Computer Research Lab, UCSB\nNIC: 7176 9 August 1971\n\n A User TELNET\n Description of an Initial Implementation\n\nPREFACE\n\n The User TELNET described in this document has been implemented\n within UCSB's Online System by Mark Krilanovich and makes teletype-\n compatible time-sharing systems in the Net accessible to Online\n System users.\n\nContents\n\n Page\n I. Function................................................... 1\n II. Invoking TELNET............................................ 2\n III. The Virtual Teletype....................................... 5\n IV. Returning to TELNET........................................ 11\n V. Breaking TELNET Connections................................ 12\n VI. Abnormal Network Conditions................................ 12\n\nFIGURES\n\n Page\n Figure 1. Network Sites........................................ 4\n Figu","scope_keywords":["206","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 216","folder":"IETF/RFC-216","source":"IETF/RFC-216/RFC-216.txt","version":null}],"search_text":"IETF RFC 206 Network Working Group J. White\nRequest for Comments: 206 Computer Research Lab, UCSB\nNIC: 7176 9 August 1971\n\n A User TELNET\n Description of an Initial Implementation\n\nPREFACE\n\n The User TELNET described in this document has been implemented\n within UCSB's Online System by Mark Krilanovich and makes teletype-\n compatible time-sharing systems in the Net accessible to Online\n System users.\n\nContents\n\n Page\n I. Function................................................... 1\n II. Invoking TELNET............................................ 2\n III. The Virtual Teletype....................................... 5\n IV. Returning to TELNET........................................ 11\n V. Breaking TELNET Connections................................ 12\n VI. Abnormal Network Conditions................................ 12\n\nFIGURES\n\n Page\n Figure 1. Network Sites........................................ 4\n Figu 206 key keys nested-reference unchanged"},{"id":"IETF RFC 2177","type":"specification","body":"IETF","designation":"RFC 2177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2177.txt","https://www.rfc-editor.org/rfc/rfc2177.pdf"],"folder":"IETF/RFC-2177","files":{"txt":{"path":"standards/IETF/RFC-2177/RFC-2177.txt","sha256":"600c02aeddb4dc47618700797b2293115d077404ce1781990fdad1a88597d8d2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Leiba\nRequest for Comments: 2177 IBM T.J. Watson Research Center\nCategory: Standards Track June 1997\n\n IMAP4 IDLE command\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Internet Message Access Protocol [IMAP4] requires a client to\n poll the server for changes to the selected mailbox (new mail,\n deletions). It's often more desirable to have the server transmit\n updates to the client in real time. This allows a user to see new\n mail immediately. It also helps some real-time applications based on\n IMAP, which might otherwise need to poll","scope_keywords":["2177","crl","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2177 Network Working Group B. Leiba\nRequest for Comments: 2177 IBM T.J. Watson Research Center\nCategory: Standards Track June 1997\n\n IMAP4 IDLE command\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Internet Message Access Protocol [IMAP4] requires a client to\n poll the server for changes to the selected mailbox (new mail,\n deletions). It's often more desirable to have the server transmit\n updates to the client in real time. This allows a user to see new\n mail immediately. It also helps some real-time applications based on\n IMAP, which might otherwise need to poll 2177 crl key subject nested-reference unchanged"},{"id":"IETF RFC 2180","type":"specification","body":"IETF","designation":"RFC 2180","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2180.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2180.txt","https://www.rfc-editor.org/rfc/rfc2180.pdf"],"folder":"IETF/RFC-2180","files":{"txt":{"path":"standards/IETF/RFC-2180/RFC-2180.txt","sha256":"191a94f85a909e14d987eebd051684e2e7fec0074bcb0f9111891067d8af4ccd"}},"tags":["nested-reference","unchanged"],"summary":"IMAP4[RFC-2060] is rich client/server protocol that allows a client\n to access and manipulate electronic mail messages on a server.\n Within the protocol framework, it is possible to have differing\n results for particular client/server interactions. If a protocol does\n not allow for this, it is often unduly restrictive.\n\n For example, when multiple clients are accessing a mailbox and one\n attempts to delete the mailbox, an IMAP4 server may choose to\n implement a solution based upon server architectural constraints or\n individual preference.\n\n With this flexibility comes greater client responsibility. It is not\n sufficient for a client to be written based upon the behavior of a\n particular IMAP server. Rather the client must be based upon the\n behavior allowed by the protocol.\n\n By documenting common IMAP4 server practice for the case of\n simultaneous client access to a mailbox, we hope to","scope_keywords":["2180","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2180 IMAP4[RFC-2060] is rich client/server protocol that allows a client\n to access and manipulate electronic mail messages on a server.\n Within the protocol framework, it is possible to have differing\n results for particular client/server interactions. If a protocol does\n not allow for this, it is often unduly restrictive.\n\n For example, when multiple clients are accessing a mailbox and one\n attempts to delete the mailbox, an IMAP4 server may choose to\n implement a solution based upon server architectural constraints or\n individual preference.\n\n With this flexibility comes greater client responsibility. It is not\n sufficient for a client to be written based upon the behavior of a\n particular IMAP server. Rather the client must be based upon the\n behavior allowed by the protocol.\n\n By documenting common IMAP4 server practice for the case of\n simultaneous client access to a mailbox, we hope to 2180 attribute key nested-reference unchanged"},{"id":"IETF RFC 2245","type":"specification","body":"IETF","designation":"RFC 2245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2245.txt","https://www.rfc-editor.org/rfc/rfc2245.pdf"],"folder":"IETF/RFC-2245","files":{"txt":{"path":"standards/IETF/RFC-2245/RFC-2245.txt","sha256":"37eb6177a1ac3d6ce82e03087e321e49e13247867b01588dfa4d95107cac6d3c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Newman\nRequest for Comments: 2245 Innosoft\nCategory: Standards Track November 1997\n\n Anonymous SASL Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n It is common practice on the Internet to permit anonymous access to\n various services. Traditionally, this has been done with a plain\n text password mechanism using \"anonymous\" as the user name and\n optional trace information, such as an email address, as the\n password. As plaintext login commands are not","scope_keywords":["2245","encryption","identification","key","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null}],"search_text":"IETF RFC 2245 Network Working Group C. Newman\nRequest for Comments: 2245 Innosoft\nCategory: Standards Track November 1997\n\n Anonymous SASL Mechanism\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n It is common practice on the Internet to permit anonymous access to\n various services. Traditionally, this has been done with a plain\n text password mechanism using \"anonymous\" as the user name and\n optional trace information, such as an email address, as the\n password. As plaintext login commands are not 2245 encryption identification key profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 2342","type":"specification","body":"IETF","designation":"RFC 2342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2342.txt","https://www.rfc-editor.org/rfc/rfc2342.pdf"],"folder":"IETF/RFC-2342","files":{"txt":{"path":"standards/IETF/RFC-2342/RFC-2342.txt","sha256":"6023278a88e94a0b1a530b1e7a14a37e89699b07d7ba65e3bfe45dd276d56aab"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Gahrns\nRequest for Comments: 2342 Microsoft\nCategory: Standards Track C. Newman\n Innosoft\n May 1998\n\n IMAP4 Namespace\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n IMAP4 [RFC-2060] does not define a default server namespace. As a\n result, two common namespace models have evolved:\n\n The \"Personal Mailbox\" model, in which the default namespace that is\n presented consists of only the user's personal mailboxes. To access\n shared mailboxes, the user must use a","scope_keywords":["2342","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 2342 Network Working Group M. Gahrns\nRequest for Comments: 2342 Microsoft\nCategory: Standards Track C. Newman\n Innosoft\n May 1998\n\n IMAP4 Namespace\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n IMAP4 [RFC-2060] does not define a default server namespace. As a\n result, two common namespace models have evolved:\n\n The \"Personal Mailbox\" model, in which the default namespace that is\n presented consists of only the user's personal mailboxes. To access\n shared mailboxes, the user must use a 2342 key nested-reference unchanged"},{"id":"IETF RFC 2359","type":"specification","body":"IETF","designation":"RFC 2359","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2359.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2359.txt","https://www.rfc-editor.org/rfc/rfc2359.pdf"],"folder":"IETF/RFC-2359","files":{"txt":{"path":"standards/IETF/RFC-2359/RFC-2359.txt","sha256":"f474ef4b601160f13f02b2aa52ff12bc8cb49d35399ed97985e110083c7b2f11"}},"tags":["nested-reference","unchanged"],"summary":"The UIDPLUS extension of the Internet Message Access Protocol [IMAP4]\n provides a set of features intended to reduce the amount of time and\n resources used by some client operations. The features in UIDPLUS\n are primarily intended for disconnected-use clients.\n\n2. Conventions Used in this Document\n\n In examples, \"C:\" and \"S:\" indicate lines sent by the client and\n server respectively.\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document are to be interpreted as defined in \"Key words for\n use in RFCs to Indicate Requirement Levels\" [KEYWORDS].\n\n3. Introduction and Overview\n\n The UIDPLUS extension is present in any IMAP4 server implementation\n which returns \"UIDPLUS\" as one of the supported capabilities to the\n CAPABILITY command. The UIDPLUS extension contains one additional\n command and additional data returned with successful APPEND and COPY\n commands.","scope_keywords":["2359","key","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4315","folder":"IETF/RFC-4315","source":"IETF/RFC-4315/RFC-4315.txt","version":null}],"search_text":"IETF RFC 2359 The UIDPLUS extension of the Internet Message Access Protocol [IMAP4]\n provides a set of features intended to reduce the amount of time and\n resources used by some client operations. The features in UIDPLUS\n are primarily intended for disconnected-use clients.\n\n2. Conventions Used in this Document\n\n In examples, \"C:\" and \"S:\" indicate lines sent by the client and\n server respectively.\n\n The key words \"MUST\", \"MUST NOT\", \"SHOULD\", \"SHOULD NOT\", and \"MAY\"\n in this document are to be interpreted as defined in \"Key words for\n use in RFCs to Indicate Requirement Levels\" [KEYWORDS].\n\n3. Introduction and Overview\n\n The UIDPLUS extension is present in any IMAP4 server implementation\n which returns \"UIDPLUS\" as one of the supported capabilities to the\n CAPABILITY command. The UIDPLUS extension contains one additional\n command and additional data returned with successful APPEND and COPY\n commands. 2359 key risk subject nested-reference unchanged"},{"id":"IETF RFC 2971","type":"specification","body":"IETF","designation":"RFC 2971","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2971.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2971.txt","https://www.rfc-editor.org/rfc/rfc2971.pdf"],"folder":"IETF/RFC-2971","files":{"txt":{"path":"standards/IETF/RFC-2971/RFC-2971.txt","sha256":"e951146a2ad39f55a6507fa6616edc101fa4a1ab3ff4c6a9b86a4de7eb019dac"}},"tags":["nested-reference","unchanged"],"summary":"The ID extension to the Internet Message Access Protocol - Version\n 4rev1 (IMAP4rev1) protocol allows the server and client to exchange\n identification information on their implementation in order to make\n bug reports and usage statistics more complete.\n\n1. Introduction\n\n The IMAP4rev1 protocol described in [IMAP4rev1] provides a method for\n accessing remote mail stores, but it provides no facility to\n advertise what program a client or server uses to provide service.\n This makes it difficult for implementors to get complete bug reports\n from users, as it is frequently difficult to know what client or\n server is in use.\n\n Additionally, some sites may wish to assemble usage statistics based\n on what clients are used, but in an an environment where users are\n permitted to obtain and maintain their own clients this is difficult\n to accomplish.\n\n The ID command provides a facility to adverti","scope_keywords":["2971","authorization","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2971 The ID extension to the Internet Message Access Protocol - Version\n 4rev1 (IMAP4rev1) protocol allows the server and client to exchange\n identification information on their implementation in order to make\n bug reports and usage statistics more complete.\n\n1. Introduction\n\n The IMAP4rev1 protocol described in [IMAP4rev1] provides a method for\n accessing remote mail stores, but it provides no facility to\n advertise what program a client or server uses to provide service.\n This makes it difficult for implementors to get complete bug reports\n from users, as it is frequently difficult to know what client or\n server is in use.\n\n Additionally, some sites may wish to assemble usage statistics based\n on what clients are used, but in an an environment where users are\n permitted to obtain and maintain their own clients this is difficult\n to accomplish.\n\n The ID command provides a facility to adverti 2971 authorization identification key nested-reference unchanged"},{"id":"IETF RFC 3348","type":"specification","body":"IETF","designation":"RFC 3348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3348.txt","https://www.rfc-editor.org/rfc/rfc3348.pdf"],"folder":"IETF/RFC-3348","files":{"txt":{"path":"standards/IETF/RFC-3348/RFC-3348.txt","sha256":"2ffed2ac59b9f452cb5f9400234b65024f42083664af57797d4be663a31c6a58"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Gahrns\nRequest for Comments: 3348 R. Cheng\nCategory: Informational Microsoft\n July 2002\n\n The Internet Message Action Protocol (IMAP4)\n Child Mailbox Extension\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n The Internet Message Action Protocol (IMAP4) CHILDREN extension\n provides a mechanism for a client to efficiently determine if a\n particular mailbox has children, without issuing a LIST \"\" * or a\n LIST \"\" % for each mailbox.\n\n1. Conventions used in this document\n\n In examples, \"C:\" and \"S:\" indicate lines sent by the client and\n server respectively. If such lines are wrapped without a new \"C:\" or\n \"S:\" label, then the wrapping is for edi","scope_keywords":["3348","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3348 Network Working Group M. Gahrns\nRequest for Comments: 3348 R. Cheng\nCategory: Informational Microsoft\n July 2002\n\n The Internet Message Action Protocol (IMAP4)\n Child Mailbox Extension\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n The Internet Message Action Protocol (IMAP4) CHILDREN extension\n provides a mechanism for a client to efficiently determine if a\n particular mailbox has children, without issuing a LIST \"\" * or a\n LIST \"\" % for each mailbox.\n\n1. Conventions used in this document\n\n In examples, \"C:\" and \"S:\" indicate lines sent by the client and\n server respectively. If such lines are wrapped without a new \"C:\" or\n \"S:\" label, then the wrapping is for edi 3348 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 5530","type":"specification","body":"IETF","designation":"RFC 5530","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5530.txt","https://www.rfc-editor.org/rfc/rfc5530.pdf"],"folder":"IETF/RFC-5530","files":{"txt":{"path":"standards/IETF/RFC-5530/RFC-5530.txt","sha256":"682e69deaf88e79e3f6da73d985bf8b1325fa1d5ef4946033836a9ba07d54d3a"}},"tags":["nested-reference","unchanged"],"summary":"IMAP responses consist of a response type (OK, NO, BAD), an optional\n machine-readable response code, and a human-readable text.\n\n This document collects and documents a variety of machine-readable\n response codes, for better interoperation and error reporting.\n\nGulbrandsen Standards Track [Page 1]\n\f\nRFC 5530 IMAP Response Codes May 2009\n\n1. Introduction\n\n Section 7.1 of [RFC3501] defines a number of response codes that can\n help tell an IMAP client why a command failed. However, experience\n has shown that more codes are useful. For example, it is useful for\n a client to know that an authentication attempt failed because of a\n server problem as opposed to a password problem.\n\n Currently, many IMAP servers use English-language, human-readable\n text to describe these errors, and a few IMAP clients attempt to\n translate this text into the user's language.\n\n This document names a variety of ","scope_keywords":["5530","authentication","authorization","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5530 IMAP responses consist of a response type (OK, NO, BAD), an optional\n machine-readable response code, and a human-readable text.\n\n This document collects and documents a variety of machine-readable\n response codes, for better interoperation and error reporting.\n\nGulbrandsen Standards Track [Page 1]\n\f\nRFC 5530 IMAP Response Codes May 2009\n\n1. Introduction\n\n Section 7.1 of [RFC3501] defines a number of response codes that can\n help tell an IMAP client why a command failed. However, experience\n has shown that more codes are useful. For example, it is useful for\n a client to know that an authentication attempt failed because of a\n server problem as opposed to a password problem.\n\n Currently, many IMAP servers use English-language, human-readable\n text to describe these errors, and a few IMAP clients attempt to\n translate this text into the user's language.\n\n This document names a variety of  5530 authentication authorization http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 3755","type":"specification","body":"IETF","designation":"RFC 3755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3755.txt","https://www.rfc-editor.org/rfc/rfc3755.pdf"],"folder":"IETF/RFC-3755","files":{"txt":{"path":"standards/IETF/RFC-3755/RFC-3755.txt","sha256":"b8d4744c85c06ec7602a174d22bbfe506d437e95600ffef4bc7ad4fb8c92eeba"}},"tags":["nested-reference","unchanged"],"summary":"As the DNS Security (DNSSEC) specifications have evolved, the syntax\n and semantics of the DNSSEC resource records (RRs) have changed.\n Many deployed nameservers understand variants of these semantics.\n Dangerous interactions can occur when a resolver that understands an\n earlier version of these semantics queries an authoritative server\n that understands the new delegation signer semantics, including at\n least one failure scenario that will cause an unsecured zone to be\n unresolvable. This document changes the type codes and mnemonics of\n the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions.\n\n1. Introduction\n\n The DNSSEC protocol has been through many iterations whose syntax and\n semantics are not completely compatible. This has occurred as part\n of the ordinary process of proposing a protocol, implementing it,\n testing it in the increasingly complex and diverse environment of","scope_keywords":["3755","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3757","folder":"IETF/RFC-3757","source":"IETF/RFC-3757/RFC-3757.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null},{"body":"IETF","designation":"RFC 6014","folder":"IETF/RFC-6014","source":"IETF/RFC-6014/RFC-6014.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null}],"search_text":"IETF RFC 3755 As the DNS Security (DNSSEC) specifications have evolved, the syntax\n and semantics of the DNSSEC resource records (RRs) have changed.\n Many deployed nameservers understand variants of these semantics.\n Dangerous interactions can occur when a resolver that understands an\n earlier version of these semantics queries an authoritative server\n that understands the new delegation signer semantics, including at\n least one failure scenario that will cause an unsecured zone to be\n unresolvable. This document changes the type codes and mnemonics of\n the DNSSEC RRs (SIG, KEY, and NXT) to avoid those interactions.\n\n1. Introduction\n\n The DNSSEC protocol has been through many iterations whose syntax and\n semantics are not completely compatible. This has occurred as part\n of the ordinary process of proposing a protocol, implementing it,\n testing it in the increasingly complex and diverse environment of 3755 key risk nested-reference unchanged"},{"id":"IETF RFC 2109","type":"specification","body":"IETF","designation":"RFC 2109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2109.txt","https://www.rfc-editor.org/rfc/rfc2109.pdf"],"folder":"IETF/RFC-2109","files":{"txt":{"path":"standards/IETF/RFC-2109/RFC-2109.txt","sha256":"6a0dc2d1529ef35638143ab60c1f15bac3913a7cf1aac202059a25e41eb741fd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a way to create a stateful session with HTTP\n requests and responses. It describes two new headers, Cookie and\n Set-Cookie, which carry state information between participating\n origin servers and user agents. The method described here differs\n from Netscape's Cookie proposal, but it can interoperate with\n HTTP/1.0 user agents that use Netscape's method. (See the HISTORICAL\n section.)\n\n2. TERMINOLOGY\n\n The terms user agent, client, server, proxy, and origin server have\n the same meaning as in the HTTP/1.0 specification.\n\n Fully-qualified host name (FQHN) means either the fully-qualified\n domain name (FQDN) of a host (i.e., a completely specified domain\n name ending in a top-level domain such as .com or .uk), or the\n numeric Internet Protocol (IP) address of a host. The fully\n qualified domain name is preferred; use of numeric IP addresses is\n strongly discouraged.\n","scope_keywords":["2109","attribute","attributes","http","key","management","path","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2458","folder":"IETF/RFC-2458","source":"IETF/RFC-2458/RFC-2458.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2965","folder":"IETF/RFC-2965","source":"IETF/RFC-2965/RFC-2965.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null}],"search_text":"IETF RFC 2109 This document specifies a way to create a stateful session with HTTP\n requests and responses. It describes two new headers, Cookie and\n Set-Cookie, which carry state information between participating\n origin servers and user agents. The method described here differs\n from Netscape's Cookie proposal, but it can interoperate with\n HTTP/1.0 user agents that use Netscape's method. (See the HISTORICAL\n section.)\n\n2. TERMINOLOGY\n\n The terms user agent, client, server, proxy, and origin server have\n the same meaning as in the HTTP/1.0 specification.\n\n Fully-qualified host name (FQHN) means either the fully-qualified\n domain name (FQDN) of a host (i.e., a completely specified domain\n name ending in a top-level domain such as .com or .uk), or the\n numeric Internet Protocol (IP) address of a host. The fully\n qualified domain name is preferred; use of numeric IP addresses is\n strongly discouraged.\n 2109 attribute attributes http key management path qualified subject nested-reference unchanged"},{"id":"IETF RFC 2227","type":"specification","body":"IETF","designation":"RFC 2227","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2227.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2227.txt","https://www.rfc-editor.org/rfc/rfc2227.pdf"],"folder":"IETF/RFC-2227","files":{"txt":{"path":"standards/IETF/RFC-2227/RFC-2227.txt","sha256":"a31e378190e5652f470c0a99283516b7ccd50af7ed8ffcfdb5c0abccb3033fb6"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a simple extension to HTTP, using a new\n \"Meter\" header, which permits a limited form of demographic\n information (colloquially called \"hit-counts\") to be reported by\n caches to origin servers, in a more efficient manner than the\n \"cache-busting\" techniques currently used. It also permits an origin\n server to control the number of times a cache uses a cached response,\n and outlines a technique that origin servers can use to capture\n referral information without \"cache-busting.\"","scope_keywords":["2227","algorithm","algorithms","http","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null}],"search_text":"IETF RFC 2227 This document proposes a simple extension to HTTP, using a new\n \"Meter\" header, which permits a limited form of demographic\n information (colloquially called \"hit-counts\") to be reported by\n caches to origin servers, in a more efficient manner than the\n \"cache-busting\" techniques currently used. It also permits an origin\n server to control the number of times a cache uses a cached response,\n and outlines a technique that origin servers can use to capture\n referral information without \"cache-busting.\" 2227 algorithm algorithms http key path nested-reference unchanged"},{"id":"IETF RFC 2296","type":"specification","body":"IETF","designation":"RFC 2296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2296.txt","https://www.rfc-editor.org/rfc/rfc2296.pdf"],"folder":"IETF/RFC-2296","files":{"txt":{"path":"standards/IETF/RFC-2296/RFC-2296.txt","sha256":"b7ae19764bd0290569b7ea4a6c2c7081edf9a7d34a284ba53eb3c4f3816f9fa6"}},"tags":["nested-reference","unchanged"],"summary":"HTTP allows web site authors to put multiple versions of the same\n information under a single URL. Transparent content negotiation is a\n mechanism for automatically selecting the best version when the URL\n is accessed. A remote variant selection algorithm can be used to\n speed up the transparent negotiation process. This document defines\n the remote variant selection algorithm with the version number 1.0.","scope_keywords":["2296","algorithm","attribute","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2296 HTTP allows web site authors to put multiple versions of the same\n information under a single URL. Transparent content negotiation is a\n mechanism for automatically selecting the best version when the URL\n is accessed. A remote variant selection algorithm can be used to\n speed up the transparent negotiation process. This document defines\n the remote variant selection algorithm with the version number 1.0. 2296 algorithm attribute http nested-reference unchanged"},{"id":"IETF RFC 2533","type":"specification","body":"IETF","designation":"RFC 2533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2533.txt","https://www.rfc-editor.org/rfc/rfc2533.pdf"],"folder":"IETF/RFC-2533","files":{"txt":{"path":"standards/IETF/RFC-2533/RFC-2533.txt","sha256":"b291e91ae891654b5c5ded6cb7944df92c62d598b224f147d24a2e8833d241d2"}},"tags":["nested-reference","unchanged"],"summary":"A number of Internet application protocols have a need to provide\n content negotiation for the resources with which they interact [1].\n A framework for such negotiation is described in [2], part of which\n is a way to describe the range of media features which can be handled\n by the sender, recipient or document transmission format of a\n message. A format for a vocabulary of individual media features and\n procedures for feature registration are presented in [3].\n\n This document introduces and describes a syntax that can be used to\n define feature sets which are formed from combinations and relations\n involving individual media features. Such feature sets are used to\n describe the media feature handling capabilities of message senders,\n recipients and file formats.\n\n An algorithm for feature set matching is also described here.","scope_keywords":["2533","algorithm","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2738","folder":"IETF/RFC-2738","source":"IETF/RFC-2738/RFC-2738.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null}],"search_text":"IETF RFC 2533 A number of Internet application protocols have a need to provide\n content negotiation for the resources with which they interact [1].\n A framework for such negotiation is described in [2], part of which\n is a way to describe the range of media features which can be handled\n by the sender, recipient or document transmission format of a\n message. A format for a vocabulary of individual media features and\n procedures for feature registration are presented in [3].\n\n This document introduces and describes a syntax that can be used to\n define feature sets which are formed from combinations and relations\n involving individual media features. Such feature sets are used to\n describe the media feature handling capabilities of message senders,\n recipients and file formats.\n\n An algorithm for feature set matching is also described here. 2533 algorithm presentation nested-reference unchanged"},{"id":"IETF RFC 5789","type":"specification","body":"IETF","designation":"RFC 5789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5789.txt","https://www.rfc-editor.org/rfc/rfc5789.pdf"],"folder":"IETF/RFC-5789","files":{"txt":{"path":"standards/IETF/RFC-5789/RFC-5789.txt","sha256":"9405262c2f3a33848c6cf1694e5e40222eb27a6858a6d93e70328b444d197e8f"}},"tags":["nested-reference","unchanged"],"summary":"Several applications extending the Hypertext Transfer Protocol (HTTP)\n require a feature to do partial resource modification. The existing\n HTTP PUT method only allows a complete replacement of a document.\n This proposal adds a new HTTP method, PATCH, to modify an existing\n HTTP resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5789.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Tr","scope_keywords":["5789","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7396","folder":"IETF/RFC-7396","source":"IETF/RFC-7396/RFC-7396.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 5789 Several applications extending the Hypertext Transfer Protocol (HTTP)\n require a feature to do partial resource modification. The existing\n HTTP PUT method only allows a complete replacement of a document.\n This proposal adds a new HTTP method, PATCH, to modify an existing\n HTTP resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5789.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Tr 5789 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7616","type":"specification","body":"IETF","designation":"RFC 7616","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7616.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7616.txt","https://www.rfc-editor.org/rfc/rfc7616.pdf"],"folder":"IETF/RFC-7616","files":{"txt":{"path":"standards/IETF/RFC-7616/RFC-7616.txt","sha256":"65e4770b3c3bfe129cdaaca358454118a6c10fd261dd3822e07ca786199e907b"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) provides a simple challenge-\n response authentication mechanism that may be used by a server to\n challenge a client request and by a client to provide authentication\n information. This document defines the HTTP Digest Authentication\n scheme that can be used with the HTTP authentication mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7616.","scope_keywords":["7616","algorithm","algorithms","authentication","authorization","hash","hashing","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 7616 The Hypertext Transfer Protocol (HTTP) provides a simple challenge-\n response authentication mechanism that may be used by a server to\n challenge a client request and by a client to provide authentication\n information. This document defines the HTTP Digest Authentication\n scheme that can be used with the HTTP authentication mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7616. 7616 algorithm algorithms authentication authorization hash hashing http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2078","type":"specification","body":"IETF","designation":"RFC 2078","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2078.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2078.txt","https://www.rfc-editor.org/rfc/rfc2078.pdf"],"folder":"IETF/RFC-2078","files":{"txt":{"path":"standards/IETF/RFC-2078/RFC-2078.txt","sha256":"8142e6c12656a1f09cc6fd470292b5a337a3df980d37ac22a2adf5c1f0311e34"}},"tags":["nested-reference","unchanged"],"summary":"The Generic Security Service Application Program Interface (GSS-API),\n as defined in RFC-1508, provides security services to callers in a\n generic fashion, supportable with a range of underlying mechanisms\n and technologies and hence allowing source-level portability of\n applications to different environments. This specification defines\n GSS-API services and primitives at a level independent of underlying\n mechanism and programming language environment, and is to be\n complemented by other, related specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to be\n implemented in order to realize GSS-API services atop particular\n security mechanisms\n\n This memo revises RFC-1508, making specific, incremental changes in\n response to implementation experience and liaison requests. It is\n i","scope_keywords":["2078","authentication","credential","credentials","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2203","folder":"IETF/RFC-2203","source":"IETF/RFC-2203/RFC-2203.txt","version":null},{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2478","folder":"IETF/RFC-2478","source":"IETF/RFC-2478/RFC-2478.txt","version":null},{"body":"IETF","designation":"RFC 2479","folder":"IETF/RFC-2479","source":"IETF/RFC-2479/RFC-2479.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2695","folder":"IETF/RFC-2695","source":"IETF/RFC-2695/RFC-2695.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2078 The Generic Security Service Application Program Interface (GSS-API),\n as defined in RFC-1508, provides security services to callers in a\n generic fashion, supportable with a range of underlying mechanisms\n and technologies and hence allowing source-level portability of\n applications to different environments. This specification defines\n GSS-API services and primitives at a level independent of underlying\n mechanism and programming language environment, and is to be\n complemented by other, related specifications:\n\n documents defining specific parameter bindings for particular\n language environments\n\n documents defining token formats, protocols, and procedures to be\n implemented in order to realize GSS-API services atop particular\n security mechanisms\n\n This memo revises RFC-1508, making specific, incremental changes in\n response to implementation experience and liaison requests. It is\n i 2078 authentication credential credentials management nested-reference unchanged"},{"id":"IETF RFC 2478","type":"specification","body":"IETF","designation":"RFC 2478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2478.txt","https://www.rfc-editor.org/rfc/rfc2478.pdf"],"folder":"IETF/RFC-2478","files":{"txt":{"path":"standards/IETF/RFC-2478/RFC-2478.txt","sha256":"5a4530d0a2596400e0c19c129e27faf399dd1559fb25fae12aeb770701ff2048"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Security Negotiation Mechanism for the\n Generic Security Service Application Program Interface (GSS-API)\n which is described in [1].\n\n The GSS-API provides a generic interface which can be layered atop\n different security mechanisms such that if communicating peers\n acquire GSS-API credentials for the same security mechanism, then a\n security context may be established between them (subject to policy).\n However, GSS-API doesn't prescribe the method by which GSS-API peers\n can establish whether they have a common security mechanism.\n\n The Simple and Protected GSS-API Negotiation Mechanism defined here\n is a pseudo-security mechanism, represented by the object identifier\n iso.org.dod.internet.security.mechanism.snego (1.3.6.1.5.5.2) which\n enables GSS-API peers to determine in-band whether their credentials\n share common GSS-API security mechanism(s), and if so, t","scope_keywords":["2478","credential","credentials","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2703","folder":"IETF/RFC-2703","source":"IETF/RFC-2703/RFC-2703.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4178","folder":"IETF/RFC-4178","source":"IETF/RFC-4178/RFC-4178.txt","version":null}],"search_text":"IETF RFC 2478 This document specifies a Security Negotiation Mechanism for the\n Generic Security Service Application Program Interface (GSS-API)\n which is described in [1].\n\n The GSS-API provides a generic interface which can be layered atop\n different security mechanisms such that if communicating peers\n acquire GSS-API credentials for the same security mechanism, then a\n security context may be established between them (subject to policy).\n However, GSS-API doesn't prescribe the method by which GSS-API peers\n can establish whether they have a common security mechanism.\n\n The Simple and Protected GSS-API Negotiation Mechanism defined here\n is a pseudo-security mechanism, represented by the object identifier\n iso.org.dod.internet.security.mechanism.snego (1.3.6.1.5.5.2) which\n enables GSS-API peers to determine in-band whether their credentials\n share common GSS-API security mechanism(s), and if so, t 2478 credential credentials policy subject nested-reference unchanged"},{"id":"IETF RFC 3296","type":"specification","body":"IETF","designation":"RFC 3296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3296.txt","https://www.rfc-editor.org/rfc/rfc3296.pdf"],"folder":"IETF/RFC-3296","files":{"txt":{"path":"standards/IETF/RFC-3296/RFC-3296.txt","sha256":"33b6485e1eaaeff2c2ed6518aa411ebad99a09a2d18930aba529955acedfbd37"}},"tags":["nested-reference","unchanged"],"summary":"This document details schema and protocol elements for representing\n and managing named subordinate references in Lightweight Directory\n Access Protocol (LDAP) Directories.\n\nConventions\n\n Schema definitions are provided using LDAPv3 description formats\n [RFC2252]. Definitions provided here are formatted (line wrapped)\n for readability.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" used in\n this document are to be interpreted as described in BCP 14 [RFC2119].\n\n1. Background and Intended Usage\n\n The broadening of interest in LDAP (Lightweight Directory Access\n Protocol) [RFC2251] directories beyond their use as front ends to\n X.500 [X.500] directories has created a need to represent knowledge\n information in a more general way. Knowledge information is\n information about one or more servers maintained in ","scope_keywords":["3296","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null}],"search_text":"IETF RFC 3296 This document details schema and protocol elements for representing\n and managing named subordinate references in Lightweight Directory\n Access Protocol (LDAP) Directories.\n\nConventions\n\n Schema definitions are provided using LDAPv3 description formats\n [RFC2252]. Definitions provided here are formatted (line wrapped)\n for readability.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" used in\n this document are to be interpreted as described in BCP 14 [RFC2119].\n\n1. Background and Intended Usage\n\n The broadening of interest in LDAP (Lightweight Directory Access\n Protocol) [RFC2251] directories beyond their use as front ends to\n X.500 [X.500] directories has created a need to represent knowledge\n information in a more general way. Knowledge information is\n information about one or more servers maintained in  3296 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 2546","type":"specification","body":"IETF","designation":"RFC 2546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2546.txt","https://www.rfc-editor.org/rfc/rfc2546.pdf"],"folder":"IETF/RFC-2546","files":{"txt":{"path":"standards/IETF/RFC-2546/RFC-2546.txt","sha256":"9ffb54c8c26fbe23bea27400a0768d75c6d6562657698a2af05e771065e28da6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Durand\nRequest for Comments: 2546 IMAG\nCategory: Informational B. Buclin\n AT&T Labs Europe\n March 1999\n\n 6Bone Routing Practice\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n The 6Bone is an environment supporting experimentation with the IPv6\n protocols and products implementing it. As the network grows, the\n need for common operation rules emerged. In particular, operation of\n the 6Bone backbone is a challenge due to the frequent insertion of\n bogus routes by leaf or even backbone sites.\n\n This memo identifies guidelines on how 6Bone sites might operate, so\n that the 6Bone can remain a quality experimentation environment and\n to av","scope_keywords":["2546","key","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null}],"search_text":"IETF RFC 2546 Network Working Group A. Durand\nRequest for Comments: 2546 IMAG\nCategory: Informational B. Buclin\n AT&T Labs Europe\n March 1999\n\n 6Bone Routing Practice\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n The 6Bone is an environment supporting experimentation with the IPv6\n protocols and products implementing it. As the network grows, the\n need for common operation rules emerged. In particular, operation of\n the 6Bone backbone is a challenge due to the frequent insertion of\n bogus routes by leaf or even backbone sites.\n\n This memo identifies guidelines on how 6Bone sites might operate, so\n that the 6Bone can remain a quality experimentation environment and\n to av 2546 key path policies nested-reference unchanged"},{"id":"IETF RFC 2772","type":"specification","body":"IETF","designation":"RFC 2772","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2772.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2772.txt","https://www.rfc-editor.org/rfc/rfc2772.pdf"],"folder":"IETF/RFC-2772","files":{"txt":{"path":"standards/IETF/RFC-2772/RFC-2772.txt","sha256":"11a36d680c097acab53db29eab34b205a367d004f97fc1d327ba1bea41362ef6"}},"tags":["nested-reference","unchanged"],"summary":"The 6Bone is an Ipv6 testbed to assist in the evolution and\n deployment of IPv6. Because of this, it is important that the core\n backbone of the IPv6 network maintain stability, and that all\n operators have a common set of rules and guidelines by which to\n deploy IPv6 routing equipment.\n\n This document provides a set of guidelines for all 6bone routing\n equipment operators to use as a reference for efficient and stable\n deployment of 6bone routing systems. As the complexity of the 6Bone\n grows,the adherence to a common set of rules becomes increasingly\n important in order for an efficient, scalable backbone to exist.\n\nRockell & Fink Informational [Page 1]\n\f\nRFC 2772 6Bone Backbone Routing Guidelines February 2000","scope_keywords":["2772","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3178","folder":"IETF/RFC-3178","source":"IETF/RFC-3178/RFC-3178.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null}],"search_text":"IETF RFC 2772 The 6Bone is an Ipv6 testbed to assist in the evolution and\n deployment of IPv6. Because of this, it is important that the core\n backbone of the IPv6 network maintain stability, and that all\n operators have a common set of rules and guidelines by which to\n deploy IPv6 routing equipment.\n\n This document provides a set of guidelines for all 6bone routing\n equipment operators to use as a reference for efficient and stable\n deployment of 6bone routing systems. As the complexity of the 6Bone\n grows,the adherence to a common set of rules becomes increasingly\n important in order for an efficient, scalable backbone to exist.\n\nRockell & Fink Informational [Page 1]\n\f\nRFC 2772 6Bone Backbone Routing Guidelines February 2000 2772 key policies nested-reference unchanged"},{"id":"IETF RFC 3178","type":"specification","body":"IETF","designation":"RFC 3178","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3178.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3178.txt","https://www.rfc-editor.org/rfc/rfc3178.pdf"],"folder":"IETF/RFC-3178","files":{"txt":{"path":"standards/IETF/RFC-3178/RFC-3178.txt","sha256":"3ed739a5939f83aea34e8ccb25cd9b6a35c9123c89feafbd7287f7d14ed98691"}},"tags":["nested-reference","unchanged"],"summary":"The document describes a mechanism for basic IPv6 multihoming\n support, and its operational requirements. Unlike currently-\n practiced IPv4 multihoming, the technique does not impact the\n worldwide routing table size, nor IGP (Interior Gateway Protocol)\n routing table size in upstream ISPs. The mechanism can be combined\n with more sophisticated (or complex) multihoming support mechanisms,\n and can be used as a foundation for other mechanisms. The document\n is largely based on RFC 2260 by Tony Bates.\n\n1. Problem\n\n Routing table size has been a major issue for both IPv4 and IPv6. As\n IPv6 addresses are 4 times larger in bit width than IPv4, the routing\n table size issue would have more serious negative effects on router\n memory usage, as well as routing table lookup performance. To cope\n with this problem, the IPv6 addressing architecture [Hinden, 1998] is\n designed to take advantage of ag","scope_keywords":["3178","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3704","folder":"IETF/RFC-3704","source":"IETF/RFC-3704/RFC-3704.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null}],"search_text":"IETF RFC 3178 The document describes a mechanism for basic IPv6 multihoming\n support, and its operational requirements. Unlike currently-\n practiced IPv4 multihoming, the technique does not impact the\n worldwide routing table size, nor IGP (Interior Gateway Protocol)\n routing table size in upstream ISPs. The mechanism can be combined\n with more sophisticated (or complex) multihoming support mechanisms,\n and can be used as a foundation for other mechanisms. The document\n is largely based on RFC 2260 by Tony Bates.\n\n1. Problem\n\n Routing table size has been a major issue for both IPv4 and IPv6. As\n IPv6 addresses are 4 times larger in bit width than IPv4, the routing\n table size issue would have more serious negative effects on router\n memory usage, as well as routing table lookup performance. To cope\n with this problem, the IPv6 addressing architecture [Hinden, 1998] is\n designed to take advantage of ag 3178 delivery nested-reference unchanged"},{"id":"IETF RFC 4191","type":"specification","body":"IETF","designation":"RFC 4191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4191.txt","https://www.rfc-editor.org/rfc/rfc4191.pdf"],"folder":"IETF/RFC-4191","files":{"txt":{"path":"standards/IETF/RFC-4191/RFC-4191.txt","sha256":"af52cea0e3aa71c020ced4543a6c46536c87f70a2a50895e9c67a30f45f8c1ea"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an optional extension to Router Advertisement\n messages for communicating default router preferences and more-\n specific routes from routers to hosts. This improves the ability of\n hosts to pick an appropriate router, especially when the host is\n multi-homed and the routers are on different links. The preference\n values and specific routes advertised to hosts require administrative\n configuration; they are not automatically derived from routing\n tables.\n\n1. Introduction\n\n Neighbor Discovery [RFC2461] specifies a conceptual model for hosts\n that includes a Default Router List and a Prefix List. Hosts send\n Router Solicitation messages and receive Router Advertisement\n messages from routers. Hosts populate their Default Router List and\n Prefix List based on information in the Router Advertisement\n messages. A conceptual sending algorithm uses the Prefix List to\n det","scope_keywords":["4191","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4311","folder":"IETF/RFC-4311","source":"IETF/RFC-4311/RFC-4311.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5221","folder":"IETF/RFC-5221","source":"IETF/RFC-5221/RFC-5221.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 4191 This document describes an optional extension to Router Advertisement\n messages for communicating default router preferences and more-\n specific routes from routers to hosts. This improves the ability of\n hosts to pick an appropriate router, especially when the host is\n multi-homed and the routers are on different links. The preference\n values and specific routes advertised to hosts require administrative\n configuration; they are not automatically derived from routing\n tables.\n\n1. Introduction\n\n Neighbor Discovery [RFC2461] specifies a conceptual model for hosts\n that includes a Default Router List and a Prefix List. Hosts send\n Router Solicitation messages and receive Router Advertisement\n messages from routers. Hosts populate their Default Router List and\n Prefix List based on information in the Router Advertisement\n messages. A conceptual sending algorithm uses the Prefix List to\n det 4191 algorithm key nested-reference unchanged"},{"id":"IETF RFC 2081","type":"specification","body":"IETF","designation":"RFC 2081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2081.txt","https://www.rfc-editor.org/rfc/rfc2081.pdf"],"folder":"IETF/RFC-2081","files":{"txt":{"path":"standards/IETF/RFC-2081/RFC-2081.txt","sha256":"c3993256134db2f1e9a4dc630657bcf62e2bd3e4e0baca27add0d11402d2b874"}},"tags":["nested-reference","unchanged"],"summary":"As required by Routing Protocol Criteria (RFC 1264), this report\n defines the applicability of the RIPng protocol within the Internet.\n This report is a prerequisite to advancing RIPng on the standards\n track.\n\n1. Protocol Documents\n\n The RIPng protocol description is defined in RFC 2080.\n\n2. Introduction\n\n This report describes how RIPng may be useful within the new IPv6\n Internet. In essence, the environments in which RIPng is the IGP of\n choice is comparable to the environments in which RIP-2 (RFC 1723) is\n used in the IPv4 Internet. It is important to remember that RIPng is\n a simple extrapolation of RIP-2; RIPng has nothing conceptually new.\n Thus, the operational aspects of distance-vector routing protocols,\n and RIP-2 in particular, within an autonomous system are well\n understood.\n\n It should be noted that RIPng is not intended to be a substitute for\n OSPFng in large autonomous s","scope_keywords":["2081","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 2081 As required by Routing Protocol Criteria (RFC 1264), this report\n defines the applicability of the RIPng protocol within the Internet.\n This report is a prerequisite to advancing RIPng on the standards\n track.\n\n1. Protocol Documents\n\n The RIPng protocol description is defined in RFC 2080.\n\n2. Introduction\n\n This report describes how RIPng may be useful within the new IPv6\n Internet. In essence, the environments in which RIPng is the IGP of\n choice is comparable to the environments in which RIP-2 (RFC 1723) is\n used in the IPv4 Internet. It is important to remember that RIPng is\n a simple extrapolation of RIP-2; RIPng has nothing conceptually new.\n Thus, the operational aspects of distance-vector routing protocols,\n and RIP-2 in particular, within an autonomous system are well\n understood.\n\n It should be noted that RIPng is not intended to be a substitute for\n OSPFng in large autonomous s 2081 authentication nested-reference unchanged"},{"id":"IETF RFC 3503","type":"specification","body":"IETF","designation":"RFC 3503","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3503.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3503.txt","https://www.rfc-editor.org/rfc/rfc3503.pdf"],"folder":"IETF/RFC-3503","files":{"txt":{"path":"standards/IETF/RFC-3503/RFC-3503.txt","sha256":"82151d011f42d2a458128ccce80f053f7e914a5791686465cfa7538c93496324"}},"tags":["nested-reference","unchanged"],"summary":"The Message Disposition Notification (MDN) facility defined in RFC\n 2298 provides a means by which a message can request that message\n processing by the recipient be acknowledged as well as a format to be\n used for such acknowledgements. However, it doesn't describe how\n multiple Mail User Agents (MUAs) should handle the generation of MDNs\n in an Internet Message Access Protocol (IMAP4) environment.\n\n This document describes how to handle MDNs in such an environment and\n provides guidelines for implementers of IMAP4 that want to add MDN\n support to their products.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 3503 MDN profile for IMAP March 2003","scope_keywords":["3503","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3503 The Message Disposition Notification (MDN) facility defined in RFC\n 2298 provides a means by which a message can request that message\n processing by the recipient be acknowledged as well as a format to be\n used for such acknowledgements. However, it doesn't describe how\n multiple Mail User Agents (MUAs) should handle the generation of MDNs\n in an Internet Message Access Protocol (IMAP4) environment.\n\n This document describes how to handle MDNs in such an environment and\n provides guidelines for implementers of IMAP4 that want to add MDN\n support to their products.\n\nMelnikov Standards Track [Page 1]\n\f\nRFC 3503 MDN profile for IMAP March 2003 3503 key profile nested-reference unchanged"},{"id":"IETF RFC 5257","type":"specification","body":"IETF","designation":"RFC 5257","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5257.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5257.txt","https://www.rfc-editor.org/rfc/rfc5257.pdf"],"folder":"IETF/RFC-5257","files":{"txt":{"path":"standards/IETF/RFC-5257/RFC-5257.txt","sha256":"0e7ae0075bd5133dd5aadc349f8dccbfd06dbfc16cd45e19a0bb2b00fa014a09"}},"tags":["nested-reference","unchanged"],"summary":"The ANNOTATE extension to the Internet Message Access Protocol\n permits clients and servers to maintain \"meta data\" for messages, or\n individual message parts, stored in a mailbox on the server. For\n example, this can be used to attach comments and other useful\n information to a message. It is also possible to attach annotations\n to specific parts of a message, so that, for example, they could be\n marked as seen, or important, or a comment added.\n\n Note that this document was the product of a WG that had good\n consensus on how to approach the problem. Nevertheless, the WG felt\n it did not have enough information on implementation and deployment\n hurdles to meet all of the requirements of a Proposed Standard. The\n IETF solicits implementations and implementation reports in order to\n make further progress.\n\n Implementers should be aware that this specification may change in an\n incompatibl","scope_keywords":["5257","attribute","attributes","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null}],"search_text":"IETF RFC 5257 The ANNOTATE extension to the Internet Message Access Protocol\n permits clients and servers to maintain \"meta data\" for messages, or\n individual message parts, stored in a mailbox on the server. For\n example, this can be used to attach comments and other useful\n information to a message. It is also possible to attach annotations\n to specific parts of a message, so that, for example, they could be\n marked as seen, or important, or a comment added.\n\n Note that this document was the product of a WG that had good\n consensus on how to approach the problem. Nevertheless, the WG felt\n it did not have enough information on implementation and deployment\n hurdles to meet all of the requirements of a Proposed Standard. The\n IETF solicits implementations and implementation reports in order to\n make further progress.\n\n Implementers should be aware that this specification may change in an\n incompatibl 5257 attribute attributes key subject nested-reference unchanged"},{"id":"IETF RFC 6851","type":"specification","body":"IETF","designation":"RFC 6851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6851.txt","https://www.rfc-editor.org/rfc/rfc6851.pdf"],"folder":"IETF/RFC-6851","files":{"txt":{"path":"standards/IETF/RFC-6851/RFC-6851.txt","sha256":"c4d5c0a7297ae1d23982ceb8422ddae8275483c4fef7e5db56edc46e55608290"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an IMAP extension consisting of two new\n commands, MOVE and UID MOVE, that are used to move messages from one\n mailbox to another.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6851.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's L","scope_keywords":["6851","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6851 This document defines an IMAP extension consisting of two new\n commands, MOVE and UID MOVE, that are used to move messages from one\n mailbox to another.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6851.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's L 6851 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8438","type":"specification","body":"IETF","designation":"RFC 8438","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8438.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8438.txt","https://www.rfc-editor.org/rfc/rfc8438.pdf"],"folder":"IETF/RFC-8438","files":{"txt":{"path":"standards/IETF/RFC-8438/RFC-8438.txt","sha256":"36432e42934250b81f19e2c7f529decc66508dcbfad19a3225654c4a375673f1"}},"tags":["nested-reference","unchanged"],"summary":"This document adds a new capability called \"STATUS=SIZE\" to the\n Internet Message Access Protocol (IMAP). It allows retrieving the\n total storage size of a mailbox with a single STATUS command rather\n than retrieving and summing the sizes of all individual messages in\n that mailbox.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8438.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust a","scope_keywords":["8438","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 8438 This document adds a new capability called \"STATUS=SIZE\" to the\n Internet Message Access Protocol (IMAP). It allows retrieving the\n total storage size of a mailbox with a single STATUS command rather\n than retrieving and summing the sizes of all individual messages in\n that mailbox.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8438.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust a 8438 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2088","type":"specification","body":"IETF","designation":"RFC 2088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2088.txt","https://www.rfc-editor.org/rfc/rfc2088.pdf"],"folder":"IETF/RFC-2088","files":{"txt":{"path":"standards/IETF/RFC-2088/RFC-2088.txt","sha256":"76855fd841a9ba11edf17783db57c41582a617b7ab7056684d189fd97f2809c8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Myers\nRequest for Comments: 2088 Carnegie Mellon\nCateogry: Standards Track January 1997\n\n IMAP4 non-synchronizing literals\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Internet Message Access Protocol [IMAP4] contains the \"literal\"\n syntactic construct for communicating strings. When sending a\n literal from client to server, IMAP4 requires the client to wait for\n the server to send a command continuation request between sending the\n octet count and the string data. This document specifies an\n alternate form of literal which does not","scope_keywords":["2088","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null}],"search_text":"IETF RFC 2088 Network Working Group J. Myers\nRequest for Comments: 2088 Carnegie Mellon\nCateogry: Standards Track January 1997\n\n IMAP4 non-synchronizing literals\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\n1. Abstract\n\n The Internet Message Access Protocol [IMAP4] contains the \"literal\"\n syntactic construct for communicating strings. When sending a\n literal from client to server, IMAP4 requires the client to wait for\n the server to send a command continuation request between sending the\n octet count and the string data. This document specifies an\n alternate form of literal which does not 2088 crl nested-reference unchanged"},{"id":"IETF RFC 4466","type":"specification","body":"IETF","designation":"RFC 4466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4466.txt","https://www.rfc-editor.org/rfc/rfc4466.pdf"],"folder":"IETF/RFC-4466","files":{"txt":{"path":"standards/IETF/RFC-4466/RFC-4466.txt","sha256":"f93db9724024384143a00fc03ef02c4125ddde6add31a981670be8d2b72ce995"}},"tags":["nested-reference","unchanged"],"summary":"Over the years, many documents from IMAPEXT and LEMONADE working\n groups, as well as many individual documents, have added syntactic\n extensions to many base IMAP commands described in RFC 3501. For\n ease of reference, this document collects most of such ABNF changes\n in one place.\n\n This document also suggests a set of standard patterns for adding\n options and extensions to several existing IMAP commands defined in\n RFC 3501. The patterns provide for compatibility between existing\n and future extensions.\n\n This document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516.\n It also includes part of the errata to RFC 3501. This document\n doesn't specify any semantic changes to the listed RFCs.\n\nMelnikov & Daboo Standards Track [Page 1]\n\f\nRFC 4466 Collected Extensions to IMAP4 ABNF April 2006","scope_keywords":["4466","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4731","folder":"IETF/RFC-4731","source":"IETF/RFC-4731/RFC-4731.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4466 Over the years, many documents from IMAPEXT and LEMONADE working\n groups, as well as many individual documents, have added syntactic\n extensions to many base IMAP commands described in RFC 3501. For\n ease of reference, this document collects most of such ABNF changes\n in one place.\n\n This document also suggests a set of standard patterns for adding\n options and extensions to several existing IMAP commands defined in\n RFC 3501. The patterns provide for compatibility between existing\n and future extensions.\n\n This document updates ABNF in RFCs 2088, 2342, 3501, 3502, and 3516.\n It also includes part of the errata to RFC 3501. This document\n doesn't specify any semantic changes to the listed RFCs.\n\nMelnikov & Daboo Standards Track [Page 1]\n\f\nRFC 4466 Collected Extensions to IMAP4 ABNF April 2006 4466 attribute key nested-reference unchanged"},{"id":"IETF RFC 6855","type":"specification","body":"IETF","designation":"RFC 6855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6855.txt","https://www.rfc-editor.org/rfc/rfc6855.pdf"],"folder":"IETF/RFC-6855","files":{"txt":{"path":"standards/IETF/RFC-6855/RFC-6855.txt","sha256":"d9b7eba828f5ec10b3d1d89a4ced437fbc4dd7813aacde08b8addbf8d351a1ed"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Internet Message Access Protocol\n (IMAP) to support UTF-8 encoded international characters in user\n names, mail addresses, and message headers. This specification\n replaces RFC 5738.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6855.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved","scope_keywords":["6855","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6855 This specification extends the Internet Message Access Protocol\n (IMAP) to support UTF-8 encoded international characters in user\n names, mail addresses, and message headers. This specification\n replaces RFC 5738.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6855.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved 6855 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7888","type":"specification","body":"IETF","designation":"RFC 7888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7888.txt","https://www.rfc-editor.org/rfc/rfc7888.pdf"],"folder":"IETF/RFC-7888","files":{"txt":{"path":"standards/IETF/RFC-7888/RFC-7888.txt","sha256":"62e676eeece48d072ab1e2049613357ef47e7a9f3fb52163f27eece0d7d95b15"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Message Access Protocol (RFC 3501) contains the\n \"literal\" syntactic construct for communicating strings. When\n sending a literal from client to server, IMAP requires the client to\n wait for the server to send a command continuation request between\n sending the octet count and the string data. This document specifies\n an alternate form of literal that does not require this network round\n trip.\n\n This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-.\n LITERAL+ allows the alternate form of literals in all IMAP commands.\n LITERAL- is the same as LITERAL+, but it disallows the alternate form\n of literals unless they are 4096 bytes or less.\n\n This document obsoletes RFC 2088.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community.","scope_keywords":["7888","crl","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 7888 The Internet Message Access Protocol (RFC 3501) contains the\n \"literal\" syntactic construct for communicating strings. When\n sending a literal from client to server, IMAP requires the client to\n wait for the server to send a command continuation request between\n sending the octet count and the string data. This document specifies\n an alternate form of literal that does not require this network round\n trip.\n\n This document specifies 2 IMAP extensions: LITERAL+ and LITERAL-.\n LITERAL+ allows the alternate form of literals in all IMAP commands.\n LITERAL- is the same as LITERAL+, but it disallows the alternate form\n of literals unless they are 4096 bytes or less.\n\n This document obsoletes RFC 2088.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. 7888 crl http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2091","type":"specification","body":"IETF","designation":"RFC 2091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2091.txt","https://www.rfc-editor.org/rfc/rfc2091.pdf"],"folder":"IETF/RFC-2091","files":{"txt":{"path":"standards/IETF/RFC-2091/RFC-2091.txt","sha256":"804b269b950e39252270d98a860b28698ba8a5f8ccdf7d04665303e40dfd0ab2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a modification which can be applied to\n Bellman-Ford (distance vector) algorithm information broadcasting\n protocols - for example IP RIP, Netware RIP or Netware SAP - which\n makes it feasible to run them on connection oriented Public Data\n Networks.\n\n This proposal has a number of efficiency advantages over the Demand\n RIP proposal (RFC 1582).\n\nAcknowledgements\n\n The authors wish to thank Richard Edmonstone of Shiva, Joahanna\n Kruger of Xyplex, Steve Waters of DEC and Guenter Roeck of Conware\n for many comments and suggestions which improved this effort.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o MUST -- the item is an absolute requirement of the specification.\n MUST is only used where it is actually required for\n interoperation, not to try to impose a particular method on\n implementors where not ","scope_keywords":["2091","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 2091 This document defines a modification which can be applied to\n Bellman-Ford (distance vector) algorithm information broadcasting\n protocols - for example IP RIP, Netware RIP or Netware SAP - which\n makes it feasible to run them on connection oriented Public Data\n Networks.\n\n This proposal has a number of efficiency advantages over the Demand\n RIP proposal (RFC 1582).\n\nAcknowledgements\n\n The authors wish to thank Richard Edmonstone of Shiva, Joahanna\n Kruger of Xyplex, Steve Waters of DEC and Guenter Roeck of Conware\n for many comments and suggestions which improved this effort.\n\nConventions\n\n The following language conventions are used in the items of\n specification in this document:\n\n o MUST -- the item is an absolute requirement of the specification.\n MUST is only used where it is actually required for\n interoperation, not to try to impose a particular method on\n implementors where not  2091 algorithm nested-reference unchanged"},{"id":"IETF RFC 2093","type":"specification","body":"IETF","designation":"RFC 2093","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2093.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2093.txt","https://www.rfc-editor.org/rfc/rfc2093.pdf"],"folder":"IETF/RFC-2093","files":{"txt":{"path":"standards/IETF/RFC-2093/RFC-2093.txt","sha256":"922ceb146fac7dd28ca1b58879750e6a6b99535073d0b6b0dc4cee993d99b54f"}},"tags":["nested-reference","unchanged"],"summary":"This specification proposes a protocol to create grouped symmetric\n keys and distribute them amongst communicating peers. This protocol\n has the following advantages: 1) virtually invisible to operator, 2)\n no central key distribution site is needed, 3) only group members\n have the key, 4) sender or receiver oriented operation, 5) can make\n use of multicast communications protocols.\n\n1 Background\n\n Traditional key management distribution has mimicked the military\n paper based key accounting system. Key was distributed, ordered, and\n accounted physically leading to large lead times and expensive\n operations.\n\n Cooperative key management algorithms exist that allow pairwise keys\n to be generated between two equipment's. This gives the a quicker\n more reliable key management structure capable of supporting large\n numbers of secure communications. Unfortunately, only pairwise keys\n are suppo","scope_keywords":["2093","algorithm","algorithms","authorization","certificate","certificates","crl","key","keys","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2627","folder":"IETF/RFC-2627","source":"IETF/RFC-2627/RFC-2627.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null}],"search_text":"IETF RFC 2093 This specification proposes a protocol to create grouped symmetric\n keys and distribute them amongst communicating peers. This protocol\n has the following advantages: 1) virtually invisible to operator, 2)\n no central key distribution site is needed, 3) only group members\n have the key, 4) sender or receiver oriented operation, 5) can make\n use of multicast communications protocols.\n\n1 Background\n\n Traditional key management distribution has mimicked the military\n paper based key accounting system. Key was distributed, ordered, and\n accounted physically leading to large lead times and expensive\n operations.\n\n Cooperative key management algorithms exist that allow pairwise keys\n to be generated between two equipment's. This gives the a quicker\n more reliable key management structure capable of supporting large\n numbers of secure communications. Unfortunately, only pairwise keys\n are suppo 2093 algorithm algorithms authorization certificate certificates crl key keys management qualified nested-reference unchanged"},{"id":"IETF RFC 3740","type":"specification","body":"IETF","designation":"RFC 3740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3740.txt","https://www.rfc-editor.org/rfc/rfc3740.pdf"],"folder":"IETF/RFC-3740","files":{"txt":{"path":"standards/IETF/RFC-3740/RFC-3740.txt","sha256":"230f19f9d5e36a37123055ea21504f42140aea4f6debda14210f19523f6b5ec3"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview and rationale of the multicast\n security architecture used to secure data packets of large multicast\n groups. The document begins by introducing a Multicast Security\n Reference Framework, and proceeds to identify the security services\n that may be part of a secure multicast solution.","scope_keywords":["3740","authentication","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4534","folder":"IETF/RFC-4534","source":"IETF/RFC-4534/RFC-4534.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null}],"search_text":"IETF RFC 3740 This document provides an overview and rationale of the multicast\n security architecture used to secure data packets of large multicast\n groups. The document begins by introducing a Multicast Security\n Reference Framework, and proceeds to identify the security services\n that may be part of a secure multicast solution. 3740 authentication key management policies policy nested-reference unchanged"},{"id":"IETF RFC 4046","type":"specification","body":"IETF","designation":"RFC 4046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4046.txt","https://www.rfc-editor.org/rfc/rfc4046.pdf"],"folder":"IETF/RFC-4046","files":{"txt":{"path":"standards/IETF/RFC-4046/RFC-4046.txt","sha256":"1140cb4864b4615958d16d78f27c324f02db4b03855e069ad2d8a2a7e2c83b92"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the common architecture for Multicast Security\n (MSEC) key management protocols to support a variety of application,\n transport, and network layer security protocols. It also defines the\n group security association (GSA), and describes the key management\n protocols that help establish a GSA. The framework and guidelines\n described in this document permit a modular and flexible design of\n group key management protocols for a variety of different settings\n that are specialized to applications needs. MSEC key management\n protocols may be used to facilitate secure one-to-many, many-to-many,\n or one-to-one communication.","scope_keywords":["4046","algorithm","algorithms","authentication","key","keys","management","policy","tls","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null}],"search_text":"IETF RFC 4046 This document defines the common architecture for Multicast Security\n (MSEC) key management protocols to support a variety of application,\n transport, and network layer security protocols. It also defines the\n group security association (GSA), and describes the key management\n protocols that help establish a GSA. The framework and guidelines\n described in this document permit a modular and flexible design of\n group key management protocols for a variety of different settings\n that are specialized to applications needs. MSEC key management\n protocols may be used to facilitate secure one-to-many, many-to-many,\n or one-to-one communication. 4046 algorithm algorithms authentication key keys management policy tls tsp nested-reference unchanged"},{"id":"IETF RFC 4535","type":"specification","body":"IETF","designation":"RFC 4535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4535.txt","https://www.rfc-editor.org/rfc/rfc4535.pdf"],"folder":"IETF/RFC-4535","files":{"txt":{"path":"standards/IETF/RFC-4535/RFC-4535.txt","sha256":"a37ec900ea3f7909f45b35a2afaa01b21176c2d00889cfcca07be91139205887"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Group Secure Association Key Management\n Protocol (GSAKMP). The GSAKMP provides a security framework for\n creating and managing cryptographic groups on a network. It provides\n mechanisms to disseminate group policy and authenticate users, rules\n to perform access control decisions during group establishment and\n recovery, capabilities to recover from the compromise of group\n members, delegation of group security functions, and capabilities to\n destroy the group. It also generates group keys.\n\nHarney, et al. Standards Track [Page 1]\n\f\nRFC 4535 GSAKMP June 2006","scope_keywords":["4535","authorization","key","keys","management","pid","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4534","folder":"IETF/RFC-4534","source":"IETF/RFC-4534/RFC-4534.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4535 This document specifies the Group Secure Association Key Management\n Protocol (GSAKMP). The GSAKMP provides a security framework for\n creating and managing cryptographic groups on a network. It provides\n mechanisms to disseminate group policy and authenticate users, rules\n to perform access control decisions during group establishment and\n recovery, capabilities to recover from the compromise of group\n members, delegation of group security functions, and capabilities to\n destroy the group. It also generates group keys.\n\nHarney, et al. Standards Track [Page 1]\n\f\nRFC 4535 GSAKMP June 2006 4535 authorization key keys management pid policy trust nested-reference unchanged"},{"id":"IETF RFC 2094","type":"specification","body":"IETF","designation":"RFC 2094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2094.txt","https://www.rfc-editor.org/rfc/rfc2094.pdf"],"folder":"IETF/RFC-2094","files":{"txt":{"path":"standards/IETF/RFC-2094/RFC-2094.txt","sha256":"1bdd49b5ae062a91ba0442c05329f508c2d5c325fdae91bd2be736b16739c52b"}},"tags":["nested-reference","unchanged"],"summary":"This specification proposes a protocol to create grouped symmetric\n keys and distribute them amongst communicating peers. This protocol\n has the following advantages: 1) virtually invisible to operator, 2)\n no central key distribution site is needed, 3) only group members\n have the key, 4) sender or receiver oriented operation, 5) can make\n use of multicast communications protocols.\n\n1 Introduction\n\n This document describes an architecture for the management of\n cryptographic keys for multicast communications. We identify the\n roles and responsibilities of communications system elements in\n accomplishing multicast key management, define security and\n functional requirements of each, and provide a detailed introduction\n to the Group Key Management Protocol (GKMP) which provides the\n ability to create and distribute keys within arbitrary-sized groups\n without the intervention of a global/c","scope_keywords":["2094","algorithm","algorithms","authentication","authorization","encryption","identification","key","keys","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2337","folder":"IETF/RFC-2337","source":"IETF/RFC-2337/RFC-2337.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2627","folder":"IETF/RFC-2627","source":"IETF/RFC-2627/RFC-2627.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3740","folder":"IETF/RFC-3740","source":"IETF/RFC-3740/RFC-3740.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null}],"search_text":"IETF RFC 2094 This specification proposes a protocol to create grouped symmetric\n keys and distribute them amongst communicating peers. This protocol\n has the following advantages: 1) virtually invisible to operator, 2)\n no central key distribution site is needed, 3) only group members\n have the key, 4) sender or receiver oriented operation, 5) can make\n use of multicast communications protocols.\n\n1 Introduction\n\n This document describes an architecture for the management of\n cryptographic keys for multicast communications. We identify the\n roles and responsibilities of communications system elements in\n accomplishing multicast key management, define security and\n functional requirements of each, and provide a detailed introduction\n to the Group Key Management Protocol (GKMP) which provides the\n ability to create and distribute keys within arbitrary-sized groups\n without the intervention of a global/c 2094 algorithm algorithms authentication authorization encryption identification key keys management trust nested-reference unchanged"},{"id":"IETF RFC 4382","type":"specification","body":"IETF","designation":"RFC 4382","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4382.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4382.txt","https://www.rfc-editor.org/rfc/rfc4382.pdf"],"folder":"IETF/RFC-4382","files":{"txt":{"path":"standards/IETF/RFC-4382/RFC-4382.txt","sha256":"b7fe1651bbe6b5c9dacc7e3b48e276243edc6613f00e183759584b7fea0d80e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor Multiprotocol Label Switching Layer-3 Virtual Private\n Networks on a Multiprotocol Label Switching (MPLS) Label Switching\n Router (LSR) supporting this feature.\n\nNadeau & van Der Linde Standards Track [Page 1]\n\f\nRFC 4382 MPLS-L3VPN-STD-MIB February 2006","scope_keywords":["4382","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null}],"search_text":"IETF RFC 4382 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor Multiprotocol Label Switching Layer-3 Virtual Private\n Networks on a Multiprotocol Label Switching (MPLS) Label Switching\n Router (LSR) supporting this feature.\n\nNadeau & van Der Linde Standards Track [Page 1]\n\f\nRFC 4382 MPLS-L3VPN-STD-MIB February 2006 4382 key management path nested-reference unchanged"},{"id":"IETF RFC 2097","type":"specification","body":"IETF","designation":"RFC 2097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2097.txt","https://www.rfc-editor.org/rfc/rfc2097.pdf"],"folder":"IETF/RFC-2097","files":{"txt":{"path":"standards/IETF/RFC-2097/RFC-2097.txt","sha256":"49f9347ab0b541b1f6a3b26299c041909d65af2c9e03a53e87429198a6dc12cf"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n The NBF protocol [3] was originally called the NetBEUI protocol. This\n document defines the Network Control Protocol for establishing and\n configuring the NBF protocol over PPP.\n\n The NBFCP protocol is only applicable for an end system to connect to\n a peer system or the LAN that peer system is connected to. It is not\n applicable for connecting two LANs together due to NetBIOS name\n limitations and NetBIOS name defense mechanisms.","scope_keywords":["2097"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2097 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links. PPP\n defines an extensible Link Control Protocol, and proposes a family of\n Network Control Protocols for establishing and configuring different\n network-layer protocols.\n\n The NBF protocol [3] was originally called the NetBEUI protocol. This\n document defines the Network Control Protocol for establishing and\n configuring the NBF protocol over PPP.\n\n The NBFCP protocol is only applicable for an end system to connect to\n a peer system or the LAN that peer system is connected to. It is not\n applicable for connecting two LANs together due to NetBIOS name\n limitations and NetBIOS name defense mechanisms. 2097 nested-reference unchanged"},{"id":"IETF RFC 2404","type":"specification","body":"IETF","designation":"RFC 2404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2404.txt","https://www.rfc-editor.org/rfc/rfc2404.pdf"],"folder":"IETF/RFC-2404","files":{"txt":{"path":"standards/IETF/RFC-2404/RFC-2404.txt","sha256":"6efc5b1329287d0a843554ac3be35a3424380338761cc9ad24c9f18020279369"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the HMAC algorithm [RFC-2104] in\n conjunction with the SHA-1 algorithm [FIPS-180-1] as an\n authentication mechanism within the revised IPSEC Encapsulating\n Security Payload [ESP] and the revised IPSEC Authentication Header\n [AH]. HMAC with SHA-1 provides data origin authentication and\n integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of SHA-1 [FIPS-180-1] combined with HMAC\n [RFC-2104] as a keyed authentication mechanism within the context of\n the Encapsulating Security Payload and the Authentication Header.\n The goal of HMAC-SHA-1-96 is to ensure that the packet is authentic\n and cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authentication as provided by HMA","scope_keywords":["2404","algorithm","algorithms","authentication","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 2404 This memo describes the use of the HMAC algorithm [RFC-2104] in\n conjunction with the SHA-1 algorithm [FIPS-180-1] as an\n authentication mechanism within the revised IPSEC Encapsulating\n Security Payload [ESP] and the revised IPSEC Authentication Header\n [AH]. HMAC with SHA-1 provides data origin authentication and\n integrity protection.\n\n Further information on the other components necessary for ESP and AH\n implementations is provided by [Thayer97a].\n\n1. Introduction\n\n This memo specifies the use of SHA-1 [FIPS-180-1] combined with HMAC\n [RFC-2104] as a keyed authentication mechanism within the context of\n the Encapsulating Security Payload and the Authentication Header.\n The goal of HMAC-SHA-1-96 is to ensure that the packet is authentic\n and cannot be modified in transit.\n\n HMAC is a secret key authentication algorithm. Data integrity and\n data origin authentication as provided by HMA 2404 algorithm algorithms authentication hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 2756","type":"specification","body":"IETF","designation":"RFC 2756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2756.txt","https://www.rfc-editor.org/rfc/rfc2756.pdf"],"folder":"IETF/RFC-2756","files":{"txt":{"path":"standards/IETF/RFC-2756/RFC-2756.txt","sha256":"fe320cc690f7e70660d601e39043a602a5ce2551a2a979fdc466065b8ec348c7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes HTCP, a protocol for discovering HTTP caches\n and cached data, managing sets of HTTP caches, and monitoring cache\n activity. This is an experimental protocol, one among several\n proposals to perform these functions.\n\n1. Definitions, Rationale and Scope","scope_keywords":["2756","authentication","crl","http","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3040","folder":"IETF/RFC-3040","source":"IETF/RFC-3040/RFC-3040.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2756 This document describes HTCP, a protocol for discovering HTTP caches\n and cached data, managing sets of HTTP caches, and monitoring cache\n activity. This is an experimental protocol, one among several\n proposals to perform these functions.\n\n1. Definitions, Rationale and Scope 2756 authentication crl http management nested-reference unchanged"},{"id":"IETF RFC 2797","type":"specification","body":"IETF","designation":"RFC 2797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2797.txt","https://www.rfc-editor.org/rfc/rfc2797.pdf"],"folder":"IETF/RFC-2797","files":{"txt":{"path":"standards/IETF/RFC-2797/RFC-2797.txt","sha256":"86bf563e1524be1506caa4fa8cdb173314d3a64e5b1c23df6d65d5ef3146da24"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Certificate Management protocol using CMS\n (CMC). This protocol addresses two immediate needs within the\n Internet PKI community:\n\n 1. The need for an interface to public key certification products and\n services based on [CMS] and [PKCS10], and\n 2. The need in [SMIMEV3] for a certificate enrollment protocol for\n DSA-signed certificates with Diffie-Hellman public keys.\n\n A small number of additional services are defined to supplement the\n core certificate request service.\n\n Throughout this specification the term CMS is used to refer to both\n [CMS] and [PKCS7]. For both signedData and envelopedData, CMS is a\n superset of the PKCS7. In general, the use of PKCS7 in this document\n is aligned to the Cryptographic Message Syntax [CMS] that provides a\n superset of the PKCS7 syntax. The term CMC refers to this\n specification.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\",","scope_keywords":["2797","algorithm","algorithms","certificate","certificates","crl","encryption","issuer","key","keys","management","pki","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null}],"search_text":"IETF RFC 2797 This document defines a Certificate Management protocol using CMS\n (CMC). This protocol addresses two immediate needs within the\n Internet PKI community:\n\n 1. The need for an interface to public key certification products and\n services based on [CMS] and [PKCS10], and\n 2. The need in [SMIMEV3] for a certificate enrollment protocol for\n DSA-signed certificates with Diffie-Hellman public keys.\n\n A small number of additional services are defined to supplement the\n core certificate request service.\n\n Throughout this specification the term CMS is used to refer to both\n [CMS] and [PKCS7]. For both signedData and envelopedData, CMS is a\n superset of the PKCS7. In general, the use of PKCS7 in this document\n is aligned to the Cryptographic Message Syntax [CMS] that provides a\n superset of the PKCS7 syntax. The term CMC refers to this\n specification.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", 2797 algorithm algorithms certificate certificates crl encryption issuer key keys management pki revocation nested-reference unchanged"},{"id":"IETF RFC 2875","type":"specification","body":"IETF","designation":"RFC 2875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2875.txt","https://www.rfc-editor.org/rfc/rfc2875.pdf"],"folder":"IETF/RFC-2875","files":{"txt":{"path":"standards/IETF/RFC-2875/RFC-2875.txt","sha256":"43ab2dd5f257371f942ae49e1087e1abe334ae83a4e5b93a2a2b7bbdbe31173c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes two methods for producing an integrity check\n value from a Diffie-Hellman key pair. This behavior is needed for\n such operations as creating the signature of a PKCS #10 certification\n request. These algorithms are designed to provide a proof-of-\n possession rather than general purpose signing.\n\n1. Introduction\n\n PKCS #10 [RFC2314] defines a syntax for certification requests. It\n assumes that the public key being requested for certification\n corresponds to an algorithm that is capable of signing/encrypting.\n Diffie-Hellman (DH) is a key agreement algorithm and as such cannot\n be directly used for signing or encryption.\n\n This document describes two new proof-of-possession algorithms using\n the Diffie-Hellman key agreement process to provide a shared secret\n as the basis of an integrity check value. In the first algorithm,\n the value is constructed for a specific re","scope_keywords":["2875","algorithm","algorithms","certificate","encryption","hash","issuer","key","keys","path","pki","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null}],"search_text":"IETF RFC 2875 This document describes two methods for producing an integrity check\n value from a Diffie-Hellman key pair. This behavior is needed for\n such operations as creating the signature of a PKCS #10 certification\n request. These algorithms are designed to provide a proof-of-\n possession rather than general purpose signing.\n\n1. Introduction\n\n PKCS #10 [RFC2314] defines a syntax for certification requests. It\n assumes that the public key being requested for certification\n corresponds to an algorithm that is capable of signing/encrypting.\n Diffie-Hellman (DH) is a key agreement algorithm and as such cannot\n be directly used for signing or encryption.\n\n This document describes two new proof-of-possession algorithms using\n the Diffie-Hellman key agreement process to provide a shared secret\n as the basis of an integrity check value. In the first algorithm,\n the value is constructed for a specific re 2875 algorithm algorithms certificate encryption hash issuer key keys path pki signature subject nested-reference unchanged"},{"id":"IETF RFC 4004","type":"specification","body":"IETF","designation":"RFC 4004","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4004.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4004.txt","https://www.rfc-editor.org/rfc/rfc4004.pdf"],"folder":"IETF/RFC-4004","files":{"txt":{"path":"standards/IETF/RFC-4004/RFC-4004.txt","sha256":"2419c8128a4d704d435a8ab8dec8474773e556a3b05f93f760e539216a9feddd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Diameter application that allows a Diameter\n server to authenticate, authorize and collect accounting information\n for Mobile IPv4 services rendered to a mobile node. Combined with\n the Inter-Realm capability of the base protocol, this application\n allows mobile nodes to receive service from foreign service\n providers. Diameter Accounting messages will be used by the foreign\n and home agents to transfer usage information to the Diameter\n servers.","scope_keywords":["4004","algorithm","authorization","key","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 4004 This document specifies a Diameter application that allows a Diameter\n server to authenticate, authorize and collect accounting information\n for Mobile IPv4 services rendered to a mobile node. Combined with\n the Inter-Realm capability of the base protocol, this application\n allows mobile nodes to receive service from foreign service\n providers. Diameter Accounting messages will be used by the foreign\n and home agents to transfer usage information to the Diameter\n servers. 4004 algorithm authorization key management timestamp nested-reference unchanged"},{"id":"IETF RFC 4226","type":"specification","body":"IETF","designation":"RFC 4226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4226.txt","https://www.rfc-editor.org/rfc/rfc4226.pdf"],"folder":"IETF/RFC-4226","files":{"txt":{"path":"standards/IETF/RFC-4226/RFC-4226.txt","sha256":"db6974cd02ca33560ec3a191ee9b1016067cd11d1f5d89e7efa36be69482229d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an algorithm to generate one-time password\n values, based on Hashed Message Authentication Code (HMAC). A\n security analysis of the algorithm is presented, and important\n parameters related to the secure deployment of the algorithm are\n discussed. The proposed algorithm can be used across a wide range of\n network applications ranging from remote Virtual Private Network\n (VPN) access, Wi-Fi network logon to transaction-oriented Web\n applications.\n\n This work is a joint effort by the OATH (Open AuTHentication)\n membership to specify an algorithm that can be freely distributed to\n the technical community. The authors believe that a common and\n shared algorithm will facilitate adoption of two-factor\n authentication on the Internet by enabling interoperability across\n commercial and open-source implementations.\n\nM'Raihi, et al. Informational [Page 1]\n\f\nRFC 4226 HOTP Al","scope_keywords":["4226","algorithm","authentication","hash","management","pid","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4449","folder":"IETF/RFC-4449","source":"IETF/RFC-4449/RFC-4449.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null}],"search_text":"IETF RFC 4226 This document describes an algorithm to generate one-time password\n values, based on Hashed Message Authentication Code (HMAC). A\n security analysis of the algorithm is presented, and important\n parameters related to the secure deployment of the algorithm are\n discussed. The proposed algorithm can be used across a wide range of\n network applications ranging from remote Virtual Private Network\n (VPN) access, Wi-Fi network logon to transaction-oriented Web\n applications.\n\n This work is a joint effort by the OATH (Open AuTHentication)\n membership to specify an algorithm that can be freely distributed to\n the technical community. The authors believe that a common and\n shared algorithm will facilitate adoption of two-factor\n authentication on the Internet by enabling interoperability across\n commercial and open-source implementations.\n\nM'Raihi, et al. Informational [Page 1]\n\f\nRFC 4226 HOTP Al 4226 algorithm authentication hash management pid validation nested-reference unchanged"},{"id":"IETF RFC 4231","type":"specification","body":"IETF","designation":"RFC 4231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4231.txt","https://www.rfc-editor.org/rfc/rfc4231.pdf"],"folder":"IETF/RFC-4231","files":{"txt":{"path":"standards/IETF/RFC-4231/RFC-4231.txt","sha256":"72178527ce93500e730bc8eb182b857e583096d652b64ece0879c52ba1df973b"}},"tags":["nested-reference","unchanged"],"summary":"This document provides test vectors for the HMAC-SHA-224,\n HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 message authentication\n schemes. It also provides ASN.1 object identifiers and Uniform\n Resource Identifiers (URIs) to identify use of these schemes in\n protocols. The test vectors provided in this document may be used\n for conformance testing.\n\nNystrom Standards Track [Page 1]\n\f\nRFC 4231 HMAC-SHA Identifiers and Test Vectors December 2005","scope_keywords":["4231","algorithm","authentication","hash","http","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 4231 This document provides test vectors for the HMAC-SHA-224,\n HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 message authentication\n schemes. It also provides ASN.1 object identifiers and Uniform\n Resource Identifiers (URIs) to identify use of these schemes in\n protocols. The test vectors provided in this document may be used\n for conformance testing.\n\nNystrom Standards Track [Page 1]\n\f\nRFC 4231 HMAC-SHA Identifiers and Test Vectors December 2005 4231 algorithm authentication hash http key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 4307","type":"specification","body":"IETF","designation":"RFC 4307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4307.txt","https://www.rfc-editor.org/rfc/rfc4307.pdf"],"folder":"IETF/RFC-4307","files":{"txt":{"path":"standards/IETF/RFC-4307/RFC-4307.txt","sha256":"2a736e21c77c2462440f1bff9894512d9e796232c59754755a8c764897654d42"}},"tags":["nested-reference","unchanged"],"summary":"The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Internet Key\n Exchange (IKE (RFC 2409) and IKEv2) provide a mechanism to negotiate\n which algorithms should be used in any given association. However,\n to ensure interoperability between disparate implementations, it is\n necessary to specify a set of mandatory-to-implement algorithms to\n ensure that there is at least one algorithm that all implementations\n will have available. This document defines the current set of\n algorithms that are mandatory to implement as part of IKEv2, as well\n as algorithms that should be implemented because they may be promoted\n to mandatory at some future time.\n\n1. Introduction\n\n The Internet Key Exchange protocol provides for the negotiation of\n cryptographic algorithms between both endpoints of a cryptographic\n\n association. Different impl","scope_keywords":["4307","algorithm","algorithms","encryption","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null}],"search_text":"IETF RFC 4307 The IPsec series of protocols makes use of various cryptographic\n algorithms in order to provide security services. The Internet Key\n Exchange (IKE (RFC 2409) and IKEv2) provide a mechanism to negotiate\n which algorithms should be used in any given association. However,\n to ensure interoperability between disparate implementations, it is\n necessary to specify a set of mandatory-to-implement algorithms to\n ensure that there is at least one algorithm that all implementations\n will have available. This document defines the current set of\n algorithms that are mandatory to implement as part of IKEv2, as well\n as algorithms that should be implemented because they may be promoted\n to mandatory at some future time.\n\n1. Introduction\n\n The Internet Key Exchange protocol provides for the negotiation of\n cryptographic algorithms between both endpoints of a cryptographic\n\n association. Different impl 4307 algorithm algorithms encryption key keys subject nested-reference unchanged"},{"id":"IETF RFC 4308","type":"specification","body":"IETF","designation":"RFC 4308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4308.txt","https://www.rfc-editor.org/rfc/rfc4308.pdf"],"folder":"IETF/RFC-4308","files":{"txt":{"path":"standards/IETF/RFC-4308/RFC-4308.txt","sha256":"07f357e27d525e9b2ccfb6392d3664ccd8e34259c89b0932e71b5db6a48e2f93"}},"tags":["nested-reference","unchanged"],"summary":"The IPsec, Internet Key Exchange (IKE), and IKEv2 protocols rely on\n security algorithms to provide privacy and authentication between the\n initiator and responder. There are many such algorithms available,\n and two IPsec systems cannot interoperate unless they are using the\n same algorithms. This document specifies optional suites of\n algorithms and attributes that can be used to simplify the\n administration of IPsec when used in manual keying mode, with IKEv1\n or with IKEv2.\n\n1. Introduction\n\n This document is a companion to IPsec [RFC2401] and its two key\n exchange protocols, IKE [RFC2409] and IKEv2 [IKEv2]. Like most\n security protocols, IPsec, IKE, and IKEv2 allow users to chose which\n cryptographic algorithms they want to use to meet their security\n needs.\n\n Implementation experience with IPsec in manual key mode and with IKE\n has shown that there are so many choices for typical sy","scope_keywords":["4308","algorithm","algorithms","attribute","attributes","authentication","encryption","key","keys","management","policies","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null}],"search_text":"IETF RFC 4308 The IPsec, Internet Key Exchange (IKE), and IKEv2 protocols rely on\n security algorithms to provide privacy and authentication between the\n initiator and responder. There are many such algorithms available,\n and two IPsec systems cannot interoperate unless they are using the\n same algorithms. This document specifies optional suites of\n algorithms and attributes that can be used to simplify the\n administration of IPsec when used in manual keying mode, with IKEv1\n or with IKEv2.\n\n1. Introduction\n\n This document is a companion to IPsec [RFC2401] and its two key\n exchange protocols, IKE [RFC2409] and IKEv2 [IKEv2]. Like most\n security protocols, IPsec, IKE, and IKEv2 allow users to chose which\n cryptographic algorithms they want to use to meet their security\n needs.\n\n Implementation experience with IPsec in manual key mode and with IKE\n has shown that there are so many choices for typical sy 4308 algorithm algorithms attribute attributes authentication encryption key keys management policies registered nested-reference unchanged"},{"id":"IETF RFC 4357","type":"specification","body":"IETF","designation":"RFC 4357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4357.txt","https://www.rfc-editor.org/rfc/rfc4357.pdf"],"folder":"IETF/RFC-4357","files":{"txt":{"path":"standards/IETF/RFC-4357/RFC-4357.txt","sha256":"384473bcec574b8934e45346006d91efaff7f92bdfd868ec3913cc713f6e21d2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the cryptographic algorithms and parameters\n supplementary to the original GOST specifications, GOST 28147-89,\n GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94, for use in\n Internet applications.","scope_keywords":["4357","algorithm","algorithms","encryption","hash","key","keys","pki"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 5830","folder":"IETF/RFC-5830","source":"IETF/RFC-5830/RFC-5830.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null}],"search_text":"IETF RFC 4357 This document describes the cryptographic algorithms and parameters\n supplementary to the original GOST specifications, GOST 28147-89,\n GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94, for use in\n Internet applications. 4357 algorithm algorithms encryption hash key keys pki nested-reference unchanged"},{"id":"IETF RFC 4366","type":"specification","body":"IETF","designation":"RFC 4366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4366.txt","https://www.rfc-editor.org/rfc/rfc4366.pdf"],"folder":"IETF/RFC-4366","files":{"txt":{"path":"standards/IETF/RFC-4366/RFC-4366.txt","sha256":"f220abd9682dbbf2d61cc545519435200cda8a29773dbe1978d250d3581e6e03"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions that may be used to add\n functionality to Transport Layer Security (TLS). It provides both\n generic extension mechanisms for the TLS handshake client and server\n hellos, and specific extensions using these generic mechanisms.\n\n The extensions may be used by TLS clients and servers. The\n extensions are backwards compatible: communication is possible\n between TLS clients that support the extensions and TLS servers that\n do not support the extensions, and vice versa.\n\nBlake-Wilson, et al. Standards Track [Page 1]\n\f\nRFC 4366 TLS Extensions April 2006","scope_keywords":["4366","certificate","crl","key","keys","ocsp","revocation","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4680","folder":"IETF/RFC-4680","source":"IETF/RFC-4680/RFC-4680.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4366 This document describes extensions that may be used to add\n functionality to Transport Layer Security (TLS). It provides both\n generic extension mechanisms for the TLS handshake client and server\n hellos, and specific extensions using these generic mechanisms.\n\n The extensions may be used by TLS clients and servers. The\n extensions are backwards compatible: communication is possible\n between TLS clients that support the extensions and TLS servers that\n do not support the extensions, and vice versa.\n\nBlake-Wilson, et al. Standards Track [Page 1]\n\f\nRFC 4366 TLS Extensions April 2006 4366 certificate crl key keys ocsp revocation tls trust nested-reference unchanged"},{"id":"IETF RFC 4383","type":"specification","body":"IETF","designation":"RFC 4383","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4383.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4383.txt","https://www.rfc-editor.org/rfc/rfc4383.pdf"],"folder":"IETF/RFC-4383","files":{"txt":{"path":"standards/IETF/RFC-4383/RFC-4383.txt","sha256":"5a2073b57fca2c9bf5a6a8596234c496155226971cfa1cf2db1c1ab1a2f108ce"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Timed Efficient Stream Loss-\n tolerant Authentication (RFC 4082) transform within the Secure Real-\n time Transport Protocol (SRTP), to provide data origin authentication\n for multicast and broadcast data streams.\n\nBaugher & Carrara Standards Track [Page 1]\n\f\nRFC 4383 TESLA-SRTP February 2006","scope_keywords":["4383","algorithm","algorithms","authentication","key","management","profile","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 4383 This memo describes the use of the Timed Efficient Stream Loss-\n tolerant Authentication (RFC 4082) transform within the Secure Real-\n time Transport Protocol (SRTP), to provide data origin authentication\n for multicast and broadcast data streams.\n\nBaugher & Carrara Standards Track [Page 1]\n\f\nRFC 4383 TESLA-SRTP February 2006 4383 algorithm algorithms authentication key management profile signature signatures nested-reference unchanged"},{"id":"IETF RFC 4467","type":"specification","body":"IETF","designation":"RFC 4467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4467.txt","https://www.rfc-editor.org/rfc/rfc4467.pdf"],"folder":"IETF/RFC-4467","files":{"txt":{"path":"standards/IETF/RFC-4467/RFC-4467.txt","sha256":"13087160371cba00dcf67411f077a779345334970e3cc242b1d43cd32c40238c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the URLAUTH extension to the Internet Message\n Access Protocol (IMAP) (RFC 3501) and the IMAP URL Scheme (IMAPURL)\n (RFC 2192). This extension provides a means by which an IMAP client\n can use URLs carrying authorization to access limited message data on\n the IMAP server.\n\n An IMAP server that supports this extension indicates this with a\n capability name of \"URLAUTH\".\n\n1. Introduction\n\n In [IMAPURL], a URL of the form imap://fred@example.com/INBOX/;uid=20\n requires authorization as userid \"fred\". However, [IMAPURL] implies\n that it only supports authentication and confuses the concepts of\n authentication and authorization.\n\n The URLAUTH extension defines an authorization mechanism for IMAP\n URLs to replace [IMAPURL]'s authentication-only mechanism. URLAUTH\n conveys authorization in the URL string itself and reuses a portion\n of the syntax of the [IMAPURL] authent","scope_keywords":["4467","algorithm","authentication","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null}],"search_text":"IETF RFC 4467 This document describes the URLAUTH extension to the Internet Message\n Access Protocol (IMAP) (RFC 3501) and the IMAP URL Scheme (IMAPURL)\n (RFC 2192). This extension provides a means by which an IMAP client\n can use URLs carrying authorization to access limited message data on\n the IMAP server.\n\n An IMAP server that supports this extension indicates this with a\n capability name of \"URLAUTH\".\n\n1. Introduction\n\n In [IMAPURL], a URL of the form imap://fred@example.com/INBOX/;uid=20\n requires authorization as userid \"fred\". However, [IMAPURL] implies\n that it only supports authentication and confuses the concepts of\n authentication and authorization.\n\n The URLAUTH extension defines an authorization mechanism for IMAP\n URLs to replace [IMAPURL]'s authentication-only mechanism. URLAUTH\n conveys authorization in the URL string itself and reuses a portion\n of the syntax of the [IMAPURL] authent 4467 algorithm authentication authorization key nested-reference unchanged"},{"id":"IETF RFC 4493","type":"specification","body":"IETF","designation":"RFC 4493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4493.txt","https://www.rfc-editor.org/rfc/rfc4493.pdf"],"folder":"IETF/RFC-4493","files":{"txt":{"path":"standards/IETF/RFC-4493/RFC-4493.txt","sha256":"252850ac038a44e931fdce6cb02b444a18ed1da0c9e212bfdd1da0ed3366fc1c"}},"tags":["nested-reference","unchanged"],"summary":"The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC), which is equivalent to the One-Key CBC MAC1 (OMAC1) submitted\n by Iwata and Kurosawa. This memo specifies an authentication\n algorithm based on CMAC with the 128-bit Advanced Encryption Standard\n (AES). This new authentication algorithm is named AES-CMAC. The\n purpose of this document is to make the AES-CMAC algorithm\n conveniently available to the Internet Community.\n\nSong, et al. Informational [Page 1]\n\f\nRFC 4493 The AES-CMAC Algorithm June 2006","scope_keywords":["4493","algorithm","authentication","encryption","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4494","folder":"IETF/RFC-4494","source":"IETF/RFC-4494/RFC-4494.txt","version":null},{"body":"IETF","designation":"RFC 4615","folder":"IETF/RFC-4615","source":"IETF/RFC-4615/RFC-4615.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 4493 The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC), which is equivalent to the One-Key CBC MAC1 (OMAC1) submitted\n by Iwata and Kurosawa. This memo specifies an authentication\n algorithm based on CMAC with the 128-bit Advanced Encryption Standard\n (AES). This new authentication algorithm is named AES-CMAC. The\n purpose of this document is to make the AES-CMAC algorithm\n conveniently available to the Internet Community.\n\nSong, et al. Informational [Page 1]\n\f\nRFC 4493 The AES-CMAC Algorithm June 2006 4493 algorithm authentication encryption hash key nested-reference unchanged"},{"id":"IETF RFC 4494","type":"specification","body":"IETF","designation":"RFC 4494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4494.txt","https://www.rfc-editor.org/rfc/rfc4494.pdf"],"folder":"IETF/RFC-4494","files":{"txt":{"path":"standards/IETF/RFC-4494/RFC-4494.txt","sha256":"eb7333f33e96221f175f61787d03fecb2639f0b502a03c2d2442a6199d537ddb"}},"tags":["nested-reference","unchanged"],"summary":"The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC), which is equivalent to the One-Key CBC-MAC1 (OMAC1) algorithm\n submitted by Iwata and Kurosawa. OMAC1 efficiently reduces the key\n size of Extended Cipher Block Chaining mode (XCBC). This memo\n specifies the use of CMAC mode on the authentication mechanism of the\n IPsec Encapsulating Security Payload (ESP) and the Authentication\n Header (AH) protocols. This new algorithm is named AES-CMAC-96.\n\nSong, et al. Standards Track [Page 1]\n\f\nRFC 4494 The AES-CMAC Algorithm and IPsec June 2006\n\n1. Introduction\n\n The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC). CMAC [NIST-CMAC] is a message authentication code that is\n based on a symmetric key block cipher such as the Advanced En","scope_keywords":["4494","algorithm","algorithms","authentication","encryption","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4494 The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC), which is equivalent to the One-Key CBC-MAC1 (OMAC1) algorithm\n submitted by Iwata and Kurosawa. OMAC1 efficiently reduces the key\n size of Extended Cipher Block Chaining mode (XCBC). This memo\n specifies the use of CMAC mode on the authentication mechanism of the\n IPsec Encapsulating Security Payload (ESP) and the Authentication\n Header (AH) protocols. This new algorithm is named AES-CMAC-96.\n\nSong, et al. Standards Track [Page 1]\n\f\nRFC 4494 The AES-CMAC Algorithm and IPsec June 2006\n\n1. Introduction\n\n The National Institute of Standards and Technology (NIST) has\n recently specified the Cipher-based Message Authentication Code\n (CMAC). CMAC [NIST-CMAC] is a message authentication code that is\n based on a symmetric key block cipher such as the Advanced En 4494 algorithm algorithms authentication encryption hash key nested-reference unchanged"},{"id":"IETF RFC 4507","type":"specification","body":"IETF","designation":"RFC 4507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4507.txt","https://www.rfc-editor.org/rfc/rfc4507.pdf"],"folder":"IETF/RFC-4507","files":{"txt":{"path":"standards/IETF/RFC-4507/RFC-4507.txt","sha256":"4e2e511415de200e8dfe30e7dbd9926fcb290678b6556d022197ae9ab31ed4b7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that enables the Transport Layer\n Security (TLS) server to resume sessions and avoid keeping per-client\n session state. The TLS server encapsulates the session state into a\n ticket and forwards it to the client. The client can subsequently\n resume a session using the obtained ticket.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 4507 Stateless TLS Session Resumption May 2006","scope_keywords":["4507","certificate","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4507 This document describes a mechanism that enables the Transport Layer\n Security (TLS) server to resume sessions and avoid keeping per-client\n session state. The TLS server encapsulates the session state into a\n ticket and forwards it to the client. The client can subsequently\n resume a session using the obtained ticket.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 4507 Stateless TLS Session Resumption May 2006 4507 certificate key management tls nested-reference unchanged"},{"id":"IETF RFC 4634","type":"specification","body":"IETF","designation":"RFC 4634","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4634.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4634.txt","https://www.rfc-editor.org/rfc/rfc4634.pdf"],"folder":"IETF/RFC-4634","files":{"txt":{"path":"standards/IETF/RFC-4634/RFC-4634.txt","sha256":"5476447e7f30de0358e0ec6f90afb6373e40284171c8f2dcbb680757e317e742"}},"tags":["nested-reference","unchanged"],"summary":"The United States of America has adopted a suite of Secure Hash\n Algorithms (SHAs), including four beyond SHA-1, as part of a Federal\n Information Processing Standard (FIPS), specifically SHA-224 (RFC\n 3874), SHA-256, SHA-384, and SHA-512. The purpose of this document\n is to make source code performing these hash functions conveniently\n available to the Internet community. The sample code supports input\n strings of arbitrary bit length. SHA-1's sample code from RFC 3174\n has also been updated to handle input strings of arbitrary bit\n length. Most of the text herein was adapted by the authors from FIPS\n 180-2.\n\n Code to perform SHA-based HMACs, with arbitrary bit length text, is\n also included.\n\nEastlake 3rd & Hansen Informational [Page 1]\n\f\nRFC 4634 SHAs and HMAC-SHAs July 2006","scope_keywords":["4634","algorithm","algorithms","authentication","hash","key","license","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6229","folder":"IETF/RFC-6229","source":"IETF/RFC-6229/RFC-6229.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null}],"search_text":"IETF RFC 4634 The United States of America has adopted a suite of Secure Hash\n Algorithms (SHAs), including four beyond SHA-1, as part of a Federal\n Information Processing Standard (FIPS), specifically SHA-224 (RFC\n 3874), SHA-256, SHA-384, and SHA-512. The purpose of this document\n is to make source code performing these hash functions conveniently\n available to the Internet community. The sample code supports input\n strings of arbitrary bit length. SHA-1's sample code from RFC 3174\n has also been updated to handle input strings of arbitrary bit\n length. Most of the text herein was adapted by the authors from FIPS\n 180-2.\n\n Code to perform SHA-based HMACs, with arbitrary bit length text, is\n also included.\n\nEastlake 3rd & Hansen Informational [Page 1]\n\f\nRFC 4634 SHAs and HMAC-SHAs July 2006 4634 algorithm algorithms authentication hash key license presentation signature nested-reference unchanged"},{"id":"IETF RFC 4758","type":"specification","body":"IETF","designation":"RFC 4758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4758.txt","https://www.rfc-editor.org/rfc/rfc4758.pdf"],"folder":"IETF/RFC-4758","files":{"txt":{"path":"standards/IETF/RFC-4758/RFC-4758.txt","sha256":"35923d665730a7c57728bb47031de427cb39b29d81e675c879a0b8cbe7612291"}},"tags":["nested-reference","unchanged"],"summary":"This document constitutes Revision 1 of Cryptographic Token Key\n Initialization Protocol (CT-KIP) Version 1.0 from RSA Laboratories'\n One-Time Password Specifications (OTPS) series. The body of this\n document, except for the intellectual property considerations\n section, is taken from the CT-KIP Version 1.0 document, but comments\n received during the IETF review are reflected; hence, the status of a\n revised version. As no \"bits-on-the-wire\" have changed, the protocol\n specified herein is compatible with CT-KIP Version 1.0.\n\n CT-KIP is a client-server protocol for initialization (and\n configuration) of cryptographic tokens. The protocol requires\n neither private-key capabilities in the cryptographic tokens, nor an\n established public-key infrastructure. Provisioned (or generated)\n secrets will only be available to the server and the cryptographic\n token itself.\n\nNystroem Informational [P","scope_keywords":["4758","authentication","encryption","http","identification","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null}],"search_text":"IETF RFC 4758 This document constitutes Revision 1 of Cryptographic Token Key\n Initialization Protocol (CT-KIP) Version 1.0 from RSA Laboratories'\n One-Time Password Specifications (OTPS) series. The body of this\n document, except for the intellectual property considerations\n section, is taken from the CT-KIP Version 1.0 document, but comments\n received during the IETF review are reflected; hence, the status of a\n revised version. As no \"bits-on-the-wire\" have changed, the protocol\n specified herein is compatible with CT-KIP Version 1.0.\n\n CT-KIP is a client-server protocol for initialization (and\n configuration) of cryptographic tokens. The protocol requires\n neither private-key capabilities in the cryptographic tokens, nor an\n established public-key infrastructure. Provisioned (or generated)\n secrets will only be available to the server and the cryptographic\n token itself.\n\nNystroem Informational [P 4758 authentication encryption http identification key keys trust nested-reference unchanged"},{"id":"IETF RFC 4868","type":"specification","body":"IETF","designation":"RFC 4868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4868.txt","https://www.rfc-editor.org/rfc/rfc4868.pdf"],"folder":"IETF/RFC-4868","files":{"txt":{"path":"standards/IETF/RFC-4868/RFC-4868.txt","sha256":"40feb304d348e909ad224a79507ebd56012b257f03c88fc472c753a000dfadbe"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes the use of Hashed Message Authentication\n Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512\n algorithms in IPsec. These algorithms may be used as the basis for\n data origin authentication and integrity verification mechanisms for\n the Authentication Header (AH), Encapsulating Security Payload (ESP),\n Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also\n as Pseudo-Random Functions (PRFs) for IKE and IKEv2. Truncated\n output lengths are specified for the authentication-related variants,\n with the corresponding algorithms designated as HMAC-SHA-256-128,\n HMAC-SHA-384-192, and HMAC-SHA-512-256. The PRF variants are not\n truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and\n PRF-HMAC-SHA-512.\n\nKelly & Frankel Standards Track [Page 1]\n\f\nRFC 4868 HMAC-SHA256, SHA384, and SHA512 in IPsec May 2007","scope_keywords":["4868","algorithm","algorithms","authentication","hash","hashing","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7539","folder":"IETF/RFC-7539","source":"IETF/RFC-7539/RFC-7539.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 4868 This specification describes the use of Hashed Message Authentication\n Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512\n algorithms in IPsec. These algorithms may be used as the basis for\n data origin authentication and integrity verification mechanisms for\n the Authentication Header (AH), Encapsulating Security Payload (ESP),\n Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also\n as Pseudo-Random Functions (PRFs) for IKE and IKEv2. Truncated\n output lengths are specified for the authentication-related variants,\n with the corresponding algorithms designated as HMAC-SHA-256-128,\n HMAC-SHA-384-192, and HMAC-SHA-512-256. The PRF variants are not\n truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and\n PRF-HMAC-SHA-512.\n\nKelly & Frankel Standards Track [Page 1]\n\f\nRFC 4868 HMAC-SHA256, SHA384, and SHA512 in IPsec May 2007 4868 algorithm algorithms authentication hash hashing key keys trust nested-reference unchanged"},{"id":"IETF RFC 5054","type":"specification","body":"IETF","designation":"RFC 5054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5054.txt","https://www.rfc-editor.org/rfc/rfc5054.pdf"],"folder":"IETF/RFC-5054","files":{"txt":{"path":"standards/IETF/RFC-5054/RFC-5054.txt","sha256":"9e02b1964e48b196a7a8c7457d5d07148996f3e39a2b4f1289951ea408e1ce1b"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a technique for using the Secure Remote Password\n protocol as an authentication method for the Transport Layer Security\n protocol.\n\nTaylor, et al. Informational [Page 1]\n\f\nRFC 5054 Using SRP for TLS Authentication November 2007","scope_keywords":["5054","algorithm","authentication","certificate","certificates","encryption","hash","key","keys","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5054 This memo presents a technique for using the Secure Remote Password\n protocol as an authentication method for the Transport Layer Security\n protocol.\n\nTaylor, et al. Informational [Page 1]\n\f\nRFC 5054 Using SRP for TLS Authentication November 2007 5054 algorithm authentication certificate certificates encryption hash key keys profile tls nested-reference unchanged"},{"id":"IETF RFC 5116","type":"specification","body":"IETF","designation":"RFC 5116","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5116.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5116.txt","https://www.rfc-editor.org/rfc/rfc5116.pdf"],"folder":"IETF/RFC-5116","files":{"txt":{"path":"standards/IETF/RFC-5116/RFC-5116.txt","sha256":"8762fee7c85e682fce609c75e0f5040ee7efa8fca96969ffd85df37585e0eda1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines algorithms for Authenticated Encryption with\n Associated Data (AEAD), and defines a uniform interface and a\n registry for such algorithms. The interface and registry can be used\n as an application-independent set of cryptoalgorithm suites. This\n approach provides advantages in efficiency and security, and promotes\n the reuse of crypto implementations.\n\nMcGrew Standards Track [Page 1]\n\f\nRFC 5116 Authenticated Encryption January 2008","scope_keywords":["5116","algorithm","algorithms","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7539","folder":"IETF/RFC-7539","source":"IETF/RFC-7539/RFC-7539.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 5116 This document defines algorithms for Authenticated Encryption with\n Associated Data (AEAD), and defines a uniform interface and a\n registry for such algorithms. The interface and registry can be used\n as an application-independent set of cryptoalgorithm suites. This\n approach provides advantages in efficiency and security, and promotes\n the reuse of crypto implementations.\n\nMcGrew Standards Track [Page 1]\n\f\nRFC 5116 Authenticated Encryption January 2008 5116 algorithm algorithms authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 5191","type":"specification","body":"IETF","designation":"RFC 5191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5191.txt","https://www.rfc-editor.org/rfc/rfc5191.pdf"],"folder":"IETF/RFC-5191","files":{"txt":{"path":"standards/IETF/RFC-5191/RFC-5191.txt","sha256":"edfc049f70e70598861bd76334cb68a7deed0e9d4fc557506db10f6b3cf45198"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Protocol for Carrying Authentication for\n Network Access (PANA), a network-layer transport for Extensible\n Authentication Protocol (EAP) to enable network access authentication\n between clients and access networks. In EAP terms, PANA is a\n UDP-based EAP lower layer that runs between the EAP peer and the EAP\n authenticator.\n\nForsberg, et al. Standards Track [Page 1]\n\f\nRFC 5191 PANA May 2008","scope_keywords":["5191","algorithm","authentication","authorization","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5872","folder":"IETF/RFC-5872","source":"IETF/RFC-5872/RFC-5872.txt","version":null},{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 5191 This document defines the Protocol for Carrying Authentication for\n Network Access (PANA), a network-layer transport for Extensible\n Authentication Protocol (EAP) to enable network access authentication\n between clients and access networks. In EAP terms, PANA is a\n UDP-based EAP lower layer that runs between the EAP peer and the EAP\n authenticator.\n\nForsberg, et al. Standards Track [Page 1]\n\f\nRFC 5191 PANA May 2008 5191 algorithm authentication authorization key keys nested-reference unchanged"},{"id":"IETF RFC 5289","type":"specification","body":"IETF","designation":"RFC 5289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5289.txt","https://www.rfc-editor.org/rfc/rfc5289.pdf"],"folder":"IETF/RFC-5289","files":{"txt":{"path":"standards/IETF/RFC-5289/RFC-5289.txt","sha256":"4bc7e5ae5b8a9e8c022a85530989593ba95bff2d2153aaf2aa5c017f2bd1410b"}},"tags":["nested-reference","unchanged"],"summary":"RFC 4492 describes elliptic curve cipher suites for Transport Layer\n Security (TLS). However, all those cipher suites use HMAC-SHA-1 as\n their Message Authentication Code (MAC) algorithm. This document\n describes sixteen new cipher suites for TLS that specify stronger MAC\n algorithms. Eight use Hashed Message Authentication Code (HMAC) with\n SHA-256 or SHA-384, and eight use AES in Galois Counter Mode (GCM).","scope_keywords":["5289","algorithm","algorithms","authentication","encryption","hash","hashing","key","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null}],"search_text":"IETF RFC 5289 RFC 4492 describes elliptic curve cipher suites for Transport Layer\n Security (TLS). However, all those cipher suites use HMAC-SHA-1 as\n their Message Authentication Code (MAC) algorithm. This document\n describes sixteen new cipher suites for TLS that specify stronger MAC\n algorithms. Eight use Hashed Message Authentication Code (HMAC) with\n SHA-256 or SHA-384, and eight use AES in Galois Counter Mode (GCM). 5289 algorithm algorithms authentication encryption hash hashing key signature tls nested-reference unchanged"},{"id":"IETF RFC 5297","type":"specification","body":"IETF","designation":"RFC 5297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5297.txt","https://www.rfc-editor.org/rfc/rfc5297.pdf"],"folder":"IETF/RFC-5297","files":{"txt":{"path":"standards/IETF/RFC-5297/RFC-5297.txt","sha256":"498a200ee427a67b27d643b3837ac04b1122755d2337b3cbe68de9c52e86a8cd"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes SIV (Synthetic Initialization Vector), a block\n cipher mode of operation. SIV takes a key, a plaintext, and multiple\n variable-length octet strings that will be authenticated but not\n encrypted. It produces a ciphertext having the same length as the\n plaintext and a synthetic initialization vector. Depending on how it\n is used, SIV achieves either the goal of deterministic authenticated\n encryption or the goal of nonce-based, misuse-resistant authenticated\n encryption.\n\nHawkins Informational [Page 1]\n\f\nRFC 5297 SIV-AES October 2008","scope_keywords":["5297","authentication","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null}],"search_text":"IETF RFC 5297 This memo describes SIV (Synthetic Initialization Vector), a block\n cipher mode of operation. SIV takes a key, a plaintext, and multiple\n variable-length octet strings that will be authenticated but not\n encrypted. It produces a ciphertext having the same length as the\n plaintext and a synthetic initialization vector. Depending on how it\n is used, SIV achieves either the goal of deterministic authenticated\n encryption or the goal of nonce-based, misuse-resistant authenticated\n encryption.\n\nHawkins Informational [Page 1]\n\f\nRFC 5297 SIV-AES October 2008 5297 authentication encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 5327","type":"specification","body":"IETF","designation":"RFC 5327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5327.txt","https://www.rfc-editor.org/rfc/rfc5327.pdf"],"folder":"IETF/RFC-5327","files":{"txt":{"path":"standards/IETF/RFC-5327/RFC-5327.txt","sha256":"36dbc6fbb95ca1ced143816af11abab97e1787afbfc3759a67202895ef4035fd"}},"tags":["nested-reference","unchanged"],"summary":"The Licklider Transmission Protocol (LTP) is intended to serve as a\n reliable convergence layer over single-hop deep-space radio frequency\n (RF) links. LTP does Automatic Repeat reQuest (ARQ) of data\n transmissions by soliciting selective-acknowledgment reception\n reports. It is stateful and has no negotiation or handshakes. This\n document describes security extensions to LTP, and is part of a\n series of related documents describing LTP.\n\n This document is a product of the Delay Tolerant Networking Research\n Group and has been reviewed by that group. No objections to its\n publication as an RFC were raised.\n\nFarrell, et al. Experimental [Page 1]\n\f\nRFC 5327 LTP - Extensions September 2008","scope_keywords":["5327","authentication","issuer","key","keys","management","pki","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null}],"search_text":"IETF RFC 5327 The Licklider Transmission Protocol (LTP) is intended to serve as a\n reliable convergence layer over single-hop deep-space radio frequency\n (RF) links. LTP does Automatic Repeat reQuest (ARQ) of data\n transmissions by soliciting selective-acknowledgment reception\n reports. It is stateful and has no negotiation or handshakes. This\n document describes security extensions to LTP, and is part of a\n series of related documents describing LTP.\n\n This document is a product of the Delay Tolerant Networking Research\n Group and has been reviewed by that group. No objections to its\n publication as an RFC were raised.\n\nFarrell, et al. Experimental [Page 1]\n\f\nRFC 5327 LTP - Extensions September 2008 5327 authentication issuer key keys management pki signature nested-reference unchanged"},{"id":"IETF RFC 5448","type":"specification","body":"IETF","designation":"RFC 5448","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5448.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5448.txt","https://www.rfc-editor.org/rfc/rfc5448.pdf"],"folder":"IETF/RFC-5448","files":{"txt":{"path":"standards/IETF/RFC-5448/RFC-5448.txt","sha256":"7af030a5873876612d64db54dc90b642a561e528d08c42f3e2e90e2394c1cd6b"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a new EAP method, EAP-AKA', which is a\n small revision of the EAP-AKA (Extensible Authentication Protocol\n Method for 3rd Generation Authentication and Key Agreement) method.\n The change is a new key derivation function that binds the keys\n derived within the method to the name of the access network. The new\n key derivation mechanism has been defined in the 3rd Generation\n Partnership Project (3GPP). This specification allows its use in EAP\n in an interoperable manner. In addition, EAP-AKA' employs SHA-256\n instead of SHA-1.\n\n This specification also updates RFC 4187, EAP-AKA, to prevent bidding\n down attacks from EAP-AKA'.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 5448 EAP-AKA' May 2009","scope_keywords":["5448","attribute","authentication","encryption","hash","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null}],"search_text":"IETF RFC 5448 This specification defines a new EAP method, EAP-AKA', which is a\n small revision of the EAP-AKA (Extensible Authentication Protocol\n Method for 3rd Generation Authentication and Key Agreement) method.\n The change is a new key derivation function that binds the keys\n derived within the method to the name of the access network. The new\n key derivation mechanism has been defined in the 3rd Generation\n Partnership Project (3GPP). This specification allows its use in EAP\n in an interoperable manner. In addition, EAP-AKA' employs SHA-256\n instead of SHA-1.\n\n This specification also updates RFC 4187, EAP-AKA, to prevent bidding\n down attacks from EAP-AKA'.\n\nArkko, et al. Informational [Page 1]\n\f\nRFC 5448 EAP-AKA' May 2009 5448 attribute authentication encryption hash http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5487","type":"specification","body":"IETF","designation":"RFC 5487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5487.txt","https://www.rfc-editor.org/rfc/rfc5487.pdf"],"folder":"IETF/RFC-5487","files":{"txt":{"path":"standards/IETF/RFC-5487/RFC-5487.txt","sha256":"f02293e7bcf5784fb98e1a0c9fcd98f9fae9cc8bd1a854add965cfd5ebd50d26"}},"tags":["nested-reference","unchanged"],"summary":"RFC 4279 and RFC 4785 describe pre-shared key cipher suites for\n Transport Layer Security (TLS). However, all those cipher suites use\n SHA-1 in their Message Authentication Code (MAC) algorithm. This\n document describes a set of pre-shared key cipher suites for TLS that\n uses stronger digest algorithms (i.e., SHA-256 or SHA-384) and\n another set that uses the Advanced Encryption Standard (AES) in\n Galois Counter Mode (GCM).\n\nBadra Standards Track [Page 1]\n\f\nRFC 5487 TLS PSK New MAC and AES-GCM March 2009","scope_keywords":["5487","algorithm","algorithms","authentication","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null}],"search_text":"IETF RFC 5487 RFC 4279 and RFC 4785 describe pre-shared key cipher suites for\n Transport Layer Security (TLS). However, all those cipher suites use\n SHA-1 in their Message Authentication Code (MAC) algorithm. This\n document describes a set of pre-shared key cipher suites for TLS that\n uses stronger digest algorithms (i.e., SHA-256 or SHA-384) and\n another set that uses the Advanced Encryption Standard (AES) in\n Galois Counter Mode (GCM).\n\nBadra Standards Track [Page 1]\n\f\nRFC 5487 TLS PSK New MAC and AES-GCM March 2009 5487 algorithm algorithms authentication encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5489","type":"specification","body":"IETF","designation":"RFC 5489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5489.txt","https://www.rfc-editor.org/rfc/rfc5489.pdf"],"folder":"IETF/RFC-5489","files":{"txt":{"path":"standards/IETF/RFC-5489/RFC-5489.txt","sha256":"99cdfff24bb302a12dcf10c14f6d0ae0f59a4ae056fa549e729e5ab456e4c8a4"}},"tags":["nested-reference","unchanged"],"summary":"This document extends RFC 4279, RFC 4492, and RFC 4785 and specifies\n a set of cipher suites that use a pre-shared key (PSK) to\n authenticate an Elliptic Curve Diffie-Hellman exchange with Ephemeral\n keys (ECDHE). These cipher suites provide Perfect Forward Secrecy\n (PFS).\n\nBadra & Hajjeh Informational [Page 1]\n\f\nRFC 5489 ECDHE_PSK Cipher Suites for TLS March 2009","scope_keywords":["5489","algorithm","authentication","certificate","certificates","encryption","hash","http","key","keys","license","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null}],"search_text":"IETF RFC 5489 This document extends RFC 4279, RFC 4492, and RFC 4785 and specifies\n a set of cipher suites that use a pre-shared key (PSK) to\n authenticate an Elliptic Curve Diffie-Hellman exchange with Ephemeral\n keys (ECDHE). These cipher suites provide Perfect Forward Secrecy\n (PFS).\n\nBadra & Hajjeh Informational [Page 1]\n\f\nRFC 5489 ECDHE_PSK Cipher Suites for TLS March 2009 5489 algorithm authentication certificate certificates encryption hash http key keys license signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5669","type":"specification","body":"IETF","designation":"RFC 5669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5669.txt","https://www.rfc-editor.org/rfc/rfc5669.pdf"],"folder":"IETF/RFC-5669","files":{"txt":{"path":"standards/IETF/RFC-5669/RFC-5669.txt","sha256":"2fc14db340ecf3aed3b80c8c4b2a11c109967586f0b0b03d4e54ab63f6c48d89"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the SEED block cipher algorithm in\n the Secure Real-time Transport Protocol (SRTP) for providing\n confidentiality for Real-time Transport Protocol (RTP) traffic and\n for the control traffic for RTP, the Real-time Transport Control\n Protocol (RTCP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5669.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust an","scope_keywords":["5669","algorithm","algorithms","authentication","encryption","http","key","keys","license","pki","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 5669 This document describes the use of the SEED block cipher algorithm in\n the Secure Real-time Transport Protocol (SRTP) for providing\n confidentiality for Real-time Transport Protocol (RTP) traffic and\n for the control traffic for RTP, the Real-time Transport Control\n Protocol (RTCP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5669.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust an 5669 algorithm algorithms authentication encryption http key keys license pki subject trust nested-reference unchanged"},{"id":"IETF RFC 5753","type":"specification","body":"IETF","designation":"RFC 5753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5753.txt","https://www.rfc-editor.org/rfc/rfc5753.pdf"],"folder":"IETF/RFC-5753","files":{"txt":{"path":"standards/IETF/RFC-5753/RFC-5753.txt","sha256":"9377ef32f64c7b40454f78860e8eee98774994c130b58cd95f872ffea2a2b6c4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use Elliptic Curve Cryptography (ECC)\n public key algorithms in the Cryptographic Message Syntax (CMS). The\n ECC algorithms support the creation of digital signatures and the\n exchange of keys to encrypt or authenticate content. The definition\n of the algorithm processing is based on the NIST FIPS 186-3 for\n digital signature, NIST SP800-56A and SEC1 for key agreement, RFC\n 3370 and RFC 3565 for key wrap and content encryption, NIST FIPS\n 180-3 for message digest, SEC1 for key derivation, and RFC 2104 and\n RFC 4231 for message authentication code standards. This document\n obsoletes RFC 3278.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re","scope_keywords":["5753","algorithm","algorithms","attribute","authentication","certificate","certificates","encryption","hash","http","key","keys","license","profile","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null}],"search_text":"IETF RFC 5753 This document describes how to use Elliptic Curve Cryptography (ECC)\n public key algorithms in the Cryptographic Message Syntax (CMS). The\n ECC algorithms support the creation of digital signatures and the\n exchange of keys to encrypt or authenticate content. The definition\n of the algorithm processing is based on the NIST FIPS 186-3 for\n digital signature, NIST SP800-56A and SEC1 for key agreement, RFC\n 3370 and RFC 3565 for key wrap and content encryption, NIST FIPS\n 180-3 for message digest, SEC1 for key derivation, and RFC 2104 and\n RFC 4231 for message authentication code standards. This document\n obsoletes RFC 3278.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n re 5753 algorithm algorithms attribute authentication certificate certificates encryption hash http key keys license profile signature signatures nested-reference unchanged"},{"id":"IETF RFC 5769","type":"specification","body":"IETF","designation":"RFC 5769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5769.txt","https://www.rfc-editor.org/rfc/rfc5769.pdf"],"folder":"IETF/RFC-5769","files":{"txt":{"path":"standards/IETF/RFC-5769/RFC-5769.txt","sha256":"d1c053153cae0e977044439b1fe1cfb5a5255fbe33050f58f9d80772542982ab"}},"tags":["nested-reference","unchanged"],"summary":"The Session Traversal Utilities for NAT (STUN) protocol defines\n several STUN attributes. The content of some of these --\n FINGERPRINT, MESSAGE-INTEGRITY, and XOR-MAPPED-ADDRESS -- involve\n binary-logical operations (hashing, xor). This document provides\n test vectors for those attributes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may ","scope_keywords":["5769","attribute","attributes","authentication","credential","credentials","hash","hashing","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 5769 The Session Traversal Utilities for NAT (STUN) protocol defines\n several STUN attributes. The content of some of these --\n FINGERPRINT, MESSAGE-INTEGRITY, and XOR-MAPPED-ADDRESS -- involve\n binary-logical operations (hashing, xor). This document provides\n test vectors for those attributes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may  5769 attribute attributes authentication credential credentials hash hashing http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5802","type":"specification","body":"IETF","designation":"RFC 5802","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5802.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5802.txt","https://www.rfc-editor.org/rfc/rfc5802.pdf"],"folder":"IETF/RFC-5802","files":{"txt":{"path":"standards/IETF/RFC-5802/RFC-5802.txt","sha256":"12fcaba0dd78fe7aeb1c63f433314722977ef6746a638fce0f168c63a5bd24ba"}},"tags":["nested-reference","unchanged"],"summary":"The secure authentication mechanism most widely deployed and used by\n Internet application protocols is the transmission of clear-text\n passwords over a channel protected by Transport Layer Security (TLS).\n There are some significant security concerns with that mechanism,\n which could be addressed by the use of a challenge response\n authentication mechanism protected by TLS. Unfortunately, the\n challenge response mechanisms presently on the standards track all\n fail to meet requirements necessary for widespread deployment, and\n have had success only in limited use.\n\n This specification describes a family of Simple Authentication and\n Security Layer (SASL; RFC 4422) authentication mechanisms called the\n Salted Challenge Response Authentication Mechanism (SCRAM), which\n addresses the security concerns and meets the deployability\n requirements. When used in combination with TLS or an equiva","scope_keywords":["5802","algorithm","attribute","attributes","authentication","authorization","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null}],"search_text":"IETF RFC 5802 The secure authentication mechanism most widely deployed and used by\n Internet application protocols is the transmission of clear-text\n passwords over a channel protected by Transport Layer Security (TLS).\n There are some significant security concerns with that mechanism,\n which could be addressed by the use of a challenge response\n authentication mechanism protected by TLS. Unfortunately, the\n challenge response mechanisms presently on the standards track all\n fail to meet requirements necessary for widespread deployment, and\n have had success only in limited use.\n\n This specification describes a family of Simple Authentication and\n Security Layer (SASL; RFC 4422) authentication mechanisms called the\n Salted Challenge Response Authentication Mechanism (SCRAM), which\n addresses the security concerns and meets the deployability\n requirements. When used in combination with TLS or an equiva 5802 algorithm attribute attributes authentication authorization http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5912","type":"specification","body":"IETF","designation":"RFC 5912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5912.txt","https://www.rfc-editor.org/rfc/rfc5912.pdf"],"folder":"IETF/RFC-5912","files":{"txt":{"path":"standards/IETF/RFC-5912/RFC-5912.txt","sha256":"32d508e114363baf6df01a8085d7a6f0515c65776801b3cb728aeed0843b18fc"}},"tags":["nested-reference","unchanged"],"summary":"The Public Key Infrastructure using X.509 (PKIX) certificate format,\n and many associated formats, are expressed using ASN.1. The current\n ASN.1 modules conform to the 1988 version of ASN.1. This document\n updates those ASN.1 modules to conform to the 2002 version of ASN.1.\n There are no bits-on-the-wire changes to any of the formats; this is\n simply a change to the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th","scope_keywords":["5912","algorithm","algorithms","attribute","certificate","certificates","crl","http","identification","key","keys","license","management","ocsp","pki","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 5912 The Public Key Infrastructure using X.509 (PKIX) certificate format,\n and many associated formats, are expressed using ASN.1. The current\n ASN.1 modules conform to the 1988 version of ASN.1. This document\n updates those ASN.1 modules to conform to the 2002 version of ASN.1.\n There are no bits-on-the-wire changes to any of the formats; this is\n simply a change to the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th 5912 algorithm algorithms attribute certificate certificates crl http identification key keys license management ocsp pki profile nested-reference unchanged"},{"id":"IETF RFC 5920","type":"specification","body":"IETF","designation":"RFC 5920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5920.txt","https://www.rfc-editor.org/rfc/rfc5920.pdf"],"folder":"IETF/RFC-5920","files":{"txt":{"path":"standards/IETF/RFC-5920/RFC-5920.txt","sha256":"d4e6580b6f8a6463166e1e34c6235c578b09f8685d57a1deaf277f6a164336f7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a security framework for Multiprotocol Label\n Switching (MPLS) and Generalized Multiprotocol Label Switching\n (GMPLS) Networks. This document addresses the security aspects that\n are relevant in the context of MPLS and GMPLS. It describes the\n security threats, the related defensive techniques, and the\n mechanisms for detection and reporting. This document emphasizes\n RSVP-TE and LDP security considerations, as well as inter-AS and\n inter-provider security considerations for building and maintaining\n MPLS and GMPLS networks across different domains or different\n Service Providers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public revie","scope_keywords":["5920","authentication","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6941","folder":"IETF/RFC-6941","source":"IETF/RFC-6941/RFC-6941.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5920 This document provides a security framework for Multiprotocol Label\n Switching (MPLS) and Generalized Multiprotocol Label Switching\n (GMPLS) Networks. This document addresses the security aspects that\n are relevant in the context of MPLS and GMPLS. It describes the\n security threats, the related defensive techniques, and the\n mechanisms for detection and reporting. This document emphasizes\n RSVP-TE and LDP security considerations, as well as inter-AS and\n inter-provider security considerations for building and maintaining\n MPLS and GMPLS networks across different domains or different\n Service Providers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public revie 5920 authentication http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5926","type":"specification","body":"IETF","designation":"RFC 5926","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5926.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5926.txt","https://www.rfc-editor.org/rfc/rfc5926.pdf"],"folder":"IETF/RFC-5926","files":{"txt":{"path":"standards/IETF/RFC-5926/RFC-5926.txt","sha256":"25a1a2c75b6be6c629c3b039d8b19aef4e797ac272841b1ef52b40c9e6da1340"}},"tags":["nested-reference","unchanged"],"summary":"The TCP Authentication Option (TCP-AO) relies on security algorithms\n to provide authentication between two end-points. There are many\n such algorithms available, and two TCP-AO systems cannot interoperate\n unless they are using the same algorithms. This document specifies\n the algorithms and attributes that can be used in TCP-AO's current\n manual keying mechanism and provides the interface for future message\n authentication codes (MACs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, ","scope_keywords":["5926","algorithm","algorithms","attribute","attributes","authentication","hash","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 5926 The TCP Authentication Option (TCP-AO) relies on security algorithms\n to provide authentication between two end-points. There are many\n such algorithms available, and two TCP-AO systems cannot interoperate\n unless they are using the same algorithms. This document specifies\n the algorithms and attributes that can be used in TCP-AO's current\n manual keying mechanism and provides the interface for future message\n authentication codes (MACs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document,  5926 algorithm algorithms attribute attributes authentication hash http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6043","type":"specification","body":"IETF","designation":"RFC 6043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6043.txt","https://www.rfc-editor.org/rfc/rfc6043.pdf"],"folder":"IETF/RFC-6043","files":{"txt":{"path":"standards/IETF/RFC-6043/RFC-6043.txt","sha256":"dd588dcdecf1887ad6a80eaf3a53e84ba678499d7a76a1b33ee8eafeb1c62bdb"}},"tags":["nested-reference","unchanged"],"summary":"The Multimedia Internet KEYing (MIKEY) specification describes a key\n management scheme for real-time applications. In this document, we\n note that the currently defined MIKEY modes are insufficient to\n address deployment scenarios built around a centralized key\n management service. Interest in such deployments is increasing.\n Therefore, a set of new MIKEY modes that work well in such scenarios\n are defined. The new modes use a trusted key management service and\n a ticket concept, similar to that in Kerberos. The new modes also\n support features used by many existing applications, where the exact\n identity of the other endpoint may not be known at the start of the\n communication session.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (I","scope_keywords":["6043","certificate","certificates","credential","credentials","hash","http","key","keys","license","management","pki","policy","signature","subject","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 6043 The Multimedia Internet KEYing (MIKEY) specification describes a key\n management scheme for real-time applications. In this document, we\n note that the currently defined MIKEY modes are insufficient to\n address deployment scenarios built around a centralized key\n management service. Interest in such deployments is increasing.\n Therefore, a set of new MIKEY modes that work well in such scenarios\n are defined. The new modes use a trusted key management service and\n a ticket concept, similar to that in Kerberos. The new modes also\n support features used by many existing applications, where the exact\n identity of the other endpoint may not be known at the start of the\n communication session.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (I 6043 certificate certificates credential credentials hash http key keys license management pki policy signature subject timestamp nested-reference unchanged"},{"id":"IETF RFC 6063","type":"specification","body":"IETF","designation":"RFC 6063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6063.txt","https://www.rfc-editor.org/rfc/rfc6063.pdf"],"folder":"IETF/RFC-6063","files":{"txt":{"path":"standards/IETF/RFC-6063/RFC-6063.txt","sha256":"6b98950429994b46b29eacc6531eda9fd450ac451db01c25afe41e3f6ccb1c88"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Symmetric Key Provisioning Protocol (DSKPP) is a client-\n server protocol for initialization (and configuration) of symmetric\n keys to locally and remotely accessible cryptographic modules. The\n protocol can be run with or without private key capabilities in the\n cryptographic modules and with or without an established public key\n infrastructure.\n\n Two variations of the protocol support multiple usage scenarios.\n With the four-pass variant, keys are mutually generated by the\n provisioning server and cryptographic module; provisioned keys are\n not transferred over-the-wire or over-the-air. The two-pass variant\n enables secure and efficient download and installation of pre-\n generated symmetric keys to a cryptographic module.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It repre","scope_keywords":["6063","algorithm","authentication","hash","http","identification","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null}],"search_text":"IETF RFC 6063 The Dynamic Symmetric Key Provisioning Protocol (DSKPP) is a client-\n server protocol for initialization (and configuration) of symmetric\n keys to locally and remotely accessible cryptographic modules. The\n protocol can be run with or without private key capabilities in the\n cryptographic modules and with or without an established public key\n infrastructure.\n\n Two variations of the protocol support multiple usage scenarios.\n With the four-pass variant, keys are mutually generated by the\n provisioning server and cryptographic module; provisioned keys are\n not transferred over-the-wire or over-the-air. The two-pass variant\n enables secure and efficient download and installation of pre-\n generated symmetric keys to a cryptographic module.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It repre 6063 algorithm authentication hash http identification key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6066","type":"specification","body":"IETF","designation":"RFC 6066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6066.txt","https://www.rfc-editor.org/rfc/rfc6066.pdf"],"folder":"IETF/RFC-6066","files":{"txt":{"path":"standards/IETF/RFC-6066/RFC-6066.txt","sha256":"6a33cceaa5e1b6518923d9d04ffaa738bad0417806b3c94a995484e140f5cbc0"}},"tags":["nested-reference","unchanged"],"summary":"This document provides specifications for existing TLS extensions.\n It is a companion document for RFC 5246, \"The Transport Layer\n Security (TLS) Protocol Version 1.2\". The extensions specified are\n server_name, max_fragment_length, client_certificate_url,\n trusted_ca_keys, truncated_hmac, and status_request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6066.\n\nCopyright Notice\n\n Copyr","scope_keywords":["6066","algorithm","algorithms","authentication","certificate","crl","http","key","keys","license","ocsp","path","pki","revocation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7366","folder":"IETF/RFC-7366","source":"IETF/RFC-7366/RFC-7366.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 6066 This document provides specifications for existing TLS extensions.\n It is a companion document for RFC 5246, \"The Transport Layer\n Security (TLS) Protocol Version 1.2\". The extensions specified are\n server_name, max_fragment_length, client_certificate_url,\n trusted_ca_keys, truncated_hmac, and status_request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6066.\n\nCopyright Notice\n\n Copyr 6066 algorithm algorithms authentication certificate crl http key keys license ocsp path pki revocation signature subject nested-reference unchanged"},{"id":"IETF RFC 6124","type":"specification","body":"IETF","designation":"RFC 6124","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6124.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6124.txt","https://www.rfc-editor.org/rfc/rfc6124.pdf"],"folder":"IETF/RFC-6124","files":{"txt":{"path":"standards/IETF/RFC-6124/RFC-6124.txt","sha256":"f3495aa89608367661981b2b682f65311db4313b0803049b265f6e5699560b56"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) describes a framework\n that allows the use of multiple authentication mechanisms. This\n document defines an authentication mechanism for EAP called EAP-EKE,\n based on the Encrypted Key Exchange (EKE) protocol. This method\n provides mutual authentication through the use of a short, easy to\n remember password. Compared with other common authentication\n methods, EAP-EKE is not susceptible to dictionary attacks. Neither\n does it require the availability of public-key certificates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group ","scope_keywords":["6124","algorithm","algorithms","authentication","certificate","certificates","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 6124 The Extensible Authentication Protocol (EAP) describes a framework\n that allows the use of multiple authentication mechanisms. This\n document defines an authentication mechanism for EAP called EAP-EKE,\n based on the Encrypted Key Exchange (EKE) protocol. This method\n provides mutual authentication through the use of a short, easy to\n remember password. Compared with other common authentication\n methods, EAP-EKE is not susceptible to dictionary attacks. Neither\n does it require the availability of public-key certificates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group  6124 algorithm algorithms authentication certificate certificates http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6234","type":"specification","body":"IETF","designation":"RFC 6234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6234.txt","https://www.rfc-editor.org/rfc/rfc6234.pdf"],"folder":"IETF/RFC-6234","files":{"txt":{"path":"standards/IETF/RFC-6234/RFC-6234.txt","sha256":"8f39f02a57bfd1da15634706724a585766e6223f77ecdaf243cad16cd3a1aa1b"}},"tags":["nested-reference","unchanged"],"summary":"The United States of America has adopted a suite of Secure Hash\n Algorithms (SHAs), including four beyond SHA-1, as part of a Federal\n Information Processing Standard (FIPS), namely SHA-224, SHA-256,\n SHA-384, and SHA-512. This document makes open source code\n performing these SHA hash functions conveniently available to the\n Internet community. The sample code supports input strings of\n arbitrary bit length. Much of the text herein was adapted by the\n authors from FIPS 180-2.\n\n This document replaces RFC 4634, fixing errata and adding code for an\n HMAC-based extract-and-expand Key Derivation Function, HKDF (RFC\n 5869). As with RFC 4634, code to perform SHA-based Hashed Message\n Authentication Codes (HMACs) is also included.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of t","scope_keywords":["6234","algorithm","algorithms","authentication","hash","http","key","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7218","folder":"IETF/RFC-7218","source":"IETF/RFC-7218/RFC-7218.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7693","folder":"IETF/RFC-7693","source":"IETF/RFC-7693/RFC-7693.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8032","folder":"IETF/RFC-8032","source":"IETF/RFC-8032/RFC-8032.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IETF RFC 6234 The United States of America has adopted a suite of Secure Hash\n Algorithms (SHAs), including four beyond SHA-1, as part of a Federal\n Information Processing Standard (FIPS), namely SHA-224, SHA-256,\n SHA-384, and SHA-512. This document makes open source code\n performing these SHA hash functions conveniently available to the\n Internet community. The sample code supports input strings of\n arbitrary bit length. Much of the text herein was adapted by the\n authors from FIPS 180-2.\n\n This document replaces RFC 4634, fixing errata and adding code for an\n HMAC-based extract-and-expand Key Derivation Function, HKDF (RFC\n 5869). As with RFC 4634, code to perform SHA-based Hashed Message\n Authentication Codes (HMACs) is also included.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of t 6234 algorithm algorithms authentication hash http key license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6367","type":"specification","body":"IETF","designation":"RFC 6367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6367.txt","https://www.rfc-editor.org/rfc/rfc6367.pdf"],"folder":"IETF/RFC-6367","files":{"txt":{"path":"standards/IETF/RFC-6367/RFC-6367.txt","sha256":"7343444b83b9d7c264cf80a940665b94181011be741b80a260500d939c421ab2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies forty-two cipher suites for the Transport\n Security Layer (TLS) protocol to support the Camellia encryption\n algorithm as a block cipher.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6367.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identif","scope_keywords":["6367","algorithm","algorithms","authentication","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6367 This document specifies forty-two cipher suites for the Transport\n Security Layer (TLS) protocol to support the Camellia encryption\n algorithm as a block cipher.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6367.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identif 6367 algorithm algorithms authentication encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6506","type":"specification","body":"IETF","designation":"RFC 6506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6506.txt","https://www.rfc-editor.org/rfc/rfc6506.pdf"],"folder":"IETF/RFC-6506","files":{"txt":{"path":"standards/IETF/RFC-6506/RFC-6506.txt","sha256":"307ab913fdacc587a48f249b9cbf002b9157c019e8ba7f89157872cf9a1018ea"}},"tags":["nested-reference","unchanged"],"summary":"Currently, OSPF for IPv6 (OSPFv3) uses IPsec as the only mechanism\n for authenticating protocol packets. This behavior is different from\n authentication mechanisms present in other routing protocols (OSPFv2,\n Intermediate System to Intermediate System (IS-IS), RIP, and Routing\n Information Protocol Next Generation (RIPng)). In some environments,\n it has been found that IPsec is difficult to configure and maintain\n and thus cannot be used. This document defines an alternative\n mechanism to authenticate OSPFv3 protocol packets so that OSPFv3 does\n not only depend upon IPsec for authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri","scope_keywords":["6506","algorithm","algorithms","authentication","hash","http","key","keys","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null}],"search_text":"IETF RFC 6506 Currently, OSPF for IPv6 (OSPFv3) uses IPsec as the only mechanism\n for authenticating protocol packets. This behavior is different from\n authentication mechanisms present in other routing protocols (OSPFv2,\n Intermediate System to Intermediate System (IS-IS), RIP, and Routing\n Information Protocol Next Generation (RIPng)). In some environments,\n it has been found that IPsec is difficult to configure and maintain\n and thus cannot be used. This document defines an alternative\n mechanism to authenticate OSPFv3 protocol packets so that OSPFv3 does\n not only depend upon IPsec for authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri 6506 algorithm algorithms authentication hash http key keys license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6584","type":"specification","body":"IETF","designation":"RFC 6584","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6584.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6584.txt","https://www.rfc-editor.org/rfc/rfc6584.pdf"],"folder":"IETF/RFC-6584","files":{"txt":{"path":"standards/IETF/RFC-6584/RFC-6584.txt","sha256":"4609bb4df38e3e2bca82d448ecc955fca868d259b6c59f2e4538eb4bcd082731"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces four schemes that provide per-packet\n authentication, integrity, and anti-replay services in the context of\n the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable\n Multicast (NORM) protocols. The first scheme is based on RSA Digital\n Signatures. The second scheme relies on the Elliptic Curve Digital\n Signature Algorithm (ECDSA). The third scheme relies on a Group-\n keyed Message Authentication Code (MAC). Finally, the fourth scheme\n merges the Digital Signature and group schemes. These schemes have\n different target use cases, and they do not all provide the same\n service.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet E","scope_keywords":["6584","algorithm","authentication","delivery","http","identification","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 6584 This document introduces four schemes that provide per-packet\n authentication, integrity, and anti-replay services in the context of\n the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable\n Multicast (NORM) protocols. The first scheme is based on RSA Digital\n Signatures. The second scheme relies on the Elliptic Curve Digital\n Signature Algorithm (ECDSA). The third scheme relies on a Group-\n keyed Message Authentication Code (MAC). Finally, the fourth scheme\n merges the Digital Signature and group schemes. These schemes have\n different target use cases, and they do not all provide the same\n service.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet E 6584 algorithm authentication delivery http identification key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6590","type":"specification","body":"IETF","designation":"RFC 6590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6590.txt","https://www.rfc-editor.org/rfc/rfc6590.pdf"],"folder":"IETF/RFC-6590","files":{"txt":{"path":"standards/IETF/RFC-6590/RFC-6590.txt","sha256":"3f5985a08344969ab8d5cbb83f9e187921ee1c8cff54055a1a71581f604c7fc7"}},"tags":["nested-reference","unchanged"],"summary":"Email messages often contain information that might be considered\n private or sensitive, per either regulation or social norms. When\n such a message becomes the subject of a report intended to be shared\n with other entities, the report generator may wish to redact or elide\n the sensitive portions of the message. This memo suggests one method\n for doing so effectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:","scope_keywords":["6590","algorithm","http","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6590 Email messages often contain information that might be considered\n private or sensitive, per either regulation or social norms. When\n such a message becomes the subject of a report intended to be shared\n with other entities, the report generator may wish to redact or elide\n the sensitive portions of the message. This memo suggests one method\n for doing so effectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http: 6590 algorithm http key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6630","type":"specification","body":"IETF","designation":"RFC 6630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6630.txt","https://www.rfc-editor.org/rfc/rfc6630.pdf"],"folder":"IETF/RFC-6630","files":{"txt":{"path":"standards/IETF/RFC-6630/RFC-6630.txt","sha256":"04d56f0a328ebf6b840d03a53409cb2c85f9f9325e515001aefb8c74a89bb05d"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP) is a generic framework\n supporting multiple types of authentication methods.\n\n The EAP Re-authentication Protocol (ERP) specifies extensions to EAP\n and the EAP keying hierarchy to support an EAP method-independent\n protocol for efficient re-authentication between the peer and an EAP\n re-authentication server through any authenticator.\n\n Authenticated Anticipatory Keying (AAK) is a method by which\n cryptographic keying material may be established upon one or more\n Candidate Attachment Points (CAPs) prior to handover. AAK uses the\n AAA infrastructure for key transport.\n\n This document specifies the extensions necessary to enable AAK\n support in ERP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. I","scope_keywords":["6630","attribute","attributes","authentication","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null}],"search_text":"IETF RFC 6630 The Extensible Authentication Protocol (EAP) is a generic framework\n supporting multiple types of authentication methods.\n\n The EAP Re-authentication Protocol (ERP) specifies extensions to EAP\n and the EAP keying hierarchy to support an EAP method-independent\n protocol for efficient re-authentication between the peer and an EAP\n re-authentication server through any authenticator.\n\n Authenticated Anticipatory Keying (AAK) is a method by which\n cryptographic keying material may be established upon one or more\n Candidate Attachment Points (CAPs) prior to handover. AAK uses the\n AAA infrastructure for key transport.\n\n This document specifies the extensions necessary to enable AAK\n support in ERP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. I 6630 attribute attributes authentication authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6952","type":"specification","body":"IETF","designation":"RFC 6952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6952.txt","https://www.rfc-editor.org/rfc/rfc6952.pdf"],"folder":"IETF/RFC-6952","files":{"txt":{"path":"standards/IETF/RFC-6952/RFC-6952.txt","sha256":"fead487f6cc00a8f64c5567555fd662411f8acbb53091fcb2973ffc347ff39cf"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes TCP-based routing protocols, the Border\n Gateway Protocol (BGP), the Label Distribution Protocol (LDP), the\n Path Computation Element Communication Protocol (PCEP), and the\n Multicast Source Distribution Protocol (MSDP), according to\n guidelines set forth in Section 4.2 of \"Keying and Authentication for\n Routing Protocols Design Guidelines\", RFC 6518.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th","scope_keywords":["6952","algorithm","authentication","encryption","hash","http","key","license","management","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 6952 This document analyzes TCP-based routing protocols, the Border\n Gateway Protocol (BGP), the Label Distribution Protocol (LDP), the\n Path Computation Element Communication Protocol (PCEP), and the\n Multicast Source Distribution Protocol (MSDP), according to\n guidelines set forth in Section 4.2 of \"Keying and Authentication for\n Routing Protocols Design Guidelines\", RFC 6518.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about th 6952 algorithm authentication encryption hash http key license management path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6979","type":"specification","body":"IETF","designation":"RFC 6979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6979.txt","https://www.rfc-editor.org/rfc/rfc6979.pdf"],"folder":"IETF/RFC-6979","files":{"txt":{"path":"standards/IETF/RFC-6979/RFC-6979.txt","sha256":"456e8f17558fdbd206f968b96fc6f1b4a71ea331ab30ad17f711ab3adaa7d701"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a deterministic digital signature generation\n procedure. Such signatures are compatible with standard Digital\n Signature Algorithm (DSA) and Elliptic Curve Digital Signature\n Algorithm (ECDSA) digital signatures and can be processed with\n unmodified verifiers, which need not be aware of the procedure\n described therein. Deterministic signatures retain the cryptographic\n security features associated with digital signatures but can be more\n easily implemented in various environments, since they do not need\n access to a source of high-quality randomness.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its v","scope_keywords":["6979","algorithm","http","key","license","signature","signatures","subject","trust","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 6979 This document defines a deterministic digital signature generation\n procedure. Such signatures are compatible with standard Digital\n Signature Algorithm (DSA) and Elliptic Curve Digital Signature\n Algorithm (ECDSA) digital signatures and can be processed with\n unmodified verifiers, which need not be aware of the procedure\n described therein. Deterministic signatures retain the cryptographic\n security features associated with digital signatures but can be more\n easily implemented in various environments, since they do not need\n access to a source of high-quality randomness.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its v 6979 algorithm http key license signature signatures subject trust verifiable nested-reference unchanged"},{"id":"IETF RFC 7804","type":"specification","body":"IETF","designation":"RFC 7804","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7804.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7804.txt","https://www.rfc-editor.org/rfc/rfc7804.pdf"],"folder":"IETF/RFC-7804","files":{"txt":{"path":"standards/IETF/RFC-7804/RFC-7804.txt","sha256":"a9bf19825ab06a0d3c6d6770c9074ab1dfe9819932530f360da1a82262c84059"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes a family of HTTP authentication\n mechanisms called the Salted Challenge Response Authentication\n Mechanism (SCRAM), which provides a more robust authentication\n mechanism than a plaintext password protected by Transport Layer\n Security (TLS) and avoids the deployment obstacles presented by\n earlier TLS-protected challenge response authentication mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents ","scope_keywords":["7804","algorithm","authentication","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 7804 This specification describes a family of HTTP authentication\n mechanisms called the Salted Challenge Response Authentication\n Mechanism (SCRAM), which provides a more robust authentication\n mechanism than a plaintext password protected by Transport Layer\n Security (TLS) and avoids the deployment obstacles presented by\n earlier TLS-protected challenge response authentication mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents  7804 algorithm authentication encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8152","type":"specification","body":"IETF","designation":"RFC 8152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8152.txt","https://www.rfc-editor.org/rfc/rfc8152.pdf"],"folder":"IETF/RFC-8152","files":{"txt":{"path":"standards/IETF/RFC-8152/RFC-8152.txt","sha256":"bd44c8c3db43614c59c778d86bab9269c89bf6dbacfd32d5ac35882660f815e1"}},"tags":["nested-reference","unchanged"],"summary":"Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need for the\n ability to have basic security services defined for this data format.\n This document defines the CBOR Object Signing and Encryption (COSE)\n protocol. This specification describes how to create and process\n signatures, message authentication codes, and encryption using CBOR\n for serialization. This specification additionally describes how to\n represent cryptographic keys using CBOR.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available i","scope_keywords":["8152","algorithm","algorithms","authentication","encryption","hash","http","key","keys","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 9021","folder":"IETF/RFC-9021","source":"IETF/RFC-9021/RFC-9021.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null}],"search_text":"IETF RFC 8152 Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need for the\n ability to have basic security services defined for this data format.\n This document defines the CBOR Object Signing and Encryption (COSE)\n protocol. This specification describes how to create and process\n signatures, message authentication codes, and encryption using CBOR\n for serialization. This specification additionally describes how to\n represent cryptographic keys using CBOR.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available i 8152 algorithm algorithms authentication encryption hash http key keys license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 9053","type":"specification","body":"IETF","designation":"RFC 9053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9053.txt","https://www.rfc-editor.org/rfc/rfc9053.pdf"],"folder":"IETF/RFC-9053","files":{"pdf":{"path":"standards/IETF/RFC-9053/RFC-9053.pdf","sha256":"b288141c8ca800256e3358299630f17c64137e3278f75b44478e3b8d763dd70e"},"txt":{"path":"standards/IETF/RFC-9053/RFC-9053.txt","sha256":"3d470615875620375f8453ba25b8dce7e4d0271e76b0b79a46df34ccb2d56ab0"}},"tags":["nested-reference","unchanged"],"summary":"Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need to be\n able to define basic security services for this data format. This\n document defines a set of algorithms that can be used with the CBOR\n Object Signing and Encryption (COSE) protocol (RFC 9052).\n\n This document, along with RFC 9052, obsoletes RFC 8152.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informat","scope_keywords":["9053","algorithm","algorithms","authentication","encryption","hash","http","https","key","keys","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 9053 Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need to be\n able to define basic security services for this data format. This\n document defines a set of algorithms that can be used with the CBOR\n Object Signing and Encryption (COSE) protocol (RFC 9052).\n\n This document, along with RFC 9052, obsoletes RFC 8152.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informat 9053 algorithm algorithms authentication encryption hash http https key keys license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 2105","type":"specification","body":"IETF","designation":"RFC 2105","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2105.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2105.txt","https://www.rfc-editor.org/rfc/rfc2105.pdf"],"folder":"IETF/RFC-2105","files":{"txt":{"path":"standards/IETF/RFC-2105/RFC-2105.txt","sha256":"7bcf9e9d22573a077e240f5115df69fe4a16fc142af147d66fc9a21ec1000287"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of a novel approach to network\n layer packet forwarding, called tag switching. The two main\n components of the tag switching architecture - forwarding and\n control - are described. Forwarding is accomplished using simple\n label-swapping techniques, while the existing network layer routing\n protocols plus mechanisms for binding and distributing tags are used\n for control. Tag switching can retain the scaling properties of IP,\n and can help improve the scalability of IP networks. While tag\n switching does not rely on ATM, it can straightforwardly be applied\n to ATM switches. A range of tag switching applications and deployment\n scenarios are described.","scope_keywords":["2105","algorithm","driving"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2702","folder":"IETF/RFC-2702","source":"IETF/RFC-2702/RFC-2702.txt","version":null}],"search_text":"IETF RFC 2105 This document provides an overview of a novel approach to network\n layer packet forwarding, called tag switching. The two main\n components of the tag switching architecture - forwarding and\n control - are described. Forwarding is accomplished using simple\n label-swapping techniques, while the existing network layer routing\n protocols plus mechanisms for binding and distributing tags are used\n for control. Tag switching can retain the scaling properties of IP,\n and can help improve the scalability of IP networks. While tag\n switching does not rely on ATM, it can straightforwardly be applied\n to ATM switches. A range of tag switching applications and deployment\n scenarios are described. 2105 algorithm driving nested-reference unchanged"},{"id":"IETF RFC 2702","type":"specification","body":"IETF","designation":"RFC 2702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2702.txt","https://www.rfc-editor.org/rfc/rfc2702.pdf"],"folder":"IETF/RFC-2702","files":{"txt":{"path":"standards/IETF/RFC-2702/RFC-2702.txt","sha256":"0f5084a33a2306ee702e85939037ef261d8fecfce9ae266dd2c59ab8378332d4"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of requirements for Traffic Engineering\n over Multiprotocol Label Switching (MPLS). It identifies the\n functional capabilities required to implement policies that\n facilitate efficient and reliable network operations in an MPLS\n domain. These capabilities can be used to optimize the utilization of\n network resources and to enhance traffic oriented performance\n characteristics.","scope_keywords":["2702","attribute","attributes","key","management","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3210","folder":"IETF/RFC-3210","source":"IETF/RFC-3210/RFC-3210.txt","version":null},{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null},{"body":"IETF","designation":"RFC 3386","folder":"IETF/RFC-3386","source":"IETF/RFC-3386/RFC-3386.txt","version":null},{"body":"IETF","designation":"RFC 3469","folder":"IETF/RFC-3469","source":"IETF/RFC-3469/RFC-3469.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null}],"search_text":"IETF RFC 2702 This document presents a set of requirements for Traffic Engineering\n over Multiprotocol Label Switching (MPLS). It identifies the\n functional capabilities required to implement policies that\n facilitate efficient and reliable network operations in an MPLS\n domain. These capabilities can be used to optimize the utilization of\n network resources and to enhance traffic oriented performance\n characteristics. 2702 attribute attributes key management path policies nested-reference unchanged"},{"id":"IETF RFC 2965","type":"specification","body":"IETF","designation":"RFC 2965","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2965.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2965.txt","https://www.rfc-editor.org/rfc/rfc2965.pdf"],"folder":"IETF/RFC-2965","files":{"txt":{"path":"standards/IETF/RFC-2965/RFC-2965.txt","sha256":"b1101e499511205ddd5739df11e01cd0e85c1ef37a7c1cb3fddb5fb73928af18"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a way to create a stateful session with\n Hypertext Transfer Protocol (HTTP) requests and responses. It\n describes three new headers, Cookie, Cookie2, and Set-Cookie2, which\n carry state information between participating origin servers and user\n agents. The method described here differs from Netscape's Cookie\n proposal [Netscape], but it can interoperate with HTTP/1.0 user\n agents that use Netscape's method. (See the HISTORICAL section.)\n\n This document reflects implementation experience with RFC 2109 and\n obsoletes it.\n\n1. TERMINOLOGY\n\n The terms user agent, client, server, proxy, origin server, and\n http_URL have the same meaning as in the HTTP/1.1 specification\n [RFC2616]. The terms abs_path and absoluteURI have the same meaning\n as in the URI Syntax specification [RFC2396].\n\nKristol & Montulli Standards Track [Page 1]\n\f\nRFC 2965 HTTP State Management Mechanism ","scope_keywords":["2965","attribute","attributes","http","key","management","path","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3041","folder":"IETF/RFC-3041","source":"IETF/RFC-3041/RFC-3041.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null}],"search_text":"IETF RFC 2965 This document specifies a way to create a stateful session with\n Hypertext Transfer Protocol (HTTP) requests and responses. It\n describes three new headers, Cookie, Cookie2, and Set-Cookie2, which\n carry state information between participating origin servers and user\n agents. The method described here differs from Netscape's Cookie\n proposal [Netscape], but it can interoperate with HTTP/1.0 user\n agents that use Netscape's method. (See the HISTORICAL section.)\n\n This document reflects implementation experience with RFC 2109 and\n obsoletes it.\n\n1. TERMINOLOGY\n\n The terms user agent, client, server, proxy, origin server, and\n http_URL have the same meaning as in the HTTP/1.1 specification\n [RFC2616]. The terms abs_path and absoluteURI have the same meaning\n as in the URI Syntax specification [RFC2396].\n\nKristol & Montulli Standards Track [Page 1]\n\f\nRFC 2965 HTTP State Management Mechanism  2965 attribute attributes http key management path qualified registered nested-reference unchanged"},{"id":"IETF RFC 7998","type":"specification","body":"IETF","designation":"RFC 7998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7998.txt","https://www.rfc-editor.org/rfc/rfc7998.pdf"],"folder":"IETF/RFC-7998","files":{"txt":{"path":"standards/IETF/RFC-7998/RFC-7998.txt","sha256":"3310f92875a281ee35341d53c9d138b9b1d9647ffe9ab5563f29525e72bd05da"}},"tags":["nested-reference","unchanged"],"summary":"This document describes some aspects of the \"prep tool\" that is\n expected to be created when the new xml2rfc version 3 specification\n is deployed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7998.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n docum","scope_keywords":["7998","attribute","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null}],"search_text":"IETF RFC 7998 This document describes some aspects of the \"prep tool\" that is\n expected to be created when the new xml2rfc version 3 specification\n is deployed.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7998.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n docum 7998 attribute http license subject trust nested-reference unchanged"},{"id":"IETF RFC 300","type":"specification","body":"IETF","designation":"RFC 300","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc300.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc300.txt","https://www.rfc-editor.org/rfc/rfc300.pdf"],"folder":"IETF/RFC-300","files":{"txt":{"path":"standards/IETF/RFC-300/RFC-300.txt","sha256":"e79ec35dde46d1163674992d8c767fbfbcdcddd048d937e8c6f415a4a4345c35"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRequest for Comments: 300 25 January 1972\nObsoletes: RFC 211 NIC 7191\nNIC 8468\n\n ARPA NETWORK MAILING LISTS\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\n (A) A. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n documents from NIC.\n\n AMES-CD CMU\n\n A. Wayne Hathawa","scope_keywords":["300"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 300 Network Working Group\nRequest for Comments: 300 25 January 1972\nObsoletes: RFC 211 NIC 7191\nNIC 8468\n\n ARPA NETWORK MAILING LISTS\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\n (A) A. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n documents from NIC.\n\n AMES-CD CMU\n\n A. Wayne Hathawa 300 nested-reference unchanged"},{"id":"IETF RFC 2113","type":"specification","body":"IETF","designation":"RFC 2113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2113.txt","https://www.rfc-editor.org/rfc/rfc2113.pdf"],"folder":"IETF/RFC-2113","files":{"txt":{"path":"standards/IETF/RFC-2113/RFC-2113.txt","sha256":"8b41537550efc580293d8aa252dcb868d4e049d8aadc2f599831c88fdd298d83"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a new IP Option type that alerts transit routers\n to more closely examine the contents of an IP packet. This is useful\n for, but not limited to, new protocols that are addressed to a\n destination but require relatively complex processing in routers\n along the path.","scope_keywords":["2113","algorithm","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2205","folder":"IETF/RFC-2205","source":"IETF/RFC-2205/RFC-2205.txt","version":null},{"body":"IETF","designation":"RFC 2236","folder":"IETF/RFC-2236","source":"IETF/RFC-2236/RFC-2236.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3208","folder":"IETF/RFC-3208","source":"IETF/RFC-3208/RFC-3208.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 2113 This memo describes a new IP Option type that alerts transit routers\n to more closely examine the contents of an IP packet. This is useful\n for, but not limited to, new protocols that are addressed to a\n destination but require relatively complex processing in routers\n along the path. 2113 algorithm management path nested-reference unchanged"},{"id":"IETF RFC 3811","type":"specification","body":"IETF","designation":"RFC 3811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3811.txt","https://www.rfc-editor.org/rfc/rfc3811.pdf"],"folder":"IETF/RFC-3811","files":{"txt":{"path":"standards/IETF/RFC-3811/RFC-3811.txt","sha256":"9e11d341754187b8f2b6647dee198889539389aa5e0203cf16c8807834f008dd"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) module which\n contains Textual Conventions to represent commonly used Multiprotocol\n Label Switching (MPLS) management information. The intent is that\n these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS\n related MIB modules that would otherwise define their own\n representations.","scope_keywords":["3811","http","key","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null}],"search_text":"IETF RFC 3811 This memo defines a Management Information Base (MIB) module which\n contains Textual Conventions to represent commonly used Multiprotocol\n Label Switching (MPLS) management information. The intent is that\n these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS\n related MIB modules that would otherwise define their own\n representations. 3811 http key management path presentation nested-reference unchanged"},{"id":"IETF RFC 5350","type":"specification","body":"IETF","designation":"RFC 5350","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5350.txt","https://www.rfc-editor.org/rfc/rfc5350.pdf"],"folder":"IETF/RFC-5350","files":{"txt":{"path":"standards/IETF/RFC-5350/RFC-5350.txt","sha256":"a5ea5c2cf529b67d190425ea789975f8ede9cd05127ad7aaf18c9fc73f353989"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the IANA allocation rules and registry of IPv4\n and IPv6 Router Alert Option Values.","scope_keywords":["5350","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null}],"search_text":"IETF RFC 5350 This document updates the IANA allocation rules and registry of IPv4\n and IPv6 Router Alert Option Values. 5350 management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 5796","type":"specification","body":"IETF","designation":"RFC 5796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5796.txt","https://www.rfc-editor.org/rfc/rfc5796.pdf"],"folder":"IETF/RFC-5796","files":{"txt":{"path":"standards/IETF/RFC-5796/RFC-5796.txt","sha256":"079471b36d5afb4a9f93bda39fa285f9d6f35c4d384053199197f2d7dbbe7526"}},"tags":["nested-reference","unchanged"],"summary":"RFC 4601 mandates the use of IPsec to ensure authentication of the\n link-local messages in the Protocol Independent Multicast - Sparse\n Mode (PIM-SM) routing protocol. This document specifies mechanisms\n to authenticate the PIM-SM link-local messages using the IP security\n (IPsec) Encapsulating Security Payload (ESP) or (optionally) the\n Authentication Header (AH). It specifies optional mechanisms to\n provide confidentiality using the ESP. Manual keying is specified as\n the mandatory and default group key management solution. To deal\n with issues of scalability and security that exist with manual\n keying, optional support for an automated group key management\n mechanism is provided. However, the procedures for implementing\n automated group key management are left to other documents. This\n document updates RFC 4601.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th","scope_keywords":["5796","authentication","http","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 5796 RFC 4601 mandates the use of IPsec to ensure authentication of the\n link-local messages in the Protocol Independent Multicast - Sparse\n Mode (PIM-SM) routing protocol. This document specifies mechanisms\n to authenticate the PIM-SM link-local messages using the IP security\n (IPsec) Encapsulating Security Payload (ESP) or (optionally) the\n Authentication Header (AH). It specifies optional mechanisms to\n provide confidentiality using the ESP. Manual keying is specified as\n the mandatory and default group key management solution. To deal\n with issues of scalability and security that exist with manual\n keying, optional support for an automated group key management\n mechanism is provided. However, the procedures for implementing\n automated group key management are left to other documents. This\n document updates RFC 4601.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n Th 5796 authentication http key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 2119","type":"specification","body":"IETF","designation":"RFC 2119","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2119.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2119.txt","https://www.rfc-editor.org/rfc/rfc2119.pdf"],"folder":"IETF/RFC-2119","files":{"txt":{"path":"standards/IETF/RFC-2119/RFC-2119.txt","sha256":"3c2ceb7bfc84cd34720f4a5271338ab9d8280d34bdd1eb250c64306202f2ed8b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Bradner\nRequest for Comments: 2119 Harvard University\nBCP: 14 March 1997\nCategory: Best Current Practice\n\n Key words for use in RFCs to Indicate Requirement Levels\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n In many standards track documents several words are used to signify\n the requirements in the specification. These words are often\n capitalized. This document defines these words as they should be\n interpreted in IETF documents. Authors who follow these guidelines\n should incorporate this phrase near the beginning of their document:\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL\n NOT\", \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and\n \"OPTIONAL\" in this document are t","scope_keywords":["2119","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS03","folder":"ARF/TS03-V1.5.2","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md","version":"1.5.2"},{"body":"ARF","designation":"TS07","folder":"ARF/TS07-V0.11","source":"ARF/TS07-V0.11/TS07-V0.11.md","version":"0.11"},{"body":"ARF","designation":"TS08","folder":"ARF/TS08-V0.11","source":"ARF/TS08-V0.11/TS08-V0.11.md","version":"0.11"},{"body":"ARF","designation":"TS09","folder":"ARF/TS09-V1.1","source":"ARF/TS09-V1.1/TS09-V1.1.md","version":"1.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2180","folder":"IETF/RFC-2180","source":"IETF/RFC-2180/RFC-2180.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2193","folder":"IETF/RFC-2193","source":"IETF/RFC-2193/RFC-2193.txt","version":null},{"body":"IETF","designation":"RFC 2197","folder":"IETF/RFC-2197","source":"IETF/RFC-2197/RFC-2197.txt","version":null},{"body":"IETF","designation":"RFC 2198","folder":"IETF/RFC-2198","source":"IETF/RFC-2198/RFC-2198.txt","version":null},{"body":"IETF","designation":"RFC 2212","folder":"IETF/RFC-2212","source":"IETF/RFC-2212/RFC-2212.txt","version":null},{"body":"IETF","designation":"RFC 2221","folder":"IETF/RFC-2221","source":"IETF/RFC-2221/RFC-2221.txt","version":null},{"body":"IETF","designation":"RFC 2222","folder":"IETF/RFC-2222","source":"IETF/RFC-2222/RFC-2222.txt","version":null},{"body":"IETF","designation":"RFC 2223","folder":"IETF/RFC-2223","source":"IETF/RFC-2223/RFC-2223.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2227","folder":"IETF/RFC-2227","source":"IETF/RFC-2227/RFC-2227.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2236","folder":"IETF/RFC-2236","source":"IETF/RFC-2236/RFC-2236.txt","version":null},{"body":"IETF","designation":"RFC 2243","folder":"IETF/RFC-2243","source":"IETF/RFC-2243/RFC-2243.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2245","folder":"IETF/RFC-2245","source":"IETF/RFC-2245/RFC-2245.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2255","folder":"IETF/RFC-2255","source":"IETF/RFC-2255/RFC-2255.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2262","folder":"IETF/RFC-2262","source":"IETF/RFC-2262/RFC-2262.txt","version":null},{"body":"IETF","designation":"RFC 2264","folder":"IETF/RFC-2264","source":"IETF/RFC-2264/RFC-2264.txt","version":null},{"body":"IETF","designation":"RFC 2265","folder":"IETF/RFC-2265","source":"IETF/RFC-2265/RFC-2265.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2272","folder":"IETF/RFC-2272","source":"IETF/RFC-2272/RFC-2272.txt","version":null},{"body":"IETF","designation":"RFC 2274","folder":"IETF/RFC-2274","source":"IETF/RFC-2274/RFC-2274.txt","version":null},{"body":"IETF","designation":"RFC 2275","folder":"IETF/RFC-2275","source":"IETF/RFC-2275/RFC-2275.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2281","folder":"IETF/RFC-2281","source":"IETF/RFC-2281/RFC-2281.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2285","folder":"IETF/RFC-2285","source":"IETF/RFC-2285/RFC-2285.txt","version":null},{"body":"IETF","designation":"RFC 2290","folder":"IETF/RFC-2290","source":"IETF/RFC-2290/RFC-2290.txt","version":null},{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2301","folder":"IETF/RFC-2301","source":"IETF/RFC-2301/RFC-2301.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2306","folder":"IETF/RFC-2306","source":"IETF/RFC-2306/RFC-2306.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2308","folder":"IETF/RFC-2308","source":"IETF/RFC-2308/RFC-2308.txt","version":null},{"body":"IETF","designation":"RFC 2310","folder":"IETF/RFC-2310","source":"IETF/RFC-2310/RFC-2310.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2316","folder":"IETF/RFC-2316","source":"IETF/RFC-2316/RFC-2316.txt","version":null},{"body":"IETF","designation":"RFC 2320","folder":"IETF/RFC-2320","source":"IETF/RFC-2320/RFC-2320.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2334","folder":"IETF/RFC-2334","source":"IETF/RFC-2334/RFC-2334.txt","version":null},{"body":"IETF","designation":"RFC 2335","folder":"IETF/RFC-2335","source":"IETF/RFC-2335/RFC-2335.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2342","folder":"IETF/RFC-2342","source":"IETF/RFC-2342/RFC-2342.txt","version":null},{"body":"IETF","designation":"RFC 2344","folder":"IETF/RFC-2344","source":"IETF/RFC-2344/RFC-2344.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2359","folder":"IETF/RFC-2359","source":"IETF/RFC-2359/RFC-2359.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2367","folder":"IETF/RFC-2367","source":"IETF/RFC-2367/RFC-2367.txt","version":null},{"body":"IETF","designation":"RFC 2369","folder":"IETF/RFC-2369","source":"IETF/RFC-2369/RFC-2369.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2374","folder":"IETF/RFC-2374","source":"IETF/RFC-2374/RFC-2374.txt","version":null},{"body":"IETF","designation":"RFC 2375","folder":"IETF/RFC-2375","source":"IETF/RFC-2375/RFC-2375.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2379","folder":"IETF/RFC-2379","source":"IETF/RFC-2379/RFC-2379.txt","version":null},{"body":"IETF","designation":"RFC 2380","folder":"IETF/RFC-2380","source":"IETF/RFC-2380/RFC-2380.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2389","folder":"IETF/RFC-2389","source":"IETF/RFC-2389/RFC-2389.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2403","folder":"IETF/RFC-2403","source":"IETF/RFC-2403/RFC-2403.txt","version":null},{"body":"IETF","designation":"RFC 2404","folder":"IETF/RFC-2404","source":"IETF/RFC-2404/RFC-2404.txt","version":null},{"body":"IETF","designation":"RFC 2405","folder":"IETF/RFC-2405","source":"IETF/RFC-2405/RFC-2405.txt","version":null},{"body":"IETF","designation":"RFC 2406","folder":"IETF/RFC-2406","source":"IETF/RFC-2406/RFC-2406.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2410","folder":"IETF/RFC-2410","source":"IETF/RFC-2410/RFC-2410.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2418","folder":"IETF/RFC-2418","source":"IETF/RFC-2418/RFC-2418.txt","version":null},{"body":"IETF","designation":"RFC 2419","folder":"IETF/RFC-2419","source":"IETF/RFC-2419/RFC-2419.txt","version":null},{"body":"IETF","designation":"RFC 2420","folder":"IETF/RFC-2420","source":"IETF/RFC-2420/RFC-2420.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 2424","folder":"IETF/RFC-2424","source":"IETF/RFC-2424/RFC-2424.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2431","folder":"IETF/RFC-2431","source":"IETF/RFC-2431/RFC-2431.txt","version":null},{"body":"IETF","designation":"RFC 2433","folder":"IETF/RFC-2433","source":"IETF/RFC-2433/RFC-2433.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2435","folder":"IETF/RFC-2435","source":"IETF/RFC-2435/RFC-2435.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2446","folder":"IETF/RFC-2446","source":"IETF/RFC-2446/RFC-2446.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2450","folder":"IETF/RFC-2450","source":"IETF/RFC-2450/RFC-2450.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2462","folder":"IETF/RFC-2462","source":"IETF/RFC-2462/RFC-2462.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2471","folder":"IETF/RFC-2471","source":"IETF/RFC-2471/RFC-2471.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2473","folder":"IETF/RFC-2473","source":"IETF/RFC-2473/RFC-2473.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2477","folder":"IETF/RFC-2477","source":"IETF/RFC-2477/RFC-2477.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2483","folder":"IETF/RFC-2483","source":"IETF/RFC-2483/RFC-2483.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2492","folder":"IETF/RFC-2492","source":"IETF/RFC-2492/RFC-2492.txt","version":null},{"body":"IETF","designation":"RFC 2497","folder":"IETF/RFC-2497","source":"IETF/RFC-2497/RFC-2497.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2508","folder":"IETF/RFC-2508","source":"IETF/RFC-2508/RFC-2508.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2511","folder":"IETF/RFC-2511","source":"IETF/RFC-2511/RFC-2511.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2526","folder":"IETF/RFC-2526","source":"IETF/RFC-2526/RFC-2526.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2535","folder":"IETF/RFC-2535","source":"IETF/RFC-2535/RFC-2535.txt","version":null},{"body":"IETF","designation":"RFC 2537","folder":"IETF/RFC-2537","source":"IETF/RFC-2537/RFC-2537.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2546","folder":"IETF/RFC-2546","source":"IETF/RFC-2546/RFC-2546.txt","version":null},{"body":"IETF","designation":"RFC 2548","folder":"IETF/RFC-2548","source":"IETF/RFC-2548/RFC-2548.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2559","folder":"IETF/RFC-2559","source":"IETF/RFC-2559/RFC-2559.txt","version":null},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2572","folder":"IETF/RFC-2572","source":"IETF/RFC-2572/RFC-2572.txt","version":null},{"body":"IETF","designation":"RFC 2573","folder":"IETF/RFC-2573","source":"IETF/RFC-2573/RFC-2573.txt","version":null},{"body":"IETF","designation":"RFC 2574","folder":"IETF/RFC-2574","source":"IETF/RFC-2574/RFC-2574.txt","version":null},{"body":"IETF","designation":"RFC 2575","folder":"IETF/RFC-2575","source":"IETF/RFC-2575/RFC-2575.txt","version":null},{"body":"IETF","designation":"RFC 2576","folder":"IETF/RFC-2576","source":"IETF/RFC-2576/RFC-2576.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2587","folder":"IETF/RFC-2587","source":"IETF/RFC-2587/RFC-2587.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2591","folder":"IETF/RFC-2591","source":"IETF/RFC-2591/RFC-2591.txt","version":null},{"body":"IETF","designation":"RFC 2592","folder":"IETF/RFC-2592","source":"IETF/RFC-2592/RFC-2592.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2596","folder":"IETF/RFC-2596","source":"IETF/RFC-2596/RFC-2596.txt","version":null},{"body":"IETF","designation":"RFC 2597","folder":"IETF/RFC-2597","source":"IETF/RFC-2597/RFC-2597.txt","version":null},{"body":"IETF","designation":"RFC 2598","folder":"IETF/RFC-2598","source":"IETF/RFC-2598/RFC-2598.txt","version":null},{"body":"IETF","designation":"RFC 2607","folder":"IETF/RFC-2607","source":"IETF/RFC-2607/RFC-2607.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2610","folder":"IETF/RFC-2610","source":"IETF/RFC-2610/RFC-2610.txt","version":null},{"body":"IETF","designation":"RFC 2613","folder":"IETF/RFC-2613","source":"IETF/RFC-2613/RFC-2613.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2615","folder":"IETF/RFC-2615","source":"IETF/RFC-2615/RFC-2615.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2623","folder":"IETF/RFC-2623","source":"IETF/RFC-2623/RFC-2623.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2631","folder":"IETF/RFC-2631","source":"IETF/RFC-2631/RFC-2631.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2639","folder":"IETF/RFC-2639","source":"IETF/RFC-2639/RFC-2639.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2644","folder":"IETF/RFC-2644","source":"IETF/RFC-2644/RFC-2644.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2650","folder":"IETF/RFC-2650","source":"IETF/RFC-2650/RFC-2650.txt","version":null},{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2658","folder":"IETF/RFC-2658","source":"IETF/RFC-2658/RFC-2658.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 2668","folder":"IETF/RFC-2668","source":"IETF/RFC-2668/RFC-2668.txt","version":null},{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2672","folder":"IETF/RFC-2672","source":"IETF/RFC-2672/RFC-2672.txt","version":null},{"body":"IETF","designation":"RFC 2673","folder":"IETF/RFC-2673","source":"IETF/RFC-2673/RFC-2673.txt","version":null},{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2686","folder":"IETF/RFC-2686","source":"IETF/RFC-2686/RFC-2686.txt","version":null},{"body":"IETF","designation":"RFC 2687","folder":"IETF/RFC-2687","source":"IETF/RFC-2687/RFC-2687.txt","version":null},{"body":"IETF","designation":"RFC 2696","folder":"IETF/RFC-2696","source":"IETF/RFC-2696/RFC-2696.txt","version":null},{"body":"IETF","designation":"RFC 2702","folder":"IETF/RFC-2702","source":"IETF/RFC-2702/RFC-2702.txt","version":null},{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 2711","folder":"IETF/RFC-2711","source":"IETF/RFC-2711/RFC-2711.txt","version":null},{"body":"IETF","designation":"RFC 2715","folder":"IETF/RFC-2715","source":"IETF/RFC-2715/RFC-2715.txt","version":null},{"body":"IETF","designation":"RFC 2716","folder":"IETF/RFC-2716","source":"IETF/RFC-2716/RFC-2716.txt","version":null},{"body":"IETF","designation":"RFC 2717","folder":"IETF/RFC-2717","source":"IETF/RFC-2717/RFC-2717.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2733","folder":"IETF/RFC-2733","source":"IETF/RFC-2733/RFC-2733.txt","version":null},{"body":"IETF","designation":"RFC 2734","folder":"IETF/RFC-2734","source":"IETF/RFC-2734/RFC-2734.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2759","folder":"IETF/RFC-2759","source":"IETF/RFC-2759/RFC-2759.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2766","folder":"IETF/RFC-2766","source":"IETF/RFC-2766/RFC-2766.txt","version":null},{"body":"IETF","designation":"RFC 2769","folder":"IETF/RFC-2769","source":"IETF/RFC-2769/RFC-2769.txt","version":null},{"body":"IETF","designation":"RFC 2772","folder":"IETF/RFC-2772","source":"IETF/RFC-2772/RFC-2772.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2779","folder":"IETF/RFC-2779","source":"IETF/RFC-2779/RFC-2779.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2784","folder":"IETF/RFC-2784","source":"IETF/RFC-2784/RFC-2784.txt","version":null},{"body":"IETF","designation":"RFC 2786","folder":"IETF/RFC-2786","source":"IETF/RFC-2786/RFC-2786.txt","version":null},{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2794","folder":"IETF/RFC-2794","source":"IETF/RFC-2794/RFC-2794.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2809","folder":"IETF/RFC-2809","source":"IETF/RFC-2809/RFC-2809.txt","version":null},{"body":"IETF","designation":"RFC 2810","folder":"IETF/RFC-2810","source":"IETF/RFC-2810/RFC-2810.txt","version":null},{"body":"IETF","designation":"RFC 2811","folder":"IETF/RFC-2811","source":"IETF/RFC-2811/RFC-2811.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2817","folder":"IETF/RFC-2817","source":"IETF/RFC-2817/RFC-2817.txt","version":null},{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2833","folder":"IETF/RFC-2833","source":"IETF/RFC-2833/RFC-2833.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2836","folder":"IETF/RFC-2836","source":"IETF/RFC-2836/RFC-2836.txt","version":null},{"body":"IETF","designation":"RFC 2845","folder":"IETF/RFC-2845","source":"IETF/RFC-2845/RFC-2845.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2851","folder":"IETF/RFC-2851","source":"IETF/RFC-2851/RFC-2851.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2855","folder":"IETF/RFC-2855","source":"IETF/RFC-2855/RFC-2855.txt","version":null},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 2862","folder":"IETF/RFC-2862","source":"IETF/RFC-2862/RFC-2862.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2867","folder":"IETF/RFC-2867","source":"IETF/RFC-2867/RFC-2867.txt","version":null},{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2870","folder":"IETF/RFC-2870","source":"IETF/RFC-2870/RFC-2870.txt","version":null},{"body":"IETF","designation":"RFC 2872","folder":"IETF/RFC-2872","source":"IETF/RFC-2872/RFC-2872.txt","version":null},{"body":"IETF","designation":"RFC 2874","folder":"IETF/RFC-2874","source":"IETF/RFC-2874/RFC-2874.txt","version":null},{"body":"IETF","designation":"RFC 2876","folder":"IETF/RFC-2876","source":"IETF/RFC-2876/RFC-2876.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 2886","folder":"IETF/RFC-2886","source":"IETF/RFC-2886/RFC-2886.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 2890","folder":"IETF/RFC-2890","source":"IETF/RFC-2890/RFC-2890.txt","version":null},{"body":"IETF","designation":"RFC 2891","folder":"IETF/RFC-2891","source":"IETF/RFC-2891/RFC-2891.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2894","folder":"IETF/RFC-2894","source":"IETF/RFC-2894/RFC-2894.txt","version":null},{"body":"IETF","designation":"RFC 2895","folder":"IETF/RFC-2895","source":"IETF/RFC-2895/RFC-2895.txt","version":null},{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2905","folder":"IETF/RFC-2905","source":"IETF/RFC-2905/RFC-2905.txt","version":null},{"body":"IETF","designation":"RFC 2906","folder":"IETF/RFC-2906","source":"IETF/RFC-2906/RFC-2906.txt","version":null},{"body":"IETF","designation":"RFC 2907","folder":"IETF/RFC-2907","source":"IETF/RFC-2907/RFC-2907.txt","version":null},{"body":"IETF","designation":"RFC 2909","folder":"IETF/RFC-2909","source":"IETF/RFC-2909/RFC-2909.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2916","folder":"IETF/RFC-2916","source":"IETF/RFC-2916/RFC-2916.txt","version":null},{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 2927","folder":"IETF/RFC-2927","source":"IETF/RFC-2927/RFC-2927.txt","version":null},{"body":"IETF","designation":"RFC 2930","folder":"IETF/RFC-2930","source":"IETF/RFC-2930/RFC-2930.txt","version":null},{"body":"IETF","designation":"RFC 2931","folder":"IETF/RFC-2931","source":"IETF/RFC-2931/RFC-2931.txt","version":null},{"body":"IETF","designation":"RFC 2937","folder":"IETF/RFC-2937","source":"IETF/RFC-2937/RFC-2937.txt","version":null},{"body":"IETF","designation":"RFC 2955","folder":"IETF/RFC-2955","source":"IETF/RFC-2955/RFC-2955.txt","version":null},{"body":"IETF","designation":"RFC 2959","folder":"IETF/RFC-2959","source":"IETF/RFC-2959/RFC-2959.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2961","folder":"IETF/RFC-2961","source":"IETF/RFC-2961/RFC-2961.txt","version":null},{"body":"IETF","designation":"RFC 2965","folder":"IETF/RFC-2965","source":"IETF/RFC-2965/RFC-2965.txt","version":null},{"body":"IETF","designation":"RFC 2971","folder":"IETF/RFC-2971","source":"IETF/RFC-2971/RFC-2971.txt","version":null},{"body":"IETF","designation":"RFC 2974","folder":"IETF/RFC-2974","source":"IETF/RFC-2974/RFC-2974.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 2979","folder":"IETF/RFC-2979","source":"IETF/RFC-2979/RFC-2979.txt","version":null},{"body":"IETF","designation":"RFC 2981","folder":"IETF/RFC-2981","source":"IETF/RFC-2981/RFC-2981.txt","version":null},{"body":"IETF","designation":"RFC 2982","folder":"IETF/RFC-2982","source":"IETF/RFC-2982/RFC-2982.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 2988","folder":"IETF/RFC-2988","source":"IETF/RFC-2988/RFC-2988.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3004","folder":"IETF/RFC-3004","source":"IETF/RFC-3004/RFC-3004.txt","version":null},{"body":"IETF","designation":"RFC 3007","folder":"IETF/RFC-3007","source":"IETF/RFC-3007/RFC-3007.txt","version":null},{"body":"IETF","designation":"RFC 3008","folder":"IETF/RFC-3008","source":"IETF/RFC-3008/RFC-3008.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3011","folder":"IETF/RFC-3011","source":"IETF/RFC-3011/RFC-3011.txt","version":null},{"body":"IETF","designation":"RFC 3012","folder":"IETF/RFC-3012","source":"IETF/RFC-3012/RFC-3012.txt","version":null},{"body":"IETF","designation":"RFC 3013","folder":"IETF/RFC-3013","source":"IETF/RFC-3013/RFC-3013.txt","version":null},{"body":"IETF","designation":"RFC 3014","folder":"IETF/RFC-3014","source":"IETF/RFC-3014/RFC-3014.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3019","folder":"IETF/RFC-3019","source":"IETF/RFC-3019/RFC-3019.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3024","folder":"IETF/RFC-3024","source":"IETF/RFC-3024/RFC-3024.txt","version":null},{"body":"IETF","designation":"RFC 3025","folder":"IETF/RFC-3025","source":"IETF/RFC-3025/RFC-3025.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3046","folder":"IETF/RFC-3046","source":"IETF/RFC-3046/RFC-3046.txt","version":null},{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3049","folder":"IETF/RFC-3049","source":"IETF/RFC-3049/RFC-3049.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3051","folder":"IETF/RFC-3051","source":"IETF/RFC-3051/RFC-3051.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3059","folder":"IETF/RFC-3059","source":"IETF/RFC-3059/RFC-3059.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3070","folder":"IETF/RFC-3070","source":"IETF/RFC-3070/RFC-3070.txt","version":null},{"body":"IETF","designation":"RFC 3074","folder":"IETF/RFC-3074","source":"IETF/RFC-3074/RFC-3074.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3078","folder":"IETF/RFC-3078","source":"IETF/RFC-3078/RFC-3078.txt","version":null},{"body":"IETF","designation":"RFC 3079","folder":"IETF/RFC-3079","source":"IETF/RFC-3079/RFC-3079.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3090","folder":"IETF/RFC-3090","source":"IETF/RFC-3090/RFC-3090.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3102","folder":"IETF/RFC-3102","source":"IETF/RFC-3102/RFC-3102.txt","version":null},{"body":"IETF","designation":"RFC 3103","folder":"IETF/RFC-3103","source":"IETF/RFC-3103/RFC-3103.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3110","folder":"IETF/RFC-3110","source":"IETF/RFC-3110/RFC-3110.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3115","folder":"IETF/RFC-3115","source":"IETF/RFC-3115/RFC-3115.txt","version":null},{"body":"IETF","designation":"RFC 3118","folder":"IETF/RFC-3118","source":"IETF/RFC-3118/RFC-3118.txt","version":null},{"body":"IETF","designation":"RFC 3122","folder":"IETF/RFC-3122","source":"IETF/RFC-3122/RFC-3122.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3138","folder":"IETF/RFC-3138","source":"IETF/RFC-3138/RFC-3138.txt","version":null},{"body":"IETF","designation":"RFC 3139","folder":"IETF/RFC-3139","source":"IETF/RFC-3139/RFC-3139.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3141","folder":"IETF/RFC-3141","source":"IETF/RFC-3141/RFC-3141.txt","version":null},{"body":"IETF","designation":"RFC 3144","folder":"IETF/RFC-3144","source":"IETF/RFC-3144/RFC-3144.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3153","folder":"IETF/RFC-3153","source":"IETF/RFC-3153/RFC-3153.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3157","folder":"IETF/RFC-3157","source":"IETF/RFC-3157/RFC-3157.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3165","folder":"IETF/RFC-3165","source":"IETF/RFC-3165/RFC-3165.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3171","folder":"IETF/RFC-3171","source":"IETF/RFC-3171/RFC-3171.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3190","folder":"IETF/RFC-3190","source":"IETF/RFC-3190/RFC-3190.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3195","folder":"IETF/RFC-3195","source":"IETF/RFC-3195/RFC-3195.txt","version":null},{"body":"IETF","designation":"RFC 3203","folder":"IETF/RFC-3203","source":"IETF/RFC-3203/RFC-3203.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3206","folder":"IETF/RFC-3206","source":"IETF/RFC-3206/RFC-3206.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3208","folder":"IETF/RFC-3208","source":"IETF/RFC-3208/RFC-3208.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3211","folder":"IETF/RFC-3211","source":"IETF/RFC-3211/RFC-3211.txt","version":null},{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3217","folder":"IETF/RFC-3217","source":"IETF/RFC-3217/RFC-3217.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3224","folder":"IETF/RFC-3224","source":"IETF/RFC-3224/RFC-3224.txt","version":null},{"body":"IETF","designation":"RFC 3225","folder":"IETF/RFC-3225","source":"IETF/RFC-3225/RFC-3225.txt","version":null},{"body":"IETF","designation":"RFC 3226","folder":"IETF/RFC-3226","source":"IETF/RFC-3226/RFC-3226.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3230","folder":"IETF/RFC-3230","source":"IETF/RFC-3230/RFC-3230.txt","version":null},{"body":"IETF","designation":"RFC 3231","folder":"IETF/RFC-3231","source":"IETF/RFC-3231/RFC-3231.txt","version":null},{"body":"IETF","designation":"RFC 3241","folder":"IETF/RFC-3241","source":"IETF/RFC-3241/RFC-3241.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3247","folder":"IETF/RFC-3247","source":"IETF/RFC-3247/RFC-3247.txt","version":null},{"body":"IETF","designation":"RFC 3248","folder":"IETF/RFC-3248","source":"IETF/RFC-3248/RFC-3248.txt","version":null},{"body":"IETF","designation":"RFC 3250","folder":"IETF/RFC-3250","source":"IETF/RFC-3250/RFC-3250.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3262","folder":"IETF/RFC-3262","source":"IETF/RFC-3262/RFC-3262.txt","version":null},{"body":"IETF","designation":"RFC 3263","folder":"IETF/RFC-3263","source":"IETF/RFC-3263/RFC-3263.txt","version":null},{"body":"IETF","designation":"RFC 3264","folder":"IETF/RFC-3264","source":"IETF/RFC-3264/RFC-3264.txt","version":null},{"body":"IETF","designation":"RFC 3265","folder":"IETF/RFC-3265","source":"IETF/RFC-3265/RFC-3265.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3273","folder":"IETF/RFC-3273","source":"IETF/RFC-3273/RFC-3273.txt","version":null},{"body":"IETF","designation":"RFC 3274","folder":"IETF/RFC-3274","source":"IETF/RFC-3274/RFC-3274.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3287","folder":"IETF/RFC-3287","source":"IETF/RFC-3287/RFC-3287.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3296","folder":"IETF/RFC-3296","source":"IETF/RFC-3296/RFC-3296.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3302","folder":"IETF/RFC-3302","source":"IETF/RFC-3302/RFC-3302.txt","version":null},{"body":"IETF","designation":"RFC 3306","folder":"IETF/RFC-3306","source":"IETF/RFC-3306/RFC-3306.txt","version":null},{"body":"IETF","designation":"RFC 3307","folder":"IETF/RFC-3307","source":"IETF/RFC-3307/RFC-3307.txt","version":null},{"body":"IETF","designation":"RFC 3308","folder":"IETF/RFC-3308","source":"IETF/RFC-3308/RFC-3308.txt","version":null},{"body":"IETF","designation":"RFC 3309","folder":"IETF/RFC-3309","source":"IETF/RFC-3309/RFC-3309.txt","version":null},{"body":"IETF","designation":"RFC 3310","folder":"IETF/RFC-3310","source":"IETF/RFC-3310/RFC-3310.txt","version":null},{"body":"IETF","designation":"RFC 3311","folder":"IETF/RFC-3311","source":"IETF/RFC-3311/RFC-3311.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3314","folder":"IETF/RFC-3314","source":"IETF/RFC-3314/RFC-3314.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3323","folder":"IETF/RFC-3323","source":"IETF/RFC-3323/RFC-3323.txt","version":null},{"body":"IETF","designation":"RFC 3325","folder":"IETF/RFC-3325","source":"IETF/RFC-3325/RFC-3325.txt","version":null},{"body":"IETF","designation":"RFC 3326","folder":"IETF/RFC-3326","source":"IETF/RFC-3326/RFC-3326.txt","version":null},{"body":"IETF","designation":"RFC 3327","folder":"IETF/RFC-3327","source":"IETF/RFC-3327/RFC-3327.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3347","folder":"IETF/RFC-3347","source":"IETF/RFC-3347/RFC-3347.txt","version":null},{"body":"IETF","designation":"RFC 3348","folder":"IETF/RFC-3348","source":"IETF/RFC-3348/RFC-3348.txt","version":null},{"body":"IETF","designation":"RFC 3351","folder":"IETF/RFC-3351","source":"IETF/RFC-3351/RFC-3351.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3357","folder":"IETF/RFC-3357","source":"IETF/RFC-3357/RFC-3357.txt","version":null},{"body":"IETF","designation":"RFC 3358","folder":"IETF/RFC-3358","source":"IETF/RFC-3358/RFC-3358.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3362","folder":"IETF/RFC-3362","source":"IETF/RFC-3362/RFC-3362.txt","version":null},{"body":"IETF","designation":"RFC 3365","folder":"IETF/RFC-3365","source":"IETF/RFC-3365/RFC-3365.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3368","folder":"IETF/RFC-3368","source":"IETF/RFC-3368/RFC-3368.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3371","folder":"IETF/RFC-3371","source":"IETF/RFC-3371/RFC-3371.txt","version":null},{"body":"IETF","designation":"RFC 3373","folder":"IETF/RFC-3373","source":"IETF/RFC-3373/RFC-3373.txt","version":null},{"body":"IETF","designation":"RFC 3375","folder":"IETF/RFC-3375","source":"IETF/RFC-3375/RFC-3375.txt","version":null},{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3386","folder":"IETF/RFC-3386","source":"IETF/RFC-3386/RFC-3386.txt","version":null},{"body":"IETF","designation":"RFC 3388","folder":"IETF/RFC-3388","source":"IETF/RFC-3388/RFC-3388.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3392","folder":"IETF/RFC-3392","source":"IETF/RFC-3392/RFC-3392.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3395","folder":"IETF/RFC-3395","source":"IETF/RFC-3395/RFC-3395.txt","version":null},{"body":"IETF","designation":"RFC 3396","folder":"IETF/RFC-3396","source":"IETF/RFC-3396/RFC-3396.txt","version":null},{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3407","folder":"IETF/RFC-3407","source":"IETF/RFC-3407/RFC-3407.txt","version":null},{"body":"IETF","designation":"RFC 3408","folder":"IETF/RFC-3408","source":"IETF/RFC-3408/RFC-3408.txt","version":null},{"body":"IETF","designation":"RFC 3410","folder":"IETF/RFC-3410","source":"IETF/RFC-3410/RFC-3410.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3412","folder":"IETF/RFC-3412","source":"IETF/RFC-3412/RFC-3412.txt","version":null},{"body":"IETF","designation":"RFC 3413","folder":"IETF/RFC-3413","source":"IETF/RFC-3413/RFC-3413.txt","version":null},{"body":"IETF","designation":"RFC 3414","folder":"IETF/RFC-3414","source":"IETF/RFC-3414/RFC-3414.txt","version":null},{"body":"IETF","designation":"RFC 3415","folder":"IETF/RFC-3415","source":"IETF/RFC-3415/RFC-3415.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3418","folder":"IETF/RFC-3418","source":"IETF/RFC-3418/RFC-3418.txt","version":null},{"body":"IETF","designation":"RFC 3419","folder":"IETF/RFC-3419","source":"IETF/RFC-3419/RFC-3419.txt","version":null},{"body":"IETF","designation":"RFC 3420","folder":"IETF/RFC-3420","source":"IETF/RFC-3420/RFC-3420.txt","version":null},{"body":"IETF","designation":"RFC 3421","folder":"IETF/RFC-3421","source":"IETF/RFC-3421/RFC-3421.txt","version":null},{"body":"IETF","designation":"RFC 3423","folder":"IETF/RFC-3423","source":"IETF/RFC-3423/RFC-3423.txt","version":null},{"body":"IETF","designation":"RFC 3425","folder":"IETF/RFC-3425","source":"IETF/RFC-3425/RFC-3425.txt","version":null},{"body":"IETF","designation":"RFC 3427","folder":"IETF/RFC-3427","source":"IETF/RFC-3427/RFC-3427.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3431","folder":"IETF/RFC-3431","source":"IETF/RFC-3431/RFC-3431.txt","version":null},{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null},{"body":"IETF","designation":"RFC 3433","folder":"IETF/RFC-3433","source":"IETF/RFC-3433/RFC-3433.txt","version":null},{"body":"IETF","designation":"RFC 3434","folder":"IETF/RFC-3434","source":"IETF/RFC-3434/RFC-3434.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3438","folder":"IETF/RFC-3438","source":"IETF/RFC-3438/RFC-3438.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3445","folder":"IETF/RFC-3445","source":"IETF/RFC-3445/RFC-3445.txt","version":null},{"body":"IETF","designation":"RFC 3446","folder":"IETF/RFC-3446","source":"IETF/RFC-3446/RFC-3446.txt","version":null},{"body":"IETF","designation":"RFC 3448","folder":"IETF/RFC-3448","source":"IETF/RFC-3448/RFC-3448.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3454","folder":"IETF/RFC-3454","source":"IETF/RFC-3454/RFC-3454.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3457","folder":"IETF/RFC-3457","source":"IETF/RFC-3457/RFC-3457.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3463","folder":"IETF/RFC-3463","source":"IETF/RFC-3463/RFC-3463.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3477","folder":"IETF/RFC-3477","source":"IETF/RFC-3477/RFC-3477.txt","version":null},{"body":"IETF","designation":"RFC 3478","folder":"IETF/RFC-3478","source":"IETF/RFC-3478/RFC-3478.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3484","folder":"IETF/RFC-3484","source":"IETF/RFC-3484/RFC-3484.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3486","folder":"IETF/RFC-3486","source":"IETF/RFC-3486/RFC-3486.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3492","folder":"IETF/RFC-3492","source":"IETF/RFC-3492/RFC-3492.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3503","folder":"IETF/RFC-3503","source":"IETF/RFC-3503/RFC-3503.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3516","folder":"IETF/RFC-3516","source":"IETF/RFC-3516/RFC-3516.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3524","folder":"IETF/RFC-3524","source":"IETF/RFC-3524/RFC-3524.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3528","folder":"IETF/RFC-3528","source":"IETF/RFC-3528/RFC-3528.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3533","folder":"IETF/RFC-3533","source":"IETF/RFC-3533/RFC-3533.txt","version":null},{"body":"IETF","designation":"RFC 3534","folder":"IETF/RFC-3534","source":"IETF/RFC-3534/RFC-3534.txt","version":null},{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3540","folder":"IETF/RFC-3540","source":"IETF/RFC-3540/RFC-3540.txt","version":null},{"body":"IETF","designation":"RFC 3543","folder":"IETF/RFC-3543","source":"IETF/RFC-3543/RFC-3543.txt","version":null},{"body":"IETF","designation":"RFC 3545","folder":"IETF/RFC-3545","source":"IETF/RFC-3545/RFC-3545.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3548","folder":"IETF/RFC-3548","source":"IETF/RFC-3548/RFC-3548.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3561","folder":"IETF/RFC-3561","source":"IETF/RFC-3561/RFC-3561.txt","version":null},{"body":"IETF","designation":"RFC 3562","folder":"IETF/RFC-3562","source":"IETF/RFC-3562/RFC-3562.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3566","folder":"IETF/RFC-3566","source":"IETF/RFC-3566/RFC-3566.txt","version":null},{"body":"IETF","designation":"RFC 3569","folder":"IETF/RFC-3569","source":"IETF/RFC-3569/RFC-3569.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3581","folder":"IETF/RFC-3581","source":"IETF/RFC-3581/RFC-3581.txt","version":null},{"body":"IETF","designation":"RFC 3583","folder":"IETF/RFC-3583","source":"IETF/RFC-3583/RFC-3583.txt","version":null},{"body":"IETF","designation":"RFC 3584","folder":"IETF/RFC-3584","source":"IETF/RFC-3584/RFC-3584.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3586","folder":"IETF/RFC-3586","source":"IETF/RFC-3586/RFC-3586.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3590","folder":"IETF/RFC-3590","source":"IETF/RFC-3590/RFC-3590.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3597","folder":"IETF/RFC-3597","source":"IETF/RFC-3597/RFC-3597.txt","version":null},{"body":"IETF","designation":"RFC 3598","folder":"IETF/RFC-3598","source":"IETF/RFC-3598/RFC-3598.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3608","folder":"IETF/RFC-3608","source":"IETF/RFC-3608/RFC-3608.txt","version":null},{"body":"IETF","designation":"RFC 3610","folder":"IETF/RFC-3610","source":"IETF/RFC-3610/RFC-3610.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3618","folder":"IETF/RFC-3618","source":"IETF/RFC-3618/RFC-3618.txt","version":null},{"body":"IETF","designation":"RFC 3621","folder":"IETF/RFC-3621","source":"IETF/RFC-3621/RFC-3621.txt","version":null},{"body":"IETF","designation":"RFC 3626","folder":"IETF/RFC-3626","source":"IETF/RFC-3626/RFC-3626.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3633","folder":"IETF/RFC-3633","source":"IETF/RFC-3633/RFC-3633.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 3636","folder":"IETF/RFC-3636","source":"IETF/RFC-3636/RFC-3636.txt","version":null},{"body":"IETF","designation":"RFC 3637","folder":"IETF/RFC-3637","source":"IETF/RFC-3637/RFC-3637.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3643","folder":"IETF/RFC-3643","source":"IETF/RFC-3643/RFC-3643.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 3646","folder":"IETF/RFC-3646","source":"IETF/RFC-3646/RFC-3646.txt","version":null},{"body":"IETF","designation":"RFC 3648","folder":"IETF/RFC-3648","source":"IETF/RFC-3648/RFC-3648.txt","version":null},{"body":"IETF","designation":"RFC 3655","folder":"IETF/RFC-3655","source":"IETF/RFC-3655/RFC-3655.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3665","folder":"IETF/RFC-3665","source":"IETF/RFC-3665/RFC-3665.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3674","folder":"IETF/RFC-3674","source":"IETF/RFC-3674/RFC-3674.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3683","folder":"IETF/RFC-3683","source":"IETF/RFC-3683/RFC-3683.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3685","folder":"IETF/RFC-3685","source":"IETF/RFC-3685/RFC-3685.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3688","folder":"IETF/RFC-3688","source":"IETF/RFC-3688/RFC-3688.txt","version":null},{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 3690","folder":"IETF/RFC-3690","source":"IETF/RFC-3690/RFC-3690.txt","version":null},{"body":"IETF","designation":"RFC 3691","folder":"IETF/RFC-3691","source":"IETF/RFC-3691/RFC-3691.txt","version":null},{"body":"IETF","designation":"RFC 3693","folder":"IETF/RFC-3693","source":"IETF/RFC-3693/RFC-3693.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3697","folder":"IETF/RFC-3697","source":"IETF/RFC-3697/RFC-3697.txt","version":null},{"body":"IETF","designation":"RFC 3701","folder":"IETF/RFC-3701","source":"IETF/RFC-3701/RFC-3701.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3706","folder":"IETF/RFC-3706","source":"IETF/RFC-3706/RFC-3706.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3726","folder":"IETF/RFC-3726","source":"IETF/RFC-3726/RFC-3726.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3741","folder":"IETF/RFC-3741","source":"IETF/RFC-3741/RFC-3741.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3749","folder":"IETF/RFC-3749","source":"IETF/RFC-3749/RFC-3749.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 3757","folder":"IETF/RFC-3757","source":"IETF/RFC-3757/RFC-3757.txt","version":null},{"body":"IETF","designation":"RFC 3758","folder":"IETF/RFC-3758","source":"IETF/RFC-3758/RFC-3758.txt","version":null},{"body":"IETF","designation":"RFC 3760","folder":"IETF/RFC-3760","source":"IETF/RFC-3760/RFC-3760.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 3770","folder":"IETF/RFC-3770","source":"IETF/RFC-3770/RFC-3770.txt","version":null},{"body":"IETF","designation":"RFC 3771","folder":"IETF/RFC-3771","source":"IETF/RFC-3771/RFC-3771.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3782","folder":"IETF/RFC-3782","source":"IETF/RFC-3782/RFC-3782.txt","version":null},{"body":"IETF","designation":"RFC 3783","folder":"IETF/RFC-3783","source":"IETF/RFC-3783/RFC-3783.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 3803","folder":"IETF/RFC-3803","source":"IETF/RFC-3803/RFC-3803.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 3809","folder":"IETF/RFC-3809","source":"IETF/RFC-3809/RFC-3809.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3820","folder":"IETF/RFC-3820","source":"IETF/RFC-3820/RFC-3820.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3822","folder":"IETF/RFC-3822","source":"IETF/RFC-3822/RFC-3822.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3825","folder":"IETF/RFC-3825","source":"IETF/RFC-3825/RFC-3825.txt","version":null},{"body":"IETF","designation":"RFC 3826","folder":"IETF/RFC-3826","source":"IETF/RFC-3826/RFC-3826.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3831","folder":"IETF/RFC-3831","source":"IETF/RFC-3831/RFC-3831.txt","version":null},{"body":"IETF","designation":"RFC 3832","folder":"IETF/RFC-3832","source":"IETF/RFC-3832/RFC-3832.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3839","folder":"IETF/RFC-3839","source":"IETF/RFC-3839/RFC-3839.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3843","folder":"IETF/RFC-3843","source":"IETF/RFC-3843/RFC-3843.txt","version":null},{"body":"IETF","designation":"RFC 3845","folder":"IETF/RFC-3845","source":"IETF/RFC-3845/RFC-3845.txt","version":null},{"body":"IETF","designation":"RFC 3846","folder":"IETF/RFC-3846","source":"IETF/RFC-3846/RFC-3846.txt","version":null},{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3857","folder":"IETF/RFC-3857","source":"IETF/RFC-3857/RFC-3857.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 3873","folder":"IETF/RFC-3873","source":"IETF/RFC-3873/RFC-3873.txt","version":null},{"body":"IETF","designation":"RFC 3874","folder":"IETF/RFC-3874","source":"IETF/RFC-3874/RFC-3874.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3877","folder":"IETF/RFC-3877","source":"IETF/RFC-3877/RFC-3877.txt","version":null},{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 3894","folder":"IETF/RFC-3894","source":"IETF/RFC-3894/RFC-3894.txt","version":null},{"body":"IETF","designation":"RFC 3898","folder":"IETF/RFC-3898","source":"IETF/RFC-3898/RFC-3898.txt","version":null},{"body":"IETF","designation":"RFC 3902","folder":"IETF/RFC-3902","source":"IETF/RFC-3902/RFC-3902.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3913","folder":"IETF/RFC-3913","source":"IETF/RFC-3913/RFC-3913.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3918","folder":"IETF/RFC-3918","source":"IETF/RFC-3918/RFC-3918.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3926","folder":"IETF/RFC-3926","source":"IETF/RFC-3926/RFC-3926.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3936","folder":"IETF/RFC-3936","source":"IETF/RFC-3936/RFC-3936.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 3943","folder":"IETF/RFC-3943","source":"IETF/RFC-3943/RFC-3943.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null},{"body":"IETF","designation":"RFC 3951","folder":"IETF/RFC-3951","source":"IETF/RFC-3951/RFC-3951.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3956","folder":"IETF/RFC-3956","source":"IETF/RFC-3956/RFC-3956.txt","version":null},{"body":"IETF","designation":"RFC 3957","folder":"IETF/RFC-3957","source":"IETF/RFC-3957/RFC-3957.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 3962","folder":"IETF/RFC-3962","source":"IETF/RFC-3962/RFC-3962.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 3969","folder":"IETF/RFC-3969","source":"IETF/RFC-3969/RFC-3969.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 3973","folder":"IETF/RFC-3973","source":"IETF/RFC-3973/RFC-3973.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 3993","folder":"IETF/RFC-3993","source":"IETF/RFC-3993/RFC-3993.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4003","folder":"IETF/RFC-4003","source":"IETF/RFC-4003/RFC-4003.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4016","folder":"IETF/RFC-4016","source":"IETF/RFC-4016/RFC-4016.txt","version":null},{"body":"IETF","designation":"RFC 4017","folder":"IETF/RFC-4017","source":"IETF/RFC-4017/RFC-4017.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4035","folder":"IETF/RFC-4035","source":"IETF/RFC-4035/RFC-4035.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4049","folder":"IETF/RFC-4049","source":"IETF/RFC-4049/RFC-4049.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4056","folder":"IETF/RFC-4056","source":"IETF/RFC-4056/RFC-4056.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4068","folder":"IETF/RFC-4068","source":"IETF/RFC-4068/RFC-4068.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4073","folder":"IETF/RFC-4073","source":"IETF/RFC-4073/RFC-4073.txt","version":null},{"body":"IETF","designation":"RFC 4075","folder":"IETF/RFC-4075","source":"IETF/RFC-4075/RFC-4075.txt","version":null},{"body":"IETF","designation":"RFC 4084","folder":"IETF/RFC-4084","source":"IETF/RFC-4084/RFC-4084.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4090","folder":"IETF/RFC-4090","source":"IETF/RFC-4090/RFC-4090.txt","version":null},{"body":"IETF","designation":"RFC 4091","folder":"IETF/RFC-4091","source":"IETF/RFC-4091/RFC-4091.txt","version":null},{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4118","folder":"IETF/RFC-4118","source":"IETF/RFC-4118/RFC-4118.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4137","folder":"IETF/RFC-4137","source":"IETF/RFC-4137/RFC-4137.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4139","folder":"IETF/RFC-4139","source":"IETF/RFC-4139/RFC-4139.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 4143","folder":"IETF/RFC-4143","source":"IETF/RFC-4143/RFC-4143.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4155","folder":"IETF/RFC-4155","source":"IETF/RFC-4155/RFC-4155.txt","version":null},{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 4164","folder":"IETF/RFC-4164","source":"IETF/RFC-4164/RFC-4164.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4169","folder":"IETF/RFC-4169","source":"IETF/RFC-4169/RFC-4169.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4174","folder":"IETF/RFC-4174","source":"IETF/RFC-4174/RFC-4174.txt","version":null},{"body":"IETF","designation":"RFC 4178","folder":"IETF/RFC-4178","source":"IETF/RFC-4178/RFC-4178.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4184","folder":"IETF/RFC-4184","source":"IETF/RFC-4184/RFC-4184.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4188","folder":"IETF/RFC-4188","source":"IETF/RFC-4188/RFC-4188.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4211","folder":"IETF/RFC-4211","source":"IETF/RFC-4211/RFC-4211.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4226","folder":"IETF/RFC-4226","source":"IETF/RFC-4226/RFC-4226.txt","version":null},{"body":"IETF","designation":"RFC 4231","folder":"IETF/RFC-4231","source":"IETF/RFC-4231/RFC-4231.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4242","folder":"IETF/RFC-4242","source":"IETF/RFC-4242/RFC-4242.txt","version":null},{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4245","folder":"IETF/RFC-4245","source":"IETF/RFC-4245/RFC-4245.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4255","folder":"IETF/RFC-4255","source":"IETF/RFC-4255/RFC-4255.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4258","folder":"IETF/RFC-4258","source":"IETF/RFC-4258/RFC-4258.txt","version":null},{"body":"IETF","designation":"RFC 4261","folder":"IETF/RFC-4261","source":"IETF/RFC-4261/RFC-4261.txt","version":null},{"body":"IETF","designation":"RFC 4262","folder":"IETF/RFC-4262","source":"IETF/RFC-4262/RFC-4262.txt","version":null},{"body":"IETF","designation":"RFC 4265","folder":"IETF/RFC-4265","source":"IETF/RFC-4265/RFC-4265.txt","version":null},{"body":"IETF","designation":"RFC 4268","folder":"IETF/RFC-4268","source":"IETF/RFC-4268/RFC-4268.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4272","folder":"IETF/RFC-4272","source":"IETF/RFC-4272/RFC-4272.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4287","folder":"IETF/RFC-4287","source":"IETF/RFC-4287/RFC-4287.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4289","folder":"IETF/RFC-4289","source":"IETF/RFC-4289/RFC-4289.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4311","folder":"IETF/RFC-4311","source":"IETF/RFC-4311/RFC-4311.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4315","folder":"IETF/RFC-4315","source":"IETF/RFC-4315/RFC-4315.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4331","folder":"IETF/RFC-4331","source":"IETF/RFC-4331/RFC-4331.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4345","folder":"IETF/RFC-4345","source":"IETF/RFC-4345/RFC-4345.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4349","folder":"IETF/RFC-4349","source":"IETF/RFC-4349/RFC-4349.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4357","folder":"IETF/RFC-4357","source":"IETF/RFC-4357/RFC-4357.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4361","folder":"IETF/RFC-4361","source":"IETF/RFC-4361/RFC-4361.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4372","folder":"IETF/RFC-4372","source":"IETF/RFC-4372/RFC-4372.txt","version":null},{"body":"IETF","designation":"RFC 4376","folder":"IETF/RFC-4376","source":"IETF/RFC-4376/RFC-4376.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4378","folder":"IETF/RFC-4378","source":"IETF/RFC-4378/RFC-4378.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4383","folder":"IETF/RFC-4383","source":"IETF/RFC-4383/RFC-4383.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4386","folder":"IETF/RFC-4386","source":"IETF/RFC-4386/RFC-4386.txt","version":null},{"body":"IETF","designation":"RFC 4387","folder":"IETF/RFC-4387","source":"IETF/RFC-4387/RFC-4387.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null},{"body":"IETF","designation":"RFC 4401","folder":"IETF/RFC-4401","source":"IETF/RFC-4401/RFC-4401.txt","version":null},{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4419","folder":"IETF/RFC-4419","source":"IETF/RFC-4419/RFC-4419.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4427","folder":"IETF/RFC-4427","source":"IETF/RFC-4427/RFC-4427.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4437","folder":"IETF/RFC-4437","source":"IETF/RFC-4437/RFC-4437.txt","version":null},{"body":"IETF","designation":"RFC 4442","folder":"IETF/RFC-4442","source":"IETF/RFC-4442/RFC-4442.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4449","folder":"IETF/RFC-4449","source":"IETF/RFC-4449/RFC-4449.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4456","folder":"IETF/RFC-4456","source":"IETF/RFC-4456/RFC-4456.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4470","folder":"IETF/RFC-4470","source":"IETF/RFC-4470/RFC-4470.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4478","folder":"IETF/RFC-4478","source":"IETF/RFC-4478/RFC-4478.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4488","folder":"IETF/RFC-4488","source":"IETF/RFC-4488/RFC-4488.txt","version":null},{"body":"IETF","designation":"RFC 4489","folder":"IETF/RFC-4489","source":"IETF/RFC-4489/RFC-4489.txt","version":null},{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4507","folder":"IETF/RFC-4507","source":"IETF/RFC-4507/RFC-4507.txt","version":null},{"body":"IETF","designation":"RFC 4509","folder":"IETF/RFC-4509","source":"IETF/RFC-4509/RFC-4509.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4546","folder":"IETF/RFC-4546","source":"IETF/RFC-4546/RFC-4546.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4563","folder":"IETF/RFC-4563","source":"IETF/RFC-4563/RFC-4563.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null},{"body":"IETF","designation":"RFC 4577","folder":"IETF/RFC-4577","source":"IETF/RFC-4577/RFC-4577.txt","version":null},{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4589","folder":"IETF/RFC-4589","source":"IETF/RFC-4589/RFC-4589.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4592","folder":"IETF/RFC-4592","source":"IETF/RFC-4592/RFC-4592.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4608","folder":"IETF/RFC-4608","source":"IETF/RFC-4608/RFC-4608.txt","version":null},{"body":"IETF","designation":"RFC 4610","folder":"IETF/RFC-4610","source":"IETF/RFC-4610/RFC-4610.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4627","folder":"IETF/RFC-4627","source":"IETF/RFC-4627/RFC-4627.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 4630","folder":"IETF/RFC-4630","source":"IETF/RFC-4630/RFC-4630.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 4636","folder":"IETF/RFC-4636","source":"IETF/RFC-4636/RFC-4636.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4644","folder":"IETF/RFC-4644","source":"IETF/RFC-4644/RFC-4644.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4648","folder":"IETF/RFC-4648","source":"IETF/RFC-4648/RFC-4648.txt","version":null},{"body":"IETF","designation":"RFC 4649","folder":"IETF/RFC-4649","source":"IETF/RFC-4649/RFC-4649.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4657","folder":"IETF/RFC-4657","source":"IETF/RFC-4657/RFC-4657.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4664","folder":"IETF/RFC-4664","source":"IETF/RFC-4664/RFC-4664.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4667","folder":"IETF/RFC-4667","source":"IETF/RFC-4667/RFC-4667.txt","version":null},{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 4674","folder":"IETF/RFC-4674","source":"IETF/RFC-4674/RFC-4674.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4680","folder":"IETF/RFC-4680","source":"IETF/RFC-4680/RFC-4680.txt","version":null},{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4684","folder":"IETF/RFC-4684","source":"IETF/RFC-4684/RFC-4684.txt","version":null},{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 4697","folder":"IETF/RFC-4697","source":"IETF/RFC-4697/RFC-4697.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 4704","folder":"IETF/RFC-4704","source":"IETF/RFC-4704/RFC-4704.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4711","folder":"IETF/RFC-4711","source":"IETF/RFC-4711/RFC-4711.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4719","folder":"IETF/RFC-4719","source":"IETF/RFC-4719/RFC-4719.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4724","folder":"IETF/RFC-4724","source":"IETF/RFC-4724/RFC-4724.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4731","folder":"IETF/RFC-4731","source":"IETF/RFC-4731/RFC-4731.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 4735","folder":"IETF/RFC-4735","source":"IETF/RFC-4735/RFC-4735.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4739","folder":"IETF/RFC-4739","source":"IETF/RFC-4739/RFC-4739.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 4754","folder":"IETF/RFC-4754","source":"IETF/RFC-4754/RFC-4754.txt","version":null},{"body":"IETF","designation":"RFC 4756","folder":"IETF/RFC-4756","source":"IETF/RFC-4756/RFC-4756.txt","version":null},{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null},{"body":"IETF","designation":"RFC 4759","folder":"IETF/RFC-4759","source":"IETF/RFC-4759/RFC-4759.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4763","folder":"IETF/RFC-4763","source":"IETF/RFC-4763/RFC-4763.txt","version":null},{"body":"IETF","designation":"RFC 4764","folder":"IETF/RFC-4764","source":"IETF/RFC-4764/RFC-4764.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4766","folder":"IETF/RFC-4766","source":"IETF/RFC-4766/RFC-4766.txt","version":null},{"body":"IETF","designation":"RFC 4771","folder":"IETF/RFC-4771","source":"IETF/RFC-4771/RFC-4771.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4781","folder":"IETF/RFC-4781","source":"IETF/RFC-4781/RFC-4781.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4785","folder":"IETF/RFC-4785","source":"IETF/RFC-4785/RFC-4785.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4789","folder":"IETF/RFC-4789","source":"IETF/RFC-4789/RFC-4789.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 4806","folder":"IETF/RFC-4806","source":"IETF/RFC-4806/RFC-4806.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4814","folder":"IETF/RFC-4814","source":"IETF/RFC-4814/RFC-4814.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4820","folder":"IETF/RFC-4820","source":"IETF/RFC-4820/RFC-4820.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 4850","folder":"IETF/RFC-4850","source":"IETF/RFC-4850/RFC-4850.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4853","folder":"IETF/RFC-4853","source":"IETF/RFC-4853/RFC-4853.txt","version":null},{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 4856","folder":"IETF/RFC-4856","source":"IETF/RFC-4856/RFC-4856.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4863","folder":"IETF/RFC-4863","source":"IETF/RFC-4863/RFC-4863.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 4870","folder":"IETF/RFC-4870","source":"IETF/RFC-4870/RFC-4870.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4893","folder":"IETF/RFC-4893","source":"IETF/RFC-4893/RFC-4893.txt","version":null},{"body":"IETF","designation":"RFC 4895","folder":"IETF/RFC-4895","source":"IETF/RFC-4895/RFC-4895.txt","version":null},{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4904","folder":"IETF/RFC-4904","source":"IETF/RFC-4904/RFC-4904.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4909","folder":"IETF/RFC-4909","source":"IETF/RFC-4909/RFC-4909.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4946","folder":"IETF/RFC-4946","source":"IETF/RFC-4946/RFC-4946.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4955","folder":"IETF/RFC-4955","source":"IETF/RFC-4955/RFC-4955.txt","version":null},{"body":"IETF","designation":"RFC 4956","folder":"IETF/RFC-4956","source":"IETF/RFC-4956/RFC-4956.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4967","folder":"IETF/RFC-4967","source":"IETF/RFC-4967/RFC-4967.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 4985","folder":"IETF/RFC-4985","source":"IETF/RFC-4985/RFC-4985.txt","version":null},{"body":"IETF","designation":"RFC 4986","folder":"IETF/RFC-4986","source":"IETF/RFC-4986/RFC-4986.txt","version":null},{"body":"IETF","designation":"RFC 4991","folder":"IETF/RFC-4991","source":"IETF/RFC-4991/RFC-4991.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 4994","folder":"IETF/RFC-4994","source":"IETF/RFC-4994/RFC-4994.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5001","folder":"IETF/RFC-5001","source":"IETF/RFC-5001/RFC-5001.txt","version":null},{"body":"IETF","designation":"RFC 5003","folder":"IETF/RFC-5003","source":"IETF/RFC-5003/RFC-5003.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5006","folder":"IETF/RFC-5006","source":"IETF/RFC-5006/RFC-5006.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null},{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5016","folder":"IETF/RFC-5016","source":"IETF/RFC-5016/RFC-5016.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 5063","folder":"IETF/RFC-5063","source":"IETF/RFC-5063/RFC-5063.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5069","folder":"IETF/RFC-5069","source":"IETF/RFC-5069/RFC-5069.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null},{"body":"IETF","designation":"RFC 5077","folder":"IETF/RFC-5077","source":"IETF/RFC-5077/RFC-5077.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5081","folder":"IETF/RFC-5081","source":"IETF/RFC-5081/RFC-5081.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5083","folder":"IETF/RFC-5083","source":"IETF/RFC-5083/RFC-5083.txt","version":null},{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5091","folder":"IETF/RFC-5091","source":"IETF/RFC-5091/RFC-5091.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5094","folder":"IETF/RFC-5094","source":"IETF/RFC-5094/RFC-5094.txt","version":null},{"body":"IETF","designation":"RFC 5095","folder":"IETF/RFC-5095","source":"IETF/RFC-5095/RFC-5095.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5103","folder":"IETF/RFC-5103","source":"IETF/RFC-5103/RFC-5103.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5106","folder":"IETF/RFC-5106","source":"IETF/RFC-5106/RFC-5106.txt","version":null},{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5111","folder":"IETF/RFC-5111","source":"IETF/RFC-5111/RFC-5111.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5135","folder":"IETF/RFC-5135","source":"IETF/RFC-5135/RFC-5135.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5142","folder":"IETF/RFC-5142","source":"IETF/RFC-5142/RFC-5142.txt","version":null},{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5148","folder":"IETF/RFC-5148","source":"IETF/RFC-5148/RFC-5148.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5155","folder":"IETF/RFC-5155","source":"IETF/RFC-5155/RFC-5155.txt","version":null},{"body":"IETF","designation":"RFC 5159","folder":"IETF/RFC-5159","source":"IETF/RFC-5159/RFC-5159.txt","version":null},{"body":"IETF","designation":"RFC 5161","folder":"IETF/RFC-5161","source":"IETF/RFC-5161/RFC-5161.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5175","folder":"IETF/RFC-5175","source":"IETF/RFC-5175/RFC-5175.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5183","folder":"IETF/RFC-5183","source":"IETF/RFC-5183/RFC-5183.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5192","folder":"IETF/RFC-5192","source":"IETF/RFC-5192/RFC-5192.txt","version":null},{"body":"IETF","designation":"RFC 5193","folder":"IETF/RFC-5193","source":"IETF/RFC-5193/RFC-5193.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5232","folder":"IETF/RFC-5232","source":"IETF/RFC-5232/RFC-5232.txt","version":null},{"body":"IETF","designation":"RFC 5233","folder":"IETF/RFC-5233","source":"IETF/RFC-5233/RFC-5233.txt","version":null},{"body":"IETF","designation":"RFC 5235","folder":"IETF/RFC-5235","source":"IETF/RFC-5235/RFC-5235.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5277","folder":"IETF/RFC-5277","source":"IETF/RFC-5277/RFC-5277.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5281","folder":"IETF/RFC-5281","source":"IETF/RFC-5281/RFC-5281.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5295","folder":"IETF/RFC-5295","source":"IETF/RFC-5295/RFC-5295.txt","version":null},{"body":"IETF","designation":"RFC 5296","folder":"IETF/RFC-5296","source":"IETF/RFC-5296/RFC-5296.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5301","folder":"IETF/RFC-5301","source":"IETF/RFC-5301/RFC-5301.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5331","folder":"IETF/RFC-5331","source":"IETF/RFC-5331/RFC-5331.txt","version":null},{"body":"IETF","designation":"RFC 5332","folder":"IETF/RFC-5332","source":"IETF/RFC-5332/RFC-5332.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5343","folder":"IETF/RFC-5343","source":"IETF/RFC-5343/RFC-5343.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5358","folder":"IETF/RFC-5358","source":"IETF/RFC-5358/RFC-5358.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5384","folder":"IETF/RFC-5384","source":"IETF/RFC-5384/RFC-5384.txt","version":null},{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5397","folder":"IETF/RFC-5397","source":"IETF/RFC-5397/RFC-5397.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5403","folder":"IETF/RFC-5403","source":"IETF/RFC-5403/RFC-5403.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5418","folder":"IETF/RFC-5418","source":"IETF/RFC-5418/RFC-5418.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5427","folder":"IETF/RFC-5427","source":"IETF/RFC-5427/RFC-5427.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5433","folder":"IETF/RFC-5433","source":"IETF/RFC-5433/RFC-5433.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5444","folder":"IETF/RFC-5444","source":"IETF/RFC-5444/RFC-5444.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5448","folder":"IETF/RFC-5448","source":"IETF/RFC-5448/RFC-5448.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5450","folder":"IETF/RFC-5450","source":"IETF/RFC-5450/RFC-5450.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5452","folder":"IETF/RFC-5452","source":"IETF/RFC-5452/RFC-5452.txt","version":null},{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5469","folder":"IETF/RFC-5469","source":"IETF/RFC-5469/RFC-5469.txt","version":null},{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5476","folder":"IETF/RFC-5476","source":"IETF/RFC-5476/RFC-5476.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null},{"body":"IETF","designation":"RFC 5496","folder":"IETF/RFC-5496","source":"IETF/RFC-5496/RFC-5496.txt","version":null},{"body":"IETF","designation":"RFC 5497","folder":"IETF/RFC-5497","source":"IETF/RFC-5497/RFC-5497.txt","version":null},{"body":"IETF","designation":"RFC 5498","folder":"IETF/RFC-5498","source":"IETF/RFC-5498/RFC-5498.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5546","folder":"IETF/RFC-5546","source":"IETF/RFC-5546/RFC-5546.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5548","folder":"IETF/RFC-5548","source":"IETF/RFC-5548/RFC-5548.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5554","folder":"IETF/RFC-5554","source":"IETF/RFC-5554/RFC-5554.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5635","folder":"IETF/RFC-5635","source":"IETF/RFC-5635/RFC-5635.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5640","folder":"IETF/RFC-5640","source":"IETF/RFC-5640/RFC-5640.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5662","folder":"IETF/RFC-5662","source":"IETF/RFC-5662/RFC-5662.txt","version":null},{"body":"IETF","designation":"RFC 5663","folder":"IETF/RFC-5663","source":"IETF/RFC-5663/RFC-5663.txt","version":null},{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 5668","folder":"IETF/RFC-5668","source":"IETF/RFC-5668/RFC-5668.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5672","folder":"IETF/RFC-5672","source":"IETF/RFC-5672/RFC-5672.txt","version":null},{"body":"IETF","designation":"RFC 5673","folder":"IETF/RFC-5673","source":"IETF/RFC-5673/RFC-5673.txt","version":null},{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5705","folder":"IETF/RFC-5705","source":"IETF/RFC-5705/RFC-5705.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5709","folder":"IETF/RFC-5709","source":"IETF/RFC-5709/RFC-5709.txt","version":null},{"body":"IETF","designation":"RFC 5713","folder":"IETF/RFC-5713","source":"IETF/RFC-5713/RFC-5713.txt","version":null},{"body":"IETF","designation":"RFC 5717","folder":"IETF/RFC-5717","source":"IETF/RFC-5717/RFC-5717.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5719","folder":"IETF/RFC-5719","source":"IETF/RFC-5719/RFC-5719.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5722","folder":"IETF/RFC-5722","source":"IETF/RFC-5722/RFC-5722.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 5729","folder":"IETF/RFC-5729","source":"IETF/RFC-5729/RFC-5729.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5746","folder":"IETF/RFC-5746","source":"IETF/RFC-5746/RFC-5746.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5756","folder":"IETF/RFC-5756","source":"IETF/RFC-5756/RFC-5756.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5759","folder":"IETF/RFC-5759","source":"IETF/RFC-5759/RFC-5759.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5782","folder":"IETF/RFC-5782","source":"IETF/RFC-5782/RFC-5782.txt","version":null},{"body":"IETF","designation":"RFC 5785","folder":"IETF/RFC-5785","source":"IETF/RFC-5785/RFC-5785.txt","version":null},{"body":"IETF","designation":"RFC 5788","folder":"IETF/RFC-5788","source":"IETF/RFC-5788/RFC-5788.txt","version":null},{"body":"IETF","designation":"RFC 5789","folder":"IETF/RFC-5789","source":"IETF/RFC-5789/RFC-5789.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5798","folder":"IETF/RFC-5798","source":"IETF/RFC-5798/RFC-5798.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5808","folder":"IETF/RFC-5808","source":"IETF/RFC-5808/RFC-5808.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 5825","folder":"IETF/RFC-5825","source":"IETF/RFC-5825/RFC-5825.txt","version":null},{"body":"IETF","designation":"RFC 5826","folder":"IETF/RFC-5826","source":"IETF/RFC-5826/RFC-5826.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5833","folder":"IETF/RFC-5833","source":"IETF/RFC-5833/RFC-5833.txt","version":null},{"body":"IETF","designation":"RFC 5834","folder":"IETF/RFC-5834","source":"IETF/RFC-5834/RFC-5834.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5861","folder":"IETF/RFC-5861","source":"IETF/RFC-5861/RFC-5861.txt","version":null},{"body":"IETF","designation":"RFC 5864","folder":"IETF/RFC-5864","source":"IETF/RFC-5864/RFC-5864.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5867","folder":"IETF/RFC-5867","source":"IETF/RFC-5867/RFC-5867.txt","version":null},{"body":"IETF","designation":"RFC 5869","folder":"IETF/RFC-5869","source":"IETF/RFC-5869/RFC-5869.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5880","folder":"IETF/RFC-5880","source":"IETF/RFC-5880/RFC-5880.txt","version":null},{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5908","folder":"IETF/RFC-5908","source":"IETF/RFC-5908/RFC-5908.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 5932","folder":"IETF/RFC-5932","source":"IETF/RFC-5932/RFC-5932.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5964","folder":"IETF/RFC-5964","source":"IETF/RFC-5964/RFC-5964.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5983","folder":"IETF/RFC-5983","source":"IETF/RFC-5983/RFC-5983.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6019","folder":"IETF/RFC-6019","source":"IETF/RFC-6019/RFC-6019.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6034","folder":"IETF/RFC-6034","source":"IETF/RFC-6034/RFC-6034.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6059","folder":"IETF/RFC-6059","source":"IETF/RFC-6059/RFC-6059.txt","version":null},{"body":"IETF","designation":"RFC 6062","folder":"IETF/RFC-6062","source":"IETF/RFC-6062/RFC-6062.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6081","folder":"IETF/RFC-6081","source":"IETF/RFC-6081/RFC-6081.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6085","folder":"IETF/RFC-6085","source":"IETF/RFC-6085/RFC-6085.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6106","folder":"IETF/RFC-6106","source":"IETF/RFC-6106/RFC-6106.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6147","folder":"IETF/RFC-6147","source":"IETF/RFC-6147/RFC-6147.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6156","folder":"IETF/RFC-6156","source":"IETF/RFC-6156/RFC-6156.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6176","folder":"IETF/RFC-6176","source":"IETF/RFC-6176/RFC-6176.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6186","folder":"IETF/RFC-6186","source":"IETF/RFC-6186/RFC-6186.txt","version":null},{"body":"IETF","designation":"RFC 6188","folder":"IETF/RFC-6188","source":"IETF/RFC-6188/RFC-6188.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6206","folder":"IETF/RFC-6206","source":"IETF/RFC-6206/RFC-6206.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6212","folder":"IETF/RFC-6212","source":"IETF/RFC-6212/RFC-6212.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6221","folder":"IETF/RFC-6221","source":"IETF/RFC-6221/RFC-6221.txt","version":null},{"body":"IETF","designation":"RFC 6222","folder":"IETF/RFC-6222","source":"IETF/RFC-6222/RFC-6222.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6243","folder":"IETF/RFC-6243","source":"IETF/RFC-6243/RFC-6243.txt","version":null},{"body":"IETF","designation":"RFC 6245","folder":"IETF/RFC-6245","source":"IETF/RFC-6245/RFC-6245.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6277","folder":"IETF/RFC-6277","source":"IETF/RFC-6277/RFC-6277.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6302","folder":"IETF/RFC-6302","source":"IETF/RFC-6302/RFC-6302.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6334","folder":"IETF/RFC-6334","source":"IETF/RFC-6334/RFC-6334.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6351","folder":"IETF/RFC-6351","source":"IETF/RFC-6351/RFC-6351.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6368","folder":"IETF/RFC-6368","source":"IETF/RFC-6368/RFC-6368.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 6386","folder":"IETF/RFC-6386","source":"IETF/RFC-6386/RFC-6386.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6431","folder":"IETF/RFC-6431","source":"IETF/RFC-6431/RFC-6431.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6549","folder":"IETF/RFC-6549","source":"IETF/RFC-6549/RFC-6549.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6552","folder":"IETF/RFC-6552","source":"IETF/RFC-6552/RFC-6552.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6562","folder":"IETF/RFC-6562","source":"IETF/RFC-6562/RFC-6562.txt","version":null},{"body":"IETF","designation":"RFC 6564","folder":"IETF/RFC-6564","source":"IETF/RFC-6564/RFC-6564.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6582","folder":"IETF/RFC-6582","source":"IETF/RFC-6582/RFC-6582.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6585","folder":"IETF/RFC-6585","source":"IETF/RFC-6585/RFC-6585.txt","version":null},{"body":"IETF","designation":"RFC 6590","folder":"IETF/RFC-6590","source":"IETF/RFC-6590/RFC-6590.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6603","folder":"IETF/RFC-6603","source":"IETF/RFC-6603/RFC-6603.txt","version":null},{"body":"IETF","designation":"RFC 6604","folder":"IETF/RFC-6604","source":"IETF/RFC-6604/RFC-6604.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6619","folder":"IETF/RFC-6619","source":"IETF/RFC-6619/RFC-6619.txt","version":null},{"body":"IETF","designation":"RFC 6620","folder":"IETF/RFC-6620","source":"IETF/RFC-6620/RFC-6620.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6630","folder":"IETF/RFC-6630","source":"IETF/RFC-6630/RFC-6630.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6644","folder":"IETF/RFC-6644","source":"IETF/RFC-6644/RFC-6644.txt","version":null},{"body":"IETF","designation":"RFC 6647","folder":"IETF/RFC-6647","source":"IETF/RFC-6647/RFC-6647.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6672","folder":"IETF/RFC-6672","source":"IETF/RFC-6672/RFC-6672.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6737","folder":"IETF/RFC-6737","source":"IETF/RFC-6737/RFC-6737.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6761","folder":"IETF/RFC-6761","source":"IETF/RFC-6761/RFC-6761.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6776","folder":"IETF/RFC-6776","source":"IETF/RFC-6776/RFC-6776.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 6791","folder":"IETF/RFC-6791","source":"IETF/RFC-6791/RFC-6791.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6807","folder":"IETF/RFC-6807","source":"IETF/RFC-6807/RFC-6807.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6834","folder":"IETF/RFC-6834","source":"IETF/RFC-6834/RFC-6834.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6862","folder":"IETF/RFC-6862","source":"IETF/RFC-6862/RFC-6862.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6891","folder":"IETF/RFC-6891","source":"IETF/RFC-6891/RFC-6891.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6928","folder":"IETF/RFC-6928","source":"IETF/RFC-6928/RFC-6928.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 6935","folder":"IETF/RFC-6935","source":"IETF/RFC-6935/RFC-6935.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6946","folder":"IETF/RFC-6946","source":"IETF/RFC-6946/RFC-6946.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 6962","folder":"IETF/RFC-6962","source":"IETF/RFC-6962/RFC-6962.txt","version":null},{"body":"IETF","designation":"RFC 6963","folder":"IETF/RFC-6963","source":"IETF/RFC-6963/RFC-6963.txt","version":null},{"body":"IETF","designation":"RFC 6970","folder":"IETF/RFC-6970","source":"IETF/RFC-6970/RFC-6970.txt","version":null},{"body":"IETF","designation":"RFC 6975","folder":"IETF/RFC-6975","source":"IETF/RFC-6975/RFC-6975.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 6985","folder":"IETF/RFC-6985","source":"IETF/RFC-6985/RFC-6985.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7043","folder":"IETF/RFC-7043","source":"IETF/RFC-7043/RFC-7043.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7050","folder":"IETF/RFC-7050","source":"IETF/RFC-7050/RFC-7050.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7083","folder":"IETF/RFC-7083","source":"IETF/RFC-7083/RFC-7083.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7164","folder":"IETF/RFC-7164","source":"IETF/RFC-7164/RFC-7164.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7179","folder":"IETF/RFC-7179","source":"IETF/RFC-7179/RFC-7179.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7238","folder":"IETF/RFC-7238","source":"IETF/RFC-7238/RFC-7238.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7283","folder":"IETF/RFC-7283","source":"IETF/RFC-7283/RFC-7283.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 7335","folder":"IETF/RFC-7335","source":"IETF/RFC-7335/RFC-7335.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7366","folder":"IETF/RFC-7366","source":"IETF/RFC-7366/RFC-7366.txt","version":null},{"body":"IETF","designation":"RFC 7384","folder":"IETF/RFC-7384","source":"IETF/RFC-7384/RFC-7384.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7400","folder":"IETF/RFC-7400","source":"IETF/RFC-7400/RFC-7400.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7465","folder":"IETF/RFC-7465","source":"IETF/RFC-7465/RFC-7465.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7488","folder":"IETF/RFC-7488","source":"IETF/RFC-7488/RFC-7488.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 7507","folder":"IETF/RFC-7507","source":"IETF/RFC-7507/RFC-7507.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null},{"body":"IETF","designation":"RFC 7539","folder":"IETF/RFC-7539","source":"IETF/RFC-7539/RFC-7539.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7578","folder":"IETF/RFC-7578","source":"IETF/RFC-7578/RFC-7578.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7637","folder":"IETF/RFC-7637","source":"IETF/RFC-7637/RFC-7637.txt","version":null},{"body":"IETF","designation":"RFC 7638","folder":"IETF/RFC-7638","source":"IETF/RFC-7638/RFC-7638.txt","version":null},{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7685","folder":"IETF/RFC-7685","source":"IETF/RFC-7685/RFC-7685.txt","version":null},{"body":"IETF","designation":"RFC 7693","folder":"IETF/RFC-7693","source":"IETF/RFC-7693/RFC-7693.txt","version":null},{"body":"IETF","designation":"RFC 7694","folder":"IETF/RFC-7694","source":"IETF/RFC-7694/RFC-7694.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7706","folder":"IETF/RFC-7706","source":"IETF/RFC-7706/RFC-7706.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 7748","folder":"IETF/RFC-7748","source":"IETF/RFC-7748/RFC-7748.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 7765","folder":"IETF/RFC-7765","source":"IETF/RFC-7765/RFC-7765.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7822","folder":"IETF/RFC-7822","source":"IETF/RFC-7822/RFC-7822.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7828","folder":"IETF/RFC-7828","source":"IETF/RFC-7828/RFC-7828.txt","version":null},{"body":"IETF","designation":"RFC 7830","folder":"IETF/RFC-7830","source":"IETF/RFC-7830/RFC-7830.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null},{"body":"IETF","designation":"RFC 7873","folder":"IETF/RFC-7873","source":"IETF/RFC-7873/RFC-7873.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7959","folder":"IETF/RFC-7959","source":"IETF/RFC-7959/RFC-7959.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 7967","folder":"IETF/RFC-7967","source":"IETF/RFC-7967/RFC-7967.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8020","folder":"IETF/RFC-8020","source":"IETF/RFC-8020/RFC-8020.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8027","folder":"IETF/RFC-8027","source":"IETF/RFC-8027/RFC-8027.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8032","folder":"IETF/RFC-8032","source":"IETF/RFC-8032/RFC-8032.txt","version":null},{"body":"IETF","designation":"RFC 8033","folder":"IETF/RFC-8033","source":"IETF/RFC-8033/RFC-8033.txt","version":null},{"body":"IETF","designation":"RFC 8035","folder":"IETF/RFC-8035","source":"IETF/RFC-8035/RFC-8035.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8078","folder":"IETF/RFC-8078","source":"IETF/RFC-8078/RFC-8078.txt","version":null},{"body":"IETF","designation":"RFC 8081","folder":"IETF/RFC-8081","source":"IETF/RFC-8081/RFC-8081.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8109","folder":"IETF/RFC-8109","source":"IETF/RFC-8109/RFC-8109.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8174","folder":"IETF/RFC-8174","source":"IETF/RFC-8174/RFC-8174.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8235","folder":"IETF/RFC-8235","source":"IETF/RFC-8235/RFC-8235.txt","version":null},{"body":"IETF","designation":"RFC 8246","folder":"IETF/RFC-8246","source":"IETF/RFC-8246/RFC-8246.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8297","folder":"IETF/RFC-8297","source":"IETF/RFC-8297/RFC-8297.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8391","folder":"IETF/RFC-8391","source":"IETF/RFC-8391/RFC-8391.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9021","folder":"IETF/RFC-9021","source":"IETF/RFC-9021/RFC-9021.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9106","folder":"IETF/RFC-9106","source":"IETF/RFC-9106/RFC-9106.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 2119 Network Working Group S. Bradner\nRequest for Comments: 2119 Harvard University\nBCP: 14 March 1997\nCategory: Best Current Practice\n\n Key words for use in RFCs to Indicate Requirement Levels\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n In many standards track documents several words are used to signify\n the requirements in the specification. These words are often\n capitalized. This document defines these words as they should be\n interpreted in IETF documents. Authors who follow these guidelines\n should incorporate this phrase near the beginning of their document:\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL\n NOT\", \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and\n \"OPTIONAL\" in this document are t 2119 key nested-reference unchanged"},{"id":"IETF RFC 2301","type":"specification","body":"IETF","designation":"RFC 2301","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2301.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2301.txt","https://www.rfc-editor.org/rfc/rfc2301.pdf"],"folder":"IETF/RFC-2301","files":{"txt":{"path":"standards/IETF/RFC-2301/RFC-2301.txt","sha256":"37a2dbebb8bbfce7a265ab4507539096066a977931ca25872c5bf893f6870304"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the TIFF (Tag Image File Format)\n representation of image data specified by the ITU-T Recommendations\n for black-and-white and color facsimile. This file format\n specification is commonly known as TIFF-FX. It formally defines\n minimal, extended and lossless JBIG modes (Profiles S, F, J) for\n black-and-white fax, and base JPEG, lossless JBIG and Mixed Raster\n Content modes (Profiles C, L, M) for color and grayscale fax. These\n modes or profiles correspond to the content of the applicable ITU-T\n Recommendations. Files formatted according to this specification use\n the image/tiff MIME Content Type.\n\nMcIntyre, et. al. Standards Track [Page 1]\n\f\nRFC 2301 File Format for Internet Fax March 1998","scope_keywords":["2301","presentation","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2302","folder":"IETF/RFC-2302","source":"IETF/RFC-2302/RFC-2302.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3250","folder":"IETF/RFC-3250","source":"IETF/RFC-3250/RFC-3250.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3949","folder":"IETF/RFC-3949","source":"IETF/RFC-3949/RFC-3949.txt","version":null}],"search_text":"IETF RFC 2301 This document describes the TIFF (Tag Image File Format)\n representation of image data specified by the ITU-T Recommendations\n for black-and-white and color facsimile. This file format\n specification is commonly known as TIFF-FX. It formally defines\n minimal, extended and lossless JBIG modes (Profiles S, F, J) for\n black-and-white fax, and base JPEG, lossless JBIG and Mixed Raster\n Content modes (Profiles C, L, M) for color and grayscale fax. These\n modes or profiles correspond to the content of the applicable ITU-T\n Recommendations. Files formatted according to this specification use\n the image/tiff MIME Content Type.\n\nMcIntyre, et. al. Standards Track [Page 1]\n\f\nRFC 2301 File Format for Internet Fax March 1998 2301 presentation profile profiles nested-reference unchanged"},{"id":"IETF RFC 2312","type":"specification","body":"IETF","designation":"RFC 2312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2312.txt","https://www.rfc-editor.org/rfc/rfc2312.pdf"],"folder":"IETF/RFC-2312","files":{"txt":{"path":"standards/IETF/RFC-2312/RFC-2312.txt","sha256":"f6afedd7508a2fec563bcc5b0376a02f25fa56657349644ade073a0d363d48c0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Dusse\nRequest for Comments: 2312 RSA Data Security\nCategory: Informational P. Hoffman\n Internet Mail Consortium\n B. Ramsdell\n Worldtalk\n J. Weinstein\n Netscape\n March 1998\n\n S/MIME Version 2 Certificate Handling\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Overview\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions), described in\n [SMIME-MSG], provides a method to send and receive secure MIME\n messages. In order to validate the keys of a message sent to it, an\n S/MIME agent needs to certify that the key is valid. This memo\n describes the mechanisms S/MIME uses to create and validate keys\n using certificates.\n\n This specification is compatible","scope_keywords":["2312","algorithm","certificate","certificates","crl","encryption","issuer","key","keys","management","path","profile","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2312 Network Working Group S. Dusse\nRequest for Comments: 2312 RSA Data Security\nCategory: Informational P. Hoffman\n Internet Mail Consortium\n B. Ramsdell\n Worldtalk\n J. Weinstein\n Netscape\n March 1998\n\n S/MIME Version 2 Certificate Handling\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Overview\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions), described in\n [SMIME-MSG], provides a method to send and receive secure MIME\n messages. In order to validate the keys of a message sent to it, an\n S/MIME agent needs to certify that the key is valid. This memo\n describes the mechanisms S/MIME uses to create and validate keys\n using certificates.\n\n This specification is compatible 2312 algorithm certificate certificates crl encryption issuer key keys management path profile revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 2389","type":"specification","body":"IETF","designation":"RFC 2389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2389.txt","https://www.rfc-editor.org/rfc/rfc2389.pdf"],"folder":"IETF/RFC-2389","files":{"txt":{"path":"standards/IETF/RFC-2389/RFC-2389.txt","sha256":"20a576b8221f418f05c1c0879e9c96b6cccc1601fd5913e8a4dd69741eae54d8"}},"tags":["nested-reference","unchanged"],"summary":"The File Transfer Protocol is, from time to time, extended with new\n commands, or facilities. Implementations of the FTP protocol cannot\n be assumed to all immediately implement all newly defined mechanisms.\n This document provides a mechanism by which clients of the FTP\n protocol can discover which new features are supported by a\n particular FTP server.\n\nHethmon & Elz Standards Track [Page 1]\n\f\nRFC 2389 Feature negotiation mechanism August 1998","scope_keywords":["2389","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null}],"search_text":"IETF RFC 2389 The File Transfer Protocol is, from time to time, extended with new\n commands, or facilities. Implementations of the FTP protocol cannot\n be assumed to all immediately implement all newly defined mechanisms.\n This document provides a mechanism by which clients of the FTP\n protocol can discover which new features are supported by a\n particular FTP server.\n\nHethmon & Elz Standards Track [Page 1]\n\f\nRFC 2389 Feature negotiation mechanism August 1998 2389 crl nested-reference unchanged"},{"id":"IETF RFC 2407","type":"specification","body":"IETF","designation":"RFC 2407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2407.txt","https://www.rfc-editor.org/rfc/rfc2407.pdf"],"folder":"IETF/RFC-2407","files":{"txt":{"path":"standards/IETF/RFC-2407/RFC-2407.txt","sha256":"40fe747803759b4ca0bfb1235f2307836742cdcfc55e40c61af913783473419f"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Security Association and Key Management Protocol\n (ISAKMP) defines a framework for security association management and\n cryptographic key establishment for the Internet. This framework\n consists of defined exchanges, payloads, and processing guidelines\n that occur within a given Domain of Interpretation (DOI). This\n document defines the Internet IP Security DOI (IPSEC DOI), which\n instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate\n security associations.\n\n For a list of changes since the previous version of the IPSEC DOI,\n please see Section 7.\n\nPiper Standards Track [Page 1]\n\f\nRFC 2407 IP Security Domain of Interpretation November 1998\n\n2. Introduction\n\n Within ISAKMP, a Domain of Interpretation is used to group related\n protocols using ISAKMP to negotiate security associations. Security\n protocols sharing a DOI choose security protocol and cryptographic\n ","scope_keywords":["2407","algorithm","attribute","attributes","authentication","identification","key","management","policies","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2394","folder":"IETF/RFC-2394","source":"IETF/RFC-2394/RFC-2394.txt","version":null},{"body":"IETF","designation":"RFC 2395","folder":"IETF/RFC-2395","source":"IETF/RFC-2395/RFC-2395.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2408","folder":"IETF/RFC-2408","source":"IETF/RFC-2408/RFC-2408.txt","version":null},{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2411","folder":"IETF/RFC-2411","source":"IETF/RFC-2411/RFC-2411.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2709","folder":"IETF/RFC-2709","source":"IETF/RFC-2709/RFC-2709.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3051","folder":"IETF/RFC-3051","source":"IETF/RFC-3051/RFC-3051.txt","version":null},{"body":"IETF","designation":"RFC 3104","folder":"IETF/RFC-3104","source":"IETF/RFC-3104/RFC-3104.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3193","folder":"IETF/RFC-3193","source":"IETF/RFC-3193/RFC-3193.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3547","folder":"IETF/RFC-3547","source":"IETF/RFC-3547/RFC-3547.txt","version":null},{"body":"IETF","designation":"RFC 3554","folder":"IETF/RFC-3554","source":"IETF/RFC-3554/RFC-3554.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3602","folder":"IETF/RFC-3602","source":"IETF/RFC-3602/RFC-3602.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3686","folder":"IETF/RFC-3686","source":"IETF/RFC-3686/RFC-3686.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 2407 The Internet Security Association and Key Management Protocol\n (ISAKMP) defines a framework for security association management and\n cryptographic key establishment for the Internet. This framework\n consists of defined exchanges, payloads, and processing guidelines\n that occur within a given Domain of Interpretation (DOI). This\n document defines the Internet IP Security DOI (IPSEC DOI), which\n instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate\n security associations.\n\n For a list of changes since the previous version of the IPSEC DOI,\n please see Section 7.\n\nPiper Standards Track [Page 1]\n\f\nRFC 2407 IP Security Domain of Interpretation November 1998\n\n2. Introduction\n\n Within ISAKMP, a Domain of Interpretation is used to group related\n protocols using ISAKMP to negotiate security associations. Security\n protocols sharing a DOI choose security protocol and cryptographic\n  2407 algorithm attribute attributes authentication identification key management policies policy registered nested-reference unchanged"},{"id":"IETF RFC 2446","type":"specification","body":"IETF","designation":"RFC 2446","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2446.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2446.txt","https://www.rfc-editor.org/rfc/rfc2446.pdf"],"folder":"IETF/RFC-2446","files":{"txt":{"path":"standards/IETF/RFC-2446/RFC-2446.txt","sha256":"7e8110ce4fb50b79deb4dd5a8c5be26aa4b6c077788fe148e41f0aef0f536c71"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how calendaring systems use iCalendar objects\n to interoperate with other calendar systems. It does so in a general\n way so as to allow multiple methods of communication between systems.\n Subsequent documents specify interoperable methods of communications\n between systems that use this protocol.\n\n The document outlines a model for calendar exchange that defines both\n static and dynamic event, to-do, journal and free/busy objects.\n Static objects are used to transmit information from one entity to\n another without the expectation of continuity or referential\n integrity with the original item. Dynamic objects are a superset of\n static objects and will gracefully degrade to their static\n counterparts for clients that only support static objects.\n\n This document specifies an Internet protocol based on the iCalendar\n object specification that provides scheduling inter","scope_keywords":["2446"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 5546","folder":"IETF/RFC-5546","source":"IETF/RFC-5546/RFC-5546.txt","version":null}],"search_text":"IETF RFC 2446 This document specifies how calendaring systems use iCalendar objects\n to interoperate with other calendar systems. It does so in a general\n way so as to allow multiple methods of communication between systems.\n Subsequent documents specify interoperable methods of communications\n between systems that use this protocol.\n\n The document outlines a model for calendar exchange that defines both\n static and dynamic event, to-do, journal and free/busy objects.\n Static objects are used to transmit information from one entity to\n another without the expectation of continuity or referential\n integrity with the original item. Dynamic objects are a superset of\n static objects and will gracefully degrade to their static\n counterparts for clients that only support static objects.\n\n This document specifies an Internet protocol based on the iCalendar\n object specification that provides scheduling inter 2446 nested-reference unchanged"},{"id":"IETF RFC 2531","type":"specification","body":"IETF","designation":"RFC 2531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2531.txt","https://www.rfc-editor.org/rfc/rfc2531.pdf"],"folder":"IETF/RFC-2531","files":{"txt":{"path":"standards/IETF/RFC-2531/RFC-2531.txt","sha256":"3560e470fd0478b9c66929469bd2092ba16da9f0dfcf0ddca732705169b3c657"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a content feature schema that is a profile of\n the media feature registration mechanisms [1,2,3] for use in\n performing capability identification between extended Internet fax\n systems [5].\n\n This document does not describe any specific mechanisms for\n communicating capability information, but does presume that any such\n mechanisms will transfer textual values. It specifies a textual\n format to be used for describing Internet fax capability information.\n\nKlyne & McIntyre Standards Track [Page 1]\n\f\nRFC 2531 Content Feature Schema for Internet Fax March 1999","scope_keywords":["2531","identification","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null}],"search_text":"IETF RFC 2531 This document defines a content feature schema that is a profile of\n the media feature registration mechanisms [1,2,3] for use in\n performing capability identification between extended Internet fax\n systems [5].\n\n This document does not describe any specific mechanisms for\n communicating capability information, but does presume that any such\n mechanisms will transfer textual values. It specifies a textual\n format to be used for describing Internet fax capability information.\n\nKlyne & McIntyre Standards Track [Page 1]\n\f\nRFC 2531 Content Feature Schema for Internet Fax March 1999 2531 identification profile registered nested-reference unchanged"},{"id":"IETF RFC 2597","type":"specification","body":"IETF","designation":"RFC 2597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2597.txt","https://www.rfc-editor.org/rfc/rfc2597.pdf"],"folder":"IETF/RFC-2597","files":{"txt":{"path":"standards/IETF/RFC-2597/RFC-2597.txt","sha256":"c6b7981e12fed3d0b297622866f1742a7318d14ded90bd159b320934c80e2dce"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Heinanen\nRequest for Comments: 2597 Telia Finland\nCategory: Standards Track F. Baker\n Cisco Systems\n W. Weiss\n Lucent Technologies\n J. Wroclawski\n MIT LCS\n June 1999\n\n Assured Forwarding PHB Group\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a general use Differentiated Services (DS)\n [Blake] Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF).\n The AF PHB group provides delivery of IP packets in four\n independently forwarded A","scope_keywords":["2597","algorithm","algorithms","delivery","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2697","folder":"IETF/RFC-2697","source":"IETF/RFC-2697/RFC-2697.txt","version":null},{"body":"IETF","designation":"RFC 2698","folder":"IETF/RFC-2698","source":"IETF/RFC-2698/RFC-2698.txt","version":null},{"body":"IETF","designation":"RFC 2836","folder":"IETF/RFC-2836","source":"IETF/RFC-2836/RFC-2836.txt","version":null},{"body":"IETF","designation":"RFC 2859","folder":"IETF/RFC-2859","source":"IETF/RFC-2859/RFC-2859.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2884","folder":"IETF/RFC-2884","source":"IETF/RFC-2884/RFC-2884.txt","version":null},{"body":"IETF","designation":"RFC 2963","folder":"IETF/RFC-2963","source":"IETF/RFC-2963/RFC-2963.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 2996","folder":"IETF/RFC-2996","source":"IETF/RFC-2996/RFC-2996.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3662","folder":"IETF/RFC-3662","source":"IETF/RFC-3662/RFC-3662.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 2597 Network Working Group J. Heinanen\nRequest for Comments: 2597 Telia Finland\nCategory: Standards Track F. Baker\n Cisco Systems\n W. Weiss\n Lucent Technologies\n J. Wroclawski\n MIT LCS\n June 1999\n\n Assured Forwarding PHB Group\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a general use Differentiated Services (DS)\n [Blake] Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF).\n The AF PHB group provides delivery of IP packets in four\n independently forwarded A 2597 algorithm algorithms delivery key profile nested-reference unchanged"},{"id":"IETF RFC 2598","type":"specification","body":"IETF","designation":"RFC 2598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2598.txt","https://www.rfc-editor.org/rfc/rfc2598.pdf"],"folder":"IETF/RFC-2598","files":{"txt":{"path":"standards/IETF/RFC-2598/RFC-2598.txt","sha256":"ff698375258a69c06d626a8fadc360488691ff03792c3b56ec0ee8424b44cb67"}},"tags":["nested-reference","unchanged"],"summary":"The definition of PHBs (per-hop forwarding behaviors) is a critical\n part of the work of the Diffserv Working Group. This document\n describes a PHB called Expedited Forwarding. We show the generality\n of this PHB by noting that it can be produced by more than one\n mechanism and give an example of its use to produce at least one\n service, a Virtual Leased Line. A recommended codepoint for this PHB\n is given.\n\n A pdf version of this document is available at\n ftp://ftp.ee.lbl.gov/papers/ef_phb.pdf\n\n1. Introduction\n\n Network nodes that implement the differentiated services enhancements\n to IP use a codepoint in the IP header to select a per-hop behavior\n (PHB) as the specific forwarding treatment for that packet [RFC2474,\n RFC2475]. This memo describes a particular PHB called expedited\n forwarding (EF). The EF PHB can be used to build a low loss, low\n latency, low jitter, assured bandwidth, ","scope_keywords":["2598","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2764","folder":"IETF/RFC-2764","source":"IETF/RFC-2764/RFC-2764.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3247","folder":"IETF/RFC-3247","source":"IETF/RFC-3247/RFC-3247.txt","version":null},{"body":"IETF","designation":"RFC 3248","folder":"IETF/RFC-3248","source":"IETF/RFC-3248/RFC-3248.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null}],"search_text":"IETF RFC 2598 The definition of PHBs (per-hop forwarding behaviors) is a critical\n part of the work of the Diffserv Working Group. This document\n describes a PHB called Expedited Forwarding. We show the generality\n of this PHB by noting that it can be produced by more than one\n mechanism and give an example of its use to produce at least one\n service, a Virtual Leased Line. A recommended codepoint for this PHB\n is given.\n\n A pdf version of this document is available at\n ftp://ftp.ee.lbl.gov/papers/ef_phb.pdf\n\n1. Introduction\n\n Network nodes that implement the differentiated services enhancements\n to IP use a codepoint in the IP header to select a per-hop behavior\n (PHB) as the specific forwarding treatment for that packet [RFC2474,\n RFC2475]. This memo describes a particular PHB called expedited\n forwarding (EF). The EF PHB can be used to build a low loss, low\n latency, low jitter, assured bandwidth,  2598 key nested-reference unchanged"},{"id":"IETF RFC 2607","type":"specification","body":"IETF","designation":"RFC 2607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2607.txt","https://www.rfc-editor.org/rfc/rfc2607.pdf"],"folder":"IETF/RFC-2607","files":{"txt":{"path":"standards/IETF/RFC-2607/RFC-2607.txt","sha256":"96e194f240b037ecd6292c7499e79526dd4eaf46f5476709e61733c2efb8bbcf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how proxy chaining and policy implementation\n can be supported in roaming systems. The mechanisms described in this\n document are in current use.\n\n However, as noted in the security considerations section, the\n techniques outlined in this document are vulnerable to attack from\n external parties as well as susceptible to fraud perpetrated by the\n roaming partners themselves. As a result, such methods are not\n suitable for wide-scale deployment on the Internet.\n\n2. Terminology\n\n This document frequently uses the following terms:\n\n Network Access Server\n The Network Access Server (NAS) is the device that clients contact\n in order to get access to the network.\n\n RADIUS server\n This is a server which provides for authentication/authorization\n via the protocol described in [3], and for accounting as described\n in [4].\n\nAboba & Vollbrecht Informational [Page 1]\n\f\nRFC 260","scope_keywords":["2607","attribute","attributes","audit","authentication","authorization","key","keys","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2904","folder":"IETF/RFC-2904","source":"IETF/RFC-2904/RFC-2904.txt","version":null},{"body":"IETF","designation":"RFC 2977","folder":"IETF/RFC-2977","source":"IETF/RFC-2977/RFC-2977.txt","version":null},{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4849","folder":"IETF/RFC-4849","source":"IETF/RFC-4849/RFC-4849.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null}],"search_text":"IETF RFC 2607 This document describes how proxy chaining and policy implementation\n can be supported in roaming systems. The mechanisms described in this\n document are in current use.\n\n However, as noted in the security considerations section, the\n techniques outlined in this document are vulnerable to attack from\n external parties as well as susceptible to fraud perpetrated by the\n roaming partners themselves. As a result, such methods are not\n suitable for wide-scale deployment on the Internet.\n\n2. Terminology\n\n This document frequently uses the following terms:\n\n Network Access Server\n The Network Access Server (NAS) is the device that clients contact\n in order to get access to the network.\n\n RADIUS server\n This is a server which provides for authentication/authorization\n via the protocol described in [3], and for accounting as described\n in [4].\n\nAboba & Vollbrecht Informational [Page 1]\n\f\nRFC 260 2607 attribute attributes audit authentication authorization key keys management path policy nested-reference unchanged"},{"id":"IETF RFC 2610","type":"specification","body":"IETF","designation":"RFC 2610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2610.txt","https://www.rfc-editor.org/rfc/rfc2610.pdf"],"folder":"IETF/RFC-2610","files":{"txt":{"path":"standards/IETF/RFC-2610/RFC-2610.txt","sha256":"315e049dc0d23c10347e3dbe6e246d48af44ffde72abc34862c8bbfdef564caf"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol provides a framework for\n passing configuration information to hosts on a TCP/IP network.\n Entities using the Service Location Protocol need to find out the\n address of Directory Agents in order to transact messages. Another\n option provides an assignment of scope for configuration of SLP User\n and Service Agents.\n\n1. Introduction\n\n The Dynamic Host Configuration Protocol [2] provides a framework for\n passing configuration information to hosts on a TCP/IP network.\n Entities using the Service Location Protocol, Version 2 [3] and\n Service Location Protocol, Version 1 [4] need to obtain the address\n of Directory Agents and Scope configuration. The Service Location\n Protocol (SLP) provides a default configuration for Scopes and\n Directory Agents may be discovered using multicast or broadcast. It\n is useful in a larger deployment to be able to configure","scope_keywords":["2610","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 3105","folder":"IETF/RFC-3105","source":"IETF/RFC-3105/RFC-3105.txt","version":null},{"body":"IETF","designation":"RFC 3528","folder":"IETF/RFC-3528","source":"IETF/RFC-3528/RFC-3528.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 2610 The Dynamic Host Configuration Protocol provides a framework for\n passing configuration information to hosts on a TCP/IP network.\n Entities using the Service Location Protocol need to find out the\n address of Directory Agents in order to transact messages. Another\n option provides an assignment of scope for configuration of SLP User\n and Service Agents.\n\n1. Introduction\n\n The Dynamic Host Configuration Protocol [2] provides a framework for\n passing configuration information to hosts on a TCP/IP network.\n Entities using the Service Location Protocol, Version 2 [3] and\n Service Location Protocol, Version 1 [4] need to obtain the address\n of Directory Agents and Scope configuration. The Service Location\n Protocol (SLP) provides a default configuration for Scopes and\n Directory Agents may be discovered using multicast or broadcast. It\n is useful in a larger deployment to be able to configure 2610 key policy nested-reference unchanged"},{"id":"IETF RFC 2631","type":"specification","body":"IETF","designation":"RFC 2631","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2631.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2631.txt","https://www.rfc-editor.org/rfc/rfc2631.pdf"],"folder":"IETF/RFC-2631","files":{"txt":{"path":"standards/IETF/RFC-2631/RFC-2631.txt","sha256":"256243e8c509fa5542ea84e46af202c7fd603aa6f46a97fbd12a7e8cbc88d9df"}},"tags":["nested-reference","unchanged"],"summary":"This document standardizes one particular Diffie-Hellman variant,\n based on the ANSI X9.42 draft, developed by the ANSI X9F1 working\n group. Diffie-Hellman is a key agreement algorithm used by two\n parties to agree on a shared secret. An algorithm for converting the\n shared secret into an arbitrary amount of keying material is\n provided. The resulting keying material is used as a symmetric\n encryption key. The Diffie-Hellman variant described requires the\n recipient to have a certificate, but the originator may have a static\n key pair (with the public key placed in a certificate) or an\n ephemeral key pair.","scope_keywords":["2631","algorithm","algorithms","certificate","encryption","key","keys","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2785","folder":"IETF/RFC-2785","source":"IETF/RFC-2785/RFC-2785.txt","version":null},{"body":"IETF","designation":"RFC 2797","folder":"IETF/RFC-2797","source":"IETF/RFC-2797/RFC-2797.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2875","folder":"IETF/RFC-2875","source":"IETF/RFC-2875/RFC-2875.txt","version":null},{"body":"IETF","designation":"RFC 3217","folder":"IETF/RFC-3217","source":"IETF/RFC-3217/RFC-3217.txt","version":null},{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3871","folder":"IETF/RFC-3871","source":"IETF/RFC-3871/RFC-3871.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null}],"search_text":"IETF RFC 2631 This document standardizes one particular Diffie-Hellman variant,\n based on the ANSI X9.42 draft, developed by the ANSI X9F1 working\n group. Diffie-Hellman is a key agreement algorithm used by two\n parties to agree on a shared secret. An algorithm for converting the\n shared secret into an arbitrary amount of keying material is\n provided. The resulting keying material is used as a symmetric\n encryption key. The Diffie-Hellman variant described requires the\n recipient to have a certificate, but the originator may have a static\n key pair (with the public key placed in a certificate) or an\n ephemeral key pair. 2631 algorithm algorithms certificate encryption key keys validation nested-reference unchanged"},{"id":"IETF RFC 2632","type":"specification","body":"IETF","designation":"RFC 2632","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2632.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2632.txt","https://www.rfc-editor.org/rfc/rfc2632.pdf"],"folder":"IETF/RFC-2632","files":{"txt":{"path":"standards/IETF/RFC-2632/RFC-2632.txt","sha256":"756bc6cbe04a8bdf9f7df5889ce5031e55269a37de0badf9859d13267aa89e15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Ramsdell, Editor\nRequest for Comments: 2632 Worldtalk\nCategory: Standards Track June 1999\n\n S/MIME Version 3 Certificate Handling\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Overview\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions), described in\n [SMIME-MSG], provides a method to send and receive secure MIME\n messages. Before using a public key to provide security services, the\n S/MIME agent MUST certify that the public key is valid. S/MIME agents\n MUST use","scope_keywords":["2632","algorithm","attribute","attributes","certificate","certificates","crl","issuer","key","keys","management","pki","profile","revocation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2632 Network Working Group B. Ramsdell, Editor\nRequest for Comments: 2632 Worldtalk\nCategory: Standards Track June 1999\n\n S/MIME Version 3 Certificate Handling\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Overview\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions), described in\n [SMIME-MSG], provides a method to send and receive secure MIME\n messages. Before using a public key to provide security services, the\n S/MIME agent MUST certify that the public key is valid. S/MIME agents\n MUST use 2632 algorithm attribute attributes certificate certificates crl issuer key keys management pki profile revocation signature subject nested-reference unchanged"},{"id":"IETF RFC 2634","type":"specification","body":"IETF","designation":"RFC 2634","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2634.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2634.txt","https://www.rfc-editor.org/rfc/rfc2634.pdf"],"folder":"IETF/RFC-2634","files":{"txt":{"path":"standards/IETF/RFC-2634/RFC-2634.txt","sha256":"821cf38ae96ff02ce2f036fdf77400646dbc25db5dfb24df7970f1a3f1b8e897"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman, Editor\nRequest for Comments: 2634 Internet Mail Consortium\nCategory: Standards Track June 1999\n\n Enhanced Security Services for S/MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document describes four optional security service extensions for\n S/MIME. The services are:\n\n - signed receipts\n - security labels\n - secure mailing lists\n - signing certificates\n\n The first three of these services provide functionality that is\n similar to the","scope_keywords":["2634","attribute","attributes","authentication","certificate","certificates","key","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null}],"search_text":"IETF RFC 2634 Network Working Group P. Hoffman, Editor\nRequest for Comments: 2634 Internet Mail Consortium\nCategory: Standards Track June 1999\n\n Enhanced Security Services for S/MIME\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Introduction\n\n This document describes four optional security service extensions for\n S/MIME. The services are:\n\n - signed receipts\n - security labels\n - secure mailing lists\n - signing certificates\n\n The first three of these services provide functionality that is\n similar to the 2634 attribute attributes authentication certificate certificates key signature signatures nested-reference unchanged"},{"id":"IETF RFC 2696","type":"specification","body":"IETF","designation":"RFC 2696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2696.txt","https://www.rfc-editor.org/rfc/rfc2696.pdf"],"folder":"IETF/RFC-2696","files":{"txt":{"path":"standards/IETF/RFC-2696/RFC-2696.txt","sha256":"a10622f84e0c5117b6cb535ef31f703c6d9d2953e25ec182b9029942228879f1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Weider\nRequest for Comments: 2696 A. Herron\nCategory: Informational A. Anantha\n Microsoft\n T. Howes\n Netscape\n September 1999\n\n LDAP Control Extension for Simple Paged Results Manipulation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n This document describes an LDAPv3 control extension for simple paging\n of search results. This control extension allows a client to control\n the rate at which an LDAP server returns the results of an LDAP\n search operation. This control may be useful when the LDAP client has\n limited resources and may not be able to process the entire result\n set from a given LDAP query, or when the LDAP client is connecte","scope_keywords":["2696","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2891","folder":"IETF/RFC-2891","source":"IETF/RFC-2891/RFC-2891.txt","version":null}],"search_text":"IETF RFC 2696 Network Working Group C. Weider\nRequest for Comments: 2696 A. Herron\nCategory: Informational A. Anantha\n Microsoft\n T. Howes\n Netscape\n September 1999\n\n LDAP Control Extension for Simple Paged Results Manipulation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\n1. Abstract\n\n This document describes an LDAPv3 control extension for simple paging\n of search results. This control extension allows a client to control\n the rate at which an LDAP server returns the results of an LDAP\n search operation. This control may be useful when the LDAP client has\n limited resources and may not be able to process the entire result\n set from a given LDAP query, or when the LDAP client is connecte 2696 key management nested-reference unchanged"},{"id":"IETF RFC 2711","type":"specification","body":"IETF","designation":"RFC 2711","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2711.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2711.txt","https://www.rfc-editor.org/rfc/rfc2711.pdf"],"folder":"IETF/RFC-2711","files":{"txt":{"path":"standards/IETF/RFC-2711/RFC-2711.txt","sha256":"f60f65defe2f470ece05a9f9789a6294b33662c889329ac7ca1f251a4ffb2dc3"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a new IPv6 Hop-by-Hop Option type that alerts\n transit routers to more closely examine the contents of an IP\n datagram. This option is useful for situations where a datagram\n addressed to a particular destination contains information that may\n require special processing by routers along the path.","scope_keywords":["2711","key","license","path","pid","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2710","folder":"IETF/RFC-2710","source":"IETF/RFC-2710/RFC-2710.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3316","folder":"IETF/RFC-3316","source":"IETF/RFC-3316/RFC-3316.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 5350","folder":"IETF/RFC-5350","source":"IETF/RFC-5350/RFC-5350.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 2711 This memo describes a new IPv6 Hop-by-Hop Option type that alerts\n transit routers to more closely examine the contents of an IP\n datagram. This option is useful for situations where a datagram\n addressed to a particular destination contains information that may\n require special processing by routers along the path. 2711 key license path pid registered nested-reference unchanged"},{"id":"IETF RFC 2805","type":"specification","body":"IETF","designation":"RFC 2805","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2805.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2805.txt","https://www.rfc-editor.org/rfc/rfc2805.pdf"],"folder":"IETF/RFC-2805","files":{"txt":{"path":"standards/IETF/RFC-2805/RFC-2805.txt","sha256":"73fb03371ba3918417d627607895279f566c6ffacd30beb68277df8a382df86b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol requirements for the Media Gateway\n Control Protocol between a Media Gateway Controller and a Media\n Gateway.\n\nGreene, et al. Informational [Page 1]\n\f\nRFC 2805 MG Control Protocol Requirements April 2000","scope_keywords":["2805","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2886","folder":"IETF/RFC-2886","source":"IETF/RFC-2886/RFC-2886.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"IETF RFC 2805 This document describes protocol requirements for the Media Gateway\n Control Protocol between a Media Gateway Controller and a Media\n Gateway.\n\nGreene, et al. Informational [Page 1]\n\f\nRFC 2805 MG Control Protocol Requirements April 2000 2805 key management nested-reference unchanged"},{"id":"IETF RFC 2817","type":"specification","body":"IETF","designation":"RFC 2817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2817.txt","https://www.rfc-editor.org/rfc/rfc2817.pdf"],"folder":"IETF/RFC-2817","files":{"txt":{"path":"standards/IETF/RFC-2817/RFC-2817.txt","sha256":"eafd56ede719efdf00c55716b5ae2f8b3d1d40d87857763e7c67099826a16306"}},"tags":["nested-reference","unchanged"],"summary":"This memo explains how to use the Upgrade mechanism in HTTP/1.1 to\n initiate Transport Layer Security (TLS) over an existing TCP\n connection. This allows unsecured and secured HTTP traffic to share\n the same well known port (in this case, http: at 80 rather than\n https: at 443). It also enables \"virtual hosting\", so a single HTTP +\n TLS server can disambiguate traffic intended for several hostnames at\n a single IP address.\n\n Since HTTP/1.1 [1] defines Upgrade as a hop-by-hop mechanism, this\n memo also documents the HTTP CONNECT method for establishing end-to-\n end tunnels across HTTP proxies. Finally, this memo establishes new\n IANA registries for public HTTP status codes, as well as public or\n private Upgrade product tokens.\n\n This memo does NOT affect the current definition of the 'https' URI\n scheme, which already defines a separate namespace\n (http://example.org/ and https://example.","scope_keywords":["2817","authentication","certificate","certificates","encryption","http","https","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2818","folder":"IETF/RFC-2818","source":"IETF/RFC-2818/RFC-2818.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 3229","folder":"IETF/RFC-3229","source":"IETF/RFC-3229/RFC-3229.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4217","folder":"IETF/RFC-4217","source":"IETF/RFC-4217/RFC-4217.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 2817 This memo explains how to use the Upgrade mechanism in HTTP/1.1 to\n initiate Transport Layer Security (TLS) over an existing TCP\n connection. This allows unsecured and secured HTTP traffic to share\n the same well known port (in this case, http: at 80 rather than\n https: at 443). It also enables \"virtual hosting\", so a single HTTP +\n TLS server can disambiguate traffic intended for several hostnames at\n a single IP address.\n\n Since HTTP/1.1 [1] defines Upgrade as a hop-by-hop mechanism, this\n memo also documents the HTTP CONNECT method for establishing end-to-\n end tunnels across HTTP proxies. Finally, this memo establishes new\n IANA registries for public HTTP status codes, as well as public or\n private Upgrade product tokens.\n\n This memo does NOT affect the current definition of the 'https' URI\n scheme, which already defines a separate namespace\n (http://example.org/ and https://example. 2817 authentication certificate certificates encryption http https key tls nested-reference unchanged"},{"id":"IETF RFC 2829","type":"specification","body":"IETF","designation":"RFC 2829","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2829.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2829.txt","https://www.rfc-editor.org/rfc/rfc2829.pdf"],"folder":"IETF/RFC-2829","files":{"txt":{"path":"standards/IETF/RFC-2829/RFC-2829.txt","sha256":"5e0d67c81a7460cfb97ede26ad0ca7f5ceab683ea4198abd246adc7d35aa99bf"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies particular combinations of security\n mechanisms which are required and recommended in LDAP [1]\n implementations.\n\n1. Introduction\n\n LDAP version 3 is a powerful access protocol for directories.\n\n It offers means of searching, fetching and manipulating directory\n content, and ways to access a rich set of security functions.\n\n In order to function for the best of the Internet, it is vital that\n these security functions be interoperable; therefore there has to be\n a minimum subset of security functions that is common to all\n implementations that claim LDAPv3 conformance.\n\n Basic threats to an LDAP directory service include:\n\n (1) Unauthorized access to data via data-fetching operations,\n\nWahl, et al. Standards Track [Page 1]\n\f\nRFC 2829 Authentication Methods for LDAP May 2000\n\n (2) Unauthorized access to reusable client authentication\n information by monitoring other","scope_keywords":["2829","attribute","attributes","authentication","authorization","credential","credentials","encryption","key","path","policies","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2830","folder":"IETF/RFC-2830","source":"IETF/RFC-2830/RFC-2830.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3894","folder":"IETF/RFC-3894","source":"IETF/RFC-3894/RFC-3894.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null}],"search_text":"IETF RFC 2829 This document specifies particular combinations of security\n mechanisms which are required and recommended in LDAP [1]\n implementations.\n\n1. Introduction\n\n LDAP version 3 is a powerful access protocol for directories.\n\n It offers means of searching, fetching and manipulating directory\n content, and ways to access a rich set of security functions.\n\n In order to function for the best of the Internet, it is vital that\n these security functions be interoperable; therefore there has to be\n a minimum subset of security functions that is common to all\n implementations that claim LDAPv3 conformance.\n\n Basic threats to an LDAP directory service include:\n\n (1) Unauthorized access to data via data-fetching operations,\n\nWahl, et al. Standards Track [Page 1]\n\f\nRFC 2829 Authentication Methods for LDAP May 2000\n\n (2) Unauthorized access to reusable client authentication\n information by monitoring other 2829 attribute attributes authentication authorization credential credentials encryption key path policies policy tls nested-reference unchanged"},{"id":"IETF RFC 2830","type":"specification","body":"IETF","designation":"RFC 2830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2830.txt","https://www.rfc-editor.org/rfc/rfc2830.pdf"],"folder":"IETF/RFC-2830","files":{"txt":{"path":"standards/IETF/RFC-2830/RFC-2830.txt","sha256":"3cd29f40ac288a490f5e6e661c49c97f3d46f8bdddd00dc4a0235f09f25540b3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the \"Start Transport Layer Security (TLS)\n Operation\" for LDAP [LDAPv3, TLS]. This operation provides for TLS\n establishment in an LDAP association and is defined in terms of an\n LDAP extended request.\n\n1. Conventions Used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [ReqsKeywords].\n\n2. The Start TLS Request\n\n This section describes the Start TLS extended request and extended\n response themselves: how to form the request, the form of the\n response, and enumerates the various result codes the client MUST be\n prepared to handle.\n\n The section following this one then describes how to sequence an\n overall Start TLS Operation.\n\nHodges, et al. Standards Track [Page 1]\n\f\nRFC 2830 LDAPv3: Extension for Transport Laye","scope_keywords":["2830","authorization","certificate","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 3062","folder":"IETF/RFC-3062","source":"IETF/RFC-3062/RFC-3062.txt","version":null},{"body":"IETF","designation":"RFC 3088","folder":"IETF/RFC-3088","source":"IETF/RFC-3088/RFC-3088.txt","version":null},{"body":"IETF","designation":"RFC 3377","folder":"IETF/RFC-3377","source":"IETF/RFC-3377/RFC-3377.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null}],"search_text":"IETF RFC 2830 This document defines the \"Start Transport Layer Security (TLS)\n Operation\" for LDAP [LDAPv3, TLS]. This operation provides for TLS\n establishment in an LDAP association and is defined in terms of an\n LDAP extended request.\n\n1. Conventions Used in this Document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [ReqsKeywords].\n\n2. The Start TLS Request\n\n This section describes the Start TLS extended request and extended\n response themselves: how to form the request, the form of the\n response, and enumerates the various result codes the client MUST be\n prepared to handle.\n\n The section following this one then describes how to sequence an\n overall Start TLS Operation.\n\nHodges, et al. Standards Track [Page 1]\n\f\nRFC 2830 LDAPv3: Extension for Transport Laye 2830 authorization certificate key tls nested-reference unchanged"},{"id":"IETF RFC 2836","type":"specification","body":"IETF","designation":"RFC 2836","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2836.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2836.txt","https://www.rfc-editor.org/rfc/rfc2836.pdf"],"folder":"IETF/RFC-2836","files":{"txt":{"path":"standards/IETF/RFC-2836/RFC-2836.txt","sha256":"cf1968e299349b9db915776017febab561669ed18e70afbce3c09e9609cca5b8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Brim\nRequest for Comments: 2836 B. Carpenter\nCategory: Standards Track F. Le Faucheur\n May 2000\n\n Per Hop Behavior Identification Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents:\n\n 1. Introduction................................................. 1\n 1.1. Usage Scenarios............................................ 2\n 2. Encoding..................................................... 3\n 3. IANA Considerations.......................................... 4","scope_keywords":["2836","identification","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3140","folder":"IETF/RFC-3140","source":"IETF/RFC-3140/RFC-3140.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null}],"search_text":"IETF RFC 2836 Network Working Group S. Brim\nRequest for Comments: 2836 B. Carpenter\nCategory: Standards Track F. Le Faucheur\n May 2000\n\n Per Hop Behavior Identification Codes\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nTable of Contents:\n\n 1. Introduction................................................. 1\n 1.1. Usage Scenarios............................................ 2\n 2. Encoding..................................................... 3\n 3. IANA Considerations.......................................... 4 2836 identification key management path nested-reference unchanged"},{"id":"IETF RFC 2867","type":"specification","body":"IETF","designation":"RFC 2867","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2867.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2867.txt","https://www.rfc-editor.org/rfc/rfc2867.pdf"],"folder":"IETF/RFC-2867","files":{"txt":{"path":"standards/IETF/RFC-2867/RFC-2867.txt","sha256":"7a072b7431b60949d111a67700ee89a19d4926b61eb33fc64afb7e11e75c72d9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new RADIUS accounting Attributes and new values\n for the existing Acct-Status-Type Attribute [1] designed to support\n the provision of compulsory tunneling in dial-up networks.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\", are to be interpreted as\n described in [2].\n\n1. Introduction\n\n Many applications of tunneling protocols such as PPTP [5] and L2TP\n [4] involve dial-up network access. Some, such as the provision of\n secure access to corporate intranets via the Internet, are\n characterized by voluntary tunneling: the tunnel is created at the\n request of the user for a specific purpose. Other applications\n involve compulsory tunneling: the tunnel is created without any\n action from the user and without allowing the user any choice in the\n matter, as a service of the ","scope_keywords":["2867","attribute","attributes","audit","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2868","folder":"IETF/RFC-2868","source":"IETF/RFC-2868/RFC-2868.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2881","folder":"IETF/RFC-2881","source":"IETF/RFC-2881/RFC-2881.txt","version":null},{"body":"IETF","designation":"RFC 2882","folder":"IETF/RFC-2882","source":"IETF/RFC-2882/RFC-2882.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null}],"search_text":"IETF RFC 2867 This document defines new RADIUS accounting Attributes and new values\n for the existing Acct-Status-Type Attribute [1] designed to support\n the provision of compulsory tunneling in dial-up networks.\n\nSpecification of Requirements\n\n In this document, the key words \"MAY\", \"MUST, \"MUST NOT\", \"optional\",\n \"recommended\", \"SHOULD\", and \"SHOULD NOT\", are to be interpreted as\n described in [2].\n\n1. Introduction\n\n Many applications of tunneling protocols such as PPTP [5] and L2TP\n [4] involve dial-up network access. Some, such as the provision of\n secure access to corporate intranets via the Internet, are\n characterized by voluntary tunneling: the tunnel is created at the\n request of the user for a specific purpose. Other applications\n involve compulsory tunneling: the tunnel is created without any\n action from the user and without allowing the user any choice in the\n matter, as a service of the  2867 attribute attributes audit key timestamp nested-reference unchanged"},{"id":"IETF RFC 2876","type":"specification","body":"IETF","designation":"RFC 2876","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2876.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2876.txt","https://www.rfc-editor.org/rfc/rfc2876.pdf"],"folder":"IETF/RFC-2876","files":{"txt":{"path":"standards/IETF/RFC-2876/RFC-2876.txt","sha256":"f88342e6d5c0551d043b56b85b0dd1af64adda3c340676a7db3768fe62e2dfc0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the Key Exchange\n Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction with\n the Cryptographic Message Syntax [CMS] enveloped-data and encrypted-\n data content types.\n\n1. Introduction\n\n Throughout this document, the terms MUST, MUST NOT, SHOULD and MAY\n are used in capital letters. This conforms to the definitions in\n [MUSTSHOULD]. [MUSTSHOULD] defines the use of these key words to help\n make the intent of standards track documents as clear as possible.\n The same key words are used in this document to help implementers\n achieve interoperability. Software that claims compliance with this\n document MUST provide the capabilities as indicated by the MUST, MUST\n NOT, SHOULD and MAY terms. The KEA and SKIPJACK cryptographic\n algorithms are described in [SJ-KEA].\n\n2. Content Encryption Process\n\n This section applies to the constructi","scope_keywords":["2876","algorithm","algorithms","certificate","certificates","encryption","issuer","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3278","folder":"IETF/RFC-3278","source":"IETF/RFC-3278/RFC-3278.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null}],"search_text":"IETF RFC 2876 This document describes the conventions for using the Key Exchange\n Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction with\n the Cryptographic Message Syntax [CMS] enveloped-data and encrypted-\n data content types.\n\n1. Introduction\n\n Throughout this document, the terms MUST, MUST NOT, SHOULD and MAY\n are used in capital letters. This conforms to the definitions in\n [MUSTSHOULD]. [MUSTSHOULD] defines the use of these key words to help\n make the intent of standards track documents as clear as possible.\n The same key words are used in this document to help implementers\n achieve interoperability. Software that claims compliance with this\n document MUST provide the capabilities as indicated by the MUST, MUST\n NOT, SHOULD and MAY terms. The KEA and SKIPJACK cryptographic\n algorithms are described in [SJ-KEA].\n\n2. Content Encryption Process\n\n This section applies to the constructi 2876 algorithm algorithms certificate certificates encryption issuer key management path subject nested-reference unchanged"},{"id":"IETF RFC 2891","type":"specification","body":"IETF","designation":"RFC 2891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2891.txt","https://www.rfc-editor.org/rfc/rfc2891.pdf"],"folder":"IETF/RFC-2891","files":{"txt":{"path":"standards/IETF/RFC-2891/RFC-2891.txt","sha256":"fd1ca66be2747855be424449c3b19b6110dd3b87035af0832e91eb0ff0a8a4b0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes two LDAPv3 control extensions for server side\n sorting of search results. These controls allows a client to specify\n the attribute types and matching rules a server should use when\n returning the results to an LDAP search request. The controls may be\n useful when the LDAP client has limited functionality or for some\n other reason cannot sort the results but still needs them sorted.\n Other permissible controls on search operations are not defined in\n this extension.\n\n The sort controls allow a server to return a result code for the\n sorting of the results that is independent of the result code\n returned for the search operation.\n\n The key words \"MUST\", \"SHOULD\", and \"MAY\" used in this document are\n to be interpreted as described in [bradner97].\n\nHowes, et al. Standards Track [Page 1]\n\f\nRFC 2891 LDAP Control Extension for Server Side Sorting August 2000\n\n1. The Cont","scope_keywords":["2891","attribute","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3421","folder":"IETF/RFC-3421","source":"IETF/RFC-3421/RFC-3421.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2891 This document describes two LDAPv3 control extensions for server side\n sorting of search results. These controls allows a client to specify\n the attribute types and matching rules a server should use when\n returning the results to an LDAP search request. The controls may be\n useful when the LDAP client has limited functionality or for some\n other reason cannot sort the results but still needs them sorted.\n Other permissible controls on search operations are not defined in\n this extension.\n\n The sort controls allow a server to return a result code for the\n sorting of the results that is independent of the result code\n returned for the search operation.\n\n The key words \"MUST\", \"SHOULD\", and \"MAY\" used in this document are\n to be interpreted as described in [bradner97].\n\nHowes, et al. Standards Track [Page 1]\n\f\nRFC 2891 LDAP Control Extension for Server Side Sorting August 2000\n\n1. The Cont 2891 attribute key keys nested-reference unchanged"},{"id":"IETF RFC 2907","type":"specification","body":"IETF","designation":"RFC 2907","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2907.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2907.txt","https://www.rfc-editor.org/rfc/rfc2907.pdf"],"folder":"IETF/RFC-2907","files":{"txt":{"path":"standards/IETF/RFC-2907/RFC-2907.txt","sha256":"7c8828fe6398dc356f35f77cbd18ade566d0eac01a2a519134b883baaf87e654"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new option to the Multicast Address Dynamic\n Client Allocation Protocol (MADCAP) to support nested scoping. The\n new option's purpose is to allow clients to learn which scopes nest\n inside each other, and hence it may be used for expanding scope\n searches or hierarchical multicast transport.","scope_keywords":["2907","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2907 This document defines a new option to the Multicast Address Dynamic\n Client Allocation Protocol (MADCAP) to support nested scoping. The\n new option's purpose is to allow clients to learn which scopes nest\n inside each other, and hence it may be used for expanding scope\n searches or hierarchical multicast transport. 2907 algorithm nested-reference unchanged"},{"id":"IETF RFC 2927","type":"specification","body":"IETF","designation":"RFC 2927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2927.txt","https://www.rfc-editor.org/rfc/rfc2927.pdf"],"folder":"IETF/RFC-2927","files":{"txt":{"path":"standards/IETF/RFC-2927/RFC-2927.txt","sha256":"771e5ecc29351b7a65ae1bf8cdcfd8247377f3ad24c04d0fa936282a0fa31448"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a multipurpose internet mail extensions (MIME)\n directory profile for holding a lightweight directory access protocol\n (LDAP) schema. It is intended for communication with the Internet\n schema listing service.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [4].\n\n1. Overview\n\n This document defines how a MIME type may be used to transfer a\n single LDAPv3 schema definition.\n\n A schema for use with LDAPv3 consists of any number of object class,\n attribute type, matching rule and syntax definitions. These concepts\n are defined in the LDAPv3 protocol definition [2]. The schema MAY\n have a numeric OID assigned to it by a schema listing or registration\n service.\n\n A schema may import definitions from another schema. Schema im","scope_keywords":["2927","attribute","attributes","crl","key","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null}],"search_text":"IETF RFC 2927 This document defines a multipurpose internet mail extensions (MIME)\n directory profile for holding a lightweight directory access protocol\n (LDAP) schema. It is intended for communication with the Internet\n schema listing service.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [4].\n\n1. Overview\n\n This document defines how a MIME type may be used to transfer a\n single LDAPv3 schema definition.\n\n A schema for use with LDAPv3 consists of any number of object class,\n attribute type, matching rule and syntax definitions. These concepts\n are defined in the LDAPv3 protocol definition [2]. The schema MAY\n have a numeric OID assigned to it by a schema listing or registration\n service.\n\n A schema may import definitions from another schema. Schema im 2927 attribute attributes crl key profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 2937","type":"specification","body":"IETF","designation":"RFC 2937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2937.txt","https://www.rfc-editor.org/rfc/rfc2937.pdf"],"folder":"IETF/RFC-2937","files":{"txt":{"path":"standards/IETF/RFC-2937/RFC-2937.txt","sha256":"11d8c332f073ddb390da2732369750ecd10e9d290c5ba60dc5dc9d605dea56ac"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to specify the order in which name services should be consulted when\n resolving hostnames and other information.","scope_keywords":["2937","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null}],"search_text":"IETF RFC 2937 This document defines a new Dynamic Host Configuration Protocol\n (DHCP) option which is passed from the DHCP Server to the DHCP Client\n to specify the order in which name services should be consulted when\n resolving hostnames and other information. 2937 authentication key nested-reference unchanged"},{"id":"IETF RFC 2985","type":"specification","body":"IETF","designation":"RFC 2985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2985.txt","https://www.rfc-editor.org/rfc/rfc2985.pdf"],"folder":"IETF/RFC-2985","files":{"txt":{"path":"standards/IETF/RFC-2985/RFC-2985.txt","sha256":"0a7a760f5becd036f11a17d5a4b4ba831ef76b29d6f74922c320139bead580f1"}},"tags":["nested-reference","unchanged"],"summary":"This memo represents a republication of PKCS #9 v2.0 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from that specification.\n\n This memo provides a selection of object classes and attribute types\n for use in conjunction with public-key cryptography and Lightweight\n Directory Access Protocol (LDAP) accessible directories. It also\n includes ASN.1 syntax for all constructs.","scope_keywords":["2985","attribute","attributes","certificate","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 2985 This memo represents a republication of PKCS #9 v2.0 from RSA\n Laboratories' Public-Key Cryptography Standards (PKCS) series, and\n change control is retained within the PKCS process. The body of this\n document, except for the security considerations section, is taken\n directly from that specification.\n\n This memo provides a selection of object classes and attribute types\n for use in conjunction with public-key cryptography and Lightweight\n Directory Access Protocol (LDAP) accessible directories. It also\n includes ASN.1 syntax for all constructs. 2985 attribute attributes certificate key keys subject nested-reference unchanged"},{"id":"IETF RFC 3004","type":"specification","body":"IETF","designation":"RFC 3004","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3004.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3004.txt","https://www.rfc-editor.org/rfc/rfc3004.pdf"],"folder":"IETF/RFC-3004","files":{"txt":{"path":"standards/IETF/RFC-3004/RFC-3004.txt","sha256":"d1488dcc8274d1e8128b734e98709088998c91f926d5141019cb0b4d34232a7c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Stump\nRequest for Comments: 3004 IBM\nCategory: Standards Track R. Droms\n Cisco Systems\n Y. Gu\n R. Vyaghrapuri\n A. Demirtjis\n Microsoft\n B. Beser\n Pacific Broadband Communications\n J. Privat\n Northstream AB\n November 2000\n\n The User Class Option for DHCP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This option is used by a Dynamic Host Configuration Protocol (DHCP)\n client to optionally identify the type or category of user or\n applications it represents. Th","scope_keywords":["3004","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 3004 Network Working Group G. Stump\nRequest for Comments: 3004 IBM\nCategory: Standards Track R. Droms\n Cisco Systems\n Y. Gu\n R. Vyaghrapuri\n A. Demirtjis\n Microsoft\n B. Beser\n Pacific Broadband Communications\n J. Privat\n Northstream AB\n November 2000\n\n The User Class Option for DHCP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This option is used by a Dynamic Host Configuration Protocol (DHCP)\n client to optionally identify the type or category of user or\n applications it represents. Th 3004 authentication key nested-reference unchanged"},{"id":"IETF RFC 3011","type":"specification","body":"IETF","designation":"RFC 3011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3011.txt","https://www.rfc-editor.org/rfc/rfc3011.pdf"],"folder":"IETF/RFC-3011","files":{"txt":{"path":"standards/IETF/RFC-3011/RFC-3011.txt","sha256":"b5809d9f053e6cdc3003c04a8c529f23fb24794c47c21370f8199a48743d0202"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Dynamic Host Configuration Protocol (DHCP)\n option for selecting the subnet on which to allocate an address.\n This option would override a DHCP server's normal methods of\n selecting the subnet on which to allocate an address for a client.","scope_keywords":["3011","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null}],"search_text":"IETF RFC 3011 This memo defines a new Dynamic Host Configuration Protocol (DHCP)\n option for selecting the subnet on which to allocate an address.\n This option would override a DHCP server's normal methods of\n selecting the subnet on which to allocate an address for a client. 3011 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 3029","type":"specification","body":"IETF","designation":"RFC 3029","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3029.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3029.txt","https://www.rfc-editor.org/rfc/rfc3029.pdf"],"folder":"IETF/RFC-3029","files":{"txt":{"path":"standards/IETF/RFC-3029/RFC-3029.txt","sha256":"d658f06543da4036fce3f06e4ae990173ad148ff9779b39fb28db8f9c6ca9983"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general Data Validation and Certification\n Server (DVCS) and the protocols to be used when communicating with\n it. The Data Validation and Certification Server is a Trusted Third\n Party (TTP) that can be used as one component in building reliable\n non-repudiation services.\n\n Useful Data Validation and Certification Server responsibilities in a\n PKI are to assert the validity of signed documents, public key\n certificates, and the possession or existence of data.\n\n Assertions created by this protocol are called Data Validation\n Certificates (DVC).\n\n We give examples of how to use the Data Validation and Certification\n Server to extend the lifetime of a signature beyond key expiry or\n revocation and to query the Data Validation and Certification Server\n regarding the status of a public key certificate. The document\n includes a complete example of a time stamping tr","scope_keywords":["3029","attribute","certificate","certificates","crl","http","https","identification","key","ocsp","pki","revocation","signature","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4134","folder":"IETF/RFC-4134","source":"IETF/RFC-4134/RFC-4134.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null}],"search_text":"IETF RFC 3029 This document describes a general Data Validation and Certification\n Server (DVCS) and the protocols to be used when communicating with\n it. The Data Validation and Certification Server is a Trusted Third\n Party (TTP) that can be used as one component in building reliable\n non-repudiation services.\n\n Useful Data Validation and Certification Server responsibilities in a\n PKI are to assert the validity of signed documents, public key\n certificates, and the possession or existence of data.\n\n Assertions created by this protocol are called Data Validation\n Certificates (DVC).\n\n We give examples of how to use the Data Validation and Certification\n Server to extend the lifetime of a signature beyond key expiry or\n revocation and to query the Data Validation and Certification Server\n regarding the status of a public key certificate. The document\n includes a complete example of a time stamping tr 3029 attribute certificate certificates crl http https identification key ocsp pki revocation signature trust validation nested-reference unchanged"},{"id":"IETF RFC 3031","type":"specification","body":"IETF","designation":"RFC 3031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3031.txt","https://www.rfc-editor.org/rfc/rfc3031.pdf"],"folder":"IETF/RFC-3031","files":{"txt":{"path":"standards/IETF/RFC-3031/RFC-3031.txt","sha256":"fa446814ffe127e39b8a4ff49766d7eba2d2c176189c23c058bc0a739eac8e8e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the architecture for Multiprotocol Label\n Switching (MPLS).","scope_keywords":["3031","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3037","folder":"IETF/RFC-3037","source":"IETF/RFC-3037/RFC-3037.txt","version":null},{"body":"IETF","designation":"RFC 3107","folder":"IETF/RFC-3107","source":"IETF/RFC-3107/RFC-3107.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3210","folder":"IETF/RFC-3210","source":"IETF/RFC-3210/RFC-3210.txt","version":null},{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3215","folder":"IETF/RFC-3215","source":"IETF/RFC-3215/RFC-3215.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null},{"body":"IETF","designation":"RFC 3429","folder":"IETF/RFC-3429","source":"IETF/RFC-3429/RFC-3429.txt","version":null},{"body":"IETF","designation":"RFC 3443","folder":"IETF/RFC-3443","source":"IETF/RFC-3443/RFC-3443.txt","version":null},{"body":"IETF","designation":"RFC 3469","folder":"IETF/RFC-3469","source":"IETF/RFC-3469/RFC-3469.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 4378","folder":"IETF/RFC-4378","source":"IETF/RFC-4378/RFC-4378.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4817","folder":"IETF/RFC-4817","source":"IETF/RFC-4817/RFC-4817.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5331","folder":"IETF/RFC-5331","source":"IETF/RFC-5331/RFC-5331.txt","version":null},{"body":"IETF","designation":"RFC 5332","folder":"IETF/RFC-5332","source":"IETF/RFC-5332/RFC-5332.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 5693","folder":"IETF/RFC-5693","source":"IETF/RFC-5693/RFC-5693.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 3031 This document specifies the architecture for Multiprotocol Label\n Switching (MPLS). 3031 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 3034","type":"specification","body":"IETF","designation":"RFC 3034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3034.txt","https://www.rfc-editor.org/rfc/rfc3034.pdf"],"folder":"IETF/RFC-3034","files":{"txt":{"path":"standards/IETF/RFC-3034/RFC-3034.txt","sha256":"18a381bff50f1332f62f71f8bf2f31f5903b1500581ebba5a2d4415a630ed5e3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the model and generic mechanisms for\n Multiprotocol Label Switching on Frame Relay networks. Furthermore,\n it extends and clarifies portions of the Multiprotocol Label\n Switching Architecture described in [ARCH] and the Label Distribution\n Protocol (LDP) described in [LDP] relative to Frame Relay Networks.\n MPLS enables the use of Frame Relay Switches as Label Switching\n Routers (LSRs).","scope_keywords":["3034","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null}],"search_text":"IETF RFC 3034 This document defines the model and generic mechanisms for\n Multiprotocol Label Switching on Frame Relay networks. Furthermore,\n it extends and clarifies portions of the Multiprotocol Label\n Switching Architecture described in [ARCH] and the Label Distribution\n Protocol (LDP) described in [LDP] relative to Frame Relay Networks.\n MPLS enables the use of Frame Relay Switches as Label Switching\n Routers (LSRs). 3034 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 3035","type":"specification","body":"IETF","designation":"RFC 3035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3035.txt","https://www.rfc-editor.org/rfc/rfc3035.pdf"],"folder":"IETF/RFC-3035","files":{"txt":{"path":"standards/IETF/RFC-3035/RFC-3035.txt","sha256":"b7a16540e4cca64563e0f91da30cb23da3903197fbcb30d9e0fef662ff6cdf1d"}},"tags":["nested-reference","unchanged"],"summary":"The Multiprotocol Label Switching (MPLS) Architecture [1] discusses a\n way in which Asynchronous Transfer Mode (ATM) switches may be used as\n Label Switching Routers. The ATM switches run network layer routing\n algorithms (such as Open Shortest Path First (OSPF), Intermediate\n System to Intermediate System (IS-IS), etc.), and their data\n forwarding is based on the results of these routing algorithms. No\n ATM-specific routing or addressing is needed. ATM switches used in\n this way are known as ATM-LSRs (Label Switching Routers).\n\n This document extends and clarifies the relevant portions of [1] and\n [2] by specifying in more detail the procedures which to be used when\n distributing labels to or from ATM-LSRs, when those labels represent\n Forwarding Equivalence Classes (FECs, see [1]) for which the routes\n are determined on a hop-by-hop basis by network layer routing\n algorithms.\n\n This do","scope_keywords":["3035","algorithm","algorithms","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3031","folder":"IETF/RFC-3031","source":"IETF/RFC-3031/RFC-3031.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 3036","folder":"IETF/RFC-3036","source":"IETF/RFC-3036/RFC-3036.txt","version":null},{"body":"IETF","designation":"RFC 3215","folder":"IETF/RFC-3215","source":"IETF/RFC-3215/RFC-3215.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null}],"search_text":"IETF RFC 3035 The Multiprotocol Label Switching (MPLS) Architecture [1] discusses a\n way in which Asynchronous Transfer Mode (ATM) switches may be used as\n Label Switching Routers. The ATM switches run network layer routing\n algorithms (such as Open Shortest Path First (OSPF), Intermediate\n System to Intermediate System (IS-IS), etc.), and their data\n forwarding is based on the results of these routing algorithms. No\n ATM-specific routing or addressing is needed. ATM switches used in\n this way are known as ATM-LSRs (Label Switching Routers).\n\n This document extends and clarifies the relevant portions of [1] and\n [2] by specifying in more detail the procedures which to be used when\n distributing labels to or from ATM-LSRs, when those labels represent\n Forwarding Equivalence Classes (FECs, see [1]) for which the routes\n are determined on a hop-by-hop basis by network layer routing\n algorithms.\n\n This do 3035 algorithm algorithms key path nested-reference unchanged"},{"id":"IETF RFC 3039","type":"specification","body":"IETF","designation":"RFC 3039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3039.txt","https://www.rfc-editor.org/rfc/rfc3039.pdf"],"folder":"IETF/RFC-3039","files":{"txt":{"path":"standards/IETF/RFC-3039/RFC-3039.txt","sha256":"d78e9991ec9f9c52784c6449dda842752f8ff945e536eb1c7d5f749db66411ce"}},"tags":["nested-reference","unchanged"],"summary":"This document forms a certificate profile for Qualified Certificates,\n based on RFC 2459, for use in the Internet. The term Qualified\n Certificate is used to describe a certificate with a certain\n qualified status within applicable governing law. Further, Qualified\n Certificates are issued exclusively to physical persons.\n\n The goal of this document is to define a general syntax independent\n of local legal requirements. The profile is however designed to\n allow further profiling in order to meet specific local needs.\n\n It is important to note that the profile does not define any legal\n requirements for Qualified Certificates.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nSantesson, et al. Standards Track [Page 1]\n\f\nRFC 3039 Qualified Cer","scope_keywords":["3039","attribute","attributes","certificate","certificates","issuer","key","pki","policies","policy","profile","profiles","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 3039 This document forms a certificate profile for Qualified Certificates,\n based on RFC 2459, for use in the Internet. The term Qualified\n Certificate is used to describe a certificate with a certain\n qualified status within applicable governing law. Further, Qualified\n Certificates are issued exclusively to physical persons.\n\n The goal of this document is to define a general syntax independent\n of local legal requirements. The profile is however designed to\n allow further profiling in order to meet specific local needs.\n\n It is important to note that the profile does not define any legal\n requirements for Qualified Certificates.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119.\n\nSantesson, et al. Standards Track [Page 1]\n\f\nRFC 3039 Qualified Cer 3039 attribute attributes certificate certificates issuer key pki policies policy profile profiles qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 3051","type":"specification","body":"IETF","designation":"RFC 3051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3051.txt","https://www.rfc-editor.org/rfc/rfc3051.pdf"],"folder":"IETF/RFC-3051","files":{"txt":{"path":"standards/IETF/RFC-3051/RFC-3051.txt","sha256":"6d77d6428fcd35235f79ec3cacad94a6a9e4f847f92110174705f34041bafef5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a compression method based on the data\n compression algorithm described in International Telecommunication\n Union (ITU-T) Recommendation V.44. Recommendation V.44 is a modem\n standard but Annex B, Clause B.1, of the recommendation describes the\n implementation of V.44 in packet networks (e.g., V.44 Packet Method).\n This document defines the application of V.44 Packet Method to the\n Internet Protocol (IP) Payload Compression Protocol (RFC 2393). RFC\n 2393 defines a method for applying lossless compression to the\n payload portion of IP datagrams.\n\n V.44 Packet Method is based upon the LZJH data compression algorithm.\n Throughout the remainder of this document the terms V.44 Packet\n Method and LZJH are synonymous.\n\nHeath & Border Informational [Page 1]\n\f\nRFC 3051 IP Payload Compression Using ITU-T V.44 January 2001","scope_keywords":["3051","algorithm","algorithms","attribute","attributes","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 3051 This document describes a compression method based on the data\n compression algorithm described in International Telecommunication\n Union (ITU-T) Recommendation V.44. Recommendation V.44 is a modem\n standard but Annex B, Clause B.1, of the recommendation describes the\n implementation of V.44 in packet networks (e.g., V.44 Packet Method).\n This document defines the application of V.44 Packet Method to the\n Internet Protocol (IP) Payload Compression Protocol (RFC 2393). RFC\n 2393 defines a method for applying lossless compression to the\n payload portion of IP datagrams.\n\n V.44 Packet Method is based upon the LZJH data compression algorithm.\n Throughout the remainder of this document the terms V.44 Packet\n Method and LZJH are synonymous.\n\nHeath & Border Informational [Page 1]\n\f\nRFC 3051 IP Payload Compression Using ITU-T V.44 January 2001 3051 algorithm algorithms attribute attributes hash key nested-reference unchanged"},{"id":"IETF RFC 3062","type":"specification","body":"IETF","designation":"RFC 3062","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3062.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3062.txt","https://www.rfc-editor.org/rfc/rfc3062.pdf"],"folder":"IETF/RFC-3062","files":{"txt":{"path":"standards/IETF/RFC-3062/RFC-3062.txt","sha256":"2579e1c8e1d57c7983c72a15679a9e328b5c3649d784e4844bd369d51cb7ba72"}},"tags":["nested-reference","unchanged"],"summary":"The integration of the Lightweight Directory Access Protocol (LDAP)\n and external authentication services has introduced non-DN\n authentication identities and allowed for non-directory storage of\n passwords. As such, mechanisms which update the directory (e.g.,\n Modify) cannot be used to change a user's password. This document\n describes an LDAP extended operation to allow modification of user\n passwords which is not dependent upon the form of the authentication\n identity nor the password storage mechanism used.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", and \"MAY\" in this document are\n to be interpreted as described in RFC 2119.\n\n1. Background and Intent of Use\n\n Lightweight Directory Access Protocol (LDAP) [RFC2251] is designed to\n support an number of authentication mechanisms including simple user\n name/password pairs.","scope_keywords":["3062","attribute","attributes","authentication","key","policies","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"IETF RFC 3062 The integration of the Lightweight Directory Access Protocol (LDAP)\n and external authentication services has introduced non-DN\n authentication identities and allowed for non-directory storage of\n passwords. As such, mechanisms which update the directory (e.g.,\n Modify) cannot be used to change a user's password. This document\n describes an LDAP extended operation to allow modification of user\n passwords which is not dependent upon the form of the authentication\n identity nor the password storage mechanism used.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", and \"MAY\" in this document are\n to be interpreted as described in RFC 2119.\n\n1. Background and Intent of Use\n\n Lightweight Directory Access Protocol (LDAP) [RFC2251] is designed to\n support an number of authentication mechanisms including simple user\n name/password pairs. 3062 attribute attributes authentication key policies policy presentation nested-reference unchanged"},{"id":"IETF RFC 3074","type":"specification","body":"IETF","designation":"RFC 3074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3074.txt","https://www.rfc-editor.org/rfc/rfc3074.pdf"],"folder":"IETF/RFC-3074","files":{"txt":{"path":"standards/IETF/RFC-3074/RFC-3074.txt","sha256":"1f3d5e93c2c7490b338b3028b0026f1570c9f2c1940b6cb65102ab0684a3a8b4"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a method of algorithmic load balancing. It\n enables multiple, cooperating servers to decide which one should\n service a client, without exchanging any information beyond initial\n configuration.\n\n The server selection is based on the servers hashing client Media\n Access Control (MAC) addresses when multiple Dynamic Host\n Configuration Protocol (DHCP) servers are available to service DHCP\n clients. The proposed technique provides for efficient server\n selection when multiple DHCP servers offer services on a network\n without requiring any changes to existing DHCP clients. The same\n method is proposed to select the target server of a forwarding agent\n such as a Bootstrap Protocol (BOOTP) relay.\n\n1. Introduction\n\n This protocol was originally devised to support a specific load\n balancing optimization of the DHCP Failover Protocol [FAILOVR]. The\n authors later realized t","scope_keywords":["3074","algorithm","attribute","hash","hashing","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5010","folder":"IETF/RFC-5010","source":"IETF/RFC-5010/RFC-5010.txt","version":null}],"search_text":"IETF RFC 3074 This document proposes a method of algorithmic load balancing. It\n enables multiple, cooperating servers to decide which one should\n service a client, without exchanging any information beyond initial\n configuration.\n\n The server selection is based on the servers hashing client Media\n Access Control (MAC) addresses when multiple Dynamic Host\n Configuration Protocol (DHCP) servers are available to service DHCP\n clients. The proposed technique provides for efficient server\n selection when multiple DHCP servers offer services on a network\n without requiring any changes to existing DHCP clients. The same\n method is proposed to select the target server of a forwarding agent\n such as a Bootstrap Protocol (BOOTP) relay.\n\n1. Introduction\n\n This protocol was originally devised to support a specific load\n balancing optimization of the DHCP Failover Protocol [FAILOVR]. The\n authors later realized t 3074 algorithm attribute hash hashing key nested-reference unchanged"},{"id":"IETF RFC 3076","type":"specification","body":"IETF","designation":"RFC 3076","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3076.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3076.txt","https://www.rfc-editor.org/rfc/rfc3076.pdf"],"folder":"IETF/RFC-3076","files":{"txt":{"path":"standards/IETF/RFC-3076/RFC-3076.txt","sha256":"c2f8abf277cb1d920cadd98c9354ef154c5c9e4b0135d0f8a17737becf3ef2ae"}},"tags":["nested-reference","unchanged"],"summary":"Any XML (Extensible Markup Language) document is part of a set of XML\n documents that are logically equivalent within an application\n context, but which vary in physical representation based on syntactic\n changes permitted by XML 1.0 and Namespaces in XML. This\n specification describes a method for generating a physical\n representation, the canonical form, of an XML document that accounts\n for the permissible changes. Except for limitations regarding a few\n unusual cases, if two documents have the same canonical form, then\n the two documents are logically equivalent within the given\n application context. Note that two documents may have differing\n canonical forms yet still be equivalent in a given context based on\n application-specific equivalence rules for which no generalized XML\n specification could account.\n\nBoyer Informational [Page 1]\n\f\nRFC 3076 Canonical XML March 2001","scope_keywords":["3076","algorithm","attribute","attributes","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3741","folder":"IETF/RFC-3741","source":"IETF/RFC-3741/RFC-3741.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 3076 Any XML (Extensible Markup Language) document is part of a set of XML\n documents that are logically equivalent within an application\n context, but which vary in physical representation based on syntactic\n changes permitted by XML 1.0 and Namespaces in XML. This\n specification describes a method for generating a physical\n representation, the canonical form, of an XML document that accounts\n for the permissible changes. Except for limitations regarding a few\n unusual cases, if two documents have the same canonical form, then\n the two documents are logically equivalent within the given\n application context. Note that two documents may have differing\n canonical forms yet still be equivalent in a given context based on\n application-specific equivalence rules for which no generalized XML\n specification could account.\n\nBoyer Informational [Page 1]\n\f\nRFC 3076 Canonical XML March 2001 3076 algorithm attribute attributes key path presentation nested-reference unchanged"},{"id":"IETF RFC 3082","type":"specification","body":"IETF","designation":"RFC 3082","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3082.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3082.txt","https://www.rfc-editor.org/rfc/rfc3082.pdf"],"folder":"IETF/RFC-3082","files":{"txt":{"path":"standards/IETF/RFC-3082/RFC-3082.txt","sha256":"a84fbe4ab54b7facc4e9dcb3466a7fa6ed1bf6c9a6c87ddd928096492877b0cb"}},"tags":["nested-reference","unchanged"],"summary":"The Service Location Protocol (SLP) provides mechanisms whereby\n service agent clients can advertise and user agent clients can query\n for services. The design is very much demand-driven, so that user\n agents only obtain service information when they specifically ask for\n it. There exists another class of user agent applications, however,\n that requires notification when a new service appears or disappears.\n In the RFC 2608 design, these applications are forced to poll the\n network to catch changes. In this document, we describe a protocol\n for allowing such clients to be notified when a change occurs,\n removing the need for polling.\n\n1. Introduction\n\n The Service Location Protocol (SLP) [1] provides a mechanism for\n service agent (SA) clients to advertise network services and for user\n agent (UA) clients to find them. The mechanism is demand-driven.\n UAs obtain service information by ac","scope_keywords":["3082","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null}],"search_text":"IETF RFC 3082 The Service Location Protocol (SLP) provides mechanisms whereby\n service agent clients can advertise and user agent clients can query\n for services. The design is very much demand-driven, so that user\n agents only obtain service information when they specifically ask for\n it. There exists another class of user agent applications, however,\n that requires notification when a new service appears or disappears.\n In the RFC 2608 design, these applications are forced to poll the\n network to catch changes. In this document, we describe a protocol\n for allowing such clients to be notified when a change occurs,\n removing the need for polling.\n\n1. Introduction\n\n The Service Location Protocol (SLP) [1] provides a mechanism for\n service agent (SA) clients to advertise network services and for user\n agent (UA) clients to find them. The mechanism is demand-driven.\n UAs obtain service information by ac 3082 key nested-reference unchanged"},{"id":"IETF RFC 3114","type":"specification","body":"IETF","designation":"RFC 3114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3114.txt","https://www.rfc-editor.org/rfc/rfc3114.pdf"],"folder":"IETF/RFC-3114","files":{"txt":{"path":"standards/IETF/RFC-3114/RFC-3114.txt","sha256":"485f96289e818b5d6635e23fd2f9e53c6788feb8e5aef511814855fe62be9224"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how company security policy for data\n classification can be mapped to the S/MIME security label. Actual\n policies from three companies provide worked examples.\n\n1. Introduction\n\n Security labels are an optional security service for S/MIME. A\n security label is a set of security information regarding the\n sensitivity of the content that is protected by S/MIME encapsulation.\n A security label can be included in the signed attributes of any\n SignedData object. A security label attribute may be included in\n either the inner signature, outer signature, or both. The syntax and\n processing rules for security labels are described in RFC 2634 [ESS].\n\n The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT',\n 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this\n document are to be interpreted as described in RFC 2119 [MUSTSHOULD].","scope_keywords":["3114","algorithm","attribute","attributes","authorization","certificate","certificates","crl","key","policies","policy","profile","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 3114 This document discusses how company security policy for data\n classification can be mapped to the S/MIME security label. Actual\n policies from three companies provide worked examples.\n\n1. Introduction\n\n Security labels are an optional security service for S/MIME. A\n security label is a set of security information regarding the\n sensitivity of the content that is protected by S/MIME encapsulation.\n A security label can be included in the signed attributes of any\n SignedData object. A security label attribute may be included in\n either the inner signature, outer signature, or both. The syntax and\n processing rules for security labels are described in RFC 2634 [ESS].\n\n The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT',\n 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this\n document are to be interpreted as described in RFC 2119 [MUSTSHOULD]. 3114 algorithm attribute attributes authorization certificate certificates crl key policies policy profile signature subject nested-reference unchanged"},{"id":"IETF RFC 3125","type":"specification","body":"IETF","designation":"RFC 3125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3125.txt","https://www.rfc-editor.org/rfc/rfc3125.pdf"],"folder":"IETF/RFC-3125","files":{"txt":{"path":"standards/IETF/RFC-3125/RFC-3125.txt","sha256":"39df5ded9bde5cecb9196ef45fb97007239ce1da5c13f581b3afd1df30a4271c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines signature policies for electronic signatures. A\n signature policy is a set of rules for the creation and validation of\n an electronic signature, under which the validity of signature can be\n determined. A given legal/contractual context may recognize a\n particular signature policy as meeting its requirements.\n\n A signature policy has a globally unique reference, which is bound to\n an electronic signature by the signer as part of the signature\n calculation.\n\n The signature policy needs to be available in human readable form so\n that it can be assessed to meet the requirements of the legal and\n contractual context in which it is being applied.\n\n To allow for the automatic processing of an electronic signature\n another part of the signature policy specifies the electronic rules\n for the creation and validation of the electronic signature in a\n computer processable form","scope_keywords":["3125","algorithm","algorithms","attribute","attributes","certificate","http","identification","issuer","key","path","policies","policy","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"IETF RFC 3125 This document defines signature policies for electronic signatures. A\n signature policy is a set of rules for the creation and validation of\n an electronic signature, under which the validity of signature can be\n determined. A given legal/contractual context may recognize a\n particular signature policy as meeting its requirements.\n\n A signature policy has a globally unique reference, which is bound to\n an electronic signature by the signer as part of the signature\n calculation.\n\n The signature policy needs to be available in human readable form so\n that it can be assessed to meet the requirements of the legal and\n contractual context in which it is being applied.\n\n To allow for the automatic processing of an electronic signature\n another part of the signature policy specifies the electronic rules\n for the creation and validation of the electronic signature in a\n computer processable form 3125 algorithm algorithms attribute attributes certificate http identification issuer key path policies policy revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 3139","type":"specification","body":"IETF","designation":"RFC 3139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3139.txt","https://www.rfc-editor.org/rfc/rfc3139.pdf"],"folder":"IETF/RFC-3139","files":{"txt":{"path":"standards/IETF/RFC-3139/RFC-3139.txt","sha256":"5d780824403c1f320cf366cac920045e87af1623d2e2dcd796dad2320c84246a"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses different approaches to configure networks and\n identifies a set of configuration management requirements for IP-\n based networks.","scope_keywords":["3139","identification","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null}],"search_text":"IETF RFC 3139 This memo discusses different approaches to configure networks and\n identifies a set of configuration management requirements for IP-\n based networks. 3139 identification key management policies policy nested-reference unchanged"},{"id":"IETF RFC 3159","type":"specification","body":"IETF","designation":"RFC 3159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3159.txt","https://www.rfc-editor.org/rfc/rfc3159.pdf"],"folder":"IETF/RFC-3159","files":{"txt":{"path":"standards/IETF/RFC-3159/RFC-3159.txt","sha256":"92f64f2ca26268cddd4d2efe96098d90d3d651164c51a6b4ba753dff726a8232"}},"tags":["nested-reference","unchanged"],"summary":"This document, the Structure of Policy Provisioning Information\n (SPPI), defines the adapted subset of SNMP's Structure of Management\n Information (SMI) used to write Policy Information Base (PIB)\n modules.\n\n RFC 2748 defines the COPS protocol, and RFC 2749 describes how the\n COPS protocol is used to provide for the outsourcing of policy\n decisions for RSVP. Another usage of the COPS protocol, for the\n provisioning of policy, is introduced in RFC 3084. In this\n provisioning model, the policy information is viewed as a collection\n of Provisioning Classes (PRCs) and Provisioning Instances (PRIs)\n residing in a virtual information store, termed the Policy\n Information Base (PIB). Collections of related Provisioning Classes\n are defined in a PIB module.\n\nMcCloghrie, et al. Standards Track [Page 1]\n\f\nRFC 3159 SPPI August 2001\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NO","scope_keywords":["3159","key","management","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3444","folder":"IETF/RFC-3444","source":"IETF/RFC-3444/RFC-3444.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3159 This document, the Structure of Policy Provisioning Information\n (SPPI), defines the adapted subset of SNMP's Structure of Management\n Information (SMI) used to write Policy Information Base (PIB)\n modules.\n\n RFC 2748 defines the COPS protocol, and RFC 2749 describes how the\n COPS protocol is used to provide for the outsourcing of policy\n decisions for RSVP. Another usage of the COPS protocol, for the\n provisioning of policy, is introduced in RFC 3084. In this\n provisioning model, the policy information is viewed as a collection\n of Provisioning Classes (PRCs) and Provisioning Instances (PRIs)\n residing in a virtual information store, termed the Policy\n Information Base (PIB). Collections of related Provisioning Classes\n are defined in a PIB module.\n\nMcCloghrie, et al. Standards Track [Page 1]\n\f\nRFC 3159 SPPI August 2001\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NO 3159 key management policy subject nested-reference unchanged"},{"id":"IETF RFC 3203","type":"specification","body":"IETF","designation":"RFC 3203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3203.txt","https://www.rfc-editor.org/rfc/rfc3203.pdf"],"folder":"IETF/RFC-3203","files":{"txt":{"path":"standards/IETF/RFC-3203/RFC-3203.txt","sha256":"979728f8cb0563e764f3e5ac9dae08ad348fd6c24178eacab2e718522852d1f1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to DHCP (Dynamic Host Configuration\n Protocol) to allow dynamic reconfiguration of a single host triggered\n by the DHCP server (e.g., a new IP address and/or local configuration\n parameters). This is achieved by introducing a unicast FORCERENEW\n message which forces the client to the RENEW state. The behaviour\n for hosts using the DHCP INFORM message to obtain configuration\n information is also described.\n\n1. Introduction\n\n The procedures as described within this document allow the dynamic\n reconfiguration of individual hosts.","scope_keywords":["3203","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 3203 This document defines extensions to DHCP (Dynamic Host Configuration\n Protocol) to allow dynamic reconfiguration of a single host triggered\n by the DHCP server (e.g., a new IP address and/or local configuration\n parameters). This is achieved by introducing a unicast FORCERENEW\n message which forces the client to the RENEW state. The behaviour\n for hosts using the DHCP INFORM message to obtain configuration\n information is also described.\n\n1. Introduction\n\n The procedures as described within this document allow the dynamic\n reconfiguration of individual hosts. 3203 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3211","type":"specification","body":"IETF","designation":"RFC 3211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3211.txt","https://www.rfc-editor.org/rfc/rfc3211.pdf"],"folder":"IETF/RFC-3211","files":{"txt":{"path":"standards/IETF/RFC-3211/RFC-3211.txt","sha256":"747fb5f1e07c87a28b15a3e4b5803b6b47872864d0ee02d075b03b52440cc6a8"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a method of encrypting data using user-\n supplied passwords and, by extension, any form of variable-length\n keying material which is not necessarily an algorithm-specific\n fixed-format key. The Cryptographic Message Syntax data format does\n not currently contain any provisions for password-based data\n encryption.\n\n1. Introduction\n\n This document describes a password-based content encryption mechanism\n for CMS. This is implemented as a new RecipientInfo type and is an\n extension to the RecipientInfo types currently defined in RFC 2630.\n\n The format of the messages are described in ASN.1 [ASN1].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document are to be\n interpreted as described in RFC 2119.\n\nGutmann Standards Track [Page 1]\n\f\nRFC 3211 Password-based Encryption for CMS December 2001","scope_keywords":["3211","algorithm","algorithms","encryption","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3852","folder":"IETF/RFC-3852","source":"IETF/RFC-3852/RFC-3852.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3962","folder":"IETF/RFC-3962","source":"IETF/RFC-3962/RFC-3962.txt","version":null},{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null}],"search_text":"IETF RFC 3211 This document provides a method of encrypting data using user-\n supplied passwords and, by extension, any form of variable-length\n keying material which is not necessarily an algorithm-specific\n fixed-format key. The Cryptographic Message Syntax data format does\n not currently contain any provisions for password-based data\n encryption.\n\n1. Introduction\n\n This document describes a password-based content encryption mechanism\n for CMS. This is implemented as a new RecipientInfo type and is an\n extension to the RecipientInfo types currently defined in RFC 2630.\n\n The format of the messages are described in ASN.1 [ASN1].\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document are to be\n interpreted as described in RFC 2119.\n\nGutmann Standards Track [Page 1]\n\f\nRFC 3211 Password-based Encryption for CMS December 2001 3211 algorithm algorithms encryption identification key nested-reference unchanged"},{"id":"IETF RFC 3212","type":"specification","body":"IETF","designation":"RFC 3212","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3212.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3212.txt","https://www.rfc-editor.org/rfc/rfc3212.pdf"],"folder":"IETF/RFC-3212","files":{"txt":{"path":"standards/IETF/RFC-3212/RFC-3212.txt","sha256":"aae468e0212b1be85bbcec7c8bfc23aa839cf1d640434a94d6a2df3e2c5e6ddb"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies mechanisms and TLVs (Type/Length/Value) for\n support of CR-LSPs (constraint-based routed Label Switched Path)\n using LDP (Label Distribution Protocol).\n\n This specification proposes an end-to-end setup mechanism of a CR-LSP\n initiated by the ingress LSR (Label Switching Router). We also\n specify mechanisms to provide means for reservation of resources\n using LDP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\nJamoussi, et al. Standards Track [Page 1]\n\f\nRFC 3212 Constraint-Based LSP Setup using LDP January 2002","scope_keywords":["3212","key","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3215","folder":"IETF/RFC-3215","source":"IETF/RFC-3215/RFC-3215.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3469","folder":"IETF/RFC-3469","source":"IETF/RFC-3469/RFC-3469.txt","version":null},{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3472","folder":"IETF/RFC-3472","source":"IETF/RFC-3472/RFC-3472.txt","version":null},{"body":"IETF","designation":"RFC 3479","folder":"IETF/RFC-3479","source":"IETF/RFC-3479/RFC-3479.txt","version":null},{"body":"IETF","designation":"RFC 3480","folder":"IETF/RFC-3480","source":"IETF/RFC-3480/RFC-3480.txt","version":null},{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 3811","folder":"IETF/RFC-3811","source":"IETF/RFC-3811/RFC-3811.txt","version":null},{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 3970","folder":"IETF/RFC-3970","source":"IETF/RFC-3970/RFC-3970.txt","version":null},{"body":"IETF","designation":"RFC 3988","folder":"IETF/RFC-3988","source":"IETF/RFC-3988/RFC-3988.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5036","folder":"IETF/RFC-5036","source":"IETF/RFC-5036/RFC-5036.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null}],"search_text":"IETF RFC 3212 This document specifies mechanisms and TLVs (Type/Length/Value) for\n support of CR-LSPs (constraint-based routed Label Switched Path)\n using LDP (Label Distribution Protocol).\n\n This specification proposes an end-to-end setup mechanism of a CR-LSP\n initiated by the ingress LSR (Label Switching Router). We also\n specify mechanisms to provide means for reservation of resources\n using LDP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [6].\n\nJamoussi, et al. Standards Track [Page 1]\n\f\nRFC 3212 Constraint-Based LSP Setup using LDP January 2002 3212 key path pid nested-reference unchanged"},{"id":"IETF RFC 3246","type":"specification","body":"IETF","designation":"RFC 3246","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3246.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3246.txt","https://www.rfc-editor.org/rfc/rfc3246.pdf"],"folder":"IETF/RFC-3246","files":{"txt":{"path":"standards/IETF/RFC-3246/RFC-3246.txt","sha256":"4b831d41bfd526276c5d2a51da0225d560d8efe35b78d52c836526fe3e84aa3d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a PHB (per-hop behavior) called Expedited\n Forwarding (EF). The PHB is a basic building block in the\n Differentiated Services architecture. EF is intended to provide a\n building block for low delay, low jitter and low loss services by\n ensuring that the EF aggregate is served at a certain configured\n rate. This document obsoletes RFC 2598.\n\nDavie, et. al. Standards Track [Page 1]\n\f\nRFC 3246 An Expedited Forwarding PHB March 2002","scope_keywords":["3246","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3247","folder":"IETF/RFC-3247","source":"IETF/RFC-3247/RFC-3247.txt","version":null},{"body":"IETF","designation":"RFC 3248","folder":"IETF/RFC-3248","source":"IETF/RFC-3248/RFC-3248.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5416","folder":"IETF/RFC-5416","source":"IETF/RFC-5416/RFC-5416.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 3246 This document defines a PHB (per-hop behavior) called Expedited\n Forwarding (EF). The PHB is a basic building block in the\n Differentiated Services architecture. EF is intended to provide a\n building block for low delay, low jitter and low loss services by\n ensuring that the EF aggregate is served at a certain configured\n rate. This document obsoletes RFC 2598.\n\nDavie, et. al. Standards Track [Page 1]\n\f\nRFC 3246 An Expedited Forwarding PHB March 2002 3246 key nested-reference unchanged"},{"id":"IETF RFC 3247","type":"specification","body":"IETF","designation":"RFC 3247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3247.txt","https://www.rfc-editor.org/rfc/rfc3247.pdf"],"folder":"IETF/RFC-3247","files":{"txt":{"path":"standards/IETF/RFC-3247/RFC-3247.txt","sha256":"620955bc74eaf28e38089462a7fa8a68fd98781e4891380939b8e298e8dd2d22"}},"tags":["nested-reference","unchanged"],"summary":"This document was written during the process of clarification of\n RFC2598 \"An Expedited Forwarding PHB\" that led to the publication of\n revised specification of EF \"An Expedited Forwarding PHB\". Its\n primary motivation is providing additional explanation to the revised\n EF definition and its properties. The document also provides\n additional implementation examples and gives some guidance for\n computation of the numerical parameters of the new definition for\n several well known schedulers and router architectures.\n\nCharny, et. al. Informational [Page 1]\n\f\nRFC 3247 Supplemental Information March 2002","scope_keywords":["3247"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 5865","folder":"IETF/RFC-5865","source":"IETF/RFC-5865/RFC-5865.txt","version":null}],"search_text":"IETF RFC 3247 This document was written during the process of clarification of\n RFC2598 \"An Expedited Forwarding PHB\" that led to the publication of\n revised specification of EF \"An Expedited Forwarding PHB\". Its\n primary motivation is providing additional explanation to the revised\n EF definition and its properties. The document also provides\n additional implementation examples and gives some guidance for\n computation of the numerical parameters of the new definition for\n several well known schedulers and router architectures.\n\nCharny, et. al. Informational [Page 1]\n\f\nRFC 3247 Supplemental Information March 2002 3247 nested-reference unchanged"},{"id":"IETF RFC 3248","type":"specification","body":"IETF","designation":"RFC 3248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3248.txt","https://www.rfc-editor.org/rfc/rfc3248.pdf"],"folder":"IETF/RFC-3248","files":{"txt":{"path":"standards/IETF/RFC-3248/RFC-3248.txt","sha256":"96382e27479d3a231c2113b7943e6b3e846dd28ff4cdd491db618657d2b03688"}},"tags":["nested-reference","unchanged"],"summary":"For historical interest, this document captures the EF Design Team's\n proposed solution, preferred by the original authors of RFC 2598 but\n not adopted by the working group in December 2000. The original\n definition of EF was based on comparison of forwarding on an unloaded\n network. This experimental Delay Bound (DB) PHB requires a bound on\n the delay of packets due to other traffic in the network. At the\n Pittsburgh IETF meeting in August 2000, the Differentiated Services\n working group faced serious questions regarding RFC 2598 - the\n group's standards track definition of the Expedited Forwarding (EF)\n Per Hop Behavior (PHB). An 'EF Design Team' volunteered to develop a\n re-expression of RFC 2598, bearing in mind the issues raised in the\n DiffServ group. At the San Diego IETF meeting in December 2000 the\n DiffServ working group decided to pursue an alternative re-expression\n of the EF","scope_keywords":["3248","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null}],"search_text":"IETF RFC 3248 For historical interest, this document captures the EF Design Team's\n proposed solution, preferred by the original authors of RFC 2598 but\n not adopted by the working group in December 2000. The original\n definition of EF was based on comparison of forwarding on an unloaded\n network. This experimental Delay Bound (DB) PHB requires a bound on\n the delay of packets due to other traffic in the network. At the\n Pittsburgh IETF meeting in August 2000, the Differentiated Services\n working group faced serious questions regarding RFC 2598 - the\n group's standards track definition of the Expedited Forwarding (EF)\n Per Hop Behavior (PHB). An 'EF Design Team' volunteered to develop a\n re-expression of RFC 2598, bearing in mind the issues raised in the\n DiffServ group. At the San Diego IETF meeting in December 2000 the\n DiffServ working group decided to pursue an alternative re-expression\n of the EF 3248 key nested-reference unchanged"},{"id":"IETF RFC 3262","type":"specification","body":"IETF","designation":"RFC 3262","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3262.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3262.txt","https://www.rfc-editor.org/rfc/rfc3262.pdf"],"folder":"IETF/RFC-3262","files":{"txt":{"path":"standards/IETF/RFC-3262/RFC-3262.txt","sha256":"4ecf9bc1141480cf800e15e7c2833e20d7fefca6743743dd8150c0768cd56e98"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the Session Initiation\n Protocol (SIP) providing reliable provisional response messages.\n This extension uses the option tag 100rel and defines the Provisional\n Response ACKnowledgement (PRACK) method.","scope_keywords":["3262","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3311","folder":"IETF/RFC-3311","source":"IETF/RFC-3311/RFC-3311.txt","version":null},{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4367","folder":"IETF/RFC-4367","source":"IETF/RFC-4367/RFC-4367.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null}],"search_text":"IETF RFC 3262 This document specifies an extension to the Session Initiation\n Protocol (SIP) providing reliable provisional response messages.\n This extension uses the option tag 100rel and defines the Provisional\n Response ACKnowledgement (PRACK) method. 3262 key nested-reference unchanged"},{"id":"IETF RFC 3263","type":"specification","body":"IETF","designation":"RFC 3263","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3263.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3263.txt","https://www.rfc-editor.org/rfc/rfc3263.pdf"],"folder":"IETF/RFC-3263","files":{"txt":{"path":"standards/IETF/RFC-3263/RFC-3263.txt","sha256":"b917d62e9421299bed19de42f8260531232006b3b4f792ba7ee2b5035e5d2a65"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) uses DNS procedures to allow a\n client to resolve a SIP Uniform Resource Identifier (URI) into the IP\n address, port, and transport protocol of the next hop to contact. It\n also uses DNS to allow a server to send a response to a backup client\n if the primary client has failed. This document describes those DNS\n procedures in detail.","scope_keywords":["3263","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3319","folder":"IETF/RFC-3319","source":"IETF/RFC-3319/RFC-3319.txt","version":null},{"body":"IETF","designation":"RFC 3329","folder":"IETF/RFC-3329","source":"IETF/RFC-3329/RFC-3329.txt","version":null},{"body":"IETF","designation":"RFC 3361","folder":"IETF/RFC-3361","source":"IETF/RFC-3361/RFC-3361.txt","version":null},{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4320","folder":"IETF/RFC-4320","source":"IETF/RFC-4320/RFC-4320.txt","version":null},{"body":"IETF","designation":"RFC 4321","folder":"IETF/RFC-4321","source":"IETF/RFC-4321/RFC-4321.txt","version":null},{"body":"IETF","designation":"RFC 4453","folder":"IETF/RFC-4453","source":"IETF/RFC-4453/RFC-4453.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 3263 The Session Initiation Protocol (SIP) uses DNS procedures to allow a\n client to resolve a SIP Uniform Resource Identifier (URI) into the IP\n address, port, and transport protocol of the next hop to contact. It\n also uses DNS to allow a server to send a response to a backup client\n if the primary client has failed. This document describes those DNS\n procedures in detail. 3263 management tls nested-reference unchanged"},{"id":"IETF RFC 3265","type":"specification","body":"IETF","designation":"RFC 3265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3265.txt","https://www.rfc-editor.org/rfc/rfc3265.pdf"],"folder":"IETF/RFC-3265","files":{"txt":{"path":"standards/IETF/RFC-3265/RFC-3265.txt","sha256":"b830d3f3d8612d26fa81502fa6b8597eadb6d456e077baae5128ece2f318b1c5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the Session Initiation\n Protocol (SIP). The purpose of this extension is to provide an\n extensible framework by which SIP nodes can request notification from\n remote nodes indicating that certain events have occurred.\n\n Concrete uses of the mechanism described in this document may be\n standardized in the future.\n\n Note that the event notification mechanisms defined herein are NOT\n intended to be a general-purpose infrastructure for all classes of\n event subscription and notification.","scope_keywords":["3265","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3311","folder":"IETF/RFC-3311","source":"IETF/RFC-3311/RFC-3311.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3420","folder":"IETF/RFC-3420","source":"IETF/RFC-3420/RFC-3420.txt","version":null},{"body":"IETF","designation":"RFC 3427","folder":"IETF/RFC-3427","source":"IETF/RFC-3427/RFC-3427.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3515","folder":"IETF/RFC-3515","source":"IETF/RFC-3515/RFC-3515.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3857","folder":"IETF/RFC-3857","source":"IETF/RFC-3857/RFC-3857.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4453","folder":"IETF/RFC-4453","source":"IETF/RFC-4453/RFC-4453.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4488","folder":"IETF/RFC-4488","source":"IETF/RFC-4488/RFC-4488.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 3265 This document describes an extension to the Session Initiation\n Protocol (SIP). The purpose of this extension is to provide an\n extensible framework by which SIP nodes can request notification from\n remote nodes indicating that certain events have occurred.\n\n Concrete uses of the mechanism described in this document may be\n standardized in the future.\n\n Note that the event notification mechanisms defined herein are NOT\n intended to be a general-purpose infrastructure for all classes of\n event subscription and notification. 3265 identification nested-reference unchanged"},{"id":"IETF RFC 3269","type":"specification","body":"IETF","designation":"RFC 3269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3269.txt","https://www.rfc-editor.org/rfc/rfc3269.pdf"],"folder":"IETF/RFC-3269","files":{"txt":{"path":"standards/IETF/RFC-3269/RFC-3269.txt","sha256":"5e11d255cfab390a25292c0b47921109513713037d7de0c35e1db70f6116fc66"}},"tags":["nested-reference","unchanged"],"summary":"This document provides general guidelines to assist the authors of\n Reliable Multicast Transport (RMT) building block and protocol\n instantiation definitions. The purpose of these guidelines is to\n ensure that any building block and protocol instantiation definitions\n produced contain sufficient information to fully explain their\n operation and use. In addition these guidelines provide directions\n to specify modular and clearly defined RMT building blocks and\n protocol instantiations that can be refined and augmented to safely\n create new protocols for use in new scenarios for which any existing\n protocols were not designed.","scope_keywords":["3269","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3369","folder":"IETF/RFC-3369","source":"IETF/RFC-3369/RFC-3369.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 3941","folder":"IETF/RFC-3941","source":"IETF/RFC-3941/RFC-3941.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null}],"search_text":"IETF RFC 3269 This document provides general guidelines to assist the authors of\n Reliable Multicast Transport (RMT) building block and protocol\n instantiation definitions. The purpose of these guidelines is to\n ensure that any building block and protocol instantiation definitions\n produced contain sufficient information to fully explain their\n operation and use. In addition these guidelines provide directions\n to specify modular and clearly defined RMT building blocks and\n protocol instantiations that can be refined and augmented to safely\n create new protocols for use in new scenarios for which any existing\n protocols were not designed. 3269 key risk nested-reference unchanged"},{"id":"IETF RFC 3311","type":"specification","body":"IETF","designation":"RFC 3311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3311.txt","https://www.rfc-editor.org/rfc/rfc3311.pdf"],"folder":"IETF/RFC-3311","files":{"txt":{"path":"standards/IETF/RFC-3311/RFC-3311.txt","sha256":"e0e3f5dce4c2163ad3c31a00f03c3e9596b9dca988b4eff7269994203ea50f8c"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the new UPDATE method for the Session\n Initiation Protocol (SIP). UPDATE allows a client to update\n parameters of a session (such as the set of media streams and their\n codecs) but has no impact on the state of a dialog. In that sense,\n it is like a re-INVITE, but unlike re-INVITE, it can be sent before\n the initial INVITE has been completed. This makes it very useful for\n updating session parameters within early dialogs.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 3311 SIP UPDATE Method September 2002","scope_keywords":["3311","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3312","folder":"IETF/RFC-3312","source":"IETF/RFC-3312/RFC-3312.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 4028","folder":"IETF/RFC-4028","source":"IETF/RFC-4028/RFC-4028.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null}],"search_text":"IETF RFC 3311 This specification defines the new UPDATE method for the Session\n Initiation Protocol (SIP). UPDATE allows a client to update\n parameters of a session (such as the set of media streams and their\n codecs) but has no impact on the state of a dialog. In that sense,\n it is like a re-INVITE, but unlike re-INVITE, it can be sent before\n the initial INVITE has been completed. This makes it very useful for\n updating session parameters within early dialogs.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 3311 SIP UPDATE Method September 2002 3311 key nested-reference unchanged"},{"id":"IETF RFC 3325","type":"specification","body":"IETF","designation":"RFC 3325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3325.txt","https://www.rfc-editor.org/rfc/rfc3325.pdf"],"folder":"IETF/RFC-3325","files":{"txt":{"path":"standards/IETF/RFC-3325/RFC-3325.txt","sha256":"a69dedf5135c95524e5db84ad39957e6a78ac3c861a018f4f0ec3b07504374a9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes private extensions to the Session Initiation\n Protocol (SIP) that enable a network of trusted SIP servers to assert\n the identity of authenticated users, and the application of existing\n privacy mechanisms to the identity problem. The use of these\n extensions is only applicable inside an administrative domain with\n previously agreed-upon policies for generation, transport and usage\n of such information. This document does NOT offer a general privacy\n or identity model suitable for use between different trust domains,\n or use in the Internet at large.","scope_keywords":["3325","authentication","key","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 3325 This document describes private extensions to the Session Initiation\n Protocol (SIP) that enable a network of trusted SIP servers to assert\n the identity of authenticated users, and the application of existing\n privacy mechanisms to the identity problem. The use of these\n extensions is only applicable inside an administrative domain with\n previously agreed-upon policies for generation, transport and usage\n of such information. This document does NOT offer a general privacy\n or identity model suitable for use between different trust domains,\n or use in the Internet at large. 3325 authentication key policies subject trust nested-reference unchanged"},{"id":"IETF RFC 3326","type":"specification","body":"IETF","designation":"RFC 3326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3326.txt","https://www.rfc-editor.org/rfc/rfc3326.pdf"],"folder":"IETF/RFC-3326","files":{"txt":{"path":"standards/IETF/RFC-3326/RFC-3326.txt","sha256":"74fe14bdb6f55642c2033094b7c9719831952d5a4a825258f3f9fb246a24d318"}},"tags":["nested-reference","unchanged"],"summary":"For creating services, it is often useful to know why a Session\n Initiation Protocol (SIP) request was issued. This document defines\n a header field, Reason, that provides this information. The Reason\n header field is also intended to be used to encapsulate a final\n status code in a provisional response. This functionality is needed\n to resolve the \"Heterogeneous Error Response Forking Problem\", or\n HERFP.\n\nSchulzrinne, et. al. Standards Track [Page 1]\n\f\nRFC 3326 The Reason Header Field for SIP December 2002","scope_keywords":["3326","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3725","folder":"IETF/RFC-3725","source":"IETF/RFC-3725/RFC-3725.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null}],"search_text":"IETF RFC 3326 For creating services, it is often useful to know why a Session\n Initiation Protocol (SIP) request was issued. This document defines\n a header field, Reason, that provides this information. The Reason\n header field is also intended to be used to encapsulate a final\n status code in a provisional response. This functionality is needed\n to resolve the \"Heterogeneous Error Response Forking Problem\", or\n HERFP.\n\nSchulzrinne, et. al. Standards Track [Page 1]\n\f\nRFC 3326 The Reason Header Field for SIP December 2002 3326 key presentation nested-reference unchanged"},{"id":"IETF RFC 3329","type":"specification","body":"IETF","designation":"RFC 3329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3329.txt","https://www.rfc-editor.org/rfc/rfc3329.pdf"],"folder":"IETF/RFC-3329","files":{"txt":{"path":"standards/IETF/RFC-3329/RFC-3329.txt","sha256":"63e4de0f309400e2dbd98c908ccf2ee8c16a75b0a6371bba5268343b2f41c10b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new functionality for negotiating the security\n mechanisms used between a Session Initiation Protocol (SIP) user\n agent and its next-hop SIP entity. This new functionality\n supplements the existing methods of choosing security mechanisms\n between SIP entities.","scope_keywords":["3329","algorithm","algorithms","authentication","hash","key","keys","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3329 This document defines new functionality for negotiating the security\n mechanisms used between a Session Initiation Protocol (SIP) user\n agent and its next-hop SIP entity. This new functionality\n supplements the existing methods of choosing security mechanisms\n between SIP entities. 3329 algorithm algorithms authentication hash key keys policies nested-reference unchanged"},{"id":"IETF RFC 3338","type":"specification","body":"IETF","designation":"RFC 3338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3338.txt","https://www.rfc-editor.org/rfc/rfc3338.pdf"],"folder":"IETF/RFC-3338","files":{"txt":{"path":"standards/IETF/RFC-3338/RFC-3338.txt","sha256":"c531279401c5dd207ffdd24f4afa2c3fd106413d25eaec4e6d30503033cff94f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism of dual stack hosts using a\n technique called \"Bump-in-the-API\"(BIA) which allows for the hosts to\n communicate with other IPv6 hosts using existing IPv4 applications.\n The goal of this mechanism is the same as that of the Bump-in-the-\n stack mechanism, but this mechanism provides the translation method\n between the IPv4 APIs and IPv6 APIs. Thus, the goal is simply\n achieved without IP header translation.\n\nLee, et al. Experimental [Page 1]\n\f\nRFC 3338 Dual Stack Hosts Using BIA October 2002","scope_keywords":["3338","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null}],"search_text":"IETF RFC 3338 This document specifies a mechanism of dual stack hosts using a\n technique called \"Bump-in-the-API\"(BIA) which allows for the hosts to\n communicate with other IPv6 hosts using existing IPv4 applications.\n The goal of this mechanism is the same as that of the Bump-in-the-\n stack mechanism, but this mechanism provides the translation method\n between the IPv4 APIs and IPv6 APIs. Thus, the goal is simply\n achieved without IP header translation.\n\nLee, et al. Experimental [Page 1]\n\f\nRFC 3338 Dual Stack Hosts Using BIA October 2002 3338 key nested-reference unchanged"},{"id":"IETF RFC 3351","type":"specification","body":"IETF","designation":"RFC 3351","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3351.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3351.txt","https://www.rfc-editor.org/rfc/rfc3351.pdf"],"folder":"IETF/RFC-3351","files":{"txt":{"path":"standards/IETF/RFC-3351/RFC-3351.txt","sha256":"a42ac6993f8235c8cc220d4d5e79840f08cdd9e5a96040cd988c5e9b3b0b2ec4"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of Session Initiation Protocol\n (SIP) user requirements that support communications for deaf, hard of\n hearing and speech-impaired individuals. These user requirements\n address the current difficulties of deaf, hard of hearing and\n speech-impaired individuals in using communications facilities, while\n acknowledging the multi-functional potential of SIP-based\n communications.\n\n A number of issues related to these user requirements are further\n raised in this document.\n\n Also included are some real world scenarios and some technical\n requirements to show the robustness of these requirements on a\n concept-level.\n\nCharlton, et al. Informational [Page 1]\n\f\nRFC 3351 SIP for Deaf, Hard of Hearing and Speech Impaired August 2002","scope_keywords":["3351","key","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null}],"search_text":"IETF RFC 3351 This document presents a set of Session Initiation Protocol\n (SIP) user requirements that support communications for deaf, hard of\n hearing and speech-impaired individuals. These user requirements\n address the current difficulties of deaf, hard of hearing and\n speech-impaired individuals in using communications facilities, while\n acknowledging the multi-functional potential of SIP-based\n communications.\n\n A number of issues related to these user requirements are further\n raised in this document.\n\n Also included are some real world scenarios and some technical\n requirements to show the robustness of these requirements on a\n concept-level.\n\nCharlton, et al. Informational [Page 1]\n\f\nRFC 3351 SIP for Deaf, Hard of Hearing and Speech Impaired August 2002 3351 key management profile nested-reference unchanged"},{"id":"IETF RFC 3357","type":"specification","body":"IETF","designation":"RFC 3357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3357.txt","https://www.rfc-editor.org/rfc/rfc3357.pdf"],"folder":"IETF/RFC-3357","files":{"txt":{"path":"standards/IETF/RFC-3357/RFC-3357.txt","sha256":"ca0fa92b68a87cd7e71cca5de232282ccee9b4f155befa3d8ff91b1a89761c79"}},"tags":["nested-reference","unchanged"],"summary":"Using the base loss metric defined in RFC 2680, this document defines\n two derived metrics \"loss distance\" and \"loss period\", and the\n associated statistics that together capture loss patterns experienced\n by packet streams on the Internet. The Internet exhibits certain\n specific types of behavior (e.g., bursty packet loss) that can affect\n the performance seen by the users as well as the operators. The loss\n pattern or loss distribution is a key parameter that determines the\n performance observed by the users for certain real-time applications\n such as packet voice and video. For the same loss rate, two\n different loss distributions could potentially produce widely\n different perceptions of performance.\n\nKoodli & Ravikanth Informational [Page 1]\n\f\nRFC 3357 One-way Loss Pattern Sample Metrics August 2002","scope_keywords":["3357","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4148","folder":"IETF/RFC-4148","source":"IETF/RFC-4148/RFC-4148.txt","version":null},{"body":"IETF","designation":"RFC 5166","folder":"IETF/RFC-5166","source":"IETF/RFC-5166/RFC-5166.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null}],"search_text":"IETF RFC 3357 Using the base loss metric defined in RFC 2680, this document defines\n two derived metrics \"loss distance\" and \"loss period\", and the\n associated statistics that together capture loss patterns experienced\n by packet streams on the Internet. The Internet exhibits certain\n specific types of behavior (e.g., bursty packet loss) that can affect\n the performance seen by the users as well as the operators. The loss\n pattern or loss distribution is a key parameter that determines the\n performance observed by the users for certain real-time applications\n such as packet voice and video. For the same loss rate, two\n different loss distributions could potentially produce widely\n different perceptions of performance.\n\nKoodli & Ravikanth Informational [Page 1]\n\f\nRFC 3357 One-way Loss Pattern Sample Metrics August 2002 3357 key nested-reference unchanged"},{"id":"IETF RFC 3365","type":"specification","body":"IETF","designation":"RFC 3365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3365.txt","https://www.rfc-editor.org/rfc/rfc3365.pdf"],"folder":"IETF/RFC-3365","files":{"txt":{"path":"standards/IETF/RFC-3365/RFC-3365.txt","sha256":"a16380cfe67e137e61a233088e36ee303def48e26f26e1e8ff2ba511afcb2b0a"}},"tags":["nested-reference","unchanged"],"summary":"It is the consensus of the IETF that IETF standard protocols MUST\n make use of appropriate strong security mechanisms. This document\n describes the history and rationale for this doctrine and establishes\n this doctrine as a best current practice.","scope_keywords":["3365","authentication","encryption","policies","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5713","folder":"IETF/RFC-5713","source":"IETF/RFC-5713/RFC-5713.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null}],"search_text":"IETF RFC 3365 It is the consensus of the IETF that IETF standard protocols MUST\n make use of appropriate strong security mechanisms. This document\n describes the history and rationale for this doctrine and establishes\n this doctrine as a best current practice. 3365 authentication encryption policies tls nested-reference unchanged"},{"id":"IETF RFC 3368","type":"specification","body":"IETF","designation":"RFC 3368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3368.txt","https://www.rfc-editor.org/rfc/rfc3368.pdf"],"folder":"IETF/RFC-3368","files":{"txt":{"path":"standards/IETF/RFC-3368/RFC-3368.txt","sha256":"82f1c5048535364a7035a6291ee467ef282bb0456ea14720bf00f5e4617cb19d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a URI scheme, 'go:' to be used with the Common\n Name Resolution Protocol. Specifically it lays out the syntactic\n components and how those components are used by URI Resolution to\n find the available transports for a CNRP service. Care should be\n taken with several of the URI components because, while they may look\n like components found in other URI schemes, they often do not act\n like them. The \"go\" scheme has more in common with the location\n independent \"news\" scheme than any other URI scheme.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3368 CNRP URI Specification August 2002","scope_keywords":["3368","attribute","http","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null}],"search_text":"IETF RFC 3368 This document defines a URI scheme, 'go:' to be used with the Common\n Name Resolution Protocol. Specifically it lays out the syntactic\n components and how those components are used by URI Resolution to\n find the available transports for a CNRP service. Care should be\n taken with several of the URI components because, while they may look\n like components found in other URI schemes, they often do not act\n like them. The \"go\" scheme has more in common with the location\n independent \"news\" scheme than any other URI scheme.\n\nMealling Standards Track [Page 1]\n\f\nRFC 3368 CNRP URI Specification August 2002 3368 attribute http key presentation nested-reference unchanged"},{"id":"IETF RFC 3379","type":"specification","body":"IETF","designation":"RFC 3379","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3379.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3379.txt","https://www.rfc-editor.org/rfc/rfc3379.pdf"],"folder":"IETF/RFC-3379","files":{"txt":{"path":"standards/IETF/RFC-3379/RFC-3379.txt","sha256":"7215d0aa48654b7e8b280f407285ec6b29d762772e07fd5afb0f2661138124bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements for Delegated Path\n Validation (DPV) and Delegated Path Discovery (DPD) for Public Key\n Certificates. It also specifies the requirements for DPV and DPD\n policy management.\n\n1. Introduction\n\n This document specifies the requirements for Delegated Path\n Validation (DPV) and Delegated Path Discovery (DPD) for Public Key\n Certificates, using two main request/response pairs.\n\n Delegated processing provides two primary services: DPV and DPD.\n Some clients require a server to perform certification path\n validation and have no need for data acquisition, while some other\n clients require only path discovery in support of local path\n validation.\n\n The DPV request/response pair, can be used to fully delegate path\n validation processing to an DPV server, according to a set of rules,\n called a validation policy.\n\n The DPD request/response pair can be used to ","scope_keywords":["3379","certificate","certificates","crl","http","key","management","ocsp","path","pki","policies","policy","revocation","signature","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null}],"search_text":"IETF RFC 3379 This document specifies the requirements for Delegated Path\n Validation (DPV) and Delegated Path Discovery (DPD) for Public Key\n Certificates. It also specifies the requirements for DPV and DPD\n policy management.\n\n1. Introduction\n\n This document specifies the requirements for Delegated Path\n Validation (DPV) and Delegated Path Discovery (DPD) for Public Key\n Certificates, using two main request/response pairs.\n\n Delegated processing provides two primary services: DPV and DPD.\n Some clients require a server to perform certification path\n validation and have no need for data acquisition, while some other\n clients require only path discovery in support of local path\n validation.\n\n The DPV request/response pair, can be used to fully delegate path\n validation processing to an DPV server, according to a set of rules,\n called a validation policy.\n\n The DPD request/response pair can be used to  3379 certificate certificates crl http key management ocsp path pki policies policy revocation signature trust validation nested-reference unchanged"},{"id":"IETF RFC 3396","type":"specification","body":"IETF","designation":"RFC 3396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3396.txt","https://www.rfc-editor.org/rfc/rfc3396.pdf"],"folder":"IETF/RFC-3396","files":{"txt":{"path":"standards/IETF/RFC-3396/RFC-3396.txt","sha256":"1093f376d3937e151cda05567f3b60ce29487c4c010ad77483001e70bfa49623"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the processing rules for Dynamic Host\n Configuration Protocol (DHCPv4) options that appear multiple times in\n the same message. Multiple instances of the same option are\n generated when an option exceeds 255 octets in size (the maximum size\n of a single option) or when an option needs to be split apart in\n order to take advantage of DHCP option overloading. When multiple\n instances of the same option appear in the options, file and/or sname\n fields in a DHCP packet, the contents of these options are\n concatenated together to form a single option prior to processing.\n\n1. Introduction\n\n This document updates RFC 2131 [3] by clarifying the rules for option\n concatenation specified in section 4.1. It is expected that the\n reader will be familiar with this portion of RFC 2131. The text in\n section 4.1 that reads \"Options may appear only once, unless\n otherwise specifie","scope_keywords":["3396","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3397","folder":"IETF/RFC-3397","source":"IETF/RFC-3397/RFC-3397.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 4280","folder":"IETF/RFC-4280","source":"IETF/RFC-4280/RFC-4280.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 7291","folder":"IETF/RFC-7291","source":"IETF/RFC-7291/RFC-7291.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 3396 This document specifies the processing rules for Dynamic Host\n Configuration Protocol (DHCPv4) options that appear multiple times in\n the same message. Multiple instances of the same option are\n generated when an option exceeds 255 octets in size (the maximum size\n of a single option) or when an option needs to be split apart in\n order to take advantage of DHCP option overloading. When multiple\n instances of the same option appear in the options, file and/or sname\n fields in a DHCP packet, the contents of these options are\n concatenated together to form a single option prior to processing.\n\n1. Introduction\n\n This document updates RFC 2131 [3] by clarifying the rules for option\n concatenation specified in section 4.1. It is expected that the\n reader will be familiar with this portion of RFC 2131. The text in\n section 4.1 that reads \"Options may appear only once, unless\n otherwise specifie 3396 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3408","type":"specification","body":"IETF","designation":"RFC 3408","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3408.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3408.txt","https://www.rfc-editor.org/rfc/rfc3408.pdf"],"folder":"IETF/RFC-3408","files":{"txt":{"path":"standards/IETF/RFC-3408/RFC-3408.txt","sha256":"1b0cb41a19c4284e361b6b3e1af9470cb5791c870c6dff974bbe26eeeb47b97b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an additional mode of the link-layer assisted\n RObust Header Compression (ROHC) profile, also known as the zero-byte\n profile, beyond the two defined in RFC 3242. Zero-byte header\n compression exists in order to prevent the single-octet ROHC header\n from pushing a packet voice stream into the next higher fixed packet\n size for the radio. It is usable in certain widely deployed older\n air interfaces. This document adds the zero-byte operation for ROHC\n Bidirectional Reliable mode (R-mode) to the ones specified for\n Unidirectional (U-mode) and Bidirectional Optimistic (O-mode) modes\n of header compression in RFC 3242.\n\n1. Introduction\n\n [RFC3242] defines a zero-byte solution for compression of IP/UDP/RTP\n packets only for Unidirectional (U-) and Bidirectional Optimistic\n (O-) modes [RFC3095]. The present specification extends the profile\n defined in [RFC3242] to provi","scope_keywords":["3408","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 3408 This document defines an additional mode of the link-layer assisted\n RObust Header Compression (ROHC) profile, also known as the zero-byte\n profile, beyond the two defined in RFC 3242. Zero-byte header\n compression exists in order to prevent the single-octet ROHC header\n from pushing a packet voice stream into the next higher fixed packet\n size for the radio. It is usable in certain widely deployed older\n air interfaces. This document adds the zero-byte operation for ROHC\n Bidirectional Reliable mode (R-mode) to the ones specified for\n Unidirectional (U-mode) and Bidirectional Optimistic (O-mode) modes\n of header compression in RFC 3242.\n\n1. Introduction\n\n [RFC3242] defines a zero-byte solution for compression of IP/UDP/RTP\n packets only for Unidirectional (U-) and Bidirectional Optimistic\n (O-) modes [RFC3095]. The present specification extends the profile\n defined in [RFC3242] to provi 3408 key profile nested-reference unchanged"},{"id":"IETF RFC 3419","type":"specification","body":"IETF","designation":"RFC 3419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3419.txt","https://www.rfc-editor.org/rfc/rfc3419.pdf"],"folder":"IETF/RFC-3419","files":{"txt":{"path":"standards/IETF/RFC-3419/RFC-3419.txt","sha256":"7dcc09aa4e01a935a92a19929b09d62c9cf27fe34920047831840c7189437775"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces a Management Information Base (MIB) module\n that defines textual conventions to represent commonly used\n transport-layer addressing information. The definitions are\n compatible with the concept of TAddress/TDomain pairs introduced by\n the Structure of Management Information version 2 (SMIv2) and support\n the Internet transport protocols over IPv4 and IPv6.","scope_keywords":["3419","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null}],"search_text":"IETF RFC 3419 This document introduces a Management Information Base (MIB) module\n that defines textual conventions to represent commonly used\n transport-layer addressing information. The definitions are\n compatible with the concept of TAddress/TDomain pairs introduced by\n the Structure of Management Information version 2 (SMIv2) and support\n the Internet transport protocols over IPv4 and IPv6. 3419 key management nested-reference unchanged"},{"id":"IETF RFC 3421","type":"specification","body":"IETF","designation":"RFC 3421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3421.txt","https://www.rfc-editor.org/rfc/rfc3421.pdf"],"folder":"IETF/RFC-3421","files":{"txt":{"path":"standards/IETF/RFC-3421/RFC-3421.txt","sha256":"3106c3fb372795068884854511702e54a2a38ad9df94b1bf444d77e8750cf24a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Zhao\nRequest for Comments: 3421 H. Schulzrinne\nCategory: Experimental Columbia University\n E. Guttman\n Sun Microsystems\n C. Bisdikian\n W. Jerome\n IBM\n November 2002\n\n Select and Sort Extensions for the Service Location Protocol (SLP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines two extensions (Select and Sort) for the\n Service Location Protocol (SLP). These extensions allow a User Agent\n (UA) to request that the Uniform Resource Locator (URL) entries in a\n Service Reply (SrvRply) be limited to the specified number, or be\n sorted according to the s","scope_keywords":["3421","attribute","attributes","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 3421 Network Working Group W. Zhao\nRequest for Comments: 3421 H. Schulzrinne\nCategory: Experimental Columbia University\n E. Guttman\n Sun Microsystems\n C. Bisdikian\n W. Jerome\n IBM\n November 2002\n\n Select and Sort Extensions for the Service Location Protocol (SLP)\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document defines two extensions (Select and Sort) for the\n Service Location Protocol (SLP). These extensions allow a User Agent\n (UA) to request that the Uniform Resource Locator (URL) entries in a\n Service Reply (SrvRply) be limited to the specified number, or be\n sorted according to the s 3421 attribute attributes key keys nested-reference unchanged"},{"id":"IETF RFC 3423","type":"specification","body":"IETF","designation":"RFC 3423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3423.txt","https://www.rfc-editor.org/rfc/rfc3423.pdf"],"folder":"IETF/RFC-3423","files":{"txt":{"path":"standards/IETF/RFC-3423/RFC-3423.txt","sha256":"951fe2904f32a7226fe2e51842ad77870c8521dc3c9c5cfa05b9f61f41952129"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Common Reliable Accounting for Network\n Element (CRANE) protocol that enables efficient and reliable delivery\n of any data, mainly accounting data from Network Elements to any\n systems, such as mediation systems and Business Support Systems\n (BSS)/ Operations Support Systems (OSS). The protocol is developed\n to address the critical needs for exporting high volume of accounting\n data from NE's with efficient use of network, storage, and processing\n resources.\n\n This document specifies the architecture of the protocol and the\n message format, which MUST be supported by all CRANE protocol\n implementations.","scope_keywords":["3423","attribute","authentication","authorization","delivery","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null}],"search_text":"IETF RFC 3423 This document defines the Common Reliable Accounting for Network\n Element (CRANE) protocol that enables efficient and reliable delivery\n of any data, mainly accounting data from Network Elements to any\n systems, such as mediation systems and Business Support Systems\n (BSS)/ Operations Support Systems (OSS). The protocol is developed\n to address the critical needs for exporting high volume of accounting\n data from NE's with efficient use of network, storage, and processing\n resources.\n\n This document specifies the architecture of the protocol and the\n message format, which MUST be supported by all CRANE protocol\n implementations. 3423 attribute authentication authorization delivery key pid nested-reference unchanged"},{"id":"IETF RFC 3428","type":"specification","body":"IETF","designation":"RFC 3428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3428.txt","https://www.rfc-editor.org/rfc/rfc3428.pdf"],"folder":"IETF/RFC-3428","files":{"txt":{"path":"standards/IETF/RFC-3428/RFC-3428.txt","sha256":"5dea7897d8a34aae35719ce7582cc72436fb64f3b2c12a2251c6f48f5befc965"}},"tags":["nested-reference","unchanged"],"summary":"Instant Messaging (IM) refers to the transfer of messages between\n users in near real-time. These messages are usually, but not\n required to be, short. IMs are often used in a conversational mode,\n that is, the transfer of messages back and forth is fast enough for\n participants to maintain an interactive conversation.\n\n This document proposes the MESSAGE method, an extension to the\n Session Initiation Protocol (SIP) that allows the transfer of Instant\n Messages. Since the MESSAGE request is an extension to SIP, it\n inherits all the request routing and security features of that\n protocol. MESSAGE requests carry the content in the form of MIME\n body parts. MESSAGE requests do not themselves initiate a SIP\n dialog; under normal usage each Instant Message stands alone, much\n like pager messages. MESSAGE requests may be sent in the context of\n a dialog initiated by some other SIP request.\n\nC","scope_keywords":["3428","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4453","folder":"IETF/RFC-4453","source":"IETF/RFC-4453/RFC-4453.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null}],"search_text":"IETF RFC 3428 Instant Messaging (IM) refers to the transfer of messages between\n users in near real-time. These messages are usually, but not\n required to be, short. IMs are often used in a conversational mode,\n that is, the transfer of messages back and forth is fast enough for\n participants to maintain an interactive conversation.\n\n This document proposes the MESSAGE method, an extension to the\n Session Initiation Protocol (SIP) that allows the transfer of Instant\n Messages. Since the MESSAGE request is an extension to SIP, it\n inherits all the request routing and security features of that\n protocol. MESSAGE requests carry the content in the form of MIME\n body parts. MESSAGE requests do not themselves initiate a SIP\n dialog; under normal usage each Instant Message stands alone, much\n like pager messages. MESSAGE requests may be sent in the context of\n a dialog initiated by some other SIP request.\n\nC 3428 authentication key nested-reference unchanged"},{"id":"IETF RFC 3431","type":"specification","body":"IETF","designation":"RFC 3431","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3431.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3431.txt","https://www.rfc-editor.org/rfc/rfc3431.pdf"],"folder":"IETF/RFC-3431","files":{"txt":{"path":"standards/IETF/RFC-3431/RFC-3431.txt","sha256":"1f61f1ca6f958a5d5458e0ff834e00ba17fa57923d37517eebe8565405950e56"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the RELATIONAL extension to the Sieve mail\n filtering language defined in RFC 3028. This extension extends\n existing conditional tests in Sieve to allow relational operators.\n In addition to testing their content, it also allows for testing of\n the number of entities in header and envelope fields.\n\n1 Introduction\n\n Sieve [SIEVE] is a language for filtering e-mail messages at the time\n of final delivery. It is designed to be implementable on either a\n mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Messages Access Protocol (IMAP) servers, as it has no\n variables, loops, nor the ability to shell out to external programs.\n\n The RELATION","scope_keywords":["3431","crl","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3685","folder":"IETF/RFC-3685","source":"IETF/RFC-3685/RFC-3685.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null}],"search_text":"IETF RFC 3431 This document describes the RELATIONAL extension to the Sieve mail\n filtering language defined in RFC 3028. This extension extends\n existing conditional tests in Sieve to allow relational operators.\n In addition to testing their content, it also allows for testing of\n the number of entities in header and envelope fields.\n\n1 Introduction\n\n Sieve [SIEVE] is a language for filtering e-mail messages at the time\n of final delivery. It is designed to be implementable on either a\n mail client or mail server. It is meant to be extensible, simple,\n and independent of access protocol, mail architecture, and operating\n system. It is suitable for running on a mail server where users may\n not be allowed to execute arbitrary programs, such as on black box\n Internet Messages Access Protocol (IMAP) servers, as it has no\n variables, loops, nor the ability to shell out to external programs.\n\n The RELATION 3431 crl delivery key subject nested-reference unchanged"},{"id":"IETF RFC 3433","type":"specification","body":"IETF","designation":"RFC 3433","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3433.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3433.txt","https://www.rfc-editor.org/rfc/rfc3433.pdf"],"folder":"IETF/RFC-3433","files":{"txt":{"path":"standards/IETF/RFC-3433/RFC-3433.txt","sha256":"b5c78f14dbeb8ca93fedd4542a10272a996e13f890d59246ac7860df1a9e8be3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for extending the Entity\n MIB (RFC 2737) to provide generalized access to information related\n to physical sensors, which are often found in networking equipment\n (such as chassis temperature, fan RPM, power supply voltage).","scope_keywords":["3433","key","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 4044","folder":"IETF/RFC-4044","source":"IETF/RFC-4044/RFC-4044.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null}],"search_text":"IETF RFC 3433 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for extending the Entity\n MIB (RFC 2737) to provide generalized access to information related\n to physical sensors, which are often found in networking equipment\n (such as chassis temperature, fan RPM, power supply voltage). 3433 key management timestamp nested-reference unchanged"},{"id":"IETF RFC 3438","type":"specification","body":"IETF","designation":"RFC 3438","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3438.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3438.txt","https://www.rfc-editor.org/rfc/rfc3438.pdf"],"folder":"IETF/RFC-3438","files":{"txt":{"path":"standards/IETF/RFC-3438/RFC-3438.txt","sha256":"4271668ceda4630aa1b4e1246f027fc333d1ef7b7c9e9220bea6160bf54d69cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes updates to the Internet Assigned Numbers\n Authority (IANA) considerations for the Layer Two Tunneling Protocol\n (L2TP).","scope_keywords":["3438","attribute","http","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4349","folder":"IETF/RFC-4349","source":"IETF/RFC-4349/RFC-4349.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null}],"search_text":"IETF RFC 3438 This document describes updates to the Internet Assigned Numbers\n Authority (IANA) considerations for the Layer Two Tunneling Protocol\n (L2TP). 3438 attribute http key policies nested-reference unchanged"},{"id":"IETF RFC 3443","type":"specification","body":"IETF","designation":"RFC 3443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3443.txt","https://www.rfc-editor.org/rfc/rfc3443.pdf"],"folder":"IETF/RFC-3443","files":{"txt":{"path":"standards/IETF/RFC-3443/RFC-3443.txt","sha256":"3c4d746c0f2b4f255c5ce361534d2f65f9abb7bacb517c85b693e55a69455f4f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Time To Live (TTL) processing in hierarchical\n Multi-Protocol Label Switching (MPLS) networks and is motivated by\n the need to formalize a TTL-transparent mode of operation for an MPLS\n label-switched path. It updates RFC 3032, \"MPLS Label Stack\n Encoding\". TTL processing in both Pipe and Uniform Model\n hierarchical tunnels are specified with examples for both \"push\" and\n \"pop\" cases. The document also complements RFC 3270, \"MPLS Support\n of Differentiated Services\" and ties together the terminology\n introduced in that document with TTL processing in hierarchical MPLS\n networks.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC-2119].\n\n1. Introduction and Motivation\n\n This document describ","scope_keywords":["3443","key","management","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null}],"search_text":"IETF RFC 3443 This document describes Time To Live (TTL) processing in hierarchical\n Multi-Protocol Label Switching (MPLS) networks and is motivated by\n the need to formalize a TTL-transparent mode of operation for an MPLS\n label-switched path. It updates RFC 3032, \"MPLS Label Stack\n Encoding\". TTL processing in both Pipe and Uniform Model\n hierarchical tunnels are specified with examples for both \"push\" and\n \"pop\" cases. The document also complements RFC 3270, \"MPLS Support\n of Differentiated Services\" and ties together the terminology\n introduced in that document with TTL processing in hierarchical MPLS\n networks.\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC-2119].\n\n1. Introduction and Motivation\n\n This document describ 3443 key management path tls nested-reference unchanged"},{"id":"IETF RFC 3445","type":"specification","body":"IETF","designation":"RFC 3445","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3445.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3445.txt","https://www.rfc-editor.org/rfc/rfc3445.pdf"],"folder":"IETF/RFC-3445","files":{"txt":{"path":"standards/IETF/RFC-3445/RFC-3445.txt","sha256":"f92c410fe8d006735801f91cbb94427f2ba2b8c1d9cb712344f96078d23c41fb"}},"tags":["nested-reference","unchanged"],"summary":"This document limits the Domain Name System (DNS) KEY Resource Record\n (RR) to only keys used by the Domain Name System Security Extensions\n (DNSSEC). The original KEY RR used sub-typing to store both DNSSEC\n keys and arbitrary application keys. Storing both DNSSEC and\n application keys with the same record type is a mistake. This\n document removes application keys from the KEY record by redefining\n the Protocol Octet field in the KEY RR Data. As a result of removing\n application keys, all but one of the flags in the KEY record become\n unnecessary and are redefined. Three existing application key sub-\n types are changed to reserved, but the format of the KEY record is\n not changed. This document updates RFC 2535.\n\n1. Introduction\n\n This document limits the scope of the KEY Resource Record (RR). The\n KEY RR was defined in [3] and used resource record sub-typing to hold\n arbitrary public k","scope_keywords":["3445","algorithm","key","keys","management","signature","signatures","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3658","folder":"IETF/RFC-3658","source":"IETF/RFC-3658/RFC-3658.txt","version":null},{"body":"IETF","designation":"RFC 3755","folder":"IETF/RFC-3755","source":"IETF/RFC-3755/RFC-3755.txt","version":null},{"body":"IETF","designation":"RFC 4025","folder":"IETF/RFC-4025","source":"IETF/RFC-4025/RFC-4025.txt","version":null},{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null}],"search_text":"IETF RFC 3445 This document limits the Domain Name System (DNS) KEY Resource Record\n (RR) to only keys used by the Domain Name System Security Extensions\n (DNSSEC). The original KEY RR used sub-typing to store both DNSSEC\n keys and arbitrary application keys. Storing both DNSSEC and\n application keys with the same record type is a mistake. This\n document removes application keys from the KEY record by redefining\n the Protocol Octet field in the KEY RR Data. As a result of removing\n application keys, all but one of the flags in the KEY record become\n unnecessary and are redefined. Three existing application key sub-\n types are changed to reserved, but the format of the KEY record is\n not changed. This document updates RFC 2535.\n\n1. Introduction\n\n This document limits the scope of the KEY Resource Record (RR). The\n KEY RR was defined in [3] and used resource record sub-typing to hold\n arbitrary public k 3445 algorithm key keys management signature signatures tls trust nested-reference unchanged"},{"id":"IETF RFC 3454","type":"specification","body":"IETF","designation":"RFC 3454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3454.txt","https://www.rfc-editor.org/rfc/rfc3454.pdf"],"folder":"IETF/RFC-3454","files":{"txt":{"path":"standards/IETF/RFC-3454/RFC-3454.txt","sha256":"eb722fa698fb7e8823b835d9fd263e4cdb8f1c7b0d234edf7f0e3bd2ccbb2c79"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for preparing Unicode text\n strings in order to increase the likelihood that string input and\n string comparison work in ways that make sense for typical users\n throughout the world. The stringprep protocol is useful for protocol\n identifier values, company and personal names, internationalized\n domain names, and other text strings.\n\n This document does not specify how protocols should prepare text\n strings. Protocols must create profiles of stringprep in order to\n fully specify the processing options.","scope_keywords":["3454","algorithm","presentation","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3490","folder":"IETF/RFC-3490","source":"IETF/RFC-3490/RFC-3490.txt","version":null},{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4013","folder":"IETF/RFC-4013","source":"IETF/RFC-4013/RFC-4013.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4343","folder":"IETF/RFC-4343","source":"IETF/RFC-4343/RFC-4343.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5051","folder":"IETF/RFC-5051","source":"IETF/RFC-5051/RFC-5051.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5893","folder":"IETF/RFC-5893","source":"IETF/RFC-5893/RFC-5893.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 3454 This document describes a framework for preparing Unicode text\n strings in order to increase the likelihood that string input and\n string comparison work in ways that make sense for typical users\n throughout the world. The stringprep protocol is useful for protocol\n identifier values, company and personal names, internationalized\n domain names, and other text strings.\n\n This document does not specify how protocols should prepare text\n strings. Protocols must create profiles of stringprep in order to\n fully specify the processing options. 3454 algorithm presentation profile profiles nested-reference unchanged"},{"id":"IETF RFC 3457","type":"specification","body":"IETF","designation":"RFC 3457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3457.txt","https://www.rfc-editor.org/rfc/rfc3457.pdf"],"folder":"IETF/RFC-3457","files":{"txt":{"path":"standards/IETF/RFC-3457/RFC-3457.txt","sha256":"ef8ba03416170078936c36cdd4364868058cd80bfdd405abbb6d78b2b010f232"}},"tags":["nested-reference","unchanged"],"summary":"IPsec offers much promise as a secure remote access mechanism.\n However, there are a number of differing remote access scenarios,\n each having some shared and some unique requirements. A thorough\n understanding of these requirements is necessary in order to\n effectively evaluate the suitability of a specific set of mechanisms\n for any particular remote access scenario. This document enumerates\n the requirements for a number of common remote access scenarios.","scope_keywords":["3457","audit","authentication","authorization","key","pki","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3456","folder":"IETF/RFC-3456","source":"IETF/RFC-3456/RFC-3456.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3457 IPsec offers much promise as a secure remote access mechanism.\n However, there are a number of differing remote access scenarios,\n each having some shared and some unique requirements. A thorough\n understanding of these requirements is necessary in order to\n effectively evaluate the suitability of a specific set of mechanisms\n for any particular remote access scenario. This document enumerates\n the requirements for a number of common remote access scenarios. 3457 audit authentication authorization key pki policy nested-reference unchanged"},{"id":"IETF RFC 3477","type":"specification","body":"IETF","designation":"RFC 3477","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3477.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3477.txt","https://www.rfc-editor.org/rfc/rfc3477.pdf"],"folder":"IETF/RFC-3477","files":{"txt":{"path":"standards/IETF/RFC-3477/RFC-3477.txt","sha256":"dce0e92c7c208fc6ec119040bd731b3d7878f7762ee6538f89c3464e3b51efd4"}},"tags":["nested-reference","unchanged"],"summary":"Current signalling used by Multi-Protocol Label Switching Traffic\n Engineering (MPLS TE) does not provide support for unnumbered links.\n This document defines procedures and extensions to Resource\n ReSerVation Protocol (RSVP) for Label Switched Path (LSP) Tunnels\n (RSVP-TE), one of the MPLS TE signalling protocols, that are needed\n in order to support unnumbered links.\n\nSpecification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n1. Overview\n\n Supporting MPLS TE over unnumbered links (i.e., links that do not\n have IP addresses) involves two components: (a) the ability to carry\n (TE) information about unnumbered links in IGP TE extensions (ISIS or\n OSPF), and (b) the ability to specify unnumbered links in","scope_keywords":["3477","attribute","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3473","folder":"IETF/RFC-3473","source":"IETF/RFC-3473/RFC-3473.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 3477 Current signalling used by Multi-Protocol Label Switching Traffic\n Engineering (MPLS TE) does not provide support for unnumbered links.\n This document defines procedures and extensions to Resource\n ReSerVation Protocol (RSVP) for Label Switched Path (LSP) Tunnels\n (RSVP-TE), one of the MPLS TE signalling protocols, that are needed\n in order to support unnumbered links.\n\nSpecification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n1. Overview\n\n Supporting MPLS TE over unnumbered links (i.e., links that do not\n have IP addresses) involves two components: (a) the ability to carry\n (TE) information about unnumbered links in IGP TE extensions (ISIS or\n OSPF), and (b) the ability to specify unnumbered links in 3477 attribute key path nested-reference unchanged"},{"id":"IETF RFC 3480","type":"specification","body":"IETF","designation":"RFC 3480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3480.txt","https://www.rfc-editor.org/rfc/rfc3480.pdf"],"folder":"IETF/RFC-3480","files":{"txt":{"path":"standards/IETF/RFC-3480/RFC-3480.txt","sha256":"32e55b935d6af9f07afcce57462029b26da7926d11c5d261522bf4d8fb67c8d3"}},"tags":["nested-reference","unchanged"],"summary":"Current signalling used by Multi-Protocol Label Switching Traffic\n Engineering (MPLS TE) does not provide support for unnumbered links.\n This document defines procedures and extensions to Constraint-Routing\n Label Distribution Protocol (CR-LDP), one of the MPLS TE signalling\n protocols that are needed in order to support unnumbered links.\n\nSpecification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n1. Overview\n\n Supporting MPLS TE over unnumbered links (i.e., links that do not\n have IP addresses) involves two components: (a) the ability to carry\n (TE) information about unnumbered links in IGP TE extensions (ISIS or\n OSPF), and (b) the ability to specify unnumbered links in MPLS TE\n signalling. The forme","scope_keywords":["3480","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null},{"body":"IETF","designation":"RFC 3630","folder":"IETF/RFC-3630","source":"IETF/RFC-3630/RFC-3630.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null}],"search_text":"IETF RFC 3480 Current signalling used by Multi-Protocol Label Switching Traffic\n Engineering (MPLS TE) does not provide support for unnumbered links.\n This document defines procedures and extensions to Constraint-Routing\n Label Distribution Protocol (CR-LDP), one of the MPLS TE signalling\n protocols that are needed in order to support unnumbered links.\n\nSpecification of Requirements\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119\n [RFC2119].\n\n1. Overview\n\n Supporting MPLS TE over unnumbered links (i.e., links that do not\n have IP addresses) involves two components: (a) the ability to carry\n (TE) information about unnumbered links in IGP TE extensions (ISIS or\n OSPF), and (b) the ability to specify unnumbered links in MPLS TE\n signalling. The forme 3480 attribute key nested-reference unchanged"},{"id":"IETF RFC 3485","type":"specification","body":"IETF","designation":"RFC 3485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3485.txt","https://www.rfc-editor.org/rfc/rfc3485.pdf"],"folder":"IETF/RFC-3485","files":{"txt":{"path":"standards/IETF/RFC-3485/RFC-3485.txt","sha256":"7fbc391c6bb96af366c8b6da21840a7454dc2686de80df26ea20f1b79e0320bc"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) is a text-based protocol for\n initiating and managing communication sessions. The protocol can be\n compressed by using Signaling Compression (SigComp). Similarly, the\n Session Description Protocol (SDP) is a text-based protocol intended\n for describing multimedia sessions for the purposes of session\n announcement, session invitation, and other forms of multimedia\n session initiation. This memo defines the SIP/SDP-specific static\n dictionary that SigComp may use in order to achieve higher\n efficiency. The dictionary is compression algorithm independent.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 3485 SIP and SDP Static Dictionary for SigComp February 2003","scope_keywords":["3485","algorithm","algorithms","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null}],"search_text":"IETF RFC 3485 The Session Initiation Protocol (SIP) is a text-based protocol for\n initiating and managing communication sessions. The protocol can be\n compressed by using Signaling Compression (SigComp). Similarly, the\n Session Description Protocol (SDP) is a text-based protocol intended\n for describing multimedia sessions for the purposes of session\n announcement, session invitation, and other forms of multimedia\n session initiation. This memo defines the SIP/SDP-specific static\n dictionary that SigComp may use in order to achieve higher\n efficiency. The dictionary is compression algorithm independent.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 3485 SIP and SDP Static Dictionary for SigComp February 2003 3485 algorithm algorithms crl presentation nested-reference unchanged"},{"id":"IETF RFC 3486","type":"specification","body":"IETF","designation":"RFC 3486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3486.txt","https://www.rfc-editor.org/rfc/rfc3486.pdf"],"folder":"IETF/RFC-3486","files":{"txt":{"path":"standards/IETF/RFC-3486/RFC-3486.txt","sha256":"6f8259199ae570de6fd607e9f1da0a3a9b61b5aa9c387e44452c2b462d9733fa"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to signal that compression is\n desired for one or more Session Initiation Protocol (SIP) messages.\n It also states when it is appropriate to send compressed SIP messages\n to a SIP entity.","scope_keywords":["3486","http","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 3969","folder":"IETF/RFC-3969","source":"IETF/RFC-3969/RFC-3969.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null}],"search_text":"IETF RFC 3486 This document describes a mechanism to signal that compression is\n desired for one or more Session Initiation Protocol (SIP) messages.\n It also states when it is appropriate to send compressed SIP messages\n to a SIP entity. 3486 http tls nested-reference unchanged"},{"id":"IETF RFC 3508","type":"specification","body":"IETF","designation":"RFC 3508","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3508.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3508.txt","https://www.rfc-editor.org/rfc/rfc3508.pdf"],"folder":"IETF/RFC-3508","files":{"txt":{"path":"standards/IETF/RFC-3508/RFC-3508.txt","sha256":"3c07aa985d1a15cdf76d06d2c697334caf965e84ba2d6a3e394bcc102517220d"}},"tags":["nested-reference","unchanged"],"summary":"ITU-T Recommendation H.323 version 4 introduced an H.323-specific\n Uniform Resource Locator (URL). This document reproduces the H323-\n URL definition found in H.323, and is published as an RFC for ease of\n access and registration with the Internet Assigned Numbers Authority\n (IANA).\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].","scope_keywords":["3508","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null}],"search_text":"IETF RFC 3508 ITU-T Recommendation H.323 version 4 introduced an H.323-specific\n Uniform Resource Locator (URL). This document reproduces the H323-\n URL definition found in H.323, and is published as an RFC for ease of\n access and registration with the Internet Assigned Numbers Authority\n (IANA).\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2]. 3508 key registered nested-reference unchanged"},{"id":"IETF RFC 3521","type":"specification","body":"IETF","designation":"RFC 3521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3521.txt","https://www.rfc-editor.org/rfc/rfc3521.pdf"],"folder":"IETF/RFC-3521","files":{"txt":{"path":"standards/IETF/RFC-3521/RFC-3521.txt","sha256":"e0624abcb0714d4ccc740abc8b0cc17aa490c54cae4c95531ab2d227ee0b612d"}},"tags":["nested-reference","unchanged"],"summary":"Establishing multimedia streams must take into account requirements\n for end-to-end QoS, authorization of network resource usage and\n accurate accounting for resources used. During session set up,\n policies may be enforced to ensure that the media streams being\n requested lie within the bounds of the service profile established\n for the requesting host. Similarly, when a host requests resources\n to provide a certain QoS for a packet flow, policies may be enforced\n to ensure that the required resources lie within the bounds of the\n resource profile established for the requesting host.\n\n To prevent fraud and to ensure accurate billing, this document\n describes various scenarios and mechanisms that provide the linkage\n required to verify that the resources being used to provide a\n requested QoS are in-line with the media streams requested (and\n authorized) for the session.\n\nHamer, et al. In","scope_keywords":["3521","authorization","key","keys","management","policies","policy","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null}],"search_text":"IETF RFC 3521 Establishing multimedia streams must take into account requirements\n for end-to-end QoS, authorization of network resource usage and\n accurate accounting for resources used. During session set up,\n policies may be enforced to ensure that the media streams being\n requested lie within the bounds of the service profile established\n for the requesting host. Similarly, when a host requests resources\n to provide a certain QoS for a packet flow, policies may be enforced\n to ensure that the required resources lie within the bounds of the\n resource profile established for the requesting host.\n\n To prevent fraud and to ensure accurate billing, this document\n describes various scenarios and mechanisms that provide the linkage\n required to verify that the resources being used to provide a\n requested QoS are in-line with the media streams requested (and\n authorized) for the session.\n\nHamer, et al. In 3521 authorization key keys management policies policy profile trust nested-reference unchanged"},{"id":"IETF RFC 3524","type":"specification","body":"IETF","designation":"RFC 3524","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3524.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3524.txt","https://www.rfc-editor.org/rfc/rfc3524.pdf"],"folder":"IETF/RFC-3524","files":{"txt":{"path":"standards/IETF/RFC-3524/RFC-3524.txt","sha256":"c6c45656a8f161203a03b8b831a2fa42efc98e01c0bbf78f0d6092949401bf5c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Session Description\n Protocol (SDP) grouping framework. It allows requesting a group of\n media streams to be mapped into a single resource reservation flow.\n The SDP syntax needed is defined, as well as a new \"semantics\"\n attribute called Single Reservation Flow (SRF).","scope_keywords":["3524","attribute","http","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 3524 This document defines an extension to the Session Description\n Protocol (SDP) grouping framework. It allows requesting a group of\n media streams to be mapped into a single resource reservation flow.\n The SDP syntax needed is defined, as well as a new \"semantics\"\n attribute called Single Reservation Flow (SRF). 3524 attribute http key registered nested-reference unchanged"},{"id":"IETF RFC 3533","type":"specification","body":"IETF","designation":"RFC 3533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3533.txt","https://www.rfc-editor.org/rfc/rfc3533.pdf"],"folder":"IETF/RFC-3533","files":{"txt":{"path":"standards/IETF/RFC-3533/RFC-3533.txt","sha256":"f170265303dd32d026611f7e080338d15d5456643d1d4c22f2c32046860c5476"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Ogg bitstream format version 0, which is\n a general, freely-available encapsulation format for media streams.\n It is able to encapsulate any kind and number of video and audio\n encoding formats as well as other data streams in a single bitstream.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2].","scope_keywords":["3533","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3534","folder":"IETF/RFC-3534","source":"IETF/RFC-3534/RFC-3534.txt","version":null},{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null}],"search_text":"IETF RFC 3533 This document describes the Ogg bitstream format version 0, which is\n a general, freely-available encapsulation format for media streams.\n It is able to encapsulate any kind and number of video and audio\n encoding formats as well as other data streams in a single bitstream.\n\nTerminology\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in BCP 14, RFC 2119 [2]. 3533 key registered nested-reference unchanged"},{"id":"IETF RFC 3534","type":"specification","body":"IETF","designation":"RFC 3534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3534.txt","https://www.rfc-editor.org/rfc/rfc3534.pdf"],"folder":"IETF/RFC-3534","files":{"txt":{"path":"standards/IETF/RFC-3534/RFC-3534.txt","sha256":"a9dd8cda127edd259d9e3f00db9708708e785ce9c48ca1ed7c8c3a8293b21656"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Walleij\nRequest for Comments: 3534 The Ogg Vorbis Community\nCategory: Standards Track May 2003\n\n The application/ogg Media Type\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n The Ogg Bitstream Format aims at becoming a general, freely-available\n standard for transporting multimedia content across computing\n platforms and networks. The intention of this document is to define\n the MIME media type application/ogg to refer to this kind of content\n when transporte","scope_keywords":["3534","encryption","http","key","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3533","folder":"IETF/RFC-3533","source":"IETF/RFC-3533/RFC-3533.txt","version":null}],"search_text":"IETF RFC 3534 Network Working Group L. Walleij\nRequest for Comments: 3534 The Ogg Vorbis Community\nCategory: Standards Track May 2003\n\n The application/ogg Media Type\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n The Ogg Bitstream Format aims at becoming a general, freely-available\n standard for transporting multimedia content across computing\n platforms and networks. The intention of this document is to define\n the MIME media type application/ogg to refer to this kind of content\n when transporte 3534 encryption http key license subject nested-reference unchanged"},{"id":"IETF RFC 3540","type":"specification","body":"IETF","designation":"RFC 3540","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3540.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3540.txt","https://www.rfc-editor.org/rfc/rfc3540.pdf"],"folder":"IETF/RFC-3540","files":{"txt":{"path":"standards/IETF/RFC-3540/RFC-3540.txt","sha256":"ecd1fcbd4a85c7b13735284f7c4691348f2a2d87e66fb6682ab3a613ac4a9e9a"}},"tags":["nested-reference","unchanged"],"summary":"This note describes the Explicit Congestion Notification (ECN)-nonce,\n an optional addition to ECN that protects against accidental or\n malicious concealment of marked packets from the TCP sender. It\n improves the robustness of congestion control by preventing receivers\n from exploiting ECN to gain an unfair share of network bandwidth.\n The ECN-nonce uses the two ECN-Capable Transport (ECT)codepoints in\n the ECN field of the IP header, and requires a flag in the TCP\n header. It is computationally efficient for both routers and hosts.\n\n1. Introduction\n\n Statement of Intent\n\n This specification describes an optional addition to Explicit\n Congestion Notification [RFC3168] improving its robustness against\n malicious or accidental concealment of marked packets. It has not\n been deployed widely. One goal of publication as an Experimental\n RFC is to be prudent, and encourage use and deployment ","scope_keywords":["3540","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 5129","folder":"IETF/RFC-5129","source":"IETF/RFC-5129/RFC-5129.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 3540 This note describes the Explicit Congestion Notification (ECN)-nonce,\n an optional addition to ECN that protects against accidental or\n malicious concealment of marked packets from the TCP sender. It\n improves the robustness of congestion control by preventing receivers\n from exploiting ECN to gain an unfair share of network bandwidth.\n The ECN-nonce uses the two ECN-Capable Transport (ECT)codepoints in\n the ECN field of the IP header, and requires a flag in the TCP\n header. It is computationally efficient for both routers and hosts.\n\n1. Introduction\n\n Statement of Intent\n\n This specification describes an optional addition to Explicit\n Congestion Notification [RFC3168] improving its robustness against\n malicious or accidental concealment of marked packets. It has not\n been deployed widely. One goal of publication as an Experimental\n RFC is to be prudent, and encourage use and deployment  3540 key path nested-reference unchanged"},{"id":"IETF RFC 3545","type":"specification","body":"IETF","designation":"RFC 3545","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3545.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3545.txt","https://www.rfc-editor.org/rfc/rfc3545.pdf"],"folder":"IETF/RFC-3545","files":{"txt":{"path":"standards/IETF/RFC-3545/RFC-3545.txt","sha256":"b35f0ea1675eea649e5686c6b063100163a0c2df5fac180e08ba5e69c457d140"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a header compression scheme for point to\n point links with packet loss and long delays. It is based on\n Compressed Real-time Transport Protocol (CRTP), the IP/UDP/RTP header\n compression described in RFC 2508. CRTP does not perform well on\n such links: packet loss results in context corruption and due to the\n long delay, many more packets are discarded before the context is\n repaired. To correct the behavior of CRTP over such links, a few\n extensions to the protocol are specified here. The extensions aim to\n reduce context corruption by changing the way the compressor updates\n the context at the decompressor: updates are repeated and include\n updates to full and differential context parameters. With these\n extensions, CRTP performs well over links with packet loss, packet\n reordering and long delays.\n\nKoren, et al. Standards Track [Page 1]\n\f\nRFC 3545 Enhanced Comp","scope_keywords":["3545"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3544","folder":"IETF/RFC-3544","source":"IETF/RFC-3544/RFC-3544.txt","version":null},{"body":"IETF","designation":"RFC 4247","folder":"IETF/RFC-4247","source":"IETF/RFC-4247/RFC-4247.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null}],"search_text":"IETF RFC 3545 This document describes a header compression scheme for point to\n point links with packet loss and long delays. It is based on\n Compressed Real-time Transport Protocol (CRTP), the IP/UDP/RTP header\n compression described in RFC 2508. CRTP does not perform well on\n such links: packet loss results in context corruption and due to the\n long delay, many more packets are discarded before the context is\n repaired. To correct the behavior of CRTP over such links, a few\n extensions to the protocol are specified here. The extensions aim to\n reduce context corruption by changing the way the compressor updates\n the context at the decompressor: updates are repeated and include\n updates to full and differential context parameters. With these\n extensions, CRTP performs well over links with packet loss, packet\n reordering and long delays.\n\nKoren, et al. Standards Track [Page 1]\n\f\nRFC 3545 Enhanced Comp 3545 nested-reference unchanged"},{"id":"IETF RFC 3553","type":"specification","body":"IETF","designation":"RFC 3553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3553.txt","https://www.rfc-editor.org/rfc/rfc3553.pdf"],"folder":"IETF/RFC-3553","files":{"txt":{"path":"standards/IETF/RFC-3553/RFC-3553.txt","sha256":"1e20bcb01189a4cf086dc304bb5da79948225a6dfe7478ac2ddb60ad479834e4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Mealling\nRequest for Comments: 3553 VeriSign\nBCP: 73 L. Masinter\nCategory: Best Current Practice Adobe Systems\n T. Hardie\n Qualcomm\n G. Klyne\n Nine by Nine\n June 2003\n\n An IETF URN Sub-namespace for Registered Protocol Parameters\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document describes a new sub-delegation for the 'ietf' URN\n namespace for registered protocol items. The 'ietf' URN namespace is\n defined in RFC 2648 as a root for persistent URIs that refer to\n IETF-defined resources.\n\n1. Introduction\n\n From time to time IETF standards require the registration of various\n protocol elements in well ","scope_keywords":["3553","key","policies","registered","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3688","folder":"IETF/RFC-3688","source":"IETF/RFC-3688/RFC-3688.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6755","folder":"IETF/RFC-6755","source":"IETF/RFC-6755/RFC-6755.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IETF RFC 3553 Network Working Group M. Mealling\nRequest for Comments: 3553 VeriSign\nBCP: 73 L. Masinter\nCategory: Best Current Practice Adobe Systems\n T. Hardie\n Qualcomm\n G. Klyne\n Nine by Nine\n June 2003\n\n An IETF URN Sub-namespace for Registered Protocol Parameters\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2003). All Rights Reserved.\n\nAbstract\n\n This document describes a new sub-delegation for the 'ietf' URN\n namespace for registered protocol items. The 'ietf' URN namespace is\n defined in RFC 2648 as a root for persistent URIs that refer to\n IETF-defined resources.\n\n1. Introduction\n\n From time to time IETF standards require the registration of various\n protocol elements in well  3553 key policies registered validation nested-reference unchanged"},{"id":"IETF RFC 3564","type":"specification","body":"IETF","designation":"RFC 3564","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3564.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3564.txt","https://www.rfc-editor.org/rfc/rfc3564.pdf"],"folder":"IETF/RFC-3564","files":{"txt":{"path":"standards/IETF/RFC-3564/RFC-3564.txt","sha256":"d321a5502f26882e5777d0b3ce3ec496c7b14fb3bba2e98a6e05e46aedd30f1e"}},"tags":["nested-reference","unchanged"],"summary":"This document presents Service Provider requirements for support of\n Differentiated Services (Diff-Serv)-aware MPLS Traffic Engineering\n (DS-TE).\n\n Its objective is to provide guidance for the definition, selection\n and specification of a technical solution addressing these\n requirements. Specification for this solution itself is outside the\n scope of this document.\n\n A problem statement is first provided. Then, the document describes\n example applications scenarios identified by Service Providers where\n existing MPLS Traffic Engineering mechanisms fall short and\n Diff-Serv-aware Traffic Engineering can address the needs. The\n detailed requirements that need to be addressed by the technical\n solution are also reviewed. Finally, the document identifies the\n evaluation criteria that should be considered for selection and\n definition of the technical solution.\n\nLe Faucheur & Lai Information","scope_keywords":["3564","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 3564 This document presents Service Provider requirements for support of\n Differentiated Services (Diff-Serv)-aware MPLS Traffic Engineering\n (DS-TE).\n\n Its objective is to provide guidance for the definition, selection\n and specification of a technical solution addressing these\n requirements. Specification for this solution itself is outside the\n scope of this document.\n\n A problem statement is first provided. Then, the document describes\n example applications scenarios identified by Service Providers where\n existing MPLS Traffic Engineering mechanisms fall short and\n Diff-Serv-aware Traffic Engineering can address the needs. The\n detailed requirements that need to be addressed by the technical\n solution are also reviewed. Finally, the document identifies the\n evaluation criteria that should be considered for selection and\n definition of the technical solution.\n\nLe Faucheur & Lai Information 3564 key path nested-reference unchanged"},{"id":"IETF RFC 3575","type":"specification","body":"IETF","designation":"RFC 3575","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3575.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3575.txt","https://www.rfc-editor.org/rfc/rfc3575.pdf"],"folder":"IETF/RFC-3575","files":{"txt":{"path":"standards/IETF/RFC-3575/RFC-3575.txt","sha256":"87e16d8aac933837467ae1f6bfedccba44bbde02d805fd885e47169d279550d5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the IANA considerations for the Remote\n Authentication Dial In User Service (RADIUS).\n\n This document updates RFC 2865.\n\n1. Introduction\n\n This document provides guidance to the Internet Assigned Numbers\n Authority (IANA) regarding registration of values related to the\n Remote Authentication Dial In User Service (RADIUS), defined in\n [RFC2865], in accordance with BCP 26, [RFC2434]. It also reserves\n Packet Type Codes that are or have been in use on the Internet.","scope_keywords":["3575","attribute","attributes","authentication","authorization","key","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4072","folder":"IETF/RFC-4072","source":"IETF/RFC-4072/RFC-4072.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 3575 This document describes the IANA considerations for the Remote\n Authentication Dial In User Service (RADIUS).\n\n This document updates RFC 2865.\n\n1. Introduction\n\n This document provides guidance to the Internet Assigned Numbers\n Authority (IANA) regarding registration of values related to the\n Remote Authentication Dial In User Service (RADIUS), defined in\n [RFC2865], in accordance with BCP 26, [RFC2434]. It also reserves\n Packet Type Codes that are or have been in use on the Internet. 3575 attribute attributes authentication authorization key policies policy nested-reference unchanged"},{"id":"IETF RFC 3581","type":"specification","body":"IETF","designation":"RFC 3581","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3581.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3581.txt","https://www.rfc-editor.org/rfc/rfc3581.pdf"],"folder":"IETF/RFC-3581","files":{"txt":{"path":"standards/IETF/RFC-3581/RFC-3581.txt","sha256":"1593242224585815dd0838f25009497369be7f783192c6b291753536a10b302f"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) operates over UDP and TCP,\n among others. When used with UDP, responses to requests are returned\n to the source address the request came from, and to the port written\n into the topmost Via header field value of the request. This\n behavior is not desirable in many cases, most notably, when the\n client is behind a Network Address Translator (NAT). This extension\n defines a new parameter for the Via header field, called \"rport\",\n that allows a client to request that the server send the response\n back to the source IP address and port from which the request\n originated.\n\nRosenberg & Schulzrinne Standards Track [Page 1]\n\f\nRFC 3581 Symmetric Response Routing August 2003","scope_keywords":["3581","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null}],"search_text":"IETF RFC 3581 The Session Initiation Protocol (SIP) operates over UDP and TCP,\n among others. When used with UDP, responses to requests are returned\n to the source address the request came from, and to the port written\n into the topmost Via header field value of the request. This\n behavior is not desirable in many cases, most notably, when the\n client is behind a Network Address Translator (NAT). This extension\n defines a new parameter for the Via header field, called \"rport\",\n that allows a client to request that the server send the response\n back to the source IP address and port from which the request\n originated.\n\nRosenberg & Schulzrinne Standards Track [Page 1]\n\f\nRFC 3581 Symmetric Response Routing August 2003 3581 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3583","type":"specification","body":"IETF","designation":"RFC 3583","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3583.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3583.txt","https://www.rfc-editor.org/rfc/rfc3583.pdf"],"folder":"IETF/RFC-3583","files":{"txt":{"path":"standards/IETF/RFC-3583/RFC-3583.txt","sha256":"8eef62b90152a7e6b5207c6af8c714515b32c93e42551e4e8609b877fb9492fd"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IP ensures correct routing of packets to a mobile node as the\n mobile node changes its point of attachment to the Internet.\n However, it is also required to provide proper Quality of Service\n (QoS) forwarding treatment to the mobile node's packet stream at the\n intermediate nodes in the network, so that QoS-sensitive IP services\n can be supported over Mobile IP. This document describes\n requirements for an IP QoS mechanism for its satisfactory operation\n with Mobile IP.\n\nChaskar Informational [Page 1]\n\f\nRFC 3583 Mobile IP QoS Requirements September 2003","scope_keywords":["3583","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null}],"search_text":"IETF RFC 3583 Mobile IP ensures correct routing of packets to a mobile node as the\n mobile node changes its point of attachment to the Internet.\n However, it is also required to provide proper Quality of Service\n (QoS) forwarding treatment to the mobile node's packet stream at the\n intermediate nodes in the network, so that QoS-sensitive IP services\n can be supported over Mobile IP. This document describes\n requirements for an IP QoS mechanism for its satisfactory operation\n with Mobile IP.\n\nChaskar Informational [Page 1]\n\f\nRFC 3583 Mobile IP QoS Requirements September 2003 3583 key path nested-reference unchanged"},{"id":"IETF RFC 3586","type":"specification","body":"IETF","designation":"RFC 3586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3586.txt","https://www.rfc-editor.org/rfc/rfc3586.pdf"],"folder":"IETF/RFC-3586","files":{"txt":{"path":"standards/IETF/RFC-3586/RFC-3586.txt","sha256":"f981be1792ca19561497228d5ec532978894571e0f9f743f968e42dfd05e33f1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the problem space and solution requirements\n for developing an IP Security Policy (IPSP) configuration and\n management framework. The IPSP architecture provides a scalable,\n decentralized framework for managing, discovering and negotiating the\n host and network security policies that govern access, authorization,\n authentication, confidentiality, data integrity, and other IP\n Security properties. This document highlights such architectural\n components and presents their functional requirements.","scope_keywords":["3586","authentication","authorization","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3586 This document describes the problem space and solution requirements\n for developing an IP Security Policy (IPSP) configuration and\n management framework. The IPSP architecture provides a scalable,\n decentralized framework for managing, discovering and negotiating the\n host and network security policies that govern access, authorization,\n authentication, confidentiality, data integrity, and other IP\n Security properties. This document highlights such architectural\n components and presents their functional requirements. 3586 authentication authorization key management policies policy nested-reference unchanged"},{"id":"IETF RFC 3590","type":"specification","body":"IETF","designation":"RFC 3590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3590.txt","https://www.rfc-editor.org/rfc/rfc3590.pdf"],"folder":"IETF/RFC-3590","files":{"txt":{"path":"standards/IETF/RFC-3590/RFC-3590.txt","sha256":"282a768641bf8ccf27e994a820ff9d20b1d280a99ed15f951bb00f02d689147e"}},"tags":["nested-reference","unchanged"],"summary":"It has come to light that there is an issue with the selection of a\n suitable IPv6 source address for Multicast Listener Discovery (MLD)\n messages when a node is performing stateless address\n autoconfiguration. This document is intended to clarify the rules on\n selecting an IPv6 address to use for MLD messages.\n\n1. Introduction\n\n The original specification of the Multicast Listener Discovery\n Protocol (MLD) for IPv6 [RFC 2710] mandates the use of a link-local\n IPv6 source address for the transmission of MLD messages. In\n addition, MLD also requires nodes to send MLD Report messages when\n joining any IPv6 multicast group (except the All-Nodes address and\n addresses of scope less than 2).\n\n These MLD requirements conflict with the use of IPv6 multicast within\n the Neighbor Discovery Protocol [RFC 2461]. For stateless\n autoconfiguration, as defined in [RFC 2462], a node is required to\n join","scope_keywords":["3590","key","license"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 3590 It has come to light that there is an issue with the selection of a\n suitable IPv6 source address for Multicast Listener Discovery (MLD)\n messages when a node is performing stateless address\n autoconfiguration. This document is intended to clarify the rules on\n selecting an IPv6 address to use for MLD messages.\n\n1. Introduction\n\n The original specification of the Multicast Listener Discovery\n Protocol (MLD) for IPv6 [RFC 2710] mandates the use of a link-local\n IPv6 source address for the transmission of MLD messages. In\n addition, MLD also requires nodes to send MLD Report messages when\n joining any IPv6 multicast group (except the All-Nodes address and\n addresses of scope less than 2).\n\n These MLD requirements conflict with the use of IPv6 multicast within\n the Neighbor Discovery Protocol [RFC 2461]. For stateless\n autoconfiguration, as defined in [RFC 2462], a node is required to\n join 3590 key license nested-reference unchanged"},{"id":"IETF RFC 3598","type":"specification","body":"IETF","designation":"RFC 3598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3598.txt","https://www.rfc-editor.org/rfc/rfc3598.pdf"],"folder":"IETF/RFC-3598","files":{"txt":{"path":"standards/IETF/RFC-3598/RFC-3598.txt","sha256":"abba9d8264c28bd0f06e275d6247daad8c294b6e04e5a95320bf4c4217fa0d8e"}},"tags":["nested-reference","unchanged"],"summary":"On email systems that allow for \"subaddressing\" or \"detailed\n addressing\" (e.g., \"ken+sieve@example.org\"), it is sometimes\n desirable to make comparisons against these sub-parts of addresses.\n This document defines an extension to the Sieve mail filtering\n language that allows users to compare against the user and detail\n parts of an address.","scope_keywords":["3598","http","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5233","folder":"IETF/RFC-5233","source":"IETF/RFC-5233/RFC-5233.txt","version":null}],"search_text":"IETF RFC 3598 On email systems that allow for \"subaddressing\" or \"detailed\n addressing\" (e.g., \"ken+sieve@example.org\"), it is sometimes\n desirable to make comparisons against these sub-parts of addresses.\n This document defines an extension to the Sieve mail filtering\n language that allows users to compare against the user and detail\n parts of an address. 3598 http key subject nested-reference unchanged"},{"id":"IETF RFC 3602","type":"specification","body":"IETF","designation":"RFC 3602","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3602.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3602.txt","https://www.rfc-editor.org/rfc/rfc3602.pdf"],"folder":"IETF/RFC-3602","files":{"txt":{"path":"standards/IETF/RFC-3602/RFC-3602.txt","sha256":"1a95ec00c065983ffa3f253d70eb4a07530d9e1829f27cdb522bdbb7343da3cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Advanced Encryption Standard\n (AES) Cipher Algorithm in Cipher Block Chaining (CBC) Mode, with an\n explicit Initialization Vector (IV), as a confidentiality mechanism\n within the context of the IPsec Encapsulating Security Payload (ESP).","scope_keywords":["3602","algorithm","algorithms","attribute","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 3602 This document describes the use of the Advanced Encryption Standard\n (AES) Cipher Algorithm in Cipher Block Chaining (CBC) Mode, with an\n explicit Initialization Vector (IV), as a confidentiality mechanism\n within the context of the IPsec Encapsulating Security Payload (ESP). 3602 algorithm algorithms attribute encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 3603","type":"specification","body":"IETF","designation":"RFC 3603","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3603.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3603.txt","https://www.rfc-editor.org/rfc/rfc3603.pdf"],"folder":"IETF/RFC-3603","files":{"txt":{"path":"standards/IETF/RFC-3603/RFC-3603.txt","sha256":"8f1f791ccd73d55fd89c8fa1b292908c1a125ad25d1f7d1ced1f93f4b626779c"}},"tags":["nested-reference","unchanged"],"summary":"In order to deploy a residential telephone service at very large\n scale across different domains, it is necessary for trusted elements\n owned by different service providers to exchange trusted information\n that conveys customer-specific information and expectations about the\n parties involved in the call. This document describes private\n extensions to the Session Initiation Protocol (SIP) (RFC3261) for\n supporting the exchange of customer information and billing\n information between trusted entities in the PacketCable Distributed\n Call Signaling Architecture. These extensions provide mechanisms for\n access network coordination to prevent theft of service, customer\n originated trace of harassing calls, support for operator services\n and emergency services, and support for various other regulatory\n issues. The use of the extensions is only applicable within closed\n administrative domains, ","scope_keywords":["3603","delivery","key","management","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3968","folder":"IETF/RFC-3968","source":"IETF/RFC-3968/RFC-3968.txt","version":null}],"search_text":"IETF RFC 3603 In order to deploy a residential telephone service at very large\n scale across different domains, it is necessary for trusted elements\n owned by different service providers to exchange trusted information\n that conveys customer-specific information and expectations about the\n parties involved in the call. This document describes private\n extensions to the Session Initiation Protocol (SIP) (RFC3261) for\n supporting the exchange of customer information and billing\n information between trusted entities in the PacketCable Distributed\n Call Signaling Architecture. These extensions provide mechanisms for\n access network coordination to prevent theft of service, customer\n originated trace of harassing calls, support for operator services\n and emergency services, and support for various other regulatory\n issues. The use of the extensions is only applicable within closed\n administrative domains,  3603 delivery key management policies trust nested-reference unchanged"},{"id":"IETF RFC 3608","type":"specification","body":"IETF","designation":"RFC 3608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3608.txt","https://www.rfc-editor.org/rfc/rfc3608.pdf"],"folder":"IETF/RFC-3608","files":{"txt":{"path":"standards/IETF/RFC-3608/RFC-3608.txt","sha256":"a79415d974ed7ac17070a7061cbc49f26e36cab0711b4ebf26e192562beb7c58"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Session Initiation Protocol (SIP) extension\n header field used in conjunction with responses to REGISTER requests\n to provide a mechanism by which a registrar may inform a registering\n user agent (UA) of a service route that the UA may use to request\n outbound services from the registrar's domain.","scope_keywords":["3608","http","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null}],"search_text":"IETF RFC 3608 This document defines a Session Initiation Protocol (SIP) extension\n header field used in conjunction with responses to REGISTER requests\n to provide a mechanism by which a registrar may inform a registering\n user agent (UA) of a service route that the UA may use to request\n outbound services from the registrar's domain. 3608 http key management registered nested-reference unchanged"},{"id":"IETF RFC 3610","type":"specification","body":"IETF","designation":"RFC 3610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3610.txt","https://www.rfc-editor.org/rfc/rfc3610.pdf"],"folder":"IETF/RFC-3610","files":{"txt":{"path":"standards/IETF/RFC-3610/RFC-3610.txt","sha256":"d6c857b1dea18d8259ee0ccc5468859990200e8580d0ad55dc75963d0c46588d"}},"tags":["nested-reference","unchanged"],"summary":"Counter with CBC-MAC (CCM) is a generic authenticated encryption\n block cipher mode. CCM is defined for use with 128-bit block\n ciphers, such as the Advanced Encryption Standard (AES).\n\n1. Introduction\n\n Counter with CBC-MAC (CCM) is a generic authenticated encryption\n block cipher mode. CCM is only defined for use with 128-bit block\n ciphers, such as AES [AES]. The CCM design principles can easily be\n applied to other block sizes, but these modes will require their own\n specifications.","scope_keywords":["3610","authentication","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4107","folder":"IETF/RFC-4107","source":"IETF/RFC-4107/RFC-4107.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 3610 Counter with CBC-MAC (CCM) is a generic authenticated encryption\n block cipher mode. CCM is defined for use with 128-bit block\n ciphers, such as the Advanced Encryption Standard (AES).\n\n1. Introduction\n\n Counter with CBC-MAC (CCM) is a generic authenticated encryption\n block cipher mode. CCM is only defined for use with 128-bit block\n ciphers, such as AES [AES]. The CCM design principles can easily be\n applied to other block sizes, but these modes will require their own\n specifications. 3610 authentication encryption key nested-reference unchanged"},{"id":"IETF RFC 3630","type":"specification","body":"IETF","designation":"RFC 3630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3630.txt","https://www.rfc-editor.org/rfc/rfc3630.pdf"],"folder":"IETF/RFC-3630","files":{"txt":{"path":"standards/IETF/RFC-3630/RFC-3630.txt","sha256":"946c0c5e459bdd716c5c193c6a64666bf7430ba0a7737667b26400e8e7dab221"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the OSPF protocol version 2 to\n support intra-area Traffic Engineering (TE), using Opaque Link State\n Advertisements.\n\n1. Introduction\n\n This document specifies a method of adding traffic engineering\n capabilities to OSPF Version 2 [1]. The architecture of traffic\n engineering is described in [5]. The semantic content of the\n extensions is essentially identical to the corresponding extensions\n to IS-IS [6]. It is expected that the traffic engineering extensions\n to OSPF will continue to mirror those in IS-IS.\n\n The extensions provide a way of describing the traffic engineering\n topology (including bandwidth and administrative constraints) and\n distributing this information within a given OSPF area. This\n topology does not necessarily match the regular routed topology,\n though this proposal depends on Network LSAs to describe multi-access\n links. This","scope_keywords":["3630","algorithm","attribute","attributes","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3623","folder":"IETF/RFC-3623","source":"IETF/RFC-3623/RFC-3623.txt","version":null},{"body":"IETF","designation":"RFC 3785","folder":"IETF/RFC-3785","source":"IETF/RFC-3785/RFC-3785.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4222","folder":"IETF/RFC-4222","source":"IETF/RFC-4222/RFC-4222.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 4970","folder":"IETF/RFC-4970","source":"IETF/RFC-4970/RFC-4970.txt","version":null},{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 3630 This document describes extensions to the OSPF protocol version 2 to\n support intra-area Traffic Engineering (TE), using Opaque Link State\n Advertisements.\n\n1. Introduction\n\n This document specifies a method of adding traffic engineering\n capabilities to OSPF Version 2 [1]. The architecture of traffic\n engineering is described in [5]. The semantic content of the\n extensions is essentially identical to the corresponding extensions\n to IS-IS [6]. It is expected that the traffic engineering extensions\n to OSPF will continue to mirror those in IS-IS.\n\n The extensions provide a way of describing the traffic engineering\n topology (including bandwidth and administrative constraints) and\n distributing this information within a given OSPF area. This\n topology does not necessarily match the regular routed topology,\n though this proposal depends on Network LSAs to describe multi-access\n links. This 3630 algorithm attribute attributes key path subject nested-reference unchanged"},{"id":"IETF RFC 3633","type":"specification","body":"IETF","designation":"RFC 3633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3633.txt","https://www.rfc-editor.org/rfc/rfc3633.pdf"],"folder":"IETF/RFC-3633","files":{"txt":{"path":"standards/IETF/RFC-3633/RFC-3633.txt","sha256":"1b250863f649f15555d03c9ae1a3a5c3b007f8008b26507c70c6cc4d340cfff7"}},"tags":["nested-reference","unchanged"],"summary":"The Prefix Delegation options provide a mechanism for automated\n delegation of IPv6 prefixes using the Dynamic Host Configuration\n Protocol (DHCP). This mechanism is intended for delegating a long-\n lived prefix from a delegating router to a requesting router, across\n an administrative boundary, where the delegating router does not\n require knowledge about the topology of the links in the network to\n which the prefixes will be assigned.","scope_keywords":["3633","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3904","folder":"IETF/RFC-3904","source":"IETF/RFC-3904/RFC-3904.txt","version":null},{"body":"IETF","designation":"RFC 4192","folder":"IETF/RFC-4192","source":"IETF/RFC-4192/RFC-4192.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4580","folder":"IETF/RFC-4580","source":"IETF/RFC-4580/RFC-4580.txt","version":null},{"body":"IETF","designation":"RFC 4649","folder":"IETF/RFC-4649","source":"IETF/RFC-4649/RFC-4649.txt","version":null},{"body":"IETF","designation":"RFC 4818","folder":"IETF/RFC-4818","source":"IETF/RFC-4818/RFC-4818.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5969","folder":"IETF/RFC-5969","source":"IETF/RFC-5969/RFC-5969.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6324","folder":"IETF/RFC-6324","source":"IETF/RFC-6324/RFC-6324.txt","version":null},{"body":"IETF","designation":"RFC 6459","folder":"IETF/RFC-6459","source":"IETF/RFC-6459/RFC-6459.txt","version":null},{"body":"IETF","designation":"RFC 6603","folder":"IETF/RFC-6603","source":"IETF/RFC-6603/RFC-6603.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6877","folder":"IETF/RFC-6877","source":"IETF/RFC-6877/RFC-6877.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7083","folder":"IETF/RFC-7083","source":"IETF/RFC-7083/RFC-7083.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7278","folder":"IETF/RFC-7278","source":"IETF/RFC-7278/RFC-7278.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3633 The Prefix Delegation options provide a mechanism for automated\n delegation of IPv6 prefixes using the Dynamic Host Configuration\n Protocol (DHCP). This mechanism is intended for delegating a long-\n lived prefix from a delegating router to a requesting router, across\n an administrative boundary, where the delegating router does not\n require knowledge about the topology of the links in the network to\n which the prefixes will be assigned. 3633 key nested-reference unchanged"},{"id":"IETF RFC 3648","type":"specification","body":"IETF","designation":"RFC 3648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3648.txt","https://www.rfc-editor.org/rfc/rfc3648.pdf"],"folder":"IETF/RFC-3648","files":{"txt":{"path":"standards/IETF/RFC-3648/RFC-3648.txt","sha256":"c3117ac1477d1c68cd511569d81865ccd55132918f945b816533116b6b983c74"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Web Distributed Authoring and\n Versioning (WebDAV) Protocol to support the server-side ordering of\n collection members. Of particular interest are orderings that are\n not based on property values, and so cannot be achieved using a\n search protocol's ordering option and cannot be maintained\n automatically by the server. Protocol elements are defined to let\n clients specify the position in the ordering of each collection\n member, as well as the semantics governing the ordering.\n\nWhitehead & Reschke Standards Track [Page 1]\n\f\nRFC 3648 WebDAV Ordered Collections Protocol December 2003","scope_keywords":["3648","attribute","attributes","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null}],"search_text":"IETF RFC 3648 This specification extends the Web Distributed Authoring and\n Versioning (WebDAV) Protocol to support the server-side ordering of\n collection members. Of particular interest are orderings that are\n not based on property values, and so cannot be achieved using a\n search protocol's ordering option and cannot be maintained\n automatically by the server. Protocol elements are defined to let\n clients specify the position in the ordering of each collection\n member, as well as the semantics governing the ordering.\n\nWhitehead & Reschke Standards Track [Page 1]\n\f\nRFC 3648 WebDAV Ordered Collections Protocol December 2003 3648 attribute attributes http key nested-reference unchanged"},{"id":"IETF RFC 3657","type":"specification","body":"IETF","designation":"RFC 3657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3657.txt","https://www.rfc-editor.org/rfc/rfc3657.pdf"],"folder":"IETF/RFC-3657","files":{"txt":{"path":"standards/IETF/RFC-3657/RFC-3657.txt","sha256":"35efaa271524f1c153bdac171c1730dbb52b96c93d0f8adc413cde1aa99aa622"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the Camellia\n encryption algorithm for encryption with the Cryptographic Message\n Syntax (CMS).\n\n1. Introduction\n\n This document specifies the conventions for using the Camellia\n encryption algorithm [CamelliaSpec] for encryption with the\n Cryptographic Message Syntax (CMS) [CMS]. The relevant object\n identifiers (OIDs) and processing steps are provided so that Camellia\n may be used in the CMS specification (RFC 3369, RFC 3370) for content\n and key encryption.\n\n Note: This work was done when the first author worked for NTT.\n\nMoriai & Kato Standards Track [Page 1]\n\f\nRFC 3657 Use of the Camellia Algorithm in CMS January 2004","scope_keywords":["3657","algorithm","algorithms","encryption","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null}],"search_text":"IETF RFC 3657 This document specifies the conventions for using the Camellia\n encryption algorithm for encryption with the Cryptographic Message\n Syntax (CMS).\n\n1. Introduction\n\n This document specifies the conventions for using the Camellia\n encryption algorithm [CamelliaSpec] for encryption with the\n Cryptographic Message Syntax (CMS) [CMS]. The relevant object\n identifiers (OIDs) and processing steps are provided so that Camellia\n may be used in the CMS specification (RFC 3369, RFC 3370) for content\n and key encryption.\n\n Note: This work was done when the first author worked for NTT.\n\nMoriai & Kato Standards Track [Page 1]\n\f\nRFC 3657 Use of the Camellia Algorithm in CMS January 2004 3657 algorithm algorithms encryption key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 3665","type":"specification","body":"IETF","designation":"RFC 3665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3665.txt","https://www.rfc-editor.org/rfc/rfc3665.pdf"],"folder":"IETF/RFC-3665","files":{"txt":{"path":"standards/IETF/RFC-3665/RFC-3665.txt","sha256":"f18daefb91b61d06d062c0ddff3dba2cbf05032355dcfa890ca12ad0fac5583c"}},"tags":["nested-reference","unchanged"],"summary":"This document gives examples of Session Initiation Protocol (SIP)\n call flows. Elements in these call flows include SIP User Agents and\n Clients, SIP Proxy and Redirect Servers. Scenarios include SIP\n Registration and SIP session establishment. Call flow diagrams and\n message details are shown.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 3665 SIP Basic Call Flow Examples December 2003","scope_keywords":["3665","authentication","http","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 4244","folder":"IETF/RFC-4244","source":"IETF/RFC-4244/RFC-4244.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null}],"search_text":"IETF RFC 3665 This document gives examples of Session Initiation Protocol (SIP)\n call flows. Elements in these call flows include SIP User Agents and\n Clients, SIP Proxy and Redirect Servers. Scenarios include SIP\n Registration and SIP session establishment. Call flow diagrams and\n message details are shown.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 3665 SIP Basic Call Flow Examples December 2003 3665 authentication http key path tls nested-reference unchanged"},{"id":"IETF RFC 3666","type":"specification","body":"IETF","designation":"RFC 3666","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3666.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3666.txt","https://www.rfc-editor.org/rfc/rfc3666.pdf"],"folder":"IETF/RFC-3666","files":{"txt":{"path":"standards/IETF/RFC-3666/RFC-3666.txt","sha256":"5d7e16447351a244b512281a70cc7d90e73547815a4cc30e44b686dda281c220"}},"tags":["nested-reference","unchanged"],"summary":"This document contains best current practice examples of Session\n Initiation Protocol (SIP) call flows showing interworking with the\n Public Switched Telephone Network (PSTN). Elements in these call\n flows include SIP User Agents, SIP Proxy Servers, and PSTN Gateways.\n Scenarios include SIP to PSTN, PSTN to SIP, and PSTN to PSTN via SIP.\n PSTN telephony protocols are illustrated using ISDN (Integrated\n Services Digital Network), ISUP (ISDN User Part), and FGB (Feature\n Group B) circuit associated signaling. PSTN calls are illustrated\n using global telephone numbers from the PSTN and private extensions\n served on by a PBX (Private Branch Exchange). Call flow diagrams and\n message details are shown.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 3666 SIP PSTN Call Flows December 2003","scope_keywords":["3666","authentication","http","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3665","folder":"IETF/RFC-3665","source":"IETF/RFC-3665/RFC-3665.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null}],"search_text":"IETF RFC 3666 This document contains best current practice examples of Session\n Initiation Protocol (SIP) call flows showing interworking with the\n Public Switched Telephone Network (PSTN). Elements in these call\n flows include SIP User Agents, SIP Proxy Servers, and PSTN Gateways.\n Scenarios include SIP to PSTN, PSTN to SIP, and PSTN to PSTN via SIP.\n PSTN telephony protocols are illustrated using ISDN (Integrated\n Services Digital Network), ISUP (ISDN User Part), and FGB (Feature\n Group B) circuit associated signaling. PSTN calls are illustrated\n using global telephone numbers from the PSTN and private extensions\n served on by a PBX (Private Branch Exchange). Call flow diagrams and\n message details are shown.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 3666 SIP PSTN Call Flows December 2003 3666 authentication http key path tls nested-reference unchanged"},{"id":"IETF RFC 3671","type":"specification","body":"IETF","designation":"RFC 3671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3671.txt","https://www.rfc-editor.org/rfc/rfc3671.pdf"],"folder":"IETF/RFC-3671","files":{"txt":{"path":"standards/IETF/RFC-3671/RFC-3671.txt","sha256":"c3e52d1f0ed61b7e65230e7bc5ef9db5b3e78fbfdd63eac58c5d9e99cca0e1f5"}},"tags":["nested-reference","unchanged"],"summary":"X.500 collective attributes allow common characteristics to be shared\n between collections of entries. This document summarizes the X.500\n information model for collective attributes and describes use of\n collective attributes in LDAP (Lightweight Directory Access\n Protocol). This document provides schema definitions for collective\n attributes for use in LDAP.\n\n1. Introduction\n\n In X.500 [X.500], a collective attribute is \"a user attribute whose\n values are the same for each member of an entry collection\" [X.501].\n This document details their use in the Lightweight Directory Access\n Protocol (LDAP) [RFC3377].","scope_keywords":["3671","attribute","attributes","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null}],"search_text":"IETF RFC 3671 X.500 collective attributes allow common characteristics to be shared\n between collections of entries. This document summarizes the X.500\n information model for collective attributes and describes use of\n collective attributes in LDAP (Lightweight Directory Access\n Protocol). This document provides schema definitions for collective\n attributes for use in LDAP.\n\n1. Introduction\n\n In X.500 [X.500], a collective attribute is \"a user attribute whose\n values are the same for each member of an entry collection\" [X.501].\n This document details their use in the Lightweight Directory Access\n Protocol (LDAP) [RFC3377]. 3671 attribute attributes key subject nested-reference unchanged"},{"id":"IETF RFC 3672","type":"specification","body":"IETF","designation":"RFC 3672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3672.txt","https://www.rfc-editor.org/rfc/rfc3672.pdf"],"folder":"IETF/RFC-3672","files":{"txt":{"path":"standards/IETF/RFC-3672/RFC-3672.txt","sha256":"5d9f4f2c523b410b96201fa5ca9848a3bd4d1b13c15cb711b8d3a609a2210ca2"}},"tags":["nested-reference","unchanged"],"summary":"In X.500 directories, subentries are special entries used to hold\n information associated with a subtree or subtree refinement. This\n document adapts X.500 subentries mechanisms for use with the\n Lightweight Directory Access Protocol (LDAP).\n\n1. Overview\n\n From [X.501]:\n\n A subentry is a special kind of entry immediately subordinate to\n an administrative point. It contains attributes that pertain to\n a subtree (or subtree refinement) associated with its\n administrative point. The subentries and their administrative\n point are part of the same naming context.\n\n A single subentry may serve all or several aspects of\n administrative authority. Alternatively, a specific aspect of\n administrative authority may be handled through one or more of\n its own subentries.\n\n Subentries in the Lightweight Directory Access Protocol (LDAP)\n [RFC3377] SHALL behave in accordance with X.501 unless noted\n oth","scope_keywords":["3672","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null}],"search_text":"IETF RFC 3672 In X.500 directories, subentries are special entries used to hold\n information associated with a subtree or subtree refinement. This\n document adapts X.500 subentries mechanisms for use with the\n Lightweight Directory Access Protocol (LDAP).\n\n1. Overview\n\n From [X.501]:\n\n A subentry is a special kind of entry immediately subordinate to\n an administrative point. It contains attributes that pertain to\n a subtree (or subtree refinement) associated with its\n administrative point. The subentries and their administrative\n point are part of the same naming context.\n\n A single subentry may serve all or several aspects of\n administrative authority. Alternatively, a specific aspect of\n administrative authority may be handled through one or more of\n its own subentries.\n\n Subentries in the Lightweight Directory Access Protocol (LDAP)\n [RFC3377] SHALL behave in accordance with X.501 unless noted\n oth 3672 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 3673","type":"specification","body":"IETF","designation":"RFC 3673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3673.txt","https://www.rfc-editor.org/rfc/rfc3673.pdf"],"folder":"IETF/RFC-3673","files":{"txt":{"path":"standards/IETF/RFC-3673/RFC-3673.txt","sha256":"ff28bee755980e1a2f707dff673bfa18877e3f91f24a4968f199002272656a70"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) supports a mechanism\n for requesting the return of all user attributes but not all\n operational attributes. This document describes an LDAP extension\n which clients may use to request the return of all operational\n attributes.\n\n1. Overview\n\n X.500 [X.500] provides a mechanism for clients to request all\n operational attributes be returned with entries provided in response\n to a search operation. This mechanism is often used by clients to\n discover which operational attributes are present in an entry.\n\n This documents extends the Lightweight Directory Access Protocol\n (LDAP) [RFC3377] to provide a simple mechanism which clients may use\n to request the return of all operational attributes. The mechanism\n is designed for use with existing general purpose LDAP clients\n (including web browsers which support LDAP URLs) and existing LDAP\n APIs.\n\n ","scope_keywords":["3673","attribute","attributes","http","key","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3674","folder":"IETF/RFC-3674","source":"IETF/RFC-3674/RFC-3674.txt","version":null}],"search_text":"IETF RFC 3673 The Lightweight Directory Access Protocol (LDAP) supports a mechanism\n for requesting the return of all user attributes but not all\n operational attributes. This document describes an LDAP extension\n which clients may use to request the return of all operational\n attributes.\n\n1. Overview\n\n X.500 [X.500] provides a mechanism for clients to request all\n operational attributes be returned with entries provided in response\n to a search operation. This mechanism is often used by clients to\n discover which operational attributes are present in an entry.\n\n This documents extends the Lightweight Directory Access Protocol\n (LDAP) [RFC3377] to provide a simple mechanism which clients may use\n to request the return of all operational attributes. The mechanism\n is designed for use with existing general purpose LDAP clients\n (including web browsers which support LDAP URLs) and existing LDAP\n APIs.\n\n  3673 attribute attributes http key license subject nested-reference unchanged"},{"id":"IETF RFC 3674","type":"specification","body":"IETF","designation":"RFC 3674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3674.txt","https://www.rfc-editor.org/rfc/rfc3674.pdf"],"folder":"IETF/RFC-3674","files":{"txt":{"path":"standards/IETF/RFC-3674/RFC-3674.txt","sha256":"7773b98628406d38264eb933424705f7d96b79a41692fca9ed8e309d0c2efe42"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) is an extensible\n protocol with numerous elective features. This document introduces a\n general mechanism for discovery of elective features and extensions\n which cannot be discovered using existing mechanisms.\n\n1. Background and Intended Use\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an\n extensible protocol with numerous elective features. LDAP provides\n mechanisms for a client to discover supported protocol versions,\n controls, extended operations, Simple Authentication and Security\n Layer (SASL) mechanisms, and subschema information. However, these\n mechanisms are not designed to support general feature discovery.\n\n This document describes a simple, general-purpose mechanism which\n clients may use to discover the set of elective features supported by\n a server. For example, this mechanism could be used by a client t","scope_keywords":["3674","attribute","attributes","authentication","key","license","registered","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null}],"search_text":"IETF RFC 3674 The Lightweight Directory Access Protocol (LDAP) is an extensible\n protocol with numerous elective features. This document introduces a\n general mechanism for discovery of elective features and extensions\n which cannot be discovered using existing mechanisms.\n\n1. Background and Intended Use\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an\n extensible protocol with numerous elective features. LDAP provides\n mechanisms for a client to discover supported protocol versions,\n controls, extended operations, Simple Authentication and Security\n Layer (SASL) mechanisms, and subschema information. However, these\n mechanisms are not designed to support general feature discovery.\n\n This document describes a simple, general-purpose mechanism which\n clients may use to discover the set of elective features supported by\n a server. For example, this mechanism could be used by a client t 3674 attribute attributes authentication key license registered risk subject nested-reference unchanged"},{"id":"IETF RFC 3680","type":"specification","body":"IETF","designation":"RFC 3680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3680.txt","https://www.rfc-editor.org/rfc/rfc3680.pdf"],"folder":"IETF/RFC-3680","files":{"txt":{"path":"standards/IETF/RFC-3680/RFC-3680.txt","sha256":"34c94d34569aa1385f6ba23cc608602b5b845511fa3f16aaf6965bf4054ec576"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Session Initiation Protocol (SIP) event\n package for registrations. Through its REGISTER method, SIP allows a\n user agent to create, modify, and delete registrations.\n Registrations can also be altered by administrators in order to\n enforce policy. As a result, these registrations represent a piece\n of state in the network that can change dynamically. There are many\n cases where a user agent would like to be notified of changes in this\n state. This event package defines a mechanism by which those user\n agents can request and obtain such notifications.","scope_keywords":["3680","authentication","key","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null}],"search_text":"IETF RFC 3680 This document defines a Session Initiation Protocol (SIP) event\n package for registrations. Through its REGISTER method, SIP allows a\n user agent to create, modify, and delete registrations.\n Registrations can also be altered by administrators in order to\n enforce policy. As a result, these registrations represent a piece\n of state in the network that can change dynamically. There are many\n cases where a user agent would like to be notified of changes in this\n state. This event package defines a mechanism by which those user\n agents can request and obtain such notifications. 3680 authentication key policy registered nested-reference unchanged"},{"id":"IETF RFC 3685","type":"specification","body":"IETF","designation":"RFC 3685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3685.txt","https://www.rfc-editor.org/rfc/rfc3685.pdf"],"folder":"IETF/RFC-3685","files":{"txt":{"path":"standards/IETF/RFC-3685/RFC-3685.txt","sha256":"a3deab831960446670893bfc84a97f41deebf85805400f5c595f9779c1ae55af"}},"tags":["nested-reference","unchanged"],"summary":"The SIEVE mail filtering language \"spamtest\" and \"virustest\"\n extensions permit users to use simple, portable commands for spam and\n virus tests on email messages. Each extension provides a new test\n using matches against numeric 'scores'. It is the responsibility of\n the underlying SIEVE implementation to do the actual checks that\n result in values returned by the tests.","scope_keywords":["3685","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5235","folder":"IETF/RFC-5235","source":"IETF/RFC-5235/RFC-5235.txt","version":null}],"search_text":"IETF RFC 3685 The SIEVE mail filtering language \"spamtest\" and \"virustest\"\n extensions permit users to use simple, portable commands for spam and\n virus tests on email messages. Each extension provides a new test\n using matches against numeric 'scores'. It is the responsibility of\n the underlying SIEVE implementation to do the actual checks that\n result in values returned by the tests. 3685 key nested-reference unchanged"},{"id":"IETF RFC 3686","type":"specification","body":"IETF","designation":"RFC 3686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3686.txt","https://www.rfc-editor.org/rfc/rfc3686.pdf"],"folder":"IETF/RFC-3686","files":{"txt":{"path":"standards/IETF/RFC-3686/RFC-3686.txt","sha256":"c8759b088f1db8bf4c1077336c9de0521c34b3e895b9742000b6044e55f7a7c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of Advanced Encryption Standard (AES)\n Counter Mode, with an explicit initialization vector, as an IPsec\n Encapsulating Security Payload (ESP) confidentiality mechanism.","scope_keywords":["3686","algorithm","attribute","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 4106","folder":"IETF/RFC-4106","source":"IETF/RFC-4106/RFC-4106.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 3686 This document describes the use of Advanced Encryption Standard (AES)\n Counter Mode, with an explicit initialization vector, as an IPsec\n Encapsulating Security Payload (ESP) confidentiality mechanism. 3686 algorithm attribute authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 3688","type":"specification","body":"IETF","designation":"RFC 3688","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3688.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3688.txt","https://www.rfc-editor.org/rfc/rfc3688.pdf"],"folder":"IETF/RFC-3688","files":{"txt":{"path":"standards/IETF/RFC-3688/RFC-3688.txt","sha256":"c319aba4706da97c2414a25c1379ce91e6d072939cf7b2167604aa75c8a01a58"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an IANA maintained registry for IETF\n standards which use Extensible Markup Language (XML) related items\n such as Namespaces, Document Type Declarations (DTDs), Schemas, and\n Resource Description Framework (RDF) Schemas.\n\n1. Introduction\n\n Over the past few years, the Extensible Markup Language (XML)\n [W3C.REC-xml] has become a widely used method for data markup. There\n have already been several IETF Working Groups that have produced\n standards that define XML Document Type Definitions (DTDs), XML\n Namespaces [W3C.REC-xml-names], and XML Schemas [W3C.REC-xmlschema-\n 1]. Each one of these technologies uses Uniform Resource Identifiers\n (URIs) [RFC2396] and other standardized identifiers to identify\n various components.\n\n For example, while it has been the practice within some standards\n that use Document Type Definitions (DTDs) to forego the use of the\n PUBLIC iden","scope_keywords":["3688","http","key","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4991","folder":"IETF/RFC-4991","source":"IETF/RFC-4991/RFC-4991.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5277","folder":"IETF/RFC-5277","source":"IETF/RFC-5277/RFC-5277.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5717","folder":"IETF/RFC-5717","source":"IETF/RFC-5717/RFC-5717.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6243","folder":"IETF/RFC-6243","source":"IETF/RFC-6243/RFC-6243.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6321","folder":"IETF/RFC-6321","source":"IETF/RFC-6321/RFC-6321.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6685","folder":"IETF/RFC-6685","source":"IETF/RFC-6685/RFC-6685.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 3688 This document describes an IANA maintained registry for IETF\n standards which use Extensible Markup Language (XML) related items\n such as Namespaces, Document Type Declarations (DTDs), Schemas, and\n Resource Description Framework (RDF) Schemas.\n\n1. Introduction\n\n Over the past few years, the Extensible Markup Language (XML)\n [W3C.REC-xml] has become a widely used method for data markup. There\n have already been several IETF Working Groups that have produced\n standards that define XML Document Type Definitions (DTDs), XML\n Namespaces [W3C.REC-xml-names], and XML Schemas [W3C.REC-xmlschema-\n 1]. Each one of these technologies uses Uniform Resource Identifiers\n (URIs) [RFC2396] and other standardized identifiers to identify\n various components.\n\n For example, while it has been the practice within some standards\n that use Document Type Definitions (DTDs) to forego the use of the\n PUBLIC iden 3688 http key presentation registered nested-reference unchanged"},{"id":"IETF RFC 3689","type":"specification","body":"IETF","designation":"RFC 3689","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3689.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3689.txt","https://www.rfc-editor.org/rfc/rfc3689.pdf"],"folder":"IETF/RFC-3689","files":{"txt":{"path":"standards/IETF/RFC-3689/RFC-3689.txt","sha256":"5bfedbcc69e64e7651f34d1fc3703974ee3762d8e787f6db69878ad2cf007721"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a list of general requirements in support of\n Emergency Telecommunications Service (ETS). Solutions to these\n requirements are not presented in this document. Additional\n requirements pertaining to specific applications, or types of\n applications, are to be specified in separate document(s).\n\n1. Introduction\n\n Effective telecommunications capabilities can be imperative to\n facilitate immediate recovery operations for serious disaster events,\n such as, hurricanes, floods, earthquakes, and terrorist attacks.\n Disasters can happen any time, any place, unexpectedly. Quick\n response for recovery operations requires immediate access to any\n public telecommunications capabilities at hand. These capabilities\n include: conventional telephone, cellular phones, and Internet\n access via online terminals, IP telephones, and wireless PDAs. The\n commercial telecommunications infr","scope_keywords":["3689","key","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3690","folder":"IETF/RFC-3690","source":"IETF/RFC-3690/RFC-3690.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 3689 This document presents a list of general requirements in support of\n Emergency Telecommunications Service (ETS). Solutions to these\n requirements are not presented in this document. Additional\n requirements pertaining to specific applications, or types of\n applications, are to be specified in separate document(s).\n\n1. Introduction\n\n Effective telecommunications capabilities can be imperative to\n facilitate immediate recovery operations for serious disaster events,\n such as, hurricanes, floods, earthquakes, and terrorist attacks.\n Disasters can happen any time, any place, unexpectedly. Quick\n response for recovery operations requires immediate access to any\n public telecommunications capabilities at hand. These capabilities\n include: conventional telephone, cellular phones, and Internet\n access via online terminals, IP telephones, and wireless PDAs. The\n commercial telecommunications infr 3689 key management pid nested-reference unchanged"},{"id":"IETF RFC 3691","type":"specification","body":"IETF","designation":"RFC 3691","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3691.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3691.txt","https://www.rfc-editor.org/rfc/rfc3691.pdf"],"folder":"IETF/RFC-3691","files":{"txt":{"path":"standards/IETF/RFC-3691/RFC-3691.txt","sha256":"2d3527e0d7cb70a3877f77685d487eed5044671197fd5f437be4f7a540dd958b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an UNSELECT command that can be used to close\n the current mailbox in an Internet Message Access Protocol - version\n 4 (IMAP4) session without expunging it. Certain types of IMAP\n clients need to release resources associated with the selected\n mailbox without selecting a different mailbox. While IMAP4 provides\n this functionality (via a SELECT command with a nonexistent mailbox\n name or reselecting the same mailbox with EXAMINE command), a more\n clean solution is desirable.","scope_keywords":["3691","http","key","license","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 3691 This document defines an UNSELECT command that can be used to close\n the current mailbox in an Internet Message Access Protocol - version\n 4 (IMAP4) session without expunging it. Certain types of IMAP\n clients need to release resources associated with the selected\n mailbox without selecting a different mailbox. While IMAP4 provides\n this functionality (via a SELECT command with a nonexistent mailbox\n name or reselecting the same mailbox with EXAMINE command), a more\n clean solution is desirable. 3691 http key license registered subject nested-reference unchanged"},{"id":"IETF RFC 3693","type":"specification","body":"IETF","designation":"RFC 3693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3693.txt","https://www.rfc-editor.org/rfc/rfc3693.pdf"],"folder":"IETF/RFC-3693","files":{"txt":{"path":"standards/IETF/RFC-3693/RFC-3693.txt","sha256":"3afbcedfa3eeb58111afe6c3c2c9cabf2f1174bb8f71343318ec99fa42f5409e"}},"tags":["nested-reference","unchanged"],"summary":"Location-based services, navigation applications, emergency services,\n management of equipment in the field, and other location-dependent\n services need geographic location information about a Target (such as\n a user, resource or other entity). There is a need to securely\n gather and transfer location information for location services, while\n at the same time protect the privacy of the individuals involved.\n\n This document focuses on the authorization, security and privacy\n requirements for such location-dependent services. Specifically, it\n describes the requirements for the Geopriv Location Object (LO) and\n for the protocols that use this Location Object. This LO is\n envisioned to be the primary data structure used in all Geopriv\n protocol exchanges to securely transfer location data.\n\nCuellar, et al. Informational [Page 1]\n\f\nRFC 3693 Geopriv Requirements February 2004","scope_keywords":["3693","authentication","authorization","credential","credentials","key","management","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3694","folder":"IETF/RFC-3694","source":"IETF/RFC-3694/RFC-3694.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5069","folder":"IETF/RFC-5069","source":"IETF/RFC-5069/RFC-5069.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5808","folder":"IETF/RFC-5808","source":"IETF/RFC-5808/RFC-5808.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null}],"search_text":"IETF RFC 3693 Location-based services, navigation applications, emergency services,\n management of equipment in the field, and other location-dependent\n services need geographic location information about a Target (such as\n a user, resource or other entity). There is a need to securely\n gather and transfer location information for location services, while\n at the same time protect the privacy of the individuals involved.\n\n This document focuses on the authorization, security and privacy\n requirements for such location-dependent services. Specifically, it\n describes the requirements for the Geopriv Location Object (LO) and\n for the protocols that use this Location Object. This LO is\n envisioned to be the primary data structure used in all Geopriv\n protocol exchanges to securely transfer location data.\n\nCuellar, et al. Informational [Page 1]\n\f\nRFC 3693 Geopriv Requirements February 2004 3693 authentication authorization credential credentials key management policy trust nested-reference unchanged"},{"id":"IETF RFC 3706","type":"specification","body":"IETF","designation":"RFC 3706","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3706.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3706.txt","https://www.rfc-editor.org/rfc/rfc3706.pdf"],"folder":"IETF/RFC-3706","files":{"txt":{"path":"standards/IETF/RFC-3706/RFC-3706.txt","sha256":"8c8cd5bb95db7a9e7e72aab04938bf92a88232bd78086767c956c8a9e82a407e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the method detecting a dead Internet Key\n Exchange (IKE) peer that is presently in use by a number of vendors.\n The method, called Dead Peer Detection (DPD) uses IPSec traffic\n patterns to minimize the number of IKE messages that are needed to\n confirm liveness. DPD, like other keepalive mechanisms, is needed to\n determine when to perform IKE peer failover, and to reclaim lost\n resources.","scope_keywords":["3706","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3706 This document describes the method detecting a dead Internet Key\n Exchange (IKE) peer that is presently in use by a number of vendors.\n The method, called Dead Peer Detection (DPD) uses IPSec traffic\n patterns to minimize the number of IKE messages that are needed to\n confirm liveness. DPD, like other keepalive mechanisms, is needed to\n determine when to perform IKE peer failover, and to reclaim lost\n resources. 3706 key pid nested-reference unchanged"},{"id":"IETF RFC 3715","type":"specification","body":"IETF","designation":"RFC 3715","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3715.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3715.txt","https://www.rfc-editor.org/rfc/rfc3715.pdf"],"folder":"IETF/RFC-3715","files":{"txt":{"path":"standards/IETF/RFC-3715/RFC-3715.txt","sha256":"363a098ad373e005cad65f5b6dda85ff81c215272509054442bfbb18d4386a9f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes known incompatibilities between Network\n Address Translation (NAT) and IPsec, and describes the requirements\n for addressing them. Perhaps the most common use of IPsec is in\n providing virtual private networking capabilities. One very popular\n use of Virtual Private Networks (VPNs) is to provide telecommuter\n access to the corporate Intranet. Today, NATs are widely deployed in\n home gateways, as well as in other locations likely to be used by\n telecommuters, such as hotels. The result is that IPsec-NAT\n incompatibilities have become a major barrier in the deployment of\n IPsec in one of its principal uses.\n\nAboba & Dixon Informational [Page 1]\n\f\nRFC 3715 IPsec-NAT Compatibility Requirements March 2004","scope_keywords":["3715","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6346","folder":"IETF/RFC-6346","source":"IETF/RFC-6346/RFC-6346.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 3715 This document describes known incompatibilities between Network\n Address Translation (NAT) and IPsec, and describes the requirements\n for addressing them. Perhaps the most common use of IPsec is in\n providing virtual private networking capabilities. One very popular\n use of Virtual Private Networks (VPNs) is to provide telecommuter\n access to the corporate Intranet. Today, NATs are widely deployed in\n home gateways, as well as in other locations likely to be used by\n telecommuters, such as hotels. The result is that IPsec-NAT\n incompatibilities have become a major barrier in the deployment of\n IPsec in one of its principal uses.\n\nAboba & Dixon Informational [Page 1]\n\f\nRFC 3715 IPsec-NAT Compatibility Requirements March 2004 3715 algorithm key nested-reference unchanged"},{"id":"IETF RFC 3722","type":"specification","body":"IETF","designation":"RFC 3722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3722.txt","https://www.rfc-editor.org/rfc/rfc3722.pdf"],"folder":"IETF/RFC-3722","files":{"txt":{"path":"standards/IETF/RFC-3722/RFC-3722.txt","sha256":"9b5eaf0c4bfc7437b2962c4f3d5b7ae56ddd5c14f3d57009ae6b76baea44a80d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to prepare internationalized iSCSI names\n to increase the likelihood that name input and comparison work in\n ways that make sense for typical users throughout the world.\n\n The Internet Small Computer Systems Interface (iSCSI) protocol\n provides a way for hosts to access SCSI devices over an IP network.\n The iSCSI end-points, called initiators and targets, each have a\n globally-unique name that must be transcribable, as well as easily\n compared.\n\n1. Introduction\n\n The iSCSI protocol [RFC3720] provides a way for hosts to access SCSI\n [SAM2] devices over an IP network. The iSCSI end-points, called\n initiators and targets, each have a globally-unique name, defined in\n [RFC3721].\n\n An iSCSI name is a string of UTF-8 [RFC3629] characters that includes\n a type designator, a naming authority based on domain names, and a\n unique part within the naming authority. The un","scope_keywords":["3722","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null}],"search_text":"IETF RFC 3722 This document describes how to prepare internationalized iSCSI names\n to increase the likelihood that name input and comparison work in\n ways that make sense for typical users throughout the world.\n\n The Internet Small Computer Systems Interface (iSCSI) protocol\n provides a way for hosts to access SCSI devices over an IP network.\n The iSCSI end-points, called initiators and targets, each have a\n globally-unique name that must be transcribable, as well as easily\n compared.\n\n1. Introduction\n\n The iSCSI protocol [RFC3720] provides a way for hosts to access SCSI\n [SAM2] devices over an IP network. The iSCSI end-points, called\n initiators and targets, each have a globally-unique name, defined in\n [RFC3721].\n\n An iSCSI name is a string of UTF-8 [RFC3629] characters that includes\n a type designator, a naming authority based on domain names, and a\n unique part within the naming authority. The un 3722 key profile nested-reference unchanged"},{"id":"IETF RFC 3725","type":"specification","body":"IETF","designation":"RFC 3725","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3725.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3725.txt","https://www.rfc-editor.org/rfc/rfc3725.pdf"],"folder":"IETF/RFC-3725","files":{"txt":{"path":"standards/IETF/RFC-3725/RFC-3725.txt","sha256":"28b5bb61c0a9aeedb3142b6df902cffb711f97e333544b4a7c56ce784fbb940c"}},"tags":["nested-reference","unchanged"],"summary":"Third party call control refers to the ability of one entity to\n create a call in which communication is actually between other\n parties. Third party call control is possible using the mechanisms\n specified within the Session Initiation Protocol (SIP). However,\n there are several possible approaches, each with different benefits\n and drawbacks. This document discusses best current practices for\n the usage of SIP for third party call control.","scope_keywords":["3725","authentication","authorization","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3893","folder":"IETF/RFC-3893","source":"IETF/RFC-3893/RFC-3893.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4032","folder":"IETF/RFC-4032","source":"IETF/RFC-4032/RFC-4032.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 3725 Third party call control refers to the ability of one entity to\n create a call in which communication is actually between other\n parties. Third party call control is possible using the mechanisms\n specified within the Session Initiation Protocol (SIP). However,\n there are several possible approaches, each with different benefits\n and drawbacks. This document discusses best current practices for\n the usage of SIP for third party call control. 3725 authentication authorization encryption key nested-reference unchanged"},{"id":"IETF RFC 3726","type":"specification","body":"IETF","designation":"RFC 3726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3726.txt","https://www.rfc-editor.org/rfc/rfc3726.pdf"],"folder":"IETF/RFC-3726","files":{"txt":{"path":"standards/IETF/RFC-3726/RFC-3726.txt","sha256":"519552dc503f5942358b96ac5c8ca4d73609f33370f48e9b057f599d72998807"}},"tags":["nested-reference","unchanged"],"summary":"This document defines requirements for signaling across different\n network environments, such as across administrative and/or technology\n domains. Signaling is mainly considered for Quality of Service (Qos)\n such as the Resource Reservation Protocol (RSVP). However, in recent\n years, several other applications of signaling have been defined.\n For example, signaling for label distribution in Multiprotocol Label\n Switching (MPLS) or signaling to middleboxes. To achieve wide\n applicability of the requirements, the starting point is a diverse\n set of scenarios/use cases concerning various types of networks and\n application interactions. This document presents the assumptions\n before listing the requirements. The requirements are grouped\n according to areas such as architecture and design goals, signaling\n flows, layering, performance, flexibility, security, and mobility.\n\nBrunner Information","scope_keywords":["3726","authentication","authorization","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 3726 This document defines requirements for signaling across different\n network environments, such as across administrative and/or technology\n domains. Signaling is mainly considered for Quality of Service (Qos)\n such as the Resource Reservation Protocol (RSVP). However, in recent\n years, several other applications of signaling have been defined.\n For example, signaling for label distribution in Multiprotocol Label\n Switching (MPLS) or signaling to middleboxes. To achieve wide\n applicability of the requirements, the starting point is a diverse\n set of scenarios/use cases concerning various types of networks and\n application interactions. This document presents the assumptions\n before listing the requirements. The requirements are grouped\n according to areas such as architecture and design goals, signaling\n flows, layering, performance, flexibility, security, and mobility.\n\nBrunner Information 3726 authentication authorization identification key path nested-reference unchanged"},{"id":"IETF RFC 3730","type":"specification","body":"IETF","designation":"RFC 3730","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3730.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3730.txt","https://www.rfc-editor.org/rfc/rfc3730.pdf"],"folder":"IETF/RFC-3730","files":{"txt":{"path":"standards/IETF/RFC-3730/RFC-3730.txt","sha256":"4af21712a4c71982157dada5f4ac6e8b0410e0ba03ae225ee285d5941a3a2dfb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration.","scope_keywords":["3730","authentication","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null}],"search_text":"IETF RFC 3730 This document describes an application layer client-server protocol\n for the provisioning and management of objects stored in a shared\n central repository. Specified in XML, the protocol defines generic\n object management operations and an extensible framework that maps\n protocol operations to objects. This document includes a protocol\n specification, an object mapping template, and an XML media type\n registration. 3730 authentication identification key management nested-reference unchanged"},{"id":"IETF RFC 3733","type":"specification","body":"IETF","designation":"RFC 3733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3733.txt","https://www.rfc-editor.org/rfc/rfc3733.pdf"],"folder":"IETF/RFC-3733","files":{"txt":{"path":"standards/IETF/RFC-3733/RFC-3733.txt","sha256":"ef5dd760c619c2151627418a343cf6f71af286533a6544479d17622dfb9f84ef"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts.","scope_keywords":["3733","attribute","attributes","authorization","key","management","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null}],"search_text":"IETF RFC 3733 This document describes an Extensible Provisioning Protocol (EPP)\n mapping for the provisioning and management of individual or\n organizational social information identifiers (known as \"contacts\")\n stored in a shared central repository. Specified in Extensible\n Markup Language (XML), the mapping defines EPP command syntax and\n semantics as applied to contacts. 3733 attribute attributes authorization key management policies subject nested-reference unchanged"},{"id":"IETF RFC 3734","type":"specification","body":"IETF","designation":"RFC 3734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3734.txt","https://www.rfc-editor.org/rfc/rfc3734.pdf"],"folder":"IETF/RFC-3734","files":{"txt":{"path":"standards/IETF/RFC-3734/RFC-3734.txt","sha256":"525ab6d9f5b55868d1e21152d7c7e517259360c1ec9d5f6043758d3722b6d476"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server.","scope_keywords":["3734","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3734 This document describes how an Extensible Provisioning Protocol (EPP)\n session is mapped onto a single Transmission Control Protocol (TCP)\n connection. This mapping requires use of the Transport Layer\n Security (TLS) protocol to protect information exchanged between an\n EPP client and an EPP server. 3734 key management tls nested-reference unchanged"},{"id":"IETF RFC 3735","type":"specification","body":"IETF","designation":"RFC 3735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3735.txt","https://www.rfc-editor.org/rfc/rfc3735.pdf"],"folder":"IETF/RFC-3735","files":{"txt":{"path":"standards/IETF/RFC-3735/RFC-3735.txt","sha256":"d60b9281eb754ca9f5cbd090103e1982dc37ee6df91a3b6a26b1043e83bc8689"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Provisioning Protocol (EPP) is an application layer\n client-server protocol for the provisioning and management of objects\n stored in a shared central repository. Specified in XML, the\n protocol defines generic object management operations and an\n extensible framework that maps protocol operations to objects. This\n document presents guidelines for use of EPP's extension mechanisms to\n define new features and object management capabilities.","scope_keywords":["3735","authentication","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 3735 The Extensible Provisioning Protocol (EPP) is an application layer\n client-server protocol for the provisioning and management of objects\n stored in a shared central repository. Specified in XML, the\n protocol defines generic object management operations and an\n extensible framework that maps protocol operations to objects. This\n document presents guidelines for use of EPP's extension mechanisms to\n define new features and object management capabilities. 3735 authentication key management presentation nested-reference unchanged"},{"id":"IETF RFC 3739","type":"specification","body":"IETF","designation":"RFC 3739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3739.txt","https://www.rfc-editor.org/rfc/rfc3739.pdf"],"folder":"IETF/RFC-3739","files":{"txt":{"path":"standards/IETF/RFC-3739/RFC-3739.txt","sha256":"1862b088f0f96eecdfc368aa54efa2656663077acdcbd1fc1a2b04baabc63d5d"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This document forms a certificate profile, based on RFC 3280, for\n identity certificates issued to natural persons.\n\n The profile defines specific conventions for certificates that are\n qualified within a defined legal framework, named Qualified\n Certificates. However, the profile does not define any legal\n requirements for such Qualified Certificates.\n\n The goal of this document is to define a certificate profile that\n supports the issuance of Qualified Certificates independent of local\n legal requirements. The profile is however not limited to Qualified\n Certificates and further profiling may facilitate specific local\n needs.\n\nSantesson, et al. Standards Track [Page 1]\n\f\nRFC 3739 Qualified Certificates Profile March 2004","scope_keywords":["3739","attribute","attributes","certificate","certificates","issuer","key","pki","policies","policy","profile","profiles","qualified","signature","subject"],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 3739 This document forms a certificate profile, based on RFC 3280, for\n identity certificates issued to natural persons.\n\n The profile defines specific conventions for certificates that are\n qualified within a defined legal framework, named Qualified\n Certificates. However, the profile does not define any legal\n requirements for such Qualified Certificates.\n\n The goal of this document is to define a certificate profile that\n supports the issuance of Qualified Certificates independent of local\n legal requirements. The profile is however not limited to Qualified\n Certificates and further profiling may facilitate specific local\n needs.\n\nSantesson, et al. Standards Track [Page 1]\n\f\nRFC 3739 Qualified Certificates Profile March 2004 3739 attribute attributes certificate certificates issuer key pki policies policy profile profiles qualified signature subject cited-by-eu-law implementing-regulation nested-reference unchanged 2025-1929 Qualified electronic time stamps 32025R1929"},{"id":"IETF RFC 3741","type":"specification","body":"IETF","designation":"RFC 3741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3741.txt","https://www.rfc-editor.org/rfc/rfc3741.pdf"],"folder":"IETF/RFC-3741","files":{"txt":{"path":"standards/IETF/RFC-3741/RFC-3741.txt","sha256":"454e0cd27150271e8e85f9f5a1c4a287b90b8c6feb558e5ce521c933fd1491c4"}},"tags":["nested-reference","unchanged"],"summary":"Canonical XML specifies a standard serialization of XML that, when\n applied to a subdocument, includes the subdocument's ancestor context\n including all of the namespace declarations and attributes in the\n \"xml:\" namespace. However, some applications require a method which,\n to the extent practical, excludes ancestor context from a\n canonicalized subdocument. For example, one might require a digital\n signature over an XML payload (subdocument) in an XML message that\n will not break when that subdocument is removed from its original\n message and/or inserted into a different context. This requirement\n is satisfied by Exclusive XML Canonicalization.","scope_keywords":["3741","attribute","attributes","http","key","path","presentation","qualified","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 3741 Canonical XML specifies a standard serialization of XML that, when\n applied to a subdocument, includes the subdocument's ancestor context\n including all of the namespace declarations and attributes in the\n \"xml:\" namespace. However, some applications require a method which,\n to the extent practical, excludes ancestor context from a\n canonicalized subdocument. For example, one might require a digital\n signature over an XML payload (subdocument) in an XML message that\n will not break when that subdocument is removed from its original\n message and/or inserted into a different context. This requirement\n is satisfied by Exclusive XML Canonicalization. 3741 attribute attributes http key path presentation qualified signature nested-reference unchanged"},{"id":"IETF RFC 3744","type":"specification","body":"IETF","designation":"RFC 3744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3744.txt","https://www.rfc-editor.org/rfc/rfc3744.pdf"],"folder":"IETF/RFC-3744","files":{"txt":{"path":"standards/IETF/RFC-3744/RFC-3744.txt","sha256":"7b6caed842bce2e2c8278aba5bce6a027dd2b2a0a718301d8c7f7069236f7959"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of methods, headers, message bodies,\n properties, and reports that define Access Control extensions to the\n WebDAV Distributed Authoring Protocol. This protocol permits a\n client to read and modify access control lists that instruct a server\n whether to allow or deny operations upon a resource (such as\n HyperText Transfer Protocol (HTTP) method invocations) by a given\n principal. A lightweight representation of principals as Web\n resources supports integration of a wide range of user management\n repositories. Search operations allow discovery and manipulation of\n principals using human names.\n\nClemm, et al. Standards Track [Page 1]\n\f\nRFC 3744 WebDAV Access Control Protocol May 2004","scope_keywords":["3744","http","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5397","folder":"IETF/RFC-5397","source":"IETF/RFC-5397/RFC-5397.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null}],"search_text":"IETF RFC 3744 This document specifies a set of methods, headers, message bodies,\n properties, and reports that define Access Control extensions to the\n WebDAV Distributed Authoring Protocol. This protocol permits a\n client to read and modify access control lists that instruct a server\n whether to allow or deny operations upon a resource (such as\n HyperText Transfer Protocol (HTTP) method invocations) by a given\n principal. A lightweight representation of principals as Web\n resources supports integration of a wide range of user management\n repositories. Search operations allow discovery and manipulation of\n principals using human names.\n\nClemm, et al. Standards Track [Page 1]\n\f\nRFC 3744 WebDAV Access Control Protocol May 2004 3744 http management presentation nested-reference unchanged"},{"id":"IETF RFC 3757","type":"specification","body":"IETF","designation":"RFC 3757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3757.txt","https://www.rfc-editor.org/rfc/rfc3757.pdf"],"folder":"IETF/RFC-3757","files":{"txt":{"path":"standards/IETF/RFC-3757/RFC-3757.txt","sha256":"47c402ead1d318467142f43228e70ebacd1d277279da2ce73ecc19d897ca2b1e"}},"tags":["nested-reference","unchanged"],"summary":"With the Delegation Signer (DS) resource record (RR), the concept of\n a public key acting as a secure entry point (SEP) has been\n introduced. During exchanges of public keys with the parent there is\n a need to differentiate SEP keys from other public keys in the Domain\n Name System KEY (DNSKEY) resource record set. A flag bit in the\n DNSKEY RR is defined to indicate that DNSKEY is to be used as a SEP.\n The flag bit is intended to assist in operational procedures to\n correctly generate DS resource records, or to indicate what DNSKEYs\n are intended for static configuration. The flag bit is not to be\n used in the DNS verification protocol. This document updates RFC\n 2535 and RFC 3755.\n\nKolkman, et al. Standard Track [Page 1]\n\f\nRFC 3757 DNSKEY RR SEP Flag April 2004","scope_keywords":["3757","algorithm","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4033","folder":"IETF/RFC-4033","source":"IETF/RFC-4033/RFC-4033.txt","version":null},{"body":"IETF","designation":"RFC 4034","folder":"IETF/RFC-4034","source":"IETF/RFC-4034/RFC-4034.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 3757 With the Delegation Signer (DS) resource record (RR), the concept of\n a public key acting as a secure entry point (SEP) has been\n introduced. During exchanges of public keys with the parent there is\n a need to differentiate SEP keys from other public keys in the Domain\n Name System KEY (DNSKEY) resource record set. A flag bit in the\n DNSKEY RR is defined to indicate that DNSKEY is to be used as a SEP.\n The flag bit is intended to assist in operational procedures to\n correctly generate DS resource records, or to indicate what DNSKEYs\n are intended for static configuration. The flag bit is not to be\n used in the DNS verification protocol. This document updates RFC\n 2535 and RFC 3755.\n\nKolkman, et al. Standard Track [Page 1]\n\f\nRFC 3757 DNSKEY RR SEP Flag April 2004 3757 algorithm key keys trust nested-reference unchanged"},{"id":"IETF RFC 3758","type":"specification","body":"IETF","designation":"RFC 3758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3758.txt","https://www.rfc-editor.org/rfc/rfc3758.pdf"],"folder":"IETF/RFC-3758","files":{"txt":{"path":"standards/IETF/RFC-3758/RFC-3758.txt","sha256":"4441419d5a0faf5d1b7560b23d151d820469ccdd7bf7f4e8ab218e87c82abba9"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an extension to the Stream Control Transmission\n Protocol (SCTP) that allows an SCTP endpoint to signal to its peer\n that it should move the cumulative ack point forward. When both\n sides of an SCTP association support this extension, it can be used\n by an SCTP implementation to provide partially reliable data\n transmission service to an upper layer protocol. This memo describes\n the protocol extensions, which consist of a new parameter for INIT\n and INIT ACK, and a new FORWARD TSN chunk type, and provides one\n example of a partially reliable service that can be provided to the\n upper layer via this mechanism.\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 3758 SCTP Partial Reliability Extension May 2004","scope_keywords":["3758"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4336","folder":"IETF/RFC-4336","source":"IETF/RFC-4336/RFC-4336.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7496","folder":"IETF/RFC-7496","source":"IETF/RFC-7496/RFC-7496.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null}],"search_text":"IETF RFC 3758 This memo describes an extension to the Stream Control Transmission\n Protocol (SCTP) that allows an SCTP endpoint to signal to its peer\n that it should move the cumulative ack point forward. When both\n sides of an SCTP association support this extension, it can be used\n by an SCTP implementation to provide partially reliable data\n transmission service to an upper layer protocol. This memo describes\n the protocol extensions, which consist of a new parameter for INIT\n and INIT ACK, and a new FORWARD TSN chunk type, and provides one\n example of a partially reliable service that can be provided to the\n upper layer via this mechanism.\n\nStewart, et al. Standards Track [Page 1]\n\f\nRFC 3758 SCTP Partial Reliability Extension May 2004 3758 nested-reference unchanged"},{"id":"IETF RFC 3761","type":"specification","body":"IETF","designation":"RFC 3761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3761.txt","https://www.rfc-editor.org/rfc/rfc3761.pdf"],"folder":"IETF/RFC-3761","files":{"txt":{"path":"standards/IETF/RFC-3761/RFC-3761.txt","sha256":"a593d90e8defec8058c7127553e712985fc3453d43c8c23b018ab04ba2e041d3"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the use of the Domain Name System (DNS) for\n storage of E.164 numbers. More specifically, how DNS can be used for\n identifying available services connected to one E.164 number. It\n specifically obsoletes RFC 2916 to bring it in line with the Dynamic\n Delegation Discovery System (DDDS) Application specification found in\n the document series specified in RFC 3401. It is very important to\n note that it is impossible to read and understand this document\n without reading the documents discussed in RFC 3401.","scope_keywords":["3761","algorithm","holder","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3764","folder":"IETF/RFC-3764","source":"IETF/RFC-3764/RFC-3764.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4143","folder":"IETF/RFC-4143","source":"IETF/RFC-4143/RFC-4143.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4759","folder":"IETF/RFC-4759","source":"IETF/RFC-4759/RFC-4759.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 3761 This document discusses the use of the Domain Name System (DNS) for\n storage of E.164 numbers. More specifically, how DNS can be used for\n identifying available services connected to one E.164 number. It\n specifically obsoletes RFC 2916 to bring it in line with the Dynamic\n Delegation Discovery System (DDDS) Application specification found in\n the document series specified in RFC 3401. It is very important to\n note that it is impossible to read and understand this document\n without reading the documents discussed in RFC 3401. 3761 algorithm holder key management policies policy nested-reference unchanged"},{"id":"IETF RFC 3767","type":"specification","body":"IETF","designation":"RFC 3767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3767.txt","https://www.rfc-editor.org/rfc/rfc3767.pdf"],"folder":"IETF/RFC-3767","files":{"txt":{"path":"standards/IETF/RFC-3767/RFC-3767.txt","sha256":"d58275819bea256b2dedd3af9979f05208ac1173380156fc3d41aced06a6ce8c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol whereby a user can acquire\n cryptographic credentials (e.g., private keys, PKCS #15 structures)\n from a credential server, using a workstation that has locally\n trusted software installed, but with no user-specific configuration.\n The protocol's payloads are described in XML. This memo also\n specifies a Blocks Extensible Exchange Protocol (BEEP) profile of the\n protocol. Security requirements are met by mandating support for\n TLS and/or DIGEST-MD5 (through BEEP).","scope_keywords":["3767","authentication","certificate","certificates","credential","credentials","hash","key","keys","management","profile","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3767 This document describes a protocol whereby a user can acquire\n cryptographic credentials (e.g., private keys, PKCS #15 structures)\n from a credential server, using a workstation that has locally\n trusted software installed, but with no user-specific configuration.\n The protocol's payloads are described in XML. This memo also\n specifies a Blocks Extensible Exchange Protocol (BEEP) profile of the\n protocol. Security requirements are met by mandating support for\n TLS and/or DIGEST-MD5 (through BEEP). 3767 authentication certificate certificates credential credentials hash key keys management profile tls trust nested-reference unchanged"},{"id":"IETF RFC 3771","type":"specification","body":"IETF","designation":"RFC 3771","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3771.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3771.txt","https://www.rfc-editor.org/rfc/rfc3771.pdf"],"folder":"IETF/RFC-3771","files":{"txt":{"path":"standards/IETF/RFC-3771/RFC-3771.txt","sha256":"893e3b5cd2a49718b92f871069c97c196fe930bc73cc024419841516e53f4014"}},"tags":["nested-reference","unchanged"],"summary":"This document defines and describes the IntermediateResponse message,\n a general mechanism for defining single-request/multiple-response\n operations in Lightweight Directory Access Protocol (LDAP). The\n IntermediateResponse message is defined in such a way that the\n protocol behavior of existing LDAP operations is maintained. This\n message is intended to be used in conjunction with the LDAP\n ExtendedRequest and ExtendedResponse to define new single-\n request/multiple-response operations or in conjunction with a control\n when extending existing LDAP operations in a way that requires them\n to return intermediate response information.\n\nHarrison & Zeilenga Standards Track [Page 1]\n\f\nRFC 3771 LDAP Intermediate Response April 2004\n\n1. Introduction\n\n The Lightweight Directory Access Protocol (LDAP), version 3 [RFC3377]\n is an extensible protocol. Extended operations ([RFC2251] Section\n 4.12) ar","scope_keywords":["3771","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null}],"search_text":"IETF RFC 3771 This document defines and describes the IntermediateResponse message,\n a general mechanism for defining single-request/multiple-response\n operations in Lightweight Directory Access Protocol (LDAP). The\n IntermediateResponse message is defined in such a way that the\n protocol behavior of existing LDAP operations is maintained. This\n message is intended to be used in conjunction with the LDAP\n ExtendedRequest and ExtendedResponse to define new single-\n request/multiple-response operations or in conjunction with a control\n when extending existing LDAP operations in a way that requires them\n to return intermediate response information.\n\nHarrison & Zeilenga Standards Track [Page 1]\n\f\nRFC 3771 LDAP Intermediate Response April 2004\n\n1. Introduction\n\n The Lightweight Directory Access Protocol (LDAP), version 3 [RFC3377]\n is an extensible protocol. Extended operations ([RFC2251] Section\n 4.12) ar 3771 key nested-reference unchanged"},{"id":"IETF RFC 3776","type":"specification","body":"IETF","designation":"RFC 3776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3776.txt","https://www.rfc-editor.org/rfc/rfc3776.pdf"],"folder":"IETF/RFC-3776","files":{"txt":{"path":"standards/IETF/RFC-3776/RFC-3776.txt","sha256":"b585db53416c7844fede99411675db639516304303817bcf9a6957868eb11f42"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 uses IPsec to protect signaling between the home agent\n and the mobile node. Mobile IPv6 base document defines the main\n requirements these nodes must follow. This document discusses these\n requirements in more depth, illustrates the used packet formats,\n describes suitable configuration procedures, and shows how\n implementations can process the packets in the right order.","scope_keywords":["3776","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4225","folder":"IETF/RFC-4225","source":"IETF/RFC-4225/RFC-4225.txt","version":null},{"body":"IETF","designation":"RFC 4283","folder":"IETF/RFC-4283","source":"IETF/RFC-4283/RFC-4283.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 3776 Mobile IPv6 uses IPsec to protect signaling between the home agent\n and the mobile node. Mobile IPv6 base document defines the main\n requirements these nodes must follow. This document discusses these\n requirements in more depth, illustrates the used packet formats,\n describes suitable configuration procedures, and shows how\n implementations can process the packets in the right order. 3776 key policy nested-reference unchanged"},{"id":"IETF RFC 3781","type":"specification","body":"IETF","designation":"RFC 3781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3781.txt","https://www.rfc-editor.org/rfc/rfc3781.pdf"],"folder":"IETF/RFC-3781","files":{"txt":{"path":"standards/IETF/RFC-3781/RFC-3781.txt","sha256":"905ce7271dde9fc4109fa5ea513b3f0541b23b3a044e1c26b84bb1fd82a9bb87"}},"tags":["nested-reference","unchanged"],"summary":"SMIng (Structure of Management Information, Next Generation)\n (RFC3780), is a protocol-independent data definition language for\n management information. This memo defines an SMIng language\n extension that specifies the mapping of SMIng definitions of\n identities, classes, and their attributes and events to dedicated\n definitions of nodes, scalar objects, tables and columnar objects,\n and notifications, for application to the SNMP management framework.","scope_keywords":["3781","attribute","attributes","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null}],"search_text":"IETF RFC 3781 SMIng (Structure of Management Information, Next Generation)\n (RFC3780), is a protocol-independent data definition language for\n management information. This memo defines an SMIng language\n extension that specifies the mapping of SMIng definitions of\n identities, classes, and their attributes and events to dedicated\n definitions of nodes, scalar objects, tables and columnar objects,\n and notifications, for application to the SNMP management framework. 3781 attribute attributes key management nested-reference unchanged"},{"id":"IETF RFC 3783","type":"specification","body":"IETF","designation":"RFC 3783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3783.txt","https://www.rfc-editor.org/rfc/rfc3783.pdf"],"folder":"IETF/RFC-3783","files":{"txt":{"path":"standards/IETF/RFC-3783/RFC-3783.txt","sha256":"52047cabd92b172e814d76fdf171819bf22881623b8176abeb1cf9e11e901c0b"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer Systems Interface (iSCSI) is a Small Computer\n Systems Interface (SCSI) transport protocol designed to run on top of\n TCP. The iSCSI session abstraction is equivalent to the classic SCSI\n \"I_T nexus\", which represents the logical relationship between an\n Initiator and a Target (I and T) required in order to communicate via\n the SCSI family of protocols. The iSCSI session provides an ordered\n command delivery from the SCSI initiator to the SCSI target. This\n document goes into the design considerations that led to the iSCSI\n session model as it is defined today, relates the SCSI command\n ordering features defined in T10 specifications to the iSCSI\n concepts, and finally provides guidance to system designers on how\n true command ordering solutions can be built based on iSCSI.","scope_keywords":["3783","attribute","attributes","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 3783 Internet Small Computer Systems Interface (iSCSI) is a Small Computer\n Systems Interface (SCSI) transport protocol designed to run on top of\n TCP. The iSCSI session abstraction is equivalent to the classic SCSI\n \"I_T nexus\", which represents the logical relationship between an\n Initiator and a Target (I and T) required in order to communicate via\n the SCSI family of protocols. The iSCSI session provides an ordered\n command delivery from the SCSI initiator to the SCSI target. This\n document goes into the design considerations that led to the iSCSI\n session model as it is defined today, relates the SCSI command\n ordering features defined in T10 specifications to the iSCSI\n concepts, and finally provides guidance to system designers on how\n true command ordering solutions can be built based on iSCSI. 3783 attribute attributes delivery presentation nested-reference unchanged"},{"id":"IETF RFC 3803","type":"specification","body":"IETF","designation":"RFC 3803","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3803.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3803.txt","https://www.rfc-editor.org/rfc/rfc3803.pdf"],"folder":"IETF/RFC-3803","files":{"txt":{"path":"standards/IETF/RFC-3803/RFC-3803.txt","sha256":"21d77ac21a37e2f62e18dc242b77b79753edd67ea7fe1419e10514ddb51944f6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*).\n\n1. Introduction\n\n This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*). The length of time is represented in seconds\n without any units indication. This document obsoletes RFC 2424.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [REQ].\n\n2. Content-Duration Header Field\n\n Time varying media contents, for example, a spoken voice message or a\n video clip, have an inherent time duration. Many audio and video\n encodings may include their duration as header information or may\n allow accurate calculat","scope_keywords":["3803","http","identification","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"IETF RFC 3803 This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*).\n\n1. Introduction\n\n This document describes the MIME header Content-Duration that is\n intended for use with any time varying media content (typically\n audio/* or video/*). The length of time is represented in seconds\n without any units indication. This document obsoletes RFC 2424.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in RFC 2119 [REQ].\n\n2. Content-Duration Header Field\n\n Time varying media contents, for example, a spoken voice message or a\n video clip, have an inherent time duration. Many audio and video\n encodings may include their duration as header information or may\n allow accurate calculat 3803 http identification key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 3806","type":"specification","body":"IETF","designation":"RFC 3806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3806.txt","https://www.rfc-editor.org/rfc/rfc3806.pdf"],"folder":"IETF/RFC-3806","files":{"txt":{"path":"standards/IETF/RFC-3806/RFC-3806.txt","sha256":"8b76d5abcd907862c5eeef6558515a5752bbffccaf8a7836c528511e553013b9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a MIB module for the management of printer\n finishing device subunits. The finishing device subunits applicable\n to this MIB are an integral part of the Printer System. This MIB\n applies only to a Finisher Device that is connected to a Printer\n System.\n\nBergman, et al. Informational [Page 1]\n\f\nRFC 3806 Printer Finishing MIB June 2004","scope_keywords":["3806","attribute","attributes","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"IETF RFC 3806 This document defines a MIB module for the management of printer\n finishing device subunits. The finishing device subunits applicable\n to this MIB are an integral part of the Printer System. This MIB\n applies only to a Finisher Device that is connected to a Printer\n System.\n\nBergman, et al. Informational [Page 1]\n\f\nRFC 3806 Printer Finishing MIB June 2004 3806 attribute attributes http key management nested-reference unchanged"},{"id":"IETF RFC 3810","type":"specification","body":"IETF","designation":"RFC 3810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3810.txt","https://www.rfc-editor.org/rfc/rfc3810.pdf"],"folder":"IETF/RFC-3810","files":{"txt":{"path":"standards/IETF/RFC-3810/RFC-3810.txt","sha256":"510adaf152cc854cd3d0c6f734bd98c77561e70cbaec5ce4ce594fe9daec771d"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 2710, and it specifies Version 2 of the\n Multicast Listener Discovery Protocol (MLDv2). MLD is used by an\n IPv6 router to discover the presence of multicast listeners on\n directly attached links, and to discover which multicast addresses\n are of interest to those neighboring nodes. MLDv2 is designed to be\n interoperable with MLDv1. MLDv2 adds the ability for a node to\n report interest in listening to packets with a particular multicast\n address only from specific source addresses or from all sources\n except for specific source addresses.\n\nVida & Costa Standards Track [Page 1]\n\f\nRFC 3810 MLDv2 for IPv6 June 2004","scope_keywords":["3810","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3776","folder":"IETF/RFC-3776","source":"IETF/RFC-3776/RFC-3776.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4045","folder":"IETF/RFC-4045","source":"IETF/RFC-4045/RFC-4045.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4286","folder":"IETF/RFC-4286","source":"IETF/RFC-4286/RFC-4286.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4541","folder":"IETF/RFC-4541","source":"IETF/RFC-4541/RFC-4541.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4605","folder":"IETF/RFC-4605","source":"IETF/RFC-4605/RFC-4605.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4890","folder":"IETF/RFC-4890","source":"IETF/RFC-4890/RFC-4890.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5121","folder":"IETF/RFC-5121","source":"IETF/RFC-5121/RFC-5121.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6224","folder":"IETF/RFC-6224","source":"IETF/RFC-6224/RFC-6224.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 3810 This document updates RFC 2710, and it specifies Version 2 of the\n Multicast Listener Discovery Protocol (MLDv2). MLD is used by an\n IPv6 router to discover the presence of multicast listeners on\n directly attached links, and to discover which multicast addresses\n are of interest to those neighboring nodes. MLDv2 is designed to be\n interoperable with MLDv1. MLDv2 adds the ability for a node to\n report interest in listening to packets with a particular multicast\n address only from specific source addresses or from all sources\n except for specific source addresses.\n\nVida & Costa Standards Track [Page 1]\n\f\nRFC 3810 MLDv2 for IPv6 June 2004 3810 key nested-reference unchanged"},{"id":"IETF RFC 3812","type":"specification","body":"IETF","designation":"RFC 3812","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3812.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3812.txt","https://www.rfc-editor.org/rfc/rfc3812.pdf"],"folder":"IETF/RFC-3812","files":{"txt":{"path":"standards/IETF/RFC-3812/RFC-3812.txt","sha256":"5fe9dadaf51390c048fbd6e67228a642551dfc5c08bdc38339269daf7fb3aee0"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Multiprotocol Label\n Switching (MPLS) based traffic engineering (TE).","scope_keywords":["3812","crl","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3813","folder":"IETF/RFC-3813","source":"IETF/RFC-3813/RFC-3813.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null}],"search_text":"IETF RFC 3812 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Multiprotocol Label\n Switching (MPLS) based traffic engineering (TE). 3812 crl key management nested-reference unchanged"},{"id":"IETF RFC 3813","type":"specification","body":"IETF","designation":"RFC 3813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3813.txt","https://www.rfc-editor.org/rfc/rfc3813.pdf"],"folder":"IETF/RFC-3813","files":{"txt":{"path":"standards/IETF/RFC-3813/RFC-3813.txt","sha256":"b3f0a9230ed6641e226c460f4d19cd81f8924654621ec5e99f588281ad80c43c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor a Multiprotocol Label Switching (MPLS) Label Switching Router\n (LSR).\n\nSrinivasan, et al. Standards Track [Page 1]\n\f\nRFC 3813 MPLS LSR MIB June 2004","scope_keywords":["3813","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3812","folder":"IETF/RFC-3812","source":"IETF/RFC-3812/RFC-3812.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4365","folder":"IETF/RFC-4365","source":"IETF/RFC-4365/RFC-4365.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null}],"search_text":"IETF RFC 3813 This memo defines an portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor a Multiprotocol Label Switching (MPLS) Label Switching Router\n (LSR).\n\nSrinivasan, et al. Standards Track [Page 1]\n\f\nRFC 3813 MPLS LSR MIB June 2004 3813 key management path nested-reference unchanged"},{"id":"IETF RFC 3822","type":"specification","body":"IETF","designation":"RFC 3822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3822.txt","https://www.rfc-editor.org/rfc/rfc3822.pdf"],"folder":"IETF/RFC-3822","files":{"txt":{"path":"standards/IETF/RFC-3822/RFC-3822.txt","sha256":"8797221895bbac97e7d268a33253cd6cc2929625e81bc1aacee74e823cc24a08"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the use of Service Location Protocol version 2\n (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities.\n\n1. Introduction\n\n This document describes the use of the Service Location Protocol\n version 2 in performing dynamic discovery of participating Fibre\n Channel over TCP/IP (FCIP) Entities. Implementation guidelines,\n service type templates, and security considerations are specified.\n\n2. Notation Conventions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n3. Terminology\n\n Here are some definitions that may aid readers that are unfamiliar\n with either SLP or FCIP. Some of these definitions have been\n reproduced from [RFC2608] and [RFC3105].\n\nPeterson Standards Track [Page 1]\n\f\nRFC 3822 Finding FCIP Entities Using SLPv2 ","scope_keywords":["3822","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 3822 This document defines the use of Service Location Protocol version 2\n (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities.\n\n1. Introduction\n\n This document describes the use of the Service Location Protocol\n version 2 in performing dynamic discovery of participating Fibre\n Channel over TCP/IP (FCIP) Entities. Implementation guidelines,\n service type templates, and security considerations are specified.\n\n2. Notation Conventions\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n3. Terminology\n\n Here are some definitions that may aid readers that are unfamiliar\n with either SLP or FCIP. Some of these definitions have been\n reproduced from [RFC2608] and [RFC3105].\n\nPeterson Standards Track [Page 1]\n\f\nRFC 3822 Finding FCIP Entities Using SLPv2  3822 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 3826","type":"specification","body":"IETF","designation":"RFC 3826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3826.txt","https://www.rfc-editor.org/rfc/rfc3826.pdf"],"folder":"IETF/RFC-3826","files":{"txt":{"path":"standards/IETF/RFC-3826/RFC-3826.txt","sha256":"a5a1c5e8b04d45de83f96bfb00751ff43aac77b13ccdd263f02f89bd16738b19"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a symmetric encryption protocol that\n supplements the protocols described in the User-based Security Model\n (USM), which is a Security Subsystem for version 3 of the Simple\n Network Management Protocol for use in the SNMP Architecture. The\n symmetric encryption protocol described in this document is based on\n the Advanced Encryption Standard (AES) cipher algorithm used in\n Cipher FeedBack Mode (CFB), with a key size of 128 bits.","scope_keywords":["3826","algorithm","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null}],"search_text":"IETF RFC 3826 This document describes a symmetric encryption protocol that\n supplements the protocols described in the User-based Security Model\n (USM), which is a Security Subsystem for version 3 of the Simple\n Network Management Protocol for use in the SNMP Architecture. The\n symmetric encryption protocol described in this document is based on\n the Advanced Encryption Standard (AES) cipher algorithm used in\n Cipher FeedBack Mode (CFB), with a key size of 128 bits. 3826 algorithm authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 3840","type":"specification","body":"IETF","designation":"RFC 3840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3840.txt","https://www.rfc-editor.org/rfc/rfc3840.pdf"],"folder":"IETF/RFC-3840","files":{"txt":{"path":"standards/IETF/RFC-3840/RFC-3840.txt","sha256":"7b2e41f255050e66f65f618fe6853b3f20d8080f347f6050269738c9883d22a5"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines mechanisms by which a Session Initiation\n Protocol (SIP) user agent can convey its capabilities and\n characteristics to other user agents and to the registrar for its\n domain. This information is conveyed as parameters of the Contact\n header field.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 3840 SIP Capabilities August 2004","scope_keywords":["3840","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4483","folder":"IETF/RFC-4483","source":"IETF/RFC-4483/RFC-4483.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5768","folder":"IETF/RFC-5768","source":"IETF/RFC-5768/RFC-5768.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3840 This specification defines mechanisms by which a Session Initiation\n Protocol (SIP) user agent can convey its capabilities and\n characteristics to other user agents and to the registrar for its\n domain. This information is conveyed as parameters of the Contact\n header field.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 3840 SIP Capabilities August 2004 3840 key nested-reference unchanged"},{"id":"IETF RFC 3841","type":"specification","body":"IETF","designation":"RFC 3841","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3841.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3841.txt","https://www.rfc-editor.org/rfc/rfc3841.pdf"],"folder":"IETF/RFC-3841","files":{"txt":{"path":"standards/IETF/RFC-3841/RFC-3841.txt","sha256":"dc188f580de2b587d021f2930b1d57bf8875006dcd369ea19fc2a7db6feb38d5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of extensions to the Session Initiation\n Protocol (SIP) which allow a caller to express preferences about\n request handling in servers. These preferences include the ability\n to select which Uniform Resource Identifiers (URI) a request gets\n routed to, and to specify certain request handling directives in\n proxies and redirect servers. It does so by defining three new\n request header fields, Accept-Contact, Reject-Contact, and Request-\n Disposition, which specify the caller's preferences.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 3841 Caller Preferences for SIP August 2004","scope_keywords":["3841","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null}],"search_text":"IETF RFC 3841 This document describes a set of extensions to the Session Initiation\n Protocol (SIP) which allow a caller to express preferences about\n request handling in servers. These preferences include the ability\n to select which Uniform Resource Identifiers (URI) a request gets\n routed to, and to specify certain request handling directives in\n proxies and redirect servers. It does so by defining three new\n request header fields, Accept-Contact, Reject-Contact, and Request-\n Disposition, which specify the caller's preferences.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 3841 Caller Preferences for SIP August 2004 3841 key policy nested-reference unchanged"},{"id":"IETF RFC 3843","type":"specification","body":"IETF","designation":"RFC 3843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3843.txt","https://www.rfc-editor.org/rfc/rfc3843.pdf"],"folder":"IETF/RFC-3843","files":{"txt":{"path":"standards/IETF/RFC-3843/RFC-3843.txt","sha256":"7081ba28c544c48a50716fd990816c5dad798094a47daf0b961bea6f6f76b41a"}},"tags":["nested-reference","unchanged"],"summary":"The original RObust Header Compression (ROHC) RFC (RFC 3095) defines\n a framework for header compression, along with compression protocols\n (profiles) for IP/UDP/RTP, IP/ESP (Encapsulating Security Payload),\n IP/UDP, and also a profile for uncompressed packet streams. However,\n no profile was defined for compression of IP only, which has been\n identified as a missing piece in RFC 3095. This document defines a\n ROHC compression profile for IP, similar to the IP/UDP profile\n defined by RFC 3095, but simplified to exclude UDP, and enhanced to\n compress IP header chains of arbitrary length.","scope_keywords":["3843","key","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 3843 The original RObust Header Compression (ROHC) RFC (RFC 3095) defines\n a framework for header compression, along with compression protocols\n (profiles) for IP/UDP/RTP, IP/ESP (Encapsulating Security Payload),\n IP/UDP, and also a profile for uncompressed packet streams. However,\n no profile was defined for compression of IP only, which has been\n identified as a missing piece in RFC 3095. This document defines a\n ROHC compression profile for IP, similar to the IP/UDP profile\n defined by RFC 3095, but simplified to exclude UDP, and enhanced to\n compress IP header chains of arbitrary length. 3843 key profile profiles nested-reference unchanged"},{"id":"IETF RFC 3846","type":"specification","body":"IETF","designation":"RFC 3846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3846.txt","https://www.rfc-editor.org/rfc/rfc3846.pdf"],"folder":"IETF/RFC-3846","files":{"txt":{"path":"standards/IETF/RFC-3846/RFC-3846.txt","sha256":"6d8d9814d58a84a8dbf5f523f684054e783217d756e77bd0dabdb92fee438ce5"}},"tags":["nested-reference","unchanged"],"summary":"When a mobile node moves between two foreign networks, it has to be\n re-authenticated. If the home network has both multiple\n Authentication Authorization and Accounting (AAA) servers and Home\n Agents (HAs) in use, the Home AAA server may not have sufficient\n information to process the re-authentication correctly (i.e., to\n ensure that the same HA continues to be used). This document defines\n a Mobile IP extension that carries identities for the Home AAA and HA\n servers in the form of Network Access Identifiers (NAIs). The\n extension allows a Home Agent to pass its identity (and that of the\n Home AAA server) to the mobile node, which can then pass it on to the\n local AAA server when changing its point of attachment. This\n extension may also be used in other situations requiring\n communication of a NAI between Mobile IP nodes.","scope_keywords":["3846","authentication","authorization","key","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4857","folder":"IETF/RFC-4857","source":"IETF/RFC-4857/RFC-4857.txt","version":null}],"search_text":"IETF RFC 3846 When a mobile node moves between two foreign networks, it has to be\n re-authenticated. If the home network has both multiple\n Authentication Authorization and Accounting (AAA) servers and Home\n Agents (HAs) in use, the Home AAA server may not have sufficient\n information to process the re-authentication correctly (i.e., to\n ensure that the same HA continues to be used). This document defines\n a Mobile IP extension that carries identities for the Home AAA and HA\n servers in the form of Network Access Identifiers (NAIs). The\n extension allows a Home Agent to pass its identity (and that of the\n Home AAA server) to the mobile node, which can then pass it on to the\n local AAA server when changing its point of attachment. This\n extension may also be used in other situations requiring\n communication of a NAI between Mobile IP nodes. 3846 authentication authorization key qualified registered nested-reference unchanged"},{"id":"IETF RFC 3850","type":"specification","body":"IETF","designation":"RFC 3850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3850.txt","https://www.rfc-editor.org/rfc/rfc3850.pdf"],"folder":"IETF/RFC-3850","files":{"txt":{"path":"standards/IETF/RFC-3850/RFC-3850.txt","sha256":"5a63704b855a6ad88e7838e453e1edc71f71054f54c295a01f4a1d8bbdab05bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) agents. S/MIME\n provides a method to send and receive secure MIME messages, and\n certificates are an integral part of S/MIME agent processing. S/MIME\n agents validate certificates as described in RFC 3280, the Internet\n X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME\n agents must meet the certificate processing requirements in this\n document as well as those in RFC 3280.","scope_keywords":["3850","algorithm","algorithms","attribute","attributes","certificate","certificates","crl","issuer","key","keys","management","path","pki","profile","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3850 This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) agents. S/MIME\n provides a method to send and receive secure MIME messages, and\n certificates are an integral part of S/MIME agent processing. S/MIME\n agents validate certificates as described in RFC 3280, the Internet\n X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME\n agents must meet the certificate processing requirements in this\n document as well as those in RFC 3280. 3850 algorithm algorithms attribute attributes certificate certificates crl issuer key keys management path pki profile revocation nested-reference unchanged"},{"id":"IETF RFC 3853","type":"specification","body":"IETF","designation":"RFC 3853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3853.txt","https://www.rfc-editor.org/rfc/rfc3853.pdf"],"folder":"IETF/RFC-3853","files":{"txt":{"path":"standards/IETF/RFC-3853/RFC-3853.txt","sha256":"3b8ca95e751f2116cff524a334b9877e0c771852eb8fd081d931ceb2c664535b"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3261 currently specifies 3DES as the mandatory-to-implement\n ciphersuite for implementations of S/MIME in the Session Initiation\n Protocol (SIP). This document updates the normative guidance of RFC\n 3261 to require the Advanced Encryption Standard (AES) for S/MIME.","scope_keywords":["3853","algorithm","algorithms","attribute","encryption","key","keys","profile","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 3853 RFC 3261 currently specifies 3DES as the mandatory-to-implement\n ciphersuite for implementations of S/MIME in the Session Initiation\n Protocol (SIP). This document updates the normative guidance of RFC\n 3261 to require the Advanced Encryption Standard (AES) for S/MIME. 3853 algorithm algorithms attribute encryption key keys profile signature tls nested-reference unchanged"},{"id":"IETF RFC 3854","type":"specification","body":"IETF","designation":"RFC 3854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3854.txt","https://www.rfc-editor.org/rfc/rfc3854.pdf"],"folder":"IETF/RFC-3854","files":{"txt":{"path":"standards/IETF/RFC-3854/RFC-3854.txt","sha256":"290b17e748577565fcf7fb5474cda48e92e9f7dec459c3f17e26ba23bcfa3811"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for adding cryptographic signature\n and encryption services to X.400 content with Secure/Multipurpose\n Internet Mail Extensions (S/MIME).\n\n1. Introduction\n\n The techniques described in the Cryptographic Message Syntax [CMS]\n specification are general enough to support many different content\n types. The [CMS] specification thus provides many options for\n providing different security mechanisms. In order to ensure\n interoperability of systems within the X.400 community, it is\n necessary to specify the use of CMS features to protect X.400 content\n (called \"CMS-X.400\" in this document).","scope_keywords":["3854","algorithm","algorithms","certificate","encryption","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null}],"search_text":"IETF RFC 3854 This document describes a protocol for adding cryptographic signature\n and encryption services to X.400 content with Secure/Multipurpose\n Internet Mail Extensions (S/MIME).\n\n1. Introduction\n\n The techniques described in the Cryptographic Message Syntax [CMS]\n specification are general enough to support many different content\n types. The [CMS] specification thus provides many options for\n providing different security mechanisms. In order to ensure\n interoperability of systems within the X.400 community, it is\n necessary to specify the use of CMS features to protect X.400 content\n (called \"CMS-X.400\" in this document). 3854 algorithm algorithms certificate encryption key signature nested-reference unchanged"},{"id":"IETF RFC 3855","type":"specification","body":"IETF","designation":"RFC 3855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3855.txt","https://www.rfc-editor.org/rfc/rfc3855.pdf"],"folder":"IETF/RFC-3855","files":{"txt":{"path":"standards/IETF/RFC-3855/RFC-3855.txt","sha256":"e6894916065a04b37c44e388a61f9e917ca0ac8c36a21f49a04366a3f88b68c3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol options for conveying objects that\n have been protected using the Cryptographic Message Syntax (CMS) and\n Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1\n over an X.400 message transfer system.\n\n1. Introduction\n\n The techniques described in the Cryptographic Message Syntax [CMS]\n specification and message specifications can reasonably be\n transported via a variety of electronic mail systems. This\n specification defines the options and values necessary to enable\n interoperable transport of S/MIME messages over an X.400 system.\n\n This document describes a mechanism for using CMS objects as the\n message content of X.400 messages in a native X.400 environment.\n This means that gateways or other functions that expect to deal with\n IPMS, such as those specified in [MIXER] and [BODYMAP], cannot do\n anything with these messages. Note that cooper","scope_keywords":["3855","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null}],"search_text":"IETF RFC 3855 This document describes protocol options for conveying objects that\n have been protected using the Cryptographic Message Syntax (CMS) and\n Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.1\n over an X.400 message transfer system.\n\n1. Introduction\n\n The techniques described in the Cryptographic Message Syntax [CMS]\n specification and message specifications can reasonably be\n transported via a variety of electronic mail systems. This\n specification defines the options and values necessary to enable\n interoperable transport of S/MIME messages over an X.400 system.\n\n This document describes a mechanism for using CMS objects as the\n message content of X.400 messages in a native X.400 environment.\n This means that gateways or other functions that expect to deal with\n IPMS, such as those specified in [MIXER] and [BODYMAP], cannot do\n anything with these messages. Note that cooper 3855 delivery key nested-reference unchanged"},{"id":"IETF RFC 3856","type":"specification","body":"IETF","designation":"RFC 3856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3856.txt","https://www.rfc-editor.org/rfc/rfc3856.pdf"],"folder":"IETF/RFC-3856","files":{"txt":{"path":"standards/IETF/RFC-3856/RFC-3856.txt","sha256":"4d33a916eb533976d170700ae2c52acaf66a65cc98fd7f4e1e62477fc05a5895"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of the Session Initiation Protocol\n (SIP) for subscriptions and notifications of presence. Presence is\n defined as the willingness and ability of a user to communicate with\n other users on the network. Historically, presence has been limited\n to \"on-line\" and \"off-line\" indicators; the notion of presence here\n is broader. Subscriptions and notifications of presence are\n supported by defining an event package within the general SIP event\n notification framework. This protocol is also compliant with the\n Common Presence Profile (CPP) framework.","scope_keywords":["3856","authentication","authorization","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3857","folder":"IETF/RFC-3857","source":"IETF/RFC-3857/RFC-3857.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3856 This document describes the usage of the Session Initiation Protocol\n (SIP) for subscriptions and notifications of presence. Presence is\n defined as the willingness and ability of a user to communicate with\n other users on the network. Historically, presence has been limited\n to \"on-line\" and \"off-line\" indicators; the notion of presence here\n is broader. Subscriptions and notifications of presence are\n supported by defining an event package within the general SIP event\n notification framework. This protocol is also compliant with the\n Common Presence Profile (CPP) framework. 3856 authentication authorization key profile nested-reference unchanged"},{"id":"IETF RFC 3857","type":"specification","body":"IETF","designation":"RFC 3857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3857.txt","https://www.rfc-editor.org/rfc/rfc3857.pdf"],"folder":"IETF/RFC-3857","files":{"txt":{"path":"standards/IETF/RFC-3857/RFC-3857.txt","sha256":"9edce6fe63cacdca291bb6b8b113da1531cc52856a5aae666d0a7562353a01e4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the watcher information template-package for\n the Session Initiation Protocol (SIP) event framework. Watcher\n information refers to the set of users subscribed to a particular\n resource within a particular event package. Watcher information\n changes dynamically as users subscribe, unsubscribe, are approved, or\n are rejected. A user can subscribe to this information, and\n therefore learn about changes to it. This event package is a\n template-package because it can be applied to any event package,\n including itself.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 3857 Watcher Information August 2004","scope_keywords":["3857","authorization","key","policy","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null}],"search_text":"IETF RFC 3857 This document defines the watcher information template-package for\n the Session Initiation Protocol (SIP) event framework. Watcher\n information refers to the set of users subscribed to a particular\n resource within a particular event package. Watcher information\n changes dynamically as users subscribe, unsubscribe, are approved, or\n are rejected. A user can subscribe to this information, and\n therefore learn about changes to it. This event package is a\n template-package because it can be applied to any event package,\n including itself.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 3857 Watcher Information August 2004 3857 authorization key policy qualified nested-reference unchanged"},{"id":"IETF RFC 3858","type":"specification","body":"IETF","designation":"RFC 3858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3858.txt","https://www.rfc-editor.org/rfc/rfc3858.pdf"],"folder":"IETF/RFC-3858","files":{"txt":{"path":"standards/IETF/RFC-3858/RFC-3858.txt","sha256":"713e2dfe8d070bd3da67d336b49b1cabe163e37c6aa5d65555d0a78d0f29172e"}},"tags":["nested-reference","unchanged"],"summary":"Watchers are defined as entities that request (i.e., subscribe to)\n information about a resource. There is fairly complex state\n associated with these subscriptions. The union of the state for all\n subscriptions to a particular resource is called the watcher\n information for that resource. This state is dynamic, changing as\n subscribers come and go. As a result, it is possible, and indeed\n useful, to subscribe to the watcher information for a particular\n resource. In order to enable this, a format is needed to describe\n the state of watchers on a resource. This specification describes an\n Extensible Markup Language (XML) document format for such state.","scope_keywords":["3858","attribute","attributes","authorization","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3857","folder":"IETF/RFC-3857","source":"IETF/RFC-3857/RFC-3857.txt","version":null},{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null}],"search_text":"IETF RFC 3858 Watchers are defined as entities that request (i.e., subscribe to)\n information about a resource. There is fairly complex state\n associated with these subscriptions. The union of the state for all\n subscriptions to a particular resource is called the watcher\n information for that resource. This state is dynamic, changing as\n subscribers come and go. As a result, it is possible, and indeed\n useful, to subscribe to the watcher information for a particular\n resource. In order to enable this, a format is needed to describe\n the state of watchers on a resource. This specification describes an\n Extensible Markup Language (XML) document format for such state. 3858 attribute attributes authorization key nested-reference unchanged"},{"id":"IETF RFC 3859","type":"specification","body":"IETF","designation":"RFC 3859","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3859.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3859.txt","https://www.rfc-editor.org/rfc/rfc3859.pdf"],"folder":"IETF/RFC-3859","files":{"txt":{"path":"standards/IETF/RFC-3859/RFC-3859.txt","sha256":"57665e808c2c6ddfc59afeb822b072704b8ae0a6070413867270ec423736d9ff"}},"tags":["nested-reference","unchanged"],"summary":"At the time this document was written, numerous presence protocols\n were in use (largely as components of commercial instant messaging\n services), and little interoperability between services based on\n these protocols has been achieved. This specification defines common\n semantics and data formats for presence to facilitate the creation of\n gateways between presence services.","scope_keywords":["3859","attribute","attributes","identification","key","presentation","preservation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null}],"search_text":"IETF RFC 3859 At the time this document was written, numerous presence protocols\n were in use (largely as components of commercial instant messaging\n services), and little interoperability between services based on\n these protocols has been achieved. This specification defines common\n semantics and data formats for presence to facilitate the creation of\n gateways between presence services. 3859 attribute attributes identification key presentation preservation profile nested-reference unchanged"},{"id":"IETF RFC 3860","type":"specification","body":"IETF","designation":"RFC 3860","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3860.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3860.txt","https://www.rfc-editor.org/rfc/rfc3860.pdf"],"folder":"IETF/RFC-3860","files":{"txt":{"path":"standards/IETF/RFC-3860/RFC-3860.txt","sha256":"9362e2a020aa522cda09d6957d462fe50352475ae8e626677256ee46eefabffa"}},"tags":["nested-reference","unchanged"],"summary":"At the time this document was written, numerous instant messaging\n protocols were in use, and little interoperability between services\n based on these protocols has been achieved. This specification\n defines common semantics and data formats for instant messaging to\n facilitate the creation of gateways between instant messaging\n services.","scope_keywords":["3860","attribute","attributes","identification","key","presentation","preservation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5509","folder":"IETF/RFC-5509","source":"IETF/RFC-5509/RFC-5509.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 3860 At the time this document was written, numerous instant messaging\n protocols were in use, and little interoperability between services\n based on these protocols has been achieved. This specification\n defines common semantics and data formats for instant messaging to\n facilitate the creation of gateways between instant messaging\n services. 3860 attribute attributes identification key presentation preservation profile nested-reference unchanged"},{"id":"IETF RFC 3865","type":"specification","body":"IETF","designation":"RFC 3865","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3865.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3865.txt","https://www.rfc-editor.org/rfc/rfc3865.pdf"],"folder":"IETF/RFC-3865","files":{"txt":{"path":"standards/IETF/RFC-3865/RFC-3865.txt","sha256":"871239ad8fa7da9a02612840f35b168a036dd96a91b953bd8a0715a86f6a773f"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an extension to Soliciting Simple Mail\n Transfer Protocol (SMTP) for an electronic mail equivalent to the\n real-world \"No Soliciting\" sign. In addition to the service\n extension, a new message header and extensions to the existing\n \"received\" message header are described.\n\nMalamud Standards Track [Page 1]\n\f\nRFC 3865 No Soliciting September 2004","scope_keywords":["3865","holder","identification","key","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 6409","folder":"IETF/RFC-6409","source":"IETF/RFC-6409/RFC-6409.txt","version":null}],"search_text":"IETF RFC 3865 This document proposes an extension to Soliciting Simple Mail\n Transfer Protocol (SMTP) for an electronic mail equivalent to the\n real-world \"No Soliciting\" sign. In addition to the service\n extension, a new message header and extensions to the existing\n \"received\" message header are described.\n\nMalamud Standards Track [Page 1]\n\f\nRFC 3865 No Soliciting September 2004 3865 holder identification key pid subject nested-reference unchanged"},{"id":"IETF RFC 3866","type":"specification","body":"IETF","designation":"RFC 3866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3866.txt","https://www.rfc-editor.org/rfc/rfc3866.pdf"],"folder":"IETF/RFC-3866","files":{"txt":{"path":"standards/IETF/RFC-3866/RFC-3866.txt","sha256":"ef206ae81ffc9c18d61b6ab015f74bf4c705107355a177da44bc644a2e4fb42e"}},"tags":["nested-reference","unchanged"],"summary":"It is often desirable to be able to indicate the natural language\n associated with values held in a directory and to be able to query\n the directory for values which fulfill the user's language needs.\n This document details the use of Language Tags and Ranges in the\n Lightweight Directory Access Protocol (LDAP).\n\n1. Background and Intended Use\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides a\n means for clients to interrogate and modify information stored in a\n distributed directory system. The information in the directory is\n maintained as attributes of entries. Most of these attributes have\n syntaxes which are human-readable strings, and it is desirable to be\n able to indicate the natural language associated with attribute\n values.\n\n This document describes how language tags and ranges [RFC3066] are\n carried in LDAP and are to be interpreted by LDAP implementation","scope_keywords":["3866","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"IETF RFC 3866 It is often desirable to be able to indicate the natural language\n associated with values held in a directory and to be able to query\n the directory for values which fulfill the user's language needs.\n This document details the use of Language Tags and Ranges in the\n Lightweight Directory Access Protocol (LDAP).\n\n1. Background and Intended Use\n\n The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides a\n means for clients to interrogate and modify information stored in a\n distributed directory system. The information in the directory is\n maintained as attributes of entries. Most of these attributes have\n syntaxes which are human-readable strings, and it is desirable to be\n able to indicate the natural language associated with attribute\n values.\n\n This document describes how language tags and ranges [RFC3066] are\n carried in LDAP and are to be interpreted by LDAP implementation 3866 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 3874","type":"specification","body":"IETF","designation":"RFC 3874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3874.txt","https://www.rfc-editor.org/rfc/rfc3874.pdf"],"folder":"IETF/RFC-3874","files":{"txt":{"path":"standards/IETF/RFC-3874/RFC-3874.txt","sha256":"7bc4b14ebd74d28eb4b862b7b6b8329cc773f87d75aa0100c5240edeb2f2f84e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a 224-bit one-way hash function, called\n SHA-224. SHA-224 is based on SHA-256, but it uses a different\n initial value and the result is truncated to 224 bits.\n\n1. Introduction\n\n This document specifies a 224-bit one-way hash function, called\n SHA-224. The National Institute of Standards and Technology (NIST)\n announced the FIPS 180-2 Change Notice on February 28, 2004 which\n specifies the SHA-224 one-way hash function. One-way hash functions\n are also known as message digests. SHA-224 is based on SHA-256, the\n 256-bit one-way hash function already specified by NIST [SHA2].\n Computation of a SHA-224 hash value is two steps. First, the SHA-256\n hash value is computed, except that a different initial value is\n used. Second, the resulting 256-bit hash value is truncated to 224\n bits.\n\n NIST is developing guidance on cryptographic key management, and NIST\n recently pub","scope_keywords":["3874","algorithm","algorithms","authentication","hash","key","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4055","folder":"IETF/RFC-4055","source":"IETF/RFC-4055/RFC-4055.txt","version":null},{"body":"IETF","designation":"RFC 4634","folder":"IETF/RFC-4634","source":"IETF/RFC-4634/RFC-4634.txt","version":null},{"body":"IETF","designation":"RFC 4635","folder":"IETF/RFC-4635","source":"IETF/RFC-4635/RFC-4635.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null}],"search_text":"IETF RFC 3874 This document specifies a 224-bit one-way hash function, called\n SHA-224. SHA-224 is based on SHA-256, but it uses a different\n initial value and the result is truncated to 224 bits.\n\n1. Introduction\n\n This document specifies a 224-bit one-way hash function, called\n SHA-224. The National Institute of Standards and Technology (NIST)\n announced the FIPS 180-2 Change Notice on February 28, 2004 which\n specifies the SHA-224 one-way hash function. One-way hash functions\n are also known as message digests. SHA-224 is based on SHA-256, the\n 256-bit one-way hash function already specified by NIST [SHA2].\n Computation of a SHA-224 hash value is two steps. First, the SHA-256\n hash value is computed, except that a different initial value is\n used. Second, the resulting 256-bit hash value is truncated to 224\n bits.\n\n NIST is developing guidance on cryptographic key management, and NIST\n recently pub 3874 algorithm algorithms authentication hash key management signature nested-reference unchanged"},{"id":"IETF RFC 3878","type":"specification","body":"IETF","designation":"RFC 3878","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3878.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3878.txt","https://www.rfc-editor.org/rfc/rfc3878.pdf"],"folder":"IETF/RFC-3878","files":{"txt":{"path":"standards/IETF/RFC-3878/RFC-3878.txt","sha256":"a13635bc80790a21f4ff2c0c430eea7120b85358a72a65f9472b9591d3199525"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for controlling the reporting of\n alarm conditions.","scope_keywords":["3878","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3878 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for controlling the reporting of\n alarm conditions. 3878 key management nested-reference unchanged"},{"id":"IETF RFC 3880","type":"specification","body":"IETF","designation":"RFC 3880","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3880.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3880.txt","https://www.rfc-editor.org/rfc/rfc3880.pdf"],"folder":"IETF/RFC-3880","files":{"txt":{"path":"standards/IETF/RFC-3880/RFC-3880.txt","sha256":"c2f30cee0df0326f8e05bc5795510189a05f22c77bcc473d24d9e55c22363965"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Call Processing Language (CPL), a language\n to describe and control Internet telephony services. It is designed\n to be implementable on either network servers or user agents. It is\n meant to be simple, extensible, easily edited by graphical clients,\n and independent of operating system or signalling protocol. It is\n suitable for running on a server where users may not be allowed to\n execute arbitrary programs, as it has no variables, loops, or ability\n to run external programs.\n\nLennox, et al. Standards Track [Page 1]\n\f\nRFC 3880 CPL October 2004","scope_keywords":["3880","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4740","folder":"IETF/RFC-4740","source":"IETF/RFC-4740/RFC-4740.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null}],"search_text":"IETF RFC 3880 This document defines the Call Processing Language (CPL), a language\n to describe and control Internet telephony services. It is designed\n to be implementable on either network servers or user agents. It is\n meant to be simple, extensible, easily edited by graphical clients,\n and independent of operating system or signalling protocol. It is\n suitable for running on a server where users may not be allowed to\n execute arbitrary programs, as it has no variables, loops, or ability\n to run external programs.\n\nLennox, et al. Standards Track [Page 1]\n\f\nRFC 3880 CPL October 2004 3880 algorithm nested-reference unchanged"},{"id":"IETF RFC 3888","type":"specification","body":"IETF","designation":"RFC 3888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3888.txt","https://www.rfc-editor.org/rfc/rfc3888.pdf"],"folder":"IETF/RFC-3888","files":{"txt":{"path":"standards/IETF/RFC-3888/RFC-3888.txt","sha256":"b46587fa285a8bf94bc989ab8b8e268db7b337eec65e71068b34ac413f7bb511"}},"tags":["nested-reference","unchanged"],"summary":"Customers buying enterprise message systems often ask: Can I track\n the messages? Message tracking is the ability to find out the path\n that a particular message has taken through a messaging system and\n the current routing status of that message. This document provides a\n model of message tracking that can be used for understanding the\n Internet-wide message infrastructure and to further enhance those\n capabilities to include message tracking, as well as requirements for\n proposed message tracking solutions.\n\n1. Problem Statement\n\n Consider sending a package through a package delivery company. Once\n you've sent a package, you would like to be able to find out if the\n package has been delivered or not, and if not, where that package\n currently is and what its status is. Note that the status of a\n package may not include whether it was delivered to its addressee,\n but just the destination","scope_keywords":["3888","authentication","delivery","identification","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null}],"search_text":"IETF RFC 3888 Customers buying enterprise message systems often ask: Can I track\n the messages? Message tracking is the ability to find out the path\n that a particular message has taken through a messaging system and\n the current routing status of that message. This document provides a\n model of message tracking that can be used for understanding the\n Internet-wide message infrastructure and to further enhance those\n capabilities to include message tracking, as well as requirements for\n proposed message tracking solutions.\n\n1. Problem Statement\n\n Consider sending a package through a package delivery company. Once\n you've sent a package, you would like to be able to find out if the\n package has been delivered or not, and if not, where that package\n currently is and what its status is. Note that the status of a\n package may not include whether it was delivered to its addressee,\n but just the destination 3888 authentication delivery identification key path policy nested-reference unchanged"},{"id":"IETF RFC 3890","type":"specification","body":"IETF","designation":"RFC 3890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3890.txt","https://www.rfc-editor.org/rfc/rfc3890.pdf"],"folder":"IETF/RFC-3890","files":{"txt":{"path":"standards/IETF/RFC-3890/RFC-3890.txt","sha256":"24a8f5c29920faa5092849edb19a0506917129342a7863402acb791dd0c08035"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Session Description Protocol (SDP) Transport\n Independent Application Specific Maximum (TIAS) bandwidth modifier\n that does not include transport overhead; instead an additional\n packet rate attribute is defined. The transport independent bit-rate\n value together with the maximum packet rate can then be used to\n calculate the real bit-rate over the transport actually used.\n\n The existing SDP bandwidth modifiers and their values include the\n bandwidth needed for the transport and IP layers. When using SDP\n with protocols like the Session Announcement Protocol (SAP), the\n Session Initiation Protocol (SIP), and the Real-Time Streaming\n Protocol (RTSP), and when the involved hosts has different transport\n overhead, for example due to different IP versions, the\n interpretation of what lower layer bandwidths are included is not\n clear.\n\nWesterlund Standards Track [Page ","scope_keywords":["3890","attribute","presentation","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3890 This document defines a Session Description Protocol (SDP) Transport\n Independent Application Specific Maximum (TIAS) bandwidth modifier\n that does not include transport overhead; instead an additional\n packet rate attribute is defined. The transport independent bit-rate\n value together with the maximum packet rate can then be used to\n calculate the real bit-rate over the transport actually used.\n\n The existing SDP bandwidth modifiers and their values include the\n bandwidth needed for the transport and IP layers. When using SDP\n with protocols like the Session Announcement Protocol (SAP), the\n Session Initiation Protocol (SIP), and the Real-Time Streaming\n Protocol (RTSP), and when the involved hosts has different transport\n overhead, for example due to different IP versions, the\n interpretation of what lower layer bandwidths are included is not\n clear.\n\nWesterlund Standards Track [Page  3890 attribute presentation tsp nested-reference unchanged"},{"id":"IETF RFC 3891","type":"specification","body":"IETF","designation":"RFC 3891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3891.txt","https://www.rfc-editor.org/rfc/rfc3891.pdf"],"folder":"IETF/RFC-3891","files":{"txt":{"path":"standards/IETF/RFC-3891/RFC-3891.txt","sha256":"454237566b031998e7ddb91e69d78ae434c05508eefa98530d2b5a52f218530b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new header for use with Session Initiation\n Protocol (SIP) multi-party applications and call control. The\n Replaces header is used to logically replace an existing SIP dialog\n with a new SIP dialog. This primitive can be used to enable a\n variety of features, for example: \"Attended Transfer\" and \"Call\n Pickup\". Note that the definition of these example features is non-\n normative.\n\nMahy, et al. Standards Track [Page 1]\n\f\nRFC 3891 The SIP \"Replaces\" Header September 2004","scope_keywords":["3891","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 3891 This document defines a new header for use with Session Initiation\n Protocol (SIP) multi-party applications and call control. The\n Replaces header is used to logically replace an existing SIP dialog\n with a new SIP dialog. This primitive can be used to enable a\n variety of features, for example: \"Attended Transfer\" and \"Call\n Pickup\". Note that the definition of these example features is non-\n normative.\n\nMahy, et al. Standards Track [Page 1]\n\f\nRFC 3891 The SIP \"Replaces\" Header September 2004 3891 key nested-reference unchanged"},{"id":"IETF RFC 3893","type":"specification","body":"IETF","designation":"RFC 3893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3893.txt","https://www.rfc-editor.org/rfc/rfc3893.pdf"],"folder":"IETF/RFC-3893","files":{"txt":{"path":"standards/IETF/RFC-3893/RFC-3893.txt","sha256":"25f715bbbff4ddc13ac8245280e35bdd9e2779320d53252b6887e7c852a54620"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3261 introduces the concept of adding an S/MIME body to a Session\n Initiation Protocol (SIP) request or response in order to provide\n reference integrity over its headers. This document provides a more\n specific mechanism to derive integrity and authentication properties\n from an 'authenticated identity body', a digitally-signed SIP\n message, or message fragment. A standard format for such bodies\n (known as Authenticated Identity Bodies, or AIBs) is given in this\n document. Some considerations for the processing of AIBs by\n recipients of SIP messages with such bodies are also given.\n\nPeterson Standards Track [Page 1]\n\f\nRFC 3893 SIP Authenticated Identity Body (AIB) FormatSeptember 2004","scope_keywords":["3893","authentication","encryption","identification","key","signature","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 3893 RFC 3261 introduces the concept of adding an S/MIME body to a Session\n Initiation Protocol (SIP) request or response in order to provide\n reference integrity over its headers. This document provides a more\n specific mechanism to derive integrity and authentication properties\n from an 'authenticated identity body', a digitally-signed SIP\n message, or message fragment. A standard format for such bodies\n (known as Authenticated Identity Bodies, or AIBs) is given in this\n document. Some considerations for the processing of AIBs by\n recipients of SIP messages with such bodies are also given.\n\nPeterson Standards Track [Page 1]\n\f\nRFC 3893 SIP Authenticated Identity Body (AIB) FormatSeptember 2004 3893 authentication encryption identification key signature verifiable nested-reference unchanged"},{"id":"IETF RFC 3894","type":"specification","body":"IETF","designation":"RFC 3894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3894.txt","https://www.rfc-editor.org/rfc/rfc3894.pdf"],"folder":"IETF/RFC-3894","files":{"txt":{"path":"standards/IETF/RFC-3894/RFC-3894.txt","sha256":"b68d9d6518a46230b5f35a9a4b6feb92b48ac1addb424a0477a141f8280e7bf8"}},"tags":["nested-reference","unchanged"],"summary":"The Sieve scripting language allows users to control handling and\n disposal of their incoming e-mail. By default, an e-mail message\n that is processed by a Sieve script is saved in the owner's \"inbox\".\n Actions such as \"fileinto\" and \"redirect\" cancel this default\n behavior.\n\n This document defines a new keyword parameter, \":copy\", to be used\n with the Sieve \"fileinto\" and \"redirect\" actions. Adding \":copy\" to\n an action suppresses cancellation of the default \"inbox\" save. It\n allows users to add commands to an existing script without changing\n the meaning of the rest of the script.\n\n1. Introduction\n\n The Sieve scripting language [SIEVE] allows users to control handling\n and disposal of their incoming e-mail. Two frequently used Sieve\n commands are \"fileinto\" (saving into a local message store, such as\n an IMAP server) and \"redirect\" (forwarding to another e-mail\n address). Both of these","scope_keywords":["3894","authentication","delivery","http","key","license","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 3894 The Sieve scripting language allows users to control handling and\n disposal of their incoming e-mail. By default, an e-mail message\n that is processed by a Sieve script is saved in the owner's \"inbox\".\n Actions such as \"fileinto\" and \"redirect\" cancel this default\n behavior.\n\n This document defines a new keyword parameter, \":copy\", to be used\n with the Sieve \"fileinto\" and \"redirect\" actions. Adding \":copy\" to\n an action suppresses cancellation of the default \"inbox\" save. It\n allows users to add commands to an existing script without changing\n the meaning of the rest of the script.\n\n1. Introduction\n\n The Sieve scripting language [SIEVE] allows users to control handling\n and disposal of their incoming e-mail. Two frequently used Sieve\n commands are \"fileinto\" (saving into a local message store, such as\n an IMAP server) and \"redirect\" (forwarding to another e-mail\n address). Both of these 3894 authentication delivery http key license subject tls nested-reference unchanged"},{"id":"IETF RFC 3898","type":"specification","body":"IETF","designation":"RFC 3898","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3898.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3898.txt","https://www.rfc-editor.org/rfc/rfc3898.pdf"],"folder":"IETF/RFC-3898","files":{"txt":{"path":"standards/IETF/RFC-3898/RFC-3898.txt","sha256":"b89517e6c3a4985a9c96e275cd6aa666e34ce3b2e7f5b91739e0dcae2ccc2f80"}},"tags":["nested-reference","unchanged"],"summary":"This document describes four options for Network Information Service\n (NIS) related configuration information in Dynamic Host Configuration\n Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client\n Domain Name, NIS+ Client Domain name.\n\n1. Introduction\n\n This document describes four options for passing configuration\n information related to Network Information Service (NIS) [3] in\n DHCPv6 (RFC 3315 [1]).\n\n The options defined in this document can only be used to configure\n information about NIS servers that can be reached using IPv6. The\n DHCP option to configure information about IPv4 NIS servers can be\n found in RFC 2132 [4]. Mechanisms for configuring IPv4/IPv6 dual-\n stack applications are being considered, but are not specified in\n this document.\n\n2. Terminology\n\n The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL i","scope_keywords":["3898","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 3898 This document describes four options for Network Information Service\n (NIS) related configuration information in Dynamic Host Configuration\n Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client\n Domain Name, NIS+ Client Domain name.\n\n1. Introduction\n\n This document describes four options for passing configuration\n information related to Network Information Service (NIS) [3] in\n DHCPv6 (RFC 3315 [1]).\n\n The options defined in this document can only be used to configure\n information about NIS servers that can be reached using IPv6. The\n DHCP option to configure information about IPv4 NIS servers can be\n found in RFC 2132 [4]. Mechanisms for configuring IPv4/IPv6 dual-\n stack applications are being considered, but are not specified in\n this document.\n\n2. Terminology\n\n The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL i 3898 key presentation nested-reference unchanged"},{"id":"IETF RFC 3902","type":"specification","body":"IETF","designation":"RFC 3902","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3902.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3902.txt","https://www.rfc-editor.org/rfc/rfc3902.pdf"],"folder":"IETF/RFC-3902","files":{"txt":{"path":"standards/IETF/RFC-3902/RFC-3902.txt","sha256":"b3f909031d0f091f968eaeb4a57db95057425167ede80eb1f558092c1ebfc1a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Baker\nRequest for Comments: 3902 Independent\nCategory: Informational M. Nottingham\n BEA Systems\n September 2004\n\n The \"application/soap+xml\" media type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004).\n\nAbstract\n\n This document defines the \"application/soap+xml\" media type which can\n be used to describe SOAP 1.2 messages serialized as XML 1.0.\n\n1. Introduction\n\n SOAP version 1.2 (SOAP) is a lightweight protocol intended for\n exchange of structured information between peers in a decentralized,\n distributed environment. It defines an extensible messaging\n framework that contains a message construct based on XML technologies\n that can be exchanged over a variety of underlying pr","scope_keywords":["3902","authentication","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4227","folder":"IETF/RFC-4227","source":"IETF/RFC-4227/RFC-4227.txt","version":null}],"search_text":"IETF RFC 3902 Network Working Group M. Baker\nRequest for Comments: 3902 Independent\nCategory: Informational M. Nottingham\n BEA Systems\n September 2004\n\n The \"application/soap+xml\" media type\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2004).\n\nAbstract\n\n This document defines the \"application/soap+xml\" media type which can\n be used to describe SOAP 1.2 messages serialized as XML 1.0.\n\n1. Introduction\n\n SOAP version 1.2 (SOAP) is a lightweight protocol intended for\n exchange of structured information between peers in a decentralized,\n distributed environment. It defines an extensible messaging\n framework that contains a message construct based on XML technologies\n that can be exchanged over a variety of underlying pr 3902 authentication http key nested-reference unchanged"},{"id":"IETF RFC 3903","type":"specification","body":"IETF","designation":"RFC 3903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3903.txt","https://www.rfc-editor.org/rfc/rfc3903.pdf"],"folder":"IETF/RFC-3903","files":{"txt":{"path":"standards/IETF/RFC-3903/RFC-3903.txt","sha256":"39b3cb7db4ebb325ed17e33b22b8c79a2d31627b383e0b074784f4050e695e15"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the Session Initiation\n Protocol (SIP) for publishing event state used within the SIP Events\n framework. The first application of this extension is for the\n publication of presence information.\n\n The mechanism described in this document can be extended to support\n publication of any event state for which there exists an appropriate\n event package. It is not intended to be a general-purpose mechanism\n for transport of arbitrary data, as there are better-suited\n mechanisms for this purpose.","scope_keywords":["3903","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3903 This document describes an extension to the Session Initiation\n Protocol (SIP) for publishing event state used within the SIP Events\n framework. The first application of this extension is for the\n publication of presence information.\n\n The mechanism described in this document can be extended to support\n publication of any event state for which there exists an appropriate\n event package. It is not intended to be a general-purpose mechanism\n for transport of arbitrary data, as there are better-suited\n mechanisms for this purpose. 3903 identification nested-reference unchanged"},{"id":"IETF RFC 3911","type":"specification","body":"IETF","designation":"RFC 3911","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3911.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3911.txt","https://www.rfc-editor.org/rfc/rfc3911.pdf"],"folder":"IETF/RFC-3911","files":{"txt":{"path":"standards/IETF/RFC-3911/RFC-3911.txt","sha256":"f828634dbe3dbdcc95bb768fe29c3de8b6999da2e30afdd155fcb8101046db9a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new header for use with SIP multi-party\n applications and call control. The Join header is used to logically\n join an existing SIP dialog with a new SIP dialog. This primitive\n can be used to enable a variety of features, for example: \"Barge-In\",\n answering-machine-style \"Message Screening\" and \"Call Center\n Monitoring\". Note that definition of these example features is non-\n normative.","scope_keywords":["3911","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 3911 This document defines a new header for use with SIP multi-party\n applications and call control. The Join header is used to logically\n join an existing SIP dialog with a new SIP dialog. This primitive\n can be used to enable a variety of features, for example: \"Barge-In\",\n answering-machine-style \"Message Screening\" and \"Call Center\n Monitoring\". Note that definition of these example features is non-\n normative. 3911 delivery key nested-reference unchanged"},{"id":"IETF RFC 3925","type":"specification","body":"IETF","designation":"RFC 3925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3925.txt","https://www.rfc-editor.org/rfc/rfc3925.pdf"],"folder":"IETF/RFC-3925","files":{"txt":{"path":"standards/IETF/RFC-3925/RFC-3925.txt","sha256":"bae9d07c4553f636f2fdf3e95a6f136581079a2e3112aab65bd04e7da389d77d"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) options for Vendor\n Class and Vendor-Specific Information can be limiting or ambiguous\n when a DHCP client represents multiple vendors. This document\n defines two new options, modeled on the IPv6 options for vendor class\n and vendor-specific information, that contain Enterprise Numbers to\n remove ambiguity.","scope_keywords":["3925","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4243","folder":"IETF/RFC-4243","source":"IETF/RFC-4243/RFC-4243.txt","version":null},{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null}],"search_text":"IETF RFC 3925 The Dynamic Host Configuration Protocol (DHCP) options for Vendor\n Class and Vendor-Specific Information can be limiting or ambiguous\n when a DHCP client represents multiple vendors. This document\n defines two new options, modeled on the IPv6 options for vendor class\n and vendor-specific information, that contain Enterprise Numbers to\n remove ambiguity. 3925 key registered nested-reference unchanged"},{"id":"IETF RFC 3936","type":"specification","body":"IETF","designation":"RFC 3936","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3936.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3936.txt","https://www.rfc-editor.org/rfc/rfc3936.pdf"],"folder":"IETF/RFC-3936","files":{"txt":{"path":"standards/IETF/RFC-3936/RFC-3936.txt","sha256":"a07aef896474f3ca45bb90d46dae2edb80913df801a7c1108067a820d7c5c23c"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies procedures for modifying the Resource reSerVation\n Protocol (RSVP). This memo also lays out new assignment guidelines\n for number spaces for RSVP messages, object classes, class-types, and\n sub-objects.\n\n1. Introduction\n\n This memo specifies procedures for modifying the Resource reSerVation\n Protocol (RSVP) [RSVP], including (but not limited to) adding,\n updating, extending or obsoleting: messages, message formats and\n procedures, object classes and class types, object formats and\n procedures; header formats, error codes and subcodes and semantics,\n and procedures for sending, receiving, and addressing RSVP messages.\n\n IANA recognizes the following RSVP name spaces: Message Types, Class\n Names, Class Numbers, Class Types and Sub-objects, Virtual\n Destination Ports, and Error Codes and (Subcode) Values (all of these\n will collectively be referred to as RSVP entities in","scope_keywords":["3936","key","management","policies","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null}],"search_text":"IETF RFC 3936 This memo specifies procedures for modifying the Resource reSerVation\n Protocol (RSVP). This memo also lays out new assignment guidelines\n for number spaces for RSVP messages, object classes, class-types, and\n sub-objects.\n\n1. Introduction\n\n This memo specifies procedures for modifying the Resource reSerVation\n Protocol (RSVP) [RSVP], including (but not limited to) adding,\n updating, extending or obsoleting: messages, message formats and\n procedures, object classes and class types, object formats and\n procedures; header formats, error codes and subcodes and semantics,\n and procedures for sending, receiving, and addressing RSVP messages.\n\n IANA recognizes the following RSVP name spaces: Message Types, Class\n Names, Class Numbers, Class Types and Sub-objects, Virtual\n Destination Ports, and Error Codes and (Subcode) Values (all of these\n will collectively be referred to as RSVP entities in 3936 key management policies registered nested-reference unchanged"},{"id":"IETF RFC 3942","type":"specification","body":"IETF","designation":"RFC 3942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3942.txt","https://www.rfc-editor.org/rfc/rfc3942.pdf"],"folder":"IETF/RFC-3942","files":{"txt":{"path":"standards/IETF/RFC-3942/RFC-3942.txt","sha256":"641cefc6fd6382923525951779e08ac21cb6e545a9bd96d9643c5517306b391a"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 2132 to reclassify Dynamic Host\n Configuration Protocol version 4 (DHCPv4) option codes 128 to 223\n (decimal) as publicly defined options to be managed by IANA in\n accordance with RFC 2939. This document directs IANA to make these\n option codes available for assignment as publicly defined DHCP\n options for future options.","scope_keywords":["3942","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 3942 This document updates RFC 2132 to reclassify Dynamic Host\n Configuration Protocol version 4 (DHCPv4) option codes 128 to 223\n (decimal) as publicly defined options to be managed by IANA in\n accordance with RFC 2939. This document directs IANA to make these\n option codes available for assignment as publicly defined DHCP\n options for future options. 3942 key nested-reference unchanged"},{"id":"IETF RFC 3946","type":"specification","body":"IETF","designation":"RFC 3946","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3946.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3946.txt","https://www.rfc-editor.org/rfc/rfc3946.pdf"],"folder":"IETF/RFC-3946","files":{"txt":{"path":"standards/IETF/RFC-3946/RFC-3946.txt","sha256":"f1f30442a47a8b0cb3512785acf3d3d758086bc77df803a7a9fde17360285036"}},"tags":["nested-reference","unchanged"],"summary":"This document is a companion to the Generalized Multi-Protocol Label\n Switching (GMPLS) signaling. It defines the Synchronous Optical\n Network (SONET)/Synchronous Digital Hierarchy (SDH) technology\n specific information needed when using GMPLS signaling.","scope_keywords":["3946","key","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4139","folder":"IETF/RFC-4139","source":"IETF/RFC-4139/RFC-4139.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null}],"search_text":"IETF RFC 3946 This document is a companion to the Generalized Multi-Protocol Label\n Switching (GMPLS) signaling. It defines the Synchronous Optical\n Network (SONET)/Synchronous Digital Hierarchy (SDH) technology\n specific information needed when using GMPLS signaling. 3946 key path profile nested-reference unchanged"},{"id":"IETF RFC 3947","type":"specification","body":"IETF","designation":"RFC 3947","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3947.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3947.txt","https://www.rfc-editor.org/rfc/rfc3947.pdf"],"folder":"IETF/RFC-3947","files":{"txt":{"path":"standards/IETF/RFC-3947/RFC-3947.txt","sha256":"d86ca809b62f093dca8a449e598360987c6af28db06d324e4593049f28c41277"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to detect one or more network address\n translation devices (NATs) between IPsec hosts, and how to negotiate\n the use of UDP encapsulation of IPsec packets through NAT boxes in\n Internet Key Exchange (IKE).\n\nKivinen, et al. Standards Track [Page 1]\n\f\nRFC 3947 Negotiation of NAT-Traversal in the IKE January 2005","scope_keywords":["3947","hash","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 4093","folder":"IETF/RFC-4093","source":"IETF/RFC-4093/RFC-4093.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 3947 This document describes how to detect one or more network address\n translation devices (NATs) between IPsec hosts, and how to negotiate\n the use of UDP encapsulation of IPsec packets through NAT boxes in\n Internet Key Exchange (IKE).\n\nKivinen, et al. Standards Track [Page 1]\n\f\nRFC 3947 Negotiation of NAT-Traversal in the IKE January 2005 3947 hash key path nested-reference unchanged"},{"id":"IETF RFC 3949","type":"specification","body":"IETF","designation":"RFC 3949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3949.txt","https://www.rfc-editor.org/rfc/rfc3949.pdf"],"folder":"IETF/RFC-3949","files":{"txt":{"path":"standards/IETF/RFC-3949/RFC-3949.txt","sha256":"5f81c791d35fe261a40a46f2443bcfc38f8881c222398b8f4a0ff91b8b55a70c"}},"tags":["nested-reference","unchanged"],"summary":"This document is a revised version of RFC 2301. The revisions,\n summarized in the list attached as Annex B, are based on discussions\n and suggestions for improvements that have been made since RFC 2301\n was issued in March 1998, and on the results of independent\n implementations and interoperability testing.\n\n This RFC 2301 revision describes the Tag Image File Format (TIFF)\n representation of image data specified by the International\n Telecommunication Union (ITU-T) Recommendations for black-and-white\n and color facsimile. This file format specification is commonly\n known as TIFF for Fax eXtended (TIFF-FX). It formally defines\n minimal, extended, and lossless Joint Bi-level Image experts Group\n (JBIG) profiles (Profiles S, F, J) for black-and-white fax and base\n JPEG, lossless JBIG, and Mixed Raster Content profiles (Profiles C,\n L, M) for color and grayscale fax. These profiles corresp","scope_keywords":["3949","presentation","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null}],"search_text":"IETF RFC 3949 This document is a revised version of RFC 2301. The revisions,\n summarized in the list attached as Annex B, are based on discussions\n and suggestions for improvements that have been made since RFC 2301\n was issued in March 1998, and on the results of independent\n implementations and interoperability testing.\n\n This RFC 2301 revision describes the Tag Image File Format (TIFF)\n representation of image data specified by the International\n Telecommunication Union (ITU-T) Recommendations for black-and-white\n and color facsimile. This file format specification is commonly\n known as TIFF for Fax eXtended (TIFF-FX). It formally defines\n minimal, extended, and lossless Joint Bi-level Image experts Group\n (JBIG) profiles (Profiles S, F, J) for black-and-white fax and base\n JPEG, lossless JBIG, and Mixed Raster Content profiles (Profiles C,\n L, M) for color and grayscale fax. These profiles corresp 3949 presentation profile profiles nested-reference unchanged"},{"id":"IETF RFC 3951","type":"specification","body":"IETF","designation":"RFC 3951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3951.txt","https://www.rfc-editor.org/rfc/rfc3951.pdf"],"folder":"IETF/RFC-3951","files":{"txt":{"path":"standards/IETF/RFC-3951/RFC-3951.txt","sha256":"be5d79cc62d72ddc8ead6dede0ee5fff225305852b0beab2fca67f39e2aec47d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a speech codec suitable for robust voice\n communication over IP. The codec is developed by Global IP Sound\n (GIPS). It is designed for narrow band speech and results in a\n payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s\n for 20 ms frames. The codec enables graceful speech quality\n degradation in the case of lost frames, which occurs in connection\n with lost or delayed IP packets.\n\nAndersen, et al. Experimental [Page 1]\n\f\nRFC 3951 Internet Low Bit Rate Codec December 2004","scope_keywords":["3951"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null}],"search_text":"IETF RFC 3951 This document specifies a speech codec suitable for robust voice\n communication over IP. The codec is developed by Global IP Sound\n (GIPS). It is designed for narrow band speech and results in a\n payload bit rate of 13.33 kbit/s for 30 ms frames and 15.20 kbit/s\n for 20 ms frames. The codec enables graceful speech quality\n degradation in the case of lost frames, which occurs in connection\n with lost or delayed IP packets.\n\nAndersen, et al. Experimental [Page 1]\n\f\nRFC 3951 Internet Low Bit Rate Codec December 2004 3951 nested-reference unchanged"},{"id":"IETF RFC 3952","type":"specification","body":"IETF","designation":"RFC 3952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3952.txt","https://www.rfc-editor.org/rfc/rfc3952.pdf"],"folder":"IETF/RFC-3952","files":{"txt":{"path":"standards/IETF/RFC-3952/RFC-3952.txt","sha256":"45cf3aea542407dea29db7b8d4e54f89c09287250536398f4f93cab5e73ebce0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Real-time Transport Protocol (RTP)\n payload format for the internet Low Bit Rate Codec (iLBC) Speech\n developed by Global IP Sound (GIPS). Also, within the document there\n are included necessary details for the use of iLBC with MIME and\n Session Description Protocol (SDP).","scope_keywords":["3952","algorithm","key","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3951","folder":"IETF/RFC-3951","source":"IETF/RFC-3951/RFC-3951.txt","version":null},{"body":"IETF","designation":"RFC 4317","folder":"IETF/RFC-4317","source":"IETF/RFC-4317/RFC-4317.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null}],"search_text":"IETF RFC 3952 This document describes the Real-time Transport Protocol (RTP)\n payload format for the internet Low Bit Rate Codec (iLBC) Speech\n developed by Global IP Sound (GIPS). Also, within the document there\n are included necessary details for the use of iLBC with MIME and\n Session Description Protocol (SDP). 3952 algorithm key profile timestamp nested-reference unchanged"},{"id":"IETF RFC 3954","type":"specification","body":"IETF","designation":"RFC 3954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3954.txt","https://www.rfc-editor.org/rfc/rfc3954.pdf"],"folder":"IETF/RFC-3954","files":{"txt":{"path":"standards/IETF/RFC-3954/RFC-3954.txt","sha256":"dfb55ec88ce0a5f53139d3e1b06f039e5237a25c21122bcc3d4d40903505ee3f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the data export format for version 9 of Cisco\n Systems' NetFlow services, for use by implementations on the network\n elements and/or matching collector programs. The version 9 export\n format uses templates to provide access to observations of IP packet\n flows in a flexible and extensible manner. A template defines a\n collection of fields, with corresponding descriptions of structure\n and semantics.","scope_keywords":["3954","key","management","risk","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5153","folder":"IETF/RFC-5153","source":"IETF/RFC-5153/RFC-5153.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7632","folder":"IETF/RFC-7632","source":"IETF/RFC-7632/RFC-7632.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 3954 This document specifies the data export format for version 9 of Cisco\n Systems' NetFlow services, for use by implementations on the network\n elements and/or matching collector programs. The version 9 export\n format uses templates to provide access to observations of IP packet\n flows in a flexible and extensible manner. A template defines a\n collection of fields, with corresponding descriptions of structure\n and semantics. 3954 key management risk timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 3956","type":"specification","body":"IETF","designation":"RFC 3956","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3956.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3956.txt","https://www.rfc-editor.org/rfc/rfc3956.pdf"],"folder":"IETF/RFC-3956","files":{"txt":{"path":"standards/IETF/RFC-3956/RFC-3956.txt","sha256":"c00109e251a0f15f849299661ef782b92c3c56bc70b1a2d32a31e272c5170b4d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an address allocation policy in which the address\n of the Rendezvous Point (RP) is encoded in an IPv6 multicast group\n address. For Protocol Independent Multicast - Sparse Mode (PIM-SM),\n this can be seen as a specification of a group-to-RP mapping\n mechanism. This allows an easy deployment of scalable inter-domain\n multicast and simplifies the intra-domain multicast configuration as\n well. This memo updates the addressing format presented in RFC 3306.","scope_keywords":["3956","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4029","folder":"IETF/RFC-4029","source":"IETF/RFC-4029/RFC-4029.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4601","folder":"IETF/RFC-4601","source":"IETF/RFC-4601/RFC-4601.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 4864","folder":"IETF/RFC-4864","source":"IETF/RFC-4864/RFC-4864.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5157","folder":"IETF/RFC-5157","source":"IETF/RFC-5157/RFC-5157.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 3956 This memo defines an address allocation policy in which the address\n of the Rendezvous Point (RP) is encoded in an IPv6 multicast group\n address. For Protocol Independent Multicast - Sparse Mode (PIM-SM),\n this can be seen as a specification of a group-to-RP mapping\n mechanism. This allows an easy deployment of scalable inter-domain\n multicast and simplifies the intra-domain multicast configuration as\n well. This memo updates the addressing format presented in RFC 3306. 3956 key management policy nested-reference unchanged"},{"id":"IETF RFC 3958","type":"specification","body":"IETF","designation":"RFC 3958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3958.txt","https://www.rfc-editor.org/rfc/rfc3958.pdf"],"folder":"IETF/RFC-3958","files":{"txt":{"path":"standards/IETF/RFC-3958/RFC-3958.txt","sha256":"555b348e31c7eb99f071fa7926463321d0355da69df3f60226a5dbbcd22e6056"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a generalized mechanism for application service\n naming that allows service location without relying on rigid domain\n naming conventions (so-called name hacks). The proposal defines a\n Dynamic Delegation Discovery System (DDDS) Application to map domain\n name, application service name, and application protocol dynamically\n to target server and port.","scope_keywords":["3958","identification","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5928","folder":"IETF/RFC-5928","source":"IETF/RFC-5928/RFC-5928.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null}],"search_text":"IETF RFC 3958 This memo defines a generalized mechanism for application service\n naming that allows service location without relying on rigid domain\n naming conventions (so-called name hacks). The proposal defines a\n Dynamic Delegation Discovery System (DDDS) Application to map domain\n name, application service name, and application protocol dynamically\n to target server and port. 3958 identification key registered nested-reference unchanged"},{"id":"IETF RFC 3959","type":"specification","body":"IETF","designation":"RFC 3959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3959.txt","https://www.rfc-editor.org/rfc/rfc3959.pdf"],"folder":"IETF/RFC-3959","files":{"txt":{"path":"standards/IETF/RFC-3959/RFC-3959.txt","sha256":"f159fe2cdf40fe05a56fe680c0e571248ec43b477419dd0c55c964411061be9c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new disposition type (early-session) for the\n Content-Disposition header field in the Session Initiation Protocol\n (SIP). The treatment of \"early-session\" bodies is similar to the\n treatment of \"session\" bodies. That is, they follow the offer/answer\n model. Their only difference is that session descriptions whose\n disposition type is \"early-session\" are used to establish early media\n sessions within early dialogs, as opposed to regular sessions within\n regular dialogs.","scope_keywords":["3959","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3960","folder":"IETF/RFC-3960","source":"IETF/RFC-3960/RFC-3960.txt","version":null},{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null}],"search_text":"IETF RFC 3959 This document defines a new disposition type (early-session) for the\n Content-Disposition header field in the Session Initiation Protocol\n (SIP). The treatment of \"early-session\" bodies is similar to the\n treatment of \"session\" bodies. That is, they follow the offer/answer\n model. Their only difference is that session descriptions whose\n disposition type is \"early-session\" are used to establish early media\n sessions within early dialogs, as opposed to regular sessions within\n regular dialogs. 3959 encryption key management nested-reference unchanged"},{"id":"IETF RFC 3960","type":"specification","body":"IETF","designation":"RFC 3960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3960.txt","https://www.rfc-editor.org/rfc/rfc3960.pdf"],"folder":"IETF/RFC-3960","files":{"txt":{"path":"standards/IETF/RFC-3960/RFC-3960.txt","sha256":"2acca4a89bd4ba3a92deefb44c2b568808b740330498c2995a01c72703fed291"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to manage early media in the Session\n Initiation Protocol (SIP) using two models: the gateway model and the\n application server model. It also describes the inputs one needs to\n consider in defining local policies for ringing tone generation.","scope_keywords":["3960","key","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3959","folder":"IETF/RFC-3959","source":"IETF/RFC-3959/RFC-3959.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 3960 This document describes how to manage early media in the Session\n Initiation Protocol (SIP) using two models: the gateway model and the\n application server model. It also describes the inputs one needs to\n consider in defining local policies for ringing tone generation. 3960 key path policies nested-reference unchanged"},{"id":"IETF RFC 3966","type":"specification","body":"IETF","designation":"RFC 3966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3966.txt","https://www.rfc-editor.org/rfc/rfc3966.pdf"],"folder":"IETF/RFC-3966","files":{"txt":{"path":"standards/IETF/RFC-3966/RFC-3966.txt","sha256":"38d9aeec48d7f07120bd603f70b2da478218ffd3356eb362a651a31d0ff816bd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the URI (Uniform Resource Identifier) scheme\n \"tel\". The \"tel\" URI describes resources identified by telephone\n numbers. This document obsoletes RFC 2806.","scope_keywords":["3966","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4590","folder":"IETF/RFC-4590","source":"IETF/RFC-4590/RFC-4590.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null},{"body":"IETF","designation":"RFC 4759","folder":"IETF/RFC-4759","source":"IETF/RFC-4759/RFC-4759.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4904","folder":"IETF/RFC-4904","source":"IETF/RFC-4904/RFC-4904.txt","version":null},{"body":"IETF","designation":"RFC 4967","folder":"IETF/RFC-4967","source":"IETF/RFC-4967/RFC-4967.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 3966 This document specifies the URI (Uniform Resource Identifier) scheme\n \"tel\". The \"tel\" URI describes resources identified by telephone\n numbers. This document obsoletes RFC 2806. 3966 policy nested-reference unchanged"},{"id":"IETF RFC 3968","type":"specification","body":"IETF","designation":"RFC 3968","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3968.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3968.txt","https://www.rfc-editor.org/rfc/rfc3968.pdf"],"folder":"IETF/RFC-3968","files":{"txt":{"path":"standards/IETF/RFC-3968/RFC-3968.txt","sha256":"851d2077cee6839875d924a7de03c61cfaf9af88f13484a4926d9fec7a06feff"}},"tags":["nested-reference","unchanged"],"summary":"This document creates an Internet Assigned Number Authority (IANA)\n registry for the Session Initiation Protocol (SIP) header field\n parameters and parameter values. It also lists the already existing\n parameters and parameter values to be used as the initial entries for\n this registry.","scope_keywords":["3968","algorithm","authorization","key","policy","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 3968 This document creates an Internet Assigned Number Authority (IANA)\n registry for the Session Initiation Protocol (SIP) header field\n parameters and parameter values. It also lists the already existing\n parameters and parameter values to be used as the initial entries for\n this registry. 3968 algorithm authorization key policy registered risk nested-reference unchanged"},{"id":"IETF RFC 3969","type":"specification","body":"IETF","designation":"RFC 3969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3969.txt","https://www.rfc-editor.org/rfc/rfc3969.pdf"],"folder":"IETF/RFC-3969","files":{"txt":{"path":"standards/IETF/RFC-3969/RFC-3969.txt","sha256":"ca61b7aada8eed5211bc2d90d1658c4e8dd86dd8c5a76e83547d57951b743ff4"}},"tags":["nested-reference","unchanged"],"summary":"This document creates an Internet Assigned Number Authority (IANA)\n registry for the Session Initiation Protocol (SIP) and SIPS Uniform\n Resource Identifier (URI) parameters, and their values. It also\n lists the already existing parameters to be used as initial values\n for that registry.","scope_keywords":["3969","key","policy","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4967","folder":"IETF/RFC-4967","source":"IETF/RFC-4967/RFC-4967.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5727","folder":"IETF/RFC-5727","source":"IETF/RFC-5727/RFC-5727.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null}],"search_text":"IETF RFC 3969 This document creates an Internet Assigned Number Authority (IANA)\n registry for the Session Initiation Protocol (SIP) and SIPS Uniform\n Resource Identifier (URI) parameters, and their values. It also\n lists the already existing parameters to be used as initial values\n for that registry. 3969 key policy registered risk nested-reference unchanged"},{"id":"IETF RFC 3970","type":"specification","body":"IETF","designation":"RFC 3970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3970.txt","https://www.rfc-editor.org/rfc/rfc3970.pdf"],"folder":"IETF/RFC-3970","files":{"txt":{"path":"standards/IETF/RFC-3970/RFC-3970.txt","sha256":"f8dd08a4ee1e604e8ea675b4d5964040ec753e344e5e31d2db80c655a509d94d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Traffic Engineered\n (TE) Tunnels; for example, Multi-Protocol Label Switched Paths.","scope_keywords":["3970","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null}],"search_text":"IETF RFC 3970 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Traffic Engineered\n (TE) Tunnels; for example, Multi-Protocol Label Switched Paths. 3970 key management path nested-reference unchanged"},{"id":"IETF RFC 3981","type":"specification","body":"IETF","designation":"RFC 3981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3981.txt","https://www.rfc-editor.org/rfc/rfc3981.pdf"],"folder":"IETF/RFC-3981","files":{"txt":{"path":"standards/IETF/RFC-3981/RFC-3981.txt","sha256":"9b69e3510c3b0d995b80aafc5dd521c1062f234cf064505aaf74a4a36bb26db4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an application layer client-server protocol\n for a framework to represent the query and result operations of the\n information services of Internet registries. Specified in the\n Extensible Markup Language (XML), the protocol defines generic query\n and result operations and a mechanism for extending these operations\n for specific registry service needs.","scope_keywords":["3981","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4991","folder":"IETF/RFC-4991","source":"IETF/RFC-4991/RFC-4991.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null}],"search_text":"IETF RFC 3981 This document describes an application layer client-server protocol\n for a framework to represent the query and result operations of the\n information services of Internet registries. Specified in the\n Extensible Markup Language (XML), the protocol defines generic query\n and result operations and a mechanism for extending these operations\n for specific registry service needs. 3981 identification nested-reference unchanged"},{"id":"IETF RFC 3983","type":"specification","body":"IETF","designation":"RFC 3983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3983.txt","https://www.rfc-editor.org/rfc/rfc3983.pdf"],"folder":"IETF/RFC-3983","files":{"txt":{"path":"standards/IETF/RFC-3983/RFC-3983.txt","sha256":"31d69842ded820501e2074c5ff7e1d5014fbfc946102d7a357968049986bfb19"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use the Blocks Extensible Exchange\n Protocol (BEEP) as the application transport substrate for the\n Internet Registry Information Service (IRIS).","scope_keywords":["3983","authentication","http","identification","key","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 3983 This document specifies how to use the Blocks Extensible Exchange\n Protocol (BEEP) as the application transport substrate for the\n Internet Registry Information Service (IRIS). 3983 authentication http identification key profile tls nested-reference unchanged"},{"id":"IETF RFC 3984","type":"specification","body":"IETF","designation":"RFC 3984","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3984.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3984.txt","https://www.rfc-editor.org/rfc/rfc3984.pdf"],"folder":"IETF/RFC-3984","files":{"txt":{"path":"standards/IETF/RFC-3984/RFC-3984.txt","sha256":"02e6603980b078230c73ef6c72077d77219a50f89f90c513649f1c9275db1946"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an RTP Payload format for the ITU-T\n Recommendation H.264 video codec and the technically identical\n ISO/IEC International Standard 14496-10 video codec. The RTP payload\n format allows for packetization of one or more Network Abstraction\n Layer Units (NALUs), produced by an H.264 video encoder, in each RTP\n payload. The payload format has wide applicability, as it supports\n applications from simple low bit-rate conversational usage, to\n Internet video streaming with interleaved transmission, to high bit-\n rate video-on-demand.","scope_keywords":["3984"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null}],"search_text":"IETF RFC 3984 This memo describes an RTP Payload format for the ITU-T\n Recommendation H.264 video codec and the technically identical\n ISO/IEC International Standard 14496-10 video codec. The RTP payload\n format allows for packetization of one or more Network Abstraction\n Layer Units (NALUs), produced by an H.264 video encoder, in each RTP\n payload. The payload format has wide applicability, as it supports\n applications from simple low bit-rate conversational usage, to\n Internet video streaming with interleaved transmission, to high bit-\n rate video-on-demand. 3984 nested-reference unchanged"},{"id":"IETF RFC 3993","type":"specification","body":"IETF","designation":"RFC 3993","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3993.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3993.txt","https://www.rfc-editor.org/rfc/rfc3993.pdf"],"folder":"IETF/RFC-3993","files":{"txt":{"path":"standards/IETF/RFC-3993/RFC-3993.txt","sha256":"243a720b1572c715f9b536ae92dac5d987b019ba1d32070dfcac5c0b365eb87c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Subscriber-ID suboption for the Dynamic Host\n Configuration Protocol's (DHCP) relay agent information option. The\n suboption allows a DHCP relay agent to associate a stable\n \"Subscriber-ID\" with DHCP client messages in a way that is\n independent of the client and of the underlying physical network\n infrastructure.","scope_keywords":["3993","authentication","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4580","folder":"IETF/RFC-4580","source":"IETF/RFC-4580/RFC-4580.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null}],"search_text":"IETF RFC 3993 This memo defines a new Subscriber-ID suboption for the Dynamic Host\n Configuration Protocol's (DHCP) relay agent information option. The\n suboption allows a DHCP relay agent to associate a stable\n \"Subscriber-ID\" with DHCP client messages in a way that is\n independent of the client and of the underlying physical network\n infrastructure. 3993 authentication key path trust nested-reference unchanged"},{"id":"IETF RFC 3994","type":"specification","body":"IETF","designation":"RFC 3994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3994.txt","https://www.rfc-editor.org/rfc/rfc3994.pdf"],"folder":"IETF/RFC-3994","files":{"txt":{"path":"standards/IETF/RFC-3994/RFC-3994.txt","sha256":"2e2e02f25571282429ca3b3ec90d405ad5c796bf5e6b71fa2b2ab6f0c732243c"}},"tags":["nested-reference","unchanged"],"summary":"In instant messaging (IM) systems, it is useful to know during an IM\n conversation whether the other party is composing a message; e.g.,\n typing or recording an audio message. This document defines a new\n status message content type and XML namespace that conveys\n information about a message being composed. The status message can\n indicate the composition of a message of any type, including text,\n voice, or video. The status messages are delivered to the instant\n messaging recipient in the same manner as the instant messages\n themselves.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 3994 isComposing January 2005","scope_keywords":["3994","delivery","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null}],"search_text":"IETF RFC 3994 In instant messaging (IM) systems, it is useful to know during an IM\n conversation whether the other party is composing a message; e.g.,\n typing or recording an audio message. This document defines a new\n status message content type and XML namespace that conveys\n information about a message being composed. The status message can\n indicate the composition of a message of any type, including text,\n voice, or video. The status messages are delivered to the instant\n messaging recipient in the same manner as the instant messages\n themselves.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 3994 isComposing January 2005 3994 delivery key pid nested-reference unchanged"},{"id":"IETF RFC 4003","type":"specification","body":"IETF","designation":"RFC 4003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4003.txt","https://www.rfc-editor.org/rfc/rfc4003.pdf"],"folder":"IETF/RFC-4003","files":{"txt":{"path":"standards/IETF/RFC-4003/RFC-4003.txt","sha256":"7253ca6e0d71c1349b3a6c59aeb02a242e95d3567a73f7266467581e79aab6af"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies the procedures for the control of the label\n used on an output/downstream interface of the egress node of a Label\n Switched Path (LSP). This control is also known as \"Egress Control\".\n Support for Egress Control is implicit in Generalized Multi-Protocol\n Label Switching (GMPLS) Signaling. This document clarifies the\n specification of GMPLS Signaling and does not modify GMPLS signaling\n mechanisms and procedures.\n\n1. Background\n\n The ability to control the label used on the output/downstream\n interface of an egress node was one of the early requirements for\n GMPLS. In the initial GMPLS documents, this was called \"Egress\n Control\". As the GMPLS documents progressed, the ability to control\n a label on an egress interface was generalized to support control of\n a label on any interface. This generalization is seen in Section 6\n of [RFC3471] and Section 5.1 of [RFC3473]","scope_keywords":["4003","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null}],"search_text":"IETF RFC 4003 This document clarifies the procedures for the control of the label\n used on an output/downstream interface of the egress node of a Label\n Switched Path (LSP). This control is also known as \"Egress Control\".\n Support for Egress Control is implicit in Generalized Multi-Protocol\n Label Switching (GMPLS) Signaling. This document clarifies the\n specification of GMPLS Signaling and does not modify GMPLS signaling\n mechanisms and procedures.\n\n1. Background\n\n The ability to control the label used on the output/downstream\n interface of an egress node was one of the early requirements for\n GMPLS. In the initial GMPLS documents, this was called \"Egress\n Control\". As the GMPLS documents progressed, the ability to control\n a label on an egress interface was generalized to support control of\n a label on any interface. This generalization is seen in Section 6\n of [RFC3471] and Section 5.1 of [RFC3473] 4003 key path nested-reference unchanged"},{"id":"IETF RFC 4007","type":"specification","body":"IETF","designation":"RFC 4007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4007.txt","https://www.rfc-editor.org/rfc/rfc4007.pdf"],"folder":"IETF/RFC-4007","files":{"txt":{"path":"standards/IETF/RFC-4007/RFC-4007.txt","sha256":"d39c1d5327dd2c21f8eef9aa93d260353be5c6e3f6d2c157d1f4e3f784a259a3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the architectural characteristics, expected\n behavior, textual representation, and usage of IPv6 addresses of\n different scopes. According to a decision in the IPv6 working group,\n this document intentionally avoids the syntax and usage of unicast\n site-local addresses.\n\nDeering, et al. Standards Track [Page 1]\n\f\nRFC 4007 IPv6 Scoped Address Architecture March 2005","scope_keywords":["4007","key","pki","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7346","folder":"IETF/RFC-7346","source":"IETF/RFC-7346/RFC-7346.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 4007 This document specifies the architectural characteristics, expected\n behavior, textual representation, and usage of IPv6 addresses of\n different scopes. According to a decision in the IPv6 working group,\n this document intentionally avoids the syntax and usage of unicast\n site-local addresses.\n\nDeering, et al. Standards Track [Page 1]\n\f\nRFC 4007 IPv6 Scoped Address Architecture March 2005 4007 key pki presentation nested-reference unchanged"},{"id":"IETF RFC 4010","type":"specification","body":"IETF","designation":"RFC 4010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4010.txt","https://www.rfc-editor.org/rfc/rfc4010.pdf"],"folder":"IETF/RFC-4010","files":{"txt":{"path":"standards/IETF/RFC-4010/RFC-4010.txt","sha256":"13e00750f938bdbd21bb938010505288908e84610aa419079584d13ac3a66545"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the SEED encryption\n algorithm for encryption with the Cryptographic Message Syntax (CMS).\n\n SEED is added to the set of optional symmetric encryption algorithms\n in CMS by providing two classes of unique object identifiers (OIDs).\n One OID class defines the content encryption algorithms and the other\n defines the key encryption algorithms.\n\n1. Introduction\n\n This document specifies the conventions for using the SEED encryption\n algorithm [SEED][TTASSEED] for encryption with the Cryptographic\n Message Syntax (CMS)[CMS]. The relevant object identifiers (OIDs)\n and processing steps are provided so that SEED may be used in the CMS\n specification (RFC 3852, RFC 3370) for content and key encryption.\n\nPark, et al. Standards Track [Page 1]\n\f\nRFC 4010 The SEED Encryption Algorithm in CMS February 2005","scope_keywords":["4010","algorithm","algorithms","encryption","key","keys","pki"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 4010 This document specifies the conventions for using the SEED encryption\n algorithm for encryption with the Cryptographic Message Syntax (CMS).\n\n SEED is added to the set of optional symmetric encryption algorithms\n in CMS by providing two classes of unique object identifiers (OIDs).\n One OID class defines the content encryption algorithms and the other\n defines the key encryption algorithms.\n\n1. Introduction\n\n This document specifies the conventions for using the SEED encryption\n algorithm [SEED][TTASSEED] for encryption with the Cryptographic\n Message Syntax (CMS)[CMS]. The relevant object identifiers (OIDs)\n and processing steps are provided so that SEED may be used in the CMS\n specification (RFC 3852, RFC 3370) for content and key encryption.\n\nPark, et al. Standards Track [Page 1]\n\f\nRFC 4010 The SEED Encryption Algorithm in CMS February 2005 4010 algorithm algorithms encryption key keys pki nested-reference unchanged"},{"id":"IETF RFC 4018","type":"specification","body":"IETF","designation":"RFC 4018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4018.txt","https://www.rfc-editor.org/rfc/rfc4018.pdf"],"folder":"IETF/RFC-4018","files":{"txt":{"path":"standards/IETF/RFC-4018/RFC-4018.txt","sha256":"9f69f48c75689cbdb1528ce8d7370c092b2698875f46a91c527cf139447d0c39"}},"tags":["nested-reference","unchanged"],"summary":"The iSCSI protocol provides a way for hosts to access SCSI devices\n over an IP network. This document defines the use of the Service\n Location Protocol (SLP) by iSCSI hosts, devices, and management\n services, along with the SLP service type templates that describe the\n services they provide.","scope_keywords":["4018","attribute","attributes","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4018 The iSCSI protocol provides a way for hosts to access SCSI devices\n over an IP network. This document defines the use of the Service\n Location Protocol (SLP) by iSCSI hosts, devices, and management\n services, along with the SLP service type templates that describe the\n services they provide. 4018 attribute attributes key management registered nested-reference unchanged"},{"id":"IETF RFC 4019","type":"specification","body":"IETF","designation":"RFC 4019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4019.txt","https://www.rfc-editor.org/rfc/rfc4019.pdf"],"folder":"IETF/RFC-4019","files":{"txt":{"path":"standards/IETF/RFC-4019/RFC-4019.txt","sha256":"92a912376c34900be8094d67e2c8538ce5a0aa0334e1b8321cb45ef73c9b9b34"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Robust Header Compression (ROHC) profiles for\n compression of Real-Time Transport Protocol, User Datagram Protocol-\n Lite, and Internet Protocol (RTP/UDP-Lite/IP) packets and UDP-\n Lite/IP. These profiles are defined based on their differences with\n the profiles for UDP as specified in RFC 3095.","scope_keywords":["4019","key","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null}],"search_text":"IETF RFC 4019 This document defines Robust Header Compression (ROHC) profiles for\n compression of Real-Time Transport Protocol, User Datagram Protocol-\n Lite, and Internet Protocol (RTP/UDP-Lite/IP) packets and UDP-\n Lite/IP. These profiles are defined based on their differences with\n the profiles for UDP as specified in RFC 3095. 4019 key profile profiles nested-reference unchanged"},{"id":"IETF RFC 4028","type":"specification","body":"IETF","designation":"RFC 4028","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4028.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4028.txt","https://www.rfc-editor.org/rfc/rfc4028.pdf"],"folder":"IETF/RFC-4028","files":{"txt":{"path":"standards/IETF/RFC-4028/RFC-4028.txt","sha256":"41b18cee9a72eb12281f4984f1a59356425d811008951f6d593c5feb6a46d72d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Session Initiation Protocol\n (SIP). This extension allows for a periodic refresh of SIP sessions\n through a re-INVITE or UPDATE request. The refresh allows both user\n agents and proxies to determine whether the SIP session is still\n active. The extension defines two new header fields:\n Session-Expires, which conveys the lifetime of the session, and\n Min-SE, which conveys the minimum allowed value for the session\n timer.\n\nDonovan & Rosenberg Standards Track [Page 1]\n\f\nRFC 4028 Session Timer April 2005","scope_keywords":["4028","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null}],"search_text":"IETF RFC 4028 This document defines an extension to the Session Initiation Protocol\n (SIP). This extension allows for a periodic refresh of SIP sessions\n through a re-INVITE or UPDATE request. The refresh allows both user\n agents and proxies to determine whether the SIP session is still\n active. The extension defines two new header fields:\n Session-Expires, which conveys the lifetime of the session, and\n Min-SE, which conveys the minimum allowed value for the session\n timer.\n\nDonovan & Rosenberg Standards Track [Page 1]\n\f\nRFC 4028 Session Timer April 2005 4028 key nested-reference unchanged"},{"id":"IETF RFC 4032","type":"specification","body":"IETF","designation":"RFC 4032","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4032.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4032.txt","https://www.rfc-editor.org/rfc/rfc4032.pdf"],"folder":"IETF/RFC-4032","files":{"txt":{"path":"standards/IETF/RFC-4032/RFC-4032.txt","sha256":"01bcd08cf762af1fd2d1bc5b3271b6faa9a239521c2b4a7bf2db24a9bb40c7cd"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3312, which defines the framework for\n preconditions in SIP. We provide guidelines for authors of new\n precondition types and describe how to use SIP preconditions in\n situations that involve session mobility.","scope_keywords":["4032","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 4032 This document updates RFC 3312, which defines the framework for\n preconditions in SIP. We provide guidelines for authors of new\n precondition types and describe how to use SIP preconditions in\n situations that involve session mobility. 4032 attribute key nested-reference unchanged"},{"id":"IETF RFC 4039","type":"specification","body":"IETF","designation":"RFC 4039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4039.txt","https://www.rfc-editor.org/rfc/rfc4039.pdf"],"folder":"IETF/RFC-4039","files":{"txt":{"path":"standards/IETF/RFC-4039/RFC-4039.txt","sha256":"550b351075b38807277420d3a9973b37966bae48997fad24b38301a2e7137c57"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Dynamic Host Configuration Protocol\n version 4 (DHCPv4) option, modeled on the DHCPv6 Rapid Commit option,\n for obtaining IP address and configuration information using a\n 2-message exchange rather than the usual 4-message exchange,\n expediting client configuration.","scope_keywords":["4039","key","pid","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null}],"search_text":"IETF RFC 4039 This document defines a new Dynamic Host Configuration Protocol\n version 4 (DHCPv4) option, modeled on the DHCPv6 Rapid Commit option,\n for obtaining IP address and configuration information using a\n 2-message exchange rather than the usual 4-message exchange,\n expediting client configuration. 4039 key pid policies nested-reference unchanged"},{"id":"IETF RFC 4043","type":"specification","body":"IETF","designation":"RFC 4043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4043.txt","https://www.rfc-editor.org/rfc/rfc4043.pdf"],"folder":"IETF/RFC-4043","files":{"txt":{"path":"standards/IETF/RFC-4043/RFC-4043.txt","sha256":"d8906c8704c0bf68d1392ce98c7762e4de65b0a6347e5e2916f24c9f1a3054cb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new form of name, called permanent\n identifier, that may be included in the subjectAltName extension of a\n public key certificate issued to an entity.\n\n The permanent identifier is an optional feature that may be used by a\n CA to indicate that two or more certificates relate to the same\n entity, even if they contain different subject name (DNs) or\n different names in the subjectAltName extension, or if the name or\n the affiliation of that entity stored in the subject or another name\n form in the subjectAltName extension has changed.\n\n The subject name, carried in the subject field, is only unique for\n each subject entity certified by the one CA as defined by the issuer\n name field. However, the new name form can carry a name that is\n unique for each subject entity certified by a CA.\n\nPinkas & Gindin Standards Track [Page 1]\n\f\nRFC 4043 Permanent Identifier May 2005","scope_keywords":["4043","attribute","attributes","audit","certificate","certificates","identification","issuer","key","policy","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null}],"search_text":"IETF RFC 4043 This document defines a new form of name, called permanent\n identifier, that may be included in the subjectAltName extension of a\n public key certificate issued to an entity.\n\n The permanent identifier is an optional feature that may be used by a\n CA to indicate that two or more certificates relate to the same\n entity, even if they contain different subject name (DNs) or\n different names in the subjectAltName extension, or if the name or\n the affiliation of that entity stored in the subject or another name\n form in the subjectAltName extension has changed.\n\n The subject name, carried in the subject field, is only unique for\n each subject entity certified by the one CA as defined by the issuer\n name field. However, the new name form can carry a name that is\n unique for each subject entity certified by a CA.\n\nPinkas & Gindin Standards Track [Page 1]\n\f\nRFC 4043 Permanent Identifier May 2005 4043 attribute attributes audit certificate certificates identification issuer key policy subject validation nested-reference unchanged"},{"id":"IETF RFC 4049","type":"specification","body":"IETF","designation":"RFC 4049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4049.txt","https://www.rfc-editor.org/rfc/rfc4049.pdf"],"folder":"IETF/RFC-4049","files":{"txt":{"path":"standards/IETF/RFC-4049/RFC-4049.txt","sha256":"5e7adf35d04d7f533433b0fbca63a1ef25bcec9bdfa90d9c46d442a5a539d3dc"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new ASN.1 type for representing time:\n BinaryTime. This document also specifies an alternate to the\n signing-time attribute for use with the Cryptographic Message Syntax\n (CMS) SignedData and AuthenticatedData content types; the binary-\n signing-time attribute uses BinaryTime. CMS and the signing-time\n attribute are defined in RFC 3852.\n\n1. Introduction\n\n This document specifies a new ASN.1 [ASN1] type for representing\n time: BinaryTime. This ASN.1 type can be used to represent date and\n time values.\n\n This document also specifies an alternative to the signing-time\n attribute used with the Cryptographic Message Syntax (CMS) [CMS]\n SignedData and AuthenticatedData content types, allowing the\n BinaryTime type to be used instead of the traditional UTCTime and\n GeneralizedTime types.","scope_keywords":["4049","attribute","attributes","key","presentation","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null}],"search_text":"IETF RFC 4049 This document specifies a new ASN.1 type for representing time:\n BinaryTime. This document also specifies an alternate to the\n signing-time attribute for use with the Cryptographic Message Syntax\n (CMS) SignedData and AuthenticatedData content types; the binary-\n signing-time attribute uses BinaryTime. CMS and the signing-time\n attribute are defined in RFC 3852.\n\n1. Introduction\n\n This document specifies a new ASN.1 [ASN1] type for representing\n time: BinaryTime. This ASN.1 type can be used to represent date and\n time values.\n\n This document also specifies an alternative to the signing-time\n attribute used with the Cryptographic Message Syntax (CMS) [CMS]\n SignedData and AuthenticatedData content types, allowing the\n BinaryTime type to be used instead of the traditional UTCTime and\n GeneralizedTime types. 4049 attribute attributes key presentation trust tsp nested-reference unchanged"},{"id":"IETF RFC 4066","type":"specification","body":"IETF","designation":"RFC 4066","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4066.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4066.txt","https://www.rfc-editor.org/rfc/rfc4066.pdf"],"folder":"IETF/RFC-4066","files":{"txt":{"path":"standards/IETF/RFC-4066/RFC-4066.txt","sha256":"395a3194c659c727641818e15e16b8e101c05372139017d050f87f76e3f33bed"}},"tags":["nested-reference","unchanged"],"summary":"To enable seamless IP-layer handover of a mobile node (MN) from one\n access router (AR) to another, the MN is required to discover the\n identities and capabilities of candidate ARs (CARs) for handover\n prior to the initiation of the handover. The act of discovery of\n CARs has two aspects: identifying the IP addresses of the CARs and\n finding their capabilities. This process is called \"candidate access\n router discovery\" (CARD). At the time of IP-layer handover, the CAR,\n whose capabilities are a good match to the preferences of the MN, is\n chosen as the target AR for handover. The protocol described in this\n document allows a mobile node to perform CARD.","scope_keywords":["4066","algorithm","certificate","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4065","folder":"IETF/RFC-4065","source":"IETF/RFC-4065/RFC-4065.txt","version":null},{"body":"IETF","designation":"RFC 5113","folder":"IETF/RFC-5113","source":"IETF/RFC-5113/RFC-5113.txt","version":null}],"search_text":"IETF RFC 4066 To enable seamless IP-layer handover of a mobile node (MN) from one\n access router (AR) to another, the MN is required to discover the\n identities and capabilities of candidate ARs (CARs) for handover\n prior to the initiation of the handover. The act of discovery of\n CARs has two aspects: identifying the IP addresses of the CARs and\n finding their capabilities. This process is called \"candidate access\n router discovery\" (CARD). At the time of IP-layer handover, the CAR,\n whose capabilities are a good match to the preferences of the MN, is\n chosen as the target AR for handover. The protocol described in this\n document allows a mobile node to perform CARD. 4066 algorithm certificate key nested-reference unchanged"},{"id":"IETF RFC 4068","type":"specification","body":"IETF","designation":"RFC 4068","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4068.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4068.txt","https://www.rfc-editor.org/rfc/rfc4068.pdf"],"folder":"IETF/RFC-4068","files":{"txt":{"path":"standards/IETF/RFC-4068/RFC-4068.txt","sha256":"c3a22d4c5205dcc014d8fb1477bb2fd0e7ff4fa3b9cf3f0651200227e586ca4f"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 enables a Mobile Node to maintain its connectivity to the\n Internet when moving from one Access Router to another, a process\n referred to as handover. During handover, there is a period during\n which the Mobile Node is unable to send or receive packets because of\n link switching delay and IP protocol operations. This \"handover\n latency\" resulting from standard Mobile IPv6 procedures, namely\n movement detection, new Care of Address configuration, and Binding\n Update, is often unacceptable to real-time traffic such as Voice over\n IP. Reducing the handover latency could be beneficial to non-real-\n time, throughput-sensitive applications as well. This document\n specifies a protocol to improve handover latency due to Mobile IPv6\n procedures. This document does not address improving the link\n switching latency.\n\nKoodli, Ed. Experimental [Page 1]\n\f\nRFC 4068 Fast Handovers for Mobile","scope_keywords":["4068","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4140","folder":"IETF/RFC-4140","source":"IETF/RFC-4140/RFC-4140.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5181","folder":"IETF/RFC-5181","source":"IETF/RFC-5181/RFC-5181.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null}],"search_text":"IETF RFC 4068 Mobile IPv6 enables a Mobile Node to maintain its connectivity to the\n Internet when moving from one Access Router to another, a process\n referred to as handover. During handover, there is a period during\n which the Mobile Node is unable to send or receive packets because of\n link switching delay and IP protocol operations. This \"handover\n latency\" resulting from standard Mobile IPv6 procedures, namely\n movement detection, new Care of Address configuration, and Binding\n Update, is often unacceptable to real-time traffic such as Voice over\n IP. Reducing the handover latency could be beneficial to non-real-\n time, throughput-sensitive applications as well. This document\n specifies a protocol to improve handover latency due to Mobile IPv6\n procedures. This document does not address improving the link\n switching latency.\n\nKoodli, Ed. Experimental [Page 1]\n\f\nRFC 4068 Fast Handovers for Mobile 4068 key nested-reference unchanged"},{"id":"IETF RFC 4084","type":"specification","body":"IETF","designation":"RFC 4084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4084.txt","https://www.rfc-editor.org/rfc/rfc4084.pdf"],"folder":"IETF/RFC-4084","files":{"txt":{"path":"standards/IETF/RFC-4084/RFC-4084.txt","sha256":"584943b7f1c7d8b6f61495f0c761b9c4de20d12f7d224575879527a3fd536e19"}},"tags":["nested-reference","unchanged"],"summary":"As the Internet has evolved, many types of arrangements have been\n advertised and sold as \"Internet connectivity\". Because these may\n differ significantly in the capabilities they offer, the range of\n options, and the lack of any standard terminology, the effort to\n distinguish between these services has caused considerable consumer\n confusion. This document provides a list of terms and definitions\n that may be helpful to providers, consumers, and, potentially,\n regulators in clarifying the type and character of services being\n offered.","scope_keywords":["4084","http","https","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 7754","folder":"IETF/RFC-7754","source":"IETF/RFC-7754/RFC-7754.txt","version":null}],"search_text":"IETF RFC 4084 As the Internet has evolved, many types of arrangements have been\n advertised and sold as \"Internet connectivity\". Because these may\n differ significantly in the capabilities they offer, the range of\n options, and the lack of any standard terminology, the effort to\n distinguish between these services has caused considerable consumer\n confusion. This document provides a list of terms and definitions\n that may be helpful to providers, consumers, and, potentially,\n regulators in clarifying the type and character of services being\n offered. 4084 http https pid subject nested-reference unchanged"},{"id":"IETF RFC 4090","type":"specification","body":"IETF","designation":"RFC 4090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4090.txt","https://www.rfc-editor.org/rfc/rfc4090.pdf"],"folder":"IETF/RFC-4090","files":{"txt":{"path":"standards/IETF/RFC-4090/RFC-4090.txt","sha256":"9559c4885710714519585569c66831900be5fb4ee2b2d9b05080422be13f0084"}},"tags":["nested-reference","unchanged"],"summary":"This document defines RSVP-TE extensions to establish backup label-\n switched path (LSP) tunnels for local repair of LSP tunnels. These\n mechanisms enable the re-direction of traffic onto backup LSP tunnels\n in 10s of milliseconds, in the event of a failure.\n\n Two methods are defined here. The one-to-one backup method creates\n detour LSPs for each protected LSP at each potential point of local\n repair. The facility backup method creates a bypass tunnel to\n protect a potential failure point; by taking advantage of MPLS label\n stacking, this bypass tunnel can protect a set of LSPs that have\n similar backup constraints. Both methods can be used to protect\n links and nodes during network failure. The described behavior and\n extensions to RSVP allow nodes to implement either method or both and\n to interoperate in a mixed network.\n\nPan, et al. Standards Track [Page 1]\n\f\nRFC 4090 RSVP-TE Fast R","scope_keywords":["4090","attribute","identification","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4461","folder":"IETF/RFC-4461","source":"IETF/RFC-4461/RFC-4461.txt","version":null},{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4090 This document defines RSVP-TE extensions to establish backup label-\n switched path (LSP) tunnels for local repair of LSP tunnels. These\n mechanisms enable the re-direction of traffic onto backup LSP tunnels\n in 10s of milliseconds, in the event of a failure.\n\n Two methods are defined here. The one-to-one backup method creates\n detour LSPs for each protected LSP at each potential point of local\n repair. The facility backup method creates a bypass tunnel to\n protect a potential failure point; by taking advantage of MPLS label\n stacking, this bypass tunnel can protect a set of LSPs that have\n similar backup constraints. Both methods can be used to protect\n links and nodes during network failure. The described behavior and\n extensions to RSVP allow nodes to implement either method or both and\n to interoperate in a mixed network.\n\nPan, et al. Standards Track [Page 1]\n\f\nRFC 4090 RSVP-TE Fast R 4090 attribute identification path nested-reference unchanged"},{"id":"IETF RFC 4091","type":"specification","body":"IETF","designation":"RFC 4091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4091.txt","https://www.rfc-editor.org/rfc/rfc4091.pdf"],"folder":"IETF/RFC-4091","files":{"txt":{"path":"standards/IETF/RFC-4091/RFC-4091.txt","sha256":"1e7a9ecf6ae597a657343e75c214d46be85fe40383c38b56a454ca559f21b4b4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Alternative Network Address Types (ANAT)\n semantics for the Session Description Protocol (SDP) grouping\n framework. The ANAT semantics allow alternative types of network\n addresses to establish a particular media stream.","scope_keywords":["4091","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4092","folder":"IETF/RFC-4092","source":"IETF/RFC-4092/RFC-4092.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4091 This document defines the Alternative Network Address Types (ANAT)\n semantics for the Session Description Protocol (SDP) grouping\n framework. The ANAT semantics allow alternative types of network\n addresses to establish a particular media stream. 4091 attribute key nested-reference unchanged"},{"id":"IETF RFC 4092","type":"specification","body":"IETF","designation":"RFC 4092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4092.txt","https://www.rfc-editor.org/rfc/rfc4092.pdf"],"folder":"IETF/RFC-4092","files":{"txt":{"path":"standards/IETF/RFC-4092/RFC-4092.txt","sha256":"585fe6d186bc400a4b70003140d9216144af36b8422c0e8a54d126fa2f2f9f38"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use the Alternative Network Address\n Types (ANAT) semantics of the Session Description Protocol (SDP)\n grouping framework in SIP. In particular, we define the sdp-anat SIP\n option-tag. This SIP option-tag ensures that SDP session\n descriptions that use ANAT are only handled by SIP entities with ANAT\n support. To justify the need for such a SIP option-tag, we describe\n what could possibly happen if an ANAT-unaware SIP entity tried to\n handle media lines grouped with ANAT.","scope_keywords":["4092","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4091","folder":"IETF/RFC-4091","source":"IETF/RFC-4091/RFC-4091.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 4092 This document describes how to use the Alternative Network Address\n Types (ANAT) semantics of the Session Description Protocol (SDP)\n grouping framework in SIP. In particular, we define the sdp-anat SIP\n option-tag. This SIP option-tag ensures that SDP session\n descriptions that use ANAT are only handled by SIP entities with ANAT\n support. To justify the need for such a SIP option-tag, we describe\n what could possibly happen if an ANAT-unaware SIP entity tried to\n handle media lines grouped with ANAT. 4092 key nested-reference unchanged"},{"id":"IETF RFC 4095","type":"specification","body":"IETF","designation":"RFC 4095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4095.txt","https://www.rfc-editor.org/rfc/rfc4095.pdf"],"folder":"IETF/RFC-4095","files":{"txt":{"path":"standards/IETF/RFC-4095/RFC-4095.txt","sha256":"96f7a3f543519cab954df9d5c4fc61419907efd4788873409ff90f2b6f9c5495"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a mechanism for finding a URI associated with\n a solicitation class keyword, which is defined in RFC 3865, the No\n Soliciting SMTP Service Extension. Solicitation class keywords are\n simple labels consisting of a domain name that has been reversed,\n such as \"org.example.adv\". These solicitation class keywords are\n inserted in selected header fields or used in the ESMTP service\n extension, including a new \"No-Solicit:\" header, which can contain\n one or more solicitation class keywords inserted by the sender.\n\n This document specifies an application based on the Dynamic\n Delegation Discovery System (DDDS) described in RFC 3401 and related\n documents. An algorithm is specified to associate a solicitation\n class keyword with a URI which contains further information about the\n meaning and usage of that solicitation class keyword. For example,\n the registrant of the \"exa","scope_keywords":["4095","algorithm","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null}],"search_text":"IETF RFC 4095 This document proposes a mechanism for finding a URI associated with\n a solicitation class keyword, which is defined in RFC 3865, the No\n Soliciting SMTP Service Extension. Solicitation class keywords are\n simple labels consisting of a domain name that has been reversed,\n such as \"org.example.adv\". These solicitation class keywords are\n inserted in selected header fields or used in the ESMTP service\n extension, including a new \"No-Solicit:\" header, which can contain\n one or more solicitation class keywords inserted by the sender.\n\n This document specifies an application based on the Dynamic\n Delegation Discovery System (DDDS) described in RFC 3401 and related\n documents. An algorithm is specified to associate a solicitation\n class keyword with a URI which contains further information about the\n meaning and usage of that solicitation class keyword. For example,\n the registrant of the \"exa 4095 algorithm delivery key nested-reference unchanged"},{"id":"IETF RFC 4103","type":"specification","body":"IETF","designation":"RFC 4103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4103.txt","https://www.rfc-editor.org/rfc/rfc4103.pdf"],"folder":"IETF/RFC-4103","files":{"txt":{"path":"standards/IETF/RFC-4103/RFC-4103.txt","sha256":"2a23a9fa870d75ef3568afd17a88a0eff102d674edd842c9aa620191046980ec"}},"tags":["nested-reference","unchanged"],"summary":"This memo obsoletes RFC 2793; it describes how to carry real-time\n text conversation session contents in RTP packets. Text conversation\n session contents are specified in ITU-T Recommendation T.140.\n\n One payload format is described for transmitting text on a separate\n RTP session dedicated for the transmission of text.\n\n This RTP payload description recommends a method to include redundant\n text from already transmitted packets in order to reduce the risk of\n text loss caused by packet loss.\n\nHellstrom & Jones Standards Track [Page 1]\n\f\nRFC 4103 RTP Payload for Text Conversation June 2005","scope_keywords":["4103","authentication","delivery","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4102","folder":"IETF/RFC-4102","source":"IETF/RFC-4102/RFC-4102.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 4597","folder":"IETF/RFC-4597","source":"IETF/RFC-4597/RFC-4597.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 4103 This memo obsoletes RFC 2793; it describes how to carry real-time\n text conversation session contents in RTP packets. Text conversation\n session contents are specified in ITU-T Recommendation T.140.\n\n One payload format is described for transmitting text on a separate\n RTP session dedicated for the transmission of text.\n\n This RTP payload description recommends a method to include redundant\n text from already transmitted packets in order to reduce the risk of\n text loss caused by packet loss.\n\nHellstrom & Jones Standards Track [Page 1]\n\f\nRFC 4103 RTP Payload for Text Conversation June 2005 4103 authentication delivery key risk nested-reference unchanged"},{"id":"IETF RFC 4105","type":"specification","body":"IETF","designation":"RFC 4105","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4105.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4105.txt","https://www.rfc-editor.org/rfc/rfc4105.pdf"],"folder":"IETF/RFC-4105","files":{"txt":{"path":"standards/IETF/RFC-4105/RFC-4105.txt","sha256":"95bc9c5535413dbe788d8aad2bea0241aa312fc122bdcd7e6e3ec662847b8274"}},"tags":["nested-reference","unchanged"],"summary":"This document lists a detailed set of functional requirements for the\n support of inter-area MPLS Traffic Engineering (inter-area MPLS TE).\n It is intended that solutions that specify procedures and protocol\n extensions for inter-area MPLS TE satisfy these requirements.","scope_keywords":["4105","key","management","path","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4561","folder":"IETF/RFC-4561","source":"IETF/RFC-4561/RFC-4561.txt","version":null},{"body":"IETF","designation":"RFC 4655","folder":"IETF/RFC-4655","source":"IETF/RFC-4655/RFC-4655.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4736","folder":"IETF/RFC-4736","source":"IETF/RFC-4736/RFC-4736.txt","version":null},{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null}],"search_text":"IETF RFC 4105 This document lists a detailed set of functional requirements for the\n support of inter-area MPLS Traffic Engineering (inter-area MPLS TE).\n It is intended that solutions that specify procedures and protocol\n extensions for inter-area MPLS TE satisfy these requirements. 4105 key management path policy risk nested-reference unchanged"},{"id":"IETF RFC 4106","type":"specification","body":"IETF","designation":"RFC 4106","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4106.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4106.txt","https://www.rfc-editor.org/rfc/rfc4106.pdf"],"folder":"IETF/RFC-4106","files":{"txt":{"path":"standards/IETF/RFC-4106/RFC-4106.txt","sha256":"2a0d8b0274cf307156e18708a13e6f9bfd0ed5124dca234b0a1ed1590a5a886a"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n in Galois/Counter Mode (GCM) as an IPsec Encapsulating Security\n Payload (ESP) mechanism to provide confidentiality and data origin\n authentication. This method can be efficiently implemented in\n hardware for speeds of 10 gigabits per second and above, and is also\n well-suited to software implementations.","scope_keywords":["4106","algorithm","algorithms","attribute","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5288","folder":"IETF/RFC-5288","source":"IETF/RFC-5288/RFC-5288.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 4106 This memo describes the use of the Advanced Encryption Standard (AES)\n in Galois/Counter Mode (GCM) as an IPsec Encapsulating Security\n Payload (ESP) mechanism to provide confidentiality and data origin\n authentication. This method can be efficiently implemented in\n hardware for speeds of 10 gigabits per second and above, and is also\n well-suited to software implementations. 4106 algorithm algorithms attribute authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 4107","type":"specification","body":"IETF","designation":"RFC 4107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4107.txt","https://www.rfc-editor.org/rfc/rfc4107.pdf"],"folder":"IETF/RFC-4107","files":{"txt":{"path":"standards/IETF/RFC-4107/RFC-4107.txt","sha256":"78e4684edbbb994ba32ff2edf99ea04b0383ee76718c898e6ad88ab8304d3eb3"}},"tags":["nested-reference","unchanged"],"summary":"The question often arises of whether a given security system requires\n some form of automated key management, or whether manual keying is\n sufficient. This memo provides guidelines for making such decisions.\n When symmetric cryptographic mechanisms are used in a protocol, the\n presumption is that automated key management is generally but not\n always needed. If manual keying is proposed, the burden of proving\n that automated key management is not required falls to the proposer.\n\n1. Introduction\n\n The question often arises of whether or not a given security system\n requires some form of automated key management, or whether manual\n keying is sufficient.\n\n There is not one answer to that question; circumstances differ. In\n general, automated key management SHOULD be used. Occasionally,\n relying on manual key management is reasonable; we propose some\n guidelines for making that judgment.\n\n On","scope_keywords":["4107","algorithm","algorithms","authentication","certificate","certificates","key","keys","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4449","folder":"IETF/RFC-4449","source":"IETF/RFC-4449/RFC-4449.txt","version":null},{"body":"IETF","designation":"RFC 4564","folder":"IETF/RFC-4564","source":"IETF/RFC-4564/RFC-4564.txt","version":null},{"body":"IETF","designation":"RFC 4656","folder":"IETF/RFC-4656","source":"IETF/RFC-4656/RFC-4656.txt","version":null},{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null},{"body":"IETF","designation":"RFC 4822","folder":"IETF/RFC-4822","source":"IETF/RFC-4822/RFC-4822.txt","version":null},{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6421","folder":"IETF/RFC-6421","source":"IETF/RFC-6421/RFC-6421.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 4107 The question often arises of whether a given security system requires\n some form of automated key management, or whether manual keying is\n sufficient. This memo provides guidelines for making such decisions.\n When symmetric cryptographic mechanisms are used in a protocol, the\n presumption is that automated key management is generally but not\n always needed. If manual keying is proposed, the burden of proving\n that automated key management is not required falls to the proposer.\n\n1. Introduction\n\n The question often arises of whether or not a given security system\n requires some form of automated key management, or whether manual\n keying is sufficient.\n\n There is not one answer to that question; circumstances differ. In\n general, automated key management SHOULD be used. Occasionally,\n relying on manual key management is reasonable; we propose some\n guidelines for making that judgment.\n\n On 4107 algorithm algorithms authentication certificate certificates key keys management tls nested-reference unchanged"},{"id":"IETF RFC 4108","type":"specification","body":"IETF","designation":"RFC 4108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4108.txt","https://www.rfc-editor.org/rfc/rfc4108.pdf"],"folder":"IETF/RFC-4108","files":{"txt":{"path":"standards/IETF/RFC-4108/RFC-4108.txt","sha256":"d843dc392f8d143009d71c7306cb7e5459c5359bcac093a4ab086ea0162626a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Cryptographic Message Syntax\n (CMS) to protect firmware packages, which provide object code for one\n or more hardware module components. CMS is specified in RFC 3852. A\n digital signature is used to protect the firmware package from\n undetected modification and to provide data origin authentication.\n Encryption is optionally used to protect the firmware package from\n disclosure, and compression is optionally used to reduce the size of\n the protected firmware package. A firmware package loading receipt\n can optionally be generated to acknowledge the successful loading of\n a firmware package. Similarly, a firmware package load error report\n can optionally be generated to convey the failure to load a firmware\n package.\n\nHousley Standards Track [Page 1]\n\f\nRFC 4108 Using CMS to Protect Firmware Packages August 2005","scope_keywords":["4108","algorithm","algorithms","attribute","attributes","authentication","certificate","encryption","key","keys","profile","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null}],"search_text":"IETF RFC 4108 This document describes the use of the Cryptographic Message Syntax\n (CMS) to protect firmware packages, which provide object code for one\n or more hardware module components. CMS is specified in RFC 3852. A\n digital signature is used to protect the firmware package from\n undetected modification and to provide data origin authentication.\n Encryption is optionally used to protect the firmware package from\n disclosure, and compression is optionally used to reduce the size of\n the protected firmware package. A firmware package loading receipt\n can optionally be generated to acknowledge the successful loading of\n a firmware package. Similarly, a firmware package load error report\n can optionally be generated to convey the failure to load a firmware\n package.\n\nHousley Standards Track [Page 1]\n\f\nRFC 4108 Using CMS to Protect Firmware Packages August 2005 4108 algorithm algorithms attribute attributes authentication certificate encryption key keys profile signature trust nested-reference unchanged"},{"id":"IETF RFC 4109","type":"specification","body":"IETF","designation":"RFC 4109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4109.txt","https://www.rfc-editor.org/rfc/rfc4109.pdf"],"folder":"IETF/RFC-4109","files":{"txt":{"path":"standards/IETF/RFC-4109/RFC-4109.txt","sha256":"c39145667b7f12a8b600bc1e0f04a8d8cfacf368c1cdbf1848be56090ef0091c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Hoffman\nRequest for Comments: 4109 VPN Consortium\nUpdates: 2409 May 2005\nCategory: Standards Track\n\n Algorithms for Internet Key Exchange version 1 (IKEv1)\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The required and suggested algorithms in the original Internet Key\n Exchange version 1 (IKEv1) specification do not reflect the current\n reality of the IPsec market requirements. The original specification\n allows weak security and suggests algorithms that are thinly\n implemented.","scope_keywords":["4109","algorithm","algorithms","authentication","encryption","hash","hashing","key","license","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4109 Network Working Group P. Hoffman\nRequest for Comments: 4109 VPN Consortium\nUpdates: 2409 May 2005\nCategory: Standards Track\n\n Algorithms for Internet Key Exchange version 1 (IKEv1)\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The required and suggested algorithms in the original Internet Key\n Exchange version 1 (IKEv1) specification do not reflect the current\n reality of the IPsec market requirements. The original specification\n allows weak security and suggests algorithms that are thinly\n implemented. 4109 algorithm algorithms authentication encryption hash hashing key license signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 4119","type":"specification","body":"IETF","designation":"RFC 4119","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4119.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4119.txt","https://www.rfc-editor.org/rfc/rfc4119.pdf"],"folder":"IETF/RFC-4119","files":{"txt":{"path":"standards/IETF/RFC-4119/RFC-4119.txt","sha256":"7d31fc526a68aac48bd9240601a26dc7b239ec33e2e0fe6ef343666398a31afd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an object format for carrying geographical\n information on the Internet. This location object extends the\n Presence Information Data Format (PIDF), which was designed for\n communicating privacy-sensitive presence information and which has\n similar properties.\n\nPeterson Standards Track [Page 1]\n\f\nRFC 4119 GEOPRIV Location Object December 2005","scope_keywords":["4119","attribute","holder","http","key","pid","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4189","folder":"IETF/RFC-4189","source":"IETF/RFC-4189/RFC-4189.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5808","folder":"IETF/RFC-5808","source":"IETF/RFC-5808/RFC-5808.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 4119 This document describes an object format for carrying geographical\n information on the Internet. This location object extends the\n Presence Information Data Format (PIDF), which was designed for\n communicating privacy-sensitive presence information and which has\n similar properties.\n\nPeterson Standards Track [Page 1]\n\f\nRFC 4119 GEOPRIV Location Object December 2005 4119 attribute holder http key pid policies policy nested-reference unchanged"},{"id":"IETF RFC 4124","type":"specification","body":"IETF","designation":"RFC 4124","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4124.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4124.txt","https://www.rfc-editor.org/rfc/rfc4124.pdf"],"folder":"IETF/RFC-4124","files":{"txt":{"path":"standards/IETF/RFC-4124/RFC-4124.txt","sha256":"638da33973675e759253f7be8c1a12d3bf3b17728445510165dc1528f7ce6cb4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the protocol extensions for support of\n Diffserv-aware MPLS Traffic Engineering (DS-TE). This includes\n generalization of the semantics of a number of Interior Gateway\n Protocol (IGP) extensions already defined for existing MPLS Traffic\n Engineering in RFC 3630, RFC 3784, and additional IGP extensions\n beyond those. This also includes extensions to RSVP-TE signaling\n beyond those already specified in RFC 3209 for existing MPLS Traffic\n Engineering. These extensions address the requirements for DS-TE\n spelled out in RFC 3564.","scope_keywords":["4124","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4124 This document specifies the protocol extensions for support of\n Diffserv-aware MPLS Traffic Engineering (DS-TE). This includes\n generalization of the semantics of a number of Interior Gateway\n Protocol (IGP) extensions already defined for existing MPLS Traffic\n Engineering in RFC 3630, RFC 3784, and additional IGP extensions\n beyond those. This also includes extensions to RSVP-TE signaling\n beyond those already specified in RFC 3209 for existing MPLS Traffic\n Engineering. These extensions address the requirements for DS-TE\n spelled out in RFC 3564. 4124 path nested-reference unchanged"},{"id":"IETF RFC 4125","type":"specification","body":"IETF","designation":"RFC 4125","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4125.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4125.txt","https://www.rfc-editor.org/rfc/rfc4125.pdf"],"folder":"IETF/RFC-4125","files":{"txt":{"path":"standards/IETF/RFC-4125/RFC-4125.txt","sha256":"92c05280cab41c5a978d916ea0bfef1d7deef2880a270c4e80e7248824e98d15"}},"tags":["nested-reference","unchanged"],"summary":"This document provides specifications for one Bandwidth Constraints\n Model for Diffserv-aware MPLS Traffic Engineering, which is referred\n to as the Maximum Allocation Model.","scope_keywords":["4125","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 4125 This document provides specifications for one Bandwidth Constraints\n Model for Diffserv-aware MPLS Traffic Engineering, which is referred\n to as the Maximum Allocation Model. 4125 key nested-reference unchanged"},{"id":"IETF RFC 4126","type":"specification","body":"IETF","designation":"RFC 4126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4126.txt","https://www.rfc-editor.org/rfc/rfc4126.pdf"],"folder":"IETF/RFC-4126","files":{"txt":{"path":"standards/IETF/RFC-4126/RFC-4126.txt","sha256":"6f9a12a9f11076cb135c0a02c20a08433da17887136ba1f51e349fb21cd6dee8"}},"tags":["nested-reference","unchanged"],"summary":"This document complements the Diffserv-aware MPLS Traffic Engineering\n (DS-TE) requirements document by giving a functional specification\n for the Maximum Allocation with Reservation (MAR) Bandwidth\n Constraints Model. Assumptions, applicability, and examples of the\n operation of the MAR Bandwidth Constraints Model are presented. MAR\n performance is analyzed relative to the criteria for selecting a\n Bandwidth Constraints Model, in order to provide guidance to user\n implementation of the model in their networks.","scope_keywords":["4126","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null}],"search_text":"IETF RFC 4126 This document complements the Diffserv-aware MPLS Traffic Engineering\n (DS-TE) requirements document by giving a functional specification\n for the Maximum Allocation with Reservation (MAR) Bandwidth\n Constraints Model. Assumptions, applicability, and examples of the\n operation of the MAR Bandwidth Constraints Model are presented. MAR\n performance is analyzed relative to the criteria for selecting a\n Bandwidth Constraints Model, in order to provide guidance to user\n implementation of the model in their networks. 4126 key path nested-reference unchanged"},{"id":"IETF RFC 4127","type":"specification","body":"IETF","designation":"RFC 4127","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4127.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4127.txt","https://www.rfc-editor.org/rfc/rfc4127.pdf"],"folder":"IETF/RFC-4127","files":{"txt":{"path":"standards/IETF/RFC-4127/RFC-4127.txt","sha256":"b2b41a5430a1b1cfbde1001de6e675bb26b84866e8c0bcd9bdc9a3eb215ec0bf"}},"tags":["nested-reference","unchanged"],"summary":"This document provides specifications for one Bandwidth Constraints\n Model for Diffserv-aware MPLS Traffic Engineering, which is referred\n to as the Russian Dolls Model.","scope_keywords":["4127","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4124","folder":"IETF/RFC-4124","source":"IETF/RFC-4124/RFC-4124.txt","version":null},{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 4127 This document provides specifications for one Bandwidth Constraints\n Model for Diffserv-aware MPLS Traffic Engineering, which is referred\n to as the Russian Dolls Model. 4127 key nested-reference unchanged"},{"id":"IETF RFC 4128","type":"specification","body":"IETF","designation":"RFC 4128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4128.txt","https://www.rfc-editor.org/rfc/rfc4128.pdf"],"folder":"IETF/RFC-4128","files":{"pdf":{"path":"standards/IETF/RFC-4128/RFC-4128.pdf","sha256":"9629f0d8d37931e6cc76a0a11a04a31624b6c8fdf79df3f67f0edaf9607b23a5"},"txt":{"path":"standards/IETF/RFC-4128/RFC-4128.txt","sha256":"be6bfb26c0fbac1771de8332039d3d379ef8e854e56d2778f11e79fb3a17278a"}},"tags":["nested-reference","unchanged"],"summary":"\"Differentiated Services (Diffserv)-aware MPLS Traffic Engineering\n Requirements\", RFC 3564, specifies the requirements and selection\n criteria for Bandwidth Constraints Models. Two such models, the\n Maximum Allocation and the Russian Dolls, are described therein.\n This document complements RFC 3564 by presenting the results of a\n performance evaluation of these two models under various operational\n conditions: normal load, overload, preemption fully or partially\n enabled, pure blocking, or complete sharing.\n\nLai Standards Track [Page 1]\n\f\nRFC 4128 BC Models for Diffserv-aware MPLS TE June 2005","scope_keywords":["4128","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4125","folder":"IETF/RFC-4125","source":"IETF/RFC-4125/RFC-4125.txt","version":null},{"body":"IETF","designation":"RFC 4126","folder":"IETF/RFC-4126","source":"IETF/RFC-4126/RFC-4126.txt","version":null},{"body":"IETF","designation":"RFC 4127","folder":"IETF/RFC-4127","source":"IETF/RFC-4127/RFC-4127.txt","version":null}],"search_text":"IETF RFC 4128 \"Differentiated Services (Diffserv)-aware MPLS Traffic Engineering\n Requirements\", RFC 3564, specifies the requirements and selection\n criteria for Bandwidth Constraints Models. Two such models, the\n Maximum Allocation and the Russian Dolls, are described therein.\n This document complements RFC 3564 by presenting the results of a\n performance evaluation of these two models under various operational\n conditions: normal load, overload, preemption fully or partially\n enabled, pure blocking, or complete sharing.\n\nLai Standards Track [Page 1]\n\f\nRFC 4128 BC Models for Diffserv-aware MPLS TE June 2005 4128 key nested-reference unchanged"},{"id":"IETF RFC 4132","type":"specification","body":"IETF","designation":"RFC 4132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4132.txt","https://www.rfc-editor.org/rfc/rfc4132.pdf"],"folder":"IETF/RFC-4132","files":{"txt":{"path":"standards/IETF/RFC-4132/RFC-4132.txt","sha256":"f358aaaa5040019f921cadf72a39f59b0c47823943a69ab49d355823dd03c0e5"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes the addition of new cipher suites to the\n Transport Layer Security (TLS) protocol to support the Camellia\n encryption algorithm as a bulk cipher algorithm.\n\n1. Introduction\n\n This document proposes the addition of new cipher suites to the TLS\n protocol [TLS] to support the Camellia encryption algorithm as a bulk\n cipher algorithm. This proposal provides a new option for fast and\n efficient bulk cipher algorithms.\n\n Note: This work was done when the first author worked for NTT.","scope_keywords":["4132","algorithm","algorithms","authentication","certificate","delivery","encryption","hash","http","key","keys","management","signature","signatures","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5932","folder":"IETF/RFC-5932","source":"IETF/RFC-5932/RFC-5932.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4132 This document proposes the addition of new cipher suites to the\n Transport Layer Security (TLS) protocol to support the Camellia\n encryption algorithm as a bulk cipher algorithm.\n\n1. Introduction\n\n This document proposes the addition of new cipher suites to the TLS\n protocol [TLS] to support the Camellia encryption algorithm as a bulk\n cipher algorithm. This proposal provides a new option for fast and\n efficient bulk cipher algorithms.\n\n Note: This work was done when the first author worked for NTT. 4132 algorithm algorithms authentication certificate delivery encryption hash http key keys management signature signatures tls nested-reference unchanged"},{"id":"IETF RFC 4139","type":"specification","body":"IETF","designation":"RFC 4139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4139.txt","https://www.rfc-editor.org/rfc/rfc4139.pdf"],"folder":"IETF/RFC-4139","files":{"txt":{"path":"standards/IETF/RFC-4139/RFC-4139.txt","sha256":"eebb14b64da4a61f0481ddc8c041e92e3ac6494ccf78209566eae743a082972c"}},"tags":["nested-reference","unchanged"],"summary":"The Generalized Multi-Protocol Label Switching (GMPLS) suite of\n protocols has been defined to control different switching\n technologies and different applications. These include support for\n requesting Time Division Multiplexing (TDM) connections, including\n Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy\n (SDH) and Optical Transport Networks (OTNs).\n\n This document concentrates on the signaling aspects of the GMPLS\n suite of protocols. It identifies the features to be covered by the\n GMPLS signaling protocol to support the capabilities of an\n Automatically Switched Optical Network (ASON). This document\n provides a problem statement and additional requirements for the\n GMPLS signaling protocol to support the ASON functionality.\n\nPapadimitriou, et al. Informational [Page 1]\n\f\nRFC 4139 GMPLS Signaling Usage and Extensions for ASON July 2005\n\n1. Introduction\n\n The General","scope_keywords":["4139","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null}],"search_text":"IETF RFC 4139 The Generalized Multi-Protocol Label Switching (GMPLS) suite of\n protocols has been defined to control different switching\n technologies and different applications. These include support for\n requesting Time Division Multiplexing (TDM) connections, including\n Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy\n (SDH) and Optical Transport Networks (OTNs).\n\n This document concentrates on the signaling aspects of the GMPLS\n suite of protocols. It identifies the features to be covered by the\n GMPLS signaling protocol to support the capabilities of an\n Automatically Switched Optical Network (ASON). This document\n provides a problem statement and additional requirements for the\n GMPLS signaling protocol to support the ASON functionality.\n\nPapadimitriou, et al. Informational [Page 1]\n\f\nRFC 4139 GMPLS Signaling Usage and Extensions for ASON July 2005\n\n1. Introduction\n\n The General 4139 key management nested-reference unchanged"},{"id":"IETF RFC 4140","type":"specification","body":"IETF","designation":"RFC 4140","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4140.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4140.txt","https://www.rfc-editor.org/rfc/rfc4140.pdf"],"folder":"IETF/RFC-4140","files":{"txt":{"path":"standards/IETF/RFC-4140/RFC-4140.txt","sha256":"aaade1ab5e7bf78e454de4d999f7fe9dde555cb74c8a9c2c8c9bef3847efa4dc"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces extensions to Mobile IPv6 and IPv6 Neighbour\n Discovery to allow for local mobility handling. Hierarchical\n mobility management for Mobile IPv6 is designed to reduce the amount\n of signalling between the Mobile Node, its Correspondent Nodes, and\n its Home Agent. The Mobility Anchor Point (MAP) described in this\n document can also be used to improve the performance of Mobile IPv6\n in terms of handover speed.\n\nSoliman, et al. Experimental [Page 1]\n\f\nRFC 4140 HMIPv6 August 2005","scope_keywords":["4140","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4977","folder":"IETF/RFC-4977","source":"IETF/RFC-4977/RFC-4977.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null}],"search_text":"IETF RFC 4140 This document introduces extensions to Mobile IPv6 and IPv6 Neighbour\n Discovery to allow for local mobility handling. Hierarchical\n mobility management for Mobile IPv6 is designed to reduce the amount\n of signalling between the Mobile Node, its Correspondent Nodes, and\n its Home Agent. The Mobility Anchor Point (MAP) described in this\n document can also be used to improve the performance of Mobile IPv6\n in terms of handover speed.\n\nSoliman, et al. Experimental [Page 1]\n\f\nRFC 4140 HMIPv6 August 2005 4140 key management nested-reference unchanged"},{"id":"IETF RFC 4142","type":"specification","body":"IETF","designation":"RFC 4142","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4142.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4142.txt","https://www.rfc-editor.org/rfc/rfc4142.pdf"],"folder":"IETF/RFC-4142","files":{"txt":{"path":"standards/IETF/RFC-4142/RFC-4142.txt","sha256":"c59a6ce880606a7df1d905b6e157115890b5b6810d37c3a1efcd55e3e38607d2"}},"tags":["nested-reference","unchanged"],"summary":"Classic facsimile document exchange represents both a set of\n technical specifications and a class of service. Previous work has\n replicated some of that service class as a profile within Internet\n mail. The current specification defines \"full mode\" carriage of\n facsimile data over the Internet, building upon that previous work\n and adding the remaining functionality necessary for achieving\n reliability and capability negotiation for Internet mail, on a par\n with classic T.30 facsimile. These additional features are designed\n to provide the highest level of interoperability with the\n standards-compliant email infrastructure and mail user agents, while\n providing a level of service that approximates what is currently\n enjoyed by fax users.\n\nCrocker & Klyne Standards Track [Page 1]\n\f\nRFC 4142 FFPIM November 2005","scope_keywords":["4142","delivery","key","path","profile","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4143","folder":"IETF/RFC-4143","source":"IETF/RFC-4143/RFC-4143.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null}],"search_text":"IETF RFC 4142 Classic facsimile document exchange represents both a set of\n technical specifications and a class of service. Previous work has\n replicated some of that service class as a profile within Internet\n mail. The current specification defines \"full mode\" carriage of\n facsimile data over the Internet, building upon that previous work\n and adding the remaining functionality necessary for achieving\n reliability and capability negotiation for Internet mail, on a par\n with classic T.30 facsimile. These additional features are designed\n to provide the highest level of interoperability with the\n standards-compliant email infrastructure and mail user agents, while\n providing a level of service that approximates what is currently\n enjoyed by fax users.\n\nCrocker & Klyne Standards Track [Page 1]\n\f\nRFC 4142 FFPIM November 2005 4142 delivery key path profile risk nested-reference unchanged"},{"id":"IETF RFC 4143","type":"specification","body":"IETF","designation":"RFC 4143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4143.txt","https://www.rfc-editor.org/rfc/rfc4143.pdf"],"folder":"IETF/RFC-4143","files":{"txt":{"path":"standards/IETF/RFC-4143/RFC-4143.txt","sha256":"387e51fc6b11a59f2c2c83e3aa02d318850daa295a8fea9ff456c5ca4d5befbb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the functional specification and definition\n of the ENUM Naming Authority Pointer (NAPTR) record for IFax service.\n IFax is \"facsimile using Internet mail\". For this use, the Domain\n Name System (DNS) returns the email address of the referenced IFax\n system. This mechanism allows email-based fax communication to use\n telephone numbers instead of requiring the sender to already know the\n recipient email address.\n\n1. Functional Specification\n\n An IFax client makes a [ENUMbis] DNS query, using the target system's\n telephone number. The returned NAPTR record specifies an email\n address to be used for reaching the target system. The email address\n is then used in accordance with Simple Mode of Facsimile using\n Internet Mail [RFC3965], Extended Facsimile using Internet Mail\n [RFC2532], or Full Mode Fax Profile for Internet Mail [FFPIM] is\n applied.\n\n The key words \"MUST","scope_keywords":["4143","key","license","profile","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4143 This document describes the functional specification and definition\n of the ENUM Naming Authority Pointer (NAPTR) record for IFax service.\n IFax is \"facsimile using Internet mail\". For this use, the Domain\n Name System (DNS) returns the email address of the referenced IFax\n system. This mechanism allows email-based fax communication to use\n telephone numbers instead of requiring the sender to already know the\n recipient email address.\n\n1. Functional Specification\n\n An IFax client makes a [ENUMbis] DNS query, using the target system's\n telephone number. The returned NAPTR record specifies an email\n address to be used for reaching the target system. The email address\n is then used in accordance with Simple Mode of Facsimile using\n Internet Mail [RFC3965], Extended Facsimile using Internet Mail\n [RFC2532], or Full Mode Fax Profile for Internet Mail [FFPIM] is\n applied.\n\n The key words \"MUST 4143 key license profile subject nested-reference unchanged"},{"id":"IETF RFC 4162","type":"specification","body":"IETF","designation":"RFC 4162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4162.txt","https://www.rfc-editor.org/rfc/rfc4162.pdf"],"folder":"IETF/RFC-4162","files":{"txt":{"path":"standards/IETF/RFC-4162/RFC-4162.txt","sha256":"ae3456638cacf62adc60577867f3f13b0c33ecb02d70ac7ca83ccaa209b1b67e"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes the addition of new cipher suites to the\n Transport Layer Security (TLS) protocol to support the SEED\n encryption algorithm as a bulk cipher algorithm.\n\n1. Introduction\n\n This document proposes the addition of new cipher suites to the TLS\n protocol [TLS] to support the SEED encryption algorithm as a bulk\n cipher algorithm.","scope_keywords":["4162","algorithm","algorithms","certificate","encryption","hash","http","key","keys","pki","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4162 This document proposes the addition of new cipher suites to the\n Transport Layer Security (TLS) protocol to support the SEED\n encryption algorithm as a bulk cipher algorithm.\n\n1. Introduction\n\n This document proposes the addition of new cipher suites to the TLS\n protocol [TLS] to support the SEED encryption algorithm as a bulk\n cipher algorithm. 4162 algorithm algorithms certificate encryption hash http key keys pki tls trust nested-reference unchanged"},{"id":"IETF RFC 4164","type":"specification","body":"IETF","designation":"RFC 4164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4164.txt","https://www.rfc-editor.org/rfc/rfc4164.pdf"],"folder":"IETF/RFC-4164","files":{"txt":{"path":"standards/IETF/RFC-4164/RFC-4164.txt","sha256":"9d755c5341166d63beb3ea4862943e952905971e6eaee95230ea9cbce86185cd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines context replication, a complement to the\n context initialization procedure found in Robust Header Compression\n (ROHC), as specified in RFC 3095. Profiles defining support for\n context replication may use the mechanism described herein to\n establish a new context based on another already existing context.\n Context replication is introduced to reduce the overhead of the\n context establishment procedure. It may be especially useful for the\n compression of multiple short-lived flows that may be occurring\n simultaneously or near-simultaneously, such as short-lived TCP flows.\n\nPelletier Standards Track [Page 1]\n\f\nRFC 4164 Context Replication for ROHC Profiles August 2005","scope_keywords":["4164","key","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 4164 This document defines context replication, a complement to the\n context initialization procedure found in Robust Header Compression\n (ROHC), as specified in RFC 3095. Profiles defining support for\n context replication may use the mechanism described herein to\n establish a new context based on another already existing context.\n Context replication is introduced to reduce the overhead of the\n context establishment procedure. It may be especially useful for the\n compression of multiple short-lived flows that may be occurring\n simultaneously or near-simultaneously, such as short-lived TCP flows.\n\nPelletier Standards Track [Page 1]\n\f\nRFC 4164 Context Replication for ROHC Profiles August 2005 4164 key profile profiles nested-reference unchanged"},{"id":"IETF RFC 4168","type":"specification","body":"IETF","designation":"RFC 4168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4168.txt","https://www.rfc-editor.org/rfc/rfc4168.pdf"],"folder":"IETF/RFC-4168","files":{"txt":{"path":"standards/IETF/RFC-4168/RFC-4168.txt","sha256":"c11bde16eba71e93d78255027b7254936ed21695f6ae6957655b63d10cc0e330"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism for usage of SCTP (the Stream\n Control Transmission Protocol) as the transport mechanism between SIP\n (Session Initiation Protocol) entities. SCTP is a new protocol that\n provides several features that may prove beneficial for transport\n between SIP entities that exchange a large amount of messages,\n including gateways and proxies. As SIP is transport-independent,\n support of SCTP is a relatively straightforward process, nearly\n identical to support for TCP.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 4168 SCTP as a Transport for SIP October 2005","scope_keywords":["4168","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4168 This document specifies a mechanism for usage of SCTP (the Stream\n Control Transmission Protocol) as the transport mechanism between SIP\n (Session Initiation Protocol) entities. SCTP is a new protocol that\n provides several features that may prove beneficial for transport\n between SIP entities that exchange a large amount of messages,\n including gateways and proxies. As SIP is transport-independent,\n support of SCTP is a relatively straightforward process, nearly\n identical to support for TCP.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 4168 SCTP as a Transport for SIP October 2005 4168 delivery key nested-reference unchanged"},{"id":"IETF RFC 4174","type":"specification","body":"IETF","designation":"RFC 4174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4174.txt","https://www.rfc-editor.org/rfc/rfc4174.pdf"],"folder":"IETF/RFC-4174","files":{"txt":{"path":"standards/IETF/RFC-4174/RFC-4174.txt","sha256":"db3ef6dc44e52f4a5cddd91f4d3905341d1ffb8e985a1137684a723ce66880fe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Dynamic Host Configuration Protocol\n (DHCP) option to allow Internet Storage Name Service (iSNS) clients\n to discover the location of the iSNS server automatically through the\n use of DHCP for IPv4. iSNS provides discovery and management\n capabilities for Internet SCSI (iSCSI) and Internet Fibre Channel\n Protocol (iFCP) storage devices in an enterprise-scale IP storage\n network. iSNS provides intelligent storage management services\n comparable to those found in Fibre Channel networks, allowing a\n commodity IP network to function in a similar capacity to that of a\n storage area network.","scope_keywords":["4174","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4174 This document describes the Dynamic Host Configuration Protocol\n (DHCP) option to allow Internet Storage Name Service (iSNS) clients\n to discover the location of the iSNS server automatically through the\n use of DHCP for IPv4. iSNS provides discovery and management\n capabilities for Internet SCSI (iSCSI) and Internet Fibre Channel\n Protocol (iFCP) storage devices in an enterprise-scale IP storage\n network. iSNS provides intelligent storage management services\n comparable to those found in Fibre Channel networks, allowing a\n commodity IP network to function in a similar capacity to that of a\n storage area network. 4174 key management registered nested-reference unchanged"},{"id":"IETF RFC 4178","type":"specification","body":"IETF","designation":"RFC 4178","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4178.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4178.txt","https://www.rfc-editor.org/rfc/rfc4178.pdf"],"folder":"IETF/RFC-4178","files":{"txt":{"path":"standards/IETF/RFC-4178/RFC-4178.txt","sha256":"c6fda3258d782c661363cef51135fa544a804b39d16a1d54b5284490a1f13bea"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a negotiation mechanism for the Generic\n Security Service Application Program Interface (GSS-API), which is\n described in RFC 2743. GSS-API peers can use this negotiation\n mechanism to choose from a common set of security mechanisms. If\n per-message integrity services are available on the established\n mechanism context, then the negotiation is protected against an\n attacker that forces the selection of a mechanism not desired by the\n peers.\n\n This mechanism replaces RFC 2478 in order to fix defects in that\n specification and to describe how to inter-operate with\n implementations of that specification that are commonly deployed on\n the Internet.\n\nZhu, et al. Standards Track [Page 1]\n\f\nRFC 4178 The GSS-API Negotiation Mechanism October 2005","scope_keywords":["4178","credential","credentials","key","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4559","folder":"IETF/RFC-4559","source":"IETF/RFC-4559/RFC-4559.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 4178 This document specifies a negotiation mechanism for the Generic\n Security Service Application Program Interface (GSS-API), which is\n described in RFC 2743. GSS-API peers can use this negotiation\n mechanism to choose from a common set of security mechanisms. If\n per-message integrity services are available on the established\n mechanism context, then the negotiation is protected against an\n attacker that forces the selection of a mechanism not desired by the\n peers.\n\n This mechanism replaces RFC 2478 in order to fix defects in that\n specification and to describe how to inter-operate with\n implementations of that specification that are commonly deployed on\n the Internet.\n\nZhu, et al. Standards Track [Page 1]\n\f\nRFC 4178 The GSS-API Negotiation Mechanism October 2005 4178 credential credentials key policy subject nested-reference unchanged"},{"id":"IETF RFC 4184","type":"specification","body":"IETF","designation":"RFC 4184","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4184.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4184.txt","https://www.rfc-editor.org/rfc/rfc4184.pdf"],"folder":"IETF/RFC-4184","files":{"txt":{"path":"standards/IETF/RFC-4184/RFC-4184.txt","sha256":"e2584bebe221ab7370b268d9aa8ec32e83bfa8aacb6c04e9da7b854f9d14112c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an RTP payload format for transporting audio\n data using the AC-3 audio compression standard. AC-3 is a high\n quality, multichannel audio coding system that is used for United\n States HDTV, DVD, cable television, satellite television and other\n media. The RTP payload format presented in this document includes\n support for data fragmentation.\n\n1. Introduction\n\n AC-3 [ATSC] is a high-quality audio codec (audio coding format)\n designed to encode multiple channels of audio into a low bit-rate\n format. AC-3 achieves its large compression ratios via encoding a\n multiplicity of channels as a single entity. Dolby Digital, which is\n a branded version of AC-3, encodes up to 5.1 channels of audio.\n\n AC-3 has been adopted as an audio compression scheme for many\n consumer and professional applications. It is a mandatory audio\n codec for DVD-video, Advanced Television Standards","scope_keywords":["4184","algorithm","key","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4598","folder":"IETF/RFC-4598","source":"IETF/RFC-4598/RFC-4598.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"IETF RFC 4184 This document describes an RTP payload format for transporting audio\n data using the AC-3 audio compression standard. AC-3 is a high\n quality, multichannel audio coding system that is used for United\n States HDTV, DVD, cable television, satellite television and other\n media. The RTP payload format presented in this document includes\n support for data fragmentation.\n\n1. Introduction\n\n AC-3 [ATSC] is a high-quality audio codec (audio coding format)\n designed to encode multiple channels of audio into a low bit-rate\n format. AC-3 achieves its large compression ratios via encoding a\n multiplicity of channels as a single entity. Dolby Digital, which is\n a branded version of AC-3, encodes up to 5.1 channels of audio.\n\n AC-3 has been adopted as an audio compression scheme for many\n consumer and professional applications. It is a mandatory audio\n codec for DVD-video, Advanced Television Standards 4184 algorithm key profile timestamp nested-reference unchanged"},{"id":"IETF RFC 4189","type":"specification","body":"IETF","designation":"RFC 4189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4189.txt","https://www.rfc-editor.org/rfc/rfc4189.pdf"],"folder":"IETF/RFC-4189","files":{"txt":{"path":"standards/IETF/RFC-4189/RFC-4189.txt","sha256":"a9d7b286a72d091dfefc17d7f3d29d5b7dd62e78a2d64b8440cdaea8336057ec"}},"tags":["nested-reference","unchanged"],"summary":"A Session Initiation Protocol (SIP) User Agent (UA) does not always\n trust all intermediaries in its request path to inspect its message\n bodies and/or headers contained in its message. The UA might want to\n protect the message bodies and/or headers from intermediaries, except\n those that provide services based on its content. This situation\n requires a mechanism called \"end-to-middle security\" to secure the\n information passed between the UA and intermediaries, which does not\n interfere with end-to-end security. This document defines a set of\n requirements for a mechanism to achieve end-to-middle security.","scope_keywords":["4189","key","path","policies","policy","tls","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null}],"search_text":"IETF RFC 4189 A Session Initiation Protocol (SIP) User Agent (UA) does not always\n trust all intermediaries in its request path to inspect its message\n bodies and/or headers contained in its message. The UA might want to\n protect the message bodies and/or headers from intermediaries, except\n those that provide services based on its content. This situation\n requires a mechanism called \"end-to-middle security\" to secure the\n information passed between the UA and intermediaries, which does not\n interfere with end-to-end security. This document defines a set of\n requirements for a mechanism to achieve end-to-middle security. 4189 key path policies policy tls trust tsp nested-reference unchanged"},{"id":"IETF RFC 4196","type":"specification","body":"IETF","designation":"RFC 4196","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4196.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4196.txt","https://www.rfc-editor.org/rfc/rfc4196.pdf"],"folder":"IETF/RFC-4196","files":{"txt":{"path":"standards/IETF/RFC-4196/RFC-4196.txt","sha256":"fcd316975dc1abe1c9fdcfc48d0d29f9caca5858075ef4882a99d40abbd97d9a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the SEED block cipher algorithm in\n the Cipher Block Chaining Mode, with an explicit IV, as a\n confidentiality mechanism within the context of the IPsec\n Encapsulating Security Payload (ESP).\n\n1. Introduction","scope_keywords":["4196","algorithm","algorithms","encryption","http","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4196 This document describes the use of the SEED block cipher algorithm in\n the Cipher Block Chaining Mode, with an explicit IV, as a\n confidentiality mechanism within the context of the IPsec\n Encapsulating Security Payload (ESP).\n\n1. Introduction 4196 algorithm algorithms encryption http key keys nested-reference unchanged"},{"id":"IETF RFC 4198","type":"specification","body":"IETF","designation":"RFC 4198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4198.txt","https://www.rfc-editor.org/rfc/rfc4198.pdf"],"folder":"IETF/RFC-4198","files":{"txt":{"path":"standards/IETF/RFC-4198/RFC-4198.txt","sha256":"897cf2fcf6203e2092d0ac0c3f17b7cd343a5ad40d6fc905907adcc4b6d1e99b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Tessman\nRequest for Comments: 4198 Zelestra\nCategory: Informational November 2005\n\n A Uniform Resource Name (URN) Namespace for Federated Content\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace for\n identifying content resources within federated content collections.\n A federated content collection often does not have a strong\n centralized authority but relies upon shared naming, metadata, and\n access conventions to provide interoperability among its members.\n\n1. Introduction\n\n Federated content collections are often loose constructs of both\n small and large content providers, with an active communit","scope_keywords":["4198","http","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 4198 Network Working Group D. Tessman\nRequest for Comments: 4198 Zelestra\nCategory: Informational November 2005\n\n A Uniform Resource Name (URN) Namespace for Federated Content\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace for\n identifying content resources within federated content collections.\n A federated content collection often does not have a strong\n centralized authority but relies upon shared naming, metadata, and\n access conventions to provide interoperability among its members.\n\n1. Introduction\n\n Federated content collections are often loose constructs of both\n small and large content providers, with an active communit 4198 http key validation nested-reference unchanged"},{"id":"IETF RFC 4201","type":"specification","body":"IETF","designation":"RFC 4201","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4201.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4201.txt","https://www.rfc-editor.org/rfc/rfc4201.pdf"],"folder":"IETF/RFC-4201","files":{"txt":{"path":"standards/IETF/RFC-4201/RFC-4201.txt","sha256":"90c15a7ea17274c31ea42991428cd91e8fb988965237842376f3c304d89b9b1d"}},"tags":["nested-reference","unchanged"],"summary":"For the purpose of Generalized Multi-Protocol Label Switching (GMPLS)\n signaling, in certain cases a combination of <link identifier, label>\n is not sufficient to unambiguously identify the appropriate resource\n used by a Label Switched Path (LSP). Such cases are handled by using\n the link bundling construct, which is described in this document.\n This document updates the interface identification TLVs, which are\n defined in the GMPLS Signaling Functional Description.\n\nKompella, et al. Standards Track [Page 1]\n\f\nRFC 4201 Link Bundling in MPLS-TE October 2005","scope_keywords":["4201","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4201 For the purpose of Generalized Multi-Protocol Label Switching (GMPLS)\n signaling, in certain cases a combination of <link identifier, label>\n is not sufficient to unambiguously identify the appropriate resource\n used by a Label Switched Path (LSP). Such cases are handled by using\n the link bundling construct, which is described in this document.\n This document updates the interface identification TLVs, which are\n defined in the GMPLS Signaling Functional Description.\n\nKompella, et al. Standards Track [Page 1]\n\f\nRFC 4201 Link Bundling in MPLS-TE October 2005 4201 identification key path nested-reference unchanged"},{"id":"IETF RFC 4202","type":"specification","body":"IETF","designation":"RFC 4202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4202.txt","https://www.rfc-editor.org/rfc/rfc4202.pdf"],"folder":"IETF/RFC-4202","files":{"txt":{"path":"standards/IETF/RFC-4202/RFC-4202.txt","sha256":"cc5e2aea083bfea3a8468176e1bf9fe20ef5fd2e48736bb37d338e17437ca90a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies routing extensions in support of carrying\n link state information for Generalized Multi-Protocol Label Switching\n (GMPLS). This document enhances the routing extensions required to\n support MPLS Traffic Engineering (TE).\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4202 Routing Extensions for GMPLS October 2005","scope_keywords":["4202","attribute","attributes","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4203","folder":"IETF/RFC-4203","source":"IETF/RFC-4203/RFC-4203.txt","version":null},{"body":"IETF","designation":"RFC 4204","folder":"IETF/RFC-4204","source":"IETF/RFC-4204/RFC-4204.txt","version":null},{"body":"IETF","designation":"RFC 4205","folder":"IETF/RFC-4205","source":"IETF/RFC-4205/RFC-4205.txt","version":null},{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5307","folder":"IETF/RFC-5307","source":"IETF/RFC-5307/RFC-5307.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 4202 This document specifies routing extensions in support of carrying\n link state information for Generalized Multi-Protocol Label Switching\n (GMPLS). This document enhances the routing extensions required to\n support MPLS Traffic Engineering (TE).\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4202 Routing Extensions for GMPLS October 2005 4202 attribute attributes path risk nested-reference unchanged"},{"id":"IETF RFC 4203","type":"specification","body":"IETF","designation":"RFC 4203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4203.txt","https://www.rfc-editor.org/rfc/rfc4203.pdf"],"folder":"IETF/RFC-4203","files":{"txt":{"path":"standards/IETF/RFC-4203/RFC-4203.txt","sha256":"cd69dd252a8c2c80d0cf0f3d36311defb773fdda4ddffc472f4caf52e1b83e88"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies encoding of extensions to the OSPF routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\n1. Introduction\n\n This document specifies extensions to the OSPF routing protocol\n [OSPF] in support of carrying link state information for Generalized\n Multi-Protocol Label Switching (GMPLS). The set of required\n enhancements to OSPF are outlined in [GMPLS-ROUTING].\n\n In this section, we define the enhancements to the Traffic\n Engineering (TE) properties of GMPLS TE links that can be announced\n in OSPF TE LSAs. The TE LSA, which is an opaque LSA with area\n flooding scope [OSPF-TE], has only one top-level Type/Length/Value\n (TLV) triplet and has one or more nested sub-TLVs for extensibility.\n The top-level TLV can take one of two values (1) Router Address or\n (2) Link. In this document, we enhance the sub-TLVs for the Link TLV\n in support of GMP","scope_keywords":["4203","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5329","folder":"IETF/RFC-5329","source":"IETF/RFC-5329/RFC-5329.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 4203 This document specifies encoding of extensions to the OSPF routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\n1. Introduction\n\n This document specifies extensions to the OSPF routing protocol\n [OSPF] in support of carrying link state information for Generalized\n Multi-Protocol Label Switching (GMPLS). The set of required\n enhancements to OSPF are outlined in [GMPLS-ROUTING].\n\n In this section, we define the enhancements to the Traffic\n Engineering (TE) properties of GMPLS TE links that can be announced\n in OSPF TE LSAs. The TE LSA, which is an opaque LSA with area\n flooding scope [OSPF-TE], has only one top-level Type/Length/Value\n (TLV) triplet and has one or more nested sub-TLVs for extensibility.\n The top-level TLV can take one of two values (1) Router Address or\n (2) Link. In this document, we enhance the sub-TLVs for the Link TLV\n in support of GMP 4203 key risk nested-reference unchanged"},{"id":"IETF RFC 4204","type":"specification","body":"IETF","designation":"RFC 4204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4204.txt","https://www.rfc-editor.org/rfc/rfc4204.pdf"],"folder":"IETF/RFC-4204","files":{"txt":{"path":"standards/IETF/RFC-4204/RFC-4204.txt","sha256":"20d048b8cef90b206c0dcb6ac046091e6f732c0227aa98e8c1904c78f1c78f70"}},"tags":["nested-reference","unchanged"],"summary":"For scalability purposes, multiple data links can be combined to form\n a single traffic engineering (TE) link. Furthermore, the management\n of TE links is not restricted to in-band messaging, but instead can\n be done using out-of-band techniques. This document specifies a link\n management protocol (LMP) that runs between a pair of nodes and is\n used to manage TE links. Specifically, LMP will be used to maintain\n control channel connectivity, verify the physical connectivity of the\n data links, correlate the link property information, suppress\n downstream alarms, and localize link failures for\n protection/restoration purposes in multiple kinds of networks.","scope_keywords":["4204","algorithm","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4209","folder":"IETF/RFC-4209","source":"IETF/RFC-4209/RFC-4209.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4204 For scalability purposes, multiple data links can be combined to form\n a single traffic engineering (TE) link. Furthermore, the management\n of TE links is not restricted to in-band messaging, but instead can\n be done using out-of-band techniques. This document specifies a link\n management protocol (LMP) that runs between a pair of nodes and is\n used to manage TE links. Specifically, LMP will be used to maintain\n control channel connectivity, verify the physical connectivity of the\n data links, correlate the link property information, suppress\n downstream alarms, and localize link failures for\n protection/restoration purposes in multiple kinds of networks. 4204 algorithm management nested-reference unchanged"},{"id":"IETF RFC 4205","type":"specification","body":"IETF","designation":"RFC 4205","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4205.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4205.txt","https://www.rfc-editor.org/rfc/rfc4205.pdf"],"folder":"IETF/RFC-4205","files":{"txt":{"path":"standards/IETF/RFC-4205/RFC-4205.txt","sha256":"cd7d5e641ec50e526b3ec984a7458d53580f8a54e1e804e33651781f0dd640aa"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies encoding of extensions to the IS-IS routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\n1. Introduction\n\n This document specifies extensions to the IS-IS routing protocol in\n support of carrying link state information for Generalized Multi-\n Protocol Label Switching (GMPLS). The set of required enhancements\n to IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered\n interfaces assumes support for the \"Point-to-Point Three-Way\n Adjacency\" IS-IS Option type [ISIS-3way].\n\n In this section we define the enhancements to the Traffic Engineering\n (TE) properties of GMPLS TE links that can be announced in IS-IS Link\n State Protocol Data Units.\n\n In this document, we enhance the sub-TLVs for the extended IS\n reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically,\n we add the following sub-TLVs:\n\n Sub-TLV Type Length Name","scope_keywords":["4205","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4201","folder":"IETF/RFC-4201","source":"IETF/RFC-4201/RFC-4201.txt","version":null},{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4206","folder":"IETF/RFC-4206","source":"IETF/RFC-4206/RFC-4206.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null}],"search_text":"IETF RFC 4205 This document specifies encoding of extensions to the IS-IS routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\n1. Introduction\n\n This document specifies extensions to the IS-IS routing protocol in\n support of carrying link state information for Generalized Multi-\n Protocol Label Switching (GMPLS). The set of required enhancements\n to IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered\n interfaces assumes support for the \"Point-to-Point Three-Way\n Adjacency\" IS-IS Option type [ISIS-3way].\n\n In this section we define the enhancements to the Traffic Engineering\n (TE) properties of GMPLS TE links that can be announced in IS-IS Link\n State Protocol Data Units.\n\n In this document, we enhance the sub-TLVs for the extended IS\n reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically,\n we add the following sub-TLVs:\n\n Sub-TLV Type Length Name 4205 key risk nested-reference unchanged"},{"id":"IETF RFC 4206","type":"specification","body":"IETF","designation":"RFC 4206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4206.txt","https://www.rfc-editor.org/rfc/rfc4206.pdf"],"folder":"IETF/RFC-4206","files":{"txt":{"path":"standards/IETF/RFC-4206/RFC-4206.txt","sha256":"83c71760921316e1c6b3e363ba62b16802d86f838996cf12fec42a70681ec853"}},"tags":["nested-reference","unchanged"],"summary":"To improve scalability of Generalized Multi-Protocol Label Switching\n (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by\n creating a hierarchy of such LSPs. A way to create such a hierarchy\n is by (a) a Label Switching Router (LSR) creating a Traffic\n Engineering Label Switched Path (TE LSP), (b) the LSR forming a\n forwarding adjacency (FA) out of that LSP (by advertising this LSP as\n a Traffic Engineering (TE) link into the same instance of ISIS/OSPF\n as the one that was used to create the LSP), (c) allowing other LSRs\n to use FAs for their path computation, and (d) nesting of LSPs\n originated by other LSRs into that LSP (by using the label stack\n construct).\n\n This document describes the mechanisms to accomplish this.\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4206 LSP Hierarchy with GMPLS TE October 2005","scope_keywords":["4206","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4202","folder":"IETF/RFC-4202","source":"IETF/RFC-4202/RFC-4202.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4208","folder":"IETF/RFC-4208","source":"IETF/RFC-4208/RFC-4208.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4220","folder":"IETF/RFC-4220","source":"IETF/RFC-4220/RFC-4220.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4420","folder":"IETF/RFC-4420","source":"IETF/RFC-4420/RFC-4420.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4206 To improve scalability of Generalized Multi-Protocol Label Switching\n (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by\n creating a hierarchy of such LSPs. A way to create such a hierarchy\n is by (a) a Label Switching Router (LSR) creating a Traffic\n Engineering Label Switched Path (TE LSP), (b) the LSR forming a\n forwarding adjacency (FA) out of that LSP (by advertising this LSP as\n a Traffic Engineering (TE) link into the same instance of ISIS/OSPF\n as the one that was used to create the LSP), (c) allowing other LSRs\n to use FAs for their path computation, and (d) nesting of LSPs\n originated by other LSRs into that LSP (by using the label stack\n construct).\n\n This document describes the mechanisms to accomplish this.\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4206 LSP Hierarchy with GMPLS TE October 2005 4206 key path nested-reference unchanged"},{"id":"IETF RFC 4208","type":"specification","body":"IETF","designation":"RFC 4208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4208.txt","https://www.rfc-editor.org/rfc/rfc4208.pdf"],"folder":"IETF/RFC-4208","files":{"txt":{"path":"standards/IETF/RFC-4208/RFC-4208.txt","sha256":"bd9d83e55f2bafbf8fffce5bf23132df6b1e58af8a477c583ed4601ac90f1738"}},"tags":["nested-reference","unchanged"],"summary":"Generalized Multiprotocol Label Switching (GMPLS) defines both\n routing and signaling protocols for the creation of Label Switched\n Paths (LSPs) in various switching technologies. These protocols can\n be used to support a number of deployment scenarios. This memo\n addresses the application of GMPLS to the overlay model.\n\nSwallow, et al. Standards Track [Page 1]\n\f\nRFC 4208 RSVP-TE Support for the Overlay Model October 2005","scope_keywords":["4208","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4783","folder":"IETF/RFC-4783","source":"IETF/RFC-4783/RFC-4783.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4874","folder":"IETF/RFC-4874","source":"IETF/RFC-4874/RFC-4874.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 4208 Generalized Multiprotocol Label Switching (GMPLS) defines both\n routing and signaling protocols for the creation of Label Switched\n Paths (LSPs) in various switching technologies. These protocols can\n be used to support a number of deployment scenarios. This memo\n addresses the application of GMPLS to the overlay model.\n\nSwallow, et al. Standards Track [Page 1]\n\f\nRFC 4208 RSVP-TE Support for the Overlay Model October 2005 4208 path nested-reference unchanged"},{"id":"IETF RFC 4209","type":"specification","body":"IETF","designation":"RFC 4209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4209.txt","https://www.rfc-editor.org/rfc/rfc4209.pdf"],"folder":"IETF/RFC-4209","files":{"txt":{"path":"standards/IETF/RFC-4209/RFC-4209.txt","sha256":"570bb19c21c38119a18dd9889c52cb0a8cd6a785575fd96c48a1ed010a6ddd80"}},"tags":["nested-reference","unchanged"],"summary":"The Link Management Protocol (LMP) is defined to manage traffic\n engineering (TE) links. In its present form, LMP focuses on peer\n nodes, i.e., nodes that peer in signaling and/or routing. This\n document proposes extensions to LMP to allow it to be used between a\n peer node and an adjacent optical line system (OLS). These\n extensions are intended to satisfy the \"Optical Link Interface\n Requirements\" described in a companion document.\n\n1. Introduction\n\n Networks are being developed with routers, switches, optical cross-\n connects (OXCs), dense wavelength division multiplexing (DWDM)\n optical line systems (OLSes), and add-drop multiplexors (ADMs) that\n use a common control plane (e.g., Generalized MPLS (GMPLS)) to\n dynamically provision resources and to provide network survivability\n using protection and restoration techniques.\n\n The Link Management Protocol (LMP) is being developed as par","scope_keywords":["4209","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null}],"search_text":"IETF RFC 4209 The Link Management Protocol (LMP) is defined to manage traffic\n engineering (TE) links. In its present form, LMP focuses on peer\n nodes, i.e., nodes that peer in signaling and/or routing. This\n document proposes extensions to LMP to allow it to be used between a\n peer node and an adjacent optical line system (OLS). These\n extensions are intended to satisfy the \"Optical Link Interface\n Requirements\" described in a companion document.\n\n1. Introduction\n\n Networks are being developed with routers, switches, optical cross-\n connects (OXCs), dense wavelength division multiplexing (DWDM)\n optical line systems (OLSes), and add-drop multiplexors (ADMs) that\n use a common control plane (e.g., Generalized MPLS (GMPLS)) to\n dynamically provision resources and to provide network survivability\n using protection and restoration techniques.\n\n The Link Management Protocol (LMP) is being developed as par 4209 key management nested-reference unchanged"},{"id":"IETF RFC 4220","type":"specification","body":"IETF","designation":"RFC 4220","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4220.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4220.txt","https://www.rfc-editor.org/rfc/rfc4220.pdf"],"folder":"IETF/RFC-4220","files":{"txt":{"path":"standards/IETF/RFC-4220/RFC-4220.txt","sha256":"1bcae8862269e5836982d0d4796703160a7df046b7cab1c887fdfb11f113fe3a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for modeling TE links as\n described in the Link Bundling in MPLS Traffic Engineering (TE)\n document.\n\nDubuc, et al. Standards Track [Page 1]\n\f\nRFC 4220 MPLS TE Link MIB Module November 2005","scope_keywords":["4220","key","management","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4221","folder":"IETF/RFC-4221","source":"IETF/RFC-4221/RFC-4221.txt","version":null},{"body":"IETF","designation":"RFC 4327","folder":"IETF/RFC-4327","source":"IETF/RFC-4327/RFC-4327.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 4220 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for modeling TE links as\n described in the Link Bundling in MPLS Traffic Engineering (TE)\n document.\n\nDubuc, et al. Standards Track [Page 1]\n\f\nRFC 4220 MPLS TE Link MIB Module November 2005 4220 key management risk nested-reference unchanged"},{"id":"IETF RFC 4235","type":"specification","body":"IETF","designation":"RFC 4235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4235.txt","https://www.rfc-editor.org/rfc/rfc4235.pdf"],"folder":"IETF/RFC-4235","files":{"txt":{"path":"standards/IETF/RFC-4235/RFC-4235.txt","sha256":"1ef85fdebc9b190a5be2c2575069e40588e5df2c2119e57b7a9efc6459ccf020"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a dialog event package for the SIP Events\n architecture, along with a data format used in notifications for this\n package. The dialog package allows users to subscribe to another\n user and to receive notification of the changes in state of INVITE-\n initiated dialog usages in which the subscribed-to user is involved.","scope_keywords":["4235"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4235 This document defines a dialog event package for the SIP Events\n architecture, along with a data format used in notifications for this\n package. The dialog package allows users to subscribe to another\n user and to receive notification of the changes in state of INVITE-\n initiated dialog usages in which the subscribed-to user is involved. 4235 nested-reference unchanged"},{"id":"IETF RFC 4242","type":"specification","body":"IETF","designation":"RFC 4242","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4242.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4242.txt","https://www.rfc-editor.org/rfc/rfc4242.pdf"],"folder":"IETF/RFC-4242","files":{"txt":{"path":"standards/IETF/RFC-4242/RFC-4242.txt","sha256":"3fe9cca6eae5817646fe120b1b5d8c4a10c7695670391d3dfd6370e83b390405"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) option for specifying an upper bound for how long a\n client should wait before refreshing information retrieved from\n DHCPv6. It is used with stateless DHCPv6 as there are no addresses\n or other entities with lifetimes that can tell the client when to\n contact the DHCPv6 server to refresh its configuration.","scope_keywords":["4242","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 6204","folder":"IETF/RFC-6204","source":"IETF/RFC-6204/RFC-6204.txt","version":null},{"body":"IETF","designation":"RFC 6731","folder":"IETF/RFC-6731","source":"IETF/RFC-6731/RFC-6731.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 4242 This document describes a Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) option for specifying an upper bound for how long a\n client should wait before refreshing information retrieved from\n DHCPv6. It is used with stateless DHCPv6 as there are no addresses\n or other entities with lifetimes that can tell the client when to\n contact the DHCPv6 server to refresh its configuration. 4242 key nested-reference unchanged"},{"id":"IETF RFC 4243","type":"specification","body":"IETF","designation":"RFC 4243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4243.txt","https://www.rfc-editor.org/rfc/rfc4243.pdf"],"folder":"IETF/RFC-4243","files":{"txt":{"path":"standards/IETF/RFC-4243/RFC-4243.txt","sha256":"5db9c152faba7a18de547959c3a4b7877d45e40d585711025a43520a65bb9916"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Vendor-Specific Information suboption for the\n Dynamic Host Configuration Protocol's (DHCP) relay agent information\n option. The suboption allows a DHCP relay agent to include vendor-\n specific information in the DHCP messages it forwards, as configured\n by its administrator.","scope_keywords":["4243","authentication","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null}],"search_text":"IETF RFC 4243 This memo defines a new Vendor-Specific Information suboption for the\n Dynamic Host Configuration Protocol's (DHCP) relay agent information\n option. The suboption allows a DHCP relay agent to include vendor-\n specific information in the DHCP messages it forwards, as configured\n by its administrator. 4243 authentication key registered nested-reference unchanged"},{"id":"IETF RFC 4244","type":"specification","body":"IETF","designation":"RFC 4244","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4244.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4244.txt","https://www.rfc-editor.org/rfc/rfc4244.pdf"],"folder":"IETF/RFC-4244","files":{"txt":{"path":"standards/IETF/RFC-4244/RFC-4244.txt","sha256":"6b69905a7790e05048bdb7c42676b5afcb3a9771620804c227cf3b1dc595082d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a standard mechanism for capturing the history\n information associated with a Session Initiation Protocol (SIP)\n request. This capability enables many enhanced services by providing\n the information as to how and why a call arrives at a specific\n application or user. This document defines a new optional SIP\n header, History-Info, for capturing the history information in\n requests.","scope_keywords":["4244","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4244 This document defines a standard mechanism for capturing the history\n information associated with a Session Initiation Protocol (SIP)\n request. This capability enables many enhanced services by providing\n the information as to how and why a call arrives at a specific\n application or user. This document defines a new optional SIP\n header, History-Info, for capturing the history information in\n requests. 4244 key management nested-reference unchanged"},{"id":"IETF RFC 4245","type":"specification","body":"IETF","designation":"RFC 4245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4245.txt","https://www.rfc-editor.org/rfc/rfc4245.pdf"],"folder":"IETF/RFC-4245","files":{"txt":{"path":"standards/IETF/RFC-4245/RFC-4245.txt","sha256":"4e9ff86df77a4df63efdca7c44d31e08a6717d4f945c63693d407838a70445f2"}},"tags":["nested-reference","unchanged"],"summary":"This document examines a wide range of conferencing requirements for\n tightly coupled SIP conferences. Separate documents will map the\n requirements to existing protocol primitives, define new protocol\n extensions, and introduce new protocols as needed. Together, these\n documents will provide a guide for building interoperable SIP\n conferencing applications.","scope_keywords":["4245","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null}],"search_text":"IETF RFC 4245 This document examines a wide range of conferencing requirements for\n tightly coupled SIP conferences. Separate documents will map the\n requirements to existing protocol primitives, define new protocol\n extensions, and introduce new protocols as needed. Together, these\n documents will provide a guide for building interoperable SIP\n conferencing applications. 4245 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 4247","type":"specification","body":"IETF","designation":"RFC 4247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4247.txt","https://www.rfc-editor.org/rfc/rfc4247.pdf"],"folder":"IETF/RFC-4247","files":{"txt":{"path":"standards/IETF/RFC-4247/RFC-4247.txt","sha256":"89d6838fd6d266d1012fb28ec65edfc68a783cf4cf70d61c8648b595e23651ae"}},"tags":["nested-reference","unchanged"],"summary":"Voice over IP (VoIP) typically uses the encapsulation\n voice/RTP/UDP/IP. When MPLS labels are added, this becomes\n voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is\n typically 48 bytes, while the voice payload is often no more than 30\n bytes, for example. Header compression can significantly reduce the\n overhead through various compression mechanisms, such as enhanced\n compressed RTP (ECRTP) and robust header compression (ROHC). We\n consider using MPLS to route compressed packets over an MPLS Label\n Switched Path (LSP) without compression/decompression cycles at each\n router. This approach can increase the bandwidth efficiency as well\n as processing scalability of the maximum number of simultaneous flows\n that use header compression at each router. In this document, we\n give a problem statement, goals and requirements, and an example\n scenario.\n\nAsh, et al. Informationa","scope_keywords":["4247","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null}],"search_text":"IETF RFC 4247 Voice over IP (VoIP) typically uses the encapsulation\n voice/RTP/UDP/IP. When MPLS labels are added, this becomes\n voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is\n typically 48 bytes, while the voice payload is often no more than 30\n bytes, for example. Header compression can significantly reduce the\n overhead through various compression mechanisms, such as enhanced\n compressed RTP (ECRTP) and robust header compression (ROHC). We\n consider using MPLS to route compressed packets over an MPLS Label\n Switched Path (LSP) without compression/decompression cycles at each\n router. This approach can increase the bandwidth efficiency as well\n as processing scalability of the maximum number of simultaneous flows\n that use header compression at each router. In this document, we\n give a problem statement, goals and requirements, and an example\n scenario.\n\nAsh, et al. Informationa 4247 algorithm path nested-reference unchanged"},{"id":"IETF RFC 4252","type":"specification","body":"IETF","designation":"RFC 4252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4252.txt","https://www.rfc-editor.org/rfc/rfc4252.pdf"],"folder":"IETF/RFC-4252","files":{"txt":{"path":"standards/IETF/RFC-4252/RFC-4252.txt","sha256":"a36b882cf77b107335d49921b5e955b4ba78e253205dfbce5096ebc0e78bdf14"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Shell Protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes the SSH authentication protocol framework and\n public key, password, and host-based client authentication methods.\n Additional authentication methods are described in separate\n documents. The SSH authentication protocol runs on top of the SSH\n transport layer protocol and provides a single authenticated tunnel\n for the SSH connection protocol.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4252 SSH Authentication Protocol January 2006","scope_keywords":["4252","authentication","hash","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null}],"search_text":"IETF RFC 4252 The Secure Shell Protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes the SSH authentication protocol framework and\n public key, password, and host-based client authentication methods.\n Additional authentication methods are described in separate\n documents. The SSH authentication protocol runs on top of the SSH\n transport layer protocol and provides a single authenticated tunnel\n for the SSH connection protocol.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4252 SSH Authentication Protocol January 2006 4252 authentication hash key nested-reference unchanged"},{"id":"IETF RFC 4254","type":"specification","body":"IETF","designation":"RFC 4254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4254.txt","https://www.rfc-editor.org/rfc/rfc4254.pdf"],"folder":"IETF/RFC-4254","files":{"txt":{"path":"standards/IETF/RFC-4254/RFC-4254.txt","sha256":"bfc727e9350067eaa49edeecc3d32f1e3518dd57cf3c36ceed02177156c5703f"}},"tags":["nested-reference","unchanged"],"summary":"Secure Shell (SSH) is a protocol for secure remote login and other\n secure network services over an insecure network.\n\n This document describes the SSH Connection Protocol. It provides\n interactive login sessions, remote execution of commands, forwarded\n TCP/IP connections, and forwarded X11 connections. All of these\n channels are multiplexed into a single encrypted tunnel.\n\n The SSH Connection Protocol has been designed to run on top of the\n SSH transport layer and user authentication protocols.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4254 SSH Connection Protocol January 2006","scope_keywords":["4254","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4742","folder":"IETF/RFC-4742","source":"IETF/RFC-4742/RFC-4742.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null}],"search_text":"IETF RFC 4254 Secure Shell (SSH) is a protocol for secure remote login and other\n secure network services over an insecure network.\n\n This document describes the SSH Connection Protocol. It provides\n interactive login sessions, remote execution of commands, forwarded\n TCP/IP connections, and forwarded X11 connections. All of these\n channels are multiplexed into a single encrypted tunnel.\n\n The SSH Connection Protocol has been designed to run on top of the\n SSH transport layer and user authentication protocols.\n\nYlonen & Lonvick Standards Track [Page 1]\n\f\nRFC 4254 SSH Connection Protocol January 2006 4254 authentication key nested-reference unchanged"},{"id":"IETF RFC 4256","type":"specification","body":"IETF","designation":"RFC 4256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4256.txt","https://www.rfc-editor.org/rfc/rfc4256.pdf"],"folder":"IETF/RFC-4256","files":{"txt":{"path":"standards/IETF/RFC-4256/RFC-4256.txt","sha256":"000091bd78ea7a4c71e2c0bd2c20998f0d0d775c71160b0f6c18fbe12d5a1233"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Shell Protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes a general purpose authentication method for the\n SSH protocol, suitable for interactive authentications where the\n authentication data should be entered via a keyboard (or equivalent\n alphanumeric input device). The major goal of this method is to\n allow the SSH client to support a whole class of authentication\n mechanism(s) without knowing the specifics of the actual\n authentication mechanism(s).\n\n1. Introduction\n\n The SSH authentication protocol [SSH-USERAUTH] is a general-purpose\n user authentication protocol. It is intended to be run over the SSH\n transport layer protocol [SSH-TRANS]. The authentication protocol\n assumes that the underlying protocols provide integrity and\n confidentiality protection.\n\n This document describes a ge","scope_keywords":["4256","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null}],"search_text":"IETF RFC 4256 The Secure Shell Protocol (SSH) is a protocol for secure remote login\n and other secure network services over an insecure network. This\n document describes a general purpose authentication method for the\n SSH protocol, suitable for interactive authentications where the\n authentication data should be entered via a keyboard (or equivalent\n alphanumeric input device). The major goal of this method is to\n allow the SSH client to support a whole class of authentication\n mechanism(s) without knowing the specifics of the actual\n authentication mechanism(s).\n\n1. Introduction\n\n The SSH authentication protocol [SSH-USERAUTH] is a general-purpose\n user authentication protocol. It is intended to be run over the SSH\n transport layer protocol [SSH-TRANS]. The authentication protocol\n assumes that the underlying protocols provide integrity and\n confidentiality protection.\n\n This document describes a ge 4256 authentication key nested-reference unchanged"},{"id":"IETF RFC 4258","type":"specification","body":"IETF","designation":"RFC 4258","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4258.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4258.txt","https://www.rfc-editor.org/rfc/rfc4258.pdf"],"folder":"IETF/RFC-4258","files":{"txt":{"path":"standards/IETF/RFC-4258/RFC-4258.txt","sha256":"c7adceb7bd3aeb0afded045662b0a180653be73dbf4a9f058267b5cdaa16b438"}},"tags":["nested-reference","unchanged"],"summary":"The Generalized Multi-Protocol Label Switching (GMPLS) suite of\n protocols has been defined to control different switching\n technologies as well as different applications. These include\n support for requesting Time Division Multiplexing (TDM) connections\n including Synchronous Optical Network (SONET)/Synchronous Digital\n Hierarchy (SDH) and Optical Transport Networks (OTNs).\n\n This document concentrates on the routing requirements placed on the\n GMPLS suite of protocols in order to support the capabilities and\n functionalities of an Automatically Switched Optical Network (ASON)\n as defined by the ITU-T.\n\nBrungard, Ed. Informational [Page 1]\n\f\nRFC 4258 GMPLS Routing for ASON November 2005","scope_keywords":["4258","attribute","attributes","key","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null}],"search_text":"IETF RFC 4258 The Generalized Multi-Protocol Label Switching (GMPLS) suite of\n protocols has been defined to control different switching\n technologies as well as different applications. These include\n support for requesting Time Division Multiplexing (TDM) connections\n including Synchronous Optical Network (SONET)/Synchronous Digital\n Hierarchy (SDH) and Optical Transport Networks (OTNs).\n\n This document concentrates on the routing requirements placed on the\n GMPLS suite of protocols in order to support the capabilities and\n functionalities of an Automatically Switched Optical Network (ASON)\n as defined by the ITU-T.\n\nBrungard, Ed. Informational [Page 1]\n\f\nRFC 4258 GMPLS Routing for ASON November 2005 4258 attribute attributes key management path presentation nested-reference unchanged"},{"id":"IETF RFC 4261","type":"specification","body":"IETF","designation":"RFC 4261","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4261.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4261.txt","https://www.rfc-editor.org/rfc/rfc4261.pdf"],"folder":"IETF/RFC-4261","files":{"txt":{"path":"standards/IETF/RFC-4261/RFC-4261.txt","sha256":"b33d4903f30381e3ea72d20e456b8a1ff4aeda81d4e19a551d9638462a5f726d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use Transport Layer Security (TLS) to\n secure Common Open Policy Service (COPS) connections over the\n Internet.\n\n This document also updates RFC 2748 by modifying the contents of the\n Client-Accept message.\n\nWalker & Kulkarni Standards Track [Page 1]\n\f\nRFC 4261 COPS Over TLS December 2005","scope_keywords":["4261","authentication","identification","key","policies","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4261 This document describes how to use Transport Layer Security (TLS) to\n secure Common Open Policy Service (COPS) connections over the\n Internet.\n\n This document also updates RFC 2748 by modifying the contents of the\n Client-Accept message.\n\nWalker & Kulkarni Standards Track [Page 1]\n\f\nRFC 4261 COPS Over TLS December 2005 4261 authentication identification key policies policy tls nested-reference unchanged"},{"id":"IETF RFC 4262","type":"specification","body":"IETF","designation":"RFC 4262","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4262.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4262.txt","https://www.rfc-editor.org/rfc/rfc4262.pdf"],"folder":"IETF/RFC-4262","files":{"txt":{"path":"standards/IETF/RFC-4262/RFC-4262.txt","sha256":"63b5756eac50229f4c7d419fc27f8cd75e1ff1579db17b929ca93dd627c3eac5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a certificate extension for inclusion of\n Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities in\n X.509 public key certificates, as defined by RFC 3280. This\n certificate extension provides an optional method to indicate the\n cryptographic capabilities of an entity as a complement to the S/MIME\n Capabilities signed attribute in S/MIME messages according to RFC\n 3851.\n\n1. Introduction\n\n This document defines a certificate extension for inclusion of S/MIME\n Capabilities in X.509 public key certificates, as defined by RFC 3280\n [RFC3280].\n\n The S/MIME Capabilities attribute, defined in RFC 3851 [RFC3851], is\n defined to indicate cryptographic capabilities of the sender of a\n signed S/MIME message. This information can be used by the recipient\n in subsequent S/MIME secured exchanges to select appropriate\n cryptographic properties.\n\n However, S/MIME does i","scope_keywords":["4262","algorithm","algorithms","attribute","certificate","certificates","crl","encryption","key","license","policy","profile","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5756","folder":"IETF/RFC-5756","source":"IETF/RFC-5756/RFC-5756.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 4262 This document defines a certificate extension for inclusion of\n Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities in\n X.509 public key certificates, as defined by RFC 3280. This\n certificate extension provides an optional method to indicate the\n cryptographic capabilities of an entity as a complement to the S/MIME\n Capabilities signed attribute in S/MIME messages according to RFC\n 3851.\n\n1. Introduction\n\n This document defines a certificate extension for inclusion of S/MIME\n Capabilities in X.509 public key certificates, as defined by RFC 3280\n [RFC3280].\n\n The S/MIME Capabilities attribute, defined in RFC 3851 [RFC3851], is\n defined to indicate cryptographic capabilities of the sender of a\n signed S/MIME message. This information can be used by the recipient\n in subsequent S/MIME secured exchanges to select appropriate\n cryptographic properties.\n\n However, S/MIME does i 4262 algorithm algorithms attribute certificate certificates crl encryption key license policy profile revocation subject nested-reference unchanged"},{"id":"IETF RFC 4265","type":"specification","body":"IETF","designation":"RFC 4265","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4265.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4265.txt","https://www.rfc-editor.org/rfc/rfc4265.pdf"],"folder":"IETF/RFC-4265","files":{"txt":{"path":"standards/IETF/RFC-4265/RFC-4265.txt","sha256":"e3e2c1495769cfd0c52ad140d21776ff60803ba262f086c52214717fbbee106f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Textual Conventions used for managing Virtual\n Private Networks (VPNs).","scope_keywords":["4265","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4382","folder":"IETF/RFC-4382","source":"IETF/RFC-4382/RFC-4382.txt","version":null}],"search_text":"IETF RFC 4265 This document describes Textual Conventions used for managing Virtual\n Private Networks (VPNs). 4265 http key management nested-reference unchanged"},{"id":"IETF RFC 4268","type":"specification","body":"IETF","designation":"RFC 4268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4268.txt","https://www.rfc-editor.org/rfc/rfc4268.pdf"],"folder":"IETF/RFC-4268","files":{"txt":{"path":"standards/IETF/RFC-4268/RFC-4268.txt","sha256":"1406828fd7e7233d736c1b4dbbe67052332ec7c6de3803b398c3ada7651c8e15"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes extensions to the Entity MIB to provide\n information about the state of physical entities.\n\n In addition, this memo defines a set of Textual Conventions to\n represent various states of an entity. The intent is that these\n Textual Conventions will be imported and used in MIB modules that\n would otherwise define their own representations.","scope_keywords":["4268","attribute","attributes","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null}],"search_text":"IETF RFC 4268 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes extensions to the Entity MIB to provide\n information about the state of physical entities.\n\n In addition, this memo defines a set of Textual Conventions to\n represent various states of an entity. The intent is that these\n Textual Conventions will be imported and used in MIB modules that\n would otherwise define their own representations. 4268 attribute attributes key management presentation nested-reference unchanged"},{"id":"IETF RFC 4272","type":"specification","body":"IETF","designation":"RFC 4272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4272.txt","https://www.rfc-editor.org/rfc/rfc4272.pdf"],"folder":"IETF/RFC-4272","files":{"txt":{"path":"standards/IETF/RFC-4272/RFC-4272.txt","sha256":"ac641eabf3f1460478a2f91f3a9e42980b2ca5b9482c671ccb5da511ffa46946"}},"tags":["nested-reference","unchanged"],"summary":"Border Gateway Protocol 4 (BGP-4), along with a host of other\n infrastructure protocols designed before the Internet environment\n became perilous, was originally designed with little consideration\n for protection of the information it carries. There are no\n mechanisms internal to BGP that protect against attacks that modify,\n delete, forge, or replay data, any of which has the potential to\n disrupt overall network routing behavior.\n\n This document discusses some of the security issues with BGP routing\n data dissemination. This document does not discuss security issues\n with forwarding of packets.\n\nMurphy Informational [Page 1]\n\f\nRFC 4272 BGP Security Vulnerabilities Analysis January 2006","scope_keywords":["4272","attribute","attributes","authentication","path","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 4272 Border Gateway Protocol 4 (BGP-4), along with a host of other\n infrastructure protocols designed before the Internet environment\n became perilous, was originally designed with little consideration\n for protection of the information it carries. There are no\n mechanisms internal to BGP that protect against attacks that modify,\n delete, forge, or replay data, any of which has the potential to\n disrupt overall network routing behavior.\n\n This document discusses some of the security issues with BGP routing\n data dissemination. This document does not discuss security issues\n with forwarding of packets.\n\nMurphy Informational [Page 1]\n\f\nRFC 4272 BGP Security Vulnerabilities Analysis January 2006 4272 attribute attributes authentication path risk subject nested-reference unchanged"},{"id":"IETF RFC 4283","type":"specification","body":"IETF","designation":"RFC 4283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4283.txt","https://www.rfc-editor.org/rfc/rfc4283.pdf"],"folder":"IETF/RFC-4283","files":{"txt":{"path":"standards/IETF/RFC-4283/RFC-4283.txt","sha256":"f56e5da672a5b871c26f146133df528283ab5f1c9f58858462b9ca506ba29bb2"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 (MIPv6) defines a new Mobility header that is used by\n mobile nodes, correspondent nodes, and home agents in all messaging\n related to the creation and management of bindings. Mobile IPv6\n nodes need the capability to identify themselves using an identity\n other than the default home IP address. Some examples of identifiers\n include Network Access Identifier (NAI), Fully Qualified Domain Name\n (FQDN), International Mobile Station Identifier (IMSI), and Mobile\n Subscriber Number (MSISDN). This document defines a new mobility\n option that can be used by Mobile IPv6 entities to identify\n themselves in messages containing a mobility header.\n\nPatel, et al. Standards Track [Page 1]\n\f\nRFC 4283 Mobile Node Identifier Option for MIPv6 November 2005","scope_keywords":["4283","authentication","authorization","key","management","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4285","folder":"IETF/RFC-4285","source":"IETF/RFC-4285/RFC-4285.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4283 Mobile IPv6 (MIPv6) defines a new Mobility header that is used by\n mobile nodes, correspondent nodes, and home agents in all messaging\n related to the creation and management of bindings. Mobile IPv6\n nodes need the capability to identify themselves using an identity\n other than the default home IP address. Some examples of identifiers\n include Network Access Identifier (NAI), Fully Qualified Domain Name\n (FQDN), International Mobile Station Identifier (IMSI), and Mobile\n Subscriber Number (MSISDN). This document defines a new mobility\n option that can be used by Mobile IPv6 entities to identify\n themselves in messages containing a mobility header.\n\nPatel, et al. Standards Track [Page 1]\n\f\nRFC 4283 Mobile Node Identifier Option for MIPv6 November 2005 4283 authentication authorization key management qualified nested-reference unchanged"},{"id":"IETF RFC 4287","type":"specification","body":"IETF","designation":"RFC 4287","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4287.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4287.txt","https://www.rfc-editor.org/rfc/rfc4287.pdf"],"folder":"IETF/RFC-4287","files":{"txt":{"path":"standards/IETF/RFC-4287/RFC-4287.txt","sha256":"3bd71d76289560c9e860151f39cebbdc402cfd8b788a62048d8dc42824f2d89c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Atom, an XML-based Web content and metadata\n syndication format.","scope_keywords":["4287","attribute","encryption","http","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4685","folder":"IETF/RFC-4685","source":"IETF/RFC-4685/RFC-4685.txt","version":null},{"body":"IETF","designation":"RFC 4946","folder":"IETF/RFC-4946","source":"IETF/RFC-4946/RFC-4946.txt","version":null},{"body":"IETF","designation":"RFC 5005","folder":"IETF/RFC-5005","source":"IETF/RFC-5005/RFC-5005.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null},{"body":"IETF","designation":"RFC 5829","folder":"IETF/RFC-5829","source":"IETF/RFC-5829/RFC-5829.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 4287 This document specifies Atom, an XML-based Web content and metadata\n syndication format. 4287 attribute encryption http signature signatures nested-reference unchanged"},{"id":"IETF RFC 4303","type":"specification","body":"IETF","designation":"RFC 4303","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4303.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4303.txt","https://www.rfc-editor.org/rfc/rfc4303.pdf"],"folder":"IETF/RFC-4303","files":{"txt":{"path":"standards/IETF/RFC-4303/RFC-4303.txt","sha256":"d22f9d4120e5645525b63ac7bbf8ef78c334fe003a2c48bf1e25ac25f6e7dc58"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an updated version of the Encapsulating\n Security Payload (ESP) protocol, which is designed to provide a mix\n of security services in IPv4 and IPv6. ESP is used to provide\n confidentiality, data origin authentication, connectionless\n integrity, an anti-replay service (a form of partial sequence\n integrity), and limited traffic flow confidentiality. This document\n obsoletes RFC 2406 (November 1998).","scope_keywords":["4303","algorithm","algorithms","audit","authentication","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4304","folder":"IETF/RFC-4304","source":"IETF/RFC-4304/RFC-4304.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 4359","folder":"IETF/RFC-4359","source":"IETF/RFC-4359/RFC-4359.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4418","folder":"IETF/RFC-4418","source":"IETF/RFC-4418/RFC-4418.txt","version":null},{"body":"IETF","designation":"RFC 4494","folder":"IETF/RFC-4494","source":"IETF/RFC-4494/RFC-4494.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4543","folder":"IETF/RFC-4543","source":"IETF/RFC-4543/RFC-4543.txt","version":null},{"body":"IETF","designation":"RFC 4552","folder":"IETF/RFC-4552","source":"IETF/RFC-4552/RFC-4552.txt","version":null},{"body":"IETF","designation":"RFC 4595","folder":"IETF/RFC-4595","source":"IETF/RFC-4595/RFC-4595.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4835","folder":"IETF/RFC-4835","source":"IETF/RFC-4835/RFC-4835.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4868","folder":"IETF/RFC-4868","source":"IETF/RFC-4868/RFC-4868.txt","version":null},{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5116","folder":"IETF/RFC-5116","source":"IETF/RFC-5116/RFC-5116.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5282","folder":"IETF/RFC-5282","source":"IETF/RFC-5282/RFC-5282.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5906","folder":"IETF/RFC-5906","source":"IETF/RFC-5906/RFC-5906.txt","version":null},{"body":"IETF","designation":"RFC 5930","folder":"IETF/RFC-5930","source":"IETF/RFC-5930/RFC-5930.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 4303 This document describes an updated version of the Encapsulating\n Security Payload (ESP) protocol, which is designed to provide a mix\n of security services in IPv4 and IPv6. ESP is used to provide\n confidentiality, data origin authentication, connectionless\n integrity, an anti-replay service (a form of partial sequence\n integrity), and limited traffic flow confidentiality. This document\n obsoletes RFC 2406 (November 1998). 4303 algorithm algorithms audit authentication encryption key management nested-reference unchanged"},{"id":"IETF RFC 4304","type":"specification","body":"IETF","designation":"RFC 4304","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4304.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4304.txt","https://www.rfc-editor.org/rfc/rfc4304.pdf"],"folder":"IETF/RFC-4304","files":{"txt":{"path":"standards/IETF/RFC-4304/RFC-4304.txt","sha256":"b5038d7f692a6b31394e842f706cb7b1d14c62663639e1e7fc0b998fc068ac0e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kent\nRequest for Comments: 4304 BBN Technologies\nCategory: Standards Track December 2005\n\n Extended Sequence Number (ESN) Addendum to\n IPsec Domain of Interpretation (DOI)\n for Internet Security Association\n and Key Management Protocol (ISAKMP)\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The IP Security Authentication Header (AH) and Encapsulating Security\n Payload (ESP) protocols use a sequence number to detect replay. This\n document describes extensions to the Internet IP Se","scope_keywords":["4304","algorithm","attribute","attributes","authentication","encryption","key","license","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4304 Network Working Group S. Kent\nRequest for Comments: 4304 BBN Technologies\nCategory: Standards Track December 2005\n\n Extended Sequence Number (ESN) Addendum to\n IPsec Domain of Interpretation (DOI)\n for Internet Security Association\n and Key Management Protocol (ISAKMP)\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The IP Security Authentication Header (AH) and Encapsulating Security\n Payload (ESP) protocols use a sequence number to detect replay. This\n document describes extensions to the Internet IP Se 4304 algorithm attribute attributes authentication encryption key license management subject nested-reference unchanged"},{"id":"IETF RFC 4311","type":"specification","body":"IETF","designation":"RFC 4311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4311.txt","https://www.rfc-editor.org/rfc/rfc4311.pdf"],"folder":"IETF/RFC-4311","files":{"txt":{"path":"standards/IETF/RFC-4311/RFC-4311.txt","sha256":"4f983d81eb4bcee6092f27d63eb01224bd8b7ba84c15871e26266cc721cf7113"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Hinden\nRequest for Comments: 4311 Nokia\nUpdates: 2461 D. Thaler\nCategory: Standards Track Microsoft\n November 2005\n\n IPv6 Host-to-Router Load Sharing\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The original IPv6 conceptual sending algorithm does not do load\n sharing among equivalent IPv6 routers, and suggests schemes that can\n be problematic in practice. This document updates the conceptual\n sending algorithm in RFC 2461 so that traffic to different\n destinations can be distri","scope_keywords":["4311","algorithm","hash","hashing","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 6419","folder":"IETF/RFC-6419","source":"IETF/RFC-6419/RFC-6419.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null}],"search_text":"IETF RFC 4311 Network Working Group R. Hinden\nRequest for Comments: 4311 Nokia\nUpdates: 2461 D. Thaler\nCategory: Standards Track Microsoft\n November 2005\n\n IPv6 Host-to-Router Load Sharing\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n The original IPv6 conceptual sending algorithm does not do load\n sharing among equivalent IPv6 routers, and suggests schemes that can\n be problematic in practice. This document updates the conceptual\n sending algorithm in RFC 2461 so that traffic to different\n destinations can be distri 4311 algorithm hash hashing key path nested-reference unchanged"},{"id":"IETF RFC 4312","type":"specification","body":"IETF","designation":"RFC 4312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4312.txt","https://www.rfc-editor.org/rfc/rfc4312.pdf"],"folder":"IETF/RFC-4312","files":{"txt":{"path":"standards/IETF/RFC-4312/RFC-4312.txt","sha256":"3a1034a459d9be0b6195576b1171b413e8556967e7126b692a617a9b4fa38988"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining Mode, with an explicit\n Initialization Vector, as a confidentiality mechanism within the\n context of the IPsec Encapsulating Security Payload (ESP).\n\n1. Introduction\n\n This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining Mode, with an explicit\n Initialization Vector, as a confidentiality mechanism within the\n context of the IPsec Encapsulating Security Payload (ESP).\n\n Camellia was selected as a recommended cryptographic primitive by the\n EU NESSIE (New European Schemes for Signatures, Integrity and\n Encryption) project [NESSIE] and was included in the list of\n cryptographic techniques for Japanese e-Government systems that was\n selected by the Japan CRYPTREC (Cryptography Research, Evaluation\n Committees) [CRYPTREC]. Camellia has been submitted to ","scope_keywords":["4312","algorithm","algorithms","encryption","key","keys","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4312 This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining Mode, with an explicit\n Initialization Vector, as a confidentiality mechanism within the\n context of the IPsec Encapsulating Security Payload (ESP).\n\n1. Introduction\n\n This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining Mode, with an explicit\n Initialization Vector, as a confidentiality mechanism within the\n context of the IPsec Encapsulating Security Payload (ESP).\n\n Camellia was selected as a recommended cryptographic primitive by the\n EU NESSIE (New European Schemes for Signatures, Integrity and\n Encryption) project [NESSIE] and was included in the list of\n cryptographic techniques for Japanese e-Government systems that was\n selected by the Japan CRYPTREC (Cryptography Research, Evaluation\n Committees) [CRYPTREC]. Camellia has been submitted to  4312 algorithm algorithms encryption key keys signature signatures nested-reference unchanged"},{"id":"IETF RFC 4313","type":"specification","body":"IETF","designation":"RFC 4313","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4313.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4313.txt","https://www.rfc-editor.org/rfc/rfc4313.pdf"],"folder":"IETF/RFC-4313","files":{"txt":{"path":"standards/IETF/RFC-4313/RFC-4313.txt","sha256":"9424fdbd948ca6c9925d74b9a3ae16cf2a631644a7891f4f3c53c8c1de6c0fcd"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines the needs and requirements for a protocol to\n control distributed speech processing of audio streams. By speech\n processing, this document specifically means automatic speech\n recognition (ASR), speaker recognition -- which includes both speaker\n identification (SI) and speaker verification (SV) -- and\n text-to-speech (TTS). Other IETF protocols, such as SIP and Real\n Time Streaming Protocol (RTSP), address rendezvous and control for\n generalized media streams. However, speech processing presents\n additional requirements that none of the extant IETF protocols\n address.","scope_keywords":["4313","identification","key","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null}],"search_text":"IETF RFC 4313 This document outlines the needs and requirements for a protocol to\n control distributed speech processing of audio streams. By speech\n processing, this document specifically means automatic speech\n recognition (ASR), speaker recognition -- which includes both speaker\n identification (SI) and speaker verification (SV) -- and\n text-to-speech (TTS). Other IETF protocols, such as SIP and Real\n Time Streaming Protocol (RTSP), address rendezvous and control for\n generalized media streams. However, speech processing presents\n additional requirements that none of the extant IETF protocols\n address. 4313 identification key tsp nested-reference unchanged"},{"id":"IETF RFC 4315","type":"specification","body":"IETF","designation":"RFC 4315","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4315.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4315.txt","https://www.rfc-editor.org/rfc/rfc4315.pdf"],"folder":"IETF/RFC-4315","files":{"txt":{"path":"standards/IETF/RFC-4315/RFC-4315.txt","sha256":"4ce974eeaa9110752c7f803ee16bb1c39bd84a2f836a68e413cecbb4c61fa805"}},"tags":["nested-reference","unchanged"],"summary":"The UIDPLUS extension of the Internet Message Access Protocol (IMAP)\n provides a set of features intended to reduce the amount of time and\n resources used by some client operations. The features in UIDPLUS\n are primarily intended for disconnected-use clients.\n\n1. Introduction and Overview\n\n The UIDPLUS extension is present in any IMAP server implementation\n that returns \"UIDPLUS\" as one of the supported capabilities to the\n CAPABILITY command.\n\n The UIDPLUS extension defines an additional command. In addition,\n this document recommends new status response codes in IMAP that\n SHOULD be returned by all server implementations, regardless of\n whether or not the UIDPLUS extension is implemented.\n\n The added facilities of the features in UIDPLUS are optimizations;\n clients can provide equivalent functionality, albeit less\n efficiently, by using facilities in the base protocol.","scope_keywords":["4315","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4550","folder":"IETF/RFC-4550","source":"IETF/RFC-4550/RFC-4550.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4315 The UIDPLUS extension of the Internet Message Access Protocol (IMAP)\n provides a set of features intended to reduce the amount of time and\n resources used by some client operations. The features in UIDPLUS\n are primarily intended for disconnected-use clients.\n\n1. Introduction and Overview\n\n The UIDPLUS extension is present in any IMAP server implementation\n that returns \"UIDPLUS\" as one of the supported capabilities to the\n CAPABILITY command.\n\n The UIDPLUS extension defines an additional command. In addition,\n this document recommends new status response codes in IMAP that\n SHOULD be returned by all server implementations, regardless of\n whether or not the UIDPLUS extension is implemented.\n\n The added facilities of the features in UIDPLUS are optimizations;\n clients can provide equivalent functionality, albeit less\n efficiently, by using facilities in the base protocol. 4315 key risk nested-reference unchanged"},{"id":"IETF RFC 4319","type":"specification","body":"IETF","designation":"RFC 4319","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4319.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4319.txt","https://www.rfc-editor.org/rfc/rfc4319.pdf"],"folder":"IETF/RFC-4319","files":{"txt":{"path":"standards/IETF/RFC-4319/RFC-4319.txt","sha256":"4b48982787e42214209b63d06b92ed1e71642f2bf0ebac447a997d0188c5438c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing High Bit-Rate\n Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and\n Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces.\n This document introduces extensions to several objects and textual\n conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This\n document obsoletes RFC 3276.\n\nSikes, et al. Standards Track [Page 1]\n\f\nRFC 4319 HDSL2-SHDSL-LINE-MIB December 2005","scope_keywords":["4319","attribute","attributes","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"IETF RFC 4319 This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing High Bit-Rate\n Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and\n Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces.\n This document introduces extensions to several objects and textual\n conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This\n document obsoletes RFC 3276.\n\nSikes, et al. Standards Track [Page 1]\n\f\nRFC 4319 HDSL2-SHDSL-LINE-MIB December 2005 4319 attribute attributes key management profile profiles nested-reference unchanged"},{"id":"IETF RFC 4325","type":"specification","body":"IETF","designation":"RFC 4325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4325.txt","https://www.rfc-editor.org/rfc/rfc4325.pdf"],"folder":"IETF/RFC-4325","files":{"txt":{"path":"standards/IETF/RFC-4325/RFC-4325.txt","sha256":"95ad945a2a6c857b008e908d43937a8f42fab0a4491a1a37cff0f5783aeded62"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3280 by defining the Authority Information\n Access Certificate Revocation List (CRL) extension. RFC 3280 defines\n the Authority Information Access certificate extension using the same\n syntax. The CRL extension provides a means of discovering and\n retrieving CRL issuer certificates.","scope_keywords":["4325","certificate","certificates","crl","http","issuer","key","keys","path","pki","revocation","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null}],"search_text":"IETF RFC 4325 This document updates RFC 3280 by defining the Authority Information\n Access Certificate Revocation List (CRL) extension. RFC 3280 defines\n the Authority Information Access certificate extension using the same\n syntax. The CRL extension provides a means of discovering and\n retrieving CRL issuer certificates. 4325 certificate certificates crl http issuer key keys path pki revocation signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 4327","type":"specification","body":"IETF","designation":"RFC 4327","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4327.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4327.txt","https://www.rfc-editor.org/rfc/rfc4327.pdf"],"folder":"IETF/RFC-4327","files":{"txt":{"path":"standards/IETF/RFC-4327/RFC-4327.txt","sha256":"b477493a51f0ea4d930c8f73d696a5721cc66b38aac50915cadfcb7d1cbf9d2b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for modeling the Link\n Management Protocol (LMP).","scope_keywords":["4327","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 4327 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for modeling the Link\n Management Protocol (LMP). 4327 key management nested-reference unchanged"},{"id":"IETF RFC 4329","type":"specification","body":"IETF","designation":"RFC 4329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4329.txt","https://www.rfc-editor.org/rfc/rfc4329.pdf"],"folder":"IETF/RFC-4329","files":{"txt":{"path":"standards/IETF/RFC-4329/RFC-4329.txt","sha256":"6e927eb2592b4d919d3cbaff508298ebd1928025f88cd8923218685a56733c66"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the registration of media types for the\n ECMAScript and JavaScript programming languages and conformance\n requirements for implementations of these types.","scope_keywords":["4329","key","presentation","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6108","folder":"IETF/RFC-6108","source":"IETF/RFC-6108/RFC-6108.txt","version":null}],"search_text":"IETF RFC 4329 This document describes the registration of media types for the\n ECMAScript and JavaScript programming languages and conformance\n requirements for implementations of these types. 4329 key presentation profile registered nested-reference unchanged"},{"id":"IETF RFC 4331","type":"specification","body":"IETF","designation":"RFC 4331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4331.txt","https://www.rfc-editor.org/rfc/rfc4331.pdf"],"folder":"IETF/RFC-4331","files":{"txt":{"path":"standards/IETF/RFC-4331/RFC-4331.txt","sha256":"a5814ac93b8d67497a9f09aa2490f1ecbf1dfd2a60633506c2973fce92dc9456"}},"tags":["nested-reference","unchanged"],"summary":"Web Distributed Authoring and Versioning (WebDAV) servers are\n frequently deployed with quota (size) limitations. This document\n discusses the properties and minor behaviors needed for clients to\n interoperate with quota (size) implementations on WebDAV\n repositories.","scope_keywords":["4331","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null}],"search_text":"IETF RFC 4331 Web Distributed Authoring and Versioning (WebDAV) servers are\n frequently deployed with quota (size) limitations. This document\n discusses the properties and minor behaviors needed for clients to\n interoperate with quota (size) implementations on WebDAV\n repositories. 4331 key nested-reference unchanged"},{"id":"IETF RFC 4342","type":"specification","body":"IETF","designation":"RFC 4342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4342.txt","https://www.rfc-editor.org/rfc/rfc4342.pdf"],"folder":"IETF/RFC-4342","files":{"txt":{"path":"standards/IETF/RFC-4342/RFC-4342.txt","sha256":"7d70f15617c443007a44c3bf7fc21d0a795aa11d17fe084c5bb88177fed8b4e2"}},"tags":["nested-reference","unchanged"],"summary":"This document contains the profile for Congestion Control Identifier\n 3, TCP-Friendly Rate Control (TFRC), in the Datagram Congestion\n Control Protocol (DCCP). CCID 3 should be used by senders that want\n a TCP-friendly sending rate, possibly with Explicit Congestion\n Notification (ECN), while minimizing abrupt rate changes.","scope_keywords":["4342","key","profile","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4774","folder":"IETF/RFC-4774","source":"IETF/RFC-4774/RFC-4774.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 5238","folder":"IETF/RFC-5238","source":"IETF/RFC-5238/RFC-5238.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 4342 This document contains the profile for Congestion Control Identifier\n 3, TCP-Friendly Rate Control (TFRC), in the Datagram Congestion\n Control Protocol (DCCP). CCID 3 should be used by senders that want\n a TCP-friendly sending rate, possibly with Explicit Congestion\n Notification (ECN), while minimizing abrupt rate changes. 4342 key profile timestamp nested-reference unchanged"},{"id":"IETF RFC 4345","type":"specification","body":"IETF","designation":"RFC 4345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4345.txt","https://www.rfc-editor.org/rfc/rfc4345.pdf"],"folder":"IETF/RFC-4345","files":{"txt":{"path":"standards/IETF/RFC-4345/RFC-4345.txt","sha256":"1593163d1d178a35adb02a91642b1d8592ea1a857ead07270693f9fb60635b3e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies methods of using the Arcfour cipher in the\n Secure Shell (SSH) protocol that mitigate the weakness of the\n cipher's key-scheduling algorithm.\n\n1. Introduction\n\n Secure Shell (SSH) [RFC4251] is a secure remote-login protocol. It\n allows for the use of an extensible variety of symmetric cipher\n algorithms to provide confidentiality for data in transit. One of\n the algorithms specified in the base protocol is \"arcfour\", which\n specifies the use of Arcfour (also known as RC4), a fast stream\n cipher. As [RFC4253] says, though, \"Arcfour (and RC4) has problems\n with weak keys, and should be used with caution.\" These problems are\n described in more detail in [MANTIN01], along with a recommendation\n to discard the first 1536 bytes of keystream so as to ensure that the\n cipher's internal state is thoroughly mixed. This document specifies\n new cipher algorithms for SSH that ","scope_keywords":["4345","algorithm","algorithms","encryption","http","key","keys","license","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6229","folder":"IETF/RFC-6229","source":"IETF/RFC-6229/RFC-6229.txt","version":null}],"search_text":"IETF RFC 4345 This document specifies methods of using the Arcfour cipher in the\n Secure Shell (SSH) protocol that mitigate the weakness of the\n cipher's key-scheduling algorithm.\n\n1. Introduction\n\n Secure Shell (SSH) [RFC4251] is a secure remote-login protocol. It\n allows for the use of an extensible variety of symmetric cipher\n algorithms to provide confidentiality for data in transit. One of\n the algorithms specified in the base protocol is \"arcfour\", which\n specifies the use of Arcfour (also known as RC4), a fast stream\n cipher. As [RFC4253] says, though, \"Arcfour (and RC4) has problems\n with weak keys, and should be used with caution.\" These problems are\n described in more detail in [MANTIN01], along with a recommendation\n to discard the first 1536 bytes of keystream so as to ensure that the\n cipher's internal state is thoroughly mixed. This document specifies\n new cipher algorithms for SSH that  4345 algorithm algorithms encryption http key keys license registered subject nested-reference unchanged"},{"id":"IETF RFC 4349","type":"specification","body":"IETF","designation":"RFC 4349","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4349.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4349.txt","https://www.rfc-editor.org/rfc/rfc4349.pdf"],"folder":"IETF/RFC-4349","files":{"txt":{"path":"standards/IETF/RFC-4349/RFC-4349.txt","sha256":"7f35874425d9e85e308243edc5f8b872b5b17a7985ca3a21e8cd9fc288c7e352"}},"tags":["nested-reference","unchanged"],"summary":"The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a\n protocol for tunneling a variety of data link protocols over IP\n networks. This document describes the specifics of how to tunnel\n High-Level Data Link Control (HDLC) frames over L2TPv3.\n\nPignataro & Townsley Standards Track [Page 1]\n\f\nRFC 4349 HDLC Frames over L2TPv3 February 2006","scope_keywords":["4349","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null}],"search_text":"IETF RFC 4349 The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a\n protocol for tunneling a variety of data link protocols over IP\n networks. This document describes the specifics of how to tunnel\n High-Level Data Link Control (HDLC) frames over L2TPv3.\n\nPignataro & Townsley Standards Track [Page 1]\n\f\nRFC 4349 HDLC Frames over L2TPv3 February 2006 4349 attribute key nested-reference unchanged"},{"id":"IETF RFC 4354","type":"specification","body":"IETF","designation":"RFC 4354","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4354.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4354.txt","https://www.rfc-editor.org/rfc/rfc4354.pdf"],"folder":"IETF/RFC-4354","files":{"txt":{"path":"standards/IETF/RFC-4354/RFC-4354.txt","sha256":"9c491f8a5dfba162ebcbdba7d1121d178c6117fdab7fafd1dda9f3e44f7dfd1a"}},"tags":["nested-reference","unchanged"],"summary":"The Open Mobile Alliance (OMA) is defining the Push-to-talk over\n Cellular (PoC) service where SIP is the protocol used to establish\n half-duplex media sessions across different participants, to send\n instant messages, etc. This document defines a SIP event package to\n support publication, subscription, and notification of additional\n capabilities required by the PoC service. This SIP event package is\n applicable to the PoC service and may not be applicable to the\n general Internet.\n\nGarcia-Martin Informational [Page 1]\n\f\nRFC 4354 PoC Settings Event Package January 2006","scope_keywords":["4354","authentication","authorization","http","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null}],"search_text":"IETF RFC 4354 The Open Mobile Alliance (OMA) is defining the Push-to-talk over\n Cellular (PoC) service where SIP is the protocol used to establish\n half-duplex media sessions across different participants, to send\n instant messages, etc. This document defines a SIP event package to\n support publication, subscription, and notification of additional\n capabilities required by the PoC service. This SIP event package is\n applicable to the PoC service and may not be applicable to the\n general Internet.\n\nGarcia-Martin Informational [Page 1]\n\f\nRFC 4354 PoC Settings Event Package January 2006 4354 authentication authorization http policy registered nested-reference unchanged"},{"id":"IETF RFC 4359","type":"specification","body":"IETF","designation":"RFC 4359","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4359.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4359.txt","https://www.rfc-editor.org/rfc/rfc4359.pdf"],"folder":"IETF/RFC-4359","files":{"txt":{"path":"standards/IETF/RFC-4359/RFC-4359.txt","sha256":"3df23244edf10358a34b94fe4dc7e56161067dd6bdb09db6d05f1b522aab9524"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the RSA digital signature algorithm as\n an authentication algorithm within the revised IP Encapsulating\n Security Payload (ESP) as described in RFC 4303 and the revised IP\n Authentication Header (AH) as described in RFC 4302. The use of a\n digital signature algorithm, such as RSA, provides data origin\n authentication in applications when a secret key method (e.g., HMAC)\n does not provide this property. One example is the use of ESP and AH\n to authenticate the sender of an IP multicast packet.\n\nWeis Standards Track [Page 1]\n\f\nRFC 4359 RSA/SHA-1 Signatures within ESP and AH January 2006","scope_keywords":["4359","algorithm","algorithms","authentication","hash","holder","key","keys","management","policy","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5776","folder":"IETF/RFC-5776","source":"IETF/RFC-5776/RFC-5776.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null}],"search_text":"IETF RFC 4359 This memo describes the use of the RSA digital signature algorithm as\n an authentication algorithm within the revised IP Encapsulating\n Security Payload (ESP) as described in RFC 4303 and the revised IP\n Authentication Header (AH) as described in RFC 4302. The use of a\n digital signature algorithm, such as RSA, provides data origin\n authentication in applications when a secret key method (e.g., HMAC)\n does not provide this property. One example is the use of ESP and AH\n to authenticate the sender of an IP multicast packet.\n\nWeis Standards Track [Page 1]\n\f\nRFC 4359 RSA/SHA-1 Signatures within ESP and AH January 2006 4359 algorithm algorithms authentication hash holder key keys management policy signature signatures nested-reference unchanged"},{"id":"IETF RFC 4361","type":"specification","body":"IETF","designation":"RFC 4361","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4361.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4361.txt","https://www.rfc-editor.org/rfc/rfc4361.pdf"],"folder":"IETF/RFC-4361","files":{"txt":{"path":"standards/IETF/RFC-4361/RFC-4361.txt","sha256":"84a37802e74aad730cabcbf5fa3051c8d02ad286c6c46a044b0491bb765637d4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the format that is to be used for encoding\n Dynamic Host Configuration Protocol Version Four (DHCPv4) client\n identifiers, so that those identifiers will be interchangeable with\n identifiers used in the DHCPv6 protocol. This document also\n addresses and corrects some problems in RFC 2131 and RFC 2132 with\n respect to the handling of DHCP client identifiers.","scope_keywords":["4361","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4477","folder":"IETF/RFC-4477","source":"IETF/RFC-4477/RFC-4477.txt","version":null},{"body":"IETF","designation":"RFC 4701","folder":"IETF/RFC-4701","source":"IETF/RFC-4701/RFC-4701.txt","version":null},{"body":"IETF","designation":"RFC 4703","folder":"IETF/RFC-4703","source":"IETF/RFC-4703/RFC-4703.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null}],"search_text":"IETF RFC 4361 This document specifies the format that is to be used for encoding\n Dynamic Host Configuration Protocol Version Four (DHCPv4) client\n identifiers, so that those identifiers will be interchangeable with\n identifiers used in the DHCPv6 protocol. This document also\n addresses and corrects some problems in RFC 2131 and RFC 2132 with\n respect to the handling of DHCP client identifiers. 4361 key nested-reference unchanged"},{"id":"IETF RFC 4372","type":"specification","body":"IETF","designation":"RFC 4372","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4372.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4372.txt","https://www.rfc-editor.org/rfc/rfc4372.pdf"],"folder":"IETF/RFC-4372","files":{"txt":{"path":"standards/IETF/RFC-4372/RFC-4372.txt","sha256":"4f84e9c19bed02cced007136c00cf20e209ea98bcec98ef65a4ca4e9f918893a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new Remote Authentication Dial-In User\n Service (RADIUS) attribute, Chargeable-User-Identity. This attribute\n can be used by a home network to identify a user for the purpose of\n roaming transactions that occur outside of the home network.","scope_keywords":["4372","attribute","attributes","authentication","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 4372 This document describes a new Remote Authentication Dial-In User\n Service (RADIUS) attribute, Chargeable-User-Identity. This attribute\n can be used by a home network to identify a user for the purpose of\n roaming transactions that occur outside of the home network. 4372 attribute attributes authentication profile tls nested-reference unchanged"},{"id":"IETF RFC 4376","type":"specification","body":"IETF","designation":"RFC 4376","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4376.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4376.txt","https://www.rfc-editor.org/rfc/rfc4376.pdf"],"folder":"IETF/RFC-4376","files":{"txt":{"path":"standards/IETF/RFC-4376/RFC-4376.txt","sha256":"af4d02fce1c70bb8cdfa25b6f996570201185f9fc5218569a3ee1a35ef8b24be"}},"tags":["nested-reference","unchanged"],"summary":"Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols. This\n document defines the requirements for a floor control protocol for\n multiparty conferences in the context of an existing framework.\n\nKoskelainen, et al. Informational [Page 1]\n\f\nRFC 4376 Floor Control Protocol Requirements February 2006","scope_keywords":["4376","holder","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 4376 Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols. This\n document defines the requirements for a floor control protocol for\n multiparty conferences in the context of an existing framework.\n\nKoskelainen, et al. Informational [Page 1]\n\f\nRFC 4376 Floor Control Protocol Requirements February 2006 4376 holder key policy nested-reference unchanged"},{"id":"IETF RFC 4377","type":"specification","body":"IETF","designation":"RFC 4377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4377.txt","https://www.rfc-editor.org/rfc/rfc4377.pdf"],"folder":"IETF/RFC-4377","files":{"txt":{"path":"standards/IETF/RFC-4377/RFC-4377.txt","sha256":"413243d4918739893adb058dad412167279d2a9842c4022c4d2645ee32b65622"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Operations and Management (OAM) requirements\n for Multi-Protocol Label Switching (MPLS), as well as for\n applications of MPLS, such as pseudo-wire voice and virtual private\n network services. These requirements have been gathered from network\n operators who have extensive experience deploying MPLS networks.","scope_keywords":["4377","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4378","folder":"IETF/RFC-4378","source":"IETF/RFC-4378/RFC-4378.txt","version":null},{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4377 This document specifies Operations and Management (OAM) requirements\n for Multi-Protocol Label Switching (MPLS), as well as for\n applications of MPLS, such as pseudo-wire voice and virtual private\n network services. These requirements have been gathered from network\n operators who have extensive experience deploying MPLS networks. 4377 key management path nested-reference unchanged"},{"id":"IETF RFC 4378","type":"specification","body":"IETF","designation":"RFC 4378","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4378.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4378.txt","https://www.rfc-editor.org/rfc/rfc4378.pdf"],"folder":"IETF/RFC-4378","files":{"txt":{"path":"standards/IETF/RFC-4378/RFC-4378.txt","sha256":"e0870c0b431ca28cd9d4a700062da1f1e62624176fdce6a1eb0e9334321be24e"}},"tags":["nested-reference","unchanged"],"summary":"This document is a framework for how data plane protocols can be\n applied to operations and maintenance procedures for Multi-Protocol\n Label Switching (MPLS). The document is structured to outline how\n Operations and Management (OAM) functionality can be used to assist\n in fault, configuration, accounting, performance, and security\n management, commonly known by the acronym FCAPS.","scope_keywords":["4378","identification","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 4378 This document is a framework for how data plane protocols can be\n applied to operations and maintenance procedures for Multi-Protocol\n Label Switching (MPLS). The document is structured to outline how\n Operations and Management (OAM) functionality can be used to assist\n in fault, configuration, accounting, performance, and security\n management, commonly known by the acronym FCAPS. 4378 identification key management path nested-reference unchanged"},{"id":"IETF RFC 4385","type":"specification","body":"IETF","designation":"RFC 4385","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4385.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4385.txt","https://www.rfc-editor.org/rfc/rfc4385.pdf"],"folder":"IETF/RFC-4385","files":{"txt":{"path":"standards/IETF/RFC-4385/RFC-4385.txt","sha256":"2ab3a43829efe8e6309e574bb63aee9440cfcac4c8e98eacf3b69c2d7f4aae56"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the preferred design of a Pseudowire\n Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS\n packet switched network, and the Pseudowire Associated Channel\n Header. The design of these fields is chosen so that an MPLS Label\n Switching Router performing MPLS payload inspection will not confuse\n a PWE3 payload with an IP payload.\n\n1. Introduction\n\n The standard MPLS encapsulations have no explicit protocol\n identifier. In order for a pseudowire (PW) [RFC3985] to operate\n correctly over an MPLS packet switched network (PSN) that performs\n MPLS payload inspection, a PW packet must not appear to a label\n switching router (LSR) as if it were an IP packet [BCP]. An example\n of an LSR that performs MPLS payload inspection is one that is\n performing equal-cost multiple-path load-balancing (ECMP) [RFC2992].\n If ECMP were performed on PW packets, the packets in ","scope_keywords":["4385","delivery","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4928","folder":"IETF/RFC-4928","source":"IETF/RFC-4928/RFC-4928.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 4385 This document describes the preferred design of a Pseudowire\n Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS\n packet switched network, and the Pseudowire Associated Channel\n Header. The design of these fields is chosen so that an MPLS Label\n Switching Router performing MPLS payload inspection will not confuse\n a PWE3 payload with an IP payload.\n\n1. Introduction\n\n The standard MPLS encapsulations have no explicit protocol\n identifier. In order for a pseudowire (PW) [RFC3985] to operate\n correctly over an MPLS packet switched network (PSN) that performs\n MPLS payload inspection, a PW packet must not appear to a label\n switching router (LSR) as if it were an IP packet [BCP]. An example\n of an LSR that performs MPLS payload inspection is one that is\n performing equal-cost multiple-path load-balancing (ECMP) [RFC2992].\n If ECMP were performed on PW packets, the packets in  4385 delivery key management path subject nested-reference unchanged"},{"id":"IETF RFC 4386","type":"specification","body":"IETF","designation":"RFC 4386","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4386.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4386.txt","https://www.rfc-editor.org/rfc/rfc4386.pdf"],"folder":"IETF/RFC-4386","files":{"txt":{"path":"standards/IETF/RFC-4386/RFC-4386.txt","sha256":"d83dd5cc5400c4ce9b832c8e821c4ca92df307908e3839822a3682175b54dd18"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Public Key Infrastructure (PKI) repository\n locator service. The service makes use of DNS SRV records defined in\n accordance with RFC 2782. The service enables certificate-using\n systems to locate PKI repositories.","scope_keywords":["4386","certificate","certificates","http","key","ocsp","pki","revocation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 4386 This document defines a Public Key Infrastructure (PKI) repository\n locator service. The service makes use of DNS SRV records defined in\n accordance with RFC 2782. The service enables certificate-using\n systems to locate PKI repositories. 4386 certificate certificates http key ocsp pki revocation trust nested-reference unchanged"},{"id":"IETF RFC 4387","type":"specification","body":"IETF","designation":"RFC 4387","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4387.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4387.txt","https://www.rfc-editor.org/rfc/rfc4387.pdf"],"folder":"IETF/RFC-4387","files":{"txt":{"path":"standards/IETF/RFC-4387/RFC-4387.txt","sha256":"9ccea21e19bb4076db1120bae3dcfed8605bbbb6e954fc107191b94cb58d7a4c"}},"tags":["nested-reference","unchanged"],"summary":"The protocol conventions described in this document satisfy some of\n the operational requirements of the Internet Public Key\n Infrastructure (PKI). This document specifies the conventions for\n using the Hypertext Transfer Protocol (HTTP/HTTPS) as an interface\n mechanism to obtain certificates and certificate revocation lists\n (CRLs) from PKI repositories. Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents.\n\nGutmann Standards Track [Page 1]\n\f\nRFC 4387 Certificate Store Access via HTTP February 2006","scope_keywords":["4387","attribute","certificate","certificates","crl","http","https","identification","key","keys","path","pki","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 4387 The protocol conventions described in this document satisfy some of\n the operational requirements of the Internet Public Key\n Infrastructure (PKI). This document specifies the conventions for\n using the Hypertext Transfer Protocol (HTTP/HTTPS) as an interface\n mechanism to obtain certificates and certificate revocation lists\n (CRLs) from PKI repositories. Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents.\n\nGutmann Standards Track [Page 1]\n\f\nRFC 4387 Certificate Store Access via HTTP February 2006 4387 attribute certificate certificates crl http https identification key keys path pki revocation nested-reference unchanged"},{"id":"IETF RFC 4395","type":"specification","body":"IETF","designation":"RFC 4395","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4395.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4395.txt","https://www.rfc-editor.org/rfc/rfc4395.pdf"],"folder":"IETF/RFC-4395","files":{"txt":{"path":"standards/IETF/RFC-4395/RFC-4395.txt","sha256":"36aa47a297912de447025414abb5c62558dc67059a82aaaa7d68be896b15eaec"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines and recommendations for the\n definition of Uniform Resource Identifier (URI) schemes. It also\n updates the process and IANA registry for URI schemes. It obsoletes\n both RFC 2717 and RFC 2718.\n\nHansen, et al. Best Current Practice [Page 1]\n\f\nRFC 4395 New URI Schemes February 2006","scope_keywords":["4395","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5781","folder":"IETF/RFC-5781","source":"IETF/RFC-5781/RFC-5781.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6694","folder":"IETF/RFC-6694","source":"IETF/RFC-6694/RFC-6694.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null}],"search_text":"IETF RFC 4395 This document provides guidelines and recommendations for the\n definition of Uniform Resource Identifier (URI) schemes. It also\n updates the process and IANA registry for URI schemes. It obsoletes\n both RFC 2717 and RFC 2718.\n\nHansen, et al. Best Current Practice [Page 1]\n\f\nRFC 4395 New URI Schemes February 2006 4395 key registered nested-reference unchanged"},{"id":"IETF RFC 4402","type":"specification","body":"IETF","designation":"RFC 4402","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4402.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4402.txt","https://www.rfc-editor.org/rfc/rfc4402.pdf"],"folder":"IETF/RFC-4402","files":{"txt":{"path":"standards/IETF/RFC-4402/RFC-4402.txt","sha256":"0533814ca0734adaffd44d0cb30c09856198ccb2eaa2e1e5e9019e8b7a6b8c5e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Pseudo-Random Function (PRF) for the\n Kerberos V mechanism for the Generic Security Service Application\n Program Interface (GSS-API), based on the PRF defined for the\n Kerberos V cryptographic framework, for keying application protocols\n given an established Kerberos V GSS-API security context.","scope_keywords":["4402","encryption","key","keys","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null}],"search_text":"IETF RFC 4402 This document defines the Pseudo-Random Function (PRF) for the\n Kerberos V mechanism for the Generic Security Service Application\n Program Interface (GSS-API), based on the PRF defined for the\n Kerberos V cryptographic framework, for keying application protocols\n given an established Kerberos V GSS-API security context. 4402 encryption key keys license subject nested-reference unchanged"},{"id":"IETF RFC 4405","type":"specification","body":"IETF","designation":"RFC 4405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4405.txt","https://www.rfc-editor.org/rfc/rfc4405.pdf"],"folder":"IETF/RFC-4405","files":{"txt":{"path":"standards/IETF/RFC-4405/RFC-4405.txt","sha256":"6789cf0fbb02cfc12d8b6ea7f3bd7fea858db83a938578a69934d1aa865526d3"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service that allows an SMTP client to specify the responsible\n submitter of an e-mail message. The responsible submitter is the\n e-mail address of the entity most recently responsible for\n introducing a message into the transport stream. This extension\n helps receiving e-mail servers efficiently determine whether the SMTP\n client is authorized to transmit mail on behalf of the responsible\n submitter's domain.","scope_keywords":["4405","delivery","identification","key","policy","risk","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null}],"search_text":"IETF RFC 4405 This memo defines an extension to the Simple Mail Transfer Protocol\n (SMTP) service that allows an SMTP client to specify the responsible\n submitter of an e-mail message. The responsible submitter is the\n e-mail address of the entity most recently responsible for\n introducing a message into the transport stream. This extension\n helps receiving e-mail servers efficiently determine whether the SMTP\n client is authorized to transmit mail on behalf of the responsible\n submitter's domain. 4405 delivery identification key policy risk validation nested-reference unchanged"},{"id":"IETF RFC 4406","type":"specification","body":"IETF","designation":"RFC 4406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4406.txt","https://www.rfc-editor.org/rfc/rfc4406.pdf"],"folder":"IETF/RFC-4406","files":{"txt":{"path":"standards/IETF/RFC-4406/RFC-4406.txt","sha256":"5eada957f4785310c2c0e107ef29f276045a08e0886368ae5432242341afc562"}},"tags":["nested-reference","unchanged"],"summary":"Internet mail suffers from the fact that much unwanted mail is sent\n using spoofed addresses -- \"spoofed\" in this case means that the\n address is used without the permission of the domain owner. This\n document describes a family of tests by which SMTP servers can\n determine whether an e-mail address in a received message was used\n with the permission of the owner of the domain contained in that\n e-mail address.\n\nLyon & Wong Experimental [Page 2]\n\f\nRFC 4406 Sender ID: Authenticating E-Mail April 2006","scope_keywords":["4406","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 6577","folder":"IETF/RFC-6577","source":"IETF/RFC-6577/RFC-6577.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 4406 Internet mail suffers from the fact that much unwanted mail is sent\n using spoofed addresses -- \"spoofed\" in this case means that the\n address is used without the permission of the domain owner. This\n document describes a family of tests by which SMTP servers can\n determine whether an e-mail address in a received message was used\n with the permission of the owner of the domain contained in that\n e-mail address.\n\nLyon & Wong Experimental [Page 2]\n\f\nRFC 4406 Sender ID: Authenticating E-Mail April 2006 4406 delivery path nested-reference unchanged"},{"id":"IETF RFC 4407","type":"specification","body":"IETF","designation":"RFC 4407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4407.txt","https://www.rfc-editor.org/rfc/rfc4407.pdf"],"folder":"IETF/RFC-4407","files":{"txt":{"path":"standards/IETF/RFC-4407/RFC-4407.txt","sha256":"894504edcc282e9224c270cf8f29fd1d4bf1063f86128212ff2ce5af922ee359"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an algorithm by which, given an e-mail message,\n one can extract the identity of the party that appears to have most\n proximately caused that message to be delivered. This identity is\n called the Purported Responsible Address (PRA).","scope_keywords":["4407","algorithm","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null},{"body":"IETF","designation":"RFC 6686","folder":"IETF/RFC-6686","source":"IETF/RFC-6686/RFC-6686.txt","version":null}],"search_text":"IETF RFC 4407 This document defines an algorithm by which, given an e-mail message,\n one can extract the identity of the party that appears to have most\n proximately caused that message to be delivered. This identity is\n called the Purported Responsible Address (PRA). 4407 algorithm key path nested-reference unchanged"},{"id":"IETF RFC 4410","type":"specification","body":"IETF","designation":"RFC 4410","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4410.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4410.txt","https://www.rfc-editor.org/rfc/rfc4410.pdf"],"folder":"IETF/RFC-4410","files":{"txt":{"path":"standards/IETF/RFC-4410/RFC-4410.txt","sha256":"ccf3a744102ae1fd331170c57e1f21ca1738d0572a447a8ad3fc5b80e2bc3f8e"}},"tags":["nested-reference","unchanged"],"summary":"The Selectively Reliable Multicast Protocol (SRMP) is a transport\n protocol, intended to deliver a mix of reliable and best-effort\n messages in an any-to-any multicast environment, where the best-\n effort traffic occurs in significantly greater volume than the\n reliable traffic and therefore can carry sequence numbers of reliable\n messages for loss detection. SRMP is intended for use in a\n distributed simulation application environment, where only the latest\n value of reliable transmission for any particular data identifier\n requires delivery. SRMP has two sublayers: a bundling sublayer\n handling message aggregation and congestion control, and a\n Selectively Reliable Transport (SRT) sublayer. Selection between\n reliable and best-effort messages is performed by the application.\n\nPullen, et al. Experimental [Page 1]\n\f\nRFC 4410 Selectively Reliable Multicast Protocol February 2006","scope_keywords":["4410","delivery","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 4410 The Selectively Reliable Multicast Protocol (SRMP) is a transport\n protocol, intended to deliver a mix of reliable and best-effort\n messages in an any-to-any multicast environment, where the best-\n effort traffic occurs in significantly greater volume than the\n reliable traffic and therefore can carry sequence numbers of reliable\n messages for loss detection. SRMP is intended for use in a\n distributed simulation application environment, where only the latest\n value of reliable transmission for any particular data identifier\n requires delivery. SRMP has two sublayers: a bundling sublayer\n handling message aggregation and congestion control, and a\n Selectively Reliable Transport (SRT) sublayer. Selection between\n reliable and best-effort messages is performed by the application.\n\nPullen, et al. Experimental [Page 1]\n\f\nRFC 4410 Selectively Reliable Multicast Protocol February 2006 4410 delivery identification key nested-reference unchanged"},{"id":"IETF RFC 4411","type":"specification","body":"IETF","designation":"RFC 4411","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4411.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4411.txt","https://www.rfc-editor.org/rfc/rfc4411.pdf"],"folder":"IETF/RFC-4411","files":{"txt":{"path":"standards/IETF/RFC-4411/RFC-4411.txt","sha256":"44147507e6edff58983ed2cc6adaf71810c1b92ed5e42efcca390685ab3e1351"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an IANA Registration extension to the Session\n Initiation Protocol (SIP) Reason Header to be included in a BYE\n Method Request as a result of a session preemption event, either at a\n user agent (UA), or somewhere in the network involving a\n reservation-based protocol such as the Resource ReSerVation Protocol\n (RSVP) or Next Steps in Signaling (NSIS). This document does not\n attempt to address routers failing in the packet path; instead, it\n addresses a deliberate tear down of a flow between UAs, and informs\n the terminated UA(s) with an indication of what occurred.\n\nPolk Standards Track [Page 1]\n\f\nRFC 4411 SIP Reason Header for Preemption Events February 2006","scope_keywords":["4411","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 4411 This document proposes an IANA Registration extension to the Session\n Initiation Protocol (SIP) Reason Header to be included in a BYE\n Method Request as a result of a session preemption event, either at a\n user agent (UA), or somewhere in the network involving a\n reservation-based protocol such as the Resource ReSerVation Protocol\n (RSVP) or Next Steps in Signaling (NSIS). This document does not\n attempt to address routers failing in the packet path; instead, it\n addresses a deliberate tear down of a flow between UAs, and informs\n the terminated UA(s) with an indication of what occurred.\n\nPolk Standards Track [Page 1]\n\f\nRFC 4411 SIP Reason Header for Preemption Events February 2006 4411 path policy nested-reference unchanged"},{"id":"IETF RFC 4412","type":"specification","body":"IETF","designation":"RFC 4412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4412.txt","https://www.rfc-editor.org/rfc/rfc4412.pdf"],"folder":"IETF/RFC-4412","files":{"txt":{"path":"standards/IETF/RFC-4412/RFC-4412.txt","sha256":"9ca020da261047ab68252dc60b03251bd0f608911f866c8c8b7a84a0c9064662"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new Session Initiation Protocol (SIP)\n header fields for communicating resource priority, namely,\n \"Resource-Priority\" and \"Accept-Resource-Priority\". The\n \"Resource-Priority\" header field can influence the behavior of SIP\n user agents (such as telephone gateways and IP telephones) and SIP\n proxies. It does not directly influence the forwarding behavior of\n IP routers.","scope_keywords":["4412","authentication","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 4412 This document defines two new Session Initiation Protocol (SIP)\n header fields for communicating resource priority, namely,\n \"Resource-Priority\" and \"Accept-Resource-Priority\". The\n \"Resource-Priority\" header field can influence the behavior of SIP\n user agents (such as telephone gateways and IP telephones) and SIP\n proxies. It does not directly influence the forwarding behavior of\n IP routers. 4412 authentication authorization nested-reference unchanged"},{"id":"IETF RFC 4419","type":"specification","body":"IETF","designation":"RFC 4419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4419.txt","https://www.rfc-editor.org/rfc/rfc4419.pdf"],"folder":"IETF/RFC-4419","files":{"txt":{"path":"standards/IETF/RFC-4419/RFC-4419.txt","sha256":"20b76eff3be0c2311636e03604b1ddb9d5368fadd75a39c0c831fa7e04da0ad6"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a new key exchange method for the Secure Shell\n (SSH) protocol. It allows the SSH server to propose new groups on\n which to perform the Diffie-Hellman key exchange to the client. The\n proposed groups need not be fixed and can change with time.\n\n1. Overview and Rationale\n\n SSH [RFC4251] is a very common protocol for secure remote login on\n the Internet. Currently, SSH performs the initial key exchange using\n the \"diffie-hellman-group1-sha1\" method [RFC4253]. This method\n prescribes a fixed group on which all operations are performed.\n\n The Diffie-Hellman key exchange provides a shared secret that cannot\n be determined by either party alone. Furthermore, the shared secret\n is known only to the participant parties. In SSH, the key exchange\n is signed with the host key to provide host authentication.\n\n The security of the Diffie-Hellman key exchange is based on the\n diffi","scope_keywords":["4419","algorithm","algorithms","authentication","certificate","certificates","hash","hashing","key","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null}],"search_text":"IETF RFC 4419 This memo describes a new key exchange method for the Secure Shell\n (SSH) protocol. It allows the SSH server to propose new groups on\n which to perform the Diffie-Hellman key exchange to the client. The\n proposed groups need not be fixed and can change with time.\n\n1. Overview and Rationale\n\n SSH [RFC4251] is a very common protocol for secure remote login on\n the Internet. Currently, SSH performs the initial key exchange using\n the \"diffie-hellman-group1-sha1\" method [RFC4253]. This method\n prescribes a fixed group on which all operations are performed.\n\n The Diffie-Hellman key exchange provides a shared secret that cannot\n be determined by either party alone. Furthermore, the shared secret\n is known only to the participant parties. In SSH, the key exchange\n is signed with the host key to provide host authentication.\n\n The security of the Diffie-Hellman key exchange is based on the\n diffi 4419 algorithm algorithms authentication certificate certificates hash hashing key signature nested-reference unchanged"},{"id":"IETF RFC 4420","type":"specification","body":"IETF","designation":"RFC 4420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4420.txt","https://www.rfc-editor.org/rfc/rfc4420.pdf"],"folder":"IETF/RFC-4420","files":{"txt":{"path":"standards/IETF/RFC-4420/RFC-4420.txt","sha256":"22e429b74415ce9941aca40af951bacfa6372e4593c3a83ff0d7762c34fddd27"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may\n be established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions. This protocol includes an object\n (the SESSION_ATTRIBUTE object) that carries a Flags field used to\n indicate options and attributes of the LSP. That Flags field has\n eight bits allowing for eight options to be set. Recent proposals in\n many documents that extend RSVP-TE have suggested uses for each of\n the previously unused bits.\n\n This document defines a new object for RSVP-TE messages that allows\n the signaling of further attribute bits and also the carriage of\n arbitrary attribute parameters to make RSVP-TE easily extensible to\n support new requirements. Additionally, this document defines a way\n to record the attributes applied to the LSP on a hop-by-hop basis.\n\n The object mechanisms defined in this document are equa","scope_keywords":["4420","attribute","attributes","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5420","folder":"IETF/RFC-5420","source":"IETF/RFC-5420/RFC-5420.txt","version":null}],"search_text":"IETF RFC 4420 Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may\n be established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions. This protocol includes an object\n (the SESSION_ATTRIBUTE object) that carries a Flags field used to\n indicate options and attributes of the LSP. That Flags field has\n eight bits allowing for eight options to be set. Recent proposals in\n many documents that extend RSVP-TE have suggested uses for each of\n the previously unused bits.\n\n This document defines a new object for RSVP-TE messages that allows\n the signaling of further attribute bits and also the carriage of\n arbitrary attribute parameters to make RSVP-TE easily extensible to\n support new requirements. Additionally, this document defines a way\n to record the attributes applied to the LSP on a hop-by-hop basis.\n\n The object mechanisms defined in this document are equa 4420 attribute attributes key path nested-reference unchanged"},{"id":"IETF RFC 4422","type":"specification","body":"IETF","designation":"RFC 4422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4422.txt","https://www.rfc-editor.org/rfc/rfc4422.pdf"],"folder":"IETF/RFC-4422","files":{"txt":{"path":"standards/IETF/RFC-4422/RFC-4422.txt","sha256":"69fbd4a501645d049dac3cac0544179d3d4cd3b13039f565768cd2f1d5978c42"}},"tags":["nested-reference","unchanged"],"summary":"The Simple Authentication and Security Layer (SASL) is a framework\n for providing authentication and data security services in\n connection-oriented protocols via replaceable mechanisms. It\n provides a structured interface between protocols and mechanisms.\n The resulting framework allows new protocols to reuse existing\n mechanisms and allows old protocols to make use of new mechanisms.\n The framework also provides a protocol for securing subsequent\n protocol exchanges within a data security layer.\n\n This document describes how a SASL mechanism is structured, describes\n how protocols include support for SASL, and defines the protocol for\n carrying a data security layer over a connection. In addition, this\n document defines one SASL mechanism, the EXTERNAL mechanism.\n\n This document obsoletes RFC 2222.\n\nMelnikov & Zeilenga Standards Track [Page 1]\n\f\nRFC 4422 SASL June 2006","scope_keywords":["4422","authentication","authorization","certificate","certificates","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4422 The Simple Authentication and Security Layer (SASL) is a framework\n for providing authentication and data security services in\n connection-oriented protocols via replaceable mechanisms. It\n provides a structured interface between protocols and mechanisms.\n The resulting framework allows new protocols to reuse existing\n mechanisms and allows old protocols to make use of new mechanisms.\n The framework also provides a protocol for securing subsequent\n protocol exchanges within a data security layer.\n\n This document describes how a SASL mechanism is structured, describes\n how protocols include support for SASL, and defines the protocol for\n carrying a data security layer over a connection. In addition, this\n document defines one SASL mechanism, the EXTERNAL mechanism.\n\n This document obsoletes RFC 2222.\n\nMelnikov & Zeilenga Standards Track [Page 1]\n\f\nRFC 4422 SASL June 2006 4422 authentication authorization certificate certificates key nested-reference unchanged"},{"id":"IETF RFC 4426","type":"specification","body":"IETF","designation":"RFC 4426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4426.txt","https://www.rfc-editor.org/rfc/rfc4426.pdf"],"folder":"IETF/RFC-4426","files":{"txt":{"path":"standards/IETF/RFC-4426/RFC-4426.txt","sha256":"26aa7c2ed08fdd73c445c7baa00b340ee47a984184dd2504de293113d90243b8"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a functional description of the protocol\n extensions needed to support Generalized Multi-Protocol Label\n Switching (GMPLS)-based recovery (i.e., protection and restoration).\n Protocol specific formats and mechanisms will be described in\n companion documents.","scope_keywords":["4426","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4427","folder":"IETF/RFC-4427","source":"IETF/RFC-4427/RFC-4427.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4426 This document presents a functional description of the protocol\n extensions needed to support Generalized Multi-Protocol Label\n Switching (GMPLS)-based recovery (i.e., protection and restoration).\n Protocol specific formats and mechanisms will be described in\n companion documents. 4426 key management path subject nested-reference unchanged"},{"id":"IETF RFC 4427","type":"specification","body":"IETF","designation":"RFC 4427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4427.txt","https://www.rfc-editor.org/rfc/rfc4427.pdf"],"folder":"IETF/RFC-4427","files":{"txt":{"path":"standards/IETF/RFC-4427/RFC-4427.txt","sha256":"d0e6fc9507019b0f2e6b4c21f8b7d08955385872e246f56321ae91c1240f5fc3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a common terminology for Generalized Multi-\n Protocol Label Switching (GMPLS)-based recovery mechanisms (i.e.,\n protection and restoration). The terminology is independent of the\n underlying transport technologies covered by GMPLS.\n\nMannie & Papadimitriou Informational [Page 1]\n\f\nRFC 4427 GMPLS Recovery Terminology March 2006","scope_keywords":["4427","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4426","folder":"IETF/RFC-4426","source":"IETF/RFC-4426/RFC-4426.txt","version":null},{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4427 This document defines a common terminology for Generalized Multi-\n Protocol Label Switching (GMPLS)-based recovery mechanisms (i.e.,\n protection and restoration). The terminology is independent of the\n underlying transport technologies covered by GMPLS.\n\nMannie & Papadimitriou Informational [Page 1]\n\f\nRFC 4427 GMPLS Recovery Terminology March 2006 4427 path nested-reference unchanged"},{"id":"IETF RFC 4428","type":"specification","body":"IETF","designation":"RFC 4428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4428.txt","https://www.rfc-editor.org/rfc/rfc4428.pdf"],"folder":"IETF/RFC-4428","files":{"txt":{"path":"standards/IETF/RFC-4428/RFC-4428.txt","sha256":"174ebbf912a59690ff19a46232a84bcb5680687b830c83fb9280b27ca48f89a1"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an analysis grid to evaluate, compare, and\n contrast the Generalized Multi-Protocol Label Switching (GMPLS)\n protocol suite capabilities with the recovery mechanisms currently\n proposed at the IETF CCAMP Working Group. A detailed analysis of\n each of the recovery phases is provided using the terminology defined\n in RFC 4427. This document focuses on transport plane survivability\n and recovery issues and not on control plane resilience and related\n aspects.","scope_keywords":["4428","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4427","folder":"IETF/RFC-4427","source":"IETF/RFC-4427/RFC-4427.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4428 This document provides an analysis grid to evaluate, compare, and\n contrast the Generalized Multi-Protocol Label Switching (GMPLS)\n protocol suite capabilities with the recovery mechanisms currently\n proposed at the IETF CCAMP Working Group. A detailed analysis of\n each of the recovery phases is provided using the terminology defined\n in RFC 4427. This document focuses on transport plane survivability\n and recovery issues and not on control plane resilience and related\n aspects. 4428 management nested-reference unchanged"},{"id":"IETF RFC 4429","type":"specification","body":"IETF","designation":"RFC 4429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4429.txt","https://www.rfc-editor.org/rfc/rfc4429.pdf"],"folder":"IETF/RFC-4429","files":{"txt":{"path":"standards/IETF/RFC-4429/RFC-4429.txt","sha256":"1d31fed69006e288f58aa4a291bf986d46379ddd7d85a6c4885f0f39ab3e8ba5"}},"tags":["nested-reference","unchanged"],"summary":"Optimistic Duplicate Address Detection is an interoperable\n modification of the existing IPv6 Neighbor Discovery (RFC 2461) and\n Stateless Address Autoconfiguration (RFC 2462) processes. The\n intention is to minimize address configuration delays in the\n successful case, to reduce disruption as far as possible in the\n failure case, and to remain interoperable with unmodified hosts and\n routers.\n\nMoore Standards Track [Page 1]\n\f\nRFC 4429 Optimistic DAD April 2006","scope_keywords":["4429","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null}],"search_text":"IETF RFC 4429 Optimistic Duplicate Address Detection is an interoperable\n modification of the existing IPv6 Neighbor Discovery (RFC 2461) and\n Stateless Address Autoconfiguration (RFC 2462) processes. The\n intention is to minimize address configuration delays in the\n successful case, to reduce disruption as far as possible in the\n failure case, and to remain interoperable with unmodified hosts and\n routers.\n\nMoore Standards Track [Page 1]\n\f\nRFC 4429 Optimistic DAD April 2006 4429 key path subject nested-reference unchanged"},{"id":"IETF RFC 4437","type":"specification","body":"IETF","designation":"RFC 4437","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4437.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4437.txt","https://www.rfc-editor.org/rfc/rfc4437.pdf"],"folder":"IETF/RFC-4437","files":{"txt":{"path":"standards/IETF/RFC-4437/RFC-4437.txt","sha256":"e594babf7f916500c531575c86b62507e248dbe71d9edd91fe29ce23637d606c"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to Web Distributed Authoring\n and Versioning (WebDAV) to allow clients to author HTTP redirect\n reference resources whose default response is an HTTP/1.1 3xx\n (Redirection) status code. A redirect reference makes it possible to\n access the target resourced indirectly through any URI mapped to the\n redirect reference resource. This specification does not address\n remapping of trees of resources or regular expression based\n redirections. There are no integrity guarantees associated with\n redirect reference resources. Other mechanisms can also be used to\n achieve the same functionality as this specification. This\n specification allows operators to experiment with this mechanism and\n develop experience on what is the best approach to the problem.","scope_keywords":["4437","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null}],"search_text":"IETF RFC 4437 This specification defines an extension to Web Distributed Authoring\n and Versioning (WebDAV) to allow clients to author HTTP redirect\n reference resources whose default response is an HTTP/1.1 3xx\n (Redirection) status code. A redirect reference makes it possible to\n access the target resourced indirectly through any URI mapped to the\n redirect reference resource. This specification does not address\n remapping of trees of resources or regular expression based\n redirections. There are no integrity guarantees associated with\n redirect reference resources. Other mechanisms can also be used to\n achieve the same functionality as this specification. This\n specification allows operators to experiment with this mechanism and\n develop experience on what is the best approach to the problem. 4437 http path nested-reference unchanged"},{"id":"IETF RFC 4446","type":"specification","body":"IETF","designation":"RFC 4446","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4446.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4446.txt","https://www.rfc-editor.org/rfc/rfc4446.pdf"],"folder":"IETF/RFC-4446","files":{"txt":{"path":"standards/IETF/RFC-4446/RFC-4446.txt","sha256":"5e9c655094ebf8caf9e3b6dd9eefac4a23cc46a369d826ba6c28ffd2dec52cab"}},"tags":["nested-reference","unchanged"],"summary":"This document allocates the fixed pseudowire identifier and other\n fixed protocol values for protocols that have been defined in the\n Pseudo Wire Edge to Edge (PWE3) working group. Detailed IANA\n allocation instructions are also included in this document.","scope_keywords":["4446","key","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4447","folder":"IETF/RFC-4447","source":"IETF/RFC-4447/RFC-4447.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4667","folder":"IETF/RFC-4667","source":"IETF/RFC-4667/RFC-4667.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4863","folder":"IETF/RFC-4863","source":"IETF/RFC-4863/RFC-4863.txt","version":null},{"body":"IETF","designation":"RFC 5003","folder":"IETF/RFC-5003","source":"IETF/RFC-5003/RFC-5003.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4446 This document allocates the fixed pseudowire identifier and other\n fixed protocol values for protocols that have been defined in the\n Pseudo Wire Edge to Edge (PWE3) working group. Detailed IANA\n allocation instructions are also included in this document. 4446 key policy registered nested-reference unchanged"},{"id":"IETF RFC 4447","type":"specification","body":"IETF","designation":"RFC 4447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4447.txt","https://www.rfc-editor.org/rfc/rfc4447.pdf"],"folder":"IETF/RFC-4447","files":{"txt":{"path":"standards/IETF/RFC-4447/RFC-4447.txt","sha256":"42212795d533410a29f6364af8288718dc690413944dc4e209c981d4bac83e77"}},"tags":["nested-reference","unchanged"],"summary":"Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode,\n and Ethernet) can be \"emulated\" over an MPLS backbone by\n encapsulating the Layer 2 Protocol Data Units (PDU) and transmitting\n them over \"pseudowires\". It is also possible to use pseudowires to\n provide low-rate Time Division Multiplexed and a Synchronous Optical\n NETworking circuit emulation over an MPLS-enabled network. This\n document specifies a protocol for establishing and maintaining the\n pseudowires, using extensions to Label Distribution Protocol (LDP).\n Procedures for encapsulating Layer 2 PDUs are specified in a set of\n companion documents.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4447 PWE3 Using LDP April 2006","scope_keywords":["4447","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4446","folder":"IETF/RFC-4446","source":"IETF/RFC-4446/RFC-4446.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 4863","folder":"IETF/RFC-4863","source":"IETF/RFC-4863/RFC-4863.txt","version":null},{"body":"IETF","designation":"RFC 5003","folder":"IETF/RFC-5003","source":"IETF/RFC-5003/RFC-5003.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5542","folder":"IETF/RFC-5542","source":"IETF/RFC-5542/RFC-5542.txt","version":null},{"body":"IETF","designation":"RFC 5561","folder":"IETF/RFC-5561","source":"IETF/RFC-5561/RFC-5561.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null}],"search_text":"IETF RFC 4447 Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode,\n and Ethernet) can be \"emulated\" over an MPLS backbone by\n encapsulating the Layer 2 Protocol Data Units (PDU) and transmitting\n them over \"pseudowires\". It is also possible to use pseudowires to\n provide low-rate Time Division Multiplexed and a Synchronous Optical\n NETworking circuit emulation over an MPLS-enabled network. This\n document specifies a protocol for establishing and maintaining the\n pseudowires, using extensions to Label Distribution Protocol (LDP).\n Procedures for encapsulating Layer 2 PDUs are specified in a set of\n companion documents.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4447 PWE3 Using LDP April 2006 4447 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 4449","type":"specification","body":"IETF","designation":"RFC 4449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4449.txt","https://www.rfc-editor.org/rfc/rfc4449.pdf"],"folder":"IETF/RFC-4449","files":{"txt":{"path":"standards/IETF/RFC-4449/RFC-4449.txt","sha256":"e8a3b0658595881d690d3fe7b1e731e940b04df336bad90809a407d130224e8f"}},"tags":["nested-reference","unchanged"],"summary":"A mobile node and a correspondent node may preconfigure data useful\n for precomputing a Binding Management Key that can subsequently be\n used for authorizing Binding Updates.","scope_keywords":["4449","authentication","authorization","key","keys","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null}],"search_text":"IETF RFC 4449 A mobile node and a correspondent node may preconfigure data useful\n for precomputing a Binding Management Key that can subsequently be\n used for authorizing Binding Updates. 4449 authentication authorization key keys management trust nested-reference unchanged"},{"id":"IETF RFC 4454","type":"specification","body":"IETF","designation":"RFC 4454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4454.txt","https://www.rfc-editor.org/rfc/rfc4454.pdf"],"folder":"IETF/RFC-4454","files":{"txt":{"path":"standards/IETF/RFC-4454/RFC-4454.txt","sha256":"dbe9d8d60e5a208d52fd3561c9dc3c3114982ce497d7cbecb57aa7c8bc5b1771"}},"tags":["nested-reference","unchanged"],"summary":"The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines an\n extensible tunneling protocol to transport layer 2 services over IP\n networks. This document describes the specifics of how to use the\n L2TP control plane for Asynchronous Transfer Mode (ATM) Pseudowires\n and provides guidelines for transporting various ATM services over an\n IP network.","scope_keywords":["4454","attribute","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 4454 The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines an\n extensible tunneling protocol to transport layer 2 services over IP\n networks. This document describes the specifics of how to use the\n L2TP control plane for Asynchronous Transfer Mode (ATM) Pseudowires\n and provides guidelines for transporting various ATM services over an\n IP network. 4454 attribute key path nested-reference unchanged"},{"id":"IETF RFC 4461","type":"specification","body":"IETF","designation":"RFC 4461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4461.txt","https://www.rfc-editor.org/rfc/rfc4461.pdf"],"folder":"IETF/RFC-4461","files":{"txt":{"path":"standards/IETF/RFC-4461/RFC-4461.txt","sha256":"d3fa578d5071c434a85c521de858bd4249aa49db2f6a2aca0e414fa4a7bf4b92"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of requirements for the establishment\n and maintenance of Point-to-Multipoint (P2MP) Traffic-Engineered (TE)\n Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs).\n\n There is no intent to specify solution-specific details or\n application-specific requirements in this document.\n\n The requirements presented in this document not only apply to\n packet-switched networks under the control of MPLS protocols, but\n also encompass the requirements of Layer Two Switching (L2SC), Time\n Division Multiplexing (TDM), lambda, and port switching networks\n managed by Generalized MPLS (GMPLS) protocols. Protocol solutions\n developed to meet the requirements set out in this document must\n attempt to be equally applicable to MPLS and GMPLS.\n\nYasukawa Informational [Page 1]\n\f\nRFC 4461 Signaling Requirements for P2MP TE MPLS LSPs April 2006","scope_keywords":["4461","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4687","folder":"IETF/RFC-4687","source":"IETF/RFC-4687/RFC-4687.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 4461 This document presents a set of requirements for the establishment\n and maintenance of Point-to-Multipoint (P2MP) Traffic-Engineered (TE)\n Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs).\n\n There is no intent to specify solution-specific details or\n application-specific requirements in this document.\n\n The requirements presented in this document not only apply to\n packet-switched networks under the control of MPLS protocols, but\n also encompass the requirements of Layer Two Switching (L2SC), Time\n Division Multiplexing (TDM), lambda, and port switching networks\n managed by Generalized MPLS (GMPLS) protocols. Protocol solutions\n developed to meet the requirements set out in this document must\n attempt to be equally applicable to MPLS and GMPLS.\n\nYasukawa Informational [Page 1]\n\f\nRFC 4461 Signaling Requirements for P2MP TE MPLS LSPs April 2006 4461 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 4470","type":"specification","body":"IETF","designation":"RFC 4470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4470.txt","https://www.rfc-editor.org/rfc/rfc4470.pdf"],"folder":"IETF/RFC-4470","files":{"txt":{"path":"standards/IETF/RFC-4470/RFC-4470.txt","sha256":"63a27bd5412a2cd3be8d576092f3f5e417ec5c351a0cfcdab51fee23882823e3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to construct DNSSEC NSEC resource records\n that cover a smaller range of names than called for by RFC 4034. By\n generating and signing these records on demand, authoritative name\n servers can effectively stop the disclosure of zone contents\n otherwise made possible by walking the chain of NSEC records in a\n signed zone.","scope_keywords":["4470","key","keys","policies","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null},{"body":"IETF","designation":"RFC 7129","folder":"IETF/RFC-7129","source":"IETF/RFC-7129/RFC-7129.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 4470 This document describes how to construct DNSSEC NSEC resource records\n that cover a smaller range of names than called for by RFC 4034. By\n generating and signing these records on demand, authoritative name\n servers can effectively stop the disclosure of zone contents\n otherwise made possible by walking the chain of NSEC records in a\n signed zone. 4470 key keys policies risk nested-reference unchanged"},{"id":"IETF RFC 4474","type":"specification","body":"IETF","designation":"RFC 4474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4474.txt","https://www.rfc-editor.org/rfc/rfc4474.pdf"],"folder":"IETF/RFC-4474","files":{"txt":{"path":"standards/IETF/RFC-4474/RFC-4474.txt","sha256":"0db58bad07dde0a03d009e819e4e35e497b55ace5d9c8a42a0cba73db7235d11"}},"tags":["nested-reference","unchanged"],"summary":"The existing security mechanisms in the Session Initiation Protocol\n (SIP) are inadequate for cryptographically assuring the identity of\n the end users that originate SIP requests, especially in an\n interdomain context. This document defines a mechanism for securely\n identifying originators of SIP messages. It does so by defining two\n new SIP header fields, Identity, for conveying a signature used for\n validating the identity, and Identity-Info, for conveying a reference\n to the certificate of the signer.\n\nPeterson & Jennings Standards Track [Page 1]\n\f\nRFC 4474 SIP Identity August 2006","scope_keywords":["4474","algorithm","authentication","authorization","certificate","certificates","key","management","policies","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4662","folder":"IETF/RFC-4662","source":"IETF/RFC-4662/RFC-4662.txt","version":null},{"body":"IETF","designation":"RFC 4916","folder":"IETF/RFC-4916","source":"IETF/RFC-4916/RFC-4916.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null}],"search_text":"IETF RFC 4474 The existing security mechanisms in the Session Initiation Protocol\n (SIP) are inadequate for cryptographically assuring the identity of\n the end users that originate SIP requests, especially in an\n interdomain context. This document defines a mechanism for securely\n identifying originators of SIP messages. It does so by defining two\n new SIP header fields, Identity, for conveying a signature used for\n validating the identity, and Identity-Info, for conveying a reference\n to the certificate of the signer.\n\nPeterson & Jennings Standards Track [Page 1]\n\f\nRFC 4474 SIP Identity August 2006 4474 algorithm authentication authorization certificate certificates key management policies signature tls nested-reference unchanged"},{"id":"IETF RFC 4478","type":"specification","body":"IETF","designation":"RFC 4478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4478.txt","https://www.rfc-editor.org/rfc/rfc4478.pdf"],"folder":"IETF/RFC-4478","files":{"txt":{"path":"standards/IETF/RFC-4478/RFC-4478.txt","sha256":"ff0322f3c4cc94c7d790ab0ee05fa3549ba2382be1504303e03950077dd671fe"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Y. Nir\nRequest for Comments: 4478 Check Point\nCategory: Experimental April 2006\n\n Repeated Authentication in Internet Key Exchange (IKEv2) Protocol\n\nStatus of This Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document extends the Internet Key Exchange (IKEv2) Protocol\n document [IKEv2]. With some IPsec peers, particularly in the remote\n access scenario, it is desirable to repeat the mutual authentication\n periodically. The purpose of this is to limit the time that security\n associations (SAs) can be used by a third party who has gained\n control of the IPsec peer. This document describes a mechanism to\n ","scope_keywords":["4478","authentication","credential","credentials","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4478 Network Working Group Y. Nir\nRequest for Comments: 4478 Check Point\nCategory: Experimental April 2006\n\n Repeated Authentication in Internet Key Exchange (IKEv2) Protocol\n\nStatus of This Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. It does not specify an Internet standard of any kind.\n Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document extends the Internet Key Exchange (IKEv2) Protocol\n document [IKEv2]. With some IPsec peers, particularly in the remote\n access scenario, it is desirable to repeat the mutual authentication\n periodically. The purpose of this is to limit the time that security\n associations (SAs) can be used by a third party who has gained\n control of the IPsec peer. This document describes a mechanism to\n  4478 authentication credential credentials key policy nested-reference unchanged"},{"id":"IETF RFC 4479","type":"specification","body":"IETF","designation":"RFC 4479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4479.txt","https://www.rfc-editor.org/rfc/rfc4479.pdf"],"folder":"IETF/RFC-4479","files":{"txt":{"path":"standards/IETF/RFC-4479/RFC-4479.txt","sha256":"6979a23ecd0c49d9e7f7d10567a22cd4dbaaf138ded29488644f34cadbee207b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the underlying presence data model used by\n Session Initiation Protocol (SIP) for Instant Messaging and Presence\n Leveraging Extensions (SIMPLE) presence agents. The data model\n provides guidance on how to map various communications systems into\n presence documents in a consistent fashion.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4479 Presence Data Model July 2006","scope_keywords":["4479","attribute","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null}],"search_text":"IETF RFC 4479 This document defines the underlying presence data model used by\n Session Initiation Protocol (SIP) for Instant Messaging and Presence\n Leveraging Extensions (SIMPLE) presence agents. The data model\n provides guidance on how to map various communications systems into\n presence documents in a consistent fashion.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4479 Presence Data Model July 2006 4479 attribute key pid nested-reference unchanged"},{"id":"IETF RFC 4480","type":"specification","body":"IETF","designation":"RFC 4480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4480.txt","https://www.rfc-editor.org/rfc/rfc4480.pdf"],"folder":"IETF/RFC-4480","files":{"txt":{"path":"standards/IETF/RFC-4480/RFC-4480.txt","sha256":"00ea72e086cba1e3363125da897c6fa1d654da1eead7299511decc345e9d5182"}},"tags":["nested-reference","unchanged"],"summary":"The Presence Information Data Format (PIDF) defines a basic format\n for representing presence information for a presentity. This format\n defines a textual note, an indication of availability (open or\n closed) and a Uniform Resource Identifier (URI) for communication.\n The Rich Presence Information Data format (RPID) described here is an\n extension that adds optional elements to the Presence Information\n Data Format (PIDF). These extensions provide additional information\n about the presentity and its contacts. The information is designed\n so that much of it can be derived automatically, e.g., from calendar\n files or user activity.\n\n This extension includes information about what the person is doing, a\n grouping identifier for a tuple, when a service or device was last\n used, the type of place a person is in, what media communications\n might remain private, the relationship of a service tu","scope_keywords":["4480","attribute","attributes","pid","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4745","folder":"IETF/RFC-4745","source":"IETF/RFC-4745/RFC-4745.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null}],"search_text":"IETF RFC 4480 The Presence Information Data Format (PIDF) defines a basic format\n for representing presence information for a presentity. This format\n defines a textual note, an indication of availability (open or\n closed) and a Uniform Resource Identifier (URI) for communication.\n The Rich Presence Information Data format (RPID) described here is an\n extension that adds optional elements to the Presence Information\n Data Format (PIDF). These extensions provide additional information\n about the presentity and its contacts. The information is designed\n so that much of it can be derived automatically, e.g., from calendar\n files or user activity.\n\n This extension includes information about what the person is doing, a\n grouping identifier for a tuple, when a service or device was last\n used, the type of place a person is in, what media communications\n might remain private, the relationship of a service tu 4480 attribute attributes pid profile nested-reference unchanged"},{"id":"IETF RFC 4481","type":"specification","body":"IETF","designation":"RFC 4481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4481.txt","https://www.rfc-editor.org/rfc/rfc4481.pdf"],"folder":"IETF/RFC-4481","files":{"txt":{"path":"standards/IETF/RFC-4481/RFC-4481.txt","sha256":"3b7f87f162aa662d387acf730abe9beb2888e93c842b77d400e743ba8efe110c"}},"tags":["nested-reference","unchanged"],"summary":"The Presence Information Data Format (PIDF) defines a basic XML\n format for presenting presence information for a presentity. This\n document extends PIDF, adding a timed status extension\n (<timed-status> element) that allows a presentity to declare its\n status for a time interval fully in the future or the past.","scope_keywords":["4481","attribute","attributes","key","pid","qualified","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null}],"search_text":"IETF RFC 4481 The Presence Information Data Format (PIDF) defines a basic XML\n format for presenting presence information for a presentity. This\n document extends PIDF, adding a timed status extension\n (<timed-status> element) that allows a presentity to declare its\n status for a time interval fully in the future or the past. 4481 attribute attributes key pid qualified timestamp nested-reference unchanged"},{"id":"IETF RFC 4482","type":"specification","body":"IETF","designation":"RFC 4482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4482.txt","https://www.rfc-editor.org/rfc/rfc4482.pdf"],"folder":"IETF/RFC-4482","files":{"txt":{"path":"standards/IETF/RFC-4482/RFC-4482.txt","sha256":"1cad4edb51ccfcab7eb2762a3288f6a9da1510945878830374e7d0c7c013831a"}},"tags":["nested-reference","unchanged"],"summary":"The Presence Information Data Format (PIDF) defines a basic XML\n format for presenting presence information for a presentity. The\n Contact Information for the Presence Information Data format (CIPID)\n is an extension that adds elements to PIDF that provide additional\n contact information about a presentity and its contacts, including\n references to address book entries and icons.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 4482 CIPID July 2006","scope_keywords":["4482","attribute","attributes","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null}],"search_text":"IETF RFC 4482 The Presence Information Data Format (PIDF) defines a basic XML\n format for presenting presence information for a presentity. The\n Contact Information for the Presence Information Data format (CIPID)\n is an extension that adds elements to PIDF that provide additional\n contact information about a presentity and its contacts, including\n references to address book entries and icons.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 4482 CIPID July 2006 4482 attribute attributes key pid nested-reference unchanged"},{"id":"IETF RFC 4485","type":"specification","body":"IETF","designation":"RFC 4485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4485.txt","https://www.rfc-editor.org/rfc/rfc4485.pdf"],"folder":"IETF/RFC-4485","files":{"txt":{"path":"standards/IETF/RFC-4485/RFC-4485.txt","sha256":"3b6ab1692b2ea2c761a3a266614c19d1bf1a24260083cc2ca7dd3a36c2088c22"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) is a flexible yet simple tool\n for establishing interactive communications sessions across the\n Internet. Part of this flexibility is the ease with which it can be\n extended. In order to facilitate effective and interoperable\n extensions to SIP, some guidelines need to be followed when\n developing SIP extensions. This document outlines a set of such\n guidelines for authors of SIP extensions.\n\nRosenberg & Schulzrinne Informational [Page 1]\n\f\nRFC 4485 SIP Guidelines May 2006","scope_keywords":["4485","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 4485 The Session Initiation Protocol (SIP) is a flexible yet simple tool\n for establishing interactive communications sessions across the\n Internet. Part of this flexibility is the ease with which it can be\n extended. In order to facilitate effective and interoperable\n extensions to SIP, some guidelines need to be followed when\n developing SIP extensions. This document outlines a set of such\n guidelines for authors of SIP extensions.\n\nRosenberg & Schulzrinne Informational [Page 1]\n\f\nRFC 4485 SIP Guidelines May 2006 4485 key management path nested-reference unchanged"},{"id":"IETF RFC 4488","type":"specification","body":"IETF","designation":"RFC 4488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4488.txt","https://www.rfc-editor.org/rfc/rfc4488.pdf"],"folder":"IETF/RFC-4488","files":{"txt":{"path":"standards/IETF/RFC-4488/RFC-4488.txt","sha256":"df34e77ad2a579b46faec66942b08e90051fbcb279a43ef47fc826653c9ce655"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) REFER extension as defined in\n RFC 3515 automatically establishes a typically short-lived event\n subscription used to notify the party sending a REFER request about\n the receiver's status in executing the transaction requested by the\n REFER. These notifications are not needed in all cases. This\n specification provides a way to prevent the automatic establishment\n of an event subscription and subsequent notifications using a new SIP\n extension header field that may be included in a REFER request.","scope_keywords":["4488","encryption","issuer","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null}],"search_text":"IETF RFC 4488 The Session Initiation Protocol (SIP) REFER extension as defined in\n RFC 3515 automatically establishes a typically short-lived event\n subscription used to notify the party sending a REFER request about\n the receiver's status in executing the transaction requested by the\n REFER. These notifications are not needed in all cases. This\n specification provides a way to prevent the automatic establishment\n of an event subscription and subsequent notifications using a new SIP\n extension header field that may be included in a REFER request. 4488 encryption issuer key nested-reference unchanged"},{"id":"IETF RFC 4489","type":"specification","body":"IETF","designation":"RFC 4489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4489.txt","https://www.rfc-editor.org/rfc/rfc4489.pdf"],"folder":"IETF/RFC-4489","files":{"txt":{"path":"standards/IETF/RFC-4489/RFC-4489.txt","sha256":"1497227304e63b5822cad8604e09ec003a4357f2efad579155be9522335a0dca"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the multicast addressing\n architecture of the IPv6 protocol. The extension allows the use of\n Interface Identifiers (IIDs) to allocate multicast addresses. When a\n link-local unicast address is configured at each interface of a node,\n an IID is uniquely determined. After that, each node can generate\n its unique multicast addresses automatically without conflicts. The\n alternative method for creating link-local multicast addresses\n proposed in this document is better than known methods like unicast-\n prefix-based IPv6 multicast addresses. This memo updates RFC 3306.","scope_keywords":["4489","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null}],"search_text":"IETF RFC 4489 This document specifies an extension to the multicast addressing\n architecture of the IPv6 protocol. The extension allows the use of\n Interface Identifiers (IIDs) to allocate multicast addresses. When a\n link-local unicast address is configured at each interface of a node,\n an IID is uniquely determined. After that, each node can generate\n its unique multicast addresses automatically without conflicts. The\n alternative method for creating link-local multicast addresses\n proposed in this document is better than known methods like unicast-\n prefix-based IPv6 multicast addresses. This memo updates RFC 3306. 4489 key nested-reference unchanged"},{"id":"IETF RFC 4490","type":"specification","body":"IETF","designation":"RFC 4490","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4490.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4490.txt","https://www.rfc-editor.org/rfc/rfc4490.pdf"],"folder":"IETF/RFC-4490","files":{"txt":{"path":"standards/IETF/RFC-4490/RFC-4490.txt","sha256":"c1391aca412ec468dd584196f0ba8e7f0ccdbaf49e3a83b7d76ebd304f5c8f45"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the cryptographic\n algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and\n GOST R 34.11-94 with the Cryptographic Message Syntax (CMS). The CMS\n is used for digital signature, digest, authentication, and encryption\n of arbitrary message contents.\n\nLeontiev & Chudov Standards Track [Page 1]\n\f\nRFC 4490 Using GOST with CMS May 2006","scope_keywords":["4490","algorithm","algorithms","attribute","attributes","authentication","encryption","hash","key","management","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 4490 This document describes the conventions for using the cryptographic\n algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and\n GOST R 34.11-94 with the Cryptographic Message Syntax (CMS). The CMS\n is used for digital signature, digest, authentication, and encryption\n of arbitrary message contents.\n\nLeontiev & Chudov Standards Track [Page 1]\n\f\nRFC 4490 Using GOST with CMS May 2006 4490 algorithm algorithms attribute attributes authentication encryption hash key management presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 4491","type":"specification","body":"IETF","designation":"RFC 4491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4491.txt","https://www.rfc-editor.org/rfc/rfc4491.pdf"],"folder":"IETF/RFC-4491","files":{"txt":{"path":"standards/IETF/RFC-4491/RFC-4491.txt","sha256":"39f1d26e869fb99e4615c0bc4cfe6a8b44aaca0b28f7f99f45d28658da89eb6e"}},"tags":["nested-reference","unchanged"],"summary":"This document supplements RFC 3279. It describes encoding formats,\n identifiers, and parameter formats for the algorithms GOST R 34.10-\n 94, GOST R 34.10-2001, and GOST R 34.11-94 for use in Internet X.509\n Public Key Infrastructure (PKI).\n\nLeontiev & Shefanovski Standards Track [Page 1]\n\f\nRFC 4491 Using GOST with PKIX May 2006","scope_keywords":["4491","algorithm","algorithms","certificate","certificates","crl","hash","key","keys","pki","profile","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 4491 This document supplements RFC 3279. It describes encoding formats,\n identifiers, and parameter formats for the algorithms GOST R 34.10-\n 94, GOST R 34.10-2001, and GOST R 34.11-94 for use in Internet X.509\n Public Key Infrastructure (PKI).\n\nLeontiev & Shefanovski Standards Track [Page 1]\n\f\nRFC 4491 Using GOST with PKIX May 2006 4491 algorithm algorithms certificate certificates crl hash key keys pki profile signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 4497","type":"specification","body":"IETF","designation":"RFC 4497","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4497.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4497.txt","https://www.rfc-editor.org/rfc/rfc4497.pdf"],"folder":"IETF/RFC-4497","files":{"txt":{"path":"standards/IETF/RFC-4497/RFC-4497.txt","sha256":"894d095665c0a40382ef11899fd4280680de752bd198803d0b0e3a614decef09"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies interworking between the Session Initiation\n Protocol (SIP) and QSIG within corporate telecommunication networks\n (also known as enterprise networks). SIP is an Internet\n application-layer control (signalling) protocol for creating,\n modifying, and terminating sessions with one or more participants.\n These sessions include, in particular, telephone calls. QSIG is a\n signalling protocol for creating, modifying, and terminating\n circuit-switched calls (in particular, telephone calls) within\n Private Integrated Services Networks (PISNs). QSIG is specified in a\n number of Ecma Standards and published also as ISO/IEC standards.\n\nElwell, et al. Best Current Practice [Page 1]\n\f\nRFC 4497 Interworking between SIP and QSIG May 2006","scope_keywords":["4497","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4497 This document specifies interworking between the Session Initiation\n Protocol (SIP) and QSIG within corporate telecommunication networks\n (also known as enterprise networks). SIP is an Internet\n application-layer control (signalling) protocol for creating,\n modifying, and terminating sessions with one or more participants.\n These sessions include, in particular, telephone calls. QSIG is a\n signalling protocol for creating, modifying, and terminating\n circuit-switched calls (in particular, telephone calls) within\n Private Integrated Services Networks (PISNs). QSIG is specified in a\n number of Ecma Standards and published also as ISO/IEC standards.\n\nElwell, et al. Best Current Practice [Page 1]\n\f\nRFC 4497 Interworking between SIP and QSIG May 2006 4497 validation nested-reference unchanged"},{"id":"IETF RFC 4509","type":"specification","body":"IETF","designation":"RFC 4509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4509.txt","https://www.rfc-editor.org/rfc/rfc4509.pdf"],"folder":"IETF/RFC-4509","files":{"txt":{"path":"standards/IETF/RFC-4509/RFC-4509.txt","sha256":"b39ee3cf95b141215e8be464fb32f7f7c8b3606738911550446f47bd0ff4d8e9"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use the SHA-256 digest type in DNS\n Delegation Signer (DS) Resource Records (RRs). DS records, when\n stored in a parent zone, point to DNSKEYs in a child zone.","scope_keywords":["4509","algorithm","authentication","key","keys","path","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4641","folder":"IETF/RFC-4641","source":"IETF/RFC-4641/RFC-4641.txt","version":null},{"body":"IETF","designation":"RFC 5702","folder":"IETF/RFC-5702","source":"IETF/RFC-5702/RFC-5702.txt","version":null},{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null}],"search_text":"IETF RFC 4509 This document specifies how to use the SHA-256 digest type in DNS\n Delegation Signer (DS) Resource Records (RRs). DS records, when\n stored in a parent zone, point to DNSKEYs in a child zone. 4509 algorithm authentication key keys path policy signature nested-reference unchanged"},{"id":"IETF RFC 4510","type":"specification","body":"IETF","designation":"RFC 4510","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4510.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4510.txt","https://www.rfc-editor.org/rfc/rfc4510.pdf"],"folder":"IETF/RFC-4510","files":{"txt":{"path":"standards/IETF/RFC-4510/RFC-4510.txt","sha256":"4f07a585d963fe31a0d8cd47f537d639721573051797992bfd939939d69257c8"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) is an Internet\n protocol for accessing distributed directory services that act in\n accordance with X.500 data and service models. This document\n provides a road map of the LDAP Technical Specification.\n\n1. The LDAP Technical Specification\n\n The technical specification detailing version 3 of the Lightweight\n Directory Access Protocol (LDAP), an Internet Protocol, consists of\n this document and the following documents:\n\n LDAP: The Protocol [RFC4511]\n LDAP: Directory Information Models [RFC4512]\n LDAP: Authentication Methods and Security Mechanisms [RFC4513]\n LDAP: String Representation of Distinguished Names [RFC4514]\n LDAP: String Representation of Search Filters [RFC4515]\n LDAP: Uniform Resource Locator [RFC4516]\n LDAP: Syntaxes and Matching Rules [RFC4517]\n LDAP: Internationalized String Preparation [RFC4518]\n LDAP: Schema for User Applic","scope_keywords":["4510","authentication","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 4510 The Lightweight Directory Access Protocol (LDAP) is an Internet\n protocol for accessing distributed directory services that act in\n accordance with X.500 data and service models. This document\n provides a road map of the LDAP Technical Specification.\n\n1. The LDAP Technical Specification\n\n The technical specification detailing version 3 of the Lightweight\n Directory Access Protocol (LDAP), an Internet Protocol, consists of\n this document and the following documents:\n\n LDAP: The Protocol [RFC4511]\n LDAP: Directory Information Models [RFC4512]\n LDAP: Authentication Methods and Security Mechanisms [RFC4513]\n LDAP: String Representation of Distinguished Names [RFC4514]\n LDAP: String Representation of Search Filters [RFC4515]\n LDAP: Uniform Resource Locator [RFC4516]\n LDAP: Syntaxes and Matching Rules [RFC4517]\n LDAP: Internationalized String Preparation [RFC4518]\n LDAP: Schema for User Applic 4510 authentication key presentation nested-reference unchanged"},{"id":"IETF RFC 4511","type":"specification","body":"IETF","designation":"RFC 4511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4511.txt","https://www.rfc-editor.org/rfc/rfc4511.pdf"],"folder":"IETF/RFC-4511","files":{"txt":{"path":"standards/IETF/RFC-4511/RFC-4511.txt","sha256":"49c6aab64bd9835420f7fc83e9cc53fe7aea46de882daa4f99fafe20273b06fd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the protocol elements, along with their\n semantics and encodings, of the Lightweight Directory Access Protocol\n (LDAP). LDAP provides access to distributed directory services that\n act in accordance with X.500 data and service models. These protocol\n elements are based on those described in the X.500 Directory Access\n Protocol (DAP).","scope_keywords":["4511","attribute","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5507","folder":"IETF/RFC-5507","source":"IETF/RFC-5507/RFC-5507.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null}],"search_text":"IETF RFC 4511 This document describes the protocol elements, along with their\n semantics and encodings, of the Lightweight Directory Access Protocol\n (LDAP). LDAP provides access to distributed directory services that\n act in accordance with X.500 data and service models. These protocol\n elements are based on those described in the X.500 Directory Access\n Protocol (DAP). 4511 attribute key tls nested-reference unchanged"},{"id":"IETF RFC 4512","type":"specification","body":"IETF","designation":"RFC 4512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4512.txt","https://www.rfc-editor.org/rfc/rfc4512.pdf"],"folder":"IETF/RFC-4512","files":{"txt":{"path":"standards/IETF/RFC-4512/RFC-4512.txt","sha256":"c3380501eaa81d93a2bcc4d9e8c38e9fdcef20d2ac4fa52759124bb2d2edd5bf"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) is an Internet\n protocol for accessing distributed directory services that act in\n accordance with X.500 data and service models. This document\n describes the X.500 Directory Information Models, as used in LDAP.\n\nZeilenga Standards Track [Page 1]\n\f\nRFC 4512 LDAP Models June 2006","scope_keywords":["4512","attribute","attributes","key","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null}],"search_text":"IETF RFC 4512 The Lightweight Directory Access Protocol (LDAP) is an Internet\n protocol for accessing distributed directory services that act in\n accordance with X.500 data and service models. This document\n describes the X.500 Directory Information Models, as used in LDAP.\n\nZeilenga Standards Track [Page 1]\n\f\nRFC 4512 LDAP Models June 2006 4512 attribute attributes key preservation nested-reference unchanged"},{"id":"IETF RFC 4513","type":"specification","body":"IETF","designation":"RFC 4513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4513.txt","https://www.rfc-editor.org/rfc/rfc4513.pdf"],"folder":"IETF/RFC-4513","files":{"txt":{"path":"standards/IETF/RFC-4513/RFC-4513.txt","sha256":"2215320fd3d1ae3efc456f331bd0e71a6cfda915ac964130d1565146bf732f6a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes authentication methods and security\n mechanisms of the Lightweight Directory Access Protocol (LDAP). This\n document details establishment of Transport Layer Security (TLS)\n using the StartTLS operation.\n\n This document details the simple Bind authentication method including\n anonymous, unauthenticated, and name/password mechanisms and the\n Simple Authentication and Security Layer (SASL) Bind authentication\n method including the EXTERNAL mechanism.\n\n This document discusses various authentication and authorization\n states through which a session to an LDAP server may pass and the\n actions that trigger these state changes.\n\n This document, together with other documents in the LDAP Technical\n Specification (see Section 1 of the specification's road map),\n obsoletes RFC 2251, RFC 2829, and RFC 2830.\n\nHarrison Standards Track [Page 1]\n\f\nRFC 4513 LDAP Authentication Met","scope_keywords":["4513","authentication","authorization","certificate","credential","credentials","encryption","hash","policy","profile","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4513 This document describes authentication methods and security\n mechanisms of the Lightweight Directory Access Protocol (LDAP). This\n document details establishment of Transport Layer Security (TLS)\n using the StartTLS operation.\n\n This document details the simple Bind authentication method including\n anonymous, unauthenticated, and name/password mechanisms and the\n Simple Authentication and Security Layer (SASL) Bind authentication\n method including the EXTERNAL mechanism.\n\n This document discusses various authentication and authorization\n states through which a session to an LDAP server may pass and the\n actions that trigger these state changes.\n\n This document, together with other documents in the LDAP Technical\n Specification (see Section 1 of the specification's road map),\n obsoletes RFC 2251, RFC 2829, and RFC 2830.\n\nHarrison Standards Track [Page 1]\n\f\nRFC 4513 LDAP Authentication Met 4513 authentication authorization certificate credential credentials encryption hash policy profile subject tls nested-reference unchanged"},{"id":"IETF RFC 4514","type":"specification","body":"IETF","designation":"RFC 4514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4514.txt","https://www.rfc-editor.org/rfc/rfc4514.pdf"],"folder":"IETF/RFC-4514","files":{"txt":{"path":"standards/IETF/RFC-4514/RFC-4514.txt","sha256":"b272176d48a231b28e478c30c59c4bee6073883a0ca25bafd93ea3526702b7de"}},"tags":["nested-reference","unchanged"],"summary":"The X.500 Directory uses distinguished names (DNs) as primary keys to\n entries in the directory. This document defines the string\n representation used in the Lightweight Directory Access Protocol\n (LDAP) to transfer distinguished names. The string representation is\n designed to give a clean representation of commonly used\n distinguished names, while being able to represent any distinguished\n name.\n\n1. Background and Intended Usage\n\n In X.500-based directory systems [X.500], including those accessed\n using the Lightweight Directory Access Protocol (LDAP) [RFC4510],\n distinguished names (DNs) are used to unambiguously refer to\n directory entries [X.501][RFC4512].\n\n The structure of a DN [X.501] is described in terms of ASN.1 [X.680].\n In the X.500 Directory Access Protocol [X.511] (and other ITU-defined\n directory protocols), DNs are encoded using the Basic Encoding Rules\n (BER) [X.690]. I","scope_keywords":["4514","algorithm","algorithms","attribute","key","keys","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 4514 The X.500 Directory uses distinguished names (DNs) as primary keys to\n entries in the directory. This document defines the string\n representation used in the Lightweight Directory Access Protocol\n (LDAP) to transfer distinguished names. The string representation is\n designed to give a clean representation of commonly used\n distinguished names, while being able to represent any distinguished\n name.\n\n1. Background and Intended Usage\n\n In X.500-based directory systems [X.500], including those accessed\n using the Lightweight Directory Access Protocol (LDAP) [RFC4510],\n distinguished names (DNs) are used to unambiguously refer to\n directory entries [X.501][RFC4512].\n\n The structure of a DN [X.501] is described in terms of ASN.1 [X.680].\n In the X.500 Directory Access Protocol [X.511] (and other ITU-defined\n directory protocols), DNs are encoded using the Basic Encoding Rules\n (BER) [X.690]. I 4514 algorithm algorithms attribute key keys presentation registered nested-reference unchanged"},{"id":"IETF RFC 4518","type":"specification","body":"IETF","designation":"RFC 4518","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4518.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4518.txt","https://www.rfc-editor.org/rfc/rfc4518.pdf"],"folder":"IETF/RFC-4518","files":{"txt":{"path":"standards/IETF/RFC-4518/RFC-4518.txt","sha256":"a12b9a04e49cf778f7a26e59d32a2bda02d6d4ab4d4151b6a8cc9db21070a068"}},"tags":["nested-reference","unchanged"],"summary":"The previous Lightweight Directory Access Protocol (LDAP) technical\n specifications did not precisely define how character string matching\n is to be performed. This led to a number of usability and\n interoperability problems. This document defines string preparation\n algorithms for character-based matching rules defined for use in\n LDAP.\n\n1. Introduction","scope_keywords":["4518","algorithm","algorithms","attribute","certificate","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null}],"search_text":"IETF RFC 4518 The previous Lightweight Directory Access Protocol (LDAP) technical\n specifications did not precisely define how character string matching\n is to be performed. This led to a number of usability and\n interoperability problems. This document defines string preparation\n algorithms for character-based matching rules defined for use in\n LDAP.\n\n1. Introduction 4518 algorithm algorithms attribute certificate key validation nested-reference unchanged"},{"id":"IETF RFC 4521","type":"specification","body":"IETF","designation":"RFC 4521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4521.txt","https://www.rfc-editor.org/rfc/rfc4521.pdf"],"folder":"IETF/RFC-4521","files":{"txt":{"path":"standards/IETF/RFC-4521/RFC-4521.txt","sha256":"ec591f3e13f00d71b13a60416e4330ba56cee59ceccda9e787f7f8769601c7ae"}},"tags":["nested-reference","unchanged"],"summary":"The Lightweight Directory Access Protocol (LDAP) is extensible. It\n provides mechanisms for adding new operations, extending existing\n operations, and expanding user and system schemas. This document\n discusses considerations for designers of LDAP extensions.\n\nZeilenga Best Current Practice [Page 1]\n\f\nRFC 4521 LDAP Extensions June 2006","scope_keywords":["4521","attribute","authentication","authorization","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 4521 The Lightweight Directory Access Protocol (LDAP) is extensible. It\n provides mechanisms for adding new operations, extending existing\n operations, and expanding user and system schemas. This document\n discusses considerations for designers of LDAP extensions.\n\nZeilenga Best Current Practice [Page 1]\n\f\nRFC 4521 LDAP Extensions June 2006 4521 attribute authentication authorization key tls nested-reference unchanged"},{"id":"IETF RFC 4522","type":"specification","body":"IETF","designation":"RFC 4522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4522.txt","https://www.rfc-editor.org/rfc/rfc4522.pdf"],"folder":"IETF/RFC-4522","files":{"txt":{"path":"standards/IETF/RFC-4522/RFC-4522.txt","sha256":"740af942a0bad712edc89a9774ea418416afac986ef105c2ab4ee4609785e676"}},"tags":["nested-reference","unchanged"],"summary":"Each attribute stored in a Lightweight Directory Access Protocol\n (LDAP) directory has a defined syntax (i.e., data type). A syntax\n definition specifies how attribute values conforming to the syntax\n are normally represented when transferred in LDAP operations. This\n representation is referred to as the LDAP-specific encoding to\n distinguish it from other methods of encoding attribute values. This\n document defines an attribute option, the binary option, that can be\n used to specify that the associated attribute values are instead\n encoded according to the Basic Encoding Rules (BER) used by X.500\n directories.","scope_keywords":["4522","algorithm","attribute","attributes","certificate","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 4522 Each attribute stored in a Lightweight Directory Access Protocol\n (LDAP) directory has a defined syntax (i.e., data type). A syntax\n definition specifies how attribute values conforming to the syntax\n are normally represented when transferred in LDAP operations. This\n representation is referred to as the LDAP-specific encoding to\n distinguish it from other methods of encoding attribute values. This\n document defines an attribute option, the binary option, that can be\n used to specify that the associated attribute values are instead\n encoded according to the Basic Encoding Rules (BER) used by X.500\n directories. 4522 algorithm attribute attributes certificate key presentation nested-reference unchanged"},{"id":"IETF RFC 4537","type":"specification","body":"IETF","designation":"RFC 4537","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4537.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4537.txt","https://www.rfc-editor.org/rfc/rfc4537.pdf"],"folder":"IETF/RFC-4537","files":{"txt":{"path":"standards/IETF/RFC-4537/RFC-4537.txt","sha256":"2265bbe116b8db7c377d274c6a8ce0485e9c778b199ef059652d2e623cb620d3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the Kerberos protocol as\n defined in RFC 4120, in which the client can send a list of supported\n encryption types in decreasing preference order, and the server then\n selects an encryption type that is supported by both the client and\n the server.","scope_keywords":["4537","authentication","authorization","encryption","key","keys","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4757","folder":"IETF/RFC-4757","source":"IETF/RFC-4757/RFC-4757.txt","version":null}],"search_text":"IETF RFC 4537 This document specifies an extension to the Kerberos protocol as\n defined in RFC 4120, in which the client can send a list of supported\n encryption types in decreasing preference order, and the server then\n selects an encryption type that is supported by both the client and\n the server. 4537 authentication authorization encryption key keys policy nested-reference unchanged"},{"id":"IETF RFC 4538","type":"specification","body":"IETF","designation":"RFC 4538","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4538.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4538.txt","https://www.rfc-editor.org/rfc/rfc4538.pdf"],"folder":"IETF/RFC-4538","files":{"txt":{"path":"standards/IETF/RFC-4538/RFC-4538.txt","sha256":"7f387c4e5df24673866adda20df2828bbd322402a2d2b395897bde9c21436dd1"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the Target-Dialog header field for the\n Session Initiation Protocol (SIP), and the corresponding option tag,\n tdialog. This header field is used in requests that create SIP\n dialogs. It indicates to the recipient that the sender is aware of\n an existing dialog with the recipient, either because the sender is\n on the other side of that dialog, or because it has access to the\n dialog identifiers. The recipient can then authorize the request\n based on this awareness.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4538 Target Dialog June 2006","scope_keywords":["4538","authorization","http","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 4538 This specification defines the Target-Dialog header field for the\n Session Initiation Protocol (SIP), and the corresponding option tag,\n tdialog. This header field is used in requests that create SIP\n dialogs. It indicates to the recipient that the sender is aware of\n an existing dialog with the recipient, either because the sender is\n on the other side of that dialog, or because it has access to the\n dialog identifiers. The recipient can then authorize the request\n based on this awareness.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4538 Target Dialog June 2006 4538 authorization http identification key path nested-reference unchanged"},{"id":"IETF RFC 4543","type":"specification","body":"IETF","designation":"RFC 4543","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4543.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4543.txt","https://www.rfc-editor.org/rfc/rfc4543.pdf"],"folder":"IETF/RFC-4543","files":{"txt":{"path":"standards/IETF/RFC-4543/RFC-4543.txt","sha256":"bd141b5690cd2d573a5fc3524a73b81651961f1eb96297d6b9c71388989a52ec"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n Galois Message Authentication Code (GMAC) as a mechanism to provide\n data origin authentication, but not confidentiality, within the IPsec\n Encapsulating Security Payload (ESP) and Authentication Header (AH).\n GMAC is based on the Galois/Counter Mode (GCM) of operation, and can\n be efficiently implemented in hardware for speeds of 10 gigabits per\n second and above, and is also well-suited to software\n implementations.\n\nMcGrew & Viega Standards Track [Page 1]\n\f\nRFC 4543 GMAC in IPsec ESP and AH May 2006","scope_keywords":["4543","algorithm","attribute","authentication","encryption","key","keys","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4869","folder":"IETF/RFC-4869","source":"IETF/RFC-4869/RFC-4869.txt","version":null},{"body":"IETF","designation":"RFC 5840","folder":"IETF/RFC-5840","source":"IETF/RFC-5840/RFC-5840.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null},{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 4543 This memo describes the use of the Advanced Encryption Standard (AES)\n Galois Message Authentication Code (GMAC) as a mechanism to provide\n data origin authentication, but not confidentiality, within the IPsec\n Encapsulating Security Payload (ESP) and Authentication Header (AH).\n GMAC is based on the Galois/Counter Mode (GCM) of operation, and can\n be efficiently implemented in hardware for speeds of 10 gigabits per\n second and above, and is also well-suited to software\n implementations.\n\nMcGrew & Viega Standards Track [Page 1]\n\f\nRFC 4543 GMAC in IPsec ESP and AH May 2006 4543 algorithm attribute authentication encryption key keys management registered nested-reference unchanged"},{"id":"IETF RFC 4546","type":"specification","body":"IETF","designation":"RFC 4546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4546.txt","https://www.rfc-editor.org/rfc/rfc4546.pdf"],"folder":"IETF/RFC-4546","files":{"txt":{"path":"standards/IETF/RFC-4546/RFC-4546.txt","sha256":"6986d11f68e96f149830345fb01122b75530cd3fc15c68e8a52258952b59eee6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a set of managed objects for Simple Network\n Management Protocol (SNMP) based management of the Radio Frequency\n (RF) interfaces for systems compliant with the Data Over Cable\n Service Interface Specifications (DOCSIS).","scope_keywords":["4546","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4546 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a set of managed objects for Simple Network\n Management Protocol (SNMP) based management of the Radio Frequency\n (RF) interfaces for systems compliant with the Data Over Cable\n Service Interface Specifications (DOCSIS). 4546 authentication key management nested-reference unchanged"},{"id":"IETF RFC 4552","type":"specification","body":"IETF","designation":"RFC 4552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4552.txt","https://www.rfc-editor.org/rfc/rfc4552.pdf"],"folder":"IETF/RFC-4552","files":{"txt":{"path":"standards/IETF/RFC-4552/RFC-4552.txt","sha256":"a9c48a890e007041f6ce47f7fe799e54cc4a6f972276bf97a69bb942bc60488d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes means and mechanisms to provide\n authentication/confidentiality to OSPFv3 using an IPv6 Authentication\n Header/Encapsulating Security Payload (AH/ESP) extension header.\n\nGupta & Melam Standards Track [Page 1]\n\f\nRFC 4552 Authentication/Confidentiality for OSPFv3 June 2006","scope_keywords":["4552","algorithm","algorithms","authentication","encryption","key","keys","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null},{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null},{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null}],"search_text":"IETF RFC 4552 This document describes means and mechanisms to provide\n authentication/confidentiality to OSPFv3 using an IPv6 Authentication\n Header/Encapsulating Security Payload (AH/ESP) extension header.\n\nGupta & Melam Standards Track [Page 1]\n\f\nRFC 4552 Authentication/Confidentiality for OSPFv3 June 2006 4552 algorithm algorithms authentication encryption key keys management path policy nested-reference unchanged"},{"id":"IETF RFC 4553","type":"specification","body":"IETF","designation":"RFC 4553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4553.txt","https://www.rfc-editor.org/rfc/rfc4553.pdf"],"folder":"IETF/RFC-4553","files":{"txt":{"path":"standards/IETF/RFC-4553/RFC-4553.txt","sha256":"30ac0bb850db32b7f52242e5f2c8cf65e726680101a265a3da21715aa1f01bdb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a pseudowire encapsulation for Time Division\n Multiplexing (TDM) bit-streams (T1, E1, T3, E3) that disregards any\n structure that may be imposed on these streams, in particular the\n structure imposed by the standard TDM framing.\n\nVainshtein & Stein Standards Track [Page 1]\n\f\nRFC 4553 Structure-Agnostic TDM over Packet June 2006","scope_keywords":["4553","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 4553 This document describes a pseudowire encapsulation for Time Division\n Multiplexing (TDM) bit-streams (T1, E1, T3, E3) that disregards any\n structure that may be imposed on these streams, in particular the\n structure imposed by the standard TDM framing.\n\nVainshtein & Stein Standards Track [Page 1]\n\f\nRFC 4553 Structure-Agnostic TDM over Packet June 2006 4553 key nested-reference unchanged"},{"id":"IETF RFC 4555","type":"specification","body":"IETF","designation":"RFC 4555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4555.txt","https://www.rfc-editor.org/rfc/rfc4555.pdf"],"folder":"IETF/RFC-4555","files":{"txt":{"path":"standards/IETF/RFC-4555/RFC-4555.txt","sha256":"ea27ba834d364ce2a95c442b7d7b5945cb343450ac5ad8e2d4e2ec2a1d1d791a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the MOBIKE protocol, a mobility and\n multihoming extension to Internet Key Exchange (IKEv2). MOBIKE\n allows the IP addresses associated with IKEv2 and tunnel mode IPsec\n Security Associations to change. A mobile Virtual Private Network\n (VPN) client could use MOBIKE to keep the connection with the VPN\n gateway active while moving from one address to another. Similarly,\n a multihomed host could use MOBIKE to move the traffic to a different\n interface if, for instance, the one currently being used stops\n working.\n\nEronen Standards Track [Page 1]\n\f\nRFC 4555 MOBIKE Protocol June 2006","scope_keywords":["4555","authentication","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5265","folder":"IETF/RFC-5265","source":"IETF/RFC-5265/RFC-5265.txt","version":null},{"body":"IETF","designation":"RFC 5266","folder":"IETF/RFC-5266","source":"IETF/RFC-5266/RFC-5266.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4555 This document describes the MOBIKE protocol, a mobility and\n multihoming extension to Internet Key Exchange (IKEv2). MOBIKE\n allows the IP addresses associated with IKEv2 and tunnel mode IPsec\n Security Associations to change. A mobile Virtual Private Network\n (VPN) client could use MOBIKE to keep the connection with the VPN\n gateway active while moving from one address to another. Similarly,\n a multihomed host could use MOBIKE to move the traffic to a different\n interface if, for instance, the one currently being used stops\n working.\n\nEronen Standards Track [Page 1]\n\f\nRFC 4555 MOBIKE Protocol June 2006 4555 authentication key path nested-reference unchanged"},{"id":"IETF RFC 4559","type":"specification","body":"IETF","designation":"RFC 4559","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4559.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4559.txt","https://www.rfc-editor.org/rfc/rfc4559.pdf"],"folder":"IETF/RFC-4559","files":{"txt":{"path":"standards/IETF/RFC-4559/RFC-4559.txt","sha256":"1f297c4c7948cdf3294ed3201242e41619420ca3ae0af271f06d6db85bfd6b9f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the Microsoft Internet Explorer (MSIE)\n and Internet Information Services (IIS) incorporated in Microsoft\n Windows 2000 use Kerberos for security enhancements of web\n transactions. The Hypertext Transport Protocol (HTTP) auth-scheme of\n \"negotiate\" is defined here; when the negotiation results in the\n selection of Kerberos, the security services of authentication and,\n optionally, impersonation (the IIS server assumes the windows\n identity of the principal that has been authenticated) are performed.\n This document explains how HTTP authentication utilizes the Simple\n and Protected GSS-API Negotiation mechanism. Details of Simple And\n Protected Negotiate (SPNEGO) implementation are not provided in this\n document.","scope_keywords":["4559","authentication","authorization","credential","credentials","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 4559 This document describes how the Microsoft Internet Explorer (MSIE)\n and Internet Information Services (IIS) incorporated in Microsoft\n Windows 2000 use Kerberos for security enhancements of web\n transactions. The Hypertext Transport Protocol (HTTP) auth-scheme of\n \"negotiate\" is defined here; when the negotiation results in the\n selection of Kerberos, the security services of authentication and,\n optionally, impersonation (the IIS server assumes the windows\n identity of the principal that has been authenticated) are performed.\n This document explains how HTTP authentication utilizes the Simple\n and Protected GSS-API Negotiation mechanism. Details of Simple And\n Protected Negotiate (SPNEGO) implementation are not provided in this\n document. 4559 authentication authorization credential credentials http key nested-reference unchanged"},{"id":"IETF RFC 4561","type":"specification","body":"IETF","designation":"RFC 4561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4561.txt","https://www.rfc-editor.org/rfc/rfc4561.pdf"],"folder":"IETF/RFC-4561","files":{"txt":{"path":"standards/IETF/RFC-4561/RFC-4561.txt","sha256":"79e24c4d45139caddf927c077e402f9ebb5d428a6346aeebe8b4b022aa9b9d74"}},"tags":["nested-reference","unchanged"],"summary":"In the context of MPLS TE Fast Reroute, the Merge Point (MP) address\n is required at the Point of Local Repair (PLR) in order to select a\n backup tunnel intersecting a fast reroutable Traffic Engineering\n Label Switched Path (TE LSP) on a downstream Label Switching Router\n (LSR). However, existing protocol mechanisms are not sufficient to\n find an MP address in multi-domain routing networks where a domain is\n defined as an Interior Gateway Protocol (IGP) area or an Autonomous\n System (AS). Hence, the current MPLS Fast Reroute mechanism cannot\n be used in order to protect inter-domain TE LSPs from a failure of an\n Area Border Router (ABR) or Autonomous System Border Router (ASBR).\n This document specifies the use of existing Record Route Object (RRO)\n IPv4 and IPv6 sub-objects (with a new flag defined) thus defining the\n node-id sub-object in order to solve this issue. The MPLS Fast\n Rero","scope_keywords":["4561","attribute","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null}],"search_text":"IETF RFC 4561 In the context of MPLS TE Fast Reroute, the Merge Point (MP) address\n is required at the Point of Local Repair (PLR) in order to select a\n backup tunnel intersecting a fast reroutable Traffic Engineering\n Label Switched Path (TE LSP) on a downstream Label Switching Router\n (LSR). However, existing protocol mechanisms are not sufficient to\n find an MP address in multi-domain routing networks where a domain is\n defined as an Interior Gateway Protocol (IGP) area or an Autonomous\n System (AS). Hence, the current MPLS Fast Reroute mechanism cannot\n be used in order to protect inter-domain TE LSPs from a failure of an\n Area Border Router (ABR) or Autonomous System Border Router (ASBR).\n This document specifies the use of existing Record Route Object (RRO)\n IPv4 and IPv6 sub-objects (with a new flag defined) thus defining the\n node-id sub-object in order to solve this issue. The MPLS Fast\n Rero 4561 attribute path risk nested-reference unchanged"},{"id":"IETF RFC 4563","type":"specification","body":"IETF","designation":"RFC 4563","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4563.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4563.txt","https://www.rfc-editor.org/rfc/rfc4563.pdf"],"folder":"IETF/RFC-4563","files":{"txt":{"path":"standards/IETF/RFC-4563/RFC-4563.txt","sha256":"a8b874ad7c6b1282eae54c3b543a134eaf110003247841c79a3e97cb1c498570"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies a new Type (the Key ID Information Type) for the\n General Extension Payload in the Multimedia Internet KEYing (MIKEY)\n Protocol. This is used in, for example, the Multimedia\n Broadcast/Multicast Service specified in the Third Generation\n Partnership Project.","scope_keywords":["4563","key","keys","management","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 4909","folder":"IETF/RFC-4909","source":"IETF/RFC-4909/RFC-4909.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null}],"search_text":"IETF RFC 4563 This memo specifies a new Type (the Key ID Information Type) for the\n General Extension Payload in the Multimedia Internet KEYing (MIKEY)\n Protocol. This is used in, for example, the Multimedia\n Broadcast/Multicast Service specified in the Third Generation\n Partnership Project. 4563 key keys management policy registered nested-reference unchanged"},{"id":"IETF RFC 4567","type":"specification","body":"IETF","designation":"RFC 4567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4567.txt","https://www.rfc-editor.org/rfc/rfc4567.pdf"],"folder":"IETF/RFC-4567","files":{"txt":{"path":"standards/IETF/RFC-4567/RFC-4567.txt","sha256":"4a1a0bb5ab4d0ef2aa239f135aab2fee1316c286630b6ffaf078c418df5f3601"}},"tags":["nested-reference","unchanged"],"summary":"This document defines general extensions for Session Description\n Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry\n messages, as specified by a key management protocol, in order to\n secure the media. These extensions are presented as a framework, to\n be used by one or more key management protocols. As such, their use\n is meaningful only when complemented by an appropriate key management\n protocol.\n\n General guidelines are also given on how the framework should be used\n together with SIP and RTSP. The usage with the Multimedia Internet\n KEYing (MIKEY) key management protocol is also defined.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 4567 Key Management Extensions for SDP and RTSP July 2006","scope_keywords":["4567","algorithm","algorithms","attribute","attributes","authentication","key","keys","management","profile","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5027","folder":"IETF/RFC-5027","source":"IETF/RFC-5027/RFC-5027.txt","version":null},{"body":"IETF","designation":"RFC 5124","folder":"IETF/RFC-5124","source":"IETF/RFC-5124/RFC-5124.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4567 This document defines general extensions for Session Description\n Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry\n messages, as specified by a key management protocol, in order to\n secure the media. These extensions are presented as a framework, to\n be used by one or more key management protocols. As such, their use\n is meaningful only when complemented by an appropriate key management\n protocol.\n\n General guidelines are also given on how the framework should be used\n together with SIP and RTSP. The usage with the Multimedia Internet\n KEYing (MIKEY) key management protocol is also defined.\n\nArkko, et al. Standards Track [Page 1]\n\f\nRFC 4567 Key Management Extensions for SDP and RTSP July 2006 4567 algorithm algorithms attribute attributes authentication key keys management profile tsp nested-reference unchanged"},{"id":"IETF RFC 4571","type":"specification","body":"IETF","designation":"RFC 4571","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4571.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4571.txt","https://www.rfc-editor.org/rfc/rfc4571.pdf"],"folder":"IETF/RFC-4571","files":{"txt":{"path":"standards/IETF/RFC-4571/RFC-4571.txt","sha256":"38eb36f0c01f1e582786f5605a08004fad179c2efceb5f4873358edfb63de682"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a method for framing Real-time Transport Protocol\n (RTP) and RTP Control Protocol (RTCP) packets onto connection-\n oriented transport (such as TCP). The memo also defines how session\n descriptions may specify RTP streams that use the framing method.","scope_keywords":["4571","crl","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null}],"search_text":"IETF RFC 4571 This memo defines a method for framing Real-time Transport Protocol\n (RTP) and RTP Control Protocol (RTCP) packets onto connection-\n oriented transport (such as TCP). The memo also defines how session\n descriptions may specify RTP streams that use the framing method. 4571 crl key management profile profiles nested-reference unchanged"},{"id":"IETF RFC 4574","type":"specification","body":"IETF","designation":"RFC 4574","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4574.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4574.txt","https://www.rfc-editor.org/rfc/rfc4574.pdf"],"folder":"IETF/RFC-4574","files":{"txt":{"path":"standards/IETF/RFC-4574/RFC-4574.txt","sha256":"d5463216c2992596db5c87765753ded5d96a32660190a8b2b3e10e531d0f0725"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Session Description Protocol (SDP)\n media-level attribute: \"label\". The \"label\" attribute carries a\n pointer to a media stream in the context of an arbitrary network\n application that uses SDP. The sender of the SDP document can attach\n the \"label\" attribute to a particular media stream or streams. The\n application can then use the provided pointer to refer to each\n particular media stream in its context.","scope_keywords":["4574","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4574 This document defines a new Session Description Protocol (SDP)\n media-level attribute: \"label\". The \"label\" attribute carries a\n pointer to a media stream in the context of an arbitrary network\n application that uses SDP. The sender of the SDP document can attach\n the \"label\" attribute to a particular media stream or streams. The\n application can then use the provided pointer to refer to each\n particular media stream in its context. 4574 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 4575","type":"specification","body":"IETF","designation":"RFC 4575","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4575.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4575.txt","https://www.rfc-editor.org/rfc/rfc4575.pdf"],"folder":"IETF/RFC-4575","files":{"txt":{"path":"standards/IETF/RFC-4575/RFC-4575.txt","sha256":"3a6b294fc039eb525b48fb089089fb0e985a808ac0bc6636f4047f65c652717f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a conference event package for tightly coupled\n conferences using the Session Initiation Protocol (SIP) events\n framework, along with a data format used in notifications for this\n package. The conference package allows users to subscribe to a\n conference Uniform Resource Identifier (URI). Notifications are sent\n about changes in the membership of this conference and optionally\n about changes in the state of additional conference components.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 4575 Conference Package August 2006","scope_keywords":["4575","authorization","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null}],"search_text":"IETF RFC 4575 This document defines a conference event package for tightly coupled\n conferences using the Session Initiation Protocol (SIP) events\n framework, along with a data format used in notifications for this\n package. The conference package allows users to subscribe to a\n conference Uniform Resource Identifier (URI). Notifications are sent\n about changes in the membership of this conference and optionally\n about changes in the state of additional conference components.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 4575 Conference Package August 2006 4575 authorization key keys nested-reference unchanged"},{"id":"IETF RFC 4577","type":"specification","body":"IETF","designation":"RFC 4577","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4577.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4577.txt","https://www.rfc-editor.org/rfc/rfc4577.pdf"],"folder":"IETF/RFC-4577","files":{"txt":{"path":"standards/IETF/RFC-4577/RFC-4577.txt","sha256":"6487f72287aec5a86873782b7ba3c6232279fc34069c21c5d316cf0f647f3efe"}},"tags":["nested-reference","unchanged"],"summary":"Many Service Providers offer Virtual Private Network (VPN) services\n to their customers, using a technique in which customer edge routers\n (CE routers) are routing peers of provider edge routers (PE routers).\n The Border Gateway Protocol (BGP) is used to distribute the\n customer's routes across the provider's IP backbone network, and\n Multiprotocol Label Switching (MPLS) is used to tunnel customer\n packets across the provider's backbone. This is known as a \"BGP/MPLS\n IP VPN\". The base specification for BGP/MPLS IP VPNs presumes that\n the routing protocol on the interface between a PE router and a CE\n router is BGP. This document extends that specification by allowing\n the routing protocol on the PE/CE interface to be the Open Shortest\n Path First (OSPF) protocol.\n\n This document updates RFC 4364.\n\nRosen, et al. Standards Track [Page 1]\n\f\nRFC 4577 OSPF for BGP/MPLS IP VPNs June 2006","scope_keywords":["4577","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null}],"search_text":"IETF RFC 4577 Many Service Providers offer Virtual Private Network (VPN) services\n to their customers, using a technique in which customer edge routers\n (CE routers) are routing peers of provider edge routers (PE routers).\n The Border Gateway Protocol (BGP) is used to distribute the\n customer's routes across the provider's IP backbone network, and\n Multiprotocol Label Switching (MPLS) is used to tunnel customer\n packets across the provider's backbone. This is known as a \"BGP/MPLS\n IP VPN\". The base specification for BGP/MPLS IP VPNs presumes that\n the routing protocol on the interface between a PE router and a CE\n router is BGP. This document extends that specification by allowing\n the routing protocol on the PE/CE interface to be the Open Shortest\n Path First (OSPF) protocol.\n\n This document updates RFC 4364.\n\nRosen, et al. Standards Track [Page 1]\n\f\nRFC 4577 OSPF for BGP/MPLS IP VPNs June 2006 4577 key path nested-reference unchanged"},{"id":"IETF RFC 4578","type":"specification","body":"IETF","designation":"RFC 4578","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4578.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4578.txt","https://www.rfc-editor.org/rfc/rfc4578.pdf"],"folder":"IETF/RFC-4578","files":{"txt":{"path":"standards/IETF/RFC-4578/RFC-4578.txt","sha256":"869b3910916dceae2a69bcb0d518e9dfcaca0c75b772a76d8fd4f415201b8ed4"}},"tags":["nested-reference","unchanged"],"summary":"We define Dynamic Host Configuration Protocol (DHCP) options being\n used by Preboot eXecution Environment (PXE) and Extensible Firmware\n Interface (EFI) clients to uniquely identify booting client machines\n and their pre-OS runtime environment so that the DHCP and/or PXE boot\n server can return the correct OS bootstrap image (or pre-boot\n application) name and server to the client.","scope_keywords":["4578","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 6355","folder":"IETF/RFC-6355","source":"IETF/RFC-6355/RFC-6355.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null}],"search_text":"IETF RFC 4578 We define Dynamic Host Configuration Protocol (DHCP) options being\n used by Preboot eXecution Environment (PXE) and Extensible Firmware\n Interface (EFI) clients to uniquely identify booting client machines\n and their pre-OS runtime environment so that the DHCP and/or PXE boot\n server can return the correct OS bootstrap image (or pre-boot\n application) name and server to the client. 4578 key trust nested-reference unchanged"},{"id":"IETF RFC 4579","type":"specification","body":"IETF","designation":"RFC 4579","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4579.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4579.txt","https://www.rfc-editor.org/rfc/rfc4579.pdf"],"folder":"IETF/RFC-4579","files":{"txt":{"path":"standards/IETF/RFC-4579/RFC-4579.txt","sha256":"d025532db730c29ebb6963eee3df36d06da86dea847a192bbf8c3a93912b684f"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines conferencing call control features for the\n Session Initiation Protocol (SIP). This document builds on the\n Conferencing Requirements and Framework documents to define how a\n tightly coupled SIP conference works. The approach is explored from\n the perspective of different user agent (UA) types: conference-\n unaware, conference-aware, and focus UAs. The use of Uniform\n Resource Identifiers (URIs) in conferencing, OPTIONS for capabilities\n discovery, and call control using REFER are covered in detail with\n example call flow diagrams. The usage of the isfocus feature tag is\n defined.","scope_keywords":["4579","authentication","authorization","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 4579 This specification defines conferencing call control features for the\n Session Initiation Protocol (SIP). This document builds on the\n Conferencing Requirements and Framework documents to define how a\n tightly coupled SIP conference works. The approach is explored from\n the perspective of different user agent (UA) types: conference-\n unaware, conference-aware, and focus UAs. The use of Uniform\n Resource Identifiers (URIs) in conferencing, OPTIONS for capabilities\n discovery, and call control using REFER are covered in detail with\n example call flow diagrams. The usage of the isfocus feature tag is\n defined. 4579 authentication authorization key policies nested-reference unchanged"},{"id":"IETF RFC 4582","type":"specification","body":"IETF","designation":"RFC 4582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4582.txt","https://www.rfc-editor.org/rfc/rfc4582.pdf"],"folder":"IETF/RFC-4582","files":{"txt":{"path":"standards/IETF/RFC-4582/RFC-4582.txt","sha256":"5e5419b9c8db79dc39ead6577fd8ffb58b05a724aa1a4940300a1586e3e0b04b"}},"tags":["nested-reference","unchanged"],"summary":"Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols.\n\n This document specifies the Binary Floor Control Protocol (BFCP).\n BFCP is used between floor participants and floor control servers,\n and between floor chairs (i.e., moderators) and floor control\n servers.","scope_keywords":["4582","attribute","attributes","authentication","authorization","policy","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4582 Floor control is a means to manage joint or exclusive access to\n shared resources in a (multiparty) conferencing environment.\n Thereby, floor control complements other functions -- such as\n conference and media session setup, conference policy manipulation,\n and media control -- that are realized by other protocols.\n\n This document specifies the Binary Floor Control Protocol (BFCP).\n BFCP is used between floor participants and floor control servers,\n and between floor chairs (i.e., moderators) and floor control\n servers. 4582 attribute attributes authentication authorization policy tls trust nested-reference unchanged"},{"id":"IETF RFC 4583","type":"specification","body":"IETF","designation":"RFC 4583","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4583.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4583.txt","https://www.rfc-editor.org/rfc/rfc4583.pdf"],"folder":"IETF/RFC-4583","files":{"txt":{"path":"standards/IETF/RFC-4583/RFC-4583.txt","sha256":"602f5a1e2bc602a97f7a43ab189ffc67d14b801e826aab09de5899509a4bf93c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to describe Binary Floor Control Protocol\n (BFCP) streams in Session Description Protocol (SDP) descriptions.\n User agents using the offer/answer model to establish BFCP streams\n use this format in their offers and answers.","scope_keywords":["4583","attribute","attributes","authentication","key","management","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 5018","folder":"IETF/RFC-5018","source":"IETF/RFC-5018/RFC-5018.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4583 This document specifies how to describe Binary Floor Control Protocol\n (BFCP) streams in Session Description Protocol (SDP) descriptions.\n User agents using the offer/answer model to establish BFCP streams\n use this format in their offers and answers. 4583 attribute attributes authentication key management tls trust nested-reference unchanged"},{"id":"IETF RFC 4584","type":"specification","body":"IETF","designation":"RFC 4584","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4584.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4584.txt","https://www.rfc-editor.org/rfc/rfc4584.pdf"],"folder":"IETF/RFC-4584","files":{"txt":{"path":"standards/IETF/RFC-4584/RFC-4584.txt","sha256":"b7a475c22416edf95fbf7df50862ebc288d3d99bedbe7fc27e137c187bd8c0cb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes data structures and API support for Mobile\n IPv6 as an extension to the Advanced Socket API for IPv6.\n\n Just as the Advanced Sockets API for IPv6 gives access to various\n extension headers and the ICMPv6 protocol, this document specifies\n the same level of access for Mobile IPv6 components. It specifies a\n mechanism for applications to retrieve and set information for\n Mobility Header messages, Home Address destination options, and\n Routing Header Type 2 extension headers. It also specifies the\n common data structures and definitions that might be used by certain\n advanced Mobile IPv6 socket applications.\n\nChakrabarti & Nordmark Informational [Page 1]\n\f\nRFC 4584 Sockets for API for Mobile IPv6 July 2006","scope_keywords":["4584","authentication","authorization","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null}],"search_text":"IETF RFC 4584 This document describes data structures and API support for Mobile\n IPv6 as an extension to the Advanced Socket API for IPv6.\n\n Just as the Advanced Sockets API for IPv6 gives access to various\n extension headers and the ICMPv6 protocol, this document specifies\n the same level of access for Mobile IPv6 components. It specifies a\n mechanism for applications to retrieve and set information for\n Mobility Header messages, Home Address destination options, and\n Routing Header Type 2 extension headers. It also specifies the\n common data structures and definitions that might be used by certain\n advanced Mobile IPv6 socket applications.\n\nChakrabarti & Nordmark Informational [Page 1]\n\f\nRFC 4584 Sockets for API for Mobile IPv6 July 2006 4584 authentication authorization policy nested-reference unchanged"},{"id":"IETF RFC 4588","type":"specification","body":"IETF","designation":"RFC 4588","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4588.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4588.txt","https://www.rfc-editor.org/rfc/rfc4588.pdf"],"folder":"IETF/RFC-4588","files":{"txt":{"path":"standards/IETF/RFC-4588/RFC-4588.txt","sha256":"93c0768b7812050d875a7c767ca76ba120f217cbcb9c0332afb5e50641ae3ac1"}},"tags":["nested-reference","unchanged"],"summary":"RTP retransmission is an effective packet loss recovery technique for\n real-time applications with relaxed delay bounds. This document\n describes an RTP payload format for performing retransmissions.\n Retransmitted RTP packets are sent in a separate stream from the\n original RTP stream. It is assumed that feedback from receivers to\n senders is available. In particular, it is assumed that Real-time\n Transport Control Protocol (RTCP) feedback as defined in the extended\n RTP profile for RTCP-based feedback (denoted RTP/AVPF) is available\n in this memo.\n\nRey, et al. Standards Track [Page 1]\n\f\nRFC 4588 RTP Retransmission Payload Format July 2006","scope_keywords":["4588","profile","profiles","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 4588 RTP retransmission is an effective packet loss recovery technique for\n real-time applications with relaxed delay bounds. This document\n describes an RTP payload format for performing retransmissions.\n Retransmitted RTP packets are sent in a separate stream from the\n original RTP stream. It is assumed that feedback from receivers to\n senders is available. In particular, it is assumed that Real-time\n Transport Control Protocol (RTCP) feedback as defined in the extended\n RTP profile for RTCP-based feedback (denoted RTP/AVPF) is available\n in this memo.\n\nRey, et al. Standards Track [Page 1]\n\f\nRFC 4588 RTP Retransmission Payload Format July 2006 4588 profile profiles tsp nested-reference unchanged"},{"id":"IETF RFC 4589","type":"specification","body":"IETF","designation":"RFC 4589","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4589.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4589.txt","https://www.rfc-editor.org/rfc/rfc4589.pdf"],"folder":"IETF/RFC-4589","files":{"txt":{"path":"standards/IETF/RFC-4589/RFC-4589.txt","sha256":"6c6cd5a386abf1734fe04286e948366804b6a37aaa321c6c23e23b6c8f5df887"}},"tags":["nested-reference","unchanged"],"summary":"This document creates a registry for describing the types of places a\n human or end system might be found. The registry is then referenced\n by other protocols that need a common set of location terms as\n protocol constants. Examples of location terms defined in this\n document include aircraft, office, and train station.","scope_keywords":["4589","attribute","attributes","authentication","key","management","pid","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4589 This document creates a registry for describing the types of places a\n human or end system might be found. The registry is then referenced\n by other protocols that need a common set of location terms as\n protocol constants. Examples of location terms defined in this\n document include aircraft, office, and train station. 4589 attribute attributes authentication key management pid presentation registered nested-reference unchanged"},{"id":"IETF RFC 4591","type":"specification","body":"IETF","designation":"RFC 4591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4591.txt","https://www.rfc-editor.org/rfc/rfc4591.pdf"],"folder":"IETF/RFC-4591","files":{"txt":{"path":"standards/IETF/RFC-4591/RFC-4591.txt","sha256":"adafa5308b7cc50b9e799e2dc837265aa0a9241cfafd6a65c099e8a7d6d9eda9"}},"tags":["nested-reference","unchanged"],"summary":"The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a\n protocol for tunneling a variety of data link protocols over IP\n networks. This document describes the specifics of how to tunnel\n Frame Relay over L2TPv3, including frame encapsulation, virtual-\n circuit creation and deletion, and status change notification.\n\nTownsley, et al. Standards Track [Page 1]\n\f\nRFC 4591 Frame Relay over L2TPv3 July 2006","scope_keywords":["4591","attribute","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5641","folder":"IETF/RFC-5641","source":"IETF/RFC-5641/RFC-5641.txt","version":null}],"search_text":"IETF RFC 4591 The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a\n protocol for tunneling a variety of data link protocols over IP\n networks. This document describes the specifics of how to tunnel\n Frame Relay over L2TPv3, including frame encapsulation, virtual-\n circuit creation and deletion, and status change notification.\n\nTownsley, et al. Standards Track [Page 1]\n\f\nRFC 4591 Frame Relay over L2TPv3 July 2006 4591 attribute key management nested-reference unchanged"},{"id":"IETF RFC 4598","type":"specification","body":"IETF","designation":"RFC 4598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4598.txt","https://www.rfc-editor.org/rfc/rfc4598.pdf"],"folder":"IETF/RFC-4598","files":{"txt":{"path":"standards/IETF/RFC-4598/RFC-4598.txt","sha256":"2321e6b81ebfc5998693f9449d3d2a5915764994910c0e744fc621e55488b115"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Real-time Transport Protocol (RTP) payload\n format for transporting Enhanced AC-3 (E-AC-3) encoded audio data.\n E-AC-3 is a high-quality, multichannel audio coding format and is an\n extension of the AC-3 audio coding format, which is used in US High-\n Definition Television (HDTV), DVD, cable and satellite television,\n and other media. E-AC-3 is an optional audio format in US and world\n wide digital television and high-definition DVD formats. The RTP\n payload format as presented in this document includes support for\n data fragmentation.\n\nLink Standards Track [Page 1]\n\f\nRFC 4598 RTP Payload Format for E-AC-3-Audio July 2006","scope_keywords":["4598","algorithm","audit","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"IETF RFC 4598 This document describes a Real-time Transport Protocol (RTP) payload\n format for transporting Enhanced AC-3 (E-AC-3) encoded audio data.\n E-AC-3 is a high-quality, multichannel audio coding format and is an\n extension of the AC-3 audio coding format, which is used in US High-\n Definition Television (HDTV), DVD, cable and satellite television,\n and other media. E-AC-3 is an optional audio format in US and world\n wide digital television and high-definition DVD formats. The RTP\n payload format as presented in this document includes support for\n data fragmentation.\n\nLink Standards Track [Page 1]\n\f\nRFC 4598 RTP Payload Format for E-AC-3-Audio July 2006 4598 algorithm audit key nested-reference unchanged"},{"id":"IETF RFC 4610","type":"specification","body":"IETF","designation":"RFC 4610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4610.txt","https://www.rfc-editor.org/rfc/rfc4610.pdf"],"folder":"IETF/RFC-4610","files":{"txt":{"path":"standards/IETF/RFC-4610/RFC-4610.txt","sha256":"d82490f241682ba5aee80cbeb68c2a09bfbd87da1b7806394575041d50ab3597"}},"tags":["nested-reference","unchanged"],"summary":"This specification allows Anycast-RP (Rendezvous Point) to be used\n inside a domain that runs Protocol Independent Multicast (PIM) only.\n Other multicast protocols (such as Multicast Source Discovery\n Protocol (MSDP), which has been used traditionally to solve this\n problem) are not required to support Anycast-RP.\n\n1. Introduction\n\n Anycast-RP as described in [I1] is a mechanism that ISP-based\n backbones have used to get fast convergence when a PIM Rendezvous\n Point (RP) router fails. To allow receivers and sources to\n Rendezvous to the closest RP, the packets from a source need to get\n to all RPs to find joined receivers.\n\n This notion of receivers finding sources is the fundamental problem\n of source discovery that MSDP was intended to solve. However, if one\n would like to retain the Anycast-RP benefits from [I1] with less\n protocol machinery, removing MSDP from the solution space is a","scope_keywords":["4610","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7063","folder":"IETF/RFC-7063","source":"IETF/RFC-7063/RFC-7063.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 4610 This specification allows Anycast-RP (Rendezvous Point) to be used\n inside a domain that runs Protocol Independent Multicast (PIM) only.\n Other multicast protocols (such as Multicast Source Discovery\n Protocol (MSDP), which has been used traditionally to solve this\n problem) are not required to support Anycast-RP.\n\n1. Introduction\n\n Anycast-RP as described in [I1] is a mechanism that ISP-based\n backbones have used to get fast convergence when a PIM Rendezvous\n Point (RP) router fails. To allow receivers and sources to\n Rendezvous to the closest RP, the packets from a source need to get\n to all RPs to find joined receivers.\n\n This notion of receivers finding sources is the fundamental problem\n of source discovery that MSDP was intended to solve. However, if one\n would like to retain the Anycast-RP benefits from [I1] with less\n protocol machinery, removing MSDP from the solution space is a 4610 key nested-reference unchanged"},{"id":"IETF RFC 4616","type":"specification","body":"IETF","designation":"RFC 4616","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4616.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4616.txt","https://www.rfc-editor.org/rfc/rfc4616.pdf"],"folder":"IETF/RFC-4616","files":{"txt":{"path":"standards/IETF/RFC-4616/RFC-4616.txt","sha256":"33aa677ab7b8efe52e86147c63b38dd8dd5de96438c63e10ba8a04504bbdbca4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Zeilenga, Ed.\nRequest for Comments: 4616 OpenLDAP Foundation\nUpdates: 2595 August 2006\nCategory: Standards Track\n\n The PLAIN Simple Authentication and Security Layer (SASL) Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document defines a simple clear-text user/password Simple\n Authentication and Security Layer (SASL) mechanism called the PLAIN\n mechanism. The PLAIN mechanism is intended to be used, in\n combination with data confidentiality services provided by a l","scope_keywords":["4616","algorithm","algorithms","authentication","authorization","credential","credentials","hash","key","presentation","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4616 Network Working Group K. Zeilenga, Ed.\nRequest for Comments: 4616 OpenLDAP Foundation\nUpdates: 2595 August 2006\nCategory: Standards Track\n\n The PLAIN Simple Authentication and Security Layer (SASL) Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document defines a simple clear-text user/password Simple\n Authentication and Security Layer (SASL) mechanism called the PLAIN\n mechanism. The PLAIN mechanism is intended to be used, in\n combination with data confidentiality services provided by a l 4616 algorithm algorithms authentication authorization credential credentials hash key presentation profile tls nested-reference unchanged"},{"id":"IETF RFC 4619","type":"specification","body":"IETF","designation":"RFC 4619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4619.txt","https://www.rfc-editor.org/rfc/rfc4619.pdf"],"folder":"IETF/RFC-4619","files":{"txt":{"path":"standards/IETF/RFC-4619/RFC-4619.txt","sha256":"002f4403a4720a9096a2d2d2d87a144eafdd1105f5fca305930175ac2bad2599"}},"tags":["nested-reference","unchanged"],"summary":"A frame relay pseudowire is a mechanism that exists between a\n provider's edge network nodes and that supports as faithfully as\n possible frame relay services over an MPLS packet switched network\n (PSN). This document describes the detailed encapsulation necessary\n to transport frame relay packets over an MPLS network.\n\nMartini & Kawa Standards Track [Page 1]\n\f\nRFC 4619 Encapsulation for Transport of Frame Relay September 2006","scope_keywords":["4619","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4720","folder":"IETF/RFC-4720","source":"IETF/RFC-4720/RFC-4720.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null}],"search_text":"IETF RFC 4619 A frame relay pseudowire is a mechanism that exists between a\n provider's edge network nodes and that supports as faithfully as\n possible frame relay services over an MPLS packet switched network\n (PSN). This document describes the detailed encapsulation necessary\n to transport frame relay packets over an MPLS network.\n\nMartini & Kawa Standards Track [Page 1]\n\f\nRFC 4619 Encapsulation for Transport of Frame Relay September 2006 4619 delivery key nested-reference unchanged"},{"id":"IETF RFC 4630","type":"specification","body":"IETF","designation":"RFC 4630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4630.txt","https://www.rfc-editor.org/rfc/rfc4630.pdf"],"folder":"IETF/RFC-4630","files":{"txt":{"path":"standards/IETF/RFC-4630/RFC-4630.txt","sha256":"281299ba8855bce1a4e8dc93248846685f0e218168cb644cbca8c4102bd76e8d"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the handling of DirectoryString in the Internet\n X.509 Public Key Infrastructure Certificate and Certificate\n Revocation List (CRL) Profile, which is published in RFC 3280. The\n use of UTF8String and PrintableString are the preferred encoding.\n The requirement for exclusive use of UTF8String after December 31,\n 2003 is removed.","scope_keywords":["4630","attribute","attributes","certificate","certificates","crl","issuer","key","path","pki","profile","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null}],"search_text":"IETF RFC 4630 This document updates the handling of DirectoryString in the Internet\n X.509 Public Key Infrastructure Certificate and Certificate\n Revocation List (CRL) Profile, which is published in RFC 3280. The\n use of UTF8String and PrintableString are the preferred encoding.\n The requirement for exclusive use of UTF8String after December 31,\n 2003 is removed. 4630 attribute attributes certificate certificates crl issuer key path pki profile revocation subject nested-reference unchanged"},{"id":"IETF RFC 4636","type":"specification","body":"IETF","designation":"RFC 4636","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4636.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4636.txt","https://www.rfc-editor.org/rfc/rfc4636.pdf"],"folder":"IETF/RFC-4636","files":{"txt":{"path":"standards/IETF/RFC-4636/RFC-4636.txt","sha256":"8cf6a57c680c3ec31c1955eb69ea56147c1ac50e409cf3c91772ab98972fbd80"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Perkins\nRequest for Comments: 4636 Nokia Research Center\nCategory: Standards Track October 2006\n\n Foreign Agent Error Extension for Mobile IPv4\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document specifies a new extension for use by Foreign Agents\n operating Mobile IP for IPv4. Currently, a foreign agent cannot\n supply status information without destroying the ability for a mobile\n node to verify authentication data supplied by the home agent. The\n new extension solves t","scope_keywords":["4636","authentication","key","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4721","folder":"IETF/RFC-4721","source":"IETF/RFC-4721/RFC-4721.txt","version":null}],"search_text":"IETF RFC 4636 Network Working Group C. Perkins\nRequest for Comments: 4636 Nokia Research Center\nCategory: Standards Track October 2006\n\n Foreign Agent Error Extension for Mobile IPv4\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document specifies a new extension for use by Foreign Agents\n operating Mobile IP for IPv4. Currently, a foreign agent cannot\n supply status information without destroying the ability for a mobile\n node to verify authentication data supplied by the home agent. The\n new extension solves t 4636 authentication key revocation nested-reference unchanged"},{"id":"IETF RFC 4642","type":"specification","body":"IETF","designation":"RFC 4642","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4642.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4642.txt","https://www.rfc-editor.org/rfc/rfc4642.pdf"],"folder":"IETF/RFC-4642","files":{"txt":{"path":"standards/IETF/RFC-4642/RFC-4642.txt","sha256":"b6abf6a451078c0958488d5a0e5ef6a29e8dca2c2237e351a582395b320895f6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Network News Transfer Protocol\n (NNTP) that allows an NNTP client and server to use Transport Layer\n Security (TLS). The primary goal is to provide encryption for\n single-link confidentiality purposes, but data integrity, (optional)\n certificate-based peer entity authentication, and (optional) data\n compression are also possible.\n\nMurchison, et al. Standards Track [Page 1]\n\f\nRFC 4642 Using TLS with NNTP October 2006","scope_keywords":["4642","authentication","certificate","encryption","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4642 This memo defines an extension to the Network News Transfer Protocol\n (NNTP) that allows an NNTP client and server to use Transport Layer\n Security (TLS). The primary goal is to provide encryption for\n single-link confidentiality purposes, but data integrity, (optional)\n certificate-based peer entity authentication, and (optional) data\n compression are also possible.\n\nMurchison, et al. Standards Track [Page 1]\n\f\nRFC 4642 Using TLS with NNTP October 2006 4642 authentication certificate encryption key tls nested-reference unchanged"},{"id":"IETF RFC 4644","type":"specification","body":"IETF","designation":"RFC 4644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4644.txt","https://www.rfc-editor.org/rfc/rfc4644.pdf"],"folder":"IETF/RFC-4644","files":{"txt":{"path":"standards/IETF/RFC-4644/RFC-4644.txt","sha256":"452fc4ff0b23d66c66dbaa4433e1ba8564217cac047ec8ce0b765b6f8d4bda2b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Network News Transfer Protocol\n (NNTP) to provide asynchronous (otherwise known as \"streaming\")\n transfer of articles. This allows servers to transfer articles to\n other servers with much greater efficiency.\n\n This document updates and formalizes the CHECK and TAKETHIS commands\n specified in RFC 2980 and deprecates the MODE STREAM command.","scope_keywords":["4644","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null}],"search_text":"IETF RFC 4644 This memo defines an extension to the Network News Transfer Protocol\n (NNTP) to provide asynchronous (otherwise known as \"streaming\")\n transfer of articles. This allows servers to transfer articles to\n other servers with much greater efficiency.\n\n This document updates and formalizes the CHECK and TAKETHIS commands\n specified in RFC 2980 and deprecates the MODE STREAM command. 4644 key nested-reference unchanged"},{"id":"IETF RFC 4649","type":"specification","body":"IETF","designation":"RFC 4649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4649.txt","https://www.rfc-editor.org/rfc/rfc4649.pdf"],"folder":"IETF/RFC-4649","files":{"txt":{"path":"standards/IETF/RFC-4649/RFC-4649.txt","sha256":"2c1bf1a662d9553a9167c6a6e2daf21679ae2221bd73dab6dbe8c6c2c993e12d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Relay Agent Remote-ID option for the Dynamic\n Host Configuration Protocol for IPv6 (DHCPv6). This option is the\n DHCPv6 equivalent for the Dynamic Host Configuration Protocol for\n IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified\n in RFC 3046.","scope_keywords":["4649","key","policies","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null}],"search_text":"IETF RFC 4649 This memo defines a new Relay Agent Remote-ID option for the Dynamic\n Host Configuration Protocol for IPv6 (DHCPv6). This option is the\n DHCPv6 equivalent for the Dynamic Host Configuration Protocol for\n IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified\n in RFC 3046. 4649 key policies registered trust nested-reference unchanged"},{"id":"IETF RFC 4657","type":"specification","body":"IETF","designation":"RFC 4657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4657.txt","https://www.rfc-editor.org/rfc/rfc4657.pdf"],"folder":"IETF/RFC-4657","files":{"txt":{"path":"standards/IETF/RFC-4657/RFC-4657.txt","sha256":"c797aed1ca8e7f167f570ce029439b6e57ce0a7798fd35c4fedc9dd8003b358c"}},"tags":["nested-reference","unchanged"],"summary":"The PCE model is described in the \"PCE Architecture\" document and\n facilitates path computation requests from Path Computation Clients\n (PCCs) to Path Computation Elements (PCEs). This document specifies\n generic requirements for a communication protocol between PCCs and\n PCEs, and also between PCEs where cooperation between PCEs is\n desirable. Subsequent documents will specify application-specific\n requirements for the PCE communication protocol.","scope_keywords":["4657","key","management","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4674","folder":"IETF/RFC-4674","source":"IETF/RFC-4674/RFC-4674.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 4657 The PCE model is described in the \"PCE Architecture\" document and\n facilitates path computation requests from Path Computation Clients\n (PCCs) to Path Computation Elements (PCEs). This document specifies\n generic requirements for a communication protocol between PCCs and\n PCEs, and also between PCEs where cooperation between PCEs is\n desirable. Subsequent documents will specify application-specific\n requirements for the PCE communication protocol. 4657 key management path policy nested-reference unchanged"},{"id":"IETF RFC 4660","type":"specification","body":"IETF","designation":"RFC 4660","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4660.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4660.txt","https://www.rfc-editor.org/rfc/rfc4660.pdf"],"folder":"IETF/RFC-4660","files":{"txt":{"path":"standards/IETF/RFC-4660/RFC-4660.txt","sha256":"b3441eccf24e77919c494b638dd6a6a06e5950ca1c992e9852110fd09b4b7eca"}},"tags":["nested-reference","unchanged"],"summary":"The SIP event notification framework describes the usage of the\n Session Initiation Protocol (SIP) for subscriptions and notifications\n of changes to the state of a resource. The document does not\n describe a mechanism whereby filtering of event notification\n information can be achieved.\n\n This document describes the operations a subscriber performs in order\n to put filtering rules associated with a subscription to event\n notification information in place. The handling, by the subscriber,\n of responses to subscriptions carrying filtering rules and the\n handling of notifications with filtering rules applied to them are\n also described. Furthermore, the document conveys how the notifier\n behaves when receiving such filtering rules and how a notification is\n constructed.\n\nKhartabil, et al. Standards Track [Page 1]\n\f\nRFC 4660 Functional Description of Filtering September 2006","scope_keywords":["4660","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 4660 The SIP event notification framework describes the usage of the\n Session Initiation Protocol (SIP) for subscriptions and notifications\n of changes to the state of a resource. The document does not\n describe a mechanism whereby filtering of event notification\n information can be achieved.\n\n This document describes the operations a subscriber performs in order\n to put filtering rules associated with a subscription to event\n notification information in place. The handling, by the subscriber,\n of responses to subscriptions carrying filtering rules and the\n handling of notifications with filtering rules applied to them are\n also described. Furthermore, the document conveys how the notifier\n behaves when receiving such filtering rules and how a notification is\n constructed.\n\nKhartabil, et al. Standards Track [Page 1]\n\f\nRFC 4660 Functional Description of Filtering September 2006 4660 key validation nested-reference unchanged"},{"id":"IETF RFC 4661","type":"specification","body":"IETF","designation":"RFC 4661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4661.txt","https://www.rfc-editor.org/rfc/rfc4661.pdf"],"folder":"IETF/RFC-4661","files":{"txt":{"path":"standards/IETF/RFC-4661/RFC-4661.txt","sha256":"85d89efcb4e8585b6bbfc3b2b76430956eda58225c5b436b3652a65030c233eb"}},"tags":["nested-reference","unchanged"],"summary":"The SIP event notification framework describes the usage of the\n Session Initiation Protocol (SIP) for subscriptions and notifications\n of changes to a state of a resource. The document does not describe\n a mechanism whereby filtering of event notification information can\n be achieved. Filtering is a mechanism for defining the preferred\n notification information to be delivered and for specifying triggers\n that cause that information to be delivered. In order to enable\n this, a format is needed to enable the subscriber to describe the\n state changes of a resource that cause notifications to be sent to it\n and what those notifications are to contain. This document presents\n a format in the form of an XML document.\n\nKhartabil, et al. Standards Track [Page 1]\n\f\nRFC 4661 XML Based Format for Filtering September 2006","scope_keywords":["4661","attribute","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4660","folder":"IETF/RFC-4660","source":"IETF/RFC-4660/RFC-4660.txt","version":null}],"search_text":"IETF RFC 4661 The SIP event notification framework describes the usage of the\n Session Initiation Protocol (SIP) for subscriptions and notifications\n of changes to a state of a resource. The document does not describe\n a mechanism whereby filtering of event notification information can\n be achieved. Filtering is a mechanism for defining the preferred\n notification information to be delivered and for specifying triggers\n that cause that information to be delivered. In order to enable\n this, a format is needed to enable the subscriber to describe the\n state changes of a resource that cause notifications to be sent to it\n and what those notifications are to contain. This document presents\n a format in the form of an XML document.\n\nKhartabil, et al. Standards Track [Page 1]\n\f\nRFC 4661 XML Based Format for Filtering September 2006 4661 attribute key nested-reference unchanged"},{"id":"IETF RFC 4667","type":"specification","body":"IETF","designation":"RFC 4667","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4667.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4667.txt","https://www.rfc-editor.org/rfc/rfc4667.pdf"],"folder":"IETF/RFC-4667","files":{"txt":{"path":"standards/IETF/RFC-4667/RFC-4667.txt","sha256":"d3023b5af8bb7016b383577f6765f802dbf631c02fbe764842c628f1c2ffb11a"}},"tags":["nested-reference","unchanged"],"summary":"The Layer 2 Tunneling Protocol (L2TP) provides a standard method for\n setting up and managing L2TP sessions to tunnel a variety of L2\n protocols. One of the reference models supported by L2TP describes\n the use of an L2TP session to connect two Layer 2 circuits attached\n to a pair of peering L2TP Access Concentrators (LACs), which is a\n basic form of Layer 2 Virtual Private Network (L2VPN). This document\n defines the protocol extensions for L2TP to set up different types of\n L2VPNs in a unified fashion.","scope_keywords":["4667","algorithm","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null}],"search_text":"IETF RFC 4667 The Layer 2 Tunneling Protocol (L2TP) provides a standard method for\n setting up and managing L2TP sessions to tunnel a variety of L2\n protocols. One of the reference models supported by L2TP describes\n the use of an L2TP session to connect two Layer 2 circuits attached\n to a pair of peering L2TP Access Concentrators (LACs), which is a\n basic form of Layer 2 Virtual Private Network (L2VPN). This document\n defines the protocol extensions for L2TP to set up different types of\n L2VPNs in a unified fashion. 4667 algorithm key management nested-reference unchanged"},{"id":"IETF RFC 4668","type":"specification","body":"IETF","designation":"RFC 4668","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4668.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4668.txt","https://www.rfc-editor.org/rfc/rfc4668.pdf"],"folder":"IETF/RFC-4668","files":{"txt":{"path":"standards/IETF/RFC-4668/RFC-4668.txt","sha256":"269278bcf9a5586a315dd13ce69db7bc5ba48822831d445b92b9c5ac886421da"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions that instrument RADIUS\n authentication client functions. These extensions represent a\n portion of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions, IP-based management stations can manage RADIUS\n authentication clients.\n\n This memo obsoletes RFC 2618 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2618 are carried forward into this document. The memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Standards Track [Page 1]\n\f\nRFC 4668 RADIUS Auth Client MIB (IPv6) August 2006","scope_keywords":["4668","attribute","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4669","folder":"IETF/RFC-4669","source":"IETF/RFC-4669/RFC-4669.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4668 This memo defines a set of extensions that instrument RADIUS\n authentication client functions. These extensions represent a\n portion of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions, IP-based management stations can manage RADIUS\n authentication clients.\n\n This memo obsoletes RFC 2618 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2618 are carried forward into this document. The memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Standards Track [Page 1]\n\f\nRFC 4668 RADIUS Auth Client MIB (IPv6) August 2006 4668 attribute authentication key management nested-reference unchanged"},{"id":"IETF RFC 4669","type":"specification","body":"IETF","designation":"RFC 4669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4669.txt","https://www.rfc-editor.org/rfc/rfc4669.pdf"],"folder":"IETF/RFC-4669","files":{"txt":{"path":"standards/IETF/RFC-4669/RFC-4669.txt","sha256":"96665b9d30bcfd589e7d4d053eafa2697c853c6325cd84fbc7befba8e4976ff6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions that instrument RADIUS\n authentication server functions. These extensions represent a\n portion of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions, IP-based management stations can manage RADIUS\n authentication servers.\n\n This memo obsoletes RFC 2619 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2619 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Standards Track [Page 1]\n\f\nRFC 4669 RADIUS Auth Server MIB (IPv6) August 2006","scope_keywords":["4669","attribute","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4668","folder":"IETF/RFC-4668","source":"IETF/RFC-4668/RFC-4668.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4669 This memo defines a set of extensions that instrument RADIUS\n authentication server functions. These extensions represent a\n portion of the Management Information Base (MIB) for use with network\n management protocols in the Internet community. Using these\n extensions, IP-based management stations can manage RADIUS\n authentication servers.\n\n This memo obsoletes RFC 2619 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2619 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Standards Track [Page 1]\n\f\nRFC 4669 RADIUS Auth Server MIB (IPv6) August 2006 4669 attribute authentication key management nested-reference unchanged"},{"id":"IETF RFC 4670","type":"specification","body":"IETF","designation":"RFC 4670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4670.txt","https://www.rfc-editor.org/rfc/rfc4670.pdf"],"folder":"IETF/RFC-4670","files":{"txt":{"path":"standards/IETF/RFC-4670/RFC-4670.txt","sha256":"93c004c5ea9c8184629d9cd1bd638ac74ecbc4a6f59e7e346219f074d0a3a4ed"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions that instrument RADIUS\n accounting client functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions,\n IP-based management stations can manage RADIUS accounting clients.\n\n This memo obsoletes RFC 2620 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2620 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Informational [Page 1]\n\f\nRFC 4670 RADIUS Acct Client MIB (IPv6) August 2006","scope_keywords":["4670","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4671","folder":"IETF/RFC-4671","source":"IETF/RFC-4671/RFC-4671.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4670 This memo defines a set of extensions that instrument RADIUS\n accounting client functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions,\n IP-based management stations can manage RADIUS accounting clients.\n\n This memo obsoletes RFC 2620 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2620 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Informational [Page 1]\n\f\nRFC 4670 RADIUS Acct Client MIB (IPv6) August 2006 4670 authentication key management nested-reference unchanged"},{"id":"IETF RFC 4671","type":"specification","body":"IETF","designation":"RFC 4671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4671.txt","https://www.rfc-editor.org/rfc/rfc4671.pdf"],"folder":"IETF/RFC-4671","files":{"txt":{"path":"standards/IETF/RFC-4671/RFC-4671.txt","sha256":"f3e51390cf997ef29b87556e5340c7a4f1c9ceac4fd707f090cb73822bdea35d"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a set of extensions that instrument RADIUS\n accounting server functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions,\n IP-based management stations can manage RADIUS accounting servers.\n\n This memo obsoletes RFC 2621 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2621 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Informational [Page 1]\n\f\nRFC 4671 RADIUS Acct Server MIB (IPv6) August 2006","scope_keywords":["4671","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4670","folder":"IETF/RFC-4670","source":"IETF/RFC-4670/RFC-4670.txt","version":null},{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4671 This memo defines a set of extensions that instrument RADIUS\n accounting server functions. These extensions represent a portion of\n the Management Information Base (MIB) for use with network management\n protocols in the Internet community. Using these extensions,\n IP-based management stations can manage RADIUS accounting servers.\n\n This memo obsoletes RFC 2621 by deprecating the MIB table containing\n IPv4-only address formats and defining a new table to add support for\n version-neutral IP address formats. The remaining MIB objects from\n RFC 2621 are carried forward into this document. This memo also adds\n UNITS and REFERENCE clauses to selected objects.\n\nNelson Informational [Page 1]\n\f\nRFC 4671 RADIUS Acct Server MIB (IPv6) August 2006 4671 authentication key management nested-reference unchanged"},{"id":"IETF RFC 4672","type":"specification","body":"IETF","designation":"RFC 4672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4672.txt","https://www.rfc-editor.org/rfc/rfc4672.pdf"],"folder":"IETF/RFC-4672","files":{"txt":{"path":"standards/IETF/RFC-4672/RFC-4672.txt","sha256":"a90d2c893f952eb9cefecf504b13155f69f6e584fd165a2df974a6741aa26346"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes the Remote Authentication Dial-In User\n Service (RADIUS) (RFC2865) Dynamic Authorization Client (DAC)\n functions that support the dynamic authorization extensions as\n defined in RFC 3576.","scope_keywords":["4672","authentication","authorization","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4673","folder":"IETF/RFC-4673","source":"IETF/RFC-4673/RFC-4673.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4672 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes the Remote Authentication Dial-In User\n Service (RADIUS) (RFC2865) Dynamic Authorization Client (DAC)\n functions that support the dynamic authorization extensions as\n defined in RFC 3576. 4672 authentication authorization key management nested-reference unchanged"},{"id":"IETF RFC 4673","type":"specification","body":"IETF","designation":"RFC 4673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4673.txt","https://www.rfc-editor.org/rfc/rfc4673.pdf"],"folder":"IETF/RFC-4673","files":{"txt":{"path":"standards/IETF/RFC-4673/RFC-4673.txt","sha256":"5ff66d0a61e874149421755e4ed0c239ab0d80ad10b22d67d72b3c7ba169d7ff"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes the Remote Authentication Dial-In User\n Service (RADIUS) (RFC 2865) Dynamic Authorization Server (DAS)\n functions that support the dynamic authorization extensions as\n defined in RFC 3576.","scope_keywords":["4673","authentication","authorization","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4672","folder":"IETF/RFC-4672","source":"IETF/RFC-4672/RFC-4672.txt","version":null},{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4673 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes the Remote Authentication Dial-In User\n Service (RADIUS) (RFC 2865) Dynamic Authorization Server (DAS)\n functions that support the dynamic authorization extensions as\n defined in RFC 3576. 4673 authentication authorization key management nested-reference unchanged"},{"id":"IETF RFC 4674","type":"specification","body":"IETF","designation":"RFC 4674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4674.txt","https://www.rfc-editor.org/rfc/rfc4674.pdf"],"folder":"IETF/RFC-4674","files":{"txt":{"path":"standards/IETF/RFC-4674/RFC-4674.txt","sha256":"1e019547111936ad502c556d7370f70328ef3d4ed94ae8155d5761f7cfb2ef0a"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a set of requirements for a Path Computation\n Element (PCE) discovery mechanism that would allow a Path Computation\n Client (PCC) to discover dynamically and automatically a set of PCEs\n along with certain information relevant for PCE selection. It is\n intended that solutions that specify procedures and protocols or\n extensions to existing protocols for such PCE discovery satisfy these\n requirements.","scope_keywords":["4674","key","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 4674 This document presents a set of requirements for a Path Computation\n Element (PCE) discovery mechanism that would allow a Path Computation\n Client (PCC) to discover dynamically and automatically a set of PCEs\n along with certain information relevant for PCE selection. It is\n intended that solutions that specify procedures and protocols or\n extensions to existing protocols for such PCE discovery satisfy these\n requirements. 4674 key path policy nested-reference unchanged"},{"id":"IETF RFC 4676","type":"specification","body":"IETF","designation":"RFC 4676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4676.txt","https://www.rfc-editor.org/rfc/rfc4676.pdf"],"folder":"IETF/RFC-4676","files":{"txt":{"path":"standards/IETF/RFC-4676/RFC-4676.txt","sha256":"1511ec3ff9ec14c26f3f0723e8ba31f4970eff3cdc207608401061678df29a57"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) option containing the civic location of the client or the\n DHCP server. The Location Configuration Information (LCI) includes\n information about the country, administrative units such as states,\n provinces, and cities, as well as street addresses, postal community\n names, and building information. The option allows multiple\n renditions of the same address in different scripts and languages.","scope_keywords":["4676","delivery","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null}],"search_text":"IETF RFC 4676 This document specifies a Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) option containing the civic location of the client or the\n DHCP server. The Location Configuration Information (LCI) includes\n information about the country, administrative units such as states,\n provinces, and cities, as well as street addresses, postal community\n names, and building information. The option allows multiple\n renditions of the same address in different scripts and languages. 4676 delivery pid trust nested-reference unchanged"},{"id":"IETF RFC 4680","type":"specification","body":"IETF","designation":"RFC 4680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4680.txt","https://www.rfc-editor.org/rfc/rfc4680.pdf"],"folder":"IETF/RFC-4680","files":{"txt":{"path":"standards/IETF/RFC-4680/RFC-4680.txt","sha256":"f70794d646a8c079ef4db94a52d0d847a9d2ab7ed41473638d153740bdb2c3e2"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a TLS handshake message for exchange of\n supplemental application data. TLS hello message extensions are used\n to determine which supplemental data types are supported by both the\n TLS client and the TLS server. Then, the supplemental data handshake\n message is used to exchange the data. Other documents will define\n the syntax of these extensions and the syntax of the associated\n supplemental data types.\n\nSantesson Standards Track [Page 1]\n\f\nRFC 4680 TLS Handshake Message for Supplemental Data September 2006\n\n1. Introduction\n\n Recent standards activities have proposed different mechanisms for\n transmitting supplemental application data in the TLS handshake\n message. For example, recent proposals transfer data that is not\n processed by the TLS protocol itself, but assist the TLS-protected\n application in the authentication and authorization decisions. One\n propo","scope_keywords":["4680","attribute","authentication","authorization","certificate","certificates","credential","credentials","key","presentation","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4681","folder":"IETF/RFC-4681","source":"IETF/RFC-4681/RFC-4681.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4680 This specification defines a TLS handshake message for exchange of\n supplemental application data. TLS hello message extensions are used\n to determine which supplemental data types are supported by both the\n TLS client and the TLS server. Then, the supplemental data handshake\n message is used to exchange the data. Other documents will define\n the syntax of these extensions and the syntax of the associated\n supplemental data types.\n\nSantesson Standards Track [Page 1]\n\f\nRFC 4680 TLS Handshake Message for Supplemental Data September 2006\n\n1. Introduction\n\n Recent standards activities have proposed different mechanisms for\n transmitting supplemental application data in the TLS handshake\n message. For example, recent proposals transfer data that is not\n processed by the TLS protocol itself, but assist the TLS-protected\n application in the authentication and authorization decisions. One\n propo 4680 attribute authentication authorization certificate certificates credential credentials key presentation tls nested-reference unchanged"},{"id":"IETF RFC 4683","type":"specification","body":"IETF","designation":"RFC 4683","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4683.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4683.txt","https://www.rfc-editor.org/rfc/rfc4683.pdf"],"folder":"IETF/RFC-4683","files":{"txt":{"path":"standards/IETF/RFC-4683/RFC-4683.txt","sha256":"3f223608ab8c02756a11e1021f35301b5c94089dff7673517d627da139555e92"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Subject Identification Method (SIM) for\n including a privacy-sensitive identifier in the subjectAltName\n extension of a certificate.\n\n The SIM is an optional feature that may be used by relying parties to\n determine whether the subject of a particular certificate is also the\n person corresponding to a particular sensitive identifier.\n\nPark, et al. Standards Track [Page 1]\n\f\nRFC 4683 Subject Identification Method October 2006","scope_keywords":["4683","certificate","certificates","credential","credentials","encryption","identification","issuer","key","license","pki","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null}],"search_text":"IETF RFC 4683 This document defines the Subject Identification Method (SIM) for\n including a privacy-sensitive identifier in the subjectAltName\n extension of a certificate.\n\n The SIM is an optional feature that may be used by relying parties to\n determine whether the subject of a particular certificate is also the\n person corresponding to a particular sensitive identifier.\n\nPark, et al. Standards Track [Page 1]\n\f\nRFC 4683 Subject Identification Method October 2006 4683 certificate certificates credential credentials encryption identification issuer key license pki subject nested-reference unchanged"},{"id":"IETF RFC 4684","type":"specification","body":"IETF","designation":"RFC 4684","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4684.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4684.txt","https://www.rfc-editor.org/rfc/rfc4684.pdf"],"folder":"IETF/RFC-4684","files":{"txt":{"path":"standards/IETF/RFC-4684/RFC-4684.txt","sha256":"794b4b3e401987039042b9518181b61dbf08bb93dc86cb8263c143194f2f25a8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Multi-Protocol BGP (MP-BGP) procedures that\n allow BGP speakers to exchange Route Target reachability information.\n This information can be used to build a route distribution graph in\n order to limit the propagation of Virtual Private Network (VPN)\n Network Layer Reachability Information (NLRI) between different\n autonomous systems or distinct clusters of the same autonomous\n system. This document updates RFC 4364.\n\nMarques, et al. Standards Track [Page 1]\n\f\nRFC 4684 Route Target (RT) Constrain November 2006","scope_keywords":["4684","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 4684 This document defines Multi-Protocol BGP (MP-BGP) procedures that\n allow BGP speakers to exchange Route Target reachability information.\n This information can be used to build a route distribution graph in\n order to limit the propagation of Virtual Private Network (VPN)\n Network Layer Reachability Information (NLRI) between different\n autonomous systems or distinct clusters of the same autonomous\n system. This document updates RFC 4364.\n\nMarques, et al. Standards Track [Page 1]\n\f\nRFC 4684 Route Target (RT) Constrain November 2006 4684 key trust nested-reference unchanged"},{"id":"IETF RFC 4685","type":"specification","body":"IETF","designation":"RFC 4685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4685.txt","https://www.rfc-editor.org/rfc/rfc4685.pdf"],"folder":"IETF/RFC-4685","files":{"txt":{"path":"standards/IETF/RFC-4685/RFC-4685.txt","sha256":"eef4bfbe893c5ef435a83d6910081b90b86c00e34f038d74dccc812bd5a513da"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a mechanism that allows feeds publishers to\n express threaded discussions within the Atom Syndication Format.","scope_keywords":["4685","attribute","attributes","http","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null}],"search_text":"IETF RFC 4685 This memo presents a mechanism that allows feeds publishers to\n express threaded discussions within the Atom Syndication Format. 4685 attribute attributes http key presentation nested-reference unchanged"},{"id":"IETF RFC 4687","type":"specification","body":"IETF","designation":"RFC 4687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4687.txt","https://www.rfc-editor.org/rfc/rfc4687.pdf"],"folder":"IETF/RFC-4687","files":{"txt":{"path":"standards/IETF/RFC-4687/RFC-4687.txt","sha256":"d6c505517da7f0836009219cf7f6a525023b1c454c03b645c22c900f317621bf"}},"tags":["nested-reference","unchanged"],"summary":"Multi-Protocol Label Switching (MPLS) has been extended to encompass\n point-to-multipoint (P2MP) Label Switched Paths (LSPs). As with\n point-to-point MPLS LSPs, the requirement to detect, handle, and\n diagnose control and data plane defects is critical.\n\n For operators deploying services based on P2MP MPLS LSPs, the\n detection and specification of how to handle those defects are\n important because such defects not only may affect the fundamentals\n of an MPLS network, but also may impact service level specification\n commitments for customers of their network.\n\n This document describes requirements for data plane operations and\n management for P2MP MPLS LSPs. These requirements apply to all forms\n of P2MP MPLS LSPs, and include P2MP Traffic Engineered (TE) LSPs and\n multicast LSPs.\n\nYasukawa, et al. Informational [Page 1]\n\f\nRFC 4687 OAM Reqs for Point-to-Multipoint MPLS September 2006","scope_keywords":["4687","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 4687 Multi-Protocol Label Switching (MPLS) has been extended to encompass\n point-to-multipoint (P2MP) Label Switched Paths (LSPs). As with\n point-to-point MPLS LSPs, the requirement to detect, handle, and\n diagnose control and data plane defects is critical.\n\n For operators deploying services based on P2MP MPLS LSPs, the\n detection and specification of how to handle those defects are\n important because such defects not only may affect the fundamentals\n of an MPLS network, but also may impact service level specification\n commitments for customers of their network.\n\n This document describes requirements for data plane operations and\n management for P2MP MPLS LSPs. These requirements apply to all forms\n of P2MP MPLS LSPs, and include P2MP Traffic Engineered (TE) LSPs and\n multicast LSPs.\n\nYasukawa, et al. Informational [Page 1]\n\f\nRFC 4687 OAM Reqs for Point-to-Multipoint MPLS September 2006 4687 key management path nested-reference unchanged"},{"id":"IETF RFC 4694","type":"specification","body":"IETF","designation":"RFC 4694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4694.txt","https://www.rfc-editor.org/rfc/rfc4694.pdf"],"folder":"IETF/RFC-4694","files":{"txt":{"path":"standards/IETF/RFC-4694/RFC-4694.txt","sha256":"b95a1f04ff62aaa779e21832d417fe9e7b866ca202ae0096415446300854e12e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines five parameters in the \"tel\" Uniform Resource\n Identifier (URI) to carry the number portability (NP)-related\n information. Those parameters can be passed to the next-hop network\n node after an NP database dip has been performed.","scope_keywords":["4694","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4694 This document defines five parameters in the \"tel\" Uniform Resource\n Identifier (URI) to carry the number portability (NP)-related\n information. Those parameters can be passed to the next-hop network\n node after an NP database dip has been performed. 4694 identification key nested-reference unchanged"},{"id":"IETF RFC 4706","type":"specification","body":"IETF","designation":"RFC 4706","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4706.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4706.txt","https://www.rfc-editor.org/rfc/rfc4706.pdf"],"folder":"IETF/RFC-4706","files":{"txt":{"path":"standards/IETF/RFC-4706/RFC-4706.txt","sha256":"5be6ecad249ec72279089af9f0eea269c2eddfbc5a70c63b1599cc65fb1545cc"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing parameters of the\n \"Asymmetric Digital Subscriber Line\" family of interface types: ADSL,\n ADSL2, ADSL2+, and their variants.\n\nMorgenstern, et al. Standards Track [Page 1]\n\f\nRFC 4706 ADSL2-LINE MIB November 2006","scope_keywords":["4706","attribute","attributes","key","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 4706 This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing parameters of the\n \"Asymmetric Digital Subscriber Line\" family of interface types: ADSL,\n ADSL2, ADSL2+, and their variants.\n\nMorgenstern, et al. Standards Track [Page 1]\n\f\nRFC 4706 ADSL2-LINE MIB November 2006 4706 attribute attributes key management profile profiles nested-reference unchanged"},{"id":"IETF RFC 4711","type":"specification","body":"IETF","designation":"RFC 4711","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4711.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4711.txt","https://www.rfc-editor.org/rfc/rfc4711.pdf"],"folder":"IETF/RFC-4711","files":{"txt":{"path":"standards/IETF/RFC-4711/RFC-4711.txt","sha256":"f693fefa6069c499d087cedde198253a8a8002547c4697204c5b461aebd36503"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n The document proposes an extension to the Remote Monitoring MIB, RFC\n 2819. In particular, it describes managed objects used for real-time\n application Quality of Service (QoS) monitoring.","scope_keywords":["4711","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4711 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n The document proposes an extension to the Remote Monitoring MIB, RFC\n 2819. In particular, it describes managed objects used for real-time\n application Quality of Service (QoS) monitoring. 4711 http key management nested-reference unchanged"},{"id":"IETF RFC 4715","type":"specification","body":"IETF","designation":"RFC 4715","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4715.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4715.txt","https://www.rfc-editor.org/rfc/rfc4715.pdf"],"folder":"IETF/RFC-4715","files":{"txt":{"path":"standards/IETF/RFC-4715/RFC-4715.txt","sha256":"326a8c1cbb4991c4f1f82a8a9ebad62798d3559c53a446d5a9ab3955934b1d48"}},"tags":["nested-reference","unchanged"],"summary":"Without a tel URI parameter to carry an encoding type of Integrated\n Services Digital Network (ISDN) subaddress, interworking between ISDN\n User Part (ISUP) network and a Session Initiation Protocol (SIP)\n network is impossible in some cases. To solve this problem, this\n document specifies a new optional tel URI parameter to carry the\n encoding type of ISDN subaddress.\n\nMunakata, et al. Informational [Page 1]\n\f\nRFC 4715 ISDN for tel URI November 2006","scope_keywords":["4715","holder","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null}],"search_text":"IETF RFC 4715 Without a tel URI parameter to carry an encoding type of Integrated\n Services Digital Network (ISDN) subaddress, interworking between ISDN\n User Part (ISUP) network and a Session Initiation Protocol (SIP)\n network is impossible in some cases. To solve this problem, this\n document specifies a new optional tel URI parameter to carry the\n encoding type of ISDN subaddress.\n\nMunakata, et al. Informational [Page 1]\n\f\nRFC 4715 ISDN for tel URI November 2006 4715 holder key trust nested-reference unchanged"},{"id":"IETF RFC 4717","type":"specification","body":"IETF","designation":"RFC 4717","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4717.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4717.txt","https://www.rfc-editor.org/rfc/rfc4717.pdf"],"folder":"IETF/RFC-4717","files":{"txt":{"path":"standards/IETF/RFC-4717/RFC-4717.txt","sha256":"d4d9734621ed708167f715e6152ee0f8e3c9afddba13e54681a842c9c1ad98c4"}},"tags":["nested-reference","unchanged"],"summary":"An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry\n ATM cells over an MPLS network. This enables service providers to\n offer \"emulated\" ATM services over existing MPLS networks. This\n document specifies methods for the encapsulation of ATM cells within\n a pseudowire. It also specifies the procedures for using a PW to\n provide an ATM service.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4717 Encapsulation for ATM over MPLS December 2006","scope_keywords":["4717","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null}],"search_text":"IETF RFC 4717 An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry\n ATM cells over an MPLS network. This enables service providers to\n offer \"emulated\" ATM services over existing MPLS networks. This\n document specifies methods for the encapsulation of ATM cells within\n a pseudowire. It also specifies the procedures for using a PW to\n provide an ATM service.\n\nMartini, et al. Standards Track [Page 1]\n\f\nRFC 4717 Encapsulation for ATM over MPLS December 2006 4717 key trust nested-reference unchanged"},{"id":"IETF RFC 4718","type":"specification","body":"IETF","designation":"RFC 4718","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4718.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4718.txt","https://www.rfc-editor.org/rfc/rfc4718.pdf"],"folder":"IETF/RFC-4718","files":{"txt":{"path":"standards/IETF/RFC-4718/RFC-4718.txt","sha256":"8a3c1285f43c5578176d14825b22cbf9362668633c7455d1475952aca998aaa6"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies many areas of the IKEv2 specification. It\n does not to introduce any changes to the protocol, but rather\n provides descriptions that are less prone to ambiguous\n interpretations. The purpose of this document is to encourage the\n development of interoperable implementations.\n\nEronen & Hoffman Informational [Page 1]\n\f\nRFC 4718 IKEv2 Clarifications October 2006","scope_keywords":["4718","attribute","authentication","authorization","certificate","hash","identification","key","policy","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4891","folder":"IETF/RFC-4891","source":"IETF/RFC-4891/RFC-4891.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5247","folder":"IETF/RFC-5247","source":"IETF/RFC-5247/RFC-5247.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4718 This document clarifies many areas of the IKEv2 specification. It\n does not to introduce any changes to the protocol, but rather\n provides descriptions that are less prone to ambiguous\n interpretations. The purpose of this document is to encourage the\n development of interoperable implementations.\n\nEronen & Hoffman Informational [Page 1]\n\f\nRFC 4718 IKEv2 Clarifications October 2006 4718 attribute authentication authorization certificate hash identification key policy signature signatures nested-reference unchanged"},{"id":"IETF RFC 4720","type":"specification","body":"IETF","designation":"RFC 4720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4720.txt","https://www.rfc-editor.org/rfc/rfc4720.pdf"],"folder":"IETF/RFC-4720","files":{"txt":{"path":"standards/IETF/RFC-4720/RFC-4720.txt","sha256":"3d9afaaed25bd860f96dfd54e2463b08345dc121ed76cab10f21c09ff364660b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism for preserving Frame Check Sequence\n (FCS) through Ethernet, Frame Relay, High-Level Data Link Control\n (HDLC), and PPP pseudowires.","scope_keywords":["4720","key","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null}],"search_text":"IETF RFC 4720 This document defines a mechanism for preserving Frame Check Sequence\n (FCS) through Ethernet, Frame Relay, High-Level Data Link Control\n (HDLC), and PPP pseudowires. 4720 key path subject trust nested-reference unchanged"},{"id":"IETF RFC 4724","type":"specification","body":"IETF","designation":"RFC 4724","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4724.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4724.txt","https://www.rfc-editor.org/rfc/rfc4724.pdf"],"folder":"IETF/RFC-4724","files":{"txt":{"path":"standards/IETF/RFC-4724/RFC-4724.txt","sha256":"673175b9b23a67a8b187936be64647aba47c427fd1ca5fa0319119e5629c0835"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for BGP that would help minimize\n the negative effects on routing caused by BGP restart. An End-of-RIB\n marker is specified and can be used to convey routing convergence\n information. A new BGP capability, termed \"Graceful Restart\n Capability\", is defined that would allow a BGP speaker to express its\n ability to preserve forwarding state during BGP restart. Finally,\n procedures are outlined for temporarily retaining routing information\n across a TCP session termination/re-establishment.\n\n The mechanisms described in this document are applicable to all\n routers, both those with the ability to preserve forwarding state\n during BGP restart and those without (although the latter need to\n implement only a subset of the mechanisms described in this\n document).\n\nSangli, et al. Standards Track [Page 1]\n\f\nRFC 4724 Graceful Restart Mechanism for BGP January 2007","scope_keywords":["4724","attribute","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4781","folder":"IETF/RFC-4781","source":"IETF/RFC-4781/RFC-4781.txt","version":null},{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 4724 This document describes a mechanism for BGP that would help minimize\n the negative effects on routing caused by BGP restart. An End-of-RIB\n marker is specified and can be used to convey routing convergence\n information. A new BGP capability, termed \"Graceful Restart\n Capability\", is defined that would allow a BGP speaker to express its\n ability to preserve forwarding state during BGP restart. Finally,\n procedures are outlined for temporarily retaining routing information\n across a TCP session termination/re-establishment.\n\n The mechanisms described in this document are applicable to all\n routers, both those with the ability to preserve forwarding state\n during BGP restart and those without (although the latter need to\n implement only a subset of the mechanisms described in this\n document).\n\nSangli, et al. Standards Track [Page 1]\n\f\nRFC 4724 Graceful Restart Mechanism for BGP January 2007 4724 attribute key trust nested-reference unchanged"},{"id":"IETF RFC 4731","type":"specification","body":"IETF","designation":"RFC 4731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4731.txt","https://www.rfc-editor.org/rfc/rfc4731.pdf"],"folder":"IETF/RFC-4731","files":{"txt":{"path":"standards/IETF/RFC-4731/RFC-4731.txt","sha256":"e5fad166cf955ab1420a57db02cef70eefe15e6db55f80f8fb99067bfb55facd"}},"tags":["nested-reference","unchanged"],"summary":"This document extends IMAP (RFC 3501) SEARCH and UID SEARCH commands\n with several result options, which can control what kind of\n information is returned. The following result options are defined:\n minimal value, maximal value, all found messages, and number of found\n messages.","scope_keywords":["4731","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4731 This document extends IMAP (RFC 3501) SEARCH and UID SEARCH commands\n with several result options, which can control what kind of\n information is returned. The following result options are defined:\n minimal value, maximal value, all found messages, and number of found\n messages. 4731 key presentation trust nested-reference unchanged"},{"id":"IETF RFC 4733","type":"specification","body":"IETF","designation":"RFC 4733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4733.txt","https://www.rfc-editor.org/rfc/rfc4733.pdf"],"folder":"IETF/RFC-4733","files":{"txt":{"path":"standards/IETF/RFC-4733/RFC-4733.txt","sha256":"60eebc200b29f0e35e2092e4a28dd0c32e6a8a5bc6e543e915026ee67c72844e"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how to carry dual-tone multifrequency (DTMF)\n signalling, other tone signals, and telephony events in RTP packets.\n It obsoletes RFC 2833.\n\n This memo captures and expands upon the basic framework defined in\n RFC 2833, but retains only the most basic event codes. It sets up an\n IANA registry to which other event code assignments may be added.\n Companion documents add event codes to this registry relating to\n modem, fax, text telephony, and channel-associated signalling events.\n The remainder of the event codes defined in RFC 2833 are\n conditionally reserved in case other documents revive their use.\n\n This document provides a number of clarifications to the original\n document. However, it specifically differs from RFC 2833 by removing\n the requirement that all compliant implementations support the DTMF\n events. Instead, compliant implementations taking part in\n out-of-","scope_keywords":["4733","key","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5167","folder":"IETF/RFC-5167","source":"IETF/RFC-5167/RFC-5167.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 4733 This memo describes how to carry dual-tone multifrequency (DTMF)\n signalling, other tone signals, and telephony events in RTP packets.\n It obsoletes RFC 2833.\n\n This memo captures and expands upon the basic framework defined in\n RFC 2833, but retains only the most basic event codes. It sets up an\n IANA registry to which other event code assignments may be added.\n Companion documents add event codes to this registry relating to\n modem, fax, text telephony, and channel-associated signalling events.\n The remainder of the event codes defined in RFC 2833 are\n conditionally reserved in case other documents revive their use.\n\n This document provides a number of clarifications to the original\n document. However, it specifically differs from RFC 2833 by removing\n the requirement that all compliant implementations support the DTMF\n events. Instead, compliant implementations taking part in\n out-of- 4733 key timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4734","type":"specification","body":"IETF","designation":"RFC 4734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4734.txt","https://www.rfc-editor.org/rfc/rfc4734.pdf"],"folder":"IETF/RFC-4734","files":{"txt":{"path":"standards/IETF/RFC-4734/RFC-4734.txt","sha256":"2a2438bc8db5bb3563942d3f417a2ad3b4fe594392d9b79e99a6a961a04a4d44"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates RFC 4733 to add event codes for modem, fax, and\n text telephony signals when carried in the telephony event RTP\n payload. It supersedes the assignment of event codes for this\n purpose in RFC 2833, and therefore obsoletes that part of RFC 2833.\n\nSchulzrinne & Taylor Standards Track [Page 1]\n\f\nRFC 4734 Modem, Fax, and Text Telephony Events December 2006","scope_keywords":["4734","identification","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null}],"search_text":"IETF RFC 4734 This memo updates RFC 4733 to add event codes for modem, fax, and\n text telephony signals when carried in the telephony event RTP\n payload. It supersedes the assignment of event codes for this\n purpose in RFC 2833, and therefore obsoletes that part of RFC 2833.\n\nSchulzrinne & Taylor Standards Track [Page 1]\n\f\nRFC 4734 Modem, Fax, and Text Telephony Events December 2006 4734 identification key trust nested-reference unchanged"},{"id":"IETF RFC 4735","type":"specification","body":"IETF","designation":"RFC 4735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4735.txt","https://www.rfc-editor.org/rfc/rfc4735.pdf"],"folder":"IETF/RFC-4735","files":{"txt":{"path":"standards/IETF/RFC-4735/RFC-4735.txt","sha256":"fce3d7bca1c42f4f6de6a926342a414c246012fadb649772f75e7b5f6a4f2c2e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Taylor\nRequest for Comments: 4735 Nortel\nCategory: Standards Track October 2006\n\n Example Media Types for Use in Documentation\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document is registration for the 'example' media type and\n 'example' subtypes within the standards tree. The 'example/*' and\n '*/example' media types are defined for documentation purposes only.\n\n1. Introduction\n\n From time to time, documents created by the IETF or by other\n standards bodies show example","scope_keywords":["4735","key","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null}],"search_text":"IETF RFC 4735 Network Working Group T. Taylor\nRequest for Comments: 4735 Nortel\nCategory: Standards Track October 2006\n\n Example Media Types for Use in Documentation\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document is registration for the 'example' media type and\n 'example' subtypes within the standards tree. The 'example/*' and\n '*/example' media types are defined for documentation purposes only.\n\n1. Introduction\n\n From time to time, documents created by the IETF or by other\n standards bodies show example 4735 key license subject nested-reference unchanged"},{"id":"IETF RFC 4736","type":"specification","body":"IETF","designation":"RFC 4736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4736.txt","https://www.rfc-editor.org/rfc/rfc4736.pdf"],"folder":"IETF/RFC-4736","files":{"txt":{"path":"standards/IETF/RFC-4736/RFC-4736.txt","sha256":"b0f75a89405c238cbfdc8477512cd4d8e2396428d55b6b95cac3ee8b35e98a94"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism for the reoptimization of loosely\n routed MPLS and GMPLS (Generalized Multiprotocol Label Switching)\n Traffic Engineering (TE) Label Switched Paths (LSPs) signaled with\n Resource Reservation Protocol Traffic Engineering (RSVP-TE). This\n document proposes a mechanism that allows a TE LSP head-end Label\n Switching Router (LSR) to trigger a new path re-evaluation on every\n hop that has a next hop defined as a loose or abstract hop and a\n mid-point LSR to signal to the head-end LSR that a better path exists\n (compared to the current path) or that the TE LSP must be reoptimized\n (because of maintenance required on the TE LSP path). The proposed\n mechanism applies to the cases of intra- and inter-domain (Interior\n Gateway Protocol area (IGP area) or Autonomous System) packet and\n non-packet TE LSPs following a loosely routed path.\n\nVasseur, et al. Informationa","scope_keywords":["4736","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null}],"search_text":"IETF RFC 4736 This document defines a mechanism for the reoptimization of loosely\n routed MPLS and GMPLS (Generalized Multiprotocol Label Switching)\n Traffic Engineering (TE) Label Switched Paths (LSPs) signaled with\n Resource Reservation Protocol Traffic Engineering (RSVP-TE). This\n document proposes a mechanism that allows a TE LSP head-end Label\n Switching Router (LSR) to trigger a new path re-evaluation on every\n hop that has a next hop defined as a loose or abstract hop and a\n mid-point LSR to signal to the head-end LSR that a better path exists\n (compared to the current path) or that the TE LSP must be reoptimized\n (because of maintenance required on the TE LSP path). The proposed\n mechanism applies to the cases of intra- and inter-domain (Interior\n Gateway Protocol area (IGP area) or Autonomous System) packet and\n non-packet TE LSPs following a loosely routed path.\n\nVasseur, et al. Informationa 4736 key path trust nested-reference unchanged"},{"id":"IETF RFC 4738","type":"specification","body":"IETF","designation":"RFC 4738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4738.txt","https://www.rfc-editor.org/rfc/rfc4738.pdf"],"folder":"IETF/RFC-4738","files":{"txt":{"path":"standards/IETF/RFC-4738/RFC-4738.txt","sha256":"de0ff01094999940ee59993a73968002eb97788859a8a8d14769df2765942fc3"}},"tags":["nested-reference","unchanged"],"summary":"The Multimedia Internet Keying (MIKEY) specification describes\n several modes of key distribution solution that address multimedia\n scenarios (e.g., SIP calls and Real Time Streaming Protocol (RTSP)\n sessions) using pre-shared keys, public keys, and optionally a\n Diffie-Hellman key exchange. In the public-key mode, the Initiator\n encrypts a random key with the Responder's public key and sends it to\n the Responder. In many communication scenarios, the Initiator may\n not know the Responder's public key, or in some cases the Responder's\n ID (e.g., call forwarding) in advance. We propose a new MIKEY mode\n that works well in such scenarios. This mode also enhances the group\n key management support in MIKEY; it supports member-initiated group\n key download (in contrast to group manager pushing the group keys to\n all members). This document updates RFC 3830 with the RSA-R mode.\n\nIgnjatic, et al","scope_keywords":["4738","authentication","certificate","key","keys","management","timestamp","timestamps","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null}],"search_text":"IETF RFC 4738 The Multimedia Internet Keying (MIKEY) specification describes\n several modes of key distribution solution that address multimedia\n scenarios (e.g., SIP calls and Real Time Streaming Protocol (RTSP)\n sessions) using pre-shared keys, public keys, and optionally a\n Diffie-Hellman key exchange. In the public-key mode, the Initiator\n encrypts a random key with the Responder's public key and sends it to\n the Responder. In many communication scenarios, the Initiator may\n not know the Responder's public key, or in some cases the Responder's\n ID (e.g., call forwarding) in advance. We propose a new MIKEY mode\n that works well in such scenarios. This mode also enhances the group\n key management support in MIKEY; it supports member-initiated group\n key download (in contrast to group manager pushing the group keys to\n all members). This document updates RFC 3830 with the RSA-R mode.\n\nIgnjatic, et al 4738 authentication certificate key keys management timestamp timestamps trust tsp nested-reference unchanged"},{"id":"IETF RFC 4739","type":"specification","body":"IETF","designation":"RFC 4739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4739.txt","https://www.rfc-editor.org/rfc/rfc4739.pdf"],"folder":"IETF/RFC-4739","files":{"txt":{"path":"standards/IETF/RFC-4739/RFC-4739.txt","sha256":"af1d9567408a1fb2aa5f163181f29860d8c4b0b82600de66fceb57223195ca64"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Key Exchange (IKEv2) protocol supports several\n mechanisms for authenticating the parties, including signatures with\n public-key certificates, shared secrets, and Extensible\n Authentication Protocol (EAP) methods. Currently, each endpoint uses\n only one of these mechanisms to authenticate itself. This document\n specifies an extension to IKEv2 that allows the use of multiple\n authentication exchanges, using either different mechanisms or the\n same mechanism. This extension allows, for instance, performing\n certificate-based authentication of the client host followed by an\n EAP authentication of the user. When backend authentication servers\n are used, they can belong to different administrative domains, such\n as the network access provider and the service provider.\n\nEronen & Korhonen Experimental [Page 1]\n\f\nRFC 4739 Multiple Auth. Exchanges in IKEv2 November 2006","scope_keywords":["4739","authentication","authorization","certificate","certificates","credential","credentials","key","keys","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4739 The Internet Key Exchange (IKEv2) protocol supports several\n mechanisms for authenticating the parties, including signatures with\n public-key certificates, shared secrets, and Extensible\n Authentication Protocol (EAP) methods. Currently, each endpoint uses\n only one of these mechanisms to authenticate itself. This document\n specifies an extension to IKEv2 that allows the use of multiple\n authentication exchanges, using either different mechanisms or the\n same mechanism. This extension allows, for instance, performing\n certificate-based authentication of the client host followed by an\n EAP authentication of the user. When backend authentication servers\n are used, they can belong to different administrative domains, such\n as the network access provider and the service provider.\n\nEronen & Korhonen Experimental [Page 1]\n\f\nRFC 4739 Multiple Auth. Exchanges in IKEv2 November 2006 4739 authentication authorization certificate certificates credential credentials key keys signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 4740","type":"specification","body":"IETF","designation":"RFC 4740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4740.txt","https://www.rfc-editor.org/rfc/rfc4740.pdf"],"folder":"IETF/RFC-4740","files":{"txt":{"path":"standards/IETF/RFC-4740/RFC-4740.txt","sha256":"6e1d9f480db21e67059158cf788caa7b52f7e8b6aeb359ec0bf35def4572ac3b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Diameter Session Initiation Protocol\n (SIP) application. This is a Diameter application that allows a\n Diameter client to request authentication and authorization\n information. This application is designed to be used in conjunction\n with SIP and provides a Diameter client co-located with a SIP server,\n with the ability to request the authentication of users and\n authorization of SIP resources usage from a Diameter server.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 4740 Diameter SIP Application November 2006","scope_keywords":["4740","authentication","authorization","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5090","folder":"IETF/RFC-5090","source":"IETF/RFC-5090/RFC-5090.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4740 This document specifies the Diameter Session Initiation Protocol\n (SIP) application. This is a Diameter application that allows a\n Diameter client to request authentication and authorization\n information. This application is designed to be used in conjunction\n with SIP and provides a Diameter client co-located with a SIP server,\n with the ability to request the authentication of users and\n authorization of SIP resources usage from a Diameter server.\n\nGarcia-Martin, et al. Standards Track [Page 1]\n\f\nRFC 4740 Diameter SIP Application November 2006 4740 authentication authorization profile trust nested-reference unchanged"},{"id":"IETF RFC 4741","type":"specification","body":"IETF","designation":"RFC 4741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4741.txt","https://www.rfc-editor.org/rfc/rfc4741.pdf"],"folder":"IETF/RFC-4741","files":{"txt":{"path":"standards/IETF/RFC-4741/RFC-4741.txt","sha256":"c52ff95750b7d9df49f7fedf7454050639ed85ec8ef93b250a0d69c9ca6c86b1"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) defined in this document\n provides mechanisms to install, manipulate, and delete the\n configuration of network devices. It uses an Extensible Markup\n Language (XML)-based data encoding for the configuration data as well\n as the protocol messages. The NETCONF protocol operations are\n realized on top of a simple Remote Procedure Call (RPC) layer.\n\nEnns Standards Track [Page 1]\n\f\nRFC 4741 NETCONF Protocol December 2006","scope_keywords":["4741","attribute","authentication","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4743","folder":"IETF/RFC-4743","source":"IETF/RFC-4743/RFC-4743.txt","version":null},{"body":"IETF","designation":"RFC 4744","folder":"IETF/RFC-4744","source":"IETF/RFC-4744/RFC-4744.txt","version":null},{"body":"IETF","designation":"RFC 5277","folder":"IETF/RFC-5277","source":"IETF/RFC-5277/RFC-5277.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 5717","folder":"IETF/RFC-5717","source":"IETF/RFC-5717/RFC-5717.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 4741 The Network Configuration Protocol (NETCONF) defined in this document\n provides mechanisms to install, manipulate, and delete the\n configuration of network devices. It uses an Extensible Markup\n Language (XML)-based data encoding for the configuration data as well\n as the protocol messages. The NETCONF protocol operations are\n realized on top of a simple Remote Procedure Call (RPC) layer.\n\nEnns Standards Track [Page 1]\n\f\nRFC 4741 NETCONF Protocol December 2006 4741 attribute authentication trust nested-reference unchanged"},{"id":"IETF RFC 4742","type":"specification","body":"IETF","designation":"RFC 4742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4742.txt","https://www.rfc-editor.org/rfc/rfc4742.pdf"],"folder":"IETF/RFC-4742","files":{"txt":{"path":"standards/IETF/RFC-4742/RFC-4742.txt","sha256":"843ad308db050adf895c1d5b4d1995be30dab23c40306d0aa2ef57db1daeea1d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for invoking and running the Network\n Configuration Protocol (NETCONF) within a Secure Shell (SSH) session\n as an SSH subsystem.","scope_keywords":["4742","authentication","encryption","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4741","folder":"IETF/RFC-4741","source":"IETF/RFC-4741/RFC-4741.txt","version":null},{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 4742 This document describes a method for invoking and running the Network\n Configuration Protocol (NETCONF) within a Secure Shell (SSH) session\n as an SSH subsystem. 4742 authentication encryption key keys trust nested-reference unchanged"},{"id":"IETF RFC 4744","type":"specification","body":"IETF","designation":"RFC 4744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4744.txt","https://www.rfc-editor.org/rfc/rfc4744.pdf"],"folder":"IETF/RFC-4744","files":{"txt":{"path":"standards/IETF/RFC-4744/RFC-4744.txt","sha256":"6ebfe60666289078e535121e881f36e3b57dc1d9fde3b627542be93effe05223"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an application protocol mapping for the\n Network Configuration Protocol (NETCONF) over the Blocks Extensible\n Exchange Protocol (BEEP).","scope_keywords":["4744","authentication","encryption","http","key","management","profile","profiles","risk","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4744 This document specifies an application protocol mapping for the\n Network Configuration Protocol (NETCONF) over the Blocks Extensible\n Exchange Protocol (BEEP). 4744 authentication encryption http key management profile profiles risk tls trust nested-reference unchanged"},{"id":"IETF RFC 4745","type":"specification","body":"IETF","designation":"RFC 4745","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4745.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4745.txt","https://www.rfc-editor.org/rfc/rfc4745.pdf"],"folder":"IETF/RFC-4745","files":{"txt":{"path":"standards/IETF/RFC-4745/RFC-4745.txt","sha256":"d7b342927766535e6664365d632ae045ee86a10f7c6703ad4f08abfcff68a393"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for authorization policies\n controlling access to application-specific data. This framework\n combines common location- and presence-specific authorization\n aspects. An XML schema specifies the language in which common policy\n rules are represented. The common policy framework can be extended\n to other application domains.\n\nSchulzrinne, et al. Standards Track [Page 1]\n\f\nRFC 4745 Common Policy February 2007","scope_keywords":["4745","authorization","identification","key","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 4745 This document defines a framework for authorization policies\n controlling access to application-specific data. This framework\n combines common location- and presence-specific authorization\n aspects. An XML schema specifies the language in which common policy\n rules are represented. The common policy framework can be extended\n to other application domains.\n\nSchulzrinne, et al. Standards Track [Page 1]\n\f\nRFC 4745 Common Policy February 2007 4745 authorization identification key policies policy trust nested-reference unchanged"},{"id":"IETF RFC 4756","type":"specification","body":"IETF","designation":"RFC 4756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4756.txt","https://www.rfc-editor.org/rfc/rfc4756.pdf"],"folder":"IETF/RFC-4756","files":{"txt":{"path":"standards/IETF/RFC-4756/RFC-4756.txt","sha256":"d2ade2bb5ca29cb9ce39fbe4339855251364065e592fdf95c330e1711fee9e7e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the semantics that allow for grouping of\n Forward Error Correction (FEC) streams with the protected payload\n streams in Session Description Protocol (SDP). The semantics defined\n in this document are to be used with \"Grouping of Media Lines in the\n Session Description Protocol\" (RFC 3388) to group together \"m\" lines\n in the same session.","scope_keywords":["4756","algorithm","attribute","identification","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null}],"search_text":"IETF RFC 4756 This document defines the semantics that allow for grouping of\n Forward Error Correction (FEC) streams with the protected payload\n streams in Session Description Protocol (SDP). The semantics defined\n in this document are to be used with \"Grouping of Media Lines in the\n Session Description Protocol\" (RFC 3388) to group together \"m\" lines\n in the same session. 4756 algorithm attribute identification key trust nested-reference unchanged"},{"id":"IETF RFC 4759","type":"specification","body":"IETF","designation":"RFC 4759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4759.txt","https://www.rfc-editor.org/rfc/rfc4759.pdf"],"folder":"IETF/RFC-4759","files":{"txt":{"path":"standards/IETF/RFC-4759/RFC-4759.txt","sha256":"3edf3e32200326cc127acac89692d3b9f17dfefb6ede83f100d6e99acbb6751f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new parameter \"enumdi\" for the \"tel\" Uniform\n Resource Identifier (URI) to support the handling of ENUM queries in\n Voice over Internet Protocol (VoIP) network elements. A VoIP network\n element may receive a URI containing an E.164 number, where that URI\n contains an \"enumdi\" parameter. The presence of the \"enumdi\"\n parameter indicates that an ENUM query has already been performed on\n the E.164 number by a previous VoIP network element. Equally, if a\n VoIP network element sends such a URI, it asserts that an ENUM query\n has been carried out on this number.\n\nStastny, et al. Standards Track [Page 1]\n\f\nRFC 4759 ENUM Dip Indicator \"tel\" URI parameter November 2006","scope_keywords":["4759","key","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null}],"search_text":"IETF RFC 4759 This document defines a new parameter \"enumdi\" for the \"tel\" Uniform\n Resource Identifier (URI) to support the handling of ENUM queries in\n Voice over Internet Protocol (VoIP) network elements. A VoIP network\n element may receive a URI containing an E.164 number, where that URI\n contains an \"enumdi\" parameter. The presence of the \"enumdi\"\n parameter indicates that an ENUM query has already been performed on\n the E.164 number by a previous VoIP network element. Equally, if a\n VoIP network element sends such a URI, it asserts that an ENUM query\n has been carried out on this number.\n\nStastny, et al. Standards Track [Page 1]\n\f\nRFC 4759 ENUM Dip Indicator \"tel\" URI parameter November 2006 4759 key policy trust nested-reference unchanged"},{"id":"IETF RFC 4760","type":"specification","body":"IETF","designation":"RFC 4760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4760.txt","https://www.rfc-editor.org/rfc/rfc4760.pdf"],"folder":"IETF/RFC-4760","files":{"txt":{"path":"standards/IETF/RFC-4760/RFC-4760.txt","sha256":"ecddcc732da523f7d6bc048b2a5e921ed505c84279b0506dff4a23d50b43633a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Bates\nRequest for Comments: 4760 Cisco Systems\nObsoletes: 2858 R. Chandra\nCategory: Standards Track Sonoa Systems\n D. Katz\n Y. Rekhter\n Juniper Networks\n January 2007\n\n Multiprotocol Extensions for BGP-4\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document defines extensions to BGP-4 to enable it to carry\n routing information for multiple Network Layer protocols (e.g., IPv6,\n IPX, L3VPN, etc.). The extensions are backward compatible - a router\n that supports the extensions can ","scope_keywords":["4760","attribute","attributes","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4797","folder":"IETF/RFC-4797","source":"IETF/RFC-4797/RFC-4797.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5015","folder":"IETF/RFC-5015","source":"IETF/RFC-5015/RFC-5015.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5492","folder":"IETF/RFC-5492","source":"IETF/RFC-5492/RFC-5492.txt","version":null},{"body":"IETF","designation":"RFC 5512","folder":"IETF/RFC-5512","source":"IETF/RFC-5512/RFC-5512.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6836","folder":"IETF/RFC-6836","source":"IETF/RFC-6836/RFC-6836.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 4760 Network Working Group T. Bates\nRequest for Comments: 4760 Cisco Systems\nObsoletes: 2858 R. Chandra\nCategory: Standards Track Sonoa Systems\n D. Katz\n Y. Rekhter\n Juniper Networks\n January 2007\n\n Multiprotocol Extensions for BGP-4\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document defines extensions to BGP-4 to enable it to carry\n routing information for multiple Network Layer protocols (e.g., IPv6,\n IPX, L3VPN, etc.). The extensions are backward compatible - a router\n that supports the extensions can  4760 attribute attributes key path trust nested-reference unchanged"},{"id":"IETF RFC 4761","type":"specification","body":"IETF","designation":"RFC 4761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4761.txt","https://www.rfc-editor.org/rfc/rfc4761.pdf"],"folder":"IETF/RFC-4761","files":{"txt":{"path":"standards/IETF/RFC-4761/RFC-4761.txt","sha256":"83fddfe55390b04c36580c919799c52f8d6689807b2f34c9d48784a5ca4cb25e"}},"tags":["nested-reference","unchanged"],"summary":"Virtual Private LAN Service (VPLS), also known as Transparent LAN\n Service and Virtual Private Switched Network service, is a useful\n Service Provider offering. The service offers a Layer 2 Virtual\n Private Network (VPN); however, in the case of VPLS, the customers in\n the VPN are connected by a multipoint Ethernet LAN, in contrast to\n the usual Layer 2 VPNs, which are point-to-point in nature.\n\n This document describes the functions required to offer VPLS, a\n mechanism for signaling a VPLS, and rules for forwarding VPLS frames\n across a packet switched network.\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4761 BGP Auto-Discovery and Signaling for VPLS January 2007","scope_keywords":["4761","path","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7365","folder":"IETF/RFC-7365","source":"IETF/RFC-7365/RFC-7365.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 4761 Virtual Private LAN Service (VPLS), also known as Transparent LAN\n Service and Virtual Private Switched Network service, is a useful\n Service Provider offering. The service offers a Layer 2 Virtual\n Private Network (VPN); however, in the case of VPLS, the customers in\n the VPN are connected by a multipoint Ethernet LAN, in contrast to\n the usual Layer 2 VPNs, which are point-to-point in nature.\n\n This document describes the functions required to offer VPLS, a\n mechanism for signaling a VPLS, and rules for forwarding VPLS frames\n across a packet switched network.\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 4761 BGP Auto-Discovery and Signaling for VPLS January 2007 4761 path qualified trust nested-reference unchanged"},{"id":"IETF RFC 4771","type":"specification","body":"IETF","designation":"RFC 4771","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4771.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4771.txt","https://www.rfc-editor.org/rfc/rfc4771.pdf"],"folder":"IETF/RFC-4771","files":{"txt":{"path":"standards/IETF/RFC-4771/RFC-4771.txt","sha256":"39535a42ea478332116a00030122566fef6a551efe5534d5b4c43431936ce9f7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an integrity transform for Secure Real-time\n Transport Protocol (SRTP; see RFC 3711), which allows the roll-over\n counter (ROC) to be transmitted in SRTP packets as part of the\n authentication tag. The need for sending the ROC in SRTP packets\n arises in situations where the receiver joins an ongoing SRTP session\n and needs to quickly and robustly synchronize. The mechanism also\n enhances SRTP operation in cases where there is a risk of losing\n sender-receiver synchronization.","scope_keywords":["4771","authentication","key","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5159","folder":"IETF/RFC-5159","source":"IETF/RFC-5159/RFC-5159.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 4771 This document defines an integrity transform for Secure Real-time\n Transport Protocol (SRTP; see RFC 3711), which allows the roll-over\n counter (ROC) to be transmitted in SRTP packets as part of the\n authentication tag. The need for sending the ROC in SRTP packets\n arises in situations where the receiver joins an ongoing SRTP session\n and needs to quickly and robustly synchronize. The mechanism also\n enhances SRTP operation in cases where there is a risk of losing\n sender-receiver synchronization. 4771 authentication key risk trust nested-reference unchanged"},{"id":"IETF RFC 4776","type":"specification","body":"IETF","designation":"RFC 4776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4776.txt","https://www.rfc-editor.org/rfc/rfc4776.pdf"],"folder":"IETF/RFC-4776","files":{"txt":{"path":"standards/IETF/RFC-4776/RFC-4776.txt","sha256":"fe1f91d6874c826dd447a5caddcb9952a90ba1dd32ac822b872713134cb14d94"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) option containing the civic location of the client or the\n DHCP server. The Location Configuration Information (LCI) includes\n information about the country, administrative units such as states,\n provinces, and cities, as well as street addresses, postal community\n names, and building information. The option allows multiple\n renditions of the same address in different scripts and languages.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 4776 DHCP Civic November 2006","scope_keywords":["4776","delivery","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null}],"search_text":"IETF RFC 4776 This document specifies a Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) option containing the civic location of the client or the\n DHCP server. The Location Configuration Information (LCI) includes\n information about the country, administrative units such as states,\n provinces, and cities, as well as street addresses, postal community\n names, and building information. The option allows multiple\n renditions of the same address in different scripts and languages.\n\nSchulzrinne Standards Track [Page 1]\n\f\nRFC 4776 DHCP Civic November 2006 4776 delivery pid trust nested-reference unchanged"},{"id":"IETF RFC 4780","type":"specification","body":"IETF","designation":"RFC 4780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4780.txt","https://www.rfc-editor.org/rfc/rfc4780.pdf"],"folder":"IETF/RFC-4780","files":{"txt":{"path":"standards/IETF/RFC-4780/RFC-4780.txt","sha256":"606ae67a699761ef286dd3e3466529fc1aafb2f3a20a64e68346627b9068f3db"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n manage Session Initiation Protocol (SIP) entities, which include User\n Agents, and Proxy, Redirect and Registrar servers.\n\nLingle, et al. Standards Track [Page 1]\n\f\nRFC 4780 SIP MIB Modules April 2007","scope_keywords":["4780","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4780 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that are used to\n manage Session Initiation Protocol (SIP) entities, which include User\n Agents, and Proxy, Redirect and Registrar servers.\n\nLingle, et al. Standards Track [Page 1]\n\f\nRFC 4780 SIP MIB Modules April 2007 4780 key management trust nested-reference unchanged"},{"id":"IETF RFC 4781","type":"specification","body":"IETF","designation":"RFC 4781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4781.txt","https://www.rfc-editor.org/rfc/rfc4781.pdf"],"folder":"IETF/RFC-4781","files":{"txt":{"path":"standards/IETF/RFC-4781/RFC-4781.txt","sha256":"0e26b4070a74c059c9a0bbd9159013a754003d3ac121a1a9f7f5e051fe7f25a5"}},"tags":["nested-reference","unchanged"],"summary":"A mechanism for BGP that helps minimize the negative effects on\n routing caused by BGP restart has already been developed and is\n described in a separate document (\"Graceful Restart Mechanism for\n BGP\"). This document extends this mechanism to minimize the negative\n effects on MPLS forwarding caused by the Label Switching Router's\n (LSR's) control plane restart, and specifically by the restart of its\n BGP component when BGP is used to carry MPLS labels and the LSR is\n capable of preserving the MPLS forwarding state across the restart.\n\n The mechanism described in this document is agnostic with respect to\n the types of the addresses carried in the BGP Network Layer\n Reachability Information (NLRI) field. As such, it works in\n conjunction with any of the address families that could be carried in\n BGP (e.g., IPv4, IPv6, etc.).\n\nRekhter & Aggarwal Standards Track [Page 1]\n\f\nRFC 4781 Graceful","scope_keywords":["4781","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null}],"search_text":"IETF RFC 4781 A mechanism for BGP that helps minimize the negative effects on\n routing caused by BGP restart has already been developed and is\n described in a separate document (\"Graceful Restart Mechanism for\n BGP\"). This document extends this mechanism to minimize the negative\n effects on MPLS forwarding caused by the Label Switching Router's\n (LSR's) control plane restart, and specifically by the restart of its\n BGP component when BGP is used to carry MPLS labels and the LSR is\n capable of preserving the MPLS forwarding state across the restart.\n\n The mechanism described in this document is agnostic with respect to\n the types of the addresses carried in the BGP Network Layer\n Reachability Information (NLRI) field. As such, it works in\n conjunction with any of the address families that could be carried in\n BGP (e.g., IPv4, IPv6, etc.).\n\nRekhter & Aggarwal Standards Track [Page 1]\n\f\nRFC 4781 Graceful 4781 key path nested-reference unchanged"},{"id":"IETF RFC 4783","type":"specification","body":"IETF","designation":"RFC 4783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4783.txt","https://www.rfc-editor.org/rfc/rfc4783.pdf"],"folder":"IETF/RFC-4783","files":{"txt":{"path":"standards/IETF/RFC-4783/RFC-4783.txt","sha256":"dc5e95cab4932e422f0c01966899f51d293392b5e5bfeb6dfaf7ad83b3b91f54"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to Generalized MPLS (Multi-\n Protocol Label Switching) signaling to support communication of alarm\n information. GMPLS signaling already supports the control of alarm\n reporting, but not the communication of alarm information. This\n document presents both a functional description and GMPLS-RSVP\n specifics of such an extension. This document also proposes\n modification of the RSVP ERROR_SPEC object.\n\n This document updates RFC 3473, \"Generalized Multi-Protocol Label\n Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic\n Engineering (RSVP-TE) Extensions\", through the addition of new,\n optional protocol elements. It does not change, and is fully\n backward compatible with, the procedures specified in RFC 3473.\n\nBerger Standards Track [Page 1]\n\f\nRFC 4783 GMPLS - Communication of Alarm Information December 2006","scope_keywords":["4783","key","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4783 This document describes an extension to Generalized MPLS (Multi-\n Protocol Label Switching) signaling to support communication of alarm\n information. GMPLS signaling already supports the control of alarm\n reporting, but not the communication of alarm information. This\n document presents both a functional description and GMPLS-RSVP\n specifics of such an extension. This document also proposes\n modification of the RSVP ERROR_SPEC object.\n\n This document updates RFC 3473, \"Generalized Multi-Protocol Label\n Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic\n Engineering (RSVP-TE) Extensions\", through the addition of new,\n optional protocol elements. It does not change, and is fully\n backward compatible with, the procedures specified in RFC 3473.\n\nBerger Standards Track [Page 1]\n\f\nRFC 4783 GMPLS - Communication of Alarm Information December 2006 4783 key path policy trust nested-reference unchanged"},{"id":"IETF RFC 4785","type":"specification","body":"IETF","designation":"RFC 4785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4785.txt","https://www.rfc-editor.org/rfc/rfc4785.pdf"],"folder":"IETF/RFC-4785","files":{"txt":{"path":"standards/IETF/RFC-4785/RFC-4785.txt","sha256":"71f97643871e42dae04ecfc65bdaa131aa136fa9b0e6c2bf99d425d62738dc0e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies authentication-only ciphersuites (with no\n encryption) for the Pre-Shared Key (PSK) based Transport Layer\n Security (TLS) protocol. These ciphersuites are useful when\n authentication and integrity protection is desired, but\n confidentiality is not needed or not permitted.","scope_keywords":["4785","authentication","certificate","certificates","encryption","hash","key","keys","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 5489","folder":"IETF/RFC-5489","source":"IETF/RFC-5489/RFC-5489.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4785 This document specifies authentication-only ciphersuites (with no\n encryption) for the Pre-Shared Key (PSK) based Transport Layer\n Security (TLS) protocol. These ciphersuites are useful when\n authentication and integrity protection is desired, but\n confidentiality is not needed or not permitted. 4785 authentication certificate certificates encryption hash key keys license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 4791","type":"specification","body":"IETF","designation":"RFC 4791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4791.txt","https://www.rfc-editor.org/rfc/rfc4791.pdf"],"folder":"IETF/RFC-4791","files":{"txt":{"path":"standards/IETF/RFC-4791/RFC-4791.txt","sha256":"e1161c41f2839649c6325ffde2c62e44e9ed39b71a3b251f4230ffce045c60ea"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to the Web Distributed Authoring and\n Versioning (WebDAV) protocol to specify a standard way of accessing,\n managing, and sharing calendaring and scheduling information based on\n the iCalendar format. This document defines the \"calendar-access\"\n feature of CalDAV.\n\nDaboo, et al. Standards Track [Page 1]\n\f\nRFC 4791 CalDAV March 2007","scope_keywords":["4791","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 6585","folder":"IETF/RFC-6585","source":"IETF/RFC-6585/RFC-6585.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 4791 This document defines extensions to the Web Distributed Authoring and\n Versioning (WebDAV) protocol to specify a standard way of accessing,\n managing, and sharing calendaring and scheduling information based on\n the iCalendar format. This document defines the \"calendar-access\"\n feature of CalDAV.\n\nDaboo, et al. Standards Track [Page 1]\n\f\nRFC 4791 CalDAV March 2007 4791 trust nested-reference unchanged"},{"id":"IETF RFC 4796","type":"specification","body":"IETF","designation":"RFC 4796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4796.txt","https://www.rfc-editor.org/rfc/rfc4796.pdf"],"folder":"IETF/RFC-4796","files":{"txt":{"path":"standards/IETF/RFC-4796/RFC-4796.txt","sha256":"5270cd281377fedc16d9edcf12646f5e68fab40770892388e6ff78cf10fcbfdf"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Session Description Protocol (SDP) media-\n level attribute, 'content'. The 'content' attribute defines the\n content of the media stream to a more detailed level than the media\n description line. The sender of an SDP session description can\n attach the 'content' attribute to one or more media streams. The\n receiving application can then treat each media stream differently\n (e.g., show it on a big or small screen) based on its content.","scope_keywords":["4796","attribute","attributes","audit","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 4796 This document defines a new Session Description Protocol (SDP) media-\n level attribute, 'content'. The 'content' attribute defines the\n content of the media stream to a more detailed level than the media\n description line. The sender of an SDP session description can\n attach the 'content' attribute to one or more media streams. The\n receiving application can then treat each media stream differently\n (e.g., show it on a big or small screen) based on its content. 4796 attribute attributes audit key presentation trust nested-reference unchanged"},{"id":"IETF RFC 4797","type":"specification","body":"IETF","designation":"RFC 4797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4797.txt","https://www.rfc-editor.org/rfc/rfc4797.pdf"],"folder":"IETF/RFC-4797","files":{"txt":{"path":"standards/IETF/RFC-4797/RFC-4797.txt","sha256":"c461dc7f8711df58b177b53c0b6d58f5c205669748db96248c60462346435150"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an implementation strategy for BGP/MPLS IP\n Virtual Private Networks (VPNs) in which the outermost MPLS label\n (i.e., the tunnel label) is replaced with either an IP header or an\n IP header with Generic Routing Encapsulation (GRE).\n\n The implementation strategy described herein enables the deployment\n of BGP/MPLS IP VPN technology in networks whose edge devices are MPLS\n and VPN aware, but whose interior devices are not.\n\nRekhter, et al. Informational [Page 1]\n\f\nRFC 4797 L3VPN GRE January 2007","scope_keywords":["4797","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null}],"search_text":"IETF RFC 4797 This document describes an implementation strategy for BGP/MPLS IP\n Virtual Private Networks (VPNs) in which the outermost MPLS label\n (i.e., the tunnel label) is replaced with either an IP header or an\n IP header with Generic Routing Encapsulation (GRE).\n\n The implementation strategy described herein enables the deployment\n of BGP/MPLS IP VPN technology in networks whose edge devices are MPLS\n and VPN aware, but whose interior devices are not.\n\nRekhter, et al. Informational [Page 1]\n\f\nRFC 4797 L3VPN GRE January 2007 4797 key path trust nested-reference unchanged"},{"id":"IETF RFC 4798","type":"specification","body":"IETF","designation":"RFC 4798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4798.txt","https://www.rfc-editor.org/rfc/rfc4798.pdf"],"folder":"IETF/RFC-4798","files":{"txt":{"path":"standards/IETF/RFC-4798/RFC-4798.txt","sha256":"160b8374834e7789f9fc34d4bc23c5c23dfa521519230a1686760190ba444b5e"}},"tags":["nested-reference","unchanged"],"summary":"This document explains how to interconnect IPv6 islands over a\n Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This\n approach relies on IPv6 Provider Edge routers (6PE), which are Dual\n Stack in order to connect to IPv6 islands and to the MPLS core, which\n is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6\n reachability information transparently over the core using the\n Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing\n so, the BGP Next Hop field is used to convey the IPv4 address of the\n 6PE router so that dynamically established IPv4-signaled MPLS Label\n Switched Paths (LSPs) can be used without explicit tunnel\n configuration.\n\nDe Clercq, et al. Standards Track [Page 1]\n\f\nRFC 4798 6PE February 2007","scope_keywords":["4798","identification","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null}],"search_text":"IETF RFC 4798 This document explains how to interconnect IPv6 islands over a\n Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This\n approach relies on IPv6 Provider Edge routers (6PE), which are Dual\n Stack in order to connect to IPv6 islands and to the MPLS core, which\n is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6\n reachability information transparently over the core using the\n Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing\n so, the BGP Next Hop field is used to convey the IPv4 address of the\n 6PE router so that dynamically established IPv4-signaled MPLS Label\n Switched Paths (LSPs) can be used without explicit tunnel\n configuration.\n\nDe Clercq, et al. Standards Track [Page 1]\n\f\nRFC 4798 6PE February 2007 4798 identification path trust nested-reference unchanged"},{"id":"IETF RFC 4802","type":"specification","body":"IETF","designation":"RFC 4802","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4802.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4802.txt","https://www.rfc-editor.org/rfc/rfc4802.pdf"],"folder":"IETF/RFC-4802","files":{"txt":{"path":"standards/IETF/RFC-4802/RFC-4802.txt","sha256":"5f5897d83bc7ed47d9648dafd9e0dbc237875daecb58269e756519e54727d580"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Generalized\n Multiprotocol Label Switching (GMPLS)-based traffic engineering.\n\nNadeau & Farrel Standards Track [Page 1]\n\f\nRFC 4802 GMPLS TE MIB February 2007","scope_keywords":["4802","key","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 4802 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for Generalized\n Multiprotocol Label Switching (GMPLS)-based traffic engineering.\n\nNadeau & Farrel Standards Track [Page 1]\n\f\nRFC 4802 GMPLS TE MIB February 2007 4802 key management path trust nested-reference unchanged"},{"id":"IETF RFC 4803","type":"specification","body":"IETF","designation":"RFC 4803","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4803.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4803.txt","https://www.rfc-editor.org/rfc/rfc4803.pdf"],"folder":"IETF/RFC-4803","files":{"txt":{"path":"standards/IETF/RFC-4803/RFC-4803.txt","sha256":"ffc2169d4c2d9cbc6e0fe99bf55c3ec89b9498ac42647fb7df4b3617ebdd724e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor a Generalized Multiprotocol Label Switching (GMPLS) Label\n Switching Router (LSR).\n\nNadeau & Farrel Standards Track [Page 1]\n\f\nRFC 4803 GMPLS LSR MIB February 2007","scope_keywords":["4803","key","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4803 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects to configure and/or\n monitor a Generalized Multiprotocol Label Switching (GMPLS) Label\n Switching Router (LSR).\n\nNadeau & Farrel Standards Track [Page 1]\n\f\nRFC 4803 GMPLS LSR MIB February 2007 4803 key management path trust nested-reference unchanged"},{"id":"IETF RFC 4806","type":"specification","body":"IETF","designation":"RFC 4806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4806.txt","https://www.rfc-editor.org/rfc/rfc4806.pdf"],"folder":"IETF/RFC-4806","files":{"txt":{"path":"standards/IETF/RFC-4806/RFC-4806.txt","sha256":"0a8fea9878ed3df13cd91f418608391a2eb91a90b10f6db010a31a46973edd53"}},"tags":["nested-reference","unchanged"],"summary":"While the Internet Key Exchange Protocol version 2 (IKEv2) supports\n public key based authentication, the corresponding use of in-band\n Certificate Revocation Lists (CRL) is problematic due to unbounded\n CRL size. The size of an Online Certificate Status Protocol (OCSP)\n response is however well-bounded and small. This document defines\n the \"OCSP Content\" extension to IKEv2. A CERTREQ payload with \"OCSP\n Content\" identifies zero or more trusted OCSP responders and is a\n request for inclusion of an OCSP response in the IKEv2 handshake. A\n cooperative recipient of such a request responds with a CERT payload\n containing the appropriate OCSP response. This content is\n recognizable via the same \"OCSP Content\" identifier.\n\n When certificates are used with IKEv2, the communicating peers need a\n mechanism to determine the revocation status of the peer's\n certificate. OCSP is one such mechanism. ","scope_keywords":["4806","authentication","certificate","certificates","crl","hash","key","ocsp","policy","revocation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 4806 While the Internet Key Exchange Protocol version 2 (IKEv2) supports\n public key based authentication, the corresponding use of in-band\n Certificate Revocation Lists (CRL) is problematic due to unbounded\n CRL size. The size of an Online Certificate Status Protocol (OCSP)\n response is however well-bounded and small. This document defines\n the \"OCSP Content\" extension to IKEv2. A CERTREQ payload with \"OCSP\n Content\" identifies zero or more trusted OCSP responders and is a\n request for inclusion of an OCSP response in the IKEv2 handshake. A\n cooperative recipient of such a request responds with a CERT payload\n containing the appropriate OCSP response. This content is\n recognizable via the same \"OCSP Content\" identifier.\n\n When certificates are used with IKEv2, the communicating peers need a\n mechanism to determine the revocation status of the peer's\n certificate. OCSP is one such mechanism.  4806 authentication certificate certificates crl hash key ocsp policy revocation trust nested-reference unchanged"},{"id":"IETF RFC 4809","type":"specification","body":"IETF","designation":"RFC 4809","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4809.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4809.txt","https://www.rfc-editor.org/rfc/rfc4809.pdf"],"folder":"IETF/RFC-4809","files":{"txt":{"path":"standards/IETF/RFC-4809/RFC-4809.txt","sha256":"7d7a471f4febfc477f6c8cb2783263787c57d33b7b64eccf906b11a80cf47ed8"}},"tags":["nested-reference","unchanged"],"summary":"This informational document describes and identifies the requirements\n for transactions to handle Public Key Certificate (PKC) lifecycle\n transactions between Internet Protocol Security (IPsec) Virtual\n Private Network (VPN) Systems using Internet Key Exchange (IKE)\n (versions 1 and 2) and Public Key Infrastructure (PKI) Systems.\n These requirements are designed to meet the needs of enterprise-scale\n IPsec VPN deployments. It is intended that a standards track profile\n of a management protocol will be created to address many of these\n requirements.\n\nBonatti, et al. Informational [Page 1]\n\f\nRFC 4809 Reqs for IPsec Certificate Mgmt Profile February 2007","scope_keywords":["4809","authorization","certificate","key","keys","management","path","pki","profile","revocation","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4809 This informational document describes and identifies the requirements\n for transactions to handle Public Key Certificate (PKC) lifecycle\n transactions between Internet Protocol Security (IPsec) Virtual\n Private Network (VPN) Systems using Internet Key Exchange (IKE)\n (versions 1 and 2) and Public Key Infrastructure (PKI) Systems.\n These requirements are designed to meet the needs of enterprise-scale\n IPsec VPN deployments. It is intended that a standards track profile\n of a management protocol will be created to address many of these\n requirements.\n\nBonatti, et al. Informational [Page 1]\n\f\nRFC 4809 Reqs for IPsec Certificate Mgmt Profile February 2007 4809 authorization certificate key keys management path pki profile revocation trust validation nested-reference unchanged"},{"id":"IETF RFC 4817","type":"specification","body":"IETF","designation":"RFC 4817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4817.txt","https://www.rfc-editor.org/rfc/rfc4817.pdf"],"folder":"IETF/RFC-4817","files":{"txt":{"path":"standards/IETF/RFC-4817/RFC-4817.txt","sha256":"08cef65ecc97e33a3e354f3dbde20e88fb4a044b1027669bbfae58d20168258f"}},"tags":["nested-reference","unchanged"],"summary":"The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines a protocol\n for tunneling a variety of payload types over IP networks. This\n document defines how to carry an MPLS label stack and its payload\n over the L2TPv3 data encapsulation. This enables an application that\n traditionally requires an MPLS-enabled core network, to utilize an\n L2TPv3 encapsulation over an IP network instead.\n\nTownsley, et al. Standards Track [Page 1]\n\f\nRFC 4817 MPLS over L2TPv3 March 2007","scope_keywords":["4817","key","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null}],"search_text":"IETF RFC 4817 The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines a protocol\n for tunneling a variety of payload types over IP networks. This\n document defines how to carry an MPLS label stack and its payload\n over the L2TPv3 data encapsulation. This enables an application that\n traditionally requires an MPLS-enabled core network, to utilize an\n L2TPv3 encapsulation over an IP network instead.\n\nTownsley, et al. Standards Track [Page 1]\n\f\nRFC 4817 MPLS over L2TPv3 March 2007 4817 key subject trust validation nested-reference unchanged"},{"id":"IETF RFC 4818","type":"specification","body":"IETF","designation":"RFC 4818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4818.txt","https://www.rfc-editor.org/rfc/rfc4818.pdf"],"folder":"IETF/RFC-4818","files":{"txt":{"path":"standards/IETF/RFC-4818/RFC-4818.txt","sha256":"04fb725055a6bfe7fa94bd19469109f56c147554908114bb568760a421eace7b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a RADIUS (Remote Authentication Dial In User\n Service) attribute that carries an IPv6 prefix that is to be\n delegated to the user. This attribute is usable within either RADIUS\n or Diameter.\n\nSalowey & Droms Standards Track [Page 1]\n\f\nRFC 4818 Delegated-IPv6-Prefix Attribute April 2007\n\n1. Introduction\n\n This document defines the Delegated-IPv6-Prefix attribute as a RADIUS\n [1] attribute that carries an IPv6 prefix to be delegated to the\n user, for use in the user's network. For example, the prefix in a\n Delegated-IPv6-Prefix attribute can be delegated to another node\n through DHCP Prefix Delegation [2].\n\n The Delegated-IPv6-Prefix attribute can be used in DHCP Prefix\n Delegation between the delegating router and a RADIUS server, as\n illustrated in the following message sequence.\n\n Requesting Router Delegating Router RADIUS Server\n | | |\n |-Solicit------------>| |\n ","scope_keywords":["4818","attribute","attributes","authentication","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5080","folder":"IETF/RFC-5080","source":"IETF/RFC-5080/RFC-5080.txt","version":null},{"body":"IETF","designation":"RFC 5176","folder":"IETF/RFC-5176","source":"IETF/RFC-5176/RFC-5176.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4818 This document defines a RADIUS (Remote Authentication Dial In User\n Service) attribute that carries an IPv6 prefix that is to be\n delegated to the user. This attribute is usable within either RADIUS\n or Diameter.\n\nSalowey & Droms Standards Track [Page 1]\n\f\nRFC 4818 Delegated-IPv6-Prefix Attribute April 2007\n\n1. Introduction\n\n This document defines the Delegated-IPv6-Prefix attribute as a RADIUS\n [1] attribute that carries an IPv6 prefix to be delegated to the\n user, for use in the user's network. For example, the prefix in a\n Delegated-IPv6-Prefix attribute can be delegated to another node\n through DHCP Prefix Delegation [2].\n\n The Delegated-IPv6-Prefix attribute can be used in DHCP Prefix\n Delegation between the delegating router and a RADIUS server, as\n illustrated in the following message sequence.\n\n Requesting Router Delegating Router RADIUS Server\n | | |\n |-Solicit------------>| |\n  4818 attribute attributes authentication key trust nested-reference unchanged"},{"id":"IETF RFC 4820","type":"specification","body":"IETF","designation":"RFC 4820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4820.txt","https://www.rfc-editor.org/rfc/rfc4820.pdf"],"folder":"IETF/RFC-4820","files":{"txt":{"path":"standards/IETF/RFC-4820/RFC-4820.txt","sha256":"c3cc524aa1b6e2441675a8b7ed4f4856eb303a193f4a1383dc7f581c33d33d53"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a padding chunk and a padding parameter and\n describes the required receiver side procedures. The padding chunk\n is used to pad a Stream Control Transmission Protocol (SCTP) packet\n to an arbitrary size. The padding parameter is used to pad an SCTP\n INIT chunk to an arbitrary size.","scope_keywords":["4820","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 5062","folder":"IETF/RFC-5062","source":"IETF/RFC-5062/RFC-5062.txt","version":null},{"body":"IETF","designation":"RFC 6096","folder":"IETF/RFC-6096","source":"IETF/RFC-6096/RFC-6096.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null}],"search_text":"IETF RFC 4820 This document defines a padding chunk and a padding parameter and\n describes the required receiver side procedures. The padding chunk\n is used to pad a Stream Control Transmission Protocol (SCTP) packet\n to an arbitrary size. The padding parameter is used to pad an SCTP\n INIT chunk to an arbitrary size. 4820 key path trust nested-reference unchanged"},{"id":"IETF RFC 4825","type":"specification","body":"IETF","designation":"RFC 4825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4825.txt","https://www.rfc-editor.org/rfc/rfc4825.pdf"],"folder":"IETF/RFC-4825","files":{"txt":{"path":"standards/IETF/RFC-4825/RFC-4825.txt","sha256":"1f19a540473c7d5accd076fafb1a5494a8e17174b3f833e25fba3fa71f986256"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the Extensible Markup Language (XML)\n Configuration Access Protocol (XCAP). XCAP allows a client to read,\n write, and modify application configuration data stored in XML format\n on a server. XCAP maps XML document sub-trees and element attributes\n to HTTP URIs, so that these components can be directly accessed by\n HTTP.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4825 XCAP May 2007","scope_keywords":["4825","attribute","attributes","authorization","http","management","policies","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 4827","folder":"IETF/RFC-4827","source":"IETF/RFC-4827/RFC-4827.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null}],"search_text":"IETF RFC 4825 This specification defines the Extensible Markup Language (XML)\n Configuration Access Protocol (XCAP). XCAP allows a client to read,\n write, and modify application configuration data stored in XML format\n on a server. XCAP maps XML document sub-trees and element attributes\n to HTTP URIs, so that these components can be directly accessed by\n HTTP.\n\nRosenberg Standards Track [Page 1]\n\f\nRFC 4825 XCAP May 2007 4825 attribute attributes authorization http management policies trust validation nested-reference unchanged"},{"id":"IETF RFC 4826","type":"specification","body":"IETF","designation":"RFC 4826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4826.txt","https://www.rfc-editor.org/rfc/rfc4826.pdf"],"folder":"IETF/RFC-4826","files":{"txt":{"path":"standards/IETF/RFC-4826/RFC-4826.txt","sha256":"cc6bd28e116663eb8d60cb606c1715ebc3787f8b1359a16005f62eb215c0a04b"}},"tags":["nested-reference","unchanged"],"summary":"In multimedia communications, presence, and instant messaging\n systems, there is a need to define Uniform Resource Identifiers\n (URIs) that represent services that are associated with a group of\n users. One example is a resource list service. If a user sends a\n Session Initiation Protocol (SIP) SUBSCRIBE message to the URI\n representing the resource list service, the server will obtain the\n state of the users in the associated group, and provide it to the\n sender. To facilitate definition of these services, this\n specification defines two Extensible Markup Language (XML) documents.\n One document contains service URIs, along with their service\n definition and a reference to the associated group of users. The\n second document contains the user lists that are referenced from the\n first. This list of users can be utilized by other applications and\n services. Both documents can be created and","scope_keywords":["4826","authorization","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4826 In multimedia communications, presence, and instant messaging\n systems, there is a need to define Uniform Resource Identifiers\n (URIs) that represent services that are associated with a group of\n users. One example is a resource list service. If a user sends a\n Session Initiation Protocol (SIP) SUBSCRIBE message to the URI\n representing the resource list service, the server will obtain the\n state of the users in the associated group, and provide it to the\n sender. To facilitate definition of these services, this\n specification defines two Extensible Markup Language (XML) documents.\n One document contains service URIs, along with their service\n definition and a reference to the associated group of users. The\n second document contains the user lists that are referenced from the\n first. This list of users can be utilized by other applications and\n services. Both documents can be created and 4826 authorization policies trust nested-reference unchanged"},{"id":"IETF RFC 4827","type":"specification","body":"IETF","designation":"RFC 4827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4827.txt","https://www.rfc-editor.org/rfc/rfc4827.pdf"],"folder":"IETF/RFC-4827","files":{"txt":{"path":"standards/IETF/RFC-4827/RFC-4827.txt","sha256":"ead0df1aefba4906804ca3193abedee403fdc030fd7a7fb924cdedd252713598"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a usage of the Extensible Markup Language\n (XML) Configuration Access Protocol (XCAP) for manipulating the\n contents of Presence Information Data Format (PIDF) based presence\n documents. It is intended to be used in Session Initiation Protocol\n (SIP) based presence systems, where the Event State Compositor can\n use the XCAP-manipulated presence document as one of the inputs on\n which it builds the overall presence state for the presentity.\n\nIsomaki & Leppanen Standards Track [Page 1]\n\f\nRFC 4827 XCAP for Manipulating Presence Document May 2007","scope_keywords":["4827","authorization","key","pid","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4827 This document describes a usage of the Extensible Markup Language\n (XML) Configuration Access Protocol (XCAP) for manipulating the\n contents of Presence Information Data Format (PIDF) based presence\n documents. It is intended to be used in Session Initiation Protocol\n (SIP) based presence systems, where the Event State Compositor can\n use the XCAP-manipulated presence document as one of the inputs on\n which it builds the overall presence state for the presentity.\n\nIsomaki & Leppanen Standards Track [Page 1]\n\f\nRFC 4827 XCAP for Manipulating Presence Document May 2007 4827 authorization key pid policies trust nested-reference unchanged"},{"id":"IETF RFC 4847","type":"specification","body":"IETF","designation":"RFC 4847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4847.txt","https://www.rfc-editor.org/rfc/rfc4847.pdf"],"folder":"IETF/RFC-4847","files":{"txt":{"path":"standards/IETF/RFC-4847/RFC-4847.txt","sha256":"298936cc15495f15ef3e21294f0be7556d60592cd42d26f38e4f2986f1c2f077"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework and service level requirements for\n Layer 1 Virtual Private Networks (L1VPNs). This framework is\n intended to aid in developing and standardizing protocols and\n mechanisms to support interoperable L1VPNs.\n\n The document examines motivations for L1VPNs, high level (service\n level) requirements, and outlines some of the architectural models\n that might be used to build L1VPNs.","scope_keywords":["4847","key","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5195","folder":"IETF/RFC-5195","source":"IETF/RFC-5195/RFC-5195.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 4847 This document provides a framework and service level requirements for\n Layer 1 Virtual Private Networks (L1VPNs). This framework is\n intended to aid in developing and standardizing protocols and\n mechanisms to support interoperable L1VPNs.\n\n The document examines motivations for L1VPNs, high level (service\n level) requirements, and outlines some of the architectural models\n that might be used to build L1VPNs. 4847 key management path trust nested-reference unchanged"},{"id":"IETF RFC 4850","type":"specification","body":"IETF","designation":"RFC 4850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4850.txt","https://www.rfc-editor.org/rfc/rfc4850.pdf"],"folder":"IETF/RFC-4850","files":{"txt":{"path":"standards/IETF/RFC-4850/RFC-4850.txt","sha256":"f7b6696bbbe4c13ae03191b7f015ebb7ae4cf7049ff5847d7fb77a0e587004ad"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Small Computer Systems Interface (iSCSI) protocol,\n described in RFC 3720, allows for extension items to the protocol in\n the form of Private or Public Extension Keys. This document\n describes a Public Extension Key for the purpose of enhancing iSCSI\n supportability. The key accomplishes this objective by allowing\n iSCSI nodes to communicate architecture details during the iSCSI\n login sequence. The receiving node can then use this information for\n enhanced logging and support. This document updates RFC 3720 to\n allow iSCSI extension items to be defined by standards track RFCs and\n experimental RFCs in addition to informational RFCs.\n\nWysochanski Standards Track [Page 1]\n\f\nRFC 4850 iSCSI Node Architecture April 2007\n\n1. Introduction","scope_keywords":["4850","http","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 4850 The Internet Small Computer Systems Interface (iSCSI) protocol,\n described in RFC 3720, allows for extension items to the protocol in\n the form of Private or Public Extension Keys. This document\n describes a Public Extension Key for the purpose of enhancing iSCSI\n supportability. The key accomplishes this objective by allowing\n iSCSI nodes to communicate architecture details during the iSCSI\n login sequence. The receiving node can then use this information for\n enhanced logging and support. This document updates RFC 3720 to\n allow iSCSI extension items to be defined by standards track RFCs and\n experimental RFCs in addition to informational RFCs.\n\nWysochanski Standards Track [Page 1]\n\f\nRFC 4850 iSCSI Node Architecture April 2007\n\n1. Introduction 4850 http key keys trust nested-reference unchanged"},{"id":"IETF RFC 4853","type":"specification","body":"IETF","designation":"RFC 4853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4853.txt","https://www.rfc-editor.org/rfc/rfc4853.pdf"],"folder":"IETF/RFC-4853","files":{"txt":{"path":"standards/IETF/RFC-4853/RFC-4853.txt","sha256":"381598c495c05df74b96ed0e15d2438cd7a53e35af50a440d8524f56d47c935f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Housley\nRequest for Comments: 4853 Vigil Security\nUpdates: 3852 April 2007\nCategory: Standards Track\n\n Cryptographic Message Syntax (CMS)\n Multiple Signer Clarification\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document updates the Cryptographic Message Syntax (CMS), which\n is published in RFC 3852. This document clarifies the proper\n handling of the SignedData protected content type when more than one\n digital signature is present.\n\nHousley Standards Track [Page 1]\n\f\nRFC 485","scope_keywords":["4853","algorithm","algorithms","certificate","certificates","hash","issuer","key","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5652","folder":"IETF/RFC-5652","source":"IETF/RFC-5652/RFC-5652.txt","version":null}],"search_text":"IETF RFC 4853 Network Working Group R. Housley\nRequest for Comments: 4853 Vigil Security\nUpdates: 3852 April 2007\nCategory: Standards Track\n\n Cryptographic Message Syntax (CMS)\n Multiple Signer Clarification\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document updates the Cryptographic Message Syntax (CMS), which\n is published in RFC 3852. This document clarifies the proper\n handling of the SignedData protected content type when more than one\n digital signature is present.\n\nHousley Standards Track [Page 1]\n\f\nRFC 485 4853 algorithm algorithms certificate certificates hash issuer key signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 4856","type":"specification","body":"IETF","designation":"RFC 4856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4856.txt","https://www.rfc-editor.org/rfc/rfc4856.pdf"],"folder":"IETF/RFC-4856","files":{"txt":{"path":"standards/IETF/RFC-4856/RFC-4856.txt","sha256":"4a2e1fea23cdbac2b0838dc5c1dcf9c848b901328fc04caaa3be50891d94a175"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies media type registrations for the RTP payload\n formats defined in the RTP Profile for Audio and Video Conferences.\n Some of these may also be used for transfer modes other than RTP.","scope_keywords":["4856","key","profile","registered","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4855","folder":"IETF/RFC-4855","source":"IETF/RFC-4855/RFC-4855.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null}],"search_text":"IETF RFC 4856 This document specifies media type registrations for the RTP payload\n formats defined in the RTP Profile for Audio and Video Conferences.\n Some of these may also be used for transfer modes other than RTP. 4856 key profile registered timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4858","type":"specification","body":"IETF","designation":"RFC 4858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4858.txt","https://www.rfc-editor.org/rfc/rfc4858.pdf"],"folder":"IETF/RFC-4858","files":{"txt":{"path":"standards/IETF/RFC-4858/RFC-4858.txt","sha256":"202c2570a4b30237fc7b3389a3a581a8fbf158cbb060ea41a0cb1c2c07f47efb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes methodologies that have been designed to\n improve and facilitate IETF document flow processing. It specifies a\n set of procedures under which a working group chair or secretary\n serves as the primary Document Shepherd for a document that has been\n submitted to the IESG for publication. Before this, the Area\n Director responsible for the working group has traditionally filled\n the shepherding role.\n\nLevkowetz, et al. Informational [Page 1]\n\f\nRFC 4858 Document Shepherding to Publication May 2007","scope_keywords":["4858","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null}],"search_text":"IETF RFC 4858 This document describes methodologies that have been designed to\n improve and facilitate IETF document flow processing. It specifies a\n set of procedures under which a working group chair or secretary\n serves as the primary Document Shepherd for a document that has been\n submitted to the IESG for publication. Before this, the Area\n Director responsible for the working group has traditionally filled\n the shepherding role.\n\nLevkowetz, et al. Informational [Page 1]\n\f\nRFC 4858 Document Shepherding to Publication May 2007 4858 key trust nested-reference unchanged"},{"id":"IETF RFC 4863","type":"specification","body":"IETF","designation":"RFC 4863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4863.txt","https://www.rfc-editor.org/rfc/rfc4863.pdf"],"folder":"IETF/RFC-4863","files":{"txt":{"path":"standards/IETF/RFC-4863/RFC-4863.txt","sha256":"ee693b151ed8b0d2372655e39d4fc9c79ed1443eddee2ce9910af5832f62f149"}},"tags":["nested-reference","unchanged"],"summary":"Pseudowire signaling requires that the Pseudowire Type (PW Type) be\n identical in both directions. For certain applications the\n configuration of the PW Type is most easily accomplished by\n configuring this information at just one PW endpoint. In any form of\n LDP-based signaling, each PW endpoint must initiate the creation of a\n unidirectional LSP. In order to allow the initiation of these two\n LSPs to remain independent, a means is needed for allowing the PW\n endpoint (lacking a priori knowledge of the PW Type) to initiate the\n creation of an LSP. This document defines a Wildcard PW Type to\n satisfy this need.","scope_keywords":["4863","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null}],"search_text":"IETF RFC 4863 Pseudowire signaling requires that the Pseudowire Type (PW Type) be\n identical in both directions. For certain applications the\n configuration of the PW Type is most easily accomplished by\n configuring this information at just one PW endpoint. In any form of\n LDP-based signaling, each PW endpoint must initiate the creation of a\n unidirectional LSP. In order to allow the initiation of these two\n LSPs to remain independent, a means is needed for allowing the PW\n endpoint (lacking a priori knowledge of the PW Type) to initiate the\n creation of an LSP. This document defines a Wildcard PW Type to\n satisfy this need. 4863 key management trust nested-reference unchanged"},{"id":"IETF RFC 4866","type":"specification","body":"IETF","designation":"RFC 4866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4866.txt","https://www.rfc-editor.org/rfc/rfc4866.pdf"],"folder":"IETF/RFC-4866","files":{"txt":{"path":"standards/IETF/RFC-4866/RFC-4866.txt","sha256":"0b948ac4be617867ba78eab5bb2e87b4b5407b3137a0984811d0cd8e2ade47e4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an enhanced version of Mobile IPv6 route\n optimization, providing lower handoff delays, increased security, and\n reduced signaling overhead.","scope_keywords":["4866","authorization","key","path","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null}],"search_text":"IETF RFC 4866 This document specifies an enhanced version of Mobile IPv6 route\n optimization, providing lower handoff delays, increased security, and\n reduced signaling overhead. 4866 authorization key path signature trust nested-reference unchanged"},{"id":"IETF RFC 4867","type":"specification","body":"IETF","designation":"RFC 4867","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4867.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4867.txt","https://www.rfc-editor.org/rfc/rfc4867.pdf"],"folder":"IETF/RFC-4867","files":{"txt":{"path":"standards/IETF/RFC-4867/RFC-4867.txt","sha256":"21e418ca0a562f79be05ecf89af0265c94a6d2aead3950908a91ee1ec10074e1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Real-time Transport Protocol (RTP) payload\n format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-\n Rate Wideband (AMR-WB) encoded speech signals. The payload format is\n designed to be able to interoperate with existing AMR and AMR-WB\n transport formats on non-IP networks. In addition, a file format is\n specified for transport of AMR and AMR-WB speech data in storage mode\n applications such as email. Two separate media type registrations\n are included, one for AMR and one for AMR-WB, specifying use of both\n the RTP payload format and the storage format. This document\n obsoletes RFC 3267.\n\nSjoberg, et al. Standards Track [Page 1]\n\f\nRFC 4867 RTP Payload Format for AMR and AMR-WB April 2007","scope_keywords":["4867","algorithm","authentication","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 4867 This document specifies a Real-time Transport Protocol (RTP) payload\n format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-\n Rate Wideband (AMR-WB) encoded speech signals. The payload format is\n designed to be able to interoperate with existing AMR and AMR-WB\n transport formats on non-IP networks. In addition, a file format is\n specified for transport of AMR and AMR-WB speech data in storage mode\n applications such as email. Two separate media type registrations\n are included, one for AMR and one for AMR-WB, specifying use of both\n the RTP payload format and the storage format. This document\n obsoletes RFC 3267.\n\nSjoberg, et al. Standards Track [Page 1]\n\f\nRFC 4867 RTP Payload Format for AMR and AMR-WB April 2007 4867 algorithm authentication trust validation nested-reference unchanged"},{"id":"IETF RFC 4869","type":"specification","body":"IETF","designation":"RFC 4869","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4869.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4869.txt","https://www.rfc-editor.org/rfc/rfc4869.pdf"],"folder":"IETF/RFC-4869","files":{"txt":{"path":"standards/IETF/RFC-4869/RFC-4869.txt","sha256":"6d6ce50eb488f2475cb725e463acd659701806169b1a3df4e2ff057d533673b1"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes four optional cryptographic user interface\n suites (\"UI suites\") for IPsec, similar to the two suites specified\n in RFC 4308. The four new suites provide compatibility with the\n United States National Security Agency's Suite B specifications.","scope_keywords":["4869","algorithm","algorithms","authentication","encryption","hash","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null}],"search_text":"IETF RFC 4869 This document proposes four optional cryptographic user interface\n suites (\"UI suites\") for IPsec, similar to the two suites specified\n in RFC 4308. The four new suites provide compatibility with the\n United States National Security Agency's Suite B specifications. 4869 algorithm algorithms authentication encryption hash key keys trust nested-reference unchanged"},{"id":"IETF RFC 4872","type":"specification","body":"IETF","designation":"RFC 4872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4872.txt","https://www.rfc-editor.org/rfc/rfc4872.pdf"],"folder":"IETF/RFC-4872","files":{"txt":{"path":"standards/IETF/RFC-4872/RFC-4872.txt","sha256":"f8373d4afd536fe6c334eb640938244e181994dd3968db24750434b7611eaaac"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol-specific procedures and extensions\n for Generalized Multi-Protocol Label Switching (GMPLS) Resource\n ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to\n support end-to-end Label Switched Path (LSP) recovery that denotes\n protection and restoration. A generic functional description of\n GMPLS recovery can be found in a companion document, RFC 4426.","scope_keywords":["4872","attribute","attributes","identification","management","path","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4873","folder":"IETF/RFC-4873","source":"IETF/RFC-4873/RFC-4873.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4872 This document describes protocol-specific procedures and extensions\n for Generalized Multi-Protocol Label Switching (GMPLS) Resource\n ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to\n support end-to-end Label Switched Path (LSP) recovery that denotes\n protection and restoration. A generic functional description of\n GMPLS recovery can be found in a companion document, RFC 4426. 4872 attribute attributes identification management path risk trust nested-reference unchanged"},{"id":"IETF RFC 4873","type":"specification","body":"IETF","designation":"RFC 4873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4873.txt","https://www.rfc-editor.org/rfc/rfc4873.pdf"],"folder":"IETF/RFC-4873","files":{"txt":{"path":"standards/IETF/RFC-4873/RFC-4873.txt","sha256":"72608ce3d4f84840368326e12bbd86981dc87234e0dd32a4e39fcc66305287a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes protocol specific procedures for GMPLS\n (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource\n ReserVation Protocol - Traffic Engineering) signaling extensions to\n support label switched path (LSP) segment protection and restoration.\n These extensions are intended to complement and be consistent with\n the RSVP-TE Extensions for End-to-End GMPLS Recovery (RFC 4872).\n Implications and interactions with fast reroute are also addressed.\n This document also updates the handling of NOTIFY_REQUEST objects.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 4873 GMPLS Segment Recovery May 2007","scope_keywords":["4873","identification","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4875","folder":"IETF/RFC-4875","source":"IETF/RFC-4875/RFC-4875.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4873 This document describes protocol specific procedures for GMPLS\n (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource\n ReserVation Protocol - Traffic Engineering) signaling extensions to\n support label switched path (LSP) segment protection and restoration.\n These extensions are intended to complement and be consistent with\n the RSVP-TE Extensions for End-to-End GMPLS Recovery (RFC 4872).\n Implications and interactions with fast reroute are also addressed.\n This document also updates the handling of NOTIFY_REQUEST objects.\n\nBerger, et al. Standards Track [Page 1]\n\f\nRFC 4873 GMPLS Segment Recovery May 2007 4873 identification key path trust nested-reference unchanged"},{"id":"IETF RFC 4874","type":"specification","body":"IETF","designation":"RFC 4874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4874.txt","https://www.rfc-editor.org/rfc/rfc4874.pdf"],"folder":"IETF/RFC-4874","files":{"txt":{"path":"standards/IETF/RFC-4874/RFC-4874.txt","sha256":"a45b44fd1a35a7e54449eafd9c2b2ea34dd12972a9dc1e896a54d285518fa8cd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies ways to communicate route exclusions during\n path setup using Resource ReserVation Protocol-Traffic Engineering\n (RSVP-TE).\n\n The RSVP-TE specification, \"RSVP-TE: Extensions to RSVP for LSP\n Tunnels\" (RFC 3209) and GMPLS extensions to RSVP-TE, \"Generalized\n Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation\n Protocol-Traffic Engineering (RSVP-TE) Extensions\" (RFC 3473) allow\n abstract nodes and resources to be explicitly included in a path\n setup, but not to be explicitly excluded.\n\n In some networks where precise explicit paths are not computed at the\n head end, it may be useful to specify and signal abstract nodes and\n resources that are to be explicitly excluded from routes. These\n exclusions may apply to the whole path, or to parts of a path between\n two abstract nodes specified in an explicit path. How Shared Risk\n Link Groups (SRLGs) can b","scope_keywords":["4874","key","path","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4872","folder":"IETF/RFC-4872","source":"IETF/RFC-4872/RFC-4872.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 4874 This document specifies ways to communicate route exclusions during\n path setup using Resource ReserVation Protocol-Traffic Engineering\n (RSVP-TE).\n\n The RSVP-TE specification, \"RSVP-TE: Extensions to RSVP for LSP\n Tunnels\" (RFC 3209) and GMPLS extensions to RSVP-TE, \"Generalized\n Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation\n Protocol-Traffic Engineering (RSVP-TE) Extensions\" (RFC 3473) allow\n abstract nodes and resources to be explicitly included in a path\n setup, but not to be explicitly excluded.\n\n In some networks where precise explicit paths are not computed at the\n head end, it may be useful to specify and signal abstract nodes and\n resources that are to be explicitly excluded from routes. These\n exclusions may apply to the whole path, or to parts of a path between\n two abstract nodes specified in an explicit path. How Shared Risk\n Link Groups (SRLGs) can b 4874 key path risk trust nested-reference unchanged"},{"id":"IETF RFC 4875","type":"specification","body":"IETF","designation":"RFC 4875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4875.txt","https://www.rfc-editor.org/rfc/rfc4875.pdf"],"folder":"IETF/RFC-4875","files":{"txt":{"path":"standards/IETF/RFC-4875/RFC-4875.txt","sha256":"dbb2889368e90b6b8376cb7f6892bd6dd00f0164fc7f196e7d298f5bbcddda87"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to Resource Reservation Protocol -\n Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered\n (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi-\n Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n networks. The solution relies on RSVP-TE without requiring a\n multicast routing protocol in the Service Provider core. Protocol\n elements and procedures for this solution are described.\n\n There can be various applications for P2MP TE LSPs such as IP\n multicast. Specification of how such applications will use a P2MP TE\n LSP is outside the scope of this document.\n\nAggarwal, et al. Standards Track [Page 1]\n\f\nRFC 4875 Extensions to RSVP-TE for P2MP TE LSPs May 2007","scope_keywords":["4875","attribute","attributes","management","path","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6348","folder":"IETF/RFC-6348","source":"IETF/RFC-6348/RFC-6348.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4875 This document describes extensions to Resource Reservation Protocol -\n Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered\n (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi-\n Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n networks. The solution relies on RSVP-TE without requiring a\n multicast routing protocol in the Service Provider core. Protocol\n elements and procedures for this solution are described.\n\n There can be various applications for P2MP TE LSPs such as IP\n multicast. Specification of how such applications will use a P2MP TE\n LSP is outside the scope of this document.\n\nAggarwal, et al. Standards Track [Page 1]\n\f\nRFC 4875 Extensions to RSVP-TE for P2MP TE LSPs May 2007 4875 attribute attributes management path presentation trust nested-reference unchanged"},{"id":"IETF RFC 4877","type":"specification","body":"IETF","designation":"RFC 4877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4877.txt","https://www.rfc-editor.org/rfc/rfc4877.pdf"],"folder":"IETF/RFC-4877","files":{"txt":{"path":"standards/IETF/RFC-4877/RFC-4877.txt","sha256":"2e93e0997761359e39bf20e269f8a7642cd8877cf38dbae6804bce0c13adc1b4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Mobile IPv6 operation with the revised IPsec\n architecture and IKEv2.\n\nDevarapalli & Dupont Standards Track [Page 1]\n\f\nRFC 4877 Mobile IPv6 with IKEv2 and IPsec April 2007","scope_keywords":["4877","authentication","authorization","key","management","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5380","folder":"IETF/RFC-5380","source":"IETF/RFC-5380/RFC-5380.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 4877 This document describes Mobile IPv6 operation with the revised IPsec\n architecture and IKEv2.\n\nDevarapalli & Dupont Standards Track [Page 1]\n\f\nRFC 4877 Mobile IPv6 with IKEv2 and IPsec April 2007 4877 authentication authorization key management policies policy trust nested-reference unchanged"},{"id":"IETF RFC 4896","type":"specification","body":"IETF","designation":"RFC 4896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4896.txt","https://www.rfc-editor.org/rfc/rfc4896.pdf"],"folder":"IETF/RFC-4896","files":{"txt":{"path":"standards/IETF/RFC-4896/RFC-4896.txt","sha256":"fddf3f0ec88528ae174f37f1d04517658b162a078b5997aeb4c804d6bbaf1c49"}},"tags":["nested-reference","unchanged"],"summary":"This document describes common misinterpretations and some\n ambiguities in the Signaling Compression Protocol (SigComp), and\n offers guidance to developers to resolve any resultant problems.\n SigComp defines a scheme for compressing messages generated by\n application protocols such as the Session Initiation Protocol (SIP).\n This document updates the following RFCs: RFC 3320, RFC 3321, and RFC\n 3485.\n\nSurtees, et al. Standards Track [Page 1]\n\f\nRFC 4896 SigComp Corrections and Clarifications June 2007","scope_keywords":["4896","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null}],"search_text":"IETF RFC 4896 This document describes common misinterpretations and some\n ambiguities in the Signaling Compression Protocol (SigComp), and\n offers guidance to developers to resolve any resultant problems.\n SigComp defines a scheme for compressing messages generated by\n application protocols such as the Session Initiation Protocol (SIP).\n This document updates the following RFCs: RFC 3320, RFC 3321, and RFC\n 3485.\n\nSurtees, et al. Standards Track [Page 1]\n\f\nRFC 4896 SigComp Corrections and Clarifications June 2007 4896 key trust nested-reference unchanged"},{"id":"IETF RFC 4904","type":"specification","body":"IETF","designation":"RFC 4904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4904.txt","https://www.rfc-editor.org/rfc/rfc4904.pdf"],"folder":"IETF/RFC-4904","files":{"txt":{"path":"standards/IETF/RFC-4904/RFC-4904.txt","sha256":"a251db3b21499184a02f488538695d6d8a8da734f3b545ad134b6605f66be5d1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a standardized mechanism to convey trunk\n group parameters in sip and tel Uniform Resource Identifiers (URIs).\n An extension to the tel URI is defined for this purpose.\n\nGurbani & Jennings Standards Track [Page 1]\n\f\nRFC 4904 Trunk Groups in tel/sip URIs June 2007","scope_keywords":["4904","identification","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null}],"search_text":"IETF RFC 4904 This document describes a standardized mechanism to convey trunk\n group parameters in sip and tel Uniform Resource Identifiers (URIs).\n An extension to the tel URI is defined for this purpose.\n\nGurbani & Jennings Standards Track [Page 1]\n\f\nRFC 4904 Trunk Groups in tel/sip URIs June 2007 4904 identification path policy trust nested-reference unchanged"},{"id":"IETF RFC 4909","type":"specification","body":"IETF","designation":"RFC 4909","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4909.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4909.txt","https://www.rfc-editor.org/rfc/rfc4909.pdf"],"folder":"IETF/RFC-4909","files":{"txt":{"path":"standards/IETF/RFC-4909/RFC-4909.txt","sha256":"78b1425eca070f2b35c32a77a26b48f1ef070c30120f4127205954fb42898396"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new Multimedia Internet KEYing (MIKEY)\n General Extension payload (RFC 3830) to transport the short-term key\n message (STKM) and long-term key message (LTKM) payloads defined in\n the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast\n (BCAST) group's Service and Content protection specification.","scope_keywords":["4909","attribute","attributes","http","key","keys","profile","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null}],"search_text":"IETF RFC 4909 This document specifies a new Multimedia Internet KEYing (MIKEY)\n General Extension payload (RFC 3830) to transport the short-term key\n message (STKM) and long-term key message (LTKM) payloads defined in\n the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast\n (BCAST) group's Service and Content protection specification. 4909 attribute attributes http key keys profile trust nested-reference unchanged"},{"id":"IETF RFC 4916","type":"specification","body":"IETF","designation":"RFC 4916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4916.txt","https://www.rfc-editor.org/rfc/rfc4916.pdf"],"folder":"IETF/RFC-4916","files":{"txt":{"path":"standards/IETF/RFC-4916/RFC-4916.txt","sha256":"dbd3037e9cb7608776fb993a9617d6892a6c60681ed27966ece018fde812d881"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a means for a Session Initiation Protocol\n (SIP) User Agent (UA) that receives a dialog-forming request to\n supply its identity to the peer UA by means of a request in the\n reverse direction, and for that identity to be signed by an\n Authentication Service. Because of retargeting of a dialog-forming\n request (changing the value of the Request-URI), the UA that receives\n it (the User Agent Server, UAS) can have a different identity from\n that in the To header field. The same mechanism can be used to\n indicate a change of identity during a dialog, e.g., because of some\n action in the Public Switched Telephone Network (PSTN) behind a\n gateway. This document normatively updates RFC 3261 (SIP).\n\nElwell Standards Track [Page 1]\n\f\nRFC 4916 SIP Connected ID June 2007","scope_keywords":["4916","authentication","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null}],"search_text":"IETF RFC 4916 This document provides a means for a Session Initiation Protocol\n (SIP) User Agent (UA) that receives a dialog-forming request to\n supply its identity to the peer UA by means of a request in the\n reverse direction, and for that identity to be signed by an\n Authentication Service. Because of retargeting of a dialog-forming\n request (changing the value of the Request-URI), the UA that receives\n it (the User Agent Server, UAS) can have a different identity from\n that in the To header field. The same mechanism can be used to\n indicate a change of identity during a dialog, e.g., because of some\n action in the Public Switched Telephone Network (PSTN) behind a\n gateway. This document normatively updates RFC 3261 (SIP).\n\nElwell Standards Track [Page 1]\n\f\nRFC 4916 SIP Connected ID June 2007 4916 authentication key path trust nested-reference unchanged"},{"id":"IETF RFC 4920","type":"specification","body":"IETF","designation":"RFC 4920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4920.txt","https://www.rfc-editor.org/rfc/rfc4920.pdf"],"folder":"IETF/RFC-4920","files":{"txt":{"path":"standards/IETF/RFC-4920/RFC-4920.txt","sha256":"6e6ad173a681a85e5b0ba22a72650c7d6e6e476861fdb24ca0dbe836cd6acc3d"}},"tags":["nested-reference","unchanged"],"summary":"In a distributed, constraint-based routing environment, the\n information used to compute a path may be out of date. This means\n that Multiprotocol Label Switching (MPLS) and Generalized MPLS\n (GMPLS) Traffic Engineered (TE) Label Switched Path (LSP) setup\n requests may be blocked by links or nodes without sufficient\n resources. Crankback is a scheme whereby setup failure information\n is returned from the point of failure to allow new setup attempts to\n be made avoiding the blocked resources. Crankback can also be\n applied to LSP recovery to indicate the location of the failed link\n or node.\n\n This document specifies crankback signaling extensions for use in\n MPLS signaling using RSVP-TE as defined in \"RSVP-TE: Extensions to\n RSVP for LSP Tunnels\", RFC 3209, and GMPLS signaling as defined in\n \"Generalized Multi-Protocol Label Switching (GMPLS) Signaling\n Functional Description\", RFC 3473.","scope_keywords":["4920","attribute","attributes","identification","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null}],"search_text":"IETF RFC 4920 In a distributed, constraint-based routing environment, the\n information used to compute a path may be out of date. This means\n that Multiprotocol Label Switching (MPLS) and Generalized MPLS\n (GMPLS) Traffic Engineered (TE) Label Switched Path (LSP) setup\n requests may be blocked by links or nodes without sufficient\n resources. Crankback is a scheme whereby setup failure information\n is returned from the point of failure to allow new setup attempts to\n be made avoiding the blocked resources. Crankback can also be\n applied to LSP recovery to indicate the location of the failed link\n or node.\n\n This document specifies crankback signaling extensions for use in\n MPLS signaling using RSVP-TE as defined in \"RSVP-TE: Extensions to\n RSVP for LSP Tunnels\", RFC 3209, and GMPLS signaling as defined in\n \"Generalized Multi-Protocol Label Switching (GMPLS) Signaling\n Functional Description\", RFC 3473. 4920 attribute attributes identification path trust nested-reference unchanged"},{"id":"IETF RFC 4927","type":"specification","body":"IETF","designation":"RFC 4927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4927.txt","https://www.rfc-editor.org/rfc/rfc4927.pdf"],"folder":"IETF/RFC-4927","files":{"txt":{"path":"standards/IETF/RFC-4927/RFC-4927.txt","sha256":"a27a0a6144da274c7de5e93acd0ab420e8d45c2d0b2129d35e1437a317b53b26"}},"tags":["nested-reference","unchanged"],"summary":"For scalability purposes, a network may comprise multiple Interior\n Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label\n Switched Path (TE-LSP) is an LSP that transits through at least two\n IGP areas. In a multi-area network, topology visibility remains\n local to a given area, and a head-end Label Switching Router (LSR)\n cannot compute an inter-area shortest constrained path. One key\n application of the Path Computation Element (PCE)-based architecture\n is the computation of inter-area TE-LSP paths. The PCE Communication\n Protocol (PCECP) is used to communicate computation requests from\n Path Computation Clients (PCCs) to PCEs, and to return computed paths\n in responses. This document lists a detailed set of PCECP-specific\n requirements for support of inter-area TE-LSP path computation. It\n complements the generic requirements for a PCE Communication\n Protocol.\n\nLe Roux ","scope_keywords":["4927","key","path","policies","risk","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 4927 For scalability purposes, a network may comprise multiple Interior\n Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label\n Switched Path (TE-LSP) is an LSP that transits through at least two\n IGP areas. In a multi-area network, topology visibility remains\n local to a given area, and a head-end Label Switching Router (LSR)\n cannot compute an inter-area shortest constrained path. One key\n application of the Path Computation Element (PCE)-based architecture\n is the computation of inter-area TE-LSP paths. The PCE Communication\n Protocol (PCECP) is used to communicate computation requests from\n Path Computation Clients (PCCs) to PCEs, and to return computed paths\n in responses. This document lists a detailed set of PCECP-specific\n requirements for support of inter-area TE-LSP path computation. It\n complements the generic requirements for a PCE Communication\n Protocol.\n\nLe Roux  4927 key path policies risk trust nested-reference unchanged"},{"id":"IETF RFC 4945","type":"specification","body":"IETF","designation":"RFC 4945","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4945.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4945.txt","https://www.rfc-editor.org/rfc/rfc4945.pdf"],"folder":"IETF/RFC-4945","files":{"txt":{"path":"standards/IETF/RFC-4945/RFC-4945.txt","sha256":"dd8221c3ca632da5bdf85f7ce5ddb8222fddfcf1dae3d5ca03a01af9fe1d5ecd"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Key Exchange (IKE) and Public Key Infrastructure for\n X.509 (PKIX) certificate profile both provide frameworks that must be\n profiled for use in a given application. This document provides a\n profile of IKE and PKIX that defines the requirements for using PKI\n technology in the context of IKE/IPsec. The document complements\n protocol specifications such as IKEv1 and IKEv2, which assume the\n existence of public key certificates and related keying materials,\n but which do not address PKI issues explicitly. This document\n addresses those issues. The intended audience is implementers of PKI\n for IPsec.\n\nKorver Standards Track [Page 1]\n\f\nRFC 4945 PKI Profile for IKE/ISAKMP/PKIX August 2007","scope_keywords":["4945","algorithm","algorithms","certificate","certificates","crl","hash","hashing","identification","key","keys","pki","policy","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null}],"search_text":"IETF RFC 4945 The Internet Key Exchange (IKE) and Public Key Infrastructure for\n X.509 (PKIX) certificate profile both provide frameworks that must be\n profiled for use in a given application. This document provides a\n profile of IKE and PKIX that defines the requirements for using PKI\n technology in the context of IKE/IPsec. The document complements\n protocol specifications such as IKEv1 and IKEv2, which assume the\n existence of public key certificates and related keying materials,\n but which do not address PKI issues explicitly. This document\n addresses those issues. The intended audience is implementers of PKI\n for IPsec.\n\nKorver Standards Track [Page 1]\n\f\nRFC 4945 PKI Profile for IKE/ISAKMP/PKIX August 2007 4945 algorithm algorithms certificate certificates crl hash hashing identification key keys pki policy profile revocation signature nested-reference unchanged"},{"id":"IETF RFC 4946","type":"specification","body":"IETF","designation":"RFC 4946","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4946.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4946.txt","https://www.rfc-editor.org/rfc/rfc4946.pdf"],"folder":"IETF/RFC-4946","files":{"txt":{"path":"standards/IETF/RFC-4946/RFC-4946.txt","sha256":"03cc9284386633d74cea36c724b0e4ecc8a64ba1fde314c76f28455769aea039"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension to the Atom Syndication Format for\n describing licenses associated with Atom feeds and entries.","scope_keywords":["4946","attribute","attributes","http","key","license","presentation","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null}],"search_text":"IETF RFC 4946 This memo defines an extension to the Atom Syndication Format for\n describing licenses associated with Atom feeds and entries. 4946 attribute attributes http key license presentation qualified trust nested-reference unchanged"},{"id":"IETF RFC 4959","type":"specification","body":"IETF","designation":"RFC 4959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4959.txt","https://www.rfc-editor.org/rfc/rfc4959.pdf"],"folder":"IETF/RFC-4959","files":{"txt":{"path":"standards/IETF/RFC-4959/RFC-4959.txt","sha256":"22a39f041118aec0cb7b5f879ccba9cc146081c5c138768b79bbd4e798ac44b8"}},"tags":["nested-reference","unchanged"],"summary":"To date, the Internet Message Access Protocol (IMAP) has used a\n Simple Authentication and Security Layer (SASL) profile which always\n required at least one complete round trip for an authentication, as\n it did not support an initial client response argument. This\n additional round trip at the beginning of the session is undesirable,\n especially when round-trip costs are high.\n\n This document defines an extension to IMAP which allows clients and\n servers to avoid this round trip by allowing an initial client\n response argument to the IMAP AUTHENTICATE command.\n\nSiemborski & Gulbrandsen Standards Track [Page 1]\n\f\nRFC 4959 IMAP Ext for SASL Initial Client Response September 2007\n\n1. Introduction\n\n The SASL initial client response extension is present in any IMAP\n [RFC3501] server implementation which returns \"SASL-IR\" as one of the\n supported capabilities in its CAPABILITY response.\n\n Serv","scope_keywords":["4959","authentication","key","profile","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4959 To date, the Internet Message Access Protocol (IMAP) has used a\n Simple Authentication and Security Layer (SASL) profile which always\n required at least one complete round trip for an authentication, as\n it did not support an initial client response argument. This\n additional round trip at the beginning of the session is undesirable,\n especially when round-trip costs are high.\n\n This document defines an extension to IMAP which allows clients and\n servers to avoid this round trip by allowing an initial client\n response argument to the IMAP AUTHENTICATE command.\n\nSiemborski & Gulbrandsen Standards Track [Page 1]\n\f\nRFC 4959 IMAP Ext for SASL Initial Client Response September 2007\n\n1. Introduction\n\n The SASL initial client response extension is present in any IMAP\n [RFC3501] server implementation which returns \"SASL-IR\" as one of the\n supported capabilities in its CAPABILITY response.\n\n Serv 4959 authentication key profile subject tls nested-reference unchanged"},{"id":"IETF RFC 4964","type":"specification","body":"IETF","designation":"RFC 4964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4964.txt","https://www.rfc-editor.org/rfc/rfc4964.pdf"],"folder":"IETF/RFC-4964","files":{"txt":{"path":"standards/IETF/RFC-4964/RFC-4964.txt","sha256":"8ed9ad16a369ce0c92dfa2ded667fa1cd3e4d6c325c5c498f38a5caad5c9c4a1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a private Session Initiation Protocol (SIP)\n header (P-header) used by the Open Mobile Alliance (OMA) for Push to\n talk over Cellular (PoC) along with its applicability, which is\n limited to the OMA PoC application. The P-Answer-State header is\n used for indicating the answering mode of the handset, which is\n particular to the PoC application.\n\nAllen, et al. Informational [Page 1]\n\f\nRFC 4964 The P-Answer-State Header September 2007","scope_keywords":["4964","http","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4964 This document describes a private Session Initiation Protocol (SIP)\n header (P-header) used by the Open Mobile Alliance (OMA) for Push to\n talk over Cellular (PoC) along with its applicability, which is\n limited to the OMA PoC application. The P-Answer-State header is\n used for indicating the answering mode of the handset, which is\n particular to the PoC application.\n\nAllen, et al. Informational [Page 1]\n\f\nRFC 4964 The P-Answer-State Header September 2007 4964 http key trust nested-reference unchanged"},{"id":"IETF RFC 4967","type":"specification","body":"IETF","designation":"RFC 4967","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4967.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4967.txt","https://www.rfc-editor.org/rfc/rfc4967.pdf"],"folder":"IETF/RFC-4967","files":{"txt":{"path":"standards/IETF/RFC-4967/RFC-4967.txt","sha256":"f0c2b54ce871382fa4566bec1d4314f7153fe45b43ea223350a645357bb83099"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3966 explicitly states that 'tel' URIs may not represent a dial\n string. That leaves no way specify a dial string in a standardized\n way. Great confusion exists with the SIP URI parameter \"user=phone\",\n and specifically, if it can represent a dial string. This memo\n creates a new value for the user parameter \"dialstring\", so that one\n may specify \"user=dialstring\" to encode a dial string as a 'sip:' or\n 'sips:' URI.","scope_keywords":["4967","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null}],"search_text":"IETF RFC 4967 RFC 3966 explicitly states that 'tel' URIs may not represent a dial\n string. That leaves no way specify a dial string in a standardized\n way. Great confusion exists with the SIP URI parameter \"user=phone\",\n and specifically, if it can represent a dial string. This memo\n creates a new value for the user parameter \"dialstring\", so that one\n may specify \"user=dialstring\" to encode a dial string as a 'sip:' or\n 'sips:' URI. 4967 key trust nested-reference unchanged"},{"id":"IETF RFC 4970","type":"specification","body":"IETF","designation":"RFC 4970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4970.txt","https://www.rfc-editor.org/rfc/rfc4970.pdf"],"folder":"IETF/RFC-4970","files":{"txt":{"path":"standards/IETF/RFC-4970/RFC-4970.txt","sha256":"842f4cbae73d36c469afe4d2470352a29a94de6968d452fa1fd94224ff7b7dfe"}},"tags":["nested-reference","unchanged"],"summary":"It is useful for routers in an OSPFv2 or OSPFv3 routing domain to\n know the capabilities of their neighbors and other routers in the\n routing domain. This document proposes extensions to OSPFv2 and\n OSPFv3 for advertising optional router capabilities. A new Router\n Information (RI) Link State Advertisement (LSA) is proposed for this\n purpose. In OSPFv2, the RI LSA will be implemented with a new opaque\n LSA type ID. In OSPFv3, the RI LSA will be implemented with a new\n LSA type function code. In both protocols, the RI LSA can be\n advertised at any of the defined flooding scopes (link, area, or\n autonomous system (AS)).\n\nLindem, et al. Standards Track [Page 1]\n\f\nRFC 4970 OSPF Capability Extensions July 2007","scope_keywords":["4970","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4972","folder":"IETF/RFC-4972","source":"IETF/RFC-4972/RFC-4972.txt","version":null},{"body":"IETF","designation":"RFC 4973","folder":"IETF/RFC-4973","source":"IETF/RFC-4973/RFC-4973.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5250","folder":"IETF/RFC-5250","source":"IETF/RFC-5250/RFC-5250.txt","version":null},{"body":"IETF","designation":"RFC 7770","folder":"IETF/RFC-7770","source":"IETF/RFC-7770/RFC-7770.txt","version":null}],"search_text":"IETF RFC 4970 It is useful for routers in an OSPFv2 or OSPFv3 routing domain to\n know the capabilities of their neighbors and other routers in the\n routing domain. This document proposes extensions to OSPFv2 and\n OSPFv3 for advertising optional router capabilities. A new Router\n Information (RI) Link State Advertisement (LSA) is proposed for this\n purpose. In OSPFv2, the RI LSA will be implemented with a new opaque\n LSA type ID. In OSPFv3, the RI LSA will be implemented with a new\n LSA type function code. In both protocols, the RI LSA can be\n advertised at any of the defined flooding scopes (link, area, or\n autonomous system (AS)).\n\nLindem, et al. Standards Track [Page 1]\n\f\nRFC 4970 OSPF Capability Extensions July 2007 4970 key trust nested-reference unchanged"},{"id":"IETF RFC 4982","type":"specification","body":"IETF","designation":"RFC 4982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4982.txt","https://www.rfc-editor.org/rfc/rfc4982.pdf"],"folder":"IETF/RFC-4982","files":{"txt":{"path":"standards/IETF/RFC-4982/RFC-4982.txt","sha256":"1f07a91f7da41dcff30be36a356c05ce3b0478712fd5660403d96b2f761a303b"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes the implications of recent attacks on commonly\n used hash functions on Cryptographically Generated Addresses (CGAs)\n and updates the CGA specification to support multiple hash\n algorithms.","scope_keywords":["4982","algorithm","algorithms","hash","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5453","folder":"IETF/RFC-5453","source":"IETF/RFC-5453/RFC-5453.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null}],"search_text":"IETF RFC 4982 This document analyzes the implications of recent attacks on commonly\n used hash functions on Cryptographically Generated Addresses (CGAs)\n and updates the CGA specification to support multiple hash\n algorithms. 4982 algorithm algorithms hash key trust nested-reference unchanged"},{"id":"IETF RFC 4986","type":"specification","body":"IETF","designation":"RFC 4986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4986.txt","https://www.rfc-editor.org/rfc/rfc4986.pdf"],"folder":"IETF/RFC-4986","files":{"txt":{"path":"standards/IETF/RFC-4986/RFC-4986.txt","sha256":"04bf7c090695e0677284faca272e758e87e503a02aa62affcde205502580c777"}},"tags":["nested-reference","unchanged"],"summary":"Every DNS security-aware resolver must have at least one Trust Anchor\n to use as the basis for validating responses from DNS signed zones.\n For various reasons, most DNS security-aware resolvers are expected\n to have several Trust Anchors. For some operations, manual\n monitoring and updating of Trust Anchors may be feasible, but many\n operations will require automated methods for updating Trust Anchors\n in their security-aware resolvers. This document identifies the\n requirements that must be met by an automated DNS Trust Anchor\n rollover solution for security-aware DNS resolvers.\n\nEland, et al. Informational [Page 1]\n\f\nRFC 4986 DNSSEC Trust Anchor Rollover Requirements August 2007","scope_keywords":["4986","authentication","hash","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5011","folder":"IETF/RFC-5011","source":"IETF/RFC-5011/RFC-5011.txt","version":null}],"search_text":"IETF RFC 4986 Every DNS security-aware resolver must have at least one Trust Anchor\n to use as the basis for validating responses from DNS signed zones.\n For various reasons, most DNS security-aware resolvers are expected\n to have several Trust Anchors. For some operations, manual\n monitoring and updating of Trust Anchors may be feasible, but many\n operations will require automated methods for updating Trust Anchors\n in their security-aware resolvers. This document identifies the\n requirements that must be met by an automated DNS Trust Anchor\n rollover solution for security-aware DNS resolvers.\n\nEland, et al. Informational [Page 1]\n\f\nRFC 4986 DNSSEC Trust Anchor Rollover Requirements August 2007 4986 authentication hash key management trust nested-reference unchanged"},{"id":"IETF RFC 4991","type":"specification","body":"IETF","designation":"RFC 4991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4991.txt","https://www.rfc-editor.org/rfc/rfc4991.pdf"],"folder":"IETF/RFC-4991","files":{"txt":{"path":"standards/IETF/RFC-4991/RFC-4991.txt","sha256":"86b8553b9654ad5ba8208245d5030b1c79c32553912b150489237f9a9259a2e2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an XML Schema for use by Internet Registry\n Information Service (IRIS) application transfer protocols that share\n common characteristics. It describes common information about the\n transfer protocol, such as version, supported extensions, and\n supported security mechanisms.","scope_keywords":["4991","attribute","authentication","http","key","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 4993","folder":"IETF/RFC-4993","source":"IETF/RFC-4993/RFC-4993.txt","version":null}],"search_text":"IETF RFC 4991 This document describes an XML Schema for use by Internet Registry\n Information Service (IRIS) application transfer protocols that share\n common characteristics. It describes common information about the\n transfer protocol, such as version, supported extensions, and\n supported security mechanisms. 4991 attribute authentication http key qualified trust nested-reference unchanged"},{"id":"IETF RFC 4994","type":"specification","body":"IETF","designation":"RFC 4994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4994.txt","https://www.rfc-editor.org/rfc/rfc4994.pdf"],"folder":"IETF/RFC-4994","files":{"txt":{"path":"standards/IETF/RFC-4994/RFC-4994.txt","sha256":"ff23d55acb6a6f1dd0db0ccb4fbc3eece5b8c38ab4608732e74cfa05e4dc25c9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Relay Agent Echo Request option for the Dynamic\n Host Configuration Protocol for IPv6 (DHCPv6). The option allows a\n DHCPv6 relay agent to request a list of relay agent options that the\n server echoes back to the relay agent.","scope_keywords":["4994","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 4994 This memo defines a Relay Agent Echo Request option for the Dynamic\n Host Configuration Protocol for IPv6 (DHCPv6). The option allows a\n DHCPv6 relay agent to request a list of relay agent options that the\n server echoes back to the relay agent. 4994 key nested-reference unchanged"},{"id":"IETF RFC 5001","type":"specification","body":"IETF","designation":"RFC 5001","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5001.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5001.txt","https://www.rfc-editor.org/rfc/rfc5001.pdf"],"folder":"IETF/RFC-5001","files":{"txt":{"path":"standards/IETF/RFC-5001/RFC-5001.txt","sha256":"9d721680277cd814c50e4db3b15dc016a85a094a448a7e2f5f41367f082d60d0"}},"tags":["nested-reference","unchanged"],"summary":"With the increased use of DNS anycast, load balancing, and other\n mechanisms allowing more than one DNS name server to share a single\n IP address, it is sometimes difficult to tell which of a pool of name\n servers has answered a particular query. While existing ad-hoc\n mechanisms allow an operator to send follow-up queries when it is\n necessary to debug such a configuration, the only completely reliable\n way to obtain the identity of the name server that responded is to\n have the name server include this information in the response itself.\n This note defines a protocol extension to support this functionality.\n\nAustein Standards Track [Page 1]\n\f\nRFC 5001 DNS NSID August 2007","scope_keywords":["5001","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 5001 With the increased use of DNS anycast, load balancing, and other\n mechanisms allowing more than one DNS name server to share a single\n IP address, it is sometimes difficult to tell which of a pool of name\n servers has answered a particular query. While existing ad-hoc\n mechanisms allow an operator to send follow-up queries when it is\n necessary to debug such a configuration, the only completely reliable\n way to obtain the identity of the name server that responded is to\n have the name server include this information in the response itself.\n This note defines a protocol extension to support this functionality.\n\nAustein Standards Track [Page 1]\n\f\nRFC 5001 DNS NSID August 2007 5001 key presentation trust nested-reference unchanged"},{"id":"IETF RFC 5003","type":"specification","body":"IETF","designation":"RFC 5003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5003.txt","https://www.rfc-editor.org/rfc/rfc5003.pdf"],"folder":"IETF/RFC-5003","files":{"txt":{"path":"standards/IETF/RFC-5003/RFC-5003.txt","sha256":"cd037ff2610ae0fbf64777ab7b5ce0d3c13169e46aa306b5a9bf388d7a45b777"}},"tags":["nested-reference","unchanged"],"summary":"The signaling protocols used to establish point-to-point pseudowires\n include type-length-value (TLV) fields that identify pseudowire\n endpoints called attachment individual identifiers (AIIs). This\n document defines AII structures in the form of new AII TLV fields\n that support AII aggregation for improved scalability and Virtual\n Private Network (VPN) auto-discovery. It is envisioned that this\n would be useful in large inter-domain virtual private wire service\n networks where pseudowires are established between selected local and\n remote provider edge (PE) nodes based on customer need.","scope_keywords":["5003","key","management","qualified","subject","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null}],"search_text":"IETF RFC 5003 The signaling protocols used to establish point-to-point pseudowires\n include type-length-value (TLV) fields that identify pseudowire\n endpoints called attachment individual identifiers (AIIs). This\n document defines AII structures in the form of new AII TLV fields\n that support AII aggregation for improved scalability and Virtual\n Private Network (VPN) auto-discovery. It is envisioned that this\n would be useful in large inter-domain virtual private wire service\n networks where pseudowires are established between selected local and\n remote provider edge (PE) nodes based on customer need. 5003 key management qualified subject validation nested-reference unchanged"},{"id":"IETF RFC 5005","type":"specification","body":"IETF","designation":"RFC 5005","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5005.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5005.txt","https://www.rfc-editor.org/rfc/rfc5005.pdf"],"folder":"IETF/RFC-5005","files":{"txt":{"path":"standards/IETF/RFC-5005/RFC-5005.txt","sha256":"29f4f92d0f081a44a2a258ccb6441a6dcf13dcbdb512c761ff5a2d3b8e659b29"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines three types of syndicated Web feeds that\n enable publication of entries across one or more feed documents.\n This includes \"paged\" feeds for piecemeal access, \"archived\" feeds\n that allow reconstruction of the feed's contents, and feeds that are\n explicitly \"complete\".","scope_keywords":["5005","archiving","http","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 5005 This specification defines three types of syndicated Web feeds that\n enable publication of entries across one or more feed documents.\n This includes \"paged\" feeds for piecemeal access, \"archived\" feeds\n that allow reconstruction of the feed's contents, and feeds that are\n explicitly \"complete\". 5005 archiving http key presentation nested-reference unchanged"},{"id":"IETF RFC 5007","type":"specification","body":"IETF","designation":"RFC 5007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5007.txt","https://www.rfc-editor.org/rfc/rfc5007.pdf"],"folder":"IETF/RFC-5007","files":{"txt":{"path":"standards/IETF/RFC-5007/RFC-5007.txt","sha256":"002bae4796e4f7d94e8a57929bd46780410b8856cd7cc8adfae01620fdb61892"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a leasequery exchange for the Dynamic Host\n Configuration Protocol for IPv6 (DHCPv6) that can be used to obtain\n lease information about DHCPv6 clients from a DHCPv6 server. This\n document specifies the scope of data that can be retrieved as well as\n both DHCPv6 leasequery requestor and server behavior. This document\n extends DHCPv6.\n\nBrzozowski, et al. Standards Track [Page 1]\n\f\nRFC 5007 DHCPv6 Leasequery September 2007","scope_keywords":["5007","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5460","folder":"IETF/RFC-5460","source":"IETF/RFC-5460/RFC-5460.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 5007 This document specifies a leasequery exchange for the Dynamic Host\n Configuration Protocol for IPv6 (DHCPv6) that can be used to obtain\n lease information about DHCPv6 clients from a DHCPv6 server. This\n document specifies the scope of data that can be retrieved as well as\n both DHCPv6 leasequery requestor and server behavior. This document\n extends DHCPv6.\n\nBrzozowski, et al. Standards Track [Page 1]\n\f\nRFC 5007 DHCPv6 Leasequery September 2007 5007 key validation nested-reference unchanged"},{"id":"IETF RFC 5010","type":"specification","body":"IETF","designation":"RFC 5010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5010.txt","https://www.rfc-editor.org/rfc/rfc5010.pdf"],"folder":"IETF/RFC-5010","files":{"txt":{"path":"standards/IETF/RFC-5010/RFC-5010.txt","sha256":"9a07097efdf06e18a329ebb0fe497c6cb11911017ec09d3ce466596e1a2366c9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new suboption of the Dynamic Host Configuration\n Protocol (DHCP) relay agent information option that allows the DHCP\n relay to specify flags for the forwarded packet. One flag is defined\n to indicate whether the DHCP relay received the packet via a unicast\n or broadcast packet. This information may be used by the DHCP server\n to better serve clients based on whether their request was originally\n broadcast or unicast.","scope_keywords":["5010","algorithm","algorithms","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5107","folder":"IETF/RFC-5107","source":"IETF/RFC-5107/RFC-5107.txt","version":null}],"search_text":"IETF RFC 5010 This memo defines a new suboption of the Dynamic Host Configuration\n Protocol (DHCP) relay agent information option that allows the DHCP\n relay to specify flags for the forwarded packet. One flag is defined\n to indicate whether the DHCP relay received the packet via a unicast\n or broadcast packet. This information may be used by the DHCP server\n to better serve clients based on whether their request was originally\n broadcast or unicast. 5010 algorithm algorithms attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 5011","type":"specification","body":"IETF","designation":"RFC 5011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5011.txt","https://www.rfc-editor.org/rfc/rfc5011.pdf"],"folder":"IETF/RFC-5011","files":{"txt":{"path":"standards/IETF/RFC-5011/RFC-5011.txt","sha256":"e00a848ca0fb6da1925ea828ea893a746f4d02528d70fedaab44b447c0778ed1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a means for automated, authenticated, and\n authorized updating of DNSSEC \"trust anchors\". The method provides\n protection against N-1 key compromises of N keys in the trust point\n key set. Based on the trust established by the presence of a current\n anchor, other anchors may be added at the same place in the\n hierarchy, and, ultimately, supplant the existing anchor(s).\n\n This mechanism will require changes to resolver management behavior\n (but not resolver resolution behavior), and the addition of a single\n flag bit to the DNSKEY record.\n\nStJohns Standards Track [Page 1]\n\f\nRFC 5011 Trust Anchor Update September 2007","scope_keywords":["5011","key","keys","management","policy","revocation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 7344","folder":"IETF/RFC-7344","source":"IETF/RFC-7344/RFC-7344.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null}],"search_text":"IETF RFC 5011 This document describes a means for automated, authenticated, and\n authorized updating of DNSSEC \"trust anchors\". The method provides\n protection against N-1 key compromises of N keys in the trust point\n key set. Based on the trust established by the presence of a current\n anchor, other anchors may be added at the same place in the\n hierarchy, and, ultimately, supplant the existing anchor(s).\n\n This mechanism will require changes to resolver management behavior\n (but not resolver resolution behavior), and the addition of a single\n flag bit to the DNSKEY record.\n\nStJohns Standards Track [Page 1]\n\f\nRFC 5011 Trust Anchor Update September 2007 5011 key keys management policy revocation trust nested-reference unchanged"},{"id":"IETF RFC 5012","type":"specification","body":"IETF","designation":"RFC 5012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5012.txt","https://www.rfc-editor.org/rfc/rfc5012.pdf"],"folder":"IETF/RFC-5012","files":{"txt":{"path":"standards/IETF/RFC-5012/RFC-5012.txt","sha256":"b65c5b31366679285166c9fb809ba1c4c1c686686f8adb0b5ec9c9bb561fd6b5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines terminology and enumerates requirements for the\n context resolution of emergency calls placed by the public using\n voice-over-IP (VoIP) and general Internet multimedia systems, where\n Internet protocols are used end to end.","scope_keywords":["5012","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5069","folder":"IETF/RFC-5069","source":"IETF/RFC-5069/RFC-5069.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5012 This document defines terminology and enumerates requirements for the\n context resolution of emergency calls placed by the public using\n voice-over-IP (VoIP) and general Internet multimedia systems, where\n Internet protocols are used end to end. 5012 identification key nested-reference unchanged"},{"id":"IETF RFC 5014","type":"specification","body":"IETF","designation":"RFC 5014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5014.txt","https://www.rfc-editor.org/rfc/rfc5014.pdf"],"folder":"IETF/RFC-5014","files":{"txt":{"path":"standards/IETF/RFC-5014/RFC-5014.txt","sha256":"ba7ac6fa0a5d6189216f27da99ed658c875b47c1999bdb4261c520ce0229db57"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 default address selection document (RFC 3484) describes the\n rules for selecting source and destination IPv6 addresses, and\n indicates that applications should be able to reverse the sense of\n some of the address selection rules through some unspecified API.\n However, no such socket API exists in the basic (RFC 3493) or\n advanced (RFC 3542) IPv6 socket API documents. This document fills\n that gap partially by specifying new socket-level options for source\n address selection and flags for the getaddrinfo() API to specify\n address selection based on the source address preference in\n accordance with the socket-level options that modify the default\n source address selection algorithm. The socket API described in this\n document will be particularly useful for IPv6 applications that want\n to choose between temporary and public addresses, and for Mobile IPv6\n aware applications that wa","scope_keywords":["5014","algorithm","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5220","folder":"IETF/RFC-5220","source":"IETF/RFC-5220/RFC-5220.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 5014 The IPv6 default address selection document (RFC 3484) describes the\n rules for selecting source and destination IPv6 addresses, and\n indicates that applications should be able to reverse the sense of\n some of the address selection rules through some unspecified API.\n However, no such socket API exists in the basic (RFC 3493) or\n advanced (RFC 3542) IPv6 socket API documents. This document fills\n that gap partially by specifying new socket-level options for source\n address selection and flags for the getaddrinfo() API to specify\n address selection based on the source address preference in\n accordance with the socket-level options that modify the default\n source address selection algorithm. The socket API described in this\n document will be particularly useful for IPv6 applications that want\n to choose between temporary and public addresses, and for Mobile IPv6\n aware applications that wa 5014 algorithm attribute attributes nested-reference unchanged"},{"id":"IETF RFC 5015","type":"specification","body":"IETF","designation":"RFC 5015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5015.txt","https://www.rfc-editor.org/rfc/rfc5015.pdf"],"folder":"IETF/RFC-5015","files":{"txt":{"path":"standards/IETF/RFC-5015/RFC-5015.txt","sha256":"70c928fdb97cfe222b2b4c69cafff776d5007ded4ca181cedb7b6cf77b8521be"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses Bidirectional PIM (BIDIR-PIM), a variant of\n PIM Sparse-Mode that builds bidirectional shared trees connecting\n multicast sources and receivers. Bidirectional trees are built using\n a fail-safe Designated Forwarder (DF) election mechanism operating on\n each link of a multicast topology. With the assistance of the DF,\n multicast data is natively forwarded from sources to the Rendezvous-\n Point (RP) and hence along the shared tree to receivers without\n requiring source-specific state. The DF election takes place at RP\n discovery time and provides the route to the RP, thus eliminating the\n requirement for data-driven protocol events.\n\nHandley, et al. Standards Track [Page 1]\n\f\nRFC 5015 Bidirectional PIM October 2007","scope_keywords":["5015","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5059","folder":"IETF/RFC-5059","source":"IETF/RFC-5059/RFC-5059.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5294","folder":"IETF/RFC-5294","source":"IETF/RFC-5294/RFC-5294.txt","version":null},{"body":"IETF","designation":"RFC 5384","folder":"IETF/RFC-5384","source":"IETF/RFC-5384/RFC-5384.txt","version":null},{"body":"IETF","designation":"RFC 5496","folder":"IETF/RFC-5496","source":"IETF/RFC-5496/RFC-5496.txt","version":null},{"body":"IETF","designation":"RFC 5501","folder":"IETF/RFC-5501","source":"IETF/RFC-5501/RFC-5501.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6807","folder":"IETF/RFC-6807","source":"IETF/RFC-6807/RFC-6807.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 7348","folder":"IETF/RFC-7348","source":"IETF/RFC-7348/RFC-7348.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 5015 This document discusses Bidirectional PIM (BIDIR-PIM), a variant of\n PIM Sparse-Mode that builds bidirectional shared trees connecting\n multicast sources and receivers. Bidirectional trees are built using\n a fail-safe Designated Forwarder (DF) election mechanism operating on\n each link of a multicast topology. With the assistance of the DF,\n multicast data is natively forwarded from sources to the Rendezvous-\n Point (RP) and hence along the shared tree to receivers without\n requiring source-specific state. The DF election takes place at RP\n discovery time and provides the route to the RP, thus eliminating the\n requirement for data-driven protocol events.\n\nHandley, et al. Standards Track [Page 1]\n\f\nRFC 5015 Bidirectional PIM October 2007 5015 authentication path nested-reference unchanged"},{"id":"IETF RFC 5016","type":"specification","body":"IETF","designation":"RFC 5016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5016.txt","https://www.rfc-editor.org/rfc/rfc5016.pdf"],"folder":"IETF/RFC-5016","files":{"txt":{"path":"standards/IETF/RFC-5016/RFC-5016.txt","sha256":"9f730b8d4b3099e08204c0f942ca67d97fd3caf2d870cc1f7a27f44131d49c74"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism\n for domains to assert responsibility for the messages they handle. A\n related mechanism will allow an administrator to publish various\n statements about their DKIM signing practices. This document defines\n requirements for this mechanism, distinguishing between those that\n must be satisfied (MUST), and those that are highly desirable\n (SHOULD).\n\nThomas Informational [Page 1]\n\f\nRFC 5016 DKIM-SSP-REQ October 2007","scope_keywords":["5016","audit","authentication","holder","key","keys","signature","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null}],"search_text":"IETF RFC 5016 DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism\n for domains to assert responsibility for the messages they handle. A\n related mechanism will allow an administrator to publish various\n statements about their DKIM signing practices. This document defines\n requirements for this mechanism, distinguishing between those that\n must be satisfied (MUST), and those that are highly desirable\n (SHOULD).\n\nThomas Informational [Page 1]\n\f\nRFC 5016 DKIM-SSP-REQ October 2007 5016 audit authentication holder key keys signature verifiable nested-reference unchanged"},{"id":"IETF RFC 5017","type":"specification","body":"IETF","designation":"RFC 5017","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5017.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5017.txt","https://www.rfc-editor.org/rfc/rfc5017.pdf"],"folder":"IETF/RFC-5017","files":{"txt":{"path":"standards/IETF/RFC-5017/RFC-5017.txt","sha256":"c909665014098743bea6cfc455566c91fe4a746467d0cc5ac7bd5ac3d5fff9f9"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent STD 66\n Uniform Resource Identifiers (URIs). The intent is that these\n textual conventions will be imported and used in MIB modules that\n would otherwise define their own representation(s).","scope_keywords":["5017","http","key","management","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 5017 This MIB module defines textual conventions to represent STD 66\n Uniform Resource Identifiers (URIs). The intent is that these\n textual conventions will be imported and used in MIB modules that\n would otherwise define their own representation(s). 5017 http key management presentation trust nested-reference unchanged"},{"id":"IETF RFC 5018","type":"specification","body":"IETF","designation":"RFC 5018","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5018.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5018.txt","https://www.rfc-editor.org/rfc/rfc5018.pdf"],"folder":"IETF/RFC-5018","files":{"txt":{"path":"standards/IETF/RFC-5018/RFC-5018.txt","sha256":"ce9946d8a2a4ef2154a158c4a8017115a1db092e580ef57a6178d9020c2f0e45"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how a Binary Floor Control Protocol (BFCP)\n client establishes a connection to a BFCP floor control server\n outside the context of an offer/answer exchange. Client and server\n authentication are based on Transport Layer Security (TLS).","scope_keywords":["5018","algorithm","algorithms","authentication","certificate","certificates","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5018 This document specifies how a Binary Floor Control Protocol (BFCP)\n client establishes a connection to a BFCP floor control server\n outside the context of an offer/answer exchange. Client and server\n authentication are based on Transport Layer Security (TLS). 5018 algorithm algorithms authentication certificate certificates key tls nested-reference unchanged"},{"id":"IETF RFC 5019","type":"specification","body":"IETF","designation":"RFC 5019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5019.txt","https://www.rfc-editor.org/rfc/rfc5019.pdf"],"folder":"IETF/RFC-5019","files":{"txt":{"path":"standards/IETF/RFC-5019/RFC-5019.txt","sha256":"d35c5115e32470a0be559cc83275f52b2e84f5bbeafcaf0c9f8ccb490256fa16"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a profile of the Online Certificate Status\n Protocol (OCSP) that addresses the scalability issues inherent when\n using OCSP in large scale (high volume) Public Key Infrastructure\n (PKI) environments and/or in PKI environments that require a\n lightweight solution to minimize communication bandwidth and client-\n side processing.\n\nDeacon & Hurst Standards Track [Page 1]\n\f\nRFC 5019 Lightweight OCSP Profile September 2007","scope_keywords":["5019","authentication","authorization","certificate","certificates","crl","http","key","ocsp","pki","profile","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5019 This specification defines a profile of the Online Certificate Status\n Protocol (OCSP) that addresses the scalability issues inherent when\n using OCSP in large scale (high volume) Public Key Infrastructure\n (PKI) environments and/or in PKI environments that require a\n lightweight solution to minimize communication bandwidth and client-\n side processing.\n\nDeacon & Hurst Standards Track [Page 1]\n\f\nRFC 5019 Lightweight OCSP Profile September 2007 5019 authentication authorization certificate certificates crl http key ocsp pki profile revocation nested-reference unchanged"},{"id":"IETF RFC 5023","type":"specification","body":"IETF","designation":"RFC 5023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5023.txt","https://www.rfc-editor.org/rfc/rfc5023.pdf"],"folder":"IETF/RFC-5023","files":{"txt":{"path":"standards/IETF/RFC-5023/RFC-5023.txt","sha256":"3765e3515b49478fec8fff051a02fddc7ea443a98d7fe9540434edcb601d0338"}},"tags":["nested-reference","unchanged"],"summary":"The Atom Publishing Protocol (AtomPub) is an application-level\n protocol for publishing and editing Web resources. The protocol is\n based on HTTP transfer of Atom-formatted representations. The Atom\n format is documented in the Atom Syndication Format.\n\nGregorio & de hOra Standards Track [Page 1]\n\f\nRFC 5023 The Atom Publishing Protocol October 2007","scope_keywords":["5023","encryption","http","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5829","folder":"IETF/RFC-5829","source":"IETF/RFC-5829/RFC-5829.txt","version":null},{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5023 The Atom Publishing Protocol (AtomPub) is an application-level\n protocol for publishing and editing Web resources. The protocol is\n based on HTTP transfer of Atom-formatted representations. The Atom\n format is documented in the Atom Syndication Format.\n\nGregorio & de hOra Standards Track [Page 1]\n\f\nRFC 5023 The Atom Publishing Protocol October 2007 5023 encryption http presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 5025","type":"specification","body":"IETF","designation":"RFC 5025","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5025.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5025.txt","https://www.rfc-editor.org/rfc/rfc5025.pdf"],"folder":"IETF/RFC-5025","files":{"txt":{"path":"standards/IETF/RFC-5025/RFC-5025.txt","sha256":"7123aca4220345a41b4912f57eb10d74a5fa73eba69faa408127abfc6a138862"}},"tags":["nested-reference","unchanged"],"summary":"Authorization is a key function in presence systems. Authorization\n policies, also known as authorization rules, specify what presence\n information can be given to which watchers, and when. This\n specification defines an Extensible Markup Language (XML) document\n format for expressing presence authorization rules. Such a document\n can be manipulated by clients using the XML Configuration Access\n Protocol (XCAP), although other techniques are permitted.","scope_keywords":["5025","attribute","attributes","authentication","authorization","key","policies","policy","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5039","folder":"IETF/RFC-5039","source":"IETF/RFC-5039/RFC-5039.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 5025 Authorization is a key function in presence systems. Authorization\n policies, also known as authorization rules, specify what presence\n information can be given to which watchers, and when. This\n specification defines an Extensible Markup Language (XML) document\n format for expressing presence authorization rules. Such a document\n can be manipulated by clients using the XML Configuration Access\n Protocol (XCAP), although other techniques are permitted. 5025 attribute attributes authentication authorization key policies policy validation nested-reference unchanged"},{"id":"IETF RFC 5026","type":"specification","body":"IETF","designation":"RFC 5026","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5026.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5026.txt","https://www.rfc-editor.org/rfc/rfc5026.pdf"],"folder":"IETF/RFC-5026","files":{"txt":{"path":"standards/IETF/RFC-5026/RFC-5026.txt","sha256":"537fb2ec7804325e3c31926efa2d2f83771e7289407f8ca9ce278a042feebb00"}},"tags":["nested-reference","unchanged"],"summary":"A Mobile IPv6 node requires a Home Agent address, a home address, and\n IPsec security associations with its Home Agent before it can start\n utilizing Mobile IPv6 service. RFC 3775 requires that some or all of\n these are statically configured. This document defines how a Mobile\n IPv6 node can bootstrap this information from non-topological\n information and security credentials pre-configured on the Mobile\n Node. The solution defined in this document solves the split\n scenario described in the Mobile IPv6 bootstrapping problem statement\n in RFC 4640. The split scenario refers to the case where the Mobile\n Node's mobility service is authorized by a different service provider\n than basic network access. The solution described in this document\n is also generically applicable to any bootstrapping case, since other\n scenarios are more specific realizations of the split scenario.\n\nGiaretta, et a","scope_keywords":["5026","attribute","authentication","authorization","certificate","certificates","credential","credentials","key","keys","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 7039","folder":"IETF/RFC-7039","source":"IETF/RFC-7039/RFC-7039.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5026 A Mobile IPv6 node requires a Home Agent address, a home address, and\n IPsec security associations with its Home Agent before it can start\n utilizing Mobile IPv6 service. RFC 3775 requires that some or all of\n these are statically configured. This document defines how a Mobile\n IPv6 node can bootstrap this information from non-topological\n information and security credentials pre-configured on the Mobile\n Node. The solution defined in this document solves the split\n scenario described in the Mobile IPv6 bootstrapping problem statement\n in RFC 4640. The split scenario refers to the case where the Mobile\n Node's mobility service is authorized by a different service provider\n than basic network access. The solution described in this document\n is also generically applicable to any bootstrapping case, since other\n scenarios are more specific realizations of the split scenario.\n\nGiaretta, et a 5026 attribute authentication authorization certificate certificates credential credentials key keys tsp nested-reference unchanged"},{"id":"IETF RFC 5027","type":"specification","body":"IETF","designation":"RFC 5027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5027.txt","https://www.rfc-editor.org/rfc/rfc5027.pdf"],"folder":"IETF/RFC-5027","files":{"txt":{"path":"standards/IETF/RFC-5027/RFC-5027.txt","sha256":"3c0e66a389c09bf56e8c5885f27cba88efe94bc623079afc4d85b9a3e57b44ec"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new security precondition for the Session\n Description Protocol (SDP) precondition framework described in RFCs\n 3312 and 4032. A security precondition can be used to delay session\n establishment or modification until media stream security for a\n secure media stream has been negotiated successfully.","scope_keywords":["5027","algorithm","encryption","key","management","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null}],"search_text":"IETF RFC 5027 This document defines a new security precondition for the Session\n Description Protocol (SDP) precondition framework described in RFCs\n 3312 and 4032. A security precondition can be used to delay session\n establishment or modification until media stream security for a\n secure media stream has been negotiated successfully. 5027 algorithm encryption key management profile nested-reference unchanged"},{"id":"IETF RFC 5035","type":"specification","body":"IETF","designation":"RFC 5035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5035.txt","https://www.rfc-editor.org/rfc/rfc5035.pdf"],"folder":"IETF/RFC-5035","files":{"txt":{"path":"standards/IETF/RFC-5035/RFC-5035.txt","sha256":"7c4a793911463367bd777e6d6104e52ec709f0c553da237cdf6782ee49b6d32b"}},"tags":["nested-reference","unchanged"],"summary":"In the original Enhanced Security Services for S/MIME document (RFC\n 2634), a structure for cryptographically linking the certificate to\n be used in validation with the signature was introduced; this\n structure was hardwired to use SHA-1. This document allows for the\n structure to have algorithm agility and defines a new attribute for\n this purpose.","scope_keywords":["5035","algorithm","algorithms","attribute","attributes","certificate","certificates","hash","identification","issuer","key","policies","policy","signature","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 522-3","folder":"ETSI/EN-319-522-3-V1.2.1","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 5035 In the original Enhanced Security Services for S/MIME document (RFC\n 2634), a structure for cryptographically linking the certificate to\n be used in validation with the signature was introduced; this\n structure was hardwired to use SHA-1. This document allows for the\n structure to have algorithm agility and defines a new attribute for\n this purpose. 5035 algorithm algorithms attribute attributes certificate certificates hash identification issuer key policies policy signature validation nested-reference unchanged"},{"id":"IETF RFC 5040","type":"specification","body":"IETF","designation":"RFC 5040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5040.txt","https://www.rfc-editor.org/rfc/rfc5040.pdf"],"folder":"IETF/RFC-5040","files":{"txt":{"path":"standards/IETF/RFC-5040/RFC-5040.txt","sha256":"0252042ba0a66566f645898e2c0259412750310f74a6e8579819884cbb3412f5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Remote Direct Memory Access Protocol (RDMAP)\n that operates over the Direct Data Placement Protocol (DDP protocol).\n RDMAP provides read and write services directly to applications and\n enables data to be transferred directly into Upper Layer Protocol\n (ULP) Buffers without intermediate data copies. It also enables a\n kernel bypass implementation.\n\nRecio, et al. Standards Track [Page 1]\n\f\nRFC 5040 RDMA Protocol Specification October 2007","scope_keywords":["5040","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5040 This document defines a Remote Direct Memory Access Protocol (RDMAP)\n that operates over the Direct Data Placement Protocol (DDP protocol).\n RDMAP provides read and write services directly to applications and\n enables data to be transferred directly into Upper Layer Protocol\n (ULP) Buffers without intermediate data copies. It also enables a\n kernel bypass implementation.\n\nRecio, et al. Standards Track [Page 1]\n\f\nRFC 5040 RDMA Protocol Specification October 2007 5040 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 5041","type":"specification","body":"IETF","designation":"RFC 5041","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5041.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5041.txt","https://www.rfc-editor.org/rfc/rfc5041.pdf"],"folder":"IETF/RFC-5041","files":{"txt":{"path":"standards/IETF/RFC-5041/RFC-5041.txt","sha256":"95f58f45986b26ce0efce8cc9fe21297025c62f7d079568110024210b3d350cc"}},"tags":["nested-reference","unchanged"],"summary":"The Direct Data Placement protocol provides information to Place the\n incoming data directly into an upper layer protocol's receive buffer\n without intermediate buffers. This removes excess CPU and memory\n utilization associated with transferring data through the\n intermediate buffers.","scope_keywords":["5041","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 5667","folder":"IETF/RFC-5667","source":"IETF/RFC-5667/RFC-5667.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5041 The Direct Data Placement protocol provides information to Place the\n incoming data directly into an upper layer protocol's receive buffer\n without intermediate buffers. This removes excess CPU and memory\n utilization associated with transferring data through the\n intermediate buffers. 5041 delivery key nested-reference unchanged"},{"id":"IETF RFC 5042","type":"specification","body":"IETF","designation":"RFC 5042","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5042.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5042.txt","https://www.rfc-editor.org/rfc/rfc5042.pdf"],"folder":"IETF/RFC-5042","files":{"txt":{"path":"standards/IETF/RFC-5042/RFC-5042.txt","sha256":"ba0c9ab4291943ffc19b7eeefd13c75f07da029b557d311785f1643b23c3de8b"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes security issues around implementation and use\n of the Direct Data Placement Protocol (DDP) and Remote Direct Memory\n Access Protocol (RDMAP). It first defines an architectural model for\n an RDMA Network Interface Card (RNIC), which can implement DDP or\n RDMAP and DDP. The document reviews various attacks against the\n resources defined in the architectural model and the countermeasures\n that can be used to protect the system. Attacks are grouped into\n those that can be mitigated by using secure communication channels\n across the network, attacks from Remote Peers, and attacks from Local\n Peers. Attack categories include spoofing, tampering, information\n disclosure, denial of service, and elevation of privilege.\n\nPinkerton & Deleganes Standards Track [Page 1]\n\f\nRFC 5042 DDP/RDMAP Security October 2007","scope_keywords":["5042","path","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 5666","folder":"IETF/RFC-5666","source":"IETF/RFC-5666/RFC-5666.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5042 This document analyzes security issues around implementation and use\n of the Direct Data Placement Protocol (DDP) and Remote Direct Memory\n Access Protocol (RDMAP). It first defines an architectural model for\n an RDMA Network Interface Card (RNIC), which can implement DDP or\n RDMAP and DDP. The document reviews various attacks against the\n resources defined in the architectural model and the countermeasures\n that can be used to protect the system. Attacks are grouped into\n those that can be mitigated by using secure communication channels\n across the network, attacks from Remote Peers, and attacks from Local\n Peers. Attack categories include spoofing, tampering, information\n disclosure, denial of service, and elevation of privilege.\n\nPinkerton & Deleganes Standards Track [Page 1]\n\f\nRFC 5042 DDP/RDMAP Security October 2007 5042 path tls trust nested-reference unchanged"},{"id":"IETF RFC 5043","type":"specification","body":"IETF","designation":"RFC 5043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5043.txt","https://www.rfc-editor.org/rfc/rfc5043.pdf"],"folder":"IETF/RFC-5043","files":{"txt":{"path":"standards/IETF/RFC-5043/RFC-5043.txt","sha256":"40042a0b330e7e4b6bb5823472dcf381d0afc432aa7c63d9062d56e73137ecb2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an adaptation layer to provide a Lower Layer\n Protocol (LLP) service for Direct Data Placement (DDP) using the\n Stream Control Transmission Protocol (SCTP).\n\nBestler & Stewart Standards Track [Page 1]\n\f\nRFC 5043 SCTP DDP Adaptation October 2007","scope_keywords":["5043","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5043 This document specifies an adaptation layer to provide a Lower Layer\n Protocol (LLP) service for Direct Data Placement (DDP) using the\n Stream Control Transmission Protocol (SCTP).\n\nBestler & Stewart Standards Track [Page 1]\n\f\nRFC 5043 SCTP DDP Adaptation October 2007 5043 key nested-reference unchanged"},{"id":"IETF RFC 5046","type":"specification","body":"IETF","designation":"RFC 5046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5046.txt","https://www.rfc-editor.org/rfc/rfc5046.pdf"],"folder":"IETF/RFC-5046","files":{"txt":{"path":"standards/IETF/RFC-5046/RFC-5046.txt","sha256":"c39f1aeff2e18da4e669e6bcda63c45eaf15909a1d36189dac84b4886a8c54eb"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer System Interface (iSCSI) Extensions for\n Remote Direct Memory Access (RDMA) provides the RDMA data transfer\n capability to iSCSI by layering iSCSI on top of an RDMA-Capable\n Protocol, such as the iWARP protocol suite. An RDMA-Capable Protocol\n provides RDMA Read and Write services, which enable data to be\n transferred directly into SCSI I/O Buffers without intermediate data\n copies. This document describes the extensions to the iSCSI protocol\n to support RDMA services as provided by an RDMA-Capable Protocol,\n such as the iWARP protocol suite.\n\nKo, et al. Standards Track [Page 1]\n\f\nRFC 5046 iSER Specification October 2007","scope_keywords":["5046","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5043","folder":"IETF/RFC-5043","source":"IETF/RFC-5043/RFC-5043.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5045","folder":"IETF/RFC-5045","source":"IETF/RFC-5045/RFC-5045.txt","version":null},{"body":"IETF","designation":"RFC 5047","folder":"IETF/RFC-5047","source":"IETF/RFC-5047/RFC-5047.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5046 Internet Small Computer System Interface (iSCSI) Extensions for\n Remote Direct Memory Access (RDMA) provides the RDMA data transfer\n capability to iSCSI by layering iSCSI on top of an RDMA-Capable\n Protocol, such as the iWARP protocol suite. An RDMA-Capable Protocol\n provides RDMA Read and Write services, which enable data to be\n transferred directly into SCSI I/O Buffers without intermediate data\n copies. This document describes the extensions to the iSCSI protocol\n to support RDMA services as provided by an RDMA-Capable Protocol,\n such as the iWARP protocol suite.\n\nKo, et al. Standards Track [Page 1]\n\f\nRFC 5046 iSER Specification October 2007 5046 key keys management nested-reference unchanged"},{"id":"IETF RFC 5047","type":"specification","body":"IETF","designation":"RFC 5047","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5047.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5047.txt","https://www.rfc-editor.org/rfc/rfc5047.pdf"],"folder":"IETF/RFC-5047","files":{"txt":{"path":"standards/IETF/RFC-5047/RFC-5047.txt","sha256":"1c922d1d65b2b7a48c5a99cfe6f06b67c286bef218afd1b59afba5d61572a9a3"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol that maps the SCSI family of application protocols\n onto TCP/IP. Datamover Architecture for iSCSI (DA) defines an\n abstract model in which the movement of data between iSCSI end nodes\n is logically separated from the rest of the iSCSI protocol in order\n to allow iSCSI to adapt to innovations available in new IP\n transports. While DA defines the architectural functions required of\n the class of Datamover protocols, it does not define any specific\n Datamover protocols. Each such Datamover protocol, defined in a\n separate document, provides a reliable transport for all iSCSI PDUs,\n but actually moves the data required for certain iSCSI PDUs without\n involving the remote iSCSI layer itself. This document begins with\n an introduction of a few new abstractions, defines a layered\n architecture for iSCSI and Datam","scope_keywords":["5047","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5047 The Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol that maps the SCSI family of application protocols\n onto TCP/IP. Datamover Architecture for iSCSI (DA) defines an\n abstract model in which the movement of data between iSCSI end nodes\n is logically separated from the rest of the iSCSI protocol in order\n to allow iSCSI to adapt to innovations available in new IP\n transports. While DA defines the architectural functions required of\n the class of Datamover protocols, it does not define any specific\n Datamover protocols. Each such Datamover protocol, defined in a\n separate document, provides a reliable transport for all iSCSI PDUs,\n but actually moves the data required for certain iSCSI PDUs without\n involving the remote iSCSI layer itself. This document begins with\n an introduction of a few new abstractions, defines a layered\n architecture for iSCSI and Datam 5047 key management nested-reference unchanged"},{"id":"IETF RFC 5048","type":"specification","body":"IETF","designation":"RFC 5048","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5048.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5048.txt","https://www.rfc-editor.org/rfc/rfc5048.pdf"],"folder":"IETF/RFC-5048","files":{"txt":{"path":"standards/IETF/RFC-5048/RFC-5048.txt","sha256":"86550e857b1ce5c8e6c1d5cc10365e95ffbaf5bd639851a2e16eb80e8c13383d"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol and maps the SCSI architecture and command sets\n onto TCP/IP. RFC 3720 defines the iSCSI protocol. This document\n compiles the clarifications to the original protocol definition in\n RFC 3720 to serve as a companion document for the iSCSI implementers.\n This document updates RFC 3720 and the text in this document\n supersedes the text in RFC 3720 when the two differ.","scope_keywords":["5048","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5048 The Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol and maps the SCSI architecture and command sets\n onto TCP/IP. RFC 3720 defines the iSCSI protocol. This document\n compiles the clarifications to the original protocol definition in\n RFC 3720 to serve as a companion document for the iSCSI implementers.\n This document updates RFC 3720 and the text in this document\n supersedes the text in RFC 3720 when the two differ. 5048 key keys management nested-reference unchanged"},{"id":"IETF RFC 5049","type":"specification","body":"IETF","designation":"RFC 5049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5049.txt","https://www.rfc-editor.org/rfc/rfc5049.pdf"],"folder":"IETF/RFC-5049","files":{"txt":{"path":"standards/IETF/RFC-5049/RFC-5049.txt","sha256":"6bbd707eff3f9526681d92d1bb02fd47fd3260d430013ea702ea7a70ab021457"}},"tags":["nested-reference","unchanged"],"summary":"This document describes some specifics that apply when Signaling\n Compression (SigComp) is applied to the Session Initiation Protocol\n (SIP), such as default minimum values of SigComp parameters,\n compartment and state management, and a few issues on SigComp over\n TCP. Any implementation of SigComp for use with SIP must conform to\n this document and SigComp, and in addition, support the SIP and\n Session Description Protocol (SDP) static dictionary.\n\nBormann, et al. Standards Track [Page 1]\n\f\nRFC 5049 Applying SigComp to SIP December 2007","scope_keywords":["5049","identification","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5049 This document describes some specifics that apply when Signaling\n Compression (SigComp) is applied to the Session Initiation Protocol\n (SIP), such as default minimum values of SigComp parameters,\n compartment and state management, and a few issues on SigComp over\n TCP. Any implementation of SigComp for use with SIP must conform to\n this document and SigComp, and in addition, support the SIP and\n Session Description Protocol (SDP) static dictionary.\n\nBormann, et al. Standards Track [Page 1]\n\f\nRFC 5049 Applying SigComp to SIP December 2007 5049 identification key management tls nested-reference unchanged"},{"id":"IETF RFC 5050","type":"specification","body":"IETF","designation":"RFC 5050","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5050.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5050.txt","https://www.rfc-editor.org/rfc/rfc5050.pdf"],"folder":"IETF/RFC-5050","files":{"txt":{"path":"standards/IETF/RFC-5050/RFC-5050.txt","sha256":"06d5b4d6abfb3ded01657dacec2548e61df19f3bc4c20a974ea135f6f1c4a005"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the end-to-end protocol, block formats, and\n abstract service description for the exchange of messages (bundles)\n in Delay Tolerant Networking (DTN).\n\n This document was produced within the IRTF's Delay Tolerant\n Networking Research Group (DTNRG) and represents the consensus of all\n of the active contributors to this group. See http://www.dtnrg.org\n for more information.\n\nScott & Burleigh Experimental [Page 1]\n\f\nRFC 5050 Bundle Protocol Specification November 2007","scope_keywords":["5050","delivery","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5325","folder":"IETF/RFC-5325","source":"IETF/RFC-5325/RFC-5325.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null}],"search_text":"IETF RFC 5050 This document describes the end-to-end protocol, block formats, and\n abstract service description for the exchange of messages (bundles)\n in Delay Tolerant Networking (DTN).\n\n This document was produced within the IRTF's Delay Tolerant\n Networking Research Group (DTNRG) and represents the consensus of all\n of the active contributors to this group. See http://www.dtnrg.org\n for more information.\n\nScott & Burleigh Experimental [Page 1]\n\f\nRFC 5050 Bundle Protocol Specification November 2007 5050 delivery http key nested-reference unchanged"},{"id":"IETF RFC 5052","type":"specification","body":"IETF","designation":"RFC 5052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5052.txt","https://www.rfc-editor.org/rfc/rfc5052.pdf"],"folder":"IETF/RFC-5052","files":{"txt":{"path":"standards/IETF/RFC-5052/RFC-5052.txt","sha256":"f82b9d6371b196be9e0eddff2f8a30ff3332272f3ded8f101a0ddc5d89a889e6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use Forward Error Correction (FEC)\n codes to efficiently provide and/or augment reliability for bulk data\n transfer over IP multicast. This document defines a framework for\n the definition of the information that needs to be communicated in\n order to use an FEC code for bulk data transfer, in addition to the\n encoded data itself, and for definition of formats and codes for\n communication of that information. Both information communicated\n with the encoded data itself and information that needs to be\n communicated 'out-of-band' are considered. The procedures for\n specifying new FEC codes, defining the information communication\n requirements associated with those codes and registering them with\n the Internet Assigned Numbers Authority (IANA) are also described.\n The requirements on Content Delivery Protocols that wish to use FEC\n codes defined within this fra","scope_keywords":["5052","algorithm","algorithms","delivery","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5401","folder":"IETF/RFC-5401","source":"IETF/RFC-5401/RFC-5401.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 5052 This document describes how to use Forward Error Correction (FEC)\n codes to efficiently provide and/or augment reliability for bulk data\n transfer over IP multicast. This document defines a framework for\n the definition of the information that needs to be communicated in\n order to use an FEC code for bulk data transfer, in addition to the\n encoded data itself, and for definition of formats and codes for\n communication of that information. Both information communicated\n with the encoded data itself and information that needs to be\n communicated 'out-of-band' are considered. The procedures for\n specifying new FEC codes, defining the information communication\n requirements associated with those codes and registering them with\n the Internet Assigned Numbers Authority (IANA) are also described.\n The requirements on Content Delivery Protocols that wish to use FEC\n codes defined within this fra 5052 algorithm algorithms delivery trust nested-reference unchanged"},{"id":"IETF RFC 5055","type":"specification","body":"IETF","designation":"RFC 5055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5055.txt","https://www.rfc-editor.org/rfc/rfc5055.pdf"],"folder":"IETF/RFC-5055","files":{"txt":{"path":"standards/IETF/RFC-5055/RFC-5055.txt","sha256":"63dbc6a193b4adf868d2dca28bb19bd9b25f60d4a1f3b11b9be7992cec9402e9"}},"tags":["nested-reference","unchanged"],"summary":"The Server-Based Certificate Validation Protocol (SCVP) allows a\n client to delegate certification path construction and certification\n path validation to a server. The path construction or validation\n (e.g., making sure that none of the certificates in the path are\n revoked) is performed according to a validation policy, which\n contains one or more trust anchors. It allows simplification of\n client implementations and use of a set of predefined validation\n policies.","scope_keywords":["5055","algorithm","authentication","certificate","certificates","hash","key","path","policies","policy","signature","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null}],"search_text":"IETF RFC 5055 The Server-Based Certificate Validation Protocol (SCVP) allows a\n client to delegate certification path construction and certification\n path validation to a server. The path construction or validation\n (e.g., making sure that none of the certificates in the path are\n revoked) is performed according to a validation policy, which\n contains one or more trust anchors. It allows simplification of\n client implementations and use of a set of predefined validation\n policies. 5055 algorithm authentication certificate certificates hash key path policies policy signature trust validation nested-reference unchanged"},{"id":"IETF RFC 5059","type":"specification","body":"IETF","designation":"RFC 5059","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5059.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5059.txt","https://www.rfc-editor.org/rfc/rfc5059.pdf"],"folder":"IETF/RFC-5059","files":{"pdf":{"path":"standards/IETF/RFC-5059/RFC-5059.pdf","sha256":"48c35e491affefb301699ec412245668c2bb91543af2f67bbf7d422195cadfc5"},"txt":{"path":"standards/IETF/RFC-5059/RFC-5059.txt","sha256":"8a51edb20f5c2e6270e4ca672619d13a9ce4f8c1e2119db0d1990c562267dbdc"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Bootstrap Router (BSR) mechanism for the\n class of multicast routing protocols in the PIM (Protocol Independent\n Multicast) family that use the concept of a Rendezvous Point as a\n means for receivers to discover the sources that send to a particular\n multicast group. BSR is one way that a multicast router can learn\n the set of group-to-RP mappings required in order to function. The\n mechanism is dynamic, largely self-configuring, and robust to router\n failure.\n\nBhaskar, et al. Standards Track [Page 1]\n\f\nRFC 5059 BSR Mechanism for PIM January 2008","scope_keywords":["5059","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null},{"body":"IETF","designation":"RFC 5110","folder":"IETF/RFC-5110","source":"IETF/RFC-5110/RFC-5110.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 5059 This document specifies the Bootstrap Router (BSR) mechanism for the\n class of multicast routing protocols in the PIM (Protocol Independent\n Multicast) family that use the concept of a Rendezvous Point as a\n means for receivers to discover the sources that send to a particular\n multicast group. BSR is one way that a multicast router can learn\n the set of group-to-RP mappings required in order to function. The\n mechanism is dynamic, largely self-configuring, and robust to router\n failure.\n\nBhaskar, et al. Standards Track [Page 1]\n\f\nRFC 5059 BSR Mechanism for PIM January 2008 5059 key nested-reference unchanged"},{"id":"IETF RFC 5060","type":"specification","body":"IETF","designation":"RFC 5060","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5060.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5060.txt","https://www.rfc-editor.org/rfc/rfc5060.pdf"],"folder":"IETF/RFC-5060","files":{"txt":{"path":"standards/IETF/RFC-5060/RFC-5060.txt","sha256":"65530d6666705f78f212f966aa64527ccae692c4ee8f1ff279354c5c1a41ed43"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Protocol Independent Multicast (PIM) protocols: PIM-SM (Sparse Mode),\n BIDIR-PIM (Bidirectional), and PIM-DM (Dense Mode). This document is\n part of work in progress to obsolete RFC 2934, and is to be preferred\n where the two documents overlap. This document does not obsolete RFC\n 2934.","scope_keywords":["5060","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5060 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Protocol Independent Multicast (PIM) protocols: PIM-SM (Sparse Mode),\n BIDIR-PIM (Bidirectional), and PIM-DM (Dense Mode). This document is\n part of work in progress to obsolete RFC 2934, and is to be preferred\n where the two documents overlap. This document does not obsolete RFC\n 2934. 5060 key management nested-reference unchanged"},{"id":"IETF RFC 5063","type":"specification","body":"IETF","designation":"RFC 5063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5063.txt","https://www.rfc-editor.org/rfc/rfc5063.pdf"],"folder":"IETF/RFC-5063","files":{"txt":{"path":"standards/IETF/RFC-5063/RFC-5063.txt","sha256":"a0e96b0738d05bf9402606629574ebe73a4c360feabc470e4ed1f8c3dde56601"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Resource Reservation\n Protocol (RSVP) Graceful Restart mechanisms defined in RFC 3473. The\n extensions enable the recovery of RSVP signaling state based on the\n Path message last sent by the node being restarted.\n\n Previously defined Graceful Restart mechanisms, also called recovery\n from nodal faults, permit recovery of signaling state from adjacent\n nodes when the data plane has retained the associated forwarding\n state across a restart. Those mechanisms do not fully support\n signaling state recovery on ingress nodes or recovery of all RSVP\n objects.\n\n The extensions defined in this document build on the RSVP Hello\n extensions defined in RFC 3209, and extensions for state recovery on\n nodal faults defined in RFC 3473. Using these extensions, the\n restarting node can recover all previously transmitted Path state,\n including the Explicit Route Ob","scope_keywords":["5063","attribute","path","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null}],"search_text":"IETF RFC 5063 This document describes extensions to the Resource Reservation\n Protocol (RSVP) Graceful Restart mechanisms defined in RFC 3473. The\n extensions enable the recovery of RSVP signaling state based on the\n Path message last sent by the node being restarted.\n\n Previously defined Graceful Restart mechanisms, also called recovery\n from nodal faults, permit recovery of signaling state from adjacent\n nodes when the data plane has retained the associated forwarding\n state across a restart. Those mechanisms do not fully support\n signaling state recovery on ingress nodes or recovery of all RSVP\n objects.\n\n The extensions defined in this document build on the RSVP Hello\n extensions defined in RFC 3209, and extensions for state recovery on\n nodal faults defined in RFC 3473. Using these extensions, the\n restarting node can recover all previously transmitted Path state,\n including the Explicit Route Ob 5063 attribute path tsp nested-reference unchanged"},{"id":"IETF RFC 5069","type":"specification","body":"IETF","designation":"RFC 5069","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5069.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5069.txt","https://www.rfc-editor.org/rfc/rfc5069.pdf"],"folder":"IETF/RFC-5069","files":{"txt":{"path":"standards/IETF/RFC-5069/RFC-5069.txt","sha256":"2a685939478a1fe80bc697e14a9ad02b245bf798b3545653e926dee3d3c7a21b"}},"tags":["nested-reference","unchanged"],"summary":"This document reviews the security threats associated with the\n marking of signalling messages to indicate that they are related to\n an emergency, and with the process of mapping locations to Universal\n Resource Identifiers (URIs) that point to Public Safety Answering\n Points (PSAPs). This mapping occurs as part of the process of\n routing emergency calls through the IP network.\n\n Based on the identified threats, this document establishes a set of\n security requirements for the mapping protocol and for the handling\n of emergency-marked calls.\n\nTaylor, et al. Informational [Page 1]\n\f\nRFC 5069 ECRIT Security Requirements January 2008","scope_keywords":["5069","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5012","folder":"IETF/RFC-5012","source":"IETF/RFC-5012/RFC-5012.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5069 This document reviews the security threats associated with the\n marking of signalling messages to indicate that they are related to\n an emergency, and with the process of mapping locations to Universal\n Resource Identifiers (URIs) that point to Public Safety Answering\n Points (PSAPs). This mapping occurs as part of the process of\n routing emergency calls through the IP network.\n\n Based on the identified threats, this document establishes a set of\n security requirements for the mapping protocol and for the handling\n of emergency-marked calls.\n\nTaylor, et al. Informational [Page 1]\n\f\nRFC 5069 ECRIT Security Requirements January 2008 5069 key path nested-reference unchanged"},{"id":"IETF RFC 5070","type":"specification","body":"IETF","designation":"RFC 5070","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5070.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5070.txt","https://www.rfc-editor.org/rfc/rfc5070.pdf"],"folder":"IETF/RFC-5070","files":{"txt":{"path":"standards/IETF/RFC-5070/RFC-5070.txt","sha256":"208a6ece68b68f207c364d7eef62ec63bcdbf862d87ef6f28c6b60ea3950760a"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) defines a\n data representation that provides a framework for sharing information\n commonly exchanged by Computer Security Incident Response Teams\n (CSIRTs) about computer security incidents. This document describes\n the information model for the IODEF and provides an associated data\n model specified with XML Schema.","scope_keywords":["5070","attribute","attributes","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6046","folder":"IETF/RFC-6046","source":"IETF/RFC-6046/RFC-6046.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6561","folder":"IETF/RFC-6561","source":"IETF/RFC-6561/RFC-6561.txt","version":null},{"body":"IETF","designation":"RFC 6685","folder":"IETF/RFC-6685","source":"IETF/RFC-6685/RFC-6685.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null}],"search_text":"IETF RFC 5070 The Incident Object Description Exchange Format (IODEF) defines a\n data representation that provides a framework for sharing information\n commonly exchanged by Computer Security Incident Response Teams\n (CSIRTs) about computer security incidents. This document describes\n the information model for the IODEF and provides an associated data\n model specified with XML Schema. 5070 attribute attributes presentation validation nested-reference unchanged"},{"id":"IETF RFC 5074","type":"specification","body":"IETF","designation":"RFC 5074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5074.txt","https://www.rfc-editor.org/rfc/rfc5074.pdf"],"folder":"IETF/RFC-5074","files":{"txt":{"path":"standards/IETF/RFC-5074/RFC-5074.txt","sha256":"87953a562842abcfd2b388bfc8f208976f0b330e85c4a780c7b64971a332b1a5"}},"tags":["nested-reference","unchanged"],"summary":"DNSSEC Lookaside Validation (DLV) is a mechanism for publishing DNS\n Security (DNSSEC) trust anchors outside of the DNS delegation chain.\n It allows validating resolvers to validate DNSSEC-signed data from\n zones whose ancestors either aren't signed or don't publish\n Delegation Signer (DS) records for their children.","scope_keywords":["5074","key","management","registered","signature","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null}],"search_text":"IETF RFC 5074 DNSSEC Lookaside Validation (DLV) is a mechanism for publishing DNS\n Security (DNSSEC) trust anchors outside of the DNS delegation chain.\n It allows validating resolvers to validate DNSSEC-signed data from\n zones whose ancestors either aren't signed or don't publish\n Delegation Signer (DS) records for their children. 5074 key management registered signature trust validation nested-reference unchanged"},{"id":"IETF RFC 5077","type":"specification","body":"IETF","designation":"RFC 5077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5077.txt","https://www.rfc-editor.org/rfc/rfc5077.pdf"],"folder":"IETF/RFC-5077","files":{"txt":{"path":"standards/IETF/RFC-5077/RFC-5077.txt","sha256":"e9f9cb247c4930a773dadf87b4cedf06cad9bbeec5e364d08fd5a83f678817ef"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that enables the Transport Layer\n Security (TLS) server to resume sessions and avoid keeping per-client\n session state. The TLS server encapsulates the session state into a\n ticket and forwards it to the client. The client can subsequently\n resume a session using the obtained ticket. This document obsoletes\n RFC 4507.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 5077 Stateless TLS Session Resumption January 2008","scope_keywords":["5077","certificate","key","management","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5169","folder":"IETF/RFC-5169","source":"IETF/RFC-5169/RFC-5169.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 5077 This document describes a mechanism that enables the Transport Layer\n Security (TLS) server to resume sessions and avoid keeping per-client\n session state. The TLS server encapsulates the session state into a\n ticket and forwards it to the client. The client can subsequently\n resume a session using the obtained ticket. This document obsoletes\n RFC 4507.\n\nSalowey, et al. Standards Track [Page 1]\n\f\nRFC 5077 Stateless TLS Session Resumption January 2008 5077 certificate key management tls nested-reference unchanged"},{"id":"IETF RFC 5081","type":"specification","body":"IETF","designation":"RFC 5081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5081.txt","https://www.rfc-editor.org/rfc/rfc5081.pdf"],"folder":"IETF/RFC-5081","files":{"txt":{"path":"standards/IETF/RFC-5081/RFC-5081.txt","sha256":"a664da9dd2cf8afc5067200f9a938e38eda57a0421c2e8658b1e3bbad94eb8e7"}},"tags":["nested-reference","unchanged"],"summary":"This memo proposes extensions to the Transport Layer Security (TLS)\n protocol to support the OpenPGP key format. The extensions discussed\n here include a certificate type negotiation mechanism, and the\n required modifications to the TLS Handshake Protocol.","scope_keywords":["5081","algorithm","authentication","certificate","certificates","encryption","key","keys","pki","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6091","folder":"IETF/RFC-6091","source":"IETF/RFC-6091/RFC-6091.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5081 This memo proposes extensions to the Transport Layer Security (TLS)\n protocol to support the OpenPGP key format. The extensions discussed\n here include a certificate type negotiation mechanism, and the\n required modifications to the TLS Handshake Protocol. 5081 algorithm authentication certificate certificates encryption key keys pki tls nested-reference unchanged"},{"id":"IETF RFC 5083","type":"specification","body":"IETF","designation":"RFC 5083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5083.txt","https://www.rfc-editor.org/rfc/rfc5083.pdf"],"folder":"IETF/RFC-5083","files":{"txt":{"path":"standards/IETF/RFC-5083/RFC-5083.txt","sha256":"e65f8a8991b57d117ba9b24068f2249e1e025cc2fcf6f4592b4baac2115f03bf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an additional content type for the\n Cryptographic Message Syntax (CMS). The authenticated-enveloped-data\n content type is intended for use with authenticated encryption modes.\n All of the various key management techniques that are supported in\n the CMS enveloped-data content type are also supported by the CMS\n authenticated-enveloped-data content type.\n\n1. Introduction\n\n This document describes an additional content type for the\n Cryptographic Message Syntax (CMS) [CMS]. The authenticated-\n enveloped-data content type is intended for use with authenticated\n encryption modes, where an arbitrary content is both authenticated\n and encrypted. Also, some associated data in the form of\n authenticated attributes can also be authenticated. All of the\n various key management techniques that are supported in the CMS\n enveloped-data content type are also supported by the CMS","scope_keywords":["5083","algorithm","algorithms","attribute","attributes","authentication","encryption","key","keys","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5084","folder":"IETF/RFC-5084","source":"IETF/RFC-5084/RFC-5084.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null}],"search_text":"IETF RFC 5083 This document describes an additional content type for the\n Cryptographic Message Syntax (CMS). The authenticated-enveloped-data\n content type is intended for use with authenticated encryption modes.\n All of the various key management techniques that are supported in\n the CMS enveloped-data content type are also supported by the CMS\n authenticated-enveloped-data content type.\n\n1. Introduction\n\n This document describes an additional content type for the\n Cryptographic Message Syntax (CMS) [CMS]. The authenticated-\n enveloped-data content type is intended for use with authenticated\n encryption modes, where an arbitrary content is both authenticated\n and encrypted. Also, some associated data in the form of\n authenticated attributes can also be authenticated. All of the\n various key management techniques that are supported in the CMS\n enveloped-data content type are also supported by the CMS 5083 algorithm algorithms attribute attributes authentication encryption key keys management path nested-reference unchanged"},{"id":"IETF RFC 5084","type":"specification","body":"IETF","designation":"RFC 5084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5084.txt","https://www.rfc-editor.org/rfc/rfc5084.pdf"],"folder":"IETF/RFC-5084","files":{"txt":{"path":"standards/IETF/RFC-5084/RFC-5084.txt","sha256":"463bcd40eb2c24db27a5e2356f94c0b1187bbc9897ec1a19429482a5c71108b8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the AES-CCM and the\n AES-GCM authenticated encryption algorithms with the Cryptographic\n Message Syntax (CMS) authenticated-enveloped-data content type.\n\n1. Introduction\n\n This document specifies the conventions for using Advanced Encryption\n Standard-Counter with Cipher Block Chaining-Message Authentication\n Code (AES-CCM) and AES-Galois/Counter Mode (GCM) authenticated\n encryption algorithms as the content-authenticated-encryption\n algorithm with the Cryptographic Message Syntax [CMS] authenticated-\n enveloped-data content type [AuthEnv].","scope_keywords":["5084","algorithm","algorithms","attribute","attributes","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5083","folder":"IETF/RFC-5083","source":"IETF/RFC-5083/RFC-5083.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 5084 This document specifies the conventions for using the AES-CCM and the\n AES-GCM authenticated encryption algorithms with the Cryptographic\n Message Syntax (CMS) authenticated-enveloped-data content type.\n\n1. Introduction\n\n This document specifies the conventions for using Advanced Encryption\n Standard-Counter with Cipher Block Chaining-Message Authentication\n Code (AES-CCM) and AES-Galois/Counter Mode (GCM) authenticated\n encryption algorithms as the content-authenticated-encryption\n algorithm with the Cryptographic Message Syntax [CMS] authenticated-\n enveloped-data content type [AuthEnv]. 5084 algorithm algorithms attribute attributes authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 5086","type":"specification","body":"IETF","designation":"RFC 5086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5086.txt","https://www.rfc-editor.org/rfc/rfc5086.pdf"],"folder":"IETF/RFC-5086","files":{"txt":{"path":"standards/IETF/RFC-5086/RFC-5086.txt","sha256":"3b35b02e53bbbf6c7a642fd279c7c8d969facced7e42ba72d438ca64823552f0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for encapsulating structured (NxDS0)\n Time Division Multiplexed (TDM) signals as pseudowires over packet-\n switching networks (PSNs). In this regard, it complements similar\n work for structure-agnostic emulation of TDM bit-streams (see RFC\n 4553).\n\nVainshtein, et al. Informational [Page 1]\n\f\nRFC 5086 TDM Circuit Emulation Service over PSN December 2007","scope_keywords":["5086","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 5086 This document describes a method for encapsulating structured (NxDS0)\n Time Division Multiplexed (TDM) signals as pseudowires over packet-\n switching networks (PSNs). In this regard, it complements similar\n work for structure-agnostic emulation of TDM bit-streams (see RFC\n 4553).\n\nVainshtein, et al. Informational [Page 1]\n\f\nRFC 5086 TDM Circuit Emulation Service over PSN December 2007 5086 key validation nested-reference unchanged"},{"id":"IETF RFC 5088","type":"specification","body":"IETF","designation":"RFC 5088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5088.txt","https://www.rfc-editor.org/rfc/rfc5088.pdf"],"folder":"IETF/RFC-5088","files":{"txt":{"path":"standards/IETF/RFC-5088/RFC-5088.txt","sha256":"e16571eca82fabf359bef4626d5a2497c12c71272fd743a0a9798028341b1206"}},"tags":["nested-reference","unchanged"],"summary":"There are various circumstances where it is highly desirable for a\n Path Computation Client (PCC) to be able to dynamically and\n automatically discover a set of Path Computation Elements (PCEs),\n along with information that can be used by the PCC for PCE selection.\n When the PCE is a Label Switching Router (LSR) participating in the\n Interior Gateway Protocol (IGP), or even a server participating\n passively in the IGP, a simple and efficient way to announce PCEs\n consists of using IGP flooding. For that purpose, this document\n defines extensions to the Open Shortest Path First (OSPF) routing\n protocol for the advertisement of PCE Discovery information within an\n OSPF area or within the entire OSPF routing domain.\n\nLe Roux, et al. Standards Track [Page 1]\n\f\nRFC 5088 OSPF Protocol Extensions for PCE Discovery January 2008","scope_keywords":["5088","algorithm","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 5088 There are various circumstances where it is highly desirable for a\n Path Computation Client (PCC) to be able to dynamically and\n automatically discover a set of Path Computation Elements (PCEs),\n along with information that can be used by the PCC for PCE selection.\n When the PCE is a Label Switching Router (LSR) participating in the\n Interior Gateway Protocol (IGP), or even a server participating\n passively in the IGP, a simple and efficient way to announce PCEs\n consists of using IGP flooding. For that purpose, this document\n defines extensions to the Open Shortest Path First (OSPF) routing\n protocol for the advertisement of PCE Discovery information within an\n OSPF area or within the entire OSPF routing domain.\n\nLe Roux, et al. Standards Track [Page 1]\n\f\nRFC 5088 OSPF Protocol Extensions for PCE Discovery January 2008 5088 algorithm path policy nested-reference unchanged"},{"id":"IETF RFC 5089","type":"specification","body":"IETF","designation":"RFC 5089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5089.txt","https://www.rfc-editor.org/rfc/rfc5089.pdf"],"folder":"IETF/RFC-5089","files":{"txt":{"path":"standards/IETF/RFC-5089/RFC-5089.txt","sha256":"abbf3d48e9ada78b218c167ed4f714de73d307a9836db47555c4d7a07bd69967"}},"tags":["nested-reference","unchanged"],"summary":"There are various circumstances where it is highly desirable for a\n Path Computation Client (PCC) to be able to dynamically and\n automatically discover a set of Path Computation Elements (PCEs),\n along with information that can be used by the PCC for PCE selection.\n When the PCE is a Label Switching Router (LSR) participating in the\n Interior Gateway Protocol (IGP), or even a server participating\n passively in the IGP, a simple and efficient way to announce PCEs\n consists of using IGP flooding. For that purpose, this document\n defines extensions to the Intermediate System to Intermediate System\n (IS-IS) routing protocol for the advertisement of PCE Discovery\n information within an IS-IS area or within the entire IS-IS routing\n domain.\n\nLe Roux, et al. Standards Track [Page 1]\n\f\nRFC 5089 IS-IS Protocol Extensions for PCE Discovery January 2008","scope_keywords":["5089","algorithm","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 5089 There are various circumstances where it is highly desirable for a\n Path Computation Client (PCC) to be able to dynamically and\n automatically discover a set of Path Computation Elements (PCEs),\n along with information that can be used by the PCC for PCE selection.\n When the PCE is a Label Switching Router (LSR) participating in the\n Interior Gateway Protocol (IGP), or even a server participating\n passively in the IGP, a simple and efficient way to announce PCEs\n consists of using IGP flooding. For that purpose, this document\n defines extensions to the Intermediate System to Intermediate System\n (IS-IS) routing protocol for the advertisement of PCE Discovery\n information within an IS-IS area or within the entire IS-IS routing\n domain.\n\nLe Roux, et al. Standards Track [Page 1]\n\f\nRFC 5089 IS-IS Protocol Extensions for PCE Discovery January 2008 5089 algorithm path policy nested-reference unchanged"},{"id":"IETF RFC 5091","type":"specification","body":"IETF","designation":"RFC 5091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5091.txt","https://www.rfc-editor.org/rfc/rfc5091.pdf"],"folder":"IETF/RFC-5091","files":{"txt":{"path":"standards/IETF/RFC-5091/RFC-5091.txt","sha256":"cb2a73f17b1425cbda6a5d209a0ec5b0f36bfdb40e00f8849924b9ac575dd819"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the algorithms that implement Boneh-Franklin\n (BF) and Boneh-Boyen (BB1) Identity-based Encryption. This document\n is in part based on IBCS #1 v2 of Voltage Security's Identity-based\n Cryptography Standards (IBCS) documents, from which some irrelevant\n sections have been removed to create the content of this document.\n\nBoyen & Martin Informational [Page 1]\n\f\nRFC 5091 IBCS #1 December 2007","scope_keywords":["5091","algorithm","algorithms","encryption","hash","hashing","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5091 This document describes the algorithms that implement Boneh-Franklin\n (BF) and Boneh-Boyen (BB1) Identity-based Encryption. This document\n is in part based on IBCS #1 v2 of Voltage Security's Identity-based\n Cryptography Standards (IBCS) documents, from which some irrelevant\n sections have been removed to create the content of this document.\n\nBoyen & Martin Informational [Page 1]\n\f\nRFC 5091 IBCS #1 December 2007 5091 algorithm algorithms encryption hash hashing key nested-reference unchanged"},{"id":"IETF RFC 5094","type":"specification","body":"IETF","designation":"RFC 5094","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5094.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5094.txt","https://www.rfc-editor.org/rfc/rfc5094.pdf"],"folder":"IETF/RFC-5094","files":{"txt":{"path":"standards/IETF/RFC-5094/RFC-5094.txt","sha256":"16b9b330883d21ca593c93210b1e264de44a49fd6160a00b3fc4381b82d43498"}},"tags":["nested-reference","unchanged"],"summary":"There is a need for vendor-specific extensions to Mobility Header\n messages so that Mobile IPv6 vendors are able to extend the protocol\n for research or deployment purposes. This document defines a new\n vendor-specific mobility option.","scope_keywords":["5094","authorization","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null}],"search_text":"IETF RFC 5094 There is a need for vendor-specific extensions to Mobility Header\n messages so that Mobile IPv6 vendors are able to extend the protocol\n for research or deployment purposes. This document defines a new\n vendor-specific mobility option. 5094 authorization key management trust nested-reference unchanged"},{"id":"IETF RFC 5095","type":"specification","body":"IETF","designation":"RFC 5095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5095.txt","https://www.rfc-editor.org/rfc/rfc5095.pdf"],"folder":"IETF/RFC-5095","files":{"txt":{"path":"standards/IETF/RFC-5095/RFC-5095.txt","sha256":"14b9fdb100625dadda2a3878c866cab9ff9b6aeae1c62b8778a6e77afcfd5e85"}},"tags":["nested-reference","unchanged"],"summary":"The functionality provided by IPv6's Type 0 Routing Header can be\n exploited in order to achieve traffic amplification over a remote\n path for the purposes of generating denial-of-service traffic. This\n document updates the IPv6 specification to deprecate the use of IPv6\n Type 0 Routing Headers, in light of this security concern.","scope_keywords":["5095","algorithm","key","path","policy","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5871","folder":"IETF/RFC-5871","source":"IETF/RFC-5871/RFC-5871.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6169","folder":"IETF/RFC-6169","source":"IETF/RFC-6169/RFC-6169.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6554","folder":"IETF/RFC-6554","source":"IETF/RFC-6554/RFC-6554.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8201","folder":"IETF/RFC-8201","source":"IETF/RFC-8201/RFC-8201.txt","version":null}],"search_text":"IETF RFC 5095 The functionality provided by IPv6's Type 0 Routing Header can be\n exploited in order to achieve traffic amplification over a remote\n path for the purposes of generating denial-of-service traffic. This\n document updates the IPv6 specification to deprecate the use of IPv6\n Type 0 Routing Headers, in light of this security concern. 5095 algorithm key path policy presentation risk nested-reference unchanged"},{"id":"IETF RFC 5097","type":"specification","body":"IETF","designation":"RFC 5097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5097.txt","https://www.rfc-editor.org/rfc/rfc5097.pdf"],"folder":"IETF/RFC-5097","files":{"txt":{"path":"standards/IETF/RFC-5097/RFC-5097.txt","sha256":"38309aa4a61368abfef9485fc97e12111e6cfa009eeb5677dcd2367652d118f6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Management Information Base (MIB) module\n for the Lightweight User Datagram Protocol (UDP-Lite). It defines a\n set of new MIB objects to characterise the behaviour and performance\n of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles\n UDP, but differs from the semantics of UDP by the addition of a\n single option. This adds the capability for variable-length data\n checksum coverage, which can benefit a class of applications that\n prefer delivery of (partially) corrupted datagram payload data in\n preference to discarding the datagram.","scope_keywords":["5097","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null}],"search_text":"IETF RFC 5097 This document specifies a Management Information Base (MIB) module\n for the Lightweight User Datagram Protocol (UDP-Lite). It defines a\n set of new MIB objects to characterise the behaviour and performance\n of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles\n UDP, but differs from the semantics of UDP by the addition of a\n single option. This adds the capability for variable-length data\n checksum coverage, which can benefit a class of applications that\n prefer delivery of (partially) corrupted datagram payload data in\n preference to discarding the datagram. 5097 delivery management nested-reference unchanged"},{"id":"IETF RFC 5103","type":"specification","body":"IETF","designation":"RFC 5103","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5103.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5103.txt","https://www.rfc-editor.org/rfc/rfc5103.pdf"],"folder":"IETF/RFC-5103","files":{"txt":{"path":"standards/IETF/RFC-5103/RFC-5103.txt","sha256":"8e8f7e0c7d2b6ad3cb0ea6ed20d08455e878ad28d99a98413accbf95b0d459c1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an efficient method for exporting\n bidirectional flow (Biflow) information using the IP Flow Information\n Export (IPFIX) protocol, representing each Biflow using a single Flow\n Record.\n\nTrammell & Boschi Standards Track [Page 1]\n\f\nRFC 5103 IPFIX Biflow Export January 2008","scope_keywords":["5103","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 5103 This document describes an efficient method for exporting\n bidirectional flow (Biflow) information using the IP Flow Information\n Export (IPFIX) protocol, representing each Biflow using a single Flow\n Record.\n\nTrammell & Boschi Standards Track [Page 1]\n\f\nRFC 5103 IPFIX Biflow Export January 2008 5103 key presentation nested-reference unchanged"},{"id":"IETF RFC 5106","type":"specification","body":"IETF","designation":"RFC 5106","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5106.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5106.txt","https://www.rfc-editor.org/rfc/rfc5106.pdf"],"folder":"IETF/RFC-5106","files":{"txt":{"path":"standards/IETF/RFC-5106/RFC-5106.txt","sha256":"8f9fe21745e72bf517ad57c0f53e375bc0a66bd5741da6f72bde575cfff97d05"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies EAP-IKEv2, an Extensible Authentication\n Protocol (EAP) method that is based on the Internet Key Exchange\n (IKEv2) protocol. EAP-IKEv2 provides mutual authentication and\n session key establishment between an EAP peer and an EAP server. It\n supports authentication techniques that are based on passwords,\n high-entropy shared keys, and public key certificates. EAP-IKEv2\n further provides support for cryptographic ciphersuite negotiation,\n hash function agility, identity confidentiality (in certain modes of\n operation), fragmentation, and an optional \"fast reconnect\" mode.\n\nTschofenig, et al. Experimental [Page 1]\n\f\nRFC 5106 EAP-IKEv2 Method February 2008","scope_keywords":["5106","authentication","certificate","certificates","credential","credentials","hash","identification","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 5106 This document specifies EAP-IKEv2, an Extensible Authentication\n Protocol (EAP) method that is based on the Internet Key Exchange\n (IKEv2) protocol. EAP-IKEv2 provides mutual authentication and\n session key establishment between an EAP peer and an EAP server. It\n supports authentication techniques that are based on passwords,\n high-entropy shared keys, and public key certificates. EAP-IKEv2\n further provides support for cryptographic ciphersuite negotiation,\n hash function agility, identity confidentiality (in certain modes of\n operation), fragmentation, and an optional \"fast reconnect\" mode.\n\nTschofenig, et al. Experimental [Page 1]\n\f\nRFC 5106 EAP-IKEv2 Method February 2008 5106 authentication certificate certificates credential credentials hash identification key keys management nested-reference unchanged"},{"id":"IETF RFC 5107","type":"specification","body":"IETF","designation":"RFC 5107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5107.txt","https://www.rfc-editor.org/rfc/rfc5107.pdf"],"folder":"IETF/RFC-5107","files":{"txt":{"path":"standards/IETF/RFC-5107/RFC-5107.txt","sha256":"ba7838b635a5106e061be38e39252ef86124c8f051383842d26d95a6bc9f2b29"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new suboption of the DHCP relay information\n option that allows the DHCP relay to specify a new value for the\n Server Identifier option, which is inserted by the DHCP Server. This\n allows the DHCP relay to act as the actual DHCP server such that\n RENEW DHCPREQUESTs will come to the relay instead of going to the\n server directly. This gives the relay the opportunity to include the\n Relay Agent option with appropriate suboptions even on DHCP RENEW\n messages.","scope_keywords":["5107","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6925","folder":"IETF/RFC-6925","source":"IETF/RFC-6925/RFC-6925.txt","version":null}],"search_text":"IETF RFC 5107 This memo defines a new suboption of the DHCP relay information\n option that allows the DHCP relay to specify a new value for the\n Server Identifier option, which is inserted by the DHCP Server. This\n allows the DHCP relay to act as the actual DHCP server such that\n RENEW DHCPREQUESTs will come to the relay instead of going to the\n server directly. This gives the relay the opportunity to include the\n Relay Agent option with appropriate suboptions even on DHCP RENEW\n messages. 5107 key nested-reference unchanged"},{"id":"IETF RFC 5109","type":"specification","body":"IETF","designation":"RFC 5109","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5109.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5109.txt","https://www.rfc-editor.org/rfc/rfc5109.pdf"],"folder":"IETF/RFC-5109","files":{"txt":{"path":"standards/IETF/RFC-5109/RFC-5109.txt","sha256":"84ce58f9a21d8887e2ac20120768760cc46bf1a88d3023fbf07a470a360340f6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a payload format for generic Forward Error\n Correction (FEC) for media data encapsulated in RTP. It is based on\n the exclusive-or (parity) operation. The payload format described in\n this document allows end systems to apply protection using various\n protection lengths and levels, in addition to using various\n protection group sizes to adapt to different media and channel\n characteristics. It enables complete recovery of the protected\n packets or partial recovery of the critical parts of the payload\n depending on the packet loss situation. This scheme is completely\n compatible with non-FEC-capable hosts, so the receivers in a\n multicast group that do not implement FEC can still work by simply\n ignoring the protection data. This specification obsoletes RFC 2733\n and RFC 3009. The FEC specified in this document is not backward\n compatible with RFC 2733 and RFC 3009.","scope_keywords":["5109","algorithm","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5109 This document specifies a payload format for generic Forward Error\n Correction (FEC) for media data encapsulated in RTP. It is based on\n the exclusive-or (parity) operation. The payload format described in\n this document allows end systems to apply protection using various\n protection lengths and levels, in addition to using various\n protection group sizes to adapt to different media and channel\n characteristics. It enables complete recovery of the protected\n packets or partial recovery of the critical parts of the payload\n depending on the packet loss situation. This scheme is completely\n compatible with non-FEC-capable hosts, so the receivers in a\n multicast group that do not implement FEC can still work by simply\n ignoring the protection data. This specification obsoletes RFC 2733\n and RFC 3009. The FEC specified in this document is not backward\n compatible with RFC 2733 and RFC 3009. 5109 algorithm identification nested-reference unchanged"},{"id":"IETF RFC 5114","type":"specification","body":"IETF","designation":"RFC 5114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5114.txt","https://www.rfc-editor.org/rfc/rfc5114.pdf"],"folder":"IETF/RFC-5114","files":{"txt":{"path":"standards/IETF/RFC-5114/RFC-5114.txt","sha256":"7fde6217be0cf9c036e755fda502ef8345dbd7c274e8fa87ca87c69b8e4ce25b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes eight Diffie-Hellman groups that can be used\n in conjunction with IETF protocols to provide security for Internet\n communications. The groups allow implementers to use the same groups\n with a variety of security protocols, e.g., SMIME, Secure SHell\n (SSH), Transport Layer Security (TLS), and Internet Key Exchange\n (IKE).\n\n All of these groups comply in form and structure with relevant\n standards from ISO, ANSI, NIST, and the IEEE. These groups are\n compatible with all IETF standards that make use of Diffie-Hellman or\n Elliptic Curve Diffie-Hellman cryptography.\n\n These groups and the associated test data are defined by NIST on\n their web site [EX80056A], but have not yet (as of this writing) been\n published in a formal NIST document. Publication of these groups and\n associated test data, as well as describing how to use Diffie-Hellman\n and Elliptic Curve Diffie-He","scope_keywords":["5114","certificate","certificates","key","keys","pki","registered","tls","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null}],"search_text":"IETF RFC 5114 This document describes eight Diffie-Hellman groups that can be used\n in conjunction with IETF protocols to provide security for Internet\n communications. The groups allow implementers to use the same groups\n with a variety of security protocols, e.g., SMIME, Secure SHell\n (SSH), Transport Layer Security (TLS), and Internet Key Exchange\n (IKE).\n\n All of these groups comply in form and structure with relevant\n standards from ISO, ANSI, NIST, and the IEEE. These groups are\n compatible with all IETF standards that make use of Diffie-Hellman or\n Elliptic Curve Diffie-Hellman cryptography.\n\n These groups and the associated test data are defined by NIST on\n their web site [EX80056A], but have not yet (as of this writing) been\n published in a formal NIST document. Publication of these groups and\n associated test data, as well as describing how to use Diffie-Hellman\n and Elliptic Curve Diffie-He 5114 certificate certificates key keys pki registered tls validation nested-reference unchanged"},{"id":"IETF RFC 5117","type":"specification","body":"IETF","designation":"RFC 5117","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5117.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5117.txt","https://www.rfc-editor.org/rfc/rfc5117.pdf"],"folder":"IETF/RFC-5117","files":{"txt":{"path":"standards/IETF/RFC-5117/RFC-5117.txt","sha256":"a7b487641228b9e3c49ca8df943e498db8a48dca8dbea9f525b37577b49cfe92"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses multi-endpoint topologies used in Real-time\n Transport Protocol (RTP)-based environments. In particular,\n centralized topologies commonly employed in the video conferencing\n industry are mapped to the RTP terminology.\n\nWesterlund & Wenger Informational [Page 1]\n\f\nRFC 5117 RTP Topologies January 2008","scope_keywords":["5117","key","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null}],"search_text":"IETF RFC 5117 This document discusses multi-endpoint topologies used in Real-time\n Transport Protocol (RTP)-based environments. In particular,\n centralized topologies commonly employed in the video conferencing\n industry are mapped to the RTP terminology.\n\nWesterlund & Wenger Informational [Page 1]\n\f\nRFC 5117 RTP Topologies January 2008 5117 key path profile nested-reference unchanged"},{"id":"IETF RFC 5124","type":"specification","body":"IETF","designation":"RFC 5124","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5124.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5124.txt","https://www.rfc-editor.org/rfc/rfc5124.pdf"],"folder":"IETF/RFC-5124","files":{"txt":{"path":"standards/IETF/RFC-5124/RFC-5124.txt","sha256":"9d3dda639b7514b408b763e30c3a1fc86ecb97bc3deb143c254814bb01acf9f3"}},"tags":["nested-reference","unchanged"],"summary":"An RTP profile (SAVP) for secure real-time communications and another\n profile (AVPF) to provide timely feedback from the receivers to a\n sender are defined in RFC 3711 and RFC 4585, respectively. This memo\n specifies the combination of both profiles to enable secure RTP\n communications with feedback.\n\nOtt & Carrara Standards Track [Page 1]\n\f\nRFC 5124 February 2008","scope_keywords":["5124","algorithm","algorithms","attribute","encryption","key","profile","profiles","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5506","folder":"IETF/RFC-5506","source":"IETF/RFC-5506/RFC-5506.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5124 An RTP profile (SAVP) for secure real-time communications and another\n profile (AVPF) to provide timely feedback from the receivers to a\n sender are defined in RFC 3711 and RFC 4585, respectively. This memo\n specifies the combination of both profiles to enable secure RTP\n communications with feedback.\n\nOtt & Carrara Standards Track [Page 1]\n\f\nRFC 5124 February 2008 5124 algorithm algorithms attribute encryption key profile profiles tsp nested-reference unchanged"},{"id":"IETF RFC 5129","type":"specification","body":"IETF","designation":"RFC 5129","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5129.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5129.txt","https://www.rfc-editor.org/rfc/rfc5129.pdf"],"folder":"IETF/RFC-5129","files":{"txt":{"path":"standards/IETF/RFC-5129/RFC-5129.txt","sha256":"e0cadb1301cb27ba60f544cd36bb88148469acbb4183011624b626326c66cf0e"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3270 defines how to support the Diffserv architecture in MPLS\n networks, including how to encode Diffserv Code Points (DSCPs) in an\n MPLS header. DSCPs may be encoded in the EXP field, while other uses\n of that field are not precluded. RFC 3270 makes no statement about\n how Explicit Congestion Notification (ECN) marking might be encoded\n in the MPLS header. This document defines how an operator might\n define some of the EXP codepoints for explicit congestion\n notification, without precluding other uses.\n\nDavie, et al. Standards Track [Page 1]\n\f\nRFC 5129 ECN for MPLS January 2008","scope_keywords":["5129"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 5129 RFC 3270 defines how to support the Diffserv architecture in MPLS\n networks, including how to encode Diffserv Code Points (DSCPs) in an\n MPLS header. DSCPs may be encoded in the EXP field, while other uses\n of that field are not precluded. RFC 3270 makes no statement about\n how Explicit Congestion Notification (ECN) marking might be encoded\n in the MPLS header. This document defines how an operator might\n define some of the EXP codepoints for explicit congestion\n notification, without precluding other uses.\n\nDavie, et al. Standards Track [Page 1]\n\f\nRFC 5129 ECN for MPLS January 2008 5129 nested-reference unchanged"},{"id":"IETF RFC 5137","type":"specification","body":"IETF","designation":"RFC 5137","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5137.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5137.txt","https://www.rfc-editor.org/rfc/rfc5137.pdf"],"folder":"IETF/RFC-5137","files":{"txt":{"path":"standards/IETF/RFC-5137/RFC-5137.txt","sha256":"f981807d18462e1eceb513bf39738a27fb2367f6db67f46a87c22d6a85f058a4"}},"tags":["nested-reference","unchanged"],"summary":"There are a number of circumstances in which an escape mechanism is\n needed in conjunction with a protocol to encode characters that\n cannot be represented or transmitted directly. With ASCII coding,\n the traditional escape has been either the decimal or hexadecimal\n numeric value of the character, written in a variety of different\n ways. The move to Unicode, where characters occupy two or more\n octets and may be coded in several different forms, has further\n complicated the question of escapes. This document discusses some\n options now in use and discusses considerations for selecting one for\n use in new IETF protocols, and protocols that are now being\n internationalized.\n\nKlensin Best Current Practice [Page 1]\n\f\nRFC 5137 Unicode Escapes February 2008","scope_keywords":["5137","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5284","folder":"IETF/RFC-5284","source":"IETF/RFC-5284/RFC-5284.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null}],"search_text":"IETF RFC 5137 There are a number of circumstances in which an escape mechanism is\n needed in conjunction with a protocol to encode characters that\n cannot be represented or transmitted directly. With ASCII coding,\n the traditional escape has been either the decimal or hexadecimal\n numeric value of the character, written in a variety of different\n ways. The move to Unicode, where characters occupy two or more\n octets and may be coded in several different forms, has further\n complicated the question of escapes. This document discusses some\n options now in use and discusses considerations for selecting one for\n use in new IETF protocols, and protocols that are now being\n internationalized.\n\nKlensin Best Current Practice [Page 1]\n\f\nRFC 5137 Unicode Escapes February 2008 5137 key presentation nested-reference unchanged"},{"id":"IETF RFC 5139","type":"specification","body":"IETF","designation":"RFC 5139","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5139.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5139.txt","https://www.rfc-editor.org/rfc/rfc5139.pdf"],"folder":"IETF/RFC-5139","files":{"txt":{"path":"standards/IETF/RFC-5139/RFC-5139.txt","sha256":"3254ae894312bdbd1bf1394c69b139445e4da3b9900d69f332a605b28b39f12b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an XML format for the representation of civic\n location. This format is designed for use with Presence Information\n Data Format Location Object (PIDF-LO) documents and replaces the\n civic location format in RFC 4119. The format is based on the civic\n address definition in PIDF-LO, but adds several new elements based on\n the civic types defined for Dynamic Host Configuration Protocol\n (DHCP), and adds a hierarchy to address complex road identity\n schemes. The format also includes support for the xml:lang language\n tag and restricts the types of elements where appropriate.\n\nThomson & Winterbottom Standards Track [Page 1]\n\f\nRFC 5139 Revised Civic LO February 2008","scope_keywords":["5139","identification","key","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5491","folder":"IETF/RFC-5491","source":"IETF/RFC-5491/RFC-5491.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5139 This document defines an XML format for the representation of civic\n location. This format is designed for use with Presence Information\n Data Format Location Object (PIDF-LO) documents and replaces the\n civic location format in RFC 4119. The format is based on the civic\n address definition in PIDF-LO, but adds several new elements based on\n the civic types defined for Dynamic Host Configuration Protocol\n (DHCP), and adds a hierarchy to address complex road identity\n schemes. The format also includes support for the xml:lang language\n tag and restricts the types of elements where appropriate.\n\nThomson & Winterbottom Standards Track [Page 1]\n\f\nRFC 5139 Revised Civic LO February 2008 5139 identification key pid presentation nested-reference unchanged"},{"id":"IETF RFC 5142","type":"specification","body":"IETF","designation":"RFC 5142","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5142.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5142.txt","https://www.rfc-editor.org/rfc/rfc5142.pdf"],"folder":"IETF/RFC-5142","files":{"txt":{"path":"standards/IETF/RFC-5142/RFC-5142.txt","sha256":"61abee23df60f0ae6f5b510f57c9ac9e803c431e5cccda675283b7f5e5132d6e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new Mobility Header message type that can\n be used between a home agent and mobile node to signal to a mobile\n node that it should acquire a new home agent.\n\nHaley, et al. Standards Track [Page 1]\n\f\nRFC 5142 Home Agent Switch Message January 2008","scope_keywords":["5142","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5685","folder":"IETF/RFC-5685","source":"IETF/RFC-5685/RFC-5685.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null}],"search_text":"IETF RFC 5142 This document specifies a new Mobility Header message type that can\n be used between a home agent and mobile node to signal to a mobile\n node that it should acquire a new home agent.\n\nHaley, et al. Standards Track [Page 1]\n\f\nRFC 5142 Home Agent Switch Message January 2008 5142 key nested-reference unchanged"},{"id":"IETF RFC 5143","type":"specification","body":"IETF","designation":"RFC 5143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5143.txt","https://www.rfc-editor.org/rfc/rfc5143.pdf"],"folder":"IETF/RFC-5143","files":{"txt":{"path":"standards/IETF/RFC-5143/RFC-5143.txt","sha256":"ab3a9715fa2122cbef367634810f7a86b6a92578391fdcbf99664ca7dd3f442e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a historical method for encapsulating\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Path signals for transport across packet-switched networks (PSNs).\n The PSNs explicitly supported by this document include MPLS and IP.\n Note that RFC 4842 describes the standards-track protocol for this\n functionality, and new implementations must use RFC 4842 rather than\n this document except when interoperability with older implementations\n is desired.\n\nMalis, et al. Historic [Page 1]\n\f\nRFC 5143 SONET/SDH Circuit Emulation over MPLS February 2008","scope_keywords":["5143","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null}],"search_text":"IETF RFC 5143 This document describes a historical method for encapsulating\n Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH)\n Path signals for transport across packet-switched networks (PSNs).\n The PSNs explicitly supported by this document include MPLS and IP.\n Note that RFC 4842 describes the standards-track protocol for this\n functionality, and new implementations must use RFC 4842 rather than\n this document except when interoperability with older implementations\n is desired.\n\nMalis, et al. Historic [Page 1]\n\f\nRFC 5143 SONET/SDH Circuit Emulation over MPLS February 2008 5143 key path nested-reference unchanged"},{"id":"IETF RFC 5149","type":"specification","body":"IETF","designation":"RFC 5149","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5149.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5149.txt","https://www.rfc-editor.org/rfc/rfc5149.pdf"],"folder":"IETF/RFC-5149","files":{"txt":{"path":"standards/IETF/RFC-5149/RFC-5149.txt","sha256":"8fc44c1f2768dcd84192307e05f1094dc399323a79118c7fe15231a62b1cb57c"}},"tags":["nested-reference","unchanged"],"summary":"In some Mobile IPv6 deployments, identifying the mobile node or the\n mobility service subscriber is not enough to distinguish between\n multiple services possibly provisioned to the said mobile node and\n its mobility service subscription. A capability to specify different\n services in addition to the mobile node identity can be leveraged to\n provide flexibility for mobility service providers on provisioning\n multiple services to one mobility service subscription. This\n document describes a Service Selection Mobility Option for both\n conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to\n assist home agents to make a specific service selection for the\n mobility service subscription during the binding registration\n procedure.","scope_keywords":["5149","authentication","authorization","credential","credentials","key","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null}],"search_text":"IETF RFC 5149 In some Mobile IPv6 deployments, identifying the mobile node or the\n mobility service subscriber is not enough to distinguish between\n multiple services possibly provisioned to the said mobile node and\n its mobility service subscription. A capability to specify different\n services in addition to the mobile node identity can be leveraged to\n provide flexibility for mobility service providers on provisioning\n multiple services to one mobility service subscription. This\n document describes a Service Selection Mobility Option for both\n conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to\n assist home agents to make a specific service selection for the\n mobility service subscription during the binding registration\n procedure. 5149 authentication authorization credential credentials key policies policy nested-reference unchanged"},{"id":"IETF RFC 5150","type":"specification","body":"IETF","designation":"RFC 5150","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5150.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5150.txt","https://www.rfc-editor.org/rfc/rfc5150.pdf"],"folder":"IETF/RFC-5150","files":{"txt":{"path":"standards/IETF/RFC-5150/RFC-5150.txt","sha256":"073c759a976c2fbbd5bbc2214c5410ecbfe861fb851b54466a15ab1509d5de7c"}},"tags":["nested-reference","unchanged"],"summary":"In certain scenarios, there may be a need to combine several\n Generalized Multiprotocol Label Switching (GMPLS) Label Switched\n Paths (LSPs) such that a single end-to-end (e2e) LSP is realized and\n all traffic from one constituent LSP is switched onto the next LSP.\n We will refer to this as \"LSP stitching\", the key requirement being\n that a constituent LSP not be allocated to more than one e2e LSP.\n The constituent LSPs will be referred to as \"LSP segments\" (S-LSPs).\n\n This document describes extensions to the existing GMPLS signaling\n protocol (Resource Reservation Protocol-Traffic Engineering (RSVP-\n TE)) to establish e2e LSPs created from S-LSPs, and describes how the\n LSPs can be managed using the GMPLS signaling and routing protocols.\n\n It may be possible to configure a GMPLS node to switch the traffic\n from an LSP for which it is the egress, to another LSP for which it\n is the ingr","scope_keywords":["5150","attribute","attributes","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null}],"search_text":"IETF RFC 5150 In certain scenarios, there may be a need to combine several\n Generalized Multiprotocol Label Switching (GMPLS) Label Switched\n Paths (LSPs) such that a single end-to-end (e2e) LSP is realized and\n all traffic from one constituent LSP is switched onto the next LSP.\n We will refer to this as \"LSP stitching\", the key requirement being\n that a constituent LSP not be allocated to more than one e2e LSP.\n The constituent LSPs will be referred to as \"LSP segments\" (S-LSPs).\n\n This document describes extensions to the existing GMPLS signaling\n protocol (Resource Reservation Protocol-Traffic Engineering (RSVP-\n TE)) to establish e2e LSPs created from S-LSPs, and describes how the\n LSPs can be managed using the GMPLS signaling and routing protocols.\n\n It may be possible to configure a GMPLS node to switch the traffic\n from an LSP for which it is the egress, to another LSP for which it\n is the ingr 5150 attribute attributes key management path nested-reference unchanged"},{"id":"IETF RFC 5151","type":"specification","body":"IETF","designation":"RFC 5151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5151.txt","https://www.rfc-editor.org/rfc/rfc5151.pdf"],"folder":"IETF/RFC-5151","files":{"txt":{"path":"standards/IETF/RFC-5151/RFC-5151.txt","sha256":"341f9600eb3873f4f04b02240ad417a0563087dd5c54ddea013dfe5f898977d3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes procedures and protocol extensions for the\n use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE)\n signaling in Multiprotocol Label Switching-Traffic Engineering\n (MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and\n non-packet networks to support the establishment and maintenance of\n Label Switched Paths that cross domain boundaries.\n\n For the purpose of this document, a domain is considered to be any\n collection of network elements within a common realm of address space\n or path computation responsibility. Examples of such domains include\n Autonomous Systems, Interior Gateway Protocol (IGP) routing areas,\n and GMPLS overlay networks.\n\nFarrel, et al. Standards Track [Page 1]\n\f\nRFC 5151 Inter-Domain MPLS & GMPLS RSVP-TE Extensions February 2008","scope_keywords":["5151","attribute","attributes","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5283","folder":"IETF/RFC-5283","source":"IETF/RFC-5283/RFC-5283.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 5151 This document describes procedures and protocol extensions for the\n use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE)\n signaling in Multiprotocol Label Switching-Traffic Engineering\n (MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and\n non-packet networks to support the establishment and maintenance of\n Label Switched Paths that cross domain boundaries.\n\n For the purpose of this document, a domain is considered to be any\n collection of network elements within a common realm of address space\n or path computation responsibility. Examples of such domains include\n Autonomous Systems, Interior Gateway Protocol (IGP) routing areas,\n and GMPLS overlay networks.\n\nFarrel, et al. Standards Track [Page 1]\n\f\nRFC 5151 Inter-Domain MPLS & GMPLS RSVP-TE Extensions February 2008 5151 attribute attributes key path nested-reference unchanged"},{"id":"IETF RFC 5152","type":"specification","body":"IETF","designation":"RFC 5152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5152.txt","https://www.rfc-editor.org/rfc/rfc5152.pdf"],"folder":"IETF/RFC-5152","files":{"txt":{"path":"standards/IETF/RFC-5152/RFC-5152.txt","sha256":"634f8160e12e2697e1d2ee5663ea960651e43b85dcd79e31c91f88bd845e1269"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a per-domain path computation technique for\n establishing inter-domain Traffic Engineering (TE) Multiprotocol\n Label Switching (MPLS) and Generalized MPLS (GMPLS) Label Switched\n Paths (LSPs). In this document, a domain refers to a collection of\n network elements within a common sphere of address management or path\n computational responsibility such as Interior Gateway Protocol (IGP)\n areas and Autonomous Systems.\n\n Per-domain computation applies where the full path of an inter-domain\n TE LSP cannot be or is not determined at the ingress node of the TE\n LSP, and is not signaled across domain boundaries. This is most\n likely to arise owing to TE visibility limitations. The signaling\n message indicates the destination and nodes up to the next domain\n boundary. It may also indicate further domain boundaries or domain\n identifiers. The path through each domain, possib","scope_keywords":["5152","attribute","attributes","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5152 This document specifies a per-domain path computation technique for\n establishing inter-domain Traffic Engineering (TE) Multiprotocol\n Label Switching (MPLS) and Generalized MPLS (GMPLS) Label Switched\n Paths (LSPs). In this document, a domain refers to a collection of\n network elements within a common sphere of address management or path\n computational responsibility such as Interior Gateway Protocol (IGP)\n areas and Autonomous Systems.\n\n Per-domain computation applies where the full path of an inter-domain\n TE LSP cannot be or is not determined at the ingress node of the TE\n LSP, and is not signaled across domain boundaries. This is most\n likely to arise owing to TE visibility limitations. The signaling\n message indicates the destination and nodes up to the next domain\n boundary. It may also indicate further domain boundaries or domain\n identifiers. The path through each domain, possib 5152 attribute attributes key management path nested-reference unchanged"},{"id":"IETF RFC 5159","type":"specification","body":"IETF","designation":"RFC 5159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5159.txt","https://www.rfc-editor.org/rfc/rfc5159.pdf"],"folder":"IETF/RFC-5159","files":{"txt":{"path":"standards/IETF/RFC-5159/RFC-5159.txt","sha256":"8ed2c82adb92f86bbf39566f3a1a34bd62a6a3eb5f3b75dc5e5485f49532ff84"}},"tags":["nested-reference","unchanged"],"summary":"This document provides descriptions of Session Description Protocol\n (SDP) attributes used by the Open Mobile Alliance's Broadcast Service\n and Content Protection specification.","scope_keywords":["5159","algorithm","attribute","attributes","authentication","key","keys","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5159 This document provides descriptions of Session Description Protocol\n (SDP) attributes used by the Open Mobile Alliance's Broadcast Service\n and Content Protection specification. 5159 algorithm attribute attributes authentication key keys management registered nested-reference unchanged"},{"id":"IETF RFC 5161","type":"specification","body":"IETF","designation":"RFC 5161","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5161.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5161.txt","https://www.rfc-editor.org/rfc/rfc5161.pdf"],"folder":"IETF/RFC-5161","files":{"txt":{"path":"standards/IETF/RFC-5161/RFC-5161.txt","sha256":"a8a34b3442e20ac21336e32a418828c21e24c253ca5d1706d9a0019e8f1301e3"}},"tags":["nested-reference","unchanged"],"summary":"Most IMAP extensions are used by the client when it wants to and the\n server supports it. However, a few extensions require the server to\n know whether a client supports that extension. The ENABLE extension\n allows an IMAP client to say which extensions it supports.\n\n1. Overview\n\n Several IMAP extensions allow the server to return unsolicited\n responses specific to these extensions in certain circumstances.\n However, servers cannot send those unsolicited responses until they\n know that the clients support such extensions and thus won't choke on\n the extension response data.\n\n Up until now, extensions have typically stated that a server cannot\n send the unsolicited responses until after the client has used a\n command with the extension data (i.e., at that point the server knows\n the client is aware of the extension). CONDSTORE ([RFC4551]),\n ANNOTATE ([ANNOTATE]), and some extensions under","scope_keywords":["5161","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5161 Most IMAP extensions are used by the client when it wants to and the\n server supports it. However, a few extensions require the server to\n know whether a client supports that extension. The ENABLE extension\n allows an IMAP client to say which extensions it supports.\n\n1. Overview\n\n Several IMAP extensions allow the server to return unsolicited\n responses specific to these extensions in certain circumstances.\n However, servers cannot send those unsolicited responses until they\n know that the clients support such extensions and thus won't choke on\n the extension response data.\n\n Up until now, extensions have typically stated that a server cannot\n send the unsolicited responses until after the client has used a\n command with the extension data (i.e., at that point the server knows\n the client is aware of the extension). CONDSTORE ([RFC4551]),\n ANNOTATE ([ANNOTATE]), and some extensions under 5161 crl key nested-reference unchanged"},{"id":"IETF RFC 5162","type":"specification","body":"IETF","designation":"RFC 5162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5162.txt","https://www.rfc-editor.org/rfc/rfc5162.pdf"],"folder":"IETF/RFC-5162","files":{"txt":{"path":"standards/IETF/RFC-5162/RFC-5162.txt","sha256":"7f75f3b573f87feb44f5c6944ce04b7c788234a2db2aa7da97026397c19188ad"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an IMAP4 extension, which gives an IMAP client\n the ability to quickly resynchronize any previously opened mailbox as\n part of the SELECT command, without the need for server-side state or\n additional client round-trips. This extension also introduces a new\n response that allows for a more compact representation of a list of\n expunged messages (and always includes the Unique Identifiers (UIDs)\n expunged).\n\nMelnikov, et al. Standards Track [Page 1]\n\f\nRFC 5162 IMAP Quick Mailbox Resync March 2008","scope_keywords":["5162","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null}],"search_text":"IETF RFC 5162 This document defines an IMAP4 extension, which gives an IMAP client\n the ability to quickly resynchronize any previously opened mailbox as\n part of the SELECT command, without the need for server-side state or\n additional client round-trips. This extension also introduces a new\n response that allows for a more compact representation of a list of\n expunged messages (and always includes the Unique Identifiers (UIDs)\n expunged).\n\nMelnikov, et al. Standards Track [Page 1]\n\f\nRFC 5162 IMAP Quick Mailbox Resync March 2008 5162 key presentation nested-reference unchanged"},{"id":"IETF RFC 5175","type":"specification","body":"IETF","designation":"RFC 5175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5175.txt","https://www.rfc-editor.org/rfc/rfc5175.pdf"],"folder":"IETF/RFC-5175","files":{"txt":{"path":"standards/IETF/RFC-5175/RFC-5175.txt","sha256":"5d4d9fe9fa4b25e44f2c010f39b83a56fa06ae06a170f3a94e3856deb66bbb6e"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 Neighbor Discovery's Router Advertisement message contains\n an 8-bit field reserved for single-bit flags. Several protocols have\n reserved flags in this field and others are preparing to reserve a\n sufficient number of flags to exhaust the field. This document\n defines an option to the Router Advertisement message that expands\n the number of flag bits available.","scope_keywords":["5175","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 5175 The IPv6 Neighbor Discovery's Router Advertisement message contains\n an 8-bit field reserved for single-bit flags. Several protocols have\n reserved flags in this field and others are preparing to reserve a\n sufficient number of flags to exhaust the field. This document\n defines an option to the Router Advertisement message that expands\n the number of flag bits available. 5175 http key nested-reference unchanged"},{"id":"IETF RFC 5182","type":"specification","body":"IETF","designation":"RFC 5182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5182.txt","https://www.rfc-editor.org/rfc/rfc5182.pdf"],"folder":"IETF/RFC-5182","files":{"txt":{"path":"standards/IETF/RFC-5182/RFC-5182.txt","sha256":"449a1a747d75a37cbcf01e099e32357ed24d13bdbeb91f1df7ca667717afff6a"}},"tags":["nested-reference","unchanged"],"summary":"Many IMAP clients use the result of a SEARCH command as the input to\n perform another operation, for example, fetching the found messages,\n deleting them, or copying them to another mailbox.\n\n This can be achieved using standard IMAP operations described in RFC\n 3501; however, this would be suboptimal. The server will send the\n list of found messages to the client; after that, the client will\n have to parse the list, reformat it, and send it back to the server.\n The client can't pipeline the SEARCH command with the subsequent\n command, and, as a result, the server might not be able to perform\n some optimizations.\n\n This document proposes an IMAP extension that allows a client to tell\n a server to use the result of a SEARCH (or Unique Identifier (UID)\n SEARCH) command as an input to any subsequent command.\n\n1. Introduction\n\n Many IMAP clients use the result of a SEARCH command as the inpu","scope_keywords":["5182","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5182 Many IMAP clients use the result of a SEARCH command as the input to\n perform another operation, for example, fetching the found messages,\n deleting them, or copying them to another mailbox.\n\n This can be achieved using standard IMAP operations described in RFC\n 3501; however, this would be suboptimal. The server will send the\n list of found messages to the client; after that, the client will\n have to parse the list, reformat it, and send it back to the server.\n The client can't pipeline the SEARCH command with the subsequent\n command, and, as a result, the server might not be able to perform\n some optimizations.\n\n This document proposes an IMAP extension that allows a client to tell\n a server to use the result of a SEARCH (or Unique Identifier (UID)\n SEARCH) command as an input to any subsequent command.\n\n1. Introduction\n\n Many IMAP clients use the result of a SEARCH command as the inpu 5182 key nested-reference unchanged"},{"id":"IETF RFC 5183","type":"specification","body":"IETF","designation":"RFC 5183","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5183.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5183.txt","https://www.rfc-editor.org/rfc/rfc5183.pdf"],"folder":"IETF/RFC-5183","files":{"txt":{"path":"standards/IETF/RFC-5183/RFC-5183.txt","sha256":"1d5db1b1e16b22a23d194b25252866a7dc62a7c7a8381119ee74195fb249935b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"environment\" extension to the Sieve\n email filtering language. The \"environment\" extension gives a Sieve\n script access to information about the Sieve interpreter itself,\n where it is running, and about any transport connection currently\n involved in transferring the message.\n\n1. Introduction\n\n Sieve [RFC5228] is a language for filtering email messages at or\n around the time of final delivery. It is designed to be\n implementable on either a mail client or mail server. It is suitable\n for running on a mail server where users may not be allowed to\n execute arbitrary programs, such as on black box Internet Message\n Access Protocol [RFC3501] servers, as it has no user-controlled loops\n or the ability to run external programs.\n\n Although Sieve is intended to be independent of access protocol, mail\n architecture, and operating system, in some cases it is useful to\n","scope_keywords":["5183","delivery","key","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5183 This document describes the \"environment\" extension to the Sieve\n email filtering language. The \"environment\" extension gives a Sieve\n script access to information about the Sieve interpreter itself,\n where it is running, and about any transport connection currently\n involved in transferring the message.\n\n1. Introduction\n\n Sieve [RFC5228] is a language for filtering email messages at or\n around the time of final delivery. It is designed to be\n implementable on either a mail client or mail server. It is suitable\n for running on a mail server where users may not be allowed to\n execute arbitrary programs, such as on black box Internet Message\n Access Protocol [RFC3501] servers, as it has no user-controlled loops\n or the ability to run external programs.\n\n Although Sieve is intended to be independent of access protocol, mail\n architecture, and operating system, in some cases it is useful to\n 5183 delivery key qualified registered nested-reference unchanged"},{"id":"IETF RFC 5188","type":"specification","body":"IETF","designation":"RFC 5188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5188.txt","https://www.rfc-editor.org/rfc/rfc5188.pdf"],"folder":"IETF/RFC-5188","files":{"txt":{"path":"standards/IETF/RFC-5188/RFC-5188.txt","sha256":"02b874538e479019bbae77c31d89a47919a0ca7dce3823f81cb2f9507926018f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Real-time Transport Protocol (RTP) payload\n formats to be used for the Enhanced Variable Rate Wideband Codec\n (EVRC-WB) and updates the media type registrations for EVRC-B codec.\n Several media type registrations are included for EVRC-WB RTP payload\n formats. In addition, a file format is specified for transport of\n EVRC-WB speech data in storage mode applications such as email.\n\nDesineni & Xie Standards Track [Page 1]\n\f\nRFC 5188 EVRC-WB RTP Payload Format February 2008","scope_keywords":["5188","attribute","attributes","key","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"IETF RFC 5188 This document specifies Real-time Transport Protocol (RTP) payload\n formats to be used for the Enhanced Variable Rate Wideband Codec\n (EVRC-WB) and updates the media type registrations for EVRC-B codec.\n Several media type registrations are included for EVRC-WB RTP payload\n formats. In addition, a file format is specified for transport of\n EVRC-WB speech data in storage mode applications such as email.\n\nDesineni & Xie Standards Track [Page 1]\n\f\nRFC 5188 EVRC-WB RTP Payload Format February 2008 5188 attribute attributes key timestamp nested-reference unchanged"},{"id":"IETF RFC 5189","type":"specification","body":"IETF","designation":"RFC 5189","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5189.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5189.txt","https://www.rfc-editor.org/rfc/rfc5189.pdf"],"folder":"IETF/RFC-5189","files":{"txt":{"path":"standards/IETF/RFC-5189/RFC-5189.txt","sha256":"acd796e00034a33cf87e7d6f4537933ae78334c80d1085fe8e7ec1c963a22901"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies semantics for a Middlebox Communication\n (MIDCOM) protocol to be used by MIDCOM agents for interacting with\n middleboxes such as firewalls and Network Address Translators (NATs).\n The semantics discussion does not include any specification of a\n concrete syntax or a transport protocol. However, a concrete\n protocol is expected to implement the specified semantics or, more\n likely, a superset of it. The MIDCOM protocol semantics is derived\n from the MIDCOM requirements, from the MIDCOM framework, and from\n working group decisions. This document obsoletes RFC 3989.\n\nStiemerling, et al. Standards Track [Page 1]\n\f\nRFC 5189 MIDCOM Protocol Semantics March 2008","scope_keywords":["5189","authentication","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null}],"search_text":"IETF RFC 5189 This document specifies semantics for a Middlebox Communication\n (MIDCOM) protocol to be used by MIDCOM agents for interacting with\n middleboxes such as firewalls and Network Address Translators (NATs).\n The semantics discussion does not include any specification of a\n concrete syntax or a transport protocol. However, a concrete\n protocol is expected to implement the specified semantics or, more\n likely, a superset of it. The MIDCOM protocol semantics is derived\n from the MIDCOM requirements, from the MIDCOM framework, and from\n working group decisions. This document obsoletes RFC 3989.\n\nStiemerling, et al. Standards Track [Page 1]\n\f\nRFC 5189 MIDCOM Protocol Semantics March 2008 5189 authentication policy trust nested-reference unchanged"},{"id":"IETF RFC 5190","type":"specification","body":"IETF","designation":"RFC 5190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5190.txt","https://www.rfc-editor.org/rfc/rfc5190.pdf"],"folder":"IETF/RFC-5190","files":{"txt":{"path":"standards/IETF/RFC-5190/RFC-5190.txt","sha256":"1a670e62a3346294c6387f5e8ac84d3ed223f941ec2e04a2325e54556a79a074"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow\n configuring middleboxes, such as firewalls and network address\n translators, in order to enable communication across these devices.\n The definitions of managed objects in this documents follow closely\n the MIDCOM semantics defined in RFC 5189.\n\nQuittek, et al. Standards Track [Page 1]\n\f\nRFC 5190 MIDCOM MIB March 2008","scope_keywords":["5190","authentication","authorization","key","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null}],"search_text":"IETF RFC 5190 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a set of managed objects that allow\n configuring middleboxes, such as firewalls and network address\n translators, in order to enable communication across these devices.\n The definitions of managed objects in this documents follow closely\n the MIDCOM semantics defined in RFC 5189.\n\nQuittek, et al. Standards Track [Page 1]\n\f\nRFC 5190 MIDCOM MIB March 2008 5190 authentication authorization key management policies policy nested-reference unchanged"},{"id":"IETF RFC 5192","type":"specification","body":"IETF","designation":"RFC 5192","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5192.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5192.txt","https://www.rfc-editor.org/rfc/rfc5192.pdf"],"folder":"IETF/RFC-5192","files":{"txt":{"path":"standards/IETF/RFC-5192/RFC-5192.txt","sha256":"6626004f0dfdb0a958bcbf7411e5befca27593dd26658c980d24f5969ac7498f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new DHCPv4 and DHCPv6 options that contain a\n list of IP addresses to locate one or more PANA (Protocol for\n carrying Authentication for Network Access) Authentication Agents\n (PAAs). This is one of the methods that a PANA Client (PaC) can use\n to locate PAAs.","scope_keywords":["5192","authentication","authorization","credential","credentials","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null}],"search_text":"IETF RFC 5192 This document defines new DHCPv4 and DHCPv6 options that contain a\n list of IP addresses to locate one or more PANA (Protocol for\n carrying Authentication for Network Access) Authentication Agents\n (PAAs). This is one of the methods that a PANA Client (PaC) can use\n to locate PAAs. 5192 authentication authorization credential credentials key nested-reference unchanged"},{"id":"IETF RFC 5194","type":"specification","body":"IETF","designation":"RFC 5194","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5194.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5194.txt","https://www.rfc-editor.org/rfc/rfc5194.pdf"],"folder":"IETF/RFC-5194","files":{"txt":{"path":"standards/IETF/RFC-5194/RFC-5194.txt","sha256":"e813dc3cae7014f62aae2c93e3c0969a6d617dbff296eda152a31f101fbbba0f"}},"tags":["nested-reference","unchanged"],"summary":"This document lists the essential requirements for real-time Text-\n over-IP (ToIP) and defines a framework for implementation of all\n required functions based on the Session Initiation Protocol (SIP) and\n the Real-Time Transport Protocol (RTP). This includes interworking\n between Text-over-IP and existing text telephony on the Public\n Switched Telephone Network (PSTN) and other networks.\n\nvan Wijk & Gybels Informational [Page 1]\n\f\nRFC 5194 Framework for TOIP using SIP June 2008","scope_keywords":["5194","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null}],"search_text":"IETF RFC 5194 This document lists the essential requirements for real-time Text-\n over-IP (ToIP) and defines a framework for implementation of all\n required functions based on the Session Initiation Protocol (SIP) and\n the Real-Time Transport Protocol (RTP). This includes interworking\n between Text-over-IP and existing text telephony on the Public\n Switched Telephone Network (PSTN) and other networks.\n\nvan Wijk & Gybels Informational [Page 1]\n\f\nRFC 5194 Framework for TOIP using SIP June 2008 5194 presentation nested-reference unchanged"},{"id":"IETF RFC 5195","type":"specification","body":"IETF","designation":"RFC 5195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5195.txt","https://www.rfc-editor.org/rfc/rfc5195.pdf"],"folder":"IETF/RFC-5195","files":{"txt":{"path":"standards/IETF/RFC-5195/RFC-5195.txt","sha256":"01614617b4d0b490ea3c9fe3d0b02a8d7fba9f35a2bba82b92ddf1395bdc94d3"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to define a BGP-based auto-discovery\n mechanism for Layer-1 VPNs (L1VPNs). The auto-discovery mechanism\n for L1VPNs allows the provider network devices to dynamically\n discover the set of Provider Edges (PEs) having ports attached to\n Customer Edge (CE) members of the same VPN. That information is\n necessary for completing the signaling phase of L1VPN connections.\n One main objective of a L1VPN auto-discovery mechanism is to support\n the \"single-end provisioning\" model, where addition of a new port to\n a given L1VPN would involve configuration changes only on the PE that\n has this port and on the CE that is connected to the PE via this\n port.\n\n1. Introduction\n\n The purpose of this document is to define a BGP-based auto-discovery\n mechanism for Layer-1 VPNs (L1VPNs) [L1VPN-FRMK]. The auto-discovery\n mechanism for L1VPNs allows the provider network devices t","scope_keywords":["5195","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5252","folder":"IETF/RFC-5252","source":"IETF/RFC-5252/RFC-5252.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null}],"search_text":"IETF RFC 5195 The purpose of this document is to define a BGP-based auto-discovery\n mechanism for Layer-1 VPNs (L1VPNs). The auto-discovery mechanism\n for L1VPNs allows the provider network devices to dynamically\n discover the set of Provider Edges (PEs) having ports attached to\n Customer Edge (CE) members of the same VPN. That information is\n necessary for completing the signaling phase of L1VPN connections.\n One main objective of a L1VPN auto-discovery mechanism is to support\n the \"single-end provisioning\" model, where addition of a new port to\n a given L1VPN would involve configuration changes only on the PE that\n has this port and on the CE that is connected to the PE via this\n port.\n\n1. Introduction\n\n The purpose of this document is to define a BGP-based auto-discovery\n mechanism for Layer-1 VPNs (L1VPNs) [L1VPN-FRMK]. The auto-discovery\n mechanism for L1VPNs allows the provider network devices t 5195 key nested-reference unchanged"},{"id":"IETF RFC 5202","type":"specification","body":"IETF","designation":"RFC 5202","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5202.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5202.txt","https://www.rfc-editor.org/rfc/rfc5202.pdf"],"folder":"IETF/RFC-5202","files":{"txt":{"path":"standards/IETF/RFC-5202/RFC-5202.txt","sha256":"b0e844c1e32ac961c3f5f36dfacaef6e1178aea7e5a5a8f5c7bb7e0005a94927"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies an Encapsulated Security Payload (ESP) based\n mechanism for transmission of user data packets, to be used with the\n Host Identity Protocol (HIP).\n\nJokela, et al. Experimental [Page 1]\n\f\nRFC 5202 Using the ESP Transport Format with HIP April 2008","scope_keywords":["5202","encryption","key","keys","management","policy","presentation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5202 This memo specifies an Encapsulated Security Payload (ESP) based\n mechanism for transmission of user data packets, to be used with the\n Host Identity Protocol (HIP).\n\nJokela, et al. Experimental [Page 1]\n\f\nRFC 5202 Using the ESP Transport Format with HIP April 2008 5202 encryption key keys management policy presentation signature nested-reference unchanged"},{"id":"IETF RFC 5203","type":"specification","body":"IETF","designation":"RFC 5203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5203.txt","https://www.rfc-editor.org/rfc/rfc5203.pdf"],"folder":"IETF/RFC-5203","files":{"txt":{"path":"standards/IETF/RFC-5203/RFC-5203.txt","sha256":"59ce896299b4e30b70426ff7aed3a2668bbe85a3a0453bca686377b2a5d8e7ad"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a registration mechanism for the Host\n Identity Protocol (HIP) that allows hosts to register with services,\n such as HIP rendezvous servers or middleboxes.\n\n1. Introduction\n\n This document specifies an extension to the Host Identity Protocol\n (HIP) [RFC5201]. The extension provides a generic means for a host\n to register with a service. The service may, for example, be a HIP\n rendezvous server [RFC5204] or a middlebox [RFC3234].\n\n This document makes no further assumptions about the exact type of\n service. Likewise, this document does not specify any mechanisms to\n discover the presence of specific services or means to interact with\n them after registration. Future documents may describe those\n operations.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be ","scope_keywords":["5203","authorization","credential","credentials","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null}],"search_text":"IETF RFC 5203 This document specifies a registration mechanism for the Host\n Identity Protocol (HIP) that allows hosts to register with services,\n such as HIP rendezvous servers or middleboxes.\n\n1. Introduction\n\n This document specifies an extension to the Host Identity Protocol\n (HIP) [RFC5201]. The extension provides a generic means for a host\n to register with a service. The service may, for example, be a HIP\n rendezvous server [RFC5204] or a middlebox [RFC3234].\n\n This document makes no further assumptions about the exact type of\n service. Likewise, this document does not specify any mechanisms to\n discover the presence of specific services or means to interact with\n them after registration. Future documents may describe those\n operations.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be  5203 authorization credential credentials key policies nested-reference unchanged"},{"id":"IETF RFC 5206","type":"specification","body":"IETF","designation":"RFC 5206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5206.txt","https://www.rfc-editor.org/rfc/rfc5206.pdf"],"folder":"IETF/RFC-5206","files":{"txt":{"path":"standards/IETF/RFC-5206/RFC-5206.txt","sha256":"90963f6a3b356598597d71384aa19ea514f2ac5522ca9bda9587d61d18ea2246"}},"tags":["nested-reference","unchanged"],"summary":"This document defines mobility and multihoming extensions to the Host\n Identity Protocol (HIP). Specifically, this document defines a\n general \"LOCATOR\" parameter for HIP messages that allows for a HIP\n host to notify peers about alternate addresses at which it may be\n reached. This document also defines elements of procedure for\n mobility of a HIP host -- the process by which a host dynamically\n changes the primary locator that it uses to receive packets. While\n the same LOCATOR parameter can also be used to support end-host\n multihoming, detailed procedures are left for further study.","scope_keywords":["5206","authorization","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 5206 This document defines mobility and multihoming extensions to the Host\n Identity Protocol (HIP). Specifically, this document defines a\n general \"LOCATOR\" parameter for HIP messages that allows for a HIP\n host to notify peers about alternate addresses at which it may be\n reached. This document also defines elements of procedure for\n mobility of a HIP host -- the process by which a host dynamically\n changes the primary locator that it uses to receive packets. While\n the same LOCATOR parameter can also be used to support end-host\n multihoming, detailed procedures are left for further study. 5206 authorization key presentation nested-reference unchanged"},{"id":"IETF RFC 5222","type":"specification","body":"IETF","designation":"RFC 5222","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5222.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5222.txt","https://www.rfc-editor.org/rfc/rfc5222.pdf"],"folder":"IETF/RFC-5222","files":{"txt":{"path":"standards/IETF/RFC-5222/RFC-5222.txt","sha256":"55ba6242a2bf176fad940dad1d287dd3d002c68bd61df1648207447b27721989"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an XML-based protocol for mapping service\n identifiers and geodetic or civic location information to service\n contact URIs. In particular, it can be used to determine the\n location-appropriate Public Safety Answering Point (PSAP) for\n emergency services.","scope_keywords":["5222","attribute","attributes","http","path","pid","profile","profiles","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5582","folder":"IETF/RFC-5582","source":"IETF/RFC-5582/RFC-5582.txt","version":null},{"body":"IETF","designation":"RFC 5964","folder":"IETF/RFC-5964","source":"IETF/RFC-5964/RFC-5964.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5222 This document describes an XML-based protocol for mapping service\n identifiers and geodetic or civic location information to service\n contact URIs. In particular, it can be used to determine the\n location-appropriate Public Safety Answering Point (PSAP) for\n emergency services. 5222 attribute attributes http path pid profile profiles validation nested-reference unchanged"},{"id":"IETF RFC 5229","type":"specification","body":"IETF","designation":"RFC 5229","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5229.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5229.txt","https://www.rfc-editor.org/rfc/rfc5229.pdf"],"folder":"IETF/RFC-5229","files":{"txt":{"path":"standards/IETF/RFC-5229/RFC-5229.txt","sha256":"e78dc629bef36eb086da2e0aa37e3e828e8db70874e7795e2152afc0388c3820"}},"tags":["nested-reference","unchanged"],"summary":"In advanced mail filtering rule sets, it is useful to keep state or\n configuration details across rules. This document updates the Sieve\n filtering language (RFC 5228) with an extension to support variables.\n The extension changes the interpretation of strings, adds an action\n to store data in variables, and supplies a new test so that the value\n of a string can be examined.\n\nHomme Standards Track [Page 1]\n\f\nRFC 5229 Sieve: Variables Extension January 2008\n\n1. Introduction\n\n This is an extension to the Sieve language defined by [SIEVE]. It\n adds support for storing and referencing named data. The mechanisms\n detailed in this document will only apply to Sieve scripts that\n include a require clause for the \"variables\" extension. The require\n clauses themselves are not affected by this extension.\n\n Conventions for notations are as in [SIEVE] section 1.1, including\n use of [KEYWORDS] and [AB","scope_keywords":["5229","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5230","folder":"IETF/RFC-5230","source":"IETF/RFC-5230/RFC-5230.txt","version":null},{"body":"IETF","designation":"RFC 5232","folder":"IETF/RFC-5232","source":"IETF/RFC-5232/RFC-5232.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null}],"search_text":"IETF RFC 5229 In advanced mail filtering rule sets, it is useful to keep state or\n configuration details across rules. This document updates the Sieve\n filtering language (RFC 5228) with an extension to support variables.\n The extension changes the interpretation of strings, adds an action\n to store data in variables, and supplies a new test so that the value\n of a string can be examined.\n\nHomme Standards Track [Page 1]\n\f\nRFC 5229 Sieve: Variables Extension January 2008\n\n1. Introduction\n\n This is an extension to the Sieve language defined by [SIEVE]. It\n adds support for storing and referencing named data. The mechanisms\n detailed in this document will only apply to Sieve scripts that\n include a require clause for the \"variables\" extension. The require\n clauses themselves are not affected by this extension.\n\n Conventions for notations are as in [SIEVE] section 1.1, including\n use of [KEYWORDS] and [AB 5229 key subject nested-reference unchanged"},{"id":"IETF RFC 5231","type":"specification","body":"IETF","designation":"RFC 5231","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5231.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5231.txt","https://www.rfc-editor.org/rfc/rfc5231.pdf"],"folder":"IETF/RFC-5231","files":{"txt":{"path":"standards/IETF/RFC-5231/RFC-5231.txt","sha256":"6217616f6fbb2413cdf87bc1a42d6de9ac5bb2f6fecf664a9c2b8c68711607c2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the RELATIONAL extension to the Sieve mail\n filtering language defined in RFC 3028. This extension extends\n existing conditional tests in Sieve to allow relational operators.\n In addition to testing their content, it also allows for testing of\n the number of entities in header and envelope fields.\n\n This document obsoletes RFC 3431.","scope_keywords":["5231","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5183","folder":"IETF/RFC-5183","source":"IETF/RFC-5183/RFC-5183.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5232","folder":"IETF/RFC-5232","source":"IETF/RFC-5232/RFC-5232.txt","version":null},{"body":"IETF","designation":"RFC 5235","folder":"IETF/RFC-5235","source":"IETF/RFC-5235/RFC-5235.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null}],"search_text":"IETF RFC 5231 This document describes the RELATIONAL extension to the Sieve mail\n filtering language defined in RFC 3028. This extension extends\n existing conditional tests in Sieve to allow relational operators.\n In addition to testing their content, it also allows for testing of\n the number of entities in header and envelope fields.\n\n This document obsoletes RFC 3431. 5231 key subject nested-reference unchanged"},{"id":"IETF RFC 5232","type":"specification","body":"IETF","designation":"RFC 5232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5232.txt","https://www.rfc-editor.org/rfc/rfc5232.pdf"],"folder":"IETF/RFC-5232","files":{"txt":{"path":"standards/IETF/RFC-5232/RFC-5232.txt","sha256":"fc7aabcadbf7f40c6fc1b470042c007b622e1aa00b128cc96c4cbdf5e85a4d9d"}},"tags":["nested-reference","unchanged"],"summary":"Recent discussions have shown that it is desirable to set different\n IMAP (RFC 3501) flags on message delivery. This can be done, for\n example, by a Sieve interpreter that works as a part of a Mail\n Delivery Agent.\n\n This document describes an extension to the Sieve mail filtering\n language for setting IMAP flags. The extension allows setting of\n both IMAP system flags and IMAP keywords.","scope_keywords":["5232","delivery","key","preservation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5232 Recent discussions have shown that it is desirable to set different\n IMAP (RFC 3501) flags on message delivery. This can be done, for\n example, by a Sieve interpreter that works as a part of a Mail\n Delivery Agent.\n\n This document describes an extension to the Sieve mail filtering\n language for setting IMAP flags. The extension allows setting of\n both IMAP system flags and IMAP keywords. 5232 delivery key preservation nested-reference unchanged"},{"id":"IETF RFC 5233","type":"specification","body":"IETF","designation":"RFC 5233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5233.txt","https://www.rfc-editor.org/rfc/rfc5233.pdf"],"folder":"IETF/RFC-5233","files":{"txt":{"path":"standards/IETF/RFC-5233/RFC-5233.txt","sha256":"1fe51573d9c46d2b8e751cd52a692411ccce6ab077308dbbcdd0dd65f2db8848"}},"tags":["nested-reference","unchanged"],"summary":"On email systems that allow for 'subaddressing' or 'detailed\n addressing' (e.g., \"ken+sieve@example.org\"), it is sometimes\n desirable to make comparisons against these sub-parts of addresses.\n This document defines an extension to the Sieve Email Filtering\n Language that allows users to compare against the user and detail\n sub-parts of an address.","scope_keywords":["5233","key","keys","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"IETF RFC 5233 On email systems that allow for 'subaddressing' or 'detailed\n addressing' (e.g., \"ken+sieve@example.org\"), it is sometimes\n desirable to make comparisons against these sub-parts of addresses.\n This document defines an extension to the Sieve Email Filtering\n Language that allows users to compare against the user and detail\n sub-parts of an address. 5233 key keys subject nested-reference unchanged"},{"id":"IETF RFC 5235","type":"specification","body":"IETF","designation":"RFC 5235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5235.txt","https://www.rfc-editor.org/rfc/rfc5235.pdf"],"folder":"IETF/RFC-5235","files":{"txt":{"path":"standards/IETF/RFC-5235/RFC-5235.txt","sha256":"0f76ec5219149d870d8aa230786740552333eee2284aaa163c2061bee28115ce"}},"tags":["nested-reference","unchanged"],"summary":"The Sieve email filtering language \"spamtest\", \"spamtestplus\", and\n \"virustest\" extensions permit users to use simple, portable commands\n for spam and virus tests on email messages. Each extension provides\n a new test using matches against numeric \"scores\". It is the\n responsibility of the underlying Sieve implementation to do the\n actual checks that result in proper input to the tests.","scope_keywords":["5235","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5463","folder":"IETF/RFC-5463","source":"IETF/RFC-5463/RFC-5463.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5235 The Sieve email filtering language \"spamtest\", \"spamtestplus\", and\n \"virustest\" extensions permit users to use simple, portable commands\n for spam and virus tests on email messages. Each extension provides\n a new test using matches against numeric \"scores\". It is the\n responsibility of the underlying Sieve implementation to do the\n actual checks that result in proper input to the tests. 5235 key nested-reference unchanged"},{"id":"IETF RFC 5238","type":"specification","body":"IETF","designation":"RFC 5238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5238.txt","https://www.rfc-editor.org/rfc/rfc5238.pdf"],"folder":"IETF/RFC-5238","files":{"txt":{"path":"standards/IETF/RFC-5238/RFC-5238.txt","sha256":"ddc38bef17201dad3c962ae8f5fb161ac3c4ed421d312b1cf8bcce5fda9a64d3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the use of Datagram Transport Layer Security\n (DTLS) over the Datagram Congestion Control Protocol (DCCP). DTLS\n provides communications privacy for applications that use datagram\n transport protocols and allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping and\n detect tampering or message forgery. DCCP is a transport protocol\n that provides a congestion-controlled unreliable datagram service.","scope_keywords":["5238","algorithm","algorithms","delivery","key","path","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6520","folder":"IETF/RFC-6520","source":"IETF/RFC-6520/RFC-6520.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 5238 This document specifies the use of Datagram Transport Layer Security\n (DTLS) over the Datagram Congestion Control Protocol (DCCP). DTLS\n provides communications privacy for applications that use datagram\n transport protocols and allows client/server applications to\n communicate in a way that is designed to prevent eavesdropping and\n detect tampering or message forgery. DCCP is a transport protocol\n that provides a congestion-controlled unreliable datagram service. 5238 algorithm algorithms delivery key path tls nested-reference unchanged"},{"id":"IETF RFC 5239","type":"specification","body":"IETF","designation":"RFC 5239","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5239.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5239.txt","https://www.rfc-editor.org/rfc/rfc5239.pdf"],"folder":"IETF/RFC-5239","files":{"txt":{"path":"standards/IETF/RFC-5239/RFC-5239.txt","sha256":"69c90dd2eed3f7cb548687a18e92aa8528723f9c7f4a880d26e7afb6bb516f0f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the framework for Centralized Conferencing.\n The framework allows participants using various call signaling\n protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part\n (ISUP), to exchange media in a centralized unicast conference. The\n Centralized Conferencing Framework defines logical entities and\n naming conventions. The framework also outlines a set of\n conferencing protocols, which are complementary to the call signaling\n protocols, for building advanced conferencing applications. The\n framework binds all the defined components together for the benefit\n of builders of conferencing systems.\n\nBarnes, et al. Standards Track [Page 1]\n\f\nRFC 5239 Centralized Conferencing Framework June 2008","scope_keywords":["5239","authentication","authorization","key","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 5239 This document defines the framework for Centralized Conferencing.\n The framework allows participants using various call signaling\n protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part\n (ISUP), to exchange media in a centralized unicast conference. The\n Centralized Conferencing Framework defines logical entities and\n naming conventions. The framework also outlines a set of\n conferencing protocols, which are complementary to the call signaling\n protocols, for building advanced conferencing applications. The\n framework binds all the defined components together for the benefit\n of builders of conferencing systems.\n\nBarnes, et al. Standards Track [Page 1]\n\f\nRFC 5239 Centralized Conferencing Framework June 2008 5239 authentication authorization key policies nested-reference unchanged"},{"id":"IETF RFC 5252","type":"specification","body":"IETF","designation":"RFC 5252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5252.txt","https://www.rfc-editor.org/rfc/rfc5252.pdf"],"folder":"IETF/RFC-5252","files":{"txt":{"path":"standards/IETF/RFC-5252/RFC-5252.txt","sha256":"f734755caff813ebdf9a6c2455ade06b270fd0c0e7cee86322e51b45f61263cc"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Open Shortest Path First (OSPF) based Layer\n 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This\n mechanism enables provider edge (PE) devices using OSPF to\n dynamically learn about the existence of each other, and attributes\n of configured customer edge (CE) links and their associations with\n L1VPNs. This document builds on the L1VPN framework and requirements\n and provides a L1VPN basic mode auto-discovery mechanism.","scope_keywords":["5252","attribute","attributes","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null}],"search_text":"IETF RFC 5252 This document defines an Open Shortest Path First (OSPF) based Layer\n 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This\n mechanism enables provider edge (PE) devices using OSPF to\n dynamically learn about the existence of each other, and attributes\n of configured customer edge (CE) links and their associations with\n L1VPNs. This document builds on the L1VPN framework and requirements\n and provides a L1VPN basic mode auto-discovery mechanism. 5252 attribute attributes key path nested-reference unchanged"},{"id":"IETF RFC 5254","type":"specification","body":"IETF","designation":"RFC 5254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5254.txt","https://www.rfc-editor.org/rfc/rfc5254.pdf"],"folder":"IETF/RFC-5254","files":{"txt":{"path":"standards/IETF/RFC-5254/RFC-5254.txt","sha256":"aebb792789f4780a43331c0cb04b1f8ac67dab7de1bbbaa5cc7bafc7137cd544"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the necessary requirements to allow a service\n provider to extend the reach of pseudowires across multiple domains.\n These domains can be autonomous systems under one provider\n administrative control, IGP areas in one autonomous system, different\n autonomous systems under the administrative control of two or more\n service providers, or administratively established pseudowire\n domains.\n\nBitar, et al. Informational [Page 1]\n\f\nRFC 5254 Requirements for Multi-Segment PWE3 October 2008","scope_keywords":["5254","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null}],"search_text":"IETF RFC 5254 This document describes the necessary requirements to allow a service\n provider to extend the reach of pseudowires across multiple domains.\n These domains can be autonomous systems under one provider\n administrative control, IGP areas in one autonomous system, different\n autonomous systems under the administrative control of two or more\n service providers, or administratively established pseudowire\n domains.\n\nBitar, et al. Informational [Page 1]\n\f\nRFC 5254 Requirements for Multi-Segment PWE3 October 2008 5254 management nested-reference unchanged"},{"id":"IETF RFC 5258","type":"specification","body":"IETF","designation":"RFC 5258","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5258.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5258.txt","https://www.rfc-editor.org/rfc/rfc5258.pdf"],"folder":"IETF/RFC-5258","files":{"txt":{"path":"standards/IETF/RFC-5258/RFC-5258.txt","sha256":"9ec84900ac85244a0ec0d530fc704349737570ffaaada7b20e78725714bccb02"}},"tags":["nested-reference","unchanged"],"summary":"IMAP4 has two commands for listing mailboxes: LIST and LSUB. As we\n have added extensions, such as Mailbox Referrals, that have required\n specialized lists we have had to expand the number of list commands,\n since each extension must add its function to both LIST and LSUB, and\n these commands are not, as they are defined, extensible. If we've\n needed the extensions to work together, we've had to add a set of\n commands to mix the different options, the set increasing in size\n with each new extension. This document describes an extension to the\n base LIST command that will allow these additions to be done with\n mutually compatible options to the LIST command, avoiding the\n exponential increase in specialized list commands.\n\nLeiba & Melnikov Standards Track [Page 1]\n\f\nRFC 5258 IMAP4 LIST Command Extensions June 2008","scope_keywords":["5258","attribute","attributes","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5258 IMAP4 has two commands for listing mailboxes: LIST and LSUB. As we\n have added extensions, such as Mailbox Referrals, that have required\n specialized lists we have had to expand the number of list commands,\n since each extension must add its function to both LIST and LSUB, and\n these commands are not, as they are defined, extensible. If we've\n needed the extensions to work together, we've had to add a set of\n commands to mix the different options, the set increasing in size\n with each new extension. This document describes an extension to the\n base LIST command that will allow these additions to be done with\n mutually compatible options to the LIST command, avoiding the\n exponential increase in specialized list commands.\n\nLeiba & Melnikov Standards Track [Page 1]\n\f\nRFC 5258 IMAP4 LIST Command Extensions June 2008 5258 attribute attributes key nested-reference unchanged"},{"id":"IETF RFC 5261","type":"specification","body":"IETF","designation":"RFC 5261","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5261.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5261.txt","https://www.rfc-editor.org/rfc/rfc5261.pdf"],"folder":"IETF/RFC-5261","files":{"txt":{"path":"standards/IETF/RFC-5261/RFC-5261.txt","sha256":"85e39d9b228d7de68fb40846c9ceec70f7ef85c383fc11784d1ddf60389fd7cd"}},"tags":["nested-reference","unchanged"],"summary":"Extensible Markup Language (XML) documents are widely used as\n containers for the exchange and storage of arbitrary data in today's\n systems. In order to send changes to an XML document, an entire copy\n of the new version must be sent, unless there is a means of\n indicating only the portions that have changed. This document\n describes an XML patch framework utilizing XML Path language (XPath)\n selectors. These selector values and updated new data content\n constitute the basis of patch operations described in this document.\n In addition to them, with basic <add>, <replace>, and <remove>\n directives a set of patches can then be applied to update an existing\n XML document.","scope_keywords":["5261","attribute","attributes","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null}],"search_text":"IETF RFC 5261 Extensible Markup Language (XML) documents are widely used as\n containers for the exchange and storage of arbitrary data in today's\n systems. In order to send changes to an XML document, an entire copy\n of the new version must be sent, unless there is a means of\n indicating only the portions that have changed. This document\n describes an XML patch framework utilizing XML Path language (XPath)\n selectors. These selector values and updated new data content\n constitute the basis of patch operations described in this document.\n In addition to them, with basic <add>, <replace>, and <remove>\n directives a set of patches can then be applied to update an existing\n XML document. 5261 attribute attributes path pid nested-reference unchanged"},{"id":"IETF RFC 5262","type":"specification","body":"IETF","designation":"RFC 5262","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5262.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5262.txt","https://www.rfc-editor.org/rfc/rfc5262.pdf"],"folder":"IETF/RFC-5262","files":{"txt":{"path":"standards/IETF/RFC-5262/RFC-5262.txt","sha256":"48a751cf6dd8e2a0d6ed30d1a9706885b11fe47282cf031eec6d81e7582d0317"}},"tags":["nested-reference","unchanged"],"summary":"The Presence Information Document Format (PIDF) specifies the\n baseline XML-based format for describing presence information. One\n of the characteristics of the PIDF is that the document always needs\n to carry all presence information available for the presentity. In\n some environments where low bandwidth and high latency links can\n exist, it is often beneficial to limit the amount of transported\n information over the network. This document introduces a new MIME\n type that enables transporting of either only the changed parts or\n the full PIDF-based presence information.\n\nLonnfors, et al. Standards Track [Page 1]\n\f\nRFC 5262 Partial PIDF September 2008","scope_keywords":["5262","attribute","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null}],"search_text":"IETF RFC 5262 The Presence Information Document Format (PIDF) specifies the\n baseline XML-based format for describing presence information. One\n of the characteristics of the PIDF is that the document always needs\n to carry all presence information available for the presentity. In\n some environments where low bandwidth and high latency links can\n exist, it is often beneficial to limit the amount of transported\n information over the network. This document introduces a new MIME\n type that enables transporting of either only the changed parts or\n the full PIDF-based presence information.\n\nLonnfors, et al. Standards Track [Page 1]\n\f\nRFC 5262 Partial PIDF September 2008 5262 attribute key pid nested-reference unchanged"},{"id":"IETF RFC 5263","type":"specification","body":"IETF","designation":"RFC 5263","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5263.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5263.txt","https://www.rfc-editor.org/rfc/rfc5263.pdf"],"folder":"IETF/RFC-5263","files":{"txt":{"path":"standards/IETF/RFC-5263/RFC-5263.txt","sha256":"c1a29c8a9e91e2dde92ab97fa7d663c09670ad4bb7513c66f8ea293da26ac406"}},"tags":["nested-reference","unchanged"],"summary":"By default, presence delivered using the presence event package for\n the Session Initiation Protocol (SIP) is represented in the Presence\n Information Data Format (PIDF). A PIDF document contains a set of\n elements, each representing a different aspect of the presence being\n reported. When any subset of the elements change, even just a single\n element, a new document containing the full set of elements is\n delivered. This memo defines an extension allowing delivery of only\n the presence data that has actually changed.\n\nLonnfors, et al. Standards Track [Page 1]\n\f\nRFC 5263 Partial Notification September 2008","scope_keywords":["5263","authorization","delivery","key","pid","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5263 By default, presence delivered using the presence event package for\n the Session Initiation Protocol (SIP) is represented in the Presence\n Information Data Format (PIDF). A PIDF document contains a set of\n elements, each representing a different aspect of the presence being\n reported. When any subset of the elements change, even just a single\n element, a new document containing the full set of elements is\n delivered. This memo defines an extension allowing delivery of only\n the presence data that has actually changed.\n\nLonnfors, et al. Standards Track [Page 1]\n\f\nRFC 5263 Partial Notification September 2008 5263 authorization delivery key pid policy nested-reference unchanged"},{"id":"IETF RFC 5266","type":"specification","body":"IETF","designation":"RFC 5266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5266.txt","https://www.rfc-editor.org/rfc/rfc5266.pdf"],"folder":"IETF/RFC-5266","files":{"txt":{"path":"standards/IETF/RFC-5266/RFC-5266.txt","sha256":"f0a77536a82d11c34378aecd5cad6bca90388b909ade08e0b999792713c799cf"}},"tags":["nested-reference","unchanged"],"summary":"Enterprise users require mobility and secure connectivity when they\n roam and connect to the services offered in the enterprise. Secure\n connectivity is required when the user connects to the enterprise\n from an untrusted network. Mobility is beneficial when the user\n moves, either inside or outside the enterprise network, and acquires\n a new IP address. This document describes a solution using Mobile\n IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide\n secure connectivity and mobility.","scope_keywords":["5266","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5454","folder":"IETF/RFC-5454","source":"IETF/RFC-5454/RFC-5454.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5266 Enterprise users require mobility and secure connectivity when they\n roam and connect to the services offered in the enterprise. Secure\n connectivity is required when the user connects to the enterprise\n from an untrusted network. Mobility is beneficial when the user\n moves, either inside or outside the enterprise network, and acquires\n a new IP address. This document describes a solution using Mobile\n IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide\n secure connectivity and mobility. 5266 key trust nested-reference unchanged"},{"id":"IETF RFC 5267","type":"specification","body":"IETF","designation":"RFC 5267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5267.txt","https://www.rfc-editor.org/rfc/rfc5267.pdf"],"folder":"IETF/RFC-5267","files":{"txt":{"path":"standards/IETF/RFC-5267/RFC-5267.txt","sha256":"90fab13fcf980b56a1d970512d277692721309a19578e2814252bc07613b3bd6"}},"tags":["nested-reference","unchanged"],"summary":"The IMAP4rev1 protocol has powerful search facilities as part of the\n core protocol, but lacks the ability to create live, updated results\n that can be easily handled. This memo provides such an extension,\n and shows how it can be used to provide a facility similar to virtual\n mailboxes.\n\nCridland & King Standards Track [Page 1]\n\f\nRFC 5267 IMAP CONTEXT July 2008","scope_keywords":["5267","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null}],"search_text":"IETF RFC 5267 The IMAP4rev1 protocol has powerful search facilities as part of the\n core protocol, but lacks the ability to create live, updated results\n that can be easily handled. This memo provides such an extension,\n and shows how it can be used to provide a facility similar to virtual\n mailboxes.\n\nCridland & King Standards Track [Page 1]\n\f\nRFC 5267 IMAP CONTEXT July 2008 5267 key presentation nested-reference unchanged"},{"id":"IETF RFC 5268","type":"specification","body":"IETF","designation":"RFC 5268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5268.txt","https://www.rfc-editor.org/rfc/rfc5268.pdf"],"folder":"IETF/RFC-5268","files":{"txt":{"path":"standards/IETF/RFC-5268/RFC-5268.txt","sha256":"333723d367f0bdeadebe4f4b09c01655b8fd0a067abdc683be6bdc353debee89"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 enables a Mobile Node (MN) to maintain its connectivity\n to the Internet when moving from one Access Router to another, a\n process referred to as handover. During handover, there is a period\n during which the Mobile Node is unable to send or receive packets\n because of link switching delay and IP protocol operations. This\n \"handover latency\" resulting from standard Mobile IPv6 procedures,\n namely movement detection, new Care-of Address configuration, and\n Binding Update, is often unacceptable to real-time traffic such as\n Voice over IP (VoIP). Reducing the handover latency could be\n beneficial to non-real-time, throughput-sensitive applications as\n well. This document specifies a protocol to improve handover latency\n due to Mobile IPv6 procedures. This document does not address\n improving the link switching latency.\n\nKoodli, Ed. Standards Track [Page 1]\n\f\nRFC 5268 MIP6 Fast H","scope_keywords":["5268","authorization","key","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null}],"search_text":"IETF RFC 5268 Mobile IPv6 enables a Mobile Node (MN) to maintain its connectivity\n to the Internet when moving from one Access Router to another, a\n process referred to as handover. During handover, there is a period\n during which the Mobile Node is unable to send or receive packets\n because of link switching delay and IP protocol operations. This\n \"handover latency\" resulting from standard Mobile IPv6 procedures,\n namely movement detection, new Care-of Address configuration, and\n Binding Update, is often unacceptable to real-time traffic such as\n Voice over IP (VoIP). Reducing the handover latency could be\n beneficial to non-real-time, throughput-sensitive applications as\n well. This document specifies a protocol to improve handover latency\n due to Mobile IPv6 procedures. This document does not address\n improving the link switching latency.\n\nKoodli, Ed. Standards Track [Page 1]\n\f\nRFC 5268 MIP6 Fast H 5268 authorization key management policy nested-reference unchanged"},{"id":"IETF RFC 5269","type":"specification","body":"IETF","designation":"RFC 5269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5269.txt","https://www.rfc-editor.org/rfc/rfc5269.pdf"],"folder":"IETF/RFC-5269","files":{"txt":{"path":"standards/IETF/RFC-5269/RFC-5269.txt","sha256":"070a9adaf076265aa3ec40ba82c12c2aa00d711b1a8964f6416746af7ec25845"}},"tags":["nested-reference","unchanged"],"summary":"Fast Mobile IPv6 requires that a Fast Binding Update is secured using\n a security association shared between an Access Router and a Mobile\n Node in order to avoid certain attacks. In this document, a method\n for provisioning a shared key from the Access Router to the Mobile\n Node is defined to protect this signaling. The Mobile Node generates\n a public/private key pair using the same public key algorithm as for\n SEND (RFC 3971). The Mobile Node sends the public key to the Access\n Router. The Access Router encrypts a shared handover key using the\n public key and sends it back to the Mobile Node. The Mobile Node\n decrypts the shared handover key using the matching private key, and\n the handover key is then available for generating an authenticator on\n a Fast Binding Update. The Mobile Node and Access Router use the\n Router Solicitation for Proxy Advertisement and Proxy Router\n Advertisemen","scope_keywords":["5269","algorithm","authentication","authorization","encryption","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5268","folder":"IETF/RFC-5268","source":"IETF/RFC-5268/RFC-5268.txt","version":null},{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null}],"search_text":"IETF RFC 5269 Fast Mobile IPv6 requires that a Fast Binding Update is secured using\n a security association shared between an Access Router and a Mobile\n Node in order to avoid certain attacks. In this document, a method\n for provisioning a shared key from the Access Router to the Mobile\n Node is defined to protect this signaling. The Mobile Node generates\n a public/private key pair using the same public key algorithm as for\n SEND (RFC 3971). The Mobile Node sends the public key to the Access\n Router. The Access Router encrypts a shared handover key using the\n public key and sends it back to the Mobile Node. The Mobile Node\n decrypts the shared handover key using the matching private key, and\n the handover key is then available for generating an authenticator on\n a Fast Binding Update. The Mobile Node and Access Router use the\n Router Solicitation for Proxy Advertisement and Proxy Router\n Advertisemen 5269 algorithm authentication authorization encryption hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 5272","type":"specification","body":"IETF","designation":"RFC 5272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5272.txt","https://www.rfc-editor.org/rfc/rfc5272.pdf"],"folder":"IETF/RFC-5272","files":{"txt":{"path":"standards/IETF/RFC-5272/RFC-5272.txt","sha256":"bb65011f1f3fe77ec4999398a3f45ff4ab734f65af21469eb38b71e4d73bc2cd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the base syntax for CMC, a Certificate\n Management protocol using the Cryptographic Message Syntax (CMS).\n This protocol addresses two immediate needs within the Internet\n Public Key Infrastructure (PKI) community:\n\n 1. The need for an interface to public key certification products\n and services based on CMS and PKCS #10 (Public Key Cryptography\n Standard), and\n\n 2. The need for a PKI enrollment protocol for encryption only keys\n due to algorithm or hardware design.\n\n CMC also requires the use of the transport document and the\n requirements usage document along with this document for a full\n definition.\n\nSchaad & Myers Standards Track [Page 1]\n\f\nRFC 5272 CMC: Structures June 2008","scope_keywords":["5272","algorithm","attribute","certificate","crl","encryption","identification","key","keys","management","pki","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5273","folder":"IETF/RFC-5273","source":"IETF/RFC-5273/RFC-5273.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5275","folder":"IETF/RFC-5275","source":"IETF/RFC-5275/RFC-5275.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 5272 This document defines the base syntax for CMC, a Certificate\n Management protocol using the Cryptographic Message Syntax (CMS).\n This protocol addresses two immediate needs within the Internet\n Public Key Infrastructure (PKI) community:\n\n 1. The need for an interface to public key certification products\n and services based on CMS and PKCS #10 (Public Key Cryptography\n Standard), and\n\n 2. The need for a PKI enrollment protocol for encryption only keys\n due to algorithm or hardware design.\n\n CMC also requires the use of the transport document and the\n requirements usage document along with this document for a full\n definition.\n\nSchaad & Myers Standards Track [Page 1]\n\f\nRFC 5272 CMC: Structures June 2008 5272 algorithm attribute certificate crl encryption identification key keys management pki revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5273","type":"specification","body":"IETF","designation":"RFC 5273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5273.txt","https://www.rfc-editor.org/rfc/rfc5273.pdf"],"folder":"IETF/RFC-5273","files":{"txt":{"path":"standards/IETF/RFC-5273/RFC-5273.txt","sha256":"2912d945a29d37ea677acaa5f6a26aa2c8d61966a28fe4003e3aaa4799f0ebb1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a number of transport mechanisms that are used\n to move CMC (Certificate Management over CMS (Cryptographic Message\n Syntax)) messages. The transport mechanisms described in this\n document are HTTP, file, mail, and TCP.\n\n1. Overview\n\n This document defines a number of transport methods that are used to\n move CMC messages (defined in [CMC-STRUCT]). The transport\n mechanisms described in this document are HTTP, file, mail, and TCP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [MUST].\n\n2. File-Based Protocol\n\n Enrollment messages and responses may be transferred between clients\n and servers using file-system-based mechanisms, such as when\n enrollment is performed for an off-line client. When files are used\n to transport binary, ","scope_keywords":["5273","authentication","certificate","http","https","identification","key","management","pki","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7114","folder":"IETF/RFC-7114","source":"IETF/RFC-7114/RFC-7114.txt","version":null}],"search_text":"IETF RFC 5273 This document defines a number of transport mechanisms that are used\n to move CMC (Certificate Management over CMS (Cryptographic Message\n Syntax)) messages. The transport mechanisms described in this\n document are HTTP, file, mail, and TCP.\n\n1. Overview\n\n This document defines a number of transport methods that are used to\n move CMC messages (defined in [CMC-STRUCT]). The transport\n mechanisms described in this document are HTTP, file, mail, and TCP.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [MUST].\n\n2. File-Based Protocol\n\n Enrollment messages and responses may be transferred between clients\n and servers using file-system-based mechanisms, such as when\n enrollment is performed for an off-line client. When files are used\n to transport binary,  5273 authentication certificate http https identification key management pki tls nested-reference unchanged"},{"id":"IETF RFC 5274","type":"specification","body":"IETF","designation":"RFC 5274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5274.txt","https://www.rfc-editor.org/rfc/rfc5274.pdf"],"folder":"IETF/RFC-5274","files":{"txt":{"path":"standards/IETF/RFC-5274/RFC-5274.txt","sha256":"acb48a578567c8e5302e1b580faa2fec4c1528b780a166439e20c7f7a58df907"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a set of compliance statements about the CMC\n (Certificate Management over CMS) enrollment protocol. The ASN.1\n structures and the transport mechanisms for the CMC enrollment\n protocol are covered in other documents. This document provides the\n information needed to make a compliant version of CMC.","scope_keywords":["5274","algorithm","certificate","certificates","encryption","http","issuer","key","keys","management","pki","revocation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 5274 This document provides a set of compliance statements about the CMC\n (Certificate Management over CMS) enrollment protocol. The ASN.1\n structures and the transport mechanisms for the CMC enrollment\n protocol are covered in other documents. This document provides the\n information needed to make a compliant version of CMC. 5274 algorithm certificate certificates encryption http issuer key keys management pki revocation signature signatures nested-reference unchanged"},{"id":"IETF RFC 5275","type":"specification","body":"IETF","designation":"RFC 5275","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5275.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5275.txt","https://www.rfc-editor.org/rfc/rfc5275.pdf"],"folder":"IETF/RFC-5275","files":{"txt":{"path":"standards/IETF/RFC-5275/RFC-5275.txt","sha256":"5d7270859b9771464509b97f6e95ebf9d0cf8bf48b19c29b395849701dc519db"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to manage (i.e., set up,\n distribute, and rekey) keys used with symmetric cryptographic\n algorithms. Also defined herein is a mechanism to organize users\n into groups to support distribution of encrypted content using\n symmetric cryptographic algorithms. The mechanism uses the\n Cryptographic Message Syntax (CMS) protocol and Certificate\n Management over CMS (CMC) protocol to manage the symmetric keys. Any\n member of the group can then later use this distributed shared key to\n decrypt other CMS encrypted objects with the symmetric key. This\n mechanism has been developed to support Secure/Multipurpose Internet\n Mail Extensions (S/MIME) Mail List Agents (MLAs).\n\nTurner Standards Track [Page 1]\n\f\nRFC 5275 CMS SymKeyDist June 2008","scope_keywords":["5275","algorithm","algorithms","attribute","attributes","certificate","certificates","crl","encryption","key","keys","management","pki","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null}],"search_text":"IETF RFC 5275 This document describes a mechanism to manage (i.e., set up,\n distribute, and rekey) keys used with symmetric cryptographic\n algorithms. Also defined herein is a mechanism to organize users\n into groups to support distribution of encrypted content using\n symmetric cryptographic algorithms. The mechanism uses the\n Cryptographic Message Syntax (CMS) protocol and Certificate\n Management over CMS (CMC) protocol to manage the symmetric keys. Any\n member of the group can then later use this distributed shared key to\n decrypt other CMS encrypted objects with the symmetric key. This\n mechanism has been developed to support Secure/Multipurpose Internet\n Mail Extensions (S/MIME) Mail List Agents (MLAs).\n\nTurner Standards Track [Page 1]\n\f\nRFC 5275 CMS SymKeyDist June 2008 5275 algorithm algorithms attribute attributes certificate certificates crl encryption key keys management pki profile nested-reference unchanged"},{"id":"IETF RFC 5277","type":"specification","body":"IETF","designation":"RFC 5277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5277.txt","https://www.rfc-editor.org/rfc/rfc5277.pdf"],"folder":"IETF/RFC-5277","files":{"txt":{"path":"standards/IETF/RFC-5277/RFC-5277.txt","sha256":"6e1c4f4d33ba6e2b1c414c7ddf9c94c67bc432acdea96232467b780e73fde89c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines mechanisms that provide an asynchronous message\n notification delivery service for the Network Configuration protocol\n (NETCONF). This is an optional capability built on top of the base\n NETCONF definition. This document defines the capabilities and\n operations necessary to support this service.\n\nChisholm & Trevino Standards Track [Page 1]\n\f\nRFC 5277 NETCONF Event Notifications July 2008","scope_keywords":["5277","delivery","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5539","folder":"IETF/RFC-5539","source":"IETF/RFC-5539/RFC-5539.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null}],"search_text":"IETF RFC 5277 This document defines mechanisms that provide an asynchronous message\n notification delivery service for the Network Configuration protocol\n (NETCONF). This is an optional capability built on top of the base\n NETCONF definition. This document defines the capabilities and\n operations necessary to support this service.\n\nChisholm & Trevino Standards Track [Page 1]\n\f\nRFC 5277 NETCONF Event Notifications July 2008 5277 delivery key management path nested-reference unchanged"},{"id":"IETF RFC 5282","type":"specification","body":"IETF","designation":"RFC 5282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5282.txt","https://www.rfc-editor.org/rfc/rfc5282.pdf"],"folder":"IETF/RFC-5282","files":{"txt":{"path":"standards/IETF/RFC-5282/RFC-5282.txt","sha256":"cb0bf136b49b0b635aa90f8fd74b0405681a7dae214990e41c1ba1da876164a4"}},"tags":["nested-reference","unchanged"],"summary":"An authenticated encryption algorithm combines encryption and\n integrity into a single operation; such algorithms may also be\n referred to as combined modes of an encryption cipher or as combined\n mode algorithms. This document describes the use of authenticated\n encryption algorithms with the Encrypted Payload of the Internet Key\n Exchange version 2 (IKEv2) protocol.\n\n The use of two specific authenticated encryption algorithms with the\n IKEv2 Encrypted Payload is also described; these two algorithms are\n the Advanced Encryption Standard (AES) in Galois/Counter Mode (AES\n GCM) and AES in Counter with CBC-MAC Mode (AES CCM). Additional\n documents may describe the use of other authenticated encryption\n algorithms with the IKEv2 Encrypted Payload.\n\nBlack & McGrew Standards Track [Page 1]\n\f\nRFC 5282 Authenticated Encryption and IKEv2 August 2008","scope_keywords":["5282","algorithm","algorithms","encryption","hash","key","keys","management","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 5282 An authenticated encryption algorithm combines encryption and\n integrity into a single operation; such algorithms may also be\n referred to as combined modes of an encryption cipher or as combined\n mode algorithms. This document describes the use of authenticated\n encryption algorithms with the Encrypted Payload of the Internet Key\n Exchange version 2 (IKEv2) protocol.\n\n The use of two specific authenticated encryption algorithms with the\n IKEv2 Encrypted Payload is also described; these two algorithms are\n the Advanced Encryption Standard (AES) in Galois/Counter Mode (AES\n GCM) and AES in Counter with CBC-MAC Mode (AES CCM). Additional\n documents may describe the use of other authenticated encryption\n algorithms with the IKEv2 Encrypted Payload.\n\nBlack & McGrew Standards Track [Page 1]\n\f\nRFC 5282 Authenticated Encryption and IKEv2 August 2008 5282 algorithm algorithms encryption hash key keys management signature nested-reference unchanged"},{"id":"IETF RFC 5284","type":"specification","body":"IETF","designation":"RFC 5284","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5284.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5284.txt","https://www.rfc-editor.org/rfc/rfc5284.pdf"],"folder":"IETF/RFC-5284","files":{"txt":{"path":"standards/IETF/RFC-5284/RFC-5284.txt","sha256":"4614f8a4be3909043d7a196a56e71a1b28b789d92d02207bbb84282114a4924e"}},"tags":["nested-reference","unchanged"],"summary":"The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object\n for communicating errors. That object has a defined format that\n permits the definition of 256 error codes. As RSVP has been\n developed and extended, the convention has been to be conservative in\n defining new error codes. Further, no provision for user-defined\n errors exists in RSVP.\n\n This document defines a USER_ERROR_SPEC to be used in addition to the\n ERROR_SPEC to carry additional user information related to errors.\n\n1. Introduction\n\n The Resource ReserVation Protocol (RSVP) [RFC2205] defines an\n ERROR_SPEC object for communicating errors. That object has a\n defined format that permits the definition of 256 error codes. As\n RSVP has been developed and extended, the convention has been to be\n conservative in communicating errors. Further, no provision for user\n defined errors exists in RSVP.\n\n When developing ext","scope_keywords":["5284","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null}],"search_text":"IETF RFC 5284 The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object\n for communicating errors. That object has a defined format that\n permits the definition of 256 error codes. As RSVP has been\n developed and extended, the convention has been to be conservative in\n defining new error codes. Further, no provision for user-defined\n errors exists in RSVP.\n\n This document defines a USER_ERROR_SPEC to be used in addition to the\n ERROR_SPEC to carry additional user information related to errors.\n\n1. Introduction\n\n The Resource ReserVation Protocol (RSVP) [RFC2205] defines an\n ERROR_SPEC object for communicating errors. That object has a\n defined format that permits the definition of 256 error codes. As\n RSVP has been developed and extended, the convention has been to be\n conservative in communicating errors. Further, no provision for user\n defined errors exists in RSVP.\n\n When developing ext 5284 key path nested-reference unchanged"},{"id":"IETF RFC 5285","type":"specification","body":"IETF","designation":"RFC 5285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5285.txt","https://www.rfc-editor.org/rfc/rfc5285.pdf"],"folder":"IETF/RFC-5285","files":{"txt":{"path":"standards/IETF/RFC-5285/RFC-5285.txt","sha256":"aef336380f029dac5baf3c088eb1fefe800bdfdc5390ccdf68758aec93560f5f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a general mechanism to use the header\n extension feature of RTP (the Real-Time Transport Protocol). It\n provides the option to use a small number of small extensions in each\n RTP packet, where the universe of possible extensions is large and\n registration is de-centralized. The actual extensions in use in a\n session are signaled in the setup information for that session.","scope_keywords":["5285","attribute","key","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5450","folder":"IETF/RFC-5450","source":"IETF/RFC-5450/RFC-5450.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5285 This document provides a general mechanism to use the header\n extension feature of RTP (the Real-Time Transport Protocol). It\n provides the option to use a small number of small extensions in each\n RTP packet, where the universe of possible extensions is large and\n registration is de-centralized. The actual extensions in use in a\n session are signaled in the setup information for that session. 5285 attribute key profile nested-reference unchanged"},{"id":"IETF RFC 5288","type":"specification","body":"IETF","designation":"RFC 5288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5288.txt","https://www.rfc-editor.org/rfc/rfc5288.pdf"],"folder":"IETF/RFC-5288","files":{"txt":{"path":"standards/IETF/RFC-5288/RFC-5288.txt","sha256":"f68375c3f1948802240ca5b21f3aa44311ea02f877e4e240d1fc70927ecf1307"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n in Galois/Counter Mode (GCM) as a Transport Layer Security (TLS)\n authenticated encryption operation. GCM provides both\n confidentiality and data origin authentication, can be efficiently\n implemented in hardware for speeds of 10 gigabits per second and\n above, and is also well-suited to software implementations. This\n memo defines TLS cipher suites that use AES-GCM with RSA, DSA, and\n Diffie-Hellman-based key exchange mechanisms.","scope_keywords":["5288","algorithm","algorithms","authentication","encryption","hash","key","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5289","folder":"IETF/RFC-5289","source":"IETF/RFC-5289/RFC-5289.txt","version":null},{"body":"IETF","designation":"RFC 5430","folder":"IETF/RFC-5430","source":"IETF/RFC-5430/RFC-5430.txt","version":null},{"body":"IETF","designation":"RFC 5487","folder":"IETF/RFC-5487","source":"IETF/RFC-5487/RFC-5487.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null},{"body":"IETF","designation":"RFC 6655","folder":"IETF/RFC-6655","source":"IETF/RFC-6655/RFC-6655.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 5288 This memo describes the use of the Advanced Encryption Standard (AES)\n in Galois/Counter Mode (GCM) as a Transport Layer Security (TLS)\n authenticated encryption operation. GCM provides both\n confidentiality and data origin authentication, can be efficiently\n implemented in hardware for speeds of 10 gigabits per second and\n above, and is also well-suited to software implementations. This\n memo defines TLS cipher suites that use AES-GCM with RSA, DSA, and\n Diffie-Hellman-based key exchange mechanisms. 5288 algorithm algorithms authentication encryption hash key tls nested-reference unchanged"},{"id":"IETF RFC 5301","type":"specification","body":"IETF","designation":"RFC 5301","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5301.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5301.txt","https://www.rfc-editor.org/rfc/rfc5301.pdf"],"folder":"IETF/RFC-5301","files":{"txt":{"path":"standards/IETF/RFC-5301/RFC-5301.txt","sha256":"e5e7a38187fe7ef9c1ea96efacc899c62f069afd51686177de97fa2c6a13b16e"}},"tags":["nested-reference","unchanged"],"summary":"RFC 2763 defined a simple and dynamic mechanism for routers running\n IS-IS to learn about symbolic hostnames. RFC 2763 defined a new TLV\n that allows the IS-IS routers to flood their name-to-systemID mapping\n information across the IS-IS network.\n\n This document obsoletes RFC 2763. This document moves the capability\n provided by RFC 2763 to the Standards Track.","scope_keywords":["5301","algorithm","key","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5301 RFC 2763 defined a simple and dynamic mechanism for routers running\n IS-IS to learn about symbolic hostnames. RFC 2763 defined a new TLV\n that allows the IS-IS routers to flood their name-to-systemID mapping\n information across the IS-IS network.\n\n This document obsoletes RFC 2763. This document moves the capability\n provided by RFC 2763 to the Standards Track. 5301 algorithm key management presentation nested-reference unchanged"},{"id":"IETF RFC 5307","type":"specification","body":"IETF","designation":"RFC 5307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5307.txt","https://www.rfc-editor.org/rfc/rfc5307.pdf"],"folder":"IETF/RFC-5307","files":{"txt":{"path":"standards/IETF/RFC-5307/RFC-5307.txt","sha256":"f8813d0c4ccc660b8ac02833b39a814993b103102d0f71f15930f3a23c9f297b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies encoding of extensions to the IS-IS routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 5307 IS-IS Extensions for GMPLS October 2008\n\n1. Introduction\n\n This document specifies extensions to the IS-IS routing protocol in\n support of carrying link state information for Generalized Multi-\n Protocol Label Switching (GMPLS). The set of required enhancements\n to IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered\n interfaces assumes support for the \"Point-to-Point Three-Way\n Adjacency\" IS-IS Option type [ISIS-3way].\n\n In this section, we define the enhancements to the Traffic\n Engineering (TE) properties of GMPLS TE links that can be announced\n in IS-IS Link State Protocol Data Units.\n\n In this document, we enhance the sub-TLVs for the extended IS\n reachability TLV (see [ISIS-T","scope_keywords":["5307","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5543","folder":"IETF/RFC-5543","source":"IETF/RFC-5543/RFC-5543.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5307 This document specifies encoding of extensions to the IS-IS routing\n protocol in support of Generalized Multi-Protocol Label Switching\n (GMPLS).\n\nKompella & Rekhter Standards Track [Page 1]\n\f\nRFC 5307 IS-IS Extensions for GMPLS October 2008\n\n1. Introduction\n\n This document specifies extensions to the IS-IS routing protocol in\n support of carrying link state information for Generalized Multi-\n Protocol Label Switching (GMPLS). The set of required enhancements\n to IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered\n interfaces assumes support for the \"Point-to-Point Three-Way\n Adjacency\" IS-IS Option type [ISIS-3way].\n\n In this section, we define the enhancements to the Traffic\n Engineering (TE) properties of GMPLS TE links that can be announced\n in IS-IS Link State Protocol Data Units.\n\n In this document, we enhance the sub-TLVs for the extended IS\n reachability TLV (see [ISIS-T 5307 key nested-reference unchanged"},{"id":"IETF RFC 5311","type":"specification","body":"IETF","designation":"RFC 5311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5311.txt","https://www.rfc-editor.org/rfc/rfc5311.pdf"],"folder":"IETF/RFC-5311","files":{"txt":{"path":"standards/IETF/RFC-5311/RFC-5311.txt","sha256":"473f41160ebc73f453f4aa28e7599c3afe49dc4dc4f4226e2e530e6df73b61de"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simplified method for extending the Link\n State PDU (LSP) space beyond the 256 LSP limit. This method is\n intended as a preferred replacement for the method defined in RFC\n 3786.\n\nMcPherson, et al. Standards Track [Page 1]\n\f\nRFC 5311 Simplified Extension of LSP Space for IS-IS February 2009","scope_keywords":["5311","attribute","attributes","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null}],"search_text":"IETF RFC 5311 This document describes a simplified method for extending the Link\n State PDU (LSP) space beyond the 256 LSP limit. This method is\n intended as a preferred replacement for the method defined in RFC\n 3786.\n\nMcPherson, et al. Standards Track [Page 1]\n\f\nRFC 5311 Simplified Extension of LSP Space for IS-IS February 2009 5311 attribute attributes http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 5323","type":"specification","body":"IETF","designation":"RFC 5323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5323.txt","https://www.rfc-editor.org/rfc/rfc5323.pdf"],"folder":"IETF/RFC-5323","files":{"txt":{"path":"standards/IETF/RFC-5323/RFC-5323.txt","sha256":"e21b24926c87909234ad7f5206518f34824f8fd7c3e0b2154a418202ed2af6a9"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of methods, headers, and properties\n composing Web Distributed Authoring and Versioning (WebDAV) SEARCH,\n an application of the HTTP/1.1 protocol to efficiently search for DAV\n resources based upon a set of client-supplied criteria.\n\nReschke, et al. Standards Track [Page 1]\n\f\nRFC 5323 WebDAV SEARCH November 2008","scope_keywords":["5323","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null}],"search_text":"IETF RFC 5323 This document specifies a set of methods, headers, and properties\n composing Web Distributed Authoring and Versioning (WebDAV) SEARCH,\n an application of the HTTP/1.1 protocol to efficiently search for DAV\n resources based upon a set of client-supplied criteria.\n\nReschke, et al. Standards Track [Page 1]\n\f\nRFC 5323 WebDAV SEARCH November 2008 5323 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5329","type":"specification","body":"IETF","designation":"RFC 5329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5329.txt","https://www.rfc-editor.org/rfc/rfc5329.pdf"],"folder":"IETF/RFC-5329","files":{"txt":{"path":"standards/IETF/RFC-5329/RFC-5329.txt","sha256":"c5a9d77a33a85619f4e1e797d840c9f8534dfe7b1cfaa2c9dca18637a809409e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to OSPFv3 to support intra-area\n Traffic Engineering (TE). This document extends OSPFv2 TE to handle\n IPv6 networks. A new TLV and several new sub-TLVs are defined to\n support IPv6 networks.\n\nIshiguro, et al. Standards Track [Page 1]\n\f\nRFC 5329 OSPFv3-Traffic Engineering September 2008","scope_keywords":["5329","key","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5330","folder":"IETF/RFC-5330","source":"IETF/RFC-5330/RFC-5330.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null}],"search_text":"IETF RFC 5329 This document describes extensions to OSPFv3 to support intra-area\n Traffic Engineering (TE). This document extends OSPFv2 TE to handle\n IPv6 networks. A new TLV and several new sub-TLVs are defined to\n support IPv6 networks.\n\nIshiguro, et al. Standards Track [Page 1]\n\f\nRFC 5329 OSPFv3-Traffic Engineering September 2008 5329 key management trust nested-reference unchanged"},{"id":"IETF RFC 5331","type":"specification","body":"IETF","designation":"RFC 5331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5331.txt","https://www.rfc-editor.org/rfc/rfc5331.pdf"],"folder":"IETF/RFC-5331","files":{"txt":{"path":"standards/IETF/RFC-5331/RFC-5331.txt","sha256":"d0d0d68ee75f47b7cb4055aab34d9d5d28ab35efef030e25f3b5e113b4b538d4"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3031 limits the MPLS architecture to downstream-assigned MPLS\n labels. This document introduces the notion of upstream-assigned\n MPLS labels. It describes the procedures for upstream MPLS label\n assignment and introduces the concept of a \"Context-Specific Label\n Space\".","scope_keywords":["5331","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5332","folder":"IETF/RFC-5332","source":"IETF/RFC-5332/RFC-5332.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null}],"search_text":"IETF RFC 5331 RFC 3031 limits the MPLS architecture to downstream-assigned MPLS\n labels. This document introduces the notion of upstream-assigned\n MPLS labels. It describes the procedures for upstream MPLS label\n assignment and introduces the concept of a \"Context-Specific Label\n Space\". 5331 key path nested-reference unchanged"},{"id":"IETF RFC 5332","type":"specification","body":"IETF","designation":"RFC 5332","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5332.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5332.txt","https://www.rfc-editor.org/rfc/rfc5332.pdf"],"folder":"IETF/RFC-5332","files":{"txt":{"path":"standards/IETF/RFC-5332/RFC-5332.txt","sha256":"96cc9e4ae5939bfba877dc887857b2a90b65a926127854f25f600cc78713151f"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3032 established two data link layer codepoints for MPLS, used to\n distinguish whether the data link layer frame is carrying an MPLS\n unicast or an MPLS multicast packet. However, this usage was never\n deployed. This specification updates RFC 3032 by redefining the\n meaning of these two codepoints. Both codepoints can now be used to\n carry multicast packets. The second codepoint (formerly the\n \"multicast codepoint\") is now to be used only on multiaccess media,\n and it is to mean \"the top label of the following label stack is an\n upstream-assigned label\".\n\n RFC 3032 does not specify the destination address to be placed in the\n \"MAC DA\" (Medium Access Layer Destination Address) field of an\n ethernet frame that carries an MPLS multicast packet. This document\n provides that specification.\n\n This document updates RFC 3032 and RFC 4023.\n\nEckert, et al. Standards Track [Page 1]\n\f\nRFC 5332 M","scope_keywords":["5332","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5331","folder":"IETF/RFC-5331","source":"IETF/RFC-5331/RFC-5331.txt","version":null},{"body":"IETF","designation":"RFC 5342","folder":"IETF/RFC-5342","source":"IETF/RFC-5342/RFC-5342.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 5332 RFC 3032 established two data link layer codepoints for MPLS, used to\n distinguish whether the data link layer frame is carrying an MPLS\n unicast or an MPLS multicast packet. However, this usage was never\n deployed. This specification updates RFC 3032 by redefining the\n meaning of these two codepoints. Both codepoints can now be used to\n carry multicast packets. The second codepoint (formerly the\n \"multicast codepoint\") is now to be used only on multiaccess media,\n and it is to mean \"the top label of the following label stack is an\n upstream-assigned label\".\n\n RFC 3032 does not specify the destination address to be placed in the\n \"MAC DA\" (Medium Access Layer Destination Address) field of an\n ethernet frame that carries an MPLS multicast packet. This document\n provides that specification.\n\n This document updates RFC 3032 and RFC 4023.\n\nEckert, et al. Standards Track [Page 1]\n\f\nRFC 5332 M 5332 key nested-reference unchanged"},{"id":"IETF RFC 5341","type":"specification","body":"IETF","designation":"RFC 5341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5341.txt","https://www.rfc-editor.org/rfc/rfc5341.pdf"],"folder":"IETF/RFC-5341","files":{"txt":{"path":"standards/IETF/RFC-5341/RFC-5341.txt","sha256":"07bb9fa66e77e74bfbdc8ebd6977e165dc8c6a2724b53bdcf603cac6c1829c57"}},"tags":["nested-reference","unchanged"],"summary":"This document creates an Internet Assigned Number Authority (IANA)\n registry for tel Uniform Resource Identifier (URI) parameters and\n their values. It populates the registry with the parameters defined\n in the tel URI specification, along with the parameters in tel URI\n extensions defined for number portability and trunk groups.","scope_keywords":["5341","key","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"}],"search_text":"IETF RFC 5341 This document creates an Internet Assigned Number Authority (IANA)\n registry for tel Uniform Resource Identifier (URI) parameters and\n their values. It populates the registry with the parameters defined\n in the tel URI specification, along with the parameters in tel URI\n extensions defined for number portability and trunk groups. 5341 key policy registered nested-reference unchanged"},{"id":"IETF RFC 5343","type":"specification","body":"IETF","designation":"RFC 5343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5343.txt","https://www.rfc-editor.org/rfc/rfc5343.pdf"],"folder":"IETF/RFC-5343","files":{"txt":{"path":"standards/IETF/RFC-5343/RFC-5343.txt","sha256":"2237face468e0d0327e837dac6b6c00f4c2951965cdcb1c1e601186103d6ad7f"}},"tags":["nested-reference","unchanged"],"summary":"The Simple Network Management Protocol (SNMP) version three (SNMPv3)\n requires that an application know the identifier (snmpEngineID) of\n the remote SNMP protocol engine in order to retrieve or manipulate\n objects maintained on the remote SNMP entity.\n\n This document introduces a well-known localEngineID and a discovery\n mechanism that can be used to learn the snmpEngineID of a remote SNMP\n protocol engine. The proposed mechanism is independent of the\n features provided by SNMP security models and may also be used by\n other protocol interfaces providing access to managed objects.\n\n This document updates RFC 3411.","scope_keywords":["5343","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null}],"search_text":"IETF RFC 5343 The Simple Network Management Protocol (SNMP) version three (SNMPv3)\n requires that an application know the identifier (snmpEngineID) of\n the remote SNMP protocol engine in order to retrieve or manipulate\n objects maintained on the remote SNMP entity.\n\n This document introduces a well-known localEngineID and a discovery\n mechanism that can be used to learn the snmpEngineID of a remote SNMP\n protocol engine. The proposed mechanism is independent of the\n features provided by SNMP security models and may also be used by\n other protocol interfaces providing access to managed objects.\n\n This document updates RFC 3411. 5343 identification key management nested-reference unchanged"},{"id":"IETF RFC 5348","type":"specification","body":"IETF","designation":"RFC 5348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5348.txt","https://www.rfc-editor.org/rfc/rfc5348.pdf"],"folder":"IETF/RFC-5348","files":{"txt":{"path":"standards/IETF/RFC-5348/RFC-5348.txt","sha256":"710ee07be69e4986cb0a926a87ddff32b66392ac162c2d137e2ce5cbff66413f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies TCP Friendly Rate Control (TFRC). TFRC is a\n congestion control mechanism for unicast flows operating in a best-\n effort Internet environment. It is reasonably fair when competing\n for bandwidth with TCP flows, but has a much lower variation of\n throughput over time compared with TCP, making it more suitable for\n applications such as streaming media where a relatively smooth\n sending rate is of importance.\n\n This document obsoletes RFC 3448 and updates RFC 4342.","scope_keywords":["5348","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5881","folder":"IETF/RFC-5881","source":"IETF/RFC-5881/RFC-5881.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null}],"search_text":"IETF RFC 5348 This document specifies TCP Friendly Rate Control (TFRC). TFRC is a\n congestion control mechanism for unicast flows operating in a best-\n effort Internet environment. It is reasonably fair when competing\n for bandwidth with TCP flows, but has a much lower variation of\n throughput over time compared with TCP, making it more suitable for\n applications such as streaming media where a relatively smooth\n sending rate is of importance.\n\n This document obsoletes RFC 3448 and updates RFC 4342. 5348 management nested-reference unchanged"},{"id":"IETF RFC 5357","type":"specification","body":"IETF","designation":"RFC 5357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5357.txt","https://www.rfc-editor.org/rfc/rfc5357.pdf"],"folder":"IETF/RFC-5357","files":{"txt":{"path":"standards/IETF/RFC-5357/RFC-5357.txt","sha256":"473849a8af63f863caad7c5b65e922e278190b16bf6c2ff877972738f476669a"}},"tags":["nested-reference","unchanged"],"summary":"The One-way Active Measurement Protocol (OWAMP), specified in RFC\n 4656, provides a common protocol for measuring one-way metrics\n between network devices. OWAMP can be used bi-directionally to\n measure one-way metrics in both directions between two network\n elements. However, it does not accommodate round-trip or two-way\n measurements. This memo specifies a Two-Way Active Measurement\n Protocol (TWAMP), based on the OWAMP, that adds two-way or round-trip\n measurement capabilities. The TWAMP measurement architecture is\n usually comprised of two hosts with specific roles, and this allows\n for some protocol simplifications, making it an attractive\n alternative in some circumstances.\n\nHedayat, et al. Standards Track [Page 1]\n\f\nRFC 5357 Two-Way Active Measurement Protocol October 2008","scope_keywords":["5357","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6349","folder":"IETF/RFC-6349","source":"IETF/RFC-6349/RFC-6349.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 5357 The One-way Active Measurement Protocol (OWAMP), specified in RFC\n 4656, provides a common protocol for measuring one-way metrics\n between network devices. OWAMP can be used bi-directionally to\n measure one-way metrics in both directions between two network\n elements. However, it does not accommodate round-trip or two-way\n measurements. This memo specifies a Two-Way Active Measurement\n Protocol (TWAMP), based on the OWAMP, that adds two-way or round-trip\n measurement capabilities. The TWAMP measurement architecture is\n usually comprised of two hosts with specific roles, and this allows\n for some protocol simplifications, making it an attractive\n alternative in some circumstances.\n\nHedayat, et al. Standards Track [Page 1]\n\f\nRFC 5357 Two-Way Active Measurement Protocol October 2008 5357 key management nested-reference unchanged"},{"id":"IETF RFC 5360","type":"specification","body":"IETF","designation":"RFC 5360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5360.txt","https://www.rfc-editor.org/rfc/rfc5360.pdf"],"folder":"IETF/RFC-5360","files":{"txt":{"path":"standards/IETF/RFC-5360/RFC-5360.txt","sha256":"4156e06a7bc5793df234feac081a4ceba7993d408fbfb2a2a7e7df2ab86acda0"}},"tags":["nested-reference","unchanged"],"summary":"SIP supports communications for several services, including real-time\n audio, video, text, instant messaging, and presence. In its current\n form, it allows session invitations, instant messages, and other\n requests to be delivered from one party to another without requiring\n explicit consent of the recipient. Without such consent, it is\n possible for SIP to be used for malicious purposes, including\n amplification and DoS (Denial of Service) attacks. This document\n identifies a framework for consent-based communications in SIP.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 5360 Consent Framework October 2008","scope_keywords":["5360","key","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5361","folder":"IETF/RFC-5361","source":"IETF/RFC-5361/RFC-5361.txt","version":null},{"body":"IETF","designation":"RFC 5362","folder":"IETF/RFC-5362","source":"IETF/RFC-5362/RFC-5362.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null}],"search_text":"IETF RFC 5360 SIP supports communications for several services, including real-time\n audio, video, text, instant messaging, and presence. In its current\n form, it allows session invitations, instant messages, and other\n requests to be delivered from one party to another without requiring\n explicit consent of the recipient. Without such consent, it is\n possible for SIP to be used for malicious purposes, including\n amplification and DoS (Denial of Service) attacks. This document\n identifies a framework for consent-based communications in SIP.\n\nRosenberg, et al. Standards Track [Page 1]\n\f\nRFC 5360 Consent Framework October 2008 5360 key revocation nested-reference unchanged"},{"id":"IETF RFC 5361","type":"specification","body":"IETF","designation":"RFC 5361","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5361.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5361.txt","https://www.rfc-editor.org/rfc/rfc5361.pdf"],"folder":"IETF/RFC-5361","files":{"txt":{"path":"standards/IETF/RFC-5361/RFC-5361.txt","sha256":"50867a923d00437abf397aa0b6039393c97ed69a496ecf3345a00b0417cdd8d6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Extensible Markup Language (XML) format for\n a permission document used to request consent. A permission document\n written in this format is used by a relay to request a specific\n recipient permission to perform a particular routing translation.","scope_keywords":["5361","attribute","attributes","authentication","key","policy","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null}],"search_text":"IETF RFC 5361 This document defines an Extensible Markup Language (XML) format for\n a permission document used to request consent. A permission document\n written in this format is used by a relay to request a specific\n recipient permission to perform a particular routing translation. 5361 attribute attributes authentication key policy signature nested-reference unchanged"},{"id":"IETF RFC 5362","type":"specification","body":"IETF","designation":"RFC 5362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5362.txt","https://www.rfc-editor.org/rfc/rfc5362.pdf"],"folder":"IETF/RFC-5362","files":{"txt":{"path":"standards/IETF/RFC-5362/RFC-5362.txt","sha256":"49e29cf25233aede689742579a50ef517fa62d6985d331e9fc5cad9f6a9ad3cd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the SIP Pending Additions event package. This\n event package is used by SIP relays to inform user agents about the\n consent-related status of the entries to be added to a resource list.\n\nCamarillo Standards Track [Page 1]\n\f\nRFC 5362 Pending Additions Event Package October 2008","scope_keywords":["5362","attribute","http","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null}],"search_text":"IETF RFC 5362 This document defines the SIP Pending Additions event package. This\n event package is used by SIP relays to inform user agents about the\n consent-related status of the entries to be added to a resource list.\n\nCamarillo Standards Track [Page 1]\n\f\nRFC 5362 Pending Additions Event Package October 2008 5362 attribute http key qualified nested-reference unchanged"},{"id":"IETF RFC 5363","type":"specification","body":"IETF","designation":"RFC 5363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5363.txt","https://www.rfc-editor.org/rfc/rfc5363.pdf"],"folder":"IETF/RFC-5363","files":{"txt":{"path":"standards/IETF/RFC-5363/RFC-5363.txt","sha256":"209a1eae12165b0083a3d0eec0c1234a6067a06248d9e45873010085caaaa314"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the need for SIP URI-list services and\n provides requirements for their invocation. Additionally, it defines\n a framework for SIP URI-list services, which includes security\n considerations applicable to these services.","scope_keywords":["5363","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5367","folder":"IETF/RFC-5367","source":"IETF/RFC-5367/RFC-5367.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null}],"search_text":"IETF RFC 5363 This document describes the need for SIP URI-list services and\n provides requirements for their invocation. Additionally, it defines\n a framework for SIP URI-list services, which includes security\n considerations applicable to these services. 5363 key nested-reference unchanged"},{"id":"IETF RFC 5364","type":"specification","body":"IETF","designation":"RFC 5364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5364.txt","https://www.rfc-editor.org/rfc/rfc5364.pdf"],"folder":"IETF/RFC-5364","files":{"txt":{"path":"standards/IETF/RFC-5364/RFC-5364.txt","sha256":"8b369801de2f934b4a5e0a5ed8ad5ef30c10173c0de642ab3c87c29347d79ee7"}},"tags":["nested-reference","unchanged"],"summary":"In certain types of multimedia communications, a Session Initiation\n Protocol (SIP) request is distributed to a group of SIP User Agents\n (UAs). The sender sends a single SIP request to a server which\n further distributes the request to the group. This SIP request\n contains a list of Uniform Resource Identifiers (URIs), which\n identify the recipients of the SIP request. This URI list is\n expressed as a resource list XML document. This specification\n defines an XML extension to the XML resource list format that allows\n the sender of the request to qualify a recipient with a copy control\n level similar to the copy control level of existing email systems.","scope_keywords":["5364","attribute","attributes","issuer","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5365","folder":"IETF/RFC-5365","source":"IETF/RFC-5365/RFC-5365.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5364 In certain types of multimedia communications, a Session Initiation\n Protocol (SIP) request is distributed to a group of SIP User Agents\n (UAs). The sender sends a single SIP request to a server which\n further distributes the request to the group. This SIP request\n contains a list of Uniform Resource Identifiers (URIs), which\n identify the recipients of the SIP request. This URI list is\n expressed as a resource list XML document. This specification\n defines an XML extension to the XML resource list format that allows\n the sender of the request to qualify a recipient with a copy control\n level similar to the copy control level of existing email systems. 5364 attribute attributes issuer key nested-reference unchanged"},{"id":"IETF RFC 5365","type":"specification","body":"IETF","designation":"RFC 5365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5365.txt","https://www.rfc-editor.org/rfc/rfc5365.pdf"],"folder":"IETF/RFC-5365","files":{"txt":{"path":"standards/IETF/RFC-5365/RFC-5365.txt","sha256":"782775aeb2ab72276517ef63e0d9a85e3bf08c7dc1c5be47709fde354af7cd33"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism that allows a SIP User Agent\n Client (UAC) to send a SIP MESSAGE request to a set of destinations,\n by using a SIP URI-list (Uniform Resource Identifier list) service.\n The UAC sends a SIP MESSAGE request that includes the payload along\n with the URI list to the MESSAGE URI-list service, which sends a\n MESSAGE request including the payload to each of the URIs included in\n the list.","scope_keywords":["5365","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null}],"search_text":"IETF RFC 5365 This document specifies a mechanism that allows a SIP User Agent\n Client (UAC) to send a SIP MESSAGE request to a set of destinations,\n by using a SIP URI-list (Uniform Resource Identifier list) service.\n The UAC sends a SIP MESSAGE request that includes the payload along\n with the URI list to the MESSAGE URI-list service, which sends a\n MESSAGE request including the payload to each of the URIs included in\n the list. 5365 key nested-reference unchanged"},{"id":"IETF RFC 5366","type":"specification","body":"IETF","designation":"RFC 5366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5366.txt","https://www.rfc-editor.org/rfc/rfc5366.pdf"],"folder":"IETF/RFC-5366","files":{"txt":{"path":"standards/IETF/RFC-5366/RFC-5366.txt","sha256":"df8d69ddc0004ad1915ff41bbaf25d20044111082ef8274a3dac2fd4adc70969"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to create a conference using SIP URI-list\n services. In particular, it describes a mechanism that allows a User\n Agent Client to provide a conference server with the initial list of\n participants using an INVITE-contained URI list.","scope_keywords":["5366","attribute","attributes","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5364","folder":"IETF/RFC-5364","source":"IETF/RFC-5364/RFC-5364.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null}],"search_text":"IETF RFC 5366 This document describes how to create a conference using SIP URI-list\n services. In particular, it describes a mechanism that allows a User\n Agent Client to provide a conference server with the initial list of\n participants using an INVITE-contained URI list. 5366 attribute attributes key registered nested-reference unchanged"},{"id":"IETF RFC 5367","type":"specification","body":"IETF","designation":"RFC 5367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5367.txt","https://www.rfc-editor.org/rfc/rfc5367.pdf"],"folder":"IETF/RFC-5367","files":{"txt":{"path":"standards/IETF/RFC-5367/RFC-5367.txt","sha256":"b3e0f131c14ef4171001816fd2069c31fccffb24b777040248b73146a13fac60"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a way to create subscription to a list of\n resources in SIP. This is achieved by including the list of\n resources in the body of a SUBSCRIBE request. Instead of having a\n subscriber send a SUBSCRIBE request for each resource individually,\n the subscriber defines the resource list, subscribes to it, and gets\n notifications about changes in the resources' states using a single\n SUBSCRIBE dialog.","scope_keywords":["5367","http","key","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null}],"search_text":"IETF RFC 5367 This document specifies a way to create subscription to a list of\n resources in SIP. This is achieved by including the list of\n resources in the body of a SUBSCRIBE request. Instead of having a\n subscriber send a SUBSCRIBE request for each resource individually,\n the subscriber defines the resource list, subscribes to it, and gets\n notifications about changes in the resources' states using a single\n SUBSCRIBE dialog. 5367 http key management registered nested-reference unchanged"},{"id":"IETF RFC 5368","type":"specification","body":"IETF","designation":"RFC 5368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5368.txt","https://www.rfc-editor.org/rfc/rfc5368.pdf"],"folder":"IETF/RFC-5368","files":{"txt":{"path":"standards/IETF/RFC-5368/RFC-5368.txt","sha256":"2d79faca7c6869576ccd0233fff39a026f3a61aad357c0ff0e435646ff06cac0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to the SIP REFER method so that it\n can be used to refer to multiple resources in a single request.\n These extensions include the use of pointers to Uniform Resource\n Identifier (URI) lists in the Refer-To header field and the\n \"multiple-refer\" SIP option-tag.","scope_keywords":["5368","issuer","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5621","folder":"IETF/RFC-5621","source":"IETF/RFC-5621/RFC-5621.txt","version":null}],"search_text":"IETF RFC 5368 This document defines extensions to the SIP REFER method so that it\n can be used to refer to multiple resources in a single request.\n These extensions include the use of pointers to Uniform Resource\n Identifier (URI) lists in the Refer-To header field and the\n \"multiple-refer\" SIP option-tag. 5368 issuer key nested-reference unchanged"},{"id":"IETF RFC 5376","type":"specification","body":"IETF","designation":"RFC 5376","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5376.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5376.txt","https://www.rfc-editor.org/rfc/rfc5376.pdf"],"folder":"IETF/RFC-5376","files":{"txt":{"path":"standards/IETF/RFC-5376/RFC-5376.txt","sha256":"76d3417fa219f6126ff620e70e79f70f1dfc78a5fcd42b717ed952617c8d881c"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label\n Switched Paths (LSPs) may be established wholly within an Autonomous\n System (AS) or may cross AS boundaries.\n\n The Path Computation Element (PCE) is a component that is capable of\n computing constrained paths for (G)MPLS TE LSPs. The PCE\n Communication Protocol (PCECP) is defined to allow communication\n between Path Computation Clients (PCCs) and PCEs, as well as between\n PCEs. The PCECP is used to request constrained paths and to supply\n computed paths in response. Generic requirements for the PCECP are\n set out in \"Path Computation Element (PCE) Communication Protocol\n Generic Requirements\", RFC 4657. This document extends those\n requirements to cover the use of PCECP in support of inter-AS MPLS\n TE.\n\nBitar, et al. Informational [Page 1]\n\f\nRFC 5376 Inter-AS Requirements for PCECP November 2008","scope_keywords":["5376","http","key","keys","license","management","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 5376 Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label\n Switched Paths (LSPs) may be established wholly within an Autonomous\n System (AS) or may cross AS boundaries.\n\n The Path Computation Element (PCE) is a component that is capable of\n computing constrained paths for (G)MPLS TE LSPs. The PCE\n Communication Protocol (PCECP) is defined to allow communication\n between Path Computation Clients (PCCs) and PCEs, as well as between\n PCEs. The PCECP is used to request constrained paths and to supply\n computed paths in response. Generic requirements for the PCECP are\n set out in \"Path Computation Element (PCE) Communication Protocol\n Generic Requirements\", RFC 4657. This document extends those\n requirements to cover the use of PCECP in support of inter-AS MPLS\n TE.\n\nBitar, et al. Informational [Page 1]\n\f\nRFC 5376 Inter-AS Requirements for PCECP November 2008 5376 http key keys license management path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5380","type":"specification","body":"IETF","designation":"RFC 5380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5380.txt","https://www.rfc-editor.org/rfc/rfc5380.pdf"],"folder":"IETF/RFC-5380","files":{"txt":{"path":"standards/IETF/RFC-5380/RFC-5380.txt","sha256":"74286d5926ea2c659a9de3d2d20e7104444de8944b131690ab9f3c8262dec0ad"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces extensions to Mobile IPv6 and IPv6 Neighbour\n Discovery to allow for local mobility handling. Hierarchical\n mobility management for Mobile IPv6 is designed to reduce the amount\n of signalling between the mobile node, its correspondent nodes, and\n its home agent. The Mobility Anchor Point (MAP) described in this\n document can also be used to improve the performance of Mobile IPv6\n in terms of handover speed.\n\nSoliman, et al. Standards Track [Page 1]\n\f\nRFC 5380 HMIPv6 October 2008","scope_keywords":["5380","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null}],"search_text":"IETF RFC 5380 This document introduces extensions to Mobile IPv6 and IPv6 Neighbour\n Discovery to allow for local mobility handling. Hierarchical\n mobility management for Mobile IPv6 is designed to reduce the amount\n of signalling between the mobile node, its correspondent nodes, and\n its home agent. The Mobility Anchor Point (MAP) described in this\n document can also be used to improve the performance of Mobile IPv6\n in terms of handover speed.\n\nSoliman, et al. Standards Track [Page 1]\n\f\nRFC 5380 HMIPv6 October 2008 5380 management nested-reference unchanged"},{"id":"IETF RFC 5384","type":"specification","body":"IETF","designation":"RFC 5384","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5384.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5384.txt","https://www.rfc-editor.org/rfc/rfc5384.pdf"],"folder":"IETF/RFC-5384","files":{"txt":{"path":"standards/IETF/RFC-5384/RFC-5384.txt","sha256":"3ec588482b042f8d227e591d854b0c633152a4813b1a8b74f6e4f412537664e5"}},"tags":["nested-reference","unchanged"],"summary":"A \"Protocol Independent Multicast - Sparse Mode\" Join message sent by\n a given node identifies one or more multicast distribution trees that\n that node wishes to join. Each tree is identified by the combination\n of a multicast group address and a source address (where the source\n address is possibly a \"wild card\"). Under certain conditions it can\n be useful, when joining a tree, to specify additional information\n related to the construction of the tree. However, there has been no\n way to do so until now. This document describes a modification of\n the Join message that allows a node to associate attributes with a\n particular tree. The attributes are encoded in Type-Length-Value\n format.\n\nBoers, et al. Standards Track [Page 1]\n\f\nRFC 5384 PIM Join Attribute November 2008","scope_keywords":["5384","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5496","folder":"IETF/RFC-5496","source":"IETF/RFC-5496/RFC-5496.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6807","folder":"IETF/RFC-6807","source":"IETF/RFC-6807/RFC-6807.txt","version":null}],"search_text":"IETF RFC 5384 A \"Protocol Independent Multicast - Sparse Mode\" Join message sent by\n a given node identifies one or more multicast distribution trees that\n that node wishes to join. Each tree is identified by the combination\n of a multicast group address and a source address (where the source\n address is possibly a \"wild card\"). Under certain conditions it can\n be useful, when joining a tree, to specify additional information\n related to the construction of the tree. However, there has been no\n way to do so until now. This document describes a modification of\n the Join message that allows a node to associate attributes with a\n particular tree. The attributes are encoded in Type-Length-Value\n format.\n\nBoers, et al. Standards Track [Page 1]\n\f\nRFC 5384 PIM Join Attribute November 2008 5384 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5386","type":"specification","body":"IETF","designation":"RFC 5386","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5386.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5386.txt","https://www.rfc-editor.org/rfc/rfc5386.pdf"],"folder":"IETF/RFC-5386","files":{"txt":{"path":"standards/IETF/RFC-5386/RFC-5386.txt","sha256":"a58621c196e615aafc51d745c6a741621d0e5012f99f988162ff22e4b2d977a4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use the Internet Key Exchange (IKE)\n protocols, such as IKEv1 and IKEv2, to setup \"unauthenticated\"\n security associations (SAs) for use with the IPsec Encapsulating\n Security Payload (ESP) and the IPsec Authentication Header (AH). No\n changes to IKEv2 bits-on-the-wire are required, but Peer\n Authorization Database (PAD) and Security Policy Database (SPD)\n extensions are specified. Unauthenticated IPsec is herein referred\n to by its popular acronym, \"BTNS\" (Better-Than-Nothing Security).\n\nWilliams & Richardson Standards Track [Page 1]\n\f\nRFC 5386 BTNS IPsec November 2008","scope_keywords":["5386","authentication","authorization","certificate","certificates","http","key","keys","license","policy","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null}],"search_text":"IETF RFC 5386 This document specifies how to use the Internet Key Exchange (IKE)\n protocols, such as IKEv1 and IKEv2, to setup \"unauthenticated\"\n security associations (SAs) for use with the IPsec Encapsulating\n Security Payload (ESP) and the IPsec Authentication Header (AH). No\n changes to IKEv2 bits-on-the-wire are required, but Peer\n Authorization Database (PAD) and Security Policy Database (SPD)\n extensions are specified. Unauthenticated IPsec is herein referred\n to by its popular acronym, \"BTNS\" (Better-Than-Nothing Security).\n\nWilliams & Richardson Standards Track [Page 1]\n\f\nRFC 5386 BTNS IPsec November 2008 5386 authentication authorization certificate certificates http key keys license policy signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5392","type":"specification","body":"IETF","designation":"RFC 5392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5392.txt","https://www.rfc-editor.org/rfc/rfc5392.pdf"],"folder":"IETF/RFC-5392","files":{"txt":{"path":"standards/IETF/RFC-5392/RFC-5392.txt","sha256":"bf38af015f0742701ba133576dea2b802810746c363fc9327d454e1ecedf785d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the OSPF version 2 and 3\n protocols to support Multiprotocol Label Switching (MPLS) and\n Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple\n Autonomous Systems (ASes). OSPF-TE v2 and v3 extensions are defined\n for the flooding of TE information about inter-AS links that can be\n used to perform inter-AS TE path computation.\n\n No support for flooding information from within one AS to another AS\n is proposed or defined in this document.\n\nChen, et al. Standards Track [Page 1]\n\f\nRFC 5392 OSPF Extensions for Inter-AS TE January 2009","scope_keywords":["5392","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5392 This document describes extensions to the OSPF version 2 and 3\n protocols to support Multiprotocol Label Switching (MPLS) and\n Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple\n Autonomous Systems (ASes). OSPF-TE v2 and v3 extensions are defined\n for the flooding of TE information about inter-AS links that can be\n used to perform inter-AS TE path computation.\n\n No support for flooding information from within one AS to another AS\n is proposed or defined in this document.\n\nChen, et al. Standards Track [Page 1]\n\f\nRFC 5392 OSPF Extensions for Inter-AS TE January 2009 5392 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5397","type":"specification","body":"IETF","designation":"RFC 5397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5397.txt","https://www.rfc-editor.org/rfc/rfc5397.pdf"],"folder":"IETF/RFC-5397","files":{"txt":{"path":"standards/IETF/RFC-5397/RFC-5397.txt","sha256":"d78af2fe387dbc2fde9711dbdb2c1c80a8e30c14030d3b84fd2918652397f8c4"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a new WebDAV property that allows clients\n to quickly determine the principal corresponding to the current\n authenticated user.","scope_keywords":["5397","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null}],"search_text":"IETF RFC 5397 This specification defines a new WebDAV property that allows clients\n to quickly determine the principal corresponding to the current\n authenticated user. 5397 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5404","type":"specification","body":"IETF","designation":"RFC 5404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5404.txt","https://www.rfc-editor.org/rfc/rfc5404.pdf"],"folder":"IETF/RFC-5404","files":{"txt":{"path":"standards/IETF/RFC-5404/RFC-5404.txt","sha256":"3d3b2ea688900f36318c8b2dab00b8fcc0f216d391c00d6f94c125d01d6f98a4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the payload format for packetization of the\n G.719 full-band codec encoded audio signals into the Real-time\n Transport Protocol (RTP). The payload format supports transmission\n of multiple channels, multiple frames per payload, and interleaving.\n\nWesterlund & Johansson Standards Track [Page 1]\n\f\nRFC 5404 RTP Payload Format for G.719 January 2009","scope_keywords":["5404","algorithm","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null}],"search_text":"IETF RFC 5404 This document specifies the payload format for packetization of the\n G.719 full-band codec encoded audio signals into the Real-time\n Transport Protocol (RTP). The payload format supports transmission\n of multiple channels, multiple frames per payload, and interleaving.\n\nWesterlund & Johansson Standards Track [Page 1]\n\f\nRFC 5404 RTP Payload Format for G.719 January 2009 5404 algorithm http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5409","type":"specification","body":"IETF","designation":"RFC 5409","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5409.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5409.txt","https://www.rfc-editor.org/rfc/rfc5409.pdf"],"folder":"IETF/RFC-5409","files":{"txt":{"path":"standards/IETF/RFC-5409/RFC-5409.txt","sha256":"067ee335f54eba322ec6d0c3946c112370a11cb80ce011d0e4b1ff2372624108"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the Boneh-Franklin\n (BF) and Boneh-Boyen (BB1) identity-based encryption algorithms in\n the Cryptographic Message Syntax (CMS) to encrypt content-encryption\n keys. Object identifiers and the convention for encoding a\n recipient's identity are also defined.\n\nMartin & Schertler Informational [Page 1]\n\f\nRFC 5409 Using IBE with CMS January 2009","scope_keywords":["5409","algorithm","algorithms","authentication","encryption","http","key","keys","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 6267","folder":"IETF/RFC-6267","source":"IETF/RFC-6267/RFC-6267.txt","version":null}],"search_text":"IETF RFC 5409 This document describes the conventions for using the Boneh-Franklin\n (BF) and Boneh-Boyen (BB1) identity-based encryption algorithms in\n the Cryptographic Message Syntax (CMS) to encrypt content-encryption\n keys. Object identifiers and the convention for encoding a\n recipient's identity are also defined.\n\nMartin & Schertler Informational [Page 1]\n\f\nRFC 5409 Using IBE with CMS January 2009 5409 algorithm algorithms authentication encryption http key keys license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5417","type":"specification","body":"IETF","designation":"RFC 5417","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5417.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5417.txt","https://www.rfc-editor.org/rfc/rfc5417.pdf"],"folder":"IETF/RFC-5417","files":{"txt":{"path":"standards/IETF/RFC-5417/RFC-5417.txt","sha256":"411b9527240741842f5e3d3d8354fe5726a597778deba277b0e5a4360902280e"}},"tags":["nested-reference","unchanged"],"summary":"The Control And Provisioning of Wireless Access Points Protocol\n allows a Wireless Termination Point to use DHCP to discover the\n Access Controllers to which it is to connect. This document\n describes the DHCP options to be used by the CAPWAP Protocol.\n\nCalhoun Standards Track [Page 1]\n\f\nRFC 5417 CAPWAP AC DHCP Option March 2009","scope_keywords":["5417","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null}],"search_text":"IETF RFC 5417 The Control And Provisioning of Wireless Access Points Protocol\n allows a Wireless Termination Point to use DHCP to discover the\n Access Controllers to which it is to connect. This document\n describes the DHCP options to be used by the CAPWAP Protocol.\n\nCalhoun Standards Track [Page 1]\n\f\nRFC 5417 CAPWAP AC DHCP Option March 2009 5417 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5420","type":"specification","body":"IETF","designation":"RFC 5420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5420.txt","https://www.rfc-editor.org/rfc/rfc5420.pdf"],"folder":"IETF/RFC-5420","files":{"txt":{"path":"standards/IETF/RFC-5420/RFC-5420.txt","sha256":"1314a993de9ab6e619b6ac33c830aabab1ad23f6c51a995d1c0c4d5d888319ae"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may\n be established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions. This protocol includes an object\n (the SESSION_ATTRIBUTE object) that carries a Flags field used to\n indicate options and attributes of the LSP. That Flags field has\n eight bits, allowing for eight options to be set. Recent proposals\n in many documents that extend RSVP-TE have suggested uses for each of\n the previously unused bits.\n\n This document defines a new object for RSVP-TE messages that allows\n the signaling of further attribute bits and also the carriage of\n arbitrary attribute parameters to make RSVP-TE easily extensible to\n support new requirements. Additionally, this document defines a way\n to record the attributes applied to the LSP on a hop-by-hop basis.\n\n The object mechanisms defined in this document are equ","scope_keywords":["5420","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null}],"search_text":"IETF RFC 5420 Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may\n be established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions. This protocol includes an object\n (the SESSION_ATTRIBUTE object) that carries a Flags field used to\n indicate options and attributes of the LSP. That Flags field has\n eight bits, allowing for eight options to be set. Recent proposals\n in many documents that extend RSVP-TE have suggested uses for each of\n the previously unused bits.\n\n This document defines a new object for RSVP-TE messages that allows\n the signaling of further attribute bits and also the carriage of\n arbitrary attribute parameters to make RSVP-TE easily extensible to\n support new requirements. Additionally, this document defines a way\n to record the attributes applied to the LSP on a hop-by-hop basis.\n\n The object mechanisms defined in this document are equ 5420 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5421","type":"specification","body":"IETF","designation":"RFC 5421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5421.txt","https://www.rfc-editor.org/rfc/rfc5421.pdf"],"folder":"IETF/RFC-5421","files":{"txt":{"path":"standards/IETF/RFC-5421/RFC-5421.txt","sha256":"aa94858c7b186c74a5afd6a95b277770c9660dc458f739ae1496903e820987ee"}},"tags":["nested-reference","unchanged"],"summary":"The Flexible Authentication via Secure Tunneling Extensible\n Authentication Protocol (EAP-FAST) method enables secure\n communication between a peer and a server by using Transport Layer\n Security (TLS) to establish a mutually authenticated tunnel. Within\n this tunnel, a basic password exchange, based on the Generic Token\n Card method (EAP-GTC), may be executed to authenticate the peer.","scope_keywords":["5421","authentication","credential","credentials","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 5421 The Flexible Authentication via Secure Tunneling Extensible\n Authentication Protocol (EAP-FAST) method enables secure\n communication between a peer and a server by using Transport Layer\n Security (TLS) to establish a mutually authenticated tunnel. Within\n this tunnel, a basic password exchange, based on the Generic Token\n Card method (EAP-GTC), may be executed to authenticate the peer. 5421 authentication credential credentials encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5425","type":"specification","body":"IETF","designation":"RFC 5425","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5425.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5425.txt","https://www.rfc-editor.org/rfc/rfc5425.pdf"],"folder":"IETF/RFC-5425","files":{"txt":{"path":"standards/IETF/RFC-5425/RFC-5425.txt","sha256":"a807ec7024fb200e9cf91590cfe41ac06029fb48bf9ddba088862bc134647639"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of Transport Layer Security (TLS) to\n provide a secure connection for the transport of syslog messages.\n This document describes the security threats to syslog and how TLS\n can be used to counter such threats.\n\nMiao, et al. Standards Track [Page 1]\n\f\nRFC 5425 TLS Transport Mapping for Syslog March 2009","scope_keywords":["5425","authentication","authorization","certificate","delivery","http","key","license","policies","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5848","folder":"IETF/RFC-5848","source":"IETF/RFC-5848/RFC-5848.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5425 This document describes the use of Transport Layer Security (TLS) to\n provide a secure connection for the transport of syslog messages.\n This document describes the security threats to syslog and how TLS\n can be used to counter such threats.\n\nMiao, et al. Standards Track [Page 1]\n\f\nRFC 5425 TLS Transport Mapping for Syslog March 2009 5425 authentication authorization certificate delivery http key license policies subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 5427","type":"specification","body":"IETF","designation":"RFC 5427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5427.txt","https://www.rfc-editor.org/rfc/rfc5427.pdf"],"folder":"IETF/RFC-5427","files":{"txt":{"path":"standards/IETF/RFC-5427/RFC-5427.txt","sha256":"e7bb1a674b5373aa1f8e4171eb943986f5c4bbc84f50998406ec223da1ded39d"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent Facility and\n Severity information commonly used in syslog messages. The intent is\n that these textual conventions will be imported and used in MIB\n modules that would otherwise define their own representations.\n\nKeeni Standards Track [Page 1]\n\f\nRFC 5427 Syslog MIB-TC March 2009","scope_keywords":["5427","holder","http","key","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5427 This MIB module defines textual conventions to represent Facility and\n Severity information commonly used in syslog messages. The intent is\n that these textual conventions will be imported and used in MIB\n modules that would otherwise define their own representations.\n\nKeeni Standards Track [Page 1]\n\f\nRFC 5427 Syslog MIB-TC March 2009 5427 holder http key license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5430","type":"specification","body":"IETF","designation":"RFC 5430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5430.txt","https://www.rfc-editor.org/rfc/rfc5430.pdf"],"folder":"IETF/RFC-5430","files":{"txt":{"path":"standards/IETF/RFC-5430/RFC-5430.txt","sha256":"dd1b624a27797470090e2da9e380f12a64b1cbc9fddfbcb0a6057a80d2f9ab6a"}},"tags":["nested-reference","unchanged"],"summary":"The United States government has published guidelines for \"NSA Suite\n B Cryptography\", which defines cryptographic algorithm policy for\n national security applications. This document defines a profile of\n Transport Layer Security (TLS) version 1.2 that is fully conformant\n with Suite B. This document also defines a transitional profile for\n use with TLS version 1.0 and TLS version 1.1 which employs Suite B\n algorithms to the greatest extent possible.","scope_keywords":["5430","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","hashing","http","key","license","path","policy","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null}],"search_text":"IETF RFC 5430 The United States government has published guidelines for \"NSA Suite\n B Cryptography\", which defines cryptographic algorithm policy for\n national security applications. This document defines a profile of\n Transport Layer Security (TLS) version 1.2 that is fully conformant\n with Suite B. This document also defines a transitional profile for\n use with TLS version 1.0 and TLS version 1.1 which employs Suite B\n algorithms to the greatest extent possible. 5430 algorithm algorithms authentication certificate certificates encryption hash hashing http key license path policy profile profiles nested-reference unchanged"},{"id":"IETF RFC 5432","type":"specification","body":"IETF","designation":"RFC 5432","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5432.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5432.txt","https://www.rfc-editor.org/rfc/rfc5432.pdf"],"folder":"IETF/RFC-5432","files":{"txt":{"path":"standards/IETF/RFC-5432/RFC-5432.txt","sha256":"bdf48aa1a1c986f7d593e34d54fb15e8cd1d2de47790d6f8977a8336f155c0bc"}},"tags":["nested-reference","unchanged"],"summary":"The offer/answer model for the Session Description Protocol (SDP)\n assumes that endpoints somehow establish the Quality of Service (QoS)\n required for the media streams they establish. Endpoints in closed\n environments typically agree out-of-band (e.g., using configuration\n information) regarding which QoS mechanism to use. However, on the\n Internet, there is more than one QoS service available.\n Consequently, there is a need for a mechanism to negotiate which QoS\n mechanism to use for a particular media stream. This document\n defines such a mechanism.","scope_keywords":["5432","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5432 The offer/answer model for the Session Description Protocol (SDP)\n assumes that endpoints somehow establish the Quality of Service (QoS)\n required for the media streams they establish. Endpoints in closed\n environments typically agree out-of-band (e.g., using configuration\n information) regarding which QoS mechanism to use. However, on the\n Internet, there is more than one QoS service available.\n Consequently, there is a need for a mechanism to negotiate which QoS\n mechanism to use for a particular media stream. This document\n defines such a mechanism. 5432 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5435","type":"specification","body":"IETF","designation":"RFC 5435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5435.txt","https://www.rfc-editor.org/rfc/rfc5435.pdf"],"folder":"IETF/RFC-5435","files":{"txt":{"path":"standards/IETF/RFC-5435/RFC-5435.txt","sha256":"81fa374027655880fdb4bde510b5b10953fd236d71e387c1b541b3f8019011fc"}},"tags":["nested-reference","unchanged"],"summary":"Users go to great lengths to be notified as quickly as possible that\n they have received new mail. Most of these methods involve polling\n to check for new messages periodically. A push method handled by the\n final delivery agent gives users quicker notifications and saves\n server resources. This document does not specify the notification\n method, but it is expected that using existing instant messaging\n infrastructure such as Extensible Messaging and Presence Protocol\n (XMPP), or Global System for Mobile Communications (GSM) Short\n Message Service (SMS) messages will be popular. This document\n describes an extension to the Sieve mail filtering language that\n allows users to give specific rules for how and when notifications\n should be sent.\n\nMelnikov, et al. Standards Track [Page 1]\n\f\nRFC 5435 Sieve Extension: Notifications January 2009","scope_keywords":["5435","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5436","folder":"IETF/RFC-5436","source":"IETF/RFC-5436/RFC-5436.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null}],"search_text":"IETF RFC 5435 Users go to great lengths to be notified as quickly as possible that\n they have received new mail. Most of these methods involve polling\n to check for new messages periodically. A push method handled by the\n final delivery agent gives users quicker notifications and saves\n server resources. This document does not specify the notification\n method, but it is expected that using existing instant messaging\n infrastructure such as Extensible Messaging and Presence Protocol\n (XMPP), or Global System for Mobile Communications (GSM) Short\n Message Service (SMS) messages will be popular. This document\n describes an extension to the Sieve mail filtering language that\n allows users to give specific rules for how and when notifications\n should be sent.\n\nMelnikov, et al. Standards Track [Page 1]\n\f\nRFC 5435 Sieve Extension: Notifications January 2009 5435 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5436","type":"specification","body":"IETF","designation":"RFC 5436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5436.txt","https://www.rfc-editor.org/rfc/rfc5436.pdf"],"folder":"IETF/RFC-5436","files":{"txt":{"path":"standards/IETF/RFC-5436/RFC-5436.txt","sha256":"1e76abbb8631c50ad28cd5bd64be2ab2c3ccbf3dd59b04ea2b176df354be3ef4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile of the Sieve extension for\n notifications, to allow notifications to be sent by electronic mail.\n\nLeiba & Haardt Standards Track [Page 1]\n\f\nRFC 5436 Sieve Notification Mechanism: mailto January 2009","scope_keywords":["5436","delivery","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null}],"search_text":"IETF RFC 5436 This document describes a profile of the Sieve extension for\n notifications, to allow notifications to be sent by electronic mail.\n\nLeiba & Haardt Standards Track [Page 1]\n\f\nRFC 5436 Sieve Notification Mechanism: mailto January 2009 5436 delivery http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5437","type":"specification","body":"IETF","designation":"RFC 5437","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5437.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5437.txt","https://www.rfc-editor.org/rfc/rfc5437.pdf"],"folder":"IETF/RFC-5437","files":{"txt":{"path":"standards/IETF/RFC-5437/RFC-5437.txt","sha256":"72015a432133444c7e80a60521a74b8505c73d7cc5765c71c1e6e7c72abbcd55"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a profile of the Sieve extension for\n notifications, to allow notifications to be sent over the Extensible\n Messaging and Presence Protocol (XMPP), also known as Jabber.\n\nSaint-Andre & Melnikov Standards Track [Page 1]\n\f\nRFC 5437 Sieve Notify Method: XMPP January 2009","scope_keywords":["5437","attribute","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5437 This document describes a profile of the Sieve extension for\n notifications, to allow notifications to be sent over the Extensible\n Messaging and Presence Protocol (XMPP), also known as Jabber.\n\nSaint-Andre & Melnikov Standards Track [Page 1]\n\f\nRFC 5437 Sieve Notify Method: XMPP January 2009 5437 attribute http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5445","type":"specification","body":"IETF","designation":"RFC 5445","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5445.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5445.txt","https://www.rfc-editor.org/rfc/rfc5445.pdf"],"folder":"IETF/RFC-5445","files":{"txt":{"path":"standards/IETF/RFC-5445/RFC-5445.txt","sha256":"a275b21d98b5ff108dafcff4255d91e77a84735444b8fa2e206fff9435e310fb"}},"tags":["nested-reference","unchanged"],"summary":"This document provides Forward Error Correction (FEC) Scheme\n specifications according to the Reliable Multicast Transport (RMT)\n FEC building block for the Compact No-Code FEC Scheme, the Small\n Block, Large Block, and Expandable FEC Scheme, the Small Block\n Systematic FEC Scheme, and the Compact FEC Scheme. This document\n obsoletes RFC 3695 and assumes responsibility for the FEC Schemes\n defined in RFC 3452.\n\nWatson Standards Track [Page 1]\n\f\nRFC 5445 Basic FEC Schemes March 2009","scope_keywords":["5445","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 6726","folder":"IETF/RFC-6726","source":"IETF/RFC-6726/RFC-6726.txt","version":null}],"search_text":"IETF RFC 5445 This document provides Forward Error Correction (FEC) Scheme\n specifications according to the Reliable Multicast Transport (RMT)\n FEC building block for the Compact No-Code FEC Scheme, the Small\n Block, Large Block, and Expandable FEC Scheme, the Small Block\n Systematic FEC Scheme, and the Compact FEC Scheme. This document\n obsoletes RFC 3695 and assumes responsibility for the FEC Schemes\n defined in RFC 3452.\n\nWatson Standards Track [Page 1]\n\f\nRFC 5445 Basic FEC Schemes March 2009 5445 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5447","type":"specification","body":"IETF","designation":"RFC 5447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5447.txt","https://www.rfc-editor.org/rfc/rfc5447.pdf"],"folder":"IETF/RFC-5447","files":{"txt":{"path":"standards/IETF/RFC-5447/RFC-5447.txt","sha256":"2f9a668b39663304886c0d5b65b40731a582fcf87b582fe7d4945a0fe45a212c"}},"tags":["nested-reference","unchanged"],"summary":"A Mobile IPv6 node requires a home agent address, a home address, and\n a security association with its home agent before it can start\n utilizing Mobile IPv6. RFC 3775 requires that some or all of these\n parameters be statically configured. Mobile IPv6 bootstrapping work\n aims to make this information dynamically available to the mobile\n node. An important aspect of the Mobile IPv6 bootstrapping solution\n is to support interworking with existing Authentication,\n Authorization, and Accounting (AAA) infrastructures. This document\n describes MIPv6 bootstrapping using the Diameter Network Access\n Server to home AAA server interface.\n\nKorhonen, et al. Standards Track [Page 1]\n\f\nRFC 5447 Diameter MIPv6 NAS-to-HAAA Interaction February 2009","scope_keywords":["5447","attribute","authentication","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null}],"search_text":"IETF RFC 5447 A Mobile IPv6 node requires a home agent address, a home address, and\n a security association with its home agent before it can start\n utilizing Mobile IPv6. RFC 3775 requires that some or all of these\n parameters be statically configured. Mobile IPv6 bootstrapping work\n aims to make this information dynamically available to the mobile\n node. An important aspect of the Mobile IPv6 bootstrapping solution\n is to support interworking with existing Authentication,\n Authorization, and Accounting (AAA) infrastructures. This document\n describes MIPv6 bootstrapping using the Diameter Network Access\n Server to home AAA server interface.\n\nKorhonen, et al. Standards Track [Page 1]\n\f\nRFC 5447 Diameter MIPv6 NAS-to-HAAA Interaction February 2009 5447 attribute authentication authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5449","type":"specification","body":"IETF","designation":"RFC 5449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5449.txt","https://www.rfc-editor.org/rfc/rfc5449.pdf"],"folder":"IETF/RFC-5449","files":{"txt":{"path":"standards/IETF/RFC-5449/RFC-5449.txt","sha256":"b5d83e9945df8015d0f7dd3aebbe80c00e17bc88811932ba48ad76414fb5fd4c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an OSPFv3 interface type tailored for mobile\n ad hoc networks. This interface type is derived from the broadcast\n interface type, and is denoted the \"OSPFv3 MANET interface type\".\n\nBaccelli, et al. Experimental [Page 1]\n\f\nRFC 5449 OSPF MPR Extension for MANET February 2009","scope_keywords":["5449","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null}],"search_text":"IETF RFC 5449 This document specifies an OSPFv3 interface type tailored for mobile\n ad hoc networks. This interface type is derived from the broadcast\n interface type, and is denoted the \"OSPFv3 MANET interface type\".\n\nBaccelli, et al. Experimental [Page 1]\n\f\nRFC 5449 OSPF MPR Extension for MANET February 2009 5449 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5450","type":"specification","body":"IETF","designation":"RFC 5450","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5450.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5450.txt","https://www.rfc-editor.org/rfc/rfc5450.pdf"],"folder":"IETF/RFC-5450","files":{"txt":{"path":"standards/IETF/RFC-5450/RFC-5450.txt","sha256":"f0bddb657648d825737e97383a6c491deba0d75058f14e2976c62eab2039fa7f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method to inform Real-time Transport\n Protocol (RTP) clients when RTP packets are transmitted at a time\n other than their 'nominal' transmission time. It also provides a\n mechanism to provide improved inter-arrival jitter reports from the\n clients, that take into account the reported transmission times.\n\nSinger & Desineni Standards Track [Page 1]\n\f\nRFC 5450 RTP Transmission Offsets March 2009","scope_keywords":["5450","http","key","license","presentation","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 5450 This document describes a method to inform Real-time Transport\n Protocol (RTP) clients when RTP packets are transmitted at a time\n other than their 'nominal' transmission time. It also provides a\n mechanism to provide improved inter-arrival jitter reports from the\n clients, that take into account the reported transmission times.\n\nSinger & Desineni Standards Track [Page 1]\n\f\nRFC 5450 RTP Transmission Offsets March 2009 5450 http key license presentation subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5453","type":"specification","body":"IETF","designation":"RFC 5453","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5453.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5453.txt","https://www.rfc-editor.org/rfc/rfc5453.pdf"],"folder":"IETF/RFC-5453","files":{"txt":{"path":"standards/IETF/RFC-5453/RFC-5453.txt","sha256":"6e6be3f0ba6acd1650a17714c4f7673efe924f79a9ad197cb51c5a95c917e2e9"}},"tags":["nested-reference","unchanged"],"summary":"Interface identifiers in IPv6 unicast addresses are used to identify\n interfaces on a link. They are required to be unique within a\n subnet. Several RFCs have specified interface identifiers or\n identifier ranges that have a special meaning attached to them. An\n IPv6 node autoconfiguring an interface identifier in these ranges\n will encounter unexpected consequences. Since there is no\n centralized repository for such reserved identifiers, this document\n aims to create one.\n\nKrishnan Standards Track [Page 1]\n\f\nRFC 5453 Reserved IPv6 Interface Identifiers February 2009","scope_keywords":["5453","hash","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 5453 Interface identifiers in IPv6 unicast addresses are used to identify\n interfaces on a link. They are required to be unique within a\n subnet. Several RFCs have specified interface identifiers or\n identifier ranges that have a special meaning attached to them. An\n IPv6 node autoconfiguring an interface identifier in these ranges\n will encounter unexpected consequences. Since there is no\n centralized repository for such reserved identifiers, this document\n aims to create one.\n\nKrishnan Standards Track [Page 1]\n\f\nRFC 5453 Reserved IPv6 Interface Identifiers February 2009 5453 hash http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5460","type":"specification","body":"IETF","designation":"RFC 5460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5460.txt","https://www.rfc-editor.org/rfc/rfc5460.pdf"],"folder":"IETF/RFC-5460","files":{"txt":{"path":"standards/IETF/RFC-5460/RFC-5460.txt","sha256":"c9aa8f7162b32d5449f377f8274195c4122ea2199b074b59bc9a0d0d2105d162"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been\n extended with a Leasequery capability that allows a client to request\n information about DHCPv6 bindings. That mechanism is limited to\n queries for individual bindings. In some situations individual\n binding queries may not be efficient, or even possible. This\n document expands on the Leasequery protocol, adding new query types\n and allowing for bulk transfer of DHCPv6 binding data via TCP.\n\nStapp Standards Track [Page 1]\n\f\nRFC 5460 DHCPv6 Bulk Leasequery February 2009","scope_keywords":["5460","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6853","folder":"IETF/RFC-6853","source":"IETF/RFC-6853/RFC-6853.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7653","folder":"IETF/RFC-7653","source":"IETF/RFC-7653/RFC-7653.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 5460 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been\n extended with a Leasequery capability that allows a client to request\n information about DHCPv6 bindings. That mechanism is limited to\n queries for individual bindings. In some situations individual\n binding queries may not be efficient, or even possible. This\n document expands on the Leasequery protocol, adding new query types\n and allowing for bulk transfer of DHCPv6 binding data via TCP.\n\nStapp Standards Track [Page 1]\n\f\nRFC 5460 DHCPv6 Bulk Leasequery February 2009 5460 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5462","type":"specification","body":"IETF","designation":"RFC 5462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5462.txt","https://www.rfc-editor.org/rfc/rfc5462.pdf"],"folder":"IETF/RFC-5462","files":{"txt":{"path":"standards/IETF/RFC-5462/RFC-5462.txt","sha256":"4e6154ec58f83fa5a7c1a14584ad87804fecc69092ea8e87b57027bf9246cc58"}},"tags":["nested-reference","unchanged"],"summary":"The early Multiprotocol Label Switching (MPLS) documents defined the\n form of the MPLS label stack entry. This includes a three-bit field\n called the \"EXP field\". The exact use of this field was not defined\n by these documents, except to state that it was to be \"reserved for\n experimental use\".\n\n Although the intended use of the EXP field was as a \"Class of\n Service\" (CoS) field, it was not named a CoS field by these early\n documents because the use of such a CoS field was not considered to\n be sufficiently defined. Today a number of standards documents\n define its usage as a CoS field.\n\nAndersson & Asati Standards Track [Page 1]\n\f\nRFC 5462 MPLS TC Field Definition February 2009\n\n To avoid misunderstanding about how this field may be used, it has\n become increasingly necessary to rename this field. This document\n changes the name of the field to the \"Traffic Class field\" (\"TC\n field\"). I","scope_keywords":["5462","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 5462 The early Multiprotocol Label Switching (MPLS) documents defined the\n form of the MPLS label stack entry. This includes a three-bit field\n called the \"EXP field\". The exact use of this field was not defined\n by these documents, except to state that it was to be \"reserved for\n experimental use\".\n\n Although the intended use of the EXP field was as a \"Class of\n Service\" (CoS) field, it was not named a CoS field by these early\n documents because the use of such a CoS field was not considered to\n be sufficiently defined. Today a number of standards documents\n define its usage as a CoS field.\n\nAndersson & Asati Standards Track [Page 1]\n\f\nRFC 5462 MPLS TC Field Definition February 2009\n\n To avoid misunderstanding about how this field may be used, it has\n become increasingly necessary to rename this field. This document\n changes the name of the field to the \"Traffic Class field\" (\"TC\n field\"). I 5462 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5463","type":"specification","body":"IETF","designation":"RFC 5463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5463.txt","https://www.rfc-editor.org/rfc/rfc5463.pdf"],"folder":"IETF/RFC-5463","files":{"txt":{"path":"standards/IETF/RFC-5463/RFC-5463.txt","sha256":"cf28cb38109358d084800f41e8e2e3f7a9f7663cae7b039852226e291512d27e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"ihave\" extension to the Sieve email\n filtering language. The \"ihave\" extension provides a means to write\n scripts that can take advantage of optional Sieve features but can\n still run when those optional features are not available. The\n extension also defines a new error control command intended to be\n used to report situations where no combination of available\n extensions satisfies the needs of the script.\n\n1. Introduction\n\n Sieve [RFC5228] is a language for filtering email messages at or\n around the time of final delivery. It is designed to be\n implementable on either a mail client or mail server. It is suitable\n for running on a mail server where users may not be allowed to\n execute arbitrary programs, such as on black-box Internet Message\n Access Protocol [RFC3501] servers, as it has no user-controlled loops\n or the ability to run external programs.\n\nFree","scope_keywords":["5463","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null}],"search_text":"IETF RFC 5463 This document describes the \"ihave\" extension to the Sieve email\n filtering language. The \"ihave\" extension provides a means to write\n scripts that can take advantage of optional Sieve features but can\n still run when those optional features are not available. The\n extension also defines a new error control command intended to be\n used to report situations where no combination of available\n extensions satisfies the needs of the script.\n\n1. Introduction\n\n Sieve [RFC5228] is a language for filtering email messages at or\n around the time of final delivery. It is designed to be\n implementable on either a mail client or mail server. It is suitable\n for running on a mail server where users may not be allowed to\n execute arbitrary programs, such as on black-box Internet Message\n Access Protocol [RFC3501] servers, as it has no user-controlled loops\n or the ability to run external programs.\n\nFree 5463 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5464","type":"specification","body":"IETF","designation":"RFC 5464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5464.txt","https://www.rfc-editor.org/rfc/rfc5464.pdf"],"folder":"IETF/RFC-5464","files":{"txt":{"path":"standards/IETF/RFC-5464/RFC-5464.txt","sha256":"333cd797e53ed4ebce5bdbc908569e571448c0c34b03e11c0ed5617aca5297a5"}},"tags":["nested-reference","unchanged"],"summary":"The METADATA extension to the Internet Message Access Protocol\n permits clients and servers to maintain \"annotations\" or \"metadata\"\n on IMAP servers. It is possible to have annotations on a per-mailbox\n basis or on the server as a whole. For example, this would allow\n comments about the purpose of a particular mailbox to be \"attached\"\n to that mailbox, or a \"message of the day\" containing server status\n information to be made available to anyone logging in to the server.\n\nDaboo Standards Track [Page 1]\n\f\nRFC 5464 The IMAP METADATA Extension February 2009","scope_keywords":["5464","attribute","crl","key","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null}],"search_text":"IETF RFC 5464 The METADATA extension to the Internet Message Access Protocol\n permits clients and servers to maintain \"annotations\" or \"metadata\"\n on IMAP servers. It is possible to have annotations on a per-mailbox\n basis or on the server as a whole. For example, this would allow\n comments about the purpose of a particular mailbox to be \"attached\"\n to that mailbox, or a \"message of the day\" containing server status\n information to be made available to anyone logging in to the server.\n\nDaboo Standards Track [Page 1]\n\f\nRFC 5464 The IMAP METADATA Extension February 2009 5464 attribute crl key risk nested-reference unchanged"},{"id":"IETF RFC 5465","type":"specification","body":"IETF","designation":"RFC 5465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5465.txt","https://www.rfc-editor.org/rfc/rfc5465.pdf"],"folder":"IETF/RFC-5465","files":{"txt":{"path":"standards/IETF/RFC-5465/RFC-5465.txt","sha256":"8b5234a0791b69bb2ca0eca02644adc10d6c5199cb9e5934e6ddf6f5a64c8e76"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an IMAP extension that allows a client to\n request specific kinds of unsolicited notifications for specified\n mailboxes, such as messages being added to or deleted from such\n mailboxes.\n\nGulbrandsen, et al. Standards Track [Page 1]\n\f\nRFC 5465 IMAP NOTIFY Extension February 2009","scope_keywords":["5465","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5465 This document defines an IMAP extension that allows a client to\n request specific kinds of unsolicited notifications for specified\n mailboxes, such as messages being added to or deleted from such\n mailboxes.\n\nGulbrandsen, et al. Standards Track [Page 1]\n\f\nRFC 5465 IMAP NOTIFY Extension February 2009 5465 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5466","type":"specification","body":"IETF","designation":"RFC 5466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5466.txt","https://www.rfc-editor.org/rfc/rfc5466.pdf"],"folder":"IETF/RFC-5466","files":{"txt":{"path":"standards/IETF/RFC-5466/RFC-5466.txt","sha256":"707bbc1e653615dcf808b685e52d3f5072a158683c9ffa148ca497265ccf402e"}},"tags":["nested-reference","unchanged"],"summary":"The document defines a way to persistently store named IMAP (RFC\n 3501) searches on the server. Such named searches can be\n subsequently referenced in a SEARCH or any other command that accepts\n a search criterion as a parameter.","scope_keywords":["5466","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null}],"search_text":"IETF RFC 5466 The document defines a way to persistently store named IMAP (RFC\n 3501) searches on the server. Such named searches can be\n subsequently referenced in a SEARCH or any other command that accepts\n a search criterion as a parameter. 5466 http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5469","type":"specification","body":"IETF","designation":"RFC 5469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5469.txt","https://www.rfc-editor.org/rfc/rfc5469.pdf"],"folder":"IETF/RFC-5469","files":{"txt":{"path":"standards/IETF/RFC-5469/RFC-5469.txt","sha256":"41ff03084d550cd6bdc187712521e60e48f3171f56c8a9247ddb3211650bbaca"}},"tags":["nested-reference","unchanged"],"summary":"Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC\n 4346) include cipher suites based on DES (Data Encryption Standard)\n and IDEA (International Data Encryption Algorithm) algorithms. DES\n (when used in single-DES mode) and IDEA are no longer recommended for\n general use in TLS, and have been removed from TLS version 1.2 (RFC\n 5246). This document specifies these cipher suites for completeness\n and discusses reasons why their use is no longer recommended.\n\n1. Introduction\n\n TLS versions 1.0 [TLS10] and 1.1 [TLS11] include cipher suites based\n on DES (Data Encryption Standard) and IDEA (International Data\n Encryption Algorithm) algorithms. DES (when used in single-DES mode)\n and IDEA are no longer recommended for general use in TLS, and have\n been removed from TLS version 1.2 [TLS12].\n\n This document specifies these cipher suites for completeness and\n discusses reasons wh","scope_keywords":["5469","algorithm","algorithms","authentication","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5469 Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC\n 4346) include cipher suites based on DES (Data Encryption Standard)\n and IDEA (International Data Encryption Algorithm) algorithms. DES\n (when used in single-DES mode) and IDEA are no longer recommended for\n general use in TLS, and have been removed from TLS version 1.2 (RFC\n 5246). This document specifies these cipher suites for completeness\n and discusses reasons why their use is no longer recommended.\n\n1. Introduction\n\n TLS versions 1.0 [TLS10] and 1.1 [TLS11] include cipher suites based\n on DES (Data Encryption Standard) and IDEA (International Data\n Encryption Algorithm) algorithms. DES (when used in single-DES mode)\n and IDEA are no longer recommended for general use in TLS, and have\n been removed from TLS version 1.2 [TLS12].\n\n This document specifies these cipher suites for completeness and\n discusses reasons wh 5469 algorithm algorithms authentication encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5471","type":"specification","body":"IETF","designation":"RFC 5471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5471.txt","https://www.rfc-editor.org/rfc/rfc5471.pdf"],"folder":"IETF/RFC-5471","files":{"txt":{"path":"standards/IETF/RFC-5471/RFC-5471.txt","sha256":"cc14267e088513a29c7933241e7ec889353f496f8783e4531a1cfb60d993c023"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a list of tests for implementers of IP Flow\n Information eXport (IPFIX) compliant Exporting Processes and\n Collecting Processes. This document specifies guidelines for a\n series of tests that can be run on the IPFIX Exporting Process and\n Collecting Process in order to probe the conformity and robustness of\n the IPFIX protocol implementations. These tests cover all important\n functions, in order to gain a level of confidence in the IPFIX\n implementation. Therefore, they allow the implementer to perform\n interoperability or plug tests with other IPFIX Exporting Processes\n and Collecting Processes.","scope_keywords":["5471","authentication","conformity","http","key","keys","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null}],"search_text":"IETF RFC 5471 This document presents a list of tests for implementers of IP Flow\n Information eXport (IPFIX) compliant Exporting Processes and\n Collecting Processes. This document specifies guidelines for a\n series of tests that can be run on the IPFIX Exporting Process and\n Collecting Process in order to probe the conformity and robustness of\n the IPFIX protocol implementations. These tests cover all important\n functions, in order to gain a level of confidence in the IPFIX\n implementation. Therefore, they allow the implementer to perform\n interoperability or plug tests with other IPFIX Exporting Processes\n and Collecting Processes. 5471 authentication conformity http key keys license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5473","type":"specification","body":"IETF","designation":"RFC 5473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5473.txt","https://www.rfc-editor.org/rfc/rfc5473.pdf"],"folder":"IETF/RFC-5473","files":{"txt":{"path":"standards/IETF/RFC-5473/RFC-5473.txt","sha256":"b611df6490074bbab73264ce692ee356f6a1367471a6a19b3b8aeff16ad1cc95"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a bandwidth saving method for exporting Flow\n or packet information using the IP Flow Information eXport (IPFIX)\n protocol. As the Packet Sampling (PSAMP) protocol is based on IPFIX,\n these considerations are valid for PSAMP exports as well.\n\nBoschi, et al. Informational [Page 1]\n\f\nRFC 5473 Reducing Redundancy March 2009\n\n This method works by separating information common to several Flow\n Records from information specific to an individual Flow Record.\n Common Flow information is exported only once in a Data Record\n defined by an Options Template, while the rest of the specific Flow\n information is associated with the common information via a unique\n identifier.","scope_keywords":["5473","attribute","attributes","http","key","keys","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 5473 This document describes a bandwidth saving method for exporting Flow\n or packet information using the IP Flow Information eXport (IPFIX)\n protocol. As the Packet Sampling (PSAMP) protocol is based on IPFIX,\n these considerations are valid for PSAMP exports as well.\n\nBoschi, et al. Informational [Page 1]\n\f\nRFC 5473 Reducing Redundancy March 2009\n\n This method works by separating information common to several Flow\n Records from information specific to an individual Flow Record.\n Common Flow information is exported only once in a Data Record\n defined by an Options Template, while the rest of the specific Flow\n information is associated with the common information via a unique\n identifier. 5473 attribute attributes http key keys license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5476","type":"specification","body":"IETF","designation":"RFC 5476","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5476.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5476.txt","https://www.rfc-editor.org/rfc/rfc5476.pdf"],"folder":"IETF/RFC-5476","files":{"txt":{"path":"standards/IETF/RFC-5476/RFC-5476.txt","sha256":"d9d1494c0a1f1177360ebfda4fa0c53298d697b262253a47d087376679a62143"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the export of packet information from a\n Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting\n Process. For export of packet information, the IP Flow Information\n eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP\n architecture match very well, and the means provided by the IPFIX\n protocol are sufficient. The document specifies in detail how the\n IPFIX protocol is used for PSAMP export of packet information.","scope_keywords":["5476","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5475","folder":"IETF/RFC-5475","source":"IETF/RFC-5475/RFC-5475.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 5476 This document specifies the export of packet information from a\n Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting\n Process. For export of packet information, the IP Flow Information\n eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP\n architecture match very well, and the means provided by the IPFIX\n protocol are sufficient. The document specifies in detail how the\n IPFIX protocol is used for PSAMP export of packet information. 5476 hash http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5479","type":"specification","body":"IETF","designation":"RFC 5479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5479.txt","https://www.rfc-editor.org/rfc/rfc5479.pdf"],"folder":"IETF/RFC-5479","files":{"txt":{"path":"standards/IETF/RFC-5479/RFC-5479.txt","sha256":"febf70371be84dc6514e3b91df49b1a160dc1f48dba20225cb13bfea523a1dbc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes requirements for a protocol to negotiate a\n security context for SIP-signaled Secure RTP (SRTP) media. In\n addition to the natural security requirements, this negotiation\n protocol must interoperate well with SIP in certain ways. A number\n of proposals have been published and a summary of these proposals is\n in the appendix of this document.\n\nWing, et al. Informational [Page 1]\n\f\nRFC 5479 Media Security Requirements April 2009","scope_keywords":["5479","algorithm","algorithms","certificate","certificates","encryption","http","key","keys","license","management","path","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 6043","folder":"IETF/RFC-6043","source":"IETF/RFC-6043/RFC-6043.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null}],"search_text":"IETF RFC 5479 This document describes requirements for a protocol to negotiate a\n security context for SIP-signaled Secure RTP (SRTP) media. In\n addition to the natural security requirements, this negotiation\n protocol must interoperate well with SIP in certain ways. A number\n of proposals have been published and a summary of these proposals is\n in the appendix of this document.\n\nWing, et al. Informational [Page 1]\n\f\nRFC 5479 Media Security Requirements April 2009 5479 algorithm algorithms certificate certificates encryption http key keys license management path subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 5480","type":"specification","body":"IETF","designation":"RFC 5480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5480.txt","https://www.rfc-editor.org/rfc/rfc5480.pdf"],"folder":"IETF/RFC-5480","files":{"txt":{"path":"standards/IETF/RFC-5480/RFC-5480.txt","sha256":"593bf29fd0da2ff8b903c3ebf1c9d189a770039159e2ba46a0c3b91355037f26"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax and semantics for the Subject\n Public Key Information field in certificates that support Elliptic\n Curve Cryptography. This document updates Sections 2.3.5 and 5, and\n the ASN.1 module of \"Algorithms and Identifiers for the Internet\n X.509 Public Key Infrastructure Certificate and Certificate\n Revocation List (CRL) Profile\", RFC 3279.\n\nTurner, et al. Standards Track [Page 1]\n\f\nRFC 5480 ECC SubjectPublicKeyInfo Format March 2009","scope_keywords":["5480","algorithm","algorithms","certificate","certificates","crl","http","key","keys","license","pki","profile","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5758","folder":"IETF/RFC-5758","source":"IETF/RFC-5758/RFC-5758.txt","version":null},{"body":"IETF","designation":"RFC 5759","folder":"IETF/RFC-5759","source":"IETF/RFC-5759/RFC-5759.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 5480 This document specifies the syntax and semantics for the Subject\n Public Key Information field in certificates that support Elliptic\n Curve Cryptography. This document updates Sections 2.3.5 and 5, and\n the ASN.1 module of \"Algorithms and Identifiers for the Internet\n X.509 Public Key Infrastructure Certificate and Certificate\n Revocation List (CRL) Profile\", RFC 3279.\n\nTurner, et al. Standards Track [Page 1]\n\f\nRFC 5480 ECC SubjectPublicKeyInfo Format March 2009 5480 algorithm algorithms certificate certificates crl http key keys license pki profile revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5484","type":"specification","body":"IETF","designation":"RFC 5484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5484.txt","https://www.rfc-editor.org/rfc/rfc5484.pdf"],"folder":"IETF/RFC-5484","files":{"txt":{"path":"standards/IETF/RFC-5484/RFC-5484.txt","sha256":"4bfd92fcf69f985e9f8a383079b1c745b9268f86341e9d35105166bbd7febce7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for associating time-codes, as\n defined by the Society of Motion Picture and Television Engineers\n (SMPTE), with media streams in a way that is independent of the RTP\n payload format of the media stream itself.\n\nSinger Standards Track [Page 1]\n\f\nRFC 5484 RTP SMPTE Time-Codes March 2009","scope_keywords":["5484","http","key","license","presentation","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null}],"search_text":"IETF RFC 5484 This document describes a mechanism for associating time-codes, as\n defined by the Society of Motion Picture and Television Engineers\n (SMPTE), with media streams in a way that is independent of the RTP\n payload format of the media stream itself.\n\nSinger Standards Track [Page 1]\n\f\nRFC 5484 RTP SMPTE Time-Codes March 2009 5484 http key license presentation subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5485","type":"specification","body":"IETF","designation":"RFC 5485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5485.txt","https://www.rfc-editor.org/rfc/rfc5485.pdf"],"folder":"IETF/RFC-5485","files":{"txt":{"path":"standards/IETF/RFC-5485/RFC-5485.txt","sha256":"ed4df6bb70250f59265873a7741499f0688ecb5d806faa9bb8008a645068814e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for digital signatures on\n Internet-Drafts. The Cryptographic Message Syntax (CMS) is used to\n create a detached signature, which is stored in a separate companion\n file so that no existing utilities are impacted by the addition of\n the digital signature.\n\nHousley Informational [Page 1]\n\f\nRFC 5485 Digital Signatures on Internet-Drafts March 2009\n\n1. Introduction\n\n This document specifies the conventions for storing a digital\n signature on Internet-Drafts. The Cryptographic Message Syntax (CMS)\n [CMS] is used to create a detached signature. The signature is\n stored in a separate companion file so that no existing utilities are\n impacted by the addition of the digital signature.\n\n Shortly after the IETF Secretariat posts the Internet-Draft in the\n repository, the digital signature is generated and posted as a\n companion file in the same repository. T","scope_keywords":["5485","algorithm","crl","http","key","license","presentation","signature","signatures","subject","timestamp","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null}],"search_text":"IETF RFC 5485 This document specifies the conventions for digital signatures on\n Internet-Drafts. The Cryptographic Message Syntax (CMS) is used to\n create a detached signature, which is stored in a separate companion\n file so that no existing utilities are impacted by the addition of\n the digital signature.\n\nHousley Informational [Page 1]\n\f\nRFC 5485 Digital Signatures on Internet-Drafts March 2009\n\n1. Introduction\n\n This document specifies the conventions for storing a digital\n signature on Internet-Drafts. The Cryptographic Message Syntax (CMS)\n [CMS] is used to create a detached signature. The signature is\n stored in a separate companion file so that no existing utilities are\n impacted by the addition of the digital signature.\n\n Shortly after the IETF Secretariat posts the Internet-Draft in the\n repository, the digital signature is generated and posted as a\n companion file in the same repository. T 5485 algorithm crl http key license presentation signature signatures subject timestamp trust validation nested-reference unchanged"},{"id":"IETF RFC 5491","type":"specification","body":"IETF","designation":"RFC 5491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5491.txt","https://www.rfc-editor.org/rfc/rfc5491.pdf"],"folder":"IETF/RFC-5491","files":{"txt":{"path":"standards/IETF/RFC-5491/RFC-5491.txt","sha256":"877213d85126d61b59298174742f04f778d1a7df6b3fe96cedadebee1d5ed557"}},"tags":["nested-reference","unchanged"],"summary":"The Presence Information Data Format Location Object (PIDF-LO)\n specification provides a flexible and versatile means to represent\n location information. There are, however, circumstances that arise\n when information needs to be constrained in how it is represented.\n In these circumstances, the range of options that need to be\n implemented are reduced. There is growing interest in being able to\n use location information contained in a PIDF-LO for routing\n applications. To allow successful interoperability between\n applications, location information needs to be normative and more\n tightly constrained than is currently specified in RFC 4119 (PIDF-\n LO). This document makes recommendations on how to constrain,\n represent, and interpret locations in a PIDF-LO. It further\n recommends a subset of Geography Markup Language (GML) 3.1.1 that is\n mandatory to implement by applications involved in ","scope_keywords":["5491","http","key","license","pid","policies","presentation","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5687","folder":"IETF/RFC-5687","source":"IETF/RFC-5687/RFC-5687.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 5491 The Presence Information Data Format Location Object (PIDF-LO)\n specification provides a flexible and versatile means to represent\n location information. There are, however, circumstances that arise\n when information needs to be constrained in how it is represented.\n In these circumstances, the range of options that need to be\n implemented are reduced. There is growing interest in being able to\n use location information contained in a PIDF-LO for routing\n applications. To allow successful interoperability between\n applications, location information needs to be normative and more\n tightly constrained than is currently specified in RFC 4119 (PIDF-\n LO). This document makes recommendations on how to constrain,\n represent, and interpret locations in a PIDF-LO. It further\n recommends a subset of Geography Markup Language (GML) 3.1.1 that is\n mandatory to implement by applications involved in  5491 http key license pid policies presentation profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5492","type":"specification","body":"IETF","designation":"RFC 5492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5492.txt","https://www.rfc-editor.org/rfc/rfc5492.pdf"],"folder":"IETF/RFC-5492","files":{"txt":{"path":"standards/IETF/RFC-5492/RFC-5492.txt","sha256":"adf102acf55b059a233989d09204fad1a6608f5d4ba362cbda1de479fdae4796"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Optional Parameter, called Capabilities,\n that is expected to facilitate the introduction of new capabilities\n in the Border Gateway Protocol (BGP) by providing graceful capability\n advertisement without requiring that BGP peering be terminated.\n\n This document obsoletes RFC 3392.\n\nScudder & Chandra Standards Track [Page 1]\n\f\nRFC 5492 Capabilities Advertisement February 2009\n\n1. Introduction\n\n The base BGP-4 specification [RFC4271] requires that when a BGP\n speaker receives an OPEN message with one or more unrecognized\n Optional Parameters, the speaker must terminate the BGP peering.\n This complicates the introduction of new capabilities in BGP.\n\n This specification defines an Optional Parameter and processing rules\n that allow BGP speakers to communicate capabilities in an OPEN\n message. A pair of BGP speakers that supports this specification can\n establish the ","scope_keywords":["5492","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null}],"search_text":"IETF RFC 5492 This document defines an Optional Parameter, called Capabilities,\n that is expected to facilitate the introduction of new capabilities\n in the Border Gateway Protocol (BGP) by providing graceful capability\n advertisement without requiring that BGP peering be terminated.\n\n This document obsoletes RFC 3392.\n\nScudder & Chandra Standards Track [Page 1]\n\f\nRFC 5492 Capabilities Advertisement February 2009\n\n1. Introduction\n\n The base BGP-4 specification [RFC4271] requires that when a BGP\n speaker receives an OPEN message with one or more unrecognized\n Optional Parameters, the speaker must terminate the BGP peering.\n This complicates the introduction of new capabilities in BGP.\n\n This specification defines an Optional Parameter and processing rules\n that allow BGP speakers to communicate capabilities in an OPEN\n message. A pair of BGP speakers that supports this specification can\n establish the  5492 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5496","type":"specification","body":"IETF","designation":"RFC 5496","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5496.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5496.txt","https://www.rfc-editor.org/rfc/rfc5496.pdf"],"folder":"IETF/RFC-5496","files":{"txt":{"path":"standards/IETF/RFC-5496/RFC-5496.txt","sha256":"5841020bef303c9a9ee37f550c179618ad8405f1bcad8688781f437c97c6340e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a use of the Protocol Independent Multicast\n (PIM) Join Attribute as defined in RFC 5384, which enables PIM to\n build multicast trees through an MPLS-enabled network, even if that\n network's IGP does not have a route to the source of the tree.\n\nWijnands, et al. Standards Track [Page 1]\n\f\nRFC 5496 The RPF Vector TLV March 2009","scope_keywords":["5496","attribute","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null}],"search_text":"IETF RFC 5496 This document describes a use of the Protocol Independent Multicast\n (PIM) Join Attribute as defined in RFC 5384, which enables PIM to\n build multicast trees through an MPLS-enabled network, even if that\n network's IGP does not have a route to the source of the tree.\n\nWijnands, et al. Standards Track [Page 1]\n\f\nRFC 5496 The RPF Vector TLV March 2009 5496 attribute http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5497","type":"specification","body":"IETF","designation":"RFC 5497","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5497.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5497.txt","https://www.rfc-editor.org/rfc/rfc5497.pdf"],"folder":"IETF/RFC-5497","files":{"txt":{"path":"standards/IETF/RFC-5497/RFC-5497.txt","sha256":"5c4d63d8029095106a7f2dba09531287688efeb2623e341231f5510b779d52c6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a general and flexible TLV (type-length-value\n structure) for representing time-values, such as an interval or a\n duration, using the generalized Mobile Ad hoc NETwork (MANET) packet/\n message format. It defines two Message TLVs and two Address Block\n TLVs for representing validity and interval times for MANET routing\n protocols.\n\nClausen & Dearlove Standards Track [Page 1]\n\f\nRFC 5497 Time TLV March 2009","scope_keywords":["5497","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null}],"search_text":"IETF RFC 5497 This document describes a general and flexible TLV (type-length-value\n structure) for representing time-values, such as an interval or a\n duration, using the generalized Mobile Ad hoc NETwork (MANET) packet/\n message format. It defines two Message TLVs and two Address Block\n TLVs for representing validity and interval times for MANET routing\n protocols.\n\nClausen & Dearlove Standards Track [Page 1]\n\f\nRFC 5497 Time TLV March 2009 5497 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5498","type":"specification","body":"IETF","designation":"RFC 5498","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5498.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5498.txt","https://www.rfc-editor.org/rfc/rfc5498.pdf"],"folder":"IETF/RFC-5498","files":{"txt":{"path":"standards/IETF/RFC-5498/RFC-5498.txt","sha256":"ea26e9dde204a4a9e17f11103d9cc31daf2181d6f4e8616a72a91ab5fecda69f"}},"tags":["nested-reference","unchanged"],"summary":"This document enumerates several common IANA allocations for use by\n Mobile Ad hoc NETwork (MANET) protocols. The following well-known\n numbers are required: a UDP port number, an IP protocol number, and a\n link-local multicast group address.\n\nChakeres Standards Track [Page 1]\n\f\nRFC 5498 IANA Allocations for MANET Protocols March 2009","scope_keywords":["5498","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6130","folder":"IETF/RFC-6130","source":"IETF/RFC-6130/RFC-6130.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null}],"search_text":"IETF RFC 5498 This document enumerates several common IANA allocations for use by\n Mobile Ad hoc NETwork (MANET) protocols. The following well-known\n numbers are required: a UDP port number, an IP protocol number, and a\n link-local multicast group address.\n\nChakeres Standards Track [Page 1]\n\f\nRFC 5498 IANA Allocations for MANET Protocols March 2009 5498 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5506","type":"specification","body":"IETF","designation":"RFC 5506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5506.txt","https://www.rfc-editor.org/rfc/rfc5506.pdf"],"folder":"IETF/RFC-5506","files":{"txt":{"path":"standards/IETF/RFC-5506/RFC-5506.txt","sha256":"355b211e298975ae0eff263260e9d202f0cb56482f12f0a68c976f81e06382e9"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses benefits and issues that arise when allowing\n Real-time Transport Protocol (RTCP) packets to be transmitted with\n reduced size. The size can be reduced if the rules on how to create\n compound packets outlined in RFC 3550 are removed or changed. Based\n on that analysis, this memo defines certain changes to the rules to\n allow feedback messages to be sent as Reduced-Size RTCP packets under\n certain conditions when using the RTP/AVPF (Real-time Transport\n Protocol / Audio-Visual Profile with Feedback) profile (RFC 4585).\n This document updates RFC 3550, RFC 3711, and RFC 4585.","scope_keywords":["5506","algorithm","authentication","delivery","encryption","http","key","license","profile","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5506 This memo discusses benefits and issues that arise when allowing\n Real-time Transport Protocol (RTCP) packets to be transmitted with\n reduced size. The size can be reduced if the rules on how to create\n compound packets outlined in RFC 3550 are removed or changed. Based\n on that analysis, this memo defines certain changes to the rules to\n allow feedback messages to be sent as Reduced-Size RTCP packets under\n certain conditions when using the RTP/AVPF (Real-time Transport\n Protocol / Audio-Visual Profile with Feedback) profile (RFC 4585).\n This document updates RFC 3550, RFC 3711, and RFC 4585. 5506 algorithm authentication delivery encryption http key license profile subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5509","type":"specification","body":"IETF","designation":"RFC 5509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5509.txt","https://www.rfc-editor.org/rfc/rfc5509.pdf"],"folder":"IETF/RFC-5509","files":{"txt":{"path":"standards/IETF/RFC-5509/RFC-5509.txt","sha256":"233f2f2f5da9373fceb6911bcc6eb4e862946c1467627b3c1301513bfa63c17a"}},"tags":["nested-reference","unchanged"],"summary":"This document registers with IANA two new DNS SRV protocol labels for\n resolving Instant Messaging and Presence services with SIP.\n\nLoreto Standards Track [Page 1]\n\f\nRFC 5509 IANA SRV Label for SIP April 2009","scope_keywords":["5509","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 5509 This document registers with IANA two new DNS SRV protocol labels for\n resolving Instant Messaging and Presence services with SIP.\n\nLoreto Standards Track [Page 1]\n\f\nRFC 5509 IANA SRV Label for SIP April 2009 5509 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5511","type":"specification","body":"IETF","designation":"RFC 5511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5511.txt","https://www.rfc-editor.org/rfc/rfc5511.pdf"],"folder":"IETF/RFC-5511","files":{"txt":{"path":"standards/IETF/RFC-5511/RFC-5511.txt","sha256":"cc089a505891b7991c633e928dd655a96ebaddf66b4659a348bee147faf85fdd"}},"tags":["nested-reference","unchanged"],"summary":"Several protocols have been specified in the Routing Area of the IETF\n using a common variant of the Backus-Naur Form (BNF) of representing\n message syntax. However, there is no formal definition of this\n version of BNF.\n\n There is value in using the same variant of BNF for the set of\n protocols that are commonly used together. This reduces confusion\n and simplifies implementation.\n\n Updating existing documents to use some other variant of BNF that is\n already formally documented would be a substantial piece of work.\n\n This document provides a formal definition of the variant of BNF that\n has been used (that we call Routing BNF) and makes it available for\n use by new protocols.","scope_keywords":["5511","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null}],"search_text":"IETF RFC 5511 Several protocols have been specified in the Routing Area of the IETF\n using a common variant of the Backus-Naur Form (BNF) of representing\n message syntax. However, there is no formal definition of this\n version of BNF.\n\n There is value in using the same variant of BNF for the set of\n protocols that are commonly used together. This reduces confusion\n and simplifies implementation.\n\n Updating existing documents to use some other variant of BNF that is\n already formally documented would be a substantial piece of work.\n\n This document provides a formal definition of the variant of BNF that\n has been used (that we call Routing BNF) and makes it available for\n use by new protocols. 5511 http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5528","type":"specification","body":"IETF","designation":"RFC 5528","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5528.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5528.txt","https://www.rfc-editor.org/rfc/rfc5528.pdf"],"folder":"IETF/RFC-5528","files":{"txt":{"path":"standards/IETF/RFC-5528/RFC-5528.txt","sha256":"3477959e97dcadfdd78abfd106f3e9bd94dd4a40bdec279b77d84e89e83760b9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the algorithms and presents test vectors for\n the Camellia block cipher algorithm in Counter mode (CTR) and Counter\n with Cipher Block Chaining MAC mode (CCM). The purpose of this\n document is to make the Camellia-CTR and Camellia-CCM algorithm\n conveniently available to the Internet Community.\n\nKato, et al. Informational [Page 1]\n\f\nRFC 5528 Camellia-CTR and Camellia-CCM algorithms April 2009","scope_keywords":["5528","algorithm","algorithms","delivery","encryption","http","key","keys","license","signature","signatures","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 6054","folder":"IETF/RFC-6054","source":"IETF/RFC-6054/RFC-6054.txt","version":null}],"search_text":"IETF RFC 5528 This document describes the algorithms and presents test vectors for\n the Camellia block cipher algorithm in Counter mode (CTR) and Counter\n with Cipher Block Chaining MAC mode (CCM). The purpose of this\n document is to make the Camellia-CTR and Camellia-CCM algorithm\n conveniently available to the Internet Community.\n\nKato, et al. Informational [Page 1]\n\f\nRFC 5528 Camellia-CTR and Camellia-CCM algorithms April 2009 5528 algorithm algorithms delivery encryption http key keys license signature signatures subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5529","type":"specification","body":"IETF","designation":"RFC 5529","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5529.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5529.txt","https://www.rfc-editor.org/rfc/rfc5529.pdf"],"folder":"IETF/RFC-5529","files":{"txt":{"path":"standards/IETF/RFC-5529/RFC-5529.txt","sha256":"6a8e197a19c385161a20f113f8c0d2b26984968e6f3a9e023dfd02c9545d66d7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining (CBC) mode, Counter (CTR) mode,\n and Counter with CBC-MAC (CCM) mode as additional, optional-to-\n implement Internet Key Exchange Protocol version 2 (IKEv2) and\n Encapsulating Security Payload (ESP) mechanisms to provide\n confidentiality, data origin authentication, and connectionless\n integrity.\n\nKato, et al. Standards Track [Page 1]\n\f\nRFC 5529 Modes of Operation for Camellia for IPsec April 2009","scope_keywords":["5529","algorithm","algorithms","attribute","authentication","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5529 This document describes the use of the Camellia block cipher\n algorithm in Cipher Block Chaining (CBC) mode, Counter (CTR) mode,\n and Counter with CBC-MAC (CCM) mode as additional, optional-to-\n implement Internet Key Exchange Protocol version 2 (IKEv2) and\n Encapsulating Security Payload (ESP) mechanisms to provide\n confidentiality, data origin authentication, and connectionless\n integrity.\n\nKato, et al. Standards Track [Page 1]\n\f\nRFC 5529 Modes of Operation for Camellia for IPsec April 2009 5529 algorithm algorithms attribute authentication http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5533","type":"specification","body":"IETF","designation":"RFC 5533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5533.txt","https://www.rfc-editor.org/rfc/rfc5533.pdf"],"folder":"IETF/RFC-5533","files":{"txt":{"path":"standards/IETF/RFC-5533/RFC-5533.txt","sha256":"8454c5ed55ce8183f34e7fe42031d95a98d034286c2c3fd123afe944e3bea875"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Shim6 protocol, a layer 3 shim for\n providing locator agility below the transport protocols, so that\n multihoming can be provided for IPv6 with failover and load-sharing\n properties, without assuming that a multihomed site will have a\n provider-independent IPv6 address prefix announced in the global IPv6\n routing table. The hosts in a site that has multiple provider-\n allocated IPv6 address prefixes will use the Shim6 protocol specified\n in this document to set up state with peer hosts so that the state\n can later be used to failover to a different locator pair, should the\n original one stop working.\n\nNordmark & Bagnulo Standards Track [Page 1]\n\f\nRFC 5533 Shim6 Protocol June 2009","scope_keywords":["5533","http","license","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5534","folder":"IETF/RFC-5534","source":"IETF/RFC-5534/RFC-5534.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 5533 This document defines the Shim6 protocol, a layer 3 shim for\n providing locator agility below the transport protocols, so that\n multihoming can be provided for IPv6 with failover and load-sharing\n properties, without assuming that a multihomed site will have a\n provider-independent IPv6 address prefix announced in the global IPv6\n routing table. The hosts in a site that has multiple provider-\n allocated IPv6 address prefixes will use the Shim6 protocol specified\n in this document to set up state with peer hosts so that the state\n can later be used to failover to a different locator pair, should the\n original one stop working.\n\nNordmark & Bagnulo Standards Track [Page 1]\n\f\nRFC 5533 Shim6 Protocol June 2009 5533 http license signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5535","type":"specification","body":"IETF","designation":"RFC 5535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5535.txt","https://www.rfc-editor.org/rfc/rfc5535.pdf"],"folder":"IETF/RFC-5535","files":{"txt":{"path":"standards/IETF/RFC-5535/RFC-5535.txt","sha256":"41e39235d8c7137d8fd1503936fa187981071b8795a5f3dc6b671c7abc3162da"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a mechanism to provide a secure binding between\n the multiple addresses with different prefixes available to a host\n within a multihomed site. This mechanism employs either\n Cryptographically Generated Addresses (CGAs) or a new variant of the\n same theme that uses the same format in the addresses. The main idea\n in the new variant is that information about the multiple prefixes is\n included within the addresses themselves. This is achieved by\n generating the interface identifiers of the addresses of a host as\n\nBagnulo Standards Track [Page 1]\n\f\nRFC 5535 HBA June 2009\n\n hashes of the available prefixes and a random number. Then, the\n multiple addresses are generated by prepending the different prefixes\n to the generated interface identifiers. The result is a set of\n addresses, called Hash-Based Addresses (HBAs), that are inherently\n bound to each other.","scope_keywords":["5535","hash","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5533","folder":"IETF/RFC-5533","source":"IETF/RFC-5533/RFC-5533.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 5535 This memo describes a mechanism to provide a secure binding between\n the multiple addresses with different prefixes available to a host\n within a multihomed site. This mechanism employs either\n Cryptographically Generated Addresses (CGAs) or a new variant of the\n same theme that uses the same format in the addresses. The main idea\n in the new variant is that information about the multiple prefixes is\n included within the addresses themselves. This is achieved by\n generating the interface identifiers of the addresses of a host as\n\nBagnulo Standards Track [Page 1]\n\f\nRFC 5535 HBA June 2009\n\n hashes of the available prefixes and a random number. Then, the\n multiple addresses are generated by prepending the different prefixes\n to the generated interface identifiers. The result is a set of\n addresses, called Hash-Based Addresses (HBAs), that are inherently\n bound to each other. 5535 hash http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5539","type":"specification","body":"IETF","designation":"RFC 5539","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5539.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5539.txt","https://www.rfc-editor.org/rfc/rfc5539.pdf"],"folder":"IETF/RFC-5539","files":{"txt":{"path":"standards/IETF/RFC-5539/RFC-5539.txt","sha256":"b35324d327fa987a99d8620958195dfb7ad3a6f3156d8ed19ea6a7964753226a"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) provides mechanisms to\n install, manipulate, and delete the configuration of network devices.\n This document describes how to use the Transport Layer Security (TLS)\n protocol to secure NETCONF exchanges.\n\nBadra Standards Track [Page 1]\n\f\nRFC 5539 NETCONF over TLS May 2009","scope_keywords":["5539","attribute","authentication","certificate","delivery","http","identification","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null}],"search_text":"IETF RFC 5539 The Network Configuration Protocol (NETCONF) provides mechanisms to\n install, manipulate, and delete the configuration of network devices.\n This document describes how to use the Transport Layer Security (TLS)\n protocol to secure NETCONF exchanges.\n\nBadra Standards Track [Page 1]\n\f\nRFC 5539 NETCONF over TLS May 2009 5539 attribute authentication certificate delivery http identification key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5542","type":"specification","body":"IETF","designation":"RFC 5542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5542.txt","https://www.rfc-editor.org/rfc/rfc5542.pdf"],"folder":"IETF/RFC-5542","files":{"txt":{"path":"standards/IETF/RFC-5542/RFC-5542.txt","sha256":"32825e606b2e5efd2c9286d4ffabd34d967fff84427f5d2a9aa849ac5fb03c49"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) module that\n contains textual conventions (TCs) to represent commonly used\n pseudowire (PW) management information. The intent is that these TCs\n will be imported and used in PW-related MIB modules that would\n otherwise define their own representations.","scope_keywords":["5542","holder","http","key","license","management","pid","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null}],"search_text":"IETF RFC 5542 This memo defines a Management Information Base (MIB) module that\n contains textual conventions (TCs) to represent commonly used\n pseudowire (PW) management information. The intent is that these TCs\n will be imported and used in PW-related MIB modules that would\n otherwise define their own representations. 5542 holder http key license management pid presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5543","type":"specification","body":"IETF","designation":"RFC 5543","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5543.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5543.txt","https://www.rfc-editor.org/rfc/rfc5543.pdf"],"folder":"IETF/RFC-5543","files":{"txt":{"path":"standards/IETF/RFC-5543/RFC-5543.txt","sha256":"83e977c40aaa60054385a21155c9be654785fb05c0a8b205ad1f5537ab2e6701"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new BGP attribute, the Traffic Engineering\n attribute, that enables BGP to carry Traffic Engineering information.\n\n The scope and applicability of this attribute currently excludes its\n use for non-VPN reachability information.\n\nOuld-Brahim, et al. Standards Track [Page 1]\n\f\nRFC 5543 BGP TE Attribute May 2009\n\n1. Introduction\n\n In certain cases (e.g., Layer-1 VPNs (L1VPNs) [RFC5195]), it may be\n useful to augment the VPN reachability information carried in BGP\n with Traffic Engineering information.\n\n This document defines a new BGP attribute, the Traffic Engineering\n attribute, that enables BGP [RFC4271] to carry Traffic Engineering\n information.\n\n Section 4 of [RFC5195] describes one possible usage of this\n attribute.\n\n The scope and applicability of this attribute currently excludes its\n use for non-VPN reachability information.\n\n Procedures for modifying the Tr","scope_keywords":["5543","attribute","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 5543 This document defines a new BGP attribute, the Traffic Engineering\n attribute, that enables BGP to carry Traffic Engineering information.\n\n The scope and applicability of this attribute currently excludes its\n use for non-VPN reachability information.\n\nOuld-Brahim, et al. Standards Track [Page 1]\n\f\nRFC 5543 BGP TE Attribute May 2009\n\n1. Introduction\n\n In certain cases (e.g., Layer-1 VPNs (L1VPNs) [RFC5195]), it may be\n useful to augment the VPN reachability information carried in BGP\n with Traffic Engineering information.\n\n This document defines a new BGP attribute, the Traffic Engineering\n attribute, that enables BGP [RFC4271] to carry Traffic Engineering\n information.\n\n Section 4 of [RFC5195] describes one possible usage of this\n attribute.\n\n The scope and applicability of this attribute currently excludes its\n use for non-VPN reachability information.\n\n Procedures for modifying the Tr 5543 attribute http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5546","type":"specification","body":"IETF","designation":"RFC 5546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5546.txt","https://www.rfc-editor.org/rfc/rfc5546.pdf"],"folder":"IETF/RFC-5546","files":{"txt":{"path":"standards/IETF/RFC-5546/RFC-5546.txt","sha256":"a7aad5fd02f4e226e09f5092f0e985131c66af530400b097a6c35bbba01b558a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol that uses the iCalendar object\n specification to provide scheduling interoperability between\n different calendaring systems. This is done without reference to a\n specific transport protocol so as to allow multiple methods of\n communication between systems. Subsequent documents will define\n profiles of this protocol that use specific, interoperable methods of\n communication between systems.\n\n The iCalendar Transport-Independent Interoperability Protocol (iTIP)\n complements the iCalendar object specification by adding semantics\n for group scheduling methods commonly available in current\n calendaring systems. These scheduling methods permit two or more\n calendaring systems to perform transactions such as publishing,\n scheduling, rescheduling, responding to scheduling requests,\n negotiating changes, or canceling.\n\nStatus of This Memo\n\n This document specifi","scope_keywords":["5546","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null}],"search_text":"IETF RFC 5546 This document specifies a protocol that uses the iCalendar object\n specification to provide scheduling interoperability between\n different calendaring systems. This is done without reference to a\n specific transport protocol so as to allow multiple methods of\n communication between systems. Subsequent documents will define\n profiles of this protocol that use specific, interoperable methods of\n communication between systems.\n\n The iCalendar Transport-Independent Interoperability Protocol (iTIP)\n complements the iCalendar object specification by adding semantics\n for group scheduling methods commonly available in current\n calendaring systems. These scheduling methods permit two or more\n calendaring systems to perform transactions such as publishing,\n scheduling, rescheduling, responding to scheduling requests,\n negotiating changes, or canceling.\n\nStatus of This Memo\n\n This document specifi 5546 http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5549","type":"specification","body":"IETF","designation":"RFC 5549","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5549.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5549.txt","https://www.rfc-editor.org/rfc/rfc5549.pdf"],"folder":"IETF/RFC-5549","files":{"txt":{"path":"standards/IETF/RFC-5549/RFC-5549.txt","sha256":"b1380e13df7da55e2b846fef35b3722c1a7278e50c6c257781937b27fae82ab6"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol BGP (MP-BGP) specifies that the set of network-layer\n protocols to which the address carried in the Next Hop field may\n belong is determined by the Address Family Identifier (AFI) and the\n Subsequent Address Family Identifier (SAFI). The current AFI/SAFI\n definitions for the IPv4 address family only have provisions for\n advertising a Next Hop address that belongs to the IPv4 protocol when\n advertising IPv4 Network Layer Reachability Information (NLRI) or\n VPN-IPv4 NLRI. This document specifies the extensions necessary to\n allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address\n that belongs to the IPv6 protocol. This comprises an extension of\n the AFI/SAFI definitions to allow the address of the Next Hop for\n IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, the\n encoding of the Next Hop in order to determine which of the protocols\n the address ac","scope_keywords":["5549","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 5549 Multiprotocol BGP (MP-BGP) specifies that the set of network-layer\n protocols to which the address carried in the Next Hop field may\n belong is determined by the Address Family Identifier (AFI) and the\n Subsequent Address Family Identifier (SAFI). The current AFI/SAFI\n definitions for the IPv4 address family only have provisions for\n advertising a Next Hop address that belongs to the IPv4 protocol when\n advertising IPv4 Network Layer Reachability Information (NLRI) or\n VPN-IPv4 NLRI. This document specifies the extensions necessary to\n allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address\n that belongs to the IPv6 protocol. This comprises an extension of\n the AFI/SAFI definitions to allow the address of the Next Hop for\n IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, the\n encoding of the Next Hop in order to determine which of the protocols\n the address ac 5549 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5554","type":"specification","body":"IETF","designation":"RFC 5554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5554.txt","https://www.rfc-editor.org/rfc/rfc5554.pdf"],"folder":"IETF/RFC-5554","files":{"txt":{"path":"standards/IETF/RFC-5554/RFC-5554.txt","sha256":"437822e69f768626295c7c81b46967b8979728f528ad779108b528314f63d87f"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies and generalizes the Generic Security Service\n Application Programming Interface (GSS-API) \"channel bindings\"\n facility, and imposes requirements on future GSS-API mechanisms and\n programming language bindings of the GSS-API.","scope_keywords":["5554","hash","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null}],"search_text":"IETF RFC 5554 This document clarifies and generalizes the Generic Security Service\n Application Programming Interface (GSS-API) \"channel bindings\"\n facility, and imposes requirements on future GSS-API mechanisms and\n programming language bindings of the GSS-API. 5554 hash http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5555","type":"specification","body":"IETF","designation":"RFC 5555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5555.txt","https://www.rfc-editor.org/rfc/rfc5555.pdf"],"folder":"IETF/RFC-5555","files":{"txt":{"path":"standards/IETF/RFC-5555/RFC-5555.txt","sha256":"c32a07f80b87fc2afada5592867194a74dfbf8f53dd54b32685d42c73aaffea4"}},"tags":["nested-reference","unchanged"],"summary":"The current Mobile IPv6 and Network Mobility (NEMO) specifications\n support IPv6 only. This specification extends those standards to\n allow the registration of IPv4 addresses and prefixes, respectively,\n and the transport of both IPv4 and IPv6 packets over the tunnel to\n the home agent. This specification also allows the mobile node to\n roam over both IPv6 and IPv4, including the case where Network\n Address Translation is present on the path between the mobile node\n and its home agent.\n\nSoliman Standards Track [Page 1]\n\f\nRFC 5555 DSMIPv6 June 2009","scope_keywords":["5555","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5568","folder":"IETF/RFC-5568","source":"IETF/RFC-5568/RFC-5568.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5555 The current Mobile IPv6 and Network Mobility (NEMO) specifications\n support IPv6 only. This specification extends those standards to\n allow the registration of IPv4 addresses and prefixes, respectively,\n and the transport of both IPv4 and IPv6 packets over the tunnel to\n the home agent. This specification also allows the mobile node to\n roam over both IPv6 and IPv4, including the case where Network\n Address Translation is present on the path between the mobile node\n and its home agent.\n\nSoliman Standards Track [Page 1]\n\f\nRFC 5555 DSMIPv6 June 2009 5555 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5560","type":"specification","body":"IETF","designation":"RFC 5560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5560.txt","https://www.rfc-editor.org/rfc/rfc5560.pdf"],"folder":"IETF/RFC-5560","files":{"txt":{"path":"standards/IETF/RFC-5560/RFC-5560.txt","sha256":"658595f58c1d38dab78d24e8ce5fea59d0d9334e34be85f4c07c51717140a4bc"}},"tags":["nested-reference","unchanged"],"summary":"When a packet is sent from one host to the other, one normally\n expects that exactly one copy of the packet that was sent arrives at\n the destination. It is, however, possible that a packet is either\n lost or that multiple copies arrive.\n\n In earlier work, a metric for packet loss was defined. This metric\n quantifies the case where a packet that is sent does not arrive at\n its destination within a reasonable time. In this memo, a metric for\n another case is defined: a packet is sent, but multiple copies\n arrive. The document also discusses streams and methods to summarize\n the results of streams.\n\nUijterwaal Standards Track [Page 1]\n\f\nRFC 5560 Packet Duplication Metric May 2009","scope_keywords":["5560","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5560 When a packet is sent from one host to the other, one normally\n expects that exactly one copy of the packet that was sent arrives at\n the destination. It is, however, possible that a packet is either\n lost or that multiple copies arrive.\n\n In earlier work, a metric for packet loss was defined. This metric\n quantifies the case where a packet that is sent does not arrive at\n its destination within a reasonable time. In this memo, a metric for\n another case is defined: a packet is sent, but multiple copies\n arrive. The document also discusses streams and methods to summarize\n the results of streams.\n\nUijterwaal Standards Track [Page 1]\n\f\nRFC 5560 Packet Duplication Metric May 2009 5560 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5561","type":"specification","body":"IETF","designation":"RFC 5561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5561.txt","https://www.rfc-editor.org/rfc/rfc5561.pdf"],"folder":"IETF/RFC-5561","files":{"txt":{"path":"standards/IETF/RFC-5561/RFC-5561.txt","sha256":"a85dc56cfd379395ad051cc321694aa5c9a92aaffa67f37faa60d885c7efedec"}},"tags":["nested-reference","unchanged"],"summary":"A number of enhancements to the Label Distribution Protocol (LDP)\n have been proposed. Some have been implemented, and some are\n advancing toward standardization. It is likely that additional\n enhancements will be proposed in the future. This document defines a\n mechanism for advertising LDP enhancements at session initialization\n time, as well as a mechanism to enable and disable enhancements after\n LDP session establishment.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All","scope_keywords":["5561","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null},{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null}],"search_text":"IETF RFC 5561 A number of enhancements to the Label Distribution Protocol (LDP)\n have been proposed. Some have been implemented, and some are\n advancing toward standardization. It is likely that additional\n enhancements will be proposed in the future. This document defines a\n mechanism for advertising LDP enhancements at session initialization\n time, as well as a mechanism to enable and disable enhancements after\n LDP session establishment.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All 5561 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5562","type":"specification","body":"IETF","designation":"RFC 5562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5562.txt","https://www.rfc-editor.org/rfc/rfc5562.pdf"],"folder":"IETF/RFC-5562","files":{"txt":{"path":"standards/IETF/RFC-5562/RFC-5562.txt","sha256":"fabf7570cc2ec81f0537b054afd0b3e92bdb70097a1fc4b7caa7b24969d80035"}},"tags":["nested-reference","unchanged"],"summary":"The proposal in this document is Experimental. While it may be\n deployed in the current Internet, it does not represent a consensus\n that this is the best possible mechanism for the use of Explicit\n Congestion Notification (ECN) in TCP SYN/ACK packets.\n\n This document describes an optional, experimental modification to RFC\n 3168 to allow TCP SYN/ACK packets to be ECN-Capable. For TCP, RFC\n 3168 specifies setting an ECN-Capable codepoint on data packets, but\n not on SYN and SYN/ACK packets. However, because of the high cost to\n the TCP transfer of having a SYN/ACK packet dropped, with the\n resulting retransmission timeout, this document describes the use of\n ECN for the SYN/ACK packet itself, when sent in response to a SYN\n packet with the two ECN flags set in the TCP header, indicating a\n willingness to use ECN. Setting the initial TCP SYN/ACK packet as\n ECN-Capable can be of great benef","scope_keywords":["5562","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null}],"search_text":"IETF RFC 5562 The proposal in this document is Experimental. While it may be\n deployed in the current Internet, it does not represent a consensus\n that this is the best possible mechanism for the use of Explicit\n Congestion Notification (ECN) in TCP SYN/ACK packets.\n\n This document describes an optional, experimental modification to RFC\n 3168 to allow TCP SYN/ACK packets to be ECN-Capable. For TCP, RFC\n 3168 specifies setting an ECN-Capable codepoint on data packets, but\n not on SYN and SYN/ACK packets. However, because of the high cost to\n the TCP transfer of having a SYN/ACK packet dropped, with the\n resulting retransmission timeout, this document describes the use of\n ECN for the SYN/ACK packet itself, when sent in response to a SYN\n packet with the two ECN flags set in the TCP header, indicating a\n willingness to use ECN. Setting the initial TCP SYN/ACK packet as\n ECN-Capable can be of great benef 5562 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5568","type":"specification","body":"IETF","designation":"RFC 5568","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5568.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5568.txt","https://www.rfc-editor.org/rfc/rfc5568.pdf"],"folder":"IETF/RFC-5568","files":{"txt":{"path":"standards/IETF/RFC-5568/RFC-5568.txt","sha256":"4589eae71ee16808f7e6dd68461411e2eacb2b0935ee5c87151a27f2a560de2e"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 enables a mobile node (MN) to maintain its connectivity\n to the Internet when moving from one Access Router to another, a\n process referred to as handover. During handover, there is a period\n during which the mobile node is unable to send or receive packets\n because of link-switching delay and IP protocol operations. This\n \"handover latency\" resulting from standard Mobile IPv6 procedures\n (namely, movement detection, new Care-of Address configuration, and\n Binding Update) is often unacceptable to real-time traffic such as\n Voice over IP (VoIP). Reducing the handover latency could be\n beneficial to non-real-time, throughput-sensitive applications as\n well. This document specifies a protocol to improve handover latency\n due to Mobile IPv6 procedures. This document does not address\n improving the link-switching latency.\n\n This document updates the packet formats for the Handover","scope_keywords":["5568","authorization","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 5757","folder":"IETF/RFC-5757","source":"IETF/RFC-5757/RFC-5757.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5568 Mobile IPv6 enables a mobile node (MN) to maintain its connectivity\n to the Internet when moving from one Access Router to another, a\n process referred to as handover. During handover, there is a period\n during which the mobile node is unable to send or receive packets\n because of link-switching delay and IP protocol operations. This\n \"handover latency\" resulting from standard Mobile IPv6 procedures\n (namely, movement detection, new Care-of Address configuration, and\n Binding Update) is often unacceptable to real-time traffic such as\n Voice over IP (VoIP). Reducing the handover latency could be\n beneficial to non-real-time, throughput-sensitive applications as\n well. This document specifies a protocol to improve handover latency\n due to Mobile IPv6 procedures. This document does not address\n improving the link-switching latency.\n\n This document updates the packet formats for the Handover 5568 authorization http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5576","type":"specification","body":"IETF","designation":"RFC 5576","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5576.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5576.txt","https://www.rfc-editor.org/rfc/rfc5576.pdf"],"folder":"IETF/RFC-5576","files":{"txt":{"path":"standards/IETF/RFC-5576/RFC-5576.txt","sha256":"84b436d9767023b04da5cded62c49f06530254355eddbc34e3b27334b45e596e"}},"tags":["nested-reference","unchanged"],"summary":"The Session Description Protocol (SDP) provides mechanisms to\n describe attributes of multimedia sessions and of individual media\n streams (e.g., Real-time Transport Protocol (RTP) sessions) within a\n multimedia session, but does not provide any mechanism to describe\n individual media sources within a media stream. This document\n defines a mechanism to describe RTP media sources, which are\n identified by their synchronization source (SSRC) identifiers, in\n SDP, to associate attributes with these sources, and to express\n relationships among sources. It also defines several source-level\n attributes that can be used to describe properties of media sources.","scope_keywords":["5576","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5956","folder":"IETF/RFC-5956","source":"IETF/RFC-5956/RFC-5956.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5576 The Session Description Protocol (SDP) provides mechanisms to\n describe attributes of multimedia sessions and of individual media\n streams (e.g., Real-time Transport Protocol (RTP) sessions) within a\n multimedia session, but does not provide any mechanism to describe\n individual media sources within a media stream. This document\n defines a mechanism to describe RTP media sources, which are\n identified by their synchronization source (SSRC) identifiers, in\n SDP, to associate attributes with these sources, and to express\n relationships among sources. It also defines several source-level\n attributes that can be used to describe properties of media sources. 5576 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5582","type":"specification","body":"IETF","designation":"RFC 5582","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5582.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5582.txt","https://www.rfc-editor.org/rfc/rfc5582.pdf"],"folder":"IETF/RFC-5582","files":{"txt":{"path":"standards/IETF/RFC-5582/RFC-5582.txt","sha256":"f8ca405589fc5d578919981bb541f1b1bc6d2d2d1f60fb3d4b1f2650ce87b60f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for a global, scalable,\nresilient, and administratively distributed system for mapping\ngeographic location information to URLs, using the Location-to-Service\nTranslation (LoST) protocol. The architecture generalizes well-known\napproaches found in hierarchical lookup systems such as DNS.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n ","scope_keywords":["5582","delivery","http","key","license","pid","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6739","folder":"IETF/RFC-6739","source":"IETF/RFC-6739/RFC-6739.txt","version":null}],"search_text":"IETF RFC 5582 This document describes an architecture for a global, scalable,\nresilient, and administratively distributed system for mapping\ngeographic location information to URLs, using the Location-to-Service\nTranslation (LoST) protocol. The architecture generalizes well-known\napproaches found in hierarchical lookup systems such as DNS.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication of this document (http://trustee.ietf.org/license-info).\n Please review these documents carefully, as they describe your rights\n  5582 delivery http key license pid subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5583","type":"specification","body":"IETF","designation":"RFC 5583","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5583.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5583.txt","https://www.rfc-editor.org/rfc/rfc5583.pdf"],"folder":"IETF/RFC-5583","files":{"txt":{"path":"standards/IETF/RFC-5583/RFC-5583.txt","sha256":"3d6239edc08049c1962355a6e05f2c8381cda4e564a8b5aaca346d67170e5af1"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines semantics that allow for signaling the decoding\n dependency of different media descriptions with the same media type\n in the Session Description Protocol (SDP). This is required, for\n example, if media data is separated and transported in different\n network streams as a result of the use of a layered or multiple\n descriptive media coding process.\n\n A new grouping type \"DDP\" -- decoding dependency -- is defined, to be\n used in conjunction with RFC 3388 entitled \"Grouping of Media Lines\n in the Session Description Protocol\". In addition, an attribute is\n specified describing the relationship of the media streams in a \"DDP\"\n group indicated by media identification attribute(s) and media format\n description(s).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improve","scope_keywords":["5583","attribute","http","identification","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5691","folder":"IETF/RFC-5691","source":"IETF/RFC-5691/RFC-5691.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5583 This memo defines semantics that allow for signaling the decoding\n dependency of different media descriptions with the same media type\n in the Session Description Protocol (SDP). This is required, for\n example, if media data is separated and transported in different\n network streams as a result of the use of a layered or multiple\n descriptive media coding process.\n\n A new grouping type \"DDP\" -- decoding dependency -- is defined, to be\n used in conjunction with RFC 3388 entitled \"Grouping of Media Lines\n in the Session Description Protocol\". In addition, an attribute is\n specified describing the relationship of the media streams in a \"DDP\"\n group indicated by media identification attribute(s) and media format\n description(s).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improve 5583 attribute http identification key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5586","type":"specification","body":"IETF","designation":"RFC 5586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5586.txt","https://www.rfc-editor.org/rfc/rfc5586.pdf"],"folder":"IETF/RFC-5586","files":{"txt":{"path":"standards/IETF/RFC-5586/RFC-5586.txt","sha256":"e008f68289bc74715f0a05281ca401013b0d8c3be48fe1f7d0b070084426d3a0"}},"tags":["nested-reference","unchanged"],"summary":"This document generalizes the applicability of the pseudowire (PW)\n Associated Channel Header (ACH), enabling the realization of a\n control channel associated to MPLS Label Switched Paths (LSPs) and\n MPLS Sections in addition to MPLS pseudowires. In order to identify\n the presence of this Associated Channel Header in the label stack,\n this document also assigns one of the reserved MPLS label values to\n the Generic Associated Channel Label (GAL), to be used as a label\n based exception mechanism.\n\nBocci, et al. Standards Track [Page 1]\n\f\nRFC 5586 G-ACh and GAL June 2009","scope_keywords":["5586","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5586 This document generalizes the applicability of the pseudowire (PW)\n Associated Channel Header (ACH), enabling the realization of a\n control channel associated to MPLS Label Switched Paths (LSPs) and\n MPLS Sections in addition to MPLS pseudowires. In order to identify\n the presence of this Associated Channel Header in the label stack,\n this document also assigns one of the reserved MPLS label values to\n the Generic Associated Channel Label (GAL), to be used as a label\n based exception mechanism.\n\nBocci, et al. Standards Track [Page 1]\n\f\nRFC 5586 G-ACh and GAL June 2009 5586 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5589","type":"specification","body":"IETF","designation":"RFC 5589","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5589.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5589.txt","https://www.rfc-editor.org/rfc/rfc5589.pdf"],"folder":"IETF/RFC-5589","files":{"txt":{"path":"standards/IETF/RFC-5589/RFC-5589.txt","sha256":"2fe9273fb066489cc8d6348db5b51fef5354d1b14a8cb36a003f5948ff820b06"}},"tags":["nested-reference","unchanged"],"summary":"This document describes providing Call Transfer capabilities in the\n Session Initiation Protocol (SIP). SIP extensions such as REFER and\n Replaces are used to provide a number of transfer services including\n blind transfer, consultative transfer, and attended transfer. This\n work is part of the SIP multiparty call control framework.\n\nSparks, et al. Best Current Practice [Page 1]\n\f\nRFC 5589 SIP CC Transfer June 2009","scope_keywords":["5589","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 5589 This document describes providing Call Transfer capabilities in the\n Session Initiation Protocol (SIP). SIP extensions such as REFER and\n Replaces are used to provide a number of transfer services including\n blind transfer, consultative transfer, and attended transfer. This\n work is part of the SIP multiparty call control framework.\n\nSparks, et al. Best Current Practice [Page 1]\n\f\nRFC 5589 SIP CC Transfer June 2009 5589 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5590","type":"specification","body":"IETF","designation":"RFC 5590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5590.txt","https://www.rfc-editor.org/rfc/rfc5590.pdf"],"folder":"IETF/RFC-5590","files":{"txt":{"path":"standards/IETF/RFC-5590/RFC-5590.txt","sha256":"3488fb275f34e14bdba50988d177eba545fb65015460d23a56898573a855bf37"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Transport Subsystem, extending the Simple\n Network Management Protocol (SNMP) architecture defined in RFC 3411.\n This document defines a subsystem to contain Transport Models that is\n comparable to other subsystems in the RFC 3411 architecture. As work\n is being done to expand the transports to include secure transports,\n such as the Secure Shell (SSH) Protocol and Transport Layer Security\n\nHarrington & Schoenwaelder Standards Track [Page 1]\n\f\nRFC 5590 SNMP Transport Subsystem June 2009\n\n (TLS), using a subsystem will enable consistent design and modularity\n of such Transport Models. This document identifies and describes\n some key aspects that need to be considered for any Transport Model\n for SNMP.","scope_keywords":["5590","authentication","authorization","http","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5591","folder":"IETF/RFC-5591","source":"IETF/RFC-5591/RFC-5591.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6065","folder":"IETF/RFC-6065","source":"IETF/RFC-6065/RFC-6065.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5590 This document defines a Transport Subsystem, extending the Simple\n Network Management Protocol (SNMP) architecture defined in RFC 3411.\n This document defines a subsystem to contain Transport Models that is\n comparable to other subsystems in the RFC 3411 architecture. As work\n is being done to expand the transports to include secure transports,\n such as the Secure Shell (SSH) Protocol and Transport Layer Security\n\nHarrington & Schoenwaelder Standards Track [Page 1]\n\f\nRFC 5590 SNMP Transport Subsystem June 2009\n\n (TLS), using a subsystem will enable consistent design and modularity\n of such Transport Models. This document identifies and describes\n some key aspects that need to be considered for any Transport Model\n for SNMP. 5590 authentication authorization http key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5591","type":"specification","body":"IETF","designation":"RFC 5591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5591.txt","https://www.rfc-editor.org/rfc/rfc5591.pdf"],"folder":"IETF/RFC-5591","files":{"txt":{"path":"standards/IETF/RFC-5591/RFC-5591.txt","sha256":"57893221b563d229444e7e35edca1c793e26ba039375461d6caa9e1fd8549b64"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a Transport Security Model for the Simple Network\n Management Protocol (SNMP).\n\n This memo also defines a portion of the Management Information Base\n (MIB) for monitoring and managing the Transport Security Model for\n SNMP.","scope_keywords":["5591","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5590","folder":"IETF/RFC-5590","source":"IETF/RFC-5590/RFC-5590.txt","version":null},{"body":"IETF","designation":"RFC 5592","folder":"IETF/RFC-5592","source":"IETF/RFC-5592/RFC-5592.txt","version":null},{"body":"IETF","designation":"RFC 5608","folder":"IETF/RFC-5608","source":"IETF/RFC-5608/RFC-5608.txt","version":null},{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7460","folder":"IETF/RFC-7460","source":"IETF/RFC-7460/RFC-7460.txt","version":null},{"body":"IETF","designation":"RFC 7461","folder":"IETF/RFC-7461","source":"IETF/RFC-7461/RFC-7461.txt","version":null}],"search_text":"IETF RFC 5591 This memo describes a Transport Security Model for the Simple Network\n Management Protocol (SNMP).\n\n This memo also defines a portion of the Management Information Base\n (MIB) for monitoring and managing the Transport Security Model for\n SNMP. 5591 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5597","type":"specification","body":"IETF","designation":"RFC 5597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5597.txt","https://www.rfc-editor.org/rfc/rfc5597.pdf"],"folder":"IETF/RFC-5597","files":{"txt":{"path":"standards/IETF/RFC-5597/RFC-5597.txt","sha256":"e9d592b83a51061607f676a59684280153223acf793f0bb07c039b0e191174a0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of requirements for NATs handling the\n Datagram Congestion Control Protocol (DCCP). These requirements\n allow DCCP applications, such as streaming applications, to operate\n consistently, and they are very similar to the TCP requirements for\n NATs, which have already been published by the IETF. Ensuring that\n NATs meet this set of requirements will greatly increase the\n likelihood that applications using DCCP will function properly.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IE","scope_keywords":["5597","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 5597 This document defines a set of requirements for NATs handling the\n Datagram Congestion Control Protocol (DCCP). These requirements\n allow DCCP applications, such as streaming applications, to operate\n consistently, and they are very similar to the TCP requirements for\n NATs, which have already been published by the IETF. Ensuring that\n NATs meet this set of requirements will greatly increase the\n likelihood that applications using DCCP will function properly.\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IE 5597 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5601","type":"specification","body":"IETF","designation":"RFC 5601","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5601.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5601.txt","https://www.rfc-editor.org/rfc/rfc5601.pdf"],"folder":"IETF/RFC-5601","files":{"txt":{"path":"standards/IETF/RFC-5601/RFC-5601.txt","sha256":"e047887c2b960205829dae44d7a79a269b529fbc3f9e90e5eafa3ee224ecc601"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Standards Track portion of the Management\n Information Base for use with network management protocols in the\n Internet community. In particular, it describes managed objects for\n modeling of Pseudowire Edge-to-Edge services carried over a general\n Packet Switched Network.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the ","scope_keywords":["5601","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5602","folder":"IETF/RFC-5602","source":"IETF/RFC-5602/RFC-5602.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 5601 This memo defines a Standards Track portion of the Management\n Information Base for use with network management protocols in the\n Internet community. In particular, it describes managed objects for\n modeling of Pseudowire Edge-to-Edge services carried over a general\n Packet Switched Network.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the  5601 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5602","type":"specification","body":"IETF","designation":"RFC 5602","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5602.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5602.txt","https://www.rfc-editor.org/rfc/rfc5602.pdf"],"folder":"IETF/RFC-5602","files":{"txt":{"path":"standards/IETF/RFC-5602/RFC-5602.txt","sha256":"9615ad60914080d530ca7824fc9ecc24051a7c200e092d09d0cb640e0fa97e6e"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a MIB module for PW operation over\n Multiprotocol Label Switching (MPLS) Label Switching Routers (LSRs).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication","scope_keywords":["5602","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null}],"search_text":"IETF RFC 5602 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes a MIB module for PW operation over\n Multiprotocol Label Switching (MPLS) Label Switching Routers (LSRs).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect on the date of\n publication 5602 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5610","type":"specification","body":"IETF","designation":"RFC 5610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5610.txt","https://www.rfc-editor.org/rfc/rfc5610.pdf"],"folder":"IETF/RFC-5610","files":{"txt":{"path":"standards/IETF/RFC-5610/RFC-5610.txt","sha256":"4e8fd91243d212bb71e5e6d31226253f343d28d52fb11b946a697d70d6a9c2c2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the IP Flow Information\n Export (IPFIX) protocol, which is used to represent and transmit data\n from IP flow measurement devices for collection, storage, and\n analysis, to allow the encoding of IPFIX Information Model properties\n within an IPFIX Message stream. This enables the export of extended\n type information for enterprise-specific Information Elements and the\n storage of such information within IPFIX Files, facilitating\n interoperability and reusability among a wide variety of applications\n and tools.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this me","scope_keywords":["5610","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 5610 This document describes an extension to the IP Flow Information\n Export (IPFIX) protocol, which is used to represent and transmit data\n from IP flow measurement devices for collection, storage, and\n analysis, to allow the encoding of IPFIX Information Model properties\n within an IPFIX Message stream. This enables the export of extended\n type information for enterprise-specific Information Elements and the\n storage of such information within IPFIX Files, facilitating\n interoperability and reusability among a wide variety of applications\n and tools.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this me 5610 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5613","type":"specification","body":"IETF","designation":"RFC 5613","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5613.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5613.txt","https://www.rfc-editor.org/rfc/rfc5613.pdf"],"folder":"IETF/RFC-5613","files":{"txt":{"path":"standards/IETF/RFC-5613/RFC-5613.txt","sha256":"46d17bf2779e196887fb4a4d1ef347cb57e1994c4db3666bc2a41acb53ea3d97"}},"tags":["nested-reference","unchanged"],"summary":"OSPF is a link-state intra-domain routing protocol. OSPF routers\n exchange information on a link using packets that follow a well-\n defined fixed format. The format is not flexible enough to enable\n new features that need to exchange arbitrary data. This document\n describes a backward-compatible technique to perform link-local\n signaling, i.e., exchange arbitrary data on a link. This document\n replaces the experimental specification published in RFC 4813 to\n bring it on the Standards Track.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IE","scope_keywords":["5613","authentication","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 6506","folder":"IETF/RFC-6506","source":"IETF/RFC-6506/RFC-6506.txt","version":null}],"search_text":"IETF RFC 5613 OSPF is a link-state intra-domain routing protocol. OSPF routers\n exchange information on a link using packets that follow a well-\n defined fixed format. The format is not flexible enough to enable\n new features that need to exchange arbitrary data. This document\n describes a backward-compatible technique to perform link-local\n signaling, i.e., exchange arbitrary data on a link. This document\n replaces the experimental specification published in RFC 4813 to\n bring it on the Standards Track.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IE 5613 authentication delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5614","type":"specification","body":"IETF","designation":"RFC 5614","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5614.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5614.txt","https://www.rfc-editor.org/rfc/rfc5614.pdf"],"folder":"IETF/RFC-5614","files":{"txt":{"path":"standards/IETF/RFC-5614/RFC-5614.txt","sha256":"088daafaffbf318028cd90730b1f6ab95fc2a4f01f8ea80aea2180443782d9ca"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension of OSPFv3 to support mobile ad\n hoc networks (MANETs). The extension, called OSPF-MDR, is designed\n as a new OSPF interface type for MANETs. OSPF-MDR is based on the\n selection of a subset of MANET routers, consisting of MANET\n Designated Routers (MDRs) and Backup MDRs. The MDRs form a connected\n dominating set (CDS), and the MDRs and Backup MDRs together form a\n biconnected CDS for robustness. This CDS is exploited in two ways.\n First, to reduce flooding overhead, an optimized flooding procedure\n is used in which only (Backup) MDRs flood new link state\n advertisements (LSAs) back out the receiving interface; reliable\n flooding is ensured by retransmitting LSAs along adjacencies.\n Second, adjacencies are formed only between (Backup) MDRs and a\n subset of their neighbors, allowing for much better scaling in dense\n networks. The CDS is constructed using","scope_keywords":["5614","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null}],"search_text":"IETF RFC 5614 This document specifies an extension of OSPFv3 to support mobile ad\n hoc networks (MANETs). The extension, called OSPF-MDR, is designed\n as a new OSPF interface type for MANETs. OSPF-MDR is based on the\n selection of a subset of MANET routers, consisting of MANET\n Designated Routers (MDRs) and Backup MDRs. The MDRs form a connected\n dominating set (CDS), and the MDRs and Backup MDRs together form a\n biconnected CDS for robustness. This CDS is exploited in two ways.\n First, to reduce flooding overhead, an optimized flooding procedure\n is used in which only (Backup) MDRs flood new link state\n advertisements (LSAs) back out the receiving interface; reliable\n flooding is ensured by retransmitting LSAs along adjacencies.\n Second, adjacencies are formed only between (Backup) MDRs and a\n subset of their neighbors, allowing for much better scaling in dense\n networks. The CDS is constructed using 5614 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5622","type":"specification","body":"IETF","designation":"RFC 5622","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5622.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5622.txt","https://www.rfc-editor.org/rfc/rfc5622.pdf"],"folder":"IETF/RFC-5622","files":{"txt":{"path":"standards/IETF/RFC-5622/RFC-5622.txt","sha256":"d3db2d7889b44193cc86ea983b66c8528a690f7c0642c101e9be40e01f421b89"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a profile for Congestion Control Identifier\n 4, the small-packet variant of TCP-Friendly Rate Control (TFRC), in\n the Datagram Congestion Control Protocol (DCCP). CCID 4 is for\n experimental use, and uses TFRC-SP (RFC 4828), a variant of TFRC\n designed for applications that send small packets. CCID 4 is\n considered experimental because TFRC-SP is itself experimental, and\n is not proposed for widespread deployment in the global Internet at\n this time. The goal for TFRC-SP is to achieve roughly the same\n bandwidth in bits per second (bps) as a TCP flow using packets of up\n to 1500 bytes but experiencing the same level of congestion. CCID 4\n is for use for senders that send small packets and would like a TCP-\n friendly sending rate, possibly with Explicit Congestion Notification\n (ECN), while minimizing abrupt rate changes.\n\nStatus of This Memo\n\n This memo defines an","scope_keywords":["5622","http","license","profile","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 5622 This document specifies a profile for Congestion Control Identifier\n 4, the small-packet variant of TCP-Friendly Rate Control (TFRC), in\n the Datagram Congestion Control Protocol (DCCP). CCID 4 is for\n experimental use, and uses TFRC-SP (RFC 4828), a variant of TFRC\n designed for applications that send small packets. CCID 4 is\n considered experimental because TFRC-SP is itself experimental, and\n is not proposed for widespread deployment in the global Internet at\n this time. The goal for TFRC-SP is to achieve roughly the same\n bandwidth in bits per second (bps) as a TCP flow using packets of up\n to 1500 bytes but experiencing the same level of congestion. CCID 4\n is for use for senders that send small packets and would like a TCP-\n friendly sending rate, possibly with Explicit Congestion Notification\n (ECN), while minimizing abrupt rate changes.\n\nStatus of This Memo\n\n This memo defines an 5622 http license profile subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5624","type":"specification","body":"IETF","designation":"RFC 5624","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5624.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5624.txt","https://www.rfc-editor.org/rfc/rfc5624.pdf"],"folder":"IETF/RFC-5624","files":{"txt":{"path":"standards/IETF/RFC-5624/RFC-5624.txt","sha256":"0f0f18588fc708f587d4034d530d08537551e1a85750ebc5e073683476e8190f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a number of Quality of Service (QoS) parameters\n that can be reused for conveying QoS information within Diameter.\n\n The defined QoS information includes data traffic parameters for\n describing a token bucket filter, a bandwidth parameter, and a per-\n hop behavior class object.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect","scope_keywords":["5624","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5777","folder":"IETF/RFC-5777","source":"IETF/RFC-5777/RFC-5777.txt","version":null},{"body":"IETF","designation":"RFC 5866","folder":"IETF/RFC-5866","source":"IETF/RFC-5866/RFC-5866.txt","version":null}],"search_text":"IETF RFC 5624 This document defines a number of Quality of Service (QoS) parameters\n that can be reused for conveying QoS information within Diameter.\n\n The defined QoS information includes data traffic parameters for\n describing a token bucket filter, a bandwidth parameter, and a per-\n hop behavior class object.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents in effect 5624 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5627","type":"specification","body":"IETF","designation":"RFC 5627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5627.txt","https://www.rfc-editor.org/rfc/rfc5627.pdf"],"folder":"IETF/RFC-5627","files":{"txt":{"path":"standards/IETF/RFC-5627/RFC-5627.txt","sha256":"a95d952cc1f83780933236a0233152016bacd7b51cb39722d392a996b030c965"}},"tags":["nested-reference","unchanged"],"summary":"Several applications of the Session Initiation Protocol (SIP) require\n a user agent (UA) to construct and distribute a URI that can be used\n by anyone on the Internet to route a call to that specific UA\n instance. A URI that routes to a specific UA instance is called a\n Globally Routable UA URI (GRUU). This document describes an\n extension to SIP for obtaining a GRUU from a registrar and for\n communicating a GRUU to a peer within a dialog.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document","scope_keywords":["5627","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null}],"search_text":"IETF RFC 5627 Several applications of the Session Initiation Protocol (SIP) require\n a user agent (UA) to construct and distribute a URI that can be used\n by anyone on the Internet to route a call to that specific UA\n instance. A URI that routes to a specific UA instance is called a\n Globally Routable UA URI (GRUU). This document describes an\n extension to SIP for obtaining a GRUU from a registrar and for\n communicating a GRUU to a peer within a dialog.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document 5627 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5628","type":"specification","body":"IETF","designation":"RFC 5628","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5628.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5628.txt","https://www.rfc-editor.org/rfc/rfc5628.pdf"],"folder":"IETF/RFC-5628","files":{"txt":{"path":"standards/IETF/RFC-5628/RFC-5628.txt","sha256":"9fc09426d90bc7a24da7e707a68857a11d50e13c3aca83a9e86d31c57010fb55"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3680 defines a Session Initiation Protocol (SIP) event package\n for registration state. This package allows a watcher to learn about\n information stored by a SIP registrar, including its registered\n contact.\n\n However, the registered contact is frequently unreachable and thus\n not useful for watchers. The Globally Routable User Agent URI\n (GRUU), defined in RFC 5627, is a URI that is capable of reaching a\n particular contact. However this URI is not included in the document\n format defined in RFC 3680. This specification defines an extension\n to the registration event package to include GRUUs assigned by the\n registrar.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for t","scope_keywords":["5628","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null}],"search_text":"IETF RFC 5628 RFC 3680 defines a Session Initiation Protocol (SIP) event package\n for registration state. This package allows a watcher to learn about\n information stored by a SIP registrar, including its registered\n contact.\n\n However, the registered contact is frequently unreachable and thus\n not useful for watchers. The Globally Routable User Agent URI\n (GRUU), defined in RFC 5627, is a URI that is capable of reaching a\n particular contact. However this URI is not included in the document\n format defined in RFC 3680. This specification defines an extension\n to the registration event package to include GRUUs assigned by the\n registrar.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for t 5628 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5630","type":"specification","body":"IETF","designation":"RFC 5630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5630.txt","https://www.rfc-editor.org/rfc/rfc5630.pdf"],"folder":"IETF/RFC-5630","files":{"txt":{"path":"standards/IETF/RFC-5630/RFC-5630.txt","sha256":"da5d256ded7ec7951b9c510cd25c67b45fd943f966a2aa72b16939c9a03fe5b7"}},"tags":["nested-reference","unchanged"],"summary":"This document provides clarifications and guidelines concerning the\n use of the SIPS URI scheme in the Session Initiation Protocol (SIP).\n It also makes normative changes to SIP.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these doc","scope_keywords":["5630","authentication","certificate","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 5630 This document provides clarifications and guidelines concerning the\n use of the SIPS URI scheme in the Session Initiation Protocol (SIP).\n It also makes normative changes to SIP.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these doc 5630 authentication certificate http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5637","type":"specification","body":"IETF","designation":"RFC 5637","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5637.txt","https://www.rfc-editor.org/rfc/rfc5637.pdf"],"folder":"IETF/RFC-5637","files":{"txt":{"path":"standards/IETF/RFC-5637/RFC-5637.txt","sha256":"6bd269084148f20d1e4e765ce54ada6bbe745b3a848a17a484c6fcba2e5f66f6"}},"tags":["nested-reference","unchanged"],"summary":"In commercial and enterprise deployments, Mobile IPv6 can be a\n service offered by a Mobility Services Provider (MSP). In this case,\n all protocol operations may need to be explicitly authorized and\n traced, requiring the interaction between Mobile IPv6 and the AAA\n infrastructure. Integrating the Authentication, Authorization, and\n Accounting (AAA) infrastructure (e.g., Network Access Server and AAA\n server) also offers a solution component for Mobile IPv6\n bootstrapping. This document describes various scenarios where a AAA\n interface for Mobile IPv6 is required. Additionally, it lists design\n goals and requirements for such an interface.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identif","scope_keywords":["5637","authentication","authorization","credential","credentials","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null}],"search_text":"IETF RFC 5637 In commercial and enterprise deployments, Mobile IPv6 can be a\n service offered by a Mobility Services Provider (MSP). In this case,\n all protocol operations may need to be explicitly authorized and\n traced, requiring the interaction between Mobile IPv6 and the AAA\n infrastructure. Integrating the Authentication, Authorization, and\n Accounting (AAA) infrastructure (e.g., Network Access Server and AAA\n server) also offers a solution component for Mobile IPv6\n bootstrapping. This document describes various scenarios where a AAA\n interface for Mobile IPv6 is required. Additionally, it lists design\n goals and requirements for such an interface.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identif 5637 authentication authorization credential credentials http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5639","type":"specification","body":"IETF","designation":"RFC 5639","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5639.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5639.txt","https://www.rfc-editor.org/rfc/rfc5639.pdf"],"folder":"IETF/RFC-5639","files":{"txt":{"path":"standards/IETF/RFC-5639/RFC-5639.txt","sha256":"d19949766009ac82b69e46b09f3a08d712908381300a340d3fa3b1478f4b215e"}},"tags":["nested-reference","unchanged"],"summary":"This memo proposes several elliptic curve domain parameters over\n finite prime fields for use in cryptographic applications. The\n domain parameters are consistent with the relevant international\n standards, and can be used in X.509 certificates and certificate\n revocation lists (CRLs), for Internet Key Exchange (IKE), Transport\n Layer Security (TLS), XML signatures, and all applications or\n protocols based on the cryptographic message syntax (CMS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level","scope_keywords":["5639","algorithm","algorithms","certificate","certificates","crl","http","key","license","revocation","risk","signature","signatures","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null}],"search_text":"IETF RFC 5639 This memo proposes several elliptic curve domain parameters over\n finite prime fields for use in cryptographic applications. The\n domain parameters are consistent with the relevant international\n standards, and can be used in X.509 certificates and certificate\n revocation lists (CRLs), for Internet Key Exchange (IKE), Transport\n Layer Security (TLS), XML signatures, and all applications or\n protocols based on the cryptographic message syntax (CMS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level 5639 algorithm algorithms certificate certificates crl http key license revocation risk signature signatures subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5640","type":"specification","body":"IETF","designation":"RFC 5640","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5640.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5640.txt","https://www.rfc-editor.org/rfc/rfc5640.pdf"],"folder":"IETF/RFC-5640","files":{"txt":{"path":"standards/IETF/RFC-5640/RFC-5640.txt","sha256":"6cef8bd9490aea355b1dc21d402bc4f081f40da431d8669a7bc1ed7e0438ab0b"}},"tags":["nested-reference","unchanged"],"summary":"Payloads transported over a Softwire mesh service (as defined by BGP\n Encapsulation Subsequent Address Family Identifier (SAFI) information\n exchange) often carry a number of identifiable, distinct flows. It\n can, in some circumstances, be desirable to distribute these flows\n over the equal cost multiple paths (ECMPs) that exist in the packet\n switched network. Currently, the payload of a packet entering the\n Softwire can only be interpreted by the ingress and egress routers.\n Thus, the load-balancing decision of a core router is only based on\n the encapsulating header, presenting much less entropy than available\n in the payload or the encapsulated header since the Softwire\n encapsulation acts in a tunneling fashion. This document describes a\n method for achieving comparable load-balancing efficiency in a\n network carrying Softwire mesh service over Layer Two Tunneling\n Protocol - Versio","scope_keywords":["5640","attribute","http","identification","key","keys","license","path","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null}],"search_text":"IETF RFC 5640 Payloads transported over a Softwire mesh service (as defined by BGP\n Encapsulation Subsequent Address Family Identifier (SAFI) information\n exchange) often carry a number of identifiable, distinct flows. It\n can, in some circumstances, be desirable to distribute these flows\n over the equal cost multiple paths (ECMPs) that exist in the packet\n switched network. Currently, the payload of a packet entering the\n Softwire can only be interpreted by the ingress and egress routers.\n Thus, the load-balancing decision of a core router is only based on\n the encapsulating header, presenting much less entropy than available\n in the payload or the encapsulated header since the Softwire\n encapsulation acts in a tunneling fashion. This document describes a\n method for achieving comparable load-balancing efficiency in a\n network carrying Softwire mesh service over Layer Two Tunneling\n Protocol - Versio 5640 attribute http identification key keys license path signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5641","type":"specification","body":"IETF","designation":"RFC 5641","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5641.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5641.txt","https://www.rfc-editor.org/rfc/rfc5641.pdf"],"folder":"IETF/RFC-5641","files":{"txt":{"path":"standards/IETF/RFC-5641/RFC-5641.txt","sha256":"6c57004950f97b991b7f64d2be035123522e9c22118819446c564400b7165703"}},"tags":["nested-reference","unchanged"],"summary":"This document defines additional Layer 2 Tunneling Protocol Version 3\n (L2TPv3) bit values to be used within the \"Circuit Status\" Attribute\n Value Pair (AVP) to communicate finer-grained error states for\n Attachment Circuits (ACs) and pseudowires (PWs). It also generalizes\n the Active bit and deprecates the use of the New bit in the Circuit\n Status AVP, updating RFC 3931, RFC 4349, RFC 4454, RFC 4591, and RFC\n 4719.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights res","scope_keywords":["5641","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5641 This document defines additional Layer 2 Tunneling Protocol Version 3\n (L2TPv3) bit values to be used within the \"Circuit Status\" Attribute\n Value Pair (AVP) to communicate finer-grained error states for\n Attachment Circuits (ACs) and pseudowires (PWs). It also generalizes\n the Active bit and deprecates the use of the New bit in the Circuit\n Status AVP, updating RFC 3931, RFC 4349, RFC 4454, RFC 4591, and RFC\n 4719.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights res 5641 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5644","type":"specification","body":"IETF","designation":"RFC 5644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5644.txt","https://www.rfc-editor.org/rfc/rfc5644.pdf"],"folder":"IETF/RFC-5644","files":{"txt":{"path":"standards/IETF/RFC-5644/RFC-5644.txt","sha256":"5a11a9d80a921e4b6338f0b4b00713246d7e9ab108be84b3c2389673f546c37a"}},"tags":["nested-reference","unchanged"],"summary":"The IETF has standardized IP Performance Metrics (IPPM) for measuring\n end-to-end performance between two points. This memo defines two new\n categories of metrics that extend the coverage to multiple\n measurement points. It defines spatial metrics for measuring the\n performance of segments of a source to destination path, and metrics\n for measuring the performance between a source and many destinations\n in multiparty communications (e.g., a multicast tree).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identifie","scope_keywords":["5644","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 5644 The IETF has standardized IP Performance Metrics (IPPM) for measuring\n end-to-end performance between two points. This memo defines two new\n categories of metrics that extend the coverage to multiple\n measurement points. It defines spatial metrics for measuring the\n performance of segments of a source to destination path, and metrics\n for measuring the performance between a source and many destinations\n in multiparty communications (e.g., a multicast tree).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identifie 5644 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5648","type":"specification","body":"IETF","designation":"RFC 5648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5648.txt","https://www.rfc-editor.org/rfc/rfc5648.pdf"],"folder":"IETF/RFC-5648","files":{"txt":{"path":"standards/IETF/RFC-5648/RFC-5648.txt","sha256":"41940fbbd720df519d3ef3e697f9d23738b0922146337e081fc4e41cf42642d1"}},"tags":["nested-reference","unchanged"],"summary":"According to the current Mobile IPv6 specification, a mobile node may\n have several care-of addresses but only one, called the primary\n care-of address, can be registered with its home agent and the\n correspondent nodes. However, for matters of cost, bandwidth, delay,\n etc, it is useful for the mobile node to get Internet access through\n multiple accesses simultaneously, in which case the mobile node would\n be configured with multiple active IPv6 care-of addresses. This\n document proposes extensions to the Mobile IPv6 protocol to register\n and use multiple care-of addresses. The extensions proposed in this\n document can be used by mobile routers using the NEMO (Network\n Mobility) Basic Support protocol as well.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please ","scope_keywords":["5648","http","identification","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5845","folder":"IETF/RFC-5845","source":"IETF/RFC-5845/RFC-5845.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null}],"search_text":"IETF RFC 5648 According to the current Mobile IPv6 specification, a mobile node may\n have several care-of addresses but only one, called the primary\n care-of address, can be registered with its home agent and the\n correspondent nodes. However, for matters of cost, bandwidth, delay,\n etc, it is useful for the mobile node to get Internet access through\n multiple accesses simultaneously, in which case the mobile node would\n be configured with multiple active IPv6 care-of addresses. This\n document proposes extensions to the Mobile IPv6 protocol to register\n and use multiple care-of addresses. The extensions proposed in this\n document can be used by mobile routers using the NEMO (Network\n Mobility) Basic Support protocol as well.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please  5648 http identification license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5650","type":"specification","body":"IETF","designation":"RFC 5650","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5650.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5650.txt","https://www.rfc-editor.org/rfc/rfc5650.pdf"],"folder":"IETF/RFC-5650","files":{"txt":{"path":"standards/IETF/RFC-5650/RFC-5650.txt","sha256":"641f31cf7d38a39f31433985ef8d8111cd0eb70f736c857460017320bce4109b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing parameters of the\n \"Very High Speed Digital Subscriber Line 2 (VDSL2)\" interface type,\n which are also applicable for managing Asymmetric Digital Subscriber\n Line (ADSL), ADSL2, and ADSL2+ interfaces.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This doc","scope_keywords":["5650","http","key","license","management","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 5650 This document defines a Management Information Base (MIB) module for\n use with network management protocols in the Internet community. In\n particular, it describes objects used for managing parameters of the\n \"Very High Speed Digital Subscriber Line 2 (VDSL2)\" interface type,\n which are also applicable for managing Asymmetric Digital Subscriber\n Line (ADSL), ADSL2, and ADSL2+ interfaces.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This doc 5650 http key license management profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5652","type":"specification","body":"IETF","designation":"RFC 5652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5652.txt","https://www.rfc-editor.org/rfc/rfc5652.pdf"],"folder":"IETF/RFC-5652","files":{"txt":{"path":"standards/IETF/RFC-5652/RFC-5652.txt","sha256":"dbd209ae7844031f51722c4d9e2d1fa3fff3081319851d581f914f5f0147f918"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefu","scope_keywords":["5652","algorithm","attribute","attributes","authentication","certificate","certificates","encryption","http","issuer","key","license","revocation","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5816","folder":"IETF/RFC-5816","source":"IETF/RFC-5816/RFC-5816.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6019","folder":"IETF/RFC-6019","source":"IETF/RFC-6019/RFC-6019.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6211","folder":"IETF/RFC-6211","source":"IETF/RFC-6211/RFC-6211.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7104","folder":"IETF/RFC-7104","source":"IETF/RFC-7104/RFC-7104.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IETF RFC 5652 This document describes the Cryptographic Message Syntax (CMS). This\n syntax is used to digitally sign, digest, authenticate, or encrypt\n arbitrary message content.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefu 5652 algorithm attribute attributes authentication certificate certificates encryption http issuer key license revocation signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 5654","type":"specification","body":"IETF","designation":"RFC 5654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5654.txt","https://www.rfc-editor.org/rfc/rfc5654.pdf"],"folder":"IETF/RFC-5654","files":{"txt":{"path":"standards/IETF/RFC-5654/RFC-5654.txt","sha256":"74510cc4ccab2eb0818213165f576895e9ddad108a22a49a4b2159080b995c1a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements of an MPLS Transport Profile\n (MPLS-TP). This document is a product of a joint effort of the\n International Telecommunications Union (ITU) and IETF to include an\n MPLS Transport Profile within the IETF MPLS and PWE3 architectures to\n support the capabilities and functionalities of a packet transport\n network as defined by International Telecommunications Union -\n Telecommunications Standardization Sector (ITU-T).\n\n This work is based on two sources of requirements: MPLS and PWE3\n architectures as defined by IETF, and packet transport networks as\n defined by ITU-T.\n\n The requirements expressed in this document are for the behavior of\n the protocol mechanisms and procedures that constitute building\n blocks out of which the MPLS Transport Profile is constructed. The\n requirements are not implementation requirements.\n\nStatus of This Memo\n\n This docume","scope_keywords":["5654","driving","http","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5659","folder":"IETF/RFC-5659","source":"IETF/RFC-5659/RFC-5659.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6941","folder":"IETF/RFC-6941","source":"IETF/RFC-6941/RFC-6941.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"IETF RFC 5654 This document specifies the requirements of an MPLS Transport Profile\n (MPLS-TP). This document is a product of a joint effort of the\n International Telecommunications Union (ITU) and IETF to include an\n MPLS Transport Profile within the IETF MPLS and PWE3 architectures to\n support the capabilities and functionalities of a packet transport\n network as defined by International Telecommunications Union -\n Telecommunications Standardization Sector (ITU-T).\n\n This work is based on two sources of requirements: MPLS and PWE3\n architectures as defined by IETF, and packet transport networks as\n defined by ITU-T.\n\n The requirements expressed in this document are for the behavior of\n the protocol mechanisms and procedures that constitute building\n blocks out of which the MPLS Transport Profile is constructed. The\n requirements are not implementation requirements.\n\nStatus of This Memo\n\n This docume 5654 driving http license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5663","type":"specification","body":"IETF","designation":"RFC 5663","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5663.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5663.txt","https://www.rfc-editor.org/rfc/rfc5663.pdf"],"folder":"IETF/RFC-5663","files":{"txt":{"path":"standards/IETF/RFC-5663/RFC-5663.txt","sha256":"420f1c959324c82cdd3af69adf604f4f085ab14c649501ba97edfa95028fcb74"}},"tags":["nested-reference","unchanged"],"summary":"Parallel NFS (pNFS) extends Network File Sharing version 4 (NFSv4) to\n allow clients to directly access file data on the storage used by the\n NFSv4 server. This ability to bypass the server for data access can\n increase both performance and parallelism, but requires additional\n client functionality for data access, some of which is dependent on\n the class of storage used. The main pNFS operations document\n specifies storage-class-independent extensions to NFS; this document\n specifies the additional extensions (primarily data structures) for\n use of pNFS with block- and volume-based storage.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri","scope_keywords":["5663","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null}],"search_text":"IETF RFC 5663 Parallel NFS (pNFS) extends Network File Sharing version 4 (NFSv4) to\n allow clients to directly access file data on the storage used by the\n NFSv4 server. This ability to bypass the server for data access can\n increase both performance and parallelism, but requires additional\n client functionality for data access, some of which is dependent on\n the class of storage used. The main pNFS operations document\n specifies storage-class-independent extensions to NFS; this document\n specifies the additional extensions (primarily data structures) for\n use of pNFS with block- and volume-based storage.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steeri 5663 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5664","type":"specification","body":"IETF","designation":"RFC 5664","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5664.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5664.txt","https://www.rfc-editor.org/rfc/rfc5664.pdf"],"folder":"IETF/RFC-5664","files":{"txt":{"path":"standards/IETF/RFC-5664/RFC-5664.txt","sha256":"8a5f271476a09c0a46661c1051bc07c4e8c5da7eeba1409c737b634fb741c2fb"}},"tags":["nested-reference","unchanged"],"summary":"Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to\n allow clients to directly access file data on the storage used by the\n NFSv4 server. This ability to bypass the server for data access can\n increase both performance and parallelism, but requires additional\n client functionality for data access, some of which is dependent on\n the class of storage used, a.k.a. the Layout Type. The main pNFS\n operations and data types in NFSv4 Minor version 1 specify a layout-\n type-independent layer; layout-type-specific information is conveyed\n using opaque data structures whose internal structure is further\n defined by the particular layout type specification. This document\n specifies the NFSv4.1 Object-Based pNFS Layout Type as a companion to\n the main NFSv4 Minor version 1 specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a produc","scope_keywords":["5664","algorithm","algorithms","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null}],"search_text":"IETF RFC 5664 Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to\n allow clients to directly access file data on the storage used by the\n NFSv4 server. This ability to bypass the server for data access can\n increase both performance and parallelism, but requires additional\n client functionality for data access, some of which is dependent on\n the class of storage used, a.k.a. the Layout Type. The main pNFS\n operations and data types in NFSv4 Minor version 1 specify a layout-\n type-independent layer; layout-type-specific information is conveyed\n using opaque data structures whose internal structure is further\n defined by the particular layout type specification. This document\n specifies the NFSv4.1 Object-Based pNFS Layout Type as a companion to\n the main NFSv4 Minor version 1 specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a produc 5664 algorithm algorithms attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5668","type":"specification","body":"IETF","designation":"RFC 5668","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5668.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5668.txt","https://www.rfc-editor.org/rfc/rfc5668.pdf"],"folder":"IETF/RFC-5668","files":{"txt":{"path":"standards/IETF/RFC-5668/RFC-5668.txt","sha256":"dd6cc2753df41248aa02d79cb612b5250d0921b37fa5cd032203f11291c4a35e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new type of a BGP extended community, which\n carries a 4-octet Autonomous System (AS) number.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with res","scope_keywords":["5668","attribute","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6793","folder":"IETF/RFC-6793","source":"IETF/RFC-6793/RFC-6793.txt","version":null}],"search_text":"IETF RFC 5668 This document defines a new type of a BGP extended community, which\n carries a 4-octet Autonomous System (AS) number.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with res 5668 attribute http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5670","type":"specification","body":"IETF","designation":"RFC 5670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5670.txt","https://www.rfc-editor.org/rfc/rfc5670.pdf"],"folder":"IETF/RFC-5670","files":{"txt":{"path":"standards/IETF/RFC-5670/RFC-5670.txt","sha256":"dadf2d8195a0ca04f12ccbf290ad26e9f58de61d5e7ab892cd389f2fecfb7a46"}},"tags":["nested-reference","unchanged"],"summary":"The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain\n in a simple, scalable, and robust fashion. This document defines the\n two metering and marking behaviours of PCN-nodes. Threshold-metering\n and -marking marks all PCN-packets if the rate of PCN-traffic is\n greater than a configured rate (\"PCN-threshold-rate\"). Excess-\n traffic-metering and -marking marks a proportion of PCN-packets, such\n that the amount marked equals the rate of PCN-traffic in excess of a\n configured rate (\"PCN-excess-rate\"). The level of marking allows\n PCN-boundary-nodes to make decisions about whether to admit or\n terminate PCN-flows.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the curren","scope_keywords":["5670","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null}],"search_text":"IETF RFC 5670 The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain\n in a simple, scalable, and robust fashion. This document defines the\n two metering and marking behaviours of PCN-nodes. Threshold-metering\n and -marking marks all PCN-packets if the rate of PCN-traffic is\n greater than a configured rate (\"PCN-threshold-rate\"). Excess-\n traffic-metering and -marking marks a proportion of PCN-packets, such\n that the amount marked equals the rate of PCN-traffic in excess of a\n configured rate (\"PCN-excess-rate\"). The level of marking allows\n PCN-boundary-nodes to make decisions about whether to admit or\n terminate PCN-flows.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the curren 5670 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5672","type":"specification","body":"IETF","designation":"RFC 5672","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5672.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5672.txt","https://www.rfc-editor.org/rfc/rfc5672.pdf"],"folder":"IETF/RFC-5672","files":{"txt":{"path":"standards/IETF/RFC-5672/RFC-5672.txt","sha256":"119c7f18fa93ab309b65a76d7449857bb0d8ffaa58a01d80eb854b2102c45d95"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 4871, \"DomainKeys Identified Mail (DKIM)\n Signatures\". Specifically, the document clarifies the nature, roles,\n and relationship of the two DKIM identifier tag values that are\n candidates for payload delivery to a receiving processing module.\n The Update is in the style of an Errata entry, albeit a rather long\n one.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Prov","scope_keywords":["5672","delivery","http","key","keys","license","policy","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5863","folder":"IETF/RFC-5863","source":"IETF/RFC-5863/RFC-5863.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null}],"search_text":"IETF RFC 5672 This document updates RFC 4871, \"DomainKeys Identified Mail (DKIM)\n Signatures\". Specifically, the document clarifies the nature, roles,\n and relationship of the two DKIM identifier tag values that are\n candidates for payload delivery to a receiving processing module.\n The Update is in the style of an Errata entry, albeit a rather long\n one.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Prov 5672 delivery http key keys license policy signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5674","type":"specification","body":"IETF","designation":"RFC 5674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5674.txt","https://www.rfc-editor.org/rfc/rfc5674.pdf"],"folder":"IETF/RFC-5674","files":{"txt":{"path":"standards/IETF/RFC-5674/RFC-5674.txt","sha256":"a61c4729604343c9ee5e306bc6c71fabedc59846cd8f442b37bfe55839afa942"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to send alarm information in syslog. It\n includes the mapping of ITU perceived severities onto syslog message\n fields. It also includes a number of alarm-specific SD-PARAM\n definitions from X.733 and the IETF Alarm MIB.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date ","scope_keywords":["5674","http","key","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5674 This document describes how to send alarm information in syslog. It\n includes the mapping of ITU perceived severities onto syslog message\n fields. It also includes a number of alarm-specific SD-PARAM\n definitions from X.733 and the IETF Alarm MIB.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date  5674 http key license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5675","type":"specification","body":"IETF","designation":"RFC 5675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5675.txt","https://www.rfc-editor.org/rfc/rfc5675.pdf"],"folder":"IETF/RFC-5675","files":{"txt":{"path":"standards/IETF/RFC-5675/RFC-5675.txt","sha256":"e2dc75daddcc889bbe399f3493f20a3edfc909e2b4ec9b99b237853d9cdb1bc5"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a mapping from Simple Network Management Protocol\n (SNMP) notifications to SYSLOG messages.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to","scope_keywords":["5675","delivery","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5675 This memo defines a mapping from Simple Network Management Protocol\n (SNMP) notifications to SYSLOG messages.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to 5675 delivery http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5676","type":"specification","body":"IETF","designation":"RFC 5676","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5676.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5676.txt","https://www.rfc-editor.org/rfc/rfc5676.pdf"],"folder":"IETF/RFC-5676","files":{"txt":{"path":"standards/IETF/RFC-5676/RFC-5676.txt","sha256":"3c14c128ff26b4b9b90b68740581fedf9a07e19c26fd84433eb5576617e90410"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a mapping of SYSLOG messages to Simple\n Network Management Protocol (SNMP) notifications.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on t","scope_keywords":["5676","http","key","license","management","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5676 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines a mapping of SYSLOG messages to Simple\n Network Management Protocol (SNMP) notifications.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on t 5676 http key license management subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5685","type":"specification","body":"IETF","designation":"RFC 5685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5685.txt","https://www.rfc-editor.org/rfc/rfc5685.pdf"],"folder":"IETF/RFC-5685","files":{"txt":{"path":"standards/IETF/RFC-5685/RFC-5685.txt","sha256":"b05da820de228e850b85f922a22f756fa0d8a088b99e398daeecafbff3801654"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Key Exchange Protocol version 2 (IKEv2) is a protocol\n for setting up Virtual Private Network (VPN) tunnels from a remote\n location to a gateway so that the VPN client can access services in\n the network behind the gateway. This document defines an IKEv2\n extension that allows an overloaded VPN gateway or a VPN gateway that\n is being shut down for maintenance to redirect the VPN client to\n attach to another gateway. The proposed mechanism can also be used\n in Mobile IPv6 to enable the home agent to redirect the mobile node\n to another home agent.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distributio","scope_keywords":["5685","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5723","folder":"IETF/RFC-5723","source":"IETF/RFC-5723/RFC-5723.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5685 The Internet Key Exchange Protocol version 2 (IKEv2) is a protocol\n for setting up Virtual Private Network (VPN) tunnels from a remote\n location to a gateway so that the VPN client can access services in\n the network behind the gateway. This document defines an IKEv2\n extension that allows an overloaded VPN gateway or a VPN gateway that\n is being shut down for maintenance to redirect the VPN client to\n attach to another gateway. The proposed mechanism can also be used\n in Mobile IPv6 to enable the home agent to redirect the mobile node\n to another home agent.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distributio 5685 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5691","type":"specification","body":"IETF","designation":"RFC 5691","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5691.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5691.txt","https://www.rfc-editor.org/rfc/rfc5691.pdf"],"folder":"IETF/RFC-5691","files":{"txt":{"path":"standards/IETF/RFC-5691/RFC-5691.txt","sha256":"31f8fb453644f442733c6a6d714ea0e56b57759b64f23447bdaa7c7ce0e47789"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes extensions for the RTP payload format defined in\n RFC 3640 for the transport of MPEG Surround multi-channel audio.\n Additional Media Type parameters are defined to signal backwards-\n compatible transmission inside an MPEG-4 Audio elementary stream. In\n addition, a layered transmission scheme that doesn't use the MPEG-4\n systems framework is presented to transport an MPEG Surround\n elementary stream via RTP in parallel with an RTP stream containing\n the downmixed audio data.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009","scope_keywords":["5691","attribute","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null}],"search_text":"IETF RFC 5691 This memo describes extensions for the RTP payload format defined in\n RFC 3640 for the transport of MPEG Surround multi-channel audio.\n Additional Media Type parameters are defined to signal backwards-\n compatible transmission inside an MPEG-4 Audio elementary stream. In\n addition, a layered transmission scheme that doesn't use the MPEG-4\n systems framework is presented to transport an MPEG Surround\n elementary stream via RTP in parallel with an RTP stream containing\n the downmixed audio data.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 5691 attribute http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5696","type":"specification","body":"IETF","designation":"RFC 5696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5696.txt","https://www.rfc-editor.org/rfc/rfc5696.pdf"],"folder":"IETF/RFC-5696","files":{"txt":{"path":"standards/IETF/RFC-5696/RFC-5696.txt","sha256":"e8492ab7ecef6d2b9a8d99fc951e03b5df831459ff947617105c6e582e99537d"}},"tags":["nested-reference","unchanged"],"summary":"The objective of the Pre-Congestion Notification (PCN) architecture\n is to protect the quality of service (QoS) of inelastic flows within\n a Diffserv domain. It achieves this by marking packets belonging to\n PCN-flows when the rate of traffic exceeds certain configured\n thresholds on links in the domain. These marks can then be evaluated\n to determine how close the domain is to being congested. This\n document specifies how such marks are encoded into the IP header by\n redefining the Explicit Congestion Notification (ECN) codepoints\n within such domains. The baseline encoding described here provides\n only two PCN encoding states: Not-marked and PCN-marked. Future\n extensions to this encoding may be needed in order to provide more\n than one level of marking severity.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and request","scope_keywords":["5696","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null}],"search_text":"IETF RFC 5696 The objective of the Pre-Congestion Notification (PCN) architecture\n is to protect the quality of service (QoS) of inelastic flows within\n a Diffserv domain. It achieves this by marking packets belonging to\n PCN-flows when the rate of traffic exceeds certain configured\n thresholds on links in the domain. These marks can then be evaluated\n to determine how close the domain is to being congested. This\n document specifies how such marks are encoded into the IP header by\n redefining the Explicit Congestion Notification (ECN) codepoints\n within such domains. The baseline encoding described here provides\n only two PCN encoding states: Not-marked and PCN-marked. Future\n extensions to this encoding may be needed in order to provide more\n than one level of marking severity.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and request 5696 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5702","type":"specification","body":"IETF","designation":"RFC 5702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5702.txt","https://www.rfc-editor.org/rfc/rfc5702.pdf"],"folder":"IETF/RFC-5702","files":{"txt":{"path":"standards/IETF/RFC-5702/RFC-5702.txt","sha256":"04871fb7e95f0ee18298bea6960527579f2a892d9c1a2658b6c3f21b3ec03446"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to produce RSA/SHA-256 and RSA/SHA-512\n DNSKEY and RRSIG resource records for use in the Domain Name System\n Security Extensions (RFC 4033, RFC 4034, and RFC 4035).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these d","scope_keywords":["5702","algorithm","algorithms","hash","http","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null},{"body":"IETF","designation":"RFC 6840","folder":"IETF/RFC-6840","source":"IETF/RFC-6840/RFC-6840.txt","version":null}],"search_text":"IETF RFC 5702 This document describes how to produce RSA/SHA-256 and RSA/SHA-512\n DNSKEY and RRSIG resource records for use in the Domain Name System\n Security Extensions (RFC 4033, RFC 4034, and RFC 4035).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these d 5702 algorithm algorithms hash http key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5705","type":"specification","body":"IETF","designation":"RFC 5705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5705.txt","https://www.rfc-editor.org/rfc/rfc5705.pdf"],"folder":"IETF/RFC-5705","files":{"txt":{"path":"standards/IETF/RFC-5705/RFC-5705.txt","sha256":"29c829cbdf29f4f6a1a0f59eacddf0503bfa67c22af28f127e25b502b3eb2c7a"}},"tags":["nested-reference","unchanged"],"summary":"A number of protocols wish to leverage Transport Layer Security (TLS)\n to perform key establishment but then use some of the keying material\n for their own purposes. This document describes a general mechanism\n for allowing that.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/5705.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All ri","scope_keywords":["5705","algorithm","algorithms","http","key","keys","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 5705 A number of protocols wish to leverage Transport Layer Security (TLS)\n to perform key establishment but then use some of the keying material\n for their own purposes. This document describes a general mechanism\n for allowing that.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/5705.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All ri 5705 algorithm algorithms http key keys license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5708","type":"specification","body":"IETF","designation":"RFC 5708","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5708.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5708.txt","https://www.rfc-editor.org/rfc/rfc5708.pdf"],"folder":"IETF/RFC-5708","files":{"txt":{"path":"standards/IETF/RFC-5708/RFC-5708.txt","sha256":"4dc433d4d07c835f1993eccd5510af9dcd6c23e3e3ec4f2b38698322e4bc9ae5"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes X.509 key identifiers and signature encoding for\n version 2 of the KeyNote trust-management system (RFC 2704). X.509\n certificates (RFC 5280) can be directly used in the Authorizer or\n Licensees field (or in both fields) in a KeyNote assertion, allowing\n for easy integration with protocols that already use X.509\n certificates for authentication.\n\n In addition, the document defines additional signature types that use\n other hash functions (beyond the MD5 and SHA1 hash functions that are\n defined in RFC 2792).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Docume","scope_keywords":["5708","algorithm","authentication","certificate","certificates","credential","credentials","hash","holder","http","key","keys","license","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null}],"search_text":"IETF RFC 5708 This memo describes X.509 key identifiers and signature encoding for\n version 2 of the KeyNote trust-management system (RFC 2704). X.509\n certificates (RFC 5280) can be directly used in the Authorizer or\n Licensees field (or in both fields) in a KeyNote assertion, allowing\n for easy integration with protocols that already use X.509\n certificates for authentication.\n\n In addition, the document defines additional signature types that use\n other hash functions (beyond the MD5 and SHA1 hash functions that are\n defined in RFC 2792).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Docume 5708 algorithm authentication certificate certificates credential credentials hash holder http key keys license management policies policy nested-reference unchanged"},{"id":"IETF RFC 5713","type":"specification","body":"IETF","designation":"RFC 5713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5713.txt","https://www.rfc-editor.org/rfc/rfc5713.pdf"],"folder":"IETF/RFC-5713","files":{"txt":{"path":"standards/IETF/RFC-5713/RFC-5713.txt","sha256":"d280b078aaa37f5a236c8c4b8812a0ce35815f12eb5e81ecae1d2d28313c78db"}},"tags":["nested-reference","unchanged"],"summary":"The Access Node Control Protocol (ANCP) aims to communicate Quality\n of Service (QoS)-related, service-related, and subscriber-related\n configurations and operations between a Network Access Server (NAS)\n and an Access Node (e.g., a Digital Subscriber Line Access\n Multiplexer (DSLAM)). The main goal of this protocol is to allow the\n NAS to configure, manage, and control access equipment, including the\n ability for the Access Nodes to report information to the NAS.\n\n This present document investigates security threats that all ANCP\n nodes could encounter. This document develops a threat model for\n ANCP security, with the aim of deciding which security functions are\n required. Based on this, security requirements regarding the Access\n Node Control Protocol are defined.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational ","scope_keywords":["5713","attribute","attributes","authentication","authorization","http","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5713 The Access Node Control Protocol (ANCP) aims to communicate Quality\n of Service (QoS)-related, service-related, and subscriber-related\n configurations and operations between a Network Access Server (NAS)\n and an Access Node (e.g., a Digital Subscriber Line Access\n Multiplexer (DSLAM)). The main goal of this protocol is to allow the\n NAS to configure, manage, and control access equipment, including the\n ability for the Access Nodes to report information to the NAS.\n\n This present document investigates security threats that all ANCP\n nodes could encounter. This document develops a threat model for\n ANCP security, with the aim of deciding which security functions are\n required. Based on this, security requirements regarding the Access\n Node Control Protocol are defined.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational  5713 attribute attributes authentication authorization http key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5717","type":"specification","body":"IETF","designation":"RFC 5717","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5717.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5717.txt","https://www.rfc-editor.org/rfc/rfc5717.pdf"],"folder":"IETF/RFC-5717","files":{"txt":{"path":"standards/IETF/RFC-5717/RFC-5717.txt","sha256":"1124ab36a146c148db555e93953513ac06863bd50938a2bf86d08ea789a2a9e0"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration protocol (NETCONF) defines the lock and\n unlock Remote Procedure Calls (RPCs), used to lock entire\n configuration datastores. In some situations, a way to lock only\n parts of a configuration datastore is required. This document\n defines a capability-based extension to the NETCONF protocol for\n locking portions of a configuration datastore.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the ","scope_keywords":["5717","http","key","keys","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5717 The Network Configuration protocol (NETCONF) defines the lock and\n unlock Remote Procedure Calls (RPCs), used to lock entire\n configuration datastores. In some situations, a way to lock only\n parts of a configuration datastore is required. This document\n defines a capability-based extension to the NETCONF protocol for\n locking portions of a configuration datastore.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the  5717 http key keys license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5719","type":"specification","body":"IETF","designation":"RFC 5719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5719.txt","https://www.rfc-editor.org/rfc/rfc5719.pdf"],"folder":"IETF/RFC-5719","files":{"txt":{"path":"standards/IETF/RFC-5719/RFC-5719.txt","sha256":"51e6adf791e9bf35cdfb6925de9068bb5cf63bd926640f3cb2395a9c55e4e8c4"}},"tags":["nested-reference","unchanged"],"summary":"The Diameter base specification, described in RFC 3588, provides a\n number of ways to extend Diameter, with new Diameter commands (i.e.,\n messages used by Diameter applications) and applications as the most\n extensive enhancements. RFC 3588 illustrates the conditions that\n lead to the need to define a new Diameter application or a new\n command code. Depending on the scope of the Diameter extension, IETF\n actions are necessary. Although defining new Diameter applications\n does not require IETF consensus, defining new Diameter commands\n requires IETF consensus per RFC 3588. This has led to questionable\n design decisions by other Standards Development Organizations, which\n chose to define new applications on existing commands -- rather than\n asking for assignment of new command codes -- for the pure purpose of\n avoiding bringing their specifications to the IETF. In some cases,\n interoperabi","scope_keywords":["5719","http","key","license","policies","policy","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 5719 The Diameter base specification, described in RFC 3588, provides a\n number of ways to extend Diameter, with new Diameter commands (i.e.,\n messages used by Diameter applications) and applications as the most\n extensive enhancements. RFC 3588 illustrates the conditions that\n lead to the need to define a new Diameter application or a new\n command code. Depending on the scope of the Diameter extension, IETF\n actions are necessary. Although defining new Diameter applications\n does not require IETF consensus, defining new Diameter commands\n requires IETF consensus per RFC 3588. This has led to questionable\n design decisions by other Standards Development Organizations, which\n chose to define new applications on existing commands -- rather than\n asking for assignment of new command codes -- for the pure purpose of\n avoiding bringing their specifications to the IETF. In some cases,\n interoperabi 5719 http key license policies policy risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5723","type":"specification","body":"IETF","designation":"RFC 5723","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5723.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5723.txt","https://www.rfc-editor.org/rfc/rfc5723.pdf"],"folder":"IETF/RFC-5723","files":{"txt":{"path":"standards/IETF/RFC-5723/RFC-5723.txt","sha256":"7dfc9e74613a2fd3ce1d7fa9540512d729e4778ae58dcd9bad9309a4b58708ee"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Key Exchange version 2 (IKEv2) protocol has a certain\n computational and communication overhead with respect to the number\n of round trips required and the cryptographic operations involved.\n In remote access situations, the Extensible Authentication Protocol\n (EAP) is used for authentication, which adds several more round trips\n and consequently latency.\n\n To re-establish security associations (SAs) upon a failure recovery\n condition is time consuming especially when an IPsec peer (such as a\n VPN gateway) needs to re-establish a large number of SAs with various\n endpoints. A high number of concurrent sessions might cause\n additional problems for an IPsec peer during SA re-establishment.\n\n In order to avoid the need to re-run the key exchange protocol from\n scratch, it would be useful to provide an efficient way to resume an\n IKE/IPsec session. This document proposes an exte","scope_keywords":["5723","authentication","http","key","license","management","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6027","folder":"IETF/RFC-6027","source":"IETF/RFC-6027/RFC-6027.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5723 The Internet Key Exchange version 2 (IKEv2) protocol has a certain\n computational and communication overhead with respect to the number\n of round trips required and the cryptographic operations involved.\n In remote access situations, the Extensible Authentication Protocol\n (EAP) is used for authentication, which adds several more round trips\n and consequently latency.\n\n To re-establish security associations (SAs) upon a failure recovery\n condition is time consuming especially when an IPsec peer (such as a\n VPN gateway) needs to re-establish a large number of SAs with various\n endpoints. A high number of concurrent sessions might cause\n additional problems for an IPsec peer during SA re-establishment.\n\n In order to avoid the need to re-run the key exchange protocol from\n scratch, it would be useful to provide an efficient way to resume an\n IKE/IPsec session. This document proposes an exte 5723 authentication http key license management revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 5725","type":"specification","body":"IETF","designation":"RFC 5725","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5725.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5725.txt","https://www.rfc-editor.org/rfc/rfc5725.pdf"],"folder":"IETF/RFC-5725","files":{"txt":{"path":"standards/IETF/RFC-5725/RFC-5725.txt","sha256":"6f34fabbdcbdc243c515021a33cd6d4738c9eaa9bb15a0ff8ef6731b91bfdf99"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new report block type within the framework of\n RTP Control Protocol (RTCP) Extended Reports (XRs). One of the\n initial XR report block types is the Loss Run Length Encoding (RLE)\n Report Block. This report conveys information regarding the\n individual Real-time Transport Protocol (RTP) packet receipt and loss\n events experienced during the RTCP interval preceding the\n transmission of the report. The new report, which is referred to as\n the Post-repair Loss RLE report, carries information regarding the\n packets that remain lost after all loss-repair methods are applied.\n By comparing the RTP packet receipts/losses before and after the loss\n repair is completed, one can determine the effectiveness of the loss-\n repair methods in an aggregated fashion. This document also defines\n the signaling of the Post-repair Loss RLE report in the Session\n Description Protocol (S","scope_keywords":["5725","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null}],"search_text":"IETF RFC 5725 This document defines a new report block type within the framework of\n RTP Control Protocol (RTCP) Extended Reports (XRs). One of the\n initial XR report block types is the Loss Run Length Encoding (RLE)\n Report Block. This report conveys information regarding the\n individual Real-time Transport Protocol (RTP) packet receipt and loss\n events experienced during the RTCP interval preceding the\n transmission of the report. The new report, which is referred to as\n the Post-repair Loss RLE report, carries information regarding the\n packets that remain lost after all loss-repair methods are applied.\n By comparing the RTP packet receipts/losses before and after the loss\n repair is completed, one can determine the effectiveness of the loss-\n repair methods in an aggregated fashion. This document also defines\n the signaling of the Post-repair Loss RLE report in the Session\n Description Protocol (S 5725 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5728","type":"specification","body":"IETF","designation":"RFC 5728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5728.txt","https://www.rfc-editor.org/rfc/rfc5728.pdf"],"folder":"IETF/RFC-5728","files":{"txt":{"path":"standards/IETF/RFC-5728/RFC-5728.txt","sha256":"59d4c7ec348ed4fc22b91673b9c16c8975b26c0fc892e43d7edabde0213b390d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the MIB module for the Digital Video\n Broadcasting Return Channel via Satellite system (DVB-RCS), as\n defined by the SatLabs Group. It defines a set of MIB objects to\n characterize the behavior and performance of network-layer entities\n deploying DVB-RCS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained","scope_keywords":["5728","http","license","pid","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"IETF RFC 5728 This document describes the MIB module for the Digital Video\n Broadcasting Return Channel via Satellite system (DVB-RCS), as\n defined by the SatLabs Group. It defines a set of MIB objects to\n characterize the behavior and performance of network-layer entities\n deploying DVB-RCS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained 5728 http license pid profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5746","type":"specification","body":"IETF","designation":"RFC 5746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5746.txt","https://www.rfc-editor.org/rfc/rfc5746.pdf"],"folder":"IETF/RFC-5746","files":{"txt":{"path":"standards/IETF/RFC-5746/RFC-5746.txt","sha256":"fb894a464bffd123ef7be802b63d7309b7af2bc34091683873c311556de2036d"}},"tags":["nested-reference","unchanged"],"summary":"Secure Socket Layer (SSL) and Transport Layer Security (TLS)\n renegotiation are vulnerable to an attack in which the attacker forms\n a TLS connection with the target server, injects content of his\n choice, and then splices in a new TLS connection from a client. The\n server treats the client's initial TLS handshake as a renegotiation\n and thus believes that the initial data transmitted by the attacker\n is from the same entity as the subsequent client data. This\n specification defines a TLS extension to cryptographically tie\n renegotiations to the TLS connections they are being performed over,\n thus preventing this attack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th","scope_keywords":["5746","authentication","certificate","http","https","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 5746 Secure Socket Layer (SSL) and Transport Layer Security (TLS)\n renegotiation are vulnerable to an attack in which the attacker forms\n a TLS connection with the target server, injects content of his\n choice, and then splices in a new TLS connection from a client. The\n server treats the client's initial TLS handshake as a renegotiation\n and thus believes that the initial data transmitted by the attacker\n is from the same entity as the subsequent client data. This\n specification defines a TLS extension to cryptographically tie\n renegotiations to the TLS connections they are being performed over,\n thus preventing this attack.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th 5746 authentication certificate http https license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5750","type":"specification","body":"IETF","designation":"RFC 5750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5750.txt","https://www.rfc-editor.org/rfc/rfc5750.pdf"],"folder":"IETF/RFC-5750","files":{"txt":{"path":"standards/IETF/RFC-5750/RFC-5750.txt","sha256":"7f99021775d4f75d41ff295a72d8a03c9b37d8dd1c64ddf77f8e259427237cfa"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) v3.2 agents.\n S/MIME provides a method to send and receive secure MIME messages,\n and certificates are an integral part of S/MIME agent processing.\n S/MIME agents validate certificates as described in RFC 5280, the\n Internet X.509 Public Key Infrastructure Certificate and CRL Profile.\n S/MIME agents must meet the certificate processing requirements in\n this document as well as those in RFC 5280. This document obsoletes\n RFC 3850.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on In","scope_keywords":["5750","algorithm","algorithms","attribute","attributes","certificate","certificates","crl","http","issuer","key","keys","license","management","path","pki"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 5750 This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) v3.2 agents.\n S/MIME provides a method to send and receive secure MIME messages,\n and certificates are an integral part of S/MIME agent processing.\n S/MIME agents validate certificates as described in RFC 5280, the\n Internet X.509 Public Key Infrastructure Certificate and CRL Profile.\n S/MIME agents must meet the certificate processing requirements in\n this document as well as those in RFC 5280. This document obsoletes\n RFC 3850.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on In 5750 algorithm algorithms attribute attributes certificate certificates crl http issuer key keys license management path pki nested-reference unchanged"},{"id":"IETF RFC 5752","type":"specification","body":"IETF","designation":"RFC 5752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5752.txt","https://www.rfc-editor.org/rfc/rfc5752.pdf"],"folder":"IETF/RFC-5752","files":{"txt":{"path":"standards/IETF/RFC-5752/RFC-5752.txt","sha256":"49ec15d90ed3d96eb2a8b68543c6e52dfdebf45b938eaf73d18e121c36ca2d38"}},"tags":["nested-reference","unchanged"],"summary":"Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo\n structure to convey per-signer information. SignedData supports\n multiple signers and multiple signature algorithms per signer with\n multiple SignerInfo structures. If a signer attaches more than one\n SignerInfo, there are concerns that an attacker could perform a\n downgrade attack by removing the SignerInfo(s) with the 'strong'\n algorithm(s). This document defines the multiple-signatures\n attribute, its generation rules, and its processing rules to allow\n signers to convey multiple SignerInfo objects while protecting\n against downgrade attacks. Additionally, this attribute may assist\n during periods of algorithm migration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. ","scope_keywords":["5752","algorithm","algorithms","attribute","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 5752 Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo\n structure to convey per-signer information. SignedData supports\n multiple signers and multiple signature algorithms per signer with\n multiple SignerInfo structures. If a signer attaches more than one\n SignerInfo, there are concerns that an attacker could perform a\n downgrade attack by removing the SignerInfo(s) with the 'strong'\n algorithm(s). This document defines the multiple-signatures\n attribute, its generation rules, and its processing rules to allow\n signers to convey multiple SignerInfo objects while protecting\n against downgrade attacks. Additionally, this attribute may assist\n during periods of algorithm migration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community.  5752 algorithm algorithms attribute hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5754","type":"specification","body":"IETF","designation":"RFC 5754","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5754.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5754.txt","https://www.rfc-editor.org/rfc/rfc5754.pdf"],"folder":"IETF/RFC-5754","files":{"txt":{"path":"standards/IETF/RFC-5754/RFC-5754.txt","sha256":"13d095299ffec21ba7726fa6626f9bc4f9e24654bb9a96d70bbc3c78ee51575e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the Secure Hash\n Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384,\n SHA-512) with the Cryptographic Message Syntax (CMS). It also\n describes the conventions for using these algorithms with the CMS and\n the Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA),\n and Elliptic Curve DSA (ECDSA) signature algorithms. Further, it\n provides SMIMECapabilities attribute values for each algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curre","scope_keywords":["5754","algorithm","algorithms","attribute","authentication","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 7929","folder":"IETF/RFC-7929","source":"IETF/RFC-7929/RFC-7929.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 5754 This document describes the conventions for using the Secure Hash\n Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384,\n SHA-512) with the Cryptographic Message Syntax (CMS). It also\n describes the conventions for using these algorithms with the CMS and\n the Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA),\n and Elliptic Curve DSA (ECDSA) signature algorithms. Further, it\n provides SMIMECapabilities attribute values for each algorithm.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curre 5754 algorithm algorithms attribute authentication hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5756","type":"specification","body":"IETF","designation":"RFC 5756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5756.txt","https://www.rfc-editor.org/rfc/rfc5756.pdf"],"folder":"IETF/RFC-5756","files":{"txt":{"path":"standards/IETF/RFC-5756/RFC-5756.txt","sha256":"304a0b826bf211028209db48bd1419c1088127f33e1689d62028378c739e67f5"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 4055. It updates the conventions for using\n the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding\n (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key\n Infrastructure (PKI). Specifically, it updates the conventions for\n algorithm parameters in an X.509 certificate's subjectPublicKeyInfo\n field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or","scope_keywords":["5756","algorithm","algorithms","certificate","certificates","crl","encryption","http","key","license","pki","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 5756 This document updates RFC 4055. It updates the conventions for using\n the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding\n (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key\n Infrastructure (PKI). Specifically, it updates the conventions for\n algorithm parameters in an X.509 certificate's subjectPublicKeyInfo\n field.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or 5756 algorithm algorithms certificate certificates crl encryption http key license pki revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5758","type":"specification","body":"IETF","designation":"RFC 5758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5758.txt","https://www.rfc-editor.org/rfc/rfc5758.pdf"],"folder":"IETF/RFC-5758","files":{"txt":{"path":"standards/IETF/RFC-5758/RFC-5758.txt","sha256":"4d02628ff0875a1960d34be584a68f88528b96242bdc5a05a40a29ef01cf1532"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3279 to specify algorithm identifiers and\n ASN.1 encoding rules for the Digital Signature Algorithm (DSA) and\n Elliptic Curve Digital Signature Algorithm (ECDSA) digital signatures\n when using SHA-224, SHA-256, SHA-384, or SHA-512 as the hashing\n algorithm. This specification applies to the Internet X.509 Public\n Key infrastructure (PKI) when digital signatures are used to sign\n certificates and certificate revocation lists (CRLs). This document\n also identifies all four SHA2 hash algorithms for use in the Internet\n X.509 PKI.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n","scope_keywords":["5758","algorithm","algorithms","certificate","certificates","crl","hash","hashing","http","key","license","pki","policy","profile","profiles","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5754","folder":"IETF/RFC-5754","source":"IETF/RFC-5754/RFC-5754.txt","version":null},{"body":"IETF","designation":"RFC 5759","folder":"IETF/RFC-5759","source":"IETF/RFC-5759/RFC-5759.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 5758 This document updates RFC 3279 to specify algorithm identifiers and\n ASN.1 encoding rules for the Digital Signature Algorithm (DSA) and\n Elliptic Curve Digital Signature Algorithm (ECDSA) digital signatures\n when using SHA-224, SHA-256, SHA-384, or SHA-512 as the hashing\n algorithm. This specification applies to the Internet X.509 Public\n Key infrastructure (PKI) when digital signatures are used to sign\n certificates and certificate revocation lists (CRLs). This document\n also identifies all four SHA2 hash algorithms for use in the Internet\n X.509 PKI.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n 5758 algorithm algorithms certificate certificates crl hash hashing http key license pki policy profile profiles revocation nested-reference unchanged"},{"id":"IETF RFC 5759","type":"specification","body":"IETF","designation":"RFC 5759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5759.txt","https://www.rfc-editor.org/rfc/rfc5759.pdf"],"folder":"IETF/RFC-5759","files":{"txt":{"path":"standards/IETF/RFC-5759/RFC-5759.txt","sha256":"f4e742384bb46f64278a5f2584300f28554f20d4b0624c0d0565c76bba939d9c"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a base profile for X.509 v3 Certificates and\n X.509 v2 Certificate Revocation Lists (CRLs) for use with the United\n States National Security Agency's Suite B Cryptography. The reader\n is assumed to have familiarity with RFC 5280, \"Internet X.509 Public\n Key Infrastructure Certificate and Certificate Revocation List (CRL)\n Profile\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of","scope_keywords":["5759","algorithm","certificate","certificates","crl","hash","http","key","license","profile","profiles","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 6460","folder":"IETF/RFC-6460","source":"IETF/RFC-6460/RFC-6460.txt","version":null}],"search_text":"IETF RFC 5759 This document specifies a base profile for X.509 v3 Certificates and\n X.509 v2 Certificate Revocation Lists (CRLs) for use with the United\n States National Security Agency's Suite B Cryptography. The reader\n is assumed to have familiarity with RFC 5280, \"Internet X.509 Public\n Key Infrastructure Certificate and Certificate Revocation List (CRL)\n Profile\".\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of 5759 algorithm certificate certificates crl hash http key license profile profiles revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5760","type":"specification","body":"IETF","designation":"RFC 5760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5760.txt","https://www.rfc-editor.org/rfc/rfc5760.pdf"],"folder":"IETF/RFC-5760","files":{"txt":{"path":"standards/IETF/RFC-5760/RFC-5760.txt","sha256":"d92301c32836b0fb41fa11e6bfc57fc69cb310830a3d06def0d0478d5a9b34ba"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the Real-time Transport\n Control Protocol (RTCP) to use unicast feedback to a multicast\n sender. The proposed extension is useful for single-source multicast\n sessions such as Source-Specific Multicast (SSM) communication where\n the traditional model of many-to-many group communication is either\n not available or not desired. In addition, it can be applied to any\n group that might benefit from a sender-controlled summarized\n reporting mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informat","scope_keywords":["5760","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5760 This document specifies an extension to the Real-time Transport\n Control Protocol (RTCP) to use unicast feedback to a multicast\n sender. The proposed extension is useful for single-source multicast\n sessions such as Source-Specific Multicast (SSM) communication where\n the traditional model of many-to-many group communication is either\n not available or not desired. In addition, it can be applied to any\n group that might benefit from a sender-controlled summarized\n reporting mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informat 5760 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5762","type":"specification","body":"IETF","designation":"RFC 5762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5762.txt","https://www.rfc-editor.org/rfc/rfc5762.pdf"],"folder":"IETF/RFC-5762","files":{"txt":{"path":"standards/IETF/RFC-5762/RFC-5762.txt","sha256":"b2fdefd3e760b84184b4889c022c36eda09956b1c7cb3ff682a4c288161f3699"}},"tags":["nested-reference","unchanged"],"summary":"The Real-time Transport Protocol (RTP) is a widely used transport for\n real-time multimedia on IP networks. The Datagram Congestion Control\n Protocol (DCCP) is a transport protocol that provides desirable\n services for real-time applications. This memo specifies a mapping\n of RTP onto DCCP, along with associated signalling, such that real-\n time applications can make use of the services provided by DCCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["5762","algorithm","algorithms","http","identification","license","management","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5762 The Real-time Transport Protocol (RTP) is a widely used transport for\n real-time multimedia on IP networks. The Datagram Congestion Control\n Protocol (DCCP) is a transport protocol that provides desirable\n services for real-time applications. This memo specifies a mapping\n of RTP onto DCCP, along with associated signalling, such that real-\n time applications can make use of the services provided by DCCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 5762 algorithm algorithms http identification license management path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5763","type":"specification","body":"IETF","designation":"RFC 5763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5763.txt","https://www.rfc-editor.org/rfc/rfc5763.pdf"],"folder":"IETF/RFC-5763","files":{"txt":{"path":"standards/IETF/RFC-5763/RFC-5763.txt","sha256":"54c4f0881e54faa4d459a8cf2dfe7a1f74388612a6d3f9d56f8c1e8443f052d1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to use the Session Initiation Protocol\n (SIP) to establish a Secure Real-time Transport Protocol (SRTP)\n security context using the Datagram Transport Layer Security (DTLS)\n protocol. It describes a mechanism of transporting a fingerprint\n attribute in the Session Description Protocol (SDP) that identifies\n the key that will be presented during the DTLS handshake. The key\n exchange travels along the media path as opposed to the signaling\n path. The SIP Identity mechanism can be used to protect the\n integrity of the fingerprint attribute from modification by\n intermediate proxies.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet En","scope_keywords":["5763","algorithm","attribute","authentication","certificate","certificates","encryption","http","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5764","folder":"IETF/RFC-5764","source":"IETF/RFC-5764/RFC-5764.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6193","folder":"IETF/RFC-6193","source":"IETF/RFC-6193/RFC-6193.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 5763 This document specifies how to use the Session Initiation Protocol\n (SIP) to establish a Secure Real-time Transport Protocol (SRTP)\n security context using the Datagram Transport Layer Security (DTLS)\n protocol. It describes a mechanism of transporting a fingerprint\n attribute in the Session Description Protocol (SDP) that identifies\n the key that will be presented during the DTLS handshake. The key\n exchange travels along the media path as opposed to the signaling\n path. The SIP Identity mechanism can be used to protect the\n integrity of the fingerprint attribute from modification by\n intermediate proxies.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet En 5763 algorithm attribute authentication certificate certificates encryption http key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5764","type":"specification","body":"IETF","designation":"RFC 5764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5764.txt","https://www.rfc-editor.org/rfc/rfc5764.pdf"],"folder":"IETF/RFC-5764","files":{"txt":{"path":"standards/IETF/RFC-5764/RFC-5764.txt","sha256":"52a16add6006166ac3bff7898d46289b5e0b132843a19d09bd10edc59b1bab1c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Datagram Transport Layer Security (DTLS)\n extension to establish keys for Secure RTP (SRTP) and Secure RTP\n Control Protocol (SRTCP) flows. DTLS keying happens on the media\n path, independent of any out-of-band signalling channel present.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5764.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons ident","scope_keywords":["5764","algorithm","algorithms","authentication","encryption","http","key","keys","license","management","path","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 7022","folder":"IETF/RFC-7022","source":"IETF/RFC-7022/RFC-7022.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7850","folder":"IETF/RFC-7850","source":"IETF/RFC-7850/RFC-7850.txt","version":null},{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 5764 This document describes a Datagram Transport Layer Security (DTLS)\n extension to establish keys for Secure RTP (SRTP) and Secure RTP\n Control Protocol (SRTCP) flows. DTLS keying happens on the media\n path, independent of any out-of-band signalling channel present.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5764.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons ident 5764 algorithm algorithms authentication encryption http key keys license management path profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5767","type":"specification","body":"IETF","designation":"RFC 5767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5767.txt","https://www.rfc-editor.org/rfc/rfc5767.pdf"],"folder":"IETF/RFC-5767","files":{"txt":{"path":"standards/IETF/RFC-5767/RFC-5767.txt","sha256":"0959e88bcbff3300a0732be7a6d5db4bdbd65920767fa87ba74445d338baaf5e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a guideline for a User Agent (UA) to generate\n an anonymous Session Initiation Protocol (SIP) message by utilizing\n mechanisms such as Globally Routable User Agent URIs (GRUUs) and\n Traversal Using Relays around NAT (TURN) without the need for a\n privacy service defined in RFC 3323.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["5767","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5763","folder":"IETF/RFC-5763","source":"IETF/RFC-5763/RFC-5763.txt","version":null},{"body":"IETF","designation":"RFC 5853","folder":"IETF/RFC-5853","source":"IETF/RFC-5853/RFC-5853.txt","version":null}],"search_text":"IETF RFC 5767 This document defines a guideline for a User Agent (UA) to generate\n an anonymous Session Initiation Protocol (SIP) message by utilizing\n mechanisms such as Globally Routable User Agent URIs (GRUUs) and\n Traversal Using Relays around NAT (TURN) without the need for a\n privacy service defined in RFC 3323.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 5767 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5768","type":"specification","body":"IETF","designation":"RFC 5768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5768.txt","https://www.rfc-editor.org/rfc/rfc5768.pdf"],"folder":"IETF/RFC-5768","files":{"txt":{"path":"standards/IETF/RFC-5768/RFC-5768.txt","sha256":"470918b6e5e3425169331217b3dc89c39ce2f0b6e9638ffed14be980f5750070"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a media feature tag and an option tag for\n use with the Session Initiation Protocol (SIP). The media feature\n tag allows a User Agent (UA) to communicate to its registrar that it\n supports ICE. The option tag allows a UA to require support for ICE\n in order for a call to proceed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5768.\n\nCopyright Notice\n\n Copyrigh","scope_keywords":["5768","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 5768 This specification defines a media feature tag and an option tag for\n use with the Session Initiation Protocol (SIP). The media feature\n tag allows a User Agent (UA) to communicate to its registrar that it\n supports ICE. The option tag allows a UA to require support for ICE\n in order for a call to proceed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5768.\n\nCopyright Notice\n\n Copyrigh 5768 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5770","type":"specification","body":"IETF","designation":"RFC 5770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5770.txt","https://www.rfc-editor.org/rfc/rfc5770.pdf"],"folder":"IETF/RFC-5770","files":{"txt":{"path":"standards/IETF/RFC-5770/RFC-5770.txt","sha256":"ac98bb30f0fb61338ddfcbc3f6ff2a8497850a3d66ad8e68db0a24aba09ac036"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies extensions to the Host Identity Protocol\n (HIP) to facilitate Network Address Translator (NAT) traversal. The\n extensions are based on the use of the Interactive Connectivity\n Establishment (ICE) methodology to discover a working path between\n two end-hosts, and on standard techniques for encapsulating\n Encapsulating Security Payload (ESP) packets within the User Datagram\n Protocol (UDP). This document also defines elements of a procedure\n for NAT traversal, including the optional use of a HIP relay server.\n With these extensions HIP is able to work in environments that have\n NATs and provides a generic NAT traversal solution to higher-layer\n networking applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experi","scope_keywords":["5770","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null}],"search_text":"IETF RFC 5770 This document specifies extensions to the Host Identity Protocol\n (HIP) to facilitate Network Address Translator (NAT) traversal. The\n extensions are based on the use of the Interactive Connectivity\n Establishment (ICE) methodology to discover a working path between\n two end-hosts, and on standard techniques for encapsulating\n Encapsulating Security Payload (ESP) packets within the User Datagram\n Protocol (UDP). This document also defines elements of a procedure\n for NAT traversal, including the optional use of a HIP relay server.\n With these extensions HIP is able to work in environments that have\n NATs and provides a generic NAT traversal solution to higher-layer\n networking applications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experi 5770 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5778","type":"specification","body":"IETF","designation":"RFC 5778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5778.txt","https://www.rfc-editor.org/rfc/rfc5778.pdf"],"folder":"IETF/RFC-5778","files":{"txt":{"path":"standards/IETF/RFC-5778/RFC-5778.txt","sha256":"58d1175bc172b5b5429c39f99b3535bec7f35466a1eb90cbc0a96d45dd313a41"}},"tags":["nested-reference","unchanged"],"summary":"Mobile IPv6 deployments may want to bootstrap their operations\n dynamically based on an interaction between the home agent and the\n Diameter server of the Mobile Service Provider. This document\n specifies the interaction between a Mobile IP home agent and a\n Diameter server.\n\n This document defines the home agent to the Diameter server\n communication when the mobile node authenticates using the Internet\n Key Exchange v2 protocol with the Extensible Authentication Protocol\n or using the Mobile IPv6 Authentication Protocol. In addition to\n authentication and authorization, the configuration of Mobile IPv6-\n specific parameters and accounting is specified in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public ","scope_keywords":["5778","algorithm","authentication","authorization","http","key","license","management","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5779","folder":"IETF/RFC-5779","source":"IETF/RFC-5779/RFC-5779.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5778 Mobile IPv6 deployments may want to bootstrap their operations\n dynamically based on an interaction between the home agent and the\n Diameter server of the Mobile Service Provider. This document\n specifies the interaction between a Mobile IP home agent and a\n Diameter server.\n\n This document defines the home agent to the Diameter server\n communication when the mobile node authenticates using the Internet\n Key Exchange v2 protocol with the Extensible Authentication Protocol\n or using the Mobile IPv6 Authentication Protocol. In addition to\n authentication and authorization, the configuration of Mobile IPv6-\n specific parameters and accounting is specified in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public  5778 algorithm authentication authorization http key license management subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5779","type":"specification","body":"IETF","designation":"RFC 5779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5779.txt","https://www.rfc-editor.org/rfc/rfc5779.pdf"],"folder":"IETF/RFC-5779","files":{"txt":{"path":"standards/IETF/RFC-5779/RFC-5779.txt","sha256":"d7c0db4be5d57a7a99706861f7e7192c62f597b169ea5c5339203a137ee7155b"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines Authentication, Authorization, and\n Accounting (AAA) interactions between Proxy Mobile IPv6 entities\n (both Mobile Access Gateway and Local Mobility Anchor) and a AAA\n server within a Proxy Mobile IPv6 Domain. These AAA interactions are\n primarily used to download and update mobile node specific policy\n profile information between Proxy Mobile IPv6 entities and a remote\n policy store.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov","scope_keywords":["5779","attribute","authentication","authorization","http","key","license","management","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6279","folder":"IETF/RFC-6279","source":"IETF/RFC-6279/RFC-6279.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null}],"search_text":"IETF RFC 5779 This specification defines Authentication, Authorization, and\n Accounting (AAA) interactions between Proxy Mobile IPv6 entities\n (both Mobile Access Gateway and Local Mobility Anchor) and a AAA\n server within a Proxy Mobile IPv6 Domain. These AAA interactions are\n primarily used to download and update mobile node specific policy\n profile information between Proxy Mobile IPv6 entities and a remote\n policy store.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to prov 5779 attribute authentication authorization http key license management policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5780","type":"specification","body":"IETF","designation":"RFC 5780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5780.txt","https://www.rfc-editor.org/rfc/rfc5780.pdf"],"folder":"IETF/RFC-5780","files":{"txt":{"path":"standards/IETF/RFC-5780/RFC-5780.txt","sha256":"0858246ec144ea89c861d7c9f6b799c8b66b4987b3140abcc84d3951b061334d"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an experimental usage of the Session\n Traversal Utilities for NAT (STUN) Protocol that discovers the\n presence and current behavior of NATs and firewalls between the STUN\n client and the STUN server.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any ","scope_keywords":["5780","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 5780 This specification defines an experimental usage of the Session\n Traversal Utilities for NAT (STUN) Protocol that discovers the\n presence and current behavior of NATs and firewalls between the STUN\n client and the STUN server.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any  5780 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5785","type":"specification","body":"IETF","designation":"RFC 5785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5785.txt","https://www.rfc-editor.org/rfc/rfc5785.pdf"],"folder":"IETF/RFC-5785","files":{"txt":{"path":"standards/IETF/RFC-5785/RFC-5785.txt","sha256":"601564dd5f96830831c85a48c0c161fd72be19dad8683d37c38d085846889f3a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a path prefix for \"well-known locations\",\n \"/.well-known/\", in selected Uniform Resource Identifier (URI)\n schemes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5785.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re","scope_keywords":["5785","authentication","http","https","key","license","path","policy","registered","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8307","folder":"IETF/RFC-8307","source":"IETF/RFC-8307/RFC-8307.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null}],"search_text":"IETF RFC 5785 This memo defines a path prefix for \"well-known locations\",\n \"/.well-known/\", in selected Uniform Resource Identifier (URI)\n schemes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5785.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re 5785 authentication http https key license path policy registered risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5788","type":"specification","body":"IETF","designation":"RFC 5788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5788.txt","https://www.rfc-editor.org/rfc/rfc5788.pdf"],"folder":"IETF/RFC-5788","files":{"txt":{"path":"standards/IETF/RFC-5788/RFC-5788.txt","sha256":"382a5d302c9d531766d11ccab3ddd83ee938ac12d6fa16df9b0e15fb3a66cd9f"}},"tags":["nested-reference","unchanged"],"summary":"The aim of this document is to establish a new IANA registry for IMAP\n keywords and to define a procedure for keyword registration, in order\n to improve interoperability between different IMAP clients.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5788.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This doc","scope_keywords":["5788","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5788 The aim of this document is to establish a new IANA registry for IMAP\n keywords and to define a procedure for keyword registration, in order\n to improve interoperability between different IMAP clients.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5788.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This doc 5788 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5792","type":"specification","body":"IETF","designation":"RFC 5792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5792.txt","https://www.rfc-editor.org/rfc/rfc5792.pdf"],"folder":"IETF/RFC-5792","files":{"txt":{"path":"standards/IETF/RFC-5792/RFC-5792.txt","sha256":"2f482ee522f7575d8daa5c62fcf5c87d968739b06093e7cb6e446d776e41f0f1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies PA-TNC, a Posture Attribute protocol\n identical to the Trusted Computing Group's IF-M 1.0 protocol. The\n document then evaluates PA-TNC against the requirements defined in\n the NEA Requirements specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5792.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. ","scope_keywords":["5792","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 5792 This document specifies PA-TNC, a Posture Attribute protocol\n identical to the Trusted Computing Group's IF-M 1.0 protocol. The\n document then evaluates PA-TNC against the requirements defined in\n the NEA Requirements specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5792.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors.  5792 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5793","type":"specification","body":"IETF","designation":"RFC 5793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5793.txt","https://www.rfc-editor.org/rfc/rfc5793.pdf"],"folder":"IETF/RFC-5793","files":{"txt":{"path":"standards/IETF/RFC-5793/RFC-5793.txt","sha256":"d20c9bc3632a43a41fd54771fb7f391c28a07f4431db30c32afd6c84e29a5867"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies PB-TNC, a Posture Broker protocol identical\n to the Trusted Computing Group's IF-TNCCS 2.0 protocol. The document\n then evaluates PB-TNC against the requirements defined in the NEA\n Requirements specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5793.\n\nSahita, et al. Standards Track [Page 1]\n\f\nRFC 5793 PB-TNC March 2010\n\nCopyright Notice\n\n Copyright (c","scope_keywords":["5793","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6813","folder":"IETF/RFC-6813","source":"IETF/RFC-6813/RFC-6813.txt","version":null},{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 5793 This document specifies PB-TNC, a Posture Broker protocol identical\n to the Trusted Computing Group's IF-TNCCS 2.0 protocol. The document\n then evaluates PB-TNC against the requirements defined in the NEA\n Requirements specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5793.\n\nSahita, et al. Standards Track [Page 1]\n\f\nRFC 5793 PB-TNC March 2010\n\nCopyright Notice\n\n Copyright (c 5793 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5803","type":"specification","body":"IETF","designation":"RFC 5803","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5803.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5803.txt","https://www.rfc-editor.org/rfc/rfc5803.pdf"],"folder":"IETF/RFC-5803","files":{"txt":{"path":"standards/IETF/RFC-5803/RFC-5803.txt","sha256":"dd115ec84abc767bc9158e09ce02273cd88dc46649d9ac291dfa993665cfbc1f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how the \"authPassword\" Lightweight Directory\n Access Protocol (LDAP) attribute can be used for storing secrets used\n by the Salted Challenge Response Authentication Message (SCRAM)\n mechanism in the Simple Authentication and Security Layer (SASL)\n framework.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained ","scope_keywords":["5803","algorithm","algorithms","attribute","authentication","hash","hashing","http","key","license","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null}],"search_text":"IETF RFC 5803 This memo describes how the \"authPassword\" Lightweight Directory\n Access Protocol (LDAP) attribute can be used for storing secrets used\n by the Salted Challenge Response Authentication Message (SCRAM)\n mechanism in the Simple Authentication and Security Layer (SASL)\n framework.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained  5803 algorithm algorithms attribute authentication hash hashing http key license registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5804","type":"specification","body":"IETF","designation":"RFC 5804","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5804.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5804.txt","https://www.rfc-editor.org/rfc/rfc5804.pdf"],"folder":"IETF/RFC-5804","files":{"txt":{"path":"standards/IETF/RFC-5804/RFC-5804.txt","sha256":"95001fed485b37b953d9adbdcbe80a83bf69d29c3ba4ffa44f30710f4880f75e"}},"tags":["nested-reference","unchanged"],"summary":"Sieve scripts allow users to filter incoming email. Message stores\n are commonly sealed servers so users cannot log into them, yet users\n must be able to update their scripts on them. This document\n describes a protocol \"ManageSieve\" for securely managing Sieve\n scripts on a remote server. This protocol allows a user to have\n multiple scripts, and also alerts a user to syntactically flawed\n scripts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback","scope_keywords":["5804","authentication","crl","http","license","seal","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6785","folder":"IETF/RFC-6785","source":"IETF/RFC-6785/RFC-6785.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5804 Sieve scripts allow users to filter incoming email. Message stores\n are commonly sealed servers so users cannot log into them, yet users\n must be able to update their scripts on them. This document\n describes a protocol \"ManageSieve\" for securely managing Sieve\n scripts on a remote server. This protocol allows a user to have\n multiple scripts, and also alerts a user to syntactically flawed\n scripts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback 5804 authentication crl http license seal subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5808","type":"specification","body":"IETF","designation":"RFC 5808","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5808.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5808.txt","https://www.rfc-editor.org/rfc/rfc5808.pdf"],"folder":"IETF/RFC-5808","files":{"txt":{"path":"standards/IETF/RFC-5808/RFC-5808.txt","sha256":"bd7d5b22a204b8921f92de24f566f20823e5d2d1892d407837f461946df3be54"}},"tags":["nested-reference","unchanged"],"summary":"This document defines terminology and provides requirements relating\n to the Location-by-Reference approach using a location Uniform\n Resource Identifier (URI) to handle location information within\n signaling and other Internet messaging.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc58","scope_keywords":["5808","authorization","http","license","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null}],"search_text":"IETF RFC 5808 This document defines terminology and provides requirements relating\n to the Location-by-Reference approach using a location Uniform\n Resource Identifier (URI) to handle location information within\n signaling and other Internet messaging.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc58 5808 authorization http license pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5815","type":"specification","body":"IETF","designation":"RFC 5815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5815.txt","https://www.rfc-editor.org/rfc/rfc5815.pdf"],"folder":"IETF/RFC-5815","files":{"txt":{"path":"standards/IETF/RFC-5815/RFC-5815.txt","sha256":"e06f786c7136dc2cf5779bd352e6150adeb852e28fb39409b31d35003f806a83"}},"tags":["nested-reference","unchanged"],"summary":"This document defines managed objects for IP Flow Information eXport\n (IPFIX). These objects provide information for monitoring IPFIX\n Exporters and IPFIX Collectors including the basic configuration\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5815.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved","scope_keywords":["5815","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5815 This document defines managed objects for IP Flow Information eXport\n (IPFIX). These objects provide information for monitoring IPFIX\n Exporters and IPFIX Collectors including the basic configuration\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5815.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved 5815 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5816","type":"specification","body":"IETF","designation":"RFC 5816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5816.txt","https://www.rfc-editor.org/rfc/rfc5816.pdf"],"folder":"IETF/RFC-5816","files":{"txt":{"path":"standards/IETF/RFC-5816/RFC-5816.txt","sha256":"9a3eba6ecf14afc7820c51034a608d54d188344a43e9189b0e023d4a6a98f649"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3161. It allows the use of ESSCertIDv2, as\n defined in RFC 5035, to specify the hash of a signer certificate when\n the hash is calculated with a function other than the Secure Hash\n Algorithm (SHA-1).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5816.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All ri","scope_keywords":["5816","algorithm","attribute","certificate","certificates","hash","http","identification","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"IETF RFC 5816 This document updates RFC 3161. It allows the use of ESSCertIDv2, as\n defined in RFC 5035, to specify the hash of a signer certificate when\n the hash is calculated with a function other than the Secure Hash\n Algorithm (SHA-1).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5816.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All ri 5816 algorithm attribute certificate certificates hash http identification key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5819","type":"specification","body":"IETF","designation":"RFC 5819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5819.txt","https://www.rfc-editor.org/rfc/rfc5819.pdf"],"folder":"IETF/RFC-5819","files":{"txt":{"path":"standards/IETF/RFC-5819/RFC-5819.txt","sha256":"7cecc3c6f63e70e872a2cc62888ecfdb5f701f11b339bb4c81e8ad40759de63a"}},"tags":["nested-reference","unchanged"],"summary":"Many IMAP clients display information about total number of\n messages / total number of unseen messages in IMAP mailboxes. In\n order to do that, they are forced to issue a LIST or LSUB command and\n to list all available mailboxes, followed by a STATUS command for\n each mailbox found. This document provides an extension to LIST\n command that allows the client to request STATUS information for\n mailboxes together with other information typically returned by the\n LIST command.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about t","scope_keywords":["5819","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 5819 Many IMAP clients display information about total number of\n messages / total number of unseen messages in IMAP mailboxes. In\n order to do that, they are forced to issue a LIST or LSUB command and\n to list all available mailboxes, followed by a STATUS command for\n each mailbox found. This document provides an extension to LIST\n command that allows the client to request STATUS information for\n mailboxes together with other information typically returned by the\n LIST command.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about t 5819 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5835","type":"specification","body":"IETF","designation":"RFC 5835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5835.txt","https://www.rfc-editor.org/rfc/rfc5835.pdf"],"folder":"IETF/RFC-5835","files":{"txt":{"path":"standards/IETF/RFC-5835/RFC-5835.txt","sha256":"3e42938f7f892ac6b18b0fc8c26e866a3feeebd642114bdbb919a68556b4a449"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a detailed framework for composing and\n aggregating metrics (both in time and in space) originally defined by\n the IP Performance Metrics (IPPM), RFC 2330, and developed by the\n IETF. This new framework memo describes the generic composition and\n aggregation mechanisms. The memo provides a basis for additional\n documents that implement the framework to define detailed\n compositions and aggregations of metrics that are useful in practice.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate f","scope_keywords":["5835","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 5835 This memo describes a detailed framework for composing and\n aggregating metrics (both in time and in space) originally defined by\n the IP Performance Metrics (IPPM), RFC 2330, and developed by the\n IETF. This new framework memo describes the generic composition and\n aggregation mechanisms. The memo provides a basis for additional\n documents that implement the framework to define detailed\n compositions and aggregations of metrics that are useful in practice.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate f 5835 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5839","type":"specification","body":"IETF","designation":"RFC 5839","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5839.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5839.txt","https://www.rfc-editor.org/rfc/rfc5839.pdf"],"folder":"IETF/RFC-5839","files":{"txt":{"path":"standards/IETF/RFC-5839/RFC-5839.txt","sha256":"32f7aee7a17e3c7f695224dd30c68c255da8ee4857119cb301604327bdc7cdcb"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) events framework enables\n receiving asynchronous notification of various events from other SIP\n user agents. This framework defines the procedures for creating,\n refreshing, and terminating subscriptions, as well as fetching and\n periodic polling of resource state. These procedures provide no\n tools to avoid replaying event notifications that have already been\n received by a user agent. This memo defines an extension to SIP\n events that allows the subscriber to condition the subscription\n request to whether the state has changed since the previous\n notification was received. When such a condition is true, either the\n body of a resulting event notification or the entire notification\n message is suppressed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). I","scope_keywords":["5839","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 5839 The Session Initiation Protocol (SIP) events framework enables\n receiving asynchronous notification of various events from other SIP\n user agents. This framework defines the procedures for creating,\n refreshing, and terminating subscriptions, as well as fetching and\n periodic polling of resource state. These procedures provide no\n tools to avoid replaying event notifications that have already been\n received by a user agent. This memo defines an extension to SIP\n events that allows the subscriber to condition the subscription\n request to whether the state has changed since the previous\n notification was received. When such a condition is true, either the\n body of a resulting event notification or the entire notification\n message is suppressed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). I 5839 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5840","type":"specification","body":"IETF","designation":"RFC 5840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5840.txt","https://www.rfc-editor.org/rfc/rfc5840.pdf"],"folder":"IETF/RFC-5840","files":{"txt":{"path":"standards/IETF/RFC-5840/RFC-5840.txt","sha256":"0981e3b08c5eb90b3f7a05209c26fb08078ca83314aa5bae91c9e91f5c7ae30f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Wrapped Encapsulating Security Payload\n (WESP) protocol, which builds on the Encapsulating Security Payload\n (ESP) RFC 4303 and is designed to allow intermediate devices to (1)\n ascertain if data confidentiality is being employed within ESP, and\n if not, (2) inspect the IPsec packets for network monitoring and\n access control functions. Currently, in the IPsec ESP standard,\n there is no deterministic way to differentiate between encrypted and\n unencrypted payloads by simply examining a packet. This poses\n certain challenges to the intermediate devices that need to deep\n inspect the packet before making a decision on what should be done\n with that packet (Inspect and/or Allow/Drop). The mechanism\n described in this document can be used to easily disambiguate\n integrity-only ESP from ESP-encrypted packets, without compromising\n on the security provided by ESP.\n\n","scope_keywords":["5840","algorithm","algorithms","authentication","encryption","http","key","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5879","folder":"IETF/RFC-5879","source":"IETF/RFC-5879/RFC-5879.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5840 This document describes the Wrapped Encapsulating Security Payload\n (WESP) protocol, which builds on the Encapsulating Security Payload\n (ESP) RFC 4303 and is designed to allow intermediate devices to (1)\n ascertain if data confidentiality is being employed within ESP, and\n if not, (2) inspect the IPsec packets for network monitoring and\n access control functions. Currently, in the IPsec ESP standard,\n there is no deterministic way to differentiate between encrypted and\n unencrypted payloads by simply examining a packet. This poses\n certain challenges to the intermediate devices that need to deep\n inspect the packet before making a decision on what should be done\n with that packet (Inspect and/or Allow/Drop). The mechanism\n described in this document can be used to easily disambiguate\n integrity-only ESP from ESP-encrypted packets, without compromising\n on the security provided by ESP.\n\n 5840 algorithm algorithms authentication encryption http key license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5848","type":"specification","body":"IETF","designation":"RFC 5848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5848.txt","https://www.rfc-editor.org/rfc/rfc5848.pdf"],"folder":"IETF/RFC-5848","files":{"txt":{"path":"standards/IETF/RFC-5848/RFC-5848.txt","sha256":"23169e504cf0303b8b2917ef39447113ceb12b6ef0df1ab70365a7f93ae3a4cc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to add origin authentication,\n message integrity, replay resistance, message sequencing, and\n detection of missing messages to the transmitted syslog messages.\n This specification is intended to be used in conjunction with the\n work defined in RFC 5424, \"The Syslog Protocol\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5848.\n\nCopyright Notice\n\n Cop","scope_keywords":["5848","authentication","authorization","certificate","delivery","hash","http","key","license","management","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5848 This document describes a mechanism to add origin authentication,\n message integrity, replay resistance, message sequencing, and\n detection of missing messages to the transmitted syslog messages.\n This specification is intended to be used in conjunction with the\n work defined in RFC 5424, \"The Syslog Protocol\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5848.\n\nCopyright Notice\n\n Cop 5848 authentication authorization certificate delivery hash http key license management signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5856","type":"specification","body":"IETF","designation":"RFC 5856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5856.txt","https://www.rfc-editor.org/rfc/rfc5856.pdf"],"folder":"IETF/RFC-5856","files":{"txt":{"path":"standards/IETF/RFC-5856/RFC-5856.txt","sha256":"3eac266a942a64111681005b6ac871aab21c601e02f23256bb38d8f464a4fb33"}},"tags":["nested-reference","unchanged"],"summary":"IP Security (IPsec) provides various security services for IP\n traffic. However, the benefits of IPsec come at the cost of\n increased overhead. This document outlines a framework for\n integrating Robust Header Compression (ROHC) over IPsec (ROHCoIPsec).\n By compressing the inner headers of IP packets, ROHCoIPsec proposes\n to reduce the amount of overhead associated with the transmission of\n traffic over IPsec Security Associations (SAs).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status o","scope_keywords":["5856","http","identification","key","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5856 IP Security (IPsec) provides various security services for IP\n traffic. However, the benefits of IPsec come at the cost of\n increased overhead. This document outlines a framework for\n integrating Robust Header Compression (ROHC) over IPsec (ROHCoIPsec).\n By compressing the inner headers of IP packets, ROHCoIPsec proposes\n to reduce the amount of overhead associated with the transmission of\n traffic over IPsec Security Associations (SAs).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status o 5856 http identification key license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5857","type":"specification","body":"IETF","designation":"RFC 5857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5857.txt","https://www.rfc-editor.org/rfc/rfc5857.pdf"],"folder":"IETF/RFC-5857","files":{"txt":{"path":"standards/IETF/RFC-5857/RFC-5857.txt","sha256":"f937efdb314df633c197d77a4ea786b2871924d92fbcd5f2cfd2383b35456c48"}},"tags":["nested-reference","unchanged"],"summary":"In order to integrate Robust Header Compression (ROHC) with IPsec, a\n mechanism is needed to signal ROHC channel parameters between\n endpoints. Internet Key Exchange (IKE) is a mechanism that can be\n leveraged to exchange these parameters. This document specifies\n extensions to IKEv2 that will allow ROHC and its associated channel\n parameters to be signaled for IPsec Security Associations (SAs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on ","scope_keywords":["5857","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 5857 In order to integrate Robust Header Compression (ROHC) with IPsec, a\n mechanism is needed to signal ROHC channel parameters between\n endpoints. Internet Key Exchange (IKE) is a mechanism that can be\n leveraged to exchange these parameters. This document specifies\n extensions to IKEv2 that will allow ROHC and its associated channel\n parameters to be signaled for IPsec Security Associations (SAs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on  5857 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5858","type":"specification","body":"IETF","designation":"RFC 5858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5858.txt","https://www.rfc-editor.org/rfc/rfc5858.pdf"],"folder":"IETF/RFC-5858","files":{"txt":{"path":"standards/IETF/RFC-5858/RFC-5858.txt","sha256":"82ef2ff84619030c58129a160722158967610e94af77977e4acd93cc12f3362b"}},"tags":["nested-reference","unchanged"],"summary":"Integrating Robust Header Compression (ROHC) with IPsec (ROHCoIPsec)\n offers the combined benefits of IP security services and efficient\n bandwidth utilization. However, in order to integrate ROHC with\n IPsec, extensions to the Security Policy Database (SPD) and Security\n Association Database (SAD) are required. This document describes the\n IPsec extensions required to support ROHCoIPsec.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may ","scope_keywords":["5858","http","identification","key","license","policy","presentation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5857","folder":"IETF/RFC-5857","source":"IETF/RFC-5857/RFC-5857.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5858 Integrating Robust Header Compression (ROHC) with IPsec (ROHCoIPsec)\n offers the combined benefits of IP security services and efficient\n bandwidth utilization. However, in order to integrate ROHC with\n IPsec, extensions to the Security Policy Database (SPD) and Security\n Association Database (SAD) are required. This document describes the\n IPsec extensions required to support ROHCoIPsec.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may  5858 http identification key license policy presentation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 5860","type":"specification","body":"IETF","designation":"RFC 5860","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5860.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5860.txt","https://www.rfc-editor.org/rfc/rfc5860.pdf"],"folder":"IETF/RFC-5860","files":{"txt":{"path":"standards/IETF/RFC-5860/RFC-5860.txt","sha256":"36de11dcb8606d501ca0c85cc413b6aef8e3451d345982e3d3e05a240a7c1cd6"}},"tags":["nested-reference","unchanged"],"summary":"This document lists architectural and functional requirements for the\n Operations, Administration, and Maintenance of MPLS Transport\n Profile. These requirements apply to pseudowires, Label Switched\n Paths, and Sections.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5860.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights r","scope_keywords":["5860","http","license","management","path","pid","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5860 This document lists architectural and functional requirements for the\n Operations, Administration, and Maintenance of MPLS Transport\n Profile. These requirements apply to pseudowires, Label Switched\n Paths, and Sections.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5860.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights r 5860 http license management path pid profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5861","type":"specification","body":"IETF","designation":"RFC 5861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5861.txt","https://www.rfc-editor.org/rfc/rfc5861.pdf"],"folder":"IETF/RFC-5861","files":{"txt":{"path":"standards/IETF/RFC-5861/RFC-5861.txt","sha256":"1193f1c8710af162e1b9fb4250d79bc6dd26497df4caeeaaa8bcb2fefdd2529e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two independent HTTP Cache-Control extensions\n that allow control over the use of stale responses by caches.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5861.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All ","scope_keywords":["5861","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 5861 This document defines two independent HTTP Cache-Control extensions\n that allow control over the use of stale responses by caches.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5861.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All  5861 http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5865","type":"specification","body":"IETF","designation":"RFC 5865","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5865.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5865.txt","https://www.rfc-editor.org/rfc/rfc5865.pdf"],"folder":"IETF/RFC-5865","files":{"txt":{"path":"standards/IETF/RFC-5865/RFC-5865.txt","sha256":"ae2430593b1297c980e463e2eda44ef3a8bfc47189b22f4c800469f6b9a20e81"}},"tags":["nested-reference","unchanged"],"summary":"This document requests one Differentiated Services Code Point (DSCP)\n from the Internet Assigned Numbers Authority (IANA) for a class of\n real-time traffic. This traffic class conforms to the Expedited\n Forwarding Per-Hop Behavior. This traffic is also admitted by the\n network using a Call Admission Control (CAC) procedure involving\n authentication, authorization, and capacity admission. This differs\n from a real-time traffic class that conforms to the Expedited\n Forwarding Per-Hop Behavior but is not subject to capacity admission\n or subject to very coarse capacity admission.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG)","scope_keywords":["5865","authentication","authorization","http","key","license","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 5865 This document requests one Differentiated Services Code Point (DSCP)\n from the Internet Assigned Numbers Authority (IANA) for a class of\n real-time traffic. This traffic class conforms to the Expedited\n Forwarding Per-Hop Behavior. This traffic is also admitted by the\n network using a Call Admission Control (CAC) procedure involving\n authentication, authorization, and capacity admission. This differs\n from a real-time traffic class that conforms to the Expedited\n Forwarding Per-Hop Behavior but is not subject to capacity admission\n or subject to very coarse capacity admission.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG) 5865 authentication authorization http key license path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5866","type":"specification","body":"IETF","designation":"RFC 5866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5866.txt","https://www.rfc-editor.org/rfc/rfc5866.pdf"],"folder":"IETF/RFC-5866","files":{"txt":{"path":"standards/IETF/RFC-5866/RFC-5866.txt","sha256":"298ceca9a4c31ffabdb93f9a8065f134b7efbff0609f945702340873f58b3984"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the framework, messages, and procedures for\n the Diameter Quality-of-Service (QoS) application. The Diameter QoS\n application allows network elements to interact with Diameter servers\n when allocating QoS resources in the network. In particular, two\n modes of operation, namely \"Pull\" and \"Push\", are defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5866.\n\nC","scope_keywords":["5866","attribute","authorization","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5866 This document describes the framework, messages, and procedures for\n the Diameter Quality-of-Service (QoS) application. The Diameter QoS\n application allows network elements to interact with Diameter servers\n when allocating QoS resources in the network. In particular, two\n modes of operation, namely \"Pull\" and \"Push\", are defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5866.\n\nC 5866 attribute authorization http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5867","type":"specification","body":"IETF","designation":"RFC 5867","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5867.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5867.txt","https://www.rfc-editor.org/rfc/rfc5867.pdf"],"folder":"IETF/RFC-5867","files":{"txt":{"path":"standards/IETF/RFC-5867/RFC-5867.txt","sha256":"44d5f5c0e7c7554bbd6ef89c3555b0077c596e656004db32ebcb0f29228f5b25"}},"tags":["nested-reference","unchanged"],"summary":"The Routing Over Low-Power and Lossy (ROLL) networks Working Group\n has been chartered to work on routing solutions for Low-Power and\n Lossy Networks (LLNs) in various markets: industrial, commercial\n (building), home, and urban networks. Pursuant to this effort, this\n document defines the IPv6 routing requirements for building\n automation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document,","scope_keywords":["5867","authentication","encryption","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7102","folder":"IETF/RFC-7102","source":"IETF/RFC-7102/RFC-7102.txt","version":null}],"search_text":"IETF RFC 5867 The Routing Over Low-Power and Lossy (ROLL) networks Working Group\n has been chartered to work on routing solutions for Low-Power and\n Lossy Networks (LLNs) in various markets: industrial, commercial\n (building), home, and urban networks. Pursuant to this effort, this\n document defines the IPv6 routing requirements for building\n automation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, 5867 authentication encryption http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5870","type":"specification","body":"IETF","designation":"RFC 5870","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5870.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5870.txt","https://www.rfc-editor.org/rfc/rfc5870.pdf"],"folder":"IETF/RFC-5870","files":{"txt":{"path":"standards/IETF/RFC-5870/RFC-5870.txt","sha256":"a3bf93084c422508bbf64976e9adee1eae88d688a2e7f7fc3a531aa44ceb3bb1"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Uniform Resource Identifier (URI) for\n geographic locations using the 'geo' scheme name. A 'geo' URI\n identifies a physical location in a two- or three-dimensional\n coordinate reference system in a compact, simple, human-readable, and\n protocol-independent way. The default coordinate reference system\n used is the World Geodetic System 1984 (WGS-84).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at","scope_keywords":["5870","attribute","attributes","http","identification","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null}],"search_text":"IETF RFC 5870 This document specifies a Uniform Resource Identifier (URI) for\n geographic locations using the 'geo' scheme name. A 'geo' URI\n identifies a physical location in a two- or three-dimensional\n coordinate reference system in a compact, simple, human-readable, and\n protocol-independent way. The default coordinate reference system\n used is the World Geodetic System 1984 (WGS-84).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at 5870 attribute attributes http identification license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5878","type":"specification","body":"IETF","designation":"RFC 5878","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5878.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5878.txt","https://www.rfc-editor.org/rfc/rfc5878.pdf"],"folder":"IETF/RFC-5878","files":{"txt":{"path":"standards/IETF/RFC-5878/RFC-5878.txt","sha256":"1e70f0a72512285619f8636714494a54358f63ca67d355a87b6bb0b29677f674"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies authorization extensions to the Transport\n Layer Security (TLS) Handshake Protocol. Extensions are carried in\n the client and server hello messages to confirm that both parties\n support the desired authorization data types. Then, if supported by\n both the client and the server, authorization information, such as\n attribute certificates (ACs) or Security Assertion Markup Language\n (SAML) assertions, is exchanged in the supplemental data handshake\n message.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been a","scope_keywords":["5878","attribute","authentication","authorization","certificate","certificates","http","identification","issuer","key","license","path","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5878 This document specifies authorization extensions to the Transport\n Layer Security (TLS) Handshake Protocol. Extensions are carried in\n the client and server hello messages to confirm that both parties\n support the desired authorization data types. Then, if supported by\n both the client and the server, authorization information, such as\n attribute certificates (ACs) or Security Assertion Markup Language\n (SAML) assertions, is exchanged in the supplemental data handshake\n message.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been a 5878 attribute authentication authorization certificate certificates http identification issuer key license path presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5881","type":"specification","body":"IETF","designation":"RFC 5881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5881.txt","https://www.rfc-editor.org/rfc/rfc5881.pdf"],"folder":"IETF/RFC-5881","files":{"txt":{"path":"standards/IETF/RFC-5881/RFC-5881.txt","sha256":"30518631501fd4607c39422653aa0eaeae8ed79d7ce7af4a21c2c6a2fc87ca3a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Bidirectional Forwarding\n Detection (BFD) protocol over IPv4 and IPv6 for single IP hops.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5881.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relatin","scope_keywords":["5881","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5883","folder":"IETF/RFC-5883","source":"IETF/RFC-5883/RFC-5883.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 5885","folder":"IETF/RFC-5885","source":"IETF/RFC-5885/RFC-5885.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5881 This document describes the use of the Bidirectional Forwarding\n Detection (BFD) protocol over IPv4 and IPv6 for single IP hops.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5881.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relatin 5881 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5883","type":"specification","body":"IETF","designation":"RFC 5883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5883.txt","https://www.rfc-editor.org/rfc/rfc5883.pdf"],"folder":"IETF/RFC-5883","files":{"txt":{"path":"standards/IETF/RFC-5883/RFC-5883.txt","sha256":"43170c8c2a9aa84ae98c363afb11ae9a8313580ae9653451471c7c1d987f9a28"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Bidirectional Forwarding\n Detection (BFD) protocol over multihop paths, including\n unidirectional links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5883.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro","scope_keywords":["5883","authentication","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5882","folder":"IETF/RFC-5882","source":"IETF/RFC-5882/RFC-5882.txt","version":null},{"body":"IETF","designation":"RFC 5884","folder":"IETF/RFC-5884","source":"IETF/RFC-5884/RFC-5884.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 5883 This document describes the use of the Bidirectional Forwarding\n Detection (BFD) protocol over multihop paths, including\n unidirectional links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5883.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Pro 5883 authentication http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5885","type":"specification","body":"IETF","designation":"RFC 5885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5885.txt","https://www.rfc-editor.org/rfc/rfc5885.pdf"],"folder":"IETF/RFC-5885","files":{"txt":{"path":"standards/IETF/RFC-5885/RFC-5885.txt","sha256":"c94a1809b6c0450a6210df8ef908bdc3c07c84ab7563f7f2a3322bcaef0d7160"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Connectivity Verification (CV) Types using\n Bidirectional Forwarding Detection (BFD) with Virtual Circuit\n Connectivity Verification (VCCV). VCCV provides a control channel\n that is associated with a pseudowire (PW), as well as the\n corresponding operations and management functions such as\n connectivity verification to be used over that control channel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained ","scope_keywords":["5885","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5885 This document describes Connectivity Verification (CV) Types using\n Bidirectional Forwarding Detection (BFD) with Virtual Circuit\n Connectivity Verification (VCCV). VCCV provides a control channel\n that is associated with a pseudowire (PW), as well as the\n corresponding operations and management functions such as\n connectivity verification to be used over that control channel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained  5885 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5892","type":"specification","body":"IETF","designation":"RFC 5892","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5892.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5892.txt","https://www.rfc-editor.org/rfc/rfc5892.pdf"],"folder":"IETF/RFC-5892","files":{"txt":{"path":"standards/IETF/RFC-5892/RFC-5892.txt","sha256":"606dd3619e1d17b3625ef323ac44b0aad272712d067692185d1e417416b66c70"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies rules for deciding whether a code point,\n considered in isolation or in context, is a candidate for inclusion\n in an Internationalized Domain Name (IDN).\n\n It is part of the specification of Internationalizing Domain Names in\n Applications 2008 (IDNA2008).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5892.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and t","scope_keywords":["5892","algorithm","algorithms","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6452","folder":"IETF/RFC-6452","source":"IETF/RFC-6452/RFC-6452.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5892 This document specifies rules for deciding whether a code point,\n considered in isolation or in context, is a candidate for inclusion\n in an Internationalized Domain Name (IDN).\n\n It is part of the specification of Internationalizing Domain Names in\n Applications 2008 (IDNA2008).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5892.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and t 5892 algorithm algorithms http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5901","type":"specification","body":"IETF","designation":"RFC 5901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5901.txt","https://www.rfc-editor.org/rfc/rfc5901.pdf"],"folder":"IETF/RFC-5901","files":{"txt":{"path":"standards/IETF/RFC-5901/RFC-5901.txt","sha256":"ea8276c2e2b0f9282bb82f2a76bd756063b1f71b573452c4e5ec9bab59f04a31"}},"tags":["nested-reference","unchanged"],"summary":"This document extends the Incident Object Description Exchange Format\n (IODEF) defined in RFC 5070 to support the reporting of phishing\n events, which is a particular type of fraud. These extensions are\n flexible enough to support information gleaned from activities\n throughout the entire electronic fraud cycle -- from receipt of the\n phishing lure to the disablement of the collection site. Both simple\n reporting and complete forensic reporting are possible, as is\n consolidating multiple incidents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 57","scope_keywords":["5901","attribute","credential","credentials","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7073","folder":"IETF/RFC-7073","source":"IETF/RFC-7073/RFC-7073.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 5901 This document extends the Incident Object Description Exchange Format\n (IODEF) defined in RFC 5070 to support the reporting of phishing\n events, which is a particular type of fraud. These extensions are\n flexible enough to support information gleaned from activities\n throughout the entire electronic fraud cycle -- from receipt of the\n phishing lure to the disablement of the collection site. Both simple\n reporting and complete forensic reporting are possible, as is\n consolidating multiple incidents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 57 5901 attribute credential credentials http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5908","type":"specification","body":"IETF","designation":"RFC 5908","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5908.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5908.txt","https://www.rfc-editor.org/rfc/rfc5908.pdf"],"folder":"IETF/RFC-5908","files":{"txt":{"path":"standards/IETF/RFC-5908/RFC-5908.txt","sha256":"d61e6ee70339f1bc8ab3ea9dfd54db6c70188ae170eac82a0a19f1939d51f570"}},"tags":["nested-reference","unchanged"],"summary":"The NTP Server Option for Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) provides NTPv4 (Network Time Protocol version 4) server\n location information to DHCPv6 hosts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5908.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78","scope_keywords":["5908","http","key","license","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 5908 The NTP Server Option for Dynamic Host Configuration Protocol for\n IPv6 (DHCPv6) provides NTPv4 (Network Time Protocol version 4) server\n location information to DHCPv6 hosts.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5908.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 5908 http key license qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 5914","type":"specification","body":"IETF","designation":"RFC 5914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5914.txt","https://www.rfc-editor.org/rfc/rfc5914.pdf"],"folder":"IETF/RFC-5914","files":{"txt":{"path":"standards/IETF/RFC-5914/RFC-5914.txt","sha256":"0ad7784e4b5f8fdb7b5d366a74dad193f7a1f3ac69b688de8af78413880cfdbb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a structure for representing trust anchor\n information. A trust anchor is an authoritative entity represented\n by a public key and associated data. The public key is used to\n verify digital signatures, and the associated data is used to\n constrain the types of information or actions for which the trust\n anchor is authoritative. The structures defined in this document are\n intended to satisfy the format-related requirements defined in Trust\n Anchor Management Requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.","scope_keywords":["5914","algorithm","certificate","certificates","http","key","license","management","path","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null}],"search_text":"IETF RFC 5914 This document describes a structure for representing trust anchor\n information. A trust anchor is an authoritative entity represented\n by a public key and associated data. The public key is used to\n verify digital signatures, and the associated data is used to\n constrain the types of information or actions for which the trust\n anchor is authoritative. The structures defined in this document are\n intended to satisfy the format-related requirements defined in Trust\n Anchor Management Requirements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741. 5914 algorithm certificate certificates http key license management path signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5918","type":"specification","body":"IETF","designation":"RFC 5918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5918.txt","https://www.rfc-editor.org/rfc/rfc5918.pdf"],"folder":"IETF/RFC-5918","files":{"txt":{"path":"standards/IETF/RFC-5918/RFC-5918.txt","sha256":"da58d89eec81b56d9fcce759129117990526180d7bbf39dc399d346a859b2fa6"}},"tags":["nested-reference","unchanged"],"summary":"The Label Distribution Protocol (LDP) specification for the Wildcard\n Forward Equivalence Class (FEC) element has several limitations.\n This document addresses those limitations by defining a Typed\n Wildcard FEC Element and associated procedures. In addition, it\n defines a new LDP capability to address backward compatibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5918.\n\nAsati, ","scope_keywords":["5918","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null}],"search_text":"IETF RFC 5918 The Label Distribution Protocol (LDP) specification for the Wildcard\n Forward Equivalence Class (FEC) element has several limitations.\n This document addresses those limitations by defining a Typed\n Wildcard FEC Element and associated procedures. In addition, it\n defines a new LDP capability to address backward compatibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5918.\n\nAsati,  5918 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5919","type":"specification","body":"IETF","designation":"RFC 5919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5919.txt","https://www.rfc-editor.org/rfc/rfc5919.pdf"],"folder":"IETF/RFC-5919","files":{"txt":{"path":"standards/IETF/RFC-5919/RFC-5919.txt","sha256":"b7a64d8cc2a4f43380ad5757b3764b3cfbc2e8d4586396db4e532b1da5c9504d"}},"tags":["nested-reference","unchanged"],"summary":"There are situations following Label Distribution Protocol (LDP)\n session establishment where it would be useful for an LDP speaker to\n know when its peer has advertised all of its labels. The LDP\n specification provides no mechanism for an LDP speaker to notify a\n peer when it has completed its initial label advertisements to that\n peer. This document specifies means for an LDP speaker to signal\n completion of its initial label advertisements following session\n establishment.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information abou","scope_keywords":["5919","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5918","folder":"IETF/RFC-5918","source":"IETF/RFC-5918/RFC-5918.txt","version":null}],"search_text":"IETF RFC 5919 There are situations following Label Distribution Protocol (LDP)\n session establishment where it would be useful for an LDP speaker to\n know when its peer has advertised all of its labels. The LDP\n specification provides no mechanism for an LDP speaker to notify a\n peer when it has completed its initial label advertisements to that\n peer. This document specifies means for an LDP speaker to signal\n completion of its initial label advertisements following session\n establishment.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information abou 5919 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5922","type":"specification","body":"IETF","designation":"RFC 5922","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5922.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5922.txt","https://www.rfc-editor.org/rfc/rfc5922.pdf"],"folder":"IETF/RFC-5922","files":{"txt":{"path":"standards/IETF/RFC-5922/RFC-5922.txt","sha256":"e385332224e250286e098ccc5168ebfd1ec07cc15fa8715919cdb1947188df56"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to construct and interpret certain\n information in a PKIX-compliant (Public Key Infrastructure using\n X.509) certificate for use in a Session Initiation Protocol (SIP)\n over Transport Layer Security (TLS) connection. More specifically,\n this document describes how to encode and extract the identity of a\n SIP domain in a certificate and how to use that identity for SIP\n domain authentication. As such, this document is relevant both to\n implementors of SIP and to issuers of certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Sect","scope_keywords":["5922","authentication","certificate","certificates","encryption","holder","http","issuer","key","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 5922 This document describes how to construct and interpret certain\n information in a PKIX-compliant (Public Key Infrastructure using\n X.509) certificate for use in a Session Initiation Protocol (SIP)\n over Transport Layer Security (TLS) connection. More specifically,\n this document describes how to encode and extract the identity of a\n SIP domain in a certificate and how to use that identity for SIP\n domain authentication. As such, this document is relevant both to\n implementors of SIP and to issuers of certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Sect 5922 authentication certificate certificates encryption holder http issuer key license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5923","type":"specification","body":"IETF","designation":"RFC 5923","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5923.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5923.txt","https://www.rfc-editor.org/rfc/rfc5923.pdf"],"folder":"IETF/RFC-5923","files":{"txt":{"path":"standards/IETF/RFC-5923/RFC-5923.txt","sha256":"1f6f361f125331082a730b74d4d7daa6dc44389b36505d35150bdc1de6ee7694"}},"tags":["nested-reference","unchanged"],"summary":"This document enables a pair of communicating proxies to reuse a\n congestion-controlled connection between themselves for sending\n requests in the forwards and backwards direction. Because the\n connection is essentially aliased for requests going in the backwards\n direction, reuse is predicated upon both the communicating endpoints\n authenticating themselves using X.509 certificates through Transport\n Layer Security (TLS). For this reason, we only consider connection\n reuse for TLS over TCP and TLS over Stream Control Transmission\n Protocol (SCTP). This document also provides guidelines on\n connection reuse and virtual SIP servers and the interaction of\n connection reuse and DNS SRV lookups in SIP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commun","scope_keywords":["5923","authentication","certificate","certificates","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null}],"search_text":"IETF RFC 5923 This document enables a pair of communicating proxies to reuse a\n congestion-controlled connection between themselves for sending\n requests in the forwards and backwards direction. Because the\n connection is essentially aliased for requests going in the backwards\n direction, reuse is predicated upon both the communicating endpoints\n authenticating themselves using X.509 certificates through Transport\n Layer Security (TLS). For this reason, we only consider connection\n reuse for TLS over TCP and TLS over Stream Control Transmission\n Protocol (SCTP). This document also provides guidelines on\n connection reuse and virtual SIP servers and the interaction of\n connection reuse and DNS SRV lookups in SIP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commun 5923 authentication certificate certificates http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5924","type":"specification","body":"IETF","designation":"RFC 5924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5924.txt","https://www.rfc-editor.org/rfc/rfc5924.pdf"],"folder":"IETF/RFC-5924","files":{"txt":{"path":"standards/IETF/RFC-5924/RFC-5924.txt","sha256":"200eac1b3e8f32efa69c54401f2e063dc173c1a4dabcd7fda9cdb2505659d99d"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents an extended key usage (EKU) X.509 certificate\n extension for restricting the applicability of a certificate to use\n with a Session Initiation Protocol (SIP) service. As such, in\n addition to providing rules for SIP implementations, this memo also\n provides guidance to issuers of certificates for use with SIP.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Int","scope_keywords":["5924","certificate","certificates","http","issuer","key","license","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5922","folder":"IETF/RFC-5922","source":"IETF/RFC-5922/RFC-5922.txt","version":null}],"search_text":"IETF RFC 5924 This memo documents an extended key usage (EKU) X.509 certificate\n extension for restricting the applicability of a certificate to use\n with a Session Initiation Protocol (SIP) service. As such, in\n addition to providing rules for SIP implementations, this memo also\n provides guidance to issuers of certificates for use with SIP.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Int 5924 certificate certificates http issuer key license subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 5928","type":"specification","body":"IETF","designation":"RFC 5928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5928.txt","https://www.rfc-editor.org/rfc/rfc5928.pdf"],"folder":"IETF/RFC-5928","files":{"txt":{"path":"standards/IETF/RFC-5928/RFC-5928.txt","sha256":"0828be470d3541cc5272510253a14750b7167a7e54668f189b33a8da62365f59"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a resolution mechanism to generate a list of\n server transport addresses that can be tried to create a Traversal\n Using Relays around NAT (TURN) allocation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5928.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP","scope_keywords":["5928","algorithm","attribute","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5928 This document defines a resolution mechanism to generate a list of\n server transport addresses that can be tried to create a Traversal\n Using Relays around NAT (TURN) allocation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5928.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 5928 algorithm attribute http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5930","type":"specification","body":"IETF","designation":"RFC 5930","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5930.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5930.txt","https://www.rfc-editor.org/rfc/rfc5930.pdf"],"folder":"IETF/RFC-5930","files":{"txt":{"path":"standards/IETF/RFC-5930/RFC-5930.txt","sha256":"cccde2dd589d1c0463dcac80350150215b37086e9c66afacac5485d50ed60df5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the usage of Advanced Encryption Standard\n Counter Mode (AES-CTR), with an explicit Initialization Vector, by\n the Internet Key Exchange version 2 (IKEv2) protocol, for encrypting\n the IKEv2 exchanges that follow the IKE_SA_INIT exchange.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.r","scope_keywords":["5930","algorithm","algorithms","attribute","authentication","encryption","http","key","keys","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5930 This document describes the usage of Advanced Encryption Standard\n Counter Mode (AES-CTR), with an explicit Initialization Vector, by\n the Internet Key Exchange version 2 (IKEv2) protocol, for encrypting\n the IKEv2 exchanges that follow the IKE_SA_INIT exchange.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.r 5930 algorithm algorithms attribute authentication encryption http key keys license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5931","type":"specification","body":"IETF","designation":"RFC 5931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5931.txt","https://www.rfc-editor.org/rfc/rfc5931.pdf"],"folder":"IETF/RFC-5931","files":{"txt":{"path":"standards/IETF/RFC-5931/RFC-5931.txt","sha256":"19aee26bf4a72c6b2f45eb0990cb6a6018d67fe55cdb946e47b1f0142956b741"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an Extensible Authentication Protocol (EAP)\n method, EAP-pwd, which uses a shared password for authentication.\n The password may be a low-entropy one and may be drawn from some set\n of possible passwords, like a dictionary, which is available to an\n attacker. The underlying key exchange is resistant to active attack,\n passive attack, and dictionary attack.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about ","scope_keywords":["5931","authentication","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5998","folder":"IETF/RFC-5998","source":"IETF/RFC-5998/RFC-5998.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 5931 This memo describes an Extensible Authentication Protocol (EAP)\n method, EAP-pwd, which uses a shared password for authentication.\n The password may be a low-entropy one and may be drawn from some set\n of possible passwords, like a dictionary, which is available to an\n attacker. The underlying key exchange is resistant to active attack,\n passive attack, and dictionary attack.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about  5931 authentication http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5932","type":"specification","body":"IETF","designation":"RFC 5932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5932.txt","https://www.rfc-editor.org/rfc/rfc5932.pdf"],"folder":"IETF/RFC-5932","files":{"txt":{"path":"standards/IETF/RFC-5932/RFC-5932.txt","sha256":"4da0b39f346d7807a210a6c4b88ea5780a74267f256547cc5cd6b1f64976bb5d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of cipher suites for the Transport\n Security Layer (TLS) protocol to support the Camellia encryption\n algorithm as a block cipher. It amends the cipher suites originally\n specified in RFC 4132 by introducing counterparts using the newer\n cryptographic hash algorithms from the SHA-2 family. This document\n obsoletes RFC 4132.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edito","scope_keywords":["5932","algorithm","algorithms","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null}],"search_text":"IETF RFC 5932 This document specifies a set of cipher suites for the Transport\n Security Layer (TLS) protocol to support the Camellia encryption\n algorithm as a block cipher. It amends the cipher suites originally\n specified in RFC 4132 by introducing counterparts using the newer\n cryptographic hash algorithms from the SHA-2 family. This document\n obsoletes RFC 4132.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edito 5932 algorithm algorithms encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5933","type":"specification","body":"IETF","designation":"RFC 5933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5933.txt","https://www.rfc-editor.org/rfc/rfc5933.pdf"],"folder":"IETF/RFC-5933","files":{"txt":{"path":"standards/IETF/RFC-5933/RFC-5933.txt","sha256":"92b2587bcbaa48887c6a3ba8347510876bf3c7ee63a694dd0f7589b4e6833162"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to produce digital signatures and hash\n functions using the GOST R 34.10-2001 and GOST R 34.11-94 algorithms\n for DNSKEY, RRSIG, and DS resource records, for use in the Domain\n Name System Security Extensions (DNSSEC).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5933.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n docu","scope_keywords":["5933","algorithm","algorithms","hash","http","key","keys","license","presentation","signature","signatures","subject","trust","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null}],"search_text":"IETF RFC 5933 This document describes how to produce digital signatures and hash\n functions using the GOST R 34.10-2001 and GOST R 34.11-94 algorithms\n for DNSKEY, RRSIG, and DS resource records, for use in the Domain\n Name System Security Extensions (DNSSEC).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5933.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n docu 5933 algorithm algorithms hash http key keys license presentation signature signatures subject trust x509 nested-reference unchanged"},{"id":"IETF RFC 5934","type":"specification","body":"IETF","designation":"RFC 5934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5934.txt","https://www.rfc-editor.org/rfc/rfc5934.pdf"],"folder":"IETF/RFC-5934","files":{"txt":{"path":"standards/IETF/RFC-5934/RFC-5934.txt","sha256":"8dea33b2f7de6fb5b4f8ac4952916013577c95920c4394029aa0237e385349c7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a transport independent protocol for the\n management of trust anchors (TAs) and community identifiers stored in\n a trust anchor store. The protocol makes use of the Cryptographic\n Message Syntax (CMS), and a digital signature is used to provide\n integrity protection and data origin authentication. The protocol\n can be used to manage trust anchor stores containing trust anchors\n represented as Certificate, TBSCertificate, or TrustAnchorInfo\n objects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about th","scope_keywords":["5934","attribute","attributes","authentication","certificate","http","key","license","management","profile","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6024","folder":"IETF/RFC-6024","source":"IETF/RFC-6024/RFC-6024.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null}],"search_text":"IETF RFC 5934 This document describes a transport independent protocol for the\n management of trust anchors (TAs) and community identifiers stored in\n a trust anchor store. The protocol makes use of the Cryptographic\n Message Syntax (CMS), and a digital signature is used to provide\n integrity protection and data origin authentication. The protocol\n can be used to manage trust anchor stores containing trust anchors\n represented as Certificate, TBSCertificate, or TrustAnchorInfo\n objects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about th 5934 attribute attributes authentication certificate http key license management profile signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5937","type":"specification","body":"IETF","designation":"RFC 5937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5937.txt","https://www.rfc-editor.org/rfc/rfc5937.pdf"],"folder":"IETF/RFC-5937","files":{"txt":{"path":"standards/IETF/RFC-5937/RFC-5937.txt","sha256":"6424a9b13e2ea7accfed71e0adef806309851909775aea74471187910f861f01"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use information associated with a\n trust anchor public key when validating certification paths. This\n information can be used to constrain the usage of a trust anchor.\n Typically, constraints are used to limit the certificate policies and\n names that can appear in certification paths validated using a trust\n anchor.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this doc","scope_keywords":["5937","algorithm","certificate","http","key","license","path","policies","policy","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null}],"search_text":"IETF RFC 5937 This document describes how to use information associated with a\n trust anchor public key when validating certification paths. This\n information can be used to constrain the usage of a trust anchor.\n Typically, constraints are used to limit the certificate policies and\n names that can appear in certification paths validated using a trust\n anchor.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this doc 5937 algorithm certificate http key license path policies policy signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5939","type":"specification","body":"IETF","designation":"RFC 5939","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5939.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5939.txt","https://www.rfc-editor.org/rfc/rfc5939.pdf"],"folder":"IETF/RFC-5939","files":{"txt":{"path":"standards/IETF/RFC-5939/RFC-5939.txt","sha256":"9cc3df32e0c6f3dab73aa94035a9d8706b8237e2277a8816b16c20f11ff4aed6"}},"tags":["nested-reference","unchanged"],"summary":"The Session Description Protocol (SDP) was intended to describe\n multimedia sessions for the purposes of session announcement, session\n invitation, and other forms of multimedia session initiation. SDP\n was not intended to provide capability indication or capability\n negotiation; however, over the years, SDP has seen widespread\n adoption and as a result it has been gradually extended to provide\n limited support for these, notably in the form of the offer/answer\n model defined in RFC 3264. SDP does not define how to negotiate one\n or more alternative transport protocols (e.g., RTP profiles) or\n attributes. This makes it difficult to deploy new RTP profiles such\n as Secure RTP or RTP with RTCP-based feedback, negotiate use of\n different security keying mechanisms, etc. It also presents problems\n for some forms of media negotiation.\n\n The purpose of this document is to address these shortco","scope_keywords":["5939","attribute","attributes","http","key","license","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7345","folder":"IETF/RFC-7345","source":"IETF/RFC-7345/RFC-7345.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5939 The Session Description Protocol (SDP) was intended to describe\n multimedia sessions for the purposes of session announcement, session\n invitation, and other forms of multimedia session initiation. SDP\n was not intended to provide capability indication or capability\n negotiation; however, over the years, SDP has seen widespread\n adoption and as a result it has been gradually extended to provide\n limited support for these, notably in the form of the offer/answer\n model defined in RFC 3264. SDP does not define how to negotiate one\n or more alternative transport protocols (e.g., RTP profiles) or\n attributes. This makes it difficult to deploy new RTP profiles such\n as Secure RTP or RTP with RTCP-based feedback, negotiate use of\n different security keying mechanisms, etc. It also presents problems\n for some forms of media negotiation.\n\n The purpose of this document is to address these shortco 5939 attribute attributes http key license profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5940","type":"specification","body":"IETF","designation":"RFC 5940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5940.txt","https://www.rfc-editor.org/rfc/rfc5940.pdf"],"folder":"IETF/RFC-5940","files":{"txt":{"path":"standards/IETF/RFC-5940/RFC-5940.txt","sha256":"734bca6d8b6f33409c08ad8a00f9cc43ed05b96f2f34a679c14c5141db5d978b"}},"tags":["nested-reference","unchanged"],"summary":"The Cryptographic Message Syntax (CMS) allows revocation information\n to be conveyed as part of the SignedData, EnvelopedData,\n AuthenticatedData, and AuthEnvelopedData content types. The\n preferred format for revocation information is the Certificate\n Revocation List (CRL), but an extension mechanism supports other\n revocation information formats. This document defines two additional\n revocation information formats for Online Certificate Status Protocol\n (OCSP) responses and Server-Based Certificate Validation Protocol\n (SCVP) requests and responses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n ","scope_keywords":["5940","attribute","authentication","certificate","certificates","crl","http","key","license","ocsp","pki","profile","revocation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"}],"search_text":"IETF RFC 5940 The Cryptographic Message Syntax (CMS) allows revocation information\n to be conveyed as part of the SignedData, EnvelopedData,\n AuthenticatedData, and AuthEnvelopedData content types. The\n preferred format for revocation information is the Certificate\n Revocation List (CRL), but an extension mechanism supports other\n revocation information formats. This document defines two additional\n revocation information formats for Online Certificate Status Protocol\n (OCSP) responses and Server-Based Certificate Validation Protocol\n (SCVP) requests and responses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n  5940 attribute authentication certificate certificates crl http key license ocsp pki profile revocation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5941","type":"specification","body":"IETF","designation":"RFC 5941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5941.txt","https://www.rfc-editor.org/rfc/rfc5941.pdf"],"folder":"IETF/RFC-5941","files":{"txt":{"path":"standards/IETF/RFC-5941/RFC-5941.txt","sha256":"7a2de736940fc26d552a62f198e0af5fdc95279cc1be86a9f93797b5304f739a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a document format for exchanging transaction\n fraud (Thraud) information. It extends the Incident Handling Working\n Group (INCH WG) Incident Object Description Exchange Format (IODEF)\n incident reporting document format.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info","scope_keywords":["5941","attribute","http","license","profile","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null}],"search_text":"IETF RFC 5941 This document describes a document format for exchanging transaction\n fraud (Thraud) information. It extends the Incident Handling Working\n Group (INCH WG) Incident Object Description Exchange Format (IODEF)\n incident reporting document format.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info 5941 attribute http license profile signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5951","type":"specification","body":"IETF","designation":"RFC 5951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5951.txt","https://www.rfc-editor.org/rfc/rfc5951.pdf"],"folder":"IETF/RFC-5951","files":{"txt":{"path":"standards/IETF/RFC-5951/RFC-5951.txt","sha256":"8db04ec10ec3a0952c965ef06b543dcb74855b5ebce2637f9d948c9c46e39185"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the requirements for the management of\n equipment used in networks supporting an MPLS Transport Profile\n (MPLS-TP). The requirements are defined for specification of\n network management aspects of protocol mechanisms and procedures\n that constitute the building blocks out of which the MPLS\n Transport Profile is constructed. That is, these requirements\n indicate what management capabilities need to be available in\n MPLS for use in managing the MPLS-TP. This document is intended\n to identify essential network management capabilities, not to\n specify what functions any particular MPLS implementation\n supports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publica","scope_keywords":["5951","http","key","license","management","path","profile","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"IETF RFC 5951 This document specifies the requirements for the management of\n equipment used in networks supporting an MPLS Transport Profile\n (MPLS-TP). The requirements are defined for specification of\n network management aspects of protocol mechanisms and procedures\n that constitute the building blocks out of which the MPLS\n Transport Profile is constructed. That is, these requirements\n indicate what management capabilities need to be available in\n MPLS for use in managing the MPLS-TP. This document is intended\n to identify essential network management capabilities, not to\n specify what functions any particular MPLS implementation\n supports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publica 5951 http key license management path profile subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5952","type":"specification","body":"IETF","designation":"RFC 5952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5952.txt","https://www.rfc-editor.org/rfc/rfc5952.pdf"],"folder":"IETF/RFC-5952","files":{"txt":{"path":"standards/IETF/RFC-5952/RFC-5952.txt","sha256":"c75e82c5f53bcec8148820fadf0d65935336ee2031fa6ce10504797ed4c1979d"}},"tags":["nested-reference","unchanged"],"summary":"As IPv6 deployment increases, there will be a dramatic increase in\n the need to use IPv6 addresses in text. While the IPv6 address\n architecture in Section 2.2 of RFC 4291 describes a flexible model\n for text representation of an IPv6 address, this flexibility has been\n causing problems for operators, system engineers, and users. This\n document defines a canonical textual representation format. It does\n not define a format for internal storage, such as within an\n application or database. It is expected that the canonical format\n will be followed by humans and systems when representing IPv6\n addresses as text, but all implementations must accept and be able to\n handle any legitimate RFC 4291 format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commun","scope_keywords":["5952","audit","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5953","folder":"IETF/RFC-5953","source":"IETF/RFC-5953/RFC-5953.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6353","folder":"IETF/RFC-6353","source":"IETF/RFC-6353/RFC-6353.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 5952 As IPv6 deployment increases, there will be a dramatic increase in\n the need to use IPv6 addresses in text. While the IPv6 address\n architecture in Section 2.2 of RFC 4291 describes a flexible model\n for text representation of an IPv6 address, this flexibility has been\n causing problems for operators, system engineers, and users. This\n document defines a canonical textual representation format. It does\n not define a format for internal storage, such as within an\n application or database. It is expected that the canonical format\n will be followed by humans and systems when representing IPv6\n addresses as text, but all implementations must accept and be able to\n handle any legitimate RFC 4291 format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commun 5952 audit http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5954","type":"specification","body":"IETF","designation":"RFC 5954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5954.txt","https://www.rfc-editor.org/rfc/rfc5954.pdf"],"folder":"IETF/RFC-5954","files":{"txt":{"path":"standards/IETF/RFC-5954/RFC-5954.txt","sha256":"aef25c159111f744004b416a974fd5ec1cd3218cf2af7a4d8cd0112844a063a4"}},"tags":["nested-reference","unchanged"],"summary":"This document corrects the Augmented Backus-Naur Form (ABNF)\n production rule associated with generating IPv6 literals in RFC 3261.\n It also clarifies the rule for Uniform Resource Identifier (URI)\n comparison when the URIs contain textual representation of IP\n addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5954.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the perso","scope_keywords":["5954","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 5954 This document corrects the Augmented Backus-Naur Form (ABNF)\n production rule associated with generating IPv6 literals in RFC 3261.\n It also clarifies the rule for Uniform Resource Identifier (URI)\n comparison when the URIs contain textual representation of IP\n addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5954.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the perso 5954 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5956","type":"specification","body":"IETF","designation":"RFC 5956","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5956.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5956.txt","https://www.rfc-editor.org/rfc/rfc5956.pdf"],"folder":"IETF/RFC-5956","files":{"txt":{"path":"standards/IETF/RFC-5956/RFC-5956.txt","sha256":"62b01ccd8cfd173a7049f2162faf9226ee92b44208ec07df9f6eb40822faf9bb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the semantics for grouping the associated\n source and FEC-based (Forward Error Correction) repair flows in the\n Session Description Protocol (SDP). The semantics defined in this\n document are to be used with the SDP Grouping Framework (RFC 5888).\n These semantics allow the description of grouping relationships\n between the source and repair flows when one or more source and/or\n repair flows are associated in the same group, and they provide\n support for additive repair flows. SSRC-level (Synchronization\n Source) grouping semantics are also defined in this document for\n Real-time Transport Protocol (RTP) streams using SSRC multiplexing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and ha","scope_keywords":["5956","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6015","folder":"IETF/RFC-6015","source":"IETF/RFC-6015/RFC-6015.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 5956 This document defines the semantics for grouping the associated\n source and FEC-based (Forward Error Correction) repair flows in the\n Session Description Protocol (SDP). The semantics defined in this\n document are to be used with the SDP Grouping Framework (RFC 5888).\n These semantics allow the description of grouping relationships\n between the source and repair flows when one or more source and/or\n repair flows are associated in the same group, and they provide\n support for additive repair flows. SSRC-level (Synchronization\n Source) grouping semantics are also defined in this document for\n Real-time Transport Protocol (RTP) streams using SSRC multiplexing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and ha 5956 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5958","type":"specification","body":"IETF","designation":"RFC 5958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5958.txt","https://www.rfc-editor.org/rfc/rfc5958.pdf"],"folder":"IETF/RFC-5958","files":{"txt":{"path":"standards/IETF/RFC-5958/RFC-5958.txt","sha256":"82778b9ce7b34f02b5ae9777bfb9e42579744aebd2e1479f476513864525af67"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the syntax for private-key information and a\n content type for it. Private-key information includes a private key\n for a specified public-key algorithm and a set of attributes. The\n Cryptographic Message Syntax (CMS), as defined in RFC 5652, can be\n used to digitally sign, digest, authenticate, or encrypt the\n asymmetric key format content type. This document obsoletes RFC\n 5208.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedb","scope_keywords":["5958","algorithm","algorithms","attribute","attributes","certificate","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null}],"search_text":"IETF RFC 5958 This document defines the syntax for private-key information and a\n content type for it. Private-key information includes a private key\n for a specified public-key algorithm and a set of attributes. The\n Cryptographic Message Syntax (CMS), as defined in RFC 5652, can be\n used to digitally sign, digest, authenticate, or encrypt the\n asymmetric key format content type. This document obsoletes RFC\n 5208.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedb 5958 algorithm algorithms attribute attributes certificate http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5960","type":"specification","body":"IETF","designation":"RFC 5960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5960.txt","https://www.rfc-editor.org/rfc/rfc5960.pdf"],"folder":"IETF/RFC-5960","files":{"txt":{"path":"standards/IETF/RFC-5960/RFC-5960.txt","sha256":"e26b7a8a8233c55eed3c511adafdc8db06cfaedeac51e2c23afe2ec59b2c9f0d"}},"tags":["nested-reference","unchanged"],"summary":"The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the\n set of MPLS protocol functions applicable to the construction and\n operation of packet-switched transport networks. This document\n specifies the subset of these functions that comprises the MPLS-TP\n data plane: the architectural layer concerned with the encapsulation\n and forwarding of packets within an MPLS-TP network.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task F","scope_keywords":["5960","http","key","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6905","folder":"IETF/RFC-6905","source":"IETF/RFC-6905/RFC-6905.txt","version":null}],"search_text":"IETF RFC 5960 The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the\n set of MPLS protocol functions applicable to the construction and\n operation of packet-switched transport networks. This document\n specifies the subset of these functions that comprises the MPLS-TP\n data plane: the architectural layer concerned with the encapsulation\n and forwarding of packets within an MPLS-TP network.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task F 5960 http key license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5964","type":"specification","body":"IETF","designation":"RFC 5964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5964.txt","https://www.rfc-editor.org/rfc/rfc5964.pdf"],"folder":"IETF/RFC-5964","files":{"txt":{"path":"standards/IETF/RFC-5964/RFC-5964.txt","sha256":"5b74ff44d53fc20d9303079b4fadc369074d2b990c89cd762849432a9b7d5a42"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how holes can be specified in geodetic\n service boundaries. One means of implementing a search solution in a\n service database, such as one might provide with a Location-to-\n Service Translation (LoST) server, is described.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5964.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n doc","scope_keywords":["5964","algorithm","http","key","license","presentation","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null}],"search_text":"IETF RFC 5964 This document describes how holes can be specified in geodetic\n service boundaries. One means of implementing a search solution in a\n service database, such as one might provide with a Location-to-\n Service Translation (LoST) server, is described.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5964.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n doc 5964 algorithm http key license presentation profile subject trust nested-reference unchanged"},{"id":"IETF RFC 5967","type":"specification","body":"IETF","designation":"RFC 5967","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5967.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5967.txt","https://www.rfc-editor.org/rfc/rfc5967.pdf"],"folder":"IETF/RFC-5967","files":{"txt":{"path":"standards/IETF/RFC-5967/RFC-5967.txt","sha256":"f894be62e8bf81cda67d51bda51486dc98058161fc098782a8e32a0d6b7314b3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a media type used to carry PKCS #10\n certification requests as defined in RFC 2986. It carries over the\n original specification from RFC 2311, which recently has been moved\n to Historic status, and properly links it to RFC 2986.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.","scope_keywords":["5967","certificate","certificates","crl","http","key","license","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 5967 This document specifies a media type used to carry PKCS #10\n certification requests as defined in RFC 2986. It carries over the\n original specification from RFC 2311, which recently has been moved\n to Historic status, and properly links it to RFC 2986.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor. 5967 certificate certificates crl http key license revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 5983","type":"specification","body":"IETF","designation":"RFC 5983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5983.txt","https://www.rfc-editor.org/rfc/rfc5983.pdf"],"folder":"IETF/RFC-5983","files":{"txt":{"path":"standards/IETF/RFC-5983/RFC-5983.txt","sha256":"66a766db2a979f0e4ee32ae77552afddee64b5c3125c3fdae9f78c04e956b351"}},"tags":["nested-reference","unchanged"],"summary":"This document describes considerations for mailing lists with the\n introduction of internationalized email addresses.\n\n This document makes some specific recommendations on how mailing\n lists should act in various situations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any e","scope_keywords":["5983","http","identification","license","path","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null}],"search_text":"IETF RFC 5983 This document describes considerations for mailing lists with the\n introduction of internationalized email addresses.\n\n This document makes some specific recommendations on how mailing\n lists should act in various situations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any e 5983 http identification license path policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5989","type":"specification","body":"IETF","designation":"RFC 5989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5989.txt","https://www.rfc-editor.org/rfc/rfc5989.pdf"],"folder":"IETF/RFC-5989","files":{"txt":{"path":"standards/IETF/RFC-5989/RFC-5989.txt","sha256":"7dec4687ef73eb2e1fd132a7b2d6d0f25f4999484c64f90b933b8f773605d5fa"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) is increasingly being used in\n systems that are tightly coupled with Hypertext Transport Protocol\n (HTTP) servers for a variety of reasons. In many of these cases,\n applications can benefit from being able to discover, in near real-\n time, when a specific HTTP resource is created, changed, or deleted.\n This document proposes a mechanism, based on the SIP Event Framework,\n for doing so.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and","scope_keywords":["5989","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7641","folder":"IETF/RFC-7641","source":"IETF/RFC-7641/RFC-7641.txt","version":null}],"search_text":"IETF RFC 5989 The Session Initiation Protocol (SIP) is increasingly being used in\n systems that are tightly coupled with Hypertext Transport Protocol\n (HTTP) servers for a variety of reasons. In many of these cases,\n applications can benefit from being able to discover, in near real-\n time, when a specific HTTP resource is created, changed, or deleted.\n This document proposes a mechanism, based on the SIP Event Framework,\n for doing so.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and 5989 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5990","type":"specification","body":"IETF","designation":"RFC 5990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5990.txt","https://www.rfc-editor.org/rfc/rfc5990.pdf"],"folder":"IETF/RFC-5990","files":{"txt":{"path":"standards/IETF/RFC-5990/RFC-5990.txt","sha256":"bfb806a0e7fcd6956c92bdbd4497ce8398fe3dbb13e7681767ed184f723b8281"}},"tags":["nested-reference","unchanged"],"summary":"The RSA-KEM Key Transport Algorithm is a one-pass (store-and-forward)\n mechanism for transporting keying data to a recipient using the\n recipient's RSA public key. (\"KEM\" stands for \"key encapsulation\n mechanism\".) This document specifies the conventions for using the\n RSA-KEM Key Transport Algorithm with the Cryptographic Message Syntax\n (CMS). The ASN.1 syntax is aligned with an expected forthcoming\n change to American National Standard (ANS) X9.44.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of th","scope_keywords":["5990","algorithm","algorithms","attribute","attributes","certificate","certificates","encryption","http","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 5990 The RSA-KEM Key Transport Algorithm is a one-pass (store-and-forward)\n mechanism for transporting keying data to a recipient using the\n recipient's RSA public key. (\"KEM\" stands for \"key encapsulation\n mechanism\".) This document specifies the conventions for using the\n RSA-KEM Key Transport Algorithm with the Cryptographic Message Syntax\n (CMS). The ASN.1 syntax is aligned with an expected forthcoming\n change to American National Standard (ANS) X9.44.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of th 5990 algorithm algorithms attribute attributes certificate certificates encryption http key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6010","type":"specification","body":"IETF","designation":"RFC 6010","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6010.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6010.txt","https://www.rfc-editor.org/rfc/rfc6010.pdf"],"folder":"IETF/RFC-6010","files":{"txt":{"path":"standards/IETF/RFC-6010/RFC-6010.txt","sha256":"c3de9efaeaa466a6b10bd4c93f6c9cfef0c947847b72c1a4d9981333a2cc3c88"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax and semantics for the\n Cryptographic Message Syntax (CMS) content constraints extension.\n This extension is used to determine whether a public key is\n appropriate to use in the processing of a protected content. In\n particular, the CMS content constraints extension is one part of the\n authorization decision; it is used when validating a digital\n signature on a CMS SignedData content or validating a message\n authentication code (MAC) on a CMS AuthenticatedData content or CMS\n AuthEnvelopedData content. The signed or authenticated content type\n is identified by an ASN.1 object identifier, and this extension\n indicates the content types that the public key is authorized to\n validate. If the authorization check is successful, the CMS content\n constraints extension also provides default values for absent\n attributes.\n\nStatus of This Memo\n\n This is an Interne","scope_keywords":["6010","attribute","attributes","authentication","authorization","certificate","certificates","http","key","license","management","path","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null}],"search_text":"IETF RFC 6010 This document specifies the syntax and semantics for the\n Cryptographic Message Syntax (CMS) content constraints extension.\n This extension is used to determine whether a public key is\n appropriate to use in the processing of a protected content. In\n particular, the CMS content constraints extension is one part of the\n authorization decision; it is used when validating a digital\n signature on a CMS SignedData content or validating a message\n authentication code (MAC) on a CMS AuthenticatedData content or CMS\n AuthEnvelopedData content. The signed or authenticated content type\n is identified by an ASN.1 object identifier, and this extension\n indicates the content types that the public key is authorized to\n validate. If the authorization check is successful, the CMS content\n constraints extension also provides default values for absent\n attributes.\n\nStatus of This Memo\n\n This is an Interne 6010 attribute attributes authentication authorization certificate certificates http key license management path signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6019","type":"specification","body":"IETF","designation":"RFC 6019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6019.txt","https://www.rfc-editor.org/rfc/rfc6019.pdf"],"folder":"IETF/RFC-6019","files":{"txt":{"path":"standards/IETF/RFC-6019/RFC-6019.txt","sha256":"1e487b9803e80adcd0172a7ff08a4579e557fce7283bd5a97efa2e09de98ce3d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new ASN.1 type for representing time:\n BinaryTime. This document also specifies an alternate to the\n signing-time attribute for use with the Cryptographic Message Syntax\n (CMS) SignedData and AuthenticatedData content types; the binary-\n signing-time attribute uses BinaryTime. CMS and the signing-time\n attribute are defined in RFC 5652.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.","scope_keywords":["6019","attribute","attributes","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null}],"search_text":"IETF RFC 6019 This document specifies a new ASN.1 type for representing time:\n BinaryTime. This document also specifies an alternate to the\n signing-time attribute for use with the Cryptographic Message Syntax\n (CMS) SignedData and AuthenticatedData content types; the binary-\n signing-time attribute uses BinaryTime. CMS and the signing-time\n attribute are defined in RFC 5652.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www. 6019 attribute attributes http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6020","type":"specification","body":"IETF","designation":"RFC 6020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6020.txt","https://www.rfc-editor.org/rfc/rfc6020.pdf"],"folder":"IETF/RFC-6020","files":{"txt":{"path":"standards/IETF/RFC-6020/RFC-6020.txt","sha256":"6a9c3025372315a2d4404ee95cb4cb6be58c8228dd42b3898a9393473419eb8c"}},"tags":["nested-reference","unchanged"],"summary":"YANG is a data modeling language used to model configuration and\n state data manipulated by the Network Configuration Protocol\n (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6020.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This documen","scope_keywords":["6020","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6087","folder":"IETF/RFC-6087","source":"IETF/RFC-6087/RFC-6087.txt","version":null},{"body":"IETF","designation":"RFC 6095","folder":"IETF/RFC-6095","source":"IETF/RFC-6095/RFC-6095.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6243","folder":"IETF/RFC-6243","source":"IETF/RFC-6243/RFC-6243.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 6020 YANG is a data modeling language used to model configuration and\n state data manipulated by the Network Configuration Protocol\n (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6020.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This documen 6020 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6024","type":"specification","body":"IETF","designation":"RFC 6024","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6024.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6024.txt","https://www.rfc-editor.org/rfc/rfc6024.pdf"],"folder":"IETF/RFC-6024","files":{"txt":{"path":"standards/IETF/RFC-6024/RFC-6024.txt","sha256":"3a6be6f5700477403befc711f49ea1d4411c130dfac52811730c96f0f6435d8b"}},"tags":["nested-reference","unchanged"],"summary":"A trust anchor represents an authoritative entity via a public key\n and associated data. The public key is used to verify digital\n signatures, and the associated data is used to constrain the types of\n information for which the trust anchor is authoritative. A relying\n party uses trust anchors to determine if a digitally signed object is\n valid by verifying a digital signature using the trust anchor's\n public key, and by enforcing the constraints expressed in the\n associated data for the trust anchor. This document describes some\n of the problems associated with the lack of a standard trust anchor\n management mechanism and defines requirements for data formats and\n push-based protocols designed to address these problems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the I","scope_keywords":["6024","authentication","certificate","certificates","crl","encryption","http","key","license","management","path","policies","revocation","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null}],"search_text":"IETF RFC 6024 A trust anchor represents an authoritative entity via a public key\n and associated data. The public key is used to verify digital\n signatures, and the associated data is used to constrain the types of\n information for which the trust anchor is authoritative. A relying\n party uses trust anchors to determine if a digitally signed object is\n valid by verifying a digital signature using the trust anchor's\n public key, and by enforcing the constraints expressed in the\n associated data for the trust anchor. This document describes some\n of the problems associated with the lack of a standard trust anchor\n management mechanism and defines requirements for data formats and\n push-based protocols designed to address these problems.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the I 6024 authentication certificate certificates crl encryption http key license management path policies revocation signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 6027","type":"specification","body":"IETF","designation":"RFC 6027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6027.txt","https://www.rfc-editor.org/rfc/rfc6027.pdf"],"folder":"IETF/RFC-6027","files":{"txt":{"path":"standards/IETF/RFC-6027/RFC-6027.txt","sha256":"ba1acc2c72dc77b4b426ad1d6c8d6e3eddba54d72483cc2bff5e11577e3faf42"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the terminology, problem statement, and\n requirements for implementing Internet Key Exchange (IKE) and IPsec\n on clusters. It also describes gaps in existing standards and their\n implementation that need to be filled in order to allow peers to\n interoperate with clusters from different vendors. Agreed upon\n terminology, problem statement, and requirements will allow IETF\n working groups to consider development of IPsec/IKEv2 mechanisms to\n simplify cluster implementations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n ","scope_keywords":["6027","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 6027 This document defines the terminology, problem statement, and\n requirements for implementing Internet Key Exchange (IKE) and IPsec\n on clusters. It also describes gaps in existing standards and their\n implementation that need to be filled in order to allow peers to\n interoperate with clusters from different vendors. Agreed upon\n terminology, problem statement, and requirements will allow IETF\n working groups to consider development of IPsec/IKEv2 mechanisms to\n simplify cluster implementations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n  6027 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6030","type":"specification","body":"IETF","designation":"RFC 6030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6030.txt","https://www.rfc-editor.org/rfc/rfc6030.pdf"],"folder":"IETF/RFC-6030","files":{"txt":{"path":"standards/IETF/RFC-6030/RFC-6030.txt","sha256":"4fa2d8b23db36bf5699e03b1480a4e7620b60b2f4f165cb2fefe65398daa661f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a symmetric key format for the transport and\n provisioning of symmetric keys to different types of crypto modules.\n For example, One-Time Password (OTP) shared secrets or symmetric\n cryptographic keys to strong authentication devices. A standard key\n transport format enables enterprises to deploy best-of-breed\n solutions combining components from different vendors into the same\n infrastructure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how ","scope_keywords":["6030","algorithm","algorithms","authentication","encryption","http","identification","key","keys","license","policy","profile","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null}],"search_text":"IETF RFC 6030 This document specifies a symmetric key format for the transport and\n provisioning of symmetric keys to different types of crypto modules.\n For example, One-Time Password (OTP) shared secrets or symmetric\n cryptographic keys to strong authentication devices. A standard key\n transport format enables enterprises to deploy best-of-breed\n solutions combining components from different vendors into the same\n infrastructure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how  6030 algorithm algorithms authentication encryption http identification key keys license policy profile signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6031","type":"specification","body":"IETF","designation":"RFC 6031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6031.txt","https://www.rfc-editor.org/rfc/rfc6031.pdf"],"folder":"IETF/RFC-6031","files":{"txt":{"path":"standards/IETF/RFC-6031/RFC-6031.txt","sha256":"3592109a6d700b5e0cad876d9b4499123f1bb7f779405cce4ba19de06fd88295"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the symmetric key format content type. It is\n transport independent. The Cryptographic Message Syntax (CMS) can be\n used to digitally sign, digest, authenticate, or encrypt this content\n type.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6031.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserve","scope_keywords":["6031","algorithm","attribute","attributes","http","issuer","key","keys","license","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 6031 This document defines the symmetric key format content type. It is\n transport independent. The Cryptographic Message Syntax (CMS) can be\n used to digitally sign, digest, authenticate, or encrypt this content\n type.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6031.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserve 6031 algorithm attribute attributes http issuer key keys license policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6034","type":"specification","body":"IETF","designation":"RFC 6034","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6034.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6034.txt","https://www.rfc-editor.org/rfc/rfc6034.pdf"],"folder":"IETF/RFC-6034","files":{"txt":{"path":"standards/IETF/RFC-6034/RFC-6034.txt","sha256":"de193c9c04577c99cda75b409806c26f1c460ccf54d447aa6d4b137cfa2b71d6"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to the multicast addressing\n architecture of the IP Version 4 protocol. The extension presented\n in this document allows for unicast-prefix-based assignment of\n multicast addresses. By delegating multicast addresses at the same\n time as unicast prefixes, network operators will be able to identify\n their multicast addresses without needing to run an inter-domain\n allocation protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and ","scope_keywords":["6034","audit","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7042","folder":"IETF/RFC-7042","source":"IETF/RFC-7042/RFC-7042.txt","version":null},{"body":"IETF","designation":"RFC 9542","folder":"IETF/RFC-9542","source":"IETF/RFC-9542/RFC-9542.txt","version":null}],"search_text":"IETF RFC 6034 This specification defines an extension to the multicast addressing\n architecture of the IP Version 4 protocol. The extension presented\n in this document allows for unicast-prefix-based assignment of\n multicast addresses. By delegating multicast addresses at the same\n time as unicast prefixes, network operators will be able to identify\n their multicast addresses without needing to run an inter-domain\n allocation protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and  6034 audit http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6035","type":"specification","body":"IETF","designation":"RFC 6035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6035.txt","https://www.rfc-editor.org/rfc/rfc6035.pdf"],"folder":"IETF/RFC-6035","files":{"txt":{"path":"standards/IETF/RFC-6035/RFC-6035.txt","sha256":"0739f0bd83a5c3c69c7740b4e52de668805416628b6352960ff6ec46a4c042e6"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Session Initiation Protocol (SIP) event\n package that enables the collection and reporting of metrics that\n measure the quality for Voice over Internet Protocol (VoIP) sessions.\n Voice call quality information derived from RTP Control Protocol\n Extended Reports (RTCP-XR) and call information from SIP is conveyed\n from a User Agent (UA) in a session, known as a reporter, to a third\n party, known as a collector. A registration for the application/ vq-\n rtcpxr media type is also included.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section ","scope_keywords":["6035","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null}],"search_text":"IETF RFC 6035 This document defines a Session Initiation Protocol (SIP) event\n package that enables the collection and reporting of metrics that\n measure the quality for Voice over Internet Protocol (VoIP) sessions.\n Voice call quality information derived from RTP Control Protocol\n Extended Reports (RTCP-XR) and call information from SIP is conveyed\n from a User Agent (UA) in a session, known as a reporter, to a third\n party, known as a collector. A registration for the application/ vq-\n rtcpxr media type is also included.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section  6035 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6042","type":"specification","body":"IETF","designation":"RFC 6042","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6042.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6042.txt","https://www.rfc-editor.org/rfc/rfc6042.pdf"],"folder":"IETF/RFC-6042","files":{"txt":{"path":"standards/IETF/RFC-6042/RFC-6042.txt","sha256":"b29dde4e691a3f807300ba636f2fc85a93ffd4a6b980ccff7fd29e22d10684a8"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the use of the KeyNote trust-management\n system as an authorization extension in the Transport Layer Security\n (TLS) Handshake Protocol, according to guidelines in RFC 5878.\n Extensions carried in the client and server hello messages confirm\n that both parties support the desired authorization data types.\n Then, if supported by both the client and the server, KeyNote\n credentials are exchanged in the supplemental data handshake message.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate f","scope_keywords":["6042","authentication","authorization","certificate","credential","credentials","hash","http","issuer","key","keys","license","management","policy","profile","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7562","folder":"IETF/RFC-7562","source":"IETF/RFC-7562/RFC-7562.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6042 This document specifies the use of the KeyNote trust-management\n system as an authorization extension in the Transport Layer Security\n (TLS) Handshake Protocol, according to guidelines in RFC 5878.\n Extensions carried in the client and server hello messages confirm\n that both parties support the desired authorization data types.\n Then, if supported by both the client and the server, KeyNote\n credentials are exchanged in the supplemental data handshake message.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate f 6042 authentication authorization certificate credential credentials hash http issuer key keys license management policy profile registered nested-reference unchanged"},{"id":"IETF RFC 6046","type":"specification","body":"IETF","designation":"RFC 6046","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6046.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6046.txt","https://www.rfc-editor.org/rfc/rfc6046.pdf"],"folder":"IETF/RFC-6046","files":{"txt":{"path":"standards/IETF/RFC-6046/RFC-6046.txt","sha256":"5a34805afcd69aed22c621817368a4de7b3e81808a0cc98e5e317c3652979127"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) defines a\n common XML format for document exchange, and Real-time Inter-network\n Defense (RID) defines extensions to IODEF intended for the\n cooperative handling of security incidents within consortia of\n network operators and enterprises. This document specifies a\n transport protocol for RID based upon the passing of RID messages\n over HTTP/TLS (Transport Layer Security).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan","scope_keywords":["6046","authorization","http","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6045","folder":"IETF/RFC-6045","source":"IETF/RFC-6045/RFC-6045.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null}],"search_text":"IETF RFC 6046 The Incident Object Description Exchange Format (IODEF) defines a\n common XML format for document exchange, and Real-time Inter-network\n Defense (RID) defines extensions to IODEF intended for the\n cooperative handling of security incidents within consortia of\n network operators and enterprises. This document specifies a\n transport protocol for RID based upon the passing of RID messages\n over HTTP/TLS (Transport Layer Security).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan 6046 authorization http key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6049","type":"specification","body":"IETF","designation":"RFC 6049","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6049.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6049.txt","https://www.rfc-editor.org/rfc/rfc6049.pdf"],"folder":"IETF/RFC-6049","files":{"txt":{"path":"standards/IETF/RFC-6049/RFC-6049.txt","sha256":"1d476d8a730f682f07bb9f9f81cf7c82e9ae9c4dcfbc3f7f8f3446dd60f1c910"}},"tags":["nested-reference","unchanged"],"summary":"This memo utilizes IP performance metrics that are applicable to both\n complete paths and sub-paths, and it defines relationships to compose\n a complete path metric from the sub-path metrics with some accuracy\n with regard to the actual metrics. This is called \"spatial\n composition\" in RFC 2330. The memo refers to the framework for\n metric composition, and provides background and motivation for\n combining metrics to derive others. The descriptions of several\n composed metrics and statistics follow.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 57","scope_keywords":["6049","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null}],"search_text":"IETF RFC 6049 This memo utilizes IP performance metrics that are applicable to both\n complete paths and sub-paths, and it defines relationships to compose\n a complete path metric from the sub-path metrics with some accuracy\n with regard to the actual metrics. This is called \"spatial\n composition\" in RFC 2330. The memo refers to the framework for\n metric composition, and provides background and motivation for\n combining metrics to derive others. The descriptions of several\n composed metrics and statistics follow.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 57 6049 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6051","type":"specification","body":"IETF","designation":"RFC 6051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6051.txt","https://www.rfc-editor.org/rfc/rfc6051.pdf"],"folder":"IETF/RFC-6051","files":{"txt":{"path":"standards/IETF/RFC-6051/RFC-6051.txt","sha256":"ec60cd09b05baff5aea1a15f629a4adb084df72a67f531e34dc6fbf8e6cf95ab"}},"tags":["nested-reference","unchanged"],"summary":"This memo outlines how RTP sessions are synchronised, and discusses\n how rapidly such synchronisation can occur. We show that most RTP\n sessions can be synchronised immediately, but that the use of video\n switching multipoint conference units (MCUs) or large source-specific\n multicast (SSM) groups can greatly increase the synchronisation\n delay. This increase in delay can be unacceptable to some\n applications that use layered and/or multi-description codecs.\n\n This memo introduces three mechanisms to reduce the synchronisation\n delay for such sessions. First, it updates the RTP Control Protocol\n (RTCP) timing rules to reduce the initial synchronisation delay for\n SSM sessions. Second, a new feedback packet is defined for use with\n the extended RTP profile for RTCP-based feedback (RTP/AVPF), allowing\n video switching MCUs to rapidly request resynchronisation. Finally,\n new RTP header exte","scope_keywords":["6051","delivery","http","key","license","pid","presentation","profile","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 6051 This memo outlines how RTP sessions are synchronised, and discusses\n how rapidly such synchronisation can occur. We show that most RTP\n sessions can be synchronised immediately, but that the use of video\n switching multipoint conference units (MCUs) or large source-specific\n multicast (SSM) groups can greatly increase the synchronisation\n delay. This increase in delay can be unacceptable to some\n applications that use layered and/or multi-description codecs.\n\n This memo introduces three mechanisms to reduce the synchronisation\n delay for such sessions. First, it updates the RTP Control Protocol\n (RTCP) timing rules to reduce the initial synchronisation delay for\n SSM sessions. Second, a new feedback packet is defined for use with\n the extended RTP profile for RTCP-based feedback (RTP/AVPF), allowing\n video switching MCUs to rapidly request resynchronisation. Finally,\n new RTP header exte 6051 delivery http key license pid presentation profile subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6054","type":"specification","body":"IETF","designation":"RFC 6054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6054.txt","https://www.rfc-editor.org/rfc/rfc6054.pdf"],"folder":"IETF/RFC-6054","files":{"txt":{"path":"standards/IETF/RFC-6054/RFC-6054.txt","sha256":"16fd0b197ca8ca996f980e2fde4a2787f38ea87a2baf5b06f7c118bf25676fb1"}},"tags":["nested-reference","unchanged"],"summary":"Counter modes have been defined for block ciphers such as the\n Advanced Encryption Standard (AES). Counter modes use a counter,\n which is typically assumed to be incremented by a single sender.\n This memo describes the use of counter modes when applied to the\n Encapsulating Security Payload (ESP) and Authentication Header (AH)\n in multiple-sender group applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://","scope_keywords":["6054","authentication","encryption","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6407","folder":"IETF/RFC-6407","source":"IETF/RFC-6407/RFC-6407.txt","version":null}],"search_text":"IETF RFC 6054 Counter modes have been defined for block ciphers such as the\n Advanced Encryption Standard (AES). Counter modes use a counter,\n which is typically assumed to be incremented by a single sender.\n This memo describes the use of counter modes when applied to the\n Encapsulating Security Payload (ESP) and Authentication Header (AH)\n in multiple-sender group applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:// 6054 authentication encryption http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6059","type":"specification","body":"IETF","designation":"RFC 6059","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6059.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6059.txt","https://www.rfc-editor.org/rfc/rfc6059.pdf"],"folder":"IETF/RFC-6059","files":{"txt":{"path":"standards/IETF/RFC-6059/RFC-6059.txt","sha256":"2becd91e902540b3f925a05e8b44c9716a6c3bf17f4b0fc1ae9bf08b80e6203d"}},"tags":["nested-reference","unchanged"],"summary":"Detecting Network Attachment allows hosts to assess if its existing\n addressing or routing configuration is valid for a newly connected\n network. This document provides simple procedures for Detecting\n Network Attachment in IPv6 hosts, and procedures for routers to\n support such services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6059.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Tr","scope_keywords":["6059","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 6059 Detecting Network Attachment allows hosts to assess if its existing\n addressing or routing configuration is valid for a newly connected\n network. This document provides simple procedures for Detecting\n Network Attachment in IPv6 hosts, and procedures for routers to\n support such services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6059.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Tr 6059 http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 6062","type":"specification","body":"IETF","designation":"RFC 6062","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6062.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6062.txt","https://www.rfc-editor.org/rfc/rfc6062.pdf"],"folder":"IETF/RFC-6062","files":{"txt":{"path":"standards/IETF/RFC-6062/RFC-6062.txt","sha256":"5ce6f4df62461d9591339626198f744ac83b54e485aaeea884389b6f53577384"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension of Traversal Using Relays\n around NAT (TURN), a relay protocol for Network Address Translator\n (NAT) traversal. This extension allows a TURN client to request TCP\n allocations, and defines new requests and indications for the TURN\n server to open and accept TCP connections with the client's peers.\n TURN and this extension both purposefully restrict the ways in which\n the relayed address can be used. In particular, it prevents users\n from running general-purpose servers from ports obtained from the\n TURN server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n I","scope_keywords":["6062","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null}],"search_text":"IETF RFC 6062 This specification defines an extension of Traversal Using Relays\n around NAT (TURN), a relay protocol for Network Address Translator\n (NAT) traversal. This extension allows a TURN client to request TCP\n allocations, and defines new requests and indications for the TURN\n server to open and accept TCP connections with the client's peers.\n TURN and this extension both purposefully restrict the ways in which\n the relayed address can be used. In particular, it prevents users\n from running general-purpose servers from ports obtained from the\n TURN server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n I 6062 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6065","type":"specification","body":"IETF","designation":"RFC 6065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6065.txt","https://www.rfc-editor.org/rfc/rfc6065.pdf"],"folder":"IETF/RFC-6065","files":{"txt":{"path":"standards/IETF/RFC-6065/RFC-6065.txt","sha256":"b15aabb6c76d46a6f626c9a527d273390c3401b184906ae1dc9c669c148a604f"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. It describes the use of\n information provided by Authentication, Authorization, and Accounting\n (AAA) services, such as the Remote Authentication Dial-In User\n Service (RADIUS), to dynamically update user-to-group mappings in the\n View-based Access Control Model (VACM).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai","scope_keywords":["6065","authentication","authorization","http","key","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 6065 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols. It describes the use of\n information provided by Authentication, Authorization, and Accounting\n (AAA) services, such as the Remote Authentication Dial-In User\n Service (RADIUS), to dynamically update user-to-group mappings in the\n View-based Access Control Model (VACM).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai 6065 authentication authorization http key license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6073","type":"specification","body":"IETF","designation":"RFC 6073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6073.txt","https://www.rfc-editor.org/rfc/rfc6073.pdf"],"folder":"IETF/RFC-6073","files":{"txt":{"path":"standards/IETF/RFC-6073/RFC-6073.txt","sha256":"1ec851b8c2e4de35265b3e71d737971259a84b2396476d6687bf4173637558e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to connect pseudowires (PWs) between\n different Packet Switched Network (PSN) domains or between two or\n more distinct PW control plane domains, where a control plane domain\n uses a common control plane protocol or instance of that protocol for\n a given PW. The different PW control plane domains may belong to\n independent autonomous systems, or the PSN technology is\n heterogeneous, or a PW might need to be aggregated at a specific PSN\n point. The PW packet data units are simply switched from one PW to\n another without changing the PW payload.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furth","scope_keywords":["6073","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null}],"search_text":"IETF RFC 6073 This document describes how to connect pseudowires (PWs) between\n different Packet Switched Network (PSN) domains or between two or\n more distinct PW control plane domains, where a control plane domain\n uses a common control plane protocol or instance of that protocol for\n a given PW. The different PW control plane domains may belong to\n independent autonomous systems, or the PSN technology is\n heterogeneous, or a PW might need to be aggregated at a specific PSN\n point. The PW packet data units are simply switched from one PW to\n another without changing the PW payload.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furth 6073 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6074","type":"specification","body":"IETF","designation":"RFC 6074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6074.txt","https://www.rfc-editor.org/rfc/rfc6074.pdf"],"folder":"IETF/RFC-6074","files":{"txt":{"path":"standards/IETF/RFC-6074/RFC-6074.txt","sha256":"89037270a82c1969d36dbdd1064061f4b70eee8632eaae5cfde26d183728a954"}},"tags":["nested-reference","unchanged"],"summary":"Provider Provisioned Layer 2 Virtual Private Networks (L2VPNs) may\n have different \"provisioning models\", i.e., models for what\n information needs to be configured in what entities. Once\n configured, the provisioning information is distributed by a\n \"discovery process\". When the discovery process is complete, a\n signaling protocol is automatically invoked to set up the mesh of\n pseudowires (PWs) that form the (virtual) backbone of the L2VPN.\n This document specifies a number of L2VPN provisioning models, and\n further specifies the semantic structure of the endpoint identifiers\n required by each model. It discusses the distribution of these\n identifiers by the discovery process, especially when discovery is\n based on the Border Gateway Protocol (BGP). It then specifies how\n the endpoint identifiers are carried in the two signaling protocols\n that are used to set up PWs, the Label Distribu","scope_keywords":["6074","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null}],"search_text":"IETF RFC 6074 Provider Provisioned Layer 2 Virtual Private Networks (L2VPNs) may\n have different \"provisioning models\", i.e., models for what\n information needs to be configured in what entities. Once\n configured, the provisioning information is distributed by a\n \"discovery process\". When the discovery process is complete, a\n signaling protocol is automatically invoked to set up the mesh of\n pseudowires (PWs) that form the (virtual) backbone of the L2VPN.\n This document specifies a number of L2VPN provisioning models, and\n further specifies the semantic structure of the endpoint identifiers\n required by each model. It discusses the distribution of these\n identifiers by the discovery process, especially when discovery is\n based on the Border Gateway Protocol (BGP). It then specifies how\n the endpoint identifiers are carried in the two signaling protocols\n that are used to set up PWs, the Label Distribu 6074 http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 6084","type":"specification","body":"IETF","designation":"RFC 6084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6084.txt","https://www.rfc-editor.org/rfc/rfc6084.pdf"],"folder":"IETF/RFC-6084","files":{"txt":{"path":"standards/IETF/RFC-6084/RFC-6084.txt","sha256":"dfd0867de127950f934b9fd3c203d2550c9a6dc376ccfab376eed7d931c17b64"}},"tags":["nested-reference","unchanged"],"summary":"The General Internet Signaling Transport (GIST) protocol currently\n uses TCP or Transport Layer Security (TLS) over TCP for Connection\n mode operation. This document describes the usage of GIST over the\n Stream Control Transmission Protocol (SCTP) and Datagram Transport\n Layer Security (DTLS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC","scope_keywords":["6084","delivery","http","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6084 The General Internet Signaling Transport (GIST) protocol currently\n uses TCP or Transport Layer Security (TLS) over TCP for Connection\n mode operation. This document describes the usage of GIST over the\n Stream Control Transmission Protocol (SCTP) and Datagram Transport\n Layer Security (DTLS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 6084 delivery http license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6085","type":"specification","body":"IETF","designation":"RFC 6085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6085.txt","https://www.rfc-editor.org/rfc/rfc6085.pdf"],"folder":"IETF/RFC-6085","files":{"txt":{"path":"standards/IETF/RFC-6085/RFC-6085.txt","sha256":"98e7e4569e6865dd45aff6388dec3412a1ab186209463414294a2b0dfd031fdf"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) S. Gundavelli\nRequest for Comments: 6085 M. Townsley\nUpdates: 2464 O. Troan\nCategory: Standards Track W. Dec\nISSN: 2070-1721 Cisco\n January 2011\n\n Address Mapping of IPv6 Multicast Packets on Ethernet\n\nAbstract\n\n When transmitting an IPv6 packet with a multicast destination\n address, the IPv6 destination address is mapped to an Ethernet link-\n layer multicast address. This document clarifies that a mapping of\n an IPv6 packet with a multicast destination address may in some\n circumstances map to an Ethernet link-layer unicast address.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur","scope_keywords":["6085","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null}],"search_text":"IETF RFC 6085 Internet Engineering Task Force (IETF) S. Gundavelli\nRequest for Comments: 6085 M. Townsley\nUpdates: 2464 O. Troan\nCategory: Standards Track W. Dec\nISSN: 2070-1721 Cisco\n January 2011\n\n Address Mapping of IPv6 Multicast Packets on Ethernet\n\nAbstract\n\n When transmitting an IPv6 packet with a multicast destination\n address, the IPv6 destination address is mapped to an Ethernet link-\n layer multicast address. This document clarifies that a mapping of\n an IPv6 packet with a multicast destination address may in some\n circumstances map to an Ethernet link-layer unicast address.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur 6085 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6087","type":"specification","body":"IETF","designation":"RFC 6087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6087.txt","https://www.rfc-editor.org/rfc/rfc6087.pdf"],"folder":"IETF/RFC-6087","files":{"txt":{"path":"standards/IETF/RFC-6087/RFC-6087.txt","sha256":"b0d20cec767feba2bfeed10914e7288802882d6e8cdaa09cf014c581aa4f0061"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides guidelines for authors and reviewers of Standards\n Track specifications containing YANG data model modules. Applicable\n portions may be used as a basis for reviews of other YANG data model\n documents. Recommendations and procedures are defined, which are\n intended to increase interoperability and usability of Network\n Configuration Protocol (NETCONF) implementations that utilize YANG\n data model modules.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard;","scope_keywords":["6087","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 6087 This memo provides guidelines for authors and reviewers of Standards\n Track specifications containing YANG data model modules. Applicable\n portions may be used as a basis for reviews of other YANG data model\n documents. Recommendations and procedures are defined, which are\n intended to increase interoperability and usability of Network\n Configuration Protocol (NETCONF) implementations that utilize YANG\n data model modules.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; 6087 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6089","type":"specification","body":"IETF","designation":"RFC 6089","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6089.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6089.txt","https://www.rfc-editor.org/rfc/rfc6089.pdf"],"folder":"IETF/RFC-6089","files":{"txt":{"path":"standards/IETF/RFC-6089/RFC-6089.txt","sha256":"813b1ba954b2890d632651bf5e97f9a9fec49f1c7012ce75c4ff28fcefba2b5f"}},"tags":["nested-reference","unchanged"],"summary":"This document introduces extensions to Mobile IPv6 that allow nodes\n to bind one or more flows to a care-of address. These extensions\n allow multihomed nodes to instruct home agents and other Mobile IPv6\n entities to direct inbound flows to specific addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6089.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identifie","scope_keywords":["6089","http","identification","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6294","folder":"IETF/RFC-6294","source":"IETF/RFC-6294/RFC-6294.txt","version":null}],"search_text":"IETF RFC 6089 This document introduces extensions to Mobile IPv6 that allow nodes\n to bind one or more flows to a care-of address. These extensions\n allow multihomed nodes to instruct home agents and other Mobile IPv6\n entities to direct inbound flows to specific addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6089.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identifie 6089 http identification license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6090","type":"specification","body":"IETF","designation":"RFC 6090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6090.txt","https://www.rfc-editor.org/rfc/rfc6090.pdf"],"folder":"IETF/RFC-6090","files":{"txt":{"path":"standards/IETF/RFC-6090/RFC-6090.txt","sha256":"0066fc48d8a4ec03a93234bd5378ab74923863908ef3d2573360ce0dcde465a0"}},"tags":["nested-reference","unchanged"],"summary":"This note describes the fundamental algorithms of Elliptic Curve\n Cryptography (ECC) as they were defined in some seminal references\n from 1994 and earlier. These descriptions may be useful for\n implementing the fundamental algorithms without using any of the\n specialized methods that were developed in following years. Only\n elliptic curves defined over fields of characteristic greater than\n three are in scope; these curves are those used in Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any ","scope_keywords":["6090","algorithm","algorithms","hash","http","key","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7748","folder":"IETF/RFC-7748","source":"IETF/RFC-7748/RFC-7748.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 6090 This note describes the fundamental algorithms of Elliptic Curve\n Cryptography (ECC) as they were defined in some seminal references\n from 1994 and earlier. These descriptions may be useful for\n implementing the fundamental algorithms without using any of the\n specialized methods that were developed in following years. Only\n elliptic curves defined over fields of characteristic greater than\n three are in scope; these curves are those used in Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any  6090 algorithm algorithms hash http key license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6091","type":"specification","body":"IETF","designation":"RFC 6091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6091.txt","https://www.rfc-editor.org/rfc/rfc6091.pdf"],"folder":"IETF/RFC-6091","files":{"txt":{"path":"standards/IETF/RFC-6091/RFC-6091.txt","sha256":"9b4867e203b019f5f988a7a4d17812bb4fe734d294c5a8eae915fad99ff18c13"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines Transport Layer Security (TLS) extensions and\n associated semantics that allow clients and servers to negotiate the\n use of OpenPGP certificates for a TLS session, and specifies how to\n transport OpenPGP certificates via TLS. It also defines the registry\n for non-X.509 certificate types.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee","scope_keywords":["6091","authentication","certificate","certificates","http","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 6091 This memo defines Transport Layer Security (TLS) extensions and\n associated semantics that allow clients and servers to negotiate the\n use of OpenPGP certificates for a TLS session, and specifies how to\n transport OpenPGP certificates via TLS. It also defines the registry\n for non-X.509 certificate types.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide fee 6091 authentication certificate certificates http key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6095","type":"specification","body":"IETF","designation":"RFC 6095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6095.txt","https://www.rfc-editor.org/rfc/rfc6095.pdf"],"folder":"IETF/RFC-6095","files":{"txt":{"path":"standards/IETF/RFC-6095/RFC-6095.txt","sha256":"3a8338d5421a0988865c2463579c462ac343da233672d59f58651dfc88e5382b"}},"tags":["nested-reference","unchanged"],"summary":"YANG -- the Network Configuration Protocol (NETCONF) Data Modeling\n Language -- supports modeling of a tree of data elements that\n represent the configuration and runtime status of a particular\n network element managed via NETCONF. This memo suggests enhancing\n YANG with supplementary modeling features and language abstractions\n with the aim to improve the model extensibility and reuse.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents","scope_keywords":["6095","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 6095 YANG -- the Network Configuration Protocol (NETCONF) Data Modeling\n Language -- supports modeling of a tree of data elements that\n represent the configuration and runtime status of a particular\n network element managed via NETCONF. This memo suggests enhancing\n YANG with supplementary modeling features and language abstractions\n with the aim to improve the model extensibility and reuse.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents 6095 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6096","type":"specification","body":"IETF","designation":"RFC 6096","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6096.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6096.txt","https://www.rfc-editor.org/rfc/rfc6096.pdf"],"folder":"IETF/RFC-6096","files":{"txt":{"path":"standards/IETF/RFC-6096/RFC-6096.txt","sha256":"896d9cd5eed435830d293788e40d28c8de8e0722be245152725fdc0f555aa482"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the procedure for registering chunk flags with\n the Internet Assigned Numbers Authority (IANA) for the Stream Control\n Transmission Protocol (SCTP). It updates RFC 4960 and also defines\n the IANA registry for contents for currently defined chunk types. It\n does not change SCTP in any other way.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6096.\n\nCopyright Notice\n","scope_keywords":["6096","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6525","folder":"IETF/RFC-6525","source":"IETF/RFC-6525/RFC-6525.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null}],"search_text":"IETF RFC 6096 This document defines the procedure for registering chunk flags with\n the Internet Assigned Numbers Authority (IANA) for the Stream Control\n Transmission Protocol (SCTP). It updates RFC 4960 and also defines\n the IANA registry for contents for currently defined chunk types. It\n does not change SCTP in any other way.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6096.\n\nCopyright Notice\n 6096 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6119","type":"specification","body":"IETF","designation":"RFC 6119","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6119.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6119.txt","https://www.rfc-editor.org/rfc/rfc6119.pdf"],"folder":"IETF/RFC-6119","files":{"txt":{"path":"standards/IETF/RFC-6119/RFC-6119.txt","sha256":"c6e0faca359e0b1dd1489df2f9125eac80f5f43a4672f985db84c2ae6405814f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method for exchanging IPv6 traffic\n engineering information using the IS-IS routing protocol. This\n information enables routers in an IS-IS network to calculate traffic-\n engineered routes using IPv6 addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6119.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document autho","scope_keywords":["6119","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 6119 This document specifies a method for exchanging IPv6 traffic\n engineering information using the IS-IS routing protocol. This\n information enables routers in an IS-IS network to calculate traffic-\n engineered routes using IPv6 addresses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6119.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document autho 6119 http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6130","type":"specification","body":"IETF","designation":"RFC 6130","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6130.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6130.txt","https://www.rfc-editor.org/rfc/rfc6130.pdf"],"folder":"IETF/RFC-6130","files":{"txt":{"path":"standards/IETF/RFC-6130/RFC-6130.txt","sha256":"7555e7aaafdccd36088082e798ab87deda5fa772e72b287979788165246c473a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a 1-hop and symmetric 2-hop neighborhood\n discovery protocol (NHDP) for mobile ad hoc networks (MANETs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6130.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relatin","scope_keywords":["6130","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6622","folder":"IETF/RFC-6622","source":"IETF/RFC-6622/RFC-6622.txt","version":null},{"body":"IETF","designation":"RFC 6779","folder":"IETF/RFC-6779","source":"IETF/RFC-6779/RFC-6779.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null},{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 6130 This document describes a 1-hop and symmetric 2-hop neighborhood\n discovery protocol (NHDP) for mobile ad hoc networks (MANETs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6130.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relatin 6130 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6141","type":"specification","body":"IETF","designation":"RFC 6141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6141.txt","https://www.rfc-editor.org/rfc/rfc6141.pdf"],"folder":"IETF/RFC-6141","files":{"txt":{"path":"standards/IETF/RFC-6141/RFC-6141.txt","sha256":"73acacc1812b98f86072a228469dd77d9176ef75c6106a037353440b9db0a295"}},"tags":["nested-reference","unchanged"],"summary":"The procedures for handling SIP re-INVITEs are described in RFC 3261.\n Implementation and deployment experience has uncovered a number of\n issues with the original documentation, and this document provides\n additional procedures that update the original specification to\n address those issues. In particular, this document defines in which\n situations a UAS (User Agent Server) should generate a success\n response and in which situations a UAS should generate an error\n response to a re-INVITE. Additionally, this document defines further\n details of procedures related to target-refresh requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steerin","scope_keywords":["6141","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6337","folder":"IETF/RFC-6337","source":"IETF/RFC-6337/RFC-6337.txt","version":null}],"search_text":"IETF RFC 6141 The procedures for handling SIP re-INVITEs are described in RFC 3261.\n Implementation and deployment experience has uncovered a number of\n issues with the original documentation, and this document provides\n additional procedures that update the original specification to\n address those issues. In particular, this document defines in which\n situations a UAS (User Agent Server) should generate a success\n response and in which situations a UAS should generate an error\n response to a re-INVITE. Additionally, this document defines further\n details of procedures related to target-refresh requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steerin 6141 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6154","type":"specification","body":"IETF","designation":"RFC 6154","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6154.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6154.txt","https://www.rfc-editor.org/rfc/rfc6154.pdf"],"folder":"IETF/RFC-6154","files":{"txt":{"path":"standards/IETF/RFC-6154/RFC-6154.txt","sha256":"c5908ee88071617d19fc847b947b149a58fb2d65366f6c800683c5b8bc3cfc0f"}},"tags":["nested-reference","unchanged"],"summary":"Some IMAP message stores include special-use mailboxes, such as those\n used to hold draft messages or sent messages. Many mail clients\n allow users to specify where draft or sent messages should be put,\n but configuring them requires that the user know which mailboxes the\n server has set aside for these purposes. This extension adds new\n optional mailbox attributes that a server may include in IMAP LIST\n command responses to identify special-use mailboxes to the client,\n easing configuration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n ","scope_keywords":["6154","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 6154 Some IMAP message stores include special-use mailboxes, such as those\n used to hold draft messages or sent messages. Many mail clients\n allow users to specify where draft or sent messages should be put,\n but configuring them requires that the user know which mailboxes the\n server has set aside for these purposes. This extension adds new\n optional mailbox attributes that a server may include in IMAP LIST\n command responses to identify special-use mailboxes to the client,\n easing configuration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n  6154 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6156","type":"specification","body":"IETF","designation":"RFC 6156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6156.txt","https://www.rfc-editor.org/rfc/rfc6156.pdf"],"folder":"IETF/RFC-6156","files":{"txt":{"path":"standards/IETF/RFC-6156/RFC-6156.txt","sha256":"6c4570eb0ebf8a4423dee02dffe118739313d493366ae080c37fd003b10b50e7"}},"tags":["nested-reference","unchanged"],"summary":"This document adds IPv6 support to Traversal Using Relays around NAT\n (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6,\n and IPv6-to-IPv4 relaying. This document defines the REQUESTED-\n ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY\n attribute allows a client to explicitly request the address type the\n TURN server will allocate (e.g., an IPv4-only node may request the\n TURN server to allocate an IPv6 address).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this docume","scope_keywords":["6156","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null}],"search_text":"IETF RFC 6156 This document adds IPv6 support to Traversal Using Relays around NAT\n (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6,\n and IPv6-to-IPv4 relaying. This document defines the REQUESTED-\n ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY\n attribute allows a client to explicitly request the address type the\n TURN server will allocate (e.g., an IPv4-only node may request the\n TURN server to allocate an IPv6 address).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this docume 6156 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6157","type":"specification","body":"IETF","designation":"RFC 6157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6157.txt","https://www.rfc-editor.org/rfc/rfc6157.pdf"],"folder":"IETF/RFC-6157","files":{"txt":{"path":"standards/IETF/RFC-6157/RFC-6157.txt","sha256":"6b4b445d8b13efea2a38be6db7b38365e9d6856ef1ca14acdbcb0ce3ed35d835"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the IPv4 Session Initiation Protocol\n (SIP) user agents can communicate with IPv6 SIP user agents (and vice\n versa) at the signaling layer as well as exchange media once the\n session has been successfully set up. Both single- and dual-stack\n (i.e., IPv4-only and IPv4/IPv6) user agents are considered.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6157.\n\nCopyr","scope_keywords":["6157","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null}],"search_text":"IETF RFC 6157 This document describes how the IPv4 Session Initiation Protocol\n (SIP) user agents can communicate with IPv6 SIP user agents (and vice\n versa) at the signaling layer as well as exchange media once the\n session has been successfully set up. Both single- and dual-stack\n (i.e., IPv4-only and IPv4/IPv6) user agents are considered.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6157.\n\nCopyr 6157 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6164","type":"specification","body":"IETF","designation":"RFC 6164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6164.txt","https://www.rfc-editor.org/rfc/rfc6164.pdf"],"folder":"IETF/RFC-6164","files":{"txt":{"path":"standards/IETF/RFC-6164/RFC-6164.txt","sha256":"029c07e519d8c24c8a2d7a623a66f30b137c36cc3685808396560e2450ffe182"}},"tags":["nested-reference","unchanged"],"summary":"On inter-router point-to-point links, it is useful, for security and\n other reasons, to use 127-bit IPv6 prefixes. Such a practice\n parallels the use of 31-bit prefixes in IPv4. This document\n specifies the motivation for, and usages of, 127-bit IPv6 prefix\n lengths on inter-router point-to-point links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6164.\n\nKohno, et al. Standards Track ","scope_keywords":["6164","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null}],"search_text":"IETF RFC 6164 On inter-router point-to-point links, it is useful, for security and\n other reasons, to use 127-bit IPv6 prefixes. Such a practice\n parallels the use of 31-bit prefixes in IPv4. This document\n specifies the motivation for, and usages of, 127-bit IPv6 prefix\n lengths on inter-router point-to-point links.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6164.\n\nKohno, et al. Standards Track  6164 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6184","type":"specification","body":"IETF","designation":"RFC 6184","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6184.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6184.txt","https://www.rfc-editor.org/rfc/rfc6184.pdf"],"folder":"IETF/RFC-6184","files":{"txt":{"path":"standards/IETF/RFC-6184/RFC-6184.txt","sha256":"6a78cf97bb1aadc36b47ceb14825d4a61c75196c0c7fee7e9c7af4d22152c2be"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an RTP Payload format for the ITU-T\n Recommendation H.264 video codec and the technically identical\n ISO/IEC International Standard 14496-10 video codec, excluding the\n Scalable Video Coding (SVC) extension and the Multiview Video Coding\n extension, for which the RTP payload formats are defined elsewhere.\n The RTP payload format allows for packetization of one or more\n Network Abstraction Layer Units (NALUs), produced by an H.264 video\n encoder, in each RTP payload. The payload format has wide\n applicability, as it supports applications from simple low bitrate\n conversational usage, to Internet video streaming with interleaved\n transmission, to high bitrate video-on-demand.\n\n This memo obsoletes RFC 3984. Changes from RFC 3984 are summarized\n in Section 14. Issues on backward compatibility to RFC 3984 are\n discussed in Section 15.\n\nStatus of This Memo\n\n This is an Int","scope_keywords":["6184","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 6184 This memo describes an RTP Payload format for the ITU-T\n Recommendation H.264 video codec and the technically identical\n ISO/IEC International Standard 14496-10 video codec, excluding the\n Scalable Video Coding (SVC) extension and the Multiview Video Coding\n extension, for which the RTP payload formats are defined elsewhere.\n The RTP payload format allows for packetization of one or more\n Network Abstraction Layer Units (NALUs), produced by an H.264 video\n encoder, in each RTP payload. The payload format has wide\n applicability, as it supports applications from simple low bitrate\n conversational usage, to Internet video streaming with interleaved\n transmission, to high bitrate video-on-demand.\n\n This memo obsoletes RFC 3984. Changes from RFC 3984 are summarized\n in Section 14. Issues on backward compatibility to RFC 3984 are\n discussed in Section 15.\n\nStatus of This Memo\n\n This is an Int 6184 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6188","type":"specification","body":"IETF","designation":"RFC 6188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6188.txt","https://www.rfc-editor.org/rfc/rfc6188.pdf"],"folder":"IETF/RFC-6188","files":{"txt":{"path":"standards/IETF/RFC-6188/RFC-6188.txt","sha256":"54f6def2251cc6480863f778e486ecf5667b0df9c2b9badbb1b1fde154b9b6d7"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n with 192- and 256-bit keys within the Secure RTP (SRTP) protocol. It\n details counter mode encryption for SRTP and Secure Realtime\n Transport Control Protocol (SRTCP) and a new SRTP Key Derivation\n Function (KDF) for AES-192 and AES-256.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6188.\n\nCopyright Notice\n\n Copyrig","scope_keywords":["6188","algorithm","algorithms","encryption","http","key","keys","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 6188 This memo describes the use of the Advanced Encryption Standard (AES)\n with 192- and 256-bit keys within the Secure RTP (SRTP) protocol. It\n details counter mode encryption for SRTP and Secure Realtime\n Transport Control Protocol (SRTCP) and a new SRTP Key Derivation\n Function (KDF) for AES-192 and AES-256.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6188.\n\nCopyright Notice\n\n Copyrig 6188 algorithm algorithms encryption http key keys license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6190","type":"specification","body":"IETF","designation":"RFC 6190","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6190.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6190.txt","https://www.rfc-editor.org/rfc/rfc6190.pdf"],"folder":"IETF/RFC-6190","files":{"txt":{"path":"standards/IETF/RFC-6190/RFC-6190.txt","sha256":"cbb9725a2da98f9939e266506e4e9823c9dc32acce6ec7cc633d79879e4b85a4"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an RTP payload format for Scalable Video Coding\n (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is\n technically identical to Amendment 3 of ISO/IEC International\n Standard 14496-10. The RTP payload format allows for packetization\n of one or more Network Abstraction Layer (NAL) units in each RTP\n packet payload, as well as fragmentation of a NAL unit in multiple\n RTP packets. Furthermore, it supports transmission of an SVC stream\n over a single as well as multiple RTP sessions. The payload format\n defines a new media subtype name \"H264-SVC\", but is still backward\n compatible to RFC 6184 since the base layer, when encapsulated in its\n own RTP stream, must use the H.264 media subtype name (\"H264\") and\n the packetization method specified in RFC 6184. The payload format\n has wide applicability in videoconferencing, Internet video\n streaming, and high-bitr","scope_keywords":["6190","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 6190 This memo describes an RTP payload format for Scalable Video Coding\n (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is\n technically identical to Amendment 3 of ISO/IEC International\n Standard 14496-10. The RTP payload format allows for packetization\n of one or more Network Abstraction Layer (NAL) units in each RTP\n packet payload, as well as fragmentation of a NAL unit in multiple\n RTP packets. Furthermore, it supports transmission of an SVC stream\n over a single as well as multiple RTP sessions. The payload format\n defines a new media subtype name \"H264-SVC\", but is still backward\n compatible to RFC 6184 since the base layer, when encapsulated in its\n own RTP stream, must use the H.264 media subtype name (\"H264\") and\n the packetization method specified in RFC 6184. The payload format\n has wide applicability in videoconferencing, Internet video\n streaming, and high-bitr 6190 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6193","type":"specification","body":"IETF","designation":"RFC 6193","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6193.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6193.txt","https://www.rfc-editor.org/rfc/rfc6193.pdf"],"folder":"IETF/RFC-6193","files":{"txt":{"path":"standards/IETF/RFC-6193/RFC-6193.txt","sha256":"133f04a1830318d0a7dce877bcc3de077432ed1a608bf99a5dc4c7780e080c2d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to establish a media session that\n represents a virtual private network using the Session Initiation\n Protocol for the purpose of on-demand media/application sharing\n between peers. It extends the protocol identifier of the Session\n Description Protocol (SDP) so that it can negotiate use of the\n Internet Key Exchange Protocol (IKE) for media sessions in the SDP\n offer/answer model. It also specifies a method to boot up IKE and\n generate IPsec security associations using a self-signed certificate.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents ","scope_keywords":["6193","authentication","authorization","certificate","certificates","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6193 This document specifies how to establish a media session that\n represents a virtual private network using the Session Initiation\n Protocol for the purpose of on-demand media/application sharing\n between peers. It extends the protocol identifier of the Session\n Description Protocol (SDP) so that it can negotiate use of the\n Internet Key Exchange Protocol (IKE) for media sessions in the SDP\n offer/answer model. It also specifies a method to boot up IKE and\n generate IPsec security associations using a self-signed certificate.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents  6193 authentication authorization certificate certificates http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6206","type":"specification","body":"IETF","designation":"RFC 6206","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6206.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6206.txt","https://www.rfc-editor.org/rfc/rfc6206.pdf"],"folder":"IETF/RFC-6206","files":{"txt":{"path":"standards/IETF/RFC-6206/RFC-6206.txt","sha256":"a38faf4084395f992b8fd2f7e07d5da22184f7251a55287a387a3c9a25337d47"}},"tags":["nested-reference","unchanged"],"summary":"The Trickle algorithm allows nodes in a lossy shared medium (e.g.,\n low-power and lossy networks) to exchange information in a highly\n robust, energy efficient, simple, and scalable manner. Dynamically\n adjusting transmission windows allows Trickle to spread new\n information on the scale of link-layer transmission times while\n sending only a few messages per hour when information does not\n change. A simple suppression mechanism and transmission point\n selection allow Trickle's communication rate to scale logarithmically\n with density. This document describes the Trickle algorithm and\n considerations in its use.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Interne","scope_keywords":["6206","algorithm","http","key","license","pki","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null}],"search_text":"IETF RFC 6206 The Trickle algorithm allows nodes in a lossy shared medium (e.g.,\n low-power and lossy networks) to exchange information in a highly\n robust, energy efficient, simple, and scalable manner. Dynamically\n adjusting transmission windows allows Trickle to spread new\n information on the scale of link-layer transmission times while\n sending only a few messages per hour when information does not\n change. A simple suppression mechanism and transmission point\n selection allow Trickle's communication rate to scale logarithmically\n with density. This document describes the Trickle algorithm and\n considerations in its use.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Interne 6206 algorithm http key license pki subject trust nested-reference unchanged"},{"id":"IETF RFC 6211","type":"specification","body":"IETF","designation":"RFC 6211","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6211.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6211.txt","https://www.rfc-editor.org/rfc/rfc6211.pdf"],"folder":"IETF/RFC-6211","files":{"txt":{"path":"standards/IETF/RFC-6211/RFC-6211.txt","sha256":"d2c431d3529ce01a8bdea3706e88e39c130896dd8d845cfba3a06664c10e6afe"}},"tags":["nested-reference","unchanged"],"summary":"The Cryptographic Message Syntax (CMS), unlike X.509/PKIX\n certificates, is vulnerable to algorithm substitution attacks. In an\n algorithm substitution attack, the attacker changes either the\n algorithm being used or the parameters of the algorithm in order to\n change the result of a signature verification process. In X.509\n certificates, the signature algorithm is protected because it is\n duplicated in the TBSCertificate.signature field with the proviso\n that the validator is to compare both fields as part of the signature\n validation process. This document defines a new attribute that\n contains a copy of the relevant algorithm identifiers so that they\n are protected by the signature or authentication process.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of th","scope_keywords":["6211","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","hash","hashing","http","key","license","pki","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null}],"search_text":"IETF RFC 6211 The Cryptographic Message Syntax (CMS), unlike X.509/PKIX\n certificates, is vulnerable to algorithm substitution attacks. In an\n algorithm substitution attack, the attacker changes either the\n algorithm being used or the parameters of the algorithm in order to\n change the result of a signature verification process. In X.509\n certificates, the signature algorithm is protected because it is\n duplicated in the TBSCertificate.signature field with the proviso\n that the validator is to compare both fields as part of the signature\n validation process. This document defines a new attribute that\n contains a copy of the relevant algorithm identifiers so that they\n are protected by the signature or authentication process.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of th 6211 algorithm algorithms attribute attributes authentication certificate certificates hash hashing http key license pki signature signatures nested-reference unchanged"},{"id":"IETF RFC 6212","type":"specification","body":"IETF","designation":"RFC 6212","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6212.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6212.txt","https://www.rfc-editor.org/rfc/rfc6212.pdf"],"folder":"IETF/RFC-6212","files":{"txt":{"path":"standards/IETF/RFC-6212/RFC-6212.txt","sha256":"5944938d70a926ee709d8330b9faf5f838f58574eaab15135481a367c0c07328"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates the registry of properties in Authentication-\n Results: message header fields to allow relaying of the results of a\n Vouch By Reference query.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6212.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF T","scope_keywords":["6212","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 6212 This memo updates the registry of properties in Authentication-\n Results: message header fields to allow relaying of the results of a\n Vouch By Reference query.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6212.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF T 6212 authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6232","type":"specification","body":"IETF","designation":"RFC 6232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6232.txt","https://www.rfc-editor.org/rfc/rfc6232.pdf"],"folder":"IETF/RFC-6232","files":{"txt":{"path":"standards/IETF/RFC-6232/RFC-6232.txt","sha256":"0aefe9f6a8b0b202c3964338694af4cfa312145b6bf71f47477356d3aecdf0f0"}},"tags":["nested-reference","unchanged"],"summary":"At present, an IS-IS purge does not contain any information\n identifying the Intermediate System (IS) that generates the purge.\n This makes it difficult to locate the source IS.\n\n To address this issue, this document defines a TLV to be added to\n purges to record the system ID of the IS generating it. Since normal\n Link State Protocol Data Unit (LSP) flooding does not change LSP\n contents, this TLV should propagate with the purge.\n\n This document updates RFC 5301, RFC 5304, and RFC 5310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Infor","scope_keywords":["6232","authentication","http","identification","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 6232 At present, an IS-IS purge does not contain any information\n identifying the Intermediate System (IS) that generates the purge.\n This makes it difficult to locate the source IS.\n\n To address this issue, this document defines a TLV to be added to\n purges to record the system ID of the IS generating it. Since normal\n Link State Protocol Data Unit (LSP) flooding does not change LSP\n contents, this TLV should propagate with the purge.\n\n This document updates RFC 5301, RFC 5304, and RFC 5310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Infor 6232 authentication http identification key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6233","type":"specification","body":"IETF","designation":"RFC 6233","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6233.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6233.txt","https://www.rfc-editor.org/rfc/rfc6233.pdf"],"folder":"IETF/RFC-6233","files":{"txt":{"path":"standards/IETF/RFC-6233/RFC-6233.txt","sha256":"e4f12160edf31c7c630b50ddad5d6fdb730835ff72b4b5f3bda31182af770d46"}},"tags":["nested-reference","unchanged"],"summary":"IANA maintains the \"IS-IS TLV Codepoints\" registry. This registry\n documents which TLVs can appear in different types of IS-IS Protocol\n Data Units (PDUs), but does not document which TLVs can be found in\n zero Remaining Lifetime Link State PDUs (LSPs), a.k.a. purges. This\n document extends the existing registry to record the set of TLVs that\n are permissible in purges and updates the rules for generating and\n processing purges in the presence of authentication. This document\n updates RFC 3563, RFC 5304, and RFC 5310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in","scope_keywords":["6233","authentication","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null}],"search_text":"IETF RFC 6233 IANA maintains the \"IS-IS TLV Codepoints\" registry. This registry\n documents which TLVs can appear in different types of IS-IS Protocol\n Data Units (PDUs), but does not document which TLVs can be found in\n zero Remaining Lifetime Link State PDUs (LSPs), a.k.a. purges. This\n document extends the existing registry to record the set of TLVs that\n are permissible in purges and updates the rules for generating and\n processing purges in the presence of authentication. This document\n updates RFC 3563, RFC 5304, and RFC 5310.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in 6233 authentication http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6235","type":"specification","body":"IETF","designation":"RFC 6235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6235.txt","https://www.rfc-editor.org/rfc/rfc6235.pdf"],"folder":"IETF/RFC-6235","files":{"txt":{"path":"standards/IETF/RFC-6235/RFC-6235.txt","sha256":"1a7f04e7ebe1beb08e97307c3011a47f2243e83b56feaac90b5f97583ac55fc1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes anonymization techniques for IP flow data and\n the export of anonymized data using the IP Flow Information Export\n (IPFIX) protocol. It categorizes common anonymization schemes and\n defines the parameters needed to describe them. It provides\n guidelines for the implementation of anonymized data export and\n storage over IPFIX, and describes an information model and Options-\n based method for anonymization metadata export within the IPFIX\n protocol or storage in IPFIX Files.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public rev","scope_keywords":["6235","http","license","management","policies","presentation","risk","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null}],"search_text":"IETF RFC 6235 This document describes anonymization techniques for IP flow data and\n the export of anonymized data using the IP Flow Information Export\n (IPFIX) protocol. It categorizes common anonymization schemes and\n defines the parameters needed to describe them. It provides\n guidelines for the implementation of anonymized data export and\n storage over IPFIX, and describes an information model and Options-\n based method for anonymization metadata export within the IPFIX\n protocol or storage in IPFIX Files.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public rev 6235 http license management policies presentation risk subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6236","type":"specification","body":"IETF","designation":"RFC 6236","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6236.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6236.txt","https://www.rfc-editor.org/rfc/rfc6236.pdf"],"folder":"IETF/RFC-6236","files":{"txt":{"path":"standards/IETF/RFC-6236/RFC-6236.txt","sha256":"4ac21ed4f66e572ec362625d202a6ef22bdde5cf32735ff97f07c95fb5dea098"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a new generic session setup attribute to make\n it possible to negotiate different image attributes such as image\n size. A possible use case is to make it possible for a low-end hand-\n held terminal to display video without the need to rescale the image,\n something that may consume large amounts of memory and processing\n power. The document also helps to maintain an optimal bitrate for\n video as only the image size that is desired by the receiver is\n transmitted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informat","scope_keywords":["6236","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6236 This document proposes a new generic session setup attribute to make\n it possible to negotiate different image attributes such as image\n size. A possible use case is to make it possible for a low-end hand-\n held terminal to display video without the need to rescale the image,\n something that may consume large amounts of memory and processing\n power. The document also helps to maintain an optimal bitrate for\n video as only the image size that is desired by the receiver is\n transmitted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Informat 6236 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6241","type":"specification","body":"IETF","designation":"RFC 6241","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6241.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6241.txt","https://www.rfc-editor.org/rfc/rfc6241.pdf"],"folder":"IETF/RFC-6241","files":{"txt":{"path":"standards/IETF/RFC-6241/RFC-6241.txt","sha256":"989b44560e4663267618b4b6bfc4cf0c7772fa2b59b5980936d9b073cbbd5314"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) defined in this document\n provides mechanisms to install, manipulate, and delete the\n configuration of network devices. It uses an Extensible Markup\n Language (XML)-based data encoding for the configuration data as well\n as the protocol messages. The NETCONF protocol operations are\n realized as remote procedure calls (RPCs). This document obsoletes\n RFC 4741.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["6241","attribute","authentication","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6243","folder":"IETF/RFC-6243","source":"IETF/RFC-6243/RFC-6243.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6536","folder":"IETF/RFC-6536","source":"IETF/RFC-6536/RFC-6536.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 6241 The Network Configuration Protocol (NETCONF) defined in this document\n provides mechanisms to install, manipulate, and delete the\n configuration of network devices. It uses an Extensible Markup\n Language (XML)-based data encoding for the configuration data as well\n as the protocol messages. The NETCONF protocol operations are\n realized as remote procedure calls (RPCs). This document obsoletes\n RFC 4741.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 6241 attribute authentication http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6242","type":"specification","body":"IETF","designation":"RFC 6242","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6242.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6242.txt","https://www.rfc-editor.org/rfc/rfc6242.pdf"],"folder":"IETF/RFC-6242","files":{"txt":{"path":"standards/IETF/RFC-6242/RFC-6242.txt","sha256":"5329ead0bd518e2f4551eab270da40913119ff85f4941fcfa9dadff612be459c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for invoking and running the Network\n Configuration Protocol (NETCONF) within a Secure Shell (SSH) session\n as an SSH subsystem. This document obsoletes RFC 4742.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6242.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["6242","authentication","encryption","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6470","folder":"IETF/RFC-6470","source":"IETF/RFC-6470/RFC-6470.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 6242 This document describes a method for invoking and running the Network\n Configuration Protocol (NETCONF) within a Secure Shell (SSH) session\n as an SSH subsystem. This document obsoletes RFC 4742.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6242.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  6242 authentication encryption http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6243","type":"specification","body":"IETF","designation":"RFC 6243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6243.txt","https://www.rfc-editor.org/rfc/rfc6243.pdf"],"folder":"IETF/RFC-6243","files":{"txt":{"path":"standards/IETF/RFC-6243/RFC-6243.txt","sha256":"9b02c1cc020361751c8173ed57ccaa9f93447dca5bdbb4a4dc20a6de485d6ebb"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) defines ways to read and\n edit configuration data from a NETCONF server. In some cases, part\n of this data may not be set by the NETCONF client, but rather a\n default value known to the server is used instead. In many\n situations the NETCONF client has a priori knowledge about default\n data, so the NETCONF server does not need to save it in a NETCONF\n configuration datastore or send it to the client in a retrieval\n operation reply. In other situations the NETCONF client will need\n this data from the server. Not all server implementations treat this\n default data the same way. This document defines a capability-based\n extension to the NETCONF protocol that allows the NETCONF client to\n identify how defaults are processed by the server, and also defines\n new mechanisms for client control of server processing of default\n data.\n\nStatus of This Mem","scope_keywords":["6243","attribute","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null}],"search_text":"IETF RFC 6243 The Network Configuration Protocol (NETCONF) defines ways to read and\n edit configuration data from a NETCONF server. In some cases, part\n of this data may not be set by the NETCONF client, but rather a\n default value known to the server is used instead. In many\n situations the NETCONF client has a priori knowledge about default\n data, so the NETCONF server does not need to save it in a NETCONF\n configuration datastore or send it to the client in a retrieval\n operation reply. In other situations the NETCONF client will need\n this data from the server. Not all server implementations treat this\n default data the same way. This document defines a capability-based\n extension to the NETCONF protocol that allows the NETCONF client to\n identify how defaults are processed by the server, and also defines\n new mechanisms for client control of server processing of default\n data.\n\nStatus of This Mem 6243 attribute http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6245","type":"specification","body":"IETF","designation":"RFC 6245","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6245.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6245.txt","https://www.rfc-editor.org/rfc/rfc6245.pdf"],"folder":"IETF/RFC-6245","files":{"txt":{"path":"standards/IETF/RFC-6245/RFC-6245.txt","sha256":"e871459435602cd048ddb270e505d12096fca8406fe34a6f5bd735b6bd031f1c"}},"tags":["nested-reference","unchanged"],"summary":"The Generic Routing Encapsulation (GRE) specification contains a Key\n field, which MAY contain a value that is used to identify a\n particular GRE data stream. This specification defines a new Mobile\n IP extension that is used to exchange the value to be used in the GRE\n Key field. This extension further allows the Mobility Agents to set\n up the necessary protocol interfaces prior to receiving the mobile\n node traffic. The new extension allows a Foreign Agent to request\n GRE tunneling without disturbing the Home Agent behavior specified\n for Mobile IPv4. GRE tunneling with the Key field allows the\n operators to have home networks that consist of multiple Virtual\n Private Networks (VPNs), which may have overlapping home addresses.\n When the tuple <Care of Address, Home Address, and Home Agent\n Address> is the same across multiple subscriber sessions, GRE\n tunneling will provide a means for","scope_keywords":["6245","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7364","folder":"IETF/RFC-7364","source":"IETF/RFC-7364/RFC-7364.txt","version":null}],"search_text":"IETF RFC 6245 The Generic Routing Encapsulation (GRE) specification contains a Key\n field, which MAY contain a value that is used to identify a\n particular GRE data stream. This specification defines a new Mobile\n IP extension that is used to exchange the value to be used in the GRE\n Key field. This extension further allows the Mobility Agents to set\n up the necessary protocol interfaces prior to receiving the mobile\n node traffic. The new extension allows a Foreign Agent to request\n GRE tunneling without disturbing the Home Agent behavior specified\n for Mobile IPv4. GRE tunneling with the Key field allows the\n operators to have home networks that consist of multiple Virtual\n Private Networks (VPNs), which may have overlapping home addresses.\n When the tuple <Care of Address, Home Address, and Home Agent\n Address> is the same across multiple subscriber sessions, GRE\n tunneling will provide a means for 6245 authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6263","type":"specification","body":"IETF","designation":"RFC 6263","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6263.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6263.txt","https://www.rfc-editor.org/rfc/rfc6263.pdf"],"folder":"IETF/RFC-6263","files":{"txt":{"path":"standards/IETF/RFC-6263/RFC-6263.txt","sha256":"e1563cbb2205e4e8695cba005852da4b051f15e994a2c7629e7451797b24c98b"}},"tags":["nested-reference","unchanged"],"summary":"This document lists the different mechanisms that enable applications\n using the Real-time Transport Protocol (RTP) and the RTP Control\n Protocol (RTCP) to keep their RTP Network Address Translator (NAT)\n mappings alive. It also makes a recommendation for a preferred\n mechanism. This document is not applicable to Interactive\n Connectivity Establishment (ICE) agents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://","scope_keywords":["6263","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 6263 This document lists the different mechanisms that enable applications\n using the Real-time Transport Protocol (RTP) and the RTP Control\n Protocol (RTCP) to keep their RTP Network Address Translator (NAT)\n mappings alive. It also makes a recommendation for a preferred\n mechanism. This document is not applicable to Interactive\n Connectivity Establishment (ICE) agents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:// 6263 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6267","type":"specification","body":"IETF","designation":"RFC 6267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6267.txt","https://www.rfc-editor.org/rfc/rfc6267.pdf"],"folder":"IETF/RFC-6267","files":{"txt":{"path":"standards/IETF/RFC-6267/RFC-6267.txt","sha256":"b96f36de66c69962d11ece867e39ae54cba65c72c4b8c7a5a3f8f1dd3bb2b9b0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a key management protocol variant for the\n Multimedia Internet KEYing (MIKEY) protocol that relies on a trusted\n key management service. In particular, this variant utilizes\n Identity-Based Authenticated Key Exchange (IBAKE) framework that\n allows the participating clients to perform mutual authentication and\n derive a session key in an asymmetric Identity-Based Encryption (IBE)\n framework. This protocol, in addition to providing mutual\n authentication, eliminates the key escrow problem that is common in\n standard IBE and provides perfect forward and backward secrecy.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has be","scope_keywords":["6267","authentication","certificate","credential","credentials","delivery","encryption","hash","http","key","keys","license","management","pki","policy","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 6267 This document describes a key management protocol variant for the\n Multimedia Internet KEYing (MIKEY) protocol that relies on a trusted\n key management service. In particular, this variant utilizes\n Identity-Based Authenticated Key Exchange (IBAKE) framework that\n allows the participating clients to perform mutual authentication and\n derive a session key in an asymmetric Identity-Based Encryption (IBE)\n framework. This protocol, in addition to providing mutual\n authentication, eliminates the key escrow problem that is common in\n standard IBE and provides perfect forward and backward secrecy.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has be 6267 authentication certificate credential credentials delivery encryption hash http key keys license management pki policy revocation nested-reference unchanged"},{"id":"IETF RFC 6268","type":"specification","body":"IETF","designation":"RFC 6268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6268.txt","https://www.rfc-editor.org/rfc/rfc6268.pdf"],"folder":"IETF/RFC-6268","files":{"txt":{"path":"standards/IETF/RFC-6268/RFC-6268.txt","sha256":"cd7f4a202cdd725fff969eb3aa1f6d9411a1e3ffe08c503594e5b2ab5d9a89cb"}},"tags":["nested-reference","unchanged"],"summary":"The Cryptographic Message Syntax (CMS) format, and many associated\n formats, are expressed using ASN.1. The current ASN.1 modules\n conform to the 1988 version of ASN.1. This document updates some\n auxiliary ASN.1 modules to conform to the 2008 version of ASN.1; the\n 1988 ASN.1 modules remain the normative version. There are no bits-\n on-the-wire changes to any of the formats; this is simply a change to\n the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Sec","scope_keywords":["6268","attribute","attributes","authentication","certificate","http","key","license","pki","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 6268 The Cryptographic Message Syntax (CMS) format, and many associated\n formats, are expressed using ASN.1. The current ASN.1 modules\n conform to the 1988 version of ASN.1. This document updates some\n auxiliary ASN.1 modules to conform to the 2008 version of ASN.1; the\n 1988 ASN.1 modules remain the normative version. There are no bits-\n on-the-wire changes to any of the formats; this is simply a change to\n the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Sec 6268 attribute attributes authentication certificate http key license pki signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6277","type":"specification","body":"IETF","designation":"RFC 6277","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6277.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6277.txt","https://www.rfc-editor.org/rfc/rfc6277.pdf"],"folder":"IETF/RFC-6277","files":{"txt":{"path":"standards/IETF/RFC-6277/RFC-6277.txt","sha256":"9d740a0b140662e6fec787ece258d5936d115d5c1239ee39ecdfbc64538a8afa"}},"tags":["nested-reference","unchanged"],"summary":"The Online Certificate Status Protocol (OCSP) requires server\n responses to be signed but does not specify a mechanism for selecting\n the signature algorithm to be used. This may lead to avoidable\n interoperability failures in contexts where multiple signature\n algorithms are in use. This document specifies rules for server\n signature algorithm selection and an extension that allows a client\n to advise a server that specific signature algorithms are supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current sta","scope_keywords":["6277","algorithm","algorithms","certificate","certificates","crl","hash","hashing","http","key","keys","license","ocsp","revocation","risk","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null}],"search_text":"IETF RFC 6277 The Online Certificate Status Protocol (OCSP) requires server\n responses to be signed but does not specify a mechanism for selecting\n the signature algorithm to be used. This may lead to avoidable\n interoperability failures in contexts where multiple signature\n algorithms are in use. This document specifies rules for server\n signature algorithm selection and an extension that allows a client\n to advise a server that specific signature algorithms are supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current sta 6277 algorithm algorithms certificate certificates crl hash hashing http key keys license ocsp revocation risk signature nested-reference unchanged"},{"id":"IETF RFC 6278","type":"specification","body":"IETF","designation":"RFC 6278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6278.txt","https://www.rfc-editor.org/rfc/rfc6278.pdf"],"folder":"IETF/RFC-6278","files":{"txt":{"path":"standards/IETF/RFC-6278/RFC-6278.txt","sha256":"ea0d78703bcf127e177b2557e626ae27d863f5083217961a04bb0f8d2d880eb5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use the 'static-static Elliptic Curve\n Diffie-Hellman key-agreement scheme (i.e., Elliptic Curve Diffie-\n Hellman where both participants use static Diffie-Hellman values)\n with the Cryptographic Message Syntax. In this form of key\n agreement, the Diffie-Hellman values of both the sender and receiver\n are long-term values contained in certificates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abo","scope_keywords":["6278","algorithm","authentication","certificate","certificates","encryption","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 6278 This document describes how to use the 'static-static Elliptic Curve\n Diffie-Hellman key-agreement scheme (i.e., Elliptic Curve Diffie-\n Hellman where both participants use static Diffie-Hellman values)\n with the Cryptographic Message Syntax. In this form of key\n agreement, the Diffie-Hellman values of both the sender and receiver\n are long-term values contained in certificates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abo 6278 algorithm authentication certificate certificates encryption http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6279","type":"specification","body":"IETF","designation":"RFC 6279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6279.txt","https://www.rfc-editor.org/rfc/rfc6279.pdf"],"folder":"IETF/RFC-6279","files":{"txt":{"path":"standards/IETF/RFC-6279/RFC-6279.txt","sha256":"039f7501ae64d5a3558fac3325b1843b2981ce7330e499403731d203c9f741dc"}},"tags":["nested-reference","unchanged"],"summary":"Proxy Mobile IPv6 is the IETF Standard for network-based mobility\n management. In Proxy Mobile IPv6, mobile nodes are topologically\n anchored at a Local Mobility Anchor, which forwards all data for\n registered mobile nodes. The setup and maintenance of localized\n routing, which allows forwarding of data packets between two mobile\n nodes' Mobility Access Gateways without involvement of their Local\n Mobility Anchor in forwarding, is not considered. This document\n describes the problem space of localized routing in Proxy Mobile\n IPv6.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Stee","scope_keywords":["6279","http","key","license","management","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null},{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null}],"search_text":"IETF RFC 6279 Proxy Mobile IPv6 is the IETF Standard for network-based mobility\n management. In Proxy Mobile IPv6, mobile nodes are topologically\n anchored at a Local Mobility Anchor, which forwards all data for\n registered mobile nodes. The setup and maintenance of localized\n routing, which allows forwarding of data packets between two mobile\n nodes' Mobility Access Gateways without involvement of their Local\n Mobility Anchor in forwarding, is not considered. This document\n describes the problem space of localized routing in Proxy Mobile\n IPv6.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Stee 6279 http key license management path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6280","type":"specification","body":"IETF","designation":"RFC 6280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6280.txt","https://www.rfc-editor.org/rfc/rfc6280.pdf"],"folder":"IETF/RFC-6280","files":{"txt":{"path":"standards/IETF/RFC-6280/RFC-6280.txt","sha256":"6c5592dbd827019b929468e786fdcc03dbcf7d38459976204d7b5c8deb660110"}},"tags":["nested-reference","unchanged"],"summary":"Location-based services (such as navigation applications, emergency\n services, and management of equipment in the field) need geographic\n location information about Internet hosts, their users, and other\n related entities. These applications need to securely gather and\n transfer location information for location services, and at the same\n time protect the privacy of the individuals involved. This document\n describes an architecture for privacy-preserving location-based\n services in the Internet, focusing on authorization, security, and\n privacy requirements for the data formats and protocols used by these\n services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b","scope_keywords":["6280","authorization","http","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6397","folder":"IETF/RFC-6397","source":"IETF/RFC-6397/RFC-6397.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 6280 Location-based services (such as navigation applications, emergency\n services, and management of equipment in the field) need geographic\n location information about Internet hosts, their users, and other\n related entities. These applications need to securely gather and\n transfer location information for location services, and at the same\n time protect the privacy of the individuals involved. This document\n describes an architecture for privacy-preserving location-based\n services in the Internet, focusing on authorization, security, and\n privacy requirements for the data formats and protocols used by these\n services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b 6280 authorization http license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6302","type":"specification","body":"IETF","designation":"RFC 6302","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6302.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6302.txt","https://www.rfc-editor.org/rfc/rfc6302.pdf"],"folder":"IETF/RFC-6302","files":{"txt":{"path":"standards/IETF/RFC-6302/RFC-6302.txt","sha256":"1d00a4b33c6aa272668596729327eb67efa32249e96996ef3271880c921daf37"}},"tags":["nested-reference","unchanged"],"summary":"In the wake of IPv4 exhaustion and deployment of IP address sharing\n techniques, this document recommends that Internet-facing servers log\n port number and accurate timestamps in addition to the incoming IP\n address.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6302.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n","scope_keywords":["6302","http","key","license","policies","presentation","risk","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6333","folder":"IETF/RFC-6333","source":"IETF/RFC-6333/RFC-6333.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 6302 In the wake of IPv4 exhaustion and deployment of IP address sharing\n techniques, this document recommends that Internet-facing servers log\n port number and accurate timestamps in addition to the incoming IP\n address.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6302.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n 6302 http key license policies presentation risk subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 6313","type":"specification","body":"IETF","designation":"RFC 6313","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6313.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6313.txt","https://www.rfc-editor.org/rfc/rfc6313.pdf"],"folder":"IETF/RFC-6313","files":{"txt":{"path":"standards/IETF/RFC-6313/RFC-6313.txt","sha256":"8b95f0da00f98d9c08ea549ee6e01bd4335689bb00a61af5d9c6e2b1f5ac43c4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the IP Flow Information\n Export (IPFIX) protocol specification in RFC 5101 and the IPFIX\n information model specified in RFC 5102 to support hierarchical\n structured data and lists (sequences) of Information Elements in data\n records. This extension allows definition of complex data structures\n such as variable-length lists and specification of hierarchical\n containment relationships between Templates. Finally, the semantics\n are provided in order to express the relationship among multiple list\n elements in a structured data record.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur","scope_keywords":["6313","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null}],"search_text":"IETF RFC 6313 This document specifies an extension to the IP Flow Information\n Export (IPFIX) protocol specification in RFC 5101 and the IPFIX\n information model specified in RFC 5102 to support hierarchical\n structured data and lists (sequences) of Information Elements in data\n records. This extension allows definition of complex data structures\n such as variable-length lists and specification of hierarchical\n containment relationships between Templates. Finally, the semantics\n are provided in order to express the relationship among multiple list\n elements in a structured data record.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur 6313 http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6316","type":"specification","body":"IETF","designation":"RFC 6316","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6316.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6316.txt","https://www.rfc-editor.org/rfc/rfc6316.pdf"],"folder":"IETF/RFC-6316","files":{"txt":{"path":"standards/IETF/RFC-6316/RFC-6316.txt","sha256":"639d8776fc02936ef551a7d65f77ab411be5979e6136bf4967e65af77c15cb1d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies sockets API extensions for the multihoming\n shim layer. The API aims to enable interactions between applications\n and the multihoming shim layer for advanced locator management, and\n access to information about failure detection and path exploration.\n\n This document is based on an assumption that a multihomed host is\n equipped with a conceptual sub-layer (hereafter called \"shim sub-\n layer\") inside the IP layer that maintains mappings between\n identifiers and locators. Examples of the shim are Shim6 and the\n Host Identity Protocol (HIP).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by ","scope_keywords":["6316","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null}],"search_text":"IETF RFC 6316 This document specifies sockets API extensions for the multihoming\n shim layer. The API aims to enable interactions between applications\n and the multihoming shim layer for advanced locator management, and\n access to information about failure detection and path exploration.\n\n This document is based on an assumption that a multihomed host is\n equipped with a conceptual sub-layer (hereafter called \"shim sub-\n layer\") inside the IP layer that maintains mappings between\n identifiers and locators. Examples of the shim are Shim6 and the\n Host Identity Protocol (HIP).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by  6316 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6318","type":"specification","body":"IETF","designation":"RFC 6318","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6318.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6318.txt","https://www.rfc-editor.org/rfc/rfc6318.pdf"],"folder":"IETF/RFC-6318","files":{"txt":{"path":"standards/IETF/RFC-6318/RFC-6318.txt","sha256":"2cda987aac6d2f4bbd7c6dfb00dc5fa8ac411bc214c7fa65c44386a8cd132400"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms in Secure/Multipurpose\n Internet Mail Extensions (S/MIME) as specified in RFC 5751. This\n document obsoletes RFC 5008.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6318.\n\n","scope_keywords":["6318","algorithm","algorithms","encryption","hash","hashing","http","key","license","management","pid","policy","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null}],"search_text":"IETF RFC 6318 This document specifies the conventions for using the United States\n National Security Agency's Suite B algorithms in Secure/Multipurpose\n Internet Mail Extensions (S/MIME) as specified in RFC 5751. This\n document obsoletes RFC 5008.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6318.\n\n 6318 algorithm algorithms encryption hash hashing http key license management pid policy signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6321","type":"specification","body":"IETF","designation":"RFC 6321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6321.txt","https://www.rfc-editor.org/rfc/rfc6321.pdf"],"folder":"IETF/RFC-6321","files":{"txt":{"path":"standards/IETF/RFC-6321/RFC-6321.txt","sha256":"dd6f14e4898e1a94659a3ed72076f60809ed46aad68a782da487960bb2b3c262"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines \"xCal\", an XML format for iCalendar data.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6321.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) ","scope_keywords":["6321","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null}],"search_text":"IETF RFC 6321 This specification defines \"xCal\", an XML format for iCalendar data.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6321.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info)  6321 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6323","type":"specification","body":"IETF","designation":"RFC 6323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6323.txt","https://www.rfc-editor.org/rfc/rfc6323.pdf"],"folder":"IETF/RFC-6323","files":{"txt":{"path":"standards/IETF/RFC-6323/RFC-6323.txt","sha256":"0ca56e8b0bd99c52f139709e5f695b1bd2e3e92e17f87c9706a7716cabe626d0"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an update to the round-trip time (RTT)\n estimation algorithm used for TFRC (TCP-Friendly Rate Control)\n congestion control by the Datagram Congestion Control Protocol\n (DCCP). It updates specifications for the CCID-3 and CCID-4\n Congestion Control IDs of DCCP.\n\n The update addresses parameter-estimation problems occurring with\n TFRC-based DCCP congestion control. It uses a recommendation made in\n the original TFRC specification to avoid the inherent problems of\n receiver-based RTT sampling, by utilising higher-accuracy RTT samples\n already available at the sender.\n\n It is integrated into the feature set of DCCP as an end-to-end\n negotiable extension.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pub","scope_keywords":["6323","algorithm","delivery","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"IETF RFC 6323 This document specifies an update to the round-trip time (RTT)\n estimation algorithm used for TFRC (TCP-Friendly Rate Control)\n congestion control by the Datagram Congestion Control Protocol\n (DCCP). It updates specifications for the CCID-3 and CCID-4\n Congestion Control IDs of DCCP.\n\n The update addresses parameter-estimation problems occurring with\n TFRC-based DCCP congestion control. It uses a recommendation made in\n the original TFRC specification to avoid the inherent problems of\n receiver-based RTT sampling, by utilising higher-accuracy RTT samples\n already available at the sender.\n\n It is integrated into the feature set of DCCP as an end-to-end\n negotiable extension.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pub 6323 algorithm delivery http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6336","type":"specification","body":"IETF","designation":"RFC 6336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6336.txt","https://www.rfc-editor.org/rfc/rfc6336.pdf"],"folder":"IETF/RFC-6336","files":{"txt":{"path":"standards/IETF/RFC-6336/RFC-6336.txt","sha256":"cbf19a95239594268f55a097935c8c282cd1e2b598d92a15ab2cb8cedc7f4398"}},"tags":["nested-reference","unchanged"],"summary":"It has been identified that \"Interactive Connectivity Establishment\n (ICE): A Protocol for Network Address Translator (NAT) Traversal for\n Offer/Answer Protocols\" (RFC 5245) is missing a registry for ICE\n options. This document defines this missing IANA registry and\n updates RFC 5245.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6336.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust ","scope_keywords":["6336","attribute","http","identification","key","license","policy","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 6336 It has been identified that \"Interactive Connectivity Establishment\n (ICE): A Protocol for Network Address Translator (NAT) Traversal for\n Offer/Answer Protocols\" (RFC 5245) is missing a registry for ICE\n options. This document defines this missing IANA registry and\n updates RFC 5245.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6336.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust  6336 attribute http identification key license policy registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6337","type":"specification","body":"IETF","designation":"RFC 6337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6337.txt","https://www.rfc-editor.org/rfc/rfc6337.pdf"],"folder":"IETF/RFC-6337","files":{"txt":{"path":"standards/IETF/RFC-6337/RFC-6337.txt","sha256":"6cc0a5de2ba62beabc78f1b9b36eaa13f0be5ebd28cba769793311b2cf927923"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) utilizes the offer/answer model\n to establish and update multimedia sessions using the Session\n Description Protocol (SDP). The description of the offer/answer\n model in SIP is dispersed across multiple RFCs. This document\n summarizes all the current usages of the offer/answer model in SIP\n communication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this documen","scope_keywords":["6337","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null}],"search_text":"IETF RFC 6337 The Session Initiation Protocol (SIP) utilizes the offer/answer model\n to establish and update multimedia sessions using the Session\n Description Protocol (SDP). The description of the offer/answer\n model in SIP is dispersed across multiple RFCs. This document\n summarizes all the current usages of the offer/answer model in SIP\n communication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this documen 6337 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6348","type":"specification","body":"IETF","designation":"RFC 6348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6348.txt","https://www.rfc-editor.org/rfc/rfc6348.pdf"],"folder":"IETF/RFC-6348","files":{"txt":{"path":"standards/IETF/RFC-6348/RFC-6348.txt","sha256":"5d1becb0020ca98dda39cd05d403c2902dacc4642947843474166cda45738aa2"}},"tags":["nested-reference","unchanged"],"summary":"This document lists a set of functional requirements that served as\n input to the design of Label Distribution Protocol (LDP) extensions\n for setting up point-to-multipoint (P2MP) Label Switched Paths (LSP),\n in order to deliver point-to-multipoint applications over a\n Multiprotocol Label Switching (MPLS) infrastructure.\n\n This work was overtaken by the protocol solution developed by the\n MPLS working group, but that solution did not closely follow the\n requirements documented here. This document is published as a\n historic record of the ideas and requirements that shaped the\n protocol work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for the historical record.\n\n This document defines a Historic Document for the Internet community.\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the cons","scope_keywords":["6348","driving","http","key","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null}],"search_text":"IETF RFC 6348 This document lists a set of functional requirements that served as\n input to the design of Label Distribution Protocol (LDP) extensions\n for setting up point-to-multipoint (P2MP) Label Switched Paths (LSP),\n in order to deliver point-to-multipoint applications over a\n Multiprotocol Label Switching (MPLS) infrastructure.\n\n This work was overtaken by the protocol solution developed by the\n MPLS working group, but that solution did not closely follow the\n requirements documented here. This document is published as a\n historic record of the ideas and requirements that shaped the\n protocol work.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for the historical record.\n\n This document defines a Historic Document for the Internet community.\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the cons 6348 driving http key license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6351","type":"specification","body":"IETF","designation":"RFC 6351","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6351.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6351.txt","https://www.rfc-editor.org/rfc/rfc6351.pdf"],"folder":"IETF/RFC-6351","files":{"txt":{"path":"standards/IETF/RFC-6351/RFC-6351.txt","sha256":"3ac0e03cccda6663ed32052749cc5c607d88e381f9cfcb795317bc39a57909e3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the XML schema of the vCard data format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6351.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in eff","scope_keywords":["6351","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6868","folder":"IETF/RFC-6868","source":"IETF/RFC-6868/RFC-6868.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null}],"search_text":"IETF RFC 6351 This document defines the XML schema of the vCard data format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6351.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in eff 6351 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6352","type":"specification","body":"IETF","designation":"RFC 6352","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6352.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6352.txt","https://www.rfc-editor.org/rfc/rfc6352.pdf"],"folder":"IETF/RFC-6352","files":{"txt":{"path":"standards/IETF/RFC-6352/RFC-6352.txt","sha256":"fb6206c01b46edac06085186575fb7c1e2e9bfeb1043d222a6a366eb41ac801c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to the Web Distributed Authoring and\n Versioning (WebDAV) protocol to specify a standard way of accessing,\n managing, and sharing contact information based on the vCard format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6352.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n ","scope_keywords":["6352","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6764","folder":"IETF/RFC-6764","source":"IETF/RFC-6764/RFC-6764.txt","version":null}],"search_text":"IETF RFC 6352 This document defines extensions to the Web Distributed Authoring and\n Versioning (WebDAV) protocol to specify a standard way of accessing,\n managing, and sharing contact information based on the vCard format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6352.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n  6352 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6363","type":"specification","body":"IETF","designation":"RFC 6363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6363.txt","https://www.rfc-editor.org/rfc/rfc6363.pdf"],"folder":"IETF/RFC-6363","files":{"txt":{"path":"standards/IETF/RFC-6363/RFC-6363.txt","sha256":"26c0e04fd0602ddb3f47bba418677fe6b1a83faa1d4346e9708c89efe745be11"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for using Forward Error\n Correction (FEC) codes with applications in public and private IP\n networks to provide protection against packet loss. The framework\n supports applying FEC to arbitrary packet flows over unreliable\n transport and is primarily intended for real-time, or streaming,\n media. This framework can be used to define Content Delivery\n Protocols that provide FEC for streaming media delivery or other\n packet flows. Content Delivery Protocols defined using this\n framework can support any FEC scheme (and associated FEC codes) that\n is compliant with various requirements defined in this document.\n Thus, Content Delivery Protocols can be defined that are not specific\n to a particular FEC scheme, and FEC schemes can be defined that are\n not specific to a particular Content Delivery Protocol.\n\nStatus of This Memo\n\n This is an Internet Standards ","scope_keywords":["6363","delivery","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null}],"search_text":"IETF RFC 6363 This document describes a framework for using Forward Error\n Correction (FEC) codes with applications in public and private IP\n networks to provide protection against packet loss. The framework\n supports applying FEC to arbitrary packet flows over unreliable\n transport and is primarily intended for real-time, or streaming,\n media. This framework can be used to define Content Delivery\n Protocols that provide FEC for streaming media delivery or other\n packet flows. Content Delivery Protocols defined using this\n framework can support any FEC scheme (and associated FEC codes) that\n is compliant with various requirements defined in this document.\n Thus, Content Delivery Protocols can be defined that are not specific\n to a particular FEC scheme, and FEC schemes can be defined that are\n not specific to a particular Content Delivery Protocol.\n\nStatus of This Memo\n\n This is an Internet Standards  6363 delivery http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6364","type":"specification","body":"IETF","designation":"RFC 6364","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6364.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6364.txt","https://www.rfc-editor.org/rfc/rfc6364.pdf"],"folder":"IETF/RFC-6364","files":{"txt":{"path":"standards/IETF/RFC-6364/RFC-6364.txt","sha256":"7470606b46460bce7d41e9c7cd2b8669c359ed85227366fce7f74f68cab9665d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the use of the Session Description Protocol\n (SDP) to describe the parameters required to signal the Forward Error\n Correction (FEC) Framework Configuration Information between the\n sender(s) and receiver(s). This document also provides examples that\n show the semantics for grouping multiple source and repair flows\n together for the applications that simultaneously use multiple\n instances of the FEC Framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any e","scope_keywords":["6364","attribute","attributes","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6364 This document specifies the use of the Session Description Protocol\n (SDP) to describe the parameters required to signal the Forward Error\n Correction (FEC) Framework Configuration Information between the\n sender(s) and receiver(s). This document also provides examples that\n show the semantics for grouping multiple source and repair flows\n together for the applications that simultaneously use multiple\n instances of the FEC Framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any e 6364 attribute attributes delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6368","type":"specification","body":"IETF","designation":"RFC 6368","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6368.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6368.txt","https://www.rfc-editor.org/rfc/rfc6368.pdf"],"folder":"IETF/RFC-6368","files":{"txt":{"path":"standards/IETF/RFC-6368/RFC-6368.txt","sha256":"4cca295360a89a26ac25c8b3ad73a57c396eeda93a09316a48de9c5b2884f4fd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines protocol extensions and procedures for BGP\n Provider/Customer Edge router iteration in BGP/MPLS IP VPNs. These\n extensions and procedures have the objective of making the usage of\n the BGP/MPLS IP VPN transparent to the customer network, as far as\n routing information is concerned.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6368.\n\nMarques, et al. Standards Trac","scope_keywords":["6368","attribute","attributes","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 6368 This document defines protocol extensions and procedures for BGP\n Provider/Customer Edge router iteration in BGP/MPLS IP VPNs. These\n extensions and procedures have the objective of making the usage of\n the BGP/MPLS IP VPN transparent to the customer network, as far as\n routing information is concerned.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6368.\n\nMarques, et al. Standards Trac 6368 attribute attributes http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6370","type":"specification","body":"IETF","designation":"RFC 6370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6370.txt","https://www.rfc-editor.org/rfc/rfc6370.pdf"],"folder":"IETF/RFC-6370","files":{"txt":{"path":"standards/IETF/RFC-6370/RFC-6370.txt","sha256":"193561f0fab996516a82763799fa1666e3984e91ab0ce0866e188f21de025aff"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an initial set of identifiers to be used in\n the Transport Profile of Multiprotocol Label Switching (MPLS-TP).\n The MPLS-TP requirements (RFC 5654) require that the elements and\n objects in an MPLS-TP environment are able to be configured and\n managed without a control plane. In such an environment, many\n conventions for defining identifiers are possible. This document\n defines identifiers for MPLS-TP management and Operations,\n Administration, and Maintenance (OAM) functions compatible with IP/\n MPLS conventions.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet","scope_keywords":["6370","http","key","license","management","path","profile","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null}],"search_text":"IETF RFC 6370 This document specifies an initial set of identifiers to be used in\n the Transport Profile of Multiprotocol Label Switching (MPLS-TP).\n The MPLS-TP requirements (RFC 5654) require that the elements and\n objects in an MPLS-TP environment are able to be configured and\n managed without a control plane. In such an environment, many\n conventions for defining identifiers are possible. This document\n defines identifiers for MPLS-TP management and Operations,\n Administration, and Maintenance (OAM) functions compatible with IP/\n MPLS conventions.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet 6370 http key license management path profile qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6379","type":"specification","body":"IETF","designation":"RFC 6379","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6379.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6379.txt","https://www.rfc-editor.org/rfc/rfc6379.pdf"],"folder":"IETF/RFC-6379","files":{"txt":{"path":"standards/IETF/RFC-6379/RFC-6379.txt","sha256":"c36e8487726d1133cef746eab3cc15783cca65d08097a8ea34b578d1f4a12c89"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes four cryptographic user interface suites\n (\"UI suites\") for IP Security (IPsec), similar to the two suites\n specified in RFC 4308. The four new suites provide compatibility\n with the United States National Security Agency's Suite B\n specifications. This document obsoletes RFC 4869, which presented\n earlier versions of these suites.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of ","scope_keywords":["6379","algorithm","algorithms","encryption","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6380","folder":"IETF/RFC-6380","source":"IETF/RFC-6380/RFC-6380.txt","version":null},{"body":"IETF","designation":"RFC 7321","folder":"IETF/RFC-7321","source":"IETF/RFC-7321/RFC-7321.txt","version":null}],"search_text":"IETF RFC 6379 This document proposes four cryptographic user interface suites\n (\"UI suites\") for IP Security (IPsec), similar to the two suites\n specified in RFC 4308. The four new suites provide compatibility\n with the United States National Security Agency's Suite B\n specifications. This document obsoletes RFC 4869, which presented\n earlier versions of these suites.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of  6379 algorithm algorithms encryption http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6380","type":"specification","body":"IETF","designation":"RFC 6380","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6380.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6380.txt","https://www.rfc-editor.org/rfc/rfc6380.pdf"],"folder":"IETF/RFC-6380","files":{"txt":{"path":"standards/IETF/RFC-6380/RFC-6380.txt","sha256":"88335efcc0cea3d763df30e78e07cc0a08ddae44a90e454a9a0ad9c3915eca3e"}},"tags":["nested-reference","unchanged"],"summary":"The United States Government has published guidelines for \"NSA\n Suite B Cryptography\" dated July, 2005, which defines cryptographic\n algorithm policy for national security applications. This document\n specifies the conventions for using Suite B cryptography in IP\n Security (IPsec).\n\n Since many of the Suite B algorithms are used in other environments,\n the majority of the conventions needed for the Suite B\n algorithms are already specified in other documents. This document\n references the source of these conventions, with some relevant\n detail repeated to aid developers who choose to support Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a","scope_keywords":["6380","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","http","key","license","management","policy","profile","registered","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6379","folder":"IETF/RFC-6379","source":"IETF/RFC-6379/RFC-6379.txt","version":null}],"search_text":"IETF RFC 6380 The United States Government has published guidelines for \"NSA\n Suite B Cryptography\" dated July, 2005, which defines cryptographic\n algorithm policy for national security applications. This document\n specifies the conventions for using Suite B cryptography in IP\n Security (IPsec).\n\n Since many of the Suite B algorithms are used in other environments,\n the majority of the conventions needed for the Suite B\n algorithms are already specified in other documents. This document\n references the source of these conventions, with some relevant\n detail repeated to aid developers who choose to support Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a 6380 algorithm algorithms authentication certificate certificates encryption hash http key license management policy profile registered signature nested-reference unchanged"},{"id":"IETF RFC 6382","type":"specification","body":"IETF","designation":"RFC 6382","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6382.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6382.txt","https://www.rfc-editor.org/rfc/rfc6382.pdf"],"folder":"IETF/RFC-6382","files":{"txt":{"path":"standards/IETF/RFC-6382/RFC-6382.txt","sha256":"ef45ba73236390b60cdd516e30e8df4349b8da549321898668ae1e5a54495e96"}},"tags":["nested-reference","unchanged"],"summary":"This document makes recommendations regarding the use of unique\n origin autonomous system numbers (ASNs) per node for globally\n anycasted critical infrastructure services in order to provide\n routing system discriminators for a given anycasted prefix. Network\n management and monitoring techniques, or other operational\n mechanisms, may employ this new discriminator in whatever manner best\n accommodates their operating environment.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n a","scope_keywords":["6382","attribute","attributes","http","identification","license","management","path","policies","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 6382 This document makes recommendations regarding the use of unique\n origin autonomous system numbers (ASNs) per node for globally\n anycasted critical infrastructure services in order to provide\n routing system discriminators for a given anycasted prefix. Network\n management and monitoring techniques, or other operational\n mechanisms, may employ this new discriminator in whatever manner best\n accommodates their operating environment.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n a 6382 attribute attributes http identification license management path policies presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6386","type":"specification","body":"IETF","designation":"RFC 6386","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6386.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6386.txt","https://www.rfc-editor.org/rfc/rfc6386.pdf"],"folder":"IETF/RFC-6386","files":{"txt":{"path":"standards/IETF/RFC-6386/RFC-6386.txt","sha256":"c044997ae5e26f74dc28569f8866937412b2783e887c96e0c09372af78be411c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the VP8 compressed video data format,\n together with a discussion of the decoding procedure for the format.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6386.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All","scope_keywords":["6386","algorithm","algorithms","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 6386 This document describes the VP8 compressed video data format,\n together with a discussion of the decoding procedure for the format.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6386.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All 6386 algorithm algorithms http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6388","type":"specification","body":"IETF","designation":"RFC 6388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6388.txt","https://www.rfc-editor.org/rfc/rfc6388.pdf"],"folder":"IETF/RFC-6388","files":{"txt":{"path":"standards/IETF/RFC-6388/RFC-6388.txt","sha256":"8f9d5105ff68886db91ed4d65597354fdd3abbb7df1b3ff9c03fc67b3a80f1af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes extensions to the Label Distribution Protocol\n (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-\n multipoint (MP2MP) Label Switched Paths (LSPs) in MPLS networks.\n These extensions are also referred to as multipoint LDP. Multipoint\n LDP constructs the P2MP or MP2MP LSPs without interacting with or\n relying upon any other multicast tree construction protocol.\n Protocol elements and procedures for this solution are described for\n building such LSPs in a receiver-initiated manner. There can be\n various applications for multipoint LSPs, for example IP multicast or\n support for multicast in BGP/MPLS Layer 3 Virtual Private Networks\n (L3VPNs). Specification of how such applications can use an LDP\n signaled multipoint LSP is outside the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pro","scope_keywords":["6388","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6389","folder":"IETF/RFC-6389","source":"IETF/RFC-6389/RFC-6389.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6512","folder":"IETF/RFC-6512","source":"IETF/RFC-6512/RFC-6512.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null},{"body":"IETF","designation":"RFC 6790","folder":"IETF/RFC-6790","source":"IETF/RFC-6790/RFC-6790.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6388 This document describes extensions to the Label Distribution Protocol\n (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-\n multipoint (MP2MP) Label Switched Paths (LSPs) in MPLS networks.\n These extensions are also referred to as multipoint LDP. Multipoint\n LDP constructs the P2MP or MP2MP LSPs without interacting with or\n relying upon any other multicast tree construction protocol.\n Protocol elements and procedures for this solution are described for\n building such LSPs in a receiver-initiated manner. There can be\n various applications for multipoint LSPs, for example IP multicast or\n support for multicast in BGP/MPLS Layer 3 Virtual Private Networks\n (L3VPNs). Specification of how such applications can use an LDP\n signaled multipoint LSP is outside the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a pro 6388 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6389","type":"specification","body":"IETF","designation":"RFC 6389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6389.txt","https://www.rfc-editor.org/rfc/rfc6389.pdf"],"folder":"IETF/RFC-6389","files":{"txt":{"path":"standards/IETF/RFC-6389/RFC-6389.txt","sha256":"a28fc57b4494f4cd5f7a57ceeade9623a69860553d3f3da7235d23f1410c0972"}},"tags":["nested-reference","unchanged"],"summary":"This document describes procedures for distributing upstream-assigned\n labels for the Label Distribution Protocol (LDP). It also describes\n how these procedures can be used for avoiding branch Label Switching\n Router (LSR) traffic replication on a LAN for LDP point-to-multipoint\n (P2MP) Label Switched Paths (LSPs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6389.\n\nCopyright Notice\n\n","scope_keywords":["6389","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null}],"search_text":"IETF RFC 6389 This document describes procedures for distributing upstream-assigned\n labels for the Label Distribution Protocol (LDP). It also describes\n how these procedures can be used for avoiding branch Label Switching\n Router (LSR) traffic replication on a LAN for LDP point-to-multipoint\n (P2MP) Label Switched Paths (LSPs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6389.\n\nCopyright Notice\n\n 6389 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6402","type":"specification","body":"IETF","designation":"RFC 6402","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6402.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6402.txt","https://www.rfc-editor.org/rfc/rfc6402.pdf"],"folder":"IETF/RFC-6402","files":{"txt":{"path":"standards/IETF/RFC-6402/RFC-6402.txt","sha256":"c7c0d0ddac42083d7566ccdb8ad8581e60947c0b627a5775c73e7fb072e17ce4"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a set of updates to the base syntax for CMC, a\n Certificate Management protocol using the Cryptographic Message\n Syntax (CMS). This document updates RFC 5272, RFC 5273, and RFC\n 5274.\n\n The new items in this document are: new controls for future work in\n doing server side key generation, definition of a Subject Information\n Access value to identify CMC servers, and the registration of a port\n number for TCP/IP for the CMC service to run on.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current ","scope_keywords":["6402","attribute","attributes","authentication","certificate","crl","http","key","license","management","path","pki","profile","revocation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6403","folder":"IETF/RFC-6403","source":"IETF/RFC-6403/RFC-6403.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 6402 This document contains a set of updates to the base syntax for CMC, a\n Certificate Management protocol using the Cryptographic Message\n Syntax (CMS). This document updates RFC 5272, RFC 5273, and RFC\n 5274.\n\n The new items in this document are: new controls for future work in\n doing server side key generation, definition of a Subject Information\n Access value to identify CMC servers, and the registration of a port\n number for TCP/IP for the CMC service to run on.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current  6402 attribute attributes authentication certificate crl http key license management path pki profile revocation signature subject nested-reference unchanged"},{"id":"IETF RFC 6403","type":"specification","body":"IETF","designation":"RFC 6403","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6403.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6403.txt","https://www.rfc-editor.org/rfc/rfc6403.pdf"],"folder":"IETF/RFC-6403","files":{"txt":{"path":"standards/IETF/RFC-6403/RFC-6403.txt","sha256":"fc4b3fb776f74ff4f8df7e655764968757976286d0fffa5abc7c719ea0371d4b"}},"tags":["nested-reference","unchanged"],"summary":"The United States government has published guidelines for \"NSA\n Suite B Cryptography\", which defines cryptographic algorithm policy\n for national security applications. This document specifies a\n profile of the Certificate Management over CMS (CMC) protocol for\n managing Suite B X.509 public key certificates. This profile is a\n refinement of RFCs 5272, 5273, and 5274.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the curr","scope_keywords":["6403","algorithm","algorithms","certificate","certificates","crl","hash","http","key","license","management","pki","policies","policy","profile","revocation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6402","folder":"IETF/RFC-6402","source":"IETF/RFC-6402/RFC-6402.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null}],"search_text":"IETF RFC 6403 The United States government has published guidelines for \"NSA\n Suite B Cryptography\", which defines cryptographic algorithm policy\n for national security applications. This document specifies a\n profile of the Certificate Management over CMS (CMC) protocol for\n managing Suite B X.509 public key certificates. This profile is a\n refinement of RFCs 5272, 5273, and 5274.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the curr 6403 algorithm algorithms certificate certificates crl hash http key license management pki policies policy profile revocation nested-reference unchanged"},{"id":"IETF RFC 6407","type":"specification","body":"IETF","designation":"RFC 6407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6407.txt","https://www.rfc-editor.org/rfc/rfc6407.pdf"],"folder":"IETF/RFC-6407","files":{"txt":{"path":"standards/IETF/RFC-6407/RFC-6407.txt","sha256":"a109cdf5a744eed986c71a7421a41f179d2d0d76978a1afce2987dcd23efb961"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Group Domain of Interpretation (GDOI)\n protocol specified in RFC 3547. The GDOI provides group key\n management to support secure group communications according to the\n architecture specified in RFC 4046. The GDOI manages group security\n associations, which are used by IPsec and potentially other data\n security protocols. This document replaces RFC 3547.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai","scope_keywords":["6407","algorithm","authentication","authorization","http","identification","key","keys","license","management","policy","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 6407 This document describes the Group Domain of Interpretation (GDOI)\n protocol specified in RFC 3547. The GDOI provides group key\n management to support secure group communications according to the\n architecture specified in RFC 4046. The GDOI manages group security\n associations, which are used by IPsec and potentially other data\n security protocols. This document replaces RFC 3547.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai 6407 algorithm authentication authorization http identification key keys license management policy signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6415","type":"specification","body":"IETF","designation":"RFC 6415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6415.txt","https://www.rfc-editor.org/rfc/rfc6415.pdf"],"folder":"IETF/RFC-6415","files":{"txt":{"path":"standards/IETF/RFC-6415/RFC-6415.txt","sha256":"6844be94c0281ba98a6760bcf21b608e4609f34af0310a47db2a860a0f22d481"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes a method for locating host metadata as\n well as information about individual resources controlled by the\n host.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6415.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provis","scope_keywords":["6415","http","license","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7033","folder":"IETF/RFC-7033","source":"IETF/RFC-7033/RFC-7033.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 6415 This specification describes a method for locating host metadata as\n well as information about individual resources controlled by the\n host.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6415.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provis 6415 http license policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6421","type":"specification","body":"IETF","designation":"RFC 6421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6421.txt","https://www.rfc-editor.org/rfc/rfc6421.pdf"],"folder":"IETF/RFC-6421","files":{"txt":{"path":"standards/IETF/RFC-6421/RFC-6421.txt","sha256":"23c5a09c6ec969904c6693d8c2fae945ee8ff5b8bef8d0a8130103e8d5d9df1f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the requirements for a crypto-agility solution\n for Remote Authentication Dial-In User Service (RADIUS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6421.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rig","scope_keywords":["6421","algorithm","algorithms","authentication","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null}],"search_text":"IETF RFC 6421 This memo describes the requirements for a crypto-agility solution\n for Remote Authentication Dial-In User Service (RADIUS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6421.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rig 6421 algorithm algorithms authentication http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6422","type":"specification","body":"IETF","designation":"RFC 6422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6422.txt","https://www.rfc-editor.org/rfc/rfc6422.pdf"],"folder":"IETF/RFC-6422","files":{"txt":{"path":"standards/IETF/RFC-6422/RFC-6422.txt","sha256":"41bc99d9348a101eb458cdc9a4516368147d397866a7cd13aa88a94d1a190e18"}},"tags":["nested-reference","unchanged"],"summary":"DHCPv6 relay agents cannot communicate with DHCPv6 clients directly.\n However, in some cases, the relay agent possesses some information\n that would be useful to the DHCPv6 client. This document describes a\n mechanism whereby the DHCPv6 relay agent can provide such information\n to the DHCPv6 server, which can, in turn, pass this information on to\n the DHCP client.\n\n This document updates RFC 3315 (DHCPv6) by making explicit the\n implicit requirement that relay agents not modify the content of\n encapsulation payloads as they are relayed back toward clients.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information","scope_keywords":["6422","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6440","folder":"IETF/RFC-6440","source":"IETF/RFC-6440/RFC-6440.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null},{"body":"IETF","designation":"RFC 6977","folder":"IETF/RFC-6977","source":"IETF/RFC-6977/RFC-6977.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6422 DHCPv6 relay agents cannot communicate with DHCPv6 clients directly.\n However, in some cases, the relay agent possesses some information\n that would be useful to the DHCPv6 client. This document describes a\n mechanism whereby the DHCPv6 relay agent can provide such information\n to the DHCPv6 server, which can, in turn, pass this information on to\n the DHCP client.\n\n This document updates RFC 3315 (DHCPv6) by making explicit the\n implicit requirement that relay agents not modify the content of\n encapsulation payloads as they are relayed back toward clients.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information 6422 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6424","type":"specification","body":"IETF","designation":"RFC 6424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6424.txt","https://www.rfc-editor.org/rfc/rfc6424.pdf"],"folder":"IETF/RFC-6424","files":{"txt":{"path":"standards/IETF/RFC-6424/RFC-6424.txt","sha256":"292387f6436d154d0c6c7a4b04d4e977e464520189a3ef570cc7e4abffeb35b4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes methods for performing LSP ping (specified in\n RFC 4379) traceroute over MPLS tunnels and for traceroute of stitched\n MPLS Label Switched Paths (LSPs). The techniques outlined in RFC\n 4379 are insufficient to perform traceroute Forwarding Equivalency\n Class (FEC) validation and path discovery for an LSP that goes over\n other MPLS tunnels or for a stitched LSP. This document deprecates\n the Downstream Mapping TLV (defined in RFC 4379) in favor of a new\n TLV that, along with other procedures outlined in this document, can\n be used to trace such LSPs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur","scope_keywords":["6424","http","key","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6424 This document describes methods for performing LSP ping (specified in\n RFC 4379) traceroute over MPLS tunnels and for traceroute of stitched\n MPLS Label Switched Paths (LSPs). The techniques outlined in RFC\n 4379 are insufficient to perform traceroute Forwarding Equivalency\n Class (FEC) validation and path discovery for an LSP that goes over\n other MPLS tunnels or for a stitched LSP. This document deprecates\n the Downstream Mapping TLV (defined in RFC 4379) in favor of a new\n TLV that, along with other procedures outlined in this document, can\n be used to trace such LSPs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Fur 6424 http key license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6425","type":"specification","body":"IETF","designation":"RFC 6425","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6425.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6425.txt","https://www.rfc-editor.org/rfc/rfc6425.pdf"],"folder":"IETF/RFC-6425","files":{"txt":{"path":"standards/IETF/RFC-6425/RFC-6425.txt","sha256":"f4777bf926304856260a128f0527e3bb341a4bf19350866178ba68b599f64d11"}},"tags":["nested-reference","unchanged"],"summary":"Recent proposals have extended the scope of Multiprotocol Label\n Switching (MPLS) Label Switched Paths (LSPs) to encompass point-to-\n multipoint (P2MP) LSPs.\n\n The requirement for a simple and efficient mechanism that can be used\n to detect data-plane failures in point-to-point (P2P) MPLS LSPs has\n been recognized and has led to the development of techniques for\n fault detection and isolation commonly referred to as \"LSP ping\".\n\n The scope of this document is fault detection and isolation for P2MP\n MPLS LSPs. This documents does not replace any of the mechanisms of\n LSP ping, but clarifies their applicability to MPLS P2MP LSPs, and\n extends the techniques and mechanisms of LSP ping to the MPLS P2MP\n environment.\n\n This document updates RFC 4379.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF)","scope_keywords":["6425","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6425 Recent proposals have extended the scope of Multiprotocol Label\n Switching (MPLS) Label Switched Paths (LSPs) to encompass point-to-\n multipoint (P2MP) LSPs.\n\n The requirement for a simple and efficient mechanism that can be used\n to detect data-plane failures in point-to-point (P2P) MPLS LSPs has\n been recognized and has led to the development of techniques for\n fault detection and isolation commonly referred to as \"LSP ping\".\n\n The scope of this document is fault detection and isolation for P2MP\n MPLS LSPs. This documents does not replace any of the mechanisms of\n LSP ping, but clarifies their applicability to MPLS P2MP LSPs, and\n extends the techniques and mechanisms of LSP ping to the MPLS P2MP\n environment.\n\n This document updates RFC 4379.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF) 6425 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6437","type":"specification","body":"IETF","designation":"RFC 6437","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6437.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6437.txt","https://www.rfc-editor.org/rfc/rfc6437.pdf"],"folder":"IETF/RFC-6437","files":{"txt":{"path":"standards/IETF/RFC-6437/RFC-6437.txt","sha256":"eb35b5edfbad380aec935e4b956d0fe5e75507d98ec74eecbfe8cdf3604bc7ea"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IPv6 Flow Label field and the minimum\n requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding\n labeled packets, and flow state establishment methods. Even when\n mentioned as examples of possible uses of the flow labeling, more\n detailed requirements for specific use cases are out of the scope for\n this document.\n\n The usage of the Flow Label field enables efficient IPv6 flow\n classification based only on IPv6 main header fields in fixed\n positions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Inform","scope_keywords":["6437","encryption","hash","http","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 6437 This document specifies the IPv6 Flow Label field and the minimum\n requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding\n labeled packets, and flow state establishment methods. Even when\n mentioned as examples of possible uses of the flow labeling, more\n detailed requirements for specific use cases are out of the scope for\n this document.\n\n The usage of the Flow Label field enables efficient IPv6 flow\n classification based only on IPv6 main header fields in fixed\n positions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Inform 6437 encryption hash http license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6438","type":"specification","body":"IETF","designation":"RFC 6438","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6438.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6438.txt","https://www.rfc-editor.org/rfc/rfc6438.pdf"],"folder":"IETF/RFC-6438","files":{"txt":{"path":"standards/IETF/RFC-6438/RFC-6438.txt","sha256":"06660fc7055211f1eec8e36a245e78d3c260cff8702ba1c520d312eed14e3961"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 flow label has certain restrictions on its use. This\n document describes how those restrictions apply when using the flow\n label for load balancing by equal cost multipath routing and for link\n aggregation, particularly for IP-in-IPv6 tunneled traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6438.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identifi","scope_keywords":["6438","algorithm","delivery","hash","http","key","keys","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6436","folder":"IETF/RFC-6436","source":"IETF/RFC-6436/RFC-6436.txt","version":null},{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 6438 The IPv6 flow label has certain restrictions on its use. This\n document describes how those restrictions apply when using the flow\n label for load balancing by equal cost multipath routing and for link\n aggregation, particularly for IP-in-IPv6 tunneled traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6438.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identifi 6438 algorithm delivery hash http key keys license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6440","type":"specification","body":"IETF","designation":"RFC 6440","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6440.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6440.txt","https://www.rfc-editor.org/rfc/rfc6440.pdf"],"folder":"IETF/RFC-6440","files":{"txt":{"path":"standards/IETF/RFC-6440/RFC-6440.txt","sha256":"690653f5c1f8c53000af0bbba848fc9584e9d8186c30cfe45a6d4592c37c5140"}},"tags":["nested-reference","unchanged"],"summary":"In order to derive a Domain-Specific Root Key (DSRK) from the\n Extended Master Session Key (EMSK) generated as a side effect of an\n Extensible Authentication Protocol (EAP) method, the EAP peer must\n discover the name of the domain to which it is attached.\n\n This document specifies a Dynamic Host Configuration Protocol\n Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform\n clients using the EAP Re-authentication Protocol (ERP) EAP method of\n the name of the local domain for ERP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.","scope_keywords":["6440","authentication","authorization","http","key","license","presentation","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6422","folder":"IETF/RFC-6422","source":"IETF/RFC-6422/RFC-6422.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 6440 In order to derive a Domain-Specific Root Key (DSRK) from the\n Extended Master Session Key (EMSK) generated as a side effect of an\n Extensible Authentication Protocol (EAP) method, the EAP peer must\n discover the name of the domain to which it is attached.\n\n This document specifies a Dynamic Host Configuration Protocol\n Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform\n clients using the EAP Re-authentication Protocol (ERP) EAP method of\n the name of the local domain for ERP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741. 6440 authentication authorization http key license presentation qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6442","type":"specification","body":"IETF","designation":"RFC 6442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6442.txt","https://www.rfc-editor.org/rfc/rfc6442.pdf"],"folder":"IETF/RFC-6442","files":{"txt":{"path":"standards/IETF/RFC-6442/RFC-6442.txt","sha256":"55ba18730bf2e0eb38f91e1586869d4695416f8aaca23d73ac5f885bc727f16a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Session Initiation Protocol\n (SIP) to convey geographic location information from one SIP entity\n to another SIP entity. The SIP extension covers end-to-end\n conveyance as well as location-based routing, where SIP\n intermediaries make routing decisions based upon the location of the\n Location Target.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r","scope_keywords":["6442","http","license","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6444","folder":"IETF/RFC-6444","source":"IETF/RFC-6444/RFC-6444.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null}],"search_text":"IETF RFC 6442 This document defines an extension to the Session Initiation Protocol\n (SIP) to convey geographic location information from one SIP entity\n to another SIP entity. The SIP extension covers end-to-end\n conveyance as well as location-based routing, where SIP\n intermediaries make routing decisions based upon the location of the\n Location Target.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r 6442 http license path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 6444","type":"specification","body":"IETF","designation":"RFC 6444","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6444.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6444.txt","https://www.rfc-editor.org/rfc/rfc6444.pdf"],"folder":"IETF/RFC-6444","files":{"txt":{"path":"standards/IETF/RFC-6444/RFC-6444.txt","sha256":"851f33548954ff96be12c784d211a5fde507d1c3065f4dad4583859835fa9b6e"}},"tags":["nested-reference","unchanged"],"summary":"The emergency services architecture developed in the IETF Emergency\n Context Resolution with Internet Technology (ECRIT) working group\n describes an architecture where location information is provided by\n access networks to endpoints or Voice over IP (VoIP) service\n providers in order to determine the correct dial string and\n information to route the call to a Public Safety Answering Point\n (PSAP). To determine the PSAP Uniform Resource Identifier (URI), the\n usage of the Location-to-Service Translation (LoST) protocol is\n envisioned.\n\n This document provides a problem statement and lists requirements for\n situations where the Internet Access Provider (IAP) and/or the\n Internet Service Provider (ISP) are only willing to disclose limited\n or no location information.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pu","scope_keywords":["6444","delivery","http","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 6444 The emergency services architecture developed in the IETF Emergency\n Context Resolution with Internet Technology (ECRIT) working group\n describes an architecture where location information is provided by\n access networks to endpoints or Voice over IP (VoIP) service\n providers in order to determine the correct dial string and\n information to route the call to a Public Safety Answering Point\n (PSAP). To determine the PSAP Uniform Resource Identifier (URI), the\n usage of the Location-to-Service Translation (LoST) protocol is\n envisioned.\n\n This document provides a problem statement and lists requirements for\n situations where the Internet Access Provider (IAP) and/or the\n Internet Service Provider (ISP) are only willing to disclose limited\n or no location information.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational pu 6444 delivery http license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6454","type":"specification","body":"IETF","designation":"RFC 6454","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6454.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6454.txt","https://www.rfc-editor.org/rfc/rfc6454.pdf"],"folder":"IETF/RFC-6454","files":{"txt":{"path":"standards/IETF/RFC-6454/RFC-6454.txt","sha256":"6a42d01bf407e87255e3bd8d870fda0f473e09f3272592ba438b57c983bc5399"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the concept of an \"origin\", which is often used\n as the scope of authority or privilege by user agents. Typically,\n user agents isolate content retrieved from different origins to\n prevent malicious web site operators from interfering with the\n operation of benign web sites. In addition to outlining the\n principles that underlie the concept of origin, this document details\n how to determine the origin of a URI and how to serialize an origin\n into a string. It also defines an HTTP header field, named \"Origin\",\n that indicates which origins are associated with an HTTP request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering S","scope_keywords":["6454","algorithm","algorithms","crl","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6555","folder":"IETF/RFC-6555","source":"IETF/RFC-6555/RFC-6555.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7541","folder":"IETF/RFC-7541","source":"IETF/RFC-7541/RFC-7541.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8752","folder":"IETF/RFC-8752","source":"IETF/RFC-8752/RFC-8752.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 6454 This document defines the concept of an \"origin\", which is often used\n as the scope of authority or privilege by user agents. Typically,\n user agents isolate content retrieved from different origins to\n prevent malicious web site operators from interfering with the\n operation of benign web sites. In addition to outlining the\n principles that underlie the concept of origin, this document details\n how to determine the origin of a URI and how to serialize an origin\n into a string. It also defines an HTTP header field, named \"Origin\",\n that indicates which origins are associated with an HTTP request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering S 6454 algorithm algorithms crl http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6460","type":"specification","body":"IETF","designation":"RFC 6460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6460.txt","https://www.rfc-editor.org/rfc/rfc6460.pdf"],"folder":"IETF/RFC-6460","files":{"txt":{"path":"standards/IETF/RFC-6460/RFC-6460.txt","sha256":"cadda2a7678a70e184ca8cf2f6bf5219db2e8ea700a164d87fac5b50627a77b2"}},"tags":["nested-reference","unchanged"],"summary":"The United States government has published guidelines for \"NSA Suite\n B Cryptography\" that define cryptographic algorithm policy for\n national security applications. This document defines a profile of\n Transport Layer Security (TLS) version 1.2 that is fully compliant\n with Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta","scope_keywords":["6460","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","http","key","license","policy","profile","signature","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6605","folder":"IETF/RFC-6605","source":"IETF/RFC-6605/RFC-6605.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6460 The United States government has published guidelines for \"NSA Suite\n B Cryptography\" that define cryptographic algorithm policy for\n national security applications. This document defines a profile of\n Transport Layer Security (TLS) version 1.2 that is fully compliant\n with Suite B.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta 6460 algorithm algorithms authentication certificate certificates encryption hash http key license policy profile signature subject tls nested-reference unchanged"},{"id":"IETF RFC 6464","type":"specification","body":"IETF","designation":"RFC 6464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6464.txt","https://www.rfc-editor.org/rfc/rfc6464.pdf"],"folder":"IETF/RFC-6464","files":{"txt":{"path":"standards/IETF/RFC-6464/RFC-6464.txt","sha256":"525ae2248e269510271aac2975362c7b26b3082994a4d282ff49d9df8ae2becd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism by which packets of Real-time\n Transport Protocol (RTP) audio streams can indicate, in an RTP header\n extension, the audio level of the audio sample carried in the RTP\n packet. In large conferences, this can reduce the load on an audio\n mixer or other middlebox that wants to forward only a few of the\n loudest audio streams, without requiring it to decode and measure\n every stream that is received.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any erra","scope_keywords":["6464","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 6464 This document defines a mechanism by which packets of Real-time\n Transport Protocol (RTP) audio streams can indicate, in an RTP header\n extension, the audio level of the audio sample carried in the RTP\n packet. In large conferences, this can reduce the load on an audio\n mixer or other middlebox that wants to forward only a few of the\n loudest audio streams, without requiring it to decode and measure\n every stream that is received.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any erra 6464 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6465","type":"specification","body":"IETF","designation":"RFC 6465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6465.txt","https://www.rfc-editor.org/rfc/rfc6465.pdf"],"folder":"IETF/RFC-6465","files":{"txt":{"path":"standards/IETF/RFC-6465/RFC-6465.txt","sha256":"496801c2e5b4d4e2f2f9b771c570c1b1f6fbf403313aed09e538bb2e3b31b6a8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism for RTP-level mixers in audio\n conferences to deliver information about the audio level of\n individual participants. Such audio level indicators are transported\n in the same RTP packets as the audio data they pertain to.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6465.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as","scope_keywords":["6465","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 6465 This document describes a mechanism for RTP-level mixers in audio\n conferences to deliver information about the audio level of\n individual participants. Such audio level indicators are transported\n in the same RTP packets as the audio data they pertain to.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6465.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as 6465 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6470","type":"specification","body":"IETF","designation":"RFC 6470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6470.txt","https://www.rfc-editor.org/rfc/rfc6470.pdf"],"folder":"IETF/RFC-6470","files":{"txt":{"path":"standards/IETF/RFC-6470/RFC-6470.txt","sha256":"15da3456aedd2f343c88ae7341550b050bf5c67438e2cc3d3ab0119e37e375db"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) provides mechanisms to\n manipulate configuration datastores. However, client applications\n often need to be aware of common events, such as a change in NETCONF\n server capabilities, that may impact management applications.\n Standard mechanisms are needed to support the monitoring of the base\n system events within the NETCONF server. This document defines a\n YANG module that allows a NETCONF client to receive notifications for\n some common system events.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 574","scope_keywords":["6470","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null}],"search_text":"IETF RFC 6470 The Network Configuration Protocol (NETCONF) provides mechanisms to\n manipulate configuration datastores. However, client applications\n often need to be aware of common events, such as a change in NETCONF\n server capabilities, that may impact management applications.\n Standard mechanisms are needed to support the monitoring of the base\n system events within the NETCONF server. This document defines a\n YANG module that allows a NETCONF client to receive notifications for\n some common system events.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 574 6470 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6481","type":"specification","body":"IETF","designation":"RFC 6481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6481.txt","https://www.rfc-editor.org/rfc/rfc6481.pdf"],"folder":"IETF/RFC-6481","files":{"txt":{"path":"standards/IETF/RFC-6481/RFC-6481.txt","sha256":"f71a5535b8e1d9113534bb58b6687727cc365c92b47299da7ae54f52c19ffcab"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a profile for the structure of the Resource\n Public Key Infrastructure (RPKI) distributed repository. Each\n individual repository publication point is a directory that contains\n files that correspond to X.509/PKIX Resource Certificates,\n Certificate Revocation Lists and signed objects. This profile\n defines the object (file) naming scheme, the contents of repository\n publication points (directories), and a suggested internal structure\n of a local repository cache that is intended to facilitate\n synchronization across a distributed collection of repository\n publication points and to facilitate certification path construction.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr","scope_keywords":["6481","attestation","attestations","certificate","certificates","crl","holder","http","issuer","key","license","path","pki","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6481 This document defines a profile for the structure of the Resource\n Public Key Infrastructure (RPKI) distributed repository. Each\n individual repository publication point is a directory that contains\n files that correspond to X.509/PKIX Resource Certificates,\n Certificate Revocation Lists and signed objects. This profile\n defines the object (file) naming scheme, the contents of repository\n publication points (directories), and a suggested internal structure\n of a local repository cache that is intended to facilitate\n synchronization across a distributed collection of repository\n publication points and to facilitate certification path construction.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr 6481 attestation attestations certificate certificates crl holder http issuer key license path pki profile revocation signature nested-reference unchanged"},{"id":"IETF RFC 6482","type":"specification","body":"IETF","designation":"RFC 6482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6482.txt","https://www.rfc-editor.org/rfc/rfc6482.pdf"],"folder":"IETF/RFC-6482","files":{"txt":{"path":"standards/IETF/RFC-6482/RFC-6482.txt","sha256":"c4d8f774df6a76eacd6c0c020f717314f762ed789a24015ceb843a5b3e3777d0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a standard profile for Route Origin\n Authorizations (ROAs). A ROA is a digitally signed object that\n provides a means of verifying that an IP address block holder has\n authorized an Autonomous System (AS) to originate routes to one or\n more prefixes within the address block.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6482.\n\nCopyright Notice\n\n Copyright (c) 201","scope_keywords":["6482","attestation","attribute","authorization","certificate","certificates","crl","holder","http","key","license","pki","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6483","folder":"IETF/RFC-6483","source":"IETF/RFC-6483/RFC-6483.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6811","folder":"IETF/RFC-6811","source":"IETF/RFC-6811/RFC-6811.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6482 This document defines a standard profile for Route Origin\n Authorizations (ROAs). A ROA is a digitally signed object that\n provides a means of verifying that an IP address block holder has\n authorized an Autonomous System (AS) to originate routes to one or\n more prefixes within the address block.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6482.\n\nCopyright Notice\n\n Copyright (c) 201 6482 attestation attribute authorization certificate certificates crl holder http key license pki profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6485","type":"specification","body":"IETF","designation":"RFC 6485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6485.txt","https://www.rfc-editor.org/rfc/rfc6485.pdf"],"folder":"IETF/RFC-6485","files":{"txt":{"path":"standards/IETF/RFC-6485/RFC-6485.txt","sha256":"fc87e1f9a20520d5aae4405a23095da276d24ff0442d9a3edc9fdc2132855354"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the algorithms, algorithms' parameters,\n asymmetric key formats, asymmetric key size, and signature format for\n the Resource Public Key Infrastructure (RPKI) subscribers that\n generate digital signatures on certificates, Certificate Revocation\n Lists, and signed objects as well as for the relying parties (RPs)\n that verify these digital signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n h","scope_keywords":["6485","algorithm","algorithms","authorization","certificate","certificates","crl","encryption","hash","hashing","http","key","keys","license","pki","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null}],"search_text":"IETF RFC 6485 This document specifies the algorithms, algorithms' parameters,\n asymmetric key formats, asymmetric key size, and signature format for\n the Resource Public Key Infrastructure (RPKI) subscribers that\n generate digital signatures on certificates, Certificate Revocation\n Lists, and signed objects as well as for the relying parties (RPs)\n that verify these digital signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n h 6485 algorithm algorithms authorization certificate certificates crl encryption hash hashing http key keys license pki policy nested-reference unchanged"},{"id":"IETF RFC 6486","type":"specification","body":"IETF","designation":"RFC 6486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6486.txt","https://www.rfc-editor.org/rfc/rfc6486.pdf"],"folder":"IETF/RFC-6486","files":{"txt":{"path":"standards/IETF/RFC-6486/RFC-6486.txt","sha256":"c0f6cb019f7b180716873e1af3c09ac22784508c708da9927424b56d8b96d941"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a \"manifest\" for use in the Resource Public Key\n Infrastructure (RPKI). A manifest is a signed object (file) that\n contains a listing of all the signed objects (files) in the\n repository publication point (directory) associated with an authority\n responsible for publishing in the repository. For each certificate,\n Certificate Revocation List (CRL), or other type of signed objects\n issued by the authority that are published at this repository\n publication point, the manifest contains both the name of the file\n containing the object and a hash of the file content. Manifests are\n intended to enable a relying party (RP) to detect certain forms of\n attacks against a repository. Specifically, if an RP checks a\n manifest's contents against the signed objects retrieved from a\n repository publication point, then the RP can detect \"stale\" (valid)\n data and deletion of signed ","scope_keywords":["6486","attribute","authorization","certificate","certificates","crl","hash","http","key","license","pki","revocation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6486 This document defines a \"manifest\" for use in the Resource Public Key\n Infrastructure (RPKI). A manifest is a signed object (file) that\n contains a listing of all the signed objects (files) in the\n repository publication point (directory) associated with an authority\n responsible for publishing in the repository. For each certificate,\n Certificate Revocation List (CRL), or other type of signed objects\n issued by the authority that are published at this repository\n publication point, the manifest contains both the name of the file\n containing the object and a hash of the file content. Manifests are\n intended to enable a relying party (RP) to detect certain forms of\n attacks against a repository. Specifically, if an RP checks a\n manifest's contents against the signed objects retrieved from a\n repository publication point, then the RP can detect \"stale\" (valid)\n data and deletion of signed  6486 attribute authorization certificate certificates crl hash http key license pki revocation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6487","type":"specification","body":"IETF","designation":"RFC 6487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6487.txt","https://www.rfc-editor.org/rfc/rfc6487.pdf"],"folder":"IETF/RFC-6487","files":{"txt":{"path":"standards/IETF/RFC-6487/RFC-6487.txt","sha256":"a0ece69327eecad7464d2cebb4f3f82b1d2452414f0f3f3fbf5bee1eb8a81184"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a standard profile for X.509 certificates for\n the purpose of supporting validation of assertions of \"right-of-use\"\n of Internet Number Resources (INRs). The certificates issued under\n this profile are used to convey the issuer's authorization of the\n subject to be regarded as the current holder of a \"right-of-use\" of\n the INRs that are described in the certificate. This document\n contains the normative specification of Certificate and Certificate\n Revocation List (CRL) syntax in the Resource Public Key\n Infrastructure (RPKI). This document also specifies profiles for the\n format of certificate requests and specifies the Relying Party RPKI\n certificate path validation procedure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF comm","scope_keywords":["6487","algorithm","attribute","attributes","authorization","certificate","certificates","crl","holder","http","issuer","key","license","path","pki","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6488","folder":"IETF/RFC-6488","source":"IETF/RFC-6488/RFC-6488.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6487 This document defines a standard profile for X.509 certificates for\n the purpose of supporting validation of assertions of \"right-of-use\"\n of Internet Number Resources (INRs). The certificates issued under\n this profile are used to convey the issuer's authorization of the\n subject to be regarded as the current holder of a \"right-of-use\" of\n the INRs that are described in the certificate. This document\n contains the normative specification of Certificate and Certificate\n Revocation List (CRL) syntax in the Resource Public Key\n Infrastructure (RPKI). This document also specifies profiles for the\n format of certificate requests and specifies the Relying Party RPKI\n certificate path validation procedure.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF comm 6487 algorithm attribute attributes authorization certificate certificates crl holder http issuer key license path pki policies nested-reference unchanged"},{"id":"IETF RFC 6488","type":"specification","body":"IETF","designation":"RFC 6488","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6488.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6488.txt","https://www.rfc-editor.org/rfc/rfc6488.pdf"],"folder":"IETF/RFC-6488","files":{"txt":{"path":"standards/IETF/RFC-6488/RFC-6488.txt","sha256":"672dd0c29c3fe7fc1362277a97014a3f0f71c6cf608272fac22d41d69bdba36d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a generic profile for signed objects used in\n the Resource Public Key Infrastructure (RPKI). These RPKI signed\n objects make use of Cryptographic Message Syntax (CMS) as a standard\n encapsulation format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6488.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All ri","scope_keywords":["6488","algorithm","algorithms","attribute","authorization","certificate","certificates","crl","holder","http","key","license","pki","profile","revocation","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6485","folder":"IETF/RFC-6485","source":"IETF/RFC-6485/RFC-6485.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6489","folder":"IETF/RFC-6489","source":"IETF/RFC-6489/RFC-6489.txt","version":null},{"body":"IETF","designation":"RFC 6493","folder":"IETF/RFC-6493","source":"IETF/RFC-6493/RFC-6493.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6488 This document defines a generic profile for signed objects used in\n the Resource Public Key Infrastructure (RPKI). These RPKI signed\n objects make use of Cryptographic Message Syntax (CMS) as a standard\n encapsulation format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6488.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All ri 6488 algorithm algorithms attribute authorization certificate certificates crl holder http key license pki profile revocation signature nested-reference unchanged"},{"id":"IETF RFC 6489","type":"specification","body":"IETF","designation":"RFC 6489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6489.txt","https://www.rfc-editor.org/rfc/rfc6489.pdf"],"folder":"IETF/RFC-6489","files":{"txt":{"path":"standards/IETF/RFC-6489/RFC-6489.txt","sha256":"a07a953ac1fe26a96ca046f9971c60843efba387ac0e62b791cdd94ca70b6c00"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how a Certification Authority (CA) in the\n Resource Public Key Infrastructure (RPKI) performs a planned rollover\n of its key pair. This document also notes the implications of this\n key rollover procedure for relying parties (RPs). In general, RPs\n are expected to maintain a local cache of the objects that have been\n published in the RPKI repository, and thus the way in which a CA\n performs key rollover impacts RPs.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any ","scope_keywords":["6489","algorithm","attestation","attestations","certificate","certificates","crl","http","key","license","path","pki","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null}],"search_text":"IETF RFC 6489 This document describes how a Certification Authority (CA) in the\n Resource Public Key Infrastructure (RPKI) performs a planned rollover\n of its key pair. This document also notes the implications of this\n key rollover procedure for relying parties (RPs). In general, RPs\n are expected to maintain a local cache of the objects that have been\n published in the RPKI repository, and thus the way in which a CA\n performs key rollover impacts RPs.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any  6489 algorithm attestation attestations certificate certificates crl http key license path pki profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6490","type":"specification","body":"IETF","designation":"RFC 6490","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6490.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6490.txt","https://www.rfc-editor.org/rfc/rfc6490.pdf"],"folder":"IETF/RFC-6490","files":{"txt":{"path":"standards/IETF/RFC-6490/RFC-6490.txt","sha256":"8fb65dc478182e7603a9fe8453d3a492789552cfe42989811f748d799a729f13"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Trust Anchor Locator (TAL) for the Resource\n Public Key Infrastructure (RPKI).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6490.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http","scope_keywords":["6490","certificate","certificates","crl","http","key","license","path","pki","profile","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null}],"search_text":"IETF RFC 6490 This document defines a Trust Anchor Locator (TAL) for the Resource\n Public Key Infrastructure (RPKI).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6490.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http 6490 certificate certificates crl http key license path pki profile subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6492","type":"specification","body":"IETF","designation":"RFC 6492","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6492.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6492.txt","https://www.rfc-editor.org/rfc/rfc6492.pdf"],"folder":"IETF/RFC-6492","files":{"txt":{"path":"standards/IETF/RFC-6492/RFC-6492.txt","sha256":"c54031a4c8ba98e13dddd10083a589a6ed6b9344799fbcce4e40f5d9e2e30ad8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for certificate management\n interactions between an Internet Number Resource issuer (\"issuer\")\n and an Internet Number Resource recipient (\"subject\") through the\n specification of a protocol for interaction between the two parties.\n The protocol supports the transmission of requests from the subject,\n and corresponding responses from the issuer encompassing the actions\n of certificate issuance, certificate revocation, and certificate\n status information reports. This protocol is intended to be limited\n to the application of Internet Number Resource Certificate management\n and is not intended to be used as part of a more general certificate\n management framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community","scope_keywords":["6492","certificate","certificates","http","issuer","key","keys","license","management","pki","profile","revocation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null}],"search_text":"IETF RFC 6492 This document defines a framework for certificate management\n interactions between an Internet Number Resource issuer (\"issuer\")\n and an Internet Number Resource recipient (\"subject\") through the\n specification of a protocol for interaction between the two parties.\n The protocol supports the transmission of requests from the subject,\n and corresponding responses from the issuer encompassing the actions\n of certificate issuance, certificate revocation, and certificate\n status information reports. This protocol is intended to be limited\n to the application of Internet Number Resource Certificate management\n and is not intended to be used as part of a more general certificate\n management framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community 6492 certificate certificates http issuer key keys license management pki profile revocation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6493","type":"specification","body":"IETF","designation":"RFC 6493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6493.txt","https://www.rfc-editor.org/rfc/rfc6493.pdf"],"folder":"IETF/RFC-6493","files":{"txt":{"path":"standards/IETF/RFC-6493/RFC-6493.txt","sha256":"4bd804550d7720b659d31bb24838d0422e197cd1cb38b36fc7adf04a7814f541"}},"tags":["nested-reference","unchanged"],"summary":"In the Resource Public Key Infrastructure (RPKI), resource\n certificates completely obscure names or any other information that\n might be useful for contacting responsible parties to deal with\n issues of certificate expiration, maintenance, roll-overs,\n compromises, etc. This document describes the RPKI Ghostbusters\n Record containing human contact information that may be verified\n (indirectly) by a Certification Authority (CA) certificate. The data\n in the record are those of a severely profiled vCard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of R","scope_keywords":["6493","attestation","authorization","certificate","certificates","crl","holder","http","key","license","path","pki","profile","profiles","revocation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6916","folder":"IETF/RFC-6916","source":"IETF/RFC-6916/RFC-6916.txt","version":null},{"body":"IETF","designation":"RFC 7132","folder":"IETF/RFC-7132","source":"IETF/RFC-7132/RFC-7132.txt","version":null}],"search_text":"IETF RFC 6493 In the Resource Public Key Infrastructure (RPKI), resource\n certificates completely obscure names or any other information that\n might be useful for contacting responsible parties to deal with\n issues of certificate expiration, maintenance, roll-overs,\n compromises, etc. This document describes the RPKI Ghostbusters\n Record containing human contact information that may be verified\n (indirectly) by a Certification Authority (CA) certificate. The data\n in the record are those of a severely profiled vCard.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of R 6493 attestation authorization certificate certificates crl holder http key license path pki profile profiles revocation subject nested-reference unchanged"},{"id":"IETF RFC 6494","type":"specification","body":"IETF","designation":"RFC 6494","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6494.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6494.txt","https://www.rfc-editor.org/rfc/rfc6494.pdf"],"folder":"IETF/RFC-6494","files":{"txt":{"path":"standards/IETF/RFC-6494/RFC-6494.txt","sha256":"6dcacf0a3a53f311df6032e1d8d7e056c854a3f7f209ff85551af08c30807f6d"}},"tags":["nested-reference","unchanged"],"summary":"SEcure Neighbor Discovery (SEND) utilizes X.509v3 certificates for\n performing router authorization. This document specifies a\n certificate profile for SEND based on resource certificates along\n with extended key usage values required for SEND.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6494.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n docume","scope_keywords":["6494","authorization","certificate","certificates","crl","http","key","license","management","ocsp","pki","profile","revocation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null}],"search_text":"IETF RFC 6494 SEcure Neighbor Discovery (SEND) utilizes X.509v3 certificates for\n performing router authorization. This document specifies a\n certificate profile for SEND based on resource certificates along\n with extended key usage values required for SEND.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6494.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n docume 6494 authorization certificate certificates crl http key license management ocsp pki profile revocation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6495","type":"specification","body":"IETF","designation":"RFC 6495","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6495.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6495.txt","https://www.rfc-editor.org/rfc/rfc6495.pdf"],"folder":"IETF/RFC-6495","files":{"txt":{"path":"standards/IETF/RFC-6495/RFC-6495.txt","sha256":"88fea5227c6ae2927b4b59dbbfe1df3d1d94f7f7745c3a731d6a5e9ec54f6a2d"}},"tags":["nested-reference","unchanged"],"summary":"SEcure Neighbor Discovery (SEND) defines the Name Type field in the\n ICMPv6 Trust Anchor option. This document specifies new Name Type\n fields based on certificate Subject Key Identifiers (SKIs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6495.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["6495","certificate","certificates","hash","http","identification","key","license","path","profile","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null}],"search_text":"IETF RFC 6495 SEcure Neighbor Discovery (SEND) defines the Name Type field in the\n ICMPv6 Trust Anchor option. This document specifies new Name Type\n fields based on certificate Subject Key Identifiers (SKIs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6495.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  6495 certificate certificates hash http identification key license path profile qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6496","type":"specification","body":"IETF","designation":"RFC 6496","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6496.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6496.txt","https://www.rfc-editor.org/rfc/rfc6496.pdf"],"folder":"IETF/RFC-6496","files":{"txt":{"path":"standards/IETF/RFC-6496/RFC-6496.txt","sha256":"2a4c211b1ba301cd8e024c65e43089e90b3c0c3a0f45a92f4916dc1ae9a2c514"}},"tags":["nested-reference","unchanged"],"summary":"SEcure Neighbor Discovery (SEND) specifies a method for securing\n Neighbor Discovery (ND) signaling against specific threats. As\n defined today, SEND assumes that the node sending an ND message is\n the owner of the address from which the message is sent and/or\n possesses a key that authorizes the node to act as a router, so that\n it is in possession of the private key or keys used to generate the\n digital signature on each message. This means that the Proxy ND\n signaling performed by nodes that do not possess knowledge of the\n address owner's private key and/or knowledge of a router's key cannot\n be secured using SEND. This document extends the current SEND\n specification in order to secure Proxy ND operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This docume","scope_keywords":["6496","authorization","http","key","keys","license","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6494","folder":"IETF/RFC-6494","source":"IETF/RFC-6494/RFC-6494.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null}],"search_text":"IETF RFC 6496 SEcure Neighbor Discovery (SEND) specifies a method for securing\n Neighbor Discovery (ND) signaling against specific threats. As\n defined today, SEND assumes that the node sending an ND message is\n the owner of the address from which the message is sent and/or\n possesses a key that authorizes the node to act as a router, so that\n it is in possession of the private key or keys used to generate the\n digital signature on each message. This means that the Proxy ND\n signaling performed by nodes that do not possess knowledge of the\n address owner's private key and/or knowledge of a router's key cannot\n be secured using SEND. This document extends the current SEND\n specification in order to secure Proxy ND operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This docume 6496 authorization http key keys license signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6501","type":"specification","body":"IETF","designation":"RFC 6501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6501.txt","https://www.rfc-editor.org/rfc/rfc6501.pdf"],"folder":"IETF/RFC-6501","files":{"txt":{"path":"standards/IETF/RFC-6501/RFC-6501.txt","sha256":"03f7226ba5c5b1733ad1d1004020001b9bba5529c7d90970402ceff653ca2c1f"}},"tags":["nested-reference","unchanged"],"summary":"RFC 5239 defines centralized conferencing (XCON) as an association of\n participants with a central focus. The state of a conference is\n represented by a conference object. This document defines an XML-\n based conference information data model to be used for conference\n objects. A conference information data model is designed to convey\n information about the conference and about participation in the\n conference. The conference information data model defined in this\n document constitutes an extension of the data format specified in the\n Session Initiation Protocol (SIP) event package for conference State.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine","scope_keywords":["6501","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 6501 RFC 5239 defines centralized conferencing (XCON) as an association of\n participants with a central focus. The state of a conference is\n represented by a conference object. This document defines an XML-\n based conference information data model to be used for conference\n objects. A conference information data model is designed to convey\n information about the conference and about participation in the\n conference. The conference information data model defined in this\n document constitutes an extension of the data format specified in the\n Session Initiation Protocol (SIP) event package for conference State.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engine 6501 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6503","type":"specification","body":"IETF","designation":"RFC 6503","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6503.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6503.txt","https://www.rfc-editor.org/rfc/rfc6503.pdf"],"folder":"IETF/RFC-6503","files":{"txt":{"path":"standards/IETF/RFC-6503/RFC-6503.txt","sha256":"39218db99a4467cb95f99bf897e6b36ed113ccb8a73ea2d5f436613a09461dba"}},"tags":["nested-reference","unchanged"],"summary":"The Centralized Conferencing Manipulation Protocol (CCMP) allows a\n Centralized Conferencing (XCON) system client to create, retrieve,\n change, and delete objects that describe a centralized conference.\n CCMP is a means to control basic and advanced conference features\n such as conference state and capabilities, participants, relative\n roles, and details. CCMP is a stateless, XML-based, client server\n protocol that carries, in its request and response messages,\n conference information in the form of XML documents and fragments\n conforming to the centralized conferencing data model schema.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering ","scope_keywords":["6503","authentication","authorization","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 6503 The Centralized Conferencing Manipulation Protocol (CCMP) allows a\n Centralized Conferencing (XCON) system client to create, retrieve,\n change, and delete objects that describe a centralized conference.\n CCMP is a means to control basic and advanced conference features\n such as conference state and capabilities, participants, relative\n roles, and details. CCMP is a stateless, XML-based, client server\n protocol that carries, in its request and response messages,\n conference information in the form of XML documents and fragments\n conforming to the centralized conferencing data model schema.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering  6503 authentication authorization http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6507","type":"specification","body":"IETF","designation":"RFC 6507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6507.txt","https://www.rfc-editor.org/rfc/rfc6507.pdf"],"folder":"IETF/RFC-6507","files":{"txt":{"path":"standards/IETF/RFC-6507/RFC-6507.txt","sha256":"b026ed202060ddc3cb6f7cd92e402fa5d209a4f3df07fa818a77f6ade5aa22f9"}},"tags":["nested-reference","unchanged"],"summary":"Many signature schemes currently in use rely on certificates for\n authentication of identity. In Identity-based cryptography, this\n adds unnecessary overhead and administration. The Elliptic Curve-\n based Certificateless Signatures for Identity-based Encryption\n (ECCSI) signature scheme described in this document is\n certificateless. This scheme has the additional advantages of low\n bandwidth and low computational requirements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this doc","scope_keywords":["6507","algorithm","algorithms","authentication","certificate","certificates","encryption","http","key","license","management","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null}],"search_text":"IETF RFC 6507 Many signature schemes currently in use rely on certificates for\n authentication of identity. In Identity-based cryptography, this\n adds unnecessary overhead and administration. The Elliptic Curve-\n based Certificateless Signatures for Identity-based Encryption\n (ECCSI) signature scheme described in this document is\n certificateless. This scheme has the additional advantages of low\n bandwidth and low computational requirements.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this doc 6507 algorithm algorithms authentication certificate certificates encryption http key license management presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6508","type":"specification","body":"IETF","designation":"RFC 6508","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6508.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6508.txt","https://www.rfc-editor.org/rfc/rfc6508.pdf"],"folder":"IETF/RFC-6508","files":{"txt":{"path":"standards/IETF/RFC-6508/RFC-6508.txt","sha256":"adef469b5a553d180bc52fbf108ce66819830f6b83a838bacb93f1d74a27dd9e"}},"tags":["nested-reference","unchanged"],"summary":"In this document, the Sakai-Kasahara Key Encryption (SAKKE) algorithm\n is described. This uses Identity-Based Encryption to exchange a\n shared secret from a Sender to a Receiver.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6508.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document","scope_keywords":["6508","algorithm","algorithms","certificate","encryption","hash","hashing","http","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null}],"search_text":"IETF RFC 6508 In this document, the Sakai-Kasahara Key Encryption (SAKKE) algorithm\n is described. This uses Identity-Based Encryption to exchange a\n shared secret from a Sender to a Receiver.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6508.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document 6508 algorithm algorithms certificate encryption hash hashing http key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6509","type":"specification","body":"IETF","designation":"RFC 6509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6509.txt","https://www.rfc-editor.org/rfc/rfc6509.pdf"],"folder":"IETF/RFC-6509","files":{"txt":{"path":"standards/IETF/RFC-6509/RFC-6509.txt","sha256":"94229c0a20f37b4082cba2976de93fe33d1dc3853428f61ade8792a163b14fc1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Multimedia Internet KEYing-Sakai-Kasahara\n Key Encryption (MIKEY-SAKKE), a method of key exchange that uses\n Identity-based Public Key Cryptography (IDPKC) to establish a shared\n secret value and certificateless signatures to provide source\n authentication. MIKEY-SAKKE has a number of desirable features,\n including simplex transmission, scalability, low-latency call setup,\n and support for secure deferred delivery.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current sta","scope_keywords":["6509","algorithm","algorithms","authentication","certificate","certificates","delivery","encryption","http","key","keys","license","management","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6507","folder":"IETF/RFC-6507","source":"IETF/RFC-6507/RFC-6507.txt","version":null},{"body":"IETF","designation":"RFC 6508","folder":"IETF/RFC-6508","source":"IETF/RFC-6508/RFC-6508.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null}],"search_text":"IETF RFC 6509 This document describes the Multimedia Internet KEYing-Sakai-Kasahara\n Key Encryption (MIKEY-SAKKE), a method of key exchange that uses\n Identity-based Public Key Cryptography (IDPKC) to establish a shared\n secret value and certificateless signatures to provide source\n authentication. MIKEY-SAKKE has a number of desirable features,\n including simplex transmission, scalability, low-latency call setup,\n and support for secure deferred delivery.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current sta 6509 algorithm algorithms authentication certificate certificates delivery encryption http key keys license management signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 6510","type":"specification","body":"IETF","designation":"RFC 6510","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6510.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6510.txt","https://www.rfc-editor.org/rfc/rfc6510.pdf"],"folder":"IETF/RFC-6510","files":{"txt":{"path":"standards/IETF/RFC-6510/RFC-6510.txt","sha256":"0f0a059dc3771217db20f15e46dd7c0c1c01ee5cb0bffad8944936c9f0fd228b"}},"tags":["nested-reference","unchanged"],"summary":"Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)\n established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions may be signaled with a set of LSP-\n specific attributes. These attributes may be carried in both Path\n and Resv messages. This document specifies how LSP attributes are to\n be carried in RSVP Path and Resv messages using the Routing Backus-\n Naur Form and clarifies related Resv message formats. This document\n updates RFC 4875 and RFC 5420.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741","scope_keywords":["6510","attribute","attributes","http","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null}],"search_text":"IETF RFC 6510 Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)\n established using the Resource Reservation Protocol Traffic\n Engineering (RSVP-TE) extensions may be signaled with a set of LSP-\n specific attributes. These attributes may be carried in both Path\n and Resv messages. This document specifies how LSP attributes are to\n be carried in RSVP Path and Resv messages using the Routing Backus-\n Naur Form and clarifies related Resv message formats. This document\n updates RFC 4875 and RFC 5420.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741 6510 attribute attributes http key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6511","type":"specification","body":"IETF","designation":"RFC 6511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6511.txt","https://www.rfc-editor.org/rfc/rfc6511.pdf"],"folder":"IETF/RFC-6511","files":{"txt":{"path":"standards/IETF/RFC-6511/RFC-6511.txt","sha256":"654de6386e818e69cd99e944aba9840fcf39a0ad1c7a422ce64ec08d5d389263"}},"tags":["nested-reference","unchanged"],"summary":"There are many deployment scenarios that require an egress Label\n Switching Router (LSR) to receive binding of the Resource Reservation\n Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to\n an application and a payload identifier using some \"out-of-band\"\n (OOB) mechanism. This document defines protocol mechanisms to\n address this requirement. The procedures described in this document\n are equally applicable for point-to-point (P2P) and point-to-\n multipoint (P2MP) LSPs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Infor","scope_keywords":["6511","attribute","attributes","http","key","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6510","folder":"IETF/RFC-6510","source":"IETF/RFC-6510/RFC-6510.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null}],"search_text":"IETF RFC 6511 There are many deployment scenarios that require an egress Label\n Switching Router (LSR) to receive binding of the Resource Reservation\n Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to\n an application and a payload identifier using some \"out-of-band\"\n (OOB) mechanism. This document defines protocol mechanisms to\n address this requirement. The procedures described in this document\n are equally applicable for point-to-point (P2P) and point-to-\n multipoint (P2MP) LSPs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Infor 6511 attribute attributes http key license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6512","type":"specification","body":"IETF","designation":"RFC 6512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6512.txt","https://www.rfc-editor.org/rfc/rfc6512.pdf"],"folder":"IETF/RFC-6512","files":{"txt":{"path":"standards/IETF/RFC-6512/RFC-6512.txt","sha256":"7d9a9aa07b920f95d17cc83fca8d070e2938576f1f1c483c8172cec7b3b60bb7"}},"tags":["nested-reference","unchanged"],"summary":"The control protocol used for constructing Point-to-Multipoint and\n Multipoint-to-Multipoint Label Switched Paths (\"MP LSPs\") contains a\n field that identifies the address of a \"root node\". Intermediate\n nodes are expected to be able to look up that address in their\n routing tables. However, this is not possible if the route to the\n root node is a BGP route and the intermediate nodes are part of a\n BGP-free core. This document specifies procedures that enable an MP\n LSP to be constructed through a BGP-free core. In these procedures,\n the root node address is temporarily replaced by an address that is\n known to the intermediate nodes and is on the path to the true root\n node.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pu","scope_keywords":["6512","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7117","folder":"IETF/RFC-7117","source":"IETF/RFC-7117/RFC-7117.txt","version":null}],"search_text":"IETF RFC 6512 The control protocol used for constructing Point-to-Multipoint and\n Multipoint-to-Multipoint Label Switched Paths (\"MP LSPs\") contains a\n field that identifies the address of a \"root node\". Intermediate\n nodes are expected to be able to look up that address in their\n routing tables. However, this is not possible if the route to the\n root node is a BGP route and the intermediate nodes are part of a\n BGP-free core. This document specifies procedures that enable an MP\n LSP to be constructed through a BGP-free core. In these procedures,\n the root node address is temporarily replaced by an address that is\n known to the intermediate nodes and is on the path to the true root\n node.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pu 6512 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6520","type":"specification","body":"IETF","designation":"RFC 6520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6520.txt","https://www.rfc-editor.org/rfc/rfc6520.pdf"],"folder":"IETF/RFC-6520","files":{"txt":{"path":"standards/IETF/RFC-6520/RFC-6520.txt","sha256":"c91107dd629722b8bd9b5a03ae9493d33f7ea0930d3aab3b2e081e8d2946c44d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Heartbeat Extension for the Transport\n Layer Security (TLS) and Datagram Transport Layer Security (DTLS)\n protocols.\n\n The Heartbeat Extension provides a new protocol for TLS/DTLS allowing\n the usage of keep-alive functionality without performing a\n renegotiation and a basis for path MTU (PMTU) discovery for DTLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r","scope_keywords":["6520","http","key","license","management","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 6520 This document describes the Heartbeat Extension for the Transport\n Layer Security (TLS) and Datagram Transport Layer Security (DTLS)\n protocols.\n\n The Heartbeat Extension provides a new protocol for TLS/DTLS allowing\n the usage of keep-alive functionality without performing a\n renegotiation and a basis for path MTU (PMTU) discovery for DTLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r 6520 http key license management path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6525","type":"specification","body":"IETF","designation":"RFC 6525","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6525.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6525.txt","https://www.rfc-editor.org/rfc/rfc6525.pdf"],"folder":"IETF/RFC-6525","files":{"txt":{"path":"standards/IETF/RFC-6525/RFC-6525.txt","sha256":"c05b5607ceb697c90e156fcc197bce42fbf6dd4303d55658b9c4115049da27de"}},"tags":["nested-reference","unchanged"],"summary":"Many applications that use the Stream Control Transmission Protocol\n (SCTP) want the ability to \"reset\" a stream. The intention of\n resetting a stream is to set the numbering sequence of the stream\n back to 'zero' with a corresponding notification to the application\n layer that the reset has been performed. Applications requiring this\n feature want it so that they can \"reuse\" streams for different\n purposes but still utilize the stream sequence number so that the\n application can track the message flows. Thus, without this feature,\n a new use of an old stream would result in message numbers greater\n than expected, unless there is a protocol mechanism to \"reset the\n streams back to zero\". This document also includes methods for\n resetting the transmission sequence numbers, adding additional\n streams, and resetting all stream sequence numbers.\n\nStatus of This Memo\n\n This is an Internet Sta","scope_keywords":["6525","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 7053","folder":"IETF/RFC-7053","source":"IETF/RFC-7053/RFC-7053.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null}],"search_text":"IETF RFC 6525 Many applications that use the Stream Control Transmission Protocol\n (SCTP) want the ability to \"reset\" a stream. The intention of\n resetting a stream is to set the numbering sequence of the stream\n back to 'zero' with a corresponding notification to the application\n layer that the reset has been performed. Applications requiring this\n feature want it so that they can \"reuse\" streams for different\n purposes but still utilize the stream sequence number so that the\n application can track the message flows. Thus, without this feature,\n a new use of an old stream would result in message numbers greater\n than expected, unless there is a protocol mechanism to \"reset the\n streams back to zero\". This document also includes methods for\n resetting the transmission sequence numbers, adding additional\n streams, and resetting all stream sequence numbers.\n\nStatus of This Memo\n\n This is an Internet Sta 6525 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6526","type":"specification","body":"IETF","designation":"RFC 6526","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6526.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6526.txt","https://www.rfc-editor.org/rfc/rfc6526.pdf"],"folder":"IETF/RFC-6526","files":{"txt":{"path":"standards/IETF/RFC-6526/RFC-6526.txt","sha256":"ee28c04949325ef31568fea1c62b3264316db5e203d467f49976e4649537bf90"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the specifications in RFC\n 5101, IP Flow Information Export (IPFIX), when using the Partial\n Reliability extension of SCTP (PR-SCTP, Partial Reliability Stream\n Control Transmission Protocol).\n\n When implemented at both the Exporting Process and Collecting\n Process, this method offers several advantages, such as the ability\n to calculate Data Record losses for PR-SCTP per Template, immediate\n export of Template Withdrawal Messages, immediate reuse of Template\n IDs within an SCTP stream, reduced likelihood of Data Record loss,\n and reduced demands on the Collecting Process. When implemented in\n only the Collecting Process or Exporting Process, then normal IPFIX\n behavior will be seen without all of the additional benefits.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Ta","scope_keywords":["6526","attribute","attributes","delivery","http","key","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null}],"search_text":"IETF RFC 6526 This document specifies an extension to the specifications in RFC\n 5101, IP Flow Information Export (IPFIX), when using the Partial\n Reliability extension of SCTP (PR-SCTP, Partial Reliability Stream\n Control Transmission Protocol).\n\n When implemented at both the Exporting Process and Collecting\n Process, this method offers several advantages, such as the ability\n to calculate Data Record losses for PR-SCTP per Template, immediate\n export of Template Withdrawal Messages, immediate reuse of Template\n IDs within an SCTP stream, reduced likelihood of Data Record loss,\n and reduced demands on the Collecting Process. When implemented in\n only the Collecting Process or Exporting Process, then normal IPFIX\n behavior will be seen without all of the additional benefits.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Ta 6526 attribute attributes delivery http key license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6536","type":"specification","body":"IETF","designation":"RFC 6536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6536.txt","https://www.rfc-editor.org/rfc/rfc6536.pdf"],"folder":"IETF/RFC-6536","files":{"txt":{"path":"standards/IETF/RFC-6536/RFC-6536.txt","sha256":"38b24085d23921b577d5239f9faaf05f16271b85badb006b97ed7fd35341464a"}},"tags":["nested-reference","unchanged"],"summary":"The standardization of network configuration interfaces for use with\n the Network Configuration Protocol (NETCONF) requires a structured\n and secure operating environment that promotes human usability and\n multi-vendor interoperability. There is a need for standard\n mechanisms to restrict NETCONF protocol access for particular users\n to a pre-configured subset of all available NETCONF protocol\n operations and content. This document defines such an access control\n model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the c","scope_keywords":["6536","authorization","http","key","license","management","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6643","folder":"IETF/RFC-6643","source":"IETF/RFC-6643/RFC-6643.txt","version":null},{"body":"IETF","designation":"RFC 7223","folder":"IETF/RFC-7223","source":"IETF/RFC-7223/RFC-7223.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7895","folder":"IETF/RFC-7895","source":"IETF/RFC-7895/RFC-7895.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null}],"search_text":"IETF RFC 6536 The standardization of network configuration interfaces for use with\n the Network Configuration Protocol (NETCONF) requires a structured\n and secure operating environment that promotes human usability and\n multi-vendor interoperability. There is a need for standard\n mechanisms to restrict NETCONF protocol access for particular users\n to a pre-configured subset of all available NETCONF protocol\n operations and content. This document defines such an access control\n model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the c 6536 authorization http key license management subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6546","type":"specification","body":"IETF","designation":"RFC 6546","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6546.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6546.txt","https://www.rfc-editor.org/rfc/rfc6546.pdf"],"folder":"IETF/RFC-6546","files":{"txt":{"path":"standards/IETF/RFC-6546/RFC-6546.txt","sha256":"d48cd4e21a23ec344c5f360458046f96552b818bbd52146fb923103f71a875f1"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) defines a\n common XML format for document exchange, and Real-time Inter-network\n Defense (RID) defines extensions to IODEF intended for the\n cooperative handling of security incidents within consortia of\n network operators and enterprises. This document specifies an\n application-layer protocol for RID based upon the passing of RID\n messages over HTTP/TLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi","scope_keywords":["6546","http","https","key","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 7203","folder":"IETF/RFC-7203","source":"IETF/RFC-7203/RFC-7203.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 6546 The Incident Object Description Exchange Format (IODEF) defines a\n common XML format for document exchange, and Real-time Inter-network\n Defense (RID) defines extensions to IODEF intended for the\n cooperative handling of security incidents within consortia of\n network operators and enterprises. This document specifies an\n application-layer protocol for RID based upon the passing of RID\n messages over HTTP/TLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi 6546 http https key license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6549","type":"specification","body":"IETF","designation":"RFC 6549","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6549.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6549.txt","https://www.rfc-editor.org/rfc/rfc6549.pdf"],"folder":"IETF/RFC-6549","files":{"txt":{"path":"standards/IETF/RFC-6549/RFC-6549.txt","sha256":"ae60fe9b153797415ead384930d6afd03570dba6ece8b42e4e57b1c606ebbfdf"}},"tags":["nested-reference","unchanged"],"summary":"OSPFv3 includes a mechanism to support multiple instances of the\n protocol running on the same interface. OSPFv2 can utilize such a\n mechanism in order to support multiple routing domains on the same\n subnet.\n\n This document defines the OSPFv2 Instance ID to enable separate\n OSPFv2 protocol instances on the same interface. Unlike OSPFv3 where\n the Instance ID can be used for multiple purposes, such as putting\n the same interface in multiple areas, the OSPFv2 Instance ID is\n reserved for identifying protocol instances.\n\n This document updates RFC 2328.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on ","scope_keywords":["6549","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 6549 OSPFv3 includes a mechanism to support multiple instances of the\n protocol running on the same interface. OSPFv2 can utilize such a\n mechanism in order to support multiple routing domains on the same\n subnet.\n\n This document defines the OSPFv2 Instance ID to enable separate\n OSPFv2 protocol instances on the same interface. Unlike OSPFv3 where\n the Instance ID can be used for multiple purposes, such as putting\n the same interface in multiple areas, the OSPFv2 Instance ID is\n reserved for identifying protocol instances.\n\n This document updates RFC 2328.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on  6549 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6552","type":"specification","body":"IETF","designation":"RFC 6552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6552.txt","https://www.rfc-editor.org/rfc/rfc6552.pdf"],"folder":"IETF/RFC-6552","files":{"txt":{"path":"standards/IETF/RFC-6552/RFC-6552.txt","sha256":"85fcc21f8f661e9dc4f9b1ac04219003cf4bce463fdbf33fdfdc523497055bc4"}},"tags":["nested-reference","unchanged"],"summary":"The Routing Protocol for Low-Power and Lossy Networks (RPL)\n specification defines a generic Distance Vector protocol that is\n adapted to a variety of network types by the application of specific\n Objective Functions (OFs). An OF states the outcome of the process\n used by a RPL node to select and optimize routes within a RPL\n Instance based on the Information Objects available; an OF is not an\n algorithm.\n\n This document specifies a basic Objective Function that relies only\n on the objects that are defined in the RPL and does not use any\n protocol extensions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat","scope_keywords":["6552","algorithm","algorithms","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6551","folder":"IETF/RFC-6551","source":"IETF/RFC-6551/RFC-6551.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null}],"search_text":"IETF RFC 6552 The Routing Protocol for Low-Power and Lossy Networks (RPL)\n specification defines a generic Distance Vector protocol that is\n adapted to a variety of network types by the application of specific\n Objective Functions (OFs). An OF states the outcome of the process\n used by a RPL node to select and optimize routes within a RPL\n Instance based on the Information Objects available; an OF is not an\n algorithm.\n\n This document specifies a basic Objective Function that relies only\n on the objects that are defined in the RPL and does not use any\n protocol extensions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat 6552 algorithm algorithms http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6553","type":"specification","body":"IETF","designation":"RFC 6553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6553.txt","https://www.rfc-editor.org/rfc/rfc6553.pdf"],"folder":"IETF/RFC-6553","files":{"txt":{"path":"standards/IETF/RFC-6553/RFC-6553.txt","sha256":"bfa1a9bb91ccb813b80139b771846d1005c7b369361d98267a0b78daf45f8fb1"}},"tags":["nested-reference","unchanged"],"summary":"The Routing Protocol for Low-Power and Lossy Networks (RPL) includes\n routing information in data-plane datagrams to quickly identify\n inconsistencies in the routing topology. This document describes the\n RPL Option for use among RPL routers to include such routing\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6553.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and th","scope_keywords":["6553","delivery","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null}],"search_text":"IETF RFC 6553 The Routing Protocol for Low-Power and Lossy Networks (RPL) includes\n routing information in data-plane datagrams to quickly identify\n inconsistencies in the routing topology. This document describes the\n RPL Option for use among RPL routers to include such routing\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6553.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and th 6553 delivery http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6554","type":"specification","body":"IETF","designation":"RFC 6554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6554.txt","https://www.rfc-editor.org/rfc/rfc6554.pdf"],"folder":"IETF/RFC-6554","files":{"txt":{"path":"standards/IETF/RFC-6554/RFC-6554.txt","sha256":"f420039074dca4b75f0c978cc36af9771ee461241487455dc934be4139635180"}},"tags":["nested-reference","unchanged"],"summary":"In Low-Power and Lossy Networks (LLNs), memory constraints on routers\n may limit them to maintaining, at most, a few routes. In some\n configurations, it is necessary to use these memory-constrained\n routers to deliver datagrams to nodes within the LLN. The Routing\n Protocol for Low-Power and Lossy Networks (RPL) can be used in some\n deployments to store most, if not all, routes on one (e.g., the\n Directed Acyclic Graph (DAG) root) or a few routers and forward the\n IPv6 datagram using a source routing technique to avoid large routing\n tables on memory-constrained routers. This document specifies a new\n IPv6 Routing header type for delivering datagrams within a RPL\n routing domain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receiv","scope_keywords":["6554","http","key","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6553","folder":"IETF/RFC-6553","source":"IETF/RFC-6553/RFC-6553.txt","version":null},{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null},{"body":"IETF","designation":"RFC 6998","folder":"IETF/RFC-6998","source":"IETF/RFC-6998/RFC-6998.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null}],"search_text":"IETF RFC 6554 In Low-Power and Lossy Networks (LLNs), memory constraints on routers\n may limit them to maintaining, at most, a few routes. In some\n configurations, it is necessary to use these memory-constrained\n routers to deliver datagrams to nodes within the LLN. The Routing\n Protocol for Low-Power and Lossy Networks (RPL) can be used in some\n deployments to store most, if not all, routes on one (e.g., the\n Directed Acyclic Graph (DAG) root) or a few routers and forward the\n IPv6 datagram using a source routing technique to avoid large routing\n tables on memory-constrained routers. This document specifies a new\n IPv6 Routing header type for delivering datagrams within a RPL\n routing domain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receiv 6554 http key license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6562","type":"specification","body":"IETF","designation":"RFC 6562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6562.txt","https://www.rfc-editor.org/rfc/rfc6562.pdf"],"folder":"IETF/RFC-6562","files":{"txt":{"path":"standards/IETF/RFC-6562/RFC-6562.txt","sha256":"5a71c2c709d6b3ec54bc7460301f444974778e6bea9fc810fde7e9724fc6628b"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses potential security issues that arise when using\n variable bit rate (VBR) audio with the secure RTP profile.\n Guidelines to mitigate these issues are suggested.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6562.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BC","scope_keywords":["6562","authentication","encryption","http","key","license","profile","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 6562 This memo discusses potential security issues that arise when using\n variable bit rate (VBR) audio with the secure RTP profile.\n Guidelines to mitigate these issues are suggested.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6562.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BC 6562 authentication encryption http key license profile risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6564","type":"specification","body":"IETF","designation":"RFC 6564","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6564.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6564.txt","https://www.rfc-editor.org/rfc/rfc6564.pdf"],"folder":"IETF/RFC-6564","files":{"txt":{"path":"standards/IETF/RFC-6564/RFC-6564.txt","sha256":"61888428a98e6e24f7a3b8c68cc0b33d0046a0b6fd49f78a86b161ed446375c9"}},"tags":["nested-reference","unchanged"],"summary":"In IPv6, optional internet-layer information is encoded in separate\n headers that may be placed between the IPv6 header and the transport-\n layer header. There are a small number of such extension headers\n currently defined. This document describes the issues that can arise\n when defining new extension headers and discusses the alternate\n extension mechanisms in IPv6. It also provides a common format for\n defining any new IPv6 extension headers, if they are needed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curren","scope_keywords":["6564","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 6564 In IPv6, optional internet-layer information is encoded in separate\n headers that may be placed between the IPv6 header and the transport-\n layer header. There are a small number of such extension headers\n currently defined. This document describes the issues that can arise\n when defining new extension headers and discusses the alternate\n extension mechanisms in IPv6. It also provides a common format for\n defining any new IPv6 extension headers, if they are needed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the curren 6564 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6570","type":"specification","body":"IETF","designation":"RFC 6570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6570.txt","https://www.rfc-editor.org/rfc/rfc6570.pdf"],"folder":"IETF/RFC-6570","files":{"txt":{"path":"standards/IETF/RFC-6570/RFC-6570.txt","sha256":"c7b8c79f432821e867fafb1127080545202994c156405ae89cbae42ec0c66810"}},"tags":["nested-reference","unchanged"],"summary":"A URI Template is a compact sequence of characters for describing a\n range of Uniform Resource Identifiers through variable expansion.\n This specification defines the URI Template syntax and the process\n for expanding a URI Template into a URI reference, along with\n guidelines for the use of URI Templates on the Internet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6570.\n\nCopyright N","scope_keywords":["6570","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 7072","folder":"IETF/RFC-7072","source":"IETF/RFC-7072/RFC-7072.txt","version":null},{"body":"IETF","designation":"RFC 7320","folder":"IETF/RFC-7320","source":"IETF/RFC-7320/RFC-7320.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null}],"search_text":"IETF RFC 6570 A URI Template is a compact sequence of characters for describing a\n range of Uniform Resource Identifiers through variable expansion.\n This specification defines the URI Template syntax and the process\n for expanding a URI Template into a URI reference, along with\n guidelines for the use of URI Templates on the Internet.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6570.\n\nCopyright N 6570 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6577","type":"specification","body":"IETF","designation":"RFC 6577","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6577.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6577.txt","https://www.rfc-editor.org/rfc/rfc6577.pdf"],"folder":"IETF/RFC-6577","files":{"txt":{"path":"standards/IETF/RFC-6577/RFC-6577.txt","sha256":"d700011af845f66a6128e563501b3e0f5fa5dd4f1271cbb17928c41fdbd9e577"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates the registry of authentication method results in\n Authentication-Results: message header fields, correcting a\n discontinuity between the original registry creation and the Sender\n Policy Framework (SPF) specification.\n\n This memo updates RFC 5451.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6577.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons iden","scope_keywords":["6577","authentication","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null}],"search_text":"IETF RFC 6577 This memo updates the registry of authentication method results in\n Authentication-Results: message header fields, correcting a\n discontinuity between the original registry creation and the Sender\n Policy Framework (SPF) specification.\n\n This memo updates RFC 5451.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6577.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons iden 6577 authentication http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6585","type":"specification","body":"IETF","designation":"RFC 6585","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6585.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6585.txt","https://www.rfc-editor.org/rfc/rfc6585.pdf"],"folder":"IETF/RFC-6585","files":{"txt":{"path":"standards/IETF/RFC-6585/RFC-6585.txt","sha256":"f6d55d1b491cd515c35827cf9181753b23b2a68c4df14e56d83dc445b3876e58"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies additional HyperText Transfer Protocol (HTTP)\n status codes for a variety of common situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6585.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF","scope_keywords":["6585","authentication","credential","credentials","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null}],"search_text":"IETF RFC 6585 This document specifies additional HyperText Transfer Protocol (HTTP)\n status codes for a variety of common situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6585.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF 6585 authentication credential credentials http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6603","type":"specification","body":"IETF","designation":"RFC 6603","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6603.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6603.txt","https://www.rfc-editor.org/rfc/rfc6603.pdf"],"folder":"IETF/RFC-6603","files":{"txt":{"path":"standards/IETF/RFC-6603/RFC-6603.txt","sha256":"c06ffc02e9a8fef9d929e902e01fecdd29ceb95fa2e396d3a49e5acaaed8d3be"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an optional mechanism to allow exclusion\n of one specific prefix from a delegated prefix set when using\n DHCPv6-based prefix delegation. The new mechanism updates RFC 3633.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6603.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docum","scope_keywords":["6603","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6603 This specification defines an optional mechanism to allow exclusion\n of one specific prefix from a delegated prefix set when using\n DHCPv6-based prefix delegation. The new mechanism updates RFC 3633.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6603.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docum 6603 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6605","type":"specification","body":"IETF","designation":"RFC 6605","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6605.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6605.txt","https://www.rfc-editor.org/rfc/rfc6605.pdf"],"folder":"IETF/RFC-6605","files":{"txt":{"path":"standards/IETF/RFC-6605/RFC-6605.txt","sha256":"fa9b6f1fb4fb8426bdb0c56c134af3f1d962414082e3953f1c4e4e861ff459ee"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to specify Elliptic Curve Digital\n Signature Algorithm (DSA) keys and signatures in DNS Security\n (DNSSEC). It lists curves of different sizes and uses the SHA-2\n family of hashes for signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6605.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All right","scope_keywords":["6605","algorithm","algorithms","authentication","hash","http","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6781","folder":"IETF/RFC-6781","source":"IETF/RFC-6781/RFC-6781.txt","version":null}],"search_text":"IETF RFC 6605 This document describes how to specify Elliptic Curve Digital\n Signature Algorithm (DSA) keys and signatures in DNS Security\n (DNSSEC). It lists curves of different sizes and uses the SHA-2\n family of hashes for signatures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6605.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All right 6605 algorithm algorithms authentication hash http key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6613","type":"specification","body":"IETF","designation":"RFC 6613","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6613.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6613.txt","https://www.rfc-editor.org/rfc/rfc6613.pdf"],"folder":"IETF/RFC-6613","files":{"txt":{"path":"standards/IETF/RFC-6613/RFC-6613.txt","sha256":"54f373f18b220788c0afba6216e4139282717bdc14fc33f40befafd421437631"}},"tags":["nested-reference","unchanged"],"summary":"The Remote Authentication Dial-In User Server (RADIUS) protocol has,\n until now, required the User Datagram Protocol (UDP) as the\n underlying transport layer. This document defines RADIUS over the\n Transmission Control Protocol (RADIUS/TCP), in order to address\n handling issues related to RADIUS over Transport Layer Security\n (RADIUS/TLS). It permits TCP to be used as a transport protocol for\n RADIUS only when a transport layer such as TLS or IPsec provides\n confidentiality and security.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and h","scope_keywords":["6613","authentication","http","license","management","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6614","folder":"IETF/RFC-6614","source":"IETF/RFC-6614/RFC-6614.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null}],"search_text":"IETF RFC 6613 The Remote Authentication Dial-In User Server (RADIUS) protocol has,\n until now, required the User Datagram Protocol (UDP) as the\n underlying transport layer. This document defines RADIUS over the\n Transmission Control Protocol (RADIUS/TCP), in order to address\n handling issues related to RADIUS over Transport Layer Security\n (RADIUS/TLS). It permits TCP to be used as a transport protocol for\n RADIUS only when a transport layer such as TLS or IPsec provides\n confidentiality and security.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and h 6613 authentication http license management path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6614","type":"specification","body":"IETF","designation":"RFC 6614","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6614.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6614.txt","https://www.rfc-editor.org/rfc/rfc6614.pdf"],"folder":"IETF/RFC-6614","files":{"txt":{"path":"standards/IETF/RFC-6614/RFC-6614.txt","sha256":"ca8de65cc14a6b37779ad99218d8cf0bd304dc289377a5068613c72427c0e8f5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a transport profile for RADIUS using\n Transport Layer Security (TLS) over TCP as the transport protocol.\n This enables dynamic trust relationships between RADIUS servers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["6614","algorithm","authentication","authorization","certificate","encryption","http","issuer","key","license","profile","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6613","folder":"IETF/RFC-6613","source":"IETF/RFC-6613/RFC-6613.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6614 This document specifies a transport profile for RADIUS using\n Transport Layer Security (TLS) over TCP as the transport protocol.\n This enables dynamic trust relationships between RADIUS servers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 6614 algorithm authentication authorization certificate encryption http issuer key license profile risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6615","type":"specification","body":"IETF","designation":"RFC 6615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6615.txt","https://www.rfc-editor.org/rfc/rfc6615.pdf"],"folder":"IETF/RFC-6615","files":{"txt":{"path":"standards/IETF/RFC-6615/RFC-6615.txt","sha256":"2408a9824d1f23860c61013ad313c3489ca8105c606310cc181418aaaed42ad0"}},"tags":["nested-reference","unchanged"],"summary":"This document defines managed objects for IP Flow Information eXport\n (IPFIX). These objects provide information for monitoring IPFIX\n Exporters and IPFIX Collectors, including basic configuration\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6615.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n","scope_keywords":["6615","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6727","folder":"IETF/RFC-6727","source":"IETF/RFC-6727/RFC-6727.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null}],"search_text":"IETF RFC 6615 This document defines managed objects for IP Flow Information eXport\n (IPFIX). These objects provide information for monitoring IPFIX\n Exporters and IPFIX Collectors, including basic configuration\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6615.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n 6615 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6642","type":"specification","body":"IETF","designation":"RFC 6642","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6642.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6642.txt","https://www.rfc-editor.org/rfc/rfc6642.pdf"],"folder":"IETF/RFC-6642","files":{"txt":{"path":"standards/IETF/RFC-6642/RFC-6642.txt","sha256":"941302c7190d8484df750d1fbd99e446efe41dd481230f1765a5e5578edc26d5"}},"tags":["nested-reference","unchanged"],"summary":"In a large RTP session using the RTP Control Protocol (RTCP) feedback\n mechanism defined in RFC 4585, a feedback target may experience\n transient overload if some event causes a large number of receivers\n to send feedback at once. This overload is usually avoided by\n ensuring that feedback reports are forwarded to all receivers,\n allowing them to avoid sending duplicate feedback reports. However,\n there are cases where it is not recommended to forward feedback\n reports, and this may allow feedback implosion. This memo discusses\n these cases and defines a new RTCP Third-Party Loss Report that can\n be used to inform receivers that the feedback target is aware of some\n loss event, allowing them to suppress feedback. Associated Session\n Description Protocol (SDP) signaling is also defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of th","scope_keywords":["6642","http","key","license","pid","profile","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6642 In a large RTP session using the RTP Control Protocol (RTCP) feedback\n mechanism defined in RFC 4585, a feedback target may experience\n transient overload if some event causes a large number of receivers\n to send feedback at once. This overload is usually avoided by\n ensuring that feedback reports are forwarded to all receivers,\n allowing them to avoid sending duplicate feedback reports. However,\n there are cases where it is not recommended to forward feedback\n reports, and this may allow feedback implosion. This memo discusses\n these cases and defines a new RTCP Third-Party Loss Report that can\n be used to inform receivers that the feedback target is aware of some\n loss event, allowing them to suppress feedback. Associated Session\n Description Protocol (SDP) signaling is also defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of th 6642 http key license pid profile risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6644","type":"specification","body":"IETF","designation":"RFC 6644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6644.txt","https://www.rfc-editor.org/rfc/rfc6644.pdf"],"folder":"IETF/RFC-6644","files":{"txt":{"path":"standards/IETF/RFC-6644/RFC-6644.txt","sha256":"6f989600a1ee05108ad52b7edf8c80f965ca8f5919b1d282aab4ad0fd0984413"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3315 (DHCPv6) to allow the Rebind message\n type to appear in the Reconfigure Message option of a Reconfigure\n message. It extends the Reconfigure message to allow a DHCPv6 server\n to cause a DHCPv6 client to send a Rebind message. The document also\n clarifies how a DHCPv6 client responds to a received Reconfigure\n message.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or","scope_keywords":["6644","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null}],"search_text":"IETF RFC 6644 This document updates RFC 3315 (DHCPv6) to allow the Rebind message\n type to appear in the Reconfigure Message option of a Reconfigure\n message. It extends the Reconfigure message to allow a DHCPv6 server\n to cause a DHCPv6 client to send a Rebind message. The document also\n clarifies how a DHCPv6 client responds to a received Reconfigure\n message.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 5741.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n http://www.rfc-editor.or 6644 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6655","type":"specification","body":"IETF","designation":"RFC 6655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6655.txt","https://www.rfc-editor.org/rfc/rfc6655.pdf"],"folder":"IETF/RFC-6655","files":{"txt":{"path":"standards/IETF/RFC-6655/RFC-6655.txt","sha256":"d981a691a1bcc374ea5011b1f6b94f7ad0229e03e0845d153b7f498a5e40bd16"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n in the Counter with Cipher Block Chaining - Message Authentication\n Code (CBC-MAC) Mode (CCM) of operation within Transport Layer\n Security (TLS) and Datagram TLS (DTLS) to provide confidentiality and\n data origin authentication. The AES-CCM algorithm is amenable to\n compact implementations, making it suitable for constrained\n environments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi","scope_keywords":["6655","algorithm","algorithms","authentication","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7251","folder":"IETF/RFC-7251","source":"IETF/RFC-7251/RFC-7251.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 6655 This memo describes the use of the Advanced Encryption Standard (AES)\n in the Counter with Cipher Block Chaining - Message Authentication\n Code (CBC-MAC) Mode (CCM) of operation within Transport Layer\n Security (TLS) and Datagram TLS (DTLS) to provide confidentiality and\n data origin authentication. The AES-CCM algorithm is amenable to\n compact implementations, making it suitable for constrained\n environments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provi 6655 algorithm algorithms authentication encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6660","type":"specification","body":"IETF","designation":"RFC 6660","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6660.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6660.txt","https://www.rfc-editor.org/rfc/rfc6660.pdf"],"folder":"IETF/RFC-6660","files":{"txt":{"path":"standards/IETF/RFC-6660/RFC-6660.txt","sha256":"b312b8f0f6cd42ec1c3cefcc2a7d34eb6d12dd8c5f34177bff66e3657d36f0df"}},"tags":["nested-reference","unchanged"],"summary":"The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain.\n The overall rate of PCN-traffic is metered on every link in the PCN-\n domain, and PCN-packets are appropriately marked when certain\n configured rates are exceeded. Egress nodes pass information about\n these PCN-marks to Decision Points that then decide whether to admit\n or block new flow requests or to terminate some already admitted\n flows during serious pre-congestion.\n\n This document specifies how PCN-marks are to be encoded into the IP\n header by reusing the Explicit Congestion Notification (ECN)\n codepoints within a PCN-domain. The PCN wire protocol for non-IP\n protocol headers will need to be defined elsewhere. Nonetheless,\n this document clarifies the PCN encoding for MPLS in an informational\n appendix. The encoding for IP provides for up to ","scope_keywords":["6660","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 6660 The objective of Pre-Congestion Notification (PCN) is to protect the\n quality of service (QoS) of inelastic flows within a Diffserv domain.\n The overall rate of PCN-traffic is metered on every link in the PCN-\n domain, and PCN-packets are appropriately marked when certain\n configured rates are exceeded. Egress nodes pass information about\n these PCN-marks to Decision Points that then decide whether to admit\n or block new flow requests or to terminate some already admitted\n flows during serious pre-congestion.\n\n This document specifies how PCN-marks are to be encoded into the IP\n header by reusing the Explicit Congestion Notification (ECN)\n codepoints within a PCN-domain. The PCN wire protocol for non-IP\n protocol headers will need to be defined elsewhere. Nonetheless,\n this document clarifies the PCN encoding for MPLS in an informational\n appendix. The encoding for IP provides for up to  6660 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6661","type":"specification","body":"IETF","designation":"RFC 6661","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6661.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6661.txt","https://www.rfc-editor.org/rfc/rfc6661.pdf"],"folder":"IETF/RFC-6661","files":{"txt":{"path":"standards/IETF/RFC-6661/RFC-6661.txt","sha256":"b061f1d05b490fb2ab23afb4b9d0f79f388c55e06d0a771dd34e9812058d57ce"}},"tags":["nested-reference","unchanged"],"summary":"Pre-Congestion Notification (PCN) is a means for protecting the\n quality of service for inelastic traffic admitted to a Diffserv\n domain. The overall PCN architecture is described in RFC 5559. This\n memo is one of a series describing possible boundary-node behaviors\n for a PCN-domain. The behavior described here is that for a form of\n measurement-based load control using three PCN marking states: not-\n marked, threshold-marked, and excess-traffic-marked. This behavior\n is known informally as the Controlled Load (CL) PCN-boundary-node\n behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus o","scope_keywords":["6661","attribute","attributes","http","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null}],"search_text":"IETF RFC 6661 Pre-Congestion Notification (PCN) is a means for protecting the\n quality of service for inelastic traffic admitted to a Diffserv\n domain. The overall PCN architecture is described in RFC 5559. This\n memo is one of a series describing possible boundary-node behaviors\n for a PCN-domain. The behavior described here is that for a form of\n measurement-based load control using three PCN marking states: not-\n marked, threshold-marked, and excess-traffic-marked. This behavior\n is known informally as the Controlled Load (CL) PCN-boundary-node\n behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus o 6661 attribute attributes http license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6662","type":"specification","body":"IETF","designation":"RFC 6662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6662.txt","https://www.rfc-editor.org/rfc/rfc6662.pdf"],"folder":"IETF/RFC-6662","files":{"txt":{"path":"standards/IETF/RFC-6662/RFC-6662.txt","sha256":"a02267a8d7e4040c7f41a4034af70c3c73cc7bebd88edc281080bef09eb128d4"}},"tags":["nested-reference","unchanged"],"summary":"Pre-Congestion Notification (PCN) is a means for protecting the\n quality of service for inelastic traffic admitted to a Diffserv\n domain. The overall PCN architecture is described in RFC 5559. This\n memo is one of a series describing possible boundary-node behaviors\n for a PCN-domain. The behavior described here is that for a form of\n measurement-based load control using two PCN marking states: not-\n marked and excess-traffic-marked. This behavior is known informally\n as the Single Marking (SM) PCN-boundary-node behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. ","scope_keywords":["6662","attribute","attributes","http","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null}],"search_text":"IETF RFC 6662 Pre-Congestion Notification (PCN) is a means for protecting the\n quality of service for inelastic traffic admitted to a Diffserv\n domain. The overall PCN architecture is described in RFC 5559. This\n memo is one of a series describing possible boundary-node behaviors\n for a PCN-domain. The behavior described here is that for a form of\n measurement-based load control using two PCN marking states: not-\n marked and excess-traffic-marked. This behavior is known informally\n as the Single Marking (SM) PCN-boundary-node behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community.  6662 attribute attributes http license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6665","type":"specification","body":"IETF","designation":"RFC 6665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6665.txt","https://www.rfc-editor.org/rfc/rfc6665.pdf"],"folder":"IETF/RFC-6665","files":{"txt":{"path":"standards/IETF/RFC-6665/RFC-6665.txt","sha256":"10699236a3ff2cc3b2a0400b0e41c83b22e725d11e4d9cabd0fd1801566672fa"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to the Session Initiation\n Protocol (SIP) defined by RFC 3261. The purpose of this extension is\n to provide an extensible framework by which SIP nodes can request\n notification from remote nodes indicating that certain events have\n occurred.\n\n Note that the event notification mechanisms defined herein are NOT\n intended to be a general-purpose infrastructure for all classes of\n event subscription and notification.\n\n This document represents a backwards-compatible improvement on the\n original mechanism described by RFC 3265, taking into account several\n years of implementation experience. Accordingly, this document\n obsoletes RFC 3265. This document also updates RFC 4660 slightly to\n accommodate some small changes to the mechanism that were discussed\n in that document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document ","scope_keywords":["6665","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 6665 This document describes an extension to the Session Initiation\n Protocol (SIP) defined by RFC 3261. The purpose of this extension is\n to provide an extensible framework by which SIP nodes can request\n notification from remote nodes indicating that certain events have\n occurred.\n\n Note that the event notification mechanisms defined herein are NOT\n intended to be a general-purpose infrastructure for all classes of\n event subscription and notification.\n\n This document represents a backwards-compatible improvement on the\n original mechanism described by RFC 3265, taking into account several\n years of implementation experience. Accordingly, this document\n obsoletes RFC 3265. This document also updates RFC 4660 slightly to\n accommodate some small changes to the mechanism that were discussed\n in that document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document  6665 http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 6705","type":"specification","body":"IETF","designation":"RFC 6705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6705.txt","https://www.rfc-editor.org/rfc/rfc6705.pdf"],"folder":"IETF/RFC-6705","files":{"txt":{"path":"standards/IETF/RFC-6705/RFC-6705.txt","sha256":"a5b7b8295209e7c0ab233828bc75e703cddee8bee590cc15b5df6ab44a63b80c"}},"tags":["nested-reference","unchanged"],"summary":"Proxy Mobile IPv6 (PMIPv6) is a network based mobility management\n protocol that enables IP mobility for a host without requiring its\n participation in any mobility-related signaling. PMIPv6 requires all\n communications to go through the local mobility anchor. As this can\n be suboptimal, Localized Routing (LR) allows Mobile Nodes (MNs)\n attached to the same or different Mobile Access Gateways (MAGs) to\n route traffic by using localized forwarding or a direct tunnel\n between the gateways. This document proposes initiation,\n utilization, and termination mechanisms for localized routing between\n mobile access gateways within a proxy mobile IPv6 domain. It defines\n two new signaling messages, Localized Routing Initiation (LRI) and\n Local Routing Acknowledgment (LRA), that are used to realize this\n mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document","scope_keywords":["6705","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7156","folder":"IETF/RFC-7156","source":"IETF/RFC-7156/RFC-7156.txt","version":null}],"search_text":"IETF RFC 6705 Proxy Mobile IPv6 (PMIPv6) is a network based mobility management\n protocol that enables IP mobility for a host without requiring its\n participation in any mobility-related signaling. PMIPv6 requires all\n communications to go through the local mobility anchor. As this can\n be suboptimal, Localized Routing (LR) allows Mobile Nodes (MNs)\n attached to the same or different Mobile Access Gateways (MAGs) to\n route traffic by using localized forwarding or a direct tunnel\n between the gateways. This document proposes initiation,\n utilization, and termination mechanisms for localized routing between\n mobile access gateways within a proxy mobile IPv6 domain. It defines\n two new signaling messages, Localized Routing Initiation (LRI) and\n Local Routing Acknowledgment (LRA), that are used to realize this\n mechanism.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document 6705 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6708","type":"specification","body":"IETF","designation":"RFC 6708","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6708.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6708.txt","https://www.rfc-editor.org/rfc/rfc6708.pdf"],"folder":"IETF/RFC-6708","files":{"txt":{"path":"standards/IETF/RFC-6708/RFC-6708.txt","sha256":"36d0257529a72a4237183ade81f08ca3462dd82aac6229a0bc69669af209201c"}},"tags":["nested-reference","unchanged"],"summary":"Many Internet applications are used to access resources, such as\n pieces of information or server processes that are available in\n several equivalent replicas on different hosts. This includes, but\n is not limited to, peer-to-peer file sharing applications. The goal\n of Application-Layer Traffic Optimization (ALTO) is to provide\n guidance to applications that have to select one or several hosts\n from a set of candidates capable of providing a desired resource.\n This guidance shall be based on parameters that affect performance\n and efficiency of the data transmission between the hosts, e.g., the\n topological distance. The ultimate goal is to improve performance or\n Quality of Experience in the application while reducing the\n utilization of the underlying network infrastructure.\n\n This document enumerates requirements for specifying, assessing, or\n comparing protocols and implementations.","scope_keywords":["6708","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null}],"search_text":"IETF RFC 6708 Many Internet applications are used to access resources, such as\n pieces of information or server processes that are available in\n several equivalent replicas on different hosts. This includes, but\n is not limited to, peer-to-peer file sharing applications. The goal\n of Application-Layer Traffic Optimization (ALTO) is to provide\n guidance to applications that have to select one or several hosts\n from a set of candidates capable of providing a desired resource.\n This guidance shall be based on parameters that affect performance\n and efficiency of the data transmission between the hosts, e.g., the\n topological distance. The ultimate goal is to improve performance or\n Quality of Experience in the application while reducing the\n utilization of the underlying network infrastructure.\n\n This document enumerates requirements for specifying, assessing, or\n comparing protocols and implementations. 6708 http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6714","type":"specification","body":"IETF","designation":"RFC 6714","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6714.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6714.txt","https://www.rfc-editor.org/rfc/rfc6714.pdf"],"folder":"IETF/RFC-6714","files":{"txt":{"path":"standards/IETF/RFC-6714/RFC-6714.txt","sha256":"784f7833221f15401953686e328c9a4b040d69a6cdb2be29ce47287b4d9a3b6f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Message Session Relay Protocol (MSRP)\n extension, Connection Establishment for Media Anchoring (CEMA).\n Support of this extension is OPTIONAL. The extension allows\n middleboxes to anchor the MSRP connection, without the need for\n middleboxes to modify the MSRP messages; thus, it also enables secure\n end-to-end MSRP communication in networks where such middleboxes are\n deployed. This document also defines a Session Description Protocol\n (SDP) attribute, 'msrp-cema', that MSRP endpoints use to indicate\n support of the CEMA extension.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information ","scope_keywords":["6714","attribute","authentication","credential","credentials","http","key","license","management","path","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 6714 This document defines a Message Session Relay Protocol (MSRP)\n extension, Connection Establishment for Media Anchoring (CEMA).\n Support of this extension is OPTIONAL. The extension allows\n middleboxes to anchor the MSRP connection, without the need for\n middleboxes to modify the MSRP messages; thus, it also enables secure\n end-to-end MSRP communication in networks where such middleboxes are\n deployed. This document also defines a Session Description Protocol\n (SDP) attribute, 'msrp-cema', that MSRP endpoints use to indicate\n support of the CEMA extension.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information  6714 attribute authentication credential credentials http key license management path policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6716","type":"specification","body":"IETF","designation":"RFC 6716","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6716.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6716.txt","https://www.rfc-editor.org/rfc/rfc6716.pdf"],"folder":"IETF/RFC-6716","files":{"txt":{"path":"standards/IETF/RFC-6716/RFC-6716.txt","sha256":"41caac5240a4a22661efd0031d5b7aee48f3c0bde3b2cdcee8165932e485f98c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Opus interactive speech and audio codec.\n Opus is designed to handle a wide range of interactive audio\n applications, including Voice over IP, videoconferencing, in-game\n chat, and even live, distributed music performances. It scales from\n low bitrate narrowband speech at 6 kbit/s to very high quality stereo\n music at 510 kbit/s. Opus uses both Linear Prediction (LP) and the\n Modified Discrete Cosine Transform (MDCT) to achieve good compression\n of both speech and music.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741","scope_keywords":["6716","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null},{"body":"IETF","designation":"RFC 7587","folder":"IETF/RFC-7587","source":"IETF/RFC-7587/RFC-7587.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 6716 This document defines the Opus interactive speech and audio codec.\n Opus is designed to handle a wide range of interactive audio\n applications, including Voice over IP, videoconferencing, in-game\n chat, and even live, distributed music performances. It scales from\n low bitrate narrowband speech at 6 kbit/s to very high quality stereo\n music at 510 kbit/s. Opus uses both Linear Prediction (LP) and the\n Modified Discrete Cosine Transform (MDCT) to achieve good compression\n of both speech and music.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741 6716 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6731","type":"specification","body":"IETF","designation":"RFC 6731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6731.txt","https://www.rfc-editor.org/rfc/rfc6731.pdf"],"folder":"IETF/RFC-6731","files":{"txt":{"path":"standards/IETF/RFC-6731/RFC-6731.txt","sha256":"9b1800c17b68b1ac6fe26c3d03acc519aebcfd1098abce00c8718e47372f8b5d"}},"tags":["nested-reference","unchanged"],"summary":"A multi-interfaced node is connected to multiple networks, some of\n which might be utilizing private DNS namespaces. A node commonly\n receives recursive DNS server configuration information from all\n connected networks. Some of the recursive DNS servers might have\n information about namespaces other servers do not have. When a\n multi-interfaced node needs to utilize DNS, the node has to choose\n which of the recursive DNS servers to use. This document describes\n DHCPv4 and DHCPv6 options that can be used to configure nodes with\n information required to perform informed recursive DNS server\n selection decisions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet","scope_keywords":["6731","algorithm","http","license","policies","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 6731 A multi-interfaced node is connected to multiple networks, some of\n which might be utilizing private DNS namespaces. A node commonly\n receives recursive DNS server configuration information from all\n connected networks. Some of the recursive DNS servers might have\n information about namespaces other servers do not have. When a\n multi-interfaced node needs to utilize DNS, the node has to choose\n which of the recursive DNS servers to use. This document describes\n DHCPv4 and DHCPv6 options that can be used to configure nodes with\n information required to perform informed recursive DNS server\n selection decisions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet 6731 algorithm http license policies qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 6737","type":"specification","body":"IETF","designation":"RFC 6737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6737.txt","https://www.rfc-editor.org/rfc/rfc6737.pdf"],"folder":"IETF/RFC-6737","files":{"txt":{"path":"standards/IETF/RFC-6737/RFC-6737.txt","sha256":"0661abd2bf19f20e8882fbe85cc5680c71a833ba78a12b8aa7a8ff003ac6e8ef"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Diameter application and associated\n Command Codes. The Capabilities Update application is intended to\n allow the dynamic update of certain Diameter peer capabilities while\n the peer-to-peer connection is in the open state.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6737.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n","scope_keywords":["6737","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null}],"search_text":"IETF RFC 6737 This document defines a new Diameter application and associated\n Command Codes. The Capabilities Update application is intended to\n allow the dynamic update of certain Diameter peer capabilities while\n the peer-to-peer connection is in the open state.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6737.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n 6737 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6739","type":"specification","body":"IETF","designation":"RFC 6739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6739.txt","https://www.rfc-editor.org/rfc/rfc6739.pdf"],"folder":"IETF/RFC-6739","files":{"txt":{"path":"standards/IETF/RFC-6739/RFC-6739.txt","sha256":"44b473782102006fb9181549148c913c8a56ba340b47fe0786b03ad91c13fc10"}},"tags":["nested-reference","unchanged"],"summary":"The Location-to-Service Translation (LoST) protocol is an XML-based\n protocol for mapping service identifiers and geodetic or civic\n location information to service URIs and service boundaries. In\n particular, it can be used to determine the location-appropriate\n Public Safety Answering Point (PSAP) for emergency services.\n\n The <mapping> element in the LoST protocol specification encapsulates\n information about service boundaries and circumscribes the region\n within which all locations map to the same service Uniform Resource\n Identifier (URI) or set of URIs for a given service.\n\n This document defines an XML protocol to exchange these mappings\n between two nodes. This mechanism is designed for the exchange of\n authoritative <mapping> elements between two entities. Exchanging\n cached <mapping> elements, i.e., non-authoritative elements, is\n possible but not envisioned. Even though the <","scope_keywords":["6739","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 6739 The Location-to-Service Translation (LoST) protocol is an XML-based\n protocol for mapping service identifiers and geodetic or civic\n location information to service URIs and service boundaries. In\n particular, it can be used to determine the location-appropriate\n Public Safety Answering Point (PSAP) for emergency services.\n\n The <mapping> element in the LoST protocol specification encapsulates\n information about service boundaries and circumscribes the region\n within which all locations map to the same service Uniform Resource\n Identifier (URI) or set of URIs for a given service.\n\n This document defines an XML protocol to exchange these mappings\n between two nodes. This mechanism is designed for the exchange of\n authoritative <mapping> elements between two entities. Exchanging\n cached <mapping> elements, i.e., non-authoritative elements, is\n possible but not envisioned. Even though the < 6739 http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6743","type":"specification","body":"IETF","designation":"RFC 6743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6743.txt","https://www.rfc-editor.org/rfc/rfc6743.pdf"],"folder":"IETF/RFC-6743","files":{"txt":{"path":"standards/IETF/RFC-6743/RFC-6743.txt","sha256":"71922e247dc9326274cae79e19e5438fbb406e03487d01f261a21a4c624dd6b1"}},"tags":["nested-reference","unchanged"],"summary":"This note specifies an experimental ICMPv6 message type used with the\n Identifier-Locator Network Protocol (ILNP). The Identifier-Locator\n Network Protocol (ILNP) is an experimental, evolutionary enhancement\n to IP. This message is used to dynamically update Identifier/Locator\n bindings for an existing ILNP session. This is a product of the IRTF\n Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more member","scope_keywords":["6743","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6743 This note specifies an experimental ICMPv6 message type used with the\n Identifier-Locator Network Protocol (ILNP). The Identifier-Locator\n Network Protocol (ILNP) is an experimental, evolutionary enhancement\n to IP. This message is used to dynamically update Identifier/Locator\n bindings for an existing ILNP session. This is a product of the IRTF\n Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more member 6743 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6744","type":"specification","body":"IETF","designation":"RFC 6744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6744.txt","https://www.rfc-editor.org/rfc/rfc6744.pdf"],"folder":"IETF/RFC-6744","files":{"txt":{"path":"standards/IETF/RFC-6744/RFC-6744.txt","sha256":"fea254b815247f323e396b4f55b5e234ce9fb10806972f3dd817dca24e640699"}},"tags":["nested-reference","unchanged"],"summary":"The Identifier-Locator Network Protocol (ILNP) is an experimental,\n evolutionary enhancement to IP. ILNP has multiple instantiations.\n This document describes an experimental Nonce Destination Option used\n only with ILNP for IPv6 (ILNPv6). This document is a product of the\n IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force ","scope_keywords":["6744","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6744 The Identifier-Locator Network Protocol (ILNP) is an experimental,\n evolutionary enhancement to IP. ILNP has multiple instantiations.\n This document describes an experimental Nonce Destination Option used\n only with ILNP for IPv6 (ILNPv6). This document is a product of the\n IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force  6744 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6745","type":"specification","body":"IETF","designation":"RFC 6745","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6745.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6745.txt","https://www.rfc-editor.org/rfc/rfc6745.pdf"],"folder":"IETF/RFC-6745","files":{"txt":{"path":"standards/IETF/RFC-6745/RFC-6745.txt","sha256":"942a24cb956b964448e44e71c32e5082fdc592dbfcaf7c84e8b7296e7da74c2d"}},"tags":["nested-reference","unchanged"],"summary":"This note defines an experimental ICMP message type for IPv4 used\n with the Identifier-Locator Network Protocol (ILNP). ILNP is an\n experimental, evolutionary enhancement to IP. The ICMP message\n defined herein is used to dynamically update Identifier/Locator\n bindings for an existing ILNP session. This is a product of the IRTF\n Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing R","scope_keywords":["6745","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6745 This note defines an experimental ICMP message type for IPv4 used\n with the Identifier-Locator Network Protocol (ILNP). ILNP is an\n experimental, evolutionary enhancement to IP. The ICMP message\n defined herein is used to dynamically update Identifier/Locator\n bindings for an existing ILNP session. This is a product of the IRTF\n Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing R 6745 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6746","type":"specification","body":"IETF","designation":"RFC 6746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6746.txt","https://www.rfc-editor.org/rfc/rfc6746.pdf"],"folder":"IETF/RFC-6746","files":{"txt":{"path":"standards/IETF/RFC-6746/RFC-6746.txt","sha256":"2b6799213a96faa9e6f32bad69b20503220b048bbc40cdd01c157145a34d45ce"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new IPv4 Options that are used only with\n the Identifier-Locator Network Protocol for IPv4 (ILNPv4). ILNP is\n an experimental, evolutionary enhancement to IP. This document is a\n product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by the IRSG","scope_keywords":["6746","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6746 This document defines two new IPv4 Options that are used only with\n the Identifier-Locator Network Protocol for IPv4 (ILNPv4). ILNP is\n an experimental, evolutionary enhancement to IP. This document is a\n product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publication by the IRSG 6746 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6747","type":"specification","body":"IETF","designation":"RFC 6747","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6747.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6747.txt","https://www.rfc-editor.org/rfc/rfc6747.pdf"],"folder":"IETF/RFC-6747","files":{"txt":{"path":"standards/IETF/RFC-6747/RFC-6747.txt","sha256":"f708e8a761cfd770940106a497879bf0e0400c35b1652fdf38cec637fd8b118c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Address Resolution Protocol (ARP) extension\n to support the Identifier-Locator Network Protocol for IPv4 (ILNPv4).\n ILNP is an experimental, evolutionary enhancement to IP. This\n document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publicatio","scope_keywords":["6747","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6742","folder":"IETF/RFC-6742","source":"IETF/RFC-6742/RFC-6742.txt","version":null},{"body":"IETF","designation":"RFC 6743","folder":"IETF/RFC-6743","source":"IETF/RFC-6743/RFC-6743.txt","version":null},{"body":"IETF","designation":"RFC 6744","folder":"IETF/RFC-6744","source":"IETF/RFC-6744/RFC-6744.txt","version":null},{"body":"IETF","designation":"RFC 6745","folder":"IETF/RFC-6745","source":"IETF/RFC-6745/RFC-6745.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null}],"search_text":"IETF RFC 6747 This document defines an Address Resolution Protocol (ARP) extension\n to support the Identifier-Locator Network Protocol for IPv4 (ILNPv4).\n ILNP is an experimental, evolutionary enhancement to IP. This\n document is a product of the IRTF Routing Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Research Task\n Force (IRTF). The IRTF publishes the results of Internet-related\n research and development activities. These results might not be\n suitable for deployment. This RFC represents the individual\n opinion(s) of one or more members of the Routing Research Group of\n the Internet Research Task Force (IRTF). Documents approved for\n publicatio 6747 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6749","type":"specification","body":"IETF","designation":"RFC 6749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6749.txt","https://www.rfc-editor.org/rfc/rfc6749.pdf"],"folder":"IETF/RFC-6749","files":{"txt":{"path":"standards/IETF/RFC-6749/RFC-6749.txt","sha256":"f204fc8661d6c92d2ec6e0b54808f961a9ad26e792f57f312d9528335519bd71"}},"tags":["nested-reference","unchanged"],"summary":"The OAuth 2.0 authorization framework enables a third-party\n application to obtain limited access to an HTTP service, either on\n behalf of a resource owner by orchestrating an approval interaction\n between the resource owner and the HTTP service, or by allowing the\n third-party application to obtain access on its own behalf. This\n specification replaces and obsoletes the OAuth 1.0 protocol described\n in RFC 5849.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pr","scope_keywords":["6749","authentication","authorization","credential","credentials","http","license","registered","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 7009","folder":"IETF/RFC-7009","source":"IETF/RFC-7009/RFC-7009.txt","version":null},{"body":"IETF","designation":"RFC 7397","folder":"IETF/RFC-7397","source":"IETF/RFC-7397/RFC-7397.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 6749 The OAuth 2.0 authorization framework enables a third-party\n application to obtain limited access to an HTTP service, either on\n behalf of a resource owner by orchestrating an approval interaction\n between the resource owner and the HTTP service, or by allowing the\n third-party application to obtain access on its own behalf. This\n specification replaces and obsoletes the OAuth 1.0 protocol described\n in RFC 5849.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to pr 6749 authentication authorization credential credentials http license registered subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 6750","type":"specification","body":"IETF","designation":"RFC 6750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6750.txt","https://www.rfc-editor.org/rfc/rfc6750.pdf"],"folder":"IETF/RFC-6750","files":{"txt":{"path":"standards/IETF/RFC-6750/RFC-6750.txt","sha256":"9dc385cf4ecdd85024e5a95e447ede9230e11700bf35251906b25b37557d604b"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes how to use bearer tokens in HTTP\n requests to access OAuth 2.0 protected resources. Any party in\n possession of a bearer token (a \"bearer\") can use it to get access to\n the associated resources (without demonstrating possession of a\n cryptographic key). To prevent misuse, bearer tokens need to be\n protected from disclosure in storage and in transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain","scope_keywords":["6750","attribute","attributes","authentication","authorization","credential","credentials","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6819","folder":"IETF/RFC-6819","source":"IETF/RFC-6819/RFC-6819.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 6750 This specification describes how to use bearer tokens in HTTP\n requests to access OAuth 2.0 protected resources. Any party in\n possession of a bearer token (a \"bearer\") can use it to get access to\n the associated resources (without demonstrating possession of a\n cryptographic key). To prevent misuse, bearer tokens need to be\n protected from disclosure in storage and in transport.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain 6750 attribute attributes authentication authorization credential credentials http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6764","type":"specification","body":"IETF","designation":"RFC 6764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6764.txt","https://www.rfc-editor.org/rfc/rfc6764.pdf"],"folder":"IETF/RFC-6764","files":{"txt":{"path":"standards/IETF/RFC-6764/RFC-6764.txt","sha256":"f9ad57d7a9c734ac833da6ef97e3e001cb98a612602cac561fbf3d1c592f104f"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes how DNS SRV records, DNS TXT records,\n and well-known URIs can be used together or separately to locate\n CalDAV (Calendaring Extensions to Web Distributed Authoring and\n Versioning (WebDAV)) or CardDAV (vCard Extensions to WebDAV)\n services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6764.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons","scope_keywords":["6764","http","key","license","path","qualified","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 6764 This specification describes how DNS SRV records, DNS TXT records,\n and well-known URIs can be used together or separately to locate\n CalDAV (Calendaring Extensions to Web Distributed Authoring and\n Versioning (WebDAV)) or CardDAV (vCard Extensions to WebDAV)\n services.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6764.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons 6764 http key license path qualified subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6772","type":"specification","body":"IETF","designation":"RFC 6772","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6772.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6772.txt","https://www.rfc-editor.org/rfc/rfc6772.pdf"],"folder":"IETF/RFC-6772","files":{"txt":{"path":"standards/IETF/RFC-6772/RFC-6772.txt","sha256":"d035824ec309552083fb6a29b68850acb1e74d46d749f40bd7a8d1072bb469c8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an authorization policy language for\n controlling access to location information. It extends the Common\n Policy authorization framework to provide location-specific access\n control. More specifically, this document defines condition elements\n specific to location information in order to restrict access to data\n based on the current location of the Target.\n\n Furthermore, this document defines two algorithms for reducing the\n granularity of returned location information. The first algorithm is\n defined for usage with civic location information, whereas the other\n one applies to geodetic location information. Both algorithms come\n with limitations. There are circumstances where the amount of\n location obfuscation provided is less than what is desired. These\n algorithms might not be appropriate for all application domains.\n\nStatus of This Memo\n\n This is an Internet Stan","scope_keywords":["6772","algorithm","algorithms","authorization","http","license","policies","policy","profile","profiles","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 6772 This document defines an authorization policy language for\n controlling access to location information. It extends the Common\n Policy authorization framework to provide location-specific access\n control. More specifically, this document defines condition elements\n specific to location information in order to restrict access to data\n based on the current location of the Target.\n\n Furthermore, this document defines two algorithms for reducing the\n granularity of returned location information. The first algorithm is\n defined for usage with civic location information, whereas the other\n one applies to geodetic location information. Both algorithms come\n with limitations. There are circumstances where the amount of\n location obfuscation provided is less than what is desired. These\n algorithms might not be appropriate for all application domains.\n\nStatus of This Memo\n\n This is an Internet Stan 6772 algorithm algorithms authorization http license policies policy profile profiles subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6776","type":"specification","body":"IETF","designation":"RFC 6776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6776.txt","https://www.rfc-editor.org/rfc/rfc6776.pdf"],"folder":"IETF/RFC-6776","files":{"txt":{"path":"standards/IETF/RFC-6776/RFC-6776.txt","sha256":"3c1e14b273408ebc238e6dd5e66d1b15546fc0689e223309a01b855c392dd331"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Source\n Description (SDES) item and an RTCP Extended Report (XR) block\n carrying parameters that identify and describe a measurement period\n to which one or more other RTCP XR blocks may refer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6776.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n docu","scope_keywords":["6776","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6843","folder":"IETF/RFC-6843","source":"IETF/RFC-6843/RFC-6843.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"IETF RFC 6776 This document defines an RTP Control Protocol (RTCP) Source\n Description (SDES) item and an RTCP Extended Report (XR) block\n carrying parameters that identify and describe a measurement period\n to which one or more other RTCP XR blocks may refer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6776.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n docu 6776 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6785","type":"specification","body":"IETF","designation":"RFC 6785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6785.txt","https://www.rfc-editor.org/rfc/rfc6785.pdf"],"folder":"IETF/RFC-6785","files":{"txt":{"path":"standards/IETF/RFC-6785/RFC-6785.txt","sha256":"b72aadd08894ad52d5b964bfb4fb0b9f8b551f318cff15fa0237722e2fb338a6"}},"tags":["nested-reference","unchanged"],"summary":"Sieve defines an email filtering language that can, in principle,\n plug into any point in the processing of an email message. As\n defined in the base specification, it plugs into mail delivery. This\n document defines how Sieve can plug into points in IMAP where\n messages are created or changed, adding the option of user-defined or\n installation-defined filtering (or, with Sieve extensions, features\n such as notifications). Because this requires future Sieve\n extensions to specify their interactions with this one, this document\n updates the base Sieve specification, RFC 5228.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). ","scope_keywords":["6785","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null}],"search_text":"IETF RFC 6785 Sieve defines an email filtering language that can, in principle,\n plug into any point in the processing of an email message. As\n defined in the base specification, it plugs into mail delivery. This\n document defines how Sieve can plug into points in IMAP where\n messages are created or changed, adding the option of user-defined or\n installation-defined filtering (or, with Sieve extensions, features\n such as notifications). Because this requires future Sieve\n extensions to specify their interactions with this one, this document\n updates the base Sieve specification, RFC 5228.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG).  6785 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6790","type":"specification","body":"IETF","designation":"RFC 6790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6790.txt","https://www.rfc-editor.org/rfc/rfc6790.pdf"],"folder":"IETF/RFC-6790","files":{"txt":{"path":"standards/IETF/RFC-6790/RFC-6790.txt","sha256":"eb3c5ba1dc1cfbcf40b83a662a9a83e8aea37f7003b89e5efe2362da0d9cd1c5"}},"tags":["nested-reference","unchanged"],"summary":"Load balancing is a powerful tool for engineering traffic across a\n network. This memo suggests ways of improving load balancing across\n MPLS networks using the concept of \"entropy labels\". It defines the\n concept, describes why entropy labels are useful, enumerates\n properties of entropy labels that allow maximal benefit, and shows\n how they can be signaled and used for various applications. This\n document updates RFCs 3031, 3107, 3209, and 5036.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this d","scope_keywords":["6790","attribute","hash","http","key","keys","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 6790 Load balancing is a powerful tool for engineering traffic across a\n network. This memo suggests ways of improving load balancing across\n MPLS networks using the concept of \"entropy labels\". It defines the\n concept, describes why entropy labels are useful, enumerates\n properties of entropy labels that allow maximal benefit, and shows\n how they can be signaled and used for various applications. This\n document updates RFCs 3031, 3107, 3209, and 5036.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this d 6790 attribute hash http key keys license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6798","type":"specification","body":"IETF","designation":"RFC 6798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6798.txt","https://www.rfc-editor.org/rfc/rfc6798.pdf"],"folder":"IETF/RFC-6798","files":{"txt":{"path":"standards/IETF/RFC-6798/RFC-6798.txt","sha256":"c152001f93268fd9bfcbae2692b12bcf689d12e9419f69e5e033da58b6afdd8d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of packet delay variation\n metrics for a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6798.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 ","scope_keywords":["6798","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6792","folder":"IETF/RFC-6792","source":"IETF/RFC-6792/RFC-6792.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 6798 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of packet delay variation\n metrics for a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6798.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78  6798 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6807","type":"specification","body":"IETF","designation":"RFC 6807","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6807.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6807.txt","https://www.rfc-editor.org/rfc/rfc6807.pdf"],"folder":"IETF/RFC-6807","files":{"txt":{"path":"standards/IETF/RFC-6807/RFC-6807.txt","sha256":"c4c47955ee7407a5ef6f04bcd8b2d3eb3f86f23c6db2c6337ac804827fbbf37a"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a method for providing multicast\n distribution-tree accounting data. Simple extensions to the Protocol\n Independent Multicast (PIM) protocol allow a rough approximation of\n tree-based data in a scalable fashion.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this do","scope_keywords":["6807","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 6807 This specification defines a method for providing multicast\n distribution-tree accounting data. Simple extensions to the Protocol\n Independent Multicast (PIM) protocol allow a rough approximation of\n tree-based data in a scalable fashion.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this do 6807 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6811","type":"specification","body":"IETF","designation":"RFC 6811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6811.txt","https://www.rfc-editor.org/rfc/rfc6811.pdf"],"folder":"IETF/RFC-6811","files":{"txt":{"path":"standards/IETF/RFC-6811/RFC-6811.txt","sha256":"05d3b68f6750fd1c6090a9132212a31bad711e513765c47ce6f8fe10fd1e68e5"}},"tags":["nested-reference","unchanged"],"summary":"To help reduce well-known threats against BGP including prefix mis-\n announcing and monkey-in-the-middle attacks, one of the security\n requirements is the ability to validate the origination Autonomous\n System (AS) of BGP routes. More specifically, one needs to validate\n that the AS number claiming to originate an address prefix (as\n derived from the AS_PATH attribute of the BGP route) is in fact\n authorized by the prefix holder to do so. This document describes a\n simple validation mechanism to partially satisfy this requirement.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is","scope_keywords":["6811","attestation","attribute","authorization","certificate","certificates","holder","http","key","license","path","pki","policy","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null}],"search_text":"IETF RFC 6811 To help reduce well-known threats against BGP including prefix mis-\n announcing and monkey-in-the-middle attacks, one of the security\n requirements is the ability to validate the origination Autonomous\n System (AS) of BGP routes. More specifically, one needs to validate\n that the AS number claiming to originate an address prefix (as\n derived from the AS_PATH attribute of the BGP route) is in fact\n authorized by the prefix holder to do so. This document describes a\n simple validation mechanism to partially satisfy this requirement.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is 6811 attestation attribute authorization certificate certificates holder http key license path pki policy signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 6817","type":"specification","body":"IETF","designation":"RFC 6817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6817.txt","https://www.rfc-editor.org/rfc/rfc6817.pdf"],"folder":"IETF/RFC-6817","files":{"txt":{"path":"standards/IETF/RFC-6817/RFC-6817.txt","sha256":"6092aa1a98afa59d8379377872c4253d7fc5c08825029d7cf6e2af1f44580d87"}},"tags":["nested-reference","unchanged"],"summary":"Low Extra Delay Background Transport (LEDBAT) is an experimental\n delay-based congestion control algorithm that seeks to utilize the\n available bandwidth on an end-to-end path while limiting the\n consequent increase in queueing delay on that path. LEDBAT uses\n changes in one-way delay measurements to limit congestion that the\n flow itself induces in the network. LEDBAT is designed for use by\n background bulk-transfer applications to be no more aggressive than\n standard TCP congestion control (as specified in RFC 5681) and to\n yield in the presence of competing flows, thus limiting interference\n with the network performance of competing flows.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This","scope_keywords":["6817","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null}],"search_text":"IETF RFC 6817 Low Extra Delay Background Transport (LEDBAT) is an experimental\n delay-based congestion control algorithm that seeks to utilize the\n available bandwidth on an end-to-end path while limiting the\n consequent increase in queueing delay on that path. LEDBAT uses\n changes in one-way delay measurements to limit congestion that the\n flow itself induces in the network. LEDBAT is designed for use by\n background bulk-transfer applications to be no more aggressive than\n standard TCP congestion control (as specified in RFC 5681) and to\n yield in the presence of competing flows, thus limiting interference\n with the network performance of competing flows.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This 6817 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6818","type":"specification","body":"IETF","designation":"RFC 6818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6818.txt","https://www.rfc-editor.org/rfc/rfc6818.pdf"],"folder":"IETF/RFC-6818","files":{"txt":{"path":"standards/IETF/RFC-6818/RFC-6818.txt","sha256":"e6bb52bd92138bb36cfd01202f22153d98318c6f7e3e5b15171374aec67a829f"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 5280, the \"Internet X.509 Public Key\n Infrastructure Certificate and Certificate Revocation List (CRL)\n Profile\". This document changes the set of acceptable encoding\n methods for the explicitText field of the user notice policy\n qualifier and clarifies the rules for converting internationalized\n domain name labels to ASCII. This document also provides some\n clarifications on the use of self-signed certificates, trust anchors,\n and some updated security considerations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n","scope_keywords":["6818","algorithm","certificate","certificates","crl","hash","http","key","license","path","policies","policy","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null}],"search_text":"IETF RFC 6818 This document updates RFC 5280, the \"Internet X.509 Public Key\n Infrastructure Certificate and Certificate Revocation List (CRL)\n Profile\". This document changes the set of acceptable encoding\n methods for the explicitText field of the user notice policy\n qualifier and clarifies the rules for converting internationalized\n domain name labels to ASCII. This document also provides some\n clarifications on the use of self-signed certificates, trust anchors,\n and some updated security considerations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n 6818 algorithm certificate certificates crl hash http key license path policies policy profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6823","type":"specification","body":"IETF","designation":"RFC 6823","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6823.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6823.txt","https://www.rfc-editor.org/rfc/rfc6823.pdf"],"folder":"IETF/RFC-6823","files":{"txt":{"path":"standards/IETF/RFC-6823/RFC-6823.txt","sha256":"9ac8452bad23935347cfb146da0bd0623d2ea6f6d33b1508aba4e5d604d30a7a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the manner in which generic application\n information (i.e., information not directly related to the operation\n of the Intermediate System to Intermediate System (IS-IS) protocol)\n should be advertised in IS-IS Link State Protocol Data Units (LSPs)\n and defines guidelines that should be used when flooding such\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i","scope_keywords":["6823","attribute","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null}],"search_text":"IETF RFC 6823 This document describes the manner in which generic application\n information (i.e., information not directly related to the operation\n of the Intermediate System to Intermediate System (IS-IS) protocol)\n should be advertised in IS-IS Link State Protocol Data Units (LSPs)\n and defines guidelines that should be used when flooding such\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/i 6823 attribute http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6831","type":"specification","body":"IETF","designation":"RFC 6831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6831.txt","https://www.rfc-editor.org/rfc/rfc6831.pdf"],"folder":"IETF/RFC-6831","files":{"txt":{"path":"standards/IETF/RFC-6831/RFC-6831.txt","sha256":"a70da8b373dd35346d725bbb645e448993cdacdb3acf9f58efa0197ccc539fbe"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how inter-domain multicast routing will\n function in an environment where Locator/ID Separation is deployed\n using the Locator/ID Separation Protocol (LISP) architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed","scope_keywords":["6831","delivery","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 6831 This document describes how inter-domain multicast routing will\n function in an environment where Locator/ID Separation is deployed\n using the Locator/ID Separation Protocol (LISP) architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feed 6831 delivery http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 6834","type":"specification","body":"IETF","designation":"RFC 6834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6834.txt","https://www.rfc-editor.org/rfc/rfc6834.pdf"],"folder":"IETF/RFC-6834","files":{"txt":{"path":"standards/IETF/RFC-6834/RFC-6834.txt","sha256":"199ae0258cb69b650277755d53c3440c9bab5d92b5e06e7f4652d92feede363b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the LISP (Locator/ID Separation Protocol)\n Map-Versioning mechanism, which provides in-packet information about\n Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to\n encapsulate LISP data packets. The proposed approach is based on\n associating a version number to EID-to-RLOC mappings and the\n transport of such a version number in the LISP-specific header of\n LISP-encapsulated packets. LISP Map-Versioning is particularly\n useful to inform communicating Ingress Tunnel Routers (ITRs) and\n Egress Tunnel Routers (ETRs) about modifications of the mappings used\n to encapsulate packets. The mechanism is transparent to\n implementations not supporting this feature, since in the LISP-\n specific header and in the Map Records, bits used for Map-Versioning\n can be safely ignored by ITRs and ETRs that do not support the\n mechanism.\n\nStatus of This Memo\n\n This document ","scope_keywords":["6834","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null}],"search_text":"IETF RFC 6834 This document describes the LISP (Locator/ID Separation Protocol)\n Map-Versioning mechanism, which provides in-packet information about\n Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to\n encapsulate LISP data packets. The proposed approach is based on\n associating a version number to EID-to-RLOC mappings and the\n transport of such a version number in the LISP-specific header of\n LISP-encapsulated packets. LISP Map-Versioning is particularly\n useful to inform communicating Ingress Tunnel Routers (ITRs) and\n Egress Tunnel Routers (ETRs) about modifications of the mappings used\n to encapsulate packets. The mechanism is transparent to\n implementations not supporting this feature, since in the LISP-\n specific header and in the Map Records, bits used for Map-Versioning\n can be safely ignored by ITRs and ETRs that do not support the\n mechanism.\n\nStatus of This Memo\n\n This document  6834 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6843","type":"specification","body":"IETF","designation":"RFC 6843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6843.txt","https://www.rfc-editor.org/rfc/rfc6843.pdf"],"folder":"IETF/RFC-6843","files":{"txt":{"path":"standards/IETF/RFC-6843/RFC-6843.txt","sha256":"ffe7354ae17de2b57945eb72191133ca5fbe1b39aa87bf1030987524a2ec2835"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of delay metrics for use in a\n range of Real-time Transport Protocol (RTP) applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6843.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["6843","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 6843 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of delay metrics for use in a\n range of Real-time Transport Protocol (RTP) applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6843.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  6843 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6849","type":"specification","body":"IETF","designation":"RFC 6849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6849.txt","https://www.rfc-editor.org/rfc/rfc6849.pdf"],"folder":"IETF/RFC-6849","files":{"txt":{"path":"standards/IETF/RFC-6849/RFC-6849.txt","sha256":"f464d5b15703ab3e33074be968c5b12178599ed6799d07bb5ae3acbddc74ee8c"}},"tags":["nested-reference","unchanged"],"summary":"The wide deployment of Voice over IP (VoIP), real-time text, and\n Video over IP services has introduced new challenges in managing and\n maintaining real-time voice/text/video quality, reliability, and\n overall performance. In particular, media delivery is an area that\n needs attention. One method of meeting these challenges is\n monitoring the media delivery performance by looping media back to\n the transmitter. This is typically referred to as \"active\n monitoring\" of services. Media loopback is especially popular in\n ensuring the quality of transport to the edge of a given VoIP, real-\n time text, or Video over IP service. Today, in networks that deliver\n real-time media, short of running 'ping' and 'traceroute' to the\n edge, administrators are left without the necessary tools to actively\n monitor, manage, and diagnose quality issues with their service. The\n extension defined herein adds ","scope_keywords":["6849","attribute","attributes","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6849 The wide deployment of Voice over IP (VoIP), real-time text, and\n Video over IP services has introduced new challenges in managing and\n maintaining real-time voice/text/video quality, reliability, and\n overall performance. In particular, media delivery is an area that\n needs attention. One method of meeting these challenges is\n monitoring the media delivery performance by looping media back to\n the transmitter. This is typically referred to as \"active\n monitoring\" of services. Media loopback is especially popular in\n ensuring the quality of transport to the edge of a given VoIP, real-\n time text, or Video over IP service. Today, in networks that deliver\n real-time media, short of running 'ping' and 'traceroute' to the\n edge, administrators are left without the necessary tools to actively\n monitor, manage, and diagnose quality issues with their service. The\n extension defined herein adds  6849 attribute attributes delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6863","type":"specification","body":"IETF","designation":"RFC 6863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6863.txt","https://www.rfc-editor.org/rfc/rfc6863.pdf"],"folder":"IETF/RFC-6863","files":{"txt":{"path":"standards/IETF/RFC-6863/RFC-6863.txt","sha256":"0326e54e8e652d951fa5452f7c7d701f09860d06a1135188fab10bc1275aece9"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes OSPFv2 and OSPFv3 according to the guidelines\n set forth in Section 4.2 of the \"Keying and Authentication for\n Routing Protocols (KARP) Design Guidelines\" (RFC 6518). Key\n components of solutions to gaps identified in this document are\n already underway.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a","scope_keywords":["6863","algorithm","algorithms","authentication","http","identification","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6952","folder":"IETF/RFC-6952","source":"IETF/RFC-6952/RFC-6952.txt","version":null}],"search_text":"IETF RFC 6863 This document analyzes OSPFv2 and OSPFv3 according to the guidelines\n set forth in Section 4.2 of the \"Keying and Authentication for\n Routing Protocols (KARP) Design Guidelines\" (RFC 6518). Key\n components of solutions to gaps identified in this document are\n already underway.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a 6863 algorithm algorithms authentication http identification key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6868","type":"specification","body":"IETF","designation":"RFC 6868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6868.txt","https://www.rfc-editor.org/rfc/rfc6868.pdf"],"folder":"IETF/RFC-6868","files":{"txt":{"path":"standards/IETF/RFC-6868/RFC-6868.txt","sha256":"f103a889a51b4a629b86a2c3369f16e4c858382899edfc80aeb8502421408e7c"}},"tags":["nested-reference","unchanged"],"summary":"This specification updates the data formats for iCalendar (RFC 5545)\n and vCard (RFC 6350) to allow parameter values to include certain\n characters forbidden by the existing specifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6868.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is sub","scope_keywords":["6868","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null}],"search_text":"IETF RFC 6868 This specification updates the data formats for iCalendar (RFC 5545)\n and vCard (RFC 6350) to allow parameter values to include certain\n characters forbidden by the existing specifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6868.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is sub 6868 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6871","type":"specification","body":"IETF","designation":"RFC 6871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6871.txt","https://www.rfc-editor.org/rfc/rfc6871.pdf"],"folder":"IETF/RFC-6871","files":{"txt":{"path":"standards/IETF/RFC-6871/RFC-6871.txt","sha256":"f693e9a7d64aec3c216161a8350fc56d25769c51c2cbe40b3b018fbc8fba704a"}},"tags":["nested-reference","unchanged"],"summary":"Session Description Protocol (SDP) capability negotiation provides a\n general framework for indicating and negotiating capabilities in SDP.\n The base framework defines only capabilities for negotiating\n transport protocols and attributes. This documents extends the\n framework by defining media capabilities that can be used to\n negotiate media types and their associated parameters.\n\n This document updates the IANA Considerations of RFC 5939.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document","scope_keywords":["6871","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6871 Session Description Protocol (SDP) capability negotiation provides a\n general framework for indicating and negotiating capabilities in SDP.\n The base framework defines only capabilities for negotiating\n transport protocols and attributes. This documents extends the\n framework by defining media capabilities that can be used to\n negotiate media types and their associated parameters.\n\n This document updates the IANA Considerations of RFC 5939.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document 6871 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6872","type":"specification","body":"IETF","designation":"RFC 6872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6872.txt","https://www.rfc-editor.org/rfc/rfc6872.pdf"],"folder":"IETF/RFC-6872","files":{"txt":{"path":"standards/IETF/RFC-6872/RFC-6872.txt","sha256":"2726162ba8a7ec997dbfff81583bb67ef8fc17f9f9a3d1dcc7acfb479f18198d"}},"tags":["nested-reference","unchanged"],"summary":"Well-known web servers such as Apache and web proxies like Squid\n support event logging using a common log format. The logs produced\n using these de facto standard formats are invaluable to system\n administrators for troubleshooting a server and tool writers to craft\n tools that mine the log files and produce reports and trends.\n Furthermore, these log files can also be used to train anomaly\n detection systems and feed events into a security event management\n system. The Session Initiation Protocol (SIP) does not have a common\n log format, and, as a result, each server supports a distinct log\n format that makes it unnecessarily complex to produce tools to do\n trend analysis and security detection. This document describes a\n framework, including requirements and analysis of existing\n approaches, and specifies an information model for development of a\n SIP common log file format that can b","scope_keywords":["6872","http","key","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 6872 Well-known web servers such as Apache and web proxies like Squid\n support event logging using a common log format. The logs produced\n using these de facto standard formats are invaluable to system\n administrators for troubleshooting a server and tool writers to craft\n tools that mine the log files and produce reports and trends.\n Furthermore, these log files can also be used to train anomaly\n detection systems and feed events into a security event management\n system. The Session Initiation Protocol (SIP) does not have a common\n log format, and, as a result, each server supports a distinct log\n format that makes it unnecessarily complex to produce tools to do\n trend analysis and security detection. This document describes a\n framework, including requirements and analysis of existing\n approaches, and specifies an information model for development of a\n SIP common log file format that can b 6872 http key license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6874","type":"specification","body":"IETF","designation":"RFC 6874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6874.txt","https://www.rfc-editor.org/rfc/rfc6874.pdf"],"folder":"IETF/RFC-6874","files":{"txt":{"path":"standards/IETF/RFC-6874/RFC-6874.txt","sha256":"5f54b04f2035eb12f9a444bc6c2389582b9400c3df64a90965f9409c939380d5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the zone identifier of an IPv6 scoped\n address, defined as <zone_id> in the IPv6 Scoped Address Architecture\n (RFC 4007), can be represented in a literal IPv6 address and in a\n Uniform Resource Identifier that includes such a literal address. It\n updates the URI Generic Syntax specification (RFC 3986) accordingly.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r","scope_keywords":["6874","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null}],"search_text":"IETF RFC 6874 This document describes how the zone identifier of an IPv6 scoped\n address, defined as <zone_id> in the IPv6 Scoped Address Architecture\n (RFC 4007), can be represented in a literal IPv6 address and in a\n Uniform Resource Identifier that includes such a literal address. It\n updates the URI Generic Syntax specification (RFC 3986) accordingly.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r 6874 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6876","type":"specification","body":"IETF","designation":"RFC 6876","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6876.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6876.txt","https://www.rfc-editor.org/rfc/rfc6876.pdf"],"folder":"IETF/RFC-6876","files":{"txt":{"path":"standards/IETF/RFC-6876/RFC-6876.txt","sha256":"8956c369671d0c3b566e86935b91ed9ed88fc40f48dd785c9734c953e9095990"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies PT-TLS, a TLS-based Posture Transport (PT)\n protocol. The PT-TLS protocol carries the Network Endpoint\n Assessment (NEA) message exchange under the protection of a Transport\n Layer Security (TLS) secured tunnel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6876.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document author","scope_keywords":["6876","authentication","authorization","http","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null},{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 6876 This document specifies PT-TLS, a TLS-based Posture Transport (PT)\n protocol. The PT-TLS protocol carries the Network Endpoint\n Assessment (NEA) message exchange under the protection of a Transport\n Layer Security (TLS) secured tunnel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6876.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document author 6876 authentication authorization http license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6881","type":"specification","body":"IETF","designation":"RFC 6881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6881.txt","https://www.rfc-editor.org/rfc/rfc6881.pdf"],"folder":"IETF/RFC-6881","files":{"txt":{"path":"standards/IETF/RFC-6881/RFC-6881.txt","sha256":"36dea8b7db4108f64df7a25eb62002a26bf1593a73273c8488ae1cbf95317844"}},"tags":["nested-reference","unchanged"],"summary":"The IETF and other standards organizations have efforts targeted at\n standardizing various aspects of placing emergency calls on IP\n networks. This memo describes best current practice on how devices,\n networks, and services using IETF protocols should use such standards\n to make emergency calls.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6881.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF","scope_keywords":["6881","http","key","license","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7406","folder":"IETF/RFC-7406","source":"IETF/RFC-7406/RFC-7406.txt","version":null}],"search_text":"IETF RFC 6881 The IETF and other standards organizations have efforts targeted at\n standardizing various aspects of placing emergency calls on IP\n networks. This memo describes best current practice on how devices,\n networks, and services using IETF protocols should use such standards\n to make emergency calls.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6881.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF 6881 http key license subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 6901","type":"specification","body":"IETF","designation":"RFC 6901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6901.txt","https://www.rfc-editor.org/rfc/rfc6901.pdf"],"folder":"IETF/RFC-6901","files":{"txt":{"path":"standards/IETF/RFC-6901/RFC-6901.txt","sha256":"12f9f4fc13d686aa4fbe7d144d70166cd3fcd4ab89174c2b13bda8f4b55e49da"}},"tags":["nested-reference","unchanged"],"summary":"JSON Pointer defines a string syntax for identifying a specific value\n within a JavaScript Object Notation (JSON) document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6901.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to ","scope_keywords":["6901","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6902","folder":"IETF/RFC-6902","source":"IETF/RFC-6902/RFC-6902.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null}],"search_text":"IETF RFC 6901 JSON Pointer defines a string syntax for identifying a specific value\n within a JavaScript Object Notation (JSON) document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6901.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to  6901 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6902","type":"specification","body":"IETF","designation":"RFC 6902","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6902.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6902.txt","https://www.rfc-editor.org/rfc/rfc6902.pdf"],"folder":"IETF/RFC-6902","files":{"txt":{"path":"standards/IETF/RFC-6902/RFC-6902.txt","sha256":"ded8fa1754ab1566fd72611c9d5bcde931cd2bdf8351889e2ef5b50efdf1eed4"}},"tags":["nested-reference","unchanged"],"summary":"JSON Patch defines a JSON document structure for expressing a\n sequence of operations to apply to a JavaScript Object Notation\n (JSON) document; it is suitable for use with the HTTP PATCH method.\n The \"application/json-patch+json\" media type is used to identify such\n patch documents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6902.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust a","scope_keywords":["6902","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null}],"search_text":"IETF RFC 6902 JSON Patch defines a JSON document structure for expressing a\n sequence of operations to apply to a JavaScript Object Notation\n (JSON) document; it is suitable for use with the HTTP PATCH method.\n The \"application/json-patch+json\" media type is used to identify such\n patch documents.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6902.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust a 6902 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6904","type":"specification","body":"IETF","designation":"RFC 6904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6904.txt","https://www.rfc-editor.org/rfc/rfc6904.pdf"],"folder":"IETF/RFC-6904","files":{"txt":{"path":"standards/IETF/RFC-6904/RFC-6904.txt","sha256":"589b92e40dff5680992fdcf4a3c1917603e6324ea2f55009aa360befbe61ca83"}},"tags":["nested-reference","unchanged"],"summary":"The Secure Real-time Transport Protocol (SRTP) provides\n authentication, but not encryption, of the headers of Real-time\n Transport Protocol (RTP) packets. However, RTP header extensions may\n carry sensitive information for which participants in multimedia\n sessions want confidentiality. This document provides a mechanism,\n extending the mechanisms of SRTP, to selectively encrypt RTP header\n extensions in SRTP.\n\n This document updates RFC 3711, the Secure Real-time Transport\n Protocol specification, to require that all future SRTP encryption\n transforms specify how RTP header extensions are to be encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet En","scope_keywords":["6904","algorithm","algorithms","authentication","encryption","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7201","folder":"IETF/RFC-7201","source":"IETF/RFC-7201/RFC-7201.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 6904 The Secure Real-time Transport Protocol (SRTP) provides\n authentication, but not encryption, of the headers of Real-time\n Transport Protocol (RTP) packets. However, RTP header extensions may\n carry sensitive information for which participants in multimedia\n sessions want confidentiality. This document provides a mechanism,\n extending the mechanisms of SRTP, to selectively encrypt RTP header\n extensions in SRTP.\n\n This document updates RFC 3711, the Secure Real-time Transport\n Protocol specification, to require that all future SRTP encryption\n transforms specify how RTP header extensions are to be encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet En 6904 algorithm algorithms authentication encryption http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 6910","type":"specification","body":"IETF","designation":"RFC 6910","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6910.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6910.txt","https://www.rfc-editor.org/rfc/rfc6910.pdf"],"folder":"IETF/RFC-6910","files":{"txt":{"path":"standards/IETF/RFC-6910/RFC-6910.txt","sha256":"8ec0b8f1fc68798a14619c31eb5ae611a40e22eb871f602f5e27a31ae2ef9b7e"}},"tags":["nested-reference","unchanged"],"summary":"The \"completion of calls\" feature defined in this specification\n allows the caller of a failed call to be notified when the callee\n becomes available to receive a call.\n\n For the realization of a basic solution without queuing, this\n document references the usage of the dialog event package (RFC 4235)\n that is described as 'Automatic Redial' in \"Session Initiation\n Protocol Service Examples\" (RFC 5359).\n\n For the realization of a more comprehensive solution with queuing,\n this document introduces an architecture for implementing these\n features in the Session Initiation Protocol where \"completion of\n calls\" implementations associated with the caller's and callee's\n endpoints cooperate to place the caller's request for completion of\n calls into a queue at the callee's endpoint; when a caller's request\n is ready to be serviced, re-attempt of the original, failed call is\n then made.\n\n The a","scope_keywords":["6910","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 6910 The \"completion of calls\" feature defined in this specification\n allows the caller of a failed call to be notified when the callee\n becomes available to receive a call.\n\n For the realization of a basic solution without queuing, this\n document references the usage of the dialog event package (RFC 4235)\n that is described as 'Automatic Redial' in \"Session Initiation\n Protocol Service Examples\" (RFC 5359).\n\n For the realization of a more comprehensive solution with queuing,\n this document introduces an architecture for implementing these\n features in the Session Initiation Protocol where \"completion of\n calls\" implementations associated with the caller's and callee's\n endpoints cooperate to place the caller's request for completion of\n calls into a queue at the callee's endpoint; when a caller's request\n is ready to be serviced, re-attempt of the original, failed call is\n then made.\n\n The a 6910 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6916","type":"specification","body":"IETF","designation":"RFC 6916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6916.txt","https://www.rfc-editor.org/rfc/rfc6916.pdf"],"folder":"IETF/RFC-6916","files":{"txt":{"path":"standards/IETF/RFC-6916/RFC-6916.txt","sha256":"05dbd8d5d0da13bea9f62c835192ebeb4d257af82d75f43eef4d1ac56710ecf7"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the process that Certification Authorities\n (CAs) and Relying Parties (RPs) participating in the Resource Public\n Key Infrastructure (RPKI) will need to follow to transition to a new\n (and probably cryptographically stronger) algorithm set. The process\n is expected to be completed over a timescale of several years.\n Consequently, no emergency transition is specified. The transition\n procedure defined in this document supports only a top-down migration\n (parent migrates before children).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of","scope_keywords":["6916","algorithm","algorithms","certificate","certificates","crl","hash","http","key","keys","license","pki","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null}],"search_text":"IETF RFC 6916 This document specifies the process that Certification Authorities\n (CAs) and Relying Parties (RPs) participating in the Resource Public\n Key Infrastructure (RPKI) will need to follow to transition to a new\n (and probably cryptographically stronger) algorithm set. The process\n is expected to be completed over a timescale of several years.\n Consequently, no emergency transition is specified. The transition\n procedure defined in this document supports only a top-down migration\n (parent migrates before children).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of 6916 algorithm algorithms certificate certificates crl hash http key keys license pki revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6925","type":"specification","body":"IETF","designation":"RFC 6925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6925.txt","https://www.rfc-editor.org/rfc/rfc6925.pdf"],"folder":"IETF/RFC-6925","files":{"txt":{"path":"standards/IETF/RFC-6925/RFC-6925.txt","sha256":"32e0db4844cbb11b981d5e1c21b26319a409fafab3cad5beaf2a4a121b5eeb5c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Relay Agent Identifier sub-option for the\n Dynamic Host Configuration Protocol (DHCP) Relay Agent Information\n option. The sub-option carries a value that uniquely identifies the\n relay agent device within the administrative domain. The value is\n normally administratively configured in the relay agent. The sub-\n option allows a DHCP relay agent to include the identifier in the\n DHCP messages it sends.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata","scope_keywords":["6925","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null}],"search_text":"IETF RFC 6925 This document defines a new Relay Agent Identifier sub-option for the\n Dynamic Host Configuration Protocol (DHCP) Relay Agent Information\n option. The sub-option carries a value that uniquely identifies the\n relay agent device within the administrative domain. The value is\n normally administratively configured in the relay agent. The sub-\n option allows a DHCP relay agent to include the identifier in the\n DHCP messages it sends.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata 6925 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6935","type":"specification","body":"IETF","designation":"RFC 6935","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6935.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6935.txt","https://www.rfc-editor.org/rfc/rfc6935.pdf"],"folder":"IETF/RFC-6935","files":{"txt":{"path":"standards/IETF/RFC-6935/RFC-6935.txt","sha256":"4b793e25834cab72106ef730fbda9d10888242e5ee14d1bbb28d20f80ec8312b"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the IPv6 specification (RFC 2460) to improve\n performance when a tunnel protocol uses UDP with IPv6 to tunnel\n packets. The performance improvement is obtained by relaxing the\n IPv6 UDP checksum requirement for tunnel protocols whose header\n information is protected on the \"inner\" packet being carried.\n Relaxing this requirement removes the overhead associated with the\n computation of UDP checksums on IPv6 packets that carry the tunnel\n protocol packets. This specification describes how the IPv6 UDP\n checksum requirement can be relaxed when the encapsulated packet\n itself contains a checksum. It also describes the limitations and\n risks of this approach and discusses the restrictions on the use of\n this method.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen","scope_keywords":["6935","http","key","license","pid","pki","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 6935 This document updates the IPv6 specification (RFC 2460) to improve\n performance when a tunnel protocol uses UDP with IPv6 to tunnel\n packets. The performance improvement is obtained by relaxing the\n IPv6 UDP checksum requirement for tunnel protocols whose header\n information is protected on the \"inner\" packet being carried.\n Relaxing this requirement removes the overhead associated with the\n computation of UDP checksums on IPv6 packets that carry the tunnel\n protocol packets. This specification describes how the IPv6 UDP\n checksum requirement can be relaxed when the encapsulated packet\n itself contains a checksum. It also describes the limitations and\n risks of this approach and discusses the restrictions on the use of\n this method.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen 6935 http key license pid pki risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6946","type":"specification","body":"IETF","designation":"RFC 6946","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6946.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6946.txt","https://www.rfc-editor.org/rfc/rfc6946.pdf"],"folder":"IETF/RFC-6946","files":{"txt":{"path":"standards/IETF/RFC-6946/RFC-6946.txt","sha256":"b70e2c2894e6ac08bc29ceef2c5d1b24822cf3d70177f1962332be185742262a"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 specification allows packets to contain a Fragment Header\n without the packet being actually fragmented into multiple pieces (we\n refer to these packets as \"atomic fragments\"). Such packets are\n typically sent by hosts that have received an ICMPv6 \"Packet Too Big\"\n error message that advertises a Next-Hop MTU smaller than 1280 bytes,\n and are currently processed by some implementations as normal\n \"fragmented traffic\" (i.e., they are \"reassembled\" with any other\n queued fragments that supposedly correspond to the same original\n packet). Thus, an attacker can cause hosts to employ atomic\n fragments by forging ICMPv6 \"Packet Too Big\" error messages, and then\n launch any fragmentation-based attacks against such traffic. This\n document discusses the generation of the aforementioned atomic\n fragments and the corresponding security implications. Additionally,\n this document formally up","scope_keywords":["6946","http","identification","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7739","folder":"IETF/RFC-7739","source":"IETF/RFC-7739/RFC-7739.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 6946 The IPv6 specification allows packets to contain a Fragment Header\n without the packet being actually fragmented into multiple pieces (we\n refer to these packets as \"atomic fragments\"). Such packets are\n typically sent by hosts that have received an ICMPv6 \"Packet Too Big\"\n error message that advertises a Next-Hop MTU smaller than 1280 bytes,\n and are currently processed by some implementations as normal\n \"fragmented traffic\" (i.e., they are \"reassembled\" with any other\n queued fragments that supposedly correspond to the same original\n packet). Thus, an attacker can cause hosts to employ atomic\n fragments by forging ICMPv6 \"Packet Too Big\" error messages, and then\n launch any fragmentation-based attacks against such traffic. This\n document discusses the generation of the aforementioned atomic\n fragments and the corresponding security implications. Additionally,\n this document formally up 6946 http identification key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6947","type":"specification","body":"IETF","designation":"RFC 6947","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6947.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6947.txt","https://www.rfc-editor.org/rfc/rfc6947.pdf"],"folder":"IETF/RFC-6947","files":{"txt":{"path":"standards/IETF/RFC-6947/RFC-6947.txt","sha256":"31ffc8df35bdd9f6454f41583c18b0cd352311b90cee8dcbc534ce5d153defa8"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a mechanism that allows the same SDP offer to\n carry multiple IP addresses of different address families (e.g., IPv4\n and IPv6). The proposed attribute, the \"altc\" attribute, solves the\n backward-compatibility problem that plagued Alternative Network\n Address Types (ANAT) due to their syntax.\n\n The proposed solution is applicable to scenarios where connectivity\n checks are not required. If connectivity checks are required,\n Interactive Connectivity Establishment (ICE), as specified in RFC\n 5245, provides such a solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or de","scope_keywords":["6947","attribute","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6947 This document proposes a mechanism that allows the same SDP offer to\n carry multiple IP addresses of different address families (e.g., IPv4\n and IPv6). The proposed attribute, the \"altc\" attribute, solves the\n backward-compatibility problem that plagued Alternative Network\n Address Types (ANAT) due to their syntax.\n\n The proposed solution is applicable to scenarios where connectivity\n checks are not required. If connectivity checks are required,\n Interactive Connectivity Establishment (ICE), as specified in RFC\n 5245, provides such a solution.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or de 6947 attribute delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6954","type":"specification","body":"IETF","designation":"RFC 6954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6954.txt","https://www.rfc-editor.org/rfc/rfc6954.pdf"],"folder":"IETF/RFC-6954","files":{"txt":{"path":"standards/IETF/RFC-6954/RFC-6954.txt","sha256":"978838530624ebabefb82e20598f9664f9159534939de7a5598cdf057be2c36d"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies use of the Elliptic Curve Cryptography (ECC)\n Brainpool elliptic curve groups for key exchange in the Internet Key\n Exchange Protocol version 2 (IKEv2).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6954.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the ","scope_keywords":["6954","certificate","certificates","http","key","license","registered","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null}],"search_text":"IETF RFC 6954 This document specifies use of the Elliptic Curve Cryptography (ECC)\n Brainpool elliptic curve groups for key exchange in the Internet Key\n Exchange Protocol version 2 (IKEv2).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6954.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the  6954 certificate certificates http key license registered revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6957","type":"specification","body":"IETF","designation":"RFC 6957","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6957.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6957.txt","https://www.rfc-editor.org/rfc/rfc6957.pdf"],"folder":"IETF/RFC-6957","files":{"txt":{"path":"standards/IETF/RFC-6957/RFC-6957.txt","sha256":"347b44e61f5bb5612d7d97888abee3238a6e991a03e16024b5097494b380636c"}},"tags":["nested-reference","unchanged"],"summary":"The document describes a proxy-based mechanism allowing the use of\n Duplicate Address Detection (DAD) by IPv6 nodes in a point-to-\n multipoint architecture with a \"split-horizon\" forwarding scheme,\n primarily deployed for Digital Subscriber Line (DSL) and Fiber access\n architectures. Based on the DAD signaling, the first-hop router\n stores in a Binding Table all known IPv6 addresses used on a point-\n to-multipoint domain (e.g., VLAN). When a node performs DAD for an\n address already used by another node, the first-hop router defends\n the address rather than the device using the address.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Gr","scope_keywords":["6957","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7136","folder":"IETF/RFC-7136","source":"IETF/RFC-7136/RFC-7136.txt","version":null}],"search_text":"IETF RFC 6957 The document describes a proxy-based mechanism allowing the use of\n Duplicate Address Detection (DAD) by IPv6 nodes in a point-to-\n multipoint architecture with a \"split-horizon\" forwarding scheme,\n primarily deployed for Digital Subscriber Line (DSL) and Fiber access\n architectures. Based on the DAD signaling, the first-hop router\n stores in a Binding Table all known IPv6 addresses used on a point-\n to-multipoint domain (e.g., VLAN). When a node performs DAD for an\n address already used by another node, the first-hop router defends\n the address rather than the device using the address.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Gr 6957 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6958","type":"specification","body":"IETF","designation":"RFC 6958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6958.txt","https://www.rfc-editor.org/rfc/rfc6958.pdf"],"folder":"IETF/RFC-6958","files":{"txt":{"path":"standards/IETF/RFC-6958/RFC-6958.txt","sha256":"80b371743ec038bd7475bac8042a3e7e1a6610c0f886d788ec9cfd5c927db6ef"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) Block that allows the reporting of burst and gap loss metrics\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6958.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP ","scope_keywords":["6958","algorithm","algorithms","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 6958 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) Block that allows the reporting of burst and gap loss metrics\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6958.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP  6958 algorithm algorithms attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6960","type":"specification","body":"IETF","designation":"RFC 6960","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6960.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6960.txt","https://www.rfc-editor.org/rfc/rfc6960.pdf"],"folder":"IETF/RFC-6960","files":{"txt":{"path":"standards/IETF/RFC-6960/RFC-6960.txt","sha256":"7e63ffa1ea2ce2737d9aaf895a63776e9105ddbdfc97b8ae4029e3e825b4cdea"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol useful in determining the current\n status of a digital certificate without requiring Certificate\n Revocation Lists (CRLs). Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents. This\n document obsoletes RFCs 2560 and 6277. It also updates RFC 5912.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6960.\n\nSante","scope_keywords":["6960","algorithm","algorithms","certificate","crl","http","key","license","ocsp","pki","revocation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 411-2","folder":"ETSI/EN-319-411-2-V2.6.1","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf","version":"2.6.1"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"IETF RFC 6960 This document specifies a protocol useful in determining the current\n status of a digital certificate without requiring Certificate\n Revocation Lists (CRLs). Additional mechanisms addressing PKIX\n operational requirements are specified in separate documents. This\n document obsoletes RFCs 2560 and 6277. It also updates RFC 5912.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6960.\n\nSante 6960 algorithm algorithms certificate crl http key license ocsp pki revocation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6961","type":"specification","body":"IETF","designation":"RFC 6961","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6961.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6961.txt","https://www.rfc-editor.org/rfc/rfc6961.pdf"],"folder":"IETF/RFC-6961","files":{"txt":{"path":"standards/IETF/RFC-6961/RFC-6961.txt","sha256":"c33e7e30760c8852509fbdae89f2daf3efcc424d6a90651de048efd6685745db"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Transport Layer Security (TLS) Certificate\n Status Version 2 Extension to allow clients to specify and support\n several certificate status methods. (The use of the Certificate\n Status extension is commonly referred to as \"OCSP stapling\".) Also\n defined is a new method based on the Online Certificate Status\n Protocol (OCSP) that servers can use to provide status information\n about not only the server's own certificate but also the status of\n intermediate certificates in the chain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of","scope_keywords":["6961","certificate","certificates","crl","http","issuer","key","license","ocsp","pki","presentation","revocation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7633","folder":"IETF/RFC-7633","source":"IETF/RFC-7633/RFC-7633.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 6961 This document defines the Transport Layer Security (TLS) Certificate\n Status Version 2 Extension to allow clients to specify and support\n several certificate status methods. (The use of the Certificate\n Status extension is commonly referred to as \"OCSP stapling\".) Also\n defined is a new method based on the Online Certificate Status\n Protocol (OCSP) that servers can use to provide status information\n about not only the server's own certificate but also the status of\n intermediate certificates in the chain.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of 6961 certificate certificates crl http issuer key license ocsp pki presentation revocation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 6962","type":"specification","body":"IETF","designation":"RFC 6962","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6962.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6962.txt","https://www.rfc-editor.org/rfc/rfc6962.pdf"],"folder":"IETF/RFC-6962","files":{"txt":{"path":"standards/IETF/RFC-6962/RFC-6962.txt","sha256":"08fdf31c10b9f20872a65c027a9fe8cee27280f930120784241a57de744752af"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an experimental protocol for publicly logging\n the existence of Transport Layer Security (TLS) certificates as they\n are issued or observed, in a manner that allows anyone to audit\n certificate authority (CA) activity and notice the issuance of\n suspect certificates as well as to audit the certificate logs\n themselves. The intent is that eventually clients would refuse to\n honor certificates that do not appear in a log, effectively forcing\n CAs to add all issued certificates to the logs.\n\n Logs are network services that implement the protocol operations for\n submissions and queries that are defined in this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This do","scope_keywords":["6962","audit","certificate","certificates","hash","holder","http","license","path","signature","signatures","subject","timestamp","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IETF RFC 6962 This document describes an experimental protocol for publicly logging\n the existence of Transport Layer Security (TLS) certificates as they\n are issued or observed, in a manner that allows anyone to audit\n certificate authority (CA) activity and notice the issuance of\n suspect certificates as well as to audit the certificate logs\n themselves. The intent is that eventually clients would refuse to\n honor certificates that do not appear in a log, effectively forcing\n CAs to add all issued certificates to the logs.\n\n Logs are network services that implement the protocol operations for\n submissions and queries that are defined in this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This do 6962 audit certificate certificates hash holder http license path signature signatures subject timestamp tls trust nested-reference unchanged"},{"id":"IETF RFC 6963","type":"specification","body":"IETF","designation":"RFC 6963","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6963.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6963.txt","https://www.rfc-editor.org/rfc/rfc6963.pdf"],"folder":"IETF/RFC-6963","files":{"txt":{"path":"standards/IETF/RFC-6963/RFC-6963.txt","sha256":"76b07264d08fd8c9897247436994714c97b4b5977080d97fd722de88ec01dedd"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Uniform Resource Name (URN) namespace\n identifier enabling the generation of URNs that are appropriate for\n use in documentation and in URN-related testing and experimentation.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6963.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document ","scope_keywords":["6963","http","key","license","registered","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 6963 This document defines a Uniform Resource Name (URN) namespace\n identifier enabling the generation of URNs that are appropriate for\n use in documentation and in URN-related testing and experimentation.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6963.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document  6963 http key license registered subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6970","type":"specification","body":"IETF","designation":"RFC 6970","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6970.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6970.txt","https://www.rfc-editor.org/rfc/rfc6970.pdf"],"folder":"IETF/RFC-6970","files":{"txt":{"path":"standards/IETF/RFC-6970/RFC-6970.txt","sha256":"1511c0a22f6dd427e24d79645ebd02e576a39d94276d6230d279651585f25c5e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the behavior of the Universal Plug and Play\n (UPnP) Internet Gateway Device - Port Control Protocol Interworking\n Function (IGD-PCP IWF). A UPnP IGD-PCP IWF is required to be\n embedded in Customer Premises (CP) routers to allow for transparent\n NAT control in environments where a UPnP IGD is used on the LAN side\n and PCP is used on the external side of the CP router.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma","scope_keywords":["6970","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7753","folder":"IETF/RFC-7753","source":"IETF/RFC-7753/RFC-7753.txt","version":null}],"search_text":"IETF RFC 6970 This document specifies the behavior of the Universal Plug and Play\n (UPnP) Internet Gateway Device - Port Control Protocol Interworking\n Function (IGD-PCP IWF). A UPnP IGD-PCP IWF is required to be\n embedded in Customer Premises (CP) routers to allow for transparent\n NAT control in environments where a UPnP IGD is used on the LAN side\n and PCP is used on the external side of the CP router.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma 6970 http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6975","type":"specification","body":"IETF","designation":"RFC 6975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6975.txt","https://www.rfc-editor.org/rfc/rfc6975.pdf"],"folder":"IETF/RFC-6975","files":{"txt":{"path":"standards/IETF/RFC-6975/RFC-6975.txt","sha256":"b1575c180351fefff2b18c203ff50b086be7ea12b866543ceaa921a90fbbead8"}},"tags":["nested-reference","unchanged"],"summary":"The DNS Security Extensions (DNSSEC) were developed to provide origin\n authentication and integrity protection for DNS data by using digital\n signatures. These digital signatures can be generated using\n different algorithms. This document specifies a way for validating\n end-system resolvers to signal to a server which digital signature\n and hash algorithms they support. The extensions allow the signaling\n of new algorithm uptake in client code to allow zone administrators\n to know when it is possible to complete an algorithm rollover in a\n DNSSEC-signed zone.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat","scope_keywords":["6975","algorithm","algorithms","authentication","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 8145","folder":"IETF/RFC-8145","source":"IETF/RFC-8145/RFC-8145.txt","version":null}],"search_text":"IETF RFC 6975 The DNS Security Extensions (DNSSEC) were developed to provide origin\n authentication and integrity protection for DNS data by using digital\n signatures. These digital signatures can be generated using\n different algorithms. This document specifies a way for validating\n end-system resolvers to signal to a server which digital signature\n and hash algorithms they support. The extensions allow the signaling\n of new algorithm uptake in client code to allow zone administrators\n to know when it is possible to complete an algorithm rollover in a\n DNSSEC-signed zone.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat 6975 algorithm algorithms authentication hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 6977","type":"specification","body":"IETF","designation":"RFC 6977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6977.txt","https://www.rfc-editor.org/rfc/rfc6977.pdf"],"folder":"IETF/RFC-6977","files":{"txt":{"path":"standards/IETF/RFC-6977/RFC-6977.txt","sha256":"b512c1fae40ef0a8ac57866ec38cb7fe7e02b2a835975284024e42c14022ddb3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two new DHCPv6 messages: Reconfigure-Request\n and Reconfigure-Reply. The Reconfigure-Request message is sent by a\n DHCPv6 relay agent to notify a DHCPv6 server about a configuration\n information change, so that the DHCPv6 server can send a Reconfigure\n message accordingly. The Reconfigure-Reply message is used by the\n server to acknowledge the receipt of the Reconfigure-Request message.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide","scope_keywords":["6977","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null}],"search_text":"IETF RFC 6977 This document defines two new DHCPv6 messages: Reconfigure-Request\n and Reconfigure-Reply. The Reconfigure-Request message is sent by a\n DHCPv6 relay agent to notify a DHCPv6 server about a configuration\n information change, so that the DHCPv6 server can send a Reconfigure\n message accordingly. The Reconfigure-Reply message is used by the\n server to acknowledge the receipt of the Reconfigure-Request message.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide 6977 http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 6980","type":"specification","body":"IETF","designation":"RFC 6980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6980.txt","https://www.rfc-editor.org/rfc/rfc6980.pdf"],"folder":"IETF/RFC-6980","files":{"txt":{"path":"standards/IETF/RFC-6980/RFC-6980.txt","sha256":"b4a487ba91fb46dab67334e6adb6fc363555446f9305f7218bfcdd862d962093"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes the security implications of employing IPv6\n fragmentation with Neighbor Discovery (ND) messages. It updates RFC\n 4861 such that use of the IPv6 Fragmentation Header is forbidden in\n all Neighbor Discovery messages, thus allowing for simple and\n effective countermeasures for Neighbor Discovery attacks. Finally,\n it discusses the security implications of using IPv6 fragmentation\n with SEcure Neighbor Discovery (SEND) and formally updates RFC 3971\n to provide advice regarding how the aforementioned security\n implications can be mitigated.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat","scope_keywords":["6980","certificate","certificates","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null}],"search_text":"IETF RFC 6980 This document analyzes the security implications of employing IPv6\n fragmentation with Neighbor Discovery (ND) messages. It updates RFC\n 4861 such that use of the IPv6 Fragmentation Header is forbidden in\n all Neighbor Discovery messages, thus allowing for simple and\n effective countermeasures for Neighbor Discovery attacks. Finally,\n it discusses the security implications of using IPv6 fragmentation\n with SEcure Neighbor Discovery (SEND) and formally updates RFC 3971\n to provide advice regarding how the aforementioned security\n implications can be mitigated.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further informat 6980 certificate certificates http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6985","type":"specification","body":"IETF","designation":"RFC 6985","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6985.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6985.txt","https://www.rfc-editor.org/rfc/rfc6985.pdf"],"folder":"IETF/RFC-6985","files":{"txt":{"path":"standards/IETF/RFC-6985/RFC-6985.txt","sha256":"f55210b1102f57d579b02ae42ffc36fe07eb3cf043c62ac9191ec2061d99b1ab"}},"tags":["nested-reference","unchanged"],"summary":"Benchmarking methodologies have always relied on test conditions with\n constant packet sizes, with the goal of understanding what network\n device capability has been tested. Tests with a constant packet size\n reveal device capabilities but differ significantly from the\n conditions encountered in operational deployment, so additional tests\n are sometimes conducted with a mixture of packet sizes, or \"IMIX\"\n (\"Internet Mix\"). The mixture of sizes a networking device will\n encounter is highly variable and depends on many factors. An IMIX\n suited for one networking device and deployment will not be\n appropriate for another. However, the mix of sizes may be known, and\n the tester may be asked to augment the fixed-size tests. To address\n this need and the perpetual goal of specifying repeatable test\n conditions, this document defines a way to specify the exact\n repeating sequence of packet size","scope_keywords":["6985","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null}],"search_text":"IETF RFC 6985 Benchmarking methodologies have always relied on test conditions with\n constant packet sizes, with the goal of understanding what network\n device capability has been tested. Tests with a constant packet size\n reveal device capabilities but differ significantly from the\n conditions encountered in operational deployment, so additional tests\n are sometimes conducted with a mixture of packet sizes, or \"IMIX\"\n (\"Internet Mix\"). The mixture of sizes a networking device will\n encounter is highly variable and depends on many factors. An IMIX\n suited for one networking device and deployment will not be\n appropriate for another. However, the mix of sizes may be known, and\n the tester may be asked to augment the fixed-size tests. To address\n this need and the perpetual goal of specifying repeatable test\n conditions, this document defines a way to specify the exact\n repeating sequence of packet size 6985 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6989","type":"specification","body":"IETF","designation":"RFC 6989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6989.txt","https://www.rfc-editor.org/rfc/rfc6989.pdf"],"folder":"IETF/RFC-6989","files":{"txt":{"path":"standards/IETF/RFC-6989/RFC-6989.txt","sha256":"efa8744f4f162f4038b48578ba96eb40fecb52006a1ecf354a26417d18d3e220"}},"tags":["nested-reference","unchanged"],"summary":"This document adds a small number of mandatory tests required for the\n secure operation of the Internet Key Exchange Protocol version 2\n (IKEv2) with elliptic curve groups. No change is required to IKE\n implementations that use modular exponential groups, other than a few\n rarely used so-called Digital Signature Algorithm (DSA) groups. This\n document updates the IKEv2 protocol, RFC 5996.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b","scope_keywords":["6989","algorithm","authentication","http","key","keys","license","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null}],"search_text":"IETF RFC 6989 This document adds a small number of mandatory tests required for the\n secure operation of the Internet Key Exchange Protocol version 2\n (IKEv2) with elliptic curve groups. No change is required to IKE\n implementations that use modular exponential groups, other than a few\n rarely used so-called Digital Signature Algorithm (DSA) groups. This\n document updates the IKEv2 protocol, RFC 5996.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may b 6989 algorithm authentication http key keys license signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6998","type":"specification","body":"IETF","designation":"RFC 6998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6998.txt","https://www.rfc-editor.org/rfc/rfc6998.pdf"],"folder":"IETF/RFC-6998","files":{"txt":{"path":"standards/IETF/RFC-6998/RFC-6998.txt","sha256":"2e6bf3c0c3b3ae26826b9aaf463333c48a11c8ed5c5d714cf33713255ed5a0fe"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism that enables a Routing Protocol\n for Low-power and Lossy Networks (RPL) router to measure the\n aggregated values of given routing metrics along an existing route\n towards another RPL router, thereby allowing the router to decide if\n it wants to initiate the discovery of a better route.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet St","scope_keywords":["6998","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6997","folder":"IETF/RFC-6997","source":"IETF/RFC-6997/RFC-6997.txt","version":null}],"search_text":"IETF RFC 6998 This document specifies a mechanism that enables a Routing Protocol\n for Low-power and Lossy Networks (RPL) router to measure the\n aggregated values of given routing metrics along an existing route\n towards another RPL router, thereby allowing the router to decide if\n it wants to initiate the discovery of a better route.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet St 6998 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7002","type":"specification","body":"IETF","designation":"RFC 7002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7002.txt","https://www.rfc-editor.org/rfc/rfc7002.pdf"],"folder":"IETF/RFC-7002","files":{"txt":{"path":"standards/IETF/RFC-7002/RFC-7002.txt","sha256":"d03ed17512939a850ba75141508783c4e8e33638ae09a765918d813695e35d79"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of a simple discard count metric\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7002.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to B","scope_keywords":["7002","attribute","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 7002 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of a simple discard count metric\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7002.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to B 7002 attribute http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7003","type":"specification","body":"IETF","designation":"RFC 7003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7003.txt","https://www.rfc-editor.org/rfc/rfc7003.pdf"],"folder":"IETF/RFC-7003","files":{"txt":{"path":"standards/IETF/RFC-7003/RFC-7003.txt","sha256":"c7383a888c88cacae1b1aaeb8e713863bb181d460b8a1da8a9bd6ad80827d385"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of burst and gap discard metrics\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7003.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to B","scope_keywords":["7003","algorithm","algorithms","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7097","folder":"IETF/RFC-7097","source":"IETF/RFC-7097/RFC-7097.txt","version":null},{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 7003 This document defines an RTP Control Protocol (RTCP) Extended Report\n (XR) block that allows the reporting of burst and gap discard metrics\n for use in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7003.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to B 7003 algorithm algorithms attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7004","type":"specification","body":"IETF","designation":"RFC 7004","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7004.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7004.txt","https://www.rfc-editor.org/rfc/rfc7004.pdf"],"folder":"IETF/RFC-7004","files":{"txt":{"path":"standards/IETF/RFC-7004/RFC-7004.txt","sha256":"37bee565aeeba724361c7e37c0429215592c4c60a2cfebbdb20c1fdd0cdef7aa"}},"tags":["nested-reference","unchanged"],"summary":"This document defines three RTP Control Protocol (RTCP) Extended\n Report (XR) blocks that allow the reporting of loss, duplication, and\n discard summary statistics metrics in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7004.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This d","scope_keywords":["7004","algorithm","algorithms","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null}],"search_text":"IETF RFC 7004 This document defines three RTP Control Protocol (RTCP) Extended\n Report (XR) blocks that allow the reporting of loss, duplication, and\n discard summary statistics metrics in a range of RTP applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7004.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This d 7004 algorithm algorithms attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7006","type":"specification","body":"IETF","designation":"RFC 7006","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7006.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7006.txt","https://www.rfc-editor.org/rfc/rfc7006.pdf"],"folder":"IETF/RFC-7006","files":{"pdf":{"path":"standards/IETF/RFC-7006/RFC-7006.pdf","sha256":"b795957614bbda2a0fd5610faba69a90f1573f9b190c73d9a2f37eaf4b4755c0"},"txt":{"path":"standards/IETF/RFC-7006/RFC-7006.txt","sha256":"efa91a0079f5a377a00ecc57f5c75b81bdc14272ed515190b8ec38c9aa73c814"}},"tags":["nested-reference","unchanged"],"summary":"The Session Description Protocol (SDP) has been extended with a\n capability negotiation mechanism framework that allows the endpoints\n to negotiate transport protocols and attributes. This framework has\n been extended with a media capabilities negotiation mechanism that\n allows endpoints to negotiate additional media-related capabilities.\n This negotiation is embedded into the widely used SDP offer/answer\n procedures.\n\n This memo extends the SDP capability negotiation framework to allow\n endpoints to negotiate three additional SDP capabilities. In\n particular, this memo provides a mechanism to negotiate bandwidth\n (\"b=\" line), connection data (\"c=\" line), and session or media titles\n (\"i=\" line for each session or media).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the cons","scope_keywords":["7006","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7006 The Session Description Protocol (SDP) has been extended with a\n capability negotiation mechanism framework that allows the endpoints\n to negotiate transport protocols and attributes. This framework has\n been extended with a media capabilities negotiation mechanism that\n allows endpoints to negotiate additional media-related capabilities.\n This negotiation is embedded into the widely used SDP offer/answer\n procedures.\n\n This memo extends the SDP capability negotiation framework to allow\n endpoints to negotiate three additional SDP capabilities. In\n particular, this memo provides a mechanism to negotiate bandwidth\n (\"b=\" line), connection data (\"c=\" line), and session or media titles\n (\"i=\" line for each session or media).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the cons 7006 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7009","type":"specification","body":"IETF","designation":"RFC 7009","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7009.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7009.txt","https://www.rfc-editor.org/rfc/rfc7009.pdf"],"folder":"IETF/RFC-7009","files":{"txt":{"path":"standards/IETF/RFC-7009/RFC-7009.txt","sha256":"b2f346d5a87ba9d7f09047901257a65f7ac0b26352095969c25821afab447829"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an additional endpoint for OAuth authorization\n servers, which allows clients to notify the authorization server that\n a previously obtained refresh or access token is no longer needed.\n This allows the authorization server to clean up security\n credentials. A revocation request will invalidate the actual token\n and, if applicable, other tokens based on the same authorization\n grant.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f","scope_keywords":["7009","authorization","credential","credentials","http","https","key","license","revocation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7662","folder":"IETF/RFC-7662","source":"IETF/RFC-7662/RFC-7662.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null}],"search_text":"IETF RFC 7009 This document proposes an additional endpoint for OAuth authorization\n servers, which allows clients to notify the authorization server that\n a previously obtained refresh or access token is no longer needed.\n This allows the authorization server to clean up security\n credentials. A revocation request will invalidate the actual token\n and, if applicable, other tokens based on the same authorization\n grant.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f 7009 authorization credential credentials http https key license revocation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7012","type":"specification","body":"IETF","designation":"RFC 7012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7012.txt","https://www.rfc-editor.org/rfc/rfc7012.pdf"],"folder":"IETF/RFC-7012","files":{"txt":{"path":"standards/IETF/RFC-7012/RFC-7012.txt","sha256":"85b4f7d66a1de7d29897e12f67d8d67cfdeb8f2eafc6107a46899ddf08fa137f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the data types and management policy for the\n information model for the IP Flow Information Export (IPFIX)\n protocol. This information model is maintained as the IANA \"IPFIX\n Information Elements\" registry, the initial contents of which were\n defined by RFC 5102. This information model is used by the IPFIX\n protocol for encoding measured traffic information and information\n related to the traffic Observation Point, the traffic Metering\n Process, and the Exporting Process. Although this model was\n developed for the IPFIX protocol, it is defined in an open way that\n allows it to be easily used in other protocols, interfaces, and\n applications. This document obsoletes RFC 5102.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communit","scope_keywords":["7012","attribute","attributes","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7012 This document defines the data types and management policy for the\n information model for the IP Flow Information Export (IPFIX)\n protocol. This information model is maintained as the IANA \"IPFIX\n Information Elements\" registry, the initial contents of which were\n defined by RFC 5102. This information model is used by the IPFIX\n protocol for encoding measured traffic information and information\n related to the traffic Observation Point, the traffic Metering\n Process, and the Exporting Process. Although this model was\n developed for the IPFIX protocol, it is defined in an open way that\n allows it to be easily used in other protocols, interfaces, and\n applications. This document obsoletes RFC 5102.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF communit 7012 attribute attributes http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7014","type":"specification","body":"IETF","designation":"RFC 7014","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7014.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7014.txt","https://www.rfc-editor.org/rfc/rfc7014.pdf"],"folder":"IETF/RFC-7014","files":{"txt":{"path":"standards/IETF/RFC-7014/RFC-7014.txt","sha256":"9e6cd03eaa08beeab44d2262c466445b7fd9ce0b045e06fd84988516c241d936"}},"tags":["nested-reference","unchanged"],"summary":"The Intermediate Flow Selection Process is the process of selecting a\n subset of Flows from all observed Flows. The Intermediate Flow\n Selection Process may be located at an IP Flow Information Export\n (IPFIX) Exporter or Collector, or within an IPFIX Mediator. It\n reduces the effort of post-processing Flow data and transferring Flow\n Records. This document describes motivations for using the\n Intermediate Flow Selection process and presents Intermediate Flow\n Selection techniques. It provides an information model for\n configuring Intermediate Flow Selection Process techniques and\n discusses what information about an Intermediate Flow Selection\n Process should be exported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ","scope_keywords":["7014","algorithm","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 7014 The Intermediate Flow Selection Process is the process of selecting a\n subset of Flows from all observed Flows. The Intermediate Flow\n Selection Process may be located at an IP Flow Information Export\n (IPFIX) Exporter or Collector, or within an IPFIX Mediator. It\n reduces the effort of post-processing Flow data and transferring Flow\n Records. This document describes motivations for using the\n Intermediate Flow Selection process and presents Intermediate Flow\n Selection techniques. It provides an information model for\n configuring Intermediate Flow Selection Process techniques and\n discusses what information about an Intermediate Flow Selection\n Process should be exported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received publ 7014 algorithm hash http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7015","type":"specification","body":"IETF","designation":"RFC 7015","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7015.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7015.txt","https://www.rfc-editor.org/rfc/rfc7015.pdf"],"folder":"IETF/RFC-7015","files":{"txt":{"path":"standards/IETF/RFC-7015/RFC-7015.txt","sha256":"749a896b15fca7f7592ec9a817325fd11ed6acacf97e7f915d23a69cc9b052eb"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a common implementation-independent basis for\n the interoperable application of the IP Flow Information Export\n (IPFIX) protocol to the handling of Aggregated Flows, which are IPFIX\n Flows representing packets from multiple Original Flows sharing some\n set of common properties. It does this through a detailed\n terminology and a descriptive Intermediate Aggregation Process\n architecture, including a specification of methods for Original Flow\n counting and counter distribution across intervals.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Se","scope_keywords":["7015","archiving","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null}],"search_text":"IETF RFC 7015 This document provides a common implementation-independent basis for\n the interoperable application of the IP Flow Information Export\n (IPFIX) protocol to the handling of Aggregated Flows, which are IPFIX\n Flows representing packets from multiple Original Flows sharing some\n set of common properties. It does this through a detailed\n terminology and a descriptive Intermediate Aggregation Process\n architecture, including a specification of methods for Original Flow\n counting and counter distribution across intervals.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Se 7015 archiving http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 7029","type":"specification","body":"IETF","designation":"RFC 7029","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7029.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7029.txt","https://www.rfc-editor.org/rfc/rfc7029.pdf"],"folder":"IETF/RFC-7029","files":{"txt":{"path":"standards/IETF/RFC-7029/RFC-7029.txt","sha256":"aef920ca788c76753503d2813d9bd54cdcd4025ac23f6049ab11e4c989af8fe7"}},"tags":["nested-reference","unchanged"],"summary":"As the Extensible Authentication Protocol (EAP) evolves, EAP peers\n rely increasingly on information received from the EAP server. EAP\n extensions such as channel binding or network posture information are\n often carried in tunnel methods; peers are likely to rely on this\n information. Cryptographic binding is a facility described in RFC\n 3748 that protects tunnel methods against man-in-the-middle attacks.\n However, cryptographic binding focuses on protecting the server\n rather than the peer. This memo explores attacks possible when the\n peer is not protected from man-in-the-middle attacks and recommends\n cryptographic binding based on an Extended Master Session Key, a new\n form of cryptographic binding that protects both peer and server\n along with other mitigations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational","scope_keywords":["7029","authentication","certificate","credential","credentials","http","key","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 7029 As the Extensible Authentication Protocol (EAP) evolves, EAP peers\n rely increasingly on information received from the EAP server. EAP\n extensions such as channel binding or network posture information are\n often carried in tunnel methods; peers are likely to rely on this\n information. Cryptographic binding is a facility described in RFC\n 3748 that protects tunnel methods against man-in-the-middle attacks.\n However, cryptographic binding focuses on protecting the server\n rather than the peer. This memo explores attacks possible when the\n peer is not protected from man-in-the-middle attacks and recommends\n cryptographic binding based on an Extended Master Session Key, a new\n form of cryptographic binding that protects both peer and server\n along with other mitigations.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational 7029 authentication certificate credential credentials http key license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7033","type":"specification","body":"IETF","designation":"RFC 7033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7033.txt","https://www.rfc-editor.org/rfc/rfc7033.pdf"],"folder":"IETF/RFC-7033","files":{"txt":{"path":"standards/IETF/RFC-7033/RFC-7033.txt","sha256":"caf47e904bf9e2edbd5612c696926bf55586bb91c9edc9ff8201139dfc503fd3"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the WebFinger protocol, which can be used\n to discover information about people or other entities on the\n Internet using standard HTTP methods. WebFinger discovers\n information for a URI that might not be usable as a locator\n otherwise, such as account or email URIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7033.\n\nCopyright Notice\n\n Copyright (c) 2013 IE","scope_keywords":["7033","attribute","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 7033 This specification defines the WebFinger protocol, which can be used\n to discover information about people or other entities on the\n Internet using standard HTTP methods. WebFinger discovers\n information for a URI that might not be usable as a locator\n otherwise, such as account or email URIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7033.\n\nCopyright Notice\n\n Copyright (c) 2013 IE 7033 attribute http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7045","type":"specification","body":"IETF","designation":"RFC 7045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7045.txt","https://www.rfc-editor.org/rfc/rfc7045.pdf"],"folder":"IETF/RFC-7045","files":{"txt":{"path":"standards/IETF/RFC-7045/RFC-7045.txt","sha256":"8cdddd65d54e86b9714e12294ba0e5f87b1d2c2ba245f0bbadfd1d47ed8c4308"}},"tags":["nested-reference","unchanged"],"summary":"Various IPv6 extension headers have been standardised since the IPv6\n standard was first published. This document updates RFC 2460 to\n clarify how intermediate nodes should deal with such extension\n headers and with any that are defined in the future. It also\n specifies how extension headers should be registered by IANA, with a\n corresponding minor update to RFC 2780.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:","scope_keywords":["7045","delivery","http","license","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7112","folder":"IETF/RFC-7112","source":"IETF/RFC-7112/RFC-7112.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 7045 Various IPv6 extension headers have been standardised since the IPv6\n standard was first published. This document updates RFC 2460 to\n clarify how intermediate nodes should deal with such extension\n headers and with any that are defined in the future. It also\n specifies how extension headers should be registered by IANA, with a\n corresponding minor update to RFC 2780.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http: 7045 delivery http license path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7053","type":"specification","body":"IETF","designation":"RFC 7053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7053.txt","https://www.rfc-editor.org/rfc/rfc7053.pdf"],"folder":"IETF/RFC-7053","files":{"txt":{"path":"standards/IETF/RFC-7053/RFC-7053.txt","sha256":"6d44b0dc5630e49dca60249d1e1465b879abf255130374e9c5481967039fde4e"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 4960 by defining a method for the sender of\n a DATA chunk to indicate that the corresponding Selective\n Acknowledgment (SACK) chunk should be sent back immediately and\n should not be delayed. It is done by specifying a bit in the DATA\n chunk header, called the (I)mmediate bit, which can get set by either\n the Stream Control Transmission Protocol (SCTP) implementation or the\n application using an SCTP stack. Since unknown flags in chunk\n headers are ignored by SCTP implementations, this extension does not\n introduce any interoperability problems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furt","scope_keywords":["7053","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null}],"search_text":"IETF RFC 7053 This document updates RFC 4960 by defining a method for the sender of\n a DATA chunk to indicate that the corresponding Selective\n Acknowledgment (SACK) chunk should be sent back immediately and\n should not be delayed. It is done by specifying a bit in the DATA\n chunk header, called the (I)mmediate bit, which can get set by either\n the Stream Control Transmission Protocol (SCTP) implementation or the\n application using an SCTP stack. Since unknown flags in chunk\n headers are ignored by SCTP implementations, this extension does not\n introduce any interoperability problems.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furt 7053 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7064","type":"specification","body":"IETF","designation":"RFC 7064","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7064.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7064.txt","https://www.rfc-editor.org/rfc/rfc7064.pdf"],"folder":"IETF/RFC-7064","files":{"txt":{"path":"standards/IETF/RFC-7064/RFC-7064.txt","sha256":"f5a7aedad4a717ede4e90d568817f0e7682a7e6be2c9bd3788d31eae4a761412"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax and semantics of the Uniform\n Resource Identifier (URI) scheme for the Session Traversal Utilities\n for NAT (STUN) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7064.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Tr","scope_keywords":["7064","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 7064 This document specifies the syntax and semantics of the Uniform\n Resource Identifier (URI) scheme for the Session Traversal Utilities\n for NAT (STUN) protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7064.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Tr 7064 http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7065","type":"specification","body":"IETF","designation":"RFC 7065","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7065.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7065.txt","https://www.rfc-editor.org/rfc/rfc7065.pdf"],"folder":"IETF/RFC-7065","files":{"txt":{"path":"standards/IETF/RFC-7065/RFC-7065.txt","sha256":"964f112bacbd32c3167a4947f460ef778e1b4761b39f4b0d2852b29c3d6c43ff"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the syntax of Uniform Resource Identifier\n (URI) schemes for the Traversal Using Relays around NAT (TURN)\n protocol. It defines two URI schemes to provision the TURN\n Resolution Mechanism (RFC 5928).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7065.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All right","scope_keywords":["7065","algorithm","authentication","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7350","folder":"IETF/RFC-7350","source":"IETF/RFC-7350/RFC-7350.txt","version":null}],"search_text":"IETF RFC 7065 This document specifies the syntax of Uniform Resource Identifier\n (URI) schemes for the Traversal Using Relays around NAT (TURN)\n protocol. It defines two URI schemes to provision the TURN\n Resolution Mechanism (RFC 5928).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7065.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All right 7065 algorithm authentication http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7073","type":"specification","body":"IETF","designation":"RFC 7073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7073.txt","https://www.rfc-editor.org/rfc/rfc7073.pdf"],"folder":"IETF/RFC-7073","files":{"txt":{"path":"standards/IETF/RFC-7073/RFC-7073.txt","sha256":"47a2755602d4c8a2bccd484f81db62fc0e228a00f60d775e9a91a08ae4024bf1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a response set for describing assertions a\n reputation service provider can make about email identifiers, for use\n in generating reputons.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7073.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF T","scope_keywords":["7073","delivery","http","key","keys","license","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7070","folder":"IETF/RFC-7070","source":"IETF/RFC-7070/RFC-7070.txt","version":null},{"body":"IETF","designation":"RFC 7071","folder":"IETF/RFC-7071","source":"IETF/RFC-7071/RFC-7071.txt","version":null}],"search_text":"IETF RFC 7073 This document defines a response set for describing assertions a\n reputation service provider can make about email identifiers, for use\n in generating reputons.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7073.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF T 7073 delivery http key keys license signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7078","type":"specification","body":"IETF","designation":"RFC 7078","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7078.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7078.txt","https://www.rfc-editor.org/rfc/rfc7078.pdf"],"folder":"IETF/RFC-7078","files":{"txt":{"path":"standards/IETF/RFC-7078/RFC-7078.txt","sha256":"35ff3cbc4c731a9f6ae6bb5ea5e165b34cb1770068af9551d4e8f2b7bee20bc1"}},"tags":["nested-reference","unchanged"],"summary":"RFC 6724 defines default address selection mechanisms for IPv6 that\n allow nodes to select an appropriate address when faced with multiple\n source and/or destination addresses to choose between. RFC 6724\n allows for the future definition of methods to administratively\n configure the address selection policy information. This document\n defines a new DHCPv6 option for such configuration, allowing a site\n administrator to distribute address selection policy overriding the\n default address selection parameters and policy table, and thus\n allowing the administrator to control the address selection behavior\n of nodes in their site.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication ","scope_keywords":["7078","algorithm","algorithms","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 7078 RFC 6724 defines default address selection mechanisms for IPv6 that\n allow nodes to select an appropriate address when faced with multiple\n source and/or destination addresses to choose between. RFC 6724\n allows for the future definition of methods to administratively\n configure the address selection policy information. This document\n defines a new DHCPv6 option for such configuration, allowing a site\n administrator to distribute address selection policy overriding the\n default address selection parameters and policy table, and thus\n allowing the administrator to control the address selection behavior\n of nodes in their site.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication  7078 algorithm algorithms http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7083","type":"specification","body":"IETF","designation":"RFC 7083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7083.txt","https://www.rfc-editor.org/rfc/rfc7083.pdf"],"folder":"IETF/RFC-7083","files":{"txt":{"path":"standards/IETF/RFC-7083/RFC-7083.txt","sha256":"d59892cf8a5f6f5f16757f1999e087fe0f5a89fa72b9d465cf7d0713ed8c0ae6"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3315 by redefining the default values for\n SOL_MAX_RT and INF_MAX_RT and defining options through which a DHCPv6\n server can override the client's default value for SOL_MAX_RT and\n INF_MAX_RT with new values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7083.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors","scope_keywords":["7083","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7083 This document updates RFC 3315 by redefining the default values for\n SOL_MAX_RT and INF_MAX_RT and defining options through which a DHCPv6\n server can override the client's default value for SOL_MAX_RT and\n INF_MAX_RT with new values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7083.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors 7083 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7088","type":"specification","body":"IETF","designation":"RFC 7088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7088.txt","https://www.rfc-editor.org/rfc/rfc7088.pdf"],"folder":"IETF/RFC-7088","files":{"txt":{"path":"standards/IETF/RFC-7088/RFC-7088.txt","sha256":"8eebd0640de52345ea0e5aea49c4ad81be7d72231449f311038917514ed9fb0c"}},"tags":["nested-reference","unchanged"],"summary":"\"Music on hold\" is one of the features of telephone systems that is\n most desired by buyers of business telephone systems. Music on hold\n means that when one party to a call has the call \"on hold\", that\n party's telephone provides an audio stream (often music) to be heard\n by the other party. Architectural features of SIP make it difficult\n to implement music on hold in a way that is fully standards-\n compliant. The implementation of music on hold described in this\n document is fully effective, is standards-compliant, and has a number\n of advantages over the methods previously documented. In particular,\n it is less likely to produce peculiar user interface effects and more\n likely to work in systems that perform authentication than the music-\n on-hold method described in Section 2.3 of RFC 5359.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n","scope_keywords":["7088","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 7088 \"Music on hold\" is one of the features of telephone systems that is\n most desired by buyers of business telephone systems. Music on hold\n means that when one party to a call has the call \"on hold\", that\n party's telephone provides an audio stream (often music) to be heard\n by the other party. Architectural features of SIP make it difficult\n to implement music on hold in a way that is fully standards-\n compliant. The implementation of music on hold described in this\n document is fully effective, is standards-compliant, and has a number\n of advantages over the methods previously documented. In particular,\n it is less likely to produce peculiar user interface effects and more\n likely to work in systems that perform authentication than the music-\n on-hold method described in Section 2.3 of RFC 5359.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n 7088 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7095","type":"specification","body":"IETF","designation":"RFC 7095","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7095.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7095.txt","https://www.rfc-editor.org/rfc/rfc7095.pdf"],"folder":"IETF/RFC-7095","files":{"txt":{"path":"standards/IETF/RFC-7095/RFC-7095.txt","sha256":"4aa8dc8a1673edb4104fae4a71f3721e73e15defd1dec7b79d9ea0067c22bfd2"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines \"jCard\", a JSON format for vCard data.\n The vCard data format is a text format for representing and\n exchanging information about individuals and other entities, for\n example, telephone numbers, email addresses, structured names, and\n delivery addresses. JSON is a lightweight, text-based, language-\n independent data interchange format commonly used in Internet\n applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedba","scope_keywords":["7095","delivery","http","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 7095 This specification defines \"jCard\", a JSON format for vCard data.\n The vCard data format is a text format for representing and\n exchanging information about individuals and other entities, for\n example, telephone numbers, email addresses, structured names, and\n delivery addresses. JSON is a lightweight, text-based, language-\n independent data interchange format commonly used in Internet\n applications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedba 7095 delivery http key license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7097","type":"specification","body":"IETF","designation":"RFC 7097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7097.txt","https://www.rfc-editor.org/rfc/rfc7097.pdf"],"folder":"IETF/RFC-7097","files":{"txt":{"path":"standards/IETF/RFC-7097/RFC-7097.txt","sha256":"0a2f4f18d27beafcdf3a08bdbbe7b9f9293861c35feae16aadfbad5fdf3e1a06"}},"tags":["nested-reference","unchanged"],"summary":"The RTP Control Protocol (RTCP) is used in conjunction with the Real-\n time Transport Protocol (RTP) in order to provide a variety of short-\n term and long-term reception statistics. The available reporting may\n include aggregate information across longer periods of time as well\n as individual packet reporting. This document specifies a per-packet\n report metric capturing individual packets discarded from the de-\n jitter buffer after successful reception.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status o","scope_keywords":["7097","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null}],"search_text":"IETF RFC 7097 The RTP Control Protocol (RTCP) is used in conjunction with the Real-\n time Transport Protocol (RTP) in order to provide a variety of short-\n term and long-term reception statistics. The available reporting may\n include aggregate information across longer periods of time as well\n as individual packet reporting. This document specifies a per-packet\n report metric capturing individual packets discarded from the de-\n jitter buffer after successful reception.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status o 7097 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7104","type":"specification","body":"IETF","designation":"RFC 7104","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7104.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7104.txt","https://www.rfc-editor.org/rfc/rfc7104.pdf"],"folder":"IETF/RFC-7104","files":{"txt":{"path":"standards/IETF/RFC-7104/RFC-7104.txt","sha256":"7d412573358f36d7c63a3c7e7353fbd674ff9505888b4f318c99fe5f971638f2"}},"tags":["nested-reference","unchanged"],"summary":"Packet loss is undesirable for real-time multimedia sessions, but it\n can occur due to congestion or other unplanned network outages. This\n is especially true for IP multicast networks, where packet loss\n patterns can vary greatly between receivers. One technique that can\n be used to recover from packet loss without incurring unbounded delay\n for all the receivers is to duplicate the packets and send them in\n separate redundant streams. This document defines the semantics for\n grouping redundant streams in the Session Description Protocol (SDP).\n The semantics defined in this document are to be used with the SDP\n Grouping Framework. Grouping semantics at the Synchronization Source\n (SSRC) level are also defined in this document for RTP streams using\n SSRC multiplexing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engine","scope_keywords":["7104","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7104 Packet loss is undesirable for real-time multimedia sessions, but it\n can occur due to congestion or other unplanned network outages. This\n is especially true for IP multicast networks, where packet loss\n patterns can vary greatly between receivers. One technique that can\n be used to recover from packet loss without incurring unbounded delay\n for all the receivers is to duplicate the packets and send them in\n separate redundant streams. This document defines the semantics for\n grouping redundant streams in the Session Description Protocol (SDP).\n The semantics defined in this document are to be used with the SDP\n Grouping Framework. Grouping semantics at the Synchronization Source\n (SSRC) level are also defined in this document for RTP streams using\n SSRC multiplexing.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engine 7104 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7141","type":"specification","body":"IETF","designation":"RFC 7141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7141.txt","https://www.rfc-editor.org/rfc/rfc7141.pdf"],"folder":"IETF/RFC-7141","files":{"txt":{"path":"standards/IETF/RFC-7141/RFC-7141.txt","sha256":"d78f3f7d15b4154dc6d15b31634dc7b4d1df33ae0f00d6e766698fca77a41014"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations of best current practice for\n dropping or marking packets using any active queue management (AQM)\n algorithm, including Random Early Detection (RED), BLUE, Pre-\n Congestion Notification (PCN), and newer schemes such as CoDel\n (Controlled Delay) and PIE (Proportional Integral controller\n Enhanced). We give three strong recommendations: (1) packet size\n should be taken into account when transports detect and respond to\n congestion indications, (2) packet size should not be taken into\n account when network equipment creates congestion signals (marking,\n dropping), and therefore (3) in the specific case of RED, the byte-\n mode packet drop variant that drops fewer small packets should not be\n used. This memo updates RFC 2309 to deprecate deliberate\n preferential treatment of small packets in AQM algorithms.\n\nStatus of This Memo\n\n This memo documents an I","scope_keywords":["7141","algorithm","algorithms","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 7806","folder":"IETF/RFC-7806","source":"IETF/RFC-7806/RFC-7806.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null}],"search_text":"IETF RFC 7141 This document provides recommendations of best current practice for\n dropping or marking packets using any active queue management (AQM)\n algorithm, including Random Early Detection (RED), BLUE, Pre-\n Congestion Notification (PCN), and newer schemes such as CoDel\n (Controlled Delay) and PIE (Proportional Integral controller\n Enhanced). We give three strong recommendations: (1) packet size\n should be taken into account when transports detect and respond to\n congestion indications, (2) packet size should not be taken into\n account when network equipment creates congestion signals (marking,\n dropping), and therefore (3) in the specific case of RED, the byte-\n mode packet drop variant that drops fewer small packets should not be\n used. This memo updates RFC 2309 to deprecate deliberate\n preferential treatment of small packets in AQM algorithms.\n\nStatus of This Memo\n\n This memo documents an I 7141 algorithm algorithms http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7144","type":"specification","body":"IETF","designation":"RFC 7144","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7144.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7144.txt","https://www.rfc-editor.org/rfc/rfc7144.pdf"],"folder":"IETF/RFC-7144","files":{"txt":{"path":"standards/IETF/RFC-7144/RFC-7144.txt","sha256":"d6884a14e5a6d2c0a2a24a169563c2ecff0b2860dc7ff3bac8d06f1791076b84"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol that maps the SCSI family of protocols onto\n TCP/IP. The iSCSI protocol as specified in RFC 7143 (and as\n previously specified by the combination of RFC 3720 and RFC\n 5048) is based on the SAM-2 (SCSI Architecture Model - 2)\n version of the SCSI family of protocols. This document\n defines enhancements to the iSCSI protocol to support certain\n additional features of the SCSI protocol that were defined in\n SAM-3, SAM-4, and SAM-5.\n\n This document is a companion document to RFC 7143.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n informat","scope_keywords":["7144","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null}],"search_text":"IETF RFC 7144 Internet Small Computer System Interface (iSCSI) is a SCSI\n transport protocol that maps the SCSI family of protocols onto\n TCP/IP. The iSCSI protocol as specified in RFC 7143 (and as\n previously specified by the combination of RFC 3720 and RFC\n 5048) is based on the SAM-2 (SCSI Architecture Model - 2)\n version of the SCSI family of protocols. This document\n defines enhancements to the iSCSI protocol to support certain\n additional features of the SCSI protocol that were defined in\n SAM-3, SAM-4, and SAM-5.\n\n This document is a companion document to RFC 7143.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n informat 7144 http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7145","type":"specification","body":"IETF","designation":"RFC 7145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7145.txt","https://www.rfc-editor.org/rfc/rfc7145.pdf"],"folder":"IETF/RFC-7145","files":{"txt":{"path":"standards/IETF/RFC-7145/RFC-7145.txt","sha256":"2db1d87df8be0c3a98b09d9450cc1e3906c32ace426c6b6359d23eb31eca5e27"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer System Interface (iSCSI) Extensions for\n Remote Direct Memory Access (RDMA) provides the RDMA data transfer\n capability to iSCSI by layering iSCSI on top of an RDMA-Capable\n Protocol. An RDMA-Capable Protocol provides RDMA Read and Write\n services, which enable data to be transferred directly into SCSI I/O\n Buffers without intermediate data copies. This document describes\n the extensions to the iSCSI protocol to support RDMA services as\n provided by an RDMA-Capable Protocol.\n\n This document obsoletes RFC 5046.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards","scope_keywords":["7145","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 7145 Internet Small Computer System Interface (iSCSI) Extensions for\n Remote Direct Memory Access (RDMA) provides the RDMA data transfer\n capability to iSCSI by layering iSCSI on top of an RDMA-Capable\n Protocol. An RDMA-Capable Protocol provides RDMA Read and Write\n services, which enable data to be transferred directly into SCSI I/O\n Buffers without intermediate data copies. This document describes\n the extensions to the iSCSI protocol to support RDMA services as\n provided by an RDMA-Capable Protocol.\n\n This document obsoletes RFC 5046.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards 7145 http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7146","type":"specification","body":"IETF","designation":"RFC 7146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7146.txt","https://www.rfc-editor.org/rfc/rfc7146.pdf"],"folder":"IETF/RFC-7146","files":{"txt":{"path":"standards/IETF/RFC-7146/RFC-7146.txt","sha256":"0c673127ef0818f7f366ff51f20fd84d3fa4d12ec8cd7fb187c311785a0b4539"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3723 specifies IPsec requirements for block storage protocols\n over IP (e.g., Internet Small Computer System Interface (iSCSI))\n based on IPsec v2 (RFC 2401 and related RFCs); those requirements\n have subsequently been applied to remote direct data placement\n protocols, e.g., the Remote Direct Memory Access Protocol (RDMAP).\n This document updates RFC 3723's IPsec requirements to IPsec v3 (RFC\n 4301 and related RFCs) and makes some changes to required algorithms\n based on developments in cryptography since RFC 3723 was published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards","scope_keywords":["7146","algorithm","algorithms","authentication","certificate","certificates","crl","encryption","http","key","keys","license","ocsp","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7146 RFC 3723 specifies IPsec requirements for block storage protocols\n over IP (e.g., Internet Small Computer System Interface (iSCSI))\n based on IPsec v2 (RFC 2401 and related RFCs); those requirements\n have subsequently been applied to remote direct data placement\n protocols, e.g., the Remote Direct Memory Access Protocol (RDMAP).\n This document updates RFC 3723's IPsec requirements to IPsec v3 (RFC\n 4301 and related RFCs) and makes some changes to required algorithms\n based on developments in cryptography since RFC 3723 was published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards 7146 algorithm algorithms authentication certificate certificates crl encryption http key keys license ocsp revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 7156","type":"specification","body":"IETF","designation":"RFC 7156","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7156.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7156.txt","https://www.rfc-editor.org/rfc/rfc7156.pdf"],"folder":"IETF/RFC-7156","files":{"txt":{"path":"standards/IETF/RFC-7156/RFC-7156.txt","sha256":"9766c64af6e62740086922064b4ded868c79272a315c47ff1100976666e665c5"}},"tags":["nested-reference","unchanged"],"summary":"In Proxy Mobile IPv6, packets received from a Mobile Node (MN) by the\n Mobile Access Gateway (MAG) to which it is attached are typically\n tunneled to a Local Mobility Anchor (LMA) for routing. The term\n \"localized routing\" refers to a method by which packets are routed\n directly between an MN's MAG and the MAG of its Correspondent Node\n (CN) without involving any LMA. In a Proxy Mobile IPv6 deployment,\n it may be desirable to control the establishment of localized routing\n sessions between two MAGs in a Proxy Mobile IPv6 domain by requiring\n that the session be authorized. This document specifies how to\n accomplish this using the Diameter protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been ap","scope_keywords":["7156","attribute","authentication","authorization","delivery","http","key","license","path","policy","profile","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null}],"search_text":"IETF RFC 7156 In Proxy Mobile IPv6, packets received from a Mobile Node (MN) by the\n Mobile Access Gateway (MAG) to which it is attached are typically\n tunneled to a Local Mobility Anchor (LMA) for routing. The term\n \"localized routing\" refers to a method by which packets are routed\n directly between an MN's MAG and the MAG of its Correspondent Node\n (CN) without involving any LMA. In a Proxy Mobile IPv6 deployment,\n it may be desirable to control the establishment of localized routing\n sessions between two MAGs in a Proxy Mobile IPv6 domain by requiring\n that the session be authorized. This document specifies how to\n accomplish this using the Diameter protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been ap 7156 attribute authentication authorization delivery http key license path policy profile registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7160","type":"specification","body":"IETF","designation":"RFC 7160","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7160.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7160.txt","https://www.rfc-editor.org/rfc/rfc7160.pdf"],"folder":"IETF/RFC-7160","files":{"txt":{"path":"standards/IETF/RFC-7160/RFC-7160.txt","sha256":"cd783041da4465f54e2ba5599e4d9dce8d6aa776021b6f0d803961f4acc07b59"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies the RTP specification regarding the use of\n different clock rates in an RTP session. It also provides guidance\n on how legacy RTP implementations that use multiple clock rates can\n interoperate with RTP implementations that use the algorithm\n described in this document. It updates RFC 3550.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7160.\n\nCopyright Notice\n\n ","scope_keywords":["7160","algorithm","algorithms","http","key","license","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null}],"search_text":"IETF RFC 7160 This document clarifies the RTP specification regarding the use of\n different clock rates in an RTP session. It also provides guidance\n on how legacy RTP implementations that use multiple clock rates can\n interoperate with RTP implementations that use the algorithm\n described in this document. It updates RFC 3550.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7160.\n\nCopyright Notice\n\n  7160 algorithm algorithms http key license subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7162","type":"specification","body":"IETF","designation":"RFC 7162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7162.txt","https://www.rfc-editor.org/rfc/rfc7162.pdf"],"folder":"IETF/RFC-7162","files":{"txt":{"path":"standards/IETF/RFC-7162/RFC-7162.txt","sha256":"7a393f4e9fc75e972cfcc4a921d51f1a0f4a186d15ef91577a14c939d010c3f6"}},"tags":["nested-reference","unchanged"],"summary":"Often, multiple IMAP (RFC 3501) clients need to coordinate changes to\n a common IMAP mailbox. Examples include different clients working on\n behalf of the same user and multiple users accessing shared\n mailboxes. These clients need a mechanism to efficiently synchronize\n state changes for messages within the mailbox.\n\n Initially defined in RFC 4551, the Conditional Store facility\n provides a protected update mechanism for message state information\n and a mechanism for requesting only changes to the message state.\n This memo updates that mechanism and obsoletes RFC 4551, based on\n operational experience.\n\n This document additionally updates another IMAP extension, Quick\n Resynchronization, which builds on the Conditional STORE extension to\n provide an IMAP client the ability to fully resynchronize a mailbox\n as part of the SELECT/EXAMINE command, without the need for\n additional server-si","scope_keywords":["7162","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 7162 Often, multiple IMAP (RFC 3501) clients need to coordinate changes to\n a common IMAP mailbox. Examples include different clients working on\n behalf of the same user and multiple users accessing shared\n mailboxes. These clients need a mechanism to efficiently synchronize\n state changes for messages within the mailbox.\n\n Initially defined in RFC 4551, the Conditional Store facility\n provides a protected update mechanism for message state information\n and a mechanism for requesting only changes to the message state.\n This memo updates that mechanism and obsoletes RFC 4551, based on\n operational experience.\n\n This document additionally updates another IMAP extension, Quick\n Resynchronization, which builds on the Conditional STORE extension to\n provide an IMAP client the ability to fully resynchronize a mailbox\n as part of the SELECT/EXAMINE command, without the need for\n additional server-si 7162 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7171","type":"specification","body":"IETF","designation":"RFC 7171","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7171.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7171.txt","https://www.rfc-editor.org/rfc/rfc7171.pdf"],"folder":"IETF/RFC-7171","files":{"txt":{"path":"standards/IETF/RFC-7171/RFC-7171.txt","sha256":"dc78c5cd1728b6181e246b456955041fe4dbbcb40b4db2e4c94054d974cc0ebf"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies PT-EAP, a Posture Transport (PT) protocol\n based on the Extensible Authentication Protocol (EAP) and designed to\n be used only inside an EAP tunnel method protected by Transport Layer\n Security (TLS). The document also describes the intended\n applicability of PT-EAP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7171.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF ","scope_keywords":["7171","attribute","attributes","authentication","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 7171 This document specifies PT-EAP, a Posture Transport (PT) protocol\n based on the Extensible Authentication Protocol (EAP) and designed to\n be used only inside an EAP tunnel method protected by Transport Layer\n Security (TLS). The document also describes the intended\n applicability of PT-EAP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7171.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF  7171 attribute attributes authentication http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7179","type":"specification","body":"IETF","designation":"RFC 7179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7179.txt","https://www.rfc-editor.org/rfc/rfc7179.pdf"],"folder":"IETF/RFC-7179","files":{"txt":{"path":"standards/IETF/RFC-7179/RFC-7179.txt","sha256":"b696e3699bc8f35721872f242bdb05de648cba003753f2d87a6db6dd7d0e798f"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Transparent Interconnection of Lots of Links (TRILL) base\n protocol (RFC 6325) specifies minimal hooks to safely support TRILL\n Header extensions. This document specifies an initial extension\n providing additional flag bits and specifies some of those bits. It\n updates RFC 6325.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7179.\n\nEastlake, et al. Standards Track [Page 1]\n\f\nRF","scope_keywords":["7179","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"IETF RFC 7179 The IETF Transparent Interconnection of Lots of Links (TRILL) base\n protocol (RFC 6325) specifies minimal hooks to safely support TRILL\n Header extensions. This document specifies an initial extension\n providing additional flag bits and specifies some of those bits. It\n updates RFC 6325.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7179.\n\nEastlake, et al. Standards Track [Page 1]\n\f\nRF 7179 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7181","type":"specification","body":"IETF","designation":"RFC 7181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7181.txt","https://www.rfc-editor.org/rfc/rfc7181.pdf"],"folder":"IETF/RFC-7181","files":{"txt":{"path":"standards/IETF/RFC-7181/RFC-7181.txt","sha256":"a5eaa55facce5496a0aabf1dc583fc69d831b93c95bba56114922ebd40a197fc"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes version 2 of the Optimized Link State\n Routing Protocol (OLSRv2) for Mobile Ad Hoc Networks (MANETs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7181.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relat","scope_keywords":["7181","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7182","folder":"IETF/RFC-7182","source":"IETF/RFC-7182/RFC-7182.txt","version":null},{"body":"IETF","designation":"RFC 7183","folder":"IETF/RFC-7183","source":"IETF/RFC-7183/RFC-7183.txt","version":null},{"body":"IETF","designation":"RFC 7548","folder":"IETF/RFC-7548","source":"IETF/RFC-7548/RFC-7548.txt","version":null}],"search_text":"IETF RFC 7181 This specification describes version 2 of the Optimized Link State\n Routing Protocol (OLSRv2) for Mobile Ad Hoc Networks (MANETs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7181.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relat 7181 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7183","type":"specification","body":"IETF","designation":"RFC 7183","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7183.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7183.txt","https://www.rfc-editor.org/rfc/rfc7183.pdf"],"folder":"IETF/RFC-7183","files":{"txt":{"path":"standards/IETF/RFC-7183/RFC-7183.txt","sha256":"8279d878ba11726d4b1fd9ff770a2d1ca70234568b8764d20da6f80cd8761534"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies integrity and replay protection for the\n Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)\n and the Optimized Link State Routing Protocol version 2 (OLSRv2).\n This protection is achieved by using an HMAC-SHA-256 Integrity Check\n Value (ICV) TLV and a Timestamp TLV based on Portable Operating\n System Interface (POSIX) time.\n\n The mechanism in this specification can also be used for other\n protocols that use the generalized packet/message format described in\n RFC 5444.\n\n This document updates RFC 6130 and RFC 7181 by mandating the\n implementation of this integrity and replay protection in NHDP and\n OLSRv2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr","scope_keywords":["7183","http","license","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null}],"search_text":"IETF RFC 7183 This document specifies integrity and replay protection for the\n Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)\n and the Optimized Link State Routing Protocol version 2 (OLSRv2).\n This protection is achieved by using an HMAC-SHA-256 Integrity Check\n Value (ICV) TLV and a Timestamp TLV based on Portable Operating\n System Interface (POSIX) time.\n\n The mechanism in this specification can also be used for other\n protocols that use the generalized packet/message format described in\n RFC 5444.\n\n This document updates RFC 6130 and RFC 7181 by mandating the\n implementation of this integrity and replay protection in NHDP and\n OLSRv2.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appr 7183 http license subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7195","type":"specification","body":"IETF","designation":"RFC 7195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7195.txt","https://www.rfc-editor.org/rfc/rfc7195.pdf"],"folder":"IETF/RFC-7195","files":{"txt":{"path":"standards/IETF/RFC-7195/RFC-7195.txt","sha256":"b3aa1cbc21f6d82be2c7a076cba8380fd7f20b23c5575ef5bc525d40eee86afe"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes use cases, requirements, and protocol extensions\n for using the Session Description Protocol (SDP) offer/answer model\n for establishing audio and video media streams over circuit-switched\n bearers in the Public Switched Telephone Network (PSTN).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7195.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons iden","scope_keywords":["7195","attribute","http","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 7195 This memo describes use cases, requirements, and protocol extensions\n for using the Session Description Protocol (SDP) offer/answer model\n for establishing audio and video media streams over circuit-switched\n bearers in the Public Switched Telephone Network (PSTN).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7195.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons iden 7195 attribute http license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7197","type":"specification","body":"IETF","designation":"RFC 7197","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7197.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7197.txt","https://www.rfc-editor.org/rfc/rfc7197.pdf"],"folder":"IETF/RFC-7197","files":{"txt":{"path":"standards/IETF/RFC-7197/RFC-7197.txt","sha256":"5e4522bfbd739ec02df847992c8fcc01e5706852aea4c4aab3db36e43f2b97bc"}},"tags":["nested-reference","unchanged"],"summary":"A straightforward approach to provide protection against packet\n losses due to network outages with a longest duration of T time units\n is to duplicate the original packets and send each copy separated in\n time by at least T time units. This approach is commonly referred to\n as \"time-shifted redundancy\", \"temporal redundancy\", or simply\n \"delayed duplication\". This document defines an attribute to\n indicate the presence of temporally redundant media streams and the\n duplication delay in the Session Description Protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available ","scope_keywords":["7197","attribute","attributes","delivery","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7198","folder":"IETF/RFC-7198","source":"IETF/RFC-7198/RFC-7198.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7197 A straightforward approach to provide protection against packet\n losses due to network outages with a longest duration of T time units\n is to duplicate the original packets and send each copy separated in\n time by at least T time units. This approach is commonly referred to\n as \"time-shifted redundancy\", \"temporal redundancy\", or simply\n \"delayed duplication\". This document defines an attribute to\n indicate the presence of temporally redundant media streams and the\n duplication delay in the Session Description Protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available  7197 attribute attributes delivery http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7198","type":"specification","body":"IETF","designation":"RFC 7198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7198.txt","https://www.rfc-editor.org/rfc/rfc7198.pdf"],"folder":"IETF/RFC-7198","files":{"txt":{"path":"standards/IETF/RFC-7198/RFC-7198.txt","sha256":"8e165bff694f8bb7f5f7e596fe9b6acea2e361fe12b159a13e6c20e2e94c7954"}},"tags":["nested-reference","unchanged"],"summary":"Packet loss is undesirable for real-time multimedia sessions but can\n occur due to a variety of reasons including unplanned network\n outages. In unicast transmissions, recovering from such an outage\n can be difficult depending on the outage duration, due to the\n potentially large number of missing packets. In multicast\n transmissions, recovery is even more challenging as many receivers\n could be impacted by the outage. For this challenge, one solution\n that does not incur unbounded delay is to duplicate the packets and\n send them in separate redundant streams, provided that the underlying\n network satisfies certain requirements. This document explains how\n Real-time Transport Protocol (RTP) streams can be duplicated without\n breaking RTP or RTP Control Protocol (RTCP) rules.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet ","scope_keywords":["7198","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null}],"search_text":"IETF RFC 7198 Packet loss is undesirable for real-time multimedia sessions but can\n occur due to a variety of reasons including unplanned network\n outages. In unicast transmissions, recovering from such an outage\n can be difficult depending on the outage duration, due to the\n potentially large number of missing packets. In multicast\n transmissions, recovery is even more challenging as many receivers\n could be impacted by the outage. For this challenge, one solution\n that does not incur unbounded delay is to duplicate the packets and\n send them in separate redundant streams, provided that the underlying\n network satisfies certain requirements. This document explains how\n Real-time Transport Protocol (RTP) streams can be duplicated without\n breaking RTP or RTP Control Protocol (RTCP) rules.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet  7198 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7203","type":"specification","body":"IETF","designation":"RFC 7203","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7203.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7203.txt","https://www.rfc-editor.org/rfc/rfc7203.pdf"],"folder":"IETF/RFC-7203","files":{"txt":{"path":"standards/IETF/RFC-7203/RFC-7203.txt","sha256":"b9094c1feca0e74b8c663e94a9f8ad5128983c0232eac82374628837abc04214"}},"tags":["nested-reference","unchanged"],"summary":"This document extends the Incident Object Description Exchange Format\n (IODEF) defined in RFC 5070 to exchange enriched cybersecurity\n information among security experts at organizations and facilitate\n their operations. It provides a well-defined pattern to consistently\n embed structured information, such as identifier- and XML-based\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org","scope_keywords":["7203","hash","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8134","folder":"IETF/RFC-8134","source":"IETF/RFC-8134/RFC-8134.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null}],"search_text":"IETF RFC 7203 This document extends the Incident Object Description Exchange Format\n (IODEF) defined in RFC 5070 to exchange enriched cybersecurity\n information among security experts at organizations and facilitate\n their operations. It provides a well-defined pattern to consistently\n embed structured information, such as identifier- and XML-based\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org 7203 hash http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7209","type":"specification","body":"IETF","designation":"RFC 7209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7209.txt","https://www.rfc-editor.org/rfc/rfc7209.pdf"],"folder":"IETF/RFC-7209","files":{"txt":{"path":"standards/IETF/RFC-7209/RFC-7209.txt","sha256":"3eea8903e150436115b4c2d669b1deff1938090013df449340e2340cb9c24b46"}},"tags":["nested-reference","unchanged"],"summary":"The widespread adoption of Ethernet L2VPN services and the advent of\n new applications for the technology (e.g., data center interconnect)\n have culminated in a new set of requirements that are not readily\n addressable by the current Virtual Private LAN Service (VPLS)\n solution. In particular, multihoming with all-active forwarding is\n not supported, and there's no existing solution to leverage\n Multipoint-to-Multipoint (MP2MP) Label Switched Paths (LSPs) for\n optimizing the delivery of multi-destination frames. Furthermore,\n the provisioning of VPLS, even in the context of BGP-based auto-\n discovery, requires network operators to specify various network\n parameters on top of the access configuration. This document\n specifies the requirements for an Ethernet VPN (EVPN) solution, which\n addresses the above issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track spe","scope_keywords":["7209","delivery","driving","http","license","path","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 7209 The widespread adoption of Ethernet L2VPN services and the advent of\n new applications for the technology (e.g., data center interconnect)\n have culminated in a new set of requirements that are not readily\n addressable by the current Virtual Private LAN Service (VPLS)\n solution. In particular, multihoming with all-active forwarding is\n not supported, and there's no existing solution to leverage\n Multipoint-to-Multipoint (MP2MP) Label Switched Paths (LSPs) for\n optimizing the delivery of multi-destination frames. Furthermore,\n the provisioning of VPLS, even in the context of BGP-based auto-\n discovery, requires network operators to specify various network\n parameters on top of the access configuration. This document\n specifies the requirements for an Ethernet VPN (EVPN) solution, which\n addresses the above issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track spe 7209 delivery driving http license path policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7223","type":"specification","body":"IETF","designation":"RFC 7223","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7223.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7223.txt","https://www.rfc-editor.org/rfc/rfc7223.pdf"],"folder":"IETF/RFC-7223","files":{"txt":{"path":"standards/IETF/RFC-7223/RFC-7223.txt","sha256":"1d4ee3203ea0babebb769844b39cdd8003d094c21c151e104aaadcfa3358522c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG data model for the management of network\n interfaces. It is expected that interface-type-specific data models\n augment the generic interfaces data model defined in this document.\n The data model includes configuration data and state data (status\n information and counters for the collection of statistics).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7223.\n","scope_keywords":["7223","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null}],"search_text":"IETF RFC 7223 This document defines a YANG data model for the management of network\n interfaces. It is expected that interface-type-specific data models\n augment the generic interfaces data model defined in this document.\n The data model includes configuration data and state data (status\n information and counters for the collection of statistics).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7223.\n 7223 http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7227","type":"specification","body":"IETF","designation":"RFC 7227","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7227.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7227.txt","https://www.rfc-editor.org/rfc/rfc7227.pdf"],"folder":"IETF/RFC-7227","files":{"txt":{"path":"standards/IETF/RFC-7227/RFC-7227.txt","sha256":"4f332b298c0cb401dd67e1fea40f71676991948748c8e5b9b23dd6cfdaba0044"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance to prospective DHCPv6 option\n developers to help them create option formats that are easily\n adoptable by existing DHCPv6 software. It also provides guidelines\n for expert reviewers to evaluate new registrations. This document\n updates RFC 3315.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7227.\n\nHankins, et al. Best Current Practice [Page 1]\n\f\nRFC 7227 DHCP","scope_keywords":["7227","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7550","folder":"IETF/RFC-7550","source":"IETF/RFC-7550/RFC-7550.txt","version":null},{"body":"IETF","designation":"RFC 7598","folder":"IETF/RFC-7598","source":"IETF/RFC-7598/RFC-7598.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null}],"search_text":"IETF RFC 7227 This document provides guidance to prospective DHCPv6 option\n developers to help them create option formats that are easily\n adoptable by existing DHCPv6 software. It also provides guidelines\n for expert reviewers to evaluate new registrations. This document\n updates RFC 3315.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7227.\n\nHankins, et al. Best Current Practice [Page 1]\n\f\nRFC 7227 DHCP 7227 http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 7232","type":"specification","body":"IETF","designation":"RFC 7232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7232.txt","https://www.rfc-editor.org/rfc/rfc7232.pdf"],"folder":"IETF/RFC-7232","files":{"txt":{"path":"standards/IETF/RFC-7232/RFC-7232.txt","sha256":"3788e183becfbdaf93121082cd90ac7c1324e871fe425438805942a10207b1b4"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP/1.1 conditional requests,\n including metadata header fields for indicating state changes,\n request header fields for making preconditions on such state, and\n rules for constructing the responses to a conditional request when\n one or more preconditions evaluate to false.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document","scope_keywords":["7232","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8246","folder":"IETF/RFC-8246","source":"IETF/RFC-8246/RFC-8246.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7232 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP/1.1 conditional requests,\n including metadata header fields for indicating state changes,\n request header fields for making preconditions on such state, and\n rules for constructing the responses to a conditional request when\n one or more preconditions evaluate to false.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document 7232 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7235","type":"specification","body":"IETF","designation":"RFC 7235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7235.txt","https://www.rfc-editor.org/rfc/rfc7235.pdf"],"folder":"IETF/RFC-7235","files":{"txt":{"path":"standards/IETF/RFC-7235/RFC-7235.txt","sha256":"abfb45a43fdebffc640b51fae46f480e65fc01238f244f94b1bcf2c20da0b862"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypermedia information\n systems. This document defines the HTTP Authentication framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7235.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This ","scope_keywords":["7235","authentication","authorization","credential","credentials","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 422","folder":"ETSI/EN-319-422-V1.1.1","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7235 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypermedia information\n systems. This document defines the HTTP Authentication framework.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7235.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This  7235 authentication authorization credential credentials http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7238","type":"specification","body":"IETF","designation":"RFC 7238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7238.txt","https://www.rfc-editor.org/rfc/rfc7238.pdf"],"folder":"IETF/RFC-7238","files":{"txt":{"path":"standards/IETF/RFC-7238/RFC-7238.txt","sha256":"f8856750bc1890471f2aa083fc0ea016c7a4195dab5d0de8778449df6d40e46b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the additional Hypertext Transfer Protocol\n (HTTP) status code 308 (Permanent Redirect).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7238.\n\nCopyright ","scope_keywords":["7238","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7538","folder":"IETF/RFC-7538","source":"IETF/RFC-7538/RFC-7538.txt","version":null}],"search_text":"IETF RFC 7238 This document specifies the additional Hypertext Transfer Protocol\n (HTTP) status code 308 (Permanent Redirect).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7238.\n\nCopyright  7238 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7240","type":"specification","body":"IETF","designation":"RFC 7240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7240.txt","https://www.rfc-editor.org/rfc/rfc7240.pdf"],"folder":"IETF/RFC-7240","files":{"txt":{"path":"standards/IETF/RFC-7240/RFC-7240.txt","sha256":"2cde510338babf6ad937e0bcb31989bb9a664ab1567d4b41cb143fe9740ae16e"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an HTTP header field that can be used by a\n client to request that certain behaviors be employed by a server\n while processing a request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7240.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IE","scope_keywords":["7240","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null}],"search_text":"IETF RFC 7240 This specification defines an HTTP header field that can be used by a\n client to request that certain behaviors be employed by a server\n while processing a request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7240.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IE 7240 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7247","type":"specification","body":"IETF","designation":"RFC 7247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7247.txt","https://www.rfc-editor.org/rfc/rfc7247.pdf"],"folder":"IETF/RFC-7247","files":{"txt":{"path":"standards/IETF/RFC-7247/RFC-7247.txt","sha256":"378844590c40c0904d6f6409f8ee3aa308af0a8c0ee0e8fac8563606df8ab357"}},"tags":["nested-reference","unchanged"],"summary":"As a foundation for the definition of bidirectional protocol mappings\n between the Session Initiation Protocol (SIP) and the Extensible\n Messaging and Presence Protocol (XMPP), this document specifies the\n architectural assumptions underlying such mappings as well as the\n mapping of addresses and error conditions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7247.\n\nSaint-Andre, et al.","scope_keywords":["7247","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null}],"search_text":"IETF RFC 7247 As a foundation for the definition of bidirectional protocol mappings\n between the Session Initiation Protocol (SIP) and the Extensible\n Messaging and Presence Protocol (XMPP), this document specifies the\n architectural assumptions underlying such mappings as well as the\n mapping of addresses and error conditions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7247.\n\nSaint-Andre, et al. 7247 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7250","type":"specification","body":"IETF","designation":"RFC 7250","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7250.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7250.txt","https://www.rfc-editor.org/rfc/rfc7250.pdf"],"folder":"IETF/RFC-7250","files":{"txt":{"path":"standards/IETF/RFC-7250/RFC-7250.txt","sha256":"834f7695e5258237efd4638f573203b325dbe8bce66a5690f6ff730fb00538dd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new certificate type and two TLS extensions\n for exchanging raw public keys in Transport Layer Security (TLS) and\n Datagram Transport Layer Security (DTLS). The new certificate type\n allows raw public keys to be used for authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7250.\n\nWouters, et al. Standards Track [Page 1]\n\f\nRFC 7250 Using Raw Public Key","scope_keywords":["7250","authentication","certificate","certificates","http","key","keys","license","path","pki","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7924","folder":"IETF/RFC-7924","source":"IETF/RFC-7924/RFC-7924.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8094","folder":"IETF/RFC-8094","source":"IETF/RFC-8094/RFC-8094.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null}],"search_text":"IETF RFC 7250 This document specifies a new certificate type and two TLS extensions\n for exchanging raw public keys in Transport Layer Security (TLS) and\n Datagram Transport Layer Security (DTLS). The new certificate type\n allows raw public keys to be used for authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7250.\n\nWouters, et al. Standards Track [Page 1]\n\f\nRFC 7250 Using Raw Public Key 7250 authentication certificate certificates http key keys license path pki subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 7251","type":"specification","body":"IETF","designation":"RFC 7251","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7251.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7251.txt","https://www.rfc-editor.org/rfc/rfc7251.pdf"],"folder":"IETF/RFC-7251","files":{"txt":{"path":"standards/IETF/RFC-7251/RFC-7251.txt","sha256":"01125c551476ac9da94f3391cd41bb9d6d9bac04b898fc5421818f809d0e9ea9"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the use of the Advanced Encryption Standard (AES)\n in the Counter and CBC-MAC Mode (CCM) of operation within Transport\n Layer Security (TLS) to provide confidentiality and data-origin\n authentication. The AES-CCM algorithm is amenable to compact\n implementations, making it suitable for constrained environments,\n while at the same time providing a high level of security. The\n cipher suites defined in this document use Elliptic Curve\n Cryptography (ECC) and are advantageous in networks with limited\n bandwidth.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering","scope_keywords":["7251","algorithm","algorithms","authentication","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null}],"search_text":"IETF RFC 7251 This memo describes the use of the Advanced Encryption Standard (AES)\n in the Counter and CBC-MAC Mode (CCM) of operation within Transport\n Layer Security (TLS) to provide confidentiality and data-origin\n authentication. The AES-CCM algorithm is amenable to compact\n implementations, making it suitable for constrained environments,\n while at the same time providing a high level of security. The\n cipher suites defined in this document use Elliptic Curve\n Cryptography (ECC) and are advantageous in networks with limited\n bandwidth.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering 7251 algorithm algorithms authentication encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7254","type":"specification","body":"IETF","designation":"RFC 7254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7254.txt","https://www.rfc-editor.org/rfc/rfc7254.pdf"],"folder":"IETF/RFC-7254","files":{"txt":{"path":"standards/IETF/RFC-7254/RFC-7254.txt","sha256":"c1355844eb72d2916f9af93b87d300a7f45229cedcb182193476f081d7a87de3"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a Uniform Resource Name (URN) namespace\n for the Global System for Mobile Communications Association (GSMA)\n and a Namespace Specific String (NSS) for the International Mobile\n station Equipment Identity (IMEI), as well as an associated parameter\n for the International Mobile station Equipment Identity and Software\n Version number (IMEISV). The IMEI and IMEISV were introduced as part\n of the specification for the GSM and are also now incorporated by the\n 3rd Generation Partnership Project (3GPP) as part of the 3GPP\n specification for GSM, Universal Mobile Telecommunications System\n (UMTS), and 3GPP Long Term Evolution (LTE) networks. The IMEI and\n IMEISV are used to uniquely identify Mobile Equipment within these\n systems and are managed by the GSMA. URNs from this namespace almost\n always contain personally identifiable information and need to be\n treated acco","scope_keywords":["7254","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7255","folder":"IETF/RFC-7255","source":"IETF/RFC-7255/RFC-7255.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null}],"search_text":"IETF RFC 7254 This specification defines a Uniform Resource Name (URN) namespace\n for the Global System for Mobile Communications Association (GSMA)\n and a Namespace Specific String (NSS) for the International Mobile\n station Equipment Identity (IMEI), as well as an associated parameter\n for the International Mobile station Equipment Identity and Software\n Version number (IMEISV). The IMEI and IMEISV were introduced as part\n of the specification for the GSM and are also now incorporated by the\n 3rd Generation Partnership Project (3GPP) as part of the 3GPP\n specification for GSM, Universal Mobile Telecommunications System\n (UMTS), and 3GPP Long Term Evolution (LTE) networks. The IMEI and\n IMEISV are used to uniquely identify Mobile Equipment within these\n systems and are managed by the GSMA. URNs from this namespace almost\n always contain personally identifiable information and need to be\n treated acco 7254 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7255","type":"specification","body":"IETF","designation":"RFC 7255","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7255.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7255.txt","https://www.rfc-editor.org/rfc/rfc7255.pdf"],"folder":"IETF/RFC-7255","files":{"txt":{"path":"standards/IETF/RFC-7255/RFC-7255.txt","sha256":"8f9534b469462f071bed42b33591721933a2139b8ef49a5f7f3e988ac6c6ffff"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines how the Uniform Resource Name (URN)\n reserved for the Global System for Mobile Communications Association\n (GSMA) identities and its sub-namespace for the International Mobile\n station Equipment Identity (IMEI) can be used as an instance-id. Its\n purpose is to fulfill the requirements for defining how a specific\n URN needs to be constructed and used in the '+sip.instance' Contact\n header field parameter for outbound behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for an","scope_keywords":["7255","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null}],"search_text":"IETF RFC 7255 This specification defines how the Uniform Resource Name (URN)\n reserved for the Global System for Mobile Communications Association\n (GSMA) identities and its sub-namespace for the International Mobile\n station Equipment Identity (IMEI) can be used as an instance-id. Its\n purpose is to fulfill the requirements for defining how a specific\n URN needs to be constructed and used in the '+sip.instance' Contact\n header field parameter for outbound behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for an 7255 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7272","type":"specification","body":"IETF","designation":"RFC 7272","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7272.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7272.txt","https://www.rfc-editor.org/rfc/rfc7272.pdf"],"folder":"IETF/RFC-7272","files":{"txt":{"path":"standards/IETF/RFC-7272/RFC-7272.txt","sha256":"737dcf2e0364f80d4467ee90d25e67c4a061bbf0560fcd57621a69b30325ab3d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new RTP Control Protocol (RTCP) Packet Type\n and an RTCP Extended Report (XR) Block Type to be used for achieving\n Inter-Destination Media Synchronization (IDMS). IDMS is the process\n of synchronizing playout across multiple media receivers. Using the\n RTCP XR IDMS Report Block defined in this document, media playout\n information from participants in a synchronization group can be\n collected. Based on the collected information, an RTCP IDMS Settings\n Packet can then be sent to distribute a common target playout point\n to which all the distributed receivers, sharing a media experience,\n can synchronize.\n\n Typical use cases in which IDMS is useful are social TV, shared\n service control (i.e., applications where two or more geographically\n separated users are watching a media stream together), distance\n learning, networked video walls, networked loudspeakers, etc.\n\nS","scope_keywords":["7272","algorithm","algorithms","attribute","delivery","http","identification","key","license","presentation","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 7272 This document defines a new RTP Control Protocol (RTCP) Packet Type\n and an RTCP Extended Report (XR) Block Type to be used for achieving\n Inter-Destination Media Synchronization (IDMS). IDMS is the process\n of synchronizing playout across multiple media receivers. Using the\n RTCP XR IDMS Report Block defined in this document, media playout\n information from participants in a synchronization group can be\n collected. Based on the collected information, an RTCP IDMS Settings\n Packet can then be sent to distribute a common target playout point\n to which all the distributed receivers, sharing a media experience,\n can synchronize.\n\n Typical use cases in which IDMS is useful are social TV, shared\n service control (i.e., applications where two or more geographically\n separated users are watching a media stream together), distance\n learning, networked video walls, networked loudspeakers, etc.\n\nS 7272 algorithm algorithms attribute delivery http identification key license presentation subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 7283","type":"specification","body":"IETF","designation":"RFC 7283","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7283.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7283.txt","https://www.rfc-editor.org/rfc/rfc7283.pdf"],"folder":"IETF/RFC-7283","files":{"txt":{"path":"standards/IETF/RFC-7283/RFC-7283.txt","sha256":"7a83bc5539fb4a343e14a7e475bf423aa2a0880f128732a674d328b042800fd0"}},"tags":["nested-reference","unchanged"],"summary":"DHCPv6 is not specific about handling messages with unknown types.\n This memo describes the problems associated with receiving DHCPv6\n messages with unknown types, and defines how a DHCPv6 server, client,\n or relay agent should behave when receiving unknown DHCPv6 messages.\n This document also provides advice for authors of future documents\n that define new messages to be sent from DHCP servers to DHCP relay\n agents. This document updates RFC 3315.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this ","scope_keywords":["7283","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7283 DHCPv6 is not specific about handling messages with unknown types.\n This memo describes the problems associated with receiving DHCPv6\n messages with unknown types, and defines how a DHCPv6 server, client,\n or relay agent should behave when receiving unknown DHCPv6 messages.\n This document also provides advice for authors of future documents\n that define new messages to be sent from DHCP servers to DHCP relay\n agents. This document updates RFC 3315.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this  7283 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7301","type":"specification","body":"IETF","designation":"RFC 7301","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7301.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7301.txt","https://www.rfc-editor.org/rfc/rfc7301.pdf"],"folder":"IETF/RFC-7301","files":{"txt":{"path":"standards/IETF/RFC-7301/RFC-7301.txt","sha256":"ba122aee58871c604c9e98e2c9f81d5042e4056bd497cd41e23ad80fe3123222"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Transport Layer Security (TLS) extension\n for application-layer protocol negotiation within the TLS handshake.\n For instances in which multiple application protocols are supported\n on the same TCP or UDP port, this extension allows the application\n layer to negotiate which protocol will be used within the TLS\n connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/","scope_keywords":["7301","certificate","http","key","license","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 7301 This document describes a Transport Layer Security (TLS) extension\n for application-layer protocol negotiation within the TLS handshake.\n For instances in which multiple application protocols are supported\n on the same TCP or UDP port, this extension allows the application\n layer to negotiate which protocol will be used within the TLS\n connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/ 7301 certificate http key license registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7312","type":"specification","body":"IETF","designation":"RFC 7312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7312.txt","https://www.rfc-editor.org/rfc/rfc7312.pdf"],"folder":"IETF/RFC-7312","files":{"txt":{"path":"standards/IETF/RFC-7312/RFC-7312.txt","sha256":"62df8d6d9d072488a7a2d7d6e5e8332587e5628aa16c6428e0b1af72c6759c2c"}},"tags":["nested-reference","unchanged"],"summary":"To obtain repeatable results in modern networks, test descriptions\n need an expanded stream parameter framework that also augments\n aspects specified as Type-P for test packets. This memo updates the\n IP Performance Metrics (IPPM) Framework, RFC 2330, with advanced\n considerations for measurement methodology and testing. The existing\n framework mostly assumes deterministic connectivity, and that a\n single test stream will represent the characteristics of the path\n when it is aggregated with other flows. Networks have evolved and\n test stream descriptions must evolve with them; otherwise, unexpected\n network features may dominate the measured performance. This memo\n describes new stream parameters for both network characterization and\n support of application design using IPPM metrics.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published f","scope_keywords":["7312","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"IETF RFC 7312 To obtain repeatable results in modern networks, test descriptions\n need an expanded stream parameter framework that also augments\n aspects specified as Type-P for test packets. This memo updates the\n IP Performance Metrics (IPPM) Framework, RFC 2330, with advanced\n considerations for measurement methodology and testing. The existing\n framework mostly assumes deterministic connectivity, and that a\n single test stream will represent the characteristics of the path\n when it is aggregated with other flows. Networks have evolved and\n test stream descriptions must evolve with them; otherwise, unexpected\n network features may dominate the measured performance. This memo\n describes new stream parameters for both network characterization and\n support of application design using IPPM metrics.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published f 7312 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7320","type":"specification","body":"IETF","designation":"RFC 7320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7320.txt","https://www.rfc-editor.org/rfc/rfc7320.pdf"],"folder":"IETF/RFC-7320","files":{"txt":{"path":"standards/IETF/RFC-7320/RFC-7320.txt","sha256":"fc17aed819e6c81258233b225feb9d18d9aafe1bae7b894a11a02b88143c4ed9"}},"tags":["nested-reference","unchanged"],"summary":"Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and\n extensible naming system wherein each scheme's specification may\n further restrict the syntax and semantics of identifiers using that\n scheme.\" In other words, the structure of a URI is defined by its\n scheme. While it is common for schemes to further delegate their\n substructure to the URI's owner, publishing independent standards\n that mandate particular forms of URI substructure is inappropriate,\n because that essentially usurps ownership. This document further\n describes this problematic practice and provides some acceptable\n alternatives for use in standards.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for ","scope_keywords":["7320","http","license","path","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7390","folder":"IETF/RFC-7390","source":"IETF/RFC-7390/RFC-7390.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null}],"search_text":"IETF RFC 7320 Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and\n extensible naming system wherein each scheme's specification may\n further restrict the syntax and semantics of identifiers using that\n scheme.\" In other words, the structure of a URI is defined by its\n scheme. While it is common for schemes to further delegate their\n substructure to the URI's owner, publishing independent standards\n that mandate particular forms of URI substructure is inappropriate,\n because that essentially usurps ownership. This document further\n describes this problematic practice and provides some acceptable\n alternatives for use in standards.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for  7320 http license path signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7321","type":"specification","body":"IETF","designation":"RFC 7321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7321.txt","https://www.rfc-editor.org/rfc/rfc7321.pdf"],"folder":"IETF/RFC-7321","files":{"txt":{"path":"standards/IETF/RFC-7321/RFC-7321.txt","sha256":"a26016b22f81da07a7a6db8d82d3b007e334ff4a5e7fe9dc9db2a5c291e3ff69"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the Cryptographic Algorithm Implementation\n Requirements for the Encapsulating Security Payload (ESP) and\n Authentication Header (AH). It also adds usage guidance to help in\n the selection of these algorithms.\n\n ESP and AH protocols make use of various cryptographic algorithms to\n provide confidentiality and/or data origin authentication to\n protected data communications in the IP Security (IPsec)\n architecture. To ensure interoperability between disparate\n implementations, the IPsec standard specifies a set of mandatory-to-\n implement algorithms. This document specifies the current set of\n mandatory-to-implement algorithms for ESP and AH, specifies\n algorithms that should be implemented because they may be promoted to\n mandatory at some future time, and also recommends against the\n implementation of some obsolete algorithms. Usage guidance is also\n provided to help","scope_keywords":["7321","algorithm","algorithms","authentication","encryption","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null}],"search_text":"IETF RFC 7321 This document updates the Cryptographic Algorithm Implementation\n Requirements for the Encapsulating Security Payload (ESP) and\n Authentication Header (AH). It also adds usage guidance to help in\n the selection of these algorithms.\n\n ESP and AH protocols make use of various cryptographic algorithms to\n provide confidentiality and/or data origin authentication to\n protected data communications in the IP Security (IPsec)\n architecture. To ensure interoperability between disparate\n implementations, the IPsec standard specifies a set of mandatory-to-\n implement algorithms. This document specifies the current set of\n mandatory-to-implement algorithms for ESP and AH, specifies\n algorithms that should be implemented because they may be promoted to\n mandatory at some future time, and also recommends against the\n implementation of some obsolete algorithms. Usage guidance is also\n provided to help 7321 algorithm algorithms authentication encryption http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7335","type":"specification","body":"IETF","designation":"RFC 7335","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7335.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7335.txt","https://www.rfc-editor.org/rfc/rfc7335.pdf"],"folder":"IETF/RFC-7335","files":{"txt":{"path":"standards/IETF/RFC-7335/RFC-7335.txt","sha256":"01f37a92ee7da25beac7260f16f9b6132818da01ab18bfc37e7a8f97017a72be"}},"tags":["nested-reference","unchanged"],"summary":"Dual-Stack Lite (DS-Lite), defined in RFC 6333, directs IANA to\n reserve 192.0.0.0/29 for the Basic Bridging BroadBand (B4) element.\n Per this memo, IANA has generalized that reservation to include other\n cases where a non-routed IPv4 interface must be numbered as part of\n an IPv6 transition solution.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7335.\n\nCopyright Notice\n\n Copyright (c)","scope_keywords":["7335","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7757","folder":"IETF/RFC-7757","source":"IETF/RFC-7757/RFC-7757.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7335 Dual-Stack Lite (DS-Lite), defined in RFC 6333, directs IANA to\n reserve 192.0.0.0/29 for the Basic Bridging BroadBand (B4) element.\n Per this memo, IANA has generalized that reservation to include other\n cases where a non-routed IPv4 interface must be numbered as part of\n an IPv6 transition solution.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7335.\n\nCopyright Notice\n\n Copyright (c) 7335 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7341","type":"specification","body":"IETF","designation":"RFC 7341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7341.txt","https://www.rfc-editor.org/rfc/rfc7341.pdf"],"folder":"IETF/RFC-7341","files":{"txt":{"path":"standards/IETF/RFC-7341/RFC-7341.txt","sha256":"da61501875905adedfd90cd0aa92c19ccedb830a505bb053c26e027e5d366e8f"}},"tags":["nested-reference","unchanged"],"summary":"IPv4 connectivity is still needed as networks migrate towards IPv6.\n Users require IPv4 configuration even if the uplink to their service\n provider supports IPv6 only. This document describes a mechanism for\n obtaining IPv4 configuration information dynamically in IPv6 networks\n by carrying DHCPv4 messages over DHCPv6 transport. Two new DHCPv6\n messages and two new DHCPv6 options are defined for this purpose.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provid","scope_keywords":["7341","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7341 IPv4 connectivity is still needed as networks migrate towards IPv6.\n Users require IPv4 configuration even if the uplink to their service\n provider supports IPv6 only. This document describes a mechanism for\n obtaining IPv4 configuration information dynamically in IPv6 networks\n by carrying DHCPv4 messages over DHCPv6 transport. Two new DHCPv6\n messages and two new DHCPv6 options are defined for this purpose.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provid 7341 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7345","type":"specification","body":"IETF","designation":"RFC 7345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7345.txt","https://www.rfc-editor.org/rfc/rfc7345.pdf"],"folder":"IETF/RFC-7345","files":{"txt":{"path":"standards/IETF/RFC-7345/RFC-7345.txt","sha256":"2abf5bd307e01e7c53a5c7196d3b9e51b93dc2c6e6089c73752e20edc90fbdec"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how the UDP Transport Layer (UDPTL) protocol,\n the predominant transport protocol for T.38 fax, can be transported\n over the Datagram Transport Layer Security (DTLS) protocol, how the\n usage of UDPTL over DTLS is indicated in the Session Description\n Protocol (SDP), and how UDPTL over DTLS is negotiated in a session\n established using the Session Initiation Protocol (SIP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on","scope_keywords":["7345","algorithm","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7983","folder":"IETF/RFC-7983","source":"IETF/RFC-7983/RFC-7983.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null}],"search_text":"IETF RFC 7345 This document specifies how the UDP Transport Layer (UDPTL) protocol,\n the predominant transport protocol for T.38 fax, can be transported\n over the Datagram Transport Layer Security (DTLS) protocol, how the\n usage of UDPTL over DTLS is indicated in the Session Description\n Protocol (SDP), and how UDPTL over DTLS is negotiated in a session\n established using the Session Initiation Protocol (SIP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on 7345 algorithm encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7350","type":"specification","body":"IETF","designation":"RFC 7350","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7350.txt","https://www.rfc-editor.org/rfc/rfc7350.pdf"],"folder":"IETF/RFC-7350","files":{"txt":{"path":"standards/IETF/RFC-7350/RFC-7350.txt","sha256":"edecaa3e028dc72009bd5f6b20cad6ff29f82e44327b3b3994fc8ff253363da5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the usage of Datagram Transport Layer\n Security (DTLS) as a transport protocol for Session Traversal\n Utilities for NAT (STUN). It provides guidance on when and how to\n use DTLS with the currently standardized STUN usages. It also\n specifies modifications to the STUN and Traversal Using Relay NAT\n (TURN) URIs and to the TURN resolution mechanism to facilitate the\n resolution of STUN and TURN URIs into the IP address and port of STUN\n and TURN servers supporting DTLS as a transport protocol. This\n document updates RFCs 5389 and 5928.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information","scope_keywords":["7350","http","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7675","folder":"IETF/RFC-7675","source":"IETF/RFC-7675/RFC-7675.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 7350 This document specifies the usage of Datagram Transport Layer\n Security (DTLS) as a transport protocol for Session Traversal\n Utilities for NAT (STUN). It provides guidance on when and how to\n use DTLS with the currently standardized STUN usages. It also\n specifies modifications to the STUN and Traversal Using Relay NAT\n (TURN) URIs and to the TURN resolution mechanism to facilitate the\n resolution of STUN and TURN URIs into the IP address and port of STUN\n and TURN servers supporting DTLS as a transport protocol. This\n document updates RFCs 5389 and 5928.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information 7350 http key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7366","type":"specification","body":"IETF","designation":"RFC 7366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7366.txt","https://www.rfc-editor.org/rfc/rfc7366.pdf"],"folder":"IETF/RFC-7366","files":{"txt":{"path":"standards/IETF/RFC-7366/RFC-7366.txt","sha256":"5dadf33fbc770231ac309c79e71c84a68a321b1c7d2fd0b9de654ed029c91f4f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a means of negotiating the use of the\n encrypt-then-MAC security mechanism in place of the existing MAC-\n then-encrypt mechanism in Transport Layer Security (TLS) and Datagram\n Transport Layer Security (DTLS). The MAC-then-encrypt mechanism has\n been the subject of a number of security vulnerabilities over a\n period of many years.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edit","scope_keywords":["7366","authentication","encryption","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7457","folder":"IETF/RFC-7457","source":"IETF/RFC-7457/RFC-7457.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7366 This document describes a means of negotiating the use of the\n encrypt-then-MAC security mechanism in place of the existing MAC-\n then-encrypt mechanism in Transport Layer Security (TLS) and Datagram\n Transport Layer Security (DTLS). The MAC-then-encrypt mechanism has\n been the subject of a number of security vulnerabilities over a\n period of many years.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edit 7366 authentication encryption http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7398","type":"specification","body":"IETF","designation":"RFC 7398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7398.txt","https://www.rfc-editor.org/rfc/rfc7398.pdf"],"folder":"IETF/RFC-7398","files":{"txt":{"path":"standards/IETF/RFC-7398/RFC-7398.txt","sha256":"7e74cf31dc15744d3f739c3e5a152da70caa5c66f59529333895c49bdedebb65"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a reference path for Large-scale Measurement of\n Broadband Access Performance (LMAP) and measurement points for\n commonly used performance metrics. Other similar measurement\n projects may also be able to use the extensions described here for\n measurement point location. The purpose is to create an efficient\n way to describe the location of the measurement point(s) used to\n conduct a particular measurement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan","scope_keywords":["7398","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 7398 This document defines a reference path for Large-scale Measurement of\n Broadband Access Performance (LMAP) and measurement points for\n commonly used performance metrics. Other similar measurement\n projects may also be able to use the extensions described here for\n measurement point location. The purpose is to create an efficient\n way to describe the location of the measurement point(s) used to\n conduct a particular measurement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Stan 7398 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7407","type":"specification","body":"IETF","designation":"RFC 7407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7407.txt","https://www.rfc-editor.org/rfc/rfc7407.pdf"],"folder":"IETF/RFC-7407","files":{"txt":{"path":"standards/IETF/RFC-7407/RFC-7407.txt","sha256":"b44a792b93c70e004eb207aac064e275b51c0e4b987cf5dab243deb85350989d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a collection of YANG definitions for\n configuring SNMP engines.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7407.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.o","scope_keywords":["7407","certificate","http","key","keys","license","management","presentation","subject","tls","trust","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null}],"search_text":"IETF RFC 7407 This document defines a collection of YANG definitions for\n configuring SNMP engines.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7407.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.o 7407 certificate http key keys license management presentation subject tls trust x509 nested-reference unchanged"},{"id":"IETF RFC 7462","type":"specification","body":"IETF","designation":"RFC 7462","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7462.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7462.txt","https://www.rfc-editor.org/rfc/rfc7462.pdf"],"folder":"IETF/RFC-7462","files":{"txt":{"path":"standards/IETF/RFC-7462/RFC-7462.txt","sha256":"8627e8bb25aea7b1795f95322a75a5c48d65289c2981b98cc4edbdea60fb5d85"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) supports the capability to\n provide a reference to a specific rendering to be used by the User\n Agent (UA) as an alerting signal (e.g., a ring tone or ringback tone)\n when the user is alerted. This is done using the Alert-Info header\n field. However, the reference (typically a URL) addresses only a\n specific network resource with specific rendering properties. There\n is currently no support for standard identifiers for describing the\n semantics of the alerting situation or the characteristics of the\n alerting signal, without being tied to a particular rendering. To\n overcome these limitations and support new applications, a new family\n of URNs for use in Alert-Info header fields (and situations with\n similar requirements) is defined in this specification.\n\n This document normatively updates RFC 3261, which defines the Session\n Initiation Protocol (SI","scope_keywords":["7462","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 7462 The Session Initiation Protocol (SIP) supports the capability to\n provide a reference to a specific rendering to be used by the User\n Agent (UA) as an alerting signal (e.g., a ring tone or ringback tone)\n when the user is alerted. This is done using the Alert-Info header\n field. However, the reference (typically a URL) addresses only a\n specific network resource with specific rendering properties. There\n is currently no support for standard identifiers for describing the\n semantics of the alerting situation or the characteristics of the\n alerting signal, without being tied to a particular rendering. To\n overcome these limitations and support new applications, a new family\n of URNs for use in Alert-Info header fields (and situations with\n similar requirements) is defined in this specification.\n\n This document normatively updates RFC 3261, which defines the Session\n Initiation Protocol (SI 7462 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7463","type":"specification","body":"IETF","designation":"RFC 7463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7463.txt","https://www.rfc-editor.org/rfc/rfc7463.pdf"],"folder":"IETF/RFC-7463","files":{"txt":{"path":"standards/IETF/RFC-7463/RFC-7463.txt","sha256":"e0444403b31641bcd80eb46648de4bf1af01b09610552498a6745c5b23a51d76"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the requirements and implementation of a\n group telephony feature commonly known as Bridged Line Appearance\n (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line\n Appearance (SCA). When implemented using the Session Initiation\n Protocol (SIP), it is referred to as shared appearances of an Address\n of Record (AOR) since SIP does not have the concept of lines. This\n feature is commonly offered in IP Centrex services and IP Private\n Branch Exchange (IPBX) offerings and is likely to be implemented on\n SIP IP telephones and SIP feature servers used in a business\n environment. This feature allows several user agents (UAs) to share\n a common AOR, learn about calls placed and received by other UAs in\n the group, and pick up or join calls within the group. This document\n discusses use cases, lists requirements, and defines extensions to\n implement this feature. Thi","scope_keywords":["7463","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 7463 This document describes the requirements and implementation of a\n group telephony feature commonly known as Bridged Line Appearance\n (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line\n Appearance (SCA). When implemented using the Session Initiation\n Protocol (SIP), it is referred to as shared appearances of an Address\n of Record (AOR) since SIP does not have the concept of lines. This\n feature is commonly offered in IP Centrex services and IP Private\n Branch Exchange (IPBX) offerings and is likely to be implemented on\n SIP IP telephones and SIP feature servers used in a business\n environment. This feature allows several user agents (UAs) to share\n a common AOR, learn about calls placed and received by other UAs in\n the group, and pick up or join calls within the group. This document\n discusses use cases, lists requirements, and defines extensions to\n implement this feature. Thi 7463 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7464","type":"specification","body":"IETF","designation":"RFC 7464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7464.txt","https://www.rfc-editor.org/rfc/rfc7464.pdf"],"folder":"IETF/RFC-7464","files":{"txt":{"path":"standards/IETF/RFC-7464/RFC-7464.txt","sha256":"a8eadbcdce5fc508b9e014299621562da041232af13848632092164d50b3f482"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the JavaScript Object Notation (JSON) text\n sequence format and associated media type \"application/json-seq\". A\n JSON text sequence consists of any number of JSON texts, all encoded\n in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each\n ending with an ASCII Line Feed character (0x0A).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7464.\n\nCopyrigh","scope_keywords":["7464","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8091","folder":"IETF/RFC-8091","source":"IETF/RFC-8091/RFC-8091.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 7464 This document describes the JavaScript Object Notation (JSON) text\n sequence format and associated media type \"application/json-seq\". A\n JSON text sequence consists of any number of JSON texts, all encoded\n in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each\n ending with an ASCII Line Feed character (0x0A).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7464.\n\nCopyrigh 7464 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7465","type":"specification","body":"IETF","designation":"RFC 7465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7465.txt","https://www.rfc-editor.org/rfc/rfc7465.pdf"],"folder":"IETF/RFC-7465","files":{"txt":{"path":"standards/IETF/RFC-7465/RFC-7465.txt","sha256":"0c619db38176f199f739dc696a2d3faabbe658ee82d59621c6d040d0b7cce2dd"}},"tags":["nested-reference","unchanged"],"summary":"This document requires that Transport Layer Security (TLS) clients\n and servers never negotiate the use of RC4 cipher suites when they\n establish connections. This applies to all TLS versions. This\n document updates RFCs 5246, 4346, and 2246.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7465.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document","scope_keywords":["7465","algorithm","algorithms","encryption","http","https","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7568","folder":"IETF/RFC-7568","source":"IETF/RFC-7568/RFC-7568.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7465 This document requires that Transport Layer Security (TLS) clients\n and servers never negotiate the use of RC4 cipher suites when they\n establish connections. This applies to all TLS versions. This\n document updates RFCs 5246, 4346, and 2246.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7465.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document 7465 algorithm algorithms encryption http https key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7469","type":"specification","body":"IETF","designation":"RFC 7469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7469.txt","https://www.rfc-editor.org/rfc/rfc7469.pdf"],"folder":"IETF/RFC-7469","files":{"txt":{"path":"standards/IETF/RFC-7469/RFC-7469.txt","sha256":"c1d5b042e77e2eb0abcfc2f1bcd444873621ea00b632c0b045492effd0888064"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new HTTP header that allows web host\n operators to instruct user agents to remember (\"pin\") the hosts'\n cryptographic identities over a period of time. During that time,\n user agents (UAs) will require that the host presents a certificate\n chain including at least one Subject Public Key Info structure whose\n fingerprint matches one of the pinned fingerprints for that host. By\n effectively reducing the number of trusted authorities who can\n authenticate the domain during the lifetime of the pin, pinning may\n reduce the incidence of man-in-the-middle attacks due to compromised\n Certification Authorities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication ","scope_keywords":["7469","attribute","authentication","certificate","certificates","http","key","keys","license","pki","risk","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null}],"search_text":"IETF RFC 7469 This document defines a new HTTP header that allows web host\n operators to instruct user agents to remember (\"pin\") the hosts'\n cryptographic identities over a period of time. During that time,\n user agents (UAs) will require that the host presents a certificate\n chain including at least one Subject Public Key Info structure whose\n fingerprint matches one of the pinned fingerprints for that host. By\n effectively reducing the number of trusted authorities who can\n authenticate the domain during the lifetime of the pin, pinning may\n reduce the incidence of man-in-the-middle attacks due to compromised\n Certification Authorities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication  7469 attribute authentication certificate certificates http key keys license pki risk subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 7480","type":"specification","body":"IETF","designation":"RFC 7480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7480.txt","https://www.rfc-editor.org/rfc/rfc7480.pdf"],"folder":"IETF/RFC-7480","files":{"txt":{"path":"standards/IETF/RFC-7480/RFC-7480.txt","sha256":"9d956ef3f3311eaf9f929f0984237c5e38cbbc20ed359dcfc4073327f5cb8feb"}},"tags":["nested-reference","unchanged"],"summary":"This document is one of a collection that together describes the\n Registration Data Access Protocol (RDAP). It describes how RDAP is\n transported using the Hypertext Transfer Protocol (HTTP). RDAP is a\n successor protocol to the very old WHOIS protocol. The purpose of\n this document is to clarify the use of standard HTTP mechanisms for\n this application.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edit","scope_keywords":["7480","http","https","license","presentation","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7480 This document is one of a collection that together describes the\n Registration Data Access Protocol (RDAP). It describes how RDAP is\n transported using the Hypertext Transfer Protocol (HTTP). RDAP is a\n successor protocol to the very old WHOIS protocol. The purpose of\n this document is to clarify the use of standard HTTP mechanisms for\n this application.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-edit 7480 http https license presentation profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7481","type":"specification","body":"IETF","designation":"RFC 7481","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7481.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7481.txt","https://www.rfc-editor.org/rfc/rfc7481.pdf"],"folder":"IETF/RFC-7481","files":{"txt":{"path":"standards/IETF/RFC-7481/RFC-7481.txt","sha256":"53fa4cbb385d015b8a4f4018f4d1034a77eb2b10efc08711f1b14adb9a74553d"}},"tags":["nested-reference","unchanged"],"summary":"The Registration Data Access Protocol (RDAP) provides \"RESTful\" web\n services to retrieve registration metadata from Domain Name and\n Regional Internet Registries. This document describes information\n security services, including access control, authentication,\n authorization, availability, data confidentiality, and data integrity\n for RDAP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r","scope_keywords":["7481","authentication","authorization","credential","http","key","license","policies","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7481 The Registration Data Access Protocol (RDAP) provides \"RESTful\" web\n services to retrieve registration metadata from Domain Name and\n Regional Internet Registries. This document describes information\n security services, including access control, authentication,\n authorization, availability, data confidentiality, and data integrity\n for RDAP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/r 7481 authentication authorization credential http key license policies policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7483","type":"specification","body":"IETF","designation":"RFC 7483","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7483.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7483.txt","https://www.rfc-editor.org/rfc/rfc7483.pdf"],"folder":"IETF/RFC-7483","files":{"txt":{"path":"standards/IETF/RFC-7483/RFC-7483.txt","sha256":"4e83515f042fa5d47924e9a366d566c05819bcb7acec25dca11b430a607f4886"}},"tags":["nested-reference","unchanged"],"summary":"This document describes JSON data structures representing\n registration information maintained by Regional Internet Registries\n (RIRs) and Domain Name Registries (DNRs). These data structures are\n used to form Registration Data Access Protocol (RDAP) query\n responses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7483.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons i","scope_keywords":["7483","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7484","folder":"IETF/RFC-7484","source":"IETF/RFC-7484/RFC-7484.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null}],"search_text":"IETF RFC 7483 This document describes JSON data structures representing\n registration information maintained by Regional Internet Registries\n (RIRs) and Domain Name Registries (DNRs). These data structures are\n used to form Registration Data Access Protocol (RDAP) query\n responses.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7483.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons i 7483 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7484","type":"specification","body":"IETF","designation":"RFC 7484","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7484.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7484.txt","https://www.rfc-editor.org/rfc/rfc7484.pdf"],"folder":"IETF/RFC-7484","files":{"txt":{"path":"standards/IETF/RFC-7484/RFC-7484.txt","sha256":"38e8f4c7068468304bfe7c7594966d79fc9af9ea2d10335debecb94b76b43a4b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method to find which Registration Data\n Access Protocol (RDAP) server is authoritative to answer queries for\n a requested scope, such as domain names, IP addresses, or Autonomous\n System numbers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7484.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights ","scope_keywords":["7484","http","https","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 7484 This document specifies a method to find which Registration Data\n Access Protocol (RDAP) server is authoritative to answer queries for\n a requested scope, such as domain names, IP addresses, or Autonomous\n System numbers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7484.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights  7484 http https key license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 7486","type":"specification","body":"IETF","designation":"RFC 7486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7486.txt","https://www.rfc-editor.org/rfc/rfc7486.pdf"],"folder":"IETF/RFC-7486","files":{"txt":{"path":"standards/IETF/RFC-7486/RFC-7486.txt","sha256":"e12f86ba32e7501945ff7c796107e47503a2ece45cd9309486117fd9e94bd65a"}},"tags":["nested-reference","unchanged"],"summary":"HTTP Origin-Bound Authentication (HOBA) is a digital-signature-based\n design for an HTTP authentication method. The design can also be\n used in JavaScript-based authentication embedded in HTML. HOBA is an\n alternative to HTTP authentication schemes that require passwords and\n therefore avoids all problems related to passwords, such as leakage\n of server-side password databases.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved","scope_keywords":["7486","algorithm","algorithms","authentication","certificate","certificates","credential","credentials","http","key","keys","license","management","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null}],"search_text":"IETF RFC 7486 HTTP Origin-Bound Authentication (HOBA) is a digital-signature-based\n design for an HTTP authentication method. The design can also be\n used in JavaScript-based authentication embedded in HTML. HOBA is an\n alternative to HTTP authentication schemes that require passwords and\n therefore avoids all problems related to passwords, such as leakage\n of server-side password databases.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved 7486 algorithm algorithms authentication certificate certificates credential credentials http key keys license management signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 7495","type":"specification","body":"IETF","designation":"RFC 7495","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7495.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7495.txt","https://www.rfc-editor.org/rfc/rfc7495.pdf"],"folder":"IETF/RFC-7495","files":{"txt":{"path":"standards/IETF/RFC-7495/RFC-7495.txt","sha256":"e869dc8fe1505634011549b23d5ba6f5c4c59a478c3475e83fa998101abaa067"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) is an XML\n data representation framework for sharing information about computer\n security incidents. In IODEF, the Reference class provides\n references to externally specified information such as a\n vulnerability, Intrusion Detection System (IDS) alert, malware\n sample, advisory, or attack technique. In practice, these references\n are based on external enumeration specifications that define both the\n enumeration format and the specific enumeration values, but the IODEF\n Reference class (as specified in IODEF v1 in RFC 5070) does not\n indicate how to include both of these important pieces of\n information.\n\n This document establishes a stand-alone data format to include both\n the external specification and specific enumeration identification\n value, and establishes an IANA registry to manage external\n enumeration specifications. While","scope_keywords":["7495","attribute","http","identification","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null}],"search_text":"IETF RFC 7495 The Incident Object Description Exchange Format (IODEF) is an XML\n data representation framework for sharing information about computer\n security incidents. In IODEF, the Reference class provides\n references to externally specified information such as a\n vulnerability, Intrusion Detection System (IDS) alert, malware\n sample, advisory, or attack technique. In practice, these references\n are based on external enumeration specifications that define both the\n enumeration format and the specific enumeration values, but the IODEF\n Reference class (as specified in IODEF v1 in RFC 5070) does not\n indicate how to include both of these important pieces of\n information.\n\n This document establishes a stand-alone data format to include both\n the external specification and specific enumeration identification\n value, and establishes an IANA registry to manage external\n enumeration specifications. While 7495 attribute http identification key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7496","type":"specification","body":"IETF","designation":"RFC 7496","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7496.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7496.txt","https://www.rfc-editor.org/rfc/rfc7496.pdf"],"folder":"IETF/RFC-7496","files":{"txt":{"path":"standards/IETF/RFC-7496/RFC-7496.txt","sha256":"22422bcaed0a57caf1587065f0d088de25c1635fbfbe70befcb353fd1a4388a3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two additional policies for the Partially\n Reliable Stream Control Transmission Protocol (PR-SCTP) extension.\n These policies allow limitation of the number of retransmissions and\n prioritization of user messages for more efficient usage of the send\n buffer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7496.\n\nTuexen, et al. Standards Track [Page 1]\n\f\nRFC 7496 Add","scope_keywords":["7496","algorithm","http","key","license","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null}],"search_text":"IETF RFC 7496 This document defines two additional policies for the Partially\n Reliable Stream Control Transmission Protocol (PR-SCTP) extension.\n These policies allow limitation of the number of retransmissions and\n prioritization of user messages for more efficient usage of the send\n buffer.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7496.\n\nTuexen, et al. Standards Track [Page 1]\n\f\nRFC 7496 Add 7496 algorithm http key license path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7507","type":"specification","body":"IETF","designation":"RFC 7507","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7507.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7507.txt","https://www.rfc-editor.org/rfc/rfc7507.pdf"],"folder":"IETF/RFC-7507","files":{"txt":{"path":"standards/IETF/RFC-7507/RFC-7507.txt","sha256":"540854df66a35bf656e912969cb091ab9ff9e48cf31671eb32ad5bc6add8b691"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Signaling Cipher Suite Value (SCSV) that\n prevents protocol downgrade attacks on the Transport Layer Security\n (TLS) and Datagram Transport Layer Security (DTLS) protocols. It\n updates RFCs 2246, 4346, 4347, 5246, and 6347. Server update\n considerations are included.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7507.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF ","scope_keywords":["7507","http","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7507 This document defines a Signaling Cipher Suite Value (SCSV) that\n prevents protocol downgrade attacks on the Transport Layer Security\n (TLS) and Datagram Transport Layer Security (DTLS) protocols. It\n updates RFCs 2246, 4346, 4347, 5246, and 6347. Server update\n considerations are included.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7507.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF  7507 http key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7510","type":"specification","body":"IETF","designation":"RFC 7510","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7510.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7510.txt","https://www.rfc-editor.org/rfc/rfc7510.pdf"],"folder":"IETF/RFC-7510","files":{"txt":{"path":"standards/IETF/RFC-7510/RFC-7510.txt","sha256":"c22acef088d16e298e47bf58366be413c06f71db84f009e40cf102d1cb25fa25"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an IP-based encapsulation for MPLS, called\n MPLS-in-UDP for situations where UDP (User Datagram Protocol)\n encapsulation is preferred to direct use of MPLS, e.g., to enable\n UDP-based ECMP (Equal-Cost Multipath) or link aggregation. The MPLS-\n in-UDP encapsulation technology must only be deployed within a single\n network (with a single network operator) or networks of an adjacent\n set of cooperating network operators where traffic is managed to\n avoid congestion, rather than over the Internet where congestion\n control is required. Usage restrictions apply to MPLS-in-UDP usage\n for traffic that is not congestion controlled and to UDP zero\n checksum usage with IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has","scope_keywords":["7510","hash","http","key","keys","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 7510 This document specifies an IP-based encapsulation for MPLS, called\n MPLS-in-UDP for situations where UDP (User Datagram Protocol)\n encapsulation is preferred to direct use of MPLS, e.g., to enable\n UDP-based ECMP (Equal-Cost Multipath) or link aggregation. The MPLS-\n in-UDP encapsulation technology must only be deployed within a single\n network (with a single network operator) or networks of an adjacent\n set of cooperating network operators where traffic is managed to\n avoid congestion, rather than over the Internet where congestion\n control is required. Usage restrictions apply to MPLS-in-UDP usage\n for traffic that is not congestion controlled and to UDP zero\n checksum usage with IPv6.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has 7510 hash http key keys license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7521","type":"specification","body":"IETF","designation":"RFC 7521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7521.txt","https://www.rfc-editor.org/rfc/rfc7521.pdf"],"folder":"IETF/RFC-7521","files":{"txt":{"path":"standards/IETF/RFC-7521/RFC-7521.txt","sha256":"d5d97b3e691c9bbc495c277cc2cd79316b82486991468fc346a96ab59ba4b3c8"}},"tags":["nested-reference","unchanged"],"summary":"This specification provides a framework for the use of assertions\n with OAuth 2.0 in the form of a new client authentication mechanism\n and a new authorization grant type. Mechanisms are specified for\n transporting assertions during interactions with a token endpoint;\n general processing rules are also specified.\n\n The intent of this specification is to provide a common framework for\n OAuth 2.0 to interwork with other identity systems using assertions\n and to provide alternative client authentication mechanisms.\n\n Note that this specification only defines abstract message flows and\n processing rules. In order to be implementable, companion\n specifications are necessary to provide the corresponding concrete\n instantiations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the con","scope_keywords":["7521","authentication","authorization","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 7521 This specification provides a framework for the use of assertions\n with OAuth 2.0 in the form of a new client authentication mechanism\n and a new authorization grant type. Mechanisms are specified for\n transporting assertions during interactions with a token endpoint;\n general processing rules are also specified.\n\n The intent of this specification is to provide a common framework for\n OAuth 2.0 to interwork with other identity systems using assertions\n and to provide alternative client authentication mechanisms.\n\n Note that this specification only defines abstract message flows and\n processing rules. In order to be implementable, companion\n specifications are necessary to provide the corresponding concrete\n instantiations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the con 7521 authentication authorization http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7522","type":"specification","body":"IETF","designation":"RFC 7522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7522.txt","https://www.rfc-editor.org/rfc/rfc7522.pdf"],"folder":"IETF/RFC-7522","files":{"txt":{"path":"standards/IETF/RFC-7522/RFC-7522.txt","sha256":"87656a015c74b2cce4ed74fdf785ea2cf824e8d13cc53860d40fac3e57569afd"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the use of a Security Assertion Markup\n Language (SAML) 2.0 Bearer Assertion as a means for requesting an\n OAuth 2.0 access token as well as for client authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7522.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i","scope_keywords":["7522","authentication","authorization","credential","credentials","http","identification","license","policy","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-3","folder":"ETSI/EN-319-522-3-V1.2.1","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null}],"search_text":"IETF RFC 7522 This specification defines the use of a Security Assertion Markup\n Language (SAML) 2.0 Bearer Assertion as a means for requesting an\n OAuth 2.0 access token as well as for client authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7522.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i 7522 authentication authorization credential credentials http identification license policy profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7523","type":"specification","body":"IETF","designation":"RFC 7523","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7523.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7523.txt","https://www.rfc-editor.org/rfc/rfc7523.pdf"],"folder":"IETF/RFC-7523","files":{"txt":{"path":"standards/IETF/RFC-7523/RFC-7523.txt","sha256":"ae24f77a8fc4338903c805c6ace38def1f23d40194aea87b123b13c5b3d2d915"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the use of a JSON Web Token (JWT) Bearer\n Token as a means for requesting an OAuth 2.0 access token as well as\n for client authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7523.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the I","scope_keywords":["7523","authentication","authorization","credential","credentials","http","identification","key","license","policy","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 7523 This specification defines the use of a JSON Web Token (JWT) Bearer\n Token as a means for requesting an OAuth 2.0 access token as well as\n for client authentication.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7523.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the I 7523 authentication authorization credential credentials http identification key license policy profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7538","type":"specification","body":"IETF","designation":"RFC 7538","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7538.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7538.txt","https://www.rfc-editor.org/rfc/rfc7538.pdf"],"folder":"IETF/RFC-7538","files":{"txt":{"path":"standards/IETF/RFC-7538/RFC-7538.txt","sha256":"0fcc1c5949e206669d4f6caa1c32982104a1bb19b56ebe49c1b6491c81beccc3"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the additional Hypertext Transfer Protocol\n (HTTP) status code 308 (Permanent Redirect).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7538.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Docume","scope_keywords":["7538","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7538 This document specifies the additional Hypertext Transfer Protocol\n (HTTP) status code 308 (Permanent Redirect).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7538.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Docume 7538 http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7539","type":"specification","body":"IETF","designation":"RFC 7539","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7539.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7539.txt","https://www.rfc-editor.org/rfc/rfc7539.pdf"],"folder":"IETF/RFC-7539","files":{"txt":{"path":"standards/IETF/RFC-7539/RFC-7539.txt","sha256":"546e12200dbbc7b08cf85c8f07ea8681be89954b7c7e0c56f0c51f775a0ba704"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the ChaCha20 stream cipher as well as the use\n of the Poly1305 authenticator, both as stand-alone algorithms and as\n a \"combined mode\", or Authenticated Encryption with Associated Data\n (AEAD) algorithm.\n\n This document does not introduce any new crypto, but is meant to\n serve as a stable reference and an implementation guide. It is a\n product of the Crypto Forum Research Group (CFRG).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for pub","scope_keywords":["7539","algorithm","algorithms","authentication","encryption","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7905","folder":"IETF/RFC-7905","source":"IETF/RFC-7905/RFC-7905.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null}],"search_text":"IETF RFC 7539 This document defines the ChaCha20 stream cipher as well as the use\n of the Poly1305 authenticator, both as stand-alone algorithms and as\n a \"combined mode\", or Authenticated Encryption with Associated Data\n (AEAD) algorithm.\n\n This document does not introduce any new crypto, but is meant to\n serve as a stable reference and an implementation guide. It is a\n product of the Crypto Forum Research Group (CFRG).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for pub 7539 algorithm algorithms authentication encryption http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7550","type":"specification","body":"IETF","designation":"RFC 7550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7550.txt","https://www.rfc-editor.org/rfc/rfc7550.pdf"],"folder":"IETF/RFC-7550","files":{"txt":{"path":"standards/IETF/RFC-7550/RFC-7550.txt","sha256":"0d6776e211d25883fc37dcc03e978e31d612ce20d1b61e48d1788c6f49f6f04b"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)\n specification defined two stateful options, IA_NA and IA_TA, but did\n not anticipate the development of additional stateful options.\n DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.\n Applications that use IA_NA and IA_PD together have revealed issues\n that need to be addressed. This document updates RFCs 3315 and 3633\n to address these issues.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h","scope_keywords":["7550","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7550 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)\n specification defined two stateful options, IA_NA and IA_TA, but did\n not anticipate the development of additional stateful options.\n DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.\n Applications that use IA_NA and IA_PD together have revealed issues\n that need to be addressed. This document updates RFCs 3315 and 3633\n to address these issues.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h 7550 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7562","type":"specification","body":"IETF","designation":"RFC 7562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7562.txt","https://www.rfc-editor.org/rfc/rfc7562.pdf"],"folder":"IETF/RFC-7562","files":{"txt":{"path":"standards/IETF/RFC-7562/RFC-7562.txt","sha256":"f17262750a6195769d0e319934a0af84cf85aecb84b94c569b4a9cf735bc761b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the use of Digital Transmission Content\n Protection (DTCP) certificates as an authorization data type in the\n authorization extension for the Transport Layer Security (TLS)\n protocol. This is in accordance with the guidelines for\n authorization extensions as specified in RFC 5878. As with other TLS\n extensions, this authorization data can be included in the client and\n server hello messages to confirm that both parties support the\n desired authorization data types. If supported by both the client\n and the server, DTCP certificates are exchanged in the supplemental\n data TLS handshake message as specified in RFC 4680. This\n authorization data type extension is in support of devices containing\n DTCP certificates issued by the Digital Transmission Licensing\n Administrator (DTLA).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; i","scope_keywords":["7562","algorithm","authentication","authorization","certificate","certificates","http","key","license","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 7562 This document specifies the use of Digital Transmission Content\n Protection (DTCP) certificates as an authorization data type in the\n authorization extension for the Transport Layer Security (TLS)\n protocol. This is in accordance with the guidelines for\n authorization extensions as specified in RFC 5878. As with other TLS\n extensions, this authorization data can be included in the client and\n server hello messages to confirm that both parties support the\n desired authorization data types. If supported by both the client\n and the server, DTCP certificates are exchanged in the supplemental\n data TLS handshake message as specified in RFC 4680. This\n authorization data type extension is in support of devices containing\n DTCP certificates issued by the Digital Transmission Licensing\n Administrator (DTLA).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; i 7562 algorithm authentication authorization certificate certificates http key license signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7572","type":"specification","body":"IETF","designation":"RFC 7572","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7572.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7572.txt","https://www.rfc-editor.org/rfc/rfc7572.pdf"],"folder":"IETF/RFC-7572","files":{"txt":{"path":"standards/IETF/RFC-7572/RFC-7572.txt","sha256":"2a8822c9b0ce232dbcb19cd2c8485399ecc2b171f7505709e013080a63124161"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a bidirectional protocol mapping for the\n exchange of single instant messages between the Session Initiation\n Protocol (SIP) and the Extensible Messaging and Presence Protocol\n (XMPP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7572.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi","scope_keywords":["7572","attribute","attributes","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7573","folder":"IETF/RFC-7573","source":"IETF/RFC-7573/RFC-7573.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null}],"search_text":"IETF RFC 7572 This document defines a bidirectional protocol mapping for the\n exchange of single instant messages between the Session Initiation\n Protocol (SIP) and the Extensible Messaging and Presence Protocol\n (XMPP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7572.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi 7572 attribute attributes delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7573","type":"specification","body":"IETF","designation":"RFC 7573","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7573.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7573.txt","https://www.rfc-editor.org/rfc/rfc7573.pdf"],"folder":"IETF/RFC-7573","files":{"txt":{"path":"standards/IETF/RFC-7573/RFC-7573.txt","sha256":"dac989e065fb4c57ec9a5b8653b99f3a0965a4123615a5cc659db33beab702a3"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a bidirectional protocol mapping for the\n exchange of instant messages in the context of a one-to-one chat\n session between a user of the Session Initiation Protocol (SIP) and a\n user of the Extensible Messaging and Presence Protocol (XMPP).\n Specifically for SIP text chat, this document specifies a mapping to\n the Message Session Relay Protocol (MSRP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at","scope_keywords":["7573","delivery","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null}],"search_text":"IETF RFC 7573 This document defines a bidirectional protocol mapping for the\n exchange of instant messages in the context of a one-to-one chat\n session between a user of the Session Initiation Protocol (SIP) and a\n user of the Extensible Messaging and Presence Protocol (XMPP).\n Specifically for SIP text chat, this document specifies a mapping to\n the Message Session Relay Protocol (MSRP).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at 7573 delivery http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7587","type":"specification","body":"IETF","designation":"RFC 7587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7587.txt","https://www.rfc-editor.org/rfc/rfc7587.pdf"],"folder":"IETF/RFC-7587","files":{"txt":{"path":"standards/IETF/RFC-7587/RFC-7587.txt","sha256":"5afdf22d62f11900166b1b3781c483f429ccb4addebd841b3fa8b77708ff5662"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Real-time Transport Protocol (RTP) payload\n format for packetization of Opus-encoded speech and audio data\n necessary to integrate the codec in the most compatible way. It also\n provides an applicability statement for the use of Opus over RTP.\n Further, it describes media type registrations for the RTP payload\n format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/inf","scope_keywords":["7587","algorithm","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 7587 This document defines the Real-time Transport Protocol (RTP) payload\n format for packetization of Opus-encoded speech and audio data\n necessary to integrate the codec in the most compatible way. It also\n provides an applicability statement for the use of Opus over RTP.\n Further, it describes media type registrations for the RTP payload\n format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/inf 7587 algorithm http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7589","type":"specification","body":"IETF","designation":"RFC 7589","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7589.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7589.txt","https://www.rfc-editor.org/rfc/rfc7589.pdf"],"folder":"IETF/RFC-7589","files":{"txt":{"path":"standards/IETF/RFC-7589/RFC-7589.txt","sha256":"cd47369dc72e4f76b43e4080a4aafa146c2d1138e5074571cded77d18e07626a"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) provides mechanisms to\n install, manipulate, and delete the configuration of network devices.\n This document describes how to use the Transport Layer Security (TLS)\n protocol with mutual X.509 authentication to secure the exchange of\n NETCONF messages. This revision of RFC 5539 documents the new\n message framing used by NETCONF 1.1 and it obsoletes RFC 5539.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb","scope_keywords":["7589","authentication","certificate","delivery","http","key","license","management","path","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 7589 The Network Configuration Protocol (NETCONF) provides mechanisms to\n install, manipulate, and delete the configuration of network devices.\n This document describes how to use the Transport Layer Security (TLS)\n protocol with mutual X.509 authentication to secure the exchange of\n NETCONF messages. This revision of RFC 5539 documents the new\n message framing used by NETCONF 1.1 and it obsoletes RFC 5539.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedb 7589 authentication certificate delivery http key license management path subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 7590","type":"specification","body":"IETF","designation":"RFC 7590","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7590.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7590.txt","https://www.rfc-editor.org/rfc/rfc7590.pdf"],"folder":"IETF/RFC-7590","files":{"txt":{"path":"standards/IETF/RFC-7590/RFC-7590.txt","sha256":"b02f7008e5830e81dcc6713bde23e4ab966618a440d3b5c5320abee67a1488d6"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations for the use of Transport Layer\n Security (TLS) in the Extensible Messaging and Presence Protocol\n (XMPP). This document updates RFC 6120.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7590.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7","scope_keywords":["7590","authentication","certificate","certificates","http","key","license","management","pki","policy","profile","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7590 This document provides recommendations for the use of Transport Layer\n Security (TLS) in the Extensible Messaging and Presence Protocol\n (XMPP). This document updates RFC 6120.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7590.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7 7590 authentication certificate certificates http key license management pki policy profile subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 7591","type":"specification","body":"IETF","designation":"RFC 7591","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7591.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7591.txt","https://www.rfc-editor.org/rfc/rfc7591.pdf"],"folder":"IETF/RFC-7591","files":{"txt":{"path":"standards/IETF/RFC-7591/RFC-7591.txt","sha256":"f9cd8b8eefdb2d1b1bd5734310f246926db0abb4ec1b2f933f358d58327964e3"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines mechanisms for dynamically registering\n OAuth 2.0 clients with authorization servers. Registration requests\n send a set of desired client metadata values to the authorization\n server. The resulting registration responses return a client\n identifier to use at the authorization server and the client metadata\n values registered for the client. The client can then use this\n registration information to communicate with the authorization server\n using the OAuth 2.0 protocol. This specification also defines a set\n of common client metadata fields and values for clients to use during\n registration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n I","scope_keywords":["7591","authentication","authorization","http","issuer","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 7592","folder":"IETF/RFC-7592","source":"IETF/RFC-7592/RFC-7592.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 7591 This specification defines mechanisms for dynamically registering\n OAuth 2.0 clients with authorization servers. Registration requests\n send a set of desired client metadata values to the authorization\n server. The resulting registration responses return a client\n identifier to use at the authorization server and the client metadata\n values registered for the client. The client can then use this\n registration information to communicate with the authorization server\n using the OAuth 2.0 protocol. This specification also defines a set\n of common client metadata fields and values for clients to use during\n registration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n I 7591 authentication authorization http issuer license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7592","type":"specification","body":"IETF","designation":"RFC 7592","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7592.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7592.txt","https://www.rfc-editor.org/rfc/rfc7592.pdf"],"folder":"IETF/RFC-7592","files":{"txt":{"path":"standards/IETF/RFC-7592/RFC-7592.txt","sha256":"6e59ce6f2f7cd98bfe849f643a55ddb45fc0278a43c49b2cf0d947ca604ccaee"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines methods for management of OAuth 2.0\n dynamic client registrations for use cases in which the properties of\n a registered client may need to be changed during the lifetime of the\n client. Not all authorization servers supporting dynamic client\n registration will support these management methods.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet St","scope_keywords":["7592","authorization","credential","credentials","http","key","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7591","folder":"IETF/RFC-7591","source":"IETF/RFC-7591/RFC-7591.txt","version":null}],"search_text":"IETF RFC 7592 This specification defines methods for management of OAuth 2.0\n dynamic client registrations for use cases in which the properties of\n a registered client may need to be changed during the lifetime of the\n client. Not all authorization servers supporting dynamic client\n registration will support these management methods.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet St 7592 authorization credential credentials http key license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7595","type":"specification","body":"IETF","designation":"RFC 7595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7595.txt","https://www.rfc-editor.org/rfc/rfc7595.pdf"],"folder":"IETF/RFC-7595","files":{"txt":{"path":"standards/IETF/RFC-7595/RFC-7595.txt","sha256":"0766f5f6a189176f1b96cebf0ed11c1d6e3c65d97ccc4cdb38e25a4ca7fe4d75"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the guidelines and recommendations, as well as\n the IANA registration processes, for the definition of Uniform\n Resource Identifier (URI) schemes. It obsoletes RFC 4395.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7595.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subjec","scope_keywords":["7595","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 7595 This document updates the guidelines and recommendations, as well as\n the IANA registration processes, for the definition of Uniform\n Resource Identifier (URI) schemes. It obsoletes RFC 4395.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7595.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subjec 7595 http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7598","type":"specification","body":"IETF","designation":"RFC 7598","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7598.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7598.txt","https://www.rfc-editor.org/rfc/rfc7598.pdf"],"folder":"IETF/RFC-7598","files":{"txt":{"path":"standards/IETF/RFC-7598/RFC-7598.txt","sha256":"2e3a96db09be6b601a21be6f18db2bee16abee8c76d502e9512ab93f90a3c83f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies DHCPv6 options, termed Softwire46 options,\n for the provisioning of Softwire46 Customer Edge (CE) devices.\n Softwire46 is a collective term used to refer to architectures based\n on the notion of IPv4 Address plus Port (A+P) for providing IPv4\n connectivity across an IPv6 network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7598.\n\nMrugalski, et al. Standards Tr","scope_keywords":["7598","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7618","folder":"IETF/RFC-7618","source":"IETF/RFC-7618/RFC-7618.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7598 This document specifies DHCPv6 options, termed Softwire46 options,\n for the provisioning of Softwire46 Customer Edge (CE) devices.\n Softwire46 is a collective term used to refer to architectures based\n on the notion of IPv4 Address plus Port (A+P) for providing IPv4\n connectivity across an IPv6 network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7598.\n\nMrugalski, et al. Standards Tr 7598 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7610","type":"specification","body":"IETF","designation":"RFC 7610","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7610.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7610.txt","https://www.rfc-editor.org/rfc/rfc7610.pdf"],"folder":"IETF/RFC-7610","files":{"txt":{"path":"standards/IETF/RFC-7610/RFC-7610.txt","sha256":"b6ed40396f9025ecdb8aeed19b89aa7d911d8099f8bb0bf063453bc30e9e144e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism for protecting hosts connected to\n a switched network against rogue DHCPv6 servers. It is based on\n DHCPv6 packet filtering at the layer 2 device at which the packets\n are received. A similar mechanism has been widely deployed in IPv4\n networks ('DHCP snooping'); hence, it is desirable that similar\n functionality be provided for IPv6 networks. This document specifies\n a Best Current Practice for the implementation of DHCPv6-Shield.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current s","scope_keywords":["7610","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 7610 This document specifies a mechanism for protecting hosts connected to\n a switched network against rogue DHCPv6 servers. It is based on\n DHCPv6 packet filtering at the layer 2 device at which the packets\n are received. A similar mechanism has been widely deployed in IPv4\n networks ('DHCP snooping'); hence, it is desirable that similar\n functionality be provided for IPv6 networks. This document specifies\n a Best Current Practice for the implementation of DHCPv6-Shield.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current s 7610 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7618","type":"specification","body":"IETF","designation":"RFC 7618","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7618.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7618.txt","https://www.rfc-editor.org/rfc/rfc7618.pdf"],"folder":"IETF/RFC-7618","files":{"txt":{"path":"standards/IETF/RFC-7618/RFC-7618.txt","sha256":"6b7b9159a89769c182d6f48f7232c81e019dd1775bf72af345ce66f30112676c"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the dynamic allocation of shared IPv4 addresses\n to clients using DHCPv4. Address sharing allows a single IPv4\n address to be allocated to multiple active clients simultaneously,\n with each client being differentiated by a unique set of transport-\n layer source port numbers. The necessary changes to existing DHCPv4\n client and server behavior are described, and a new DHCPv4 option for\n provisioning clients with shared IPv4 addresses is included.\n\n Due to the nature of IP address sharing, some limitations to its\n applicability are necessary. This memo describes these limitations\n and recommends suitable architectures and technologies where address\n sharing may be utilized.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It","scope_keywords":["7618","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null}],"search_text":"IETF RFC 7618 This memo describes the dynamic allocation of shared IPv4 addresses\n to clients using DHCPv4. Address sharing allows a single IPv4\n address to be allocated to multiple active clients simultaneously,\n with each client being differentiated by a unique set of transport-\n layer source port numbers. The necessary changes to existing DHCPv4\n client and server behavior are described, and a new DHCPv4 option for\n provisioning clients with shared IPv4 addresses is included.\n\n Due to the nature of IP address sharing, some limitations to its\n applicability are necessary. This memo describes these limitations\n and recommends suitable architectures and technologies where address\n sharing may be utilized.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It 7618 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7619","type":"specification","body":"IETF","designation":"RFC 7619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7619.txt","https://www.rfc-editor.org/rfc/rfc7619.pdf"],"folder":"IETF/RFC-7619","files":{"txt":{"path":"standards/IETF/RFC-7619/RFC-7619.txt","sha256":"57cba56d6c71f690d5bd122112ea0c49c8e658dfb47618b61c20e6e531e1a328"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the NULL Authentication method and the\n ID_NULL Identification Payload ID Type for Internet Key Exchange\n Protocol version 2 (IKEv2). This allows two IKE peers to establish\n single-side authenticated or mutual unauthenticated IKE sessions for\n those use cases where a peer is unwilling or unable to authenticate\n or identify itself. This ensures IKEv2 can be used for Opportunistic\n Security (also known as Opportunistic Encryption) to defend against\n Pervasive Monitoring attacks without the need to sacrifice anonymity.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Sta","scope_keywords":["7619","audit","authentication","authorization","encryption","http","identification","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7619 This document specifies the NULL Authentication method and the\n ID_NULL Identification Payload ID Type for Internet Key Exchange\n Protocol version 2 (IKEv2). This allows two IKE peers to establish\n single-side authenticated or mutual unauthenticated IKE sessions for\n those use cases where a peer is unwilling or unable to authenticate\n or identify itself. This ensures IKEv2 can be used for Opportunistic\n Security (also known as Opportunistic Encryption) to defend against\n Pervasive Monitoring attacks without the need to sacrifice anonymity.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Sta 7619 audit authentication authorization encryption http identification key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7627","type":"specification","body":"IETF","designation":"RFC 7627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7627.txt","https://www.rfc-editor.org/rfc/rfc7627.pdf"],"folder":"IETF/RFC-7627","files":{"txt":{"path":"standards/IETF/RFC-7627/RFC-7627.txt","sha256":"3e908b1a511f5894b64b2c7867c5e0e8db43896add4d99a340fe67a07ee11a59"}},"tags":["nested-reference","unchanged"],"summary":"The Transport Layer Security (TLS) master secret is not\n cryptographically bound to important session parameters such as the\n server certificate. Consequently, it is possible for an active\n attacker to set up two sessions, one with a client and another with a\n server, such that the master secrets on the two sessions are the\n same. Thereafter, any mechanism that relies on the master secret for\n authentication, including session resumption, becomes vulnerable to a\n man-in-the-middle attack, where the attacker can simply forward\n messages back and forth between the client and server. This\n specification defines a TLS extension that contextually binds the\n master secret to a log of the full handshake that computes it, thus\n preventing such attacks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF).","scope_keywords":["7627","authentication","certificate","hash","http","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null},{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7627 The Transport Layer Security (TLS) master secret is not\n cryptographically bound to important session parameters such as the\n server certificate. Consequently, it is possible for an active\n attacker to set up two sessions, one with a client and another with a\n server, such that the master secrets on the two sessions are the\n same. Thereafter, any mechanism that relies on the master secret for\n authentication, including session resumption, becomes vulnerable to a\n man-in-the-middle attack, where the attacker can simply forward\n messages back and forth between the client and server. This\n specification defines a TLS extension that contextually binds the\n master secret to a log of the full handshake that computes it, thus\n preventing such attacks.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). 7627 authentication certificate hash http key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7633","type":"specification","body":"IETF","designation":"RFC 7633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7633.txt","https://www.rfc-editor.org/rfc/rfc7633.pdf"],"folder":"IETF/RFC-7633","files":{"txt":{"path":"standards/IETF/RFC-7633/RFC-7633.txt","sha256":"7e69fff081b9b28fb130954464e80d50bfb6a9c8c656077445951b566323edf5"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of the TLS feature extension is to prevent downgrade\n attacks that are not otherwise prevented by the TLS protocol. In\n particular, the TLS feature extension may be used to mandate support\n for revocation checking features in the TLS protocol such as Online\n Certificate Status Protocol (OCSP) stapling. Informing clients that\n an OCSP status response will always be stapled permits an immediate\n failure in the case that the response is not stapled. This in turn\n prevents a denial-of-service attack that might otherwise be possible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet St","scope_keywords":["7633","authorization","certificate","certificates","credential","credentials","http","issuer","key","license","ocsp","revocation","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7633 The purpose of the TLS feature extension is to prevent downgrade\n attacks that are not otherwise prevented by the TLS protocol. In\n particular, the TLS feature extension may be used to mandate support\n for revocation checking features in the TLS protocol such as Online\n Certificate Status Protocol (OCSP) stapling. Informing clients that\n an OCSP status response will always be stapled permits an immediate\n failure in the case that the response is not stapled. This in turn\n prevents a denial-of-service attack that might otherwise be possible.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet St 7633 authorization certificate certificates credential credentials http issuer key license ocsp revocation risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7638","type":"specification","body":"IETF","designation":"RFC 7638","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7638.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7638.txt","https://www.rfc-editor.org/rfc/rfc7638.pdf"],"folder":"IETF/RFC-7638","files":{"txt":{"path":"standards/IETF/RFC-7638/RFC-7638.txt","sha256":"98b29ab9652070e6a5fec748d43e221bbedc66b6b22e05903fb5366c04ef3110"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a method for computing a hash value over a\n JSON Web Key (JWK). It defines which fields in a JWK are used in the\n hash computation, the method of creating a canonical form for those\n fields, and how to convert the resulting Unicode string into a byte\n sequence to be hashed. The resulting hash value can be used for\n identifying or selecting the key represented by the JWK that is the\n subject of the thumbprint.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any","scope_keywords":["7638","algorithm","algorithms","hash","http","key","keys","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null}],"search_text":"IETF RFC 7638 This specification defines a method for computing a hash value over a\n JSON Web Key (JWK). It defines which fields in a JWK are used in the\n hash computation, the method of creating a canonical form for those\n fields, and how to convert the resulting Unicode string into a byte\n sequence to be hashed. The resulting hash value can be used for\n identifying or selecting the key represented by the JWK that is the\n subject of the thumbprint.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any 7638 algorithm algorithms hash http key keys license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7643","type":"specification","body":"IETF","designation":"RFC 7643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7643.txt","https://www.rfc-editor.org/rfc/rfc7643.pdf"],"folder":"IETF/RFC-7643","files":{"txt":{"path":"standards/IETF/RFC-7643/RFC-7643.txt","sha256":"df799c112a3fa5be3c0fe054c08b1f4eb5d07590c4c8343a014c4537bf638ae3"}},"tags":["nested-reference","unchanged"],"summary":"The System for Cross-domain Identity Management (SCIM) specifications\n are designed to make identity management in cloud-based applications\n and services easier. The specification suite builds upon experience\n with existing schemas and deployments, placing specific emphasis on\n simplicity of development and integration, while applying existing\n authentication, authorization, and privacy models. Its intent is to\n reduce the cost and complexity of user management operations by\n providing a common user schema and extension model as well as binding\n documents to provide patterns for exchanging this schema using HTTP.\n\n This document provides a platform-neutral schema and extension model\n for representing users and groups and other resource types in JSON\n format. This schema is intended for exchange and use with cloud\n service providers.\n\nStatus of This Memo\n\n This is an Internet Standards Tr","scope_keywords":["7643","attribute","attributes","authentication","authorization","http","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null}],"search_text":"IETF RFC 7643 The System for Cross-domain Identity Management (SCIM) specifications\n are designed to make identity management in cloud-based applications\n and services easier. The specification suite builds upon experience\n with existing schemas and deployments, placing specific emphasis on\n simplicity of development and integration, while applying existing\n authentication, authorization, and privacy models. Its intent is to\n reduce the cost and complexity of user management operations by\n providing a common user schema and extension model as well as binding\n documents to provide patterns for exchanging this schema using HTTP.\n\n This document provides a platform-neutral schema and extension model\n for representing users and groups and other resource types in JSON\n format. This schema is intended for exchange and use with cloud\n service providers.\n\nStatus of This Memo\n\n This is an Internet Standards Tr 7643 attribute attributes authentication authorization http license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7644","type":"specification","body":"IETF","designation":"RFC 7644","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7644.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7644.txt","https://www.rfc-editor.org/rfc/rfc7644.pdf"],"folder":"IETF/RFC-7644","files":{"txt":{"path":"standards/IETF/RFC-7644/RFC-7644.txt","sha256":"b9078e016c98b86934a23c80926b74fc8b59885ab2943729ec2493c17488a09b"}},"tags":["nested-reference","unchanged"],"summary":"The System for Cross-domain Identity Management (SCIM) specification\n is an HTTP-based protocol that makes managing identities in multi-\n domain scenarios easier to support via a standardized service.\n Examples include, but are not limited to, enterprise-to-cloud service\n providers and inter-cloud scenarios. The specification suite seeks\n to build upon experience with existing schemas and deployments,\n placing specific emphasis on simplicity of development and\n integration, while applying existing authentication, authorization,\n and privacy models. SCIM's intent is to reduce the cost and\n complexity of user management operations by providing a common user\n schema, an extension model, and a service protocol defined by this\n document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen","scope_keywords":["7644","attribute","attributes","authentication","authorization","http","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null}],"search_text":"IETF RFC 7644 The System for Cross-domain Identity Management (SCIM) specification\n is an HTTP-based protocol that makes managing identities in multi-\n domain scenarios easier to support via a standardized service.\n Examples include, but are not limited to, enterprise-to-cloud service\n providers and inter-cloud scenarios. The specification suite seeks\n to build upon experience with existing schemas and deployments,\n placing specific emphasis on simplicity of development and\n integration, while applying existing authentication, authorization,\n and privacy models. SCIM's intent is to reduce the cost and\n complexity of user management operations by providing a common user\n schema, an extension model, and a service protocol defined by this\n document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen 7644 attribute attributes authentication authorization http license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7653","type":"specification","body":"IETF","designation":"RFC 7653","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7653.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7653.txt","https://www.rfc-editor.org/rfc/rfc7653.pdf"],"folder":"IETF/RFC-7653","files":{"txt":{"path":"standards/IETF/RFC-7653/RFC-7653.txt","sha256":"bb8cbb91f23e99ee30e4935b0d06996ca3b7a1be455c1102a508342ea70b147a"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been\n extended with a Leasequery capability that allows a requestor to\n request information about DHCPv6 bindings. That mechanism is limited\n to queries for DHCPv6 binding data updates prior to the time the\n DHCPv6 server receives the Leasequery request. Continuous update of\n an external requestor with Leasequery data is sometimes desired.\n This document expands on the DHCPv6 Leasequery protocol and allows\n for active transfer of real-time DHCPv6 binding information data via\n TCP. This document also updates DHCPv6 Bulk Leasequery (RFC 5460) by\n adding new options.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b","scope_keywords":["7653","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null}],"search_text":"IETF RFC 7653 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been\n extended with a Leasequery capability that allows a requestor to\n request information about DHCPv6 bindings. That mechanism is limited\n to queries for DHCPv6 binding data updates prior to the time the\n DHCPv6 server receives the Leasequery request. Continuous update of\n an external requestor with Leasequery data is sometimes desired.\n This document expands on the DHCPv6 Leasequery protocol and allows\n for active transfer of real-time DHCPv6 binding information data via\n TCP. This document also updates DHCPv6 Bulk Leasequery (RFC 5460) by\n adding new options.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication b 7653 http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7662","type":"specification","body":"IETF","designation":"RFC 7662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7662.txt","https://www.rfc-editor.org/rfc/rfc7662.pdf"],"folder":"IETF/RFC-7662","files":{"txt":{"path":"standards/IETF/RFC-7662/RFC-7662.txt","sha256":"2b7d688cb849f093e860557ac97e6cddac2556d69a4386561b22cdf97bf13657"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a method for a protected resource to query\n an OAuth 2.0 authorization server to determine the active state of an\n OAuth 2.0 token and to determine meta-information about this token.\n OAuth 2.0 deployments can use this method to convey information about\n the authorization context of the token from the authorization server\n to the protected resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a","scope_keywords":["7662","authorization","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null}],"search_text":"IETF RFC 7662 This specification defines a method for a protected resource to query\n an OAuth 2.0 authorization server to determine the active state of an\n OAuth 2.0 token and to determine meta-information about this token.\n OAuth 2.0 deployments can use this method to convey information about\n the authorization context of the token from the authorization server\n to the protected resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a 7662 authorization http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7665","type":"specification","body":"IETF","designation":"RFC 7665","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7665.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7665.txt","https://www.rfc-editor.org/rfc/rfc7665.pdf"],"folder":"IETF/RFC-7665","files":{"txt":{"path":"standards/IETF/RFC-7665/RFC-7665.txt","sha256":"7f0d6f2e421bdd540bd914690139599b89a2ec86d0dd5c54e502b5bd390be24d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for the specification,\n creation, and ongoing maintenance of Service Function Chains (SFCs)\n in a network. It includes architectural concepts, principles, and\n components used in the construction of composite services through\n deployment of SFCs, with a focus on those to be standardized in the\n IETF. This document does not propose solutions, protocols, or\n extensions to existing protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Sta","scope_keywords":["7665","delivery","http","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7665 This document describes an architecture for the specification,\n creation, and ongoing maintenance of Service Function Chains (SFCs)\n in a network. It includes architectural concepts, principles, and\n components used in the construction of composite services through\n deployment of SFCs, with a focus on those to be standardized in the\n IETF. This document does not propose solutions, protocols, or\n extensions to existing protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Sta 7665 delivery http license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7673","type":"specification","body":"IETF","designation":"RFC 7673","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7673.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7673.txt","https://www.rfc-editor.org/rfc/rfc7673.pdf"],"folder":"IETF/RFC-7673","files":{"txt":{"path":"standards/IETF/RFC-7673/RFC-7673.txt","sha256":"13eb8624f169d1a449d9d95d59baf43c77af21a567bb2203d7b8e0595158fb0c"}},"tags":["nested-reference","unchanged"],"summary":"The DNS-Based Authentication of Named Entities (DANE) specification\n (RFC 6698) describes how to use TLSA resource records secured by\n DNSSEC (RFC 4033) to associate a server's connection endpoint with\n its Transport Layer Security (TLS) certificate (thus enabling\n administrators of domain names to specify the keys used in that\n domain's TLS servers). However, application protocols that use SRV\n records (RFC 2782) to indirectly name the target server connection\n endpoints for a service domain name cannot apply the rules from RFC\n 6698. Therefore, this document provides guidelines that enable such\n protocols to locate and use TLSA records.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for","scope_keywords":["7673","authentication","certificate","http","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7673 The DNS-Based Authentication of Named Entities (DANE) specification\n (RFC 6698) describes how to use TLSA resource records secured by\n DNSSEC (RFC 4033) to associate a server's connection endpoint with\n its Transport Layer Security (TLS) certificate (thus enabling\n administrators of domain names to specify the keys used in that\n domain's TLS servers). However, application protocols that use SRV\n records (RFC 2782) to indirectly name the target server connection\n endpoints for a service domain name cannot apply the rules from RFC\n 6698. Therefore, this document provides guidelines that enable such\n protocols to locate and use TLSA records.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for 7673 authentication certificate http key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7675","type":"specification","body":"IETF","designation":"RFC 7675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7675.txt","https://www.rfc-editor.org/rfc/rfc7675.pdf"],"folder":"IETF/RFC-7675","files":{"txt":{"path":"standards/IETF/RFC-7675/RFC-7675.txt","sha256":"301ef56c53015c8e10ba42aac959d467bfc4e784cd2b5dbd59db41b835b949dd"}},"tags":["nested-reference","unchanged"],"summary":"To prevent WebRTC applications, such as browsers, from launching\n attacks by sending traffic to unwilling victims, periodic consent to\n send needs to be obtained from remote endpoints.\n\n This document describes a consent mechanism using a new Session\n Traversal Utilities for NAT (STUN) usage.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7675.\n\nPerumal, et al. Standards Track [Page 1]\n","scope_keywords":["7675","http","key","license","revocation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 7675 To prevent WebRTC applications, such as browsers, from launching\n attacks by sending traffic to unwilling victims, periodic consent to\n send needs to be obtained from remote endpoints.\n\n This document describes a consent mechanism using a new Session\n Traversal Utilities for NAT (STUN) usage.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7675.\n\nPerumal, et al. Standards Track [Page 1]\n 7675 http key license revocation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7677","type":"specification","body":"IETF","designation":"RFC 7677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7677.txt","https://www.rfc-editor.org/rfc/rfc7677.pdf"],"folder":"IETF/RFC-7677","files":{"txt":{"path":"standards/IETF/RFC-7677/RFC-7677.txt","sha256":"81490224a838bf5da7bfcce53e4ec1b1d2f69717c43c600111dec6652a386c71"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Simple Authentication and Security Layer\n (SASL) mechanisms SCRAM-SHA-256 and SCRAM-SHA-256-PLUS, provides\n guidance for secure implementation of the original SCRAM-SHA-1-PLUS\n mechanism, and updates the SCRAM registration procedures of RFC 5802.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7677.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the per","scope_keywords":["7677","algorithm","algorithms","authentication","hash","http","key","license","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 7677 This document registers the Simple Authentication and Security Layer\n (SASL) mechanisms SCRAM-SHA-256 and SCRAM-SHA-256-PLUS, provides\n guidance for secure implementation of the original SCRAM-SHA-1-PLUS\n mechanism, and updates the SCRAM registration procedures of RFC 5802.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7677.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the per 7677 algorithm algorithms authentication hash http key license registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7685","type":"specification","body":"IETF","designation":"RFC 7685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7685.txt","https://www.rfc-editor.org/rfc/rfc7685.pdf"],"folder":"IETF/RFC-7685","files":{"txt":{"path":"standards/IETF/RFC-7685/RFC-7685.txt","sha256":"872478b60fa383c204f3de4596648d5f8eeb27a07287725fc5e5ee14d2f61c1b"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a Transport Layer Security (TLS) extension that\n can be used to pad ClientHello messages to a desired size.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7685.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating","scope_keywords":["7685","http","key","license","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 7685 This memo describes a Transport Layer Security (TLS) extension that\n can be used to pad ClientHello messages to a desired size.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7685.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating 7685 http key license registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7693","type":"specification","body":"IETF","designation":"RFC 7693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7693.txt","https://www.rfc-editor.org/rfc/rfc7693.pdf"],"folder":"IETF/RFC-7693","files":{"txt":{"path":"standards/IETF/RFC-7693/RFC-7693.txt","sha256":"c943754888364fe29bbd0bb3c71c6658ef392371497eaa4a9d9dde015b0721e5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the cryptographic hash function BLAKE2 and\n makes the algorithm specification and C source code conveniently\n available to the Internet community. BLAKE2 comes in two main\n flavors: BLAKE2b is optimized for 64-bit platforms and BLAKE2s for\n smaller architectures. BLAKE2 can be directly keyed, making it\n functionally equivalent to a Message Authentication Code (MAC).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informa","scope_keywords":["7693","algorithm","algorithms","authentication","hash","http","key","license","pki","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9106","folder":"IETF/RFC-9106","source":"IETF/RFC-9106/RFC-9106.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 7693 This document describes the cryptographic hash function BLAKE2 and\n makes the algorithm specification and C source code conveniently\n available to the Internet community. BLAKE2 comes in two main\n flavors: BLAKE2b is optimized for 64-bit platforms and BLAKE2s for\n smaller architectures. BLAKE2 can be directly keyed, making it\n functionally equivalent to a Message Authentication Code (MAC).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Informa 7693 algorithm algorithms authentication hash http key license pki signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7694","type":"specification","body":"IETF","designation":"RFC 7694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7694.txt","https://www.rfc-editor.org/rfc/rfc7694.pdf"],"folder":"IETF/RFC-7694","files":{"txt":{"path":"standards/IETF/RFC-7694/RFC-7694.txt","sha256":"d1fa9329036287f4ade0a84cca2a3ed581677cdfda3f2fbc198d9733b2cab4eb"}},"tags":["nested-reference","unchanged"],"summary":"In HTTP, content codings allow for payload encodings such as for\n compression or integrity checks. In particular, the \"gzip\" content\n coding is widely used for payload data sent in response messages.\n\n Content codings can be used in request messages as well; however,\n discoverability is not on par with response messages. This document\n extends the HTTP \"Accept-Encoding\" header field for use in responses,\n to indicate the content codings that are supported in requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cur","scope_keywords":["7694","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7694 In HTTP, content codings allow for payload encodings such as for\n compression or integrity checks. In particular, the \"gzip\" content\n coding is widely used for payload data sent in response messages.\n\n Content codings can be used in request messages as well; however,\n discoverability is not on par with response messages. This document\n extends the HTTP \"Accept-Encoding\" header field for use in responses,\n to indicate the content codings that are supported in requests.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the cur 7694 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7711","type":"specification","body":"IETF","designation":"RFC 7711","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7711.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7711.txt","https://www.rfc-editor.org/rfc/rfc7711.pdf"],"folder":"IETF/RFC-7711","files":{"txt":{"path":"standards/IETF/RFC-7711/RFC-7711.txt","sha256":"8a789f93b66258e12afe09e1a62b6d545c7cf0a0e16ff29c943671dd46f376bd"}},"tags":["nested-reference","unchanged"],"summary":"Experience has shown that it is difficult to deploy proper PKIX\n certificates for Transport Layer Security (TLS) in multi-tenanted\n environments. As a result, domains hosted in such environments often\n deploy applications using certificates that identify the hosting\n service, not the hosted domain. Such deployments force end users and\n peer services to accept a certificate with an improper identifier,\n resulting in degraded security. This document defines methods that\n make it easier to deploy certificates for proper server identity\n checking in non-HTTP application protocols. Although these methods\n were developed for use in the Extensible Messaging and Presence\n Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they\n might also be usable in other non-HTTP application protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product","scope_keywords":["7711","authentication","certificate","certificates","http","https","key","keys","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null}],"search_text":"IETF RFC 7711 Experience has shown that it is difficult to deploy proper PKIX\n certificates for Transport Layer Security (TLS) in multi-tenanted\n environments. As a result, domains hosted in such environments often\n deploy applications using certificates that identify the hosting\n service, not the hosted domain. Such deployments force end users and\n peer services to accept a certificate with an improper identifier,\n resulting in degraded security. This document defines methods that\n make it easier to deploy certificates for proper server identity\n checking in non-HTTP application protocols. Although these methods\n were developed for use in the Extensible Messaging and Presence\n Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they\n might also be usable in other non-HTTP application protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product 7711 authentication certificate certificates http https key keys license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7742","type":"specification","body":"IETF","designation":"RFC 7742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7742.txt","https://www.rfc-editor.org/rfc/rfc7742.pdf"],"folder":"IETF/RFC-7742","files":{"txt":{"path":"standards/IETF/RFC-7742/RFC-7742.txt","sha256":"6aa0b8ad51a6018ff0dcdc2c2dfca8fa0d7760bb1d634d3d1e33ae6e7c1de4f2"}},"tags":["nested-reference","unchanged"],"summary":"This specification provides the requirements and considerations for\n WebRTC applications to send and receive video across a network. It\n specifies the video processing that is required as well as video\n codecs and their parameters.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7742.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. A","scope_keywords":["7742","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7742 This specification provides the requirements and considerations for\n WebRTC applications to send and receive video across a network. It\n specifies the video processing that is required as well as video\n codecs and their parameters.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7742.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. A 7742 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7748","type":"specification","body":"IETF","designation":"RFC 7748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7748.txt","https://www.rfc-editor.org/rfc/rfc7748.pdf"],"folder":"IETF/RFC-7748","files":{"txt":{"path":"standards/IETF/RFC-7748/RFC-7748.txt","sha256":"279ca0ecc5e92e2962e27b846986aeb74729d9dd34bd4a04a362f80dcb596ad3"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies two elliptic curves over prime fields that offer\n a high level of practical security in cryptographic applications,\n including Transport Layer Security (TLS). These curves are intended\n to operate at the ~128-bit and ~224-bit security level, respectively,\n and are generated deterministically based on a list of required\n properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidate for any\n level o","scope_keywords":["7748","algorithm","algorithms","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7925","folder":"IETF/RFC-7925","source":"IETF/RFC-7925/RFC-7925.txt","version":null},{"body":"IETF","designation":"RFC 8032","folder":"IETF/RFC-8032","source":"IETF/RFC-8032/RFC-8032.txt","version":null},{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 7748 This memo specifies two elliptic curves over prime fields that offer\n a high level of practical security in cryptographic applications,\n including Transport Layer Security (TLS). These curves are intended\n to operate at the ~128-bit and ~224-bit security level, respectively,\n and are generated deterministically based on a list of required\n properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidate for any\n level o 7748 algorithm algorithms http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7753","type":"specification","body":"IETF","designation":"RFC 7753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7753.txt","https://www.rfc-editor.org/rfc/rfc7753.pdf"],"folder":"IETF/RFC-7753","files":{"txt":{"path":"standards/IETF/RFC-7753/RFC-7753.txt","sha256":"e3339d58400150d67acb2cbb39a3311e9c038a6a3a95800ebc9167f919ccc5cb"}},"tags":["nested-reference","unchanged"],"summary":"In some use cases, e.g., Lightweight 4over6, the client may require\n not just one port, but a port set. This document defines an\n extension to the Port Control Protocol (PCP) that allows clients to\n manipulate a set of ports as a whole. This is accomplished using a\n new MAP option: PORT_SET.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7753.\n\nSun, et al. Standards Track [Page 1]\n\f\nRFC","scope_keywords":["7753","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7857","folder":"IETF/RFC-7857","source":"IETF/RFC-7857/RFC-7857.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7753 In some use cases, e.g., Lightweight 4over6, the client may require\n not just one port, but a port set. This document defines an\n extension to the Port Control Protocol (PCP) that allows clients to\n manipulate a set of ports as a whole. This is accomplished using a\n new MAP option: PORT_SET.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7753.\n\nSun, et al. Standards Track [Page 1]\n\f\nRFC 7753 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7757","type":"specification","body":"IETF","designation":"RFC 7757","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7757.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7757.txt","https://www.rfc-editor.org/rfc/rfc7757.pdf"],"folder":"IETF/RFC-7757","files":{"txt":{"path":"standards/IETF/RFC-7757/RFC-7757.txt","sha256":"6b9da45fd0ca512983d49e94bc3384a9740bec6c7b5992ff40b8c797e00817bd"}},"tags":["nested-reference","unchanged"],"summary":"This document extends the Stateless IP/ICMP Translation Algorithm\n (SIIT) with an Explicit Address Mapping (EAM) algorithm and formally\n updates RFC 6145. The EAM algorithm facilitates stateless IP/ICMP\n translation between arbitrary (non-IPv4-translatable) IPv6 endpoints\n and IPv4.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7757.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust an","scope_keywords":["7757","algorithm","algorithms","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7757 This document extends the Stateless IP/ICMP Translation Algorithm\n (SIIT) with an Explicit Address Mapping (EAM) algorithm and formally\n updates RFC 6145. The EAM algorithm facilitates stateless IP/ICMP\n translation between arbitrary (non-IPv4-translatable) IPv6 endpoints\n and IPv4.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7757.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust an 7757 algorithm algorithms http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7770","type":"specification","body":"IETF","designation":"RFC 7770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7770.txt","https://www.rfc-editor.org/rfc/rfc7770.pdf"],"folder":"IETF/RFC-7770","files":{"txt":{"path":"standards/IETF/RFC-7770/RFC-7770.txt","sha256":"c55582c08d48c774a827f5879fab9ee41077e109b7878a8a58bae97624701f6f"}},"tags":["nested-reference","unchanged"],"summary":"It is useful for routers in an OSPFv2 or OSPFv3 routing domain to\n know the capabilities of their neighbors and other routers in the\n routing domain. This document proposes extensions to OSPFv2 and\n OSPFv3 for advertising optional router capabilities. The Router\n Information (RI) Link State Advertisement (LSA) is defined for this\n purpose. In OSPFv2, the RI LSA will be implemented with an Opaque\n LSA type ID. In OSPFv3, the RI LSA will be implemented with a unique\n LSA type function code. In both protocols, the RI LSA can be\n advertised at any of the defined flooding scopes (link, area, or\n autonomous system (AS)). This document obsoletes RFC 4970 by\n providing a revised specification that includes support for\n advertisement of multiple instances of the RI LSA and a TLV for\n functional capabilities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a","scope_keywords":["7770","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 7770 It is useful for routers in an OSPFv2 or OSPFv3 routing domain to\n know the capabilities of their neighbors and other routers in the\n routing domain. This document proposes extensions to OSPFv2 and\n OSPFv3 for advertising optional router capabilities. The Router\n Information (RI) Link State Advertisement (LSA) is defined for this\n purpose. In OSPFv2, the RI LSA will be implemented with an Opaque\n LSA type ID. In OSPFv3, the RI LSA will be implemented with a unique\n LSA type function code. In both protocols, the RI LSA can be\n advertised at any of the defined flooding scopes (link, area, or\n autonomous system (AS)). This document obsoletes RFC 4970 by\n providing a revised specification that includes support for\n advertisement of multiple instances of the RI LSA and a TLV for\n functional capabilities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a 7770 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7797","type":"specification","body":"IETF","designation":"RFC 7797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7797.txt","https://www.rfc-editor.org/rfc/rfc7797.pdf"],"folder":"IETF/RFC-7797","files":{"txt":{"path":"standards/IETF/RFC-7797/RFC-7797.txt","sha256":"5bbed0e2df28126e147f79dde99058fd1ca18977b7f9f0e5e75626d8efa31138"}},"tags":["nested-reference","unchanged"],"summary":"JSON Web Signature (JWS) represents the payload of a JWS as a\n base64url-encoded value and uses this value in the JWS Signature\n computation. While this enables arbitrary payloads to be integrity\n protected, some have described use cases in which the base64url\n encoding is unnecessary and/or an impediment to adoption, especially\n when the payload is large and/or detached. This specification\n defines a means of accommodating these use cases by defining an\n option to change the JWS Signing Input computation to not base64url-\n encode the payload. This option is intended to broaden the set of\n use cases for which the use of JWS is a good fit.\n\n This specification updates RFC 7519 by stating that JSON Web Tokens\n (JWTs) MUST NOT use the unencoded payload option defined by this\n specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of ","scope_keywords":["7797","algorithm","algorithms","authentication","encryption","http","key","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 7797 JSON Web Signature (JWS) represents the payload of a JWS as a\n base64url-encoded value and uses this value in the JWS Signature\n computation. While this enables arbitrary payloads to be integrity\n protected, some have described use cases in which the base64url\n encoding is unnecessary and/or an impediment to adoption, especially\n when the payload is large and/or detached. This specification\n defines a means of accommodating these use cases by defining an\n option to change the JWS Signing Input computation to not base64url-\n encode the payload. This option is intended to broaden the set of\n use cases for which the use of JWS is a good fit.\n\n This specification updates RFC 7519 by stating that JSON Web Tokens\n (JWTs) MUST NOT use the unencoded payload option defined by this\n specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of  7797 algorithm algorithms authentication encryption http key license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7799","type":"specification","body":"IETF","designation":"RFC 7799","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7799.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7799.txt","https://www.rfc-editor.org/rfc/rfc7799.pdf"],"folder":"IETF/RFC-7799","files":{"txt":{"path":"standards/IETF/RFC-7799/RFC-7799.txt","sha256":"d78239d92dfc746d65f2cf7eab47d98992f344e797a7528c49cb38a71ae4bb6d"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides clear definitions for Active and Passive\n performance assessment. The construction of Metrics and Methods can\n be described as either \"Active\" or \"Passive\". Some methods may use a\n subset of both Active and Passive attributes, and we refer to these\n as \"Hybrid Methods\". This memo also describes multiple dimensions to\n help evaluate new methods as they emerge.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abou","scope_keywords":["7799","attribute","attributes","http","https","key","license","path","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7799 This memo provides clear definitions for Active and Passive\n performance assessment. The construction of Metrics and Methods can\n be described as either \"Active\" or \"Passive\". Some methods may use a\n subset of both Active and Passive attributes, and we refer to these\n as \"Hybrid Methods\". This memo also describes multiple dimensions to\n help evaluate new methods as they emerge.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abou 7799 attribute attributes http https key license path presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7800","type":"specification","body":"IETF","designation":"RFC 7800","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7800.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7800.txt","https://www.rfc-editor.org/rfc/rfc7800.pdf"],"folder":"IETF/RFC-7800","files":{"txt":{"path":"standards/IETF/RFC-7800/RFC-7800.txt","sha256":"051514a781038027c2ac07c26ebe8533556012b2353cdaec8f3baeac53a7c919"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification describes how to declare in a JSON Web Token (JWT)\n that the presenter of the JWT possesses a particular proof-of-\n possession key and how the recipient can cryptographically confirm\n proof of possession of the key by the presenter. Being able to prove\n possession of a key is also sometimes described as the presenter\n being a holder-of-key.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc","scope_keywords":["7800","encryption","holder","http","issuer","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 7800 This specification describes how to declare in a JSON Web Token (JWT)\n that the presenter of the JWT possesses a particular proof-of-\n possession key and how the recipient can cryptographically confirm\n proof of possession of the key by the presenter. Being able to prove\n possession of a key is also sometimes described as the presenter\n being a holder-of-key.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc 7800 encryption holder http issuer key keys license presentation subject trust cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 7807","type":"specification","body":"IETF","designation":"RFC 7807","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7807.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7807.txt","https://www.rfc-editor.org/rfc/rfc7807.pdf"],"folder":"IETF/RFC-7807","files":{"txt":{"path":"standards/IETF/RFC-7807/RFC-7807.txt","sha256":"c6ee12b7109d42ed3e68659da5f67397bd573226d86492fecf7d954f5f6ca03e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a \"problem detail\" as a way to carry machine-\n readable details of errors in a HTTP response to avoid the need to\n define new error response formats for HTTP APIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7807.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject","scope_keywords":["7807","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null}],"search_text":"IETF RFC 7807 This document defines a \"problem detail\" as a way to carry machine-\n readable details of errors in a HTTP response to avoid the need to\n define new error response formats for HTTP APIs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7807.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject 7807 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7822","type":"specification","body":"IETF","designation":"RFC 7822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7822.txt","https://www.rfc-editor.org/rfc/rfc7822.pdf"],"folder":"IETF/RFC-7822","files":{"txt":{"path":"standards/IETF/RFC-7822/RFC-7822.txt","sha256":"0c0a7b2d6ef27fbd0f27cf25e5b88358e7e9d9614ea83dbf418acd7c3f361f6e"}},"tags":["nested-reference","unchanged"],"summary":"The Network Time Protocol version 4 (NTPv4) defines the optional\n usage of extension fields. An extension field, as defined in RFC\n 5905, is an optional field that resides at the end of the NTP header\n and that can be used to add optional capabilities or additional\n information that is not conveyed in the standard NTP header. This\n document updates RFC 5905 by clarifying some points regarding NTP\n extension fields and their usage with Message Authentication Codes\n (MACs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the","scope_keywords":["7822","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null}],"search_text":"IETF RFC 7822 The Network Time Protocol version 4 (NTPv4) defines the optional\n usage of extension fields. An extension field, as defined in RFC\n 5905, is an optional field that resides at the end of the NTP header\n and that can be used to add optional capabilities or additional\n information that is not conveyed in the standard NTP header. This\n document updates RFC 5905 by clarifying some points regarding NTP\n extension fields and their usage with Message Authentication Codes\n (MACs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the 7822 authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7825","type":"specification","body":"IETF","designation":"RFC 7825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7825.txt","https://www.rfc-editor.org/rfc/rfc7825.pdf"],"folder":"IETF/RFC-7825","files":{"txt":{"path":"standards/IETF/RFC-7825/RFC-7825.txt","sha256":"57b71e4c953ffa6074516c381822d32c63f9a04cb1a865ea0c3642471902ac29"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a solution for Network Address Translation\n (NAT) traversal for datagram-based media streams set up and\n controlled with the Real-Time Streaming Protocol version 2 (RTSP\n 2.0). It uses Interactive Connectivity Establishment (ICE) adapted\n to use RTSP as a signaling channel, defining the necessary RTSP\n extensions and procedures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o","scope_keywords":["7825","attribute","http","key","license","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 7825 This document defines a solution for Network Address Translation\n (NAT) traversal for datagram-based media streams set up and\n controlled with the Real-Time Streaming Protocol version 2 (RTSP\n 2.0). It uses Interactive Connectivity Establishment (ICE) adapted\n to use RTSP as a signaling channel, defining the necessary RTSP\n extensions and procedures.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.o 7825 attribute http key license subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 7838","type":"specification","body":"IETF","designation":"RFC 7838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7838.txt","https://www.rfc-editor.org/rfc/rfc7838.pdf"],"folder":"IETF/RFC-7838","files":{"txt":{"path":"standards/IETF/RFC-7838/RFC-7838.txt","sha256":"ac2ee358ed7406e8128fc85ada8a1891de54b963bd7d47875e290a23a4e95021"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies \"Alternative Services\" for HTTP, which allow\n an origin's resources to be authoritatively available at a separate\n network location, possibly accessed with a different protocol\n configuration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7838.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reser","scope_keywords":["7838","authentication","http","https","identification","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 7838 This document specifies \"Alternative Services\" for HTTP, which allow\n an origin's resources to be authoritatively available at a separate\n network location, possibly accessed with a different protocol\n configuration.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7838.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reser 7838 authentication http https identification key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7850","type":"specification","body":"IETF","designation":"RFC 7850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7850.txt","https://www.rfc-editor.org/rfc/rfc7850.pdf"],"folder":"IETF/RFC-7850","files":{"txt":{"path":"standards/IETF/RFC-7850/RFC-7850.txt","sha256":"bd929dbbf8b1d944eec9fab5009fffc29132692aa16182315026f04d316eadad"}},"tags":["nested-reference","unchanged"],"summary":"The Real-time Transport Protocol (RTP) specification establishes a\n registry of profile names for use by higher-level control protocols,\n such as the Session Description Protocol (SDP), to refer to the\n transport methods. This specification describes the following new\n SDP transport protocol identifiers for transporting RTP Media over\n TCP: 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF',\n 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', and\n 'TCP/TLS/RTP/AVPF'.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about ","scope_keywords":["7850","delivery","http","identification","key","license","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null}],"search_text":"IETF RFC 7850 The Real-time Transport Protocol (RTP) specification establishes a\n registry of profile names for use by higher-level control protocols,\n such as the Session Description Protocol (SDP), to refer to the\n transport methods. This specification describes the following new\n SDP transport protocol identifiers for transporting RTP Media over\n TCP: 'TCP/RTP/AVPF', 'TCP/RTP/SAVP', 'TCP/RTP/SAVPF',\n 'TCP/DTLS/RTP/SAVP', 'TCP/DTLS/RTP/SAVPF', 'TCP/TLS/RTP/AVP', and\n 'TCP/TLS/RTP/AVPF'.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about  7850 delivery http identification key license profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7857","type":"specification","body":"IETF","designation":"RFC 7857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7857.txt","https://www.rfc-editor.org/rfc/rfc7857.pdf"],"folder":"IETF/RFC-7857","files":{"txt":{"path":"standards/IETF/RFC-7857/RFC-7857.txt","sha256":"92b72ebfdcca49c9a412275a90502a8c0a4ffffcc4400c1644d296e8043f06d6"}},"tags":["nested-reference","unchanged"],"summary":"This document clarifies and updates several requirements of RFCs\n 4787, 5382, and 5508 based on operational and development experience.\n The focus of this document is Network Address Translation from IPv4\n to IPv4 (NAT44).\n\n This document updates RFCs 4787, 5382, and 5508.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7857.\n\nPenno, et al. Best Current Practice [Page 1]\n\f\nRFC 7857 Updates to","scope_keywords":["7857","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null}],"search_text":"IETF RFC 7857 This document clarifies and updates several requirements of RFCs\n 4787, 5382, and 5508 based on operational and development experience.\n The focus of this document is Network Address Translation from IPv4\n to IPv4 (NAT44).\n\n This document updates RFCs 4787, 5382, and 5508.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7857.\n\nPenno, et al. Best Current Practice [Page 1]\n\f\nRFC 7857 Updates to 7857 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7874","type":"specification","body":"IETF","designation":"RFC 7874","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7874.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7874.txt","https://www.rfc-editor.org/rfc/rfc7874.pdf"],"folder":"IETF/RFC-7874","files":{"txt":{"path":"standards/IETF/RFC-7874/RFC-7874.txt","sha256":"8f5e658b22b71a60d4821c0f3678963b9d61c37ea3cf6ad9dc075704ff9f5e87"}},"tags":["nested-reference","unchanged"],"summary":"This document outlines the audio codec and processing requirements\n for WebRTC endpoints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7874.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ie","scope_keywords":["7874","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7874 This document outlines the audio codec and processing requirements\n for WebRTC endpoints.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7874.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ie 7874 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7889","type":"specification","body":"IETF","designation":"RFC 7889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7889.txt","https://www.rfc-editor.org/rfc/rfc7889.pdf"],"folder":"IETF/RFC-7889","files":{"txt":{"path":"standards/IETF/RFC-7889/RFC-7889.txt","sha256":"31802a849f5e000ec3af5f85bea222698209597cded807fefd4904777a667869"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the IMAP service whereby a\n server can inform the client about maximum message upload sizes,\n allowing the client to avoid sending APPEND commands that will fail\n because the messages are too large.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7889.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document autho","scope_keywords":["7889","attribute","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null}],"search_text":"IETF RFC 7889 This document defines an extension to the IMAP service whereby a\n server can inform the client about maximum message upload sizes,\n allowing the client to avoid sending APPEND commands that will fail\n because the messages are too large.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7889.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document autho 7889 attribute http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7895","type":"specification","body":"IETF","designation":"RFC 7895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7895.txt","https://www.rfc-editor.org/rfc/rfc7895.pdf"],"folder":"IETF/RFC-7895","files":{"txt":{"path":"standards/IETF/RFC-7895/RFC-7895.txt","sha256":"91b802b109a3671578067707085608ea45bdf71cabb78d50eaecbdb2af128454"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a YANG library that provides information\n about all the YANG modules used by a network management server (e.g.,\n a Network Configuration Protocol (NETCONF) server). Simple caching\n mechanisms are provided to allow clients to minimize retrieval of\n this information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7895.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Tr","scope_keywords":["7895","http","key","keys","license","management","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8022","folder":"IETF/RFC-8022","source":"IETF/RFC-8022/RFC-8022.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 7895 This document describes a YANG library that provides information\n about all the YANG modules used by a network management server (e.g.,\n a Network Configuration Protocol (NETCONF) server). Simple caching\n mechanisms are provided to allow clients to minimize retrieval of\n this information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7895.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Tr 7895 http key keys license management presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7919","type":"specification","body":"IETF","designation":"RFC 7919","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7919.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7919.txt","https://www.rfc-editor.org/rfc/rfc7919.pdf"],"folder":"IETF/RFC-7919","files":{"txt":{"path":"standards/IETF/RFC-7919/RFC-7919.txt","sha256":"e7ffd3d8109670aa48d218964ceccf82cc6d2fd36132403c89589434bf8a4d72"}},"tags":["nested-reference","unchanged"],"summary":"Traditional finite-field-based Diffie-Hellman (DH) key exchange\n during the Transport Layer Security (TLS) handshake suffers from a\n number of security, interoperability, and efficiency shortcomings.\n These shortcomings arise from lack of clarity about which DH group\n parameters TLS servers should offer and clients should accept. This\n document offers a solution to these shortcomings for compatible peers\n by using a section of the TLS \"Supported Groups Registry\" (renamed\n from \"EC Named Curve Registry\" by this document) to establish common\n finite field DH parameters with known structure and a mechanism for\n peers to negotiate support for these groups.\n\n This document updates TLS versions 1.0 (RFC 2246), 1.1 (RFC 4346),\n and 1.2 (RFC 5246), as well as the TLS Elliptic Curve Cryptography\n (ECC) extensions (RFC 4492).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n T","scope_keywords":["7919","http","key","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7919 Traditional finite-field-based Diffie-Hellman (DH) key exchange\n during the Transport Layer Security (TLS) handshake suffers from a\n number of security, interoperability, and efficiency shortcomings.\n These shortcomings arise from lack of clarity about which DH group\n parameters TLS servers should offer and clients should accept. This\n document offers a solution to these shortcomings for compatible peers\n by using a section of the TLS \"Supported Groups Registry\" (renamed\n from \"EC Named Curve Registry\" by this document) to establish common\n finite field DH parameters with known structure and a mechanism for\n peers to negotiate support for these groups.\n\n This document updates TLS versions 1.0 (RFC 2246), 1.1 (RFC 4346),\n and 1.2 (RFC 5246), as well as the TLS Elliptic Curve Cryptography\n (ECC) extensions (RFC 4492).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n T 7919 http key license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7941","type":"specification","body":"IETF","designation":"RFC 7941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7941.txt","https://www.rfc-editor.org/rfc/rfc7941.pdf"],"folder":"IETF/RFC-7941","files":{"txt":{"path":"standards/IETF/RFC-7941/RFC-7941.txt","sha256":"3589765c376d37c0e2d8e7e9f4454927789b40be94cff8700ae20f7f524501bf"}},"tags":["nested-reference","unchanged"],"summary":"Source Description (SDES) items are normally transported in the RTP\n Control Protocol (RTCP). In some cases, it can be beneficial to\n speed up the delivery of these items. The main case is when a new\n synchronization source (SSRC) joins an RTP session and the receivers\n need this source's identity, relation to other sources, or its\n synchronization context, all of which may be fully or partially\n identified using SDES items. To enable this optimization, this\n document specifies a new RTP header extension that can carry SDES\n items.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards i","scope_keywords":["7941","delivery","http","key","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 7941 Source Description (SDES) items are normally transported in the RTP\n Control Protocol (RTCP). In some cases, it can be beneficial to\n speed up the delivery of these items. The main case is when a new\n synchronization source (SSRC) joins an RTP session and the receivers\n need this source's identity, relation to other sources, or its\n synchronization context, all of which may be fully or partially\n identified using SDES items. To enable this optimization, this\n document specifies a new RTP header extension that can carry SDES\n items.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards i 7941 delivery http key license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 7952","type":"specification","body":"IETF","designation":"RFC 7952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7952.txt","https://www.rfc-editor.org/rfc/rfc7952.pdf"],"folder":"IETF/RFC-7952","files":{"txt":{"path":"standards/IETF/RFC-7952/RFC-7952.txt","sha256":"5a53bf3774059569bef895841fb17ec27d700f0d5f7d4ea6daaf63e8bba59209"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG extension that allows for defining\n metadata annotations in YANG modules. The document also specifies\n XML and JSON encoding of annotations and other rules for annotating\n instances of YANG data nodes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7952.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. Al","scope_keywords":["7952","attribute","attributes","http","key","license","management","registered","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null}],"search_text":"IETF RFC 7952 This document defines a YANG extension that allows for defining\n metadata annotations in YANG modules. The document also specifies\n XML and JSON encoding of annotations and other rules for annotating\n instances of YANG data nodes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7952.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. Al 7952 attribute attributes http key license management registered risk subject trust nested-reference unchanged"},{"id":"IETF RFC 7967","type":"specification","body":"IETF","designation":"RFC 7967","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7967.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7967.txt","https://www.rfc-editor.org/rfc/rfc7967.pdf"],"folder":"IETF/RFC-7967","files":{"txt":{"path":"standards/IETF/RFC-7967/RFC-7967.txt","sha256":"c11726bc1462597ffbbff5e7427c50673556fe6074c050893015c52c1e260103"}},"tags":["nested-reference","unchanged"],"summary":"There can be machine-to-machine (M2M) scenarios where server\n responses to client requests are redundant. This kind of open-loop\n exchange (with no response path from the server to the client) may be\n desired to minimize resource consumption in constrained systems while\n updating many resources simultaneously or performing high-frequency\n updates. CoAP already provides Non-confirmable (NON) messages that\n are not acknowledged by the recipient. However, the request/response\n semantics still require the server to respond with a status code\n indicating \"the result of the attempt to understand and satisfy the\n request\", per RFC 7252.\n\n This specification introduces a CoAP option called 'No-Response'.\n Using this option, the client can explicitly express to the server\n its disinterest in all responses against the particular request.\n This option also provides granular control to enable expres","scope_keywords":["7967","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 7967 There can be machine-to-machine (M2M) scenarios where server\n responses to client requests are redundant. This kind of open-loop\n exchange (with no response path from the server to the client) may be\n desired to minimize resource consumption in constrained systems while\n updating many resources simultaneously or performing high-frequency\n updates. CoAP already provides Non-confirmable (NON) messages that\n are not acknowledged by the recipient. However, the request/response\n semantics still require the server to respond with a status code\n indicating \"the result of the attempt to understand and satisfy the\n request\", per RFC 7252.\n\n This specification introduces a CoAP option called 'No-Response'.\n Using this option, the client can explicitly express to the server\n its disinterest in all responses against the particular request.\n This option also provides granular control to enable expres 7967 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7975","type":"specification","body":"IETF","designation":"RFC 7975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7975.txt","https://www.rfc-editor.org/rfc/rfc7975.pdf"],"folder":"IETF/RFC-7975","files":{"txt":{"path":"standards/IETF/RFC-7975/RFC-7975.txt","sha256":"44876cf564ec0c741d283668eaf6360f561482d9f5c96e824208fa8adefd661d"}},"tags":["nested-reference","unchanged"],"summary":"The Request Routing interface comprises (1) the asynchronous\n advertisement of footprint and capabilities by a downstream Content\n Delivery Network (CDN) that allows an upstream CDN to decide whether\n to redirect particular user requests to that downstream CDN; and (2)\n the synchronous operation of an upstream CDN requesting whether a\n downstream CDN is prepared to accept a user request and of a\n downstream CDN responding with how to actually redirect the user\n request. This document describes an interface for the latter part,\n i.e., the CDNI Request Routing Redirection interface.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (I","scope_keywords":["7975","authentication","authorization","delivery","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null}],"search_text":"IETF RFC 7975 The Request Routing interface comprises (1) the asynchronous\n advertisement of footprint and capabilities by a downstream Content\n Delivery Network (CDN) that allows an upstream CDN to decide whether\n to redirect particular user requests to that downstream CDN; and (2)\n the synchronous operation of an upstream CDN requesting whether a\n downstream CDN is prepared to accept a user request and of a\n downstream CDN responding with how to actually redirect the user\n request. This document describes an interface for the latter part,\n i.e., the CDNI Request Routing Redirection interface.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (I 7975 authentication authorization delivery http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7977","type":"specification","body":"IETF","designation":"RFC 7977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7977.txt","https://www.rfc-editor.org/rfc/rfc7977.pdf"],"folder":"IETF/RFC-7977","files":{"txt":{"path":"standards/IETF/RFC-7977/RFC-7977.txt","sha256":"fecd834a016c6789588252fc408c6929bee607bb5bfefcfc8602ab7c6eb72e8d"}},"tags":["nested-reference","unchanged"],"summary":"The WebSocket protocol enables two-way real-time communication\n between clients and servers in situations where direct access to TCP\n and UDP is not available (for example, from within JavaScript in a\n web browser). This document specifies a new WebSocket subprotocol as\n a reliable transport mechanism between Message Session Relay Protocol\n (MSRP) clients and relays to enable usage of MSRP in new scenarios.\n This document normatively updates RFCs 4975 and 4976.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current st","scope_keywords":["7977","authentication","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 7977 The WebSocket protocol enables two-way real-time communication\n between clients and servers in situations where direct access to TCP\n and UDP is not available (for example, from within JavaScript in a\n web browser). This document specifies a new WebSocket subprotocol as\n a reliable transport mechanism between Message Session Relay Protocol\n (MSRP) clients and relays to enable usage of MSRP in new scenarios.\n This document normatively updates RFCs 4975 and 4976.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current st 7977 authentication http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7983","type":"specification","body":"IETF","designation":"RFC 7983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7983.txt","https://www.rfc-editor.org/rfc/rfc7983.pdf"],"folder":"IETF/RFC-7983","files":{"txt":{"path":"standards/IETF/RFC-7983/RFC-7983.txt","sha256":"be205744e19a0bb4d83f9a37c9d0662d2bfc6f373d1551c468397af46ea4cecc"}},"tags":["nested-reference","unchanged"],"summary":"This document defines how Datagram Transport Layer Security (DTLS),\n Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),\n Session Traversal Utilities for NAT (STUN), Traversal Using Relays\n around NAT (TURN), and ZRTP packets are multiplexed on a single\n receiving socket. It overrides the guidance from RFC 5764 (\"SRTP\n Extension for DTLS\"), which suffered from four issues described and\n fixed in this document.\n\n This document updates RFC 5764.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status ","scope_keywords":["7983","algorithm","http","key","keys","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 7983 This document defines how Datagram Transport Layer Security (DTLS),\n Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),\n Session Traversal Utilities for NAT (STUN), Traversal Using Relays\n around NAT (TURN), and ZRTP packets are multiplexed on a single\n receiving socket. It overrides the guidance from RFC 5764 (\"SRTP\n Extension for DTLS\"), which suffered from four issues described and\n fixed in this document.\n\n This document updates RFC 5764.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status  7983 algorithm http key keys license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8008","type":"specification","body":"IETF","designation":"RFC 8008","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8008.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8008.txt","https://www.rfc-editor.org/rfc/rfc8008.pdf"],"folder":"IETF/RFC-8008","files":{"txt":{"path":"standards/IETF/RFC-8008/RFC-8008.txt","sha256":"3ca8eddb69b9625152853326af30b78564c2408950d3e102e26db663453f5ae0"}},"tags":["nested-reference","unchanged"],"summary":"This document captures the semantics of the \"Footprint and\n Capabilities Advertisement\" part of the Content Delivery Network\n Interconnection (CDNI) Request Routing interface, i.e., the desired\n meaning of \"Footprint\" and \"Capabilities\" in the CDNI context and\n what the \"Footprint & Capabilities Advertisement interface (FCI)\"\n offers within CDNI. The document also provides guidelines for the\n CDNI FCI protocol. It further defines a Base Advertisement Object,\n the necessary registries for capabilities and footprints, and\n guidelines on how these registries can be extended in the future.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Gro","scope_keywords":["8008","delivery","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null}],"search_text":"IETF RFC 8008 This document captures the semantics of the \"Footprint and\n Capabilities Advertisement\" part of the Content Delivery Network\n Interconnection (CDNI) Request Routing interface, i.e., the desired\n meaning of \"Footprint\" and \"Capabilities\" in the CDNI context and\n what the \"Footprint & Capabilities Advertisement interface (FCI)\"\n offers within CDNI. The document also provides guidelines for the\n CDNI FCI protocol. It further defines a Base Advertisement Object,\n the necessary registries for capabilities and footprints, and\n guidelines on how these registries can be extended in the future.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Gro 8008 delivery http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8022","type":"specification","body":"IETF","designation":"RFC 8022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8022.txt","https://www.rfc-editor.org/rfc/rfc8022.pdf"],"folder":"IETF/RFC-8022","files":{"txt":{"path":"standards/IETF/RFC-8022/RFC-8022.txt","sha256":"e9e7b34ce7931dc1ba6f0057c6554ea9c6ef679efd2f6b2c642a94e60827ee0c"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a specification of three YANG modules and one\n submodule. Together they form the core routing data model that\n serves as a framework for configuring and managing a routing\n subsystem. It is expected that these modules will be augmented by\n additional YANG modules defining data models for control-plane\n protocols, route filters, and other functions. The core routing data\n model provides common building blocks for such extensions -- routes,\n Routing Information Bases (RIBs), and control-plane protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availa","scope_keywords":["8022","http","key","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null}],"search_text":"IETF RFC 8022 This document contains a specification of three YANG modules and one\n submodule. Together they form the core routing data model that\n serves as a framework for configuring and managing a routing\n subsystem. It is expected that these modules will be augmented by\n additional YANG modules defining data models for control-plane\n protocols, route filters, and other functions. The core routing data\n model provides common building blocks for such extensions -- routes,\n Routing Information Bases (RIBs), and control-plane protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availa 8022 http key license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8027","type":"specification","body":"IETF","designation":"RFC 8027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8027.txt","https://www.rfc-editor.org/rfc/rfc8027.pdf"],"folder":"IETF/RFC-8027","files":{"txt":{"path":"standards/IETF/RFC-8027/RFC-8027.txt","sha256":"edaf9c3055b022f89307a377735d00697959ecc95ba4707535c7158dbaeea4cf"}},"tags":["nested-reference","unchanged"],"summary":"This document describes problems that a Validating DNS resolver,\n stub-resolver, or application might run into within a non-compliant\n infrastructure. It outlines potential detection and mitigation\n techniques. The scope of the document is to create a shared approach\n to detect and overcome network issues that a DNSSEC software/system\n may face.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf","scope_keywords":["8027","algorithm","algorithms","http","key","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null}],"search_text":"IETF RFC 8027 This document describes problems that a Validating DNS resolver,\n stub-resolver, or application might run into within a non-compliant\n infrastructure. It outlines potential detection and mitigation\n techniques. The scope of the document is to create a shared approach\n to detect and overcome network issues that a DNSSEC software/system\n may face.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf 8027 algorithm algorithms http key license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8030","type":"specification","body":"IETF","designation":"RFC 8030","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8030.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8030.txt","https://www.rfc-editor.org/rfc/rfc8030.pdf"],"folder":"IETF/RFC-8030","files":{"txt":{"path":"standards/IETF/RFC-8030/RFC-8030.txt","sha256":"bc8b9646c153e2d1ac79b35e1d8850a92608fabf6fae8a54b223dc39791a0e13"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple protocol for the delivery of real-\n time events to user agents. This scheme uses HTTP/2 server push.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8030.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re","scope_keywords":["8030","authorization","delivery","http","key","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 8030 This document describes a simple protocol for the delivery of real-\n time events to user agents. This scheme uses HTTP/2 server push.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8030.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Re 8030 authorization delivery http key license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 8032","type":"specification","body":"IETF","designation":"RFC 8032","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8032.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8032.txt","https://www.rfc-editor.org/rfc/rfc8032.pdf"],"folder":"IETF/RFC-8032","files":{"txt":{"path":"standards/IETF/RFC-8032/RFC-8032.txt","sha256":"ed63657ff389301282b169b0abde9b5dd2c7e4d524fdfa5da6ff3094fc93c4c3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes elliptic curve signature scheme Edwards-curve\n Digital Signature Algorithm (EdDSA). The algorithm is instantiated\n with recommended parameters for the edwards25519 and edwards448\n curves. An example implementation and test vectors are provided.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidate for any\n level of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current statu","scope_keywords":["8032","algorithm","hash","http","key","keys","license","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8037","folder":"IETF/RFC-8037","source":"IETF/RFC-8037/RFC-8037.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null}],"search_text":"IETF RFC 8032 This document describes elliptic curve signature scheme Edwards-curve\n Digital Signature Algorithm (EdDSA). The algorithm is instantiated\n with recommended parameters for the edwards25519 and edwards448\n curves. An example implementation and test vectors are provided.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not a candidate for any\n level of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current statu 8032 algorithm hash http key keys license signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8035","type":"specification","body":"IETF","designation":"RFC 8035","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8035.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8035.txt","https://www.rfc-editor.org/rfc/rfc8035.pdf"],"folder":"IETF/RFC-8035","files":{"txt":{"path":"standards/IETF/RFC-8035/RFC-8035.txt","sha256":"66729c8a0d15f9936a636f2af3a1d05839e122448815d731424aad6ebdfd7db6"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 5761 by clarifying the SDP offer/answer\n negotiation of RTP and RTP Control Protocol (RTCP) multiplexing. It\n makes it clear that an answerer can only include an \"a=rtcp-mux\"\n attribute in a Session Description Protocol (SDP) answer if the\n associated SDP offer contained the attribute.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8035.\n\nHolmberg Standards Tra","scope_keywords":["8035","attribute","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null}],"search_text":"IETF RFC 8035 This document updates RFC 5761 by clarifying the SDP offer/answer\n negotiation of RTP and RTP Control Protocol (RTCP) multiplexing. It\n makes it clear that an answerer can only include an \"a=rtcp-mux\"\n attribute in a Session Description Protocol (SDP) answer if the\n associated SDP offer contained the attribute.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8035.\n\nHolmberg Standards Tra 8035 attribute http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8037","type":"specification","body":"IETF","designation":"RFC 8037","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8037.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8037.txt","https://www.rfc-editor.org/rfc/rfc8037.pdf"],"folder":"IETF/RFC-8037","files":{"txt":{"path":"standards/IETF/RFC-8037/RFC-8037.txt","sha256":"f14347f9d8eead78ef6e7a1ea3d795d35d664033095a76a80fcd567904aaedaa"}},"tags":["nested-reference","unchanged"],"summary":"This document defines how to use the Diffie-Hellman algorithms\n \"X25519\" and \"X448\" as well as the signature algorithms \"Ed25519\" and\n \"Ed448\" from the IRTF CFRG elliptic curves work in JSON Object\n Signing and Encryption (JOSE).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8037.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All","scope_keywords":["8037","algorithm","algorithms","encryption","hash","http","key","keys","license","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null}],"search_text":"IETF RFC 8037 This document defines how to use the Diffie-Hellman algorithms\n \"X25519\" and \"X448\" as well as the signature algorithms \"Ed25519\" and\n \"Ed448\" from the IRTF CFRG elliptic curves work in JSON Object\n Signing and Encryption (JOSE).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8037.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All 8037 algorithm algorithms encryption hash http key keys license signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8053","type":"specification","body":"IETF","designation":"RFC 8053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8053.txt","https://www.rfc-editor.org/rfc/rfc8053.pdf"],"folder":"IETF/RFC-8053","files":{"txt":{"path":"standards/IETF/RFC-8053/RFC-8053.txt","sha256":"1b15253bce813d1417d253214fa6580c71b811dfc11604fe68c24e385c1f86be"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies extensions for the HTTP authentication\n framework for interactive clients. Currently, fundamental features\n of HTTP-level authentication are insufficient for complex\n requirements of various Web-based applications. This forces these\n applications to implement their own authentication frameworks by\n means such as HTML forms, which becomes one of the hurdles against\n introducing secure authentication mechanisms handled jointly by\n servers and user agents. The extended framework fills gaps between\n Web application requirements and HTTP authentication provisions to\n solve the above problems, while maintaining compatibility with\n existing Web and non-Web uses of HTTP authentication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document define","scope_keywords":["8053","authentication","http","key","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null}],"search_text":"IETF RFC 8053 This document specifies extensions for the HTTP authentication\n framework for interactive clients. Currently, fundamental features\n of HTTP-level authentication are insufficient for complex\n requirements of various Web-based applications. This forces these\n applications to implement their own authentication frameworks by\n means such as HTML forms, which becomes one of the hurdles against\n introducing secure authentication mechanisms handled jointly by\n servers and user agents. The extended framework fills gaps between\n Web application requirements and HTTP authentication provisions to\n solve the above problems, while maintaining compatibility with\n existing Web and non-Web uses of HTTP authentication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document define 8053 authentication http key license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 8055","type":"specification","body":"IETF","designation":"RFC 8055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8055.txt","https://www.rfc-editor.org/rfc/rfc8055.pdf"],"folder":"IETF/RFC-8055","files":{"txt":{"path":"standards/IETF/RFC-8055/RFC-8055.txt","sha256":"181e4d18233eed60519bc7792a50ea2ca51422d148fe647b09703a4c20e5f806"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a new Session Initiation Protocol (SIP)\n Via header field parameter, 'received-realm', which allows a SIP\n entity acting as an entry point to a transit network to indicate from\n which adjacent upstream network a SIP request is received by using a\n network realm value associated with the adjacent network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8055.\n\nCo","scope_keywords":["8055","http","license","policies","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null}],"search_text":"IETF RFC 8055 This specification defines a new Session Initiation Protocol (SIP)\n Via header field parameter, 'received-realm', which allows a SIP\n entity acting as an entry point to a transit network to indicate from\n which adjacent upstream network a SIP request is received by using a\n network realm value associated with the adjacent network.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8055.\n\nCo 8055 http license policies profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8075","type":"specification","body":"IETF","designation":"RFC 8075","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8075.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8075.txt","https://www.rfc-editor.org/rfc/rfc8075.pdf"],"folder":"IETF/RFC-8075","files":{"txt":{"path":"standards/IETF/RFC-8075/RFC-8075.txt","sha256":"873cae04616063d3d1c4d1c7c47d778b2c8680785b56b302bd0a9061093cdd61"}},"tags":["nested-reference","unchanged"],"summary":"This document provides reference information for implementing a\n cross-protocol network proxy that performs translation from the HTTP\n protocol to the Constrained Application Protocol (CoAP). This will\n enable an HTTP client to access resources on a CoAP server through\n the proxy. This document describes how an HTTP request is mapped to\n a CoAP request and how a CoAP response is mapped back to an HTTP\n response. This includes guidelines for status code, URI, and media\n type mappings, as well as additional interworking advice.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai","scope_keywords":["8075","algorithm","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 8075 This document provides reference information for implementing a\n cross-protocol network proxy that performs translation from the HTTP\n protocol to the Constrained Application Protocol (CoAP). This will\n enable an HTTP client to access resources on a CoAP server through\n the proxy. This document describes how an HTTP request is mapped to\n a CoAP request and how a CoAP response is mapped back to an HTTP\n response. This includes guidelines for status code, URI, and media\n type mappings, as well as additional interworking advice.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai 8075 algorithm http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8078","type":"specification","body":"IETF","designation":"RFC 8078","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8078.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8078.txt","https://www.rfc-editor.org/rfc/rfc8078.pdf"],"folder":"IETF/RFC-8078","files":{"txt":{"path":"standards/IETF/RFC-8078/RFC-8078.txt","sha256":"022c1ad3ec8eb52bf3bbf55939110256605301af6fd040dbbac300b0d3c6ede3"}},"tags":["nested-reference","unchanged"],"summary":"RFC 7344 specifies how DNS trust can be maintained across key\n rollovers in-band between parent and child. This document elevates\n RFC 7344 from Informational to Standards Track. It also adds a\n method for initial trust setup and removal of a secure entry point.\n\n Changing a domain's DNSSEC status can be a complicated matter\n involving multiple unrelated parties. Some of these parties, such as\n the DNS operator, might not even be known by all the organizations\n involved. The inability to disable DNSSEC via in-band signaling is\n seen as a problem or liability that prevents some DNSSEC adoption at\n a large scale. This document adds a method for in-band signaling of\n these DNSSEC status changes.\n\n This document describes reasonable policies to ease deployment of the\n initial acceptance of new secure entry points (DS records).\n\n It is preferable that operators collaborate on the transfer or ","scope_keywords":["8078","algorithm","algorithms","holder","http","key","license","policies","policy","risk","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null}],"search_text":"IETF RFC 8078 RFC 7344 specifies how DNS trust can be maintained across key\n rollovers in-band between parent and child. This document elevates\n RFC 7344 from Informational to Standards Track. It also adds a\n method for initial trust setup and removal of a secure entry point.\n\n Changing a domain's DNSSEC status can be a complicated matter\n involving multiple unrelated parties. Some of these parties, such as\n the DNS operator, might not even be known by all the organizations\n involved. The inability to disable DNSSEC via in-band signaling is\n seen as a problem or liability that prevents some DNSSEC adoption at\n a large scale. This document adds a method for in-band signaling of\n these DNSSEC status changes.\n\n This document describes reasonable policies to ease deployment of the\n initial acceptance of new secure entry points (DS records).\n\n It is preferable that operators collaborate on the transfer or  8078 algorithm algorithms holder http key license policies policy risk subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8081","type":"specification","body":"IETF","designation":"RFC 8081","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8081.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8081.txt","https://www.rfc-editor.org/rfc/rfc8081.pdf"],"folder":"IETF/RFC-8081","files":{"txt":{"path":"standards/IETF/RFC-8081/RFC-8081.txt","sha256":"4d0dbcf38ab38d87cd26e8f412c7b42ff53a47fc07ee5b69fddd0e42311e1f28"}},"tags":["nested-reference","unchanged"],"summary":"This memo serves to register and document the \"font\" top-level media\n type, under which subtypes for representation formats for fonts may\n be registered. This document also serves as a registration\n application for a set of intended subtypes, which are representative\n of some existing subtypes already in use, and currently registered\n under the \"application\" tree by their separate registrations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on ","scope_keywords":["8081","http","key","license","pid","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null}],"search_text":"IETF RFC 8081 This memo serves to register and document the \"font\" top-level media\n type, under which subtypes for representation formats for fonts may\n be registered. This document also serves as a registration\n application for a set of intended subtypes, which are representative\n of some existing subtypes already in use, and currently registered\n under the \"application\" tree by their separate registrations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on  8081 http key license pid presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8083","type":"specification","body":"IETF","designation":"RFC 8083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8083.txt","https://www.rfc-editor.org/rfc/rfc8083.pdf"],"folder":"IETF/RFC-8083","files":{"txt":{"path":"standards/IETF/RFC-8083/RFC-8083.txt","sha256":"f5dab2fc51fd1843dcbd74778b967e12db6dedb2711c71fdb706dba85f3a79d7"}},"tags":["nested-reference","unchanged"],"summary":"The Real-time Transport Protocol (RTP) is widely used in telephony,\n video conferencing, and telepresence applications. Such applications\n are often run on best-effort UDP/IP networks. If congestion control\n is not implemented in these applications, then network congestion can\n lead to uncontrolled packet loss and a resulting deterioration of the\n user's multimedia experience. The congestion control algorithm acts\n as a safety measure by stopping RTP flows from using excessive\n resources and protecting the network from overload. At the time of\n this writing, however, while there are several proprietary solutions,\n there is no standard algorithm for congestion control of interactive\n RTP flows.\n\n This document does not propose a congestion control algorithm. It\n instead defines a minimal set of RTP circuit breakers: conditions\n under which an RTP sender needs to stop transmitting media da","scope_keywords":["8083","algorithm","algorithms","http","license","path","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8083 The Real-time Transport Protocol (RTP) is widely used in telephony,\n video conferencing, and telepresence applications. Such applications\n are often run on best-effort UDP/IP networks. If congestion control\n is not implemented in these applications, then network congestion can\n lead to uncontrolled packet loss and a resulting deterioration of the\n user's multimedia experience. The congestion control algorithm acts\n as a safety measure by stopping RTP flows from using excessive\n resources and protecting the network from overload. At the time of\n this writing, however, while there are several proprietary solutions,\n there is no standard algorithm for congestion control of interactive\n RTP flows.\n\n This document does not propose a congestion control algorithm. It\n instead defines a minimal set of RTP circuit breakers: conditions\n under which an RTP sender needs to stop transmitting media da 8083 algorithm algorithms http license path profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8091","type":"specification","body":"IETF","designation":"RFC 8091","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8091.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8091.txt","https://www.rfc-editor.org/rfc/rfc8091.pdf"],"folder":"IETF/RFC-8091","files":{"txt":{"path":"standards/IETF/RFC-8091/RFC-8091.txt","sha256":"79c57255cbfbf566ca33a15fb281e94ec99b7e1e839c3b2e3788aed5bba72c58"}},"tags":["nested-reference","unchanged"],"summary":"Structured syntax suffixes for media types allow other media types to\n build on them and make it explicit that they are built on an existing\n media type as their foundation. This specification defines and\n registers \"+json-seq\" as a structured syntax suffix for JSON text\n sequences.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta","scope_keywords":["8091","http","https","identification","key","license","presentation","registered","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null}],"search_text":"IETF RFC 8091 Structured syntax suffixes for media types allow other media types to\n build on them and make it explicit that they are built on an existing\n media type as their foundation. This specification defines and\n registers \"+json-seq\" as a structured syntax suffix for JSON text\n sequences.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta 8091 http https identification key license presentation registered signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8108","type":"specification","body":"IETF","designation":"RFC 8108","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8108.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8108.txt","https://www.rfc-editor.org/rfc/rfc8108.pdf"],"folder":"IETF/RFC-8108","files":{"txt":{"path":"standards/IETF/RFC-8108/RFC-8108.txt","sha256":"0201b3aec2a7a165404c2699132d8a0d6ca79025eacfc7ebf91227b44eeed805"}},"tags":["nested-reference","unchanged"],"summary":"This memo expands and clarifies the behavior of Real-time Transport\n Protocol (RTP) endpoints that use multiple synchronization sources\n (SSRCs). This occurs, for example, when an endpoint sends multiple\n RTP streams in a single RTP session. This memo updates RFC 3550 with\n regard to handling multiple SSRCs per endpoint in RTP sessions, with\n a particular focus on RTP Control Protocol (RTCP) behavior. It also\n updates RFC 4585 to change and clarify the calculation of the timeout\n of SSRCs and the inclusion of feedback messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av","scope_keywords":["8108","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8083","folder":"IETF/RFC-8083","source":"IETF/RFC-8083/RFC-8083.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 8108 This memo expands and clarifies the behavior of Real-time Transport\n Protocol (RTP) endpoints that use multiple synchronization sources\n (SSRCs). This occurs, for example, when an endpoint sends multiple\n RTP streams in a single RTP session. This memo updates RFC 3550 with\n regard to handling multiple SSRCs per endpoint in RTP sessions, with\n a particular focus on RTP Control Protocol (RTCP) behavior. It also\n updates RFC 4585 to change and clarify the calculation of the timeout\n of SSRCs and the inclusion of feedback messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av 8108 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8132","type":"specification","body":"IETF","designation":"RFC 8132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8132.txt","https://www.rfc-editor.org/rfc/rfc8132.pdf"],"folder":"IETF/RFC-8132","files":{"txt":{"path":"standards/IETF/RFC-8132/RFC-8132.txt","sha256":"495ff8973748345748fea84ea96ab949b25f6b437171526d2353ac1d72eda149"}},"tags":["nested-reference","unchanged"],"summary":"The methods defined in RFC 7252 for the Constrained Application\n Protocol (CoAP) only allow access to a complete resource, not to\n parts of a resource. In case of resources with larger or complex\n data, or in situations where resource continuity is required,\n replacing or requesting the whole resource is undesirable. Several\n applications using CoAP need to access parts of the resources.\n\n This specification defines the new CoAP methods, FETCH, PATCH, and\n iPATCH, which are used to access and update parts of a resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available ","scope_keywords":["8132","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 8132 The methods defined in RFC 7252 for the Constrained Application\n Protocol (CoAP) only allow access to a complete resource, not to\n parts of a resource. In case of resources with larger or complex\n data, or in situations where resource continuity is required,\n replacing or requesting the whole resource is undesirable. Several\n applications using CoAP need to access parts of the resources.\n\n This specification defines the new CoAP methods, FETCH, PATCH, and\n iPATCH, which are used to access and update parts of a resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available  8132 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8143","type":"specification","body":"IETF","designation":"RFC 8143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8143.txt","https://www.rfc-editor.org/rfc/rfc8143.pdf"],"folder":"IETF/RFC-8143","files":{"txt":{"path":"standards/IETF/RFC-8143/RFC-8143.txt","sha256":"f219e3760fe8de93b448e9fb239ea102115ff18445c00efdb783c523961dbf27"}},"tags":["nested-reference","unchanged"],"summary":"This document provides recommendations for improving the security of\n the Network News Transfer Protocol (NNTP) when using Transport Layer\n Security (TLS). It modernizes the NNTP usage of TLS to be consistent\n with TLS best current practices. This document updates RFC 4642.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8143.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the per","scope_keywords":["8143","certificate","http","key","license","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 8143 This document provides recommendations for improving the security of\n the Network News Transfer Protocol (NNTP) when using Transport Layer\n Security (TLS). It modernizes the NNTP usage of TLS to be consistent\n with TLS best current practices. This document updates RFC 4642.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8143.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the per 8143 certificate http key license subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8162","type":"specification","body":"IETF","designation":"RFC 8162","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8162.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8162.txt","https://www.rfc-editor.org/rfc/rfc8162.pdf"],"folder":"IETF/RFC-8162","files":{"txt":{"path":"standards/IETF/RFC-8162/RFC-8162.txt","sha256":"c2d71dbdbbbf2538709a1522e17b374568eb0d0e59ddd242cb98f8bc2b8f07bb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to use secure DNS to associate an S/MIME\n user's certificate with the intended domain name, similar to the way\n that DNS-Based Authentication of Named Entities (DANE), RFC 6698,\n does for TLS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata","scope_keywords":["8162","authentication","certificate","certificates","encryption","http","key","keys","license","management","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null}],"search_text":"IETF RFC 8162 This document describes how to use secure DNS to associate an S/MIME\n user's certificate with the intended domain name, similar to the way\n that DNS-Based Authentication of Named Entities (DANE), RFC 6698,\n does for TLS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata 8162 authentication certificate certificates encryption http key keys license management pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8164","type":"specification","body":"IETF","designation":"RFC 8164","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8164.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8164.txt","https://www.rfc-editor.org/rfc/rfc8164.pdf"],"folder":"IETF/RFC-8164","files":{"txt":{"path":"standards/IETF/RFC-8164/RFC-8164.txt","sha256":"19f1595536be650af3690188009554b06e88acd15dfbbc25281dc391f5fe0291"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how \"http\" URIs can be accessed using\n Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive\n monitoring attacks. This mechanism not a replacement for \"https\"\n URIs; it is vulnerable to active attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this docum","scope_keywords":["8164","certificate","certificates","encryption","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null}],"search_text":"IETF RFC 8164 This document describes how \"http\" URIs can be accessed using\n Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive\n monitoring attacks. This mechanism not a replacement for \"https\"\n URIs; it is vulnerable to active attacks.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this docum 8164 certificate certificates encryption http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8168","type":"specification","body":"IETF","designation":"RFC 8168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8168.txt","https://www.rfc-editor.org/rfc/rfc8168.pdf"],"folder":"IETF/RFC-8168","files":{"txt":{"path":"standards/IETF/RFC-8168/RFC-8168.txt","sha256":"2f2d426a484318407fc3f76fc0bec88096ebc551165c058e7de394fe47278613"}},"tags":["nested-reference","unchanged"],"summary":"DHCPv6 Prefix Delegation allows a client to include a prefix-length\n hint value in the IA_PD option to indicate a preference for the size\n of the prefix to be delegated, but it is unclear about how the client\n and server should act in different situations involving the prefix-\n length hint. This document provides a summary of the existing\n problems with the prefix-length hint and guidance on what the client\n and server could do in different situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of t","scope_keywords":["8168","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 8168 DHCPv6 Prefix Delegation allows a client to include a prefix-length\n hint value in the IA_PD option to indicate a preference for the size\n of the prefix to be delegated, but it is unclear about how the client\n and server should act in different situations involving the prefix-\n length hint. This document provides a summary of the existing\n problems with the prefix-length hint and guidance on what the client\n and server could do in different situations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of t 8168 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8174","type":"specification","body":"IETF","designation":"RFC 8174","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8174.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8174.txt","https://www.rfc-editor.org/rfc/rfc8174.pdf"],"folder":"IETF/RFC-8174","files":{"txt":{"path":"standards/IETF/RFC-8174/RFC-8174.txt","sha256":"5ca0e2f90be0bc5928ee465f76518fee316dfa775aed885658a29a419cc293b7"}},"tags":["nested-reference","unchanged"],"summary":"RFC 2119 specifies common key words that may be used in protocol\n specifications. This document aims to reduce the ambiguity by\n clarifying that only UPPERCASE usage of the key words have the\n defined special meanings.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8174.\n\nLeiba Best Current Practice [Page 1]\n\f\nRFC 8174 RFC 2119 Clarification May 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IE","scope_keywords":["8174","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS03","folder":"ARF/TS03-V1.5.2","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md","version":"1.5.2"},{"body":"ARF","designation":"TS09","folder":"ARF/TS09-V1.1","source":"ARF/TS09-V1.1/TS09-V1.1.md","version":"1.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null},{"body":"IETF","designation":"RFC 8168","folder":"IETF/RFC-8168","source":"IETF/RFC-8168/RFC-8168.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8198","folder":"IETF/RFC-8198","source":"IETF/RFC-8198/RFC-8198.txt","version":null},{"body":"IETF","designation":"RFC 8213","folder":"IETF/RFC-8213","source":"IETF/RFC-8213/RFC-8213.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8230","folder":"IETF/RFC-8230","source":"IETF/RFC-8230/RFC-8230.txt","version":null},{"body":"IETF","designation":"RFC 8235","folder":"IETF/RFC-8235","source":"IETF/RFC-8235/RFC-8235.txt","version":null},{"body":"IETF","designation":"RFC 8246","folder":"IETF/RFC-8246","source":"IETF/RFC-8246/RFC-8246.txt","version":null},{"body":"IETF","designation":"RFC 8250","folder":"IETF/RFC-8250","source":"IETF/RFC-8250/RFC-8250.txt","version":null},{"body":"IETF","designation":"RFC 8252","folder":"IETF/RFC-8252","source":"IETF/RFC-8252/RFC-8252.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8260","folder":"IETF/RFC-8260","source":"IETF/RFC-8260/RFC-8260.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8279","folder":"IETF/RFC-8279","source":"IETF/RFC-8279/RFC-8279.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null},{"body":"IETF","designation":"RFC 8290","folder":"IETF/RFC-8290","source":"IETF/RFC-8290/RFC-8290.txt","version":null},{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null},{"body":"IETF","designation":"RFC 8297","folder":"IETF/RFC-8297","source":"IETF/RFC-8297/RFC-8297.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8305","folder":"IETF/RFC-8305","source":"IETF/RFC-8305/RFC-8305.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8336","folder":"IETF/RFC-8336","source":"IETF/RFC-8336/RFC-8336.txt","version":null},{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8391","folder":"IETF/RFC-8391","source":"IETF/RFC-8391/RFC-8391.txt","version":null},{"body":"IETF","designation":"RFC 8392","folder":"IETF/RFC-8392","source":"IETF/RFC-8392/RFC-8392.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8414","folder":"IETF/RFC-8414","source":"IETF/RFC-8414/RFC-8414.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8427","folder":"IETF/RFC-8427","source":"IETF/RFC-8427/RFC-8427.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8439","folder":"IETF/RFC-8439","source":"IETF/RFC-8439/RFC-8439.txt","version":null},{"body":"IETF","designation":"RFC 8441","folder":"IETF/RFC-8441","source":"IETF/RFC-8441/RFC-8441.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8447","folder":"IETF/RFC-8447","source":"IETF/RFC-8447/RFC-8447.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8452","folder":"IETF/RFC-8452","source":"IETF/RFC-8452/RFC-8452.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 8467","folder":"IETF/RFC-8467","source":"IETF/RFC-8467/RFC-8467.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8521","folder":"IETF/RFC-8521","source":"IETF/RFC-8521/RFC-8521.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null},{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8573","folder":"IETF/RFC-8573","source":"IETF/RFC-8573/RFC-8573.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8707","folder":"IETF/RFC-8707","source":"IETF/RFC-8707/RFC-8707.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null},{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 8742","folder":"IETF/RFC-8742","source":"IETF/RFC-8742/RFC-8742.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 8767","folder":"IETF/RFC-8767","source":"IETF/RFC-8767/RFC-8767.txt","version":null},{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8785","folder":"IETF/RFC-8785","source":"IETF/RFC-8785/RFC-8785.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8820","folder":"IETF/RFC-8820","source":"IETF/RFC-8820/RFC-8820.txt","version":null},{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8863","folder":"IETF/RFC-8863","source":"IETF/RFC-8863/RFC-8863.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8914","folder":"IETF/RFC-8914","source":"IETF/RFC-8914/RFC-8914.txt","version":null},{"body":"IETF","designation":"RFC 8915","folder":"IETF/RFC-8915","source":"IETF/RFC-8915/RFC-8915.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8937","folder":"IETF/RFC-8937","source":"IETF/RFC-8937/RFC-8937.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8945","folder":"IETF/RFC-8945","source":"IETF/RFC-8945/RFC-8945.txt","version":null},{"body":"IETF","designation":"RFC 8947","folder":"IETF/RFC-8947","source":"IETF/RFC-8947/RFC-8947.txt","version":null},{"body":"IETF","designation":"RFC 8948","folder":"IETF/RFC-8948","source":"IETF/RFC-8948/RFC-8948.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 8973","folder":"IETF/RFC-8973","source":"IETF/RFC-8973/RFC-8973.txt","version":null},{"body":"IETF","designation":"RFC 8974","folder":"IETF/RFC-8974","source":"IETF/RFC-8974/RFC-8974.txt","version":null},{"body":"IETF","designation":"RFC 8976","folder":"IETF/RFC-8976","source":"IETF/RFC-8976/RFC-8976.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 8999","folder":"IETF/RFC-8999","source":"IETF/RFC-8999/RFC-8999.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null},{"body":"IETF","designation":"RFC 9021","folder":"IETF/RFC-9021","source":"IETF/RFC-9021/RFC-9021.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9106","folder":"IETF/RFC-9106","source":"IETF/RFC-9106/RFC-9106.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9204","folder":"IETF/RFC-9204","source":"IETF/RFC-9204/RFC-9204.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9471","folder":"IETF/RFC-9471","source":"IETF/RFC-9471/RFC-9471.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9876","folder":"IETF/RFC-9876","source":"IETF/RFC-9876/RFC-9876.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 8174 RFC 2119 specifies common key words that may be used in protocol\n specifications. This document aims to reduce the ambiguity by\n clarifying that only UPPERCASE usage of the key words have the\n defined special meanings.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8174.\n\nLeiba Best Current Practice [Page 1]\n\f\nRFC 8174 RFC 2119 Clarification May 2017\n\nCopyright Notice\n\n Copyright (c) 2017 IE 8174 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8188","type":"specification","body":"IETF","designation":"RFC 8188","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8188.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8188.txt","https://www.rfc-editor.org/rfc/rfc8188.pdf"],"folder":"IETF/RFC-8188","files":{"txt":{"path":"standards/IETF/RFC-8188/RFC-8188.txt","sha256":"0423a8c435562a9f4f32504d3b3cc4b59230b8671f905bf7bd396de2f95b7b50"}},"tags":["nested-reference","unchanged"],"summary":"This memo introduces a content coding for HTTP that allows message\n payloads to be encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8188.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://truste","scope_keywords":["8188","algorithm","encryption","http","key","keys","license","management","profile","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8291","folder":"IETF/RFC-8291","source":"IETF/RFC-8291/RFC-8291.txt","version":null}],"search_text":"IETF RFC 8188 This memo introduces a content coding for HTTP that allows message\n payloads to be encrypted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8188.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://truste 8188 algorithm encryption http key keys license management profile subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8198","type":"specification","body":"IETF","designation":"RFC 8198","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8198.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8198.txt","https://www.rfc-editor.org/rfc/rfc8198.pdf"],"folder":"IETF/RFC-8198","files":{"txt":{"path":"standards/IETF/RFC-8198/RFC-8198.txt","sha256":"78b49d40dc78dffb30fd1aad7313c21800ff9642ab60c27b1a507d2662bec80a"}},"tags":["nested-reference","unchanged"],"summary":"The DNS relies upon caching to scale; however, the cache lookup\n generally requires an exact match. This document specifies the use\n of NSEC/NSEC3 resource records to allow DNSSEC-validating resolvers\n to generate negative answers within a range and positive answers from\n wildcards. This increases performance, decreases latency, decreases\n resource utilization on both authoritative and recursive servers, and\n increases privacy. Also, it may help increase resilience to certain\n DoS attacks in some circumstances.\n\n This document updates RFC 4035 by allowing validating resolvers to\n generate negative answers based upon NSEC/NSEC3 records and positive\n answers in the presence of wildcards.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n ","scope_keywords":["8198","hash","http","key","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8806","folder":"IETF/RFC-8806","source":"IETF/RFC-8806/RFC-8806.txt","version":null},{"body":"IETF","designation":"RFC 8901","folder":"IETF/RFC-8901","source":"IETF/RFC-8901/RFC-8901.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null}],"search_text":"IETF RFC 8198 The DNS relies upon caching to scale; however, the cache lookup\n generally requires an exact match. This document specifies the use\n of NSEC/NSEC3 resource records to allow DNSSEC-validating resolvers\n to generate negative answers within a range and positive answers from\n wildcards. This increases performance, decreases latency, decreases\n resource utilization on both authoritative and recursive servers, and\n increases privacy. Also, it may help increase resilience to certain\n DoS attacks in some circumstances.\n\n This document updates RFC 4035 by allowing validating resolvers to\n generate negative answers based upon NSEC/NSEC3 records and positive\n answers in the presence of wildcards.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n  8198 hash http key license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8224","type":"specification","body":"IETF","designation":"RFC 8224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8224.txt","https://www.rfc-editor.org/rfc/rfc8224.pdf"],"folder":"IETF/RFC-8224","files":{"txt":{"path":"standards/IETF/RFC-8224/RFC-8224.txt","sha256":"c6f0972ec7400b02dac78aa24724206600be57316c8ea1af20e40ca66305fc85"}},"tags":["nested-reference","unchanged"],"summary":"The baseline security mechanisms in the Session Initiation Protocol\n (SIP) are inadequate for cryptographically assuring the identity of\n the end users that originate SIP requests, especially in an\n interdomain context. This document defines a mechanism for securely\n identifying originators of SIP requests. It does so by defining a\n SIP header field for conveying a signature used for validating the\n identity and for conveying a reference to the credentials of the\n signer.\n\n This document obsoletes RFC 4474.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 ","scope_keywords":["8224","algorithm","authentication","authorization","credential","credentials","http","https","license","management","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null}],"search_text":"IETF RFC 8224 The baseline security mechanisms in the Session Initiation Protocol\n (SIP) are inadequate for cryptographically assuring the identity of\n the end users that originate SIP requests, especially in an\n interdomain context. This document defines a mechanism for securely\n identifying originators of SIP requests. It does so by defining a\n SIP header field for conveying a signature used for validating the\n identity and for conveying a reference to the credentials of the\n signer.\n\n This document obsoletes RFC 4474.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2  8224 algorithm authentication authorization credential credentials http https license management signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8230","type":"specification","body":"IETF","designation":"RFC 8230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8230.txt","https://www.rfc-editor.org/rfc/rfc8230.pdf"],"folder":"IETF/RFC-8230","files":{"txt":{"path":"standards/IETF/RFC-8230/RFC-8230.txt","sha256":"d59c3f07682118a937092cd2b07c3d2f3aa97dca034ed90fb11f621fbf58ae05"}},"tags":["nested-reference","unchanged"],"summary":"The CBOR Object Signing and Encryption (COSE) specification defines\n cryptographic message encodings using Concise Binary Object\n Representation (CBOR). This specification defines algorithm\n encodings and representations enabling RSA algorithms to be used for\n COSE messages. Encodings are specified for the use of RSA\n Probabilistic Signature Scheme (RSASSA-PSS) signatures, RSA\n Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-\n OAEP) encryption, and RSA keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about ","scope_keywords":["8230","algorithm","algorithms","encryption","hash","hashing","http","key","keys","license","presentation","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 8230 The CBOR Object Signing and Encryption (COSE) specification defines\n cryptographic message encodings using Concise Binary Object\n Representation (CBOR). This specification defines algorithm\n encodings and representations enabling RSA algorithms to be used for\n COSE messages. Encodings are specified for the use of RSA\n Probabilistic Signature Scheme (RSASSA-PSS) signatures, RSA\n Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-\n OAEP) encryption, and RSA keys.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about  8230 algorithm algorithms encryption hash hashing http key keys license presentation signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8235","type":"specification","body":"IETF","designation":"RFC 8235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8235.txt","https://www.rfc-editor.org/rfc/rfc8235.pdf"],"folder":"IETF/RFC-8235","files":{"txt":{"path":"standards/IETF/RFC-8235/RFC-8235.txt","sha256":"c1f4937bfb9e830d4a56b08bb02857e23109aa33e4534a83968ff7edaf3a36db"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Schnorr non-interactive zero-knowledge\n (NIZK) proof, a non-interactive variant of the three-pass Schnorr\n identification scheme. The Schnorr NIZK proof allows one to prove\n the knowledge of a discrete logarithm without leaking any information\n about its value. It can serve as a useful building block for many\n cryptographic protocols to ensure that participants follow the\n protocol specification honestly. This document specifies the Schnorr\n NIZK proof in both the finite field and the elliptic curve settings.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deploymen","scope_keywords":["8235","hash","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"IETF RFC 8235 This document describes the Schnorr non-interactive zero-knowledge\n (NIZK) proof, a non-interactive variant of the three-pass Schnorr\n identification scheme. The Schnorr NIZK proof allows one to prove\n the knowledge of a discrete logarithm without leaking any information\n about its value. It can serve as a useful building block for many\n cryptographic protocols to ensure that participants follow the\n protocol specification honestly. This document specifies the Schnorr\n NIZK proof in both the finite field and the elliptic curve settings.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deploymen 8235 hash http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8246","type":"specification","body":"IETF","designation":"RFC 8246","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8246.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8246.txt","https://www.rfc-editor.org/rfc/rfc8246.pdf"],"folder":"IETF/RFC-8246","files":{"txt":{"path":"standards/IETF/RFC-8246/RFC-8246.txt","sha256":"69cfa5be26b918d5754652f5b93d707abdd68c0512f2ee66b92821cb64439b57"}},"tags":["nested-reference","unchanged"],"summary":"The immutable HTTP response Cache-Control extension allows servers to\n identify resources that will not be updated during their freshness\n lifetime. This ensures that a client never needs to revalidate a\n cached fresh resource to be certain it has not been modified.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8246.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons id","scope_keywords":["8246","http","https","key","license","path","presentation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 8246 The immutable HTTP response Cache-Control extension allows servers to\n identify resources that will not be updated during their freshness\n lifetime. This ensures that a client never needs to revalidate a\n cached fresh resource to be certain it has not been modified.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8246.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons id 8246 http https key license path presentation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8252","type":"specification","body":"IETF","designation":"RFC 8252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8252.txt","https://www.rfc-editor.org/rfc/rfc8252.pdf"],"folder":"IETF/RFC-8252","files":{"txt":{"path":"standards/IETF/RFC-8252/RFC-8252.txt","sha256":"4233c0650ec7e7918c20e0fde2dc565f85e2aa2d4c18123e3cd834295c2f68d0"}},"tags":["nested-reference","unchanged"],"summary":"OAuth 2.0 authorization requests from native apps should only be made\n through external user-agents, primarily the user's browser. This\n specification details the security and usability reasons why this is\n the case and how native apps and authorization servers can implement\n this best practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8252.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF","scope_keywords":["8252","authentication","authorization","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 8252 OAuth 2.0 authorization requests from native apps should only be made\n through external user-agents, primarily the user's browser. This\n specification details the security and usability reasons why this is\n the case and how native apps and authorization servers can implement\n this best practice.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8252.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF 8252 authentication authorization http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8279","type":"specification","body":"IETF","designation":"RFC 8279","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8279.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8279.txt","https://www.rfc-editor.org/rfc/rfc8279.pdf"],"folder":"IETF/RFC-8279","files":{"txt":{"path":"standards/IETF/RFC-8279/RFC-8279.txt","sha256":"8b33c2b4e3604dd3ecfa46a1629029a3ad6e7bbf000a94acc904e1ab77a48f2f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new architecture for the forwarding of\n multicast data packets. It provides optimal forwarding of multicast\n packets through a \"multicast domain\". However, it does not require a\n protocol for explicitly building multicast distribution trees, nor\n does it require intermediate nodes to maintain any per-flow state.\n This architecture is known as \"Bit Index Explicit Replication\"\n (BIER). When a multicast data packet enters the domain, the ingress\n router determines the set of egress routers to which the packet needs\n to be sent. The ingress router then encapsulates the packet in a\n BIER header. The BIER header contains a bit string in which each bit\n represents exactly one egress router in the domain; to forward the\n packet to a given set of egress routers, the bits corresponding to\n those routers are set in the BIER header. The procedures for\n forwarding a packet b","scope_keywords":["8279","http","https","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8293","folder":"IETF/RFC-8293","source":"IETF/RFC-8293/RFC-8293.txt","version":null}],"search_text":"IETF RFC 8279 This document specifies a new architecture for the forwarding of\n multicast data packets. It provides optimal forwarding of multicast\n packets through a \"multicast domain\". However, it does not require a\n protocol for explicitly building multicast distribution trees, nor\n does it require intermediate nodes to maintain any per-flow state.\n This architecture is known as \"Bit Index Explicit Replication\"\n (BIER). When a multicast data packet enters the domain, the ingress\n router determines the set of egress routers to which the packet needs\n to be sent. The ingress router then encapsulates the packet in a\n BIER header. The BIER header contains a bit string in which each bit\n represents exactly one egress router in the domain; to forward the\n packet to a given set of egress routers, the bits corresponding to\n those routers are set in the BIER header. The procedures for\n forwarding a packet b 8279 http https license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8285","type":"specification","body":"IETF","designation":"RFC 8285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8285.txt","https://www.rfc-editor.org/rfc/rfc8285.pdf"],"folder":"IETF/RFC-8285","files":{"txt":{"path":"standards/IETF/RFC-8285/RFC-8285.txt","sha256":"e6fc1f0e6638560b6052f08d548b02b0418bb4f7b1f362a5ec340293e673d60a"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a general mechanism to use the header\n extension feature of RTP (the Real-time Transport Protocol). It\n provides the option to use a small number of small extensions in each\n RTP packet, where the universe of possible extensions is large and\n registration is decentralized. The actual extensions in use in a\n session are signaled in the setup information for that session. This\n document obsoletes RFC 5285.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n","scope_keywords":["8285","attribute","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 8285 This document provides a general mechanism to use the header\n extension feature of RTP (the Real-time Transport Protocol). It\n provides the option to use a small number of small extensions in each\n RTP packet, where the universe of possible extensions is large and\n registration is decentralized. The actual extensions in use in a\n session are signaled in the setup information for that session. This\n document obsoletes RFC 5285.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n 8285 attribute http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8291","type":"specification","body":"IETF","designation":"RFC 8291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8291.txt","https://www.rfc-editor.org/rfc/rfc8291.pdf"],"folder":"IETF/RFC-8291","files":{"txt":{"path":"standards/IETF/RFC-8291/RFC-8291.txt","sha256":"d7130962cbe0940465ca375a9fcecfaaa33afb0febd71dd58e2712502fdc0504"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a message encryption scheme for the Web Push\n protocol. This scheme provides confidentiality and integrity for\n messages sent from an application server to a user agent.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8291.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i","scope_keywords":["8291","authentication","encryption","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 8291 This document describes a message encryption scheme for the Web Push\n protocol. This scheme provides confidentiality and integrity for\n messages sent from an application server to a user agent.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8291.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document i 8291 authentication encryption http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8297","type":"specification","body":"IETF","designation":"RFC 8297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8297.txt","https://www.rfc-editor.org/rfc/rfc8297.pdf"],"folder":"IETF/RFC-8297","files":{"txt":{"path":"standards/IETF/RFC-8297/RFC-8297.txt","sha256":"ce97f9531cc74227a36785bb0136bcb032e5e7544551519c5dcee80db68d42e5"}},"tags":["nested-reference","unchanged"],"summary":"This memo introduces an informational HTTP status code that can be\n used to convey hints that help a client make preparations for\n processing the final response.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht","scope_keywords":["8297","delivery","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9292","folder":"IETF/RFC-9292","source":"IETF/RFC-9292/RFC-9292.txt","version":null}],"search_text":"IETF RFC 8297 This memo introduces an informational HTTP status code that can be\n used to convey hints that help a client make preparations for\n processing the final response.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are a candidate for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n ht 8297 delivery http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8300","type":"specification","body":"IETF","designation":"RFC 8300","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8300.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8300.txt","https://www.rfc-editor.org/rfc/rfc8300.pdf"],"folder":"IETF/RFC-8300","files":{"txt":{"path":"standards/IETF/RFC-8300/RFC-8300.txt","sha256":"0636afea7e20d503e6b62b65921a132ea76b453019d678add4672bc0482dcee1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Network Service Header (NSH) imposed on\n packets or frames to realize Service Function Paths (SFPs). The NSH\n also provides a mechanism for metadata exchange along the\n instantiated service paths. The NSH is the Service Function Chaining\n (SFC) encapsulation required to support the SFC architecture (defined\n in RFC 7665).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org","scope_keywords":["8300","delivery","http","https","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 8300 This document describes a Network Service Header (NSH) imposed on\n packets or frames to realize Service Function Paths (SFPs). The NSH\n also provides a mechanism for metadata exchange along the\n instantiated service paths. The NSH is the Service Function Chaining\n (SFC) encapsulation required to support the SFC architecture (defined\n in RFC 7665).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org 8300 delivery http https license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8305","type":"specification","body":"IETF","designation":"RFC 8305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8305.txt","https://www.rfc-editor.org/rfc/rfc8305.pdf"],"folder":"IETF/RFC-8305","files":{"txt":{"path":"standards/IETF/RFC-8305/RFC-8305.txt","sha256":"9bb65e288b32acae072d1bf403c609f71c32ea7a5087d0056ee9af3cedca47e1"}},"tags":["nested-reference","unchanged"],"summary":"Many communication protocols operating over the modern Internet use\n hostnames. These often resolve to multiple IP addresses, each of\n which may have different performance and connectivity\n characteristics. Since specific addresses or address families (IPv4\n or IPv6) may be blocked, broken, or sub-optimal on a network, clients\n that attempt multiple connections in parallel have a chance of\n establishing a connection more quickly. This document specifies\n requirements for algorithms that reduce this user-visible delay and\n provides an example algorithm, referred to as \"Happy Eyeballs\". This\n document obsoletes the original algorithm description in RFC 6555.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has","scope_keywords":["8305","algorithm","algorithms","http","https","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8421","folder":"IETF/RFC-8421","source":"IETF/RFC-8421/RFC-8421.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null}],"search_text":"IETF RFC 8305 Many communication protocols operating over the modern Internet use\n hostnames. These often resolve to multiple IP addresses, each of\n which may have different performance and connectivity\n characteristics. Since specific addresses or address families (IPv4\n or IPv6) may be blocked, broken, or sub-optimal on a network, clients\n that attempt multiple connections in parallel have a chance of\n establishing a connection more quickly. This document specifies\n requirements for algorithms that reduce this user-visible delay and\n provides an example algorithm, referred to as \"Happy Eyeballs\". This\n document obsoletes the original algorithm description in RFC 6555.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has 8305 algorithm algorithms http https key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8310","type":"specification","body":"IETF","designation":"RFC 8310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8310.txt","https://www.rfc-editor.org/rfc/rfc8310.pdf"],"folder":"IETF/RFC-8310","files":{"txt":{"path":"standards/IETF/RFC-8310/RFC-8310.txt","sha256":"33d9deb3783b1fa1fefb3b44bbe99ebcbf16495436524674b6d4023148bfdcb2"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses usage profiles, based on one or more\n authentication mechanisms, which can be used for DNS over Transport\n Layer Security (TLS) or Datagram TLS (DTLS). These profiles can\n increase the privacy of DNS transactions compared to using only\n cleartext DNS. This document also specifies new authentication\n mechanisms -- it describes several ways that a DNS client can use an\n authentication domain name to authenticate a (D)TLS connection to a\n DNS server. Additionally, it defines (D)TLS protocol profiles for\n DNS clients and servers implementing DNS over (D)TLS. This document\n updates RFC 7858.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet","scope_keywords":["8310","authentication","certificate","credential","http","https","license","pki","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 8310 This document discusses usage profiles, based on one or more\n authentication mechanisms, which can be used for DNS over Transport\n Layer Security (TLS) or Datagram TLS (DTLS). These profiles can\n increase the privacy of DNS transactions compared to using only\n cleartext DNS. This document also specifies new authentication\n mechanisms -- it describes several ways that a DNS client can use an\n authentication domain name to authenticate a (D)TLS connection to a\n DNS server. Additionally, it defines (D)TLS protocol profiles for\n DNS clients and servers implementing DNS over (D)TLS. This document\n updates RFC 7858.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet 8310 authentication certificate credential http https license pki profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8311","type":"specification","body":"IETF","designation":"RFC 8311","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8311.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8311.txt","https://www.rfc-editor.org/rfc/rfc8311.pdf"],"folder":"IETF/RFC-8311","files":{"txt":{"path":"standards/IETF/RFC-8311/RFC-8311.txt","sha256":"ea94f04b233617923e086c2ed81b755761a2c4f4ce857b078aab3959cb3c917e"}},"tags":["nested-reference","unchanged"],"summary":"This memo updates RFC 3168, which specifies Explicit Congestion\n Notification (ECN) as an alternative to packet drops for indicating\n network congestion to endpoints. It relaxes restrictions in RFC 3168\n that hinder experimentation towards benefits beyond just removal of\n loss. This memo summarizes the anticipated areas of experimentation\n and updates RFC 3168 to enable experimentation in these areas. An\n Experimental RFC in the IETF document stream is required to take\n advantage of any of these enabling updates. In addition, this memo\n makes related updates to the ECN specifications for RTP in RFC 6679\n and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341,\n 4342, and 5622. This memo also records the conclusion of the ECN\n nonce experiment in RFC 3540 and provides the rationale for\n reclassification of RFC 3540 from Experimental to Historic; this\n reclassification enables","scope_keywords":["8311","http","https","license","management","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 8311 This memo updates RFC 3168, which specifies Explicit Congestion\n Notification (ECN) as an alternative to packet drops for indicating\n network congestion to endpoints. It relaxes restrictions in RFC 3168\n that hinder experimentation towards benefits beyond just removal of\n loss. This memo summarizes the anticipated areas of experimentation\n and updates RFC 3168 to enable experimentation in these areas. An\n Experimental RFC in the IETF document stream is required to take\n advantage of any of these enabling updates. In addition, this memo\n makes related updates to the ECN specifications for RTP in RFC 6679\n and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341,\n 4342, and 5622. This memo also records the conclusion of the ECN\n nonce experiment in RFC 3540 and provides the rationale for\n reclassification of RFC 3540 from Experimental to Historic; this\n reclassification enables 8311 http https license management profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8312","type":"specification","body":"IETF","designation":"RFC 8312","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8312.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8312.txt","https://www.rfc-editor.org/rfc/rfc8312.pdf"],"folder":"IETF/RFC-8312","files":{"txt":{"path":"standards/IETF/RFC-8312/RFC-8312.txt","sha256":"189f32e43b5da0ddcc08ec3426a3ee63dea10431fdeb14c160f02d00e9a1bf64"}},"tags":["nested-reference","unchanged"],"summary":"CUBIC is an extension to the current TCP standards. It differs from\n the current TCP standards only in the congestion control algorithm on\n the sender side. In particular, it uses a cubic function instead of\n a linear window increase function of the current TCP standards to\n improve scalability and stability under fast and long-distance\n networks. CUBIC and its predecessor algorithm have been adopted as\n defaults by Linux and have been used for many years. This document\n provides a specification of CUBIC to enable third-party\n implementations and to solicit community feedback through\n experimentation on the performance of CUBIC.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It ","scope_keywords":["8312","algorithm","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8511","folder":"IETF/RFC-8511","source":"IETF/RFC-8511/RFC-8511.txt","version":null},{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 8312 CUBIC is an extension to the current TCP standards. It differs from\n the current TCP standards only in the congestion control algorithm on\n the sender side. In particular, it uses a cubic function instead of\n a linear window increase function of the current TCP standards to\n improve scalability and stability under fast and long-distance\n networks. CUBIC and its predecessor algorithm have been adopted as\n defaults by Linux and have been used for many years. This document\n provides a specification of CUBIC to enable third-party\n implementations and to solicit community feedback through\n experimentation on the performance of CUBIC.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It  8312 algorithm http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8336","type":"specification","body":"IETF","designation":"RFC 8336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8336.txt","https://www.rfc-editor.org/rfc/rfc8336.pdf"],"folder":"IETF/RFC-8336","files":{"txt":{"path":"standards/IETF/RFC-8336/RFC-8336.txt","sha256":"4fea82567ad3296937042cff7a13a061ff0af4b3610fe164ddbd543db1a831b9"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the ORIGIN frame for HTTP/2, to indicate what\n origins are available on a given connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8336.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Do","scope_keywords":["8336","algorithm","certificate","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8744","folder":"IETF/RFC-8744","source":"IETF/RFC-8744/RFC-8744.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 8336 This document specifies the ORIGIN frame for HTTP/2, to indicate what\n origins are available on a given connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8336.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Do 8336 algorithm certificate http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8341","type":"specification","body":"IETF","designation":"RFC 8341","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8341.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8341.txt","https://www.rfc-editor.org/rfc/rfc8341.pdf"],"folder":"IETF/RFC-8341","files":{"txt":{"path":"standards/IETF/RFC-8341/RFC-8341.txt","sha256":"9f4beb2222ea87c00b45345faa213c184f31279083192ead500a333f1669a34f"}},"tags":["nested-reference","unchanged"],"summary":"The standardization of network configuration interfaces for use with\n the Network Configuration Protocol (NETCONF) or the RESTCONF protocol\n requires a structured and secure operating environment that promotes\n human usability and multi-vendor interoperability. There is a need\n for standard mechanisms to restrict NETCONF or RESTCONF protocol\n access for particular users to a preconfigured subset of all\n available NETCONF or RESTCONF protocol operations and content. This\n document defines such an access control model.\n\n This document obsoletes RFC 6536.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n","scope_keywords":["8341","authorization","http","https","license","management","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null}],"search_text":"IETF RFC 8341 The standardization of network configuration interfaces for use with\n the Network Configuration Protocol (NETCONF) or the RESTCONF protocol\n requires a structured and secure operating environment that promotes\n human usability and multi-vendor interoperability. There is a need\n for standard mechanisms to restrict NETCONF or RESTCONF protocol\n access for particular users to a preconfigured subset of all\n available NETCONF or RESTCONF protocol operations and content. This\n document defines such an access control model.\n\n This document obsoletes RFC 6536.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n 8341 authorization http https license management subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8342","type":"specification","body":"IETF","designation":"RFC 8342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8342.txt","https://www.rfc-editor.org/rfc/rfc8342.pdf"],"folder":"IETF/RFC-8342","files":{"txt":{"path":"standards/IETF/RFC-8342/RFC-8342.txt","sha256":"eef450e0d1d72a1a927fee4674af09586ab5957db83b512cb6e0b4d454dc012d"}},"tags":["nested-reference","unchanged"],"summary":"Datastores are a fundamental concept binding the data models written\n in the YANG data modeling language to network management protocols\n such as the Network Configuration Protocol (NETCONF) and RESTCONF.\n This document defines an architectural framework for datastores based\n on the experience gained with the initial simpler model, addressing\n requirements that were not well supported in the initial model. This\n document updates RFC 7950.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, ","scope_keywords":["8342","http","https","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8341","folder":"IETF/RFC-8341","source":"IETF/RFC-8341/RFC-8341.txt","version":null},{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null}],"search_text":"IETF RFC 8342 Datastores are a fundamental concept binding the data models written\n in the YANG data modeling language to network management protocols\n such as the Network Configuration Protocol (NETCONF) and RESTCONF.\n This document defines an architectural framework for datastores based\n on the experience gained with the initial simpler model, addressing\n requirements that were not well supported in the initial model. This\n document updates RFC 7950.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document,  8342 http https key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8343","type":"specification","body":"IETF","designation":"RFC 8343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8343.txt","https://www.rfc-editor.org/rfc/rfc8343.pdf"],"folder":"IETF/RFC-8343","files":{"txt":{"path":"standards/IETF/RFC-8343/RFC-8343.txt","sha256":"e0ee5ab5f48e933c7042a0e34c297a84ddf4bac0c36ed15c1ef704b74a767237"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG data model for the management of network\n interfaces. It is expected that interface-type-specific data models\n augment the generic interfaces data model defined in this document.\n The data model includes definitions for configuration and system\n state (status information and counters for the collection of\n statistics).\n\n The YANG data model in this document conforms to the Network\n Management Datastore Architecture (NMDA) defined in RFC 8342.\n\n This document obsoletes RFC 7223.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 o","scope_keywords":["8343","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8340","folder":"IETF/RFC-8340","source":"IETF/RFC-8340/RFC-8340.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 8343 This document defines a YANG data model for the management of network\n interfaces. It is expected that interface-type-specific data models\n augment the generic interfaces data model defined in this document.\n The data model includes definitions for configuration and system\n state (status information and counters for the collection of\n statistics).\n\n The YANG data model in this document conforms to the Network\n Management Datastore Architecture (NMDA) defined in RFC 8342.\n\n This document obsoletes RFC 7223.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 o 8343 http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8348","type":"specification","body":"IETF","designation":"RFC 8348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8348.txt","https://www.rfc-editor.org/rfc/rfc8348.pdf"],"folder":"IETF/RFC-8348","files":{"txt":{"path":"standards/IETF/RFC-8348/RFC-8348.txt","sha256":"d2b2f7ab05ec0e6446442df622d8f257559a4339e92af41403bfad4ebcaa56ce"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG data model for the management of\n hardware on a single server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8348.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://truste","scope_keywords":["8348","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null}],"search_text":"IETF RFC 8348 This document defines a YANG data model for the management of\n hardware on a single server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8348.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://truste 8348 http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8391","type":"specification","body":"IETF","designation":"RFC 8391","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8391.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8391.txt","https://www.rfc-editor.org/rfc/rfc8391.pdf"],"folder":"IETF/RFC-8391","files":{"txt":{"path":"standards/IETF/RFC-8391/RFC-8391.txt","sha256":"1c9af7d63cd9ba38f6be8c72bb91f56d83fcce8e158c6da89782df727130106e"}},"tags":["nested-reference","unchanged"],"summary":"This note describes the eXtended Merkle Signature Scheme (XMSS), a\n hash-based digital signature system that is based on existing\n descriptions in scientific literature. This note specifies\n Winternitz One-Time Signature Plus (WOTS+), a one-time signature\n scheme; XMSS, a single-tree scheme; and XMSS^MT, a multi-tree variant\n of XMSS. Both XMSS and XMSS^MT use WOTS+ as a main building block.\n XMSS provides cryptographic digital signatures without relying on the\n conjectured hardness of mathematical problems. Instead, it is proven\n that it only relies on the properties of cryptographic hash\n functions. XMSS provides strong security guarantees and is even\n secure when the collision resistance of the underlying hash function\n is broken. It is suitable for compact implementations, is relatively\n simple to implement, and naturally resists side-channel attacks.\n Unlike most other signature sys","scope_keywords":["8391","hash","hashing","http","https","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8554","folder":"IETF/RFC-8554","source":"IETF/RFC-8554/RFC-8554.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null}],"search_text":"IETF RFC 8391 This note describes the eXtended Merkle Signature Scheme (XMSS), a\n hash-based digital signature system that is based on existing\n descriptions in scientific literature. This note specifies\n Winternitz One-Time Signature Plus (WOTS+), a one-time signature\n scheme; XMSS, a single-tree scheme; and XMSS^MT, a multi-tree variant\n of XMSS. Both XMSS and XMSS^MT use WOTS+ as a main building block.\n XMSS provides cryptographic digital signatures without relying on the\n conjectured hardness of mathematical problems. Instead, it is proven\n that it only relies on the properties of cryptographic hash\n functions. XMSS provides strong security guarantees and is even\n secure when the collision resistance of the underlying hash function\n is broken. It is suitable for compact implementations, is relatively\n simple to implement, and naturally resists side-channel attacks.\n Unlike most other signature sys 8391 hash hashing http https key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8392","type":"specification","body":"IETF","designation":"RFC 8392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8392.txt","https://www.rfc-editor.org/rfc/rfc8392.pdf"],"folder":"IETF/RFC-8392","files":{"txt":{"path":"standards/IETF/RFC-8392/RFC-8392.txt","sha256":"9021ff7c4d274cf34873fe4f4fb17c4fe323247dd0f96bfcab54909bfcdc5f13"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"CBOR Web Token (CWT) is a compact means of representing claims to be\n transferred between two parties. The claims in a CWT are encoded in\n the Concise Binary Object Representation (CBOR), and CBOR Object\n Signing and Encryption (COSE) is used for added application-layer\n security protection. A claim is a piece of information asserted\n about a subject and is represented as a name/value pair consisting of\n a claim name and a claim value. CWT is derived from JSON Web Token\n (JWT) but uses CBOR rather than JSON.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2","scope_keywords":["8392","algorithm","encryption","http","https","issuer","key","keys","license","presentation","registered","signature","subject","trust","wallet"],"parent_legal_regulations":[{"celex":"32025R0848","eli":"https://data.europa.eu/eli/reg_impl/2025/848/oj/eng","id":"2025-848","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-848/2025-848.md","title":"Registration of wallet-relying parties"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 8747","folder":"IETF/RFC-8747","source":"IETF/RFC-8747/RFC-8747.txt","version":null},{"body":"IETF","designation":"RFC 9191","folder":"IETF/RFC-9191","source":"IETF/RFC-9191/RFC-9191.txt","version":null},{"body":"IETF","designation":"RFC 9334","folder":"IETF/RFC-9334","source":"IETF/RFC-9334/RFC-9334.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 8392 CBOR Web Token (CWT) is a compact means of representing claims to be\n transferred between two parties. The claims in a CWT are encoded in\n the Concise Binary Object Representation (CBOR), and CBOR Object\n Signing and Encryption (COSE) is used for added application-layer\n security protection. A claim is a piece of information asserted\n about a subject and is represented as a name/value pair consisting of\n a claim name and a claim value. CWT is derived from JSON Web Token\n (JWT) but uses CBOR rather than JSON.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 8392 algorithm encryption http https issuer key keys license presentation registered signature subject trust wallet cited-by-eu-law implementing-regulation nested-reference unchanged 2025-848 Registration of wallet-relying parties 32025R0848"},{"id":"IETF RFC 8398","type":"specification","body":"IETF","designation":"RFC 8398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8398.txt","https://www.rfc-editor.org/rfc/rfc8398.pdf"],"folder":"IETF/RFC-8398","files":{"txt":{"path":"standards/IETF/RFC-8398/RFC-8398.txt","sha256":"2b84031c2680e1bbb0d6d86559d8eea8604cb90a8a647d8d7ad65a6e8f2bba67"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new name form for inclusion in the otherName\n field of an X.509 Subject Alternative Name and Issuer Alternative\n Name extension that allows a certificate subject to be associated\n with an internationalized email address.\n\n This document updates RFC 5280.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8398.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and th","scope_keywords":["8398","certificate","certificates","http","https","issuer","key","license","path","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 8398 This document defines a new name form for inclusion in the otherName\n field of an X.509 Subject Alternative Name and Issuer Alternative\n Name extension that allows a certificate subject to be associated\n with an internationalized email address.\n\n This document updates RFC 5280.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8398.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and th 8398 certificate certificates http https issuer key license path subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8399","type":"specification","body":"IETF","designation":"RFC 8399","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8399.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8399.txt","https://www.rfc-editor.org/rfc/rfc8399.pdf"],"folder":"IETF/RFC-8399","files":{"txt":{"path":"standards/IETF/RFC-8399/RFC-8399.txt","sha256":"80cf7212c3afd2927baadfc55535163e1438ba8df7c9928e7679737b635c6abc"}},"tags":["nested-reference","unchanged"],"summary":"The updates to RFC 5280 described in this document provide alignment\n with the 2008 specification for Internationalized Domain Names (IDNs)\n and add support for internationalized email addresses in X.509\n certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8399.\n\nHousley Standards Track [Page 1]\n\f\nRFC 8399 I18n Updates to RFC 5280 May 2018\n\nCopyright Notice\n\n Copyright (c) 201","scope_keywords":["8399","algorithm","certificate","certificates","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null}],"search_text":"IETF RFC 8399 The updates to RFC 5280 described in this document provide alignment\n with the 2008 specification for Internationalized Domain Names (IDNs)\n and add support for internationalized email addresses in X.509\n certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8399.\n\nHousley Standards Track [Page 1]\n\f\nRFC 8399 I18n Updates to RFC 5280 May 2018\n\nCopyright Notice\n\n Copyright (c) 201 8399 algorithm certificate certificates http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8410","type":"specification","body":"IETF","designation":"RFC 8410","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8410.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8410.txt","https://www.rfc-editor.org/rfc/rfc8410.pdf"],"folder":"IETF/RFC-8410","files":{"txt":{"path":"standards/IETF/RFC-8410/RFC-8410.txt","sha256":"90a0ff0b3dd661d3e26e1873f40f2ca8b41709a7bbd755a1ed3599c4746313d2"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies algorithm identifiers and ASN.1 encoding\n formats for elliptic curve constructs using the curve25519 and\n curve448 curves. The signature algorithms covered are Ed25519 and\n Ed448. The key agreement algorithms covered are X25519 and X448.\n The encoding for public key, private key, and Edwards-curve Digital\n Signature Algorithm (EdDSA) structures is provided.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai","scope_keywords":["8410","algorithm","algorithms","certificate","certificates","hash","hashing","http","https","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null}],"search_text":"IETF RFC 8410 This document specifies algorithm identifiers and ASN.1 encoding\n formats for elliptic curve constructs using the curve25519 and\n curve448 curves. The signature algorithms covered are Ed25519 and\n Ed448. The key agreement algorithms covered are X25519 and X448.\n The encoding for public key, private key, and Edwards-curve Digital\n Signature Algorithm (EdDSA) structures is provided.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai 8410 algorithm algorithms certificate certificates hash hashing http https key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8412","type":"specification","body":"IETF","designation":"RFC 8412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8412.txt","https://www.rfc-editor.org/rfc/rfc8412.pdf"],"folder":"IETF/RFC-8412","files":{"txt":{"path":"standards/IETF/RFC-8412/RFC-8412.txt","sha256":"1c84803a3b73d6e88e2b3c865b00387440cf5af31c32851d1fced0d61e94ec2b"}},"tags":["nested-reference","unchanged"],"summary":"This document extends \"PA-TNC: A Posture Attribute (PA) Protocol\n Compatible with Trusted Network Connect (TNC)\" (RFC 5792) by\n providing specific attributes and message exchanges to allow\n endpoints to report their installed software inventory information to\n a NEA Server, as defined in \"Network Endpoint Assessment (NEA):\n Overview and Requirements\" (RFC 5209).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www","scope_keywords":["8412","attribute","attributes","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"IETF RFC 8412 This document extends \"PA-TNC: A Posture Attribute (PA) Protocol\n Compatible with Trusted Network Connect (TNC)\" (RFC 5792) by\n providing specific attributes and message exchanges to allow\n endpoints to report their installed software inventory information to\n a NEA Server, as defined in \"Network Endpoint Assessment (NEA):\n Overview and Requirements\" (RFC 5209).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www 8412 attribute attributes http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 8414","type":"specification","body":"IETF","designation":"RFC 8414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8414.txt","https://www.rfc-editor.org/rfc/rfc8414.pdf"],"folder":"IETF/RFC-8414","files":{"txt":{"path":"standards/IETF/RFC-8414/RFC-8414.txt","sha256":"16c816e4e0fdbffb7e910ff3017867bf39debe9cb7f52f5cbc508a052ed660e8"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a metadata format that an OAuth 2.0 client\n can use to obtain the information needed to interact with an\n OAuth 2.0 authorization server, including its endpoint locations and\n authorization server capabilities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8414.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document aut","scope_keywords":["8414","authentication","authorization","encryption","http","https","issuer","key","license","registered","signature","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8725","folder":"IETF/RFC-8725","source":"IETF/RFC-8725/RFC-8725.txt","version":null},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9207","folder":"IETF/RFC-9207","source":"IETF/RFC-9207/RFC-9207.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9470","folder":"IETF/RFC-9470","source":"IETF/RFC-9470/RFC-9470.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8414 This specification defines a metadata format that an OAuth 2.0 client\n can use to obtain the information needed to interact with an\n OAuth 2.0 authorization server, including its endpoint locations and\n authorization server capabilities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8414.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document aut 8414 authentication authorization encryption http https issuer key license registered signature subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8418","type":"specification","body":"IETF","designation":"RFC 8418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8418.txt","https://www.rfc-editor.org/rfc/rfc8418.pdf"],"folder":"IETF/RFC-8418","files":{"txt":{"path":"standards/IETF/RFC-8418/RFC-8418.txt","sha256":"8cb9ba07b58af7532ace29b9ddd3b37f92b116f7967f04c484f05382c8701a58"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using the Elliptic Curve\n Diffie-Hellman (ECDH) key agreement algorithm with curve25519 and\n curve448 in the Cryptographic Message Syntax (CMS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 7841.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8418.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is su","scope_keywords":["8418","algorithm","algorithms","attribute","certificate","encryption","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 8418 This document describes the conventions for using the Elliptic Curve\n Diffie-Hellman (ECDH) key agreement algorithm with curve25519 and\n curve448 in the Cryptographic Message Syntax (CMS).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by\n the Internet Engineering Steering Group (IESG). Further\n information on Internet Standards is available in Section 2 of\n RFC 7841.\n\n Information about the current status of this document, any\n errata, and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8418.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is su 8418 algorithm algorithms attribute certificate encryption http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8419","type":"specification","body":"IETF","designation":"RFC 8419","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8419.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8419.txt","https://www.rfc-editor.org/rfc/rfc8419.pdf"],"folder":"IETF/RFC-8419","files":{"txt":{"path":"standards/IETF/RFC-8419/RFC-8419.txt","sha256":"a5d073c06a170ae7cd8b2c5279854dc73939e8cdaad12543e33d449fd295672b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the Edwards-curve\n Digital Signature Algorithm (EdDSA) for curve25519 and curve448 in\n the Cryptographic Message Syntax (CMS). For each curve, EdDSA\n defines the PureEdDSA and HashEdDSA modes. However, the HashEdDSA\n mode is not used with the CMS. In addition, no context string is\n used with the CMS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.o","scope_keywords":["8419","algorithm","algorithms","attribute","attributes","certificate","certificates","hash","http","https","key","keys","license","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 8419 This document specifies the conventions for using the Edwards-curve\n Digital Signature Algorithm (EdDSA) for curve25519 and curve448 in\n the Cryptographic Message Syntax (CMS). For each curve, EdDSA\n defines the PureEdDSA and HashEdDSA modes. However, the HashEdDSA\n mode is not used with the CMS. In addition, no context string is\n used with the CMS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.o 8419 algorithm algorithms attribute attributes certificate certificates hash http https key keys license signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 8439","type":"specification","body":"IETF","designation":"RFC 8439","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8439.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8439.txt","https://www.rfc-editor.org/rfc/rfc8439.pdf"],"folder":"IETF/RFC-8439","files":{"txt":{"path":"standards/IETF/RFC-8439/RFC-8439.txt","sha256":"25bef70fbf7a07ff45c2fe4cb7c6ce954eac687413d8610603268b4e4415324c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the ChaCha20 stream cipher as well as the use\n of the Poly1305 authenticator, both as stand-alone algorithms and as\n a \"combined mode\", or Authenticated Encryption with Associated Data\n (AEAD) algorithm.\n\n RFC 7539, the predecessor of this document, was meant to serve as a\n stable reference and an implementation guide. It was a product of\n the Crypto Forum Research Group (CFRG). This document merges the\n errata filed against RFC 7539 and adds a little text to the Security\n Considerations section.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the cons","scope_keywords":["8439","algorithm","algorithms","authentication","encryption","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null}],"search_text":"IETF RFC 8439 This document defines the ChaCha20 stream cipher as well as the use\n of the Poly1305 authenticator, both as stand-alone algorithms and as\n a \"combined mode\", or Authenticated Encryption with Associated Data\n (AEAD) algorithm.\n\n RFC 7539, the predecessor of this document, was meant to serve as a\n stable reference and an implementation guide. It was a product of\n the Crypto Forum Research Group (CFRG). This document merges the\n errata filed against RFC 7539 and adds a little text to the Security\n Considerations section.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the cons 8439 algorithm algorithms authentication encryption http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8441","type":"specification","body":"IETF","designation":"RFC 8441","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8441.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8441.txt","https://www.rfc-editor.org/rfc/rfc8441.pdf"],"folder":"IETF/RFC-8441","files":{"txt":{"path":"standards/IETF/RFC-8441/RFC-8441.txt","sha256":"209ea84eae8866098587726a9a78e3d513539afe71fd4fd7cbcffe133a83d535"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a mechanism for running the WebSocket Protocol\n (RFC 6455) over a single stream of an HTTP/2 connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8441.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating","scope_keywords":["8441","http","https","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null}],"search_text":"IETF RFC 8441 This document defines a mechanism for running the WebSocket Protocol\n (RFC 6455) over a single stream of an HTTP/2 connection.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8441.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating 8441 http https key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8447","type":"specification","body":"IETF","designation":"RFC 8447","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8447.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8447.txt","https://www.rfc-editor.org/rfc/rfc8447.pdf"],"folder":"IETF/RFC-8447","files":{"txt":{"path":"standards/IETF/RFC-8447/RFC-8447.txt","sha256":"45ea188a76b41dffce472324923dd208b9440732f9003271242131b6f74deb6a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a number of changes to TLS and DTLS IANA\n registries that range from adding notes to the registry all the way\n to changing the registration policy. These changes were mostly\n motivated by WG review of the TLS- and DTLS-related registries\n undertaken as part of the TLS 1.3 development process.\n\n This document updates the following RFCs: 3749, 5077, 4680, 5246,\n 5705, 5878, 6520, and 7301.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to prov","scope_keywords":["8447","authorization","certificate","http","https","key","license","policies","policy","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8449","folder":"IETF/RFC-8449","source":"IETF/RFC-8449/RFC-8449.txt","version":null},{"body":"IETF","designation":"RFC 8879","folder":"IETF/RFC-8879","source":"IETF/RFC-8879/RFC-8879.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9155","folder":"IETF/RFC-9155","source":"IETF/RFC-9155/RFC-9155.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null}],"search_text":"IETF RFC 8447 This document describes a number of changes to TLS and DTLS IANA\n registries that range from adding notes to the registry all the way\n to changing the registration policy. These changes were mostly\n motivated by WG review of the TLS- and DTLS-related registries\n undertaken as part of the TLS 1.3 development process.\n\n This document updates the following RFCs: 3749, 5077, 4680, 5246,\n 5705, 5878, 6520, and 7301.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to prov 8447 authorization certificate http https key license policies policy presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8449","type":"specification","body":"IETF","designation":"RFC 8449","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8449.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8449.txt","https://www.rfc-editor.org/rfc/rfc8449.pdf"],"folder":"IETF/RFC-8449","files":{"txt":{"path":"standards/IETF/RFC-8449/RFC-8449.txt","sha256":"b67744f9a9fbca30eaa0580ea51ccd455dd1448e75a7c244559954c175e84724"}},"tags":["nested-reference","unchanged"],"summary":"An extension to Transport Layer Security (TLS) is defined that allows\n endpoints to negotiate the maximum size of protected records that\n each will send the other.\n\n This replaces the maximum fragment length extension defined in\n RFC 6066.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8449.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document a","scope_keywords":["8449","algorithm","algorithms","authentication","encryption","http","https","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"IETF RFC 8449 An extension to Transport Layer Security (TLS) is defined that allows\n endpoints to negotiate the maximum size of protected records that\n each will send the other.\n\n This replaces the maximum fragment length extension defined in\n RFC 6066.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8449.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document a 8449 algorithm algorithms authentication encryption http https key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8452","type":"specification","body":"IETF","designation":"RFC 8452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8452.txt","https://www.rfc-editor.org/rfc/rfc8452.pdf"],"folder":"IETF/RFC-8452","files":{"txt":{"path":"standards/IETF/RFC-8452/RFC-8452.txt","sha256":"ca48ec466b401ce5d68d6d1628127a1800adcc16f2573646aaa3d7df284d3c17"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies two authenticated encryption algorithms that are\n nonce misuse resistant -- that is, they do not fail catastrophically\n if a nonce is repeated.\n\n This document is the product of the Crypto Forum Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and ho","scope_keywords":["8452","algorithm","algorithms","encryption","hash","http","https","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 8452 This memo specifies two authenticated encryption algorithms that are\n nonce misuse resistant -- that is, they do not fail catastrophically\n if a nonce is repeated.\n\n This document is the product of the Crypto Forum Research Group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and ho 8452 algorithm algorithms encryption hash http https key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 8461","type":"specification","body":"IETF","designation":"RFC 8461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8461.txt","https://www.rfc-editor.org/rfc/rfc8461.pdf"],"folder":"IETF/RFC-8461","files":{"txt":{"path":"standards/IETF/RFC-8461/RFC-8461.txt","sha256":"31296488efa6ce89fb3a8a26a17ffe3b75f9379acc709aa5f82af6c9ae71283e"}},"tags":["nested-reference","unchanged"],"summary":"SMTP MTA Strict Transport Security (MTA-STS) is a mechanism enabling\n mail service providers (SPs) to declare their ability to receive\n Transport Layer Security (TLS) secure SMTP connections and to specify\n whether sending SMTP servers should refuse to deliver to MX hosts\n that do not offer TLS with a trusted server certificate.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8461.\n\nMar","scope_keywords":["8461","certificate","delivery","encryption","http","https","key","license","pki","policies","policy","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 8461 SMTP MTA Strict Transport Security (MTA-STS) is a mechanism enabling\n mail service providers (SPs) to declare their ability to receive\n Transport Layer Security (TLS) secure SMTP connections and to specify\n whether sending SMTP servers should refuse to deliver to MX hosts\n that do not offer TLS with a trusted server certificate.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8461.\n\nMar 8461 certificate delivery encryption http https key license pki policies policy subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8464","type":"specification","body":"IETF","designation":"RFC 8464","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8464.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8464.txt","https://www.rfc-editor.org/rfc/rfc8464.pdf"],"folder":"IETF/RFC-8464","files":{"txt":{"path":"standards/IETF/RFC-8464/RFC-8464.txt","sha256":"e60c2421d0cb068dd63dc28e52993092800f65a58d3e659c70c10b88a74bc9d7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Uniform Resource Name (URN) namespace for the\n Third Generation Partnership Project 2 (3GPP2) and a Namespace\n Specific String (NSS) for the Mobile Equipment Identity (MEID). The\n structure of an MEID is 15 hexadecimal digits long and is defined in\n the 3GPP2 to uniquely identify each individual mobile equipment\n (e.g., a handset or mobile phone). The 3GPP2 has a requirement to be\n able to use an MEID as a URN. This document fulfills that\n requirement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IES","scope_keywords":["8464","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8465","folder":"IETF/RFC-8465","source":"IETF/RFC-8465/RFC-8465.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null}],"search_text":"IETF RFC 8464 This document defines a Uniform Resource Name (URN) namespace for the\n Third Generation Partnership Project 2 (3GPP2) and a Namespace\n Specific String (NSS) for the Mobile Equipment Identity (MEID). The\n structure of an MEID is 15 hexadecimal digits long and is defined in\n the 3GPP2 to uniquely identify each individual mobile equipment\n (e.g., a handset or mobile phone). The 3GPP2 has a requirement to be\n able to use an MEID as a URN. This document fulfills that\n requirement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IES 8464 http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8465","type":"specification","body":"IETF","designation":"RFC 8465","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8465.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8465.txt","https://www.rfc-editor.org/rfc/rfc8465.pdf"],"folder":"IETF/RFC-8465","files":{"txt":{"path":"standards/IETF/RFC-8465/RFC-8465.txt","sha256":"15123c29c6681658d4fec181c17133e99fb98a448871bd00f2a62f6af8957bad"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how the Uniform Resource Name (URN) namespace\n reserved for the Third Generation Partnership Project 2 (3GPP2)\n identities and its Namespace Specific String (NSS) for the Mobile\n Equipment Identity (MEID) can be used as an Instance ID. The purpose\n of this Instance ID is to fulfill the requirements for defining how a\n specific URN needs to be constructed and used in the \"+sip.instance\"\n Contact header field parameter for outbound behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candida","scope_keywords":["8465","http","https","key","license","pid","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null}],"search_text":"IETF RFC 8465 This document specifies how the Uniform Resource Name (URN) namespace\n reserved for the Third Generation Partnership Project 2 (3GPP2)\n identities and its Namespace Specific String (NSS) for the Mobile\n Equipment Identity (MEID) can be used as an Instance ID. The purpose\n of this Instance ID is to fulfill the requirements for defining how a\n specific URN needs to be constructed and used in the \"+sip.instance\"\n Contact header field parameter for outbound behavior.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candida 8465 http https key license pid registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8467","type":"specification","body":"IETF","designation":"RFC 8467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8467.txt","https://www.rfc-editor.org/rfc/rfc8467.pdf"],"folder":"IETF/RFC-8467","files":{"txt":{"path":"standards/IETF/RFC-8467/RFC-8467.txt","sha256":"f01aaa06e41a4421b41caff1cade7cbd5830d57f011e16682eb315da77a35f00"}},"tags":["nested-reference","unchanged"],"summary":"RFC 7830 specifies the \"Padding\" option for Extension Mechanisms for\n DNS (EDNS(0)) but does not specify the actual padding length for\n specific applications. This memo lists the possible options\n (\"padding policies\"), discusses the implications of each option, and\n provides a recommended (experimental) option.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standard; see","scope_keywords":["8467","http","https","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8484","folder":"IETF/RFC-8484","source":"IETF/RFC-8484/RFC-8484.txt","version":null},{"body":"IETF","designation":"RFC 8490","folder":"IETF/RFC-8490","source":"IETF/RFC-8490/RFC-8490.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null},{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 8467 RFC 7830 specifies the \"Padding\" option for Extension Mechanisms for\n DNS (EDNS(0)) but does not specify the actual padding length for\n specific applications. This memo lists the possible options\n (\"padding policies\"), discusses the implications of each option, and\n provides a recommended (experimental) option.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standard; see 8467 http https key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 8470","type":"specification","body":"IETF","designation":"RFC 8470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8470.txt","https://www.rfc-editor.org/rfc/rfc8470.pdf"],"folder":"IETF/RFC-8470","files":{"txt":{"path":"standards/IETF/RFC-8470/RFC-8470.txt","sha256":"483c316c2b5d2687357fc66e3da5acc153cc4cfe9817d92da8f63b9e21a62974"}},"tags":["nested-reference","unchanged"],"summary":"Using TLS early data creates an exposure to the possibility of a\n replay attack. This document defines mechanisms that allow clients\n to communicate with servers about HTTP requests that are sent in\n early data. Techniques are described that use these mechanisms to\n mitigate the risk of replay.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8470.\n\nCopyright Notice\n\n Copyright (c) 2018 ","scope_keywords":["8470","delivery","http","https","key","license","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8740","folder":"IETF/RFC-8740","source":"IETF/RFC-8740/RFC-8740.txt","version":null},{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 8470 Using TLS early data creates an exposure to the possibility of a\n replay attack. This document defines mechanisms that allow clients\n to communicate with servers about HTTP requests that are sent in\n early data. Techniques are described that use these mechanisms to\n mitigate the risk of replay.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8470.\n\nCopyright Notice\n\n Copyright (c) 2018  8470 delivery http https key license risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8471","type":"specification","body":"IETF","designation":"RFC 8471","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8471.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8471.txt","https://www.rfc-editor.org/rfc/rfc8471.pdf"],"folder":"IETF/RFC-8471","files":{"txt":{"path":"standards/IETF/RFC-8471/RFC-8471.txt","sha256":"2c6e05b58e2d19c99e33e828f22b6e143be9cd02c2af06c434d42b6628d8a109"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies version 1.0 of the Token Binding protocol.\n The Token Binding protocol allows client/server applications to\n create long-lived, uniquely identifiable TLS bindings spanning\n multiple TLS sessions and connections. Applications are then enabled\n to cryptographically bind security tokens to the TLS layer,\n preventing token export and replay attacks. To protect privacy, the\n Token Binding identifiers are only conveyed over TLS and can be reset\n by the user at any time.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Infor","scope_keywords":["8471","hash","http","https","key","license","signature","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8472","folder":"IETF/RFC-8472","source":"IETF/RFC-8472/RFC-8472.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 8471 This document specifies version 1.0 of the Token Binding protocol.\n The Token Binding protocol allows client/server applications to\n create long-lived, uniquely identifiable TLS bindings spanning\n multiple TLS sessions and connections. Applications are then enabled\n to cryptographically bind security tokens to the TLS layer,\n preventing token export and replay attacks. To protect privacy, the\n Token Binding identifiers are only conveyed over TLS and can be reset\n by the user at any time.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Infor 8471 hash http https key license signature subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8472","type":"specification","body":"IETF","designation":"RFC 8472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8472.txt","https://www.rfc-editor.org/rfc/rfc8472.pdf"],"folder":"IETF/RFC-8472","files":{"txt":{"path":"standards/IETF/RFC-8472/RFC-8472.txt","sha256":"2d586d0b8291949a0e93e154e2bfdaa61ef5e0f5eb3d391392008fc8a7cf393f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Transport Layer Security (TLS) extension\n for the negotiation of Token Binding protocol version and key\n parameters. Negotiation of Token Binding in TLS 1.3 and later\n versions is beyond the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8472.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document ","scope_keywords":["8472","algorithm","http","https","key","license","presentation","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null},{"body":"IETF","designation":"RFC 8473","folder":"IETF/RFC-8473","source":"IETF/RFC-8473/RFC-8473.txt","version":null}],"search_text":"IETF RFC 8472 This document specifies a Transport Layer Security (TLS) extension\n for the negotiation of Token Binding protocol version and key\n parameters. Negotiation of Token Binding in TLS 1.3 and later\n versions is beyond the scope of this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8472.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document  8472 algorithm http https key license presentation signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8473","type":"specification","body":"IETF","designation":"RFC 8473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8473.txt","https://www.rfc-editor.org/rfc/rfc8473.pdf"],"folder":"IETF/RFC-8473","files":{"txt":{"path":"standards/IETF/RFC-8473/RFC-8473.txt","sha256":"3db094d2a6d15745c29a70811bd505131be2c44248084207815ec869f558f307"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a collection of mechanisms that allow HTTP\n servers to cryptographically bind security tokens (such as cookies\n and OAuth tokens) to TLS connections.\n\n We describe both first-party and federated scenarios. In a first-\n party scenario, an HTTP server is able to cryptographically bind the\n security tokens that it issues to a client -- and that the client\n subsequently returns to the server -- to the TLS connection between\n the client and the server. Such bound security tokens are protected\n from misuse, since the server can generally detect if they are\n replayed inappropriately, e.g., over other TLS connections.\n\n Federated Token Bindings, on the other hand, allow servers to\n cryptographically bind security tokens to a TLS connection that the\n client has with a different server than the one issuing the token.\n\n This document is a companion document to \"The Token Bin","scope_keywords":["8473","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8471","folder":"IETF/RFC-8471","source":"IETF/RFC-8471/RFC-8471.txt","version":null}],"search_text":"IETF RFC 8473 This document describes a collection of mechanisms that allow HTTP\n servers to cryptographically bind security tokens (such as cookies\n and OAuth tokens) to TLS connections.\n\n We describe both first-party and federated scenarios. In a first-\n party scenario, an HTTP server is able to cryptographically bind the\n security tokens that it issues to a client -- and that the client\n subsequently returns to the server -- to the TLS connection between\n the client and the server. Such bound security tokens are protected\n from misuse, since the server can generally detect if they are\n replayed inappropriately, e.g., over other TLS connections.\n\n Federated Token Bindings, on the other hand, allow servers to\n cryptographically bind security tokens to a TLS connection that the\n client has with a different server than the one issuing the token.\n\n This document is a companion document to \"The Token Bin 8473 http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8474","type":"specification","body":"IETF","designation":"RFC 8474","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8474.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8474.txt","https://www.rfc-editor.org/rfc/rfc8474.pdf"],"folder":"IETF/RFC-8474","files":{"txt":{"path":"standards/IETF/RFC-8474/RFC-8474.txt","sha256":"a5f7b850f3b222805030aa1bbce800272fe1e173c8a322d49638e75a789782a4"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3501 (IMAP4rev1) with persistent\n identifiers on mailboxes and messages to allow clients to more\n efficiently reuse cached data when resources have changed location on\n the server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8474.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Th","scope_keywords":["8474","attribute","http","https","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 8474 This document updates RFC 3501 (IMAP4rev1) with persistent\n identifiers on mailboxes and messages to allow clients to more\n efficiently reuse cached data when resources have changed location on\n the server.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8474.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Th 8474 attribute http https identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8511","type":"specification","body":"IETF","designation":"RFC 8511","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8511.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8511.txt","https://www.rfc-editor.org/rfc/rfc8511.pdf"],"folder":"IETF/RFC-8511","files":{"txt":{"path":"standards/IETF/RFC-8511/RFC-8511.txt","sha256":"cf8118682113f8887a8db149d4148051bfeb7700112a7e153033337686c50739"}},"tags":["nested-reference","unchanged"],"summary":"Active Queue Management (AQM) mechanisms allow for burst tolerance\n while enforcing short queues to minimise the time that packets spend\n enqueued at a bottleneck. This can cause noticeable performance\n degradation for TCP connections traversing such a bottleneck,\n especially if there are only a few flows or their bandwidth-delay\n product (BDP) is large. The reception of a Congestion Experienced\n (CE) Explicit Congestion Notification (ECN) mark indicates that an\n AQM mechanism is used at the bottleneck, and the bottleneck network\n queue is therefore likely to be short. Feedback of this signal\n allows the TCP sender-side ECN reaction in congestion avoidance to\n reduce the Congestion Window (cwnd) by a smaller amount than the\n congestion control algorithm's reaction to inferred packet loss.\n Therefore, this specification defines an experimental change to the\n TCP reaction specified in RFC ","scope_keywords":["8511","algorithm","algorithms","http","https","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9002","folder":"IETF/RFC-9002","source":"IETF/RFC-9002/RFC-9002.txt","version":null}],"search_text":"IETF RFC 8511 Active Queue Management (AQM) mechanisms allow for burst tolerance\n while enforcing short queues to minimise the time that packets spend\n enqueued at a bottleneck. This can cause noticeable performance\n degradation for TCP connections traversing such a bottleneck,\n especially if there are only a few flows or their bandwidth-delay\n product (BDP) is large. The reception of a Congestion Experienced\n (CE) Explicit Congestion Notification (ECN) mark indicates that an\n AQM mechanism is used at the bottleneck, and the bottleneck network\n queue is therefore likely to be short. Feedback of this signal\n allows the TCP sender-side ECN reaction in congestion avoidance to\n reduce the Congestion Window (cwnd) by a smaller amount than the\n congestion control algorithm's reaction to inferred packet loss.\n Therefore, this specification defines an experimental change to the\n TCP reaction specified in RFC  8511 algorithm algorithms http https key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8521","type":"specification","body":"IETF","designation":"RFC 8521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8521.txt","https://www.rfc-editor.org/rfc/rfc8521.pdf"],"folder":"IETF/RFC-8521","files":{"txt":{"path":"standards/IETF/RFC-8521/RFC-8521.txt","sha256":"a7d98ba51006e059fe9e2541a6a2d1d9fa40ed851f1c7e0c3d4ef1b9e4b844cb"}},"tags":["nested-reference","unchanged"],"summary":"The Registration Data Access Protocol (RDAP) includes a method that\n can be used to identify the authoritative server for processing\n domain name, IP address, and autonomous system number queries. The\n method does not describe how to identify the authoritative server for\n processing other RDAP query types, such as entity queries. This\n limitation exists because the identifiers associated with these query\n types are typically unstructured. This document updates RFC 7484 by\n describing an operational practice that can be used to add structure\n to RDAP identifiers and that makes it possible to identify the\n authoritative server for additional RDAP queries.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a","scope_keywords":["8521","attribute","http","https","key","license","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 8521 The Registration Data Access Protocol (RDAP) includes a method that\n can be used to identify the authoritative server for processing\n domain name, IP address, and autonomous system number queries. The\n method does not describe how to identify the authoritative server for\n processing other RDAP query types, such as entity queries. This\n limitation exists because the identifiers associated with these query\n types are typically unstructured. This document updates RFC 7484 by\n describing an operational practice that can be used to add structure\n to RDAP identifiers and that makes it possible to identify the\n authoritative server for additional RDAP queries.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a 8521 attribute http https key license path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 8550","type":"specification","body":"IETF","designation":"RFC 8550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8550.txt","https://www.rfc-editor.org/rfc/rfc8550.pdf"],"folder":"IETF/RFC-8550","files":{"txt":{"path":"standards/IETF/RFC-8550/RFC-8550.txt","sha256":"adf5aa630e6fd10f75de524e4af249302548a68d6cb7254bf3bfb99b544d6c7a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) v4.0 agents.\n S/MIME provides a method to send and receive secure MIME messages,\n and certificates are an integral part of S/MIME agent processing.\n S/MIME agents validate certificates as described in RFC 5280\n (\"Internet X.509 Public Key Infrastructure Certificate and\n Certificate Revocation List (CRL) Profile\"). S/MIME agents must meet\n the certificate-processing requirements in this document as well as\n those in RFC 5280. This document obsoletes RFC 5750.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG","scope_keywords":["8550","algorithm","algorithms","attribute","certificate","certificates","crl","http","https","key","keys","license","management","path","pki","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 8550 This document specifies conventions for X.509 certificate usage by\n Secure/Multipurpose Internet Mail Extensions (S/MIME) v4.0 agents.\n S/MIME provides a method to send and receive secure MIME messages,\n and certificates are an integral part of S/MIME agent processing.\n S/MIME agents validate certificates as described in RFC 5280\n (\"Internet X.509 Public Key Infrastructure Certificate and\n Certificate Revocation List (CRL) Profile\"). S/MIME agents must meet\n the certificate-processing requirements in this document as well as\n those in RFC 5280. This document obsoletes RFC 5750.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG 8550 algorithm algorithms attribute certificate certificates crl http https key keys license management path pki profile nested-reference unchanged"},{"id":"IETF RFC 8554","type":"specification","body":"IETF","designation":"RFC 8554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8554.txt","https://www.rfc-editor.org/rfc/rfc8554.pdf"],"folder":"IETF/RFC-8554","files":{"txt":{"path":"standards/IETF/RFC-8554/RFC-8554.txt","sha256":"d5bfdbd457dfe7bc5f67cc1f62482999c2f55bf8033f2af56da323f2ffc2c055"}},"tags":["nested-reference","unchanged"],"summary":"This note describes a digital-signature system based on cryptographic\n hash functions, following the seminal work in this area of Lamport,\n Diffie, Winternitz, and Merkle, as adapted by Leighton and Micali in\n 1995. It specifies a one-time signature scheme and a general\n signature scheme. These systems provide asymmetric authentication\n without using large integer mathematics and can achieve a high\n security level. They are suitable for compact implementations, are\n relatively simple to implement, and are naturally resistant to side-\n channel attacks. Unlike many other signature systems, hash-based\n signatures would still be secure even if it proves feasible for an\n attacker to build a quantum computer.\n\n This document is a product of the Crypto Forum Research Group (CFRG)\n in the IRTF. This has been reviewed by many researchers, both in the\n research group and outside of it. The Acknowl","scope_keywords":["8554","algorithm","authentication","hash","http","https","key","keys","license","path","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8778","folder":"IETF/RFC-8778","source":"IETF/RFC-8778/RFC-8778.txt","version":null}],"search_text":"IETF RFC 8554 This note describes a digital-signature system based on cryptographic\n hash functions, following the seminal work in this area of Lamport,\n Diffie, Winternitz, and Merkle, as adapted by Leighton and Micali in\n 1995. It specifies a one-time signature scheme and a general\n signature scheme. These systems provide asymmetric authentication\n without using large integer mathematics and can achieve a high\n security level. They are suitable for compact implementations, are\n relatively simple to implement, and are naturally resistant to side-\n channel attacks. Unlike many other signature systems, hash-based\n signatures would still be secure even if it proves feasible for an\n attacker to build a quantum computer.\n\n This document is a product of the Crypto Forum Research Group (CFRG)\n in the IRTF. This has been reviewed by many researchers, both in the\n research group and outside of it. The Acknowl 8554 algorithm authentication hash http https key keys license path signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8586","type":"specification","body":"IETF","designation":"RFC 8586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8586.txt","https://www.rfc-editor.org/rfc/rfc8586.pdf"],"folder":"IETF/RFC-8586","files":{"txt":{"path":"standards/IETF/RFC-8586/RFC-8586.txt","sha256":"6013c8ad038f4ed7d5e6b9a6b70016b3f6de1327dec6241d8479506bb58259b4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the CDN-Loop request header field for HTTP.\n CDN-Loop addresses an operational need that occurs when an HTTP\n request is intentionally forwarded between Content Delivery Networks\n (CDNs), but is then accidentally or maliciously re-routed back into\n the original CDN causing a non-terminating loop. The new header\n field can be used to identify the error and terminate the loop.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on","scope_keywords":["8586","delivery","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8768","folder":"IETF/RFC-8768","source":"IETF/RFC-8768/RFC-8768.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null}],"search_text":"IETF RFC 8586 This document defines the CDN-Loop request header field for HTTP.\n CDN-Loop addresses an operational need that occurs when an HTTP\n request is intentionally forwarded between Content Delivery Networks\n (CDNs), but is then accidentally or maliciously re-routed back into\n the original CDN causing a non-terminating loop. The new header\n field can be used to identify the error and terminate the loop.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on 8586 delivery http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8619","type":"specification","body":"IETF","designation":"RFC 8619","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8619.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8619.txt","https://www.rfc-editor.org/rfc/rfc8619.pdf"],"folder":"IETF/RFC-8619","files":{"txt":{"path":"standards/IETF/RFC-8619/RFC-8619.txt","sha256":"a7546d0558f387f62e2da717547a8b26335d86fdcdb49c7bb3d185547dad2793"}},"tags":["nested-reference","unchanged"],"summary":"RFC 5869 specifies the HMAC-based Extract-and-Expand Key Derivation\n Function (HKDF) algorithm. This document assigns algorithm\n identifiers to the HKDF algorithm when used with three common one-way\n hash functions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8619.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document authors. All rights reser","scope_keywords":["8619","algorithm","algorithms","authentication","hash","http","https","key","license","pki","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null}],"search_text":"IETF RFC 8619 RFC 5869 specifies the HMAC-based Extract-and-Expand Key Derivation\n Function (HKDF) algorithm. This document assigns algorithm\n identifiers to the HKDF algorithm when used with three common one-way\n hash functions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8619.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document authors. All rights reser 8619 algorithm algorithms authentication hash http https key license pki subject trust nested-reference unchanged"},{"id":"IETF RFC 8620","type":"specification","body":"IETF","designation":"RFC 8620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8620.txt","https://www.rfc-editor.org/rfc/rfc8620.pdf"],"folder":"IETF/RFC-8620","files":{"txt":{"path":"standards/IETF/RFC-8620/RFC-8620.txt","sha256":"2faef52947b75a4a624154ae6bde930688c1a2f122f05925273c7d8a9a85cd25"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a protocol for clients to efficiently query,\n fetch, and modify JSON-based data objects, with support for push\n notification of changes and fast resynchronisation and for out-of-\n band binary data upload/download.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8620.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document aut","scope_keywords":["8620","authentication","encryption","holder","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8620 This document specifies a protocol for clients to efficiently query,\n fetch, and modify JSON-based data objects, with support for push\n notification of changes and fast resynchronisation and for out-of-\n band binary data upload/download.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8620.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document aut 8620 authentication encryption holder http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 8628","type":"specification","body":"IETF","designation":"RFC 8628","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8628.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8628.txt","https://www.rfc-editor.org/rfc/rfc8628.pdf"],"folder":"IETF/RFC-8628","files":{"txt":{"path":"standards/IETF/RFC-8628/RFC-8628.txt","sha256":"ebd3c37415aa665b55b412fccd9571943e8dbd3f2bf0b18fee4924264252decd"}},"tags":["nested-reference","unchanged"],"summary":"The OAuth 2.0 device authorization grant is designed for Internet-\n connected devices that either lack a browser to perform a user-agent-\n based authorization or are input constrained to the extent that\n requiring the user to input text in order to authenticate during the\n authorization flow is impractical. It enables OAuth clients on such\n devices (like smart TVs, media consoles, digital picture frames, and\n printers) to obtain user authorization to access protected resources\n by using a user agent on a separate device.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available","scope_keywords":["8628","authorization","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null}],"search_text":"IETF RFC 8628 The OAuth 2.0 device authorization grant is designed for Internet-\n connected devices that either lack a browser to perform a user-agent-\n based authorization or are input constrained to the extent that\n requiring the user to input text in order to authenticate during the\n authorization flow is impractical. It enables OAuth clients on such\n devices (like smart TVs, media consoles, digital picture frames, and\n printers) to obtain user authorization to access protected resources\n by using a user agent on a separate device.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available 8628 authorization http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 8693","type":"specification","body":"IETF","designation":"RFC 8693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8693.txt","https://www.rfc-editor.org/rfc/rfc8693.pdf"],"folder":"IETF/RFC-8693","files":{"pdf":{"path":"standards/IETF/RFC-8693/RFC-8693.pdf","sha256":"6547a40e9301e1bb3e28ba72d8858b6e1c7735fae9f97da985a00b462211a07d"},"txt":{"path":"standards/IETF/RFC-8693/RFC-8693.txt","sha256":"358d658014738bf4dc56c8aae2094ce716ede23b6d5a80488a7dc8e8d72da609"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a protocol for an HTTP- and JSON-based\n Security Token Service (STS) by defining how to request and obtain\n security tokens from OAuth 2.0 authorization servers, including\n security tokens employing impersonation and delegation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8693.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as","scope_keywords":["8693","authorization","credential","credentials","http","https","license","presentation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null}],"search_text":"IETF RFC 8693 This specification defines a protocol for an HTTP- and JSON-based\n Security Token Service (STS) by defining how to request and obtain\n security tokens from OAuth 2.0 authorization servers, including\n security tokens employing impersonation and delegation.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8693.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as 8693 authorization credential credentials http https license presentation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8696","type":"specification","body":"IETF","designation":"RFC 8696","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8696.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8696.txt","https://www.rfc-editor.org/rfc/rfc8696.pdf"],"folder":"IETF/RFC-8696","files":{"pdf":{"path":"standards/IETF/RFC-8696/RFC-8696.pdf","sha256":"8b3044124ca2fc914e4e5c9af5d07b4b76318ef5940898deec0fa63ee4558b2e"},"txt":{"path":"standards/IETF/RFC-8696/RFC-8696.txt","sha256":"ad4451b691600e2bea3a701660a207c50674e19369869b012bf2cd230672de19"}},"tags":["nested-reference","unchanged"],"summary":"The invention of a large-scale quantum computer would pose a serious\n challenge for the cryptographic algorithms that are widely deployed\n today. The Cryptographic Message Syntax (CMS) supports key transport\n and key agreement algorithms that could be broken by the invention of\n such a quantum computer. By storing communications that are\n protected with the CMS today, someone could decrypt them in the\n future when a large-scale quantum computer becomes available. Once\n quantum-secure key management algorithms are available, the CMS will\n be extended to support the new algorithms if the existing syntax does\n not accommodate them. This document describes a mechanism to protect\n today's communication from the future invention of a large-scale\n quantum computer by mixing the output of key transport and key\n agreement algorithms with a pre-shared key.\n\nStatus of This Memo\n\n This is an Interne","scope_keywords":["8696","algorithm","algorithms","encryption","http","https","key","keys","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null}],"search_text":"IETF RFC 8696 The invention of a large-scale quantum computer would pose a serious\n challenge for the cryptographic algorithms that are widely deployed\n today. The Cryptographic Message Syntax (CMS) supports key transport\n and key agreement algorithms that could be broken by the invention of\n such a quantum computer. By storing communications that are\n protected with the CMS today, someone could decrypt them in the\n future when a large-scale quantum computer becomes available. Once\n quantum-secure key management algorithms are available, the CMS will\n be extended to support the new algorithms if the existing syntax does\n not accommodate them. This document describes a mechanism to protect\n today's communication from the future invention of a large-scale\n quantum computer by mixing the output of key transport and key\n agreement algorithms with a pre-shared key.\n\nStatus of This Memo\n\n This is an Interne 8696 algorithm algorithms encryption http https key keys license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 8705","type":"specification","body":"IETF","designation":"RFC 8705","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8705.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8705.txt","https://www.rfc-editor.org/rfc/rfc8705.pdf"],"folder":"IETF/RFC-8705","files":{"pdf":{"path":"standards/IETF/RFC-8705/RFC-8705.pdf","sha256":"274affc3b5e2386fd88931806a4b157d7bad8cad695c052e9c809c1f7e427e0d"},"txt":{"path":"standards/IETF/RFC-8705/RFC-8705.txt","sha256":"6e45a1ee94c6a6a177a4cb077fe67d74bd70c1218c9362f2db2f153239612414"}},"tags":["nested-reference","unchanged"],"summary":"This document describes OAuth client authentication and certificate-\n bound access and refresh tokens using mutual Transport Layer Security\n (TLS) authentication with X.509 certificates. OAuth clients are\n provided a mechanism for authentication to the authorization server\n using mutual TLS, based on either self-signed certificates or public\n key infrastructure (PKI). OAuth authorization servers are provided a\n mechanism for binding access tokens to a client's mutual-TLS\n certificate, and OAuth protected resources are provided a method for\n ensuring that such an access token presented to it was issued to the\n client presenting the token.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for ","scope_keywords":["8705","authentication","authorization","certificate","certificates","credential","credentials","http","https","key","license","pki","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8705 This document describes OAuth client authentication and certificate-\n bound access and refresh tokens using mutual Transport Layer Security\n (TLS) authentication with X.509 certificates. OAuth clients are\n provided a mechanism for authentication to the authorization server\n using mutual TLS, based on either self-signed certificates or public\n key infrastructure (PKI). OAuth authorization servers are provided a\n mechanism for binding access tokens to a client's mutual-TLS\n certificate, and OAuth protected resources are provided a method for\n ensuring that such an access token presented to it was issued to the\n client presenting the token.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for  8705 authentication authorization certificate certificates credential credentials http https key license pki subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 8707","type":"specification","body":"IETF","designation":"RFC 8707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8707.txt","https://www.rfc-editor.org/rfc/rfc8707.pdf"],"folder":"IETF/RFC-8707","files":{"pdf":{"path":"standards/IETF/RFC-8707/RFC-8707.pdf","sha256":"2b50f376b4e3e58a6e008536f939117204127a03dd3a384d701eaa6e31eedfc3"},"txt":{"path":"standards/IETF/RFC-8707/RFC-8707.txt","sha256":"3b89844a938b9219571931b664ed4a7b380555a4dda1df4e9445a2f72188e76b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an extension to the OAuth 2.0 Authorization\n Framework defining request parameters that enable a client to\n explicitly signal to an authorization server about the identity of\n the protected resource(s) to which it is requesting access.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8707.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identifie","scope_keywords":["8707","authorization","http","https","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8707 This document specifies an extension to the OAuth 2.0 Authorization\n Framework defining request parameters that enable a client to\n explicitly signal to an authorization server about the identity of\n the protected resource(s) to which it is requesting access.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8707.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identifie 8707 authorization http https key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8725","type":"specification","body":"IETF","designation":"RFC 8725","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8725.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8725.txt","https://www.rfc-editor.org/rfc/rfc8725.pdf"],"folder":"IETF/RFC-8725","files":{"pdf":{"path":"standards/IETF/RFC-8725/RFC-8725.pdf","sha256":"e45310f8efcb408936388ec3d40e41003d206be3d382df8787ef469b71a7aede"},"txt":{"path":"standards/IETF/RFC-8725/RFC-8725.txt","sha256":"737b7013a2495dcfd5481cf4c57c87e2455d537c4cec1140c9096a71fcef0812"}},"tags":["nested-reference","unchanged"],"summary":"JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security\n tokens that contain a set of claims that can be signed and/or\n encrypted. JWTs are being widely used and deployed as a simple\n security token format in numerous protocols and applications, both in\n the area of digital identity and in other application areas. This\n Best Current Practices document updates RFC 7519 to provide\n actionable guidance leading to secure implementation and deployment\n of JWTs.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the curren","scope_keywords":["8725","algorithm","algorithms","authentication","encryption","http","https","issuer","key","keys","license","pid","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 9068","folder":"IETF/RFC-9068","source":"IETF/RFC-9068/RFC-9068.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 8725 JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security\n tokens that contain a set of claims that can be signed and/or\n encrypted. JWTs are being widely used and deployed as a simple\n security token format in numerous protocols and applications, both in\n the area of digital identity and in other application areas. This\n Best Current Practices document updates RFC 7519 to provide\n actionable guidance leading to secure implementation and deployment\n of JWTs.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the curren 8725 algorithm algorithms authentication encryption http https issuer key keys license pid signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8740","type":"specification","body":"IETF","designation":"RFC 8740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8740.txt","https://www.rfc-editor.org/rfc/rfc8740.pdf"],"folder":"IETF/RFC-8740","files":{"pdf":{"path":"standards/IETF/RFC-8740/RFC-8740.pdf","sha256":"43e0ea508637a7cebb3d04942339490318a097778c60211cdbb08c5e6fbc1784"},"txt":{"path":"standards/IETF/RFC-8740/RFC-8740.txt","sha256":"baa7c672b48c926094807245a8a3376afd420c6070a970d1b1c99b23b0b9878b"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 7540 by forbidding TLS 1.3 post-handshake\n authentication, as an analog to the existing TLS 1.2 renegotiation\n restriction.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8740.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg","scope_keywords":["8740","authentication","certificate","http","https","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9001","folder":"IETF/RFC-9001","source":"IETF/RFC-9001/RFC-9001.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null}],"search_text":"IETF RFC 8740 This document updates RFC 7540 by forbidding TLS 1.3 post-handshake\n authentication, as an analog to the existing TLS 1.2 renegotiation\n restriction.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8740.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Leg 8740 authentication certificate http https key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8742","type":"specification","body":"IETF","designation":"RFC 8742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8742.txt","https://www.rfc-editor.org/rfc/rfc8742.pdf"],"folder":"IETF/RFC-8742","files":{"pdf":{"path":"standards/IETF/RFC-8742/RFC-8742.pdf","sha256":"b7f290da0681bbb439f7ad94a8d5c796e805079fa876328cea9e324078ffb8f6"},"txt":{"path":"standards/IETF/RFC-8742/RFC-8742.txt","sha256":"4462966836b60f42ebae9b5f1d2a479c328e16f0380a3434311a083bccbce30e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Concise Binary Object Representation\n (CBOR) Sequence format and associated media type \"application/cbor-\n seq\". A CBOR Sequence consists of any number of encoded CBOR data\n items, simply concatenated in sequence.\n\n Structured syntax suffixes for media types allow other media types to\n build on them and make it explicit that they are built on an existing\n media type as their foundation. This specification defines and\n registers \"+cbor-seq\" as a structured syntax suffix for CBOR\n Sequences.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in ","scope_keywords":["8742","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null}],"search_text":"IETF RFC 8742 This document describes the Concise Binary Object Representation\n (CBOR) Sequence format and associated media type \"application/cbor-\n seq\". A CBOR Sequence consists of any number of encoded CBOR data\n items, simply concatenated in sequence.\n\n Structured syntax suffixes for media types allow other media types to\n build on them and make it explicit that they are built on an existing\n media type as their foundation. This specification defines and\n registers \"+cbor-seq\" as a structured syntax suffix for CBOR\n Sequences.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in  8742 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8747","type":"specification","body":"IETF","designation":"RFC 8747","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8747.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8747.txt","https://www.rfc-editor.org/rfc/rfc8747.pdf"],"folder":"IETF/RFC-8747","files":{"pdf":{"path":"standards/IETF/RFC-8747/RFC-8747.pdf","sha256":"dc12041dcae5a1b24c006a32b837a7a535f4b21a32b27ea7b3ee931f9106cc1c"},"txt":{"path":"standards/IETF/RFC-8747/RFC-8747.txt","sha256":"9b695379f119f9675828d054f1b0e76014c06c9a59dccef8bb417e0420272dda"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes how to declare in a CBOR Web Token (CWT)\n (which is defined by RFC 8392) that the presenter of the CWT\n possesses a particular proof-of-possession key. Being able to prove\n possession of a key is also sometimes described as being the holder-\n of-key. This specification provides equivalent functionality to\n \"Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)\" (RFC\n 7800) but using Concise Binary Object Representation (CBOR) and CWTs\n rather than JavaScript Object Notation (JSON) and JSON Web Tokens\n (JWTs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Interne","scope_keywords":["8747","encryption","holder","http","https","issuer","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 8747 This specification describes how to declare in a CBOR Web Token (CWT)\n (which is defined by RFC 8392) that the presenter of the CWT\n possesses a particular proof-of-possession key. Being able to prove\n possession of a key is also sometimes described as being the holder-\n of-key. This specification provides equivalent functionality to\n \"Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)\" (RFC\n 7800) but using Concise Binary Object Representation (CBOR) and CWTs\n rather than JavaScript Object Notation (JSON) and JSON Web Tokens\n (JWTs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Interne 8747 encryption holder http https issuer key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8768","type":"specification","body":"IETF","designation":"RFC 8768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8768.txt","https://www.rfc-editor.org/rfc/rfc8768.pdf"],"folder":"IETF/RFC-8768","files":{"pdf":{"path":"standards/IETF/RFC-8768/RFC-8768.pdf","sha256":"6eaff9e7a3e92b8724b563812320049d23cc1bdc9ce4fcf5a0be3203a612c2f4"},"txt":{"path":"standards/IETF/RFC-8768/RFC-8768.txt","sha256":"08655371705654b4920beb032221b806a2b37f281a3ab7353d31ec2e537e1f84"}},"tags":["nested-reference","unchanged"],"summary":"The presence of Constrained Application Protocol (CoAP) proxies may\n lead to infinite forwarding loops, which is undesirable. To prevent\n and detect such loops, this document specifies the Hop-Limit CoAP\n option.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8768.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved","scope_keywords":["8768","http","https","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8768 The presence of Constrained Application Protocol (CoAP) proxies may\n lead to infinite forwarding loops, which is undesirable. To prevent\n and detect such loops, this document specifies the Hop-Limit CoAP\n option.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8768.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved 8768 http https key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8778","type":"specification","body":"IETF","designation":"RFC 8778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8778.txt","https://www.rfc-editor.org/rfc/rfc8778.pdf"],"folder":"IETF/RFC-8778","files":{"pdf":{"path":"standards/IETF/RFC-8778/RFC-8778.pdf","sha256":"9d062805882880120bd368311fd1e8212b645c1fb8075819397da49344a8d0f7"},"txt":{"path":"standards/IETF/RFC-8778/RFC-8778.txt","sha256":"2d43646b974c76b9e13565af9b96432ac2b7ba39b66a61820d97f94f3cf1c398"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the Hierarchical\n Signature System (HSS) / Leighton-Micali Signature (LMS) hash-based\n signature algorithm with the CBOR Object Signing and Encryption\n (COSE) syntax. The HSS/LMS algorithm is one form of hash-based\n digital signature; it is described in RFC 8554.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8778.\n\nCopyright Notice\n\n C","scope_keywords":["8778","algorithm","algorithms","authentication","encryption","hash","http","https","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 8778 This document specifies the conventions for using the Hierarchical\n Signature System (HSS) / Leighton-Micali Signature (LMS) hash-based\n signature algorithm with the CBOR Object Signing and Encryption\n (COSE) syntax. The HSS/LMS algorithm is one form of hash-based\n digital signature; it is described in RFC 8554.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8778.\n\nCopyright Notice\n\n C 8778 algorithm algorithms authentication encryption hash http https key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 8791","type":"specification","body":"IETF","designation":"RFC 8791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8791.txt","https://www.rfc-editor.org/rfc/rfc8791.pdf"],"folder":"IETF/RFC-8791","files":{"pdf":{"path":"standards/IETF/RFC-8791/RFC-8791.pdf","sha256":"f645c1999b86329777b9baa17a757a6c09ee360c1a0c45f2ef7a2813818d3b4a"},"txt":{"path":"standards/IETF/RFC-8791/RFC-8791.txt","sha256":"df52a357bd70e1fe0fe4f4544c22c6404ddb37d3f3a70b99ffb6ee29443da7f3"}},"tags":["nested-reference","unchanged"],"summary":"This document describes YANG mechanisms for defining abstract data\n structures with YANG.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8791.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.","scope_keywords":["8791","http","https","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8791 This document describes YANG mechanisms for defining abstract data\n structures with YANG.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8791.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee. 8791 http https key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 8792","type":"specification","body":"IETF","designation":"RFC 8792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8792.txt","https://www.rfc-editor.org/rfc/rfc8792.pdf"],"folder":"IETF/RFC-8792","files":{"pdf":{"path":"standards/IETF/RFC-8792/RFC-8792.pdf","sha256":"3bde85e7499531db14241028ea1df5102e434a4124636f5edd8dd335d26220e4"},"txt":{"path":"standards/IETF/RFC-8792/RFC-8792.txt","sha256":"4f413d97643c3cc96d7d7011469d66a6bbec94a573e125f065356608e892802e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines two strategies for handling long lines in\n width-bounded text content. One strategy, called the \"single\n backslash\" strategy, is based on the historical use of a single\n backslash ('\\') character to indicate where line-folding has\n occurred, with the continuation occurring with the first character\n that is not a space character (' ') on the next line. The second\n strategy, called the \"double backslash\" strategy, extends the first\n strategy by adding a second backslash character to identify where the\n continuation begins and is thereby able to handle cases not supported\n by the first strategy. Both strategies use a self-describing header\n enabling automated reconstitution of the original content.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Inter","scope_keywords":["8792","algorithm","algorithms","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 8792 This document defines two strategies for handling long lines in\n width-bounded text content. One strategy, called the \"single\n backslash\" strategy, is based on the historical use of a single\n backslash ('\\') character to indicate where line-folding has\n occurred, with the continuation occurring with the first character\n that is not a space character (' ') on the next line. The second\n strategy, called the \"double backslash\" strategy, extends the first\n strategy by adding a second backslash character to identify where the\n continuation begins and is thereby able to handle cases not supported\n by the first strategy. Both strategies use a self-describing header\n enabling automated reconstitution of the original content.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Inter 8792 algorithm algorithms http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8826","type":"specification","body":"IETF","designation":"RFC 8826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8826.txt","https://www.rfc-editor.org/rfc/rfc8826.pdf"],"folder":"IETF/RFC-8826","files":{"pdf":{"path":"standards/IETF/RFC-8826/RFC-8826.pdf","sha256":"e3de4b6a70f806dde8994e3d9995f090c7d70a8346a7c35ab3bd66fdc1bb6978"},"txt":{"path":"standards/IETF/RFC-8826/RFC-8826.txt","sha256":"d526463bcb1b1e93283fd55ed34f0f3d90d63f181ca42a934455db3cb847fda9"}},"tags":["nested-reference","unchanged"],"summary":"WebRTC is a protocol suite for use with real-time applications that\n can be deployed in browsers -- \"real-time communication on the Web\".\n This document defines the WebRTC threat model and analyzes the\n security threats of WebRTC in that model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8826.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n docum","scope_keywords":["8826","authentication","http","https","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8826 WebRTC is a protocol suite for use with real-time applications that\n can be deployed in browsers -- \"real-time communication on the Web\".\n This document defines the WebRTC threat model and analyzes the\n security threats of WebRTC in that model.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8826.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n docum 8826 authentication http https key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8827","type":"specification","body":"IETF","designation":"RFC 8827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8827.txt","https://www.rfc-editor.org/rfc/rfc8827.pdf"],"folder":"IETF/RFC-8827","files":{"pdf":{"path":"standards/IETF/RFC-8827/RFC-8827.pdf","sha256":"f5c58c780093d15c1f298f63fcd333804aeac3f6ba8e64891620221b5cae1700"},"txt":{"path":"standards/IETF/RFC-8827/RFC-8827.txt","sha256":"ac905792a914f61fa5ff02c92ec9ff93ac8841bc41c0d4d163a71440f123ec52"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the security architecture for WebRTC, a\n protocol suite intended for use with real-time applications that can\n be deployed in browsers -- \"real-time communication on the Web\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8827.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume","scope_keywords":["8827","attribute","authentication","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8827 This document defines the security architecture for WebRTC, a\n protocol suite intended for use with real-time applications that can\n be deployed in browsers -- \"real-time communication on the Web\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8827.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume 8827 attribute authentication http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8829","type":"specification","body":"IETF","designation":"RFC 8829","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8829.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8829.txt","https://www.rfc-editor.org/rfc/rfc8829.pdf"],"folder":"IETF/RFC-8829","files":{"pdf":{"path":"standards/IETF/RFC-8829/RFC-8829.pdf","sha256":"d7e7e61eb4c2ea3d5d3bea60b42ab291cfc67b8de3cfd7b81c3b68d776cfc69a"},"txt":{"path":"standards/IETF/RFC-8829/RFC-8829.txt","sha256":"00d27c72aabdd38b9e68b7e714ad7b09183ebbfa20fbef6e331ec9869161e587"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the mechanisms for allowing a JavaScript\n application to control the signaling plane of a multimedia session\n via the interface specified in the W3C RTCPeerConnection API and\n discusses how this relates to existing signaling protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8829.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identifie","scope_keywords":["8829","attribute","attributes","http","https","key","license","management","policy","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null}],"search_text":"IETF RFC 8829 This document describes the mechanisms for allowing a JavaScript\n application to control the signaling plane of a multimedia session\n via the interface specified in the W3C RTCPeerConnection API and\n discusses how this relates to existing signaling protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8829.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identifie 8829 attribute attributes http https key license management policy profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8830","type":"specification","body":"IETF","designation":"RFC 8830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8830.txt","https://www.rfc-editor.org/rfc/rfc8830.pdf"],"folder":"IETF/RFC-8830","files":{"pdf":{"path":"standards/IETF/RFC-8830/RFC-8830.pdf","sha256":"c7c1a0733a2b6b022add006b1a6c7e9d0ad736bfbc473a3f6c8dffd71133e045"},"txt":{"path":"standards/IETF/RFC-8830/RFC-8830.txt","sha256":"c6772a31f95e83735ed328669cc11cf42608ef83c6475741827379e048e09d96"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Session Description Protocol (SDP) grouping\n mechanism for RTP media streams that can be used to specify relations\n between media streams.\n\n This mechanism is used to signal the association between the SDP\n concept of \"media description\" and the Web Real-Time Communication\n (WebRTC) concept of MediaStream/MediaStreamTrack using SDP signaling.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https","scope_keywords":["8830","attribute","http","https","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null}],"search_text":"IETF RFC 8830 This document specifies a Session Description Protocol (SDP) grouping\n mechanism for RTP media streams that can be used to specify relations\n between media streams.\n\n This mechanism is used to signal the association between the SDP\n concept of \"media description\" and the Web Real-Time Communication\n (WebRTC) concept of MediaStream/MediaStreamTrack using SDP signaling.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https 8830 attribute http https identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8832","type":"specification","body":"IETF","designation":"RFC 8832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8832.txt","https://www.rfc-editor.org/rfc/rfc8832.pdf"],"folder":"IETF/RFC-8832","files":{"pdf":{"path":"standards/IETF/RFC-8832/RFC-8832.pdf","sha256":"f64ca528fc7b3d1567635aa758f40588c03f899adaa4005412a49111fcc425c7"},"txt":{"path":"standards/IETF/RFC-8832/RFC-8832.txt","sha256":"64f9addf6ff135f37c5ff8ec5b9b905ad882d6288400af144425cac3df507df5"}},"tags":["nested-reference","unchanged"],"summary":"The WebRTC framework specifies protocol support for direct\n interactive rich communication using audio, video, and data between\n two peers' web browsers. This document specifies a simple protocol\n for establishing symmetric data channels between the peers. It uses\n a two-way handshake and allows sending of user data without waiting\n for the handshake to complete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://ww","scope_keywords":["8832","delivery","http","https","key","license","pid","registered","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8831","folder":"IETF/RFC-8831","source":"IETF/RFC-8831/RFC-8831.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null}],"search_text":"IETF RFC 8832 The WebRTC framework specifies protocol support for direct\n interactive rich communication using audio, video, and data between\n two peers' web browsers. This document specifies a simple protocol\n for establishing symmetric data channels between the peers. It uses\n a two-way handshake and allows sending of user data without waiting\n for the handshake to complete.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://ww 8832 delivery http https key license pid registered subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8834","type":"specification","body":"IETF","designation":"RFC 8834","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8834.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8834.txt","https://www.rfc-editor.org/rfc/rfc8834.pdf"],"folder":"IETF/RFC-8834","files":{"pdf":{"path":"standards/IETF/RFC-8834/RFC-8834.pdf","sha256":"894d38a22412f584ebfa23bee743344bcaa0f75fb5fe2c6ffd9694217e651dcd"},"txt":{"path":"standards/IETF/RFC-8834/RFC-8834.txt","sha256":"8bc95ea7e25f350adb265457b4c700357a47285b8d2931654b72db8cbc78b630"}},"tags":["nested-reference","unchanged"],"summary":"The framework for Web Real-Time Communication (WebRTC) provides\n support for direct interactive rich communication using audio, video,\n text, collaboration, games, etc. between two peers' web browsers.\n This memo describes the media transport aspects of the WebRTC\n framework. It specifies how the Real-time Transport Protocol (RTP)\n is used in the WebRTC context and gives requirements for which RTP\n features, profiles, and extensions need to be supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of","scope_keywords":["8834","delivery","http","https","identification","license","management","pid","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null}],"search_text":"IETF RFC 8834 The framework for Web Real-Time Communication (WebRTC) provides\n support for direct interactive rich communication using audio, video,\n text, collaboration, games, etc. between two peers' web browsers.\n This memo describes the media transport aspects of the WebRTC\n framework. It specifies how the Real-time Transport Protocol (RTP)\n is used in the WebRTC context and gives requirements for which RTP\n features, profiles, and extensions need to be supported.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of 8834 delivery http https identification license management pid profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 8839","type":"specification","body":"IETF","designation":"RFC 8839","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8839.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8839.txt","https://www.rfc-editor.org/rfc/rfc8839.pdf"],"folder":"IETF/RFC-8839","files":{"pdf":{"path":"standards/IETF/RFC-8839/RFC-8839.pdf","sha256":"570029c396a2e16306505066dd7e5c37087be51fb868709bf686d30f06d81d2c"},"txt":{"path":"standards/IETF/RFC-8839/RFC-8839.txt","sha256":"8c9c5c2af624bfa0a1f781078cbfa76903a990883b92769442b420151e8ec44e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes Session Description Protocol (SDP) Offer/\n Answer procedures for carrying out Interactive Connectivity\n Establishment (ICE) between the agents.\n\n This document obsoletes RFCs 5245 and 6336.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8839.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserve","scope_keywords":["8839","attribute","attributes","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 8839 This document describes Session Description Protocol (SDP) Offer/\n Answer procedures for carrying out Interactive Connectivity\n Establishment (ICE) between the agents.\n\n This document obsoletes RFCs 5245 and 6336.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8839.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserve 8839 attribute attributes http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8840","type":"specification","body":"IETF","designation":"RFC 8840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8840.txt","https://www.rfc-editor.org/rfc/rfc8840.pdf"],"folder":"IETF/RFC-8840","files":{"pdf":{"path":"standards/IETF/RFC-8840/RFC-8840.pdf","sha256":"a0f7fffbb1171e9fbaeec27cfa6369087780595f36dd3b2265a85747ad142210"},"txt":{"path":"standards/IETF/RFC-8840/RFC-8840.txt","sha256":"14448e9b3917b0abd0f74d0edbef6285454cb7050e1bea0f3d3be5cc3098cba1"}},"tags":["nested-reference","unchanged"],"summary":"The Interactive Connectivity Establishment (ICE) protocol describes a\n Network Address Translator (NAT) traversal mechanism for UDP-based\n multimedia sessions established with the Offer/Answer model. The ICE\n extension for Incremental Provisioning of Candidates (Trickle ICE)\n defines a mechanism that allows ICE Agents to shorten session\n establishment delays by making the candidate gathering and\n connectivity checking phases of ICE non-blocking and by executing\n them in parallel.\n\n This document defines usage semantics for Trickle ICE with the\n Session Initiation Protocol (SIP). The document also defines a new\n SIP Info Package to support this usage together with the\n corresponding media type. Additionally, a new Session Description\n Protocol (SDP) \"end-of-candidates\" attribute and a new SIP option tag\n \"trickle-ice\" are defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track","scope_keywords":["8840","attribute","delivery","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8838","folder":"IETF/RFC-8838","source":"IETF/RFC-8838/RFC-8838.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null}],"search_text":"IETF RFC 8840 The Interactive Connectivity Establishment (ICE) protocol describes a\n Network Address Translator (NAT) traversal mechanism for UDP-based\n multimedia sessions established with the Offer/Answer model. The ICE\n extension for Incremental Provisioning of Candidates (Trickle ICE)\n defines a mechanism that allows ICE Agents to shorten session\n establishment delays by making the candidate gathering and\n connectivity checking phases of ICE non-blocking and by executing\n them in parallel.\n\n This document defines usage semantics for Trickle ICE with the\n Session Initiation Protocol (SIP). The document also defines a new\n SIP Info Package to support this usage together with the\n corresponding media type. Additionally, a new Session Description\n Protocol (SDP) \"end-of-candidates\" attribute and a new SIP option tag\n \"trickle-ice\" are defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track 8840 attribute delivery http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8842","type":"specification","body":"IETF","designation":"RFC 8842","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8842.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8842.txt","https://www.rfc-editor.org/rfc/rfc8842.pdf"],"folder":"IETF/RFC-8842","files":{"pdf":{"path":"standards/IETF/RFC-8842/RFC-8842.pdf","sha256":"af484047eaf162fa1df3239bac8c5b208e991c1e6bc3b60ea42715f84fecc492"},"txt":{"path":"standards/IETF/RFC-8842/RFC-8842.txt","sha256":"e6c6ed44a1fc88a1f326e9af7f81734033d73ba54b26f028703e53a2d078582d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Session Description Protocol (SDP) offer/\n answer procedures for negotiating and establishing a Datagram\n Transport Layer Security (DTLS) association. The document also\n defines the criteria for when a new DTLS association must be\n established. The document updates RFCs 5763 and 7345 by replacing\n common SDP offer/answer procedures with a reference to this\n specification.\n\n This document defines a new SDP media-level attribute, \"tls-id\".\n\n This document also defines how the \"tls-id\" attribute can be used for\n negotiating and establishing a Transport Layer Security (TLS)\n connection, in conjunction with the procedures in RFCs 4145 and 8122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public revie","scope_keywords":["8842","attribute","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null}],"search_text":"IETF RFC 8842 This document defines the Session Description Protocol (SDP) offer/\n answer procedures for negotiating and establishing a Datagram\n Transport Layer Security (DTLS) association. The document also\n defines the criteria for when a new DTLS association must be\n established. The document updates RFCs 5763 and 7345 by replacing\n common SDP offer/answer procedures with a reference to this\n specification.\n\n This document defines a new SDP media-level attribute, \"tls-id\".\n\n This document also defines how the \"tls-id\" attribute can be used for\n negotiating and establishing a Transport Layer Security (TLS)\n connection, in conjunction with the procedures in RFCs 4145 and 8122.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public revie 8842 attribute http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8843","type":"specification","body":"IETF","designation":"RFC 8843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8843.txt","https://www.rfc-editor.org/rfc/rfc8843.pdf"],"folder":"IETF/RFC-8843","files":{"pdf":{"path":"standards/IETF/RFC-8843/RFC-8843.pdf","sha256":"cce08ae49ec9eecad5ff9fb48a3868097ee21170e0bb71c9f3f78ab48148a309"},"txt":{"path":"standards/IETF/RFC-8843/RFC-8843.txt","sha256":"d31e65f96fdd138cd642429aa4ca7c5c947c2ddb255623676c7962b735f0fa99"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a new Session Description Protocol (SDP)\n Grouping Framework extension called 'BUNDLE'. The extension can be\n used with the SDP offer/answer mechanism to negotiate the usage of a\n single transport (5-tuple) for sending and receiving media described\n by multiple SDP media descriptions (\"m=\" sections). Such transport\n is referred to as a BUNDLE transport, and the media is referred to as\n bundled media. The \"m=\" sections that use the BUNDLE transport form\n a BUNDLE group.\n\n This specification defines a new RTP Control Protocol (RTCP) Source\n Description (SDES) item and a new RTP header extension.\n\n This specification updates RFCs 3264, 5888, and 7941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pu","scope_keywords":["8843","attribute","attributes","http","https","identification","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 8843 This specification defines a new Session Description Protocol (SDP)\n Grouping Framework extension called 'BUNDLE'. The extension can be\n used with the SDP offer/answer mechanism to negotiate the usage of a\n single transport (5-tuple) for sending and receiving media described\n by multiple SDP media descriptions (\"m=\" sections). Such transport\n is referred to as a BUNDLE transport, and the media is referred to as\n bundled media. The \"m=\" sections that use the BUNDLE transport form\n a BUNDLE group.\n\n This specification defines a new RTP Control Protocol (RTCP) Source\n Description (SDES) item and a new RTP header extension.\n\n This specification updates RFCs 3264, 5888, and 7941.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received pu 8843 attribute attributes http https identification license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8848","type":"specification","body":"IETF","designation":"RFC 8848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8848.txt","https://www.rfc-editor.org/rfc/rfc8848.pdf"],"folder":"IETF/RFC-8848","files":{"pdf":{"path":"standards/IETF/RFC-8848/RFC-8848.pdf","sha256":"c6ba3ddee3698246918fb6f628ac06f790c93970ca63ea175e742f0aad85a4fe"},"txt":{"path":"standards/IETF/RFC-8848/RFC-8848.txt","sha256":"3fca8f1a11650ff0752b5788e58c8d992c9da5653db06858299bebbd8a378a93"}},"tags":["nested-reference","unchanged"],"summary":"This document is about Controlling Multiple Streams for Telepresence\n (CLUE) signaling. It specifies how the CLUE protocol and the CLUE\n data channel are used in conjunction with each other and with\n existing signaling mechanisms, such as SIP and the Session\n Description Protocol (SDP), to produce a telepresence call.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standa","scope_keywords":["8848","attribute","attributes","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null}],"search_text":"IETF RFC 8848 This document is about Controlling Multiple Streams for Telepresence\n (CLUE) signaling. It specifies how the CLUE protocol and the CLUE\n data channel are used in conjunction with each other and with\n existing signaling mechanisms, such as SIP and the Session\n Description Protocol (SDP), to produce a telepresence call.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standa 8848 attribute attributes http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8850","type":"specification","body":"IETF","designation":"RFC 8850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8850.txt","https://www.rfc-editor.org/rfc/rfc8850.pdf"],"folder":"IETF/RFC-8850","files":{"pdf":{"path":"standards/IETF/RFC-8850/RFC-8850.pdf","sha256":"7eb3133bb57dfed60955205760a951ef50208404c19f22d1e00a1cede247d9c3"},"txt":{"path":"standards/IETF/RFC-8850/RFC-8850.txt","sha256":"84b7133a94149ece3ba5a1bf211126428f2aa16f46b0c50b43e761908d7d15ea"}},"tags":["nested-reference","unchanged"],"summary":"This document defines how to use the WebRTC data channel mechanism to\n realize a data channel, referred to as a Controlling Multiple Streams\n for Telepresence (CLUE) data channel, for transporting CLUE protocol\n messages between two CLUE entities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of","scope_keywords":["8850","attribute","attributes","delivery","http","https","key","license","pid","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null}],"search_text":"IETF RFC 8850 This document defines how to use the WebRTC data channel mechanism to\n realize a data channel, referred to as a Controlling Multiple Streams\n for Telepresence (CLUE) data channel, for transporting CLUE protocol\n messages between two CLUE entities.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents the consensus of the IETF\n community. It has received public review and has been approved for\n publication by the Internet Engineering Steering Group (IESG). Not\n all documents approved by the IESG are candidates for any level of\n Internet Standard; see Section 2 of RFC 7841.\n\n Information about the current status of 8850 attribute attributes delivery http https key license pid policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8851","type":"specification","body":"IETF","designation":"RFC 8851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8851.txt","https://www.rfc-editor.org/rfc/rfc8851.pdf"],"folder":"IETF/RFC-8851","files":{"pdf":{"path":"standards/IETF/RFC-8851/RFC-8851.pdf","sha256":"848c885b9b24060c76ac2486965362640f73f1f99bd673880174672a700bdd4a"},"txt":{"path":"standards/IETF/RFC-8851/RFC-8851.txt","sha256":"1c1283cc28c2fd0f6a71c656b85943afc994e980e83f44bcab948b3208ee9cac"}},"tags":["nested-reference","unchanged"],"summary":"In this specification, we define a framework for specifying\n restrictions on RTP streams in the Session Description Protocol\n (SDP). This framework defines a new \"rid\" (\"restriction identifier\")\n SDP attribute to unambiguously identify the RTP streams within an RTP\n session and restrict the streams' payload format parameters in a\n codec-agnostic way beyond what is provided with the regular payload\n types.\n\n This specification updates RFC 4855 to give additional guidance on\n choice of Format Parameter (fmtp) names and their relation to the\n restrictions defined by this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG","scope_keywords":["8851","attribute","attributes","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 8851 In this specification, we define a framework for specifying\n restrictions on RTP streams in the Session Description Protocol\n (SDP). This framework defines a new \"rid\" (\"restriction identifier\")\n SDP attribute to unambiguously identify the RTP streams within an RTP\n session and restrict the streams' payload format parameters in a\n codec-agnostic way beyond what is provided with the regular payload\n types.\n\n This specification updates RFC 4855 to give additional guidance on\n choice of Format Parameter (fmtp) names and their relation to the\n restrictions defined by this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG 8851 attribute attributes http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8853","type":"specification","body":"IETF","designation":"RFC 8853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8853.txt","https://www.rfc-editor.org/rfc/rfc8853.pdf"],"folder":"IETF/RFC-8853","files":{"pdf":{"path":"standards/IETF/RFC-8853/RFC-8853.pdf","sha256":"176ac37c9ebe029d4ea517a9fb45b07bd48f7e0549a531638c7df31438635c9b"},"txt":{"path":"standards/IETF/RFC-8853/RFC-8853.txt","sha256":"e4ca28a1496e4590768c3052925b7430f6c07a49e7bda4e3c4c35b4270a8c6f2"}},"tags":["nested-reference","unchanged"],"summary":"In some application scenarios, it may be desirable to send multiple\n differently encoded versions of the same media source in different\n RTP streams. This is called simulcast. This document describes how\n to accomplish simulcast in RTP and how to signal it in the Session\n Description Protocol (SDP). The described solution uses an RTP/RTCP\n identification method to identify RTP streams belonging to the same\n media source and makes an extension to SDP to indicate that those RTP\n streams are different simulcast formats of that media source. The\n SDP extension consists of a new media-level SDP attribute that\n expresses capability to send and/or receive simulcast RTP streams.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public","scope_keywords":["8853","attribute","http","https","identification","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null}],"search_text":"IETF RFC 8853 In some application scenarios, it may be desirable to send multiple\n differently encoded versions of the same media source in different\n RTP streams. This is called simulcast. This document describes how\n to accomplish simulcast in RTP and how to signal it in the Session\n Description Protocol (SDP). The described solution uses an RTP/RTCP\n identification method to identify RTP streams belonging to the same\n media source and makes an extension to SDP to indicate that those RTP\n streams are different simulcast formats of that media source. The\n SDP extension consists of a new media-level SDP attribute that\n expresses capability to send and/or receive simulcast RTP streams.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public 8853 attribute http https identification key license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 8854","type":"specification","body":"IETF","designation":"RFC 8854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8854.txt","https://www.rfc-editor.org/rfc/rfc8854.pdf"],"folder":"IETF/RFC-8854","files":{"pdf":{"path":"standards/IETF/RFC-8854/RFC-8854.pdf","sha256":"be392bf7ed0bd0e19aa06b6000df40375e97b7eb3016e8c8e37e29d252ec04ba"},"txt":{"path":"standards/IETF/RFC-8854/RFC-8854.txt","sha256":"fecd67e90c7d11a3c7785ea68b1448cda11df9e122924e76eb3848c75a88d58f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides information and requirements for the use of\n Forward Error Correction (FEC) by WebRTC implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8854.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating ","scope_keywords":["8854","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8854 This document provides information and requirements for the use of\n Forward Error Correction (FEC) by WebRTC implementations.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8854.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating  8854 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8856","type":"specification","body":"IETF","designation":"RFC 8856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8856.txt","https://www.rfc-editor.org/rfc/rfc8856.pdf"],"folder":"IETF/RFC-8856","files":{"pdf":{"path":"standards/IETF/RFC-8856/RFC-8856.pdf","sha256":"51dba29b984c9382d354879cd3a881727d88d535a76d475f2cf905ccb8ef7d43"},"txt":{"path":"standards/IETF/RFC-8856/RFC-8856.txt","sha256":"7ed31e67d5884c5d0313d4a8b82d8ade98fef71689b75be2df70c12598b4a710"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Session Description Protocol (SDP) offer/\n answer procedures for negotiating and establishing Binary Floor\n Control Protocol (BFCP) streams.\n\n This document obsoletes RFC 4583.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8856.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This d","scope_keywords":["8856","attribute","attributes","encryption","http","https","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 8856 This document defines the Session Description Protocol (SDP) offer/\n answer procedures for negotiating and establishing Binary Floor\n Control Protocol (BFCP) streams.\n\n This document obsoletes RFC 4583.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8856.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This d 8856 attribute attributes encryption http https key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8858","type":"specification","body":"IETF","designation":"RFC 8858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8858.txt","https://www.rfc-editor.org/rfc/rfc8858.pdf"],"folder":"IETF/RFC-8858","files":{"pdf":{"path":"standards/IETF/RFC-8858/RFC-8858.pdf","sha256":"df2329c4b84da8966deb3f51fee1b7ef4436ca7c7e2a7af8656bd65d640bf6f2"},"txt":{"path":"standards/IETF/RFC-8858/RFC-8858.txt","sha256":"fa7fb916c318171fb985fea007fe8d3cd9e430de1cdc92b8f335e557edcd6847"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Session Description Protocol (SDP) media-\n level attribute, 'rtcp-mux-only', that can be used by an endpoint to\n indicate exclusive support of RTP and RTP Control Protocol (RTCP)\n multiplexing. The document also updates RFC 5761 by clarifying that\n an offerer can use a mechanism to indicate that it is not able to\n send and receive RTCP on separate ports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta","scope_keywords":["8858","attribute","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null}],"search_text":"IETF RFC 8858 This document defines a new Session Description Protocol (SDP) media-\n level attribute, 'rtcp-mux-only', that can be used by an endpoint to\n indicate exclusive support of RTP and RTP Control Protocol (RTCP)\n multiplexing. The document also updates RFC 5761 by clarifying that\n an offerer can use a mechanism to indicate that it is not able to\n send and receive RTCP on separate ports.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obta 8858 attribute http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8859","type":"specification","body":"IETF","designation":"RFC 8859","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8859.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8859.txt","https://www.rfc-editor.org/rfc/rfc8859.pdf"],"folder":"IETF/RFC-8859","files":{"pdf":{"path":"standards/IETF/RFC-8859/RFC-8859.pdf","sha256":"e1428e1e39b58bc54aec057b6ae6cde7784f5ebdd31428ba7902d575fd6871f5"},"txt":{"path":"standards/IETF/RFC-8859/RFC-8859.txt","sha256":"f8f1e4e336dac6d4d3e7f3236c0fbd94a8e5424bed6bd2ec702b683847a87582"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this specification is to provide a framework for\n analyzing the multiplexing characteristics of Session Description\n Protocol (SDP) attributes when SDP is used to negotiate the usage of\n a single 5-tuple for sending and receiving media associated with\n multiple media descriptions.\n\n This specification also categorizes the existing SDP attributes based\n on the framework described herein.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedba","scope_keywords":["8859","attribute","attributes","http","https","key","license","management","pid","profile","subject","timestamp","tls","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8858","folder":"IETF/RFC-8858","source":"IETF/RFC-8858/RFC-8858.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 8859 The purpose of this specification is to provide a framework for\n analyzing the multiplexing characteristics of Session Description\n Protocol (SDP) attributes when SDP is used to negotiate the usage of\n a single 5-tuple for sending and receiving media associated with\n multiple media descriptions.\n\n This specification also categorizes the existing SDP attributes based\n on the framework described herein.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedba 8859 attribute attributes http https key license management pid profile subject timestamp tls trust tsp nested-reference unchanged"},{"id":"IETF RFC 8863","type":"specification","body":"IETF","designation":"RFC 8863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8863.txt","https://www.rfc-editor.org/rfc/rfc8863.pdf"],"folder":"IETF/RFC-8863","files":{"pdf":{"path":"standards/IETF/RFC-8863/RFC-8863.pdf","sha256":"c1cc236b230a839555e56733063d3fa1ecfe7d3a1254c5610c12881dccb886b7"},"txt":{"path":"standards/IETF/RFC-8863/RFC-8863.txt","sha256":"5171bc7689aaf1873c60abd42ccb2baec3c0a306e9cdd0c51f28656e413c8d72"}},"tags":["nested-reference","unchanged"],"summary":"During the process of establishing peer-to-peer connectivity,\n Interactive Connectivity Establishment (ICE) agents can encounter\n situations where they have no candidate pairs to check, and, as a\n result, conclude that ICE processing has failed. However, because\n additional candidate pairs can be discovered during ICE processing,\n declaring failure at this point may be premature. This document\n discusses when these situations can occur.\n\n This document updates RFCs 8445 and 8838 by requiring that an ICE\n agent wait a minimum amount of time before declaring ICE failure,\n even if there are no candidate pairs left to check.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th","scope_keywords":["8863","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null}],"search_text":"IETF RFC 8863 During the process of establishing peer-to-peer connectivity,\n Interactive Connectivity Establishment (ICE) agents can encounter\n situations where they have no candidate pairs to check, and, as a\n result, conclude that ICE processing has failed. However, because\n additional candidate pairs can be discovered during ICE processing,\n declaring failure at this point may be premature. This document\n discusses when these situations can occur.\n\n This document updates RFCs 8445 and 8838 by requiring that an ICE\n agent wait a minimum amount of time before declaring ICE failure,\n even if there are no candidate pairs left to check.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by th 8863 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8864","type":"specification","body":"IETF","designation":"RFC 8864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8864.txt","https://www.rfc-editor.org/rfc/rfc8864.pdf"],"folder":"IETF/RFC-8864","files":{"pdf":{"path":"standards/IETF/RFC-8864/RFC-8864.pdf","sha256":"934c7a270162801e1c0dce275450769dc66fe1b179d0edc5ed84768e5f55d4a2"},"txt":{"path":"standards/IETF/RFC-8864/RFC-8864.txt","sha256":"b2fc615e8fb5b5032a25d940828b9f37c9f257f49a71c83f175293f783273d5b"}},"tags":["nested-reference","unchanged"],"summary":"Data channel setup can be done using either the in-band Data Channel\n Establishment Protocol (DCEP) or some out-of-band non-DCEP protocol.\n This document specifies how the SDP (Session Description Protocol)\n offer/answer exchange can be used to achieve an out-of-band non-DCEP\n negotiation for establishing a data channel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8864.\n\nCopyright N","scope_keywords":["8864","attribute","attributes","delivery","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null},{"body":"IETF","designation":"RFC 8850","folder":"IETF/RFC-8850","source":"IETF/RFC-8850/RFC-8850.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 8864 Data channel setup can be done using either the in-band Data Channel\n Establishment Protocol (DCEP) or some out-of-band non-DCEP protocol.\n This document specifies how the SDP (Session Description Protocol)\n offer/answer exchange can be used to achieve an out-of-band non-DCEP\n negotiation for establishing a data channel.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8864.\n\nCopyright N 8864 attribute attributes delivery http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8873","type":"specification","body":"IETF","designation":"RFC 8873","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8873.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8873.txt","https://www.rfc-editor.org/rfc/rfc8873.pdf"],"folder":"IETF/RFC-8873","files":{"pdf":{"path":"standards/IETF/RFC-8873/RFC-8873.pdf","sha256":"271e2f1eb1d3c7db40bfeac41dc2781622b18a0c3aa737d7a84a42aaa184d3cc"},"txt":{"path":"standards/IETF/RFC-8873/RFC-8873.txt","sha256":"ee652c5af978e0c62aaeda55183c1c65320aa1ab77ece3c64ba627d9cfb525a5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how a Web Real-Time Communication (WebRTC)\n data channel can be used as a transport mechanism for the Message\n Session Relay Protocol (MSRP) and how the Session Description\n Protocol (SDP) offer/answer mechanism can be used to negotiate such a\n data channel, referred to as an MSRP data channel. Two network\n configurations are supported: the connection of two MSRP data channel\n endpoints; and a gateway configuration, which connects an MSRP data\n channel endpoint with an MSRP endpoint that uses either TCP or TLS.\n This document updates RFC 4975.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further ","scope_keywords":["8873","attribute","attributes","http","https","key","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null}],"search_text":"IETF RFC 8873 This document specifies how a Web Real-Time Communication (WebRTC)\n data channel can be used as a transport mechanism for the Message\n Session Relay Protocol (MSRP) and how the Session Description\n Protocol (SDP) offer/answer mechanism can be used to negotiate such a\n data channel, referred to as an MSRP data channel. Two network\n configurations are supported: the connection of two MSRP data channel\n endpoints; and a gateway configuration, which connects an MSRP data\n channel endpoint with an MSRP endpoint that uses either TCP or TLS.\n This document updates RFC 4975.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further  8873 attribute attributes http https key license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8914","type":"specification","body":"IETF","designation":"RFC 8914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8914.txt","https://www.rfc-editor.org/rfc/rfc8914.pdf"],"folder":"IETF/RFC-8914","files":{"pdf":{"path":"standards/IETF/RFC-8914/RFC-8914.pdf","sha256":"ba3dace0e3360b252e66c3b7de465502d74a316ff81876b4c0677f8f424a1eaf"},"txt":{"path":"standards/IETF/RFC-8914/RFC-8914.txt","sha256":"5a04480b6db25618bd600672d86a0ab0a1ed431567bdae7802b04cd1fb0fe3bb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extensible method to return additional\n information about the cause of DNS errors. Though created primarily\n to extend SERVFAIL to provide additional information about the cause\n of DNS and DNSSEC failures, the Extended DNS Errors option defined in\n this document allows all response types to contain extended error\n information. Extended DNS Error information does not change the\n processing of RCODEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n a","scope_keywords":["8914","algorithm","http","https","key","license","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9209","folder":"IETF/RFC-9209","source":"IETF/RFC-9209/RFC-9209.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 8914 This document defines an extensible method to return additional\n information about the cause of DNS errors. Though created primarily\n to extend SERVFAIL to provide additional information about the cause\n of DNS and DNSSEC failures, the Extended DNS Errors option defined in\n this document allows all response types to contain extended error\n information. Extended DNS Error information does not change the\n processing of RCODEs.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n a 8914 algorithm http https key license signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 8932","type":"specification","body":"IETF","designation":"RFC 8932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8932.txt","https://www.rfc-editor.org/rfc/rfc8932.pdf"],"folder":"IETF/RFC-8932","files":{"pdf":{"path":"standards/IETF/RFC-8932/RFC-8932.pdf","sha256":"c1805b6cb506e9a875083245a3fe6ab3c58a8257ad81af74c2623155b1d80787"},"txt":{"path":"standards/IETF/RFC-8932/RFC-8932.txt","sha256":"77f0b044eee01708ba851095a219ba0e39049dc293537d77154667a90b4d7530"}},"tags":["nested-reference","unchanged"],"summary":"This document presents operational, policy, and security\n considerations for DNS recursive resolver operators who choose to\n offer DNS privacy services. With these recommendations, the operator\n can make deliberate decisions regarding which services to provide, as\n well as understanding how those decisions and the alternatives impact\n the privacy of users.\n\n This document also presents a non-normative framework to assist\n writers of a Recursive operator Privacy Statement, analogous to DNS\n Security Extensions (DNSSEC) Policies and DNSSEC Practice Statements\n described in RFC 6841.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering","scope_keywords":["8932","authentication","encryption","hash","http","https","license","policies","policy","risk","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null}],"search_text":"IETF RFC 8932 This document presents operational, policy, and security\n considerations for DNS recursive resolver operators who choose to\n offer DNS privacy services. With these recommendations, the operator\n can make deliberate decisions regarding which services to provide, as\n well as understanding how those decisions and the alternatives impact\n the privacy of users.\n\n This document also presents a non-normative framework to assist\n writers of a Recursive operator Privacy Statement, analogous to DNS\n Security Extensions (DNSSEC) Policies and DNSSEC Practice Statements\n described in RFC 6841.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering 8932 authentication encryption hash http https license policies policy risk subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8973","type":"specification","body":"IETF","designation":"RFC 8973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8973.txt","https://www.rfc-editor.org/rfc/rfc8973.pdf"],"folder":"IETF/RFC-8973","files":{"pdf":{"path":"standards/IETF/RFC-8973/RFC-8973.pdf","sha256":"3d65f0f628c179e8da9a5929e3cfced44fabf4e9d753868c9b6a9b4747ca301c"},"txt":{"path":"standards/IETF/RFC-8973/RFC-8973.txt","sha256":"7eafcb25154ccf34b998767e5ed195571f8ed11a17aa0609ac387fcc69db2842"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies mechanisms to configure DDoS Open Threat\n Signaling (DOTS) clients with their DOTS servers. The discovery\n procedure also covers the DOTS signal channel Call Home. It can be\n useful to know the appropriate DOTS server for a given location in\n order to engage mitigation actions. This is true even in cases where\n the DOTS client cannot localize the attack: cases where it only knows\n that some resources are under attack and that help is needed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the curren","scope_keywords":["8973","authentication","credential","credentials","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8973 This document specifies mechanisms to configure DDoS Open Threat\n Signaling (DOTS) clients with their DOTS servers. The discovery\n procedure also covers the DOTS signal channel Call Home. It can be\n useful to know the appropriate DOTS server for a given location in\n order to engage mitigation actions. This is true even in cases where\n the DOTS client cannot localize the attack: cases where it only knows\n that some resources are under attack and that help is needed.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the curren 8973 authentication credential credentials http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8974","type":"specification","body":"IETF","designation":"RFC 8974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8974.txt","https://www.rfc-editor.org/rfc/rfc8974.pdf"],"folder":"IETF/RFC-8974","files":{"pdf":{"path":"standards/IETF/RFC-8974/RFC-8974.pdf","sha256":"22a88d3719c1e37685771946b184337461edd668b5081321ff609c675654f0c6"},"txt":{"path":"standards/IETF/RFC-8974/RFC-8974.txt","sha256":"1c70f3ceb9af34688284da9db592a28f89b745c43b0ac2702dc6787901bb347b"}},"tags":["nested-reference","unchanged"],"summary":"This document provides considerations for alleviating Constrained\n Application Protocol (CoAP) clients and intermediaries of keeping\n per-request state. To facilitate this, this document additionally\n introduces a new, optional CoAP protocol extension for extended token\n lengths.\n\n This document updates RFCs 7252 and 8323 with an extended definition\n of the \"TKL\" field in the CoAP message header.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on","scope_keywords":["8974","http","https","identification","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9175","folder":"IETF/RFC-9175","source":"IETF/RFC-9175/RFC-9175.txt","version":null},{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 8974 This document provides considerations for alleviating Constrained\n Application Protocol (CoAP) clients and intermediaries of keeping\n per-request state. To facilitate this, this document additionally\n introduces a new, optional CoAP protocol extension for extended token\n lengths.\n\n This document updates RFCs 7252 and 8323 with an extended definition\n of the \"TKL\" field in the CoAP message header.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on 8974 http https identification key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8996","type":"specification","body":"IETF","designation":"RFC 8996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8996.txt","https://www.rfc-editor.org/rfc/rfc8996.pdf"],"folder":"IETF/RFC-8996","files":{"pdf":{"path":"standards/IETF/RFC-8996/RFC-8996.pdf","sha256":"73f2c59331877733e9b533332b7a1b1958d132247183f6cd7d9ab829c83a30eb"},"txt":{"path":"standards/IETF/RFC-8996/RFC-8996.txt","sha256":"a8250792df7fc533328f2021dbdcce847bbdfbc703de89a93e18ce165d4b8d14"}},"tags":["nested-reference","unchanged"],"summary":"This document formally deprecates Transport Layer Security (TLS)\n versions 1.0 (RFC 2246) and 1.1 (RFC 4346). Accordingly, those\n documents have been moved to Historic status. These versions lack\n support for current and recommended cryptographic algorithms and\n mechanisms, and various government and industry profiles of\n applications using TLS now mandate avoiding these old TLS versions.\n TLS version 1.2 became the recommended version for IETF protocols in\n 2008 (subsequently being obsoleted by TLS version 1.3 in 2018),\n providing sufficient time to transition away from older versions.\n Removing support for older versions from implementations reduces the\n attack surface, reduces opportunity for misconfiguration, and\n streamlines library and product maintenance.\n\n This document also deprecates Datagram TLS (DTLS) version 1.0 (RFC\n 4347) but not DTLS version 1.2, and there is no DTLS vers","scope_keywords":["8996","algorithm","algorithms","authentication","encryption","hash","http","https","license","profile","profiles","signature","signatures","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9250","folder":"IETF/RFC-9250","source":"IETF/RFC-9250/RFC-9250.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 8996 This document formally deprecates Transport Layer Security (TLS)\n versions 1.0 (RFC 2246) and 1.1 (RFC 4346). Accordingly, those\n documents have been moved to Historic status. These versions lack\n support for current and recommended cryptographic algorithms and\n mechanisms, and various government and industry profiles of\n applications using TLS now mandate avoiding these old TLS versions.\n TLS version 1.2 became the recommended version for IETF protocols in\n 2008 (subsequently being obsoleted by TLS version 1.3 in 2018),\n providing sufficient time to transition away from older versions.\n Removing support for older versions from implementations reduces the\n attack surface, reduces opportunity for misconfiguration, and\n streamlines library and product maintenance.\n\n This document also deprecates Datagram TLS (DTLS) version 1.0 (RFC\n 4347) but not DTLS version 1.2, and there is no DTLS vers 8996 algorithm algorithms authentication encryption hash http https license profile profiles signature signatures subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8999","type":"specification","body":"IETF","designation":"RFC 8999","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8999.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8999.txt","https://www.rfc-editor.org/rfc/rfc8999.pdf"],"folder":"IETF/RFC-8999","files":{"pdf":{"path":"standards/IETF/RFC-8999/RFC-8999.pdf","sha256":"0175769deed0454b5141e4555b3cddbd8a7174e5ff1234fb165851642d1affce"},"txt":{"path":"standards/IETF/RFC-8999/RFC-8999.txt","sha256":"9c266f21fdea0cb3d99c9741672fd21153f04669fc73d8ea3a3488484ce38c88"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the properties of the QUIC transport protocol\n that are common to all versions of the protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8999.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF ","scope_keywords":["8999","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null}],"search_text":"IETF RFC 8999 This document defines the properties of the QUIC transport protocol\n that are common to all versions of the protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8999.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF  8999 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9021","type":"specification","body":"IETF","designation":"RFC 9021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9021.txt","https://www.rfc-editor.org/rfc/rfc9021.pdf"],"folder":"IETF/RFC-9021","files":{"pdf":{"path":"standards/IETF/RFC-9021/RFC-9021.pdf","sha256":"4c36aa90a05c9270db753fc99452c4b37173576e6308321b86a390999aa85c48"},"txt":{"path":"standards/IETF/RFC-9021/RFC-9021.txt","sha256":"177b3ea486296b0866d8d46ad3a9b2de1a8360e36355ad9110c474de6b9669c6"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the conventions for using the Walnut Digital\n Signature Algorithm (WalnutDSA) for digital signatures with the CBOR\n Object Signing and Encryption (COSE) syntax. WalnutDSA is a\n lightweight, quantum-resistant signature scheme based on Group\n Theoretic Cryptography with implementation and computational\n efficiency of signature verification in constrained environments,\n even on 8- and 16-bit platforms.\n\n The goal of this publication is to document a way to use the\n lightweight, quantum-resistant WalnutDSA signature algorithm in COSE\n in a way that would allow multiple developers to build compatible\n implementations. As of this publication, the security properties of\n WalnutDSA have not been evaluated by the IETF and its use has not\n been endorsed by the IETF.\n\n WalnutDSA and the Walnut Digital Signature Algorithm are trademarks\n of Veridify Security Inc.\n\nStatus of T","scope_keywords":["9021","algorithm","algorithms","encryption","hash","http","https","key","keys","license","risk","signature","signatures","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 9021 This document specifies the conventions for using the Walnut Digital\n Signature Algorithm (WalnutDSA) for digital signatures with the CBOR\n Object Signing and Encryption (COSE) syntax. WalnutDSA is a\n lightweight, quantum-resistant signature scheme based on Group\n Theoretic Cryptography with implementation and computational\n efficiency of signature verification in constrained environments,\n even on 8- and 16-bit platforms.\n\n The goal of this publication is to document a way to use the\n lightweight, quantum-resistant WalnutDSA signature algorithm in COSE\n in a way that would allow multiple developers to build compatible\n implementations. As of this publication, the security properties of\n WalnutDSA have not been evaluated by the IETF and its use has not\n been endorsed by the IETF.\n\n WalnutDSA and the Walnut Digital Signature Algorithm are trademarks\n of Veridify Security Inc.\n\nStatus of T 9021 algorithm algorithms encryption hash http https key keys license risk signature signatures subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 9039","type":"specification","body":"IETF","designation":"RFC 9039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9039.txt","https://www.rfc-editor.org/rfc/rfc9039.pdf"],"folder":"IETF/RFC-9039","files":{"pdf":{"path":"standards/IETF/RFC-9039/RFC-9039.pdf","sha256":"c9cd7a7366940c059d631438ebcab259894411af21ef2fb2e2a24e4dc3e8abaa"},"txt":{"path":"standards/IETF/RFC-9039/RFC-9039.txt","sha256":"f7eb43073bff1baa5c8f3b8f51f49424a0caf27b7b4db9f6da7acab3bde9091a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new Uniform Resource Name (URN) namespace\n for hardware device identifiers. A general representation of device\n identity can be useful in many applications, such as in sensor data\n streams and storage or in equipment inventories. A URN-based\n representation can be passed along in applications that need the\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/i","scope_keywords":["9039","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 9039 This document describes a new Uniform Resource Name (URN) namespace\n for hardware device identifiers. A general representation of device\n identity can be useful in many applications, such as in sensor data\n streams and storage or in equipment inventories. A URN-based\n representation can be passed along in applications that need the\n information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/i 9039 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 9052","type":"specification","body":"IETF","designation":"RFC 9052","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9052.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9052.txt","https://www.rfc-editor.org/rfc/rfc9052.pdf"],"folder":"IETF/RFC-9052","files":{"pdf":{"path":"standards/IETF/RFC-9052/RFC-9052.pdf","sha256":"551a082e8f5b1f1347f0627738c37115fda4f9feabba05ffaf7a62fd265eade3"},"txt":{"path":"standards/IETF/RFC-9052/RFC-9052.txt","sha256":"01eecd7f646537600e7aad665b1fa581ce6ec33dae4ef4add0997aaf38cd0a45"}},"tags":["nested-reference","unchanged"],"summary":"Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need to be\n able to define basic security services for this data format. This\n document defines the CBOR Object Signing and Encryption (COSE)\n protocol. This specification describes how to create and process\n signatures, message authentication codes, and encryption using CBOR\n for serialization. This specification additionally describes how to\n represent cryptographic keys using CBOR.\n\n This document, along with RFC 9053, obsoletes RFC 8152.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further in","scope_keywords":["9052","algorithm","algorithms","attribute","attributes","authentication","encryption","http","https","key","keys","license","presentation","signature","signatures","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9338","folder":"IETF/RFC-9338","source":"IETF/RFC-9338/RFC-9338.txt","version":null},{"body":"IETF","designation":"RFC 9360","folder":"IETF/RFC-9360","source":"IETF/RFC-9360/RFC-9360.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9052 Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. There is a need to be\n able to define basic security services for this data format. This\n document defines the CBOR Object Signing and Encryption (COSE)\n protocol. This specification describes how to create and process\n signatures, message authentication codes, and encryption using CBOR\n for serialization. This specification additionally describes how to\n represent cryptographic keys using CBOR.\n\n This document, along with RFC 9053, obsoletes RFC 8152.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further in 9052 algorithm algorithms attribute attributes authentication encryption http https key keys license presentation signature signatures subject nested-reference unchanged"},{"id":"IETF RFC 9054","type":"specification","body":"IETF","designation":"RFC 9054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9054.txt","https://www.rfc-editor.org/rfc/rfc9054.pdf"],"folder":"IETF/RFC-9054","files":{"pdf":{"path":"standards/IETF/RFC-9054/RFC-9054.pdf","sha256":"de576dbde17d5898daede4d6e697b990adbf8bc851777407703c025ddcc6e3c6"},"txt":{"path":"standards/IETF/RFC-9054/RFC-9054.txt","sha256":"75a6bf62b4226baa1e14ccdcc4c603b8a039084ad79677db029e0bbec4525e6f"}},"tags":["nested-reference","unchanged"],"summary":"The CBOR Object Signing and Encryption (COSE) syntax (see RFC 9052)\n does not define any direct methods for using hash algorithms. There\n are, however, circumstances where hash algorithms are used, such as\n indirect signatures, where the hash of one or more contents are\n signed, and identification of an X.509 certificate or other object by\n the use of a fingerprint. This document defines hash algorithms that\n are identified by COSE algorithm identifiers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for a","scope_keywords":["9054","algorithm","algorithms","certificate","certificates","encryption","hash","http","https","identification","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null}],"search_text":"IETF RFC 9054 The CBOR Object Signing and Encryption (COSE) syntax (see RFC 9052)\n does not define any direct methods for using hash algorithms. There\n are, however, circumstances where hash algorithms are used, such as\n indirect signatures, where the hash of one or more contents are\n signed, and identification of an X.509 certificate or other object by\n the use of a fingerprint. This document defines hash algorithms that\n are identified by COSE algorithm identifiers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for a 9054 algorithm algorithms certificate certificates encryption hash http https identification key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 9083","type":"specification","body":"IETF","designation":"RFC 9083","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9083.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9083.txt","https://www.rfc-editor.org/rfc/rfc9083.pdf"],"folder":"IETF/RFC-9083","files":{"pdf":{"path":"standards/IETF/RFC-9083/RFC-9083.pdf","sha256":"54f90f5016a6d193f7067f24c96173af241cb0726502ccb8aac50bd7bfac5282"},"txt":{"path":"standards/IETF/RFC-9083/RFC-9083.txt","sha256":"a21092594836495e1f37bcf6d383bf8aa2a9ad29e2efd7852a73a92915b79eb9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes JSON data structures representing\n registration information maintained by Regional Internet Registries\n (RIRs) and Domain Name Registries (DNRs). These data structures are\n used to form Registration Data Access Protocol (RDAP) query\n responses. This document obsoletes RFC 7483.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9083.\n\nCopyright Notice\n\n Copyright (c","scope_keywords":["9083","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9083 This document describes JSON data structures representing\n registration information maintained by Regional Internet Registries\n (RIRs) and Domain Name Registries (DNRs). These data structures are\n used to form Registration Data Access Protocol (RDAP) query\n responses. This document obsoletes RFC 7483.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9083.\n\nCopyright Notice\n\n Copyright (c 9083 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9090","type":"specification","body":"IETF","designation":"RFC 9090","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9090.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9090.txt","https://www.rfc-editor.org/rfc/rfc9090.pdf"],"folder":"IETF/RFC-9090","files":{"pdf":{"path":"standards/IETF/RFC-9090/RFC-9090.pdf","sha256":"4aaa9b2722b6237b39a0edc9803c02633db5d7ffeb738cdf17a5325544cba441"},"txt":{"path":"standards/IETF/RFC-9090/RFC-9090.txt","sha256":"16e606aa7e7d0d1f019cb67c95ece5f5e4dbada5585b5251860958c80e31cb89"}},"tags":["nested-reference","unchanged"],"summary":"The Concise Binary Object Representation (CBOR), defined in RFC 8949,\n is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n This document defines CBOR tags for object identifiers (OIDs) and is\n the reference document for the IANA registration of the CBOR tags so\n defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o","scope_keywords":["9090","http","https","key","keys","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 9090 The Concise Binary Object Representation (CBOR), defined in RFC 8949,\n is a data format whose design goals include the possibility of\n extremely small code size, fairly small message size, and\n extensibility without the need for version negotiation.\n\n This document defines CBOR tags for object identifiers (OIDs) and is\n the reference document for the IANA registration of the CBOR tags so\n defined.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o 9090 http https key keys license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 9106","type":"specification","body":"IETF","designation":"RFC 9106","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9106.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9106.txt","https://www.rfc-editor.org/rfc/rfc9106.pdf"],"folder":"IETF/RFC-9106","files":{"pdf":{"path":"standards/IETF/RFC-9106/RFC-9106.pdf","sha256":"b88ac945c998b566981276edbd3b18cb5e0347f4e311b16cc8892cb84f6c3ea4"},"txt":{"path":"standards/IETF/RFC-9106/RFC-9106.txt","sha256":"855c06f060379e34285e83a217e9069b5c72e161a1e54df9af5cd88dbb231f31"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Argon2 memory-hard function for password\n hashing and proof-of-work applications. We provide an implementer-\n oriented description with test vectors. The purpose is to simplify\n adoption of Argon2 for Internet protocols. This document is a\n product of the Crypto Forum Research Group (CFRG) in the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; se","scope_keywords":["9106","algorithm","hash","hashing","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9380","folder":"IETF/RFC-9380","source":"IETF/RFC-9380/RFC-9380.txt","version":null}],"search_text":"IETF RFC 9106 This document describes the Argon2 memory-hard function for password\n hashing and proof-of-work applications. We provide an implementer-\n oriented description with test vectors. The purpose is to simplify\n adoption of Argon2 for Internet protocols. This document is a\n product of the Crypto Forum Research Group (CFRG) in the IRTF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Research Task Force\n (IRTF). The IRTF publishes the results of Internet-related research\n and development activities. These results might not be suitable for\n deployment. This RFC represents the consensus of the Crypto Forum\n Research Group of the Internet Research Task Force (IRTF). Documents\n approved for publication by the IRSG are not candidates for any level\n of Internet Standard; se 9106 algorithm hash hashing http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9111","type":"specification","body":"IETF","designation":"RFC 9111","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9111.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9111.txt","https://www.rfc-editor.org/rfc/rfc9111.pdf"],"folder":"IETF/RFC-9111","files":{"pdf":{"path":"standards/IETF/RFC-9111/RFC-9111.pdf","sha256":"2663227a94ec8a81892a02f5697fc15c578571cdee96407adb5c60a60236c76f"},"txt":{"path":"standards/IETF/RFC-9111/RFC-9111.txt","sha256":"aeb52adb3279d5f23dae34f68af11bd5cef0a0aff7ffcd014c9ca93c5302cf3e"}},"tags":["nested-reference","unchanged"],"summary":"The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP caches and the associated header\n fields that control cache behavior or indicate cacheable response\n messages.\n\n This document obsoletes RFC 7234.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9111.\n\nCopyright Not","scope_keywords":["9111","http","https","key","keys","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null},{"body":"IETF","designation":"RFC 9218","folder":"IETF/RFC-9218","source":"IETF/RFC-9218/RFC-9218.txt","version":null},{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9111 The Hypertext Transfer Protocol (HTTP) is a stateless application-\n level protocol for distributed, collaborative, hypertext information\n systems. This document defines HTTP caches and the associated header\n fields that control cache behavior or indicate cacheable response\n messages.\n\n This document obsoletes RFC 7234.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9111.\n\nCopyright Not 9111 http https key keys license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 9126","type":"specification","body":"IETF","designation":"RFC 9126","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9126.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9126.txt","https://www.rfc-editor.org/rfc/rfc9126.pdf"],"folder":"IETF/RFC-9126","files":{"pdf":{"path":"standards/IETF/RFC-9126/RFC-9126.pdf","sha256":"3bb701aa98120a9097bef7f3f6d6265f7685b2324a779f674dfd314e5d388881"},"txt":{"path":"standards/IETF/RFC-9126/RFC-9126.txt","sha256":"a79d0e30fcc24a22b79c8e18aa82362f6e63a7b8a5d58b480e746360e97388db"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the pushed authorization request (PAR)\n endpoint, which allows clients to push the payload of an OAuth 2.0\n authorization request to the authorization server via a direct\n request and provides them with a request URI that is used as\n reference to the data in a subsequent call to the authorization\n endpoint.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9126.\n\nCop","scope_keywords":["9126","authorization","http","https","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 9396","folder":"IETF/RFC-9396","source":"IETF/RFC-9396/RFC-9396.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 9126 This document defines the pushed authorization request (PAR)\n endpoint, which allows clients to push the payload of an OAuth 2.0\n authorization request to the authorization server via a direct\n request and provides them with a request URI that is used as\n reference to the data in a subsequent call to the authorization\n endpoint.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9126.\n\nCop 9126 authorization http https license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 9146","type":"specification","body":"IETF","designation":"RFC 9146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9146.txt","https://www.rfc-editor.org/rfc/rfc9146.pdf"],"folder":"IETF/RFC-9146","files":{"pdf":{"path":"standards/IETF/RFC-9146/RFC-9146.pdf","sha256":"8a7f9f645487a5812460a9a4286fd1fbafd5d82a18e8664f119c5784b7977075"},"txt":{"path":"standards/IETF/RFC-9146/RFC-9146.txt","sha256":"b6a4a2ace20ceefb4c8c6c2433b21fb39bc4d7279f52030d960f981a29aac1be"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the Connection ID (CID) construct for the\n Datagram Transport Layer Security (DTLS) protocol version 1.2.\n\n A CID is an identifier carried in the record layer header that gives\n the recipient additional information for selecting the appropriate\n security association. In \"classical\" DTLS, selecting a security\n association of an incoming DTLS record is accomplished with the help\n of the 5-tuple. If the source IP address and/or source port changes\n during the lifetime of an ongoing DTLS session, then the receiver\n will be unable to locate the correct security context.\n\n The new ciphertext record format with the CID also provides content\n type encryption and record layer padding.\n\n This document updates RFC 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen","scope_keywords":["9146","authentication","encryption","http","https","key","keys","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null}],"search_text":"IETF RFC 9146 This document specifies the Connection ID (CID) construct for the\n Datagram Transport Layer Security (DTLS) protocol version 1.2.\n\n A CID is an identifier carried in the record layer header that gives\n the recipient additional information for selecting the appropriate\n security association. In \"classical\" DTLS, selecting a security\n association of an incoming DTLS record is accomplished with the help\n of the 5-tuple. If the source IP address and/or source port changes\n during the lifetime of an ongoing DTLS session, then the receiver\n will be unable to locate the correct security context.\n\n The new ciphertext record format with the CID also provides content\n type encryption and record layer padding.\n\n This document updates RFC 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represen 9146 authentication encryption http https key keys license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9155","type":"specification","body":"IETF","designation":"RFC 9155","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9155.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9155.txt","https://www.rfc-editor.org/rfc/rfc9155.pdf"],"folder":"IETF/RFC-9155","files":{"pdf":{"path":"standards/IETF/RFC-9155/RFC-9155.pdf","sha256":"c9ac9494ae5dadb57c947eba8d3577e6854512b81954cc81650b6c35aba028f4"},"txt":{"path":"standards/IETF/RFC-9155/RFC-9155.txt","sha256":"87c859e927ab6bbf245f4f3cd909852b28c5d253e2305cbdd715e93aa79db7d2"}},"tags":["nested-reference","unchanged"],"summary":"The MD5 and SHA-1 hashing algorithms are increasingly vulnerable to\n attack, and this document deprecates their use in TLS 1.2 and DTLS\n 1.2 digital signatures. However, this document does not deprecate\n SHA-1 with Hashed Message Authentication Code (HMAC), as used in\n record protection. This document updates RFC 5246.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9155.\n\nCopyright Not","scope_keywords":["9155","algorithm","algorithms","authentication","certificate","hash","hashing","http","https","key","license","signature","signatures","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 9155 The MD5 and SHA-1 hashing algorithms are increasingly vulnerable to\n attack, and this document deprecates their use in TLS 1.2 and DTLS\n 1.2 digital signatures. However, this document does not deprecate\n SHA-1 with Hashed Message Authentication Code (HMAC), as used in\n record protection. This document updates RFC 5246.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9155.\n\nCopyright Not 9155 algorithm algorithms authentication certificate hash hashing http https key license signature signatures subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9165","type":"specification","body":"IETF","designation":"RFC 9165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9165.txt","https://www.rfc-editor.org/rfc/rfc9165.pdf"],"folder":"IETF/RFC-9165","files":{"pdf":{"path":"standards/IETF/RFC-9165/RFC-9165.pdf","sha256":"75b5f60bf56db5e5c655edc0da0644b955be1cb7827b223ececd4f3be96a4fd2"},"txt":{"path":"standards/IETF/RFC-9165/RFC-9165.txt","sha256":"94f86116c04fde0f11d54576465181090ec33983d78db82527c0703a41976774"}},"tags":["nested-reference","unchanged"],"summary":"The Concise Data Definition Language (CDDL), standardized in RFC\n 8610, provides \"control operators\" as its main language extension\n point.\n\n The present document defines a number of control operators that were\n not yet ready at the time RFC 8610 was completed: .plus, .cat, and\n .det for the construction of constants; .abnf/.abnfb for including\n ABNF (RFC 5234 and RFC 7405) in CDDL specifications; and .feature for\n indicating the use of a non-basic feature in an instance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the","scope_keywords":["9165","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9165 The Concise Data Definition Language (CDDL), standardized in RFC\n 8610, provides \"control operators\" as its main language extension\n point.\n\n The present document defines a number of control operators that were\n not yet ready at the time RFC 8610 was completed: .plus, .cat, and\n .det for the construction of constants; .abnf/.abnfb for including\n ABNF (RFC 5234 and RFC 7405) in CDDL specifications; and .feature for\n indicating the use of a non-basic feature in an instance.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the 9165 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9175","type":"specification","body":"IETF","designation":"RFC 9175","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9175.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9175.txt","https://www.rfc-editor.org/rfc/rfc9175.pdf"],"folder":"IETF/RFC-9175","files":{"pdf":{"path":"standards/IETF/RFC-9175/RFC-9175.pdf","sha256":"851b65a91462ea7dab22719076525e2e72b9539804f6c802e5c130de073fefa8"},"txt":{"path":"standards/IETF/RFC-9175/RFC-9175.txt","sha256":"103a997a5a3391f9432a84162168e63c0e7de83c08cf0159339d8e7358a4666a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies enhancements to the Constrained Application\n Protocol (CoAP) that mitigate security issues in particular use\n cases. The Echo option enables a CoAP server to verify the freshness\n of a request or to force a client to demonstrate reachability at its\n claimed network address. The Request-Tag option allows the CoAP\n server to match block-wise message fragments belonging to the same\n request. This document updates RFC 7252 with respect to the\n following: processing requirements for client Tokens, forbidding non-\n secure reuse of Tokens to ensure response-to-request binding when\n CoAP is used with a security protocol, and amplification mitigation\n (where the use of the Echo option is now recommended).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consen","scope_keywords":["9175","http","https","key","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9177","folder":"IETF/RFC-9177","source":"IETF/RFC-9177/RFC-9177.txt","version":null}],"search_text":"IETF RFC 9175 This document specifies enhancements to the Constrained Application\n Protocol (CoAP) that mitigate security issues in particular use\n cases. The Echo option enables a CoAP server to verify the freshness\n of a request or to force a client to demonstrate reachability at its\n claimed network address. The Request-Tag option allows the CoAP\n server to match block-wise message fragments belonging to the same\n request. This document updates RFC 7252 with respect to the\n following: processing requirements for client Tokens, forbidding non-\n secure reuse of Tokens to ensure response-to-request binding when\n CoAP is used with a security protocol, and amplification mitigation\n (where the use of the Echo option is now recommended).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consen 9175 http https key license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9177","type":"specification","body":"IETF","designation":"RFC 9177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9177.txt","https://www.rfc-editor.org/rfc/rfc9177.pdf"],"folder":"IETF/RFC-9177","files":{"pdf":{"path":"standards/IETF/RFC-9177/RFC-9177.pdf","sha256":"6474d2f28e4286102c4c83bab419e9ccad432e024eb040919b8c7573d4c4f0db"},"txt":{"path":"standards/IETF/RFC-9177/RFC-9177.txt","sha256":"9d30ee75ff09a98919e310c903b7a371325b1fb017c5e46646c8bb5f0fe9fb0f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies alternative Constrained Application Protocol\n (CoAP) block-wise transfer options: Q-Block1 and Q-Block2.\n\n These options are similar to, but distinct from, the CoAP Block1 and\n Block2 options defined in RFC 7959. The Q-Block1 and Q-Block2\n options are not intended to replace the Block1 and Block2 options but\n rather have the goal of supporting Non-confirmable (NON) messages for\n large amounts of data with fewer packet interchanges. Also, the\n Q-Block1 and Q-Block2 options support faster recovery should any of\n the blocks get lost in transmission.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furth","scope_keywords":["9177","delivery","http","https","key","license","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null}],"search_text":"IETF RFC 9177 This document specifies alternative Constrained Application Protocol\n (CoAP) block-wise transfer options: Q-Block1 and Q-Block2.\n\n These options are similar to, but distinct from, the CoAP Block1 and\n Block2 options defined in RFC 7959. The Q-Block1 and Q-Block2\n options are not intended to replace the Block1 and Block2 options but\n rather have the goal of supporting Non-confirmable (NON) messages for\n large amounts of data with fewer packet interchanges. Also, the\n Q-Block1 and Q-Block2 options support faster recovery should any of\n the blocks get lost in transmission.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Furth 9177 delivery http https key license presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9191","type":"specification","body":"IETF","designation":"RFC 9191","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9191.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9191.txt","https://www.rfc-editor.org/rfc/rfc9191.pdf"],"folder":"IETF/RFC-9191","files":{"pdf":{"path":"standards/IETF/RFC-9191/RFC-9191.pdf","sha256":"9dc9f8458860571c430a331d207a9ed02d223fb5e32f71a5e425e1f877d90cbc"},"txt":{"path":"standards/IETF/RFC-9191/RFC-9191.txt","sha256":"28761a08888bb483eeefd600702617e3c3d463d62265894a6cb32fb3c3434bfd"}},"tags":["nested-reference","unchanged"],"summary":"The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides a standard mechanism for support of multiple authentication\n methods. EAP-TLS and other TLS-based EAP methods are widely deployed\n and used for network access authentication. Large certificates and\n long certificate chains combined with authenticators that drop an EAP\n session after only 40 - 50 round trips is a major deployment problem.\n This document looks at this problem in detail and describes the\n potential solutions available.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not a","scope_keywords":["9191","algorithm","algorithms","authentication","certificate","certificates","credential","credentials","http","https","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 9191 The Extensible Authentication Protocol (EAP), defined in RFC 3748,\n provides a standard mechanism for support of multiple authentication\n methods. EAP-TLS and other TLS-based EAP methods are widely deployed\n and used for network access authentication. Large certificates and\n long certificate chains combined with authenticators that drop an EAP\n session after only 40 - 50 round trips is a major deployment problem.\n This document looks at this problem in detail and describes the\n potential solutions available.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not a 9191 algorithm algorithms authentication certificate certificates credential credentials http https key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9205","type":"specification","body":"IETF","designation":"RFC 9205","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9205.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9205.txt","https://www.rfc-editor.org/rfc/rfc9205.pdf"],"folder":"IETF/RFC-9205","files":{"pdf":{"path":"standards/IETF/RFC-9205/RFC-9205.pdf","sha256":"84cab20e3451dca689ab4895c1d6dea26ac41ee44597d33b3ced36671a943dce"},"txt":{"path":"standards/IETF/RFC-9205/RFC-9205.txt","sha256":"43f73e1abf672f4183892a022efe9e71fd40d2def597e546cfb3c035990e2675"}},"tags":["nested-reference","unchanged"],"summary":"Applications often use HTTP as a substrate to create HTTP-based APIs.\n This document specifies best practices for writing specifications\n that use HTTP to define new application protocols. It is written\n primarily to guide IETF efforts to define application protocols using\n HTTP for deployment on the Internet but might be applicable in other\n situations.\n\n This document obsoletes RFC 3205.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be o","scope_keywords":["9205","authentication","encryption","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null}],"search_text":"IETF RFC 9205 Applications often use HTTP as a substrate to create HTTP-based APIs.\n This document specifies best practices for writing specifications\n that use HTTP to define new application protocols. It is written\n primarily to guide IETF efforts to define application protocols using\n HTTP for deployment on the Internet but might be applicable in other\n situations.\n\n This document obsoletes RFC 3205.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be o 9205 authentication encryption http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9207","type":"specification","body":"IETF","designation":"RFC 9207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9207.txt","https://www.rfc-editor.org/rfc/rfc9207.pdf"],"folder":"IETF/RFC-9207","files":{"pdf":{"path":"standards/IETF/RFC-9207/RFC-9207.pdf","sha256":"f72bc17c45b445a421f11498ca6d4f530c9cf0e04f09edc98a9ca6ec15d8a249"},"txt":{"path":"standards/IETF/RFC-9207/RFC-9207.txt","sha256":"c9c17b9824315aca9bda5c0b5e3627cb24aa28d54324292f3761006209b705fd"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new parameter called iss. This parameter\n is used to explicitly include the issuer identifier of the\n authorization server in the authorization response of an OAuth\n authorization flow. The iss parameter serves as an effective\n countermeasure to \"mix-up attacks\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9207.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF T","scope_keywords":["9207","authorization","credential","credentials","http","https","identification","issuer","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 9207 This document specifies a new parameter called iss. This parameter\n is used to explicitly include the issuer identifier of the\n authorization server in the authorization response of an OAuth\n authorization flow. The iss parameter serves as an effective\n countermeasure to \"mix-up attacks\".\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9207.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF T 9207 authorization credential credentials http https identification issuer key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9209","type":"specification","body":"IETF","designation":"RFC 9209","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9209.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9209.txt","https://www.rfc-editor.org/rfc/rfc9209.pdf"],"folder":"IETF/RFC-9209","files":{"pdf":{"path":"standards/IETF/RFC-9209/RFC-9209.pdf","sha256":"fe82b80202eb4476aac84bb8e00947a5b8f33988badef9dcb6034bf531c6b1f2"},"txt":{"path":"standards/IETF/RFC-9209/RFC-9209.txt","sha256":"f8fad90cdc25954dd7419bd8b5f67620252706dade2f5e08a63f4083406f9da1"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Proxy-Status HTTP response field to convey\n the details of an intermediary's response handling, including\n generated errors.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9209.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Le","scope_keywords":["9209","certificate","delivery","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9230","folder":"IETF/RFC-9230","source":"IETF/RFC-9230/RFC-9230.txt","version":null}],"search_text":"IETF RFC 9209 This document defines the Proxy-Status HTTP response field to convey\n the details of an intermediary's response handling, including\n generated errors.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9209.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Le 9209 certificate delivery http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9218","type":"specification","body":"IETF","designation":"RFC 9218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9218.txt","https://www.rfc-editor.org/rfc/rfc9218.pdf"],"folder":"IETF/RFC-9218","files":{"pdf":{"path":"standards/IETF/RFC-9218/RFC-9218.pdf","sha256":"fa7ae6e57e10cc750c6e37f92d96dd6b0fa3446357b5998d235a95ab2ede5811"},"txt":{"path":"standards/IETF/RFC-9218/RFC-9218.txt","sha256":"b7ae1a59fde881e839f947e2fbd01f7a859e9ffedbaf0a38e78a97aeea01d190"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a scheme that allows an HTTP client to\n communicate its preferences for how the upstream server prioritizes\n responses to its requests, and also allows a server to hint to a\n downstream intermediary how its responses should be prioritized when\n they are forwarded. This document defines the Priority header field\n for communicating the initial priority in an HTTP version-independent\n manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing\n responses. These share a common format structure that is designed to\n provide future extensibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further i","scope_keywords":["9218","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9205","folder":"IETF/RFC-9205","source":"IETF/RFC-9205/RFC-9205.txt","version":null}],"search_text":"IETF RFC 9218 This document describes a scheme that allows an HTTP client to\n communicate its preferences for how the upstream server prioritizes\n responses to its requests, and also allows a server to hint to a\n downstream intermediary how its responses should be prioritized when\n they are forwarded. This document defines the Priority header field\n for communicating the initial priority in an HTTP version-independent\n manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing\n responses. These share a common format structure that is designed to\n provide future extensibility.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further i 9218 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 9224","type":"specification","body":"IETF","designation":"RFC 9224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9224.txt","https://www.rfc-editor.org/rfc/rfc9224.pdf"],"folder":"IETF/RFC-9224","files":{"pdf":{"path":"standards/IETF/RFC-9224/RFC-9224.pdf","sha256":"54dd260db54acd6709e13433e4a54305d0311cb955786073e5af9880a423bcfe"},"txt":{"path":"standards/IETF/RFC-9224/RFC-9224.txt","sha256":"2a3ee03a57df50c57f8b71e1b292d31ab0a32b43e06bcc609039502b357c4403"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a method to find which Registration Data\n Access Protocol (RDAP) server is authoritative to answer queries for\n a requested scope, such as domain names, IP addresses, or Autonomous\n System numbers. This document obsoletes RFC 7484.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9224.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as","scope_keywords":["9224","http","https","key","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 9224 This document specifies a method to find which Registration Data\n Access Protocol (RDAP) server is authoritative to answer queries for\n a requested scope, such as domain names, IP addresses, or Autonomous\n System numbers. This document obsoletes RFC 7484.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9224.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as 9224 http https key license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 9230","type":"specification","body":"IETF","designation":"RFC 9230","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9230.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9230.txt","https://www.rfc-editor.org/rfc/rfc9230.pdf"],"folder":"IETF/RFC-9230","files":{"pdf":{"path":"standards/IETF/RFC-9230/RFC-9230.pdf","sha256":"0ee5949d6a8f437752d2849e1e11e37a67de812f0064347c01fd00376728bf5e"},"txt":{"path":"standards/IETF/RFC-9230/RFC-9230.txt","sha256":"517fdfc47fe9aeb82b1972b3c129db8bdcbea7e75b581295df021a57c3f16e9d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol that allows clients to hide their\n IP addresses from DNS resolvers via proxying encrypted DNS over HTTPS\n (DoH) messages. This improves privacy of DNS operations by not\n allowing any one server entity to be aware of both the client IP\n address and the content of DNS queries and answers.\n\n This experimental protocol has been developed outside the IETF and is\n published here to guide implementation, ensure interoperability among\n implementations, and enable wide-scale experimentation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n documen","scope_keywords":["9230","authentication","encryption","http","https","key","keys","license","policies","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 9230 This document describes a protocol that allows clients to hide their\n IP addresses from DNS resolvers via proxying encrypted DNS over HTTPS\n (DoH) messages. This improves privacy of DNS operations by not\n allowing any one server entity to be aware of both the client IP\n address and the content of DNS queries and answers.\n\n This experimental protocol has been developed outside the IETF and is\n published here to guide implementation, ensure interoperability among\n implementations, and enable wide-scale experimentation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This is a contribution to the RFC Series, independently\n of any other RFC stream. The RFC Editor has chosen to publish this\n documen 9230 authentication encryption http https key keys license policies subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9285","type":"specification","body":"IETF","designation":"RFC 9285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9285.txt","https://www.rfc-editor.org/rfc/rfc9285.pdf"],"folder":"IETF/RFC-9285","files":{"pdf":{"path":"standards/IETF/RFC-9285/RFC-9285.pdf","sha256":"d6a844c97dcee1c2e2653e8abc3704aaf176f4c9684e6ac1397ca912adb7156d"},"txt":{"path":"standards/IETF/RFC-9285/RFC-9285.txt","sha256":"36b6125bbefac3b6d84874034084bf12fce840de11fc31d293332d021bbf6298"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Base45 encoding scheme, which is built\n upon the Base64, Base32, and Base16 encoding schemes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9285.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights","scope_keywords":["9285","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 9285 This document describes the Base45 encoding scheme, which is built\n upon the Base64, Base32, and Base16 encoding schemes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9285.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights 9285 http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 9292","type":"specification","body":"IETF","designation":"RFC 9292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9292.txt","https://www.rfc-editor.org/rfc/rfc9292.pdf"],"folder":"IETF/RFC-9292","files":{"pdf":{"path":"standards/IETF/RFC-9292/RFC-9292.pdf","sha256":"4459d9fc48382bc6a4091e8b5d03e45e0f692a79f348984826e8c888021edbf8"},"txt":{"path":"standards/IETF/RFC-9292/RFC-9292.txt","sha256":"82499b50f19e8667459710b270a3b56eb594494d87f5d6b6f29e79c0e1176e51"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a binary format for representing HTTP messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9292.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.org/license-inf","scope_keywords":["9292","encryption","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null}],"search_text":"IETF RFC 9292 This document defines a binary format for representing HTTP messages.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9292.\n\nCopyright Notice\n\n Copyright (c) 2022 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (https://trustee.ietf.org/license-inf 9292 encryption http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 9338","type":"specification","body":"IETF","designation":"RFC 9338","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9338.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9338.txt","https://www.rfc-editor.org/rfc/rfc9338.pdf"],"folder":"IETF/RFC-9338","files":{"pdf":{"path":"standards/IETF/RFC-9338/RFC-9338.pdf","sha256":"ee400c26599ca3af1f47656303c1fb53ac2a22ad2f88d312f4e40683b3429524"},"txt":{"path":"standards/IETF/RFC-9338/RFC-9338.txt","sha256":"3fd3a4b1cb4060070ffcf6104de0c12c6c5bed6cf2329d9019a16f7717365dde"}},"tags":["nested-reference","unchanged"],"summary":"Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. CBOR Object Signing and\n Encryption (COSE) defines a set of security services for CBOR. This\n document defines a countersignature algorithm along with the needed\n header parameters and CBOR tags for COSE. This document updates RFC\n 9052.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.","scope_keywords":["9338","algorithm","authentication","encryption","http","https","key","license","path","presentation","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 9338 Concise Binary Object Representation (CBOR) is a data format designed\n for small code size and small message size. CBOR Object Signing and\n Encryption (COSE) defines a set of security services for CBOR. This\n document defines a countersignature algorithm along with the needed\n header parameters and CBOR tags for COSE. This document updates RFC\n 9052.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor. 9338 algorithm authentication encryption http https key license path presentation signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 9345","type":"specification","body":"IETF","designation":"RFC 9345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9345.txt","https://www.rfc-editor.org/rfc/rfc9345.pdf"],"folder":"IETF/RFC-9345","files":{"pdf":{"path":"standards/IETF/RFC-9345/RFC-9345.pdf","sha256":"ce3be53a28ec9c83991d612f27ad37a199b84d126e0acbfdcda2d3d43d0c8aa4"},"txt":{"path":"standards/IETF/RFC-9345/RFC-9345.txt","sha256":"42817f99b19f29ebe8cf1c4b3976d3d908cd3605d2846a763fba04aa09f73b1f"}},"tags":["nested-reference","unchanged"],"summary":"The organizational separation between operators of TLS and DTLS\n endpoints and the certification authority can create limitations.\n For example, the lifetime of certificates, how they may be used, and\n the algorithms they support are ultimately determined by the\n Certification Authority (CA). This document describes a mechanism to\n overcome some of these limitations by enabling operators to delegate\n their own credentials for use in TLS and DTLS without breaking\n compatibility with peers that do not support this specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is ava","scope_keywords":["9345","algorithm","algorithms","authentication","certificate","certificates","credential","credentials","delivery","http","https","key","keys","license","revocation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9345 The organizational separation between operators of TLS and DTLS\n endpoints and the certification authority can create limitations.\n For example, the lifetime of certificates, how they may be used, and\n the algorithms they support are ultimately determined by the\n Certification Authority (CA). This document describes a mechanism to\n overcome some of these limitations by enabling operators to delegate\n their own credentials for use in TLS and DTLS without breaking\n compatibility with peers that do not support this specification.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is ava 9345 algorithm algorithms authentication certificate certificates credential credentials delivery http https key keys license revocation risk nested-reference unchanged"},{"id":"IETF RFC 9360","type":"specification","body":"IETF","designation":"RFC 9360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9360.txt","https://www.rfc-editor.org/rfc/rfc9360.pdf"],"folder":"IETF/RFC-9360","files":{"pdf":{"path":"standards/IETF/RFC-9360/RFC-9360.pdf","sha256":"5b43a9e5b217c53984cb5d9d31974b3aa77aa0de16f00298f95347975473dfc0"},"txt":{"path":"standards/IETF/RFC-9360/RFC-9360.txt","sha256":"3dbe546adf08e309b429c8e71b2ee8384292fb8767338d3eb17d1c4e5adefc23"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"The CBOR Object Signing and Encryption (COSE) message structure uses\n references to keys in general. For some algorithms, additional\n properties are defined that carry parameters relating to keys as\n needed. The COSE Key structure is used for transporting keys outside\n of COSE messages. This document extends the way that keys can be\n identified and transported by providing attributes that refer to or\n contain X.509 certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata","scope_keywords":["9360","algorithm","algorithms","attribute","attributes","authentication","certificate","certificates","encryption","hash","http","https","key","keys","license","management"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 9360 The CBOR Object Signing and Encryption (COSE) message structure uses\n references to keys in general. For some algorithms, additional\n properties are defined that carry parameters relating to keys as\n needed. The COSE Key structure is used for transporting keys outside\n of COSE messages. This document extends the way that keys can be\n identified and transported by providing attributes that refer to or\n contain X.509 certificates.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata 9360 algorithm algorithms attribute attributes authentication certificate certificates encryption hash http https key keys license management cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"IETF RFC 9393","type":"specification","body":"IETF","designation":"RFC 9393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9393.txt","https://www.rfc-editor.org/rfc/rfc9393.pdf"],"folder":"IETF/RFC-9393","files":{"pdf":{"path":"standards/IETF/RFC-9393/RFC-9393.pdf","sha256":"ea0e18b270f5450b0997d9e1b426584db6e57df394dba5b8ad6c839d101cc1cc"},"txt":{"path":"standards/IETF/RFC-9393/RFC-9393.txt","sha256":"6708be37258615edb39de76e32b11439967885d6792f4e2f0ee02de1a0864ebc"}},"tags":["nested-reference","unchanged"],"summary":"ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an\n extensible XML-based structure to identify and describe individual\n software components, patches, and installation bundles. SWID tag\n representations can be too large for devices with network and storage\n constraints. This document defines a concise representation of SWID\n tags: Concise SWID (CoSWID) tags. CoSWID supports a set of semantics\n and features that are similar to those for SWID tags, as well as new\n semantics that allow CoSWIDs to describe additional types of\n information, all in a more memory-efficient format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering","scope_keywords":["9393","attestation","attribute","attributes","hash","http","https","identification","license","management","path","presentation","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 9393 ISO/IEC 19770-2:2015 Software Identification (SWID) tags provide an\n extensible XML-based structure to identify and describe individual\n software components, patches, and installation bundles. SWID tag\n representations can be too large for devices with network and storage\n constraints. This document defines a concise representation of SWID\n tags: Concise SWID (CoSWID) tags. CoSWID supports a set of semantics\n and features that are similar to those for SWID tags, as well as new\n semantics that allow CoSWIDs to describe additional types of\n information, all in a more memory-efficient format.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering 9393 attestation attribute attributes hash http https identification license management path presentation subject trust validation nested-reference unchanged"},{"id":"IETF RFC 9440","type":"specification","body":"IETF","designation":"RFC 9440","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9440.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9440.txt","https://www.rfc-editor.org/rfc/rfc9440.pdf"],"folder":"IETF/RFC-9440","files":{"pdf":{"path":"standards/IETF/RFC-9440/RFC-9440.pdf","sha256":"39be74fadc5ecebdbbb055ba90e0b1204e2b29708e57a896180e6fc6c2ce5014"},"txt":{"path":"standards/IETF/RFC-9440/RFC-9440.txt","sha256":"5cd22667bded4984e28933bdd12be23452d3a372f8dadf5a9a72341f7691cb48"}},"tags":["nested-reference","unchanged"],"summary":"This document describes HTTP extension header fields that allow a TLS\n terminating reverse proxy (TTRP) to convey the client certificate\n information of a mutually authenticated TLS connection to the origin\n server in a common and predictable manner.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.or","scope_keywords":["9440","audit","authentication","certificate","delivery","http","https","key","license","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9700","folder":"IETF/RFC-9700","source":"IETF/RFC-9700/RFC-9700.txt","version":null}],"search_text":"IETF RFC 9440 This document describes HTTP extension header fields that allow a TLS\n terminating reverse proxy (TTRP) to convey the client certificate\n information of a mutually authenticated TLS connection to the origin\n server in a common and predictable manner.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.or 9440 audit authentication certificate delivery http https key license subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9457","type":"specification","body":"IETF","designation":"RFC 9457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9457.txt","https://www.rfc-editor.org/rfc/rfc9457.pdf"],"folder":"IETF/RFC-9457","files":{"pdf":{"path":"standards/IETF/RFC-9457/RFC-9457.pdf","sha256":"9e556f5dcbf7dd780928cfe03ec7f2080a635e1bcb41ddbeecbe8141c67d09ed"},"txt":{"path":"standards/IETF/RFC-9457/RFC-9457.txt","sha256":"f2b3db92fb0bf3489cb3841a0da0c0d88dff40797b64d40b6123085183886c7b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a \"problem detail\" to carry machine-readable\n details of errors in HTTP response content to avoid the need to\n define new error response formats for HTTP APIs.\n\n This document obsoletes RFC 7807.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9457.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights res","scope_keywords":["9457","http","https","key","license","presentation","profile","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9458","folder":"IETF/RFC-9458","source":"IETF/RFC-9458/RFC-9458.txt","version":null},{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"IETF RFC 9457 This document defines a \"problem detail\" to carry machine-readable\n details of errors in HTTP response content to avoid the need to\n define new error response formats for HTTP APIs.\n\n This document obsoletes RFC 7807.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9457.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights res 9457 http https key license presentation profile registered subject trust nested-reference unchanged"},{"id":"IETF RFC 9461","type":"specification","body":"IETF","designation":"RFC 9461","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9461.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9461.txt","https://www.rfc-editor.org/rfc/rfc9461.pdf"],"folder":"IETF/RFC-9461","files":{"pdf":{"path":"standards/IETF/RFC-9461/RFC-9461.pdf","sha256":"01ba0bf1464091f0f7f3216a64f5a049900b4e417d54ea75ea7d1d3617e84ae8"},"txt":{"path":"standards/IETF/RFC-9461/RFC-9461.txt","sha256":"893239820e32384f536b607037a5bca225bd67a7ecbf0414fea5746e1b25c4c0"}},"tags":["nested-reference","unchanged"],"summary":"The SVCB DNS resource record type expresses a bound collection of\n endpoint metadata, for use when establishing a connection to a named\n service. DNS itself can be such a service, when the server is\n identified by a domain name. This document provides the SVCB mapping\n for named DNS servers, allowing them to indicate support for\n encrypted transport protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.r","scope_keywords":["9461","authentication","http","https","key","keys","license","path","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"IETF RFC 9461 The SVCB DNS resource record type expresses a bound collection of\n endpoint metadata, for use when establishing a connection to a named\n service. DNS itself can be such a service, when the server is\n identified by a domain name. This document provides the SVCB mapping\n for named DNS servers, allowing them to indicate support for\n encrypted transport protocols.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.r 9461 authentication http https key keys license path subject tls trust nested-reference unchanged"},{"id":"IETF RFC 9470","type":"specification","body":"IETF","designation":"RFC 9470","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9470.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9470.txt","https://www.rfc-editor.org/rfc/rfc9470.pdf"],"folder":"IETF/RFC-9470","files":{"pdf":{"path":"standards/IETF/RFC-9470/RFC-9470.pdf","sha256":"1a1c5dbebb81d6110041f6eae98f332d4ca00b4c491ca3dc6b8d063e85830ec6"},"txt":{"path":"standards/IETF/RFC-9470/RFC-9470.txt","sha256":"02d742f49cc0a03fb09197563c436b6f38928a71b0d8e41cde9cfe0362363e56"}},"tags":["nested-reference","unchanged"],"summary":"It is not uncommon for resource servers to require different\n authentication strengths or recentness according to the\n characteristics of a request. This document introduces a mechanism\n that resource servers can use to signal to a client that the\n authentication event associated with the access token of the current\n request does not meet its authentication requirements and, further,\n how to meet them. This document also codifies a mechanism for a\n client to request that an authorization server achieve a specific\n authentication strength or recentness when processing an\n authorization request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Stee","scope_keywords":["9470","authentication","authorization","http","https","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9470 It is not uncommon for resource servers to require different\n authentication strengths or recentness according to the\n characteristics of a request. This document introduces a mechanism\n that resource servers can use to signal to a client that the\n authentication event associated with the access token of the current\n request does not meet its authentication requirements and, further,\n how to meet them. This document also codifies a mechanism for a\n client to request that an authorization server achieve a specific\n authentication strength or recentness when processing an\n authorization request.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Stee 9470 authentication authorization http https key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 9485","type":"specification","body":"IETF","designation":"RFC 9485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9485.txt","https://www.rfc-editor.org/rfc/rfc9485.pdf"],"folder":"IETF/RFC-9485","files":{"pdf":{"path":"standards/IETF/RFC-9485/RFC-9485.pdf","sha256":"fc4a525ee5be7b08ff288a2dace6a22d6bee14cc201abbcf732bf887d7e62c6e"},"txt":{"path":"standards/IETF/RFC-9485/RFC-9485.txt","sha256":"61e7addfe64e3b0fbff96619d067f3812aa9960cf9b87526d064c3fb3bfbe91f"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies I-Regexp, a flavor of regular expression that\n is limited in scope with the goal of interoperation across many\n different regular expression libraries.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9485.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7","scope_keywords":["9485","http","https","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"IETF RFC 9485 This document specifies I-Regexp, a flavor of regular expression that\n is limited in scope with the goal of interoperation across many\n different regular expression libraries.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9485.\n\nCopyright Notice\n\n Copyright (c) 2023 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7 9485 http https key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 9700","type":"specification","body":"IETF","designation":"RFC 9700","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9700.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9700.txt","https://www.rfc-editor.org/rfc/rfc9700.pdf"],"folder":"IETF/RFC-9700","files":{"pdf":{"path":"standards/IETF/RFC-9700/RFC-9700.pdf","sha256":"2a9d43a83bc39c2f033046ff685f94651ddac94e57ee261d7303790af6cbf648"},"txt":{"path":"standards/IETF/RFC-9700/RFC-9700.txt","sha256":"9919d061d40a97886ca866b51c69389b6c81c65cd4b979056c14fdbebfcf622a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes best current security practice for OAuth 2.0.\n It updates and extends the threat model and security advice given in\n RFCs 6749, 6750, and 6819 to incorporate practical experiences\n gathered since OAuth 2.0 was published and covers new threats\n relevant due to the broader application of OAuth 2.0. Further, it\n deprecates some modes of operation that are deemed less secure or\n even insecure.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide","scope_keywords":["9700","authentication","authorization","credential","credentials","http","https","identification","issuer","license","signature","signatures","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 9728","folder":"IETF/RFC-9728","source":"IETF/RFC-9728/RFC-9728.txt","version":null}],"search_text":"IETF RFC 9700 This document describes best current security practice for OAuth 2.0.\n It updates and extends the threat model and security advice given in\n RFCs 6749, 6750, and 6819 to incorporate practical experiences\n gathered since OAuth 2.0 was published and covers new threats\n relevant due to the broader application of OAuth 2.0. Further, it\n deprecates some modes of operation that are deemed less secure or\n even insecure.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide 9700 authentication authorization credential credentials http https identification issuer license signature signatures subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 9728","type":"specification","body":"IETF","designation":"RFC 9728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9728.txt","https://www.rfc-editor.org/rfc/rfc9728.pdf"],"folder":"IETF/RFC-9728","files":{"pdf":{"path":"standards/IETF/RFC-9728/RFC-9728.pdf","sha256":"06a875bd465d1d40d07c1fce7e6323022d6161b2b2e256ca62bf321919360df4"},"txt":{"path":"standards/IETF/RFC-9728/RFC-9728.txt","sha256":"b65bcd0d9daf90fd7006a42cf48e0ac3ba24b7f5637d5197f2de41c6b91c8a89"}},"tags":["unchanged"],"summary":"This specification defines a metadata format that an OAuth 2.0 client\n or authorization server can use to obtain the information needed to\n interact with an OAuth 2.0 protected resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9728.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje","scope_keywords":["9728","authentication","authorization","encryption","http","https","issuer","key","keys","license","signature","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"IETF RFC 9728 This specification defines a metadata format that an OAuth 2.0 client\n or authorization server can use to obtain the information needed to\n interact with an OAuth 2.0 protected resource.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9728.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subje 9728 authentication authorization encryption http https issuer key keys license signature subject tls trust validation unchanged"},{"id":"IETF RFC 9741","type":"specification","body":"IETF","designation":"RFC 9741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9741.txt","https://www.rfc-editor.org/rfc/rfc9741.pdf"],"folder":"IETF/RFC-9741","files":{"pdf":{"path":"standards/IETF/RFC-9741/RFC-9741.pdf","sha256":"53ff8ff2bb4cfc9579329e2dca8e5905d048c1b01ab40dc5f3730f89108820b3"},"txt":{"path":"standards/IETF/RFC-9741/RFC-9741.txt","sha256":"3234aeea39d01b7c1c8e9c70d4d7dc8745852e0b6edbea167a3e55b91e7a9ee3"}},"tags":["nested-reference","unchanged"],"summary":"The Concise Data Definition Language (CDDL), standardized in RFC\n 8610, provides \"control operators\" as its main language extension\n point. RFCs have added to this extension point in both an\n application-specific and a more general way.\n\n The present document defines a number of additional generally\n applicable control operators for text conversion (bytes, integers,\n printf-style formatting, and JSON) and for an operation on text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any erra","scope_keywords":["9741","http","https","key","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9741 The Concise Data Definition Language (CDDL), standardized in RFC\n 8610, provides \"control operators\" as its main language extension\n point. RFCs have added to this extension point in both an\n application-specific and a more general way.\n\n The present document defines a number of additional generally\n applicable control operators for text conversion (bytes, integers,\n printf-style formatting, and JSON) and for an operation on text.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any erra 9741 http https key license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 9781","type":"specification","body":"IETF","designation":"RFC 9781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9781.txt","https://www.rfc-editor.org/rfc/rfc9781.pdf"],"folder":"IETF/RFC-9781","files":{"pdf":{"path":"standards/IETF/RFC-9781/RFC-9781.pdf","sha256":"288a5b155716ff62d2db18f0fdd1b3e626bb4892e63427374ece825c1e75cdd7"},"txt":{"path":"standards/IETF/RFC-9781/RFC-9781.txt","sha256":"d8c927ce89da936de9fff0021565154b38394775d643780b3a1b55243112d4c5"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the Unprotected CWT Claims Set (UCCS), a data\n format for representing a CBOR Web Token (CWT) Claims Set without\n protecting it by a signature, Message Authentication Code (MAC), or\n encryption. UCCS enables the use of CWT claims in environments where\n protection is provided by other means, such as secure communication\n channels or trusted execution environments. This specification\n defines a CBOR tag for UCCS and describes the UCCS format, its\n encoding, and its processing considerations. It also discusses\n security implications of using unprotected claims sets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Grou","scope_keywords":["9781","algorithm","attestation","authentication","encryption","http","https","key","keys","license","path","presentation","preservation","signature","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9781 This document defines the Unprotected CWT Claims Set (UCCS), a data\n format for representing a CBOR Web Token (CWT) Claims Set without\n protecting it by a signature, Message Authentication Code (MAC), or\n encryption. UCCS enables the use of CWT claims in environments where\n protection is provided by other means, such as secure communication\n channels or trusted execution environments. This specification\n defines a CBOR tag for UCCS and describes the UCCS format, its\n encoding, and its processing considerations. It also discusses\n security implications of using unprotected claims sets.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Grou 9781 algorithm attestation authentication encryption http https key keys license path presentation preservation signature subject tls nested-reference unchanged"},{"id":"IETF RFC 9999","type":"specification","body":"IETF","designation":"RFC 9999","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9999.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9999.txt","https://www.rfc-editor.org/rfc/rfc9999.pdf"],"folder":"IETF/RFC-9999","files":{"pdf":{"path":"standards/IETF/RFC-9999/RFC-9999.pdf","sha256":"1991243259c278f4ed62de796e63d97c32a511de86f963aba75de79cfc15494c"},"txt":{"path":"standards/IETF/RFC-9999/RFC-9999.txt","sha256":"cd456e6843e0bb9f0d2ae5530b24147ec77efb257a8e46ccfec6f5fb33d2a1e7"}},"tags":["nested-reference","unchanged"],"summary":"The conceptual messages introduced by the Remote ATtestation\n procedureS (RATS) architecture (RFC 9334) are protocol-agnostic data\n units that are conveyed between RATS roles during RATS interactions.\n Conceptual messages describe the meaning and function of such data\n units within RATS data flows without specifying a wire format,\n encoding, transport mechanism, or processing details. The initial\n set of conceptual messages is defined in Section 8 of RFC 9334 and\n includes Evidence, Attestation Results, Endorsements, Reference\n Values, and Appraisal Policies.\n\n This document introduces the Conceptual Message Wrapper (CMW) that\n provides a common structure to encapsulate these messages. It\n defines a dedicated Concise Binary Object Representation (CBOR) tag,\n corresponding JSON Web Token (JWT) and CBOR Web Token (CWT) claims,\n and an X.509 extension.\n\n Together, these mechanisms allow CMW","scope_keywords":["9999","attestation","certificate","certificates","http","https","license","path","pki","policies","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null}],"search_text":"IETF RFC 9999 The conceptual messages introduced by the Remote ATtestation\n procedureS (RATS) architecture (RFC 9334) are protocol-agnostic data\n units that are conveyed between RATS roles during RATS interactions.\n Conceptual messages describe the meaning and function of such data\n units within RATS data flows without specifying a wire format,\n encoding, transport mechanism, or processing details. The initial\n set of conceptual messages is defined in Section 8 of RFC 9334 and\n includes Evidence, Attestation Results, Endorsements, Reference\n Values, and Appraisal Policies.\n\n This document introduces the Conceptual Message Wrapper (CMW) that\n provides a common structure to encapsulate these messages. It\n defines a dedicated Concise Binary Object Representation (CBOR) tag,\n corresponding JSON Web Token (JWT) and CBOR Web Token (CWT) claims,\n and an X.509 extension.\n\n Together, these mechanisms allow CMW 9999 attestation certificate certificates http https license path pki policies presentation subject tls trust nested-reference unchanged"},{"id":"IETF SD-JWT VC","type":"specification","body":"IETF","designation":"SD-JWT VC","version":null,"title":"SD-JWT-based Verifiable Credentials","purpose":null,"status":"unchanged","download_url":"https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-17.html","download_urls":["https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-17.html","https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc"],"folder":"IETF/SD-JWT-VC","files":{"html":{"path":"standards/IETF/SD-JWT-VC/SD-JWT-VC.html","sha256":"a6d9bb8d147d2a54cfa7e722e63f92f28253ddf774b6cebface19ffbbaf80e21"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification describes data formats as well as validation and processing\nrules to express Verifiable Digital Credentials with JSON payloads with and without selective disclosure based on the SD-JWT format. ¶ \n \n \n \n Discussion Venues \n \n This note is to be removed before publishing as an RFC. ¶ \n Discussion of this document takes place on the\n Web Authorization Protocol Working Group mailing list (oauth@ietf.org),\n which is archived at https://mailarchive.ietf.org/arch/browse/oauth/ . ¶ \n Source for this draft and an issue tracker can be found at\n https://github.com/oauth-wg/oauth-sd-jwt-vc . ¶ \n \n \n \n \n Status of This Memo \n \n \n This Internet-Draft is submitted in full conformance with the\n provisions of BCP 78 and BCP 79. ¶ \n \n Internet-Drafts are working documents of the Internet Engineering Task\n Force (IETF). Note that other groups may also distribute working\n documents as Int","scope_keywords":["jwt","authorization","credential","credentials","http","https","key","license","validation","verifiable"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS04","folder":"ARF/TS04-V1.0.1","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS09","folder":"ARF/TS09-V1.1","source":"ARF/TS09-V1.1/TS09-V1.1.md","version":"1.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS13","folder":"ARF/TS13","source":"ARF/TS13/TS13-V1.0.1.md","version":null},{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF SD-JWT VC SD-JWT-based Verifiable Credentials This specification describes data formats as well as validation and processing\nrules to express Verifiable Digital Credentials with JSON payloads with and without selective disclosure based on the SD-JWT format. ¶ \n \n \n \n Discussion Venues \n \n This note is to be removed before publishing as an RFC. ¶ \n Discussion of this document takes place on the\n Web Authorization Protocol Working Group mailing list (oauth@ietf.org),\n which is archived at https://mailarchive.ietf.org/arch/browse/oauth/ . ¶ \n Source for this draft and an issue tracker can be found at\n https://github.com/oauth-wg/oauth-sd-jwt-vc . ¶ \n \n \n \n \n Status of This Memo \n \n \n This Internet-Draft is submitted in full conformance with the\n provisions of BCP 78 and BCP 79. ¶ \n \n Internet-Drafts are working documents of the Internet Engineering Task\n Force (IETF). Note that other groups may also distribute working\n documents as Int jwt authorization credential credentials http https key license validation verifiable cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"W3C vc-data-model V1.1","type":"specification","body":"W3C","designation":"vc-data-model","version":"1.1","title":"Verifiable Credentials Data Model 1.1","purpose":null,"status":"unchanged","download_url":"https://www.w3.org/TR/vc-data-model/","download_urls":["https://www.w3.org/TR/vc-data-model/","https://www.w3.org/TR/vc-data-model-1.1/"],"folder":"W3C/vc-data-model-V1.1","files":{"html":{"path":"standards/W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","sha256":"a9196a3d0b6601356c4e127bad24f8c7f2c17f6ed22e41b35755a910104156f8"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"Abstract \n \nA verifiable credential is a specific way to express a set of claims \nmade by an issuer , such as a driver's license or an education certificate. This\nspecification describes the extensible data model for verifiable credentials ,\nhow they can be secured from tampering, and a three-party ecosystem for\nthe exchange of these credentials that is composed of issuers , holders ,\nand verifiers . This document also covers a variety of security, privacy,\ninternationalization, and accessibility considerations for ecosystems that\nuse the technologies described in this specification.","scope_keywords":["model","algorithm","attestation","attestations","attribute","attributes","certificate","credential","credentials","eudi","holder","http","https","issuer","key","license"],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32024R2979","eli":"https://data.europa.eu/eli/reg_impl/2024/2979/oj/eng","id":"2024-2979","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2979/2024-2979.md","title":"Integrity and core functionalities of EUDI Wallets"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"W3C vc-data-model 1.1 Verifiable Credentials Data Model 1.1 Abstract \n \nA verifiable credential is a specific way to express a set of claims \nmade by an issuer , such as a driver's license or an education certificate. This\nspecification describes the extensible data model for verifiable credentials ,\nhow they can be secured from tampering, and a three-party ecosystem for\nthe exchange of these credentials that is composed of issuers , holders ,\nand verifiers . This document also covers a variety of security, privacy,\ninternationalization, and accessibility considerations for ecosystems that\nuse the technologies described in this specification. model algorithm attestation attestations attribute attributes certificate credential credentials eudi holder http https issuer key license cited-by-eu-law implementing-regulation nested-reference unchanged 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2024-2979 Integrity and core functionalities of EUDI Wallets 32024R2979"},{"id":"IETF RFC 2489","type":"specification","body":"IETF","designation":"RFC 2489","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2489.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2489.txt","https://www.rfc-editor.org/rfc/rfc2489.pdf"],"folder":"IETF/RFC-2489","files":{"txt":{"path":"standards/IETF/RFC-2489/RFC-2489.txt","sha256":"384c051dee61c54a3e81b9f9d0252cc212f002683e602685c5d6f60bd8748ac3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Droms\nRequest for Comments: 2489 Bucknell University\nBCP: 29 January 1999\nCategory: Best Current Practice\n\n Procedure for Defining New DHCP Options\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n Configuration parameters and other control information are carried in\n tagged data items that are stored in the 'options' field of the DHCP\n message. The data items themselves are also called \"options.\"\n\n New DHCP options may be defined after the publication of the DHCP\n specificati","scope_keywords":["2489","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2939","folder":"IETF/RFC-2939","source":"IETF/RFC-2939/RFC-2939.txt","version":null},{"body":"IETF","designation":"RFC 3679","folder":"IETF/RFC-3679","source":"IETF/RFC-3679/RFC-3679.txt","version":null}],"search_text":"IETF RFC 2489 Network Working Group R. Droms\nRequest for Comments: 2489 Bucknell University\nBCP: 29 January 1999\nCategory: Best Current Practice\n\n Procedure for Defining New DHCP Options\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a TCP/IP network.\n Configuration parameters and other control information are carried in\n tagged data items that are stored in the 'options' field of the DHCP\n message. The data items themselves are also called \"options.\"\n\n New DHCP options may be defined after the publication of the DHCP\n specificati 2489 authentication nested-reference unchanged"},{"id":"IETF RFC 2939","type":"specification","body":"IETF","designation":"RFC 2939","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2939.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2939.txt","https://www.rfc-editor.org/rfc/rfc2939.pdf"],"folder":"IETF/RFC-2939","files":{"txt":{"path":"standards/IETF/RFC-2939/RFC-2939.txt","sha256":"aeb311959b9596ee4afb0acd3200ba1fc980b80f1cb98371c17e790669bfc7ec"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a Transmission\n Control Protocol/Internet Protocol (TCP/IP) network. Configuration\n parameters and other control information are carried in tagged data\n items that are stored in the 'options' field of the DHCP message.\n The data items themselves are also called \"options\".\n\n DHCP protocol messages are identified by the 'DHCP Message Type'\n option (option code 51). Each message type is defined by the data\n value carried in the 'DHCP Message Type' option.\n\n New DHCP options and message types may be defined after the\n publication of the DHCP specification to accommodate requirements for\n conveyance of new configuration parameters or to accommodate new\n protocol semantics. This document describes the procedure for\n defining new DHCP options and message types.\n\n1. Introduction","scope_keywords":["2939"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3679","folder":"IETF/RFC-3679","source":"IETF/RFC-3679/RFC-3679.txt","version":null},{"body":"IETF","designation":"RFC 3925","folder":"IETF/RFC-3925","source":"IETF/RFC-3925/RFC-3925.txt","version":null},{"body":"IETF","designation":"RFC 3942","folder":"IETF/RFC-3942","source":"IETF/RFC-3942/RFC-3942.txt","version":null},{"body":"IETF","designation":"RFC 4039","folder":"IETF/RFC-4039","source":"IETF/RFC-4039/RFC-4039.txt","version":null},{"body":"IETF","designation":"RFC 4578","folder":"IETF/RFC-4578","source":"IETF/RFC-4578/RFC-4578.txt","version":null},{"body":"IETF","designation":"RFC 4833","folder":"IETF/RFC-4833","source":"IETF/RFC-4833/RFC-4833.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 2939 The Dynamic Host Configuration Protocol (DHCP) provides a framework\n for passing configuration information to hosts on a Transmission\n Control Protocol/Internet Protocol (TCP/IP) network. Configuration\n parameters and other control information are carried in tagged data\n items that are stored in the 'options' field of the DHCP message.\n The data items themselves are also called \"options\".\n\n DHCP protocol messages are identified by the 'DHCP Message Type'\n option (option code 51). Each message type is defined by the data\n value carried in the 'DHCP Message Type' option.\n\n New DHCP options and message types may be defined after the\n publication of the DHCP specification to accommodate requirements for\n conveyance of new configuration parameters or to accommodate new\n protocol semantics. This document describes the procedure for\n defining new DHCP options and message types.\n\n1. Introduction 2939 nested-reference unchanged"},{"id":"IETF RFC 4477","type":"specification","body":"IETF","designation":"RFC 4477","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4477.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4477.txt","https://www.rfc-editor.org/rfc/rfc4477.pdf"],"folder":"IETF/RFC-4477","files":{"txt":{"path":"standards/IETF/RFC-4477/RFC-4477.txt","sha256":"d2feb6973794f7960586905e7d14e6796f602dca1e8d73a1619f31af9f1cffb8"}},"tags":["nested-reference","unchanged"],"summary":"A node may have support for communications using IPv4 and/or IPv6\n protocols. Such a node may wish to obtain IPv4 and/or IPv6\n configuration settings via the Dynamic Host Configuration Protocol\n (DHCP). The original version of DHCP (RFC 2131) designed for IPv4\n has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This\n document describes issues identified with dual IP version DHCP\n interactions, the most important aspect of which is how to handle\n potential problems in clients processing configuration information\n received from both DHCPv4 and DHCPv6 servers. The document makes a\n recommendation on the general strategy on how best to handle such\n issues and identifies future work to be undertaken.\n\nChown, et al. Informational [Page 1]\n\f\nRFC 4477 DHCP: Dual-Stack Issues May 2006","scope_keywords":["4477","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 4477 A node may have support for communications using IPv4 and/or IPv6\n protocols. Such a node may wish to obtain IPv4 and/or IPv6\n configuration settings via the Dynamic Host Configuration Protocol\n (DHCP). The original version of DHCP (RFC 2131) designed for IPv4\n has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This\n document describes issues identified with dual IP version DHCP\n interactions, the most important aspect of which is how to handle\n potential problems in clients processing configuration information\n received from both DHCPv4 and DHCPv6 servers. The document makes a\n recommendation on the general strategy on how best to handle such\n issues and identifies future work to be undertaken.\n\nChown, et al. Informational [Page 1]\n\f\nRFC 4477 DHCP: Dual-Stack Issues May 2006 4477 management path nested-reference unchanged"},{"id":"IETF RFC 4580","type":"specification","body":"IETF","designation":"RFC 4580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4580.txt","https://www.rfc-editor.org/rfc/rfc4580.pdf"],"folder":"IETF/RFC-4580","files":{"txt":{"path":"standards/IETF/RFC-4580/RFC-4580.txt","sha256":"0ade921ddd1f04172fa65d18910746b549fe98f3806feae1bc805366ad604951"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a new Relay Agent Subscriber-ID option for the\n Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option\n allows a DHCPv6 relay agent to associate a stable \"Subscriber-ID\"\n with DHCPv6 client messages in a way that is independent of the\n client and of the underlying physical network infrastructure.","scope_keywords":["4580","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null}],"search_text":"IETF RFC 4580 This memo defines a new Relay Agent Subscriber-ID option for the\n Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option\n allows a DHCPv6 relay agent to associate a stable \"Subscriber-ID\"\n with DHCPv6 client messages in a way that is independent of the\n client and of the underlying physical network infrastructure. 4580 path nested-reference unchanged"},{"id":"IETF RFC 4925","type":"specification","body":"IETF","designation":"RFC 4925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4925.txt","https://www.rfc-editor.org/rfc/rfc4925.pdf"],"folder":"IETF/RFC-4925","files":{"txt":{"path":"standards/IETF/RFC-4925/RFC-4925.txt","sha256":"65b178df6a0109011d502852602a70ab559b56ad66fe55739d0fa31509a3f929"}},"tags":["nested-reference","unchanged"],"summary":"This document captures the problem statement for the Softwires\n Working Group, which is developing standards for the discovery,\n control, and encapsulation methods for connecting IPv4 networks\n across IPv6-only networks as well as IPv6 networks across IPv4-only\n networks. The standards will encourage multiple, inter-operable\n vendor implementations by identifying, and extending where necessary,\n existing standard protocols to resolve a selected set of \"IPv4/IPv6\"\n and \"IPv6/IPv4\" transition problems. This document describes the\n specific problems (\"Hubs and Spokes\" and \"Mesh\") that will be solved\n by the standards developed by the Softwires Working Group. Some\n requirements (and non-requirements) are also identified to better\n describe the specific problem scope.\n\nLi, et al. Informational [Page 1]\n\f\nRFC 4925 Softwire Problem Statement July 2007","scope_keywords":["4925","authentication","authorization","delivery","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 5571","folder":"IETF/RFC-5571","source":"IETF/RFC-5571/RFC-5571.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 7040","folder":"IETF/RFC-7040","source":"IETF/RFC-7040/RFC-7040.txt","version":null}],"search_text":"IETF RFC 4925 This document captures the problem statement for the Softwires\n Working Group, which is developing standards for the discovery,\n control, and encapsulation methods for connecting IPv4 networks\n across IPv6-only networks as well as IPv6 networks across IPv4-only\n networks. The standards will encourage multiple, inter-operable\n vendor implementations by identifying, and extending where necessary,\n existing standard protocols to resolve a selected set of \"IPv4/IPv6\"\n and \"IPv6/IPv4\" transition problems. This document describes the\n specific problems (\"Hubs and Spokes\" and \"Mesh\") that will be solved\n by the standards developed by the Softwires Working Group. Some\n requirements (and non-requirements) are also identified to better\n describe the specific problem scope.\n\nLi, et al. Informational [Page 1]\n\f\nRFC 4925 Softwire Problem Statement July 2007 4925 authentication authorization delivery management path trust nested-reference unchanged"},{"id":"IETF RFC 7039","type":"specification","body":"IETF","designation":"RFC 7039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7039.txt","https://www.rfc-editor.org/rfc/rfc7039.pdf"],"folder":"IETF/RFC-7039","files":{"txt":{"path":"standards/IETF/RFC-7039/RFC-7039.txt","sha256":"32b483bc348b7038a7369e4668a61abc9643951db237bd1bba2c6cd34d7a10b1"}},"tags":["nested-reference","unchanged"],"summary":"Source Address Validation Improvement (SAVI) methods were developed\n to prevent nodes attached to the same IP link from spoofing each\n other's IP addresses, so as to complement ingress filtering with\n finer-grained, standardized IP source address validation. This\n document is a framework document that describes and motivates the\n design of the SAVI methods. Particular SAVI methods are described in\n other documents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Sec","scope_keywords":["7039","delivery","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null},{"body":"IETF","designation":"RFC 8981","folder":"IETF/RFC-8981","source":"IETF/RFC-8981/RFC-8981.txt","version":null}],"search_text":"IETF RFC 7039 Source Address Validation Improvement (SAVI) methods were developed\n to prevent nodes attached to the same IP link from spoofing each\n other's IP addresses, so as to complement ingress filtering with\n finer-grained, standardized IP source address validation. This\n document is a framework document that describes and motivates the\n design of the SAVI methods. Particular SAVI methods are described in\n other documents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Sec 7039 delivery http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 7819","type":"specification","body":"IETF","designation":"RFC 7819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7819.txt","https://www.rfc-editor.org/rfc/rfc7819.pdf"],"folder":"IETF/RFC-7819","files":{"txt":{"path":"standards/IETF/RFC-7819/RFC-7819.txt","sha256":"7fdf309ef86b7dbd51633e4932c7a6c95f223016942aaab177723cdd27f398df"}},"tags":["nested-reference","unchanged"],"summary":"DHCP is a protocol that is used to provide addressing and\n configuration information to IPv4 hosts. This document discusses the\n various identifiers used by DHCP and the potential privacy issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7819.\n\nCopyright Notice\n\n Copyright (c) 2016 ","scope_keywords":["7819","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null}],"search_text":"IETF RFC 7819 DHCP is a protocol that is used to provide addressing and\n configuration information to IPv4 hosts. This document discusses the\n various identifiers used by DHCP and the potential privacy issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7819.\n\nCopyright Notice\n\n Copyright (c) 2016  7819 http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8293","type":"specification","body":"IETF","designation":"RFC 8293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8293.txt","https://www.rfc-editor.org/rfc/rfc8293.pdf"],"folder":"IETF/RFC-8293","files":{"txt":{"path":"standards/IETF/RFC-8293/RFC-8293.txt","sha256":"b91458463c442734b690623ed2f95437d2d4657d5fd9941e730417bcce5240dc"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for supporting multicast traffic\n in a network that uses Network Virtualization over Layer 3 (NVO3).\n Both infrastructure multicast and application-specific multicast are\n discussed. It describes the various mechanisms that can be used for\n delivering such traffic as well as the data plane and control plane\n considerations for each of the mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informati","scope_keywords":["8293","delivery","http","https","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null}],"search_text":"IETF RFC 8293 This document provides a framework for supporting multicast traffic\n in a network that uses Network Virtualization over Layer 3 (NVO3).\n Both infrastructure multicast and application-specific multicast are\n discussed. It describes the various mechanisms that can be used for\n delivering such traffic as well as the data plane and control plane\n considerations for each of the mechanisms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informati 8293 delivery http https license management subject trust nested-reference unchanged"},{"id":"IETF RFC 6355","type":"specification","body":"IETF","designation":"RFC 6355","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6355.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6355.txt","https://www.rfc-editor.org/rfc/rfc6355.pdf"],"folder":"IETF/RFC-6355","files":{"txt":{"path":"standards/IETF/RFC-6355/RFC-6355.txt","sha256":"cdade3611388016ab4f75b9a31eadc887af7eed29ff16d3ba36c444865f8eeab"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new DHCPv6 Unique Identifier (DUID) type\n called DUID-UUID. DUID-UUIDs are derived from the already-\n standardized Universally Unique IDentifier (UUID) format. DUID-UUID\n makes it possible for devices to use UUIDs to identify themselves to\n DHC servers and vice versa. UUIDs are globally unique and readily\n available on many systems, making them convenient identifiers to\n leverage within DHCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to","scope_keywords":["6355","http","license","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6355 This document defines a new DHCPv6 Unique Identifier (DUID) type\n called DUID-UUID. DUID-UUIDs are derived from the already-\n standardized Universally Unique IDentifier (UUID) format. DUID-UUID\n makes it possible for devices to use UUIDs to identify themselves to\n DHC servers and vice versa. UUIDs are globally unique and readily\n available on many systems, making them convenient identifiers to\n leverage within DHCP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to 6355 http license subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 3493","type":"specification","body":"IETF","designation":"RFC 3493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3493.txt","https://www.rfc-editor.org/rfc/rfc3493.pdf"],"folder":"IETF/RFC-3493","files":{"txt":{"path":"standards/IETF/RFC-3493/RFC-3493.txt","sha256":"51502b0f8395ff2f291b56842b856eb80610444061a28ce58174bf2f3551d0e8"}},"tags":["nested-reference","unchanged"],"summary":"The de facto standard Application Program Interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl","scope_keywords":["3493","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3542","folder":"IETF/RFC-3542","source":"IETF/RFC-3542/RFC-3542.txt","version":null},{"body":"IETF","designation":"RFC 3582","folder":"IETF/RFC-3582","source":"IETF/RFC-3582/RFC-3582.txt","version":null},{"body":"IETF","designation":"RFC 3678","folder":"IETF/RFC-3678","source":"IETF/RFC-3678/RFC-3678.txt","version":null},{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 4007","folder":"IETF/RFC-4007","source":"IETF/RFC-4007/RFC-4007.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4584","folder":"IETF/RFC-4584","source":"IETF/RFC-4584/RFC-4584.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5014","folder":"IETF/RFC-5014","source":"IETF/RFC-5014/RFC-5014.txt","version":null},{"body":"IETF","designation":"RFC 5221","folder":"IETF/RFC-5221","source":"IETF/RFC-5221/RFC-5221.txt","version":null},{"body":"IETF","designation":"RFC 5338","folder":"IETF/RFC-5338","source":"IETF/RFC-5338/RFC-5338.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6535","folder":"IETF/RFC-6535","source":"IETF/RFC-6535/RFC-6535.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6943","folder":"IETF/RFC-6943","source":"IETF/RFC-6943/RFC-6943.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 3493 The de facto standard Application Program Interface (API) for TCP/IP\n applications is the \"sockets\" interface. Although this API was\n developed for Unix in the early 1980s it has also been implemented on\n a wide variety of non-Unix systems. TCP/IP applications written\n using the sockets API have in the past enjoyed a high degree of\n portability and we would like the same portability with IPv6\n applications. But changes are required to the sockets API to support\n IPv6 and this memo describes these changes. These include a new\n socket address structure to carry IPv6 addresses, new address\n conversion functions, and some new socket options. These extensions\n are designed to provide access to the basic IPv6 features required by\n TCP and UDP applications, including multicasting, while introducing a\n minimum of change into the system and providing complete\n compatibility for existing IPv4 appl 3493 identification nested-reference unchanged"},{"id":"IETF RFC 4038","type":"specification","body":"IETF","designation":"RFC 4038","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4038.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4038.txt","https://www.rfc-editor.org/rfc/rfc4038.pdf"],"folder":"IETF/RFC-4038","files":{"txt":{"path":"standards/IETF/RFC-4038/RFC-4038.txt","sha256":"10494949f6cd6557b518cfcb376aa45d187e180892db1b02960ac9abc037c31c"}},"tags":["nested-reference","unchanged"],"summary":"As IPv6 networks are deployed and the network transition is\n discussed, one should also consider how to enable IPv6 support in\n applications running on IPv6 hosts, and the best strategy to develop\n IP protocol support in applications. This document specifies\n scenarios and aspects of application transition. It also proposes\n guidelines on how to develop IP version-independent applications\n during the transition period.\n\nShin, Ed., et al. Informational [Page 1]\n\f\nRFC 4038 Application Aspects of IPv6 Transition March 2005","scope_keywords":["4038","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4057","folder":"IETF/RFC-4057","source":"IETF/RFC-4057/RFC-4057.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5952","folder":"IETF/RFC-5952","source":"IETF/RFC-5952/RFC-5952.txt","version":null},{"body":"IETF","designation":"RFC 6157","folder":"IETF/RFC-6157","source":"IETF/RFC-6157/RFC-6157.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 4038 As IPv6 networks are deployed and the network transition is\n discussed, one should also consider how to enable IPv6 support in\n applications running on IPv6 hosts, and the best strategy to develop\n IP protocol support in applications. This document specifies\n scenarios and aspects of application transition. It also proposes\n guidelines on how to develop IP version-independent applications\n during the transition period.\n\nShin, Ed., et al. Informational [Page 1]\n\f\nRFC 4038 Application Aspects of IPv6 Transition March 2005 4038 key presentation nested-reference unchanged"},{"id":"IETF RFC 4423","type":"specification","body":"IETF","designation":"RFC 4423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4423.txt","https://www.rfc-editor.org/rfc/rfc4423.pdf"],"folder":"IETF/RFC-4423","files":{"txt":{"path":"standards/IETF/RFC-4423/RFC-4423.txt","sha256":"7af02aabb776b9335ca39d79e94a3121395738807071d81be030cd5ef02bd934"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a snapshot of the reasoning behind a proposed new\n namespace, the Host Identity namespace, and a new protocol layer, the\n Host Identity Protocol (HIP), between the internetworking and\n transport layers. Herein are presented the basics of the current\n namespaces, their strengths and weaknesses, and how a new namespace\n will add completeness to them. The roles of this new namespace in\n the protocols are defined. The memo describes the thinking of the\n authors as of Fall 2003. The architecture may have evolved since.\n This document represents one stable point in that evolution of\n understanding.","scope_keywords":["4423","authentication","identification","key","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5164","folder":"IETF/RFC-5164","source":"IETF/RFC-5164/RFC-5164.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5202","folder":"IETF/RFC-5202","source":"IETF/RFC-5202/RFC-5202.txt","version":null},{"body":"IETF","designation":"RFC 5203","folder":"IETF/RFC-5203","source":"IETF/RFC-5203/RFC-5203.txt","version":null},{"body":"IETF","designation":"RFC 5204","folder":"IETF/RFC-5204","source":"IETF/RFC-5204/RFC-5204.txt","version":null},{"body":"IETF","designation":"RFC 5205","folder":"IETF/RFC-5205","source":"IETF/RFC-5205/RFC-5205.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5207","folder":"IETF/RFC-5207","source":"IETF/RFC-5207/RFC-5207.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6281","folder":"IETF/RFC-6281","source":"IETF/RFC-6281/RFC-6281.txt","version":null},{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6317","folder":"IETF/RFC-6317","source":"IETF/RFC-6317/RFC-6317.txt","version":null}],"search_text":"IETF RFC 4423 This memo describes a snapshot of the reasoning behind a proposed new\n namespace, the Host Identity namespace, and a new protocol layer, the\n Host Identity Protocol (HIP), between the internetworking and\n transport layers. Herein are presented the basics of the current\n namespaces, their strengths and weaknesses, and how a new namespace\n will add completeness to them. The roles of this new namespace in\n the protocols are defined. The memo describes the thinking of the\n authors as of Fall 2003. The architecture may have evolved since.\n This document represents one stable point in that evolution of\n understanding. 4423 authentication identification key policies trust nested-reference unchanged"},{"id":"IETF RFC 5158","type":"specification","body":"IETF","designation":"RFC 5158","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5158.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5158.txt","https://www.rfc-editor.org/rfc/rfc5158.pdf"],"folder":"IETF/RFC-5158","files":{"txt":{"path":"standards/IETF/RFC-5158/RFC-5158.txt","sha256":"c65af96e5f93cef291af35cb837ae05a046b55513d230b33fe529b49432bd5e4"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes the service mechanism for entering a delegation\n of DNS servers that provide reverse lookup of 6to4 IPv6 addresses\n into the 6to4 reverse zone file. The mechanism is based on a\n conventional DNS delegation service interface, allowing the service\n client to enter the details of a number of DNS servers for the\n delegated domain. In the context of a 6to4 reverse delegation, the\n client is primarily authenticated by its source address used in the\n delegation request, and is authorized to use the function if its IPv6\n address prefix corresponds to an address from within the requested\n 6to4 delegation address block.\n\nHuston Informational [Page 1]\n\f\nRFC 5158 6to4 Reverse DNS March 2008\n\n1. Introduction\n\n 6to4 [RFC3056] defines a mechanism for allowing isolated IPv6 sites\n to communicate using IPv6 over the public IPv4 Internet. This is\n achieved through the use of a dedicate","scope_keywords":["5158","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 5158 This memo describes the service mechanism for entering a delegation\n of DNS servers that provide reverse lookup of 6to4 IPv6 addresses\n into the 6to4 reverse zone file. The mechanism is based on a\n conventional DNS delegation service interface, allowing the service\n client to enter the details of a number of DNS servers for the\n delegated domain. In the context of a 6to4 reverse delegation, the\n client is primarily authenticated by its source address used in the\n delegation request, and is authorized to use the function if its IPv6\n address prefix corresponds to an address from within the requested\n 6to4 delegation address block.\n\nHuston Informational [Page 1]\n\f\nRFC 5158 6to4 Reverse DNS March 2008\n\n1. Introduction\n\n 6to4 [RFC3056] defines a mechanism for allowing isolated IPv6 sites\n to communicate using IPv6 over the public IPv4 Internet. This is\n achieved through the use of a dedicate 5158 path nested-reference unchanged"},{"id":"IETF RFC 6853","type":"specification","body":"IETF","designation":"RFC 6853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6853.txt","https://www.rfc-editor.org/rfc/rfc6853.pdf"],"folder":"IETF/RFC-6853","files":{"txt":{"path":"standards/IETF/RFC-6853/RFC-6853.txt","sha256":"8e41281c501b5f0f44781c78255961999cd3f6caa1c9f51e87d53df36d2c8547"}},"tags":["nested-reference","unchanged"],"summary":"This document provides information for those wishing to use DHCPv6 to\n support their deployment of IPv6. In particular, it discusses the\n provision of semi-redundant DHCPv6 services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6853.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP ","scope_keywords":["6853","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7031","folder":"IETF/RFC-7031","source":"IETF/RFC-7031/RFC-7031.txt","version":null}],"search_text":"IETF RFC 6853 This document provides information for those wishing to use DHCPv6 to\n support their deployment of IPv6. In particular, it discusses the\n provision of semi-redundant DHCPv6 services.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6853.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP  6853 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7031","type":"specification","body":"IETF","designation":"RFC 7031","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7031.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7031.txt","https://www.rfc-editor.org/rfc/rfc7031.pdf"],"folder":"IETF/RFC-7031","files":{"txt":{"path":"standards/IETF/RFC-7031/RFC-7031.txt","sha256":"251d952df0c900f7170096713e5177f42df5ff38954d2d45cbbd64612d62cbb0"}},"tags":["nested-reference","unchanged"],"summary":"The DHCPv6 protocol, defined in RFC 3315, allows for multiple servers\n to operate on a single network; however, it does not define any way\n the servers could share information about currently active clients\n and their leases. Some sites are interested in running multiple\n servers in such a way as to provide increased availability in case of\n server failure. In order for this to work reliably, the cooperating\n primary and secondary servers must maintain a consistent database of\n the lease information. RFC 3315 allows for, but does not define, any\n redundancy or failover mechanisms. This document outlines\n requirements for DHCPv6 failover, enumerates related problems, and\n discusses the proposed scope of work to be conducted. This document\n does not define a DHCPv6 failover protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for","scope_keywords":["7031","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8156","folder":"IETF/RFC-8156","source":"IETF/RFC-8156/RFC-8156.txt","version":null}],"search_text":"IETF RFC 7031 The DHCPv6 protocol, defined in RFC 3315, allows for multiple servers\n to operate on a single network; however, it does not define any way\n the servers could share information about currently active clients\n and their leases. Some sites are interested in running multiple\n servers in such a way as to provide increased availability in case of\n server failure. In order for this to work reliably, the cooperating\n primary and secondary servers must maintain a consistent database of\n the lease information. RFC 3315 allows for, but does not define, any\n redundancy or failover mechanisms. This document outlines\n requirements for DHCPv6 failover, enumerates related problems, and\n discusses the proposed scope of work to be conducted. This document\n does not define a DHCPv6 failover protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for 7031 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7824","type":"specification","body":"IETF","designation":"RFC 7824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7824.txt","https://www.rfc-editor.org/rfc/rfc7824.pdf"],"folder":"IETF/RFC-7824","files":{"txt":{"path":"standards/IETF/RFC-7824/RFC-7824.txt","sha256":"cf6ca8f2cd2a439a13190cf0fe3def7b9ac78ed43a92e730726c0fca63e963fd"}},"tags":["nested-reference","unchanged"],"summary":"DHCPv6 is a protocol that is used to provide addressing and\n configuration information to IPv6 hosts. This document describes the\n privacy issues associated with the use of DHCPv6 by Internet users.\n It is intended to be an analysis of the present situation and does\n not propose any solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ","scope_keywords":["7824","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7844","folder":"IETF/RFC-7844","source":"IETF/RFC-7844/RFC-7844.txt","version":null},{"body":"IETF","designation":"RFC 7969","folder":"IETF/RFC-7969","source":"IETF/RFC-7969/RFC-7969.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 7824 DHCPv6 is a protocol that is used to provide addressing and\n configuration information to IPv6 hosts. This document describes the\n privacy issues associated with the use of DHCPv6 by Internet users.\n It is intended to be an analysis of the present situation and does\n not propose any solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it  7824 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2882","type":"specification","body":"IETF","designation":"RFC 2882","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2882.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2882.txt","https://www.rfc-editor.org/rfc/rfc2882.pdf"],"folder":"IETF/RFC-2882","files":{"txt":{"path":"standards/IETF/RFC-2882/RFC-2882.txt","sha256":"1df80372daab08d7c438d9240b3a2df48030a2434d02207b4d751032ac9398f8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes current practices implemented in NAS products\n that go beyond the scope of the RADIUS RFCs 2138, 2139 [1,2]. The\n purpose of this effort is to give examples that show the need for\n addressing and standardizing these types of ad-hoc functions. Since\n many of these features require a matching server support component,\n the ability to deploy and manage interoperable NAS and AAA server\n products is severely hindered.\n\n These practices are documented here to show functions that are\n obviously desired in developing future AAA protocols for NAS\n deployment.","scope_keywords":["2882","attribute","attributes","audit","authentication","authorization","management","policy","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2989","folder":"IETF/RFC-2989","source":"IETF/RFC-2989/RFC-2989.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3575","folder":"IETF/RFC-3575","source":"IETF/RFC-3575/RFC-3575.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null}],"search_text":"IETF RFC 2882 This document describes current practices implemented in NAS products\n that go beyond the scope of the RADIUS RFCs 2138, 2139 [1,2]. The\n purpose of this effort is to give examples that show the need for\n addressing and standardizing these types of ad-hoc functions. Since\n many of these features require a matching server support component,\n the ability to deploy and manage interoperable NAS and AAA server\n products is severely hindered.\n\n These practices are documented here to show functions that are\n obviously desired in developing future AAA protocols for NAS\n deployment. 2882 attribute attributes audit authentication authorization management policy presentation subject nested-reference unchanged"},{"id":"IETF RFC 2140","type":"specification","body":"IETF","designation":"RFC 2140","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2140.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2140.txt","https://www.rfc-editor.org/rfc/rfc2140.pdf"],"folder":"IETF/RFC-2140","files":{"txt":{"path":"standards/IETF/RFC-2140/RFC-2140.txt","sha256":"3a6cc93711e124c82d38e19fcc77974cbe59ecc6c0451c9e1bb12b5ab077d471"}},"tags":["nested-reference","unchanged"],"summary":"This memo makes the case for interdependent TCP control blocks, where\n part of the TCP state is shared among similar concurrent connections,\n or across similar connection instances. TCP state includes a\n combination of parameters, such as connection state, current round-\n trip time estimates, congestion control information, and process\n information. This state is currently maintained on a per-connection\n basis in the TCP control block, but should be shared across\n connections to the same host. The goal is to improve transient\n transport performance, while maintaining backward-compatibility with\n existing implementations.\n\n This document is a product of the LSAM project at ISI.","scope_keywords":["2140","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6269","folder":"IETF/RFC-6269","source":"IETF/RFC-6269/RFC-6269.txt","version":null},{"body":"IETF","designation":"RFC 6323","folder":"IETF/RFC-6323","source":"IETF/RFC-6323/RFC-6323.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2140 This memo makes the case for interdependent TCP control blocks, where\n part of the TCP state is shared among similar concurrent connections,\n or across similar connection instances. TCP state includes a\n combination of parameters, such as connection state, current round-\n trip time estimates, congestion control information, and process\n information. This state is currently maintained on a per-connection\n basis in the TCP control block, but should be shared across\n connections to the same host. The goal is to improve transient\n transport performance, while maintaining backward-compatibility with\n existing implementations.\n\n This document is a product of the LSAM project at ISI. 2140 delivery nested-reference unchanged"},{"id":"IETF RFC 2648","type":"specification","body":"IETF","designation":"RFC 2648","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2648.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2648.txt","https://www.rfc-editor.org/rfc/rfc2648.pdf"],"folder":"IETF/RFC-2648","files":{"txt":{"path":"standards/IETF/RFC-2648/RFC-2648.txt","sha256":"d219ae397c409300de0cde64ca3fbc0c80eec810950e8ea88db89479eb63b527"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Moats\nRequest for Comments: 2648 AT&T\nCategory: Informational August 1999\n\n A URN Namespace for IETF Documents\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n A system for Uniform Resource Names (URNs) must be capable of\n supporting new naming systems. As an example of proposing a new\n namespace, this document proposes the \"ietf\" namespace. This\n namespace consists of the RFC family of documents (RFCs, STDs, FYIs,\n and BCPs) developed by the IETF and published by the RFC Editor, the\n minutes of working groups (WG) and birds of a feather (BOF) meetings\n that occur during IETF conferences, and the Internet Drafts published\n by the Internet Dra","scope_keywords":["2648","http","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3680","folder":"IETF/RFC-3680","source":"IETF/RFC-3680/RFC-3680.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4482","folder":"IETF/RFC-4482","source":"IETF/RFC-4482/RFC-4482.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4826","folder":"IETF/RFC-4826","source":"IETF/RFC-4826/RFC-4826.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 2648 Network Working Group R. Moats\nRequest for Comments: 2648 AT&T\nCategory: Informational August 1999\n\n A URN Namespace for IETF Documents\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n A system for Uniform Resource Names (URNs) must be capable of\n supporting new naming systems. As an example of proposing a new\n namespace, this document proposes the \"ietf\" namespace. This\n namespace consists of the RFC family of documents (RFCs, STDs, FYIs,\n and BCPs) developed by the IETF and published by the RFC Editor, the\n minutes of working groups (WG) and birds of a feather (BOF) meetings\n that occur during IETF conferences, and the Internet Drafts published\n by the Internet Dra 2648 http validation nested-reference unchanged"},{"id":"IETF RFC 3043","type":"specification","body":"IETF","designation":"RFC 3043","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3043.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3043.txt","https://www.rfc-editor.org/rfc/rfc3043.pdf"],"folder":"IETF/RFC-3043","files":{"txt":{"path":"standards/IETF/RFC-3043/RFC-3043.txt","sha256":"8fe9264782c6d310803dd4c33e20b407a960d0b67d26e3d8ec0a01268f437b04"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Mealling\nRequest for Comments: 3043 Network Solutions, Inc.\nCategory: Informational January 2001\n\n The Network Solutions Personal Internet Name (PIN): A URN Namespace\n for People and Organizations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace that\n is engineered by Network Solutions, Inc. for naming people and\n organizations.\n\n1. Introduction\n\n In many cases Network Solutions' maintained directory applications\n require some unique and persistent way to talk about an individual or\n organization. For example, white pages style services need to\n determine if one entry is distinct","scope_keywords":["3043","algorithm","authentication","http","identification","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 3043 Network Working Group M. Mealling\nRequest for Comments: 3043 Network Solutions, Inc.\nCategory: Informational January 2001\n\n The Network Solutions Personal Internet Name (PIN): A URN Namespace\n for People and Organizations\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace that\n is engineered by Network Solutions, Inc. for naming people and\n organizations.\n\n1. Introduction\n\n In many cases Network Solutions' maintained directory applications\n require some unique and persistent way to talk about an individual or\n organization. For example, white pages style services need to\n determine if one entry is distinct 3043 algorithm authentication http identification presentation validation nested-reference unchanged"},{"id":"IETF RFC 3084","type":"specification","body":"IETF","designation":"RFC 3084","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3084.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3084.txt","https://www.rfc-editor.org/rfc/rfc3084.pdf"],"folder":"IETF/RFC-3084","files":{"txt":{"path":"standards/IETF/RFC-3084/RFC-3084.txt","sha256":"f3e49a2e1bb907069614571ddb0942b72fe17a468b4c8dc24d194a97a2f0171f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the Common Open Policy Service\n (COPS) protocol for support of policy provisioning (COPS-PR). This\n specification is independent of the type of policy being provisioned\n (QoS, Security, etc.) but focuses on the mechanisms and conventions\n used to communicate provisioned information between PDPs and PEPs.\n The protocol extensions described in this document do not make any\n assumptions about the policy data model being communicated, but\n describe the message formats and objects that carry the modeled\n policy data.\n\nChan, et al. Standards Track [Page 1]\n\f\nRFC 3084 COPS-PR March 2001\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC-2119].","scope_keywords":["3084","attribute","attributes","authorization","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3139","folder":"IETF/RFC-3139","source":"IETF/RFC-3139/RFC-3139.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3216","folder":"IETF/RFC-3216","source":"IETF/RFC-3216/RFC-3216.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3535","folder":"IETF/RFC-3535","source":"IETF/RFC-3535/RFC-3535.txt","version":null},{"body":"IETF","designation":"RFC 3585","folder":"IETF/RFC-3585","source":"IETF/RFC-3585/RFC-3585.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4097","folder":"IETF/RFC-4097","source":"IETF/RFC-4097/RFC-4097.txt","version":null},{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3084 This document describes the use of the Common Open Policy Service\n (COPS) protocol for support of policy provisioning (COPS-PR). This\n specification is independent of the type of policy being provisioned\n (QoS, Security, etc.) but focuses on the mechanisms and conventions\n used to communicate provisioned information between PDPs and PEPs.\n The protocol extensions described in this document do not make any\n assumptions about the policy data model being communicated, but\n describe the message formats and objects that carry the modeled\n policy data.\n\nChan, et al. Standards Track [Page 1]\n\f\nRFC 3084 COPS-PR March 2001\n\nConventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC-2119]. 3084 attribute attributes authorization key policy nested-reference unchanged"},{"id":"IETF RFC 3085","type":"specification","body":"IETF","designation":"RFC 3085","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3085.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3085.txt","https://www.rfc-editor.org/rfc/rfc3085.pdf"],"folder":"IETF/RFC-3085","files":{"txt":{"path":"standards/IETF/RFC-3085/RFC-3085.txt","sha256":"01916eaf2cab3f52632815f0811855cbea15654a4909c6099320f62d34a29ce3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Coates\nRequest for Comments: 3085 Reuters\nCategory: Informational D. Allen\n IPTC\n D. Rivers-Moore\n Rivcom\n March 2001\n\n URN Namespace for NewsML Resources\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace for\n identifying NewsML NewsItems. A NewsItem is an information resource\n that is expressible as a NewsML element within a NewsML document\n conforming to the NewsML Document Type Declaration (DTD) as defined\n by the International Press Telecommunications Council (IPTC).\n\n1. Introduction\n\n NewsML is an XML format for packaging multimedia news resources. It\n has been created under ","scope_keywords":["3085","http","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null}],"search_text":"IETF RFC 3085 Network Working Group A. Coates\nRequest for Comments: 3085 Reuters\nCategory: Informational D. Allen\n IPTC\n D. Rivers-Moore\n Rivcom\n March 2001\n\n URN Namespace for NewsML Resources\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace for\n identifying NewsML NewsItems. A NewsItem is an information resource\n that is expressible as a NewsML element within a NewsML document\n conforming to the NewsML Document Type Declaration (DTD) as defined\n by the International Press Telecommunications Council (IPTC).\n\n1. Introduction\n\n NewsML is an XML format for packaging multimedia news resources. It\n has been created under  3085 http management validation nested-reference unchanged"},{"id":"IETF RFC 3120","type":"specification","body":"IETF","designation":"RFC 3120","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3120.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3120.txt","https://www.rfc-editor.org/rfc/rfc3120.pdf"],"folder":"IETF/RFC-3120","files":{"txt":{"path":"standards/IETF/RFC-3120/RFC-3120.txt","sha256":"08964f6bdd6b30b59cfffbd66fd65c74398e27e6e24c60d4a83fba1e405069a1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Best\nRequest for Comments: 3120 OASIS, Inc.\nCategory: Informational N. Walsh\n Sun Microsystems, Inc.\n June 2001\n\n A URN Namespace for XML.org\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace that\n is engineered by the Organization for the Advancement of Structured\n Information Standards (OASIS) for naming persistent resources stored\n in the XML.org repository (such as XML (Extensible Markup Language)\n Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and\n other documents).\n\n1. Introduction\n\n The XML.org Registry is provided by XML.org as a public service where\n XML","scope_keywords":["3120","http","management","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 3120 Network Working Group K. Best\nRequest for Comments: 3120 OASIS, Inc.\nCategory: Informational N. Walsh\n Sun Microsystems, Inc.\n June 2001\n\n A URN Namespace for XML.org\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace that\n is engineered by the Organization for the Advancement of Structured\n Information Standards (OASIS) for naming persistent resources stored\n in the XML.org repository (such as XML (Extensible Markup Language)\n Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and\n other documents).\n\n1. Introduction\n\n The XML.org Registry is provided by XML.org as a public service where\n XML 3120 http management validation nested-reference unchanged"},{"id":"IETF RFC 3121","type":"specification","body":"IETF","designation":"RFC 3121","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3121.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3121.txt","https://www.rfc-editor.org/rfc/rfc3121.pdf"],"folder":"IETF/RFC-3121","files":{"txt":{"path":"standards/IETF/RFC-3121/RFC-3121.txt","sha256":"a896890ea5faf58e3892b95cbd99d3971d6bbe063169544e19000567209faff1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Best\nRequest for Comments: 3121 OASIS, Inc.\nCategory: Informational N. Walsh\n Sun Microsystems, Inc.\n June 2001\n\n A URN Namespace for OASIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace that\n is engineered by the Organization for the Advancement of Structured\n Information Standards (OASIS) for naming persistent resources\n published by OASIS (such as OASIS Standards, XML (Extensible Markup\n Language) Document Type Definitions, XML Schemas, Namespaces,\n Stylesheets, and other documents).\n\n1. Introduction\n\n The Organization for the Advancement of Structured Information\n Standards","scope_keywords":["3121","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null}],"search_text":"IETF RFC 3121 Network Working Group K. Best\nRequest for Comments: 3121 OASIS, Inc.\nCategory: Informational N. Walsh\n Sun Microsystems, Inc.\n June 2001\n\n A URN Namespace for OASIS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This document describes a URN (Uniform Resource Name) namespace that\n is engineered by the Organization for the Advancement of Structured\n Information Standards (OASIS) for naming persistent resources\n published by OASIS (such as OASIS Standards, XML (Extensible Markup\n Language) Document Type Definitions, XML Schemas, Namespaces,\n Stylesheets, and other documents).\n\n1. Introduction\n\n The Organization for the Advancement of Structured Information\n Standards 3121 validation nested-reference unchanged"},{"id":"IETF RFC 3151","type":"specification","body":"IETF","designation":"RFC 3151","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3151.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3151.txt","https://www.rfc-editor.org/rfc/rfc3151.pdf"],"folder":"IETF/RFC-3151","files":{"txt":{"path":"standards/IETF/RFC-3151/RFC-3151.txt","sha256":"61a64155a07c01de9b93c80c6b4dd72b6ccc2478cd48635f489ba0860adb780e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a URN (Uniform Resource Name) namespace that\n is designed to allow Public Identifiers to be expressed in URI\n (Uniform Resource Identifiers) syntax.\n\n1. Introduction\n\n XML [1] external entities have two identifiers: a system identifier\n and a public identifier. The system identifier is a URI, by\n definition, but the public identifier is simply a string.\n\n Historically, the system identifier of an external entity has been a\n local, or system-specific identifier while the public identifier has\n been a more global, persistent name.\n\n Unfortunately, public identifiers do not fit neatly into the existing\n web architecture because they are not legal URIs. Many new\n specifications (XSLT, XML Schema, etc.) have the implicit or explicit\n requirement that all external identifiers be URIs.\n\n The purpose of this namespace is to allow public identifiers to be\n encoded in URNs ","scope_keywords":["3151","algorithm","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3688","folder":"IETF/RFC-3688","source":"IETF/RFC-3688/RFC-3688.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"IETF RFC 3151 This document describes a URN (Uniform Resource Name) namespace that\n is designed to allow Public Identifiers to be expressed in URI\n (Uniform Resource Identifiers) syntax.\n\n1. Introduction\n\n XML [1] external entities have two identifiers: a system identifier\n and a public identifier. The system identifier is a URI, by\n definition, but the public identifier is simply a string.\n\n Historically, the system identifier of an external entity has been a\n local, or system-specific identifier while the public identifier has\n been a more global, persistent name.\n\n Unfortunately, public identifiers do not fit neatly into the existing\n web architecture because they are not legal URIs. Many new\n specifications (XSLT, XML Schema, etc.) have the implicit or explicit\n requirement that all external identifiers be URIs.\n\n The purpose of this namespace is to allow public identifiers to be\n encoded in URNs  3151 algorithm registered nested-reference unchanged"},{"id":"IETF RFC 3187","type":"specification","body":"IETF","designation":"RFC 3187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3187.txt","https://www.rfc-editor.org/rfc/rfc3187.pdf"],"folder":"IETF/RFC-3187","files":{"txt":{"path":"standards/IETF/RFC-3187/RFC-3187.txt","sha256":"bd1a384b7d742932f348b49babc3725bcc26e53edf1a1e19505c3c39fb2796ff"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how International Standard Book Numbers\n (ISBN) can be supported within the URN (Uniform Resource Names)\n framework and the syntax for URNs defined in RFC 2141. Much of the\n discussion below is based on the ideas expressed in RFC 2288.\n\n1. Introduction\n\n As part of the validation process for the development of URNs, the\n IETF URN working group agreed that it is important to demonstrate\n that the current URN syntax proposal can accommodate existing\n identifiers from well established namespaces. One such\n infrastructure for assigning and managing names comes from the\n bibliographic community. Bibliographic identifiers function as names\n for objects that exist both in print and, increasingly, in electronic\n formats. RFC 2288 [Lynch, et al.] investigated the feasibility of\n using three identifiers (ISBN, ISSN and SICI) as URNs. This document\n will analyse the usage of","scope_keywords":["3187","http","identification","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 3187 This document discusses how International Standard Book Numbers\n (ISBN) can be supported within the URN (Uniform Resource Names)\n framework and the syntax for URNs defined in RFC 2141. Much of the\n discussion below is based on the ideas expressed in RFC 2288.\n\n1. Introduction\n\n As part of the validation process for the development of URNs, the\n IETF URN working group agreed that it is important to demonstrate\n that the current URN syntax proposal can accommodate existing\n identifiers from well established namespaces. One such\n infrastructure for assigning and managing names comes from the\n bibliographic community. Bibliographic identifiers function as names\n for objects that exist both in print and, increasingly, in electronic\n formats. RFC 2288 [Lynch, et al.] investigated the feasibility of\n using three identifiers (ISBN, ISSN and SICI) as URNs. This document\n will analyse the usage of 3187 http identification validation nested-reference unchanged"},{"id":"IETF RFC 4179","type":"specification","body":"IETF","designation":"RFC 4179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4179.txt","https://www.rfc-editor.org/rfc/rfc4179.pdf"],"folder":"IETF/RFC-4179","files":{"txt":{"path":"standards/IETF/RFC-4179/RFC-4179.txt","sha256":"adb649f11f7c4bc218d7d122c6cbadc480a4393e8e976b84c3e7a9984a7a78a7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Kang\nRequest for Comments: 4179 National Computerization Agency\nCategory: Informational October 2005\n\n Using Universal Content Identifier (UCI)\n as Uniform Resource Names (URN)\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace for\n the National Computerization Agency (NCA) for naming persistent\n digital resources such as music, videos, texts, images, e-books, and\n other types of digital resources produced or managed by NCA.\n\n1. Introduction\n\n NCA is a non-profit organization with a mandate to develop and\n promote information infrastructure and manage public digital contents\n in Korea and possibly worl","scope_keywords":["4179","http","registered","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 4179 Network Working Group S. Kang\nRequest for Comments: 4179 National Computerization Agency\nCategory: Informational October 2005\n\n Using Universal Content Identifier (UCI)\n as Uniform Resource Names (URN)\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace for\n the National Computerization Agency (NCA) for naming persistent\n digital resources such as music, videos, texts, images, e-books, and\n other types of digital resources produced or managed by NCA.\n\n1. Introduction\n\n NCA is a non-profit organization with a mandate to develop and\n promote information infrastructure and manage public digital contents\n in Korea and possibly worl 4179 http registered validation nested-reference unchanged"},{"id":"IETF RFC 4195","type":"specification","body":"IETF","designation":"RFC 4195","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4195.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4195.txt","https://www.rfc-editor.org/rfc/rfc4195.pdf"],"folder":"IETF/RFC-4195","files":{"txt":{"path":"standards/IETF/RFC-4195/RFC-4195.txt","sha256":"d2ec27af6bf580955e120b138ada9abba4f5ddc42de682fa0c636d407bdb4eb7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Kameyama\nRequest for Comments: 4195 GITS, Waseda University\nCategory: Informational October 2005\n\n A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace that\n is engineered by the TV-Anytime Forum for naming persistent resources\n published by the TV-Anytime Forum including the TV-Anytime Forum\n Standards, XML (Extensible Markup Language) Document Type\n Definitions, XML Schemas, Namespaces, and other documents.\n\n1. Introduction\n\n The TV-Anytime Forum produces many kinds of documents (i.e.,\n specifications, working documents, and schemas) that","scope_keywords":["4195","registered","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 4195 Network Working Group W. Kameyama\nRequest for Comments: 4195 GITS, Waseda University\nCategory: Informational October 2005\n\n A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document describes a Uniform Resource Name (URN) namespace that\n is engineered by the TV-Anytime Forum for naming persistent resources\n published by the TV-Anytime Forum including the TV-Anytime Forum\n Standards, XML (Extensible Markup Language) Document Type\n Definitions, XML Schemas, Namespaces, and other documents.\n\n1. Introduction\n\n The TV-Anytime Forum produces many kinds of documents (i.e.,\n specifications, working documents, and schemas) that 4195 registered validation nested-reference unchanged"},{"id":"IETF RFC 4854","type":"specification","body":"IETF","designation":"RFC 4854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4854.txt","https://www.rfc-editor.org/rfc/rfc4854.pdf"],"folder":"IETF/RFC-4854","files":{"txt":{"path":"standards/IETF/RFC-4854/RFC-4854.txt","sha256":"25718cfccd7cafc1ce9e5876985779b823daae242d7520a70da84447f6896376"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Name (URN) namespace for\n uniquely identifying Extensible Markup Language (XML) formats and\n protocols that provide extensions to the Extensible Messaging and\n Presence Protocol (XMPP) and are defined in specifications published\n by the XMPP Standards Foundation (XSF).\n\nSaint-Andre Informational [Page 1]\n\f\nRFC 4854 URN Namespace for XMPP Extensions April 2007","scope_keywords":["4854","http","key","management","qualified","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"IETF RFC 4854 This document describes a Uniform Resource Name (URN) namespace for\n uniquely identifying Extensible Markup Language (XML) formats and\n protocols that provide extensions to the Extensible Messaging and\n Presence Protocol (XMPP) and are defined in specifications published\n by the XMPP Standards Foundation (XSF).\n\nSaint-Andre Informational [Page 1]\n\f\nRFC 4854 URN Namespace for XMPP Extensions April 2007 4854 http key management qualified registered trust nested-reference unchanged"},{"id":"IETF RFC 5141","type":"specification","body":"IETF","designation":"RFC 5141","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5141.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5141.txt","https://www.rfc-editor.org/rfc/rfc5141.pdf"],"folder":"IETF/RFC-5141","files":{"txt":{"path":"standards/IETF/RFC-5141/RFC-5141.txt","sha256":"cdfc8c2337bb73d5aa515080856763bb6e5ddae85fb62f14e5e82fb56372a1e0"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Name Namespace\n Identification (URN NID) for the International Organization for\n Standardization (ISO). This URN NID is intended for use for the\n identification of persistent resources published by the ISO standards\n body (including documents, document metadata, extracted resources\n such as standard schemata and standard value sets, and other\n resources).\n\nGoodwin & Apel Informational [Page 1]\n\f\nRFC 5141 ISO URN Schema March 2008","scope_keywords":["5141","holder","http","identification","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"IETF RFC 5141 This document describes a Uniform Resource Name Namespace\n Identification (URN NID) for the International Organization for\n Standardization (ISO). This URN NID is intended for use for the\n identification of persistent resources published by the ISO standards\n body (including documents, document metadata, extracted resources\n such as standard schemata and standard value sets, and other\n resources).\n\nGoodwin & Apel Informational [Page 1]\n\f\nRFC 5141 ISO URN Schema March 2008 5141 holder http identification validation nested-reference unchanged"},{"id":"IETF RFC 6755","type":"specification","body":"IETF","designation":"RFC 6755","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6755.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6755.txt","https://www.rfc-editor.org/rfc/rfc6755.pdf"],"folder":"IETF/RFC-6755","files":{"txt":{"path":"standards/IETF/RFC-6755/RFC-6755.txt","sha256":"234e7af0f899d96ab67fc0284fd51aa1e52992f7e250225cbc6ad0cf9e2f16b1"}},"tags":["nested-reference","unchanged"],"summary":"This document establishes an IETF URN Sub-namespace for use with\n OAuth-related specifications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6755.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document","scope_keywords":["6755","authorization","http","license","presentation","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7522","folder":"IETF/RFC-7522","source":"IETF/RFC-7522/RFC-7522.txt","version":null},{"body":"IETF","designation":"RFC 7523","folder":"IETF/RFC-7523","source":"IETF/RFC-7523/RFC-7523.txt","version":null},{"body":"IETF","designation":"RFC 8628","folder":"IETF/RFC-8628","source":"IETF/RFC-8628/RFC-8628.txt","version":null},{"body":"IETF","designation":"RFC 8693","folder":"IETF/RFC-8693","source":"IETF/RFC-8693/RFC-8693.txt","version":null},{"body":"IETF","designation":"RFC 9126","folder":"IETF/RFC-9126","source":"IETF/RFC-9126/RFC-9126.txt","version":null}],"search_text":"IETF RFC 6755 This document establishes an IETF URN Sub-namespace for use with\n OAuth-related specifications.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6755.\n\nCopyright Notice\n\n Copyright (c) 2012 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document 6755 authorization http license presentation registered subject trust nested-reference unchanged"},{"id":"IETF RFC 2143","type":"specification","body":"IETF","designation":"RFC 2143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2143.txt","https://www.rfc-editor.org/rfc/rfc2143.pdf"],"folder":"IETF/RFC-2143","files":{"txt":{"path":"standards/IETF/RFC-2143/RFC-2143.txt","sha256":"bd7ee10fd5f30b1aa35fc948160a407fe01decd594fdf1a4b4e38567913f9dd5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Elliston\nRequest for Comments: 2143 Compucat Research\nCategory: Experimental May 1997\n\n Encapsulating IP with the Small Computer System Interface\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Brief background to the Small Computer System Interface . 2\n 3. Link Encapsulation . . . . . . . . . . . . . . . . . . . . 3\n 4. An Address Resolution Protocol . . . . . . . . . . . . . . 4\n 5. Scalability . . . . . . . . . . . . . . . . . . . . . . . 4\n 6. Possible applications . . . . . . . . . . . . . . . . . . 5\n 7. Security considerations . . . . . . . . . . . . . . . . . 5\n 8","scope_keywords":["2143","path","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2143 Network Working Group B. Elliston\nRequest for Comments: 2143 Compucat Research\nCategory: Experimental May 1997\n\n Encapsulating IP with the Small Computer System Interface\n\nStatus of this Memo\n\n This memo defines an Experimental Protocol for the Internet\n community. This memo does not specify an Internet standard of any\n kind. Discussion and suggestions for improvement are requested.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 1\n 2. Brief background to the Small Computer System Interface . 2\n 3. Link Encapsulation . . . . . . . . . . . . . . . . . . . . 3\n 4. An Address Resolution Protocol . . . . . . . . . . . . . . 4\n 5. Scalability . . . . . . . . . . . . . . . . . . . . . . . 4\n 6. Possible applications . . . . . . . . . . . . . . . . . . 5\n 7. Security considerations . . . . . . . . . . . . . . . . . 5\n 8 2143 path policy presentation nested-reference unchanged"},{"id":"IETF RFC 2144","type":"specification","body":"IETF","designation":"RFC 2144","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2144.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2144.txt","https://www.rfc-editor.org/rfc/rfc2144.pdf"],"folder":"IETF/RFC-2144","files":{"txt":{"path":"standards/IETF/RFC-2144/RFC-2144.txt","sha256":"05f382eb588517d8c34624d4425838805d420abe94ab41b9fb9cb520eb6f51c7"}},"tags":["nested-reference","unchanged"],"summary":"There is a need in the Internet community for an unencumbered\n encryption algorithm with a range of key sizes that can provide\n security for a variety of cryptographic applications and protocols.\n\n This document describes an existing algorithm that can be used to\n satisfy this requirement. Included are a description of the cipher\n and the key scheduling algorithm (Section 2), the s-boxes (Appendix\n A), and a set of test vectors (Appendix B).","scope_keywords":["2144","algorithm","algorithms","encryption","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2409","folder":"IETF/RFC-2409","source":"IETF/RFC-2409/RFC-2409.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2451","folder":"IETF/RFC-2451","source":"IETF/RFC-2451/RFC-2451.txt","version":null},{"body":"IETF","designation":"RFC 2612","folder":"IETF/RFC-2612","source":"IETF/RFC-2612/RFC-2612.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2144 There is a need in the Internet community for an unencumbered\n encryption algorithm with a range of key sizes that can provide\n security for a variety of cryptographic applications and protocols.\n\n This document describes an existing algorithm that can be used to\n satisfy this requirement. Included are a description of the cipher\n and the key scheduling algorithm (Section 2), the s-boxes (Appendix\n A), and a set of test vectors (Appendix B). 2144 algorithm algorithms encryption key keys trust nested-reference unchanged"},{"id":"IETF RFC 2612","type":"specification","body":"IETF","designation":"RFC 2612","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2612.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2612.txt","https://www.rfc-editor.org/rfc/rfc2612.pdf"],"folder":"IETF/RFC-2612","files":{"txt":{"path":"standards/IETF/RFC-2612/RFC-2612.txt","sha256":"f803f906018f9a92c853daad2f859137051f21dddf87e9d16fb0587417b097d7"}},"tags":["nested-reference","unchanged"],"summary":"There is always a desire in the Internet community for unencumbered\n encryption algorithms with a range of key sizes that can provide\n security for a variety of cryptographic applications and protocols.\n\n This document describes an existing algorithm that can be used to\n satisfy this requirement. Included are a description of the cipher\n and the key scheduling algorithm, the s-boxes, and a set of test\n vectors (Appendix A).","scope_keywords":["2612","algorithm","algorithms","encryption","key","keys","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2612 There is always a desire in the Internet community for unencumbered\n encryption algorithms with a range of key sizes that can provide\n security for a variety of cryptographic applications and protocols.\n\n This document describes an existing algorithm that can be used to\n satisfy this requirement. Included are a description of the cipher\n and the key scheduling algorithm, the s-boxes, and a set of test\n vectors (Appendix A). 2612 algorithm algorithms encryption key keys trust nested-reference unchanged"},{"id":"IETF RFC 3401","type":"specification","body":"IETF","designation":"RFC 3401","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3401.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3401.txt","https://www.rfc-editor.org/rfc/rfc3401.pdf"],"folder":"IETF/RFC-3401","files":{"txt":{"path":"standards/IETF/RFC-3401/RFC-3401.txt","sha256":"c22c06a1432c7f332074408409c26acf8bb37a55f21f73dab978450f518f662e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Mealling\nRequest for Comments: 3401 VeriSign\nUpdates: 2276 October 2002\nObsoletes: 2915, 2168\nCategory: Informational\n\n Dynamic Delegation Discovery System (DDDS)\n Part One: The Comprehensive DDDS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document specifies the exact documents that make up the complete\n Dynamic Delegation Discovery System (DDDS). DDDS is an abstract\n algorithm for applying dynamically retrieved string transformation\n rules to an application-unique string.\n\n This document along with RFC 3402, RFC 3403 and RFC 3404 obsolete RFC\n 2168 and RFC 2915, as well as updates RFC 2276.\n\n1. Intended Audience\n\n This document an","scope_keywords":["3401","algorithm","algorithms","key","keys","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3402","folder":"IETF/RFC-3402","source":"IETF/RFC-3402/RFC-3402.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3404","folder":"IETF/RFC-3404","source":"IETF/RFC-3404/RFC-3404.txt","version":null},{"body":"IETF","designation":"RFC 3405","folder":"IETF/RFC-3405","source":"IETF/RFC-3405/RFC-3405.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3553","folder":"IETF/RFC-3553","source":"IETF/RFC-3553/RFC-3553.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3824","folder":"IETF/RFC-3824","source":"IETF/RFC-3824/RFC-3824.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 4095","folder":"IETF/RFC-4095","source":"IETF/RFC-4095/RFC-4095.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 3401 Network Working Group M. Mealling\nRequest for Comments: 3401 VeriSign\nUpdates: 2276 October 2002\nObsoletes: 2915, 2168\nCategory: Informational\n\n Dynamic Delegation Discovery System (DDDS)\n Part One: The Comprehensive DDDS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document specifies the exact documents that make up the complete\n Dynamic Delegation Discovery System (DDDS). DDDS is an abstract\n algorithm for applying dynamically retrieved string transformation\n rules to an application-unique string.\n\n This document along with RFC 3402, RFC 3403 and RFC 3404 obsolete RFC\n 2168 and RFC 2915, as well as updates RFC 2276.\n\n1. Intended Audience\n\n This document an 3401 algorithm algorithms key keys risk subject nested-reference unchanged"},{"id":"IETF RFC 2172","type":"specification","body":"IETF","designation":"RFC 2172","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2172.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2172.txt","https://www.rfc-editor.org/rfc/rfc2172.pdf"],"folder":"IETF/RFC-2172","files":{"txt":{"path":"standards/IETF/RFC-2172/RFC-2172.txt","sha256":"ec88a48bea4438858a663bdb2c93afeef41e9d7f9c55db575a3ce45d9d76c00d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Maruyama\nRequest for Comments: 2172 K. Murakami\nCategory: Informational NTT Laboratories\n June 1997\n\n MAPOS Version 1 Assigned Numbers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAuthors' Note\n\n This memo documents the parameters used in the Multiple Access\n Protocol over SONET/SDH Version 1. This document is NOT the product\n of an IETF working group nor is it a standards track document. It\n has not necessarily benefited from the widespread and in-depth\n community review that standards track documents receive.\n\nAbstract\n\n This document describes the protocol parameters used in the Multiple\n Access Over SONET/SDH (MAPOS) version 1. MAPOS is a link layer\n protocol and provides multiple access capability over SONET/SDH\n links.","scope_keywords":["2172"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2174","folder":"IETF/RFC-2174","source":"IETF/RFC-2174/RFC-2174.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null}],"search_text":"IETF RFC 2172 Network Working Group M. Maruyama\nRequest for Comments: 2172 K. Murakami\nCategory: Informational NTT Laboratories\n June 1997\n\n MAPOS Version 1 Assigned Numbers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAuthors' Note\n\n This memo documents the parameters used in the Multiple Access\n Protocol over SONET/SDH Version 1. This document is NOT the product\n of an IETF working group nor is it a standards track document. It\n has not necessarily benefited from the widespread and in-depth\n community review that standards track documents receive.\n\nAbstract\n\n This document describes the protocol parameters used in the Multiple\n Access Over SONET/SDH (MAPOS) version 1. MAPOS is a link layer\n protocol and provides multiple access capability over SONET/SDH\n links. 2172 nested-reference unchanged"},{"id":"IETF RFC 2173","type":"specification","body":"IETF","designation":"RFC 2173","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2173.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2173.txt","https://www.rfc-editor.org/rfc/rfc2173.pdf"],"folder":"IETF/RFC-2173","files":{"txt":{"path":"standards/IETF/RFC-2173/RFC-2173.txt","sha256":"d49b173e0cc2d1e520dc1864e48f47aeeb9e328830eee7ffb71800383530943a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a MAPOS extension, Node Switch Protocol, for\n automatic node address assignment. MAPOS is a multiple access\n protocol for transmission of network-protocol datagrams, encapsulated\n in High-Level Data Link Control (HDLC) frames, over SONET/SDH. NSP\n automates the HDLC address configuration of each node. Using NSP, a\n node retrieves its HDLC address from the switch to which it is\n connected.\n\n1. Introduction\n\n MAPOS[1], Multiple Access Protocol over SONET(Synchronous Optical\n Network)/SDH(Synchronous Digital Hierarchy)[2][3][4][5], is a\n protocol for transmission of HDLC frames over SONET/SDH. A SONET\n switch provides multiple access capability to each node. In MAPOS,\n each node has a unique HDLC address within a switch. The address is\n equivalent to the port number of the switch to which the node is\n connected. This document describes an extension to MAPOS, Node\n Sw","scope_keywords":["2173"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2174","folder":"IETF/RFC-2174","source":"IETF/RFC-2174/RFC-2174.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null}],"search_text":"IETF RFC 2173 This document describes a MAPOS extension, Node Switch Protocol, for\n automatic node address assignment. MAPOS is a multiple access\n protocol for transmission of network-protocol datagrams, encapsulated\n in High-Level Data Link Control (HDLC) frames, over SONET/SDH. NSP\n automates the HDLC address configuration of each node. Using NSP, a\n node retrieves its HDLC address from the switch to which it is\n connected.\n\n1. Introduction\n\n MAPOS[1], Multiple Access Protocol over SONET(Synchronous Optical\n Network)/SDH(Synchronous Digital Hierarchy)[2][3][4][5], is a\n protocol for transmission of HDLC frames over SONET/SDH. A SONET\n switch provides multiple access capability to each node. In MAPOS,\n each node has a unique HDLC address within a switch. The address is\n equivalent to the port number of the switch to which the node is\n connected. This document describes an extension to MAPOS, Node\n Sw 2173 nested-reference unchanged"},{"id":"IETF RFC 2176","type":"specification","body":"IETF","designation":"RFC 2176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2176.txt","https://www.rfc-editor.org/rfc/rfc2176.pdf"],"folder":"IETF/RFC-2176","files":{"txt":{"path":"standards/IETF/RFC-2176/RFC-2176.txt","sha256":"5a8f2749f4d76586c3403a4970fba376fe7f2fa299332910b164e48d0fb4f342"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a protocol for transmission of the Internet\n Protocol Version 4 (IPv4) over Multiple Access Over SONET/SDH (MAPOS)\n version 1. MAPOS is a link layer protocol and provides multiple\n access capability over SONET/SDH links. IP runs on top of MAPOS. This\n document explains IP datagram encapsulation in HDLC frame of MAPOS,\n and the Address Resolution Protocol (ARP).\n\n1. Introduction\n\n Multiple Access Protocol over SONET/SDH (MAPOS) [1] is a high-speed\n link-layer protocol that provides multiple access capability over\n SONET/SDH. Its frame format is based on the HDLC-like framing [2] for\n PPP. A component called \"Frame Switch\" [1] allows multiple nodes to\n be connected together in a star topology to form a LAN. Using long\n haul SONET/SDH links, the nodes on such a \"SONET-LAN\" can span over a\n wide geographical area. The Internet Protocol (IP) [3] datagrams are\n transmit","scope_keywords":["2176","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null}],"search_text":"IETF RFC 2176 This document describes a protocol for transmission of the Internet\n Protocol Version 4 (IPv4) over Multiple Access Over SONET/SDH (MAPOS)\n version 1. MAPOS is a link layer protocol and provides multiple\n access capability over SONET/SDH links. IP runs on top of MAPOS. This\n document explains IP datagram encapsulation in HDLC frame of MAPOS,\n and the Address Resolution Protocol (ARP).\n\n1. Introduction\n\n Multiple Access Protocol over SONET/SDH (MAPOS) [1] is a high-speed\n link-layer protocol that provides multiple access capability over\n SONET/SDH. Its frame format is based on the HDLC-like framing [2] for\n PPP. A component called \"Frame Switch\" [1] allows multiple nodes to\n be connected together in a star topology to form a LAN. Using long\n haul SONET/SDH links, the nodes on such a \"SONET-LAN\" can span over a\n wide geographical area. The Internet Protocol (IP) [3] datagrams are\n transmit 2176 path validation nested-reference unchanged"},{"id":"IETF RFC 5551","type":"specification","body":"IETF","designation":"RFC 5551","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5551.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5551.txt","https://www.rfc-editor.org/rfc/rfc5551.pdf"],"folder":"IETF/RFC-5551","files":{"txt":{"path":"standards/IETF/RFC-5551/RFC-5551.txt","sha256":"a60de0d81ca6a65bac78916a175bccef521666a298922056d91a7910e7f13de0"}},"tags":["nested-reference","unchanged"],"summary":"Notification and filtering mechanisms can make email more enjoyable\n on mobile and other constrained devices (such as those with limited\n screen sizes, memory, data transfer rates, etc.). Notifications make\n the client aware of significant events (such as the arrival of new\n mail) so it can react (such as by fetching interesting mail\n immediately). Filtering reduces the visible mail to a set of\n messages that meet some criteria for \"interesting\". This\n functionality is included in the goals of the Lemonade (Enhancements\n to Internet email to Support Diverse Service Environments) Working\n Group.\n\n This document also discusses the use of server-to-server\n notifications, and how server to server notifications fit into an\n architecture that provides server to client notifications.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Intern","scope_keywords":["5551","http","license","policies","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null}],"search_text":"IETF RFC 5551 Notification and filtering mechanisms can make email more enjoyable\n on mobile and other constrained devices (such as those with limited\n screen sizes, memory, data transfer rates, etc.). Notifications make\n the client aware of significant events (such as the arrival of new\n mail) so it can react (such as by fetching interesting mail\n immediately). Filtering reduces the visible mail to a set of\n messages that meet some criteria for \"interesting\". This\n functionality is included in the goals of the Lemonade (Enhancements\n to Internet email to Support Diverse Service Environments) Working\n Group.\n\n This document also discusses the use of server-to-server\n notifications, and how server to server notifications fit into an\n architecture that provides server to client notifications.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Intern 5551 http license policies profile subject trust nested-reference unchanged"},{"id":"IETF RFC 2179","type":"specification","body":"IETF","designation":"RFC 2179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2179.txt","https://www.rfc-editor.org/rfc/rfc2179.pdf"],"folder":"IETF/RFC-2179","files":{"txt":{"path":"standards/IETF/RFC-2179/RFC-2179.txt","sha256":"f8772fd14d588a8fac564693d02dce266762a385befc61c6fe2fa55df5a25d45"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Gwinn\nRequest for Comments: 2179 Networld+Interop NOC Team\nCategory: Informational July 1997\n\n Network Security For Trade Shows\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document is designed to assist vendors and other participants in\n trade shows, such as Networld+Interop, in designing effective\n protection against network and system attacks by unauthorized\n individuals. Generally, it has been observed that many system\n administrators and trade show coordinators tend to overlook the\n importance of system security at trade shows. In fact, systems at\n trade shows are at least as prone to attack as office-based\n platforms. Trade show systems should be treated as seriously as an\n office computer. A breach of ","scope_keywords":["2179","authentication","identification","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2179 Network Working Group A. Gwinn\nRequest for Comments: 2179 Networld+Interop NOC Team\nCategory: Informational July 1997\n\n Network Security For Trade Shows\n\nStatus of this Memo\n\n This memo provides information for the Internet community. This memo\n does not specify an Internet standard of any kind. Distribution of\n this memo is unlimited.\n\nAbstract\n\n This document is designed to assist vendors and other participants in\n trade shows, such as Networld+Interop, in designing effective\n protection against network and system attacks by unauthorized\n individuals. Generally, it has been observed that many system\n administrators and trade show coordinators tend to overlook the\n importance of system security at trade shows. In fact, systems at\n trade shows are at least as prone to attack as office-based\n platforms. Trade show systems should be treated as seriously as an\n office computer. A breach of  2179 authentication identification key subject nested-reference unchanged"},{"id":"IETF RFC 2763","type":"specification","body":"IETF","designation":"RFC 2763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2763.txt","https://www.rfc-editor.org/rfc/rfc2763.pdf"],"folder":"IETF/RFC-2763","files":{"txt":{"path":"standards/IETF/RFC-2763/RFC-2763.txt","sha256":"31fc8ada01a952e66895365e6b35284c6b234c0fde34c33b733df8f103390389"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Shen\nRequest for Comments: 2763 Siara Systems\nCategory: Informational H. Smit\n Cisco Systems\n February 2000\n\n Dynamic Hostname Exchange Mechanism\n for IS-IS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently, there does not exist a simple and dynamic mechanism for\n routers running IS-IS to learn about symbolic hostnames. This\n document defines a new TLV which allows the IS-IS routers to flood\n their name to system ID mapping information across the IS-IS network.\n\n1. Introduction\n\n IS-IS uses a 1-8 byte system ID (normally 6 bytes) to represent a\n node in the network. For management and operation reasons, network\n operators need to che","scope_keywords":["2763","authentication","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3359","folder":"IETF/RFC-3359","source":"IETF/RFC-3359/RFC-3359.txt","version":null},{"body":"IETF","designation":"RFC 5301","folder":"IETF/RFC-5301","source":"IETF/RFC-5301/RFC-5301.txt","version":null}],"search_text":"IETF RFC 2763 Network Working Group N. Shen\nRequest for Comments: 2763 Siara Systems\nCategory: Informational H. Smit\n Cisco Systems\n February 2000\n\n Dynamic Hostname Exchange Mechanism\n for IS-IS\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n Currently, there does not exist a simple and dynamic mechanism for\n routers running IS-IS to learn about symbolic hostnames. This\n document defines a new TLV which allows the IS-IS routers to flood\n their name to system ID mapping information across the IS-IS network.\n\n1. Introduction\n\n IS-IS uses a 1-8 byte system ID (normally 6 bytes) to represent a\n node in the network. For management and operation reasons, network\n operators need to che 2763 authentication management presentation nested-reference unchanged"},{"id":"IETF RFC 3143","type":"specification","body":"IETF","designation":"RFC 3143","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3143.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3143.txt","https://www.rfc-editor.org/rfc/rfc3143.pdf"],"folder":"IETF/RFC-3143","files":{"txt":{"path":"standards/IETF/RFC-3143/RFC-3143.txt","sha256":"e34730e4d5570207567954a67c0d3acf753ea15d56583b6c85e48748ea6cac1b"}},"tags":["nested-reference","unchanged"],"summary":"This document catalogs a number of known problems with World Wide Web\n (WWW) (caching) proxies and cache servers. The goal of the document\n is to provide a discussion of the problems and proposed workarounds,\n and ultimately to improve conditions by illustrating problems. The\n construction of this document is a joint effort of the Web caching\n community.","scope_keywords":["3143","authentication","http","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5019","folder":"IETF/RFC-5019","source":"IETF/RFC-5019/RFC-5019.txt","version":null}],"search_text":"IETF RFC 3143 This document catalogs a number of known problems with World Wide Web\n (WWW) (caching) proxies and cache servers. The goal of the document\n is to provide a discussion of the problems and proposed workarounds,\n and ultimately to improve conditions by illustrating problems. The\n construction of this document is a joint effort of the Web caching\n community. 3143 authentication http timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 7656","type":"specification","body":"IETF","designation":"RFC 7656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7656.txt","https://www.rfc-editor.org/rfc/rfc7656.pdf"],"folder":"IETF/RFC-7656","files":{"txt":{"path":"standards/IETF/RFC-7656/RFC-7656.txt","sha256":"092dea2dbcd263336fb3593f3e2bd691f7e2eb22607e40b2ebccfc047e246131"}},"tags":["nested-reference","unchanged"],"summary":"The terminology about, and associations among, Real-time Transport\n Protocol (RTP) sources can be complex and somewhat opaque. This\n document describes a number of existing and proposed properties and\n relationships among RTP sources and defines common terminology for\n discussing protocol entities and their relationships.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h","scope_keywords":["7656","http","license","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7667","folder":"IETF/RFC-7667","source":"IETF/RFC-7667/RFC-7667.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8852","folder":"IETF/RFC-8852","source":"IETF/RFC-8852/RFC-8852.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 7656 The terminology about, and associations among, Real-time Transport\n Protocol (RTP) sources can be complex and somewhat opaque. This\n document describes a number of existing and proposed properties and\n relationships among RTP sources and defines common terminology for\n discussing protocol entities and their relationships.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and h 7656 http license subject trust validation nested-reference unchanged"},{"id":"IETF RFC 2204","type":"specification","body":"IETF","designation":"RFC 2204","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2204.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2204.txt","https://www.rfc-editor.org/rfc/rfc2204.pdf"],"folder":"IETF/RFC-2204","files":{"txt":{"path":"standards/IETF/RFC-2204/RFC-2204.txt","sha256":"cfccc23ee875f908ae8e98eb2eaad62584e518cdf933c7e3bf14da14b2f9379b"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a file transfer protocol to facilitate electronic\n data interchange between trading partners.\n\n The protocol, denoted the ODETTE File Transfer Protocol, supports\n both direct communication between installations and indirect\n communication via a third party clearing centre. It was developed by\n the Organisation for Data Exchange by Tele Transmission in Europe to\n facilitate communication within the European motor industry and is\n presented here to allow for wider use within the Internet community.","scope_keywords":["2204","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null}],"search_text":"IETF RFC 2204 This memo describes a file transfer protocol to facilitate electronic\n data interchange between trading partners.\n\n The protocol, denoted the ODETTE File Transfer Protocol, supports\n both direct communication between installations and indirect\n communication via a third party clearing centre. It was developed by\n the Organisation for Data Exchange by Tele Transmission in Europe to\n facilitate communication within the European motor industry and is\n presented here to allow for wider use within the Internet community. 2204 identification nested-reference unchanged"},{"id":"IETF RFC 2430","type":"specification","body":"IETF","designation":"RFC 2430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2430.txt","https://www.rfc-editor.org/rfc/rfc2430.pdf"],"folder":"IETF/RFC-2430","files":{"txt":{"path":"standards/IETF/RFC-2430/RFC-2430.txt","sha256":"0cb0623239e335f4d980e40f22b62dc04d4cd74d02030b6399d5afdc444748da"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Provider Architecture for Differentiated\n Services and Traffic Engineering (PASTE) for Internet Service\n Providers (ISPs). Providing differentiated services in ISPs is a\n challenge because the scaling problems presented by the sheer number\n of flows present in large ISPs makes the cost of maintaining per-flow\n state unacceptable. Coupled with this, large ISPs need the ability\n to perform traffic engineering by directing aggregated flows of\n traffic along specific paths.\n\n PASTE addresses these issues by using Multiprotocol Label Switching\n (MPLS) [1] and the Resource Reservation Protocol (RSVP) [2] to create\n a scalable traffic management architecture that supports\n differentiated services. This document assumes that the reader has\n at least some familiarity with both of these technologies.","scope_keywords":["2430","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2547","folder":"IETF/RFC-2547","source":"IETF/RFC-2547/RFC-2547.txt","version":null},{"body":"IETF","designation":"RFC 2702","folder":"IETF/RFC-2702","source":"IETF/RFC-2702/RFC-2702.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4364","folder":"IETF/RFC-4364","source":"IETF/RFC-4364/RFC-4364.txt","version":null}],"search_text":"IETF RFC 2430 This document describes the Provider Architecture for Differentiated\n Services and Traffic Engineering (PASTE) for Internet Service\n Providers (ISPs). Providing differentiated services in ISPs is a\n challenge because the scaling problems presented by the sheer number\n of flows present in large ISPs makes the cost of maintaining per-flow\n state unacceptable. Coupled with this, large ISPs need the ability\n to perform traffic engineering by directing aggregated flows of\n traffic along specific paths.\n\n PASTE addresses these issues by using Multiprotocol Label Switching\n (MPLS) [1] and the Resource Reservation Protocol (RSVP) [2] to create\n a scalable traffic management architecture that supports\n differentiated services. This document assumes that the reader has\n at least some familiarity with both of these technologies. 2430 management path subject nested-reference unchanged"},{"id":"IETF RFC 2638","type":"specification","body":"IETF","designation":"RFC 2638","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2638.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2638.txt","https://www.rfc-editor.org/rfc/rfc2638.pdf"],"folder":"IETF/RFC-2638","files":{"pdf":{"path":"standards/IETF/RFC-2638/RFC-2638.pdf","sha256":"a74e426d1f759b5aeca1bffb67decd6602b9e7649ad71a4f378eca6b7b8eb618"},"txt":{"path":"standards/IETF/RFC-2638/RFC-2638.txt","sha256":"841ba57e37b67f6237e03645e80e732d7d59e2075256f3a0c3b934e396bbcc58"}},"tags":["nested-reference","unchanged"],"summary":"This document was originally submitted as an internet draft in\n November of 1997. As one of the documents predating the formation of\n the IETF's Differentiated Services Working Group, many of the ideas\n presented here, in concert with Dave Clark's subsequent presentation\n to the December 1997 meeting of the IETF Integrated Services Working\n Group, were key to the work which led to RFCs 2474 and 2475 and the\n section on allocation remains a timely proposal. For this reason, and\n to provide a reference, it is being submitted in its original form.\n The forwarding path portion of this document is intended as a record\n of where we were at in late 1997 and not as an indication of future\n direction.\n\n The postscript version of this document includes Clark's slides as an\n appendix. The postscript version of this document also includes many\n figures that aid greatly in its readability.\n\n1. Introd","scope_keywords":["2638","key","management","path","policy","presentation","profile","profiles","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 5977","folder":"IETF/RFC-5977","source":"IETF/RFC-5977/RFC-5977.txt","version":null}],"search_text":"IETF RFC 2638 This document was originally submitted as an internet draft in\n November of 1997. As one of the documents predating the formation of\n the IETF's Differentiated Services Working Group, many of the ideas\n presented here, in concert with Dave Clark's subsequent presentation\n to the December 1997 meeting of the IETF Integrated Services Working\n Group, were key to the work which led to RFCs 2474 and 2475 and the\n section on allocation remains a timely proposal. For this reason, and\n to provide a reference, it is being submitted in its original form.\n The forwarding path portion of this document is intended as a record\n of where we were at in late 1997 and not as an indication of future\n direction.\n\n The postscript version of this document includes Clark's slides as an\n appendix. The postscript version of this document also includes many\n figures that aid greatly in its readability.\n\n1. Introd 2638 key management path policy presentation profile profiles risk nested-reference unchanged"},{"id":"IETF RFC 2745","type":"specification","body":"IETF","designation":"RFC 2745","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2745.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2745.txt","https://www.rfc-editor.org/rfc/rfc2745.pdf"],"folder":"IETF/RFC-2745","files":{"txt":{"path":"standards/IETF/RFC-2745/RFC-2745.txt","sha256":"cb85b5d345b8734639b2c72e93979ec586642816b5f09854aca0dc8577c43f4a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the RSVP diagnostic facility, which allows a\n user to collect information about the RSVP state along a path. This\n specification describes the functionality, diagnostic message\n formats, and processing rules.\n\n1. Introduction\n\n In the basic RSVP protocol [RSVP], error messages are the only means\n for an end host to receive feedback regarding a failure in setting up\n either path state or reservation state. An error message carries\n back only the information from the failed point, without any\n information about the state at other hops before or after the\n failure. In the absence of failures, a host receives no feedback\n regarding the details of a reservation that has been put in place,\n such as whether, or where, or how, its own reservation request is\n being merged with that of others. Such missing information can be\n highly desirable for debugging purposes, or for ","scope_keywords":["2745","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null}],"search_text":"IETF RFC 2745 This document specifies the RSVP diagnostic facility, which allows a\n user to collect information about the RSVP state along a path. This\n specification describes the functionality, diagnostic message\n formats, and processing rules.\n\n1. Introduction\n\n In the basic RSVP protocol [RSVP], error messages are the only means\n for an end host to receive feedback regarding a failure in setting up\n either path state or reservation state. An error message carries\n back only the information from the failed point, without any\n information about the state at other hops before or after the\n failure. In the absence of failures, a host receives no feedback\n regarding the details of a reservation that has been put in place,\n such as whether, or where, or how, its own reservation request is\n being merged with that of others. Such missing information can be\n highly desirable for debugging purposes, or for  2745 management path nested-reference unchanged"},{"id":"IETF RFC 2749","type":"specification","body":"IETF","designation":"RFC 2749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2749.txt","https://www.rfc-editor.org/rfc/rfc2749.pdf"],"folder":"IETF/RFC-2749","files":{"txt":{"path":"standards/IETF/RFC-2749/RFC-2749.txt","sha256":"afe0bda9811af283edb6498038169ab51caa9b2e6d7469ec9102b5e3e9a72abc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes usage directives for supporting COPS policy\n services in RSVP environments.","scope_keywords":["2749","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2750","folder":"IETF/RFC-2750","source":"IETF/RFC-2750/RFC-2750.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3139","folder":"IETF/RFC-3139","source":"IETF/RFC-3139/RFC-3139.txt","version":null},{"body":"IETF","designation":"RFC 3159","folder":"IETF/RFC-3159","source":"IETF/RFC-3159/RFC-3159.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3198","folder":"IETF/RFC-3198","source":"IETF/RFC-3198/RFC-3198.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null}],"search_text":"IETF RFC 2749 This document describes usage directives for supporting COPS policy\n services in RSVP environments. 2749 path policies policy nested-reference unchanged"},{"id":"IETF RFC 2750","type":"specification","body":"IETF","designation":"RFC 2750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2750.txt","https://www.rfc-editor.org/rfc/rfc2750.pdf"],"folder":"IETF/RFC-2750","files":{"txt":{"path":"standards/IETF/RFC-2750/RFC-2750.txt","sha256":"da47b5278b81475745d142f2fece837267c14464eef51217c59f1a28970aedf1"}},"tags":["nested-reference","unchanged"],"summary":"This memo presents a set of extensions for supporting generic policy\n based admission control in RSVP. It should be perceived as an\n extension to the RSVP functional specifications [RSVP]\n\n These extensions include the standard format of POLICY_DATA objects,\n and a description of RSVP's handling of policy events.\n\n This document does not advocate particular policy control mechanisms;\n however, a Router/Server Policy Protocol description for these\n extensions can be found in [RAP, COPS, COPS-RSVP].\n\nHerzog Standards Track [Page 1]\n\f\nRFC 2750 RSVP Extensions for Policy Control January 2000","scope_keywords":["2750","holder","path","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2749","folder":"IETF/RFC-2749","source":"IETF/RFC-2749/RFC-2749.txt","version":null},{"body":"IETF","designation":"RFC 2751","folder":"IETF/RFC-2751","source":"IETF/RFC-2751/RFC-2751.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2753","folder":"IETF/RFC-2753","source":"IETF/RFC-2753/RFC-2753.txt","version":null},{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3521","folder":"IETF/RFC-3521","source":"IETF/RFC-3521/RFC-3521.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4230","folder":"IETF/RFC-4230","source":"IETF/RFC-4230/RFC-4230.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"IETF RFC 2750 This memo presents a set of extensions for supporting generic policy\n based admission control in RSVP. It should be perceived as an\n extension to the RSVP functional specifications [RSVP]\n\n These extensions include the standard format of POLICY_DATA objects,\n and a description of RSVP's handling of policy events.\n\n This document does not advocate particular policy control mechanisms;\n however, a Router/Server Policy Protocol description for these\n extensions can be found in [RAP, COPS, COPS-RSVP].\n\nHerzog Standards Track [Page 1]\n\f\nRFC 2750 RSVP Extensions for Policy Control January 2000 2750 holder path policies policy trust nested-reference unchanged"},{"id":"IETF RFC 2751","type":"specification","body":"IETF","designation":"RFC 2751","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2751.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2751.txt","https://www.rfc-editor.org/rfc/rfc2751.pdf"],"folder":"IETF/RFC-2751","files":{"txt":{"path":"standards/IETF/RFC-2751/RFC-2751.txt","sha256":"277666b4606a30fab974b90626fec34aa2d910b006ae1582d0a9e408fa85c59c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a preemption priority policy element for use\n by signaled policy based admission protocols (such as [RSVP] and\n [COPS]).\n\n Preemption priority defines a relative importance (rank) within the\n set of flows competing to be admitted into the network. Rather than\n admitting flows by order of arrival (First Come First Admitted)\n network nodes may consider priorities to preempt some previously\n admitted low priority flows in order to make room for a newer, high-\n priority flow.\n\nHerzog Standards Track [Page 1]\n\f\nRFC 2751 Signaled Preemption Priority Policy Element January 2000","scope_keywords":["2751","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3181","folder":"IETF/RFC-3181","source":"IETF/RFC-3181/RFC-3181.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null}],"search_text":"IETF RFC 2751 This document describes a preemption priority policy element for use\n by signaled policy based admission protocols (such as [RSVP] and\n [COPS]).\n\n Preemption priority defines a relative importance (rank) within the\n set of flows competing to be admitted into the network. Rather than\n admitting flows by order of arrival (First Come First Admitted)\n network nodes may consider priorities to preempt some previously\n admitted low priority flows in order to make room for a newer, high-\n priority flow.\n\nHerzog Standards Track [Page 1]\n\f\nRFC 2751 Signaled Preemption Priority Policy Element January 2000 2751 policy registered nested-reference unchanged"},{"id":"IETF RFC 2996","type":"specification","body":"IETF","designation":"RFC 2996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2996.txt","https://www.rfc-editor.org/rfc/rfc2996.pdf"],"folder":"IETF/RFC-2996","files":{"txt":{"path":"standards/IETF/RFC-2996/RFC-2996.txt","sha256":"8a9a95e840d97a22e5d3663eb805976891e1fd816f1bda5699367b8e3d5d8863"}},"tags":["nested-reference","unchanged"],"summary":"Resource Reservation Protocol (RSVP) signaling may be used to request\n Quality of Service (QoS) services and enhance the manageability of\n application traffic's QoS in a differentiated service (diff-serv or\n DS) network. When using RSVP with DS networks it is useful to be\n able to carry carry Differentiated Services Code Points (DSCPs) in\n RSVP message objects. One example of this is the use of RSVP to\n arrange for the marking of packets with a particular DSCP upstream\n from the DS network's ingress point, at the sender or at a previous\n network's egress router.\n\n The DCLASS object is used to represent and carry DSCPs within RSVP\n messages. This document specifies the format of the DCLASS object\n and briefly discusses its use.\n\n1. Introduction\n\n This section describes the mechanics of using RSVP [RSVP] signaling\n and the DCLASS object for effecting admission control and applying\n QoS pol","scope_keywords":["2996","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2990","folder":"IETF/RFC-2990","source":"IETF/RFC-2990/RFC-2990.txt","version":null},{"body":"IETF","designation":"RFC 2997","folder":"IETF/RFC-2997","source":"IETF/RFC-2997/RFC-2997.txt","version":null},{"body":"IETF","designation":"RFC 2998","folder":"IETF/RFC-2998","source":"IETF/RFC-2998/RFC-2998.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null}],"search_text":"IETF RFC 2996 Resource Reservation Protocol (RSVP) signaling may be used to request\n Quality of Service (QoS) services and enhance the manageability of\n application traffic's QoS in a differentiated service (diff-serv or\n DS) network. When using RSVP with DS networks it is useful to be\n able to carry carry Differentiated Services Code Points (DSCPs) in\n RSVP message objects. One example of this is the use of RSVP to\n arrange for the marking of packets with a particular DSCP upstream\n from the DS network's ingress point, at the sender or at a previous\n network's egress router.\n\n The DCLASS object is used to represent and carry DSCPs within RSVP\n messages. This document specifies the format of the DCLASS object\n and briefly discusses its use.\n\n1. Introduction\n\n This section describes the mechanics of using RSVP [RSVP] signaling\n and the DCLASS object for effecting admission control and applying\n QoS pol 2996 path policy nested-reference unchanged"},{"id":"IETF RFC 2997","type":"specification","body":"IETF","designation":"RFC 2997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2997.txt","https://www.rfc-editor.org/rfc/rfc2997.pdf"],"folder":"IETF/RFC-2997","files":{"txt":{"path":"standards/IETF/RFC-2997/RFC-2997.txt","sha256":"5619b5c7a70c37e24effc520dcf9c6f1f3fe131ae62619091e2efd1cea0599ed"}},"tags":["nested-reference","unchanged"],"summary":"In the typical Resource Reservation Protocol (RSVP)/Intserv model,\n applications request a specific Intserv service type and quantify the\n resources required for that service. For certain applications, the\n determination of service parameters is best left to the discretion of\n the network administrator. For example, ERP applications are often\n mission critical and require some form of prioritized service, but\n cannot readily specify their resource requirements. To serve such\n applications, we introduce the notion of the 'Null Service'. The\n Null Service allows applications to identify themselves to network\n Quality of Service (QoS) policy agents, using RSVP signaling.\n However, it does not require them to specify resource requirements.\n QoS policy agents in the network respond by applying QoS policies\n appropriate for the application (as determined by the network\n administrator). This mo","scope_keywords":["2997","management","path","policies","policy","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 2997 In the typical Resource Reservation Protocol (RSVP)/Intserv model,\n applications request a specific Intserv service type and quantify the\n resources required for that service. For certain applications, the\n determination of service parameters is best left to the discretion of\n the network administrator. For example, ERP applications are often\n mission critical and require some form of prioritized service, but\n cannot readily specify their resource requirements. To serve such\n applications, we introduce the notion of the 'Null Service'. The\n Null Service allows applications to identify themselves to network\n Quality of Service (QoS) policy agents, using RSVP signaling.\n However, it does not require them to specify resource requirements.\n QoS policy agents in the network respond by applying QoS policies\n appropriate for the application (as determined by the network\n administrator). This mo 2997 management path policies policy tsp nested-reference unchanged"},{"id":"IETF RFC 3181","type":"specification","body":"IETF","designation":"RFC 3181","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3181.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3181.txt","https://www.rfc-editor.org/rfc/rfc3181.pdf"],"folder":"IETF/RFC-3181","files":{"txt":{"path":"standards/IETF/RFC-3181/RFC-3181.txt","sha256":"d7d9fc56a90f1fefdc4bc26002501e7b4ed654f75f40111ed0d55f56a2d68f7c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a preemption priority policy element for use\n by signaled policy based admission protocols (such as the Resource\n ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS).\n\n Preemption priority defines a relative importance (rank) within the\n set of flows competing to be admitted into the network. Rather than\n admitting flows by order of arrival (First Come First Admitted)\n network nodes may consider priorities to preempt some previously\n admitted low priority flows in order to make room for a newer, high-\n priority flow.\n\n This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment\n error in RFC 2751.\n\nHerzog Standards Track [Page 1]\n\f\nRFC 3181 Signaled Preemption Priority Policy Element October 2001","scope_keywords":["3181","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3644","folder":"IETF/RFC-3644","source":"IETF/RFC-3644/RFC-3644.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null}],"search_text":"IETF RFC 3181 This document describes a preemption priority policy element for use\n by signaled policy based admission protocols (such as the Resource\n ReSerVation Protocol (RSVP) and Common Open Policy Service (COPS).\n\n Preemption priority defines a relative importance (rank) within the\n set of flows competing to be admitted into the network. Rather than\n admitting flows by order of arrival (First Come First Admitted)\n network nodes may consider priorities to preempt some previously\n admitted low priority flows in order to make room for a newer, high-\n priority flow.\n\n This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment\n error in RFC 2751.\n\nHerzog Standards Track [Page 1]\n\f\nRFC 3181 Signaled Preemption Priority Policy Element October 2001 3181 policy registered nested-reference unchanged"},{"id":"IETF RFC 3210","type":"specification","body":"IETF","designation":"RFC 3210","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3210.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3210.txt","https://www.rfc-editor.org/rfc/rfc3210.pdf"],"folder":"IETF/RFC-3210","files":{"txt":{"path":"standards/IETF/RFC-3210/RFC-3210.txt","sha256":"ed4245bf00bebe4e2fc1a62f6ab0be982080326ec5520ef38d6bd0971e70145f"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses the applicability of \"Extensions to RSVP\n (Resource ReSerVation Protocol) for LSP Tunnels\". It highlights the\n protocol's principles of operation and describes the network context\n for which it was designed. Guidelines for deployment are offered and\n known protocol limitations are indicated. This document is intended\n to accompany the submission of \"Extensions to RSVP for LSP Tunnels\"\n onto the Internet standards track.","scope_keywords":["3210","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3213","folder":"IETF/RFC-3213","source":"IETF/RFC-3213/RFC-3213.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3346","folder":"IETF/RFC-3346","source":"IETF/RFC-3346/RFC-3346.txt","version":null}],"search_text":"IETF RFC 3210 This memo discusses the applicability of \"Extensions to RSVP\n (Resource ReSerVation Protocol) for LSP Tunnels\". It highlights the\n protocol's principles of operation and describes the network context\n for which it was designed. Guidelines for deployment are offered and\n known protocol limitations are indicated. This document is intended\n to accompany the submission of \"Extensions to RSVP for LSP Tunnels\"\n onto the Internet standards track. 3210 path policies nested-reference unchanged"},{"id":"IETF RFC 3469","type":"specification","body":"IETF","designation":"RFC 3469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3469.txt","https://www.rfc-editor.org/rfc/rfc3469.pdf"],"folder":"IETF/RFC-3469","files":{"txt":{"path":"standards/IETF/RFC-3469/RFC-3469.txt","sha256":"98de3416d3cc924632a93236f4a62db5077aa3dee09c98fd20143e601ff0960c"}},"tags":["nested-reference","unchanged"],"summary":"Multi-protocol label switching (MPLS) integrates the label swapping\n forwarding paradigm with network layer routing. To deliver reliable\n service, MPLS requires a set of procedures to provide protection of\n the traffic carried on different paths. This requires that the label\n switching routers (LSRs) support fault detection, fault notification,\n and fault recovery mechanisms, and that MPLS signaling support the\n configuration of recovery. With these objectives in mind, this\n document specifies a framework for MPLS based recovery. Restart\n issues are not included in this framework.","scope_keywords":["3469","algorithm","algorithms","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null},{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 3469 Multi-protocol label switching (MPLS) integrates the label swapping\n forwarding paradigm with network layer routing. To deliver reliable\n service, MPLS requires a set of procedures to provide protection of\n the traffic carried on different paths. This requires that the label\n switching routers (LSRs) support fault detection, fault notification,\n and fault recovery mechanisms, and that MPLS signaling support the\n configuration of recovery. With these objectives in mind, this\n document specifies a framework for MPLS based recovery. Restart\n issues are not included in this framework. 3469 algorithm algorithms delivery path nested-reference unchanged"},{"id":"IETF RFC 6372","type":"specification","body":"IETF","designation":"RFC 6372","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6372.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6372.txt","https://www.rfc-editor.org/rfc/rfc6372.pdf"],"folder":"IETF/RFC-6372","files":{"txt":{"path":"standards/IETF/RFC-6372/RFC-6372.txt","sha256":"e393405fd737b127bd47f3eaa19dd28f473325238b87f080ae969d3592135563"}},"tags":["nested-reference","unchanged"],"summary":"Network survivability is the ability of a network to recover traffic\n delivery following failure or degradation of network resources.\n Survivability is critical for the delivery of guaranteed network\n services, such as those subject to strict Service Level Agreements\n (SLAs) that place maximum bounds on the length of time that services\n may be degraded or unavailable.\n\n The Transport Profile of Multiprotocol Label Switching (MPLS-TP) is a\n packet-based transport technology based on the MPLS data plane that\n reuses many aspects of the MPLS management and control planes.\n\n This document comprises a framework for the provision of\n survivability in an MPLS-TP network; it describes recovery elements,\n types, methods, and topological considerations. To enable data-plane\n recovery, survivability may be supported by the control plane,\n management plane, and by Operations, Administration, and Mai","scope_keywords":["6372","delivery","http","license","management","path","profile","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"IETF RFC 6372 Network survivability is the ability of a network to recover traffic\n delivery following failure or degradation of network resources.\n Survivability is critical for the delivery of guaranteed network\n services, such as those subject to strict Service Level Agreements\n (SLAs) that place maximum bounds on the length of time that services\n may be degraded or unavailable.\n\n The Transport Profile of Multiprotocol Label Switching (MPLS-TP) is a\n packet-based transport technology based on the MPLS data plane that\n reuses many aspects of the MPLS management and control planes.\n\n This document comprises a framework for the provision of\n survivability in an MPLS-TP network; it describes recovery elements,\n types, methods, and topological considerations. To enable data-plane\n recovery, survivability may be supported by the control plane,\n management plane, and by Operations, Administration, and Mai 6372 delivery http license management path profile risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6436","type":"specification","body":"IETF","designation":"RFC 6436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6436.txt","https://www.rfc-editor.org/rfc/rfc6436.pdf"],"folder":"IETF/RFC-6436","files":{"txt":{"path":"standards/IETF/RFC-6436/RFC-6436.txt","sha256":"5d317bc582692c9113a1b52e828c0a8a00fd713fcce58c8b84a98f84e18663ef"}},"tags":["nested-reference","unchanged"],"summary":"Various published proposals for use of the IPv6 flow label are\n incompatible with its original specification in RFC 3697.\n Furthermore, very little practical use is made of the flow label,\n partly due to some uncertainties about the correct interpretation of\n the specification. This document discusses and motivates changes to\n the specification in order to clarify it and to introduce some\n additional flexibility.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Secti","scope_keywords":["6436","hash","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6437","folder":"IETF/RFC-6437","source":"IETF/RFC-6437/RFC-6437.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null}],"search_text":"IETF RFC 6436 Various published proposals for use of the IPv6 flow label are\n incompatible with its original specification in RFC 3697.\n Furthermore, very little practical use is made of the flow label,\n partly due to some uncertainties about the correct interpretation of\n the specification. This document discusses and motivates changes to\n the specification in order to clarify it and to introduce some\n additional flexibility.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Secti 6436 hash http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2214","type":"specification","body":"IETF","designation":"RFC 2214","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2214.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2214.txt","https://www.rfc-editor.org/rfc/rfc2214.pdf"],"folder":"IETF/RFC-2214","files":{"txt":{"path":"standards/IETF/RFC-2214/RFC-2214.txt","sha256":"88dde9e42c1c179ea159c7bdd9114da4df19c995f540267355fc37e6acfa629a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the the interface\n attributes defined in the Guaranteed Service of the Integrated\n Services Model. Comments should be made to the Integrated Services\n Working Group, intserv@isi.edu.","scope_keywords":["2214","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2214 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing the the interface\n attributes defined in the Guaranteed Service of the Integrated\n Services Model. Comments should be made to the Integrated Services\n Working Group, intserv@isi.edu. 2214 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 3213","type":"specification","body":"IETF","designation":"RFC 3213","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3213.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3213.txt","https://www.rfc-editor.org/rfc/rfc3213.pdf"],"folder":"IETF/RFC-3213","files":{"txt":{"path":"standards/IETF/RFC-3213/RFC-3213.txt","sha256":"a0d3e2dfed489c45578df61f6a037867f5772d69750e460250729c1050da89f0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Ash\nRequest for Comments: 3213 AT&T\nCategory: Informational M. Girish\n Atoga Systems\n E. Gray\n Sandburst\n B. Jamoussi\n G. Wright\n Nortel Networks Corp.\n January 2002\n\n Applicability Statement for CR-LDP\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document discusses the applicability of Constraint-Based LSP\n Setup using LDP. It discusses possible network applications,\n extensions to Label Distribution Protocol (LDP) required to implement\n constraint-based routing, guidelines for deployment and known\n limitations of the protocol. This document is a prerequisite to\n advancing CR-LDP on the standards track.\n\n1. Introduction\n\n As the Int","scope_keywords":["3213","delivery","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3214","folder":"IETF/RFC-3214","source":"IETF/RFC-3214/RFC-3214.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3468","folder":"IETF/RFC-3468","source":"IETF/RFC-3468/RFC-3468.txt","version":null}],"search_text":"IETF RFC 3213 Network Working Group J. Ash\nRequest for Comments: 3213 AT&T\nCategory: Informational M. Girish\n Atoga Systems\n E. Gray\n Sandburst\n B. Jamoussi\n G. Wright\n Nortel Networks Corp.\n January 2002\n\n Applicability Statement for CR-LDP\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document discusses the applicability of Constraint-Based LSP\n Setup using LDP. It discusses possible network applications,\n extensions to Label Distribution Protocol (LDP) required to implement\n constraint-based routing, guidelines for deployment and known\n limitations of the protocol. This document is a prerequisite to\n advancing CR-LDP on the standards track.\n\n1. Introduction\n\n As the Int 3213 delivery management path nested-reference unchanged"},{"id":"IETF RFC 3285","type":"specification","body":"IETF","designation":"RFC 3285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3285.txt","https://www.rfc-editor.org/rfc/rfc3285.pdf"],"folder":"IETF/RFC-3285","files":{"txt":{"path":"standards/IETF/RFC-3285/RFC-3285.txt","sha256":"75f2fbe8851efff7a0fbd3e14e71806ba37bad6369204ea784b6982d25d55dfc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the steps to configure the Microsoft Word\n application to produce documents in Internet Draft and RFC format.","scope_keywords":["3285","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"IETF RFC 3285 This document describes the steps to configure the Microsoft Word\n application to produce documents in Internet Draft and RFC format. 3285 crl nested-reference unchanged"},{"id":"IETF RFC 6949","type":"specification","body":"IETF","designation":"RFC 6949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6949.txt","https://www.rfc-editor.org/rfc/rfc6949.pdf"],"folder":"IETF/RFC-6949","files":{"txt":{"path":"standards/IETF/RFC-6949/RFC-6949.txt","sha256":"21e315d5f1a40694f3df7308e758337236ebb8f4c4773856a47324ce1c87cd60"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the current requirements and requests for\n enhancements for the format of the canonical version of RFCs. Terms\n are defined to help clarify exactly which stages of document\n production are under discussion for format changes. The requirements\n described in this document will determine what changes will be made\n to RFC format. This document updates RFC 2223.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abo","scope_keywords":["6949","driving","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null},{"body":"IETF","designation":"RFC 7998","folder":"IETF/RFC-7998","source":"IETF/RFC-7998/RFC-7998.txt","version":null}],"search_text":"IETF RFC 6949 This document describes the current requirements and requests for\n enhancements for the format of the canonical version of RFCs. Terms\n are defined to help clarify exactly which stages of document\n production are under discussion for format changes. The requirements\n described in this document will determine what changes will be made\n to RFC format. This document updates RFC 2223.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information abo 6949 driving http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2601","type":"specification","body":"IETF","designation":"RFC 2601","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2601.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2601.txt","https://www.rfc-editor.org/rfc/rfc2601.pdf"],"folder":"IETF/RFC-2601","files":{"txt":{"path":"standards/IETF/RFC-2601/RFC-2601.txt","sha256":"455ffefcf2352874755d0192cfaccb6e228dac3284ddbb2357e47b7b1b60ace9"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate ATMARP servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use ATMARP [1] is\n cumbersome and error-prone since it requires at least one ATM address\n to be statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use ATMARP\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the in","scope_keywords":["2601","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2601 This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate ATMARP servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use ATMARP [1] is\n cumbersome and error-prone since it requires at least one ATM address\n to be statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use ATMARP\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the in 2601 management nested-reference unchanged"},{"id":"IETF RFC 2226","type":"specification","body":"IETF","designation":"RFC 2226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2226.txt","https://www.rfc-editor.org/rfc/rfc2226.pdf"],"folder":"IETF/RFC-2226","files":{"txt":{"path":"standards/IETF/RFC-2226/RFC-2226.txt","sha256":"f5635bed0f8e63ccb43799d68c939d39a1efe8e91d61efb8e31d455d4bdc174f"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes how the IP multicast service being developed by\n the IP over ATM working group may be used to support IP broadcast\n transmission. The solution revolves around treating the broadcast\n problem as a special case of multicast, where every host in the\n subnet or cluster is a member of the group.\n\n An understanding of the services provided by RFC 2022 is assumed.\n\n1. Introduction.\n\n The IETF's first step in solving the problems of running IP over\n Asynchronous Transfer Mode (ATM) technology is described in RFC 1577\n [1]. It provides for unicast communication between hosts and routers\n within Logical IP Subnets (LISs), and proposes a centralized ATM ARP\n Server which provides IP to ATM address resolution services to LIS\n members.\n\n Two classes of IP service were omitted - multicast and broadcast\n transmissions. Multicasting allows a single transmit operation to\n cause a pack","scope_keywords":["2226","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2226 This memo describes how the IP multicast service being developed by\n the IP over ATM working group may be used to support IP broadcast\n transmission. The solution revolves around treating the broadcast\n problem as a special case of multicast, where every host in the\n subnet or cluster is a member of the group.\n\n An understanding of the services provided by RFC 2022 is assumed.\n\n1. Introduction.\n\n The IETF's first step in solving the problems of running IP over\n Asynchronous Transfer Mode (ATM) technology is described in RFC 1577\n [1]. It provides for unicast communication between hosts and routers\n within Logical IP Subnets (LISs), and proposes a centralized ATM ARP\n Server which provides IP to ATM address resolution services to LIS\n members.\n\n Two classes of IP service were omitted - multicast and broadcast\n transmissions. Multicasting allows a single transmit operation to\n cause a pack 2226 key management nested-reference unchanged"},{"id":"IETF RFC 2773","type":"specification","body":"IETF","designation":"RFC 2773","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2773.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2773.txt","https://www.rfc-editor.org/rfc/rfc2773.pdf"],"folder":"IETF/RFC-2773","files":{"txt":{"path":"standards/IETF/RFC-2773/RFC-2773.txt","sha256":"cc023c4c201e25c4dac546ed29b29e7b2ace3b9d4c044a4d0afbf05d4e203ed2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a method to encrypt a file transfer using the\n FTP specification STD 9, RFC 959, \"File Transfer Protocol (FTP)\",\n (October 1985) [3] and RFC 2228, \"FTP Security Extensions\" (October\n 1997) [1]. This method will use the Key Exchange Algorithm (KEA) to\n give mutual authentication and establish the data encryption keys.\n SKIPJACK is used to encrypt file data and the FTP command channel.","scope_keywords":["2773","algorithm","attribute","attributes","authentication","certificate","certificates","encryption","key","keys","path","profile","profiles","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2773 This document defines a method to encrypt a file transfer using the\n FTP specification STD 9, RFC 959, \"File Transfer Protocol (FTP)\",\n (October 1985) [3] and RFC 2228, \"FTP Security Extensions\" (October\n 1997) [1]. This method will use the Key Exchange Algorithm (KEA) to\n give mutual authentication and establish the data encryption keys.\n SKIPJACK is used to encrypt file data and the FTP command channel. 2773 algorithm attribute attributes authentication certificate certificates encryption key keys path profile profiles validation nested-reference unchanged"},{"id":"IETF RFC 2232","type":"specification","body":"IETF","designation":"RFC 2232","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2232.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2232.txt","https://www.rfc-editor.org/rfc/rfc2232.pdf"],"folder":"IETF/RFC-2232","files":{"txt":{"path":"standards/IETF/RFC-2232/RFC-2232.txt","sha256":"026d7a4add0946845b66a548bfdf21097d6cef8581294db6a5264605adbdb556"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Clouston, Editor\nRequest for Comments: 2232 Cisco Systems\nCategory: Standards Track B. Moore, Editor\n IBM Corporation\n November 1997\n\n Definitions of Managed Objects\n for DLUR using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Status of this Memo .................................... 1\n 2. Introduction ........................................... 1\n 3. The SNMP Network Management Framework .................. 2\n 4. Overview ..................","scope_keywords":["2232","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2232 Network Working Group B. Clouston, Editor\nRequest for Comments: 2232 Cisco Systems\nCategory: Standards Track B. Moore, Editor\n IBM Corporation\n November 1997\n\n Definitions of Managed Objects\n for DLUR using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Status of this Memo .................................... 1\n 2. Introduction ........................................... 1\n 3. The SNMP Network Management Framework .................. 2\n 4. Overview .................. 2232 identification management nested-reference unchanged"},{"id":"IETF RFC 2234","type":"specification","body":"IETF","designation":"RFC 2234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2234.txt","https://www.rfc-editor.org/rfc/rfc2234.pdf"],"folder":"IETF/RFC-2234","files":{"txt":{"path":"standards/IETF/RFC-2234/RFC-2234.txt","sha256":"dcaf77997b83a9a0bda70bc00aa4670c084087e86b4aed57f5b705dfef6eb9ca"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker, Ed.\nRequest for Comments: 2234 Internet Mail Consortium\nCategory: Standards Track P. Overell\n Demon Internet Ltd.\n November 1997\n\n Augmented BNF for Syntax Specifications: ABNF\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 2\n\n 2. RULE DEFINITION ............................................... 2\n 2.1 RULE NAMING .................................................. 2\n 2.2 RULE F","scope_keywords":["2234","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2245","folder":"IETF/RFC-2245","source":"IETF/RFC-2245/RFC-2245.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2342","folder":"IETF/RFC-2342","source":"IETF/RFC-2342/RFC-2342.txt","version":null},{"body":"IETF","designation":"RFC 2373","folder":"IETF/RFC-2373","source":"IETF/RFC-2373/RFC-2373.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2389","folder":"IETF/RFC-2389","source":"IETF/RFC-2389/RFC-2389.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2530","folder":"IETF/RFC-2530","source":"IETF/RFC-2530/RFC-2530.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2569","folder":"IETF/RFC-2569","source":"IETF/RFC-2569/RFC-2569.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2648","folder":"IETF/RFC-2648","source":"IETF/RFC-2648/RFC-2648.txt","version":null},{"body":"IETF","designation":"RFC 2653","folder":"IETF/RFC-2653","source":"IETF/RFC-2653/RFC-2653.txt","version":null},{"body":"IETF","designation":"RFC 2673","folder":"IETF/RFC-2673","source":"IETF/RFC-2673/RFC-2673.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2738","folder":"IETF/RFC-2738","source":"IETF/RFC-2738/RFC-2738.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2812","folder":"IETF/RFC-2812","source":"IETF/RFC-2812/RFC-2812.txt","version":null},{"body":"IETF","designation":"RFC 2813","folder":"IETF/RFC-2813","source":"IETF/RFC-2813/RFC-2813.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2849","folder":"IETF/RFC-2849","source":"IETF/RFC-2849/RFC-2849.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 2913","folder":"IETF/RFC-2913","source":"IETF/RFC-2913/RFC-2913.txt","version":null},{"body":"IETF","designation":"RFC 2915","folder":"IETF/RFC-2915","source":"IETF/RFC-2915/RFC-2915.txt","version":null},{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 2938","folder":"IETF/RFC-2938","source":"IETF/RFC-2938/RFC-2938.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3081","folder":"IETF/RFC-3081","source":"IETF/RFC-3081/RFC-3081.txt","version":null},{"body":"IETF","designation":"RFC 3082","folder":"IETF/RFC-3082","source":"IETF/RFC-3082/RFC-3082.txt","version":null},{"body":"IETF","designation":"RFC 3084","folder":"IETF/RFC-3084","source":"IETF/RFC-3084/RFC-3084.txt","version":null},{"body":"IETF","designation":"RFC 3085","folder":"IETF/RFC-3085","source":"IETF/RFC-3085/RFC-3085.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3112","folder":"IETF/RFC-3112","source":"IETF/RFC-3112/RFC-3112.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3266","folder":"IETF/RFC-3266","source":"IETF/RFC-3266/RFC-3266.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3325","folder":"IETF/RFC-3325","source":"IETF/RFC-3325/RFC-3325.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3348","folder":"IETF/RFC-3348","source":"IETF/RFC-3348/RFC-3348.txt","version":null},{"body":"IETF","designation":"RFC 3368","folder":"IETF/RFC-3368","source":"IETF/RFC-3368/RFC-3368.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3420","folder":"IETF/RFC-3420","source":"IETF/RFC-3420/RFC-3420.txt","version":null},{"body":"IETF","designation":"RFC 3421","folder":"IETF/RFC-3421","source":"IETF/RFC-3421/RFC-3421.txt","version":null},{"body":"IETF","designation":"RFC 3431","folder":"IETF/RFC-3431","source":"IETF/RFC-3431/RFC-3431.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3458","folder":"IETF/RFC-3458","source":"IETF/RFC-3458/RFC-3458.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3460","folder":"IETF/RFC-3460","source":"IETF/RFC-3460/RFC-3460.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3502","folder":"IETF/RFC-3502","source":"IETF/RFC-3502/RFC-3502.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3516","folder":"IETF/RFC-3516","source":"IETF/RFC-3516/RFC-3516.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 3617","folder":"IETF/RFC-3617","source":"IETF/RFC-3617/RFC-3617.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3656","folder":"IETF/RFC-3656","source":"IETF/RFC-3656/RFC-3656.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3676","folder":"IETF/RFC-3676","source":"IETF/RFC-3676/RFC-3676.txt","version":null},{"body":"IETF","designation":"RFC 3691","folder":"IETF/RFC-3691","source":"IETF/RFC-3691/RFC-3691.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3781","folder":"IETF/RFC-3781","source":"IETF/RFC-3781/RFC-3781.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3842","folder":"IETF/RFC-3842","source":"IETF/RFC-3842/RFC-3842.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3865","folder":"IETF/RFC-3865","source":"IETF/RFC-3865/RFC-3865.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 3885","folder":"IETF/RFC-3885","source":"IETF/RFC-3885/RFC-3885.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3958","folder":"IETF/RFC-3958","source":"IETF/RFC-3958/RFC-3958.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4004","folder":"IETF/RFC-4004","source":"IETF/RFC-4004/RFC-4004.txt","version":null},{"body":"IETF","designation":"RFC 4088","folder":"IETF/RFC-4088","source":"IETF/RFC-4088/RFC-4088.txt","version":null},{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4168","folder":"IETF/RFC-4168","source":"IETF/RFC-4168/RFC-4168.txt","version":null},{"body":"IETF","designation":"RFC 4179","folder":"IETF/RFC-4179","source":"IETF/RFC-4179/RFC-4179.txt","version":null},{"body":"IETF","designation":"RFC 4180","folder":"IETF/RFC-4180","source":"IETF/RFC-4180/RFC-4180.txt","version":null},{"body":"IETF","designation":"RFC 4234","folder":"IETF/RFC-4234","source":"IETF/RFC-4234/RFC-4234.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null}],"search_text":"IETF RFC 2234 Network Working Group D. Crocker, Ed.\nRequest for Comments: 2234 Internet Mail Consortium\nCategory: Standards Track P. Overell\n Demon Internet Ltd.\n November 1997\n\n Augmented BNF for Syntax Specifications: ABNF\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 2\n\n 2. RULE DEFINITION ............................................... 2\n 2.1 RULE NAMING .................................................. 2\n 2.2 RULE F 2234 crl presentation nested-reference unchanged"},{"id":"IETF RFC 2738","type":"specification","body":"IETF","designation":"RFC 2738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2738.txt","https://www.rfc-editor.org/rfc/rfc2738.pdf"],"folder":"IETF/RFC-2738","files":{"txt":{"path":"standards/IETF/RFC-2738/RFC-2738.txt","sha256":"344d7e00e2e6466713405c7ea63249599488e60e18520b31a14799ce76995500"}},"tags":["nested-reference","unchanged"],"summary":"In RFC 2533, \"A Syntax for Describing Media Feature Sets\", an\n expression format is presented for describing media feature\n capabilities using simple media feature tags.\n\n This memo contains two corrections to that specification: one fixes\n an error in the formal syntax specification, and the other fixes an\n error in the rules for reducing feature comparison predicates.","scope_keywords":["2738","algorithm","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3840","folder":"IETF/RFC-3840","source":"IETF/RFC-3840/RFC-3840.txt","version":null}],"search_text":"IETF RFC 2738 In RFC 2533, \"A Syntax for Describing Media Feature Sets\", an\n expression format is presented for describing media feature\n capabilities using simple media feature tags.\n\n This memo contains two corrections to that specification: one fixes\n an error in the formal syntax specification, and the other fixes an\n error in the rules for reducing feature comparison predicates. 2738 algorithm http nested-reference unchanged"},{"id":"IETF RFC 4234","type":"specification","body":"IETF","designation":"RFC 4234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4234.txt","https://www.rfc-editor.org/rfc/rfc4234.pdf"],"folder":"IETF/RFC-4234","files":{"txt":{"path":"standards/IETF/RFC-4234/RFC-4234.txt","sha256":"4b912796ffd6fe0a00e900ba2c2b77f2a85e468b0648f47503436eadb5af8277"}},"tags":["nested-reference","unchanged"],"summary":"Internet technical specifications often need to define a formal\n syntax. Over the years, a modified version of Backus-Naur Form\n (BNF), called Augmented BNF (ABNF), has been popular among many\n Internet specifications. The current specification documents ABNF.\n It balances compactness and simplicity, with reasonable\n representational power. The differences between standard BNF and\n ABNF involve naming rules, repetition, alternatives, order-\n independence, and value ranges. This specification also supplies\n additional rule definitions and encoding for a core lexical analyzer\n of the type common to several Internet specifications.\n\nCrocker & Overell Standards Track [Page 1]\n\f\nRFC 4234 ABNF October 2005","scope_keywords":["4234","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4284","folder":"IETF/RFC-4284","source":"IETF/RFC-4284/RFC-4284.txt","version":null},{"body":"IETF","designation":"RFC 4288","folder":"IETF/RFC-4288","source":"IETF/RFC-4288/RFC-4288.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4315","folder":"IETF/RFC-4315","source":"IETF/RFC-4315/RFC-4315.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4466","folder":"IETF/RFC-4466","source":"IETF/RFC-4466/RFC-4466.txt","version":null},{"body":"IETF","designation":"RFC 4467","folder":"IETF/RFC-4467","source":"IETF/RFC-4467/RFC-4467.txt","version":null},{"body":"IETF","designation":"RFC 4468","folder":"IETF/RFC-4468","source":"IETF/RFC-4468/RFC-4468.txt","version":null},{"body":"IETF","designation":"RFC 4469","folder":"IETF/RFC-4469","source":"IETF/RFC-4469/RFC-4469.txt","version":null},{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4501","folder":"IETF/RFC-4501","source":"IETF/RFC-4501/RFC-4501.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4551","folder":"IETF/RFC-4551","source":"IETF/RFC-4551/RFC-4551.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4567","folder":"IETF/RFC-4567","source":"IETF/RFC-4567/RFC-4567.txt","version":null},{"body":"IETF","designation":"RFC 4568","folder":"IETF/RFC-4568","source":"IETF/RFC-4568/RFC-4568.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4574","folder":"IETF/RFC-4574","source":"IETF/RFC-4574/RFC-4574.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4583","folder":"IETF/RFC-4583","source":"IETF/RFC-4583/RFC-4583.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4627","folder":"IETF/RFC-4627","source":"IETF/RFC-4627/RFC-4627.txt","version":null},{"body":"IETF","designation":"RFC 4642","folder":"IETF/RFC-4642","source":"IETF/RFC-4642/RFC-4642.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4644","folder":"IETF/RFC-4644","source":"IETF/RFC-4644/RFC-4644.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4647","folder":"IETF/RFC-4647","source":"IETF/RFC-4647/RFC-4647.txt","version":null},{"body":"IETF","designation":"RFC 4661","folder":"IETF/RFC-4661","source":"IETF/RFC-4661/RFC-4661.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null},{"body":"IETF","designation":"RFC 4730","folder":"IETF/RFC-4730","source":"IETF/RFC-4730/RFC-4730.txt","version":null},{"body":"IETF","designation":"RFC 4731","folder":"IETF/RFC-4731","source":"IETF/RFC-4731/RFC-4731.txt","version":null},{"body":"IETF","designation":"RFC 4759","folder":"IETF/RFC-4759","source":"IETF/RFC-4759/RFC-4759.txt","version":null},{"body":"IETF","designation":"RFC 4770","folder":"IETF/RFC-4770","source":"IETF/RFC-4770/RFC-4770.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4796","folder":"IETF/RFC-4796","source":"IETF/RFC-4796/RFC-4796.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4848","folder":"IETF/RFC-4848","source":"IETF/RFC-4848/RFC-4848.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4904","folder":"IETF/RFC-4904","source":"IETF/RFC-4904/RFC-4904.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4959","folder":"IETF/RFC-4959","source":"IETF/RFC-4959/RFC-4959.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4978","folder":"IETF/RFC-4978","source":"IETF/RFC-4978/RFC-4978.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5231","folder":"IETF/RFC-5231","source":"IETF/RFC-5231/RFC-5231.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null}],"search_text":"IETF RFC 4234 Internet technical specifications often need to define a formal\n syntax. Over the years, a modified version of Backus-Naur Form\n (BNF), called Augmented BNF (ABNF), has been popular among many\n Internet specifications. The current specification documents ABNF.\n It balances compactness and simplicity, with reasonable\n representational power. The differences between standard BNF and\n ABNF involve naming rules, repetition, alternatives, order-\n independence, and value ranges. This specification also supplies\n additional rule definitions and encoding for a core lexical analyzer\n of the type common to several Internet specifications.\n\nCrocker & Overell Standards Track [Page 1]\n\f\nRFC 4234 ABNF October 2005 4234 crl presentation nested-reference unchanged"},{"id":"IETF RFC 2235","type":"specification","body":"IETF","designation":"RFC 2235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2235.txt","https://www.rfc-editor.org/rfc/rfc2235.pdf"],"folder":"IETF/RFC-2235","files":{"txt":{"path":"standards/IETF/RFC-2235/RFC-2235.txt","sha256":"04251f8d01ddc400d874b878b19f9cf59a36404b0ab71ad3c24cc250159a0359"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Zakon\nRequest for Comments: 2235 MITRE\nFYI: 32 November 1997\nCategory: Informational\n\n Hobbes' Internet Timeline\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) Robert H. Zakon and The Internet Society (1997).\n All Rights Reserved.\n\n1. Introduction\n\n This document presents a history of the Internet in timeline fashion,\n highlighting some of the key events and technologies which helped\n shape the Internet as we know it today. A growth summary of the\n Internet and some associated technologies is also included.\n\n2. Hobbes' Internet Timeline\n\n Excerpted from the author's copyrighted work of the same name. The\n most current version of Hobbes' Internet Timeline is available at\n http://info.isoc.org/guest/zak","scope_keywords":["2235","http","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2324","folder":"IETF/RFC-2324","source":"IETF/RFC-2324/RFC-2324.txt","version":null}],"search_text":"IETF RFC 2235 Network Working Group R. Zakon\nRequest for Comments: 2235 MITRE\nFYI: 32 November 1997\nCategory: Informational\n\n Hobbes' Internet Timeline\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) Robert H. Zakon and The Internet Society (1997).\n All Rights Reserved.\n\n1. Introduction\n\n This document presents a history of the Internet in timeline fashion,\n highlighting some of the key events and technologies which helped\n shape the Internet as we know it today. A growth summary of the\n Internet and some associated technologies is also included.\n\n2. Hobbes' Internet Timeline\n\n Excerpted from the author's copyrighted work of the same name. The\n most current version of Hobbes' Internet Timeline is available at\n http://info.isoc.org/guest/zak 2235 http key management nested-reference unchanged"},{"id":"IETF RFC 3228","type":"specification","body":"IETF","designation":"RFC 3228","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3228.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3228.txt","https://www.rfc-editor.org/rfc/rfc3228.pdf"],"folder":"IETF/RFC-3228","files":{"txt":{"path":"standards/IETF/RFC-3228/RFC-3228.txt","sha256":"8075afbd10b58f3ae2abf19e51143177ee2948e4a1dc3ffa0e950569bccb37ba"}},"tags":["nested-reference","unchanged"],"summary":"This memo requests that the IANA create a registry for fields in the\n IGMP (Internet Group Management Protocol) protocol header, and\n provides guidance for the IANA to use in assigning parameters for\n those fields.","scope_keywords":["3228","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3376","folder":"IETF/RFC-3376","source":"IETF/RFC-3376/RFC-3376.txt","version":null},{"body":"IETF","designation":"RFC 3488","folder":"IETF/RFC-3488","source":"IETF/RFC-3488/RFC-3488.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 3228 This memo requests that the IANA create a registry for fields in the\n IGMP (Internet Group Management Protocol) protocol header, and\n provides guidance for the IANA to use in assigning parameters for\n those fields. 3228 management policy nested-reference unchanged"},{"id":"IETF RFC 6224","type":"specification","body":"IETF","designation":"RFC 6224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6224.txt","https://www.rfc-editor.org/rfc/rfc6224.pdf"],"folder":"IETF/RFC-6224","files":{"txt":{"path":"standards/IETF/RFC-6224/RFC-6224.txt","sha256":"a85bd5b0e0ccc160cea2cf14c4b828aac4003b07881e5fdf780a96b2c682f2e1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes deployment options for activating multicast\n listener functions in Proxy Mobile IPv6 domains without modifying\n mobility and multicast protocol standards. Similar to home agents in\n Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as\n multicast subscription anchor points, while Mobile Access Gateways\n provide Multicast Listener Discovery (MLD) proxy functions. In this\n scenario, mobile nodes remain agnostic of multicast mobility\n operations. Support for mobile multicast senders is outside the\n scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n In","scope_keywords":["6224","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6636","folder":"IETF/RFC-6636","source":"IETF/RFC-6636/RFC-6636.txt","version":null}],"search_text":"IETF RFC 6224 This document describes deployment options for activating multicast\n listener functions in Proxy Mobile IPv6 domains without modifying\n mobility and multicast protocol standards. Similar to home agents in\n Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as\n multicast subscription anchor points, while Mobile Access Gateways\n provide Multicast Listener Discovery (MLD) proxy functions. In this\n scenario, mobile nodes remain agnostic of multicast mobility\n operations. Support for mobile multicast senders is outside the\n scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n In 6224 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 2238","type":"specification","body":"IETF","designation":"RFC 2238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2238.txt","https://www.rfc-editor.org/rfc/rfc2238.pdf"],"folder":"IETF/RFC-2238","files":{"txt":{"path":"standards/IETF/RFC-2238/RFC-2238.txt","sha256":"6511d0f9ff8db9912efc6a11374577b36a5295403f9cd3c6e3108ca3e46e0ccf"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Clouston, Editor\nRequest for Comments: 2238 Cisco Systems\nCategory: Standards Track B. Moore, Editor\n IBM Corporation\n November 1997\n\n Definitions of Managed Objects\n for HPR using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Status of this Memo ..................................... 1\n 2. Introduction ............................................ 1\n 3. The SNMP Network Management Framework ................... 2\n 4. Overview ................","scope_keywords":["2238","algorithm","http","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2238 Network Working Group B. Clouston, Editor\nRequest for Comments: 2238 Cisco Systems\nCategory: Standards Track B. Moore, Editor\n IBM Corporation\n November 1997\n\n Definitions of Managed Objects\n for HPR using SMIv2\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nTable of Contents\n\n 1. Status of this Memo ..................................... 1\n 2. Introduction ............................................ 1\n 3. The SNMP Network Management Framework ................... 2\n 4. Overview ................ 2238 algorithm http management path pid nested-reference unchanged"},{"id":"IETF RFC 2241","type":"specification","body":"IETF","designation":"RFC 2241","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2241.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2241.txt","https://www.rfc-editor.org/rfc/rfc2241.pdf"],"folder":"IETF/RFC-2241","files":{"txt":{"path":"standards/IETF/RFC-2241/RFC-2241.txt","sha256":"8d163342b066228f932dd4e074cf6a86701ef68bec268b8736d241da35c9766e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Provan\nRequest for Comments: 2241 Novell, Inc.\nCategory: Standards Track November 1997\n\n DHCP Options for Novell Directory Services\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n This document defines three new DHCP options for delivering\n configuration information to clients of the Novell Directory\n Services. The first option carries a list of NDS servers. The second\n option carries the name of the client's NDS tree. The third carries\n the initial NDS contex","scope_keywords":["2241","authentication","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2241 Network Working Group D. Provan\nRequest for Comments: 2241 Novell, Inc.\nCategory: Standards Track November 1997\n\n DHCP Options for Novell Directory Services\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1997). All Rights Reserved.\n\nAbstract\n\n This document defines three new DHCP options for delivering\n configuration information to clients of the Novell Directory\n Services. The first option carries a list of NDS servers. The second\n option carries the name of the client's NDS tree. The third carries\n the initial NDS contex 2241 authentication key nested-reference unchanged"},{"id":"IETF RFC 2242","type":"specification","body":"IETF","designation":"RFC 2242","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2242.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2242.txt","https://www.rfc-editor.org/rfc/rfc2242.pdf"],"folder":"IETF/RFC-2242","files":{"txt":{"path":"standards/IETF/RFC-2242/RFC-2242.txt","sha256":"2fe03dcd0e4ef5f913acfa0ce9f290ccd75996e82535910e44a454fff918f458"}},"tags":["nested-reference","unchanged"],"summary":"The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. DHCP includes options for specific configuration parameters\n [RFC 2132]. This document defines options that carry NetWare/IP\n domain name and NetWare/IP sub-options to DHCP clients.","scope_keywords":["2242","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2242 The Dynamic Host Configuration Protocol (DHCP) [RFC 2131] provides a\n framework for passing configuration information to hosts on a TCP/IP\n network. DHCP includes options for specific configuration parameters\n [RFC 2132]. This document defines options that carry NetWare/IP\n domain name and NetWare/IP sub-options to DHCP clients. 2242 key nested-reference unchanged"},{"id":"IETF RFC 4505","type":"specification","body":"IETF","designation":"RFC 4505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4505.txt","https://www.rfc-editor.org/rfc/rfc4505.pdf"],"folder":"IETF/RFC-4505","files":{"txt":{"path":"standards/IETF/RFC-4505/RFC-4505.txt","sha256":"4711c4d80bf0c44c50ba9b8eb4106ca0fb06e652a0b60ce233b0acd12ab8a6c4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Zeilenga, Ed.\nRequest for Comments: 4505 OpenLDAP Foundation\nObsoletes: 2245 June 2006\nCategory: Standards Track\n\n Anonymous Simple Authentication and Security Layer (SASL) Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n On the Internet, it is common practice to permit anonymous access to\n various services. Traditionally, this has been done with a plain-\n text password mechanism using \"anonymous\" as the user name and using\n optional trace information, such as an email ad","scope_keywords":["4505","authentication","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null}],"search_text":"IETF RFC 4505 Network Working Group K. Zeilenga, Ed.\nRequest for Comments: 4505 OpenLDAP Foundation\nObsoletes: 2245 June 2006\nCategory: Standards Track\n\n Anonymous Simple Authentication and Security Layer (SASL) Mechanism\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n On the Internet, it is common practice to permit anonymous access to\n various services. Traditionally, this has been done with a plain-\n text password mechanism using \"anonymous\" as the user name and using\n optional trace information, such as an email ad 4505 authentication profile profiles nested-reference unchanged"},{"id":"IETF RFC 2628","type":"specification","body":"IETF","designation":"RFC 2628","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2628.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2628.txt","https://www.rfc-editor.org/rfc/rfc2628.pdf"],"folder":"IETF/RFC-2628","files":{"txt":{"path":"standards/IETF/RFC-2628/RFC-2628.txt","sha256":"520acf67753872150ccdbafcc4125121cbee198c30ccb651a7722764f20fcfb8"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple Application Program Interface to\n cryptographic functions. The main purpose of such an interface is to\n separate cryptographic libraries from internet applications, thus\n allowing an independent development of both. It can be used in\n various internet applications such as [IPsec], [ISAKMP], [IKE],\n [TLS].","scope_keywords":["2628","algorithm","algorithms","encryption","hash","key","signature","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2628 This document describes a simple Application Program Interface to\n cryptographic functions. The main purpose of such an interface is to\n separate cryptographic libraries from internet applications, thus\n allowing an independent development of both. It can be used in\n various internet applications such as [IPsec], [ISAKMP], [IKE],\n [TLS]. 2628 algorithm algorithms encryption hash key signature tls nested-reference unchanged"},{"id":"IETF RFC 2719","type":"specification","body":"IETF","designation":"RFC 2719","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2719.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2719.txt","https://www.rfc-editor.org/rfc/rfc2719.pdf"],"folder":"IETF/RFC-2719","files":{"txt":{"path":"standards/IETF/RFC-2719/RFC-2719.txt","sha256":"29c7144510eb62f0aee85912e6fcb1e1f90a5bc861cd9e9688d624cc4e8b5fbf"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an architecture framework and functional\n requirements for transport of signaling information over IP. The\n framework describes relationships between functional and physical\n entities exchanging signaling information, such as Signaling Gateways\n and Media Gateway Controllers. It identifies interfaces where\n signaling transport may be used and the functional and performance\n requirements that apply from existing Switched Circuit Network (SCN)\n signaling protocols.\n\nOng, et al. Informational [Page 1]\n\f\nRFC 2719 Framework Architecture for Signaling Transport October 1999","scope_keywords":["2719","delivery","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 4040","folder":"IETF/RFC-4040","source":"IETF/RFC-4040/RFC-4040.txt","version":null}],"search_text":"IETF RFC 2719 This document defines an architecture framework and functional\n requirements for transport of signaling information over IP. The\n framework describes relationships between functional and physical\n entities exchanging signaling information, such as Signaling Gateways\n and Media Gateway Controllers. It identifies interfaces where\n signaling transport may be used and the functional and performance\n requirements that apply from existing Switched Circuit Network (SCN)\n signaling protocols.\n\nOng, et al. Informational [Page 1]\n\f\nRFC 2719 Framework Architecture for Signaling Transport October 1999 2719 delivery management policy nested-reference unchanged"},{"id":"IETF RFC 3268","type":"specification","body":"IETF","designation":"RFC 3268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3268.txt","https://www.rfc-editor.org/rfc/rfc3268.pdf"],"folder":"IETF/RFC-3268","files":{"txt":{"path":"standards/IETF/RFC-3268/RFC-3268.txt","sha256":"3d1c829799254ed79f84a6424030cebf60d77816fee1675509b0d7f81d5b552f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Chown\nRequest for Comments: 3268 Skygate Technology\nCategory: Standards Track June 2002\n\n Advanced Encryption Standard (AES) Ciphersuites for Transport Layer\n Security (TLS)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document proposes several new ciphersuites. At present, the\n symmetric ciphers supported by Transport Layer Security (TLS) are\n RC2, RC4, International Data Encryption Algorithm (IDEA), Data\n Encryption Standard (DES), and triple DES. Th","scope_keywords":["3268","algorithm","authentication","certificate","encryption","key","keys","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3767","folder":"IETF/RFC-3767","source":"IETF/RFC-3767/RFC-3767.txt","version":null},{"body":"IETF","designation":"RFC 3983","folder":"IETF/RFC-3983","source":"IETF/RFC-3983/RFC-3983.txt","version":null},{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4851","folder":"IETF/RFC-4851","source":"IETF/RFC-4851/RFC-4851.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 4976","folder":"IETF/RFC-4976","source":"IETF/RFC-4976/RFC-4976.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5216","folder":"IETF/RFC-5216","source":"IETF/RFC-5216/RFC-5216.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null}],"search_text":"IETF RFC 3268 Network Working Group P. Chown\nRequest for Comments: 3268 Skygate Technology\nCategory: Standards Track June 2002\n\n Advanced Encryption Standard (AES) Ciphersuites for Transport Layer\n Security (TLS)\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document proposes several new ciphersuites. At present, the\n symmetric ciphers supported by Transport Layer Security (TLS) are\n RC2, RC4, International Data Encryption Algorithm (IDEA), Data\n Encryption Standard (DES), and triple DES. Th 3268 algorithm authentication certificate encryption key keys subject tls nested-reference unchanged"},{"id":"IETF RFC 3989","type":"specification","body":"IETF","designation":"RFC 3989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3989.txt","https://www.rfc-editor.org/rfc/rfc3989.pdf"],"folder":"IETF/RFC-3989","files":{"txt":{"path":"standards/IETF/RFC-3989/RFC-3989.txt","sha256":"d7914e8cdd61cccd1e751dc90fb54bede1da52fa6f21d9a58e62abd2bba337e1"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies semantics for a Middlebox Communication (MIDCOM)\n protocol to be used by MIDCOM agents for interacting with middleboxes\n such as firewalls and Network Address Translators (NATs). The\n semantics discussion does not include any specification of a concrete\n syntax or a transport protocol. However, a concrete protocol is\n expected to implement the specified semantics or, more likely, a\n superset of it. The MIDCOM protocol semantics is derived from the\n MIDCOM requirements, from the MIDCOM framework, and from working\n group decisions.","scope_keywords":["3989","authentication","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5190","folder":"IETF/RFC-5190","source":"IETF/RFC-5190/RFC-5190.txt","version":null}],"search_text":"IETF RFC 3989 This memo specifies semantics for a Middlebox Communication (MIDCOM)\n protocol to be used by MIDCOM agents for interacting with middleboxes\n such as firewalls and Network Address Translators (NATs). The\n semantics discussion does not include any specification of a concrete\n syntax or a transport protocol. However, a concrete protocol is\n expected to implement the specified semantics or, more likely, a\n superset of it. The MIDCOM protocol semantics is derived from the\n MIDCOM requirements, from the MIDCOM framework, and from working\n group decisions. 3989 authentication policy trust nested-reference unchanged"},{"id":"IETF RFC 4297","type":"specification","body":"IETF","designation":"RFC 4297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4297.txt","https://www.rfc-editor.org/rfc/rfc4297.pdf"],"folder":"IETF/RFC-4297","files":{"txt":{"path":"standards/IETF/RFC-4297/RFC-4297.txt","sha256":"22669ba2dc9096975b46c8b085755b72ca3ea0a753aa3003ca15848f4bedf815"}},"tags":["nested-reference","unchanged"],"summary":"Overhead due to the movement of user data in the end-system network\n I/O processing path at high speeds is significant, and has limited\n the use of Internet protocols in interconnection networks, and the\n Internet itself -- especially where high bandwidth, low latency,\n and/or low overhead are required by the hosted application.\n\n This document examines this overhead, and addresses an architectural,\n IP-based \"copy avoidance\" solution for its elimination, by enabling\n Remote Direct Memory Access (RDMA).\n\nRomanow, et al. Informational [Page 1]\n\f\nRFC 4297 RDMA over IP Problem Statement December 2005","scope_keywords":["4297","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4296","folder":"IETF/RFC-4296","source":"IETF/RFC-4296/RFC-4296.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5532","folder":"IETF/RFC-5532","source":"IETF/RFC-5532/RFC-5532.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 4297 Overhead due to the movement of user data in the end-system network\n I/O processing path at high speeds is significant, and has limited\n the use of Internet protocols in interconnection networks, and the\n Internet itself -- especially where high bandwidth, low latency,\n and/or low overhead are required by the hosted application.\n\n This document examines this overhead, and addresses an architectural,\n IP-based \"copy avoidance\" solution for its elimination, by enabling\n Remote Direct Memory Access (RDMA).\n\nRomanow, et al. Informational [Page 1]\n\f\nRFC 4297 RDMA over IP Problem Statement December 2005 4297 key path nested-reference unchanged"},{"id":"IETF RFC 8744","type":"specification","body":"IETF","designation":"RFC 8744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8744.txt","https://www.rfc-editor.org/rfc/rfc8744.pdf"],"folder":"IETF/RFC-8744","files":{"pdf":{"path":"standards/IETF/RFC-8744/RFC-8744.pdf","sha256":"3a7a01ef22a0d00288550b373237ac6da4cb4dfc801dcba97a83d6705eb56b79"},"txt":{"path":"standards/IETF/RFC-8744/RFC-8744.txt","sha256":"5fc1c4937c46febbefbc93d276098a81badd0760c8dfad1ff185ed8417982151"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the general problem of encrypting the Server\n Name Identification (SNI) TLS parameter. The proposed solutions hide\n a hidden service behind a fronting service, only disclosing the SNI\n of the fronting service to external observers. This document lists\n known attacks against SNI encryption, discusses the current \"HTTP co-\n tenancy\" solution, and presents requirements for future TLS-layer\n solutions.\n\n In practice, it may well be that no solution can meet every\n requirement and that practical solutions will have to make some\n compromises.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by t","scope_keywords":["8744","delivery","encryption","http","https","identification","license","management","profile","profiles","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null}],"search_text":"IETF RFC 8744 This document describes the general problem of encrypting the Server\n Name Identification (SNI) TLS parameter. The proposed solutions hide\n a hidden service behind a fronting service, only disclosing the SNI\n of the fronting service to external observers. This document lists\n known attacks against SNI encryption, discusses the current \"HTTP co-\n tenancy\" solution, and presents requirements for future TLS-layer\n solutions.\n\n In practice, it may well be that no solution can meet every\n requirement and that practical solutions will have to make some\n compromises.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by t 8744 delivery encryption http https identification license management profile profiles subject tls trust nested-reference unchanged"},{"id":"IETF RFC 2589","type":"specification","body":"IETF","designation":"RFC 2589","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2589.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2589.txt","https://www.rfc-editor.org/rfc/rfc2589.pdf"],"folder":"IETF/RFC-2589","files":{"txt":{"path":"standards/IETF/RFC-2589/RFC-2589.txt","sha256":"21ff146adf30f04b6d121a7f4170a52043751a4036d8cbba5a6fb953cc9f02be"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the requirements for dynamic directory services\n and specifies the format of request and response extended operations\n for supporting client-server interoperation in a dynamic directories\n environment.\n\n The Lightweight Directory Access Protocol (LDAP) [1] supports\n lightweight access to static directory services, allowing relatively\n fast search and update access. Static directory services store\n information about people that persists in its accuracy and value over\n a long period of time.\n\n Dynamic directory services are different in that they store\n information that only persists in its accuracy and value when it is\n being periodically refreshed. This information is stored as dynamic\n entries in the directory. A typical use will be a client or a person\n that is either online - in which case it has an entry in the\n directory, or is offline - in which case its entry","scope_keywords":["2589","attribute","attributes","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2589 This document defines the requirements for dynamic directory services\n and specifies the format of request and response extended operations\n for supporting client-server interoperation in a dynamic directories\n environment.\n\n The Lightweight Directory Access Protocol (LDAP) [1] supports\n lightweight access to static directory services, allowing relatively\n fast search and update access. Static directory services store\n information about people that persists in its accuracy and value over\n a long period of time.\n\n Dynamic directory services are different in that they store\n information that only persists in its accuracy and value when it is\n being periodically refreshed. This information is stored as dynamic\n entries in the directory. A typical use will be a client or a person\n that is either online - in which case it has an entry in the\n directory, or is offline - in which case its entry 2589 attribute attributes registered subject nested-reference unchanged"},{"id":"IETF RFC 2739","type":"specification","body":"IETF","designation":"RFC 2739","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2739.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2739.txt","https://www.rfc-editor.org/rfc/rfc2739.pdf"],"folder":"IETF/RFC-2739","files":{"txt":{"path":"standards/IETF/RFC-2739/RFC-2739.txt","sha256":"cdb9e57239da0dd05a5865cb4f392b09a2aaa5019fe1a7ee0f7bf40c39e18aad"}},"tags":["nested-reference","unchanged"],"summary":"When scheduling a calendar entity, such as an event, it is a\n prerequisite that an organizer has the calendar address of each\n attendee that will be invited to the event. Additionally, access to\n an attendee's current \"busy time\" provides an a priori indication of\n whether the attendee will be free to participate in the event.\n\n In order to meet these challenges, a calendar user agent (CUA) needs\n a mechanism to locate (URI) individual user's calendar and free/busy\n time.\n\n This memo defines three mechanisms for obtaining a URI to a user's\n calendar and free/busy time. These include:\n\n - Manual transfer of the information;\n\n - Personal data exchange using the vCard format; and\n\n - Directory lookup using the LDAP protocol.\n\nSmall, et al. Standards Track [Page 1]\n\f\nRFC 2739 Locating a Calendar User January 2000","scope_keywords":["2739","attribute","attributes","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4791","folder":"IETF/RFC-4791","source":"IETF/RFC-4791/RFC-4791.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null}],"search_text":"IETF RFC 2739 When scheduling a calendar entity, such as an event, it is a\n prerequisite that an organizer has the calendar address of each\n attendee that will be invited to the event. Additionally, access to\n an attendee's current \"busy time\" provides an a priori indication of\n whether the attendee will be free to participate in the event.\n\n In order to meet these challenges, a calendar user agent (CUA) needs\n a mechanism to locate (URI) individual user's calendar and free/busy\n time.\n\n This memo defines three mechanisms for obtaining a URI to a user's\n calendar and free/busy time. These include:\n\n - Manual transfer of the information;\n\n - Personal data exchange using the vCard format; and\n\n - Directory lookup using the LDAP protocol.\n\nSmall, et al. Standards Track [Page 1]\n\f\nRFC 2739 Locating a Calendar User January 2000 2739 attribute attributes http nested-reference unchanged"},{"id":"IETF RFC 3377","type":"specification","body":"IETF","designation":"RFC 3377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3377.txt","https://www.rfc-editor.org/rfc/rfc3377.pdf"],"folder":"IETF/RFC-3377","files":{"txt":{"path":"standards/IETF/RFC-3377/RFC-3377.txt","sha256":"11db7df9dedd7f703fe33affd529316013d9ee9a348f5d09e7f7efd5996a1f35"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Hodges\nRequest for Comments: 3377 Sun Microsystems Inc.\nCategory: Standards Track R. Morgan\n University of Washington\n September 2002\n\n Lightweight Directory Access Protocol (v3):\n Technical Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document specifies the set of RFCs comprising the Lightweight\n Directory Access Protocol Version 3 (LDAPv3), and addresses the \"IESG\n Note\" attached to RFCs 2251 through 2256.\n\n1. Background and Motivation\n","scope_keywords":["3377","attribute","authentication","license","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3672","folder":"IETF/RFC-3672","source":"IETF/RFC-3672/RFC-3672.txt","version":null},{"body":"IETF","designation":"RFC 3673","folder":"IETF/RFC-3673","source":"IETF/RFC-3673/RFC-3673.txt","version":null},{"body":"IETF","designation":"RFC 3674","folder":"IETF/RFC-3674","source":"IETF/RFC-3674/RFC-3674.txt","version":null},{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3771","folder":"IETF/RFC-3771","source":"IETF/RFC-3771/RFC-3771.txt","version":null},{"body":"IETF","designation":"RFC 3866","folder":"IETF/RFC-3866","source":"IETF/RFC-3866/RFC-3866.txt","version":null},{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4110","folder":"IETF/RFC-4110","source":"IETF/RFC-4110/RFC-4110.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 3377 Network Working Group J. Hodges\nRequest for Comments: 3377 Sun Microsystems Inc.\nCategory: Standards Track R. Morgan\n University of Washington\n September 2002\n\n Lightweight Directory Access Protocol (v3):\n Technical Specification\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n This document specifies the set of RFCs comprising the Lightweight\n Directory Access Protocol Version 3 (LDAPv3), and addresses the \"IESG\n Note\" attached to RFCs 2251 through 2256.\n\n1. Background and Motivation\n 3377 attribute authentication license presentation nested-reference unchanged"},{"id":"IETF RFC 3698","type":"specification","body":"IETF","designation":"RFC 3698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3698.txt","https://www.rfc-editor.org/rfc/rfc3698.pdf"],"folder":"IETF/RFC-3698","files":{"txt":{"path":"standards/IETF/RFC-3698/RFC-3698.txt","sha256":"e8f9adc32418e3176724327ceeb612f635b4168438d9e81f35ddfd845ff633cd"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a collection of matching rules for use with\n the Lightweight Directory Access Protocol (LDAP). As these matching\n rules are simple adaptations of matching rules specified for use with\n the X.500 Directory, most are already in wide use.","scope_keywords":["3698","attribute","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null}],"search_text":"IETF RFC 3698 This document provides a collection of matching rules for use with\n the Lightweight Directory Access Protocol (LDAP). As these matching\n rules are simple adaptations of matching rules specified for use with\n the X.500 Directory, most are already in wide use. 3698 attribute key policy nested-reference unchanged"},{"id":"IETF RFC 226","type":"specification","body":"IETF","designation":"RFC 226","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc226.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc226.txt","https://www.rfc-editor.org/rfc/rfc226.pdf"],"folder":"IETF/RFC-226","files":{"txt":{"path":"standards/IETF/RFC-226/RFC-226.txt","sha256":"ac793de89815e1a361fa2bfa55f386b0715bb64b7f3b6805a26bf34eff95fbd7"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP PEGGY KARP\nREQUEST FOR COMMENTS #226 MITRE\nNIC #7625 20 SEPT 71\nCATEGORIES: D.3\nUPDATES: NONE\nOBSOLETES: NONE\n\n STANDARDIZATION OF HOST MNEUMONICS\n\nIN EACH TELNET IMPLEMENTATION, A LIST OF HOST NMEUMONICS IS PROVIDED\nFOR THE USER TO INDICATE THE SERVING HOST DESIRED. CURRENTLY, EACH\nSITE EMPLOYS THEIR OWN SPECIAL LIST. RATHER THAN REQUIRE THE USER TO\nBE COGNIZANT OF THE IDIOSYNCRASIES OF EACH LIST, ESPECIALLY WHEN\nCHAINED THROUGH SEVERAL HOSTS VIA TELNET, IT HAS BEEN RECOMMENDED THAT\nSTANDARD HOST DESIGNATORS BE ADOPTED.\n\nTHE FOLLOWING LIST OF SIX CHARACTER DESIGNATORS IS PROPOSED AS THE\nSTANDARD LIST. REGISTER ANY OBJECTIONS BY 3 OCTOBER TO P. KARP (703)\n893-3500 X2391, X2318. AN OFFICIAL POLICY AND IMPLEMENTATION DATE WILL\nBE SET ON 8 OCTOBER.\n\nTHE LIST:\n HOST # DESIGNATOR\n 1 UCLA\n 65 UCLA36\n 2 SRIARC\n 66 SRIAI\n 3 UCSB\n 4 UTAH\n 6 MULTCS\n 70 MITDM\n 7 RAND\n 8 SDC\n 9","scope_keywords":["226","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 289","folder":"IETF/RFC-289","source":"IETF/RFC-289/RFC-289.txt","version":null}],"search_text":"IETF RFC 226 NETWORK WORKING GROUP PEGGY KARP\nREQUEST FOR COMMENTS #226 MITRE\nNIC #7625 20 SEPT 71\nCATEGORIES: D.3\nUPDATES: NONE\nOBSOLETES: NONE\n\n STANDARDIZATION OF HOST MNEUMONICS\n\nIN EACH TELNET IMPLEMENTATION, A LIST OF HOST NMEUMONICS IS PROVIDED\nFOR THE USER TO INDICATE THE SERVING HOST DESIRED. CURRENTLY, EACH\nSITE EMPLOYS THEIR OWN SPECIAL LIST. RATHER THAN REQUIRE THE USER TO\nBE COGNIZANT OF THE IDIOSYNCRASIES OF EACH LIST, ESPECIALLY WHEN\nCHAINED THROUGH SEVERAL HOSTS VIA TELNET, IT HAS BEEN RECOMMENDED THAT\nSTANDARD HOST DESIGNATORS BE ADOPTED.\n\nTHE FOLLOWING LIST OF SIX CHARACTER DESIGNATORS IS PROPOSED AS THE\nSTANDARD LIST. REGISTER ANY OBJECTIONS BY 3 OCTOBER TO P. KARP (703)\n893-3500 X2391, X2318. AN OFFICIAL POLICY AND IMPLEMENTATION DATE WILL\nBE SET ON 8 OCTOBER.\n\nTHE LIST:\n HOST # DESIGNATOR\n 1 UCLA\n 65 UCLA36\n 2 SRIARC\n 66 SRIAI\n 3 UCSB\n 4 UTAH\n 6 MULTCS\n 70 MITDM\n 7 RAND\n 8 SDC\n 9 226 policy nested-reference unchanged"},{"id":"IETF RFC 289","type":"specification","body":"IETF","designation":"RFC 289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc289.txt","https://www.rfc-editor.org/rfc/rfc289.pdf"],"folder":"IETF/RFC-289","files":{"txt":{"path":"standards/IETF/RFC-289/RFC-289.txt","sha256":"ece7924ff64a654a1538cc1e625aa9c1aaceea2e952dc4c8caff88dc7824018c"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC #289 21-DEC-71 16:29 8295\nWhat We Hope Is An Official List of Host Names Richard W. Watson\n SRI-ARC\n\n The enclosed is what we hope will be accepted as a list of\n official formal host names and nicknames. As no other subject\n worked on by the NWG has generated so much comment, it is\n worthwhile to review briefly how this list came into being.\n\n The need for some standard set of names recognized by NCP's and\n Telnets and usable on hardcopy to designate a persons affiliation\n had been recognized for some time and several sets of names were\n in use.\n\n Peggy Karp issued the first formal proposal of a set of standard\n names in RFC 226, NIC 7625. This proposal was answered by a\n number of counter proposals and culminated in RFC 247, NIC 7688.\n People still were not happy with this proposal as names normally\n associated with hosts or projects were not used.\n\n At the last NWG meeting a nu","scope_keywords":["289","subject","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 289 NWG/RFC #289 21-DEC-71 16:29 8295\nWhat We Hope Is An Official List of Host Names Richard W. Watson\n SRI-ARC\n\n The enclosed is what we hope will be accepted as a list of\n official formal host names and nicknames. As no other subject\n worked on by the NWG has generated so much comment, it is\n worthwhile to review briefly how this list came into being.\n\n The need for some standard set of names recognized by NCP's and\n Telnets and usable on hardcopy to designate a persons affiliation\n had been recognized for some time and several sets of names were\n in use.\n\n Peggy Karp issued the first formal proposal of a set of standard\n names in RFC 226, NIC 7625. This proposal was answered by a\n number of counter proposals and culminated in RFC 247, NIC 7688.\n People still were not happy with this proposal as names normally\n associated with hosts or projects were not used.\n\n At the last NWG meeting a nu 289 subject tsp nested-reference unchanged"},{"id":"IETF RFC 2266","type":"specification","body":"IETF","designation":"RFC 2266","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2266.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2266.txt","https://www.rfc-editor.org/rfc/rfc2266.pdf"],"folder":"IETF/RFC-2266","files":{"txt":{"path":"standards/IETF/RFC-2266/RFC-2266.txt","sha256":"af3adfe8fcff7aff28942ee5807767c5d8b319d14c39772cf2b1037a61289b9b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing network repeaters\n based on IEEE 802.12.","scope_keywords":["2266","attribute","attributes","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2266 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, it defines objects for managing network repeaters\n based on IEEE 802.12. 2266 attribute attributes management presentation nested-reference unchanged"},{"id":"IETF RFC 3142","type":"specification","body":"IETF","designation":"RFC 3142","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3142.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3142.txt","https://www.rfc-editor.org/rfc/rfc3142.pdf"],"folder":"IETF/RFC-3142","files":{"txt":{"path":"standards/IETF/RFC-3142/RFC-3142.txt","sha256":"71e2368797e9673a0fccc52368d9e55f53dc08461c28eaedc4322279256f1bcd"}},"tags":["nested-reference","unchanged"],"summary":"The document describes an IPv6-to-IPv4 transport relay translator\n (TRT). It enables IPv6-only hosts to exchange {TCP,UDP} traffic with\n IPv4-only hosts. A TRT system, which locates in the middle,\n translates {TCP,UDP}/IPv6 to {TCP,UDP}/IPv4, or vice versa.\n\n The memo talks about how to implement a TRT system using existing\n technologies. It does not define any new protocols.\n\n1. Problem domain\n\n When you deploy an IPv6-only network, you still want to gain access\n to IPv4-only network resources outside, such as IPv4-only web\n servers. To solve this problem, many IPv6-to-IPv4 translation\n technologies are proposed, mainly in the IETF ngtrans working group.\n The memo describes a translator based on the transport relay\n technique to solve the same problem.\n\n In this memo, we call this kind of translator \"TRT\" (transport relay\n translator). A TRT system locates between IPv6-only hosts and IP","scope_keywords":["3142","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3879","folder":"IETF/RFC-3879","source":"IETF/RFC-3879/RFC-3879.txt","version":null},{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null}],"search_text":"IETF RFC 3142 The document describes an IPv6-to-IPv4 transport relay translator\n (TRT). It enables IPv6-only hosts to exchange {TCP,UDP} traffic with\n IPv4-only hosts. A TRT system, which locates in the middle,\n translates {TCP,UDP}/IPv6 to {TCP,UDP}/IPv4, or vice versa.\n\n The memo talks about how to implement a TRT system using existing\n technologies. It does not define any new protocols.\n\n1. Problem domain\n\n When you deploy an IPv6-only network, you still want to gain access\n to IPv4-only network resources outside, such as IPv4-only web\n servers. To solve this problem, many IPv6-to-IPv4 translation\n technologies are proposed, mainly in the IETF ngtrans working group.\n The memo describes a translator based on the transport relay\n technique to solve the same problem.\n\n In this memo, we call this kind of translator \"TRT\" (transport relay\n translator). A TRT system locates between IPv6-only hosts and IP 3142 path nested-reference unchanged"},{"id":"IETF RFC 2268","type":"specification","body":"IETF","designation":"RFC 2268","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2268.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2268.txt","https://www.rfc-editor.org/rfc/rfc2268.pdf"],"folder":"IETF/RFC-2268","files":{"txt":{"path":"standards/IETF/RFC-2268/RFC-2268.txt","sha256":"1229e54b0569f96daedfddb0b93d03df139f4f32d3cf5cfd3b9295a11ca5ae27"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Rivest\nRequest for Comments: 2268 MIT Laboratory for Computer Science\nCategory: Informational and RSA Data Security, Inc.\n March 1998\n\n A Description of the RC2(r) Encryption Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo is an RSA Laboratories Technical Note. It is meant for\n informational use by the Internet community.\n\n This memo describes a conventional (secret-key) block encryption\n algorithm, called RC2, which may be considered as a proposal for a\n DES replacement. The input and output block sizes are 64 bits each.\n The key size is variable, from one byte up to 128 bytes, although the\n current implementation","scope_keywords":["2268","algorithm","algorithms","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2311","folder":"IETF/RFC-2311","source":"IETF/RFC-2311/RFC-2311.txt","version":null},{"body":"IETF","designation":"RFC 2630","folder":"IETF/RFC-2630","source":"IETF/RFC-2630/RFC-2630.txt","version":null},{"body":"IETF","designation":"RFC 2633","folder":"IETF/RFC-2633","source":"IETF/RFC-2633/RFC-2633.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 3217","folder":"IETF/RFC-3217","source":"IETF/RFC-3217/RFC-3217.txt","version":null},{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2268 Network Working Group R. Rivest\nRequest for Comments: 2268 MIT Laboratory for Computer Science\nCategory: Informational and RSA Data Security, Inc.\n March 1998\n\n A Description of the RC2(r) Encryption Algorithm\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n This memo is an RSA Laboratories Technical Note. It is meant for\n informational use by the Internet community.\n\n This memo describes a conventional (secret-key) block encryption\n algorithm, called RC2, which may be considered as a proposal for a\n DES replacement. The input and output block sizes are 64 bits each.\n The key size is variable, from one byte up to 128 bytes, although the\n current implementation 2268 algorithm algorithms encryption key nested-reference unchanged"},{"id":"IETF RFC 3305","type":"specification","body":"IETF","designation":"RFC 3305","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3305.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3305.txt","https://www.rfc-editor.org/rfc/rfc3305.pdf"],"folder":"IETF/RFC-3305","files":{"txt":{"path":"standards/IETF/RFC-3305/RFC-3305.txt","sha256":"66d2f0eec873b17544fe41c5df27f166a9784c966157ce69923c58b3234eb6d1"}},"tags":["nested-reference","unchanged"],"summary":"This document, a product of the W3C Uniform Resource Identifier (URI)\n Interest Group, addresses and attempts to clarify issues pertaining\n to URIs. This document addresses how URI space is partitioned and\n the relationship between URIs, URLs, and URNs, describes how URI\n schemes and URN namespaces ids are registered, and presents\n recommendations for continued work on this subject.\n\nMealling & Denenberg Informational [Page 1]\n\f\nRFC 3305 URIs, URLs, and URNs August 2002","scope_keywords":["3305","attribute","attributes","http","presentation","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 5017","folder":"IETF/RFC-5017","source":"IETF/RFC-5017/RFC-5017.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 3305 This document, a product of the W3C Uniform Resource Identifier (URI)\n Interest Group, addresses and attempts to clarify issues pertaining\n to URIs. This document addresses how URI space is partitioned and\n the relationship between URIs, URLs, and URNs, describes how URI\n schemes and URN namespaces ids are registered, and presents\n recommendations for continued work on this subject.\n\nMealling & Denenberg Informational [Page 1]\n\f\nRFC 3305 URIs, URLs, and URNs August 2002 3305 attribute attributes http presentation registered subject nested-reference unchanged"},{"id":"IETF RFC 4690","type":"specification","body":"IETF","designation":"RFC 4690","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4690.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4690.txt","https://www.rfc-editor.org/rfc/rfc4690.pdf"],"folder":"IETF/RFC-4690","files":{"txt":{"path":"standards/IETF/RFC-4690/RFC-4690.txt","sha256":"f4c3eb412749f1fd91fdb3e594d059298e888a8c0e2755479f84f59faee4ed55"}},"tags":["nested-reference","unchanged"],"summary":"This note describes issues raised by the deployment and use of\n Internationalized Domain Names. It describes problems both at the\n time of registration and for use of those names in the DNS. It\n recommends that IETF should update the RFCs relating to IDNs and a\n framework to be followed in doing so, as well as summarizing and\n identifying some work that is required outside the IETF. In\n particular, it proposes that some changes be investigated for the\n Internationalizing Domain Names in Applications (IDNA) standard and\n its supporting tables, based on experience gained since those\n standards were completed.","scope_keywords":["4690","certificate","certificates","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 4690 This note describes issues raised by the deployment and use of\n Internationalized Domain Names. It describes problems both at the\n time of registration and for use of those names in the DNS. It\n recommends that IETF should update the RFCs relating to IDNs and a\n framework to be followed in doing so, as well as summarizing and\n identifying some work that is required outside the IETF. In\n particular, it proposes that some changes be investigated for the\n Internationalizing Domain Names in Applications (IDNA) standard and\n its supporting tables, based on experience gained since those\n standards were completed. 4690 certificate certificates policy registered nested-reference unchanged"},{"id":"IETF RFC 2718","type":"specification","body":"IETF","designation":"RFC 2718","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2718.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2718.txt","https://www.rfc-editor.org/rfc/rfc2718.pdf"],"folder":"IETF/RFC-2718","files":{"txt":{"path":"standards/IETF/RFC-2718/RFC-2718.txt","sha256":"edcd6324fdf90c7e68af5f5de7fd516646d84960c4689f0033b7f0891b8891c8"}},"tags":["nested-reference","unchanged"],"summary":"A Uniform Resource Locator (URL) is a compact string representation\n of the location for a resource that is available via the Internet.\n This document provides guidelines for the definition of new URL\n schemes.\n\n1. Introduction\n\n A Uniform Resource Locator (URL) is a compact string representation\n of the location for a resource that is available via the Internet.\n RFC 2396 [1] defines the general syntax and semantics of URIs, and,\n by inclusion, URLs. URLs are designated by including a \"<scheme>:\"\n and then a \"<scheme-specific-part>\". Many URL schemes are already\n defined.\n\n This document provides guidelines for the definition of new URL\n schemes, for consideration by those who are defining and registering\n or evaluating those definitions.\n\n The process by which new URL schemes are registered is defined in RFC\n 2717 [2].\n\nMasinter, et al. Informational [Page 1]\n\f\nRFC 2718 Guidelines for ","scope_keywords":["2718","http","path","presentation","registered","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2717","folder":"IETF/RFC-2717","source":"IETF/RFC-2717/RFC-2717.txt","version":null},{"body":"IETF","designation":"RFC 3305","folder":"IETF/RFC-3305","source":"IETF/RFC-3305/RFC-3305.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4395","folder":"IETF/RFC-4395","source":"IETF/RFC-4395/RFC-4395.txt","version":null},{"body":"IETF","designation":"RFC 7595","folder":"IETF/RFC-7595","source":"IETF/RFC-7595/RFC-7595.txt","version":null}],"search_text":"IETF RFC 2718 A Uniform Resource Locator (URL) is a compact string representation\n of the location for a resource that is available via the Internet.\n This document provides guidelines for the definition of new URL\n schemes.\n\n1. Introduction\n\n A Uniform Resource Locator (URL) is a compact string representation\n of the location for a resource that is available via the Internet.\n RFC 2396 [1] defines the general syntax and semantics of URIs, and,\n by inclusion, URLs. URLs are designated by including a \"<scheme>:\"\n and then a \"<scheme-specific-part>\". Many URL schemes are already\n defined.\n\n This document provides guidelines for the definition of new URL\n schemes, for consideration by those who are defining and registering\n or evaluating those definitions.\n\n The process by which new URL schemes are registered is defined in RFC\n 2717 [2].\n\nMasinter, et al. Informational [Page 1]\n\f\nRFC 2718 Guidelines for  2718 http path presentation registered signature nested-reference unchanged"},{"id":"IETF RFC 2727","type":"specification","body":"IETF","designation":"RFC 2727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2727.txt","https://www.rfc-editor.org/rfc/rfc2727.pdf"],"folder":"IETF/RFC-2727","files":{"txt":{"path":"standards/IETF/RFC-2727/RFC-2727.txt","sha256":"49d434f855454e6d14d56a7ae3caded3268d4a8b8543b41049a446b9a8acd0f4"}},"tags":["nested-reference","unchanged"],"summary":"The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. This document is a self-\n consistent, organized compilation of the process as it was known at\n the time of publication.","scope_keywords":["2727","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2777","folder":"IETF/RFC-2777","source":"IETF/RFC-2777/RFC-2777.txt","version":null},{"body":"IETF","designation":"RFC 3233","folder":"IETF/RFC-3233","source":"IETF/RFC-3233/RFC-3233.txt","version":null},{"body":"IETF","designation":"RFC 3677","folder":"IETF/RFC-3677","source":"IETF/RFC-3677/RFC-3677.txt","version":null},{"body":"IETF","designation":"RFC 3710","folder":"IETF/RFC-3710","source":"IETF/RFC-3710/RFC-3710.txt","version":null},{"body":"IETF","designation":"RFC 3777","folder":"IETF/RFC-3777","source":"IETF/RFC-3777/RFC-3777.txt","version":null}],"search_text":"IETF RFC 2727 The process by which the members of the IAB and IESG are selected,\n confirmed, and recalled is specified. This document is a self-\n consistent, organized compilation of the process as it was known at\n the time of publication. 2727 subject nested-reference unchanged"},{"id":"IETF RFC 229","type":"specification","body":"IETF","designation":"RFC 229","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc229.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc229.txt","https://www.rfc-editor.org/rfc/rfc229.pdf"],"folder":"IETF/RFC-229","files":{"txt":{"path":"standards/IETF/RFC-229/RFC-229.txt","sha256":"b2ccdf5aa746d02da1ef4f6bdd9dae62beecb7b08ec253adac0b61e4786b1766"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: #229 UCLA-NMC\nNIC 7646 Computer Science\nCategories: D.3 22 September 71\nRelated: #226\nObsoletes: None\n\n STANDARD HOST NAMES\n\nI suggest 8 character names and the following list:\n\n Site Standard Name Alternate Name\n ---- ------------- --------------\n 1 UCLA-NMC SEX\n\n 65 UCLA-CCN CCN\n\n 2 SRI-ARC NIC\n\n 66 SRI-AI\n\n 3 UCSB\n\n 4 UTAH\n\n 5 BBN-NCC NCC\n\n 69 BBN-A BBN\n\n 133 BBN-B\n\n 6 MIT-MLTX MULTICS\n\n 70 MIT-DMCG DMCG\n\n 7 RAND-65\n\n 71 RAND-10\n\n 8 SDC\n\n 9 HARV\n\n 73 HARV-1\n\n 137 HARV-11\n\n [Page 1]\n\f\nNetwork Working Group Jon Postel\nRequest for Comments: #229 22 September 71\n\n Site Standard Name\n ---- -------------\n 10 LL-67\n\n 74 LL-TX2\n\n 11 STAN\n\n 12 ILL\n\n 13 CASE\n\n 14 CMU\n\n 15 BUROUGHS\n\n 16 AMES-67\n\n 144 AMES-TIP\n\n 145 MITRE\n\n 18 RADC\n\n 146 RADC-TIP\n\n 19 NBS\n\n 147 NBS-TIP\n\n 148 ETAC\n\n 21 TINKER\n\n 22 MCLELLAN\n\n 23 USC\n\n 151 USC-TIP\n\n 152 GWC\n\n [P","scope_keywords":["229"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 229 Network Working Group Jon Postel\nRequest for Comments: #229 UCLA-NMC\nNIC 7646 Computer Science\nCategories: D.3 22 September 71\nRelated: #226\nObsoletes: None\n\n STANDARD HOST NAMES\n\nI suggest 8 character names and the following list:\n\n Site Standard Name Alternate Name\n ---- ------------- --------------\n 1 UCLA-NMC SEX\n\n 65 UCLA-CCN CCN\n\n 2 SRI-ARC NIC\n\n 66 SRI-AI\n\n 3 UCSB\n\n 4 UTAH\n\n 5 BBN-NCC NCC\n\n 69 BBN-A BBN\n\n 133 BBN-B\n\n 6 MIT-MLTX MULTICS\n\n 70 MIT-DMCG DMCG\n\n 7 RAND-65\n\n 71 RAND-10\n\n 8 SDC\n\n 9 HARV\n\n 73 HARV-1\n\n 137 HARV-11\n\n [Page 1]\n\f\nNetwork Working Group Jon Postel\nRequest for Comments: #229 22 September 71\n\n Site Standard Name\n ---- -------------\n 10 LL-67\n\n 74 LL-TX2\n\n 11 STAN\n\n 12 ILL\n\n 13 CASE\n\n 14 CMU\n\n 15 BUROUGHS\n\n 16 AMES-67\n\n 144 AMES-TIP\n\n 145 MITRE\n\n 18 RADC\n\n 146 RADC-TIP\n\n 19 NBS\n\n 147 NBS-TIP\n\n 148 ETAC\n\n 21 TINKER\n\n 22 MCLELLAN\n\n 23 USC\n\n 151 USC-TIP\n\n 152 GWC\n\n [P 229 nested-reference unchanged"},{"id":"IETF RFC 2297","type":"specification","body":"IETF","designation":"RFC 2297","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2297.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2297.txt","https://www.rfc-editor.org/rfc/rfc2297.pdf"],"folder":"IETF/RFC-2297","files":{"txt":{"path":"standards/IETF/RFC-2297/RFC-2297.txt","sha256":"7e4462eeeeb44544286357bb33a630fda3d4aa3f29a7794db153247fa0781d05"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies enhancements to the General Switch Management\n Protocol (GSMP) [RFC1987]. The major enhancement is the addition of\n Quality of Service (QoS) messages. Other improvements have been made\n to the protocol resulting from operational experience. GSMP is a\n general purpose protocol to control an ATM switch. It allows a\n controller to establish and release connections across the switch;\n add and delete leaves on a multicast connection; manage switch ports;\n request configuration information; and request statistics.\n\nNewman, et. al. Informational [Page 1]\n\f\nRFC 2297 Ipsilon's General Switch Management March 1998","scope_keywords":["2297","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null}],"search_text":"IETF RFC 2297 This memo specifies enhancements to the General Switch Management\n Protocol (GSMP) [RFC1987]. The major enhancement is the addition of\n Quality of Service (QoS) messages. Other improvements have been made\n to the protocol resulting from operational experience. GSMP is a\n general purpose protocol to control an ATM switch. It allows a\n controller to establish and release connections across the switch;\n add and delete leaves on a multicast connection; manage switch ports;\n request configuration information; and request statistics.\n\nNewman, et. al. Informational [Page 1]\n\f\nRFC 2297 Ipsilon's General Switch Management March 1998 2297 management path nested-reference unchanged"},{"id":"IETF RFC 2879","type":"specification","body":"IETF","designation":"RFC 2879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2879.txt","https://www.rfc-editor.org/rfc/rfc2879.pdf"],"folder":"IETF/RFC-2879","files":{"txt":{"path":"standards/IETF/RFC-2879/RFC-2879.txt","sha256":"7838264a4e6d9835372e5e19db1c89bd4ddb3cc326e0f6b636affd0c88f6d6be"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a content media feature schema for Internet\n fax.\n\n It is a profile of the media feature registration mechanisms [1,2,3]\n for use in performing capability identification between extended\n Internet fax systems [5]. It replaces and updates the feature schema\n defined in RFC 2531.","scope_keywords":["2879","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null}],"search_text":"IETF RFC 2879 This document defines a content media feature schema for Internet\n fax.\n\n It is a profile of the media feature registration mechanisms [1,2,3]\n for use in performing capability identification between extended\n Internet fax systems [5]. It replaces and updates the feature schema\n defined in RFC 2531. 2879 identification profile nested-reference unchanged"},{"id":"IETF RFC 4336","type":"specification","body":"IETF","designation":"RFC 4336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4336.txt","https://www.rfc-editor.org/rfc/rfc4336.pdf"],"folder":"IETF/RFC-4336","files":{"txt":{"path":"standards/IETF/RFC-4336/RFC-4336.txt","sha256":"08cf9b4d625100b1f1ca6c92b30d8f728eacfc505d916c29160dd3e38775c472"}},"tags":["nested-reference","unchanged"],"summary":"This document describes for the historical record the motivation\n behind the Datagram Congestion Control Protocol (DCCP), an unreliable\n transport protocol incorporating end-to-end congestion control. DCCP\n implements a congestion-controlled, unreliable flow of datagrams for\n use by applications such as streaming media or on-line games.\n\nFloyd, et al. Informational [Page 1]\n\f\nRFC 4336 Problem Statement for DCCP March 2006","scope_keywords":["4336","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null}],"search_text":"IETF RFC 4336 This document describes for the historical record the motivation\n behind the Datagram Congestion Control Protocol (DCCP), an unreliable\n transport protocol incorporating end-to-end congestion control. DCCP\n implements a congestion-controlled, unreliable flow of datagrams for\n use by applications such as streaming media or on-line games.\n\nFloyd, et al. Informational [Page 1]\n\f\nRFC 4336 Problem Statement for DCCP March 2006 4336 delivery nested-reference unchanged"},{"id":"IETF RFC 3218","type":"specification","body":"IETF","designation":"RFC 3218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3218.txt","https://www.rfc-editor.org/rfc/rfc3218.pdf"],"folder":"IETF/RFC-3218","files":{"txt":{"path":"standards/IETF/RFC-3218/RFC-3218.txt","sha256":"e676774d31e262badfcf0259ad3dab82ce100f4efed7659c6f7e29d60dabd753"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a strategy for resisting the Million Message\n Attack.","scope_keywords":["3218","encryption","key","keys","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3370","folder":"IETF/RFC-3370","source":"IETF/RFC-3370/RFC-3370.txt","version":null},{"body":"IETF","designation":"RFC 3560","folder":"IETF/RFC-3560","source":"IETF/RFC-3560/RFC-3560.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 3218 This memo describes a strategy for resisting the Million Message\n Attack. 3218 encryption key keys signature nested-reference unchanged"},{"id":"IETF RFC 3713","type":"specification","body":"IETF","designation":"RFC 3713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3713.txt","https://www.rfc-editor.org/rfc/rfc3713.pdf"],"folder":"IETF/RFC-3713","files":{"txt":{"path":"standards/IETF/RFC-3713/RFC-3713.txt","sha256":"126cea1768aed9257fbdf52a4e1938eb15d79c8aacb83d14f60f1320d5b8770f"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Camellia encryption algorithm. Camellia\n is a block cipher with 128-bit block size and 128-, 192-, and 256-bit\n keys. The algorithm description is presented together with key\n scheduling part and data randomizing part.\n\n1. Introduction","scope_keywords":["3713","algorithm","algorithms","encryption","key","keys","presentation","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null},{"body":"IETF","designation":"RFC 5529","folder":"IETF/RFC-5529","source":"IETF/RFC-5529/RFC-5529.txt","version":null},{"body":"IETF","designation":"RFC 5932","folder":"IETF/RFC-5932","source":"IETF/RFC-5932/RFC-5932.txt","version":null},{"body":"IETF","designation":"RFC 6367","folder":"IETF/RFC-6367","source":"IETF/RFC-6367/RFC-6367.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 3713 This document describes the Camellia encryption algorithm. Camellia\n is a block cipher with 128-bit block size and 128-, 192-, and 256-bit\n keys. The algorithm description is presented together with key\n scheduling part and data randomizing part.\n\n1. Introduction 3713 algorithm algorithms encryption key keys presentation signature signatures nested-reference unchanged"},{"id":"IETF RFC 3238","type":"specification","body":"IETF","designation":"RFC 3238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3238.txt","https://www.rfc-editor.org/rfc/rfc3238.pdf"],"folder":"IETF/RFC-3238","files":{"txt":{"path":"standards/IETF/RFC-3238/RFC-3238.txt","sha256":"5121fa56b402acf0cbafc7bb24511d37be4b80febc9c97efc087a5feded0b574"}},"tags":["nested-reference","unchanged"],"summary":"This document includes comments and recommendations by the IAB on\n some architectural and policy issues related to the chartering of\n Open Pluggable Edge Services (OPES) in the IETF. OPES are services\n that would be deployed at application-level intermediaries in the\n network, for example, at a web proxy cache between the origin server\n and the client. These intermediaries would transform or filter\n content, with the explicit consent of either the content provider or\n the end user.\n\n1. Introduction\n\n Open Pluggable Edge Services (OPES) are services that would be\n deployed in the network, for example, at a web proxy cache between\n the origin server and the client, that would transform or filter\n content. Examples of proposed OPES services include assembling\n personalized web pages, adding user-specific regional information to\n web pages, virus scanning, content adaptation for clients with","scope_keywords":["3238","authorization","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3507","folder":"IETF/RFC-3507","source":"IETF/RFC-3507/RFC-3507.txt","version":null},{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 4141","folder":"IETF/RFC-4141","source":"IETF/RFC-4141/RFC-4141.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 4313","folder":"IETF/RFC-4313","source":"IETF/RFC-4313/RFC-4313.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null}],"search_text":"IETF RFC 3238 This document includes comments and recommendations by the IAB on\n some architectural and policy issues related to the chartering of\n Open Pluggable Edge Services (OPES) in the IETF. OPES are services\n that would be deployed at application-level intermediaries in the\n network, for example, at a web proxy cache between the origin server\n and the client. These intermediaries would transform or filter\n content, with the explicit consent of either the content provider or\n the end user.\n\n1. Introduction\n\n Open Pluggable Edge Services (OPES) are services that would be\n deployed in the network, for example, at a web proxy cache between\n the origin server and the client, that would transform or filter\n content. Examples of proposed OPES services include assembling\n personalized web pages, adding user-specific regional information to\n web pages, virus scanning, content adaptation for clients with 3238 authorization policy risk nested-reference unchanged"},{"id":"IETF RFC 2323","type":"specification","body":"IETF","designation":"RFC 2323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2323.txt","https://www.rfc-editor.org/rfc/rfc2323.pdf"],"folder":"IETF/RFC-2323","files":{"txt":{"path":"standards/IETF/RFC-2323/RFC-2323.txt","sha256":"9fd85faea143eef31cd5d9a6b1e81bee856e4cffe3a8d1ef02bd351453fed2ad"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Ramos\nRequest for Comments: 2323 ISI\nCategory: Informational 1 April 1998\n\n IETF Identification and Security Guidelines\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n This RFC is meant to represent a guideline by which the IETF\n conferences may run more effeciently with regards to identification\n and security protocols, with specific attention paid to a particular\n sub-group within the IETF: \"facial hairius extremis\".\n\n This document will shed further illumination on these problems and\n provide some possible solutions.\n\n This memo provides entertainment for the Internet community. It does\n not specify an Internet standard of any kind, bu","scope_keywords":["2323","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"IETF RFC 2323 Network Working Group A. Ramos\nRequest for Comments: 2323 ISI\nCategory: Informational 1 April 1998\n\n IETF Identification and Security Guidelines\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Abstract\n\n This RFC is meant to represent a guideline by which the IETF\n conferences may run more effeciently with regards to identification\n and security protocols, with specific attention paid to a particular\n sub-group within the IETF: \"facial hairius extremis\".\n\n This document will shed further illumination on these problems and\n provide some possible solutions.\n\n This memo provides entertainment for the Internet community. It does\n not specify an Internet standard of any kind, bu 2323 identification nested-reference unchanged"},{"id":"IETF RFC 3466","type":"specification","body":"IETF","designation":"RFC 3466","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3466.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3466.txt","https://www.rfc-editor.org/rfc/rfc3466.pdf"],"folder":"IETF/RFC-3466","files":{"txt":{"path":"standards/IETF/RFC-3466/RFC-3466.txt","sha256":"0c05aa9f317d4c782f229a4cf7928dd7b871f569db325afc57fa6f8d0037e626"}},"tags":["nested-reference","unchanged"],"summary":"Content (distribution) internetworking (CDI) is the technology for\n interconnecting content networks, sometimes previously called\n \"content peering\" or \"CDN peering\". A common vocabulary helps the\n process of discussing such interconnection and interoperation. This\n document introduces content networks and content internetworking, and\n defines elements for such a common vocabulary.","scope_keywords":["3466","http","management","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3568","folder":"IETF/RFC-3568","source":"IETF/RFC-3568/RFC-3568.txt","version":null},{"body":"IETF","designation":"RFC 3570","folder":"IETF/RFC-3570","source":"IETF/RFC-3570/RFC-3570.txt","version":null},{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null}],"search_text":"IETF RFC 3466 Content (distribution) internetworking (CDI) is the technology for\n interconnecting content networks, sometimes previously called\n \"content peering\" or \"CDN peering\". A common vocabulary helps the\n process of discussing such interconnection and interoperation. This\n document introduces content networks and content internetworking, and\n defines elements for such a common vocabulary. 3466 http management tsp nested-reference unchanged"},{"id":"IETF RFC 3048","type":"specification","body":"IETF","designation":"RFC 3048","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3048.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3048.txt","https://www.rfc-editor.org/rfc/rfc3048.pdf"],"folder":"IETF/RFC-3048","files":{"txt":{"path":"standards/IETF/RFC-3048/RFC-3048.txt","sha256":"a165d8f5b2a889029ba8f3e94b73ff2dabcdbf1e3ed2d2be7f13f6e02d637613"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for the standardization of bulk-\n data reliable multicast transport. It builds upon the experience\n gained during the deployment of several classes of contemporary\n reliable multicast transport, and attempts to pull out the\n commonalities between these classes of protocols into a number of\n building blocks. To that end, this document recommends that certain\n components that are common to multiple protocol classes be\n standardized as \"building blocks\". The remaining parts of the\n protocols, consisting of highly protocol specific, tightly\n intertwined functions, shall be designated as \"protocol cores\".\n Thus, each protocol can then be constructed by merging a \"protocol\n core\" with a number of \"building blocks\" which can be re-used across\n multiple protocols.\n\nWhetten, et al. Informational [Page 1]\n\f\nRFC 3048 RMT Building Blocks January 2001","scope_keywords":["3048","authentication","delivery","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3452","folder":"IETF/RFC-3452","source":"IETF/RFC-3452/RFC-3452.txt","version":null},{"body":"IETF","designation":"RFC 3695","folder":"IETF/RFC-3695","source":"IETF/RFC-3695/RFC-3695.txt","version":null},{"body":"IETF","designation":"RFC 3738","folder":"IETF/RFC-3738","source":"IETF/RFC-3738/RFC-3738.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3940","folder":"IETF/RFC-3940","source":"IETF/RFC-3940/RFC-3940.txt","version":null},{"body":"IETF","designation":"RFC 4654","folder":"IETF/RFC-4654","source":"IETF/RFC-4654/RFC-4654.txt","version":null},{"body":"IETF","designation":"RFC 5052","folder":"IETF/RFC-5052","source":"IETF/RFC-5052/RFC-5052.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5445","folder":"IETF/RFC-5445","source":"IETF/RFC-5445/RFC-5445.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5740","folder":"IETF/RFC-5740","source":"IETF/RFC-5740/RFC-5740.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 3048 This document describes a framework for the standardization of bulk-\n data reliable multicast transport. It builds upon the experience\n gained during the deployment of several classes of contemporary\n reliable multicast transport, and attempts to pull out the\n commonalities between these classes of protocols into a number of\n building blocks. To that end, this document recommends that certain\n components that are common to multiple protocol classes be\n standardized as \"building blocks\". The remaining parts of the\n protocols, consisting of highly protocol specific, tightly\n intertwined functions, shall be designated as \"protocol cores\".\n Thus, each protocol can then be constructed by merging a \"protocol\n core\" with a number of \"building blocks\" which can be re-used across\n multiple protocols.\n\nWhetten, et al. Informational [Page 1]\n\f\nRFC 3048 RMT Building Blocks January 2001 3048 authentication delivery risk nested-reference unchanged"},{"id":"IETF RFC 3372","type":"specification","body":"IETF","designation":"RFC 3372","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3372.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3372.txt","https://www.rfc-editor.org/rfc/rfc3372.pdf"],"folder":"IETF/RFC-3372","files":{"txt":{"path":"standards/IETF/RFC-3372/RFC-3372.txt","sha256":"00c4858ce7ff151110474210bc07d2ece516387f8bc161a0636b31047f40f53a"}},"tags":["nested-reference","unchanged"],"summary":"The popularity of gateways that interwork between the PSTN (Public\n Switched Telephone Network) and SIP networks has motivated the\n publication of a set of common practices that can assure consistent\n behavior across implementations. This document taxonomizes the uses\n of PSTN-SIP gateways, provides uses cases, and identifies mechanisms\n necessary for interworking. The mechanisms detail how SIP provides\n for both 'encapsulation' (bridging the PSTN signaling across a SIP\n network) and 'translation' (gatewaying).","scope_keywords":["3372","delivery","key","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null},{"body":"IETF","designation":"RFC 3666","folder":"IETF/RFC-3666","source":"IETF/RFC-3666/RFC-3666.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 5479","folder":"IETF/RFC-5479","source":"IETF/RFC-5479/RFC-5479.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 3372 The popularity of gateways that interwork between the PSTN (Public\n Switched Telephone Network) and SIP networks has motivated the\n publication of a set of common practices that can assure consistent\n behavior across implementations. This document taxonomizes the uses\n of PSTN-SIP gateways, provides uses cases, and identifies mechanisms\n necessary for interworking. The mechanisms detail how SIP provides\n for both 'encapsulation' (bridging the PSTN signaling across a SIP\n network) and 'translation' (gatewaying). 3372 delivery key path trust nested-reference unchanged"},{"id":"IETF RFC 3556","type":"specification","body":"IETF","designation":"RFC 3556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3556.txt","https://www.rfc-editor.org/rfc/rfc3556.pdf"],"folder":"IETF/RFC-3556","files":{"txt":{"path":"standards/IETF/RFC-3556/RFC-3556.txt","sha256":"e53acf52d1ddc506b4c2a8e3d30189d5763d48ff6007b1873019f87e749ad1b7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an extension to the Session Description\n Protocol (SDP) to specify two additional modifiers for the bandwidth\n attribute. These modifiers may be used to specify the bandwidth\n allowed for RTP Control Protocol (RTCP) packets in a Real-time\n Transport Protocol (RTP) session.\n\n1. Introduction\n\n The Real-time Transport Protocol (RTP), RFC 3550 [1], includes a\n control protocol RTCP which provides synchronization information from\n data senders and feedback information from data receivers.\n\n Normally, the amount of bandwidth allocated to RTCP in an RTP session\n is 5% of the session bandwidth. For some applications, it may be\n appropriate to specify the RTCP bandwidth independently of the\n session bandwidth. Using a separate parameter allows rate-adaptive\n applications to set an RTCP bandwidth consistent with a \"typical\"\n data bandwidth that is lower than the maximum bandw","scope_keywords":["3556","algorithm","algorithms","attribute","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4571","folder":"IETF/RFC-4571","source":"IETF/RFC-4571/RFC-4571.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5761","folder":"IETF/RFC-5761","source":"IETF/RFC-5761/RFC-5761.txt","version":null},{"body":"IETF","designation":"RFC 5968","folder":"IETF/RFC-5968","source":"IETF/RFC-5968/RFC-5968.txt","version":null},{"body":"IETF","designation":"RFC 6051","folder":"IETF/RFC-6051","source":"IETF/RFC-6051/RFC-6051.txt","version":null},{"body":"IETF","designation":"RFC 6263","folder":"IETF/RFC-6263","source":"IETF/RFC-6263/RFC-6263.txt","version":null},{"body":"IETF","designation":"RFC 7160","folder":"IETF/RFC-7160","source":"IETF/RFC-7160/RFC-7160.txt","version":null},{"body":"IETF","designation":"RFC 8108","folder":"IETF/RFC-8108","source":"IETF/RFC-8108/RFC-8108.txt","version":null},{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"IETF RFC 3556 This document defines an extension to the Session Description\n Protocol (SDP) to specify two additional modifiers for the bandwidth\n attribute. These modifiers may be used to specify the bandwidth\n allowed for RTP Control Protocol (RTCP) packets in a Real-time\n Transport Protocol (RTP) session.\n\n1. Introduction\n\n The Real-time Transport Protocol (RTP), RFC 3550 [1], includes a\n control protocol RTCP which provides synchronization information from\n data senders and feedback information from data receivers.\n\n Normally, the amount of bandwidth allocated to RTCP in an RTP session\n is 5% of the session bandwidth. For some applications, it may be\n appropriate to specify the RTCP bandwidth independently of the\n session bandwidth. Using a separate parameter allows rate-adaptive\n applications to set an RTCP bandwidth consistent with a \"typical\"\n data bandwidth that is lower than the maximum bandw 3556 algorithm algorithms attribute profile profiles nested-reference unchanged"},{"id":"IETF RFC 4215","type":"specification","body":"IETF","designation":"RFC 4215","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4215.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4215.txt","https://www.rfc-editor.org/rfc/rfc4215.pdf"],"folder":"IETF/RFC-4215","files":{"txt":{"path":"standards/IETF/RFC-4215/RFC-4215.txt","sha256":"d914bf6496cb8d0ce810857110399cb16b1949d141fccf87401182d2252c1b1a"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes the transition to IPv6 in Third Generation\n Partnership Project (3GPP) packet networks. These networks are based\n on General Packet Radio Service (GPRS) technology, and the radio\n network architecture is based on Global System for Mobile\n Communications (GSM) or Universal Mobile Telecommunications System\n (UMTS)/Wideband Code Division Multiple Access (WCDMA) technology.\n\n The focus is on analyzing different transition scenarios and\n applicable transition mechanisms and finding solutions for those\n transition scenarios. In these scenarios, the User Equipment (UE)\n connects to other nodes, e.g., in the Internet, and IPv6/IPv4\n transition mechanisms are needed.","scope_keywords":["4215"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4472","folder":"IETF/RFC-4472","source":"IETF/RFC-4472/RFC-4472.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4966","folder":"IETF/RFC-4966","source":"IETF/RFC-4966/RFC-4966.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4215 This document analyzes the transition to IPv6 in Third Generation\n Partnership Project (3GPP) packet networks. These networks are based\n on General Packet Radio Service (GPRS) technology, and the radio\n network architecture is based on Global System for Mobile\n Communications (GSM) or Universal Mobile Telecommunications System\n (UMTS)/Wideband Code Division Multiple Access (WCDMA) technology.\n\n The focus is on analyzing different transition scenarios and\n applicable transition mechanisms and finding solutions for those\n transition scenarios. In these scenarios, the User Equipment (UE)\n connects to other nodes, e.g., in the Internet, and IPv6/IPv4\n transition mechanisms are needed. 4215 nested-reference unchanged"},{"id":"IETF RFC 4317","type":"specification","body":"IETF","designation":"RFC 4317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4317.txt","https://www.rfc-editor.org/rfc/rfc4317.pdf"],"folder":"IETF/RFC-4317","files":{"txt":{"path":"standards/IETF/RFC-4317/RFC-4317.txt","sha256":"8a9c667559a11cba6cc8978264a443aa35f2614a3ec85980d5fc2ac016c4aaf9"}},"tags":["nested-reference","unchanged"],"summary":"This document gives examples of Session Description Protocol (SDP)\n offer/answer exchanges. Examples include codec negotiation and\n selection, hold and resume, and addition and deletion of media\n streams. The examples show multiple media types, bidirectional,\n unidirectional, inactive streams, and dynamic payload types. Common\n Third Party Call Control (3pcc) examples are also given.\n\nJohnston & Sparks Informational [Page 1]\n\f\nRFC 4317 SDP Offer/Answer Examples December 2005","scope_keywords":["4317","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null}],"search_text":"IETF RFC 4317 This document gives examples of Session Description Protocol (SDP)\n offer/answer exchanges. Examples include codec negotiation and\n selection, hold and resume, and addition and deletion of media\n streams. The examples show multiple media types, bidirectional,\n unidirectional, inactive streams, and dynamic payload types. Common\n Third Party Call Control (3pcc) examples are also given.\n\nJohnston & Sparks Informational [Page 1]\n\f\nRFC 4317 SDP Offer/Answer Examples December 2005 4317 subject nested-reference unchanged"},{"id":"IETF RFC 2991","type":"specification","body":"IETF","designation":"RFC 2991","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2991.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2991.txt","https://www.rfc-editor.org/rfc/rfc2991.pdf"],"folder":"IETF/RFC-2991","files":{"txt":{"path":"standards/IETF/RFC-2991/RFC-2991.txt","sha256":"7ed2e5951b4a31294333563c2829d7ba04b2e2d9e56362653bbd9d9311ad1e7f"}},"tags":["nested-reference","unchanged"],"summary":"Various routing protocols, including Open Shortest Path First (OSPF)\n and Intermediate System to Intermediate System (ISIS), explicitly\n allow \"Equal-Cost Multipath\" (ECMP) routing. Some router\n implementations also allow equal-cost multipath usage with RIP and\n other routing protocols. The effect of multipath routing on a\n forwarder is that the forwarder potentially has several next-hops for\n any given destination and must use some method to choose which next-\n hop should be used for a given data packet.\n\n1. Introduction\n\n Various routing protocols, including OSPF and ISIS, explicitly allow\n \"Equal-Cost Multipath\" routing. Some router implementations also\n allow equal-cost multipath usage with RIP and other routing\n protocols. Using equal-cost multipath means that if multiple equal-\n cost routes to the same destination exist, they can be discovered and\n used to provide load balancing am","scope_keywords":["2991","delivery","hash","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2992","folder":"IETF/RFC-2992","source":"IETF/RFC-2992/RFC-2992.txt","version":null},{"body":"IETF","designation":"RFC 4080","folder":"IETF/RFC-4080","source":"IETF/RFC-4080/RFC-4080.txt","version":null},{"body":"IETF","designation":"RFC 4311","folder":"IETF/RFC-4311","source":"IETF/RFC-4311/RFC-4311.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6438","folder":"IETF/RFC-6438","source":"IETF/RFC-6438/RFC-6438.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7098","folder":"IETF/RFC-7098","source":"IETF/RFC-7098/RFC-7098.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 2991 Various routing protocols, including Open Shortest Path First (OSPF)\n and Intermediate System to Intermediate System (ISIS), explicitly\n allow \"Equal-Cost Multipath\" (ECMP) routing. Some router\n implementations also allow equal-cost multipath usage with RIP and\n other routing protocols. The effect of multipath routing on a\n forwarder is that the forwarder potentially has several next-hops for\n any given destination and must use some method to choose which next-\n hop should be used for a given data packet.\n\n1. Introduction\n\n Various routing protocols, including OSPF and ISIS, explicitly allow\n \"Equal-Cost Multipath\" routing. Some router implementations also\n allow equal-cost multipath usage with RIP and other routing\n protocols. Using equal-cost multipath means that if multiple equal-\n cost routes to the same destination exist, they can be discovered and\n used to provide load balancing am 2991 delivery hash key path nested-reference unchanged"},{"id":"IETF RFC 3509","type":"specification","body":"IETF","designation":"RFC 3509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3509.txt","https://www.rfc-editor.org/rfc/rfc3509.pdf"],"folder":"IETF/RFC-3509","files":{"txt":{"path":"standards/IETF/RFC-3509/RFC-3509.txt","sha256":"96437f289027395488142ceb1814bae170e057d9daefa0476fd458f4a65c8530"}},"tags":["nested-reference","unchanged"],"summary":"Open Shortest Path First (OSPF) is a link-state intra-domain routing\n protocol used for routing in IP networks. Though the definition of\n the Area Border Router (ABR) in the OSPF specification does not\n require a router with multiple attached areas to have a backbone\n connection, it is actually necessary to provide successful routing to\n the inter-area and external destinations. If this requirement is not\n met, all traffic destined for the areas not connected to such an ABR\n or out of the OSPF domain, is dropped. This document describes\n alternative ABR behaviors implemented in Cisco and IBM routers.\n\n1 Overview","scope_keywords":["3509","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5286","folder":"IETF/RFC-5286","source":"IETF/RFC-5286/RFC-5286.txt","version":null}],"search_text":"IETF RFC 3509 Open Shortest Path First (OSPF) is a link-state intra-domain routing\n protocol used for routing in IP networks. Though the definition of\n the Area Border Router (ABR) in the OSPF specification does not\n require a router with multiple attached areas to have a backbone\n connection, it is actually necessary to provide successful routing to\n the inter-area and external destinations. If this requirement is not\n met, all traffic destined for the areas not connected to such an ABR\n or out of the OSPF domain, is dropped. This document describes\n alternative ABR behaviors implemented in Cisco and IBM routers.\n\n1 Overview 3509 path nested-reference unchanged"},{"id":"IETF RFC 3753","type":"specification","body":"IETF","designation":"RFC 3753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3753.txt","https://www.rfc-editor.org/rfc/rfc3753.pdf"],"folder":"IETF/RFC-3753","files":{"txt":{"path":"standards/IETF/RFC-3753/RFC-3753.txt","sha256":"e0423efaefa4119357aef92b8c5b9617c9e09a39559659f5553c71b6117cb1e3"}},"tags":["nested-reference","unchanged"],"summary":"There is a need for common definitions of terminology in the work to\n be done around IP mobility. This document defines terms for mobility\n related terminology. The document originated out of work done in the\n Seamoby Working Group but has broader applicability for terminology\n used in IETF-wide discourse on technology for mobility and IP\n networks. Other working groups dealing with mobility may want to\n take advantage of this terminology.","scope_keywords":["3753","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3963","folder":"IETF/RFC-3963","source":"IETF/RFC-3963/RFC-3963.txt","version":null},{"body":"IETF","designation":"RFC 4066","folder":"IETF/RFC-4066","source":"IETF/RFC-4066/RFC-4066.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4135","folder":"IETF/RFC-4135","source":"IETF/RFC-4135/RFC-4135.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4640","folder":"IETF/RFC-4640","source":"IETF/RFC-4640/RFC-4640.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4832","folder":"IETF/RFC-4832","source":"IETF/RFC-4832/RFC-4832.txt","version":null},{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4887","folder":"IETF/RFC-4887","source":"IETF/RFC-4887/RFC-4887.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5417","folder":"IETF/RFC-5417","source":"IETF/RFC-5417/RFC-5417.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null}],"search_text":"IETF RFC 3753 There is a need for common definitions of terminology in the work to\n be done around IP mobility. This document defines terms for mobility\n related terminology. The document originated out of work done in the\n Seamoby Working Group but has broader applicability for terminology\n used in IETF-wide discourse on technology for mobility and IP\n networks. Other working groups dealing with mobility may want to\n take advantage of this terminology. 3753 registered nested-reference unchanged"},{"id":"IETF RFC 4222","type":"specification","body":"IETF","designation":"RFC 4222","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4222.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4222.txt","https://www.rfc-editor.org/rfc/rfc4222.pdf"],"folder":"IETF/RFC-4222","files":{"txt":{"path":"standards/IETF/RFC-4222/RFC-4222.txt","sha256":"f956dd810faf3fc12cc809d318c5039c6e68883a8db2f2ca1b985aeb74f89011"}},"tags":["nested-reference","unchanged"],"summary":"This document recommends methods that are intended to improve the\n scalability and stability of large networks using Open Shortest Path\n First (OSPF) Version 2 protocol. The methods include processing OSPF\n Hellos and Link State Advertisement (LSA) Acknowledgments at a higher\n priority compared to other OSPF packets, and other congestion\n avoidance procedures.","scope_keywords":["4222","authentication","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6863","folder":"IETF/RFC-6863","source":"IETF/RFC-6863/RFC-6863.txt","version":null}],"search_text":"IETF RFC 4222 This document recommends methods that are intended to improve the\n scalability and stability of large networks using Open Shortest Path\n First (OSPF) Version 2 protocol. The methods include processing OSPF\n Hellos and Link State Advertisement (LSA) Acknowledgments at a higher\n priority compared to other OSPF packets, and other congestion\n avoidance procedures. 4222 authentication path nested-reference unchanged"},{"id":"IETF RFC 4811","type":"specification","body":"IETF","designation":"RFC 4811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4811.txt","https://www.rfc-editor.org/rfc/rfc4811.pdf"],"folder":"IETF/RFC-4811","files":{"txt":{"path":"standards/IETF/RFC-4811/RFC-4811.txt","sha256":"817a13c9794808391218d14a53cc787474f6a4f0221b8641a98648667a9ca940"}},"tags":["nested-reference","unchanged"],"summary":"OSPF is a link-state intra-domain routing protocol used in IP\n networks. Link State Database (LSDB) synchronization in OSPF is\n achieved via two methods -- initial LSDB synchronization when an OSPF\n router has just been connected to the network and asynchronous\n flooding that ensures continuous LSDB synchronization in the presence\n of topology changes after the initial procedure was completed. It\n may sometime be necessary for OSPF routers to resynchronize their\n LSDBs. The OSPF standard, however, does not allow routers to do so\n without actually changing the topology view of the network.\n\n This memo describes a vendor-specific mechanism to perform such a\n form of out-of-band LSDB synchronization. The mechanism described in\n this document was proposed before Graceful OSPF Restart, as described\n in RFC 3623, came into existence. It is implemented/supported by at\n least one major vendor an","scope_keywords":["4811","algorithm","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4812","folder":"IETF/RFC-4812","source":"IETF/RFC-4812/RFC-4812.txt","version":null},{"body":"IETF","designation":"RFC 4813","folder":"IETF/RFC-4813","source":"IETF/RFC-4813/RFC-4813.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null}],"search_text":"IETF RFC 4811 OSPF is a link-state intra-domain routing protocol used in IP\n networks. Link State Database (LSDB) synchronization in OSPF is\n achieved via two methods -- initial LSDB synchronization when an OSPF\n router has just been connected to the network and asynchronous\n flooding that ensures continuous LSDB synchronization in the presence\n of topology changes after the initial procedure was completed. It\n may sometime be necessary for OSPF routers to resynchronize their\n LSDBs. The OSPF standard, however, does not allow routers to do so\n without actually changing the topology view of the network.\n\n This memo describes a vendor-specific mechanism to perform such a\n form of out-of-band LSDB synchronization. The mechanism described in\n this document was proposed before Graceful OSPF Restart, as described\n in RFC 3623, came into existence. It is implemented/supported by at\n least one major vendor an 4811 algorithm trust nested-reference unchanged"},{"id":"IETF RFC 4812","type":"specification","body":"IETF","designation":"RFC 4812","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4812.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4812.txt","https://www.rfc-editor.org/rfc/rfc4812.pdf"],"folder":"IETF/RFC-4812","files":{"txt":{"path":"standards/IETF/RFC-4812/RFC-4812.txt","sha256":"f67edc356daaadeac8bf3f52dba985bf6e2574a5bffec47292730e08083a3188"}},"tags":["nested-reference","unchanged"],"summary":"OSPF is a link-state intra-domain routing protocol used in IP\n networks. Routers find new and detect unreachable neighbors via the\n Hello subprotocol. Hello OSPF packets are also used to ensure two-\n way connectivity within time. When a router restarts its OSPF\n software, it may not know its neighbors. If such a router sends a\n Hello packet on an interface, its neighbors are going to reset the\n adjacency, which may not be desirable in certain conditions.\n\n This memo describes a vendor-specific mechanism that allows OSPF\n routers to inform their neighbors about the restart process. Note\n that this mechanism requires support from neighboring routers. The\n mechanism described in this document was proposed before Graceful\n OSPF Restart, as described in RFC 3623, came into existence. It is\n implemented/supported by at least one major vendor and is currently\n deployed in the field. The purpose","scope_keywords":["4812","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4813","folder":"IETF/RFC-4813","source":"IETF/RFC-4813/RFC-4813.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null}],"search_text":"IETF RFC 4812 OSPF is a link-state intra-domain routing protocol used in IP\n networks. Routers find new and detect unreachable neighbors via the\n Hello subprotocol. Hello OSPF packets are also used to ensure two-\n way connectivity within time. When a router restarts its OSPF\n software, it may not know its neighbors. If such a router sends a\n Hello packet on an interface, its neighbors are going to reset the\n adjacency, which may not be desirable in certain conditions.\n\n This memo describes a vendor-specific mechanism that allows OSPF\n routers to inform their neighbors about the restart process. Note\n that this mechanism requires support from neighboring routers. The\n mechanism described in this document was proposed before Graceful\n OSPF Restart, as described in RFC 3623, came into existence. It is\n implemented/supported by at least one major vendor and is currently\n deployed in the field. The purpose 4812 trust nested-reference unchanged"},{"id":"IETF RFC 4813","type":"specification","body":"IETF","designation":"RFC 4813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4813.txt","https://www.rfc-editor.org/rfc/rfc4813.pdf"],"folder":"IETF/RFC-4813","files":{"txt":{"path":"standards/IETF/RFC-4813/RFC-4813.txt","sha256":"9ad64b9a322907dd72411f45ba9b929638a0f6035c682c8416d1449ba328e302"}},"tags":["nested-reference","unchanged"],"summary":"OSPF is a link-state intra-domain routing protocol used in IP\n networks. OSPF routers exchange information on a link using packets\n that follow a well-defined format. The format of OSPF packets is not\n flexible enough to enable applications to exchange arbitrary data,\n which may be necessary in certain situations. This memo describes a\n vendor-specific, backward-compatible technique to perform link-local\n signaling, i.e., exchange arbitrary data on a link.\n\nFriedman, et al. Experimental [Page 1]\n\f\nRFC 4813 OSPF Link-Local Signaling February 2007","scope_keywords":["4813","authentication","delivery","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4811","folder":"IETF/RFC-4811","source":"IETF/RFC-4811/RFC-4811.txt","version":null},{"body":"IETF","designation":"RFC 4812","folder":"IETF/RFC-4812","source":"IETF/RFC-4812/RFC-4812.txt","version":null},{"body":"IETF","designation":"RFC 5449","folder":"IETF/RFC-5449","source":"IETF/RFC-5449/RFC-5449.txt","version":null},{"body":"IETF","designation":"RFC 5613","folder":"IETF/RFC-5613","source":"IETF/RFC-5613/RFC-5613.txt","version":null}],"search_text":"IETF RFC 4813 OSPF is a link-state intra-domain routing protocol used in IP\n networks. OSPF routers exchange information on a link using packets\n that follow a well-defined format. The format of OSPF packets is not\n flexible enough to enable applications to exchange arbitrary data,\n which may be necessary in certain situations. This memo describes a\n vendor-specific, backward-compatible technique to perform link-local\n signaling, i.e., exchange arbitrary data on a link.\n\nFriedman, et al. Experimental [Page 1]\n\f\nRFC 4813 OSPF Link-Local Signaling February 2007 4813 authentication delivery trust nested-reference unchanged"},{"id":"IETF RFC 5243","type":"specification","body":"IETF","designation":"RFC 5243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5243.txt","https://www.rfc-editor.org/rfc/rfc5243.pdf"],"folder":"IETF/RFC-5243","files":{"txt":{"path":"standards/IETF/RFC-5243/RFC-5243.txt","sha256":"80ecce62bd317cdfb340fdff28c04001340843e60173adfd8a925a46c2ce1bbd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Ogier\nRequest for Comments: 5243 SRI International\nCategory: Informational May 2008\n\n OSPF Database Exchange Summary List Optimization\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nAbstract\n\n This document describes a backward-compatible optimization for the\n Database Exchange process in OSPFv2 and OSPFv3. In this\n optimization, a router does not list a Link State Advertisement (LSA)\n in Database Description packets sent to a neighbor, if the same or a\n more recent instance of the LSA was listed in a Database Description\n packet already received from the neighbor. This optimization reduces\n Database Description overhead by about 50% in large networks. This\n optimization does not affect synchronization, since it only omits\n unnecessa","scope_keywords":["5243"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5614","folder":"IETF/RFC-5614","source":"IETF/RFC-5614/RFC-5614.txt","version":null}],"search_text":"IETF RFC 5243 Network Working Group R. Ogier\nRequest for Comments: 5243 SRI International\nCategory: Informational May 2008\n\n OSPF Database Exchange Summary List Optimization\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nAbstract\n\n This document describes a backward-compatible optimization for the\n Database Exchange process in OSPFv2 and OSPFv3. In this\n optimization, a router does not list a Link State Advertisement (LSA)\n in Database Description packets sent to a neighbor, if the same or a\n more recent instance of the LSA was listed in a Database Description\n packet already received from the neighbor. This optimization reduces\n Database Description overhead by about 50% in large networks. This\n optimization does not affect synchronization, since it only omits\n unnecessa 5243 nested-reference unchanged"},{"id":"IETF RFC 3763","type":"specification","body":"IETF","designation":"RFC 3763","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3763.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3763.txt","https://www.rfc-editor.org/rfc/rfc3763.pdf"],"folder":"IETF/RFC-3763","files":{"txt":{"path":"standards/IETF/RFC-3763/RFC-3763.txt","sha256":"464a92fa2ad210961e8945479422052a5a1b4be14e5e9c1f6557820f013fe6be"}},"tags":["nested-reference","unchanged"],"summary":"With growing availability of good time sources to network nodes, it\n becomes increasingly possible to measure one-way IP performance\n metrics with high precision. To do so in an interoperable manner, a\n common protocol for such measurements is required. This document\n specifies requirements for a one-way active measurement protocol\n (OWAMP) standard. The protocol can measure one-way delay, as well as\n other unidirectional characteristics, such as one-way loss.\n\n1. Motivations and Goals\n\n The IETF IP Performance Metrics (IPPM) working group has proposed\n standards track metrics for one-way packet delay [RFC2679] and loss\n [RFC 2680] across Internet paths. Although there are now several\n measurement platforms that implement the collection of these metrics\n ([CQOS], [BRIX], [RIPE], [SURVEYOR]), there is not currently a\n standard for interoperability. This requirements document is aimed\n at ","scope_keywords":["3763","algorithm","algorithms","delivery","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null}],"search_text":"IETF RFC 3763 With growing availability of good time sources to network nodes, it\n becomes increasingly possible to measure one-way IP performance\n metrics with high precision. To do so in an interoperable manner, a\n common protocol for such measurements is required. This document\n specifies requirements for a one-way active measurement protocol\n (OWAMP) standard. The protocol can measure one-way delay, as well as\n other unidirectional characteristics, such as one-way loss.\n\n1. Motivations and Goals\n\n The IETF IP Performance Metrics (IPPM) working group has proposed\n standards track metrics for one-way packet delay [RFC2679] and loss\n [RFC 2680] across Internet paths. Although there are now several\n measurement platforms that implement the collection of these metrics\n ([CQOS], [BRIX], [RIPE], [SURVEYOR]), there is not currently a\n standard for interoperability. This requirements document is aimed\n at  3763 algorithm algorithms delivery path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 6248","type":"specification","body":"IETF","designation":"RFC 6248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6248.txt","https://www.rfc-editor.org/rfc/rfc6248.pdf"],"folder":"IETF/RFC-6248","files":{"txt":{"path":"standards/IETF/RFC-6248/RFC-6248.txt","sha256":"40a83174b1f37b10c5f3f94a45774d37e9f49b45a06a48bc8cb87ad12e8b88c4"}},"tags":["nested-reference","unchanged"],"summary":"This memo reclassifies RFC 4148, \"IP Performance Metrics (IPPM)\n Metrics Registry\", as Obsolete, and withdraws the IANA IPPM Metrics\n Registry itself from use because it is obsolete. The current\n registry structure has been found to be insufficiently detailed to\n uniquely identify IPPM metrics. Despite apparent efforts to find\n current or even future users, no one responded to the call for\n interest in the RFC 4148 registry during the second half of 2010.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for","scope_keywords":["6248","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 6248 This memo reclassifies RFC 4148, \"IP Performance Metrics (IPPM)\n Metrics Registry\", as Obsolete, and withdraws the IANA IPPM Metrics\n Registry itself from use because it is obsolete. The current\n registry structure has been found to be insufficiently detailed to\n uniquely identify IPPM metrics. Despite apparent efforts to find\n current or even future users, no one responded to the call for\n interest in the RFC 4148 registry during the second half of 2010.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for 6248 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6703","type":"specification","body":"IETF","designation":"RFC 6703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6703.txt","https://www.rfc-editor.org/rfc/rfc6703.pdf"],"folder":"IETF/RFC-6703","files":{"txt":{"path":"standards/IETF/RFC-6703/RFC-6703.txt","sha256":"16676567380ba11a8a40b04c593d1f219e74bff8037306188024455a56b5dd46"}},"tags":["nested-reference","unchanged"],"summary":"Consumers of IP network performance metrics have many different uses\n in mind. This memo provides \"long-term\" reporting considerations\n (e.g., hours, days, weeks, or months, as opposed to 10 seconds),\n based on analysis of the points of view of two key audiences. It\n describes how these audience categories affect the selection of\n metric parameters and options when seeking information that serves\n their needs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section ","scope_keywords":["6703","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6808","folder":"IETF/RFC-6808","source":"IETF/RFC-6808/RFC-6808.txt","version":null},{"body":"IETF","designation":"RFC 7290","folder":"IETF/RFC-7290","source":"IETF/RFC-7290/RFC-7290.txt","version":null},{"body":"IETF","designation":"RFC 7312","folder":"IETF/RFC-7312","source":"IETF/RFC-7312/RFC-7312.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null}],"search_text":"IETF RFC 6703 Consumers of IP network performance metrics have many different uses\n in mind. This memo provides \"long-term\" reporting considerations\n (e.g., hours, days, weeks, or months, as opposed to 10 seconds),\n based on analysis of the points of view of two key audiences. It\n describes how these audience categories affect the selection of\n metric parameters and options when seeking information that serves\n their needs.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section  6703 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2603","type":"specification","body":"IETF","designation":"RFC 2603","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2603.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2603.txt","https://www.rfc-editor.org/rfc/rfc2603.pdf"],"folder":"IETF/RFC-2603","files":{"txt":{"path":"standards/IETF/RFC-2603/RFC-2603.txt","sha256":"672fd5ace57a14022ae938da69ed1a5463d0df086936b0ebf46332fc203580d6"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate NHRP servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use NHRP [1] is cumbersome\n and error-prone since it requires at least one ATM address to be\n statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use NHRP\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the informat","scope_keywords":["2603","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2603 This memo defines how ILMI-based Server Discovery, which provides a\n method for ATM-attached hosts and routers to dynamically determine\n the ATM addresses of servers, shall be used to locate NHRP servers.\n\n1. Introduction\n\n Presently, configuring a host or router to use NHRP [1] is cumbersome\n and error-prone since it requires at least one ATM address to be\n statically configured on each host or router in the network.\n Further, it is impossible to implement a diskless host to use NHRP\n since local configuration is required. ILMI-based Server Discovery,\n hereafter referred to as \"server discovery,\" provides a solution to\n these problems.\n\n A brief overview of the Integrated Local Management Interface (ILMI)\n and the Service Registry MIB, as defined by the ATM Forum, are\n provided in this memo. The reader should consult [2] for a complete\n description of ILMI and this MIB, but the informat 2603 management nested-reference unchanged"},{"id":"IETF RFC 2333","type":"specification","body":"IETF","designation":"RFC 2333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2333.txt","https://www.rfc-editor.org/rfc/rfc2333.pdf"],"folder":"IETF/RFC-2333","files":{"txt":{"path":"standards/IETF/RFC-2333/RFC-2333.txt","sha256":"970ee7d6e86818027cd896a47e7c3414cb696441b652922602f203fb1aea68a5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Cansever\nRequest for Comments: 2333 GTE Laboratories, Inc.\nCategory: Standards Track April 1998\n\n NHRP Protocol Applicability Statement\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n As required by the Routing Protocol Criteria [RFC 1264], this memo\n discusses the applicability of the Next Hop Resolution Protocol\n (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access\n (NBMA) networks, such as ATM, SMDS and X.25.\n\n1. Protocol Documents\n\n The NHR","scope_keywords":["2333","algorithm","attribute","delivery","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2333 Network Working Group D. Cansever\nRequest for Comments: 2333 GTE Laboratories, Inc.\nCategory: Standards Track April 1998\n\n NHRP Protocol Applicability Statement\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n As required by the Routing Protocol Criteria [RFC 1264], this memo\n discusses the applicability of the Next Hop Resolution Protocol\n (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access\n (NBMA) networks, such as ATM, SMDS and X.25.\n\n1. Protocol Documents\n\n The NHR 2333 algorithm attribute delivery key path subject nested-reference unchanged"},{"id":"IETF RFC 2345","type":"specification","body":"IETF","designation":"RFC 2345","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2345.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2345.txt","https://www.rfc-editor.org/rfc/rfc2345.pdf"],"folder":"IETF/RFC-2345","files":{"txt":{"path":"standards/IETF/RFC-2345/RFC-2345.txt","sha256":"08118c3b3fb79bfe4724d2ee4cc4ee9339918a126cd5ef829bfdbfc2ec9464d8"}},"tags":["nested-reference","unchanged"],"summary":"Location of web information for particular companies based on their\n names has become an increasingly difficult problem as the Internet\n and the web grow. The use of a naming convention and the domain\n name system (DNS) for that purpose has caused complications for the\n latter while not solving the problem. While there have been several\n proposals to use contemporary, high-capability, directory service and\n search protocols to reduce the dependencies on DNS conventions, none\n of them have been significantly deployed.\n\n This document proposes a company name to URL mapping service based on\n the oldest and least complex of Internet directory protocols, whois,\n in order to explore whether an extremely simple and widely-deployed\n protocol can succeed where more complex and powerful options have\n failed or been excessively delayed.\n\n1. Introduction and Context\n\n In recent months, there have be","scope_keywords":["2345","http","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2345 Location of web information for particular companies based on their\n names has become an increasingly difficult problem as the Internet\n and the web grow. The use of a naming convention and the domain\n name system (DNS) for that purpose has caused complications for the\n latter while not solving the problem. While there have been several\n proposals to use contemporary, high-capability, directory service and\n search protocols to reduce the dependencies on DNS conventions, none\n of them have been significantly deployed.\n\n This document proposes a company name to URL mapping service based on\n the oldest and least complex of Internet directory protocols, whois,\n in order to explore whether an extremely simple and widely-deployed\n protocol can succeed where more complex and powerful options have\n failed or been excessively delayed.\n\n1. Introduction and Context\n\n In recent months, there have be 2345 http policy nested-reference unchanged"},{"id":"IETF RFC 7995","type":"specification","body":"IETF","designation":"RFC 7995","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7995.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7995.txt","https://www.rfc-editor.org/rfc/rfc7995.pdf"],"folder":"IETF/RFC-7995","files":{"txt":{"path":"standards/IETF/RFC-7995/RFC-7995.txt","sha256":"f53d12e32a05bd08e0a049aad20765460bc4b5d037ee812e7ce1d0361ab8051f"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses options and requirements for the PDF\n rendering of RFCs in the RFC Series, as outlined in RFC 6949. It\n also discusses the use of PDF for Internet-Drafts, and available or\n needed software tools for producing and working with PDF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.","scope_keywords":["7995","http","license","management","presentation","preservation","profile","profiles","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null}],"search_text":"IETF RFC 7995 This document discusses options and requirements for the PDF\n rendering of RFCs in the RFC Series, as outlined in RFC 6949. It\n also discusses the use of PDF for Internet-Drafts, and available or\n needed software tools for producing and working with PDF.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor. 7995 http license management presentation preservation profile profiles signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 235","type":"specification","body":"IETF","designation":"RFC 235","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc235.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc235.txt","https://www.rfc-editor.org/rfc/rfc235.pdf"],"folder":"IETF/RFC-235","files":{"txt":{"path":"standards/IETF/RFC-235/RFC-235.txt","sha256":"4059e7ba3846d34fbcb9f3a8995f3bf5f0847353d68464502b1e234f3fd922b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Westheimer\nRequest for Comments: 235 BBN\nNIC: 7652 September 27, 1971\nObsoletes: None\nUpdates: None\n\n SITE STATUS\n\n Beginning with this RFC, BBN will report on the status of most\n Network Hosts approximately once every two weeks. The information\n for these reports will be gained from talking to people at each site,\n and from experimental \"data\". These data will be the results of\n daily attempts to log into each of the Hosts which might be\n accessible to a Network user; the attempts will have been made from\n the BBN prototype Terminal IMP at a random time each weekday.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) for at least a\n month. Included here are:\n\n Network Site Computer\n Address\n\n 71 Ra","scope_keywords":["235"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 240","folder":"IETF/RFC-240","source":"IETF/RFC-240/RFC-240.txt","version":null}],"search_text":"IETF RFC 235 Network Working Group E. Westheimer\nRequest for Comments: 235 BBN\nNIC: 7652 September 27, 1971\nObsoletes: None\nUpdates: None\n\n SITE STATUS\n\n Beginning with this RFC, BBN will report on the status of most\n Network Hosts approximately once every two weeks. The information\n for these reports will be gained from talking to people at each site,\n and from experimental \"data\". These data will be the results of\n daily attempts to log into each of the Hosts which might be\n accessible to a Network user; the attempts will have been made from\n the BBN prototype Terminal IMP at a random time each weekday.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) for at least a\n month. Included here are:\n\n Network Site Computer\n Address\n\n 71 Ra 235 nested-reference unchanged"},{"id":"IETF RFC 240","type":"specification","body":"IETF","designation":"RFC 240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc240.txt","https://www.rfc-editor.org/rfc/rfc240.pdf"],"folder":"IETF/RFC-240","files":{"txt":{"path":"standards/IETF/RFC-240/RFC-240.txt","sha256":"916a29991b25e7765efaf613525097f0bbca090f76843a7ddf1a78061d7b5769"}},"tags":["nested-reference","unchanged"],"summary":"Networking Group A. McKenzie\nRequest for Comments: 240 BBN\nNIC #7665 30 September 1971\nCategories: F, G.3 Rand 50ctu\nUpdates: none\nObsoletes: RFC 235\n\n SITE STATUS\n\n Due to extensive typographic errors in RFC #235, I have\ndecided to reissue the first of our experimental site status reports.\n\n In compiling RFC #235, I followed the principle that\ntimeliness was somewhat more important than extremely careful editing;\nthis seemed to me to be in keeping with the original RFC philosophy. I\nam sorry for any embarrassment this may have caused to anyone associated\nwith the Network, and accept full responsibility for the content of RFC\n#235. I will try to do a better job in the future.\n\nAlex McKenzie\n\n SITE STATUS\n\n Beginning with this RFC, BBN will report on the status of\nmost Network Hosts approximately once every two weeks. The information\nfor these reports will be gained from talking to people","scope_keywords":["240"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 240 Networking Group A. McKenzie\nRequest for Comments: 240 BBN\nNIC #7665 30 September 1971\nCategories: F, G.3 Rand 50ctu\nUpdates: none\nObsoletes: RFC 235\n\n SITE STATUS\n\n Due to extensive typographic errors in RFC #235, I have\ndecided to reissue the first of our experimental site status reports.\n\n In compiling RFC #235, I followed the principle that\ntimeliness was somewhat more important than extremely careful editing;\nthis seemed to me to be in keeping with the original RFC philosophy. I\nam sorry for any embarrassment this may have caused to anyone associated\nwith the Network, and accept full responsibility for the content of RFC\n#235. I will try to do a better job in the future.\n\nAlex McKenzie\n\n SITE STATUS\n\n Beginning with this RFC, BBN will report on the status of\nmost Network Hosts approximately once every two weeks. The information\nfor these reports will be gained from talking to people 240 nested-reference unchanged"},{"id":"IETF RFC 2992","type":"specification","body":"IETF","designation":"RFC 2992","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2992.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2992.txt","https://www.rfc-editor.org/rfc/rfc2992.pdf"],"folder":"IETF/RFC-2992","files":{"txt":{"path":"standards/IETF/RFC-2992/RFC-2992.txt","sha256":"f83257fe427dc29e498c5d1c03b285d757c2ce0750aaa5c62892b0babfa68010"}},"tags":["nested-reference","unchanged"],"summary":"Equal-cost multi-path (ECMP) is a routing technique for routing\n packets along multiple paths of equal cost. The forwarding engine\n identifies paths by next-hop. When forwarding a packet the router\n must decide which next-hop (path) to use. This document gives an\n analysis of one method for making that decision. The analysis\n includes the performance of the algorithm and the disruption caused\n by changes to the set of next-hops.\n\n1. Hash-Threshold\n\n One method for determining which next-hop to use when routing with\n ECMP can be called hash-threshold. The router first selects a key by\n performing a hash (e.g., CRC16) over the packet header fields that\n identify a flow. The N next-hops have been assigned unique regions\n in the key space. The router uses the key to determine which region\n and thus which next-hop to use.\n\n As an example of hash-threshold, upon receiving a packet the router\n ","scope_keywords":["2992","algorithm","algorithms","hash","key","keys","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2991","folder":"IETF/RFC-2991","source":"IETF/RFC-2991/RFC-2991.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 7424","folder":"IETF/RFC-7424","source":"IETF/RFC-7424/RFC-7424.txt","version":null},{"body":"IETF","designation":"RFC 8021","folder":"IETF/RFC-8021","source":"IETF/RFC-8021/RFC-8021.txt","version":null}],"search_text":"IETF RFC 2992 Equal-cost multi-path (ECMP) is a routing technique for routing\n packets along multiple paths of equal cost. The forwarding engine\n identifies paths by next-hop. When forwarding a packet the router\n must decide which next-hop (path) to use. This document gives an\n analysis of one method for making that decision. The analysis\n includes the performance of the algorithm and the disruption caused\n by changes to the set of next-hops.\n\n1. Hash-Threshold\n\n One method for determining which next-hop to use when routing with\n ECMP can be called hash-threshold. The router first selects a key by\n performing a hash (e.g., CRC16) over the packet header fields that\n identify a flow. The N next-hops have been assigned unique regions\n in the key space. The router uses the key to determine which region\n and thus which next-hop to use.\n\n As an example of hash-threshold, upon receiving a packet the router\n  2992 algorithm algorithms hash key keys path nested-reference unchanged"},{"id":"IETF RFC 4621","type":"specification","body":"IETF","designation":"RFC 4621","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4621.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4621.txt","https://www.rfc-editor.org/rfc/rfc4621.pdf"],"folder":"IETF/RFC-4621","files":{"txt":{"path":"standards/IETF/RFC-4621/RFC-4621.txt","sha256":"58996760ebd18446fe22a16e6dcf49264c4e530413cdd863b809bb3952493d2b"}},"tags":["nested-reference","unchanged"],"summary":"The IKEv2 Mobility and Multihoming (MOBIKE) protocol is an extension\n of the Internet Key Exchange Protocol version 2 (IKEv2). These\n extensions should enable an efficient management of IKE and IPsec\n Security Associations when a host possesses multiple IP addresses\n and/or where IP addresses of an IPsec host change over time (for\n example, due to mobility).\n\n This document discusses the involved network entities and the\n relationship between IKEv2 signaling and information provided by\n other protocols. Design decisions for the MOBIKE protocol,\n background information, and discussions within the working group are\n recorded.\n\nKivinen & Tschofenig Informational [Page 1]\n\f\nRFC 4621 Design of the MOBIKE Protocol August 2006","scope_keywords":["4621","algorithm","algorithms","authentication","key","keys","management","path","policies","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4621 The IKEv2 Mobility and Multihoming (MOBIKE) protocol is an extension\n of the Internet Key Exchange Protocol version 2 (IKEv2). These\n extensions should enable an efficient management of IKE and IPsec\n Security Associations when a host possesses multiple IP addresses\n and/or where IP addresses of an IPsec host change over time (for\n example, due to mobility).\n\n This document discusses the involved network entities and the\n relationship between IKEv2 signaling and information provided by\n other protocols. Design decisions for the MOBIKE protocol,\n background information, and discussions within the working group are\n recorded.\n\nKivinen & Tschofenig Informational [Page 1]\n\f\nRFC 4621 Design of the MOBIKE Protocol August 2006 4621 algorithm algorithms authentication key keys management path policies presentation nested-reference unchanged"},{"id":"IETF RFC 2372","type":"specification","body":"IETF","designation":"RFC 2372","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2372.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2372.txt","https://www.rfc-editor.org/rfc/rfc2372.pdf"],"folder":"IETF/RFC-2372","files":{"txt":{"path":"standards/IETF/RFC-2372/RFC-2372.txt","sha256":"c10f85b7360b3a021ca8783e75f6902a576df116d251e3b70a7d87f05ee43b9a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the purpose (usage scenarios), and\n requirements for the Transaction Internet Protocol [1]. It is\n intended to help qualify the necessary features and functions of the\n protocol. It also provides supplemental information to aid\n understanding and facilitate implementation of the TIP protocol.","scope_keywords":["2372","http","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2371","folder":"IETF/RFC-2371","source":"IETF/RFC-2371/RFC-2371.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 2372 This document describes the purpose (usage scenarios), and\n requirements for the Transaction Internet Protocol [1]. It is\n intended to help qualify the necessary features and functions of the\n protocol. It also provides supplemental information to aid\n understanding and facilitate implementation of the TIP protocol. 2372 http key nested-reference unchanged"},{"id":"IETF RFC 3587","type":"specification","body":"IETF","designation":"RFC 3587","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3587.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3587.txt","https://www.rfc-editor.org/rfc/rfc3587.pdf"],"folder":"IETF/RFC-3587","files":{"txt":{"path":"standards/IETF/RFC-3587/RFC-3587.txt","sha256":"abfc5694ddb6d52c42848f612837e9e7bea73e7a69107ac7a855df8b559e9a5e"}},"tags":["nested-reference","unchanged"],"summary":"This document obsoletes RFC 2374, \"An IPv6 Aggregatable Global\n Unicast Address Format\". It defined an IPv6 address allocation\n structure that includes Top Level Aggregator (TLA) and Next Level\n Aggregator (NLA). This document makes RFC 2374 and the TLA/NLA\n structure historic.\n\n1. Introduction\n\n RFC 2374, \"An IPv6 Aggregatable Global Unicast Address Format\",\n defined an IPv6 address allocation structure that includes TLA and\n NLA. This document replaces RFC 2374, and makes RFC 2374 and the\n TLA/NLA structure historic.\n\n2. TLA/NLA Made Historic\n\n The TLA/NLA scheme has been replaced by a coordinated allocation\n policy defined by the Regional Internet Registries (RIRs) [IPV6RIR].\n\n Part of the motivation for obsoleting the TLA/NLA structure is\n technical; for instance, there is concern that TLA/NLA is not the\n technically best approach at this stage of the deployment of IPv6.\n Moreover, t","scope_keywords":["3587","http","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4193","folder":"IETF/RFC-4193","source":"IETF/RFC-4193/RFC-4193.txt","version":null},{"body":"IETF","designation":"RFC 4291","folder":"IETF/RFC-4291","source":"IETF/RFC-4291/RFC-4291.txt","version":null},{"body":"IETF","designation":"RFC 4620","folder":"IETF/RFC-4620","source":"IETF/RFC-4620/RFC-4620.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5889","folder":"IETF/RFC-5889","source":"IETF/RFC-5889/RFC-5889.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null}],"search_text":"IETF RFC 3587 This document obsoletes RFC 2374, \"An IPv6 Aggregatable Global\n Unicast Address Format\". It defined an IPv6 address allocation\n structure that includes Top Level Aggregator (TLA) and Next Level\n Aggregator (NLA). This document makes RFC 2374 and the TLA/NLA\n structure historic.\n\n1. Introduction\n\n RFC 2374, \"An IPv6 Aggregatable Global Unicast Address Format\",\n defined an IPv6 address allocation structure that includes TLA and\n NLA. This document replaces RFC 2374, and makes RFC 2374 and the\n TLA/NLA structure historic.\n\n2. TLA/NLA Made Historic\n\n The TLA/NLA scheme has been replaced by a coordinated allocation\n policy defined by the Regional Internet Registries (RIRs) [IPV6RIR].\n\n Part of the motivation for obsoleting the TLA/NLA structure is\n technical; for instance, there is concern that TLA/NLA is not the\n technically best approach at this stage of the deployment of IPv6.\n Moreover, t 3587 http policy nested-reference unchanged"},{"id":"IETF RFC 238","type":"specification","body":"IETF","designation":"RFC 238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc238.txt","https://www.rfc-editor.org/rfc/rfc238.pdf"],"folder":"IETF/RFC-238","files":{"txt":{"path":"standards/IETF/RFC-238/RFC-238.txt","sha256":"c9ff9a2cdf47e1f74ff7e93e5d227119775414f641da7b94735575d0e543ec33"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. T. Braden\nRequest for Comments #238 UCLA-CCN\nNIC #7663 September 29, 1971\nCategory:\nUpdates: RFC #171, RFC #172\n\n COMMENTS ON DTP AND FTP PROPOSALS\n\n Data Transfer Protocol\n ----------------------\n\n 1. In the Descriptor/Count mode, the Information Separators should\n have a transaction sequence number field. Otherwise, the receiver\n cannot be sure he received all transactions before the separation.\n This requires that there be two forms of information separators, one\n for Descriptor/Count mode, the other for the DLE mode.\n\n 2. The modes-available handshake should not be mandatory, as it makes\n no sense in the simplex case. The receiver doesn't care what modes\n the transmitter might use; he only cares what mode is used, which\n he discovers when the first data or control transaction arrives. Even\n in the duplex case, it is not clear what use the receiver should make","scope_keywords":["238"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 238 Network Working Group R. T. Braden\nRequest for Comments #238 UCLA-CCN\nNIC #7663 September 29, 1971\nCategory:\nUpdates: RFC #171, RFC #172\n\n COMMENTS ON DTP AND FTP PROPOSALS\n\n Data Transfer Protocol\n ----------------------\n\n 1. In the Descriptor/Count mode, the Information Separators should\n have a transaction sequence number field. Otherwise, the receiver\n cannot be sure he received all transactions before the separation.\n This requires that there be two forms of information separators, one\n for Descriptor/Count mode, the other for the DLE mode.\n\n 2. The modes-available handshake should not be mandatory, as it makes\n no sense in the simplex case. The receiver doesn't care what modes\n the transmitter might use; he only cares what mode is used, which\n he discovers when the first data or control transaction arrives. Even\n in the duplex case, it is not clear what use the receiver should make 238 nested-reference unchanged"},{"id":"IETF RFC 5387","type":"specification","body":"IETF","designation":"RFC 5387","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5387.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5387.txt","https://www.rfc-editor.org/rfc/rfc5387.pdf"],"folder":"IETF/RFC-5387","files":{"txt":{"path":"standards/IETF/RFC-5387/RFC-5387.txt","sha256":"4bda60a6334a84635801fb3bfafd32afee93ec45ee9e5458fbcf01f428767c74"}},"tags":["nested-reference","unchanged"],"summary":"The Internet network security protocol suite, IPsec, requires\n authentication, usually of network-layer entities, to enable access\n control and provide security services. This authentication can be\n based on mechanisms such as pre-shared symmetric keys, certificates\n with associated asymmetric keys, or the use of Kerberos (via\n Kerberized Internet Negotiation of Keys (KINK)). The need to deploy\n authentication information and its associated identities can be a\n significant obstacle to the use of IPsec.\n\n This document explains the rationale for extending the Internet\n network security protocol suite to enable use of IPsec security\n services without authentication. These extensions are intended to\n protect communication, providing \"better-than-nothing security\"\n (BTNS). The extensions may be used on their own (this use is called\n Stand-Alone BTNS, or SAB) or may be used to provide network","scope_keywords":["5387","authentication","certificate","certificates","credential","credentials","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5386","folder":"IETF/RFC-5386","source":"IETF/RFC-5386/RFC-5386.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5387 The Internet network security protocol suite, IPsec, requires\n authentication, usually of network-layer entities, to enable access\n control and provide security services. This authentication can be\n based on mechanisms such as pre-shared symmetric keys, certificates\n with associated asymmetric keys, or the use of Kerberos (via\n Kerberized Internet Negotiation of Keys (KINK)). The need to deploy\n authentication information and its associated identities can be a\n significant obstacle to the use of IPsec.\n\n This document explains the rationale for extending the Internet\n network security protocol suite to enable use of IPsec security\n services without authentication. These extensions are intended to\n protect communication, providing \"better-than-nothing security\"\n (BTNS). The extensions may be used on their own (this use is called\n Stand-Alone BTNS, or SAB) or may be used to provide network 5387 authentication certificate certificates credential credentials http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5406","type":"specification","body":"IETF","designation":"RFC 5406","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5406.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5406.txt","https://www.rfc-editor.org/rfc/rfc5406.pdf"],"folder":"IETF/RFC-5406","files":{"txt":{"path":"standards/IETF/RFC-5406/RFC-5406.txt","sha256":"680f088b888b3ae8add7a4b54f2a61655f3744c9c3a0d2bce9cab63696962f35"}},"tags":["nested-reference","unchanged"],"summary":"The Security Considerations sections of many Internet Drafts say, in\n effect, \"just use IPsec\". While this is sometimes correct, more\n often it will leave users without real, interoperable security\n mechanisms. This memo offers some guidance on when IPsec Version 2\n should and should not be specified.\n\nBellovin Best Current Practice [Page 1]\n\f\nRFC 5406 IPsec Usage February 2009\n\n1. Introduction\n\n The Security Considerations sections of many Internet Drafts say, in\n effect, \"just use IPsec\". While the use of IPsec is sometimes the\n correct security solution, more information is needed to provide\n interoperable security solutions. In some cases, IPsec is\n unavailable in the likely endpoints. If IPsec is unavailable to --\n and hence unusable by -- a majority of the users in a particular\n protocol environment, then the specification of IPsec is tantamount\n to saying \"turn off security\" withi","scope_keywords":["5406","authentication","encryption","http","key","license","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null}],"search_text":"IETF RFC 5406 The Security Considerations sections of many Internet Drafts say, in\n effect, \"just use IPsec\". While this is sometimes correct, more\n often it will leave users without real, interoperable security\n mechanisms. This memo offers some guidance on when IPsec Version 2\n should and should not be specified.\n\nBellovin Best Current Practice [Page 1]\n\f\nRFC 5406 IPsec Usage February 2009\n\n1. Introduction\n\n The Security Considerations sections of many Internet Drafts say, in\n effect, \"just use IPsec\". While the use of IPsec is sometimes the\n correct security solution, more information is needed to provide\n interoperable security solutions. In some cases, IPsec is\n unavailable in the likely endpoints. If IPsec is unavailable to --\n and hence unusable by -- a majority of the users in a particular\n protocol environment, then the specification of IPsec is tantamount\n to saying \"turn off security\" withi 5406 authentication encryption http key license management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 2807","type":"specification","body":"IETF","designation":"RFC 2807","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2807.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2807.txt","https://www.rfc-editor.org/rfc/rfc2807.pdf"],"folder":"IETF/RFC-2807","files":{"txt":{"path":"standards/IETF/RFC-2807/RFC-2807.txt","sha256":"9b3a40f141dcf9370dfcba29cfeab3b5365b7dbc5b9a1e57af1231e3c299a98a"}},"tags":["nested-reference","unchanged"],"summary":"This document lists the design principles, scope, and requirements\n for the XML Digital Signature specification. It includes requirements\n as they relate to the signature syntax, data model, format,\n cryptographic processing, and external requirements and coordination.","scope_keywords":["2807","algorithm","algorithms","authentication","hash","hashing","identification","key","path","signature","signatures","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null}],"search_text":"IETF RFC 2807 This document lists the design principles, scope, and requirements\n for the XML Digital Signature specification. It includes requirements\n as they relate to the signature syntax, data model, format,\n cryptographic processing, and external requirements and coordination. 2807 algorithm algorithms authentication hash hashing identification key path signature signatures timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5781","type":"specification","body":"IETF","designation":"RFC 5781","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5781.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5781.txt","https://www.rfc-editor.org/rfc/rfc5781.pdf"],"folder":"IETF/RFC-5781","files":{"txt":{"path":"standards/IETF/RFC-5781/RFC-5781.txt","sha256":"6591555ce06d68b3845cc23e53994b9e450b63c39e4351c6fb8f76882da75165"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) S. Weiler\nRequest for Comments: 5781 SPARTA, Inc.\nCategory: Informational D. Ward\nISSN: 2070-1721 Juniper\n R. Housley\n Vigil Security\n February 2010\n\n The rsync URI Scheme\n\nAbstract\n\n This document specifies the rsync Uniform Resource Identifier (URI)\n scheme.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o","scope_keywords":["5781","http","license","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6481","folder":"IETF/RFC-6481","source":"IETF/RFC-6481/RFC-6481.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null},{"body":"IETF","designation":"RFC 6490","folder":"IETF/RFC-6490","source":"IETF/RFC-6490/RFC-6490.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6810","folder":"IETF/RFC-6810","source":"IETF/RFC-6810/RFC-6810.txt","version":null}],"search_text":"IETF RFC 5781 Internet Engineering Task Force (IETF) S. Weiler\nRequest for Comments: 5781 SPARTA, Inc.\nCategory: Informational D. Ward\nISSN: 2070-1721 Juniper\n R. Housley\n Vigil Security\n February 2010\n\n The rsync URI Scheme\n\nAbstract\n\n This document specifies the rsync Uniform Resource Identifier (URI)\n scheme.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback o 5781 http license path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 2398","type":"specification","body":"IETF","designation":"RFC 2398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2398.txt","https://www.rfc-editor.org/rfc/rfc2398.pdf"],"folder":"IETF/RFC-2398","files":{"txt":{"path":"standards/IETF/RFC-2398/RFC-2398.txt","sha256":"19e8eaf3488ff2e057f8153aa3f27671d1f4a1951469b8c024ebd0887fc2313f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Parker\nRequest for Comments: 2398 C. Schmechel\nFYI: 33 Sun Microsystems, Inc.\nCategory: Informational August 1998\n\n Some Testing Tools for TCP Implementors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n Available tools for testing TCP implementations are catalogued by\n this memo. Hopefully disseminating this information will encourage\n those responsible for building and maintaining TCP to make the best\n use of available tests. The type of testing the tool provides, the\n type of tests it is capable of doing, and its availability is\n enumerated. This document lists only tools which can evaluate one or\n more TCP implementations, or whic","scope_keywords":["2398","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2398 Network Working Group S. Parker\nRequest for Comments: 2398 C. Schmechel\nFYI: 33 Sun Microsystems, Inc.\nCategory: Informational August 1998\n\n Some Testing Tools for TCP Implementors\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\n1. Introduction\n\n Available tools for testing TCP implementations are catalogued by\n this memo. Hopefully disseminating this information will encourage\n those responsible for building and maintaining TCP to make the best\n use of available tests. The type of testing the tool provides, the\n type of tests it is capable of doing, and its availability is\n enumerated. This document lists only tools which can evaluate one or\n more TCP implementations, or whic 2398 http nested-reference unchanged"},{"id":"IETF RFC 3554","type":"specification","body":"IETF","designation":"RFC 3554","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3554.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3554.txt","https://www.rfc-editor.org/rfc/rfc3554.pdf"],"folder":"IETF/RFC-3554","files":{"txt":{"path":"standards/IETF/RFC-3554/RFC-3554.txt","sha256":"9cef8bb2d8ff5034ff0eb41dd38dd25098b64b8f18ac6ef81040dd5d95a2e3c2"}},"tags":["nested-reference","unchanged"],"summary":"This document describes functional requirements for IPsec (RFC 2401)\n and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in\n securing SCTP (RFC 2960) traffic.\n\n1. Introduction\n\n The Stream Control Transmission Protocol (SCTP) is a reliable\n transport protocol operating on top of a connection-less packet\n network such as IP. SCTP is designed to transport PSTN signaling\n messages over IP networks, but is capable of broader applications.\n\n When SCTP is used over IP networks, it may utilize the IP security\n protocol suite [RFC2402][RFC2406] for integrity and confidentiality.\n To dynamically establish IPsec Security Associations (SAs), a key\n negotiation protocol such as IKE [RFC2409] may be used.\n\n This document describes functional requirements for IPsec and IKE to\n facilitate their use in securing SCTP traffic. In particular, we\n discuss additional support in the form of a ","scope_keywords":["3554","authentication","identification","key","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 5406","folder":"IETF/RFC-5406","source":"IETF/RFC-5406/RFC-5406.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 3554 This document describes functional requirements for IPsec (RFC 2401)\n and Internet Key Exchange (IKE) (RFC 2409) to facilitate their use in\n securing SCTP (RFC 2960) traffic.\n\n1. Introduction\n\n The Stream Control Transmission Protocol (SCTP) is a reliable\n transport protocol operating on top of a connection-less packet\n network such as IP. SCTP is designed to transport PSTN signaling\n messages over IP networks, but is capable of broader applications.\n\n When SCTP is used over IP networks, it may utilize the IP security\n protocol suite [RFC2402][RFC2406] for integrity and confidentiality.\n To dynamically establish IPsec Security Associations (SAs), a key\n negotiation protocol such as IKE [RFC2409] may be used.\n\n This document describes functional requirements for IPsec and IKE to\n facilitate their use in securing SCTP traffic. In particular, we\n discuss additional support in the form of a  3554 authentication identification key policy nested-reference unchanged"},{"id":"IETF RFC 4176","type":"specification","body":"IETF","designation":"RFC 4176","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4176.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4176.txt","https://www.rfc-editor.org/rfc/rfc4176.pdf"],"folder":"IETF/RFC-4176","files":{"txt":{"path":"standards/IETF/RFC-4176/RFC-4176.txt","sha256":"9cf7492c23bc10a27540b5ec9b64b3b5c506ff6d9e30fa67e884cb9157d0fff5"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for the operation and management\n of Layer 3 Virtual Private Networks (L3VPNs). This framework intends\n to produce a coherent description of the significant technical issues\n that are important in the design of L3VPN management solutions. The\n selection of specific approaches, and making choices among\n information models and protocols are outside the scope of this\n document.\n\nEl Mghazli, et al. Informational [Page 1]\n\f\nRFC 4176 L3VPN Operations and Management Framework October 2005","scope_keywords":["4176","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4834","folder":"IETF/RFC-4834","source":"IETF/RFC-4834/RFC-4834.txt","version":null},{"body":"IETF","designation":"RFC 4847","folder":"IETF/RFC-4847","source":"IETF/RFC-4847/RFC-4847.txt","version":null},{"body":"IETF","designation":"RFC 5565","folder":"IETF/RFC-5565","source":"IETF/RFC-5565/RFC-5565.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 4176 This document provides a framework for the operation and management\n of Layer 3 Virtual Private Networks (L3VPNs). This framework intends\n to produce a coherent description of the significant technical issues\n that are important in the design of L3VPN management solutions. The\n selection of specific approaches, and making choices among\n information models and protocols are outside the scope of this\n document.\n\nEl Mghazli, et al. Informational [Page 1]\n\f\nRFC 4176 L3VPN Operations and Management Framework October 2005 4176 encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 4891","type":"specification","body":"IETF","designation":"RFC 4891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4891.txt","https://www.rfc-editor.org/rfc/rfc4891.pdf"],"folder":"IETF/RFC-4891","files":{"txt":{"path":"standards/IETF/RFC-4891/RFC-4891.txt","sha256":"9db12b8ee91adf7556567d4e115d0fd8620a1856fae5ac282bd4b478b1181aa1"}},"tags":["nested-reference","unchanged"],"summary":"This document gives guidance on securing manually configured IPv6-in-\n IPv4 tunnels using IPsec in transport mode. No additional protocol\n extensions are described beyond those available with the IPsec\n framework.\n\nGraveman, et al. Informational [Page 1]\n\f\nRFC 4891 IPsec with IPv6-in-IPv4 Tunnels May 2007","scope_keywords":["4891","attribute","attributes","authentication","authorization","encryption","key","path","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4925","folder":"IETF/RFC-4925","source":"IETF/RFC-4925/RFC-4925.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5739","folder":"IETF/RFC-5739","source":"IETF/RFC-5739/RFC-5739.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null}],"search_text":"IETF RFC 4891 This document gives guidance on securing manually configured IPv6-in-\n IPv4 tunnels using IPsec in transport mode. No additional protocol\n extensions are described beyond those available with the IPsec\n framework.\n\nGraveman, et al. Informational [Page 1]\n\f\nRFC 4891 IPsec with IPv6-in-IPv4 Tunnels May 2007 4891 attribute attributes authentication authorization encryption key path policy trust nested-reference unchanged"},{"id":"IETF RFC 5045","type":"specification","body":"IETF","designation":"RFC 5045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5045.txt","https://www.rfc-editor.org/rfc/rfc5045.pdf"],"folder":"IETF/RFC-5045","files":{"txt":{"path":"standards/IETF/RFC-5045/RFC-5045.txt","sha256":"d2cc3c2b688733a9480dbe47256a19c12b1f9aa44cab9ccdcaf403ad706ada79"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the applicability of Remote Direct Memory\n Access Protocol (RDMAP) and the Direct Data Placement Protocol (DDP).\n It compares and contrasts the different transport options over IP\n that DDP can use, provides guidance to ULP developers on choosing\n between available transports and/or how to be indifferent to the\n specific transport layer used, compares use of DDP with direct use of\n the supporting transports, and compares DDP over IP transports with\n non-IP transports that support RDMA functionality.\n\nBestler & Coene Informational [Page 1]\n\f\nRFC 5045 RDMA/DDP Applicability October 2007","scope_keywords":["5045"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 5045 This document describes the applicability of Remote Direct Memory\n Access Protocol (RDMAP) and the Direct Data Placement Protocol (DDP).\n It compares and contrasts the different transport options over IP\n that DDP can use, provides guidance to ULP developers on choosing\n between available transports and/or how to be indifferent to the\n specific transport layer used, compares use of DDP with direct use of\n the supporting transports, and compares DDP over IP transports with\n non-IP transports that support RDMA functionality.\n\nBestler & Coene Informational [Page 1]\n\f\nRFC 5045 RDMA/DDP Applicability October 2007 5045 nested-reference unchanged"},{"id":"IETF RFC 3756","type":"specification","body":"IETF","designation":"RFC 3756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3756.txt","https://www.rfc-editor.org/rfc/rfc3756.pdf"],"folder":"IETF/RFC-3756","files":{"txt":{"path":"standards/IETF/RFC-3756/RFC-3756.txt","sha256":"dbb129b3b78179b1fec050cce5f5e047fbb7e1dc192a1f817a40e539a6ca7fc2"}},"tags":["nested-reference","unchanged"],"summary":"The existing IETF standards specify that IPv6 Neighbor Discovery (ND)\n and Address Autoconfiguration mechanisms may be protected with IPsec\n Authentication Header (AH). However, the current specifications\n limit the security solutions to manual keying due to practical\n problems faced with automatic key management. This document\n specifies three different trust models and discusses the threats\n pertinent to IPv6 Neighbor Discovery. The purpose of this discussion\n is to define the requirements for Securing IPv6 Neighbor Discovery.","scope_keywords":["3756","authentication","authorization","key","keys","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3964","folder":"IETF/RFC-3964","source":"IETF/RFC-3964/RFC-3964.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 4057","folder":"IETF/RFC-4057","source":"IETF/RFC-4057/RFC-4057.txt","version":null},{"body":"IETF","designation":"RFC 4081","folder":"IETF/RFC-4081","source":"IETF/RFC-4081/RFC-4081.txt","version":null},{"body":"IETF","designation":"RFC 4135","folder":"IETF/RFC-4135","source":"IETF/RFC-4135/RFC-4135.txt","version":null},{"body":"IETF","designation":"RFC 4191","folder":"IETF/RFC-4191","source":"IETF/RFC-4191/RFC-4191.txt","version":null},{"body":"IETF","designation":"RFC 4214","folder":"IETF/RFC-4214","source":"IETF/RFC-4214/RFC-4214.txt","version":null},{"body":"IETF","designation":"RFC 4389","folder":"IETF/RFC-4389","source":"IETF/RFC-4389/RFC-4389.txt","version":null},{"body":"IETF","designation":"RFC 4429","folder":"IETF/RFC-4429","source":"IETF/RFC-4429/RFC-4429.txt","version":null},{"body":"IETF","designation":"RFC 4832","folder":"IETF/RFC-4832","source":"IETF/RFC-4832/RFC-4832.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4862","folder":"IETF/RFC-4862","source":"IETF/RFC-4862/RFC-4862.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 4943","folder":"IETF/RFC-4943","source":"IETF/RFC-4943/RFC-4943.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5214","folder":"IETF/RFC-5214","source":"IETF/RFC-5214/RFC-5214.txt","version":null},{"body":"IETF","designation":"RFC 5269","folder":"IETF/RFC-5269","source":"IETF/RFC-5269/RFC-5269.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null},{"body":"IETF","designation":"RFC 5909","folder":"IETF/RFC-5909","source":"IETF/RFC-5909/RFC-5909.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6606","folder":"IETF/RFC-6606","source":"IETF/RFC-6606/RFC-6606.txt","version":null},{"body":"IETF","designation":"RFC 6775","folder":"IETF/RFC-6775","source":"IETF/RFC-6775/RFC-6775.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null}],"search_text":"IETF RFC 3756 The existing IETF standards specify that IPv6 Neighbor Discovery (ND)\n and Address Autoconfiguration mechanisms may be protected with IPsec\n Authentication Header (AH). However, the current specifications\n limit the security solutions to manual keying due to practical\n problems faced with automatic key management. This document\n specifies three different trust models and discusses the threats\n pertinent to IPv6 Neighbor Discovery. The purpose of this discussion\n is to define the requirements for Securing IPv6 Neighbor Discovery. 3756 authentication authorization key keys management trust nested-reference unchanged"},{"id":"IETF RFC 3526","type":"specification","body":"IETF","designation":"RFC 3526","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3526.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3526.txt","https://www.rfc-editor.org/rfc/rfc3526.pdf"],"folder":"IETF/RFC-3526","files":{"txt":{"path":"standards/IETF/RFC-3526/RFC-3526.txt","sha256":"6c95b231eb1c2d9ffa480efbe3ae53477231271f3438570a3af370b2aa4a968b"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new Modular Exponential (MODP) Groups for the\n Internet Key Exchange (IKE) protocol. It documents the well known\n and used 1536 bit group 5, and also defines new 2048, 3072, 4096,\n 6144, and 8192 bit Diffie-Hellman groups numbered starting at 14.\n The selection of the primes for theses groups follows the criteria\n established by Richard Schroeppel.","scope_keywords":["3526","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4705","folder":"IETF/RFC-4705","source":"IETF/RFC-4705/RFC-4705.txt","version":null},{"body":"IETF","designation":"RFC 4746","folder":"IETF/RFC-4746","source":"IETF/RFC-4746/RFC-4746.txt","version":null},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6989","folder":"IETF/RFC-6989","source":"IETF/RFC-6989/RFC-6989.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null}],"search_text":"IETF RFC 3526 This document defines new Modular Exponential (MODP) Groups for the\n Internet Key Exchange (IKE) protocol. It documents the well known\n and used 1536 bit group 5, and also defines new 2048, 3072, 4096,\n 6144, and 8192 bit Diffie-Hellman groups numbered starting at 14.\n The selection of the primes for theses groups follows the criteria\n established by Richard Schroeppel. 3526 encryption key keys nested-reference unchanged"},{"id":"IETF RFC 4894","type":"specification","body":"IETF","designation":"RFC 4894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4894.txt","https://www.rfc-editor.org/rfc/rfc4894.pdf"],"folder":"IETF/RFC-4894","files":{"txt":{"path":"standards/IETF/RFC-4894/RFC-4894.txt","sha256":"eea10b2556c64cbd3c81d50ba078bcd9a65bbd260569b8fc6f6fada2ba78ee82"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the IKEv1 (Internet Key Exchange version\n 1), IKEv2, and IPsec protocols use hash functions, and explains the\n level of vulnerability of these protocols to the reduced collision\n resistance of the MD5 and SHA-1 hash algorithms.","scope_keywords":["4894","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","key","keys","pki","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 4894 This document describes how the IKEv1 (Internet Key Exchange version\n 1), IKEv2, and IPsec protocols use hash functions, and explains the\n level of vulnerability of these protocols to the reduced collision\n resistance of the MD5 and SHA-1 hash algorithms. 4894 algorithm algorithms authentication certificate certificates encryption hash key keys pki signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 5879","type":"specification","body":"IETF","designation":"RFC 5879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5879.txt","https://www.rfc-editor.org/rfc/rfc5879.pdf"],"folder":"IETF/RFC-5879","files":{"txt":{"path":"standards/IETF/RFC-5879/RFC-5879.txt","sha256":"f419b6ae5eb24ab0119c4e1b0ad0af0f3d1efd43a050e326c4095b8c8dca2cc7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a set of heuristics for distinguishing IPsec\n ESP-NULL (Encapsulating Security Payload without encryption) packets\n from encrypted ESP packets. These heuristics can be used on\n intermediate devices, like traffic analyzers, and deep-inspection\n engines, to quickly decide whether or not a given packet flow is\n encrypted, i.e., whether or not it can be inspected. Use of these\n heuristics does not require any changes made on existing IPsec hosts\n that are compliant with RFC 4303.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all docume","scope_keywords":["5879","authentication","encryption","http","license","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 5879 This document describes a set of heuristics for distinguishing IPsec\n ESP-NULL (Encapsulating Security Payload without encryption) packets\n from encrypted ESP packets. These heuristics can be used on\n intermediate devices, like traffic analyzers, and deep-inspection\n engines, to quickly decide whether or not a given packet flow is\n encrypted, i.e., whether or not it can be inspected. Use of these\n heuristics does not require any changes made on existing IPsec hosts\n that are compliant with RFC 4303.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all docume 5879 authentication encryption http license path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5013","type":"specification","body":"IETF","designation":"RFC 5013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5013.txt","https://www.rfc-editor.org/rfc/rfc5013.pdf"],"folder":"IETF/RFC-5013","files":{"txt":{"path":"standards/IETF/RFC-5013/RFC-5013.txt","sha256":"1cf981dd8f748b1052cdd53dd00092a048f7ea7ac69c5fe6150c9e1137215a65"}},"tags":["nested-reference","unchanged"],"summary":"The Dublin Core Metadata Element Set is a standard for cross-domain\n resource description. As in RFC 3986 [RFC3986], \"Uniform Resource\n Identifier (URI): Generic Syntax\", this specification does not limit\n the scope of what might be a resource.","scope_keywords":["5013","key","policies","policy","presentation","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null}],"search_text":"IETF RFC 5013 The Dublin Core Metadata Element Set is a standard for cross-domain\n resource description. As in RFC 3986 [RFC3986], \"Uniform Resource\n Identifier (URI): Generic Syntax\", this specification does not limit\n the scope of what might be a resource. 5013 key policies policy presentation profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 2416","type":"specification","body":"IETF","designation":"RFC 2416","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2416.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2416.txt","https://www.rfc-editor.org/rfc/rfc2416.pdf"],"folder":"IETF/RFC-2416","files":{"txt":{"path":"standards/IETF/RFC-2416/RFC-2416.txt","sha256":"7847a106249416affc0aa6ba2b7e3222c73cdb1e2c8acdc4b0c3d72624e2facb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Shepard\nRequest for Comments: 2416 C. Partridge\nCategory: Informational BBN Technologies\n September 1998\n\n When TCP Starts Up With Four Packets Into Only Three Buffers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This memo is to document a simple experiment. The experiment showed\n that in the case of a TCP receiver behind a 9600 bps modem link at\n the edge of a fast Internet where there are only 3 buffers before the\n modem (and the fourth packet of a four-packet start will surely be\n dropped), no significant degradation in performance is experienced by\n a TCP sending with a four-packet start when compared with a normal\n slow start (which ","scope_keywords":["2416","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 3150","folder":"IETF/RFC-3150","source":"IETF/RFC-3150/RFC-3150.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2416 Network Working Group T. Shepard\nRequest for Comments: 2416 C. Partridge\nCategory: Informational BBN Technologies\n September 1998\n\n When TCP Starts Up With Four Packets Into Only Three Buffers\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n This memo is to document a simple experiment. The experiment showed\n that in the case of a TCP receiver behind a 9600 bps modem link at\n the edge of a fast Internet where there are only 3 buffers before the\n modem (and the fourth packet of a four-packet start will surely be\n dropped), no significant degradation in performance is experienced by\n a TCP sending with a four-packet start when compared with a normal\n slow start (which  2416 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 2415","type":"specification","body":"IETF","designation":"RFC 2415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2415.txt","https://www.rfc-editor.org/rfc/rfc2415.pdf"],"folder":"IETF/RFC-2415","files":{"txt":{"path":"standards/IETF/RFC-2415/RFC-2415.txt","sha256":"2d922270d6559e20fd1503e23b3ef9c761205611b0687aecedc6e43f094e6d82"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Poduri\nRequest for Comments: 2415 K. Nichols\nCategory: Informational Bay Networks\n September 1998\n\n Simulation Studies of Increased Initial TCP Window Size\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n An increase in the permissible initial window size of a TCP\n connection, from one segment to three or four segments, has been\n under discussion in the tcp-impl working group. This document covers\n some simulation studies of the effects of increasing the initial\n window size of TCP. Both long-lived TCP connections (file transfers)\n and short-lived web-browsing style connections were modeled. The\n simulations were performed using the publicly ","scope_keywords":["2415","http","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2598","folder":"IETF/RFC-2598","source":"IETF/RFC-2598/RFC-2598.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 2415 Network Working Group K. Poduri\nRequest for Comments: 2415 K. Nichols\nCategory: Informational Bay Networks\n September 1998\n\n Simulation Studies of Increased Initial TCP Window Size\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nAbstract\n\n An increase in the permissible initial window size of a TCP\n connection, from one segment to three or four segments, has been\n under discussion in the tcp-impl working group. This document covers\n some simulation studies of the effects of increasing the initial\n window size of TCP. Both long-lived TCP connections (file transfers)\n and short-lived web-browsing style connections were modeled. The\n simulations were performed using the publicly  2415 http path nested-reference unchanged"},{"id":"IETF RFC 2417","type":"specification","body":"IETF","designation":"RFC 2417","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2417.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2417.txt","https://www.rfc-editor.org/rfc/rfc2417.pdf"],"folder":"IETF/RFC-2417","files":{"txt":{"path":"standards/IETF/RFC-2417/RFC-2417.txt","sha256":"9c22b8045b4c47a89a345a5ade624f5f21629057d8cf2b7788c894d6085405ee"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for IP hosts and routers\n that use a Multicast Address Resolution Server (MARS) to support IP\n multicast over ATM, as described in 'Support for Multicast over UNI\n 3.0/3.1 based ATM Networks' [1].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.\n\nChung & Greene Standards Track [Page 1]\n\f\nRFC 2417 Multicast MIB September 1998","scope_keywords":["2417","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2417 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for IP hosts and routers\n that use a Multicast Address Resolution Server (MARS) to support IP\n multicast over ATM, as described in 'Support for Multicast over UNI\n 3.0/3.1 based ATM Networks' [1].\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SNMPv2 SMI, and semantically identical to the peer SNMPv1\n definitions.\n\nChung & Greene Standards Track [Page 1]\n\f\nRFC 2417 Multicast MIB September 1998 2417 management registered nested-reference unchanged"},{"id":"IETF RFC 4693","type":"specification","body":"IETF","designation":"RFC 4693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4693.txt","https://www.rfc-editor.org/rfc/rfc4693.pdf"],"folder":"IETF/RFC-4693","files":{"txt":{"path":"standards/IETF/RFC-4693/RFC-4693.txt","sha256":"36b11954f98f0c7881f28a7e53a035e4f7409547ce1a03e8b3d30418bbbb79ed"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a new document series intended for use as a\n repository for IETF operations documents, which should be more\n ephemeral than RFCs, but more referenceable than Internet-Drafts, and\n with more clear handling procedures than a random Web page.\n\n It proposes to establish this series as an RFC 3933 process\n experiment.","scope_keywords":["4693","attribute","attributes","http","identification","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null}],"search_text":"IETF RFC 4693 This document describes a new document series intended for use as a\n repository for IETF operations documents, which should be more\n ephemeral than RFCs, but more referenceable than Internet-Drafts, and\n with more clear handling procedures than a random Web page.\n\n It proposes to establish this series as an RFC 3933 process\n experiment. 4693 attribute attributes http identification management policy nested-reference unchanged"},{"id":"IETF RFC 4770","type":"specification","body":"IETF","designation":"RFC 4770","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4770.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4770.txt","https://www.rfc-editor.org/rfc/rfc4770.pdf"],"folder":"IETF/RFC-4770","files":{"txt":{"path":"standards/IETF/RFC-4770/RFC-4770.txt","sha256":"26dff34c73f02ffe647b4bbb2210a7f9e3f798b2c16f028da3405cb39d5cc8fc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to vCard to support Instant\n Messaging (IM) and Presence Protocol (PP) applications. IM and PP\n are becoming increasingly common ways of communicating, and users\n want to save this contact information in their address books. It\n allows a URI that is associated with IM or PP to be specified inside\n a vCard.","scope_keywords":["4770","http","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null}],"search_text":"IETF RFC 4770 This document describes an extension to vCard to support Instant\n Messaging (IM) and Presence Protocol (PP) applications. IM and PP\n are becoming increasingly common ways of communicating, and users\n want to save this contact information in their address books. It\n allows a URI that is associated with IM or PP to be specified inside\n a vCard. 4770 http profile subject trust nested-reference unchanged"},{"id":"IETF RFC 243","type":"specification","body":"IETF","designation":"RFC 243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc243.txt","https://www.rfc-editor.org/rfc/rfc243.pdf"],"folder":"IETF/RFC-243","files":{"txt":{"path":"standards/IETF/RFC-243/RFC-243.txt","sha256":"932069a51a2513c078d3670016e45c7e417a8edf58dee05c0870ca6a6a2fbbfd"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 243 Alvin P. Mullery\nCategory: T Thomas J. Watson Research Center\nNIC: 7673 Yorktown Heights, N.Y.\n October 5, 1971\n\n NETWORK AND DATA SHARING BIBLIOGRAPHY\n\n GENERAL DATA STRUCTURES\n\n F. D. Anzelno, \"A Data-Storage Format for Information System Files,\"\n IEEE Trans. Computers, vol. c-20, pp. 39-43, January 1971.\n\n E. F. Codd, \"A Relational Model of Data for Large Shared Data Banks,\"\n Comm. ACM, vol 13, pp. 377-387, June 1970.\n\n C. T. Davies, \"A Logical Concept for the Control and Management of\n Data\", AR-0803-00.\n\n S. E. Madnick and J. W. Alsop II, \"A Modular Approach to File System\n Design,\" 1969 Spring Joint Computer Conf., AFIPS Proc., vol 34, pp.\n 1-13, 1969.\n\n W. C. McGee, \"File Structures for Generalized Data Management,\" Proc.\n IFIPS Congress 68, pp. 1233, 1968.\n\n P. D. Rovner and J. A. Feldman, \"The IEAP Language and Data\n Structure,\" Proc IFIPS Congress 68, ","scope_keywords":["243","management","pid","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 290","folder":"IETF/RFC-290","source":"IETF/RFC-290/RFC-290.txt","version":null}],"search_text":"IETF RFC 243 Request for Comments: 243 Alvin P. Mullery\nCategory: T Thomas J. Watson Research Center\nNIC: 7673 Yorktown Heights, N.Y.\n October 5, 1971\n\n NETWORK AND DATA SHARING BIBLIOGRAPHY\n\n GENERAL DATA STRUCTURES\n\n F. D. Anzelno, \"A Data-Storage Format for Information System Files,\"\n IEEE Trans. Computers, vol. c-20, pp. 39-43, January 1971.\n\n E. F. Codd, \"A Relational Model of Data for Large Shared Data Banks,\"\n Comm. ACM, vol 13, pp. 377-387, June 1970.\n\n C. T. Davies, \"A Logical Concept for the Control and Management of\n Data\", AR-0803-00.\n\n S. E. Madnick and J. W. Alsop II, \"A Modular Approach to File System\n Design,\" 1969 Spring Joint Computer Conf., AFIPS Proc., vol 34, pp.\n 1-13, 1969.\n\n W. C. McGee, \"File Structures for Generalized Data Management,\" Proc.\n IFIPS Congress 68, pp. 1233, 1968.\n\n P. D. Rovner and J. A. Feldman, \"The IEAP Language and Data\n Structure,\" Proc IFIPS Congress 68,  243 management pid presentation nested-reference unchanged"},{"id":"IETF RFC 290","type":"specification","body":"IETF","designation":"RFC 290","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc290.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc290.txt","https://www.rfc-editor.org/rfc/rfc290.pdf"],"folder":"IETF/RFC-290","files":{"txt":{"path":"standards/IETF/RFC-290/RFC-290.txt","sha256":"f74d7399b002c732c9deb8354a8d8ae4e27ec97c50ad6bbf8849db4ba0a6040e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Alvin P. Mullery\nRequest for Comments: 290 Thomas J. Watson Research Center\nUpdates: RFC 243 January 11, 1972\nNIC: 8300\n\n COMPUTER NETWORKS AND DATE SHARING: A BIBLIOGRAPHY\n\n Abstract. The bibliography is broken into seven subject areas -\n general data structures, data description, data conversion, data\n management, data security, data transmission, and computer network\n design. Two of these areas, general data structures and data\n management, cover a very broad range of subjects: however, in these\n two areas, only entries that seem to be specially pertinent to\n computer networks and data sharing are included. The bibliography\n also contains an index of authors.\n\n A. GENERAL DATA STRUCTURES\n\n 1. F.D. Anzelmo, \"A Data-Storage Format for Information System\n Files,\" IEEE Trans. Computers, vol. C-20, p. 39-43, January 1971.\n\n 2. E. F. Codd, \"A Relational Model of Data f","scope_keywords":["290","management","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 290 Network Working Group Alvin P. Mullery\nRequest for Comments: 290 Thomas J. Watson Research Center\nUpdates: RFC 243 January 11, 1972\nNIC: 8300\n\n COMPUTER NETWORKS AND DATE SHARING: A BIBLIOGRAPHY\n\n Abstract. The bibliography is broken into seven subject areas -\n general data structures, data description, data conversion, data\n management, data security, data transmission, and computer network\n design. Two of these areas, general data structures and data\n management, cover a very broad range of subjects: however, in these\n two areas, only entries that seem to be specially pertinent to\n computer networks and data sharing are included. The bibliography\n also contains an index of authors.\n\n A. GENERAL DATA STRUCTURES\n\n 1. F.D. Anzelmo, \"A Data-Storage Format for Information System\n Files,\" IEEE Trans. Computers, vol. C-20, p. 39-43, January 1971.\n\n 2. E. F. Codd, \"A Relational Model of Data f 290 management presentation subject nested-reference unchanged"},{"id":"IETF RFC 2946","type":"specification","body":"IETF","designation":"RFC 2946","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2946.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2946.txt","https://www.rfc-editor.org/rfc/rfc2946.pdf"],"folder":"IETF/RFC-2946","files":{"txt":{"path":"standards/IETF/RFC-2946/RFC-2946.txt","sha256":"163e59a62bdd3eaa390b1500085582863dee4d9a0eaed508f9c55fe53109b822"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Ts'o\nRequest for Comments: 2946 VA Linux Systems\nCategory: Standards Track September 2000\n\n Telnet Data Encryption Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a the telnet encryption option as a generic\n method of providing data confidentiality services for the telnet data\n stream. While this document summarizes currently utilized encryption\n types and codes, it does not define a specific encryption algorithm.\n Separate docum","scope_keywords":["2946","algorithm","authentication","encryption","key","keys","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2941","folder":"IETF/RFC-2941","source":"IETF/RFC-2941/RFC-2941.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2946 Network Working Group T. Ts'o\nRequest for Comments: 2946 VA Linux Systems\nCategory: Standards Track September 2000\n\n Telnet Data Encryption Option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes a the telnet encryption option as a generic\n method of providing data confidentiality services for the telnet data\n stream. While this document summarizes currently utilized encryption\n types and codes, it does not define a specific encryption algorithm.\n Separate docum 2946 algorithm authentication encryption key keys policy nested-reference unchanged"},{"id":"IETF RFC 3086","type":"specification","body":"IETF","designation":"RFC 3086","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3086.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3086.txt","https://www.rfc-editor.org/rfc/rfc3086.pdf"],"folder":"IETF/RFC-3086","files":{"txt":{"path":"standards/IETF/RFC-3086/RFC-3086.txt","sha256":"feddcc8ae9ea828371ed40062ee8b9a85eea02e7d76d110772cec39691e22154"}},"tags":["nested-reference","unchanged"],"summary":"The differentiated services framework enables quality-of-service\n provisioning within a network domain by applying rules at the edges\n to create traffic aggregates and coupling each of these with a\n specific forwarding path treatment in the domain through use of a\n codepoint in the IP header. The diffserv WG has defined the general\n architecture for differentiated services and has focused on the\n forwarding path behavior required in routers, known as \"per-hop\n forwarding behaviors\" (or PHBs). The WG has also discussed\n functionality required at diffserv (DS) domain edges to select\n (classifiers) and condition (e.g., policing and shaping) traffic\n according to the rules. Short-term changes in the QoS goals for a DS\n domain are implemented by changing only the configuration of these\n edge behaviors without necessarily reconfiguring the behavior of\n interior network nodes.\n\n The next step i","scope_keywords":["3086","attribute","attributes","path","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3246","folder":"IETF/RFC-3246","source":"IETF/RFC-3246/RFC-3246.txt","version":null},{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3564","folder":"IETF/RFC-3564","source":"IETF/RFC-3564/RFC-3564.txt","version":null},{"body":"IETF","designation":"RFC 3662","folder":"IETF/RFC-3662","source":"IETF/RFC-3662/RFC-3662.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5127","folder":"IETF/RFC-5127","source":"IETF/RFC-5127/RFC-5127.txt","version":null},{"body":"IETF","designation":"RFC 6661","folder":"IETF/RFC-6661","source":"IETF/RFC-6661/RFC-6661.txt","version":null},{"body":"IETF","designation":"RFC 6662","folder":"IETF/RFC-6662","source":"IETF/RFC-6662/RFC-6662.txt","version":null}],"search_text":"IETF RFC 3086 The differentiated services framework enables quality-of-service\n provisioning within a network domain by applying rules at the edges\n to create traffic aggregates and coupling each of these with a\n specific forwarding path treatment in the domain through use of a\n codepoint in the IP header. The diffserv WG has defined the general\n architecture for differentiated services and has focused on the\n forwarding path behavior required in routers, known as \"per-hop\n forwarding behaviors\" (or PHBs). The WG has also discussed\n functionality required at diffserv (DS) domain edges to select\n (classifiers) and condition (e.g., policing and shaping) traffic\n according to the rules. Short-term changes in the QoS goals for a DS\n domain are implemented by changing only the configuration of these\n edge behaviors without necessarily reconfiguring the behavior of\n interior network nodes.\n\n The next step i 3086 attribute attributes path policy nested-reference unchanged"},{"id":"IETF RFC 3692","type":"specification","body":"IETF","designation":"RFC 3692","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3692.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3692.txt","https://www.rfc-editor.org/rfc/rfc3692.pdf"],"folder":"IETF/RFC-3692","files":{"txt":{"path":"standards/IETF/RFC-3692/RFC-3692.txt","sha256":"86c13296fa803f320702fa238c0332aee31c4faa795128621d5fcbd2081eb518"}},"tags":["nested-reference","unchanged"],"summary":"When experimenting with or extending protocols, it is often necessary\n to use some sort of protocol number or constant in order to actually\n test or experiment with the new function, even when testing in a\n closed environment. For example, to test a new DHCP option, one\n needs an option number to identify the new function. This document\n recommends that when writing IANA Considerations sections, authors\n should consider assigning a small range of numbers for\n experimentation purposes that implementers can use when testing\n protocol extensions or other new features. This document reserves\n some ranges of numbers for experimentation purposes in specific\n protocols where the need to support experimentation has been\n identified.","scope_keywords":["3692"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4342","folder":"IETF/RFC-4342","source":"IETF/RFC-4342/RFC-4342.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4581","folder":"IETF/RFC-4581","source":"IETF/RFC-4581/RFC-4581.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4915","folder":"IETF/RFC-4915","source":"IETF/RFC-4915/RFC-4915.txt","version":null},{"body":"IETF","designation":"RFC 4940","folder":"IETF/RFC-4940","source":"IETF/RFC-4940/RFC-4940.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5622","folder":"IETF/RFC-5622","source":"IETF/RFC-5622/RFC-5622.txt","version":null},{"body":"IETF","designation":"RFC 5690","folder":"IETF/RFC-5690","source":"IETF/RFC-5690/RFC-5690.txt","version":null},{"body":"IETF","designation":"RFC 5719","folder":"IETF/RFC-5719","source":"IETF/RFC-5719/RFC-5719.txt","version":null},{"body":"IETF","designation":"RFC 5872","folder":"IETF/RFC-5872","source":"IETF/RFC-5872/RFC-5872.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5978","folder":"IETF/RFC-5978","source":"IETF/RFC-5978/RFC-5978.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6424","folder":"IETF/RFC-6424","source":"IETF/RFC-6424/RFC-6424.txt","version":null},{"body":"IETF","designation":"RFC 6495","folder":"IETF/RFC-6495","source":"IETF/RFC-6495/RFC-6495.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7045","folder":"IETF/RFC-7045","source":"IETF/RFC-7045/RFC-7045.txt","version":null},{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null}],"search_text":"IETF RFC 3692 When experimenting with or extending protocols, it is often necessary\n to use some sort of protocol number or constant in order to actually\n test or experiment with the new function, even when testing in a\n closed environment. For example, to test a new DHCP option, one\n needs an option number to identify the new function. This document\n recommends that when writing IANA Considerations sections, authors\n should consider assigning a small range of numbers for\n experimentation purposes that implementers can use when testing\n protocol extensions or other new features. This document reserves\n some ranges of numbers for experimentation purposes in specific\n protocols where the need to support experimentation has been\n identified. 3692 nested-reference unchanged"},{"id":"IETF RFC 4020","type":"specification","body":"IETF","designation":"RFC 4020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4020.txt","https://www.rfc-editor.org/rfc/rfc4020.pdf"],"folder":"IETF/RFC-4020","files":{"txt":{"path":"standards/IETF/RFC-4020/RFC-4020.txt","sha256":"33a1c39e79863a4cbdf05fc546b1d47d548abc0502bd6e83b83a9e1b00f30955"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses earlier allocation of code points by IANA as a\n remedy to the problem created by the \"Standards Action\" IANA policy\n for protocols for which, by the IETF process, implementation and\n deployment experience is desired or required prior to publication.\n\n1. Introduction\n\n In Standards Track RFCs, there is often a need to allocate code\n points for various objects, messages, or other protocol entities so\n that implementations can interoperate. Many of these code point\n spaces have registries handled by the Internet Assigned Number\n Authority (IANA). Several IANA allocation policies are described in\n RFC 2434 [2434]. Some of them, such as First Come First Served or\n Expert Review, do not require a formal IETF action before the IANA\n performs allocation. However, in situations where code points are a\n scarce resource and/or the IETF community is willing to retain tight\n contr","scope_keywords":["4020","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4360","folder":"IETF/RFC-4360","source":"IETF/RFC-4360/RFC-4360.txt","version":null},{"body":"IETF","designation":"RFC 4760","folder":"IETF/RFC-4760","source":"IETF/RFC-4760/RFC-4760.txt","version":null},{"body":"IETF","designation":"RFC 4858","folder":"IETF/RFC-4858","source":"IETF/RFC-4858/RFC-4858.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5395","folder":"IETF/RFC-5395","source":"IETF/RFC-5395/RFC-5395.txt","version":null},{"body":"IETF","designation":"RFC 6195","folder":"IETF/RFC-6195","source":"IETF/RFC-6195/RFC-6195.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6677","folder":"IETF/RFC-6677","source":"IETF/RFC-6677/RFC-6677.txt","version":null},{"body":"IETF","designation":"RFC 6895","folder":"IETF/RFC-6895","source":"IETF/RFC-6895/RFC-6895.txt","version":null},{"body":"IETF","designation":"RFC 7120","folder":"IETF/RFC-7120","source":"IETF/RFC-7120/RFC-7120.txt","version":null}],"search_text":"IETF RFC 4020 This memo discusses earlier allocation of code points by IANA as a\n remedy to the problem created by the \"Standards Action\" IANA policy\n for protocols for which, by the IETF process, implementation and\n deployment experience is desired or required prior to publication.\n\n1. Introduction\n\n In Standards Track RFCs, there is often a need to allocate code\n points for various objects, messages, or other protocol entities so\n that implementations can interoperate. Many of these code point\n spaces have registries handled by the Internet Assigned Number\n Authority (IANA). Several IANA allocation policies are described in\n RFC 2434 [2434]. Some of them, such as First Come First Served or\n Expert Review, do not require a formal IETF action before the IANA\n performs allocation. However, in situations where code points are a\n scarce resource and/or the IETF community is willing to retain tight\n contr 4020 policies policy nested-reference unchanged"},{"id":"IETF RFC 4148","type":"specification","body":"IETF","designation":"RFC 4148","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4148.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4148.txt","https://www.rfc-editor.org/rfc/rfc4148.pdf"],"folder":"IETF/RFC-4148","files":{"txt":{"path":"standards/IETF/RFC-4148/RFC-4148.txt","sha256":"761017360bee74e0f7c74ad5b63295985a9d1bb428ff78cb99f52549adeba606"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a registry for IP Performance Metrics (IPPM). It\n assigns and registers an initial set of OBJECT IDENTITIES to\n currently defined metrics in the IETF.\n\n This memo also defines the rules for adding IP Performance Metrics\n that are defined in the future and for encouraging all IP performance\n metrics to be registered here.\n\n IANA has been assigned to administer this new registry.","scope_keywords":["4148","management","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5472","folder":"IETF/RFC-5472","source":"IETF/RFC-5472/RFC-5472.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5644","folder":"IETF/RFC-5644","source":"IETF/RFC-5644/RFC-5644.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6248","folder":"IETF/RFC-6248","source":"IETF/RFC-6248/RFC-6248.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4148 This memo defines a registry for IP Performance Metrics (IPPM). It\n assigns and registers an initial set of OBJECT IDENTITIES to\n currently defined metrics in the IETF.\n\n This memo also defines the rules for adding IP Performance Metrics\n that are defined in the future and for encouraging all IP performance\n metrics to be registered here.\n\n IANA has been assigned to administer this new registry. 4148 management registered nested-reference unchanged"},{"id":"IETF RFC 4581","type":"specification","body":"IETF","designation":"RFC 4581","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4581.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4581.txt","https://www.rfc-editor.org/rfc/rfc4581.pdf"],"folder":"IETF/RFC-4581","files":{"txt":{"path":"standards/IETF/RFC-4581/RFC-4581.txt","sha256":"0ec328903854dd5000e13b59dc00ee88f46a52d30fbf2de82ceaffb3cd92fd71"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Type-Length-Value format for\n Cryptographically Generated Address (CGA) Extensions. This document\n updates RFC 3972.","scope_keywords":["4581","http","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null}],"search_text":"IETF RFC 4581 This document defines a Type-Length-Value format for\n Cryptographically Generated Address (CGA) Extensions. This document\n updates RFC 3972. 4581 http license subject nested-reference unchanged"},{"id":"IETF RFC 4773","type":"specification","body":"IETF","designation":"RFC 4773","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4773.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4773.txt","https://www.rfc-editor.org/rfc/rfc4773.pdf"],"folder":"IETF/RFC-4773","files":{"txt":{"path":"standards/IETF/RFC-4773/RFC-4773.txt","sha256":"651fb2284dfaf9c90a0a91a79fe6b60f417bf4b89b9ad50f49b6deaa0ef73dd6"}},"tags":["nested-reference","unchanged"],"summary":"address block designated according to this direction.","scope_keywords":["4773","certificate","management","policies","policy","signature","signatures","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5736","folder":"IETF/RFC-5736","source":"IETF/RFC-5736/RFC-5736.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null}],"search_text":"IETF RFC 4773 address block designated according to this direction. 4773 certificate management policies policy signature signatures subject trust validation nested-reference unchanged"},{"id":"IETF RFC 4848","type":"specification","body":"IETF","designation":"RFC 4848","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4848.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4848.txt","https://www.rfc-editor.org/rfc/rfc4848.pdf"],"folder":"IETF/RFC-4848","files":{"txt":{"path":"standards/IETF/RFC-4848/RFC-4848.txt","sha256":"c4d4e152307f493d654e8085223e91cfcd12458f5605c4b53c576757df9bd9cc"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to define a new, straightforward\n Dynamic Delegation Discovery Service (DDDS) application to allow\n mapping of domain names to URIs for particular application services\n and protocols. Although defined as a new DDDS application, dubbed\n U-NAPTR, this is effectively an extension of the Straightforward\n NAPTR (S-NAPTR) DDDS Application.\n\nDaigle Standards Track [Page 1]\n\f\nRFC 4848 URI-Enabled NAPTR April 2007","scope_keywords":["4848","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5222","folder":"IETF/RFC-5222","source":"IETF/RFC-5222/RFC-5222.txt","version":null},{"body":"IETF","designation":"RFC 5223","folder":"IETF/RFC-5223","source":"IETF/RFC-5223/RFC-5223.txt","version":null},{"body":"IETF","designation":"RFC 5986","folder":"IETF/RFC-5986","source":"IETF/RFC-5986/RFC-5986.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null}],"search_text":"IETF RFC 4848 The purpose of this document is to define a new, straightforward\n Dynamic Delegation Discovery Service (DDDS) application to allow\n mapping of domain names to URIs for particular application services\n and protocols. Although defined as a new DDDS application, dubbed\n U-NAPTR, this is effectively an extension of the Straightforward\n NAPTR (S-NAPTR) DDDS Application.\n\nDaigle Standards Track [Page 1]\n\f\nRFC 4848 URI-Enabled NAPTR April 2007 4848 qualified trust nested-reference unchanged"},{"id":"IETF RFC 5224","type":"specification","body":"IETF","designation":"RFC 5224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5224.txt","https://www.rfc-editor.org/rfc/rfc5224.pdf"],"folder":"IETF/RFC-5224","files":{"txt":{"path":"standards/IETF/RFC-5224/RFC-5224.txt","sha256":"8578bbf053b4b86234ee3e2bdbcf579e1ec925710db9ed4a7850bd7b24dc8067"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the need for a new IANA Diameter Command Code\n to be used in a vendor-specific new application for invocation of\n Policy Processing (Policy Evaluation, or Evaluation and Enforcement).\n This application is needed as one of the implementations of the Open\n Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management\n (PEEM) enabler, namely for the PEM-1 interface used to send a\n request/response for Policy Processing.","scope_keywords":["5224","authentication","authorization","http","management","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5431","folder":"IETF/RFC-5431","source":"IETF/RFC-5431/RFC-5431.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5224 This document describes the need for a new IANA Diameter Command Code\n to be used in a vendor-specific new application for invocation of\n Policy Processing (Policy Evaluation, or Evaluation and Enforcement).\n This application is needed as one of the implementations of the Open\n Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management\n (PEEM) enabler, namely for the PEM-1 interface used to send a\n request/response for Policy Processing. 5224 authentication authorization http management policy registered nested-reference unchanged"},{"id":"IETF RFC 2441","type":"specification","body":"IETF","designation":"RFC 2441","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2441.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2441.txt","https://www.rfc-editor.org/rfc/rfc2441.pdf"],"folder":"IETF/RFC-2441","files":{"txt":{"path":"standards/IETF/RFC-2441/RFC-2441.txt","sha256":"0753a2edae8b6f595f83f29e0abe26b36d6ecb736a7aec24d8174cab44bcb494"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Cohen\nRequest for Comments: 2441 Myricom\nCategory: Informational November 1998\n\n Working with Jon\n Tribute delivered at UCLA, October 30, 1998\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTribute\n\n In 1973, after doing interactive flight simulation over the ARPAnet,\n I joined ISI and applied that experience to interactive speech over\n the ARPAnet.\n\n The communication requirements for realtime speech were unique (more\n like UDP than like TCP). This got me involved in the Network Working\n Group, and I started another project at ISI called \"Internet\n Concepts\".\n\n In 1977 Steve Crocker, who was then at ISI, told me that Jon was\n willing to join us, and ","scope_keywords":["2441","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null}],"search_text":"IETF RFC 2441 Network Working Group D. Cohen\nRequest for Comments: 2441 Myricom\nCategory: Informational November 1998\n\n Working with Jon\n Tribute delivered at UCLA, October 30, 1998\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nTribute\n\n In 1973, after doing interactive flight simulation over the ARPAnet,\n I joined ISI and applied that experience to interactive speech over\n the ARPAnet.\n\n The communication requirements for realtime speech were unique (more\n like UDP than like TCP). This got me involved in the Network Working\n Group, and I started another project at ISI called \"Internet\n Concepts\".\n\n In 1977 Steve Crocker, who was then at ISI, told me that Jon was\n willing to join us, and  2441 management subject nested-reference unchanged"},{"id":"IETF RFC 2443","type":"specification","body":"IETF","designation":"RFC 2443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2443.txt","https://www.rfc-editor.org/rfc/rfc2443.pdf"],"folder":"IETF/RFC-2443","files":{"txt":{"path":"standards/IETF/RFC-2443/RFC-2443.txt","sha256":"be0d3a6fc6c956ec1035faf122324b31cf4289203cb1bc2999d2d6d8a77cb157"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for distributing a MARS service\n within a LIS[1]. This method uses the Server Cache Synchronization\n Protocol (SCSP)[2] to synchronize the MARS Server databases within a\n LIS. When SCSP is used to synchronize the caches of MARS Servers in\n a LIS, the LIS defines the boundary of an SCSP Server Group (SG).\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [5].\n\n The MARS is an extended analog of the ATMARP Server introduced in\n [4]. It provides the necessary connection and addressing services\n required by layer 3 multicast services over ATM. There are three\n basic elements to the MARS model. First, the MARS Server which\n manages and distributes layer 3 group membership information to the\n LIS. Second, MARS ","scope_keywords":["2443","key","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2443 This document describes a method for distributing a MARS service\n within a LIS[1]. This method uses the Server Cache Synchronization\n Protocol (SCSP)[2] to synchronize the MARS Server databases within a\n LIS. When SCSP is used to synchronize the caches of MARS Servers in\n a LIS, the LIS defines the boundary of an SCSP Server Group (SG).\n\n1. Introduction\n\n The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,\n SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this\n document, are to be interpreted as described in [5].\n\n The MARS is an extended analog of the ATMARP Server introduced in\n [4]. It provides the necessary connection and addressing services\n required by layer 3 multicast services over ATM. There are three\n basic elements to the MARS model. First, the MARS Server which\n manages and distributes layer 3 group membership information to the\n LIS. Second, MARS  2443 key pid nested-reference unchanged"},{"id":"IETF RFC 4011","type":"specification","body":"IETF","designation":"RFC 4011","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4011.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4011.txt","https://www.rfc-editor.org/rfc/rfc4011.pdf"],"folder":"IETF/RFC-4011","files":{"txt":{"path":"standards/IETF/RFC-4011/RFC-4011.txt","sha256":"8bb696ba955fd339bd520041c47e312144027a156cca41fac2a39980af6a2023"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, this MIB defines objects that enable policy-based\n monitoring and management of Simple Network Management Protocol\n (SNMP) infrastructures, a scripting language, and a script execution\n environment.","scope_keywords":["4011","management","policy","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null}],"search_text":"IETF RFC 4011 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP-based internets.\n In particular, this MIB defines objects that enable policy-based\n monitoring and management of Simple Network Management Protocol\n (SNMP) infrastructures, a scripting language, and a script execution\n environment. 4011 management policy profile nested-reference unchanged"},{"id":"IETF RFC 2455","type":"specification","body":"IETF","designation":"RFC 2455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2455.txt","https://www.rfc-editor.org/rfc/rfc2455.pdf"],"folder":"IETF/RFC-2455","files":{"txt":{"path":"standards/IETF/RFC-2455/RFC-2455.txt","sha256":"8fdb151cb5640766663a6ae54e7c08817fa73f1f72c1814857bfe8019027d8ca"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling\n network devices with APPN (Advanced Peer-to-Peer Networking)\n capabilities. This memo identifies managed objects for the APPN\n protocol.","scope_keywords":["2455","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2455 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling\n network devices with APPN (Advanced Peer-to-Peer Networking)\n capabilities. This memo identifies managed objects for the APPN\n protocol. 2455 key management nested-reference unchanged"},{"id":"IETF RFC 2456","type":"specification","body":"IETF","designation":"RFC 2456","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2456.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2456.txt","https://www.rfc-editor.org/rfc/rfc2456.pdf"],"folder":"IETF/RFC-2456","files":{"txt":{"path":"standards/IETF/RFC-2456/RFC-2456.txt","sha256":"959cee420e12a18e5004e53b4dca19f88d633119408b19946ccc1c67da903565"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for receiving notifications from\n network devices with APPN (Advanced Peer-to-Peer Network) and DLUR\n (Dependent LU Requester) capabilities. This memo identifies\n notifications for the APPN and DLUR architecture.","scope_keywords":["2456","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2456 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for receiving notifications from\n network devices with APPN (Advanced Peer-to-Peer Network) and DLUR\n (Dependent LU Requester) capabilities. This memo identifies\n notifications for the APPN and DLUR architecture. 2456 key management nested-reference unchanged"},{"id":"IETF RFC 2457","type":"specification","body":"IETF","designation":"RFC 2457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2457.txt","https://www.rfc-editor.org/rfc/rfc2457.pdf"],"folder":"IETF/RFC-2457","files":{"txt":{"path":"standards/IETF/RFC-2457/RFC-2457.txt","sha256":"cb06cb9136de24f6c18837c2ec4aaad31993accedb66b5fedc50df282c71039b"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling\n network devices with APPN (Advanced Peer-to-Peer Network) EBN\n (Extended Border Node) capabilities. This memo identifies managed\n objects for the EBN architecture.","scope_keywords":["2457","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2457 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling\n network devices with APPN (Advanced Peer-to-Peer Network) EBN\n (Extended Border Node) capabilities. This memo identifies managed\n objects for the EBN architecture. 2457 key management nested-reference unchanged"},{"id":"IETF RFC 2528","type":"specification","body":"IETF","designation":"RFC 2528","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2528.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2528.txt","https://www.rfc-editor.org/rfc/rfc2528.pdf"],"folder":"IETF/RFC-2528","files":{"txt":{"path":"standards/IETF/RFC-2528/RFC-2528.txt","sha256":"e4dd2ed17f4aba585a7c85a766cf051e8e2a4c7c8c61c71d3b8503e77cf494cc"}},"tags":["nested-reference","unchanged"],"summary":"The Key Exchange Algorithm (KEA) is a classified algorithm for\n exchanging keys. This specification profiles the format and\n semantics of fields in X.509 V3 certificates containing KEA keys. The\n specification addresses the subjectPublicKeyInfo field and the\n keyUsage extension.\n\n1. Executive Summary\n\n This specification contains guidance on the use of the Internet\n Public Key Infrastructure certificates to convey Key Exchange\n Algorithm (KEA) keys. This specification is an addendum to RFC 2459,\n \"Internet X.509 Public Key Infrastructure: Certificate and CRL\n Profile\". Implementations of this specification must also conform to\n RFC 2459. Implementations of this specification are not required to\n conform to other parts from that series.\n\n2. Requirements and Assumptions\n\n The goal is to augment the X.509 certificate profile presented in\n Part 1 to facilitate the management of KEA keys for ","scope_keywords":["2528","algorithm","attribute","attributes","authentication","authorization","certificate","certificates","crl","identification","key","keys","management","path","pki","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2876","folder":"IETF/RFC-2876","source":"IETF/RFC-2876/RFC-2876.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null}],"search_text":"IETF RFC 2528 The Key Exchange Algorithm (KEA) is a classified algorithm for\n exchanging keys. This specification profiles the format and\n semantics of fields in X.509 V3 certificates containing KEA keys. The\n specification addresses the subjectPublicKeyInfo field and the\n keyUsage extension.\n\n1. Executive Summary\n\n This specification contains guidance on the use of the Internet\n Public Key Infrastructure certificates to convey Key Exchange\n Algorithm (KEA) keys. This specification is an addendum to RFC 2459,\n \"Internet X.509 Public Key Infrastructure: Certificate and CRL\n Profile\". Implementations of this specification must also conform to\n RFC 2459. Implementations of this specification are not required to\n conform to other parts from that series.\n\n2. Requirements and Assumptions\n\n The goal is to augment the X.509 certificate profile presented in\n Part 1 to facilitate the management of KEA keys for  2528 algorithm attribute attributes authentication authorization certificate certificates crl identification key keys management path pki policy nested-reference unchanged"},{"id":"IETF RFC 3595","type":"specification","body":"IETF","designation":"RFC 3595","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3595.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3595.txt","https://www.rfc-editor.org/rfc/rfc3595.pdf"],"folder":"IETF/RFC-3595","files":{"txt":{"path":"standards/IETF/RFC-3595/RFC-3595.txt","sha256":"0ac0a26134eb42e09e472cfbcaedb05a0af6d7d7cc68f66d904189c34a896049"}},"tags":["nested-reference","unchanged"],"summary":"This MIB module defines textual conventions to represent the commonly\n used IPv6 Flow Label. The intent is that these textual conventions\n (TCs) will be imported and used in MIB modules that would otherwise\n define their own representations.","scope_keywords":["3595","license","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4087","folder":"IETF/RFC-4087","source":"IETF/RFC-4087/RFC-4087.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"IETF RFC 3595 This MIB module defines textual conventions to represent the commonly\n used IPv6 Flow Label. The intent is that these textual conventions\n (TCs) will be imported and used in MIB modules that would otherwise\n define their own representations. 3595 license management presentation nested-reference unchanged"},{"id":"IETF RFC 3769","type":"specification","body":"IETF","designation":"RFC 3769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3769.txt","https://www.rfc-editor.org/rfc/rfc3769.pdf"],"folder":"IETF/RFC-3769","files":{"txt":{"path":"standards/IETF/RFC-3769/RFC-3769.txt","sha256":"a17fd4ff2424a58a7b67906e5e6dc5d70068d960859509cc6b33895225a12a0a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes requirements for how IPv6 address prefixes\n should be delegated to an IPv6 subscriber's network (or \"site\").\n\n1. Introduction\n\n With the deployment of IPv6 [1], several Internet Service Providers\n are ready to offer IPv6 access to the public. In conjunction with\n widely deployed \"always on\" media such as ADSL and the expectation\n that customers will be assigned a /48 IPv6 unicast address prefix\n (see RFC 3513 [3] and section 3 of RFC 3177 [2]), an efficient\n mechanism for delegating address prefixes to the customer's sites is\n needed. The delegation mechanism will be intended to automate the\n process of informing the customer's networking equipment of the\n prefixes to be used at the customer's site.\n\n This document clarifies the requirements for IPv6 address prefix\n delegation from the ISP to the site.\n\nMiyakawa & Droms Informational [Page 1]\n\f\nRFC 3769 Requiremen","scope_keywords":["3769","authentication","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 3769 This document describes requirements for how IPv6 address prefixes\n should be delegated to an IPv6 subscriber's network (or \"site\").\n\n1. Introduction\n\n With the deployment of IPv6 [1], several Internet Service Providers\n are ready to offer IPv6 access to the public. In conjunction with\n widely deployed \"always on\" media such as ADSL and the expectation\n that customers will be assigned a /48 IPv6 unicast address prefix\n (see RFC 3513 [3] and section 3 of RFC 3177 [2]), an efficient\n mechanism for delegating address prefixes to the customer's sites is\n needed. The delegation mechanism will be intended to automate the\n process of informing the customer's networking equipment of the\n prefixes to be used at the customer's site.\n\n This document clarifies the requirements for IPv6 address prefix\n delegation from the ISP to the site.\n\nMiyakawa & Droms Informational [Page 1]\n\f\nRFC 3769 Requiremen 3769 authentication policy trust nested-reference unchanged"},{"id":"IETF RFC 3904","type":"specification","body":"IETF","designation":"RFC 3904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3904.txt","https://www.rfc-editor.org/rfc/rfc3904.pdf"],"folder":"IETF/RFC-3904","files":{"txt":{"path":"standards/IETF/RFC-3904/RFC-3904.txt","sha256":"15da7fc94973ee8e66b0add3b290641822531a6f698db534dd80dab172b5c461"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes issues involved in the transition of\n \"unmanaged networks\" from IPv4 to IPv6. Unmanaged networks typically\n correspond to home networks or small office networks. A companion\n paper analyzes out the requirements for mechanisms needed in various\n transition scenarios of these networks to IPv6. Starting from this\n analysis, we evaluate the suitability of mechanisms that have already\n been specified, proposed, or deployed.","scope_keywords":["3904","attribute","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null}],"search_text":"IETF RFC 3904 This document analyzes issues involved in the transition of\n \"unmanaged networks\" from IPv4 to IPv6. Unmanaged networks typically\n correspond to home networks or small office networks. A companion\n paper analyzes out the requirements for mechanisms needed in various\n transition scenarios of these networks to IPv6. Starting from this\n analysis, we evaluate the suitability of mechanisms that have already\n been specified, proposed, or deployed. 3904 attribute path risk nested-reference unchanged"},{"id":"IETF RFC 4659","type":"specification","body":"IETF","designation":"RFC 4659","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4659.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4659.txt","https://www.rfc-editor.org/rfc/rfc4659.pdf"],"folder":"IETF/RFC-4659","files":{"txt":{"path":"standards/IETF/RFC-4659/RFC-4659.txt","sha256":"046035fe5b0e68e3c8c60dd205e4a9eae5e4a3a0d9819a3f493862a8d3d15035"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method by which a Service Provider may use\n its packet-switched backbone to provide Virtual Private Network (VPN)\n services for its IPv6 customers. This method reuses, and extends\n where necessary, the \"BGP/MPLS IP VPN\" method for support of IPv6.\n In BGP/MPLS IP VPN, \"Multiprotocol BGP\" is used for distributing IPv4\n VPN routes over the service provider backbone, and MPLS is used to\n forward IPv4 VPN packets over the backbone. This document defines an\n IPv6 VPN address family and describes the corresponding IPv6 VPN\n route distribution in \"Multiprotocol BGP\".\n\n This document defines support of the IPv6 VPN service over both an\n IPv4 and an IPv6 backbone, and for using various tunneling techniques\n over the core, including MPLS, IP-in-IP, Generic Routing\n Encapsulation (GRE) and IPsec protected tunnels. The inter-working\n between an IPv4 site and an IPv6 site is","scope_keywords":["4659","algorithm","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 5549","folder":"IETF/RFC-5549","source":"IETF/RFC-5549/RFC-5549.txt","version":null},{"body":"IETF","designation":"RFC 5566","folder":"IETF/RFC-5566","source":"IETF/RFC-5566/RFC-5566.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6513","folder":"IETF/RFC-6513","source":"IETF/RFC-6513/RFC-6513.txt","version":null},{"body":"IETF","designation":"RFC 6514","folder":"IETF/RFC-6514","source":"IETF/RFC-6514/RFC-6514.txt","version":null}],"search_text":"IETF RFC 4659 This document describes a method by which a Service Provider may use\n its packet-switched backbone to provide Virtual Private Network (VPN)\n services for its IPv6 customers. This method reuses, and extends\n where necessary, the \"BGP/MPLS IP VPN\" method for support of IPv6.\n In BGP/MPLS IP VPN, \"Multiprotocol BGP\" is used for distributing IPv4\n VPN routes over the service provider backbone, and MPLS is used to\n forward IPv4 VPN packets over the backbone. This document defines an\n IPv6 VPN address family and describes the corresponding IPv6 VPN\n route distribution in \"Multiprotocol BGP\".\n\n This document defines support of the IPv6 VPN service over both an\n IPv4 and an IPv6 backbone, and for using various tunneling techniques\n over the core, including MPLS, IP-in-IP, Generic Routing\n Encapsulation (GRE) and IPsec protected tunnels. The inter-working\n between an IPv4 site and an IPv6 site is 4659 algorithm key management path nested-reference unchanged"},{"id":"IETF RFC 4885","type":"specification","body":"IETF","designation":"RFC 4885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4885.txt","https://www.rfc-editor.org/rfc/rfc4885.pdf"],"folder":"IETF/RFC-4885","files":{"txt":{"path":"standards/IETF/RFC-4885/RFC-4885.txt","sha256":"06318ad143abe4e0414c6b0c2a27333550c608be502add468a3caac92c611853"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a terminology for discussing network mobility\n (NEMO) issues and solution requirements.","scope_keywords":["4885","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null},{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null},{"body":"IETF","designation":"RFC 6089","folder":"IETF/RFC-6089","source":"IETF/RFC-6089/RFC-6089.txt","version":null}],"search_text":"IETF RFC 4885 This document defines a terminology for discussing network mobility\n (NEMO) issues and solution requirements. 4885 trust nested-reference unchanged"},{"id":"IETF RFC 5157","type":"specification","body":"IETF","designation":"RFC 5157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5157.txt","https://www.rfc-editor.org/rfc/rfc5157.pdf"],"folder":"IETF/RFC-5157","files":{"txt":{"path":"standards/IETF/RFC-5157/RFC-5157.txt","sha256":"2ba8ee1bd7e550a10f88dbb6aabae79918a82bb876dfed2645872e732c86bd7b"}},"tags":["nested-reference","unchanged"],"summary":"The much larger default 64-bit subnet address space of IPv6 should in\n principle make traditional network (port) scanning techniques used by\n certain network worms or scanning tools less effective. While\n traditional network scanning probes (whether by individuals or\n automated via network worms) may become less common, administrators\n should be aware that attackers may use other techniques to discover\n IPv6 addresses on a target network, and thus they should also be\n aware of measures that are available to mitigate them. This\n informational document discusses approaches that administrators could\n take when planning their site address allocation and management\n strategies as part of a defence-in-depth approach to network\n security.\n\nChown Informational [Page 1]\n\f\nRFC 5157 IPv6 Network Scanning March 2008","scope_keywords":["5157","key","management","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 5991","folder":"IETF/RFC-5991","source":"IETF/RFC-5991/RFC-5991.txt","version":null},{"body":"IETF","designation":"RFC 6583","folder":"IETF/RFC-6583","source":"IETF/RFC-6583/RFC-6583.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null}],"search_text":"IETF RFC 5157 The much larger default 64-bit subnet address space of IPv6 should in\n principle make traditional network (port) scanning techniques used by\n certain network worms or scanning tools less effective. While\n traditional network scanning probes (whether by individuals or\n automated via network worms) may become less common, administrators\n should be aware that attackers may use other techniques to discover\n IPv6 addresses on a target network, and thus they should also be\n aware of measures that are available to mitigate them. This\n informational document discusses approaches that administrators could\n take when planning their site address allocation and management\n strategies as part of a defence-in-depth approach to network\n security.\n\nChown Informational [Page 1]\n\f\nRFC 5157 IPv6 Network Scanning March 2008 5157 key management pid subject nested-reference unchanged"},{"id":"IETF RFC 5871","type":"specification","body":"IETF","designation":"RFC 5871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5871.txt","https://www.rfc-editor.org/rfc/rfc5871.pdf"],"folder":"IETF/RFC-5871","files":{"txt":{"path":"standards/IETF/RFC-5871/RFC-5871.txt","sha256":"5e981d8d787caf97bc61ca580a576364f7a04209aac0df981da8530cd4dcd433"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the IANA guidelines for allocating new values\n for the Routing Type field in the IPv6 Routing Header.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5871.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating t","scope_keywords":["5871","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 5871 This document specifies the IANA guidelines for allocating new values\n for the Routing Type field in the IPv6 Routing Header.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5871.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating t 5871 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7098","type":"specification","body":"IETF","designation":"RFC 7098","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7098.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7098.txt","https://www.rfc-editor.org/rfc/rfc7098.pdf"],"folder":"IETF/RFC-7098","files":{"txt":{"path":"standards/IETF/RFC-7098/RFC-7098.txt","sha256":"1b1f39be52231ed94c40001b58974e1c43a64d544d01f2107b71565f2d4d9155"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the currently specified IPv6 flow label\n can be used to enhance layer 3/4 (L3/4) load distribution and\n balancing for large server farms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7098.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons ide","scope_keywords":["7098","algorithm","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null}],"search_text":"IETF RFC 7098 This document describes how the currently specified IPv6 flow label\n can be used to enhance layer 3/4 (L3/4) load distribution and\n balancing for large server farms.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7098.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons ide 7098 algorithm http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 8021","type":"specification","body":"IETF","designation":"RFC 8021","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8021.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8021.txt","https://www.rfc-editor.org/rfc/rfc8021.pdf"],"folder":"IETF/RFC-8021","files":{"txt":{"path":"standards/IETF/RFC-8021/RFC-8021.txt","sha256":"3d9ac2e9fbea2386197358f88006a1b8a345f39fd6f7bf5557b07a9c8d1a2f72"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the security implications of the generation\n of IPv6 atomic fragments and a number of interoperability issues\n associated with IPv6 atomic fragments. It concludes that the\n aforementioned functionality is undesirable and thus documents the\n motivation for removing this functionality from an upcoming revision\n of the core IPv6 protocol specification (RFC 2460).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informatio","scope_keywords":["8021","algorithm","http","identification","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null}],"search_text":"IETF RFC 8021 This document discusses the security implications of the generation\n of IPv6 atomic fragments and a number of interoperability issues\n associated with IPv6 atomic fragments. It concludes that the\n aforementioned functionality is undesirable and thus documents the\n motivation for removing this functionality from an upcoming revision\n of the core IPv6 protocol specification (RFC 2460).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Informatio 8021 algorithm http identification license path subject trust nested-reference unchanged"},{"id":"IETF RFC 2469","type":"specification","body":"IETF","designation":"RFC 2469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2469.txt","https://www.rfc-editor.org/rfc/rfc2469.pdf"],"folder":"IETF/RFC-2469","files":{"txt":{"path":"standards/IETF/RFC-2469/RFC-2469.txt","sha256":"b169facb96353713c504085e04aeb5ec17a0e9a9fb1168f77dbd46ace331e24d"}},"tags":["nested-reference","unchanged"],"summary":"Protocols such as ARP and Neighbor Discovery have data fields that\n contain link-layer addresses. In order to interoperate properly, a\n sender setting such a field must insure that the receiver extracts\n those bits and interprets them correctly. In most cases, such fields\n must be in \"canonical form\". Unfortunately, not all LAN adaptors are\n consistent in their use of canonical form, and implementations may\n need to explicitly bit swap individual bytes in order to obtain the\n correct format. This document provides information to implementors\n to help them avoid the pitfall of using non-canonical forms when\n canonical forms are required.","scope_keywords":["2469"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2467","folder":"IETF/RFC-2467","source":"IETF/RFC-2467/RFC-2467.txt","version":null},{"body":"IETF","designation":"RFC 2470","folder":"IETF/RFC-2470","source":"IETF/RFC-2470/RFC-2470.txt","version":null},{"body":"IETF","designation":"RFC 2472","folder":"IETF/RFC-2472","source":"IETF/RFC-2472/RFC-2472.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 3572","folder":"IETF/RFC-3572","source":"IETF/RFC-3572/RFC-3572.txt","version":null},{"body":"IETF","designation":"RFC 3643","folder":"IETF/RFC-3643","source":"IETF/RFC-3643/RFC-3643.txt","version":null},{"body":"IETF","designation":"RFC 5072","folder":"IETF/RFC-5072","source":"IETF/RFC-5072/RFC-5072.txt","version":null}],"search_text":"IETF RFC 2469 Protocols such as ARP and Neighbor Discovery have data fields that\n contain link-layer addresses. In order to interoperate properly, a\n sender setting such a field must insure that the receiver extracts\n those bits and interprets them correctly. In most cases, such fields\n must be in \"canonical form\". Unfortunately, not all LAN adaptors are\n consistent in their use of canonical form, and implementations may\n need to explicitly bit swap individual bytes in order to obtain the\n correct format. This document provides information to implementors\n to help them avoid the pitfall of using non-canonical forms when\n canonical forms are required. 2469 nested-reference unchanged"},{"id":"IETF RFC 3627","type":"specification","body":"IETF","designation":"RFC 3627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3627.txt","https://www.rfc-editor.org/rfc/rfc3627.pdf"],"folder":"IETF/RFC-3627","files":{"txt":{"path":"standards/IETF/RFC-3627/RFC-3627.txt","sha256":"f53a50f02fa84cc1d858ade8b0cc8d26effac11c74de5563095cfad2546618e3"}},"tags":["nested-reference","unchanged"],"summary":"In some cases, the operational decision may be to use IPv6 /127\n prefix lengths, especially on point-to-point links between routers.\n Under certain situations, this may lead to one router claiming both\n addresses due to subnet-router anycast being implemented. This\n document discusses the issue and offers a couple of solutions to the\n problem; nevertheless, /127 should be avoided between two routers.\n\n1. Introduction\n\n [ADDRARCH] defines Subnet-router anycast address: in a subnet prefix\n of n bits, the last 128-n bits are all zero. It is meant to be in\n use of any one router in the subnet.\n\n Even though having prefix length longer than /64 is forbidden by\n [ADDRARCH] section 2.4 for non-000/3 unicast prefixes, using /127\n prefix length has gained a lot of operational popularity; it seems\n like that these prefix lengths are being used heavily in point-to-\n point links. The operational pra","scope_keywords":["3627","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3775","folder":"IETF/RFC-3775","source":"IETF/RFC-3775/RFC-3775.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null},{"body":"IETF","designation":"RFC 6164","folder":"IETF/RFC-6164","source":"IETF/RFC-6164/RFC-6164.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null}],"search_text":"IETF RFC 3627 In some cases, the operational decision may be to use IPv6 /127\n prefix lengths, especially on point-to-point links between routers.\n Under certain situations, this may lead to one router claiming both\n addresses due to subnet-router anycast being implemented. This\n document discusses the issue and offers a couple of solutions to the\n problem; nevertheless, /127 should be avoided between two routers.\n\n1. Introduction\n\n [ADDRARCH] defines Subnet-router anycast address: in a subnet prefix\n of n bits, the last 128-n bits are all zero. It is meant to be in\n use of any one router in the subnet.\n\n Even though having prefix length longer than /64 is forbidden by\n [ADDRARCH] section 2.4 for non-000/3 unicast prefixes, using /127\n prefix length has gained a lot of operational popularity; it seems\n like that these prefix lengths are being used heavily in point-to-\n point links. The operational pra 3627 path nested-reference unchanged"},{"id":"IETF RFC 4076","type":"specification","body":"IETF","designation":"RFC 4076","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4076.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4076.txt","https://www.rfc-editor.org/rfc/rfc4076.pdf"],"folder":"IETF/RFC-4076","files":{"txt":{"path":"standards/IETF/RFC-4076/RFC-4076.txt","sha256":"2c37f6ea2b8067f64085fe923882e7bd49b6b96aac7ed4a509ff5c74dc34991d"}},"tags":["nested-reference","unchanged"],"summary":"IPv6 hosts using Stateless Address Autoconfiguration are able to\n configure their IPv6 address and default router settings\n automatically. However, further settings are not available. If\n these hosts wish to configure their DNS, NTP, or other specific\n settings automatically, the stateless variant of the Dynamic Host\n Configuration Protocol for IPv6 (DHCPv6) could be used. This\n combination of Stateless Address Autoconfiguration and stateless\n DHCPv6 could be used quite commonly in IPv6 networks. However, hosts\n using this combination currently have no means by which to be\n informed of changes in stateless DHCPv6 option settings; e.g., the\n addition of a new NTP server address, a change in DNS search paths,\n or full site renumbering. This document is presented as a problem\n statement from which a solution should be proposed in a subsequent\n document.\n\nChown, et al. Informational [Page 1]","scope_keywords":["4076","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4242","folder":"IETF/RFC-4242","source":"IETF/RFC-4242/RFC-4242.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 5887","folder":"IETF/RFC-5887","source":"IETF/RFC-5887/RFC-5887.txt","version":null}],"search_text":"IETF RFC 4076 IPv6 hosts using Stateless Address Autoconfiguration are able to\n configure their IPv6 address and default router settings\n automatically. However, further settings are not available. If\n these hosts wish to configure their DNS, NTP, or other specific\n settings automatically, the stateless variant of the Dynamic Host\n Configuration Protocol for IPv6 (DHCPv6) could be used. This\n combination of Stateless Address Autoconfiguration and stateless\n DHCPv6 could be used quite commonly in IPv6 networks. However, hosts\n using this combination currently have no means by which to be\n informed of changes in stateless DHCPv6 option settings; e.g., the\n addition of a new NTP server address, a change in DNS search paths,\n or full site renumbering. This document is presented as a problem\n statement from which a solution should be proposed in a subsequent\n document.\n\nChown, et al. Informational [Page 1] 4076 path nested-reference unchanged"},{"id":"IETF RFC 4135","type":"specification","body":"IETF","designation":"RFC 4135","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4135.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4135.txt","https://www.rfc-editor.org/rfc/rfc4135.pdf"],"folder":"IETF/RFC-4135","files":{"txt":{"path":"standards/IETF/RFC-4135/RFC-4135.txt","sha256":"1261ac9d097053070988ff2dd3669104c10a70052af365d33a8de473938b3c99"}},"tags":["nested-reference","unchanged"],"summary":"When a host establishes a new link-layer connection, it may or may\n not have a valid IP configuration for Internet connectivity. The\n host may check for link change (i.e., determine whether a link change\n has occurred), and then, based on the result, it can automatically\n decide whether its IP configuration is still valid. During link\n identity detection, the host may also collect necessary information\n to initiate a new IP configuration if the IP subnet has changed. In\n this memo, this procedure is called Detecting Network Attachment\n (DNA). DNA schemes should be precise, sufficiently fast, secure, and\n of limited signaling.","scope_keywords":["4135","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 4941","folder":"IETF/RFC-4941","source":"IETF/RFC-4941/RFC-4941.txt","version":null},{"body":"IETF","designation":"RFC 4957","folder":"IETF/RFC-4957","source":"IETF/RFC-4957/RFC-4957.txt","version":null}],"search_text":"IETF RFC 4135 When a host establishes a new link-layer connection, it may or may\n not have a valid IP configuration for Internet connectivity. The\n host may check for link change (i.e., determine whether a link change\n has occurred), and then, based on the result, it can automatically\n decide whether its IP configuration is still valid. During link\n identity detection, the host may also collect necessary information\n to initiate a new IP configuration if the IP subnet has changed. In\n this memo, this procedure is called Detecting Network Attachment\n (DNA). DNA schemes should be precise, sufficiently fast, secure, and\n of limited signaling. 4135 pid nested-reference unchanged"},{"id":"IETF RFC 4225","type":"specification","body":"IETF","designation":"RFC 4225","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4225.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4225.txt","https://www.rfc-editor.org/rfc/rfc4225.pdf"],"folder":"IETF/RFC-4225","files":{"txt":{"path":"standards/IETF/RFC-4225/RFC-4225.txt","sha256":"02f2ec7a7c8cc627105e77e25dfda00340b692c33e19ebc52e0b4fb324dfa7a2"}},"tags":["nested-reference","unchanged"],"summary":"This document is an account of the rationale behind the Mobile IPv6\n (MIPv6) Route Optimization security design. The purpose of this\n document is to present the thinking and to preserve the reasoning\n behind the Mobile IPv6 security design in 2001 - 2002.\n\n The document has two target audiences: (1) helping MIPv6 implementors\n to better understand the design choices in MIPv6 security procedures,\n and (2) allowing people dealing with mobility or multi-homing to\n avoid a number of potential security pitfalls in their designs.\n\nNikander, et al. Informational [Page 1]\n\f\nRFC 4225 Mobile IPv6 RO Security Design December 2005","scope_keywords":["4225","authorization","risk","seal","sealing","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4423","folder":"IETF/RFC-4423","source":"IETF/RFC-4423/RFC-4423.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null},{"body":"IETF","designation":"RFC 4866","folder":"IETF/RFC-4866","source":"IETF/RFC-4866/RFC-4866.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 5206","folder":"IETF/RFC-5206","source":"IETF/RFC-5206/RFC-5206.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5619","folder":"IETF/RFC-5619","source":"IETF/RFC-5619/RFC-5619.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null}],"search_text":"IETF RFC 4225 This document is an account of the rationale behind the Mobile IPv6\n (MIPv6) Route Optimization security design. The purpose of this\n document is to present the thinking and to preserve the reasoning\n behind the Mobile IPv6 security design in 2001 - 2002.\n\n The document has two target audiences: (1) helping MIPv6 implementors\n to better understand the design choices in MIPv6 security procedures,\n and (2) allowing people dealing with mobility or multi-homing to\n avoid a number of potential security pitfalls in their designs.\n\nNikander, et al. Informational [Page 1]\n\f\nRFC 4225 Mobile IPv6 RO Security Design December 2005 4225 authorization risk seal sealing trust nested-reference unchanged"},{"id":"IETF RFC 4889","type":"specification","body":"IETF","designation":"RFC 4889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4889.txt","https://www.rfc-editor.org/rfc/rfc4889.pdf"],"folder":"IETF/RFC-4889","files":{"txt":{"path":"standards/IETF/RFC-4889/RFC-4889.txt","sha256":"1d37e030bafa5777d1ae1448c986b4ad14915bf4edb1201542ad7b417424ba22"}},"tags":["nested-reference","unchanged"],"summary":"With current Network Mobility (NEMO) Basic Support, all\n communications to and from Mobile Network Nodes must go through the\n Mobile Router and Home Agent (MRHA) tunnel when the mobile network is\n away. This results in increased length of packet route and increased\n packet delay in most cases. To overcome these limitations, one might\n have to turn to Route Optimization (RO) for NEMO. This memo\n documents various types of Route Optimization in NEMO and explores\n the benefits and tradeoffs in different aspects of NEMO Route\n Optimization.","scope_keywords":["4889","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4886","folder":"IETF/RFC-4886","source":"IETF/RFC-4886/RFC-4886.txt","version":null}],"search_text":"IETF RFC 4889 With current Network Mobility (NEMO) Basic Support, all\n communications to and from Mobile Network Nodes must go through the\n Mobile Router and Home Agent (MRHA) tunnel when the mobile network is\n away. This results in increased length of packet route and increased\n packet delay in most cases. To overcome these limitations, one might\n have to turn to Route Optimization (RO) for NEMO. This memo\n documents various types of Route Optimization in NEMO and explores\n the benefits and tradeoffs in different aspects of NEMO Route\n Optimization. 4889 path trust nested-reference unchanged"},{"id":"IETF RFC 4980","type":"specification","body":"IETF","designation":"RFC 4980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4980.txt","https://www.rfc-editor.org/rfc/rfc4980.pdf"],"folder":"IETF/RFC-4980","files":{"txt":{"path":"standards/IETF/RFC-4980/RFC-4980.txt","sha256":"a7f08d3689c07722d76ded2d53a1a23c40c2630ebe3ad4c3bbbb163b8fe1956f"}},"tags":["nested-reference","unchanged"],"summary":"This document is an analysis of multihoming in the context of network\n mobility (NEMO) in IPv6. As there are many situations in which\n mobile networks may be multihomed, a taxonomy is proposed to classify\n the possible configurations. The possible deployment scenarios of\n multihomed mobile networks are described together with the associated\n issues when network mobility is supported by RFC 3963 (NEMO Basic\n Support). Recommendations are offered on how to address these\n issues.","scope_keywords":["4980","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5648","folder":"IETF/RFC-5648","source":"IETF/RFC-5648/RFC-5648.txt","version":null}],"search_text":"IETF RFC 4980 This document is an analysis of multihoming in the context of network\n mobility (NEMO) in IPv6. As there are many situations in which\n mobile networks may be multihomed, a taxonomy is proposed to classify\n the possible configurations. The possible deployment scenarios of\n multihomed mobile networks are described together with the associated\n issues when network mobility is supported by RFC 3963 (NEMO Basic\n Support). Recommendations are offered on how to address these\n issues. 4980 management path nested-reference unchanged"},{"id":"IETF RFC 4057","type":"specification","body":"IETF","designation":"RFC 4057","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4057.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4057.txt","https://www.rfc-editor.org/rfc/rfc4057.pdf"],"folder":"IETF/RFC-4057","files":{"txt":{"path":"standards/IETF/RFC-4057/RFC-4057.txt","sha256":"984c737affe966480c212ab8288b0fe9cf79b18c38aa4ed139456983a15498dc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the scenarios for IPv6 deployment within\n enterprise networks. It defines a small set of basic enterprise\n scenarios and includes pertinent questions to allow enterprise\n administrators to further refine their deployment scenarios.\n Enterprise deployment requirements are discussed in terms of\n coexistence with IPv4 nodes, networks and applications, and in terms\n of basic network infrastructure requirements for IPv6 deployment.\n The scenarios and requirements described in this document will be the\n basis for further analysis to determine what coexistence techniques\n and mechanisms are needed for enterprise IPv6 deployment. The\n results of that analysis will be published in a separate document.","scope_keywords":["4057","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 5211","folder":"IETF/RFC-5211","source":"IETF/RFC-5211/RFC-5211.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null}],"search_text":"IETF RFC 4057 This document describes the scenarios for IPv6 deployment within\n enterprise networks. It defines a small set of basic enterprise\n scenarios and includes pertinent questions to allow enterprise\n administrators to further refine their deployment scenarios.\n Enterprise deployment requirements are discussed in terms of\n coexistence with IPv4 nodes, networks and applications, and in terms\n of basic network infrastructure requirements for IPv6 deployment.\n The scenarios and requirements described in this document will be the\n basis for further analysis to determine what coexistence techniques\n and mechanisms are needed for enterprise IPv6 deployment. The\n results of that analysis will be published in a separate document. 4057 management nested-reference unchanged"},{"id":"IETF RFC 2468","type":"specification","body":"IETF","designation":"RFC 2468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2468.txt","https://www.rfc-editor.org/rfc/rfc2468.pdf"],"folder":"IETF/RFC-2468","files":{"txt":{"path":"standards/IETF/RFC-2468/RFC-2468.txt","sha256":"f5360f4e8a7be2a06c1b7f171148d48b8e4b973e7c608fb20b6fcbb25d4d55d6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 2468 MCI\nCategory: Informational October 1998\n\n I REMEMBER IANA\n\n October 17, 1998\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nRemembrance\n\n A long time ago, in a network, far far away, a great adventure took\n place!\n\n Out of the chaos of new ideas for communication, the experiments, the\n tentative designs, and crucible of testing, there emerged a\n cornucopia of networks. Beginning with the ARPANET, an endless\n stream of networks evolved, and ultimately were interlinked to become\n the Internet. Someone had to keep track of all the protocols, the\n identifiers, networks and addresses and ultimately the names of all\n the thi","scope_keywords":["2468","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"IETF RFC 2468 Network Working Group V. Cerf\nRequest for Comments: 2468 MCI\nCategory: Informational October 1998\n\n I REMEMBER IANA\n\n October 17, 1998\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1998). All Rights Reserved.\n\nRemembrance\n\n A long time ago, in a network, far far away, a great adventure took\n place!\n\n Out of the chaos of new ideas for communication, the experiments, the\n tentative designs, and crucible of testing, there emerged a\n cornucopia of networks. Beginning with the ARPANET, an endless\n stream of networks evolved, and ultimately were interlinked to become\n the Internet. Someone had to keep track of all the protocols, the\n identifiers, networks and addresses and ultimately the names of all\n the thi 2468 risk subject trust nested-reference unchanged"},{"id":"IETF RFC 247","type":"specification","body":"IETF","designation":"RFC 247","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc247.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc247.txt","https://www.rfc-editor.org/rfc/rfc247.pdf"],"folder":"IETF/RFC-247","files":{"txt":{"path":"standards/IETF/RFC-247/RFC-247.txt","sha256":"b4de9a05d72fe5f46476c1f0c31cea9564939fd8f013f4e7863838b045aa5b54"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Peggy Karp\nRequest for Comments: #247 MITRE\nNIC 7688 12 October 1971\nCategories: Policy, Telnet\nRelated: #226, 236, 239, 233, 237\nObsoletes: #226\n\n Proferred Set of Standard Host Names\n\n In RFC #226, BBN's TENEX list of Host names was set up as a strawman\n set of standard Host names. Comments received since then (an RFC\n actually generated comments!!!) have influenced me to propose the\n following general rules for forming Host names.\n\n The Host names will be 8 characters in length. The general form is\n\n '-' \n\n will be at most 4 characters, formed as follows:\n\n (a) Use the keyword in the site name, if not more than\n four characters, e.g., NASA Ames, Case Western\n Reserve. ---- ----\n\n (b) Use the standard acronym, if not more than four\n characters, e.g., UCLA, RADC, NBS.\n\n (c) If a standard abbreviation exists, use it, e.g., Ill.\n\n (d) If none of the above apply, use ","scope_keywords":["247","key","policy","subject","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 273","folder":"IETF/RFC-273","source":"IETF/RFC-273/RFC-273.txt","version":null},{"body":"IETF","designation":"RFC 289","folder":"IETF/RFC-289","source":"IETF/RFC-289/RFC-289.txt","version":null}],"search_text":"IETF RFC 247 Network Working Group Peggy Karp\nRequest for Comments: #247 MITRE\nNIC 7688 12 October 1971\nCategories: Policy, Telnet\nRelated: #226, 236, 239, 233, 237\nObsoletes: #226\n\n Proferred Set of Standard Host Names\n\n In RFC #226, BBN's TENEX list of Host names was set up as a strawman\n set of standard Host names. Comments received since then (an RFC\n actually generated comments!!!) have influenced me to propose the\n following general rules for forming Host names.\n\n The Host names will be 8 characters in length. The general form is\n\n '-' \n\n will be at most 4 characters, formed as follows:\n\n (a) Use the keyword in the site name, if not more than\n four characters, e.g., NASA Ames, Case Western\n Reserve. ---- ----\n\n (b) Use the standard acronym, if not more than four\n characters, e.g., UCLA, RADC, NBS.\n\n (c) If a standard abbreviation exists, use it, e.g., Ill.\n\n (d) If none of the above apply, use  247 key policy subject tsp nested-reference unchanged"},{"id":"IETF RFC 273","type":"specification","body":"IETF","designation":"RFC 273","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc273.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc273.txt","https://www.rfc-editor.org/rfc/rfc273.pdf"],"folder":"IETF/RFC-273","files":{"txt":{"path":"standards/IETF/RFC-273/RFC-273.txt","sha256":"711e962f05bd5dbed147e11003c466769286c487f97b4f8d3902dfa7fc2aba7a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Richard W. Watson\nRequest for Comments #273 SRI-ARC\nNIC 7837 18 October 1971\nCategories:\nRelated: 7625, 7626, 7661, 7688, 7650, 7646\nObsoletes: 7662\n\n MORE ON STANDARD HOST NAMES\n\n The Network Information Center is a logical place to handle this\n problem of Standard Host Names and so the ball now rests here.\n This is clearly a delicate subject with people having strong\n feelings and attachments to names. No past proposal, including\n RFC 247, NIC 7668, has yet achieved any acceptance. This\n identification seems a natural thing and should be taken into\n account in setting up a naming scheme. Therefore, the following\n proposal is offered which I hope may be satisfactory to everyone.\n\n Any naming scheme must:\n\n (1) Recognize the expanding character of the Network, with\n the potential eventually of several hundred sites.\n\n (2) Recognize the need for abbreviations to simp","scope_keywords":["273","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 289","folder":"IETF/RFC-289","source":"IETF/RFC-289/RFC-289.txt","version":null}],"search_text":"IETF RFC 273 Network Working Group Richard W. Watson\nRequest for Comments #273 SRI-ARC\nNIC 7837 18 October 1971\nCategories:\nRelated: 7625, 7626, 7661, 7688, 7650, 7646\nObsoletes: 7662\n\n MORE ON STANDARD HOST NAMES\n\n The Network Information Center is a logical place to handle this\n problem of Standard Host Names and so the ball now rests here.\n This is clearly a delicate subject with people having strong\n feelings and attachments to names. No past proposal, including\n RFC 247, NIC 7668, has yet achieved any acceptance. This\n identification seems a natural thing and should be taken into\n account in setting up a naming scheme. Therefore, the following\n proposal is offered which I hope may be satisfactory to everyone.\n\n Any naming scheme must:\n\n (1) Recognize the expanding character of the Network, with\n the potential eventually of several hundred sites.\n\n (2) Recognize the need for abbreviations to simp 273 identification subject nested-reference unchanged"},{"id":"IETF RFC 7040","type":"specification","body":"IETF","designation":"RFC 7040","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7040.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7040.txt","https://www.rfc-editor.org/rfc/rfc7040.pdf"],"folder":"IETF/RFC-7040","files":{"txt":{"path":"standards/IETF/RFC-7040/RFC-7040.txt","sha256":"739b8075dab287ae46c06a50f4a27d654799a93de26fdcc16920d1e1b04c36e5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism called Public 4over6, which is\n designed to provide IPv4 Internet connectivity over an IPv6 access\n network using global IPv4 addresses. Public 4over6 was developed in\n the IETF and is in use in some existing deployments but is not\n recommended for new deployments. Future deployments of similar\n scenarios should use Lightweight 4over6. Public 4over6 follows the\n Hub and Spoke softwire model and uses an IPv4-in-IPv6 tunnel to\n forward IPv4 packets over an IPv6 access network. The\n bidirectionality of the IPv4 communication is achieved by explicitly\n allocating global non-shared IPv4 addresses to end users and by\n maintaining IPv4-IPv6 address binding on the border relay. Public\n 4over6 aims to provide uninterrupted IPv4 services to users, like\n Internet Content Providers (ICPs), etc., while an operator makes the\n access network transition to an IPv6-onl","scope_keywords":["7040","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7596","folder":"IETF/RFC-7596","source":"IETF/RFC-7596/RFC-7596.txt","version":null}],"search_text":"IETF RFC 7040 This document describes a mechanism called Public 4over6, which is\n designed to provide IPv4 Internet connectivity over an IPv6 access\n network using global IPv4 addresses. Public 4over6 was developed in\n the IETF and is in use in some existing deployments but is not\n recommended for new deployments. Future deployments of similar\n scenarios should use Lightweight 4over6. Public 4over6 follows the\n Hub and Spoke softwire model and uses an IPv4-in-IPv6 tunnel to\n forward IPv4 packets over an IPv6 access network. The\n bidirectionality of the IPv4 communication is achieved by explicitly\n allocating global non-shared IPv4 addresses to end users and by\n maintaining IPv4-IPv6 address binding on the border relay. Public\n 4over6 aims to provide uninterrupted IPv4 services to users, like\n Internet Content Providers (ICPs), etc., while an operator makes the\n access network transition to an IPv6-onl 7040 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2697","type":"specification","body":"IETF","designation":"RFC 2697","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2697.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2697.txt","https://www.rfc-editor.org/rfc/rfc2697.pdf"],"folder":"IETF/RFC-2697","files":{"txt":{"path":"standards/IETF/RFC-2697/RFC-2697.txt","sha256":"a5f862a1997cf6fe230242ce04a726e75af798f07af7bbc012f20fa8540b6541"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Heinanen\nRequest for Comments: 2697 Telia Finland\nCategory: Informational R. Guerin\n University of Pennsylvania\n September 1999\n\n A Single Rate Three Color Marker\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a Single Rate Three Color Marker (srTCM), which\n can be used as component in a Diffserv traffic conditioner [RFC2475,\n RFC2474]. The srTCM meters a traffic stream and marks its packets\n according to three traffic parameters, Committed Information Rate\n (CIR), Committed Burst Size (CBS), and Excess Burst Size (EBS), to be\n either green, yellow, or red. A packet is marked green if it doesn't\n exceed the CBS, yellow","scope_keywords":["2697","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2698","folder":"IETF/RFC-2698","source":"IETF/RFC-2698/RFC-2698.txt","version":null},{"body":"IETF","designation":"RFC 2963","folder":"IETF/RFC-2963","source":"IETF/RFC-2963/RFC-2963.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 5624","folder":"IETF/RFC-5624","source":"IETF/RFC-5624/RFC-5624.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 2697 Network Working Group J. Heinanen\nRequest for Comments: 2697 Telia Finland\nCategory: Informational R. Guerin\n University of Pennsylvania\n September 1999\n\n A Single Rate Three Color Marker\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a Single Rate Three Color Marker (srTCM), which\n can be used as component in a Diffserv traffic conditioner [RFC2475,\n RFC2474]. The srTCM meters a traffic stream and marks its packets\n according to three traffic parameters, Committed Information Rate\n (CIR), Committed Burst Size (CBS), and Excess Burst Size (EBS), to be\n either green, yellow, or red. A packet is marked green if it doesn't\n exceed the CBS, yellow 2697 policies policy nested-reference unchanged"},{"id":"IETF RFC 2698","type":"specification","body":"IETF","designation":"RFC 2698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2698.txt","https://www.rfc-editor.org/rfc/rfc2698.pdf"],"folder":"IETF/RFC-2698","files":{"txt":{"path":"standards/IETF/RFC-2698/RFC-2698.txt","sha256":"5ed1953c5d027b87b97316312e117ff747fdb8a73503e4af62fe7977361520bd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Heinanen\nRequest for Comments: 2698 Telia Finland\nCategory: Informational R. Guerin\n University of Pennsylvania\n September 1999\n\n A Two Rate Three Color Marker\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a Two Rate Three Color Marker (trTCM), which\n can be used as a component in a Diffserv traffic conditioner\n [RFC2475, RFC2474]. The trTCM meters an IP packet stream and marks\n its packets based on two rates, Peak Information Rate (PIR) and\n Committed Information Rate (CIR), and their associated burst sizes to\n be either green, yellow, or red. A packet is marked red if it\n exceeds the PIR. Otherwise it is marked eith","scope_keywords":["2698"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2697","folder":"IETF/RFC-2697","source":"IETF/RFC-2697/RFC-2697.txt","version":null},{"body":"IETF","designation":"RFC 2963","folder":"IETF/RFC-2963","source":"IETF/RFC-2963/RFC-2963.txt","version":null},{"body":"IETF","designation":"RFC 3086","folder":"IETF/RFC-3086","source":"IETF/RFC-3086/RFC-3086.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 2698 Network Working Group J. Heinanen\nRequest for Comments: 2698 Telia Finland\nCategory: Informational R. Guerin\n University of Pennsylvania\n September 1999\n\n A Two Rate Three Color Marker\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (1999). All Rights Reserved.\n\nAbstract\n\n This document defines a Two Rate Three Color Marker (trTCM), which\n can be used as a component in a Diffserv traffic conditioner\n [RFC2475, RFC2474]. The trTCM meters an IP packet stream and marks\n its packets based on two rates, Peak Information Rate (PIR) and\n Committed Information Rate (CIR), and their associated burst sizes to\n be either green, yellow, or red. A packet is marked red if it\n exceeds the PIR. Otherwise it is marked eith 2698 nested-reference unchanged"},{"id":"IETF RFC 2859","type":"specification","body":"IETF","designation":"RFC 2859","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2859.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2859.txt","https://www.rfc-editor.org/rfc/rfc2859.pdf"],"folder":"IETF/RFC-2859","files":{"txt":{"path":"standards/IETF/RFC-2859/RFC-2859.txt","sha256":"3a92ca5674549ce2da5b39007c3da1741cb6780f4801382be9a3c0a7366085ca"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Time Sliding Window Three Colour Marker (TSWTCM),\n which can be used as a component in a Diff-Serv traffic conditioner\n [RFC2475, RFC2474]. The marker is intended to mark packets that will\n be treated by the Assured Forwarding (AF) Per Hop Behaviour (PHB)\n [AFPHB] in downstream routers. The TSWTCM meters a traffic stream and\n marks packets to be either green, yellow or red based on the measured\n throughput relative to two specified rates: Committed Target Rate\n (CTR) and Peak Target Rate (PTR).","scope_keywords":["2859","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2963","folder":"IETF/RFC-2963","source":"IETF/RFC-2963/RFC-2963.txt","version":null},{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2859 This memo defines a Time Sliding Window Three Colour Marker (TSWTCM),\n which can be used as a component in a Diff-Serv traffic conditioner\n [RFC2475, RFC2474]. The marker is intended to mark packets that will\n be treated by the Assured Forwarding (AF) Per Hop Behaviour (PHB)\n [AFPHB] in downstream routers. The TSWTCM meters a traffic stream and\n marks packets to be either green, yellow or red based on the measured\n throughput relative to two specified rates: Committed Target Rate\n (CTR) and Peak Target Rate (PTR). 2859 algorithm nested-reference unchanged"},{"id":"IETF RFC 3662","type":"specification","body":"IETF","designation":"RFC 3662","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3662.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3662.txt","https://www.rfc-editor.org/rfc/rfc3662.pdf"],"folder":"IETF/RFC-3662","files":{"txt":{"path":"standards/IETF/RFC-3662/RFC-3662.txt","sha256":"0a544d8d5e23699c3f54beb87f87fd174cd201c2cb2bf1e9aecde65c7a07674c"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes a differentiated services per-domain behavior\n (PDB) whose traffic may be \"starved\" (although starvation is not\n strictly required) in a properly functioning network. This is in\n contrast to the Internet's \"best-effort\" or \"normal Internet traffic\"\n model, where prolonged starvation indicates network problems. In\n this sense, the proposed PDB's traffic is forwarded with a \"lower\"\n priority than the normal \"best-effort\" Internet traffic, thus the PDB\n is called \"Lower Effort\" (LE). Use of this PDB permits a network\n operator to strictly limit the effect of its traffic on \"best-\n effort\"/\"normal\" or all other Internet traffic. This document gives\n some example uses, but does not propose constraining the PDB's use to\n any particular type of traffic.\n\n1. Description of the Lower Effort PDB\n\n This document proposes a differentiated services per-domain behavior\n [RFC3086","scope_keywords":["3662","delivery","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4924","folder":"IETF/RFC-4924","source":"IETF/RFC-4924/RFC-4924.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6297","folder":"IETF/RFC-6297","source":"IETF/RFC-6297/RFC-6297.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null}],"search_text":"IETF RFC 3662 This document proposes a differentiated services per-domain behavior\n (PDB) whose traffic may be \"starved\" (although starvation is not\n strictly required) in a properly functioning network. This is in\n contrast to the Internet's \"best-effort\" or \"normal Internet traffic\"\n model, where prolonged starvation indicates network problems. In\n this sense, the proposed PDB's traffic is forwarded with a \"lower\"\n priority than the normal \"best-effort\" Internet traffic, thus the PDB\n is called \"Lower Effort\" (LE). Use of this PDB permits a network\n operator to strictly limit the effect of its traffic on \"best-\n effort\"/\"normal\" or all other Internet traffic. This document gives\n some example uses, but does not propose constraining the PDB's use to\n any particular type of traffic.\n\n1. Description of the Lower Effort PDB\n\n This document proposes a differentiated services per-domain behavior\n [RFC3086 3662 delivery profile profiles nested-reference unchanged"},{"id":"IETF RFC 5594","type":"specification","body":"IETF","designation":"RFC 5594","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5594.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5594.txt","https://www.rfc-editor.org/rfc/rfc5594.pdf"],"folder":"IETF/RFC-5594","files":{"txt":{"path":"standards/IETF/RFC-5594/RFC-5594.txt","sha256":"68a3c4722000daf348fcb001135d925a498db547d5607f2cb17c599f59b5e3b4"}},"tags":["nested-reference","unchanged"],"summary":"This document reports the outcome of a workshop organized by the\n Real-time Applications and Infrastructure Area Directors of the IETF\n to discuss network delay and congestion issues resulting from\n increased Peer-to-Peer (P2P) traffic volumes. The workshop was held\n on May 28, 2008 at MIT in Cambridge, MA, USA. The goals of the\n workshop were twofold: to understand the technical problems that ISPs\n and end users are experiencing as a result of high volumes of P2P\n traffic, and to begin to understand how the IETF may be helpful in\n addressing these problems. Gaining an understanding of where in the\n IETF this work might be pursued and how to extract feasible work\n items were highlighted as important tasks in pursuit of the latter\n goal. The workshop was very well attended and produced several work\n items that have since been taken up by members of the IETF community.\n\nStatus of This Memo","scope_keywords":["5594","http","license","management","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6057","folder":"IETF/RFC-6057","source":"IETF/RFC-6057/RFC-6057.txt","version":null}],"search_text":"IETF RFC 5594 This document reports the outcome of a workshop organized by the\n Real-time Applications and Infrastructure Area Directors of the IETF\n to discuss network delay and congestion issues resulting from\n increased Peer-to-Peer (P2P) traffic volumes. The workshop was held\n on May 28, 2008 at MIT in Cambridge, MA, USA. The goals of the\n workshop were twofold: to understand the technical problems that ISPs\n and end users are experiencing as a result of high volumes of P2P\n traffic, and to begin to understand how the IETF may be helpful in\n addressing these problems. Gaining an understanding of where in the\n IETF this work might be pursued and how to extract feasible work\n items were highlighted as important tasks in pursuit of the latter\n goal. The workshop was very well attended and produced several work\n items that have since been taken up by members of the IETF community.\n\nStatus of This Memo 5594 http license management policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6371","type":"specification","body":"IETF","designation":"RFC 6371","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6371.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6371.txt","https://www.rfc-editor.org/rfc/rfc6371.pdf"],"folder":"IETF/RFC-6371","files":{"txt":{"path":"standards/IETF/RFC-6371/RFC-6371.txt","sha256":"5a5726c2bccb6fad822b74e3b78ed701a368ed6ba5a5f0190ea0988855a91a65"}},"tags":["nested-reference","unchanged"],"summary":"The Transport Profile of Multiprotocol Label Switching (MPLS-TP) is a\n packet-based transport technology based on the MPLS Traffic\n Engineering (MPLS-TE) and pseudowire (PW) data-plane architectures.\n\n This document describes a framework to support a comprehensive set of\n Operations, Administration, and Maintenance (OAM) procedures that\n fulfill the MPLS-TP OAM requirements for fault, performance, and\n protection-switching management and that do not rely on the presence\n of a control plane.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunications Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nSt","scope_keywords":["6371","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6371 The Transport Profile of Multiprotocol Label Switching (MPLS-TP) is a\n packet-based transport technology based on the MPLS Traffic\n Engineering (MPLS-TE) and pseudowire (PW) data-plane architectures.\n\n This document describes a framework to support a comprehensive set of\n Operations, Administration, and Maintenance (OAM) procedures that\n fulfill the MPLS-TP OAM requirements for fault, performance, and\n protection-switching management and that do not rely on the presence\n of a control plane.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunications Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nSt 6371 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 2963","type":"specification","body":"IETF","designation":"RFC 2963","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2963.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2963.txt","https://www.rfc-editor.org/rfc/rfc2963.pdf"],"folder":"IETF/RFC-2963","files":{"txt":{"path":"standards/IETF/RFC-2963/RFC-2963.txt","sha256":"f7221769bedbbc49b4d180cded72284294f83ac306719ca651613ce218410482"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes several Rate Adaptive Shapers (RAS) that can be\n used in combination with the single rate Three Color Markers (srTCM)\n and the two rate Three Color Marker (trTCM) described in RFC2697 and\n RFC2698, respectively. These RAS improve the performance of TCP when\n a TCM is used at the ingress of a diffserv network by reducing the\n burstiness of the traffic. With TCP traffic, this reduction of the\n burstiness is accompanied by a reduction of the number of marked\n packets and by an improved TCP goodput. The proposed RAS can be used\n at the ingress of Diffserv networks providing the Assured Forwarding\n Per Hop Behavior (AF PHB). They are especially useful when a TCM is\n used to mark traffic composed of a small number of TCP connections.\n\n1. Introduction\n\n In DiffServ networks [RFC2475], the incoming data traffic, with the\n AF PHB in particular, could be subject to marking wher","scope_keywords":["2963","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3289","folder":"IETF/RFC-3289","source":"IETF/RFC-3289/RFC-3289.txt","version":null},{"body":"IETF","designation":"RFC 3317","folder":"IETF/RFC-3317","source":"IETF/RFC-3317/RFC-3317.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null}],"search_text":"IETF RFC 2963 This memo describes several Rate Adaptive Shapers (RAS) that can be\n used in combination with the single rate Three Color Markers (srTCM)\n and the two rate Three Color Marker (trTCM) described in RFC2697 and\n RFC2698, respectively. These RAS improve the performance of TCP when\n a TCM is used at the ingress of a diffserv network by reducing the\n burstiness of the traffic. With TCP traffic, this reduction of the\n burstiness is accompanied by a reduction of the number of marked\n packets and by an improved TCP goodput. The proposed RAS can be used\n at the ingress of Diffserv networks providing the Assured Forwarding\n Per Hop Behavior (AF PHB). They are especially useful when a TCM is\n used to mark traffic composed of a small number of TCP connections.\n\n1. Introduction\n\n In DiffServ networks [RFC2475], the incoming data traffic, with the\n AF PHB in particular, could be subject to marking wher 2963 presentation subject nested-reference unchanged"},{"id":"IETF RFC 6789","type":"specification","body":"IETF","designation":"RFC 6789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6789.txt","https://www.rfc-editor.org/rfc/rfc6789.pdf"],"folder":"IETF/RFC-6789","files":{"txt":{"path":"standards/IETF/RFC-6789/RFC-6789.txt","sha256":"e552ac69fbb64a49fdf1e0656837206c05e765356fd9af5b681f204c55718a74"}},"tags":["nested-reference","unchanged"],"summary":"This document provides the entry point to the set of documentation\n about the Congestion Exposure (ConEx) protocol. It explains the\n motivation for including a ConEx marking at the IP layer: to expose\n information about congestion to network nodes. Although such\n information may have a number of uses, this document focuses on how\n the information communicated by the ConEx marking can serve as the\n basis for significantly more efficient and effective traffic\n management than what exists on the Internet today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not a","scope_keywords":["6789","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7141","folder":"IETF/RFC-7141","source":"IETF/RFC-7141/RFC-7141.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7713","folder":"IETF/RFC-7713","source":"IETF/RFC-7713/RFC-7713.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null}],"search_text":"IETF RFC 6789 This document provides the entry point to the set of documentation\n about the Congestion Exposure (ConEx) protocol. It explains the\n motivation for including a ConEx marking at the IP layer: to expose\n information about congestion to network nodes. Although such\n information may have a number of uses, this document focuses on how\n the information communicated by the ConEx marking can serve as the\n basis for significantly more efficient and effective traffic\n management than what exists on the Internet today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not a 6789 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 2485","type":"specification","body":"IETF","designation":"RFC 2485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2485.txt","https://www.rfc-editor.org/rfc/rfc2485.pdf"],"folder":"IETF/RFC-2485","files":{"txt":{"path":"standards/IETF/RFC-2485/RFC-2485.txt","sha256":"a91036aa9899513dd16ad4f84d342bcbf470d0e08c2aba3a9e9af2c53df82497"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a DHCP [1] option that contains a list of\n pointers to User Authentication Protocol servers that provide user\n authentication services for clients that conform to The Open Group\n Network Computing Client Technical Standard [2].","scope_keywords":["2485","authentication","http","https","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2485 This document defines a DHCP [1] option that contains a list of\n pointers to User Authentication Protocol servers that provide user\n authentication services for clients that conform to The Open Group\n Network Computing Client Technical Standard [2]. 2485 authentication http https path nested-reference unchanged"},{"id":"IETF RFC 5033","type":"specification","body":"IETF","designation":"RFC 5033","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5033.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5033.txt","https://www.rfc-editor.org/rfc/rfc5033.pdf"],"folder":"IETF/RFC-5033","files":{"txt":{"path":"standards/IETF/RFC-5033/RFC-5033.txt","sha256":"d8a86f1198e1e0fade7a21d662b7a071e52fa21a83f93517e9076fc53799ece0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Floyd\nRequest for Comments: 5033 M. Allman\nBCP: 133 ICIR / ICSI\nCategory: Best Current Practice August 2007\n\n Specifying New Congestion Control Algorithms\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n The IETF's standard congestion control schemes have been widely shown\n to be inadequate for various environments (e.g., high-speed\n networks). Recent research has yielded many alternate congestion\n control schemes that significantly differ from the IETF's congestion\n control principles. Using these new congestion control schemes in\n the global Internet has possible ramifications to both the traffic\n using the new congestion control and to traffic using the currently\n standardized congestion co","scope_keywords":["5033","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null}],"search_text":"IETF RFC 5033 Network Working Group S. Floyd\nRequest for Comments: 5033 M. Allman\nBCP: 133 ICIR / ICSI\nCategory: Best Current Practice August 2007\n\n Specifying New Congestion Control Algorithms\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nAbstract\n\n The IETF's standard congestion control schemes have been widely shown\n to be inadequate for various environments (e.g., high-speed\n networks). Recent research has yielded many alternate congestion\n control schemes that significantly differ from the IETF's congestion\n control principles. Using these new congestion control schemes in\n the global Internet has possible ramifications to both the traffic\n using the new congestion control and to traffic using the currently\n standardized congestion co 5033 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 3593","type":"specification","body":"IETF","designation":"RFC 3593","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3593.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3593.txt","https://www.rfc-editor.org/rfc/rfc3593.pdf"],"folder":"IETF/RFC-3593","files":{"txt":{"path":"standards/IETF/RFC-3593/RFC-3593.txt","sha256":"6314e5c578868275ff83246d3899f7ed4f46a1276cad759a1afc973fa6cce4f8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a set of Textual Conventions for MIB modules\n that make use of performance history data based on 15 minute\n intervals.\n\n This memo replaces RFC 2493. Changes relative to RFC 2493 are\n summarized in the MIB module's REVISION clause.","scope_keywords":["3593","http","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3705","folder":"IETF/RFC-3705","source":"IETF/RFC-3705/RFC-3705.txt","version":null},{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 4181","folder":"IETF/RFC-4181","source":"IETF/RFC-4181/RFC-4181.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5601","folder":"IETF/RFC-5601","source":"IETF/RFC-5601/RFC-5601.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"IETF RFC 3593 This document defines a set of Textual Conventions for MIB modules\n that make use of performance history data based on 15 minute\n intervals.\n\n This memo replaces RFC 2493. Changes relative to RFC 2493 are\n summarized in the MIB module's REVISION clause. 3593 http management policy nested-reference unchanged"},{"id":"IETF RFC 2534","type":"specification","body":"IETF","designation":"RFC 2534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2534.txt","https://www.rfc-editor.org/rfc/rfc2534.pdf"],"folder":"IETF/RFC-2534","files":{"txt":{"path":"standards/IETF/RFC-2534/RFC-2534.txt","sha256":"42b9d98f0850de8493a3a5df145c98b301f632a94a9f218bf6bbd64086b8bdb8"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines some common media features for describing\n image resolution, size, color, and image representation methods that\n are common to web browsing, printing, and facsimile applications.\n These features are registered for use within the framework of [REG].\n\n1. Introduction\n\n This work was originally motivated by the requirements from web\n browsers to send the browser's display characteristics to the web\n server to allow the server to choose an appropriate representation.\n\n This specification defines some common media features [REG] by which\n a recipient may inform a sender as to the characteristics of its\n message handling. The sender may then provide the variant of the\n message that is most suitable for the recipient.\n\n Different variants would typically be higher or lower resolution\n images (for example) as appropriate. In the case of a sending to a\n printer, the res","scope_keywords":["2534","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2506","folder":"IETF/RFC-2506","source":"IETF/RFC-2506/RFC-2506.txt","version":null},{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2533","folder":"IETF/RFC-2533","source":"IETF/RFC-2533/RFC-2533.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4142","folder":"IETF/RFC-4142","source":"IETF/RFC-4142/RFC-4142.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null}],"search_text":"IETF RFC 2534 This specification defines some common media features for describing\n image resolution, size, color, and image representation methods that\n are common to web browsing, printing, and facsimile applications.\n These features are registered for use within the framework of [REG].\n\n1. Introduction\n\n This work was originally motivated by the requirements from web\n browsers to send the browser's display characteristics to the web\n server to allow the server to choose an appropriate representation.\n\n This specification defines some common media features [REG] by which\n a recipient may inform a sender as to the characteristics of its\n message handling. The sender may then provide the variant of the\n message that is most suitable for the recipient.\n\n Different variants would typically be higher or lower resolution\n images (for example) as appropriate. In the case of a sending to a\n printer, the res 2534 presentation registered nested-reference unchanged"},{"id":"IETF RFC 2880","type":"specification","body":"IETF","designation":"RFC 2880","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2880.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2880.txt","https://www.rfc-editor.org/rfc/rfc2880.pdf"],"folder":"IETF/RFC-2880","files":{"txt":{"path":"standards/IETF/RFC-2880/RFC-2880.txt","sha256":"aa062a149c40bd7e90fdbcb5deb813d8bf70cefcbb29da9b92548f991d06b88d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to map Group 3 fax capability\n identification bits, described in ITU T.30 [6], into the Internet fax\n feature schema described in \"Content feature schema for Internet fax\"\n [4].\n\n This is a companion to the fax feature schema document [4], which\n itself defines a profile of the media feature registration mechanisms\n [1,2,3], for use in performing capability identification between\n extended Internet fax systems [5].","scope_keywords":["2880","http","identification","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null}],"search_text":"IETF RFC 2880 This document describes how to map Group 3 fax capability\n identification bits, described in ITU T.30 [6], into the Internet fax\n feature schema described in \"Content feature schema for Internet fax\"\n [4].\n\n This is a companion to the fax feature schema document [4], which\n itself defines a profile of the media feature registration mechanisms\n [1,2,3], for use in performing capability identification between\n extended Internet fax systems [5]. 2880 http identification profile nested-reference unchanged"},{"id":"IETF RFC 252","type":"specification","body":"IETF","designation":"RFC 252","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc252.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc252.txt","https://www.rfc-editor.org/rfc/rfc252.pdf"],"folder":"IETF/RFC-252","files":{"txt":{"path":"standards/IETF/RFC-252/RFC-252.txt","sha256":"7d281bb310b00ddd5da70cb52f722365cb1e3b679e09054e2970dd95f9824b08"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Wentheimer\nRequest for Comments: 252 Bolt, Beranek and Newman\nCategory: F, G.3 8 October 1971\nNIC: 7696\n\n The purpose of this RFC is to report on the recent status of most\n Network Hosts. During September 27 through September 29 the BBN\n prototype Terminal IMP (Network Address 158) was inaccessible due to\n hardware debugging. The Network was, therefore, not examined on\n these days.\n\n Three Hosts which were not officially able to act as Server's at the\n time of RFC #240 are now able to do so. These Hosts are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n 2 SRI (NIC) PDF-10\n 6 MIT (Multics) H-645\n 9 HARVARD PDP-10\n\n The Harvard PDP-10, however, has limited core space. They will,\n therefore, run the Telnet program only occasionally.\n\n The following two tables summarize the information on the Host status\n for September 30 - October 8.\n\n NETWORK SITE COMPUTER DAY, DATE AND TIME (","scope_keywords":["252"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 252 Network Working Group E. Wentheimer\nRequest for Comments: 252 Bolt, Beranek and Newman\nCategory: F, G.3 8 October 1971\nNIC: 7696\n\n The purpose of this RFC is to report on the recent status of most\n Network Hosts. During September 27 through September 29 the BBN\n prototype Terminal IMP (Network Address 158) was inaccessible due to\n hardware debugging. The Network was, therefore, not examined on\n these days.\n\n Three Hosts which were not officially able to act as Server's at the\n time of RFC #240 are now able to do so. These Hosts are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n 2 SRI (NIC) PDF-10\n 6 MIT (Multics) H-645\n 9 HARVARD PDP-10\n\n The Harvard PDP-10, however, has limited core space. They will,\n therefore, run the Telnet program only occasionally.\n\n The following two tables summarize the information on the Host status\n for September 30 - October 8.\n\n NETWORK SITE COMPUTER DAY, DATE AND TIME ( 252 nested-reference unchanged"},{"id":"IETF RFC 2520","type":"specification","body":"IETF","designation":"RFC 2520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2520.txt","https://www.rfc-editor.org/rfc/rfc2520.pdf"],"folder":"IETF/RFC-2520","files":{"txt":{"path":"standards/IETF/RFC-2520/RFC-2520.txt","sha256":"154dd3e34c9cba6e2cd9e0442dc19b4e35ff5b6c03403c71fc0096b62c9c4647"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension to NHRP [1] which would allow\n Mobile NHCs to perform a registration with and attach to an NHS in\n their home LIS in an authenticated manner.\n\n As described in this document, Mobile NHCs are NHCs which are not\n configured with enough information to find a specific serving NHS in\n their home LIS, but which have a mechanism to find an NHS (which may\n or may not be a serving NHS) to which they will attach. As described\n in [1], an NHC may attach to a 'surrogate' NHS by using a mechanism\n such as an anycast address. In this case, the NHC may use the\n surrogate NHS to send a NHRP Registration Request toward the NHC's\n home LIS where a serving NHS resides. However, as defined in [1],\n packet authentication is performed on a hop by hop basis. In the\n mobile NHC case, it is not practical for the mobile NHC be in a\n security relationship with every surrogate N","scope_keywords":["2520","algorithm","authentication","hash","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2520 This document describes an extension to NHRP [1] which would allow\n Mobile NHCs to perform a registration with and attach to an NHS in\n their home LIS in an authenticated manner.\n\n As described in this document, Mobile NHCs are NHCs which are not\n configured with enough information to find a specific serving NHS in\n their home LIS, but which have a mechanism to find an NHS (which may\n or may not be a serving NHS) to which they will attach. As described\n in [1], an NHC may attach to a 'surrogate' NHS by using a mechanism\n such as an anycast address. In this case, the NHC may use the\n surrogate NHS to send a NHRP Registration Request toward the NHC's\n home LIS where a serving NHS resides. However, as defined in [1],\n packet authentication is performed on a hop by hop basis. In the\n mobile NHC case, it is not practical for the mobile NHC be in a\n security relationship with every surrogate N 2520 algorithm authentication hash key keys management nested-reference unchanged"},{"id":"IETF RFC 2521","type":"specification","body":"IETF","designation":"RFC 2521","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2521.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2521.txt","https://www.rfc-editor.org/rfc/rfc2521.pdf"],"folder":"IETF/RFC-2521","files":{"txt":{"path":"standards/IETF/RFC-2521/RFC-2521.txt","sha256":"55799ec326f7de33f936716bb170eb3ec77aaf078f3a042bee1eb544d31832ab"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies ICMP messages for indicating failures when\n using IP Security Protocols (AH and ESP).\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2521 ICMP Security Failures March 1999","scope_keywords":["2521","authentication","authorization","encryption","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null}],"search_text":"IETF RFC 2521 This document specifies ICMP messages for indicating failures when\n using IP Security Protocols (AH and ESP).\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2521 ICMP Security Failures March 1999 2521 authentication authorization encryption key management nested-reference unchanged"},{"id":"IETF RFC 2523","type":"specification","body":"IETF","designation":"RFC 2523","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2523.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2523.txt","https://www.rfc-editor.org/rfc/rfc2523.pdf"],"folder":"IETF/RFC-2523","files":{"txt":{"path":"standards/IETF/RFC-2523/RFC-2523.txt","sha256":"67197e87e4f4895ef3a80cc48a7beb9c558c9e65488603030c0fdab4e9a05cc8"}},"tags":["nested-reference","unchanged"],"summary":"Photuris is a session-key management protocol. Extensible Exchange-\n Schemes are provided to enable future implementation changes without\n affecting the basic protocol.\n\n Additional authentication attributes are included for use with the IP\n Authentication Header (AH) or the IP Encapsulating Security Protocol\n (ESP).\n\n Additional confidentiality attributes are included for use with ESP.\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2523 Schemes and Attributes March 1999","scope_keywords":["2523","attribute","attributes","authentication","encryption","hash","identification","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2523 Photuris is a session-key management protocol. Extensible Exchange-\n Schemes are provided to enable future implementation changes without\n affecting the basic protocol.\n\n Additional authentication attributes are included for use with the IP\n Authentication Header (AH) or the IP Encapsulating Security Protocol\n (ESP).\n\n Additional confidentiality attributes are included for use with ESP.\n\nKarn & Simpson Experimental [Page i]\n\f\nRFC 2523 Schemes and Attributes March 1999 2523 attribute attributes authentication encryption hash identification key management nested-reference unchanged"},{"id":"IETF RFC 2785","type":"specification","body":"IETF","designation":"RFC 2785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2785.txt","https://www.rfc-editor.org/rfc/rfc2785.pdf"],"folder":"IETF/RFC-2785","files":{"txt":{"path":"standards/IETF/RFC-2785/RFC-2785.txt","sha256":"4d6d6284a7a18298319a6313ad859ff7c4629054e6b46839d683d99a37480eb9"}},"tags":["nested-reference","unchanged"],"summary":"In some circumstances the use of the Diffie-Hellman key agreement\n scheme in a prime order subgroup of a large prime p is vulnerable to\n certain attacks known as \"small-subgroup\" attacks. Methods exist,\n however, to prevent these attacks. This document will describe the\n situations relevant to implementations of S/MIME version 3 in which\n protection is necessary and the methods that can be used to prevent\n these attacks.\n\n1. Introduction\n\n This document will describe those situations in which protection from\n \"small-subgroup\" type attacks is necessary when using Diffie-Hellman\n key agreement [RFC2631] in implementations of S/MIME version 3\n [RFC2630, RFC2633]. Thus, the ephemeral-static and static-static\n modes of Diffie-Hellman will be focused on. Some possible non-S/MIME\n usages of CMS are also considered, though with less emphasis than the\n cases arising in S/MIME. The situations for ","scope_keywords":["2785","algorithm","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5272","folder":"IETF/RFC-5272","source":"IETF/RFC-5272/RFC-5272.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 2785 In some circumstances the use of the Diffie-Hellman key agreement\n scheme in a prime order subgroup of a large prime p is vulnerable to\n certain attacks known as \"small-subgroup\" attacks. Methods exist,\n however, to prevent these attacks. This document will describe the\n situations relevant to implementations of S/MIME version 3 in which\n protection is necessary and the methods that can be used to prevent\n these attacks.\n\n1. Introduction\n\n This document will describe those situations in which protection from\n \"small-subgroup\" type attacks is necessary when using Diffie-Hellman\n key agreement [RFC2631] in implementations of S/MIME version 3\n [RFC2630, RFC2633]. Thus, the ephemeral-static and static-static\n modes of Diffie-Hellman will be focused on. Some possible non-S/MIME\n usages of CMS are also considered, though with less emphasis than the\n cases arising in S/MIME. The situations for  2785 algorithm key trust nested-reference unchanged"},{"id":"IETF RFC 6841","type":"specification","body":"IETF","designation":"RFC 6841","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6841.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6841.txt","https://www.rfc-editor.org/rfc/rfc6841.pdf"],"folder":"IETF/RFC-6841","files":{"txt":{"path":"standards/IETF/RFC-6841/RFC-6841.txt","sha256":"23a5023d37f4df96a2bb47e2b17a67a016aecf4f3f6ed7be27321f3dbfc8cff3"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a framework to assist writers of DNS Security\n Extensions (DNSSEC) Policies and DNSSEC Practice Statements, such as\n domain managers and zone operators on both the top level and\n secondary level, who are managing and operating a DNS zone with\n Security Extensions implemented.\n\n In particular, the framework provides a comprehensive list of topics\n that should be considered for inclusion into a DNSSEC Policy\n definition and Practice Statement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a cand","scope_keywords":["6841","audit","authentication","certificate","holder","http","key","license","management","pki","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 6841 This document presents a framework to assist writers of DNS Security\n Extensions (DNSSEC) Policies and DNSSEC Practice Statements, such as\n domain managers and zone operators on both the top level and\n secondary level, who are managing and operating a DNS zone with\n Security Extensions implemented.\n\n In particular, the framework provides a comprehensive list of topics\n that should be considered for inclusion into a DNSSEC Policy\n definition and Practice Statement.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a cand 6841 audit authentication certificate holder http key license management pki policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6169","type":"specification","body":"IETF","designation":"RFC 6169","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6169.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6169.txt","https://www.rfc-editor.org/rfc/rfc6169.pdf"],"folder":"IETF/RFC-6169","files":{"txt":{"path":"standards/IETF/RFC-6169/RFC-6169.txt","sha256":"37031cb283d73bc77253e3b65e62df50b9353728582c4755d8ea9bac147ab961"}},"tags":["nested-reference","unchanged"],"summary":"A number of security concerns with IP tunnels are documented in this\n memo. The intended audience of this document includes network\n administrators and future protocol developers. The primary intent of\n this document is to raise the awareness level regarding the security\n issues with IP tunnels as deployed and propose strategies for the\n mitigation of those issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current","scope_keywords":["6169","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6127","folder":"IETF/RFC-6127","source":"IETF/RFC-6127/RFC-6127.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6264","folder":"IETF/RFC-6264","source":"IETF/RFC-6264/RFC-6264.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null}],"search_text":"IETF RFC 6169 A number of security concerns with IP tunnels are documented in this\n memo. The intended audience of this document includes network\n administrators and future protocol developers. The primary intent of\n this document is to raise the awareness level regarding the security\n issues with IP tunnels as deployed and propose strategies for the\n mitigation of those issues.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current 6169 http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6264","type":"specification","body":"IETF","designation":"RFC 6264","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6264.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6264.txt","https://www.rfc-editor.org/rfc/rfc6264.pdf"],"folder":"IETF/RFC-6264","files":{"txt":{"path":"standards/IETF/RFC-6264/RFC-6264.txt","sha256":"011bc7d967d4bf3c8f171aac2d5a2e19befd9fe27cb72d57d3284907c6fe2ebc"}},"tags":["nested-reference","unchanged"],"summary":"Global IPv6 deployment was slower than originally expected. As IPv4\n address exhaustion approaches, IPv4 to IPv6 transition issues become\n more critical and less tractable. Host-based transition mechanisms\n used in dual-stack environments cannot meet all transition\n requirements. Most end users are not sufficiently expert to\n configure or maintain host-based transition mechanisms. Carrier-\n Grade NAT (CGN) devices with integrated transition mechanisms can\n reduce the operational changes required during the IPv4 to IPv6\n migration or coexistence period.\n\n This document proposes an incremental CGN approach for IPv6\n transition. It can provide IPv6 access services for IPv6 hosts and\n IPv4 access services for IPv4 hosts while leaving much of a legacy\n ISP network unchanged during the initial stage of IPv4 to IPv6\n migration. Unlike CGN alone, incremental CGN also supports and\n encourages smo","scope_keywords":["6264","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6598","folder":"IETF/RFC-6598","source":"IETF/RFC-6598/RFC-6598.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null}],"search_text":"IETF RFC 6264 Global IPv6 deployment was slower than originally expected. As IPv4\n address exhaustion approaches, IPv4 to IPv6 transition issues become\n more critical and less tractable. Host-based transition mechanisms\n used in dual-stack environments cannot meet all transition\n requirements. Most end users are not sufficiently expert to\n configure or maintain host-based transition mechanisms. Carrier-\n Grade NAT (CGN) devices with integrated transition mechanisms can\n reduce the operational changes required during the IPv4 to IPv6\n migration or coexistence period.\n\n This document proposes an incremental CGN approach for IPv6\n transition. It can provide IPv6 access services for IPv6 hosts and\n IPv4 access services for IPv4 hosts while leaving much of a legacy\n ISP network unchanged during the initial stage of IPv4 to IPv6\n migration. Unlike CGN alone, incremental CGN also supports and\n encourages smo 6264 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 254","type":"specification","body":"IETF","designation":"RFC 254","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc254.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc254.txt","https://www.rfc-editor.org/rfc/rfc254.pdf"],"folder":"IETF/RFC-254","files":{"pdf":{"path":"standards/IETF/RFC-254/RFC-254.pdf","sha256":"bedb2233b77cf7eea6e1ab5b7738da8c77b84a52a8552cebcdb680b6bceb0880"},"txt":{"path":"standards/IETF/RFC-254/RFC-254.txt","sha256":"5792cb7d4a3d2fbc72fc1cb32b152aae6a485b617cd75919d150366320198a6a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. K. Bhushan\nRequest for Comments: 254 MIT Project MAC\nNIC: 7695 October 1971\n\n SCENARIOS FOR USING ARPANET COMPUTERS\n\n This scenario booklet is provided to facilitate the use of ARPANET\n host computer systems via the ARPANET. The objective of these\n scenarios is to aid a user in sampling host computers on the ARPANET,\n thereby stimulating this interest in using ARPANET.\n\n The scenarios describe the login procedure, the use of some simple or\n interesting facilities, and obtaining on-line help facilities such as\n on-line documentation and interactive dialog with experienced users\n via \"link\" or \"message\" type mechanisms. The use of TELNETS for\n \"piggy-back login\" is included to help system programmers in\n debugging and testing their protocol implementations. An exercise of\n editing and running a very simple program is also included, where\n appropriate.\n\n The scenari","scope_keywords":["254"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 308","folder":"IETF/RFC-308","source":"IETF/RFC-308/RFC-308.txt","version":null}],"search_text":"IETF RFC 254 Network Working Group A. K. Bhushan\nRequest for Comments: 254 MIT Project MAC\nNIC: 7695 October 1971\n\n SCENARIOS FOR USING ARPANET COMPUTERS\n\n This scenario booklet is provided to facilitate the use of ARPANET\n host computer systems via the ARPANET. The objective of these\n scenarios is to aid a user in sampling host computers on the ARPANET,\n thereby stimulating this interest in using ARPANET.\n\n The scenarios describe the login procedure, the use of some simple or\n interesting facilities, and obtaining on-line help facilities such as\n on-line documentation and interactive dialog with experienced users\n via \"link\" or \"message\" type mechanisms. The use of TELNETS for\n \"piggy-back login\" is included to help system programmers in\n debugging and testing their protocol implementations. An exercise of\n editing and running a very simple program is also included, where\n appropriate.\n\n The scenari 254 nested-reference unchanged"},{"id":"IETF RFC 308","type":"specification","body":"IETF","designation":"RFC 308","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc308.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc308.txt","https://www.rfc-editor.org/rfc/rfc308.pdf"],"folder":"IETF/RFC-308","files":{"txt":{"path":"standards/IETF/RFC-308/RFC-308.txt","sha256":"b80f0c669235893d24c092444ac964f4ed52ef59d20c43bc907eff3e293d59f7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Marc Seriff\nRequest for Comments 308 MIT-DMCG\nNIC 9259 13 MARCH 1972\nReferences: RFC 254\n\n ARPANET HOST AVAILABILITY DATA\n\n Several months ago a SURVEY program was implemented on the\nMIT-DMCG ITS PDP-10 system to aid in gathering information on the\navailability of various HOSTS on the ARPANET. The purpose of this\nRequest for Comments is threefold:\n\n 1. to inform the Network Working Group of the\n existence of this information gathering service\n and about getting access to it,\n\n 2. to present the results of SURVEY for its first\n few months, and\n\n 3. to correct errors in our data or collection methods.\n\n Briefly, the SURVEY program works as follows: At 15-minute\nintervals whenever the MIT-DMCG ITS Time-Sharing system is in normal\noperation, a SURVEY is started. The SURVEY program attempts to\nestablish a connection to the LOGGER (socket 1) of each HOST listed in\nits tab","scope_keywords":["308"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 530","folder":"IETF/RFC-530","source":"IETF/RFC-530/RFC-530.pdf","version":null}],"search_text":"IETF RFC 308 Network Working Group Marc Seriff\nRequest for Comments 308 MIT-DMCG\nNIC 9259 13 MARCH 1972\nReferences: RFC 254\n\n ARPANET HOST AVAILABILITY DATA\n\n Several months ago a SURVEY program was implemented on the\nMIT-DMCG ITS PDP-10 system to aid in gathering information on the\navailability of various HOSTS on the ARPANET. The purpose of this\nRequest for Comments is threefold:\n\n 1. to inform the Network Working Group of the\n existence of this information gathering service\n and about getting access to it,\n\n 2. to present the results of SURVEY for its first\n few months, and\n\n 3. to correct errors in our data or collection methods.\n\n Briefly, the SURVEY program works as follows: At 15-minute\nintervals whenever the MIT-DMCG ITS Time-Sharing system is in normal\noperation, a SURVEY is started. The SURVEY program attempts to\nestablish a connection to the LOGGER (socket 1) of each HOST listed in\nits tab 308 nested-reference unchanged"},{"id":"IETF RFC 2824","type":"specification","body":"IETF","designation":"RFC 2824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2824.txt","https://www.rfc-editor.org/rfc/rfc2824.pdf"],"folder":"IETF/RFC-2824","files":{"txt":{"path":"standards/IETF/RFC-2824/RFC-2824.txt","sha256":"59899ab4f94e2345f4a8fd4c3d45cf7f246bf4973a21d7d5aff6ca49d6a9278a"}},"tags":["nested-reference","unchanged"],"summary":"A large number of the services we wish to make possible for Internet\n telephony require fairly elaborate combinations of signalling\n operations, often in network devices, to complete. We want a simple\n and standardized way to create such services to make them easier to\n implement and deploy. This document describes an architectural\n framework for such a mechanism, which we call a call processing\n language. It also outlines requirements for such a language.","scope_keywords":["2824"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null}],"search_text":"IETF RFC 2824 A large number of the services we wish to make possible for Internet\n telephony require fairly elaborate combinations of signalling\n operations, often in network devices, to complete. We want a simple\n and standardized way to create such services to make them easier to\n implement and deploy. This document describes an architectural\n framework for such a mechanism, which we call a call processing\n language. It also outlines requirements for such a language. 2824 nested-reference unchanged"},{"id":"IETF RFC 2976","type":"specification","body":"IETF","designation":"RFC 2976","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2976.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2976.txt","https://www.rfc-editor.org/rfc/rfc2976.pdf"],"folder":"IETF/RFC-2976","files":{"txt":{"path":"standards/IETF/RFC-2976/RFC-2976.txt","sha256":"c55b07340e32046a0cc0b45c85c53e29aee31f4b0434dc479e6ddcc8574611b2"}},"tags":["nested-reference","unchanged"],"summary":"This document proposes an extension to the Session Initiation\n Protocol (SIP). This extension adds the INFO method to the SIP\n protocol. The intent of the INFO method is to allow for the carrying\n of session related control information that is generated during a\n session. One example of such session control information is ISUP and\n ISDN signaling messages used to control telephony call services.\n\n This and other example uses of the INFO method may be standardized in\n the future.","scope_keywords":["2976","authorization","encryption","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3313","folder":"IETF/RFC-3313","source":"IETF/RFC-3313/RFC-3313.txt","version":null},{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 2976 This document proposes an extension to the Session Initiation\n Protocol (SIP). This extension adds the INFO method to the SIP\n protocol. The intent of the INFO method is to allow for the carrying\n of session related control information that is generated during a\n session. One example of such session control information is ISUP and\n ISDN signaling messages used to control telephony call services.\n\n This and other example uses of the INFO method may be standardized in\n the future. 2976 authorization encryption path nested-reference unchanged"},{"id":"IETF RFC 3087","type":"specification","body":"IETF","designation":"RFC 3087","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3087.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3087.txt","https://www.rfc-editor.org/rfc/rfc3087.pdf"],"folder":"IETF/RFC-3087","files":{"txt":{"path":"standards/IETF/RFC-3087/RFC-3087.txt","sha256":"b2b40fdc67d2720105309f94a8db73be76eb58fe8c2168dae7c1b7281018eae6"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides information for the Internet community. It\n describes a useful way to conceptualize the use of the standard SIP\n (Session Initiation Protocol) Request-URI (Uniform Resource\n Identifier) that the authors and many members of the SIP community\n think is suitable as a convention. It does not define any new\n protocol with respect to RFC 2543.\n\n In a conventional telephony environment, extended service\n applications often use call state information, such as calling party,\n called party, reason for forward, etc, to infer application context.\n In a SIP/2.0 call, much of this information may be either non-\n existent or unreliable. This document proposes a mechanism to\n communicate context information to an application. Under this\n proposal, a client or proxy can communicate context through the use\n of a distinctive Request-URI. This document continues with examples\n of how this","scope_keywords":["3087","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null}],"search_text":"IETF RFC 3087 This memo provides information for the Internet community. It\n describes a useful way to conceptualize the use of the standard SIP\n (Session Initiation Protocol) Request-URI (Uniform Resource\n Identifier) that the authors and many members of the SIP community\n think is suitable as a convention. It does not define any new\n protocol with respect to RFC 2543.\n\n In a conventional telephony environment, extended service\n applications often use call state information, such as calling party,\n called party, reason for forward, etc, to infer application context.\n In a SIP/2.0 call, much of this information may be either non-\n existent or unreliable. This document proposes a mechanism to\n communicate context information to an application. Under this\n proposal, a client or proxy can communicate context through the use\n of a distinctive Request-URI. This document continues with examples\n of how this 3087 trust nested-reference unchanged"},{"id":"IETF RFC 4475","type":"specification","body":"IETF","designation":"RFC 4475","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4475.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4475.txt","https://www.rfc-editor.org/rfc/rfc4475.pdf"],"folder":"IETF/RFC-4475","files":{"txt":{"path":"standards/IETF/RFC-4475/RFC-4475.txt","sha256":"ab5fbd8c6d266b19988760183c57b4fbacbd0b23be7ac0710a8ddf4be6c3005b"}},"tags":["nested-reference","unchanged"],"summary":"This informational document gives examples of Session Initiation\n Protocol (SIP) test messages designed to exercise and \"torture\" a SIP\n implementation.","scope_keywords":["4475","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4474","folder":"IETF/RFC-4474","source":"IETF/RFC-4474/RFC-4474.txt","version":null},{"body":"IETF","designation":"RFC 4488","folder":"IETF/RFC-4488","source":"IETF/RFC-4488/RFC-4488.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 5118","folder":"IETF/RFC-5118","source":"IETF/RFC-5118/RFC-5118.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5628","folder":"IETF/RFC-5628","source":"IETF/RFC-5628/RFC-5628.txt","version":null},{"body":"IETF","designation":"RFC 6189","folder":"IETF/RFC-6189","source":"IETF/RFC-6189/RFC-6189.txt","version":null},{"body":"IETF","designation":"RFC 6873","folder":"IETF/RFC-6873","source":"IETF/RFC-6873/RFC-6873.txt","version":null},{"body":"IETF","designation":"RFC 7997","folder":"IETF/RFC-7997","source":"IETF/RFC-7997/RFC-7997.txt","version":null}],"search_text":"IETF RFC 4475 This informational document gives examples of Session Initiation\n Protocol (SIP) test messages designed to exercise and \"torture\" a SIP\n implementation. 4475 authorization nested-reference unchanged"},{"id":"IETF RFC 25434","type":"specification","body":"IETF","designation":"RFC 25434","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc25434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc25434.txt","https://www.rfc-editor.org/rfc/rfc25434.pdf"],"folder":"IETF/RFC-25434","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null}],"search_text":"IETF RFC 25434 nested-reference unavailable"},{"id":"IETF RFC 4029","type":"specification","body":"IETF","designation":"RFC 4029","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4029.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4029.txt","https://www.rfc-editor.org/rfc/rfc4029.pdf"],"folder":"IETF/RFC-4029","files":{"txt":{"path":"standards/IETF/RFC-4029/RFC-4029.txt","sha256":"d787665ec7d549fa06f4d6a543305d6543bd6aa133580e93360accd324bf20eb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes different scenarios for the introduction of\n IPv6 into an ISP's existing IPv4 network without disrupting the IPv4\n service. The scenarios for introducing IPv6 are analyzed, and the\n relevance of already defined transition mechanisms are evaluated.\n Known challenges are also identified.","scope_keywords":["4029","authentication","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 4779","folder":"IETF/RFC-4779","source":"IETF/RFC-4779/RFC-4779.txt","version":null},{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 4852","folder":"IETF/RFC-4852","source":"IETF/RFC-4852/RFC-4852.txt","version":null},{"body":"IETF","designation":"RFC 4942","folder":"IETF/RFC-4942","source":"IETF/RFC-4942/RFC-4942.txt","version":null},{"body":"IETF","designation":"RFC 6036","folder":"IETF/RFC-6036","source":"IETF/RFC-6036/RFC-6036.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 4029 This document describes different scenarios for the introduction of\n IPv6 into an ISP's existing IPv4 network without disrupting the IPv4\n service. The scenarios for introducing IPv6 are analyzed, and the\n relevance of already defined transition mechanisms are evaluated.\n Known challenges are also identified. 4029 authentication identification management nested-reference unchanged"},{"id":"IETF RFC 2550","type":"specification","body":"IETF","designation":"RFC 2550","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2550.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2550.txt","https://www.rfc-editor.org/rfc/rfc2550.pdf"],"folder":"IETF/RFC-2550","files":{"txt":{"path":"standards/IETF/RFC-2550/RFC-2550.txt","sha256":"10e9e6e319dde34cc7ef3fea2755c14073f68a938ae0733d3e07d3c7e6048550"}},"tags":["nested-reference","unchanged"],"summary":"As we approach the end of the millennium, much attention has been\n paid to the so-called \"Y2K\" problem. Nearly everyone now regrets the\n short-sightedness of the programmers of yore who wrote programs\n designed to fail in the year 2000. Unfortunately, the current fixes\n for Y2K lead inevitably to a crisis in the year 10,000 when the\n programs are again designed to fail.\n\n This specification provides a solution to the \"Y10K\" problem which\n has also been called the \"YAK\" problem (hex) and the \"YXK\" problem\n (Roman numerals).\n\n1. Introduction, Discussion, and Related Work\n\n Many programs and standards contain, manipulate and maintain dates.\n Comparing and sorting dates is a common activity. Many different\n formats and standards for dates have been developed and all have been\n found wanting.\n\n Early date formats reserved only two digits to represent the year\n portion of a date. Programs that","scope_keywords":["2550","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2795","folder":"IETF/RFC-2795","source":"IETF/RFC-2795/RFC-2795.txt","version":null}],"search_text":"IETF RFC 2550 As we approach the end of the millennium, much attention has been\n paid to the so-called \"Y2K\" problem. Nearly everyone now regrets the\n short-sightedness of the programmers of yore who wrote programs\n designed to fail in the year 2000. Unfortunately, the current fixes\n for Y2K lead inevitably to a crisis in the year 10,000 when the\n programs are again designed to fail.\n\n This specification provides a solution to the \"Y10K\" problem which\n has also been called the \"YAK\" problem (hex) and the \"YXK\" problem\n (Roman numerals).\n\n1. Introduction, Discussion, and Related Work\n\n Many programs and standards contain, manipulate and maintain dates.\n Comparing and sorting dates is a common activity. Many different\n formats and standards for dates have been developed and all have been\n found wanting.\n\n Early date formats reserved only two digits to represent the year\n portion of a date. Programs that 2550 presentation nested-reference unchanged"},{"id":"IETF RFC 6025","type":"specification","body":"IETF","designation":"RFC 6025","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6025.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6025.txt","https://www.rfc-editor.org/rfc/rfc6025.pdf"],"folder":"IETF/RFC-6025","files":{"txt":{"path":"standards/IETF/RFC-6025/RFC-6025.txt","sha256":"6b31b75d6f25aa9b084575ae9a442bed9be22cda09e0d7f21e2bb5faf09ac8a6"}},"tags":["nested-reference","unchanged"],"summary":"Abstract Syntax Notation One (ASN.1) is widely used throughout the\n IETF Security Area and has been for many years. Some specifications\n were written using a now deprecated version of ASN.1 and some were\n written using the current version of ASN.1. Not all ASN.1 compilers\n support both older and current syntax. This document is intended to\n provide guidance to specification authors and to implementers\n converting ASN.1 modules from one version of ASN.1 to another version\n without causing changes to the \"bits on the wire\". This document\n does not provide a comprehensive tutorial of any version of ASN.1.\n Instead, it addresses ASN.1 features that are used in IETF Security\n Area specifications with a focus on items that vary with the ASN.1\n version.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu","scope_keywords":["6025","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null}],"search_text":"IETF RFC 6025 Abstract Syntax Notation One (ASN.1) is widely used throughout the\n IETF Security Area and has been for many years. Some specifications\n were written using a now deprecated version of ASN.1 and some were\n written using the current version of ASN.1. Not all ASN.1 compilers\n support both older and current syntax. This document is intended to\n provide guidance to specification authors and to implementers\n converting ASN.1 modules from one version of ASN.1 to another version\n without causing changes to the \"bits on the wire\". This document\n does not provide a comprehensive tutorial of any version of ASN.1.\n Instead, it addresses ASN.1 features that are used in IETF Security\n Area specifications with a focus on items that vary with the ASN.1\n version.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu 6025 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6678","type":"specification","body":"IETF","designation":"RFC 6678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6678.txt","https://www.rfc-editor.org/rfc/rfc6678.pdf"],"folder":"IETF/RFC-6678","files":{"txt":{"path":"standards/IETF/RFC-6678/RFC-6678.txt","sha256":"e4f97c98eaeb581559de906f7d9e68ff85e0ce33c1b2b6a5e74de4fc101779ab"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the requirements for a tunnel-based Extensible\n Authentication Protocol (EAP) Method. This tunnel method will use\n Transport Layer Security (TLS) to establish a secure tunnel. The\n tunnel will provide support for password authentication, EAP\n authentication, and the transport of additional data for other\n purposes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any err","scope_keywords":["6678","algorithm","algorithms","attribute","attributes","authentication","certificate","http","key","license","revocation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7029","folder":"IETF/RFC-7029","source":"IETF/RFC-7029/RFC-7029.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null}],"search_text":"IETF RFC 6678 This memo defines the requirements for a tunnel-based Extensible\n Authentication Protocol (EAP) Method. This tunnel method will use\n Transport Layer Security (TLS) to establish a secure tunnel. The\n tunnel will provide support for password authentication, EAP\n authentication, and the transport of additional data for other\n purposes.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any err 6678 algorithm algorithms attribute attributes authentication certificate http key license revocation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 2561","type":"specification","body":"IETF","designation":"RFC 2561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2561.txt","https://www.rfc-editor.org/rfc/rfc2561.pdf"],"folder":"IETF/RFC-2561","files":{"txt":{"path":"standards/IETF/RFC-2561/RFC-2561.txt","sha256":"b567ded528ccc94648bfcabd8266e2001f7382e5a616488a07aa5fb0fc3eb1fb"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) for configuring\n and managing TN3270E servers. TN3270E, defined by RFC 2355 [19],\n refers to the enhancements made to the Telnet 3270 (TN3270) terminal\n emulation practices. Refer to RFC 1041 [18], STD 8, RFC 854 [16],\n and STD 31, RFC 860 [17] for a sample of what is meant by TN3270\n practices.\n\n The MIB defined by this memo provides generic support for both host\n and gateway TN3270E server implementations. A TN3270E server\n connects a Telnet client performing 3270 emulation to a target SNA\n host over both a client-side network (client to TN3270E server) and\n an SNA Network (TN3270E server to target SNA host). The client-side\n network is typically TCP/IP, but it need not be.\n\n A host TN3270E server refers to an implementation where the TN3270E\n server is collocated with the Systems Network Architecture (SNA)\n System Services Control ","scope_keywords":["2561","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2561 This memo defines a Management Information Base (MIB) for configuring\n and managing TN3270E servers. TN3270E, defined by RFC 2355 [19],\n refers to the enhancements made to the Telnet 3270 (TN3270) terminal\n emulation practices. Refer to RFC 1041 [18], STD 8, RFC 854 [16],\n and STD 31, RFC 860 [17] for a sample of what is meant by TN3270\n practices.\n\n The MIB defined by this memo provides generic support for both host\n and gateway TN3270E server implementations. A TN3270E server\n connects a Telnet client performing 3270 emulation to a target SNA\n host over both a client-side network (client to TN3270E server) and\n an SNA Network (TN3270E server to target SNA host). The client-side\n network is typically TCP/IP, but it need not be.\n\n A host TN3270E server refers to an implementation where the TN3270E\n server is collocated with the Systems Network Architecture (SNA)\n System Services Control  2561 key management nested-reference unchanged"},{"id":"IETF RFC 2562","type":"specification","body":"IETF","designation":"RFC 2562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2562.txt","https://www.rfc-editor.org/rfc/rfc2562.pdf"],"folder":"IETF/RFC-2562","files":{"txt":{"path":"standards/IETF/RFC-2562/RFC-2562.txt","sha256":"ea3fb71728c06a70cab8275df3f240f718cd8d7334674b274ccdb3f400338b8a"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines the protocol and the Management Information Base\n (MIB) for performing response time data collection on TN3270 and\n TN3270E sessions by a TN3270E server. The response time data\n collected by a TN3270E server is structured to support both\n validation of service level agreements and performance monitoring of\n TN3270 and TN3270E Sessions. This MIB has as a prerequisite the\n TN3270E-MIB, reference [20].\n\n TN3270E, defined by RFC 2355 [19], refers to the enhancements made to\n the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC\n 1041 [18], STD 8, RFC 854 [16], and STD 31, RFC 860 [17] for a sample\n of what is meant by TN3270 practices.","scope_keywords":["2562","key","management","timestamp","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2562 This memo defines the protocol and the Management Information Base\n (MIB) for performing response time data collection on TN3270 and\n TN3270E sessions by a TN3270E server. The response time data\n collected by a TN3270E server is structured to support both\n validation of service level agreements and performance monitoring of\n TN3270 and TN3270E Sessions. This MIB has as a prerequisite the\n TN3270E-MIB, reference [20].\n\n TN3270E, defined by RFC 2355 [19], refers to the enhancements made to\n the Telnet 3270 (TN3270) terminal emulation practices. Refer to RFC\n 1041 [18], STD 8, RFC 854 [16], and STD 31, RFC 860 [17] for a sample\n of what is meant by TN3270 practices. 2562 key management timestamp validation nested-reference unchanged"},{"id":"IETF RFC 2563","type":"specification","body":"IETF","designation":"RFC 2563","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2563.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2563.txt","https://www.rfc-editor.org/rfc/rfc2563.pdf"],"folder":"IETF/RFC-2563","files":{"txt":{"path":"standards/IETF/RFC-2563/RFC-2563.txt","sha256":"11decc3356b82748e60b078ec553499ea1ca875c95dd61c8ef81fe0e6e3ab6c4"}},"tags":["nested-reference","unchanged"],"summary":"Operating Systems are now attempting to support ad-hoc networks of\n two or more systems, while keeping user configuration at a minimum.\n To accommodate this, in the absence of a central configuration\n mechanism (DHCP), some OS's are automatically choosing a link-local\n IP address which will allow them to communicate only with other hosts\n on the same link. This address will not allow the OS to communicate\n with anything beyond a router. However, some sites depend on the\n fact that a host with no DHCP response will have no IP address. This\n document describes a mechanism by which DHCP servers are able to tell\n clients that they do not have an IP address to offer, and that the\n client should not generate an IP address it's own.\n\n1. Introduction\n\n With computers becoming a larger part of everyday life, operating\n systems must be able to support a larger range of operating\n environments. One","scope_keywords":["2563","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2563 Operating Systems are now attempting to support ad-hoc networks of\n two or more systems, while keeping user configuration at a minimum.\n To accommodate this, in the absence of a central configuration\n mechanism (DHCP), some OS's are automatically choosing a link-local\n IP address which will allow them to communicate only with other hosts\n on the same link. This address will not allow the OS to communicate\n with anything beyond a router. However, some sites depend on the\n fact that a host with no DHCP response will have no IP address. This\n document describes a mechanism by which DHCP servers are able to tell\n clients that they do not have an IP address to offer, and that the\n client should not generate an IP address it's own.\n\n1. Introduction\n\n With computers becoming a larger part of everyday life, operating\n systems must be able to support a larger range of operating\n environments. One 2563 key registered nested-reference unchanged"},{"id":"IETF RFC 2861","type":"specification","body":"IETF","designation":"RFC 2861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2861.txt","https://www.rfc-editor.org/rfc/rfc2861.pdf"],"folder":"IETF/RFC-2861","files":{"txt":{"path":"standards/IETF/RFC-2861/RFC-2861.txt","sha256":"bbb1911f314d2f8b38701a8dd52c587c6a14d1cf88283d4f245f07c5cb99e628"}},"tags":["nested-reference","unchanged"],"summary":"TCP's congestion window controls the number of packets a TCP flow may\n have in the network at any time. However, long periods when the\n sender is idle or application-limited can lead to the invalidation of\n the congestion window, in that the congestion window no longer\n reflects current information about the state of the network. This\n document describes a simple modification to TCP's congestion control\n algorithms to decay the congestion window cwnd after the transition\n from a sufficiently-long application-limited period, while using the\n slow-start threshold ssthresh to save information about the previous\n value of the congestion window.\n\n An invalid congestion window also results when the congestion window\n is increased (i.e., in TCP's slow-start or congestion avoidance\n phases) during application-limited periods, when the previous value\n of the congestion window might never have bee","scope_keywords":["2861","algorithm","algorithms","http","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3465","folder":"IETF/RFC-3465","source":"IETF/RFC-3465/RFC-3465.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5348","folder":"IETF/RFC-5348","source":"IETF/RFC-5348/RFC-5348.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null}],"search_text":"IETF RFC 2861 TCP's congestion window controls the number of packets a TCP flow may\n have in the network at any time. However, long periods when the\n sender is idle or application-limited can lead to the invalidation of\n the congestion window, in that the congestion window no longer\n reflects current information about the state of the network. This\n document describes a simple modification to TCP's congestion control\n algorithms to decay the congestion window cwnd after the transition\n from a sufficiently-long application-limited period, while using the\n slow-start threshold ssthresh to save information about the previous\n value of the congestion window.\n\n An invalid congestion window also results when the congestion window\n is increased (i.e., in TCP's slow-start or congestion avoidance\n phases) during application-limited periods, when the previous value\n of the congestion window might never have bee 2861 algorithm algorithms http key validation nested-reference unchanged"},{"id":"IETF RFC 3742","type":"specification","body":"IETF","designation":"RFC 3742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3742.txt","https://www.rfc-editor.org/rfc/rfc3742.pdf"],"folder":"IETF/RFC-3742","files":{"txt":{"path":"standards/IETF/RFC-3742/RFC-3742.txt","sha256":"a5a58b8d981cc2b27eb407872cbcbb1be3c6dee3011a1262b0d9560e84ef1ce7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an optional modification for TCP's slow-start\n for use with TCP connections with large congestion windows. For TCP\n connections that are able to use congestion windows of thousands (or\n tens of thousands) of MSS-sized segments (for MSS the sender's\n MAXIMUM SEGMENT SIZE), the current slow-start procedure can result in\n increasing the congestion window by thousands of segments in a single\n round-trip time. Such an increase can easily result in thousands of\n packets being dropped in one round-trip time. This is often\n counter-productive for the TCP flow itself, and is also hard on the\n rest of the traffic sharing the congested link. This note describes\n Limited Slow-Start as an optional mechanism for limiting the number\n of segments by which the congestion window is increased for one\n window of data during slow-start, in order to improve performance for\n TCP connect","scope_keywords":["3742","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 8312","folder":"IETF/RFC-8312","source":"IETF/RFC-8312/RFC-8312.txt","version":null}],"search_text":"IETF RFC 3742 This document describes an optional modification for TCP's slow-start\n for use with TCP connections with large congestion windows. For TCP\n connections that are able to use congestion windows of thousands (or\n tens of thousands) of MSS-sized segments (for MSS the sender's\n MAXIMUM SEGMENT SIZE), the current slow-start procedure can result in\n increasing the congestion window by thousands of segments in a single\n round-trip time. Such an increase can easily result in thousands of\n packets being dropped in one round-trip time. This is often\n counter-productive for the TCP flow itself, and is also hard on the\n rest of the traffic sharing the congested link. This note describes\n Limited Slow-Start as an optional mechanism for limiting the number\n of segments by which the congestion window is increased for one\n window of data during slow-start, in order to improve performance for\n TCP connect 3742 management nested-reference unchanged"},{"id":"IETF RFC 4774","type":"specification","body":"IETF","designation":"RFC 4774","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4774.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4774.txt","https://www.rfc-editor.org/rfc/rfc4774.pdf"],"folder":"IETF/RFC-4774","files":{"txt":{"path":"standards/IETF/RFC-4774/RFC-4774.txt","sha256":"e6def990995d1bc5114e3fe1f8d1424da57c494b82b2af75375993d1b69b1cce"}},"tags":["nested-reference","unchanged"],"summary":"There have been a number of proposals for alternate semantics for the\n Explicit Congestion Notification (ECN) field in the IP header RFC\n 3168. This document discusses some of the issues in defining\n alternate semantics for the ECN field, and specifies requirements for\n a safe coexistence in an Internet that could include routers that do\n not understand the defined alternate semantics. This document\n evolved as a result of discussions with the authors of one recent\n proposal for such alternate semantics.\n\nFloyd Best Current Practice [Page 1]\n\f\nRFC 4774 Alternate Semantics for the ECN Field November 2006","scope_keywords":["4774","path","pid","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5696","folder":"IETF/RFC-5696","source":"IETF/RFC-5696/RFC-5696.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6660","folder":"IETF/RFC-6660","source":"IETF/RFC-6660/RFC-6660.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 8311","folder":"IETF/RFC-8311","source":"IETF/RFC-8311/RFC-8311.txt","version":null}],"search_text":"IETF RFC 4774 There have been a number of proposals for alternate semantics for the\n Explicit Congestion Notification (ECN) field in the IP header RFC\n 3168. This document discusses some of the issues in defining\n alternate semantics for the ECN field, and specifies requirements for\n a safe coexistence in an Internet that could include routers that do\n not understand the defined alternate semantics. This document\n evolved as a result of discussions with the authors of one recent\n proposal for such alternate semantics.\n\nFloyd Best Current Practice [Page 1]\n\f\nRFC 4774 Alternate Semantics for the ECN Field November 2006 4774 path pid trust nested-reference unchanged"},{"id":"IETF RFC 2584","type":"specification","body":"IETF","designation":"RFC 2584","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2584.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2584.txt","https://www.rfc-editor.org/rfc/rfc2584.pdf"],"folder":"IETF/RFC-2584","files":{"txt":{"path":"standards/IETF/RFC-2584/RFC-2584.txt","sha256":"e76ce95a36a1f15086a976747af8161c7f8bb7d674a62ba2818cc26758fef87c"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling HPR\n (High Performance Routing) network devices which have the capability\n to communicate in IP (Internet Protocol) networks. This memo\n identifies managed objects for the HPR in IP network communications.","scope_keywords":["2584","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2584 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it defines objects for monitoring and controlling HPR\n (High Performance Routing) network devices which have the capability\n to communicate in IP (Internet Protocol) networks. This memo\n identifies managed objects for the HPR in IP network communications. 2584 key management nested-reference unchanged"},{"id":"IETF RFC 5877","type":"specification","body":"IETF","designation":"RFC 5877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5877.txt","https://www.rfc-editor.org/rfc/rfc5877.pdf"],"folder":"IETF/RFC-5877","files":{"txt":{"path":"standards/IETF/RFC-5877/RFC-5877.txt","sha256":"24407a711de53683243260c45ffda645d4c8f06c337b64923d4366480a85e60e"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a MIME media type used to carry a single\n attribute certificate as defined in RFC 5755.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5877.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.","scope_keywords":["5877","attribute","authorization","certificate","certificates","crl","holder","http","issuer","key","license","pki","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null}],"search_text":"IETF RFC 5877 This document specifies a MIME media type used to carry a single\n attribute certificate as defined in RFC 5755.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5877.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved. 5877 attribute authorization certificate certificates crl holder http issuer key license pki profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 6394","type":"specification","body":"IETF","designation":"RFC 6394","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6394.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6394.txt","https://www.rfc-editor.org/rfc/rfc6394.pdf"],"folder":"IETF/RFC-6394","files":{"txt":{"path":"standards/IETF/RFC-6394/RFC-6394.txt","sha256":"13bef362b89041d4891fd61be1ddd8c1f8d31c418a73a51d67abc087dc438e49"}},"tags":["nested-reference","unchanged"],"summary":"Many current applications use the certificate-based authentication\n features in Transport Layer Security (TLS) to allow clients to verify\n that a connected server properly represents a desired domain name.\n Typically, this authentication has been based on PKIX certificate\n chains rooted in well-known certificate authorities (CAs), but\n additional information can be provided via the DNS itself. This\n document describes a set of use cases in which the DNS and DNS\n Security Extensions (DNSSEC) could be used to make assertions that\n support the TLS authentication process. The main focus of this\n document is TLS server authentication, but it also covers TLS client\n authentication for applications where TLS clients are identified by\n domain names.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document ","scope_keywords":["6394","authentication","authorization","certificate","certificates","credential","credentials","holder","http","https","key","keys","license","pki","subject","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 6394 Many current applications use the certificate-based authentication\n features in Transport Layer Security (TLS) to allow clients to verify\n that a connected server properly represents a desired domain name.\n Typically, this authentication has been based on PKIX certificate\n chains rooted in well-known certificate authorities (CAs), but\n additional information can be provided via the DNS itself. This\n document describes a set of use cases in which the DNS and DNS\n Security Extensions (DNSSEC) could be used to make assertions that\n support the TLS authentication process. The main focus of this\n document is TLS server authentication, but it also covers TLS client\n authentication for applications where TLS clients are identified by\n domain names.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document  6394 authentication authorization certificate certificates credential credentials holder http https key keys license pki subject tls nested-reference unchanged"},{"id":"IETF RFC 2600","type":"specification","body":"IETF","designation":"RFC 2600","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2600.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2600.txt","https://www.rfc-editor.org/rfc/rfc2600.pdf"],"folder":"IETF/RFC-2600","files":{"txt":{"path":"standards/IETF/RFC-2600/RFC-2600.txt","sha256":"acf7a12ee325c25be17ce8e82fdfcec64413336887ee396fb3d174613e594f71"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Internet Engineering Task Force\nRequest for Comments: 2600 J. Reynolds\nObsoletes: 2500, 2400, 2300, 2200, 2000, 1920, R. Braden\n1880, 1800, 1780, 1720, 1610, 1600, 1540, 1500, Editors\n1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100, March 2000\n1083\nSTD: 1\nCategory: Standards Track\n\n Internet Official Protocol Standards\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Engineering Task Force\n (IETF). This memo is an Internet Standard. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nOverview\n\n This memo is published by the RFC Editor in accordance with Section\n 2.1 of \"The Internet Standards Process -- Revision 3\", RFC 2026,\n which specifies the rules and procedures by which all Internet\n standards are set.","scope_keywords":["2600","http","identification","key","management","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 2600 Network Working Group Internet Engineering Task Force\nRequest for Comments: 2600 J. Reynolds\nObsoletes: 2500, 2400, 2300, 2200, 2000, 1920, R. Braden\n1880, 1800, 1780, 1720, 1610, 1600, 1540, 1500, Editors\n1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100, March 2000\n1083\nSTD: 1\nCategory: Standards Track\n\n Internet Official Protocol Standards\n\nStatus of this Memo\n\n This memo describes the state of standardization of protocols used in\n the Internet as determined by the Internet Engineering Task Force\n (IETF). This memo is an Internet Standard. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nOverview\n\n This memo is published by the RFC Editor in accordance with Section\n 2.1 of \"The Internet Standards Process -- Revision 3\", RFC 2026,\n which specifies the rules and procedures by which all Internet\n standards are set. 2600 http identification key management path subject nested-reference unchanged"},{"id":"IETF RFC 2605","type":"specification","body":"IETF","designation":"RFC 2605","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2605.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2605.txt","https://www.rfc-editor.org/rfc/rfc2605.pdf"],"folder":"IETF/RFC-2605","files":{"txt":{"path":"standards/IETF/RFC-2605/RFC-2605.txt","sha256":"bff9a768d333893badee3a00641992d761931ca927f4c596a773f33642eca6fd"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1567, \"X.500 Directory Monitoring MIB\". This\n memo extends that specification to a more generic MIB for monitoring\n one or more directory servers each of which may support multiple\n access protocols. The MIB defined in this memo will be used in\n conjunction with the NETWORK-SERVICES-MIB [19] for monitoring\n Directory Servers.","scope_keywords":["2605","attribute","attributes","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2605 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n This memo obsoletes RFC 1567, \"X.500 Directory Monitoring MIB\". This\n memo extends that specification to a more generic MIB for monitoring\n one or more directory servers each of which may support multiple\n access protocols. The MIB defined in this memo will be used in\n conjunction with the NETWORK-SERVICES-MIB [19] for monitoring\n Directory Servers. 2605 attribute attributes management nested-reference unchanged"},{"id":"IETF RFC 3849","type":"specification","body":"IETF","designation":"RFC 3849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3849.txt","https://www.rfc-editor.org/rfc/rfc3849.pdf"],"folder":"IETF/RFC-3849","files":{"txt":{"path":"standards/IETF/RFC-3849/RFC-3849.txt","sha256":"b0741fc609be565b356c62d2f9b9ef30469f3fe7bde386c2690e173751bb1941"}},"tags":["nested-reference","unchanged"],"summary":"To reduce the likelihood of conflict and confusion when relating\n documented examples to deployed systems, an IPv6 unicast address\n prefix is reserved for use in examples in RFCs, books, documentation,\n and the like. Since site-local and link-local unicast addresses have\n special meaning in IPv6, these addresses cannot be used in many\n example situations. The document describes the use of the IPv6\n address prefix 2001:DB8::/32 as a reserved prefix for use in\n documentation.\n\n1. Introduction\n\n The address architecture for IPv6 [1] does not specifically allocate\n an IPv6 address prefix for use for documentation purposes.\n Documentation material is currently using address prefixes drawn from\n address blocks already allocated or assigned to existing\n organizations or to well known ISPs, or drawn from the currently\n unallocated address pool. Such use conflicts with existing or future\n allocat","scope_keywords":["3849","http","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4085","folder":"IETF/RFC-4085","source":"IETF/RFC-4085/RFC-4085.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 5156","folder":"IETF/RFC-5156","source":"IETF/RFC-5156/RFC-5156.txt","version":null},{"body":"IETF","designation":"RFC 5180","folder":"IETF/RFC-5180","source":"IETF/RFC-5180/RFC-5180.txt","version":null},{"body":"IETF","designation":"RFC 5398","folder":"IETF/RFC-5398","source":"IETF/RFC-5398/RFC-5398.txt","version":null},{"body":"IETF","designation":"RFC 5737","folder":"IETF/RFC-5737","source":"IETF/RFC-5737/RFC-5737.txt","version":null},{"body":"IETF","designation":"RFC 6052","folder":"IETF/RFC-6052","source":"IETF/RFC-6052/RFC-6052.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6666","folder":"IETF/RFC-6666","source":"IETF/RFC-6666/RFC-6666.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null}],"search_text":"IETF RFC 3849 To reduce the likelihood of conflict and confusion when relating\n documented examples to deployed systems, an IPv6 unicast address\n prefix is reserved for use in examples in RFCs, books, documentation,\n and the like. Since site-local and link-local unicast addresses have\n special meaning in IPv6, these addresses cannot be used in many\n example situations. The document describes the use of the IPv6\n address prefix 2001:DB8::/32 as a reserved prefix for use in\n documentation.\n\n1. Introduction\n\n The address architecture for IPv6 [1] does not specifically allocate\n an IPv6 address prefix for use for documentation purposes.\n Documentation material is currently using address prefixes drawn from\n address blocks already allocated or assigned to existing\n organizations or to well known ISPs, or drawn from the currently\n unallocated address pool. Such use conflicts with existing or future\n allocat 3849 http license subject nested-reference unchanged"},{"id":"IETF RFC 5398","type":"specification","body":"IETF","designation":"RFC 5398","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5398.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5398.txt","https://www.rfc-editor.org/rfc/rfc5398.pdf"],"folder":"IETF/RFC-5398","files":{"txt":{"path":"standards/IETF/RFC-5398/RFC-5398.txt","sha256":"e43a36634b92ab2299da2502d5d9a9250c50d4ac3ffc079c8a085429a0d7fa7f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Huston\nRequest for Comments: 5398 December 2008\nCategory: Informational\n\n Autonomous System (AS) Number Reservation for Documentation Use\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2008 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents (http://trustee.ietf.org/\n license-info) in effect on the date of publication of this document.\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nAbstract\n\n To reduce the likelihood of conflict and confusion when relating\n documented examples to deployed system","scope_keywords":["5398","http","license","policy","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5612","folder":"IETF/RFC-5612","source":"IETF/RFC-5612/RFC-5612.txt","version":null}],"search_text":"IETF RFC 5398 Network Working Group G. Huston\nRequest for Comments: 5398 December 2008\nCategory: Informational\n\n Autonomous System (AS) Number Reservation for Documentation Use\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2008 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents (http://trustee.ietf.org/\n license-info) in effect on the date of publication of this document.\n Please review these documents carefully, as they describe your rights\n and restrictions with respect to this document.\n\nAbstract\n\n To reduce the likelihood of conflict and confusion when relating\n documented examples to deployed system 5398 http license policy risk subject trust nested-reference unchanged"},{"id":"IETF RFC 3721","type":"specification","body":"IETF","designation":"RFC 3721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3721.txt","https://www.rfc-editor.org/rfc/rfc3721.pdf"],"folder":"IETF/RFC-3721","files":{"txt":{"path":"standards/IETF/RFC-3721/RFC-3721.txt","sha256":"2630855d71aa483e3d599e0a2ceaff2d2a6db785310cbc085d015666e7036e8f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides examples of the Internet Small Computer\n Systems Interface (iSCSI; or SCSI over TCP) name construction and\n discussion of discovery of iSCSI resources (targets) by iSCSI\n initiators. This document complements the iSCSI protocol document.\n Flexibility is the key guiding principle behind this document. That\n is, an effort has been made to satisfy the needs of both small\n isolated environments, as well as large environments requiring\n secure/scalable solutions.\n\nBakke, et al. Informational [Page 1]\n\f\nRFC 3721 iSCSI Naming and Discovery April 2004","scope_keywords":["3721","authentication","authorization","identification","key","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 4018","folder":"IETF/RFC-4018","source":"IETF/RFC-4018/RFC-4018.txt","version":null},{"body":"IETF","designation":"RFC 5048","folder":"IETF/RFC-5048","source":"IETF/RFC-5048/RFC-5048.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7146","folder":"IETF/RFC-7146","source":"IETF/RFC-7146/RFC-7146.txt","version":null}],"search_text":"IETF RFC 3721 This document provides examples of the Internet Small Computer\n Systems Interface (iSCSI; or SCSI over TCP) name construction and\n discussion of discovery of iSCSI resources (targets) by iSCSI\n initiators. This document complements the iSCSI protocol document.\n Flexibility is the key guiding principle behind this document. That\n is, an effort has been made to satisfy the needs of both small\n isolated environments, as well as large environments requiring\n secure/scalable solutions.\n\nBakke, et al. Informational [Page 1]\n\f\nRFC 3721 iSCSI Naming and Discovery April 2004 3721 authentication authorization identification key path qualified nested-reference unchanged"},{"id":"IETF RFC 6879","type":"specification","body":"IETF","designation":"RFC 6879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6879.txt","https://www.rfc-editor.org/rfc/rfc6879.pdf"],"folder":"IETF/RFC-6879","files":{"txt":{"path":"standards/IETF/RFC-6879/RFC-6879.txt","sha256":"000aa86dc5dec146c1ba71cf0d3fc0d812d28e51921c1f8d4f18366b98ac225b"}},"tags":["nested-reference","unchanged"],"summary":"This document analyzes events that cause renumbering and describes\n the current renumbering methods. These are described in three\n categories: those applicable during network design, those applicable\n during preparation for renumbering, and those applicable during the\n renumbering operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma","scope_keywords":["6879","http","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6866","folder":"IETF/RFC-6866","source":"IETF/RFC-6866/RFC-6866.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null}],"search_text":"IETF RFC 6879 This document analyzes events that cause renumbering and describes\n the current renumbering methods. These are described in three\n categories: those applicable during network design, those applicable\n during preparation for renumbering, and those applicable during the\n renumbering operation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma 6879 http license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6707","type":"specification","body":"IETF","designation":"RFC 6707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6707.txt","https://www.rfc-editor.org/rfc/rfc6707.pdf"],"folder":"IETF/RFC-6707","files":{"txt":{"path":"standards/IETF/RFC-6707/RFC-6707.txt","sha256":"381ca412539f72a592d518665f12eeafc2b3135b74f421e77b74b1d3cbfa4c71"}},"tags":["nested-reference","unchanged"],"summary":"Content Delivery Networks (CDNs) provide numerous benefits for\n cacheable content: reduced delivery cost, improved quality of\n experience for End Users, and increased robustness of delivery. For\n these reasons, they are frequently used for large-scale content\n delivery. As a result, existing CDN Providers are scaling up their\n infrastructure, and many Network Service Providers (NSPs) are\n deploying their own CDNs. It is generally desirable that a given\n content item can be delivered to an End User regardless of that End\n User's location or attachment network. This is the motivation for\n interconnecting standalone CDNs so they can interoperate as an open\n content delivery infrastructure for the end-to-end delivery of\n content from Content Service Providers (CSPs) to End Users. However,\n no standards or open specifications currently exist to facilitate\n such CDN Interconnection.\n\n The goal","scope_keywords":["6707","delivery","http","license","pid","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null},{"body":"IETF","designation":"RFC 6983","folder":"IETF/RFC-6983","source":"IETF/RFC-6983/RFC-6983.txt","version":null},{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null},{"body":"IETF","designation":"RFC 7337","folder":"IETF/RFC-7337","source":"IETF/RFC-7337/RFC-7337.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 6707 Content Delivery Networks (CDNs) provide numerous benefits for\n cacheable content: reduced delivery cost, improved quality of\n experience for End Users, and increased robustness of delivery. For\n these reasons, they are frequently used for large-scale content\n delivery. As a result, existing CDN Providers are scaling up their\n infrastructure, and many Network Service Providers (NSPs) are\n deploying their own CDNs. It is generally desirable that a given\n content item can be delivered to an End User regardless of that End\n User's location or attachment network. This is the motivation for\n interconnecting standalone CDNs so they can interoperate as an open\n content delivery infrastructure for the end-to-end delivery of\n content from Content Service Providers (CSPs) to End Users. However,\n no standards or open specifications currently exist to facilitate\n such CDN Interconnection.\n\n The goal 6707 delivery http license pid subject trust nested-reference unchanged"},{"id":"IETF RFC 6973","type":"specification","body":"IETF","designation":"RFC 6973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6973.txt","https://www.rfc-editor.org/rfc/rfc6973.pdf"],"folder":"IETF/RFC-6973","files":{"txt":{"path":"standards/IETF/RFC-6973/RFC-6973.txt","sha256":"94bb6027b22603c58728431ec4606a0f2a7aad569234322c55d6a91e22ffa06e"}},"tags":["nested-reference","unchanged"],"summary":"This document offers guidance for developing privacy considerations\n for inclusion in protocol specifications. It aims to make designers,\n implementers, and users of Internet protocols aware of privacy-\n related design choices. It suggests that whether any individual RFC\n warrants a specific privacy considerations section will depend on the\n document's content.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current statu","scope_keywords":["6973","http","identification","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7258","folder":"IETF/RFC-7258","source":"IETF/RFC-7258/RFC-7258.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7452","folder":"IETF/RFC-7452","source":"IETF/RFC-7452/RFC-7452.txt","version":null},{"body":"IETF","designation":"RFC 7521","folder":"IETF/RFC-7521","source":"IETF/RFC-7521/RFC-7521.txt","version":null},{"body":"IETF","designation":"RFC 7536","folder":"IETF/RFC-7536","source":"IETF/RFC-7536/RFC-7536.txt","version":null},{"body":"IETF","designation":"RFC 7593","folder":"IETF/RFC-7593","source":"IETF/RFC-7593/RFC-7593.txt","version":null},{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7624","folder":"IETF/RFC-7624","source":"IETF/RFC-7624/RFC-7624.txt","version":null},{"body":"IETF","designation":"RFC 7626","folder":"IETF/RFC-7626","source":"IETF/RFC-7626/RFC-7626.txt","version":null},{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7721","folder":"IETF/RFC-7721","source":"IETF/RFC-7721/RFC-7721.txt","version":null},{"body":"IETF","designation":"RFC 7816","folder":"IETF/RFC-7816","source":"IETF/RFC-7816/RFC-7816.txt","version":null},{"body":"IETF","designation":"RFC 7819","folder":"IETF/RFC-7819","source":"IETF/RFC-7819/RFC-7819.txt","version":null},{"body":"IETF","designation":"RFC 7824","folder":"IETF/RFC-7824","source":"IETF/RFC-7824/RFC-7824.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 8030","folder":"IETF/RFC-8030","source":"IETF/RFC-8030/RFC-8030.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8240","folder":"IETF/RFC-8240","source":"IETF/RFC-8240/RFC-8240.txt","version":null},{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 9076","folder":"IETF/RFC-9076","source":"IETF/RFC-9076/RFC-9076.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9103","folder":"IETF/RFC-9103","source":"IETF/RFC-9103/RFC-9103.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9146","folder":"IETF/RFC-9146","source":"IETF/RFC-9146/RFC-9146.txt","version":null}],"search_text":"IETF RFC 6973 This document offers guidance for developing privacy considerations\n for inclusion in protocol specifications. It aims to make designers,\n implementers, and users of Internet protocols aware of privacy-\n related design choices. It suggests that whether any individual RFC\n warrants a specific privacy considerations section will depend on the\n document's content.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current statu 6973 http identification license management subject trust nested-reference unchanged"},{"id":"IETF RFC 7615","type":"specification","body":"IETF","designation":"RFC 7615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7615.txt","https://www.rfc-editor.org/rfc/rfc7615.pdf"],"folder":"IETF/RFC-7615","files":{"txt":{"path":"standards/IETF/RFC-7615/RFC-7615.txt","sha256":"496983fa766685c2d253a6094aed1f343152f4d3ab3367264e132264cbe4c4c7"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the \"Authentication-Info\" and \"Proxy-\n Authentication-Info\" response header fields for use in Hypertext\n Transfer Protocol (HTTP) authentication schemes that need to return\n information once the client's authentication credentials have been\n accepted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7615.\n\nReschke Standards Track [Page 1]\n\f\nRFC 7615 HTTP Authent","scope_keywords":["7615","authentication","authorization","credential","credentials","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null}],"search_text":"IETF RFC 7615 This specification defines the \"Authentication-Info\" and \"Proxy-\n Authentication-Info\" response header fields for use in Hypertext\n Transfer Protocol (HTTP) authentication schemes that need to return\n information once the client's authentication credentials have been\n accepted.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7615.\n\nReschke Standards Track [Page 1]\n\f\nRFC 7615 HTTP Authent 7615 authentication authorization credential credentials http license subject trust nested-reference unchanged"},{"id":"IETF RFC 4012","type":"specification","body":"IETF","designation":"RFC 4012","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4012.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4012.txt","https://www.rfc-editor.org/rfc/rfc4012.pdf"],"folder":"IETF/RFC-4012","files":{"txt":{"path":"standards/IETF/RFC-4012/RFC-4012.txt","sha256":"96357630eba6fe1cadd67080a5bf8f08010b9db668bf4cc56a078836545de344"}},"tags":["nested-reference","unchanged"],"summary":"This memo introduces a new set of simple extensions to the Routing\n Policy Specification Language (RPSL), enabling the language to\n document routing policies for the IPv6 and multicast address families\n currently used in the Internet.","scope_keywords":["4012","attribute","attributes","authorization","key","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6382","folder":"IETF/RFC-6382","source":"IETF/RFC-6382/RFC-6382.txt","version":null}],"search_text":"IETF RFC 4012 This memo introduces a new set of simple extensions to the Routing\n Policy Specification Language (RPSL), enabling the language to\n document routing policies for the IPv6 and multicast address families\n currently used in the Internet. 4012 attribute attributes authorization key policies policy nested-reference unchanged"},{"id":"IETF RFC 7485","type":"specification","body":"IETF","designation":"RFC 7485","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7485.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7485.txt","https://www.rfc-editor.org/rfc/rfc7485.pdf"],"folder":"IETF/RFC-7485","files":{"txt":{"path":"standards/IETF/RFC-7485/RFC-7485.txt","sha256":"2a66e0eea81bdea6d5ab23d0801bd8fad0d830a9e113c238fea0e4d75d8f6b4c"}},"tags":["nested-reference","unchanged"],"summary":"WHOIS output objects from registries, including both Regional\n Internet Registries (RIRs) and Domain Name Registries (DNRs), were\n collected and analyzed. This document describes the process and\n results of the statistical analysis of existing WHOIS information.\n The purpose of this document is to build an object inventory to\n facilitate discussions of data objects included in Registration Data\n Access Protocol (RDAP) responses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Sta","scope_keywords":["7485","authentication","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 7485 WHOIS output objects from registries, including both Regional\n Internet Registries (RIRs) and Domain Name Registries (DNRs), were\n collected and analyzed. This document describes the process and\n results of the statistical analysis of existing WHOIS information.\n The purpose of this document is to build an object inventory to\n facilitate discussions of data objects included in Registration Data\n Access Protocol (RDAP) responses.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Sta 7485 authentication http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 2887","type":"specification","body":"IETF","designation":"RFC 2887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2887.txt","https://www.rfc-editor.org/rfc/rfc2887.pdf"],"folder":"IETF/RFC-2887","files":{"txt":{"path":"standards/IETF/RFC-2887/RFC-2887.txt","sha256":"83849be7334772875b9f189427df0e7513672df11b6576b8af6772d7d4de7b46"}},"tags":["nested-reference","unchanged"],"summary":"The design space for reliable multicast is rich, with many possible\n solutions having been devised. However, application requirements\n serve to constrain this design space to a relatively small solution\n space. This document provides an overview of the design space and\n the ways in which application constraints affect possible solutions.\n\n1. Introduction\n\n The term \"general purpose reliable multicast protocol\" is something\n of an oxymoron. Different applications have different requirements\n of a reliable multicast protocol, and these requirements constrain\n the design space in ways that two applications with differing\n requirements often cannot share a single solution. There are however\n many successful reliable multicast protocol designs that serve more\n special purpose requirements well.\n\n In this document we attempt to review the design space for reliable\n multicast protocols intended","scope_keywords":["2887","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3048","folder":"IETF/RFC-3048","source":"IETF/RFC-3048/RFC-3048.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 4410","folder":"IETF/RFC-4410","source":"IETF/RFC-4410/RFC-4410.txt","version":null},{"body":"IETF","designation":"RFC 4588","folder":"IETF/RFC-4588","source":"IETF/RFC-4588/RFC-4588.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"IETF RFC 2887 The design space for reliable multicast is rich, with many possible\n solutions having been devised. However, application requirements\n serve to constrain this design space to a relatively small solution\n space. This document provides an overview of the design space and\n the ways in which application constraints affect possible solutions.\n\n1. Introduction\n\n The term \"general purpose reliable multicast protocol\" is something\n of an oxymoron. Different applications have different requirements\n of a reliable multicast protocol, and these requirements constrain\n the design space in ways that two applications with differing\n requirements often cannot share a single solution. There are however\n many successful reliable multicast protocol designs that serve more\n special purpose requirements well.\n\n In this document we attempt to review the design space for reliable\n multicast protocols intended 2887 delivery path nested-reference unchanged"},{"id":"IETF RFC 4371","type":"specification","body":"IETF","designation":"RFC 4371","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4371.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4371.txt","https://www.rfc-editor.org/rfc/rfc4371.pdf"],"folder":"IETF/RFC-4371","files":{"txt":{"path":"standards/IETF/RFC-4371/RFC-4371.txt","sha256":"b1befbe9c7eaa95d158ef8c9528c60f01a49b9d18c84b48a0d8a14c693db2148"}},"tags":["nested-reference","unchanged"],"summary":"This document updates BCP 101 to take account of the new IETF\n Intellectual Property Trust.","scope_keywords":["4371","http","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4748","folder":"IETF/RFC-4748","source":"IETF/RFC-4748/RFC-4748.txt","version":null},{"body":"IETF","designation":"RFC 5377","folder":"IETF/RFC-5377","source":"IETF/RFC-5377/RFC-5377.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null}],"search_text":"IETF RFC 4371 This document updates BCP 101 to take account of the new IETF\n Intellectual Property Trust. 4371 http license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5911","type":"specification","body":"IETF","designation":"RFC 5911","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5911.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5911.txt","https://www.rfc-editor.org/rfc/rfc5911.pdf"],"folder":"IETF/RFC-5911","files":{"txt":{"path":"standards/IETF/RFC-5911/RFC-5911.txt","sha256":"8d2fe1f11e2b84edd252b8268ba3efc9223fa31a9c18e63c436fb90d09b04a7b"}},"tags":["nested-reference","unchanged"],"summary":"The Cryptographic Message Syntax (CMS) format, and many associated\n formats, are expressed using ASN.1. The current ASN.1 modules\n conform to the 1988 version of ASN.1. This document updates those\n ASN.1 modules to conform to the 2002 version of ASN.1. There are no\n bits-on-the-wire changes to any of the formats; this is simply a\n change to the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of th","scope_keywords":["5911","algorithm","algorithms","encryption","http","identification","key","keys","license","management","pki","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6025","folder":"IETF/RFC-6025","source":"IETF/RFC-6025/RFC-6025.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 6268","folder":"IETF/RFC-6268","source":"IETF/RFC-6268/RFC-6268.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null}],"search_text":"IETF RFC 5911 The Cryptographic Message Syntax (CMS) format, and many associated\n formats, are expressed using ASN.1. The current ASN.1 modules\n conform to the 1988 version of ASN.1. This document updates those\n ASN.1 modules to conform to the 2002 version of ASN.1. There are no\n bits-on-the-wire changes to any of the formats; this is simply a\n change to the syntax.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of th 5911 algorithm algorithms encryption http identification key keys license management pki subject trust nested-reference unchanged"},{"id":"IETF RFC 7114","type":"specification","body":"IETF","designation":"RFC 7114","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7114.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7114.txt","https://www.rfc-editor.org/rfc/rfc7114.pdf"],"folder":"IETF/RFC-7114","files":{"txt":{"path":"standards/IETF/RFC-7114/RFC-7114.txt","sha256":"0fcd12cdba9e4631fa680c2c1b7976629ce046b251dc71235c376e72c01d754c"}},"tags":["nested-reference","unchanged"],"summary":"Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the\n Content-Type parameter \"smime-type\". As the list of defined values\n for that parameter has increased, it has become clear that a registry\n is needed to document these values. This document creates the\n registry, registers the current values, and specifies the policies\n for registration of new values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://","scope_keywords":["7114","certificate","http","key","license","management","policies","policy","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 7114 Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the\n Content-Type parameter \"smime-type\". As the list of defined values\n for that parameter has increased, it has become clear that a registry\n is needed to document these values. This document creates the\n registry, registers the current values, and specifies the policies\n for registration of new values.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:// 7114 certificate http key license management policies policy registered subject trust nested-reference unchanged"},{"id":"IETF RFC 354","type":"specification","body":"IETF","designation":"RFC 354","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc354.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc354.txt","https://www.rfc-editor.org/rfc/rfc354.pdf"],"folder":"IETF/RFC-354","files":{"txt":{"path":"standards/IETF/RFC-354/RFC-354.txt","sha256":"cd1bcbdaf31d4c2dc5ffe268b8875013fd795a24eca3ad06460cde77c230782e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Abhay Bhushan\nRequest for Comments: 354 MIT-MAC\nNIC: 10596 July 8, 1972\nCategories D.4, D.5, D.7\nObsoletes: RFC 264 and 265\n\n THE FILE TRANSFER PROTOCOL\n\nI. INTRODUCTION\n\n The File Transfer Protocol (FTP) is a protocol for file\ntransfer betweet HOSTs (including terminal IMPs), on the ARPA\nComputer Network (ARPANET). The primary function of FTP is to\ntransfer files efficiently and reliably among HOSTs and to allow\nthe convenient use of remote file storage capabilities.\n\n The objectives of FTP are 1) to promote sharing of files\n(computer programs and/or data), 2) fo encourage indirect or\nimplicit (via programs) use of remote computers, 3) to shield a\nuser from variations in file storage systems among HOSTs, and\n4) to transfer data reliably and efficiently. FTP, though usable\ndirectly by user at a terminal, is designed mainly for use by\nprograms.\n\n The attempt in this ","scope_keywords":["354","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 385","folder":"IETF/RFC-385","source":"IETF/RFC-385/RFC-385.txt","version":null},{"body":"IETF","designation":"RFC 414","folder":"IETF/RFC-414","source":"IETF/RFC-414/RFC-414.txt","version":null},{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 438","folder":"IETF/RFC-438","source":"IETF/RFC-438/RFC-438.txt","version":null},{"body":"IETF","designation":"RFC 448","folder":"IETF/RFC-448","source":"IETF/RFC-448/RFC-448.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null},{"body":"IETF","designation":"RFC 501","folder":"IETF/RFC-501","source":"IETF/RFC-501/RFC-501.txt","version":null},{"body":"IETF","designation":"RFC 683","folder":"IETF/RFC-683","source":"IETF/RFC-683/RFC-683.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 354 Network Working Group Abhay Bhushan\nRequest for Comments: 354 MIT-MAC\nNIC: 10596 July 8, 1972\nCategories D.4, D.5, D.7\nObsoletes: RFC 264 and 265\n\n THE FILE TRANSFER PROTOCOL\n\nI. INTRODUCTION\n\n The File Transfer Protocol (FTP) is a protocol for file\ntransfer betweet HOSTs (including terminal IMPs), on the ARPA\nComputer Network (ARPANET). The primary function of FTP is to\ntransfer files efficiently and reliably among HOSTs and to allow\nthe convenient use of remote file storage capabilities.\n\n The objectives of FTP are 1) to promote sharing of files\n(computer programs and/or data), 2) fo encourage indirect or\nimplicit (via programs) use of remote computers, 3) to shield a\nuser from variations in file storage systems among HOSTs, and\n4) to transfer data reliably and efficiently. FTP, though usable\ndirectly by user at a terminal, is designed mainly for use by\nprograms.\n\n The attempt in this  354 path presentation nested-reference unchanged"},{"id":"IETF RFC 4487","type":"specification","body":"IETF","designation":"RFC 4487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4487.txt","https://www.rfc-editor.org/rfc/rfc4487.pdf"],"folder":"IETF/RFC-4487","files":{"txt":{"path":"standards/IETF/RFC-4487/RFC-4487.txt","sha256":"b0d5b58354701702d95ebc33655e514226f0c7bf157405e72315f707be0f2ae9"}},"tags":["nested-reference","unchanged"],"summary":"This document captures the issues that may arise in the deployment of\n IPv6 networks when they support Mobile IPv6 and firewalls. The\n issues are not only applicable to firewalls protecting enterprise\n networks, but are also applicable in 3G mobile networks such as\n General Packet Radio Service / Universal Mobile Telecommunications\n System (GPRS/UMTS) and CDMA2000 networks.\n\n The goal of this document is to highlight the issues with firewalls\n and Mobile IPv6 and act as an enabler for further discussion. Issues\n identified here can be solved by developing appropriate solutions.\n\nLe, et al. Informational [Page 1]\n\f\nRFC 4487 MIPv6 and Firewalls May 2006","scope_keywords":["4487"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 4487 This document captures the issues that may arise in the deployment of\n IPv6 networks when they support Mobile IPv6 and firewalls. The\n issues are not only applicable to firewalls protecting enterprise\n networks, but are also applicable in 3G mobile networks such as\n General Packet Radio Service / Universal Mobile Telecommunications\n System (GPRS/UMTS) and CDMA2000 networks.\n\n The goal of this document is to highlight the issues with firewalls\n and Mobile IPv6 and act as an enabler for further discussion. Issues\n identified here can be solved by developing appropriate solutions.\n\nLe, et al. Informational [Page 1]\n\f\nRFC 4487 MIPv6 and Firewalls May 2006 4487 nested-reference unchanged"},{"id":"IETF RFC 294","type":"specification","body":"IETF","designation":"RFC 294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc294.txt","https://www.rfc-editor.org/rfc/rfc294.pdf"],"folder":"IETF/RFC-294","files":{"txt":{"path":"standards/IETF/RFC-294/RFC-294.txt","sha256":"9e32d05bab4138f1b26d03ec87516ff26a5e1652d85ed36e13249a64ee8e00bb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 25 January 1972\nRFC 294 Abhay Bhushan, MIT\nNIC 8304\nCategories: D.4, D.5, and D.7\nUpdates: RFC 265\n\nThe Use of 'Set Data Type' Transaction in File Transfer Protocol\n----------------------------------------------------------------\n\n As mentioned in RFC 265, the opcode of '00' is set aside for the\nclarify the use of 'set data type' in file transfer operations.\n\n In many systems such as Multics at MIT, there is no provision to\nidentify the type of data (i.e., ASCII or numeric) stored in files.\nThe manner in which the data is handled is context dependent. ASCII\ncharacters are stored as four 9-bit characters per 36-bit word, right\njustified with left most bit as zero. As efficient conversion\nprograms exists in Multics for conversion of data from Multics' ASCII\ninto Network ASCII, it would be useful for a user to be able to\ninstruct the Multics server to convert data into","scope_keywords":["294"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 294 Network Working Group 25 January 1972\nRFC 294 Abhay Bhushan, MIT\nNIC 8304\nCategories: D.4, D.5, and D.7\nUpdates: RFC 265\n\nThe Use of 'Set Data Type' Transaction in File Transfer Protocol\n----------------------------------------------------------------\n\n As mentioned in RFC 265, the opcode of '00' is set aside for the\nclarify the use of 'set data type' in file transfer operations.\n\n In many systems such as Multics at MIT, there is no provision to\nidentify the type of data (i.e., ASCII or numeric) stored in files.\nThe manner in which the data is handled is context dependent. ASCII\ncharacters are stored as four 9-bit characters per 36-bit word, right\njustified with left most bit as zero. As efficient conversion\nprograms exists in Multics for conversion of data from Multics' ASCII\ninto Network ASCII, it would be useful for a user to be able to\ninstruct the Multics server to convert data into 294 nested-reference unchanged"},{"id":"IETF RFC 8752","type":"specification","body":"IETF","designation":"RFC 8752","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8752.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8752.txt","https://www.rfc-editor.org/rfc/rfc8752.pdf"],"folder":"IETF/RFC-8752","files":{"pdf":{"path":"standards/IETF/RFC-8752/RFC-8752.pdf","sha256":"2ae8e5ea081793a8f19b6c3bb71e5d9213a3a82325994a0b08b3f819c183133a"},"txt":{"path":"standards/IETF/RFC-8752/RFC-8752.txt","sha256":"71d49677f7b34feb178c0817e9cf48c69d9787ed635612ac64a581fd6d0c175e"}},"tags":["nested-reference","unchanged"],"summary":"The Exploring Synergy between Content Aggregation and the Publisher\n Ecosystem (ESCAPE) Workshop was convened by the Internet Architecture\n Board (IAB) in July 2019. This report summarizes its significant\n points of discussion and identifies topics that may warrant further\n consideration.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved f","scope_keywords":["8752","archiving","attribute","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null}],"search_text":"IETF RFC 8752 The Exploring Synergy between Content Aggregation and the Publisher\n Ecosystem (ESCAPE) Workshop was convened by the Internet Architecture\n Board (IAB) in July 2019. This report summarizes its significant\n points of discussion and identifies topics that may warrant further\n consideration.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved f 8752 archiving attribute http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 5207","type":"specification","body":"IETF","designation":"RFC 5207","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5207.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5207.txt","https://www.rfc-editor.org/rfc/rfc5207.pdf"],"folder":"IETF/RFC-5207","files":{"txt":{"path":"standards/IETF/RFC-5207/RFC-5207.txt","sha256":"884e78d6d002579f0f3050ac57116f5d603ad9ee36152929651878de2953f927"}},"tags":["nested-reference","unchanged"],"summary":"The Host Identity Protocol (HIP) changes the way in which two\n Internet hosts communicate. One key advantage over other schemes is\n that HIP does not require modifications to the traditional network-\n layer functionality of the Internet, i.e., its routers. In the\n current Internet, however, many devices other than routers modify the\n traditional network-layer behavior of the Internet. These\n \"middleboxes\" are intermediary devices that perform functions other\n than the standard functions of an IP router on the datagram path\n between source and destination hosts. Whereas some types of\n middleboxes may not interfere with HIP at all, others can affect some\n aspects of HIP communication, and others can render HIP communication\n impossible. This document discusses the problems associated with HIP\n communication across network paths that include specific types of\n middleboxes, namely, network a","scope_keywords":["5207","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5770","folder":"IETF/RFC-5770","source":"IETF/RFC-5770/RFC-5770.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 5207 The Host Identity Protocol (HIP) changes the way in which two\n Internet hosts communicate. One key advantage over other schemes is\n that HIP does not require modifications to the traditional network-\n layer functionality of the Internet, i.e., its routers. In the\n current Internet, however, many devices other than routers modify the\n traditional network-layer behavior of the Internet. These\n \"middleboxes\" are intermediary devices that perform functions other\n than the standard functions of an IP router on the datagram path\n between source and destination hosts. Whereas some types of\n middleboxes may not interfere with HIP at all, others can affect some\n aspects of HIP communication, and others can render HIP communication\n impossible. This document discusses the problems associated with HIP\n communication across network paths that include specific types of\n middleboxes, namely, network a 5207 key path nested-reference unchanged"},{"id":"IETF RFC 8512","type":"specification","body":"IETF","designation":"RFC 8512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8512.txt","https://www.rfc-editor.org/rfc/rfc8512.pdf"],"folder":"IETF/RFC-8512","files":{"txt":{"path":"standards/IETF/RFC-8512/RFC-8512.txt","sha256":"4dfd17b7b6547eb225a8c3db0e3b4d69dc1e890419d5eaf485a8043d27f76cdb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG module for the Network Address\n Translation (NAT) function.\n\n Network Address Translation from IPv4 to IPv4 (NAT44), Network\n Address and Protocol Translation from IPv6 Clients to IPv4 Servers\n (NAT64), customer-side translator (CLAT), Stateless IP/ICMP\n Translation (SIIT), Explicit Address Mappings (EAM) for SIIT,\n IPv6-to-IPv6 Network Prefix Translation (NPTv6), and Destination NAT\n are covered in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this docume","scope_keywords":["8512","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null}],"search_text":"IETF RFC 8512 This document defines a YANG module for the Network Address\n Translation (NAT) function.\n\n Network Address Translation from IPv4 to IPv4 (NAT44), Network\n Address and Protocol Translation from IPv6 Clients to IPv4 Servers\n (NAT64), customer-side translator (CLAT), Stateless IP/ICMP\n Translation (SIIT), Explicit Address Mappings (EAM) for SIIT,\n IPv6-to-IPv6 Network Prefix Translation (NPTv6), and Destination NAT\n are covered in this document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this docume 8512 http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 5893","type":"specification","body":"IETF","designation":"RFC 5893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5893.txt","https://www.rfc-editor.org/rfc/rfc5893.pdf"],"folder":"IETF/RFC-5893","files":{"txt":{"path":"standards/IETF/RFC-5893/RFC-5893.txt","sha256":"d7daca034781d7f43c24f28c229aaba5aecbb76a68a6a59b70a5505adc23f42d"}},"tags":["nested-reference","unchanged"],"summary":"The use of right-to-left scripts in Internationalized Domain Names\n (IDNs) has presented several challenges. This memo provides a new\n Bidi rule for Internationalized Domain Names for Applications (IDNA)\n labels, based on the encountered problems with some scripts and some\n shortcomings in the 2003 IDNA Bidi criterion.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5893.\n\nCopyright Noti","scope_keywords":["5893","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5891","folder":"IETF/RFC-5891","source":"IETF/RFC-5891/RFC-5891.txt","version":null},{"body":"IETF","designation":"RFC 5892","folder":"IETF/RFC-5892","source":"IETF/RFC-5892/RFC-5892.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 5893 The use of right-to-left scripts in Internationalized Domain Names\n (IDNs) has presented several challenges. This memo provides a new\n Bidi rule for Internationalized Domain Names for Applications (IDNA)\n labels, based on the encountered problems with some scripts and some\n shortcomings in the 2003 IDNA Bidi criterion.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5893.\n\nCopyright Noti 5893 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2677","type":"specification","body":"IETF","designation":"RFC 2677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2677.txt","https://www.rfc-editor.org/rfc/rfc2677.pdf"],"folder":"IETF/RFC-2677","files":{"txt":{"path":"standards/IETF/RFC-2677/RFC-2677.txt","sha256":"7efd06a0fd0f53274329f70f44f7cf9176b2f80dea8effef0b1277edb0c55600"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for the Next Hop\n Resolution Protocol (NHRP) as defined in RFC 2332.","scope_keywords":["2677","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2677 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects for the Next Hop\n Resolution Protocol (NHRP) as defined in RFC 2332. 2677 key management nested-reference unchanged"},{"id":"IETF RFC 5472","type":"specification","body":"IETF","designation":"RFC 5472","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5472.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5472.txt","https://www.rfc-editor.org/rfc/rfc5472.pdf"],"folder":"IETF/RFC-5472","files":{"txt":{"path":"standards/IETF/RFC-5472/RFC-5472.txt","sha256":"d1f662f0e3981882303dd0385e2002d2cc7e51ff60b6cde56712f5180f85d890"}},"tags":["nested-reference","unchanged"],"summary":"In this document, we describe the applicability of the IP Flow\n Information eXport (IPFIX) protocol for a variety of applications.\n We show how applications can use IPFIX, describe the relevant\n Information Elements (IEs) for those applications, and present\n opportunities and limitations of the protocol. Furthermore, we\n describe relations of the IPFIX framework to other architectures and\n frameworks.\n\nZseby, et al Informational [Page 2]\n\f\nRFC 5472 IPFIX Applicability March 2009","scope_keywords":["5472","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5470","folder":"IETF/RFC-5470","source":"IETF/RFC-5470/RFC-5470.txt","version":null},{"body":"IETF","designation":"RFC 5471","folder":"IETF/RFC-5471","source":"IETF/RFC-5471/RFC-5471.txt","version":null},{"body":"IETF","designation":"RFC 5473","folder":"IETF/RFC-5473","source":"IETF/RFC-5473/RFC-5473.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5815","folder":"IETF/RFC-5815","source":"IETF/RFC-5815/RFC-5815.txt","version":null},{"body":"IETF","designation":"RFC 5982","folder":"IETF/RFC-5982","source":"IETF/RFC-5982/RFC-5982.txt","version":null},{"body":"IETF","designation":"RFC 6183","folder":"IETF/RFC-6183","source":"IETF/RFC-6183/RFC-6183.txt","version":null},{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6313","folder":"IETF/RFC-6313","source":"IETF/RFC-6313/RFC-6313.txt","version":null},{"body":"IETF","designation":"RFC 6526","folder":"IETF/RFC-6526","source":"IETF/RFC-6526/RFC-6526.txt","version":null},{"body":"IETF","designation":"RFC 6615","folder":"IETF/RFC-6615","source":"IETF/RFC-6615/RFC-6615.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6728","folder":"IETF/RFC-6728","source":"IETF/RFC-6728/RFC-6728.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7013","folder":"IETF/RFC-7013","source":"IETF/RFC-7013/RFC-7013.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 5472 In this document, we describe the applicability of the IP Flow\n Information eXport (IPFIX) protocol for a variety of applications.\n We show how applications can use IPFIX, describe the relevant\n Information Elements (IEs) for those applications, and present\n opportunities and limitations of the protocol. Furthermore, we\n describe relations of the IPFIX framework to other architectures and\n frameworks.\n\nZseby, et al Informational [Page 2]\n\f\nRFC 5472 IPFIX Applicability March 2009 5472 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 2688","type":"specification","body":"IETF","designation":"RFC 2688","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2688.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2688.txt","https://www.rfc-editor.org/rfc/rfc2688.pdf"],"folder":"IETF/RFC-2688","files":{"txt":{"path":"standards/IETF/RFC-2688/RFC-2688.txt","sha256":"91854dd838aaa31ff23122cd8cd093c1f2c2138e3a9ce51719e14a1cb7fa0f93"}},"tags":["nested-reference","unchanged"],"summary":"A set of companion documents describe an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1, 2, 3, 4]. The main components of the\n architecture are: a set of real-time encapsulation formats for\n asynchronous and synchronous low-bitrate links, a header compression\n architecture optimized for real-time flows, elements of negotiation\n protocols used between routers (or between hosts and routers), and\n announcement protocols used by applications to allow this negotiation\n to take place.\n\n This document defines the service mappings of the IETF Integrated\n Services for low-bitrate links, specifically the controlled load [5]\n and guaranteed [6] services. The approach takes the form of a set of\n guidelines and considerations for implementing these services, along\n with evaluation criteria for elements providing these","scope_keywords":["2688","delivery","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2688 A set of companion documents describe an architecture for providing\n integrated services over low-bitrate links, such as modem lines, ISDN\n B-channels, and sub-T1 links [1, 2, 3, 4]. The main components of the\n architecture are: a set of real-time encapsulation formats for\n asynchronous and synchronous low-bitrate links, a header compression\n architecture optimized for real-time flows, elements of negotiation\n protocols used between routers (or between hosts and routers), and\n announcement protocols used by applications to allow this negotiation\n to take place.\n\n This document defines the service mappings of the IETF Integrated\n Services for low-bitrate links, specifically the controlled load [5]\n and guaranteed [6] services. The approach takes the form of a set of\n guidelines and considerations for implementing these services, along\n with evaluation criteria for elements providing these 2688 delivery key path nested-reference unchanged"},{"id":"IETF RFC 269","type":"specification","body":"IETF","designation":"RFC 269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc269.txt","https://www.rfc-editor.org/rfc/rfc269.pdf"],"folder":"IETF/RFC-269","files":{"txt":{"path":"standards/IETF/RFC-269/RFC-269.txt","sha256":"b39163a9e0cec43b4ca16d739e642d525794e580df1fb5b5db1e1550ded45ef3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Brodie\nRequest for Comments #269 UCLA-NMC\nNIC # 7817 6 December 71\nCategories: File Transfer\nUpdates: 122, 238, 172\nObsoletes: None\n\n Some Experience with File Transfer\n\nAt UCLA-NMC we have recently completed implementation of a program which\nutilizes UCSB's storage capability via their Simple Minded File System\n(See RFC #122 by Jim White for a description of SMFS). The use of the\nprogram is detailed in Appendix A.\n\nWe learned a number of things in the implementation effort and\nsubsequent usage. We think a number of these apply towards the\ndevelopment of a net- word-wide File Transfer Protocol, and we hope to\nstimulate further dis- cussion of these issues. We discovered some\nthings in the UCSB protocol that we would like to see included in the\nnetwork-wide protocol, and we see some things that are in the currently\nproposed net protocol and are unfortunately absen","scope_keywords":["269"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3092","folder":"IETF/RFC-3092","source":"IETF/RFC-3092/RFC-3092.txt","version":null}],"search_text":"IETF RFC 269 Network Working Group H. Brodie\nRequest for Comments #269 UCLA-NMC\nNIC # 7817 6 December 71\nCategories: File Transfer\nUpdates: 122, 238, 172\nObsoletes: None\n\n Some Experience with File Transfer\n\nAt UCLA-NMC we have recently completed implementation of a program which\nutilizes UCSB's storage capability via their Simple Minded File System\n(See RFC #122 by Jim White for a description of SMFS). The use of the\nprogram is detailed in Appendix A.\n\nWe learned a number of things in the implementation effort and\nsubsequent usage. We think a number of these apply towards the\ndevelopment of a net- word-wide File Transfer Protocol, and we hope to\nstimulate further dis- cussion of these issues. We discovered some\nthings in the UCSB protocol that we would like to see included in the\nnetwork-wide protocol, and we see some things that are in the currently\nproposed net protocol and are unfortunately absen 269 nested-reference unchanged"},{"id":"IETF RFC 2692","type":"specification","body":"IETF","designation":"RFC 2692","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2692.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2692.txt","https://www.rfc-editor.org/rfc/rfc2692.pdf"],"folder":"IETF/RFC-2692","files":{"txt":{"path":"standards/IETF/RFC-2692/RFC-2692.txt","sha256":"6a88c1563590e8094bb37cda5c5d29ef70f8384e5a3a0528bce29c501826976d"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Simple Public Key Infrastructure [SPKI] Working Group is\n tasked with producing a certificate structure and operating procedure\n to meet the needs of the Internet community for trust management in\n as easy, simple and extensible a way as possible.\n\n The SPKI Working Group first established a list of things one might\n want to do with certificates (attached at the end of this document),\n and then summarized that list of desires into requirements. This\n document presents that summary of requirements.","scope_keywords":["2692","attribute","attributes","authorization","certificate","certificates","crl","hash","holder","key","keys","management","pki","revocation","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4398","folder":"IETF/RFC-4398","source":"IETF/RFC-4398/RFC-4398.txt","version":null}],"search_text":"IETF RFC 2692 The IETF Simple Public Key Infrastructure [SPKI] Working Group is\n tasked with producing a certificate structure and operating procedure\n to meet the needs of the Internet community for trust management in\n as easy, simple and extensible a way as possible.\n\n The SPKI Working Group first established a list of things one might\n want to do with certificates (attached at the end of this document),\n and then summarized that list of desires into requirements. This\n document presents that summary of requirements. 2692 attribute attributes authorization certificate certificates crl hash holder key keys management pki revocation signature trust nested-reference unchanged"},{"id":"IETF RFC 3346","type":"specification","body":"IETF","designation":"RFC 3346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3346.txt","https://www.rfc-editor.org/rfc/rfc3346.pdf"],"folder":"IETF/RFC-3346","files":{"txt":{"path":"standards/IETF/RFC-3346/RFC-3346.txt","sha256":"46d81ed0b543877c1b3551714a8fc2055459b8c02ff9ca9a4c7ac3705ea20209"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the applicability of Multiprotocol Label\n Switching (MPLS) to traffic engineering in IP networks. Special\n considerations for deployment of MPLS for traffic engineering in\n operational contexts are discussed and the limitations of the MPLS\n approach to traffic engineering are highlighted.\n\nBoyle, et al. Informational [Page 1]\n\f\nRFC 3346 Applicability Statement for Traffic Engineering August 2002","scope_keywords":["3346","algorithm","algorithms","attribute","attributes","management","path","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4128","folder":"IETF/RFC-4128","source":"IETF/RFC-4128/RFC-4128.txt","version":null},{"body":"IETF","designation":"RFC 4216","folder":"IETF/RFC-4216","source":"IETF/RFC-4216/RFC-4216.txt","version":null}],"search_text":"IETF RFC 3346 This document describes the applicability of Multiprotocol Label\n Switching (MPLS) to traffic engineering in IP networks. Special\n considerations for deployment of MPLS for traffic engineering in\n operational contexts are discussed and the limitations of the MPLS\n approach to traffic engineering are highlighted.\n\nBoyle, et al. Informational [Page 1]\n\f\nRFC 3346 Applicability Statement for Traffic Engineering August 2002 3346 algorithm algorithms attribute attributes management path policies subject nested-reference unchanged"},{"id":"IETF RFC 3785","type":"specification","body":"IETF","designation":"RFC 3785","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3785.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3785.txt","https://www.rfc-editor.org/rfc/rfc3785.pdf"],"folder":"IETF/RFC-3785","files":{"txt":{"path":"standards/IETF/RFC-3785/RFC-3785.txt","sha256":"95db04d6776800dc94fe34882fd7d00705f019d07b9be21083359481c9525434"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a common practice on how the existing metric\n of Interior Gateway Protocols (IGP) can be used as an alternative\n metric to the Traffic Engineering (TE) metric for Constraint Based\n Routing of MultiProtocol Label Switching (MPLS) Traffic Engineering\n tunnels. This effectively results in the ability to perform\n Constraint Based Routing with optimization of one metric (e.g., link\n bandwidth) for some Traffic Engineering tunnels (e.g., Data Trunks)\n while optimizing another metric (e.g., propagation delay) for some\n other tunnels with different requirements (e.g., Voice Trunks). No\n protocol extensions or modifications are required. This text\n documents current router implementations and deployment practices.\n\n1. Introduction\n\n Interior Gateway Protocol (IGP) routing protocols (OSPF and IS-IS) as\n well as MultiProtocol Label Switching (MPLS) signaling protocols\n (RSVP","scope_keywords":["3785","algorithm","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4105","folder":"IETF/RFC-4105","source":"IETF/RFC-4105/RFC-4105.txt","version":null},{"body":"IETF","designation":"RFC 4657","folder":"IETF/RFC-4657","source":"IETF/RFC-4657/RFC-4657.txt","version":null},{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null}],"search_text":"IETF RFC 3785 This document describes a common practice on how the existing metric\n of Interior Gateway Protocols (IGP) can be used as an alternative\n metric to the Traffic Engineering (TE) metric for Constraint Based\n Routing of MultiProtocol Label Switching (MPLS) Traffic Engineering\n tunnels. This effectively results in the ability to perform\n Constraint Based Routing with optimization of one metric (e.g., link\n bandwidth) for some Traffic Engineering tunnels (e.g., Data Trunks)\n while optimizing another metric (e.g., propagation delay) for some\n other tunnels with different requirements (e.g., Voice Trunks). No\n protocol extensions or modifications are required. This text\n documents current router implementations and deployment practices.\n\n1. Introduction\n\n Interior Gateway Protocol (IGP) routing protocols (OSPF and IS-IS) as\n well as MultiProtocol Label Switching (MPLS) signaling protocols\n (RSVP 3785 algorithm path policies nested-reference unchanged"},{"id":"IETF RFC 4655","type":"specification","body":"IETF","designation":"RFC 4655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4655.txt","https://www.rfc-editor.org/rfc/rfc4655.pdf"],"folder":"IETF/RFC-4655","files":{"txt":{"path":"standards/IETF/RFC-4655/RFC-4655.txt","sha256":"31f08c35c720fe4370e07d1ac80da712a0db206a8c7b0a05334e8428750d5701"}},"tags":["nested-reference","unchanged"],"summary":"Constraint-based path computation is a fundamental building block for\n traffic engineering systems such as Multiprotocol Label Switching\n (MPLS) and Generalized Multiprotocol Label Switching (GMPLS)\n networks. Path computation in large, multi-domain, multi-region, or\n multi-layer networks is complex and may require special computational\n components and cooperation between the different network domains.\n\n This document specifies the architecture for a Path Computation\n Element (PCE)-based model to address this problem space. This\n document does not attempt to provide a detailed description of all\n the architectural components, but rather it describes a set of\n building blocks for the PCE architecture from which solutions may be\n constructed.","scope_keywords":["4655","management","path","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4657","folder":"IETF/RFC-4657","source":"IETF/RFC-4657/RFC-4657.txt","version":null},{"body":"IETF","designation":"RFC 4674","folder":"IETF/RFC-4674","source":"IETF/RFC-4674/RFC-4674.txt","version":null},{"body":"IETF","designation":"RFC 4726","folder":"IETF/RFC-4726","source":"IETF/RFC-4726/RFC-4726.txt","version":null},{"body":"IETF","designation":"RFC 4920","folder":"IETF/RFC-4920","source":"IETF/RFC-4920/RFC-4920.txt","version":null},{"body":"IETF","designation":"RFC 4927","folder":"IETF/RFC-4927","source":"IETF/RFC-4927/RFC-4927.txt","version":null},{"body":"IETF","designation":"RFC 5088","folder":"IETF/RFC-5088","source":"IETF/RFC-5088/RFC-5088.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5253","folder":"IETF/RFC-5253","source":"IETF/RFC-5253/RFC-5253.txt","version":null},{"body":"IETF","designation":"RFC 5316","folder":"IETF/RFC-5316","source":"IETF/RFC-5316/RFC-5316.txt","version":null},{"body":"IETF","designation":"RFC 5376","folder":"IETF/RFC-5376","source":"IETF/RFC-5376/RFC-5376.txt","version":null},{"body":"IETF","designation":"RFC 5392","folder":"IETF/RFC-5392","source":"IETF/RFC-5392/RFC-5392.txt","version":null},{"body":"IETF","designation":"RFC 5440","folder":"IETF/RFC-5440","source":"IETF/RFC-5440/RFC-5440.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 4655 Constraint-based path computation is a fundamental building block for\n traffic engineering systems such as Multiprotocol Label Switching\n (MPLS) and Generalized Multiprotocol Label Switching (GMPLS)\n networks. Path computation in large, multi-domain, multi-region, or\n multi-layer networks is complex and may require special computational\n components and cooperation between the different network domains.\n\n This document specifies the architecture for a Path Computation\n Element (PCE)-based model to address this problem space. This\n document does not attempt to provide a detailed description of all\n the architectural components, but rather it describes a set of\n building blocks for the PCE architecture from which solutions may be\n constructed. 4655 management path policies policy nested-reference unchanged"},{"id":"IETF RFC 2704","type":"specification","body":"IETF","designation":"RFC 2704","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2704.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2704.txt","https://www.rfc-editor.org/rfc/rfc2704.pdf"],"folder":"IETF/RFC-2704","files":{"txt":{"path":"standards/IETF/RFC-2704/RFC-2704.txt","sha256":"fd05c7bd5ba8bb0d1682d09d62b2fc0b617d818e7e7ec83c694ba5048c838230"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes version 2 of the KeyNote trust-management system.\n It specifies the syntax and semantics of KeyNote `assertions',\n describes `action attribute' processing, and outlines the application\n architecture into which a KeyNote implementation can be fit. The\n KeyNote architecture and language are useful as building blocks for\n the trust management aspects of a variety of Internet protocols and\n services.\n\n1. Introduction\n\n Trust management, introduced in the PolicyMaker system [BFL96], is a\n unified approach to specifying and interpreting security policies,\n credentials, and relationships; it allows direct authorization of\n security-critical actions. A trust-management system provides\n standard, general-purpose mechanisms for specifying application\n security policies and credentials. Trust-management credentials\n describe a specific delegation of trust and subsume the role of","scope_keywords":["2704","attribute","authorization","certificate","certificates","credential","credentials","holder","key","keys","management","policies","policy","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2792","folder":"IETF/RFC-2792","source":"IETF/RFC-2792/RFC-2792.txt","version":null},{"body":"IETF","designation":"RFC 2903","folder":"IETF/RFC-2903","source":"IETF/RFC-2903/RFC-2903.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 6042","folder":"IETF/RFC-6042","source":"IETF/RFC-6042/RFC-6042.txt","version":null}],"search_text":"IETF RFC 2704 This memo describes version 2 of the KeyNote trust-management system.\n It specifies the syntax and semantics of KeyNote `assertions',\n describes `action attribute' processing, and outlines the application\n architecture into which a KeyNote implementation can be fit. The\n KeyNote architecture and language are useful as building blocks for\n the trust management aspects of a variety of Internet protocols and\n services.\n\n1. Introduction\n\n Trust management, introduced in the PolicyMaker system [BFL96], is a\n unified approach to specifying and interpreting security policies,\n credentials, and relationships; it allows direct authorization of\n security-critical actions. A trust-management system provides\n standard, general-purpose mechanisms for specifying application\n security policies and credentials. Trust-management credentials\n describe a specific delegation of trust and subsume the role of 2704 attribute authorization certificate certificates credential credentials holder key keys management policies policy signature trust nested-reference unchanged"},{"id":"IETF RFC 2726","type":"specification","body":"IETF","designation":"RFC 2726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2726.txt","https://www.rfc-editor.org/rfc/rfc2726.pdf"],"folder":"IETF/RFC-2726","files":{"txt":{"path":"standards/IETF/RFC-2726/RFC-2726.txt","sha256":"436eb5de270e58b30f667a7aee4bd960a99a5ccfc6cb5cbfade56d700a95fead"}},"tags":["nested-reference","unchanged"],"summary":"This document presents the proposal for a stronger authentication\n method of the updates of the RIPE database based on digital\n signatures. The proposal tries to be as general as possible as far as\n digital signing methods are concerned, however, it concentrates\n mainly on PGP, as the first method to be implemented. The proposal\n is the result of the discussions within the RIPE DBSEC Task Force.\n\n1. Rationale\n\n An increasing need has been identified for a stronger authentication\n of the database maintainer upon database updates (addition,\n modification and deletion of objects). The existing authentication\n methods have serious security problems: the MAIL-FROM has the\n drawback that a mail header is very easy to forge whereas CRYPT-PW is\n exposed to message interception, since the password is sent\n unencrypted in the update mail message.\n\n The goal was to implement a digital signature mec","scope_keywords":["2726","attribute","attributes","authentication","authorization","certificate","certificates","key","keys","presentation","signature","signatures","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2769","folder":"IETF/RFC-2769","source":"IETF/RFC-2769/RFC-2769.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2726 This document presents the proposal for a stronger authentication\n method of the updates of the RIPE database based on digital\n signatures. The proposal tries to be as general as possible as far as\n digital signing methods are concerned, however, it concentrates\n mainly on PGP, as the first method to be implemented. The proposal\n is the result of the discussions within the RIPE DBSEC Task Force.\n\n1. Rationale\n\n An increasing need has been identified for a stronger authentication\n of the database maintainer upon database updates (addition,\n modification and deletion of objects). The existing authentication\n methods have serious security problems: the MAIL-FROM has the\n drawback that a mail header is very easy to forge whereas CRYPT-PW is\n exposed to message interception, since the password is sent\n unencrypted in the update mail message.\n\n The goal was to implement a digital signature mec 2726 attribute attributes authentication authorization certificate certificates key keys presentation signature signatures trust nested-reference unchanged"},{"id":"IETF RFC 3677","type":"specification","body":"IETF","designation":"RFC 3677","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3677.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3677.txt","https://www.rfc-editor.org/rfc/rfc3677.pdf"],"folder":"IETF/RFC-3677","files":{"txt":{"path":"standards/IETF/RFC-3677/RFC-3677.txt","sha256":"411c75b33b5f2783a38c00e51d5c0eac21dfa4a6d23e40d5489710e8e44a319f"}},"tags":["nested-reference","unchanged"],"summary":"This memo outlines the process by which the IETF makes a selection of\n an Internet Society (ISOC) Board of Trustees appointment.\n\n1. Introduction\n\n The Internet Society (ISOC) provides organizational and financial\n support for the IETF. As stipulated in ISOC's by-laws the IETF is\n called upon to name 3 Trustees to its Board (BoT), with staggered 3\n year terms. This requires that the IETF name one Trustee each year.\n\n This memo outlines the process by which the IETF makes that\n selection. This process will also be used in the event of mid-term\n vacancies that may arise with IETF nominated Board positions.","scope_keywords":["3677","delivery","holder","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4071","folder":"IETF/RFC-4071","source":"IETF/RFC-4071/RFC-4071.txt","version":null},{"body":"IETF","designation":"RFC 4333","folder":"IETF/RFC-4333","source":"IETF/RFC-4333/RFC-4333.txt","version":null}],"search_text":"IETF RFC 3677 This memo outlines the process by which the IETF makes a selection of\n an Internet Society (ISOC) Board of Trustees appointment.\n\n1. Introduction\n\n The Internet Society (ISOC) provides organizational and financial\n support for the IETF. As stipulated in ISOC's by-laws the IETF is\n called upon to name 3 Trustees to its Board (BoT), with staggered 3\n year terms. This requires that the IETF name one Trustee each year.\n\n This memo outlines the process by which the IETF makes that\n selection. This process will also be used in the event of mid-term\n vacancies that may arise with IETF nominated Board positions. 3677 delivery holder policies trust nested-reference unchanged"},{"id":"IETF RFC 2728","type":"specification","body":"IETF","designation":"RFC 2728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2728.txt","https://www.rfc-editor.org/rfc/rfc2728.pdf"],"folder":"IETF/RFC-2728","files":{"txt":{"path":"standards/IETF/RFC-2728/RFC-2728.txt","sha256":"cd80f81b51c7c7cf1aaa8639cf3520ca261148905aa2ef2798af25018ac9f511"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a method for broadcasting IP data in a\n unidirectional manner using the vertical blanking interval of\n television signals. It includes a description for compressing IP\n headers on unidirectional networks, a framing protocol identical to\n SLIP, a forward error correction scheme, and the NABTS byte\n structures.\n\n2. Introduction\n\n This RFC proposes several protocols to be used in the transmission of\n IP datagrams using the Vertical Blanking Interval (VBI) of a\n television signal. The VBI is a non-viewable portion of the\n television signal that can be used to provide point-to-multipoint IP\n data services which will relieve congestion and traffic in the\n traditional Internet access networks. Wherever possible these\n protocols make use of existing RFC standards and non-standards.\n\n Traditionally, point-to-point connections (TCP/IP) have been used\n even for the transmiss","scope_keywords":["2728","delivery","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2728 This document describes a method for broadcasting IP data in a\n unidirectional manner using the vertical blanking interval of\n television signals. It includes a description for compressing IP\n headers on unidirectional networks, a framing protocol identical to\n SLIP, a forward error correction scheme, and the NABTS byte\n structures.\n\n2. Introduction\n\n This RFC proposes several protocols to be used in the transmission of\n IP datagrams using the Vertical Blanking Interval (VBI) of a\n television signal. The VBI is a non-viewable portion of the\n television signal that can be used to provide point-to-multipoint IP\n data services which will relieve congestion and traffic in the\n traditional Internet access networks. Wherever possible these\n protocols make use of existing RFC standards and non-standards.\n\n Traditionally, point-to-point connections (TCP/IP) have been used\n even for the transmiss 2728 delivery key nested-reference unchanged"},{"id":"IETF RFC 2729","type":"specification","body":"IETF","designation":"RFC 2729","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2729.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2729.txt","https://www.rfc-editor.org/rfc/rfc2729.pdf"],"folder":"IETF/RFC-2729","files":{"txt":{"path":"standards/IETF/RFC-2729/RFC-2729.txt","sha256":"1a28b07a04867a0b7686c7d21d3f9d616e5ca75cbc85b7d01d4792d3a4f784ec"}},"tags":["nested-reference","unchanged"],"summary":"The intention of this memo is to define a classification system for\n the communication requirements of any large-scale multicast\n application (LSMA). It is very unlikely one protocol can achieve a\n compromise between the diverse requirements of all the parties\n involved in any LSMA. It is therefore necessary to understand the\n worst-case scenarios in order to minimize the range of protocols\n needed. Dynamic protocol adaptation is likely to be necessary which\n will require logic to map particular combinations of requirements to\n particular mechanisms. Standardizing the way that applications\n define their requirements is a necessary step towards this.\n Classification is a first step towards standardization.\n\nBagnall, et al. Informational [Page 1]\n\f\nRFC 2729 Taxonomy of Communication Requirements December 1999","scope_keywords":["2729","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3170","folder":"IETF/RFC-3170","source":"IETF/RFC-3170/RFC-3170.txt","version":null}],"search_text":"IETF RFC 2729 The intention of this memo is to define a classification system for\n the communication requirements of any large-scale multicast\n application (LSMA). It is very unlikely one protocol can achieve a\n compromise between the diverse requirements of all the parties\n involved in any LSMA. It is therefore necessary to understand the\n worst-case scenarios in order to minimize the range of protocols\n needed. Dynamic protocol adaptation is likely to be necessary which\n will require logic to map particular combinations of requirements to\n particular mechanisms. Standardizing the way that applications\n define their requirements is a necessary step towards this.\n Classification is a first step towards standardization.\n\nBagnall, et al. Informational [Page 1]\n\f\nRFC 2729 Taxonomy of Communication Requirements December 1999 2729 identification nested-reference unchanged"},{"id":"IETF RFC 2735","type":"specification","body":"IETF","designation":"RFC 2735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2735.txt","https://www.rfc-editor.org/rfc/rfc2735.pdf"],"folder":"IETF/RFC-2735","files":{"txt":{"path":"standards/IETF/RFC-2735/RFC-2735.txt","sha256":"1b5606f5c4d52b0182390df85b880241c21cfa10b78cad460581709c82e62cf2"}},"tags":["nested-reference","unchanged"],"summary":"The NBMA Next Hop Resolution Protocol (NHRP) is used to determine the\n NBMA subnetwork addresses of the \"NBMA next hop\" towards a public\n internetworking layer address (see [1]). This document describes the\n enhancements necessary to enable NHRP to perform the same function\n for private internetworking layer addresses available within the\n framework of a Virtual Private Network (VPN) service on a shared NBMA\n network.\n\n1. Introduction\n\n NHRP is a public internetworking layer based resolution protocol.\n There is an implicit understanding in [1] that a control message\n applies to the public address space.\n\n Service Providers of Virtual Private Network (VPN) services will\n offer VPN participants specific service level agreements (SLA) which\n may include, for example, dedicated routing functions and/or specific\n QoS levels. A particularly important feature of a VPN service is the\n ability to","scope_keywords":["2735","identification","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2735 The NBMA Next Hop Resolution Protocol (NHRP) is used to determine the\n NBMA subnetwork addresses of the \"NBMA next hop\" towards a public\n internetworking layer address (see [1]). This document describes the\n enhancements necessary to enable NHRP to perform the same function\n for private internetworking layer addresses available within the\n framework of a Virtual Private Network (VPN) service on a shared NBMA\n network.\n\n1. Introduction\n\n NHRP is a public internetworking layer based resolution protocol.\n There is an implicit understanding in [1] that a control message\n applies to the public address space.\n\n Service Providers of Virtual Private Network (VPN) services will\n offer VPN participants specific service level agreements (SLA) which\n may include, for example, dedicated routing functions and/or specific\n QoS levels. A particularly important feature of a VPN service is the\n ability to 2735 identification key path nested-reference unchanged"},{"id":"IETF RFC 6366","type":"specification","body":"IETF","designation":"RFC 6366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6366.txt","https://www.rfc-editor.org/rfc/rfc6366.pdf"],"folder":"IETF/RFC-6366","files":{"txt":{"path":"standards/IETF/RFC-6366/RFC-6366.txt","sha256":"3ce210d03a38ef4c92e1e1245f3012aaee76665beae62454b1f8255bb56a6402"}},"tags":["nested-reference","unchanged"],"summary":"This document provides specific requirements for an Internet audio\n codec. These requirements address quality, sampling rate, bit-rate,\n and packet-loss robustness, as well as other desirable properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6366.\n\nCopyright Notice\n\n Copyright (","scope_keywords":["6366","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6716","folder":"IETF/RFC-6716","source":"IETF/RFC-6716/RFC-6716.txt","version":null}],"search_text":"IETF RFC 6366 This document provides specific requirements for an Internet audio\n codec. These requirements address quality, sampling rate, bit-rate,\n and packet-loss robustness, as well as other desirable properties.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6366.\n\nCopyright Notice\n\n Copyright ( 6366 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2742","type":"specification","body":"IETF","designation":"RFC 2742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2742.txt","https://www.rfc-editor.org/rfc/rfc2742.pdf"],"folder":"IETF/RFC-2742","files":{"txt":{"path":"standards/IETF/RFC-2742/RFC-2742.txt","sha256":"c83f3a7a8cd77557d6558750b298d3d9617f3115d5d9355f48334d356e292bab"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects managing SNMP agents that use the\n Agent Extensibility (AgentX) Protocol.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SMIv2, and semantically identical to the peer SMIv1\n definitions.","scope_keywords":["2742","management","registered","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2742 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects managing SNMP agents that use the\n Agent Extensibility (AgentX) Protocol.\n\n This memo specifies a MIB module in a manner that is both compliant\n to the SMIv2, and semantically identical to the peer SMIv1\n definitions. 2742 management registered timestamp nested-reference unchanged"},{"id":"IETF RFC 2744","type":"specification","body":"IETF","designation":"RFC 2744","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2744.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2744.txt","https://www.rfc-editor.org/rfc/rfc2744.pdf"],"folder":"IETF/RFC-2744","files":{"txt":{"path":"standards/IETF/RFC-2744/RFC-2744.txt","sha256":"494d9f48349271453cbec3d87f541d8302dc7ad338286b03dd77207700bac74b"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies C language bindings for Version 2, Update 1\n of the Generic Security Service Application Program Interface (GSS-\n API), which is described at a language-independent conceptual level\n in RFC-2743 [GSSAPI]. It obsoletes RFC-1509, making specific\n incremental changes in response to implementation experience and\n liaison requests. It is intended, therefore, that this memo or a\n successor version thereof will become the basis for subsequent\n progression of the GSS-API specification on the standards track.\n\n The Generic Security Service Application Programming Interface\n provides security services to its callers, and is intended for\n implementation atop a variety of underlying cryptographic mechanisms.\n Typically, GSS-API callers will be application protocols into which\n security enhancements are integrated through invocation of services\n provided by the GSS-API. The GS","scope_keywords":["2744","authentication","credential","credentials","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 3631","folder":"IETF/RFC-3631","source":"IETF/RFC-3631/RFC-3631.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4121","folder":"IETF/RFC-4121","source":"IETF/RFC-4121/RFC-4121.txt","version":null},{"body":"IETF","designation":"RFC 4401","folder":"IETF/RFC-4401","source":"IETF/RFC-4401/RFC-4401.txt","version":null},{"body":"IETF","designation":"RFC 4402","folder":"IETF/RFC-4402","source":"IETF/RFC-4402/RFC-4402.txt","version":null},{"body":"IETF","designation":"RFC 5056","folder":"IETF/RFC-5056","source":"IETF/RFC-5056/RFC-5056.txt","version":null},{"body":"IETF","designation":"RFC 5554","folder":"IETF/RFC-5554","source":"IETF/RFC-5554/RFC-5554.txt","version":null},{"body":"IETF","designation":"RFC 5587","folder":"IETF/RFC-5587","source":"IETF/RFC-5587/RFC-5587.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null}],"search_text":"IETF RFC 2744 This document specifies C language bindings for Version 2, Update 1\n of the Generic Security Service Application Program Interface (GSS-\n API), which is described at a language-independent conceptual level\n in RFC-2743 [GSSAPI]. It obsoletes RFC-1509, making specific\n incremental changes in response to implementation experience and\n liaison requests. It is intended, therefore, that this memo or a\n successor version thereof will become the basis for subsequent\n progression of the GSS-API specification on the standards track.\n\n The Generic Security Service Application Programming Interface\n provides security services to its callers, and is intended for\n implementation atop a variety of underlying cryptographic mechanisms.\n Typically, GSS-API callers will be application protocols into which\n security enhancements are integrated through invocation of services\n provided by the GSS-API. The GS 2744 authentication credential credentials key keys management nested-reference unchanged"},{"id":"IETF RFC 3097","type":"specification","body":"IETF","designation":"RFC 3097","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3097.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3097.txt","https://www.rfc-editor.org/rfc/rfc3097.pdf"],"folder":"IETF/RFC-3097","files":{"txt":{"path":"standards/IETF/RFC-3097/RFC-3097.txt","sha256":"edcddf818dce3c95e8d3d71b3f7453813fd3671f9dc568a13250c48ea5ebdef6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braden\nRequest for Comments: 3097 ISI\nUpdates: 2747 L. Zhang\nCategory: Standards Track UCLA\n April 2001\n\n RSVP Cryptographic Authentication --\n Updated Message Type Value\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo resolves a duplication in the assignment of RSVP Message\n Types, by changing the Message Types assigned by RFC 2747 to\n Challenge and Integrity Response messages.\n\n1. Introduction\n\n RFC 2747 (\"RSVP Cryptographic Authentication\") [RFC27","scope_keywords":["3097","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 3097 Network Working Group R. Braden\nRequest for Comments: 3097 ISI\nUpdates: 2747 L. Zhang\nCategory: Standards Track UCLA\n April 2001\n\n RSVP Cryptographic Authentication --\n Updated Message Type Value\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2001). All Rights Reserved.\n\nAbstract\n\n This memo resolves a duplication in the assignment of RSVP Message\n Types, by changing the Message Types assigned by RFC 2747 to\n Challenge and Integrity Response messages.\n\n1. Introduction\n\n RFC 2747 (\"RSVP Cryptographic Authentication\") [RFC27 3097 authentication nested-reference unchanged"},{"id":"IETF RFC 3535","type":"specification","body":"IETF","designation":"RFC 3535","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3535.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3535.txt","https://www.rfc-editor.org/rfc/rfc3535.pdf"],"folder":"IETF/RFC-3535","files":{"txt":{"path":"standards/IETF/RFC-3535/RFC-3535.txt","sha256":"9350c5c2cab901e8ca901de1859a55275c5faace09d54f28d4b4fa526dfcb0cf"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on Network Management. The workshop was\n hosted by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The\n goal of the workshop was to continue the important dialog started\n between network operators and protocol developers, and to guide the\n IETFs focus on future work regarding network management. This report\n summarizes the discussions and lists the conclusions and\n recommendations to the Internet Engineering Task Force (IETF)\n community.\n\nSchoenwaelder Informational [Page 1]\n\f\nRFC 3535 IAB Network Management Workshop May 2003","scope_keywords":["3535","http","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5706","folder":"IETF/RFC-5706","source":"IETF/RFC-5706/RFC-5706.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6550","folder":"IETF/RFC-6550","source":"IETF/RFC-6550/RFC-6550.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3535 This document provides an overview of a workshop held by the Internet\n Architecture Board (IAB) on Network Management. The workshop was\n hosted by CNRI in Reston, VA, USA on June 4 thru June 6, 2002. The\n goal of the workshop was to continue the important dialog started\n between network operators and protocol developers, and to guide the\n IETFs focus on future work regarding network management. This report\n summarizes the discussions and lists the conclusions and\n recommendations to the Internet Engineering Task Force (IETF)\n community.\n\nSchoenwaelder Informational [Page 1]\n\f\nRFC 3535 IAB Network Management Workshop May 2003 3535 http management policies policy nested-reference unchanged"},{"id":"IETF RFC 2758","type":"specification","body":"IETF","designation":"RFC 2758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2758.txt","https://www.rfc-editor.org/rfc/rfc2758.pdf"],"folder":"IETF/RFC-2758","files":{"txt":{"path":"standards/IETF/RFC-2758/RFC-2758.txt","sha256":"6bcf5a296ef50d808a0f04d4dcf926997b249b8d98781f666657bec7777c82de"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a Management Information Base (MIB) for performance\n monitoring of Service Level Agreements (SLAs) defined via policy\n definitions. The MIB defined herein focuses on defining a set of\n objects for monitoring SLAs and not on replication of the content of\n the policy definitions being monitored. The goal of the MIB defined\n within this document is to defined statistics related to a policy\n rule definition for reporting on the effect that a policy rule has on\n a system and to defined a method of monitoring this data.","scope_keywords":["2758","key","management","policy","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2758 This memo defines a Management Information Base (MIB) for performance\n monitoring of Service Level Agreements (SLAs) defined via policy\n definitions. The MIB defined herein focuses on defining a set of\n objects for monitoring SLAs and not on replication of the content of\n the policy definitions being monitored. The goal of the MIB defined\n within this document is to defined statistics related to a policy\n rule definition for reporting on the effect that a policy rule has on\n a system and to defined a method of monitoring this data. 2758 key management policy profile nested-reference unchanged"},{"id":"IETF RFC 4977","type":"specification","body":"IETF","designation":"RFC 4977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4977.txt","https://www.rfc-editor.org/rfc/rfc4977.pdf"],"folder":"IETF/RFC-4977","files":{"txt":{"path":"standards/IETF/RFC-4977/RFC-4977.txt","sha256":"129b23fc0a8595a8cd03db4afa5eb15ffabe32b897b1642412091843ad0e766f"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the issues associated with mobility\n management for dual stack mobile nodes. Currently, two mobility\n management protocols are defined for IPv4 and IPv6. Deploying both\n in a dual stack mobile node introduces a number of problems.\n Deployment and operational issues motivate the use of a single\n mobility management protocol. This document discusses such\n motivations. The document also discusses requirements for the Mobile\n IPv4 (MIPv4) and Mobile IPv6 (MIPv6) protocol so that they can\n support mobility management for a dual stack node.","scope_keywords":["4977","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5555","folder":"IETF/RFC-5555","source":"IETF/RFC-5555/RFC-5555.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null}],"search_text":"IETF RFC 4977 This document discusses the issues associated with mobility\n management for dual stack mobile nodes. Currently, two mobility\n management protocols are defined for IPv4 and IPv6. Deploying both\n in a dual stack mobile node introduces a number of problems.\n Deployment and operational issues motivate the use of a single\n mobility management protocol. This document discusses such\n motivations. The document also discusses requirements for the Mobile\n IPv4 (MIPv4) and Mobile IPv6 (MIPv6) protocol so that they can\n support mobility management for a dual stack node. 4977 management subject nested-reference unchanged"},{"id":"IETF RFC 2778","type":"specification","body":"IETF","designation":"RFC 2778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2778.txt","https://www.rfc-editor.org/rfc/rfc2778.pdf"],"folder":"IETF/RFC-2778","files":{"txt":{"path":"standards/IETF/RFC-2778/RFC-2778.txt","sha256":"2a151b9a638679c30d8bec975a9e73990481ff31680f5953d4e383602da5f7d2"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an abstract model for a presence and instant\n messaging system. It defines the various entities involved, defines\n terminology, and outlines the services provided by the system. The\n goal is to provide a common vocabulary for further work on\n requirements for protocols and markup for presence and instant\n messaging.\n\n1. Introduction\n\n A presence and instant messaging system allows users to subscribe to\n each other and be notified of changes in state, and for users to send\n each other short instant messages. To facilitate development of a\n suite of protocols to provide this service, we believe that it is\n valuable to first develop a model for the system. The model consists\n of the various entities involved, descriptions of the basic functions\n they provide, and most importantly, definition of a vocabulary which\n can be used to facilitate discussion.\n\n We note that th","scope_keywords":["2778"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2779","folder":"IETF/RFC-2779","source":"IETF/RFC-2779/RFC-2779.txt","version":null},{"body":"IETF","designation":"RFC 3428","folder":"IETF/RFC-3428","source":"IETF/RFC-3428/RFC-3428.txt","version":null},{"body":"IETF","designation":"RFC 3856","folder":"IETF/RFC-3856","source":"IETF/RFC-3856/RFC-3856.txt","version":null},{"body":"IETF","designation":"RFC 3858","folder":"IETF/RFC-3858","source":"IETF/RFC-3858/RFC-3858.txt","version":null},{"body":"IETF","designation":"RFC 3859","folder":"IETF/RFC-3859","source":"IETF/RFC-3859/RFC-3859.txt","version":null},{"body":"IETF","designation":"RFC 3860","folder":"IETF/RFC-3860","source":"IETF/RFC-3860/RFC-3860.txt","version":null},{"body":"IETF","designation":"RFC 3861","folder":"IETF/RFC-3861","source":"IETF/RFC-3861/RFC-3861.txt","version":null},{"body":"IETF","designation":"RFC 3863","folder":"IETF/RFC-3863","source":"IETF/RFC-3863/RFC-3863.txt","version":null},{"body":"IETF","designation":"RFC 3903","folder":"IETF/RFC-3903","source":"IETF/RFC-3903/RFC-3903.txt","version":null},{"body":"IETF","designation":"RFC 3921","folder":"IETF/RFC-3921","source":"IETF/RFC-3921/RFC-3921.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3923","folder":"IETF/RFC-3923","source":"IETF/RFC-3923/RFC-3923.txt","version":null},{"body":"IETF","designation":"RFC 3994","folder":"IETF/RFC-3994","source":"IETF/RFC-3994/RFC-3994.txt","version":null},{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4479","folder":"IETF/RFC-4479","source":"IETF/RFC-4479/RFC-4479.txt","version":null},{"body":"IETF","designation":"RFC 4480","folder":"IETF/RFC-4480","source":"IETF/RFC-4480/RFC-4480.txt","version":null},{"body":"IETF","designation":"RFC 4481","folder":"IETF/RFC-4481","source":"IETF/RFC-4481/RFC-4481.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5025","folder":"IETF/RFC-5025","source":"IETF/RFC-5025/RFC-5025.txt","version":null},{"body":"IETF","designation":"RFC 5262","folder":"IETF/RFC-5262","source":"IETF/RFC-5262/RFC-5262.txt","version":null},{"body":"IETF","designation":"RFC 5263","folder":"IETF/RFC-5263","source":"IETF/RFC-5263/RFC-5263.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 6121","folder":"IETF/RFC-6121","source":"IETF/RFC-6121/RFC-6121.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 2778 This document defines an abstract model for a presence and instant\n messaging system. It defines the various entities involved, defines\n terminology, and outlines the services provided by the system. The\n goal is to provide a common vocabulary for further work on\n requirements for protocols and markup for presence and instant\n messaging.\n\n1. Introduction\n\n A presence and instant messaging system allows users to subscribe to\n each other and be notified of changes in state, and for users to send\n each other short instant messages. To facilitate development of a\n suite of protocols to provide this service, we believe that it is\n valuable to first develop a model for the system. The model consists\n of the various entities involved, descriptions of the basic functions\n they provide, and most importantly, definition of a vocabulary which\n can be used to facilitate discussion.\n\n We note that th 2778 nested-reference unchanged"},{"id":"IETF RFC 4079","type":"specification","body":"IETF","designation":"RFC 4079","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4079.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4079.txt","https://www.rfc-editor.org/rfc/rfc4079.pdf"],"folder":"IETF/RFC-4079","files":{"txt":{"path":"standards/IETF/RFC-4079/RFC-4079.txt","sha256":"894a86a6d623a998ba963a4f98816ed94b230f4aa5a43a96475c2343346cafd5"}},"tags":["nested-reference","unchanged"],"summary":"GEOPRIV defines the concept of a 'using protocol' -- a protocol that\n carries GEOPRIV location objects. GEOPRIV also defines various\n scenarios for the distribution of location objects that require the\n concepts of subscriptions and asynchronous notifications. This\n document examines some existing IETF work on the concept of presence,\n shows how presence architectures map onto GEOPRIV architectures, and\n moreover demonstrates that tools already developed for presence could\n be reused to simplify the standardization and implementation of\n GEOPRIV.","scope_keywords":["4079","delivery","holder","pid","policies","policy","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null},{"body":"IETF","designation":"RFC 6973","folder":"IETF/RFC-6973","source":"IETF/RFC-6973/RFC-6973.txt","version":null}],"search_text":"IETF RFC 4079 GEOPRIV defines the concept of a 'using protocol' -- a protocol that\n carries GEOPRIV location objects. GEOPRIV also defines various\n scenarios for the distribution of location objects that require the\n concepts of subscriptions and asynchronous notifications. This\n document examines some existing IETF work on the concept of presence,\n shows how presence architectures map onto GEOPRIV architectures, and\n moreover demonstrates that tools already developed for presence could\n be reused to simplify the standardization and implementation of\n GEOPRIV. 4079 delivery holder pid policies policy profile nested-reference unchanged"},{"id":"IETF RFC 4321","type":"specification","body":"IETF","designation":"RFC 4321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4321.txt","https://www.rfc-editor.org/rfc/rfc4321.pdf"],"folder":"IETF/RFC-4321","files":{"txt":{"path":"standards/IETF/RFC-4321/RFC-4321.txt","sha256":"c7f66c24e0d5e623922e887890745864eec473ef4aa757057331999808fcad73"}},"tags":["nested-reference","unchanged"],"summary":"This document describes several problems that have been identified\n with the Session Initiation Protocol's (SIP) non-INVITE transaction.","scope_keywords":["4321","algorithm","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4320","folder":"IETF/RFC-4320","source":"IETF/RFC-4320/RFC-4320.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null}],"search_text":"IETF RFC 4321 This document describes several problems that have been identified\n with the Session Initiation Protocol's (SIP) non-INVITE transaction. 4321 algorithm risk nested-reference unchanged"},{"id":"IETF RFC 5486","type":"specification","body":"IETF","designation":"RFC 5486","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5486.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5486.txt","https://www.rfc-editor.org/rfc/rfc5486.pdf"],"folder":"IETF/RFC-5486","files":{"txt":{"path":"standards/IETF/RFC-5486/RFC-5486.txt","sha256":"fd75378a370ed28c9324a9ffa9451deadf268296c61b2ab1b14a6d1cf7fd7c8a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the terminology that is to be used in\n describing Session PEERing for Multimedia INTerconnect (SPEERMINT).\n\nMalas & Meyer Informational [Page 1]\n\f\nRFC 5486 SPEERMINT Terminology March 2009","scope_keywords":["5486","delivery","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null}],"search_text":"IETF RFC 5486 This document defines the terminology that is to be used in\n describing Session PEERing for Multimedia INTerconnect (SPEERMINT).\n\nMalas & Meyer Informational [Page 1]\n\f\nRFC 5486 SPEERMINT Terminology March 2009 5486 delivery http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6836","type":"specification","body":"IETF","designation":"RFC 6836","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6836.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6836.txt","https://www.rfc-editor.org/rfc/rfc6836.pdf"],"folder":"IETF/RFC-6836","files":{"txt":{"path":"standards/IETF/RFC-6836/RFC-6836.txt","sha256":"89dee30ffe18d60d7c1d62bfe5dd273ecb8bb1e0f57d6e5c81dfd5a6d19c8849"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a simple distributed index system to be used\n by a Locator/ID Separation Protocol (LISP) Ingress Tunnel Router\n (ITR) or Map-Resolver (MR) to find the Egress Tunnel Router (ETR)\n that holds the mapping information for a particular Endpoint\n Identifier (EID). The MR can then query that ETR to obtain the\n actual mapping information, which consists of a list of Routing\n Locators (RLOCs) for the EID. Termed the Alternative Logical\n Topology (ALT), the index is built as an overlay network on the\n public Internet using the Border Gateway Protocol (BGP) and Generic\n Routing Encapsulation (GRE).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the In","scope_keywords":["6836","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6831","folder":"IETF/RFC-6831","source":"IETF/RFC-6831/RFC-6831.txt","version":null},{"body":"IETF","designation":"RFC 6832","folder":"IETF/RFC-6832","source":"IETF/RFC-6832/RFC-6832.txt","version":null},{"body":"IETF","designation":"RFC 6833","folder":"IETF/RFC-6833","source":"IETF/RFC-6833/RFC-6833.txt","version":null},{"body":"IETF","designation":"RFC 6835","folder":"IETF/RFC-6835","source":"IETF/RFC-6835/RFC-6835.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null}],"search_text":"IETF RFC 6836 This document describes a simple distributed index system to be used\n by a Locator/ID Separation Protocol (LISP) Ingress Tunnel Router\n (ITR) or Map-Resolver (MR) to find the Egress Tunnel Router (ETR)\n that holds the mapping information for a particular Endpoint\n Identifier (EID). The MR can then query that ETR to obtain the\n actual mapping information, which consists of a list of Routing\n Locators (RLOCs) for the EID. Termed the Alternative Logical\n Topology (ALT), the index is built as an overlay network on the\n public Internet using the Border Gateway Protocol (BGP) and Generic\n Routing Encapsulation (GRE).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the In 6836 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7893","type":"specification","body":"IETF","designation":"RFC 7893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7893.txt","https://www.rfc-editor.org/rfc/rfc7893.pdf"],"folder":"IETF/RFC-7893","files":{"pdf":{"path":"standards/IETF/RFC-7893/RFC-7893.pdf","sha256":"7cd98cc7844e9109d32ec8b6ca69fedbf00c89d33f1657708742d364bd413056"},"txt":{"path":"standards/IETF/RFC-7893/RFC-7893.txt","sha256":"877a87952c78a8433664aabc82158d7364a93cab8a0a35ac35b11df63bec835a"}},"tags":["nested-reference","unchanged"],"summary":"Pseudowires (PWs) have become a common mechanism for tunneling\n traffic and may be found in unmanaged scenarios competing for network\n resources both with other PWs and with non-PW traffic, such as TCP/IP\n flows. Thus, it is worthwhile specifying under what conditions such\n competition is acceptable, i.e., the PW traffic does not\n significantly harm other traffic or contribute more than it should to\n congestion. We conclude that PWs transporting responsive traffic\n behave as desired without the need for additional mechanisms. For\n inelastic PWs (such as Time Division Multiplexing (TDM) PWs), we\n derive a bound under which such PWs consume no more network capacity\n than a TCP flow. For TDM PWs, we find that the level of congestion\n at which the PW can no longer deliver acceptable TDM service is never\n significantly greater, and is typically much lower, than this bound.\n Therefore, as long","scope_keywords":["7893","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8084","folder":"IETF/RFC-8084","source":"IETF/RFC-8084/RFC-8084.txt","version":null}],"search_text":"IETF RFC 7893 Pseudowires (PWs) have become a common mechanism for tunneling\n traffic and may be found in unmanaged scenarios competing for network\n resources both with other PWs and with non-PW traffic, such as TCP/IP\n flows. Thus, it is worthwhile specifying under what conditions such\n competition is acceptable, i.e., the PW traffic does not\n significantly harm other traffic or contribute more than it should to\n congestion. We conclude that PWs transporting responsive traffic\n behave as desired without the need for additional mechanisms. For\n inelastic PWs (such as Time Division Multiplexing (TDM) PWs), we\n derive a bound under which such PWs consume no more network capacity\n than a TCP flow. For TDM PWs, we find that the level of congestion\n at which the PW can no longer deliver acceptable TDM service is never\n significantly greater, and is typically much lower, than this bound.\n Therefore, as long 7893 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 2787","type":"specification","body":"IETF","designation":"RFC 2787","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2787.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2787.txt","https://www.rfc-editor.org/rfc/rfc2787.pdf"],"folder":"IETF/RFC-2787","files":{"txt":{"path":"standards/IETF/RFC-2787/RFC-2787.txt","sha256":"a6f95e8dd32bd4855ab3747889564b00100173ad2ed802a3ddc0c24db832ea16"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for configuring, monitoring, and\n controlling routers that employ the Virtual Router Redundancy\n Protocol (VRRP) [17].\n\n This memo specifies a MIB module in a manner that is compliant with\n SMIv2 [5], and semantically identical to the SMIv1 definitions [2].\n\nJewell & Chuang Standards Track [Page 1]\n\f\nRFC 2787 VRRP MIB Management Objects March 2000","scope_keywords":["2787","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2787 This specification defines an extension to the Management Information\n Base (MIB) for use with SNMP-based network management. In\n particular, it defines objects for configuring, monitoring, and\n controlling routers that employ the Virtual Router Redundancy\n Protocol (VRRP) [17].\n\n This memo specifies a MIB module in a manner that is compliant with\n SMIv2 [5], and semantically identical to the SMIv1 definitions [2].\n\nJewell & Chuang Standards Track [Page 1]\n\f\nRFC 2787 VRRP MIB Management Objects March 2000 2787 management nested-reference unchanged"},{"id":"IETF RFC 2788","type":"specification","body":"IETF","designation":"RFC 2788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2788.txt","https://www.rfc-editor.org/rfc/rfc2788.pdf"],"folder":"IETF/RFC-2788","files":{"txt":{"path":"standards/IETF/RFC-2788/RFC-2788.txt","sha256":"cccec3bbb62d89c15de219de4142d740f3684dfa98916b0a9b5b651555bd4a35"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2788 Innosoft\nCategory: Standards Track S. Kille\nObsoletes: 2248 MessagingDirect Ltd.\n March 2000\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nIntroduction\n\n A networked application is a realization of some well-defined service\n on one or more host computers that is accessible via some network,\n uses some network for its internal operations, or both.\n\n There are a wide range of networked applications for wh","scope_keywords":["2788","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4780","folder":"IETF/RFC-4780","source":"IETF/RFC-4780/RFC-4780.txt","version":null}],"search_text":"IETF RFC 2788 Network Working Group N. Freed\nRequest for Comments: 2788 Innosoft\nCategory: Standards Track S. Kille\nObsoletes: 2248 MessagingDirect Ltd.\n March 2000\n\n Network Services Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nIntroduction\n\n A networked application is a realization of some well-defined service\n on one or more host computers that is accessible via some network,\n uses some network for its internal operations, or both.\n\n There are a wide range of networked applications for wh 2788 management nested-reference unchanged"},{"id":"IETF RFC 2789","type":"specification","body":"IETF","designation":"RFC 2789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2789.txt","https://www.rfc-editor.org/rfc/rfc2789.pdf"],"folder":"IETF/RFC-2789","files":{"txt":{"path":"standards/IETF/RFC-2789/RFC-2789.txt","sha256":"10595f82f244ec03522a40b9b0d8ec45a49b519405016bf732efaaa65e54e138"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Freed\nRequest for Comments: 2789 Innosoft\nObsoletes: 2249, 1566 S. Kille\nCategory: Standards Track MessagingDirect Ltd.\n March 2000\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nIntroduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this memo extends the basic Network Services Monitoring\n MIB defined in RFC 2788 [16] to allow monitorin","scope_keywords":["2789","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2789 Network Working Group N. Freed\nRequest for Comments: 2789 Innosoft\nObsoletes: 2249, 1566 S. Kille\nCategory: Standards Track MessagingDirect Ltd.\n March 2000\n\n Mail Monitoring MIB\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nIntroduction\n\n This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n Specifically, this memo extends the basic Network Services Monitoring\n MIB defined in RFC 2788 [16] to allow monitorin 2789 management nested-reference unchanged"},{"id":"IETF RFC 4640","type":"specification","body":"IETF","designation":"RFC 4640","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4640.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4640.txt","https://www.rfc-editor.org/rfc/rfc4640.pdf"],"folder":"IETF/RFC-4640","files":{"txt":{"path":"standards/IETF/RFC-4640/RFC-4640.txt","sha256":"142e7a98c79389f14796298e5f15dd281d3823cc35a8d121d48f369f5cf1da96"}},"tags":["nested-reference","unchanged"],"summary":"A mobile node needs at least the following information: a home\n address, a home agent address, and a security association with home\n agent to register with the home agent. The process of obtaining this\n information is called bootstrapping. This document discusses issues\n involved with how the mobile node can be bootstrapped for Mobile IPv6\n (MIPv6) and various potential deployment scenarios for mobile node\n bootstrapping.","scope_keywords":["4640","authentication","credential","credentials","management","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5026","folder":"IETF/RFC-5026","source":"IETF/RFC-5026/RFC-5026.txt","version":null},{"body":"IETF","designation":"RFC 5447","folder":"IETF/RFC-5447","source":"IETF/RFC-5447/RFC-5447.txt","version":null},{"body":"IETF","designation":"RFC 5637","folder":"IETF/RFC-5637","source":"IETF/RFC-5637/RFC-5637.txt","version":null},{"body":"IETF","designation":"RFC 5778","folder":"IETF/RFC-5778","source":"IETF/RFC-5778/RFC-5778.txt","version":null},{"body":"IETF","designation":"RFC 6610","folder":"IETF/RFC-6610","source":"IETF/RFC-6610/RFC-6610.txt","version":null}],"search_text":"IETF RFC 4640 A mobile node needs at least the following information: a home\n address, a home agent address, and a security association with home\n agent to register with the home agent. The process of obtaining this\n information is called bootstrapping. This document discusses issues\n involved with how the mobile node can be bootstrapped for Mobile IPv6\n (MIPv6) and various potential deployment scenarios for mobile node\n bootstrapping. 4640 authentication credential credentials management trust nested-reference unchanged"},{"id":"IETF RFC 280","type":"specification","body":"IETF","designation":"RFC 280","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc280.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc280.txt","https://www.rfc-editor.org/rfc/rfc280.pdf"],"folder":"IETF/RFC-280","files":{"txt":{"path":"standards/IETF/RFC-280/RFC-280.txt","sha256":"82b9cb94505a6c5c922af2cbf3e0f2d235bae7b34554b6dabfff40b1bec464c5"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 280 17-NOV-71 15:57 8060\nA Draft Set of Host Names Richard W. Watson\n SRI-ARC\n\nThe enclosed list of host names is a draft. The hosts with an *\nnext to them indicated that this is the name they desired. The\nothers are names assigned. If I do not hear from representatives\nat the hosts to change or correct the names in this list by\nDecember 3, I will publish a list which we all can consider\nofficial.\n\n Formal Name Nickname Network Address\n\n*AMES-ILLIAC I4\n\n*AMES-67 16\n\n*AMES-TIP 144\n\n*BBN-NCC NCC 5\n\n*BBN-TESTIP 158\n\n*CMU-10 14\n\n*MIT-DMCG DMCG 70\n\n*MIT-MULTICS MIT-M 6\n\n*MITRE-TIP 145\n\n*RAND-CSG 71\n\n*RAND-RCC 7\n\n*SRI-AI 66\n\n*SRI-ARC NIC 2\n\n*UCLA-CCN CCN 65\n\n*UCLA-NMC SEX 1\n\n*UCSB-MOD75 MOD75 3\n\n*USC-44 23\n\nBBN-TENEX TENEX 69\n\n [Page 1]\n\f\nNWG/RFC# 280 17-NOV-71 15:57 8060\nA Draft Set of Host Names\n\nBBN-TENEXB 133\n\nBURR 15\n\nBURR-TEST 79\n\nCASE-10 13\n\nETAC-TIP 148\n\nGWC-TIP 152\n\nHARV-1 73","scope_keywords":["280","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 289","folder":"IETF/RFC-289","source":"IETF/RFC-289/RFC-289.txt","version":null}],"search_text":"IETF RFC 280 NWG/RFC# 280 17-NOV-71 15:57 8060\nA Draft Set of Host Names Richard W. Watson\n SRI-ARC\n\nThe enclosed list of host names is a draft. The hosts with an *\nnext to them indicated that this is the name they desired. The\nothers are names assigned. If I do not hear from representatives\nat the hosts to change or correct the names in this list by\nDecember 3, I will publish a list which we all can consider\nofficial.\n\n Formal Name Nickname Network Address\n\n*AMES-ILLIAC I4\n\n*AMES-67 16\n\n*AMES-TIP 144\n\n*BBN-NCC NCC 5\n\n*BBN-TESTIP 158\n\n*CMU-10 14\n\n*MIT-DMCG DMCG 70\n\n*MIT-MULTICS MIT-M 6\n\n*MITRE-TIP 145\n\n*RAND-CSG 71\n\n*RAND-RCC 7\n\n*SRI-AI 66\n\n*SRI-ARC NIC 2\n\n*UCLA-CCN CCN 65\n\n*UCLA-NMC SEX 1\n\n*UCSB-MOD75 MOD75 3\n\n*USC-44 23\n\nBBN-TENEX TENEX 69\n\n [Page 1]\n\f\nNWG/RFC# 280 17-NOV-71 15:57 8060\nA Draft Set of Host Names\n\nBBN-TENEXB 133\n\nBURR 15\n\nBURR-TEST 79\n\nCASE-10 13\n\nETAC-TIP 148\n\nGWC-TIP 152\n\nHARV-1 73 280 tsp nested-reference unchanged"},{"id":"IETF RFC 7013","type":"specification","body":"IETF","designation":"RFC 7013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7013.txt","https://www.rfc-editor.org/rfc/rfc7013.pdf"],"folder":"IETF/RFC-7013","files":{"txt":{"path":"standards/IETF/RFC-7013/RFC-7013.txt","sha256":"0c39773ffb0f68107342acb66dd934e1dfb7d42febb7621953c11e5237629932"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines for how to write definitions of new\n Information Elements for the IP Flow Information Export (IPFIX)\n protocol. It provides instructions on using the proper conventions\n for Information Elements to be registered in the IANA IPFIX\n Information Element registry, and provides guidelines for expert\n reviewers to evaluate new registrations.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww","scope_keywords":["7013","http","license","management","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 7013 This document provides guidelines for how to write definitions of new\n Information Elements for the IP Flow Information Export (IPFIX)\n protocol. It provides instructions on using the proper conventions\n for Information Elements to be registered in the IANA IPFIX\n Information Element registry, and provides guidelines for expert\n reviewers to evaluate new registrations.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww 7013 http license management registered subject trust nested-reference unchanged"},{"id":"IETF RFC 281","type":"specification","body":"IETF","designation":"RFC 281","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc281.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc281.txt","https://www.rfc-editor.org/rfc/rfc281.pdf"],"folder":"IETF/RFC-281","files":{"txt":{"path":"standards/IETF/RFC-281/RFC-281.txt","sha256":"4b244fbbc2da97d65497fc3e183dc1a3c1bd7c6f64bdfc053376c8453472a351"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comment: 281 BBN\nNIC: 8163 8 December 1971\nCategory: D.7\nReference: RFC #264, #265\n\n A suggested Addition to File Transfer Protocol\n\nOn November 16, an informal meeting was held at UCLA to discuss\nprospects for a network standard Remote Job Service (RJS) protocol. In\nattendance were representatives of UCLA-CCN and UCSB, the\nnetwork's only current RJS sites, as well as UCLA-NMC and the BBN\nnetwork project. A report on that discussion will be published as an\nRFC shortly and will not be discussed here. In thinking about the use\nof the proposed File Transfer Protocol (FTP) (RFC #265) for RJS,\nhowever, we came to the conclusion that a \"restart\" procedure might be\nan extremely useful addition to the FTP.\n\nMany, perhaps most, of the individuals involved in protocol design thus\nfar are oriented toward the use of short date transmissions over the\nnetw","scope_keywords":["281","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 281 Network Working Group A. McKenzie\nRequest for Comment: 281 BBN\nNIC: 8163 8 December 1971\nCategory: D.7\nReference: RFC #264, #265\n\n A suggested Addition to File Transfer Protocol\n\nOn November 16, an informal meeting was held at UCLA to discuss\nprospects for a network standard Remote Job Service (RJS) protocol. In\nattendance were representatives of UCLA-CCN and UCSB, the\nnetwork's only current RJS sites, as well as UCLA-NMC and the BBN\nnetwork project. A report on that discussion will be published as an\nRFC shortly and will not be discussed here. In thinking about the use\nof the proposed File Transfer Protocol (FTP) (RFC #265) for RJS,\nhowever, we came to the conclusion that a \"restart\" procedure might be\nan extremely useful addition to the FTP.\n\nMany, perhaps most, of the individuals involved in protocol design thus\nfar are oriented toward the use of short date transmissions over the\nnetw 281 path nested-reference unchanged"},{"id":"IETF RFC 6128","type":"specification","body":"IETF","designation":"RFC 6128","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6128.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6128.txt","https://www.rfc-editor.org/rfc/rfc6128.pdf"],"folder":"IETF/RFC-6128","files":{"txt":{"path":"standards/IETF/RFC-6128/RFC-6128.txt","sha256":"7c224d06e8cf564908fb268e4c599c83854691945f53fef55873af58d9d0a08b"}},"tags":["nested-reference","unchanged"],"summary":"The Session Description Protocol (SDP) has an attribute that allows\n RTP applications to specify an address and a port associated with the\n RTP Control Protocol (RTCP) traffic. In RTP-based source-specific\n multicast (SSM) sessions, the same attribute is used to designate the\n address and the RTCP port of the Feedback Target in the SDP\n description. However, the RTCP port associated with the SSM session\n itself cannot be specified by the same attribute to avoid ambiguity,\n and thus, is required to be derived from the \"m=\" line of the media\n description. Deriving the RTCP port from the \"m=\" line imposes an\n unnecessary restriction. This document removes this restriction by\n introducing a new SDP attribute.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF","scope_keywords":["6128","attribute","attributes","crl","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"IETF RFC 6128 The Session Description Protocol (SDP) has an attribute that allows\n RTP applications to specify an address and a port associated with the\n RTP Control Protocol (RTCP) traffic. In RTP-based source-specific\n multicast (SSM) sessions, the same attribute is used to designate the\n address and the RTCP port of the Feedback Target in the SDP\n description. However, the RTCP port associated with the SSM session\n itself cannot be specified by the same attribute to avoid ambiguity,\n and thus, is required to be derived from the \"m=\" line of the media\n description. Deriving the RTCP port from the \"m=\" line imposes an\n unnecessary restriction. This document removes this restriction by\n introducing a new SDP attribute.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF 6128 attribute attributes crl http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 282","type":"specification","body":"IETF","designation":"RFC 282","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc282.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc282.txt","https://www.rfc-editor.org/rfc/rfc282.pdf"],"folder":"IETF/RFC-282","files":{"txt":{"path":"standards/IETF/RFC-282/RFC-282.txt","sha256":"8974fdb19e7a3f184044ac68e0bd31e9ec9b35c54f982579c286426cea280a67"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. A. Padlipsky\nRequest for Comments: 282 Project MAC\nNIC: 8164 December 8, 1971\n\n GRAPHICS MEETING REPORT\n\n The second Network Graphics Group Meeting was convened at the\n Stanford Artificial Intelligence Lab at 6:00p.m. Sunday, November\n 21st. (Attendees are listed in the Appendix.) Jim Michener served\n as chairman, and I either volunteered or was volunteered to serve as\n recording secretary, with Karl Kelly's assistance in keeping notes.\n\n An agenda was agreed upon for the meeting, covering three major\n topics: 1) reports on the experiments which had been set up at the\n July meeting, 2) prepared talks by attendees who had general points\n to raise about Network Graphics, and 3) specification of a \"first-\n pass\" graphics protocol. Before the reports were given, some general\n discussion was held on two important topics: the \"context\" problem\n (just how, in the Networ","scope_keywords":["282","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 493","folder":"IETF/RFC-493","source":"IETF/RFC-493/RFC-493.txt","version":null}],"search_text":"IETF RFC 282 Network Working Group M. A. Padlipsky\nRequest for Comments: 282 Project MAC\nNIC: 8164 December 8, 1971\n\n GRAPHICS MEETING REPORT\n\n The second Network Graphics Group Meeting was convened at the\n Stanford Artificial Intelligence Lab at 6:00p.m. Sunday, November\n 21st. (Attendees are listed in the Appendix.) Jim Michener served\n as chairman, and I either volunteered or was volunteered to serve as\n recording secretary, with Karl Kelly's assistance in keeping notes.\n\n An agenda was agreed upon for the meeting, covering three major\n topics: 1) reports on the experiments which had been set up at the\n July meeting, 2) prepared talks by attendees who had general points\n to raise about Network Graphics, and 3) specification of a \"first-\n pass\" graphics protocol. Before the reports were given, some general\n discussion was held on two important topics: the \"context\" problem\n (just how, in the Networ 282 key presentation nested-reference unchanged"},{"id":"IETF RFC 493","type":"specification","body":"IETF","designation":"RFC 493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc493.txt","https://www.rfc-editor.org/rfc/rfc493.pdf"],"folder":"IETF/RFC-493","files":{"pdf":{"path":"standards/IETF/RFC-493/RFC-493.pdf","sha256":"d8d749542bd981bdba1ed7a8e749b6f1ebc85891674b81828fc020eede6c8e5a"},"txt":{"path":"standards/IETF/RFC-493/RFC-493.txt","sha256":"24861989260e66c1263c3df9ad8123f0d828fa41c8d944eac9ee2fedd7a25102"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Michener\nRequest for Comments: 493 MAC\nNIC: 15358 I. Cotton\nReferences: 282, 258 MITRE\nObsoletes: 292 K. Kelley\n U. of Ill.\n D. Liddle\n Ownes Ill.\n E. Meyer\n MAC\n\n GRAPHICS PROTOCOL\n\nIntroduction\n\n This document reflects opinions expressed and decisions reached at\n the second meeting of the Network Graphics Group, held at the\n Stanford Artificial Intelligence Laboratory in late November 1971.\n It describes part of a proposed Network Standard Graphics Protocol\n for transmitting graphics data within the ARPA network. The\n particular aspects of the protocol covered in this document relate to\n the form and content of graphics information sent from a source of\n graphical information (an application program, say, in the \"Serving\n Host\") to a display package for output to a graphics console (at the\n \"Using Host\"). This will take the form of a sequence of 8-bit bytes,\n a","scope_keywords":["493"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 549","folder":"IETF/RFC-549","source":"IETF/RFC-549/RFC-549.txt","version":null},{"body":"IETF","designation":"RFC 553","folder":"IETF/RFC-553","source":"IETF/RFC-553/RFC-553.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 493 Network Working Group J. Michener\nRequest for Comments: 493 MAC\nNIC: 15358 I. Cotton\nReferences: 282, 258 MITRE\nObsoletes: 292 K. Kelley\n U. of Ill.\n D. Liddle\n Ownes Ill.\n E. Meyer\n MAC\n\n GRAPHICS PROTOCOL\n\nIntroduction\n\n This document reflects opinions expressed and decisions reached at\n the second meeting of the Network Graphics Group, held at the\n Stanford Artificial Intelligence Laboratory in late November 1971.\n It describes part of a proposed Network Standard Graphics Protocol\n for transmitting graphics data within the ARPA network. The\n particular aspects of the protocol covered in this document relate to\n the form and content of graphics information sent from a source of\n graphical information (an application program, say, in the \"Serving\n Host\") to a display package for output to a graphics console (at the\n \"Using Host\"). This will take the form of a sequence of 8-bit bytes,\n a 493 nested-reference unchanged"},{"id":"IETF RFC 4997","type":"specification","body":"IETF","designation":"RFC 4997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4997.txt","https://www.rfc-editor.org/rfc/rfc4997.pdf"],"folder":"IETF/RFC-4997","files":{"txt":{"path":"standards/IETF/RFC-4997/RFC-4997.txt","sha256":"448c877b05e228d9ebeec721054d8ec8b88473593f4d121d0c7a465dda1f74ec"}},"tags":["nested-reference","unchanged"],"summary":"This document defines Robust Header Compression - Formal Notation\n (ROHC-FN), a formal notation to specify field encodings for\n compressed formats when defining new profiles within the ROHC\n framework. ROHC-FN offers a library of encoding methods that are\n often used in ROHC profiles and can thereby help to simplify future\n profile development work.","scope_keywords":["4997","algorithm","attribute","attributes","presentation","profile","profiles","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 4997 This document defines Robust Header Compression - Formal Notation\n (ROHC-FN), a formal notation to specify field encodings for\n compressed formats when defining new profiles within the ROHC\n framework. ROHC-FN offers a library of encoding methods that are\n often used in ROHC profiles and can thereby help to simplify future\n profile development work. 4997 algorithm attribute attributes presentation profile profiles trust nested-reference unchanged"},{"id":"IETF RFC 2823","type":"specification","body":"IETF","designation":"RFC 2823","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2823.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2823.txt","https://www.rfc-editor.org/rfc/rfc2823.pdf"],"folder":"IETF/RFC-2823","files":{"txt":{"path":"standards/IETF/RFC-2823/RFC-2823.txt","sha256":"fd4a5f169be281e8f80b332b72f315fe370b5ad1bea6c4af0727d4a74c2c61b6"}},"tags":["nested-reference","unchanged"],"summary":"The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links, and\n RFCs 1662 [2] and 2615 [3] provide a means to carry PPP over\n Synchronous Optical Network (SONET) [4] and Synchronous Digital\n Hierarchy (SDH) [5] circuits. This document extends these standards\n to include a new encapsulation for PPP called Simple Data Link (SDL)\n [6]. SDL provides a very low overhead alternative to HDLC-like\n encapsulation, and can also be used on SONET/SDH links.\n\nApplicability\n\n This specification is intended for those implementations that use PPP\n over high speed point-to-point circuits, both with so-called \"dark\n fiber\" and over public telecommunications networks. Because this\n enhanced PPP encapsulation has very low overhead and good hardware\n scaling characteristics, it is anticipated that significantly higher\n throughput can","scope_keywords":["2823","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 2823 The Point-to-Point Protocol (PPP) [1] provides a standard method for\n transporting multi-protocol datagrams over point-to-point links, and\n RFCs 1662 [2] and 2615 [3] provide a means to carry PPP over\n Synchronous Optical Network (SONET) [4] and Synchronous Digital\n Hierarchy (SDH) [5] circuits. This document extends these standards\n to include a new encapsulation for PPP called Simple Data Link (SDL)\n [6]. SDL provides a very low overhead alternative to HDLC-like\n encapsulation, and can also be used on SONET/SDH links.\n\nApplicability\n\n This specification is intended for those implementations that use PPP\n over high speed point-to-point circuits, both with so-called \"dark\n fiber\" and over public telecommunications networks. Because this\n enhanced PPP encapsulation has very low overhead and good hardware\n scaling characteristics, it is anticipated that significantly higher\n throughput can 2823 path presentation nested-reference unchanged"},{"id":"IETF RFC 3026","type":"specification","body":"IETF","designation":"RFC 3026","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3026.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3026.txt","https://www.rfc-editor.org/rfc/rfc3026.pdf"],"folder":"IETF/RFC-3026","files":{"txt":{"path":"standards/IETF/RFC-3026/RFC-3026.txt","sha256":"e3b57f111b35f24df939b8d59261f52d3ac4fcb16e10aebbe149dc0f05089d75"}},"tags":["nested-reference","unchanged"],"summary":"Working Party 1/2, of the International Telecommunication Union\n Telecommunication Standardization Sector (ITU-T) held a meeting of\n its collaborators in Berlin Germany 19-26 October 2000. The agenda\n of the meeting contained several contributions regarding RFC 2916:\n \"E.164 Number and DNS\" from the Internet Engineering Task Force's\n (IETF) ENUM Working Group - more specifically, the method for\n administering and maintaining the E.164-based resources in the Domain\n Name System (DNS) as related to the ENUM protocol. Consequently, in\n addition to the WP1/2 collaborators, there were several members of\n the IETF present to assist with the discussion of issues contained in\n the aforementioned contributions.\n\n This liaison from WP1/2 to the IETF/ISOC conveys the understandings\n of the WP1/2 collaborators resulting from the discussions.\n\n1. Considerations under Question 1/2 (Numbering)\n\n Throug","scope_keywords":["3026","identification","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3152","folder":"IETF/RFC-3152","source":"IETF/RFC-3152/RFC-3152.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null}],"search_text":"IETF RFC 3026 Working Party 1/2, of the International Telecommunication Union\n Telecommunication Standardization Sector (ITU-T) held a meeting of\n its collaborators in Berlin Germany 19-26 October 2000. The agenda\n of the meeting contained several contributions regarding RFC 2916:\n \"E.164 Number and DNS\" from the Internet Engineering Task Force's\n (IETF) ENUM Working Group - more specifically, the method for\n administering and maintaining the E.164-based resources in the Domain\n Name System (DNS) as related to the ENUM protocol. Consequently, in\n addition to the WP1/2 collaborators, there were several members of\n the IETF present to assist with the discussion of issues contained in\n the aforementioned contributions.\n\n This liaison from WP1/2 to the IETF/ISOC conveys the understandings\n of the WP1/2 collaborators resulting from the discussions.\n\n1. Considerations under Question 1/2 (Numbering)\n\n Throug 3026 identification policy nested-reference unchanged"},{"id":"IETF RFC 4778","type":"specification","body":"IETF","designation":"RFC 4778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4778.txt","https://www.rfc-editor.org/rfc/rfc4778.pdf"],"folder":"IETF/RFC-4778","files":{"txt":{"path":"standards/IETF/RFC-4778/RFC-4778.txt","sha256":"dc7a79c3b2d3c86cb4342dd85c2c1ee78a0593f4fa320897980e707dc167f775"}},"tags":["nested-reference","unchanged"],"summary":"This document is a survey of the current practices used in today's\n large ISP operational networks to secure layer 2 and layer 3\n infrastructure devices. The information listed here is the result of\n information gathered from people directly responsible for defining\n and implementing secure infrastructures in Internet Service Provider\n environments.\n\nKaeo Informational [Page 1]\n\f\nRFC 4778 OPSEC Practices January 2007","scope_keywords":["4778","management","path","policy","risk","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5670","folder":"IETF/RFC-5670","source":"IETF/RFC-5670/RFC-5670.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 4778 This document is a survey of the current practices used in today's\n large ISP operational networks to secure layer 2 and layer 3\n infrastructure devices. The information listed here is the result of\n information gathered from people directly responsible for defining\n and implementing secure infrastructures in Internet Service Provider\n environments.\n\nKaeo Informational [Page 1]\n\f\nRFC 4778 OPSEC Practices January 2007 4778 management path policy risk subject trust validation nested-reference unchanged"},{"id":"IETF RFC 4832","type":"specification","body":"IETF","designation":"RFC 4832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4832.txt","https://www.rfc-editor.org/rfc/rfc4832.pdf"],"folder":"IETF/RFC-4832","files":{"txt":{"path":"standards/IETF/RFC-4832/RFC-4832.txt","sha256":"b0317d64b16e827cb2c1ee9fc256ad5373e6fc3b99a6bcf3b21873f3f150a99b"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses security threats to network-based localized\n mobility management. Threats may occur on two interfaces: the\n interface between a localized mobility anchor and a mobile access\n gateway, as well as the interface between a mobile access gateway and\n a mobile node. Threats to the former interface impact the localized\n mobility management protocol itself.","scope_keywords":["4832","management","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4831","folder":"IETF/RFC-4831","source":"IETF/RFC-4831/RFC-4831.txt","version":null},{"body":"IETF","designation":"RFC 5213","folder":"IETF/RFC-5213","source":"IETF/RFC-5213/RFC-5213.txt","version":null},{"body":"IETF","designation":"RFC 6705","folder":"IETF/RFC-6705","source":"IETF/RFC-6705/RFC-6705.txt","version":null}],"search_text":"IETF RFC 4832 This document discusses security threats to network-based localized\n mobility management. Threats may occur on two interfaces: the\n interface between a localized mobility anchor and a mobile access\n gateway, as well as the interface between a mobile access gateway and\n a mobile node. Threats to the former interface impact the localized\n mobility management protocol itself. 4832 management registered trust nested-reference unchanged"},{"id":"IETF RFC 8073","type":"specification","body":"IETF","designation":"RFC 8073","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8073.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8073.txt","https://www.rfc-editor.org/rfc/rfc8073.pdf"],"folder":"IETF/RFC-8073","files":{"txt":{"path":"standards/IETF/RFC-8073/RFC-8073.txt","sha256":"f0f5beee8997f809ec0370bb94c6fe6c5eb68020ea99ea3f91d26efa410c9ea5"}},"tags":["nested-reference","unchanged"],"summary":"This report documents the discussions and conclusions from the\n Coordinating Attack Response at Internet Scale (CARIS) workshop that\n took place in Berlin, Germany on 18 June 2015. The purpose of this\n workshop was to improve mutual awareness, understanding, and\n coordination among the diverse participating organizations and their\n representatives.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of","scope_keywords":["8073","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 8073 This report documents the discussions and conclusions from the\n Coordinating Attack Response at Internet Scale (CARIS) workshop that\n took place in Berlin, Germany on 18 June 2015. The purpose of this\n workshop was to improve mutual awareness, understanding, and\n coordination among the diverse participating organizations and their\n representatives.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of 8073 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 2844","type":"specification","body":"IETF","designation":"RFC 2844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2844.txt","https://www.rfc-editor.org/rfc/rfc2844.pdf"],"folder":"IETF/RFC-2844","files":{"txt":{"path":"standards/IETF/RFC-2844/RFC-2844.txt","sha256":"4bc8ae1c4ec3c0d2885978b2ab04d9a92ed77a9ace63ab55bab65366f736fde3"}},"tags":["nested-reference","unchanged"],"summary":"This memo specifies, for OSPF implementors and users, mechanisms\n describing how the protocol operates in ATM networks over PVC and SVC\n meshes with the presence of Proxy-PAR. These recommendations require\n no protocol changes and allow simpler, more efficient and cost-\n effective network designs. It is recommended that OSPF\n implementations should be able to support logical interfaces, each\n consisting of one or more virtual circuits and used either as\n numbered logical point-to-point links (one VC), logical NBMA networks\n (more than one VC) or Point-to-MultiPoint networks (more than one\n VC), where a solution simulating broadcast interfaces is not\n appropriate. PAR can help distribute across the ATM cloud\n configuration setup and changes of such interfaces when OSPF capable\n routers are (re-)configured. Proxy-PAR can in turn be used to\n exchange this information between the ATM cloud a","scope_keywords":["2844","path","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 2844 This memo specifies, for OSPF implementors and users, mechanisms\n describing how the protocol operates in ATM networks over PVC and SVC\n meshes with the presence of Proxy-PAR. These recommendations require\n no protocol changes and allow simpler, more efficient and cost-\n effective network designs. It is recommended that OSPF\n implementations should be able to support logical interfaces, each\n consisting of one or more virtual circuits and used either as\n numbered logical point-to-point links (one VC), logical NBMA networks\n (more than one VC) or Point-to-MultiPoint networks (more than one\n VC), where a solution simulating broadcast interfaces is not\n appropriate. PAR can help distribute across the ATM cloud\n configuration setup and changes of such interfaces when OSPF capable\n routers are (re-)configured. Proxy-PAR can in turn be used to\n exchange this information between the ATM cloud a 2844 path registered nested-reference unchanged"},{"id":"IETF RFC 285","type":"specification","body":"IETF","designation":"RFC 285","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc285.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc285.txt","https://www.rfc-editor.org/rfc/rfc285.pdf"],"folder":"IETF/RFC-285","files":{"txt":{"path":"standards/IETF/RFC-285/RFC-285.txt","sha256":"e75b1fdf7dede284d1c93d33c91283590df7193f35b08487f1578e528b02d8b6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Huff\nRequest for Comments: 285 CWRU (Case)\nNIC: 8271 December 15, 1971\nUpdates: None\nObsoletes: None\n\n Network Graphics\n\n Not much has been written about graphics on the ARPANET when the\nvolume of the NIC collection is considered. Presently it contains some\n8000 entries of which only about 20 are on the subject of graphics. The\nreason is probably similar to that given by L. G. Roberts in A FORWARD\nLOOK (NIC 7542) as the reason that data base sharing or software sharing\nwill not be important topics for several more years: the NET hasn't been\nup long enough for interested people to have enough of the facts to know\nif it is feasible and to think creatively.\n\n This paper is therefore aimed at bringing together the present\nstate of graphics on the NET for the newcomer and attempting to add a\nlittle more distance to the ground covered so far. I will start with an\noverv","scope_keywords":["285","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 493","folder":"IETF/RFC-493","source":"IETF/RFC-493/RFC-493.txt","version":null}],"search_text":"IETF RFC 285 Network Working Group D. Huff\nRequest for Comments: 285 CWRU (Case)\nNIC: 8271 December 15, 1971\nUpdates: None\nObsoletes: None\n\n Network Graphics\n\n Not much has been written about graphics on the ARPANET when the\nvolume of the NIC collection is considered. Presently it contains some\n8000 entries of which only about 20 are on the subject of graphics. The\nreason is probably similar to that given by L. G. Roberts in A FORWARD\nLOOK (NIC 7542) as the reason that data base sharing or software sharing\nwill not be important topics for several more years: the NET hasn't been\nup long enough for interested people to have enough of the facts to know\nif it is feasible and to think creatively.\n\n This paper is therefore aimed at bringing together the present\nstate of graphics on the NET for the newcomer and attempting to add a\nlittle more distance to the ground covered so far. I will start with an\noverv 285 key subject nested-reference unchanged"},{"id":"IETF RFC 4714","type":"specification","body":"IETF","designation":"RFC 4714","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4714.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4714.txt","https://www.rfc-editor.org/rfc/rfc4714.pdf"],"folder":"IETF/RFC-4714","files":{"txt":{"path":"standards/IETF/RFC-4714/RFC-4714.txt","sha256":"55be11531f06ac41b0961a6962ca2102f275c5bbc0fcefb579f78fc870da4c8c"}},"tags":["nested-reference","unchanged"],"summary":"The work of the IETF is to discuss, develop, and disseminate\n technical specifications to support the Internet's operation.\n Technical publication is the process by which that output is\n disseminated to the community at large. As such, it is important to\n understand the requirements on the publication process.\n\nMankin & Hayes Informational [Page 1]\n\f\nRFC 4714 IETF Technical Publisher Requirements October 2006","scope_keywords":["4714","management","policies","policy","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null}],"search_text":"IETF RFC 4714 The work of the IETF is to discuss, develop, and disseminate\n technical specifications to support the Internet's operation.\n Technical publication is the process by which that output is\n disseminated to the community at large. As such, it is important to\n understand the requirements on the publication process.\n\nMankin & Hayes Informational [Page 1]\n\f\nRFC 4714 IETF Technical Publisher Requirements October 2006 4714 management policies policy validation nested-reference unchanged"},{"id":"IETF RFC 6635","type":"specification","body":"IETF","designation":"RFC 6635","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6635.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6635.txt","https://www.rfc-editor.org/rfc/rfc6635.pdf"],"folder":"IETF/RFC-6635","files":{"txt":{"path":"standards/IETF/RFC-6635/RFC-6635.txt","sha256":"7607a61dc2606075f70130b7357ebd6d6aa7ce0b801c6cf7464f4fb4ef40e62b"}},"tags":["nested-reference","unchanged"],"summary":"The RFC Editor model described in this document divides the\n responsibilities for the RFC Series into three functions: the RFC\n Series Editor, the RFC Production Center, and the RFC Publisher.\n Internet Architecture Board (IAB) oversight via the RFC Series\n Oversight Committee (RSOC) is described, as is the relationship\n between the IETF Administrative Oversight Committee (IAOC) and the\n RSOC. This document reflects the experience gained with \"RFC Editor\n Model (Version 1)\", documented in RFC 5620, and obsoletes that\n document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate fo","scope_keywords":["6635","http","license","management","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null},{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null}],"search_text":"IETF RFC 6635 The RFC Editor model described in this document divides the\n responsibilities for the RFC Series into three functions: the RFC\n Series Editor, the RFC Production Center, and the RFC Publisher.\n Internet Architecture Board (IAB) oversight via the RFC Series\n Oversight Committee (RSOC) is described, as is the relationship\n between the IETF Administrative Oversight Committee (IAOC) and the\n RSOC. This document reflects the experience gained with \"RFC Editor\n Model (Version 1)\", documented in RFC 5620, and obsoletes that\n document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate fo 6635 http license management policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 2853","type":"specification","body":"IETF","designation":"RFC 2853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2853.txt","https://www.rfc-editor.org/rfc/rfc2853.pdf"],"folder":"IETF/RFC-2853","files":{"txt":{"path":"standards/IETF/RFC-2853/RFC-2853.txt","sha256":"27100dec2cab8d612457133b07c1d682348a7a2785eab107b6a6bf0ac1a1fb30"}},"tags":["nested-reference","unchanged"],"summary":"The Generic Security Services Application Program Interface (GSS-API)\n offers application programmers uniform access to security services\n atop a variety of underlying cryptographic mechanisms. This document\n specifies the Java bindings for GSS-API which is described at a\n language independent conceptual level in RFC 2743 [GSSAPIv2-UPDATE].\n\n The GSS-API allows a caller application to authenticate a principal\n identity, to delegate rights to a peer, and to apply security\n services such as confidentiality and integrity on a per-message\n basis. Examples of security mechanisms defined for GSS-API are The\n Simple Public-Key GSS-API Mechanism [SPKM] and The Kerberos Version 5\n GSS-API Mechanism [KERBV5].","scope_keywords":["2853","authentication","credential","credentials","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2853 The Generic Security Services Application Program Interface (GSS-API)\n offers application programmers uniform access to security services\n atop a variety of underlying cryptographic mechanisms. This document\n specifies the Java bindings for GSS-API which is described at a\n language independent conceptual level in RFC 2743 [GSSAPIv2-UPDATE].\n\n The GSS-API allows a caller application to authenticate a principal\n identity, to delegate rights to a peer, and to apply security\n services such as confidentiality and integrity on a per-message\n basis. Examples of security mechanisms defined for GSS-API are The\n Simple Public-Key GSS-API Mechanism [SPKM] and The Kerberos Version 5\n GSS-API Mechanism [KERBV5]. 2853 authentication credential credentials key nested-reference unchanged"},{"id":"IETF RFC 2860","type":"specification","body":"IETF","designation":"RFC 2860","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2860.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2860.txt","https://www.rfc-editor.org/rfc/rfc2860.pdf"],"folder":"IETF/RFC-2860","files":{"txt":{"path":"standards/IETF/RFC-2860/RFC-2860.txt","sha256":"61f1a46685b6361075be4a89de999294f2d7ac8031cc6a4b86f256cffed5c123"}},"tags":["nested-reference","unchanged"],"summary":"This document places on record the text of the Memorandum of\n Understanding concerning the technical work of the IANA that was\n signed on March 1, 2000 between the IETF and ICANN, and ratified by\n the ICANN Board on March 10, 2000.\n\nMoU text as signed\n\n MEMORANDUM OF UNDERSTANDING CONCERNING THE TECHNICAL WORK OF THE\n INTERNET ASSIGNED NUMBERS AUTHORITY\n\n 1. This Memorandum of Understanding (\"MOU\") defines an agreement\n between the Internet Engineering Task Force and the Internet\n Corporation for Assigned Names and Numbers. Its intent is exclusively\n to define the technical work to be carried out by the Internet\n Assigned Numbers Authority on behalf of the Internet Engineering Task\n Force and the Internet Research Task Force. It is recognized that\n ICANN may, through the IANA, provide similar services to other\n organisations with respect to protocols not within IETF's scope (i.e.\n regist","scope_keywords":["2860","management","policy","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 3330","folder":"IETF/RFC-3330","source":"IETF/RFC-3330/RFC-3330.txt","version":null},{"body":"IETF","designation":"RFC 3716","folder":"IETF/RFC-3716","source":"IETF/RFC-3716/RFC-3716.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4773","folder":"IETF/RFC-4773","source":"IETF/RFC-4773/RFC-4773.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 5736","folder":"IETF/RFC-5736","source":"IETF/RFC-5736/RFC-5736.txt","version":null},{"body":"IETF","designation":"RFC 5771","folder":"IETF/RFC-5771","source":"IETF/RFC-5771/RFC-5771.txt","version":null},{"body":"IETF","designation":"RFC 5855","folder":"IETF/RFC-5855","source":"IETF/RFC-5855/RFC-5855.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 2860 This document places on record the text of the Memorandum of\n Understanding concerning the technical work of the IANA that was\n signed on March 1, 2000 between the IETF and ICANN, and ratified by\n the ICANN Board on March 10, 2000.\n\nMoU text as signed\n\n MEMORANDUM OF UNDERSTANDING CONCERNING THE TECHNICAL WORK OF THE\n INTERNET ASSIGNED NUMBERS AUTHORITY\n\n 1. This Memorandum of Understanding (\"MOU\") defines an agreement\n between the Internet Engineering Task Force and the Internet\n Corporation for Assigned Names and Numbers. Its intent is exclusively\n to define the technical work to be carried out by the Internet\n Assigned Numbers Authority on behalf of the Internet Engineering Task\n Force and the Internet Research Task Force. It is recognized that\n ICANN may, through the IANA, provide similar services to other\n organisations with respect to protocols not within IETF's scope (i.e.\n regist 2860 management policy registered subject nested-reference unchanged"},{"id":"IETF RFC 5736","type":"specification","body":"IETF","designation":"RFC 5736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5736.txt","https://www.rfc-editor.org/rfc/rfc5736.pdf"],"folder":"IETF/RFC-5736","files":{"txt":{"path":"standards/IETF/RFC-5736/RFC-5736.txt","sha256":"01745fb12c1d4452436b54944bc995cfbb78d69d135e67c0d3e23438194d5463"}},"tags":["nested-reference","unchanged"],"summary":"This is a direction to IANA concerning the creation and management of\n the IANA IPv4 Special Purpose Address Registry.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5736.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights re","scope_keywords":["5736","http","license","management","policies","policy","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5735","folder":"IETF/RFC-5735","source":"IETF/RFC-5735/RFC-5735.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6890","folder":"IETF/RFC-6890","source":"IETF/RFC-6890/RFC-6890.txt","version":null}],"search_text":"IETF RFC 5736 This is a direction to IANA concerning the creation and management of\n the IANA IPv4 Special Purpose Address Registry.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5736.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights re 5736 http license management policies policy subject trust validation nested-reference unchanged"},{"id":"IETF RFC 287","type":"specification","body":"IETF","designation":"RFC 287","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc287.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc287.txt","https://www.rfc-editor.org/rfc/rfc287.pdf"],"folder":"IETF/RFC-287","files":{"txt":{"path":"standards/IETF/RFC-287/RFC-287.txt","sha256":"a285fdb9606ddef463390b5068ff5f0f49490240c7c41dbe2ad19b4fafb25c99"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: #287 BBN\nNIC: #8273 22 December 1971\nCategories: F, G.3\nUpdates: RFC #267\nObsoletes: None\n\n Status of Network Hosts\n\n This RFC reports on the status of most Network Hosts from\nDecember 6 to December 18. Due to hardware debugging, the BBN\nprototype Terminal IMP (Network Address 158) was unavailable for most\nof the two weeks from November 22 to December 6. There was, therefore,\nno Host status reports for that period.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on\n the Network as servers (available for use from\n other sites) on a regular basis for at least two\n weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n\n 133 BBN PDP-10 (B)\n 71 Rand PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500","scope_keywords":["287"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 287 Network Working Group Ellen Westheimer\nRequest for Comments: #287 BBN\nNIC: #8273 22 December 1971\nCategories: F, G.3\nUpdates: RFC #267\nObsoletes: None\n\n Status of Network Hosts\n\n This RFC reports on the status of most Network Hosts from\nDecember 6 to December 18. Due to hardware debugging, the BBN\nprototype Terminal IMP (Network Address 158) was unavailable for most\nof the two weeks from November 22 to December 6. There was, therefore,\nno Host status reports for that period.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on\n the Network as servers (available for use from\n other sites) on a regular basis for at least two\n weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n\n 133 BBN PDP-10 (B)\n 71 Rand PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500 287 nested-reference unchanged"},{"id":"IETF RFC 288","type":"specification","body":"IETF","designation":"RFC 288","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc288.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc288.txt","https://www.rfc-editor.org/rfc/rfc288.pdf"],"folder":"IETF/RFC-288","files":{"txt":{"path":"standards/IETF/RFC-288/RFC-288.txt","sha256":"a648899c2838ed7d48edd3a6f222266c02c1dc25b9ff37fa5dc457bf08a6e46d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Westheimer\nRequest for Comments: 288 BBN\nNIC: 8274 January 6, 1972\nObsoletes: None\nUpdates: 287\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from December 20\n to December 30. (On December 24 and December 31 BBN celebrated\n Christmas and New Year's Day respectively.)\n\n During these two weeks the Lincoln Labs TX2 (Network Address 112)\n became a server.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10 (B)\n 15 Case PDP-10\n 13 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are p","scope_keywords":["288"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 293","folder":"IETF/RFC-293","source":"IETF/RFC-293/RFC-293.txt","version":null}],"search_text":"IETF RFC 288 Network Working Group E. Westheimer\nRequest for Comments: 288 BBN\nNIC: 8274 January 6, 1972\nObsoletes: None\nUpdates: 287\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from December 20\n to December 30. (On December 24 and December 31 BBN celebrated\n Christmas and New Year's Day respectively.)\n\n During these two weeks the Lincoln Labs TX2 (Network Address 112)\n became a server.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10 (B)\n 15 Case PDP-10\n 13 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are p 288 nested-reference unchanged"},{"id":"IETF RFC 293","type":"specification","body":"IETF","designation":"RFC 293","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc293.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc293.txt","https://www.rfc-editor.org/rfc/rfc293.pdf"],"folder":"IETF/RFC-293","files":{"txt":{"path":"standards/IETF/RFC-293/RFC-293.txt","sha256":"eaffc99b912925bece12dfd7fb63d453376042e1b2cece1b36a0a2a919908ef4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRFC #293 BBN\nNIC #8303 18 January 1972\nCategories: F, G.3\nUpdates: RFC 288\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January\n3 to January 15.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 133 BBN PDP-10 (B)\n 8* SDC IBM-370/155\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC-(B6500)\n\n2) Hosts which are currently intended to be users only. Included here\nare the Terminal IMPs, which are presently in the Network (AMES,\nMITRE, NBS and BBN**). This category also includes the Network\nControl Center Computer (Network Address 5)","scope_keywords":["293"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 293 Network Working Group Ellen Westheimer\nRFC #293 BBN\nNIC #8303 18 January 1972\nCategories: F, G.3\nUpdates: RFC 288\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January\n3 to January 15.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 133 BBN PDP-10 (B)\n 8* SDC IBM-370/155\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC-(B6500)\n\n2) Hosts which are currently intended to be users only. Included here\nare the Terminal IMPs, which are presently in the Network (AMES,\nMITRE, NBS and BBN**). This category also includes the Network\nControl Center Computer (Network Address 5) 293 nested-reference unchanged"},{"id":"IETF RFC 4009","type":"specification","body":"IETF","designation":"RFC 4009","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4009.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4009.txt","https://www.rfc-editor.org/rfc/rfc4009.pdf"],"folder":"IETF/RFC-4009","files":{"txt":{"path":"standards/IETF/RFC-4009/RFC-4009.txt","sha256":"8457c58665575c6d9d7aa69b3f7957e30d0abe7a08a9bdcede97feac464c60a5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the SEED encryption algorithm, which has been\n adopted by most of the security systems in the Republic of Korea.\n Included are a description of the cipher and the key scheduling\n algorithm (Section 2), the S-boxes (Appendix A), and a set of test\n vectors (Appendix B).\n\n1. Introduction","scope_keywords":["4009","algorithm","encryption","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 4196","folder":"IETF/RFC-4196","source":"IETF/RFC-4196/RFC-4196.txt","version":null},{"body":"IETF","designation":"RFC 4269","folder":"IETF/RFC-4269","source":"IETF/RFC-4269/RFC-4269.txt","version":null}],"search_text":"IETF RFC 4009 This document describes the SEED encryption algorithm, which has been\n adopted by most of the security systems in the Republic of Korea.\n Included are a description of the cipher and the key scheduling\n algorithm (Section 2), the S-boxes (Appendix A), and a set of test\n vectors (Appendix B).\n\n1. Introduction 4009 algorithm encryption key keys presentation nested-reference unchanged"},{"id":"IETF RFC 4269","type":"specification","body":"IETF","designation":"RFC 4269","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4269.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4269.txt","https://www.rfc-editor.org/rfc/rfc4269.pdf"],"folder":"IETF/RFC-4269","files":{"txt":{"path":"standards/IETF/RFC-4269/RFC-4269.txt","sha256":"a1132bf03be7ff05ae9be59189632f849a200c2f1c86ce9ecc2f94f51b668f54"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the SEED encryption algorithm, which has been\n adopted by most of the security systems in the Republic of Korea.\n Included are a description of the encryption and the key scheduling\n algorithm (Section 2), the S-boxes (Appendix A), and a set of test\n vectors (Appendix B).\n\n This document obsoletes RFC 4009.\n\nLee, et al. Informational [Page 1]\n\f\nRFC 4269 The SEED Encryption Algorithm December 2005\n\n1. Introduction","scope_keywords":["4269","algorithm","encryption","key","keys","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5669","folder":"IETF/RFC-5669","source":"IETF/RFC-5669/RFC-5669.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"IETF RFC 4269 This document describes the SEED encryption algorithm, which has been\n adopted by most of the security systems in the Republic of Korea.\n Included are a description of the encryption and the key scheduling\n algorithm (Section 2), the S-boxes (Appendix A), and a set of test\n vectors (Appendix B).\n\n This document obsoletes RFC 4009.\n\nLee, et al. Informational [Page 1]\n\f\nRFC 4269 The SEED Encryption Algorithm December 2005\n\n1. Introduction 4269 algorithm encryption key keys presentation nested-reference unchanged"},{"id":"IETF RFC 291","type":"specification","body":"IETF","designation":"RFC 291","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc291.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc291.txt","https://www.rfc-editor.org/rfc/rfc291.pdf"],"folder":"IETF/RFC-291","files":{"txt":{"path":"standards/IETF/RFC-291/RFC-291.txt","sha256":"7a7b1af69e2c151891db1298c0fe7aaafb187e7b983fbe5dc6ae24e712f1a574"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group 14 January 1972\nRequest for Comments 291 D. B. McKay, IBM\nNIC 8301 (Area Code 914)- 945-1159\nCategories: A.2, D.4, D.7\n\n Data Management Meeting Announcement\n ------------------------------------\n\n Mitre will host a Network Data Management Meeting, February 23,\n 24. As a follow-on from past meetings, the meeting is being held to\n accomplish two objectives. As a result of the first data management\n meeting in Aug- ust, the general consensus was a need to learn about\n applications of net- work data facilities, and how networks will\n better help users achieve their objectives. There are several people\n that have expressed an inter- est in discussing applications. The\n attached schedule is a list of people who have agreed to talk. If\n anyone knows of other people interested in discussing applications,\n please have them contact me.\n\n Secondly, the meeting will discuss an","scope_keywords":["291","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null}],"search_text":"IETF RFC 291 Network Working Group 14 January 1972\nRequest for Comments 291 D. B. McKay, IBM\nNIC 8301 (Area Code 914)- 945-1159\nCategories: A.2, D.4, D.7\n\n Data Management Meeting Announcement\n ------------------------------------\n\n Mitre will host a Network Data Management Meeting, February 23,\n 24. As a follow-on from past meetings, the meeting is being held to\n accomplish two objectives. As a result of the first data management\n meeting in Aug- ust, the general consensus was a need to learn about\n applications of net- work data facilities, and how networks will\n better help users achieve their objectives. There are several people\n that have expressed an inter- est in discussing applications. The\n attached schedule is a list of people who have agreed to talk. If\n anyone knows of other people interested in discussing applications,\n please have them contact me.\n\n Secondly, the meeting will discuss an 291 management nested-reference unchanged"},{"id":"IETF RFC 4431","type":"specification","body":"IETF","designation":"RFC 4431","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4431.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4431.txt","https://www.rfc-editor.org/rfc/rfc4431.pdf"],"folder":"IETF/RFC-4431","files":{"txt":{"path":"standards/IETF/RFC-4431/RFC-4431.txt","sha256":"1c76a6d113b616b06b3118f1024926c8f4ea605a8ef57865d9641ad24e88c5ff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Andrews\nRequest for Comments: 4431 Internet Systems Consortium\nCategory: Informational S. Weiler\n SPARTA, Inc.\n February 2006\n\n The DNSSEC Lookaside Validation (DLV) DNS Resource Record\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document defines a new DNS resource record, called the DNSSEC\n Lookaside Validation (DLV) RR, for publishing DNSSEC trust anchors\n outside of the DNS delegation chain.\n\n1. Introduction\n\n DNSSEC [1] [2] [3] authenticates DNS data by building public-key\n signature chains along the DNS delegation chain from a trust anchor,\n ideally a trust anchor for the DNS root.\n\n This document defines a new resource record for publishing such t","scope_keywords":["4431","algorithm","authentication","http","key","license","presentation","signature","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5074","folder":"IETF/RFC-5074","source":"IETF/RFC-5074/RFC-5074.txt","version":null}],"search_text":"IETF RFC 4431 Network Working Group M. Andrews\nRequest for Comments: 4431 Internet Systems Consortium\nCategory: Informational S. Weiler\n SPARTA, Inc.\n February 2006\n\n The DNSSEC Lookaside Validation (DLV) DNS Resource Record\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2006).\n\nAbstract\n\n This document defines a new DNS resource record, called the DNSSEC\n Lookaside Validation (DLV) RR, for publishing DNSSEC trust anchors\n outside of the DNS delegation chain.\n\n1. Introduction\n\n DNSSEC [1] [2] [3] authenticates DNS data by building public-key\n signature chains along the DNS delegation chain from a trust anchor,\n ideally a trust anchor for the DNS root.\n\n This document defines a new resource record for publishing such t 4431 algorithm authentication http key license presentation signature subject trust validation nested-reference unchanged"},{"id":"IETF RFC 2933","type":"specification","body":"IETF","designation":"RFC 2933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2933.txt","https://www.rfc-editor.org/rfc/rfc2933.pdf"],"folder":"IETF/RFC-2933","files":{"txt":{"path":"standards/IETF/RFC-2933/RFC-2933.txt","sha256":"483b0abfbf8a376f1820df2392f8007cc57489a2e14211b029ae509375de04f7"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing the Internet\n Group Management Protocol (IGMP).","scope_keywords":["2933","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2933 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes objects used for managing the Internet\n Group Management Protocol (IGMP). 2933 management nested-reference unchanged"},{"id":"IETF RFC 2934","type":"specification","body":"IETF","designation":"RFC 2934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2934.txt","https://www.rfc-editor.org/rfc/rfc2934.pdf"],"folder":"IETF/RFC-2934","files":{"txt":{"path":"standards/IETF/RFC-2934/RFC-2934.txt","sha256":"e121ea97c4c98e70d21552bafd1e40acbaedcf0611b7da3ba6ae4ddb3dcd5554"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Protocol Independent Multicast (PIM) protocol for IPv4.","scope_keywords":["2934","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null}],"search_text":"IETF RFC 2934 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in the Internet community.\n In particular, it describes managed objects used for managing the\n Protocol Independent Multicast (PIM) protocol for IPv4. 2934 management nested-reference unchanged"},{"id":"IETF RFC 2935","type":"specification","body":"IETF","designation":"RFC 2935","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2935.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2935.txt","https://www.rfc-editor.org/rfc/rfc2935.pdf"],"folder":"IETF/RFC-2935","files":{"txt":{"path":"standards/IETF/RFC-2935/RFC-2935.txt","sha256":"b323eba8034797c6c47391bda62c455d1382d80197ee53db6e1f799393c157f4"}},"tags":["nested-reference","unchanged"],"summary":"Internet Open Trading Protocol (IOTP) messages will be carried as\n Extensible Markup Language (XML) documents. As such, the goal of\n mapping to the transport layer is to ensure that the underlying XML\n documents are carried successfully between the various parties.\n\n This document describes that mapping for the Hyper Text Transport\n Protocol (HTTP), Versions 1.0 and 1.1.","scope_keywords":["2935","delivery","http","key","signature","signatures","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2935 Internet Open Trading Protocol (IOTP) messages will be carried as\n Extensible Markup Language (XML) documents. As such, the goal of\n mapping to the transport layer is to ensure that the underlying XML\n documents are carried successfully between the various parties.\n\n This document describes that mapping for the Hyper Text Transport\n Protocol (HTTP), Versions 1.0 and 1.1. 2935 delivery http key signature signatures tls nested-reference unchanged"},{"id":"IETF RFC 2940","type":"specification","body":"IETF","designation":"RFC 2940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2940.txt","https://www.rfc-editor.org/rfc/rfc2940.pdf"],"folder":"IETF/RFC-2940","files":{"txt":{"path":"standards/IETF/RFC-2940/RFC-2940.txt","sha256":"281a3e513e9d34e215895bb18710161af45806ab1fc1d0b309f6ce039d72bdae"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing a client of the Common\n Open Policy Service (COPS) protocol.\n\n This memo includes a MIB module in a manner that is compliant to the\n SMIv2 [V2SMI].\n\nSmith Standards Track [Page 1]\n\f\nRFC 2940 COPS Client MIB October 2000\n\n1. The SNMP Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n o An overall architecture, described in an Architecture for\n Describing SNMP Management Frameworks [ARCH].\n\n o Mechanisms for describing and naming objects and events for the\n purpose of management. The first version of this Structure of\n Management Information (SMI) is called SMIv1 and described in\n STD 16, RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC\n 1215 [V1TRAPS]","scope_keywords":["2940","algorithm","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 2940 This memo defines a portion of the Management Information Base (MIB)\n for use with network management protocols in TCP/IP based internets.\n In particular it defines objects for managing a client of the Common\n Open Policy Service (COPS) protocol.\n\n This memo includes a MIB module in a manner that is compliant to the\n SMIv2 [V2SMI].\n\nSmith Standards Track [Page 1]\n\f\nRFC 2940 COPS Client MIB October 2000\n\n1. The SNMP Management Framework\n\n The SNMP Management Framework presently consists of five major\n components:\n\n o An overall architecture, described in an Architecture for\n Describing SNMP Management Frameworks [ARCH].\n\n o Mechanisms for describing and naming objects and events for the\n purpose of management. The first version of this Structure of\n Management Information (SMI) is called SMIv1 and described in\n STD 16, RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC\n 1215 [V1TRAPS] 2940 algorithm management policy nested-reference unchanged"},{"id":"IETF RFC 2942","type":"specification","body":"IETF","designation":"RFC 2942","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2942.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2942.txt","https://www.rfc-editor.org/rfc/rfc2942.pdf"],"folder":"IETF/RFC-2942","files":{"txt":{"path":"standards/IETF/RFC-2942/RFC-2942.txt","sha256":"12b3cb8f21d4144aae445469dd88799dbadaa5ddaa500e6fe9f5e60f53aee31b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Ts'o\nRequest for Comments: 2942 VA Linux Systems\nCategory: Standards Track September 2000\n\n Telnet Authentication: Kerberos Version 5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes how Kerberos Version 5 [1] is used with the\n telnet protocol. It describes an telnet authentication suboption to\n be used with the telnet authentication option [2]. This mechanism\n can also used to provide keying material to provide data\n confidentiality ser","scope_keywords":["2942","authentication","credential","credentials","encryption","key","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2942 Network Working Group T. Ts'o\nRequest for Comments: 2942 VA Linux Systems\nCategory: Standards Track September 2000\n\n Telnet Authentication: Kerberos Version 5\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document describes how Kerberos Version 5 [1] is used with the\n telnet protocol. It describes an telnet authentication suboption to\n be used with the telnet authentication option [2]. This mechanism\n can also used to provide keying material to provide data\n confidentiality ser 2942 authentication credential credentials encryption key qualified nested-reference unchanged"},{"id":"IETF RFC 2943","type":"specification","body":"IETF","designation":"RFC 2943","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2943.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2943.txt","https://www.rfc-editor.org/rfc/rfc2943.pdf"],"folder":"IETF/RFC-2943","files":{"txt":{"path":"standards/IETF/RFC-2943/RFC-2943.txt","sha256":"b930e0eda17f957736855619fb4285379a5a83f49d20446d34c01e8891bc4af4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a telnet authentication mechanism using the\n Digital Signature Algorithm (DSA) [FIPS186]. It relies on the Telnet\n Authentication Option [RFC2941].\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n\n Authentication Commands:\n\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types:\n\n DSS 14\n\n Modifiers:\n\n AUTH_WHO_MASK 1\n AUTH_CLIENT_TO_SERVER 0\n AUTH_SERVER_TO CLIENT 1\n\nHousley, et al. Standards Track [Page 1]\n\f\nRFC 2943 TELNET Authentication Using DSA September 2000\n\n AUTH_HOW_MASK 2\n AUTH_HOW_ONE_WAY 0\n AUTH_HOW_MUTUAL 2\n\n ENCRYPT_MASK 20\n ENCRYPT_OFF 0\n ENCRYPT_USING_TELOPT 4\n ENCRYPT_AFTER_EXCHANGE 16\n ENCRYPT_RESERVED 20\n\n INI_CRED_FWD_MASK 8\n INI_CRED_FWD_OFF 0\n INI_CRED_FWD_ON 8\n\n Sub-option Commands:\n\n DSS_INITIALIZE 1\n DSS_TOKENBA 2\n DSS_CERTA_TOKENAB 3\n DSS_CERTB_TOKENBA2 4\n\n2. TELNET Security Extensions\n\n TELNET, as a protocol, has no concept of security. Wi","scope_keywords":["2943","algorithm","authentication","authorization","certificate","certificates","encryption","key","keys","profile","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2943 This document defines a telnet authentication mechanism using the\n Digital Signature Algorithm (DSA) [FIPS186]. It relies on the Telnet\n Authentication Option [RFC2941].\n\n1. Command Names and Codes\n\n AUTHENTICATION 37\n\n Authentication Commands:\n\n IS 0\n SEND 1\n REPLY 2\n NAME 3\n\n Authentication Types:\n\n DSS 14\n\n Modifiers:\n\n AUTH_WHO_MASK 1\n AUTH_CLIENT_TO_SERVER 0\n AUTH_SERVER_TO CLIENT 1\n\nHousley, et al. Standards Track [Page 1]\n\f\nRFC 2943 TELNET Authentication Using DSA September 2000\n\n AUTH_HOW_MASK 2\n AUTH_HOW_ONE_WAY 0\n AUTH_HOW_MUTUAL 2\n\n ENCRYPT_MASK 20\n ENCRYPT_OFF 0\n ENCRYPT_USING_TELOPT 4\n ENCRYPT_AFTER_EXCHANGE 16\n ENCRYPT_RESERVED 20\n\n INI_CRED_FWD_MASK 8\n INI_CRED_FWD_OFF 0\n INI_CRED_FWD_ON 8\n\n Sub-option Commands:\n\n DSS_INITIALIZE 1\n DSS_TOKENBA 2\n DSS_CERTA_TOKENAB 3\n DSS_CERTB_TOKENBA2 4\n\n2. TELNET Security Extensions\n\n TELNET, as a protocol, has no concept of security. Wi 2943 algorithm authentication authorization certificate certificates encryption key keys profile signature nested-reference unchanged"},{"id":"IETF RFC 2944","type":"specification","body":"IETF","designation":"RFC 2944","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2944.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2944.txt","https://www.rfc-editor.org/rfc/rfc2944.pdf"],"folder":"IETF/RFC-2944","files":{"txt":{"path":"standards/IETF/RFC-2944/RFC-2944.txt","sha256":"49c4e07bf56e63490a1fd6894b0ab57a9d169710648214db906197523eae3bb3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Wu\nRequest for Comments: 2944 Standford University\nCategory: Standards Track September 2000\n\n Telnet Authentication: SRP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies an authentication scheme for the Telnet\n protocol under the framework described in [RFC2941], using the Secure\n Remote Password Protocol (SRP) authentication mechanism. The\n specific mechanism, SRP-SHA1, is described in [RFC2945].\n\n1. Command Names and Codes\n\n Authentica","scope_keywords":["2944","authentication","encryption","hash","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2944 Network Working Group T. Wu\nRequest for Comments: 2944 Standford University\nCategory: Standards Track September 2000\n\n Telnet Authentication: SRP\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies an authentication scheme for the Telnet\n protocol under the framework described in [RFC2941], using the Secure\n Remote Password Protocol (SRP) authentication mechanism. The\n specific mechanism, SRP-SHA1, is described in [RFC2945].\n\n1. Command Names and Codes\n\n Authentica 2944 authentication encryption hash key keys nested-reference unchanged"},{"id":"IETF RFC 2947","type":"specification","body":"IETF","designation":"RFC 2947","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2947.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2947.txt","https://www.rfc-editor.org/rfc/rfc2947.pdf"],"folder":"IETF/RFC-2947","files":{"txt":{"path":"standards/IETF/RFC-2947/RFC-2947.txt","sha256":"16592d6fd89462fa7fb13f32da60e702554c1f779f29d4e996df435f09052c68"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Altman\nRequest for Comments: 2947 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: DES3 64 bit Cipher Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the Triple-DES (data encryption\n standard) encryption algorithm in cipher feedback mode with the\n telnet encryption option.\n\n1. Command Names and Codes\n\n Encryption Type\n\n DES3CFB64 3\n\n Suboption Commands\n\n CFB64IV 1\n CFB64IVOK 2\n CFB64I","scope_keywords":["2947","algorithm","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2947 Network Working Group J. Altman\nRequest for Comments: 2947 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: DES3 64 bit Cipher Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the Triple-DES (data encryption\n standard) encryption algorithm in cipher feedback mode with the\n telnet encryption option.\n\n1. Command Names and Codes\n\n Encryption Type\n\n DES3CFB64 3\n\n Suboption Commands\n\n CFB64IV 1\n CFB64IVOK 2\n CFB64I 2947 algorithm authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2948","type":"specification","body":"IETF","designation":"RFC 2948","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2948.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2948.txt","https://www.rfc-editor.org/rfc/rfc2948.pdf"],"folder":"IETF/RFC-2948","files":{"txt":{"path":"standards/IETF/RFC-2948/RFC-2948.txt","sha256":"1d2a5a65a202f15d3df4b4eb25c2f908c23fa019babf59557e96000ea82e840c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Altman\nRequest for Comments: 2948 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: DES3 64 bit Output Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the Triple-DES (data encryption\n standard) encryption algorithm in output feedback mode with the\n telnet encryption option.\n\n1. Command Names and Codes\n\n Encryption Type\n\n DES3OFB64 4\n\n Suboption Commands\n\n OFB64IV 1\n OFB64IVOK 2\n OFB64I","scope_keywords":["2948","algorithm","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2948 Network Working Group J. Altman\nRequest for Comments: 2948 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: DES3 64 bit Output Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the Triple-DES (data encryption\n standard) encryption algorithm in output feedback mode with the\n telnet encryption option.\n\n1. Command Names and Codes\n\n Encryption Type\n\n DES3OFB64 4\n\n Suboption Commands\n\n OFB64IV 1\n OFB64IVOK 2\n OFB64I 2948 algorithm authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2949","type":"specification","body":"IETF","designation":"RFC 2949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2949.txt","https://www.rfc-editor.org/rfc/rfc2949.pdf"],"folder":"IETF/RFC-2949","files":{"txt":{"path":"standards/IETF/RFC-2949/RFC-2949.txt","sha256":"4ae82fc9f78aceeef60d90952ceb20c6aa845117ed807fc73ca2af44791c7a2f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Altman\nRequest for Comments: 2949 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: CAST-128 64 bit Output Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the CAST-128 encryption algorithm\n in output feedback mode with the telnet encryption option. Two key\n sizes are defined: 40 bit and 128 bit.\n\n1. Command Names and Codes\n\n Encryption Type\n\n CAST540OFB64 9\n CAST128OFB64 11\n\n Suboption","scope_keywords":["2949","algorithm","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2949 Network Working Group J. Altman\nRequest for Comments: 2949 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: CAST-128 64 bit Output Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the CAST-128 encryption algorithm\n in output feedback mode with the telnet encryption option. Two key\n sizes are defined: 40 bit and 128 bit.\n\n1. Command Names and Codes\n\n Encryption Type\n\n CAST540OFB64 9\n CAST128OFB64 11\n\n Suboption 2949 algorithm authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 2950","type":"specification","body":"IETF","designation":"RFC 2950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2950.txt","https://www.rfc-editor.org/rfc/rfc2950.pdf"],"folder":"IETF/RFC-2950","files":{"txt":{"path":"standards/IETF/RFC-2950/RFC-2950.txt","sha256":"099852d70f48eca6e603726a537e9f1742c543187bad992e7b66331a0f93b5a0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Altman\nRequest for Comments: 2950 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: CAST-128 64 bit Cipher Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the CAST-128 encryption algorithm\n in cipher feedback mode with the telnet encryption option. Two key\n sizes are defined: 40 bit and 128 bit.\n\n1. Command Names and Codes\n\n Encryption Type\n\n CAST540CFB64 8\n CAST128CFB64 10\n\n Suboption","scope_keywords":["2950","algorithm","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2950 Network Working Group J. Altman\nRequest for Comments: 2950 Columbia University\nCategory: Standards Track September 2000\n\n Telnet Encryption: CAST-128 64 bit Cipher Feedback\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document specifies how to use the CAST-128 encryption algorithm\n in cipher feedback mode with the telnet encryption option. Two key\n sizes are defined: 40 bit and 128 bit.\n\n1. Command Names and Codes\n\n Encryption Type\n\n CAST540CFB64 8\n CAST128CFB64 10\n\n Suboption 2950 algorithm authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 4296","type":"specification","body":"IETF","designation":"RFC 4296","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4296.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4296.txt","https://www.rfc-editor.org/rfc/rfc4296.pdf"],"folder":"IETF/RFC-4296","files":{"txt":{"path":"standards/IETF/RFC-4296/RFC-4296.txt","sha256":"f6dda67521ca5abe3fae3a4b19d4aac50a4fcc1441ab1cd7e7e76a64aa3cab08"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an abstract architecture for Direct Data\n Placement (DDP) and Remote Direct Memory Access (RDMA) protocols to\n run on Internet Protocol-suite transports. This architecture does\n not necessarily reflect the proper way to implement such protocols,\n but is, rather, a descriptive tool for defining and understanding the\n protocols. DDP allows the efficient placement of data into buffers\n designated by Upper Layer Protocols (e.g., RDMA). RDMA provides the\n semantics to enable Remote Direct Memory Access between peers in a\n way consistent with application requirements.\n\nBailey & Talpey Informational [Page 1]\n\f\nRFC 4296 DDP and RDMA Architecture December 2005","scope_keywords":["4296","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null}],"search_text":"IETF RFC 4296 This document defines an abstract architecture for Direct Data\n Placement (DDP) and Remote Direct Memory Access (RDMA) protocols to\n run on Internet Protocol-suite transports. This architecture does\n not necessarily reflect the proper way to implement such protocols,\n but is, rather, a descriptive tool for defining and understanding the\n protocols. DDP allows the efficient placement of data into buffers\n designated by Upper Layer Protocols (e.g., RDMA). RDMA provides the\n semantics to enable Remote Direct Memory Access between peers in a\n way consistent with application requirements.\n\nBailey & Talpey Informational [Page 1]\n\f\nRFC 4296 DDP and RDMA Architecture December 2005 4296 delivery nested-reference unchanged"},{"id":"IETF RFC 4838","type":"specification","body":"IETF","designation":"RFC 4838","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4838.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4838.txt","https://www.rfc-editor.org/rfc/rfc4838.pdf"],"folder":"IETF/RFC-4838","files":{"txt":{"path":"standards/IETF/RFC-4838/RFC-4838.txt","sha256":"5e24f7c42d7cce46f321a2264b44fc91f7888f69d68b95ca10bd3c680e8d6790"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for delay-tolerant and\n disruption-tolerant networks, and is an evolution of the architecture\n originally designed for the Interplanetary Internet, a communication\n system envisioned to provide Internet-like services across\n interplanetary distances in support of deep space exploration. This\n document describes an architecture that addresses a variety of\n problems with internetworks having operational and performance\n characteristics that make conventional (Internet-like) networking\n approaches either unworkable or impractical. We define a message-\n oriented overlay that exists above the transport (or other) layers of\n\nCerf, et al. Informational [Page 1]\n\f\nRFC 4838 Delay-Tolerant Networking Architecture April 2007\n\n the networks it interconnects. The document presents a motivation\n for the architecture, an architectural overview, review of state\n m","scope_keywords":["4838","delivery","management","policy","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null}],"search_text":"IETF RFC 4838 This document describes an architecture for delay-tolerant and\n disruption-tolerant networks, and is an evolution of the architecture\n originally designed for the Interplanetary Internet, a communication\n system envisioned to provide Internet-like services across\n interplanetary distances in support of deep space exploration. This\n document describes an architecture that addresses a variety of\n problems with internetworks having operational and performance\n characteristics that make conventional (Internet-like) networking\n approaches either unworkable or impractical. We define a message-\n oriented overlay that exists above the transport (or other) layers of\n\nCerf, et al. Informational [Page 1]\n\f\nRFC 4838 Delay-Tolerant Networking Architecture April 2007\n\n the networks it interconnects. The document presents a motivation\n for the architecture, an architectural overview, review of state\n m 4838 delivery management policy subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 5062","type":"specification","body":"IETF","designation":"RFC 5062","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5062.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5062.txt","https://www.rfc-editor.org/rfc/rfc5062.pdf"],"folder":"IETF/RFC-5062","files":{"txt":{"path":"standards/IETF/RFC-5062/RFC-5062.txt","sha256":"fd859c7eef1a4140c8f53e772ed428796aaa5a0528410a725c237838919485fa"}},"tags":["nested-reference","unchanged"],"summary":"This document describes certain security threats to SCTP. It also\n describes ways to mitigate these threats, in particular by using\n techniques from the SCTP Specification Errata and Issues memo (RFC\n 4460). These techniques are included in RFC 4960, which obsoletes\n RFC 2960. It is hoped that this information will provide some useful\n background information for many of the newest requirements spelled\n out in the SCTP Specification Errata and Issues and included in RFC\n 4960.\n\nStewart, et al. Informational [Page 1]\n\f\nRFC 5062 SCTP Security Attacks September 2007","scope_keywords":["5062","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5061","folder":"IETF/RFC-5061","source":"IETF/RFC-5061/RFC-5061.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null}],"search_text":"IETF RFC 5062 This document describes certain security threats to SCTP. It also\n describes ways to mitigate these threats, in particular by using\n techniques from the SCTP Specification Errata and Issues memo (RFC\n 4460). These techniques are included in RFC 4960, which obsoletes\n RFC 2960. It is hoped that this information will provide some useful\n background information for many of the newest requirements spelled\n out in the SCTP Specification Errata and Issues and included in RFC\n 4960.\n\nStewart, et al. Informational [Page 1]\n\f\nRFC 5062 SCTP Security Attacks September 2007 5062 risk nested-reference unchanged"},{"id":"IETF RFC 2972","type":"specification","body":"IETF","designation":"RFC 2972","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2972.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2972.txt","https://www.rfc-editor.org/rfc/rfc2972.pdf"],"folder":"IETF/RFC-2972","files":{"txt":{"path":"standards/IETF/RFC-2972/RFC-2972.txt","sha256":"76ca57b1e027aad1eb2dca4014b31bdee8d0feb729babf6d6382cf7d799f5878"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Popp\nRequest for Comments: 2972 RealNames Corporation\nCategory: Informational M. Mealling\n Network Solutions\n L. Masinter\n AT&T Labs\n K. Sollins\n MIT\n October 2000\n\n Context and Goals for Common Name Resolution\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document establishes the context and goals for a Common Name\n Resolution Protocol. It defines the terminology used concerning a\n \"Common Name\" and how one might be \"resolved\", and establishes the\n distinction between \"resolution\" and more elaborate search\n mechanisms. It establishes some expected contexts for use of Common\n Name Resolution, and the criteria for evaluating a successf","scope_keywords":["2972","attribute","authentication","http","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null}],"search_text":"IETF RFC 2972 Network Working Group N. Popp\nRequest for Comments: 2972 RealNames Corporation\nCategory: Informational M. Mealling\n Network Solutions\n L. Masinter\n AT&T Labs\n K. Sollins\n MIT\n October 2000\n\n Context and Goals for Common Name Resolution\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n This document establishes the context and goals for a Common Name\n Resolution Protocol. It defines the terminology used concerning a\n \"Common Name\" and how one might be \"resolved\", and establishes the\n distinction between \"resolution\" and more elaborate search\n mechanisms. It establishes some expected contexts for use of Common\n Name Resolution, and the criteria for evaluating a successf 2972 attribute authentication http identification key nested-reference unchanged"},{"id":"IETF RFC 2973","type":"specification","body":"IETF","designation":"RFC 2973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2973.txt","https://www.rfc-editor.org/rfc/rfc2973.pdf"],"folder":"IETF/RFC-2973","files":{"txt":{"path":"standards/IETF/RFC-2973/RFC-2973.txt","sha256":"939ec42f7460c1a4e1d43528a3492d421d7e7d4c0c123839547cfc874d22c6b7"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism to reduce redundant packet\n transmissions for the Intermediate System to Intermediate System\n (IS-IS) Routing protocol, as described in ISO 10589. The described\n mechanism can be used to reduce the flooding of Link State PDUs\n (Protocol Data Units) (LSPs) in IS-IS topologies. The net effect is\n to engineer a flooding topology for LSPs which is a subset of the\n physical topology. This document serves to document the existing\n behavior in deployed implementations.\n\n The document describes behaviors that are backwards compatible with\n implementations that do not support this feature.","scope_keywords":["2973","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 5060","folder":"IETF/RFC-5060","source":"IETF/RFC-5060/RFC-5060.txt","version":null}],"search_text":"IETF RFC 2973 This document describes a mechanism to reduce redundant packet\n transmissions for the Intermediate System to Intermediate System\n (IS-IS) Routing protocol, as described in ISO 10589. The described\n mechanism can be used to reduce the flooding of Link State PDUs\n (Protocol Data Units) (LSPs) in IS-IS topologies. The net effect is\n to engineer a flooding topology for LSPs which is a subset of the\n physical topology. This document serves to document the existing\n behavior in deployed implementations.\n\n The document describes behaviors that are backwards compatible with\n implementations that do not support this feature. 2973 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 298","type":"specification","body":"IETF","designation":"RFC 298","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc298.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc298.txt","https://www.rfc-editor.org/rfc/rfc298.pdf"],"folder":"IETF/RFC-298","files":{"txt":{"path":"standards/IETF/RFC-298/RFC-298.txt","sha256":"ee092313f479f96ddda6158592e4cb490017d1b458dbfe7d6ee4babe049a39c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Westheimer\nRequest for Comments: 298 1 February 1972\nNIC: 8486\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January 17\n to January 28.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network as\n servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10(B)\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are presently in the Network\n (AMES, MITRE, NBS and BBN*). This category also includes the\n Network Control Center (Network Address 5) which is used solely\n for gathering statistics from the Network. Finally, included\n ","scope_keywords":["298"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 298 Network Working Group E. Westheimer\nRequest for Comments: 298 1 February 1972\nNIC: 8486\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January 17\n to January 28.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network as\n servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10(B)\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are presently in the Network\n (AMES, MITRE, NBS and BBN*). This category also includes the\n Network Control Center (Network Address 5) which is used solely\n for gathering statistics from the Network. Finally, included\n  298 nested-reference unchanged"},{"id":"IETF RFC 2984","type":"specification","body":"IETF","designation":"RFC 2984","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc2984.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc2984.txt","https://www.rfc-editor.org/rfc/rfc2984.pdf"],"folder":"IETF/RFC-2984","files":{"txt":{"path":"standards/IETF/RFC-2984/RFC-2984.txt","sha256":"dec90009b47e270a210e5ef6101d444d806c1a9ed6da993c1a01650345f3aee5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how to incorporate CAST-128 (RFC2144) into\n the S/MIME Cryptographic Message Syntax (CMS) as an additional\n algorithm for symmetric encryption. The relevant OIDs and processing\n steps are provided so that CAST-128 may be included in the CMS\n specification (RFC2630) for symmetric content and key encryption.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document (in uppercase,\n as shown) are to be interpreted as described in [RFC2119].\n\n1. Motivation\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) [SMIME2,\n SMIME3] is a set of specifications for the secure transport of MIME\n objects. In the current (S/MIME v3) specifications the mandatory-\n to-implement symmetric algorithm for content encryption and key\n encryption is triple-DES (3DES). While this is perfectly acceptable\n in many cases b","scope_keywords":["2984","algorithm","algorithms","attribute","encryption","key","keys","license","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null}],"search_text":"IETF RFC 2984 This document specifies how to incorporate CAST-128 (RFC2144) into\n the S/MIME Cryptographic Message Syntax (CMS) as an additional\n algorithm for symmetric encryption. The relevant OIDs and processing\n steps are provided so that CAST-128 may be included in the CMS\n specification (RFC2630) for symmetric content and key encryption.\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHOULD\", \"SHOULD NOT\",\n \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this document (in uppercase,\n as shown) are to be interpreted as described in [RFC2119].\n\n1. Motivation\n\n S/MIME (Secure/Multipurpose Internet Mail Extensions) [SMIME2,\n SMIME3] is a set of specifications for the secure transport of MIME\n objects. In the current (S/MIME v3) specifications the mandatory-\n to-implement symmetric algorithm for content encryption and key\n encryption is triple-DES (3DES). While this is perfectly acceptable\n in many cases b 2984 algorithm algorithms attribute encryption key keys license trust nested-reference unchanged"},{"id":"IETF RFC 5902","type":"specification","body":"IETF","designation":"RFC 5902","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5902.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5902.txt","https://www.rfc-editor.org/rfc/rfc5902.pdf"],"folder":"IETF/RFC-5902","files":{"txt":{"path":"standards/IETF/RFC-5902/RFC-5902.txt","sha256":"abde890bfb43453d55723fd2339d59889e3dc0600a915f5ade3c0fbf2c2c375b"}},"tags":["nested-reference","unchanged"],"summary":"There has been much recent discussion on the topic of whether the\n IETF should develop standards for IPv6 Network Address Translators\n (NATs). This document articulates the architectural issues raised by\n IPv6 NATs, the pros and cons of having IPv6 NATs, and provides the\n IAB's thoughts on the current open issues and the solution space.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww","scope_keywords":["5902","http","key","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7934","folder":"IETF/RFC-7934","source":"IETF/RFC-7934/RFC-7934.txt","version":null}],"search_text":"IETF RFC 5902 There has been much recent discussion on the topic of whether the\n IETF should develop standards for IPv6 Network Address Translators\n (NATs). This document articulates the architectural issues raised by\n IPv6 NATs, the pros and cons of having IPv6 NATs, and provides the\n IAB's thoughts on the current open issues and the solution space.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. Documents approved for publication by\n the IAB are not a candidate for any level of Internet Standard; see\n Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://ww 5902 http key license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 3003","type":"specification","body":"IETF","designation":"RFC 3003","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3003.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3003.txt","https://www.rfc-editor.org/rfc/rfc3003.pdf"],"folder":"IETF/RFC-3003","files":{"txt":{"path":"standards/IETF/RFC-3003/RFC-3003.txt","sha256":"c1712b1d3b07bd764f3519c7ffb915e516dba720da2332b26d6c7a8d68b027ef"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Nilsson\nRequest for Comments: 3003 November 2000\nCategory: Standards Track\n\n The audio/mpeg Media Type\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The audio layers of the MPEG-1 and MPEG-2 standards are in frequent\n use on the internet, but there is no uniform Multipurpose Internet\n Mail Extension (MIME) type for these files. The intention of this\n document is to define the media type audio/mpeg to refer to this kind\n of contents.\n\n The key words \"MUST\", \"","scope_keywords":["3003","http","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 3003 Network Working Group M. Nilsson\nRequest for Comments: 3003 November 2000\nCategory: Standards Track\n\n The audio/mpeg Media Type\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The audio layers of the MPEG-1 and MPEG-2 standards are in frequent\n use on the internet, but there is no uniform Multipurpose Internet\n Mail Extension (MIME) type for these files. The intention of this\n document is to define the media type audio/mpeg to refer to this kind\n of contents.\n\n The key words \"MUST\", \" 3003 http key subject nested-reference unchanged"},{"id":"IETF RFC 3005","type":"specification","body":"IETF","designation":"RFC 3005","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3005.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3005.txt","https://www.rfc-editor.org/rfc/rfc3005.pdf"],"folder":"IETF/RFC-3005","files":{"txt":{"path":"standards/IETF/RFC-3005/RFC-3005.txt","sha256":"875bc2625988011e87a266ee9ae4feeff812fe8b0c5ed4937c5cd3b8b56ac7a8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Harris\nRequest for Comments: 3005 Merit Network\nBCP: 45 November 2000\nCategory: Best Current Practice\n\n IETF Discussion List Charter\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Internet Engineering Task Force (IETF) discussion mailing list\n furthers the development and specification of Internet technology\n through discussion of technical issues, and hosts discussions of IETF\n direction, policy, meetings, and procedures. As this is the most\n general IETF mailing list, considerable latitude is allowed.\n Advertising, whether to solicit business or promote employment\n opportunities, falls well outside the ","scope_keywords":["3005","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3683","folder":"IETF/RFC-3683","source":"IETF/RFC-3683/RFC-3683.txt","version":null},{"body":"IETF","designation":"RFC 4693","folder":"IETF/RFC-4693","source":"IETF/RFC-4693/RFC-4693.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null}],"search_text":"IETF RFC 3005 Network Working Group S. Harris\nRequest for Comments: 3005 Merit Network\nBCP: 45 November 2000\nCategory: Best Current Practice\n\n IETF Discussion List Charter\n\nStatus of this Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2000). All Rights Reserved.\n\nAbstract\n\n The Internet Engineering Task Force (IETF) discussion mailing list\n furthers the development and specification of Internet technology\n through discussion of technical issues, and hosts discussions of IETF\n direction, policy, meetings, and procedures. As this is the most\n general IETF mailing list, considerable latitude is allowed.\n Advertising, whether to solicit business or promote employment\n opportunities, falls well outside the  3005 policies policy subject nested-reference unchanged"},{"id":"IETF RFC 4177","type":"specification","body":"IETF","designation":"RFC 4177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4177.txt","https://www.rfc-editor.org/rfc/rfc4177.pdf"],"folder":"IETF/RFC-4177","files":{"txt":{"path":"standards/IETF/RFC-4177/RFC-4177.txt","sha256":"53f286ed64a89b8b04f33a5553f90f4d752f210abc522dbb7f0964d1448459c9"}},"tags":["nested-reference","unchanged"],"summary":"This memo provides an analysis of the architectural aspects of\n multi-homing support for the IPv6 protocol suite. The purpose of\n this analysis is to provide a taxonomy for classification of various\n proposed approaches to multi-homing. It is also an objective of this\n exercise to identify common aspects of this domain of study, and also\n to provide a framework that can allow exploration of some of the\n further implications of various architectural extensions that are\n intended to support multi-homing.\n\nHuston Informational [Page 1]\n\f\nRFC 4177 Multi6 Architecture September 2005","scope_keywords":["4177","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4651","folder":"IETF/RFC-4651","source":"IETF/RFC-4651/RFC-4651.txt","version":null}],"search_text":"IETF RFC 4177 This memo provides an analysis of the architectural aspects of\n multi-homing support for the IPv6 protocol suite. The purpose of\n this analysis is to provide a taxonomy for classification of various\n proposed approaches to multi-homing. It is also an objective of this\n exercise to identify common aspects of this domain of study, and also\n to provide a framework that can allow exploration of some of the\n further implications of various architectural extensions that are\n intended to support multi-homing.\n\nHuston Informational [Page 1]\n\f\nRFC 4177 Multi6 Architecture September 2005 4177 registered nested-reference unchanged"},{"id":"IETF RFC 7157","type":"specification","body":"IETF","designation":"RFC 7157","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7157.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7157.txt","https://www.rfc-editor.org/rfc/rfc7157.pdf"],"folder":"IETF/RFC-7157","files":{"txt":{"path":"standards/IETF/RFC-7157/RFC-7157.txt","sha256":"16778e3292e3a209999de4897ab93ad0c8787db6862e5e5eaa7fcd4524268fa3"}},"tags":["nested-reference","unchanged"],"summary":"Network Address and Port Translation (NAPT) works well for conserving\n global addresses and addressing multihoming requirements because an\n IPv4 NAPT router implements three functions: source address\n selection, next-hop resolution, and (optionally) DNS resolution. For\n IPv6 hosts, one approach could be the use of IPv6-to-IPv6 Network\n Prefix Translation (NPTv6). However, NAT and NPTv6 should be\n avoided, if at all possible, to permit transparent end-to-end\n connectivity. In this document, we analyze the use cases of\n multihoming. We also describe functional requirements and possible\n solutions for multihoming without the use of NAT in IPv6 for hosts\n and small IPv6 networks that would otherwise be unable to meet\n minimum IPv6-allocation criteria. We conclude that DHCPv6-based\n solutions are suitable to solve the multihoming issues described in\n this document, but NPTv6 may be required a","scope_keywords":["7157","algorithm","algorithms","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null}],"search_text":"IETF RFC 7157 Network Address and Port Translation (NAPT) works well for conserving\n global addresses and addressing multihoming requirements because an\n IPv4 NAPT router implements three functions: source address\n selection, next-hop resolution, and (optionally) DNS resolution. For\n IPv6 hosts, one approach could be the use of IPv6-to-IPv6 Network\n Prefix Translation (NPTv6). However, NAT and NPTv6 should be\n avoided, if at all possible, to permit transparent end-to-end\n connectivity. In this document, we analyze the use cases of\n multihoming. We also describe functional requirements and possible\n solutions for multihoming without the use of NAT in IPv6 for hosts\n and small IPv6 networks that would otherwise be unable to meet\n minimum IPv6-allocation criteria. We conclude that DHCPv6-based\n solutions are suitable to solve the multihoming issues described in\n this document, but NPTv6 may be required a 7157 algorithm algorithms http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7498","type":"specification","body":"IETF","designation":"RFC 7498","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7498.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7498.txt","https://www.rfc-editor.org/rfc/rfc7498.pdf"],"folder":"IETF/RFC-7498","files":{"txt":{"path":"standards/IETF/RFC-7498/RFC-7498.txt","sha256":"4d5d9282b99a059f45eb507e13739ed90148b91a0368909a3aa5f6b56b101f15"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of the issues associated with the\n deployment of service functions (such as firewalls, load balancers,\n etc.) in large-scale environments. The term \"service function\n chaining\" is used to describe the definition and instantiation of an\n ordered list of instances of such service functions, and the\n subsequent \"steering\" of traffic flows through those service\n functions.\n\n The set of enabled service function chains reflects operator service\n offerings and is designed in conjunction with application delivery\n and service and network policy.\n\n This document also identifies several key areas that the Service\n Function Chaining (SFC) working group will investigate to guide its\n architectural and protocol work and associated documents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purp","scope_keywords":["7498","delivery","http","key","license","pid","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7665","folder":"IETF/RFC-7665","source":"IETF/RFC-7665/RFC-7665.txt","version":null},{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 7498 This document provides an overview of the issues associated with the\n deployment of service functions (such as firewalls, load balancers,\n etc.) in large-scale environments. The term \"service function\n chaining\" is used to describe the definition and instantiation of an\n ordered list of instances of such service functions, and the\n subsequent \"steering\" of traffic flows through those service\n functions.\n\n The set of enabled service function chains reflects operator service\n offerings and is designed in conjunction with application delivery\n and service and network policy.\n\n This document also identifies several key areas that the Service\n Function Chaining (SFC) working group will investigate to guide its\n architectural and protocol work and associated documents.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purp 7498 delivery http key license pid policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 4267","type":"specification","body":"IETF","designation":"RFC 4267","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4267.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4267.txt","https://www.rfc-editor.org/rfc/rfc4267.pdf"],"folder":"IETF/RFC-4267","files":{"txt":{"path":"standards/IETF/RFC-4267/RFC-4267.txt","sha256":"c3164373dd9df6a52e606b88f18a8fbfeb2f4d15d5201897f3afbd3e0a473ac7"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the media types for the languages of the W3C\n Speech Interface Framework, as designed by the Voice Browser Working\n Group in the following specifications: the Voice Extensible Markup\n Language (VoiceXML), the Speech Synthesis Markup Language (SSML), the\n Speech Recognition Grammar Specification (SRGS), the Call Control XML\n (CCXML), and the Pronunciation Lexicon Specification (PLS).","scope_keywords":["4267","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null}],"search_text":"IETF RFC 4267 This document defines the media types for the languages of the W3C\n Speech Interface Framework, as designed by the Voice Browser Working\n Group in the following specifications: the Voice Extensible Markup\n Language (VoiceXML), the Speech Synthesis Markup Language (SSML), the\n Speech Recognition Grammar Specification (SRGS), the Call Control XML\n (CCXML), and the Pronunciation Lexicon Specification (PLS). 4267 key registered nested-reference unchanged"},{"id":"IETF RFC 4134","type":"specification","body":"IETF","designation":"RFC 4134","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4134.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4134.txt","https://www.rfc-editor.org/rfc/rfc4134.pdf"],"folder":"IETF/RFC-4134","files":{"txt":{"path":"standards/IETF/RFC-4134/RFC-4134.txt","sha256":"9d54ad3f23e8d47845beb7612435303dd059d1ab7d5052ad77b5b9316a2f5358"}},"tags":["nested-reference","unchanged"],"summary":"This document gives examples of message bodies formatted using\n S/MIME. Specifically, it has examples of Cryptographic Message\n Syntax (CMS) objects and S/MIME messages (including the MIME\n formatting). It includes examples of many common CMS formats. The\n purpose of this document is to help increase interoperability for\n S/MIME and other protocols that rely on CMS.\n\nHoffman, Ed. Informational [Page 1]\n\f\nRFC 4134 Examples of S/MIME Messages July 2005","scope_keywords":["4134","algorithm","attribute","attributes","certificate","certificates","crl","hash","key","keys","pki","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4357","folder":"IETF/RFC-4357","source":"IETF/RFC-4357/RFC-4357.txt","version":null},{"body":"IETF","designation":"RFC 4490","folder":"IETF/RFC-4490","source":"IETF/RFC-4490/RFC-4490.txt","version":null},{"body":"IETF","designation":"RFC 6210","folder":"IETF/RFC-6210","source":"IETF/RFC-6210/RFC-6210.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 4134 This document gives examples of message bodies formatted using\n S/MIME. Specifically, it has examples of Cryptographic Message\n Syntax (CMS) objects and S/MIME messages (including the MIME\n formatting). It includes examples of many common CMS formats. The\n purpose of this document is to help increase interoperability for\n S/MIME and other protocols that rely on CMS.\n\nHoffman, Ed. Informational [Page 1]\n\f\nRFC 4134 Examples of S/MIME Messages July 2005 4134 algorithm attribute attributes certificate certificates crl hash key keys pki validation nested-reference unchanged"},{"id":"IETF RFC 3215","type":"specification","body":"IETF","designation":"RFC 3215","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3215.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3215.txt","https://www.rfc-editor.org/rfc/rfc3215.pdf"],"folder":"IETF/RFC-3215","files":{"txt":{"path":"standards/IETF/RFC-3215/RFC-3215.txt","sha256":"444c6c4f11ea0e4b0d1edbc681150db6e9f378946c589fb6170bc720157ef941"}},"tags":["nested-reference","unchanged"],"summary":"This document provides state machine tables for ATM (Asynchronous\n Transfer Mode) switch LSRs. In the current LDP specification, there\n is no state machine specified for processing LDP messages. We think\n that defining a common state machine is very important for\n interoperability between different LDP and CR-LDP implementations.\n\n We begin in section 1 by defining a list of terminologies. Then in\n section 2, we propose two sets of state machine tables for ATM switch\n LSRs that use downstream-on-demand mode, one method can be used for\n non-vc merge capable ATM LSRs, while the other one can be used for\n the vc-merge capable ATM LSRs. In section 3, we provides a state\n machine for downstream unsolicited mode ATM LSRs.\n\n We focus on the LDP state machines and the associated control blocks\n used for establishing and maintaining LSPs. We do not describe state\n machines for the \"LDP controller","scope_keywords":["3215","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3212","folder":"IETF/RFC-3212","source":"IETF/RFC-3212/RFC-3212.txt","version":null},{"body":"IETF","designation":"RFC 3815","folder":"IETF/RFC-3815","source":"IETF/RFC-3815/RFC-3815.txt","version":null}],"search_text":"IETF RFC 3215 This document provides state machine tables for ATM (Asynchronous\n Transfer Mode) switch LSRs. In the current LDP specification, there\n is no state machine specified for processing LDP messages. We think\n that defining a common state machine is very important for\n interoperability between different LDP and CR-LDP implementations.\n\n We begin in section 1 by defining a list of terminologies. Then in\n section 2, we propose two sets of state machine tables for ATM switch\n LSRs that use downstream-on-demand mode, one method can be used for\n non-vc merge capable ATM LSRs, while the other one can be used for\n the vc-merge capable ATM LSRs. In section 3, we provides a state\n machine for downstream unsolicited mode ATM LSRs.\n\n We focus on the LDP state machines and the associated control blocks\n used for establishing and maintaining LSPs. We do not describe state\n machines for the \"LDP controller 3215 management nested-reference unchanged"},{"id":"IETF RFC 3429","type":"specification","body":"IETF","designation":"RFC 3429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3429.txt","https://www.rfc-editor.org/rfc/rfc3429.pdf"],"folder":"IETF/RFC-3429","files":{"txt":{"path":"standards/IETF/RFC-3429/RFC-3429.txt","sha256":"5a92d08a0c83761c4b51f2f46eec8b38b10b4f8ca76c0fc02066e00b0befe04e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the assignment of one of the reserved label\n values defined in RFC 3032 (MPLS label stack encoding) to the\n 'Operation and Maintenance (OAM) Alert Label' that is used by user-\n plane Multiprotocol Label Switching Architecture (MPLS) OAM functions\n for identification of MPLS OAM packets.\n\n1. Introduction\n\n This document describes the assignment of one of the reserved label\n values defined in RFC 3032 (MPLS label stack encoding [2]) to the\n 'OAM Alert Label' that is used by user-plane MPLS OAM functions for\n identification of MPLS OAM packets as described in the ITU-T\n Recommendation Y.1711 [1] (on MPLS OAM functions).\n\n2. OAM functions\n\n MPLS OAM (Operation and Maintenance) functions provide necessary\n tools for network operators to operate and maintain the networks.\n MPLS OAM functionality is required at the MPLS layer, and more\n specifically at each MPLS level, i","scope_keywords":["3429","identification","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 5586","folder":"IETF/RFC-5586","source":"IETF/RFC-5586/RFC-5586.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 3429 This document describes the assignment of one of the reserved label\n values defined in RFC 3032 (MPLS label stack encoding) to the\n 'Operation and Maintenance (OAM) Alert Label' that is used by user-\n plane Multiprotocol Label Switching Architecture (MPLS) OAM functions\n for identification of MPLS OAM packets.\n\n1. Introduction\n\n This document describes the assignment of one of the reserved label\n values defined in RFC 3032 (MPLS label stack encoding [2]) to the\n 'OAM Alert Label' that is used by user-plane MPLS OAM functions for\n identification of MPLS OAM packets as described in the ITU-T\n Recommendation Y.1711 [1] (on MPLS OAM functions).\n\n2. OAM functions\n\n MPLS OAM (Operation and Maintenance) functions provide necessary\n tools for network operators to operate and maintain the networks.\n MPLS OAM functionality is required at the MPLS layer, and more\n specifically at each MPLS level, i 3429 identification management nested-reference unchanged"},{"id":"IETF RFC 3793","type":"specification","body":"IETF","designation":"RFC 3793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3793.txt","https://www.rfc-editor.org/rfc/rfc3793.pdf"],"folder":"IETF/RFC-3793","files":{"txt":{"path":"standards/IETF/RFC-3793/RFC-3793.txt","sha256":"9bf05c757096e759ee5e24fe76859f83a70f05125d5957ea553fcec92a1cba2d"}},"tags":["nested-reference","unchanged"],"summary":"This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Sub-IP Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented.","scope_keywords":["3793","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null}],"search_text":"IETF RFC 3793 This document seeks to document all usage of IPv4 addresses in\n currently deployed IETF Sub-IP Area documented standards. In order\n to successfully transition from an all IPv4 Internet to an all IPv6\n Internet, many interim steps will be taken. One of these steps is\n the evolution of current protocols that have IPv4 dependencies. It\n is hoped that these protocols (and their implementations) will be\n redesigned to be network address independent, but failing that will\n at least dually support IPv4 and IPv6. To this end, all Standards\n (Full, Draft, and Proposed) as well as Experimental RFCs will be\n surveyed and any dependencies will be documented. 3793 management nested-reference unchanged"},{"id":"IETF RFC 4726","type":"specification","body":"IETF","designation":"RFC 4726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4726.txt","https://www.rfc-editor.org/rfc/rfc4726.pdf"],"folder":"IETF/RFC-4726","files":{"txt":{"path":"standards/IETF/RFC-4726/RFC-4726.txt","sha256":"8e6f25babd168a1a104669b5e4afa8861efafbe09885b7aa43c3fcde03ca1737"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for establishing and controlling\n Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n Traffic Engineered (TE) Label Switched Paths (LSPs) in multi-domain\n networks.\n\n For the purposes of this document, a domain is considered to be any\n collection of network elements within a common sphere of address\n management or path computational responsibility. Examples of such\n domains include Interior Gateway Protocol (IGP) areas and Autonomous\n Systems (ASes).\n\nFarrel, et al. Informational [Page 1]\n\f\nRFC 4726 Framework for Inter-Domain TE November 2006","scope_keywords":["4726","management","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5150","folder":"IETF/RFC-5150","source":"IETF/RFC-5150/RFC-5150.txt","version":null},{"body":"IETF","designation":"RFC 5151","folder":"IETF/RFC-5151","source":"IETF/RFC-5151/RFC-5151.txt","version":null},{"body":"IETF","designation":"RFC 5152","folder":"IETF/RFC-5152","source":"IETF/RFC-5152/RFC-5152.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null}],"search_text":"IETF RFC 4726 This document provides a framework for establishing and controlling\n Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n Traffic Engineered (TE) Label Switched Paths (LSPs) in multi-domain\n networks.\n\n For the purposes of this document, a domain is considered to be any\n collection of network elements within a common sphere of address\n management or path computational responsibility. Examples of such\n domains include Interior Gateway Protocol (IGP) areas and Autonomous\n Systems (ASes).\n\nFarrel, et al. Informational [Page 1]\n\f\nRFC 4726 Framework for Inter-Domain TE November 2006 4726 management path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 4928","type":"specification","body":"IETF","designation":"RFC 4928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4928.txt","https://www.rfc-editor.org/rfc/rfc4928.pdf"],"folder":"IETF/RFC-4928","files":{"txt":{"path":"standards/IETF/RFC-4928/RFC-4928.txt","sha256":"cfaea50eaf916a8fc2b0e3085190f9c7c539ab520397daa8d62042e52575a1b5"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the Equal Cost Multipath (ECMP) behavior of\n currently deployed MPLS networks. This document makes best practice\n recommendations for anyone defining an application to run over an\n MPLS network that wishes to avoid the reordering that can result from\n transmission of different packets from the same flow over multiple\n different equal cost paths. These recommendations rely on inspection\n of the IP version number field in packets. Despite the heuristic\n nature of the recommendations, they provide a relatively safe way to\n operate MPLS networks, even if future allocations of IP version\n numbers were made for some purpose.","scope_keywords":["4928","algorithm","hash","hashing","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5143","folder":"IETF/RFC-5143","source":"IETF/RFC-5143/RFC-5143.txt","version":null},{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6391","folder":"IETF/RFC-6391","source":"IETF/RFC-6391/RFC-6391.txt","version":null},{"body":"IETF","designation":"RFC 6576","folder":"IETF/RFC-6576","source":"IETF/RFC-6576/RFC-6576.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4928 This document describes the Equal Cost Multipath (ECMP) behavior of\n currently deployed MPLS networks. This document makes best practice\n recommendations for anyone defining an application to run over an\n MPLS network that wishes to avoid the reordering that can result from\n transmission of different packets from the same flow over multiple\n different equal cost paths. These recommendations rely on inspection\n of the IP version number field in packets. Despite the heuristic\n nature of the recommendations, they provide a relatively safe way to\n operate MPLS networks, even if future allocations of IP version\n numbers were made for some purpose. 4928 algorithm hash hashing path subject trust nested-reference unchanged"},{"id":"IETF RFC 5253","type":"specification","body":"IETF","designation":"RFC 5253","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5253.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5253.txt","https://www.rfc-editor.org/rfc/rfc5253.pdf"],"folder":"IETF/RFC-5253","files":{"txt":{"path":"standards/IETF/RFC-5253/RFC-5253.txt","sha256":"e3f36d22eb6743f1dde128ca8bbd00b37725f3f83e5fe93f01d599cecbb6e18f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an applicability statement on the use of\n Generalized Multiprotocol Label Switching (GMPLS) protocols and\n mechanisms to support Basic Mode Layer 1 Virtual Private Networks\n (L1VPNs).\n\n L1VPNs provide customer services and connectivity at Layer 1 over\n Layer 1 networks. The operation of L1VPNs is divided into the Basic\n Mode and the Enhanced Mode, where the Basic Mode of operation does\n not feature any exchange of routing information between the Layer 1\n network and the customer domain. This document examines how GMPLS\n protocols can be used to satisfy the requirements of a Basic Mode\n L1VPN.\n\nTakeda Informational [Page 1]\n\f\nRFC 5253 AS for L1VPN Basic Mode July 2008","scope_keywords":["5253","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5251","folder":"IETF/RFC-5251","source":"IETF/RFC-5251/RFC-5251.txt","version":null}],"search_text":"IETF RFC 5253 This document provides an applicability statement on the use of\n Generalized Multiprotocol Label Switching (GMPLS) protocols and\n mechanisms to support Basic Mode Layer 1 Virtual Private Networks\n (L1VPNs).\n\n L1VPNs provide customer services and connectivity at Layer 1 over\n Layer 1 networks. The operation of L1VPNs is divided into the Basic\n Mode and the Enhanced Mode, where the Basic Mode of operation does\n not feature any exchange of routing information between the Layer 1\n network and the customer domain. This document examines how GMPLS\n protocols can be used to satisfy the requirements of a Basic Mode\n L1VPN.\n\nTakeda Informational [Page 1]\n\f\nRFC 5253 AS for L1VPN Basic Mode July 2008 5253 management path nested-reference unchanged"},{"id":"IETF RFC 5659","type":"specification","body":"IETF","designation":"RFC 5659","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5659.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5659.txt","https://www.rfc-editor.org/rfc/rfc5659.pdf"],"folder":"IETF/RFC-5659","files":{"txt":{"path":"standards/IETF/RFC-5659/RFC-5659.txt","sha256":"606ec3c956bbae1f732396f16bf6f53c50ef2a1d170d2331e1693b5d2e06b1dc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architecture for extending pseudowire\n emulation across multiple packet switched network (PSN) segments.\n Scenarios are discussed where each segment of a given edge-to-edge\n emulated service spans a different provider's PSN, as are other\n scenarios where the emulated service originates and terminates on the\n same provider's PSN, but may pass through several PSN tunnel segments\n in that PSN. It presents an architectural framework for such multi-\n segment pseudowires, defines terminology, and specifies the various\n protocol elements and their functions.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n","scope_keywords":["5659","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6040","folder":"IETF/RFC-6040","source":"IETF/RFC-6040/RFC-6040.txt","version":null},{"body":"IETF","designation":"RFC 6073","folder":"IETF/RFC-6073","source":"IETF/RFC-6073/RFC-6073.txt","version":null},{"body":"IETF","designation":"RFC 6074","folder":"IETF/RFC-6074","source":"IETF/RFC-6074/RFC-6074.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null}],"search_text":"IETF RFC 5659 This document describes an architecture for extending pseudowire\n emulation across multiple packet switched network (PSN) segments.\n Scenarios are discussed where each segment of a given edge-to-edge\n emulated service spans a different provider's PSN, as are other\n scenarios where the emulated service originates and terminates on the\n same provider's PSN, but may pass through several PSN tunnel segments\n in that PSN. It presents an architectural framework for such multi-\n segment pseudowires, defines terminology, and specifies the various\n protocol elements and their functions.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n 5659 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5693","type":"specification","body":"IETF","designation":"RFC 5693","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5693.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5693.txt","https://www.rfc-editor.org/rfc/rfc5693.pdf"],"folder":"IETF/RFC-5693","files":{"txt":{"path":"standards/IETF/RFC-5693/RFC-5693.txt","sha256":"18dac34dffb4c4a82efef72fbebf5c384fd3a45d583e7deb55c740e5cd0c65c4"}},"tags":["nested-reference","unchanged"],"summary":"Distributed applications -- such as file sharing, real-time\n communication, and live and on-demand media streaming -- prevalent on\n the Internet use a significant amount of network resources. Such\n applications often transfer large amounts of data through connections\n established between nodes distributed across the Internet with little\n knowledge of the underlying network topology. Some applications are\n so designed that they choose a random subset of peers from a larger\n set with which to exchange data. Absent any topology information\n guiding such choices, or acting on suboptimal or local information\n obtained from measurements and statistics, these applications often\n make less than desirable choices.\n\n This document discusses issues related to an information-sharing\n service that enables applications to perform better-than-random peer\n selection.\n\nStatus of This Memo\n\n This memo pro","scope_keywords":["5693","algorithm","hash","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6708","folder":"IETF/RFC-6708","source":"IETF/RFC-6708/RFC-6708.txt","version":null},{"body":"IETF","designation":"RFC 7285","folder":"IETF/RFC-7285","source":"IETF/RFC-7285/RFC-7285.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"IETF RFC 5693 Distributed applications -- such as file sharing, real-time\n communication, and live and on-demand media streaming -- prevalent on\n the Internet use a significant amount of network resources. Such\n applications often transfer large amounts of data through connections\n established between nodes distributed across the Internet with little\n knowledge of the underlying network topology. Some applications are\n so designed that they choose a random subset of peers from a larger\n set with which to exchange data. Absent any topology information\n guiding such choices, or acting on suboptimal or local information\n obtained from measurements and statistics, these applications often\n make less than desirable choices.\n\n This document discusses issues related to an information-sharing\n service that enables applications to perform better-than-random peer\n selection.\n\nStatus of This Memo\n\n This memo pro 5693 algorithm hash http license subject trust nested-reference unchanged"},{"id":"IETF RFC 5921","type":"specification","body":"IETF","designation":"RFC 5921","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5921.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5921.txt","https://www.rfc-editor.org/rfc/rfc5921.pdf"],"folder":"IETF/RFC-5921","files":{"txt":{"path":"standards/IETF/RFC-5921/RFC-5921.txt","sha256":"a23d34fe756dc2aa47c6904baa0063bee7cffd874cceb293aba26b723462d102"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies an architectural framework for the\n application of Multiprotocol Label Switching (MPLS) to the\n construction of packet-switched transport networks. It describes a\n common set of protocol functions -- the MPLS Transport Profile (MPLS-\n TP) -- that supports the operational models and capabilities typical\n of such networks, including signaled or explicitly provisioned\n bidirectional connection-oriented paths, protection and restoration\n mechanisms, comprehensive Operations, Administration, and Maintenance\n (OAM) functions, and network operation in the absence of a dynamic\n control plane or IP forwarding support. Some of these functions are\n defined in existing MPLS specifications, while others require\n extensions to existing specifications to meet the requirements of the\n MPLS-TP.\n\n This document defines the subset of the MPLS-TP applicable in general\n and to point-t","scope_keywords":["5921","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null},{"body":"IETF","designation":"RFC 6215","folder":"IETF/RFC-6215","source":"IETF/RFC-6215/RFC-6215.txt","version":null},{"body":"IETF","designation":"RFC 6370","folder":"IETF/RFC-6370","source":"IETF/RFC-6370/RFC-6370.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 6511","folder":"IETF/RFC-6511","source":"IETF/RFC-6511/RFC-6511.txt","version":null},{"body":"IETF","designation":"RFC 6941","folder":"IETF/RFC-6941","source":"IETF/RFC-6941/RFC-6941.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"IETF RFC 5921 This document specifies an architectural framework for the\n application of Multiprotocol Label Switching (MPLS) to the\n construction of packet-switched transport networks. It describes a\n common set of protocol functions -- the MPLS Transport Profile (MPLS-\n TP) -- that supports the operational models and capabilities typical\n of such networks, including signaled or explicitly provisioned\n bidirectional connection-oriented paths, protection and restoration\n mechanisms, comprehensive Operations, Administration, and Maintenance\n (OAM) functions, and network operation in the absence of a dynamic\n control plane or IP forwarding support. Some of these functions are\n defined in existing MPLS specifications, while others require\n extensions to existing specifications to meet the requirements of the\n MPLS-TP.\n\n This document defines the subset of the MPLS-TP applicable in general\n and to point-t 5921 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 3038","type":"specification","body":"IETF","designation":"RFC 3038","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3038.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3038.txt","https://www.rfc-editor.org/rfc/rfc3038.pdf"],"folder":"IETF/RFC-3038","files":{"txt":{"path":"standards/IETF/RFC-3038/RFC-3038.txt","sha256":"fbd578c42e9aa5c687128d187091f60825fa7a021000a97793e11c4130d48f37"}},"tags":["nested-reference","unchanged"],"summary":"The Asynchronous Transfer Mode Label Switching Router (ATM-LSR) is\n one of the major applications of label switching. Because the ATM\n layer labels (VPI and VCI) associated with a VC rewritten with new\n value at every ATM switch nodes, it is not possible to use them to\n identify a VC in label mapping messages. The concept of Virtual\n Connection Identifier (VCID) is introduced to solve this problem.\n VCID has the same value at both ends of a VC. This document\n specifies the procedures for the communication of VCID values between\n neighboring ATM-LSRs that must occur in order to ensure this\n property.\n\n1. Introduction\n\n Several label switching schemes have been proposed to integrate Layer\n 2 and Layer 3. The ATM Label Switching Router (ATM-LSR) is one of\n the major applications of label switching.\n\n In the case of ATM VCs, the VPI and VCI labels are, in the general\n case, rewritten with ne","scope_keywords":["3038","identification","management","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3035","folder":"IETF/RFC-3035","source":"IETF/RFC-3035/RFC-3035.txt","version":null},{"body":"IETF","designation":"RFC 3353","folder":"IETF/RFC-3353","source":"IETF/RFC-3353/RFC-3353.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null}],"search_text":"IETF RFC 3038 The Asynchronous Transfer Mode Label Switching Router (ATM-LSR) is\n one of the major applications of label switching. Because the ATM\n layer labels (VPI and VCI) associated with a VC rewritten with new\n value at every ATM switch nodes, it is not possible to use them to\n identify a VC in label mapping messages. The concept of Virtual\n Connection Identifier (VCID) is introduced to solve this problem.\n VCID has the same value at both ends of a VC. This document\n specifies the procedures for the communication of VCID values between\n neighboring ATM-LSRs that must occur in order to ensure this\n property.\n\n1. Introduction\n\n Several label switching schemes have been proposed to integrate Layer\n 2 and Layer 3. The ATM Label Switching Router (ATM-LSR) is one of\n the major applications of label switching.\n\n In the case of ATM VCs, the VPI and VCI labels are, in the general\n case, rewritten with ne 3038 identification management path pid nested-reference unchanged"},{"id":"IETF RFC 4182","type":"specification","body":"IETF","designation":"RFC 4182","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4182.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4182.txt","https://www.rfc-editor.org/rfc/rfc4182.pdf"],"folder":"IETF/RFC-4182","files":{"txt":{"path":"standards/IETF/RFC-4182/RFC-4182.txt","sha256":"d9f3f55b2d1683a5e2a107c482ca86b8d96e4703f0ba21067e799bf58189f360"}},"tags":["nested-reference","unchanged"],"summary":"The label stack encoding for Multi-protocol Label Switching (MPLS)\n defines a reserved label value known as \"IPv4 Explicit NULL\" and a\n reserved label value known as \"IPv6 Explicit NULL\". Previously,\n these labels were only legal when they occurred at the bottom of the\n MPLS label stack. This restriction is now removed, so that these\n label values may legally occur anywhere in the stack.\n\n This document updates RFC 3032.","scope_keywords":["4182"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4798","folder":"IETF/RFC-4798","source":"IETF/RFC-4798/RFC-4798.txt","version":null},{"body":"IETF","designation":"RFC 5462","folder":"IETF/RFC-5462","source":"IETF/RFC-5462/RFC-5462.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4182 The label stack encoding for Multi-protocol Label Switching (MPLS)\n defines a reserved label value known as \"IPv4 Explicit NULL\" and a\n reserved label value known as \"IPv6 Explicit NULL\". Previously,\n these labels were only legal when they occurred at the bottom of the\n MPLS label stack. This restriction is now removed, so that these\n label values may legally occur anywhere in the stack.\n\n This document updates RFC 3032. 4182 nested-reference unchanged"},{"id":"IETF RFC 5220","type":"specification","body":"IETF","designation":"RFC 5220","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5220.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5220.txt","https://www.rfc-editor.org/rfc/rfc5220.pdf"],"folder":"IETF/RFC-5220","files":{"txt":{"path":"standards/IETF/RFC-5220/RFC-5220.txt","sha256":"4b5c0fe5ad2e4f64ee72e670b2d1027e39a0abe450899f4d19b10f0ef64cc170"}},"tags":["nested-reference","unchanged"],"summary":"A single physical link can have multiple prefixes assigned to it. In\n that environment, end hosts might have multiple IP addresses and be\n required to use them selectively. RFC 3484 defines default source\n and destination address selection rules and is implemented in a\n variety of OSs. But, it has been too difficult to use operationally\n for several reasons. In some environments where multiple prefixes\n are assigned on a single physical link, the host using the default\n address selection rules will experience some trouble in\n communication. This document describes the possible problems that\n end hosts could encounter in an environment with multiple prefixes.\n\nMatsumoto, et al. Informational [Page 1]\n\f\nRFC 5220 Address Selection PS July 2008","scope_keywords":["5220","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5221","folder":"IETF/RFC-5221","source":"IETF/RFC-5221/RFC-5221.txt","version":null},{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 6724","folder":"IETF/RFC-6724","source":"IETF/RFC-6724/RFC-6724.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null},{"body":"IETF","designation":"RFC 7157","folder":"IETF/RFC-7157","source":"IETF/RFC-7157/RFC-7157.txt","version":null}],"search_text":"IETF RFC 5220 A single physical link can have multiple prefixes assigned to it. In\n that environment, end hosts might have multiple IP addresses and be\n required to use them selectively. RFC 3484 defines default source\n and destination address selection rules and is implemented in a\n variety of OSs. But, it has been too difficult to use operationally\n for several reasons. In some environments where multiple prefixes\n are assigned on a single physical link, the host using the default\n address selection rules will experience some trouble in\n communication. This document describes the possible problems that\n end hosts could encounter in an environment with multiple prefixes.\n\nMatsumoto, et al. Informational [Page 1]\n\f\nRFC 5220 Address Selection PS July 2008 5220 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 3487","type":"specification","body":"IETF","designation":"RFC 3487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3487.txt","https://www.rfc-editor.org/rfc/rfc3487.pdf"],"folder":"IETF/RFC-3487","files":{"txt":{"path":"standards/IETF/RFC-3487/RFC-3487.txt","sha256":"3861836092b2083d2ba683f8a0484dd71affc20cedfb29a3ee8767140970e828"}},"tags":["nested-reference","unchanged"],"summary":"This document summarizes requirements for prioritizing access to\n circuit-switched network, end system and proxy resources for\n emergency preparedness communications using the Session Initiation\n Protocol (SIP).","scope_keywords":["3487","algorithm","algorithms","authentication","authorization","policies","policy","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 3690","folder":"IETF/RFC-3690","source":"IETF/RFC-3690/RFC-3690.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null}],"search_text":"IETF RFC 3487 This document summarizes requirements for prioritizing access to\n circuit-switched network, end system and proxy resources for\n emergency preparedness communications using the Session Initiation\n Protocol (SIP). 3487 algorithm algorithms authentication authorization policies policy subject nested-reference unchanged"},{"id":"IETF RFC 3055","type":"specification","body":"IETF","designation":"RFC 3055","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3055.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3055.txt","https://www.rfc-editor.org/rfc/rfc3055.pdf"],"folder":"IETF/RFC-3055","files":{"txt":{"path":"standards/IETF/RFC-3055/RFC-3055.txt","sha256":"0379a68cff46eb6d9cd3fb96e10763f7e5a9701ef2f89df462c392f0dc8a9326"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a proposed Management Information Base (MIB) for\n the PSTN/Internet Interworking (PINT) Services Architecture.","scope_keywords":["3055","authentication","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 3055 This memo describes a proposed Management Information Base (MIB) for\n the PSTN/Internet Interworking (PINT) Services Architecture. 3055 authentication management nested-reference unchanged"},{"id":"IETF RFC 6177","type":"specification","body":"IETF","designation":"RFC 6177","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6177.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6177.txt","https://www.rfc-editor.org/rfc/rfc6177.pdf"],"folder":"IETF/RFC-6177","files":{"txt":{"path":"standards/IETF/RFC-6177/RFC-6177.txt","sha256":"6964b32276721dfa8b52ac6091e21dd38ce3601856be5fb4a0fa4d5f0305f4ca"}},"tags":["nested-reference","unchanged"],"summary":"RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks\n in most cases. The Regional Internet Registries (RIRs) adopted that\n recommendation in 2002, but began reconsidering the policy in 2005.\n This document obsoletes the RFC 3177 recommendations on the\n assignment of IPv6 address space to end sites. The exact choice of\n how much address space to assign end sites is an issue for the\n operational community. The IETF's role in this case is limited to\n providing guidance on IPv6 architectural and operational\n considerations. This document reviews the architectural and\n operational considerations of end site assignments as well as the\n motivations behind the original recommendations in RFC 3177.\n Moreover, this document clarifies that a one-size-fits-all\n recommendation of /48 is not nuanced enough for the broad range of\n end sites and is no longer recommended as a single defa","scope_keywords":["6177","http","key","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6748","folder":"IETF/RFC-6748","source":"IETF/RFC-6748/RFC-6748.txt","version":null},{"body":"IETF","designation":"RFC 7084","folder":"IETF/RFC-7084","source":"IETF/RFC-7084/RFC-7084.txt","version":null},{"body":"IETF","designation":"RFC 7368","folder":"IETF/RFC-7368","source":"IETF/RFC-7368/RFC-7368.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7871","folder":"IETF/RFC-7871","source":"IETF/RFC-7871/RFC-7871.txt","version":null}],"search_text":"IETF RFC 6177 RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks\n in most cases. The Regional Internet Registries (RIRs) adopted that\n recommendation in 2002, but began reconsidering the policy in 2005.\n This document obsoletes the RFC 3177 recommendations on the\n assignment of IPv6 address space to end sites. The exact choice of\n how much address space to assign end sites is an issue for the\n operational community. The IETF's role in this case is limited to\n providing guidance on IPv6 architectural and operational\n considerations. This document reviews the architectural and\n operational considerations of end site assignments as well as the\n motivations behind the original recommendations in RFC 3177.\n Moreover, this document clarifies that a one-size-fits-all\n recommendation of /48 is not nuanced enough for the broad range of\n end sites and is no longer recommended as a single defa 6177 http key license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 3057","type":"specification","body":"IETF","designation":"RFC 3057","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3057.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3057.txt","https://www.rfc-editor.org/rfc/rfc3057.pdf"],"folder":"IETF/RFC-3057","files":{"txt":{"path":"standards/IETF/RFC-3057/RFC-3057.txt","sha256":"caa0d60017ff1ffa4465183903c3dee1097207c04e96885a4f36ce675d194f25"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a protocol for backhauling of ISDN Q.921 User\n messages over IP using the Stream Control Transmission Protocol\n (SCTP). This protocol would be used between a Signaling Gateway (SG)\n and Media Gateway Controller (MGC). It is assumed that the SG\n receives ISDN signaling over a standard ISDN interface.\n\nMorneault, et al. Standards Track [Page 1]\n\f\nRFC 3057 ISDN Q.921-User Adaptation Layer February 2001","scope_keywords":["3057","delivery","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 3057 This document defines a protocol for backhauling of ISDN Q.921 User\n messages over IP using the Stream Control Transmission Protocol\n (SCTP). This protocol would be used between a Signaling Gateway (SG)\n and Media Gateway Controller (MGC). It is assumed that the SG\n receives ISDN signaling over a standard ISDN interface.\n\nMorneault, et al. Standards Track [Page 1]\n\f\nRFC 3057 ISDN Q.921-User Adaptation Layer February 2001 3057 delivery management policy nested-reference unchanged"},{"id":"IETF RFC 306","type":"specification","body":"IETF","designation":"RFC 306","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc306.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc306.txt","https://www.rfc-editor.org/rfc/rfc306.pdf"],"folder":"IETF/RFC-306","files":{"txt":{"path":"standards/IETF/RFC-306/RFC-306.txt","sha256":"449075ff043e6279fef7b5184c6ceb68149ab601bd70e67e73cff8ebb2bed17b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Westheimer\nRequest for Comments: 306 BBN\nNIC: 9257 February 15, 1972\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January 31\n to February 11.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular\n basis for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10 (B)\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are presently in the Network\n (AMES, MITRE, NBS and BBN*). This category also includes the\n Network Control Center computer (Network Address 5) which is\n used solely for gathering statistics from","scope_keywords":["306"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 306 Network Working Group E. Westheimer\nRequest for Comments: 306 BBN\nNIC: 9257 February 15, 1972\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from January 31\n to February 11.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular\n basis for at least two weeks. Included here are:\n\n NETWORK SITE COMPUTER\n ADDRESS\n\n 133 BBN PDP-10 (B)\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMPs, which are presently in the Network\n (AMES, MITRE, NBS and BBN*). This category also includes the\n Network Control Center computer (Network Address 5) which is\n used solely for gathering statistics from 306 nested-reference unchanged"},{"id":"IETF RFC 3063","type":"specification","body":"IETF","designation":"RFC 3063","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3063.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3063.txt","https://www.rfc-editor.org/rfc/rfc3063.pdf"],"folder":"IETF/RFC-3063","files":{"txt":{"path":"standards/IETF/RFC-3063/RFC-3063.txt","sha256":"3ce983b8ebcfef08c17b97489c55ce133584195d0288eb5e1ca4c42a0225bc60"}},"tags":["nested-reference","unchanged"],"summary":"This paper presents a simple mechanism, based on \"threads\", which can\n be used to prevent Multiprotocol Label Switching (MPLS) from setting\n up label switched path (LSPs) which have loops. The mechanism is\n compatible with, but does not require, VC merge. The mechanism can\n be used with either the ordered downstream-on-demand allocation or\n ordered downstream allocation. The amount of information that must\n be passed in a protocol message is tightly bounded (i.e., no path-\n vector is used). When a node needs to change its next hop, a\n distributed procedure is executed, but only nodes which are\n downstream of the change are involved.\n\nOhba, et al. Experimental [Page 1]\n\f\nRFC 3063 MPLS Loop Prevention Mechanism February 2001","scope_keywords":["3063","algorithm","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null}],"search_text":"IETF RFC 3063 This paper presents a simple mechanism, based on \"threads\", which can\n be used to prevent Multiprotocol Label Switching (MPLS) from setting\n up label switched path (LSPs) which have loops. The mechanism is\n compatible with, but does not require, VC merge. The mechanism can\n be used with either the ordered downstream-on-demand allocation or\n ordered downstream allocation. The amount of information that must\n be passed in a protocol message is tightly bounded (i.e., no path-\n vector is used). When a node needs to change its next hop, a\n distributed procedure is executed, but only nodes which are\n downstream of the change are involved.\n\nOhba, et al. Experimental [Page 1]\n\f\nRFC 3063 MPLS Loop Prevention Mechanism February 2001 3063 algorithm attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 530","type":"specification","body":"IETF","designation":"RFC 530","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc530.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc530.txt","https://www.rfc-editor.org/rfc/rfc530.pdf"],"folder":"IETF/RFC-530","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 530 nested-reference unavailable"},{"id":"IETF RFC 4219","type":"specification","body":"IETF","designation":"RFC 4219","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4219.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4219.txt","https://www.rfc-editor.org/rfc/rfc4219.pdf"],"folder":"IETF/RFC-4219","files":{"txt":{"path":"standards/IETF/RFC-4219/RFC-4219.txt","sha256":"8f792be283e0fa4ac1120a316a7c903d4cdb6844d61117068b0626df1c000a38"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a set of questions that authors should be\n prepared to answer as part of a solution to multihoming with IPv6.\n The questions do not assume that multihoming is the only problem of\n interest, nor do they demand a more general solution.","scope_keywords":["4219","authentication","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5375","folder":"IETF/RFC-5375","source":"IETF/RFC-5375/RFC-5375.txt","version":null}],"search_text":"IETF RFC 4219 This document specifies a set of questions that authors should be\n prepared to answer as part of a solution to multihoming with IPv6.\n The questions do not assume that multihoming is the only problem of\n interest, nor do they demand a more general solution. 4219 authentication authorization nested-reference unchanged"},{"id":"IETF RFC 3243","type":"specification","body":"IETF","designation":"RFC 3243","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3243.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3243.txt","https://www.rfc-editor.org/rfc/rfc3243.pdf"],"folder":"IETF/RFC-3243","files":{"txt":{"path":"standards/IETF/RFC-3243/RFC-3243.txt","sha256":"cf247edb26d185c7f21f4fff89354ce952ae957ff90c89ada91018d234e181ca"}},"tags":["nested-reference","unchanged"],"summary":"This document contains requirements for the 0-byte IP/UDP/RTP\n (Internet Protocol/User Datagram Protocol/Real-Time Transport\n Protocol) header compression scheme to be developed by the Robust\n Header Compression (ROHC) Working Group. It also includes the basic\n assumptions for the typical link layers over which 0-byte compression\n may be implemented, and assumptions about its usage in general.\n\n1. Introduction\n\n The goal of the Robust Header Compression (ROHC) Working Group is to\n develop header compression schemes that perform well over links with\n high error rates and long link roundtrip times. The schemes must\n perform well for cellular links, using technologies such as WCDMA,\n EDGE, and CDMA-2000. However, the schemes should also be applicable\n to other future link technologies with high loss and long roundtrip\n times.\n\n ROHC RTP has become a very efficient, robust and capable compre","scope_keywords":["3243"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null}],"search_text":"IETF RFC 3243 This document contains requirements for the 0-byte IP/UDP/RTP\n (Internet Protocol/User Datagram Protocol/Real-Time Transport\n Protocol) header compression scheme to be developed by the Robust\n Header Compression (ROHC) Working Group. It also includes the basic\n assumptions for the typical link layers over which 0-byte compression\n may be implemented, and assumptions about its usage in general.\n\n1. Introduction\n\n The goal of the Robust Header Compression (ROHC) Working Group is to\n develop header compression schemes that perform well over links with\n high error rates and long link roundtrip times. The schemes must\n perform well for cellular links, using technologies such as WCDMA,\n EDGE, and CDMA-2000. However, the schemes should also be applicable\n to other future link technologies with high loss and long roundtrip\n times.\n\n ROHC RTP has become a very efficient, robust and capable compre 3243 nested-reference unchanged"},{"id":"IETF RFC 3759","type":"specification","body":"IETF","designation":"RFC 3759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3759.txt","https://www.rfc-editor.org/rfc/rfc3759.pdf"],"folder":"IETF/RFC-3759","files":{"txt":{"path":"standards/IETF/RFC-3759/RFC-3759.txt","sha256":"245b59a0a06a30552e52e944b445bc1c7bd95b46e6c0004f4f1844db241b4c36"}},"tags":["nested-reference","unchanged"],"summary":"This document aims to clarify terms and concepts presented in RFC\n 3095. RFC 3095 defines a Proposed Standard framework with profiles\n for RObust Header Compression (ROHC). The standard introduces\n various concepts which might be difficult to understand and\n especially to relate correctly to the surrounding environments where\n header compression may be used. This document aims at clarifying\n these aspects of ROHC, discussing terms such as ROHC instances, ROHC\n channels, ROHC feedback, and ROHC contexts, and how these terms\n relate to other terms, like network elements and IP interfaces,\n commonly used, for example, when addressing MIB issues.\n\nJonsson Informational [Page 1]\n\f\nRFC 3759 ROHC Terminology and Channel Mapping Examples April 2004","scope_keywords":["3759","path","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4224","folder":"IETF/RFC-4224","source":"IETF/RFC-4224/RFC-4224.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 5858","folder":"IETF/RFC-5858","source":"IETF/RFC-5858/RFC-5858.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 3759 This document aims to clarify terms and concepts presented in RFC\n 3095. RFC 3095 defines a Proposed Standard framework with profiles\n for RObust Header Compression (ROHC). The standard introduces\n various concepts which might be difficult to understand and\n especially to relate correctly to the surrounding environments where\n header compression may be used. This document aims at clarifying\n these aspects of ROHC, discussing terms such as ROHC instances, ROHC\n channels, ROHC feedback, and ROHC contexts, and how these terms\n relate to other terms, like network elements and IP interfaces,\n commonly used, for example, when addressing MIB issues.\n\nJonsson Informational [Page 1]\n\f\nRFC 3759 ROHC Terminology and Channel Mapping Examples April 2004 3759 path profile profiles nested-reference unchanged"},{"id":"IETF RFC 4224","type":"specification","body":"IETF","designation":"RFC 4224","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4224.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4224.txt","https://www.rfc-editor.org/rfc/rfc4224.pdf"],"folder":"IETF/RFC-4224","files":{"txt":{"path":"standards/IETF/RFC-4224/RFC-4224.txt","sha256":"ec9664a55022cd9de144d3500884a3ce9c448ce6a7ce916806857e651f4d3377"}},"tags":["nested-reference","unchanged"],"summary":"RObust Header Compression (ROHC), RFC 3095, defines a framework for\n header compression, along with a number of compression protocols\n (profiles). One operating assumption for the profiles defined in RFC\n 3095 is that the channel between compressor and decompressor is\n required to maintain packet ordering. This document discusses\n aspects of using ROHC over channels that can reorder packets. It\n provides guidelines on how to implement existing profiles over such\n channels, as well as suggestions for the design of new profiles.\n\nPelletier, et al. Informational [Page 1]\n\f\nRFC 4224 ROHC over Reordering Channels January 2006","scope_keywords":["4224","delivery","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5856","folder":"IETF/RFC-5856","source":"IETF/RFC-5856/RFC-5856.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null}],"search_text":"IETF RFC 4224 RObust Header Compression (ROHC), RFC 3095, defines a framework for\n header compression, along with a number of compression protocols\n (profiles). One operating assumption for the profiles defined in RFC\n 3095 is that the channel between compressor and decompressor is\n required to maintain packet ordering. This document discusses\n aspects of using ROHC over channels that can reorder packets. It\n provides guidelines on how to implement existing profiles over such\n channels, as well as suggestions for the design of new profiles.\n\nPelletier, et al. Informational [Page 1]\n\f\nRFC 4224 ROHC over Reordering Channels January 2006 4224 delivery profile profiles nested-reference unchanged"},{"id":"IETF RFC 3100","type":"specification","body":"IETF","designation":"RFC 3100","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc3100.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3100.txt","https://www.rfc-editor.org/rfc/rfc3100.pdf"],"folder":"IETF/RFC-3100","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3791","folder":"IETF/RFC-3791","source":"IETF/RFC-3791/RFC-3791.txt","version":null},{"body":"IETF","designation":"RFC 3792","folder":"IETF/RFC-3792","source":"IETF/RFC-3792/RFC-3792.txt","version":null},{"body":"IETF","designation":"RFC 3793","folder":"IETF/RFC-3793","source":"IETF/RFC-3793/RFC-3793.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 3100 nested-reference unavailable"},{"id":"IETF RFC 3113","type":"specification","body":"IETF","designation":"RFC 3113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3113.txt","https://www.rfc-editor.org/rfc/rfc3113.pdf"],"folder":"IETF/RFC-3113","files":{"txt":{"path":"standards/IETF/RFC-3113/RFC-3113.txt","sha256":"c8e7fcf5a13de08bc671810d6e24183eb0da6a0f01d48aaa6212393eb656cb47"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the standardization collaboration between\n 3GPP and IETF.\n\n1. Conventions used in this document\n\n This document uses significant terminology that is specialized to\n IETF, 3GPP, or their areas of work. See Appendix A for definitions\n of acronyms. The organizational definitions can be found in their\n respective web-sites.\n\n2. Introduction\n\n This document contains a set of principles and guidelines that serves\n as the basis for establishing the collaboration between 3GPP and\n IETF, with the objective of securing timely development of technical\n specification that facilitate maximum interoperability with existing\n (fixed and mobile) Internet systems, devices, and protocols.\n\n Each organization will operate according to their own rules and\n procedures including rules governing IPR policy, specification\n elaboration, approval and maintenance.\n\nRosenbrock, et al. Informa","scope_keywords":["3113","http","management","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3131","folder":"IETF/RFC-3131","source":"IETF/RFC-3131/RFC-3131.txt","version":null},{"body":"IETF","designation":"RFC 4052","folder":"IETF/RFC-4052","source":"IETF/RFC-4052/RFC-4052.txt","version":null},{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null}],"search_text":"IETF RFC 3113 This document describes the standardization collaboration between\n 3GPP and IETF.\n\n1. Conventions used in this document\n\n This document uses significant terminology that is specialized to\n IETF, 3GPP, or their areas of work. See Appendix A for definitions\n of acronyms. The organizational definitions can be found in their\n respective web-sites.\n\n2. Introduction\n\n This document contains a set of principles and guidelines that serves\n as the basis for establishing the collaboration between 3GPP and\n IETF, with the objective of securing timely development of technical\n specification that facilitate maximum interoperability with existing\n (fixed and mobile) Internet systems, devices, and protocols.\n\n Each organization will operate according to their own rules and\n procedures including rules governing IPR policy, specification\n elaboration, approval and maintenance.\n\nRosenbrock, et al. Informa 3113 http management policies policy nested-reference unchanged"},{"id":"IETF RFC 3119","type":"specification","body":"IETF","designation":"RFC 3119","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3119.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3119.txt","https://www.rfc-editor.org/rfc/rfc3119.pdf"],"folder":"IETF/RFC-3119","files":{"txt":{"path":"standards/IETF/RFC-3119/RFC-3119.txt","sha256":"c2a3dd47e4a8c30025ad49562e4f9039e708150bccc5abc061a15abc148be5c9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a RTP (Real-Time Protocol) payload format for\n transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III\n audio (commonly known as \"MP3\"). This format is an alternative to\n that described in RFC 2250, and performs better if there is packet\n loss.\n\n1. Introduction\n\n While the RTP payload format defined in RFC 2250 [2] is generally\n applicable to all forms of MPEG audio or video, it is sub-optimal for\n MPEG 1 or 2, layer III audio (commonly known as \"MP3\"). The reason\n for this is that an MP3 frame is not a true \"Application Data Unit\" -\n it contains a back-pointer to data in earlier frames, and so cannot\n be decoded independently of these earlier frames. Because RFC 2250\n defines that packet boundaries coincide with frame boundaries, it\n handles packet loss inefficiently when carrying MP3 data. The loss\n of an MP3 frame will render some data in previous (o","scope_keywords":["3119"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 3119 This document describes a RTP (Real-Time Protocol) payload format for\n transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III\n audio (commonly known as \"MP3\"). This format is an alternative to\n that described in RFC 2250, and performs better if there is packet\n loss.\n\n1. Introduction\n\n While the RTP payload format defined in RFC 2250 [2] is generally\n applicable to all forms of MPEG audio or video, it is sub-optimal for\n MPEG 1 or 2, layer III audio (commonly known as \"MP3\"). The reason\n for this is that an MP3 frame is not a true \"Application Data Unit\" -\n it contains a back-pointer to data in earlier frames, and so cannot\n be decoded independently of these earlier frames. Because RFC 2250\n defines that packet boundaries coincide with frame boundaries, it\n handles packet loss inefficiently when carrying MP3 data. The loss\n of an MP3 frame will render some data in previous (o 3119 nested-reference unchanged"},{"id":"IETF RFC 3123","type":"specification","body":"IETF","designation":"RFC 3123","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3123.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3123.txt","https://www.rfc-editor.org/rfc/rfc3123.pdf"],"folder":"IETF/RFC-3123","files":{"txt":{"path":"standards/IETF/RFC-3123/RFC-3123.txt","sha256":"884cfa1e812c9445dffc097a3e672006f4a2ee0a37eec3993e77cc04f11a6d51"}},"tags":["nested-reference","unchanged"],"summary":"The Domain Name System (DNS) is primarily used to translate domain\n names into IPv4 addresses using A RRs (Resource Records). Several\n approaches exist to describe networks or address ranges. This\n document specifies a new DNS RR type \"APL\" for address prefix lists.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n Domain names herein are for explanatory purposes only and should not\n be expected to lead to useful information in real life [RFC2606].\n\n2. Background\n\n The Domain Name System [RFC1034], [RFC1035] provides a mechanism to\n associate addresses and other Internet infrastructure elements with\n hierarchically built domain names. Various types of resource records\n have been defined, especially tho","scope_keywords":["3123","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 3123 The Domain Name System (DNS) is primarily used to translate domain\n names into IPv4 addresses using A RRs (Resource Records). Several\n approaches exist to describe networks or address ranges. This\n document specifies a new DNS RR type \"APL\" for address prefix lists.\n\n1. Conventions used in this document\n\n The key words \"MUST\", \"MUST NOT\", \"REQUIRED\", \"SHALL\", \"SHALL NOT\",\n \"SHOULD\", \"SHOULD NOT\", \"RECOMMENDED\", \"MAY\", and \"OPTIONAL\" in this\n document are to be interpreted as described in [RFC2119].\n\n Domain names herein are for explanatory purposes only and should not\n be expected to lead to useful information in real life [RFC2606].\n\n2. Background\n\n The Domain Name System [RFC1034], [RFC1035] provides a mechanism to\n associate addresses and other Internet infrastructure elements with\n hierarchically built domain names. Various types of resource records\n have been defined, especially tho 3123 key presentation nested-reference unchanged"},{"id":"IETF RFC 313","type":"specification","body":"IETF","designation":"RFC 313","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc313.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc313.txt","https://www.rfc-editor.org/rfc/rfc313.pdf"],"folder":"IETF/RFC-313","files":{"txt":{"path":"standards/IETF/RFC-313/RFC-313.txt","sha256":"39c3c6fbba04e10097a41280f0e9dc7e83b371a751893c1acb058569dead13c7"}},"tags":["nested-reference","unchanged"],"summary":"Computer Network, there are several specific classes of network\n resources that may be useful.","scope_keywords":["313","management","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 313 Computer Network, there are several specific classes of network\n resources that may be useful. 313 management presentation nested-reference unchanged"},{"id":"IETF RFC 3145","type":"specification","body":"IETF","designation":"RFC 3145","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3145.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3145.txt","https://www.rfc-editor.org/rfc/rfc3145.pdf"],"folder":"IETF/RFC-3145","files":{"txt":{"path":"standards/IETF/RFC-3145/RFC-3145.txt","sha256":"ffa622a28694e2f3ab63976b75098bb2af432719b2ef961318137da52fcf07df"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an extension to the Layer 2 Tunneling Protocol\n (\"L2TP\"), a mechanism for tunneling Point-to-Point Protocol (PPP)\n sessions. L2TP lacks a mechanism for a host to provide PPP-related\n disconnect cause information to another host. This information,\n provided by the extension described in this document, can be useful\n for accounting and debugging purposes.\n\n1. Introduction\n\n L2TP [1] defines a general-purpose mechanism for tunneling PPP over\n various media. By design, it insulates L2TP operation from the\n details of the PPP session that is being encapsulated by L2TP. There\n are, however, cases where it may be desirable for PPP-specific\n disconnect information to be provided to an L2TP host (L2TP Access\n Concentrator [LAC] or L2TP Network Server [LNS]) in a descriptive\n format. The lack of this information is especially a problem when\n the LAC and LNS are not owned or ","scope_keywords":["3145","attribute","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null}],"search_text":"IETF RFC 3145 This document provides an extension to the Layer 2 Tunneling Protocol\n (\"L2TP\"), a mechanism for tunneling Point-to-Point Protocol (PPP)\n sessions. L2TP lacks a mechanism for a host to provide PPP-related\n disconnect cause information to another host. This information,\n provided by the extension described in this document, can be useful\n for accounting and debugging purposes.\n\n1. Introduction\n\n L2TP [1] defines a general-purpose mechanism for tunneling PPP over\n various media. By design, it insulates L2TP operation from the\n details of the PPP session that is being encapsulated by L2TP. There\n are, however, cases where it may be desirable for PPP-specific\n disconnect information to be provided to an L2TP host (L2TP Access\n Concentrator [LAC] or L2TP Network Server [LNS]) in a descriptive\n format. The lack of this information is especially a problem when\n the LAC and LNS are not owned or  3145 attribute encryption key nested-reference unchanged"},{"id":"IETF RFC 315","type":"specification","body":"IETF","designation":"RFC 315","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc315.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc315.txt","https://www.rfc-editor.org/rfc/rfc315.pdf"],"folder":"IETF/RFC-315","files":{"txt":{"path":"standards/IETF/RFC-315/RFC-315.txt","sha256":"7073e06ddce2475dbe98e2497985b468de3936ae9e2e5b1cc5dcca92c62d2c35"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: 315 BBN\nNIC: 9345 March 8, 1972\nUpdates: 306\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from February 14\n to February 25. On February 21 Massachusetts celebrated Washington's\n Birthday. During these two weeks the MIT Artificial Intelligence\n (MIT-AI) PDP-10, Network address 134, became a Network User.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMP's wh","scope_keywords":["315"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 319","folder":"IETF/RFC-319","source":"IETF/RFC-319/RFC-319.txt","version":null}],"search_text":"IETF RFC 315 Network Working Group Ellen Westheimer\nRequest for Comments: 315 BBN\nNIC: 9345 March 8, 1972\nUpdates: 306\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from February 14\n to February 25. On February 21 Massachusetts celebrated Washington's\n Birthday. During these two weeks the MIT Artificial Intelligence\n (MIT-AI) PDP-10, Network address 134, became a Network User.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMP's wh 315 nested-reference unchanged"},{"id":"IETF RFC 319","type":"specification","body":"IETF","designation":"RFC 319","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc319.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc319.txt","https://www.rfc-editor.org/rfc/rfc319.pdf"],"folder":"IETF/RFC-319","files":{"txt":{"path":"standards/IETF/RFC-319/RFC-319.txt","sha256":"6019c538d3ba928da22919e5491d49a28a9382289a7b5d3f7d66e8faa7592b28"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: 319 BBN\nNIC: 9349 March 21, 1972\nUpdates: RFC 315\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from February 28\n to March 10. The ETAC Terminal IMP (Network address 148) was\n installed during this period.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular\n basis for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMP's which are presently in the Network\n (AMES, MITRE, NBS and BBN). [The BBN Terminal IMP (Network\n Addres","scope_keywords":["319"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 319 Network Working Group Ellen Westheimer\nRequest for Comments: 319 BBN\nNIC: 9349 March 21, 1972\nUpdates: RFC 315\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from February 28\n to March 10. The ETAC Terminal IMP (Network address 148) was\n installed during this period.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular\n basis for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n 15 Ames/(Paoli) ILLIAC/(B6500)\n\n 2) Hosts which are currently intended to be users only. Included\n here are the Terminal IMP's which are presently in the Network\n (AMES, MITRE, NBS and BBN). [The BBN Terminal IMP (Network\n Addres 319 nested-reference unchanged"},{"id":"IETF RFC 4159","type":"specification","body":"IETF","designation":"RFC 4159","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4159.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4159.txt","https://www.rfc-editor.org/rfc/rfc4159.pdf"],"folder":"IETF/RFC-4159","files":{"txt":{"path":"standards/IETF/RFC-4159/RFC-4159.txt","sha256":"255c860a7c4141d63b38dbd25292eb8d50c27c2a30e8d9083693fa569aa4173b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Huston\nRequest for Comments: 4159 APNIC\nBCP: 109 August 2005\nCategory: Best Current Practice\n\n Deprecation of \"ip6.int\"\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document advises of the deprecation of the use of \"ip6.int\" for\n Standards Conformant IPv6 implementations.\n\n1. IPv6 Standards Action\n\n In August 2001 the IETF published [RFC3152], which advised that the\n use of \"ip6.int\" as the domain for reverse-mapping of IPv6 addresses\n to DNS names was deprecated. The document noted that the use of\n \"ip6.int\" would be phased out in an orderly fashion.\n\n As of 1 September 2005, the IETF advises the community that the DNS\n d","scope_keywords":["4159","http","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6303","folder":"IETF/RFC-6303","source":"IETF/RFC-6303/RFC-6303.txt","version":null}],"search_text":"IETF RFC 4159 Network Working Group G. Huston\nRequest for Comments: 4159 APNIC\nBCP: 109 August 2005\nCategory: Best Current Practice\n\n Deprecation of \"ip6.int\"\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2005).\n\nAbstract\n\n This document advises of the deprecation of the use of \"ip6.int\" for\n Standards Conformant IPv6 implementations.\n\n1. IPv6 Standards Action\n\n In August 2001 the IETF published [RFC3152], which advised that the\n use of \"ip6.int\" as the domain for reverse-mapping of IPv6 addresses\n to DNS names was deprecated. The document noted that the use of\n \"ip6.int\" would be phased out in an orderly fashion.\n\n As of 1 September 2005, the IETF advises the community that the DNS\n d 4159 http license subject nested-reference unchanged"},{"id":"IETF RFC 5039","type":"specification","body":"IETF","designation":"RFC 5039","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5039.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5039.txt","https://www.rfc-editor.org/rfc/rfc5039.pdf"],"folder":"IETF/RFC-5039","files":{"txt":{"path":"standards/IETF/RFC-5039/RFC-5039.txt","sha256":"a347bf763c0e2ee81cf86e9905b106f4da50e3cbb06fead1e1c64bd4fdf83c3a"}},"tags":["nested-reference","unchanged"],"summary":"Spam, defined as the transmission of bulk unsolicited messages, has\n plagued Internet email. Unfortunately, spam is not limited to email.\n It can affect any system that enables user-to-user communications.\n The Session Initiation Protocol (SIP) defines a system for user-to-\n user multimedia communications. Therefore, it is susceptible to\n spam, just as email is. In this document, we analyze the problem of\n spam in SIP. We first identify the ways in which the problem is the\n same and the ways in which it is different from email. We then\n examine the various possible solutions that have been discussed for\n email and consider their applicability to SIP.\n\nRosenberg & Jennings Informational [Page 1]\n\f\nRFC 5039 SIP Spam January 2008","scope_keywords":["5039","risk","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null}],"search_text":"IETF RFC 5039 Spam, defined as the transmission of bulk unsolicited messages, has\n plagued Internet email. Unfortunately, spam is not limited to email.\n It can affect any system that enables user-to-user communications.\n The Session Initiation Protocol (SIP) defines a system for user-to-\n user multimedia communications. Therefore, it is susceptible to\n spam, just as email is. In this document, we analyze the problem of\n spam in SIP. We first identify the ways in which the problem is the\n same and the ways in which it is different from email. We then\n examine the various possible solutions that have been discussed for\n email and consider their applicability to SIP.\n\nRosenberg & Jennings Informational [Page 1]\n\f\nRFC 5039 SIP Spam January 2008 5039 risk signature subject trust nested-reference unchanged"},{"id":"IETF RFC 4810","type":"specification","body":"IETF","designation":"RFC 4810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4810.txt","https://www.rfc-editor.org/rfc/rfc4810.pdf"],"folder":"IETF/RFC-4810","files":{"txt":{"path":"standards/IETF/RFC-4810/RFC-4810.txt","sha256":"f9a4f78cb35d2fb6ac849303cf76992b46db252d79ee195423f327bbd27d2dfa"}},"tags":["nested-reference","unchanged"],"summary":"There are many scenarios in which users must be able to prove the\n existence of data at a specific point in time and be able to\n demonstrate the integrity of data since that time, even when the\n duration from time of existence to time of demonstration spans a\n large period of time. Additionally, users must be able to verify\n signatures on digitally signed data many years after the generation\n of the signature. This document describes a class of long-term\n archive services to support such scenarios and the technical\n requirements for interacting with such services.\n\nWallace, et al. Informational [Page 1]\n\f\nRFC 4810 Archive Requirements March 2007","scope_keywords":["4810","algorithm","algorithms","certificate","certificates","encryption","key","management","policy","preservation","signature","signatures","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4998","folder":"IETF/RFC-4998","source":"IETF/RFC-4998/RFC-4998.txt","version":null},{"body":"IETF","designation":"RFC 5655","folder":"IETF/RFC-5655","source":"IETF/RFC-5655/RFC-5655.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null}],"search_text":"IETF RFC 4810 There are many scenarios in which users must be able to prove the\n existence of data at a specific point in time and be able to\n demonstrate the integrity of data since that time, even when the\n duration from time of existence to time of demonstration spans a\n large period of time. Additionally, users must be able to verify\n signatures on digitally signed data many years after the generation\n of the signature. This document describes a class of long-term\n archive services to support such scenarios and the technical\n requirements for interacting with such services.\n\nWallace, et al. Informational [Page 1]\n\f\nRFC 4810 Archive Requirements March 2007 4810 algorithm algorithms certificate certificates encryption key management policy preservation signature signatures trust validation nested-reference unchanged"},{"id":"IETF RFC 4270","type":"specification","body":"IETF","designation":"RFC 4270","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4270.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4270.txt","https://www.rfc-editor.org/rfc/rfc4270.pdf"],"folder":"IETF/RFC-4270","files":{"txt":{"path":"standards/IETF/RFC-4270/RFC-4270.txt","sha256":"b1cfbc945fe68b3c2471c190d009374ceb968aee82d551ab8836833077f6473f"}},"tags":["nested-reference","unchanged"],"summary":"Recent announcements of better-than-expected collision attacks in\n popular hash algorithms have caused some people to question whether\n common Internet protocols need to be changed, and if so, how. This\n document summarizes the use of hashes in many protocols, discusses\n how the collision attacks affect and do not affect the protocols,\n shows how to thwart known attacks on digital certificates, and\n discusses future directions for protocol designers.\n\n1. Introduction\n\n In summer 2004, a team of researchers showed concrete evidence that\n the MD5 hash algorithm was susceptible to collision attacks\n [MD5-attack]. In early 2005, the same team demonstrated a similar\n attack on a variant of the SHA-1 [RFC3174] hash algorithm, with a\n prediction that the normally used SHA-1 would also be susceptible\n with a large amount of work (but at a level below what should be\n required if SHA-1 worked prop","scope_keywords":["4270","algorithm","algorithms","certificate","certificates","hash","pki","signature","signatures"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 4843","folder":"IETF/RFC-4843","source":"IETF/RFC-4843/RFC-4843.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4982","folder":"IETF/RFC-4982","source":"IETF/RFC-4982/RFC-4982.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5535","folder":"IETF/RFC-5535","source":"IETF/RFC-5535/RFC-5535.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5752","folder":"IETF/RFC-5752","source":"IETF/RFC-5752/RFC-5752.txt","version":null},{"body":"IETF","designation":"RFC 5997","folder":"IETF/RFC-5997","source":"IETF/RFC-5997/RFC-5997.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6149","folder":"IETF/RFC-6149","source":"IETF/RFC-6149/RFC-6149.txt","version":null},{"body":"IETF","designation":"RFC 6150","folder":"IETF/RFC-6150","source":"IETF/RFC-6150/RFC-6150.txt","version":null},{"body":"IETF","designation":"RFC 6151","folder":"IETF/RFC-6151","source":"IETF/RFC-6151/RFC-6151.txt","version":null},{"body":"IETF","designation":"RFC 6194","folder":"IETF/RFC-6194","source":"IETF/RFC-6194/RFC-6194.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 7711","folder":"IETF/RFC-7711","source":"IETF/RFC-7711/RFC-7711.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 4270 Recent announcements of better-than-expected collision attacks in\n popular hash algorithms have caused some people to question whether\n common Internet protocols need to be changed, and if so, how. This\n document summarizes the use of hashes in many protocols, discusses\n how the collision attacks affect and do not affect the protocols,\n shows how to thwart known attacks on digital certificates, and\n discusses future directions for protocol designers.\n\n1. Introduction\n\n In summer 2004, a team of researchers showed concrete evidence that\n the MD5 hash algorithm was susceptible to collision attacks\n [MD5-attack]. In early 2005, the same team demonstrated a similar\n attack on a variant of the SHA-1 [RFC3174] hash algorithm, with a\n prediction that the normally used SHA-1 would also be susceptible\n with a large amount of work (but at a level below what should be\n required if SHA-1 worked prop 4270 algorithm algorithms certificate certificates hash pki signature signatures nested-reference unchanged"},{"id":"IETF RFC 3179","type":"specification","body":"IETF","designation":"RFC 3179","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3179.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3179.txt","https://www.rfc-editor.org/rfc/rfc3179.pdf"],"folder":"IETF/RFC-3179","files":{"txt":{"path":"standards/IETF/RFC-3179/RFC-3179.txt","sha256":"a0c74b1d95d663f761759f9c8b6a3b22b8ad81f59d92f027ec6d1ee9ce1159b3"}},"tags":["nested-reference","unchanged"],"summary":"The Script MIB extensibility protocol (SMX) defined in this memo\n separates language specific runtime systems from language independent\n Script MIB implementations. The IETF Script MIB defines an interface\n for the delegation of management functions based on the Internet\n management framework. A management script is a set of instructions\n that are executed by a language specific runtime system.","scope_keywords":["3179","management","profile","profiles"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null}],"search_text":"IETF RFC 3179 The Script MIB extensibility protocol (SMX) defined in this memo\n separates language specific runtime systems from language independent\n Script MIB implementations. The IETF Script MIB defines an interface\n for the delegation of management functions based on the Internet\n management framework. A management script is a set of instructions\n that are executed by a language specific runtime system. 3179 management profile profiles nested-reference unchanged"},{"id":"IETF RFC 435","type":"specification","body":"IETF","designation":"RFC 435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc435.txt","https://www.rfc-editor.org/rfc/rfc435.pdf"],"folder":"IETF/RFC-435","files":{"txt":{"path":"standards/IETF/RFC-435/RFC-435.txt","sha256":"8b37288ac6841d06fc90ed9a2998b362a73ba26cc0fc195e0bd9f2bef72187a0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Cosell\nRequest for Comment: 435 BBN-NET\nNIC: 13675 D. Walden\nCategory: TELNET, Protocols, Echoing BBN-NET\nReferences: 318, 357 5 January 1973\n\n TELNET Issues\n\n This RFC discusses a number of TELNET related issues which have been\n bothering us [1]. The basic, central issue we started from was that\n of echoing. We worked downward from our difficulties to discover the\n basic principles at the root of our unhappiness, and from there\n worked back upwards to design a scheme which we believe to be better.\n In this note we will discuss both the alternate scheme and its\n underlying principles.\n\n As something of a non sequitur, before discussing echoing we feel it\n expedient to dismiss one possible stumbling block, outright. HIDE\n YOUR INPUT may or may not be a good idea, this question not\n concerning us at the moment. Whatever the case, the issue of hiding\n input is certa","scope_keywords":["435"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 451","folder":"IETF/RFC-451","source":"IETF/RFC-451/RFC-451.txt","version":null}],"search_text":"IETF RFC 435 Network Working Group B. Cosell\nRequest for Comment: 435 BBN-NET\nNIC: 13675 D. Walden\nCategory: TELNET, Protocols, Echoing BBN-NET\nReferences: 318, 357 5 January 1973\n\n TELNET Issues\n\n This RFC discusses a number of TELNET related issues which have been\n bothering us [1]. The basic, central issue we started from was that\n of echoing. We worked downward from our difficulties to discover the\n basic principles at the root of our unhappiness, and from there\n worked back upwards to design a scheme which we believe to be better.\n In this note we will discuss both the alternate scheme and its\n underlying principles.\n\n As something of a non sequitur, before discussing echoing we feel it\n expedient to dismiss one possible stumbling block, outright. HIDE\n YOUR INPUT may or may not be a good idea, this question not\n concerning us at the moment. Whatever the case, the issue of hiding\n input is certa 435 nested-reference unchanged"},{"id":"IETF RFC 750","type":"specification","body":"IETF","designation":"RFC 750","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc750.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc750.txt","https://www.rfc-editor.org/rfc/rfc750.pdf"],"folder":"IETF/RFC-750","files":{"txt":{"path":"standards/IETF/RFC-750/RFC-750.txt","sha256":"294840011c74a3bf8fe290278435232c750097bddcd73f07db2317d5e33a9fd4"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 750 JBP 26-Sep-78 18:30 45500\n\nNetwork Working Group J. Postel\nRequest for Comments: 750 USC-ISI\nNIC: 45500 26 September 1978\n\nObsoletes: 739,\n604, 503, 433, 349\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The ","scope_keywords":["750","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null}],"search_text":"IETF RFC 750 NWG/RFC 750 JBP 26-Sep-78 18:30 45500\n\nNetwork Working Group J. Postel\nRequest for Comments: 750 USC-ISI\nNIC: 45500 26 September 1978\n\nObsoletes: 739,\n604, 503, 433, 349\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The  750 authentication nested-reference unchanged"},{"id":"IETF RFC 758","type":"specification","body":"IETF","designation":"RFC 758","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc758.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc758.txt","https://www.rfc-editor.org/rfc/rfc758.pdf"],"folder":"IETF/RFC-758","files":{"txt":{"path":"standards/IETF/RFC-758/RFC-758.txt","sha256":"fd65a2580ca5d087a0155c016419f5bd7f8a29222e2caff7df6bf65942499e4e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 758 USC-ISI\nIEN: 117 August 1979\n\nObsoletes RFCs: 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent","scope_keywords":["758"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null}],"search_text":"IETF RFC 758 Network Working Group J. Postel\nRequest for Comments: 758 USC-ISI\nIEN: 117 August 1979\n\nObsoletes RFCs: 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIB\n\nMost of the protocols mentioned here are documented in the RFC series of\nnotes. The more prominent 758 nested-reference unchanged"},{"id":"IETF RFC 762","type":"specification","body":"IETF","designation":"RFC 762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc762.txt","https://www.rfc-editor.org/rfc/rfc762.pdf"],"folder":"IETF/RFC-762","files":{"txt":{"path":"standards/IETF/RFC-762/RFC-762.txt","sha256":"477c97752bd17e63b3ff5080ca53ac8fc487a71900908d244e3ce093ba6e78d2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 762 USC-ISI\nInternet Experiment Note: 127 January 1980\n\nObsoletes RFCs: 758, 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIE\n\nMost of the protocols mentioned here are documented in the RFC ser","scope_keywords":["762"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0768","folder":"IETF/RFC-0768","source":"IETF/RFC-0768/RFC-0768.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 760","folder":"IETF/RFC-760","source":"IETF/RFC-760/RFC-760.txt","version":null},{"body":"IETF","designation":"RFC 768","folder":"IETF/RFC-768","source":"IETF/RFC-768/RFC-768.txt","version":null}],"search_text":"IETF RFC 762 Network Working Group J. Postel\nRequest for Comments: 762 USC-ISI\nInternet Experiment Note: 127 January 1980\n\nObsoletes RFCs: 758, 755,\n750,739, 604, 503, 433, 349\nObsoletes IENs: 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, etc. please\ncontact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIE\n\nMost of the protocols mentioned here are documented in the RFC ser 762 nested-reference unchanged"},{"id":"IETF RFC 776","type":"specification","body":"IETF","designation":"RFC 776","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc776.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc776.txt","https://www.rfc-editor.org/rfc/rfc776.pdf"],"folder":"IETF/RFC-776","files":{"txt":{"path":"standards/IETF/RFC-776/RFC-776.txt","sha256":"f4057d326420c4dcb5b7b19b31e96944f8d818ee0e0640bf12a7d9ceb2613f5c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 776 ISI\n January 1981\n\nObsoletes RFCs: 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, port, protocol,\nor network number please contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIF\n\nMost of the protocols mentioned here are documented in","scope_keywords":["776"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 776 Network Working Group J. Postel\nRequest for Comments: 776 ISI\n January 1981\n\nObsoletes RFCs: 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, port, protocol,\nor network number please contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIF\n\nMost of the protocols mentioned here are documented in 776 nested-reference unchanged"},{"id":"IETF RFC 790","type":"specification","body":"IETF","designation":"RFC 790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc790.txt","https://www.rfc-editor.org/rfc/rfc790.pdf"],"folder":"IETF/RFC-790","files":{"txt":{"path":"standards/IETF/RFC-790/RFC-790.txt","sha256":"8f6e445ca9eee011ea0862cd0202e9249af44befe4a50d2042a3b39f979d4bfb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 790 ISI\n September 1981\n\nObsoletes RFCs: 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, port, protocol,\nor network number please contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIF\n\nMost of the protocols mentioned here are docume","scope_keywords":["790"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0791","folder":"IETF/RFC-0791","source":"IETF/RFC-0791/RFC-0791.txt","version":null},{"body":"IETF","designation":"RFC 0793","folder":"IETF/RFC-0793","source":"IETF/RFC-0793/RFC-0793.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 791","folder":"IETF/RFC-791","source":"IETF/RFC-791/RFC-791.txt","version":null},{"body":"IETF","designation":"RFC 793","folder":"IETF/RFC-793","source":"IETF/RFC-793/RFC-793.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 802","folder":"IETF/RFC-802","source":"IETF/RFC-802/RFC-802.txt","version":null},{"body":"IETF","designation":"RFC 810","folder":"IETF/RFC-810","source":"IETF/RFC-810/RFC-810.txt","version":null},{"body":"IETF","designation":"RFC 823","folder":"IETF/RFC-823","source":"IETF/RFC-823/RFC-823.txt","version":null},{"body":"IETF","designation":"RFC 824","folder":"IETF/RFC-824","source":"IETF/RFC-824/RFC-824.txt","version":null},{"body":"IETF","designation":"RFC 830","folder":"IETF/RFC-830","source":"IETF/RFC-830/RFC-830.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 790 Network Working Group J. Postel\nRequest for Comments: 790 ISI\n September 1981\n\nObsoletes RFCs: 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon. If you are developing a protocol or\napplication that will require the use of a link, socket, port, protocol,\nor network number please contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n phone: (213) 822-1511\n\n ARPANET mail: POSTEL@ISIF\n\nMost of the protocols mentioned here are docume 790 nested-reference unchanged"},{"id":"IETF RFC 820","type":"specification","body":"IETF","designation":"RFC 820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc820.txt","https://www.rfc-editor.org/rfc/rfc820.pdf"],"folder":"IETF/RFC-820","files":{"txt":{"path":"standards/IETF/RFC-820/RFC-820.txt","sha256":"0a3ac8fc3f7296335859f43648e7cc627c61b20f087968d58d68bc9fd60617ac"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 820 J. Vernon\n January 1983\n\nObsoletes RFCs: 790, 776, 770, 762,\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon, subject to the agreement between\nDARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A\nof this RFC. If you are developing a protocol or application that will\nrequire the use of a link, socket, port, protocol, or network number\nplease contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marin","scope_keywords":["820","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null}],"search_text":"IETF RFC 820 Network Working Group J. Postel\nRequest for Comments: 820 J. Vernon\n January 1983\n\nObsoletes RFCs: 790, 776, 770, 762,\n758, 755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Jon Postel. The assignment of\nnumbers is also handled by Jon, subject to the agreement between\nDARPA/IPTO and DDN/PMO about number allocation, documented in Appendix A\nof this RFC. If you are developing a protocol or application that will\nrequire the use of a link, socket, port, protocol, or network number\nplease contact Jon to receive a number assignment.\n\n Jon Postel\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marin 820 risk subject nested-reference unchanged"},{"id":"IETF RFC 3200","type":"specification","body":"IETF","designation":"RFC 3200","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc3200.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3200.txt","https://www.rfc-editor.org/rfc/rfc3200.pdf"],"folder":"IETF/RFC-3200","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null}],"search_text":"IETF RFC 3200 nested-reference unavailable"},{"id":"IETF RFC 7435","type":"specification","body":"IETF","designation":"RFC 7435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7435.txt","https://www.rfc-editor.org/rfc/rfc7435.pdf"],"folder":"IETF/RFC-7435","files":{"txt":{"path":"standards/IETF/RFC-7435/RFC-7435.txt","sha256":"edb78fc4e497b7e451bba914decc3e2b77da8f37b9fb645c8f81d3287454a3d4"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the concept \"Opportunistic Security\" in the\n context of communications protocols. Protocol designs based on\n Opportunistic Security use encryption even when authentication is not\n available, and use authentication when possible, thereby removing\n barriers to the widespread use of encryption on the Internet.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,","scope_keywords":["7435","authentication","certificate","certificates","encryption","http","key","keys","license","management","pki","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7619","folder":"IETF/RFC-7619","source":"IETF/RFC-7619/RFC-7619.txt","version":null},{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7687","folder":"IETF/RFC-7687","source":"IETF/RFC-7687/RFC-7687.txt","version":null},{"body":"IETF","designation":"RFC 7696","folder":"IETF/RFC-7696","source":"IETF/RFC-7696/RFC-7696.txt","version":null},{"body":"IETF","designation":"RFC 7858","folder":"IETF/RFC-7858","source":"IETF/RFC-7858/RFC-7858.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8164","folder":"IETF/RFC-8164","source":"IETF/RFC-8164/RFC-8164.txt","version":null},{"body":"IETF","designation":"RFC 8310","folder":"IETF/RFC-8310","source":"IETF/RFC-8310/RFC-8310.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7435 This document defines the concept \"Opportunistic Security\" in the\n context of communications protocols. Protocol designs based on\n Opportunistic Security use encryption even when authentication is not\n available, and use authentication when possible, thereby removing\n barriers to the widespread use of encryption on the Internet.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata, 7435 authentication certificate certificates encryption http key keys license management pki policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 5317","type":"specification","body":"IETF","designation":"RFC 5317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5317.txt","https://www.rfc-editor.org/rfc/rfc5317.pdf"],"folder":"IETF/RFC-5317","files":{"pdf":{"path":"standards/IETF/RFC-5317/RFC-5317.pdf","sha256":"e3208240a5da42cd06e2cf61aeae5dc92728c155f3426b1841e379eac46fe165"},"txt":{"path":"standards/IETF/RFC-5317/RFC-5317.txt","sha256":"3464110aeeb500db72a3111597e69cf99450a13e68af63553bc73636b8b3f2f1"}},"tags":["nested-reference","unchanged"],"summary":"This RFC archives the report of the IETF - ITU-T Joint Working Team\n (JWT) on the application of MPLS to transport networks. The JWT\n recommended of Option 1: The IETF and the ITU-T jointly agree to work\n together and bring transport requirements into the IETF and extend\n IETF MPLS forwarding, OAM (Operations, Administration, and\n Management), survivability, network management and control plane\n protocols to meet those requirements through the IETF Standards\n Process. This RFC is available in ASCII (which contains a summary of\n the slides) and in PDF (which contains the summary and a copy of the\n slides).\n\nBryant & Andersson Informational [Page 1]\n\f\nRFC 5317 JWT MPLS-TP Report February 2009","scope_keywords":["5317","http","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5317 This RFC archives the report of the IETF - ITU-T Joint Working Team\n (JWT) on the application of MPLS to transport networks. The JWT\n recommended of Option 1: The IETF and the ITU-T jointly agree to work\n together and bring transport requirements into the IETF and extend\n IETF MPLS forwarding, OAM (Operations, Administration, and\n Management), survivability, network management and control plane\n protocols to meet those requirements through the IETF Standards\n Process. This RFC is available in ASCII (which contains a summary of\n the slides) and in PDF (which contains the summary and a copy of the\n slides).\n\nBryant & Andersson Informational [Page 1]\n\f\nRFC 5317 JWT MPLS-TP Report February 2009 5317 http license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 323","type":"specification","body":"IETF","designation":"RFC 323","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc323.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc323.txt","https://www.rfc-editor.org/rfc/rfc323.pdf"],"folder":"IETF/RFC-323","files":{"txt":{"path":"standards/IETF/RFC-323/RFC-323.txt","sha256":"b6eacb833e70d77bd7e8790eec3a8239c7e4508da368a924bed9542db83c9f15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Vint Cerf\nRequest for Comments: 323 UCLA-NMC\nNIC: 9630 March 23, 1972\n\n Formation of Network Measurement Group (NMG)\n\n On March 17, 1972, at MIT project MAC, the following group met to\n discuss plans to perform measurement experiments on the ARPANET:\n\n A. Bhushan - MIT/DMCG\n\n V. Cerf - UCLA/NMC, Chairman, NMG\n\n S. Crocker - ARPA/IPT\n\n J. Forgie - LL/TX-2\n\n R. Metcalfe - MIT/HARV/DMCG\n\n M. Padlipsky - MIT/MULTICS\n\n J. Postel - UCLA/NMC\n\n J. Winett - LL/67\n\n The purpose of the meeting was to discuss existing and planned\n measurements of network and HOST behavior.\n\n1. Measurement Link #'s\n\n It was agreed (after a ridiculously long discussion) to allocate\n links 159-191 for network measurement only (see RFC #317). It was\n further agreed that these links would be allocated in the following\n way:\n\n 159-174 HOST DISCARD; co-operating HOSTS receiving messages on\n these link","scope_keywords":["323"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 388","folder":"IETF/RFC-388","source":"IETF/RFC-388/RFC-388.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null}],"search_text":"IETF RFC 323 Network Working Group Vint Cerf\nRequest for Comments: 323 UCLA-NMC\nNIC: 9630 March 23, 1972\n\n Formation of Network Measurement Group (NMG)\n\n On March 17, 1972, at MIT project MAC, the following group met to\n discuss plans to perform measurement experiments on the ARPANET:\n\n A. Bhushan - MIT/DMCG\n\n V. Cerf - UCLA/NMC, Chairman, NMG\n\n S. Crocker - ARPA/IPT\n\n J. Forgie - LL/TX-2\n\n R. Metcalfe - MIT/HARV/DMCG\n\n M. Padlipsky - MIT/MULTICS\n\n J. Postel - UCLA/NMC\n\n J. Winett - LL/67\n\n The purpose of the meeting was to discuss existing and planned\n measurements of network and HOST behavior.\n\n1. Measurement Link #'s\n\n It was agreed (after a ridiculously long discussion) to allocate\n links 159-191 for network measurement only (see RFC #317). It was\n further agreed that these links would be allocated in the following\n way:\n\n 159-174 HOST DISCARD; co-operating HOSTS receiving messages on\n these link 323 nested-reference unchanged"},{"id":"IETF RFC 388","type":"specification","body":"IETF","designation":"RFC 388","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc388.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc388.txt","https://www.rfc-editor.org/rfc/rfc388.pdf"],"folder":"IETF/RFC-388","files":{"txt":{"path":"standards/IETF/RFC-388/RFC-388.txt","sha256":"340ae7bb54f925a8ff9a68c7d007c80bd18fec71a0c8970141d0da4f5e1591c8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 388 UCLA-NMC\nObsoletes: 323 23 August 1972\nNIC: 11360\nNetwork Measurement Note #8\n\n NCP Statistics\n\n After a lapse of 5 months since RFC #323 was issued (23 March), I am\n pleased to announce that UCLA-NMC is prepared to gather your NCP\n statistics automatically on a daily basis. The results will be\n published monthly as Network Measurement notes and as RFC's. We will\n periodically open a connection on your local socket @241 (decimal),\n expecting you to send the following data in the format shown:\n\n \n\n a. Total bits sent to HOST\n b. Total bits received from HOST\n c. Total messages sent to HOST\n d. Total messages received from HOST and optionally\n e. Average Round Trip delay on send connections to HOST\n\n The information above should be collected only for standard open\n connections (i.e. those using standard NCP protocol) and not\n measurem","scope_keywords":["388"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null}],"search_text":"IETF RFC 388 Network Working Group V. Cerf\nRequest for Comments: 388 UCLA-NMC\nObsoletes: 323 23 August 1972\nNIC: 11360\nNetwork Measurement Note #8\n\n NCP Statistics\n\n After a lapse of 5 months since RFC #323 was issued (23 March), I am\n pleased to announce that UCLA-NMC is prepared to gather your NCP\n statistics automatically on a daily basis. The results will be\n published monthly as Network Measurement notes and as RFC's. We will\n periodically open a connection on your local socket @241 (decimal),\n expecting you to send the following data in the format shown:\n\n \n\n a. Total bits sent to HOST\n b. Total bits received from HOST\n c. Total messages sent to HOST\n d. Total messages received from HOST and optionally\n e. Average Round Trip delay on send connections to HOST\n\n The information above should be collected only for standard open\n connections (i.e. those using standard NCP protocol) and not\n measurem 388 nested-reference unchanged"},{"id":"IETF RFC 5829","type":"specification","body":"IETF","designation":"RFC 5829","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5829.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5829.txt","https://www.rfc-editor.org/rfc/rfc5829.pdf"],"folder":"IETF/RFC-5829","files":{"txt":{"path":"standards/IETF/RFC-5829/RFC-5829.txt","sha256":"45bc26d1e355d4e6929ca0963ecc8b9d9b75426a1741bf588d8564f88d2dbe9d"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a set of link relation types that may be\n used on Web resources for navigation between a resource and other\n resources related to version control, such as past versions and\n working copies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5829.\n\nCopyright Notice\n","scope_keywords":["5829","http","license","management","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5988","folder":"IETF/RFC-5988","source":"IETF/RFC-5988/RFC-5988.txt","version":null},{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null}],"search_text":"IETF RFC 5829 This specification defines a set of link relation types that may be\n used on Web resources for navigation between a resource and other\n resources related to version control, such as past versions and\n working copies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5829.\n\nCopyright Notice\n 5829 http license management subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 3256","type":"specification","body":"IETF","designation":"RFC 3256","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3256.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3256.txt","https://www.rfc-editor.org/rfc/rfc3256.pdf"],"folder":"IETF/RFC-3256","files":{"txt":{"path":"standards/IETF/RFC-3256/RFC-3256.txt","sha256":"e0b852a4db917feb08c5abfadf5e5ed953272a9945aafa750dd7e6ec1641aa7a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Jones\nRequest for Comments: 3256 YAS Corporation\nCategory: Standards Track R. Woundy\n AT&T Broadband\n April 2002\n\n The DOCSIS (Data-Over-Cable Service Interface Specifications) Device\n Class DHCP (Dynamic Host Configuration Protocol) Relay Agent\n Information Sub-option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document proposes a new sub-option to the DHCP (Dynamic Host\n Configuration Protocol) Relay Agent Information Option. This new\n sub-option is for use with DOCSIS (Data-Over-Cable Service Interface\n Specifications) cable modem","scope_keywords":["3256","attribute","attributes","http","identification","key","policies","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null}],"search_text":"IETF RFC 3256 Network Working Group D. Jones\nRequest for Comments: 3256 YAS Corporation\nCategory: Standards Track R. Woundy\n AT&T Broadband\n April 2002\n\n The DOCSIS (Data-Over-Cable Service Interface Specifications) Device\n Class DHCP (Dynamic Host Configuration Protocol) Relay Agent\n Information Sub-option\n\nStatus of this Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document proposes a new sub-option to the DHCP (Dynamic Host\n Configuration Protocol) Relay Agent Information Option. This new\n sub-option is for use with DOCSIS (Data-Over-Cable Service Interface\n Specifications) cable modem 3256 attribute attributes http identification key policies policy trust nested-reference unchanged"},{"id":"IETF RFC 326","type":"specification","body":"IETF","designation":"RFC 326","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc326.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc326.txt","https://www.rfc-editor.org/rfc/rfc326.pdf"],"folder":"IETF/RFC-326","files":{"txt":{"path":"standards/IETF/RFC-326/RFC-326.txt","sha256":"ff9ecc8b500cce402442a88c8cb1528bbd791837bfc0888785980701404a6770"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC # 9633 BBN\nRFC # 326 3 April 1972\nCategories: F, G.3\nUpdates: RFC #319\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from\nMarch 13 to March 24. During this period the SRI-AI computer\nbecame a server.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n2) Hosts which are currently intended to be users only. Included here\nare the Terminal IMPs, which are presently in the Network (AMES,\nMITRE, NBS, ETAC, and BBN*). This category also includes the Network\nControl Center computer (Network Addr","scope_keywords":["326"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 326 Network Working Group Ellen Westheimer\nNIC # 9633 BBN\nRFC # 326 3 April 1972\nCategories: F, G.3\nUpdates: RFC #319\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from\nMarch 13 to March 24. During this period the SRI-AI computer\nbecame a server.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n2) Hosts which are currently intended to be users only. Included here\nare the Terminal IMPs, which are presently in the Network (AMES,\nMITRE, NBS, ETAC, and BBN*). This category also includes the Network\nControl Center computer (Network Addr 326 nested-reference unchanged"},{"id":"IETF RFC 3321","type":"specification","body":"IETF","designation":"RFC 3321","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3321.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3321.txt","https://www.rfc-editor.org/rfc/rfc3321.pdf"],"folder":"IETF/RFC-3321","files":{"txt":{"path":"standards/IETF/RFC-3321/RFC-3321.txt","sha256":"d63294743807541191a9628c23740bfc84788dedbf4005a393b986e054bbd057"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to implement certain mechanisms in\n Signaling Compression (SigComp), RFC 3320, which can significantly\n improve the compression efficiency compared to using simple per-\n message compression.\n\n SigComp uses a Universal Decompressor Virtual Machine (UDVM) for\n decompression, and the mechanisms described in this document are\n possible to implement using the UDVM instructions defined in RFC\n 3320.\n\nHannu, et. al. Informational [Page 1]\n\f\nRFC 3321 SigComp - Extended Operations January 2003","scope_keywords":["3321","algorithm","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 4077","folder":"IETF/RFC-4077","source":"IETF/RFC-4077/RFC-4077.txt","version":null},{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null}],"search_text":"IETF RFC 3321 This document describes how to implement certain mechanisms in\n Signaling Compression (SigComp), RFC 3320, which can significantly\n improve the compression efficiency compared to using simple per-\n message compression.\n\n SigComp uses a Universal Decompressor Virtual Machine (UDVM) for\n decompression, and the mechanisms described in this document are\n possible to implement using the UDVM instructions defined in RFC\n 3320.\n\nHannu, et. al. Informational [Page 1]\n\f\nRFC 3321 SigComp - Extended Operations January 2003 3321 algorithm risk nested-reference unchanged"},{"id":"IETF RFC 3324","type":"specification","body":"IETF","designation":"RFC 3324","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3324.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3324.txt","https://www.rfc-editor.org/rfc/rfc3324.pdf"],"folder":"IETF/RFC-3324","files":{"txt":{"path":"standards/IETF/RFC-3324/RFC-3324.txt","sha256":"0f558e529d19c4f0d315466f2af22c831bbdd3e09af74f76291fce93f4cfdf28"}},"tags":["nested-reference","unchanged"],"summary":"A Network Asserted Identity is an identity initially derived by a\n Session Initiation Protocol (SIP) network intermediary as a result of\n an authentication process. This document describes short term\n requirements for the exchange of Network Asserted Identities within\n networks of securely interconnected trusted nodes and to User Agents\n securely connected to such networks.\n\n There is no requirement for identities asserted by a UA in a SIP\n message to be anything other than the user's desired alias.\n\nWatson Informational [Page 1]\n\f\nRFC 3324 Requirements for Network Asserted Identity November 2002","scope_keywords":["3324","authentication","key","policy","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3325","folder":"IETF/RFC-3325","source":"IETF/RFC-3325/RFC-3325.txt","version":null},{"body":"IETF","designation":"RFC 3455","folder":"IETF/RFC-3455","source":"IETF/RFC-3455/RFC-3455.txt","version":null},{"body":"IETF","designation":"RFC 3487","folder":"IETF/RFC-3487","source":"IETF/RFC-3487/RFC-3487.txt","version":null},{"body":"IETF","designation":"RFC 7340","folder":"IETF/RFC-7340","source":"IETF/RFC-7340/RFC-7340.txt","version":null}],"search_text":"IETF RFC 3324 A Network Asserted Identity is an identity initially derived by a\n Session Initiation Protocol (SIP) network intermediary as a result of\n an authentication process. This document describes short term\n requirements for the exchange of Network Asserted Identities within\n networks of securely interconnected trusted nodes and to User Agents\n securely connected to such networks.\n\n There is no requirement for identities asserted by a UA in a SIP\n message to be anything other than the user's desired alias.\n\nWatson Informational [Page 1]\n\f\nRFC 3324 Requirements for Network Asserted Identity November 2002 3324 authentication key policy trust nested-reference unchanged"},{"id":"IETF RFC 3515","type":"specification","body":"IETF","designation":"RFC 3515","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3515.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3515.txt","https://www.rfc-editor.org/rfc/rfc3515.pdf"],"folder":"IETF/RFC-3515","files":{"txt":{"path":"standards/IETF/RFC-3515/RFC-3515.txt","sha256":"77898412d832bbd8f70a2dd8c1c1a82bc7fa2eae2e59ca65c5fe28d34ebf6a49"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the REFER method. This Session Initiation\n Protocol (SIP) extension requests that the recipient REFER to a\n resource provided in the request. It provides a mechanism allowing\n the party sending the REFER to be notified of the outcome of the\n referenced request. This can be used to enable many applications,\n including call transfer.\n\n In addition to the REFER method, this document defines the the refer\n event package and the Refer-To request header.","scope_keywords":["3515","authorization","encryption","http"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3603","folder":"IETF/RFC-3603","source":"IETF/RFC-3603/RFC-3603.txt","version":null},{"body":"IETF","designation":"RFC 3841","folder":"IETF/RFC-3841","source":"IETF/RFC-3841/RFC-3841.txt","version":null},{"body":"IETF","designation":"RFC 3891","folder":"IETF/RFC-3891","source":"IETF/RFC-3891/RFC-3891.txt","version":null},{"body":"IETF","designation":"RFC 3892","folder":"IETF/RFC-3892","source":"IETF/RFC-3892/RFC-3892.txt","version":null},{"body":"IETF","designation":"RFC 3911","folder":"IETF/RFC-3911","source":"IETF/RFC-3911/RFC-3911.txt","version":null},{"body":"IETF","designation":"RFC 4235","folder":"IETF/RFC-4235","source":"IETF/RFC-4235/RFC-4235.txt","version":null},{"body":"IETF","designation":"RFC 4353","folder":"IETF/RFC-4353","source":"IETF/RFC-4353/RFC-4353.txt","version":null},{"body":"IETF","designation":"RFC 4412","folder":"IETF/RFC-4412","source":"IETF/RFC-4412/RFC-4412.txt","version":null},{"body":"IETF","designation":"RFC 4485","folder":"IETF/RFC-4485","source":"IETF/RFC-4485/RFC-4485.txt","version":null},{"body":"IETF","designation":"RFC 4488","folder":"IETF/RFC-4488","source":"IETF/RFC-4488/RFC-4488.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5057","folder":"IETF/RFC-5057","source":"IETF/RFC-5057/RFC-5057.txt","version":null},{"body":"IETF","designation":"RFC 5359","folder":"IETF/RFC-5359","source":"IETF/RFC-5359/RFC-5359.txt","version":null},{"body":"IETF","designation":"RFC 5368","folder":"IETF/RFC-5368","source":"IETF/RFC-5368/RFC-5368.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5630","folder":"IETF/RFC-5630","source":"IETF/RFC-5630/RFC-5630.txt","version":null},{"body":"IETF","designation":"RFC 5767","folder":"IETF/RFC-5767","source":"IETF/RFC-5767/RFC-5767.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6881","folder":"IETF/RFC-6881","source":"IETF/RFC-6881/RFC-6881.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 3515 This document defines the REFER method. This Session Initiation\n Protocol (SIP) extension requests that the recipient REFER to a\n resource provided in the request. It provides a mechanism allowing\n the party sending the REFER to be notified of the outcome of the\n referenced request. This can be used to enable many applications,\n including call transfer.\n\n In addition to the REFER method, this document defines the the refer\n event package and the Refer-To request header. 3515 authorization encryption http nested-reference unchanged"},{"id":"IETF RFC 3574","type":"specification","body":"IETF","designation":"RFC 3574","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3574.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3574.txt","https://www.rfc-editor.org/rfc/rfc3574.pdf"],"folder":"IETF/RFC-3574","files":{"txt":{"path":"standards/IETF/RFC-3574/RFC-3574.txt","sha256":"3630e9f4cf5d959235543065ed0df41bb1c5f48f9bba3bc4bc77019ac32dc08e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes different scenarios in Third Generation\n Partnership Project (3GPP) defined packet network, i.e., General\n Packet Radio Service (GPRS) that would need IP version 6 and IP\n version 4 transition. The focus of this document is on the scenarios\n where the User Equipment (UE) connects to nodes in other networks,\n e.g., in the Internet. GPRS network internal transition scenarios,\n i.e., between different GPRS elements in the network, are out of\n scope. The purpose of the document is to list the scenarios for\n further discussion and study.","scope_keywords":["3574","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4215","folder":"IETF/RFC-4215","source":"IETF/RFC-4215/RFC-4215.txt","version":null},{"body":"IETF","designation":"RFC 4339","folder":"IETF/RFC-4339","source":"IETF/RFC-4339/RFC-4339.txt","version":null},{"body":"IETF","designation":"RFC 6180","folder":"IETF/RFC-6180","source":"IETF/RFC-6180/RFC-6180.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 3574 This document describes different scenarios in Third Generation\n Partnership Project (3GPP) defined packet network, i.e., General\n Packet Radio Service (GPRS) that would need IP version 6 and IP\n version 4 transition. The focus of this document is on the scenarios\n where the User Equipment (UE) connects to nodes in other networks,\n e.g., in the Internet. GPRS network internal transition scenarios,\n i.e., between different GPRS elements in the network, are out of\n scope. The purpose of the document is to list the scenarios for\n further discussion and study. 3574 management nested-reference unchanged"},{"id":"IETF RFC 3578","type":"specification","body":"IETF","designation":"RFC 3578","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3578.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3578.txt","https://www.rfc-editor.org/rfc/rfc3578.pdf"],"folder":"IETF/RFC-3578","files":{"txt":{"path":"standards/IETF/RFC-3578/RFC-3578.txt","sha256":"0ca125218b4330619b5e0bfb9c2d11d624630c0c0339826f3ab21108b8ac72eb"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a way to map Integrated Services Digital\n Network User Part (ISUP) overlap signalling to Session Initiation\n Protocol (SIP). This mechanism might be implemented when using SIP\n in an environment where part of the call involves interworking with\n the Public Switched Telephone Network (PSTN).\n\nCamarillo, et al. Standards Track [Page 1]\n\f\nRFC 3578 ISUP Overlap Signalling to SIP August 2003","scope_keywords":["3578"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null}],"search_text":"IETF RFC 3578 This document describes a way to map Integrated Services Digital\n Network User Part (ISUP) overlap signalling to Session Initiation\n Protocol (SIP). This mechanism might be implemented when using SIP\n in an environment where part of the call involves interworking with\n the Public Switched Telephone Network (PSTN).\n\nCamarillo, et al. Standards Track [Page 1]\n\f\nRFC 3578 ISUP Overlap Signalling to SIP August 2003 3578 nested-reference unchanged"},{"id":"IETF RFC 4077","type":"specification","body":"IETF","designation":"RFC 4077","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4077.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4077.txt","https://www.rfc-editor.org/rfc/rfc4077.pdf"],"folder":"IETF/RFC-4077","files":{"txt":{"path":"standards/IETF/RFC-4077/RFC-4077.txt","sha256":"6100fdaa0d4729a0a3d1d1c277c3e32acd852b1539d90a757a6736b2ac8ea356"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a mechanism that allows Signaling Compression\n (SigComp) implementations to report precise error information upon\n receipt of a message which cannot be decompressed. This negative\n feedback can be used by the recipient to make fine-grained\n adjustments to the compressed message before retransmitting it,\n allowing for rapid and efficient recovery from error situations.\n\nRoach Standards Track [Page 1]\n\f\nRFC 4077 SigComp NACK May 2005","scope_keywords":["4077","key","pid","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4896","folder":"IETF/RFC-4896","source":"IETF/RFC-4896/RFC-4896.txt","version":null},{"body":"IETF","designation":"RFC 5049","folder":"IETF/RFC-5049","source":"IETF/RFC-5049/RFC-5049.txt","version":null}],"search_text":"IETF RFC 4077 This document describes a mechanism that allows Signaling Compression\n (SigComp) implementations to report precise error information upon\n receipt of a message which cannot be decompressed. This negative\n feedback can be used by the recipient to make fine-grained\n adjustments to the compressed message before retransmitting it,\n allowing for rapid and efficient recovery from error situations.\n\nRoach Standards Track [Page 1]\n\f\nRFC 4077 SigComp NACK May 2005 4077 key pid tls nested-reference unchanged"},{"id":"IETF RFC 4320","type":"specification","body":"IETF","designation":"RFC 4320","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4320.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4320.txt","https://www.rfc-editor.org/rfc/rfc4320.pdf"],"folder":"IETF/RFC-4320","files":{"txt":{"path":"standards/IETF/RFC-4320/RFC-4320.txt","sha256":"9ac366f57e354d352877743cffe9e5a5155c5ff3293b33f83d27c8c69b3b57c9"}},"tags":["nested-reference","unchanged"],"summary":"This document describes modifications to the Session Initiation\n Protocol (SIP) to address problems that have been identified with the\n SIP non-INVITE transaction. These modifications reduce the\n probability of messages losing the race condition inherent in the\n non-INVITE transaction and reduce useless network traffic. They also\n improve the robustness of SIP networks when elements stop responding.\n These changes update behavior defined in RFC 3261.","scope_keywords":["4320","pid","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4321","folder":"IETF/RFC-4321","source":"IETF/RFC-4321/RFC-4321.txt","version":null},{"body":"IETF","designation":"RFC 6141","folder":"IETF/RFC-6141","source":"IETF/RFC-6141/RFC-6141.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null}],"search_text":"IETF RFC 4320 This document describes modifications to the Session Initiation\n Protocol (SIP) to address problems that have been identified with the\n SIP non-INVITE transaction. These modifications reduce the\n probability of messages losing the race condition inherent in the\n non-INVITE transaction and reduce useless network traffic. They also\n improve the robustness of SIP networks when elements stop responding.\n These changes update behavior defined in RFC 3261. 4320 pid policy risk nested-reference unchanged"},{"id":"IETF RFC 4353","type":"specification","body":"IETF","designation":"RFC 4353","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4353.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4353.txt","https://www.rfc-editor.org/rfc/rfc4353.pdf"],"folder":"IETF/RFC-4353","files":{"txt":{"path":"standards/IETF/RFC-4353/RFC-4353.txt","sha256":"634fe864ec6f6315cad9a6cf1d450e8d30317b0094cfef5934f7c6043e6d07f2"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) supports the initiation,\n modification, and termination of media sessions between user agents.\n These sessions are managed by SIP dialogs, which represent a SIP\n relationship between a pair of user agents. Because dialogs are\n between pairs of user agents, SIP's usage for two-party\n communications (such as a phone call), is obvious. Communications\n sessions with multiple participants, generally known as conferencing,\n are more complicated. This document defines a framework for how such\n conferencing can occur. This framework describes the overall\n architecture, terminology, and protocol components needed for multi-\n party conferencing.","scope_keywords":["4353","policies","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4376","folder":"IETF/RFC-4376","source":"IETF/RFC-4376/RFC-4376.txt","version":null},{"body":"IETF","designation":"RFC 4538","folder":"IETF/RFC-4538","source":"IETF/RFC-4538/RFC-4538.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4579","folder":"IETF/RFC-4579","source":"IETF/RFC-4579/RFC-4579.txt","version":null},{"body":"IETF","designation":"RFC 4597","folder":"IETF/RFC-4597","source":"IETF/RFC-4597/RFC-4597.txt","version":null},{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null},{"body":"IETF","designation":"RFC 4964","folder":"IETF/RFC-4964","source":"IETF/RFC-4964/RFC-4964.txt","version":null},{"body":"IETF","designation":"RFC 5167","folder":"IETF/RFC-5167","source":"IETF/RFC-5167/RFC-5167.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 5366","folder":"IETF/RFC-5366","source":"IETF/RFC-5366/RFC-5366.txt","version":null},{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 7656","folder":"IETF/RFC-7656","source":"IETF/RFC-7656/RFC-7656.txt","version":null},{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null}],"search_text":"IETF RFC 4353 The Session Initiation Protocol (SIP) supports the initiation,\n modification, and termination of media sessions between user agents.\n These sessions are managed by SIP dialogs, which represent a SIP\n relationship between a pair of user agents. Because dialogs are\n between pairs of user agents, SIP's usage for two-party\n communications (such as a phone call), is obvious. Communications\n sessions with multiple participants, generally known as conferencing,\n are more complicated. This document defines a framework for how such\n conferencing can occur. This framework describes the overall\n architecture, terminology, and protocol components needed for multi-\n party conferencing. 4353 policies policy nested-reference unchanged"},{"id":"IETF RFC 4453","type":"specification","body":"IETF","designation":"RFC 4453","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4453.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4453.txt","https://www.rfc-editor.org/rfc/rfc4453.pdf"],"folder":"IETF/RFC-4453","files":{"txt":{"path":"standards/IETF/RFC-4453/RFC-4453.txt","sha256":"1167df0f94a604233eb69ee644c49b426c058424165dd2cce5ebcc239fb2cb53"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) supports communications across\n many media types, including real-time audio, video, text, instant\n messaging, and presence. In its current form, it allows session\n invitations, instant messages, and other requests to be delivered\n from one party to another without requiring explicit consent of the\n recipient. Without such consent, it is possible for SIP to be used\n for malicious purposes, including spam and denial-of-service attacks.\n This document identifies a set of requirements for extensions to SIP\n that add consent-based communications.","scope_keywords":["4453","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5363","folder":"IETF/RFC-5363","source":"IETF/RFC-5363/RFC-5363.txt","version":null}],"search_text":"IETF RFC 4453 The Session Initiation Protocol (SIP) supports communications across\n many media types, including real-time audio, video, text, instant\n messaging, and presence. In its current form, it allows session\n invitations, instant messages, and other requests to be delivered\n from one party to another without requiring explicit consent of the\n recipient. Without such consent, it is possible for SIP to be used\n for malicious purposes, including spam and denial-of-service attacks.\n This document identifies a set of requirements for extensions to SIP\n that add consent-based communications. 4453 subject nested-reference unchanged"},{"id":"IETF RFC 4458","type":"specification","body":"IETF","designation":"RFC 4458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4458.txt","https://www.rfc-editor.org/rfc/rfc4458.pdf"],"folder":"IETF/RFC-4458","files":{"txt":{"path":"standards/IETF/RFC-4458/RFC-4458.txt","sha256":"d74f4ca1b2a290cde5c10739baf481a3fd9b221b2f93d7a621f097dbc1f97eaa"}},"tags":["nested-reference","unchanged"],"summary":"The Session Initiation Protocol (SIP) is often used to initiate\n connections to applications such as voicemail or interactive voice\n recognition systems. This specification describes a convention for\n forming SIP service URIs that request particular services based on\n redirecting targets from such applications.\n\nJennings, et al. Informational [Page 1]\n\f\nRFC 4458 SIP Voicemail URI April 2006","scope_keywords":["4458"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null}],"search_text":"IETF RFC 4458 The Session Initiation Protocol (SIP) is often used to initiate\n connections to applications such as voicemail or interactive voice\n recognition systems. This specification describes a convention for\n forming SIP service URIs that request particular services based on\n redirecting targets from such applications.\n\nJennings, et al. Informational [Page 1]\n\f\nRFC 4458 SIP Voicemail URI April 2006 4458 nested-reference unchanged"},{"id":"IETF RFC 5057","type":"specification","body":"IETF","designation":"RFC 5057","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5057.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5057.txt","https://www.rfc-editor.org/rfc/rfc5057.pdf"],"folder":"IETF/RFC-5057","files":{"txt":{"path":"standards/IETF/RFC-5057/RFC-5057.txt","sha256":"75a3fb2098c7c2f3fb027b86702b0ab197cd63f5751c6e77df15996f70ea0790"}},"tags":["nested-reference","unchanged"],"summary":"Several methods in the Session Initiation Protocol (SIP) can create\n an association between endpoints known as a dialog. Some of these\n methods can also create a different, but related, association within\n an existing dialog. These multiple associations, or dialog usages,\n require carefully coordinated processing as they have independent\n life-cycles, but share common dialog state. Processing multiple\n dialog usages correctly is not completely understood. What is\n understood is difficult to implement.\n\n This memo argues that multiple dialog usages should be avoided. It\n discusses alternatives to their use and clarifies essential behavior\n for elements that cannot currently avoid them.\n\n This is an informative document and makes no normative statements of\n any kind.\n\nSparks Informational [Page 1]\n\f\nRFC 5057 Multiple Dialog Usages November 2007","scope_keywords":["5057","authentication","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5589","folder":"IETF/RFC-5589","source":"IETF/RFC-5589/RFC-5589.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null}],"search_text":"IETF RFC 5057 Several methods in the Session Initiation Protocol (SIP) can create\n an association between endpoints known as a dialog. Some of these\n methods can also create a different, but related, association within\n an existing dialog. These multiple associations, or dialog usages,\n require carefully coordinated processing as they have independent\n life-cycles, but share common dialog state. Processing multiple\n dialog usages correctly is not completely understood. What is\n understood is difficult to implement.\n\n This memo argues that multiple dialog usages should be avoided. It\n discusses alternatives to their use and clarifies essential behavior\n for elements that cannot currently avoid them.\n\n This is an informative document and makes no normative statements of\n any kind.\n\nSparks Informational [Page 1]\n\f\nRFC 5057 Multiple Dialog Usages November 2007 5057 authentication key management nested-reference unchanged"},{"id":"IETF RFC 5167","type":"specification","body":"IETF","designation":"RFC 5167","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5167.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5167.txt","https://www.rfc-editor.org/rfc/rfc5167.pdf"],"folder":"IETF/RFC-5167","files":{"txt":{"path":"standards/IETF/RFC-5167/RFC-5167.txt","sha256":"dec43c87fae17aa3c5087a0fcb0714b6cf924c9096226e9b358b18ca213e386b"}},"tags":["nested-reference","unchanged"],"summary":"This document addresses the communication between an application\n server and media server. The current work in IETF working groups\n shows these logical entities, but it does not address the physical\n decomposition and the protocol between the entities.\n\n This document presents the requirements for a Media Server Control\n Protocol (MCP) that enables an application server to use a media\n server. It will address the aspects of announcements, Interactive\n Voice Response, and conferencing media services.","scope_keywords":["5167","algorithm","algorithms","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null}],"search_text":"IETF RFC 5167 This document addresses the communication between an application\n server and media server. The current work in IETF working groups\n shows these logical entities, but it does not address the physical\n decomposition and the protocol between the entities.\n\n This document presents the requirements for a Media Server Control\n Protocol (MCP) that enables an application server to use a media\n server. It will address the aspects of announcements, Interactive\n Voice Response, and conferencing media services. 5167 algorithm algorithms policy nested-reference unchanged"},{"id":"IETF RFC 5359","type":"specification","body":"IETF","designation":"RFC 5359","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5359.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5359.txt","https://www.rfc-editor.org/rfc/rfc5359.pdf"],"folder":"IETF/RFC-5359","files":{"txt":{"path":"standards/IETF/RFC-5359/RFC-5359.txt","sha256":"10e59f33ad3e7245d7e6af1fd16d50da14bdefb5b92ea68507e75027342bb760"}},"tags":["nested-reference","unchanged"],"summary":"This document gives examples of Session Initiation Protocol (SIP)\n services. This covers most features offered in so-called IP Centrex\n offerings from local exchange carriers and PBX (Private Branch\n Exchange) features. Most of the services shown in this document are\n implemented in the SIP user agents, although some require the\n assistance of a SIP proxy. Some require some extensions to SIP\n including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces\n and Join header fields. These features are not intended to be an\n exhaustive set, but rather show implementations of common features\n likely to be implemented on SIP IP telephones in a business\n environment.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 5359 SIP Service Examples October 2008","scope_keywords":["5359","authentication","certificate","management","tls","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6443","folder":"IETF/RFC-6443","source":"IETF/RFC-6443/RFC-6443.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 7088","folder":"IETF/RFC-7088","source":"IETF/RFC-7088/RFC-7088.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null}],"search_text":"IETF RFC 5359 This document gives examples of Session Initiation Protocol (SIP)\n services. This covers most features offered in so-called IP Centrex\n offerings from local exchange carriers and PBX (Private Branch\n Exchange) features. Most of the services shown in this document are\n implemented in the SIP user agents, although some require the\n assistance of a SIP proxy. Some require some extensions to SIP\n including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces\n and Join header fields. These features are not intended to be an\n exhaustive set, but rather show implementations of common features\n likely to be implemented on SIP IP telephones in a business\n environment.\n\nJohnston, et al. Best Current Practice [Page 1]\n\f\nRFC 5359 SIP Service Examples October 2008 5359 authentication certificate management tls validation nested-reference unchanged"},{"id":"IETF RFC 5853","type":"specification","body":"IETF","designation":"RFC 5853","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5853.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5853.txt","https://www.rfc-editor.org/rfc/rfc5853.pdf"],"folder":"IETF/RFC-5853","files":{"txt":{"path":"standards/IETF/RFC-5853/RFC-5853.txt","sha256":"7dad10f87c5c28151c1c81a5b35b1bb7c5c6a4ee3aed509fecd20ac92a1cea00"}},"tags":["nested-reference","unchanged"],"summary":"This document describes functions implemented in Session Initiation\n Protocol (SIP) intermediaries known as Session Border Controllers\n (SBCs). The goal of this document is to describe the commonly\n provided functions of SBCs. A special focus is given to those\n practices that are viewed to be in conflict with SIP architectural\n principles. This document also explores the underlying requirements\n of network operators that have led to the use of these functions and\n practices in order to identify protocol requirements and determine\n whether those requirements are satisfied by existing specifications\n or if additional standards work is required.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF ","scope_keywords":["5853","encryption","http","license","management","pid","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null}],"search_text":"IETF RFC 5853 This document describes functions implemented in Session Initiation\n Protocol (SIP) intermediaries known as Session Border Controllers\n (SBCs). The goal of this document is to describe the commonly\n provided functions of SBCs. A special focus is given to those\n practices that are viewed to be in conflict with SIP architectural\n principles. This document also explores the underlying requirements\n of network operators that have led to the use of these functions and\n practices in order to identify protocol requirements and determine\n whether those requirements are satisfied by existing specifications\n or if additional standards work is required.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF  5853 encryption http license management pid policies subject trust nested-reference unchanged"},{"id":"IETF RFC 6504","type":"specification","body":"IETF","designation":"RFC 6504","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6504.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6504.txt","https://www.rfc-editor.org/rfc/rfc6504.pdf"],"folder":"IETF/RFC-6504","files":{"txt":{"path":"standards/IETF/RFC-6504/RFC-6504.txt","sha256":"5d964cddb52373929489c25d37bcb5f49a918bb4be6c9ed49df6ad5528352b18"}},"tags":["nested-reference","unchanged"],"summary":"This document provides detailed call flows for the scenarios\n documented in the Framework for Centralized Conferencing (XCON) (RFC\n 5239) and in the XCON scenarios (RFC 4597). The call flows document\n the use of the interface between a conference control client and a\n conference control server using the Centralized Conferencing\n Manipulation Protocol (CCMP) (RFC 6503). The objective is to provide\n detailed examples for reference by both protocol researchers and\n developers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG ","scope_keywords":["6504","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null}],"search_text":"IETF RFC 6504 This document provides detailed call flows for the scenarios\n documented in the Framework for Centralized Conferencing (XCON) (RFC\n 5239) and in the XCON scenarios (RFC 4597). The call flows document\n the use of the interface between a conference control client and a\n conference control server using the Centralized Conferencing\n Manipulation Protocol (CCMP) (RFC 6503). The objective is to provide\n detailed examples for reference by both protocol researchers and\n developers.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG  6504 http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7092","type":"specification","body":"IETF","designation":"RFC 7092","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7092.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7092.txt","https://www.rfc-editor.org/rfc/rfc7092.pdf"],"folder":"IETF/RFC-7092","files":{"txt":{"path":"standards/IETF/RFC-7092/RFC-7092.txt","sha256":"b3c57a6a440dd659e8c0bc9f1c3a307c3e03d2aae83230fe054a58e9a4f7036e"}},"tags":["nested-reference","unchanged"],"summary":"In many SIP deployments, SIP entities exist in the SIP signaling path\n between the originating and final terminating endpoints, which go\n beyond the definition of a SIP proxy, performing functions not\n defined in Standards Track RFCs. The only term for such devices\n provided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), which\n is defined as the logical concatenation of a SIP User Agent Server\n (UAS) and User Agent Client (UAC).\n\n There are numerous types of SIP B2BUAs performing different roles in\n different ways; for example, IP Private Branch Exchanges (IPBXs),\n Session Border Controllers (SBCs), and Application Servers (ASs).\n This document identifies several common B2BUA roles in order to\n provide taxonomy other documents can use and reference.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n","scope_keywords":["7092","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 8873","folder":"IETF/RFC-8873","source":"IETF/RFC-8873/RFC-8873.txt","version":null}],"search_text":"IETF RFC 7092 In many SIP deployments, SIP entities exist in the SIP signaling path\n between the originating and final terminating endpoints, which go\n beyond the definition of a SIP proxy, performing functions not\n defined in Standards Track RFCs. The only term for such devices\n provided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), which\n is defined as the logical concatenation of a SIP User Agent Server\n (UAS) and User Agent Client (UAC).\n\n There are numerous types of SIP B2BUAs performing different roles in\n different ways; for example, IP Private Branch Exchanges (IPBXs),\n Session Border Controllers (SBCs), and Application Servers (ASs).\n This document identifies several common B2BUA roles in order to\n provide taxonomy other documents can use and reference.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n 7092 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7340","type":"specification","body":"IETF","designation":"RFC 7340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7340.txt","https://www.rfc-editor.org/rfc/rfc7340.pdf"],"folder":"IETF/RFC-7340","files":{"txt":{"path":"standards/IETF/RFC-7340/RFC-7340.txt","sha256":"f4b204b12555487f312625c4246e89d3ff169854c2031a8ceca0cf7602b814b5"}},"tags":["nested-reference","unchanged"],"summary":"Over the past decade, Voice over IP (VoIP) systems based on SIP have\n replaced many traditional telephony deployments. Interworking VoIP\n systems with the traditional telephone network has reduced the\n overall level of calling party number and Caller ID assurances by\n granting attackers new and inexpensive tools to impersonate or\n obscure calling party numbers when orchestrating bulk commercial\n calling schemes, hacking voicemail boxes, or even circumventing\n multi-factor authentication systems trusted by banks. Despite\n previous attempts to provide a secure assurance of the origin of SIP\n communications, we still lack effective standards for identifying the\n calling party in a VoIP session. This document examines the reasons\n why providing identity for telephone numbers on the Internet has\n proven so difficult and shows how changes in the last decade may\n provide us with new strategies ","scope_keywords":["7340","authentication","authorization","certificate","http","identification","key","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7375","folder":"IETF/RFC-7375","source":"IETF/RFC-7375/RFC-7375.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null}],"search_text":"IETF RFC 7340 Over the past decade, Voice over IP (VoIP) systems based on SIP have\n replaced many traditional telephony deployments. Interworking VoIP\n systems with the traditional telephone network has reduced the\n overall level of calling party number and Caller ID assurances by\n granting attackers new and inexpensive tools to impersonate or\n obscure calling party numbers when orchestrating bulk commercial\n calling schemes, hacking voicemail boxes, or even circumventing\n multi-factor authentication systems trusted by banks. Despite\n previous attempts to provide a secure assurance of the origin of SIP\n communications, we still lack effective standards for identifying the\n calling party in a VoIP session. This document examines the reasons\n why providing identity for telephone numbers on the Internet has\n proven so difficult and shows how changes in the last decade may\n provide us with new strategies  7340 authentication authorization certificate http identification key license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7362","type":"specification","body":"IETF","designation":"RFC 7362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7362.txt","https://www.rfc-editor.org/rfc/rfc7362.pdf"],"folder":"IETF/RFC-7362","files":{"txt":{"path":"standards/IETF/RFC-7362/RFC-7362.txt","sha256":"89be2c7dfe70064ff804da085ee78c66ad2a7d6c3adebe1809e686d63b693604"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the behavior of signaling intermediaries in\n Real-Time Communication (RTC) deployments, sometimes referred to as\n Session Border Controllers (SBCs), when performing Hosted NAT\n Traversal (HNT). HNT is a set of mechanisms, such as media relaying\n and latching, that such intermediaries use to enable other RTC\n devices behind NATs to communicate with each other.\n\n This document is non-normative and is only written to explain HNT in\n order to provide a reference to the Internet community and an\n informative description to manufacturers and users.\n\n Latching, which is one of the HNT components, has a number of\n security issues covered here. Because of those, and unless all\n security considerations explained here are taken into account and\n solved, the IETF advises against use of the latching mechanism over\n the Internet and recommends other solutions, such as the Inter","scope_keywords":["7362","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null}],"search_text":"IETF RFC 7362 This document describes the behavior of signaling intermediaries in\n Real-Time Communication (RTC) deployments, sometimes referred to as\n Session Border Controllers (SBCs), when performing Hosted NAT\n Traversal (HNT). HNT is a set of mechanisms, such as media relaying\n and latching, that such intermediaries use to enable other RTC\n devices behind NATs to communicate with each other.\n\n This document is non-normative and is only written to explain HNT in\n order to provide a reference to the Internet community and an\n informative description to manufacturers and users.\n\n Latching, which is one of the HNT components, has a number of\n security issues covered here. Because of those, and unless all\n security considerations explained here are taken into account and\n solved, the IETF advises against use of the latching mechanism over\n the Internet and recommends other solutions, such as the Inter 7362 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7375","type":"specification","body":"IETF","designation":"RFC 7375","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7375.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7375.txt","https://www.rfc-editor.org/rfc/rfc7375.pdf"],"folder":"IETF/RFC-7375","files":{"txt":{"path":"standards/IETF/RFC-7375/RFC-7375.txt","sha256":"1ecec74c9b3b78fad8959b39ccc519f0d1c925d3ef7a65fcdd9cf129cf1d026d"}},"tags":["nested-reference","unchanged"],"summary":"As the Internet and the telephone network have become increasingly\n interconnected and interdependent, attackers can impersonate or\n obscure calling party numbers when orchestrating bulk commercial\n calling schemes, hacking voicemail boxes, or even circumventing\n multi-factor authentication systems trusted by banks. This document\n analyzes threats in the resulting system, enumerating actors,\n reviewing the capabilities available to and used by attackers, and\n describing scenarios in which attacks are launched.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not","scope_keywords":["7375","authentication","http","license","path","policies","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null}],"search_text":"IETF RFC 7375 As the Internet and the telephone network have become increasingly\n interconnected and interdependent, attackers can impersonate or\n obscure calling party numbers when orchestrating bulk commercial\n calling schemes, hacking voicemail boxes, or even circumventing\n multi-factor authentication systems trusted by banks. This document\n analyzes threats in the resulting system, enumerating actors,\n reviewing the capabilities available to and used by attackers, and\n describing scenarios in which attacks are launched.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not 7375 authentication http license path policies presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7687","type":"specification","body":"IETF","designation":"RFC 7687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7687.txt","https://www.rfc-editor.org/rfc/rfc7687.pdf"],"folder":"IETF/RFC-7687","files":{"txt":{"path":"standards/IETF/RFC-7687/RFC-7687.txt","sha256":"8f548599a53f816224bcbe040bf4136259e97b6818f6236f8a5cec2447c0992d"}},"tags":["nested-reference","unchanged"],"summary":"The Strengthening the Internet (STRINT) workshop assembled one\n hundred participants in London for two days in early 2014 to discuss\n how the technical community, and in particular the IETF and the W3C,\n should react to Pervasive Monitoring and more generally how to\n strengthen the Internet in the face of such attacks. The discussions\n covered issues of terminology, the role of user interfaces, classes\n of mitigation, some specific use cases, transition strategies\n (including opportunistic encryption), and more. The workshop ended\n with a few high-level recommendations, that it is believed could be\n implemented and could help strengthen the Internet. This is the\n report of that workshop.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n vi","scope_keywords":["7687","encryption","http","https","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8165","folder":"IETF/RFC-8165","source":"IETF/RFC-8165/RFC-8165.txt","version":null}],"search_text":"IETF RFC 7687 The Strengthening the Internet (STRINT) workshop assembled one\n hundred participants in London for two days in early 2014 to discuss\n how the technical community, and in particular the IETF and the W3C,\n should react to Pervasive Monitoring and more generally how to\n strengthen the Internet in the face of such attacks. The discussions\n covered issues of terminology, the role of user interfaces, classes\n of mitigation, some specific use cases, transition strategies\n (including opportunistic encryption), and more. The workshop ended\n with a few high-level recommendations, that it is believed could be\n implemented and could help strengthen the Internet. This is the\n report of that workshop.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n vi 7687 encryption http https license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7027","type":"specification","body":"IETF","designation":"RFC 7027","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7027.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7027.txt","https://www.rfc-editor.org/rfc/rfc7027.pdf"],"folder":"IETF/RFC-7027","files":{"txt":{"path":"standards/IETF/RFC-7027/RFC-7027.txt","sha256":"28aaaff85a4d52b426194839b222e314fa6476ec75d7fa70427724710696a1f5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the use of several Elliptic Curve\n Cryptography (ECC) Brainpool curves for authentication and key\n exchange in the Transport Layer Security (TLS) protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7027.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and t","scope_keywords":["7027","algorithm","algorithms","authentication","certificate","certificates","encryption","hash","http","key","keys","license","signature","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7919","folder":"IETF/RFC-7919","source":"IETF/RFC-7919/RFC-7919.txt","version":null}],"search_text":"IETF RFC 7027 This document specifies the use of several Elliptic Curve\n Cryptography (ECC) Brainpool curves for authentication and key\n exchange in the Transport Layer Security (TLS) protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7027.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and t 7027 algorithm algorithms authentication certificate certificates encryption hash http key keys license signature subject tls trust nested-reference unchanged"},{"id":"IETF RFC 328","type":"specification","body":"IETF","designation":"RFC 328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc328.txt","https://www.rfc-editor.org/rfc/rfc328.pdf"],"folder":"IETF/RFC-328","files":{"txt":{"path":"standards/IETF/RFC-328/RFC-328.txt","sha256":"91d3a9865a84a51dbddcbc242cd8fea160e2b5d3b6aaa69b58b29835b5236d9b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 328 Computer Science\n UCLA-NMC\nNIC 9635 29 April 72\nCategories: Telnet\nReferences: RFC 328\n\n Suggested Telnet Protocol Changes\n\n I hereby propose the following changes to the Telnet protocol. If\nno substantial negative response is received by 15 May 72 it will be\nassumed that these changes are desired and should be incorporated in\nany \"Official Telnet Protocol\".\n\n First I suggest that we drop the idea of a \"minimum\"\nimplementation and require a standard implementation which includes all\naspects of the protocol.\n\n Second I suggest that we eliminate the DATA TYPE signals.\n\n Third I suggest that we do away with HIDE YOUR INPUT signal.\n\nArguments:\n\n Standard Implementation:\n The idea of an accepted implementation which does not include\n whole protocol is an admission that the parts of the\n protocol left out are either not useful or not e","scope_keywords":["328"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 4576","folder":"IETF/RFC-4576","source":"IETF/RFC-4576/RFC-4576.txt","version":null}],"search_text":"IETF RFC 328 Network Working Group Jon Postel\nRequest for Comments: 328 Computer Science\n UCLA-NMC\nNIC 9635 29 April 72\nCategories: Telnet\nReferences: RFC 328\n\n Suggested Telnet Protocol Changes\n\n I hereby propose the following changes to the Telnet protocol. If\nno substantial negative response is received by 15 May 72 it will be\nassumed that these changes are desired and should be incorporated in\nany \"Official Telnet Protocol\".\n\n First I suggest that we drop the idea of a \"minimum\"\nimplementation and require a standard implementation which includes all\naspects of the protocol.\n\n Second I suggest that we eliminate the DATA TYPE signals.\n\n Third I suggest that we do away with HIDE YOUR INPUT signal.\n\nArguments:\n\n Standard Implementation:\n The idea of an accepted implementation which does not include\n whole protocol is an admission that the parts of the\n protocol left out are either not useful or not e 328 nested-reference unchanged"},{"id":"IETF RFC 4534","type":"specification","body":"IETF","designation":"RFC 4534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4534.txt","https://www.rfc-editor.org/rfc/rfc4534.pdf"],"folder":"IETF/RFC-4534","files":{"txt":{"path":"standards/IETF/RFC-4534/RFC-4534.txt","sha256":"a23a3dfc0e8589b45e4cf231918746e3faede87f068db294e19ef9caf2fc4363"}},"tags":["nested-reference","unchanged"],"summary":"The Group Security Policy Token is a structure used to specify the\n security policy and configurable parameters for a cryptographic\n group, such as a secure multicast group. Because the security of a\n group is composed of the totality of multiple security services,\n mechanisms, and attributes throughout the communications\n infrastructure, an authenticatable representation of the features\n that must be supported throughout the system is needed to ensure\n consistent security. This document specifies the structure of such a\n token.\n\nColegrove & Harney Standards Track [Page 1]\n\f\nRFC 4534 Group Security Policy Token v1 June 2006","scope_keywords":["4534","attribute","attributes","authorization","key","policy","presentation","trust","verifiable"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null}],"search_text":"IETF RFC 4534 The Group Security Policy Token is a structure used to specify the\n security policy and configurable parameters for a cryptographic\n group, such as a secure multicast group. Because the security of a\n group is composed of the totality of multiple security services,\n mechanisms, and attributes throughout the communications\n infrastructure, an authenticatable representation of the features\n that must be supported throughout the system is needed to ensure\n consistent security. This document specifies the structure of such a\n token.\n\nColegrove & Harney Standards Track [Page 1]\n\f\nRFC 4534 Group Security Policy Token v1 June 2006 4534 attribute attributes authorization key policy presentation trust verifiable nested-reference unchanged"},{"id":"IETF RFC 329","type":"specification","body":"IETF","designation":"RFC 329","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc329.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc329.txt","https://www.rfc-editor.org/rfc/rfc329.pdf"],"folder":"IETF/RFC-329","files":{"txt":{"path":"standards/IETF/RFC-329/RFC-329.txt","sha256":"a0b4182970a9ad0bc18748c81ada3dbb530b30899d4b6d606420c0560ab39e06"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Network Information Center\nRequest for Comments: 329 Stanford Research Institute\nObsoletes: 303 17 May 1972\nNIC: 9636\n\n ARPA NETWORK MAILING LISTS\n\nABSTRACT\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\nA. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n document","scope_keywords":["329"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 363","folder":"IETF/RFC-363","source":"IETF/RFC-363/RFC-363.txt","version":null}],"search_text":"IETF RFC 329 Network Working Group Network Information Center\nRequest for Comments: 329 Stanford Research Institute\nObsoletes: 303 17 May 1972\nNIC: 9636\n\n ARPA NETWORK MAILING LISTS\n\nABSTRACT\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\nA. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other formal\n document 329 nested-reference unchanged"},{"id":"IETF RFC 363","type":"specification","body":"IETF","designation":"RFC 363","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc363.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc363.txt","https://www.rfc-editor.org/rfc/rfc363.pdf"],"folder":"IETF/RFC-363","files":{"txt":{"path":"standards/IETF/RFC-363/RFC-363.txt","sha256":"65311e2ef26e3ed657dcd37ba93f20a7e35c1246f8e64dd6cab396369bddbfee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Network Information Center\nRequest for Comments: 363 Stanford Research Institute\nObsoletes: RFC 329, NIC 9636 8 August 1972\nNIC: 10605\n\n ARPA NETWORK MAILING LISTS\n\nABSTRACT\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\nA. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other","scope_keywords":["363"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 363 Network Working Group Network Information Center\nRequest for Comments: 363 Stanford Research Institute\nObsoletes: RFC 329, NIC 9636 8 August 1972\nNIC: 10605\n\n ARPA NETWORK MAILING LISTS\n\nABSTRACT\n\n The following are three lists to be used for distribution of Network\n documents. List A should be used by sites when they distribute their\n own documents, to get RFC's to Liaisons as quickly as possible. All\n but local mail should be sent Air Mail. Lists B and C will be used\n by NIC in making distribution of copies to non-site Network\n Participants and to Station Agents.\n\n For phone numbers and lists of names by sites see the Current\n Directory of Network Participants.\n\nA. INITIAL DISTRIBUTION LIST\n\n Note: This list includes all Network Liaisons and others who should\n receive initial distribution of RFC's, whether sent from NIC or from\n sites. They will also receive selected catalogs and other 363 nested-reference unchanged"},{"id":"IETF RFC 3292","type":"specification","body":"IETF","designation":"RFC 3292","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3292.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3292.txt","https://www.rfc-editor.org/rfc/rfc3292.pdf"],"folder":"IETF/RFC-3292","files":{"txt":{"path":"standards/IETF/RFC-3292/RFC-3292.txt","sha256":"e532bbbfdfae187b3dd99ff246b2e3e6c9d7f614651f460d468376981643fc21"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the General Switch Management Protocol\n Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows\n one or more external switch controllers to establish and maintain the\n state of a label switch such as, an ATM, frame relay or MPLS switch.\n The GSMPv3 allows control of both unicast and multicast switch\n connection state as well as control of switch system resources and\n QoS features.\n\nAcknowledgement\n\n GSMP was created by P. Newman, W. Edwards, R. Hinden, E. Hoffman, F.\n Ching Liaw, T. Lyon, and G. Minshall (see [6] and [7]). This version\n of GSMP is based on their work.\n\nContributors\n\n In addition to the authors/editors listed in the heading, many\n members of the GSMP group have made significant contributions to this\n specification. Among the contributors who have contributed\n materially are: Constantin Adam, Clint Bishard, Joachim Buerkle,\n Torbjorn He","scope_keywords":["3292","crl","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null}],"search_text":"IETF RFC 3292 This document describes the General Switch Management Protocol\n Version 3 (GSMPv3). The GSMPv3 is an asymmetric protocol that allows\n one or more external switch controllers to establish and maintain the\n state of a label switch such as, an ATM, frame relay or MPLS switch.\n The GSMPv3 allows control of both unicast and multicast switch\n connection state as well as control of switch system resources and\n QoS features.\n\nAcknowledgement\n\n GSMP was created by P. Newman, W. Edwards, R. Hinden, E. Hoffman, F.\n Ching Liaw, T. Lyon, and G. Minshall (see [6] and [7]). This version\n of GSMP is based on their work.\n\nContributors\n\n In addition to the authors/editors listed in the heading, many\n members of the GSMP group have made significant contributions to this\n specification. Among the contributors who have contributed\n materially are: Constantin Adam, Clint Bishard, Joachim Buerkle,\n Torbjorn He 3292 crl key management nested-reference unchanged"},{"id":"IETF RFC 330","type":"specification","body":"IETF","designation":"RFC 330","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc330.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc330.txt","https://www.rfc-editor.org/rfc/rfc330.pdf"],"folder":"IETF/RFC-330","files":{"txt":{"path":"standards/IETF/RFC-330/RFC-330.txt","sha256":"b1863c80393c84efc4a4ed8049e77e7f6c9a944dde70a4f540e2e9265cb42a32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC #9923 BBN\nRFC #330 13 April 1972\nCategories: F, G.3\nUpdates: RFC #326\nObsoletes: None\n\n NETWORK HOST STATUS\n\nThis RFC reports on the status of most Network Hosts from March 27 to\nApril 7. During this interval the PDP-10 at Ames which acts as a\nfront-end to the Illiac (Network address 15) became a server.\nHowever, this Host will not be available to general use for several\nmonths. Also a Terminal IMP was installed at the University of\nSouthern California (Network Address 23) on March 29.\n\nSeveral Hosts are currently excluded from the daily testing. These\nHost fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n","scope_keywords":["330"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 330 Network Working Group Ellen Westheimer\nNIC #9923 BBN\nRFC #330 13 April 1972\nCategories: F, G.3\nUpdates: RFC #326\nObsoletes: None\n\n NETWORK HOST STATUS\n\nThis RFC reports on the status of most Network Hosts from March 27 to\nApril 7. During this interval the PDP-10 at Ames which acts as a\nfront-end to the Illiac (Network address 15) became a server.\nHowever, this Host will not be available to general use for several\nmonths. Also a Terminal IMP was installed at the University of\nSouthern California (Network Address 23) on March 29.\n\nSeveral Hosts are currently excluded from the daily testing. These\nHost fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n 330 nested-reference unchanged"},{"id":"IETF RFC 331","type":"specification","body":"IETF","designation":"RFC 331","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc331.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc331.txt","https://www.rfc-editor.org/rfc/rfc331.pdf"],"folder":"IETF/RFC-331","files":{"txt":{"path":"standards/IETF/RFC-331/RFC-331.txt","sha256":"aeacd63b5aa48ebdd33bf2b0d0d55f2c70e0af62ee8973ffebf3f8d393c0ce9f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. McQuillan\nRFC #331 BBN-NET\nNIC #9924 19 April 1972\nCategory: B.1\n\n IMP System Change Notification\n\n We are planning to release IMPSYS 2600 on May 15, 1972, be- tween\n12 noon and 3 p.m. E.D.T. As discussed at the March 16 seminar held\nat BBN, this release constitutes a major change to the IMP program.\nBecause of the magnitude of the change, the system will be released on\nan experimental basis. If problems develop, then the current system,\nIMPSYS 2514, will be reloaded and the cutover for IMPSYS 2600 will be\nrescheduled for some later time.\n\n The actual transfer over to IMPSYS 2600 will require assis- tance\nfrom site personnel, and we hereby request this assistance. A new\ntape of IMPLOD 2600 will be mailed to all sites shortly, and the staff\nat BBN will request each site in turn on May 15 to load the new IMPLOD\ntape and will detail other procedures to follow therea","scope_keywords":["331"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 331 Network Working Group J. McQuillan\nRFC #331 BBN-NET\nNIC #9924 19 April 1972\nCategory: B.1\n\n IMP System Change Notification\n\n We are planning to release IMPSYS 2600 on May 15, 1972, be- tween\n12 noon and 3 p.m. E.D.T. As discussed at the March 16 seminar held\nat BBN, this release constitutes a major change to the IMP program.\nBecause of the magnitude of the change, the system will be released on\nan experimental basis. If problems develop, then the current system,\nIMPSYS 2514, will be reloaded and the cutover for IMPSYS 2600 will be\nrescheduled for some later time.\n\n The actual transfer over to IMPSYS 2600 will require assis- tance\nfrom site personnel, and we hereby request this assistance. A new\ntape of IMPLOD 2600 will be mailed to all sites shortly, and the staff\nat BBN will request each site in turn on May 15 to load the new IMPLOD\ntape and will detail other procedures to follow therea 331 nested-reference unchanged"},{"id":"IETF RFC 7113","type":"specification","body":"IETF","designation":"RFC 7113","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7113.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7113.txt","https://www.rfc-editor.org/rfc/rfc7113.pdf"],"folder":"IETF/RFC-7113","files":{"txt":{"path":"standards/IETF/RFC-7113/RFC-7113.txt","sha256":"ce21dc999874c1c4eddc5aa2ff1002ff0114344e0a4f255882d740b27bbc5d33"}},"tags":["nested-reference","unchanged"],"summary":"The IPv6 Router Advertisement Guard (RA-Guard) mechanism is commonly\n employed to mitigate attack vectors based on forged ICMPv6 Router\n Advertisement messages. Many existing IPv6 deployments rely on\n RA-Guard as the first line of defense against the aforementioned\n attack vectors. However, some implementations of RA-Guard have been\n found to be prone to circumvention by employing IPv6 Extension\n Headers. This document describes the evasion techniques that affect\n the aforementioned implementations and formally updates RFC 6105,\n such that the aforementioned RA-Guard evasion vectors are eliminated.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and","scope_keywords":["7113","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null}],"search_text":"IETF RFC 7113 The IPv6 Router Advertisement Guard (RA-Guard) mechanism is commonly\n employed to mitigate attack vectors based on forged ICMPv6 Router\n Advertisement messages. Many existing IPv6 deployments rely on\n RA-Guard as the first line of defense against the aforementioned\n attack vectors. However, some implementations of RA-Guard have been\n found to be prone to circumvention by employing IPv6 Extension\n Headers. This document describes the evasion techniques that affect\n the aforementioned implementations and formally updates RFC 6105,\n such that the aforementioned RA-Guard evasion vectors are eliminated.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and 7113 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 332","type":"specification","body":"IETF","designation":"RFC 332","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc332.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc332.txt","https://www.rfc-editor.org/rfc/rfc332.pdf"],"folder":"IETF/RFC-332","files":{"txt":{"path":"standards/IETF/RFC-332/RFC-332.txt","sha256":"44aa891ef156fc9279f01c6da3b807edb80bc8180fc7d06507c664c644073dd2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC #9925 BBN\nRFC #332 25 April 1972\nCategories: F, G.3\nUpdates: RFC #330\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from April\n10 to April 21. During this interval the IBM 360/44 at the University\nof Southern California (Network Address 23) was connected to the\nNetwork; also, a Terminal IMP was installed in Omaha, Nebraska at\nGlobal Weather Central (Network Address 152) on April 18.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n2) Hosts which are currently intended to be users only. ","scope_keywords":["332"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 332 Network Working Group Ellen Westheimer\nNIC #9925 BBN\nRFC #332 25 April 1972\nCategories: F, G.3\nUpdates: RFC #330\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from April\n10 to April 21. During this interval the IBM 360/44 at the University\nof Southern California (Network Address 23) was connected to the\nNetwork; also, a Terminal IMP was installed in Omaha, Nebraska at\nGlobal Weather Central (Network Address 152) on April 18.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. Included here are:\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n2) Hosts which are currently intended to be users only.  332 nested-reference unchanged"},{"id":"IETF RFC 333","type":"specification","body":"IETF","designation":"RFC 333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc333.txt","https://www.rfc-editor.org/rfc/rfc333.pdf"],"folder":"IETF/RFC-333","files":{"txt":{"path":"standards/IETF/RFC-333/RFC-333.txt","sha256":"9f1c6181729bb5c5160d0f2719828200c41f8321aa960a2666fb56e6a78a120d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bob Bressler\nRequest for Comments: 333 MIT/Dynamic Modeling\nNIC # 9926 Dan Murphy\nCategory: C9 (experimentation) BBN/TENEX\nObsoletes: 62 Dave Walden\nUpdates: none BBN/IMP\n 15 May 1972\n\n A PROPOSED EXPERIMENT WITH A MESSAGE SWITCHING PROTOCOL\n\nCONTENTS\n\n Introduction .................................................. 1\n Some Background ............................................... 2\n References .................................................... 3\n MSP Specification ............................................. 4\n Issue ......................................................... 8\n Message Header ................................................ 10\n Examples ...................................................... 15\n TELNET ........................................................ 16\n The Information Operator ...................................... 16\n Unique Port Numbe","scope_keywords":["333"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0333","folder":"IETF/RFC-0333","source":"IETF/RFC-0333/RFC-0333.txt","version":null},{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null}],"search_text":"IETF RFC 333 Network Working Group Bob Bressler\nRequest for Comments: 333 MIT/Dynamic Modeling\nNIC # 9926 Dan Murphy\nCategory: C9 (experimentation) BBN/TENEX\nObsoletes: 62 Dave Walden\nUpdates: none BBN/IMP\n 15 May 1972\n\n A PROPOSED EXPERIMENT WITH A MESSAGE SWITCHING PROTOCOL\n\nCONTENTS\n\n Introduction .................................................. 1\n Some Background ............................................... 2\n References .................................................... 3\n MSP Specification ............................................. 4\n Issue ......................................................... 8\n Message Header ................................................ 10\n Examples ...................................................... 15\n TELNET ........................................................ 16\n The Information Operator ...................................... 16\n Unique Port Numbe 333 nested-reference unchanged"},{"id":"IETF RFC 3350","type":"specification","body":"IETF","designation":"RFC 3350","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc3350.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3350.txt","https://www.rfc-editor.org/rfc/rfc3350.pdf"],"folder":"IETF/RFC-3350","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3711","folder":"IETF/RFC-3711","source":"IETF/RFC-3711/RFC-3711.txt","version":null}],"search_text":"IETF RFC 3350 nested-reference unavailable"},{"id":"IETF RFC 3678","type":"specification","body":"IETF","designation":"RFC 3678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3678.txt","https://www.rfc-editor.org/rfc/rfc3678.pdf"],"folder":"IETF/RFC-3678","files":{"txt":{"path":"standards/IETF/RFC-3678/RFC-3678.txt","sha256":"c416152eb0cc2036594671280b15f8c490645fc5a90d8ec066eec98526045658"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Group Management Protocol (IGMPv3) for IPv4 and the\n Multicast Listener Discovery (MLDv2) for IPv6 add the capability for\n applications to express source filters on multicast group\n memberships, which allows receiver applications to determine the set\n of senders (sources) from which to accept multicast traffic. This\n capability also simplifies support of one-to-many type multicast\n applications.\n\n This document specifies new socket options and functions to manage\n source filters for IP Multicast group memberships. It also defines\n the socket structures to provide input and output arguments to these\n new application program interfaces (APIs). These extensions are\n designed to provide access to the source filtering features, while\n introducing a minimum of change into the system and providing\n complete compatibility for existing multicast applications.","scope_keywords":["3678","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3810","folder":"IETF/RFC-3810","source":"IETF/RFC-3810/RFC-3810.txt","version":null},{"body":"IETF","designation":"RFC 4038","folder":"IETF/RFC-4038","source":"IETF/RFC-4038/RFC-4038.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4604","folder":"IETF/RFC-4604","source":"IETF/RFC-4604/RFC-4604.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4609","folder":"IETF/RFC-4609","source":"IETF/RFC-4609/RFC-4609.txt","version":null},{"body":"IETF","designation":"RFC 5790","folder":"IETF/RFC-5790","source":"IETF/RFC-5790/RFC-5790.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null}],"search_text":"IETF RFC 3678 The Internet Group Management Protocol (IGMPv3) for IPv4 and the\n Multicast Listener Discovery (MLDv2) for IPv6 add the capability for\n applications to express source filters on multicast group\n memberships, which allows receiver applications to determine the set\n of senders (sources) from which to accept multicast traffic. This\n capability also simplifies support of one-to-many type multicast\n applications.\n\n This document specifies new socket options and functions to manage\n source filters for IP Multicast group memberships. It also defines\n the socket structures to provide input and output arguments to these\n new application program interfaces (APIs). These extensions are\n designed to provide access to the source filtering features, while\n introducing a minimum of change into the system and providing\n complete compatibility for existing multicast applications. 3678 management nested-reference unchanged"},{"id":"IETF RFC 3394","type":"specification","body":"IETF","designation":"RFC 3394","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3394.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3394.txt","https://www.rfc-editor.org/rfc/rfc3394.pdf"],"folder":"IETF/RFC-3394","files":{"txt":{"path":"standards/IETF/RFC-3394/RFC-3394.txt","sha256":"faa400c69c22e5f4a911222dc19c17091931a4b8c0658adc7011163e63b253ff"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this document is to make the Advanced Encryption\n Standard (AES) Key Wrap algorithm conveniently available to the\n Internet community. The United States of America has adopted AES as\n the new encryption standard. The AES Key Wrap algorithm will\n probably be adopted by the USA for encryption of AES keys. The\n authors took most of the text in this document from the draft AES Key\n Wrap posted by NIST.","scope_keywords":["3394","algorithm","algorithms","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3537","folder":"IETF/RFC-3537","source":"IETF/RFC-3537/RFC-3537.txt","version":null},{"body":"IETF","designation":"RFC 3565","folder":"IETF/RFC-3565","source":"IETF/RFC-3565/RFC-3565.txt","version":null},{"body":"IETF","designation":"RFC 3657","folder":"IETF/RFC-3657","source":"IETF/RFC-3657/RFC-3657.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 3853","folder":"IETF/RFC-3853","source":"IETF/RFC-3853/RFC-3853.txt","version":null},{"body":"IETF","designation":"RFC 4010","folder":"IETF/RFC-4010","source":"IETF/RFC-4010/RFC-4010.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 5008","folder":"IETF/RFC-5008","source":"IETF/RFC-5008/RFC-5008.txt","version":null},{"body":"IETF","designation":"RFC 5274","folder":"IETF/RFC-5274","source":"IETF/RFC-5274/RFC-5274.txt","version":null},{"body":"IETF","designation":"RFC 5297","folder":"IETF/RFC-5297","source":"IETF/RFC-5297/RFC-5297.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6318","folder":"IETF/RFC-6318","source":"IETF/RFC-6318/RFC-6318.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 8152","folder":"IETF/RFC-8152","source":"IETF/RFC-8152/RFC-8152.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 9052","folder":"IETF/RFC-9052","source":"IETF/RFC-9052/RFC-9052.txt","version":null},{"body":"IETF","designation":"RFC 9053","folder":"IETF/RFC-9053","source":"IETF/RFC-9053/RFC-9053.txt","version":null}],"search_text":"IETF RFC 3394 The purpose of this document is to make the Advanced Encryption\n Standard (AES) Key Wrap algorithm conveniently available to the\n Internet community. The United States of America has adopted AES as\n the new encryption standard. The AES Key Wrap algorithm will\n probably be adopted by the USA for encryption of AES keys. The\n authors took most of the text in this document from the draft AES Key\n Wrap posted by NIST. 3394 algorithm algorithms encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 5649","type":"specification","body":"IETF","designation":"RFC 5649","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5649.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5649.txt","https://www.rfc-editor.org/rfc/rfc5649.pdf"],"folder":"IETF/RFC-5649","files":{"txt":{"path":"standards/IETF/RFC-5649/RFC-5649.txt","sha256":"5555b0a3a22543985d56c2136c8ad3c5c3bf30835638006d56096b84ffb63a91"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a padding convention for use with the AES Key\n Wrap algorithm specified in RFC 3394. This convention eliminates the\n requirement that the length of the key to be wrapped be a multiple of\n 64 bits, allowing a key of any practical length to be wrapped.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to this do","scope_keywords":["5649","algorithm","encryption","http","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null}],"search_text":"IETF RFC 5649 This document specifies a padding convention for use with the AES Key\n Wrap algorithm specified in RFC 3394. This convention eliminates the\n requirement that the length of the key to be wrapped be a multiple of\n 64 bits, allowing a key of any practical length to be wrapped.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of this document. Please review these documents\n carefully, as they describe your rights and restrictions with respect\n to this do 5649 algorithm encryption http key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 4152","type":"specification","body":"IETF","designation":"RFC 4152","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4152.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4152.txt","https://www.rfc-editor.org/rfc/rfc4152.pdf"],"folder":"IETF/RFC-4152","files":{"txt":{"path":"standards/IETF/RFC-4152/RFC-4152.txt","sha256":"218558f7223cb3e89ea7683f614156b0405585bbe6fe6251541506acd8c6c90a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Name (URN) namespace\n (RFC 3406) for the assignment of the Common Language Equipment\n Identifier (CLEI) code, which is used in messages standardized by\n ANSI. The URN namespace is managed by Telcordia Technologies, Inc.,\n as the maintenance agent for ANSI T1.213. The CLEI code is a\n globally unique, ten-character alphanumeric intelligent code assigned\n by Telcordia Technologies at the request of equipment suppliers. The\n CLEI code identifies communications equipment by specifying product\n type and features. There is a one-to-one relationship between a CLEI\n code and supplier's product ID (the manufacturer's name and the part\n number along with its version number).","scope_keywords":["4152","http","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4133","folder":"IETF/RFC-4133","source":"IETF/RFC-4133/RFC-4133.txt","version":null},{"body":"IETF","designation":"RFC 5031","folder":"IETF/RFC-5031","source":"IETF/RFC-5031/RFC-5031.txt","version":null},{"body":"IETF","designation":"RFC 6933","folder":"IETF/RFC-6933","source":"IETF/RFC-6933/RFC-6933.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"IETF RFC 4152 This document describes a Uniform Resource Name (URN) namespace\n (RFC 3406) for the assignment of the Common Language Equipment\n Identifier (CLEI) code, which is used in messages standardized by\n ANSI. The URN namespace is managed by Telcordia Technologies, Inc.,\n as the maintenance agent for ANSI T1.213. The CLEI code is a\n globally unique, ten-character alphanumeric intelligent code assigned\n by Telcordia Technologies at the request of equipment suppliers. The\n CLEI code identifies communications equipment by specifying product\n type and features. There is a one-to-one relationship between a CLEI\n code and supplier's product ID (the manufacturer's name and the part\n number along with its version number). 4152 http validation nested-reference unchanged"},{"id":"IETF RFC 342","type":"specification","body":"IETF","designation":"RFC 342","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc342.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc342.txt","https://www.rfc-editor.org/rfc/rfc342.pdf"],"folder":"IETF/RFC-342","files":{"txt":{"path":"standards/IETF/RFC-342/RFC-342.txt","sha256":"067aedcc05bf9219b8ddfc46b22b39bd71ee408c6d7931a0643a4c48165b0e68"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC #10421 BBN\nRFC #342 15 May 1972\nCategories: F. G.3\nUpdates: RFC #332\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from April\n 24 to May 5. During this interval the IBM 360/44 at the University\n of Southern California (Network Address 23) became a Network user.\n\n Several Hosts are currently excluded from the daily testing.\n These Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n 2) Hosts which are currently intended to be users only.\n Included here are the Terminal IMPs, which are presently in the\n Network (AMES, MITRE, NBS, ETAC, USC, GWC, and BBN*)","scope_keywords":["342"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 342 Network Working Group Ellen Westheimer\nNIC #10421 BBN\nRFC #342 15 May 1972\nCategories: F. G.3\nUpdates: RFC #332\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from April\n 24 to May 5. During this interval the IBM 360/44 at the University\n of Southern California (Network Address 23) became a Network user.\n\n Several Hosts are currently excluded from the daily testing.\n These Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the Network\n as servers (available for use from other sites) on a regular basis\n for at least two weeks. Included here are:\n\n Network\n Address Site Computer\n ------- ---- --------\n 134 MIT-AI PDP-10\n 13 Case PDP-10\n\n 2) Hosts which are currently intended to be users only.\n Included here are the Terminal IMPs, which are presently in the\n Network (AMES, MITRE, NBS, ETAC, USC, GWC, and BBN*) 342 nested-reference unchanged"},{"id":"IETF RFC 3424","type":"specification","body":"IETF","designation":"RFC 3424","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3424.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3424.txt","https://www.rfc-editor.org/rfc/rfc3424.pdf"],"folder":"IETF/RFC-3424","files":{"txt":{"path":"standards/IETF/RFC-3424/RFC-3424.txt","sha256":"4f7d204f7905798ef5ca8d15efb5baaba8b9a0142fce77521b27509c0e221c60"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Daigle, Ed.\nRequest for Comments: 3424 Internet Architecture Board\nCategory: Informational IAB\n November 2002\n\n IAB Considerations for UNilateral Self-Address Fixing (UNSAF)\n Across Network Address Translation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n As a result of the nature of Network Address Translation (NAT)\n Middleboxes, communicating endpoints that are separated by one or\n more NATs do not know how to refer to themselves using addresses that\n are valid in the addressing realms of their (current and future)\n peers. Various proposals have been made for \"UNilateral Self-Address\n Fixing (UNSAF)\" processes. These are processes whereb","scope_keywords":["3424"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3426","folder":"IETF/RFC-3426","source":"IETF/RFC-3426/RFC-3426.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3581","folder":"IETF/RFC-3581","source":"IETF/RFC-3581/RFC-3581.txt","version":null},{"body":"IETF","designation":"RFC 3605","folder":"IETF/RFC-3605","source":"IETF/RFC-3605/RFC-3605.txt","version":null},{"body":"IETF","designation":"RFC 3947","folder":"IETF/RFC-3947","source":"IETF/RFC-3947/RFC-3947.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3989","folder":"IETF/RFC-3989","source":"IETF/RFC-3989/RFC-3989.txt","version":null},{"body":"IETF","designation":"RFC 4101","folder":"IETF/RFC-4101","source":"IETF/RFC-4101/RFC-4101.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4555","folder":"IETF/RFC-4555","source":"IETF/RFC-4555/RFC-4555.txt","version":null},{"body":"IETF","designation":"RFC 4621","folder":"IETF/RFC-4621","source":"IETF/RFC-4621/RFC-4621.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5189","folder":"IETF/RFC-5189","source":"IETF/RFC-5189/RFC-5189.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5597","folder":"IETF/RFC-5597","source":"IETF/RFC-5597/RFC-5597.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5780","folder":"IETF/RFC-5780","source":"IETF/RFC-5780/RFC-5780.txt","version":null},{"body":"IETF","designation":"RFC 5973","folder":"IETF/RFC-5973","source":"IETF/RFC-5973/RFC-5973.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6296","folder":"IETF/RFC-6296","source":"IETF/RFC-6296/RFC-6296.txt","version":null},{"body":"IETF","designation":"RFC 6886","folder":"IETF/RFC-6886","source":"IETF/RFC-6886/RFC-6886.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 3424 Network Working Group L. Daigle, Ed.\nRequest for Comments: 3424 Internet Architecture Board\nCategory: Informational IAB\n November 2002\n\n IAB Considerations for UNilateral Self-Address Fixing (UNSAF)\n Across Network Address Translation\n\nStatus of this Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The Internet Society (2002). All Rights Reserved.\n\nAbstract\n\n As a result of the nature of Network Address Translation (NAT)\n Middleboxes, communicating endpoints that are separated by one or\n more NATs do not know how to refer to themselves using addresses that\n are valid in the addressing realms of their (current and future)\n peers. Various proposals have been made for \"UNilateral Self-Address\n Fixing (UNSAF)\" processes. These are processes whereb 3424 nested-reference unchanged"},{"id":"IETF RFC 4053","type":"specification","body":"IETF","designation":"RFC 4053","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4053.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4053.txt","https://www.rfc-editor.org/rfc/rfc4053.pdf"],"folder":"IETF/RFC-4053","files":{"txt":{"path":"standards/IETF/RFC-4053/RFC-4053.txt","sha256":"5d5fe7e200d7fab26fa739f603b7d6232ece01525a3f21b4e75952292c5f003b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the procedure for proper handling of incoming\n liaison statements from other standards development organizations\n (SDOs), consortia, and industry fora, and for generating liaison\n statements to be transmitted from IETF to other SDOs, consortia and\n industry fora. This procedure allows IETF to effectively collaborate\n with other organizations in the international standards community.\n\n The IETF expects that liaison statements might come from a variety of\n organizations, and it may choose to respond to many of those. The\n IETF is only obligated to respond if there is an agreed liaison\n relationship, however.\n\nTrowbridge, et al. Best Current Practice [Page 1]\n\f\nRFC 4053 Handling of Liaison Statements April 2005","scope_keywords":["4053"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4691","folder":"IETF/RFC-4691","source":"IETF/RFC-4691/RFC-4691.txt","version":null},{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 4929","folder":"IETF/RFC-4929","source":"IETF/RFC-4929/RFC-4929.txt","version":null}],"search_text":"IETF RFC 4053 This document describes the procedure for proper handling of incoming\n liaison statements from other standards development organizations\n (SDOs), consortia, and industry fora, and for generating liaison\n statements to be transmitted from IETF to other SDOs, consortia and\n industry fora. This procedure allows IETF to effectively collaborate\n with other organizations in the international standards community.\n\n The IETF expects that liaison statements might come from a variety of\n organizations, and it may choose to respond to many of those. The\n IETF is only obligated to respond if there is an agreed liaison\n relationship, however.\n\nTrowbridge, et al. Best Current Practice [Page 1]\n\f\nRFC 4053 Handling of Liaison Statements April 2005 4053 nested-reference unchanged"},{"id":"IETF RFC 343","type":"specification","body":"IETF","designation":"RFC 343","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc343.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc343.txt","https://www.rfc-editor.org/rfc/rfc343.pdf"],"folder":"IETF/RFC-343","files":{"txt":{"path":"standards/IETF/RFC-343/RFC-343.txt","sha256":"c371d613f94a4cf80bd4fd223ad05edf4724c259cddf36601a51278321ba0477"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 343 BBN-NET\nNIC #10422 19 May 1972\nCategory: B.1\nObsoletes: RFC #331\n\n IMP System Change Notification\n\n As most of you probably know, our attempt to release IMPSYS 2600 on\n May 15 (as discussed in RFC #331) was unsuccessful. Briefly, the\n primary reasons for failure (all operational rather than programming\n bugs) were:\n\n 1) The network appears to have grown too large for us to\n successfully coordinate operator intervention at all sites.\n\n 2) An unanticipated aspect of the gradual release of the new\n system was the \"poisoning\" of IMP's running the new system by\n adjacent IMP's running the old system, and vice versa. Working\n around this problem made the dissemination of the new system\n take much longer than anticipated.\n\n We believe we see solutions to both of these problems and are now\n ready to schedule the next attempt(s) to relea","scope_keywords":["343"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 343 Network Working Group A. McKenzie\nRequest for Comments: 343 BBN-NET\nNIC #10422 19 May 1972\nCategory: B.1\nObsoletes: RFC #331\n\n IMP System Change Notification\n\n As most of you probably know, our attempt to release IMPSYS 2600 on\n May 15 (as discussed in RFC #331) was unsuccessful. Briefly, the\n primary reasons for failure (all operational rather than programming\n bugs) were:\n\n 1) The network appears to have grown too large for us to\n successfully coordinate operator intervention at all sites.\n\n 2) An unanticipated aspect of the gradual release of the new\n system was the \"poisoning\" of IMP's running the new system by\n adjacent IMP's running the old system, and vice versa. Working\n around this problem made the dissemination of the new system\n take much longer than anticipated.\n\n We believe we see solutions to both of these problems and are now\n ready to schedule the next attempt(s) to relea 343 nested-reference unchanged"},{"id":"IETF RFC 344","type":"specification","body":"IETF","designation":"RFC 344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc344.txt","https://www.rfc-editor.org/rfc/rfc344.pdf"],"folder":"IETF/RFC-344","files":{"txt":{"path":"standards/IETF/RFC-344/RFC-344.txt","sha256":"88a46b92c71e185fb64d9328acff0fc8916c51f0f66151ce92eaa5136339b3f0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: 344 BBN\nNIC #10423 22 May 1972\nCategories: F, G.3\nUpdates: RFC #342\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from\n May 8 to May 19. No testing was done on May 15 due to the attempt\n to install the new IMP system on that day.\n\n During this interval the PDP-10 of the MIT Artificial\n Intelligence Group (Network address 134) and the PDP-10 at\n Stanford (Network address 11) each became Network Servers.\n\n Several Hosts are currently excluded from the daily testing.\n These Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the\n Network as servers (available for use from other sites)\n on a regular basis for at least two weeks. The only\n Host in this category is the PDP-10 at Case (Network\n address 13).\n\n 2) Hosts which are currently intended to be u","scope_keywords":["344"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 344 Network Working Group Ellen Westheimer\nRequest for Comments: 344 BBN\nNIC #10423 22 May 1972\nCategories: F, G.3\nUpdates: RFC #342\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from\n May 8 to May 19. No testing was done on May 15 due to the attempt\n to install the new IMP system on that day.\n\n During this interval the PDP-10 of the MIT Artificial\n Intelligence Group (Network address 134) and the PDP-10 at\n Stanford (Network address 11) each became Network Servers.\n\n Several Hosts are currently excluded from the daily testing.\n These Hosts fall into two categories:\n\n 1) Hosts which are not expected to be functioning on the\n Network as servers (available for use from other sites)\n on a regular basis for at least two weeks. The only\n Host in this category is the PDP-10 at Case (Network\n address 13).\n\n 2) Hosts which are currently intended to be u 344 nested-reference unchanged"},{"id":"IETF RFC 7632","type":"specification","body":"IETF","designation":"RFC 7632","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7632.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7632.txt","https://www.rfc-editor.org/rfc/rfc7632.pdf"],"folder":"IETF/RFC-7632","files":{"txt":{"path":"standards/IETF/RFC-7632/RFC-7632.txt","sha256":"9be3cb8e4443aa7adda843739fdcf887ae40421e36cb0186a2279dd5dadb2067"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents a sampling of use cases for securely aggregating\n configuration and operational data and evaluating that data to\n determine an organization's security posture. From these operational\n use cases, we can derive common functional capabilities and\n requirements to guide development of vendor-neutral, interoperable\n standards for aggregating and evaluating data relevant to security\n posture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of","scope_keywords":["7632","attribute","attributes","http","identification","license","policies","policy","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8248","folder":"IETF/RFC-8248","source":"IETF/RFC-8248/RFC-8248.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 7632 This memo documents a sampling of use cases for securely aggregating\n configuration and operational data and evaluating that data to\n determine an organization's security posture. From these operational\n use cases, we can derive common functional capabilities and\n requirements to guide development of vendor-neutral, interoperable\n standards for aggregating and evaluating data relevant to security\n posture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of 7632 attribute attributes http identification license policies policy risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5325","type":"specification","body":"IETF","designation":"RFC 5325","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5325.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5325.txt","https://www.rfc-editor.org/rfc/rfc5325.pdf"],"folder":"IETF/RFC-5325","files":{"txt":{"path":"standards/IETF/RFC-5325/RFC-5325.txt","sha256":"eb6f4a608aa45d18e9fed0eb1e5fd5cb74cc2920104939a4a9302325e2c0c3e1"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the motivation for the development of the\n Licklider Transmission Protocol (LTP) designed to provide\n retransmission-based reliability over links characterized by\n extremely long message round-trip times (RTTs) and/or frequent\n interruptions in connectivity. Since communication across\n interplanetary space is the most prominent example of this sort of\n environment, LTP is principally aimed at supporting \"long-haul\"\n reliable transmission in interplanetary space, but it has\n applications in other environments as well.\n\n In an Interplanetary Internet setting deploying the Bundle protocol,\n LTP is intended to serve as a reliable convergence layer over\n single-hop deep-space radio frequency (RF) links. LTP does Automatic\n Repeat reQuest (ARQ) of data transmissions by soliciting selective-\n acknowledgment reception reports. It is stateful and has no\n negotiation or han","scope_keywords":["5325","delivery","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5327","folder":"IETF/RFC-5327","source":"IETF/RFC-5327/RFC-5327.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null}],"search_text":"IETF RFC 5325 This document describes the motivation for the development of the\n Licklider Transmission Protocol (LTP) designed to provide\n retransmission-based reliability over links characterized by\n extremely long message round-trip times (RTTs) and/or frequent\n interruptions in connectivity. Since communication across\n interplanetary space is the most prominent example of this sort of\n environment, LTP is principally aimed at supporting \"long-haul\"\n reliable transmission in interplanetary space, but it has\n applications in other environments as well.\n\n In an Interplanetary Internet setting deploying the Bundle protocol,\n LTP is intended to serve as a reliable convergence layer over\n single-hop deep-space radio frequency (RF) links. LTP does Automatic\n Repeat reQuest (ARQ) of data transmissions by soliciting selective-\n acknowledgment reception reports. It is stateful and has no\n negotiation or han 5325 delivery management nested-reference unchanged"},{"id":"IETF RFC 4013","type":"specification","body":"IETF","designation":"RFC 4013","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4013.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4013.txt","https://www.rfc-editor.org/rfc/rfc4013.pdf"],"folder":"IETF/RFC-4013","files":{"txt":{"path":"standards/IETF/RFC-4013/RFC-4013.txt","sha256":"63daa764693815ae8544728099d17a1c46e96b5818f2a399b3ec475ea153a991"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to prepare Unicode strings representing\n user names and passwords for comparison. The document defines the\n \"SASLprep\" profile of the \"stringprep\" algorithm to be used for both\n user names and passwords. This profile is intended to be used by\n Simple Authentication and Security Layer (SASL) mechanisms (such as\n PLAIN, CRAM-MD5, and DIGEST-MD5), as well as other protocols\n exchanging simple user names and/or passwords.\n\n1. Introduction\n\n The use of simple user names and passwords in authentication and\n authorization is pervasive on the Internet. To increase the\n likelihood that user name and password input and comparison work in\n ways that make sense for typical users throughout the world, this\n document defines rules for preparing internationalized user names and\n passwords for comparison. For simplicity and implementation ease, a\n single algorithm is defined ","scope_keywords":["4013","algorithm","algorithms","authentication","authorization","presentation","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4643","folder":"IETF/RFC-4643","source":"IETF/RFC-4643/RFC-4643.txt","version":null},{"body":"IETF","designation":"RFC 4954","folder":"IETF/RFC-4954","source":"IETF/RFC-4954/RFC-4954.txt","version":null},{"body":"IETF","designation":"RFC 4992","folder":"IETF/RFC-4992","source":"IETF/RFC-4992/RFC-4992.txt","version":null},{"body":"IETF","designation":"RFC 5034","folder":"IETF/RFC-5034","source":"IETF/RFC-5034/RFC-5034.txt","version":null},{"body":"IETF","designation":"RFC 5054","folder":"IETF/RFC-5054","source":"IETF/RFC-5054/RFC-5054.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5769","folder":"IETF/RFC-5769","source":"IETF/RFC-5769/RFC-5769.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5931","folder":"IETF/RFC-5931","source":"IETF/RFC-5931/RFC-5931.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"IETF RFC 4013 This document describes how to prepare Unicode strings representing\n user names and passwords for comparison. The document defines the\n \"SASLprep\" profile of the \"stringprep\" algorithm to be used for both\n user names and passwords. This profile is intended to be used by\n Simple Authentication and Security Layer (SASL) mechanisms (such as\n PLAIN, CRAM-MD5, and DIGEST-MD5), as well as other protocols\n exchanging simple user names and/or passwords.\n\n1. Introduction\n\n The use of simple user names and passwords in authentication and\n authorization is pervasive on the Internet. To increase the\n likelihood that user name and password input and comparison work in\n ways that make sense for typical users throughout the world, this\n document defines rules for preparing internationalized user names and\n passwords for comparison. For simplicity and implementation ease, a\n single algorithm is defined  4013 algorithm algorithms authentication authorization presentation profile nested-reference unchanged"},{"id":"IETF RFC 5051","type":"specification","body":"IETF","designation":"RFC 5051","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5051.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5051.txt","https://www.rfc-editor.org/rfc/rfc5051.pdf"],"folder":"IETF/RFC-5051","files":{"txt":{"path":"standards/IETF/RFC-5051/RFC-5051.txt","sha256":"9ceb287ee83205235b4045dac23d2649c7273d8cead9f97e8cc55e2524595b36"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Crispin\nRequest for Comments: 5051 University of Washington\nCategory: Standards Track October 2007\n\n i;unicode-casemap - Simple Unicode Collation Algorithm\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes \"i;unicode-casemap\", a simple case-\n insensitive collation for Unicode strings. It provides equality,\n substring, and ordering operations.\n\n1. Introduction\n\n The \"i;ascii-casemap\" collation described in [COMPARATOR] is quite\n simple to implement and provides case-independent comparisons for the\n 26 Latin alphabetics. I","scope_keywords":["5051","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null}],"search_text":"IETF RFC 5051 Network Working Group M. Crispin\nRequest for Comments: 5051 University of Washington\nCategory: Standards Track October 2007\n\n i;unicode-casemap - Simple Unicode Collation Algorithm\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nAbstract\n\n This document describes \"i;unicode-casemap\", a simple case-\n insensitive collation for Unicode strings. It provides equality,\n substring, and ordering operations.\n\n1. Introduction\n\n The \"i;ascii-casemap\" collation described in [COMPARATOR] is quite\n simple to implement and provides case-independent comparisons for the\n 26 Latin alphabetics. I 5051 algorithm nested-reference unchanged"},{"id":"IETF RFC 7790","type":"specification","body":"IETF","designation":"RFC 7790","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7790.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7790.txt","https://www.rfc-editor.org/rfc/rfc7790.pdf"],"folder":"IETF/RFC-7790","files":{"txt":{"path":"standards/IETF/RFC-7790/RFC-7790.txt","sha256":"52f0f68ba380645612915f75d8624ed656ba498c5ca07333f9d31e8de544a63d"}},"tags":["nested-reference","unchanged"],"summary":"The framework for the preparation, enforcement, and comparison of\n internationalized strings (PRECIS) defines several classes of strings\n for use in application protocols. Because many protocols perform\n case-sensitive or case-insensitive string comparison, it is necessary\n to define methods for case mapping. In addition, both the\n Internationalized Domain Names in Applications (IDNA) and the PRECIS\n problem statement describe mappings for internationalized strings\n that are not limited to case, but include width mapping and mapping\n of delimiters and other special characters that can be taken into\n consideration. This document provides guidelines for designers of\n PRECIS profiles and describes several mappings that can be applied\n between receiving user input and passing permitted code points to\n internationalized protocols. In particular, this document describes\n both locale-dependent ","scope_keywords":["7790","http","key","license","presentation","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 7790 The framework for the preparation, enforcement, and comparison of\n internationalized strings (PRECIS) defines several classes of strings\n for use in application protocols. Because many protocols perform\n case-sensitive or case-insensitive string comparison, it is necessary\n to define methods for case mapping. In addition, both the\n Internationalized Domain Names in Applications (IDNA) and the PRECIS\n problem statement describe mappings for internationalized strings\n that are not limited to case, but include width mapping and mapping\n of delimiters and other special characters that can be taken into\n consideration. This document provides guidelines for designers of\n PRECIS profiles and describes several mappings that can be applied\n between receiving user input and passing permitted code points to\n internationalized protocols. In particular, this document describes\n both locale-dependent  7790 http key license presentation profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 346","type":"specification","body":"IETF","designation":"RFC 346","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc346.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc346.txt","https://www.rfc-editor.org/rfc/rfc346.pdf"],"folder":"IETF/RFC-346","files":{"txt":{"path":"standards/IETF/RFC-346/RFC-346.txt","sha256":"d6dd20962c6c2597911c628fc8c0bd4aef1c48805fa3ab55da40b1d0227cfcc7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 346 Computer Science\n UCLA-NMC\nNIC : 10425 30 May 72\n\nCategories : Echo Plex, Satellite\nReferences : RFC's 1, 5, 51\n\n Satellite Considerations\n\nThe consideration of using space satellite transmission links in the\nARPANET should be cause for some thought by the parties making use of\nthe network. The satellite transmission path will not necessarily affect\nthe transmission rate but it will affect the delay. The change in the\ndelay characteristics can be approximated by the change in path length.\nThus if the satellite is in synchronous orbit about 22,000 miles above\nthe earth, the path length is about 44,000 miles compared to (worst\ncase) 3,000 miles or about a 15 to 1 increase in path length and delay.\n(The time for light to travel 3,000 miles is .016 seconds, to travel\n44,000 miles is .236 seconds.)\nIn the current (surface) ARPANET del","scope_keywords":["346","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 357","folder":"IETF/RFC-357","source":"IETF/RFC-357/RFC-357.txt","version":null}],"search_text":"IETF RFC 346 Network Working Group Jon Postel\nRequest for Comments: 346 Computer Science\n UCLA-NMC\nNIC : 10425 30 May 72\n\nCategories : Echo Plex, Satellite\nReferences : RFC's 1, 5, 51\n\n Satellite Considerations\n\nThe consideration of using space satellite transmission links in the\nARPANET should be cause for some thought by the parties making use of\nthe network. The satellite transmission path will not necessarily affect\nthe transmission rate but it will affect the delay. The change in the\ndelay characteristics can be approximated by the change in path length.\nThus if the satellite is in synchronous orbit about 22,000 miles above\nthe earth, the path length is about 44,000 miles compared to (worst\ncase) 3,000 miles or about a 15 to 1 increase in path length and delay.\n(The time for light to travel 3,000 miles is .016 seconds, to travel\n44,000 miles is .236 seconds.)\nIn the current (surface) ARPANET del 346 path nested-reference unchanged"},{"id":"IETF RFC 357","type":"specification","body":"IETF","designation":"RFC 357","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc357.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc357.txt","https://www.rfc-editor.org/rfc/rfc357.pdf"],"folder":"IETF/RFC-357","files":{"txt":{"path":"standards/IETF/RFC-357/RFC-357.txt","sha256":"45dd198f64a6bd138bd13e127ffd1392cff8a241075383506f21618951f06d01"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Davidson\nRequest for Comments: 357 University of Hawaii\nNIC: 10599 Will Crowther\nCategories: Remote Controlled Echoing, Satellite, TELNET BBN\nReferences: RFC's 346, 355, 358, 318 John McConnell\n ILLIAC\n Jon Postel\n UCLA\n June 26, 1972\n\n An Echoing Strategy For Satellite Links\n\nI. Introduction\n\n As mentioned in RFC 346 (\"Satellite Considerations\" by Jon Postel)\n those interactive systems which provide echoing for full-duplex\n terminals over the ARPANET become more awkward to use as transmission\n delays increase. The reason, of course, is that a character's round\n trip time is added to the inherent echo delay of the server with the\n result that the terminal echoing appears extremely sluggish.\n\n For a terminal separated from its server by a single satellite link,\n the delay will be such that even if echoing at the server were\n instantaneous, the latency between ke","scope_keywords":["357","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 435","folder":"IETF/RFC-435","source":"IETF/RFC-435/RFC-435.txt","version":null},{"body":"IETF","designation":"RFC 560","folder":"IETF/RFC-560","source":"IETF/RFC-560/RFC-560.txt","version":null},{"body":"IETF","designation":"RFC 726","folder":"IETF/RFC-726","source":"IETF/RFC-726/RFC-726.txt","version":null}],"search_text":"IETF RFC 357 Network Working Group John Davidson\nRequest for Comments: 357 University of Hawaii\nNIC: 10599 Will Crowther\nCategories: Remote Controlled Echoing, Satellite, TELNET BBN\nReferences: RFC's 346, 355, 358, 318 John McConnell\n ILLIAC\n Jon Postel\n UCLA\n June 26, 1972\n\n An Echoing Strategy For Satellite Links\n\nI. Introduction\n\n As mentioned in RFC 346 (\"Satellite Considerations\" by Jon Postel)\n those interactive systems which provide echoing for full-duplex\n terminals over the ARPANET become more awkward to use as transmission\n delays increase. The reason, of course, is that a character's round\n trip time is added to the inherent echo delay of the server with the\n result that the terminal echoing appears extremely sluggish.\n\n For a terminal separated from its server by a single satellite link,\n the delay will be such that even if echoing at the server were\n instantaneous, the latency between ke 357 key nested-reference unchanged"},{"id":"IETF RFC 3570","type":"specification","body":"IETF","designation":"RFC 3570","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3570.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3570.txt","https://www.rfc-editor.org/rfc/rfc3570.pdf"],"folder":"IETF/RFC-3570","files":{"txt":{"path":"standards/IETF/RFC-3570/RFC-3570.txt","sha256":"3e6a5b2bd26ebd9eedb033dee4a6f873ea89a1c9d0310a7f05186823ba0ce35c"}},"tags":["nested-reference","unchanged"],"summary":"In describing content internetworking as a technology targeted for\n use in production networks, it is useful to provide examples of the\n sequence of events that may occur when two content networks decide to\n interconnect. The scenarios presented here seek to provide some\n concrete examples of what content internetworking is, and also to\n provide a basis for evaluating content internetworking proposals.","scope_keywords":["3570"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6707","folder":"IETF/RFC-6707","source":"IETF/RFC-6707/RFC-6707.txt","version":null},{"body":"IETF","designation":"RFC 6770","folder":"IETF/RFC-6770","source":"IETF/RFC-6770/RFC-6770.txt","version":null}],"search_text":"IETF RFC 3570 In describing content internetworking as a technology targeted for\n use in production networks, it is useful to provide examples of the\n sequence of events that may occur when two content networks decide to\n interconnect. The scenarios presented here seek to provide some\n concrete examples of what content internetworking is, and also to\n provide a basis for evaluating content internetworking proposals. 3570 nested-reference unchanged"},{"id":"IETF RFC 7336","type":"specification","body":"IETF","designation":"RFC 7336","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7336.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7336.txt","https://www.rfc-editor.org/rfc/rfc7336.pdf"],"folder":"IETF/RFC-7336","files":{"txt":{"path":"standards/IETF/RFC-7336/RFC-7336.txt","sha256":"662f6538083fc6cce07cea997aeafed95365a045f824b0b6891a306afcdbe7b8"}},"tags":["nested-reference","unchanged"],"summary":"This document presents a framework for Content Distribution Network\n Interconnection (CDNI). The purpose of the framework is to provide\n an overall picture of the problem space of CDNI and to describe the\n relationships among the various components necessary to interconnect\n CDNs. CDNI requires the specification of interfaces and mechanisms\n to address issues such as request routing, distribution metadata\n exchange, and logging information exchange across CDNs. The intent\n of this document is to outline what each interface needs to\n accomplish and to describe how these interfaces and mechanisms fit\n together, while leaving their detailed specification to other\n documents. This document, in combination with RFC 6707, obsoletes\n RFC 3466.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a ","scope_keywords":["7336","http","license","management","policies","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7337","folder":"IETF/RFC-7337","source":"IETF/RFC-7337/RFC-7337.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 7336 This document presents a framework for Content Distribution Network\n Interconnection (CDNI). The purpose of the framework is to provide\n an overall picture of the problem space of CDNI and to describe the\n relationships among the various components necessary to interconnect\n CDNs. CDNI requires the specification of interfaces and mechanisms\n to address issues such as request routing, distribution metadata\n exchange, and logging information exchange across CDNs. The intent\n of this document is to outline what each interface needs to\n accomplish and to describe how these interfaces and mechanisms fit\n together, while leaving their detailed specification to other\n documents. This document, in combination with RFC 6707, obsoletes\n RFC 3466.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a  7336 http license management policies qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 347","type":"specification","body":"IETF","designation":"RFC 347","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc347.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc347.txt","https://www.rfc-editor.org/rfc/rfc347.pdf"],"folder":"IETF/RFC-347","files":{"txt":{"path":"standards/IETF/RFC-347/RFC-347.txt","sha256":"ddb8127b0a6ee560a30f7638835b8530d18967002ad0142dd6bd693a5400110e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments : 347 Computer Science\n UCLA-NMC\nNIC 10426 30 May 72\n\nCategories: Standard Processes\n\n Echo Process\n\nI suggest that for debugging and measurement purposes those hosts which\nare willing implement an \"Echo\" process.\nThis echo process would listen for a request for connection and execute\nthe Initial Connection Protocol (ICP) as specified in NIC 7104 the\n\"Current Network Protocols\" notebook. Upon completion of the ICP the\necho process would wait for data from the network. When the data is\nreceived from the network it is echoed at once, (and the buffer space is\nre-allocated). By echoed I mean that the data received is sent back\nover the network, bit for bit with no modification by the echo process.\nThe echo process is terminated by closing the network connections.\nNote that BBN-TENEX has had such an echo process available for use for a\nlon","scope_keywords":["347"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null}],"search_text":"IETF RFC 347 Network Working Group Jon Postel\nRequest for Comments : 347 Computer Science\n UCLA-NMC\nNIC 10426 30 May 72\n\nCategories: Standard Processes\n\n Echo Process\n\nI suggest that for debugging and measurement purposes those hosts which\nare willing implement an \"Echo\" process.\nThis echo process would listen for a request for connection and execute\nthe Initial Connection Protocol (ICP) as specified in NIC 7104 the\n\"Current Network Protocols\" notebook. Upon completion of the ICP the\necho process would wait for data from the network. When the data is\nreceived from the network it is echoed at once, (and the buffer space is\nre-allocated). By echoed I mean that the data received is sent back\nover the network, bit for bit with no modification by the echo process.\nThe echo process is terminated by closing the network connections.\nNote that BBN-TENEX has had such an echo process available for use for a\nlon 347 nested-reference unchanged"},{"id":"IETF RFC 840","type":"specification","body":"IETF","designation":"RFC 840","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc840.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc840.txt","https://www.rfc-editor.org/rfc/rfc840.pdf"],"folder":"IETF/RFC-840","files":{"txt":{"path":"standards/IETF/RFC-840/RFC-840.txt","sha256":"fc9a3f1b317958fc2f13219297257eec749287efd7b3fd6fbb18ea8fa8875f68"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 840 ISI\n April 1983\n\n Official Protocols\n\nThis RFC identifies the documents specifying the official protocols used\nin the Internet. Annotations identify any revisions or changes planned.\n\nTo first order, the official protocols are those in the Internet\nProtocol Transition Workbook (IPTW) dated March 1982. There are several\nprotocols in use that are not in the IPTW. A few of the protocols in\nthe IPTW have been revised these are noted here. In particular, the\nmail protocols have been revised and issued as a volume titled \"Internet\nMail Protocols\" dated November 1982. There is a volume of protocol\nrelated information called the Internet Protocol Implementers Guide\n(IPIG) dated August 1982. A few of the protocols (in particular the\nTelnet Options) have not been revised for many years, these are found in\nthe old ARPANET Protocol Handbook (","scope_keywords":["840","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null}],"search_text":"IETF RFC 840 Network Working Group J. Postel\nRequest for Comments: 840 ISI\n April 1983\n\n Official Protocols\n\nThis RFC identifies the documents specifying the official protocols used\nin the Internet. Annotations identify any revisions or changes planned.\n\nTo first order, the official protocols are those in the Internet\nProtocol Transition Workbook (IPTW) dated March 1982. There are several\nprotocols in use that are not in the IPTW. A few of the protocols in\nthe IPTW have been revised these are noted here. In particular, the\nmail protocols have been revised and issued as a volume titled \"Internet\nMail Protocols\" dated November 1982. There is a volume of protocol\nrelated information called the Internet Protocol Implementers Guide\n(IPIG) dated August 1982. A few of the protocols (in particular the\nTelnet Options) have not been revised for many years, these are found in\nthe old ARPANET Protocol Handbook ( 840 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 4394","type":"specification","body":"IETF","designation":"RFC 4394","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4394.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4394.txt","https://www.rfc-editor.org/rfc/rfc4394.pdf"],"folder":"IETF/RFC-4394","files":{"txt":{"path":"standards/IETF/RFC-4394/RFC-4394.txt","sha256":"19a5af1094494d4bc4e24bc9f8c17c6fc4e17ff04f558bf05243966b81da01e3"}},"tags":["nested-reference","unchanged"],"summary":"The Link Management Protocol (LMP) has been developed as part of the\n Generalized MPLS (GMPLS) protocol suite to manage Traffic Engineering\n (TE) resources and links. The GMPLS control plane (routing and\n signaling) uses TE links for establishing Label Switched Paths\n (LSPs). This memo describes the relationship of the LMP procedures\n to 'discovery' as defined in the International Telecommunication\n Union (ITU-T), and ongoing ITU-T work. This document provides an\n overview of LMP in the context of the ITU-T Automatically Switched\n Optical Networks (ASON) and transport network terminology and relates\n it to the ITU-T discovery work to promote a common understanding for\n progressing the work of IETF and ITU-T.\n\nFedyk, et al. Informational [Page 1]\n\f\nRFC 4394 Transport Network View of LMP February 2006","scope_keywords":["4394","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null}],"search_text":"IETF RFC 4394 The Link Management Protocol (LMP) has been developed as part of the\n Generalized MPLS (GMPLS) protocol suite to manage Traffic Engineering\n (TE) resources and links. The GMPLS control plane (routing and\n signaling) uses TE links for establishing Label Switched Paths\n (LSPs). This memo describes the relationship of the LMP procedures\n to 'discovery' as defined in the International Telecommunication\n Union (ITU-T), and ongoing ITU-T work. This document provides an\n overview of LMP in the context of the ITU-T Automatically Switched\n Optical Networks (ASON) and transport network terminology and relates\n it to the ITU-T discovery work to promote a common understanding for\n progressing the work of IETF and ITU-T.\n\nFedyk, et al. Informational [Page 1]\n\f\nRFC 4394 Transport Network View of LMP February 2006 4394 management path presentation nested-reference unchanged"},{"id":"IETF RFC 4397","type":"specification","body":"IETF","designation":"RFC 4397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4397.txt","https://www.rfc-editor.org/rfc/rfc4397.pdf"],"folder":"IETF/RFC-4397","files":{"txt":{"path":"standards/IETF/RFC-4397/RFC-4397.txt","sha256":"a5c01456773fbc3c61b84ffaeb0b50c3089e0f89f192c3c4092b830a3988fa5d"}},"tags":["nested-reference","unchanged"],"summary":"Generalized Multiprotocol Label Switching (GMPLS) has been developed\n by the IETF to facilitate the establishment of Label Switched Paths\n (LSPs) in a variety of data plane technologies and across several\n architectural models. The ITU-T has specified an architecture for\n the control of Automatically Switched Optical Networks (ASON).\n\n This document provides a lexicography for the interpretation of GMPLS\n terminology within the context of the ASON architecture.\n\n It is important to note that GMPLS is applicable in a wider set of\n contexts than just ASON. The definitions presented in this document\n do not provide exclusive or complete interpretations of GMPLS\n concepts. This document simply allows the GMPLS terms to be applied\n within the ASON context.\n\nBryskin & Farrel Informational [Page 1]\n\f\nRFC 4397 GMPLS ASON Lexicography February 2006","scope_keywords":["4397","key","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"IETF RFC 4397 Generalized Multiprotocol Label Switching (GMPLS) has been developed\n by the IETF to facilitate the establishment of Label Switched Paths\n (LSPs) in a variety of data plane technologies and across several\n architectural models. The ITU-T has specified an architecture for\n the control of Automatically Switched Optical Networks (ASON).\n\n This document provides a lexicography for the interpretation of GMPLS\n terminology within the context of the ASON architecture.\n\n It is important to note that GMPLS is applicable in a wider set of\n contexts than just ASON. The definitions presented in this document\n do not provide exclusive or complete interpretations of GMPLS\n concepts. This document simply allows the GMPLS terms to be applied\n within the ASON context.\n\nBryskin & Farrel Informational [Page 1]\n\f\nRFC 4397 GMPLS ASON Lexicography February 2006 4397 key management path nested-reference unchanged"},{"id":"IETF RFC 348","type":"specification","body":"IETF","designation":"RFC 348","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc348.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc348.txt","https://www.rfc-editor.org/rfc/rfc348.pdf"],"folder":"IETF/RFC-348","files":{"txt":{"path":"standards/IETF/RFC-348/RFC-348.txt","sha256":"caaf51c02126a17c7090711a95b7d3d7eafe3bad092fafc0a258cb93e814659e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments : 348 Computer Science\n UCLA-NMC\nNIC : 10427 30 May 72\n\nCategories : Standard Processes\n\n Discard Process\n\nI suggest that for debugging and measurement purposes those hosts which\nare willing implement a \"Discard\" process.\n\nThis discard process would listen for a request for connection and\nexecute the Initial Connection Protocol (ICP) as specified in NIC 7104\nthe \"Current Network Protocols\" notebook. Upon completion of the ICP\nthe discard process would wait for data from the network. When data is\nreceived from the network it is discarded at once, (and the buffer space\nis re-allocated). The discard process is terminated by closing the\nnetwork connections.\n\n [ This RFC was put into machine readable form for entry ]\n [ into the online RFC archives by BBN Corp. under the ]\n [ direction of Alex McKenzie. 12/96 ]\n\n [Page 1]","scope_keywords":["348"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 429","folder":"IETF/RFC-429","source":"IETF/RFC-429/RFC-429.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null}],"search_text":"IETF RFC 348 Network Working Group Jon Postel\nRequest for Comments : 348 Computer Science\n UCLA-NMC\nNIC : 10427 30 May 72\n\nCategories : Standard Processes\n\n Discard Process\n\nI suggest that for debugging and measurement purposes those hosts which\nare willing implement a \"Discard\" process.\n\nThis discard process would listen for a request for connection and\nexecute the Initial Connection Protocol (ICP) as specified in NIC 7104\nthe \"Current Network Protocols\" notebook. Upon completion of the ICP\nthe discard process would wait for data from the network. When data is\nreceived from the network it is discarded at once, (and the buffer space\nis re-allocated). The discard process is terminated by closing the\nnetwork connections.\n\n [ This RFC was put into machine readable form for entry ]\n [ into the online RFC archives by BBN Corp. under the ]\n [ direction of Alex McKenzie. 12/96 ]\n\n [Page 1] 348 nested-reference unchanged"},{"id":"IETF RFC 429","type":"specification","body":"IETF","designation":"RFC 429","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc429.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc429.txt","https://www.rfc-editor.org/rfc/rfc429.pdf"],"folder":"IETF/RFC-429","files":{"txt":{"path":"standards/IETF/RFC-429/RFC-429.txt","sha256":"e7822d3ee41e9200764c41021144132b7bb17ac2b79aa078e27575bd734e564e"}},"tags":["nested-reference","unchanged"],"summary":"ARPA Network Information Center\nStanford Research Institute\nMenlo Park, California 94025\n\nNWG/RFC #429 Jonathan B. Postel (UCLA-NMC)\nNIC #13281 12-DEC-72\n\n Character Generator Process\n\nI hereby propose that there be a standard process implemented on\nwhatever hosts desire which generates character data with out any\nregard to input. In some sense the process is the converse of the\ndiscard process [RFC 348]. Many hosts have an existing terminal\ntesting program [e.g. TTYTST] which would suit this function\nadequately.\n\nThis Character Generator process would listen for a request for\nconnection and execute the Initial Connection Protocol (ICP) as\nspecified in NIC 7104 the \"Current Network Protocols\" notebook. Upon\ncompletion of the ICP the Character Generator process would begin to\nsend characters into the network as buffer space is made available .\nThe Character Generator process is terminated","scope_keywords":["429"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null}],"search_text":"IETF RFC 429 ARPA Network Information Center\nStanford Research Institute\nMenlo Park, California 94025\n\nNWG/RFC #429 Jonathan B. Postel (UCLA-NMC)\nNIC #13281 12-DEC-72\n\n Character Generator Process\n\nI hereby propose that there be a standard process implemented on\nwhatever hosts desire which generates character data with out any\nregard to input. In some sense the process is the converse of the\ndiscard process [RFC 348]. Many hosts have an existing terminal\ntesting program [e.g. TTYTST] which would suit this function\nadequately.\n\nThis Character Generator process would listen for a request for\nconnection and execute the Initial Connection Protocol (ICP) as\nspecified in NIC 7104 the \"Current Network Protocols\" notebook. Upon\ncompletion of the ICP the Character Generator process would begin to\nsend characters into the network as buffer space is made available .\nThe Character Generator process is terminated 429 nested-reference unchanged"},{"id":"IETF RFC 5221","type":"specification","body":"IETF","designation":"RFC 5221","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5221.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5221.txt","https://www.rfc-editor.org/rfc/rfc5221.pdf"],"folder":"IETF/RFC-5221","files":{"txt":{"path":"standards/IETF/RFC-5221/RFC-5221.txt","sha256":"56fa09efb7ab64bff0588efc3f3434bbd1da0c6aed04f098b50e3bf0737dc720"}},"tags":["nested-reference","unchanged"],"summary":"There are some problematic cases when using the default address\n selection mechanism that RFC 3484 defines. This document describes\n additional requirements that operate with RFC 3484 to solve the\n problems.","scope_keywords":["5221","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6418","folder":"IETF/RFC-6418","source":"IETF/RFC-6418/RFC-6418.txt","version":null},{"body":"IETF","designation":"RFC 7078","folder":"IETF/RFC-7078","source":"IETF/RFC-7078/RFC-7078.txt","version":null}],"search_text":"IETF RFC 5221 There are some problematic cases when using the default address\n selection mechanism that RFC 3484 defines. This document describes\n additional requirements that operate with RFC 3484 to solve the\n problems. 5221 policy nested-reference unchanged"},{"id":"IETF RFC 4713","type":"specification","body":"IETF","designation":"RFC 4713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4713.txt","https://www.rfc-editor.org/rfc/rfc4713.pdf"],"folder":"IETF/RFC-4713","files":{"txt":{"path":"standards/IETF/RFC-4713/RFC-4713.txt","sha256":"6847264f2ce04ccded08973384c5312dd1aed8f68b8d0ea6b40da62775925894"}},"tags":["nested-reference","unchanged"],"summary":"Many Chinese characters in common use have variants, which makes most\n of the Chinese Domain Names (CDNs) have at least two different forms.\n The equivalence between Simplified Chinese (SC) and Traditional\n Chinese (TC) characters is very important for CDN registration. This\n memo builds on the basic concepts, general guidelines, and framework\n of RFC 3743 to specify proposed registration and administration\n procedures for Chinese domain names. The document provides the\n information needed for understanding and using the tables defined in\n the IANA table registrations for Simplified and Traditional Chinese.\n\nLee, et al. Informational [Page 1]\n\f\nRFC 4713 Recommendations for Chinese Domain Names October 2006","scope_keywords":["4713"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6927","folder":"IETF/RFC-6927","source":"IETF/RFC-6927/RFC-6927.txt","version":null}],"search_text":"IETF RFC 4713 Many Chinese characters in common use have variants, which makes most\n of the Chinese Domain Names (CDNs) have at least two different forms.\n The equivalence between Simplified Chinese (SC) and Traditional\n Chinese (TC) characters is very important for CDN registration. This\n memo builds on the basic concepts, general guidelines, and framework\n of RFC 3743 to specify proposed registration and administration\n procedures for Chinese domain names. The document provides the\n information needed for understanding and using the tables defined in\n the IANA table registrations for Simplified and Traditional Chinese.\n\nLee, et al. Informational [Page 1]\n\f\nRFC 4713 Recommendations for Chinese Domain Names October 2006 4713 nested-reference unchanged"},{"id":"IETF RFC 6317","type":"specification","body":"IETF","designation":"RFC 6317","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6317.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6317.txt","https://www.rfc-editor.org/rfc/rfc6317.pdf"],"folder":"IETF/RFC-6317","files":{"txt":{"path":"standards/IETF/RFC-6317/RFC-6317.txt","sha256":"594c6f90a32804c901081c290af39a2038f14532de52342335c4b009f446a47a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines extensions to the current sockets API for the\n Host Identity Protocol (HIP). The extensions focus on the use of\n public-key-based identifiers discovered via DNS resolution, but also\n define interfaces for manual bindings between Host Identity Tags\n (HITs) and locators. With the extensions, the application can also\n support more relaxed security models where communication can be non-\n HIP-based, according to local policies. The extensions in this\n document are experimental and provide basic tools for further\n experimentation with policies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents","scope_keywords":["6317","hash","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6316","folder":"IETF/RFC-6316","source":"IETF/RFC-6316/RFC-6316.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null}],"search_text":"IETF RFC 6317 This document defines extensions to the current sockets API for the\n Host Identity Protocol (HIP). The extensions focus on the use of\n public-key-based identifiers discovered via DNS resolution, but also\n define interfaces for manual bindings between Host Identity Tags\n (HITs) and locators. With the extensions, the application can also\n support more relaxed security models where communication can be non-\n HIP-based, according to local policies. The extensions in this\n document are experimental and provide basic tools for further\n experimentation with policies.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for examination, experimental implementation, and\n evaluation.\n\n This document defines an Experimental Protocol for the Internet\n community. This document is a product of the Internet Engineering\n Task Force (IETF). It represents 6317 hash http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 5442","type":"specification","body":"IETF","designation":"RFC 5442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5442.txt","https://www.rfc-editor.org/rfc/rfc5442.pdf"],"folder":"IETF/RFC-5442","files":{"txt":{"path":"standards/IETF/RFC-5442/RFC-5442.txt","sha256":"4c8c9fc81b190f26966432fca9964e71fe44943bbcbd49c713bb9a7d1ce951a5"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the architecture for mobile email, as\n described by the Open Mobile Alliance (OMA), using Internet Mail\n protocols. This architecture was an important consideration for much\n of the work of the LEMONADE (Enhancements to Internet email to\n Support Diverse Service Environments) working group in the IETF.\n This document also describes how the LEMONADE architecture meets\n OMA's requirements for their Mobile Email (MEM) service.\n\nBurger & Parsons Informational [Page 1]\n\f\nRFC 5442 LEMONADE Architecture March 2009","scope_keywords":["5442","http","license","management","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null}],"search_text":"IETF RFC 5442 This document specifies the architecture for mobile email, as\n described by the Open Mobile Alliance (OMA), using Internet Mail\n protocols. This architecture was an important consideration for much\n of the work of the LEMONADE (Enhancements to Internet email to\n Support Diverse Service Environments) working group in the IETF.\n This document also describes how the LEMONADE architecture meets\n OMA's requirements for their Mobile Email (MEM) service.\n\nBurger & Parsons Informational [Page 1]\n\f\nRFC 5442 LEMONADE Architecture March 2009 5442 http license management profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 3523","type":"specification","body":"IETF","designation":"RFC 3523","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3523.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3523.txt","https://www.rfc-editor.org/rfc/rfc3523.pdf"],"folder":"IETF/RFC-3523","files":{"txt":{"path":"standards/IETF/RFC-3523/RFC-3523.txt","sha256":"908a2d4ecadb6c4429a64888b1cd74db88996c16492e5896388fccf67009c491"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the topology naming conventions that are to be\n used in reference to Internet Emergency Preparedness (IEPREP) phone\n calls. These naming conventions should be used to focus the IEPREP\n Working Group during discussions and when writing requirements, gap\n analysis and other solutions documents.","scope_keywords":["3523","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null}],"search_text":"IETF RFC 3523 This document defines the topology naming conventions that are to be\n used in reference to Internet Emergency Preparedness (IEPREP) phone\n calls. These naming conventions should be used to focus the IEPREP\n Working Group during discussions and when writing requirements, gap\n analysis and other solutions documents. 3523 path nested-reference unchanged"},{"id":"IETF RFC 3529","type":"specification","body":"IETF","designation":"RFC 3529","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3529.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3529.txt","https://www.rfc-editor.org/rfc/rfc3529.pdf"],"folder":"IETF/RFC-3529","files":{"txt":{"path":"standards/IETF/RFC-3529/RFC-3529.txt","sha256":"585d8c354c69245eba6a8348a60e93dd76b9fd3adba332799aefa3f950567010"}},"tags":["nested-reference","unchanged"],"summary":"XML-RPC is an Extensible Markup Language-Remote Procedure Calling\n protocol that works over the Internet. It defines an XML format for\n messages that are transfered between clients and servers using HTTP.\n An XML-RPC message encodes either a procedure to be invoked by the\n server, along with the parameters to use in the invocation, or the\n result of an invocation. Procedure parameters and results can be\n scalars, numbers, strings, dates, etc.; they can also be complex\n record and list structures.\n\n This document specifies a how to use the Blocks Extensible Exchange\n Protocol (BEEP) to transfer messages encoded in the XML-RPC format\n between clients and servers.","scope_keywords":["3529","attribute","http","identification","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 3529 XML-RPC is an Extensible Markup Language-Remote Procedure Calling\n protocol that works over the Internet. It defines an XML format for\n messages that are transfered between clients and servers using HTTP.\n An XML-RPC message encodes either a procedure to be invoked by the\n server, along with the parameters to use in the invocation, or the\n result of an invocation. Procedure parameters and results can be\n scalars, numbers, strings, dates, etc.; they can also be complex\n record and list structures.\n\n This document specifies a how to use the Blocks Extensible Exchange\n Protocol (BEEP) to transfer messages encoded in the XML-RPC format\n between clients and servers. 3529 attribute http identification path profile nested-reference unchanged"},{"id":"IETF RFC 353","type":"specification","body":"IETF","designation":"RFC 353","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc353.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc353.txt","https://www.rfc-editor.org/rfc/rfc353.pdf"],"folder":"IETF/RFC-353","files":{"txt":{"path":"standards/IETF/RFC-353/RFC-353.txt","sha256":"fc7679f3fb7c7fc7c8444484cf370d53410db6b18389dda5ee6cacccb9cb9ba0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: 353 BBN\nNIC #10595 12 June 1972\nCategories: F, G.3\nUpdates: RFC #344\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from May 22 to\n June 2.\n\n No testing was done on Memorial Day, which Massachusetts celebrated\n on May 29. No testing was done on May 31 and June 1 due to an\n attempt to install the new IMP system.\n\n Three new terminal IMPs were installed during this interval. On June\n 1, Terminal IMP #155 was installed at Fort Belvoir in Fairfax,\n Virginia; on June 3, Terminal IMP #154 was installed at SAAC (Seismic\n Array Analysis Center) in Alexandria, Virginia; and on June 5,\n Terminal IMP #153 was installed at NOAA (National Oceanic Analysis\n Agency) in Boulder, Colorado.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Host","scope_keywords":["353"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 353 Network Working Group Ellen Westheimer\nRequest for Comments: 353 BBN\nNIC #10595 12 June 1972\nCategories: F, G.3\nUpdates: RFC #344\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from May 22 to\n June 2.\n\n No testing was done on Memorial Day, which Massachusetts celebrated\n on May 29. No testing was done on May 31 and June 1 due to an\n attempt to install the new IMP system.\n\n Three new terminal IMPs were installed during this interval. On June\n 1, Terminal IMP #155 was installed at Fort Belvoir in Fairfax,\n Virginia; on June 3, Terminal IMP #154 was installed at SAAC (Seismic\n Array Analysis Center) in Alexandria, Virginia; and on June 5,\n Terminal IMP #153 was installed at NOAA (National Oceanic Analysis\n Agency) in Boulder, Colorado.\n\n Several Hosts are currently excluded from the daily testing. These\n Hosts fall into two categories:\n\n 1) Host 353 nested-reference unchanged"},{"id":"IETF RFC 3532","type":"specification","body":"IETF","designation":"RFC 3532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3532.txt","https://www.rfc-editor.org/rfc/rfc3532.pdf"],"folder":"IETF/RFC-3532","files":{"txt":{"path":"standards/IETF/RFC-3532/RFC-3532.txt","sha256":"1bc38743d9d648b98879132389ad051325564e92b678412e5f9f062951a61cd7"}},"tags":["nested-reference","unchanged"],"summary":"This document identifies a set of requirements for the mechanisms\n used to dynamically reallocate the resources of a switching element\n (e.g., an ATM switch) to its partitions. These requirements are\n particularly critical in the case of an operator creating a switch\n partition and then leasing control of that partition to a third\n party.","scope_keywords":["3532","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3654","folder":"IETF/RFC-3654","source":"IETF/RFC-3654/RFC-3654.txt","version":null}],"search_text":"IETF RFC 3532 This document identifies a set of requirements for the mechanisms\n used to dynamically reallocate the resources of a switching element\n (e.g., an ATM switch) to its partitions. These requirements are\n particularly critical in the case of an operator creating a switch\n partition and then leasing control of that partition to a third\n party. 3532 management policy nested-reference unchanged"},{"id":"IETF RFC 6244","type":"specification","body":"IETF","designation":"RFC 6244","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6244.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6244.txt","https://www.rfc-editor.org/rfc/rfc6244.pdf"],"folder":"IETF/RFC-6244","files":{"txt":{"path":"standards/IETF/RFC-6244/RFC-6244.txt","sha256":"59f9821ea05278ebd28204c4893ae7249a1769b5b013140bab9911d841e3802d"}},"tags":["nested-reference","unchanged"],"summary":"The Network Configuration Protocol (NETCONF) gives access to native\n capabilities of the devices within a network, defining methods for\n manipulating configuration databases, retrieving operational data,\n and invoking specific operations. YANG provides the means to define\n the content carried via NETCONF, both data and operations. Using\n both technologies, standard modules can be defined to give\n interoperability and commonality to devices, while still allowing\n devices to express their unique capabilities.\n\n This document describes how NETCONF and YANG help build network\n management applications that meet the needs of network operators.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commu","scope_keywords":["6244","http","license","management","qualified","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 8342","folder":"IETF/RFC-8342","source":"IETF/RFC-8342/RFC-8342.txt","version":null}],"search_text":"IETF RFC 6244 The Network Configuration Protocol (NETCONF) gives access to native\n capabilities of the devices within a network, defining methods for\n manipulating configuration databases, retrieving operational data,\n and invoking specific operations. YANG provides the means to define\n the content carried via NETCONF, both data and operations. Using\n both technologies, standard modules can be defined to give\n interoperability and commonality to devices, while still allowing\n devices to express their unique capabilities.\n\n This document describes how NETCONF and YANG help build network\n management applications that meet the needs of network operators.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF commu 6244 http license management qualified subject trust nested-reference unchanged"},{"id":"IETF RFC 414","type":"specification","body":"IETF","designation":"RFC 414","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc414.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc414.txt","https://www.rfc-editor.org/rfc/rfc414.pdf"],"folder":"IETF/RFC-414","files":{"txt":{"path":"standards/IETF/RFC-414/RFC-414.txt","sha256":"b47a394f0538155850bc39f0684a3216d72392c9005a9d222bab3ab75989bd8e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Bhushan\nRequest for Comments: 414 MIT-MAC\nUpdates: RFC 354, RFC 385 29 November 1972\nNIC: 12406\n\n FILE TRANSFER PROTOCOL (FTP) STATUS AND FURTHER COMMENTS\n\n A number of HOSTs have working server and user FTPs now. The\n following reflects the status of FTP implementations to the best of\n my knowledge:\n\n BBN(A and B), SRI-ARC, UTAH, CASE, USC-ISI, CCA, MIT-AI MIT-\n Mathlab, MIT-DMCG, CMU, AMES-67, and SU-AI have fully functionning\n server and user FTPs.\n\n MIT-Multics has user and server FTPs but the server does not\n listen on socket 3 (it can be started by normal login and the\n command ftp_server). UCSB will soon have user and server FTP's.\n\n The servers at all the TENEX systems are more or less identical\n (developed by Bob Clements at BBN). The servers at MIT-AI and MIT-ML\n are also identical (developed by Pitts Jarvis of MAC). Others\n currently involved with FTP ","scope_keywords":["414","crl","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 448","folder":"IETF/RFC-448","source":"IETF/RFC-448/RFC-448.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 414 Network Working Group A. Bhushan\nRequest for Comments: 414 MIT-MAC\nUpdates: RFC 354, RFC 385 29 November 1972\nNIC: 12406\n\n FILE TRANSFER PROTOCOL (FTP) STATUS AND FURTHER COMMENTS\n\n A number of HOSTs have working server and user FTPs now. The\n following reflects the status of FTP implementations to the best of\n my knowledge:\n\n BBN(A and B), SRI-ARC, UTAH, CASE, USC-ISI, CCA, MIT-AI MIT-\n Mathlab, MIT-DMCG, CMU, AMES-67, and SU-AI have fully functionning\n server and user FTPs.\n\n MIT-Multics has user and server FTPs but the server does not\n listen on socket 3 (it can be started by normal login and the\n command ftp_server). UCSB will soon have user and server FTP's.\n\n The servers at all the TENEX systems are more or less identical\n (developed by Bob Clements at BBN). The servers at MIT-AI and MIT-ML\n are also identical (developed by Pitts Jarvis of MAC). Others\n currently involved with FTP  414 crl path presentation nested-reference unchanged"},{"id":"IETF RFC 430","type":"specification","body":"IETF","designation":"RFC 430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc430.txt","https://www.rfc-editor.org/rfc/rfc430.pdf"],"folder":"IETF/RFC-430","files":{"txt":{"path":"standards/IETF/RFC-430/RFC-430.txt","sha256":"173426248542f106e9a61dbdde48616c86e57894e471a7982f77cbd605d3ca42"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braden\nRequest for Comments: 430 CCN/UCLA\nNIC: 13299 7 February 1973\n\n COMMENTS ON FILE TRANSFER PROTOCOL\n\n On January 23, 1973, Jon Postel (NMC), Eric Harslem (RAND), Stephen\n Wolfe (CCN), and Robert Braden (CCN), held and informal meeting at\n UCLA on FTP. This RFC generally reports the consensus of that\n meeting on the following issues: server-server transfers (ref. RFC\n 438 by Thomas and Clements); site-dependent information; and\n miscellaneous questions/disagreements with RFC 354, 385, and 414.\n There was also a discussion of the print file muddle, but that\n subject is addressed in a separate RFC, No. 448.\n\nMiscellaneous Comments on FTP\n\n 1. RFC 385, P. 1 (3)\n\n The question of print files will be discussed at length in another\n RFC. However, we did feel that the word \"still\" on the second\n line from the bottom of Page 1 is gratuitous.\n\n 2. RFC 385, P. 2 (5.)\n","scope_keywords":["430","attribute","attributes","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 451","folder":"IETF/RFC-451","source":"IETF/RFC-451/RFC-451.txt","version":null},{"body":"IETF","designation":"RFC 463","folder":"IETF/RFC-463","source":"IETF/RFC-463/RFC-463.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 430 Network Working Group R. Braden\nRequest for Comments: 430 CCN/UCLA\nNIC: 13299 7 February 1973\n\n COMMENTS ON FILE TRANSFER PROTOCOL\n\n On January 23, 1973, Jon Postel (NMC), Eric Harslem (RAND), Stephen\n Wolfe (CCN), and Robert Braden (CCN), held and informal meeting at\n UCLA on FTP. This RFC generally reports the consensus of that\n meeting on the following issues: server-server transfers (ref. RFC\n 438 by Thomas and Clements); site-dependent information; and\n miscellaneous questions/disagreements with RFC 354, 385, and 414.\n There was also a discussion of the print file muddle, but that\n subject is addressed in a separate RFC, No. 448.\n\nMiscellaneous Comments on FTP\n\n 1. RFC 385, P. 1 (3)\n\n The question of print files will be discussed at length in another\n RFC. However, we did feel that the word \"still\" on the second\n line from the bottom of Page 1 is gratuitous.\n\n 2. RFC 385, P. 2 (5.)\n 430 attribute attributes subject nested-reference unchanged"},{"id":"IETF RFC 438","type":"specification","body":"IETF","designation":"RFC 438","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc438.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc438.txt","https://www.rfc-editor.org/rfc/rfc438.pdf"],"folder":"IETF/RFC-438","files":{"txt":{"path":"standards/IETF/RFC-438/RFC-438.txt","sha256":"0f55b44fa0045400850b6ce91e8b9e2fc52e35d99b5191c2c11d9cab482cb526"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Thomas\nRequest for Comments: 438 B. Clements\nNIC: 13770 BBN-TENEX\nReferences: 354,385,414,418 15 January 1973\n\n FTP Server-Server Interaction\n\n The current ARPANET File Transfer Protocol as specified by RFC 354\n and updated by RFC's 385, 414 and 418 allows for \"third host\"\n participation but does not specify a mechanism by which the process\n at the third site may be the FTP server at that site. This RFC\n suggests a simple extension to FTP which would allow an FTP user\n process at one site to arrange for FTP server processes at other\n sites to act cooperatively on its behalf.\n\n Such server-server cooperation may appear to be of limited utility.\n Consider, however, the requirements placed on FTP by a Resource\n Sharing Executive (RSEXEC) program - a command language interpreter\n which extends the range of a user's commands beyond the boundaries of\n the user's local ","scope_keywords":["438","crl","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 438 Network Working Group B. Thomas\nRequest for Comments: 438 B. Clements\nNIC: 13770 BBN-TENEX\nReferences: 354,385,414,418 15 January 1973\n\n FTP Server-Server Interaction\n\n The current ARPANET File Transfer Protocol as specified by RFC 354\n and updated by RFC's 385, 414 and 418 allows for \"third host\"\n participation but does not specify a mechanism by which the process\n at the third site may be the FTP server at that site. This RFC\n suggests a simple extension to FTP which would allow an FTP user\n process at one site to arrange for FTP server processes at other\n sites to act cooperatively on its behalf.\n\n Such server-server cooperation may appear to be of limited utility.\n Consider, however, the requirements placed on FTP by a Resource\n Sharing Executive (RSEXEC) program - a command language interpreter\n which extends the range of a user's commands beyond the boundaries of\n the user's local  438 crl path qualified nested-reference unchanged"},{"id":"IETF RFC 448","type":"specification","body":"IETF","designation":"RFC 448","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc448.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc448.txt","https://www.rfc-editor.org/rfc/rfc448.pdf"],"folder":"IETF/RFC-448","files":{"txt":{"path":"standards/IETF/RFC-448/RFC-448.txt","sha256":"65c31c9f1bf450517b9c0a67b73ea3993a4d0a833bff8f1e25fbe528b714d9cf"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP R.T. Braden\nREQUEST FOR COMMENT NO. 448 UCLA/CCN\nNIC #13299 February 27, 1973\nUPDATES: RFC 354, 385, 454\n\n PRINT FILES IN FTP\n\nINTRODUCTION\n------------\n\n Many of those who contributed to the definition of the FTP and RJE\nprotocols have expressed varying degrees of uncertainty or unhappiness\nwith the \"print file\" type in FTP. This RFC is intended to review the\nproblem of print files in preparation for the forthcoming FTP meeting.\nOriginally drafted on the basis of RFC 385, this RFC has been updated to\nreflect the terminology of the latest FTP document 454. (Changing the\nterminology doesn't solve the problem!)\n\n It turns out that the Network RJE protocol as presently defined (see\nNIC 12112) seems to force a particular interpretation of print files in\nFTP and in fact, this interpretation is probably different from the one\nassumed by most FTP implementors.\n\nVERTICAL FO","scope_keywords":["448","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 448 NETWORK WORKING GROUP R.T. Braden\nREQUEST FOR COMMENT NO. 448 UCLA/CCN\nNIC #13299 February 27, 1973\nUPDATES: RFC 354, 385, 454\n\n PRINT FILES IN FTP\n\nINTRODUCTION\n------------\n\n Many of those who contributed to the definition of the FTP and RJE\nprotocols have expressed varying degrees of uncertainty or unhappiness\nwith the \"print file\" type in FTP. This RFC is intended to review the\nproblem of print files in preparation for the forthcoming FTP meeting.\nOriginally drafted on the basis of RFC 385, this RFC has been updated to\nreflect the terminology of the latest FTP document 454. (Changing the\nterminology doesn't solve the problem!)\n\n It turns out that the Network RJE protocol as presently defined (see\nNIC 12112) seems to force a particular interpretation of print files in\nFTP and in fact, this interpretation is probably different from the one\nassumed by most FTP implementors.\n\nVERTICAL FO 448 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 501","type":"specification","body":"IETF","designation":"RFC 501","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc501.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc501.txt","https://www.rfc-editor.org/rfc/rfc501.pdf"],"folder":"IETF/RFC-501","files":{"txt":{"path":"standards/IETF/RFC-501/RFC-501.txt","sha256":"e48406eed73c0806546c91078414d7cc0281a603413a6e24e8d2f48923badb77"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Pogran\nRequest for Comments: 501 MIT-Multics\nNIC: 15718 11 May 1973\n\n Un-Muddling \"Free File Transfer\"\n\n As the ARPA Network begin to mature, we find ourselves addressing\n issues and concepts deliberately put off and left untouched at\n earlier stages of Network development. Among the issues now coming\n to the fore are access control, user authentication, and accounting.\n These issues arise immediately out of efforts to develop uniform\n methods for providing limited \"free\" access to the File Transfer\n Servers of the host systems, to meet user needs for mail transmission\n and similar services.\n\n Several proposals have been made, described by such phrases as\n \"login-less mail\", \"'free' accounts\", \"free file transfer\", etc.\n These proposals inevitably have imbedded in them some particular\n notion of how such things as access control and user authentication\n are accom","scope_keywords":["501","authentication","path","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 505","folder":"IETF/RFC-505","source":"IETF/RFC-505/RFC-505.txt","version":null}],"search_text":"IETF RFC 501 Network Working Group K. Pogran\nRequest for Comments: 501 MIT-Multics\nNIC: 15718 11 May 1973\n\n Un-Muddling \"Free File Transfer\"\n\n As the ARPA Network begin to mature, we find ourselves addressing\n issues and concepts deliberately put off and left untouched at\n earlier stages of Network development. Among the issues now coming\n to the fore are access control, user authentication, and accounting.\n These issues arise immediately out of efforts to develop uniform\n methods for providing limited \"free\" access to the File Transfer\n Servers of the host systems, to meet user needs for mail transmission\n and similar services.\n\n Several proposals have been made, described by such phrases as\n \"login-less mail\", \"'free' accounts\", \"free file transfer\", etc.\n These proposals inevitably have imbedded in them some particular\n notion of how such things as access control and user authentication\n are accom 501 authentication path validation nested-reference unchanged"},{"id":"IETF RFC 683","type":"specification","body":"IETF","designation":"RFC 683","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc683.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc683.txt","https://www.rfc-editor.org/rfc/rfc683.pdf"],"folder":"IETF/RFC-683","files":{"txt":{"path":"standards/IETF/RFC-683/RFC-683.txt","sha256":"ef59ad82cb665c0481c42b747f50eca0a203ceda274446f5a1f60a315adfb70e"}},"tags":["nested-reference","unchanged"],"summary":"RFC 683, NIC 32251\n\n FTPSRV - TENEX FTP EXTENSIONS FOR PAGED FILES\n\n R. Clements - BBN - 3 April 75\n\n1 Introduction\n\n In response to a long-known need for the ability to transfer TENEX paged\nfiles over the net via FTP, the TENEX FTP implementation has been extended.\n\n This implementation is an extension to the \"OLD\" protocol (RFC 354). It\nwas built after useful discussions with Postel, Neigus, et al. I do not mean\nto imply that they agreed that this implementation is correct, nor for that\nmatter do I feel it is correct. A \"correct\" implementation will be negotiated\nand implemented in the \"NEW\" protocol (RFC 542), if funding ever appears for\nthat task.\n\n2 The Problem(s)\n\n This extension attacks two separate problems: Network reliability and\nTENEX disk file format's incompatibility with FTP. A checksummed and\nblock-sequence-numbered transmission mode is seriously needed, in my opinion.\nThi","scope_keywords":["683","attribute","attributes","crl","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null}],"search_text":"IETF RFC 683 RFC 683, NIC 32251\n\n FTPSRV - TENEX FTP EXTENSIONS FOR PAGED FILES\n\n R. Clements - BBN - 3 April 75\n\n1 Introduction\n\n In response to a long-known need for the ability to transfer TENEX paged\nfiles over the net via FTP, the TENEX FTP implementation has been extended.\n\n This implementation is an extension to the \"OLD\" protocol (RFC 354). It\nwas built after useful discussions with Postel, Neigus, et al. I do not mean\nto imply that they agreed that this implementation is correct, nor for that\nmatter do I feel it is correct. A \"correct\" implementation will be negotiated\nand implemented in the \"NEW\" protocol (RFC 542), if funding ever appears for\nthat task.\n\n2 The Problem(s)\n\n This extension attacks two separate problems: Network reliability and\nTENEX disk file format's incompatibility with FTP. A checksummed and\nblock-sequence-numbered transmission mode is seriously needed, in my opinion.\nThi 683 attribute attributes crl key path presentation nested-reference unchanged"},{"id":"IETF RFC 691","type":"specification","body":"IETF","designation":"RFC 691","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc691.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc691.txt","https://www.rfc-editor.org/rfc/rfc691.pdf"],"folder":"IETF/RFC-691","files":{"txt":{"path":"standards/IETF/RFC-691/RFC-691.txt","sha256":"2134d68030cc4164a0413d6da596cd0e2a71d92c5f1e6608dbaa05dbc2443017"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 691 BH 6-JUN-75 23:15 32700\nOne More Try on the FTP\n\n Brian Harvey\n SU-AI\nRe: File Transfer Protocol May 28, 1975\nRef: RFC 354, 385, 414, 448, 454, 630, 542, 640 1\n\n One More Try on the FTP 2\n\n This is a slight revision of RFC 686, mainly differing in the\n discussion of print files. Reading several RFCs that I (sigh)\n never heard of before writing 686 has convinced me that although\n I was right all along it was for the wrong reasons. The list of\n reply codes is also slightly different to reflect the four lists\n in RFCs 354, 454, 542, and 640 more completely. Let me also\n suggest that if there are no objections before June 1, everyone\n take it as official that HELP should return 200, that SRVR should\n be used as discussed below, and that \"permanent\" 4xx errors be\n changed to 5xx. And thanks to Jon Postel who just spent all\n evening helping me straighten this all out. 2a\n\n Aside f","scope_keywords":["691","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 743","folder":"IETF/RFC-743","source":"IETF/RFC-743/RFC-743.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 775","folder":"IETF/RFC-775","source":"IETF/RFC-775/RFC-775.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 691 NWG/RFC# 691 BH 6-JUN-75 23:15 32700\nOne More Try on the FTP\n\n Brian Harvey\n SU-AI\nRe: File Transfer Protocol May 28, 1975\nRef: RFC 354, 385, 414, 448, 454, 630, 542, 640 1\n\n One More Try on the FTP 2\n\n This is a slight revision of RFC 686, mainly differing in the\n discussion of print files. Reading several RFCs that I (sigh)\n never heard of before writing 686 has convinced me that although\n I was right all along it was for the wrong reasons. The list of\n reply codes is also slightly different to reflect the four lists\n in RFCs 354, 454, 542, and 640 more completely. Let me also\n suggest that if there are no objections before June 1, everyone\n take it as official that HELP should return 200, that SRVR should\n be used as discussed below, and that \"permanent\" 4xx errors be\n changed to 5xx. And thanks to Jon Postel who just spent all\n evening helping me straighten this all out. 2a\n\n Aside f 691 subject nested-reference unchanged"},{"id":"IETF RFC 5294","type":"specification","body":"IETF","designation":"RFC 5294","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5294.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5294.txt","https://www.rfc-editor.org/rfc/rfc5294.pdf"],"folder":"IETF/RFC-5294","files":{"txt":{"path":"standards/IETF/RFC-5294/RFC-5294.txt","sha256":"b177160204b91f418652891c0d5d0cce7c98223161c27ca8f56493254d83aa08"}},"tags":["nested-reference","unchanged"],"summary":"This memo complements the list of multicast infrastructure security\n threat analysis documents by describing Protocol Independent\n Multicast (PIM) threats specific to router interfaces connecting\n hosts.","scope_keywords":["5294","authorization","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5796","folder":"IETF/RFC-5796","source":"IETF/RFC-5796/RFC-5796.txt","version":null},{"body":"IETF","designation":"RFC 7761","folder":"IETF/RFC-7761","source":"IETF/RFC-7761/RFC-7761.txt","version":null}],"search_text":"IETF RFC 5294 This memo complements the list of multicast infrastructure security\n threat analysis documents by describing Protocol Independent\n Multicast (PIM) threats specific to router interfaces connecting\n hosts. 5294 authorization management nested-reference unchanged"},{"id":"IETF RFC 4337","type":"specification","body":"IETF","designation":"RFC 4337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4337.txt","https://www.rfc-editor.org/rfc/rfc4337.pdf"],"folder":"IETF/RFC-4337","files":{"txt":{"path":"standards/IETF/RFC-4337/RFC-4337.txt","sha256":"c47e7a1964e669f490501aabece73c8c8b7548c6ea16498d1478a1e8b853353c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the standard MIME types associated with MP4\n files. It also recommends use of registered MIME types according to\n the type of contents.","scope_keywords":["4337","algorithm","algorithms","delivery","http","management","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null}],"search_text":"IETF RFC 4337 This document defines the standard MIME types associated with MP4\n files. It also recommends use of registered MIME types according to\n the type of contents. 4337 algorithm algorithms delivery http management presentation registered nested-reference unchanged"},{"id":"IETF RFC 5457","type":"specification","body":"IETF","designation":"RFC 5457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5457.txt","https://www.rfc-editor.org/rfc/rfc5457.pdf"],"folder":"IETF/RFC-5457","files":{"txt":{"path":"standards/IETF/RFC-5457/RFC-5457.txt","sha256":"3504d18d01c422e8b7e4a68d9b81126e2ff01f7089fe4001d040dd1ebf3cb04f"}},"tags":["nested-reference","unchanged"],"summary":"This document establishes the IANA registries for IAX, the Inter-\n Asterisk eXchange protocol, an application-layer control and media\n protocol for creating, modifying, and terminating multimedia sessions\n over Internet Protocol (IP) networks. IAX was developed by the open\n source community for the Asterisk PBX and is targeted primarily at\n Voice over Internet Protocol (VoIP) call control, but it can be used\n with streaming video or any other type of multimedia.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate","scope_keywords":["5457","authentication","encryption","http","identification","license","management","presentation","registered","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null}],"search_text":"IETF RFC 5457 This document establishes the IANA registries for IAX, the Inter-\n Asterisk eXchange protocol, an application-layer control and media\n protocol for creating, modifying, and terminating multimedia sessions\n over Internet Protocol (IP) networks. IAX was developed by the open\n source community for the Asterisk PBX and is targeted primarily at\n Voice over Internet Protocol (VoIP) call control, but it can be used\n with streaming video or any other type of multimedia.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate 5457 authentication encryption http identification license management presentation registered risk subject trust nested-reference unchanged"},{"id":"IETF RFC 8852","type":"specification","body":"IETF","designation":"RFC 8852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8852.txt","https://www.rfc-editor.org/rfc/rfc8852.pdf"],"folder":"IETF/RFC-8852","files":{"pdf":{"path":"standards/IETF/RFC-8852/RFC-8852.pdf","sha256":"2f1fa8b82b2ad566c90b4c6379fa10a33be24f9cbb876f6ddaf7174c94c4f286"},"txt":{"path":"standards/IETF/RFC-8852/RFC-8852.txt","sha256":"135ad34e144f71f733a4898ffa08a4dddc6f694c3363f287ab731e4b342c8c48"}},"tags":["nested-reference","unchanged"],"summary":"This document defines and registers two new Real-time Transport\n Control Protocol (RTCP) Stream Identifier Source Description (SDES)\n items. One, named RtpStreamId, is used for unique identification of\n RTP streams. The other, RepairedRtpStreamId, can be used to identify\n which stream is to be repaired using a redundancy RTP stream.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8852.\n","scope_keywords":["8852","http","https","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8829","folder":"IETF/RFC-8829","source":"IETF/RFC-8829/RFC-8829.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 8852 This document defines and registers two new Real-time Transport\n Control Protocol (RTCP) Stream Identifier Source Description (SDES)\n items. One, named RtpStreamId, is used for unique identification of\n RTP streams. The other, RepairedRtpStreamId, can be used to identify\n which stream is to be repaired using a redundancy RTP stream.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8852.\n 8852 http https identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 3558","type":"specification","body":"IETF","designation":"RFC 3558","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3558.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3558.txt","https://www.rfc-editor.org/rfc/rfc3558.pdf"],"folder":"IETF/RFC-3558","files":{"txt":{"path":"standards/IETF/RFC-3558/RFC-3558.txt","sha256":"d4df3d44363cc5f09a85c4a7b634ad65785d744452a46bb7cbabfcd79d504f6a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the RTP payload format for Enhanced Variable\n Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV) Speech.\n Two sub-formats are specified for different application scenarios. A\n bundled/interleaved format is included to reduce the effect of packet\n loss on speech quality and amortize the overhead of the RTP header\n over more than one speech frame. A non-bundled format is also\n supported for conversational applications.","scope_keywords":["3558","algorithm","algorithms","key","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null}],"search_text":"IETF RFC 3558 This document describes the RTP payload format for Enhanced Variable\n Rate Codec (EVRC) Speech and Selectable Mode Vocoder (SMV) Speech.\n Two sub-formats are specified for different application scenarios. A\n bundled/interleaved format is included to reduce the effect of packet\n loss on speech quality and amortize the overhead of the RTP header\n over more than one speech frame. A non-bundled format is also\n supported for conversational applications. 3558 algorithm algorithms key validation nested-reference unchanged"},{"id":"IETF RFC 3664","type":"specification","body":"IETF","designation":"RFC 3664","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3664.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3664.txt","https://www.rfc-editor.org/rfc/rfc3664.pdf"],"folder":"IETF/RFC-3664","files":{"txt":{"path":"standards/IETF/RFC-3664/RFC-3664.txt","sha256":"4b582e960277e49bd9f17196c36c6fac04d2e86a7b13cc7d40d7d9d4f622b4e6"}},"tags":["nested-reference","unchanged"],"summary":"Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function derived from the Advanced Encryption Standard\n (AES). This document describes such an algorithm, called AES-XCBC-\n PRF-128.\n\n1. Introduction\n\n [AES-XCBC-MAC] describes a method to use the Advanced Encryption\n Standard (AES) as a message authentication code (MAC) whose output is\n 96 bits long. While 96 bits is considered appropriate for a MAC, it\n is too short to be useful as a long-lived pseudo-random (PRF) in\n either IKE version 1 or version 2. Both versions of IKE use the PRF\n to create keys in a fashion that is dependent on the length of the\n output of the PRF. Using a PRF that has 96 bits of output creates\n keys that are easier to attack with brute force than a PRF that uses\n 128 bits of output.\n\n Fortunately, there is a very simple method to use much of [AES-XCBC-\n MAC] as a PRF whose output is 128","scope_keywords":["3664","algorithm","authentication","encryption","key","keys","license","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4109","folder":"IETF/RFC-4109","source":"IETF/RFC-4109/RFC-4109.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4307","folder":"IETF/RFC-4307","source":"IETF/RFC-4307/RFC-4307.txt","version":null},{"body":"IETF","designation":"RFC 4308","folder":"IETF/RFC-4308","source":"IETF/RFC-4308/RFC-4308.txt","version":null},{"body":"IETF","designation":"RFC 4434","folder":"IETF/RFC-4434","source":"IETF/RFC-4434/RFC-4434.txt","version":null},{"body":"IETF","designation":"RFC 4615","folder":"IETF/RFC-4615","source":"IETF/RFC-4615/RFC-4615.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null}],"search_text":"IETF RFC 3664 Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function derived from the Advanced Encryption Standard\n (AES). This document describes such an algorithm, called AES-XCBC-\n PRF-128.\n\n1. Introduction\n\n [AES-XCBC-MAC] describes a method to use the Advanced Encryption\n Standard (AES) as a message authentication code (MAC) whose output is\n 96 bits long. While 96 bits is considered appropriate for a MAC, it\n is too short to be useful as a long-lived pseudo-random (PRF) in\n either IKE version 1 or version 2. Both versions of IKE use the PRF\n to create keys in a fashion that is dependent on the length of the\n output of the PRF. Using a PRF that has 96 bits of output creates\n keys that are easier to attack with brute force than a PRF that uses\n 128 bits of output.\n\n Fortunately, there is a very simple method to use much of [AES-XCBC-\n MAC] as a PRF whose output is 128 3664 algorithm authentication encryption key keys license management nested-reference unchanged"},{"id":"IETF RFC 4434","type":"specification","body":"IETF","designation":"RFC 4434","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4434.txt","https://www.rfc-editor.org/rfc/rfc4434.pdf"],"folder":"IETF/RFC-4434","files":{"txt":{"path":"standards/IETF/RFC-4434/RFC-4434.txt","sha256":"8c1f5367b301eab3c8309a639a02dd3eacffc3c1dbb15b8127818b66255e6b8b"}},"tags":["nested-reference","unchanged"],"summary":"Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function derived from the Advanced Encryption Standard\n (AES). This document describes such an algorithm, called\n AES-XCBC-PRF-128.\n\n1. Introduction\n\n [AES-XCBC-MAC] describes a method to use the Advanced Encryption\n Standard (AES) as a message authentication code (MAC) whose output is\n 96 bits long. While 96 bits is considered appropriate for a MAC, it\n is too short to be useful as a long-lived pseudo-random function\n (PRF) in either IKE version 1 or version 2. Both versions of IKE use\n the PRF to create keys in a fashion that is dependent on the length\n of the output of the PRF. Using a PRF that has 96 bits of output\n creates keys that are easier to attack with brute force than a PRF\n that uses 128 bits of output.\n\n Fortunately, there is a very simple method to use much of\n [AES-XCBC-MAC] as a PRF whose output","scope_keywords":["4434","algorithm","authentication","encryption","key","keys","license","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4615","folder":"IETF/RFC-4615","source":"IETF/RFC-4615/RFC-4615.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4894","folder":"IETF/RFC-4894","source":"IETF/RFC-4894/RFC-4894.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4434 Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function derived from the Advanced Encryption Standard\n (AES). This document describes such an algorithm, called\n AES-XCBC-PRF-128.\n\n1. Introduction\n\n [AES-XCBC-MAC] describes a method to use the Advanced Encryption\n Standard (AES) as a message authentication code (MAC) whose output is\n 96 bits long. While 96 bits is considered appropriate for a MAC, it\n is too short to be useful as a long-lived pseudo-random function\n (PRF) in either IKE version 1 or version 2. Both versions of IKE use\n the PRF to create keys in a fashion that is dependent on the length\n of the output of the PRF. Using a PRF that has 96 bits of output\n creates keys that are easier to attack with brute force than a PRF\n that uses 128 bits of output.\n\n Fortunately, there is a very simple method to use much of\n [AES-XCBC-MAC] as a PRF whose output 4434 algorithm authentication encryption key keys license management subject nested-reference unchanged"},{"id":"IETF RFC 560","type":"specification","body":"IETF","designation":"RFC 560","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc560.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc560.txt","https://www.rfc-editor.org/rfc/rfc560.pdf"],"folder":"IETF/RFC-560","files":{"pdf":{"path":"standards/IETF/RFC-560/RFC-560.pdf","sha256":"8ce0c8f7351bb3712c2b8393bf22a9192a6ebc67968c485b5ac724782fa1c5d9"},"txt":{"path":"standards/IETF/RFC-560/RFC-560.txt","sha256":"f51fbeb0cb223542a7e059ec79bafbcc235c4fc317313d8dfa1e1934f90926ca"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker\nRequest for Comments: 560 J. Postel\nCategory: Protocols, TELNET 20 August 1973\nNIC: 18492\n\n Remote Controlled Transmission & Echoing TELNET Option\n\n Currently, a terminal in character-at-a-time transmission and\n foreign-host echo causes four Network Messages for each character\n struck. (The character sent from local to foreign host; its RFNM;\n the echoed character sent from the foreign to the local host; and its\n RFNM.)\n\n By eliminating most echoing (1/2 as many messages) and packaging the\n characters into useful units (assuming an average of five character\n per unit; therefore another 80 per cent reduction), it is believed\n that almost a 90 per cent reduction in character-mode interactive\n Network terminal traffic can be attained.\n\n The packaging of characters and elimination of foreign echoing should\n also lessen the load placed on the foreign hosts.\n\n1","scope_keywords":["560","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 560 Network Working Group D. Crocker\nRequest for Comments: 560 J. Postel\nCategory: Protocols, TELNET 20 August 1973\nNIC: 18492\n\n Remote Controlled Transmission & Echoing TELNET Option\n\n Currently, a terminal in character-at-a-time transmission and\n foreign-host echo causes four Network Messages for each character\n struck. (The character sent from local to foreign host; its RFNM;\n the echoed character sent from the foreign to the local host; and its\n RFNM.)\n\n By eliminating most echoing (1/2 as many messages) and packaging the\n characters into useful units (assuming an average of five character\n per unit; therefore another 80 per cent reduction), it is believed\n that almost a 90 per cent reduction in character-mode interactive\n Network terminal traffic can be attained.\n\n The packaging of characters and elimination of foreign echoing should\n also lessen the load placed on the foreign hosts.\n\n1 560 path nested-reference unchanged"},{"id":"IETF RFC 726","type":"specification","body":"IETF","designation":"RFC 726","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc726.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc726.txt","https://www.rfc-editor.org/rfc/rfc726.pdf"],"folder":"IETF/RFC-726","files":{"txt":{"path":"standards/IETF/RFC-726/RFC-726.txt","sha256":"a4820b4ec7a4c3ce4f341b2b3a2c5bd6c4faacd336b67adcd00bff7b1c11ec92"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 726 JBP DHC 8-MAR-77 08:29 39237\n Remote Controlled Transmission & Echoing Telnet Option\n\n Network Working Group Jon Postel & Dave Crocker\n Request for Comments: 726 SRI-ARC UC Irvine\n NIC: 39237 8 March 1977\n\n \n \n Remote Controlled Transmssion and Echoing Telnet Option\n\n 1\n\n 1. Command name and code: 2\n\n RCTE 7 2a\n\n 2. Command meanings: 3\n\n IAC WILL RCTE 3a\n\n The sender of this command REQUESTS or AGREES to use\n the RCTE option, and will send instructions for\n controlling the other side's terminal printer. 3a1\n\n IAC WON'T RCTE 3b\n\n The sender of this option REFUSES to send instructions\n for controlling the other side's terminal printer. 3b1\n\n IAC DO RCTE 3c\n\n The sender REQUEST or AGREES to have the other side\n (sender of WILL RCTE) issue commands which will control\n his (sender of the DO) output to the terminal printer. 3c1\n\n IAC DON'T RCTE 3d\n\n The sender of this command REFU","scope_keywords":["726","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 731","folder":"IETF/RFC-731","source":"IETF/RFC-731/RFC-731.txt","version":null},{"body":"IETF","designation":"RFC 732","folder":"IETF/RFC-732","source":"IETF/RFC-732/RFC-732.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 726 NWG/RFC# 726 JBP DHC 8-MAR-77 08:29 39237\n Remote Controlled Transmission & Echoing Telnet Option\n\n Network Working Group Jon Postel & Dave Crocker\n Request for Comments: 726 SRI-ARC UC Irvine\n NIC: 39237 8 March 1977\n\n \n \n Remote Controlled Transmssion and Echoing Telnet Option\n\n 1\n\n 1. Command name and code: 2\n\n RCTE 7 2a\n\n 2. Command meanings: 3\n\n IAC WILL RCTE 3a\n\n The sender of this command REQUESTS or AGREES to use\n the RCTE option, and will send instructions for\n controlling the other side's terminal printer. 3a1\n\n IAC WON'T RCTE 3b\n\n The sender of this option REFUSES to send instructions\n for controlling the other side's terminal printer. 3b1\n\n IAC DO RCTE 3c\n\n The sender REQUEST or AGREES to have the other side\n (sender of WILL RCTE) issue commands which will control\n his (sender of the DO) output to the terminal printer. 3c1\n\n IAC DON'T RCTE 3d\n\n The sender of this command REFU 726 presentation nested-reference unchanged"},{"id":"IETF RFC 358","type":"specification","body":"IETF","designation":"RFC 358","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc358.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc358.txt","https://www.rfc-editor.org/rfc/rfc358.pdf"],"folder":"IETF/RFC-358","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 357","folder":"IETF/RFC-357","source":"IETF/RFC-357/RFC-357.txt","version":null}],"search_text":"IETF RFC 358 nested-reference unavailable"},{"id":"IETF RFC 5431","type":"specification","body":"IETF","designation":"RFC 5431","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5431.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5431.txt","https://www.rfc-editor.org/rfc/rfc5431.pdf"],"folder":"IETF/RFC-5431","files":{"txt":{"path":"standards/IETF/RFC-5431/RFC-5431.txt","sha256":"73a69cbe8116c7acd9b4bd391d526bd418b5857def5ab5990476fff3662233e4"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the need for a new pair of IANA Diameter\n Command Codes to be used in a vendor-specific new application, namely\n for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/\n response for authorizing network Quality of Service (QoS) resources\n and policy enforcement in a network element, as one of the\n recommendations of the International Telecommunication Union -\n Telecommunication Standardization Sector (ITU-T).","scope_keywords":["5431","attribute","authorization","http","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5431 This document describes the need for a new pair of IANA Diameter\n Command Codes to be used in a vendor-specific new application, namely\n for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/\n response for authorizing network Quality of Service (QoS) resources\n and policy enforcement in a network element, as one of the\n recommendations of the International Telecommunication Union -\n Telecommunication Standardization Sector (ITU-T). 5431 attribute authorization http license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5516","type":"specification","body":"IETF","designation":"RFC 5516","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5516.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5516.txt","https://www.rfc-editor.org/rfc/rfc5516.pdf"],"folder":"IETF/RFC-5516","files":{"txt":{"path":"standards/IETF/RFC-5516/RFC-5516.txt","sha256":"bac6949b715937a86fec1bfd77dffb7e4fb4cad67cc99d48b57335a5973447ce"}},"tags":["nested-reference","unchanged"],"summary":"This document registers a set of IANA Diameter Command Codes to be\n used in new vendor-specific Diameter applications defined for the\n Third Generation Partnership Project (3GPP) Evolved Packet System\n (EPS). These new Diameter applications are defined for Mobile\n Management Entity (MME)- and Serving GPRS (General Packet Radio\n Service) Support Node (SGSN)-related interfaces in in the\n architecture for the Evolved 3GPP Packet Switched Domain, which is\n also known as the Evolved Packet System (EPS).\n\nJones & Morand Informational [Page 1]\n\f\nRFC 5516 3GPP EPS Command Codes April 2009","scope_keywords":["5516","authentication","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"IETF RFC 5516 This document registers a set of IANA Diameter Command Codes to be\n used in new vendor-specific Diameter applications defined for the\n Third Generation Partnership Project (3GPP) Evolved Packet System\n (EPS). These new Diameter applications are defined for Mobile\n Management Entity (MME)- and Serving GPRS (General Packet Radio\n Service) Support Node (SGSN)-related interfaces in in the\n architecture for the Evolved 3GPP Packet Switched Domain, which is\n also known as the Evolved Packet System (EPS).\n\nJones & Morand Informational [Page 1]\n\f\nRFC 5516 3GPP EPS Command Codes April 2009 5516 authentication http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 360","type":"specification","body":"IETF","designation":"RFC 360","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc360.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc360.txt","https://www.rfc-editor.org/rfc/rfc360.pdf"],"folder":"IETF/RFC-360","files":{"pdf":{"path":"standards/IETF/RFC-360/RFC-360.pdf","sha256":"a9db7f462eff8d2280b4fdb4454bc2a4276731f5d7e4b503d6aeb19cb8ae9124"},"txt":{"path":"standards/IETF/RFC-360/RFC-360.txt","sha256":"865ce3278c9a3e188356cd87d110252bb16502f436ea6d3b77b1743325e5780c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Holland\nRequest for Comments: 360 UCSD-CC\nCategory: Protocols, RJE June 1972\nNIC: 10602\n\n PROPOSED REMOTE JOB ENTRY PROTOCOL\n\n Remote job entry is the mechanism whereby a user at one location\n causes a batch-processing job to be run at some other location. This\n protocol specifies the Network standard procedures for such a user to\n communicate over the Network with a remote batch-processing server,\n causing that server to retrieve a job-input file, process the job,\n and deliver the job's output file(s) to a remote location. The\n protocol uses TELNET (to a special standardized logger, not socket 1)\n connection for all control communication between the user and the\n server RJE process. The server-site then uses the File Transfer\n Protocol to retrieve the job-input file and to deliver the output\n file(s).\n\n There are two types of users: direct users (persons) and us","scope_keywords":["360","crl","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 407","folder":"IETF/RFC-407","source":"IETF/RFC-407/RFC-407.txt","version":null}],"search_text":"IETF RFC 360 Network Working Group C. Holland\nRequest for Comments: 360 UCSD-CC\nCategory: Protocols, RJE June 1972\nNIC: 10602\n\n PROPOSED REMOTE JOB ENTRY PROTOCOL\n\n Remote job entry is the mechanism whereby a user at one location\n causes a batch-processing job to be run at some other location. This\n protocol specifies the Network standard procedures for such a user to\n communicate over the Network with a remote batch-processing server,\n causing that server to retrieve a job-input file, process the job,\n and deliver the job's output file(s) to a remote location. The\n protocol uses TELNET (to a special standardized logger, not socket 1)\n connection for all control communication between the user and the\n server RJE process. The server-site then uses the File Transfer\n Protocol to retrieve the job-input file and to deliver the output\n file(s).\n\n There are two types of users: direct users (persons) and us 360 crl path nested-reference unchanged"},{"id":"IETF RFC 407","type":"specification","body":"IETF","designation":"RFC 407","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc407.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc407.txt","https://www.rfc-editor.org/rfc/rfc407.pdf"],"folder":"IETF/RFC-407","files":{"txt":{"path":"standards/IETF/RFC-407/RFC-407.txt","sha256":"9aa2f6021cbdbe6d054b9aa21c359bf358438da50e03badf9f495bd55eeafac0"}},"tags":["nested-reference","unchanged"],"summary":"(Oct. 16, 1972)\n RFC 407 NIC 12112\n\nRobert Bressler, MIT-DMCG Obsoletes RFC 360\nRichard Guida, MIT-DMCG\nAlex McKenzie, BBN-NET\n\n REMOTE JOB ENTRY PROTOCOL\f\n\n REMOTE Job Entry Protocol\n (Oct. 16, 1972)\n RFC 407 NIC 12112\n\n REMOTE JOB ENTRY PROTOCOL\n\nINTRODUCTION\n\n Remote job entry is the mechanism whereby a user at one location\n causes a batch-processing job to be run at some other location. This\n protocol specifies the Network standard procedures for such a user to\n communicate over the Network with a remote batch-processing server,\n causing that server to retrieve a job-input file, process the job,\n and deliver the job's output file(s) to a remote location. The\n protocol uses a TELNET connection (to a special standardized logger,\n not socket 1) for all control communication between the user and the\n server RJE processes. The server-site then uses the File Transfer\n Protocol to retrieve ","scope_keywords":["407"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 407 (Oct. 16, 1972)\n RFC 407 NIC 12112\n\nRobert Bressler, MIT-DMCG Obsoletes RFC 360\nRichard Guida, MIT-DMCG\nAlex McKenzie, BBN-NET\n\n REMOTE JOB ENTRY PROTOCOL\f\n\n REMOTE Job Entry Protocol\n (Oct. 16, 1972)\n RFC 407 NIC 12112\n\n REMOTE JOB ENTRY PROTOCOL\n\nINTRODUCTION\n\n Remote job entry is the mechanism whereby a user at one location\n causes a batch-processing job to be run at some other location. This\n protocol specifies the Network standard procedures for such a user to\n communicate over the Network with a remote batch-processing server,\n causing that server to retrieve a job-input file, process the job,\n and deliver the job's output file(s) to a remote location. The\n protocol uses a TELNET connection (to a special standardized logger,\n not socket 1) for all control communication between the user and the\n server RJE processes. The server-site then uses the File Transfer\n Protocol to retrieve  407 nested-reference unchanged"},{"id":"IETF RFC 362","type":"specification","body":"IETF","designation":"RFC 362","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc362.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc362.txt","https://www.rfc-editor.org/rfc/rfc362.pdf"],"folder":"IETF/RFC-362","files":{"txt":{"path":"standards/IETF/RFC-362/RFC-362.txt","sha256":"e826a90f491063bd93138529132d13c14725d07e3ad5cf99bafc0294a936397b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC #10604 BBN\nRFC #362 28 June 1972\nCategories: F, G.3\nUpdates: RFC #353\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from June 5\nto June 16. During this period the MIT Math Lab PDP-10 (Network\naddress 198) became a server.\n\n No testing was done on June 6 due to an attempt to install the\nnew IMP system. No testing was done on June 9 as the prototype\nTerminal IMP was being used for software debugging.\n\n On June 16 the ARPA Terminal IMP (Network 156) was installed in\nArlington, Virginia.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. The only Host in this category is the PDP-10 at Case\n(Network a","scope_keywords":["362"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 362 Network Working Group Ellen Westheimer\nNIC #10604 BBN\nRFC #362 28 June 1972\nCategories: F, G.3\nUpdates: RFC #353\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from June 5\nto June 16. During this period the MIT Math Lab PDP-10 (Network\naddress 198) became a server.\n\n No testing was done on June 6 due to an attempt to install the\nnew IMP system. No testing was done on June 9 as the prototype\nTerminal IMP was being used for software debugging.\n\n On June 16 the ARPA Terminal IMP (Network 156) was installed in\nArlington, Virginia.\n\n Several Hosts are currently excluded from the daily testing.\nThese Hosts fall into two categories:\n\n1) Hosts which are not expected to be functioning on the Network as\nservers (available for use from other sites) on a regular basis for at\nleast two weeks. The only Host in this category is the PDP-10 at Case\n(Network a 362 nested-reference unchanged"},{"id":"IETF RFC 3620","type":"specification","body":"IETF","designation":"RFC 3620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3620.txt","https://www.rfc-editor.org/rfc/rfc3620.pdf"],"folder":"IETF/RFC-3620","files":{"txt":{"path":"standards/IETF/RFC-3620/RFC-3620.txt","sha256":"0fab1c1f022f0ad7529cde0e97a54300be786d07b6c4e8bd6c93dbb1ba2643b3"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes a Blocks Extensible Exchange Protocol (BEEP)\n profile that allows a BEEP peer to serve as an application-layer\n proxy. It allows authorized users to access services through a\n firewall.","scope_keywords":["3620","authorization","certificate","certificates","key","profile","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 3620 This memo describes a Blocks Extensible Exchange Protocol (BEEP)\n profile that allows a BEEP peer to serve as an application-layer\n proxy. It allows authorized users to access services through a\n firewall. 3620 authorization certificate certificates key profile tls nested-reference unchanged"},{"id":"IETF RFC 7994","type":"specification","body":"IETF","designation":"RFC 7994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7994.txt","https://www.rfc-editor.org/rfc/rfc7994.pdf"],"folder":"IETF/RFC-7994","files":{"txt":{"path":"standards/IETF/RFC-7994/RFC-7994.txt","sha256":"ba9ca9170f58c01e0d14966ad1cda6ae37a5097c79624cf41b4f554f5236c534"}},"tags":["nested-reference","unchanged"],"summary":"In 2013, after a great deal of community discussion, the decision was\n made to shift from the plain-text, ASCII-only canonical format for\n RFCs to XML as the canonical format with more human-readable formats\n rendered from that XML. The high-level requirements that informed\n this change were defined in RFC 6949, \"RFC Series Format Requirements\n and Future Development\". Plain text remains an important format for\n many in the IETF community, and it will be one of the publication\n formats rendered from the XML. This document outlines the rendering\n requirements for the plain-text RFC publication format. These\n requirements do not apply to plain-text RFCs published before the\n format transition.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IA","scope_keywords":["7994","attribute","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null}],"search_text":"IETF RFC 7994 In 2013, after a great deal of community discussion, the decision was\n made to shift from the plain-text, ASCII-only canonical format for\n RFCs to XML as the canonical format with more human-readable formats\n rendered from that XML. The high-level requirements that informed\n this change were defined in RFC 6949, \"RFC Series Format Requirements\n and Future Development\". Plain text remains an important format for\n many in the IETF community, and it will be one of the publication\n formats rendered from the XML. This document outlines the rendering\n requirements for the plain-text RFC publication format. These\n requirements do not apply to plain-text RFCs published before the\n format transition.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IA 7994 attribute http license subject trust nested-reference unchanged"},{"id":"legal:2024-2980","type":"legal_regulation","act_id":"2024-2980","title":"Trust framework and electronic notification system","celex":"32024R2980","eli":"https://data.europa.eu/eli/reg_impl/2024/2980/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/e331b1f3-b1e0-11ef-acb1-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2024-2980/2024-2980.html","sha256":"f9d82eb35f4b5b8f7bdf209936306593b965925e8aef2dccad62bdcfc20e1345","size":83812},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/e331b1f3-b1e0-11ef-acb1-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2024-2980/2024-2980.pdf","sha256":"b3ca8d38825e87a7377ce420fd8949a08dc70efd6c8035ac6b634f0dee555141","size":567496}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards notifications to the Commission concerning the European Digital Identity Wallet ecosystem The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, while ensuring the protection of personal data and… the electronic registers used by a Member State to publish information on wallet-relying parties registered in that Member State in accordance with Article 5b(5) of Regulation (EU) No 910/2014 (‘registers of wallet-relying parties’), the location of the registers of…","scope_keywords":["article","commission","council","data","digital","ecosystem","electronic","european","framework","identification","identity","information","member","notifications","parliament","parties","registered","registers","regulation","states","union","wallet","wallet-relying","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.071300+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2024-2980 Trust framework and electronic notification system 32024R2980 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards notifications to the Commission concerning the European Digital Identity Wallet ecosystem The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, while ensuring the protection of personal data and… the electronic registers used by a Member State to publish information on wallet-relying parties registered in that Member State in accordance with Article 5b(5) of Regulation (EU) No 910/2014 (‘registers of wallet-relying parties’), the location of the registers of… article commission council data digital ecosystem electronic european framework identification identity information member notifications parliament parties registered registers regulation states union wallet wallet-relying wallets"},{"id":"IETF RFC 365","type":"specification","body":"IETF","designation":"RFC 365","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc365.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc365.txt","https://www.rfc-editor.org/rfc/rfc365.pdf"],"folder":"IETF/RFC-365","files":{"txt":{"path":"standards/IETF/RFC-365/RFC-365.txt","sha256":"c308be883f920b42c467dc65037cbc7098f8c7b622d75a5ca4327eb2a024ec32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David Walden\nRequest for Comments #365 Bolt Beranek and Newman Inc.\nNIC # 10607 July 11, 1972\nCategories:\nUpdates:\nObsoletes:\n\n A LETTER TO ALL TIP USERS\n\nDear TIP Users,\n\n You will shortly be sent a revised version of the \"TIP User's\nGuide.\" Besides now having a loose leaf format, mainly descriptions\nof new commands have been added. Appendix B will be an alphabetical\nlist of all TIP commands. The new commands are:\n\n @BINARY INPUT START\n @BINARY INPUT END\n @BINARY OUTPUT START\n @BINARY OUTPUT END\n @CLEAR DEVICE WILD\n @CLEAR INSERT LINEFEED\n @INSERT LINEFEED\n @SEND COMMAND\n @RECEIVE FROM WILD\n @SEND TO WILD\n @SET DEVICE WILD\n @MAG ABORT\n @MAG BACKSPACE FILE\n @MAG BACKSPACE RECORD\n @MAG READ FILE\n @MAG READ RECORD\n @MAG SETUP COPY\n @MAG SPACE FILE\n @MAG SPACE RECORD\n @MAG UNLOAD\n @MAG WRITE EOF\n @MAG WRITE TAPE\n\nThe MAG commands are, of course, not relevant to users o","scope_keywords":["365"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 365 Network Working Group David Walden\nRequest for Comments #365 Bolt Beranek and Newman Inc.\nNIC # 10607 July 11, 1972\nCategories:\nUpdates:\nObsoletes:\n\n A LETTER TO ALL TIP USERS\n\nDear TIP Users,\n\n You will shortly be sent a revised version of the \"TIP User's\nGuide.\" Besides now having a loose leaf format, mainly descriptions\nof new commands have been added. Appendix B will be an alphabetical\nlist of all TIP commands. The new commands are:\n\n @BINARY INPUT START\n @BINARY INPUT END\n @BINARY OUTPUT START\n @BINARY OUTPUT END\n @CLEAR DEVICE WILD\n @CLEAR INSERT LINEFEED\n @INSERT LINEFEED\n @SEND COMMAND\n @RECEIVE FROM WILD\n @SEND TO WILD\n @SET DEVICE WILD\n @MAG ABORT\n @MAG BACKSPACE FILE\n @MAG BACKSPACE RECORD\n @MAG READ FILE\n @MAG READ RECORD\n @MAG SETUP COPY\n @MAG SPACE FILE\n @MAG SPACE RECORD\n @MAG UNLOAD\n @MAG WRITE EOF\n @MAG WRITE TAPE\n\nThe MAG commands are, of course, not relevant to users o 365 nested-reference unchanged"},{"id":"IETF RFC 366","type":"specification","body":"IETF","designation":"RFC 366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc366.txt","https://www.rfc-editor.org/rfc/rfc366.pdf"],"folder":"IETF/RFC-366","files":{"txt":{"path":"standards/IETF/RFC-366/RFC-366.txt","sha256":"4e5d3896f507c9a12cfd83094b79a199ece8f81abeb3fed57a6638b78b0a1cda"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC # 11013 BBN\nRFC # 366 11 July 1972\nCategories: F. G.3\nUpdates: RFC #362\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from June 19\nto June 30.\n\n No testing was done on June 20 due to an attempt to install the\nnew IMP system.\n\n Several Hosts are currently excluded from the daily testing as\nthey are presently intended to be users only. Included here are the\nTerminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\nNBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\nincludes the Network Control Center computer (Network address 5) which\nis used solely for gathering statistics from the Network. Finally,\nincluded among these Hosts are the following:\n Network\n Address Site Computer\n ------- ---- --------\n\n 7 Rand IBM - 360/65\n 73 Harvard PDP-1\n 138 Lincoln TSP\n 12 Illinois PDP-","scope_keywords":["366","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 366 Network Working Group Ellen Westheimer\nNIC # 11013 BBN\nRFC # 366 11 July 1972\nCategories: F. G.3\nUpdates: RFC #362\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from June 19\nto June 30.\n\n No testing was done on June 20 due to an attempt to install the\nnew IMP system.\n\n Several Hosts are currently excluded from the daily testing as\nthey are presently intended to be users only. Included here are the\nTerminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\nNBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\nincludes the Network Control Center computer (Network address 5) which\nis used solely for gathering statistics from the Network. Finally,\nincluded among these Hosts are the following:\n Network\n Address Site Computer\n ------- ---- --------\n\n 7 Rand IBM - 360/65\n 73 Harvard PDP-1\n 138 Lincoln TSP\n 12 Illinois PDP- 366 tsp nested-reference unchanged"},{"id":"IETF RFC 4615","type":"specification","body":"IETF","designation":"RFC 4615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4615.txt","https://www.rfc-editor.org/rfc/rfc4615.pdf"],"folder":"IETF/RFC-4615","files":{"txt":{"path":"standards/IETF/RFC-4615/RFC-4615.txt","sha256":"32b6965e8e5e78c444f140ac6993e330cc8951cf5097fea41c40bd2bd1b7c57c"}},"tags":["nested-reference","unchanged"],"summary":"Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function (PRF) based on the Advanced Encryption\n Standard (AES). This memo describes such an algorithm, called\n AES-CMAC-PRF-128. It supports fixed and variable key sizes.","scope_keywords":["4615","algorithm","authentication","encryption","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5926","folder":"IETF/RFC-5926","source":"IETF/RFC-5926/RFC-5926.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6071","folder":"IETF/RFC-6071","source":"IETF/RFC-6071/RFC-6071.txt","version":null},{"body":"IETF","designation":"RFC 6518","folder":"IETF/RFC-6518","source":"IETF/RFC-6518/RFC-6518.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null}],"search_text":"IETF RFC 4615 Some implementations of IP Security (IPsec) may want to use a\n pseudo-random function (PRF) based on the Advanced Encryption\n Standard (AES). This memo describes such an algorithm, called\n AES-CMAC-PRF-128. It supports fixed and variable key sizes. 4615 algorithm authentication encryption key keys nested-reference unchanged"},{"id":"IETF RFC 367","type":"specification","body":"IETF","designation":"RFC 367","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc367.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc367.txt","https://www.rfc-editor.org/rfc/rfc367.pdf"],"folder":"IETF/RFC-367","files":{"txt":{"path":"standards/IETF/RFC-367/RFC-367.txt","sha256":"9c3e9a404b643f953e1da5d778f0090cab76cf3e25dbe125881ce2a7a7528acb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nRequest for Comments: 367 BBN\nNIC #11014 19 July 1972\nCategory: F, G.3\nUpdates: 366\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from July 3 to\n July 14.\n\n No testing was done on July 4 as BBN took a holiday to celebrate\n Independence Day. No testing was done on July 11 and 12 as I was on\n vacation.\n\n Several Hosts are currently excluded from the daily testing as they\n are presently intended to be users only. Included here are the\n Terminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\n NBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\n includes the Network Control Center computer (Network address 5)\n which is used solely for gathering statistics from the Network.\n Finally, included among these Hosts are the following:\n\n Network\n Address Site Computer\n ------- ---- ---","scope_keywords":["367","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 367 Network Working Group Ellen Westheimer\nRequest for Comments: 367 BBN\nNIC #11014 19 July 1972\nCategory: F, G.3\nUpdates: 366\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from July 3 to\n July 14.\n\n No testing was done on July 4 as BBN took a holiday to celebrate\n Independence Day. No testing was done on July 11 and 12 as I was on\n vacation.\n\n Several Hosts are currently excluded from the daily testing as they\n are presently intended to be users only. Included here are the\n Terminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\n NBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\n includes the Network Control Center computer (Network address 5)\n which is used solely for gathering statistics from the Network.\n Finally, included among these Hosts are the following:\n\n Network\n Address Site Computer\n ------- ---- --- 367 tsp nested-reference unchanged"},{"id":"IETF RFC 4333","type":"specification","body":"IETF","designation":"RFC 4333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4333.txt","https://www.rfc-editor.org/rfc/rfc4333.pdf"],"folder":"IETF/RFC-4333","files":{"txt":{"path":"standards/IETF/RFC-4333/RFC-4333.txt","sha256":"fef4ea5798097fbf2dbd0c007f751f799e41b6d9e04b3f7fa59a6169e9401b36"}},"tags":["nested-reference","unchanged"],"summary":"This memo outlines the guidelines for selection of members of the\n IETF Administrative Oversight Committee, and describes the selection\n process used by the IAB and the IESG.\n\n1. Introduction\n\n The IETF Administrative Support Activity (IASA) provides the\n administrative structure required to support the IETF standards\n process and to support the IETF's technical activities. Within this\n activity is the office of the IETF Administrative Director (IAD) and\n the IETF Administrative Oversight Committee (IAOC). In addition to\n the ex-officio roles of the IETF Chair and IAB Chair on this\n committee, the IAB and IESG are each responsible for the appointment\n of one voting member of this committee.\n\n This memo outlines the process by which the IAB and IESG make their\n selections. This process will also be used in the event of mid-term\n vacancies that may arise with these positions.\n\n The documen","scope_keywords":["4333","policies","qualified","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5620","folder":"IETF/RFC-5620","source":"IETF/RFC-5620/RFC-5620.txt","version":null}],"search_text":"IETF RFC 4333 This memo outlines the guidelines for selection of members of the\n IETF Administrative Oversight Committee, and describes the selection\n process used by the IAB and the IESG.\n\n1. Introduction\n\n The IETF Administrative Support Activity (IASA) provides the\n administrative structure required to support the IETF standards\n process and to support the IETF's technical activities. Within this\n activity is the office of the IETF Administrative Director (IAD) and\n the IETF Administrative Oversight Committee (IAOC). In addition to\n the ex-officio roles of the IETF Chair and IAB Chair on this\n committee, the IAB and IESG are each responsible for the appointment\n of one voting member of this committee.\n\n This memo outlines the process by which the IAB and IESG make their\n selections. This process will also be used in the event of mid-term\n vacancies that may arise with these positions.\n\n The documen 4333 policies qualified trust nested-reference unchanged"},{"id":"IETF RFC 6685","type":"specification","body":"IETF","designation":"RFC 6685","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6685.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6685.txt","https://www.rfc-editor.org/rfc/rfc6685.pdf"],"folder":"IETF/RFC-6685","files":{"txt":{"path":"standards/IETF/RFC-6685/RFC-6685.txt","sha256":"ee5176398d12f18d0e8eadcae5557db50301f74c788410ba074ba90102b0f0cb"}},"tags":["nested-reference","unchanged"],"summary":"Internet Engineering Task Force (IETF) B. Trammell\nRequest for Comments: 6685 ETH Zurich\nUpdates: 5070 July 2012\nCategory: Standards Track\nISSN: 2070-1721\n\n Expert Review for Incident Object Description Exchange Format (IODEF)\n Extensions in IANA XML Registry\n\nAbstract\n\n This document specifies restrictions on additions to the subset of\n the IANA XML Namespace and Schema registries, to require Expert\n Review for extensions to Incident Object Description Exchange Format\n (IODEF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information ab","scope_keywords":["6685","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"IETF RFC 6685 Internet Engineering Task Force (IETF) B. Trammell\nRequest for Comments: 6685 ETH Zurich\nUpdates: 5070 July 2012\nCategory: Standards Track\nISSN: 2070-1721\n\n Expert Review for Incident Object Description Exchange Format (IODEF)\n Extensions in IANA XML Registry\n\nAbstract\n\n This document specifies restrictions on additions to the subset of\n the IANA XML Namespace and Schema registries, to require Expert\n Review for extensions to Incident Object Description Exchange Format\n (IODEF).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information ab 6685 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 369","type":"specification","body":"IETF","designation":"RFC 369","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc369.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc369.txt","https://www.rfc-editor.org/rfc/rfc369.pdf"],"folder":"IETF/RFC-369","files":{"txt":{"path":"standards/IETF/RFC-369/RFC-369.txt","sha256":"d0d46bb32d241d5602ea9c4c447b7a5b525837d902ffab6cb5c384fd10607a79"}},"tags":["nested-reference","unchanged"],"summary":"RFC #302, Exercising the ARPANET, described a group organized at UCSB\n to investigate the network resources. The stated goals were to\n develop problem solving capability and, in the process, produce\n helpful criticism for the nodes investigated. This report summarizes\n the group's experiences and finding and suggests network refinements\n to improve user satisfaction.\n\n The group's encounter with ARPANET included many unexpected problems\n and difficulties. Most worthy of mention are software heterogeneity\n and inadequate documentation.\n\n From this first hand experience the group has formulated criteria for\n ease in use of network resources. The report presents these criteria\n as well as suggestions for improved documentation, better utilization\n of current resources, and a plea for regular usage of inter-personal\n communications facilities. Individual sites have been graded on\n reliabilit","scope_keywords":["369","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 531","folder":"IETF/RFC-531","source":"IETF/RFC-531/RFC-531.txt","version":null}],"search_text":"IETF RFC 369 RFC #302, Exercising the ARPANET, described a group organized at UCSB\n to investigate the network resources. The stated goals were to\n develop problem solving capability and, in the process, produce\n helpful criticism for the nodes investigated. This report summarizes\n the group's experiences and finding and suggests network refinements\n to improve user satisfaction.\n\n The group's encounter with ARPANET included many unexpected problems\n and difficulties. Most worthy of mention are software heterogeneity\n and inadequate documentation.\n\n From this first hand experience the group has formulated criteria for\n ease in use of network resources. The report presents these criteria\n as well as suggestions for improved documentation, better utilization\n of current resources, and a plea for regular usage of inter-personal\n communications facilities. Individual sites have been graded on\n reliabilit 369 presentation nested-reference unchanged"},{"id":"IETF RFC 531","type":"specification","body":"IETF","designation":"RFC 531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc531.txt","https://www.rfc-editor.org/rfc/rfc531.pdf"],"folder":"IETF/RFC-531","files":{"txt":{"path":"standards/IETF/RFC-531/RFC-531.txt","sha256":"560231a2aa6a5be7c4a2a2131cd0fda7c852bd253be401bce0f73981bb7b1f4c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. A. Padlipsky\nRequest for Comments #531 MIT-Multics\nNIC 17450 June 26, 1973\n\n Feast or famine?\n A Response to Two Recent RFC's About Network Information\n\nIn RFC 514, Will Kantrowitz returns to the theme of his superb RFC 459.\nThere are too many people spending too much time asking for too much\ninformation about Network Hosts. In RFC 519, John Pickens returns to\nthe theme of his rather querulous RFC 369. It's not easy to learn how\nto use network Hosts. On the one hand, it would seem that there's a\nveritable feast of information going around; on the other hand it would\nseem that there's a terrible famine. Can this apparent contradiction be\nresolved?\n\nI think it can be, and will attempt to do so after making a few\nobservations about the respective poles. In regard to the issues\nKantrowitz raises, matters are perhaps even worse for the \"big\" Servers\nthan for the exper","scope_keywords":["531","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 531 Network Working Group M. A. Padlipsky\nRequest for Comments #531 MIT-Multics\nNIC 17450 June 26, 1973\n\n Feast or famine?\n A Response to Two Recent RFC's About Network Information\n\nIn RFC 514, Will Kantrowitz returns to the theme of his superb RFC 459.\nThere are too many people spending too much time asking for too much\ninformation about Network Hosts. In RFC 519, John Pickens returns to\nthe theme of his rather querulous RFC 369. It's not easy to learn how\nto use network Hosts. On the one hand, it would seem that there's a\nveritable feast of information going around; on the other hand it would\nseem that there's a terrible famine. Can this apparent contradiction be\nresolved?\n\nI think it can be, and will attempt to do so after making a few\nobservations about the respective poles. In regard to the issues\nKantrowitz raises, matters are perhaps even worse for the \"big\" Servers\nthan for the exper 531 key nested-reference unchanged"},{"id":"IETF RFC 5872","type":"specification","body":"IETF","designation":"RFC 5872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5872.txt","https://www.rfc-editor.org/rfc/rfc5872.pdf"],"folder":"IETF/RFC-5872","files":{"txt":{"path":"standards/IETF/RFC-5872/RFC-5872.txt","sha256":"3f4751bc00435d390b568b020b19917e3165a5965f186a2b5802b505c5c87b33"}},"tags":["nested-reference","unchanged"],"summary":"This document relaxes the IANA rules for the Protocol for Carrying\n Authentication for Network Access (PANA).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5872.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents","scope_keywords":["5872","attribute","authentication","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5873","folder":"IETF/RFC-5873","source":"IETF/RFC-5873/RFC-5873.txt","version":null}],"search_text":"IETF RFC 5872 This document relaxes the IANA rules for the Protocol for Carrying\n Authentication for Network Access (PANA).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5872.\n\nCopyright Notice\n\n Copyright (c) 2010 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents 5872 attribute authentication http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 7153","type":"specification","body":"IETF","designation":"RFC 7153","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7153.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7153.txt","https://www.rfc-editor.org/rfc/rfc7153.pdf"],"folder":"IETF/RFC-7153","files":{"txt":{"path":"standards/IETF/RFC-7153/RFC-7153.txt","sha256":"774ed869a7fdaf38a1a37623abe3c50c537ba5adc0d9b649ebbf3bf03d3604d6"}},"tags":["nested-reference","unchanged"],"summary":"This document reorganizes the IANA registries for the type values and\n sub-type values of the BGP Extended Communities attribute and the BGP\n IPv6-Address-Specific Extended Communities attribute. This is done\n in order to remove interdependencies among the registries, thus\n making it easier for IANA to determine which codepoints are available\n for assignment in which registries. This document also clarifies the\n information that must be provided to IANA when requesting an\n allocation from one or more of these registries. These changes are\n compatible with the existing allocations and thus do not affect\n protocol implementations. The changes will, however, impact the\n \"IANA Considerations\" sections of future protocol specifications.\n This document updates RFC 4360 and RFC 5701.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Interne","scope_keywords":["7153","attribute","http","license","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7432","folder":"IETF/RFC-7432","source":"IETF/RFC-7432/RFC-7432.txt","version":null}],"search_text":"IETF RFC 7153 This document reorganizes the IANA registries for the type values and\n sub-type values of the BGP Extended Communities attribute and the BGP\n IPv6-Address-Specific Extended Communities attribute. This is done\n in order to remove interdependencies among the registries, thus\n making it easier for IANA to determine which codepoints are available\n for assignment in which registries. This document also clarifies the\n information that must be provided to IANA when requesting an\n allocation from one or more of these registries. These changes are\n compatible with the existing allocations and thus do not affect\n protocol implementations. The changes will, however, impact the\n \"IANA Considerations\" sections of future protocol specifications.\n This document updates RFC 4360 and RFC 5701.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Interne 7153 attribute http license policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 3694","type":"specification","body":"IETF","designation":"RFC 3694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3694.txt","https://www.rfc-editor.org/rfc/rfc3694.pdf"],"folder":"IETF/RFC-3694","files":{"txt":{"path":"standards/IETF/RFC-3694/RFC-3694.txt","sha256":"3fa1bc300d95136d6886b0b9147294d1a8b61fc6ed1788753317ddfa8c63f90f"}},"tags":["nested-reference","unchanged"],"summary":"This document provides some analysis of threats against the Geopriv\n protocol architecture. It focuses on protocol threats, threats that\n result from the storage of data by entities in the architecture, and\n threats posed by the abuse of information yielded by Geopriv. Some\n security properties that meet these threats are enumerated as a\n reference for Geopriv requirements.\n\nDanley, et al. Informational [Page 1]\n\f\nRFC 3694 Threat Analysis of the Geopriv Protocol February 2004","scope_keywords":["3694","authentication","identification","policy","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4079","folder":"IETF/RFC-4079","source":"IETF/RFC-4079/RFC-4079.txt","version":null},{"body":"IETF","designation":"RFC 4119","folder":"IETF/RFC-4119","source":"IETF/RFC-4119/RFC-4119.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 6225","folder":"IETF/RFC-6225","source":"IETF/RFC-6225/RFC-6225.txt","version":null},{"body":"IETF","designation":"RFC 6280","folder":"IETF/RFC-6280","source":"IETF/RFC-6280/RFC-6280.txt","version":null},{"body":"IETF","designation":"RFC 6772","folder":"IETF/RFC-6772","source":"IETF/RFC-6772/RFC-6772.txt","version":null}],"search_text":"IETF RFC 3694 This document provides some analysis of threats against the Geopriv\n protocol architecture. It focuses on protocol threats, threats that\n result from the storage of data by entities in the architecture, and\n threats posed by the abuse of information yielded by Geopriv. Some\n security properties that meet these threats are enumerated as a\n reference for Geopriv requirements.\n\nDanley, et al. Informational [Page 1]\n\f\nRFC 3694 Threat Analysis of the Geopriv Protocol February 2004 3694 authentication identification policy risk nested-reference unchanged"},{"id":"IETF RFC 370","type":"specification","body":"IETF","designation":"RFC 370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc370.txt","https://www.rfc-editor.org/rfc/rfc370.pdf"],"folder":"IETF/RFC-370","files":{"txt":{"path":"standards/IETF/RFC-370/RFC-370.txt","sha256":"ae06be0b137579c9d6b126a383d9264f761f136deeb04520f66029aff7e699c8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ellen Westheimer\nNIC #11017 BBN\nRFC #370 31 July 1972\nCategories: F, G.3\nUpdates: RFC #367\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from July 17\nto July 28.\n\n On Tuesday, July 18, the new IMP software was released.\n\n Several Hosts are currently excluded from the daily testing as\nthey are presently intended to be users only. Included here are the\nTerminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\nNBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\nincludes the Network Control Center computer (Network address 5) which\nis used solely for gathering statistics from the Network. Finally,\nincluded among these Hosts are the following:\n\n Network\n Address Site Computer\n ------- ---- --------\n\n 7 Rand IBM-360/65\n 73 Harvard PDP-1\n 138 Lincoln TSP\n 12 Illinois PDP-11\n 19 NBS PDP-11\n 23 USC I","scope_keywords":["370","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 370 Network Working Group Ellen Westheimer\nNIC #11017 BBN\nRFC #370 31 July 1972\nCategories: F, G.3\nUpdates: RFC #367\nObsoletes: None\n\n NETWORK HOST STATUS\n\n This RFC reports on the status of most Network Hosts from July 17\nto July 28.\n\n On Tuesday, July 18, the new IMP software was released.\n\n Several Hosts are currently excluded from the daily testing as\nthey are presently intended to be users only. Included here are the\nTerminal IMPs, which are presently in the Network (AMES, MITRE, RADC,\nNBS, ETAC, USC, GWC, NOAA, SAAC, ARPA, and BBN*). This category also\nincludes the Network Control Center computer (Network address 5) which\nis used solely for gathering statistics from the Network. Finally,\nincluded among these Hosts are the following:\n\n Network\n Address Site Computer\n ------- ---- --------\n\n 7 Rand IBM-360/65\n 73 Harvard PDP-1\n 138 Lincoln TSP\n 12 Illinois PDP-11\n 19 NBS PDP-11\n 23 USC I 370 tsp nested-reference unchanged"},{"id":"IETF RFC 3717","type":"specification","body":"IETF","designation":"RFC 3717","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3717.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3717.txt","https://www.rfc-editor.org/rfc/rfc3717.pdf"],"folder":"IETF/RFC-3717","files":{"txt":{"path":"standards/IETF/RFC-3717/RFC-3717.txt","sha256":"1e2218b770bfa6cdefd11381b6bca6dfca30a0abe068858dd7f39746634852f6"}},"tags":["nested-reference","unchanged"],"summary":"The Internet transport infrastructure is moving towards a model of\n high-speed routers interconnected by optical core networks. The\n architectural choices for the interaction between IP and optical\n network layers, specifically, the routing and signaling aspects, are\n maturing. At the same time, a consensus has emerged in the industry\n on utilizing IP-based protocols for the optical control plane. This\n document defines a framework for IP over Optical networks,\n considering both the IP-based control plane for optical networks as\n well as IP-optical network interactions (together referred to as \"IP\n over optical networks\").\n\nRajagopalan, et al. Informational [Page 1]\n\f\nRFC 3717 IP over Optical Networks: A Framework March 2004","scope_keywords":["3717","attribute","path","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4054","folder":"IETF/RFC-4054","source":"IETF/RFC-4054/RFC-4054.txt","version":null}],"search_text":"IETF RFC 3717 The Internet transport infrastructure is moving towards a model of\n high-speed routers interconnected by optical core networks. The\n architectural choices for the interaction between IP and optical\n network layers, specifically, the routing and signaling aspects, are\n maturing. At the same time, a consensus has emerged in the industry\n on utilizing IP-based protocols for the optical control plane. This\n document defines a framework for IP over Optical networks,\n considering both the IP-based control plane for optical networks as\n well as IP-optical network interactions (together referred to as \"IP\n over optical networks\").\n\nRajagopalan, et al. Informational [Page 1]\n\f\nRFC 3717 IP over Optical Networks: A Framework March 2004 3717 attribute path pid nested-reference unchanged"},{"id":"IETF RFC 4054","type":"specification","body":"IETF","designation":"RFC 4054","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4054.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4054.txt","https://www.rfc-editor.org/rfc/rfc4054.pdf"],"folder":"IETF/RFC-4054","files":{"txt":{"path":"standards/IETF/RFC-4054/RFC-4054.txt","sha256":"37904f4f25c40b654bd705d156f61c101b75fd8b1984fa0960ffab7231c33edb"}},"tags":["nested-reference","unchanged"],"summary":"Optical networking poses a number challenges for Generalized Multi-\n Protocol Label Switching (GMPLS). Fundamentally, optical technology\n is an analog rather than digital technology whereby the optical layer\n is lowest in the transport hierarchy and hence has an intimate\n relationship with the physical geography of the network. This\n contribution surveys some of the aspects of optical networks that\n impact routing and identifies possible GMPLS responses for each: (1)\n Constraints arising from the design of new software controllable\n network elements, (2) Constraints in a single all-optical domain\n without wavelength conversion, (3) Complications arising in more\n complex networks incorporating both all-optical and opaque\n architectures, and (4) Impacts of diversity constraints.","scope_keywords":["4054","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4428","folder":"IETF/RFC-4428","source":"IETF/RFC-4428/RFC-4428.txt","version":null}],"search_text":"IETF RFC 4054 Optical networking poses a number challenges for Generalized Multi-\n Protocol Label Switching (GMPLS). Fundamentally, optical technology\n is an analog rather than digital technology whereby the optical layer\n is lowest in the transport hierarchy and hence has an intimate\n relationship with the physical geography of the network. This\n contribution surveys some of the aspects of optical networks that\n impact routing and identifies possible GMPLS responses for each: (1)\n Constraints arising from the design of new software controllable\n network elements, (2) Constraints in a single all-optical domain\n without wavelength conversion, (3) Complications arising in more\n complex networks incorporating both all-optical and opaque\n architectures, and (4) Impacts of diversity constraints. 4054 management path nested-reference unchanged"},{"id":"IETF RFC 3980","type":"specification","body":"IETF","designation":"RFC 3980","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3980.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3980.txt","https://www.rfc-editor.org/rfc/rfc3980.pdf"],"folder":"IETF/RFC-3980","files":{"txt":{"path":"standards/IETF/RFC-3980/RFC-3980.txt","sha256":"e3f76b0f09d006e0ef168908eeb9537098e55db1f44cfe31327c7725fc002202"}},"tags":["nested-reference","unchanged"],"summary":"Internet Small Computer Systems Interface (iSCSI) is a SCSI transport\n protocol that maps the SCSI family of protocols onto TCP/IP. This\n document defines an additional iSCSI node name type format to enable\n use of the \"Network Address Authority\" (NAA) worldwide naming format\n defined by the InterNational Committee for Information Technology\n Standards (INCITS) T11 - Fibre Channel (FC) protocols and used by\n Serial Attached SCSI (SAS). This document updates RFC 3720.","scope_keywords":["3980","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5664","folder":"IETF/RFC-5664","source":"IETF/RFC-5664/RFC-5664.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"IETF RFC 3980 Internet Small Computer Systems Interface (iSCSI) is a SCSI transport\n protocol that maps the SCSI family of protocols onto TCP/IP. This\n document defines an additional iSCSI node name type format to enable\n use of the \"Network Address Authority\" (NAA) worldwide naming format\n defined by the InterNational Committee for Information Technology\n Standards (INCITS) T11 - Fibre Channel (FC) protocols and used by\n Serial Attached SCSI (SAS). This document updates RFC 3720. 3980 presentation nested-reference unchanged"},{"id":"IETF RFC 373","type":"specification","body":"IETF","designation":"RFC 373","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc373.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc373.txt","https://www.rfc-editor.org/rfc/rfc373.pdf"],"folder":"IETF/RFC-373","files":{"txt":{"path":"standards/IETF/RFC-373/RFC-373.txt","sha256":"98078b27bf1280f915258a51d28dc57e7c05f310f5ddf778bdbbd44e07ff1d6c"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC #373 14 July 1972\nNIC 11058 SU-AI\n\n ARBITRARY CHARACTER SETS\n\n by John McCarthy\n\nIt would be nice to be able to have documents stored in computers that\ncould include arbitrary characters and to be able to display them on\nany CRT screen, edit them using any keyboard, and print them on any\nprinter. The object of this memorandum is to suggest how to get there\nfrom here with special reference to the ARPA network.\n\nWhere are we now?\n\n (1) At present, there is 96 character ASCII, and everyone agrees that\n it should be included in any larger set.\n\n (2) Many installations are dependent on 64 character sets which do not\n even include the lower case latin alphabet.\n\n (3) At the Stanford Artificial Intelligence Laboratory, we have a 114\n character set that includes 96 character ASCII and which is\n implemented in our keyboards, displays, and line printer\n\n (4) Printers are becoming available","scope_keywords":["373","key","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"IETF RFC 373 NWG/RFC #373 14 July 1972\nNIC 11058 SU-AI\n\n ARBITRARY CHARACTER SETS\n\n by John McCarthy\n\nIt would be nice to be able to have documents stored in computers that\ncould include arbitrary characters and to be able to display them on\nany CRT screen, edit them using any keyboard, and print them on any\nprinter. The object of this memorandum is to suggest how to get there\nfrom here with special reference to the ARPA network.\n\nWhere are we now?\n\n (1) At present, there is 96 character ASCII, and everyone agrees that\n it should be included in any larger set.\n\n (2) Many installations are dependent on 64 character sets which do not\n even include the lower case latin alphabet.\n\n (3) At the Stanford Artificial Intelligence Laboratory, we have a 114\n character set that includes 96 character ASCII and which is\n implemented in our keyboards, displays, and line printer\n\n (4) Printers are becoming available 373 key policy registered nested-reference unchanged"},{"id":"IETF RFC 4886","type":"specification","body":"IETF","designation":"RFC 4886","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4886.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4886.txt","https://www.rfc-editor.org/rfc/rfc4886.pdf"],"folder":"IETF/RFC-4886","files":{"txt":{"path":"standards/IETF/RFC-4886/RFC-4886.txt","sha256":"f364ab3eb8d375090af18987b7aedd36df076c819fbeeb67008639f42d17c624"}},"tags":["nested-reference","unchanged"],"summary":"Network mobility arises when a router connecting a network to the\n Internet dynamically changes its point of attachment to the Internet\n thereby causing the reachability of the said network to be changed in\n relation to the fixed Internet topology. Such a type of network is\n referred to as a mobile network. With appropriate mechanisms,\n sessions established between nodes in the mobile network and the\n global Internet can be maintained after the mobile router changes its\n point of attachment. This document outlines the goals expected from\n network mobility support and defines the requirements that must be\n met by the NEMO Basic Support solution.\n\nErnst Informational [Page 1]\n\f\nRFC 4886 NEMO Goals July 2007","scope_keywords":["4886","driving","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4885","folder":"IETF/RFC-4885","source":"IETF/RFC-4885/RFC-4885.txt","version":null},{"body":"IETF","designation":"RFC 4888","folder":"IETF/RFC-4888","source":"IETF/RFC-4888/RFC-4888.txt","version":null},{"body":"IETF","designation":"RFC 4889","folder":"IETF/RFC-4889","source":"IETF/RFC-4889/RFC-4889.txt","version":null},{"body":"IETF","designation":"RFC 4980","folder":"IETF/RFC-4980","source":"IETF/RFC-4980/RFC-4980.txt","version":null}],"search_text":"IETF RFC 4886 Network mobility arises when a router connecting a network to the\n Internet dynamically changes its point of attachment to the Internet\n thereby causing the reachability of the said network to be changed in\n relation to the fixed Internet topology. Such a type of network is\n referred to as a mobile network. With appropriate mechanisms,\n sessions established between nodes in the mobile network and the\n global Internet can be maintained after the mobile router changes its\n point of attachment. This document outlines the goals expected from\n network mobility support and defines the requirements that must be\n met by the NEMO Basic Support solution.\n\nErnst Informational [Page 1]\n\f\nRFC 4886 NEMO Goals July 2007 4886 driving path trust nested-reference unchanged"},{"id":"IETF RFC 5909","type":"specification","body":"IETF","designation":"RFC 5909","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5909.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5909.txt","https://www.rfc-editor.org/rfc/rfc5909.pdf"],"folder":"IETF/RFC-5909","files":{"txt":{"path":"standards/IETF/RFC-5909/RFC-5909.txt","sha256":"2588c96c0fe45422cd9bcc7ea36009bba5c808a59b14400bb424d6f145e84173"}},"tags":["nested-reference","unchanged"],"summary":"Neighbor Discovery Proxies are used to provide an address presence on\n a link for nodes that are no longer present on the link. They allow\n a node to receive packets directed at its address by allowing another\n device to perform Neighbor Discovery operations on its behalf.\n\n Neighbor Discovery Proxy is used in Mobile IPv6 and related protocols\n to provide reachability from nodes on the home network when a Mobile\n Node is not at home, by allowing the Home Agent to act as proxy. It\n is also used as a mechanism to allow a global prefix to span multiple\n links, where proxies act as relays for Neighbor Discovery messages.\n\n Neighbor Discovery Proxy currently cannot be secured using Secure\n Neighbor Discovery (SEND). Today, SEND assumes that a node\n advertising an address is the address owner and in possession of\n appropriate public and private keys for that node. This document\n describes how ","scope_keywords":["5909","authorization","certificate","http","key","keys","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6496","folder":"IETF/RFC-6496","source":"IETF/RFC-6496/RFC-6496.txt","version":null},{"body":"IETF","designation":"RFC 6957","folder":"IETF/RFC-6957","source":"IETF/RFC-6957/RFC-6957.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null}],"search_text":"IETF RFC 5909 Neighbor Discovery Proxies are used to provide an address presence on\n a link for nodes that are no longer present on the link. They allow\n a node to receive packets directed at its address by allowing another\n device to perform Neighbor Discovery operations on its behalf.\n\n Neighbor Discovery Proxy is used in Mobile IPv6 and related protocols\n to provide reachability from nodes on the home network when a Mobile\n Node is not at home, by allowing the Home Agent to act as proxy. It\n is also used as a mechanism to allow a global prefix to span multiple\n links, where proxies act as relays for Neighbor Discovery messages.\n\n Neighbor Discovery Proxy currently cannot be secured using Secure\n Neighbor Discovery (SEND). Today, SEND assumes that a node\n advertising an address is the address owner and in possession of\n appropriate public and private keys for that node. This document\n describes how  5909 authorization certificate http key keys license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 3762","type":"specification","body":"IETF","designation":"RFC 3762","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3762.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3762.txt","https://www.rfc-editor.org/rfc/rfc3762.pdf"],"folder":"IETF/RFC-3762","files":{"txt":{"path":"standards/IETF/RFC-3762/RFC-3762.txt","sha256":"7620bf43589224d000d1b0ecb3815e287b8a6f2e6292dbc1d2ad0a59581eee41"}},"tags":["nested-reference","unchanged"],"summary":"The H.323 specification defines a means for building multimedia\n communication services over an arbitrary Packet Based Network,\n including the Internet. This document registers a Telephone Number\n Mapping (ENUM) service for H.323 according to specifications and\n guidelines in RFC 3761.","scope_keywords":["3762","authentication","encryption","http","key","license","policies","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 3762 The H.323 specification defines a means for building multimedia\n communication services over an arbitrary Packet Based Network,\n including the Internet. This document registers a Telephone Number\n Mapping (ENUM) service for H.323 according to specifications and\n guidelines in RFC 3761. 3762 authentication encryption http key license policies subject nested-reference unchanged"},{"id":"IETF RFC 6483","type":"specification","body":"IETF","designation":"RFC 6483","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6483.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6483.txt","https://www.rfc-editor.org/rfc/rfc6483.pdf"],"folder":"IETF/RFC-6483","files":{"txt":{"path":"standards/IETF/RFC-6483/RFC-6483.txt","sha256":"7e74a70caa5ad1e14f0e7ae45c61b9b7881ce6aae07e3df0120211a1ff57df9c"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the semantics of a Route Origin Authorization\n (ROA) in terms of the context of an application of the Resource\n Public Key Infrastructure to validate the origination of routes\n advertised in the Border Gateway Protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf","scope_keywords":["6483","attestation","attribute","attributes","authorization","certificate","certificates","holder","http","issuer","key","license","path","pki","profile","signature"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6480","folder":"IETF/RFC-6480","source":"IETF/RFC-6480/RFC-6480.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null}],"search_text":"IETF RFC 6483 This document defines the semantics of a Route Origin Authorization\n (ROA) in terms of the context of an application of the Resource\n Public Key Infrastructure to validate the origination of routes\n advertised in the Border Gateway Protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf 6483 attestation attribute attributes authorization certificate certificates holder http issuer key license path pki profile signature nested-reference unchanged"},{"id":"IETF RFC 7132","type":"specification","body":"IETF","designation":"RFC 7132","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7132.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7132.txt","https://www.rfc-editor.org/rfc/rfc7132.pdf"],"folder":"IETF/RFC-7132","files":{"txt":{"path":"standards/IETF/RFC-7132/RFC-7132.txt","sha256":"8db908f2b4bf5b152645f2a00cdf2932478be0ed6d19380e83442de069574d4a"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a threat model for the context in which\n External Border Gateway Protocol (EBGP) path security mechanisms will\n be developed. The threat model includes an analysis of the Resource\n Public Key Infrastructure (RPKI) and focuses on the ability of an\n Autonomous System (AS) to verify the authenticity of the AS path info\n received in a BGP update. We use the term \"PATHSEC\" to refer to any\n BGP path security technology that makes use of the RPKI. PATHSEC\n will secure BGP, consistent with the inter-AS security focus of the\n RPKI.\n\n The document characterizes classes of potential adversaries that are\n considered to be threats and examines classes of attacks that might\n be launched against PATHSEC. It does not revisit attacks against\n unprotected BGP, as that topic has already been addressed in the\n BGP-4 standard. It concludes with a brief discussion of residual\n vulnerab","scope_keywords":["7132","attribute","authentication","http","key","license","management","path","pki","risk","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null}],"search_text":"IETF RFC 7132 This document describes a threat model for the context in which\n External Border Gateway Protocol (EBGP) path security mechanisms will\n be developed. The threat model includes an analysis of the Resource\n Public Key Infrastructure (RPKI) and focuses on the ability of an\n Autonomous System (AS) to verify the authenticity of the AS path info\n received in a BGP update. We use the term \"PATHSEC\" to refer to any\n BGP path security technology that makes use of the RPKI. PATHSEC\n will secure BGP, consistent with the inter-AS security focus of the\n RPKI.\n\n The document characterizes classes of potential adversaries that are\n considered to be threats and examines classes of attacks that might\n be launched against PATHSEC. It does not revisit attacks against\n unprotected BGP, as that topic has already been addressed in the\n BGP-4 standard. It concludes with a brief discussion of residual\n vulnerab 7132 attribute authentication http key license management path pki risk subject trust validation nested-reference unchanged"},{"id":"IETF RFC 378","type":"specification","body":"IETF","designation":"RFC 378","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc378.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc378.txt","https://www.rfc-editor.org/rfc/rfc378.pdf"],"folder":"IETF/RFC-378","files":{"txt":{"path":"standards/IETF/RFC-378/RFC-378.txt","sha256":"50a96e66cbfa114eaf029610a1b969d28fe5b5bd9f403cfd5be3ffbabf50be56"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 378 BBN\nNIC #11120 10 August 1972\n\n Traffic Statistics (July 1972)\n\n For several months BBN has been supplying ARPA with a monthly summary\n of \"Host packets output.\" In response to questions from several\n sites, ARPA has agreed to allow us to publish these statistics in RFC\n form also. Attached are the traffic statistics for the month of July\n 1972.\n\n Please note that the numbers given are either monthly totals or\n overall averages (i.e., based on 24 hours per day, seven days a\n week). Thus, these numbers are not useful in determining peak\n traffic conditions.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JULY 1972\n\n MISSING DATA FOR 17\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 100083 74730 174813\n UCLA HOST 2 1168305 78751 1247056\n UCLA HOST 3 33544 11950 45494\n -------- ------- --------\n 1301932 1654","scope_keywords":["378"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 378 Network Working Group A. McKenzie\nRequest for Comments: 378 BBN\nNIC #11120 10 August 1972\n\n Traffic Statistics (July 1972)\n\n For several months BBN has been supplying ARPA with a monthly summary\n of \"Host packets output.\" In response to questions from several\n sites, ARPA has agreed to allow us to publish these statistics in RFC\n form also. Attached are the traffic statistics for the month of July\n 1972.\n\n Please note that the numbers given are either monthly totals or\n overall averages (i.e., based on 24 hours per day, seven days a\n week). Thus, these numbers are not useful in determining peak\n traffic conditions.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JULY 1972\n\n MISSING DATA FOR 17\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 100083 74730 174813\n UCLA HOST 2 1168305 78751 1247056\n UCLA HOST 3 33544 11950 45494\n -------- ------- --------\n 1301932 1654 378 nested-reference unchanged"},{"id":"IETF RFC 3787","type":"specification","body":"IETF","designation":"RFC 3787","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3787.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3787.txt","https://www.rfc-editor.org/rfc/rfc3787.pdf"],"folder":"IETF/RFC-3787","files":{"txt":{"path":"standards/IETF/RFC-3787/RFC-3787.txt","sha256":"3cf99446c8e78ab0298fd5505c900fb4ccbe0428769267e8d10d5202a5cc37ed"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses a number of differences between the\n Intermediate System to Intermediate System (IS-IS) protocol used to\n route IP traffic as described in RFC 1195 and the protocol as it is\n deployed today. These differences are discussed as a service to\n those implementing, testing, and deploying the IS-IS Protocol to\n route IP traffic. A companion document describes the differences\n between the protocol described in ISO 10589 and current practice.","scope_keywords":["3787","algorithm","authentication","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null}],"search_text":"IETF RFC 3787 This document discusses a number of differences between the\n Intermediate System to Intermediate System (IS-IS) protocol used to\n route IP traffic as described in RFC 1195 and the protocol as it is\n deployed today. These differences are discussed as a service to\n those implementing, testing, and deploying the IS-IS Protocol to\n route IP traffic. A companion document describes the differences\n between the protocol described in ISO 10589 and current practice. 3787 algorithm authentication key path nested-reference unchanged"},{"id":"IETF RFC 3788","type":"specification","body":"IETF","designation":"RFC 3788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3788.txt","https://www.rfc-editor.org/rfc/rfc3788.pdf"],"folder":"IETF/RFC-3788","files":{"txt":{"path":"standards/IETF/RFC-3788/RFC-3788.txt","sha256":"9e2ddfc750fa5f5bf864b1ffac30ff9f353194ae57b413fd72d3a7628603e5be"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses how Transport Layer Security (TLS) and IPsec\n can be used to secure communication for SIGTRAN protocols. The main\n goal is to recommend the minimum security means that a SIGTRAN node\n must implement in order to attain secured communication. The support\n of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS\n support is optional.\n\nLoughney, et al. Standards Track [Page 1]\n\f\nRFC 3788 SIGTRAN Security June 2004","scope_keywords":["3788","authentication","encryption","key","pki","qualified","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null}],"search_text":"IETF RFC 3788 This document discusses how Transport Layer Security (TLS) and IPsec\n can be used to secure communication for SIGTRAN protocols. The main\n goal is to recommend the minimum security means that a SIGTRAN node\n must implement in order to attain secured communication. The support\n of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS\n support is optional.\n\nLoughney, et al. Standards Track [Page 1]\n\f\nRFC 3788 SIGTRAN Security June 2004 3788 authentication encryption key pki qualified tls nested-reference unchanged"},{"id":"IETF RFC 381","type":"specification","body":"IETF","designation":"RFC 381","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc381.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc381.txt","https://www.rfc-editor.org/rfc/rfc381.pdf"],"folder":"IETF/RFC-381","files":{"txt":{"path":"standards/IETF/RFC-381/RFC-381.txt","sha256":"8bd88c86a16bc9dcc2a777ab44ce555152ae804ec28e901aae8b1474605d9899"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. McQuillan\nRequest for Comments: 381 D. Walden\nNIC: 11151 Bolt Beranek and Newman Inc.\n 26 July 1972\n\n Three Aids To Improved Network Operation\n\n1. Scheduled Software Maintenance\n\n As the ARPA Network has grown larger, we have found it difficult to\n find times when necessary new software can be slipped into the\n network without disrupting anyone. For instance, there is always\n intrasite traffic between the machines at MIT, and there is almost\n always traffic between the AMES TIP and IMP--the sun never sets on\n the ARPA Network. To minimize unscheduled disruptions and to\n simultaneously let us do what we have to do, we propose to schedule 7\n A.M. - 8 A.M. eastern time every Tuesday as a time when the IMPs can\n be reloaded. We will probably not use this period every Tuesday, but\n we do reserve this period every Tuesday. The above period is in\n addition to the severa","scope_keywords":["381","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 381 Network Working Group J. McQuillan\nRequest for Comments: 381 D. Walden\nNIC: 11151 Bolt Beranek and Newman Inc.\n 26 July 1972\n\n Three Aids To Improved Network Operation\n\n1. Scheduled Software Maintenance\n\n As the ARPA Network has grown larger, we have found it difficult to\n find times when necessary new software can be slipped into the\n network without disrupting anyone. For instance, there is always\n intrasite traffic between the machines at MIT, and there is almost\n always traffic between the AMES TIP and IMP--the sun never sets on\n the ARPA Network. To minimize unscheduled disruptions and to\n simultaneously let us do what we have to do, we propose to schedule 7\n A.M. - 8 A.M. eastern time every Tuesday as a time when the IMPs can\n be reloaded. We will probably not use this period every Tuesday, but\n we do reserve this period every Tuesday. The above period is in\n addition to the severa 381 identification nested-reference unchanged"},{"id":"IETF RFC 686","type":"specification","body":"IETF","designation":"RFC 686","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc686.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc686.txt","https://www.rfc-editor.org/rfc/rfc686.pdf"],"folder":"IETF/RFC-686","files":{"txt":{"path":"standards/IETF/RFC-686/RFC-686.txt","sha256":"f46be5c668001e99b062b21d53d37d211459cff73338742a2a70614e303e326d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Brian Harvey\nRequest for Comments: 686 SU-AI\nNIC 32481 10 May 1975\nReferences: 354, 385, 630, 542, 640.\n\n Leaving Well Enough Alone\n\n I recently decided it was time for an overhaul of our FTP user and\n server programs. This was my first venture into the world of network\n protocols, and I soon discovered that there was a lot we were doing\n wrong -- and a few things that everyone seemed to be doing\n differently from each other. When I enquired about this, the\n response from some quarters was \"Oh, you're running version 1!\"\n\n Since, as far as I can tell, all but one network host are running\n version 1, and basically transferring files OK, it seems to me that\n the existence on paper of an unused protocol should not stand in the\n way of maintaining the current one unless there is a good reason to\n believe that the new one is either imminent or strongly superior or\n both.","scope_keywords":["686","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 686 Network Working Group Brian Harvey\nRequest for Comments: 686 SU-AI\nNIC 32481 10 May 1975\nReferences: 354, 385, 630, 542, 640.\n\n Leaving Well Enough Alone\n\n I recently decided it was time for an overhaul of our FTP user and\n server programs. This was my first venture into the world of network\n protocols, and I soon discovered that there was a lot we were doing\n wrong -- and a few things that everyone seemed to be doing\n differently from each other. When I enquired about this, the\n response from some quarters was \"Oh, you're running version 1!\"\n\n Since, as far as I can tell, all but one network host are running\n version 1, and basically transferring files OK, it seems to me that\n the existence on paper of an unused protocol should not stand in the\n way of maintaining the current one unless there is a good reason to\n believe that the new one is either imminent or strongly superior or\n both. 686 subject trust nested-reference unchanged"},{"id":"IETF RFC 3889","type":"specification","body":"IETF","designation":"RFC 3889","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc3889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3889.txt","https://www.rfc-editor.org/rfc/rfc3889.pdf"],"folder":"IETF/RFC-3889","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null}],"search_text":"IETF RFC 3889 nested-reference unavailable"},{"id":"IETF RFC 389","type":"specification","body":"IETF","designation":"RFC 389","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc389.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc389.txt","https://www.rfc-editor.org/rfc/rfc389.pdf"],"folder":"IETF/RFC-389","files":{"txt":{"path":"standards/IETF/RFC-389/RFC-389.txt","sha256":"455bc43e09a4c998fce4501591ada0ec490d2737ea84b730f8c8e12ee453a60a"}},"tags":["nested-reference","unchanged"],"summary":"NETWORK WORKING GROUP BARBARA NOBLE\nREQUEST FOR COMMENTS #389 UCLA/CCN\nNIC 11361 AUGUST 30, 1972\nCATEGORIES:\nOBSELETES:\nUPDATES: 10264\n\nTO: ARPA NETWORK USERS\n\nTOPIC: UCLA CAMPUS COMPUTING NETWORK LIAISON STAFF FOR ARPA NETWORK\n\n The ARPA Network contacts at CCN are:\n\n 1. Initial Contact - User Relations Fred Ebrahimi (213) 825-7548\n\n 2. ARPA Liaison - User Services Barbara Noble (213) 825-7438\n 825-7548\n\n 3. Network Technical Liaison Robert Braden (213) 825-7518\n\n 4. Operations Manager William Tippit (213) 825-7546\n\n 5. Operations (213) 825-7554\n\n 6. Consulting (213) 825-7452\n\nPlease make initial contact with CCN through these representatives:\n\n A. Administrative Matters and General Facility Orientation:\n\n Fred Ebrahimi, Head - User Relations (213) 825-7548\n\n Fred handles administrative matters, such as: charge number\n applications and funding, and will discuss your application\n and the","scope_keywords":["389"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 389 NETWORK WORKING GROUP BARBARA NOBLE\nREQUEST FOR COMMENTS #389 UCLA/CCN\nNIC 11361 AUGUST 30, 1972\nCATEGORIES:\nOBSELETES:\nUPDATES: 10264\n\nTO: ARPA NETWORK USERS\n\nTOPIC: UCLA CAMPUS COMPUTING NETWORK LIAISON STAFF FOR ARPA NETWORK\n\n The ARPA Network contacts at CCN are:\n\n 1. Initial Contact - User Relations Fred Ebrahimi (213) 825-7548\n\n 2. ARPA Liaison - User Services Barbara Noble (213) 825-7438\n 825-7548\n\n 3. Network Technical Liaison Robert Braden (213) 825-7518\n\n 4. Operations Manager William Tippit (213) 825-7546\n\n 5. Operations (213) 825-7554\n\n 6. Consulting (213) 825-7452\n\nPlease make initial contact with CCN through these representatives:\n\n A. Administrative Matters and General Facility Orientation:\n\n Fred Ebrahimi, Head - User Relations (213) 825-7548\n\n Fred handles administrative matters, such as: charge number\n applications and funding, and will discuss your application\n and the 389 nested-reference unchanged"},{"id":"IETF RFC 391","type":"specification","body":"IETF","designation":"RFC 391","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc391.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc391.txt","https://www.rfc-editor.org/rfc/rfc391.pdf"],"folder":"IETF/RFC-391","files":{"txt":{"path":"standards/IETF/RFC-391/RFC-391.txt","sha256":"581c313e34470efb97ee304d40238360f6a826178436f321817cdd93c3f3edff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 391 15 September 1972\nUpdates: 378 NIC: 11583\n\n TRAFFIC STATISTICS (August 1972)\n\nABSTRACT\n\n Attached are the network traffic statistics for the month of August\n 1972.\n\n AAM/jm\n\n Attach.\n\n INTER- INTRA- AVG. DAILY DAYS\n NODE NODE TOTAL INTERNODE\n\nUSLA HOST 1 163800 187696 351496\nUCLA HOST 2 1189956 308725 1498681\nUCLA HOST 3 483386 6107 489493\n ------- ------ -------\n 1837142 502528 2339670 59263 31\n\nSRI HOST 1 1708465 120157 1828622\nSRI HOST 2 32837 7006 39843\nSRI HOST 4 83904 0 83904\n ------- ------ -------\n 1825206 127163 1952369 58878 31\n\nUCSB HOST 1 368992 452967 821959 11903 31\n\nUTAH HOST 1 692757 107679 800436 22347 31\n\nBBN HOST 2 2909317 777743 3687060\nBBN HOST 3 590 0 590\nBBN HOST 4 168313 587 168900\n ------- ------ -------\n 3078220 778330 3856550 99297 31\n\nMcKenzie [Page 1]\n\f\nRFC 391 TRAFFIC STATISTICS September 1972\n\nMIT ","scope_keywords":["391"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 391 Network Working Group A. McKenzie\nRequest for Comments: 391 15 September 1972\nUpdates: 378 NIC: 11583\n\n TRAFFIC STATISTICS (August 1972)\n\nABSTRACT\n\n Attached are the network traffic statistics for the month of August\n 1972.\n\n AAM/jm\n\n Attach.\n\n INTER- INTRA- AVG. DAILY DAYS\n NODE NODE TOTAL INTERNODE\n\nUSLA HOST 1 163800 187696 351496\nUCLA HOST 2 1189956 308725 1498681\nUCLA HOST 3 483386 6107 489493\n ------- ------ -------\n 1837142 502528 2339670 59263 31\n\nSRI HOST 1 1708465 120157 1828622\nSRI HOST 2 32837 7006 39843\nSRI HOST 4 83904 0 83904\n ------- ------ -------\n 1825206 127163 1952369 58878 31\n\nUCSB HOST 1 368992 452967 821959 11903 31\n\nUTAH HOST 1 692757 107679 800436 22347 31\n\nBBN HOST 2 2909317 777743 3687060\nBBN HOST 3 590 0 590\nBBN HOST 4 168313 587 168900\n ------- ------ -------\n 3078220 778330 3856550 99297 31\n\nMcKenzie [Page 1]\n\f\nRFC 391 TRAFFIC STATISTICS September 1972\n\nMIT  391 nested-reference unchanged"},{"id":"IETF RFC 3912","type":"specification","body":"IETF","designation":"RFC 3912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3912.txt","https://www.rfc-editor.org/rfc/rfc3912.pdf"],"folder":"IETF/RFC-3912","files":{"txt":{"path":"standards/IETF/RFC-3912/RFC-3912.txt","sha256":"04df3d3ebbf6dc1667889af1a5d2430cbd40bc10c66626ffb4075eb88be2698f"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the specification of the WHOIS protocol,\n thereby obsoleting RFC 954. The update is intended to remove the\n material from RFC 954 that does not have to do with the on-the-wire\n protocol, and is no longer applicable in today's Internet. This\n document does not attempt to change or update the protocol per se, or\n document other uses of the protocol that have come into existence\n since the publication of RFC 954.\n\n1. Introduction\n\n WHOIS is a TCP-based transaction-oriented query/response protocol\n that is widely used to provide information services to Internet\n users. While originally used to provide \"white pages\" services and\n information about registered domain names, current deployments cover\n a much broader range of information services. The protocol delivers\n its content in a human-readable format. This document updates the\n specification of the WHOIS protocol, th","scope_keywords":["3912","attribute","attributes","http","license","registered","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7481","folder":"IETF/RFC-7481","source":"IETF/RFC-7481/RFC-7481.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7485","folder":"IETF/RFC-7485","source":"IETF/RFC-7485/RFC-7485.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 3912 This document updates the specification of the WHOIS protocol,\n thereby obsoleting RFC 954. The update is intended to remove the\n material from RFC 954 that does not have to do with the on-the-wire\n protocol, and is no longer applicable in today's Internet. This\n document does not attempt to change or update the protocol per se, or\n document other uses of the protocol that have come into existence\n since the publication of RFC 954.\n\n1. Introduction\n\n WHOIS is a TCP-based transaction-oriented query/response protocol\n that is widely used to provide information services to Internet\n users. While originally used to provide \"white pages\" services and\n information about registered domain names, current deployments cover\n a much broader range of information services. The protocol delivers\n its content in a human-readable format. This document updates the\n specification of the WHOIS protocol, th 3912 attribute attributes http license registered subject nested-reference unchanged"},{"id":"IETF RFC 6183","type":"specification","body":"IETF","designation":"RFC 6183","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6183.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6183.txt","https://www.rfc-editor.org/rfc/rfc6183.pdf"],"folder":"IETF/RFC-6183","files":{"txt":{"path":"standards/IETF/RFC-6183/RFC-6183.txt","sha256":"558285acbe5d51f99679512b49992517b73a857da945e5d18738f61f6c458d3d"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a framework for IP Flow Information Export\n (IPFIX) Mediation. This framework extends the IPFIX reference model\n specified in RFC 5470 by defining the IPFIX Mediator components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6183.\n\nCopyright Notice\n\n Copyright (c)","scope_keywords":["6183","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6235","folder":"IETF/RFC-6235","source":"IETF/RFC-6235/RFC-6235.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7014","folder":"IETF/RFC-7014","source":"IETF/RFC-7014/RFC-7014.txt","version":null},{"body":"IETF","designation":"RFC 7015","folder":"IETF/RFC-7015","source":"IETF/RFC-7015/RFC-7015.txt","version":null}],"search_text":"IETF RFC 6183 This document describes a framework for IP Flow Information Export\n (IPFIX) Mediation. This framework extends the IPFIX reference model\n specified in RFC 5470 by defining the IPFIX Mediator components.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6183.\n\nCopyright Notice\n\n Copyright (c) 6183 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 392","type":"specification","body":"IETF","designation":"RFC 392","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc392.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc392.txt","https://www.rfc-editor.org/rfc/rfc392.pdf"],"folder":"IETF/RFC-392","files":{"txt":{"path":"standards/IETF/RFC-392/RFC-392.txt","sha256":"0f22559dc5be2f7ab4b27ba43d54bce2a1e3c46df561715b1c357283a2d3cee2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Hicks\nRequest for Comments: 392 B. Wessler\nNIC: 11584 Utah\n 20 September 1972\n\n Measurement of Host Costs for Transmitting Network Data\n\nBackground for the UTAH Timing Experiments\n\n Since October 1971 we, at the University of Utah, have had very large\n compute bound jobs running daily. These jobs would run for many cpu\n hours to achieve partial results and used resources that may be\n better obtained elsewhere. We felt that since these processes were\n being treated as batch jobs, they should be run on a batch machine.\n\n To meet the needs of these \"batch\" users, in March of this year, we\n developed a program[1] to use the Remote Job Service System (RJS) at\n UCLA-CCN. RJS at UCLA is run on an IBM 360/91.\n\n Some examples of these jobs were (and still are!):\n\n (a) Algebraic simplification (using LISP and REDUCE)\n\n (b) Applications of partial differential equation solv","scope_keywords":["392"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 392 Network Working Group G. Hicks\nRequest for Comments: 392 B. Wessler\nNIC: 11584 Utah\n 20 September 1972\n\n Measurement of Host Costs for Transmitting Network Data\n\nBackground for the UTAH Timing Experiments\n\n Since October 1971 we, at the University of Utah, have had very large\n compute bound jobs running daily. These jobs would run for many cpu\n hours to achieve partial results and used resources that may be\n better obtained elsewhere. We felt that since these processes were\n being treated as batch jobs, they should be run on a batch machine.\n\n To meet the needs of these \"batch\" users, in March of this year, we\n developed a program[1] to use the Remote Job Service System (RJS) at\n UCLA-CCN. RJS at UCLA is run on an IBM 360/91.\n\n Some examples of these jobs were (and still are!):\n\n (a) Algebraic simplification (using LISP and REDUCE)\n\n (b) Applications of partial differential equation solv 392 nested-reference unchanged"},{"id":"IETF RFC 4981","type":"specification","body":"IETF","designation":"RFC 4981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4981.txt","https://www.rfc-editor.org/rfc/rfc4981.pdf"],"folder":"IETF/RFC-4981","files":{"txt":{"path":"standards/IETF/RFC-4981/RFC-4981.txt","sha256":"b9550d4748cdd1ac33625f52e23bae6b2efdfaf2526394aa2c4dc67d3accfffe"}},"tags":["nested-reference","unchanged"],"summary":"The pace of research on peer-to-peer (P2P) networking in the last\n five years warrants a critical survey. P2P has the makings of a\n disruptive technology -- it can aggregate enormous storage and\n processing resources while minimizing entry and scaling costs.\n\n Failures are common amongst massive numbers of distributed peers,\n though the impact of individual failures may be less than in\n conventional architectures. Thus, the key to realizing P2P's\n potential in applications other than casual file sharing is\n robustness.\n\n P2P search methods are first couched within an overall P2P taxonomy.\n P2P indexes for simple key lookup are assessed, including those based\n on Plaxton trees, rings, tori, butterflies, de Bruijn graphs, and\n skip graphs. Similarly, P2P indexes for keyword lookup, information\n retrieval and data management are explored. Finally, early efforts\n to optimize range, multi-att","scope_keywords":["4981","attribute","hash","hashing","key","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5694","folder":"IETF/RFC-5694","source":"IETF/RFC-5694/RFC-5694.txt","version":null}],"search_text":"IETF RFC 4981 The pace of research on peer-to-peer (P2P) networking in the last\n five years warrants a critical survey. P2P has the makings of a\n disruptive technology -- it can aggregate enormous storage and\n processing resources while minimizing entry and scaling costs.\n\n Failures are common amongst massive numbers of distributed peers,\n though the impact of individual failures may be less than in\n conventional architectures. Thus, the key to realizing P2P's\n potential in applications other than casual file sharing is\n robustness.\n\n P2P search methods are first couched within an overall P2P taxonomy.\n P2P indexes for simple key lookup are assessed, including those based\n on Plaxton trees, rings, tori, butterflies, de Bruijn graphs, and\n skip graphs. Similarly, P2P indexes for keyword lookup, information\n retrieval and data management are explored. Finally, early efforts\n to optimize range, multi-att 4981 attribute hash hashing key management nested-reference unchanged"},{"id":"IETF RFC 3935","type":"specification","body":"IETF","designation":"RFC 3935","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3935.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3935.txt","https://www.rfc-editor.org/rfc/rfc3935.pdf"],"folder":"IETF/RFC-3935","files":{"txt":{"path":"standards/IETF/RFC-3935/RFC-3935.txt","sha256":"6081334c9c40262fec0915d4af2150f318135b9d366827208039280856056cd1"}},"tags":["nested-reference","unchanged"],"summary":"This memo gives a mission statement for the IETF, tries to define the\n terms used in the statement sufficiently to make the mission\n statement understandable and useful, argues why the IETF needs a\n mission statement, and tries to capture some of the debate that led\n to this point.\n\n1. Mission Statement\n\n The goal of the IETF is to make the Internet work better.\n\n The mission of the IETF is to produce high quality, relevant\n technical and engineering documents that influence the way people\n design, use, and manage the Internet in such a way as to make the\n Internet work better. These documents include protocol standards,\n best current practices, and informational documents of various kinds.\n\n The IETF will pursue this mission in adherence to the following\n cardinal principles:\n\n Open process - any interested person can participate in the work,\n know what is being decided, and make his or","scope_keywords":["3935","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4775","folder":"IETF/RFC-4775","source":"IETF/RFC-4775/RFC-4775.txt","version":null},{"body":"IETF","designation":"RFC 5377","folder":"IETF/RFC-5377","source":"IETF/RFC-5377/RFC-5377.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 8890","folder":"IETF/RFC-8890","source":"IETF/RFC-8890/RFC-8890.txt","version":null}],"search_text":"IETF RFC 3935 This memo gives a mission statement for the IETF, tries to define the\n terms used in the statement sufficiently to make the mission\n statement understandable and useful, argues why the IETF needs a\n mission statement, and tries to capture some of the debate that led\n to this point.\n\n1. Mission Statement\n\n The goal of the IETF is to make the Internet work better.\n\n The mission of the IETF is to produce high quality, relevant\n technical and engineering documents that influence the way people\n design, use, and manage the Internet in such a way as to make the\n Internet work better. These documents include protocol standards,\n best current practices, and informational documents of various kinds.\n\n The IETF will pursue this mission in adherence to the following\n cardinal principles:\n\n Open process - any interested person can participate in the work,\n know what is being decided, and make his or 3935 subject trust nested-reference unchanged"},{"id":"IETF RFC 5377","type":"specification","body":"IETF","designation":"RFC 5377","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5377.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5377.txt","https://www.rfc-editor.org/rfc/rfc5377.pdf"],"folder":"IETF/RFC-5377","files":{"txt":{"path":"standards/IETF/RFC-5377/RFC-5377.txt","sha256":"8383d861e73c227da36d03ca8f6ba6d3b609798fec652e773f01f2e903846bd4"}},"tags":["nested-reference","unchanged"],"summary":"Contributors grant intellectual property rights to the IETF. The\n IETF Trust holds and manages those rights on behalf of the IETF. The\n Trustees of the IETF Trust are responsible for that management. This\n management includes granting the licenses to copy, implement, and\n otherwise use IETF Contributions, among them Internet-Drafts and\n RFCs. The Trustees of the IETF Trust accepts direction from the IETF\n regarding the rights to be granted. This document describes the\n desires of the IETF regarding outbound rights to be granted in IETF\n Contributions.\n\nHalpern Informational [Page 1]\n\f\nRFC 5377 Outbound Rights Advice November 2008","scope_keywords":["5377","http","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null}],"search_text":"IETF RFC 5377 Contributors grant intellectual property rights to the IETF. The\n IETF Trust holds and manages those rights on behalf of the IETF. The\n Trustees of the IETF Trust are responsible for that management. This\n management includes granting the licenses to copy, implement, and\n otherwise use IETF Contributions, among them Internet-Drafts and\n RFCs. The Trustees of the IETF Trust accepts direction from the IETF\n regarding the rights to be granted. This document describes the\n desires of the IETF regarding outbound rights to be granted in IETF\n Contributions.\n\nHalpern Informational [Page 1]\n\f\nRFC 5377 Outbound Rights Advice November 2008 5377 http license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 3953","type":"specification","body":"IETF","designation":"RFC 3953","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc3953.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc3953.txt","https://www.rfc-editor.org/rfc/rfc3953.pdf"],"folder":"IETF/RFC-3953","files":{"txt":{"path":"standards/IETF/RFC-3953/RFC-3953.txt","sha256":"6a50d138d5c4631ec54d100aa732d60939e9b4d3bab24c49821c3bf802a391b4"}},"tags":["nested-reference","unchanged"],"summary":"This document registers a Telephone Number Mapping (ENUM) service for\n presence. Specifically, this document focuses on provisioning pres\n URIs in ENUM.","scope_keywords":["3953","pid","policy","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 3953 This document registers a Telephone Number Mapping (ENUM) service for\n presence. Specifically, this document focuses on provisioning pres\n URIs in ENUM. 3953 pid policy registered nested-reference unchanged"},{"id":"IETF RFC 6105","type":"specification","body":"IETF","designation":"RFC 6105","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6105.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6105.txt","https://www.rfc-editor.org/rfc/rfc6105.pdf"],"folder":"IETF/RFC-6105","files":{"txt":{"path":"standards/IETF/RFC-6105/RFC-6105.txt","sha256":"1f640f5c5b63e33bc7e1318bbb1cdbf1e6497458e189a064b1526effbb41f779"}},"tags":["nested-reference","unchanged"],"summary":"Routed protocols are often susceptible to spoof attacks. The\n canonical solution for IPv6 is Secure Neighbor Discovery (SEND), a\n solution that is non-trivial to deploy. This document proposes a\n light-weight alternative and complement to SEND based on filtering in\n the layer-2 network fabric, using a variety of filtering criteria,\n including, for example, SEND status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the cur","scope_keywords":["6105","authorization","http","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6104","folder":"IETF/RFC-6104","source":"IETF/RFC-6104/RFC-6104.txt","version":null},{"body":"IETF","designation":"RFC 6343","folder":"IETF/RFC-6343","source":"IETF/RFC-6343/RFC-6343.txt","version":null},{"body":"IETF","designation":"RFC 6879","folder":"IETF/RFC-6879","source":"IETF/RFC-6879/RFC-6879.txt","version":null},{"body":"IETF","designation":"RFC 6980","folder":"IETF/RFC-6980","source":"IETF/RFC-6980/RFC-6980.txt","version":null},{"body":"IETF","designation":"RFC 7113","folder":"IETF/RFC-7113","source":"IETF/RFC-7113/RFC-7113.txt","version":null},{"body":"IETF","designation":"RFC 7217","folder":"IETF/RFC-7217","source":"IETF/RFC-7217/RFC-7217.txt","version":null},{"body":"IETF","designation":"RFC 7610","folder":"IETF/RFC-7610","source":"IETF/RFC-7610/RFC-7610.txt","version":null}],"search_text":"IETF RFC 6105 Routed protocols are often susceptible to spoof attacks. The\n canonical solution for IPv6 is Secure Neighbor Discovery (SEND), a\n solution that is non-trivial to deploy. This document proposes a\n light-weight alternative and complement to SEND based on filtering in\n the layer-2 network fabric, using a variety of filtering criteria,\n including, for example, SEND status.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the cur 6105 authorization http license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 4748","type":"specification","body":"IETF","designation":"RFC 4748","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4748.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4748.txt","https://www.rfc-editor.org/rfc/rfc4748.pdf"],"folder":"IETF/RFC-4748","files":{"txt":{"path":"standards/IETF/RFC-4748/RFC-4748.txt","sha256":"92f2a262b2905cfd3ba593e6e62fa3a1b929c28fc320bb01012c35c0e1856f14"}},"tags":["nested-reference","unchanged"],"summary":"This document updates RFC 3978 \"IETF Rights in Contributions\" to\n recognize that the IETF Trust is now the proper custodian of all\n IETF-related intellectual property rights.\n\n This document does not constrain how the IETF Trust exercises those\n rights.\n\n1. Introduction","scope_keywords":["4748","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4844","folder":"IETF/RFC-4844","source":"IETF/RFC-4844/RFC-4844.txt","version":null},{"body":"IETF","designation":"RFC 4846","folder":"IETF/RFC-4846","source":"IETF/RFC-4846/RFC-4846.txt","version":null},{"body":"IETF","designation":"RFC 5378","folder":"IETF/RFC-5378","source":"IETF/RFC-5378/RFC-5378.txt","version":null}],"search_text":"IETF RFC 4748 This document updates RFC 3978 \"IETF Rights in Contributions\" to\n recognize that the IETF Trust is now the proper custodian of all\n IETF-related intellectual property rights.\n\n This document does not constrain how the IETF Trust exercises those\n rights.\n\n1. Introduction 4748 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 4879","type":"specification","body":"IETF","designation":"RFC 4879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4879.txt","https://www.rfc-editor.org/rfc/rfc4879.pdf"],"folder":"IETF/RFC-4879","files":{"txt":{"path":"standards/IETF/RFC-4879/RFC-4879.txt","sha256":"e550787b0aad9e2a3af6696ed1dcd74a97c690d384e35d85135ec836b4898dd2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Narten\nRequest for Comments: 4879 IBM\nBCP: 79 April 2007\nUpdates: 3979\nCategory: Best Current Practice\n\n Clarification of the Third Party Disclosure Procedure in RFC 3979\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document clarifies and updates a single sentence in RFC 3979.\n Specifically, when third party Intellectual Property Rights (IPR)\n disclosures are made, the intention is that the IETF Executive\n Director notify the IPR holder that a third party disclosure has been\n filed, and to ask the IPR holder whether they have any disclosure\n that needs to be made, per applicable RFC 3979 rules.\n\nNarten Best Current Practice [Pag","scope_keywords":["4879","holder","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 5743","folder":"IETF/RFC-5743","source":"IETF/RFC-5743/RFC-5743.txt","version":null},{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 6090","folder":"IETF/RFC-6090","source":"IETF/RFC-6090/RFC-6090.txt","version":null},{"body":"IETF","designation":"RFC 6701","folder":"IETF/RFC-6701","source":"IETF/RFC-6701/RFC-6701.txt","version":null},{"body":"IETF","designation":"RFC 6702","folder":"IETF/RFC-6702","source":"IETF/RFC-6702/RFC-6702.txt","version":null},{"body":"IETF","designation":"RFC 7841","folder":"IETF/RFC-7841","source":"IETF/RFC-7841/RFC-7841.txt","version":null},{"body":"IETF","designation":"RFC 8179","folder":"IETF/RFC-8179","source":"IETF/RFC-8179/RFC-8179.txt","version":null}],"search_text":"IETF RFC 4879 Network Working Group T. Narten\nRequest for Comments: 4879 IBM\nBCP: 79 April 2007\nUpdates: 3979\nCategory: Best Current Practice\n\n Clarification of the Third Party Disclosure Procedure in RFC 3979\n\nStatus of This Memo\n\n This document specifies an Internet Best Current Practices for the\n Internet Community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (C) The IETF Trust (2007).\n\nAbstract\n\n This document clarifies and updates a single sentence in RFC 3979.\n Specifically, when third party Intellectual Property Rights (IPR)\n disclosures are made, the intention is that the IETF Executive\n Director notify the IPR holder that a third party disclosure has been\n filed, and to ask the IPR holder whether they have any disclosure\n that needs to be made, per applicable RFC 3979 rules.\n\nNarten Best Current Practice [Pag 4879 holder http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6694","type":"specification","body":"IETF","designation":"RFC 6694","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6694.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6694.txt","https://www.rfc-editor.org/rfc/rfc6694.pdf"],"folder":"IETF/RFC-6694","files":{"txt":{"path":"standards/IETF/RFC-6694/RFC-6694.txt","sha256":"cf203882dece4f9bb1b69555901eab0a4705403315aa42361ac165c51529fd88"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the \"about\" URI scheme, which is widely used\n by Web browsers and some other applications to designate access to\n their internal resources, such as settings, application information,\n hidden built-in functionality, and so on.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org","scope_keywords":["6694","http","license","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null}],"search_text":"IETF RFC 6694 This document describes the \"about\" URI scheme, which is widely used\n by Web browsers and some other applications to designate access to\n their internal resources, such as settings, application information,\n hidden built-in functionality, and so on.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org 6694 http license registered subject trust nested-reference unchanged"},{"id":"IETF RFC 6983","type":"specification","body":"IETF","designation":"RFC 6983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6983.txt","https://www.rfc-editor.org/rfc/rfc6983.pdf"],"folder":"IETF/RFC-6983","files":{"txt":{"path":"standards/IETF/RFC-6983/RFC-6983.txt","sha256":"06531bca5b3e54407ba19246844ae75bc2c2f7b8b0d2355726020fc6e9e18cdc"}},"tags":["nested-reference","unchanged"],"summary":"This document presents thoughts on the potential impact of supporting\n HTTP Adaptive Streaming (HAS) technologies in Content Distribution\n Network Interconnection (CDNI) scenarios. The intent is to present\n the authors' analysis of the CDNI-HAS problem space and discuss\n different options put forward by the authors (and by others during\n informal discussions) on how to deal with HAS in the context of CDNI.\n This document has been used as input information during the CDNI\n working group process for making a decision regarding support for\n HAS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or dep","scope_keywords":["6983","authorization","delivery","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null}],"search_text":"IETF RFC 6983 This document presents thoughts on the potential impact of supporting\n HTTP Adaptive Streaming (HAS) technologies in Content Distribution\n Network Interconnection (CDNI) scenarios. The intent is to present\n the authors' analysis of the CDNI-HAS problem space and discuss\n different options put forward by the authors (and by others during\n informal discussions) on how to deal with HAS in the context of CDNI.\n This document has been used as input information during the CDNI\n working group process for making a decision regarding support for\n HAS.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or dep 6983 authorization delivery http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 9782","type":"specification","body":"IETF","designation":"RFC 9782","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9782.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9782.txt","https://www.rfc-editor.org/rfc/rfc9782.pdf"],"folder":"IETF/RFC-9782","files":{"pdf":{"path":"standards/IETF/RFC-9782/RFC-9782.pdf","sha256":"79748de782c59f9c30324206624162f0a667a36a203ba9b7f3f1ec9de650dfe3"},"txt":{"path":"standards/IETF/RFC-9782/RFC-9782.txt","sha256":"28f8f263bb9fcabad47004365ffc99ae773fb809261e9a6b0a23d33fb182ada5"}},"tags":["nested-reference","unchanged"],"summary":"The payloads used in Remote ATtestation procedureS (RATS) may require\n an associated media type for their conveyance, for example, when the\n payloads are used in RESTful APIs.\n\n This memo defines media types to be used for Entity Attestation\n Tokens (EATs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9782.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified ","scope_keywords":["9782","attestation","http","https","license","profile","profiles","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9782 The payloads used in Remote ATtestation procedureS (RATS) may require\n an associated media type for their conveyance, for example, when the\n payloads are used in RESTful APIs.\n\n This memo defines media types to be used for Entity Attestation\n Tokens (EATs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc9782.\n\nCopyright Notice\n\n Copyright (c) 2025 IETF Trust and the persons identified  9782 attestation http https license profile profiles signature subject trust nested-reference unchanged"},{"id":"IETF RFC 399","type":"specification","body":"IETF","designation":"RFC 399","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc399.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc399.txt","https://www.rfc-editor.org/rfc/rfc399.pdf"],"folder":"IETF/RFC-399","files":{"txt":{"path":"standards/IETF/RFC-399/RFC-399.txt","sha256":"7be87bd65a232c7f1c6eea8f215a272b6fc1c0a970529ad869639a5df5090128"}},"tags":["nested-reference","unchanged"],"summary":"RFC #399 Mark Krilanovich\nNIC #11917 UCSB\nUpdates: 122 Sept. 26, 1972\n\n SMFS Login and Logout\n\n Two new commands have been added to UCSB's Simple Minded\nFile System (SMFS). They are described below.\n\n Login (LGI)\n The login command is the means whereby the user\nidentifies himself and specifies the account number to which his\nuse of SMFS is to be billed. The user should issue a LGI command\ndirectly after completing the ICP and before any command\nreferencing a file. The user name and account number specified\nremain in effect until another LGI command is issued, a LGO\ncommand is issued, or the connection is closed.\n\n At present, the use of SMFS is not billed, and therefore\nuse of the accounting commands is optional. It is requested,\nhowever, that users and user processes begin to use this command\nas soon as possible, since we would like to collect statistics on\nSMFS utilization before imple","scope_keywords":["399"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 399 RFC #399 Mark Krilanovich\nNIC #11917 UCSB\nUpdates: 122 Sept. 26, 1972\n\n SMFS Login and Logout\n\n Two new commands have been added to UCSB's Simple Minded\nFile System (SMFS). They are described below.\n\n Login (LGI)\n The login command is the means whereby the user\nidentifies himself and specifies the account number to which his\nuse of SMFS is to be billed. The user should issue a LGI command\ndirectly after completing the ICP and before any command\nreferencing a file. The user name and account number specified\nremain in effect until another LGI command is issued, a LGO\ncommand is issued, or the connection is closed.\n\n At present, the use of SMFS is not billed, and therefore\nuse of the accounting commands is optional. It is requested,\nhowever, that users and user processes begin to use this command\nas soon as possible, since we would like to collect statistics on\nSMFS utilization before imple 399 nested-reference unchanged"},{"id":"IETF RFC 400","type":"specification","body":"IETF","designation":"RFC 400","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc400.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc400.txt","https://www.rfc-editor.org/rfc/rfc400.pdf"],"folder":"IETF/RFC-400","files":{"txt":{"path":"standards/IETF/RFC-400/RFC-400.txt","sha256":"8de1be0f8db0ae0765f0d28632b98b51edd76db2f76e0f1fd9eead056fddc443"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 400 BBN\nUpdates: 391 18 October 1972\nNIC: 11922\n\n TRAFFIC STATISTICS (September 1972)\n\nAttached are the network traffic statistics for the month of September\n1972.\n\nAAM/jm\n\nAttach.\n\n HOST THROUGHPUT SUMMARY\n (PACKET OUTPUT)\n SEPTEMBER 1972\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 232650 32005 264655\nUCLA HOST 2 1264597 25042 1289639\nUCLA HOST 3 431011 10235 441246\n ------- ----- -------\n 1928258 67282 1995540 64275 30\n\nSRI HOST 1 1801046 24363 1825409\nSRI HOST 2 16168 1327 17495\n ------- ----- -------\n 1817214 25690 1842904 60574 30\n\nUCSB HOST 1 428498 922768 1351366 14283 30\n\nBBN HOST 2 3816667 1180948 4997615\nBBN HOST 3 12899 1589244 1602143\nBBN HOST 4 90831 2276 93107\n ------- ------- -------\n 3920397 2772468 6692865 130680 30\n\nMIT HOST 1 61014 37330 98344\nMIT HOST 2 588706 414366 1003072\nMIT HOST 3","scope_keywords":["400"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 413","folder":"IETF/RFC-413","source":"IETF/RFC-413/RFC-413.txt","version":null}],"search_text":"IETF RFC 400 Network Working Group A. McKenzie\nRequest for Comments: 400 BBN\nUpdates: 391 18 October 1972\nNIC: 11922\n\n TRAFFIC STATISTICS (September 1972)\n\nAttached are the network traffic statistics for the month of September\n1972.\n\nAAM/jm\n\nAttach.\n\n HOST THROUGHPUT SUMMARY\n (PACKET OUTPUT)\n SEPTEMBER 1972\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 232650 32005 264655\nUCLA HOST 2 1264597 25042 1289639\nUCLA HOST 3 431011 10235 441246\n ------- ----- -------\n 1928258 67282 1995540 64275 30\n\nSRI HOST 1 1801046 24363 1825409\nSRI HOST 2 16168 1327 17495\n ------- ----- -------\n 1817214 25690 1842904 60574 30\n\nUCSB HOST 1 428498 922768 1351366 14283 30\n\nBBN HOST 2 3816667 1180948 4997615\nBBN HOST 3 12899 1589244 1602143\nBBN HOST 4 90831 2276 93107\n ------- ------- -------\n 3920397 2772468 6692865 130680 30\n\nMIT HOST 1 61014 37330 98344\nMIT HOST 2 588706 414366 1003072\nMIT HOST 3 400 nested-reference unchanged"},{"id":"IETF RFC 413","type":"specification","body":"IETF","designation":"RFC 413","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc413.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc413.txt","https://www.rfc-editor.org/rfc/rfc413.pdf"],"folder":"IETF/RFC-413","files":{"txt":{"path":"standards/IETF/RFC-413/RFC-413.txt","sha256":"1e57297596032a9a06205c037a7d14e5c785947905413059a701e1d46894b93e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 413 BBN\nNIC: 12405 13 November 1972\nUpdates: RFC 400\n\n TRAFFIC STATISTICS (October 1972)\n\nABSTRACT\n\n Attached are three sets of network traffic statistics as follows:\n\n - the entire month of October 1972\n - the four days preceding the ICCC (Oct. 20-23)\n - the three days of the ICCC (Oct. 24-26)\n\n AAM/jm\n\n Attach\n\nMcKenzie [Page 1]\n\f\nRFC 413 TRAFFIC STATISTICS (October 1972) November 1972\n\n HOST THROUGHPUT SUMMARY (PACKETS OUTPUT)\n OCTOBER 1972\n MISSING DATA FOR 4\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 312153 26551 338704\nUCLA HOST 2 1031946 15378 1047324\nUCLA HOST 3 373434 23428 396862\n ------- ------ -------\n 1717533 65357 1782890 57251 30\n\nSRI HOST 1 2387082 31517 2418599\nSRI HOST 2 11381 2082 13463\n -------- ----- -------\n 2398463 33599 2432062 79949 30\n\nUCSB HOST 1 676097 520360 1196457 22537 30\n","scope_keywords":["413"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 413 Network Working Group A. McKenzie\nRequest for Comments: 413 BBN\nNIC: 12405 13 November 1972\nUpdates: RFC 400\n\n TRAFFIC STATISTICS (October 1972)\n\nABSTRACT\n\n Attached are three sets of network traffic statistics as follows:\n\n - the entire month of October 1972\n - the four days preceding the ICCC (Oct. 20-23)\n - the three days of the ICCC (Oct. 24-26)\n\n AAM/jm\n\n Attach\n\nMcKenzie [Page 1]\n\f\nRFC 413 TRAFFIC STATISTICS (October 1972) November 1972\n\n HOST THROUGHPUT SUMMARY (PACKETS OUTPUT)\n OCTOBER 1972\n MISSING DATA FOR 4\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 312153 26551 338704\nUCLA HOST 2 1031946 15378 1047324\nUCLA HOST 3 373434 23428 396862\n ------- ------ -------\n 1717533 65357 1782890 57251 30\n\nSRI HOST 1 2387082 31517 2418599\nSRI HOST 2 11381 2082 13463\n -------- ----- -------\n 2398463 33599 2432062 79949 30\n\nUCSB HOST 1 676097 520360 1196457 22537 30\n 413 nested-reference unchanged"},{"id":"IETF RFC 4002","type":"specification","body":"IETF","designation":"RFC 4002","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4002.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4002.txt","https://www.rfc-editor.org/rfc/rfc4002.pdf"],"folder":"IETF/RFC-4002","files":{"txt":{"path":"standards/IETF/RFC-4002/RFC-4002.txt","sha256":"73000d1d33636ad3c3ebbebe4e4536023de9b0a2af7419c3bb7fc8c6f835794f"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Enumservices 'web' and 'ft' by using the\n URI schemes 'http:', 'https:' and 'ftp:' as per the IANA registration\n process defined in the ENUM specification (RFC 3761).","scope_keywords":["4002","http","https","key","policies","registered","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4002 This document registers the Enumservices 'web' and 'ft' by using the\n URI schemes 'http:', 'https:' and 'ftp:' as per the IANA registration\n process defined in the ENUM specification (RFC 3761). 4002 http https key policies registered tls nested-reference unchanged"},{"id":"IETF RFC 5863","type":"specification","body":"IETF","designation":"RFC 5863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5863.txt","https://www.rfc-editor.org/rfc/rfc5863.pdf"],"folder":"IETF/RFC-5863","files":{"txt":{"path":"standards/IETF/RFC-5863/RFC-5863.txt","sha256":"ee9dc1bb16aced0d8a477fb9ad1315b6b8d74ffd7bf26c140277a656aca0b1cd"}},"tags":["nested-reference","unchanged"],"summary":"DomainKeys Identified Mail (DKIM) allows an organization to claim\n responsibility for transmitting a message, in a way that can be\n validated by a recipient. The organization can be the author's, the\n originating sending site, an intermediary, or one of their agents. A\n message can contain multiple signatures, from the same or different\n organizations involved with the message. DKIM defines a domain-level\n digital signature authentication framework for email, using public\n key cryptography and using the domain name service as its key server\n technology. This permits verification of a responsible organization,\n as well as the integrity of the message content. DKIM will also\n provide a mechanism that permits potential email signers to publish\n information about their email signing practices; this will permit\n email receivers to make additional assessments about messages.\n DKIM's authentica","scope_keywords":["5863","authentication","delivery","http","key","keys","license","management","policies","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6377","folder":"IETF/RFC-6377","source":"IETF/RFC-6377/RFC-6377.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null}],"search_text":"IETF RFC 5863 DomainKeys Identified Mail (DKIM) allows an organization to claim\n responsibility for transmitting a message, in a way that can be\n validated by a recipient. The organization can be the author's, the\n originating sending site, an intermediary, or one of their agents. A\n message can contain multiple signatures, from the same or different\n organizations involved with the message. DKIM defines a domain-level\n digital signature authentication framework for email, using public\n key cryptography and using the domain name service as its key server\n technology. This permits verification of a responsible organization,\n as well as the integrity of the message content. DKIM will also\n provide a mechanism that permits potential email signers to publish\n information about their email signing practices; this will permit\n email receivers to make additional assessments about messages.\n DKIM's authentica 5863 authentication delivery http key keys license management policies signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 404","type":"specification","body":"IETF","designation":"RFC 404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc404.txt","https://www.rfc-editor.org/rfc/rfc404.pdf"],"folder":"IETF/RFC-404","files":{"txt":{"path":"standards/IETF/RFC-404/RFC-404.txt","sha256":"79cc07a190c542de73bad9febba2304e50202da655b9e68e38e343e173e2ef0e"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC #404 AAM 5-OCT-72 13:51 12068\nHost Address Changes Involving RAND and ISI\n\n This week the RAND IMP was temporarily removed from the\n Network and a new IMP was installed at ISI. Some of the\n people and computers from RAND have moved to ISI, in\n particular the RAND TENEX is now the ISI TENEX. The address\n of the ISI IMP is 86 (decimal) and the TENEX at ISI is Host\n number one; thus the \"Network Address\" of the ISI TENEX is 86.\n Sometime early next week the RAND IMP will be re-installed.\n It will still be IMP number 7, and the IBM 360/65 at RAND will\n still be \"Network Address\" 7.\n\n [ This RFC was put into machine readable form for entry ]\n [ into the online RFC archives by BBN Corp. under the ]\n [ direction of Alex McKenzie. 1/97 ]\n\n [Page 1]","scope_keywords":["404"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 404 NWG/RFC #404 AAM 5-OCT-72 13:51 12068\nHost Address Changes Involving RAND and ISI\n\n This week the RAND IMP was temporarily removed from the\n Network and a new IMP was installed at ISI. Some of the\n people and computers from RAND have moved to ISI, in\n particular the RAND TENEX is now the ISI TENEX. The address\n of the ISI IMP is 86 (decimal) and the TENEX at ISI is Host\n number one; thus the \"Network Address\" of the ISI TENEX is 86.\n Sometime early next week the RAND IMP will be re-installed.\n It will still be IMP number 7, and the IBM 360/65 at RAND will\n still be \"Network Address\" 7.\n\n [ This RFC was put into machine readable form for entry ]\n [ into the online RFC archives by BBN Corp. under the ]\n [ direction of Alex McKenzie. 1/97 ]\n\n [Page 1] 404 nested-reference unchanged"},{"id":"IETF RFC 870","type":"specification","body":"IETF","designation":"RFC 870","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc870.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc870.txt","https://www.rfc-editor.org/rfc/rfc870.pdf"],"folder":"IETF/RFC-870","files":{"txt":{"path":"standards/IETF/RFC-870/RFC-870.txt","sha256":"f06d5abb0ce74ad742aec9833ae31ee61cd06f8718afc961d2df7687774be4f7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 870 J. Postel\n ISI\nObsoletes RFCs: 820, October 1983\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Joyce Reynolds. The assignment\nof numbers is also handled by Joyce. If you are developing a protocol\nor application that will require the use of a link, socket, port,\nprotocol, or network number please contact Joyce to receive a number\nassignment.\n\n Joyce Reynolds\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90292\n\n phone: (213) 822-1511\n\n ARPA mail: JKREYNOLDS@USC-ISIF\n\nMost of the","scope_keywords":["870","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null}],"search_text":"IETF RFC 870 Network Working Group J. Reynolds\nRequest for Comments: 870 J. Postel\n ISI\nObsoletes RFCs: 820, October 1983\n790, 776, 770, 762, 758, 755,\n750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n ASSIGNED NUMBERS\n\nThis Network Working Group Request for Comments documents the currently\nassigned values from several series of numbers used in network protocol\nimplementations. This RFC will be updated periodically, and in any case\ncurrent information can be obtained from Joyce Reynolds. The assignment\nof numbers is also handled by Joyce. If you are developing a protocol\nor application that will require the use of a link, socket, port,\nprotocol, or network number please contact Joyce to receive a number\nassignment.\n\n Joyce Reynolds\n USC - Information Sciences Institute\n 4676 Admiralty Way\n Marina del Rey, California 90292\n\n phone: (213) 822-1511\n\n ARPA mail: JKREYNOLDS@USC-ISIF\n\nMost of the 870 risk nested-reference unchanged"},{"id":"IETF RFC 880","type":"specification","body":"IETF","designation":"RFC 880","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc880.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc880.txt","https://www.rfc-editor.org/rfc/rfc880.pdf"],"folder":"IETF/RFC-880","files":{"txt":{"path":"standards/IETF/RFC-880/RFC-880.txt","sha256":"1a914783eadafd67969520a5e02ba4ba3f406aecbe33bff3a070a8410d5d9a71"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 880 J. Postel\n ISI\nObsoletes: RFC 840 October 1983\n\n OFFICIAL PROTOCOLS\n\nThis RFC identifies the documents specifying the official protocols used\nin the Internet. Annotations identify any revisions or changes planned.\n\nTo first order, the official protocols are those in the \"Internet\nProtocol Transition Workbook\" (IPTW) dated March 1982. There are\nseveral protocols in use that are not in the IPTW. A few of the\nprotocols in the IPTW have been revised. Notably, the mail protocols\nhave been revised and issued as a volume titled \"Internet Mail\nProtocols\" dated November 1982. Telnet and the most useful option\nprotocols were issued by the NIC in a booklet entitled \"Internet Telnet\nProtocol and Options\" (ITP), dated June 1983. Some protocols have not\nbeen revised for many years, these are found in the old \"ARPANET\nProtocol Handbook\" (APH) ","scope_keywords":["880","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null}],"search_text":"IETF RFC 880 Network Working Group J. Reynolds\nRequest for Comments: 880 J. Postel\n ISI\nObsoletes: RFC 840 October 1983\n\n OFFICIAL PROTOCOLS\n\nThis RFC identifies the documents specifying the official protocols used\nin the Internet. Annotations identify any revisions or changes planned.\n\nTo first order, the official protocols are those in the \"Internet\nProtocol Transition Workbook\" (IPTW) dated March 1982. There are\nseveral protocols in use that are not in the IPTW. A few of the\nprotocols in the IPTW have been revised. Notably, the mail protocols\nhave been revised and issued as a volume titled \"Internet Mail\nProtocols\" dated November 1982. Telnet and the most useful option\nprotocols were issued by the NIC in a booklet entitled \"Internet Telnet\nProtocol and Options\" (ITP), dated June 1983. Some protocols have not\nbeen revised for many years, these are found in the old \"ARPANET\nProtocol Handbook\" (APH)  880 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 901","type":"specification","body":"IETF","designation":"RFC 901","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc901.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc901.txt","https://www.rfc-editor.org/rfc/rfc901.pdf"],"folder":"IETF/RFC-901","files":{"txt":{"path":"standards/IETF/RFC-901/RFC-901.txt","sha256":"c64bf8b0268675ef0038bea377caf8d13bb2fd549f84c7763a9f2ebc46e94768"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 901 J. Postel\n ISI\nObsoletes: RFCs 880, 840 June 1984\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nStatus of this Memo\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community.\n\nIntroduction\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Annotations identify any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful option\n protocols were issued by the NIC in a booklet entitled \"Internet\n Telnet P","scope_keywords":["901","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null}],"search_text":"IETF RFC 901 Network Working Group J. Reynolds\nRequest for Comments: 901 J. Postel\n ISI\nObsoletes: RFCs 880, 840 June 1984\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nStatus of this Memo\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community.\n\nIntroduction\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Annotations identify any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful option\n protocols were issued by the NIC in a booklet entitled \"Internet\n Telnet P 901 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 924","type":"specification","body":"IETF","designation":"RFC 924","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc924.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc924.txt","https://www.rfc-editor.org/rfc/rfc924.pdf"],"folder":"IETF/RFC-924","files":{"txt":{"path":"standards/IETF/RFC-924/RFC-924.txt","sha256":"e801e45a5b60a7fb4a6228e218a6b90431de2adef366926b218f53f56a674d37"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 924 J. Postel\n ISI\nObsoletes: RFCs 901, 880, 840 October 1984\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been revised and","scope_keywords":["924","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null}],"search_text":"IETF RFC 924 Network Working Group J. Reynolds\nRequest for Comments: 924 J. Postel\n ISI\nObsoletes: RFCs 901, 880, 840 October 1984\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been revised and 924 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 944","type":"specification","body":"IETF","designation":"RFC 944","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc944.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc944.txt","https://www.rfc-editor.org/rfc/rfc944.pdf"],"folder":"IETF/RFC-944","files":{"txt":{"path":"standards/IETF/RFC-944/RFC-944.txt","sha256":"41942b065f85aedf20d5adf87ccd3a4e7d95dd2b17e83a8361df85b8b2ea4bba"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 944 J. Postel\n ISI\nObsoletes: RFCs 924, 901, 880, 840 April 1985\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been revised ","scope_keywords":["944","algorithm","algorithms","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1131","folder":"IETF/RFC-1131","source":"IETF/RFC-1131/RFC-1131.pdf","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null}],"search_text":"IETF RFC 944 Network Working Group J. Reynolds\nRequest for Comments: 944 J. Postel\n ISI\nObsoletes: RFCs 924, 901, 880, 840 April 1985\n\n OFFICIAL ARPA-INTERNET PROTOCOLS\n\nSTATUS OF THIS MEMO\n\n This memo is an official status report on the protocols used in the\n ARPA-Internet community. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n This RFC identifies the documents specifying the official protocols\n used in the Internet. Comments indicate any revisions or changes\n planned.\n\n To first order, the official protocols are those in the \"Internet\n Protocol Transition Workbook\" (IPTW) dated March 1982. There are\n several protocols in use that are not in the IPTW. A few of the\n protocols in the IPTW have been revised. Notably, the mail protocols\n have been revised and issued as a volume titled \"Internet Mail\n Protocols\" dated November 1982. Telnet and the most useful Telnet\n options have been revised  944 algorithm algorithms subject nested-reference unchanged"},{"id":"IETF RFC 9334","type":"specification","body":"IETF","designation":"RFC 9334","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9334.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9334.txt","https://www.rfc-editor.org/rfc/rfc9334.pdf"],"folder":"IETF/RFC-9334","files":{"pdf":{"path":"standards/IETF/RFC-9334/RFC-9334.pdf","sha256":"e8f5658dbcbef7b01bb10553adcf4d0359ae2873886abb8e4606dd93ab82e71f"},"txt":{"path":"standards/IETF/RFC-9334/RFC-9334.txt","sha256":"b80d035fb64a00a637d4888d2855772412246230913231301727ef78d4b00540"}},"tags":["nested-reference","unchanged"],"summary":"In network protocol exchanges, it is often useful for one end of a\n communication to know whether the other end is in an intended\n operating state. This document provides an architectural overview of\n the entities involved that make such tests possible through the\n process of generating, conveying, and evaluating evidentiary Claims.\n It provides a model that is neutral toward processor architectures,\n the content of Claims, and protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Inte","scope_keywords":["9334","attestation","authentication","http","https","key","license","policies","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null},{"body":"IETF","designation":"RFC 9782","folder":"IETF/RFC-9782","source":"IETF/RFC-9782/RFC-9782.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"IETF RFC 9334 In network protocol exchanges, it is often useful for one end of a\n communication to know whether the other end is in an intended\n operating state. This document provides an architectural overview of\n the entities involved that make such tests possible through the\n process of generating, conveying, and evaluating evidentiary Claims.\n It provides a model that is neutral toward processor architectures,\n the content of Claims, and protocols.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Inte 9334 attestation authentication http https key license policies subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 4597","type":"specification","body":"IETF","designation":"RFC 4597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4597.txt","https://www.rfc-editor.org/rfc/rfc4597.pdf"],"folder":"IETF/RFC-4597","files":{"txt":{"path":"standards/IETF/RFC-4597/RFC-4597.txt","sha256":"cf5746cfec63481a4a480496f9ca9ffdf350a7f5cafef9e704c7cd71d0206f68"}},"tags":["nested-reference","unchanged"],"summary":"This document describes multimedia conferencing scenarios. It\n describes both basic and advanced conferencing scenarios involving\n voice, video, text, and interactive text sessions. These scenarios\n will help with the definition and evaluation of the protocols being\n developed in the centralized conferencing XCON working group.\n\nEven & Ismail Informational [Page 1]\n\f\nRFC 4597 Conference Scenarios July 2006","scope_keywords":["4597","policy","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null},{"body":"IETF","designation":"RFC 5239","folder":"IETF/RFC-5239","source":"IETF/RFC-5239/RFC-5239.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null}],"search_text":"IETF RFC 4597 This document describes multimedia conferencing scenarios. It\n describes both basic and advanced conferencing scenarios involving\n voice, video, text, and interactive text sessions. These scenarios\n will help with the definition and evaluation of the protocols being\n developed in the centralized conferencing XCON working group.\n\nEven & Ismail Informational [Page 1]\n\f\nRFC 4597 Conference Scenarios July 2006 4597 policy presentation nested-reference unchanged"},{"id":"IETF RFC 8240","type":"specification","body":"IETF","designation":"RFC 8240","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8240.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8240.txt","https://www.rfc-editor.org/rfc/rfc8240.pdf"],"folder":"IETF/RFC-8240","files":{"txt":{"path":"standards/IETF/RFC-8240/RFC-8240.txt","sha256":"b56c4858da3f5ead233f6925f0d95356d2426fc193157edc2064c22ed86e67ff"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a summary of the Internet of Things Software\n Update (IoTSU) Workshop that took place at Trinity College Dublin,\n Ireland on the 13th and 14th of June, 2016. The main goal of the\n workshop was to foster a discussion on requirements, challenges, and\n solutions for bringing software and firmware updates to IoT devices.\n This report summarizes the discussions and lists recommendations to\n the standards community.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IA","scope_keywords":["8240","certificate","http","https","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9019","folder":"IETF/RFC-9019","source":"IETF/RFC-9019/RFC-9019.txt","version":null}],"search_text":"IETF RFC 8240 This document provides a summary of the Internet of Things Software\n Update (IoTSU) Workshop that took place at Trinity College Dublin,\n Ireland on the 13th and 14th of June, 2016. The main goal of the\n workshop was to foster a discussion on requirements, challenges, and\n solutions for bringing software and firmware updates to IoT devices.\n This report summarizes the discussions and lists recommendations to\n the standards community.\n\n Note that this document is a report on the proceedings of the\n workshop. The views and positions documented in this report are\n those of the workshop participants and do not necessarily reflect IAB\n views and positions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IA 8240 certificate http https license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 4117","type":"specification","body":"IETF","designation":"RFC 4117","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4117.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4117.txt","https://www.rfc-editor.org/rfc/rfc4117.pdf"],"folder":"IETF/RFC-4117","files":{"txt":{"path":"standards/IETF/RFC-4117/RFC-4117.txt","sha256":"2c5600c63f23b49fcbc2aa30b290ba38ac92f5d890292724737c195d90d8104b"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to invoke transcoding services using\n Session Initiation Protocol (SIP) and third party call control. This\n way of invocation meets the requirements for SIP regarding\n transcoding services invocation to support deaf, hard of hearing and\n speech-impaired individuals.","scope_keywords":["4117"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null}],"search_text":"IETF RFC 4117 This document describes how to invoke transcoding services using\n Session Initiation Protocol (SIP) and third party call control. This\n way of invocation meets the requirements for SIP regarding\n transcoding services invocation to support deaf, hard of hearing and\n speech-impaired individuals. 4117 nested-reference unchanged"},{"id":"IETF RFC 412","type":"specification","body":"IETF","designation":"RFC 412","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc412.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc412.txt","https://www.rfc-editor.org/rfc/rfc412.pdf"],"folder":"IETF/RFC-412","files":{"txt":{"path":"standards/IETF/RFC-412/RFC-412.txt","sha256":"4a28dc21a4cbf2cbdecda164fe309c8cd661eae555f4428edf23c58d3e4f1b58"}},"tags":["nested-reference","unchanged"],"summary":"Work Information Center # 12404 G. Hicks\nRequest for Comments # 412 Utah\n 27-Nov-72\n\n User FTP Documentation\n\n The attached document is the HELP file for the Utah-10\nimplementation of the User FTP Process. This is what the user has\ntyped on his console when he types 'HELP ', and as such is the only\ndocumention produced to date.\n\n [Page 1]\n\f\nUser FTP Documentation Detailed Command Listing\n\n FTP User Documentation\n November 27, 1972\n\nI. Control Characters\n\n There are several control characters that have meaning to the FTP\nProcess. First, the abort character is (SUB), next for\nediting, only , , , ,\n , , , , and have\nany meaning, (SOH) and (BS) are the character\ndelete keys. is the word delete character, Note: When dowing\nthe ' funktion, this character will delete the entire line typed.\n says take the next character literally. (ESC)\nterminates the command giving helpful noise words, and are\n","scope_keywords":["412","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 412 Work Information Center # 12404 G. Hicks\nRequest for Comments # 412 Utah\n 27-Nov-72\n\n User FTP Documentation\n\n The attached document is the HELP file for the Utah-10\nimplementation of the User FTP Process. This is what the user has\ntyped on his console when he types 'HELP ', and as such is the only\ndocumention produced to date.\n\n [Page 1]\n\f\nUser FTP Documentation Detailed Command Listing\n\n FTP User Documentation\n November 27, 1972\n\nI. Control Characters\n\n There are several control characters that have meaning to the FTP\nProcess. First, the abort character is (SUB), next for\nediting, only , , , ,\n , , , , and have\nany meaning, (SOH) and (BS) are the character\ndelete keys. is the word delete character, Note: When dowing\nthe ' funktion, this character will delete the entire line typed.\n says take the next character literally. (ESC)\nterminates the command giving helpful noise words, and are\n 412 key keys nested-reference unchanged"},{"id":"IETF RFC 4146","type":"specification","body":"IETF","designation":"RFC 4146","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4146.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4146.txt","https://www.rfc-editor.org/rfc/rfc4146.pdf"],"folder":"IETF/RFC-4146","files":{"txt":{"path":"standards/IETF/RFC-4146/RFC-4146.txt","sha256":"db0ccc7aedd04d055debb914f94e8f92f061c190aae85dff7bcb4ed8dd9c6245"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents a long-standing technique, supported by a large\n number of mail servers, which allows users to be notified of new\n mail. In addition to server support, there are a number of clients\n that support this, ranging from full email clients to specialized\n clients whose only purpose is to receive new mail notifications and\n alert a mail client.\n\n In brief, the server sends the string \"nm_notifyuser\" CRLF to the\n finger port on the IP address (either configured or last used) of the\n user who has received new mail.","scope_keywords":["4146","crl","license","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5423","folder":"IETF/RFC-5423","source":"IETF/RFC-5423/RFC-5423.txt","version":null},{"body":"IETF","designation":"RFC 5550","folder":"IETF/RFC-5550","source":"IETF/RFC-5550/RFC-5550.txt","version":null},{"body":"IETF","designation":"RFC 5551","folder":"IETF/RFC-5551","source":"IETF/RFC-5551/RFC-5551.txt","version":null}],"search_text":"IETF RFC 4146 This memo documents a long-standing technique, supported by a large\n number of mail servers, which allows users to be notified of new\n mail. In addition to server support, there are a number of clients\n that support this, ranging from full email clients to specialized\n clients whose only purpose is to receive new mail notifications and\n alert a mail client.\n\n In brief, the server sends the string \"nm_notifyuser\" CRLF to the\n finger port on the IP address (either configured or last used) of the\n user who has received new mail. 4146 crl license subject nested-reference unchanged"},{"id":"IETF RFC 418","type":"specification","body":"IETF","designation":"RFC 418","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc418.txt","https://www.rfc-editor.org/rfc/rfc418.pdf"],"folder":"IETF/RFC-418","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 430","folder":"IETF/RFC-430","source":"IETF/RFC-430/RFC-430.txt","version":null},{"body":"IETF","designation":"RFC 454","folder":"IETF/RFC-454","source":"IETF/RFC-454/RFC-454.txt","version":null}],"search_text":"IETF RFC 418 nested-reference unavailable"},{"id":"IETF RFC 420","type":"specification","body":"IETF","designation":"RFC 420","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc420.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc420.txt","https://www.rfc-editor.org/rfc/rfc420.pdf"],"folder":"IETF/RFC-420","files":{"txt":{"path":"standards/IETF/RFC-420/RFC-420.txt","sha256":"eff9165dff23268c56b0f321dea6db409641c39712ed7fa276c77d346d5d3538"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group H. Murray\nRequest for Comments: 420 Computer Corporation of America\nNIC 12764 04 January 1973\n\n CCA ICCC WEATHER DEMO\n\n THE WEATHER DEMO ORIGINALLY DEVELOPED FOR THE ICCC SHOW IS NOW\n GENERALLY AVAILABLE. IT IS A VERY NICE NETWORK DEMO SINCE IT REALLY\n CAN/DOES RUN ON TWO MACHINES.\n\n THIS DEMO IS TWO INDEPENDENT PROGRAMS. TOGETHER THEY TRY TO ANSWER\n ENGLISH QUESTIONS ABOUT THE WEATHER. FOR EXAMPLE, 'DID IT RAIN IN\n BOSTON ON OCTOBER 7?'. THE NATURAL LANGUAGE PROGRAM IS WRITTEN IN\n LISP. IT IS A MODIFICATION OF A SYSTEM DEVELOPED BY T. WINOGRAD AT\n MIT. THE OTHER HALF IS A PRIMITIVE DATACOMPUTER. THE DATACOMPUTER\n PROVIDES NETWORK DATAMANAGEMENT FACILITIES AND WILL INCORPORATE THE\n TRILLION-BIT UNICON CURRENTLY BEING INSTALLED AT AMES.\n\n THE TWO PROGRAMS COMMUNICATE VIA DATALANGUAGE USING THE NET.\n\n 'WEATHER' NOW USES HOST '37' AS THE LOCATION OF THE DATACOMPUTER.\n ","scope_keywords":["420","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 420 Network Working Group H. Murray\nRequest for Comments: 420 Computer Corporation of America\nNIC 12764 04 January 1973\n\n CCA ICCC WEATHER DEMO\n\n THE WEATHER DEMO ORIGINALLY DEVELOPED FOR THE ICCC SHOW IS NOW\n GENERALLY AVAILABLE. IT IS A VERY NICE NETWORK DEMO SINCE IT REALLY\n CAN/DOES RUN ON TWO MACHINES.\n\n THIS DEMO IS TWO INDEPENDENT PROGRAMS. TOGETHER THEY TRY TO ANSWER\n ENGLISH QUESTIONS ABOUT THE WEATHER. FOR EXAMPLE, 'DID IT RAIN IN\n BOSTON ON OCTOBER 7?'. THE NATURAL LANGUAGE PROGRAM IS WRITTEN IN\n LISP. IT IS A MODIFICATION OF A SYSTEM DEVELOPED BY T. WINOGRAD AT\n MIT. THE OTHER HALF IS A PRIMITIVE DATACOMPUTER. THE DATACOMPUTER\n PROVIDES NETWORK DATAMANAGEMENT FACILITIES AND WILL INCORPORATE THE\n TRILLION-BIT UNICON CURRENTLY BEING INSTALLED AT AMES.\n\n THE TWO PROGRAMS COMMUNICATE VIA DATALANGUAGE USING THE NET.\n\n 'WEATHER' NOW USES HOST '37' AS THE LOCATION OF THE DATACOMPUTER.\n  420 management nested-reference unchanged"},{"id":"IETF RFC 422","type":"specification","body":"IETF","designation":"RFC 422","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc422.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc422.txt","https://www.rfc-editor.org/rfc/rfc422.pdf"],"folder":"IETF/RFC-422","files":{"txt":{"path":"standards/IETF/RFC-422/RFC-422.txt","sha256":"a93c2955205cdfc7dcd53010f69af1390bffcc525fe53197f09fb39d0e9dee15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 422 BBN\nNIC: 13007 11 December 1972\nUpdates: RFC #413\n\n Traffic Statistics (November 1972)\n\nAttached are the Host traffic statistics for the month of\nNovember 1972.\n\nAAM/jm\nAttach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n NOVEMBER 1972\n\n MISSING DATA FOR 1, 3, 4, 5, 17, 18, 19, 20, 25\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 151897 12063 163960\nUCLA HOST 2 765560 8997 774557\nUCLA HOST 3 213530 2942 216472\n -------- -------- --------\n 1130987 24002 1154989 53857 21\n\nSRI HOST 1 1308261 51214 1359475\nSRI HOST 2 4696 489 5185\n -------- -------- --------\n 1312957 51703 1364660 62522 21\n\nUCSB HOST 1 714942 495570 1210512 34045 21\n\nUTAH HOST 1 591309 77843 669152 28158 21\n\nBBN HOST 2 3390144 763647 4153791\nBBN HOST 3 98068 84342 182410\nBBN HOST 4 101120 265 101385\n -------- -------- --------\n 3589332 848","scope_keywords":["422"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 443","folder":"IETF/RFC-443","source":"IETF/RFC-443/RFC-443.txt","version":null}],"search_text":"IETF RFC 422 Network Working Group A. McKenzie\nRequest for Comments: 422 BBN\nNIC: 13007 11 December 1972\nUpdates: RFC #413\n\n Traffic Statistics (November 1972)\n\nAttached are the Host traffic statistics for the month of\nNovember 1972.\n\nAAM/jm\nAttach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n NOVEMBER 1972\n\n MISSING DATA FOR 1, 3, 4, 5, 17, 18, 19, 20, 25\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 151897 12063 163960\nUCLA HOST 2 765560 8997 774557\nUCLA HOST 3 213530 2942 216472\n -------- -------- --------\n 1130987 24002 1154989 53857 21\n\nSRI HOST 1 1308261 51214 1359475\nSRI HOST 2 4696 489 5185\n -------- -------- --------\n 1312957 51703 1364660 62522 21\n\nUCSB HOST 1 714942 495570 1210512 34045 21\n\nUTAH HOST 1 591309 77843 669152 28158 21\n\nBBN HOST 2 3390144 763647 4153791\nBBN HOST 3 98068 84342 182410\nBBN HOST 4 101120 265 101385\n -------- -------- --------\n 3589332 848 422 nested-reference unchanged"},{"id":"IETF RFC 443","type":"specification","body":"IETF","designation":"RFC 443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc443.txt","https://www.rfc-editor.org/rfc/rfc443.pdf"],"folder":"IETF/RFC-443","files":{"txt":{"path":"standards/IETF/RFC-443/RFC-443.txt","sha256":"a0779b2eef7c5265fb7763ffd6f13bff31322553b910c56c526f894a2a6423db"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 443 BBN\nNIC: 13899 18 January 1973\nUpdates: RFC 422\n\n Traffic Statistics (December 1972)\n\n Attached are the Host traffic statistics for the month of December\n 1972.\n\n AAM/jm\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n DECEMBER 1972\n\n MISSING DATA FOR 2, 3, 4, 8, 15, 20\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 181141 57162 238303\n UCLA HOST 2 668578 44616 713194\n -------- -------- --------\n 849719 101778 951497 33989 25\n\n SRI HOST 1 1396436 17556 1413992\n SRI HOST 2 31365 3836 35201\n -------- -------- --------\n 1427801 21392 1449193 57112 25\n\n UCSB HOST 1 545166 173928 719094 21807 25\n\n UTAH HOST 1 536453 35616 572069 21458 25\n\n BBN HOST 2 2424250 373106 2797356\n BBN HOST 3 108384 29878 138262\n BBN HOST 4 153239 37 153276\n -------- -------- --------\n 2685873 403021 3088894 107435 25\n\n MIT HOST 1 48752","scope_keywords":["443"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 443 Network Working Group A. McKenzie\nRequest for Comments: 443 BBN\nNIC: 13899 18 January 1973\nUpdates: RFC 422\n\n Traffic Statistics (December 1972)\n\n Attached are the Host traffic statistics for the month of December\n 1972.\n\n AAM/jm\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n DECEMBER 1972\n\n MISSING DATA FOR 2, 3, 4, 8, 15, 20\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 181141 57162 238303\n UCLA HOST 2 668578 44616 713194\n -------- -------- --------\n 849719 101778 951497 33989 25\n\n SRI HOST 1 1396436 17556 1413992\n SRI HOST 2 31365 3836 35201\n -------- -------- --------\n 1427801 21392 1449193 57112 25\n\n UCSB HOST 1 545166 173928 719094 21807 25\n\n UTAH HOST 1 536453 35616 572069 21458 25\n\n BBN HOST 2 2424250 373106 2797356\n BBN HOST 3 108384 29878 138262\n BBN HOST 4 153239 37 153276\n -------- -------- --------\n 2685873 403021 3088894 107435 25\n\n MIT HOST 1 48752 443 nested-reference unchanged"},{"id":"IETF RFC 4238","type":"specification","body":"IETF","designation":"RFC 4238","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4238.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4238.txt","https://www.rfc-editor.org/rfc/rfc4238.pdf"],"folder":"IETF/RFC-4238","files":{"txt":{"path":"standards/IETF/RFC-4238/RFC-4238.txt","sha256":"b1d674d1de6138f03278599ba4f83f0fff52c050b8bc5d99b3e4cf8ed99db628"}},"tags":["nested-reference","unchanged"],"summary":"Voice messaging is traditionally addressed using telephone number\n addressing. This document describes two techniques for routing voice\n messages based on a telephone number. The complete service uses the\n Voice Profile for Internet Mail (VPIM) Directory service to lookup a\n VPIM email address with a telephone number and confirm that the\n address is both valid and associated with the intended recipient.\n However, this service will take time to become widely deployed in the\n near term. This document also describes a basic send-and-pray\n service that routes and delivers messages using only the ENUM\n telephone number resolution service and the existing DNS mail routing\n facilities.\n\nVaudreuil Standards Track [Page 1]\n\f\nRFC 4238 Voice Message Routing Service October 2005","scope_keywords":["4238","attribute","attributes","policies","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4238 Voice messaging is traditionally addressed using telephone number\n addressing. This document describes two techniques for routing voice\n messages based on a telephone number. The complete service uses the\n Voice Profile for Internet Mail (VPIM) Directory service to lookup a\n VPIM email address with a telephone number and confirm that the\n address is both valid and associated with the intended recipient.\n However, this service will take time to become widely deployed in the\n near term. This document also describes a basic send-and-pray\n service that routes and delivers messages using only the ENUM\n telephone number resolution service and the existing DNS mail routing\n facilities.\n\nVaudreuil Standards Track [Page 1]\n\f\nRFC 4238 Voice Message Routing Service October 2005 4238 attribute attributes policies profile nested-reference unchanged"},{"id":"IETF RFC 6194","type":"specification","body":"IETF","designation":"RFC 6194","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6194.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6194.txt","https://www.rfc-editor.org/rfc/rfc6194.pdf"],"folder":"IETF/RFC-6194","files":{"txt":{"path":"standards/IETF/RFC-6194/RFC-6194.txt","sha256":"7a826d37bf32b2b4e872dcf9c0bae142c067d2892ceeafd500701085181e67be"}},"tags":["nested-reference","unchanged"],"summary":"This document includes security considerations for the SHA-0 and\n SHA-1 message digest algorithm.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6194.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume","scope_keywords":["6194","algorithm","algorithms","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6234","folder":"IETF/RFC-6234","source":"IETF/RFC-6234/RFC-6234.txt","version":null},{"body":"IETF","designation":"RFC 6275","folder":"IETF/RFC-6275","source":"IETF/RFC-6275/RFC-6275.txt","version":null},{"body":"IETF","designation":"RFC 6545","folder":"IETF/RFC-6545","source":"IETF/RFC-6545/RFC-6545.txt","version":null},{"body":"IETF","designation":"RFC 6584","folder":"IETF/RFC-6584","source":"IETF/RFC-6584/RFC-6584.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 7677","folder":"IETF/RFC-7677","source":"IETF/RFC-7677/RFC-7677.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 9054","folder":"IETF/RFC-9054","source":"IETF/RFC-9054/RFC-9054.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"IETF RFC 6194 This document includes security considerations for the SHA-0 and\n SHA-1 message digest algorithm.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6194.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This docume 6194 algorithm algorithms hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 5701","type":"specification","body":"IETF","designation":"RFC 5701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5701.txt","https://www.rfc-editor.org/rfc/rfc5701.pdf"],"folder":"IETF/RFC-5701","files":{"txt":{"path":"standards/IETF/RFC-5701/RFC-5701.txt","sha256":"979cb09671947754c1113e41a3691ba6ee9ae809449513c8351bd49c079549dc"}},"tags":["nested-reference","unchanged"],"summary":"Current specifications of BGP Extended Communities (RFC 4360) support\n the IPv4 Address Specific Extended Community, but do not support an\n IPv6 Address Specific Extended Community. The lack of an IPv6\n Address Specific Extended Community may be a problem when an\n application uses the IPv4 Address Specific Extended Community, and\n one wants to use this application in a pure IPv6 environment. This\n document defines a new BGP attribute, the IPv6 Address Specific\n Extended Community, that addresses this problem. The IPv6 Address\n Specific Extended Community is similar to the IPv4 Address Specific\n Extended Community, except that it carries an IPv6 address rather\n than an IPv4 address.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition o","scope_keywords":["5701","attribute","http","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7153","folder":"IETF/RFC-7153","source":"IETF/RFC-7153/RFC-7153.txt","version":null},{"body":"IETF","designation":"RFC 7606","folder":"IETF/RFC-7606","source":"IETF/RFC-7606/RFC-7606.txt","version":null}],"search_text":"IETF RFC 5701 Current specifications of BGP Extended Communities (RFC 4360) support\n the IPv4 Address Specific Extended Community, but do not support an\n IPv6 Address Specific Extended Community. The lack of an IPv6\n Address Specific Extended Community may be a problem when an\n application uses the IPv4 Address Specific Extended Community, and\n one wants to use this application in a pure IPv6 environment. This\n document defines a new BGP attribute, the IPv6 Address Specific\n Extended Community, that addresses this problem. The IPv6 Address\n Specific Extended Community is similar to the IPv4 Address Specific\n Extended Community, except that it carries an IPv6 address rather\n than an IPv4 address.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition o 5701 attribute http license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 451","type":"specification","body":"IETF","designation":"RFC 451","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc451.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc451.txt","https://www.rfc-editor.org/rfc/rfc451.pdf"],"folder":"IETF/RFC-451","files":{"txt":{"path":"standards/IETF/RFC-451/RFC-451.txt","sha256":"ef5bd650019b4b34cb710b2bc92384523b6e8981824dce56edf757170be8e608"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M.A. Padlipsky\nRequest for Comments # 451 MIT-Multics\nNIC # 14135 February 22, 1973\n\n Tentative Proposal for a Unified User Level Protocol\n\nNow that proposals for expansions to the Telnet Protocol are in vogue\nagain (RFC's 426 and 435, for example), I'd like to promote some\ndiscussion of a particular favorite of my own. Please note that this is\npresented as a tentative proposal: it's an attempt to consider the\ndesirability of a new approach, not a rigorous specification. To begin\nsomewhat obliquely, for some time I've felt that we (the NWG) have\nfallen into a trap in regard to the Initial Connection Protocol. The\npoint is that even though the ICP gives us the ability to define a\n\"family\" of ICPlets by varying the contact socket, there's no compelling\nreason why we should do so. That we have done so in the FTP and RJEP I\nview as unfortunate--but also undesirable and ","scope_keywords":["451"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 491","folder":"IETF/RFC-491","source":"IETF/RFC-491/RFC-491.txt","version":null}],"search_text":"IETF RFC 451 Network Working Group M.A. Padlipsky\nRequest for Comments # 451 MIT-Multics\nNIC # 14135 February 22, 1973\n\n Tentative Proposal for a Unified User Level Protocol\n\nNow that proposals for expansions to the Telnet Protocol are in vogue\nagain (RFC's 426 and 435, for example), I'd like to promote some\ndiscussion of a particular favorite of my own. Please note that this is\npresented as a tentative proposal: it's an attempt to consider the\ndesirability of a new approach, not a rigorous specification. To begin\nsomewhat obliquely, for some time I've felt that we (the NWG) have\nfallen into a trap in regard to the Initial Connection Protocol. The\npoint is that even though the ICP gives us the ability to define a\n\"family\" of ICPlets by varying the contact socket, there's no compelling\nreason why we should do so. That we have done so in the FTP and RJEP I\nview as unfortunate--but also undesirable and  451 nested-reference unchanged"},{"id":"IETF RFC 463","type":"specification","body":"IETF","designation":"RFC 463","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc463.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc463.txt","https://www.rfc-editor.org/rfc/rfc463.pdf"],"folder":"IETF/RFC-463","files":{"txt":{"path":"standards/IETF/RFC-463/RFC-463.txt","sha256":"f8cf41478204f5ec56a99e6c82a4f4d0c723a42f028fc66499fbc8a9eba89df5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Abhay K. Bhushan\nRFC # 463 MIT-DMCG\nNIC # 14573 February 21, 1973\n\n FTP Comments and Response to RFC 430\n\n Most of the comments in RFC 430 by Bob Braden are useful suggestions\nwhich should be included in the forthcoming official FTP specification.\nThis RFC represents my response to Braden's comments and other views.\nThese comments should be useful for the FTP meeting on March 16 at BBN\n(announcement warning AAM NIC #14417). The results of the FTP subgroup\nmeeting held at BBN on January 25 will be published in RFC 4541 (are\npublished?).\n\nSPECIFIC RESPONSES TO RFC 430.\n\n Item A1 - I will let Bob Braden handle the \"print file\" issues (the\n \"still\" should be removed).\n\n Item A2 - I agree that concessions are undesirable and should be\n removed unless people cannot \"live\" without them.\n\n Item A3 - I strongly support \"bit flag coding\" for descriptors.\n Other definition imp","scope_keywords":["463"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 463 Network Working Group Abhay K. Bhushan\nRFC # 463 MIT-DMCG\nNIC # 14573 February 21, 1973\n\n FTP Comments and Response to RFC 430\n\n Most of the comments in RFC 430 by Bob Braden are useful suggestions\nwhich should be included in the forthcoming official FTP specification.\nThis RFC represents my response to Braden's comments and other views.\nThese comments should be useful for the FTP meeting on March 16 at BBN\n(announcement warning AAM NIC #14417). The results of the FTP subgroup\nmeeting held at BBN on January 25 will be published in RFC 4541 (are\npublished?).\n\nSPECIFIC RESPONSES TO RFC 430.\n\n Item A1 - I will let Bob Braden handle the \"print file\" issues (the\n \"still\" should be removed).\n\n Item A2 - I agree that concessions are undesirable and should be\n removed unless people cannot \"live\" without them.\n\n Item A3 - I strongly support \"bit flag coding\" for descriptors.\n Other definition imp 463 nested-reference unchanged"},{"id":"IETF RFC 4418","type":"specification","body":"IETF","designation":"RFC 4418","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4418.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4418.txt","https://www.rfc-editor.org/rfc/rfc4418.pdf"],"folder":"IETF/RFC-4418","files":{"txt":{"path":"standards/IETF/RFC-4418/RFC-4418.txt","sha256":"8944b1c5c4a7e06625963667577e839a8e518e60973540bb0b47cb70a0711580"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes how to generate an authentication tag\n using the UMAC message authentication algorithm. UMAC is designed to\n be very fast to compute in software on contemporary uniprocessors.\n Measured speeds are as low as one cycle per byte. UMAC relies on\n addition of 32-bit and 64-bit numbers and multiplication of 32-bit\n numbers, operations well-supported by contemporary machines.\n\n To generate the authentication tag on a given message, a \"universal\"\n hash function is applied to the message and key to produce a short,\n fixed-length hash value, and this hash value is then xor'ed with a\n key-derived pseudorandom pad. UMAC enjoys a rigorous security\n analysis, and its only internal \"cryptographic\" component is a block\n cipher used to generate the pseudorandom pads and internal key\n material.\n\nKrovetz Informational [Page 1]\n\f\nRFC 4418 UMAC March 2006","scope_keywords":["4418","algorithm","authentication","encryption","hash","hashing","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4808","folder":"IETF/RFC-4808","source":"IETF/RFC-4808/RFC-4808.txt","version":null}],"search_text":"IETF RFC 4418 This specification describes how to generate an authentication tag\n using the UMAC message authentication algorithm. UMAC is designed to\n be very fast to compute in software on contemporary uniprocessors.\n Measured speeds are as low as one cycle per byte. UMAC relies on\n addition of 32-bit and 64-bit numbers and multiplication of 32-bit\n numbers, operations well-supported by contemporary machines.\n\n To generate the authentication tag on a given message, a \"universal\"\n hash function is applied to the message and key to produce a short,\n fixed-length hash value, and this hash value is then xor'ed with a\n key-derived pseudorandom pad. UMAC enjoys a rigorous security\n analysis, and its only internal \"cryptographic\" component is a block\n cipher used to generate the pseudorandom pads and internal key\n material.\n\nKrovetz Informational [Page 1]\n\f\nRFC 4418 UMAC March 2006 4418 algorithm authentication encryption hash hashing key keys nested-reference unchanged"},{"id":"IETF RFC 4328","type":"specification","body":"IETF","designation":"RFC 4328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4328.txt","https://www.rfc-editor.org/rfc/rfc4328.pdf"],"folder":"IETF/RFC-4328","files":{"txt":{"path":"standards/IETF/RFC-4328/RFC-4328.txt","sha256":"b58694cbc6ba3c5c678b3e1509fa39e3e77eeb99e614173cad4e902c08fb1546"}},"tags":["nested-reference","unchanged"],"summary":"This document is a companion to the Generalized Multi-Protocol Label\n Switching (GMPLS) signaling documents. It describes the technology-\n specific information needed to extend GMPLS signaling to control\n Optical Transport Networks (OTN); it also includes the so-called\n pre-OTN developments.","scope_keywords":["4328","key","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4802","folder":"IETF/RFC-4802","source":"IETF/RFC-4802/RFC-4802.txt","version":null}],"search_text":"IETF RFC 4328 This document is a companion to the Generalized Multi-Protocol Label\n Switching (GMPLS) signaling documents. It describes the technology-\n specific information needed to extend GMPLS signaling to control\n Optical Transport Networks (OTN); it also includes the so-called\n pre-OTN developments. 4328 key management pid nested-reference unchanged"},{"id":"IETF RFC 5620","type":"specification","body":"IETF","designation":"RFC 5620","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5620.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5620.txt","https://www.rfc-editor.org/rfc/rfc5620.pdf"],"folder":"IETF/RFC-5620","files":{"txt":{"path":"standards/IETF/RFC-5620/RFC-5620.txt","sha256":"3b1ddaa599e982f661c642fee16e07b748d5b465a3f113eab4ea0b9b7b987f6c"}},"tags":["nested-reference","unchanged"],"summary":"The RFC Editor performs a number of functions that may be carried out\n by various persons or entities. The RFC Editor model presented in\n this document divides the responsibilities for the RFC Series into\n four functions: The RFC Series Editor, the Independent Submission\n Editor, the RFC Production Center, and the RFC Publisher. It also\n introduces the RFC Series Advisory Group and an (optional)\n Independent Submission Stream Editorial Board. The model outlined\n here is intended to increase flexibility and operational support\n options, provide for the orderly succession of the RFC Editor, and\n ensure the continuity of the RFC series, while maintaining RFC\n quality and timely processing, ensuring document accessibility,\n reducing costs, and increasing cost transparency.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet stand","scope_keywords":["5620","archiving","http","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5744","folder":"IETF/RFC-5744","source":"IETF/RFC-5744/RFC-5744.txt","version":null},{"body":"IETF","designation":"RFC 6635","folder":"IETF/RFC-6635","source":"IETF/RFC-6635/RFC-6635.txt","version":null}],"search_text":"IETF RFC 5620 The RFC Editor performs a number of functions that may be carried out\n by various persons or entities. The RFC Editor model presented in\n this document divides the responsibilities for the RFC Series into\n four functions: The RFC Series Editor, the Independent Submission\n Editor, the RFC Production Center, and the RFC Publisher. It also\n introduces the RFC Series Advisory Group and an (optional)\n Independent Submission Stream Editorial Board. The model outlined\n here is intended to increase flexibility and operational support\n options, provide for the orderly succession of the RFC Editor, and\n ensure the continuity of the RFC series, while maintaining RFC\n quality and timely processing, ensuring document accessibility,\n reducing costs, and increasing cost transparency.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet stand 5620 archiving http license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 434","type":"specification","body":"IETF","designation":"RFC 434","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc434.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc434.txt","https://www.rfc-editor.org/rfc/rfc434.pdf"],"folder":"IETF/RFC-434","files":{"txt":{"path":"standards/IETF/RFC-434/RFC-434.txt","sha256":"cb3d35b12bdcf6e483556191adf6ee2977ca8e78838934cbf261e4f4cf74e748"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Alexander A. McKenzie\nRFC 434 BBN-NET\nNIC 13658 January 4, 1973\n\n IMP/TIP MEMORY RETROFIT SCHEDULE\n\n During the first several months of 1973 we will be retrofitting each\n IMP and TIP with additional core memory. At the end of the retrofit\n program, the memory sizes of the various machines will be as follows:\n\n IMP (516 or 316) - 16K words\n\n TIP - 28K words\n\n TIP with magnetic Tape Option - 32K words\n\n In addition, the expansion of the TIP core memory will necessitate\n enlarging the TIP to two cabinets.\n\n Listed below is the preliminary schedule for these retrofits. We\n have arranged this schedule to coincide with the usual monthly\n Preventive Maintenance at each site so as to minimize user\n inconvenience, but the work required will frequently require the\n machines to be down longer than normal. I will issue additional\n RFC's updating this schedule as necessary.\n\n An","scope_keywords":["434"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 434 Network Working Group Alexander A. McKenzie\nRFC 434 BBN-NET\nNIC 13658 January 4, 1973\n\n IMP/TIP MEMORY RETROFIT SCHEDULE\n\n During the first several months of 1973 we will be retrofitting each\n IMP and TIP with additional core memory. At the end of the retrofit\n program, the memory sizes of the various machines will be as follows:\n\n IMP (516 or 316) - 16K words\n\n TIP - 28K words\n\n TIP with magnetic Tape Option - 32K words\n\n In addition, the expansion of the TIP core memory will necessitate\n enlarging the TIP to two cabinets.\n\n Listed below is the preliminary schedule for these retrofits. We\n have arranged this schedule to coincide with the usual monthly\n Preventive Maintenance at each site so as to minimize user\n inconvenience, but the work required will frequently require the\n machines to be down longer than normal. I will issue additional\n RFC's updating this schedule as necessary.\n\n An 434 nested-reference unchanged"},{"id":"IETF RFC 4344","type":"specification","body":"IETF","designation":"RFC 4344","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4344.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4344.txt","https://www.rfc-editor.org/rfc/rfc4344.pdf"],"folder":"IETF/RFC-4344","files":{"txt":{"path":"standards/IETF/RFC-4344/RFC-4344.txt","sha256":"be7136101f41619175421f0343866bd9a4eee0b32b74a29f29e8fd26e7ef01ce"}},"tags":["nested-reference","unchanged"],"summary":"Researchers have discovered that the authenticated encryption portion\n of the current SSH Transport Protocol is vulnerable to several\n attacks.\n\n This document describes new symmetric encryption methods for the\n Secure Shell (SSH) Transport Protocol and gives specific\n recommendations on how frequently SSH implementations should rekey.","scope_keywords":["4344","encryption","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4345","folder":"IETF/RFC-4345","source":"IETF/RFC-4345/RFC-4345.txt","version":null}],"search_text":"IETF RFC 4344 Researchers have discovered that the authenticated encryption portion\n of the current SSH Transport Protocol is vulnerable to several\n attacks.\n\n This document describes new symmetric encryption methods for the\n Secure Shell (SSH) Transport Protocol and gives specific\n recommendations on how frequently SSH implementations should rekey. 4344 encryption key nested-reference unchanged"},{"id":"IETF RFC 6229","type":"specification","body":"IETF","designation":"RFC 6229","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6229.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6229.txt","https://www.rfc-editor.org/rfc/rfc6229.pdf"],"folder":"IETF/RFC-6229","files":{"txt":{"path":"standards/IETF/RFC-6229/RFC-6229.txt","sha256":"8602f8b3199ecf18d8a89a4dba19f9683f947d5c8306c137e16b34fb0da79eb7"}},"tags":["nested-reference","unchanged"],"summary":"This document contains test vectors for the stream cipher RC4.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6229.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IET","scope_keywords":["6229","algorithm","algorithms","hash","hashing","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 7181","folder":"IETF/RFC-7181","source":"IETF/RFC-7181/RFC-7181.txt","version":null}],"search_text":"IETF RFC 6229 This document contains test vectors for the stream cipher RC4.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6229.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IET 6229 algorithm algorithms hash hashing http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 4531","type":"specification","body":"IETF","designation":"RFC 4531","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4531.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4531.txt","https://www.rfc-editor.org/rfc/rfc4531.pdf"],"folder":"IETF/RFC-4531","files":{"txt":{"path":"standards/IETF/RFC-4531/RFC-4531.txt","sha256":"266ec03d0134f3a2063e840722743bf183cb5a772d3b84d46373e08c425437c8"}},"tags":["nested-reference","unchanged"],"summary":"This specification describes a Lightweight Directory Access Protocol\n (LDAP) extended operation to reverse (or \"turn\") the roles of client\n and server for subsequent protocol exchanges in the session, or to\n enable each peer to act as both client and server with respect to the\n other.","scope_keywords":["4531","authentication","policy","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null}],"search_text":"IETF RFC 4531 This specification describes a Lightweight Directory Access Protocol\n (LDAP) extended operation to reverse (or \"turn\") the roles of client\n and server for subsequent protocol exchanges in the session, or to\n enable each peer to act as both client and server with respect to the\n other. 4531 authentication policy tls nested-reference unchanged"},{"id":"IETF RFC 7457","type":"specification","body":"IETF","designation":"RFC 7457","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7457.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7457.txt","https://www.rfc-editor.org/rfc/rfc7457.pdf"],"folder":"IETF/RFC-7457","files":{"txt":{"path":"standards/IETF/RFC-7457/RFC-7457.txt","sha256":"f90360738aaa90dc2071e82bc089ffd1169995e7104ae252cd596444da49685f"}},"tags":["nested-reference","unchanged"],"summary":"Over the last few years, there have been several serious attacks on\n Transport Layer Security (TLS), including attacks on its most\n commonly used ciphers and modes of operation. This document\n summarizes these attacks, with the goal of motivating generic and\n protocol-specific recommendations on the usage of TLS and Datagram\n TLS (DTLS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, an","scope_keywords":["7457","attribute","certificate","http","key","keys","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7525","folder":"IETF/RFC-7525","source":"IETF/RFC-7525/RFC-7525.txt","version":null},{"body":"IETF","designation":"RFC 7590","folder":"IETF/RFC-7590","source":"IETF/RFC-7590/RFC-7590.txt","version":null},{"body":"IETF","designation":"RFC 7627","folder":"IETF/RFC-7627","source":"IETF/RFC-7627/RFC-7627.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8143","folder":"IETF/RFC-8143","source":"IETF/RFC-8143/RFC-8143.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null},{"body":"IETF","designation":"RFC 8932","folder":"IETF/RFC-8932","source":"IETF/RFC-8932/RFC-8932.txt","version":null},{"body":"IETF","designation":"RFC 8996","folder":"IETF/RFC-8996","source":"IETF/RFC-8996/RFC-8996.txt","version":null},{"body":"IETF","designation":"RFC 9190","folder":"IETF/RFC-9190","source":"IETF/RFC-9190/RFC-9190.txt","version":null},{"body":"IETF","designation":"RFC 9325","folder":"IETF/RFC-9325","source":"IETF/RFC-9325/RFC-9325.txt","version":null}],"search_text":"IETF RFC 7457 Over the last few years, there have been several serious attacks on\n Transport Layer Security (TLS), including attacks on its most\n commonly used ciphers and modes of operation. This document\n summarizes these attacks, with the goal of motivating generic and\n protocol-specific recommendations on the usage of TLS and Datagram\n TLS (DTLS).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, an 7457 attribute certificate http key keys license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 4355","type":"specification","body":"IETF","designation":"RFC 4355","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4355.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4355.txt","https://www.rfc-editor.org/rfc/rfc4355.pdf"],"folder":"IETF/RFC-4355","files":{"txt":{"path":"standards/IETF/RFC-4355/RFC-4355.txt","sha256":"f3cc8e165e2da9ab8628fc89ac20f6808e18e4cd4a1396e4cdae43db15050fed"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Enumservices \"email\", \"fax\", \"sms\",\n \"ems\", and \"mms\" using the URI schemes 'tel:' and 'mailto:' as per\n the IANA registration process defined in the ENUM specification RFC\n 3761.\n\nBrandner, et al. Standards Track [Page 1]\n\f\nRFC 4355 IANA Msg Enumservice Registrations January 2006","scope_keywords":["4355","key","policies","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4355 This document registers the Enumservices \"email\", \"fax\", \"sms\",\n \"ems\", and \"mms\" using the URI schemes 'tel:' and 'mailto:' as per\n the IANA registration process defined in the ENUM specification RFC\n 3761.\n\nBrandner, et al. Standards Track [Page 1]\n\f\nRFC 4355 IANA Msg Enumservice Registrations January 2006 4355 key policies registered nested-reference unchanged"},{"id":"IETF RFC 5830","type":"specification","body":"IETF","designation":"RFC 5830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5830.txt","https://www.rfc-editor.org/rfc/rfc5830.pdf"],"folder":"IETF/RFC-5830","files":{"txt":{"path":"standards/IETF/RFC-5830/RFC-5830.txt","sha256":"5b85a3587130cd2c43e6b3a4a41f6b3bdaa3b320c84e0298a09c4fe1016b663e"}},"tags":["nested-reference","unchanged"],"summary":"This document is intended to be a source of information about the\n Russian Federal standard for electronic encryption, decryption, and\n message authentication algorithms (GOST 28147-89), which is one of\n the Russian cryptographic standard algorithms called GOST\n algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST 28147-89 for encryption,\n decryption, and message authentication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the","scope_keywords":["5830","algorithm","algorithms","authentication","encryption","http","key","keys","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 5830 This document is intended to be a source of information about the\n Russian Federal standard for electronic encryption, decryption, and\n message authentication algorithms (GOST 28147-89), which is one of\n the Russian cryptographic standard algorithms called GOST\n algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST 28147-89 for encryption,\n decryption, and message authentication.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the 5830 algorithm algorithms authentication encryption http key keys license subject trust nested-reference unchanged"},{"id":"IETF RFC 5832","type":"specification","body":"IETF","designation":"RFC 5832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5832.txt","https://www.rfc-editor.org/rfc/rfc5832.pdf"],"folder":"IETF/RFC-5832","files":{"txt":{"path":"standards/IETF/RFC-5832/RFC-5832.txt","sha256":"af8a37e9c70e0375cc32588cf398aebcf7b4be2079451fece484bc6d15ae0069"}},"tags":["nested-reference","unchanged"],"summary":"This document is intended to be a source of information about the\n Russian Federal standard for digital signatures (GOST R 34.10-2001),\n which is one of the Russian cryptographic standard algorithms (called\n GOST algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST R 34.10-2001 for digital\n signature generation and verification.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of In","scope_keywords":["5832","algorithm","algorithms","hash","http","key","license","signature","signatures","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 5832 This document is intended to be a source of information about the\n Russian Federal standard for digital signatures (GOST R 34.10-2001),\n which is one of the Russian cryptographic standard algorithms (called\n GOST algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST R 34.10-2001 for digital\n signature generation and verification.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of In 5832 algorithm algorithms hash http key license signature signatures subject trust nested-reference unchanged"},{"id":"IETF RFC 436","type":"specification","body":"IETF","designation":"RFC 436","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc436.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc436.txt","https://www.rfc-editor.org/rfc/rfc436.pdf"],"folder":"IETF/RFC-436","files":{"txt":{"path":"standards/IETF/RFC-436/RFC-436.txt","sha256":"db0803c890a650f358d9a2c883b4bbeaf83b31e75f43a1b901ede3fc4c561c59"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mark Krilanovich\nRFC #436 UCSB\nNIC #13700 Jan. 10 1973\n\n Announcement of RJS at UCSB\n\n There now is resident under socket 5 at UCSB a server program which\nsupports a subset of the Remote Job Entry Protocol of RFC #407. This\ndocument includes enough information to allow the user to gain access\nto, and use the more basic function of UCSB's RJS. An RFC containing\nmore detailed documentation will be forthcoming shortly.\n\n The accounting parameters needed to login to RJS are a userid and a\npassword, each consisting of one to eight alphameric characters, the\nfirst of which must be alphabetic. The userid is, at present,\ncompletely arbitrary. The password is arbitrary the first time it is\nused with a particular userid; in subsequent logins with that userid,\nthe same password must appear. Eventually, users will be assigned\nuserid-password pairs by UCSB Computer Center.\n\n The","scope_keywords":["436","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 436 Network Working Group Mark Krilanovich\nRFC #436 UCSB\nNIC #13700 Jan. 10 1973\n\n Announcement of RJS at UCSB\n\n There now is resident under socket 5 at UCSB a server program which\nsupports a subset of the Remote Job Entry Protocol of RFC #407. This\ndocument includes enough information to allow the user to gain access\nto, and use the more basic function of UCSB's RJS. An RFC containing\nmore detailed documentation will be forthcoming shortly.\n\n The accounting parameters needed to login to RJS are a userid and a\npassword, each consisting of one to eight alphameric characters, the\nfirst of which must be alphabetic. The userid is, at present,\ncompletely arbitrary. The password is arbitrary the first time it is\nused with a particular userid; in subsequent logins with that userid,\nthe same password must appear. Eventually, users will be assigned\nuserid-password pairs by UCSB Computer Center.\n\n The 436 path nested-reference unchanged"},{"id":"IETF RFC 4393","type":"specification","body":"IETF","designation":"RFC 4393","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4393.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4393.txt","https://www.rfc-editor.org/rfc/rfc4393.pdf"],"folder":"IETF/RFC-4393","files":{"txt":{"path":"standards/IETF/RFC-4393/RFC-4393.txt","sha256":"22396afdf50ccba038db0c386a27513a9ccbd3c3b4bac0dc4033ecd54bb0ee42"}},"tags":["nested-reference","unchanged"],"summary":"This document serves to register and document the standard MIME types\n associated with the 3GPP2 multimedia file format, which is part of\n the family based on the ISO Media File Format.","scope_keywords":["4393","authentication","encryption","http","identification","key","presentation","risk","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null}],"search_text":"IETF RFC 4393 This document serves to register and document the standard MIME types\n associated with the 3GPP2 multimedia file format, which is part of\n the family based on the ISO Media File Format. 4393 authentication encryption http identification key presentation risk subject nested-reference unchanged"},{"id":"IETF RFC 441","type":"specification","body":"IETF","designation":"RFC 441","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc441.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc441.txt","https://www.rfc-editor.org/rfc/rfc441.pdf"],"folder":"IETF/RFC-441","files":{"txt":{"path":"standards/IETF/RFC-441/RFC-441.txt","sha256":"01a9b7b00987a6aadc33a8093be4bbc15424e3b14d70f660fecb93db8d5e420b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bob Bressler\nRequest for Comments: 441 Bob Thomas\nNIC 13773 January 19, 1973\n\n Inter-Entity Communication - An Experiment\n\n This note is an attempt to be a status report concerning an\n experiment based on the desire of users, at their consoles, to\n converse with one another, and perhaps to get some debugging\n assistance. The user might ask: \"who can I talk to\"; \"can I show him\n what I have done\", and \"can I let him run my program?\" Many time\n sharing systems provide capabilities such as these, within the bounds\n of their system. Almost all systems have a \"WHO\" or \"SYSTAT\", many\n have commands like \"LINK\" or \"TALK\", and some support more esoteric\n capabilities like controlling another user's program. At the last\n formal meeting of the Network Working Group, in October of 1971 at\n MIT, a group got together to talk about these features for Inter\n Entity Communications ","scope_keywords":["441","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 441 Network Working Group Bob Bressler\nRequest for Comments: 441 Bob Thomas\nNIC 13773 January 19, 1973\n\n Inter-Entity Communication - An Experiment\n\n This note is an attempt to be a status report concerning an\n experiment based on the desire of users, at their consoles, to\n converse with one another, and perhaps to get some debugging\n assistance. The user might ask: \"who can I talk to\"; \"can I show him\n what I have done\", and \"can I let him run my program?\" Many time\n sharing systems provide capabilities such as these, within the bounds\n of their system. Almost all systems have a \"WHO\" or \"SYSTAT\", many\n have commands like \"LINK\" or \"TALK\", and some support more esoteric\n capabilities like controlling another user's program. At the last\n formal meeting of the Network Working Group, in October of 1971 at\n MIT, a group got together to talk about these features for Inter\n Entity Communications  441 identification nested-reference unchanged"},{"id":"IETF RFC 4415","type":"specification","body":"IETF","designation":"RFC 4415","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4415.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4415.txt","https://www.rfc-editor.org/rfc/rfc4415.pdf"],"folder":"IETF/RFC-4415","files":{"txt":{"path":"standards/IETF/RFC-4415/RFC-4415.txt","sha256":"adce04cca4a9c5db0095a815121f008636ae1dacd2739c4d1941aa1cbc5c8b7a"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Enumservice \"voice\" (which has a defined\n subtype \"tel\"), as per the IANA registration process defined in the\n ENUM specification RFC 3761. This service indicates that the contact\n held in the generated Uniform Resource Identifier (URI) can be used\n to initiate an interactive voice (audio) call.","scope_keywords":["4415","key","qualified","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4415 This document registers the Enumservice \"voice\" (which has a defined\n subtype \"tel\"), as per the IANA registration process defined in the\n ENUM specification RFC 3761. This service indicates that the contact\n held in the generated Uniform Resource Identifier (URI) can be used\n to initiate an interactive voice (audio) call. 4415 key qualified registered nested-reference unchanged"},{"id":"IETF RFC 442","type":"specification","body":"IETF","designation":"RFC 442","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc442.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc442.txt","https://www.rfc-editor.org/rfc/rfc442.pdf"],"folder":"IETF/RFC-442","files":{"txt":{"path":"standards/IETF/RFC-442/RFC-442.txt","sha256":"5959e3324a83236669dba18d53af5eb3fe7ae5473a2a7fec0c370547fce80655"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 442 24 January 1973\nNIC: 13774\n\n The Current Flow-Control Scheme for IMPSYS\n\n BB&N quarterly report #13 outlines part of the current flow control\n scheme in the IMP operating system. A meeting held March 16, 1972,\n at BB&N was devoted to the description of this new scheme for the\n benefit of interested network participants.\n\n This note represents my understanding of the flow control mechanism.\n The essential goal is to eliminate unnecessary retransmissions when\n the load is heavy, eliminate the retransmission time-out period when\n the load is light, increase bandwidth, prevent re-assembly lock-up,\n control traffic from HOSTS into the net more strictly than the\n earlier link blocking method, and secure the rights of life, liberty,\n and the pursuit of happiness for ourselves and our posterity,...oops.\n\nSource IMP-to-Destination IMP Protoc","scope_keywords":["442","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 442 Network Working Group V. Cerf\nRequest for Comments: 442 24 January 1973\nNIC: 13774\n\n The Current Flow-Control Scheme for IMPSYS\n\n BB&N quarterly report #13 outlines part of the current flow control\n scheme in the IMP operating system. A meeting held March 16, 1972,\n at BB&N was devoted to the description of this new scheme for the\n benefit of interested network participants.\n\n This note represents my understanding of the flow control mechanism.\n The essential goal is to eliminate unnecessary retransmissions when\n the load is heavy, eliminate the retransmission time-out period when\n the load is light, increase bandwidth, prevent re-assembly lock-up,\n control traffic from HOSTS into the net more strictly than the\n earlier link blocking method, and secure the rights of life, liberty,\n and the pursuit of happiness for ourselves and our posterity,...oops.\n\nSource IMP-to-Destination IMP Protoc 442 key nested-reference unchanged"},{"id":"IETF RFC 44520","type":"specification","body":"IETF","designation":"RFC 44520","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc44520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc44520.txt","https://www.rfc-editor.org/rfc/rfc44520.pdf"],"folder":"IETF/RFC-44520","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null}],"search_text":"IETF RFC 44520 nested-reference unavailable"},{"id":"IETF RFC 7905","type":"specification","body":"IETF","designation":"RFC 7905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7905.txt","https://www.rfc-editor.org/rfc/rfc7905.pdf"],"folder":"IETF/RFC-7905","files":{"txt":{"path":"standards/IETF/RFC-7905/RFC-7905.txt","sha256":"afa1e233822c6bda1f1ced014d32e6d740454415b53130fa84630a9c5ad2fe69"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the use of the ChaCha stream cipher and\n Poly1305 authenticator in the Transport Layer Security (TLS) and\n Datagram Transport Layer Security (DTLS) protocols.\n\n This document updates RFCs 5246 and 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7905.\n\nLangley, et al. Standards Track [Page 1]\n\f\nRFC 7905 ChaCha-Poly1305 for TLS June 2016\n\nCopyright Notice\n\n Co","scope_keywords":["7905","algorithm","encryption","hash","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"IETF RFC 7905 This document describes the use of the ChaCha stream cipher and\n Poly1305 authenticator in the Transport Layer Security (TLS) and\n Datagram Transport Layer Security (DTLS) protocols.\n\n This document updates RFCs 5246 and 6347.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7905.\n\nLangley, et al. Standards Track [Page 1]\n\f\nRFC 7905 ChaCha-Poly1305 for TLS June 2016\n\nCopyright Notice\n\n Co 7905 algorithm encryption hash http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 491","type":"specification","body":"IETF","designation":"RFC 491","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc491.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc491.txt","https://www.rfc-editor.org/rfc/rfc491.pdf"],"folder":"IETF/RFC-491","files":{"txt":{"path":"standards/IETF/RFC-491/RFC-491.txt","sha256":"94ef604b9c92905cdca5d6b0e39f5960c978ad316b2e1d3796b6ffc18e897ac1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. A. Padlipsky\nRequest for Comments: 491 MIT-Multics\nNIC: 15356 12 April 1973\n\n What Is Free\n\n In at least three of the RFC's about \"mail\" and the File Transfer\n Protocol (RFC's 454, 475, 479), something very like the following is\n asserted: \"Network mail should be free; i.e., no login or USER\n command should be required.\" Unfortunately, \"i.e\" (=that is) is\n misleading. It simply does not follow to imply that the only way\n mail can be free is for it not to require a login; explicit login on\n a free account would of course also work. Indeed, depending upon\n per-Host idiosyncrasies in the Logger / Answering Service / process\n creation environment, an explicit login may well prove to be far more\n natural than an implicit login. (Even in environments where implicit\n login is easy, surely explicit login is just easy.) Granted, login\n on a free account requires users to ","scope_keywords":["491","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 501","folder":"IETF/RFC-501","source":"IETF/RFC-501/RFC-501.txt","version":null},{"body":"IETF","designation":"RFC 505","folder":"IETF/RFC-505","source":"IETF/RFC-505/RFC-505.txt","version":null}],"search_text":"IETF RFC 491 Network Working Group M. A. Padlipsky\nRequest for Comments: 491 MIT-Multics\nNIC: 15356 12 April 1973\n\n What Is Free\n\n In at least three of the RFC's about \"mail\" and the File Transfer\n Protocol (RFC's 454, 475, 479), something very like the following is\n asserted: \"Network mail should be free; i.e., no login or USER\n command should be required.\" Unfortunately, \"i.e\" (=that is) is\n misleading. It simply does not follow to imply that the only way\n mail can be free is for it not to require a login; explicit login on\n a free account would of course also work. Indeed, depending upon\n per-Host idiosyncrasies in the Logger / Answering Service / process\n creation environment, an explicit login may well prove to be far more\n natural than an implicit login. (Even in environments where implicit\n login is easy, surely explicit login is just easy.) Granted, login\n on a free account requires users to  491 authentication nested-reference unchanged"},{"id":"IETF RFC 453","type":"specification","body":"IETF","designation":"RFC 453","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc453.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc453.txt","https://www.rfc-editor.org/rfc/rfc453.pdf"],"folder":"IETF/RFC-453","files":{"txt":{"path":"standards/IETF/RFC-453/RFC-453.txt","sha256":"850c2d1a30a613f7b26cf2d74ee4eb314c48e69526500bf776b54e11eebb6537"}},"tags":["nested-reference","unchanged"],"summary":"The purpose of this RFC is to announce a meeting at SRI-ARC on the\nNetwork Mail problem discussed at the January 1973 Principal\nInvestigators' Meeting in San Diego.","scope_keywords":["453","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 453 The purpose of this RFC is to announce a meeting at SRI-ARC on the\nNetwork Mail problem discussed at the January 1973 Principal\nInvestigators' Meeting in San Diego. 453 identification subject nested-reference unchanged"},{"id":"IETF RFC 468","type":"specification","body":"IETF","designation":"RFC 468","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc468.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc468.txt","https://www.rfc-editor.org/rfc/rfc468.pdf"],"folder":"IETF/RFC-468","files":{"txt":{"path":"standards/IETF/RFC-468/RFC-468.txt","sha256":"9cbbd993f69cbfaace9470ef07b9ed6c02fb0bfbd0bc3bbd022cbafd792ce3b8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Braden\nRequest for Comment: 468 UCLA/CCN\nNIC: 14742 March 8, 1973\n\n FTP DATA COMPRESSION\n\nI. INTRODUCTION\n\nAPOLOGIA\n\n Major design objectives of the proposed File Transfer Protocol (FTP)\n are reliability and efficiency for transmission of large files.\n Efficiency has two faces: efficiency of the host CPU's, and efficient\n use of the Network bandwidth. Block mode is intended to minimize CPU\n overhead for bandwidth efficiency, there is a mode called \"HASP\" in\n RFC 454. The \"HASP\" mode of FTP is really transmission with data\n compression, i.e., an encoding scheme to reduce the information\n redundancy in the messages.\n\n RFC 454 contains no explicit definition of the \"HASP\" or compressed\n mode, but instead notes that a future RFC by yours truly will define\n the mode. Students of FTP may find this scarcely credible, but you\n are now reading the promised RFC. It turned ","scope_keywords":["468","algorithm","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 468 Network Working Group R. Braden\nRequest for Comment: 468 UCLA/CCN\nNIC: 14742 March 8, 1973\n\n FTP DATA COMPRESSION\n\nI. INTRODUCTION\n\nAPOLOGIA\n\n Major design objectives of the proposed File Transfer Protocol (FTP)\n are reliability and efficiency for transmission of large files.\n Efficiency has two faces: efficiency of the host CPU's, and efficient\n use of the Network bandwidth. Block mode is intended to minimize CPU\n overhead for bandwidth efficiency, there is a mode called \"HASP\" in\n RFC 454. The \"HASP\" mode of FTP is really transmission with data\n compression, i.e., an encoding scheme to reduce the information\n redundancy in the messages.\n\n RFC 454 contains no explicit definition of the \"HASP\" or compressed\n mode, but instead notes that a future RFC by yours truly will define\n the mode. Students of FTP may find this scarcely credible, but you\n are now reading the promised RFC. It turned  468 algorithm trust nested-reference unchanged"},{"id":"IETF RFC 455","type":"specification","body":"IETF","designation":"RFC 455","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc455.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc455.txt","https://www.rfc-editor.org/rfc/rfc455.pdf"],"folder":"IETF/RFC-455","files":{"txt":{"path":"standards/IETF/RFC-455/RFC-455.txt","sha256":"c2456d7cf2f226e56ae3646d75131d0b35bfca366534417c8096df9dbeccf0f7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 455 BBN\nNIC: 14375 12 February 1973\n\n Traffic Statistics (January 1973)\n\nAttached are the Host traffic statistics for the month of January 1973.\n\nAAM/jm\n\nAttach.\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JANUARY 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 191053 48601 239654\nUCLA HOST 2 1124219 27595 1151814\n --------- ------ -------\n 1315272 76196 1391468 42428 31\n\nSRI HOST 1 2778675 38938 2817613\nSRI HOST 2 50570 2523 53093\n -------- ------ --------\n 2829245 41461 2870706 91266 31\n\nUCSB HOST 1 1503946 1177354 2681300 48514 31\n\nBBN HOST 2 3645936 747861 4393797\nBBN HOST 3 76277 174815 251092\nBBN HOST 4 182456 67 182523\n -------- ------ -------\n 3904669 922743 4827412 125957 31\n\nMIT HOST 1 123582 22731 146313\nMIT HOST 2 125534 94244 219778\nMIT HOST 3 771730 523251 1294981\nMIT HOST 4 277007 624947 ","scope_keywords":["455"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 482","folder":"IETF/RFC-482","source":"IETF/RFC-482/RFC-482.txt","version":null}],"search_text":"IETF RFC 455 Network Working Group A. McKenzie\nRequest for Comments: 455 BBN\nNIC: 14375 12 February 1973\n\n Traffic Statistics (January 1973)\n\nAttached are the Host traffic statistics for the month of January 1973.\n\nAAM/jm\n\nAttach.\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JANUARY 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 1 191053 48601 239654\nUCLA HOST 2 1124219 27595 1151814\n --------- ------ -------\n 1315272 76196 1391468 42428 31\n\nSRI HOST 1 2778675 38938 2817613\nSRI HOST 2 50570 2523 53093\n -------- ------ --------\n 2829245 41461 2870706 91266 31\n\nUCSB HOST 1 1503946 1177354 2681300 48514 31\n\nBBN HOST 2 3645936 747861 4393797\nBBN HOST 3 76277 174815 251092\nBBN HOST 4 182456 67 182523\n -------- ------ -------\n 3904669 922743 4827412 125957 31\n\nMIT HOST 1 123582 22731 146313\nMIT HOST 2 125534 94244 219778\nMIT HOST 3 771730 523251 1294981\nMIT HOST 4 277007 624947  455 nested-reference unchanged"},{"id":"IETF RFC 482","type":"specification","body":"IETF","designation":"RFC 482","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc482.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc482.txt","https://www.rfc-editor.org/rfc/rfc482.pdf"],"folder":"IETF/RFC-482","files":{"txt":{"path":"standards/IETF/RFC-482/RFC-482.txt","sha256":"ffb826d959926c1942f64dd02dc84327f6c5b99c9b437ab7813da41200392270"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 482 BBN-NET\nNIC: 14966 12 March 1973\nUpdates: RFC 455\n\n Traffic Statistics (February 1973)\n\n Attached are the Host traffic statistics for the month of February\n 1973.\n\n AAM/jm\n Attach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n FEBRUARY 1973\n\n MISSING DATA FOR 7, 8\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 317437 34933 352370\n UCLA HOST 2 1058286 63540 1121826\n -------- -------- --------\n 1375723 98473 1474196 52912 26\n\n SRI HOST 1 2423370 100583 2523953\n SRI HOST 2 130260 8178 138438\n -------- -------- --------\n 2553630 108761 2662391 98217 26\n\n UCSB HOST 1 914034 974131 1888165 35155 26\n\n UTAH HOST 1 627257 143632 770889 24125 26\n\n BBN HOST 1 0 4640 4640\n BBN HOST 2 3552317 779092 4331409\n BBN HOST 3 79020 72763 151783\n BBN HOST 4 150285 4529 154814\n -------- -------- --------\n 3781622 861024 4642","scope_keywords":["482"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 482 Network Working Group A. McKenzie\nRequest for Comments: 482 BBN-NET\nNIC: 14966 12 March 1973\nUpdates: RFC 455\n\n Traffic Statistics (February 1973)\n\n Attached are the Host traffic statistics for the month of February\n 1973.\n\n AAM/jm\n Attach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n FEBRUARY 1973\n\n MISSING DATA FOR 7, 8\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 1 317437 34933 352370\n UCLA HOST 2 1058286 63540 1121826\n -------- -------- --------\n 1375723 98473 1474196 52912 26\n\n SRI HOST 1 2423370 100583 2523953\n SRI HOST 2 130260 8178 138438\n -------- -------- --------\n 2553630 108761 2662391 98217 26\n\n UCSB HOST 1 914034 974131 1888165 35155 26\n\n UTAH HOST 1 627257 143632 770889 24125 26\n\n BBN HOST 1 0 4640 4640\n BBN HOST 2 3552317 779092 4331409\n BBN HOST 3 79020 72763 151783\n BBN HOST 4 150285 4529 154814\n -------- -------- --------\n 3781622 861024 4642 482 nested-reference unchanged"},{"id":"IETF RFC 458","type":"specification","body":"IETF","designation":"RFC 458","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc458.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc458.txt","https://www.rfc-editor.org/rfc/rfc458.pdf"],"folder":"IETF/RFC-458","files":{"txt":{"path":"standards/IETF/RFC-458/RFC-458.txt","sha256":"daa5be70a78aaea9d966cedc8a2c6047f8509bf01526e68803b34821d697f83d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Bressler\nRequest for Comments: 458 BBN-NET\nNIC: 14378 B. Thomas\n BBN-TENEX\n 20 February 1973\n\n Mail Retrieval via FTP\n\n We propose two new FTP commands called ReaDMailFile and ReaDMail.\n These commands are intended to be symmetric with respect to the\n current MLFL and MAIL commands. They would allow a user to read his\n mail at one or more sites without incurring the overhead of logging\n in and without having to use several different retrieval methods.\n The user might go further and create a program to go around to all\n the server sites and retrieve his mail for him. The current FTP\n mechanisms provide for password protection, should security be\n required.\n\n This proposal brings into focus, once again, the problems of\n different users with the same ID, and to a lesser extent, one user\n with multiple IDs. This RFC does not attempt to address these issues\n at this t","scope_keywords":["458"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 475","folder":"IETF/RFC-475","source":"IETF/RFC-475/RFC-475.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 458 Network Working Group B. Bressler\nRequest for Comments: 458 BBN-NET\nNIC: 14378 B. Thomas\n BBN-TENEX\n 20 February 1973\n\n Mail Retrieval via FTP\n\n We propose two new FTP commands called ReaDMailFile and ReaDMail.\n These commands are intended to be symmetric with respect to the\n current MLFL and MAIL commands. They would allow a user to read his\n mail at one or more sites without incurring the overhead of logging\n in and without having to use several different retrieval methods.\n The user might go further and create a program to go around to all\n the server sites and retrieve his mail for him. The current FTP\n mechanisms provide for password protection, should security be\n required.\n\n This proposal brings into focus, once again, the problems of\n different users with the same ID, and to a lesser extent, one user\n with multiple IDs. This RFC does not attempt to address these issues\n at this t 458 nested-reference unchanged"},{"id":"IETF RFC 475","type":"specification","body":"IETF","designation":"RFC 475","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc475.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc475.txt","https://www.rfc-editor.org/rfc/rfc475.pdf"],"folder":"IETF/RFC-475","files":{"pdf":{"path":"standards/IETF/RFC-475/RFC-475.pdf","sha256":"1539899a96e242969f7e3d6065a5b19542916e29896005d72b194a15cae49f48"},"txt":{"path":"standards/IETF/RFC-475/RFC-475.txt","sha256":"8a136873b480ed6589fa421aec9b956c1e19c34e324be14c5ceb52715fe28853"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Bhushan\nRequest for Comments: 475 MIT-DMCG\nNIC: 14919 March 6, 1973\n\n FTP AND NETWORK MAIL SYSTEM\n\n This paper describes my understanding of the results of the Network\n Mail System meeting SRI-ARC on February 23, 1973, and the\n implications for FTP (File Transfer Protocol). There was general\n agreement at the meeting that network mail function should be within\n FTP.\n\n FTP currently provides two commands for handling mail. The MAIL\n command allows a user to send mail via the TELNET connection (the\n server collects the mail and determines its end by searching for the\n character sequence \"CRLF.CRLF\"). The MLFL (mail file) command allows\n a user to send mail via the data connection (requires a user-FTP to\n handle the command but transfer is more efficient as server need not\n search for a special character sequence). These commands are being\n used to provide network m","scope_keywords":["475","crl","delivery","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 491","folder":"IETF/RFC-491","source":"IETF/RFC-491/RFC-491.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 475 Network Working Group A. Bhushan\nRequest for Comments: 475 MIT-DMCG\nNIC: 14919 March 6, 1973\n\n FTP AND NETWORK MAIL SYSTEM\n\n This paper describes my understanding of the results of the Network\n Mail System meeting SRI-ARC on February 23, 1973, and the\n implications for FTP (File Transfer Protocol). There was general\n agreement at the meeting that network mail function should be within\n FTP.\n\n FTP currently provides two commands for handling mail. The MAIL\n command allows a user to send mail via the TELNET connection (the\n server collects the mail and determines its end by searching for the\n character sequence \"CRLF.CRLF\"). The MLFL (mail file) command allows\n a user to send mail via the data connection (requires a user-FTP to\n handle the command but transfer is more efficient as server need not\n search for a special character sequence). These commands are being\n used to provide network m 475 crl delivery identification nested-reference unchanged"},{"id":"IETF RFC 459","type":"specification","body":"IETF","designation":"RFC 459","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc459.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc459.txt","https://www.rfc-editor.org/rfc/rfc459.pdf"],"folder":"IETF/RFC-459","files":{"txt":{"path":"standards/IETF/RFC-459/RFC-459.txt","sha256":"5b86bd33b3d3eccc1a9a9a36e72e97262d5eed922737347ed4ab379f67fcd2a9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Kantrowitz\nRFC: 459 LL-TX-2\nNIC: 14379 February 26, 1973\n\n Network Questionnaires\n\n In recent times, a steady stream of questionnaires has been arriving\nfrom the network community. Each questionnaire creates an additional\ndistraction from more useful work and raises the general annoyance level\nsomewhat. The arrival of the seven-page NCP questionnaire (RFC 460) has\npushed the annoyance level over the top.\n\n We are wondering if any of the questionnaire polluters has given any\nthought to the fact that it takes time to fill out these questionnaires\nespecially if one wants to do a conscientious job and provide reasonable\nanswers to questions which are frequently only partially applicable.\n\n It seems rather presumptuous for RFC 460 to provide a lengthy\nquestionnaire without any explanation as to the motivation for it and\nthen request a response in two weeks. And tantal","scope_keywords":["459"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 514","folder":"IETF/RFC-514","source":"IETF/RFC-514/RFC-514.txt","version":null},{"body":"IETF","designation":"RFC 531","folder":"IETF/RFC-531","source":"IETF/RFC-531/RFC-531.txt","version":null}],"search_text":"IETF RFC 459 Network Working Group W. Kantrowitz\nRFC: 459 LL-TX-2\nNIC: 14379 February 26, 1973\n\n Network Questionnaires\n\n In recent times, a steady stream of questionnaires has been arriving\nfrom the network community. Each questionnaire creates an additional\ndistraction from more useful work and raises the general annoyance level\nsomewhat. The arrival of the seven-page NCP questionnaire (RFC 460) has\npushed the annoyance level over the top.\n\n We are wondering if any of the questionnaire polluters has given any\nthought to the fact that it takes time to fill out these questionnaires\nespecially if one wants to do a conscientious job and provide reasonable\nanswers to questions which are frequently only partially applicable.\n\n It seems rather presumptuous for RFC 460 to provide a lengthy\nquestionnaire without any explanation as to the motivation for it and\nthen request a response in two weeks. And tantal 459 nested-reference unchanged"},{"id":"IETF RFC 514","type":"specification","body":"IETF","designation":"RFC 514","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc514.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc514.txt","https://www.rfc-editor.org/rfc/rfc514.pdf"],"folder":"IETF/RFC-514","files":{"txt":{"path":"standards/IETF/RFC-514/RFC-514.txt","sha256":"97740579806ad472af1ff744b77168e09b2dfd16ecd8361700aea079adf0c196"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group W. Kantrowitz\nRequest for Comments: 514 LL TX-2\nNIC: 16445 5 June 1973\nUpdates: RFC 459\n\n NETWORK MAKE-WORK\n\n The ARPA Network seems to have developed the proclivity of dragging\n compulsive collectors and organizers out of the woodwork and placing\n them in the forefront to annoy everybody.\n\n Recent occurrences have been:\n\n 1. A set of charts on characteristics of the hosts. The orientation\n seems to have been: If you can come up with names for the\n horizontal and vertical nodes and if it has to do with the hosts,\n make a chart out of it. This collection of charts goes under the\n euphemism \"ARPA Network handbook\". Information on a host is\n scattered over all the pages which is a questionable organizing\n scheme. Additionally, since the charts contain much of what is\n already in the Resource Notebook, we now have the delightful task\n of maintaining two documents when c","scope_keywords":["514","key","management","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 531","folder":"IETF/RFC-531","source":"IETF/RFC-531/RFC-531.txt","version":null}],"search_text":"IETF RFC 514 Network Working Group W. Kantrowitz\nRequest for Comments: 514 LL TX-2\nNIC: 16445 5 June 1973\nUpdates: RFC 459\n\n NETWORK MAKE-WORK\n\n The ARPA Network seems to have developed the proclivity of dragging\n compulsive collectors and organizers out of the woodwork and placing\n them in the forefront to annoy everybody.\n\n Recent occurrences have been:\n\n 1. A set of charts on characteristics of the hosts. The orientation\n seems to have been: If you can come up with names for the\n horizontal and vertical nodes and if it has to do with the hosts,\n make a chart out of it. This collection of charts goes under the\n euphemism \"ARPA Network handbook\". Information on a host is\n scattered over all the pages which is a questionable organizing\n scheme. Additionally, since the charts contain much of what is\n already in the Resource Notebook, we now have the delightful task\n of maintaining two documents when c 514 key management subject nested-reference unchanged"},{"id":"IETF RFC 460","type":"specification","body":"IETF","designation":"RFC 460","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc460.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc460.txt","https://www.rfc-editor.org/rfc/rfc460.pdf"],"folder":"IETF/RFC-460","files":{"txt":{"path":"standards/IETF/RFC-460/RFC-460.txt","sha256":"1513cdb6aa65dd0f84d0ba619ff829db842cf83400ac06354d98c5ef8bd36657"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Chuck S. Kline CSK\nRequest for Comments: 460 UCLA\nNIC 14415 13 February 73\n\n NCP Survey\n\n 1 This RFC is the first in a series which will request information on\n implementation of host to host protocol. We would appreciate a reply\n to this RFC from all sites within two weeks. One convenient way to\n reply is to make a copy of this RFC at the NIC and insert the replies\n at the appropriate spots. The results of this survey will be\n published. Please send replies to nic ident CSK or to\n\n Charles Kline\n Boelter Hall 3804\n UCLA\n 405 Hilgard Ave.\n Los Angeles, Cal. 90034\n\n 2 This particular RFC will deal with implementations of Network\n Control Programs (NCPs). Future RFCs will deal with .\n implementations of Telnet, RJE, etc.\n\n 3 In order to ask questions about NCPs and get meaningful replies, I\n will here describe what I consider to be my concept of an NCP.\n\n 3a An NCP is","scope_keywords":["460","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 459","folder":"IETF/RFC-459","source":"IETF/RFC-459/RFC-459.txt","version":null}],"search_text":"IETF RFC 460 Network Working Group Chuck S. Kline CSK\nRequest for Comments: 460 UCLA\nNIC 14415 13 February 73\n\n NCP Survey\n\n 1 This RFC is the first in a series which will request information on\n implementation of host to host protocol. We would appreciate a reply\n to this RFC from all sites within two weeks. One convenient way to\n reply is to make a copy of this RFC at the NIC and insert the replies\n at the appropriate spots. The results of this survey will be\n published. Please send replies to nic ident CSK or to\n\n Charles Kline\n Boelter Hall 3804\n UCLA\n 405 Hilgard Ave.\n Los Angeles, Cal. 90034\n\n 2 This particular RFC will deal with implementations of Network\n Control Programs (NCPs). Future RFCs will deal with .\n implementations of Telnet, RJE, etc.\n\n 3 In order to ask questions about NCPs and get meaningful replies, I\n will here describe what I consider to be my concept of an NCP.\n\n 3a An NCP is 460 management nested-reference unchanged"},{"id":"IETF RFC 4606","type":"specification","body":"IETF","designation":"RFC 4606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4606.txt","https://www.rfc-editor.org/rfc/rfc4606.pdf"],"folder":"IETF/RFC-4606","files":{"txt":{"path":"standards/IETF/RFC-4606/RFC-4606.txt","sha256":"3b77539a19f54dcb69f26f5a8a8fade65ac3f21915067ae7274f7add1782aef6"}},"tags":["nested-reference","unchanged"],"summary":"This document provides minor clarification to RFC 3946.\n\n This document is a companion to the Generalized Multi-protocol Label\n Switching (GMPLS) signaling. It defines the Synchronous Optical\n Network (SONET)/Synchronous Digital Hierarchy (SDH) technology-\n specific information needed when GMPLS signaling is used.","scope_keywords":["4606","key","path","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null}],"search_text":"IETF RFC 4606 This document provides minor clarification to RFC 3946.\n\n This document is a companion to the Generalized Multi-protocol Label\n Switching (GMPLS) signaling. It defines the Synchronous Optical\n Network (SONET)/Synchronous Digital Hierarchy (SDH) technology-\n specific information needed when GMPLS signaling is used. 4606 key path profile nested-reference unchanged"},{"id":"IETF RFC 4628","type":"specification","body":"IETF","designation":"RFC 4628","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4628.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4628.txt","https://www.rfc-editor.org/rfc/rfc4628.pdf"],"folder":"IETF/RFC-4628","files":{"txt":{"path":"standards/IETF/RFC-4628/RFC-4628.txt","sha256":"e56b39fe67cac168c21f1ab18b110873ef87b12457b4974b2b9ecbc58096b364"}},"tags":["nested-reference","unchanged"],"summary":"The first RFC that describes an RTP payload format for ITU\n Telecommunication Standardization Sector (ITU-T) recommendation H.263\n is RFC 2190. This specification discusses why to move RFC 2190 to\n historic status.","scope_keywords":["4628","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null}],"search_text":"IETF RFC 4628 The first RFC that describes an RTP payload format for ITU\n Telecommunication Standardization Sector (ITU-T) recommendation H.263\n is RFC 2190. This specification discusses why to move RFC 2190 to\n historic status. 4628 http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6835","type":"specification","body":"IETF","designation":"RFC 6835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6835.txt","https://www.rfc-editor.org/rfc/rfc6835.pdf"],"folder":"IETF/RFC-6835","files":{"txt":{"path":"standards/IETF/RFC-6835/RFC-6835.txt","sha256":"f68c4750f74b4f811f731cd4962b43f382baf4cfb36d25f41e21b1b96c6d073d"}},"tags":["nested-reference","unchanged"],"summary":"A simple tool called the Locator/ID Separation Protocol (LISP)\n Internet Groper or 'lig' can be used to query the LISP mapping\n database. This document describes how it works.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6835.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the p","scope_keywords":["6835","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null}],"search_text":"IETF RFC 6835 A simple tool called the Locator/ID Separation Protocol (LISP)\n Internet Groper or 'lig' can be used to query the LISP mapping\n database. This document describes how it works.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6835.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the p 6835 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 4637","type":"specification","body":"IETF","designation":"RFC 4637","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc4637.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4637.txt","https://www.rfc-editor.org/rfc/rfc4637.pdf"],"folder":"IETF/RFC-4637","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"IETF RFC 4637 nested-reference unavailable"},{"id":"IETF RFC 467","type":"specification","body":"IETF","designation":"RFC 467","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc467.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc467.txt","https://www.rfc-editor.org/rfc/rfc467.pdf"],"folder":"IETF/RFC-467","files":{"txt":{"path":"standards/IETF/RFC-467/RFC-467.txt","sha256":"995a8d0319efa83b1509ad5b3cbecdf96b489c667c63b50fbc4b4c9bfe7e9364"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Burchfiel\nRequest for Comments: 467 R. Tomlinson\nNIC: 14741 Bolt Beranek and Newman\n 20 February 1973\n\n Proposed Change To Host-Host Protocol\n Resynchronization Of Connection Status\n\nI. Introduction\n\n The current Host-Host protocol (NIC #8246) contains no provisions for\n resynchronizing the status information kept at the two ends of each\n connection. In particular, if either host suffers a service\n interruption, or if a control message is lost or corrupted in an\n interface or in the subnet, the status information at the two ends of\n the connection will be inconsistent.\n\n Since the current protocol provides no way to correct this condition,\n the NCP's at the two ends stay \"confused\" forever. A frequent and\n frustrating symptom of this effect is the \"lost allocate\" phenomenon,\n where the receiving NCP believes that it has bit and message\n allocations outstanding, w","scope_keywords":["467"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 501","folder":"IETF/RFC-501","source":"IETF/RFC-501/RFC-501.txt","version":null}],"search_text":"IETF RFC 467 Network Working Group J. Burchfiel\nRequest for Comments: 467 R. Tomlinson\nNIC: 14741 Bolt Beranek and Newman\n 20 February 1973\n\n Proposed Change To Host-Host Protocol\n Resynchronization Of Connection Status\n\nI. Introduction\n\n The current Host-Host protocol (NIC #8246) contains no provisions for\n resynchronizing the status information kept at the two ends of each\n connection. In particular, if either host suffers a service\n interruption, or if a control message is lost or corrupted in an\n interface or in the subnet, the status information at the two ends of\n the connection will be inconsistent.\n\n Since the current protocol provides no way to correct this condition,\n the NCP's at the two ends stay \"confused\" forever. A frequent and\n frustrating symptom of this effect is the \"lost allocate\" phenomenon,\n where the receiving NCP believes that it has bit and message\n allocations outstanding, w 467 nested-reference unchanged"},{"id":"IETF RFC 469","type":"specification","body":"IETF","designation":"RFC 469","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc469.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc469.txt","https://www.rfc-editor.org/rfc/rfc469.pdf"],"folder":"IETF/RFC-469","files":{"txt":{"path":"standards/IETF/RFC-469/RFC-469.txt","sha256":"c700b4102fd04ca3b37ea1b01c1dc8ce281ac190177c76ca40ba68e0d1eb37d1"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC#469 Michael D. Kudlick MDK (SRI-ARC)\nNIC 14798 8-MAR-73\n\n Network Mail Meeting Summary\n\nIntroduction\n\n The purpose of this RFC is to briefly summarize, from the NIC's\n viewpoint, the principal conclusions reached at the Network Mail\n Meeting held Friday, February 23 1973, at SRI-ARC.\n\n Please refer to RFC #475 (NIC 14919) for Abhay Bhushan's\n comprehensive summary of the issues discussed at the meeting.\n\n There is no major disagreement between the present RFC and RFC\n #475.\n\n RFC #453 (NIC 14317) contains background information on the\n meeting.\n\n RFC #479 (NIC 14948) describes what the NIC would like to see\n included in the File Transfer Protocol for Network Mail purposes,\n and also describes briefly how the NIC would use the information.\n\n The present RFC is organized as follows:\n\n Conclusions\n Discussion\n Attendees\n\nConclusions\n\n Additional FTP mail requirements were decided up","scope_keywords":["469","attribute","delivery","identification","key","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 469 NWG/RFC#469 Michael D. Kudlick MDK (SRI-ARC)\nNIC 14798 8-MAR-73\n\n Network Mail Meeting Summary\n\nIntroduction\n\n The purpose of this RFC is to briefly summarize, from the NIC's\n viewpoint, the principal conclusions reached at the Network Mail\n Meeting held Friday, February 23 1973, at SRI-ARC.\n\n Please refer to RFC #475 (NIC 14919) for Abhay Bhushan's\n comprehensive summary of the issues discussed at the meeting.\n\n There is no major disagreement between the present RFC and RFC\n #475.\n\n RFC #453 (NIC 14317) contains background information on the\n meeting.\n\n RFC #479 (NIC 14948) describes what the NIC would like to see\n included in the File Transfer Protocol for Network Mail purposes,\n and also describes briefly how the NIC would use the information.\n\n The present RFC is organized as follows:\n\n Conclusions\n Discussion\n Attendees\n\nConclusions\n\n Additional FTP mail requirements were decided up 469 attribute delivery identification key qualified subject nested-reference unchanged"},{"id":"IETF RFC 473","type":"specification","body":"IETF","designation":"RFC 473","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc473.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc473.txt","https://www.rfc-editor.org/rfc/rfc473.pdf"],"folder":"IETF/RFC-473","files":{"txt":{"path":"standards/IETF/RFC-473/RFC-473.txt","sha256":"d0039776bb787d2aef9ae658e3575c7ba024c848a516046fc38d4de7f1681fe1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Walden\nRequest for Comments: 473 BBN-NET\nNIC: 14811 28 February 1973\n\n MIX and MIXAL?\n\n Is there an interpreter for Knuth's hypothetical computer, MIX,\n together with an assemble for the MIX assembly language, MIXAL,\n available on any ARPA Network Host? If not, will not some Network\n Host make them available (cheaply)?--it would be considerable service\n to all of us who are students of the \"Art of Computer Programming.\"\n\n [This RFC was put into machine readable form for entry]\n [into the online RFC archives by Helene Morin, Via Genie 12/1999]\n\nWalden [Page 1]","scope_keywords":["473"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 473 Network Working Group D. Walden\nRequest for Comments: 473 BBN-NET\nNIC: 14811 28 February 1973\n\n MIX and MIXAL?\n\n Is there an interpreter for Knuth's hypothetical computer, MIX,\n together with an assemble for the MIX assembly language, MIXAL,\n available on any ARPA Network Host? If not, will not some Network\n Host make them available (cheaply)?--it would be considerable service\n to all of us who are students of the \"Art of Computer Programming.\"\n\n [This RFC was put into machine readable form for entry]\n [into the online RFC archives by Helene Morin, Via Genie 12/1999]\n\nWalden [Page 1] 473 nested-reference unchanged"},{"id":"IETF RFC 6583","type":"specification","body":"IETF","designation":"RFC 6583","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6583.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6583.txt","https://www.rfc-editor.org/rfc/rfc6583.pdf"],"folder":"IETF/RFC-6583","files":{"txt":{"path":"standards/IETF/RFC-6583/RFC-6583.txt","sha256":"96fd0fb82e1f5fa9dacc2a49870c6d20c4ec19aedd7bd3999ae7bf7c7d821fc4"}},"tags":["nested-reference","unchanged"],"summary":"In IPv4, subnets are generally small, made just large enough to cover\n the actual number of machines on the subnet. In contrast, the\n default IPv6 subnet size is a /64, a number so large it covers\n trillions of addresses, the overwhelming number of which will be\n unassigned. Consequently, simplistic implementations of Neighbor\n Discovery (ND) can be vulnerable to deliberate or accidental denial\n of service (DoS), whereby they attempt to perform address resolution\n for large numbers of unassigned addresses. Such denial-of-service\n attacks can be launched intentionally (by an attacker) or result from\n legitimate operational tools or accident conditions. As a result of\n these vulnerabilities, new devices may not be able to \"join\" a\n network, it may be impossible to establish new IPv6 flows, and\n existing IPv6 transported flows may be interrupted.\n\n This document describes the potential for ","scope_keywords":["6583","audit","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 7066","folder":"IETF/RFC-7066","source":"IETF/RFC-7066/RFC-7066.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7707","folder":"IETF/RFC-7707","source":"IETF/RFC-7707/RFC-7707.txt","version":null}],"search_text":"IETF RFC 6583 In IPv4, subnets are generally small, made just large enough to cover\n the actual number of machines on the subnet. In contrast, the\n default IPv6 subnet size is a /64, a number so large it covers\n trillions of addresses, the overwhelming number of which will be\n unassigned. Consequently, simplistic implementations of Neighbor\n Discovery (ND) can be vulnerable to deliberate or accidental denial\n of service (DoS), whereby they attempt to perform address resolution\n for large numbers of unassigned addresses. Such denial-of-service\n attacks can be launched intentionally (by an attacker) or result from\n legitimate operational tools or accident conditions. As a result of\n these vulnerabilities, new devices may not be able to \"join\" a\n network, it may be impossible to establish new IPv6 flows, and\n existing IPv6 transported flows may be interrupted.\n\n This document describes the potential for  6583 audit http license subject trust nested-reference unchanged"},{"id":"IETF RFC 8134","type":"specification","body":"IETF","designation":"RFC 8134","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8134.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8134.txt","https://www.rfc-editor.org/rfc/rfc8134.pdf"],"folder":"IETF/RFC-8134","files":{"txt":{"path":"standards/IETF/RFC-8134/RFC-8134.txt","sha256":"5e54cadc842f10a68a53d490e23d2ad828645cf4f576036afab7ac262c42f5f4"}},"tags":["nested-reference","unchanged"],"summary":"This document is a collection of implementation reports from vendors,\n consortiums, and researchers who have implemented one or more of the\n standards published from the IETF INCident Handling (INCH) and\n Management Incident Lightweight Exchange (MILE) working groups.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:/","scope_keywords":["8134","holder","http","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8274","folder":"IETF/RFC-8274","source":"IETF/RFC-8274/RFC-8274.txt","version":null}],"search_text":"IETF RFC 8134 This document is a collection of implementation reports from vendors,\n consortiums, and researchers who have implemented one or more of the\n standards published from the IETF INCident Handling (INCH) and\n Management Incident Lightweight Exchange (MILE) working groups.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http:/ 8134 holder http license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 4769","type":"specification","body":"IETF","designation":"RFC 4769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4769.txt","https://www.rfc-editor.org/rfc/rfc4769.pdf"],"folder":"IETF/RFC-4769","files":{"txt":{"path":"standards/IETF/RFC-4769/RFC-4769.txt","sha256":"11c8c4b9538d27e9a47865ff122cdb36d3f725c1c44c33efd16943bf143ece1c"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Enumservice type \"pstn\" and subtype \"tel\"\n using the URI scheme 'tel', as well as the subtype \"sip\" using the\n URI scheme 'sip' as per the IANA registration process defined in the\n ENUM specification, RFC 3761. This Enumservice is used to facilitate\n the routing of telephone calls in those countries where number\n portability exists.\n\nLivingood & Shockey Standards Track [Page 1]\n\f\nRFC 4769 PSTN Enumservice November 2006","scope_keywords":["4769","key","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4769 This document registers the Enumservice type \"pstn\" and subtype \"tel\"\n using the URI scheme 'tel', as well as the subtype \"sip\" using the\n URI scheme 'sip' as per the IANA registration process defined in the\n ENUM specification, RFC 3761. This Enumservice is used to facilitate\n the routing of telephone calls in those countries where number\n portability exists.\n\nLivingood & Shockey Standards Track [Page 1]\n\f\nRFC 4769 PSTN Enumservice November 2006 4769 key registered trust nested-reference unchanged"},{"id":"IETF RFC 4772","type":"specification","body":"IETF","designation":"RFC 4772","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4772.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4772.txt","https://www.rfc-editor.org/rfc/rfc4772.pdf"],"folder":"IETF/RFC-4772","files":{"txt":{"path":"standards/IETF/RFC-4772/RFC-4772.txt","sha256":"e5f1b3cec778c8d08b5d212b9a8b32e785cc113c8ec266e6c7445c8db30c6b71"}},"tags":["nested-reference","unchanged"],"summary":"The Data Encryption Standard (DES) is susceptible to brute-force\n attacks, which are well within the reach of a modestly financed\n adversary. As a result, DES has been deprecated, and replaced by the\n Advanced Encryption Standard (AES). Nonetheless, many applications\n continue to rely on DES for security, and designers and implementers\n continue to support it in new applications. While this is not always\n inappropriate, it frequently is. This note discusses DES security\n implications in detail, so that designers and implementers have all\n the information they need to make judicious decisions regarding its\n use.\n\nKelly Informational [Page 1]\n\f\nRFC 4772 DES Security Implications December 2006","scope_keywords":["4772","algorithm","encryption","key","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6649","folder":"IETF/RFC-6649","source":"IETF/RFC-6649/RFC-6649.txt","version":null}],"search_text":"IETF RFC 4772 The Data Encryption Standard (DES) is susceptible to brute-force\n attacks, which are well within the reach of a modestly financed\n adversary. As a result, DES has been deprecated, and replaced by the\n Advanced Encryption Standard (AES). Nonetheless, many applications\n continue to rely on DES for security, and designers and implementers\n continue to support it in new applications. While this is not always\n inappropriate, it frequently is. This note discusses DES security\n implications in detail, so that designers and implementers have all\n the information they need to make judicious decisions regarding its\n use.\n\nKelly Informational [Page 1]\n\f\nRFC 4772 DES Security Implications December 2006 4772 algorithm encryption key risk subject trust nested-reference unchanged"},{"id":"IETF RFC 478","type":"specification","body":"IETF","designation":"RFC 478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc478.txt","https://www.rfc-editor.org/rfc/rfc478.pdf"],"folder":"IETF/RFC-478","files":{"txt":{"path":"standards/IETF/RFC-478/RFC-478.txt","sha256":"8f11ccf8c69e78eb5ebda53376a2d7a92664fff01eef9a5d7de543f7374bed1e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group B. Bressler\nRequest for Comments: 478 B. Thomas\nNIC: 14947 BBN\n 26 March 1973\n\n FTP Server-Server Interaction-II\n\n At the recent FTP meeting at BBN in Cambridge, one of the topics\n discussed was that of server-server interaction. In a typical\n situation a user (A) conversing with two servers (B,C) is interested\n in retrieving a file from one site (B) and sending it to the other\n (C).\n\n +------+\n | USER |\n | A |\n /+------+\\\n control control\n / \\\n +------+ +------+\n |SERVER| DATA |SERVER|\n | B |----------->| C |\n +------+ +------+\n\n The consensus of the meeting was that mechanisms were necessary to\n make B and C aware of each other and to allow a data connection to be\n established without forcing each other to queue RFCs for local\n sockets before they exist.\n\n The proposed solution to this problem was a command called PASSIVE\n (PASV?). The following is our conclusion ","scope_keywords":["478"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 478 Network Working Group B. Bressler\nRequest for Comments: 478 B. Thomas\nNIC: 14947 BBN\n 26 March 1973\n\n FTP Server-Server Interaction-II\n\n At the recent FTP meeting at BBN in Cambridge, one of the topics\n discussed was that of server-server interaction. In a typical\n situation a user (A) conversing with two servers (B,C) is interested\n in retrieving a file from one site (B) and sending it to the other\n (C).\n\n +------+\n | USER |\n | A |\n /+------+\\\n control control\n / \\\n +------+ +------+\n |SERVER| DATA |SERVER|\n | B |----------->| C |\n +------+ +------+\n\n The consensus of the meeting was that mechanisms were necessary to\n make B and C aware of each other and to allow a data connection to be\n established without forcing each other to queue RFCs for local\n sockets before they exist.\n\n The proposed solution to this problem was a command called PASSIVE\n (PASV?). The following is our conclusion  478 nested-reference unchanged"},{"id":"IETF RFC 4788","type":"specification","body":"IETF","designation":"RFC 4788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4788.txt","https://www.rfc-editor.org/rfc/rfc4788.pdf"],"folder":"IETF/RFC-4788","files":{"txt":{"path":"standards/IETF/RFC-4788/RFC-4788.txt","sha256":"8003b37fcb72cab1c9444e21cf90f3bde05b04681499413becfeb7fa8661e3a9"}},"tags":["nested-reference","unchanged"],"summary":"This document updates the Enhanced Variable Rate Codec (EVRC) RTP\n payload formats defined in RFC 3558 with several enhancements and\n extensions. In particular, it defines support for the header-free\n and interleaved/bundled packet formats for the EVRC-B codec, a new\n compact bundled format for the EVRC and EVRC-B codecs, as well as\n discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded\n speech transported via RTP. Voice over IP (VoIP) applications\n operating over low bandwidth dial-up and wireless networks require\n such enhancements for efficient use of the bandwidth.\n\nXie & Kapoor Standards Track [Page 1]\n\f\nRFC 4788 EVRC RTP Format Enhancements January 2007","scope_keywords":["4788","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5188","folder":"IETF/RFC-5188","source":"IETF/RFC-5188/RFC-5188.txt","version":null}],"search_text":"IETF RFC 4788 This document updates the Enhanced Variable Rate Codec (EVRC) RTP\n payload formats defined in RFC 3558 with several enhancements and\n extensions. In particular, it defines support for the header-free\n and interleaved/bundled packet formats for the EVRC-B codec, a new\n compact bundled format for the EVRC and EVRC-B codecs, as well as\n discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded\n speech transported via RTP. Voice over IP (VoIP) applications\n operating over low bandwidth dial-up and wireless networks require\n such enhancements for efficient use of the bandwidth.\n\nXie & Kapoor Standards Track [Page 1]\n\f\nRFC 4788 EVRC RTP Format Enhancements January 2007 4788 trust nested-reference unchanged"},{"id":"IETF RFC 479","type":"specification","body":"IETF","designation":"RFC 479","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc479.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc479.txt","https://www.rfc-editor.org/rfc/rfc479.pdf"],"folder":"IETF/RFC-479","files":{"txt":{"path":"standards/IETF/RFC-479/RFC-479.txt","sha256":"d5c82b6022469ae1aa2fff05f1c982f8b8adce8ee9c39ce47d5e3e07dc88b99c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group James E. White (JEW)\nRequest for Comments: 479 SRI-ARC\nNIC: 14948 March 8, 1973\n\n Use of FTP by the NIC Journal\n\n At the Network Mail Meeting (see -- 14317,) the NIC outlined it's\n requirements for implementing FTP Journal delivery and submission.\n\n It had always been our thinking that those two services should rely\n upon the File Transfer Protocol's MLFL command for their\n implementation.\n\n Prior to the meeting, we had envisioned that, in the case of\n submission, for example, the user would embed what parameters the NIC\n required (e.g., an indication that this piece of mail was to be\n journalized, a list of NIC idents, etc.) in the USERNAME field of the\n MLFL command, in a way that was transparent to his FTP user process,\n and that SRI-ARC's FTP server process would parse the 'user name' for\n the parameters and internally invoke the Journal System with them and\n th","scope_keywords":["479","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 479 Network Working Group James E. White (JEW)\nRequest for Comments: 479 SRI-ARC\nNIC: 14948 March 8, 1973\n\n Use of FTP by the NIC Journal\n\n At the Network Mail Meeting (see -- 14317,) the NIC outlined it's\n requirements for implementing FTP Journal delivery and submission.\n\n It had always been our thinking that those two services should rely\n upon the File Transfer Protocol's MLFL command for their\n implementation.\n\n Prior to the meeting, we had envisioned that, in the case of\n submission, for example, the user would embed what parameters the NIC\n required (e.g., an indication that this piece of mail was to be\n journalized, a list of NIC idents, etc.) in the USERNAME field of the\n MLFL command, in a way that was transparent to his FTP user process,\n and that SRI-ARC's FTP server process would parse the 'user name' for\n the parameters and internally invoke the Journal System with them and\n th 479 delivery nested-reference unchanged"},{"id":"IETF RFC 480","type":"specification","body":"IETF","designation":"RFC 480","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc480.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc480.txt","https://www.rfc-editor.org/rfc/rfc480.pdf"],"folder":"IETF/RFC-480","files":{"txt":{"path":"standards/IETF/RFC-480/RFC-480.txt","sha256":"60ec69ea100eb7c7440dd467c18338c888198b87f17e96c53aabb5b6635626d4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group James E. White\nRFC #480 SRI-ARC\nNIC #14949 8 March 73\n\n Host-Dependent FTP Parameters\n\nThis memo is in response to (and support of) one of the points raised by\nBob Braden (RTB) of UCLA-CCN in RFC #430, \"COMMENTS ON FILE TRANSFER\nPROTOCOL\" (see -- 13299,), namely that raised in Section D., \"Site-\nDependent FTP Parameters\".\n\nThe NIC has been confronted with similar problems (and tentatively\ndecided upon similar solutions) in designing mechanisms which would\nenable a user to use FTP to retrieve from the NIC, in sequential form, a\nVIEW of some portion for an NLS tree-structured file.\n\nTo be done without modification to FTP, this task requires the user to\ncommunicate information -- a filename, a statement address, viewspecs,\nand the name of a conversion algorithm -- to SRI-ARC's server FTP\nprocess in a manner that is transparent to the user's user FTP process.\n\nWe curren","scope_keywords":["480","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 480 Network Working Group James E. White\nRFC #480 SRI-ARC\nNIC #14949 8 March 73\n\n Host-Dependent FTP Parameters\n\nThis memo is in response to (and support of) one of the points raised by\nBob Braden (RTB) of UCLA-CCN in RFC #430, \"COMMENTS ON FILE TRANSFER\nPROTOCOL\" (see -- 13299,), namely that raised in Section D., \"Site-\nDependent FTP Parameters\".\n\nThe NIC has been confronted with similar problems (and tentatively\ndecided upon similar solutions) in designing mechanisms which would\nenable a user to use FTP to retrieve from the NIC, in sequential form, a\nVIEW of some portion for an NLS tree-structured file.\n\nTo be done without modification to FTP, this task requires the user to\ncommunicate information -- a filename, a statement address, viewspecs,\nand the name of a conversion algorithm -- to SRI-ARC's server FTP\nprocess in a manner that is transparent to the user's user FTP process.\n\nWe curren 480 algorithm path nested-reference unchanged"},{"id":"IETF RFC 4801","type":"specification","body":"IETF","designation":"RFC 4801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4801.txt","https://www.rfc-editor.org/rfc/rfc4801.pdf"],"folder":"IETF/RFC-4801","files":{"txt":{"path":"standards/IETF/RFC-4801/RFC-4801.txt","sha256":"0eef50dcb871db3a20ebd3975751868a0d42cf1d9512bca1c058fbdc6b45423e"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Management Information Base (MIB) module that\n contains textual conventions (TCs) to represent commonly used\n Generalized Multiprotocol Label Switching (GMPLS) management\n information. The intent is that these textual conventions will be\n imported and used in GMPLS-related MIB modules that would otherwise\n define their own representations.","scope_keywords":["4801","key","management","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4803","folder":"IETF/RFC-4803","source":"IETF/RFC-4803/RFC-4803.txt","version":null}],"search_text":"IETF RFC 4801 This document defines a Management Information Base (MIB) module that\n contains textual conventions (TCs) to represent commonly used\n Generalized Multiprotocol Label Switching (GMPLS) management\n information. The intent is that these textual conventions will be\n imported and used in GMPLS-related MIB modules that would otherwise\n define their own representations. 4801 key management presentation trust nested-reference unchanged"},{"id":"IETF RFC 4816","type":"specification","body":"IETF","designation":"RFC 4816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4816.txt","https://www.rfc-editor.org/rfc/rfc4816.pdf"],"folder":"IETF/RFC-4816","files":{"txt":{"path":"standards/IETF/RFC-4816/RFC-4816.txt","sha256":"31a7742cde3e0dda45840af12a43026d3a159667e92af215fd89f6bda074436c"}},"tags":["nested-reference","unchanged"],"summary":"The document describes a transparent cell transport service that\n makes use of the \"N-to-one\" cell relay mode for Pseudowire Emulation\n Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell\n encapsulation.\n\n1. Introduction\n\n This transparent cell transport service allows migration of ATM\n services to a PSN without having to provision the ATM subscriber or\n customer edge (CE) devices. The ATM CEs will view the ATM\n transparent cell transport service as if they were directly connected\n via a Time Division Multiplexer (TDM) leased line. This service is\n most likely to be used as an internal function in an ATM service\n provider's network as a way to connect existing ATM switches via a\n higher-speed PSN, or to provide ATM \"backhaul\" services for remote\n access to existing ATM networks.\n\nMalis, et al. Standards Track [Page 1]\n\f\nRFC 4816 PWE3 ATM Transparent Cell Transport Service February ","scope_keywords":["4816","key","management","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5960","folder":"IETF/RFC-5960","source":"IETF/RFC-5960/RFC-5960.txt","version":null}],"search_text":"IETF RFC 4816 The document describes a transparent cell transport service that\n makes use of the \"N-to-one\" cell relay mode for Pseudowire Emulation\n Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell\n encapsulation.\n\n1. Introduction\n\n This transparent cell transport service allows migration of ATM\n services to a PSN without having to provision the ATM subscriber or\n customer edge (CE) devices. The ATM CEs will view the ATM\n transparent cell transport service as if they were directly connected\n via a Time Division Multiplexer (TDM) leased line. This service is\n most likely to be used as an internal function in an ATM service\n provider's network as a way to connect existing ATM switches via a\n higher-speed PSN, or to provide ATM \"backhaul\" services for remote\n access to existing ATM networks.\n\nMalis, et al. Standards Track [Page 1]\n\f\nRFC 4816 PWE3 ATM Transparent Cell Transport Service February  4816 key management path trust nested-reference unchanged"},{"id":"IETF RFC 7990","type":"specification","body":"IETF","designation":"RFC 7990","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7990.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7990.txt","https://www.rfc-editor.org/rfc/rfc7990.pdf"],"folder":"IETF/RFC-7990","files":{"txt":{"path":"standards/IETF/RFC-7990/RFC-7990.txt","sha256":"90e8f1857328e25878018e0268acc22fe5e4ebe245e4611fd68bb617d1f2813b"}},"tags":["nested-reference","unchanged"],"summary":"In order to improve the readability of RFCs while supporting their\n archivability, the canonical format of the RFC Series will be\n transitioning from plain-text ASCII to XML using the xml2rfc version\n 3 vocabulary; different publication formats will be rendered from\n that base document. With these changes comes an increase in\n complexity for authors, consumers, and the publisher of RFCs. This\n document serves as the framework that provides the problem statement,\n lays out a road map of the documents that capture the specific\n requirements, and describes the transition plan.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the cons","scope_keywords":["7990","http","key","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7993","folder":"IETF/RFC-7993","source":"IETF/RFC-7993/RFC-7993.txt","version":null}],"search_text":"IETF RFC 7990 In order to improve the readability of RFCs while supporting their\n archivability, the canonical format of the RFC Series will be\n transitioning from plain-text ASCII to XML using the xml2rfc version\n 3 vocabulary; different publication formats will be rendered from\n that base document. With these changes comes an increase in\n complexity for authors, consumers, and the publisher of RFCs. This\n document serves as the framework that provides the problem statement,\n lays out a road map of the documents that capture the specific\n requirements, and describes the transition plan.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the cons 7990 http key license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 487","type":"specification","body":"IETF","designation":"RFC 487","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc487.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc487.txt","https://www.rfc-editor.org/rfc/rfc487.pdf"],"folder":"IETF/RFC-487","files":{"txt":{"path":"standards/IETF/RFC-487/RFC-487.txt","sha256":"a0d1de4ea26a402fe19c9f2c2034c24785b13131104dffdfb1797e0f1e0cd89f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bob Bressler\nRequest for Comments #487 BBN\nNIC #15065 6 April 1973\n\n Free File Transfer\n\n In the past several months, many people have commented to me about\ntheir difficulty in transferring files. The hang up appears to be with\nsystems that have some flavor of security, but on which the user has no\naccess privileges. Specifically, the FTP server demands a user and\npassword before it will grant any system access. The loophole which\npeople have been using is the MAIL FILE facility, which is both limited\nin scope and intended for other purposes.\n\n A frequently used model for file protection is to define three\nlevels of user access: 1) only the user himself; 2) all users in a\ngroup; 3) everyone. Up until now, \"everyone\" has meant anyone already\ngranted logon privileges. A new class is, perhaps, needed to cover\neveryone, exclusive of whether or not they are logged on.\n\n ","scope_keywords":["487"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 501","folder":"IETF/RFC-501","source":"IETF/RFC-501/RFC-501.txt","version":null},{"body":"IETF","designation":"RFC 505","folder":"IETF/RFC-505","source":"IETF/RFC-505/RFC-505.txt","version":null}],"search_text":"IETF RFC 487 Network Working Group Bob Bressler\nRequest for Comments #487 BBN\nNIC #15065 6 April 1973\n\n Free File Transfer\n\n In the past several months, many people have commented to me about\ntheir difficulty in transferring files. The hang up appears to be with\nsystems that have some flavor of security, but on which the user has no\naccess privileges. Specifically, the FTP server demands a user and\npassword before it will grant any system access. The loophole which\npeople have been using is the MAIL FILE facility, which is both limited\nin scope and intended for other purposes.\n\n A frequently used model for file protection is to define three\nlevels of user access: 1) only the user himself; 2) all users in a\ngroup; 3) everyone. Up until now, \"everyone\" has meant anyone already\ngranted logon privileges. A new class is, perhaps, needed to cover\neveryone, exclusive of whether or not they are logged on.\n\n  487 nested-reference unchanged"},{"id":"IETF RFC 505","type":"specification","body":"IETF","designation":"RFC 505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc505.txt","https://www.rfc-editor.org/rfc/rfc505.pdf"],"folder":"IETF/RFC-505","files":{"txt":{"path":"standards/IETF/RFC-505/RFC-505.txt","sha256":"20731224af8ce152db63f22f24544c2378f1c4fc85122333c98c576b39065446"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. A. Padlipsky\nRequest for Comments: 505 MIT-Multics\nNIC: 16156 25 June 1973\n\n Two Solutions to a File Transfer Access Problem\n\n In RFC #87, Bob Bressler raises the issue of how one can use the File\n Transfer Protocol to send a file to a user on another system without\n knowing that user's password. In RFC 501, Kan Pogran points out\n certain objections to Bressler's solution of having a \"daemon\"\n process do the job -- in particular, the fact that it would require\n an interpretive access control mechanism in the daemon different from\n most system's normal access control mechanisms. Because Ken felt\n that it would be too much of a digression in RFC 501 for him to cover\n the following points fully, I decided it might be of interest to deal\n with them separately: There are at least two solutions to the problem\n Bob raised in RFC 487 -- in regard to \"my\" sending \"him\" a ","scope_keywords":["505","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 949","folder":"IETF/RFC-949","source":"IETF/RFC-949/RFC-949.txt","version":null}],"search_text":"IETF RFC 505 Network Working Group M. A. Padlipsky\nRequest for Comments: 505 MIT-Multics\nNIC: 16156 25 June 1973\n\n Two Solutions to a File Transfer Access Problem\n\n In RFC #87, Bob Bressler raises the issue of how one can use the File\n Transfer Protocol to send a file to a user on another system without\n knowing that user's password. In RFC 501, Kan Pogran points out\n certain objections to Bressler's solution of having a \"daemon\"\n process do the job -- in particular, the fact that it would require\n an interpretive access control mechanism in the daemon different from\n most system's normal access control mechanisms. Because Ken felt\n that it would be too much of a digression in RFC 501 for him to cover\n the following points fully, I decided it might be of interest to deal\n with them separately: There are at least two solutions to the problem\n Bob raised in RFC 487 -- in regard to \"my\" sending \"him\" a  505 path subject nested-reference unchanged"},{"id":"IETF RFC 549","type":"specification","body":"IETF","designation":"RFC 549","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc549.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc549.txt","https://www.rfc-editor.org/rfc/rfc549.pdf"],"folder":"IETF/RFC-549","files":{"txt":{"path":"standards/IETF/RFC-549/RFC-549.txt","sha256":"77c81331b12b21b9147155d41cc6d6f19341ff1203d3f58248b0e7bb675a6648"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Anonymous\nRequest for Comments: 549 Center for Advanced Computation, U of Ill\nNIC: 17795 15-17 July 1973\n\n MINUTES OF NETWORK GRAPHICS GROUP MEETING\n\nSunday evening, 15 July\n\n The meeting came to order around 1930, Jim Michener presiding. After\n introductions, an agenda was constructed for the rest of the meeting.\n\n Elaine Thomas distributed copies of an Alternative Network Graphics\n Protocol for attendees to read overnight prior to discussion.\n\n Because some individuals were absent who had definitely indicated\n that they were coming Monday morning, the meeting was adjourned at\n 2030 after deciding to meet at 0930 the next morning.\n\nMonday Morning/Afternoon, 16 July\n\n The meeting was called to order at 0930\n\n Jim Michener distributed an outline of a paper describing desirable\n facilities for the use of two dimensional input devices with a\n hierarchically structured ","scope_keywords":["549"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 549 Network Working Group Anonymous\nRequest for Comments: 549 Center for Advanced Computation, U of Ill\nNIC: 17795 15-17 July 1973\n\n MINUTES OF NETWORK GRAPHICS GROUP MEETING\n\nSunday evening, 15 July\n\n The meeting came to order around 1930, Jim Michener presiding. After\n introductions, an agenda was constructed for the rest of the meeting.\n\n Elaine Thomas distributed copies of an Alternative Network Graphics\n Protocol for attendees to read overnight prior to discussion.\n\n Because some individuals were absent who had definitely indicated\n that they were coming Monday morning, the meeting was adjourned at\n 2030 after deciding to meet at 0930 the next morning.\n\nMonday Morning/Afternoon, 16 July\n\n The meeting was called to order at 0930\n\n Jim Michener distributed an outline of a paper describing desirable\n facilities for the use of two dimensional input devices with a\n hierarchically structured  549 nested-reference unchanged"},{"id":"IETF RFC 553","type":"specification","body":"IETF","designation":"RFC 553","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc553.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc553.txt","https://www.rfc-editor.org/rfc/rfc553.pdf"],"folder":"IETF/RFC-553","files":{"txt":{"path":"standards/IETF/RFC-553/RFC-553.txt","sha256":"1b857e30122d8e6b35071a019aecf09f3a66133afcb59aead89b0ad646717390"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group C. Irby\nRequest for Comments: 553 K. Victor\nNIC: 17810 SRI-ARC\n 14 July 1973\n\n Draft design for a text/graphics protocol\n\nDRAFT DESIGN FOR A TEXT/GRAPHICS PROTOCOL\n\n This proposal should be seen as a synthesis of existing ideas rather\n than an attempt to put forth new ones. It is based on work by the\n NGG, Elaine Thomas, Peter Deutsch, Charles Irby, Ken Victor, Bill\n Duvall, Bob Sproull, and others at ARC, PARC, and BBN.\n\n We are concerned about the lack of text-handling capabilities of the\n protocol suggested in RFC 493. Also, we feel that the protocol will\n have a significant influence on the interface provided to writers of\n future graphics application programs, and consequently that such\n things as \"beam twiddling\" should not be part of the protocol.\n\n Things of this nature address the problem at too low a level for a\n facility which is intended to service the n","scope_keywords":["553"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 549","folder":"IETF/RFC-549","source":"IETF/RFC-549/RFC-549.txt","version":null}],"search_text":"IETF RFC 553 Network Working Group C. Irby\nRequest for Comments: 553 K. Victor\nNIC: 17810 SRI-ARC\n 14 July 1973\n\n Draft design for a text/graphics protocol\n\nDRAFT DESIGN FOR A TEXT/GRAPHICS PROTOCOL\n\n This proposal should be seen as a synthesis of existing ideas rather\n than an attempt to put forth new ones. It is based on work by the\n NGG, Elaine Thomas, Peter Deutsch, Charles Irby, Ken Victor, Bill\n Duvall, Bob Sproull, and others at ARC, PARC, and BBN.\n\n We are concerned about the lack of text-handling capabilities of the\n protocol suggested in RFC 493. Also, we feel that the protocol will\n have a significant influence on the interface provided to writers of\n future graphics application programs, and consequently that such\n things as \"beam twiddling\" should not be part of the protocol.\n\n Things of this nature address the problem at too low a level for a\n facility which is intended to service the n 553 nested-reference unchanged"},{"id":"IETF RFC 8165","type":"specification","body":"IETF","designation":"RFC 8165","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8165.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8165.txt","https://www.rfc-editor.org/rfc/rfc8165.pdf"],"folder":"IETF/RFC-8165","files":{"txt":{"path":"standards/IETF/RFC-8165/RFC-8165.txt","sha256":"bae0feffc71ed474c82e514817f353bf4efee44b525a8495c18a5d691d8ecc1f"}},"tags":["nested-reference","unchanged"],"summary":"The IAB published RFC 7624 in response to several revelations of\n pervasive attacks on Internet communications. This document\n considers the implications of protocol designs that associate\n metadata with encrypted flows. In particular, it asserts that\n designs that share metadata only by explicit actions at the host are\n preferable to designs in which middleboxes insert metadata.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information ab","scope_keywords":["8165","encryption","http","license","path","policies","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8300","folder":"IETF/RFC-8300","source":"IETF/RFC-8300/RFC-8300.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 8165 The IAB published RFC 7624 in response to several revelations of\n pervasive attacks on Internet communications. This document\n considers the implications of protocol designs that associate\n metadata with encrypted flows. In particular, it asserts that\n designs that share metadata only by explicit actions at the host are\n preferable to designs in which middleboxes insert metadata.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information ab 8165 encryption http license path policies risk subject trust nested-reference unchanged"},{"id":"IETF RFC 9397","type":"specification","body":"IETF","designation":"RFC 9397","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9397.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9397.txt","https://www.rfc-editor.org/rfc/rfc9397.pdf"],"folder":"IETF/RFC-9397","files":{"pdf":{"path":"standards/IETF/RFC-9397/RFC-9397.pdf","sha256":"cc8ed6d61530fb4b7a0f76b08cd7f7e2961dd4ae75a3c9b5b219e0be7fb71377"},"txt":{"path":"standards/IETF/RFC-9397/RFC-9397.txt","sha256":"70c6f39a9cd19af59591d1ddd14c1e5d85bb56c8e8dbe8f2a68c17f9f235d692"}},"tags":["nested-reference","unchanged"],"summary":"A Trusted Execution Environment (TEE) is an environment that enforces\n the following: any code within the environment cannot be tampered\n with, and any data used by such code cannot be read or tampered with\n by any code outside the environment. This architecture document\n discusses the motivation for designing and standardizing a protocol\n for managing the lifecycle of Trusted Applications running inside\n such a TEE.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Se","scope_keywords":["9397","algorithm","attestation","authentication","certificate","delivery","http","https","key","keys","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9781","folder":"IETF/RFC-9781","source":"IETF/RFC-9781/RFC-9781.txt","version":null}],"search_text":"IETF RFC 9397 A Trusted Execution Environment (TEE) is an environment that enforces\n the following: any code within the environment cannot be tampered\n with, and any data used by such code cannot be read or tampered with\n by any code outside the environment. This architecture document\n discusses the motivation for designing and standardizing a protocol\n for managing the lifecycle of Trusted Applications running inside\n such a TEE.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level of Internet\n Standard; see Se 9397 algorithm attestation authentication certificate delivery http https key keys license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 495","type":"specification","body":"IETF","designation":"RFC 495","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc495.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc495.txt","https://www.rfc-editor.org/rfc/rfc495.pdf"],"folder":"IETF/RFC-495","files":{"txt":{"path":"standards/IETF/RFC-495/RFC-495.txt","sha256":"8ddd60acd7a1841a3849d2be0d20333615380b20a82504e092aaef326d93df39"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 495 BBN-NET\nNIC #15371 1 May 1973\nCategories: TELNET, Protocols\nReferences: RFCs 318, 435; NIC 7104\n\n TELNET Protocol Specification\n\nFollowing much discussion of TELNET via the RFC series, an open meeting\nwas held at UCLA on 5 March to formulate a new specification for the\nTELNET Protocol. Two attached documents (TELNET Protocol Specification,\nNIC #15372, and TELNET Option Specifications, NIC #15373) report the\nresults of that meeting, which was attended by: Alex McKenzie, BBN-NET,\nco-chairman; Jon Postel, UCLA-NMC, co-chairman; Bob Braden, UCLA-CCN;\nVint Cerf, Stanford University; Bernie Cosell, BBN-NET; Dave Crocker,\nUCLA-NMC; Steve Crocker, ARPA; John Davidson, Univ. of Hawaii; Gary\nGrossman, Univ. of Illinois; Bob Merryman, UCSD; Lou Nelson, UCLA-NMC;\nMike Padlipsky, MIT-MULTICS: Milt Reese, FNW; Bob Thomas, BBN-TENEX;\nSteve Wol","scope_keywords":["495","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 562","folder":"IETF/RFC-562","source":"IETF/RFC-562/RFC-562.txt","version":null}],"search_text":"IETF RFC 495 Network Working Group A. McKenzie\nRequest for Comments: 495 BBN-NET\nNIC #15371 1 May 1973\nCategories: TELNET, Protocols\nReferences: RFCs 318, 435; NIC 7104\n\n TELNET Protocol Specification\n\nFollowing much discussion of TELNET via the RFC series, an open meeting\nwas held at UCLA on 5 March to formulate a new specification for the\nTELNET Protocol. Two attached documents (TELNET Protocol Specification,\nNIC #15372, and TELNET Option Specifications, NIC #15373) report the\nresults of that meeting, which was attended by: Alex McKenzie, BBN-NET,\nco-chairman; Jon Postel, UCLA-NMC, co-chairman; Bob Braden, UCLA-CCN;\nVint Cerf, Stanford University; Bernie Cosell, BBN-NET; Dave Crocker,\nUCLA-NMC; Steve Crocker, ARPA; John Davidson, Univ. of Hawaii; Gary\nGrossman, Univ. of Illinois; Bob Merryman, UCSD; Lou Nelson, UCLA-NMC;\nMike Padlipsky, MIT-MULTICS: Milt Reese, FNW; Bob Thomas, BBN-TENEX;\nSteve Wol 495 key subject nested-reference unchanged"},{"id":"IETF RFC 562","type":"specification","body":"IETF","designation":"RFC 562","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc562.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc562.txt","https://www.rfc-editor.org/rfc/rfc562.pdf"],"folder":"IETF/RFC-562","files":{"pdf":{"path":"standards/IETF/RFC-562/RFC-562.pdf","sha256":"dbe94b0c5b8acdf543a987735a56807c752d6c6708873af14036d32e7a14a816"},"txt":{"path":"standards/IETF/RFC-562/RFC-562.txt","sha256":"ed298a9e4b9668b514d6994525bc24240bd753f659c1092ebf7094f38b1dc819"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 562 BBN-TENEX\nNIC: 18638 28 August 1973\nUpdates: RFC 495\nReferences: RFCs 513, 529\n\n Modifications to the TELNET Specification\n\n Almost four months have passed since the new TELNET Protocol\n specification was published. Since then, only two RFCs have been\n issued suggesting modifications, and the most recent of these was\n distributed two months ago. Further, the date from the old TELNET to\n the new TELNET (1 January 1974) is only four months away. It\n therefore seems appropriate to officially modify the specification to\n account for the suggested modifications, and to declare a moratorium\n on the incorporation of additional suggestions until after the\n switchover. (Of course, no moratorium on the specification of\n additional options is required.)\n\n The two attached documents represent the revised TELNET Protocol\n specifications; the","scope_keywords":["562"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 580","folder":"IETF/RFC-580","source":"IETF/RFC-580/RFC-580.txt","version":null}],"search_text":"IETF RFC 562 Network Working Group A. McKenzie\nRequest for Comments: 562 BBN-TENEX\nNIC: 18638 28 August 1973\nUpdates: RFC 495\nReferences: RFCs 513, 529\n\n Modifications to the TELNET Specification\n\n Almost four months have passed since the new TELNET Protocol\n specification was published. Since then, only two RFCs have been\n issued suggesting modifications, and the most recent of these was\n distributed two months ago. Further, the date from the old TELNET to\n the new TELNET (1 January 1974) is only four months away. It\n therefore seems appropriate to officially modify the specification to\n account for the suggested modifications, and to declare a moratorium\n on the incorporation of additional suggestions until after the\n switchover. (Of course, no moratorium on the specification of\n additional options is required.)\n\n The two attached documents represent the revised TELNET Protocol\n specifications; the 562 nested-reference unchanged"},{"id":"IETF RFC 4950","type":"specification","body":"IETF","designation":"RFC 4950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4950.txt","https://www.rfc-editor.org/rfc/rfc4950.pdf"],"folder":"IETF/RFC-4950","files":{"txt":{"path":"standards/IETF/RFC-4950/RFC-4950.txt","sha256":"536c3e4c4df80b25a9daaea846d6940388a2134d68b59de51baa9e4ade388949"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines an extension object that can be appended to\n selected multi-part ICMP messages. This extension permits Label\n Switching Routers to append MPLS information to ICMP messages, and\n has already been widely deployed.","scope_keywords":["4950","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 4950 This memo defines an extension object that can be appended to\n selected multi-part ICMP messages. This extension permits Label\n Switching Routers to append MPLS information to ICMP messages, and\n has already been widely deployed. 4950 key trust nested-reference unchanged"},{"id":"IETF RFC 4969","type":"specification","body":"IETF","designation":"RFC 4969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4969.txt","https://www.rfc-editor.org/rfc/rfc4969.pdf"],"folder":"IETF/RFC-4969","files":{"txt":{"path":"standards/IETF/RFC-4969/RFC-4969.txt","sha256":"8b13a00ef6f3a11ffc56b2f05ec8af761cd3099c6d9aff6a0d32a1bc581391f8"}},"tags":["nested-reference","unchanged"],"summary":"This memo registers the Enumservice \"vCard\" using the URI schemes\n \"http\" and \"https\". This Enumservice is to be used to refer from an\n ENUM domain name to a vCard instance describing the user of the\n respective E.164 number.\n\n Information gathered from those vCards could be used before, during,\n or after inbound or outbound communication takes place. For example,\n a callee might be presented with the name and association of the\n caller before picking up the call.","scope_keywords":["4969","authentication","authorization","http","https","key","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4969 This memo registers the Enumservice \"vCard\" using the URI schemes\n \"http\" and \"https\". This Enumservice is to be used to refer from an\n ENUM domain name to a vCard instance describing the user of the\n respective E.164 number.\n\n Information gathered from those vCards could be used before, during,\n or after inbound or outbound communication takes place. For example,\n a callee might be presented with the name and association of the\n caller before picking up the call. 4969 authentication authorization http https key trust nested-reference unchanged"},{"id":"IETF RFC 497","type":"specification","body":"IETF","designation":"RFC 497","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc497.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc497.txt","https://www.rfc-editor.org/rfc/rfc497.pdf"],"folder":"IETF/RFC-497","files":{"pdf":{"path":"standards/IETF/RFC-497/RFC-497.pdf","sha256":"d6e0c606cfde9fe7dd7772d6a2bf0031748da46710b03c67df7fc5ade4fe09c8"},"txt":{"path":"standards/IETF/RFC-497/RFC-497.txt","sha256":"34afa651f3c53f349f03e50c0d84c7b45e6b5425e7dca0e025b1fc0f3c889b32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 497 BBN-NET\nNIC: 15651 10 April 1973\nUpdates: RFC #482\n\n Traffic Statistics (March 1973)\n\nAttached are the Host traffic statistics for the month of\nMarch 1973.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n MARCH 1973\n\n MISSING DATA FOR 16, 20\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 188383 55261 243644\nUCLA HOST 1 1406528 105973 1512501\n -------- -------- --------\n 1594911 161234 1756145 54997 29\n\nSRI HOST 0 4112207 116788 4228995\nSRI HOST 1 150388 9932 160320\n -------- -------- --------\n 4262595 126720 4389315 146986 29\n\nUCSB HOST 0 1151686 860021 2011707\nUCSB HOST 1 558 2570 3128\n -------- -------- --------\n 1152244 862591 2014835 39733 29\n\nUTAH HOST 0 600680 82655 683335 20713 29\n\nBBN HOST 0 17 24341 24358\nBBN HOST 1 5003328 855463 5858791\nBBN HOST 2 125394 594853 720247\nBBN HOST 3 142697 21956 1646","scope_keywords":["497"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 497 Network Working Group A. McKenzie\nRequest for Comments: 497 BBN-NET\nNIC: 15651 10 April 1973\nUpdates: RFC #482\n\n Traffic Statistics (March 1973)\n\nAttached are the Host traffic statistics for the month of\nMarch 1973.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n MARCH 1973\n\n MISSING DATA FOR 16, 20\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 188383 55261 243644\nUCLA HOST 1 1406528 105973 1512501\n -------- -------- --------\n 1594911 161234 1756145 54997 29\n\nSRI HOST 0 4112207 116788 4228995\nSRI HOST 1 150388 9932 160320\n -------- -------- --------\n 4262595 126720 4389315 146986 29\n\nUCSB HOST 0 1151686 860021 2011707\nUCSB HOST 1 558 2570 3128\n -------- -------- --------\n 1152244 862591 2014835 39733 29\n\nUTAH HOST 0 600680 82655 683335 20713 29\n\nBBN HOST 0 17 24341 24358\nBBN HOST 1 5003328 855463 5858791\nBBN HOST 2 125394 594853 720247\nBBN HOST 3 142697 21956 1646 497 nested-reference unchanged"},{"id":"IETF RFC 4979","type":"specification","body":"IETF","designation":"RFC 4979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc4979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc4979.txt","https://www.rfc-editor.org/rfc/rfc4979.pdf"],"folder":"IETF/RFC-4979","files":{"txt":{"path":"standards/IETF/RFC-4979/RFC-4979.txt","sha256":"e8407af0b3aaecb5ccf5dabd6379eb0852be09ceaace90a0ddaf6f03ebf2598c"}},"tags":["nested-reference","unchanged"],"summary":"This document requests IANA registration of an Enumservice for XMPP,\n the Extensible Messaging and Presence Protocol. This Enumservice\n specifically allows the use of 'xmpp' Uniform Resource Identifiers\n (URIs) in the context of E.164 Number Mapping (ENUM).","scope_keywords":["4979","key","presentation","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 4979 This document requests IANA registration of an Enumservice for XMPP,\n the Extensible Messaging and Presence Protocol. This Enumservice\n specifically allows the use of 'xmpp' Uniform Resource Identifiers\n (URIs) in the context of E.164 Number Mapping (ENUM). 4979 key presentation registered trust nested-reference unchanged"},{"id":"IETF RFC 5022","type":"specification","body":"IETF","designation":"RFC 5022","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5022.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5022.txt","https://www.rfc-editor.org/rfc/rfc5022.pdf"],"folder":"IETF/RFC-5022","files":{"txt":{"path":"standards/IETF/RFC-5022/RFC-5022.txt","sha256":"2a5e115d201301e0c2c8424076bdf914b49929172e4d1e282e62e5547ec17900"}},"tags":["nested-reference","unchanged"],"summary":"Media Server Control Markup Language (MSCML) is a markup language\n used in conjunction with SIP to provide advanced conferencing and\n interactive voice response (IVR) functions. MSCML presents an\n application-level control model, as opposed to device-level control\n models. One use of this protocol is for communications between a\n conference focus and mixer in the IETF SIP Conferencing Framework.\n\nVan Dyke, et al. Informational [Page 1]\n\f\nRFC 5022 MSCML September 2007","scope_keywords":["5022","attribute","attributes","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 5022 Media Server Control Markup Language (MSCML) is a markup language\n used in conjunction with SIP to provide advanced conferencing and\n interactive voice response (IVR) functions. MSCML presents an\n application-level control model, as opposed to device-level control\n models. One use of this protocol is for communications between a\n conference focus and mixer in the IETF SIP Conferencing Framework.\n\nVan Dyke, et al. Informational [Page 1]\n\f\nRFC 5022 MSCML September 2007 5022 attribute attributes key keys nested-reference unchanged"},{"id":"IETF RFC 5028","type":"specification","body":"IETF","designation":"RFC 5028","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5028.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5028.txt","https://www.rfc-editor.org/rfc/rfc5028.pdf"],"folder":"IETF/RFC-5028","files":{"txt":{"path":"standards/IETF/RFC-5028/RFC-5028.txt","sha256":"9d9ef14189723f62c7c1c3c4a09240ef1f5890ddb381ff62c4cf2bb049892e45"}},"tags":["nested-reference","unchanged"],"summary":"This document registers a Telephone Number Mapping (ENUM) service for\n Instant Messaging (IM). Specifically, this document focuses on\n provisioning 'im:' URIs (Uniform Resource Identifiers) in ENUM.\n\n1. Introduction\n\n ENUM (E.164 Number Mapping, RFC 3761 [1]) is a system that uses DNS\n (Domain Name Service, RFC 1034 [2]) to translate telephone numbers,\n such as '+12025550100', into URIs (Uniform Resource Identifiers, RFC\n 3986 [3]), such as 'im:user@example.com'. ENUM exists primarily to\n facilitate the interconnection of systems that rely on telephone\n numbers with those that use URIs to identify resources.\n\n Instant Messaging (IM) is a service defined in RFC 2778 [6] that\n allows users to send and receive typically short, often textual\n messages in near real-time. The IETF has defined a generic URI used\n to identify an IM service for a particular resource: the 'im:' URI\n scheme (define","scope_keywords":["5028","authentication","authorization","credential","credentials","delivery","license","policy","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 5028 This document registers a Telephone Number Mapping (ENUM) service for\n Instant Messaging (IM). Specifically, this document focuses on\n provisioning 'im:' URIs (Uniform Resource Identifiers) in ENUM.\n\n1. Introduction\n\n ENUM (E.164 Number Mapping, RFC 3761 [1]) is a system that uses DNS\n (Domain Name Service, RFC 1034 [2]) to translate telephone numbers,\n such as '+12025550100', into URIs (Uniform Resource Identifiers, RFC\n 3986 [3]), such as 'im:user@example.com'. ENUM exists primarily to\n facilitate the interconnection of systems that rely on telephone\n numbers with those that use URIs to identify resources.\n\n Instant Messaging (IM) is a service defined in RFC 2778 [6] that\n allows users to send and receive typically short, often textual\n messages in near real-time. The IETF has defined a generic URI used\n to identify an IM service for a particular resource: the 'im:' URI\n scheme (define 5028 authentication authorization credential credentials delivery license policy risk subject trust nested-reference unchanged"},{"id":"IETF RFC 949","type":"specification","body":"IETF","designation":"RFC 949","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc949.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc949.txt","https://www.rfc-editor.org/rfc/rfc949.pdf"],"folder":"IETF/RFC-949","files":{"txt":{"path":"standards/IETF/RFC-949/RFC-949.txt","sha256":"53607c2bb05e1f7db701e657c387e3ee06df942bbff84744b3840b135833aca2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mike Padlipsky\nRequest for Comments: 949 Mitre\nSemisupersedes RFC 505 July 1985\n\n FTP UNIQUE-NAMED STORE COMMAND\n\nSTATUS OF THIS MEMO\n\n This RFC proposes an extension to the File Transfer Protocol for the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nDISCUSSION\n\n There are various contexts in which it would be desirable to have an\n FTP command that had the effect of the present STOR but rather than\n requiring the sender to specify a file name instead caused the\n resultant file to have a unique name relative to the current\n directory. This would be useful for all sorts of \"pool\" directories;\n the directories that serve as queues for printer daemons come\n immediately to mind (so do fax and even cardpunch daemons' queues),\n although naturally the sort of printer queue that a local command h","scope_keywords":["949","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 949 Network Working Group Mike Padlipsky\nRequest for Comments: 949 Mitre\nSemisupersedes RFC 505 July 1985\n\n FTP UNIQUE-NAMED STORE COMMAND\n\nSTATUS OF THIS MEMO\n\n This RFC proposes an extension to the File Transfer Protocol for the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nDISCUSSION\n\n There are various contexts in which it would be desirable to have an\n FTP command that had the effect of the present STOR but rather than\n requiring the sender to specify a file name instead caused the\n resultant file to have a unique name relative to the current\n directory. This would be useful for all sorts of \"pool\" directories;\n the directories that serve as queues for printer daemons come\n immediately to mind (so do fax and even cardpunch daemons' queues),\n although naturally the sort of printer queue that a local command h 949 authentication nested-reference unchanged"},{"id":"IETF RFC 506","type":"specification","body":"IETF","designation":"RFC 506","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc506.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc506.txt","https://www.rfc-editor.org/rfc/rfc506.pdf"],"folder":"IETF/RFC-506","files":{"txt":{"path":"standards/IETF/RFC-506/RFC-506.txt","sha256":"ec26036ec3aaef313c6573643b3b5c715683b22be034dc84fe9a70d40f9d0cce"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M.A. Padlipsky\nRequest for Comments #506 MIT-Multics\nNIC #16157 6/26/73\n\n An FTP Command-Naming Problem\n\nIn using the File Transfer Protocol, I've noticed that the choice of\nnames for two crucial commands is faulty. The commands are STOR, which\ntell the Server to take a file in, and RETR, which tells the Server to\nsend a file out. The trouble is that telling the Server to \"retrieve\" a\nfile sounds like a desire for the file to be taken in by the Server\nrather than be sent out. For that matter, telling the Server to \"store\"\nthe file sounds like it could be either a command to send it out or a\ncommand to take it in. The names of the commands, then, are both\nconnotatively ambiguous and not very mnemonic if they are thought of as\ncommands to the Server. (If they're thought of as commands to the User\nHost, they make more sense -- but they're not commands to the Use\n(Host.","scope_keywords":["506"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 506 Network Working Group M.A. Padlipsky\nRequest for Comments #506 MIT-Multics\nNIC #16157 6/26/73\n\n An FTP Command-Naming Problem\n\nIn using the File Transfer Protocol, I've noticed that the choice of\nnames for two crucial commands is faulty. The commands are STOR, which\ntell the Server to take a file in, and RETR, which tells the Server to\nsend a file out. The trouble is that telling the Server to \"retrieve\" a\nfile sounds like a desire for the file to be taken in by the Server\nrather than be sent out. For that matter, telling the Server to \"store\"\nthe file sounds like it could be either a command to send it out or a\ncommand to take it in. The names of the commands, then, are both\nconnotatively ambiguous and not very mnemonic if they are thought of as\ncommands to the Server. (If they're thought of as commands to the User\nHost, they make more sense -- but they're not commands to the Use\n(Host. 506 nested-reference unchanged"},{"id":"IETF RFC 5067","type":"specification","body":"IETF","designation":"RFC 5067","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5067.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5067.txt","https://www.rfc-editor.org/rfc/rfc5067.pdf"],"folder":"IETF/RFC-5067","files":{"txt":{"path":"standards/IETF/RFC-5067/RFC-5067.txt","sha256":"11d0d53a34b4a701cf3e002bfcb9b6781fda7d29a1a8dce5485110c95644d56d"}},"tags":["nested-reference","unchanged"],"summary":"This document provides requirements for \"infrastructure\" or \"carrier\"\n ENUM (E.164 Number Mapping), defined as the use of RFC 3761\n technology to facilitate interconnection of networks for E.164 number\n addressed services, in particular but not restricted to VoIP (Voice\n over IP.)","scope_keywords":["5067","authentication","delivery","key","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 5067 This document provides requirements for \"infrastructure\" or \"carrier\"\n ENUM (E.164 Number Mapping), defined as the use of RFC 3761\n technology to facilitate interconnection of networks for E.164 number\n addressed services, in particular but not restricted to VoIP (Voice\n over IP.) 5067 authentication delivery key qualified subject nested-reference unchanged"},{"id":"IETF RFC 509","type":"specification","body":"IETF","designation":"RFC 509","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc509.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc509.txt","https://www.rfc-editor.org/rfc/rfc509.pdf"],"folder":"IETF/RFC-509","files":{"txt":{"path":"standards/IETF/RFC-509/RFC-509.txt","sha256":"9b523dfb0677a99412464e1ac9c93516049958f4a67d7c85014de414e4b7e108"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 509 BBN-NET\nNIC: 16294 7 May 1973\nUpdates: 497\n\n Traffic Statistics (April 1973)\n\nABSTRACT\n\n Attached are the Host traffic statistics for the month of April 1973.\n\n AAM/jm\n\n Attach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n APRIL 1973\n\n MISSING DATA FOR 1, 7\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 172982 77316 250298\n UCLA HOST 1 1218041 196398 1414439\n -------- ------- -------\n 1391023 273714 1664737 49679 28\n\n SRI HOST 0 4376148 50271 4426419\n SRI HOST 1 237661 30783 268444\n -------- ----- -------\n 4613809 81054 4694863 164779 28\n\n UCSB HOST 0 1147817 1276185 2424002\n UCSB HOST 1 33119 19596 52715\n ------- ------- -------\n 1180936 1295781 2476717 42176 28\n\n UTAH HOST 0 1038511 63866 1102377 37090 28\n\nMcKenzie [Page 1]\n\f\nRFC 509 Traffic Statistics (April 1973) 7 May 1973\n\n BBN HOST 0 24 28514 28","scope_keywords":["509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 509 Network Working Group A. McKenzie\nRequest for Comments: 509 BBN-NET\nNIC: 16294 7 May 1973\nUpdates: 497\n\n Traffic Statistics (April 1973)\n\nABSTRACT\n\n Attached are the Host traffic statistics for the month of April 1973.\n\n AAM/jm\n\n Attach.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n APRIL 1973\n\n MISSING DATA FOR 1, 7\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 172982 77316 250298\n UCLA HOST 1 1218041 196398 1414439\n -------- ------- -------\n 1391023 273714 1664737 49679 28\n\n SRI HOST 0 4376148 50271 4426419\n SRI HOST 1 237661 30783 268444\n -------- ----- -------\n 4613809 81054 4694863 164779 28\n\n UCSB HOST 0 1147817 1276185 2424002\n UCSB HOST 1 33119 19596 52715\n ------- ------- -------\n 1180936 1295781 2476717 42176 28\n\n UTAH HOST 0 1038511 63866 1102377 37090 28\n\nMcKenzie [Page 1]\n\f\nRFC 509 Traffic Statistics (April 1973) 7 May 1973\n\n BBN HOST 0 24 28514 28 509 nested-reference unchanged"},{"id":"IETF RFC 512","type":"specification","body":"IETF","designation":"RFC 512","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc512.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc512.txt","https://www.rfc-editor.org/rfc/rfc512.pdf"],"folder":"IETF/RFC-512","files":{"txt":{"path":"standards/IETF/RFC-512/RFC-512.txt","sha256":"23b5ac1a26f13197bffd386c8cc5b1b659697bff81151016d15f005ddf3cd5ee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Wayne Hathaway\nRFC # 512 AMES-67\nNIC # 16443 25 May 1973\n\n MORE ON LOST MESSAGE DETECTION\n\nI would like to second Edwin Meyer's (RFC #492) strong opposition to the\nproposals made in RFC #467 concerning solutions to the \"lost allocate\"\nand \"half-closed\" phenomena. In particular I support all of his\nprinciples concerning the \"half-closed\" phenomenon. I also agree that\nthe proposed \"lost allocate\" solution tends to mask the real problem of\nlost messages. I would, however, like to propose the following\nalternative scheme for recognizing lost messages.\n\nI propose that one of the two unused eight-bit bytes in the level 2\nmessage leader be designated the \"Sequence Control Byte\" (SCB). This\nSCB would be essentially a modulo 255 message count. Upon receipt of a\nmessage, the receiving NCP would compare the SCB in the previous the\nmessage with the expected SCB as computed from","scope_keywords":["512"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 534","folder":"IETF/RFC-534","source":"IETF/RFC-534/RFC-534.txt","version":null}],"search_text":"IETF RFC 512 Network Working Group Wayne Hathaway\nRFC # 512 AMES-67\nNIC # 16443 25 May 1973\n\n MORE ON LOST MESSAGE DETECTION\n\nI would like to second Edwin Meyer's (RFC #492) strong opposition to the\nproposals made in RFC #467 concerning solutions to the \"lost allocate\"\nand \"half-closed\" phenomena. In particular I support all of his\nprinciples concerning the \"half-closed\" phenomenon. I also agree that\nthe proposed \"lost allocate\" solution tends to mask the real problem of\nlost messages. I would, however, like to propose the following\nalternative scheme for recognizing lost messages.\n\nI propose that one of the two unused eight-bit bytes in the level 2\nmessage leader be designated the \"Sequence Control Byte\" (SCB). This\nSCB would be essentially a modulo 255 message count. Upon receipt of a\nmessage, the receiving NCP would compare the SCB in the previous the\nmessage with the expected SCB as computed from 512 nested-reference unchanged"},{"id":"IETF RFC 534","type":"specification","body":"IETF","designation":"RFC 534","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc534.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc534.txt","https://www.rfc-editor.org/rfc/rfc534.pdf"],"folder":"IETF/RFC-534","files":{"txt":{"path":"standards/IETF/RFC-534/RFC-534.txt","sha256":"0dbbec3b5fdb8709267191f71d8b00fa103c6b5fdbc440cc04c9106f765d7bf2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David Walden\nRequest for Comments: 534 BBN-NET\nNIC: 17453 17 July 1973\nReferences: 512, 516, 533\n\n Lost Message Detection\n\n As an aside to RFC 533, note that if sending Hosts do uniquely\n identify messages on a given link using the extra four bits and\n receiving Hosts do look at these bits, a lost message detection\n system such as those suggested in RFCs 512 and 516 drops right out of\n using of the unique message-id. These extra four bits can be treated\n as Hathaway's SCB of RFC 512 providing a 16 element sequence number\n on a per connection basis. A 16 element sequence is sufficient as\n the IMPs never allow more than four outstanding messages at one time\n between a given pair of Hosts. As Hathaway also suggests, the 0\n element in the sequence can be used to indicate to the receiving Host\n that sequence numbers are not being used.\n\n To summarize, there appear to be ","scope_keywords":["534"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 534 Network Working Group David Walden\nRequest for Comments: 534 BBN-NET\nNIC: 17453 17 July 1973\nReferences: 512, 516, 533\n\n Lost Message Detection\n\n As an aside to RFC 533, note that if sending Hosts do uniquely\n identify messages on a given link using the extra four bits and\n receiving Hosts do look at these bits, a lost message detection\n system such as those suggested in RFCs 512 and 516 drops right out of\n using of the unique message-id. These extra four bits can be treated\n as Hathaway's SCB of RFC 512 providing a 16 element sequence number\n on a per connection basis. A 16 element sequence is sufficient as\n the IMPs never allow more than four outstanding messages at one time\n between a given pair of Hosts. As Hathaway also suggests, the 0\n element in the sequence can be used to indicate to the receiving Host\n that sequence numbers are not being used.\n\n To summarize, there appear to be  534 nested-reference unchanged"},{"id":"IETF RFC 513","type":"specification","body":"IETF","designation":"RFC 513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc513.txt","https://www.rfc-editor.org/rfc/rfc513.pdf"],"folder":"IETF/RFC-513","files":{"txt":{"path":"standards/IETF/RFC-513/RFC-513.txt","sha256":"459c4a4c36711ef75ab0a09daf2c748020def49ebd0ca998f73ecf0df313e1dd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Wayne Hathaway\nRFC # 513 AMES-67\nNIC # 16444 30 May 1973\n\n COMMENTS ON THE NEW TELNET SPECIFICATIONS\n\nI would like to make the following comments on the proposed new TELNET\nProtocol Specification (NIC # 15372) and TELNET Option Specification\n(NIC 15373). In general I feel the new TELNET protocol is far superior\nto the previous version. There are, however, a few items of substance\nwhich I feel should be changed, as well as some recommended editorial\nchanges.\n\nI feel the most significant error concerns the \"Note on 'Sub-\nnegotiations'\" section of the Option Specification (page 2). The\nproblem stems from the statements \"Each party is presumed to be able to\nparse the parameter(s)\" and \"Finally, if parameters in an option\n'subnegotiation' include a byte with a value of 255, it is not necessary\nto double this byte in accordance with the general TELNET IAC.\" These\ntwo stat","scope_keywords":["513"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 562","folder":"IETF/RFC-562","source":"IETF/RFC-562/RFC-562.pdf","version":null}],"search_text":"IETF RFC 513 Network Working Group Wayne Hathaway\nRFC # 513 AMES-67\nNIC # 16444 30 May 1973\n\n COMMENTS ON THE NEW TELNET SPECIFICATIONS\n\nI would like to make the following comments on the proposed new TELNET\nProtocol Specification (NIC # 15372) and TELNET Option Specification\n(NIC 15373). In general I feel the new TELNET protocol is far superior\nto the previous version. There are, however, a few items of substance\nwhich I feel should be changed, as well as some recommended editorial\nchanges.\n\nI feel the most significant error concerns the \"Note on 'Sub-\nnegotiations'\" section of the Option Specification (page 2). The\nproblem stems from the statements \"Each party is presumed to be able to\nparse the parameter(s)\" and \"Finally, if parameters in an option\n'subnegotiation' include a byte with a value of 255, it is not necessary\nto double this byte in accordance with the general TELNET IAC.\" These\ntwo stat 513 nested-reference unchanged"},{"id":"IETF RFC 5168","type":"specification","body":"IETF","designation":"RFC 5168","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5168.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5168.txt","https://www.rfc-editor.org/rfc/rfc5168.pdf"],"folder":"IETF/RFC-5168","files":{"txt":{"path":"standards/IETF/RFC-5168/RFC-5168.txt","sha256":"d0f44b160177bdbb0c2bb261b80ce13547de4f250dbcef140031523f6012e211"}},"tags":["nested-reference","unchanged"],"summary":"This document defines an Extensible Markup Language (XML) Schema for\n video fast update in a tightly controlled environment, developed by\n Microsoft, Polycom, Radvision and used by multiple vendors. This\n document describes a method that has been deployed in Session\n Initiation Protocol (SIP) based systems over the last three years and\n is being used across real-time interactive applications from\n different vendors in an interoperable manner. New implementations\n are discouraged from using the method described except for backward\n compatibility purposes. New implementations are required to use the\n new Full Intra Request command in the RTP Control Protocol (RTCP)\n channel.\n\nLevin, et al. Informational [Page 1]\n\f\nRFC 5168 Media Control March 2008","scope_keywords":["5168","delivery","http","key","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 5168 This document defines an Extensible Markup Language (XML) Schema for\n video fast update in a tightly controlled environment, developed by\n Microsoft, Polycom, Radvision and used by multiple vendors. This\n document describes a method that has been deployed in Session\n Initiation Protocol (SIP) based systems over the last three years and\n is being used across real-time interactive applications from\n different vendors in an interoperable manner. New implementations\n are discouraged from using the method described except for backward\n compatibility purposes. New implementations are required to use the\n new Full Intra Request command in the RTP Control Protocol (RTCP)\n channel.\n\nLevin, et al. Informational [Page 1]\n\f\nRFC 5168 Media Control March 2008 5168 delivery http key path qualified nested-reference unchanged"},{"id":"IETF RFC 519","type":"specification","body":"IETF","designation":"RFC 519","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc519.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc519.txt","https://www.rfc-editor.org/rfc/rfc519.pdf"],"folder":"IETF/RFC-519","files":{"pdf":{"path":"standards/IETF/RFC-519/RFC-519.pdf","sha256":"c2568da574735e4440beed7b10d89e494ad135d242622e31348a205181280b02"},"txt":{"path":"standards/IETF/RFC-519/RFC-519.txt","sha256":"5e615a52d0b765abafcdf4c0e02d8b79c17c291217dc0d2d2c681d40acc156c1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Pickens\nRequest for Comments: 519 Computer Systems Laboratory -- UCSB\nNIC: 16818 June 1973\n\n Resource Evaluation\n\nAbstract\n\n In the spirit of RFC # 369, Evaluation of ARPANET resources, a new\n test group was organized at UCSB to take a detailed look at specific\n network resources and develop initial site dependent and function\n dependent MINIMAN's (Concise User Manuals). As the group was again\n composed of novices, initial effort revolved about basic procedural\n indoctrination. In the period between January and March 1973 a\n number of resources were investigated with varying degrees of\n success, as to availability, proper usage, sample problem solutions,\n and access to help and documentation. Included in this paper are a\n summary of the projects undertaken, initial suggestions at MINIMAN\n composition, and suggestions for future test groups. As these groups\n are a","scope_keywords":["519","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 531","folder":"IETF/RFC-531","source":"IETF/RFC-531/RFC-531.txt","version":null}],"search_text":"IETF RFC 519 Network Working Group J. Pickens\nRequest for Comments: 519 Computer Systems Laboratory -- UCSB\nNIC: 16818 June 1973\n\n Resource Evaluation\n\nAbstract\n\n In the spirit of RFC # 369, Evaluation of ARPANET resources, a new\n test group was organized at UCSB to take a detailed look at specific\n network resources and develop initial site dependent and function\n dependent MINIMAN's (Concise User Manuals). As the group was again\n composed of novices, initial effort revolved about basic procedural\n indoctrination. In the period between January and March 1973 a\n number of resources were investigated with varying degrees of\n success, as to availability, proper usage, sample problem solutions,\n and access to help and documentation. Included in this paper are a\n summary of the projects undertaken, initial suggestions at MINIMAN\n composition, and suggestions for future test groups. As these groups\n are a 519 key nested-reference unchanged"},{"id":"IETF RFC 520","type":"specification","body":"IETF","designation":"RFC 520","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc520.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc520.txt","https://www.rfc-editor.org/rfc/rfc520.pdf"],"folder":"IETF/RFC-520","files":{"txt":{"path":"standards/IETF/RFC-520/RFC-520.txt","sha256":"3d4a44198895273288d24daf91f8a8f65ecdda9b659290aff3d833b50b77164c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Day\nRequest for Comments: 520 Center for Advanced Computation\nNIC: 16819 25 June 1973\n\n A Proposed File Access Protocol Specification\n\n Attached is a proposal for the File Access Protocol. FAP is an\n extension to FTP. I believe the specification is fairly general and\n should provide a good jumping-off place. I hope the protocol is\n specified in such a way as to fit with idiosyncrasies of most\n systems. If the protocol would cause an inordinate amount of burden\n on your system for one reason or another I would like to hear about\n it.\n\n At some later date when the difficulties of implementation are better\n known, I would like to see several levels of implementation specified\n and implementation be done in terms of those levels.\n\n From rumors I have heard I believe this will also allow creation and\n transfer of what TENEX calls \"holey\" files. But, I am not sure of\n ","scope_keywords":["520","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 520 Network Working Group J. Day\nRequest for Comments: 520 Center for Advanced Computation\nNIC: 16819 25 June 1973\n\n A Proposed File Access Protocol Specification\n\n Attached is a proposal for the File Access Protocol. FAP is an\n extension to FTP. I believe the specification is fairly general and\n should provide a good jumping-off place. I hope the protocol is\n specified in such a way as to fit with idiosyncrasies of most\n systems. If the protocol would cause an inordinate amount of burden\n on your system for one reason or another I would like to hear about\n it.\n\n At some later date when the difficulties of implementation are better\n known, I would like to see several levels of implementation specified\n and implementation be done in terms of those levels.\n\n From rumors I have heard I believe this will also allow creation and\n transfer of what TENEX calls \"holey\" files. But, I am not sure of\n  520 crl presentation nested-reference unchanged"},{"id":"IETF RFC 5208","type":"specification","body":"IETF","designation":"RFC 5208","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5208.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5208.txt","https://www.rfc-editor.org/rfc/rfc5208.pdf"],"folder":"IETF/RFC-5208","files":{"txt":{"path":"standards/IETF/RFC-5208/RFC-5208.txt","sha256":"89f7338cf546abaee1d14eef7357440f4fc45e579d47dd4b436c29533abafc2e"}},"tags":["nested-reference","unchanged"],"summary":"This document represents a republication of PKCS #8 v1.2 from RSA\n Laboratories' Public Key Cryptography Standard (PKCS) series. Change\n control is transferred to the IETF. The body of this document,\n except for the security considerations section, is taken directly\n from the PKCS #8 v1.2 specification.\n\n This document describes a syntax for private-key information.","scope_keywords":["5208","algorithm","attribute","attributes","encryption","key","keys","signature","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7914","folder":"IETF/RFC-7914","source":"IETF/RFC-7914/RFC-7914.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"IETF RFC 5208 This document represents a republication of PKCS #8 v1.2 from RSA\n Laboratories' Public Key Cryptography Standard (PKCS) series. Change\n control is transferred to the IETF. The body of this document,\n except for the security considerations section, is taken directly\n from the PKCS #8 v1.2 specification.\n\n This document describes a syntax for private-key information. 5208 algorithm attribute attributes encryption key keys signature trust nested-reference unchanged"},{"id":"IETF RFC 6813","type":"specification","body":"IETF","designation":"RFC 6813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6813.txt","https://www.rfc-editor.org/rfc/rfc6813.pdf"],"folder":"IETF/RFC-6813","files":{"txt":{"path":"standards/IETF/RFC-6813/RFC-6813.txt","sha256":"9f2ba4f720a294c21e460508838759b81da751e2dbb01d909f818dc8f9a0d4a4"}},"tags":["nested-reference","unchanged"],"summary":"The Network Endpoint Assessment (NEA) protocols are subject to a\n subtle forwarding attack that has become known as the NEA Asokan\n Attack. This document describes the attack and countermeasures that\n may be mounted.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6813.\n\nCopyright Notice\n","scope_keywords":["6813","attribute","authentication","authorization","http","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6876","folder":"IETF/RFC-6876","source":"IETF/RFC-6876/RFC-6876.txt","version":null},{"body":"IETF","designation":"RFC 7171","folder":"IETF/RFC-7171","source":"IETF/RFC-7171/RFC-7171.txt","version":null}],"search_text":"IETF RFC 6813 The Network Endpoint Assessment (NEA) protocols are subject to a\n subtle forwarding attack that has become known as the NEA Asokan\n Attack. This document describes the attack and countermeasures that\n may be mounted.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6813.\n\nCopyright Notice\n 6813 attribute authentication authorization http license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8248","type":"specification","body":"IETF","designation":"RFC 8248","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8248.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8248.txt","https://www.rfc-editor.org/rfc/rfc8248.pdf"],"folder":"IETF/RFC-8248","files":{"txt":{"path":"standards/IETF/RFC-8248/RFC-8248.txt","sha256":"db4dace4f2071ffeb0e268ac2692d884a81e0c907285b89a7c28241ffab2561a"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the scope and set of requirements for the\n Security Automation and Continuous Monitoring (SACM) architecture,\n data model, and transfer protocols. The requirements and scope are\n based on the agreed-upon use cases described in RFC 7632.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-","scope_keywords":["8248","attribute","attributes","http","https","identification","license","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"IETF RFC 8248 This document defines the scope and set of requirements for the\n Security Automation and Continuous Monitoring (SACM) architecture,\n data model, and transfer protocols. The requirements and scope are\n based on the agreed-upon use cases described in RFC 7632.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc- 8248 attribute attributes http https identification license pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5212","type":"specification","body":"IETF","designation":"RFC 5212","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5212.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5212.txt","https://www.rfc-editor.org/rfc/rfc5212.pdf"],"folder":"IETF/RFC-5212","files":{"txt":{"path":"standards/IETF/RFC-5212/RFC-5212.txt","sha256":"d3fa6bed09460ad5281d10e126d6ad23c185d28b28a399883a1ebc45a2b08047"}},"tags":["nested-reference","unchanged"],"summary":"Most of the initial efforts to utilize Generalized MPLS (GMPLS) have\n been related to environments hosting devices with a single switching\n capability. The complexity raised by the control of such data planes\n is similar to that seen in classical IP/MPLS networks. By extending\n MPLS to support multiple switching technologies, GMPLS provides a\n comprehensive framework for the control of a multi-layered network of\n either a single switching technology or multiple switching\n technologies.\n\n In GMPLS, a switching technology domain defines a region, and a\n network of multiple switching types is referred to in this document\n as a multi-region network (MRN). When referring in general to a\n layered network, which may consist of either single or multiple\n regions, this document uses the term multi-layer network (MLN). This\n document defines a framework for GMPLS based multi-region / multi-\n layer","scope_keywords":["5212","attribute","key","management","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 5212 Most of the initial efforts to utilize Generalized MPLS (GMPLS) have\n been related to environments hosting devices with a single switching\n capability. The complexity raised by the control of such data planes\n is similar to that seen in classical IP/MPLS networks. By extending\n MPLS to support multiple switching technologies, GMPLS provides a\n comprehensive framework for the control of a multi-layered network of\n either a single switching technology or multiple switching\n technologies.\n\n In GMPLS, a switching technology domain defines a region, and a\n network of multiple switching types is referred to in this document\n as a multi-region network (MRN). When referring in general to a\n layered network, which may consist of either single or multiple\n regions, this document uses the term multi-layer network (MLN). This\n document defines a framework for GMPLS based multi-region / multi-\n layer 5212 attribute key management path presentation nested-reference unchanged"},{"id":"IETF RFC 522","type":"specification","body":"IETF","designation":"RFC 522","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc522.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc522.txt","https://www.rfc-editor.org/rfc/rfc522.pdf"],"folder":"IETF/RFC-522","files":{"pdf":{"path":"standards/IETF/RFC-522/RFC-522.pdf","sha256":"1c74f6d872c698d934e9f8e0cbfb68f9ed3ae2aecfe0b82804184f337e7b4ea5"},"txt":{"path":"standards/IETF/RFC-522/RFC-522.txt","sha256":"8af57e18555c0ebf60aabae11e34d4b65c6f5fbb23813d0b1b60567a668de39e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 522 BBN-NET\nNIC: 17033 June 1973\nUpdates: 509\n\n Traffic Statistics (May 1973)\n\n Attached are the Host traffic statistics for the month of May 1973.\n\n AAM/jm\n\nMcKenzie [Page 1]\n\f\nRFC 522 Traffic Statistics June 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n MAY 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 185058 62867 247925\n UCLA HOST 1 1570767 173284 1744051\n UCLA HOST 2 2 693047 693049\n ---------- -------- ----------\n 1755827 929198 2685025 56640 31\n\n SRI HOST 0 3380587 131122 3511709\n SRI HOST 1 109950 96245 206195\n --------- -------- ---------\n 3490537 227367 3717904 112598 31\n\n UTAH HOST 0 840680 108731 949411 27119 31\n\n MIT HOST 0 199665 26780 226445\n MIT HOST 1 624682 147253 671935\n MIT HOST 2 724064 830745 1554809\n MIT HOST 3 666939 620027 1286966\n -------- -------- ---------\n 2115350 162","scope_keywords":["522"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 538","folder":"IETF/RFC-538","source":"IETF/RFC-538/RFC-538.txt","version":null}],"search_text":"IETF RFC 522 Network Working Group A. McKenzie\nRequest for Comments: 522 BBN-NET\nNIC: 17033 June 1973\nUpdates: 509\n\n Traffic Statistics (May 1973)\n\n Attached are the Host traffic statistics for the month of May 1973.\n\n AAM/jm\n\nMcKenzie [Page 1]\n\f\nRFC 522 Traffic Statistics June 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n MAY 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 185058 62867 247925\n UCLA HOST 1 1570767 173284 1744051\n UCLA HOST 2 2 693047 693049\n ---------- -------- ----------\n 1755827 929198 2685025 56640 31\n\n SRI HOST 0 3380587 131122 3511709\n SRI HOST 1 109950 96245 206195\n --------- -------- ---------\n 3490537 227367 3717904 112598 31\n\n UTAH HOST 0 840680 108731 949411 27119 31\n\n MIT HOST 0 199665 26780 226445\n MIT HOST 1 624682 147253 671935\n MIT HOST 2 724064 830745 1554809\n MIT HOST 3 666939 620027 1286966\n -------- -------- ---------\n 2115350 162 522 nested-reference unchanged"},{"id":"IETF RFC 538","type":"specification","body":"IETF","designation":"RFC 538","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc538.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc538.txt","https://www.rfc-editor.org/rfc/rfc538.pdf"],"folder":"IETF/RFC-538","files":{"txt":{"path":"standards/IETF/RFC-538/RFC-538.txt","sha256":"7e25c6da8bafa86551f72dfbe050b569c5e50efdff11fdb4bf2d7f07ec7abd60"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 538 BBN-NET\nNIC: 17642 5 July 1973\nUpdates: RFC 522\n\n Traffic Statistics (June 1973)\n\nABSTRACT\n\n Attached are the Host traffic statistics for the month of June 1973.\n\n AAM/jm\n\n Attach\n\nHOST THROUGHPUT SUMMARY (PACKETS OUTPUT)\n\nJUNE 1973\n\n INTER- INTRA- AVG.DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 233219 23987 257205\n UCLA HOST 1 1622927 86513 17094400\n UCLA HOST 2 0 634752 634752\n ------- ------- --------\n 1856146 745252 2601398 61872 30\n\n SRI HOST 0 3437898 1923744 5361642\n SRI HOST 1 140401 5809 146210\n ------- ------- -------\n 3578299 1929553 5507852 119277 30\n\n UCSB HOST 0 927927 1374995 2302922\n UCSB HOST 1 101548 4678 106226\n ------- ------- -------\n 1029475 1379673 2409148 34316 30\n\n UTAH HOST 0 332271 86501 418772 11076 30\n\n BBN HOST 0 15 36219 36234\n BBN HOST 1 3408020 1030589 4438609\n BBN HOST 2 24615 1298310 13","scope_keywords":["538"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 538 Network Working Group A. McKenzie\nRequest for Comments: 538 BBN-NET\nNIC: 17642 5 July 1973\nUpdates: RFC 522\n\n Traffic Statistics (June 1973)\n\nABSTRACT\n\n Attached are the Host traffic statistics for the month of June 1973.\n\n AAM/jm\n\n Attach\n\nHOST THROUGHPUT SUMMARY (PACKETS OUTPUT)\n\nJUNE 1973\n\n INTER- INTRA- AVG.DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 233219 23987 257205\n UCLA HOST 1 1622927 86513 17094400\n UCLA HOST 2 0 634752 634752\n ------- ------- --------\n 1856146 745252 2601398 61872 30\n\n SRI HOST 0 3437898 1923744 5361642\n SRI HOST 1 140401 5809 146210\n ------- ------- -------\n 3578299 1929553 5507852 119277 30\n\n UCSB HOST 0 927927 1374995 2302922\n UCSB HOST 1 101548 4678 106226\n ------- ------- -------\n 1029475 1379673 2409148 34316 30\n\n UTAH HOST 0 332271 86501 418772 11076 30\n\n BBN HOST 0 15 36219 36234\n BBN HOST 1 3408020 1030589 4438609\n BBN HOST 2 24615 1298310 13 538 nested-reference unchanged"},{"id":"IETF RFC 7736","type":"specification","body":"IETF","designation":"RFC 7736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7736.txt","https://www.rfc-editor.org/rfc/rfc7736.pdf"],"folder":"IETF/RFC-7736","files":{"txt":{"path":"standards/IETF/RFC-7736/RFC-7736.txt","sha256":"0789e46b03e80569cbcf0f7af6dbc54e74d218598d6e775345fb2a73ab69e908"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the standard media type used by the Content\n Delivery Network Interconnection (CDNI) protocol suite, including the\n registration procedure and recommended usage of the required payload-\n type parameter.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7736.\n\nCopyright","scope_keywords":["7736","authentication","authorization","delivery","http","license","management","registered","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 7736 This document defines the standard media type used by the Content\n Delivery Network Interconnection (CDNI) protocol suite, including the\n registration procedure and recommended usage of the required payload-\n type parameter.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7736.\n\nCopyright 7736 authentication authorization delivery http license management registered subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5234","type":"specification","body":"IETF","designation":"RFC 5234","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5234.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5234.txt","https://www.rfc-editor.org/rfc/rfc5234.pdf"],"folder":"IETF/RFC-5234","files":{"txt":{"path":"standards/IETF/RFC-5234/RFC-5234.txt","sha256":"fc871020f53baa6b60fc6835c557b433f38d53c5cc41ab56d03622b084f53a12"}},"tags":["nested-reference","unchanged"],"summary":"Internet technical specifications often need to define a formal\n syntax. Over the years, a modified version of Backus-Naur Form\n (BNF), called Augmented BNF (ABNF), has been popular among many\n Internet specifications. The current specification documents ABNF.\n It balances compactness and simplicity with reasonable\n representational power. The differences between standard BNF and\n ABNF involve naming rules, repetition, alternatives, order-\n independence, and value ranges. This specification also supplies\n additional rule definitions and encoding for a core lexical analyzer\n of the type common to several Internet specifications.\n\nCrocker & Overell Standards Track [Page 1]\n\f\nRFC 5234 ABNF January 2008","scope_keywords":["5234","crl","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5161","folder":"IETF/RFC-5161","source":"IETF/RFC-5161/RFC-5161.txt","version":null},{"body":"IETF","designation":"RFC 5162","folder":"IETF/RFC-5162","source":"IETF/RFC-5162/RFC-5162.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5191","folder":"IETF/RFC-5191","source":"IETF/RFC-5191/RFC-5191.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5245","folder":"IETF/RFC-5245","source":"IETF/RFC-5245/RFC-5245.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5258","folder":"IETF/RFC-5258","source":"IETF/RFC-5258/RFC-5258.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5267","folder":"IETF/RFC-5267","source":"IETF/RFC-5267/RFC-5267.txt","version":null},{"body":"IETF","designation":"RFC 5285","folder":"IETF/RFC-5285","source":"IETF/RFC-5285/RFC-5285.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5360","folder":"IETF/RFC-5360","source":"IETF/RFC-5360/RFC-5360.txt","version":null},{"body":"IETF","designation":"RFC 5393","folder":"IETF/RFC-5393","source":"IETF/RFC-5393/RFC-5393.txt","version":null},{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5425","folder":"IETF/RFC-5425","source":"IETF/RFC-5425/RFC-5425.txt","version":null},{"body":"IETF","designation":"RFC 5432","folder":"IETF/RFC-5432","source":"IETF/RFC-5432/RFC-5432.txt","version":null},{"body":"IETF","designation":"RFC 5435","folder":"IETF/RFC-5435","source":"IETF/RFC-5435/RFC-5435.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5464","folder":"IETF/RFC-5464","source":"IETF/RFC-5464/RFC-5464.txt","version":null},{"body":"IETF","designation":"RFC 5465","folder":"IETF/RFC-5465","source":"IETF/RFC-5465/RFC-5465.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5484","folder":"IETF/RFC-5484","source":"IETF/RFC-5484/RFC-5484.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null},{"body":"IETF","designation":"RFC 5518","folder":"IETF/RFC-5518","source":"IETF/RFC-5518/RFC-5518.txt","version":null},{"body":"IETF","designation":"RFC 5530","folder":"IETF/RFC-5530","source":"IETF/RFC-5530/RFC-5530.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5576","folder":"IETF/RFC-5576","source":"IETF/RFC-5576/RFC-5576.txt","version":null},{"body":"IETF","designation":"RFC 5583","folder":"IETF/RFC-5583","source":"IETF/RFC-5583/RFC-5583.txt","version":null},{"body":"IETF","designation":"RFC 5617","folder":"IETF/RFC-5617","source":"IETF/RFC-5617/RFC-5617.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5627","folder":"IETF/RFC-5627","source":"IETF/RFC-5627/RFC-5627.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5657","folder":"IETF/RFC-5657","source":"IETF/RFC-5657/RFC-5657.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5725","folder":"IETF/RFC-5725","source":"IETF/RFC-5725/RFC-5725.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5762","folder":"IETF/RFC-5762","source":"IETF/RFC-5762/RFC-5762.txt","version":null},{"body":"IETF","designation":"RFC 5781","folder":"IETF/RFC-5781","source":"IETF/RFC-5781/RFC-5781.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5803","folder":"IETF/RFC-5803","source":"IETF/RFC-5803/RFC-5803.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5819","folder":"IETF/RFC-5819","source":"IETF/RFC-5819/RFC-5819.txt","version":null},{"body":"IETF","designation":"RFC 5839","folder":"IETF/RFC-5839","source":"IETF/RFC-5839/RFC-5839.txt","version":null},{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null},{"body":"IETF","designation":"RFC 5888","folder":"IETF/RFC-5888","source":"IETF/RFC-5888/RFC-5888.txt","version":null},{"body":"IETF","designation":"RFC 5923","folder":"IETF/RFC-5923","source":"IETF/RFC-5923/RFC-5923.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 5954","folder":"IETF/RFC-5954","source":"IETF/RFC-5954/RFC-5954.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5971","folder":"IETF/RFC-5971","source":"IETF/RFC-5971/RFC-5971.txt","version":null},{"body":"IETF","designation":"RFC 5974","folder":"IETF/RFC-5974","source":"IETF/RFC-5974/RFC-5974.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 5989","folder":"IETF/RFC-5989","source":"IETF/RFC-5989/RFC-5989.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6080","folder":"IETF/RFC-6080","source":"IETF/RFC-6080/RFC-6080.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6128","folder":"IETF/RFC-6128","source":"IETF/RFC-6128/RFC-6128.txt","version":null},{"body":"IETF","designation":"RFC 6152","folder":"IETF/RFC-6152","source":"IETF/RFC-6152/RFC-6152.txt","version":null},{"body":"IETF","designation":"RFC 6154","folder":"IETF/RFC-6154","source":"IETF/RFC-6154/RFC-6154.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 6242","folder":"IETF/RFC-6242","source":"IETF/RFC-6242/RFC-6242.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6336","folder":"IETF/RFC-6336","source":"IETF/RFC-6336/RFC-6336.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6363","folder":"IETF/RFC-6363","source":"IETF/RFC-6363/RFC-6363.txt","version":null},{"body":"IETF","designation":"RFC 6364","folder":"IETF/RFC-6364","source":"IETF/RFC-6364/RFC-6364.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6408","folder":"IETF/RFC-6408","source":"IETF/RFC-6408/RFC-6408.txt","version":null},{"body":"IETF","designation":"RFC 6415","folder":"IETF/RFC-6415","source":"IETF/RFC-6415/RFC-6415.txt","version":null},{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null},{"body":"IETF","designation":"RFC 6454","folder":"IETF/RFC-6454","source":"IETF/RFC-6454/RFC-6454.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6541","folder":"IETF/RFC-6541","source":"IETF/RFC-6541/RFC-6541.txt","version":null},{"body":"IETF","designation":"RFC 6544","folder":"IETF/RFC-6544","source":"IETF/RFC-6544/RFC-6544.txt","version":null},{"body":"IETF","designation":"RFC 6546","folder":"IETF/RFC-6546","source":"IETF/RFC-6546/RFC-6546.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6642","folder":"IETF/RFC-6642","source":"IETF/RFC-6642/RFC-6642.txt","version":null},{"body":"IETF","designation":"RFC 6651","folder":"IETF/RFC-6651","source":"IETF/RFC-6651/RFC-6651.txt","version":null},{"body":"IETF","designation":"RFC 6652","folder":"IETF/RFC-6652","source":"IETF/RFC-6652/RFC-6652.txt","version":null},{"body":"IETF","designation":"RFC 6665","folder":"IETF/RFC-6665","source":"IETF/RFC-6665/RFC-6665.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6694","folder":"IETF/RFC-6694","source":"IETF/RFC-6694/RFC-6694.txt","version":null},{"body":"IETF","designation":"RFC 6714","folder":"IETF/RFC-6714","source":"IETF/RFC-6714/RFC-6714.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6750","folder":"IETF/RFC-6750","source":"IETF/RFC-6750/RFC-6750.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 6849","folder":"IETF/RFC-6849","source":"IETF/RFC-6849/RFC-6849.txt","version":null},{"body":"IETF","designation":"RFC 6851","folder":"IETF/RFC-6851","source":"IETF/RFC-6851/RFC-6851.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6871","folder":"IETF/RFC-6871","source":"IETF/RFC-6871/RFC-6871.txt","version":null},{"body":"IETF","designation":"RFC 6874","folder":"IETF/RFC-6874","source":"IETF/RFC-6874/RFC-6874.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 6904","folder":"IETF/RFC-6904","source":"IETF/RFC-6904/RFC-6904.txt","version":null},{"body":"IETF","designation":"RFC 6910","folder":"IETF/RFC-6910","source":"IETF/RFC-6910/RFC-6910.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null},{"body":"IETF","designation":"RFC 6929","folder":"IETF/RFC-6929","source":"IETF/RFC-6929/RFC-6929.txt","version":null},{"body":"IETF","designation":"RFC 6947","folder":"IETF/RFC-6947","source":"IETF/RFC-6947/RFC-6947.txt","version":null},{"body":"IETF","designation":"RFC 6958","folder":"IETF/RFC-6958","source":"IETF/RFC-6958/RFC-6958.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7002","folder":"IETF/RFC-7002","source":"IETF/RFC-7002/RFC-7002.txt","version":null},{"body":"IETF","designation":"RFC 7003","folder":"IETF/RFC-7003","source":"IETF/RFC-7003/RFC-7003.txt","version":null},{"body":"IETF","designation":"RFC 7004","folder":"IETF/RFC-7004","source":"IETF/RFC-7004/RFC-7004.txt","version":null},{"body":"IETF","designation":"RFC 7006","folder":"IETF/RFC-7006","source":"IETF/RFC-7006/RFC-7006.txt","version":null},{"body":"IETF","designation":"RFC 7064","folder":"IETF/RFC-7064","source":"IETF/RFC-7064/RFC-7064.txt","version":null},{"body":"IETF","designation":"RFC 7065","folder":"IETF/RFC-7065","source":"IETF/RFC-7065/RFC-7065.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7155","folder":"IETF/RFC-7155","source":"IETF/RFC-7155/RFC-7155.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 7162","folder":"IETF/RFC-7162","source":"IETF/RFC-7162/RFC-7162.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7197","folder":"IETF/RFC-7197","source":"IETF/RFC-7197/RFC-7197.txt","version":null},{"body":"IETF","designation":"RFC 7208","folder":"IETF/RFC-7208","source":"IETF/RFC-7208/RFC-7208.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 7232","folder":"IETF/RFC-7232","source":"IETF/RFC-7232/RFC-7232.txt","version":null},{"body":"IETF","designation":"RFC 7233","folder":"IETF/RFC-7233","source":"IETF/RFC-7233/RFC-7233.txt","version":null},{"body":"IETF","designation":"RFC 7234","folder":"IETF/RFC-7234","source":"IETF/RFC-7234/RFC-7234.txt","version":null},{"body":"IETF","designation":"RFC 7235","folder":"IETF/RFC-7235","source":"IETF/RFC-7235/RFC-7235.txt","version":null},{"body":"IETF","designation":"RFC 7239","folder":"IETF/RFC-7239","source":"IETF/RFC-7239/RFC-7239.txt","version":null},{"body":"IETF","designation":"RFC 7240","folder":"IETF/RFC-7240","source":"IETF/RFC-7240/RFC-7240.txt","version":null},{"body":"IETF","designation":"RFC 7247","folder":"IETF/RFC-7247","source":"IETF/RFC-7247/RFC-7247.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null},{"body":"IETF","designation":"RFC 7272","folder":"IETF/RFC-7272","source":"IETF/RFC-7272/RFC-7272.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 7405","folder":"IETF/RFC-7405","source":"IETF/RFC-7405/RFC-7405.txt","version":null},{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null},{"body":"IETF","designation":"RFC 7463","folder":"IETF/RFC-7463","source":"IETF/RFC-7463/RFC-7463.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7469","folder":"IETF/RFC-7469","source":"IETF/RFC-7469/RFC-7469.txt","version":null},{"body":"IETF","designation":"RFC 7480","folder":"IETF/RFC-7480","source":"IETF/RFC-7480/RFC-7480.txt","version":null},{"body":"IETF","designation":"RFC 7486","folder":"IETF/RFC-7486","source":"IETF/RFC-7486/RFC-7486.txt","version":null},{"body":"IETF","designation":"RFC 7489","folder":"IETF/RFC-7489","source":"IETF/RFC-7489/RFC-7489.txt","version":null},{"body":"IETF","designation":"RFC 7495","folder":"IETF/RFC-7495","source":"IETF/RFC-7495/RFC-7495.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7615","folder":"IETF/RFC-7615","source":"IETF/RFC-7615/RFC-7615.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7636","folder":"IETF/RFC-7636","source":"IETF/RFC-7636/RFC-7636.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7736","folder":"IETF/RFC-7736","source":"IETF/RFC-7736/RFC-7736.txt","version":null},{"body":"IETF","designation":"RFC 7749","folder":"IETF/RFC-7749","source":"IETF/RFC-7749/RFC-7749.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7817","folder":"IETF/RFC-7817","source":"IETF/RFC-7817/RFC-7817.txt","version":null},{"body":"IETF","designation":"RFC 7825","folder":"IETF/RFC-7825","source":"IETF/RFC-7825/RFC-7825.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7888","folder":"IETF/RFC-7888","source":"IETF/RFC-7888/RFC-7888.txt","version":null},{"body":"IETF","designation":"RFC 7889","folder":"IETF/RFC-7889","source":"IETF/RFC-7889/RFC-7889.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7951","folder":"IETF/RFC-7951","source":"IETF/RFC-7951/RFC-7951.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8040","folder":"IETF/RFC-8040","source":"IETF/RFC-8040/RFC-8040.txt","version":null},{"body":"IETF","designation":"RFC 8053","folder":"IETF/RFC-8053","source":"IETF/RFC-8053/RFC-8053.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8055","folder":"IETF/RFC-8055","source":"IETF/RFC-8055/RFC-8055.txt","version":null},{"body":"IETF","designation":"RFC 8075","folder":"IETF/RFC-8075","source":"IETF/RFC-8075/RFC-8075.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8285","folder":"IETF/RFC-8285","source":"IETF/RFC-8285/RFC-8285.txt","version":null},{"body":"IETF","designation":"RFC 8288","folder":"IETF/RFC-8288","source":"IETF/RFC-8288/RFC-8288.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8322","folder":"IETF/RFC-8322","source":"IETF/RFC-8322/RFC-8322.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8464","folder":"IETF/RFC-8464","source":"IETF/RFC-8464/RFC-8464.txt","version":null},{"body":"IETF","designation":"RFC 8470","folder":"IETF/RFC-8470","source":"IETF/RFC-8470/RFC-8470.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8586","folder":"IETF/RFC-8586","source":"IETF/RFC-8586/RFC-8586.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8613","folder":"IETF/RFC-8613","source":"IETF/RFC-8613/RFC-8613.txt","version":null},{"body":"IETF","designation":"RFC 8689","folder":"IETF/RFC-8689","source":"IETF/RFC-8689/RFC-8689.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8839","folder":"IETF/RFC-8839","source":"IETF/RFC-8839/RFC-8839.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8856","folder":"IETF/RFC-8856","source":"IETF/RFC-8856/RFC-8856.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9193","folder":"IETF/RFC-9193","source":"IETF/RFC-9193/RFC-9193.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9449","folder":"IETF/RFC-9449","source":"IETF/RFC-9449/RFC-9449.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null},{"body":"IETF","designation":"RFC 9460","folder":"IETF/RFC-9460","source":"IETF/RFC-9460/RFC-9460.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"IETF RFC 5234 Internet technical specifications often need to define a formal\n syntax. Over the years, a modified version of Backus-Naur Form\n (BNF), called Augmented BNF (ABNF), has been popular among many\n Internet specifications. The current specification documents ABNF.\n It balances compactness and simplicity with reasonable\n representational power. The differences between standard BNF and\n ABNF involve naming rules, repetition, alternatives, order-\n independence, and value ranges. This specification also supplies\n additional rule definitions and encoding for a core lexical analyzer\n of the type common to several Internet specifications.\n\nCrocker & Overell Standards Track [Page 1]\n\f\nRFC 5234 ABNF January 2008 5234 crl presentation nested-reference unchanged"},{"id":"IETF RFC 7405","type":"specification","body":"IETF","designation":"RFC 7405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7405.txt","https://www.rfc-editor.org/rfc/rfc7405.pdf"],"folder":"IETF/RFC-7405","files":{"txt":{"path":"standards/IETF/RFC-7405/RFC-7405.txt","sha256":"f85c88bcf8ca8035585b39f518adfe274bb095801c95ef665b49a27b61245f17"}},"tags":["nested-reference","unchanged"],"summary":"This document extends the base definition of ABNF (Augmented Backus-\n Naur Form) to include a way to specify US-ASCII string literals that\n are matched in a case-sensitive manner.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7405.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BC","scope_keywords":["7405","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7838","folder":"IETF/RFC-7838","source":"IETF/RFC-7838/RFC-7838.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8054","folder":"IETF/RFC-8054","source":"IETF/RFC-8054/RFC-8054.txt","version":null},{"body":"IETF","designation":"RFC 8460","folder":"IETF/RFC-8460","source":"IETF/RFC-8460/RFC-8460.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8840","folder":"IETF/RFC-8840","source":"IETF/RFC-8840/RFC-8840.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 9039","folder":"IETF/RFC-9039","source":"IETF/RFC-9039/RFC-9039.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9111","folder":"IETF/RFC-9111","source":"IETF/RFC-9111/RFC-9111.txt","version":null},{"body":"IETF","designation":"RFC 9112","folder":"IETF/RFC-9112","source":"IETF/RFC-9112/RFC-9112.txt","version":null},{"body":"IETF","designation":"RFC 9165","folder":"IETF/RFC-9165","source":"IETF/RFC-9165/RFC-9165.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9711","folder":"IETF/RFC-9711","source":"IETF/RFC-9711/RFC-9711.txt","version":null}],"search_text":"IETF RFC 7405 This document extends the base definition of ABNF (Augmented Backus-\n Naur Form) to include a way to specify US-ASCII string literals that\n are matched in a case-sensitive manner.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7405.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BC 7405 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 524","type":"specification","body":"IETF","designation":"RFC 524","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc524.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc524.txt","https://www.rfc-editor.org/rfc/rfc524.pdf"],"folder":"IETF/RFC-524","files":{"txt":{"path":"standards/IETF/RFC-524/RFC-524.txt","sha256":"5df9385b116e062589a0154d8cf0259926f9ff299eef0c2ad5d76d31e5172dee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. White\nRequest for Comments: 524 SRI-ARC\nNIC: 17140 13 June 1973\n\n A Proposed Mail Protocol\n\nAUTHOR'S INTENT\n\n This is the document I offered in (15146,) to write. It's a proposed\n specification for handling mail in the Network -- a Mail Protocol.\n\n Main handling is currently implemented as two FTP commands, MAIL and\n MLFL, which permit an FTP user process to deliver a file or string of\n text to an FTP server process, designating it as mail to be made\n available to a user, identified by a local name, in its host. The\n protocol proposed here is much richer than that, both in terms of the\n functions it supports, and in terms of the flexibility it provides.\n\n Although one can (I think) and might, implement software on the basis\n of this document, this REALLY IS a Request for Comments. Comments,\n questions, position papers are solicited. There are, I'm sure, bugs\n in ","scope_keywords":["524","attribute","attributes","crl","presentation","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 539","folder":"IETF/RFC-539","source":"IETF/RFC-539/RFC-539.txt","version":null},{"body":"IETF","designation":"RFC 555","folder":"IETF/RFC-555","source":"IETF/RFC-555/RFC-555.txt","version":null},{"body":"IETF","designation":"RFC 561","folder":"IETF/RFC-561","source":"IETF/RFC-561/RFC-561.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null}],"search_text":"IETF RFC 524 Network Working Group J. White\nRequest for Comments: 524 SRI-ARC\nNIC: 17140 13 June 1973\n\n A Proposed Mail Protocol\n\nAUTHOR'S INTENT\n\n This is the document I offered in (15146,) to write. It's a proposed\n specification for handling mail in the Network -- a Mail Protocol.\n\n Main handling is currently implemented as two FTP commands, MAIL and\n MLFL, which permit an FTP user process to deliver a file or string of\n text to an FTP server process, designating it as mail to be made\n available to a user, identified by a local name, in its host. The\n protocol proposed here is much richer than that, both in terms of the\n functions it supports, and in terms of the flexibility it provides.\n\n Although one can (I think) and might, implement software on the basis\n of this document, this REALLY IS a Request for Comments. Comments,\n questions, position papers are solicited. There are, I'm sure, bugs\n in  524 attribute attributes crl presentation qualified nested-reference unchanged"},{"id":"IETF RFC 539","type":"specification","body":"IETF","designation":"RFC 539","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc539.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc539.txt","https://www.rfc-editor.org/rfc/rfc539.pdf"],"folder":"IETF/RFC-539","files":{"txt":{"path":"standards/IETF/RFC-539/RFC-539.txt","sha256":"10f43e7bdd22d85c009c9890fcaa32426eff2343f0f731fe74b05fc15bb99dc8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker (UCLA-NMC)\nRequest For Comment: #539 J. Postel (UCLA-NMC)\nNIC 17644 July 9, 1973\nReferences: 524\n\n Thoughts on the Mail Protocol Proposed in RFC 524\n\nGenerally, we feel that the protocol is extremely rich. We also feel\nthat there are some minor and some major problems.\n\nThe minor points first:\n\n 1. and are not explained until the formal syntax. It\n would be more convenient, if they were explained sooner.\n\n 2. The Proposed is a bad thing, since it is the Telnet Go-\n Ahead, which should not be used by higher level protocols.\n\n 3. The default SIGNATURE should be the sign-on or ident of the\n author(s).\n\n 4. The Disposition INTERRUPT would be more useful if it had\n author/clerk-assigned \"levels\". Currently mail would be either\n urgent or not. With levels (say 1 to 10), the sender could rate the\n degree of urgency.\n\n There would be no precise defined meaning to","scope_keywords":["539","attribute","attributes","path","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 555","folder":"IETF/RFC-555","source":"IETF/RFC-555/RFC-555.txt","version":null}],"search_text":"IETF RFC 539 Network Working Group D. Crocker (UCLA-NMC)\nRequest For Comment: #539 J. Postel (UCLA-NMC)\nNIC 17644 July 9, 1973\nReferences: 524\n\n Thoughts on the Mail Protocol Proposed in RFC 524\n\nGenerally, we feel that the protocol is extremely rich. We also feel\nthat there are some minor and some major problems.\n\nThe minor points first:\n\n 1. and are not explained until the formal syntax. It\n would be more convenient, if they were explained sooner.\n\n 2. The Proposed is a bad thing, since it is the Telnet Go-\n Ahead, which should not be used by higher level protocols.\n\n 3. The default SIGNATURE should be the sign-on or ident of the\n author(s).\n\n 4. The Disposition INTERRUPT would be more useful if it had\n author/clerk-assigned \"levels\". Currently mail would be either\n urgent or not. With levels (say 1 to 10), the sender could rate the\n degree of urgency.\n\n There would be no precise defined meaning to 539 attribute attributes path signature subject nested-reference unchanged"},{"id":"IETF RFC 555","type":"specification","body":"IETF","designation":"RFC 555","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc555.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc555.txt","https://www.rfc-editor.org/rfc/rfc555.pdf"],"folder":"IETF/RFC-555","files":{"txt":{"path":"standards/IETF/RFC-555/RFC-555.txt","sha256":"6e9cc60ed943d26a3972160b1abf46044d421ecd585309d815b012112144ecde"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group James E. White (JEW)\nRequest for Comments: 555 SRI-ARC\nNIC: 17993 July 27, 1973\n\n Response to Critiques of the Proposed Mail Protocol\n\n A number of people have responded to my proposal for a Mail Protocol\n (JEW RFC 524 -- 17140,2:y). In the current RFC, I've attempted to\n collect and respond to the questions, complaints, and suggestions\n that various individuals in the Network community have offered. I\n intend to critique myself in a forthcoming RFC.\n\n I hope that dialog on the protocol proposal will continue, and that\n others will join in the discussion. I will respond via RFC to any\n additional critiques I receive (I hope there'll be many).\n\nI. QUESTIONS\n\n HOW DOES THE SERVER VERIFY AN ID?\n\n References:\n\n (DHC JBP RFC 539 -- 17644,3g:gy)\n\n Discussion:\n\n One postulates the existence of AT LEAST ONE host whose Mail\n server process implements the User Verification Fu","scope_keywords":["555","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 555 Network Working Group James E. White (JEW)\nRequest for Comments: 555 SRI-ARC\nNIC: 17993 July 27, 1973\n\n Response to Critiques of the Proposed Mail Protocol\n\n A number of people have responded to my proposal for a Mail Protocol\n (JEW RFC 524 -- 17140,2:y). In the current RFC, I've attempted to\n collect and respond to the questions, complaints, and suggestions\n that various individuals in the Network community have offered. I\n intend to critique myself in a forthcoming RFC.\n\n I hope that dialog on the protocol proposal will continue, and that\n others will join in the discussion. I will respond via RFC to any\n additional critiques I receive (I hope there'll be many).\n\nI. QUESTIONS\n\n HOW DOES THE SERVER VERIFY AN ID?\n\n References:\n\n (DHC JBP RFC 539 -- 17644,3g:gy)\n\n Discussion:\n\n One postulates the existence of AT LEAST ONE host whose Mail\n server process implements the User Verification Fu 555 delivery nested-reference unchanged"},{"id":"IETF RFC 561","type":"specification","body":"IETF","designation":"RFC 561","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc561.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc561.txt","https://www.rfc-editor.org/rfc/rfc561.pdf"],"folder":"IETF/RFC-561","files":{"txt":{"path":"standards/IETF/RFC-561/RFC-561.txt","sha256":"a3fb94ab3b1fb8229e9672abe4837bcd74cc8d94671d2b5d94b69c596ec37409"}},"tags":["nested-reference","unchanged"],"summary":"RFC # 561 Abhay Bhushan (AKB) MIT-DMCG\n NIC # 18516 Ken Pogran (KP) MIT-MULTICS\n Ray Tomlinson (RST) BBN-TENEX\n Jim White (JEW) SRI-ARC\n 5 September 73\n\n Standardizing Network Mail Headers\n\n \n\n One of the deficiences of the current FTP mail protocol is that\n it makes no provision for the explicit specification of such\n header information as author, title, and date. Many systems\n send that information, but each in a different format. One\n fairly serious result of this lack of standardization is that\n it's next to impossible for a system or user program to\n intelligently process incoming mail. \n\n Although the long-term solution to the problem is probably to\n add commands for specifying such information to the mail\n protocol command space (as suggested in RFC 524 -- 17140,), we\n hereby propose a more quickly implemented solution for the\n interim. \n\n We suggest that the text of network mail,","scope_keywords":["561","crl","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 680","folder":"IETF/RFC-680","source":"IETF/RFC-680/RFC-680.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null}],"search_text":"IETF RFC 561 RFC # 561 Abhay Bhushan (AKB) MIT-DMCG\n NIC # 18516 Ken Pogran (KP) MIT-MULTICS\n Ray Tomlinson (RST) BBN-TENEX\n Jim White (JEW) SRI-ARC\n 5 September 73\n\n Standardizing Network Mail Headers\n\n \n\n One of the deficiences of the current FTP mail protocol is that\n it makes no provision for the explicit specification of such\n header information as author, title, and date. Many systems\n send that information, but each in a different format. One\n fairly serious result of this lack of standardization is that\n it's next to impossible for a system or user program to\n intelligently process incoming mail. \n\n Although the long-term solution to the problem is probably to\n add commands for specifying such information to the mail\n protocol command space (as suggested in RFC 524 -- 17140,), we\n hereby propose a more quickly implemented solution for the\n interim. \n\n We suggest that the text of network mail, 561 crl key subject nested-reference unchanged"},{"id":"IETF RFC 753","type":"specification","body":"IETF","designation":"RFC 753","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc753.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc753.txt","https://www.rfc-editor.org/rfc/rfc753.pdf"],"folder":"IETF/RFC-753","files":{"txt":{"path":"standards/IETF/RFC-753/RFC-753.txt","sha256":"e0b15547e2552874a246c3ba188d4c5532c724ae5b37b9295525d84dd3032ea0"}},"tags":["nested-reference","unchanged"],"summary":"March 1979\n\nIEN: 85\nRFC: 753\n \n \n \n \n \n \n INTERNET MESSAGE PROTOCOL\n \n \n \n Jonathan B. Postel\n\n March 1979\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n \n (213) 822-1511\n\f\n\n , 31-Mar-79 19:50 JBP ;;;;\n\n[Page 0] Postel\n\f\n\nMarch 1979 \n Internet Message Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. The Internetwork Environment ................................. 2\n 1.4. Operation .................................................... 2\n 1.5. Interfaces ................................................... 3\n\n2. FUNCTIONAL DESCRIPTION .........","scope_keywords":["753","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 806","folder":"IETF/RFC-806","source":"IETF/RFC-806/RFC-806.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 841","folder":"IETF/RFC-841","source":"IETF/RFC-841/RFC-841.txt","version":null}],"search_text":"IETF RFC 753 March 1979\n\nIEN: 85\nRFC: 753\n \n \n \n \n \n \n INTERNET MESSAGE PROTOCOL\n \n \n \n Jonathan B. Postel\n\n March 1979\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n \n (213) 822-1511\n\f\n\n , 31-Mar-79 19:50 JBP ;;;;\n\n[Page 0] Postel\n\f\n\nMarch 1979 \n Internet Message Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. The Internetwork Environment ................................. 2\n 1.4. Operation .................................................... 2\n 1.5. Interfaces ................................................... 3\n\n2. FUNCTIONAL DESCRIPTION ......... 753 delivery nested-reference unchanged"},{"id":"IETF RFC 759","type":"specification","body":"IETF","designation":"RFC 759","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc759.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc759.txt","https://www.rfc-editor.org/rfc/rfc759.pdf"],"folder":"IETF/RFC-759","files":{"txt":{"path":"standards/IETF/RFC-759/RFC-759.txt","sha256":"4f2bb4d49989db466a8c4e9722b229f9c6d257e499213f716ce1dca6d80548cd"}},"tags":["nested-reference","unchanged"],"summary":"IEN: 113\nRFC: 759\n \n \n \n \n \n \n INTERNET MESSAGE PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1980\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\n\f\n\nAugust 1980 \n Internet Message Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. The Internetwork Environment ................................. 2\n 1.4. Model of Operation ........................................... 2\n 1.5. Interfaces ................................................... 4\n\n2. FUNCTIONAL DESCRIPTION ........................................... 5\n\n 2.1. Terminology","scope_keywords":["759","delivery","encryption","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 759 IEN: 113\nRFC: 759\n \n \n \n \n \n \n INTERNET MESSAGE PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1980\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\n\f\n\nAugust 1980 \n Internet Message Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. The Internetwork Environment ................................. 2\n 1.4. Model of Operation ........................................... 2\n 1.5. Interfaces ................................................... 4\n\n2. FUNCTIONAL DESCRIPTION ........................................... 5\n\n 2.1. Terminology 759 delivery encryption identification nested-reference unchanged"},{"id":"IETF RFC 767","type":"specification","body":"IETF","designation":"RFC 767","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc767.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc767.txt","https://www.rfc-editor.org/rfc/rfc767.pdf"],"folder":"IETF/RFC-767","files":{"txt":{"path":"standards/IETF/RFC-767/RFC-767.txt","sha256":"7c2e989cf90fd4bd964d53cd68ec87f45f793a1bb605962497f92b75d2ebaddf"}},"tags":["nested-reference","unchanged"],"summary":"RFC:767\n \n \n \n \n \n \n A STRUCTURED FORMAT FOR TRANSMISSION OF MULTI-MEDIA DOCUMENTS\n \n \n \n Jonathan B. Postel\n\n August 1980\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\n , 5-Sep-80 20:19 JBP ;;;;\n\n Postel\n\f\n\nAugust 1980 \n A Structured Format for Transmission of Multi-Media Documents\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. Terminology .................................................. 1\n 1.4. Document Description ......................................... 2\n 1.5. Other Work ...............................................","scope_keywords":["767","delivery","identification","presentation","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 767 RFC:767\n \n \n \n \n \n \n A STRUCTURED FORMAT FOR TRANSMISSION OF MULTI-MEDIA DOCUMENTS\n \n \n \n Jonathan B. Postel\n\n August 1980\n \n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\n , 5-Sep-80 20:19 JBP ;;;;\n\n Postel\n\f\n\nAugust 1980 \n A Structured Format for Transmission of Multi-Media Documents\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1. Motivation ................................................... 1\n 1.2. Scope ........................................................ 1\n 1.3. Terminology .................................................. 1\n 1.4. Document Description ......................................... 2\n 1.5. Other Work ............................................... 767 delivery identification presentation signature subject nested-reference unchanged"},{"id":"IETF RFC 8421","type":"specification","body":"IETF","designation":"RFC 8421","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8421.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8421.txt","https://www.rfc-editor.org/rfc/rfc8421.pdf"],"folder":"IETF/RFC-8421","files":{"txt":{"path":"standards/IETF/RFC-8421/RFC-8421.txt","sha256":"425046c25f13ba49e48bde16415eabee28317d35a3b923bd21b5ee745f5259b6"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidelines on how to make Interactive\n Connectivity Establishment (ICE) conclude faster in multihomed and\n IPv4/IPv6 dual-stack scenarios where broken paths exist. The\n provided guidelines are backward compatible with the original ICE\n specification (see RFC 5245).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8421.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust a","scope_keywords":["8421","http","https","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8445","folder":"IETF/RFC-8445","source":"IETF/RFC-8445/RFC-8445.txt","version":null}],"search_text":"IETF RFC 8421 This document provides guidelines on how to make Interactive\n Connectivity Establishment (ICE) conclude faster in multihomed and\n IPv4/IPv6 dual-stack scenarios where broken paths exist. The\n provided guidelines are backward compatible with the original ICE\n specification (see RFC 5245).\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8421.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust a 8421 http https license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5278","type":"specification","body":"IETF","designation":"RFC 5278","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5278.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5278.txt","https://www.rfc-editor.org/rfc/rfc5278.pdf"],"folder":"IETF/RFC-5278","files":{"txt":{"path":"standards/IETF/RFC-5278/RFC-5278.txt","sha256":"bb9812f53754c77662a6269bcb9880f5336d35f30886ab8f56c80ea6a4fc40bf"}},"tags":["nested-reference","unchanged"],"summary":"This document registers the Enumservice named \"vmsg\", which is used\n to facilitate the real-time routing of voice, video, and unified\n communications to a messaging system. This vmsg Enumservice\n registers three Enumservice types: \"voicemsg\", \"videomsg\", and\n \"unifmsg\". Each type also registers the subtypes \"sip\", \"sips\",\n \"http\", and \"https\", as well as the subtype \"tel\" for the \"voicemsg\"\n type.\n\nLivingood & Troshynski Standards Track [Page 1]\n\f\nRFC 5278 VMSG Enumservice July 2008","scope_keywords":["5278","http","https","profile"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 5278 This document registers the Enumservice named \"vmsg\", which is used\n to facilitate the real-time routing of voice, video, and unified\n communications to a messaging system. This vmsg Enumservice\n registers three Enumservice types: \"voicemsg\", \"videomsg\", and\n \"unifmsg\". Each type also registers the subtypes \"sip\", \"sips\",\n \"http\", and \"https\", as well as the subtype \"tel\" for the \"voicemsg\"\n type.\n\nLivingood & Troshynski Standards Track [Page 1]\n\f\nRFC 5278 VMSG Enumservice July 2008 5278 http https profile nested-reference unchanged"},{"id":"IETF RFC 5298","type":"specification","body":"IETF","designation":"RFC 5298","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5298.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5298.txt","https://www.rfc-editor.org/rfc/rfc5298.pdf"],"folder":"IETF/RFC-5298","files":{"txt":{"path":"standards/IETF/RFC-5298/RFC-5298.txt","sha256":"3d31dc43a2847aa472c94813410dd8933ba545d682f599becd8c6e37e38d7a5b"}},"tags":["nested-reference","unchanged"],"summary":"Protection and recovery are important features of service offerings\n in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n networks. Increasingly, MPLS and GMPLS networks are being extended\n from single domain scope to multi-domain environments.\n\n Various schemes and processes have been developed to establish Label\n Switched Paths (LSPs) in multi-domain environments. These are\n discussed in RFC 4726: \"A Framework for Inter-Domain Multiprotocol\n Label Switching Traffic Engineering\".\n\n This document analyzes the application of these techniques to\n protection and recovery in multi-domain networks. The main focus for\n this document is on establishing end-to-end diverse Traffic\n Engineering (TE) LSPs in multi-domain networks.\n\nTakeda, et al. Informational [Page 1]\n\f\nRFC 5298 Analysis of Inter-Domain LSP Recovery August 2008","scope_keywords":["5298","delivery","key","management","path","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 5298 Protection and recovery are important features of service offerings\n in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)\n networks. Increasingly, MPLS and GMPLS networks are being extended\n from single domain scope to multi-domain environments.\n\n Various schemes and processes have been developed to establish Label\n Switched Paths (LSPs) in multi-domain environments. These are\n discussed in RFC 4726: \"A Framework for Inter-Domain Multiprotocol\n Label Switching Traffic Engineering\".\n\n This document analyzes the application of these techniques to\n protection and recovery in multi-domain networks. The main focus for\n this document is on establishing end-to-end diverse Traffic\n Engineering (TE) LSPs in multi-domain networks.\n\nTakeda, et al. Informational [Page 1]\n\f\nRFC 5298 Analysis of Inter-Domain LSP Recovery August 2008 5298 delivery key management path risk nested-reference unchanged"},{"id":"IETF RFC 532","type":"specification","body":"IETF","designation":"RFC 532","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc532.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc532.txt","https://www.rfc-editor.org/rfc/rfc532.pdf"],"folder":"IETF/RFC-532","files":{"txt":{"path":"standards/IETF/RFC-532/RFC-532.txt","sha256":"8c17a5b232b756f96dfa05e03f8e30dc9410b0352d4074b9646958a7b8c9be2a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Merryman\nRequest for Comments: 532 UCSD-CC\nNIC: 17451 12 July 1973\n\n The UCSD-CC Server-FTP Facility\n\n1.0 Introduction\n\n The UCSD Computer Center is a service site that must support itself\n by charging for the usage of its facilities. Because of this, the\n prospective user of our Server-FTP must supply a valid usercode\n (USER) and password (PASS) before any further FTP commands are\n accepted.\n\n Through FTP, you are allowed to access or store files on our disk or\n on any of our 7 or 9-track tape drives. Each individual file\n transfer is handled by a separate process on the B6700 and the user\n is charged for the processor, I/O, core, and (if any) tape charges\n incurred by this process (note that these charges are quite minimal).\n Each of these transfer processes is given a separate \"job\" number and\n is therefore billed separately for each transfer by our accounting","scope_keywords":["532","attribute","attributes","crl","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 532 Network Working Group R. Merryman\nRequest for Comments: 532 UCSD-CC\nNIC: 17451 12 July 1973\n\n The UCSD-CC Server-FTP Facility\n\n1.0 Introduction\n\n The UCSD Computer Center is a service site that must support itself\n by charging for the usage of its facilities. Because of this, the\n prospective user of our Server-FTP must supply a valid usercode\n (USER) and password (PASS) before any further FTP commands are\n accepted.\n\n Through FTP, you are allowed to access or store files on our disk or\n on any of our 7 or 9-track tape drives. Each individual file\n transfer is handled by a separate process on the B6700 and the user\n is charged for the processor, I/O, core, and (if any) tape charges\n incurred by this process (note that these charges are quite minimal).\n Each of these transfer processes is given a separate \"job\" number and\n is therefore billed separately for each transfer by our accounting 532 attribute attributes crl path nested-reference unchanged"},{"id":"legal:2024-2977","type":"legal_regulation","act_id":"2024-2977","title":"PID and electronic attestations of attributes (lifecycle)","celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/acccd446-b1e0-11ef-acb1-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2024-2977/2024-2977.html","sha256":"e6823fd65f11dc56c803daac4e5e5fde5c6404b0fad6924f80bd54264bcb3e94","size":82808},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/acccd446-b1e0-11ef-acb1-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2024-2977/2024-2977.pdf","sha256":"d1cb63b80d86706d7c6d604668b872abe5fd5a3689bfd3c26ad683801f9b5365","size":586855}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards person identification data and electronic attestations of attributes issued to European Digital Identity Wallets The European Digital Identity Framework established by Regulation (EU) No 910/2014, is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) as the cornerstone of the framework, it aims at facilitating access to services across Member States, while ensuring the protection of personal data and privacy. ‘wallet user’ means a user who is in control of the wallet unit;","scope_keywords":["access","across","attestation","attestations","attributes","certificates","council","data","digital","electronic","european","framework","identification","identity","member","parliament","person","personal","regulation","services","states","union","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.028032+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards person identification data and electronic attestations of attributes issued to European Digital Identity Wallets The European Digital Identity Framework established by Regulation (EU) No 910/2014, is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) as the cornerstone of the framework, it aims at facilitating access to services across Member States, while ensuring the protection of personal data and privacy. ‘wallet user’ means a user who is in control of the wallet unit; access across attestation attestations attributes certificates council data digital electronic european framework identification identity member parliament person personal regulation services states union wallet wallets"},{"id":"IETF RFC 5328","type":"specification","body":"IETF","designation":"RFC 5328","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5328.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5328.txt","https://www.rfc-editor.org/rfc/rfc5328.pdf"],"folder":"IETF/RFC-5328","files":{"txt":{"path":"standards/IETF/RFC-5328/RFC-5328.txt","sha256":"8d55289693168282b03eccfd9bd95a2917fa22808441245d20f93b82d1ca3646"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a Uniform Resource Name (URN) namespace for\n the Digital Video Broadcasting Project (DVB) for naming persistent\n resources defined within DVB standards. Example resources include\n technical documents and specifications, eXtensible Markup Language\n (XML) Schemas, classification schemes, XML Document Type Definitions\n (DTDs), namespaces, style sheets, media assets, and other types of\n resources produced or managed by DVB.","scope_keywords":["5328","delivery","http","registered","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5328 This document describes a Uniform Resource Name (URN) namespace for\n the Digital Video Broadcasting Project (DVB) for naming persistent\n resources defined within DVB standards. Example resources include\n technical documents and specifications, eXtensible Markup Language\n (XML) Schemas, classification schemes, XML Document Type Definitions\n (DTDs), namespaces, style sheets, media assets, and other types of\n resources produced or managed by DVB. 5328 delivery http registered validation nested-reference unchanged"},{"id":"IETF RFC 533","type":"specification","body":"IETF","designation":"RFC 533","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc533.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc533.txt","https://www.rfc-editor.org/rfc/rfc533.pdf"],"folder":"IETF/RFC-533","files":{"txt":{"path":"standards/IETF/RFC-533/RFC-533.txt","sha256":"ea16c63c6dbfa7b6e14533e0fc929fc51870198ff57f6db442ed09ef9e3d9a32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David Walden\nRFC # 533 BBN-NET\nNIC # 17452 July 17, 1973\n\n MESSAGE-ID NUMBERS\n\n It has been noted that the IMP message format (specified in BBN\nReport 1822) constrains network users to low throughputs if messages are\nto be uniquely identified via the link number. We have recently\nimplemented a change in the IMP/Host protocol which alleviates this\ndifficulty. The link field in the IMP/Host and Host/IMP leaders has\nbeen extended to the right by four bits (in other words, it now uses\nbits 17 to 28 of the leader), and the name of the link field has been\nchanged to the message-id field. We expect this field to be used to\nuniquely identify messages between the IMPs and the Hosts. All 12 bits\nin the message-id will be returned to the Host in RFNMs, INCOMPLETE\nTRANSMISSIONs, etc. Note that no ordering is implied by the use of the\nmessage-id field.\n\n Given that the Host/Host","scope_keywords":["533"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 534","folder":"IETF/RFC-534","source":"IETF/RFC-534/RFC-534.txt","version":null}],"search_text":"IETF RFC 533 Network Working Group David Walden\nRFC # 533 BBN-NET\nNIC # 17452 July 17, 1973\n\n MESSAGE-ID NUMBERS\n\n It has been noted that the IMP message format (specified in BBN\nReport 1822) constrains network users to low throughputs if messages are\nto be uniquely identified via the link number. We have recently\nimplemented a change in the IMP/Host protocol which alleviates this\ndifficulty. The link field in the IMP/Host and Host/IMP leaders has\nbeen extended to the right by four bits (in other words, it now uses\nbits 17 to 28 of the leader), and the name of the link field has been\nchanged to the message-id field. We expect this field to be used to\nuniquely identify messages between the IMPs and the Hosts. All 12 bits\nin the message-id will be returned to the Host in RFNMs, INCOMPLETE\nTRANSMISSIONs, etc. Note that no ordering is implied by the use of the\nmessage-id field.\n\n Given that the Host/Host 533 nested-reference unchanged"},{"id":"IETF RFC 5333","type":"specification","body":"IETF","designation":"RFC 5333","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5333.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5333.txt","https://www.rfc-editor.org/rfc/rfc5333.pdf"],"folder":"IETF/RFC-5333","files":{"txt":{"path":"standards/IETF/RFC-5333/RFC-5333.txt","sha256":"21f819208d2a6133279335e5b22a7cdf01ec3bae55772b0324225fb59d5a0c85"}},"tags":["nested-reference","unchanged"],"summary":"This document registers Enumservices for Internet calendaring.\n Specifically, this document focuses on Enumservices for scheduling\n with iMIP (iCalendar Message-Based Interoperability Protocol) and for\n accessing Internet calendaring information with CalDAV (Calendaring\n Extensions to WebDAV).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (h","scope_keywords":["5333","http","https","license","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null}],"search_text":"IETF RFC 5333 This document registers Enumservices for Internet calendaring.\n Specifically, this document focuses on Enumservices for scheduling\n with iMIP (iCalendar Message-Based Interoperability Protocol) and for\n accessing Internet calendaring information with CalDAV (Calendaring\n Extensions to WebDAV).\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright and License Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (h 5333 http https license policy subject trust nested-reference unchanged"},{"id":"IETF RFC 5369","type":"specification","body":"IETF","designation":"RFC 5369","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5369.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5369.txt","https://www.rfc-editor.org/rfc/rfc5369.pdf"],"folder":"IETF/RFC-5369","files":{"txt":{"path":"standards/IETF/RFC-5369/RFC-5369.txt","sha256":"0c1a555fc0c5c0fdcf8c36dc8d0b9a6acad2d1fd5cad781b6ba8a03e7b3c6ec8"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for transcoding with SIP. This\n framework includes how to discover the need for transcoding services\n in a session and how to invoke those transcoding services. Two\n models for transcoding services invocation are discussed: the\n conference bridge model and the third-party call control model. Both\n models meet the requirements for SIP regarding transcoding services\n invocation to support deaf, hard of hearing, and speech-impaired\n individuals.","scope_keywords":["5369"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null}],"search_text":"IETF RFC 5369 This document defines a framework for transcoding with SIP. This\n framework includes how to discover the need for transcoding services\n in a session and how to invoke those transcoding services. Two\n models for transcoding services invocation are discussed: the\n conference bridge model and the third-party call control model. Both\n models meet the requirements for SIP regarding transcoding services\n invocation to support deaf, hard of hearing, and speech-impaired\n individuals. 5369 nested-reference unchanged"},{"id":"IETF RFC 5370","type":"specification","body":"IETF","designation":"RFC 5370","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5370.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5370.txt","https://www.rfc-editor.org/rfc/rfc5370.pdf"],"folder":"IETF/RFC-5370","files":{"txt":{"path":"standards/IETF/RFC-5370/RFC-5370.txt","sha256":"0bea025cc0caa272e51dd333a5b8c7a970a1f36e108d8180b4b07987748d6e0e"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how to invoke transcoding services using the\n conference bridge model. This way of invocation meets the\n requirements for SIP regarding transcoding services invocation to\n support deaf, hard of hearing, and speech-impaired individuals.","scope_keywords":["5370","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7092","folder":"IETF/RFC-7092","source":"IETF/RFC-7092/RFC-7092.txt","version":null}],"search_text":"IETF RFC 5370 This document describes how to invoke transcoding services using the\n conference bridge model. This way of invocation meets the\n requirements for SIP regarding transcoding services invocation to\n support deaf, hard of hearing, and speech-impaired individuals. 5370 key subject nested-reference unchanged"},{"id":"IETF RFC 5391","type":"specification","body":"IETF","designation":"RFC 5391","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5391.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5391.txt","https://www.rfc-editor.org/rfc/rfc5391.pdf"],"folder":"IETF/RFC-5391","files":{"txt":{"path":"standards/IETF/RFC-5391/RFC-5391.txt","sha256":"74f9e18257f41018fb76286117e6bbaaa41cfb9035c176d9af27c6d3c8bc04b0"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a Real-time Transport Protocol (RTP) payload\n format to be used for the ITU Telecommunication Standardization\n Sector (ITU-T) G.711.1 audio codec. Two media type registrations are\n also included.\n\nSollaud Standards Track [Page 1]\n\f\nRFC 5391 RTP Payload Format for G.711.1 November 2008","scope_keywords":["5391","algorithm","http","key","license","profile","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 5391 This document specifies a Real-time Transport Protocol (RTP) payload\n format to be used for the ITU Telecommunication Standardization\n Sector (ITU-T) G.711.1 audio codec. Two media type registrations are\n also included.\n\nSollaud Standards Track [Page 1]\n\f\nRFC 5391 RTP Payload Format for G.711.1 November 2008 5391 algorithm http key license profile subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 5396","type":"specification","body":"IETF","designation":"RFC 5396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5396.txt","https://www.rfc-editor.org/rfc/rfc5396.pdf"],"folder":"IETF/RFC-5396","files":{"txt":{"path":"standards/IETF/RFC-5396/RFC-5396.txt","sha256":"693561442e4b7a1e6b0016aa109c9285af7eeb7734fa88e747912a685258ca8a"}},"tags":["nested-reference","unchanged"],"summary":"A textual representation for Autonomous System (AS) numbers is\n defined as the decimal value of the AS number. This textual\n representation is to be used by all documents, systems, and user\n interfaces referring to AS numbers.","scope_keywords":["5396","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9224","folder":"IETF/RFC-9224","source":"IETF/RFC-9224/RFC-9224.txt","version":null}],"search_text":"IETF RFC 5396 A textual representation for Autonomous System (AS) numbers is\n defined as the decimal value of the AS number. This textual\n representation is to be used by all documents, systems, and user\n interfaces referring to AS numbers. 5396 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 542","type":"specification","body":"IETF","designation":"RFC 542","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc542.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc542.txt","https://www.rfc-editor.org/rfc/rfc542.pdf"],"folder":"IETF/RFC-542","files":{"txt":{"path":"standards/IETF/RFC-542/RFC-542.txt","sha256":"845f120129b00549c7fa4630d057f32e6a2bf5378d6b809346af4f1d4fadc619"}},"tags":["nested-reference","unchanged"],"summary":"File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\nNancy J. Neigus See Also: RFCs 354, 454, 495\nBolt Beranek and Newman, Inc.\nCambridge, Mass.\n\n File Transfer Protocol for the ARPA Network\f\n\n File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\n PREFACE\n\nThis document is the result of several months discussion via RFC\n(relevant numbers are 430, 448, 454, 463, 468, 478, 480), followed by a\nmeeting of the FTP committee at BBN on March 16, followed by further\ncommunication among committee members. There are a considerable number\nof changes for the last \"official\" version, see RFCs 354, 385, but the\ngross structure remains the same. The places to look for differences\nare (1) in the definitions pf types and modes, (2) in the specification\nof the data connection and data sockets, (3) in the command-reply\nsequences, (4) in the functions dependent on the TELNET protocol (FTP\nhas ","scope_keywords":["542","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0542","folder":"IETF/RFC-0542","source":"IETF/RFC-0542/RFC-0542.txt","version":null},{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 555","folder":"IETF/RFC-555","source":"IETF/RFC-555/RFC-555.txt","version":null},{"body":"IETF","designation":"RFC 614","folder":"IETF/RFC-614","source":"IETF/RFC-614/RFC-614.txt","version":null},{"body":"IETF","designation":"RFC 624","folder":"IETF/RFC-624","source":"IETF/RFC-624/RFC-624.txt","version":null},{"body":"IETF","designation":"RFC 640","folder":"IETF/RFC-640","source":"IETF/RFC-640/RFC-640.txt","version":null},{"body":"IETF","designation":"RFC 683","folder":"IETF/RFC-683","source":"IETF/RFC-683/RFC-683.txt","version":null},{"body":"IETF","designation":"RFC 686","folder":"IETF/RFC-686","source":"IETF/RFC-686/RFC-686.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 775","folder":"IETF/RFC-775","source":"IETF/RFC-775/RFC-775.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 542 File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\nNancy J. Neigus See Also: RFCs 354, 454, 495\nBolt Beranek and Newman, Inc.\nCambridge, Mass.\n\n File Transfer Protocol for the ARPA Network\f\n\n File Transfer Protocol\n (Aug. 12, 1973)\n RFC 542 NIC 17759\n\n PREFACE\n\nThis document is the result of several months discussion via RFC\n(relevant numbers are 430, 448, 454, 463, 468, 478, 480), followed by a\nmeeting of the FTP committee at BBN on March 16, followed by further\ncommunication among committee members. There are a considerable number\nof changes for the last \"official\" version, see RFCs 354, 385, but the\ngross structure remains the same. The places to look for differences\nare (1) in the definitions pf types and modes, (2) in the specification\nof the data connection and data sockets, (3) in the command-reply\nsequences, (4) in the functions dependent on the TELNET protocol (FTP\nhas  542 path nested-reference unchanged"},{"id":"IETF RFC 614","type":"specification","body":"IETF","designation":"RFC 614","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc614.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc614.txt","https://www.rfc-editor.org/rfc/rfc614.pdf"],"folder":"IETF/RFC-614","files":{"txt":{"path":"standards/IETF/RFC-614/RFC-614.txt","sha256":"6619cd0c6f72c731c103f0e72f0b32818973647e5b1acabed3b674250f19b50f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Pogran (MIT-Multics)\nRequest for Comments: 614 N. Neigus (BBN-NET)\nNIC #21530 Jan 1974\nReferences: RFC #607, RFC #542\n\n Response to RFC 607, \"Comments on the File Transfer Protocol\"\n\nMark Krilanovich and George Gregg have pointed out a number of \"sticky\"\nissues in the current File Transfer Protocol. Although we don't agree\nwith all of their proposed protocol modifications, we do feel that each\nof the points they have raised should be given some thought by everyone\nconcerned about FTP. Each numbered paragraph in the discussion below is a\ncomment on the identically-numbered paragraph in RFC 607.\n\n1. Instructions to the Server to be \"passive\" are defined to apply only\nto the next single file transfer operation, after which the Server\nreverts to active mode. RFC 607 does, however, point out a drawback in\nthe present specification, in that there is no way for a user t","scope_keywords":["614","algorithm","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 614 Network Working Group K. Pogran (MIT-Multics)\nRequest for Comments: 614 N. Neigus (BBN-NET)\nNIC #21530 Jan 1974\nReferences: RFC #607, RFC #542\n\n Response to RFC 607, \"Comments on the File Transfer Protocol\"\n\nMark Krilanovich and George Gregg have pointed out a number of \"sticky\"\nissues in the current File Transfer Protocol. Although we don't agree\nwith all of their proposed protocol modifications, we do feel that each\nof the points they have raised should be given some thought by everyone\nconcerned about FTP. Each numbered paragraph in the discussion below is a\ncomment on the identically-numbered paragraph in RFC 607.\n\n1. Instructions to the Server to be \"passive\" are defined to apply only\nto the next single file transfer operation, after which the Server\nreverts to active mode. RFC 607 does, however, point out a drawback in\nthe present specification, in that there is no way for a user t 614 algorithm attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 624","type":"specification","body":"IETF","designation":"RFC 624","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc624.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc624.txt","https://www.rfc-editor.org/rfc/rfc624.pdf"],"folder":"IETF/RFC-624","files":{"txt":{"path":"standards/IETF/RFC-624/RFC-624.txt","sha256":"62589646c8bd56d783064660a117344ea1f134c97d844e51a834469079fc583f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mark Krilanovich (UCSB)\nRequest for Comments: 624 George Gregg (UCSB)\nNIC #22054 Wayne Hathaway (AMES-67)\nreferences: RFC 542 Jim White (SRI-ARC)\nobsoletes: RFC 607 Feb 1974\n \n \n Comments on the File Transfer Protocol\n\nThis document replaces RFC 607, which was inadvertently released\nwhile still in rough draft form. It would be appreciated if RFC 607\nwere disregarded, and this document considered the accurate statement\nof the authors' opinions.\n\nThere are several aspects of the File Transfer Protocol of RFC\n542 that constitute serious drawbacks. Some of these are quite basic\nin nature, and imply substantial design changes; these will be\ndiscussed in a later RFC. Others could be remedied with very little\neffort, and this should be done as soon as possible.\n\nFollowing is a list of those problems that can be easily solved,\ntogether with their proposed solutions:\n\n1. Onc","scope_keywords":["624","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 624 Network Working Group Mark Krilanovich (UCSB)\nRequest for Comments: 624 George Gregg (UCSB)\nNIC #22054 Wayne Hathaway (AMES-67)\nreferences: RFC 542 Jim White (SRI-ARC)\nobsoletes: RFC 607 Feb 1974\n \n \n Comments on the File Transfer Protocol\n\nThis document replaces RFC 607, which was inadvertently released\nwhile still in rough draft form. It would be appreciated if RFC 607\nwere disregarded, and this document considered the accurate statement\nof the authors' opinions.\n\nThere are several aspects of the File Transfer Protocol of RFC\n542 that constitute serious drawbacks. Some of these are quite basic\nin nature, and imply substantial design changes; these will be\ndiscussed in a later RFC. Others could be remedied with very little\neffort, and this should be done as soon as possible.\n\nFollowing is a list of those problems that can be easily solved,\ntogether with their proposed solutions:\n\n1. Onc 624 path subject nested-reference unchanged"},{"id":"IETF RFC 640","type":"specification","body":"IETF","designation":"RFC 640","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc640.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc640.txt","https://www.rfc-editor.org/rfc/rfc640.pdf"],"folder":"IETF/RFC-640","files":{"txt":{"path":"standards/IETF/RFC-640/RFC-640.txt","sha256":"496cf344dfef322495ff6d39c1e018c18b774d3d715f0f0ee0f23d2491e3eac1"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 640 JBP NJN 5-JUN-74 16:07 30843\n Revised FTP Reply Codes\n\n Jon Postel\n 19 JUN 75\n\n Revised FTP Reply Codes 1\n\n This document describes a revised set of reply codes for the File\n Transfer Protocol. 2\n\n The aim of this revision is to satisfy the goal of using reply\n codes to enable the command issuing process to easily determine\n the outcome of each command. The user protocol interpreter should\n be able to determine the success or failure of a command by\n examining the first digit of the reply code. 3\n\n An important change in the sequencing of commands and replies\n which may not be obvious in the following documents concerns the\n establishment of the data connection. 4\n\n In the previous FTP specifications when an actual transfer\n command (STOR, RETR, APPE, LIST, NLIST, MLFL) was issued the\n preliminary reply was sent after the data connection was\n established. This presented a pr","scope_keywords":["640"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 686","folder":"IETF/RFC-686","source":"IETF/RFC-686/RFC-686.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 775","folder":"IETF/RFC-775","source":"IETF/RFC-775/RFC-775.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 640 NWG/RFC# 640 JBP NJN 5-JUN-74 16:07 30843\n Revised FTP Reply Codes\n\n Jon Postel\n 19 JUN 75\n\n Revised FTP Reply Codes 1\n\n This document describes a revised set of reply codes for the File\n Transfer Protocol. 2\n\n The aim of this revision is to satisfy the goal of using reply\n codes to enable the command issuing process to easily determine\n the outcome of each command. The user protocol interpreter should\n be able to determine the success or failure of a command by\n examining the first digit of the reply code. 3\n\n An important change in the sequencing of commands and replies\n which may not be obvious in the following documents concerns the\n establishment of the data connection. 4\n\n In the previous FTP specifications when an actual transfer\n command (STOR, RETR, APPE, LIST, NLIST, MLFL) was issued the\n preliminary reply was sent after the data connection was\n established. This presented a pr 640 nested-reference unchanged"},{"id":"IETF RFC 775","type":"specification","body":"IETF","designation":"RFC 775","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc775.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc775.txt","https://www.rfc-editor.org/rfc/rfc775.pdf"],"folder":"IETF/RFC-775","files":{"txt":{"path":"standards/IETF/RFC-775/RFC-775.txt","sha256":"076fc6c00539d927ea364941e05d3c5ae4e7d41d43e3bc1da5e45b4aacef41ed"}},"tags":["nested-reference","unchanged"],"summary":"RFC 775 Directory oriented FTP commands Page 1\n\n DIRECTORY ORIENTED FTP COMMANDS\n\n David Mankins (dm@bbn-unix)\n Dan Franklin (dan@bbn-unix)\n A. D. Owen (ADOwen@bbnd)\n\n As a part of the Remote Site Maintenance (RSM) project for ARPA,\n BBN has installed and maintains the software of several DEC PDP-\n 11s running the Unix operating system. Since Unix has a tree-\n like directory structure, in which directories are as easy to\n manipulate as ordinary files, we have found it convenient to\n expand the FTP servers on these machines to include commands\n which deal with the creation of directories. Since there are\n other hosts on the ARPA net which have tree-like directories,\n including Tops-20 and Multics, we have tried to make these\n commands as general as possible.\n\n We have added four commands to our server:\n\n XMKD child\n Make a directory with the name \"child\".\n\n XRMD child\n Remove the director","scope_keywords":["775","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null}],"search_text":"IETF RFC 775 RFC 775 Directory oriented FTP commands Page 1\n\n DIRECTORY ORIENTED FTP COMMANDS\n\n David Mankins (dm@bbn-unix)\n Dan Franklin (dan@bbn-unix)\n A. D. Owen (ADOwen@bbnd)\n\n As a part of the Remote Site Maintenance (RSM) project for ARPA,\n BBN has installed and maintains the software of several DEC PDP-\n 11s running the Unix operating system. Since Unix has a tree-\n like directory structure, in which directories are as easy to\n manipulate as ordinary files, we have found it convenient to\n expand the FTP servers on these machines to include commands\n which deal with the creation of directories. Since there are\n other hosts on the ARPA net which have tree-like directories,\n including Tops-20 and Multics, we have tried to make these\n commands as general as possible.\n\n We have added four commands to our server:\n\n XMKD child\n Make a directory with the name \"child\".\n\n XRMD child\n Remove the director 775 path nested-reference unchanged"},{"id":"IETF RFC 5443","type":"specification","body":"IETF","designation":"RFC 5443","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5443.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5443.txt","https://www.rfc-editor.org/rfc/rfc5443.pdf"],"folder":"IETF/RFC-5443","files":{"txt":{"path":"standards/IETF/RFC-5443/RFC-5443.txt","sha256":"823c6bb8067b97960bcdf33e6d2721ac96832d97b0d54183e8c288c890d746d0"}},"tags":["nested-reference","unchanged"],"summary":"In certain networks, there is dependency on the edge-to-edge Label\n Switched Paths (LSPs) setup by the Label Distribution Protocol (LDP),\n e.g., networks that are used for Multiprotocol Label Switching (MPLS)\n Virtual Private Network (VPN) applications. For such applications,\n it is not possible to rely on Internet Protocol (IP) forwarding if\n the MPLS LSP is not operating appropriately. Blackholing of labeled\n traffic can occur in situations where the Interior Gateway Protocol\n (IGP) is operational on a link on which LDP is not. While the link\n could still be used for IP forwarding, it is not useful for MPLS\n forwarding, for example, MPLS VPN applications or Border Gateway\n Protocol (BGP) route-free cores. This document describes a mechanism\n to avoid traffic loss due to this condition without introducing any\n protocol changes.","scope_keywords":["5443","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5919","folder":"IETF/RFC-5919","source":"IETF/RFC-5919/RFC-5919.txt","version":null}],"search_text":"IETF RFC 5443 In certain networks, there is dependency on the edge-to-edge Label\n Switched Paths (LSPs) setup by the Label Distribution Protocol (LDP),\n e.g., networks that are used for Multiprotocol Label Switching (MPLS)\n Virtual Private Network (VPN) applications. For such applications,\n it is not possible to rely on Internet Protocol (IP) forwarding if\n the MPLS LSP is not operating appropriately. Blackholing of labeled\n traffic can occur in situations where the Interior Gateway Protocol\n (IGP) is operational on a link on which LDP is not. While the link\n could still be used for IP forwarding, it is not useful for MPLS\n forwarding, for example, MPLS VPN applications or Border Gateway\n Protocol (BGP) route-free cores. This document describes a mechanism\n to avoid traffic loss due to this condition without introducing any\n protocol changes. 5443 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5493","type":"specification","body":"IETF","designation":"RFC 5493","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5493.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5493.txt","https://www.rfc-editor.org/rfc/rfc5493.pdf"],"folder":"IETF/RFC-5493","files":{"txt":{"path":"standards/IETF/RFC-5493/RFC-5493.txt","sha256":"54117d63ff76d7d1dc4c8113b449dbfcce22eb9cbc002899397ff9dfd1184e9a"}},"tags":["nested-reference","unchanged"],"summary":"From a carrier perspective, the possibility of turning a permanent\n connection (PC) into a soft permanent connection (SPC) and vice\n versa, without actually affecting data plane traffic being carried\n over it, is a valuable option. In other terms, such operation can be\n seen as a way of transferring the ownership and control of an\n existing and in-use data plane connection between the management\n plane and the control plane, leaving its data plane state untouched.\n\n This memo sets out the requirements for such procedures within a\n Generalized Multiprotocol Label Switching (GMPLS) network.","scope_keywords":["5493","attribute","attributes","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"IETF RFC 5493 From a carrier perspective, the possibility of turning a permanent\n connection (PC) into a soft permanent connection (SPC) and vice\n versa, without actually affecting data plane traffic being carried\n over it, is a valuable option. In other terms, such operation can be\n seen as a way of transferring the ownership and control of an\n existing and in-use data plane connection between the management\n plane and the control plane, leaving its data plane state untouched.\n\n This memo sets out the requirements for such procedures within a\n Generalized Multiprotocol Label Switching (GMPLS) network. 5493 attribute attributes http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 552","type":"specification","body":"IETF","designation":"RFC 552","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc552.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc552.txt","https://www.rfc-editor.org/rfc/rfc552.pdf"],"folder":"IETF/RFC-552","files":{"txt":{"path":"standards/IETF/RFC-552/RFC-552.txt","sha256":"d51a2df8244a8cefcc737662d5ef46d9b7012ffd06ba7d69345118658bab76ee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Buz Owen\nRFC # 552 SDAC-TIP\nNIC # 17809 13 July, 1973\n\n Single access to Standard Protocols\n\nIsn't the idea of a single access protocol simple enough that one could\nbe specified, and a socket reserved for it, before the proposed mail\nprotocol becomes official? The result would be that MP could be the\nfirst protocol implemented under UULP (or whatever it is to be called),\nand the other protocols could be \"moved\" as soon as any problems in the\nofficial specifications could be worked out, and at the convenience of\nimplementors.\n\nThe single access protocol might have the following commands:\n\n USER\n PASS\n ACCT\n MAIL\n FTP\n RJS\n DRS (?)\n HELP (?)\n BYE\n\nfollowing Jim White's idea of nested command and reply spaces.\n\nThis doesn't address the question of \"what is free\", or of the\ninterrelationships between the various protocols, but it doesn't make\nthose problem any worse, on","scope_keywords":["552"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 555","folder":"IETF/RFC-555","source":"IETF/RFC-555/RFC-555.txt","version":null}],"search_text":"IETF RFC 552 Network Working Group Buz Owen\nRFC # 552 SDAC-TIP\nNIC # 17809 13 July, 1973\n\n Single access to Standard Protocols\n\nIsn't the idea of a single access protocol simple enough that one could\nbe specified, and a socket reserved for it, before the proposed mail\nprotocol becomes official? The result would be that MP could be the\nfirst protocol implemented under UULP (or whatever it is to be called),\nand the other protocols could be \"moved\" as soon as any problems in the\nofficial specifications could be worked out, and at the convenience of\nimplementors.\n\nThe single access protocol might have the following commands:\n\n USER\n PASS\n ACCT\n MAIL\n FTP\n RJS\n DRS (?)\n HELP (?)\n BYE\n\nfollowing Jim White's idea of nested command and reply spaces.\n\nThis doesn't address the question of \"what is free\", or of the\ninterrelationships between the various protocols, but it doesn't make\nthose problem any worse, on 552 nested-reference unchanged"},{"id":"IETF RFC 556","type":"specification","body":"IETF","designation":"RFC 556","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc556.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc556.txt","https://www.rfc-editor.org/rfc/rfc556.pdf"],"folder":"IETF/RFC-556","files":{"pdf":{"path":"standards/IETF/RFC-556/RFC-556.pdf","sha256":"90dfc5b6771a3b85381033108286f09dfcceb41abff39874a3dee468f02cc9f9"},"txt":{"path":"standards/IETF/RFC-556/RFC-556.txt","sha256":"26d91e709ce71ec697e6c447413b3c689e82fccb8dce9e7733f3b809c404d7a0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 556 BBN-NET\nUpdates: 538 13 August 1973\nNIC: 18376\n\n Traffic Statistics (July 1973)\n\n Attached are the Host Traffic statistics for the month of July 1973.\n\n AAM/jm\n Encl.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JULY 1973\n\n INTER- INTRA- AVG.DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 308670 80817 389487\nUCLA HOST 1 1575798 155225 1731023\n -------- -------- --------\n 1884468 236042 2120510 60789 31\n\nSRI HOST 0 3958512 11320100 15278610\nSRI HOST 1 262939 25701 288640\n -------- -------- --------\n 4221451 11345800 155667250 136176 31\n\nUCSB HOST 0 1568426 600854 2169280\nUCSB HOST 1 334498 6544 341042\n -------- -------- --------\n 1902924 607398 2510322 61385 31\n\nUTAH HOST 0 735892 60049 785941 23738 31\n\nBBN HOST 0 8 41136 41144\nBBN HOST 1 4550530 636982 5187512\nBBN HOST 2 37255 24758 62013\nBBN HOST 3 126867 133512 260379\n ---","scope_keywords":["556"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 566","folder":"IETF/RFC-566","source":"IETF/RFC-566/RFC-566.txt","version":null}],"search_text":"IETF RFC 556 Network Working Group A. McKenzie\nRequest for Comments: 556 BBN-NET\nUpdates: 538 13 August 1973\nNIC: 18376\n\n Traffic Statistics (July 1973)\n\n Attached are the Host Traffic statistics for the month of July 1973.\n\n AAM/jm\n Encl.\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n JULY 1973\n\n INTER- INTRA- AVG.DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 308670 80817 389487\nUCLA HOST 1 1575798 155225 1731023\n -------- -------- --------\n 1884468 236042 2120510 60789 31\n\nSRI HOST 0 3958512 11320100 15278610\nSRI HOST 1 262939 25701 288640\n -------- -------- --------\n 4221451 11345800 155667250 136176 31\n\nUCSB HOST 0 1568426 600854 2169280\nUCSB HOST 1 334498 6544 341042\n -------- -------- --------\n 1902924 607398 2510322 61385 31\n\nUTAH HOST 0 735892 60049 785941 23738 31\n\nBBN HOST 0 8 41136 41144\nBBN HOST 1 4550530 636982 5187512\nBBN HOST 2 37255 24758 62013\nBBN HOST 3 126867 133512 260379\n --- 556 nested-reference unchanged"},{"id":"IETF RFC 566","type":"specification","body":"IETF","designation":"RFC 566","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc566.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc566.txt","https://www.rfc-editor.org/rfc/rfc566.pdf"],"folder":"IETF/RFC-566","files":{"txt":{"path":"standards/IETF/RFC-566/RFC-566.txt","sha256":"4b26b22637725f2b8733f139b78743260afc6d2e8255142a0abc7c8d661bb3f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 566 BBN-NET\nNIC: 18801 4 September 1973\nUpdates: RFC 556\n\n Traffic Statistics (August 1973)\n\n Attached are the Hosts traffic statistics for the month of August\n 1973.\n\n AAM/jm\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n AUGUST 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 302287 92769 395056\n UCLA HOST 1 2246832 182154 2428986\n UCLA HOST 2 454 66247 66701\n -------- -------- --------\n 2549573 341170 2890743 82244 31\n\n SRI HOST 0 5201216 6982664 12183880\n SRI HOST 1 369316 18453 387769\n -------- -------- --------\n 5570532 7001117 12571650 179695 31\n\n UCSB HOST 0 2682535 53971 2736506\n UCSB HOST 1 370000 543 370543\n -------- -------- --------\n 3052535 54514 3107049 98469 31\n\n UTAH HOST 0 1120918 319084 1440002 36159 31\n\n BBN HOST 0 2 40484 40486\n BBN HOST 1 5195648 413554 5609202\n BBN HOST 2 22191 1949","scope_keywords":["566"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 566 Network Working Group A. McKenzie\nRequest for Comments: 566 BBN-NET\nNIC: 18801 4 September 1973\nUpdates: RFC 556\n\n Traffic Statistics (August 1973)\n\n Attached are the Hosts traffic statistics for the month of August\n 1973.\n\n AAM/jm\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n AUGUST 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 302287 92769 395056\n UCLA HOST 1 2246832 182154 2428986\n UCLA HOST 2 454 66247 66701\n -------- -------- --------\n 2549573 341170 2890743 82244 31\n\n SRI HOST 0 5201216 6982664 12183880\n SRI HOST 1 369316 18453 387769\n -------- -------- --------\n 5570532 7001117 12571650 179695 31\n\n UCSB HOST 0 2682535 53971 2736506\n UCSB HOST 1 370000 543 370543\n -------- -------- --------\n 3052535 54514 3107049 98469 31\n\n UTAH HOST 0 1120918 319084 1440002 36159 31\n\n BBN HOST 0 2 40484 40486\n BBN HOST 1 5195648 413554 5609202\n BBN HOST 2 22191 1949 566 nested-reference unchanged"},{"id":"IETF RFC 5567","type":"specification","body":"IETF","designation":"RFC 5567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5567.txt","https://www.rfc-editor.org/rfc/rfc5567.pdf"],"folder":"IETF/RFC-5567","files":{"txt":{"path":"standards/IETF/RFC-5567/RFC-5567.txt","sha256":"7ed2dc308eda3fd24746159ee90d1e459a4e451571c50792caed0435b3ceb887"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an architectural framework for Media Server\n control. The primary focus will be to define logical entities that\n exist within the context of Media Server control, and define the\n appropriate naming conventions and interactions between them.\n\nMelanchuk Informational [Page 1]\n\f\nRFC 5567 Mediactrl Architecture June 2009","scope_keywords":["5567","http","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null}],"search_text":"IETF RFC 5567 This document describes an architectural framework for Media Server\n control. The primary focus will be to define logical entities that\n exist within the context of Media Server control, and define the\n appropriate naming conventions and interactions between them.\n\nMelanchuk Informational [Page 1]\n\f\nRFC 5567 Mediactrl Architecture June 2009 5567 http license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 559","type":"specification","body":"IETF","designation":"RFC 559","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc559.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc559.txt","https://www.rfc-editor.org/rfc/rfc559.pdf"],"folder":"IETF/RFC-559","files":{"txt":{"path":"standards/IETF/RFC-559/RFC-559.txt","sha256":"28085c58f32bc891db66fa801f4764657dd000c2a2408e654ee363d4ba050171"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Abhay K. Bushan\nRequest For Comments #559 MIT Project MAC\nNIC # 18482 August 15, 1973\n\n Comments on the new TELNET Protocol and its Implementation\n\n We at MIT-DN have implemented the new TELNET protocol (both server\nand user). This RFC describes our experience with the implementation\n(particularly the use of GO AHEAD) and in bringing the new User and\nServer TELNET's in operation (the new TELNET is not compatible with the\nold). We have a few suggestions here which should help other\nimplementors and lead to a smoother transition to the new protocol.\n\nI. OUR TELNET SERVER IMPLEMENTATION\n\n Our new server TELNET accepts both the \"old\" and the \"new\" TELNET\n\"control sequences\". Currently we have the ECHO and the \"Suppress Go\nAhead\" options implemented and do the \"right thing\" to varying degrees\nwith the Interrupt Process (IP), Erase Character (EC), Abort Output\n(AO), Are Y","scope_keywords":["559","crl","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 593","folder":"IETF/RFC-593","source":"IETF/RFC-593/RFC-593.txt","version":null}],"search_text":"IETF RFC 559 Network Working Group Abhay K. Bushan\nRequest For Comments #559 MIT Project MAC\nNIC # 18482 August 15, 1973\n\n Comments on the new TELNET Protocol and its Implementation\n\n We at MIT-DN have implemented the new TELNET protocol (both server\nand user). This RFC describes our experience with the implementation\n(particularly the use of GO AHEAD) and in bringing the new User and\nServer TELNET's in operation (the new TELNET is not compatible with the\nold). We have a few suggestions here which should help other\nimplementors and lead to a smoother transition to the new protocol.\n\nI. OUR TELNET SERVER IMPLEMENTATION\n\n Our new server TELNET accepts both the \"old\" and the \"new\" TELNET\n\"control sequences\". Currently we have the ECHO and the \"Suppress Go\nAhead\" options implemented and do the \"right thing\" to varying degrees\nwith the Interrupt Process (IP), Erase Character (EC), Abort Output\n(AO), Are Y 559 crl key nested-reference unchanged"},{"id":"IETF RFC 593","type":"specification","body":"IETF","designation":"RFC 593","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc593.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc593.txt","https://www.rfc-editor.org/rfc/rfc593.pdf"],"folder":"IETF/RFC-593","files":{"txt":{"path":"standards/IETF/RFC-593/RFC-593.txt","sha256":"26babeb4056da92db0d7e4e76c840d861b908ffa2b26a3e0cafd22cb5932ba1e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Alex McKenzie\nRequest for Comments: 593 BBN\n Jon Postel\n MITRE\n\n Telnet and FTP Implementation Schedule Change\n\nTelnet and FTP Implementation Schedule Change\n\n We have been contacted by several Telnet implementers and concerned\n users regarding the scheduled changeover from old to new Telnet.\n There is a good deal of concern about accomplishing a coordinated\n changeover especially in light of the potential incompatibilities\n (RFC 559, NIC18482). Therefore the changeover is reformulated as\n follows.\n\n New Telnet implementations are to be ready 1 Jan 74 (as before), but\n are to use ICP socket 23 (decimal). That is the server Telnet will\n listen on socket 23, and user Telnet programs will connect to socket\n 23. It will also be useful for the user program to let the user\n optionally select the server socket, as many user Telnet programs\n currently do. It will also be us","scope_keywords":["593"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 593 Network Working Group Alex McKenzie\nRequest for Comments: 593 BBN\n Jon Postel\n MITRE\n\n Telnet and FTP Implementation Schedule Change\n\nTelnet and FTP Implementation Schedule Change\n\n We have been contacted by several Telnet implementers and concerned\n users regarding the scheduled changeover from old to new Telnet.\n There is a good deal of concern about accomplishing a coordinated\n changeover especially in light of the potential incompatibilities\n (RFC 559, NIC18482). Therefore the changeover is reformulated as\n follows.\n\n New Telnet implementations are to be ready 1 Jan 74 (as before), but\n are to use ICP socket 23 (decimal). That is the server Telnet will\n listen on socket 23, and user Telnet programs will connect to socket\n 23. It will also be useful for the user program to let the user\n optionally select the server socket, as many user Telnet programs\n currently do. It will also be us 593 nested-reference unchanged"},{"id":"IETF RFC 5606","type":"specification","body":"IETF","designation":"RFC 5606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5606.txt","https://www.rfc-editor.org/rfc/rfc5606.pdf"],"folder":"IETF/RFC-5606","files":{"txt":{"path":"standards/IETF/RFC-5606/RFC-5606.txt","sha256":"f254b4792c46c3a0695735f6345bda6d85bc722a8f8804aeb395498858dd6600"}},"tags":["nested-reference","unchanged"],"summary":"This document explores an ambiguity in the interpretation of the\n <retransmission-allowed> element of the Presence Information Data\n Format for Location Objects (PIDF-LO) in cases where PIDF-LO is\n conveyed by the Session Initiation Protocol (SIP). It provides\n recommendations for how the SIP location conveyance mechanism should\n adapt to this ambiguity.\n\n Documents standardizing the SIP location conveyance mechanisms will\n be Standards-Track documents processed according to the usual SIP\n process. This document is intended primarily to provide the SIP\n working group with a statement of the consensus of the GEOPRIV\n working group on this topic. It secondarily provides tutorial\n information on the problem space for the general reader.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of thi","scope_keywords":["5606","encryption","http","key","license","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6442","folder":"IETF/RFC-6442","source":"IETF/RFC-6442/RFC-6442.txt","version":null}],"search_text":"IETF RFC 5606 This document explores an ambiguity in the interpretation of the\n <retransmission-allowed> element of the Presence Information Data\n Format for Location Objects (PIDF-LO) in cases where PIDF-LO is\n conveyed by the Session Initiation Protocol (SIP). It provides\n recommendations for how the SIP location conveyance mechanism should\n adapt to this ambiguity.\n\n Documents standardizing the SIP location conveyance mechanisms will\n be Standards-Track documents processed according to the usual SIP\n process. This document is intended primarily to provide the SIP\n working group with a statement of the consensus of the GEOPRIV\n working group on this topic. It secondarily provides tutorial\n information on the problem space for the general reader.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of thi 5606 encryption http key license pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 680","type":"specification","body":"IETF","designation":"RFC 680","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc680.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc680.txt","https://www.rfc-editor.org/rfc/rfc680.pdf"],"folder":"IETF/RFC-680","files":{"txt":{"path":"standards/IETF/RFC-680/RFC-680.txt","sha256":"1340ff71c26c71a5ab4d94f0cfd6c81f14a2fc90809bf5d8cbbcab8db8dc9851"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group T. Myer\nRequest for Comment: 680 D. Henderson\nNIC: 32116 BBN-TENEX\n April 30, 1975\n\n Message Transmission Protocol\n\n Theodore H. Myer\n\n D. Austin Henderson\n\n BBN-TENEX\n\n This document defines a number of message fields beyond those\n discussed in RFC 561. The overall message format is compatible with\n RFC 561; it makes extensive use of the miscellaneous fileds defined\n within RFC 561. The purpose of this document is to establish ARPANET\n standards with regard to the syntax and semantics for these\n additional fields. It is fully expected that all fields discussed\n herein will not be automatically processed by all Message Servers;\n however, the standard is necessary so that sites which wish to make\n use of these fields have a standard to work with.\n\n This document attempts to tread the narrow line between features for\n human processing and features for machine processi","scope_keywords":["680","authentication","crl","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0713","folder":"IETF/RFC-0713","source":"IETF/RFC-0713/RFC-0713.txt","version":null},{"body":"IETF","designation":"RFC 0733","folder":"IETF/RFC-0733","source":"IETF/RFC-0733/RFC-0733.txt","version":null},{"body":"IETF","designation":"RFC 713","folder":"IETF/RFC-713","source":"IETF/RFC-713/RFC-713.txt","version":null},{"body":"IETF","designation":"RFC 733","folder":"IETF/RFC-733","source":"IETF/RFC-733/RFC-733.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null}],"search_text":"IETF RFC 680 Network Working Group T. Myer\nRequest for Comment: 680 D. Henderson\nNIC: 32116 BBN-TENEX\n April 30, 1975\n\n Message Transmission Protocol\n\n Theodore H. Myer\n\n D. Austin Henderson\n\n BBN-TENEX\n\n This document defines a number of message fields beyond those\n discussed in RFC 561. The overall message format is compatible with\n RFC 561; it makes extensive use of the miscellaneous fileds defined\n within RFC 561. The purpose of this document is to establish ARPANET\n standards with regard to the syntax and semantics for these\n additional fields. It is fully expected that all fields discussed\n herein will not be automatically processed by all Message Servers;\n however, the standard is necessary so that sites which wish to make\n use of these fields have a standard to work with.\n\n This document attempts to tread the narrow line between features for\n human processing and features for machine processi 680 authentication crl key subject nested-reference unchanged"},{"id":"IETF RFC 580","type":"specification","body":"IETF","designation":"RFC 580","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc580.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc580.txt","https://www.rfc-editor.org/rfc/rfc580.pdf"],"folder":"IETF/RFC-580","files":{"txt":{"path":"standards/IETF/RFC-580/RFC-580.txt","sha256":"83b0fceb05f469a278735b4a69eeeb26c8c3554e2630345ba7f30df4036ef42a"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 580 JBP 25-OCT-73 06:00 19849\nnote to protocol designers and implementers\n\n Hereafter proposed protocols shall be submitted in the form of\non-line documents, preferably as nls files at the Network\nInformation Center. This will greatly facilitate the review\nprocess and enable editorial and substantive changes to proceed\nquickly. This also will permit timely updating of protocol\ndocuments as may be neccessitated by future decisions. On-line\ndocuments are also easily distributed to the network community.\nIf you find great difficulty in complying with this request\nplease contact me. \n\nIt should be noted by all Telnet protocol readers and especially\nimplementers that all the existing Telnet Options that involve\nsubnegotiation are modified [see RFC 562] to terminate the\nsubnegotiation strings with IAC SE. The value of SE is 240. Also\nnote that within subnegotiations the occurance of a","scope_keywords":["580"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 580 NWG/RFC# 580 JBP 25-OCT-73 06:00 19849\nnote to protocol designers and implementers\n\n Hereafter proposed protocols shall be submitted in the form of\non-line documents, preferably as nls files at the Network\nInformation Center. This will greatly facilitate the review\nprocess and enable editorial and substantive changes to proceed\nquickly. This also will permit timely updating of protocol\ndocuments as may be neccessitated by future decisions. On-line\ndocuments are also easily distributed to the network community.\nIf you find great difficulty in complying with this request\nplease contact me. \n\nIt should be noted by all Telnet protocol readers and especially\nimplementers that all the existing Telnet Options that involve\nsubnegotiation are modified [see RFC 562] to terminate the\nsubnegotiation strings with IAC SE. The value of SE is 240. Also\nnote that within subnegotiations the occurance of a 580 nested-reference unchanged"},{"id":"IETF RFC 565","type":"specification","body":"IETF","designation":"RFC 565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc565.txt","https://www.rfc-editor.org/rfc/rfc565.pdf"],"folder":"IETF/RFC-565","files":{"txt":{"path":"standards/IETF/RFC-565/RFC-565.txt","sha256":"ea65a7078796dc42e60d0dc7916fe25770f1007d259147f8e6a7268fd0bdaa83"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Cantor\nRequest for Comments: 565 Computer Corporation of America\nNIC: 18777 28 August 1973\n\n Storing Network Survey Data at the Datacomputer\n\n In November, 1972, Computer Corporation of America (CCA) and the\n Programming Technology Division of the Dynamics Modeling System (DMS)\n at M.I.T.'s Project MAC began planning to transmit to CCA's\n datacomputer [1] information about the behavior of ARPA network hosts\n collected by DMS's program SURVEY [2]. The information was to be\n stored at the datacomputer and retrieved by an interactive program\n that would address the datacomputer from DMS's PDP-10.\n\n One goal of this joint project was to enable DMS to retain all of the\n information that SURVEY collects: SURVEY had been running since late\n 1971, saving only a short daily summary of its findings and\n discarding potentially useful details. A second goal was to discover\n ","scope_keywords":["565","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null}],"search_text":"IETF RFC 565 Network Working Group D. Cantor\nRequest for Comments: 565 Computer Corporation of America\nNIC: 18777 28 August 1973\n\n Storing Network Survey Data at the Datacomputer\n\n In November, 1972, Computer Corporation of America (CCA) and the\n Programming Technology Division of the Dynamics Modeling System (DMS)\n at M.I.T.'s Project MAC began planning to transmit to CCA's\n datacomputer [1] information about the behavior of ARPA network hosts\n collected by DMS's program SURVEY [2]. The information was to be\n stored at the datacomputer and retrieved by an interactive program\n that would address the datacomputer from DMS's PDP-10.\n\n One goal of this joint project was to enable DMS to retain all of the\n information that SURVEY collects: SURVEY had been running since late\n 1971, saving only a short daily summary of its findings and\n discarding potentially useful details. A second goal was to discover\n  565 pid nested-reference unchanged"},{"id":"IETF RFC 6941","type":"specification","body":"IETF","designation":"RFC 6941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6941.txt","https://www.rfc-editor.org/rfc/rfc6941.pdf"],"folder":"IETF/RFC-6941","files":{"txt":{"path":"standards/IETF/RFC-6941/RFC-6941.txt","sha256":"27ffcac3209791bf739742539a07539c840094e04092ce8935e2f0eb265963d5"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a security framework for the MPLS Transport\n Profile (MPLS-TP). MPLS-TP extends MPLS technologies and introduces\n new Operations, Administration, and Maintenance (OAM) capabilities, a\n transport-oriented path protection mechanism, and strong emphasis on\n static provisioning supported by network management systems. This\n document addresses the security aspects relevant in the context of\n MPLS-TP specifically. It describes potential security threats as\n well as mitigation procedures related to MPLS-TP networks and to\n MPLS-TP interconnection to other MPLS and GMPLS networks. This\n document is built on RFC 5920 (\"Security Framework for MPLS and GMPLS\n Networks\") by providing additional security considerations that are\n applicable to the MPLS-TP extensions. All the security\n considerations from RFC 5920 are assumed to apply.\n\n This document is a product of a joint Inte","scope_keywords":["6941","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6941 This document provides a security framework for the MPLS Transport\n Profile (MPLS-TP). MPLS-TP extends MPLS technologies and introduces\n new Operations, Administration, and Maintenance (OAM) capabilities, a\n transport-oriented path protection mechanism, and strong emphasis on\n static provisioning supported by network management systems. This\n document addresses the security aspects relevant in the context of\n MPLS-TP specifically. It describes potential security threats as\n well as mitigation procedures related to MPLS-TP networks and to\n MPLS-TP interconnection to other MPLS and GMPLS networks. This\n document is built on RFC 5920 (\"Security Framework for MPLS and GMPLS\n Networks\") by providing additional security considerations that are\n applicable to the MPLS-TP extensions. All the security\n considerations from RFC 5920 are assumed to apply.\n\n This document is a product of a joint Inte 6941 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 567","type":"specification","body":"IETF","designation":"RFC 567","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc567.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc567.txt","https://www.rfc-editor.org/rfc/rfc567.pdf"],"folder":"IETF/RFC-567","files":{"txt":{"path":"standards/IETF/RFC-567/RFC-567.txt","sha256":"03c4e263393c3df9633bb3d1a06f83b12618394fa9962186b99cdd11d9a93039"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group L. Peter Deutsch (PARC-MAXC)\nRequest for Comments: 567 September 6, 1973\nNIC #18970\n\n CROSS-COUNTRY NETWORK BANDWIDTH\n\nThe following computation of cross-country network bandwidth was\ncontributed by Butler Lampson of PARC.\n\nConsider what happens when a TIP user on the West Coast, connected to a\nfull-duplex Host on the East Coast, strikes a key on his terminal.\n\nThe TIP sends a one-character message (1 packet).\n\nThe destination IMP sends a RFNM (1 packet).\n\nThe destination Host sends an ALLocate - this seems to be the strategy\nused by TENEX Hosts, at least (1 packet).\n\nThc TIP sends a RFNM for the ALLocate (1 packet).\n\nThe same sequence repeats itself, with roles interchanged, for the echo\ncharacter (4 packets).\n\nThis constitutes 4 packets or 4OOO bits in each direction. The current\ncross-country transmission capability of the ARPANET is 3 5OKb phone\nlines; ergo, it ","scope_keywords":["567","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 567 Network Working Group L. Peter Deutsch (PARC-MAXC)\nRequest for Comments: 567 September 6, 1973\nNIC #18970\n\n CROSS-COUNTRY NETWORK BANDWIDTH\n\nThe following computation of cross-country network bandwidth was\ncontributed by Butler Lampson of PARC.\n\nConsider what happens when a TIP user on the West Coast, connected to a\nfull-duplex Host on the East Coast, strikes a key on his terminal.\n\nThe TIP sends a one-character message (1 packet).\n\nThe destination IMP sends a RFNM (1 packet).\n\nThe destination Host sends an ALLocate - this seems to be the strategy\nused by TENEX Hosts, at least (1 packet).\n\nThc TIP sends a RFNM for the ALLocate (1 packet).\n\nThe same sequence repeats itself, with roles interchanged, for the echo\ncharacter (4 packets).\n\nThis constitutes 4 packets or 4OOO bits in each direction. The current\ncross-country transmission capability of the ARPANET is 3 5OKb phone\nlines; ergo, it  567 key nested-reference unchanged"},{"id":"IETF RFC 5678","type":"specification","body":"IETF","designation":"RFC 5678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5678.txt","https://www.rfc-editor.org/rfc/rfc5678.pdf"],"folder":"IETF/RFC-5678","files":{"txt":{"path":"standards/IETF/RFC-5678/RFC-5678.txt","sha256":"ac109337193e12a141f2db91345500664a8dfda20647f2e767a47e4d0d8a7dcb"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) options that contain a list of IP addresses and a list of\n domain names that can be mapped to servers providing IEEE 802.21 type\n of Mobility Service (MoS) (see RFC 5677). These Mobility Services\n are used to assist a mobile node (MN) in handover preparation\n (network discovery) and handover decision (network selection). The\n services addressed in this document are the Media Independent\n Handover Services defined in IEEE 802.21.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n C","scope_keywords":["5678","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null}],"search_text":"IETF RFC 5678 This document defines new Dynamic Host Configuration Protocol (DHCPv4\n and DHCPv6) options that contain a list of IP addresses and a list of\n domain names that can be mapped to servers providing IEEE 802.21 type\n of Mobility Service (MoS) (see RFC 5677). These Mobility Services\n are used to assist a mobile node (MN) in handover preparation\n (network discovery) and handover decision (network selection). The\n services addressed in this document are the Media Independent\n Handover Services defined in IEEE 802.21.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n C 5678 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 5679","type":"specification","body":"IETF","designation":"RFC 5679","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5679.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5679.txt","https://www.rfc-editor.org/rfc/rfc5679.pdf"],"folder":"IETF/RFC-5679","files":{"txt":{"path":"standards/IETF/RFC-5679/RFC-5679.txt","sha256":"5280fae31c90f27922a05c3c318c3878c1fffdb80cc1eaac11890ffbe9571a99"}},"tags":["nested-reference","unchanged"],"summary":"This document defines application service tags that allow service\n location without relying on rigid domain naming conventions, and DNS\n procedures for discovering servers that provide IEEE 802.21-defined\n Mobility Services. Such Mobility Services are used to assist a\n Mobile Node (MN) supporting IEEE 802.21, in handover preparation\n (network discovery) and handover decision (network selection). The\n services addressed by this document are the Media Independent\n Handover Services defined in IEEE 802.21.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyrigh","scope_keywords":["5679","http","key","license","management","path","registered","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 5679 This document defines application service tags that allow service\n location without relying on rigid domain naming conventions, and DNS\n procedures for discovering servers that provide IEEE 802.21-defined\n Mobility Services. Such Mobility Services are used to assist a\n Mobile Node (MN) supporting IEEE 802.21, in handover preparation\n (network discovery) and handover decision (network selection). The\n services addressed by this document are the Media Independent\n Handover Services defined in IEEE 802.21.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyrigh 5679 http key license management path registered subject trust nested-reference unchanged"},{"id":"IETF RFC 5689","type":"specification","body":"IETF","designation":"RFC 5689","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5689.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5689.txt","https://www.rfc-editor.org/rfc/rfc5689.pdf"],"folder":"IETF/RFC-5689","files":{"txt":{"path":"standards/IETF/RFC-5689/RFC-5689.txt","sha256":"37980dea6815566ef89c8caf459efa78601a87307f4bbb296067ef4ae9f5c48e"}},"tags":["nested-reference","unchanged"],"summary":"This specification extends the Web Distributed Authoring and\n Versioning (WebDAV) MKCOL (Make Collection) method to allow\n collections of arbitrary resourcetype to be created and to allow\n properties to be set at the same time.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of t","scope_keywords":["5689","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6352","folder":"IETF/RFC-6352","source":"IETF/RFC-6352/RFC-6352.txt","version":null}],"search_text":"IETF RFC 5689 This specification extends the Web Distributed Authoring and\n Versioning (WebDAV) MKCOL (Make Collection) method to allow\n collections of arbitrary resourcetype to be created and to allow\n properties to be set at the same time.\n\nStatus of This Memo\n\n This document specifies an Internet standards track protocol for the\n Internet community, and requests discussion and suggestions for\n improvements. Please refer to the current edition of the \"Internet\n Official Protocol Standards\" (STD 1) for the standardization state\n and status of this protocol. Distribution of this memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on the date of\n publication of t 5689 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 569","type":"specification","body":"IETF","designation":"RFC 569","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc569.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc569.txt","https://www.rfc-editor.org/rfc/rfc569.pdf"],"folder":"IETF/RFC-569","files":{"txt":{"path":"standards/IETF/RFC-569/RFC-569.txt","sha256":"e85d9b5799a6e8ba1dd89bd0569de029b1f5cc0ac17e8952999b5d3fe76e269e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mike Padlipsky\nRFC 569/ NET-USING Memo 1 NET-USING\nNIC # 18972 October 15, 1973\n\n NETED: A Common Editor for the ARPA Network\n\nBACKGROUND\n\nAt the recent Resource Sharing Workshop, there was a somewhat\nsurprising degree of consensus on what I had anticipated would the\nleast popular aspect of the my \"Unified User-Level Protocol\" proposal:\nA number of the attendees agreed without argument that it would be\na good thing to have \"the same\" context editor available on all\nServers -- where \"the same\" refers, of course, to the user interface.\nWe even agreed that \"NETED\" seemed to be a plausible common name. In\nview of the fact that the rest of the proposal didn't seem to capture\nanybody's imagination, though, it seemed to be a useful notion to\nseparate out the common editor and make it the subject of a\nstand-alone proposal.\n\nMy resolve to come up with the following was furth","scope_keywords":["569","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 569 Network Working Group Mike Padlipsky\nRFC 569/ NET-USING Memo 1 NET-USING\nNIC # 18972 October 15, 1973\n\n NETED: A Common Editor for the ARPA Network\n\nBACKGROUND\n\nAt the recent Resource Sharing Workshop, there was a somewhat\nsurprising degree of consensus on what I had anticipated would the\nleast popular aspect of the my \"Unified User-Level Protocol\" proposal:\nA number of the attendees agreed without argument that it would be\na good thing to have \"the same\" context editor available on all\nServers -- where \"the same\" refers, of course, to the user interface.\nWe even agreed that \"NETED\" seemed to be a plausible common name. In\nview of the fact that the rest of the proposal didn't seem to capture\nanybody's imagination, though, it seemed to be a useful notion to\nseparate out the common editor and make it the subject of a\nstand-alone proposal.\n\nMy resolve to come up with the following was furth 569 subject nested-reference unchanged"},{"id":"IETF RFC 5695","type":"specification","body":"IETF","designation":"RFC 5695","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5695.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5695.txt","https://www.rfc-editor.org/rfc/rfc5695.pdf"],"folder":"IETF/RFC-5695","files":{"txt":{"path":"standards/IETF/RFC-5695/RFC-5695.txt","sha256":"1045dbde23f91883d488c4adb34cabb14cccb0d97c54127c51bc5821068835dd"}},"tags":["nested-reference","unchanged"],"summary":"This document describes a methodology specific to the benchmarking\n of Multiprotocol Label Switching (MPLS) forwarding devices, limited\n to the most common MPLS packet forwarding scenarios and delay\n measurements for each, considering IP flows. It builds upon the\n tenets set forth in RFC 2544, RFC 1242, and other IETF Benchmarking\n Methodology Working Group (BMWG) efforts. This document seeks to\n extend these efforts to the MPLS paradigm.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on","scope_keywords":["5695","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5695 This document describes a methodology specific to the benchmarking\n of Multiprotocol Label Switching (MPLS) forwarding devices, limited\n to the most common MPLS packet forwarding scenarios and delay\n measurements for each, considering IP flows. It builds upon the\n tenets set forth in RFC 2544, RFC 1242, and other IETF Benchmarking\n Methodology Working Group (BMWG) efforts. This document seeks to\n extend these efforts to the MPLS paradigm.\n\nStatus of This Memo\n\n This memo provides information for the Internet community. It does\n not specify an Internet standard of any kind. Distribution of this\n memo is unlimited.\n\nCopyright Notice\n\n Copyright (c) 2009 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust's Legal\n Provisions Relating to IETF Documents\n (http://trustee.ietf.org/license-info) in effect on 5695 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 5707","type":"specification","body":"IETF","designation":"RFC 5707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5707.txt","https://www.rfc-editor.org/rfc/rfc5707.pdf"],"folder":"IETF/RFC-5707","files":{"txt":{"path":"standards/IETF/RFC-5707/RFC-5707.txt","sha256":"098a9b399213c1617b128786ae9888c4dd2684592d8e1462fc871e55f5892379"}},"tags":["nested-reference","unchanged"],"summary":"The Media Server Markup Language (MSML) is used to control and invoke\n many different types of services on IP media servers. The MSML\n control interface was initially driven by RadiSys with subsequent\n significant contributions from Intel, Dialogic, and others in the\n industry. Clients can use it to define how multimedia sessions\n interact on a media server and to apply services to individuals or\n groups of users. MSML can be used, for example, to control media\n server conferencing features such as video layout and audio mixing,\n create sidebar conferences or personal mixes, and set the properties\n of media streams. As well, clients can use MSML to define media\n processing dialogs, which may be used as parts of application\n interactions with users or conferences. Transformation of media\n streams to and from users or conferences as well as interactive voice\n response (IVR) dialogs are exa","scope_keywords":["5707","audit","http","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null}],"search_text":"IETF RFC 5707 The Media Server Markup Language (MSML) is used to control and invoke\n many different types of services on IP media servers. The MSML\n control interface was initially driven by RadiSys with subsequent\n significant contributions from Intel, Dialogic, and others in the\n industry. Clients can use it to define how multimedia sessions\n interact on a media server and to apply services to individuals or\n groups of users. MSML can be used, for example, to control media\n server conferencing features such as video layout and audio mixing,\n create sidebar conferences or personal mixes, and set the properties\n of media streams. As well, clients can use MSML to define media\n processing dialogs, which may be used as parts of application\n interactions with users or conferences. Transformation of media\n streams to and from users or conferences as well as interactive voice\n response (IVR) dialogs are exa 5707 audit http license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 571","type":"specification","body":"IETF","designation":"RFC 571","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc571.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc571.txt","https://www.rfc-editor.org/rfc/rfc571.pdf"],"folder":"IETF/RFC-571","files":{"txt":{"path":"standards/IETF/RFC-571/RFC-571.txt","sha256":"a713af55cc9bd706d2e9a824a377b35b5589394fbd9ed75960daffd63e29b857"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Robert T. Braden\nRequest for Comments: 571 UCLA/CCN\nNIC #18974 November 15, 1973\n\n TENEX FTP PROBLEM\n\n Tenex users of FTP should beware of a problem in the current Tenex\n implementation which is likely to cause incorrect results when\n transferring files to a non-Tenex site. Some Tenex programs create\n an ASCII US (Unit Separator) character as an end-of-line indicator,\n instead of CR LF. The current Tenex FTP user implementation passes\n these US characters over the Network instead of translating them to\n CR LF as required by FTP protocol. If the recipient is not a Tenex,\n he will not do anything special with these US characters and the line\n spacing will be lost. In the case of sending to CCN, we will treat it\n as a very long logical record and fold it into successive 360\n records.\n\n A circumvention is to pass the Tenex file through some Tenex program\n that does the ","scope_keywords":["571"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 571 Network Working Group Robert T. Braden\nRequest for Comments: 571 UCLA/CCN\nNIC #18974 November 15, 1973\n\n TENEX FTP PROBLEM\n\n Tenex users of FTP should beware of a problem in the current Tenex\n implementation which is likely to cause incorrect results when\n transferring files to a non-Tenex site. Some Tenex programs create\n an ASCII US (Unit Separator) character as an end-of-line indicator,\n instead of CR LF. The current Tenex FTP user implementation passes\n these US characters over the Network instead of translating them to\n CR LF as required by FTP protocol. If the recipient is not a Tenex,\n he will not do anything special with these US characters and the line\n spacing will be lost. In the case of sending to CCN, we will treat it\n as a very long logical record and fold it into successive 360\n records.\n\n A circumvention is to pass the Tenex file through some Tenex program\n that does the  571 nested-reference unchanged"},{"id":"IETF RFC 5714","type":"specification","body":"IETF","designation":"RFC 5714","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5714.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5714.txt","https://www.rfc-editor.org/rfc/rfc5714.pdf"],"folder":"IETF/RFC-5714","files":{"txt":{"path":"standards/IETF/RFC-5714/RFC-5714.txt","sha256":"7740365d777aba78b65acd26bf4ba78b227d29fef4a6dc4e300b5e0895029b63"}},"tags":["nested-reference","unchanged"],"summary":"This document provides a framework for the development of IP fast-\n reroute mechanisms that provide protection against link or router\n failure by invoking locally determined repair paths. Unlike MPLS\n fast-reroute, the mechanisms are applicable to a network employing\n conventional IP routing and forwarding.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f","scope_keywords":["5714","algorithm","algorithms","delivery","http","license","management","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5714 This document provides a framework for the development of IP fast-\n reroute mechanisms that provide protection against link or router\n failure by invoking locally determined repair paths. Unlike MPLS\n fast-reroute, the mechanisms are applicable to a network employing\n conventional IP routing and forwarding.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide f 5714 algorithm algorithms delivery http license management path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 5715","type":"specification","body":"IETF","designation":"RFC 5715","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5715.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5715.txt","https://www.rfc-editor.org/rfc/rfc5715.pdf"],"folder":"IETF/RFC-5715","files":{"txt":{"path":"standards/IETF/RFC-5715/RFC-5715.txt","sha256":"14d539b0ae4111be4fad0920d85da2207fa191443e9a71be477a2ed010b4cbec"}},"tags":["nested-reference","unchanged"],"summary":"A micro-loop is a packet forwarding loop that may occur transiently\n among two or more routers in a hop-by-hop packet forwarding paradigm.\n\n This framework provides a summary of the causes and consequences of\n micro-loops and enables the reader to form a judgement on whether\n micro-looping is an issue that needs to be addressed in specific\n networks. It also provides a survey of the currently proposed\n mechanisms that may be used to prevent or to suppress the formation\n of micro-loops when an IP or MPLS network undergoes topology change\n due to failure, repair, or management action. When sufficiently fast\n convergence is not available and the topology is susceptible to\n micro-loops, use of one or more of these mechanisms may be desirable.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is ","scope_keywords":["5715","algorithm","algorithms","delivery","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 5715 A micro-loop is a packet forwarding loop that may occur transiently\n among two or more routers in a hop-by-hop packet forwarding paradigm.\n\n This framework provides a summary of the causes and consequences of\n micro-loops and enables the reader to form a judgement on whether\n micro-looping is an issue that needs to be addressed in specific\n networks. It also provides a survey of the currently proposed\n mechanisms that may be used to prevent or to suppress the formation\n of micro-loops when an IP or MPLS network undergoes topology change\n due to failure, repair, or management action. When sufficiently fast\n convergence is not available and the topology is susceptible to\n micro-loops, use of one or more of these mechanisms may be desirable.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is  5715 algorithm algorithms delivery http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 5831","type":"specification","body":"IETF","designation":"RFC 5831","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5831.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5831.txt","https://www.rfc-editor.org/rfc/rfc5831.pdf"],"folder":"IETF/RFC-5831","files":{"txt":{"path":"standards/IETF/RFC-5831/RFC-5831.txt","sha256":"76631c870cd1afa5fe4986245336f99628e0a4ad7096fe5a928eea128a5bb587"}},"tags":["nested-reference","unchanged"],"summary":"This document is intended to be a source of information about the\n Russian Federal standard hash function (GOST R 34.11-94), which is\n one of the Russian cryptographic standard algorithms (called GOST\n algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST R 34.11-94 for hash\n computation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 574","scope_keywords":["5831","algorithm","algorithms","encryption","hash","http","key","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5933","folder":"IETF/RFC-5933","source":"IETF/RFC-5933/RFC-5933.txt","version":null}],"search_text":"IETF RFC 5831 This document is intended to be a source of information about the\n Russian Federal standard hash function (GOST R 34.11-94), which is\n one of the Russian cryptographic standard algorithms (called GOST\n algorithms). Recently, Russian cryptography is being used in\n Internet applications, and this document has been created as\n information for developers and users of GOST R 34.11-94 for hash\n computation.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 574 5831 algorithm algorithms encryption hash http key license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 5895","type":"specification","body":"IETF","designation":"RFC 5895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5895.txt","https://www.rfc-editor.org/rfc/rfc5895.pdf"],"folder":"IETF/RFC-5895","files":{"txt":{"path":"standards/IETF/RFC-5895/RFC-5895.txt","sha256":"528227c96a5c331547f527b708602330261550f0b6e18cdd8ad2cd08e90396da"}},"tags":["nested-reference","unchanged"],"summary":"In the original version of the Internationalized Domain Names in\n Applications (IDNA) protocol, any Unicode code points taken from user\n input were mapped into a set of Unicode code points that \"made\n sense\", and then encoded and passed to the domain name system (DNS).\n The IDNA2008 protocol (described in RFCs 5890, 5891, 5892, and 5893)\n presumes that the input to the protocol comes from a set of\n \"permitted\" code points, which it then encodes and passes to the DNS,\n but does not specify what to do with the result of user input. This\n document describes the actions that can be taken by an implementation\n between receiving user input and passing permitted code points to the\n new IDNA protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any ","scope_keywords":["5895","http","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6797","folder":"IETF/RFC-6797","source":"IETF/RFC-6797/RFC-6797.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6912","folder":"IETF/RFC-6912","source":"IETF/RFC-6912/RFC-6912.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7790","folder":"IETF/RFC-7790","source":"IETF/RFC-7790/RFC-7790.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 5895 In the original version of the Internationalized Domain Names in\n Applications (IDNA) protocol, any Unicode code points taken from user\n input were mapped into a set of Unicode code points that \"made\n sense\", and then encoded and passed to the domain name system (DNS).\n The IDNA2008 protocol (described in RFCs 5890, 5891, 5892, and 5893)\n presumes that the input to the protocol comes from a set of\n \"permitted\" code points, which it then encodes and passes to the DNS,\n but does not specify what to do with the result of user input. This\n document describes the actions that can be taken by an implementation\n between receiving user input and passing permitted code points to the\n new IDNA protocol.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any  5895 http key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6215","type":"specification","body":"IETF","designation":"RFC 6215","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6215.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6215.txt","https://www.rfc-editor.org/rfc/rfc6215.pdf"],"folder":"IETF/RFC-6215","files":{"txt":{"path":"standards/IETF/RFC-6215/RFC-6215.txt","sha256":"92618fba43fb7a69ffe60ab007ad4f70e710835baac48833a58572debaf5959c"}},"tags":["nested-reference","unchanged"],"summary":"The framework for MPLS in transport networks (RFC 5921) provides\n reference models for the MPLS Transport Profile (MPLS-TP) Transport\n Service Interfaces, which are a User-to-Network Interface (UNI), and\n a Network-to-Network Interface (NNI). This document updates those\n reference models to show detailed reference points for these\n interfaces, along with further clarification of the functional\n architecture of MPLS-TP at a UNI and NNI.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nStatus of This Memo\n\n This document is not an Internet Stan","scope_keywords":["6215","http","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null}],"search_text":"IETF RFC 6215 The framework for MPLS in transport networks (RFC 5921) provides\n reference models for the MPLS Transport Profile (MPLS-TP) Transport\n Service Interfaces, which are a User-to-Network Interface (UNI), and\n a Network-to-Network Interface (NNI). This document updates those\n reference models to show detailed reference points for these\n interfaces, along with further clarification of the functional\n architecture of MPLS-TP at a UNI and NNI.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nStatus of This Memo\n\n This document is not an Internet Stan 6215 http license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6430","type":"specification","body":"IETF","designation":"RFC 6430","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6430.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6430.txt","https://www.rfc-editor.org/rfc/rfc6430.pdf"],"folder":"IETF/RFC-6430","files":{"txt":{"path":"standards/IETF/RFC-6430/RFC-6430.txt","sha256":"13cde355994bd31731a99e6bb4009ea7016fb045b14f96cadcff4f3d4750ae0f"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a new Abuse Reporting Format (ARF) feedback\n report type value: \"not-spam\". It can be used to report an email\n message that was mistakenly marked as spam.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6430.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7","scope_keywords":["6430","algorithm","algorithms","http","key","keys","license","presentation","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6650","folder":"IETF/RFC-6650","source":"IETF/RFC-6650/RFC-6650.txt","version":null},{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 6430 This document defines a new Abuse Reporting Format (ARF) feedback\n report type value: \"not-spam\". It can be used to report an email\n message that was mistakenly marked as spam.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6430.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 7 6430 algorithm algorithms http key keys license presentation signature subject trust nested-reference unchanged"},{"id":"IETF RFC 6452","type":"specification","body":"IETF","designation":"RFC 6452","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6452.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6452.txt","https://www.rfc-editor.org/rfc/rfc6452.pdf"],"folder":"IETF/RFC-6452","files":{"txt":{"path":"standards/IETF/RFC-6452/RFC-6452.txt","sha256":"3ef89afc6f34f25b3d9c013a4c136f4a632b59aa05ad31e8a29322dc7cf47605"}},"tags":["nested-reference","unchanged"],"summary":"This memo documents IETF consensus for Internationalized Domain Names\n for Applications (IDNA) derived character properties related to the\n three code points, existing in Unicode 5.2, that changed property\n values when version 6.0 was released. The consensus is that no\n update is needed to RFC 5892 based on the changes made in Unicode\n 6.0.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf","scope_keywords":["6452","algorithm","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null}],"search_text":"IETF RFC 6452 This memo documents IETF consensus for Internationalized Domain Names\n for Applications (IDNA) derived character properties related to the\n three code points, existing in Unicode 5.2, that changed property\n values when version 6.0 was released. The consensus is that no\n update is needed to RFC 5892 based on the changes made in Unicode\n 6.0.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rf 6452 algorithm http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7218","type":"specification","body":"IETF","designation":"RFC 7218","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7218.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7218.txt","https://www.rfc-editor.org/rfc/rfc7218.pdf"],"folder":"IETF/RFC-7218","files":{"txt":{"path":"standards/IETF/RFC-7218/RFC-7218.txt","sha256":"7d1c32c0cb10ed2cddfe4fe2fe95ed04950da5bf718f2c074ffb92f1ff3ae0da"}},"tags":["nested-reference","unchanged"],"summary":"Experience has shown that people get confused when discussing the\n three numeric fields of the TLSA record. This document specifies\n descriptive acronyms for the three numeric fields in TLSA records.\n This document updates the format of the IANA registry created by RFC\n 6698.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7218.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the p","scope_keywords":["7218","authentication","certificate","hash","http","key","license","pki","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7671","folder":"IETF/RFC-7671","source":"IETF/RFC-7671/RFC-7671.txt","version":null},{"body":"IETF","designation":"RFC 7672","folder":"IETF/RFC-7672","source":"IETF/RFC-7672/RFC-7672.txt","version":null},{"body":"IETF","designation":"RFC 7673","folder":"IETF/RFC-7673","source":"IETF/RFC-7673/RFC-7673.txt","version":null},{"body":"IETF","designation":"RFC 7712","folder":"IETF/RFC-7712","source":"IETF/RFC-7712/RFC-7712.txt","version":null},{"body":"IETF","designation":"RFC 8162","folder":"IETF/RFC-8162","source":"IETF/RFC-8162/RFC-8162.txt","version":null}],"search_text":"IETF RFC 7218 Experience has shown that people get confused when discussing the\n three numeric fields of the TLSA record. This document specifies\n descriptive acronyms for the three numeric fields in TLSA records.\n This document updates the format of the IANA registry created by RFC\n 6698.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7218.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the p 7218 authentication certificate hash http key license pki subject tls trust nested-reference unchanged"},{"id":"IETF RFC 7337","type":"specification","body":"IETF","designation":"RFC 7337","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7337.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7337.txt","https://www.rfc-editor.org/rfc/rfc7337.pdf"],"folder":"IETF/RFC-7337","files":{"txt":{"path":"standards/IETF/RFC-7337/RFC-7337.txt","sha256":"f0504c3c95e79697df7cbba0889ee9ef312c947c8b1b7c527758fd131ebd332f"}},"tags":["nested-reference","unchanged"],"summary":"Content delivery is frequently provided by specifically architected\n and provisioned Content Delivery Networks (CDNs). As a result of\n significant growth in content delivered over IP networks, existing\n CDN providers are scaling up their infrastructure. Many Network\n Service Providers (NSPs) and Enterprise Service Providers (ESPs) are\n also deploying their own CDNs. To deliver contents from the Content\n Service Provider (CSP) to end users, the contents may traverse across\n multiple CDNs. This creates a need for interconnecting (previously)\n standalone CDNs so that they can collectively act as a single\n delivery platform from the CSP to the end users.\n\n The goal of the present document is to outline the requirements for\n the solution and interfaces to be specified by the CDNI working\n group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publ","scope_keywords":["7337","delivery","http","key","license","pid","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7336","folder":"IETF/RFC-7336","source":"IETF/RFC-7336/RFC-7336.txt","version":null},{"body":"IETF","designation":"RFC 7937","folder":"IETF/RFC-7937","source":"IETF/RFC-7937/RFC-7937.txt","version":null},{"body":"IETF","designation":"RFC 7975","folder":"IETF/RFC-7975","source":"IETF/RFC-7975/RFC-7975.txt","version":null},{"body":"IETF","designation":"RFC 8006","folder":"IETF/RFC-8006","source":"IETF/RFC-8006/RFC-8006.txt","version":null},{"body":"IETF","designation":"RFC 8007","folder":"IETF/RFC-8007","source":"IETF/RFC-8007/RFC-8007.txt","version":null},{"body":"IETF","designation":"RFC 8008","folder":"IETF/RFC-8008","source":"IETF/RFC-8008/RFC-8008.txt","version":null}],"search_text":"IETF RFC 7337 Content delivery is frequently provided by specifically architected\n and provisioned Content Delivery Networks (CDNs). As a result of\n significant growth in content delivered over IP networks, existing\n CDN providers are scaling up their infrastructure. Many Network\n Service Providers (NSPs) and Enterprise Service Providers (ESPs) are\n also deploying their own CDNs. To deliver contents from the Content\n Service Provider (CSP) to end users, the contents may traverse across\n multiple CDNs. This creates a need for interconnecting (previously)\n standalone CDNs so that they can collectively act as a single\n delivery platform from the CSP to the end users.\n\n The goal of the present document is to outline the requirements for\n the solution and interfaces to be specified by the CDNI working\n group.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n publ 7337 delivery http key license pid policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7396","type":"specification","body":"IETF","designation":"RFC 7396","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7396.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7396.txt","https://www.rfc-editor.org/rfc/rfc7396.pdf"],"folder":"IETF/RFC-7396","files":{"txt":{"path":"standards/IETF/RFC-7396/RFC-7396.txt","sha256":"545e1d61667c243ea14d6b1a56212370a26d46e1acd441803805fcdecd9164c6"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines the JSON merge patch format and processing\n rules. The merge patch format is primarily intended for use with the\n HTTP PATCH method as a means of describing a set of modifications to\n a target resource's content.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7396.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document au","scope_keywords":["7396","http","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8132","folder":"IETF/RFC-8132","source":"IETF/RFC-8132/RFC-8132.txt","version":null}],"search_text":"IETF RFC 7396 This specification defines the JSON merge patch format and processing\n rules. The merge patch format is primarily intended for use with the\n HTTP PATCH method as a means of describing a set of modifications to\n a target resource's content.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7396.\n\nCopyright Notice\n\n Copyright (c) 2014 IETF Trust and the persons identified as the\n document au 7396 http license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7536","type":"specification","body":"IETF","designation":"RFC 7536","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7536.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7536.txt","https://www.rfc-editor.org/rfc/rfc7536.pdf"],"folder":"IETF/RFC-7536","files":{"txt":{"path":"standards/IETF/RFC-7536/RFC-7536.txt","sha256":"899b514b2b44acf5eea94a4b647d1e14eb0e507782adac20f85ae7cb084414ea"}},"tags":["nested-reference","unchanged"],"summary":"Measuring broadband performance on a large scale is important for\n network diagnostics by providers and users, as well as for public\n policy. Understanding the various scenarios and users of measuring\n broadband performance is essential to development of the Large-scale\n Measurement of Broadband Performance (LMAP) framework, information\n model, and protocol. This document details two use cases that can\n assist in developing that framework. The details of the measurement\n metrics themselves are beyond the scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering","scope_keywords":["7536","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7594","folder":"IETF/RFC-7594","source":"IETF/RFC-7594/RFC-7594.txt","version":null}],"search_text":"IETF RFC 7536 Measuring broadband performance on a large scale is important for\n network diagnostics by providers and users, as well as for public\n policy. Understanding the various scenarios and users of measuring\n broadband performance is essential to development of the Large-scale\n Measurement of Broadband Performance (LMAP) framework, information\n model, and protocol. This document details two use cases that can\n assist in developing that framework. The details of the measurement\n metrics themselves are beyond the scope of this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering 7536 http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 8307","type":"specification","body":"IETF","designation":"RFC 8307","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8307.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8307.txt","https://www.rfc-editor.org/rfc/rfc8307.pdf"],"folder":"IETF/RFC-8307","files":{"txt":{"path":"standards/IETF/RFC-8307/RFC-8307.txt","sha256":"db2da99541cf4daa78f1eebb126f54dd85ea82bfdd92caeca2a379e2dfee62c1"}},"tags":["nested-reference","unchanged"],"summary":"RFC 5785 defines a path prefix, \"/.well-known/\", that can be used by\n well-known URIs. It was specifically defined for the \"http\" and\n \"https\" URI schemes. The present memo formally updates RFC 6455,\n which defines the URI schemes defined for the WebSocket Protocol, to\n extend the use of these well-known URIs to those URI schemes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8307.\n\nC","scope_keywords":["8307","http","https","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 8615","folder":"IETF/RFC-8615","source":"IETF/RFC-8615/RFC-8615.txt","version":null}],"search_text":"IETF RFC 8307 RFC 5785 defines a path prefix, \"/.well-known/\", that can be used by\n well-known URIs. It was specifically defined for the \"http\" and\n \"https\" URI schemes. The present memo formally updates RFC 6455,\n which defines the URI schemes defined for the WebSocket Protocol, to\n extend the use of these well-known URIs to those URI schemes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8307.\n\nC 8307 http https license path subject trust nested-reference unchanged"},{"id":"IETF RFC 579","type":"specification","body":"IETF","designation":"RFC 579","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc579.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc579.txt","https://www.rfc-editor.org/rfc/rfc579.pdf"],"folder":"IETF/RFC-579","files":{"pdf":{"path":"standards/IETF/RFC-579/RFC-579.pdf","sha256":"fec745370d9eaa6e775d3898012867787edbdd3eda9ee021507738129489cce2"},"txt":{"path":"standards/IETF/RFC-579/RFC-579.txt","sha256":"da05d0d700a4e76d6a90ff95e38542eb4f4cacd031fddf3ef51d9ab39478ffc8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 579 BBN-NET\nNIC: 19655 October 1973\nUpdates: 566\n\n Traffic Statistics (September 1973)\n\n Attached are the Host traffic statistics for the month of\n September 1973. It is my intention to issue Traffic Statistics\n for October, November, and December in RFC form, and then to\n remove these reports from the RFC series. I will continue to\n produce the reports, and so could have the NIC distribute them\n to technical Liaisons if there is any interest. Alternatively,\n I could continue issuing them as RFC's if there is great interest.\n Let me know.\n\n AAM/jm\n Attach.\n\n RECEIVED AT NIC OCTOBER 19, 1973.\n\nMcKenzie [Page 1]\n\f\nRFC 579 Traffic Statistics October 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n SEPTEMBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 285955 39986 325941\n UCLA HOST 1 1059718 44377 110","scope_keywords":["579"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 579 Network Working Group A. McKenzie\nRequest for Comments: 579 BBN-NET\nNIC: 19655 October 1973\nUpdates: 566\n\n Traffic Statistics (September 1973)\n\n Attached are the Host traffic statistics for the month of\n September 1973. It is my intention to issue Traffic Statistics\n for October, November, and December in RFC form, and then to\n remove these reports from the RFC series. I will continue to\n produce the reports, and so could have the NIC distribute them\n to technical Liaisons if there is any interest. Alternatively,\n I could continue issuing them as RFC's if there is great interest.\n Let me know.\n\n AAM/jm\n Attach.\n\n RECEIVED AT NIC OCTOBER 19, 1973.\n\nMcKenzie [Page 1]\n\f\nRFC 579 Traffic Statistics October 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n SEPTEMBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 285955 39986 325941\n UCLA HOST 1 1059718 44377 110 579 nested-reference unchanged"},{"id":"IETF RFC 5817","type":"specification","body":"IETF","designation":"RFC 5817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5817.txt","https://www.rfc-editor.org/rfc/rfc5817.pdf"],"folder":"IETF/RFC-5817","files":{"txt":{"path":"standards/IETF/RFC-5817/RFC-5817.txt","sha256":"54ec088c8db689008c6536a7b702196c83e6c87ea5ae0d0010f814ab8893c4b1"}},"tags":["nested-reference","unchanged"],"summary":"MPLS-TE Graceful Shutdown is a method for explicitly notifying the\n nodes in a Traffic Engineering (TE) enabled network that the TE\n capability on a link or on an entire Label Switching Router (LSR) is\n going to be disabled. MPLS-TE graceful shutdown mechanisms are\n tailored toward addressing planned outage in the network.\n\n This document provides requirements and protocol mechanisms to reduce\n or eliminate traffic disruption in the event of a planned shutdown of\n a network resource. These operations are equally applicable to both\n MPLS-TE and its Generalized MPLS (GMPLS) extensions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appro","scope_keywords":["5817","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 5817 MPLS-TE Graceful Shutdown is a method for explicitly notifying the\n nodes in a Traffic Engineering (TE) enabled network that the TE\n capability on a link or on an entire Label Switching Router (LSR) is\n going to be disabled. MPLS-TE graceful shutdown mechanisms are\n tailored toward addressing planned outage in the network.\n\n This document provides requirements and protocol mechanisms to reduce\n or eliminate traffic disruption in the event of a planned shutdown of\n a network resource. These operations are equally applicable to both\n MPLS-TE and its Generalized MPLS (GMPLS) extensions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been appro 5817 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 5852","type":"specification","body":"IETF","designation":"RFC 5852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5852.txt","https://www.rfc-editor.org/rfc/rfc5852.pdf"],"folder":"IETF/RFC-5852","files":{"txt":{"path":"standards/IETF/RFC-5852/RFC-5852.txt","sha256":"2a40327ffb1d34bd4d51454b564a86fad722ab30b99c9de13457c66c7b97cbd2"}},"tags":["nested-reference","unchanged"],"summary":"In a transport network scenario, Data Plane connections controlled by\n either a Generalized Multiprotocol Label Switching (GMPLS) Control\n Plane (Soft Permanent Connections - SPC) or a Management System\n (Permanent Connections - PC) may independently coexist. The ability\n of transforming an existing PC into an SPC and vice versa -- without\n actually affecting Data Plane traffic being carried over it -- is a\n requirement. The requirements for the conversion between permanent\n connections and switched connections in a GMPLS Network are defined\n in RFC 5493.\n\n This memo describes an extension to GMPLS Resource Reservation\n Protocol - Traffic Engineering (RSVP-TE) signaling that enables the\n transfer of connection ownership between the Management and the\n Control Planes. Such a transfer is referred to as a Handover. This\n document defines all Handover-related procedures. This includes the\n h","scope_keywords":["5852","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"IETF RFC 5852 In a transport network scenario, Data Plane connections controlled by\n either a Generalized Multiprotocol Label Switching (GMPLS) Control\n Plane (Soft Permanent Connections - SPC) or a Management System\n (Permanent Connections - PC) may independently coexist. The ability\n of transforming an existing PC into an SPC and vice versa -- without\n actually affecting Data Plane traffic being carried over it -- is a\n requirement. The requirements for the conversion between permanent\n connections and switched connections in a GMPLS Network are defined\n in RFC 5493.\n\n This memo describes an extension to GMPLS Resource Reservation\n Protocol - Traffic Engineering (RSVP-TE) signaling that enables the\n transfer of connection ownership between the Management and the\n Control Planes. Such a transfer is referred to as a Handover. This\n document defines all Handover-related procedures. This includes the\n h 5852 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 586","type":"specification","body":"IETF","designation":"RFC 586","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc586.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc586.txt","https://www.rfc-editor.org/rfc/rfc586.pdf"],"folder":"IETF/RFC-586","files":{"pdf":{"path":"standards/IETF/RFC-586/RFC-586.pdf","sha256":"280f401cbea307727a857c4cc711e83c62fc0819c3a2fca3654ba04f93104eff"},"txt":{"path":"standards/IETF/RFC-586/RFC-586.txt","sha256":"01b767ebf98caae3711fdca5decdf28c804dbd3e2ff418059eb9d494b56c3928"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRFC #586 BBN-NET\nNIC #20096 8 November 1973\nUpdates: RFC #579\n\n Traffic Statistics (October 1973)\n\n Attached are the Host traffic statistics for the month of October\n 1973.\n\n AAM/jm\n Attach.\n\n RECEIVED AT NIC NOVEMBER 14, 1973.\n\nMcKenzie [Page 1]\n\f\nRFC 586 Traffic Statistics (October 1973) November 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n OCTOBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 256764 17221 273985\n UCLA HOST 1 1604925 34897 1639822\n UCLA HOST 2 42009 338 42347\n -------- -------- --------\n 1903698 52456 1956154 61410 31\n\n SRI HOST 0 6070784 731464 6802248\n SRI HOST 1 409423 101235 510658\n -------- -------- --------\n 6480207 832699 7312906 209039 31\n\n UCSB HOST 0 2839618 13415 2853033\n UCSB HOST 1 347310 4414 351724\n -------- -------- --------\n 3186928 17829 3204757 102804 31\n\n UTAH HOST 1 908427 2643","scope_keywords":["586"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 586 Network Working Group A. McKenzie\nRFC #586 BBN-NET\nNIC #20096 8 November 1973\nUpdates: RFC #579\n\n Traffic Statistics (October 1973)\n\n Attached are the Host traffic statistics for the month of October\n 1973.\n\n AAM/jm\n Attach.\n\n RECEIVED AT NIC NOVEMBER 14, 1973.\n\nMcKenzie [Page 1]\n\f\nRFC 586 Traffic Statistics (October 1973) November 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n OCTOBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\n UCLA HOST 0 256764 17221 273985\n UCLA HOST 1 1604925 34897 1639822\n UCLA HOST 2 42009 338 42347\n -------- -------- --------\n 1903698 52456 1956154 61410 31\n\n SRI HOST 0 6070784 731464 6802248\n SRI HOST 1 409423 101235 510658\n -------- -------- --------\n 6480207 832699 7312906 209039 31\n\n UCSB HOST 0 2839618 13415 2853033\n UCSB HOST 1 347310 4414 351724\n -------- -------- --------\n 3186928 17829 3204757 102804 31\n\n UTAH HOST 1 908427 2643 586 nested-reference unchanged"},{"id":"IETF RFC 8274","type":"specification","body":"IETF","designation":"RFC 8274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8274.txt","https://www.rfc-editor.org/rfc/rfc8274.pdf"],"folder":"IETF/RFC-8274","files":{"txt":{"path":"standards/IETF/RFC-8274/RFC-8274.txt","sha256":"30edf4a7d581441582a6dce11f66b9e6c60c074923c738a8f0b6168cef1c397e"}},"tags":["nested-reference","unchanged"],"summary":"The Incident Object Description Exchange Format (IODEF) v2 (RFC 7970)\n defines a data representation that provides a framework for sharing\n information about computer security incidents commonly exchanged by\n Computer Security Incident Response Teams (CSIRTs). Since the IODEF\n model includes a wealth of available options that can be used to\n describe a security incident or issue, it can be challenging for\n security practitioners to develop tools that leverage IODEF for\n incident sharing. This document provides guidelines for IODEF\n implementers. It addresses how common security indicators can be\n represented in IODEF and provides use cases of how IODEF is being\n used. This document aims to make IODEF's adoption by vendors easier\n and to encourage faster and wider adoption of the model by CSIRTs\n around the world.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track spe","scope_keywords":["8274","attribute","delivery","http","https","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8404","folder":"IETF/RFC-8404","source":"IETF/RFC-8404/RFC-8404.txt","version":null}],"search_text":"IETF RFC 8274 The Incident Object Description Exchange Format (IODEF) v2 (RFC 7970)\n defines a data representation that provides a framework for sharing\n information about computer security incidents commonly exchanged by\n Computer Security Incident Response Teams (CSIRTs). Since the IODEF\n model includes a wealth of available options that can be used to\n describe a security incident or issue, it can be challenging for\n security practitioners to develop tools that leverage IODEF for\n incident sharing. This document provides guidelines for IODEF\n implementers. It addresses how common security indicators can be\n represented in IODEF and provides use cases of how IODEF is being\n used. This document aims to make IODEF's adoption by vendors easier\n and to encourage faster and wider adoption of the model by CSIRTs\n around the world.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track spe 8274 attribute delivery http https license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 5950","type":"specification","body":"IETF","designation":"RFC 5950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5950.txt","https://www.rfc-editor.org/rfc/rfc5950.pdf"],"folder":"IETF/RFC-5950","files":{"txt":{"path":"standards/IETF/RFC-5950/RFC-5950.txt","sha256":"c5411770eb6398cf9f34aa866b1dc36d9afbae6dce47e1cb9d905446132b2ebc"}},"tags":["nested-reference","unchanged"],"summary":"This document provides the network management framework for the\n Transport Profile for Multi-Protocol Label Switching (MPLS-TP).\n\n This framework relies on the management terminology from the ITU-T to\n describe the management architecture that could be used for an MPLS-\n TP management network.\n\n The management of the MPLS-TP network could be based on multi-tiered\n distributed management systems. This document provides a description\n of the network and element management architectures that could be\n applied and also describes heuristics associated with fault,\n configuration, and performance aspects of the management system.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and PWE3 architectures to support","scope_keywords":["5950","http","license","management","path","profile","subject","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 5950 This document provides the network management framework for the\n Transport Profile for Multi-Protocol Label Switching (MPLS-TP).\n\n This framework relies on the management terminology from the ITU-T to\n describe the management architecture that could be used for an MPLS-\n TP management network.\n\n The management of the MPLS-TP network could be based on multi-tiered\n distributed management systems. This document provides a description\n of the network and element management architectures that could be\n applied and also describes heuristics associated with fault,\n configuration, and performance aspects of the management system.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and PWE3 architectures to support 5950 http license management path profile subject trust validation nested-reference unchanged"},{"id":"IETF RFC 5959","type":"specification","body":"IETF","designation":"RFC 5959","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc5959.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc5959.txt","https://www.rfc-editor.org/rfc/rfc5959.pdf"],"folder":"IETF/RFC-5959","files":{"txt":{"path":"standards/IETF/RFC-5959/RFC-5959.txt","sha256":"9e1c56dad2ba1e4233cee0b8c39471877151376b7d0707313f749286a36b1b97"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the conventions for using several\n cryptographic algorithms with the EncryptedPrivateKeyInfo structure,\n as defined in RFC 5958. It also includes conventions necessary to\n protect the AsymmetricKeyPackage content type with SignedData,\n EnvelopedData, EncryptedData, AuthenticatedData, and\n AuthEnvelopedData.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5959.\n\nCo","scope_keywords":["5959","algorithm","algorithms","attribute","attributes","certificate","certificates","encryption","hash","http","key","keys","license","management","signature","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6072","folder":"IETF/RFC-6072","source":"IETF/RFC-6072/RFC-6072.txt","version":null}],"search_text":"IETF RFC 5959 This document describes the conventions for using several\n cryptographic algorithms with the EncryptedPrivateKeyInfo structure,\n as defined in RFC 5958. It also includes conventions necessary to\n protect the AsymmetricKeyPackage content type with SignedData,\n EnvelopedData, EncryptedData, AuthenticatedData, and\n AuthEnvelopedData.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc5959.\n\nCo 5959 algorithm algorithms attribute attributes certificate certificates encryption hash http key keys license management signature subject nested-reference unchanged"},{"id":"IETF RFC 596","type":"specification","body":"IETF","designation":"RFC 596","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc596.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc596.txt","https://www.rfc-editor.org/rfc/rfc596.pdf"],"folder":"IETF/RFC-596","files":{"txt":{"path":"standards/IETF/RFC-596/RFC-596.txt","sha256":"43496679074abebe483a323101eecc06e078e30b3677fd7c811c77ac6f1baaf5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Taft\nRequest for Comments: 596 PARC-MAXC\nNIC: 15372 8 December 1973\n\n Second Thoughts on Telnet Go-Ahead\n\nINTRODUCTION\n\n In this RFC we present objections to the requirement that hosts\n implement the Telnet Go-Ahead (GA) command, as specified in the\n Telnet Protocol Specification (NIC #15372). The thrust of these\n objections is in three major directions:\n\n 1. The GA mechanism is esthetically unappealing, both to myself\n and to many other people I have talked to. I shall attempt to\n describe why this is so.\n\n 2. As specified in the Protocol, GA will not, in general, work;\n i.e. it will not serve its intended purpose unless hosts make\n various unwarranted assumptions about how other hosts operate.\n\n 3. GA is impossible for most hosts to implement correctly in all\n cases. This is certainly true of the PDP-10 operating systems\n with which I am familiar (10/50 and Ten","scope_keywords":["596","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 596 Network Working Group E. Taft\nRequest for Comments: 596 PARC-MAXC\nNIC: 15372 8 December 1973\n\n Second Thoughts on Telnet Go-Ahead\n\nINTRODUCTION\n\n In this RFC we present objections to the requirement that hosts\n implement the Telnet Go-Ahead (GA) command, as specified in the\n Telnet Protocol Specification (NIC #15372). The thrust of these\n objections is in three major directions:\n\n 1. The GA mechanism is esthetically unappealing, both to myself\n and to many other people I have talked to. I shall attempt to\n describe why this is so.\n\n 2. As specified in the Protocol, GA will not, in general, work;\n i.e. it will not serve its intended purpose unless hosts make\n various unwarranted assumptions about how other hosts operate.\n\n 3. GA is impossible for most hosts to implement correctly in all\n cases. This is certainly true of the PDP-10 operating systems\n with which I am familiar (10/50 and Ten 596 key path nested-reference unchanged"},{"id":"IETF RFC 597","type":"specification","body":"IETF","designation":"RFC 597","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc597.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc597.txt","https://www.rfc-editor.org/rfc/rfc597.pdf"],"folder":"IETF/RFC-597","files":{"txt":{"path":"standards/IETF/RFC-597/RFC-597.txt","sha256":"3c99a1350d4eb7efaa052327daf9c2aeb06ffb5ea22007e3feb1632a4e6605b6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group N. Neigus\nRequest for Comment: 597 J. Feinler\nNIC: 20826 12 December 1973\n\n Host Status\n\n Attached are the latest network maps -- geographic and logical -- and\n a list of Hosts connected to the ARPANET.\n\n The geographic map shows all IMPs and TIPs currently installed in the\n subnetwork.\n\n The logical map diagrams the current (as of Dec. 10, 1973) status of\n all computers on the net, with the exception of MIT-MULTICS which is\n shown in the advanced state of being attached to IMP #44 rather than\n IMP #5. (My apologies for not reprinting the map.) Hosts with\n interfaces to the subnet are shown with intersected ovals; the small\n \"v\" represents a Very Distant Host (VDH) interface to the IMP; IMPs\n are the solid black circles and TIPs the circles with \"T\" enclosed.\n The two jagged lines represent satellite links.\n\n Note: The names listed on this map are unofficial IMP nam","scope_keywords":["597","crl","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 606","folder":"IETF/RFC-606","source":"IETF/RFC-606/RFC-606.txt","version":null}],"search_text":"IETF RFC 597 Network Working Group N. Neigus\nRequest for Comment: 597 J. Feinler\nNIC: 20826 12 December 1973\n\n Host Status\n\n Attached are the latest network maps -- geographic and logical -- and\n a list of Hosts connected to the ARPANET.\n\n The geographic map shows all IMPs and TIPs currently installed in the\n subnetwork.\n\n The logical map diagrams the current (as of Dec. 10, 1973) status of\n all computers on the net, with the exception of MIT-MULTICS which is\n shown in the advanced state of being attached to IMP #44 rather than\n IMP #5. (My apologies for not reprinting the map.) Hosts with\n interfaces to the subnet are shown with intersected ovals; the small\n \"v\" represents a Very Distant Host (VDH) interface to the IMP; IMPs\n are the solid black circles and TIPs the circles with \"T\" enclosed.\n The two jagged lines represent satellite links.\n\n Note: The names listed on this map are unofficial IMP nam 597 crl tsp nested-reference unchanged"},{"id":"IETF RFC 606","type":"specification","body":"IETF","designation":"RFC 606","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc606.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc606.txt","https://www.rfc-editor.org/rfc/rfc606.pdf"],"folder":"IETF/RFC-606","files":{"txt":{"path":"standards/IETF/RFC-606/RFC-606.txt","sha256":"4741dfffe67f4bcce09042d79cb4497ef9c2bd4470b8797288d1c78d8719dfa5"}},"tags":["nested-reference","unchanged"],"summary":"Netork Working Group L. Peter Deutsch\nRequest For Comments: 606 PARC-MAXC\n December 1973\n\n Host Names On-line\n\nNow that we finally have an official list of host names, it seems\nabout time to put an end to the absurd situation where each site\non the network must maintain a different, generally out-of-date,\nhost list for the use of its own operating system or user\nprograms.\n\nFor example, each of the TENEX sites to which I have access\n( SRI-ARC, BBN-TENEX, USC-ISI, and PARC-MAXC) has a slightly\ndifferent mapping between host names and host addresses: none\nis complete, and I believe each one differs in some way from\nthe official List.\n\nSince the NIC has responsibility for maintaining the official\nlist, lt seems appropriate for them to maintain an on-line file,\naccessible to anyone, which Lists names and host addresses ( and\ncertain other information which I will suggest in a moment) in an\nea","scope_keywords":["606","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 623","folder":"IETF/RFC-623","source":"IETF/RFC-623/RFC-623.txt","version":null}],"search_text":"IETF RFC 606 Netork Working Group L. Peter Deutsch\nRequest For Comments: 606 PARC-MAXC\n December 1973\n\n Host Names On-line\n\nNow that we finally have an official list of host names, it seems\nabout time to put an end to the absurd situation where each site\non the network must maintain a different, generally out-of-date,\nhost list for the use of its own operating system or user\nprograms.\n\nFor example, each of the TENEX sites to which I have access\n( SRI-ARC, BBN-TENEX, USC-ISI, and PARC-MAXC) has a slightly\ndifferent mapping between host names and host addresses: none\nis complete, and I believe each one differs in some way from\nthe official List.\n\nSince the NIC has responsibility for maintaining the official\nlist, lt seems appropriate for them to maintain an on-line file,\naccessible to anyone, which Lists names and host addresses ( and\ncertain other information which I will suggest in a moment) in an\nea 606 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 600","type":"specification","body":"IETF","designation":"RFC 600","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc600.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc600.txt","https://www.rfc-editor.org/rfc/rfc600.pdf"],"folder":"IETF/RFC-600","files":{"pdf":{"path":"standards/IETF/RFC-600/RFC-600.pdf","sha256":"1f721a07511e316c5c935d4dc7d3b2e187a6ba0491dd221297c0dbb5857d275a"},"txt":{"path":"standards/IETF/RFC-600/RFC-600.txt","sha256":"a2cabb109a616697ec7c2e62773ddf9e2a5ad99302693d57926029fa81527302"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Berggreen\nRequest for Comments: 600 COMPUTER SYSTEMS LABORATORY--UCSB\nNIC: 20884 November 1973\n\n INTERFACING AN ILLINOIS PLASMA TERMINAL TO THE ARPANET\n\nINTRODUCTION\n\n The PLATO IV System based at the University of Illinois at Urbana is\n a highly sophisticated and very powerful approach to Computer Aided\n Instruction. The PLATO IV system makes use of a plasma display\n terminal that is a unique device with capabilities not presently\n found on computer terminals. A number of ARPA supported projects\n intend to use the plasma terminal on local connection to computer\n resources or by long-distance connection to the PLATO IV System.\n\n One problem in using the PLATO System from any appreciable distance,\n is the communication costs involved (i.e. long-distance telephone\n rates for many consecutive hours). Also, use of the plasma terminal\n in other applications is hampere","scope_keywords":["600","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 600 Network Working Group A. Berggreen\nRequest for Comments: 600 COMPUTER SYSTEMS LABORATORY--UCSB\nNIC: 20884 November 1973\n\n INTERFACING AN ILLINOIS PLASMA TERMINAL TO THE ARPANET\n\nINTRODUCTION\n\n The PLATO IV System based at the University of Illinois at Urbana is\n a highly sophisticated and very powerful approach to Computer Aided\n Instruction. The PLATO IV system makes use of a plasma display\n terminal that is a unique device with capabilities not presently\n found on computer terminals. A number of ARPA supported projects\n intend to use the plasma terminal on local connection to computer\n resources or by long-distance connection to the PLATO IV System.\n\n One problem in using the PLATO System from any appreciable distance,\n is the communication costs involved (i.e. long-distance telephone\n rates for many consecutive hours). Also, use of the plasma terminal\n in other applications is hampere 600 key nested-reference unchanged"},{"id":"IETF RFC 601","type":"specification","body":"IETF","designation":"RFC 601","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc601.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc601.txt","https://www.rfc-editor.org/rfc/rfc601.pdf"],"folder":"IETF/RFC-601","files":{"txt":{"path":"standards/IETF/RFC-601/RFC-601.txt","sha256":"4f53fbfbc762f3d6213343a3822862fd77249f7f3319fd0dc1f8b90bac060f15"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRFC # 601 BBN-NET\nNIC # 20905 14 December 1973\nUpdates: RFC # 586\n\n Traffic Statistics (November 1973)\n\nAttached are the Host traffic statistics for the month of November 1973.\n\nAAM/jm\nAttach.\n\nMcKenzie [Page 1]\n\f\nRFC 601 Traffic Statistics (November 1973) December 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n NOVEMBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 241273 30480 271753\nUCLA HOST 1 1536918 56526 1593444\nUCLA HOST 2 26253 4954 31207\n -------- -------- --------\n 1804444 91960 1896404 60148 30\n\nSRI HOST 0 6519907 208536 6728443\nSRI HOST 1 574488 162319 736807\n -------- -------- --------\n 7094395 370855 7465250 236480 30\n\nUCSB HOST 0 2549879 76826 2626705\nUCSB HOST 1 313615 2751 316366\n -------- -------- --------\n 2863494 79577 2943071 95450 30\n\nUTAH HOST 0 1304159 203988 1508147\nUTAH HOST 2 87741 187693 2754","scope_keywords":["601"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 601 Network Working Group A. McKenzie\nRFC # 601 BBN-NET\nNIC # 20905 14 December 1973\nUpdates: RFC # 586\n\n Traffic Statistics (November 1973)\n\nAttached are the Host traffic statistics for the month of November 1973.\n\nAAM/jm\nAttach.\n\nMcKenzie [Page 1]\n\f\nRFC 601 Traffic Statistics (November 1973) December 1973\n\n HOST THROUGHPUT SUMMARY\n (PACKETS OUTPUT)\n\n NOVEMBER 1973\n\n INTER- INTRA- AVG. DAILY\n NODE NODE TOTAL INTERNODE DAYS\n\nUCLA HOST 0 241273 30480 271753\nUCLA HOST 1 1536918 56526 1593444\nUCLA HOST 2 26253 4954 31207\n -------- -------- --------\n 1804444 91960 1896404 60148 30\n\nSRI HOST 0 6519907 208536 6728443\nSRI HOST 1 574488 162319 736807\n -------- -------- --------\n 7094395 370855 7465250 236480 30\n\nUCSB HOST 0 2549879 76826 2626705\nUCSB HOST 1 313615 2751 316366\n -------- -------- --------\n 2863494 79577 2943071 95450 30\n\nUTAH HOST 0 1304159 203988 1508147\nUTAH HOST 2 87741 187693 2754 601 nested-reference unchanged"},{"id":"IETF RFC 9019","type":"specification","body":"IETF","designation":"RFC 9019","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc9019.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc9019.txt","https://www.rfc-editor.org/rfc/rfc9019.pdf"],"folder":"IETF/RFC-9019","files":{"pdf":{"path":"standards/IETF/RFC-9019/RFC-9019.pdf","sha256":"d67a1ec4c1f60a6ce516fa6a739a56504b22220c4504286d9d2ce7f4bb264229"},"txt":{"path":"standards/IETF/RFC-9019/RFC-9019.txt","sha256":"b29e6c39ff2db10cb4c138c0c45bd47a478386a6b053b02129b3704efa1008e6"}},"tags":["nested-reference","unchanged"],"summary":"Vulnerabilities in Internet of Things (IoT) devices have raised the\n need for a reliable and secure firmware update mechanism suitable for\n devices with resource constraints. Incorporating such an update\n mechanism is a fundamental requirement for fixing vulnerabilities,\n but it also enables other important capabilities such as updating\n configuration settings and adding new functionality.\n\n In addition to the definition of terminology and an architecture,\n this document provides the motivation for the standardization of a\n manifest format as a transport-agnostic means for describing and\n protecting firmware updates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive","scope_keywords":["9019","authentication","credential","credentials","delivery","holder","http","https","key","keys","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9397","folder":"IETF/RFC-9397","source":"IETF/RFC-9397/RFC-9397.txt","version":null}],"search_text":"IETF RFC 9019 Vulnerabilities in Internet of Things (IoT) devices have raised the\n need for a reliable and secure firmware update mechanism suitable for\n devices with resource constraints. Incorporating such an update\n mechanism is a fundamental requirement for fixing vulnerabilities,\n but it also enables other important capabilities such as updating\n configuration settings and adding new functionality.\n\n In addition to the definition of terminology and an architecture,\n this document provides the motivation for the standardization of a\n manifest format as a transport-agnostic means for describing and\n protecting firmware updates.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n receive 9019 authentication credential credentials delivery holder http https key keys license management subject trust nested-reference unchanged"},{"id":"IETF RFC 603","type":"specification","body":"IETF","designation":"RFC 603","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc603.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc603.txt","https://www.rfc-editor.org/rfc/rfc603.pdf"],"folder":"IETF/RFC-603","files":{"txt":{"path":"standards/IETF/RFC-603/RFC-603.txt","sha256":"f1f84b7db8138d356a12d1deac0f1ceaec0a35fe4edbc8ef610db0c6ac6f350e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J.D. Burchfiel\nRFC # 603 BBN-TENEX\nNIC # 21022 31 December, 1973\n\n Response to RFC # 597: Host Status\n\n I have several questions about the November 1973 ARPANET\ntopographical map:\n\n 1. AMES is 4-connected, i.e. four network connections will go down\n if the IMP fails. Is there some aspiration that IMPs should be\n no more than three connected?\n\n 2. The seven IMPS in the Washington area are arranged into a loop.\n This guarantees that local communication can take place even if\n one connection fails, and is probably a worthwhile preparation\n for area routing. On the other hand, for example, a break\n between MIT-IPC and MIT-MAC will require them to communicate\n through a 12-hop path through Washington. This can be remedied\n by a short (inexpensive) connection between Harvard and Lincoln\n Labs. Is there a plan to pull the Boston area, the San\n Francisco area, and the Los A","scope_keywords":["603","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 603 Network Working Group J.D. Burchfiel\nRFC # 603 BBN-TENEX\nNIC # 21022 31 December, 1973\n\n Response to RFC # 597: Host Status\n\n I have several questions about the November 1973 ARPANET\ntopographical map:\n\n 1. AMES is 4-connected, i.e. four network connections will go down\n if the IMP fails. Is there some aspiration that IMPs should be\n no more than three connected?\n\n 2. The seven IMPS in the Washington area are arranged into a loop.\n This guarantees that local communication can take place even if\n one connection fails, and is probably a worthwhile preparation\n for area routing. On the other hand, for example, a break\n between MIT-IPC and MIT-MAC will require them to communicate\n through a 12-hop path through Washington. This can be remedied\n by a short (inexpensive) connection between Harvard and Lincoln\n Labs. Is there a plan to pull the Boston area, the San\n Francisco area, and the Los A 603 path nested-reference unchanged"},{"id":"IETF RFC 623","type":"specification","body":"IETF","designation":"RFC 623","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc623.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc623.txt","https://www.rfc-editor.org/rfc/rfc623.pdf"],"folder":"IETF/RFC-623","files":{"txt":{"path":"standards/IETF/RFC-623/RFC-623.txt","sha256":"af7b1497438d740ce11a88083362bfe5cac686d9577359b760a14dc2c4dc9378"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mark Krilanovich\nRFC # 623 UCSB\nNIC # 22004 February 22, 1974\nReference: RFC #606, 608\n\n Comments on On-Line Host Name Service\n\n Peter Deutsch in RFC #606 pointed out the desirability of having a\nsingle host maintain a data base containing official host names and host\naddresses, as well as other information of secondary importance. Mike\nKudlick in RFC #608 agreed with the concept, and proposed that the NIC\nwould implement Peter's ideas. I would like to add my voice to those in\nsupport of such a service, and express a few ideas for its modification.\n\n The notion of having a single host maintain this data base clearly\nhas the weakness that anyone wishing to obtain a copy of the data may be\nfaced with the situation that the serving host is not available when the\ndata is desired. It is true that each host could save a copy of the\nmost recently obtained data, such that w","scope_keywords":["623","attribute"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 625","folder":"IETF/RFC-625","source":"IETF/RFC-625/RFC-625.txt","version":null}],"search_text":"IETF RFC 623 Network Working Group Mark Krilanovich\nRFC # 623 UCSB\nNIC # 22004 February 22, 1974\nReference: RFC #606, 608\n\n Comments on On-Line Host Name Service\n\n Peter Deutsch in RFC #606 pointed out the desirability of having a\nsingle host maintain a data base containing official host names and host\naddresses, as well as other information of secondary importance. Mike\nKudlick in RFC #608 agreed with the concept, and proposed that the NIC\nwould implement Peter's ideas. I would like to add my voice to those in\nsupport of such a service, and express a few ideas for its modification.\n\n The notion of having a single host maintain this data base clearly\nhas the weakness that anyone wishing to obtain a copy of the data may be\nfaced with the situation that the serving host is not available when the\ndata is desired. It is true that each host could save a copy of the\nmost recently obtained data, such that w 623 attribute nested-reference unchanged"},{"id":"IETF RFC 607","type":"specification","body":"IETF","designation":"RFC 607","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc607.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc607.txt","https://www.rfc-editor.org/rfc/rfc607.pdf"],"folder":"IETF/RFC-607","files":{"txt":{"path":"standards/IETF/RFC-607/RFC-607.txt","sha256":"20ef56009e6462c49a13437fbc50ad7817c916ceb805489ecedb4f8df1f04303"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 607 Mark Krilanovich\nNIC # 21255 George Gregg\nreferences: RFC #542 UCSB Jan 1974\n \n\n Comments on the File Transfer Protocol\n\nThere are several aspects of the File Transfer Protocol that constitute\nserious drawbacks. Some of these are quite basic in nature, and imply\nsubstantial design changes; these will be discussed in a later RFC.\nOthers could be remedied with very little effort, and this should be done\nas soon as possible.\n\nFollowing is a list of those problems that can be easily solved, together\nwith their proposed solutions:\n\n1. Once a server has been told to be \"passive\" with regard to establishment\nof data connections, there is no way for the user to make him \"active\"\nagain. SOLUTION: define a new command, with a command verb of \"ACTV\", to\nmean that the server is to issue a CONNECT rather than a LISTEN on the data\nsocket. If the server is already \"active\", th","scope_keywords":["607","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 614","folder":"IETF/RFC-614","source":"IETF/RFC-614/RFC-614.txt","version":null},{"body":"IETF","designation":"RFC 624","folder":"IETF/RFC-624","source":"IETF/RFC-624/RFC-624.txt","version":null},{"body":"IETF","designation":"RFC 7159","folder":"IETF/RFC-7159","source":"IETF/RFC-7159/RFC-7159.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 607 Request for Comments: 607 Mark Krilanovich\nNIC # 21255 George Gregg\nreferences: RFC #542 UCSB Jan 1974\n \n\n Comments on the File Transfer Protocol\n\nThere are several aspects of the File Transfer Protocol that constitute\nserious drawbacks. Some of these are quite basic in nature, and imply\nsubstantial design changes; these will be discussed in a later RFC.\nOthers could be remedied with very little effort, and this should be done\nas soon as possible.\n\nFollowing is a list of those problems that can be easily solved, together\nwith their proposed solutions:\n\n1. Once a server has been told to be \"passive\" with regard to establishment\nof data connections, there is no way for the user to make him \"active\"\nagain. SOLUTION: define a new command, with a command verb of \"ACTV\", to\nmean that the server is to issue a CONNECT rather than a LISTEN on the data\nsocket. If the server is already \"active\", th 607 path nested-reference unchanged"},{"id":"IETF RFC 608","type":"specification","body":"IETF","designation":"RFC 608","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc608.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc608.txt","https://www.rfc-editor.org/rfc/rfc608.pdf"],"folder":"IETF/RFC-608","files":{"txt":{"path":"standards/IETF/RFC-608/RFC-608.txt","sha256":"e683653b7ea72cac7d83461aa984bf6020ae07564ae2bd5161a2f7321935e796"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M.D. Kudlick\nRFC # 608 SRI-ARC\nNIC # 21256 January 10, 1974\n\n HOST NAMES ON-LINE\n\nWe at the NIC agree with Peter Deutsch's suggestion (in RFC# 606 / NIC#\n21246) that the NIC maintain an online ASCII text file of Host names,\naddresses, and attributes. That suggestion corresponds to one made by\nVint Cerf recently, and evidently receives ARPA/IPT support.\n\nJake Feinler at the NIC designed and maintains a source file, in NLS\nformat, that can be used to generate the ASCII file Peter outlined. A\nprogram to generate an up to date version of the ASCII file needs to be\nwritten at the NIC, and run periodically (weekly, or as the situation\nwarrants). Such a mechanism would allow us, of course, to maintain one\nsource of data and use it for this and other purposes.\n\nOur present data includes official Host name, Host address, Host status\n(user, server, TIP) and certain other info","scope_keywords":["608","attribute","attributes","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 623","folder":"IETF/RFC-623","source":"IETF/RFC-623/RFC-623.txt","version":null},{"body":"IETF","designation":"RFC 810","folder":"IETF/RFC-810","source":"IETF/RFC-810/RFC-810.txt","version":null}],"search_text":"IETF RFC 608 Network Working Group M.D. Kudlick\nRFC # 608 SRI-ARC\nNIC # 21256 January 10, 1974\n\n HOST NAMES ON-LINE\n\nWe at the NIC agree with Peter Deutsch's suggestion (in RFC# 606 / NIC#\n21246) that the NIC maintain an online ASCII text file of Host names,\naddresses, and attributes. That suggestion corresponds to one made by\nVint Cerf recently, and evidently receives ARPA/IPT support.\n\nJake Feinler at the NIC designed and maintains a source file, in NLS\nformat, that can be used to generate the ASCII file Peter outlined. A\nprogram to generate an up to date version of the ASCII file needs to be\nwritten at the NIC, and run periodically (weekly, or as the situation\nwarrants). Such a mechanism would allow us, of course, to maintain one\nsource of data and use it for this and other purposes.\n\nOur present data includes official Host name, Host address, Host status\n(user, server, TIP) and certain other info 608 attribute attributes path nested-reference unchanged"},{"id":"IETF RFC 810","type":"specification","body":"IETF","designation":"RFC 810","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc810.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc810.txt","https://www.rfc-editor.org/rfc/rfc810.pdf"],"folder":"IETF/RFC-810","files":{"txt":{"path":"standards/IETF/RFC-810/RFC-810.txt","sha256":"6268e520f0b5fc3f85ee39a8bbbe1f0f97da142fbf35a2e1141af46fc30bc274"}},"tags":["nested-reference","unchanged"],"summary":"Elizabeth Feinler RFC 810\nKen Harrenstien 1 March 1982\nZaw-Sing Su References: RFC 811, 796\nVic White Obsoletes: RFC 608\nNetwork Information Center\nSRI International\n\n DoD INTERNET HOST TABLE SPECIFICATION\n\nINTRODUCTION\n\n The ARPANET Official Network Host Table, as outlined in RFC 608, no\n longer suits the needs of the DoD community, nor does it follow a\n format suitable for internetting. This paper specifies a new host\n table format applicable to both ARPANET and Internet needs.\n\n In addition to host name to host address translation and selected\n protocol information, we have also included network and gateway name\n to address correspondence, and host operating system information.\n\n This Host Table is utilized by the DoD Host Name Server maintained by\n the ARPANET Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) (RFC 811). It obsoletes the host table","scope_keywords":["810","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0952","folder":"IETF/RFC-0952","source":"IETF/RFC-0952/RFC-0952.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 811","folder":"IETF/RFC-811","source":"IETF/RFC-811/RFC-811.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 952","folder":"IETF/RFC-952","source":"IETF/RFC-952/RFC-952.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null}],"search_text":"IETF RFC 810 Elizabeth Feinler RFC 810\nKen Harrenstien 1 March 1982\nZaw-Sing Su References: RFC 811, 796\nVic White Obsoletes: RFC 608\nNetwork Information Center\nSRI International\n\n DoD INTERNET HOST TABLE SPECIFICATION\n\nINTRODUCTION\n\n The ARPANET Official Network Host Table, as outlined in RFC 608, no\n longer suits the needs of the DoD community, nor does it follow a\n format suitable for internetting. This paper specifies a new host\n table format applicable to both ARPANET and Internet needs.\n\n In addition to host name to host address translation and selected\n protocol information, we have also included network and gateway name\n to address correspondence, and host operating system information.\n\n This Host Table is utilized by the DoD Host Name Server maintained by\n the ARPANET Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) (RFC 811). It obsoletes the host table 810 key registered nested-reference unchanged"},{"id":"IETF RFC 6116","type":"specification","body":"IETF","designation":"RFC 6116","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6116.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6116.txt","https://www.rfc-editor.org/rfc/rfc6116.pdf"],"folder":"IETF/RFC-6116","files":{"txt":{"path":"standards/IETF/RFC-6116/RFC-6116.txt","sha256":"35b5bfe7db7455ff2d2ab12c98d8d2110aefd1ad78671b35a163f3fe111c6413"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the use of the Domain Name System (DNS) for\n storage of data associated with E.164 numbers, and for resolving\n those numbers into URIs that can be used (for example) in telephony\n call setup. This document also describes how the DNS can be used to\n identify the services associated with an E.164 number. This document\n obsoletes RFC 3761.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rf","scope_keywords":["6116","algorithm","holder","http","key","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null}],"search_text":"IETF RFC 6116 This document discusses the use of the Domain Name System (DNS) for\n storage of data associated with E.164 numbers, and for resolving\n those numbers into URIs that can be used (for example) in telephony\n call setup. This document also describes how the DNS can be used to\n identify the services associated with an E.164 number. This document\n obsoletes RFC 3761.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rf 6116 algorithm holder http key license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 6117","type":"specification","body":"IETF","designation":"RFC 6117","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6117.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6117.txt","https://www.rfc-editor.org/rfc/rfc6117.pdf"],"folder":"IETF/RFC-6117","files":{"txt":{"path":"standards/IETF/RFC-6117/RFC-6117.txt","sha256":"77eac7ca279fa4e788ee6814026d1b9341cc0c8bd8e19203e0a9d03189e22c21"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a revision of the IANA Registration\n Guidelines for Enumservices, describes corresponding registration\n procedures, and provides a guideline for creating Enumservice\n Specifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6117.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi","scope_keywords":["6117","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6118","folder":"IETF/RFC-6118","source":"IETF/RFC-6118/RFC-6118.txt","version":null},{"body":"IETF","designation":"RFC 7553","folder":"IETF/RFC-7553","source":"IETF/RFC-7553/RFC-7553.txt","version":null},{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null},{"body":"IETF","designation":"RFC 8553","folder":"IETF/RFC-8553","source":"IETF/RFC-8553/RFC-8553.txt","version":null}],"search_text":"IETF RFC 6117 This document specifies a revision of the IANA Registration\n Guidelines for Enumservices, describes corresponding registration\n procedures, and provides a guideline for creating Enumservice\n Specifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6117.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n Thi 6117 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6123","type":"specification","body":"IETF","designation":"RFC 6123","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6123.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6123.txt","https://www.rfc-editor.org/rfc/rfc6123.pdf"],"folder":"IETF/RFC-6123","files":{"txt":{"path":"standards/IETF/RFC-6123/RFC-6123.txt","sha256":"e34350484f58a487a3aa312a776141f3d52d1eac55fd5f52c59cc703d9b1c013"}},"tags":["nested-reference","unchanged"],"summary":"It has often been the case that manageability considerations have\n been retrofitted to protocols after they have been specified,\n standardized, implemented, or deployed. This is sub-optimal.\n Similarly, new protocols or protocol extensions are frequently\n designed without due consideration of manageability requirements.\n\n The Operations Area has developed \"Guidelines for Considering\n Operations and Management of New Protocols and Protocol Extensions\"\n (RFC 5706), and those guidelines have been adopted by the Path\n Computation Element (PCE) Working Group.\n\n Previously, the PCE Working Group used the recommendations contained\n in this document to guide authors of Internet-Drafts on the contents\n of \"Manageability Considerations\" sections in their work. This\n document is retained for historic reference.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; i","scope_keywords":["6123","http","key","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 6123 It has often been the case that manageability considerations have\n been retrofitted to protocols after they have been specified,\n standardized, implemented, or deployed. This is sub-optimal.\n Similarly, new protocols or protocol extensions are frequently\n designed without due consideration of manageability requirements.\n\n The Operations Area has developed \"Guidelines for Considering\n Operations and Management of New Protocols and Protocol Extensions\"\n (RFC 5706), and those guidelines have been adopted by the Path\n Computation Element (PCE) Working Group.\n\n Previously, the PCE Working Group used the recommendations contained\n in this document to guide authors of Internet-Drafts on the contents\n of \"Manageability Considerations\" sections in their work. This\n document is retained for historic reference.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; i 6123 http key license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 615","type":"specification","body":"IETF","designation":"RFC 615","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc615.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc615.txt","https://www.rfc-editor.org/rfc/rfc615.pdf"],"folder":"IETF/RFC-615","files":{"txt":{"path":"standards/IETF/RFC-615/RFC-615.txt","sha256":"de1e197bf27f3588fa23f9f3649110eae7425af8191aab3edcee694ee2dddbc7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Crocker (UCLA-NMC)\nRequest for Comments: 615 MAR 74\nNIC #21531\n\n Proposed Network\n Standard Data Pathname Syntax\n\nThere seems to be an increasing call for a Network Standard Data Pathname\n(NSDP); that is, a standardized means of referring to a specific location\nfor/of a collection of bits somewhere on the Network.\n\nThe reasons for a standard or virtual anything have been discussed, at\nlength, elsewhere and will not be elaborated upon here. Rather than\nattack the entire issue of virtual pathnames, I wish only to propose a\nstandardized SYNTAX for specifying pathnames. Such a standard will be\nuseful for 1) users who are unfamiliar with a site or who use several\ndifferent sites and do not want to have to remember each site's\nidiosynchracies, 2) programs accessing data at several other sites, and\n3) documentation:\n\nThe syntax allows the user to specify the necessary n","scope_keywords":["615","attribute","attributes","key","keys","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 615 Network Working Group D. Crocker (UCLA-NMC)\nRequest for Comments: 615 MAR 74\nNIC #21531\n\n Proposed Network\n Standard Data Pathname Syntax\n\nThere seems to be an increasing call for a Network Standard Data Pathname\n(NSDP); that is, a standardized means of referring to a specific location\nfor/of a collection of bits somewhere on the Network.\n\nThe reasons for a standard or virtual anything have been discussed, at\nlength, elsewhere and will not be elaborated upon here. Rather than\nattack the entire issue of virtual pathnames, I wish only to propose a\nstandardized SYNTAX for specifying pathnames. Such a standard will be\nuseful for 1) users who are unfamiliar with a site or who use several\ndifferent sites and do not want to have to remember each site's\nidiosynchracies, 2) programs accessing data at several other sites, and\n3) documentation:\n\nThe syntax allows the user to specify the necessary n 615 attribute attributes key keys path nested-reference unchanged"},{"id":"IETF RFC 6187","type":"specification","body":"IETF","designation":"RFC 6187","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6187.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6187.txt","https://www.rfc-editor.org/rfc/rfc6187.pdf"],"folder":"IETF/RFC-6187","files":{"txt":{"path":"standards/IETF/RFC-6187/RFC-6187.txt","sha256":"92074112c1aa563231db35d9b63c5e1a5896a5ff60fda926024456568f1aa407"}},"tags":["nested-reference","unchanged"],"summary":"X.509 public key certificates use a signature by a trusted\n certification authority to bind a given public key to a given digital\n identity. This document specifies how to use X.509 version 3 public\n key certificates in public key algorithms in the Secure Shell\n protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6187.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the perso","scope_keywords":["6187","algorithm","algorithms","authentication","certificate","certificates","http","key","keys","license","management","signature","signatures","subject","trust","x509"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 6187 X.509 public key certificates use a signature by a trusted\n certification authority to bind a given public key to a given digital\n identity. This document specifies how to use X.509 version 3 public\n key certificates in public key algorithms in the Secure Shell\n protocol.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6187.\n\nCopyright Notice\n\n Copyright (c) 2011 IETF Trust and the perso 6187 algorithm algorithms authentication certificate certificates http key keys license management signature signatures subject trust x509 nested-reference unchanged"},{"id":"IETF RFC 625","type":"specification","body":"IETF","designation":"RFC 625","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc625.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc625.txt","https://www.rfc-editor.org/rfc/rfc625.pdf"],"folder":"IETF/RFC-625","files":{"txt":{"path":"standards/IETF/RFC-625/RFC-625.txt","sha256":"4bccffb234b4f8215f9bb942094f01c0e74dde2e96109c57a578c57665519cc1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mike Kudlick (SRI-ARC)\nRFC # 625 Jake Feinler (SRI-ARC)\nNIC # 22152 March 7, 1974\n\n ON LINE HOSTNAMES SERVICE\n\nWe agree with the suggestion in RFC 623 that more than one Host should\nbe responsible for maintaining a copy of the Hostnames data base. The\nNIC is certainly willing to continue to maintain the master data base,\nand make it available to any secondary Host that volunteers to maintain\na copy. We would be pleased to have UCSB serve as one of the secondary\nHosts.\n\nHowever, we disagree with the suggestion in RFC 623 that a server\nprocess should be implemented to give user processes access to the\nofficial Hostnames file at the NIC. The file in question is a\nsequential file and it seems to us that FTP is entirely appropriate for\nthis need. As far as setting up common login parameters among the\nservers, this doesn't appear to be a major problem. Even with a\nuser/se","scope_keywords":["625"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null}],"search_text":"IETF RFC 625 Network Working Group Mike Kudlick (SRI-ARC)\nRFC # 625 Jake Feinler (SRI-ARC)\nNIC # 22152 March 7, 1974\n\n ON LINE HOSTNAMES SERVICE\n\nWe agree with the suggestion in RFC 623 that more than one Host should\nbe responsible for maintaining a copy of the Hostnames data base. The\nNIC is certainly willing to continue to maintain the master data base,\nand make it available to any secondary Host that volunteers to maintain\na copy. We would be pleased to have UCSB serve as one of the secondary\nHosts.\n\nHowever, we disagree with the suggestion in RFC 623 that a server\nprocess should be implemented to give user processes access to the\nofficial Hostnames file at the NIC. The file in question is a\nsequential file and it seems to us that FTP is entirely appropriate for\nthis need. As far as setting up common login parameters among the\nservers, this doesn't appear to be a major problem. Even with a\nuser/se 625 nested-reference unchanged"},{"id":"IETF RFC 6271","type":"specification","body":"IETF","designation":"RFC 6271","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6271.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6271.txt","https://www.rfc-editor.org/rfc/rfc6271.pdf"],"folder":"IETF/RFC-6271","files":{"txt":{"path":"standards/IETF/RFC-6271/RFC-6271.txt","sha256":"408f72b6a0151e1369c482823daad1fade5a7c3882e59471ea61b6c5969da2ba"}},"tags":["nested-reference","unchanged"],"summary":"This memo captures protocol requirements to enable session peering of\n voice, presence, instant messaging, and other types of multimedia\n traffic. This informational document is intended to link the various\n use cases described for session peering to protocol solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http","scope_keywords":["6271","authentication","http","key","license","management","path","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 6271 This memo captures protocol requirements to enable session peering of\n voice, presence, instant messaging, and other types of multimedia\n traffic. This informational document is intended to link the various\n use cases described for session peering to protocol solutions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http 6271 authentication http key license management path policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 630","type":"specification","body":"IETF","designation":"RFC 630","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc630.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc630.txt","https://www.rfc-editor.org/rfc/rfc630.pdf"],"folder":"IETF/RFC-630","files":{"txt":{"path":"standards/IETF/RFC-630/RFC-630.txt","sha256":"073437a9deb69098ca3624babbcf663e503e27d194ed3b16d9918eb2d6e82d28"}},"tags":["nested-reference","unchanged"],"summary":"A major hindrance to providing reliable mail service is the lack of\nwell-defined FTP error replies that would enable a mailing process to\ndecide how to handle a failure. New FTP error codes are currently in\nthe design stage, and a proposal will be announced soon. In the\ninterim, we can get some improvement by simply defining how we intend to\nuse the current FTP codes. The purpose of this RFC is to inform all\nsites of how TENEX sites will use and interpret the codes starting in\nthe near future.","scope_keywords":["630"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 686","folder":"IETF/RFC-686","source":"IETF/RFC-686/RFC-686.txt","version":null},{"body":"IETF","designation":"RFC 691","folder":"IETF/RFC-691","source":"IETF/RFC-691/RFC-691.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 630 A major hindrance to providing reliable mail service is the lack of\nwell-defined FTP error replies that would enable a mailing process to\ndecide how to handle a failure. New FTP error codes are currently in\nthe design stage, and a proposal will be announced soon. In the\ninterim, we can get some improvement by simply defining how we intend to\nuse the current FTP codes. The purpose of this RFC is to inform all\nsites of how TENEX sites will use and interpret the codes starting in\nthe near future. 630 nested-reference unchanged"},{"id":"IETF RFC 6310","type":"specification","body":"IETF","designation":"RFC 6310","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6310.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6310.txt","https://www.rfc-editor.org/rfc/rfc6310.pdf"],"folder":"IETF/RFC-6310","files":{"txt":{"path":"standards/IETF/RFC-6310/RFC-6310.txt","sha256":"22c8539e5259fa0b95d2a2f011fa293406d0edd5fdd6ee94b8e89c4f48e6ec5a"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the mapping and notification of defect states\n between a pseudowire (PW) and the Attachment Circuits (ACs) of the\n end-to-end emulated service. It standardizes the behavior of\n Provider Edges (PEs) with respect to PW and AC defects. It addresses\n ATM, Frame Relay, Time Division Multiplexing (TDM), and Synchronous\n Optical Network / Synchronous Digital Hierarchy (SONET/SDH) PW\n services, carried over MPLS, MPLS/IP, and Layer 2 Tunneling Protocol\n version 3/IP (L2TPv3/IP) Packet Switched Networks (PSNs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai","scope_keywords":["6310","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6310 This document specifies the mapping and notification of defect states\n between a pseudowire (PW) and the Attachment Circuits (ACs) of the\n end-to-end emulated service. It standardizes the behavior of\n Provider Edges (PEs) with respect to PW and AC defects. It addresses\n ATM, Frame Relay, Time Division Multiplexing (TDM), and Synchronous\n Optical Network / Synchronous Digital Hierarchy (SONET/SDH) PW\n services, carried over MPLS, MPLS/IP, and Layer 2 Tunneling Protocol\n version 3/IP (L2TPv3/IP) Packet Switched Networks (PSNs).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is avai 6310 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 633","type":"specification","body":"IETF","designation":"RFC 633","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc633.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc633.txt","https://www.rfc-editor.org/rfc/rfc633.pdf"],"folder":"IETF/RFC-633","files":{"txt":{"path":"standards/IETF/RFC-633/RFC-633.txt","sha256":"3776bdf25bfb5a8040ef6990835fb7e24ec2f649cde45700695af807fe479996"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. McKenzie\nRequest for Comments: 633 BBN-NET\nNIC: 30240 March 18, 1974\n\n IMP/TIP Preventive Maintenance Schedule\n\n This note presents the current IMP/TIP Preventive Maintenance\n schedule. Preventive Maintenance is scheduled on a monthly basis and\n a given machine is normally scheduled at the same time each month;\n wherever possible the time is chosen to coincide with the PM time for\n the Host(s) at the site.\n\n It is sometimes necessary to reschedule PM's because of network\n connectivity considerations or for other reasons. Whenever this is\n necessary we will follow the usual procedure for scheduling down time\n with our \"primary contact\" at the site. Permanent changes to the\n schedule will he announced via the RFC mechanism.\n\n PM's normally do not require the IMP/TIP to be taken down. However,\n machines must be taken down in some cases, so no one should rely on\n the","scope_keywords":["633"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 633 Network Working Group A. McKenzie\nRequest for Comments: 633 BBN-NET\nNIC: 30240 March 18, 1974\n\n IMP/TIP Preventive Maintenance Schedule\n\n This note presents the current IMP/TIP Preventive Maintenance\n schedule. Preventive Maintenance is scheduled on a monthly basis and\n a given machine is normally scheduled at the same time each month;\n wherever possible the time is chosen to coincide with the PM time for\n the Host(s) at the site.\n\n It is sometimes necessary to reschedule PM's because of network\n connectivity considerations or for other reasons. Whenever this is\n necessary we will follow the usual procedure for scheduling down time\n with our \"primary contact\" at the site. Permanent changes to the\n schedule will he announced via the RFC mechanism.\n\n PM's normally do not require the IMP/TIP to be taken down. However,\n machines must be taken down in some cases, so no one should rely on\n the 633 nested-reference unchanged"},{"id":"IETF RFC 6373","type":"specification","body":"IETF","designation":"RFC 6373","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6373.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6373.txt","https://www.rfc-editor.org/rfc/rfc6373.pdf"],"folder":"IETF/RFC-6373","files":{"txt":{"path":"standards/IETF/RFC-6373/RFC-6373.txt","sha256":"c1763ee7abdb5ec744618f02e5ec894924b238ccc609c3ed96ffa50d3c0d09d6"}},"tags":["nested-reference","unchanged"],"summary":"The MPLS Transport Profile (MPLS-TP) supports static provisioning of\n transport paths via a Network Management System (NMS) and dynamic\n provisioning of transport paths via a control plane. This document\n provides the framework for MPLS-TP dynamic provisioning and covers\n control-plane addressing, routing, path computation, signaling,\n traffic engineering, and path recovery. MPLS-TP uses GMPLS as the\n control plane for MPLS-TP Label Switched Paths (LSPs). MPLS-TP also\n uses the pseudowire (PW) control plane for pseudowires. Management-\n plane functions are out of scope of this document.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support","scope_keywords":["6373","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6372","folder":"IETF/RFC-6372","source":"IETF/RFC-6372/RFC-6372.txt","version":null}],"search_text":"IETF RFC 6373 The MPLS Transport Profile (MPLS-TP) supports static provisioning of\n transport paths via a Network Management System (NMS) and dynamic\n provisioning of transport paths via a control plane. This document\n provides the framework for MPLS-TP dynamic provisioning and covers\n control-plane addressing, routing, path computation, signaling,\n traffic engineering, and path recovery. MPLS-TP uses GMPLS as the\n control plane for MPLS-TP Label Switched Paths (LSPs). MPLS-TP also\n uses the pseudowire (PW) control plane for pseudowires. Management-\n plane functions are out of scope of this document.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support 6373 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6375","type":"specification","body":"IETF","designation":"RFC 6375","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6375.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6375.txt","https://www.rfc-editor.org/rfc/rfc6375.pdf"],"folder":"IETF/RFC-6375","files":{"txt":{"path":"standards/IETF/RFC-6375/RFC-6375.txt","sha256":"94f1576a31df36719153478ee0db97d7f49495592bfce9f6d61437fcbe11b889"}},"tags":["nested-reference","unchanged"],"summary":"Procedures and protocol mechanisms to enable efficient and accurate\n measurement of packet loss, delay, and throughput in MPLS networks\n are defined in RFC 6374.\n\n The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol\n functions applicable to the construction and operation of packet-\n switched transport networks.\n\n This document describes a profile of the general MPLS loss, delay,\n and throughput measurement techniques that suffices to meet the\n specific requirements of MPLS-TP.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nStat","scope_keywords":["6375","http","license","management","path","profile","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6375 Procedures and protocol mechanisms to enable efficient and accurate\n measurement of packet loss, delay, and throughput in MPLS networks\n are defined in RFC 6374.\n\n The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol\n functions applicable to the construction and operation of packet-\n switched transport networks.\n\n This document describes a profile of the general MPLS loss, delay,\n and throughput measurement techniques that suffices to meet the\n specific requirements of MPLS-TP.\n\n This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunication Union Telecommunication\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\nStat 6375 http license management path profile subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 6378","type":"specification","body":"IETF","designation":"RFC 6378","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6378.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6378.txt","https://www.rfc-editor.org/rfc/rfc6378.pdf"],"folder":"IETF/RFC-6378","files":{"txt":{"path":"standards/IETF/RFC-6378/RFC-6378.txt","sha256":"e6c1f3424d2e06eeb0fca7033be1dd14d3f0f172b3279ab06ef0f04ff5286490"}},"tags":["nested-reference","unchanged"],"summary":"This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunications Union Telecommunications\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\n This document addresses the functionality described in the MPLS-TP\n Survivability Framework document (RFC 6372) and defines a protocol\n that may be used to fulfill the function of the Protection State\n Coordination for linear protection, as described in that document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a","scope_keywords":["6378","delivery","http","license","path","pid","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6378 This document is a product of a joint Internet Engineering Task Force\n (IETF) / International Telecommunications Union Telecommunications\n Standardization Sector (ITU-T) effort to include an MPLS Transport\n Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge\n (PWE3) architectures to support the capabilities and functionalities\n of a packet transport network as defined by the ITU-T.\n\n This document addresses the functionality described in the MPLS-TP\n Survivability Framework document (RFC 6372) and defines a protocol\n that may be used to fulfill the function of the Protection State\n Coordination for linear protection, as described in that document.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review a 6378 delivery http license path pid profile subject trust nested-reference unchanged"},{"id":"IETF RFC 638","type":"specification","body":"IETF","designation":"RFC 638","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc638.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc638.txt","https://www.rfc-editor.org/rfc/rfc638.pdf"],"folder":"IETF/RFC-638","files":{"txt":{"path":"standards/IETF/RFC-638/RFC-638.txt","sha256":"2996fe499d6f7e3c5b90a729f7be3a7a1558422dd38fa89fda8d8c227378bc36"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Alex A. McKenzie\nRequest for Comments: 638 BBN-NET\nNIC: 30538 April 25, 1974\n\n IMP/TIP Preventive Maintenance Schedule\n\n This RFC corrects numerous inaccuracies in RFC #633. Rather than\n trying to list all the changes, I urge all Liaisons and other\n interested parties to look carefully at the times now listed for\n the sites they are interested in.\n\n This note presents the current IMP/TIP Preventive Maintenance\n schedule. Preventive Maintenance is scheduled on a monthly basis and\n a given machine is normally scheduled at the same time each month;\n wherever possible the time is chosen to coincide with the PM time for\n the Host(s) at the site.\n\n It is sometimes necessary to reschedule PM's because of network\n connectivity considerations or for other reasons. Whenever this is\n necessary we will follow the usual procedure for scheduling down time\n with our \"primary conta","scope_keywords":["638"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 638 Network Working Group Alex A. McKenzie\nRequest for Comments: 638 BBN-NET\nNIC: 30538 April 25, 1974\n\n IMP/TIP Preventive Maintenance Schedule\n\n This RFC corrects numerous inaccuracies in RFC #633. Rather than\n trying to list all the changes, I urge all Liaisons and other\n interested parties to look carefully at the times now listed for\n the sites they are interested in.\n\n This note presents the current IMP/TIP Preventive Maintenance\n schedule. Preventive Maintenance is scheduled on a monthly basis and\n a given machine is normally scheduled at the same time each month;\n wherever possible the time is chosen to coincide with the PM time for\n the Host(s) at the site.\n\n It is sometimes necessary to reschedule PM's because of network\n connectivity considerations or for other reasons. Whenever this is\n necessary we will follow the usual procedure for scheduling down time\n with our \"primary conta 638 nested-reference unchanged"},{"id":"IETF RFC 6404","type":"specification","body":"IETF","designation":"RFC 6404","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6404.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6404.txt","https://www.rfc-editor.org/rfc/rfc6404.pdf"],"folder":"IETF/RFC-6404","files":{"txt":{"path":"standards/IETF/RFC-6404/RFC-6404.txt","sha256":"91fb3271f5de5d1e3ac520e0b5226f4cebaa35c658d8b572f0dcf99870ab9d8d"}},"tags":["nested-reference","unchanged"],"summary":"The Session PEERing for Multimedia INTerconnect (SPEERMINT) working\n group (WG) provides a peering framework that leverages the building\n blocks of existing IETF-defined protocols such as SIP and ENUM for\n the interconnection between SIP Service Providers (SSPs). The\n objective of this document is to identify and enumerate SPEERMINT-\n specific threat vectors and to give guidance for implementers on\n selecting appropriate countermeasures. Security requirements for\n SPEERMINT that have been derived from the threats detailed in this\n document can be found in RFC 6271; this document provides concrete\n countermeasures to meet those SPEERMINT security requirements. In\n this document, the different security threats related to SPEERMINT\n are classified into threats to the Lookup Function (LUF), the\n Location Routing Function (LRF), the Signaling Function (SF), and the\n Media Function (MF) of a s","scope_keywords":["6404","encryption","http","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 6404 The Session PEERing for Multimedia INTerconnect (SPEERMINT) working\n group (WG) provides a peering framework that leverages the building\n blocks of existing IETF-defined protocols such as SIP and ENUM for\n the interconnection between SIP Service Providers (SSPs). The\n objective of this document is to identify and enumerate SPEERMINT-\n specific threat vectors and to give guidance for implementers on\n selecting appropriate countermeasures. Security requirements for\n SPEERMINT that have been derived from the threats detailed in this\n document can be found in RFC 6271; this document provides concrete\n countermeasures to meet those SPEERMINT security requirements. In\n this document, the different security threats related to SPEERMINT\n are classified into threats to the Lookup Function (LUF), the\n Location Routing Function (LRF), the Signaling Function (SF), and the\n Media Function (MF) of a s 6404 encryption http license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6405","type":"specification","body":"IETF","designation":"RFC 6405","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6405.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6405.txt","https://www.rfc-editor.org/rfc/rfc6405.pdf"],"folder":"IETF/RFC-6405","files":{"txt":{"path":"standards/IETF/RFC-6405/RFC-6405.txt","sha256":"aa80386de311ec7aeafc0e027bd1e4073100e28805de6bdbf061e7abf4bb2111"}},"tags":["nested-reference","unchanged"],"summary":"This document depicts many common Voice over IP (VoIP) use cases for\n Session Initiation Protocol (SIP) peering. These use cases are\n categorized into static and on-demand, and then further sub-\n categorized into direct and indirect. These use cases are not an\n exhaustive set, but rather the most common use cases deployed today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,","scope_keywords":["6405","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6406","folder":"IETF/RFC-6406","source":"IETF/RFC-6406/RFC-6406.txt","version":null}],"search_text":"IETF RFC 6405 This document depicts many common Voice over IP (VoIP) use cases for\n Session Initiation Protocol (SIP) peering. These use cases are\n categorized into static and on-demand, and then further sub-\n categorized into direct and indirect. These use cases are not an\n exhaustive set, but rather the most common use cases deployed today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata, 6405 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6423","type":"specification","body":"IETF","designation":"RFC 6423","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6423.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6423.txt","https://www.rfc-editor.org/rfc/rfc6423.pdf"],"folder":"IETF/RFC-6423","files":{"txt":{"path":"standards/IETF/RFC-6423/RFC-6423.txt","sha256":"791b34b7cbd4ab21c47813eef171d377c4ddb5d6a6f3b4d4c7a6978c4e2b989c"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the requirements for using the Generic\n Associated Channel Label (GAL) in pseudowires (PWs) in MPLS Transport\n Profile (MPLS-TP) networks, and provides an update to the description\n of GAL usage in RFC 5586 by removing the restriction that is imposed\n on using GAL for PWs, especially in MPLS-TP environments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6423.\n\nL","scope_keywords":["6423","http","key","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 6423 This document describes the requirements for using the Generic\n Associated Channel Label (GAL) in pseudowires (PWs) in MPLS Transport\n Profile (MPLS-TP) networks, and provides an update to the description\n of GAL usage in RFC 5586 by removing the restriction that is imposed\n on using GAL for PWs, especially in MPLS-TP environments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6423.\n\nL 6423 http key license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6426","type":"specification","body":"IETF","designation":"RFC 6426","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6426.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6426.txt","https://www.rfc-editor.org/rfc/rfc6426.pdf"],"folder":"IETF/RFC-6426","files":{"txt":{"path":"standards/IETF/RFC-6426/RFC-6426.txt","sha256":"75c31a18641dae888fe8942d6c108f95e8857f23994eaa7b80f9b3e5527e355c"}},"tags":["nested-reference","unchanged"],"summary":"Label Switched Path Ping (LSP ping) is an existing and widely\n deployed Operations, Administration, and Maintenance (OAM) mechanism\n for Multi-Protocol Label Switching (MPLS) Label Switched Paths\n (LSPs). This document describes extensions to LSP ping so that LSP\n ping can be used for on-demand connectivity verification of MPLS\n Transport Profile (MPLS-TP) LSPs and pseudowires. This document also\n clarifies procedures to be used for processing the related OAM\n packets. Further, it describes procedures for using LSP ping to\n perform connectivity verification and route tracing functions in\n MPLS-TP networks. Finally, this document updates RFC 4379 by adding\n a new address type and creating an IANA registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF","scope_keywords":["6426","http","key","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6426 Label Switched Path Ping (LSP ping) is an existing and widely\n deployed Operations, Administration, and Maintenance (OAM) mechanism\n for Multi-Protocol Label Switching (MPLS) Label Switched Paths\n (LSPs). This document describes extensions to LSP ping so that LSP\n ping can be used for on-demand connectivity verification of MPLS\n Transport Profile (MPLS-TP) LSPs and pseudowires. This document also\n clarifies procedures to be used for processing the related OAM\n packets. Further, it describes procedures for using LSP ping to\n perform connectivity verification and route tracing functions in\n MPLS-TP networks. Finally, this document updates RFC 4379 by adding\n a new address type and creating an IANA registry.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF 6426 http key license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6427","type":"specification","body":"IETF","designation":"RFC 6427","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6427.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6427.txt","https://www.rfc-editor.org/rfc/rfc6427.pdf"],"folder":"IETF/RFC-6427","files":{"txt":{"path":"standards/IETF/RFC-6427/RFC-6427.txt","sha256":"2c9c53a1f801703decc825aec34e78ec9488800de33da110b8739343503bb5c4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies Operations, Administration, and Maintenance\n (OAM) messages to indicate service disruptive conditions for MPLS-\n based transport network Label Switched Paths. The notification\n mechanism employs a generic method for a service disruptive condition\n to be communicated to a Maintenance Entity Group End Point. This\n document defines an MPLS OAM channel, along with messages to\n communicate various types of service disruptive conditions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status o","scope_keywords":["6427","http","license","management","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6427 This document specifies Operations, Administration, and Maintenance\n (OAM) messages to indicate service disruptive conditions for MPLS-\n based transport network Label Switched Paths. The notification\n mechanism employs a generic method for a service disruptive condition\n to be communicated to a Maintenance Entity Group End Point. This\n document defines an MPLS OAM channel, along with messages to\n communicate various types of service disruptive conditions.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status o 6427 http license management path subject trust nested-reference unchanged"},{"id":"IETF RFC 6428","type":"specification","body":"IETF","designation":"RFC 6428","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6428.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6428.txt","https://www.rfc-editor.org/rfc/rfc6428.pdf"],"folder":"IETF/RFC-6428","files":{"txt":{"path":"standards/IETF/RFC-6428/RFC-6428.txt","sha256":"434d9ab2df5169740cb717e40a802280d2daed6cdcaa33630273344cd80945b4"}},"tags":["nested-reference","unchanged"],"summary":"Continuity Check, Proactive Connectivity Verification, and Remote\n Defect Indication functionalities are required for MPLS Transport\n Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM).\n\n Continuity Check monitors a Label Switched Path for any loss of\n continuity defect. Connectivity Verification augments Continuity\n Check in order to provide confirmation that the desired source is\n connected to the desired sink. Remote Defect Indication enables an\n end point to report, to its associated end point, a fault or defect\n condition that it detects on a pseudowire, Label Switched Path, or\n Section.\n\n This document specifies specific extensions to Bidirectional\n Forwarding Detection (BFD) and methods for proactive Continuity\n Check, Continuity Verification, and Remote Defect Indication for\n MPLS-TP pseudowires, Label Switched Paths, and Sections using BFD as\n extended by this m","scope_keywords":["6428","http","license","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6428 Continuity Check, Proactive Connectivity Verification, and Remote\n Defect Indication functionalities are required for MPLS Transport\n Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM).\n\n Continuity Check monitors a Label Switched Path for any loss of\n continuity defect. Connectivity Verification augments Continuity\n Check in order to provide confirmation that the desired source is\n connected to the desired sink. Remote Defect Indication enables an\n end point to report, to its associated end point, a fault or defect\n condition that it detects on a pseudowire, Label Switched Path, or\n Section.\n\n This document specifies specific extensions to Bidirectional\n Forwarding Detection (BFD) and methods for proactive Continuity\n Check, Continuity Verification, and Remote Defect Indication for\n MPLS-TP pseudowires, Label Switched Paths, and Sections using BFD as\n extended by this m 6428 http license path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 643","type":"specification","body":"IETF","designation":"RFC 643","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc643.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc643.txt","https://www.rfc-editor.org/rfc/rfc643.pdf"],"folder":"IETF/RFC-643","files":{"txt":{"path":"standards/IETF/RFC-643/RFC-643.txt","sha256":"099d8eee477c2747f183670f94c4ff0fdaa3d5be8a64242fdd55d1299574942b"}},"tags":["nested-reference","unchanged"],"summary":"Network Debugging Protocol Eric Mader\nRFC: 643 July 1974\nNIC #30873\n\n This document describes a proposed protocol to be used in an\nimplementation of a PDP-11 network Bootstrap service and a\ncross-network debugger. The protocol is designed for debugging\nprocesses running under an operating system which can perform some of\nthe \"lower level\" debugging tasks, such as planting and removing\nbreakpoints and single stepping. A subset of the protocol could be\nused if such a capability does not exist (a stand-alone program for\nexample).\n\n The protocol is a level 2 protocol, which bypasses the ARPANET\nHOST-HOST protocol. (This is implemented on TENEX using special\nprivileged system calls which allow messages to be sent directly to\nand received directly from the IMP). Messages are sent between the\nPDP-11 and the remote debugger on one link (currently 377 octal).\nEach message from the remote debugger","scope_keywords":["643"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 643 Network Debugging Protocol Eric Mader\nRFC: 643 July 1974\nNIC #30873\n\n This document describes a proposed protocol to be used in an\nimplementation of a PDP-11 network Bootstrap service and a\ncross-network debugger. The protocol is designed for debugging\nprocesses running under an operating system which can perform some of\nthe \"lower level\" debugging tasks, such as planting and removing\nbreakpoints and single stepping. A subset of the protocol could be\nused if such a capability does not exist (a stand-alone program for\nexample).\n\n The protocol is a level 2 protocol, which bypasses the ARPANET\nHOST-HOST protocol. (This is implemented on TENEX using special\nprivileged system calls which allow messages to be sent directly to\nand received directly from the IMP). Messages are sent between the\nPDP-11 and the remote debugger on one link (currently 377 octal).\nEach message from the remote debugger 643 nested-reference unchanged"},{"id":"IETF RFC 6435","type":"specification","body":"IETF","designation":"RFC 6435","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6435.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6435.txt","https://www.rfc-editor.org/rfc/rfc6435.pdf"],"folder":"IETF/RFC-6435","files":{"txt":{"path":"standards/IETF/RFC-6435/RFC-6435.txt","sha256":"c9bcf66dac59e7292caf9bcf9d1ccaf7f984cbae5de79afb3db5dc52e695cdcc"}},"tags":["nested-reference","unchanged"],"summary":"Two useful Operations, Administration, and Maintenance (OAM)\n functions in a transport network are \"lock\" and \"loopback\". The lock\n function enables an operator to lock a transport path such that it\n does not carry client traffic, but can continue to carry OAM messages\n and may carry test traffic. The loopback function allows an operator\n to set a specific node on the transport path into loopback mode such\n that it returns all received data.\n\n This document specifies the lock function for MPLS networks and\n describes how the loopback function operates in MPLS networks.\n\n This document updates Sections 7.1.1 and 7.1.2 of RFC 6371.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publicat","scope_keywords":["6435","http","key","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6435 Two useful Operations, Administration, and Maintenance (OAM)\n functions in a transport network are \"lock\" and \"loopback\". The lock\n function enables an operator to lock a transport path such that it\n does not carry client traffic, but can continue to carry OAM messages\n and may carry test traffic. The loopback function allows an operator\n to set a specific node on the transport path into loopback mode such\n that it returns all received data.\n\n This document specifies the lock function for MPLS networks and\n describes how the loopback function operates in MPLS networks.\n\n This document updates Sections 7.1.1 and 7.1.2 of RFC 6371.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publicat 6435 http key license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6478","type":"specification","body":"IETF","designation":"RFC 6478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6478.txt","https://www.rfc-editor.org/rfc/rfc6478.pdf"],"folder":"IETF/RFC-6478","files":{"txt":{"path":"standards/IETF/RFC-6478/RFC-6478.txt","sha256":"aeab92020aa5ee74171233b68c8dfb4bf7b81673ec2ce9b372f2489c5a211746"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a mechanism to signal Pseudowire (PW) status\n messages using a PW associated channel (ACh). Such a mechanism is\n suitable for use where no PW dynamic control plane exits, known as\n static PWs, or where a Terminating Provider Edge (T-PE) needs to send\n a PW status message directly to a far-end T-PE. The mechanism allows\n PW Operations, Administration, and Maintenance (OAM) message mapping\n and PW redundancy to operate on static PWs. This document also\n updates RFC 5885 in the case when Bi-directional Forwarding Detection\n (BFD) is used to convey PW status-signaling information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri","scope_keywords":["6478","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6478 This document specifies a mechanism to signal Pseudowire (PW) status\n messages using a PW associated channel (ACh). Such a mechanism is\n suitable for use where no PW dynamic control plane exits, known as\n static PWs, or where a Terminating Provider Edge (T-PE) needs to send\n a PW status message directly to a far-end T-PE. The mechanism allows\n PW Operations, Administration, and Maintenance (OAM) message mapping\n and PW redundancy to operate on static PWs. This document also\n updates RFC 5885 in the case when Bi-directional Forwarding Detection\n (BFD) is used to convey PW status-signaling information.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineeri 6478 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 6502","type":"specification","body":"IETF","designation":"RFC 6502","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6502.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6502.txt","https://www.rfc-editor.org/rfc/rfc6502.pdf"],"folder":"IETF/RFC-6502","files":{"txt":{"path":"standards/IETF/RFC-6502/RFC-6502.txt","sha256":"de9b6153d986855f7e8babd4faf326fe2fc68fdc8c5be43b45f59d26ff9ca127"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the notification mechanism for XCON\n (centralized conferencing). This mechanism reuses the SIP (Session\n Initiation Protocol) event package for conference state.\n Additionally, the notification mechanism includes support for the\n XCON data model and for partial notifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6502.\n\nCamarillo, et al. Standards Track ","scope_keywords":["6502","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6503","folder":"IETF/RFC-6503","source":"IETF/RFC-6503/RFC-6503.txt","version":null},{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null}],"search_text":"IETF RFC 6502 This document specifies the notification mechanism for XCON\n (centralized conferencing). This mechanism reuses the SIP (Session\n Initiation Protocol) event package for conference state.\n Additionally, the notification mechanism includes support for the\n XCON data model and for partial notifications.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6502.\n\nCamarillo, et al. Standards Track  6502 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6505","type":"specification","body":"IETF","designation":"RFC 6505","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6505.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6505.txt","https://www.rfc-editor.org/rfc/rfc6505.pdf"],"folder":"IETF/RFC-6505","files":{"txt":{"path":"standards/IETF/RFC-6505/RFC-6505.txt","sha256":"6d770719abfabd28eb8083f6021fb43cf822cb8ad2a468ed82894be25389ff59"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a Media Control Channel Framework Package for\n managing mixers for media conferences and connections. The package\n defines request elements for managing conference mixers, managing\n mixers between conferences and/or connections, as well as associated\n responses and notifications. The package also defines elements for\n auditing package capabilities and mixers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai","scope_keywords":["6505","audit","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6504","folder":"IETF/RFC-6504","source":"IETF/RFC-6504/RFC-6504.txt","version":null}],"search_text":"IETF RFC 6505 This document defines a Media Control Channel Framework Package for\n managing mixers for media conferences and connections. The package\n defines request elements for managing conference mixers, managing\n mixers between conferences and/or connections, as well as associated\n responses and notifications. The package also defines elements for\n auditing package capabilities and mixers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtai 6505 audit http license subject trust nested-reference unchanged"},{"id":"IETF RFC 651","type":"specification","body":"IETF","designation":"RFC 651","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc651.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc651.txt","https://www.rfc-editor.org/rfc/rfc651.pdf"],"folder":"IETF/RFC-651","files":{"txt":{"path":"standards/IETF/RFC-651/RFC-651.txt","sha256":"8c85b80acef05f06759f3e8e4da65bbac6e13dbb1f1721cb89072a31745c2154"}},"tags":["nested-reference","unchanged"],"summary":"Revised Telnet Status Option\nNIC 31154 (25 Oct. 74)\nRequest for Comments: 651\nD. Crocker (UCLA-NMC) 25 Oct. 74\nRFC# 651\nOnline file: STATUS-OPTION-REVISION.RNO\n\n Revised Telnet Status Option\n1. Command name and code\n STATUS 5\n2. Command meanings\n As described in the NAOL and NAOP option specifications, this option applies\n to a simplex connection.\n IAC DO STATUS \n Sender of DO wishes to be able to send requests for status-of-options \n information, or confirms that he is willing to send such requests.\n IAC WILL STATUS \n Sender of WILL wishes or agrees to send status information, \n spontaneously or in response to future requests.\n IAC DON'T STATUS \n Sender refuses to carry on any further discussion of the current \n status of options.\n IAC WON'T STATUS \n Sender refuses to carry on any further discussion of the current \n status of options.\n IAC SB STATUS SEND IAC SE\n Sender requests receiver","scope_keywords":["651"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 859","folder":"IETF/RFC-859","source":"IETF/RFC-859/RFC-859.txt","version":null}],"search_text":"IETF RFC 651 Revised Telnet Status Option\nNIC 31154 (25 Oct. 74)\nRequest for Comments: 651\nD. Crocker (UCLA-NMC) 25 Oct. 74\nRFC# 651\nOnline file: STATUS-OPTION-REVISION.RNO\n\n Revised Telnet Status Option\n1. Command name and code\n STATUS 5\n2. Command meanings\n As described in the NAOL and NAOP option specifications, this option applies\n to a simplex connection.\n IAC DO STATUS \n Sender of DO wishes to be able to send requests for status-of-options \n information, or confirms that he is willing to send such requests.\n IAC WILL STATUS \n Sender of WILL wishes or agrees to send status information, \n spontaneously or in response to future requests.\n IAC DON'T STATUS \n Sender refuses to carry on any further discussion of the current \n status of options.\n IAC WON'T STATUS \n Sender refuses to carry on any further discussion of the current \n status of options.\n IAC SB STATUS SEND IAC SE\n Sender requests receiver 651 nested-reference unchanged"},{"id":"IETF RFC 859","type":"specification","body":"IETF","designation":"RFC 859","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc859.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc859.txt","https://www.rfc-editor.org/rfc/rfc859.pdf"],"folder":"IETF/RFC-859","files":{"txt":{"path":"standards/IETF/RFC-859/RFC-859.txt","sha256":"38c81d449e57c3ad890db913c56616acd0d18f95cda1b7aacebe10b18418b76d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 859 J. Reynolds\n ISI\nObsoletes: RFC 651 (NIC 31154) May 1983\n\n TELNET STATUS OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n STATUS 5\n\n2. Command Meanings\n\n This option applies separately to each direction of data flow.\n\n IAC DON'T STATUS\n\n Sender refuses to carry on any further discussion of the current\n status of options.\n\n IAC WON'T STATUS\n\n Sender refuses to carry on any further discussion of the current\n status of options.\n\n IAC SB STATUS SEND IAC SE\n\n Sender requests receiver to transmit his (the receiver's)\n perception of the current status of Telnet options. The code for\n SEND is 1. (See below.)\n\n IAC SB STATUS IS ... IAC SE\n\n Sender is stating his perception of the current status of Telnet\n options.","scope_keywords":["859"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 859 Network Working Group J. Postel\nRequest for Comments: 859 J. Reynolds\n ISI\nObsoletes: RFC 651 (NIC 31154) May 1983\n\n TELNET STATUS OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n STATUS 5\n\n2. Command Meanings\n\n This option applies separately to each direction of data flow.\n\n IAC DON'T STATUS\n\n Sender refuses to carry on any further discussion of the current\n status of options.\n\n IAC WON'T STATUS\n\n Sender refuses to carry on any further discussion of the current\n status of options.\n\n IAC SB STATUS SEND IAC SE\n\n Sender requests receiver to transmit his (the receiver's)\n perception of the current status of Telnet options. The code for\n SEND is 1. (See below.)\n\n IAC SB STATUS IS ... IAC SE\n\n Sender is stating his perception of the current status of Telnet\n options. 859 nested-reference unchanged"},{"id":"IETF RFC 652","type":"specification","body":"IETF","designation":"RFC 652","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc652.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc652.txt","https://www.rfc-editor.org/rfc/rfc652.pdf"],"folder":"IETF/RFC-652","files":{"txt":{"path":"standards/IETF/RFC-652/RFC-652.txt","sha256":"d0c5858518801ffbbb611b05589177a59dcb3efb1c6ea5538cd7c6e92023a0e6"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 652 D. Crocker (UCLA-NMC)\n 25 Oct. 74\nNIC #31155\nOnline file: [ISI] NAOCRD.TXT\n\n Telnet Output Carriage-Return Disposition Option\n\n1. Command name and code\n\n NAOCRD 10 (Negotiate About Output Carriage-Return Disposition)\n\n2. Command meanings\n\n In the following, we are discussing a simplex connection, as\n described in the NAOL and NAOP Telnet options.\n\n IAC DO NAOCRD The data sender requests or agrees to negotiate\n about output carriage-return character\n disposition with the data receiver. In the\n case where agreement has been reached and in\n the absence of further subnegotiations, the\n data receiver is assumed to be handling output\n carriage-returns.\n\n IAC DON'T NAOCRD The data sender refuses to negotiate about\n output carriage-return disposition with the\n data receiver, or demands a return to the\n unnegotiated default mode.\n\n IAC WILL NAOCRD The data receiver reque","scope_keywords":["652"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 652 Request for Comments: 652 D. Crocker (UCLA-NMC)\n 25 Oct. 74\nNIC #31155\nOnline file: [ISI] NAOCRD.TXT\n\n Telnet Output Carriage-Return Disposition Option\n\n1. Command name and code\n\n NAOCRD 10 (Negotiate About Output Carriage-Return Disposition)\n\n2. Command meanings\n\n In the following, we are discussing a simplex connection, as\n described in the NAOL and NAOP Telnet options.\n\n IAC DO NAOCRD The data sender requests or agrees to negotiate\n about output carriage-return character\n disposition with the data receiver. In the\n case where agreement has been reached and in\n the absence of further subnegotiations, the\n data receiver is assumed to be handling output\n carriage-returns.\n\n IAC DON'T NAOCRD The data sender refuses to negotiate about\n output carriage-return disposition with the\n data receiver, or demands a return to the\n unnegotiated default mode.\n\n IAC WILL NAOCRD The data receiver reque 652 nested-reference unchanged"},{"id":"IETF RFC 653","type":"specification","body":"IETF","designation":"RFC 653","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc653.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc653.txt","https://www.rfc-editor.org/rfc/rfc653.pdf"],"folder":"IETF/RFC-653","files":{"txt":{"path":"standards/IETF/RFC-653/RFC-653.txt","sha256":"7c9eef8e4f62a38dabfdddd156e6361c97a95e5156fd9359be15cb33c86c0509"}},"tags":["nested-reference","unchanged"],"summary":"TELNET OUTPUT HORIZONTAL TABSTOPS OPTION\nRFC 653, NIC 31156 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOHTS.TXT\n\n TELNET OUTPUT HORIZONTAL TABSTOPS OPTION\n\n1. Command name and code\n NAOHTS 11 (Negotiate About Output Horizontal Tabstops)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet options.\n IAC DO NAOHTS \n The data sender requests or agrees to negotiate about output \n horizontal tabstops with the data receiver. In the case where \n agreement has been reached and in the absence of further \n subnegotiations, the data receiver is assumed to be handling output \n horizontal tabstops.\n IAC DON'T NAOHTS \n The data sender refuses to negotiate about output horizontal tabstops \n with the data receiver, or demands a return to the unnegotiated \n default mode.\n IAC WILL NAOHTS \n The data receiver requests or ","scope_keywords":["653"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 653 TELNET OUTPUT HORIZONTAL TABSTOPS OPTION\nRFC 653, NIC 31156 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOHTS.TXT\n\n TELNET OUTPUT HORIZONTAL TABSTOPS OPTION\n\n1. Command name and code\n NAOHTS 11 (Negotiate About Output Horizontal Tabstops)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet options.\n IAC DO NAOHTS \n The data sender requests or agrees to negotiate about output \n horizontal tabstops with the data receiver. In the case where \n agreement has been reached and in the absence of further \n subnegotiations, the data receiver is assumed to be handling output \n horizontal tabstops.\n IAC DON'T NAOHTS \n The data sender refuses to negotiate about output horizontal tabstops \n with the data receiver, or demands a return to the unnegotiated \n default mode.\n IAC WILL NAOHTS \n The data receiver requests or  653 nested-reference unchanged"},{"id":"IETF RFC 8340","type":"specification","body":"IETF","designation":"RFC 8340","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8340.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8340.txt","https://www.rfc-editor.org/rfc/rfc8340.pdf"],"folder":"IETF/RFC-8340","files":{"txt":{"path":"standards/IETF/RFC-8340/RFC-8340.txt","sha256":"2e1ee8c99d06320357ea6a8288303554a581c8f5c7a172c949c16eac55fb7336"}},"tags":["nested-reference","unchanged"],"summary":"This document captures the current syntax used in YANG module tree\n diagrams. The purpose of this document is to provide a single\n location for this definition. This syntax may be updated from time\n to time based on the evolution of the YANG language.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8340.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n doc","scope_keywords":["8340","http","https","key","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8343","folder":"IETF/RFC-8343","source":"IETF/RFC-8343/RFC-8343.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8348","folder":"IETF/RFC-8348","source":"IETF/RFC-8348/RFC-8348.txt","version":null},{"body":"IETF","designation":"RFC 8349","folder":"IETF/RFC-8349","source":"IETF/RFC-8349/RFC-8349.txt","version":null},{"body":"IETF","designation":"RFC 8407","folder":"IETF/RFC-8407","source":"IETF/RFC-8407/RFC-8407.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 8783","folder":"IETF/RFC-8783","source":"IETF/RFC-8783/RFC-8783.txt","version":null},{"body":"IETF","designation":"RFC 8791","folder":"IETF/RFC-8791","source":"IETF/RFC-8791/RFC-8791.txt","version":null},{"body":"IETF","designation":"RFC 8792","folder":"IETF/RFC-8792","source":"IETF/RFC-8792/RFC-8792.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8340 This document captures the current syntax used in YANG module tree\n diagrams. The purpose of this document is to provide a single\n location for this definition. This syntax may be updated from time\n to time based on the evolution of the YANG language.\n\nStatus of This Memo\n\n This memo documents an Internet Best Current Practice.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n BCPs is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8340.\n\nCopyright Notice\n\n Copyright (c) 2018 IETF Trust and the persons identified as the\n doc 8340 http https key license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 654","type":"specification","body":"IETF","designation":"RFC 654","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc654.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc654.txt","https://www.rfc-editor.org/rfc/rfc654.pdf"],"folder":"IETF/RFC-654","files":{"txt":{"path":"standards/IETF/RFC-654/RFC-654.txt","sha256":"4697c0e10de1bd6bd7c572591b8fc9587fdf17d669a4964364e007c17a7397c7"}},"tags":["nested-reference","unchanged"],"summary":"TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION\nRFC 654, NIC 31157 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOHTD.TXT\n\n TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION\n\n1. Command name and code\n NAOHTD 12\n (Negotiate About Output Horizontal Tab Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet options.\n IAC DO NAOHTD\n The data sender requests or agrees to negotiate about output \n horizontal tab character disposition with the data receiver. In the \n case where agreement has been reached and in the absence of further \n subnegotiations, the data receiver is assumed to be handling output \n horizontal tab character considerations.\n IAC DON'T NAOHTD\n The data sender refuses to negotiate about output horizontal tab \n characters with the data receiver, or demands a return to the \n unnegotiated ","scope_keywords":["654"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 654 TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION\nRFC 654, NIC 31157 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOHTD.TXT\n\n TELNET OUTPUT HORIZONTAL TAB DISPOSITION OPTION\n\n1. Command name and code\n NAOHTD 12\n (Negotiate About Output Horizontal Tab Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet options.\n IAC DO NAOHTD\n The data sender requests or agrees to negotiate about output \n horizontal tab character disposition with the data receiver. In the \n case where agreement has been reached and in the absence of further \n subnegotiations, the data receiver is assumed to be handling output \n horizontal tab character considerations.\n IAC DON'T NAOHTD\n The data sender refuses to negotiate about output horizontal tab \n characters with the data receiver, or demands a return to the \n unnegotiated  654 nested-reference unchanged"},{"id":"IETF RFC 655","type":"specification","body":"IETF","designation":"RFC 655","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc655.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc655.txt","https://www.rfc-editor.org/rfc/rfc655.pdf"],"folder":"IETF/RFC-655","files":{"txt":{"path":"standards/IETF/RFC-655/RFC-655.txt","sha256":"245114206f6b85463a5c601010950ea8aed0a50e5b3c4c9b535d1df9574086cb"}},"tags":["nested-reference","unchanged"],"summary":"TELNET OUTPUT FORMFEED DISPOSITION OPTION\nRFC 655, NIC 31158 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOFFD.TXT\n\n TELNET OUTPUT FORMFEED DISPOSITION OPTION\n\n1. Command name and code\n NAOFFD - 13\n (Negotiate About Output Formfeed Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOFFD\n The data sender requests or agrees to negotiate about output\n formfeed disposition with the data receiver. In the case\n where agreement has been reached and in the absence of\n further subnegotiations, the data receiver is assumed to be\n handling output formfeeds.\n IAC DON'T NAOFFD\n The data sender refuses to negotiate about output formfeed\n disposition with the data receiver, or demands a return to\n the unnegotiated default mode.\n IAC WILL NAOFFD\n The data receiver requests","scope_keywords":["655"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 655 TELNET OUTPUT FORMFEED DISPOSITION OPTION\nRFC 655, NIC 31158 (Oct. 25, 1974)\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOFFD.TXT\n\n TELNET OUTPUT FORMFEED DISPOSITION OPTION\n\n1. Command name and code\n NAOFFD - 13\n (Negotiate About Output Formfeed Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOFFD\n The data sender requests or agrees to negotiate about output\n formfeed disposition with the data receiver. In the case\n where agreement has been reached and in the absence of\n further subnegotiations, the data receiver is assumed to be\n handling output formfeeds.\n IAC DON'T NAOFFD\n The data sender refuses to negotiate about output formfeed\n disposition with the data receiver, or demands a return to\n the unnegotiated default mode.\n IAC WILL NAOFFD\n The data receiver requests 655 nested-reference unchanged"},{"id":"IETF RFC 656","type":"specification","body":"IETF","designation":"RFC 656","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc656.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc656.txt","https://www.rfc-editor.org/rfc/rfc656.pdf"],"folder":"IETF/RFC-656","files":{"txt":{"path":"standards/IETF/RFC-656/RFC-656.txt","sha256":"7bf2d66c134f10485e2757ecae1054eb4d6a2de5f94b9498492b64a6033034b0"}},"tags":["nested-reference","unchanged"],"summary":"TELNET OUTPUT VERTICAL TABSTOPS OPTION\nRFC 656, NIC 31159 (Oct. 25, 1974)\"\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOVTS.TXT\n\n TELNET OUTPUT VERTICAL TABSTOPS OPTION\n\n1. Command name and code\n NAOVTS 14\n (Negotiate About Vertcial Tabstops)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOVTS \n The data sender requests or agrees to negotiate about output\n vertical tabstops with the data receiver. In the case where\n agreement has been reached and in the absence of further\n subnegotiations, the data receiver is assumed to be handling output\n vertical tabstop considerations.\n IAC DON'T NAOVTS \n The data sender refuses to negotiate about output vertical tabstops \n with the data receiver, or demands a return to the unnegotiated \n default mode.\n IAC WILL NAOVTS \n The data receiver requ","scope_keywords":["656"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 656 TELNET OUTPUT VERTICAL TABSTOPS OPTION\nRFC 656, NIC 31159 (Oct. 25, 1974)\"\nD. Crocker (UCLA-NMC)\nOnline file: [ISI] NAOVTS.TXT\n\n TELNET OUTPUT VERTICAL TABSTOPS OPTION\n\n1. Command name and code\n NAOVTS 14\n (Negotiate About Vertcial Tabstops)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOVTS \n The data sender requests or agrees to negotiate about output\n vertical tabstops with the data receiver. In the case where\n agreement has been reached and in the absence of further\n subnegotiations, the data receiver is assumed to be handling output\n vertical tabstop considerations.\n IAC DON'T NAOVTS \n The data sender refuses to negotiate about output vertical tabstops \n with the data receiver, or demands a return to the unnegotiated \n default mode.\n IAC WILL NAOVTS \n The data receiver requ 656 nested-reference unchanged"},{"id":"IETF RFC 657","type":"specification","body":"IETF","designation":"RFC 657","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc657.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc657.txt","https://www.rfc-editor.org/rfc/rfc657.pdf"],"folder":"IETF/RFC-657","files":{"txt":{"path":"standards/IETF/RFC-657/RFC-657.txt","sha256":"aa1ab8b33384f2cc5bd635171a8b256ebb0a33189c9ffb1522879c617b1c6a1d"}},"tags":["nested-reference","unchanged"],"summary":"D. Crocker (UCLA-NMC)\nRFC 657, NIC 31160 (Oct. 25, 1974)\nOnline file: [ISI] NAOVTD.TXT\n\n TELNET OUTPUT VERTICAL TAB DISPOSITION OPTION\n\n1. Command name and code\n NAOVTD 15\n (Negotiate About Output Vertcial Tab Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as\n described in the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOVTD\n The data sender requests or agrees to negotiate about output\n vertical tab character disposition with the data receiver.\n In the case where agreement has been reached and in the\n absence of further subnegotiations, the data receiver is\n assumed to be handling output vertical tab character considerations.\n IAC DON'T NAOVTD\n The data sender refuses to negotiate about output vertical tab\n character disposition with the data receiver, or demands a\n return to the unnegotiated default mode.\n IAC WILL NAOVTD\n The dat","scope_keywords":["657"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 657 D. Crocker (UCLA-NMC)\nRFC 657, NIC 31160 (Oct. 25, 1974)\nOnline file: [ISI] NAOVTD.TXT\n\n TELNET OUTPUT VERTICAL TAB DISPOSITION OPTION\n\n1. Command name and code\n NAOVTD 15\n (Negotiate About Output Vertcial Tab Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as\n described in the NAOL and NAOP Telnet Options specifications.\n IAC DO NAOVTD\n The data sender requests or agrees to negotiate about output\n vertical tab character disposition with the data receiver.\n In the case where agreement has been reached and in the\n absence of further subnegotiations, the data receiver is\n assumed to be handling output vertical tab character considerations.\n IAC DON'T NAOVTD\n The data sender refuses to negotiate about output vertical tab\n character disposition with the data receiver, or demands a\n return to the unnegotiated default mode.\n IAC WILL NAOVTD\n The dat 657 nested-reference unchanged"},{"id":"IETF RFC 658","type":"specification","body":"IETF","designation":"RFC 658","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc658.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc658.txt","https://www.rfc-editor.org/rfc/rfc658.pdf"],"folder":"IETF/RFC-658","files":{"txt":{"path":"standards/IETF/RFC-658/RFC-658.txt","sha256":"b19f0acf9ea77bacf39355062eee361a045a9a0d47667a94f3ec5adb036e2638"}},"tags":["nested-reference","unchanged"],"summary":"D. Crocker (UCLA-NMC)\nRFC 658, NIC 31161 (Oct. 25, 1974)\nOnline file: [ISI] NAOLFD.TXT\n\n TELNET OUTPUT LINEFEED DISPOSITION\n\n1. Command name and code\n NAOLFD 16 \n (Negotiate About Output Linefeed Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options.\n IAC DO NAOLFD \n The data sender requests or agrees to negotiate about output\n linefeed disposition with the data receiver. In the case where\n agreement has been reached and in the absence of further\n subnegotiations, the data receiver is assumed to be handling output\n linefeed considerations.\n IAC DON'T NAOLFD \n The data sender refuses to negotiate about output linefeed\n disposition with the data receiver, or demands a return to the\n unnegotiated default mode.\n IAC WILL NAOLFD \n The data receiver requests or agrees to negotiate about output\n linefeed d","scope_keywords":["658"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 658 D. Crocker (UCLA-NMC)\nRFC 658, NIC 31161 (Oct. 25, 1974)\nOnline file: [ISI] NAOLFD.TXT\n\n TELNET OUTPUT LINEFEED DISPOSITION\n\n1. Command name and code\n NAOLFD 16 \n (Negotiate About Output Linefeed Disposition)\n\n2. Command meanings\n In the following, we are discussing a simplex connection, as described in \n the NAOL and NAOP Telnet Options.\n IAC DO NAOLFD \n The data sender requests or agrees to negotiate about output\n linefeed disposition with the data receiver. In the case where\n agreement has been reached and in the absence of further\n subnegotiations, the data receiver is assumed to be handling output\n linefeed considerations.\n IAC DON'T NAOLFD \n The data sender refuses to negotiate about output linefeed\n disposition with the data receiver, or demands a return to the\n unnegotiated default mode.\n IAC WILL NAOLFD \n The data receiver requests or agrees to negotiate about output\n linefeed d 658 nested-reference unchanged"},{"id":"IETF RFC 6639","type":"specification","body":"IETF","designation":"RFC 6639","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6639.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6639.txt","https://www.rfc-editor.org/rfc/rfc6639.pdf"],"folder":"IETF/RFC-6639","files":{"txt":{"path":"standards/IETF/RFC-6639/RFC-6639.txt","sha256":"8a9ca35e5862cfd140ddc95d7cb1c147c7c8fbdb473e2251ec60ea30dc1ef825"}},"tags":["nested-reference","unchanged"],"summary":"A range of Management Information Base (MIB) modules has been\n developed to help model and manage the various aspects of\n Multiprotocol Label Switching (MPLS) networks. These MIB modules are\n defined in separate documents that focus on the specific areas of\n responsibility of the modules that they describe.\n\n The MPLS Transport Profile (MPLS-TP) is a profile of MPLS\n functionality specific to the construction of packet-switched\n transport networks.\n\n This document describes the MIB-based architecture for MPLS-TP,\n indicates the interrelationships between different existing MIB\n modules that can be leveraged for MPLS-TP network management, and\n identifies areas where additional MIB modules are required.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering","scope_keywords":["6639","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6639 A range of Management Information Base (MIB) modules has been\n developed to help model and manage the various aspects of\n Multiprotocol Label Switching (MPLS) networks. These MIB modules are\n defined in separate documents that focus on the specific areas of\n responsibility of the modules that they describe.\n\n The MPLS Transport Profile (MPLS-TP) is a profile of MPLS\n functionality specific to the construction of packet-switched\n transport networks.\n\n This document describes the MIB-based architecture for MPLS-TP,\n indicates the interrelationships between different existing MIB\n modules that can be leveraged for MPLS-TP network management, and\n identifies areas where additional MIB modules are required.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering 6639 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6669","type":"specification","body":"IETF","designation":"RFC 6669","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6669.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6669.txt","https://www.rfc-editor.org/rfc/rfc6669.pdf"],"folder":"IETF/RFC-6669","files":{"txt":{"path":"standards/IETF/RFC-6669/RFC-6669.txt","sha256":"e9e060e4347eb7d71e9e9e8facddd9bb8184c3d54da693ba28cd5dc5668c77c8"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an overview of the Operations, Administration,\n and Maintenance (OAM) toolset for MPLS-based transport networks. The\n toolset consists of a comprehensive set of fault management and\n performance monitoring capabilities (operating in the data plane)\n that are appropriate for transport networks as required in RFC 5860\n and support the network and services at different nested levels.\n This overview includes a brief recap of the MPLS Transport Profile\n (MPLS-TP) OAM requirements and functions and the generic mechanisms\n created in the MPLS data plane that allow the OAM packets to run\n in-band and share their fate with data packets. The protocol\n definitions for each of the MPLS-TP OAM tools are defined in separate\n documents (RFCs or Working Group documents), which are referenced by\n this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track","scope_keywords":["6669","http","license","management","path","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6669 This document provides an overview of the Operations, Administration,\n and Maintenance (OAM) toolset for MPLS-based transport networks. The\n toolset consists of a comprehensive set of fault management and\n performance monitoring capabilities (operating in the data plane)\n that are appropriate for transport networks as required in RFC 5860\n and support the network and services at different nested levels.\n This overview includes a brief recap of the MPLS Transport Profile\n (MPLS-TP) OAM requirements and functions and the generic mechanisms\n created in the MPLS data plane that allow the OAM packets to run\n in-band and share their fate with data packets. The protocol\n definitions for each of the MPLS-TP OAM tools are defined in separate\n documents (RFCs or Working Group documents), which are referenced by\n this document.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track 6669 http license management path profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6670","type":"specification","body":"IETF","designation":"RFC 6670","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6670.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6670.txt","https://www.rfc-editor.org/rfc/rfc6670.pdf"],"folder":"IETF/RFC-6670","files":{"txt":{"path":"standards/IETF/RFC-6670/RFC-6670.txt","sha256":"125d320a7e5ca8b8d380e7fb509f6af9a82e3743f284d058e8b3605f4548ca43"}},"tags":["nested-reference","unchanged"],"summary":"The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS\n technology for use in transport network deployments. The work on\n MPLS-TP has extended the MPLS technology with additional\n architectural elements and functions that can be used in any MPLS\n deployment. MPLS-TP is a set of functions and features selected from\n the extended MPLS toolset and applied in a consistent way to meet the\n needs and requirements of operators of packet transport networks.\n\n During the process of development of the profile, additions to the\n MPLS toolset have been made to ensure that the tools available met\n the requirements. These additions were motivated by MPLS-TP, but\n form part of the wider MPLS toolset such that any of them could be\n used in any MPLS deployment.\n\n One major set of additions provides enhanced support for Operations,\n Administration, and Maintenance (OAM). This enables fault manageme","scope_keywords":["6670","http","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6670 The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS\n technology for use in transport network deployments. The work on\n MPLS-TP has extended the MPLS technology with additional\n architectural elements and functions that can be used in any MPLS\n deployment. MPLS-TP is a set of functions and features selected from\n the extended MPLS toolset and applied in a consistent way to meet the\n needs and requirements of operators of packet transport networks.\n\n During the process of development of the profile, additions to the\n MPLS toolset have been made to ensure that the tools available met\n the requirements. These additions were motivated by MPLS-TP, but\n form part of the wider MPLS toolset such that any of them could be\n used in any MPLS deployment.\n\n One major set of additions provides enhanced support for Operations,\n Administration, and Maintenance (OAM). This enables fault manageme 6670 http license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6671","type":"specification","body":"IETF","designation":"RFC 6671","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6671.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6671.txt","https://www.rfc-editor.org/rfc/rfc6671.pdf"],"folder":"IETF/RFC-6671","files":{"txt":{"path":"standards/IETF/RFC-6671/RFC-6671.txt","sha256":"233998441a8f389599464dc31d50f62dad032804f161ce29f47ceeafb7abff66"}},"tags":["nested-reference","unchanged"],"summary":"This document assigns a Generic Associated Channel (G-ACh) Type for\n carrying ITU-T MPLS Transport Profile Operations, Administration, and\n Management (MPLS-TP OAM) messages in the MPLS Generic Associated\n Channel.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6671.\n\nIESG Note\n\n The IES","scope_keywords":["6671","http","key","license","management","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"IETF RFC 6671 This document assigns a Generic Associated Channel (G-ACh) Type for\n carrying ITU-T MPLS Transport Profile Operations, Administration, and\n Management (MPLS-TP OAM) messages in the MPLS Generic Associated\n Channel.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6671.\n\nIESG Note\n\n The IES 6671 http key license management profile subject trust nested-reference unchanged"},{"id":"IETF RFC 6720","type":"specification","body":"IETF","designation":"RFC 6720","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6720.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6720.txt","https://www.rfc-editor.org/rfc/rfc6720.pdf"],"folder":"IETF/RFC-6720","files":{"txt":{"path":"standards/IETF/RFC-6720/RFC-6720.txt","sha256":"54609f14ff18250a23c2a665a9b5bd4ac236e97405911253db7bfbefa9af49a8"}},"tags":["nested-reference","unchanged"],"summary":"The Generalized TTL Security Mechanism (GTSM) describes a generalized\n use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to\n verify that the packet was sourced by a node on a connected link,\n thereby protecting the router's IP control plane from CPU\n utilization-based attacks. This technique improves security and is\n used by many protocols. This document defines the GTSM use for the\n Label Distribution Protocol (LDP).\n\n This specification uses a bit reserved in RFC 5036 and therefore\n updates RFC 5036.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in S","scope_keywords":["6720","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6720 The Generalized TTL Security Mechanism (GTSM) describes a generalized\n use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to\n verify that the packet was sourced by a node on a connected link,\n thereby protecting the router's IP control plane from CPU\n utilization-based attacks. This technique improves security and is\n used by many protocols. This document defines the GTSM use for the\n Label Distribution Protocol (LDP).\n\n This specification uses a bit reserved in RFC 5036 and therefore\n updates RFC 5036.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in S 6720 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 6736","type":"specification","body":"IETF","designation":"RFC 6736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6736.txt","https://www.rfc-editor.org/rfc/rfc6736.pdf"],"folder":"IETF/RFC-6736","files":{"txt":{"path":"standards/IETF/RFC-6736/RFC-6736.txt","sha256":"88f3ad85bd89654bdad51ee7511f0c4ef5ac9d3f051a4b7f109c5fd7ba5464df"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the framework, messages, and procedures for\n the Diameter Network address and port translation Control\n Application. This Diameter application allows per-endpoint control\n of Network Address Translators and Network Address and Port\n Translators, which are added to networks to cope with IPv4 address\n space depletion. This Diameter application allows external devices\n to configure and manage a Network Address Translator device --\n expanding the existing Diameter-based Authentication, Authorization,\n and Accounting (AAA) and policy control capabilities with a Network\n Address Translator and Network Address and Port Translator control\n component. These external devices can be network elements in the\n data plane such as a Network Access Server, or can be more\n centralized control plane devices such as AAA-servers. This Diameter\n application establishes a context to com","scope_keywords":["6736","authentication","authorization","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 6736 This document describes the framework, messages, and procedures for\n the Diameter Network address and port translation Control\n Application. This Diameter application allows per-endpoint control\n of Network Address Translators and Network Address and Port\n Translators, which are added to networks to cope with IPv4 address\n space depletion. This Diameter application allows external devices\n to configure and manage a Network Address Translator device --\n expanding the existing Diameter-based Authentication, Authorization,\n and Accounting (AAA) and policy control capabilities with a Network\n Address Translator and Network Address and Port Translator control\n component. These external devices can be network elements in the\n data plane such as a Network Access Server, or can be more\n centralized control plane devices such as AAA-servers. This Diameter\n application establishes a context to com 6736 authentication authorization http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 674","type":"specification","body":"IETF","designation":"RFC 674","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc674.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc674.txt","https://www.rfc-editor.org/rfc/rfc674.pdf"],"folder":"IETF/RFC-674","files":{"txt":{"path":"standards/IETF/RFC-674/RFC-674.txt","sha256":"e1ba204c04d8333a8c3e090babf8bad25ed062d95629962f52d4dc45c6db57c1"}},"tags":["nested-reference","unchanged"],"summary":"31484.NLS;1, 12-DEC-74 04:32 XXX ;;;; Title: Author(s):\nJonathan B. Postel/JBP; Distribution: /NAG( [ ACTION ] ) NLG( [ ACTION ]\n) NSW( [ ACTION ] ) PI( [ ACTION ] ) ; Sub-Collections: NIC NWG SRI-ARC\nNAG NLG NSW PI; RFC# 674; Clerk: JAKE; Origin: , 11-DEC-74 17:58 JAKE ;;;;####;\f\n\nNWG/RFC# 674 JBP 11-DEC-74 18:04 31484\nProcedure Call Protocol Documents\n\nRequest for Comments 674 Jon Postel\nNIC 31484 Jim White\n SRI-ARC\n 12 December 1974\n\n Procedure Call Protocol Documents\n Version 2\n\n 1\n\nAs many of you may know SRI is part of a team working on the National\nSoftware Works project. In the course of our work we have developed a\nProcedure Call Protocol to be used between the modules which make up\nthe NSW. We are interested in your comments on this protocol. Please\nforeward your remarks to either: 2\n\n James E. White (WHITE@SRI-ARC) or Jon Postel (POSTEL@SRI-ARC) 2a\n\n Augmentation Research Cent","scope_keywords":["674","identification","management","path","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 684","folder":"IETF/RFC-684","source":"IETF/RFC-684/RFC-684.txt","version":null}],"search_text":"IETF RFC 674 31484.NLS;1, 12-DEC-74 04:32 XXX ;;;; Title: Author(s):\nJonathan B. Postel/JBP; Distribution: /NAG( [ ACTION ] ) NLG( [ ACTION ]\n) NSW( [ ACTION ] ) PI( [ ACTION ] ) ; Sub-Collections: NIC NWG SRI-ARC\nNAG NLG NSW PI; RFC# 674; Clerk: JAKE; Origin: , 11-DEC-74 17:58 JAKE ;;;;####;\f\n\nNWG/RFC# 674 JBP 11-DEC-74 18:04 31484\nProcedure Call Protocol Documents\n\nRequest for Comments 674 Jon Postel\nNIC 31484 Jim White\n SRI-ARC\n 12 December 1974\n\n Procedure Call Protocol Documents\n Version 2\n\n 1\n\nAs many of you may know SRI is part of a team working on the National\nSoftware Works project. In the course of our work we have developed a\nProcedure Call Protocol to be used between the modules which make up\nthe NSW. We are interested in your comments on this protocol. Please\nforeward your remarks to either: 2\n\n James E. White (WHITE@SRI-ARC) or Jon Postel (POSTEL@SRI-ARC) 2a\n\n Augmentation Research Cent 674 identification management path policies nested-reference unchanged"},{"id":"IETF RFC 684","type":"specification","body":"IETF","designation":"RFC 684","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc684.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc684.txt","https://www.rfc-editor.org/rfc/rfc684.pdf"],"folder":"IETF/RFC-684","files":{"txt":{"path":"standards/IETF/RFC-684/RFC-684.txt","sha256":"e39773343ac98f0b1ddc5df9251d4caa7ad92503df3e0c44b9767e9954e8662c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRFC #684\nNIC #32252\nApril 15,1975\n\n A Commentary on Procedure Calling as a Network Protocol\n\n Richard Schantz\n\n BBN-TENEX\n\nPreface_____\n\nThis RFC is being issued as a first step in an attempt to stimulate\na dialog on some issues in designing a distributed computing system.\nIn particular, it considers the approach taken in a design set forth\nin RFC #674, commonly known as the \"Procedure Call Protocol\" (PCP).\nIn the present document, the concentration is on what we believe to\nbe the shortcomings of such a design approach.\n\nNote at the outset that this is not the first time we are providing\na critical commentary on PCP. During the earlier PCP design stages,\nwe met with the PCP designers for a brief period, and suggested\nseveral changes, many of which became part of PCP Version 2. We\nhasten to add, however, that the nature of those suggestions stem\nfrom an entirely diff","scope_keywords":["684","algorithm","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 684 Network Working Group\nRFC #684\nNIC #32252\nApril 15,1975\n\n A Commentary on Procedure Calling as a Network Protocol\n\n Richard Schantz\n\n BBN-TENEX\n\nPreface_____\n\nThis RFC is being issued as a first step in an attempt to stimulate\na dialog on some issues in designing a distributed computing system.\nIn particular, it considers the approach taken in a design set forth\nin RFC #674, commonly known as the \"Procedure Call Protocol\" (PCP).\nIn the present document, the concentration is on what we believe to\nbe the shortcomings of such a design approach.\n\nNote at the outset that this is not the first time we are providing\na critical commentary on PCP. During the earlier PCP design stages,\nwe met with the PCP designers for a brief period, and suggested\nseveral changes, many of which became part of PCP Version 2. We\nhasten to add, however, that the nature of those suggestions stem\nfrom an entirely diff 684 algorithm key path nested-reference unchanged"},{"id":"IETF RFC 675","type":"specification","body":"IETF","designation":"RFC 675","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc675.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc675.txt","https://www.rfc-editor.org/rfc/rfc675.pdf"],"folder":"IETF/RFC-675","files":{"txt":{"path":"standards/IETF/RFC-675/RFC-675.txt","sha256":"61406b9b6830d59629dc095933c7ca3f345bb05298dd6e19cc74c3282d17d2da"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Vinton Cerf\nRequest for Comments: 675 Yogen Dalal\nNIC: 2 Carl Sunshine\nINWG: 72 December 1974\n\n SPECIFICATION OF INTERNET TRANSMISSION CONTROL PROGRAM\n\n December 1974 Version\n\n1. INTRODUCTION\n\n This document describes the functions to be performed by the\n internetwork Transmission Control Program [TCP] and its interface to\n programs or users that require its services. Several basic\n assumptions are made about process to process communication and these\n are listed here without further justification. The interested reader\n is referred to [CEKA74, TOML74, BELS74, DALA74, SUNS74] for further\n discussion.\n\n The authors would like to acknowledge the contributions of R.\n Tomlinson (three way handshake and Initial Sequence Number\n Selection), D. Belsnes, J. Burchfiel, M. Galland, R. Kahn, D. Lloyd,\n W. Plummer, and J. Postel all of whose good ideas and counsel have\n had a b","scope_keywords":["675","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 721","folder":"IETF/RFC-721","source":"IETF/RFC-721/RFC-721.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 675 Network Working Group Vinton Cerf\nRequest for Comments: 675 Yogen Dalal\nNIC: 2 Carl Sunshine\nINWG: 72 December 1974\n\n SPECIFICATION OF INTERNET TRANSMISSION CONTROL PROGRAM\n\n December 1974 Version\n\n1. INTRODUCTION\n\n This document describes the functions to be performed by the\n internetwork Transmission Control Program [TCP] and its interface to\n programs or users that require its services. Several basic\n assumptions are made about process to process communication and these\n are listed here without further justification. The interested reader\n is referred to [CEKA74, TOML74, BELS74, DALA74, SUNS74] for further\n discussion.\n\n The authors would like to acknowledge the contributions of R.\n Tomlinson (three way handshake and Initial Sequence Number\n Selection), D. Belsnes, J. Burchfiel, M. Galland, R. Kahn, D. Lloyd,\n W. Plummer, and J. Postel all of whose good ideas and counsel have\n had a b 675 delivery nested-reference unchanged"},{"id":"IETF RFC 721","type":"specification","body":"IETF","designation":"RFC 721","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc721.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc721.txt","https://www.rfc-editor.org/rfc/rfc721.pdf"],"folder":"IETF/RFC-721","files":{"txt":{"path":"standards/IETF/RFC-721/RFC-721.txt","sha256":"424237ef7f9d469328da589a49d8e9825edbca414ab5c173650d01b5186b96a1"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 721 1 SEP 76 LLG 36636\nOut-of-Band Control Signals\n\nNetwork Working Group Larry Garlick\nRequest for Comments 721 SRI-ARC\nNIC 36636 1 September 76\n\n Out-of-Band Control Signals\n in a\n Host-to-Host Protocol\n\nThis note addresses the problem of implementing a reliable out-of-band\nsignal for use in a host-to-host protocol. It is motivated by the fact\nthat such a satisfactory mechanism does not exist in the Transmission\nControl Protocol (TCP) of Cerf et. al. [reference 4, 6] In addition to\ndiscussing some requirements for such an out-of-band signal (interrupts)\nand the implications for the implementation of the requirements, a\ndiscussion of the problem for the TCP case will be presented.\n\nWhile the ARPANET host-to-host protocol does not support reliable\ntransmission of either data or controls, it does meet the other\nrequirements we have for an out-of-band control signal and will be dra","scope_keywords":["721","delivery","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 721 NWG/RFC 721 1 SEP 76 LLG 36636\nOut-of-Band Control Signals\n\nNetwork Working Group Larry Garlick\nRequest for Comments 721 SRI-ARC\nNIC 36636 1 September 76\n\n Out-of-Band Control Signals\n in a\n Host-to-Host Protocol\n\nThis note addresses the problem of implementing a reliable out-of-band\nsignal for use in a host-to-host protocol. It is motivated by the fact\nthat such a satisfactory mechanism does not exist in the Transmission\nControl Protocol (TCP) of Cerf et. al. [reference 4, 6] In addition to\ndiscussing some requirements for such an out-of-band signal (interrupts)\nand the implications for the implementation of the requirements, a\ndiscussion of the problem for the TCP case will be presented.\n\nWhile the ARPANET host-to-host protocol does not support reliable\ntransmission of either data or controls, it does meet the other\nrequirements we have for an out-of-band control signal and will be dra 721 delivery path subject nested-reference unchanged"},{"id":"IETF RFC 678","type":"specification","body":"IETF","designation":"RFC 678","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc678.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc678.txt","https://www.rfc-editor.org/rfc/rfc678.pdf"],"folder":"IETF/RFC-678","files":{"txt":{"path":"standards/IETF/RFC-678/RFC-678.txt","sha256":"b00306e9eb492db8b23ed4d93357c2eb45fee8f7c3f59cb8947ec85440201e70"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 678 (SRI-ARC)\nNIC: 31524 19 December 1974\n\n Standard File Formats\n\nIntroduction\n\n In an attempt to provide online documents to the network community we\n have had many problems with the physical format of the final\n documents. Much of this difficulty lies in the fact that we do not\n have control or even knowledge of all the processing steps or devices\n that act on the document file. A large part of the difficulty in the\n past has been due to some assumptions we made about the rest of the\n world being approximately like our own environment. We now see that\n the problems are due to differing assumptions and treatment of files\n to be printed as documents. We therefore propose to define certain\n standard formats for files and describe the expected final form for\n printed copies of such files.\n\n These standard formats are not additional Fil","scope_keywords":["678"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 678 Network Working Group J. Postel\nRequest for Comments: 678 (SRI-ARC)\nNIC: 31524 19 December 1974\n\n Standard File Formats\n\nIntroduction\n\n In an attempt to provide online documents to the network community we\n have had many problems with the physical format of the final\n documents. Much of this difficulty lies in the fact that we do not\n have control or even knowledge of all the processing steps or devices\n that act on the document file. A large part of the difficulty in the\n past has been due to some assumptions we made about the rest of the\n world being approximately like our own environment. We now see that\n the problems are due to differing assumptions and treatment of files\n to be printed as documents. We therefore propose to define certain\n standard formats for files and describe the expected final form for\n printed copies of such files.\n\n These standard formats are not additional Fil 678 nested-reference unchanged"},{"id":"IETF RFC 713","type":"specification","body":"IETF","designation":"RFC 713","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc713.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc713.txt","https://www.rfc-editor.org/rfc/rfc713.pdf"],"folder":"IETF/RFC-713","files":{"txt":{"path":"standards/IETF/RFC-713/RFC-713.txt","sha256":"2c7ec7fe46e6a83ee7613410d28e9052ccbfa4da0f0dad58e965325f038bdaea"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 713 Jack Haverty (JFH@MIT-DMS)\nNIC #34739 Apr 1976\n\nI. ABSTRACT\n\nA mechanism is defined for use by message servers in\ntransferring data between hosts. The mechanism, called the\nMSDTP, is defined in terms of a model of the process as a\ntranslation between two sets of items, the abstract entities\nsuch as 'strings' and 'integers', and the formats used to\nrepresent such data as a byte stream.\n\nA proposed organization of a general data transfer\nmechanism is described, and the manner in which the MSDTP\nwould be used in that environment is presented.\n\n -1-\f\n\nII. REFERENCES\n\nBlack, Edward H., \"The DMS Message Composer\", MIT Project\nMAC, Programming Technology Division Document\nSYS.16.02.\n\nBurchfiel, Jerry D., Leavitt, Elsie M., Shapiro, Sonya and\nStrollo, Theodore R., compilers, \"Tenex Users' Guide\",\nBolt Beranek and Newman, Cambridge, Mass., May 1971,\nrevised January 1975,","scope_keywords":["713","holder","presentation","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 722","folder":"IETF/RFC-722","source":"IETF/RFC-722/RFC-722.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"IETF RFC 713 Request for Comments: 713 Jack Haverty (JFH@MIT-DMS)\nNIC #34739 Apr 1976\n\nI. ABSTRACT\n\nA mechanism is defined for use by message servers in\ntransferring data between hosts. The mechanism, called the\nMSDTP, is defined in terms of a model of the process as a\ntranslation between two sets of items, the abstract entities\nsuch as 'strings' and 'integers', and the formats used to\nrepresent such data as a byte stream.\n\nA proposed organization of a general data transfer\nmechanism is described, and the manner in which the MSDTP\nwould be used in that environment is presented.\n\n -1-\f\n\nII. REFERENCES\n\nBlack, Edward H., \"The DMS Message Composer\", MIT Project\nMAC, Programming Technology Division Document\nSYS.16.02.\n\nBurchfiel, Jerry D., Leavitt, Elsie M., Shapiro, Sonya and\nStrollo, Theodore R., compilers, \"Tenex Users' Guide\",\nBolt Beranek and Newman, Cambridge, Mass., May 1971,\nrevised January 1975, 713 holder presentation risk nested-reference unchanged"},{"id":"IETF RFC 733","type":"specification","body":"IETF","designation":"RFC 733","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc733.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc733.txt","https://www.rfc-editor.org/rfc/rfc733.pdf"],"folder":"IETF/RFC-733","files":{"txt":{"path":"standards/IETF/RFC-733/RFC-733.txt","sha256":"07de5642a57636a027cf33346775baf7b19e5075888995f5440c46d3f01bf371"}},"tags":["nested-reference","unchanged"],"summary":"RFC # 733\nNIC # 41952\n\nObsoletes: RFC #561 (NIC #18516)\n RFC #680 (NIC #32116)\n RFC #724 (NIC #37435)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA NETWORK TEXT MESSAGES(1)\n\n 21 November 1977\n\n by\n\n David H. Crocker\n The Rand Corporation\n\n John J. Vittal\n Bolt Beranek and Newman Inc.\n\n Kenneth T. Pogran\n Massachusets Institute of Technology\n\n D. Austin Henderson, Jr.(2)\n Bolt Beranek and Newman Inc.\n\n_________________________________________________________________\n(1)This work was supported by the Defense Advanced Research\nProjects Agency of the Department of Defense, under contract Nos.\nN00014-75-C-0661, MDA903-76-C-0212, and DAHC15-73-C0181.\n\n(2)The authors' postal addresses are: D. Crocker, The Rand\nCorporation, Information Sciences Dept., 1700 Main St., Santa\nMonica, California 90406; J. Vittal & D. A. Henderson, Bolt\nBeranek & Newman, 50 Moulton St., Cambridge, Massachusetts 02138;\nand K. Po","scope_keywords":["733"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2234","folder":"IETF/RFC-2234","source":"IETF/RFC-2234/RFC-2234.txt","version":null},{"body":"IETF","designation":"RFC 2235","folder":"IETF/RFC-2235","source":"IETF/RFC-2235/RFC-2235.txt","version":null},{"body":"IETF","designation":"RFC 4234","folder":"IETF/RFC-4234","source":"IETF/RFC-4234/RFC-4234.txt","version":null},{"body":"IETF","designation":"RFC 5234","folder":"IETF/RFC-5234","source":"IETF/RFC-5234/RFC-5234.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null},{"body":"IETF","designation":"RFC 772","folder":"IETF/RFC-772","source":"IETF/RFC-772/RFC-772.txt","version":null},{"body":"IETF","designation":"RFC 780","folder":"IETF/RFC-780","source":"IETF/RFC-780/RFC-780.txt","version":null},{"body":"IETF","designation":"RFC 788","folder":"IETF/RFC-788","source":"IETF/RFC-788/RFC-788.txt","version":null},{"body":"IETF","designation":"RFC 805","folder":"IETF/RFC-805","source":"IETF/RFC-805/RFC-805.txt","version":null},{"body":"IETF","designation":"RFC 806","folder":"IETF/RFC-806","source":"IETF/RFC-806/RFC-806.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 841","folder":"IETF/RFC-841","source":"IETF/RFC-841/RFC-841.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 733 RFC # 733\nNIC # 41952\n\nObsoletes: RFC #561 (NIC #18516)\n RFC #680 (NIC #32116)\n RFC #724 (NIC #37435)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA NETWORK TEXT MESSAGES(1)\n\n 21 November 1977\n\n by\n\n David H. Crocker\n The Rand Corporation\n\n John J. Vittal\n Bolt Beranek and Newman Inc.\n\n Kenneth T. Pogran\n Massachusets Institute of Technology\n\n D. Austin Henderson, Jr.(2)\n Bolt Beranek and Newman Inc.\n\n_________________________________________________________________\n(1)This work was supported by the Defense Advanced Research\nProjects Agency of the Department of Defense, under contract Nos.\nN00014-75-C-0661, MDA903-76-C-0212, and DAHC15-73-C0181.\n\n(2)The authors' postal addresses are: D. Crocker, The Rand\nCorporation, Information Sciences Dept., 1700 Main St., Santa\nMonica, California 90406; J. Vittal & D. A. Henderson, Bolt\nBeranek & Newman, 50 Moulton St., Cambridge, Massachusetts 02138;\nand K. Po 733 nested-reference unchanged"},{"id":"IETF RFC 6829","type":"specification","body":"IETF","designation":"RFC 6829","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6829.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6829.txt","https://www.rfc-editor.org/rfc/rfc6829.pdf"],"folder":"IETF/RFC-6829","files":{"txt":{"path":"standards/IETF/RFC-6829/RFC-6829.txt","sha256":"4fdc2d5d016b95cdbf13f8041f191b3ded8f6a71d722c85a4c6c75b0e6ebc57b"}},"tags":["nested-reference","unchanged"],"summary":"The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)\n Ping and traceroute mechanisms are commonly used to detect and\n isolate data-plane failures in all MPLS LSPs, including LSPs used for\n each direction of an MPLS Pseudowire (PW). However, the LSP Ping and\n traceroute elements used for PWs are not specified for IPv6 address\n usage.\n\n This document extends the PW LSP Ping and traceroute mechanisms so\n they can be used with PWs that are set up and maintained using IPv6\n LDP sessions. This document updates RFC 4379.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av","scope_keywords":["6829","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6829 The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)\n Ping and traceroute mechanisms are commonly used to detect and\n isolate data-plane failures in all MPLS LSPs, including LSPs used for\n each direction of an MPLS Pseudowire (PW). However, the LSP Ping and\n traceroute elements used for PWs are not specified for IPv6 address\n usage.\n\n This document extends the PW LSP Ping and traceroute mechanisms so\n they can be used with PWs that are set up and maintained using IPv6\n LDP sessions. This document updates RFC 4379.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is av 6829 http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 687","type":"specification","body":"IETF","designation":"RFC 687","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc687.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc687.txt","https://www.rfc-editor.org/rfc/rfc687.pdf"],"folder":"IETF/RFC-687","files":{"txt":{"path":"standards/IETF/RFC-687/RFC-687.txt","sha256":"6049d722cb1670ededfdd034b955dd5a57a1d442b3eab6461a8a60d267344f90"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David C. Walden (WALDEN@BBN)\nRequest for Comments: 687 Jun 1975\nNIC #32654\n\n IMP/Host and Host/IMP Protocol Change\n\nThis note sketches the design of an expansion to the\nIMP/host and host/IMP protocol which will include among other\nthings the possibility of addressing hosts on more than 63 IMPs.\nOur intention in this expansion is to correct certain existing\nlimits without fundamental changes in the philosophy of the\nIMP/host protocol; i.e., while many issues which would represent\nfundamental changes to the IMP/host protocol are presently under\ndiscussion in the world-wide packet-switching com unity, we are\nnot able to undertake massive fundamental changes on a time scale\ncompatible with the short term needs for network improvement\n(e.g., already there are almost 60 IMPs).\n\nThe following paragraphs cover each of the major\ncharacteristics of the expanded protocol. A kn","scope_keywords":["687"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 687 Network Working Group David C. Walden (WALDEN@BBN)\nRequest for Comments: 687 Jun 1975\nNIC #32654\n\n IMP/Host and Host/IMP Protocol Change\n\nThis note sketches the design of an expansion to the\nIMP/host and host/IMP protocol which will include among other\nthings the possibility of addressing hosts on more than 63 IMPs.\nOur intention in this expansion is to correct certain existing\nlimits without fundamental changes in the philosophy of the\nIMP/host protocol; i.e., while many issues which would represent\nfundamental changes to the IMP/host protocol are presently under\ndiscussion in the world-wide packet-switching com unity, we are\nnot able to undertake massive fundamental changes on a time scale\ncompatible with the short term needs for network improvement\n(e.g., already there are almost 60 IMPs).\n\nThe following paragraphs cover each of the major\ncharacteristics of the expanded protocol. A kn 687 nested-reference unchanged"},{"id":"IETF RFC 6883","type":"specification","body":"IETF","designation":"RFC 6883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6883.txt","https://www.rfc-editor.org/rfc/rfc6883.pdf"],"folder":"IETF/RFC-6883","files":{"txt":{"path":"standards/IETF/RFC-6883/RFC-6883.txt","sha256":"068c83fed55a13750f9ac25618d1584981361c10162402346a90a52b97b2d544"}},"tags":["nested-reference","unchanged"],"summary":"This document provides guidance and suggestions for Internet Content\n Providers and Application Service Providers who wish to offer their\n service to both IPv6 and IPv4 customers. Many of the points will\n also apply to hosting providers or to any enterprise network\n preparing for IPv6 users.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma","scope_keywords":["6883","delivery","http","license","management","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 6883 This document provides guidance and suggestions for Internet Content\n Providers and Application Service Providers who wish to offer their\n service to both IPv6 and IPv4 customers. Many of the points will\n also apply to hosting providers or to any enterprise network\n preparing for IPv6 users.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it ma 6883 delivery http license management risk subject trust nested-reference unchanged"},{"id":"IETF RFC 6894","type":"specification","body":"IETF","designation":"RFC 6894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6894.txt","https://www.rfc-editor.org/rfc/rfc6894.pdf"],"folder":"IETF/RFC-6894","files":{"txt":{"path":"standards/IETF/RFC-6894/RFC-6894.txt","sha256":"b70b0e397a70bf111ab8691df8361c38d14a65b106dc2b9b857a0520ab820531"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the methodology for benchmarking MPLS Fast\n Reroute (FRR) protection mechanisms for link and node protection.\n This document provides test methodologies and testbed setup for\n measuring failover times of Fast Reroute techniques while considering\n factors (such as underlying links) that might impact\n recovery times for real-time applications bound to MPLS Traffic\n Engineered (MPLS-TE) tunnels.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Se","scope_keywords":["6894","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6894 This document describes the methodology for benchmarking MPLS Fast\n Reroute (FRR) protection mechanisms for link and node protection.\n This document provides test methodologies and testbed setup for\n measuring failover times of Fast Reroute techniques while considering\n factors (such as underlying links) that might impact\n recovery times for real-time applications bound to MPLS Traffic\n Engineered (MPLS-TE) tunnels.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Se 6894 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 6903","type":"specification","body":"IETF","designation":"RFC 6903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6903.txt","https://www.rfc-editor.org/rfc/rfc6903.pdf"],"folder":"IETF/RFC-6903","files":{"txt":{"path":"standards/IETF/RFC-6903/RFC-6903.txt","sha256":"67e762642d2b24fd386c2b47d581e621cc9c5f9c60c994b1411f700010266b8a"}},"tags":["nested-reference","unchanged"],"summary":"This specification defines a number of additional link relation types\n that can used for a range of purposes in a variety of applications\n types.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6903.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n documen","scope_keywords":["6903","hash","http","license","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7089","folder":"IETF/RFC-7089","source":"IETF/RFC-7089/RFC-7089.txt","version":null}],"search_text":"IETF RFC 6903 This specification defines a number of additional link relation types\n that can used for a range of purposes in a variety of applications\n types.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This is a contribution to the RFC Series, independently of any other\n RFC stream. The RFC Editor has chosen to publish this document at\n its discretion and makes no statement about its value for\n implementation or deployment. Documents approved for publication by\n the RFC Editor are not a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc6903.\n\nCopyright Notice\n\n Copyright (c) 2013 IETF Trust and the persons identified as the\n documen 6903 hash http license policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 6908","type":"specification","body":"IETF","designation":"RFC 6908","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6908.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6908.txt","https://www.rfc-editor.org/rfc/rfc6908.pdf"],"folder":"IETF/RFC-6908","files":{"txt":{"path":"standards/IETF/RFC-6908/RFC-6908.txt","sha256":"6e1499fc96734485057316e4968268264e31ef670f60dd9415f23a393122ec77"}},"tags":["nested-reference","unchanged"],"summary":"This document discusses the deployment issues of and the requirements\n for the deployment and operation of Dual-Stack Lite (DS-Lite). This\n document describes the various deployment considerations and\n applicability of the DS-Lite architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info","scope_keywords":["6908","http","license","management","policies","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 6908 This document discusses the deployment issues of and the requirements\n for the deployment and operation of Dual-Stack Lite (DS-Lite). This\n document describes the various deployment considerations and\n applicability of the DS-Lite architecture.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info 6908 http license management policies policy subject trust nested-reference unchanged"},{"id":"IETF RFC 743","type":"specification","body":"IETF","designation":"RFC 743","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc743.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc743.txt","https://www.rfc-editor.org/rfc/rfc743.pdf"],"folder":"IETF/RFC-743","files":{"txt":{"path":"standards/IETF/RFC-743/RFC-743.txt","sha256":"f873a0a73be9229137d2539fa484a8ca4aefe56d225870eeb727558f32f1d8c9"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 743 KLH 30-Dec-77 08:39 42759\nNetwork Working Group K. Harrenstien\nRequest for Comments: 743 SRI-KL\nNIC: 42758 30 December 1977\n\n FTP extension: XRSQ/XRCP\n\nThis RFC describes an extension to FTP which allows the user of an ITS\nFTP server (i.e. on MIT-(AI/ML/MC/DMS)) to mail the text of a message to\nseveral recipients simultaneously; such message transmission is far more\nefficient than the current practice of sending the text again and again\nfor each additional recipient at a site.\n\nWithin this extension, there are two basic ways of sending a single text\nto several recipients. In one, all recipients are specified first, and\nthen the text is sent; in the other, the order is reversed and the text\nis sent first, followed by the recipients. Both schemes are necessary\nbecaue neither by itself is optimal for all systems, as will be\nexplained later. To select a particular scheme, the XR","scope_keywords":["743","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 743 NWG/RFC# 743 KLH 30-Dec-77 08:39 42759\nNetwork Working Group K. Harrenstien\nRequest for Comments: 743 SRI-KL\nNIC: 42758 30 December 1977\n\n FTP extension: XRSQ/XRCP\n\nThis RFC describes an extension to FTP which allows the user of an ITS\nFTP server (i.e. on MIT-(AI/ML/MC/DMS)) to mail the text of a message to\nseveral recipients simultaneously; such message transmission is far more\nefficient than the current practice of sending the text again and again\nfor each additional recipient at a site.\n\nWithin this extension, there are two basic ways of sending a single text\nto several recipients. In one, all recipients are specified first, and\nthen the text is sent; in the other, the order is reversed and the text\nis sent first, followed by the recipients. Both schemes are necessary\nbecaue neither by itself is optimal for all systems, as will be\nexplained later. To select a particular scheme, the XR 743 crl nested-reference unchanged"},{"id":"IETF RFC 697","type":"specification","body":"IETF","designation":"RFC 697","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc697.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc697.txt","https://www.rfc-editor.org/rfc/rfc697.pdf"],"folder":"IETF/RFC-697","files":{"txt":{"path":"standards/IETF/RFC-697/RFC-697.txt","sha256":"879eb476f28202d7ecd4941d7f4053c3c54f5b753787cdc7a4d702d2119051c5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jim Lieb\nRFC # 697 SUMEX-AIM\nNIC # 32963 July 14, 1975\n\n CWD Command of FTP\n\nIntroduction\n\nThe Tenex file system support a \"files only\" directory. This type of\ndirectory cannot be \"logged in\" but it can be \"connected to\". A login\ngives directory \"owner\" access to the job generated by the system and an\naddress space in which the user can execute programs. A connect allows\nan existing job and its associated user \"owner\" access to a directory\nbut creates no address space. The words \"owner\", \"group\", and\n\"universal\" or \"public\" determine which field of the protection\nspecification is to be used to check the legality of a file access\nrequest.\n\nProblem\n\nThe Tenex FTP server does not allow an FTP Login to a \"files only\"\ndirectory. The current protocol contains the CWD (Change Working\nDirectory) command which gets part of the \"connect\" functions but it\ndoes not grant \"owner","scope_keywords":["697"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 775","folder":"IETF/RFC-775","source":"IETF/RFC-775/RFC-775.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 697 Network Working Group Jim Lieb\nRFC # 697 SUMEX-AIM\nNIC # 32963 July 14, 1975\n\n CWD Command of FTP\n\nIntroduction\n\nThe Tenex file system support a \"files only\" directory. This type of\ndirectory cannot be \"logged in\" but it can be \"connected to\". A login\ngives directory \"owner\" access to the job generated by the system and an\naddress space in which the user can execute programs. A connect allows\nan existing job and its associated user \"owner\" access to a directory\nbut creates no address space. The words \"owner\", \"group\", and\n\"universal\" or \"public\" determine which field of the protection\nspecification is to be used to check the legality of a file access\nrequest.\n\nProblem\n\nThe Tenex FTP server does not allow an FTP Login to a \"files only\"\ndirectory. The current protocol contains the CWD (Change Working\nDirectory) command which gets part of the \"connect\" functions but it\ndoes not grant \"owner 697 nested-reference unchanged"},{"id":"IETF RFC 698","type":"specification","body":"IETF","designation":"RFC 698","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc698.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc698.txt","https://www.rfc-editor.org/rfc/rfc698.pdf"],"folder":"IETF/RFC-698","files":{"txt":{"path":"standards/IETF/RFC-698/RFC-698.txt","sha256":"a67d173ac8a5807983f9396ad1f67d0e65f082b08e74b849299c5feb2945c85f"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 698 Jul 1975\nNIC #32964\n\n TELNET EXTENDED ASCII OPTION\n\n1. Command Name and Code.\n\nEXTEND-ASCII 17\n\n2. Command Meanings.\n\nIAC WILL EXTEND-ASCII\n\nThe sender of this command requests Permission to begin\ntransmitting, or confirms that it may now begin transmitting\nextended ASCII, where additional 'control' bits are added to\nnormal ASCII, which are treated sPecially by certain programs on\nthe host computer.\n\nIAC WON'T EXTEND-ASCII\n\nIf the connection is already being operated in extended ASCII\nmode, the sender of this command demands that the receiver begin\ntransmitting data characters in standard NVT ASCII. If the\nconnection is not already being operated in extended ASCII mode,\nThe sender of this command refuses to begin transmitting extended\nASCII.\n\nIAC DO EXTEND-ASCII\n\nThe sender of this command requests that the receiver begin\ntransmitting,or confirms that the receiv","scope_keywords":["698","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0698","folder":"IETF/RFC-0698","source":"IETF/RFC-0698/RFC-0698.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 698 Request for Comments: 698 Jul 1975\nNIC #32964\n\n TELNET EXTENDED ASCII OPTION\n\n1. Command Name and Code.\n\nEXTEND-ASCII 17\n\n2. Command Meanings.\n\nIAC WILL EXTEND-ASCII\n\nThe sender of this command requests Permission to begin\ntransmitting, or confirms that it may now begin transmitting\nextended ASCII, where additional 'control' bits are added to\nnormal ASCII, which are treated sPecially by certain programs on\nthe host computer.\n\nIAC WON'T EXTEND-ASCII\n\nIf the connection is already being operated in extended ASCII\nmode, the sender of this command demands that the receiver begin\ntransmitting data characters in standard NVT ASCII. If the\nconnection is not already being operated in extended ASCII mode,\nThe sender of this command refuses to begin transmitting extended\nASCII.\n\nIAC DO EXTEND-ASCII\n\nThe sender of this command requests that the receiver begin\ntransmitting,or confirms that the receiv 698 key nested-reference unchanged"},{"id":"IETF RFC 6981","type":"specification","body":"IETF","designation":"RFC 6981","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc6981.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc6981.txt","https://www.rfc-editor.org/rfc/rfc6981.pdf"],"folder":"IETF/RFC-6981","files":{"txt":{"path":"standards/IETF/RFC-6981/RFC-6981.txt","sha256":"f9dfd98d5bdd5737d11127ae84c7e0276a3a13fe42334289c384aaf3db687a20"}},"tags":["nested-reference","unchanged"],"summary":"This document presents an illustrative framework for providing fast\n reroute in an IP or MPLS network through encapsulation and forwarding\n to \"not-via\" addresses. The general approach described here uses a\n single level of encapsulation and could be used to protect unicast,\n multicast, and LDP traffic against link, router, and shared risk\n group failure, regardless of network topology and metrics.\n\n The mechanisms presented in this document are purely illustrative of\n the general approach and do not constitute a protocol specification.\n The document represents a snapshot of the work of the Routing Area\n Working Group at the time of publication and is published as a\n document of record. Further work is needed before implementation or\n deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu","scope_keywords":["6981","http","license","path","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 6981 This document presents an illustrative framework for providing fast\n reroute in an IP or MPLS network through encapsulation and forwarding\n to \"not-via\" addresses. The general approach described here uses a\n single level of encapsulation and could be used to protect unicast,\n multicast, and LDP traffic against link, router, and shared risk\n group failure, regardless of network topology and metrics.\n\n The mechanisms presented in this document are purely illustrative of\n the general approach and do not constitute a protocol specification.\n The document represents a snapshot of the work of the Routing Area\n Working Group at the time of publication and is published as a\n document of record. Further work is needed before implementation or\n deployment.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This docu 6981 http license path risk subject trust nested-reference unchanged"},{"id":"IETF RFC 700","type":"specification","body":"IETF","designation":"RFC 700","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc700.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc700.txt","https://www.rfc-editor.org/rfc/rfc700.pdf"],"folder":"IETF/RFC-700","files":{"txt":{"path":"standards/IETF/RFC-700/RFC-700.txt","sha256":"b5cac6ad0e0ed46396f61301cb5ccc7a882198d07be54a4c7d3c135cbccc6e5c"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 700 August 1974\nNIC 31020\nINWG Experiments Note 1\n\n A Protocol Experiment\n\n Eric R. Mader\n William W. Plummer\n Raymond S. Tomlinson\n\nI. Introduction\n\nIn early February, 1974 the main line printer on BBN's TENEX system\nfailed and it was decided to use the PDP-11 line printer via the ARPANET\nboth for the direct purpose of obtaining listings and also the indirect\npurpose of studying network protocols.\n\nII. The Basic Protocol\n\nThe design was based on the protocol described by Cerf and Kahn in INWG\nNote #39. Familiarity with that document is assumed. The following is\na brief sketch of the protocol. Not all features described in this\nsection have been implemented. See Section VI.\n\nAt any instant, the sender has two pointers into the stream of bytes to\nbe sent. Bytes to the left of the LEFT pointer have already been sent\nand acknowledged. Bytes in the \"window\" between the LEFT and RIGHT","scope_keywords":["700","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 700 NWG/RFC 700 August 1974\nNIC 31020\nINWG Experiments Note 1\n\n A Protocol Experiment\n\n Eric R. Mader\n William W. Plummer\n Raymond S. Tomlinson\n\nI. Introduction\n\nIn early February, 1974 the main line printer on BBN's TENEX system\nfailed and it was decided to use the PDP-11 line printer via the ARPANET\nboth for the direct purpose of obtaining listings and also the indirect\npurpose of studying network protocols.\n\nII. The Basic Protocol\n\nThe design was based on the protocol described by Cerf and Kahn in INWG\nNote #39. Familiarity with that document is assumed. The following is\na brief sketch of the protocol. Not all features described in this\nsection have been implemented. See Section VI.\n\nAt any instant, the sender has two pointers into the stream of bytes to\nbe sent. Bytes to the left of the LEFT pointer have already been sent\nand acknowledged. Bytes in the \"window\" between the LEFT and RIGHT 700 trust nested-reference unchanged"},{"id":"IETF RFC 800","type":"specification","body":"IETF","designation":"RFC 800","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc800.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc800.txt","https://www.rfc-editor.org/rfc/rfc800.pdf"],"folder":"IETF/RFC-800","files":{"txt":{"path":"standards/IETF/RFC-800/RFC-800.txt","sha256":"853d642369106de4c47190d1a50c095e5f7876c8435af93a5939e550fb962e77"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 800 J. Vernon\n ISI\n November 1982\n\n Requests For Comments Summary\n Notes: 700-799\n\nThis RFC is a slightly annotated list of the 100 RFCs from RFC 700\nthrough RFC 799. This is a kind of status report on these RFCs.\n\nRFC Author Date Title\n--- ------ ---- -----\n\n799 Mills Sep 81 Internet Name Domains\n\n A suggestion that, as the internet grows, the space of host names\n cannot remain a flat space of globally unique names, and that a\n hierarchy of name domains be introduced; see also RFC 822.\n\n798 Katz Sep 81 Decoding Facsimile Data From the\n Rapicom 450\n\n A description of the encoding/decoding procedure for Rapicom450\n facsimile machine.\n\n797 Katz Sep 81 Format for Bitmap Files\n\n The description of a simple file format for bitmap data.\n\n796 Postel Sep 81 Address Mappings\n\n A description of the way the addresses of a few actual networks are","scope_keywords":["800","delivery","management","timestamp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 800 Network Working Group J. Postel\nRequest for Comments: 800 J. Vernon\n ISI\n November 1982\n\n Requests For Comments Summary\n Notes: 700-799\n\nThis RFC is a slightly annotated list of the 100 RFCs from RFC 700\nthrough RFC 799. This is a kind of status report on these RFCs.\n\nRFC Author Date Title\n--- ------ ---- -----\n\n799 Mills Sep 81 Internet Name Domains\n\n A suggestion that, as the internet grows, the space of host names\n cannot remain a flat space of globally unique names, and that a\n hierarchy of name domains be introduced; see also RFC 822.\n\n798 Katz Sep 81 Decoding Facsimile Data From the\n Rapicom 450\n\n A description of the encoding/decoding procedure for Rapicom450\n facsimile machine.\n\n797 Katz Sep 81 Format for Bitmap Files\n\n The description of a simple file format for bitmap data.\n\n796 Postel Sep 81 Address Mappings\n\n A description of the way the addresses of a few actual networks are 800 delivery management timestamp nested-reference unchanged"},{"id":"IETF RFC 7007","type":"specification","body":"IETF","designation":"RFC 7007","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7007.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7007.txt","https://www.rfc-editor.org/rfc/rfc7007.pdf"],"folder":"IETF/RFC-7007","files":{"txt":{"path":"standards/IETF/RFC-7007/RFC-7007.txt","sha256":"dd8a7935098e0b486b5644048e022d97d701729a2e5d3dbc145790a6c5878f9a"}},"tags":["nested-reference","unchanged"],"summary":"The RTP Profile for Audio and Video Conferences with Minimal Control\n (RTP/AVP) is the basis for many other profiles, such as the Secure\n Real-time Transport Protocol (RTP/SAVP), the Extended RTP Profile for\n Real-time Transport Control Protocol (RTCP)-Based Feedback\n (RTP/AVPF), and the Extended Secure RTP Profile for RTCP-Based\n Feedback (RTP/SAVPF). This document updates RFC 3551, the RTP/AVP\n profile (and by extension, the profiles that build upon it), to\n reflect changes in audio codec usage since that document was\n originally published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet ","scope_keywords":["7007","http","key","license","profile","profiles","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7007 The RTP Profile for Audio and Video Conferences with Minimal Control\n (RTP/AVP) is the basis for many other profiles, such as the Secure\n Real-time Transport Protocol (RTP/SAVP), the Extended RTP Profile for\n Real-time Transport Control Protocol (RTCP)-Based Feedback\n (RTP/AVPF), and the Extended Secure RTP Profile for RTCP-Based\n Feedback (RTP/SAVPF). This document updates RFC 3551, the RTP/AVP\n profile (and by extension, the profiles that build upon it), to\n reflect changes in audio codec usage since that document was\n originally published.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet  7007 http key license profile profiles subject trust nested-reference unchanged"},{"id":"IETF RFC 7016","type":"specification","body":"IETF","designation":"RFC 7016","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7016.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7016.txt","https://www.rfc-editor.org/rfc/rfc7016.pdf"],"folder":"IETF/RFC-7016","files":{"txt":{"path":"standards/IETF/RFC-7016/RFC-7016.txt","sha256":"4cf594f6f57e3d77ea0fd45f0c30219a949a893df318105f931ac8e3c87565d0"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes Adobe's Secure Real-Time Media Flow Protocol\n (RTMFP), an endpoint-to-endpoint communication protocol designed to\n securely transport parallel flows of real-time video, audio, and data\n messages, as well as bulk data, over IP networks. RTMFP has features\n that make it effective for peer-to-peer (P2P) as well as client-\n server communications, even when Network Address Translators (NATs)\n are used.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this document, any ","scope_keywords":["7016","encryption","http","key","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null}],"search_text":"IETF RFC 7016 This memo describes Adobe's Secure Real-Time Media Flow Protocol\n (RTMFP), an endpoint-to-endpoint communication protocol designed to\n securely transport parallel flows of real-time video, audio, and data\n messages, as well as bulk data, over IP networks. RTMFP has features\n that make it effective for peer-to-peer (P2P) as well as client-\n server communications, even when Network Address Translators (NATs)\n are used.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see Section\n 2 of RFC 5741.\n\n Information about the current status of this document, any  7016 encryption http key license path subject trust nested-reference unchanged"},{"id":"IETF RFC 702","type":"specification","body":"IETF","designation":"RFC 702","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc702.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc702.txt","https://www.rfc-editor.org/rfc/rfc702.pdf"],"folder":"IETF/RFC-702","files":{"txt":{"path":"standards/IETF/RFC-702/RFC-702.txt","sha256":"56cc6d7256ef42f9ec30e9b3855ca6ebf8b0c2d574afff1dd9687c2f222e10f7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.W. Dodds\nRFC # 702 BBN-TENEXA\n September 25, 1974\n\n SEPTEMBER, 1974, SURVEY OF NEW-PROTOCOL TELNET SERVERS\n\nLAST MONTH'S SURVEY PRODUCED A GRATIFYING AMOUNT OF FEEDBACK CLARIFYING\nTHE STATUS OF SEVERAL SITES; HOWEVER THERE HAVE BEEN VERY FEW CHANGES IN\nTHE STATUS OF HOST SERVERS. THE CHANGES IN THIS MONTH'S LIST, IN\nNUMERICAL ORDER (HOST NUMBER THROUGHOUT ARE OCTAL):\n\nUCLA-NMC IS NO LONGER A SERVER;\nHOST 205 IS NOW BBN-TENEXD, A NEW SYSTEM (BBNB) IS NOW HOST 61;\nRAND-RCC WAS ACCIDENTALLY OMITTED FROM THE PREVIOUS LIST;\nSDC-LAB HAS BEEN TEMPORARILY ELIMINATED FROM THE LIST UNTIL IT RETURNS\n TO THE NET;\nI4-TENEXA (117) IS NOT A SERVER--KI4B-TENEX (217) IS, AND HAS BEEN ADDED\n TO THE LIST;\nAMES-67 FIXED A BUG, REVEALING TO THE WORLD THE NEW-PROTOCOL SERVER (NO\n OPTIONS) THAT WAS THERE ALL ALONG;\nISI-DEVTENEX (226) AND USC-ECL (327) HAVE BEEN ADDED.\n\nWHAT FOLLOWS IS A","scope_keywords":["702","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 702 Network Working Group D.W. Dodds\nRFC # 702 BBN-TENEXA\n September 25, 1974\n\n SEPTEMBER, 1974, SURVEY OF NEW-PROTOCOL TELNET SERVERS\n\nLAST MONTH'S SURVEY PRODUCED A GRATIFYING AMOUNT OF FEEDBACK CLARIFYING\nTHE STATUS OF SEVERAL SITES; HOWEVER THERE HAVE BEEN VERY FEW CHANGES IN\nTHE STATUS OF HOST SERVERS. THE CHANGES IN THIS MONTH'S LIST, IN\nNUMERICAL ORDER (HOST NUMBER THROUGHOUT ARE OCTAL):\n\nUCLA-NMC IS NO LONGER A SERVER;\nHOST 205 IS NOW BBN-TENEXD, A NEW SYSTEM (BBNB) IS NOW HOST 61;\nRAND-RCC WAS ACCIDENTALLY OMITTED FROM THE PREVIOUS LIST;\nSDC-LAB HAS BEEN TEMPORARILY ELIMINATED FROM THE LIST UNTIL IT RETURNS\n TO THE NET;\nI4-TENEXA (117) IS NOT A SERVER--KI4B-TENEX (217) IS, AND HAS BEEN ADDED\n TO THE LIST;\nAMES-67 FIXED A BUG, REVEALING TO THE WORLD THE NEW-PROTOCOL SERVER (NO\n OPTIONS) THAT WAS THERE ALL ALONG;\nISI-DEVTENEX (226) AND USC-ECL (327) HAVE BEEN ADDED.\n\nWHAT FOLLOWS IS A 702 key nested-reference unchanged"},{"id":"IETF RFC 7020","type":"specification","body":"IETF","designation":"RFC 7020","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7020.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7020.txt","https://www.rfc-editor.org/rfc/rfc7020.pdf"],"folder":"IETF/RFC-7020","files":{"txt":{"path":"standards/IETF/RFC-7020/RFC-7020.txt","sha256":"d170fa9fbbb9f9b4511c0754845b5cc54be5c49041437c786ff76c44aec3caa8"}},"tags":["nested-reference","unchanged"],"summary":"This document provides information about the current Internet Numbers\n Registry System used in the distribution of globally unique Internet\n Protocol (IP) address space and autonomous system (AS) numbers.\n\n This document also provides information about the processes for\n further evolution of the Internet Numbers Registry System.\n\n This document replaces RFC 2050.\n\n This document does not propose any changes to the current Internet\n Numbers Registry System. Rather, it documents the Internet Numbers\n Registry System as it works today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Ste","scope_keywords":["7020","http","license","management","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 7020 This document provides information about the current Internet Numbers\n Registry System used in the distribution of globally unique Internet\n Protocol (IP) address space and autonomous system (AS) numbers.\n\n This document also provides information about the processes for\n further evolution of the Internet Numbers Registry System.\n\n This document replaces RFC 2050.\n\n This document does not propose any changes to the current Internet\n Numbers Registry System. Rather, it documents the Internet Numbers\n Registry System as it works today.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Ste 7020 http license management policies subject trust nested-reference unchanged"},{"id":"IETF RFC 7023","type":"specification","body":"IETF","designation":"RFC 7023","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7023.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7023.txt","https://www.rfc-editor.org/rfc/rfc7023.pdf"],"folder":"IETF/RFC-7023","files":{"txt":{"path":"standards/IETF/RFC-7023/RFC-7023.txt","sha256":"80daa2e7da58d380af481ec5d80b2e1b8126f505ad4a679c44815364ba8bcba4"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies the mapping of defect states between Ethernet\n Attachment Circuits (ACs) and associated Ethernet pseudowires (PWs)\n connected in accordance with the Pseudowire Emulation Edge-to-Edge\n (PWE3) architecture to realize an end-to-end emulated Ethernet\n service. It standardizes the behavior of Provider Edges (PEs) with\n respect to Ethernet PW and AC defects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a","scope_keywords":["7023","http","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 7023 This document specifies the mapping of defect states between Ethernet\n Attachment Circuits (ACs) and associated Ethernet pseudowires (PWs)\n connected in accordance with the Pseudowire Emulation Edge-to-Edge\n (PWE3) architecture to realize an end-to-end emulated Ethernet\n service. It standardizes the behavior of Provider Edges (PEs) with\n respect to Ethernet PW and AC defects.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained a 7023 http key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 703","type":"specification","body":"IETF","designation":"RFC 703","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc703.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc703.txt","https://www.rfc-editor.org/rfc/rfc703.pdf"],"folder":"IETF/RFC-703","files":{"txt":{"path":"standards/IETF/RFC-703/RFC-703.txt","sha256":"640f1605b74131f836bba389f6b01eb4af5aab36d67eedee8e63dace5c22a586"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.W. Dodds\nRFC # 703 BBN-TENEXA\nNIC # 32988 11 July, 1975\n\n July, 1975, Survey of New-Protocol TELNET Servers\n\nIn the nearly five months since the last report several new server sites\nhave joined the network and there has been some significant progress in\nNew-Protocol implementation. Perhaps the New-Protocol implementation on\nthe TIPs scheduled for the end of the year will encourage further\nprogress in the near future.\n\nThere have been numerous changes since the last list (numbers in octal):\n\nSRI-ARC (2) is no longer a server host;\nMIT-AI (206), MIT-ML (306), LONDON (52), and OFFICE-1 (53) have added\n New-Protocol servers;\nLLL-RISOS (25), SDAC-44 (32), and ARPA-DMS (34) have joined the network;\nSCI-TENEX (55), Rutgers-10 (56), USC-ISIC (364), and SUMEX-AIM (70) have\n joined the network with New-Protocol servers.\n\nThe following is the latest version* of the summary a","scope_keywords":["703","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 703 Network Working Group D.W. Dodds\nRFC # 703 BBN-TENEXA\nNIC # 32988 11 July, 1975\n\n July, 1975, Survey of New-Protocol TELNET Servers\n\nIn the nearly five months since the last report several new server sites\nhave joined the network and there has been some significant progress in\nNew-Protocol implementation. Perhaps the New-Protocol implementation on\nthe TIPs scheduled for the end of the year will encourage further\nprogress in the near future.\n\nThere have been numerous changes since the last list (numbers in octal):\n\nSRI-ARC (2) is no longer a server host;\nMIT-AI (206), MIT-ML (306), LONDON (52), and OFFICE-1 (53) have added\n New-Protocol servers;\nLLL-RISOS (25), SDAC-44 (32), and ARPA-DMS (34) have joined the network;\nSCI-TENEX (55), Rutgers-10 (56), USC-ISIC (364), and SUMEX-AIM (70) have\n joined the network with New-Protocol servers.\n\nThe following is the latest version* of the summary a 703 key nested-reference unchanged"},{"id":"IETF RFC 707","type":"specification","body":"IETF","designation":"RFC 707","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc707.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc707.txt","https://www.rfc-editor.org/rfc/rfc707.pdf"],"folder":"IETF/RFC-707","files":{"txt":{"path":"standards/IETF/RFC-707/RFC-707.txt","sha256":"67e4b2d5435304de0bc79e39b980f71fda0e7191bdaf408ff61f8c3cc0de8583"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 707 JEW 14-JAN-76 19:51 34263\nNCC 76 A High-Level Framework for Network-Based Resource Sharing\n\nTHE GOAL, RESOURCE SHARING 1\n\n The principal goal of all resource-sharing computer networks,\nincluding the now international ARPA Network (the ARPANET), is to\nusefully interconnect geographically distributed hardware, software,\nand human resources [1]. Achieving this goal requires the design\nand implementation of various levels of support software within each\nconstituent computer, and the specification of network-wide\n\"protocols\" (that is, conventions regarding the format and the\nrelative timing of network messages) governing their interaction.\nThis paper outlines an alternative to the approach that ARPANET\nsystem builders have been taking since work in this area began in\n1970, and suggests a strategy for modeling distributed systems\nwithin any large computer network. 1a\n\n The first s","scope_keywords":["707"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 707 NWG/RFC# 707 JEW 14-JAN-76 19:51 34263\nNCC 76 A High-Level Framework for Network-Based Resource Sharing\n\nTHE GOAL, RESOURCE SHARING 1\n\n The principal goal of all resource-sharing computer networks,\nincluding the now international ARPA Network (the ARPANET), is to\nusefully interconnect geographically distributed hardware, software,\nand human resources [1]. Achieving this goal requires the design\nand implementation of various levels of support software within each\nconstituent computer, and the specification of network-wide\n\"protocols\" (that is, conventions regarding the format and the\nrelative timing of network messages) governing their interaction.\nThis paper outlines an alternative to the approach that ARPANET\nsystem builders have been taking since work in this area began in\n1970, and suggests a strategy for modeling distributed systems\nwithin any large computer network. 1a\n\n The first s 707 nested-reference unchanged"},{"id":"IETF RFC 7074","type":"specification","body":"IETF","designation":"RFC 7074","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7074.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7074.txt","https://www.rfc-editor.org/rfc/rfc7074.pdf"],"folder":"IETF/RFC-7074","files":{"txt":{"path":"standards/IETF/RFC-7074/RFC-7074.txt","sha256":"4104c8a39801bf8b19531ab8e4c709f33b6b50c96d934e105c36064d3fb386bb"}},"tags":["nested-reference","unchanged"],"summary":"GMPLS provides control for multiple switching technologies and for\n hierarchical switching within a technology. GMPLS routing and\n signaling use common values to indicate the type of switching\n technology. These values are carried in routing protocols via the\n Switching Capability field, and in signaling protocols via the\n Switching Type field. While the values used in these fields are the\n primary indicators of the technology and hierarchy level being\n controlled, the values are not consistently defined and used across\n the different technologies supported by GMPLS. This document is\n intended to resolve the inconsistent definition and use of the\n Switching Capability and Type fields by narrowly scoping the meaning\n and use of the fields. This document updates all documents that use\n the GMPLS Switching Capability and Types fields, in particular RFCs\n 3471, 4202, 4203, and 5307.\n\nStatus ","scope_keywords":["7074","http","identification","license","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 7074 GMPLS provides control for multiple switching technologies and for\n hierarchical switching within a technology. GMPLS routing and\n signaling use common values to indicate the type of switching\n technology. These values are carried in routing protocols via the\n Switching Capability field, and in signaling protocols via the\n Switching Type field. While the values used in these fields are the\n primary indicators of the technology and hierarchy level being\n controlled, the values are not consistently defined and used across\n the different technologies supported by GMPLS. This document is\n intended to resolve the inconsistent definition and use of the\n Switching Capability and Type fields by narrowly scoping the meaning\n and use of the fields. This document updates all documents that use\n the GMPLS Switching Capability and Types fields, in particular RFCs\n 3471, 4202, 4203, and 5307.\n\nStatus  7074 http identification license presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 7079","type":"specification","body":"IETF","designation":"RFC 7079","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7079.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7079.txt","https://www.rfc-editor.org/rfc/rfc7079.pdf"],"folder":"IETF/RFC-7079","files":{"txt":{"path":"standards/IETF/RFC-7079/RFC-7079.txt","sha256":"ac3d92b9144b745152820a370f95f7c8982306be2ee51aae004b59c700e22598"}},"tags":["nested-reference","unchanged"],"summary":"The IETF Pseudowire Emulation Edge-to-Edge (PWE3) working group has\n defined many encapsulations of various layer 1 and layer 2 service-\n specific PDUs and circuit data. In most of these encapsulations, use\n of the Pseudowire (PW) Control Word is required. However, there are\n several encapsulations for which the Control Word is optional, and\n this optionality has been seen in practice to possibly introduce\n interoperability concerns between multiple implementations of those\n encapsulations. This survey of the Pseudowire / Virtual Circuit\n Connectivity Verification (VCCV) user community was conducted to\n determine implementation trends and the possibility of always\n mandating the Control Word.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Forc","scope_keywords":["7079","http","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 7079 The IETF Pseudowire Emulation Edge-to-Edge (PWE3) working group has\n defined many encapsulations of various layer 1 and layer 2 service-\n specific PDUs and circuit data. In most of these encapsulations, use\n of the Pseudowire (PW) Control Word is required. However, there are\n several encapsulations for which the Control Word is optional, and\n this optionality has been seen in practice to possibly introduce\n interoperability concerns between multiple implementations of those\n encapsulations. This survey of the Pseudowire / Virtual Circuit\n Connectivity Verification (VCCV) user community was conducted to\n determine implementation trends and the possibility of always\n mandating the Control Word.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Forc 7079 http license path subject trust nested-reference unchanged"},{"id":"IETF RFC 708","type":"specification","body":"IETF","designation":"RFC 708","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc708.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc708.txt","https://www.rfc-editor.org/rfc/rfc708.pdf"],"folder":"IETF/RFC-708","files":{"txt":{"path":"standards/IETF/RFC-708/RFC-708.txt","sha256":"a6d5d1eb3fa77c51ffeb80e1859a8cc7501de4d4927aaf340bfbd38035c34648"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group James E. White\nRequest for Comments: 708 Augmentation Research Center\n\n Elements of a Distributed Programming System\n\n January 5, 1976\n\n James E. White\n Augmentation Research Center\n\n Stanford Research Institute\n Menlo Park, California 94025\n\n (415) 326-6200 X2960\n\nThis paper suggests some extensions to the simple Procedure Call Protocol\ndescribed in a previous paper (27197). By expanding the procedure call\nmodel and standardizing other common forms of inter-process interaction,\nsuch extensions would provide the applications programmer with an even\nmore powerful distributed programming system.\n\nThe work reported here was supported by the Advanced Research Projects\nAgency of the Department of Defense, and by the Rome Air Development \nCenter of the Air Force.\n\nThis paper will be submitted to publication in the Journal of Computer\nLanguages.\f\n\nNetwork Working Group Jam","scope_keywords":["708","holder","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 708 Network Working Group James E. White\nRequest for Comments: 708 Augmentation Research Center\n\n Elements of a Distributed Programming System\n\n January 5, 1976\n\n James E. White\n Augmentation Research Center\n\n Stanford Research Institute\n Menlo Park, California 94025\n\n (415) 326-6200 X2960\n\nThis paper suggests some extensions to the simple Procedure Call Protocol\ndescribed in a previous paper (27197). By expanding the procedure call\nmodel and standardizing other common forms of inter-process interaction,\nsuch extensions would provide the applications programmer with an even\nmore powerful distributed programming system.\n\nThe work reported here was supported by the Advanced Research Projects\nAgency of the Department of Defense, and by the Rome Air Development \nCenter of the Air Force.\n\nThis paper will be submitted to publication in the Journal of Computer\nLanguages.\f\n\nNetwork Working Group Jam 708 holder presentation nested-reference unchanged"},{"id":"IETF RFC 7107","type":"specification","body":"IETF","designation":"RFC 7107","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7107.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7107.txt","https://www.rfc-editor.org/rfc/rfc7107.pdf"],"folder":"IETF/RFC-7107","files":{"txt":{"path":"standards/IETF/RFC-7107/RFC-7107.txt","sha256":"ef728ddd32fb66a04b2f5f178a2cda4c5c97d2772c6ef339cc81549fb1695933"}},"tags":["nested-reference","unchanged"],"summary":"When the S/MIME Mail Security Working Group was chartered, an object\n identifier arc was donated by RSA Data Security for use by that\n working group. This document describes the object identifiers that\n were assigned in that donated arc, transfers control of that arc to\n IANA, and establishes IANA allocation policies for any future\n assignments within that arc.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current sta","scope_keywords":["7107","algorithm","algorithms","attribute","attributes","certificate","http","key","license","policies","policy","signature","subject","trust","tsp"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 7107 When the S/MIME Mail Security Working Group was chartered, an object\n identifier arc was donated by RSA Data Security for use by that\n working group. This document describes the object identifiers that\n were assigned in that donated arc, transfers control of that arc to\n IANA, and establishes IANA allocation policies for any future\n assignments within that arc.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current sta 7107 algorithm algorithms attribute attributes certificate http key license policies policy signature subject trust tsp nested-reference unchanged"},{"id":"IETF RFC 7118","type":"specification","body":"IETF","designation":"RFC 7118","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7118.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7118.txt","https://www.rfc-editor.org/rfc/rfc7118.pdf"],"folder":"IETF/RFC-7118","files":{"txt":{"path":"standards/IETF/RFC-7118/RFC-7118.txt","sha256":"2adddc1935f4ad8aeba35cf02d1a89dc5f6c7f3ff513787396f8030a5e36df88"}},"tags":["nested-reference","unchanged"],"summary":"The WebSocket protocol enables two-way real-time communication\n between clients and servers in web-based applications. This document\n specifies a WebSocket subprotocol as a reliable transport mechanism\n between Session Initiation Protocol (SIP) entities to enable use of\n SIP in web-oriented deployments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7118.\n\nCopyright Notice\n\n Copyright (","scope_keywords":["7118","authentication","http","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7977","folder":"IETF/RFC-7977","source":"IETF/RFC-7977/RFC-7977.txt","version":null}],"search_text":"IETF RFC 7118 The WebSocket protocol enables two-way real-time communication\n between clients and servers in web-based applications. This document\n specifies a WebSocket subprotocol as a reliable transport mechanism\n between Session Initiation Protocol (SIP) entities to enable use of\n SIP in web-oriented deployments.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7118.\n\nCopyright Notice\n\n Copyright ( 7118 authentication http key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 722","type":"specification","body":"IETF","designation":"RFC 722","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc722.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc722.txt","https://www.rfc-editor.org/rfc/rfc722.pdf"],"folder":"IETF/RFC-722","files":{"txt":{"path":"standards/IETF/RFC-722/RFC-722.txt","sha256":"a10ee78d58dfeb605ccd9876074bb5f02e00ac71cb49ac7be31aed46d7504cb9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jack Haverty (MIT)\nRequest for Comments: 722 Sept 1976\nNIC #36806\n\nI. ABSTRACT\n\n This paper addresses some issues concerned with the\ndesign of distributed services. In particular, it is\nconcerned with the characteristics of the interactions,\nbetween programs which support some service at various\nnetwork sites. The ideas presented are derived mainly from\nexperience with various service protocols [Reference 1]\non the ARPANET.\n\n A model is developed of interactions between programs.\nSalient features of this model which promote and simplify\nthe construction of reliable, responsive services are\nidentified. These dualities are motivated by problems\nexperienced with various ARPANET protocols and in the design\nand maintenance of programs which use these protocols in the\nperformance of some service.\n\n Using this model as a template, the general\narchitecture of one possible i","scope_keywords":["722","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 753","folder":"IETF/RFC-753","source":"IETF/RFC-753/RFC-753.txt","version":null},{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null}],"search_text":"IETF RFC 722 Network Working Group Jack Haverty (MIT)\nRequest for Comments: 722 Sept 1976\nNIC #36806\n\nI. ABSTRACT\n\n This paper addresses some issues concerned with the\ndesign of distributed services. In particular, it is\nconcerned with the characteristics of the interactions,\nbetween programs which support some service at various\nnetwork sites. The ideas presented are derived mainly from\nexperience with various service protocols [Reference 1]\non the ARPANET.\n\n A model is developed of interactions between programs.\nSalient features of this model which promote and simplify\nthe construction of reliable, responsive services are\nidentified. These dualities are motivated by problems\nexperienced with various ARPANET protocols and in the design\nand maintenance of programs which use these protocols in the\nperformance of some service.\n\n Using this model as a template, the general\narchitecture of one possible i 722 presentation nested-reference unchanged"},{"id":"IETF RFC 723","type":"specification","body":"IETF","designation":"RFC 723","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.rfc-editor.org/rfc/rfc723.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc723.txt","https://www.rfc-editor.org/rfc/rfc723.pdf"],"folder":"IETF/RFC-723","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 722","folder":"IETF/RFC-722","source":"IETF/RFC-722/RFC-722.txt","version":null}],"search_text":"IETF RFC 723 nested-reference unavailable"},{"id":"IETF RFC 731","type":"specification","body":"IETF","designation":"RFC 731","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc731.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc731.txt","https://www.rfc-editor.org/rfc/rfc731.pdf"],"folder":"IETF/RFC-731","files":{"txt":{"path":"standards/IETF/RFC-731/RFC-731.txt","sha256":"e8ff05bc5a49e0af39bee434910c7b1974b1149fc99f8379ddc7f4823ff6ac61"}},"tags":["nested-reference","unchanged"],"summary":"John Day Data Entry Terminal Option\nJune 27,1977 NIC 40652\n RFC 731\n\n Telnet Data Entry Terminal Option\n\n1. Command Name and code:\n\n DET 20\n\n2. Command Meanings\n\n IAC WILL DET\n The sender of this command REQUESTS or AGREES to send and\n receive subcommands to control the Data Entry Terminal.\n\n IAC WONT DET\n The sender of this command REFUSES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC DO DET\n The sender of this command REQUESTS or AGREES to send and\n receive subcommands to control the Data Entry Terminal.\n\n IAC DONT DET\n The sender of this command REFUSES to send and receive\n subcommands to control the Data Entry Terminal.\n\n The DET option uses five classes of subcommands 1) to\n establish the requirements and capabilities of the\n application and the terminal, 2) to format the screen, and\n to control the 3) edit, 4) erasure, and 5) transmission\n functions. Th","scope_keywords":["731","attribute","attributes","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 731 John Day Data Entry Terminal Option\nJune 27,1977 NIC 40652\n RFC 731\n\n Telnet Data Entry Terminal Option\n\n1. Command Name and code:\n\n DET 20\n\n2. Command Meanings\n\n IAC WILL DET\n The sender of this command REQUESTS or AGREES to send and\n receive subcommands to control the Data Entry Terminal.\n\n IAC WONT DET\n The sender of this command REFUSES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC DO DET\n The sender of this command REQUESTS or AGREES to send and\n receive subcommands to control the Data Entry Terminal.\n\n IAC DONT DET\n The sender of this command REFUSES to send and receive\n subcommands to control the Data Entry Terminal.\n\n The DET option uses five classes of subcommands 1) to\n establish the requirements and capabilities of the\n application and the terminal, 2) to format the screen, and\n to control the 3) edit, 4) erasure, and 5) transmission\n functions. Th 731 attribute attributes key keys nested-reference unchanged"},{"id":"IETF RFC 732","type":"specification","body":"IETF","designation":"RFC 732","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc732.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc732.txt","https://www.rfc-editor.org/rfc/rfc732.pdf"],"folder":"IETF/RFC-732","files":{"txt":{"path":"standards/IETF/RFC-732/RFC-732.txt","sha256":"80327999641230be9289759fb6910d68477b0eacd32744219688e78b98c4ca7f"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 732 DAY 13-Sep-77 18:38 41762\nData Entry Terminal Option\n\nNetwork Working Group John Day\nRequest for Comments: 732 \nNIC: 41762 12 September 1977\n\nObsoletes: 731\n\n Telnet Data Entry Terminal Option\n\n1. Command Name and Code:\n\n DET 20\n\n2. Command Meanings\n\n IAC WILL DET\n\n The sender of this command REQUESTS or AGREES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC WONT DET\n\n The sender of this command REFUSES to send and receive subcommands\n to control the Data Entry Terminal.\n\n IAC DO DET\n\n The sender of this command REQUESTS or AGREES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC DONT DET\n\n The sender of this command REFUSES to send and receive subcommands\n to control the Data Entry Terminal.\n\n The DET option uses five classes of subcommands 1) to establish the\n requirements and capabilities of the application and the termi","scope_keywords":["732","attribute","attributes","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1043","folder":"IETF/RFC-1043","source":"IETF/RFC-1043/RFC-1043.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 732 NWG/RFC# 732 DAY 13-Sep-77 18:38 41762\nData Entry Terminal Option\n\nNetwork Working Group John Day\nRequest for Comments: 732 \nNIC: 41762 12 September 1977\n\nObsoletes: 731\n\n Telnet Data Entry Terminal Option\n\n1. Command Name and Code:\n\n DET 20\n\n2. Command Meanings\n\n IAC WILL DET\n\n The sender of this command REQUESTS or AGREES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC WONT DET\n\n The sender of this command REFUSES to send and receive subcommands\n to control the Data Entry Terminal.\n\n IAC DO DET\n\n The sender of this command REQUESTS or AGREES to send and receive\n subcommands to control the Data Entry Terminal.\n\n IAC DONT DET\n\n The sender of this command REFUSES to send and receive subcommands\n to control the Data Entry Terminal.\n\n The DET option uses five classes of subcommands 1) to establish the\n requirements and capabilities of the application and the termi 732 attribute attributes key keys nested-reference unchanged"},{"id":"IETF RFC 7262","type":"specification","body":"IETF","designation":"RFC 7262","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7262.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7262.txt","https://www.rfc-editor.org/rfc/rfc7262.pdf"],"folder":"IETF/RFC-7262","files":{"txt":{"path":"standards/IETF/RFC-7262/RFC-7262.txt","sha256":"c8df43d720cc480a57a00854b8b060a6fd8271ad9e35acc69b7429247a3820a1"}},"tags":["nested-reference","unchanged"],"summary":"This memo discusses the requirements for specifications that enable\n telepresence interoperability by describing behaviors and protocols\n for Controlling Multiple Streams for Telepresence (CLUE). In\n addition, the problem statement and related definitions are also\n covered herein.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain","scope_keywords":["7262","attribute","attributes","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null}],"search_text":"IETF RFC 7262 This memo discusses the requirements for specifications that enable\n telepresence interoperability by describing behaviors and protocols\n for Controlling Multiple Streams for Telepresence (CLUE). In\n addition, the problem statement and related definitions are also\n covered herein.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain 7262 attribute attributes http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 727","type":"specification","body":"IETF","designation":"RFC 727","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc727.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc727.txt","https://www.rfc-editor.org/rfc/rfc727.pdf"],"folder":"IETF/RFC-727","files":{"txt":{"path":"standards/IETF/RFC-727/RFC-727.txt","sha256":"5b9167480106bbbd76b3080d67def774fdb6dae4891163956e40491ab0df189e"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 727 MRC 26-APR-77 18:24 40025\nTelnet Logout Option\n\nNetwork Working Group Mark Crispin\nRequest for Comments 727 MIT-AI\nNIC 40025 27 April 1977\n\n TELNET Logout Option\n\n1. Command name and code.\n\n LOGOUT 18\n\n2. Command meanings.\n\n IAC WILL LOGOUT\n\n The sender of this command REQUESTS permission to, or confirms\n that it will, forcibly log off the user process at its end.\n\n IAC WON'T LOGOUT\n\n The sender of this command REFUSES to forcibly log off the user\n process at its end.\n\n IAC DO LOGOUT\n\n The sender of this command REQUESTS that the receiver forcibly log\n off the user process at the receiver's end, or confirms that the\n receiver has its permission to do so.\n\n IAC DON'T LOGOUT\n\n The sender of this command DEMANDS that the receiver not forcibly\n log off the user process at the receiver's end.\n\n3. Default.\n\n WON'T LOGOUT\n\n DON'T LOGOUT\n\n i.e., no forcible logging off of the server","scope_keywords":["727"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 727 NWG/RFC# 727 MRC 26-APR-77 18:24 40025\nTelnet Logout Option\n\nNetwork Working Group Mark Crispin\nRequest for Comments 727 MIT-AI\nNIC 40025 27 April 1977\n\n TELNET Logout Option\n\n1. Command name and code.\n\n LOGOUT 18\n\n2. Command meanings.\n\n IAC WILL LOGOUT\n\n The sender of this command REQUESTS permission to, or confirms\n that it will, forcibly log off the user process at its end.\n\n IAC WON'T LOGOUT\n\n The sender of this command REFUSES to forcibly log off the user\n process at its end.\n\n IAC DO LOGOUT\n\n The sender of this command REQUESTS that the receiver forcibly log\n off the user process at the receiver's end, or confirms that the\n receiver has its permission to do so.\n\n IAC DON'T LOGOUT\n\n The sender of this command DEMANDS that the receiver not forcibly\n log off the user process at the receiver's end.\n\n3. Default.\n\n WON'T LOGOUT\n\n DON'T LOGOUT\n\n i.e., no forcible logging off of the server 727 nested-reference unchanged"},{"id":"IETF RFC 7274","type":"specification","body":"IETF","designation":"RFC 7274","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7274.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7274.txt","https://www.rfc-editor.org/rfc/rfc7274.pdf"],"folder":"IETF/RFC-7274","files":{"txt":{"path":"standards/IETF/RFC-7274/RFC-7274.txt","sha256":"5059d8709c33bbe8764e6242a173500a0c38134e5baef7a6276c9fd09263224f"}},"tags":["nested-reference","unchanged"],"summary":"Some MPLS labels have been allocated for specific purposes. A block\n of labels (0-15) has been set aside to this end; these labels are\n commonly called \"reserved labels\". They will be called \"special-\n purpose labels\" in this document.\n\n As there are only 16 of these special-purpose labels, caution is\n needed in the allocation of new special-purpose labels; yet, at the\n same time, forward progress should be allowed when one is called for.\n\n This memo defines new procedures for the allocation and retirement of\n special-purpose labels, as well as a method to extend the special-\n purpose label space and a description of how to handle extended\n special-purpose labels in the data plane. Finally, this memo renames\n the IANA registry for special-purpose labels to \"Special-Purpose MPLS\n Label Values\" and creates a new registry called the \"Extended\n Special-Purpose MPLS Label Values\" registry.\n\n ","scope_keywords":["7274","http","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 7274 Some MPLS labels have been allocated for specific purposes. A block\n of labels (0-15) has been set aside to this end; these labels are\n commonly called \"reserved labels\". They will be called \"special-\n purpose labels\" in this document.\n\n As there are only 16 of these special-purpose labels, caution is\n needed in the allocation of new special-purpose labels; yet, at the\n same time, forward progress should be allowed when one is called for.\n\n This memo defines new procedures for the allocation and retirement of\n special-purpose labels, as well as a method to extend the special-\n purpose label space and a description of how to handle extended\n special-purpose labels in the data plane. Finally, this memo renames\n the IANA registry for special-purpose labels to \"Special-Purpose MPLS\n Label Values\" and creates a new registry called the \"Extended\n Special-Purpose MPLS Label Values\" registry.\n\n  7274 http key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 728","type":"specification","body":"IETF","designation":"RFC 728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc728.txt","https://www.rfc-editor.org/rfc/rfc728.pdf"],"folder":"IETF/RFC-728","files":{"txt":{"path":"standards/IETF/RFC-728/RFC-728.txt","sha256":"175ac4b241b0274c9ba03dcff49eb99c39ebf61ee7683e6d54fcc83b109227f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Day\nRequest for Comments: 728 Apr 1977\nNIC #40036\n\n A Minor Pitfall in the Telnet Protocol\n\nDesigners of Telnet options should be aware of the following possible\ncase in the Telnet protocol which may generate unexpected behavior on\neither end of the connection. Although at present none of the existing\noptions are susceptible to this problem, it could arise in the future.\n\nThe Telnet sync sequence causes all data to be deleted from the data\nstream until a data mark is encountered. Telnet control functions are\nnot affected by the sync sequence (see page 9 of the protocol\nspecification). A Telnet option subnegotiation could be defined such\nthat it had an affect on the data following it in the data stream. For\nexample, a subnegotiation might be used to indicate the terminal was to\ndisplay the following data in a particular font or should receive other\nspecial treat","scope_keywords":["728"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 731","folder":"IETF/RFC-731","source":"IETF/RFC-731/RFC-731.txt","version":null},{"body":"IETF","designation":"RFC 732","folder":"IETF/RFC-732","source":"IETF/RFC-732/RFC-732.txt","version":null}],"search_text":"IETF RFC 728 Network Working Group John Day\nRequest for Comments: 728 Apr 1977\nNIC #40036\n\n A Minor Pitfall in the Telnet Protocol\n\nDesigners of Telnet options should be aware of the following possible\ncase in the Telnet protocol which may generate unexpected behavior on\neither end of the connection. Although at present none of the existing\noptions are susceptible to this problem, it could arise in the future.\n\nThe Telnet sync sequence causes all data to be deleted from the data\nstream until a data mark is encountered. Telnet control functions are\nnot affected by the sync sequence (see page 9 of the protocol\nspecification). A Telnet option subnegotiation could be defined such\nthat it had an affect on the data following it in the data stream. For\nexample, a subnegotiation might be used to indicate the terminal was to\ndisplay the following data in a particular font or should receive other\nspecial treat 728 nested-reference unchanged"},{"id":"IETF RFC 7289","type":"specification","body":"IETF","designation":"RFC 7289","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7289.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7289.txt","https://www.rfc-editor.org/rfc/rfc7289.pdf"],"folder":"IETF/RFC-7289","files":{"txt":{"path":"standards/IETF/RFC-7289/RFC-7289.txt","sha256":"6ecd4d38389bea6830672f7d20fb8e683527e63df620862cc4752b360c5ef374"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a framework to integrate a Network Address\n Translation (NAT) layer into an operator's network to function as a\n Carrier-Grade NAT (also known as CGN or Large-Scale NAT). The CGN\n infrastructure will often form a NAT444 environment as the subscriber\n home network will likely also maintain a subscriber-side NAT\n function. Exhaustion of the IPv4 address pool is a major driver\n compelling some operators to implement CGN. Although operators may\n wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near-\n term needs may not be satisfied with an IPv6 deployment alone. This\n document provides a practical integration model that allows the CGN\n platform to be integrated into the network, meeting the connectivity\n needs of the subscriber while being mindful of not disrupting\n existing services and meeting the technical challenges that CGN\n brings. The model includ","scope_keywords":["7289","delivery","http","key","license","path","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7289 This document specifies a framework to integrate a Network Address\n Translation (NAT) layer into an operator's network to function as a\n Carrier-Grade NAT (also known as CGN or Large-Scale NAT). The CGN\n infrastructure will often form a NAT444 environment as the subscriber\n home network will likely also maintain a subscriber-side NAT\n function. Exhaustion of the IPv4 address pool is a major driver\n compelling some operators to implement CGN. Although operators may\n wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near-\n term needs may not be satisfied with an IPv6 deployment alone. This\n document provides a practical integration model that allows the CGN\n platform to be integrated into the network, meeting the connectivity\n needs of the subscriber while being mindful of not disrupting\n existing services and meeting the technical challenges that CGN\n brings. The model includ 7289 delivery http key license path policy subject trust nested-reference unchanged"},{"id":"IETF RFC 729","type":"specification","body":"IETF","designation":"RFC 729","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc729.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc729.txt","https://www.rfc-editor.org/rfc/rfc729.pdf"],"folder":"IETF/RFC-729","files":{"txt":{"path":"standards/IETF/RFC-729/RFC-729.txt","sha256":"cf7d5c1048201ab2f9e071c864776f5060e7ed5068345867163e08d9721f7f39"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Dave Crocker, Rand-ISD\nRequest for Comments: 729 (Dcrocker at Rand-Unix)\nNlC: 40306 13 May l977\n\n TELNET Byte Macro Option\n\n1. Command name and code:\n\n BM 19\n\n2. Command Meanings:\n\n IAC WILL BM\n\n The sender of this command REQUESTS or AGREES to use the BM\n option, and will send sing1e data characters which are to be\n interpreted as if longer data strings had been sent.\n\n IAC WON'T BM\n\n The sender of this option REFUSES to send single data\n characters which are to be interpreted as if longer data\n strings had been sent.\n\n IAC DO BM\n\n The sender REQUESTS or AGREES to have the other side (send of\n WILL BM) issue send single data characters which are to be\n interpreted as if longer data strings had been sent.\n\n IAC DON'T BM\n\n The sender REFUSES to allow the other side to send single data\n characters which are to be interpreted as if longer data\n strings had been sent.\n\n","scope_keywords":["729","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 731","folder":"IETF/RFC-731","source":"IETF/RFC-731/RFC-731.txt","version":null},{"body":"IETF","designation":"RFC 732","folder":"IETF/RFC-732","source":"IETF/RFC-732/RFC-732.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 729 Network Working Group Dave Crocker, Rand-ISD\nRequest for Comments: 729 (Dcrocker at Rand-Unix)\nNlC: 40306 13 May l977\n\n TELNET Byte Macro Option\n\n1. Command name and code:\n\n BM 19\n\n2. Command Meanings:\n\n IAC WILL BM\n\n The sender of this command REQUESTS or AGREES to use the BM\n option, and will send sing1e data characters which are to be\n interpreted as if longer data strings had been sent.\n\n IAC WON'T BM\n\n The sender of this option REFUSES to send single data\n characters which are to be interpreted as if longer data\n strings had been sent.\n\n IAC DO BM\n\n The sender REQUESTS or AGREES to have the other side (send of\n WILL BM) issue send single data characters which are to be\n interpreted as if longer data strings had been sent.\n\n IAC DON'T BM\n\n The sender REFUSES to allow the other side to send single data\n characters which are to be interpreted as if longer data\n strings had been sent.\n\n 729 subject nested-reference unchanged"},{"id":"IETF RFC 7993","type":"specification","body":"IETF","designation":"RFC 7993","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7993.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7993.txt","https://www.rfc-editor.org/rfc/rfc7993.pdf"],"folder":"IETF/RFC-7993","files":{"txt":{"path":"standards/IETF/RFC-7993/RFC-7993.txt","sha256":"4a7cb08eb611feadecdedddf575b08d1b1a4f95d5e8212431db4c01f636f987f"}},"tags":["nested-reference","unchanged"],"summary":"The HTML format for RFCs assigns style guidance to a Cascading Style\n Sheet (CSS) specifically defined for the RFC Series. The embedded,\n default CSS as included by the RFC Editor is expected to take into\n account accessibility needs and to be built along a responsive design\n model. This document describes the requirements for the default CSS\n used by the RFC Editor. The class names are based on the classes\n defined in \"HTML for RFCs\" (RFC 7992).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level ","scope_keywords":["7993","attribute","attributes","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"IETF RFC 7993 The HTML format for RFCs assigns style guidance to a Cascading Style\n Sheet (CSS) specifically defined for the RFC Series. The embedded,\n default CSS as included by the RFC Editor is expected to take into\n account accessibility needs and to be built along a responsive design\n model. This document describes the requirements for the default CSS\n used by the RFC Editor. The class names are based on the classes\n defined in \"HTML for RFCs\" (RFC 7992).\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Architecture Board (IAB)\n and represents information that the IAB has deemed valuable to\n provide for permanent record. It represents the consensus of the\n Internet Architecture Board (IAB). Documents approved for\n publication by the IAB are not a candidate for any level  7993 attribute attributes http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7324","type":"specification","body":"IETF","designation":"RFC 7324","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7324.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7324.txt","https://www.rfc-editor.org/rfc/rfc7324.pdf"],"folder":"IETF/RFC-7324","files":{"txt":{"path":"standards/IETF/RFC-7324/RFC-7324.txt","sha256":"8b40235cca258c602045bcb43fd4c81261bf865a0a8ca7e5d6552ad27b518f6e"}},"tags":["nested-reference","unchanged"],"summary":"This document contains a number of updates to the Protection State\n Coordination (PSC) logic defined in RFC 6378, \"MPLS Transport Profile\n (MPLS-TP) Linear Protection\". These updates provide some rules and\n recommendations around the use of TLVs in PSC, address some issues\n raised in an ITU-T liaison statement, and clarify PSC's behavior in a\n case not well explained in RFC 6378.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain","scope_keywords":["7324","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"IETF RFC 7324 This document contains a number of updates to the Protection State\n Coordination (PSC) logic defined in RFC 6378, \"MPLS Transport Profile\n (MPLS-TP) Linear Protection\". These updates provide some rules and\n recommendations around the use of TLVs in PSC, address some issues\n raised in an ITU-T liaison statement, and clarify PSC's behavior in a\n case not well explained in RFC 6378.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain 7324 http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 772","type":"specification","body":"IETF","designation":"RFC 772","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc772.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc772.txt","https://www.rfc-editor.org/rfc/rfc772.pdf"],"folder":"IETF/RFC-772","files":{"txt":{"path":"standards/IETF/RFC-772/RFC-772.txt","sha256":"c16c42481aeeb869a9b4a7dff9c1a1e54ef28a9ee0eca0626b7635b0b016827d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Sluizer\nRequest for Comments: 772 J. Postel\n ISI\n September 1980\n\n MAIL TRANSFER PROTOCOL\n\nPREFACE\n\n This is a first draft of this protocol and comments are very\n definitely requested.\n\nINTRODUCTION\n\n The objective of Mail Transfer Protocol (MTP) is to transfer mail\n reliably and efficiently.\n\n This paper assumes knowledge of the following protocols described in\n the ARPA Internet Protocol Handbook. The reader will note strong\n similarities to portions of the File Transfer Protocol; in part, this\n is due to the original ARPA Network implementation of computer mail\n as a feature of FTP.\n\n The ARPANET Host-to-Host Protocol [Network Control Protocol] (NCP)\n\n The Transmission Control Protocol (TCP)\n\n The TELNET Protocol (TELNET)\n\n The File Transfer Protocol (FTP)\n\nDISCUSSION\n\n In this section, the terminology and the MTP model are discussed.\n The terms defined in thi","scope_keywords":["772","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 780","folder":"IETF/RFC-780","source":"IETF/RFC-780/RFC-780.txt","version":null}],"search_text":"IETF RFC 772 Network Working Group S. Sluizer\nRequest for Comments: 772 J. Postel\n ISI\n September 1980\n\n MAIL TRANSFER PROTOCOL\n\nPREFACE\n\n This is a first draft of this protocol and comments are very\n definitely requested.\n\nINTRODUCTION\n\n The objective of Mail Transfer Protocol (MTP) is to transfer mail\n reliably and efficiently.\n\n This paper assumes knowledge of the following protocols described in\n the ARPA Internet Protocol Handbook. The reader will note strong\n similarities to portions of the File Transfer Protocol; in part, this\n is due to the original ARPA Network implementation of computer mail\n as a feature of FTP.\n\n The ARPANET Host-to-Host Protocol [Network Control Protocol] (NCP)\n\n The Transmission Control Protocol (TCP)\n\n The TELNET Protocol (TELNET)\n\n The File Transfer Protocol (FTP)\n\nDISCUSSION\n\n In this section, the terminology and the MTP model are discussed.\n The terms defined in thi 772 path presentation nested-reference unchanged"},{"id":"IETF RFC 780","type":"specification","body":"IETF","designation":"RFC 780","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc780.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc780.txt","https://www.rfc-editor.org/rfc/rfc780.pdf"],"folder":"IETF/RFC-780","files":{"txt":{"path":"standards/IETF/RFC-780/RFC-780.txt","sha256":"4bcf307bf4e11c1810bb314c5bd77d0517f28511ffac5863f1d0f1a6e49f7576"}},"tags":["nested-reference","unchanged"],"summary":"MAIL TRANSFER PROTOCOL\n \n \n \n Suzanne Sluizer\n \n and\n \n Jonathan B. Postel\n\n RFC 780\n\n May 1981\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nMay 1981 RFC 780\nMail Transfer Protocol \n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE MTP MODEL ................................................. 2\n\n 3. BASIC MAIL .................................................... 4\n\n 3.1. Forwarding ............................................... 5\n 3.2. Source Routing ........................................... 6\n\n 4. MULTI-RECIPIENT MAIL .......................................... 8\n\n 4.1. Scheme Selection: MRSQ ................................... 8\n 4.2. Message Text Specification: MAIL ......................... 9\n 4.3. Recipient Specification: MRCP ..","scope_keywords":["780","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 788","folder":"IETF/RFC-788","source":"IETF/RFC-788/RFC-788.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null}],"search_text":"IETF RFC 780 MAIL TRANSFER PROTOCOL\n \n \n \n Suzanne Sluizer\n \n and\n \n Jonathan B. Postel\n\n RFC 780\n\n May 1981\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nMay 1981 RFC 780\nMail Transfer Protocol \n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE MTP MODEL ................................................. 2\n\n 3. BASIC MAIL .................................................... 4\n\n 3.1. Forwarding ............................................... 5\n 3.2. Source Routing ........................................... 6\n\n 4. MULTI-RECIPIENT MAIL .......................................... 8\n\n 4.1. Scheme Selection: MRSQ ................................... 8\n 4.2. Message Text Specification: MAIL ......................... 9\n 4.3. Recipient Specification: MRCP .. 780 path nested-reference unchanged"},{"id":"IETF RFC 788","type":"specification","body":"IETF","designation":"RFC 788","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc788.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc788.txt","https://www.rfc-editor.org/rfc/rfc788.pdf"],"folder":"IETF/RFC-788","files":{"txt":{"path":"standards/IETF/RFC-788/RFC-788.txt","sha256":"12c6abea850130fbe46e3343d84d9245afc7324f9597a7891cd12eafdba6433d"}},"tags":["nested-reference","unchanged"],"summary":"RFC788\n \n\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n November 1981\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n \nRFC 788 November 1981\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 10\n 3.5. Opening and Closing ..................................... 12\n 3.6. Relaying ......................","scope_keywords":["788"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0821","folder":"IETF/RFC-0821","source":"IETF/RFC-0821/RFC-0821.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 821","folder":"IETF/RFC-821","source":"IETF/RFC-821/RFC-821.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 788 RFC788\n \n\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n November 1981\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n \nRFC 788 November 1981\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 10\n 3.5. Opening and Closing ..................................... 12\n 3.6. Relaying ...................... 788 nested-reference unchanged"},{"id":"IETF RFC 805","type":"specification","body":"IETF","designation":"RFC 805","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc805.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc805.txt","https://www.rfc-editor.org/rfc/rfc805.pdf"],"folder":"IETF/RFC-805","files":{"txt":{"path":"standards/IETF/RFC-805/RFC-805.txt","sha256":"b67f7c59f128e340e490a627c247d8974bbb3c83623c3675db649f03034a9db4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 805 ISI\n 8 February 1982\n\n Computer Mail Meeting Notes\n\nIntroduction\n\n A meeting was held on the 11th of January 1982 at USC Information\n Sciences Institute to discuss addressing issues in computer mail.\n The attendees are listed at the end of this memo. The major\n conclusion reached at the meeting is to extend the\n \"username@hostname\" mailbox format to \"username@host.domain\", where\n the domain itself can be further structured.\n\nOverview\n\n The meeting opened with a brief discussion of the objectives of the\n meeting and a review of the agenda.\n\n The meeting was called to discuss a few specific issues in text\n mail systems for the ARPA Internet. In particular, issues of\n addressing are of major concern as we develop an internet in which\n mail relaying is a common occurance. We need to discuss\n alternatives in the design of the mail syst","scope_keywords":["805","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null}],"search_text":"IETF RFC 805 Network Working Group J. Postel\nRequest for Comments: 805 ISI\n 8 February 1982\n\n Computer Mail Meeting Notes\n\nIntroduction\n\n A meeting was held on the 11th of January 1982 at USC Information\n Sciences Institute to discuss addressing issues in computer mail.\n The attendees are listed at the end of this memo. The major\n conclusion reached at the meeting is to extend the\n \"username@hostname\" mailbox format to \"username@host.domain\", where\n the domain itself can be further structured.\n\nOverview\n\n The meeting opened with a brief discussion of the objectives of the\n meeting and a review of the agenda.\n\n The meeting was called to discuss a few specific issues in text\n mail systems for the ARPA Internet. In particular, issues of\n addressing are of major concern as we develop an internet in which\n mail relaying is a common occurance. We need to discuss\n alternatives in the design of the mail syst 805 identification key nested-reference unchanged"},{"id":"IETF RFC 806","type":"specification","body":"IETF","designation":"RFC 806","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc806.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc806.txt","https://www.rfc-editor.org/rfc/rfc806.pdf"],"folder":"IETF/RFC-806","files":{"txt":{"path":"standards/IETF/RFC-806/RFC-806.txt","sha256":"d4096f19e0e341d11fd2d2ffc4e66b4598c5625e76fc07e7f2a53934509c0a36"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRequest for Comments: 806\n\n \n Proposed Federal Information Processing Standard\n\n SPECIFICATION FOR MESSAGE FORMAT FOR \n COMPUTER BASED MESSAGE SYSTEMS\n\n National Bureau of Standards\n Institute for Computer Sciences and Technology\n\n September 1981\n\n \n\n \n \n \n\n \n \n\f\n\f\n\n TABLE OF CONTENTS\n\n Page\n\n EXECUTIVE SUMMARY 1\n\n 1. INTRODUCTION 3\n\n 1.1 Guide to Reading This Document 3\n 1.2 Vendor-Defined Extensions to the Specification 4\n 1.3 The Scope of the Message Format Specification 4\n 1.4 Issues Not Within the Scope of the Message Format 4\n Specification\n 1.5 Relationship to Other Efforts 5\n\n 2. A SIMPLE MODEL OF A CBMS ENVIRONMENT 6\n\n 2.1 Logical Model of a CBMS 8\n 2.2 Relationship to the ISO Reference Model for Open 10\n Systems Interconnection\n 2.3 Messages and Fields 10\n 2.4 Message Originators and Recipients 11\n\n 3. SEMANTICS 12\n\n 3.1 Semantics of Message Fields 12\n 3.1","scope_keywords":["806","delivery","encryption"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 806 Network Working Group\nRequest for Comments: 806\n\n \n Proposed Federal Information Processing Standard\n\n SPECIFICATION FOR MESSAGE FORMAT FOR \n COMPUTER BASED MESSAGE SYSTEMS\n\n National Bureau of Standards\n Institute for Computer Sciences and Technology\n\n September 1981\n\n \n\n \n \n \n\n \n \n\f\n\f\n\n TABLE OF CONTENTS\n\n Page\n\n EXECUTIVE SUMMARY 1\n\n 1. INTRODUCTION 3\n\n 1.1 Guide to Reading This Document 3\n 1.2 Vendor-Defined Extensions to the Specification 4\n 1.3 The Scope of the Message Format Specification 4\n 1.4 Issues Not Within the Scope of the Message Format 4\n Specification\n 1.5 Relationship to Other Efforts 5\n\n 2. A SIMPLE MODEL OF A CBMS ENVIRONMENT 6\n\n 2.1 Logical Model of a CBMS 8\n 2.2 Relationship to the ISO Reference Model for Open 10\n Systems Interconnection\n 2.3 Messages and Fields 10\n 2.4 Message Originators and Recipients 11\n\n 3. SEMANTICS 12\n\n 3.1 Semantics of Message Fields 12\n 3.1 806 delivery encryption nested-reference unchanged"},{"id":"IETF RFC 841","type":"specification","body":"IETF","designation":"RFC 841","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc841.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc841.txt","https://www.rfc-editor.org/rfc/rfc841.pdf"],"folder":"IETF/RFC-841","files":{"txt":{"path":"standards/IETF/RFC-841/RFC-841.txt","sha256":"72682c67f9d6f9a0d2d08126e576dd2bf34df8fa3e6c43ec368dcdf396989ff1"}},"tags":["nested-reference","unchanged"],"summary":"RFC 841\n\n FIPS Pub 98\n\n SPECIFICATION FOR MESSAGE FORMAT FOR COMPUTER\n BASED MESSAGE SYSTEMS\n\n \n\n 27 January 1983\n\n National Bureau of Standards\n\n This RFC is FIPS 98. The purpose of distributing this document\n as an RFC is to make it easily accesible to the ARPA research\n community. This RFC does not specify a standard for the ARPA\n Internet.\n\n\f\n\f\n\n TABLE OF CONTENTS\n\n Page\n\n EXECUTIVE SUMMARY 5\n\n 1. INTRODUCTION 7\n\n 1.1 Guide to Reading This Document 7\n 1.2 Vendor-Defined Extensions to the Specification 8\n 1.3 The Scope of the Message Format Specification 8\n 1.4 Issues Not Within the Scope of the Message Format 8\n Specification\n 1.5 Relationship to Other Efforts 9\n\n 2. A SIMPLE MODEL OF A CBMS ENVIRONMENT 10\n\n 2.1 Logical Model of a CBMS 12\n 2.2 Relationship to the ISO Reference Model for Open 14\n Systems Interconnection\n 2.3 Messages and Fields 14\n 2.4 Message Originators and Recipien","scope_keywords":["841","delivery","encryption"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 841 RFC 841\n\n FIPS Pub 98\n\n SPECIFICATION FOR MESSAGE FORMAT FOR COMPUTER\n BASED MESSAGE SYSTEMS\n\n \n\n 27 January 1983\n\n National Bureau of Standards\n\n This RFC is FIPS 98. The purpose of distributing this document\n as an RFC is to make it easily accesible to the ARPA research\n community. This RFC does not specify a standard for the ARPA\n Internet.\n\n\f\n\f\n\n TABLE OF CONTENTS\n\n Page\n\n EXECUTIVE SUMMARY 5\n\n 1. INTRODUCTION 7\n\n 1.1 Guide to Reading This Document 7\n 1.2 Vendor-Defined Extensions to the Specification 8\n 1.3 The Scope of the Message Format Specification 8\n 1.4 Issues Not Within the Scope of the Message Format 8\n Specification\n 1.5 Relationship to Other Efforts 9\n\n 2. A SIMPLE MODEL OF A CBMS ENVIRONMENT 10\n\n 2.1 Logical Model of a CBMS 12\n 2.2 Relationship to the ISO Reference Model for Open 14\n Systems Interconnection\n 2.3 Messages and Fields 14\n 2.4 Message Originators and Recipien 841 delivery encryption nested-reference unchanged"},{"id":"IETF RFC 734","type":"specification","body":"IETF","designation":"RFC 734","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc734.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc734.txt","https://www.rfc-editor.org/rfc/rfc734.pdf"],"folder":"IETF/RFC-734","files":{"txt":{"path":"standards/IETF/RFC-734/RFC-734.txt","sha256":"4b1d7e1de3a9b6f6690f9c197f19f51b98601d5fd8ae61ca2a19c8b0e7cd25a4"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 734 MRC 07-OCT-77 08:46 41953\nSUPDUP Display Protocol Page 1\n\nNetwork Working Group Mark Crispin\nRequest for Comments 734 SU-AI\nNIC 41953 7 October 1977\n\n SUPDUP Protocol\n\nINTRODUCTION\n\nThis document describes the SUPDUP protocol, a highly efficient display\ntelnet protocol. It originally started as a private protocol between the\nITS systems at MIT to allow a user at any one of these systems to use one\nof the others as a display. At the current writing, SUPDUP user programs\nalso exist for Data Disc and Datamedia displays at SU-AI and for\nDatamedias at SRI-KL. The author is not aware of any SUPDUP servers other\nthan at the four MIT ITS sites.\n\nThe advantage of the SUPDUP protocol over an individual terminal's\nprotocol is that SUPDUP defines a \"virtual\" or \"software\" display terminal\nthat implements relevant cursor motion operations. The protocol is not\nbuilt on any particular disp","scope_keywords":["734","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 736","folder":"IETF/RFC-736","source":"IETF/RFC-736/RFC-736.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 746","folder":"IETF/RFC-746","source":"IETF/RFC-746/RFC-746.txt","version":null},{"body":"IETF","designation":"RFC 747","folder":"IETF/RFC-747","source":"IETF/RFC-747/RFC-747.txt","version":null},{"body":"IETF","designation":"RFC 749","folder":"IETF/RFC-749","source":"IETF/RFC-749/RFC-749.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 779","folder":"IETF/RFC-779","source":"IETF/RFC-779/RFC-779.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 734 NWG/RFC# 734 MRC 07-OCT-77 08:46 41953\nSUPDUP Display Protocol Page 1\n\nNetwork Working Group Mark Crispin\nRequest for Comments 734 SU-AI\nNIC 41953 7 October 1977\n\n SUPDUP Protocol\n\nINTRODUCTION\n\nThis document describes the SUPDUP protocol, a highly efficient display\ntelnet protocol. It originally started as a private protocol between the\nITS systems at MIT to allow a user at any one of these systems to use one\nof the others as a display. At the current writing, SUPDUP user programs\nalso exist for Data Disc and Datamedia displays at SU-AI and for\nDatamedias at SRI-KL. The author is not aware of any SUPDUP servers other\nthan at the four MIT ITS sites.\n\nThe advantage of the SUPDUP protocol over an individual terminal's\nprotocol is that SUPDUP defines a \"virtual\" or \"software\" display terminal\nthat implements relevant cursor motion operations. The protocol is not\nbuilt on any particular disp 734 key keys nested-reference unchanged"},{"id":"IETF RFC 736","type":"specification","body":"IETF","designation":"RFC 736","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc736.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc736.txt","https://www.rfc-editor.org/rfc/rfc736.pdf"],"folder":"IETF/RFC-736","files":{"txt":{"path":"standards/IETF/RFC-736/RFC-736.txt","sha256":"d056c29801a6bbaf65dd6392718c2d0431100465a7c6a659809046a83743f70a"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 736 MRC 31-OCT-77 23:28 42213\nTelnet SUPDUP Option\n\nNetwork Working Group Mark Crispin\nRequest for Comments 736 SU-AI\nNIC 42213 31 October 1977\n\n TELNET SUPDUP Option\n\n1. Command name and code.\n\n SUPDUP 21\n\n2. Command meanings.\n\n IAC WILL SUPDUP\n\n The sender of this command REQUESTS permission to, or confirms\n that it will, use the SUPDUP display protocol\n\n IAC WON'T SUPDUP\n\n The sender of this command REFUSES to use the SUPDUP protocol.\n\n IAC DO SUPDUP\n\n The sender of this command REQUESTS that the receiver use, or\n grants the receiver permission to use, the SUPDUP protocol.\n\n IAC DON'T\n\n The sender of this command DEMANDS that the receiver not use the\n SUPDUP protocol.\n\n3. Default.\n\n WON'T SUPDUP\n\n DON'T SUPDUP\n\n i.e., the SUPDUP display protocol is not in use.\n\nMark Crispin [page 1]\n\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\f\n\nNWG/R","scope_keywords":["736"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 749","folder":"IETF/RFC-749","source":"IETF/RFC-749/RFC-749.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 736 NWG/RFC# 736 MRC 31-OCT-77 23:28 42213\nTelnet SUPDUP Option\n\nNetwork Working Group Mark Crispin\nRequest for Comments 736 SU-AI\nNIC 42213 31 October 1977\n\n TELNET SUPDUP Option\n\n1. Command name and code.\n\n SUPDUP 21\n\n2. Command meanings.\n\n IAC WILL SUPDUP\n\n The sender of this command REQUESTS permission to, or confirms\n that it will, use the SUPDUP display protocol\n\n IAC WON'T SUPDUP\n\n The sender of this command REFUSES to use the SUPDUP protocol.\n\n IAC DO SUPDUP\n\n The sender of this command REQUESTS that the receiver use, or\n grants the receiver permission to use, the SUPDUP protocol.\n\n IAC DON'T\n\n The sender of this command DEMANDS that the receiver not use the\n SUPDUP protocol.\n\n3. Default.\n\n WON'T SUPDUP\n\n DON'T SUPDUP\n\n i.e., the SUPDUP display protocol is not in use.\n\nMark Crispin [page 1]\n\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\f\n\nNWG/R 736 nested-reference unchanged"},{"id":"IETF RFC 746","type":"specification","body":"IETF","designation":"RFC 746","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc746.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc746.txt","https://www.rfc-editor.org/rfc/rfc746.pdf"],"folder":"IETF/RFC-746","files":{"txt":{"path":"standards/IETF/RFC-746/RFC-746.txt","sha256":"de7450b8e91deb9bd5634dc77ac55b0937458f6bd0647113a1bed765530f9282"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 746 RMS 17-MAR-78 43976\nThe SUPDUP Graphics Extension\n\nNetwork Working Group Richard Stallman\nRequest for Comments 746 MIT-AI\nNIC 43976 17 March 1978\n\nThe SUPDUP Graphics Extension\n\n ... extends SUPDUP to permit the display of drawings on the screen of\n the terminal, as well as text. We refer constantly to the\n documentation of the SUPDUP protocol, described by Crispin in RFC 734\n \"SUPDUP Protocol\".\n\n Since this extension has never been implemented, it presumably has\n some problems. It is being published to ask for suggestions, and to\n encourage someone to try to bring it up.\n\nThe major accomplishments are these:\n\n * It is easy to do simple things.\n\n * Any program on the server host can at any time begin outputting\n pictures. No special preparations are needed.\n\n * No additional network connections are needed. Graphics commands\n go through the normal text output connection.\n\n * ","scope_keywords":["746"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 747","folder":"IETF/RFC-747","source":"IETF/RFC-747/RFC-747.txt","version":null}],"search_text":"IETF RFC 746 NWG/RFC# 746 RMS 17-MAR-78 43976\nThe SUPDUP Graphics Extension\n\nNetwork Working Group Richard Stallman\nRequest for Comments 746 MIT-AI\nNIC 43976 17 March 1978\n\nThe SUPDUP Graphics Extension\n\n ... extends SUPDUP to permit the display of drawings on the screen of\n the terminal, as well as text. We refer constantly to the\n documentation of the SUPDUP protocol, described by Crispin in RFC 734\n \"SUPDUP Protocol\".\n\n Since this extension has never been implemented, it presumably has\n some problems. It is being published to ask for suggestions, and to\n encourage someone to try to bring it up.\n\nThe major accomplishments are these:\n\n * It is easy to do simple things.\n\n * Any program on the server host can at any time begin outputting\n pictures. No special preparations are needed.\n\n * No additional network connections are needed. Graphics commands\n go through the normal text output connection.\n\n *  746 nested-reference unchanged"},{"id":"IETF RFC 747","type":"specification","body":"IETF","designation":"RFC 747","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc747.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc747.txt","https://www.rfc-editor.org/rfc/rfc747.pdf"],"folder":"IETF/RFC-747","files":{"txt":{"path":"standards/IETF/RFC-747/RFC-747.txt","sha256":"b57752490da3f1710c8ccf54cb46e60ec73f5a0b32dd157c5f28c3572b1c7eb0"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 747 MRC 21-MAR-78 44015\nRecent Extensions to the SUPDUP Protocol\n\nNetwork Working Group Mark Crispin\nRequest for Comments 747 SU-AI\nNIC 44015 21 March 1978\n\nUpdates: RFC 734. See also RFC 746.\n\n Recent Extensions to the SUPDUP Protocol\n\nRecently, some extensions have been made to the SUPDUP protocol. RFC\n746, by Richard Stallman, documented the SUPDUP graphics extension.\nIn addition, a TTYOPT bit has been added and two more variables have\nbeen added to the initial negotiation. This RFC describes the changes\nfrom RFC 734, but excludes the detailed information in RFC 746.\nThese extensions are upwards and downwards compatable, and are\ncompletely optional. For most SUPDUP user and server programs,\nRFC 734 remains an adequate description of the protocol.\nHowever, it is suggested that if the console's line speed is\nknown, the user SUPDUP should be modified to send the new ISPEED and\nO","scope_keywords":["747"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 749","folder":"IETF/RFC-749","source":"IETF/RFC-749/RFC-749.txt","version":null}],"search_text":"IETF RFC 747 NWG/RFC# 747 MRC 21-MAR-78 44015\nRecent Extensions to the SUPDUP Protocol\n\nNetwork Working Group Mark Crispin\nRequest for Comments 747 SU-AI\nNIC 44015 21 March 1978\n\nUpdates: RFC 734. See also RFC 746.\n\n Recent Extensions to the SUPDUP Protocol\n\nRecently, some extensions have been made to the SUPDUP protocol. RFC\n746, by Richard Stallman, documented the SUPDUP graphics extension.\nIn addition, a TTYOPT bit has been added and two more variables have\nbeen added to the initial negotiation. This RFC describes the changes\nfrom RFC 734, but excludes the detailed information in RFC 746.\nThese extensions are upwards and downwards compatable, and are\ncompletely optional. For most SUPDUP user and server programs,\nRFC 734 remains an adequate description of the protocol.\nHowever, it is suggested that if the console's line speed is\nknown, the user SUPDUP should be modified to send the new ISPEED and\nO 747 nested-reference unchanged"},{"id":"IETF RFC 749","type":"specification","body":"IETF","designation":"RFC 749","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc749.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc749.txt","https://www.rfc-editor.org/rfc/rfc749.pdf"],"folder":"IETF/RFC-749","files":{"txt":{"path":"standards/IETF/RFC-749/RFC-749.txt","sha256":"d66e1b35455116db3bf3e37e35b1949053d138bb6ff50c74c6dab81b3c407470"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 749 BSG 26-Sep-78 13:13 45499\nNetwork Working Group Bernard Greenberg\nRequest for Comments 749 MIT-Multics\nNIC 45499 18 September 1978\n\n Telnet SUPDUP-OUTPUT Option\n\n1. Command name and code.\n\n SUPDUP-OUTPUT 22\n\n2. Command meanings.\n\n IAC WILL SUPDUP-OUTPUT\n\n The sender of this command REQUESTS permission to transmit\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC WON'T SUPDUP-OUTPUT\n\n The sender of this command STATES that he will no longer send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC DO SUPDUP-OUTPUT\n\n The sender of this command grants the receiver permission to send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC DON'T SUPDUP-OUTPUT\n\n The sender of this command DEMANDS that the receiver not send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC SB SUPDUP-OUTPUT 1 IAC SE\n\n The sender of this command (whic","scope_keywords":["749","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 749 NWG/RFC 749 BSG 26-Sep-78 13:13 45499\nNetwork Working Group Bernard Greenberg\nRequest for Comments 749 MIT-Multics\nNIC 45499 18 September 1978\n\n Telnet SUPDUP-OUTPUT Option\n\n1. Command name and code.\n\n SUPDUP-OUTPUT 22\n\n2. Command meanings.\n\n IAC WILL SUPDUP-OUTPUT\n\n The sender of this command REQUESTS permission to transmit\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC WON'T SUPDUP-OUTPUT\n\n The sender of this command STATES that he will no longer send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC DO SUPDUP-OUTPUT\n\n The sender of this command grants the receiver permission to send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC DON'T SUPDUP-OUTPUT\n\n The sender of this command DEMANDS that the receiver not send\n SUPDUP-OUTPUT format messages over the TELNET connection.\n\n IAC SB SUPDUP-OUTPUT 1 IAC SE\n\n The sender of this command (whic 749 management nested-reference unchanged"},{"id":"IETF RFC 779","type":"specification","body":"IETF","designation":"RFC 779","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc779.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc779.txt","https://www.rfc-editor.org/rfc/rfc779.pdf"],"folder":"IETF/RFC-779","files":{"txt":{"path":"standards/IETF/RFC-779/RFC-779.txt","sha256":"9b5feee4f1db47580257f8400b3ca59fe7ac752c49786be3dea9ba9841bf4d17"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group E. Killian\nRequest for Comments: 779 LLL\n April 1981\n\n TELNET SEND-LOCATION Option\n\n1. Command name and code.\n\n SEND-LOCATION 23\n\n2. Command meanings.\n\n IAC WILL SEND-LOCATION\n\n The sender REQUESTS or AGREES to use the SEND-LOCATION option to\n send the user's location.\n\n IAC WON'T SEND-LOCATION\n\n The sender REFUSES to use the SEND-LOCATION option.\n\n IAC DO SEND-LOCATION\n\n The sender REQUESTS that, or AGREES to have, the other side use\n SEND-LOCATION commands send the user's location.\n\n IAC DON'T SEND-LOCATION\n\n The sender DEMANDS the other side not use the SEND-LOCATION\n option.\n\n IAC SB SEND-LOCATION IAC SE\n\n The sender specifies the user's location to the other side via a\n SEND-LOCATION subnegotiation. is a sequence of ASCII\n printable characters; it is terminated by the IAC SE.\n\n3. Default.\n\n WON'T SEND-LOCATION\n\n DON'T SEND-LOCATION\n\nKillian [page 1]\n\f\n\nRFC 779 ","scope_keywords":["779"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 779 Network Working Group E. Killian\nRequest for Comments: 779 LLL\n April 1981\n\n TELNET SEND-LOCATION Option\n\n1. Command name and code.\n\n SEND-LOCATION 23\n\n2. Command meanings.\n\n IAC WILL SEND-LOCATION\n\n The sender REQUESTS or AGREES to use the SEND-LOCATION option to\n send the user's location.\n\n IAC WON'T SEND-LOCATION\n\n The sender REFUSES to use the SEND-LOCATION option.\n\n IAC DO SEND-LOCATION\n\n The sender REQUESTS that, or AGREES to have, the other side use\n SEND-LOCATION commands send the user's location.\n\n IAC DON'T SEND-LOCATION\n\n The sender DEMANDS the other side not use the SEND-LOCATION\n option.\n\n IAC SB SEND-LOCATION IAC SE\n\n The sender specifies the user's location to the other side via a\n SEND-LOCATION subnegotiation. is a sequence of ASCII\n printable characters; it is terminated by the IAC SE.\n\n3. Default.\n\n WON'T SEND-LOCATION\n\n DON'T SEND-LOCATION\n\nKillian [page 1]\n\f\n\nRFC 779  779 nested-reference unchanged"},{"id":"IETF RFC 735","type":"specification","body":"IETF","designation":"RFC 735","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc735.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc735.txt","https://www.rfc-editor.org/rfc/rfc735.pdf"],"folder":"IETF/RFC-735","files":{"txt":{"path":"standards/IETF/RFC-735/RFC-735.txt","sha256":"371b2b098d392975bf97237e6021586b4b0136b9c063da7167d41e8a1d578b90"}},"tags":["nested-reference","unchanged"],"summary":"RFC 735 DHC RHG 3 Nov 77 42083\nTelnet Byte Macro Option\n\nNetwork Working Group David H. Crocker\nRFC: #735 Rand-ISD\nNIC: #42083 (Dcrocker at Rand-Unix)\n Richard H. Gumpertz\n Carnegie-Mellon University\n (Gumpertz at CMU-10A)\n\nObsoletes: RFC #729 (NIC #40306) 3 November 1977\n\n Revised TELNET Byte Macro Option\n\n1. Command name and code:\n\n BM 19\n\n2. Command Meanings:\n\n IAC WILL BM\n\n The sender of this command REQUESTS or AGREES to use the BM\n option, and will send single data characters which are to be\n interpreted as if replacement data strings had been sent.\n\n IAC WON'T BM\n\n The sender of this option REFUSES to send single data characters\n which are to be interpreted as if replacement data strings had\n been sent. Any existing BM definitions are discarded\n (i.e., reset to their original data interpretations).\n\n IAC DO BM\n\n The sender REQUESTS or AGREES to have the other side (sender of\n WILL","scope_keywords":["735"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 735 RFC 735 DHC RHG 3 Nov 77 42083\nTelnet Byte Macro Option\n\nNetwork Working Group David H. Crocker\nRFC: #735 Rand-ISD\nNIC: #42083 (Dcrocker at Rand-Unix)\n Richard H. Gumpertz\n Carnegie-Mellon University\n (Gumpertz at CMU-10A)\n\nObsoletes: RFC #729 (NIC #40306) 3 November 1977\n\n Revised TELNET Byte Macro Option\n\n1. Command name and code:\n\n BM 19\n\n2. Command Meanings:\n\n IAC WILL BM\n\n The sender of this command REQUESTS or AGREES to use the BM\n option, and will send single data characters which are to be\n interpreted as if replacement data strings had been sent.\n\n IAC WON'T BM\n\n The sender of this option REFUSES to send single data characters\n which are to be interpreted as if replacement data strings had\n been sent. Any existing BM definitions are discarded\n (i.e., reset to their original data interpretations).\n\n IAC DO BM\n\n The sender REQUESTS or AGREES to have the other side (sender of\n WILL 735 nested-reference unchanged"},{"id":"IETF RFC 737","type":"specification","body":"IETF","designation":"RFC 737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc737.txt","https://www.rfc-editor.org/rfc/rfc737.pdf"],"folder":"IETF/RFC-737","files":{"txt":{"path":"standards/IETF/RFC-737/RFC-737.txt","sha256":"d56fbd54abaea15c9afab46ebda01e64c3ef1687e814a24faeef4d8d919e4445"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 737 KLH 31 Oct 77 42217\nNetwork Working Group K. Harrenstien\nRequest for Comments: 737 SRI-KL\nNIC: 42217 31 October 1977\n\n FTP Extension: XSEN\n\nThis note describes an extension to the File Transfer Protocol which\nprovides for \"sending\" a message to a logged-in user, as well as\nvariants for mailing it normally whether the user is logged in or not.\n\nSeveral systems have a SEND command or program which sends a message\ndirectly to a user's terminal. On the SAIL (SU-AI) and ITS\n(MIT-(AI/ML/MC/DMS)) systems the concept has been broadened to allow\nSEND'ing to users on other network sites; to support this, three new FTP\ncommands were added which have a syntax identical to the existing MAIL\ncommand. For reference, the latter is:\n\n MAIL \n\n If accepted, returns 350 reply and considers all succeeding lines\n to be the message text, terminated by a line containing only a\n period, upon which a","scope_keywords":["737","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 737 NWG/RFC# 737 KLH 31 Oct 77 42217\nNetwork Working Group K. Harrenstien\nRequest for Comments: 737 SRI-KL\nNIC: 42217 31 October 1977\n\n FTP Extension: XSEN\n\nThis note describes an extension to the File Transfer Protocol which\nprovides for \"sending\" a message to a logged-in user, as well as\nvariants for mailing it normally whether the user is logged in or not.\n\nSeveral systems have a SEND command or program which sends a message\ndirectly to a user's terminal. On the SAIL (SU-AI) and ITS\n(MIT-(AI/ML/MC/DMS)) systems the concept has been broadened to allow\nSEND'ing to users on other network sites; to support this, three new FTP\ncommands were added which have a syntax identical to the existing MAIL\ncommand. For reference, the latter is:\n\n MAIL \n\n If accepted, returns 350 reply and considers all succeeding lines\n to be the message text, terminated by a line containing only a\n period, upon which a 737 crl nested-reference unchanged"},{"id":"IETF RFC 738","type":"specification","body":"IETF","designation":"RFC 738","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc738.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc738.txt","https://www.rfc-editor.org/rfc/rfc738.pdf"],"folder":"IETF/RFC-738","files":{"txt":{"path":"standards/IETF/RFC-738/RFC-738.txt","sha256":"707e0bd9cd57ba6f99d83454b975e21dcf5eed221ad4e29d2074fe9a9104ed7f"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 738 KLH 31 Oct 77 42218\nNetwork Working Group K. Harrenstien\nRequest for Comments: 738 SRI-KL\nNIC: 42218 31 October 1977\n\n Time Server\n\nThis note describes the Time Server protocol, as currently implemented\non ITS hosts (i.e. MIT-(AI/ML/MC/DMS)). The idea is to provide a\nsite-independent, machine readable date and time in as efficient and\nswift a manner as possible; its motivation arises from the fact that not\nall systems have a date/time clock, and all are subject to occasional\nhuman or machine error. The use of time-servers makes it possible to\nquickly confirm or correct a system's idea of the time, by making a\nbrief poll of several independent sites on the network.\n\nIn particular the network time server works as follows:\n\n S: Listen on socket 37 (45 octal).\n\n U: Connect to socket 37 [not ICP].\n\n S: Send the time as a 32 bit binary number.\n\n U: Close the connection.\n\n S: Close","scope_keywords":["738","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0739","folder":"IETF/RFC-0739","source":"IETF/RFC-0739/RFC-0739.txt","version":null},{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 739","folder":"IETF/RFC-739","source":"IETF/RFC-739/RFC-739.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null}],"search_text":"IETF RFC 738 NWG/RFC# 738 KLH 31 Oct 77 42218\nNetwork Working Group K. Harrenstien\nRequest for Comments: 738 SRI-KL\nNIC: 42218 31 October 1977\n\n Time Server\n\nThis note describes the Time Server protocol, as currently implemented\non ITS hosts (i.e. MIT-(AI/ML/MC/DMS)). The idea is to provide a\nsite-independent, machine readable date and time in as efficient and\nswift a manner as possible; its motivation arises from the fact that not\nall systems have a date/time clock, and all are subject to occasional\nhuman or machine error. The use of time-servers makes it possible to\nquickly confirm or correct a system's idea of the time, by making a\nbrief poll of several independent sites on the network.\n\nIn particular the network time server works as follows:\n\n S: Listen on socket 37 (45 octal).\n\n U: Connect to socket 37 [not ICP].\n\n S: Send the time as a 32 bit binary number.\n\n U: Close the connection.\n\n S: Close 738 subject nested-reference unchanged"},{"id":"IETF RFC 740","type":"specification","body":"IETF","designation":"RFC 740","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc740.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc740.txt","https://www.rfc-editor.org/rfc/rfc740.pdf"],"folder":"IETF/RFC-740","files":{"txt":{"path":"standards/IETF/RFC-740/RFC-740.txt","sha256":"8223090f15b92e749306777dd8b60b73e71556cb0e737de75b337e0194e497fc"}},"tags":["nested-reference","unchanged"],"summary":"RFC 740 RTB 42423 22 Nov 77\nNETRJS Protocol\n\nNetwork Working Group R. Braden\nRequest for Comments: 740 UCLA-CCN\nNIC: 42423 22 November 1977\nObsoletes: 189, 599\n\n NETRJS PROTOCOL\n\nA. Introduction\n\n NETRJS, a private protocol for remote job entry service, was defined\n and implemented by the UCLA Campus Computing Network (CCN) for batch\n job submission to an IBM 360 Model 91. CCN's NETRJS server allows a\n remote user, or a daemon process working in behalf of a user, to\n access CCN's RJS (\"Remote Job Service\") subsystem. RJS provides\n remote job entry service to real remote batch (card reader/line\n printer) terminals over direct communications lines as well as to the\n ARPANET.\n\n A batch user at a remote host needs a NETRJS user process to\n communicate with the NETRJS server at the batch host. An active\n NETRJS user process simulates a \"Virtual Remote Batch Terminal\", or\n \"VRBT\".\n\n A VRBT may","scope_keywords":["740"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 765","folder":"IETF/RFC-765","source":"IETF/RFC-765/RFC-765.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 740 RFC 740 RTB 42423 22 Nov 77\nNETRJS Protocol\n\nNetwork Working Group R. Braden\nRequest for Comments: 740 UCLA-CCN\nNIC: 42423 22 November 1977\nObsoletes: 189, 599\n\n NETRJS PROTOCOL\n\nA. Introduction\n\n NETRJS, a private protocol for remote job entry service, was defined\n and implemented by the UCLA Campus Computing Network (CCN) for batch\n job submission to an IBM 360 Model 91. CCN's NETRJS server allows a\n remote user, or a daemon process working in behalf of a user, to\n access CCN's RJS (\"Remote Job Service\") subsystem. RJS provides\n remote job entry service to real remote batch (card reader/line\n printer) terminals over direct communications lines as well as to the\n ARPANET.\n\n A batch user at a remote host needs a NETRJS user process to\n communicate with the NETRJS server at the batch host. An active\n NETRJS user process simulates a \"Virtual Remote Batch Terminal\", or\n \"VRBT\".\n\n A VRBT may 740 nested-reference unchanged"},{"id":"IETF RFC 765","type":"specification","body":"IETF","designation":"RFC 765","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc765.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc765.txt","https://www.rfc-editor.org/rfc/rfc765.pdf"],"folder":"IETF/RFC-765","files":{"txt":{"path":"standards/IETF/RFC-765/RFC-765.txt","sha256":"a12b7f7cc2788579c1f6c200665980405ed0171ca2df7d40debe7a61e4e55020"}},"tags":["nested-reference","unchanged"],"summary":"IEN 149 J. Postel\nRFC 765 ISI\n June 1980\n\n FILE TRANSFER PROTOCOL\n\nINTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among Hosts, and 4) to transfer\n data reliably and efficiently. FTP, though usable directly by a user\n at a terminal, is designed mainly for use by programs.\n\n The attempt in this specification is to satisfy the diverse needs of\n users of maxi-Hosts, mini-Hosts, and TIPs, with a simple, and easily\n implemented protocol design.\n\n This paper assumes knowledge of the following protocols described in\n the ARPA Internet Protocol Handbook.\n\n The Transmission Control Protocol\n\n The TELNET Protocol\n\nDISCUSSION\n\n In this section, the terminology and the FTP model are discussed.\n The terms d","scope_keywords":["765","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 775","folder":"IETF/RFC-775","source":"IETF/RFC-775/RFC-775.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 765 IEN 149 J. Postel\nRFC 765 ISI\n June 1980\n\n FILE TRANSFER PROTOCOL\n\nINTRODUCTION\n\n The objectives of FTP are 1) to promote sharing of files (computer\n programs and/or data), 2) to encourage indirect or implicit (via\n programs) use of remote computers, 3) to shield a user from\n variations in file storage systems among Hosts, and 4) to transfer\n data reliably and efficiently. FTP, though usable directly by a user\n at a terminal, is designed mainly for use by programs.\n\n The attempt in this specification is to satisfy the diverse needs of\n users of maxi-Hosts, mini-Hosts, and TIPs, with a simple, and easily\n implemented protocol design.\n\n This paper assumes knowledge of the following protocols described in\n the ARPA Internet Protocol Handbook.\n\n The Transmission Control Protocol\n\n The TELNET Protocol\n\nDISCUSSION\n\n In this section, the terminology and the FTP model are discussed.\n The terms d 765 path presentation nested-reference unchanged"},{"id":"IETF RFC 741","type":"specification","body":"IETF","designation":"RFC 741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc741.txt","https://www.rfc-editor.org/rfc/rfc741.pdf"],"folder":"IETF/RFC-741","files":{"txt":{"path":"standards/IETF/RFC-741/RFC-741.txt","sha256":"0851f56d498808030e14b24486b2ea4d940f823824036424b5068fe9040d7346"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 741 DC 22 Nov 77 42444\n\n \n \n \n \n \n \n \n \n \n \n SPECIFICATIONS FOR THE\n \n NETWORK VOICE PROTOCOL (NVP)\n \n and\n\n Appendix 1: The Definition of Tables-Set-#1 (for LPC)\n\n Appendix 2: Implementation Recommendations\n\n NSC NOTE 68\n\n (Revision of NSC Notes 26, 40, and 43)\n\n Danny Cohen, ISI\n\n January 29, 1976\f\nNWG/RFC 741 DC 22 Nov 77 42444\nSpecifications for the Network Voice Protocol (NVP)\n\n CONTENTS\n\n PREFACE iii\n\n ACKNOWLEDGMENTS iv\n\n INTRODUCTION 2\n\n THE CONTROL PROTOCOL 2\n Summary of the CONTROL Messages 3\n Definition of the CONTROL Messages 4\n Definition of the and \n Negotiation Tables 8\n On RENEGOTIATION 10\n The Header of Data Messages 10\n\n THE LPC DATA PROTOCOL 13\n\n EXAMPLES FOR THE CONTROL PROTOCOL 15\n\n APPENDIX 1: THE DEFINITION OF TABLES-SET-#1 18\n General Comments 20\n Comments on the PITCH Table 20\n Comments on the GAIN Table 21\n Comments on the INDEX7 Table 21\n Comments on th","scope_keywords":["741","encryption"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 767","folder":"IETF/RFC-767","source":"IETF/RFC-767/RFC-767.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 741 NWG/RFC 741 DC 22 Nov 77 42444\n\n \n \n \n \n \n \n \n \n \n \n SPECIFICATIONS FOR THE\n \n NETWORK VOICE PROTOCOL (NVP)\n \n and\n\n Appendix 1: The Definition of Tables-Set-#1 (for LPC)\n\n Appendix 2: Implementation Recommendations\n\n NSC NOTE 68\n\n (Revision of NSC Notes 26, 40, and 43)\n\n Danny Cohen, ISI\n\n January 29, 1976\f\nNWG/RFC 741 DC 22 Nov 77 42444\nSpecifications for the Network Voice Protocol (NVP)\n\n CONTENTS\n\n PREFACE iii\n\n ACKNOWLEDGMENTS iv\n\n INTRODUCTION 2\n\n THE CONTROL PROTOCOL 2\n Summary of the CONTROL Messages 3\n Definition of the CONTROL Messages 4\n Definition of the and \n Negotiation Tables 8\n On RENEGOTIATION 10\n The Header of Data Messages 10\n\n THE LPC DATA PROTOCOL 13\n\n EXAMPLES FOR THE CONTROL PROTOCOL 15\n\n APPENDIX 1: THE DEFINITION OF TABLES-SET-#1 18\n General Comments 20\n Comments on the PITCH Table 20\n Comments on the GAIN Table 21\n Comments on the INDEX7 Table 21\n Comments on th 741 encryption nested-reference unchanged"},{"id":"IETF RFC 742","type":"specification","body":"IETF","designation":"RFC 742","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc742.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc742.txt","https://www.rfc-editor.org/rfc/rfc742.pdf"],"folder":"IETF/RFC-742","files":{"txt":{"path":"standards/IETF/RFC-742/RFC-742.txt","sha256":"e242fb7222329d4015b148a30bb4d7eeaf96e0aaa06452cd3169dba9201a016f"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC# 742 KLH 30-Dec-77 08:31 42758\nNetwork Working Group K. Harrenstien\nRequest for Comments: 742 SRI-KL\nNIC: 42758 30 December 1977\n\n NAME/FINGER\n\nIntroduction\n\n This note describes the Name/Finger protocol. This is a simple\n protocol which provides an interface to the Name and Finger programs\n at several network sites. These programs return a friendly,\n human-oriented status report on either the system at the moment or a\n particular person in depth. Currently only the SAIL (SU-AI), SRI\n (SRI-(KA/KL)), and ITS (MIT-(AI/ML/MC/DMS)) sites support this\n protocol, but there are other systems with similar programs that\n could easily be made servers; there is no required format and the\n protocol consists mostly of specifying a single \"command line\".\n\nTo use via the network:\n\n ICP to socket 117 (octal, 79. decimal) and establish two 8-bit\n connections.\n\n Send a single \"command line\", endin","scope_keywords":["742","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0758","folder":"IETF/RFC-0758","source":"IETF/RFC-0758/RFC-0758.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1135","folder":"IETF/RFC-1135","source":"IETF/RFC-1135/RFC-1135.txt","version":null},{"body":"IETF","designation":"RFC 1194","folder":"IETF/RFC-1194","source":"IETF/RFC-1194/RFC-1194.txt","version":null},{"body":"IETF","designation":"RFC 1196","folder":"IETF/RFC-1196","source":"IETF/RFC-1196/RFC-1196.txt","version":null},{"body":"IETF","designation":"RFC 1288","folder":"IETF/RFC-1288","source":"IETF/RFC-1288/RFC-1288.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 750","folder":"IETF/RFC-750","source":"IETF/RFC-750/RFC-750.txt","version":null},{"body":"IETF","designation":"RFC 758","folder":"IETF/RFC-758","source":"IETF/RFC-758/RFC-758.txt","version":null},{"body":"IETF","designation":"RFC 762","folder":"IETF/RFC-762","source":"IETF/RFC-762/RFC-762.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 779","folder":"IETF/RFC-779","source":"IETF/RFC-779/RFC-779.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 812","folder":"IETF/RFC-812","source":"IETF/RFC-812/RFC-812.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 742 NWG/RFC# 742 KLH 30-Dec-77 08:31 42758\nNetwork Working Group K. Harrenstien\nRequest for Comments: 742 SRI-KL\nNIC: 42758 30 December 1977\n\n NAME/FINGER\n\nIntroduction\n\n This note describes the Name/Finger protocol. This is a simple\n protocol which provides an interface to the Name and Finger programs\n at several network sites. These programs return a friendly,\n human-oriented status report on either the system at the moment or a\n particular person in depth. Currently only the SAIL (SU-AI), SRI\n (SRI-(KA/KL)), and ITS (MIT-(AI/ML/MC/DMS)) sites support this\n protocol, but there are other systems with similar programs that\n could easily be made servers; there is no required format and the\n protocol consists mostly of specifying a single \"command line\".\n\nTo use via the network:\n\n ICP to socket 117 (octal, 79. decimal) and establish two 8-bit\n connections.\n\n Send a single \"command line\", endin 742 crl nested-reference unchanged"},{"id":"IETF RFC 812","type":"specification","body":"IETF","designation":"RFC 812","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc812.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc812.txt","https://www.rfc-editor.org/rfc/rfc812.pdf"],"folder":"IETF/RFC-812","files":{"txt":{"path":"standards/IETF/RFC-812/RFC-812.txt","sha256":"416722bfa8e453acd29d415150dac056e5a1072a0eb66babda40c8445b3a70d5"}},"tags":["nested-reference","unchanged"],"summary":"Ken Harrenstien RFC-812\nVic White 1 March 1982\nNetwork Information Center\nSRI International\n NICNAME/WHOIS\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is an NCP/TCP transaction based\n query/response server, running on the SRI-NIC machine, that\n provides netwide directory service to ARPANET users. It is\n one of a series of ARPANET/Internet name services maintained\n by the Network Information Center (NIC) at SRI International\n on behalf of the Defense Communications Agency (DCA). The\n server is accessible across the ARPANET from user programs\n running on local hosts, and it delivers the full name, U.S.\n mailing address, telephone number, and network mailbox for\n ARPANET users.\n\n This server, together with the corresponding Identification\n Data Base provides online directory look-up equivalent to the\n ARPANET Directory. DCA strongly encourages network hosts to\n provide their users with access ","scope_keywords":["812","crl","identification","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0954","folder":"IETF/RFC-0954","source":"IETF/RFC-0954/RFC-0954.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1712","folder":"IETF/RFC-1712","source":"IETF/RFC-1712/RFC-1712.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 954","folder":"IETF/RFC-954","source":"IETF/RFC-954/RFC-954.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 812 Ken Harrenstien RFC-812\nVic White 1 March 1982\nNetwork Information Center\nSRI International\n NICNAME/WHOIS\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is an NCP/TCP transaction based\n query/response server, running on the SRI-NIC machine, that\n provides netwide directory service to ARPANET users. It is\n one of a series of ARPANET/Internet name services maintained\n by the Network Information Center (NIC) at SRI International\n on behalf of the Defense Communications Agency (DCA). The\n server is accessible across the ARPANET from user programs\n running on local hosts, and it delivers the full name, U.S.\n mailing address, telephone number, and network mailbox for\n ARPANET users.\n\n This server, together with the corresponding Identification\n Data Base provides online directory look-up equivalent to the\n ARPANET Directory. DCA strongly encourages network hosts to\n provide their users with access  812 crl identification registered risk nested-reference unchanged"},{"id":"IETF RFC 882","type":"specification","body":"IETF","designation":"RFC 882","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc882.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc882.txt","https://www.rfc-editor.org/rfc/rfc882.pdf"],"folder":"IETF/RFC-882","files":{"txt":{"path":"standards/IETF/RFC-882/RFC-882.txt","sha256":"70320c14a770d259bc0b218932b6c9a5aca3f209f8535c597724ed2fb270ac7a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 882 ISI\n November 1983\n\n DOMAIN NAMES - CONCEPTS and FACILITIES\n\n +-----------------------------------------------------+\n | |\n | This RFC introduces domain style names, their use |\n | for ARPA Internet mail and host address support, |\n | and the protocols and servers used to implement |\n | domain name facilities. |\n | |\n | This memo describes the conceptual framework of the |\n | domain system and some uses, but it omits many |\n | uses, fields, and implementation details. A |\n | complete specification of formats, timeouts, etc. |\n | is presented in RFC 883, \"Domain Names - |\n | Implementation and Specification\". That RFC |\n | assumes that the reader is familiar with the |\n | concepts discussed in this memo. |\n | |\n +-----------------------------------------------------+\n\nINTRODUCTION\n\n The need for domain names\n\n As applications ","scope_keywords":["882","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 882 Network Working Group P. Mockapetris\nRequest for Comments: 882 ISI\n November 1983\n\n DOMAIN NAMES - CONCEPTS and FACILITIES\n\n +-----------------------------------------------------+\n | |\n | This RFC introduces domain style names, their use |\n | for ARPA Internet mail and host address support, |\n | and the protocols and servers used to implement |\n | domain name facilities. |\n | |\n | This memo describes the conceptual framework of the |\n | domain system and some uses, but it omits many |\n | uses, fields, and implementation details. A |\n | complete specification of formats, timeouts, etc. |\n | is presented in RFC 883, \"Domain Names - |\n | Implementation and Specification\". That RFC |\n | assumes that the reader is familiar with the |\n | concepts discussed in this memo. |\n | |\n +-----------------------------------------------------+\n\nINTRODUCTION\n\n The need for domain names\n\n As applications  882 registered nested-reference unchanged"},{"id":"IETF RFC 883","type":"specification","body":"IETF","designation":"RFC 883","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc883.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc883.txt","https://www.rfc-editor.org/rfc/rfc883.pdf"],"folder":"IETF/RFC-883","files":{"txt":{"path":"standards/IETF/RFC-883/RFC-883.txt","sha256":"9a69f193b479bf7ccc45a2953e625c057f2bbdb926bf44aab35cff4f2642db77"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group P. Mockapetris\nRequest for Comments: 883 ISI\n November 1983\n\n DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION\n\n +-----------------------------------------------------+\n | |\n | This memo discusses the implementation of domain |\n | name servers and resolvers, specifies the format of |\n | transactions, and discusses the use of domain names |\n | in the context of existing mail systems and other |\n | network software. |\n | |\n | This memo assumes that the reader is familiar with |\n | RFC 882, \"Domain Names - Concepts and Facilities\" |\n | which discusses the basic principles of domain |\n | names and their use. |\n | |\n | The algorithms and internal data structures used in |\n | this memo are offered as suggestions rather than |\n | requirements; implementers are free to design their |\n | own structures so long as the same external |\n | behavior is achieved. |\n | |\n +---------","scope_keywords":["883","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1002","folder":"IETF/RFC-1002","source":"IETF/RFC-1002/RFC-1002.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 883 Network Working Group P. Mockapetris\nRequest for Comments: 883 ISI\n November 1983\n\n DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION\n\n +-----------------------------------------------------+\n | |\n | This memo discusses the implementation of domain |\n | name servers and resolvers, specifies the format of |\n | transactions, and discusses the use of domain names |\n | in the context of existing mail systems and other |\n | network software. |\n | |\n | This memo assumes that the reader is familiar with |\n | RFC 882, \"Domain Names - Concepts and Facilities\" |\n | which discusses the basic principles of domain |\n | names and their use. |\n | |\n | The algorithms and internal data structures used in |\n | this memo are offered as suggestions rather than |\n | requirements; implementers are free to design their |\n | own structures so long as the same external |\n | behavior is achieved. |\n | |\n +--------- 883 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 7478","type":"specification","body":"IETF","designation":"RFC 7478","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7478.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7478.txt","https://www.rfc-editor.org/rfc/rfc7478.pdf"],"folder":"IETF/RFC-7478","files":{"txt":{"path":"standards/IETF/RFC-7478/RFC-7478.txt","sha256":"e7112aeabdd151115cae6028c5f5d1812b8ef2d98798efcd97a152db145f7cce"}},"tags":["nested-reference","unchanged"],"summary":"This document describes web-based real-time communication use cases.\n Requirements on the browser functionality are derived from the use\n cases.\n\n This document was developed in an initial phase of the work with\n rather minor updates at later stages. It has not really served as a\n tool in deciding features or scope for the WG's efforts so far. It\n is being published to record the early conclusions of the WG. It\n will not be used as a set of rigid guidelines that specifications and\n implementations will be held to in the future.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering","scope_keywords":["7478","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 7478 This document describes web-based real-time communication use cases.\n Requirements on the browser functionality are derived from the use\n cases.\n\n This document was developed in an initial phase of the work with\n rather minor updates at later stages. It has not really served as a\n tool in deciding features or scope for the WG's efforts so far. It\n is being published to record the early conclusions of the WG. It\n will not be used as a set of rigid guidelines that specifications and\n implementations will be held to in the future.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering 7478 http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 751","type":"specification","body":"IETF","designation":"RFC 751","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc751.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc751.txt","https://www.rfc-editor.org/rfc/rfc751.pdf"],"folder":"IETF/RFC-751","files":{"txt":{"path":"standards/IETF/RFC-751/RFC-751.txt","sha256":"c049bc4481b155b5d66ed9a2831d15460645804f408b8ae4373ba0317a806b76"}},"tags":["nested-reference","unchanged"],"summary":"NWG/RFC 751 PDL 10 Dec 78 nnnnn\n\nNetwork Working Group P. David Lebling\nRequest for Comments: 751 (PDL@MIT-DMS)\nNIC: nnnnn 10 December 1978\n\n SURVEY OF FTP MAIL AND MLFL\n\nTwo surveys of Arpanet Server hosts were run between September 20, 1978\nand December 11, 1978. The intent was to determine the response of the\nhost's Server FTP program to:\n\n(a) An attempt to mail to an unknown recipient at that host. The\npurpose of this survey was two-fold. First, to determine whether the\nhost accepts mail for unknown recipients at all, and second, what\nresponse the host gives if it does not accept such mail.\n\n(b) An attempt to mail to a known recipient using the MLFL command\nrather than the usual MAIL command. This survey was undertaken to\ndetermine the extent of support for the MLFL command among Server hosts,\nand the sort of reply received if the Server does not support MLFL. MLFL\nis potentially a '","scope_keywords":["751","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null}],"search_text":"IETF RFC 751 NWG/RFC 751 PDL 10 Dec 78 nnnnn\n\nNetwork Working Group P. David Lebling\nRequest for Comments: 751 (PDL@MIT-DMS)\nNIC: nnnnn 10 December 1978\n\n SURVEY OF FTP MAIL AND MLFL\n\nTwo surveys of Arpanet Server hosts were run between September 20, 1978\nand December 11, 1978. The intent was to determine the response of the\nhost's Server FTP program to:\n\n(a) An attempt to mail to an unknown recipient at that host. The\npurpose of this survey was two-fold. First, to determine whether the\nhost accepts mail for unknown recipients at all, and second, what\nresponse the host gives if it does not accept such mail.\n\n(b) An attempt to mail to a known recipient using the MLFL command\nrather than the usual MAIL command. This survey was undertaken to\ndetermine the extent of support for the MLFL command among Server hosts,\nand the sort of reply received if the Server does not support MLFL. MLFL\nis potentially a ' 751 algorithm nested-reference unchanged"},{"id":"legal:2026-248","type":"legal_regulation","act_id":"2026-248","title":"Formats of advanced electronic signatures and seals","celex":"32026R0248","eli":"https://data.europa.eu/eli/reg_impl/2026/248/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/c539cc01-00a1-11f1-825d-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2026-248/2026-248.html","sha256":"f4513524bc2bdedd1556379b64cad8821138e8f98416d7dc810076fd91ba35d3","size":68040},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/c539cc01-00a1-11f1-825d-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2026-248/2026-248.pdf","sha256":"d5794d9ad1717d8140dcd82cf8a416b2b2ad89c5dc99e794212e061f825775ea","size":545023}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the formats of advanced electronic signatures and advanced electronic seals to be recognised by public sector bodies and repealing Commission Implementing Decision (EU) 2015/1506 Member States need to put in place the necessary technical means allowing them to process electronically signed or sealed documents that are required when using an online service offered by, or on behalf of, a public sector body. Pursuant to Article 27 and Article 37 of Regulation (EU) No 910/2014, Member States that require an advanced electronic signature or an advanced electronic seal for the use of an online service offered by, or on behalf of, a public sector body, are to recognise advanced electronic signatures and advanced electronic seals, advanced electronic signatures and…","scope_keywords":["advanced","article","behalf","certificate","commission","electronic","european","formats","implementing","member","offered","online","public","qualified","regulation","seal","seals","sector","service","signature","signatures","states","technical","validation"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.554250+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2026-248 Formats of advanced electronic signatures and seals 32026R0248 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the formats of advanced electronic signatures and advanced electronic seals to be recognised by public sector bodies and repealing Commission Implementing Decision (EU) 2015/1506 Member States need to put in place the necessary technical means allowing them to process electronically signed or sealed documents that are required when using an online service offered by, or on behalf of, a public sector body. Pursuant to Article 27 and Article 37 of Regulation (EU) No 910/2014, Member States that require an advanced electronic signature or an advanced electronic seal for the use of an online service offered by, or on behalf of, a public sector body, are to recognise advanced electronic signatures and advanced electronic seals, advanced electronic signatures and… advanced article behalf certificate commission electronic european formats implementing member offered online public qualified regulation seal seals sector service signature signatures states technical validation"},{"id":"legal:2025-848","type":"legal_regulation","act_id":"2025-848","title":"Registration of wallet-relying parties","celex":"32025R0848","eli":"https://data.europa.eu/eli/reg_impl/2025/848/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/a6ba31dd-2adb-11f0-8a44-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-848/2025-848.html","sha256":"ad3e50c59821596b3e829d6fdf08125d1da8255c9d0613648b79e0013a88226e","size":157516},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/a6ba31dd-2adb-11f0-8a44-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-848/2025-848.pdf","sha256":"07ce6b4187a8e051f86992c01e113f41de7d6d0503ebae50279906606b4db1a3","size":634312}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties For the purposes of registering relying parties that intend to rely on European Digital Identity Wallets (‘wallets’) for the provision of digital public or private services, as required by Regulation (EU) No 910/2014, Member States should establish and maintain national registers of wallet-relying parties established in their territory. ‘wallet-relying party’ means a relying party that intends to rely upon wallet units for the provision of public or private services by means of digital interaction;","scope_keywords":["certificate","certificates","council","digital","european","identification","member","national","parliament","parties","party","policies","purpose","registered","registers","registration","regulation","rely","states","their","trust","wallet","wallet-relying","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.525069+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-848 Registration of wallet-relying parties 32025R0848 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties For the purposes of registering relying parties that intend to rely on European Digital Identity Wallets (‘wallets’) for the provision of digital public or private services, as required by Regulation (EU) No 910/2014, Member States should establish and maintain national registers of wallet-relying parties established in their territory. ‘wallet-relying party’ means a relying party that intends to rely upon wallet units for the provision of public or private services by means of digital interaction; certificate certificates council digital european identification member national parliament parties party policies purpose registered registers registration regulation rely states their trust wallet wallet-relying wallets"},{"id":"IETF RFC 754","type":"specification","body":"IETF","designation":"RFC 754","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc754.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc754.txt","https://www.rfc-editor.org/rfc/rfc754.pdf"],"folder":"IETF/RFC-754","files":{"txt":{"path":"standards/IETF/RFC-754/RFC-754.txt","sha256":"cd85e33215dd5899acc2ae9042d96e674a213bfa08fb5669dce7a8907dfc78cf"}},"tags":["nested-reference","unchanged"],"summary":"RFC 754 J. Postel\n ISI\n 6 April 1979\n\n Out-of-Net Host Addresses for Mail\n\nThere is now interest in sustantially extending the scope of the\ncomputer mail system used in the ARPANET to allow communication of\nvoice, fax, graphics, as well as text information between users in\ndifferent networks as wells as within the ARPANET.\n\nThe discussion of a transition from the current ARPANET sndmsg\nenvironment and mechanisms to a more general internet environment and\nricher mechanisms must consider techniques for continued activity during\nthe transition. In addition, there is a current need for a mechanism to\nsupport the interaction of the several already existing NSW-like message\nenvironments with the ARPANET message environment.\n\nThis memo discusses some possible alternatives for computer mail\naddressing for hosts outside the ARPANET in the short term. This memo\nis hopelessly Tenex oriented in its ","scope_keywords":["754","key","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 759","folder":"IETF/RFC-759","source":"IETF/RFC-759/RFC-759.txt","version":null}],"search_text":"IETF RFC 754 RFC 754 J. Postel\n ISI\n 6 April 1979\n\n Out-of-Net Host Addresses for Mail\n\nThere is now interest in sustantially extending the scope of the\ncomputer mail system used in the ARPANET to allow communication of\nvoice, fax, graphics, as well as text information between users in\ndifferent networks as wells as within the ARPANET.\n\nThe discussion of a transition from the current ARPANET sndmsg\nenvironment and mechanisms to a more general internet environment and\nricher mechanisms must consider techniques for continued activity during\nthe transition. In addition, there is a current need for a mechanism to\nsupport the interaction of the several already existing NSW-like message\nenvironments with the ARPANET message environment.\n\nThis memo discusses some possible alternatives for computer mail\naddressing for hosts outside the ARPANET in the short term. This memo\nis hopelessly Tenex oriented in its  754 key presentation nested-reference unchanged"},{"id":"IETF RFC 7565","type":"specification","body":"IETF","designation":"RFC 7565","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7565.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7565.txt","https://www.rfc-editor.org/rfc/rfc7565.pdf"],"folder":"IETF/RFC-7565","files":{"txt":{"path":"standards/IETF/RFC-7565/RFC-7565.txt","sha256":"7484f2c4dbcf7aa09c6f18e2095ae83fbe4d119928a5622828c54890e51e726d"}},"tags":["nested-reference","unchanged"],"summary":"This document defines the 'acct' Uniform Resource Identifier (URI)\n scheme as a way to identify a user's account at a service provider,\n irrespective of the particular protocols that can be used to interact\n with the account.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7565.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rig","scope_keywords":["7565","attribute","http","identification","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7566","folder":"IETF/RFC-7566","source":"IETF/RFC-7566/RFC-7566.txt","version":null}],"search_text":"IETF RFC 7565 This document defines the 'acct' Uniform Resource Identifier (URI)\n scheme as a way to identify a user's account at a service provider,\n irrespective of the particular protocols that can be used to interact\n with the account.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7565.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rig 7565 attribute http identification key license subject trust nested-reference unchanged"},{"id":"IETF RFC 760","type":"specification","body":"IETF","designation":"RFC 760","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc760.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc760.txt","https://www.rfc-editor.org/rfc/rfc760.pdf"],"folder":"IETF/RFC-760","files":{"txt":{"path":"standards/IETF/RFC-760/RFC-760.txt","sha256":"bacc2bdc52f68e06280788e9e6e7138dc7eb54079eec814a006911e555355c10"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 760\nIEN: 128\n \n \n \n \n \n \n \n DOD STANDARD\n \n INTERNET PROTOCOL\n \n \n \n January 1980\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\nJanuary 1980 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW .....................................","scope_keywords":["760","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0768","folder":"IETF/RFC-0768","source":"IETF/RFC-0768/RFC-0768.txt","version":null},{"body":"IETF","designation":"RFC 0791","folder":"IETF/RFC-0791","source":"IETF/RFC-0791/RFC-0791.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 761","folder":"IETF/RFC-761","source":"IETF/RFC-761/RFC-761.txt","version":null},{"body":"IETF","designation":"RFC 768","folder":"IETF/RFC-768","source":"IETF/RFC-768/RFC-768.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 777","folder":"IETF/RFC-777","source":"IETF/RFC-777/RFC-777.txt","version":null},{"body":"IETF","designation":"RFC 791","folder":"IETF/RFC-791","source":"IETF/RFC-791/RFC-791.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 760 RFC: 760\nIEN: 128\n \n \n \n \n \n \n \n DOD STANDARD\n \n INTERNET PROTOCOL\n \n \n \n January 1980\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\nJanuary 1980 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW ..................................... 760 key path nested-reference unchanged"},{"id":"IETF RFC 761","type":"specification","body":"IETF","designation":"RFC 761","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc761.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc761.txt","https://www.rfc-editor.org/rfc/rfc761.pdf"],"folder":"IETF/RFC-761","files":{"txt":{"path":"standards/IETF/RFC-761/RFC-761.txt","sha256":"18686117e1110d0fd4282e54dd9f913bbc5f475e65689e52c8b424560da03cd9"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 761\nIEN: 129\n \n \n \n \n \n \n \n DOD STANDARD\n \n TRANSMISSION CONTROL PROTOCOL\n \n \n \n January 1980\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\nJanuary 1980 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces .................................................... 3\n 1.5 Operation ...........","scope_keywords":["761","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0768","folder":"IETF/RFC-0768","source":"IETF/RFC-0768/RFC-0768.txt","version":null},{"body":"IETF","designation":"RFC 0793","folder":"IETF/RFC-0793","source":"IETF/RFC-0793/RFC-0793.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 768","folder":"IETF/RFC-768","source":"IETF/RFC-768/RFC-768.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 780","folder":"IETF/RFC-780","source":"IETF/RFC-780/RFC-780.txt","version":null},{"body":"IETF","designation":"RFC 793","folder":"IETF/RFC-793","source":"IETF/RFC-793/RFC-793.txt","version":null}],"search_text":"IETF RFC 761 RFC: 761\nIEN: 129\n \n \n \n \n \n \n \n DOD STANDARD\n \n TRANSMISSION CONTROL PROTOCOL\n \n \n \n January 1980\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\nJanuary 1980 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces .................................................... 3\n 1.5 Operation ........... 761 delivery nested-reference unchanged"},{"id":"IETF RFC 768","type":"specification","body":"IETF","designation":"RFC 768","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc768.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc768.txt","https://www.rfc-editor.org/rfc/rfc768.pdf"],"folder":"IETF/RFC-768","files":{"txt":{"path":"standards/IETF/RFC-768/RFC-768.txt","sha256":"7dc8880e1ecef9c3f9da0db4b876a16e96bfa4f0953cc9d977d414f8f680c2f0"}},"tags":["nested-reference","unchanged"],"summary":"RFC 768 J. Postel\n ISI\n 28 August 1980\n\n User Datagram Protocol\n ----------------------\n\nIntroduction\n------------\n\nThis User Datagram Protocol (UDP) is defined to make available a\ndatagram mode of packet-switched computer communication in the\nenvironment of an interconnected set of computer networks. This\nprotocol assumes that the Internet Protocol (IP) [1] is used as the\nunderlying protocol.\n\nThis protocol provides a procedure for application programs to send\nmessages to other programs with a minimum of protocol mechanism. The\nprotocol is transaction oriented, and delivery and duplicate protection\nare not guaranteed. Applications requiring ordered reliable delivery of\nstreams of data should use the Transmission Control Protocol (TCP) [2].\n\nFormat\n------\n\n \n 0 7 8 15 16 23 24 31 \n +--------+--------+--------+--------+ \n | Source | Destination | \n | Port | Port | \n +--------+--------+---","scope_keywords":["768","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0768","folder":"IETF/RFC-0768","source":"IETF/RFC-0768/RFC-0768.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1067","folder":"IETF/RFC-1067","source":"IETF/RFC-1067/RFC-1067.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1098","folder":"IETF/RFC-1098","source":"IETF/RFC-1098/RFC-1098.txt","version":null},{"body":"IETF","designation":"RFC 1157","folder":"IETF/RFC-1157","source":"IETF/RFC-1157/RFC-1157.txt","version":null},{"body":"IETF","designation":"RFC 1161","folder":"IETF/RFC-1161","source":"IETF/RFC-1161/RFC-1161.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1234","folder":"IETF/RFC-1234","source":"IETF/RFC-1234/RFC-1234.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1283","folder":"IETF/RFC-1283","source":"IETF/RFC-1283/RFC-1283.txt","version":null},{"body":"IETF","designation":"RFC 1298","folder":"IETF/RFC-1298","source":"IETF/RFC-1298/RFC-1298.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1350","folder":"IETF/RFC-1350","source":"IETF/RFC-1350/RFC-1350.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1418","folder":"IETF/RFC-1418","source":"IETF/RFC-1418/RFC-1418.txt","version":null},{"body":"IETF","designation":"RFC 1420","folder":"IETF/RFC-1420","source":"IETF/RFC-1420/RFC-1420.txt","version":null},{"body":"IETF","designation":"RFC 1448","folder":"IETF/RFC-1448","source":"IETF/RFC-1448/RFC-1448.txt","version":null},{"body":"IETF","designation":"RFC 1449","folder":"IETF/RFC-1449","source":"IETF/RFC-1449/RFC-1449.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1769","folder":"IETF/RFC-1769","source":"IETF/RFC-1769/RFC-1769.txt","version":null},{"body":"IETF","designation":"RFC 1770","folder":"IETF/RFC-1770","source":"IETF/RFC-1770/RFC-1770.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1905","folder":"IETF/RFC-1905","source":"IETF/RFC-1905/RFC-1905.txt","version":null},{"body":"IETF","designation":"RFC 1906","folder":"IETF/RFC-1906","source":"IETF/RFC-1906/RFC-1906.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1986","folder":"IETF/RFC-1986","source":"IETF/RFC-1986/RFC-1986.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2013","folder":"IETF/RFC-2013","source":"IETF/RFC-2013/RFC-2013.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2059","folder":"IETF/RFC-2059","source":"IETF/RFC-2059/RFC-2059.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2107","folder":"IETF/RFC-2107","source":"IETF/RFC-2107/RFC-2107.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2139","folder":"IETF/RFC-2139","source":"IETF/RFC-2139/RFC-2139.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3096","folder":"IETF/RFC-3096","source":"IETF/RFC-3096/RFC-3096.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3416","folder":"IETF/RFC-3416","source":"IETF/RFC-3416/RFC-3416.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3450","folder":"IETF/RFC-3450","source":"IETF/RFC-3450/RFC-3450.txt","version":null},{"body":"IETF","designation":"RFC 3451","folder":"IETF/RFC-3451","source":"IETF/RFC-3451/RFC-3451.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3576","folder":"IETF/RFC-3576","source":"IETF/RFC-3576/RFC-3576.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3948","folder":"IETF/RFC-3948","source":"IETF/RFC-3948/RFC-3948.txt","version":null},{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 3985","folder":"IETF/RFC-3985","source":"IETF/RFC-3985/RFC-3985.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4113","folder":"IETF/RFC-4113","source":"IETF/RFC-4113/RFC-4113.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4636","folder":"IETF/RFC-4636","source":"IETF/RFC-4636/RFC-4636.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4944","folder":"IETF/RFC-4944","source":"IETF/RFC-4944/RFC-4944.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5097","folder":"IETF/RFC-5097","source":"IETF/RFC-5097/RFC-5097.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5505","folder":"IETF/RFC-5505","source":"IETF/RFC-5505/RFC-5505.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5651","folder":"IETF/RFC-5651","source":"IETF/RFC-5651/RFC-5651.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5775","folder":"IETF/RFC-5775","source":"IETF/RFC-5775/RFC-5775.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 6012","folder":"IETF/RFC-6012","source":"IETF/RFC-6012/RFC-6012.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6064","folder":"IETF/RFC-6064","source":"IETF/RFC-6064/RFC-6064.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6282","folder":"IETF/RFC-6282","source":"IETF/RFC-6282/RFC-6282.txt","version":null},{"body":"IETF","designation":"RFC 6285","folder":"IETF/RFC-6285","source":"IETF/RFC-6285/RFC-6285.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6773","folder":"IETF/RFC-6773","source":"IETF/RFC-6773/RFC-6773.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7388","folder":"IETF/RFC-7388","source":"IETF/RFC-7388/RFC-7388.txt","version":null},{"body":"IETF","designation":"RFC 7510","folder":"IETF/RFC-7510","source":"IETF/RFC-7510/RFC-7510.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 783","folder":"IETF/RFC-783","source":"IETF/RFC-783/RFC-783.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 8087","folder":"IETF/RFC-8087","source":"IETF/RFC-8087/RFC-8087.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 906","folder":"IETF/RFC-906","source":"IETF/RFC-906/RFC-906.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 768 RFC 768 J. Postel\n ISI\n 28 August 1980\n\n User Datagram Protocol\n ----------------------\n\nIntroduction\n------------\n\nThis User Datagram Protocol (UDP) is defined to make available a\ndatagram mode of packet-switched computer communication in the\nenvironment of an interconnected set of computer networks. This\nprotocol assumes that the Internet Protocol (IP) [1] is used as the\nunderlying protocol.\n\nThis protocol provides a procedure for application programs to send\nmessages to other programs with a minimum of protocol mechanism. The\nprotocol is transaction oriented, and delivery and duplicate protection\nare not guaranteed. Applications requiring ordered reliable delivery of\nstreams of data should use the Transmission Control Protocol (TCP) [2].\n\nFormat\n------\n\n \n 0 7 8 15 16 23 24 31 \n +--------+--------+--------+--------+ \n | Source | Destination | \n | Port | Port | \n +--------+--------+--- 768 delivery nested-reference unchanged"},{"id":"IETF RFC 777","type":"specification","body":"IETF","designation":"RFC 777","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc777.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc777.txt","https://www.rfc-editor.org/rfc/rfc777.pdf"],"folder":"IETF/RFC-777","files":{"txt":{"path":"standards/IETF/RFC-777/RFC-777.txt","sha256":"a987e77d4a9dce33b071421641f234ed5ebfdff0f6b4d0353376b8a245f5d0ff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 777 ISI\n April 1981\nUpdates: IENs 109, 128\nUpdates: RFC 760\n\n Internet Control Message Protocol\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be implemented by every IP module.\n\n ICMP messages are sent in se","scope_keywords":["777","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 778","folder":"IETF/RFC-778","source":"IETF/RFC-778/RFC-778.txt","version":null}],"search_text":"IETF RFC 777 Network Working Group J. Postel\nRequest for Comments: 777 ISI\n April 1981\nUpdates: IENs 109, 128\nUpdates: RFC 760\n\n Internet Control Message Protocol\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be implemented by every IP module.\n\n ICMP messages are sent in se 777 identification nested-reference unchanged"},{"id":"IETF RFC 791","type":"specification","body":"IETF","designation":"RFC 791","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc791.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc791.txt","https://www.rfc-editor.org/rfc/rfc791.pdf"],"folder":"IETF/RFC-791","files":{"txt":{"path":"standards/IETF/RFC-791/RFC-791.txt","sha256":"6cfb387fcecfc1b72f2f69343c5b6951b5d263d708162e2b5c66ab8f394f6265"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 791\n \n \n \n \n \n \n \n INTERNET PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW ..","scope_keywords":["791","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0792","folder":"IETF/RFC-0792","source":"IETF/RFC-0792/RFC-0792.txt","version":null},{"body":"IETF","designation":"RFC 0793","folder":"IETF/RFC-0793","source":"IETF/RFC-0793/RFC-0793.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0919","folder":"IETF/RFC-0919","source":"IETF/RFC-0919/RFC-0919.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1016","folder":"IETF/RFC-1016","source":"IETF/RFC-1016/RFC-1016.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1075","folder":"IETF/RFC-1075","source":"IETF/RFC-1075/RFC-1075.txt","version":null},{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null},{"body":"IETF","designation":"RFC 1131","folder":"IETF/RFC-1131","source":"IETF/RFC-1131/RFC-1131.pdf","version":null},{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1234","folder":"IETF/RFC-1234","source":"IETF/RFC-1234/RFC-1234.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1241","folder":"IETF/RFC-1241","source":"IETF/RFC-1241/RFC-1241.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 1248","folder":"IETF/RFC-1248","source":"IETF/RFC-1248/RFC-1248.txt","version":null},{"body":"IETF","designation":"RFC 1252","folder":"IETF/RFC-1252","source":"IETF/RFC-1252/RFC-1252.txt","version":null},{"body":"IETF","designation":"RFC 1253","folder":"IETF/RFC-1253","source":"IETF/RFC-1253/RFC-1253.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1265","folder":"IETF/RFC-1265","source":"IETF/RFC-1265/RFC-1265.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1383","folder":"IETF/RFC-1383","source":"IETF/RFC-1383/RFC-1383.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1455","folder":"IETF/RFC-1455","source":"IETF/RFC-1455/RFC-1455.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 1517","folder":"IETF/RFC-1517","source":"IETF/RFC-1517/RFC-1517.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1624","folder":"IETF/RFC-1624","source":"IETF/RFC-1624/RFC-1624.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1710","folder":"IETF/RFC-1710","source":"IETF/RFC-1710/RFC-1710.txt","version":null},{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1769","folder":"IETF/RFC-1769","source":"IETF/RFC-1769/RFC-1769.txt","version":null},{"body":"IETF","designation":"RFC 1770","folder":"IETF/RFC-1770","source":"IETF/RFC-1770/RFC-1770.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1810","folder":"IETF/RFC-1810","source":"IETF/RFC-1810/RFC-1810.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1819","folder":"IETF/RFC-1819","source":"IETF/RFC-1819/RFC-1819.txt","version":null},{"body":"IETF","designation":"RFC 1850","folder":"IETF/RFC-1850","source":"IETF/RFC-1850/RFC-1850.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 1858","folder":"IETF/RFC-1858","source":"IETF/RFC-1858/RFC-1858.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null},{"body":"IETF","designation":"RFC 1883","folder":"IETF/RFC-1883","source":"IETF/RFC-1883/RFC-1883.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1940","folder":"IETF/RFC-1940","source":"IETF/RFC-1940/RFC-1940.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2004","folder":"IETF/RFC-2004","source":"IETF/RFC-2004/RFC-2004.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2067","folder":"IETF/RFC-2067","source":"IETF/RFC-2067/RFC-2067.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2145","folder":"IETF/RFC-2145","source":"IETF/RFC-2145/RFC-2145.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2233","folder":"IETF/RFC-2233","source":"IETF/RFC-2233/RFC-2233.txt","version":null},{"body":"IETF","designation":"RFC 2283","folder":"IETF/RFC-2283","source":"IETF/RFC-2283/RFC-2283.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2386","folder":"IETF/RFC-2386","source":"IETF/RFC-2386/RFC-2386.txt","version":null},{"body":"IETF","designation":"RFC 2393","folder":"IETF/RFC-2393","source":"IETF/RFC-2393/RFC-2393.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2402","folder":"IETF/RFC-2402","source":"IETF/RFC-2402/RFC-2402.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2434","folder":"IETF/RFC-2434","source":"IETF/RFC-2434/RFC-2434.txt","version":null},{"body":"IETF","designation":"RFC 2441","folder":"IETF/RFC-2441","source":"IETF/RFC-2441/RFC-2441.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2460","folder":"IETF/RFC-2460","source":"IETF/RFC-2460/RFC-2460.txt","version":null},{"body":"IETF","designation":"RFC 2474","folder":"IETF/RFC-2474","source":"IETF/RFC-2474/RFC-2474.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2529","folder":"IETF/RFC-2529","source":"IETF/RFC-2529/RFC-2529.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2661","folder":"IETF/RFC-2661","source":"IETF/RFC-2661/RFC-2661.txt","version":null},{"body":"IETF","designation":"RFC 2678","folder":"IETF/RFC-2678","source":"IETF/RFC-2678/RFC-2678.txt","version":null},{"body":"IETF","designation":"RFC 2679","folder":"IETF/RFC-2679","source":"IETF/RFC-2679/RFC-2679.txt","version":null},{"body":"IETF","designation":"RFC 2680","folder":"IETF/RFC-2680","source":"IETF/RFC-2680/RFC-2680.txt","version":null},{"body":"IETF","designation":"RFC 2681","folder":"IETF/RFC-2681","source":"IETF/RFC-2681/RFC-2681.txt","version":null},{"body":"IETF","designation":"RFC 2734","folder":"IETF/RFC-2734","source":"IETF/RFC-2734/RFC-2734.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2767","folder":"IETF/RFC-2767","source":"IETF/RFC-2767/RFC-2767.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2795","folder":"IETF/RFC-2795","source":"IETF/RFC-2795/RFC-2795.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2835","folder":"IETF/RFC-2835","source":"IETF/RFC-2835/RFC-2835.txt","version":null},{"body":"IETF","designation":"RFC 2858","folder":"IETF/RFC-2858","source":"IETF/RFC-2858/RFC-2858.txt","version":null},{"body":"IETF","designation":"RFC 2863","folder":"IETF/RFC-2863","source":"IETF/RFC-2863/RFC-2863.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2962","folder":"IETF/RFC-2962","source":"IETF/RFC-2962/RFC-2962.txt","version":null},{"body":"IETF","designation":"RFC 2983","folder":"IETF/RFC-2983","source":"IETF/RFC-2983/RFC-2983.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3056","folder":"IETF/RFC-3056","source":"IETF/RFC-3056/RFC-3056.txt","version":null},{"body":"IETF","designation":"RFC 3095","folder":"IETF/RFC-3095","source":"IETF/RFC-3095/RFC-3095.txt","version":null},{"body":"IETF","designation":"RFC 3096","folder":"IETF/RFC-3096","source":"IETF/RFC-3096/RFC-3096.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3173","folder":"IETF/RFC-3173","source":"IETF/RFC-3173/RFC-3173.txt","version":null},{"body":"IETF","designation":"RFC 3175","folder":"IETF/RFC-3175","source":"IETF/RFC-3175/RFC-3175.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3260","folder":"IETF/RFC-3260","source":"IETF/RFC-3260/RFC-3260.txt","version":null},{"body":"IETF","designation":"RFC 3269","folder":"IETF/RFC-3269","source":"IETF/RFC-3269/RFC-3269.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3338","folder":"IETF/RFC-3338","source":"IETF/RFC-3338/RFC-3338.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 3417","folder":"IETF/RFC-3417","source":"IETF/RFC-3417/RFC-3417.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3489","folder":"IETF/RFC-3489","source":"IETF/RFC-3489/RFC-3489.txt","version":null},{"body":"IETF","designation":"RFC 3514","folder":"IETF/RFC-3514","source":"IETF/RFC-3514/RFC-3514.txt","version":null},{"body":"IETF","designation":"RFC 3519","folder":"IETF/RFC-3519","source":"IETF/RFC-3519/RFC-3519.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3670","folder":"IETF/RFC-3670","source":"IETF/RFC-3670/RFC-3670.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3682","folder":"IETF/RFC-3682","source":"IETF/RFC-3682/RFC-3682.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3692","folder":"IETF/RFC-3692","source":"IETF/RFC-3692/RFC-3692.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3750","folder":"IETF/RFC-3750","source":"IETF/RFC-3750/RFC-3750.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3814","folder":"IETF/RFC-3814","source":"IETF/RFC-3814/RFC-3814.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3843","folder":"IETF/RFC-3843","source":"IETF/RFC-3843/RFC-3843.txt","version":null},{"body":"IETF","designation":"RFC 3890","folder":"IETF/RFC-3890","source":"IETF/RFC-3890/RFC-3890.txt","version":null},{"body":"IETF","designation":"RFC 3917","folder":"IETF/RFC-3917","source":"IETF/RFC-3917/RFC-3917.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4019","folder":"IETF/RFC-4019","source":"IETF/RFC-4019/RFC-4019.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4067","folder":"IETF/RFC-4067","source":"IETF/RFC-4067/RFC-4067.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4149","folder":"IETF/RFC-4149","source":"IETF/RFC-4149/RFC-4149.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4213","folder":"IETF/RFC-4213","source":"IETF/RFC-4213/RFC-4213.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4302","folder":"IETF/RFC-4302","source":"IETF/RFC-4302/RFC-4302.txt","version":null},{"body":"IETF","designation":"RFC 4303","folder":"IETF/RFC-4303","source":"IETF/RFC-4303/RFC-4303.txt","version":null},{"body":"IETF","designation":"RFC 4305","folder":"IETF/RFC-4305","source":"IETF/RFC-4305/RFC-4305.txt","version":null},{"body":"IETF","designation":"RFC 4309","folder":"IETF/RFC-4309","source":"IETF/RFC-4309/RFC-4309.txt","version":null},{"body":"IETF","designation":"RFC 4322","folder":"IETF/RFC-4322","source":"IETF/RFC-4322/RFC-4322.txt","version":null},{"body":"IETF","designation":"RFC 4323","folder":"IETF/RFC-4323","source":"IETF/RFC-4323/RFC-4323.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4380","folder":"IETF/RFC-4380","source":"IETF/RFC-4380/RFC-4380.txt","version":null},{"body":"IETF","designation":"RFC 4385","folder":"IETF/RFC-4385","source":"IETF/RFC-4385/RFC-4385.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4540","folder":"IETF/RFC-4540","source":"IETF/RFC-4540/RFC-4540.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4607","folder":"IETF/RFC-4607","source":"IETF/RFC-4607/RFC-4607.txt","version":null},{"body":"IETF","designation":"RFC 4623","folder":"IETF/RFC-4623","source":"IETF/RFC-4623/RFC-4623.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4727","folder":"IETF/RFC-4727","source":"IETF/RFC-4727/RFC-4727.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4750","folder":"IETF/RFC-4750","source":"IETF/RFC-4750/RFC-4750.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4815","folder":"IETF/RFC-4815","source":"IETF/RFC-4815/RFC-4815.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4945","folder":"IETF/RFC-4945","source":"IETF/RFC-4945/RFC-4945.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4963","folder":"IETF/RFC-4963","source":"IETF/RFC-4963/RFC-4963.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5082","folder":"IETF/RFC-5082","source":"IETF/RFC-5082/RFC-5082.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5225","folder":"IETF/RFC-5225","source":"IETF/RFC-5225/RFC-5225.txt","version":null},{"body":"IETF","designation":"RFC 5226","folder":"IETF/RFC-5226","source":"IETF/RFC-5226/RFC-5226.txt","version":null},{"body":"IETF","designation":"RFC 5237","folder":"IETF/RFC-5237","source":"IETF/RFC-5237/RFC-5237.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5340","folder":"IETF/RFC-5340","source":"IETF/RFC-5340/RFC-5340.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5426","folder":"IETF/RFC-5426","source":"IETF/RFC-5426/RFC-5426.txt","version":null},{"body":"IETF","designation":"RFC 5474","folder":"IETF/RFC-5474","source":"IETF/RFC-5474/RFC-5474.txt","version":null},{"body":"IETF","designation":"RFC 5477","folder":"IETF/RFC-5477","source":"IETF/RFC-5477/RFC-5477.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5720","folder":"IETF/RFC-5720","source":"IETF/RFC-5720/RFC-5720.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5766","folder":"IETF/RFC-5766","source":"IETF/RFC-5766/RFC-5766.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6491","folder":"IETF/RFC-6491","source":"IETF/RFC-6491/RFC-6491.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6621","folder":"IETF/RFC-6621","source":"IETF/RFC-6621/RFC-6621.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6746","folder":"IETF/RFC-6746","source":"IETF/RFC-6746/RFC-6746.txt","version":null},{"body":"IETF","designation":"RFC 6830","folder":"IETF/RFC-6830","source":"IETF/RFC-6830/RFC-6830.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6864","folder":"IETF/RFC-6864","source":"IETF/RFC-6864/RFC-6864.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 792","folder":"IETF/RFC-792","source":"IETF/RFC-792/RFC-792.txt","version":null},{"body":"IETF","designation":"RFC 793","folder":"IETF/RFC-793","source":"IETF/RFC-793/RFC-793.txt","version":null},{"body":"IETF","designation":"RFC 795","folder":"IETF/RFC-795","source":"IETF/RFC-795/RFC-795.txt","version":null},{"body":"IETF","designation":"RFC 796","folder":"IETF/RFC-796","source":"IETF/RFC-796/RFC-796.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 810","folder":"IETF/RFC-810","source":"IETF/RFC-810/RFC-810.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 8200","folder":"IETF/RFC-8200","source":"IETF/RFC-8200/RFC-8200.txt","version":null},{"body":"IETF","designation":"RFC 823","folder":"IETF/RFC-823","source":"IETF/RFC-823/RFC-823.txt","version":null},{"body":"IETF","designation":"RFC 824","folder":"IETF/RFC-824","source":"IETF/RFC-824/RFC-824.txt","version":null},{"body":"IETF","designation":"RFC 8261","folder":"IETF/RFC-8261","source":"IETF/RFC-8261/RFC-8261.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 8782","folder":"IETF/RFC-8782","source":"IETF/RFC-8782/RFC-8782.txt","version":null},{"body":"IETF","designation":"RFC 879","folder":"IETF/RFC-879","source":"IETF/RFC-879/RFC-879.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 906","folder":"IETF/RFC-906","source":"IETF/RFC-906/RFC-906.txt","version":null},{"body":"IETF","designation":"RFC 908","folder":"IETF/RFC-908","source":"IETF/RFC-908/RFC-908.txt","version":null},{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null},{"body":"IETF","designation":"RFC 919","folder":"IETF/RFC-919","source":"IETF/RFC-919/RFC-919.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 983","folder":"IETF/RFC-983","source":"IETF/RFC-983/RFC-983.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 791 RFC: 791\n \n \n \n \n \n \n \n INTERNET PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Internet Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 1\n 1.3 Interfaces .................................................... 1\n 1.4 Operation ..................................................... 2\n\n2. OVERVIEW .. 791 key path nested-reference unchanged"},{"id":"IETF RFC 793","type":"specification","body":"IETF","designation":"RFC 793","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc793.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc793.txt","https://www.rfc-editor.org/rfc/rfc793.pdf"],"folder":"IETF/RFC-793","files":{"txt":{"path":"standards/IETF/RFC-793/RFC-793.txt","sha256":"e55b1faa35edbeecceb2400233a16ae81897bdf9c31d5b3031e91139e5ea8142"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 793\n \n \n \n \n \n \n \n TRANSMISSION CONTROL PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces .............................................","scope_keywords":["793"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0821","folder":"IETF/RFC-0821","source":"IETF/RFC-0821/RFC-0821.txt","version":null},{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1072","folder":"IETF/RFC-1072","source":"IETF/RFC-1072/RFC-1072.txt","version":null},{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1105","folder":"IETF/RFC-1105","source":"IETF/RFC-1105/RFC-1105.txt","version":null},{"body":"IETF","designation":"RFC 1106","folder":"IETF/RFC-1106","source":"IETF/RFC-1106/RFC-1106.txt","version":null},{"body":"IETF","designation":"RFC 1144","folder":"IETF/RFC-1144","source":"IETF/RFC-1144/RFC-1144.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1177","folder":"IETF/RFC-1177","source":"IETF/RFC-1177/RFC-1177.txt","version":null},{"body":"IETF","designation":"RFC 1185","folder":"IETF/RFC-1185","source":"IETF/RFC-1185/RFC-1185.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1190","folder":"IETF/RFC-1190","source":"IETF/RFC-1190/RFC-1190.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1241","folder":"IETF/RFC-1241","source":"IETF/RFC-1241/RFC-1241.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1270","folder":"IETF/RFC-1270","source":"IETF/RFC-1270/RFC-1270.txt","version":null},{"body":"IETF","designation":"RFC 1301","folder":"IETF/RFC-1301","source":"IETF/RFC-1301/RFC-1301.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1626","folder":"IETF/RFC-1626","source":"IETF/RFC-1626/RFC-1626.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1693","folder":"IETF/RFC-1693","source":"IETF/RFC-1693/RFC-1693.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1726","folder":"IETF/RFC-1726","source":"IETF/RFC-1726/RFC-1726.txt","version":null},{"body":"IETF","designation":"RFC 1770","folder":"IETF/RFC-1770","source":"IETF/RFC-1770/RFC-1770.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1831","folder":"IETF/RFC-1831","source":"IETF/RFC-1831/RFC-1831.txt","version":null},{"body":"IETF","designation":"RFC 1858","folder":"IETF/RFC-1858","source":"IETF/RFC-1858/RFC-1858.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1982","folder":"IETF/RFC-1982","source":"IETF/RFC-1982/RFC-1982.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2012","folder":"IETF/RFC-2012","source":"IETF/RFC-2012/RFC-2012.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2101","folder":"IETF/RFC-2101","source":"IETF/RFC-2101/RFC-2101.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2428","folder":"IETF/RFC-2428","source":"IETF/RFC-2428/RFC-2428.txt","version":null},{"body":"IETF","designation":"RFC 2452","folder":"IETF/RFC-2452","source":"IETF/RFC-2452/RFC-2452.txt","version":null},{"body":"IETF","designation":"RFC 2481","folder":"IETF/RFC-2481","source":"IETF/RFC-2481/RFC-2481.txt","version":null},{"body":"IETF","designation":"RFC 2488","folder":"IETF/RFC-2488","source":"IETF/RFC-2488/RFC-2488.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2577","folder":"IETF/RFC-2577","source":"IETF/RFC-2577/RFC-2577.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2637","folder":"IETF/RFC-2637","source":"IETF/RFC-2637/RFC-2637.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2675","folder":"IETF/RFC-2675","source":"IETF/RFC-2675/RFC-2675.txt","version":null},{"body":"IETF","designation":"RFC 2747","folder":"IETF/RFC-2747","source":"IETF/RFC-2747/RFC-2747.txt","version":null},{"body":"IETF","designation":"RFC 2760","folder":"IETF/RFC-2760","source":"IETF/RFC-2760/RFC-2760.txt","version":null},{"body":"IETF","designation":"RFC 2775","folder":"IETF/RFC-2775","source":"IETF/RFC-2775/RFC-2775.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2795","folder":"IETF/RFC-2795","source":"IETF/RFC-2795/RFC-2795.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2873","folder":"IETF/RFC-2873","source":"IETF/RFC-2873/RFC-2873.txt","version":null},{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 2960","folder":"IETF/RFC-2960","source":"IETF/RFC-2960/RFC-2960.txt","version":null},{"body":"IETF","designation":"RFC 2975","folder":"IETF/RFC-2975","source":"IETF/RFC-2975/RFC-2975.txt","version":null},{"body":"IETF","designation":"RFC 2988","folder":"IETF/RFC-2988","source":"IETF/RFC-2988/RFC-2988.txt","version":null},{"body":"IETF","designation":"RFC 2993","folder":"IETF/RFC-2993","source":"IETF/RFC-2993/RFC-2993.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3018","folder":"IETF/RFC-3018","source":"IETF/RFC-3018/RFC-3018.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3042","folder":"IETF/RFC-3042","source":"IETF/RFC-3042/RFC-3042.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3081","folder":"IETF/RFC-3081","source":"IETF/RFC-3081/RFC-3081.txt","version":null},{"body":"IETF","designation":"RFC 3124","folder":"IETF/RFC-3124","source":"IETF/RFC-3124/RFC-3124.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3142","folder":"IETF/RFC-3142","source":"IETF/RFC-3142/RFC-3142.txt","version":null},{"body":"IETF","designation":"RFC 3148","folder":"IETF/RFC-3148","source":"IETF/RFC-3148/RFC-3148.txt","version":null},{"body":"IETF","designation":"RFC 3155","folder":"IETF/RFC-3155","source":"IETF/RFC-3155/RFC-3155.txt","version":null},{"body":"IETF","designation":"RFC 3168","folder":"IETF/RFC-3168","source":"IETF/RFC-3168/RFC-3168.txt","version":null},{"body":"IETF","designation":"RFC 3237","folder":"IETF/RFC-3237","source":"IETF/RFC-3237/RFC-3237.txt","version":null},{"body":"IETF","designation":"RFC 3242","folder":"IETF/RFC-3242","source":"IETF/RFC-3242/RFC-3242.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3257","folder":"IETF/RFC-3257","source":"IETF/RFC-3257/RFC-3257.txt","version":null},{"body":"IETF","designation":"RFC 3291","folder":"IETF/RFC-3291","source":"IETF/RFC-3291/RFC-3291.txt","version":null},{"body":"IETF","designation":"RFC 3360","folder":"IETF/RFC-3360","source":"IETF/RFC-3360/RFC-3360.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3430","folder":"IETF/RFC-3430","source":"IETF/RFC-3430/RFC-3430.txt","version":null},{"body":"IETF","designation":"RFC 3436","folder":"IETF/RFC-3436","source":"IETF/RFC-3436/RFC-3436.txt","version":null},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 3481","folder":"IETF/RFC-3481","source":"IETF/RFC-3481/RFC-3481.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 3517","folder":"IETF/RFC-3517","source":"IETF/RFC-3517/RFC-3517.txt","version":null},{"body":"IETF","designation":"RFC 3522","folder":"IETF/RFC-3522","source":"IETF/RFC-3522/RFC-3522.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3708","folder":"IETF/RFC-3708","source":"IETF/RFC-3708/RFC-3708.txt","version":null},{"body":"IETF","designation":"RFC 3715","folder":"IETF/RFC-3715","source":"IETF/RFC-3715/RFC-3715.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3723","folder":"IETF/RFC-3723","source":"IETF/RFC-3723/RFC-3723.txt","version":null},{"body":"IETF","designation":"RFC 3724","folder":"IETF/RFC-3724","source":"IETF/RFC-3724/RFC-3724.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3734","folder":"IETF/RFC-3734","source":"IETF/RFC-3734/RFC-3734.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3783","folder":"IETF/RFC-3783","source":"IETF/RFC-3783/RFC-3783.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3821","folder":"IETF/RFC-3821","source":"IETF/RFC-3821/RFC-3821.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3954","folder":"IETF/RFC-3954","source":"IETF/RFC-3954/RFC-3954.txt","version":null},{"body":"IETF","designation":"RFC 3955","folder":"IETF/RFC-3955","source":"IETF/RFC-3955/RFC-3955.txt","version":null},{"body":"IETF","designation":"RFC 4001","folder":"IETF/RFC-4001","source":"IETF/RFC-4001/RFC-4001.txt","version":null},{"body":"IETF","designation":"RFC 4015","folder":"IETF/RFC-4015","source":"IETF/RFC-4015/RFC-4015.txt","version":null},{"body":"IETF","designation":"RFC 4022","folder":"IETF/RFC-4022","source":"IETF/RFC-4022/RFC-4022.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4163","folder":"IETF/RFC-4163","source":"IETF/RFC-4163/RFC-4163.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4180","folder":"IETF/RFC-4180","source":"IETF/RFC-4180/RFC-4180.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4294","folder":"IETF/RFC-4294","source":"IETF/RFC-4294/RFC-4294.txt","version":null},{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4341","folder":"IETF/RFC-4341","source":"IETF/RFC-4341/RFC-4341.txt","version":null},{"body":"IETF","designation":"RFC 4347","folder":"IETF/RFC-4347","source":"IETF/RFC-4347/RFC-4347.txt","version":null},{"body":"IETF","designation":"RFC 4362","folder":"IETF/RFC-4362","source":"IETF/RFC-4362/RFC-4362.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4430","folder":"IETF/RFC-4430","source":"IETF/RFC-4430/RFC-4430.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4786","folder":"IETF/RFC-4786","source":"IETF/RFC-4786/RFC-4786.txt","version":null},{"body":"IETF","designation":"RFC 4821","folder":"IETF/RFC-4821","source":"IETF/RFC-4821/RFC-4821.txt","version":null},{"body":"IETF","designation":"RFC 4898","folder":"IETF/RFC-4898","source":"IETF/RFC-4898/RFC-4898.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4934","folder":"IETF/RFC-4934","source":"IETF/RFC-4934/RFC-4934.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4953","folder":"IETF/RFC-4953","source":"IETF/RFC-4953/RFC-4953.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 4961","folder":"IETF/RFC-4961","source":"IETF/RFC-4961/RFC-4961.txt","version":null},{"body":"IETF","designation":"RFC 4987","folder":"IETF/RFC-4987","source":"IETF/RFC-4987/RFC-4987.txt","version":null},{"body":"IETF","designation":"RFC 4995","folder":"IETF/RFC-4995","source":"IETF/RFC-4995/RFC-4995.txt","version":null},{"body":"IETF","designation":"RFC 4996","folder":"IETF/RFC-4996","source":"IETF/RFC-4996/RFC-4996.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5040","folder":"IETF/RFC-5040","source":"IETF/RFC-5040/RFC-5040.txt","version":null},{"body":"IETF","designation":"RFC 5041","folder":"IETF/RFC-5041","source":"IETF/RFC-5041/RFC-5041.txt","version":null},{"body":"IETF","designation":"RFC 5042","folder":"IETF/RFC-5042","source":"IETF/RFC-5042/RFC-5042.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5046","folder":"IETF/RFC-5046","source":"IETF/RFC-5046/RFC-5046.txt","version":null},{"body":"IETF","designation":"RFC 5101","folder":"IETF/RFC-5101","source":"IETF/RFC-5101/RFC-5101.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5128","folder":"IETF/RFC-5128","source":"IETF/RFC-5128/RFC-5128.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5382","folder":"IETF/RFC-5382","source":"IETF/RFC-5382/RFC-5382.txt","version":null},{"body":"IETF","designation":"RFC 5383","folder":"IETF/RFC-5383","source":"IETF/RFC-5383/RFC-5383.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5513","folder":"IETF/RFC-5513","source":"IETF/RFC-5513/RFC-5513.txt","version":null},{"body":"IETF","designation":"RFC 5531","folder":"IETF/RFC-5531","source":"IETF/RFC-5531/RFC-5531.txt","version":null},{"body":"IETF","designation":"RFC 5562","folder":"IETF/RFC-5562","source":"IETF/RFC-5562/RFC-5562.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null},{"body":"IETF","designation":"RFC 5575","folder":"IETF/RFC-5575","source":"IETF/RFC-5575/RFC-5575.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 5596","folder":"IETF/RFC-5596","source":"IETF/RFC-5596/RFC-5596.txt","version":null},{"body":"IETF","designation":"RFC 5625","folder":"IETF/RFC-5625","source":"IETF/RFC-5625/RFC-5625.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5660","folder":"IETF/RFC-5660","source":"IETF/RFC-5660/RFC-5660.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5677","folder":"IETF/RFC-5677","source":"IETF/RFC-5677/RFC-5677.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5734","folder":"IETF/RFC-5734","source":"IETF/RFC-5734/RFC-5734.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 5795","folder":"IETF/RFC-5795","source":"IETF/RFC-5795/RFC-5795.txt","version":null},{"body":"IETF","designation":"RFC 5827","folder":"IETF/RFC-5827","source":"IETF/RFC-5827/RFC-5827.txt","version":null},{"body":"IETF","designation":"RFC 5898","folder":"IETF/RFC-5898","source":"IETF/RFC-5898/RFC-5898.txt","version":null},{"body":"IETF","designation":"RFC 5905","folder":"IETF/RFC-5905","source":"IETF/RFC-5905/RFC-5905.txt","version":null},{"body":"IETF","designation":"RFC 5925","folder":"IETF/RFC-5925","source":"IETF/RFC-5925/RFC-5925.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 5936","folder":"IETF/RFC-5936","source":"IETF/RFC-5936/RFC-5936.txt","version":null},{"body":"IETF","designation":"RFC 5961","folder":"IETF/RFC-5961","source":"IETF/RFC-5961/RFC-5961.txt","version":null},{"body":"IETF","designation":"RFC 5966","folder":"IETF/RFC-5966","source":"IETF/RFC-5966/RFC-5966.txt","version":null},{"body":"IETF","designation":"RFC 5985","folder":"IETF/RFC-5985","source":"IETF/RFC-5985/RFC-5985.txt","version":null},{"body":"IETF","designation":"RFC 6013","folder":"IETF/RFC-6013","source":"IETF/RFC-6013/RFC-6013.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6039","folder":"IETF/RFC-6039","source":"IETF/RFC-6039/RFC-6039.txt","version":null},{"body":"IETF","designation":"RFC 6056","folder":"IETF/RFC-6056","source":"IETF/RFC-6056/RFC-6056.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6077","folder":"IETF/RFC-6077","source":"IETF/RFC-6077/RFC-6077.txt","version":null},{"body":"IETF","designation":"RFC 6083","folder":"IETF/RFC-6083","source":"IETF/RFC-6083/RFC-6083.txt","version":null},{"body":"IETF","designation":"RFC 6084","folder":"IETF/RFC-6084","source":"IETF/RFC-6084/RFC-6084.txt","version":null},{"body":"IETF","designation":"RFC 6086","folder":"IETF/RFC-6086","source":"IETF/RFC-6086/RFC-6086.txt","version":null},{"body":"IETF","designation":"RFC 6088","folder":"IETF/RFC-6088","source":"IETF/RFC-6088/RFC-6088.txt","version":null},{"body":"IETF","designation":"RFC 6092","folder":"IETF/RFC-6092","source":"IETF/RFC-6092/RFC-6092.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6135","folder":"IETF/RFC-6135","source":"IETF/RFC-6135/RFC-6135.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6146","folder":"IETF/RFC-6146","source":"IETF/RFC-6146/RFC-6146.txt","version":null},{"body":"IETF","designation":"RFC 6181","folder":"IETF/RFC-6181","source":"IETF/RFC-6181/RFC-6181.txt","version":null},{"body":"IETF","designation":"RFC 6182","folder":"IETF/RFC-6182","source":"IETF/RFC-6182/RFC-6182.txt","version":null},{"body":"IETF","designation":"RFC 6191","folder":"IETF/RFC-6191","source":"IETF/RFC-6191/RFC-6191.txt","version":null},{"body":"IETF","designation":"RFC 6202","folder":"IETF/RFC-6202","source":"IETF/RFC-6202/RFC-6202.txt","version":null},{"body":"IETF","designation":"RFC 6219","folder":"IETF/RFC-6219","source":"IETF/RFC-6219/RFC-6219.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6284","folder":"IETF/RFC-6284","source":"IETF/RFC-6284/RFC-6284.txt","version":null},{"body":"IETF","designation":"RFC 6298","folder":"IETF/RFC-6298","source":"IETF/RFC-6298/RFC-6298.txt","version":null},{"body":"IETF","designation":"RFC 6335","folder":"IETF/RFC-6335","source":"IETF/RFC-6335/RFC-6335.txt","version":null},{"body":"IETF","designation":"RFC 6347","folder":"IETF/RFC-6347","source":"IETF/RFC-6347/RFC-6347.txt","version":null},{"body":"IETF","designation":"RFC 6356","folder":"IETF/RFC-6356","source":"IETF/RFC-6356/RFC-6356.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 6429","folder":"IETF/RFC-6429","source":"IETF/RFC-6429/RFC-6429.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 6458","folder":"IETF/RFC-6458","source":"IETF/RFC-6458/RFC-6458.txt","version":null},{"body":"IETF","designation":"RFC 6466","folder":"IETF/RFC-6466","source":"IETF/RFC-6466/RFC-6466.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 6574","folder":"IETF/RFC-6574","source":"IETF/RFC-6574/RFC-6574.txt","version":null},{"body":"IETF","designation":"RFC 6627","folder":"IETF/RFC-6627","source":"IETF/RFC-6627/RFC-6627.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6675","folder":"IETF/RFC-6675","source":"IETF/RFC-6675/RFC-6675.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6824","folder":"IETF/RFC-6824","source":"IETF/RFC-6824/RFC-6824.txt","version":null},{"body":"IETF","designation":"RFC 6846","folder":"IETF/RFC-6846","source":"IETF/RFC-6846/RFC-6846.txt","version":null},{"body":"IETF","designation":"RFC 6887","folder":"IETF/RFC-6887","source":"IETF/RFC-6887/RFC-6887.txt","version":null},{"body":"IETF","designation":"RFC 6888","folder":"IETF/RFC-6888","source":"IETF/RFC-6888/RFC-6888.txt","version":null},{"body":"IETF","designation":"RFC 6897","folder":"IETF/RFC-6897","source":"IETF/RFC-6897/RFC-6897.txt","version":null},{"body":"IETF","designation":"RFC 6921","folder":"IETF/RFC-6921","source":"IETF/RFC-6921/RFC-6921.txt","version":null},{"body":"IETF","designation":"RFC 6936","folder":"IETF/RFC-6936","source":"IETF/RFC-6936/RFC-6936.txt","version":null},{"body":"IETF","designation":"RFC 6937","folder":"IETF/RFC-6937","source":"IETF/RFC-6937/RFC-6937.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7094","folder":"IETF/RFC-7094","source":"IETF/RFC-7094/RFC-7094.txt","version":null},{"body":"IETF","designation":"RFC 7111","folder":"IETF/RFC-7111","source":"IETF/RFC-7111/RFC-7111.txt","version":null},{"body":"IETF","designation":"RFC 7145","folder":"IETF/RFC-7145","source":"IETF/RFC-7145/RFC-7145.txt","version":null},{"body":"IETF","designation":"RFC 7202","folder":"IETF/RFC-7202","source":"IETF/RFC-7202/RFC-7202.txt","version":null},{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7288","folder":"IETF/RFC-7288","source":"IETF/RFC-7288/RFC-7288.txt","version":null},{"body":"IETF","designation":"RFC 7323","folder":"IETF/RFC-7323","source":"IETF/RFC-7323/RFC-7323.txt","version":null},{"body":"IETF","designation":"RFC 7413","folder":"IETF/RFC-7413","source":"IETF/RFC-7413/RFC-7413.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7540","folder":"IETF/RFC-7540","source":"IETF/RFC-7540/RFC-7540.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 7604","folder":"IETF/RFC-7604","source":"IETF/RFC-7604/RFC-7604.txt","version":null},{"body":"IETF","designation":"RFC 7605","folder":"IETF/RFC-7605","source":"IETF/RFC-7605/RFC-7605.txt","version":null},{"body":"IETF","designation":"RFC 7657","folder":"IETF/RFC-7657","source":"IETF/RFC-7657/RFC-7657.txt","version":null},{"body":"IETF","designation":"RFC 7661","folder":"IETF/RFC-7661","source":"IETF/RFC-7661/RFC-7661.txt","version":null},{"body":"IETF","designation":"RFC 7676","folder":"IETF/RFC-7676","source":"IETF/RFC-7676/RFC-7676.txt","version":null},{"body":"IETF","designation":"RFC 7766","folder":"IETF/RFC-7766","source":"IETF/RFC-7766/RFC-7766.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7872","folder":"IETF/RFC-7872","source":"IETF/RFC-7872/RFC-7872.txt","version":null},{"body":"IETF","designation":"RFC 788","folder":"IETF/RFC-788","source":"IETF/RFC-788/RFC-788.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 7915","folder":"IETF/RFC-7915","source":"IETF/RFC-7915/RFC-7915.txt","version":null},{"body":"IETF","designation":"RFC 7918","folder":"IETF/RFC-7918","source":"IETF/RFC-7918/RFC-7918.txt","version":null},{"body":"IETF","designation":"RFC 7928","folder":"IETF/RFC-7928","source":"IETF/RFC-7928/RFC-7928.txt","version":null},{"body":"IETF","designation":"RFC 7996","folder":"IETF/RFC-7996","source":"IETF/RFC-7996/RFC-7996.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 821","folder":"IETF/RFC-821","source":"IETF/RFC-821/RFC-821.txt","version":null},{"body":"IETF","designation":"RFC 8257","folder":"IETF/RFC-8257","source":"IETF/RFC-8257/RFC-8257.txt","version":null},{"body":"IETF","designation":"RFC 8314","folder":"IETF/RFC-8314","source":"IETF/RFC-8314/RFC-8314.txt","version":null},{"body":"IETF","designation":"RFC 8323","folder":"IETF/RFC-8323","source":"IETF/RFC-8323/RFC-8323.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8612","folder":"IETF/RFC-8612","source":"IETF/RFC-8612/RFC-8612.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 879","folder":"IETF/RFC-879","source":"IETF/RFC-879/RFC-879.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 8811","folder":"IETF/RFC-8811","source":"IETF/RFC-8811/RFC-8811.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 8841","folder":"IETF/RFC-8841","source":"IETF/RFC-8841/RFC-8841.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8985","folder":"IETF/RFC-8985","source":"IETF/RFC-8985/RFC-8985.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 9113","folder":"IETF/RFC-9113","source":"IETF/RFC-9113/RFC-9113.txt","version":null},{"body":"IETF","designation":"RFC 9114","folder":"IETF/RFC-9114","source":"IETF/RFC-9114/RFC-9114.txt","version":null},{"body":"IETF","designation":"RFC 9147","folder":"IETF/RFC-9147","source":"IETF/RFC-9147/RFC-9147.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 793 RFC: 793\n \n \n \n \n \n \n \n TRANSMISSION CONTROL PROTOCOL\n \n \n DARPA INTERNET PROGRAM\n \n PROTOCOL SPECIFICATION\n \n \n \n September 1981\n\n prepared for\n \n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\f\n\f\n\nSeptember 1981 \n Transmission Control Protocol\n\n TABLE OF CONTENTS\n\n PREFACE ........................................................ iii\n\n1. INTRODUCTION ..................................................... 1\n\n 1.1 Motivation .................................................... 1\n 1.2 Scope ......................................................... 2\n 1.3 About This Document ........................................... 2\n 1.4 Interfaces ............................................. 793 nested-reference unchanged"},{"id":"IETF RFC 764","type":"specification","body":"IETF","designation":"RFC 764","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc764.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc764.txt","https://www.rfc-editor.org/rfc/rfc764.pdf"],"folder":"IETF/RFC-764","files":{"txt":{"path":"standards/IETF/RFC-764/RFC-764.txt","sha256":"fdea3a32868fe31d55a16ab5be325e8039a2031ca8471e15df54206605db4613"}},"tags":["nested-reference","unchanged"],"summary":"IEN 148 J. Postel\nRFC 764 ISI\n June 1980\n\n TELNET PROTOCOL SPECIFICATION\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information. TCP and the connection establishment procedure are\n documentented in the ARPA Internet Protocol Handbook.\n\n The TELNET Protocol is built upon three main ideas: first, the\n concept of a \"Network Virtual Terminal\"; secon","scope_keywords":["764","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1350","folder":"IETF/RFC-1350","source":"IETF/RFC-1350/RFC-1350.txt","version":null},{"body":"IETF","designation":"RFC 776","folder":"IETF/RFC-776","source":"IETF/RFC-776/RFC-776.txt","version":null},{"body":"IETF","designation":"RFC 783","folder":"IETF/RFC-783","source":"IETF/RFC-783/RFC-783.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 764 IEN 148 J. Postel\nRFC 764 ISI\n June 1980\n\n TELNET PROTOCOL SPECIFICATION\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information. TCP and the connection establishment procedure are\n documentented in the ARPA Internet Protocol Handbook.\n\n The TELNET Protocol is built upon three main ideas: first, the\n concept of a \"Network Virtual Terminal\"; secon 764 presentation nested-reference unchanged"},{"id":"IETF RFC 783","type":"specification","body":"IETF","designation":"RFC 783","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc783.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc783.txt","https://www.rfc-editor.org/rfc/rfc783.pdf"],"folder":"IETF/RFC-783","files":{"txt":{"path":"standards/IETF/RFC-783/RFC-783.txt","sha256":"90ae54295a41acae7519ee1c1e6c085c066c9e5079ceafe0cf79c63d6aa60dda"}},"tags":["nested-reference","unchanged"],"summary":"TFTP is a simple protocol to transfer files, and therefore was named","scope_keywords":["783","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1350","folder":"IETF/RFC-1350","source":"IETF/RFC-1350/RFC-1350.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 879","folder":"IETF/RFC-879","source":"IETF/RFC-879/RFC-879.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 906","folder":"IETF/RFC-906","source":"IETF/RFC-906/RFC-906.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 783 TFTP is a simple protocol to transfer files, and therefore was named 783 authentication nested-reference unchanged"},{"id":"IETF RFC 801","type":"specification","body":"IETF","designation":"RFC 801","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc801.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc801.txt","https://www.rfc-editor.org/rfc/rfc801.pdf"],"folder":"IETF/RFC-801","files":{"txt":{"path":"standards/IETF/RFC-801/RFC-801.txt","sha256":"a7cbc0348ceb9f0f3b93f31a012286e157fc001034f6877ffdab274e92167dcc"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 801 ISI\n November 1981\n\n NCP/TCP TRANSITION PLAN\n\nIntroduction\n------------\n\n ARPA sponsored research on computer networks led to the development\n of the ARPANET. The installation of the ARPANET began in September\n 1969, and regular operational use was underway by 1971. The ARPANET\n has been an operational service for at least 10 years. Even while it\n has provided a reliable service in support of a variety of computer\n research activities, it has itself been a subject of continuing\n research, and has evolved significantly during that time.\n\n In the past several years ARPA has sponsored additional research on\n computer networks, principally networks based on different underlying\n communication techniques, in particular, digital packet broadcast\n radio and satellite networks. Also, in the ARPA community there has\n been significant work ","scope_keywords":["801","delivery","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 805","folder":"IETF/RFC-805","source":"IETF/RFC-805/RFC-805.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null}],"search_text":"IETF RFC 801 Network Working Group J. Postel\nRequest for Comments: 801 ISI\n November 1981\n\n NCP/TCP TRANSITION PLAN\n\nIntroduction\n------------\n\n ARPA sponsored research on computer networks led to the development\n of the ARPANET. The installation of the ARPANET began in September\n 1969, and regular operational use was underway by 1971. The ARPANET\n has been an operational service for at least 10 years. Even while it\n has provided a reliable service in support of a variety of computer\n research activities, it has itself been a subject of continuing\n research, and has evolved significantly during that time.\n\n In the past several years ARPA has sponsored additional research on\n computer networks, principally networks based on different underlying\n communication techniques, in particular, digital packet broadcast\n radio and satellite networks. Also, in the ARPA community there has\n been significant work  801 delivery key subject nested-reference unchanged"},{"id":"IETF RFC 887","type":"specification","body":"IETF","designation":"RFC 887","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc887.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc887.txt","https://www.rfc-editor.org/rfc/rfc887.pdf"],"folder":"IETF/RFC-887","files":{"txt":{"path":"standards/IETF/RFC-887/RFC-887.txt","sha256":"1a72bad501b04f0055f423645bdbeb6fdd9d20a7d13f665613a0e04ceb0a3f7f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Accetta\nRequest for Comments: 887 Carnegie-Mellon University\n December 1983\n\n RESOURCE LOCATION PROTOCOL\n\nThis note describes a resource location protocol for use in the ARPA\nInternet. It is most useful on networks employing technologies which\nsupport some method of broadcast addressing, however it may also be used\non other types of networks. For maximum benefit, all hosts which\nprovide significant resources or services to other hosts on the Internet\nshould implement this protocol. Hosts failing to implement the Resource\nLocation Protocol risk being ignored by other hosts which are attempting\nto locate resources on the Internet. This RFC specifies a draft\nstandard for the ARPA Internet community.\n\nThe Resource Location Protocol (RLP) utilizes the User Datagram Protocol\n(UDP) [1] which in turn calls on the Internet Protocol (IP) [3] to\ndeliver its datagrams. See A","scope_keywords":["887","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 887 Network Working Group M. Accetta\nRequest for Comments: 887 Carnegie-Mellon University\n December 1983\n\n RESOURCE LOCATION PROTOCOL\n\nThis note describes a resource location protocol for use in the ARPA\nInternet. It is most useful on networks employing technologies which\nsupport some method of broadcast addressing, however it may also be used\non other types of networks. For maximum benefit, all hosts which\nprovide significant resources or services to other hosts on the Internet\nshould implement this protocol. Hosts failing to implement the Resource\nLocation Protocol risk being ignored by other hosts which are attempting\nto locate resources on the Internet. This RFC specifies a draft\nstandard for the ARPA Internet community.\n\nThe Resource Location Protocol (RLP) utilizes the User Datagram Protocol\n(UDP) [1] which in turn calls on the Internet Protocol (IP) [3] to\ndeliver its datagrams. See A 887 risk nested-reference unchanged"},{"id":"IETF RFC 951","type":"specification","body":"IETF","designation":"RFC 951","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc951.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc951.txt","https://www.rfc-editor.org/rfc/rfc951.pdf"],"folder":"IETF/RFC-951","files":{"txt":{"path":"standards/IETF/RFC-951/RFC-951.txt","sha256":"098809562693d95c502d59451fa8cc6a4a2f263448fad077f0af677088cb0c52"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Bill Croft (Stanford University)\nRequest for Comments: 951 John Gilmore (Sun Microsystems)\n September 1985\n\n BOOTSTRAP PROTOCOL (BOOTP)\n\n1. Status of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n2. Overview\n\n This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows\n a diskless client machine to discover its own IP address, the address\n of a server host, and the name of a file to be loaded into memory and\n executed. The bootstrap operation can be thought of as consisting of\n TWO PHASES. This RFC describes the first phase, which could be\n labeled 'address determination and bootfile selection'. After this\n address and filename information is obtained, control passes to the\n second phase of the bootstrap where a file tran","scope_keywords":["951","path","qualified"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3396","folder":"IETF/RFC-3396","source":"IETF/RFC-3396/RFC-3396.txt","version":null},{"body":"IETF","designation":"RFC 3527","folder":"IETF/RFC-3527","source":"IETF/RFC-3527/RFC-3527.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4030","folder":"IETF/RFC-4030","source":"IETF/RFC-4030/RFC-4030.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4390","folder":"IETF/RFC-4390","source":"IETF/RFC-4390/RFC-4390.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 6607","folder":"IETF/RFC-6607","source":"IETF/RFC-6607/RFC-6607.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null},{"body":"IETF","designation":"RFC 6926","folder":"IETF/RFC-6926","source":"IETF/RFC-6926/RFC-6926.txt","version":null},{"body":"IETF","designation":"RFC 6994","folder":"IETF/RFC-6994","source":"IETF/RFC-6994/RFC-6994.txt","version":null},{"body":"IETF","designation":"RFC 7341","folder":"IETF/RFC-7341","source":"IETF/RFC-7341/RFC-7341.txt","version":null},{"body":"IETF","designation":"RFC 7724","folder":"IETF/RFC-7724","source":"IETF/RFC-7724/RFC-7724.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 951 Network Working Group Bill Croft (Stanford University)\nRequest for Comments: 951 John Gilmore (Sun Microsystems)\n September 1985\n\n BOOTSTRAP PROTOCOL (BOOTP)\n\n1. Status of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n2. Overview\n\n This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows\n a diskless client machine to discover its own IP address, the address\n of a server host, and the name of a file to be loaded into memory and\n executed. The bootstrap operation can be thought of as consisting of\n TWO PHASES. This RFC describes the first phase, which could be\n labeled 'address determination and bootfile selection'. After this\n address and filename information is obtained, control passes to the\n second phase of the bootstrap where a file tran 951 path qualified nested-reference unchanged"},{"id":"IETF RFC 7659","type":"specification","body":"IETF","designation":"RFC 7659","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7659.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7659.txt","https://www.rfc-editor.org/rfc/rfc7659.pdf"],"folder":"IETF/RFC-7659","files":{"txt":{"path":"standards/IETF/RFC-7659/RFC-7659.txt","sha256":"936d336076883d57ddfe7e210bc96c5b2197d041881db0c1e6749414eed04c37"}},"tags":["nested-reference","unchanged"],"summary":"This memo defines a portion of the Management Information Base (MIB)\n for devices implementing the Network Address Translator (NAT)\n function. The new MIB module defined in this document, NATV2-MIB, is\n intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not\n backwards compatible with NAT-MIB, for reasons given in the text of\n this document. A companion document deprecates all objects in NAT-\n MIB. NATV2-MIB can be used for the monitoring of NAT instances on a\n device capable of NAT function. Compliance levels are defined for\n three application scenarios: basic NAT, pooled NAT, and\n carrier-grade NAT (CGN).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Int","scope_keywords":["7659","http","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 7659 This memo defines a portion of the Management Information Base (MIB)\n for devices implementing the Network Address Translator (NAT)\n function. The new MIB module defined in this document, NATV2-MIB, is\n intended to replace module NAT-MIB (RFC 4008). NATV2-MIB is not\n backwards compatible with NAT-MIB, for reasons given in the text of\n this document. A companion document deprecates all objects in NAT-\n MIB. NATV2-MIB can be used for the monitoring of NAT instances on a\n device capable of NAT function. Compliance levels are defined for\n three application scenarios: basic NAT, pooled NAT, and\n carrier-grade NAT (CGN).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Int 7659 http license management subject trust nested-reference unchanged"},{"id":"IETF RFC 906","type":"specification","body":"IETF","designation":"RFC 906","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc906.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc906.txt","https://www.rfc-editor.org/rfc/rfc906.pdf"],"folder":"IETF/RFC-906","files":{"txt":{"path":"standards/IETF/RFC-906/RFC-906.txt","sha256":"8ab070a28a7a6b81ef600d253fcec2eb9d849318d2b6bcc262a71321fc57a349"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ross Finlayson\nRequest for Comments: 906 Stanford University\n June 1984\n\n Bootstrap Loading using TFTP\n\nStatus of this Memo\n\n It is often convenient to be able to bootstrap a computer system from\n a communications network. This RFC proposes the use of the IP TFTP\n protocol for bootstrap loading in this case.\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nIntroduction\n\n Many computer systems, such as diskless workstations, are\n bootstrapped by loading one or more code files across a network.\n Unfortunately, the protocol used to load these initial files has not\n been standardized - numerous methods have been employed by different\n computer manufacturers. This can make it difficult, for example, for\n an installation to support several different kinds of systems on a\n local-area netwo","scope_keywords":["906"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null}],"search_text":"IETF RFC 906 Network Working Group Ross Finlayson\nRequest for Comments: 906 Stanford University\n June 1984\n\n Bootstrap Loading using TFTP\n\nStatus of this Memo\n\n It is often convenient to be able to bootstrap a computer system from\n a communications network. This RFC proposes the use of the IP TFTP\n protocol for bootstrap loading in this case.\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nIntroduction\n\n Many computer systems, such as diskless workstations, are\n bootstrapped by loading one or more code files across a network.\n Unfortunately, the protocol used to load these initial files has not\n been standardized - numerous methods have been employed by different\n computer manufacturers. This can make it difficult, for example, for\n an installation to support several different kinds of systems on a\n local-area netwo 906 nested-reference unchanged"},{"id":"IETF RFC 769","type":"specification","body":"IETF","designation":"RFC 769","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc769.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc769.txt","https://www.rfc-editor.org/rfc/rfc769.pdf"],"folder":"IETF/RFC-769","files":{"txt":{"path":"standards/IETF/RFC-769/RFC-769.txt","sha256":"e6df447631966ef104c73dfc220fc662af78370e10c75340b113de746af23aa0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 769 ISI\n 26 September 1980\n\n Rapicom 450 Facsimile File Format\n ---------------------------------\n\nIntroduction:\n\nSeveral organizations in the ARPA Internet community have RAPICOM 450\nfacsimile machines interfaced to computers. This allows these\norganizations to enter a facsimile representation of a page into a\ncomputer file, and to produce a page from stored facsimile data. These\norganizations can exchange stored facsimile data via file transfer and\nother protocols. The purpose of this note is to document the format\nused for these files so that other organizations with compatible\nfacsimile devices can join in this information exchange procedure.\n\nThe Rapicom 450:\n\nThe Rapicom 450 has a built in encoding/decoding scheme. It produces\ndata blocks of 585 bits. There are \"set up\" blocks and \"data\" blocks.\nThe machine sends/receives severa","scope_keywords":["769","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 798","folder":"IETF/RFC-798","source":"IETF/RFC-798/RFC-798.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 769 Network Working Group J. Postel\nRequest for Comments: 769 ISI\n 26 September 1980\n\n Rapicom 450 Facsimile File Format\n ---------------------------------\n\nIntroduction:\n\nSeveral organizations in the ARPA Internet community have RAPICOM 450\nfacsimile machines interfaced to computers. This allows these\norganizations to enter a facsimile representation of a page into a\ncomputer file, and to produce a page from stored facsimile data. These\norganizations can exchange stored facsimile data via file transfer and\nother protocols. The purpose of this note is to document the format\nused for these files so that other organizations with compatible\nfacsimile devices can join in this information exchange procedure.\n\nThe Rapicom 450:\n\nThe Rapicom 450 has a built in encoding/decoding scheme. It produces\ndata blocks of 585 bits. There are \"set up\" blocks and \"data\" blocks.\nThe machine sends/receives severa 769 presentation nested-reference unchanged"},{"id":"IETF RFC 798","type":"specification","body":"IETF","designation":"RFC 798","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc798.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc798.txt","https://www.rfc-editor.org/rfc/rfc798.pdf"],"folder":"IETF/RFC-798","files":{"txt":{"path":"standards/IETF/RFC-798/RFC-798.txt","sha256":"8050e64f4df44ce388c74390da832a786be52133137e5112c202ffa4e9d10a80"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Katz\nRequest for Comments: 798 ISI\n September 1981\n\n DECODING FACSIMILE DATA FROM THE RAPICOM 450\n\nI. Introduction\n\n This note describes the implementation of a program to decode\n facsimile data from the Rapicom 450 facsimile (fax) machine into an\n ordinary bitmap. This bitmap can then be displayed on other devices\n or edited and then encoded back into the Rapicom 450 format. In\n order to do this, it was necessary to understand the how the\n encoding/decoding process works within the fax machine and to\n duplicate that process in a program. This algorithm is descibed in\n an article by Weber [1] as well as in a memo by Mills [2], however,\n more information than is presented in these papers is necessary to\n successfully decode the data.\n\n The program was written in L10 as a subsystem of NLS running on\n TOPS20. The fax machine is interfaced to TOPS20 as a terminal\n th","scope_keywords":["798","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 798 Network Working Group A. Katz\nRequest for Comments: 798 ISI\n September 1981\n\n DECODING FACSIMILE DATA FROM THE RAPICOM 450\n\nI. Introduction\n\n This note describes the implementation of a program to decode\n facsimile data from the Rapicom 450 facsimile (fax) machine into an\n ordinary bitmap. This bitmap can then be displayed on other devices\n or edited and then encoded back into the Rapicom 450 format. In\n order to do this, it was necessary to understand the how the\n encoding/decoding process works within the fax machine and to\n duplicate that process in a program. This algorithm is descibed in\n an article by Weber [1] as well as in a memo by Mills [2], however,\n more information than is presented in these papers is necessary to\n successfully decode the data.\n\n The program was written in L10 as a subsystem of NLS running on\n TOPS20. The fax machine is interfaced to TOPS20 as a terminal\n th 798 algorithm nested-reference unchanged"},{"id":"IETF RFC 7700","type":"specification","body":"IETF","designation":"RFC 7700","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7700.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7700.txt","https://www.rfc-editor.org/rfc/rfc7700.pdf"],"folder":"IETF/RFC-7700","files":{"txt":{"path":"standards/IETF/RFC-7700/RFC-7700.txt","sha256":"49979e71bbb4c3bf33c373b8511f3334964a34aa6a2c7a1d4a3ad7d45cb7b8dc"}},"tags":["nested-reference","unchanged"],"summary":"This document describes methods for handling Unicode strings\n representing memorable, human-friendly names (called \"nicknames\",\n \"display names\", or \"petnames\") for people, devices, accounts,\n websites, and other entities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7700.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights","scope_keywords":["7700","algorithm","http","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null}],"search_text":"IETF RFC 7700 This document describes methods for handling Unicode strings\n representing memorable, human-friendly names (called \"nicknames\",\n \"display names\", or \"petnames\") for people, devices, accounts,\n websites, and other entities.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7700.\n\nCopyright Notice\n\n Copyright (c) 2015 IETF Trust and the persons identified as the\n document authors. All rights 7700 algorithm http key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 7701","type":"specification","body":"IETF","designation":"RFC 7701","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7701.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7701.txt","https://www.rfc-editor.org/rfc/rfc7701.pdf"],"folder":"IETF/RFC-7701","files":{"txt":{"path":"standards/IETF/RFC-7701/RFC-7701.txt","sha256":"015c558cd96e8c94abea0256656f0af328200efdc851faedfe7a14ec6e136230"}},"tags":["nested-reference","unchanged"],"summary":"The Message Session Relay Protocol (MSRP) defines a mechanism for\n sending instant messages (IMs) within a peer-to-peer session,\n negotiated using the Session Initiation Protocol (SIP) and the\n Session Description Protocol (SDP). This document defines the\n necessary tools for establishing multi-party chat sessions, or chat\n rooms, using MSRP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/","scope_keywords":["7701","attribute","attributes","http","license","management","policy","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8266","folder":"IETF/RFC-8266","source":"IETF/RFC-8266/RFC-8266.txt","version":null}],"search_text":"IETF RFC 7701 The Message Session Relay Protocol (MSRP) defines a mechanism for\n sending instant messages (IMs) within a peer-to-peer session,\n negotiated using the Session Initiation Protocol (SIP) and the\n Session Description Protocol (SDP). This document defines the\n necessary tools for establishing multi-party chat sessions, or chat\n rooms, using MSRP.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/ 7701 attribute attributes http license management policy subject trust nested-reference unchanged"},{"id":"IETF RFC 7728","type":"specification","body":"IETF","designation":"RFC 7728","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7728.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7728.txt","https://www.rfc-editor.org/rfc/rfc7728.pdf"],"folder":"IETF/RFC-7728","files":{"txt":{"path":"standards/IETF/RFC-7728/RFC-7728.txt","sha256":"db80d0729bf601c81a72fbcfcb91729538da2729b98cebaba9528339762e7f2d"}},"tags":["nested-reference","unchanged"],"summary":"With the increased popularity of real-time multimedia applications,\n it is desirable to provide good control of resource usage, and users\n also demand more control over communication sessions. This document\n describes how a receiver in a multimedia conversation can pause and\n resume incoming data from a sender by sending real-time feedback\n messages when using the Real-time Transport Protocol (RTP) for real-\n time data transport. This document extends the Codec Control Message\n (CCM) RTP Control Protocol (RTCP) feedback package by explicitly\n allowing and describing specific use of existing CCMs and adding a\n group of new real-time feedback messages used to pause and resume RTP\n data streams. This document updates RFC 5104.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co","scope_keywords":["7728","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 7728 With the increased popularity of real-time multimedia applications,\n it is desirable to provide good control of resource usage, and users\n also demand more control over communication sessions. This document\n describes how a receiver in a multimedia conversation can pause and\n resume incoming data from a sender by sending real-time feedback\n messages when using the Real-time Transport Protocol (RTP) for real-\n time data transport. This document extends the Codec Control Message\n (CCM) RTP Control Protocol (RTCP) feedback package by explicitly\n allowing and describing specific use of existing CCMs and adding a\n group of new real-time feedback messages used to pause and resume RTP\n data streams. This document updates RFC 5104.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co 7728 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 7741","type":"specification","body":"IETF","designation":"RFC 7741","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7741.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7741.txt","https://www.rfc-editor.org/rfc/rfc7741.pdf"],"folder":"IETF/RFC-7741","files":{"txt":{"path":"standards/IETF/RFC-7741/RFC-7741.txt","sha256":"8016595dc29aed17b056a63918ad226d9abd8bc3e3930445df2a907ef2944594"}},"tags":["nested-reference","unchanged"],"summary":"This memo describes an RTP payload format for the VP8 video codec.\n The payload format has wide applicability, as it supports\n applications from low-bitrate peer-to-peer usage to high-bitrate\n video conferences.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7741.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n","scope_keywords":["7741","algorithm","algorithms","http","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 7741 This memo describes an RTP payload format for the VP8 video codec.\n The payload format has wide applicability, as it supports\n applications from low-bitrate peer-to-peer usage to high-bitrate\n video conferences.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 5741.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc7741.\n\nCopyright Notice\n\n Copyright (c) 2016 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n 7741 algorithm algorithms http key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8411","type":"specification","body":"IETF","designation":"RFC 8411","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8411.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8411.txt","https://www.rfc-editor.org/rfc/rfc8411.pdf"],"folder":"IETF/RFC-8411","files":{"txt":{"path":"standards/IETF/RFC-8411/RFC-8411.txt","sha256":"f10124f2cc25f535ada362bf859c406d9fd99ea6eb119d87d56fe9305446fc96"}},"tags":["nested-reference","unchanged"],"summary":"When the Curdle Security Working Group was chartered, a range of\n object identifiers was donated by DigiCert, Inc. for the purpose of\n registering the Edwards Elliptic Curve key agreement and signature\n algorithms. This donated set of OIDs allowed for shorter values than\n would be possible using the existing S/MIME or PKIX arcs. This\n document describes the donated range and the identifiers that were\n assigned from that range, transfers control of that range to IANA,\n and establishes IANA allocation policies for any future assignments\n within that range.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n In","scope_keywords":["8411","algorithm","algorithms","http","https","key","license","pki","policies","policy","signature","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8410","folder":"IETF/RFC-8410","source":"IETF/RFC-8410/RFC-8410.txt","version":null}],"search_text":"IETF RFC 8411 When the Curdle Security Working Group was chartered, a range of\n object identifiers was donated by DigiCert, Inc. for the purpose of\n registering the Edwards Elliptic Curve key agreement and signature\n algorithms. This donated set of OIDs allowed for shorter values than\n would be possible using the existing S/MIME or PKIX arcs. This\n document describes the donated range and the identifiers that were\n assigned from that range, transfers control of that range to IANA,\n and establishes IANA allocation policies for any future assignments\n within that range.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n In 8411 algorithm algorithms http https key license pki policies policy signature subject trust nested-reference unchanged"},{"id":"IETF RFC 7756","type":"specification","body":"IETF","designation":"RFC 7756","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7756.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7756.txt","https://www.rfc-editor.org/rfc/rfc7756.pdf"],"folder":"IETF/RFC-7756","files":{"txt":{"path":"standards/IETF/RFC-7756/RFC-7756.txt","sha256":"7382632c1ddb6fc4e1860176a18067a0da53685eb1df203257d6bb30677987b6"}},"tags":["nested-reference","unchanged"],"summary":"This document describes an extension of the Stateless IP/ICMP\n Translation for IPv6 Internet Data Center Environments (SIIT-DC)\n architecture, which allows applications, protocols, or nodes that are\n incompatible with IPv6 and/or Network Address Translation to operate\n correctly with SIIT-DC. This is accomplished by introducing a new\n component called an SIIT-DC Edge Relay, which reverses the\n translations made by an SIIT-DC Border Relay. The application and/or\n node is thus provided with seemingly native IPv4 connectivity that\n provides end-to-end address transparency.\n\n The reader is expected to be familiar with the SIIT-DC architecture\n described in RFC 7755.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co","scope_keywords":["7756","http","identification","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7755","folder":"IETF/RFC-7755","source":"IETF/RFC-7755/RFC-7755.txt","version":null}],"search_text":"IETF RFC 7756 This document describes an extension of the Stateless IP/ICMP\n Translation for IPv6 Internet Data Center Environments (SIIT-DC)\n architecture, which allows applications, protocols, or nodes that are\n incompatible with IPv6 and/or Network Address Translation to operate\n correctly with SIIT-DC. This is accomplished by introducing a new\n component called an SIIT-DC Edge Relay, which reverses the\n translations made by an SIIT-DC Border Relay. The application and/or\n node is thus provided with seemingly native IPv4 connectivity that\n provides end-to-end address transparency.\n\n The reader is expected to be familiar with the SIIT-DC architecture\n described in RFC 7755.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the co 7756 http identification license path subject trust nested-reference unchanged"},{"id":"IETF RFC 778","type":"specification","body":"IETF","designation":"RFC 778","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc778.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc778.txt","https://www.rfc-editor.org/rfc/rfc778.pdf"],"folder":"IETF/RFC-778","files":{"txt":{"path":"standards/IETF/RFC-778/RFC-778.txt","sha256":"fac1b762bf49cef8fb2d9368a2d259faefe4cabd870deacd70e74562af2ab024"}},"tags":["nested-reference","unchanged"],"summary":"RFC 778\n\n DCNET Internet Clock Service\n D.L. Mills, COMSAT Laboratories\n 18 April 1981\n\nIntroduction\n\n Following is a description of the Internet Clock\nService (ICS) provided by all DCNET hosts. The service,\nintended primarily for clock synchronization and one-way\ndelay measurements with cooperating internet hosts, is\nprovided using the Timestamp and Timestamp Reply messages of\nthe proposed Internet Control Message Protocol (ICMP). In\naddition, in order to maintain compatability with present\nsystems, this service will be provided for a limited time\nusing the Echo and Echo Reply messages of the\nGateway-Gateway Protocol (GGP).\n It should be understood that ICMP and GGP datagrams are\nnormally considered tightly bound to the Internet Protocol\n(IP) itself and not directly accessable to the user on a\nTOPS-20 system, for example. These datagrams are treated\nsomewhat differently from user datagr","scope_keywords":["778","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0792","folder":"IETF/RFC-0792","source":"IETF/RFC-0792/RFC-0792.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 777","folder":"IETF/RFC-777","source":"IETF/RFC-777/RFC-777.txt","version":null},{"body":"IETF","designation":"RFC 792","folder":"IETF/RFC-792","source":"IETF/RFC-792/RFC-792.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 778 RFC 778\n\n DCNET Internet Clock Service\n D.L. Mills, COMSAT Laboratories\n 18 April 1981\n\nIntroduction\n\n Following is a description of the Internet Clock\nService (ICS) provided by all DCNET hosts. The service,\nintended primarily for clock synchronization and one-way\ndelay measurements with cooperating internet hosts, is\nprovided using the Timestamp and Timestamp Reply messages of\nthe proposed Internet Control Message Protocol (ICMP). In\naddition, in order to maintain compatability with present\nsystems, this service will be provided for a limited time\nusing the Echo and Echo Reply messages of the\nGateway-Gateway Protocol (GGP).\n It should be understood that ICMP and GGP datagrams are\nnormally considered tightly bound to the Internet Protocol\n(IP) itself and not directly accessable to the user on a\nTOPS-20 system, for example. These datagrams are treated\nsomewhat differently from user datagr 778 path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 792","type":"specification","body":"IETF","designation":"RFC 792","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc792.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc792.txt","https://www.rfc-editor.org/rfc/rfc792.pdf"],"folder":"IETF/RFC-792","files":{"txt":{"path":"standards/IETF/RFC-792/RFC-792.txt","sha256":"58714393ded142bacf188d7e8977eef98f4110c4c87ac94595f750df5664c2c6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 792 ISI\n September 1981\nUpdates: RFCs 777, 760\nUpdates: IENs 109, 128\n\n INTERNET CONTROL MESSAGE PROTOCOL\n\n DARPA INTERNET PROGRAM\n PROTOCOL SPECIFICATION\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be imp","scope_keywords":["792","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0791","folder":"IETF/RFC-0791","source":"IETF/RFC-0791/RFC-0791.txt","version":null},{"body":"IETF","designation":"RFC 0792","folder":"IETF/RFC-0792","source":"IETF/RFC-0792/RFC-0792.txt","version":null},{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 0896","folder":"IETF/RFC-0896","source":"IETF/RFC-0896/RFC-0896.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1016","folder":"IETF/RFC-1016","source":"IETF/RFC-1016/RFC-1016.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1241","folder":"IETF/RFC-1241","source":"IETF/RFC-1241/RFC-1241.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1393","folder":"IETF/RFC-1393","source":"IETF/RFC-1393/RFC-1393.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1458","folder":"IETF/RFC-1458","source":"IETF/RFC-1458/RFC-1458.txt","version":null},{"body":"IETF","designation":"RFC 1475","folder":"IETF/RFC-1475","source":"IETF/RFC-1475/RFC-1475.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1788","folder":"IETF/RFC-1788","source":"IETF/RFC-1788/RFC-1788.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1853","folder":"IETF/RFC-1853","source":"IETF/RFC-1853/RFC-1853.txt","version":null},{"body":"IETF","designation":"RFC 1885","folder":"IETF/RFC-1885","source":"IETF/RFC-1885/RFC-1885.txt","version":null},{"body":"IETF","designation":"RFC 1937","folder":"IETF/RFC-1937","source":"IETF/RFC-1937/RFC-1937.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2003","folder":"IETF/RFC-2003","source":"IETF/RFC-2003/RFC-2003.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2201","folder":"IETF/RFC-2201","source":"IETF/RFC-2201/RFC-2201.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2463","folder":"IETF/RFC-2463","source":"IETF/RFC-2463/RFC-2463.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 2765","folder":"IETF/RFC-2765","source":"IETF/RFC-2765/RFC-2765.txt","version":null},{"body":"IETF","designation":"RFC 2780","folder":"IETF/RFC-2780","source":"IETF/RFC-2780/RFC-2780.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 3022","folder":"IETF/RFC-3022","source":"IETF/RFC-3022/RFC-3022.txt","version":null},{"body":"IETF","designation":"RFC 3032","folder":"IETF/RFC-3032","source":"IETF/RFC-3032/RFC-3032.txt","version":null},{"body":"IETF","designation":"RFC 3135","folder":"IETF/RFC-3135","source":"IETF/RFC-3135/RFC-3135.txt","version":null},{"body":"IETF","designation":"RFC 3209","folder":"IETF/RFC-3209","source":"IETF/RFC-3209/RFC-3209.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4008","folder":"IETF/RFC-4008","source":"IETF/RFC-4008/RFC-4008.txt","version":null},{"body":"IETF","designation":"RFC 4023","folder":"IETF/RFC-4023","source":"IETF/RFC-4023/RFC-4023.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4340","folder":"IETF/RFC-4340","source":"IETF/RFC-4340/RFC-4340.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4379","folder":"IETF/RFC-4379","source":"IETF/RFC-4379/RFC-4379.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4443","folder":"IETF/RFC-4443","source":"IETF/RFC-4443/RFC-4443.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4782","folder":"IETF/RFC-4782","source":"IETF/RFC-4782/RFC-4782.txt","version":null},{"body":"IETF","designation":"RFC 4787","folder":"IETF/RFC-4787","source":"IETF/RFC-4787/RFC-4787.txt","version":null},{"body":"IETF","designation":"RFC 4838","folder":"IETF/RFC-4838","source":"IETF/RFC-4838/RFC-4838.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4884","folder":"IETF/RFC-4884","source":"IETF/RFC-4884/RFC-4884.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5085","folder":"IETF/RFC-5085","source":"IETF/RFC-5085/RFC-5085.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5102","folder":"IETF/RFC-5102","source":"IETF/RFC-5102/RFC-5102.txt","version":null},{"body":"IETF","designation":"RFC 5201","folder":"IETF/RFC-5201","source":"IETF/RFC-5201/RFC-5201.txt","version":null},{"body":"IETF","designation":"RFC 5320","folder":"IETF/RFC-5320","source":"IETF/RFC-5320/RFC-5320.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5508","folder":"IETF/RFC-5508","source":"IETF/RFC-5508/RFC-5508.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5665","folder":"IETF/RFC-5665","source":"IETF/RFC-5665/RFC-5665.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6115","folder":"IETF/RFC-6115","source":"IETF/RFC-6115/RFC-6115.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6425","folder":"IETF/RFC-6425","source":"IETF/RFC-6425/RFC-6425.txt","version":null},{"body":"IETF","designation":"RFC 6633","folder":"IETF/RFC-6633","source":"IETF/RFC-6633/RFC-6633.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6951","folder":"IETF/RFC-6951","source":"IETF/RFC-6951/RFC-6951.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7450","folder":"IETF/RFC-7450","source":"IETF/RFC-7450/RFC-7450.txt","version":null},{"body":"IETF","designation":"RFC 7588","folder":"IETF/RFC-7588","source":"IETF/RFC-7588/RFC-7588.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 7658","folder":"IETF/RFC-7658","source":"IETF/RFC-7658/RFC-7658.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 790","folder":"IETF/RFC-790","source":"IETF/RFC-790/RFC-790.txt","version":null},{"body":"IETF","designation":"RFC 791","folder":"IETF/RFC-791","source":"IETF/RFC-791/RFC-791.txt","version":null},{"body":"IETF","designation":"RFC 7990","folder":"IETF/RFC-7990","source":"IETF/RFC-7990/RFC-7990.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 801","folder":"IETF/RFC-801","source":"IETF/RFC-801/RFC-801.txt","version":null},{"body":"IETF","designation":"RFC 8086","folder":"IETF/RFC-8086","source":"IETF/RFC-8086/RFC-8086.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 823","folder":"IETF/RFC-823","source":"IETF/RFC-823/RFC-823.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 8618","folder":"IETF/RFC-8618","source":"IETF/RFC-8618/RFC-8618.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 879","folder":"IETF/RFC-879","source":"IETF/RFC-879/RFC-879.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 887","folder":"IETF/RFC-887","source":"IETF/RFC-887/RFC-887.txt","version":null},{"body":"IETF","designation":"RFC 8899","folder":"IETF/RFC-8899","source":"IETF/RFC-8899/RFC-8899.txt","version":null},{"body":"IETF","designation":"RFC 8900","folder":"IETF/RFC-8900","source":"IETF/RFC-8900/RFC-8900.txt","version":null},{"body":"IETF","designation":"RFC 8926","folder":"IETF/RFC-8926","source":"IETF/RFC-8926/RFC-8926.txt","version":null},{"body":"IETF","designation":"RFC 896","folder":"IETF/RFC-896","source":"IETF/RFC-896/RFC-896.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 792 Network Working Group J. Postel\nRequest for Comments: 792 ISI\n September 1981\nUpdates: RFCs 777, 760\nUpdates: IENs 109, 128\n\n INTERNET CONTROL MESSAGE PROTOCOL\n\n DARPA INTERNET PROGRAM\n PROTOCOL SPECIFICATION\n\nIntroduction\n\n The Internet Protocol (IP) [1] is used for host-to-host datagram\n service in a system of interconnected networks called the\n Catenet [2]. The network connecting devices are called Gateways.\n These gateways communicate between themselves for control purposes\n via a Gateway to Gateway Protocol (GGP) [3,4]. Occasionally a\n gateway or destination host will communicate with a source host, for\n example, to report an error in datagram processing. For such\n purposes this protocol, the Internet Control Message Protocol (ICMP),\n is used. ICMP, uses the basic support of IP as if it were a higher\n level protocol, however, ICMP is actually an integral part of IP, and\n must be imp 792 identification nested-reference unchanged"},{"id":"IETF RFC 7820","type":"specification","body":"IETF","designation":"RFC 7820","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7820.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7820.txt","https://www.rfc-editor.org/rfc/rfc7820.pdf"],"folder":"IETF/RFC-7820","files":{"txt":{"path":"standards/IETF/RFC-7820/RFC-7820.txt","sha256":"2ea04cf1c01348e2470bcaf49a4f7405465f32f33da7f3b4cb4e1b92a362681c"}},"tags":["nested-reference","unchanged"],"summary":"The One-Way Active Measurement Protocol (OWAMP) and the Two-Way\n Active Measurement Protocol (TWAMP) are used for performance\n monitoring in IP networks. Delay measurement is performed in these\n protocols by using timestamped test packets. Some implementations\n use hardware-based timestamping engines that integrate the accurate\n transmission time into every outgoing OWAMP/TWAMP test packet during\n transmission. Since these packets are transported over UDP, the UDP\n Checksum field is then updated to reflect this modification. This\n document proposes to use the last 2 octets of every test packet as a\n Checksum Complement, allowing timestamping engines to reflect the\n checksum modification in the last 2 octets rather than in the UDP\n Checksum field. The behavior defined in this document is completely\n interoperable with existing OWAMP/TWAMP implementations.\n\nStatus of This Memo\n\n This docum","scope_keywords":["7820","authentication","http","license","subject","timestamp","timestamps","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7821","folder":"IETF/RFC-7821","source":"IETF/RFC-7821/RFC-7821.txt","version":null}],"search_text":"IETF RFC 7820 The One-Way Active Measurement Protocol (OWAMP) and the Two-Way\n Active Measurement Protocol (TWAMP) are used for performance\n monitoring in IP networks. Delay measurement is performed in these\n protocols by using timestamped test packets. Some implementations\n use hardware-based timestamping engines that integrate the accurate\n transmission time into every outgoing OWAMP/TWAMP test packet during\n transmission. Since these packets are transported over UDP, the UDP\n Checksum field is then updated to reflect this modification. This\n document proposes to use the last 2 octets of every test packet as a\n Checksum Complement, allowing timestamping engines to reflect the\n checksum modification in the last 2 octets rather than in the UDP\n Checksum field. The behavior defined in this document is completely\n interoperable with existing OWAMP/TWAMP implementations.\n\nStatus of This Memo\n\n This docum 7820 authentication http license subject timestamp timestamps trust nested-reference unchanged"},{"id":"IETF RFC 879","type":"specification","body":"IETF","designation":"RFC 879","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc879.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc879.txt","https://www.rfc-editor.org/rfc/rfc879.pdf"],"folder":"IETF/RFC-879","files":{"txt":{"path":"standards/IETF/RFC-879/RFC-879.txt","sha256":"0e8aefe7e1ac9fac0893f21f3c310b07e4936b88e312498b8b01e5613c476c65"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 879 ISI\n November 1983\n\n The TCP Maximum Segment Size\n and Related Topics\n\nThis memo discusses the TCP Maximum Segment Size Option and related\ntopics. The purposes is to clarify some aspects of TCP and its\ninteraction with IP. This memo is a clarification to the TCP\nspecification, and contains information that may be considered as\n\"advice to implementers\".\n\n1. Introduction\n\n This memo discusses the TCP Maximum Segment Size and its relation to\n the IP Maximum Datagram Size. TCP is specified in reference [1]. IP\n is specified in references [2,3].\n\n This discussion is necessary because the current specification of\n this TCP option is ambiguous.\n\n Much of the difficulty with understanding these sizes and their\n relationship has been due to the variable size of the IP and TCP\n headers.\n\n There have been some assumptions made about using ot","scope_keywords":["879"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1332","folder":"IETF/RFC-1332","source":"IETF/RFC-1332/RFC-1332.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4828","folder":"IETF/RFC-4828","source":"IETF/RFC-4828/RFC-4828.txt","version":null},{"body":"IETF","designation":"RFC 6145","folder":"IETF/RFC-6145","source":"IETF/RFC-6145/RFC-6145.txt","version":null},{"body":"IETF","designation":"RFC 6691","folder":"IETF/RFC-6691","source":"IETF/RFC-6691/RFC-6691.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7597","folder":"IETF/RFC-7597","source":"IETF/RFC-7597/RFC-7597.txt","version":null},{"body":"IETF","designation":"RFC 7599","folder":"IETF/RFC-7599","source":"IETF/RFC-7599/RFC-7599.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 879 Network Working Group J. Postel\nRequest for Comments: 879 ISI\n November 1983\n\n The TCP Maximum Segment Size\n and Related Topics\n\nThis memo discusses the TCP Maximum Segment Size Option and related\ntopics. The purposes is to clarify some aspects of TCP and its\ninteraction with IP. This memo is a clarification to the TCP\nspecification, and contains information that may be considered as\n\"advice to implementers\".\n\n1. Introduction\n\n This memo discusses the TCP Maximum Segment Size and its relation to\n the IP Maximum Datagram Size. TCP is specified in reference [1]. IP\n is specified in references [2,3].\n\n This discussion is necessary because the current specification of\n this TCP option is ambiguous.\n\n Much of the difficulty with understanding these sizes and their\n relationship has been due to the variable size of the IP and TCP\n headers.\n\n There have been some assumptions made about using ot 879 nested-reference unchanged"},{"id":"IETF RFC 8903","type":"specification","body":"IETF","designation":"RFC 8903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8903.txt","https://www.rfc-editor.org/rfc/rfc8903.pdf"],"folder":"IETF/RFC-8903","files":{"pdf":{"path":"standards/IETF/RFC-8903/RFC-8903.pdf","sha256":"4dd20a37ed83c9feafb6d4c245abd3916069b7aebf4cfe212f481286a09b1ffd"},"txt":{"path":"standards/IETF/RFC-8903/RFC-8903.txt","sha256":"9a7bd8f23d78f0ee62a90165dd6f399983f0ec73d45b0429f4712fd00c7c7bc4"}},"tags":["nested-reference","unchanged"],"summary":"The DDoS Open Threat Signaling (DOTS) effort is intended to provide\n protocols to facilitate interoperability across disparate DDoS\n Mitigation solutions. This document presents sample use cases that\n describe the interactions expected between the DOTS components as\n well as DOTS messaging exchanges. These use cases are meant to\n identify the interacting DOTS components, how they collaborate, and\n what the typical information to be exchanged is.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level ","scope_keywords":["8903","http","https","license","path","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9132","folder":"IETF/RFC-9132","source":"IETF/RFC-9132/RFC-9132.txt","version":null}],"search_text":"IETF RFC 8903 The DDoS Open Threat Signaling (DOTS) effort is intended to provide\n protocols to facilitate interoperability across disparate DDoS\n Mitigation solutions. This document presents sample use cases that\n describe the interactions expected between the DOTS components as\n well as DOTS messaging exchanges. These use cases are meant to\n identify the interacting DOTS components, how they collaborate, and\n what the typical information to be exchanged is.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are candidates for any level  8903 http https license path subject trust nested-reference unchanged"},{"id":"IETF RFC 7875","type":"specification","body":"IETF","designation":"RFC 7875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc7875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc7875.txt","https://www.rfc-editor.org/rfc/rfc7875.pdf"],"folder":"IETF/RFC-7875","files":{"txt":{"path":"standards/IETF/RFC-7875/RFC-7875.txt","sha256":"65368a2901e054cea4346dbdf5f9b3503ae860a54ccfd3df26518a1057b14e6a"}},"tags":["nested-reference","unchanged"],"summary":"To ensure a baseline of interoperability between WebRTC endpoints, a\n minimum set of required codecs is specified. However, to maximize\n the possibility of establishing the session without the need for\n audio transcoding, it is also recommended to include in the offer\n other suitable audio codecs that are available to the browser.\n\n This document provides some guidelines on the suitable codecs to be\n considered for WebRTC endpoints to address the use cases most\n relevant to interoperability.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see\n Section ","scope_keywords":["7875","http","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null}],"search_text":"IETF RFC 7875 To ensure a baseline of interoperability between WebRTC endpoints, a\n minimum set of required codecs is specified. However, to maximize\n the possibility of establishing the session without the need for\n audio transcoding, it is also recommended to include in the offer\n other suitable audio codecs that are available to the browser.\n\n This document provides some guidelines on the suitable codecs to be\n considered for WebRTC endpoints to address the use cases most\n relevant to interoperability.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It has been approved for publication by the Internet\n Engineering Steering Group (IESG). Not all documents approved by the\n IESG are a candidate for any level of Internet Standard; see\n Section  7875 http license subject trust nested-reference unchanged"},{"id":"IETF RFC 821","type":"specification","body":"IETF","designation":"RFC 821","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc821.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc821.txt","https://www.rfc-editor.org/rfc/rfc821.pdf"],"folder":"IETF/RFC-821","files":{"txt":{"path":"standards/IETF/RFC-821/RFC-821.txt","sha256":"b7111020e63d77bc84fbcebf8adb0638a1bb0efaeed2e289def743b4fe994882"}},"tags":["nested-reference","unchanged"],"summary":"RFC 821\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1982\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nRFC 821 August 1982\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 11\n 3.5. Opening and Closing ..................................... 13\n 3.6. Relaying .........................","scope_keywords":["821"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0821","folder":"IETF/RFC-0821","source":"IETF/RFC-0821/RFC-0821.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1064","folder":"IETF/RFC-1064","source":"IETF/RFC-1064/RFC-1064.txt","version":null},{"body":"IETF","designation":"RFC 1081","folder":"IETF/RFC-1081","source":"IETF/RFC-1081/RFC-1081.txt","version":null},{"body":"IETF","designation":"RFC 1090","folder":"IETF/RFC-1090","source":"IETF/RFC-1090/RFC-1090.txt","version":null},{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1135","folder":"IETF/RFC-1135","source":"IETF/RFC-1135/RFC-1135.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1175","folder":"IETF/RFC-1175","source":"IETF/RFC-1175/RFC-1175.txt","version":null},{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1204","folder":"IETF/RFC-1204","source":"IETF/RFC-1204/RFC-1204.txt","version":null},{"body":"IETF","designation":"RFC 1208","folder":"IETF/RFC-1208","source":"IETF/RFC-1208/RFC-1208.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1343","folder":"IETF/RFC-1343","source":"IETF/RFC-1343/RFC-1343.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1425","folder":"IETF/RFC-1425","source":"IETF/RFC-1425/RFC-1425.txt","version":null},{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1440","folder":"IETF/RFC-1440","source":"IETF/RFC-1440/RFC-1440.txt","version":null},{"body":"IETF","designation":"RFC 1460","folder":"IETF/RFC-1460","source":"IETF/RFC-1460/RFC-1460.txt","version":null},{"body":"IETF","designation":"RFC 1492","folder":"IETF/RFC-1492","source":"IETF/RFC-1492/RFC-1492.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1524","folder":"IETF/RFC-1524","source":"IETF/RFC-1524/RFC-1524.txt","version":null},{"body":"IETF","designation":"RFC 1568","folder":"IETF/RFC-1568","source":"IETF/RFC-1568/RFC-1568.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1651","folder":"IETF/RFC-1651","source":"IETF/RFC-1651/RFC-1651.txt","version":null},{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1725","folder":"IETF/RFC-1725","source":"IETF/RFC-1725/RFC-1725.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1767","folder":"IETF/RFC-1767","source":"IETF/RFC-1767/RFC-1767.txt","version":null},{"body":"IETF","designation":"RFC 1830","folder":"IETF/RFC-1830","source":"IETF/RFC-1830/RFC-1830.txt","version":null},{"body":"IETF","designation":"RFC 1835","folder":"IETF/RFC-1835","source":"IETF/RFC-1835/RFC-1835.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1846","folder":"IETF/RFC-1846","source":"IETF/RFC-1846/RFC-1846.txt","version":null},{"body":"IETF","designation":"RFC 1854","folder":"IETF/RFC-1854","source":"IETF/RFC-1854/RFC-1854.txt","version":null},{"body":"IETF","designation":"RFC 1869","folder":"IETF/RFC-1869","source":"IETF/RFC-1869/RFC-1869.txt","version":null},{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1893","folder":"IETF/RFC-1893","source":"IETF/RFC-1893/RFC-1893.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 1985","folder":"IETF/RFC-1985","source":"IETF/RFC-1985/RFC-1985.txt","version":null},{"body":"IETF","designation":"RFC 2033","folder":"IETF/RFC-2033","source":"IETF/RFC-2033/RFC-2033.txt","version":null},{"body":"IETF","designation":"RFC 2034","folder":"IETF/RFC-2034","source":"IETF/RFC-2034/RFC-2034.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2197","folder":"IETF/RFC-2197","source":"IETF/RFC-2197/RFC-2197.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2414","folder":"IETF/RFC-2414","source":"IETF/RFC-2414/RFC-2414.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2449","folder":"IETF/RFC-2449","source":"IETF/RFC-2449/RFC-2449.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2486","folder":"IETF/RFC-2486","source":"IETF/RFC-2486/RFC-2486.txt","version":null},{"body":"IETF","designation":"RFC 2487","folder":"IETF/RFC-2487","source":"IETF/RFC-2487/RFC-2487.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2645","folder":"IETF/RFC-2645","source":"IETF/RFC-2645/RFC-2645.txt","version":null},{"body":"IETF","designation":"RFC 2646","folder":"IETF/RFC-2646","source":"IETF/RFC-2646/RFC-2646.txt","version":null},{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2705","folder":"IETF/RFC-2705","source":"IETF/RFC-2705/RFC-2705.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2920","folder":"IETF/RFC-2920","source":"IETF/RFC-2920/RFC-2920.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 2979","folder":"IETF/RFC-2979","source":"IETF/RFC-2979/RFC-2979.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3027","folder":"IETF/RFC-3027","source":"IETF/RFC-3027/RFC-3027.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3207","folder":"IETF/RFC-3207","source":"IETF/RFC-3207/RFC-3207.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3390","folder":"IETF/RFC-3390","source":"IETF/RFC-3390/RFC-3390.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3463","folder":"IETF/RFC-3463","source":"IETF/RFC-3463/RFC-3463.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3848","folder":"IETF/RFC-3848","source":"IETF/RFC-3848/RFC-3848.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 4282","folder":"IETF/RFC-4282","source":"IETF/RFC-4282/RFC-4282.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5068","folder":"IETF/RFC-5068","source":"IETF/RFC-5068/RFC-5068.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 937","folder":"IETF/RFC-937","source":"IETF/RFC-937/RFC-937.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 987","folder":"IETF/RFC-987","source":"IETF/RFC-987/RFC-987.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 821 RFC 821\n \n \n \n \n \n SIMPLE MAIL TRANSFER PROTOCOL\n \n \n \n Jonathan B. Postel\n\n August 1982\n \n \n \n Information Sciences Institute\n University of Southern California\n 4676 Admiralty Way\n Marina del Rey, California 90291\n\n (213) 822-1511\n\f\n\f\n\n \nRFC 821 August 1982\n Simple Mail Transfer Protocol\n\n TABLE OF CONTENTS\n\n 1. INTRODUCTION .................................................. 1\n\n 2. THE SMTP MODEL ................................................ 2\n\n 3. THE SMTP PROCEDURE ............................................ 4\n\n 3.1. Mail ..................................................... 4\n 3.2. Forwarding ............................................... 7\n 3.3. Verifying and Expanding .................................. 8\n 3.4. Sending and Mailing ..................................... 11\n 3.5. Opening and Closing ..................................... 13\n 3.6. Relaying ......................... 821 nested-reference unchanged"},{"id":"IETF RFC 789","type":"specification","body":"IETF","designation":"RFC 789","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc789.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc789.txt","https://www.rfc-editor.org/rfc/rfc789.pdf"],"folder":"IETF/RFC-789","files":{"txt":{"path":"standards/IETF/RFC-789/RFC-789.txt","sha256":"0fe6f4634eb6a799ac559a4432a05dc928d089407020048c8ddd7174c5a4d8d8"}},"tags":["nested-reference","unchanged"],"summary":"RFC 789\n\n Vulnerabilities of Network Control Protocols: An Example\n\n Eric C. Rosen\n\n Bolt Beranek and Newman Inc.\n\f\nRFC 789 Bolt Beranek and Newman Inc.\n Eric C. Rosen\n\n This paper has appeared in the January 1981 edition of the\n\nSIGSOFT Software Engineering Notes, and will soon appear in the\n\nSIGCOMM Computer Communications Review. It is being circulated\n\nas an RFC because it is thought that it may be of interest to a\n\nwider audience, particularly to the internet community. It is a\n\ncase study of a particular kind of problem that can arise in\n\nlarge distributed systems, and of the approach used in the\n\nARPANET to deal with one such problem.\n\n On October 27, 1980, there was an unusual occurrence on the\n\nARPANET. For a period of several hours, the network appeared to\n\nbe unusable, due to what was later diagnosed as a high priority\n\nsoftware process running out of control. Network-wide\n\ndi","scope_keywords":["789","algorithm","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null}],"search_text":"IETF RFC 789 RFC 789\n\n Vulnerabilities of Network Control Protocols: An Example\n\n Eric C. Rosen\n\n Bolt Beranek and Newman Inc.\n\f\nRFC 789 Bolt Beranek and Newman Inc.\n Eric C. Rosen\n\n This paper has appeared in the January 1981 edition of the\n\nSIGSOFT Software Engineering Notes, and will soon appear in the\n\nSIGCOMM Computer Communications Review. It is being circulated\n\nas an RFC because it is thought that it may be of interest to a\n\nwider audience, particularly to the internet community. It is a\n\ncase study of a particular kind of problem that can arise in\n\nlarge distributed systems, and of the approach used in the\n\nARPANET to deal with one such problem.\n\n On October 27, 1980, there was an unusual occurrence on the\n\nARPANET. For a period of several hours, the network appeared to\n\nbe unusable, due to what was later diagnosed as a high priority\n\nsoftware process running out of control. Network-wide\n\ndi 789 algorithm path nested-reference unchanged"},{"id":"IETF RFC 802","type":"specification","body":"IETF","designation":"RFC 802","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc802.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc802.txt","https://www.rfc-editor.org/rfc/rfc802.pdf"],"folder":"IETF/RFC-802","files":{"txt":{"path":"standards/IETF/RFC-802/RFC-802.txt","sha256":"081d5e4f9ca9385e50f28e4fe22ef580b22130fe8d4bde5de63b34f820de78ab"}},"tags":["nested-reference","unchanged"],"summary":"RFC 802: The ARPANET 1822L Host Access Protocol\n\n Andrew G. Malis\n Netmail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n\n November 1981\n\n\f\nRFC 802 Andrew G. Malis\n\n Table of Contents\n\n1 INTRODUCTION.......................................... 1\n2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 4\n2.1 Addresses and Names................................. 6\n2.2 Name Authorization and Effectiveness................ 8\n2.3 Uncontrolled Messages.............................. 14\n2.4 The Short-Blocking Feature......................... 15\n2.4.1 Host Blocking.................................... 16\n2.4.2 Reasons for Host Blockage........................ 19\n2.5 Establishing Host-IMP Communications............... 22\n3 1822L LEADER FORMATS................................. 25\n3.1 Host-to-IMP 1822L Leader Format.................... 26\n3.2 IMP-to-Host 1822L Leader Format.................... 34\n4 REFE","scope_keywords":["802","authorization","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 851","folder":"IETF/RFC-851","source":"IETF/RFC-851/RFC-851.txt","version":null},{"body":"IETF","designation":"RFC 852","folder":"IETF/RFC-852","source":"IETF/RFC-852/RFC-852.txt","version":null}],"search_text":"IETF RFC 802 RFC 802: The ARPANET 1822L Host Access Protocol\n\n Andrew G. Malis\n Netmail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n\n November 1981\n\n\f\nRFC 802 Andrew G. Malis\n\n Table of Contents\n\n1 INTRODUCTION.......................................... 1\n2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 4\n2.1 Addresses and Names................................. 6\n2.2 Name Authorization and Effectiveness................ 8\n2.3 Uncontrolled Messages.............................. 14\n2.4 The Short-Blocking Feature......................... 15\n2.4.1 Host Blocking.................................... 16\n2.4.2 Reasons for Host Blockage........................ 19\n2.5 Establishing Host-IMP Communications............... 22\n3 1822L LEADER FORMATS................................. 25\n3.1 Host-to-IMP 1822L Leader Format.................... 26\n3.2 IMP-to-Host 1822L Leader Format.................... 34\n4 REFE 802 authorization subject nested-reference unchanged"},{"id":"IETF RFC 823","type":"specification","body":"IETF","designation":"RFC 823","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc823.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc823.txt","https://www.rfc-editor.org/rfc/rfc823.pdf"],"folder":"IETF/RFC-823","files":{"txt":{"path":"standards/IETF/RFC-823/RFC-823.txt","sha256":"d92a2bd1f71563c10ed2d75eb51a450ed356f65f31be377491db5268bb64386a"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 823\nObsoletes IEN-30 and IEN-109\n\n THE DARPA INTERNET GATEWAY\n\n RFC 823\n\n Robert Hinden\n Alan Sheltzer\n\n Bolt Beranek and Newman Inc.\n 10 Moulton St.\n Cambridge, Massachusetts 02238\n\n September 1982\n\n Prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\nThis RFC is a status report on the Internet Gateway developed by BBN. It\ndescribes the Internet Gateway as of September 1982. This memo presents\ndetailed descriptions of message formats and gateway procedures, however\nthis is not an implementation specification, and such details are \nsubject to change.\n\n\f\n\n DARPA Internet Gateway September 1982\n RFC 823\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 BACKGROUND............................................ 2\n 3 FORWARDING INTERNET DATAGRA","scope_keywords":["823","algorithm","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 823 Request for Comments: 823\nObsoletes IEN-30 and IEN-109\n\n THE DARPA INTERNET GATEWAY\n\n RFC 823\n\n Robert Hinden\n Alan Sheltzer\n\n Bolt Beranek and Newman Inc.\n 10 Moulton St.\n Cambridge, Massachusetts 02238\n\n September 1982\n\n Prepared for\n\n Defense Advanced Research Projects Agency\n Information Processing Techniques Office\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\nThis RFC is a status report on the Internet Gateway developed by BBN. It\ndescribes the Internet Gateway as of September 1982. This memo presents\ndetailed descriptions of message formats and gateway procedures, however\nthis is not an implementation specification, and such details are \nsubject to change.\n\n\f\n\n DARPA Internet Gateway September 1982\n RFC 823\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 BACKGROUND............................................ 2\n 3 FORWARDING INTERNET DATAGRA 823 algorithm subject nested-reference unchanged"},{"id":"IETF RFC 824","type":"specification","body":"IETF","designation":"RFC 824","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc824.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc824.txt","https://www.rfc-editor.org/rfc/rfc824.pdf"],"folder":"IETF/RFC-824","files":{"txt":{"path":"standards/IETF/RFC-824/RFC-824.txt","sha256":"b53dd64358db42fd2cd0e275daa8efcb2292f8a4497648436d5a2569ba7ab755"}},"tags":["nested-reference","unchanged"],"summary":"DOS-26 Rev A Virtual Local Network\n RFC 824\n\n THE CRONUS VIRTUAL LOCAL NETWORK\n\n William I. MacGregor\n Daniel C. Tappan\n Bolt Beranek and Newman Inc.\n\n 25 August 1982\n\n [The purpose of this note is to describe the CRONUS Virtual\n Local Network, especially the addressing related features.\n These features include a method for mapping between Internet\n Addresses and Local Network addresses. This is a topic of \n current concern in the ARPA Internet community. This note is\n intended to stimulate discussion. This is not a specification\n of an Internet Standard.]\n\n 1 Purpose and Scope\n\n This note defines the Cronus (1) Virtual Local Network\n\n (VLN), a facility which provides interhost message transport to\n\n the Cronus Distributed Operating System. The VLN consists of a\n\n 'client interface specification' and an 'implementation'; the\n\n client interface is expected to be available on every Cronus\n","scope_keywords":["824","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 824 DOS-26 Rev A Virtual Local Network\n RFC 824\n\n THE CRONUS VIRTUAL LOCAL NETWORK\n\n William I. MacGregor\n Daniel C. Tappan\n Bolt Beranek and Newman Inc.\n\n 25 August 1982\n\n [The purpose of this note is to describe the CRONUS Virtual\n Local Network, especially the addressing related features.\n These features include a method for mapping between Internet\n Addresses and Local Network addresses. This is a topic of \n current concern in the ARPA Internet community. This note is\n intended to stimulate discussion. This is not a specification\n of an Internet Standard.]\n\n 1 Purpose and Scope\n\n This note defines the Cronus (1) Virtual Local Network\n\n (VLN), a facility which provides interhost message transport to\n\n the Cronus Distributed Operating System. The VLN consists of a\n\n 'client interface specification' and an 'implementation'; the\n\n client interface is expected to be available on every Cronus\n 824 presentation nested-reference unchanged"},{"id":"IETF RFC 830","type":"specification","body":"IETF","designation":"RFC 830","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc830.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc830.txt","https://www.rfc-editor.org/rfc/rfc830.pdf"],"folder":"IETF/RFC-830","files":{"txt":{"path":"standards/IETF/RFC-830/RFC-830.txt","sha256":"751590751e7baf5b9bd8a09b5efdcd963878faba980c8de449ca75909e5d0e9f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group\nRequest for Comments: 830\n\n A Distributed System for Internet Name Service\n\n by\n Zaw-Sing Su\n\n +-------------------------------------------------------------+ \n | |\n | This RFC proposes a distributed name service for DARPA |\n | Internet. Its purpose is to focus discussion on the |\n | subject. It is hoped that a general consensus will |\n | emerge leading eventually to the adoption of standards. |\n | | \n +-------------------------------------------------------------+\n\n October 1982\n\n SRI International\n 333 Ravenswood Avenue\n Menlo Park, California 94025\n\n (415) 859-4576\n\f\n\f\nRFC 830 October 1982\n\n A Distributed System for Internet Name Service\n\n 1 INTRODUCTION\n\n For many years, the ARPANET Naming Convention \" @ \" has\nserved its user community for its mail system. The substring \" \"\nhas been used for other user applications such as file transfer (FTP)\nand terminal access","scope_keywords":["830","qualified","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null}],"search_text":"IETF RFC 830 Network Working Group\nRequest for Comments: 830\n\n A Distributed System for Internet Name Service\n\n by\n Zaw-Sing Su\n\n +-------------------------------------------------------------+ \n | |\n | This RFC proposes a distributed name service for DARPA |\n | Internet. Its purpose is to focus discussion on the |\n | subject. It is hoped that a general consensus will |\n | emerge leading eventually to the adoption of standards. |\n | | \n +-------------------------------------------------------------+\n\n October 1982\n\n SRI International\n 333 Ravenswood Avenue\n Menlo Park, California 94025\n\n (415) 859-4576\n\f\n\f\nRFC 830 October 1982\n\n A Distributed System for Internet Name Service\n\n 1 INTRODUCTION\n\n For many years, the ARPANET Naming Convention \" @ \" has\nserved its user community for its mail system. The substring \" \"\nhas been used for other user applications such as file transfer (FTP)\nand terminal access 830 qualified subject nested-reference unchanged"},{"id":"IETF RFC 795","type":"specification","body":"IETF","designation":"RFC 795","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc795.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc795.txt","https://www.rfc-editor.org/rfc/rfc795.pdf"],"folder":"IETF/RFC-795","files":{"txt":{"path":"standards/IETF/RFC-795/RFC-795.txt","sha256":"d1ace88ee12e25771fb9b601adf91c4575a6ceeb608840e6b0bd2b7089fd6a38"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 795 ISI\n September 1981\n SERVICE MAPPINGS\n ----------------\n\nThis memo describes the relationship between the Internet\nProtocol (IP) [1] Type of Service and the service parameters of specific\nnetworks.\n\nThe IP Type of Service has the following fields:\n\n Bits 0-2: Precedence.\n Bit 3: 0 = Normal Delay, 1 = Low Delay.\n Bits 4: 0 = Normal Throughput, 1 = High Throughput.\n Bits 5: 0 = Normal Relibility, 1 = High Relibility.\n Bit 6-7: Reserved for Future Use.\n\n 0 1 2 3 4 5 6 7\n +-----+-----+-----+-----+-----+-----+-----+-----+\n | | | | | | |\n | PRECEDENCE | D | T | R | 0 | 0 |\n | | | | | | |\n +-----+-----+-----+-----+-----+-----+-----+-----+\n\n 111 - Network Control\n 110 - Internetwork Control\n 101 - CRITIC/ECP\n 100 - Flash Override\n 011 - Flash\n 010 - Immediate\n 001 - Priority\n 000 - Routine\n\nThe individual networks listed here have very di","scope_keywords":["795"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0791","folder":"IETF/RFC-0791","source":"IETF/RFC-0791/RFC-0791.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 791","folder":"IETF/RFC-791","source":"IETF/RFC-791/RFC-791.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 795 Network Working Group J. Postel\nRequest for Comments: 795 ISI\n September 1981\n SERVICE MAPPINGS\n ----------------\n\nThis memo describes the relationship between the Internet\nProtocol (IP) [1] Type of Service and the service parameters of specific\nnetworks.\n\nThe IP Type of Service has the following fields:\n\n Bits 0-2: Precedence.\n Bit 3: 0 = Normal Delay, 1 = Low Delay.\n Bits 4: 0 = Normal Throughput, 1 = High Throughput.\n Bits 5: 0 = Normal Relibility, 1 = High Relibility.\n Bit 6-7: Reserved for Future Use.\n\n 0 1 2 3 4 5 6 7\n +-----+-----+-----+-----+-----+-----+-----+-----+\n | | | | | | |\n | PRECEDENCE | D | T | R | 0 | 0 |\n | | | | | | |\n +-----+-----+-----+-----+-----+-----+-----+-----+\n\n 111 - Network Control\n 110 - Internetwork Control\n 101 - CRITIC/ECP\n 100 - Flash Override\n 011 - Flash\n 010 - Immediate\n 001 - Priority\n 000 - Routine\n\nThe individual networks listed here have very di 795 nested-reference unchanged"},{"id":"IETF RFC 796","type":"specification","body":"IETF","designation":"RFC 796","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc796.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc796.txt","https://www.rfc-editor.org/rfc/rfc796.pdf"],"folder":"IETF/RFC-796","files":{"txt":{"path":"standards/IETF/RFC-796/RFC-796.txt","sha256":"08498318fcd84578bc0bcdef6d14fe903e337161c9083ecf0a2e3a6e395fcce6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 796 ISI\nReplaces: IEN 115 September 1981\n ADDRESS MAPPINGS\n ----------------\n\nInternet Addresses\n------------------\n\n This memo describes the relationship between address fields used in\n the Internet Protocol (IP) [1] and several specific networks.\n\n An internet address is a 32 bit quantity, with several codings as\n shown below.\n\n The first type (or class a) of address has a 7-bit network number and\n a 24-bit local address.\n\n 1 2 3 \n 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 \n +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\n |0| NETWORK | Local Address |\n +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\n\n Class A Address\n\n The second type (or class b) of address has a 14-bit network number\n and a 16-bit local address.\n\n 1 2 3 \n 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5","scope_keywords":["796","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0791","folder":"IETF/RFC-0791","source":"IETF/RFC-0791/RFC-0791.txt","version":null},{"body":"IETF","designation":"RFC 1005","folder":"IETF/RFC-1005","source":"IETF/RFC-1005/RFC-1005.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 791","folder":"IETF/RFC-791","source":"IETF/RFC-791/RFC-791.txt","version":null},{"body":"IETF","designation":"RFC 810","folder":"IETF/RFC-810","source":"IETF/RFC-810/RFC-810.txt","version":null},{"body":"IETF","designation":"RFC 811","folder":"IETF/RFC-811","source":"IETF/RFC-811/RFC-811.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 878","folder":"IETF/RFC-878","source":"IETF/RFC-878/RFC-878.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 953","folder":"IETF/RFC-953","source":"IETF/RFC-953/RFC-953.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 796 Network Working Group J. Postel\nRequest for Comments: 796 ISI\nReplaces: IEN 115 September 1981\n ADDRESS MAPPINGS\n ----------------\n\nInternet Addresses\n------------------\n\n This memo describes the relationship between address fields used in\n the Internet Protocol (IP) [1] and several specific networks.\n\n An internet address is a 32 bit quantity, with several codings as\n shown below.\n\n The first type (or class a) of address has a 7-bit network number and\n a 24-bit local address.\n\n 1 2 3 \n 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 \n +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\n |0| NETWORK | Local Address |\n +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+\n\n Class A Address\n\n The second type (or class b) of address has a 14-bit network number\n and a 16-bit local address.\n\n 1 2 3 \n 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 796 pid nested-reference unchanged"},{"id":"IETF RFC 908","type":"specification","body":"IETF","designation":"RFC 908","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc908.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc908.txt","https://www.rfc-editor.org/rfc/rfc908.pdf"],"folder":"IETF/RFC-908","files":{"txt":{"path":"standards/IETF/RFC-908/RFC-908.txt","sha256":"3fefba66e845edc49cd1d2b23c0881b2e7cecbf3c749591d666fcef535905b53"}},"tags":["nested-reference","unchanged"],"summary":"Reliable Data Protocol\n\n RFC-908\n\n David Velten\n\n Robert Hinden\n\n Jack Sax\n\n BBN Communications Corporation\n\n July 1984\n\nStatus of This Memo\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n\f\n\f\n\n RDP Specification \n\n Table of Contents\n\n 1 Introduction.......................................... 1\n\n 2 General Description................................... 3\n 2.1 Motivation.......................................... 3\n 2.2 Relation to Other Protocols......................... 5\n\n 3 Protocol Operation.................................... 7\n 3.1 Protocol Service Objectives......................... 7\n 3.2 RDP Connection Management........................... 7\n 3.2.1 Opening a Connection.............................. 8\n 3.2.2 Ports............................................","scope_keywords":["908","algorithm","delivery","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1072","folder":"IETF/RFC-1072","source":"IETF/RFC-1072/RFC-1072.txt","version":null},{"body":"IETF","designation":"RFC 1151","folder":"IETF/RFC-1151","source":"IETF/RFC-1151/RFC-1151.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2757","folder":"IETF/RFC-2757","source":"IETF/RFC-2757/RFC-2757.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 909","folder":"IETF/RFC-909","source":"IETF/RFC-909/RFC-909.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 908 Reliable Data Protocol\n\n RFC-908\n\n David Velten\n\n Robert Hinden\n\n Jack Sax\n\n BBN Communications Corporation\n\n July 1984\n\nStatus of This Memo\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n\f\n\f\n\n RDP Specification \n\n Table of Contents\n\n 1 Introduction.......................................... 1\n\n 2 General Description................................... 3\n 2.1 Motivation.......................................... 3\n 2.2 Relation to Other Protocols......................... 5\n\n 3 Protocol Operation.................................... 7\n 3.1 Protocol Service Objectives......................... 7\n 3.2 RDP Connection Management........................... 7\n 3.2.1 Opening a Connection.............................. 8\n 3.2.2 Ports............................................ 908 algorithm delivery management path nested-reference unchanged"},{"id":"IETF RFC 983","type":"specification","body":"IETF","designation":"RFC 983","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc983.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc983.txt","https://www.rfc-editor.org/rfc/rfc983.pdf"],"folder":"IETF/RFC-983","files":{"txt":{"path":"standards/IETF/RFC-983/RFC-983.txt","sha256":"e32a64f5d4d2286f8b85e03ca16c4b69745a3ed81260ceeb0204537c96452723"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. E. Cass (NRTC)\nRequest for Comments: 983 M. T. Rose (NRTC)\n April 1986\n\n ISO Transport Services on Top of the TCP\n\nStatus of This Memo\n\n This memo describes a proposed protocol standard for the ARPA\n Internet community. The intention is that hosts in the ARPA-Internet\n that choose to implement ISO TSAP services on top of the TCP be\n expected to adopt and implement this standard. Suggestions for\n improvement are encouraged. Distribution of this memo is unlimited.\n\n1. Introduction and Philosophy\n\n The ARPA Internet community has a well-developed, mature set of\n transport and internetwork protocols (TCP/IP), which are quite\n successful in offering network and transport services to end-users.\n The CCITT and the ISO have defined various session, presentation, and\n application recommendations which have been adopted by the\n international community and numerous vendors.","scope_keywords":["983","key","path","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 983 Network Working Group D. E. Cass (NRTC)\nRequest for Comments: 983 M. T. Rose (NRTC)\n April 1986\n\n ISO Transport Services on Top of the TCP\n\nStatus of This Memo\n\n This memo describes a proposed protocol standard for the ARPA\n Internet community. The intention is that hosts in the ARPA-Internet\n that choose to implement ISO TSAP services on top of the TCP be\n expected to adopt and implement this standard. Suggestions for\n improvement are encouraged. Distribution of this memo is unlimited.\n\n1. Introduction and Philosophy\n\n The ARPA Internet community has a well-developed, mature set of\n transport and internetwork protocols (TCP/IP), which are quite\n successful in offering network and transport services to end-users.\n The CCITT and the ISO have defined various session, presentation, and\n application recommendations which have been adopted by the\n international community and numerous vendors. 983 key path presentation nested-reference unchanged"},{"id":"IETF RFC 997","type":"specification","body":"IETF","designation":"RFC 997","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc997.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc997.txt","https://www.rfc-editor.org/rfc/rfc997.pdf"],"folder":"IETF/RFC-997","files":{"txt":{"path":"standards/IETF/RFC-997/RFC-997.txt","sha256":"324f72109807bcd78f529c0a46699c9ef565a921be7142b24c26a0612d006e3f"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Reynolds\nRequest for Comments: 997 J. Postel\n ISI\nObsoletes RFCs: 990, 960, 943, 923, 900, March 1987\n870, 820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the network numbers used in\n the Internet community. Distribution of this memo is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned network numbers and gateway autonomous systems.\n This RFC will be updated periodically, and in any case current\n information can be obtained from Hostmaster.\n\n Hostmaster\n DDN Network Information Center\n SRI International\n 333 Ravenswood Avenue\n Menlo Park, California 94025\n\n Phone: 1-800-235-3155\n\n ARPA mail: HOSTMASTER@SRI-NIC.ARPA\n\n Most of the protocols used in the Internet are documented in t","scope_keywords":["997"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null}],"search_text":"IETF RFC 997 Network Working Group J. Reynolds\nRequest for Comments: 997 J. Postel\n ISI\nObsoletes RFCs: 990, 960, 943, 923, 900, March 1987\n870, 820, 790, 776, 770, 762, 758,\n755, 750, 739, 604, 503, 433, 349\nObsoletes IENs: 127, 117, 93\n\n INTERNET NUMBERS\n\nStatus of this Memo\n\n This memo is an official status report on the network numbers used in\n the Internet community. Distribution of this memo is unlimited.\n\nIntroduction\n\n This Network Working Group Request for Comments documents the\n currently assigned network numbers and gateway autonomous systems.\n This RFC will be updated periodically, and in any case current\n information can be obtained from Hostmaster.\n\n Hostmaster\n DDN Network Information Center\n SRI International\n 333 Ravenswood Avenue\n Menlo Park, California 94025\n\n Phone: 1-800-235-3155\n\n ARPA mail: HOSTMASTER@SRI-NIC.ARPA\n\n Most of the protocols used in the Internet are documented in t 997 nested-reference unchanged"},{"id":"IETF RFC 896","type":"specification","body":"IETF","designation":"RFC 896","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc896.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc896.txt","https://www.rfc-editor.org/rfc/rfc896.pdf"],"folder":"IETF/RFC-896","files":{"txt":{"path":"standards/IETF/RFC-896/RFC-896.txt","sha256":"9f50ffb6d2557be2727bb0f4ca9b5dec9777b3617c66e47822d2ba28df2dfda3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Nagle\nRequest For Comments: 896 6 January 1984\n Ford Aerospace and Communications Corporation\n\n Congestion Control in IP/TCP Internetworks\n\nThis memo discusses some aspects of congestion control in IP/TCP\nInternetworks. It is intended to stimulate thought and further\ndiscussion of this topic. While some specific suggestions are\nmade for improved congestion control implementation, this memo\ndoes not specify any standards.\n\n Introduction\n\nCongestion control is a recognized problem in complex networks.\nWe have discovered that the Department of Defense's Internet Pro-\ntocol (IP) , a pure datagram protocol, and Transmission Control\nProtocol (TCP), a transport layer protocol, when used together,\nare subject to unusual congestion problems caused by interactions\nbetween the transport and datagram layers. In particular, IP\ngateways are vulnerable to a phenomenon we call","scope_keywords":["896","algorithm","algorithms","key","path","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0896","folder":"IETF/RFC-0896","source":"IETF/RFC-0896/RFC-0896.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1016","folder":"IETF/RFC-1016","source":"IETF/RFC-1016/RFC-1016.txt","version":null},{"body":"IETF","designation":"RFC 1072","folder":"IETF/RFC-1072","source":"IETF/RFC-1072/RFC-1072.txt","version":null},{"body":"IETF","designation":"RFC 1254","folder":"IETF/RFC-1254","source":"IETF/RFC-1254/RFC-1254.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2309","folder":"IETF/RFC-2309","source":"IETF/RFC-2309/RFC-2309.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2556","folder":"IETF/RFC-2556","source":"IETF/RFC-2556/RFC-2556.txt","version":null},{"body":"IETF","designation":"RFC 2914","folder":"IETF/RFC-2914","source":"IETF/RFC-2914/RFC-2914.txt","version":null},{"body":"IETF","designation":"RFC 3539","folder":"IETF/RFC-3539","source":"IETF/RFC-3539/RFC-3539.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 4138","folder":"IETF/RFC-4138","source":"IETF/RFC-4138/RFC-4138.txt","version":null},{"body":"IETF","designation":"RFC 4172","folder":"IETF/RFC-4172","source":"IETF/RFC-4172/RFC-4172.txt","version":null},{"body":"IETF","designation":"RFC 4413","folder":"IETF/RFC-4413","source":"IETF/RFC-4413/RFC-4413.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4653","folder":"IETF/RFC-4653","source":"IETF/RFC-4653/RFC-4653.txt","version":null},{"body":"IETF","designation":"RFC 5044","folder":"IETF/RFC-5044","source":"IETF/RFC-5044/RFC-5044.txt","version":null},{"body":"IETF","designation":"RFC 5290","folder":"IETF/RFC-5290","source":"IETF/RFC-5290/RFC-5290.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5682","folder":"IETF/RFC-5682","source":"IETF/RFC-5682/RFC-5682.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 7560","folder":"IETF/RFC-7560","source":"IETF/RFC-7560/RFC-7560.txt","version":null},{"body":"IETF","designation":"RFC 7567","folder":"IETF/RFC-7567","source":"IETF/RFC-7567/RFC-7567.txt","version":null},{"body":"IETF","designation":"RFC 8289","folder":"IETF/RFC-8289","source":"IETF/RFC-8289/RFC-8289.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 896 Network Working Group John Nagle\nRequest For Comments: 896 6 January 1984\n Ford Aerospace and Communications Corporation\n\n Congestion Control in IP/TCP Internetworks\n\nThis memo discusses some aspects of congestion control in IP/TCP\nInternetworks. It is intended to stimulate thought and further\ndiscussion of this topic. While some specific suggestions are\nmade for improved congestion control implementation, this memo\ndoes not specify any standards.\n\n Introduction\n\nCongestion control is a recognized problem in complex networks.\nWe have discovered that the Department of Defense's Internet Pro-\ntocol (IP) , a pure datagram protocol, and Transmission Control\nProtocol (TCP), a transport layer protocol, when used together,\nare subject to unusual congestion problems caused by interactions\nbetween the transport and datagram layers. In particular, IP\ngateways are vulnerable to a phenomenon we call 896 algorithm algorithms key path pid subject nested-reference unchanged"},{"id":"IETF RFC 915","type":"specification","body":"IETF","designation":"RFC 915","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc915.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc915.txt","https://www.rfc-editor.org/rfc/rfc915.pdf"],"folder":"IETF/RFC-915","files":{"txt":{"path":"standards/IETF/RFC-915/RFC-915.txt","sha256":"62cdfab2bc16225129802e0550f48ffdf4ac998f52bf681bbf4a34e8d713ec81"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Marc A. Elvy\nRequest for Comments: 915 Harvard University\n Rudy Nedved\n Carnegie-Mellon University\n December 1984\n\n NETWORK MAIL PATH SERVICE\n\nSTATUS OF THIS MEMO\n\n This RFC proposes a new service for the ARPA-Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nINTRODUCTION\n\n The network mail path service fills the current need of people to\n determine mailbox addresses for hosts that are not part of the\n ARPA-Internet but can be reached by one or more relay hosts that have\n Unix To Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail,\n etc.\n\n Anyone can use the service if they have TCP/TELNET to one of the\n hosts with a mail path server.\n\nDISCUSSION\n\n Currently many hosts that are not connected to the ARPA-Internet\n network can send mail to and receive mail from the ARPA-Internet\n community.","scope_keywords":["915","crl","mdl","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 915 Network Working Group Marc A. Elvy\nRequest for Comments: 915 Harvard University\n Rudy Nedved\n Carnegie-Mellon University\n December 1984\n\n NETWORK MAIL PATH SERVICE\n\nSTATUS OF THIS MEMO\n\n This RFC proposes a new service for the ARPA-Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nINTRODUCTION\n\n The network mail path service fills the current need of people to\n determine mailbox addresses for hosts that are not part of the\n ARPA-Internet but can be reached by one or more relay hosts that have\n Unix To Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail,\n etc.\n\n Anyone can use the service if they have TCP/TELNET to one of the\n hosts with a mail path server.\n\nDISCUSSION\n\n Currently many hosts that are not connected to the ARPA-Internet\n network can send mail to and receive mail from the ARPA-Internet\n community. 915 crl mdl path nested-reference unchanged"},{"id":"IETF RFC 794","type":"specification","body":"IETF","designation":"RFC 794","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc794.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc794.txt","https://www.rfc-editor.org/rfc/rfc794.pdf"],"folder":"IETF/RFC-794","files":{"txt":{"path":"standards/IETF/RFC-794/RFC-794.txt","sha256":"17a662042051c7be549172b980f21e5bb1662b507690485dfa45b578f57c4d45"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group V. Cerf\nRequest for Comments: 794 ARPA\nReplaces: IEN 125 September 1981\n PRE-EMPTION\n\nIn circuit-switching systems, once a user has acquired a circuit, the\ncommunication bandwidth of that circuit is dedicated, even if it is not\nused. When the system saturates, additional circuit set-up requests are\nblocked. To allow high precedence users to gain access to circuit\nresources, systems such as AUTOVON associate a precedence with each\ntelephone instrument. Those instruments with high precedence can\npre-empt circuit resources, causing lower precedence users to be cut\noff.\n\nIn message switching systems such as AUTODIN I, incoming traffic is\nstored on disks (or drums or tape) and processed in order of\nprecedence. If a high precedence message is entered into the system, it\nis processed and forwarded as quickly as possible. When the high\nprecedence message arrives at the dest","scope_keywords":["794"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 794 Network Working Group V. Cerf\nRequest for Comments: 794 ARPA\nReplaces: IEN 125 September 1981\n PRE-EMPTION\n\nIn circuit-switching systems, once a user has acquired a circuit, the\ncommunication bandwidth of that circuit is dedicated, even if it is not\nused. When the system saturates, additional circuit set-up requests are\nblocked. To allow high precedence users to gain access to circuit\nresources, systems such as AUTOVON associate a precedence with each\ntelephone instrument. Those instruments with high precedence can\npre-empt circuit resources, causing lower precedence users to be cut\noff.\n\nIn message switching systems such as AUTODIN I, incoming traffic is\nstored on disks (or drums or tape) and processed in order of\nprecedence. If a high precedence message is entered into the system, it\nis processed and forwarded as quickly as possible. When the high\nprecedence message arrives at the dest 794 nested-reference unchanged"},{"id":"IETF RFC 811","type":"specification","body":"IETF","designation":"RFC 811","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc811.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc811.txt","https://www.rfc-editor.org/rfc/rfc811.pdf"],"folder":"IETF/RFC-811","files":{"txt":{"path":"standards/IETF/RFC-811/RFC-811.txt","sha256":"e41a25e991cfeba24b70ea19a04ced9c407c6b37af52f156e3047dc69216d998"}},"tags":["nested-reference","unchanged"],"summary":"Ken Harrenstien RFC-811\nVic White 1 March 1982\nElizabeth Feinler\nNetwork Information Center\nSRI International\n\n HOSTNAMES SERVER\n\nINTRODUCTION\n\n The NIC Internet Hostnames Server is an NCP/TCP-based host\n information program and protocol running on the SRI-NIC\n machine. It is one of a series of ARPANET/Internet name\n services maintained by the Network Information Center (NIC) at\n SRI International on behalf of the Defense Communications\n Agency (DCA). The function of this particular server is to\n deliver machine-readable name/address information describing\n networks, gateways, hosts, and eventually domains, within the\n internet environment. As currently implemented, the server\n provides the information outlined in the DoD Internet Host\n Table Specification (RFC 810).\n\nQUERY/RESPONSE FORMAT\n\n The name server accepts simple text query requests of the form\n\n [ ]\n\n where square brackets (\"[]","scope_keywords":["811","crl","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 810","folder":"IETF/RFC-810","source":"IETF/RFC-810/RFC-810.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 953","folder":"IETF/RFC-953","source":"IETF/RFC-953/RFC-953.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 811 Ken Harrenstien RFC-811\nVic White 1 March 1982\nElizabeth Feinler\nNetwork Information Center\nSRI International\n\n HOSTNAMES SERVER\n\nINTRODUCTION\n\n The NIC Internet Hostnames Server is an NCP/TCP-based host\n information program and protocol running on the SRI-NIC\n machine. It is one of a series of ARPANET/Internet name\n services maintained by the Network Information Center (NIC) at\n SRI International on behalf of the Defense Communications\n Agency (DCA). The function of this particular server is to\n deliver machine-readable name/address information describing\n networks, gateways, hosts, and eventually domains, within the\n internet environment. As currently implemented, the server\n provides the information outlined in the DoD Internet Host\n Table Specification (RFC 810).\n\nQUERY/RESPONSE FORMAT\n\n The name server accepts simple text query requests of the form\n\n [ ]\n\n where square brackets (\"[] 811 crl key keys nested-reference unchanged"},{"id":"IETF RFC 878","type":"specification","body":"IETF","designation":"RFC 878","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc878.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc878.txt","https://www.rfc-editor.org/rfc/rfc878.pdf"],"folder":"IETF/RFC-878","files":{"txt":{"path":"standards/IETF/RFC-878/RFC-878.txt","sha256":"338361d562af303de386f78febcefe0fbbb0f652377646519cfc579c11c2b36c"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 878\n Obsoletes RFCs: 851, 802\n\n The ARPANET 1822L Host Access Protocol\n\n RFC 878\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n BBN Communications Corp.\n 50 Moulton St.\n Cambridge, MA 02238\n\n December 1983\n\n This RFC specifies the ARPANET 1822L Host Access Protocol, which\n is a successor to the existing 1822 Host Access Protocol. 1822L\n allows ARPANET hosts to use logical names as well as 1822's\n physical port locations to address each other.\n\n\f\n\f\n\n 1822L Host Access Protocol December 1983\n RFC 878\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n\n 2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 3\n 2.1 Addresses and Names................................. 5\n 2.2 Name Translations................................... 7\n 2.2.1 Authorization and Effectiveness................... 7\n 2.2.2 Translation Policies......................","scope_keywords":["878","authorization","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1546","folder":"IETF/RFC-1546","source":"IETF/RFC-1546/RFC-1546.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 878 Request for Comments: 878\n Obsoletes RFCs: 851, 802\n\n The ARPANET 1822L Host Access Protocol\n\n RFC 878\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n BBN Communications Corp.\n 50 Moulton St.\n Cambridge, MA 02238\n\n December 1983\n\n This RFC specifies the ARPANET 1822L Host Access Protocol, which\n is a successor to the existing 1822 Host Access Protocol. 1822L\n allows ARPANET hosts to use logical names as well as 1822's\n physical port locations to address each other.\n\n\f\n\f\n\n 1822L Host Access Protocol December 1983\n RFC 878\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n\n 2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 3\n 2.1 Addresses and Names................................. 5\n 2.2 Name Translations................................... 7\n 2.2.1 Authorization and Effectiveness................... 7\n 2.2.2 Translation Policies...................... 878 authorization policies nested-reference unchanged"},{"id":"IETF RFC 953","type":"specification","body":"IETF","designation":"RFC 953","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc953.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc953.txt","https://www.rfc-editor.org/rfc/rfc953.pdf"],"folder":"IETF/RFC-953","files":{"txt":{"path":"standards/IETF/RFC-953/RFC-953.txt","sha256":"d493e4c3fa6b1c90a447e3e5bfb2cb6ec247ec798e02c24a38e9ca8b21be1e13"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 953 M. Stahl (SRI)\nObsoletes: RFC 811 E. Feinler (SRI)\n October 1985\n\n HOSTNAME SERVER\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the Hostname Server\n Protocol. This edition of the specification includes minor revisions\n to RFC 811 which brings it up to date. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The NIC Internet Hostname Server is a TCP-based host information\n program and protocol running on the SRI-NIC machine. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The function of this particular\n server is to deliver machine-readable name/address information\n describing networks, gateways, hosts, and eventually domains, within\n the internet environment. As ","scope_keywords":["953","crl","key","keys"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 953 Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 953 M. Stahl (SRI)\nObsoletes: RFC 811 E. Feinler (SRI)\n October 1985\n\n HOSTNAME SERVER\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the Hostname Server\n Protocol. This edition of the specification includes minor revisions\n to RFC 811 which brings it up to date. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The NIC Internet Hostname Server is a TCP-based host information\n program and protocol running on the SRI-NIC machine. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The function of this particular\n server is to deliver machine-readable name/address information\n describing networks, gateways, hosts, and eventually domains, within\n the internet environment. As  953 crl key keys nested-reference unchanged"},{"id":"IETF RFC 797","type":"specification","body":"IETF","designation":"RFC 797","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc797.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc797.txt","https://www.rfc-editor.org/rfc/rfc797.pdf"],"folder":"IETF/RFC-797","files":{"txt":{"path":"standards/IETF/RFC-797/RFC-797.txt","sha256":"d8f14ff8716c4c80f683bc384671c4328cc50a98f4f215eb76a1ee792f529fd7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Katz\nRequest for Comments: 797 ISI\n September 1981\n\n FORMAT FOR BITMAP FILES\n\n This note describes a proposed format for storing simple bitmaps (one\n bit per pixel) in a file. These files may be very large and the\n intent is to use this format for short term storage and passing data\n between closely coupled programs. The data in the file should be\n stored in 8-bit bytes (octets). Bitmaps may be any size.\n\n The first 4 octets of the file gives the width of each line (x\n direction), and the next 4 octets should give the number of lines of\n the display (length, y direction). After this is one octet for the x\n increment and one octet for the y increment. Following these 10\n octets is the bitmap itself. The length and width fields are\n stored most significant octet first.\n\n The x and y increment octets tell how much space is between pixels.\n For an ordinary display, b","scope_keywords":["797","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 797 Network Working Group A. Katz\nRequest for Comments: 797 ISI\n September 1981\n\n FORMAT FOR BITMAP FILES\n\n This note describes a proposed format for storing simple bitmaps (one\n bit per pixel) in a file. These files may be very large and the\n intent is to use this format for short term storage and passing data\n between closely coupled programs. The data in the file should be\n stored in 8-bit bytes (octets). Bitmaps may be any size.\n\n The first 4 octets of the file gives the width of each line (x\n direction), and the next 4 octets should give the number of lines of\n the display (length, y direction). After this is one octet for the x\n increment and one octet for the y increment. Following these 10\n octets is the bitmap itself. The length and width fields are\n stored most significant octet first.\n\n The x and y increment octets tell how much space is between pixels.\n For an ordinary display, b 797 presentation nested-reference unchanged"},{"id":"IETF RFC 799","type":"specification","body":"IETF","designation":"RFC 799","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc799.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc799.txt","https://www.rfc-editor.org/rfc/rfc799.pdf"],"folder":"IETF/RFC-799","files":{"txt":{"path":"standards/IETF/RFC-799/RFC-799.txt","sha256":"0e3a09dbf78809b8483cd03dfd6e3eb823801846c9d142e08769d5b71e2f90b6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. L. Mills\nRequest for Comments: 799 COMSAT Laboratories\n September 1981\n\n Internet Name Domains\n\n1. Introduction\n\n In the long run, it will not be practicable for every internet\nhost to include all internet hosts in its name-address tables. Even\nnow, with over four hundred names and nicknames in the combined\nARPANET-DCNET tables, this has become awkward. Some sort of\nhierarchical name-space partitioning can easily be devised to deal\nwith this problem; however, it has been wickedly difficult to find one\ncompatible with the known mail systems throughout the community. The\none proposed here is the product of several discussions and meetings\nand is believed both compatible with existing systems and extensible\nfor future systems involving thousands of hosts.\n\n2. General Topology\n\n We first observe that every internet host is uniquely identified\nby one or more 32-bit in","scope_keywords":["799","delivery","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null}],"search_text":"IETF RFC 799 Network Working Group D. L. Mills\nRequest for Comments: 799 COMSAT Laboratories\n September 1981\n\n Internet Name Domains\n\n1. Introduction\n\n In the long run, it will not be practicable for every internet\nhost to include all internet hosts in its name-address tables. Even\nnow, with over four hundred names and nicknames in the combined\nARPANET-DCNET tables, this has become awkward. Some sort of\nhierarchical name-space partitioning can easily be devised to deal\nwith this problem; however, it has been wickedly difficult to find one\ncompatible with the known mail systems throughout the community. The\none proposed here is the product of several discussions and meetings\nand is believed both compatible with existing systems and extensible\nfor future systems involving thousands of hosts.\n\n2. General Topology\n\n We first observe that every internet host is uniquely identified\nby one or more 32-bit in 799 delivery path nested-reference unchanged"},{"id":"IETF RFC 851","type":"specification","body":"IETF","designation":"RFC 851","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc851.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc851.txt","https://www.rfc-editor.org/rfc/rfc851.pdf"],"folder":"IETF/RFC-851","files":{"txt":{"path":"standards/IETF/RFC-851/RFC-851.txt","sha256":"161b209d4bf950c2b58eb8c80c5d3a72027f2f125f3b7f9fe794c3dccc403be4"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 851\n Obsoletes RFC: 802\n\n The ARPANET 1822L Host Access Protocol\n\n RFC 851\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n 50 Moulton St.\n Cambridge, MA 02238\n\n April 1983\n\n This RFC specifies the ARPANET 1822L Host Access Protocol, which\n is a successor to the existing 1822 Host Access Protocol. 1822L\n allows ARPANET hosts to use logical names as well as 1822's\n physical port locations to address each other. The RFC is also\n being presented as a solicitation of comments on 1822L,\n especially from host network software implementers and\n maintainers.\n\n\f\n\n 1822L Host Access Protocol April 1983\n RFC 851\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 4\n 2.1 Addresses and Names................................. 6\n 2.2 Name Translations...............","scope_keywords":["851","authorization","policies"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 852","folder":"IETF/RFC-852","source":"IETF/RFC-852/RFC-852.txt","version":null},{"body":"IETF","designation":"RFC 878","folder":"IETF/RFC-878","source":"IETF/RFC-878/RFC-878.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 851 Request for Comments: 851\n Obsoletes RFC: 802\n\n The ARPANET 1822L Host Access Protocol\n\n RFC 851\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n 50 Moulton St.\n Cambridge, MA 02238\n\n April 1983\n\n This RFC specifies the ARPANET 1822L Host Access Protocol, which\n is a successor to the existing 1822 Host Access Protocol. 1822L\n allows ARPANET hosts to use logical names as well as 1822's\n physical port locations to address each other. The RFC is also\n being presented as a solicitation of comments on 1822L,\n especially from host network software implementers and\n maintainers.\n\n\f\n\n 1822L Host Access Protocol April 1983\n RFC 851\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 4\n 2.1 Addresses and Names................................. 6\n 2.2 Name Translations............... 851 authorization policies nested-reference unchanged"},{"id":"IETF RFC 852","type":"specification","body":"IETF","designation":"RFC 852","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc852.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc852.txt","https://www.rfc-editor.org/rfc/rfc852.pdf"],"folder":"IETF/RFC-852","files":{"txt":{"path":"standards/IETF/RFC-852/RFC-852.txt","sha256":"f30b16d7e25b3b6e04d749df74c00eeab3ffc7e3c6b9549ad86c237979e01dea"}},"tags":["nested-reference","unchanged"],"summary":"Request for Comments: 852\n\n The ARPANET Short Blocking Feature\n\n RFC 852\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n 50 Moulton St.\n Cambridge, MA 02238\n\n April 1983\n\n This RFC specifies the ARPANET Short Blocking Feature, which will\n allow ARPANET hosts to optionally shorten the IMP's host blocking\n timer. This Feature is a replacement of the ARPANET non-blocking\n host interface, which was never implemented, and will be\n available to hosts using either the 1822 or 1822L Host Access\n Protocol. The RFC is also being presented as a solicitation of\n comments on the Short Blocking Feature, especially from host\n network software implementers and maintainers.\n\n\f\n\n ARPANET Short Blocking Feature April 1983\n RFC 852\n\n 1 INTRODUCTION\n\n This RFC specifies the ARPANET Short Blocking Feature, which will\n\n allow a host to shorten the amount of time that it may be b","scope_keywords":["852","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 851","folder":"IETF/RFC-851","source":"IETF/RFC-851/RFC-851.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 852 Request for Comments: 852\n\n The ARPANET Short Blocking Feature\n\n RFC 852\n\n Andrew G. Malis\n ARPANET Mail: malis@bbn-unix\n\n Bolt Beranek and Newman Inc.\n 50 Moulton St.\n Cambridge, MA 02238\n\n April 1983\n\n This RFC specifies the ARPANET Short Blocking Feature, which will\n allow ARPANET hosts to optionally shorten the IMP's host blocking\n timer. This Feature is a replacement of the ARPANET non-blocking\n host interface, which was never implemented, and will be\n available to hosts using either the 1822 or 1822L Host Access\n Protocol. The RFC is also being presented as a solicitation of\n comments on the Short Blocking Feature, especially from host\n network software implementers and maintainers.\n\n\f\n\n ARPANET Short Blocking Feature April 1983\n RFC 852\n\n 1 INTRODUCTION\n\n This RFC specifies the ARPANET Short Blocking Feature, which will\n\n allow a host to shorten the amount of time that it may be b 852 delivery nested-reference unchanged"},{"id":"IETF RFC 804","type":"specification","body":"IETF","designation":"RFC 804","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc804.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc804.txt","https://www.rfc-editor.org/rfc/rfc804.pdf"],"folder":"IETF/RFC-804","files":{"txt":{"path":"standards/IETF/RFC-804/RFC-804.txt","sha256":"73643147f9279ae301aa6796282c421c98301a99e04ef6be3ee60c38470900d3"}},"tags":["nested-reference","unchanged"],"summary":"RFC 804\n\n CCITT Draft Recommendation T.4\n\n As Defined In: CCITT STUDY GROUP XIV, CONTRIBUTION No.25-E\n\nSOURCE: DRAFTING GROUP ON DRAFT RECOMMENDATION T.4\nTITLE: DRAFT RECOMMENDATION T.4 - STANDARDIZATION OF GROUP 3\n FACSIMILE APPARATUS FOR DOCUMENT TRANSMISSION (as\n amended and agreed by Working Party XIV/2)\n\nDraft Recommendation T.4\n\nSTANDARDIZATION OF GROUP 3 FACSIMILE APPARATUS FOR DOCUMENT\nTRANSMISSION\n\nThe CCITT, considering\n\na. that Recommendation T.2 refers to Group 1 type apparatus\n for ISO A4 document transmission over a telephone-type\n circuit in approximately six minutes;\nb. that Recommendation T.3 refers to Group 2 type apparatus\n for ISO A4 document transmission over a telephone-type\n circuit in approximately three minutes:\nc. that there is a demand for Group 3 apparatus which\n enables an ISO A4 document to be transmitted over a\n telephone-type circuit in approximately one m","scope_keywords":["804","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 804 RFC 804\n\n CCITT Draft Recommendation T.4\n\n As Defined In: CCITT STUDY GROUP XIV, CONTRIBUTION No.25-E\n\nSOURCE: DRAFTING GROUP ON DRAFT RECOMMENDATION T.4\nTITLE: DRAFT RECOMMENDATION T.4 - STANDARDIZATION OF GROUP 3\n FACSIMILE APPARATUS FOR DOCUMENT TRANSMISSION (as\n amended and agreed by Working Party XIV/2)\n\nDraft Recommendation T.4\n\nSTANDARDIZATION OF GROUP 3 FACSIMILE APPARATUS FOR DOCUMENT\nTRANSMISSION\n\nThe CCITT, considering\n\na. that Recommendation T.2 refers to Group 1 type apparatus\n for ISO A4 document transmission over a telephone-type\n circuit in approximately six minutes;\nb. that Recommendation T.3 refers to Group 2 type apparatus\n for ISO A4 document transmission over a telephone-type\n circuit in approximately three minutes:\nc. that there is a demand for Group 3 apparatus which\n enables an ISO A4 document to be transmitted over a\n telephone-type circuit in approximately one m 804 identification nested-reference unchanged"},{"id":"IETF RFC 8045","type":"specification","body":"IETF","designation":"RFC 8045","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8045.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8045.txt","https://www.rfc-editor.org/rfc/rfc8045.pdf"],"folder":"IETF/RFC-8045","files":{"txt":{"path":"standards/IETF/RFC-8045/RFC-8045.txt","sha256":"09d9cf9248967f05e4d33afdf7eb04aa9dbfd31ebeb7a4d7d91e5ed32ae0b3ca"}},"tags":["nested-reference","unchanged"],"summary":"This document defines three new RADIUS attributes. For devices that\n implement IP port ranges, these attributes are used to communicate\n with a RADIUS server in order to configure and report IP transport\n ports as well as mapping behavior for specific hosts. This mechanism\n can be used in various deployment scenarios such as Carrier-Grade\n NAT, IPv4/IPv6 translators, Provider WLAN gateway, etc. This\n document defines a mapping between some RADIUS attributes and IP Flow\n Information Export (IPFIX) Information Element identifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is a","scope_keywords":["8045","attribute","attributes","http","identification","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 8045 This document defines three new RADIUS attributes. For devices that\n implement IP port ranges, these attributes are used to communicate\n with a RADIUS server in order to configure and report IP transport\n ports as well as mapping behavior for specific hosts. This mechanism\n can be used in various deployment scenarios such as Carrier-Grade\n NAT, IPv4/IPv6 translators, Provider WLAN gateway, etc. This\n document defines a mapping between some RADIUS attributes and IP Flow\n Information Export (IPFIX) Information Element identifiers.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is a 8045 attribute attributes http identification license subject trust nested-reference unchanged"},{"id":"IETF RFC 8071","type":"specification","body":"IETF","designation":"RFC 8071","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8071.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8071.txt","https://www.rfc-editor.org/rfc/rfc8071.pdf"],"folder":"IETF/RFC-8071","files":{"txt":{"path":"standards/IETF/RFC-8071/RFC-8071.txt","sha256":"04483ba75eed387701692231cfee3edea55e06bacd4ef9680d977b47c37c0195"}},"tags":["nested-reference","unchanged"],"summary":"This RFC presents NETCONF Call Home and RESTCONF Call Home, which\n enable a NETCONF or RESTCONF server to initiate a secure connection\n to a NETCONF or RESTCONF client, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8071.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to","scope_keywords":["8071","authentication","certificate","http","key","license","management","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 8071 This RFC presents NETCONF Call Home and RESTCONF Call Home, which\n enable a NETCONF or RESTCONF server to initiate a secure connection\n to a NETCONF or RESTCONF client, respectively.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n http://www.rfc-editor.org/info/rfc8071.\n\nCopyright Notice\n\n Copyright (c) 2017 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to 8071 authentication certificate http key license management subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8088","type":"specification","body":"IETF","designation":"RFC 8088","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8088.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8088.txt","https://www.rfc-editor.org/rfc/rfc8088.pdf"],"folder":"IETF/RFC-8088","files":{"txt":{"path":"standards/IETF/RFC-8088/RFC-8088.txt","sha256":"9191ef31f9c2f171cc8eed31c1eba1043ab00acfdba4654ed0faa00630d7423b"}},"tags":["nested-reference","unchanged"],"summary":"This document contains information on how best to write an RTP\n payload format specification. It provides reading tips, design\n practices, and practical tips on how to produce an RTP payload format\n specification quickly and with good results. A template is also\n included with instructions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may","scope_keywords":["8088","algorithm","algorithms","http","license","path","subject","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8088 This document contains information on how best to write an RTP\n payload format specification. It provides reading tips, design\n practices, and practical tips on how to produce an RTP payload format\n specification quickly and with good results. A template is also\n included with instructions.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Not all documents\n approved by the IESG are a candidate for any level of Internet\n Standard; see Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may 8088 algorithm algorithms http license path subject timestamp trust nested-reference unchanged"},{"id":"IETF RFC 952","type":"specification","body":"IETF","designation":"RFC 952","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc952.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc952.txt","https://www.rfc-editor.org/rfc/rfc952.pdf"],"folder":"IETF/RFC-952","files":{"txt":{"path":"standards/IETF/RFC-952/RFC-952.txt","sha256":"fbef98b87d31526430b390ac37f9c6935e84233cdd3a30be8f5a007e1d9be593"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 952 M. Stahl (SRI)\n E. Feinler (SRI)\nObsoletes: RFC 810, 608 October 1985\n\n DOD INTERNET HOST TABLE SPECIFICATION\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the format of the Internet\n Host Table. This edition of the specification includes minor\n revisions to RFC-810 which brings it up to date. Distribution of this\n memo is unlimited.\n\nINTRODUCTION\n\n The DoD Host Table is utilized by the DoD Hostname Server maintained\n by the DDN Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) [See RFC-953].\n\nLOCATION OF THE STANDARD DOD ONLINE HOST TABLE\n\n A machine-translatable ASCII text version of the DoD Host Table is\n online in the file NETINFO:HOSTS.TXT on the SRI-NIC host. It can be\n obtained via FTP from your local host by connecting to host\n SRI-NIC.ARPA (26.0.0.73 or 10","scope_keywords":["952","key","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0952","folder":"IETF/RFC-0952","source":"IETF/RFC-0952/RFC-0952.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1459","folder":"IETF/RFC-1459","source":"IETF/RFC-1459/RFC-1459.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2317","folder":"IETF/RFC-2317","source":"IETF/RFC-2317/RFC-2317.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3492","folder":"IETF/RFC-3492","source":"IETF/RFC-3492/RFC-3492.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 4290","folder":"IETF/RFC-4290","source":"IETF/RFC-4290/RFC-4290.txt","version":null},{"body":"IETF","designation":"RFC 4702","folder":"IETF/RFC-4702","source":"IETF/RFC-4702/RFC-4702.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5890","folder":"IETF/RFC-5890","source":"IETF/RFC-5890/RFC-5890.txt","version":null},{"body":"IETF","designation":"RFC 5894","folder":"IETF/RFC-5894","source":"IETF/RFC-5894/RFC-5894.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6885","folder":"IETF/RFC-6885","source":"IETF/RFC-6885/RFC-6885.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7482","folder":"IETF/RFC-7482","source":"IETF/RFC-7482/RFC-7482.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 8552","folder":"IETF/RFC-8552","source":"IETF/RFC-8552/RFC-8552.txt","version":null},{"body":"IETF","designation":"RFC 9082","folder":"IETF/RFC-9082","source":"IETF/RFC-9082/RFC-9082.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 952 Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 952 M. Stahl (SRI)\n E. Feinler (SRI)\nObsoletes: RFC 810, 608 October 1985\n\n DOD INTERNET HOST TABLE SPECIFICATION\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the format of the Internet\n Host Table. This edition of the specification includes minor\n revisions to RFC-810 which brings it up to date. Distribution of this\n memo is unlimited.\n\nINTRODUCTION\n\n The DoD Host Table is utilized by the DoD Hostname Server maintained\n by the DDN Network Information Center (NIC) on behalf of the Defense\n Communications Agency (DCA) [See RFC-953].\n\nLOCATION OF THE STANDARD DOD ONLINE HOST TABLE\n\n A machine-translatable ASCII text version of the DoD Host Table is\n online in the file NETINFO:HOSTS.TXT on the SRI-NIC host. It can be\n obtained via FTP from your local host by connecting to host\n SRI-NIC.ARPA (26.0.0.73 or 10 952 key registered nested-reference unchanged"},{"id":"IETF RFC 954","type":"specification","body":"IETF","designation":"RFC 954","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc954.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc954.txt","https://www.rfc-editor.org/rfc/rfc954.pdf"],"folder":"IETF/RFC-954","files":{"txt":{"path":"standards/IETF/RFC-954/RFC-954.txt","sha256":"f7a84d312f8e2d2b4f3105f32d7849333b41bd60097a2b534aefaae8483fb8c9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 954 M. Stahl (SRI)\nObsoletes: RFC 812 E. Feinler (SRI)\n October 1985\n\n NICNAME/WHOIS\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the NICNAME/WHOIS protocol.\n This memo describes the protocol and the service. This is an update\n of RFC 812. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is a TCP transaction based query/response\n server, running on the SRI-NIC machine (26.0.0.73 or 10.0.0.51), that\n provides netwide directory service to internet users. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The server is accessible across\n the Internet from user programs running on local hosts, and it\n delivers the full name, U.S. mailing address, te","scope_keywords":["954","crl","registered","risk"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0954","folder":"IETF/RFC-0954","source":"IETF/RFC-0954/RFC-0954.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1609","folder":"IETF/RFC-1609","source":"IETF/RFC-1609/RFC-1609.txt","version":null},{"body":"IETF","designation":"RFC 1714","folder":"IETF/RFC-1714","source":"IETF/RFC-1714/RFC-1714.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1834","folder":"IETF/RFC-1834","source":"IETF/RFC-1834/RFC-1834.txt","version":null},{"body":"IETF","designation":"RFC 1835","folder":"IETF/RFC-1835","source":"IETF/RFC-1835/RFC-1835.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2958","folder":"IETF/RFC-2958","source":"IETF/RFC-2958/RFC-2958.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3707","folder":"IETF/RFC-3707","source":"IETF/RFC-3707/RFC-3707.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3912","folder":"IETF/RFC-3912","source":"IETF/RFC-3912/RFC-3912.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 954 Network Working Group K. Harrenstien (SRI)\nRequest for Comments: 954 M. Stahl (SRI)\nObsoletes: RFC 812 E. Feinler (SRI)\n October 1985\n\n NICNAME/WHOIS\n\nSTATUS OF THIS MEMO\n\n This RFC is the official specification of the NICNAME/WHOIS protocol.\n This memo describes the protocol and the service. This is an update\n of RFC 812. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The NICNAME/WHOIS Server is a TCP transaction based query/response\n server, running on the SRI-NIC machine (26.0.0.73 or 10.0.0.51), that\n provides netwide directory service to internet users. It is one of a\n series of internet name services maintained by the DDN Network\n Information Center (NIC) at SRI International on behalf of the\n Defense Communications Agency (DCA). The server is accessible across\n the Internet from user programs running on local hosts, and it\n delivers the full name, U.S. mailing address, te 954 crl registered risk nested-reference unchanged"},{"id":"IETF RFC 813","type":"specification","body":"IETF","designation":"RFC 813","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc813.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc813.txt","https://www.rfc-editor.org/rfc/rfc813.pdf"],"folder":"IETF/RFC-813","files":{"txt":{"path":"standards/IETF/RFC-813/RFC-813.txt","sha256":"245a5544849581cf930ecb897aaa93e416b6be5da36cd88239cdafa2ff62fde8"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 813\n\n \n WINDOW AND ACKNOWLEDGEMENT STRATEGY IN TCP\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n This document describes implementation strategies to deal with two\n\nmechanisms in TCP, the window and the acknowledgement. These mechanisms\n\nare described in the specification document, but it is possible, while\n\ncomplying with the specification, to produce implementations which yield\n\nvery bad performance. Happily, the pitfalls possible in window and\n\nacknowledgement strategies are very easy to avoid.\n\n It is a much more difficult exercise to verify the performance of a\n\nspecification than the correctness. Certainly, we have less experience\n\nin this area, and we certainly lack any useful formal technique.\n\nNonetheless, it is important to attempt a specification in this area,\n\nbecause different implementor","scope_keywords":["813","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0817","folder":"IETF/RFC-0817","source":"IETF/RFC-0817/RFC-0817.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2525","folder":"IETF/RFC-2525","source":"IETF/RFC-2525/RFC-2525.txt","version":null},{"body":"IETF","designation":"RFC 2581","folder":"IETF/RFC-2581","source":"IETF/RFC-2581/RFC-2581.txt","version":null},{"body":"IETF","designation":"RFC 2923","folder":"IETF/RFC-2923","source":"IETF/RFC-2923/RFC-2923.txt","version":null},{"body":"IETF","designation":"RFC 4460","folder":"IETF/RFC-4460","source":"IETF/RFC-4460/RFC-4460.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4960","folder":"IETF/RFC-4960","source":"IETF/RFC-4960/RFC-4960.txt","version":null},{"body":"IETF","designation":"RFC 5681","folder":"IETF/RFC-5681","source":"IETF/RFC-5681/RFC-5681.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 817","folder":"IETF/RFC-817","source":"IETF/RFC-817/RFC-817.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 813 RFC: 813\n\n \n WINDOW AND ACKNOWLEDGEMENT STRATEGY IN TCP\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n This document describes implementation strategies to deal with two\n\nmechanisms in TCP, the window and the acknowledgement. These mechanisms\n\nare described in the specification document, but it is possible, while\n\ncomplying with the specification, to produce implementations which yield\n\nvery bad performance. Happily, the pitfalls possible in window and\n\nacknowledgement strategies are very easy to avoid.\n\n It is a much more difficult exercise to verify the performance of a\n\nspecification than the correctness. Certainly, we have less experience\n\nin this area, and we certainly lack any useful formal technique.\n\nNonetheless, it is important to attempt a specification in this area,\n\nbecause different implementor 813 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 817","type":"specification","body":"IETF","designation":"RFC 817","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc817.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc817.txt","https://www.rfc-editor.org/rfc/rfc817.pdf"],"folder":"IETF/RFC-817","files":{"txt":{"path":"standards/IETF/RFC-817/RFC-817.txt","sha256":"e615a41efddce03cb66592fd0dd3e0af203a57f8b5b7ca4b7deb82af47d1dbb6"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 817\n\n MODULARITY AND EFFICIENCY IN PROTOCOL IMPLEMENTATION\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Many protocol implementers have made the unpleasant discovery that\n\ntheir packages do not run quite as fast as they had hoped. The blame\n\nfor this widely observed problem has been attributed to a variety of\n\ncauses, ranging from details in the design of the protocol to the\n\nunderlying structure of the host operating system. This RFC will\n\ndiscuss some of the commonly encountered reasons why protocol\n\nimplementations seem to run slowly.\n\n Experience suggests that one of the most important factors in\n\ndetermining the performance of an implementation is the manner in which\n\nthat implementation is modularized and integrated into the host\n\noperating system. For this reason, it is useful to discuss the q","scope_keywords":["817","attribute","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0814","folder":"IETF/RFC-0814","source":"IETF/RFC-0814/RFC-0814.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 814","folder":"IETF/RFC-814","source":"IETF/RFC-814/RFC-814.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 817 RFC: 817\n\n MODULARITY AND EFFICIENCY IN PROTOCOL IMPLEMENTATION\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Many protocol implementers have made the unpleasant discovery that\n\ntheir packages do not run quite as fast as they had hoped. The blame\n\nfor this widely observed problem has been attributed to a variety of\n\ncauses, ranging from details in the design of the protocol to the\n\nunderlying structure of the host operating system. This RFC will\n\ndiscuss some of the commonly encountered reasons why protocol\n\nimplementations seem to run slowly.\n\n Experience suggests that one of the most important factors in\n\ndetermining the performance of an implementation is the manner in which\n\nthat implementation is modularized and integrated into the host\n\noperating system. For this reason, it is useful to discuss the q 817 attribute management path nested-reference unchanged"},{"id":"IETF RFC 814","type":"specification","body":"IETF","designation":"RFC 814","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc814.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc814.txt","https://www.rfc-editor.org/rfc/rfc814.pdf"],"folder":"IETF/RFC-814","files":{"txt":{"path":"standards/IETF/RFC-814/RFC-814.txt","sha256":"6fe70f10aa4df70bcec56bc42935e212a2c06c6e0ce64c578a229c40775afdc5"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 814\n\n NAME, ADDRESSES, PORTS, AND ROUTES\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n It has been said that the principal function of an operating system\n\nis to define a number of different names for the same object, so that it\n\ncan busy itself keeping track of the relationship between all of the\n\ndifferent names. Network protocols seem to have somewhat the same\n\ncharacteristic. In TCP/IP, there are several ways of referring to\n\nthings. At the human visible interface, there are character string\n\n\"names\" to identify networks, hosts, and services. Host names are\n\ntranslated into network \"addresses\", 32-bit values that identify the\n\nnetwork to which a host is attached, and the location of the host on\n\nthat net. Service names are translated into a \"port identifier\", which\n\nin TCP is a 16-bit value. Final","scope_keywords":["814","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0817","folder":"IETF/RFC-0817","source":"IETF/RFC-0817/RFC-0817.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 5595","folder":"IETF/RFC-5595","source":"IETF/RFC-5595/RFC-5595.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 817","folder":"IETF/RFC-817","source":"IETF/RFC-817/RFC-817.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 814 RFC: 814\n\n NAME, ADDRESSES, PORTS, AND ROUTES\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n It has been said that the principal function of an operating system\n\nis to define a number of different names for the same object, so that it\n\ncan busy itself keeping track of the relationship between all of the\n\ndifferent names. Network protocols seem to have somewhat the same\n\ncharacteristic. In TCP/IP, there are several ways of referring to\n\nthings. At the human visible interface, there are character string\n\n\"names\" to identify networks, hosts, and services. Host names are\n\ntranslated into network \"addresses\", 32-bit values that identify the\n\nnetwork to which a host is attached, and the location of the host on\n\nthat net. Service names are translated into a \"port identifier\", which\n\nin TCP is a 16-bit value. Final 814 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 815","type":"specification","body":"IETF","designation":"RFC 815","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc815.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc815.txt","https://www.rfc-editor.org/rfc/rfc815.pdf"],"folder":"IETF/RFC-815","files":{"txt":{"path":"standards/IETF/RFC-815/RFC-815.txt","sha256":"db8097b149042244d0e05e32cbd0718e8e3bf77f70608b4c46e4541abcaea08f"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 815\n\n IP DATAGRAM REASSEMBLY ALGORITHMS\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n One of the mechanisms of IP is fragmentation and reassembly. Under\n\ncertain circumstances, a datagram originally transmitted as a single\n\nunit will arrive at its final destination broken into several fragments.\n\nThe IP layer at the receiving host must accumulate these fragments until\n\nenough have arrived to completely reconstitute the original datagram.\n\nThe specification document for IP gives a complete description of the\n\nreassembly mechanism, and contains several examples. It also provides\n\none possible algorithm for reassembly, based on keeping track of\n\narriving fragments in a vector of bits. This document describes an\n\nalternate approach which should prove more suitable in some machines.\n\n A superficial examina","scope_keywords":["815","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0817","folder":"IETF/RFC-0817","source":"IETF/RFC-0817/RFC-0817.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1858","folder":"IETF/RFC-1858","source":"IETF/RFC-1858/RFC-1858.txt","version":null},{"body":"IETF","designation":"RFC 2011","folder":"IETF/RFC-2011","source":"IETF/RFC-2011/RFC-2011.txt","version":null},{"body":"IETF","designation":"RFC 2465","folder":"IETF/RFC-2465","source":"IETF/RFC-2465/RFC-2465.txt","version":null},{"body":"IETF","designation":"RFC 3511","folder":"IETF/RFC-3511","source":"IETF/RFC-3511/RFC-3511.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 817","folder":"IETF/RFC-817","source":"IETF/RFC-817/RFC-817.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 815 RFC: 815\n\n IP DATAGRAM REASSEMBLY ALGORITHMS\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n One of the mechanisms of IP is fragmentation and reassembly. Under\n\ncertain circumstances, a datagram originally transmitted as a single\n\nunit will arrive at its final destination broken into several fragments.\n\nThe IP layer at the receiving host must accumulate these fragments until\n\nenough have arrived to completely reconstitute the original datagram.\n\nThe specification document for IP gives a complete description of the\n\nreassembly mechanism, and contains several examples. It also provides\n\none possible algorithm for reassembly, based on keeping track of\n\narriving fragments in a vector of bits. This document describes an\n\nalternate approach which should prove more suitable in some machines.\n\n A superficial examina 815 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 816","type":"specification","body":"IETF","designation":"RFC 816","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc816.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc816.txt","https://www.rfc-editor.org/rfc/rfc816.pdf"],"folder":"IETF/RFC-816","files":{"txt":{"path":"standards/IETF/RFC-816/RFC-816.txt","sha256":"3c00723e94de1abb98313c04c1415e0de3c0ae8721d2a2597043f36bce93504f"}},"tags":["nested-reference","unchanged"],"summary":"RFC: 816\n\n FAULT ISOLATION AND RECOVERY\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Occasionally, a network or a gateway will go down, and the sequence\n\nof hops which the packet takes from source to destination must change.\n\nFault isolation is that action which hosts and gateways collectively\n\ntake to determine that something is wrong; fault recovery is the\n\nidentification and selection of an alternative route which will serve to\n\nreconnect the source to the destination. In fact, the gateways perform\n\nmost of the functions of fault isolation and recovery. There are,\n\nhowever, a few actions which hosts must take if they wish to provide a\n\nreasonable level of service. This document describes the portion of\n\nfault isolation and recovery which is the responsibility of the host.\n\n 2. What Gateways Do\n\n Gatewa","scope_keywords":["816","algorithm","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0814","folder":"IETF/RFC-0814","source":"IETF/RFC-0814/RFC-0814.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 4907","folder":"IETF/RFC-4907","source":"IETF/RFC-4907/RFC-4907.txt","version":null},{"body":"IETF","designation":"RFC 5461","folder":"IETF/RFC-5461","source":"IETF/RFC-5461/RFC-5461.txt","version":null},{"body":"IETF","designation":"RFC 5927","folder":"IETF/RFC-5927","source":"IETF/RFC-5927/RFC-5927.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 814","folder":"IETF/RFC-814","source":"IETF/RFC-814/RFC-814.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 816 RFC: 816\n\n FAULT ISOLATION AND RECOVERY\n\n David D. Clark\n MIT Laboratory for Computer Science\n Computer Systems and Communications Group\n July, 1982\n\n 1. Introduction\n\n Occasionally, a network or a gateway will go down, and the sequence\n\nof hops which the packet takes from source to destination must change.\n\nFault isolation is that action which hosts and gateways collectively\n\ntake to determine that something is wrong; fault recovery is the\n\nidentification and selection of an alternative route which will serve to\n\nreconnect the source to the destination. In fact, the gateways perform\n\nmost of the functions of fault isolation and recovery. There are,\n\nhowever, a few actions which hosts must take if they wish to provide a\n\nreasonable level of service. This document describes the portion of\n\nfault isolation and recovery which is the responsibility of the host.\n\n 2. What Gateways Do\n\n Gatewa 816 algorithm identification nested-reference unchanged"},{"id":"IETF RFC 818","type":"specification","body":"IETF","designation":"RFC 818","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc818.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc818.txt","https://www.rfc-editor.org/rfc/rfc818.pdf"],"folder":"IETF/RFC-818","files":{"txt":{"path":"standards/IETF/RFC-818/RFC-818.txt","sha256":"ad423773165d653295fdea5a899b949ffae5404defec33b53b7b9a0ff3d368b1"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 818 ISI\n November 1982\n\n \n\n The Remote User Telnet Service\n\nThis RFC is the specification of an application protocol. Any host that\nimplements this application level service must follow this protocol.\n\nThis RFC was suggested by Mike Mulligan some months ago when he was at\nBBN.\n\nIn the ARPANET Host-to-Host Network Control Protocol (NCP) and in the\nInternet Transmission Control Protocol (TCP) well known sockets or ports\nare used to identify services. The general notion is that there are a\nfew types of services that are distinct and useful enough to use the NCP\nor TCP demultiplexing mechanism directly.\n\nThe most common of these is the Server Telnet which generally speaking\ndefines the network terminal access procedure for a system executive.\nThat is, making a connection to the server Telnet port actually puts the\ncaller in contact with t","scope_keywords":["818","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 818 Network Working Group J. Postel\nRequest for Comments: 818 ISI\n November 1982\n\n \n\n The Remote User Telnet Service\n\nThis RFC is the specification of an application protocol. Any host that\nimplements this application level service must follow this protocol.\n\nThis RFC was suggested by Mike Mulligan some months ago when he was at\nBBN.\n\nIn the ARPANET Host-to-Host Network Control Protocol (NCP) and in the\nInternet Transmission Control Protocol (TCP) well known sockets or ports\nare used to identify services. The general notion is that there are a\nfew types of services that are distinct and useful enough to use the NCP\nor TCP demultiplexing mechanism directly.\n\nThe most common of these is the Server Telnet which generally speaking\ndefines the network terminal access procedure for a system executive.\nThat is, making a connection to the server Telnet port actually puts the\ncaller in contact with t 818 path nested-reference unchanged"},{"id":"IETF RFC 819","type":"specification","body":"IETF","designation":"RFC 819","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc819.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc819.txt","https://www.rfc-editor.org/rfc/rfc819.pdf"],"folder":"IETF/RFC-819","files":{"txt":{"path":"standards/IETF/RFC-819/RFC-819.txt","sha256":"0e7845df0cb460e2831d916d8df3dd3d385b937540551f176607160672b1689e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Zaw-Sing Su (SRI)\nRequest for Comments: 819 Jon Postel (ISI)\n August 1982\n\n The Domain Naming Convention for Internet User Applications\n\n1. Introduction\n\n For many years, the naming convention \" @ \" has served the\n ARPANET user community for its mail system, and the substring\n \" \" has been used for other applications such as file transfer\n (FTP) and terminal access (Telnet). With the advent of network\n interconnection, this naming convention needs to be generalized to\n accommodate internetworking. A decision has recently been reached to\n replace the simple name field, \" \", by a composite name field,\n \" \" [2]. This note is an attempt to clarify this generalized\n naming convention, the Internet Naming Convention, and to explore the\n implications of its adoption for Internet name service and user\n applications.\n\n The following example illustrates the changes in naming ","scope_keywords":["819","presentation","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0819","folder":"IETF/RFC-0819","source":"IETF/RFC-0819/RFC-0819.txt","version":null},{"body":"IETF","designation":"RFC 0882","folder":"IETF/RFC-0882","source":"IETF/RFC-0882/RFC-0882.txt","version":null},{"body":"IETF","designation":"RFC 0883","folder":"IETF/RFC-0883","source":"IETF/RFC-0883/RFC-0883.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 7719","folder":"IETF/RFC-7719","source":"IETF/RFC-7719/RFC-7719.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 830","folder":"IETF/RFC-830","source":"IETF/RFC-830/RFC-830.txt","version":null},{"body":"IETF","designation":"RFC 8499","folder":"IETF/RFC-8499","source":"IETF/RFC-8499/RFC-8499.txt","version":null},{"body":"IETF","designation":"RFC 882","folder":"IETF/RFC-882","source":"IETF/RFC-882/RFC-882.txt","version":null},{"body":"IETF","designation":"RFC 883","folder":"IETF/RFC-883","source":"IETF/RFC-883/RFC-883.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 9499","folder":"IETF/RFC-9499","source":"IETF/RFC-9499/RFC-9499.txt","version":null}],"search_text":"IETF RFC 819 Network Working Group Zaw-Sing Su (SRI)\nRequest for Comments: 819 Jon Postel (ISI)\n August 1982\n\n The Domain Naming Convention for Internet User Applications\n\n1. Introduction\n\n For many years, the naming convention \" @ \" has served the\n ARPANET user community for its mail system, and the substring\n \" \" has been used for other applications such as file transfer\n (FTP) and terminal access (Telnet). With the advent of network\n interconnection, this naming convention needs to be generalized to\n accommodate internetworking. A decision has recently been reached to\n replace the simple name field, \" \", by a composite name field,\n \" \" [2]. This note is an attempt to clarify this generalized\n naming convention, the Internet Naming Convention, and to explore the\n implications of its adoption for Internet name service and user\n applications.\n\n The following example illustrates the changes in naming  819 presentation subject nested-reference unchanged"},{"id":"IETF RFC 937","type":"specification","body":"IETF","designation":"RFC 937","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc937.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc937.txt","https://www.rfc-editor.org/rfc/rfc937.pdf"],"folder":"IETF/RFC-937","files":{"txt":{"path":"standards/IETF/RFC-937/RFC-937.txt","sha256":"a4aa8f5368ef5fba2b4a4bbd28e469e3ae09aa764a95fcd13d6ecd2a246c4814"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. Butler\nRequest for Comments: 937 J. Postel\n D. Chase\n J. Goldberger\n J. K. Reynolds\nObsoletes: RFC 918 ISI\n February 1985\n\n POST OFFICE PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvement. This memo is a revision of RFC 918.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Post Office Protocol Version 2 (POP2) is to allow a\n user's workstation to access mail from a mailbox server. It is\n expected that mail will be posted from the workstation to the mailbox\n server via the Simple Mail Transfer Protocol (SMTP). For further\n information see RFC-821 [1] and RFC-822 [2].\n\n This protocol assumes a reliable data stream such ","scope_keywords":["937","authorization","crl","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1064","folder":"IETF/RFC-1064","source":"IETF/RFC-1064/RFC-1064.txt","version":null},{"body":"IETF","designation":"RFC 1081","folder":"IETF/RFC-1081","source":"IETF/RFC-1081/RFC-1081.txt","version":null},{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 937 Network Working Group M. Butler\nRequest for Comments: 937 J. Postel\n D. Chase\n J. Goldberger\n J. K. Reynolds\nObsoletes: RFC 918 ISI\n February 1985\n\n POST OFFICE PROTOCOL - VERSION 2\n\nStatus of this Memo\n\n This RFC suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvement. This memo is a revision of RFC 918.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The intent of the Post Office Protocol Version 2 (POP2) is to allow a\n user's workstation to access mail from a mailbox server. It is\n expected that mail will be posted from the workstation to the mailbox\n server via the Simple Mail Transfer Protocol (SMTP). For further\n information see RFC-821 [1] and RFC-822 [2].\n\n This protocol assumes a reliable data stream such  937 authorization crl subject nested-reference unchanged"},{"id":"IETF RFC 987","type":"specification","body":"IETF","designation":"RFC 987","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc987.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc987.txt","https://www.rfc-editor.org/rfc/rfc987.pdf"],"folder":"IETF/RFC-987","files":{"txt":{"path":"standards/IETF/RFC-987/RFC-987.txt","sha256":"962f263f94062eb6bcef163506b97e22d8718e17b0f66c3d6370b74ffda4099f"}},"tags":["nested-reference","unchanged"],"summary":"UCL Technical Report 120\nMailgroup Note 19\n\nNetwork Working Group S.E. Kille\nRequest for Comments: 987 University College London\n June 1986\n\n Mapping between X.400 and RFC 822\n\nStatus of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This document describes a set of mappings which will enable\n interworking between systems operating the CCITT X.400 (1984) series\n of protocols [CCITT84a], and systems using the RFC 822 mail protocol\n [Crocker82a], or protocols derived from RFC 822. The approach aims\n to maximise the services offered across the boundary, whilst not\n requiring unduly complex mappings. The mappings should not require\n any changes to end systems.\n\n This specification should be used when this mapping is performed on\n the ARPA-Internet or in th","scope_keywords":["987","profile","profiles","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1026","folder":"IETF/RFC-1026","source":"IETF/RFC-1026/RFC-1026.txt","version":null},{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1137","folder":"IETF/RFC-1137","source":"IETF/RFC-1137/RFC-1137.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1274","folder":"IETF/RFC-1274","source":"IETF/RFC-1274/RFC-1274.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1405","folder":"IETF/RFC-1405","source":"IETF/RFC-1405/RFC-1405.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"IETF RFC 987 UCL Technical Report 120\nMailgroup Note 19\n\nNetwork Working Group S.E. Kille\nRequest for Comments: 987 University College London\n June 1986\n\n Mapping between X.400 and RFC 822\n\nStatus of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This document describes a set of mappings which will enable\n interworking between systems operating the CCITT X.400 (1984) series\n of protocols [CCITT84a], and systems using the RFC 822 mail protocol\n [Crocker82a], or protocols derived from RFC 822. The approach aims\n to maximise the services offered across the boundary, whilst not\n requiring unduly complex mappings. The mappings should not require\n any changes to end systems.\n\n This specification should be used when this mapping is performed on\n the ARPA-Internet or in th 987 profile profiles subject nested-reference unchanged"},{"id":"IETF RFC 822","type":"specification","body":"IETF","designation":"RFC 822","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc822.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc822.txt","https://www.rfc-editor.org/rfc/rfc822.pdf"],"folder":"IETF/RFC-822","files":{"txt":{"path":"standards/IETF/RFC-822/RFC-822.txt","sha256":"1e7bc6c75e4c6866c54cbf26ae280b96cac9e87d6293db5a21d7aaf4ffb8bc1a"}},"tags":["nested-reference","unchanged"],"summary":"RFC # 822\n\n Obsoletes: RFC #733 (NIC #41952)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA INTERNET TEXT MESSAGES\n\n August 13, 1982\n\n Revised by\n\n David H. Crocker\n\n Dept. of Electrical Engineering\n University of Delaware, Newark, DE 19711\n Network: DCrocker @ UDel-Relay\n\n\f\n\n \n Standard for ARPA Internet Text Messages\n\n TABLE OF CONTENTS\n\n PREFACE .................................................... ii\n\n 1. INTRODUCTION ........................................... 1\n\n 1.1. Scope ............................................ 1\n 1.2. Communication Framework .......................... 2\n\n 2. NOTATIONAL CONVENTIONS ................................. 3\n\n 3. LEXICAL ANALYSIS OF MESSAGES ........................... 5\n\n 3.1. General Description .............................. 5\n 3.2. Header Field Definitions ......................... 9\n 3.3. Lexical Tokens ................................... 10\n 3.4. Clarific","scope_keywords":["822","delivery","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0821","folder":"IETF/RFC-0821","source":"IETF/RFC-0821/RFC-0821.txt","version":null},{"body":"IETF","designation":"RFC 0850","folder":"IETF/RFC-0850","source":"IETF/RFC-0850/RFC-0850.txt","version":null},{"body":"IETF","designation":"RFC 0989","folder":"IETF/RFC-0989","source":"IETF/RFC-0989/RFC-0989.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1064","folder":"IETF/RFC-1064","source":"IETF/RFC-1064/RFC-1064.txt","version":null},{"body":"IETF","designation":"RFC 1081","folder":"IETF/RFC-1081","source":"IETF/RFC-1081/RFC-1081.txt","version":null},{"body":"IETF","designation":"RFC 1120","folder":"IETF/RFC-1120","source":"IETF/RFC-1120/RFC-1120.txt","version":null},{"body":"IETF","designation":"RFC 1123","folder":"IETF/RFC-1123","source":"IETF/RFC-1123/RFC-1123.txt","version":null},{"body":"IETF","designation":"RFC 1137","folder":"IETF/RFC-1137","source":"IETF/RFC-1137/RFC-1137.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1140","folder":"IETF/RFC-1140","source":"IETF/RFC-1140/RFC-1140.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1153","folder":"IETF/RFC-1153","source":"IETF/RFC-1153/RFC-1153.txt","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1176","folder":"IETF/RFC-1176","source":"IETF/RFC-1176/RFC-1176.txt","version":null},{"body":"IETF","designation":"RFC 1203","folder":"IETF/RFC-1203","source":"IETF/RFC-1203/RFC-1203.txt","version":null},{"body":"IETF","designation":"RFC 1208","folder":"IETF/RFC-1208","source":"IETF/RFC-1208/RFC-1208.txt","version":null},{"body":"IETF","designation":"RFC 1211","folder":"IETF/RFC-1211","source":"IETF/RFC-1211/RFC-1211.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null},{"body":"IETF","designation":"RFC 1274","folder":"IETF/RFC-1274","source":"IETF/RFC-1274/RFC-1274.txt","version":null},{"body":"IETF","designation":"RFC 1279","folder":"IETF/RFC-1279","source":"IETF/RFC-1279/RFC-1279.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1328","folder":"IETF/RFC-1328","source":"IETF/RFC-1328/RFC-1328.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1342","folder":"IETF/RFC-1342","source":"IETF/RFC-1342/RFC-1342.txt","version":null},{"body":"IETF","designation":"RFC 1343","folder":"IETF/RFC-1343","source":"IETF/RFC-1343/RFC-1343.txt","version":null},{"body":"IETF","designation":"RFC 1344","folder":"IETF/RFC-1344","source":"IETF/RFC-1344/RFC-1344.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1405","folder":"IETF/RFC-1405","source":"IETF/RFC-1405/RFC-1405.txt","version":null},{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1424","folder":"IETF/RFC-1424","source":"IETF/RFC-1424/RFC-1424.txt","version":null},{"body":"IETF","designation":"RFC 1425","folder":"IETF/RFC-1425","source":"IETF/RFC-1425/RFC-1425.txt","version":null},{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1460","folder":"IETF/RFC-1460","source":"IETF/RFC-1460/RFC-1460.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null},{"body":"IETF","designation":"RFC 1485","folder":"IETF/RFC-1485","source":"IETF/RFC-1485/RFC-1485.txt","version":null},{"body":"IETF","designation":"RFC 1486","folder":"IETF/RFC-1486","source":"IETF/RFC-1486/RFC-1486.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1522","folder":"IETF/RFC-1522","source":"IETF/RFC-1522/RFC-1522.txt","version":null},{"body":"IETF","designation":"RFC 1524","folder":"IETF/RFC-1524","source":"IETF/RFC-1524/RFC-1524.txt","version":null},{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 1557","folder":"IETF/RFC-1557","source":"IETF/RFC-1557/RFC-1557.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1630","folder":"IETF/RFC-1630","source":"IETF/RFC-1630/RFC-1630.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1648","folder":"IETF/RFC-1648","source":"IETF/RFC-1648/RFC-1648.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1651","folder":"IETF/RFC-1651","source":"IETF/RFC-1651/RFC-1651.txt","version":null},{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1685","folder":"IETF/RFC-1685","source":"IETF/RFC-1685/RFC-1685.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1725","folder":"IETF/RFC-1725","source":"IETF/RFC-1725/RFC-1725.txt","version":null},{"body":"IETF","designation":"RFC 1730","folder":"IETF/RFC-1730","source":"IETF/RFC-1730/RFC-1730.txt","version":null},{"body":"IETF","designation":"RFC 1732","folder":"IETF/RFC-1732","source":"IETF/RFC-1732/RFC-1732.txt","version":null},{"body":"IETF","designation":"RFC 1733","folder":"IETF/RFC-1733","source":"IETF/RFC-1733/RFC-1733.txt","version":null},{"body":"IETF","designation":"RFC 1734","folder":"IETF/RFC-1734","source":"IETF/RFC-1734/RFC-1734.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1766","folder":"IETF/RFC-1766","source":"IETF/RFC-1766/RFC-1766.txt","version":null},{"body":"IETF","designation":"RFC 1767","folder":"IETF/RFC-1767","source":"IETF/RFC-1767/RFC-1767.txt","version":null},{"body":"IETF","designation":"RFC 1779","folder":"IETF/RFC-1779","source":"IETF/RFC-1779/RFC-1779.txt","version":null},{"body":"IETF","designation":"RFC 1786","folder":"IETF/RFC-1786","source":"IETF/RFC-1786/RFC-1786.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 1806","folder":"IETF/RFC-1806","source":"IETF/RFC-1806/RFC-1806.txt","version":null},{"body":"IETF","designation":"RFC 1808","folder":"IETF/RFC-1808","source":"IETF/RFC-1808/RFC-1808.txt","version":null},{"body":"IETF","designation":"RFC 1830","folder":"IETF/RFC-1830","source":"IETF/RFC-1830/RFC-1830.txt","version":null},{"body":"IETF","designation":"RFC 1834","folder":"IETF/RFC-1834","source":"IETF/RFC-1834/RFC-1834.txt","version":null},{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null},{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1847","folder":"IETF/RFC-1847","source":"IETF/RFC-1847/RFC-1847.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 1864","folder":"IETF/RFC-1864","source":"IETF/RFC-1864/RFC-1864.txt","version":null},{"body":"IETF","designation":"RFC 1869","folder":"IETF/RFC-1869","source":"IETF/RFC-1869/RFC-1869.txt","version":null},{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1872","folder":"IETF/RFC-1872","source":"IETF/RFC-1872/RFC-1872.txt","version":null},{"body":"IETF","designation":"RFC 1873","folder":"IETF/RFC-1873","source":"IETF/RFC-1873/RFC-1873.txt","version":null},{"body":"IETF","designation":"RFC 1889","folder":"IETF/RFC-1889","source":"IETF/RFC-1889/RFC-1889.txt","version":null},{"body":"IETF","designation":"RFC 1891","folder":"IETF/RFC-1891","source":"IETF/RFC-1891/RFC-1891.txt","version":null},{"body":"IETF","designation":"RFC 1892","folder":"IETF/RFC-1892","source":"IETF/RFC-1892/RFC-1892.txt","version":null},{"body":"IETF","designation":"RFC 1894","folder":"IETF/RFC-1894","source":"IETF/RFC-1894/RFC-1894.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 1920","folder":"IETF/RFC-1920","source":"IETF/RFC-1920/RFC-1920.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1939","folder":"IETF/RFC-1939","source":"IETF/RFC-1939/RFC-1939.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2007","folder":"IETF/RFC-2007","source":"IETF/RFC-2007/RFC-2007.txt","version":null},{"body":"IETF","designation":"RFC 2017","folder":"IETF/RFC-2017","source":"IETF/RFC-2017/RFC-2017.txt","version":null},{"body":"IETF","designation":"RFC 2034","folder":"IETF/RFC-2034","source":"IETF/RFC-2034/RFC-2034.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2060","folder":"IETF/RFC-2060","source":"IETF/RFC-2060/RFC-2060.txt","version":null},{"body":"IETF","designation":"RFC 2062","folder":"IETF/RFC-2062","source":"IETF/RFC-2062/RFC-2062.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2079","folder":"IETF/RFC-2079","source":"IETF/RFC-2079/RFC-2079.txt","version":null},{"body":"IETF","designation":"RFC 2086","folder":"IETF/RFC-2086","source":"IETF/RFC-2086/RFC-2086.txt","version":null},{"body":"IETF","designation":"RFC 2087","folder":"IETF/RFC-2087","source":"IETF/RFC-2087/RFC-2087.txt","version":null},{"body":"IETF","designation":"RFC 2088","folder":"IETF/RFC-2088","source":"IETF/RFC-2088/RFC-2088.txt","version":null},{"body":"IETF","designation":"RFC 2095","folder":"IETF/RFC-2095","source":"IETF/RFC-2095/RFC-2095.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2111","folder":"IETF/RFC-2111","source":"IETF/RFC-2111/RFC-2111.txt","version":null},{"body":"IETF","designation":"RFC 2112","folder":"IETF/RFC-2112","source":"IETF/RFC-2112/RFC-2112.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2160","folder":"IETF/RFC-2160","source":"IETF/RFC-2160/RFC-2160.txt","version":null},{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2164","folder":"IETF/RFC-2164","source":"IETF/RFC-2164/RFC-2164.txt","version":null},{"body":"IETF","designation":"RFC 2167","folder":"IETF/RFC-2167","source":"IETF/RFC-2167/RFC-2167.txt","version":null},{"body":"IETF","designation":"RFC 2168","folder":"IETF/RFC-2168","source":"IETF/RFC-2168/RFC-2168.txt","version":null},{"body":"IETF","designation":"RFC 2180","folder":"IETF/RFC-2180","source":"IETF/RFC-2180/RFC-2180.txt","version":null},{"body":"IETF","designation":"RFC 2183","folder":"IETF/RFC-2183","source":"IETF/RFC-2183/RFC-2183.txt","version":null},{"body":"IETF","designation":"RFC 2184","folder":"IETF/RFC-2184","source":"IETF/RFC-2184/RFC-2184.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2193","folder":"IETF/RFC-2193","source":"IETF/RFC-2193/RFC-2193.txt","version":null},{"body":"IETF","designation":"RFC 2195","folder":"IETF/RFC-2195","source":"IETF/RFC-2195/RFC-2195.txt","version":null},{"body":"IETF","designation":"RFC 2200","folder":"IETF/RFC-2200","source":"IETF/RFC-2200/RFC-2200.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null},{"body":"IETF","designation":"RFC 2231","folder":"IETF/RFC-2231","source":"IETF/RFC-2231/RFC-2231.txt","version":null},{"body":"IETF","designation":"RFC 2234","folder":"IETF/RFC-2234","source":"IETF/RFC-2234/RFC-2234.txt","version":null},{"body":"IETF","designation":"RFC 2243","folder":"IETF/RFC-2243","source":"IETF/RFC-2243/RFC-2243.txt","version":null},{"body":"IETF","designation":"RFC 2245","folder":"IETF/RFC-2245","source":"IETF/RFC-2245/RFC-2245.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2253","folder":"IETF/RFC-2253","source":"IETF/RFC-2253/RFC-2253.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2280","folder":"IETF/RFC-2280","source":"IETF/RFC-2280/RFC-2280.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 2298","folder":"IETF/RFC-2298","source":"IETF/RFC-2298/RFC-2298.txt","version":null},{"body":"IETF","designation":"RFC 2303","folder":"IETF/RFC-2303","source":"IETF/RFC-2303/RFC-2303.txt","version":null},{"body":"IETF","designation":"RFC 2304","folder":"IETF/RFC-2304","source":"IETF/RFC-2304/RFC-2304.txt","version":null},{"body":"IETF","designation":"RFC 2305","folder":"IETF/RFC-2305","source":"IETF/RFC-2305/RFC-2305.txt","version":null},{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2359","folder":"IETF/RFC-2359","source":"IETF/RFC-2359/RFC-2359.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2368","folder":"IETF/RFC-2368","source":"IETF/RFC-2368/RFC-2368.txt","version":null},{"body":"IETF","designation":"RFC 2369","folder":"IETF/RFC-2369","source":"IETF/RFC-2369/RFC-2369.txt","version":null},{"body":"IETF","designation":"RFC 2377","folder":"IETF/RFC-2377","source":"IETF/RFC-2377/RFC-2377.txt","version":null},{"body":"IETF","designation":"RFC 2387","folder":"IETF/RFC-2387","source":"IETF/RFC-2387/RFC-2387.txt","version":null},{"body":"IETF","designation":"RFC 2392","folder":"IETF/RFC-2392","source":"IETF/RFC-2392/RFC-2392.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2423","folder":"IETF/RFC-2423","source":"IETF/RFC-2423/RFC-2423.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2442","folder":"IETF/RFC-2442","source":"IETF/RFC-2442/RFC-2442.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2447","folder":"IETF/RFC-2447","source":"IETF/RFC-2447/RFC-2447.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2479","folder":"IETF/RFC-2479","source":"IETF/RFC-2479/RFC-2479.txt","version":null},{"body":"IETF","designation":"RFC 2480","folder":"IETF/RFC-2480","source":"IETF/RFC-2480/RFC-2480.txt","version":null},{"body":"IETF","designation":"RFC 2505","folder":"IETF/RFC-2505","source":"IETF/RFC-2505/RFC-2505.txt","version":null},{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2538","folder":"IETF/RFC-2538","source":"IETF/RFC-2538/RFC-2538.txt","version":null},{"body":"IETF","designation":"RFC 2542","folder":"IETF/RFC-2542","source":"IETF/RFC-2542/RFC-2542.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2554","folder":"IETF/RFC-2554","source":"IETF/RFC-2554/RFC-2554.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2622","folder":"IETF/RFC-2622","source":"IETF/RFC-2622/RFC-2622.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2635","folder":"IETF/RFC-2635","source":"IETF/RFC-2635/RFC-2635.txt","version":null},{"body":"IETF","designation":"RFC 2652","folder":"IETF/RFC-2652","source":"IETF/RFC-2652/RFC-2652.txt","version":null},{"body":"IETF","designation":"RFC 2654","folder":"IETF/RFC-2654","source":"IETF/RFC-2654/RFC-2654.txt","version":null},{"body":"IETF","designation":"RFC 2660","folder":"IETF/RFC-2660","source":"IETF/RFC-2660/RFC-2660.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 2692","folder":"IETF/RFC-2692","source":"IETF/RFC-2692/RFC-2692.txt","version":null},{"body":"IETF","designation":"RFC 2704","folder":"IETF/RFC-2704","source":"IETF/RFC-2704/RFC-2704.txt","version":null},{"body":"IETF","designation":"RFC 2725","folder":"IETF/RFC-2725","source":"IETF/RFC-2725/RFC-2725.txt","version":null},{"body":"IETF","designation":"RFC 2774","folder":"IETF/RFC-2774","source":"IETF/RFC-2774/RFC-2774.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2825","folder":"IETF/RFC-2825","source":"IETF/RFC-2825/RFC-2825.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2846","folder":"IETF/RFC-2846","source":"IETF/RFC-2846/RFC-2846.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2912","folder":"IETF/RFC-2912","source":"IETF/RFC-2912/RFC-2912.txt","version":null},{"body":"IETF","designation":"RFC 2919","folder":"IETF/RFC-2919","source":"IETF/RFC-2919/RFC-2919.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2971","folder":"IETF/RFC-2971","source":"IETF/RFC-2971/RFC-2971.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3030","folder":"IETF/RFC-3030","source":"IETF/RFC-3030/RFC-3030.txt","version":null},{"body":"IETF","designation":"RFC 3050","folder":"IETF/RFC-3050","source":"IETF/RFC-3050/RFC-3050.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3156","folder":"IETF/RFC-3156","source":"IETF/RFC-3156/RFC-3156.txt","version":null},{"body":"IETF","designation":"RFC 3191","folder":"IETF/RFC-3191","source":"IETF/RFC-3191/RFC-3191.txt","version":null},{"body":"IETF","designation":"RFC 3192","folder":"IETF/RFC-3192","source":"IETF/RFC-3192/RFC-3192.txt","version":null},{"body":"IETF","designation":"RFC 3249","folder":"IETF/RFC-3249","source":"IETF/RFC-3249/RFC-3249.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 3297","folder":"IETF/RFC-3297","source":"IETF/RFC-3297/RFC-3297.txt","version":null},{"body":"IETF","designation":"RFC 3335","folder":"IETF/RFC-3335","source":"IETF/RFC-3335/RFC-3335.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3459","folder":"IETF/RFC-3459","source":"IETF/RFC-3459/RFC-3459.txt","version":null},{"body":"IETF","designation":"RFC 3461","folder":"IETF/RFC-3461","source":"IETF/RFC-3461/RFC-3461.txt","version":null},{"body":"IETF","designation":"RFC 3462","folder":"IETF/RFC-3462","source":"IETF/RFC-3462/RFC-3462.txt","version":null},{"body":"IETF","designation":"RFC 3464","folder":"IETF/RFC-3464","source":"IETF/RFC-3464/RFC-3464.txt","version":null},{"body":"IETF","designation":"RFC 3501","folder":"IETF/RFC-3501","source":"IETF/RFC-3501/RFC-3501.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3798","folder":"IETF/RFC-3798","source":"IETF/RFC-3798/RFC-3798.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null},{"body":"IETF","designation":"RFC 3834","folder":"IETF/RFC-3834","source":"IETF/RFC-3834/RFC-3834.txt","version":null},{"body":"IETF","designation":"RFC 3851","folder":"IETF/RFC-3851","source":"IETF/RFC-3851/RFC-3851.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 3864","folder":"IETF/RFC-3864","source":"IETF/RFC-3864/RFC-3864.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3886","folder":"IETF/RFC-3886","source":"IETF/RFC-3886/RFC-3886.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3888","folder":"IETF/RFC-3888","source":"IETF/RFC-3888/RFC-3888.txt","version":null},{"body":"IETF","designation":"RFC 3965","folder":"IETF/RFC-3965","source":"IETF/RFC-3965/RFC-3965.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4234","folder":"IETF/RFC-4234","source":"IETF/RFC-4234/RFC-4234.txt","version":null},{"body":"IETF","designation":"RFC 4250","folder":"IETF/RFC-4250","source":"IETF/RFC-4250/RFC-4250.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4301","folder":"IETF/RFC-4301","source":"IETF/RFC-4301/RFC-4301.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4356","folder":"IETF/RFC-4356","source":"IETF/RFC-4356/RFC-4356.txt","version":null},{"body":"IETF","designation":"RFC 4405","folder":"IETF/RFC-4405","source":"IETF/RFC-4405/RFC-4405.txt","version":null},{"body":"IETF","designation":"RFC 4406","folder":"IETF/RFC-4406","source":"IETF/RFC-4406/RFC-4406.txt","version":null},{"body":"IETF","designation":"RFC 4407","folder":"IETF/RFC-4407","source":"IETF/RFC-4407/RFC-4407.txt","version":null},{"body":"IETF","designation":"RFC 4408","folder":"IETF/RFC-4408","source":"IETF/RFC-4408/RFC-4408.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4549","folder":"IETF/RFC-4549","source":"IETF/RFC-4549/RFC-4549.txt","version":null},{"body":"IETF","designation":"RFC 4683","folder":"IETF/RFC-4683","source":"IETF/RFC-4683/RFC-4683.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4718","folder":"IETF/RFC-4718","source":"IETF/RFC-4718/RFC-4718.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4809","folder":"IETF/RFC-4809","source":"IETF/RFC-4809/RFC-4809.txt","version":null},{"body":"IETF","designation":"RFC 4823","folder":"IETF/RFC-4823","source":"IETF/RFC-4823/RFC-4823.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 4877","folder":"IETF/RFC-4877","source":"IETF/RFC-4877/RFC-4877.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 5064","folder":"IETF/RFC-5064","source":"IETF/RFC-5064/RFC-5064.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5182","folder":"IETF/RFC-5182","source":"IETF/RFC-5182/RFC-5182.txt","version":null},{"body":"IETF","designation":"RFC 5234","folder":"IETF/RFC-5234","source":"IETF/RFC-5234/RFC-5234.txt","version":null},{"body":"IETF","designation":"RFC 5259","folder":"IETF/RFC-5259","source":"IETF/RFC-5259/RFC-5259.txt","version":null},{"body":"IETF","designation":"RFC 5293","folder":"IETF/RFC-5293","source":"IETF/RFC-5293/RFC-5293.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5322","folder":"IETF/RFC-5322","source":"IETF/RFC-5322/RFC-5322.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5374","folder":"IETF/RFC-5374","source":"IETF/RFC-5374/RFC-5374.txt","version":null},{"body":"IETF","designation":"RFC 5387","folder":"IETF/RFC-5387","source":"IETF/RFC-5387/RFC-5387.txt","version":null},{"body":"IETF","designation":"RFC 5451","folder":"IETF/RFC-5451","source":"IETF/RFC-5451/RFC-5451.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5598","folder":"IETF/RFC-5598","source":"IETF/RFC-5598/RFC-5598.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5901","folder":"IETF/RFC-5901","source":"IETF/RFC-5901/RFC-5901.txt","version":null},{"body":"IETF","designation":"RFC 5965","folder":"IETF/RFC-5965","source":"IETF/RFC-5965/RFC-5965.txt","version":null},{"body":"IETF","designation":"RFC 5996","folder":"IETF/RFC-5996","source":"IETF/RFC-5996/RFC-5996.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6430","folder":"IETF/RFC-6430","source":"IETF/RFC-6430/RFC-6430.txt","version":null},{"body":"IETF","designation":"RFC 6449","folder":"IETF/RFC-6449","source":"IETF/RFC-6449/RFC-6449.txt","version":null},{"body":"IETF","designation":"RFC 6522","folder":"IETF/RFC-6522","source":"IETF/RFC-6522/RFC-6522.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6591","folder":"IETF/RFC-6591","source":"IETF/RFC-6591/RFC-6591.txt","version":null},{"body":"IETF","designation":"RFC 6648","folder":"IETF/RFC-6648","source":"IETF/RFC-6648/RFC-6648.txt","version":null},{"body":"IETF","designation":"RFC 6709","folder":"IETF/RFC-6709","source":"IETF/RFC-6709/RFC-6709.txt","version":null},{"body":"IETF","designation":"RFC 6854","folder":"IETF/RFC-6854","source":"IETF/RFC-6854/RFC-6854.txt","version":null},{"body":"IETF","designation":"RFC 6858","folder":"IETF/RFC-6858","source":"IETF/RFC-6858/RFC-6858.txt","version":null},{"body":"IETF","designation":"RFC 7001","folder":"IETF/RFC-7001","source":"IETF/RFC-7001/RFC-7001.txt","version":null},{"body":"IETF","designation":"RFC 7296","folder":"IETF/RFC-7296","source":"IETF/RFC-7296/RFC-7296.txt","version":null},{"body":"IETF","designation":"RFC 7407","folder":"IETF/RFC-7407","source":"IETF/RFC-7407/RFC-7407.txt","version":null},{"body":"IETF","designation":"RFC 7589","folder":"IETF/RFC-7589","source":"IETF/RFC-7589/RFC-7589.txt","version":null},{"body":"IETF","designation":"RFC 800","folder":"IETF/RFC-800","source":"IETF/RFC-800/RFC-800.txt","version":null},{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 821","folder":"IETF/RFC-821","source":"IETF/RFC-821/RFC-821.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 8438","folder":"IETF/RFC-8438","source":"IETF/RFC-8438/RFC-8438.txt","version":null},{"body":"IETF","designation":"RFC 8474","folder":"IETF/RFC-8474","source":"IETF/RFC-8474/RFC-8474.txt","version":null},{"body":"IETF","designation":"RFC 850","folder":"IETF/RFC-850","source":"IETF/RFC-850/RFC-850.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 937","folder":"IETF/RFC-937","source":"IETF/RFC-937/RFC-937.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 987","folder":"IETF/RFC-987","source":"IETF/RFC-987/RFC-987.txt","version":null},{"body":"IETF","designation":"RFC 989","folder":"IETF/RFC-989","source":"IETF/RFC-989/RFC-989.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 822 RFC # 822\n\n Obsoletes: RFC #733 (NIC #41952)\n\n STANDARD FOR THE FORMAT OF\n\n ARPA INTERNET TEXT MESSAGES\n\n August 13, 1982\n\n Revised by\n\n David H. Crocker\n\n Dept. of Electrical Engineering\n University of Delaware, Newark, DE 19711\n Network: DCrocker @ UDel-Relay\n\n\f\n\n \n Standard for ARPA Internet Text Messages\n\n TABLE OF CONTENTS\n\n PREFACE .................................................... ii\n\n 1. INTRODUCTION ........................................... 1\n\n 1.1. Scope ............................................ 1\n 1.2. Communication Framework .......................... 2\n\n 2. NOTATIONAL CONVENTIONS ................................. 3\n\n 3. LEXICAL ANALYSIS OF MESSAGES ........................... 5\n\n 3.1. General Description .............................. 5\n 3.2. Header Field Definitions ......................... 9\n 3.3. Lexical Tokens ................................... 10\n 3.4. Clarific 822 delivery presentation nested-reference unchanged"},{"id":"IETF RFC 850","type":"specification","body":"IETF","designation":"RFC 850","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc850.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc850.txt","https://www.rfc-editor.org/rfc/rfc850.pdf"],"folder":"IETF/RFC-850","files":{"txt":{"path":"standards/IETF/RFC-850/RFC-850.txt","sha256":"660c5d88cb473d80ebd768e43cb554386ed96ea4c427099c1c5efb551534bd19"}},"tags":["nested-reference","unchanged"],"summary":"RFC 850 June 1983\n\n Standard for Interchange of USENET Messages\n\n Mark R. Horton\n\n[ This memo is distributed as an RFC only to make this\ninformation easily accessible to researchers in the ARPA\ncommunity. It does not specify an Internet standard. ] \n\n1. Introduction\n\nThis document defines the standard format for interchange\nof Network News articles among USENET sites. It describes\nthe format for articles themselves, and gives partial\nstandards for transmission of news. The news transmission\nis not entirely standardized in order to give a good deal\nof flexibility to the individual hosts to choose\ntransmission hardware and software, whether to batch news,\nand so on.\n\nThere are five sections to this document. Section two\nsection defines the format. Section three defines the\nvalid control messages. Section four specifies some valid\ntransmission methods. Section five describes the overall\nnew","scope_keywords":["850","algorithm","key","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0850","folder":"IETF/RFC-0850","source":"IETF/RFC-0850/RFC-0850.txt","version":null},{"body":"IETF","designation":"RFC 0977","folder":"IETF/RFC-0977","source":"IETF/RFC-0977/RFC-0977.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 5536","folder":"IETF/RFC-5536","source":"IETF/RFC-5536/RFC-5536.txt","version":null},{"body":"IETF","designation":"RFC 7231","folder":"IETF/RFC-7231","source":"IETF/RFC-7231/RFC-7231.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.txt","version":null},{"body":"IETF","designation":"RFC 977","folder":"IETF/RFC-977","source":"IETF/RFC-977/RFC-977.txt","version":null}],"search_text":"IETF RFC 850 RFC 850 June 1983\n\n Standard for Interchange of USENET Messages\n\n Mark R. Horton\n\n[ This memo is distributed as an RFC only to make this\ninformation easily accessible to researchers in the ARPA\ncommunity. It does not specify an Internet standard. ] \n\n1. Introduction\n\nThis document defines the standard format for interchange\nof Network News articles among USENET sites. It describes\nthe format for articles themselves, and gives partial\nstandards for transmission of news. The news transmission\nis not entirely standardized in order to give a good deal\nof flexibility to the individual hosts to choose\ntransmission hardware and software, whether to batch news,\nand so on.\n\nThere are five sections to this document. Section two\nsection defines the format. Section three defines the\nvalid control messages. Section four specifies some valid\ntransmission methods. Section five describes the overall\nnew 850 algorithm key path subject nested-reference unchanged"},{"id":"IETF RFC 989","type":"specification","body":"IETF","designation":"RFC 989","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc989.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc989.txt","https://www.rfc-editor.org/rfc/rfc989.pdf"],"folder":"IETF/RFC-989","files":{"txt":{"path":"standards/IETF/RFC-989/RFC-989.txt","sha256":"9dbf7ba8ff2f2bfe3cb4837d1dffd54798a6cf39f2cb765a68d0b5f876bfce4e"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group John Linn (BBNCC)\nRequest for Comments: 989 IAB Privacy Task Force\n February 1987\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Matt Bishop, Danny Cohen, Tom Daniel, Charles Fox, Morrie\n Gasser, Steve Kent (chairman), John Laws, Steve Lipner, Dan Nessett,\n Mike Padlipsky,","scope_keywords":["989","attribute","attributes","authentication","encryption","key","keys","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0989","folder":"IETF/RFC-0989","source":"IETF/RFC-0989/RFC-0989.txt","version":null},{"body":"IETF","designation":"RFC 5585","folder":"IETF/RFC-5585","source":"IETF/RFC-5585/RFC-5585.txt","version":null}],"search_text":"IETF RFC 989 Network Working Group John Linn (BBNCC)\nRequest for Comments: 989 IAB Privacy Task Force\n February 1987\n\n Privacy Enhancement for Internet Electronic Mail:\n Part I: Message Encipherment and Authentication Procedures\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the Internet community and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\nACKNOWLEDGMENT\n\n This RFC is the outgrowth of a series of IAB Privacy Task Force\n meetings and of internal working papers distributed for those\n meetings. I would like to thank the following Privacy Task Force\n members and meeting guests for their comments and contributions at\n the meetings which led to the preparation of this RFC: David\n Balenson, Matt Bishop, Danny Cohen, Tom Daniel, Charles Fox, Morrie\n Gasser, Steve Kent (chairman), John Laws, Steve Lipner, Dan Nessett,\n Mike Padlipsky, 989 attribute attributes authentication encryption key keys management nested-reference unchanged"},{"id":"IETF RFC 826","type":"specification","body":"IETF","designation":"RFC 826","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc826.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc826.txt","https://www.rfc-editor.org/rfc/rfc826.pdf"],"folder":"IETF/RFC-826","files":{"txt":{"path":"standards/IETF/RFC-826/RFC-826.txt","sha256":"01bc62fe6a37e90f1246ac43e8e145f1322b4ed1474836145c3da93d2bd3c8a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David C. Plummer \nRequest For Comments: 826 (DCP@MIT-MC)\n November 1982\n\n An Ethernet Address Resolution Protocol\n -- or --\n Converting Network Protocol Addresses\n to 48.bit Ethernet Address\n for Transmission on\n Ethernet Hardware\n\n Abstract\n\nThe implementation of protocol P on a sending host S decides,\nthrough protocol P's routing mechanism, that it wants to transmit\nto a target host T located some place on a connected piece of\n10Mbit Ethernet cable. To actually transmit the Ethernet packet\na 48.bit Ethernet address must be generated. The addresses of\nhosts within protocol P are not always compatible with the\ncorresponding Ethernet address (being different lengths or\nvalues). Presented here is a protocol that allows dynamic\ndistribution of the information needed to build tables to\ntranslate an address A in protocol P's address space into a\n48.bit Ethernet address.\n","scope_keywords":["826"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0879","folder":"IETF/RFC-0879","source":"IETF/RFC-0879/RFC-0879.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0903","folder":"IETF/RFC-0903","source":"IETF/RFC-0903/RFC-0903.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1209","folder":"IETF/RFC-1209","source":"IETF/RFC-1209/RFC-1209.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1433","folder":"IETF/RFC-1433","source":"IETF/RFC-1433/RFC-1433.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1532","folder":"IETF/RFC-1532","source":"IETF/RFC-1532/RFC-1532.txt","version":null},{"body":"IETF","designation":"RFC 1542","folder":"IETF/RFC-1542","source":"IETF/RFC-1542/RFC-1542.txt","version":null},{"body":"IETF","designation":"RFC 1577","folder":"IETF/RFC-1577","source":"IETF/RFC-1577/RFC-1577.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1620","folder":"IETF/RFC-1620","source":"IETF/RFC-1620/RFC-1620.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1701","folder":"IETF/RFC-1701","source":"IETF/RFC-1701/RFC-1701.txt","version":null},{"body":"IETF","designation":"RFC 1735","folder":"IETF/RFC-1735","source":"IETF/RFC-1735/RFC-1735.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 1970","folder":"IETF/RFC-1970","source":"IETF/RFC-1970/RFC-1970.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2225","folder":"IETF/RFC-2225","source":"IETF/RFC-2225/RFC-2225.txt","version":null},{"body":"IETF","designation":"RFC 2332","folder":"IETF/RFC-2332","source":"IETF/RFC-2332/RFC-2332.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2461","folder":"IETF/RFC-2461","source":"IETF/RFC-2461/RFC-2461.txt","version":null},{"body":"IETF","designation":"RFC 2469","folder":"IETF/RFC-2469","source":"IETF/RFC-2469/RFC-2469.txt","version":null},{"body":"IETF","designation":"RFC 2491","folder":"IETF/RFC-2491","source":"IETF/RFC-2491/RFC-2491.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3077","folder":"IETF/RFC-3077","source":"IETF/RFC-3077/RFC-3077.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3315","folder":"IETF/RFC-3315","source":"IETF/RFC-3315/RFC-3315.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3684","folder":"IETF/RFC-3684","source":"IETF/RFC-3684/RFC-3684.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4058","folder":"IETF/RFC-4058","source":"IETF/RFC-4058/RFC-4058.txt","version":null},{"body":"IETF","designation":"RFC 4293","folder":"IETF/RFC-4293","source":"IETF/RFC-4293/RFC-4293.txt","version":null},{"body":"IETF","designation":"RFC 4338","folder":"IETF/RFC-4338","source":"IETF/RFC-4338/RFC-4338.txt","version":null},{"body":"IETF","designation":"RFC 4388","folder":"IETF/RFC-4388","source":"IETF/RFC-4388/RFC-4388.txt","version":null},{"body":"IETF","designation":"RFC 4391","folder":"IETF/RFC-4391","source":"IETF/RFC-4391/RFC-4391.txt","version":null},{"body":"IETF","designation":"RFC 4436","folder":"IETF/RFC-4436","source":"IETF/RFC-4436/RFC-4436.txt","version":null},{"body":"IETF","designation":"RFC 4562","folder":"IETF/RFC-4562","source":"IETF/RFC-4562/RFC-4562.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 4861","folder":"IETF/RFC-4861","source":"IETF/RFC-4861/RFC-4861.txt","version":null},{"body":"IETF","designation":"RFC 4881","folder":"IETF/RFC-4881","source":"IETF/RFC-4881/RFC-4881.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5007","folder":"IETF/RFC-5007","source":"IETF/RFC-5007/RFC-5007.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 5556","folder":"IETF/RFC-5556","source":"IETF/RFC-5556/RFC-5556.txt","version":null},{"body":"IETF","designation":"RFC 5558","folder":"IETF/RFC-5558","source":"IETF/RFC-5558/RFC-5558.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5838","folder":"IETF/RFC-5838","source":"IETF/RFC-5838/RFC-5838.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6069","folder":"IETF/RFC-6069","source":"IETF/RFC-6069/RFC-6069.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 6740","folder":"IETF/RFC-6740","source":"IETF/RFC-6740/RFC-6740.txt","version":null},{"body":"IETF","designation":"RFC 6741","folder":"IETF/RFC-6741","source":"IETF/RFC-6741/RFC-6741.txt","version":null},{"body":"IETF","designation":"RFC 6747","folder":"IETF/RFC-6747","source":"IETF/RFC-6747/RFC-6747.txt","version":null},{"body":"IETF","designation":"RFC 6820","folder":"IETF/RFC-6820","source":"IETF/RFC-6820/RFC-6820.txt","version":null},{"body":"IETF","designation":"RFC 6939","folder":"IETF/RFC-6939","source":"IETF/RFC-6939/RFC-6939.txt","version":null},{"body":"IETF","designation":"RFC 6959","folder":"IETF/RFC-6959","source":"IETF/RFC-6959/RFC-6959.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7277","folder":"IETF/RFC-7277","source":"IETF/RFC-7277/RFC-7277.txt","version":null},{"body":"IETF","designation":"RFC 7513","folder":"IETF/RFC-7513","source":"IETF/RFC-7513/RFC-7513.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 8344","folder":"IETF/RFC-8344","source":"IETF/RFC-8344/RFC-8344.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 879","folder":"IETF/RFC-879","source":"IETF/RFC-879/RFC-879.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 903","folder":"IETF/RFC-903","source":"IETF/RFC-903/RFC-903.txt","version":null},{"body":"IETF","designation":"RFC 906","folder":"IETF/RFC-906","source":"IETF/RFC-906/RFC-906.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 826 Network Working Group David C. Plummer \nRequest For Comments: 826 (DCP@MIT-MC)\n November 1982\n\n An Ethernet Address Resolution Protocol\n -- or --\n Converting Network Protocol Addresses\n to 48.bit Ethernet Address\n for Transmission on\n Ethernet Hardware\n\n Abstract\n\nThe implementation of protocol P on a sending host S decides,\nthrough protocol P's routing mechanism, that it wants to transmit\nto a target host T located some place on a connected piece of\n10Mbit Ethernet cable. To actually transmit the Ethernet packet\na 48.bit Ethernet address must be generated. The addresses of\nhosts within protocol P are not always compatible with the\ncorresponding Ethernet address (being different lengths or\nvalues). Presented here is a protocol that allows dynamic\ndistribution of the information needed to build tables to\ntranslate an address A in protocol P's address space into a\n48.bit Ethernet address.\n 826 nested-reference unchanged"},{"id":"IETF RFC 903","type":"specification","body":"IETF","designation":"RFC 903","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc903.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc903.txt","https://www.rfc-editor.org/rfc/rfc903.pdf"],"folder":"IETF/RFC-903","files":{"txt":{"path":"standards/IETF/RFC-903/RFC-903.txt","sha256":"74e97a29c12979734d4aec3df5b8d159b0987707338be1e299d90ecc3645b6fa"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Finlayson, Mann, Mogul, Theimer\nRequest for Comments: 903 Stanford University\n June 1984\n\n A Reverse Address Resolution Protocol\n\n Ross Finlayson, Timothy Mann, Jeffrey Mogul, Marvin Theimer\n Computer Science Department\n Stanford University\n June 1984\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically find their\n protocol address (e.g., their Internet Address), when they know only\n their hardware address (e.g., their attached physical network\n address).\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nI. Introduction\n\n Network hosts such as diskless workstations frequently do not know\n their protocol addresses when booted; they often know only their\n hardware interface addresses. To communicate using higher-level\n protocols like IP, they must discover ","scope_keywords":["903"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0903","folder":"IETF/RFC-0903","source":"IETF/RFC-0903/RFC-0903.txt","version":null},{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1201","folder":"IETF/RFC-1201","source":"IETF/RFC-1201/RFC-1201.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1374","folder":"IETF/RFC-1374","source":"IETF/RFC-1374/RFC-1374.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 1933","folder":"IETF/RFC-1933","source":"IETF/RFC-1933/RFC-1933.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2390","folder":"IETF/RFC-2390","source":"IETF/RFC-2390/RFC-2390.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 2893","folder":"IETF/RFC-2893","source":"IETF/RFC-2893/RFC-2893.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 5494","folder":"IETF/RFC-5494","source":"IETF/RFC-5494/RFC-5494.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null},{"body":"IETF","designation":"RFC 906","folder":"IETF/RFC-906","source":"IETF/RFC-906/RFC-906.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 903 Network Working Group Finlayson, Mann, Mogul, Theimer\nRequest for Comments: 903 Stanford University\n June 1984\n\n A Reverse Address Resolution Protocol\n\n Ross Finlayson, Timothy Mann, Jeffrey Mogul, Marvin Theimer\n Computer Science Department\n Stanford University\n June 1984\n\nStatus of this Memo\n\n This RFC suggests a method for workstations to dynamically find their\n protocol address (e.g., their Internet Address), when they know only\n their hardware address (e.g., their attached physical network\n address).\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for improvements.\n\nI. Introduction\n\n Network hosts such as diskless workstations frequently do not know\n their protocol addresses when booted; they often know only their\n hardware interface addresses. To communicate using higher-level\n protocols like IP, they must discover  903 nested-reference unchanged"},{"id":"IETF RFC 827","type":"specification","body":"IETF","designation":"RFC 827","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc827.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc827.txt","https://www.rfc-editor.org/rfc/rfc827.pdf"],"folder":"IETF/RFC-827","files":{"txt":{"path":"standards/IETF/RFC-827/RFC-827.txt","sha256":"4bdbb31a85e39f5438facc4d65ad9a5cf14d90d6ccb17ac985efcb3bed4c4af2"}},"tags":["nested-reference","unchanged"],"summary":"RFC 827\n\n EXTERIOR GATEWAY PROTOCOL (EGP)\n\n Eric C. Rosen\n\n Bolt Beranek and Newman Inc.\n\n October 1982\n\nIt is proposed to establish a standard for Gateway to Gateway procedures\nthat allow the Gateways to be mutually suspicious. This document is a\nDRAFT for that standard. Your comments are strongly encouraged.\n\n\f\n RFC 827 Bolt Beranek and Newman Inc.\n Eric C. Rosen\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 NEIGHBOR ACQUISITION.................................. 8\n 3 NEIGHBOR REACHABILITY PROTOCOL....................... 11\n 4 NETWORK REACHABILITY (NR) MESSAGE.................... 15\n 5 POLLING FOR NR MESSAGES.............................. 22\n 6 SENDING NR MESSAGES.................................. 25\n 7 INDIRECT NEIGHBORS................................... 27\n 8 HOW TO BE A STUB GATEWAY............................. 28\n 9 LIMITATIONS.................","scope_keywords":["827","algorithm","algorithms","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0820","folder":"IETF/RFC-0820","source":"IETF/RFC-0820/RFC-0820.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1125","folder":"IETF/RFC-1125","source":"IETF/RFC-1125/RFC-1125.txt","version":null},{"body":"IETF","designation":"RFC 1136","folder":"IETF/RFC-1136","source":"IETF/RFC-1136/RFC-1136.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2235","folder":"IETF/RFC-2235","source":"IETF/RFC-2235/RFC-2235.txt","version":null},{"body":"IETF","designation":"RFC 820","folder":"IETF/RFC-820","source":"IETF/RFC-820/RFC-820.txt","version":null},{"body":"IETF","designation":"RFC 840","folder":"IETF/RFC-840","source":"IETF/RFC-840/RFC-840.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 827 RFC 827\n\n EXTERIOR GATEWAY PROTOCOL (EGP)\n\n Eric C. Rosen\n\n Bolt Beranek and Newman Inc.\n\n October 1982\n\nIt is proposed to establish a standard for Gateway to Gateway procedures\nthat allow the Gateways to be mutually suspicious. This document is a\nDRAFT for that standard. Your comments are strongly encouraged.\n\n\f\n RFC 827 Bolt Beranek and Newman Inc.\n Eric C. Rosen\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n 2 NEIGHBOR ACQUISITION.................................. 8\n 3 NEIGHBOR REACHABILITY PROTOCOL....................... 11\n 4 NETWORK REACHABILITY (NR) MESSAGE.................... 15\n 5 POLLING FOR NR MESSAGES.............................. 22\n 6 SENDING NR MESSAGES.................................. 25\n 7 INDIRECT NEIGHBORS................................... 27\n 8 HOW TO BE A STUB GATEWAY............................. 28\n 9 LIMITATIONS................. 827 algorithm algorithms identification nested-reference unchanged"},{"id":"IETF RFC 832","type":"specification","body":"IETF","designation":"RFC 832","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc832.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc832.txt","https://www.rfc-editor.org/rfc/rfc832.pdf"],"folder":"IETF/RFC-832","files":{"txt":{"path":"standards/IETF/RFC-832/RFC-832.txt","sha256":"315b1dcad2933ac88215d8f17dead44baf4e04cf3aaf050aae02600f9821c7e8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Smallberg\nRequest for Comments: 832 December 1982\n\n Who Talks TCP?\n\nThe list of hosts was taken from the NIC hostname table of 2-Dec-82.\nThe tests were run on 7-Dec-82 from ~12:01 am to ~2:15 am PST and from\n ~12:30 pm to ~7:00 pm PST.\nDead, refused, and unreachable hosts were retried 8-Dec-82 from ~3:15 pm\n to ~4:30 pm PST.\n\nClaims are taken from the NIC host table:\n T = tcp (no particular services mentioned)\n t = tcp/telnet\n f = tcp/ftp\n s = tcp/smtp\n\nResults for each service:\n blank (not accepted)\n refused\n unreachable\n dead\n accepted\n accepted+ (FTP allowed user anonymous, password guest)\n\nSummary information:\n\n Telnet Result\n\n no telnet unreachable refused dead accepted\n +-----------+-------------+---------+------+------------+\nC tcp/telnet | 22 | 7 | 2 | 35 | 64 | 130\nl +-----------+-------------+---------+------+------------+\na tcp | 11 | 0 | 1 | 4 | 7 | 2","scope_keywords":["832"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 847","folder":"IETF/RFC-847","source":"IETF/RFC-847/RFC-847.txt","version":null}],"search_text":"IETF RFC 832 Network Working Group D. Smallberg\nRequest for Comments: 832 December 1982\n\n Who Talks TCP?\n\nThe list of hosts was taken from the NIC hostname table of 2-Dec-82.\nThe tests were run on 7-Dec-82 from ~12:01 am to ~2:15 am PST and from\n ~12:30 pm to ~7:00 pm PST.\nDead, refused, and unreachable hosts were retried 8-Dec-82 from ~3:15 pm\n to ~4:30 pm PST.\n\nClaims are taken from the NIC host table:\n T = tcp (no particular services mentioned)\n t = tcp/telnet\n f = tcp/ftp\n s = tcp/smtp\n\nResults for each service:\n blank (not accepted)\n refused\n unreachable\n dead\n accepted\n accepted+ (FTP allowed user anonymous, password guest)\n\nSummary information:\n\n Telnet Result\n\n no telnet unreachable refused dead accepted\n +-----------+-------------+---------+------+------------+\nC tcp/telnet | 22 | 7 | 2 | 35 | 64 | 130\nl +-----------+-------------+---------+------+------------+\na tcp | 11 | 0 | 1 | 4 | 7 | 2 832 nested-reference unchanged"},{"id":"IETF RFC 847","type":"specification","body":"IETF","designation":"RFC 847","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc847.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc847.txt","https://www.rfc-editor.org/rfc/rfc847.pdf"],"folder":"IETF/RFC-847","files":{"txt":{"path":"standards/IETF/RFC-847/RFC-847.txt","sha256":"94aa79eab49a0e3e5e08f462181a832e26e5dcc31db517672c9d6702e8bb4570"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group A. Westine\nRequest for Comments: 847 D. Smallberg\n J. Postel\n February, 1983\n\n SUMMARY OF SMALLBERG SURVEYS\n \nThis is a summary of the surveys of Telnet, FTP and Mail (SMTP)\nservers conducted by David Smallberg in December 1982 and January\nand February 1983 as reported in RFC 832-843, 845-846. This memo\nextracts the number of hosts that accepted the connection to\ntheir server for each of Telnet, FTP, and SMTP, and compares it\nto the total host in the Internet (not counting TACs or ECHOS).\n\nOne would not expect the percentage to reach 100, since some\nhosts will be down when the surveys are run, but many hosts are\nfor special purposes and don't offer these services. We estimate\nthat 37 hosts or 11 percent are in this catagory and the highest\npercentage one could reasonably expect is 89.\n \n TELNET\n\n RFC DATE ACCEPT TOTAL PERCENT\n --- ---- ------ ----- -------\n 832 7 De","scope_keywords":["847"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1705","folder":"IETF/RFC-1705","source":"IETF/RFC-1705/RFC-1705.txt","version":null}],"search_text":"IETF RFC 847 Network Working Group A. Westine\nRequest for Comments: 847 D. Smallberg\n J. Postel\n February, 1983\n\n SUMMARY OF SMALLBERG SURVEYS\n \nThis is a summary of the surveys of Telnet, FTP and Mail (SMTP)\nservers conducted by David Smallberg in December 1982 and January\nand February 1983 as reported in RFC 832-843, 845-846. This memo\nextracts the number of hosts that accepted the connection to\ntheir server for each of Telnet, FTP, and SMTP, and compares it\nto the total host in the Internet (not counting TACs or ECHOS).\n\nOne would not expect the percentage to reach 100, since some\nhosts will be down when the surveys are run, but many hosts are\nfor special purposes and don't offer these services. We estimate\nthat 37 hosts or 11 percent are in this catagory and the highest\npercentage one could reasonably expect is 89.\n \n TELNET\n\n RFC DATE ACCEPT TOTAL PERCENT\n --- ---- ------ ----- -------\n 832 7 De 847 nested-reference unchanged"},{"id":"IETF RFC 8366","type":"specification","body":"IETF","designation":"RFC 8366","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8366.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8366.txt","https://www.rfc-editor.org/rfc/rfc8366.pdf"],"folder":"IETF/RFC-8366","files":{"txt":{"path":"standards/IETF/RFC-8366/RFC-8366.txt","sha256":"89c459bb8b3e8aeb2003e16e4de5bb4c07ddef6d4f73a9afaacabc1b6868df77"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a strategy to securely assign a pledge to an\n owner using an artifact signed, directly or indirectly, by the\n pledge's manufacturer. This artifact is known as a \"voucher\".\n\n This document defines an artifact format as a YANG-defined JSON\n document that has been signed using a Cryptographic Message Syntax\n (CMS) structure. Other YANG-derived formats are possible. The\n voucher artifact is normally generated by the pledge's manufacturer\n (i.e., the Manufacturer Authorized Signing Authority (MASA)).\n\n This document only defines the voucher artifact, leaving it to other\n documents to describe specialized protocols for accessing it.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been ap","scope_keywords":["8366","certificate","driving","http","https","key","license","pki","profile","revocation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null}],"search_text":"IETF RFC 8366 This document defines a strategy to securely assign a pledge to an\n owner using an artifact signed, directly or indirectly, by the\n pledge's manufacturer. This artifact is known as a \"voucher\".\n\n This document defines an artifact format as a YANG-defined JSON\n document that has been signed using a Cryptographic Message Syntax\n (CMS) structure. Other YANG-derived formats are possible. The\n voucher artifact is normally generated by the pledge's manufacturer\n (i.e., the Manufacturer Authorized Signing Authority (MASA)).\n\n This document only defines the voucher artifact, leaving it to other\n documents to describe specialized protocols for accessing it.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been ap 8366 certificate driving http https key license pki profile revocation subject trust nested-reference unchanged"},{"id":"IETF RFC 843","type":"specification","body":"IETF","designation":"RFC 843","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc843.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc843.txt","https://www.rfc-editor.org/rfc/rfc843.pdf"],"folder":"IETF/RFC-843","files":{"txt":{"path":"standards/IETF/RFC-843/RFC-843.txt","sha256":"d64b03e4bf23ab6199227191404092e8d381b9a07433d926ef9f34893dcfebff"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. Smallberg\nRequest for Comments: 843 February 1983\n\n Who Talks TCP? -- Survey of 8 February 1983\n\nThe list of hosts was taken from the NIC hostname table of 3-Feb-83.\nThe tests were run on 8-Feb-83 from 10 am to ~5:10 pm PST, and on\n 9-Feb-83 from 1 am to ~5:15 am PST from ISI-VAXA.ARPA\nDead, refused, and unreachable hosts were retried 9-Feb-83 from ~8 am\n to ~4:40 pm PST.\n\nClaims are taken from the NIC host table:\n T = tcp (no particular services mentioned)\n t = tcp/telnet\n f = tcp/ftp\n s = tcp/smtp\n\nResults for each service:\n blank (not accepted)\n refused\n unreachable\n dead\n accepted\n accepted+ (FTP allowed user anonymous, password guest)\n\nSummary information:\n\n Telnet Result\n\n no telnet unreachable refused dead accepted\n +-----------+-------------+---------+------+------------+\nC tcp/telnet | 23 | 10 | 3 | 16 | 165 | 217\nl +-----------+-------------+---------+-","scope_keywords":["843"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 843 Network Working Group D. Smallberg\nRequest for Comments: 843 February 1983\n\n Who Talks TCP? -- Survey of 8 February 1983\n\nThe list of hosts was taken from the NIC hostname table of 3-Feb-83.\nThe tests were run on 8-Feb-83 from 10 am to ~5:10 pm PST, and on\n 9-Feb-83 from 1 am to ~5:15 am PST from ISI-VAXA.ARPA\nDead, refused, and unreachable hosts were retried 9-Feb-83 from ~8 am\n to ~4:40 pm PST.\n\nClaims are taken from the NIC host table:\n T = tcp (no particular services mentioned)\n t = tcp/telnet\n f = tcp/ftp\n s = tcp/smtp\n\nResults for each service:\n blank (not accepted)\n refused\n unreachable\n dead\n accepted\n accepted+ (FTP allowed user anonymous, password guest)\n\nSummary information:\n\n Telnet Result\n\n no telnet unreachable refused dead accepted\n +-----------+-------------+---------+------+------------+\nC tcp/telnet | 23 | 10 | 3 | 16 | 165 | 217\nl +-----------+-------------+---------+- 843 nested-reference unchanged"},{"id":"IETF RFC 977","type":"specification","body":"IETF","designation":"RFC 977","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc977.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc977.txt","https://www.rfc-editor.org/rfc/rfc977.pdf"],"folder":"IETF/RFC-977","files":{"txt":{"path":"standards/IETF/RFC-977/RFC-977.txt","sha256":"c6c987a0a0d832344d66f07c69f13398705dd23467df205c51a97609f5bc98ae"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Brian Kantor (U.C. San Diego)\nRequest for Comments: 977 Phil Lapsley (U.C. Berkeley)\n February 1986\n\n Network News Transfer Protocol\n \n A Proposed Standard for the Stream-Based\n Transmission of News\n\nStatus of This Memo\n\n NNTP specifies a protocol for the distribution, inquiry, retrieval,\n and posting of news articles using a reliable stream-based\n transmission of news among the ARPA-Internet community. NNTP is\n designed so that news articles are stored in a central database\n allowing a subscriber to select only those items he wishes to read.\n Indexing, cross-referencing, and expiration of aged messages are also\n provided. This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n For many years, the ARPA-Internet community has supported","scope_keywords":["977","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0977","folder":"IETF/RFC-0977","source":"IETF/RFC-0977/RFC-0977.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1580","folder":"IETF/RFC-1580","source":"IETF/RFC-1580/RFC-1580.txt","version":null},{"body":"IETF","designation":"RFC 1630","folder":"IETF/RFC-1630","source":"IETF/RFC-1630/RFC-1630.txt","version":null},{"body":"IETF","designation":"RFC 1738","folder":"IETF/RFC-1738","source":"IETF/RFC-1738/RFC-1738.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2594","folder":"IETF/RFC-2594","source":"IETF/RFC-2594/RFC-2594.txt","version":null},{"body":"IETF","designation":"RFC 2616","folder":"IETF/RFC-2616","source":"IETF/RFC-2616/RFC-2616.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 2980","folder":"IETF/RFC-2980","source":"IETF/RFC-2980/RFC-2980.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3675","folder":"IETF/RFC-3675","source":"IETF/RFC-3675/RFC-3675.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3887","folder":"IETF/RFC-3887","source":"IETF/RFC-3887/RFC-3887.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 4086","folder":"IETF/RFC-4086","source":"IETF/RFC-4086/RFC-4086.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 977 Network Working Group Brian Kantor (U.C. San Diego)\nRequest for Comments: 977 Phil Lapsley (U.C. Berkeley)\n February 1986\n\n Network News Transfer Protocol\n \n A Proposed Standard for the Stream-Based\n Transmission of News\n\nStatus of This Memo\n\n NNTP specifies a protocol for the distribution, inquiry, retrieval,\n and posting of news articles using a reliable stream-based\n transmission of news among the ARPA-Internet community. NNTP is\n designed so that news articles are stored in a central database\n allowing a subscriber to select only those items he wishes to read.\n Indexing, cross-referencing, and expiration of aged messages are also\n provided. This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n1. Introduction\n\n For many years, the ARPA-Internet community has supported 977 pid nested-reference unchanged"},{"id":"IETF RFC 8513","type":"specification","body":"IETF","designation":"RFC 8513","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8513.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8513.txt","https://www.rfc-editor.org/rfc/rfc8513.pdf"],"folder":"IETF/RFC-8513","files":{"txt":{"path":"standards/IETF/RFC-8513/RFC-8513.txt","sha256":"711c7fe7119f52a17c8f52671891e818f7a17754eefdd1c3923ae14b17462512"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a YANG module for the Dual-Stack Lite (DS-Lite)\n Address Family Transition Router (AFTR) and Basic Bridging BroadBand\n (B4) elements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8513.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust","scope_keywords":["8513","http","https","license","management","policy","preservation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8512","folder":"IETF/RFC-8512","source":"IETF/RFC-8512/RFC-8512.txt","version":null}],"search_text":"IETF RFC 8513 This document defines a YANG module for the Dual-Stack Lite (DS-Lite)\n Address Family Transition Router (AFTR) and Basic Bridging BroadBand\n (B4) elements.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8513.\n\nCopyright Notice\n\n Copyright (c) 2019 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IETF Trust 8513 http https license management policy preservation subject trust nested-reference unchanged"},{"id":"IETF RFC 854","type":"specification","body":"IETF","designation":"RFC 854","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc854.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc854.txt","https://www.rfc-editor.org/rfc/rfc854.pdf"],"folder":"IETF/RFC-854","files":{"txt":{"path":"standards/IETF/RFC-854/RFC-854.txt","sha256":"f9cb6d4a7d7a67e5a1ac5ae3c2962b1183fb26119632a1617f3c8379820dfb10"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 854 J. Reynolds\n ISI\nObsoletes: NIC 18639 May 1983\n\n TELNET PROTOCOL SPECIFICATION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information.\n\n The TELNET","scope_keywords":["854","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0854","folder":"IETF/RFC-0854","source":"IETF/RFC-0854/RFC-0854.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 0959","folder":"IETF/RFC-0959","source":"IETF/RFC-0959/RFC-0959.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1091","folder":"IETF/RFC-1091","source":"IETF/RFC-1091/RFC-1091.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1143","folder":"IETF/RFC-1143","source":"IETF/RFC-1143/RFC-1143.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1206","folder":"IETF/RFC-1206","source":"IETF/RFC-1206/RFC-1206.txt","version":null},{"body":"IETF","designation":"RFC 1207","folder":"IETF/RFC-1207","source":"IETF/RFC-1207/RFC-1207.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1244","folder":"IETF/RFC-1244","source":"IETF/RFC-1244/RFC-1244.txt","version":null},{"body":"IETF","designation":"RFC 1325","folder":"IETF/RFC-1325","source":"IETF/RFC-1325/RFC-1325.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1443","folder":"IETF/RFC-1443","source":"IETF/RFC-1443/RFC-1443.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1646","folder":"IETF/RFC-1646","source":"IETF/RFC-1646/RFC-1646.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1739","folder":"IETF/RFC-1739","source":"IETF/RFC-1739/RFC-1739.txt","version":null},{"body":"IETF","designation":"RFC 1903","folder":"IETF/RFC-1903","source":"IETF/RFC-1903/RFC-1903.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1948","folder":"IETF/RFC-1948","source":"IETF/RFC-1948/RFC-1948.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2151","folder":"IETF/RFC-2151","source":"IETF/RFC-2151/RFC-2151.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 2579","folder":"IETF/RFC-2579","source":"IETF/RFC-2579/RFC-2579.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2941","folder":"IETF/RFC-2941","source":"IETF/RFC-2941/RFC-2941.txt","version":null},{"body":"IETF","designation":"RFC 2946","folder":"IETF/RFC-2946","source":"IETF/RFC-2946/RFC-2946.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3205","folder":"IETF/RFC-3205","source":"IETF/RFC-3205/RFC-3205.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3552","folder":"IETF/RFC-3552","source":"IETF/RFC-3552/RFC-3552.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3993","folder":"IETF/RFC-3993","source":"IETF/RFC-3993/RFC-3993.txt","version":null},{"body":"IETF","designation":"RFC 4111","folder":"IETF/RFC-4111","source":"IETF/RFC-4111/RFC-4111.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4580","folder":"IETF/RFC-4580","source":"IETF/RFC-4580/RFC-4580.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 5929","folder":"IETF/RFC-5929","source":"IETF/RFC-5929/RFC-5929.txt","version":null},{"body":"IETF","designation":"RFC 6093","folder":"IETF/RFC-6093","source":"IETF/RFC-6093/RFC-6093.txt","version":null},{"body":"IETF","designation":"RFC 6101","folder":"IETF/RFC-6101","source":"IETF/RFC-6101/RFC-6101.txt","version":null},{"body":"IETF","designation":"RFC 6528","folder":"IETF/RFC-6528","source":"IETF/RFC-6528/RFC-6528.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 959","folder":"IETF/RFC-959","source":"IETF/RFC-959/RFC-959.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 854 Network Working Group J. Postel\nRequest for Comments: 854 J. Reynolds\n ISI\nObsoletes: NIC 18639 May 1983\n\n TELNET PROTOCOL SPECIFICATION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nINTRODUCTION\n\n The purpose of the TELNET Protocol is to provide a fairly general,\n bi-directional, eight-bit byte oriented communications facility. Its\n primary goal is to allow a standard method of interfacing terminal\n devices and terminal-oriented processes to each other. It is\n envisioned that the protocol may also be used for terminal-terminal\n communication (\"linking\") and process-process communication\n (distributed computation).\n\nGENERAL CONSIDERATIONS\n\n A TELNET connection is a Transmission Control Protocol (TCP)\n connection used to transmit data with interspersed TELNET control\n information.\n\n The TELNET 854 presentation nested-reference unchanged"},{"id":"IETF RFC 855","type":"specification","body":"IETF","designation":"RFC 855","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc855.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc855.txt","https://www.rfc-editor.org/rfc/rfc855.pdf"],"folder":"IETF/RFC-855","files":{"txt":{"path":"standards/IETF/RFC-855/RFC-855.txt","sha256":"c8c4744c9fa7650c0ae78d140f560b26e26b2935391e1ff624476c5fdbf4e03a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 855 J. Reynolds\n ISI\nObsoletes: NIC 18640 May 1983\n\n TELNET OPTION SPECIFICATIONS\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nThe intent of providing for options in the TELNET Protocol is to permit\nhosts to obtain more elegant solutions to the problems of communication\nbetween dissimilar devices than is possible within the framework\nprovided by the Network Virtual Terminal (NVT). It should be possible\nfor hosts to invent, test, or discard options at will. Nevertheless, it\nis envisioned that options which prove to be generally useful will\neventually be supported by many hosts; therefore it is desirable that\noptions should be carefully documented and well publicized. In\naddition, it is necessary to insure that a single option code is not\nu","scope_keywords":["855"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1091","folder":"IETF/RFC-1091","source":"IETF/RFC-1091/RFC-1091.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2246","folder":"IETF/RFC-2246","source":"IETF/RFC-2246/RFC-2246.txt","version":null},{"body":"IETF","designation":"RFC 2951","folder":"IETF/RFC-2951","source":"IETF/RFC-2951/RFC-2951.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 5920","folder":"IETF/RFC-5920","source":"IETF/RFC-5920/RFC-5920.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 855 Network Working Group J. Postel\nRequest for Comments: 855 J. Reynolds\n ISI\nObsoletes: NIC 18640 May 1983\n\n TELNET OPTION SPECIFICATIONS\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\nThe intent of providing for options in the TELNET Protocol is to permit\nhosts to obtain more elegant solutions to the problems of communication\nbetween dissimilar devices than is possible within the framework\nprovided by the Network Virtual Terminal (NVT). It should be possible\nfor hosts to invent, test, or discard options at will. Nevertheless, it\nis envisioned that options which prove to be generally useful will\neventually be supported by many hosts; therefore it is desirable that\noptions should be carefully documented and well publicized. In\naddition, it is necessary to insure that a single option code is not\nu 855 nested-reference unchanged"},{"id":"IETF RFC 856","type":"specification","body":"IETF","designation":"RFC 856","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc856.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc856.txt","https://www.rfc-editor.org/rfc/rfc856.pdf"],"folder":"IETF/RFC-856","files":{"txt":{"path":"standards/IETF/RFC-856/RFC-856.txt","sha256":"ae0676f720345740764119606529b1d4a160e4c5ef558e0da4b3ec7bdf53c102"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 856 J. Reynolds\n ISI\nObsoletes: NIC 15389 May 1983\n\n TELNET BINARY TRANSMISSION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TRANSMIT-BINARY 0\n\n2. Command Meanings\n\n IAC WILL TRANSMIT-BINARY\n\n The sender of this command REQUESTS permission to begin\n transmitting, or confirms that it will now begin transmitting\n characters which are to be interpreted as 8 bits of binary data by\n the receiver of the data.\n\n IAC WON'T TRANSMIT-BINARY\n\n If the connection is already being operated in binary transmission\n mode, the sender of this command DEMANDS to begin transmitting\n data characters which are to be interpreted as standard NVT ASCII\n characters by the receiver of the data. If the connection is not\n already being opera","scope_keywords":["856","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1646","folder":"IETF/RFC-1646","source":"IETF/RFC-1646/RFC-1646.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 856 Network Working Group J. Postel\nRequest for Comments: 856 J. Reynolds\n ISI\nObsoletes: NIC 15389 May 1983\n\n TELNET BINARY TRANSMISSION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TRANSMIT-BINARY 0\n\n2. Command Meanings\n\n IAC WILL TRANSMIT-BINARY\n\n The sender of this command REQUESTS permission to begin\n transmitting, or confirms that it will now begin transmitting\n characters which are to be interpreted as 8 bits of binary data by\n the receiver of the data.\n\n IAC WON'T TRANSMIT-BINARY\n\n If the connection is already being operated in binary transmission\n mode, the sender of this command DEMANDS to begin transmitting\n data characters which are to be interpreted as standard NVT ASCII\n characters by the receiver of the data. If the connection is not\n already being opera 856 path nested-reference unchanged"},{"id":"IETF RFC 857","type":"specification","body":"IETF","designation":"RFC 857","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc857.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc857.txt","https://www.rfc-editor.org/rfc/rfc857.pdf"],"folder":"IETF/RFC-857","files":{"txt":{"path":"standards/IETF/RFC-857/RFC-857.txt","sha256":"6b04dca101550d7a13971429bb476eb432cd8a39c2ec59f5f5efad81788e00a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 857 J. Reynolds\n ISI\nObsoletes: NIC 15390 May 1983\n\n TELNET ECHO OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n ECHO 1\n\n2. Command Meanings\n\n IAC WILL ECHO\n\n The sender of this command REQUESTS to begin, or confirms that it\n will now begin, echoing data characters it receives over the\n TELNET connection back to the sender of the data characters.\n\n IAC WON'T ECHO\n\n The sender of this command DEMANDS to stop, or refuses to start,\n echoing the data characters it receives over the TELNET connection\n back to the sender of the data characters.\n\n IAC DO ECHO\n\n The sender of this command REQUESTS that the receiver of this\n command begin echoing, or confirms that the receiver of this\n command is expected to echo, da","scope_keywords":["857","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 857 Network Working Group J. Postel\nRequest for Comments: 857 J. Reynolds\n ISI\nObsoletes: NIC 15390 May 1983\n\n TELNET ECHO OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n ECHO 1\n\n2. Command Meanings\n\n IAC WILL ECHO\n\n The sender of this command REQUESTS to begin, or confirms that it\n will now begin, echoing data characters it receives over the\n TELNET connection back to the sender of the data characters.\n\n IAC WON'T ECHO\n\n The sender of this command DEMANDS to stop, or refuses to start,\n echoing the data characters it receives over the TELNET connection\n back to the sender of the data characters.\n\n IAC DO ECHO\n\n The sender of this command REQUESTS that the receiver of this\n command begin echoing, or confirms that the receiver of this\n command is expected to echo, da 857 key nested-reference unchanged"},{"id":"IETF RFC 858","type":"specification","body":"IETF","designation":"RFC 858","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc858.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc858.txt","https://www.rfc-editor.org/rfc/rfc858.pdf"],"folder":"IETF/RFC-858","files":{"txt":{"path":"standards/IETF/RFC-858/RFC-858.txt","sha256":"87b93cb4b4cd0bf0be401d1a9524400a9570555e9ac962a1504cfdca522dc8f4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 858 J. Reynolds\n ISI\nObsoletes: NIC 15392 May 1983\n\n TELNET SUPPRESS GO AHEAD OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n SUPPRESS-GO-AHEAD 3\n\n2. Command Meanings\n\n IAC WILL SUPPRESS-GO-AHEAD\n\n The sender of this command requests permission to begin\n suppressing transmission of the TELNET GO AHEAD (GA) character\n when transmitting data characters, or the sender of this command\n confirms it will now begin suppressing transmission of GAs with\n transmitted data characters.\n\n IAC WON'T SUPPRESS-GO-AHEAD\n\n The sender of this command demands to begin transmitting, or to\n continue transmitting, the GA character when transmitting data\n characters.\n\n IAC DO SUPPRESS-GO-AHEAD\n\n The sender of this commannd requests","scope_keywords":["858"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 858 Network Working Group J. Postel\nRequest for Comments: 858 J. Reynolds\n ISI\nObsoletes: NIC 15392 May 1983\n\n TELNET SUPPRESS GO AHEAD OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n SUPPRESS-GO-AHEAD 3\n\n2. Command Meanings\n\n IAC WILL SUPPRESS-GO-AHEAD\n\n The sender of this command requests permission to begin\n suppressing transmission of the TELNET GO AHEAD (GA) character\n when transmitting data characters, or the sender of this command\n confirms it will now begin suppressing transmission of GAs with\n transmitted data characters.\n\n IAC WON'T SUPPRESS-GO-AHEAD\n\n The sender of this command demands to begin transmitting, or to\n continue transmitting, the GA character when transmitting data\n characters.\n\n IAC DO SUPPRESS-GO-AHEAD\n\n The sender of this commannd requests 858 nested-reference unchanged"},{"id":"IETF RFC 860","type":"specification","body":"IETF","designation":"RFC 860","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc860.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc860.txt","https://www.rfc-editor.org/rfc/rfc860.pdf"],"folder":"IETF/RFC-860","files":{"txt":{"path":"standards/IETF/RFC-860/RFC-860.txt","sha256":"a24128118ea0f93390ae163aaa3e7ab7386c8ef8a96dc42af1c7fb8460259798"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 860 J. Reynolds\n ISI\nObsoletes: NIC 16238 May 1983\n\n TELNET TIMING MARK OPTION\n\nThis RFC specifies a standard for the ARPA community. Hosts on the ARPA\nInternet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TIMING-MARK 6\n\n2. Command Meanings\n\n IAC DO TIMING-MARK\n\n The sender of this command REQUESTS that the receiver of this\n command return a WILL TIMING-MARK in the data stream at the\n \"appropriate place\" as defined in section 4 below.\n\n IAC WILL TIMING-MARK\n\n The sender of this command ASSURES the receiver of this command\n that it is inserted in the data stream at the \"appropriate place\"\n to insure synchronization with a DO TIMING-MARK transmitted by the\n receiver of this command.\n\n IAC WON'T TIMING-MARK\n\n The sender of this command REFUSES to insure that this command is\n inserted in the data stream a","scope_keywords":["860"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 860 Network Working Group J. Postel\nRequest for Comments: 860 J. Reynolds\n ISI\nObsoletes: NIC 16238 May 1983\n\n TELNET TIMING MARK OPTION\n\nThis RFC specifies a standard for the ARPA community. Hosts on the ARPA\nInternet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TIMING-MARK 6\n\n2. Command Meanings\n\n IAC DO TIMING-MARK\n\n The sender of this command REQUESTS that the receiver of this\n command return a WILL TIMING-MARK in the data stream at the\n \"appropriate place\" as defined in section 4 below.\n\n IAC WILL TIMING-MARK\n\n The sender of this command ASSURES the receiver of this command\n that it is inserted in the data stream at the \"appropriate place\"\n to insure synchronization with a DO TIMING-MARK transmitted by the\n receiver of this command.\n\n IAC WON'T TIMING-MARK\n\n The sender of this command REFUSES to insure that this command is\n inserted in the data stream a 860 nested-reference unchanged"},{"id":"IETF RFC 861","type":"specification","body":"IETF","designation":"RFC 861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc861.txt","https://www.rfc-editor.org/rfc/rfc861.pdf"],"folder":"IETF/RFC-861","files":{"txt":{"path":"standards/IETF/RFC-861/RFC-861.txt","sha256":"86fe6c61441b5405f72fdc26d66416f91d053759cc589666ef4fa7c4db827f20"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 861 J. Reynolds\n ISI\nObsoletes: NIC 16239 May 1983\n\n TELNET EXTENDED OPTIONS - LIST OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n EXTENDED-OPTIONS-LIST (EXOPL) 255\n\n2. Command Meanings\n\n IAC DO EXOPL\n\n The sender of this command REQUESTS that the receiver of this\n command begin negotiating, or confirms that the receiver of this\n command is expected to begin negotiating, TELNET options which are\n on the \"Extended Options List\".\n\n IAC WILL EXOPL\n\n The sender of this command requests permission to begin\n negotiating, or confirms that it will begin negotiating, TELNET\n options which are on the \"Extended Options List\".\n\n IAC WON'T EXOPL\n\n The sender of this command REFUSES to negotiate, or to continue\n negotiat","scope_keywords":["861"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 861 Network Working Group J. Postel\nRequest for Comments: 861 J. Reynolds\n ISI\nObsoletes: NIC 16239 May 1983\n\n TELNET EXTENDED OPTIONS - LIST OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n EXTENDED-OPTIONS-LIST (EXOPL) 255\n\n2. Command Meanings\n\n IAC DO EXOPL\n\n The sender of this command REQUESTS that the receiver of this\n command begin negotiating, or confirms that the receiver of this\n command is expected to begin negotiating, TELNET options which are\n on the \"Extended Options List\".\n\n IAC WILL EXOPL\n\n The sender of this command requests permission to begin\n negotiating, or confirms that it will begin negotiating, TELNET\n options which are on the \"Extended Options List\".\n\n IAC WON'T EXOPL\n\n The sender of this command REFUSES to negotiate, or to continue\n negotiat 861 nested-reference unchanged"},{"id":"IETF RFC 862","type":"specification","body":"IETF","designation":"RFC 862","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc862.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc862.txt","https://www.rfc-editor.org/rfc/rfc862.pdf"],"folder":"IETF/RFC-862","files":{"txt":{"path":"standards/IETF/RFC-862/RFC-862.txt","sha256":"7dea6a0ec5a964dc91ebf198040dbb179b7d626fef36c6096b7e2ca15dc90532"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 862 ISI\n May 1983\n\n Echo Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement an Echo Protocol are expected\nto adopt and implement this standard.\n\nA very useful debugging and measurement tool is an echo service. An\necho service simply sends back to the originating source any data it\nreceives.\n\nTCP Based Echo Service\n\n One echo service is defined as a connection based application on TCP.\n A server listens for TCP connections on TCP port 7. Once a\n connection is established any data received is sent back. This\n continues until the calling user terminates the connection.\n\nUDP Based Echo Service\n\n Another echo service is defined as a datagram based application on\n UDP. A server listens for UDP datagrams on UDP port 7. When a\n datagram is received, the data from it is ","scope_keywords":["862"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 2925","folder":"IETF/RFC-2925","source":"IETF/RFC-2925/RFC-2925.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4560","folder":"IETF/RFC-4560","source":"IETF/RFC-4560/RFC-4560.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 862 Network Working Group J. Postel\nRequest for Comments: 862 ISI\n May 1983\n\n Echo Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement an Echo Protocol are expected\nto adopt and implement this standard.\n\nA very useful debugging and measurement tool is an echo service. An\necho service simply sends back to the originating source any data it\nreceives.\n\nTCP Based Echo Service\n\n One echo service is defined as a connection based application on TCP.\n A server listens for TCP connections on TCP port 7. Once a\n connection is established any data received is sent back. This\n continues until the calling user terminates the connection.\n\nUDP Based Echo Service\n\n Another echo service is defined as a datagram based application on\n UDP. A server listens for UDP datagrams on UDP port 7. When a\n datagram is received, the data from it is  862 nested-reference unchanged"},{"id":"IETF RFC 8627","type":"specification","body":"IETF","designation":"RFC 8627","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8627.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8627.txt","https://www.rfc-editor.org/rfc/rfc8627.pdf"],"folder":"IETF/RFC-8627","files":{"txt":{"path":"standards/IETF/RFC-8627/RFC-8627.txt","sha256":"5ce7466024eb094dea82b71ce874332f026fa2962d9c25b7428a858ba40900a9"}},"tags":["nested-reference","unchanged"],"summary":"This document defines new RTP payload formats for the Forward Error\n Correction (FEC) packets that are generated by the non-interleaved\n and interleaved parity codes from source media encapsulated in RTP.\n These parity codes are systematic codes (Flexible FEC, or \"FLEX\n FEC\"), where a number of FEC repair packets are generated from a set\n of source packets from one or more source RTP streams. These FEC\n repair packets are sent in a redundancy RTP stream separate from the\n source RTP stream(s) that carries the source packets. RTP source\n packets that were lost in transmission can be reconstructed using the\n source and repair packets that were received. The non-interleaved\n and interleaved parity codes that are defined in this specification\n offer a good protection against random and bursty packet losses,\n respectively, at a cost of complexity. The RTP payload formats that\n are defined in ","scope_keywords":["8627","algorithm","http","https","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null},{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"IETF RFC 8627 This document defines new RTP payload formats for the Forward Error\n Correction (FEC) packets that are generated by the non-interleaved\n and interleaved parity codes from source media encapsulated in RTP.\n These parity codes are systematic codes (Flexible FEC, or \"FLEX\n FEC\"), where a number of FEC repair packets are generated from a set\n of source packets from one or more source RTP streams. These FEC\n repair packets are sent in a redundancy RTP stream separate from the\n source RTP stream(s) that carries the source packets. RTP source\n packets that were lost in transmission can be reconstructed using the\n source and repair packets that were received. The non-interleaved\n and interleaved parity codes that are defined in this specification\n offer a good protection against random and bursty packet losses,\n respectively, at a cost of complexity. The RTP payload formats that\n are defined in  8627 algorithm http https license subject trust nested-reference unchanged"},{"id":"IETF RFC 863","type":"specification","body":"IETF","designation":"RFC 863","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc863.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc863.txt","https://www.rfc-editor.org/rfc/rfc863.pdf"],"folder":"IETF/RFC-863","files":{"txt":{"path":"standards/IETF/RFC-863/RFC-863.txt","sha256":"4b4a68690f539b9851685ba6ce94c36cbcd607c6f5e64b97ab22b3ba6df5000b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 863 ISI\n May 1983\n\n Discard Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Discard Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a discard service. A discard\nservice simply throws away any data it receives.\n\nTCP Based Discard Service\n\n One discard service is defined as a connection based application on\n TCP. A server listens for TCP connections on TCP port 9. Once a\n connection is established any data received is thrown away. No\n response is sent. This continues until the calling user terminates\n the connection.\n\nUDP Based Discard Service\n\n Another discard service is defined as a datagram based application on\n UDP. A server listens for UDP datagrams on UDP port 9. When a\n datagram is received, it is","scope_keywords":["863"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 863 Network Working Group J. Postel\nRequest for Comments: 863 ISI\n May 1983\n\n Discard Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Discard Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a discard service. A discard\nservice simply throws away any data it receives.\n\nTCP Based Discard Service\n\n One discard service is defined as a connection based application on\n TCP. A server listens for TCP connections on TCP port 9. Once a\n connection is established any data received is thrown away. No\n response is sent. This continues until the calling user terminates\n the connection.\n\nUDP Based Discard Service\n\n Another discard service is defined as a datagram based application on\n UDP. A server listens for UDP datagrams on UDP port 9. When a\n datagram is received, it is 863 nested-reference unchanged"},{"id":"IETF RFC 864","type":"specification","body":"IETF","designation":"RFC 864","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc864.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc864.txt","https://www.rfc-editor.org/rfc/rfc864.pdf"],"folder":"IETF/RFC-864","files":{"txt":{"path":"standards/IETF/RFC-864/RFC-864.txt","sha256":"87b0090f49ba494d0a479ec05e792f82430796dfcde2d9ca32d8385afece57f0"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 864 ISI\n May 1983\n\n Character Generator Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Character Generator\nProtocol are expected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a character generator\nservice. A character generator service simply sends data without regard\nto the input.\n\nTCP Based Character Generator Service\n\n One character generator service is defined as a connection based\n application on TCP. A server listens for TCP connections on TCP port\n 19. Once a connection is established a stream of data is sent out\n the connection (and any data received is thrown away). This\n continues until the calling user terminates the connection.\n\n It is fairly likely that users of this service will abruptly decide\n that they h","scope_keywords":["864"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 864 Network Working Group J. Postel\nRequest for Comments: 864 ISI\n May 1983\n\n Character Generator Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Character Generator\nProtocol are expected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a character generator\nservice. A character generator service simply sends data without regard\nto the input.\n\nTCP Based Character Generator Service\n\n One character generator service is defined as a connection based\n application on TCP. A server listens for TCP connections on TCP port\n 19. Once a connection is established a stream of data is sent out\n the connection (and any data received is thrown away). This\n continues until the calling user terminates the connection.\n\n It is fairly likely that users of this service will abruptly decide\n that they h 864 nested-reference unchanged"},{"id":"IETF RFC 865","type":"specification","body":"IETF","designation":"RFC 865","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc865.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc865.txt","https://www.rfc-editor.org/rfc/rfc865.pdf"],"folder":"IETF/RFC-865","files":{"txt":{"path":"standards/IETF/RFC-865/RFC-865.txt","sha256":"4e97a3d229df5ef0d4796beace0a7116bc041c1291698dda59b0823a655d3e0c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 865 ISI\n May 1983\n\n Quote of the Day Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Quote of the Day Protocol\nare expected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a quote of the day service.\nA quote of the day service simply sends a short message without regard\nto the input.\n\nTCP Based Character Generator Service\n\n One quote of the day service is defined as a connection based\n application on TCP. A server listens for TCP connections on TCP port\n 17. Once a connection is established a short message is sent out the\n connection (and any data received is thrown away). The service\n closes the connection after sending the quote.\n\nUDP Based Character Generator Service\n\n Another quote of the day service is defined as a dat","scope_keywords":["865"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 865 Network Working Group J. Postel\nRequest for Comments: 865 ISI\n May 1983\n\n Quote of the Day Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Quote of the Day Protocol\nare expected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a quote of the day service.\nA quote of the day service simply sends a short message without regard\nto the input.\n\nTCP Based Character Generator Service\n\n One quote of the day service is defined as a connection based\n application on TCP. A server listens for TCP connections on TCP port\n 17. Once a connection is established a short message is sent out the\n connection (and any data received is thrown away). The service\n closes the connection after sending the quote.\n\nUDP Based Character Generator Service\n\n Another quote of the day service is defined as a dat 865 nested-reference unchanged"},{"id":"IETF RFC 866","type":"specification","body":"IETF","designation":"RFC 866","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc866.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc866.txt","https://www.rfc-editor.org/rfc/rfc866.pdf"],"folder":"IETF/RFC-866","files":{"txt":{"path":"standards/IETF/RFC-866/RFC-866.txt","sha256":"c31911965572c5a6f7feb370a850905ec07c688849039c2652a174f67cb5ad93"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 866 ISI\n May 1983\n\n Active Users\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement an Active Users Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is an active users service. An\nactive users service simply sends a list of the currently active users\non the host without regard to the input.\n\nAn active user is one logged in, such as listed in SYSTAT or WHO.\n\nTCP Based Active Users Service\n\n One active users service is defined as a connection based application\n on TCP. A server listens for TCP connections on TCP port 11. Once a\n connection is established a list of the currently active users is\n sent out the connection (and any data received is thrown away). The\n service closes the connection after sending the list.\n\nUDP B","scope_keywords":["866"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 866 Network Working Group J. Postel\nRequest for Comments: 866 ISI\n May 1983\n\n Active Users\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement an Active Users Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is an active users service. An\nactive users service simply sends a list of the currently active users\non the host without regard to the input.\n\nAn active user is one logged in, such as listed in SYSTAT or WHO.\n\nTCP Based Active Users Service\n\n One active users service is defined as a connection based application\n on TCP. A server listens for TCP connections on TCP port 11. Once a\n connection is established a list of the currently active users is\n sent out the connection (and any data received is thrown away). The\n service closes the connection after sending the list.\n\nUDP B 866 nested-reference unchanged"},{"id":"IETF RFC 867","type":"specification","body":"IETF","designation":"RFC 867","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc867.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc867.txt","https://www.rfc-editor.org/rfc/rfc867.pdf"],"folder":"IETF/RFC-867","files":{"txt":{"path":"standards/IETF/RFC-867/RFC-867.txt","sha256":"148a8dbd124245920f427a077527f031af12b37df4fb81d5f07115334ecdb765"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 867 ISI\n May 1983\n\n Daytime Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Daytime Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a daytime service. A daytime\nservice simply sends a the current date and time as a character string\nwithout regard to the input.\n\nTCP Based Daytime Service\n\n One daytime service is defined as a connection based application on\n TCP. A server listens for TCP connections on TCP port 13. Once a\n connection is established the current date and time is sent out the\n connection as a ascii character string (and any data received is\n thrown away). The service closes the connection after sending the\n quote.\n\nUDP Based Daytime Service\n\n Another daytime service service is defined as a ","scope_keywords":["867"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 867 Network Working Group J. Postel\nRequest for Comments: 867 ISI\n May 1983\n\n Daytime Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Daytime Protocol are\nexpected to adopt and implement this standard.\n\nA useful debugging and measurement tool is a daytime service. A daytime\nservice simply sends a the current date and time as a character string\nwithout regard to the input.\n\nTCP Based Daytime Service\n\n One daytime service is defined as a connection based application on\n TCP. A server listens for TCP connections on TCP port 13. Once a\n connection is established the current date and time is sent out the\n connection as a ascii character string (and any data received is\n thrown away). The service closes the connection after sending the\n quote.\n\nUDP Based Daytime Service\n\n Another daytime service service is defined as a  867 nested-reference unchanged"},{"id":"IETF RFC 868","type":"specification","body":"IETF","designation":"RFC 868","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc868.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc868.txt","https://www.rfc-editor.org/rfc/rfc868.pdf"],"folder":"IETF/RFC-868","files":{"txt":{"path":"standards/IETF/RFC-868/RFC-868.txt","sha256":"42d96cd4e0743f947be4dfe69a507aa1ab23fa0a1846ae9be67164ebba6bc2f8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel - ISI\nRequest for Comments: 868 K. Harrenstien - SRI\n May 1983\n\n Time Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Time Protocol are expected\nto adopt and implement this standard.\n\nThis protocol provides a site-independent, machine readable date and\ntime. The Time service sends back to the originating source the time in\nseconds since midnight on January first 1900.\n\nOne motivation arises from the fact that not all systems have a\ndate/time clock, and all are subject to occasional human or machine\nerror. The use of time-servers makes it possible to quickly confirm or\ncorrect a system's idea of the time, by making a brief poll of several\nindependent sites on the network.\n\nThis protocol may be used either above the Transmission Control Protocol\n(TCP) or above the User Datagram Pr","scope_keywords":["868","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0868","folder":"IETF/RFC-0868","source":"IETF/RFC-0868/RFC-0868.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1769","folder":"IETF/RFC-1769","source":"IETF/RFC-1769/RFC-1769.txt","version":null},{"body":"IETF","designation":"RFC 2030","folder":"IETF/RFC-2030","source":"IETF/RFC-2030/RFC-2030.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4330","folder":"IETF/RFC-4330","source":"IETF/RFC-4330/RFC-4330.txt","version":null},{"body":"IETF","designation":"RFC 7273","folder":"IETF/RFC-7273","source":"IETF/RFC-7273/RFC-7273.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 868 Network Working Group J. Postel - ISI\nRequest for Comments: 868 K. Harrenstien - SRI\n May 1983\n\n Time Protocol\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that choose to implement a Time Protocol are expected\nto adopt and implement this standard.\n\nThis protocol provides a site-independent, machine readable date and\ntime. The Time service sends back to the originating source the time in\nseconds since midnight on January first 1900.\n\nOne motivation arises from the fact that not all systems have a\ndate/time clock, and all are subject to occasional human or machine\nerror. The use of time-servers makes it possible to quickly confirm or\ncorrect a system's idea of the time, by making a brief poll of several\nindependent sites on the network.\n\nThis protocol may be used either above the Transmission Control Protocol\n(TCP) or above the User Datagram Pr 868 subject nested-reference unchanged"},{"id":"IETF RFC 869","type":"specification","body":"IETF","designation":"RFC 869","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc869.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc869.txt","https://www.rfc-editor.org/rfc/rfc869.pdf"],"folder":"IETF/RFC-869","files":{"txt":{"path":"standards/IETF/RFC-869/RFC-869.txt","sha256":"77aef3af039d79e1496dd13660e33391b3697a8a419a964d24a07840178fdc5d"}},"tags":["nested-reference","unchanged"],"summary":"RFC - 869\n\n A Host Monitoring Protocol\n\n Robert M. Hinden\n\n BBN Communications Corporation\n\n December 1983\n\n\f\nRFC-869 December 1983\n\n Table of Contents\n\n1 Introduction.......................................... 1\n\n2 General Description................................... 3\n\n3 Relationship to Other Protocols....................... 6\n\n4 Protocol Operation.................................... 7\n\n5 Header Formats....................................... 12\n5.1 IP Headers......................................... 12\n5.2 HMP Header......................................... 13\n\n6 HMP Monitoring Center Message Formats................ 16\n6.1 Message Type 100: Polling Message.................. 16\n6.2 Message Type 101: Error in Poll.................... 18\n6.3 Message Type 102: Control acknowledgment........... 20\n\nA Appendix A - IMP Monitoring.......................... 21\nA.1 Message Type 1: IMP Trap.....","scope_keywords":["869"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 869 RFC - 869\n\n A Host Monitoring Protocol\n\n Robert M. Hinden\n\n BBN Communications Corporation\n\n December 1983\n\n\f\nRFC-869 December 1983\n\n Table of Contents\n\n1 Introduction.......................................... 1\n\n2 General Description................................... 3\n\n3 Relationship to Other Protocols....................... 6\n\n4 Protocol Operation.................................... 7\n\n5 Header Formats....................................... 12\n5.1 IP Headers......................................... 12\n5.2 HMP Header......................................... 13\n\n6 HMP Monitoring Center Message Formats................ 16\n6.1 Message Type 100: Polling Message.................. 16\n6.2 Message Type 101: Error in Poll.................... 18\n6.3 Message Type 102: Control acknowledgment........... 20\n\nA Appendix A - IMP Monitoring.......................... 21\nA.1 Message Type 1: IMP Trap..... 869 nested-reference unchanged"},{"id":"IETF RFC 871","type":"specification","body":"IETF","designation":"RFC 871","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc871.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc871.txt","https://www.rfc-editor.org/rfc/rfc871.pdf"],"folder":"IETF/RFC-871","files":{"txt":{"path":"standards/IETF/RFC-871/RFC-871.txt","sha256":"163a501e6d2ef8ba7e90d22da1090456d864d6db008731d7e819b6ac0e0e539a"}},"tags":["nested-reference","unchanged"],"summary":"The paper, by one of its developers, describes the\n conceptual framework in which the ARPANET intercomputer\n networking protocol suite, including the DoD standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP),\n were designed. It also compares and contrasts several aspects of\n the ARPANET Reference Model (ARM) with the more widely publicized\n International Standards Organization's Reference Model for Open\n System Interconnection (ISORM).\n\n i\f\n \n \n \n \n \"A PERSPECTIVE ON THE ARPANET REFERENCE MODEL\"\n\n M. A. Padlipsky","scope_keywords":["871","key","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 871 The paper, by one of its developers, describes the\n conceptual framework in which the ARPANET intercomputer\n networking protocol suite, including the DoD standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP),\n were designed. It also compares and contrasts several aspects of\n the ARPANET Reference Model (ARM) with the more widely publicized\n International Standards Organization's Reference Model for Open\n System Interconnection (ISORM).\n\n i\f\n \n \n \n \n \"A PERSPECTIVE ON THE ARPANET REFERENCE MODEL\"\n\n M. A. Padlipsky 871 key path nested-reference unchanged"},{"id":"IETF RFC 872","type":"specification","body":"IETF","designation":"RFC 872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc872.txt","https://www.rfc-editor.org/rfc/rfc872.pdf"],"folder":"IETF/RFC-872","files":{"txt":{"path":"standards/IETF/RFC-872/RFC-872.txt","sha256":"57b1625fada4a4561285e6b6c848cce422c29fd4724fc169f363e0736617dc51"}},"tags":["nested-reference","unchanged"],"summary":"RFC 872 September 1982\n M82-48\n\n TCP-ON-A-LAN\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n Abstract\n \n\n \n\n The sometimes-held position that the DoD Standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP)\n are inappropriate for use \"on\" a Local Area Network (LAN) is\n shown to be fallacious. The paper is a companion piece to\n M82-47, M82-49, M82-50, and M82-51.\n\n i\f\n \n \n \n \n \"TCP-ON-A-LAN\"\n\n M. A. Padlipsky\n\n Thesis\n\n It is the thesis of this paper that fearing \"TCP-on-a-LAN\"\n is a Woozle which needs slaying. To slay the \"TCP-on-a-LAN\"\n Woozle, we need to know three things: What's a Woozle? What's a\n LAN? What's a TCP?\n\n Woozles\n\n The first is rather straightforward [1]:\n\n One fine winter's day when Piglet was brushing away the\n snow in front of his house, he happened to look up, and\n there was Winnie-the-Pooh. Pooh was walking round and rou","scope_keywords":["872"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0872","folder":"IETF/RFC-0872","source":"IETF/RFC-0872/RFC-0872.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null}],"search_text":"IETF RFC 872 RFC 872 September 1982\n M82-48\n\n TCP-ON-A-LAN\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n Abstract\n \n\n \n\n The sometimes-held position that the DoD Standard\n Transmission Control Protocol (TCP) and Internet Protocol (IP)\n are inappropriate for use \"on\" a Local Area Network (LAN) is\n shown to be fallacious. The paper is a companion piece to\n M82-47, M82-49, M82-50, and M82-51.\n\n i\f\n \n \n \n \n \"TCP-ON-A-LAN\"\n\n M. A. Padlipsky\n\n Thesis\n\n It is the thesis of this paper that fearing \"TCP-on-a-LAN\"\n is a Woozle which needs slaying. To slay the \"TCP-on-a-LAN\"\n Woozle, we need to know three things: What's a Woozle? What's a\n LAN? What's a TCP?\n\n Woozles\n\n The first is rather straightforward [1]:\n\n One fine winter's day when Piglet was brushing away the\n snow in front of his house, he happened to look up, and\n there was Winnie-the-Pooh. Pooh was walking round and rou 872 nested-reference unchanged"},{"id":"IETF RFC 8737","type":"specification","body":"IETF","designation":"RFC 8737","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8737.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8737.txt","https://www.rfc-editor.org/rfc/rfc8737.pdf"],"folder":"IETF/RFC-8737","files":{"pdf":{"path":"standards/IETF/RFC-8737/RFC-8737.pdf","sha256":"3feba9f03a031c1952c003c70f0f9bc179f1e9b2ef9e6880532b01fe3b989789"},"txt":{"path":"standards/IETF/RFC-8737/RFC-8737.txt","sha256":"d8b5604a01e762f4e8eb6650b05b94c5ee9646b4c2c46b6a87bfbcb64bd122bc"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies a new challenge for the Automated Certificate\n Management Environment (ACME) protocol that allows for domain control\n validation using TLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8737.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IE","scope_keywords":["8737","authorization","certificate","http","https","key","license","management","pki","signature","subject","tls","trust","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8738","folder":"IETF/RFC-8738","source":"IETF/RFC-8738/RFC-8738.txt","version":null}],"search_text":"IETF RFC 8737 This document specifies a new challenge for the Automated Certificate\n Management Environment (ACME) protocol that allows for domain control\n validation using TLS.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8737.\n\nCopyright Notice\n\n Copyright (c) 2020 IETF Trust and the persons identified as the\n document authors. All rights reserved.\n\n This document is subject to BCP 78 and the IE 8737 authorization certificate http https key license management pki signature subject tls trust validation nested-reference unchanged"},{"id":"IETF RFC 875","type":"specification","body":"IETF","designation":"RFC 875","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc875.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc875.txt","https://www.rfc-editor.org/rfc/rfc875.pdf"],"folder":"IETF/RFC-875","files":{"txt":{"path":"standards/IETF/RFC-875/RFC-875.txt","sha256":"fede34c5a2df5cde4365773dc3bc3c0486de7c6e5aa0cbc764ec05112c55675e"}},"tags":["nested-reference","unchanged"],"summary":"RFC 875 September 1982\n M82-51\n\n Gateways, Architectures, and Heffalumps\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n ABSTRACT\n \n\n \n\n The growth of autonomous intercomputer networks has led to a\n desire on the part of their respective proprietors to \"gateway\"\n from one to the other. Unfortunately, however, the implications\n and shortcomings of gateways which must translate or map between\n differing protocol suites are not widely understood. Some\n protocol sets have such severe functionality mismatches that\n proper T/MG's cannot be generated for them; all attempts to mesh\n heterogeneous suites are subject to numerous problems, including\n the introduction of \"singularity points\" on logical connections\n which would otherwise be able to enjoy the advantages of\n communications subnetwork alternate routing, loss of\n functionality, difficulty of Flow Control reso","scope_keywords":["875","key","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null}],"search_text":"IETF RFC 875 RFC 875 September 1982\n M82-51\n\n Gateways, Architectures, and Heffalumps\n\n \n \n\n \n\n M.A. PADLIPSKY\n THE MITRE CORPORATION\n Bedford, Massachusetts\f\n \n\n ABSTRACT\n \n\n \n\n The growth of autonomous intercomputer networks has led to a\n desire on the part of their respective proprietors to \"gateway\"\n from one to the other. Unfortunately, however, the implications\n and shortcomings of gateways which must translate or map between\n differing protocol suites are not widely understood. Some\n protocol sets have such severe functionality mismatches that\n proper T/MG's cannot be generated for them; all attempts to mesh\n heterogeneous suites are subject to numerous problems, including\n the introduction of \"singularity points\" on logical connections\n which would otherwise be able to enjoy the advantages of\n communications subnetwork alternate routing, loss of\n functionality, difficulty of Flow Control reso 875 key subject nested-reference unchanged"},{"id":"IETF RFC 877","type":"specification","body":"IETF","designation":"RFC 877","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc877.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc877.txt","https://www.rfc-editor.org/rfc/rfc877.pdf"],"folder":"IETF/RFC-877","files":{"txt":{"path":"standards/IETF/RFC-877/RFC-877.txt","sha256":"fb8dcccb87f70d8462ac7bc740522cc0850e14aa210a90c08f2e9638efa901e6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. T. Korb\nRequest for Comments: 877 Purdue University\n September 1983\n\n A Standard for the Transmission of IP Datagrams\n Over\n Public Data Networks\n\nThis RFC specifies a standard adopted by CSNET, the VAN gateway, and\nother organizations for the transmission of IP datagrams over the\nX.25-based public data networks. \n\nAn X.25 virtual circuit is opened on demand when a datagram arrives at\nthe network interface for transmission. A virtual circuit is closed\nafter some period of inactivity (the length of the period depends on\nthe cost associated with an open virtual circuit). A virtual circuit\nmay also be closed if the interface runs out of virtual circuits. An\nalgorithm for managing virtual circuits during peak demand is given\nin [1].\n\nSTANDARDS\n\n1.1 The first octet in the Call User Data Field (the first data octet\n in the Call Request packet) is used for protocol demu","scope_keywords":["877","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1183","folder":"IETF/RFC-1183","source":"IETF/RFC-1183/RFC-1183.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 870","folder":"IETF/RFC-870","source":"IETF/RFC-870/RFC-870.txt","version":null},{"body":"IETF","designation":"RFC 880","folder":"IETF/RFC-880","source":"IETF/RFC-880/RFC-880.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 877 Network Working Group J. T. Korb\nRequest for Comments: 877 Purdue University\n September 1983\n\n A Standard for the Transmission of IP Datagrams\n Over\n Public Data Networks\n\nThis RFC specifies a standard adopted by CSNET, the VAN gateway, and\nother organizations for the transmission of IP datagrams over the\nX.25-based public data networks. \n\nAn X.25 virtual circuit is opened on demand when a datagram arrives at\nthe network interface for transmission. A virtual circuit is closed\nafter some period of inactivity (the length of the period depends on\nthe cost associated with an open virtual circuit). A virtual circuit\nmay also be closed if the interface runs out of virtual circuits. An\nalgorithm for managing virtual circuits during peak demand is given\nin [1].\n\nSTANDARDS\n\n1.1 The first octet in the Call User Data Field (the first data octet\n in the Call Request packet) is used for protocol demu 877 algorithm nested-reference unchanged"},{"id":"IETF RFC 881","type":"specification","body":"IETF","designation":"RFC 881","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc881.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc881.txt","https://www.rfc-editor.org/rfc/rfc881.pdf"],"folder":"IETF/RFC-881","files":{"txt":{"path":"standards/IETF/RFC-881/RFC-881.txt","sha256":"80e3ae65b798c5d0469854a3755fbee67c0888efcf89b8e630b454538ab9feb2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 881 ISI\n November 1983\n\n The Domain Names Plan and Schedule\n\nThis RFC outlines a plan and schedule for the implementation of domain\nstyle names throughout the DDN/ARPA Internet community. The\nintroduction of domain style names will impact all hosts on the DDN/ARPA\nInternet.\n\nThe Plan\n\n Introduction\n\n Domain style names are being introduced in the Internet to allow a\n controlled delegation of the authority and responsibility for\n adding hosts to the system. This also allows a subdivision of the\n task of maintaining information about hosts.\n\n The subdivision will be based on administrative authority or\n organization boundaries (not necessarily network boundaries).\n Certain requirements will be placed on organizations wishing to be\n \"top level\" domains. Initially, all the hosts in the Internet\n will be in the domain \"ARPA\". As soon as is","scope_keywords":["881","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0881","folder":"IETF/RFC-0881","source":"IETF/RFC-0881/RFC-0881.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 3245","folder":"IETF/RFC-3245","source":"IETF/RFC-3245/RFC-3245.txt","version":null},{"body":"IETF","designation":"RFC 897","folder":"IETF/RFC-897","source":"IETF/RFC-897/RFC-897.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 921","folder":"IETF/RFC-921","source":"IETF/RFC-921/RFC-921.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 881 Network Working Group J. Postel\nRequest for Comments: 881 ISI\n November 1983\n\n The Domain Names Plan and Schedule\n\nThis RFC outlines a plan and schedule for the implementation of domain\nstyle names throughout the DDN/ARPA Internet community. The\nintroduction of domain style names will impact all hosts on the DDN/ARPA\nInternet.\n\nThe Plan\n\n Introduction\n\n Domain style names are being introduced in the Internet to allow a\n controlled delegation of the authority and responsibility for\n adding hosts to the system. This also allows a subdivision of the\n task of maintaining information about hosts.\n\n The subdivision will be based on administrative authority or\n organization boundaries (not necessarily network boundaries).\n Certain requirements will be placed on organizations wishing to be\n \"top level\" domains. Initially, all the hosts in the Internet\n will be in the domain \"ARPA\". As soon as is 881 management nested-reference unchanged"},{"id":"IETF RFC 897","type":"specification","body":"IETF","designation":"RFC 897","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc897.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc897.txt","https://www.rfc-editor.org/rfc/rfc897.pdf"],"folder":"IETF/RFC-897","files":{"txt":{"path":"standards/IETF/RFC-897/RFC-897.txt","sha256":"f94409939f3fc98276f27e41d3535c15f31f44b48feb358636c89b4b5513c18a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 897 ISI\n February 1984\nUpdates: RFC 881\n\n Domain Name System Implementation Schedule\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Domain\n Style Naming System in the Internet. This memo is a partial update\n of RFC 881. This is an official policy statement of the ICCB and the\n DARPA.\n\n The intent of this memo is to detail the schedule for the\n implementation for the Domain Style Naming System. The explanation\n of how this system works is to be found in the references.\n\nThe Current Situation\n\n Simple Names\n\n Hosts in the ARPA research and DDN operational communities are\n currently assigned names in a flat or global name space of\n character strings. There are some limits on these names. They\n must start with a letter, end with a letter or digit and have only\n letters or digits or hyphen as interior ","scope_keywords":["897","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 915","folder":"IETF/RFC-915","source":"IETF/RFC-915/RFC-915.txt","version":null},{"body":"IETF","designation":"RFC 921","folder":"IETF/RFC-921","source":"IETF/RFC-921/RFC-921.txt","version":null}],"search_text":"IETF RFC 897 Network Working Group Jon Postel\nRequest for Comments: 897 ISI\n February 1984\nUpdates: RFC 881\n\n Domain Name System Implementation Schedule\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Domain\n Style Naming System in the Internet. This memo is a partial update\n of RFC 881. This is an official policy statement of the ICCB and the\n DARPA.\n\n The intent of this memo is to detail the schedule for the\n implementation for the Domain Style Naming System. The explanation\n of how this system works is to be found in the references.\n\nThe Current Situation\n\n Simple Names\n\n Hosts in the ARPA research and DDN operational communities are\n currently assigned names in a flat or global name space of\n character strings. There are some limits on these names. They\n must start with a letter, end with a letter or digit and have only\n letters or digits or hyphen as interior  897 policy nested-reference unchanged"},{"id":"IETF RFC 921","type":"specification","body":"IETF","designation":"RFC 921","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc921.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc921.txt","https://www.rfc-editor.org/rfc/rfc921.pdf"],"folder":"IETF/RFC-921","files":{"txt":{"path":"standards/IETF/RFC-921/RFC-921.txt","sha256":"1ea0a85d092e97f0f6d501c9d50e1954ee6e970216fdd645afe86abfe3e36553"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 921 ISI\n October 1984\nUpdates: RFC 897, RFC 881\n\n Domain Name System Implementation Schedule - Revised\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Domain\n Style Naming System in the Internet. This memo is an update of\n RFC-881, and RFC-897. This is an official policy statement of the\n IAB and the DARPA. Distribution of this memo is unlimited.\n\n The intent of this memo is to detail the schedule for the\n implementation for the Domain Style Naming System. The explanation\n of how this system works is to be found in the references.\n\nThe Current Situation\n\n There are three aspects to the domain style naming system, (1) the\n names themselves, (2) the method of translating names to addresses,\n and (3) the relationship between the Internet and the rest of the\n world.\n\n Names\n\n The names are being change","scope_keywords":["921","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 921 Network Working Group Jon Postel\nRequest for Comments: 921 ISI\n October 1984\nUpdates: RFC 897, RFC 881\n\n Domain Name System Implementation Schedule - Revised\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Domain\n Style Naming System in the Internet. This memo is an update of\n RFC-881, and RFC-897. This is an official policy statement of the\n IAB and the DARPA. Distribution of this memo is unlimited.\n\n The intent of this memo is to detail the schedule for the\n implementation for the Domain Style Naming System. The explanation\n of how this system works is to be found in the references.\n\nThe Current Situation\n\n There are three aspects to the domain style naming system, (1) the\n names themselves, (2) the method of translating names to addresses,\n and (3) the relationship between the Internet and the rest of the\n world.\n\n Names\n\n The names are being change 921 policy nested-reference unchanged"},{"id":"IETF RFC 8825","type":"specification","body":"IETF","designation":"RFC 8825","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8825.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8825.txt","https://www.rfc-editor.org/rfc/rfc8825.pdf"],"folder":"IETF/RFC-8825","files":{"pdf":{"path":"standards/IETF/RFC-8825/RFC-8825.pdf","sha256":"f6f3990bd6a84d1060e73d7fd1be77b8b550fcebdae9c606fef03be4402de967"},"txt":{"path":"standards/IETF/RFC-8825/RFC-8825.txt","sha256":"ab8097517c0a807e06b3168331edbde290f905dae50db0907e6f31b6da0ec7d3"}},"tags":["nested-reference","unchanged"],"summary":"This document gives an overview and context of a protocol suite\n intended for use with real-time applications that can be deployed in\n browsers -- \"real-time communication on the Web\".\n\n It intends to serve as a starting and coordination point to make sure\n that (1) all the parts that are needed to achieve this goal are\n findable and (2) the parts that belong in the Internet protocol suite\n are fully specified and on the right publication track.\n\n This document is an applicability statement -- it does not itself\n specify any protocol, but it specifies which other specifications\n implementations are supposed to follow to be compliant with Web Real-\n Time Communication (WebRTC).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received ","scope_keywords":["8825","attribute","http","https","identification","license","management","presentation","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8826","folder":"IETF/RFC-8826","source":"IETF/RFC-8826/RFC-8826.txt","version":null},{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8830","folder":"IETF/RFC-8830","source":"IETF/RFC-8830/RFC-8830.txt","version":null},{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8825 This document gives an overview and context of a protocol suite\n intended for use with real-time applications that can be deployed in\n browsers -- \"real-time communication on the Web\".\n\n It intends to serve as a starting and coordination point to make sure\n that (1) all the parts that are needed to achieve this goal are\n findable and (2) the parts that belong in the Internet protocol suite\n are fully specified and on the right publication track.\n\n This document is an applicability statement -- it does not itself\n specify any protocol, but it specifies which other specifications\n implementations are supposed to follow to be compliant with Web Real-\n Time Communication (WebRTC).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received  8825 attribute http https identification license management presentation subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8835","type":"specification","body":"IETF","designation":"RFC 8835","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8835.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8835.txt","https://www.rfc-editor.org/rfc/rfc8835.pdf"],"folder":"IETF/RFC-8835","files":{"pdf":{"path":"standards/IETF/RFC-8835/RFC-8835.pdf","sha256":"2dc7102b74419722adc758a7b29c5974bd8e417c5f7bfa8dc6567e5ac4024e10"},"txt":{"path":"standards/IETF/RFC-8835/RFC-8835.txt","sha256":"b108121d42e09ea16973f23dd0d6ad395d43d4bbc2f4490ecc14b34cae50aa88"}},"tags":["nested-reference","unchanged"],"summary":"This document describes the data transport protocols used by Web\n Real-Time Communication (WebRTC), including the protocols used for\n interaction with intermediate boxes such as firewalls, relays, and\n NAT boxes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8835.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved","scope_keywords":["8835","http","https","key","license","policy","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8828","folder":"IETF/RFC-8828","source":"IETF/RFC-8828/RFC-8828.txt","version":null}],"search_text":"IETF RFC 8835 This document describes the data transport protocols used by Web\n Real-Time Communication (WebRTC), including the protocols used for\n interaction with intermediate boxes such as firewalls, relays, and\n NAT boxes.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8835.\n\nCopyright Notice\n\n Copyright (c) 2021 IETF Trust and the persons identified as the\n document authors. All rights reserved 8835 http https key license policy subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8836","type":"specification","body":"IETF","designation":"RFC 8836","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8836.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8836.txt","https://www.rfc-editor.org/rfc/rfc8836.pdf"],"folder":"IETF/RFC-8836","files":{"pdf":{"path":"standards/IETF/RFC-8836/RFC-8836.pdf","sha256":"e366d37bfed889fbe90e095be9078da9958186342e4dbbf45a8ecb2e22f9afd2"},"txt":{"path":"standards/IETF/RFC-8836/RFC-8836.txt","sha256":"b124b69c5f067cabac4beac23c55dc1cae15be94b802a66f1649db64b01056a6"}},"tags":["nested-reference","unchanged"],"summary":"Congestion control is needed for all data transported across the\n Internet, in order to promote fair usage and prevent congestion\n collapse. The requirements for interactive, point-to-point real-time\n multimedia, which needs low-delay, semi-reliable data delivery, are\n different from the requirements for bulk transfer like FTP or bursty\n transfers like web pages. Due to an increasing amount of RTP-based\n real-time media traffic on the Internet (e.g., with the introduction\n of the Web Real-Time Communication (WebRTC)), it is especially\n important to ensure that this kind of traffic is congestion\n controlled.\n\n This document describes a set of requirements that can be used to\n evaluate other congestion control mechanisms in order to figure out\n their fitness for this purpose, and in particular to provide a set of\n possible requirements for a real-time media congestion avoidance\n technique.","scope_keywords":["8836","algorithm","algorithms","delivery","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8836 Congestion control is needed for all data transported across the\n Internet, in order to promote fair usage and prevent congestion\n collapse. The requirements for interactive, point-to-point real-time\n multimedia, which needs low-delay, semi-reliable data delivery, are\n different from the requirements for bulk transfer like FTP or bursty\n transfers like web pages. Due to an increasing amount of RTP-based\n real-time media traffic on the Internet (e.g., with the introduction\n of the Web Real-Time Communication (WebRTC)), it is especially\n important to ensure that this kind of traffic is congestion\n controlled.\n\n This document describes a set of requirements that can be used to\n evaluate other congestion control mechanisms in order to figure out\n their fitness for this purpose, and in particular to provide a set of\n possible requirements for a real-time media congestion avoidance\n technique. 8836 algorithm algorithms delivery http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8837","type":"specification","body":"IETF","designation":"RFC 8837","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8837.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8837.txt","https://www.rfc-editor.org/rfc/rfc8837.pdf"],"folder":"IETF/RFC-8837","files":{"pdf":{"path":"standards/IETF/RFC-8837/RFC-8837.pdf","sha256":"3de829c6c62afda4fa607fc46757fd97bc36eed56f0e60d7303db5e4ef45d35b"},"txt":{"path":"standards/IETF/RFC-8837/RFC-8837.txt","sha256":"2b13881b73d012384b4824256ce19a56b198992670d31d3d8f4498d19f01cb63"}},"tags":["nested-reference","unchanged"],"summary":"Networks can provide different forwarding treatments for individual\n packets based on Differentiated Services Code Point (DSCP) values on\n a per-hop basis. This document provides the recommended DSCP values\n for web browsers to use for various classes of Web Real-Time\n Communication (WebRTC) traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8837.\n\nCopyright Notice\n\n Copyright (c)","scope_keywords":["8837","authorization","http","https","key","license","policies","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8837 Networks can provide different forwarding treatments for individual\n packets based on Differentiated Services Code Point (DSCP) values on\n a per-hop basis. This document provides the recommended DSCP values\n for web browsers to use for various classes of Web Real-Time\n Communication (WebRTC) traffic.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtained at\n https://www.rfc-editor.org/info/rfc8837.\n\nCopyright Notice\n\n Copyright (c) 8837 authorization http https key license policies subject trust nested-reference unchanged"},{"id":"IETF RFC 884","type":"specification","body":"IETF","designation":"RFC 884","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc884.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc884.txt","https://www.rfc-editor.org/rfc/rfc884.pdf"],"folder":"IETF/RFC-884","files":{"txt":{"path":"standards/IETF/RFC-884/RFC-884.txt","sha256":"6c769adc96aa2aadfefb49763c07faf50af08f784aa57225df9d4470cd9fc078"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Marvin Solomon\nRequest for Comments: 884 Edward Wimmers\n University of Wisconsin - Madison\n December 1983\n\n TELNET TERMINAL TYPE OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that exchange terminal type information within the\nTelnet protocol are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation\n\n IAC DO TERMINAL-TYPE\n\n Sender is willing to receive terminal type information in a\n subsequent sub-negotiation\n\n IAC DON'T TERMINAL-TYPE\n\n Sender refuses to accept terminal type information\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send terminal type information\n\n IAC SB TERMINAL-TYPE SEND IAC SE\n\n Sender requests receiver to transmit his (the rec","scope_keywords":["884"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 930","folder":"IETF/RFC-930","source":"IETF/RFC-930/RFC-930.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 884 Network Working Group Marvin Solomon\nRequest for Comments: 884 Edward Wimmers\n University of Wisconsin - Madison\n December 1983\n\n TELNET TERMINAL TYPE OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that exchange terminal type information within the\nTelnet protocol are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation\n\n IAC DO TERMINAL-TYPE\n\n Sender is willing to receive terminal type information in a\n subsequent sub-negotiation\n\n IAC DON'T TERMINAL-TYPE\n\n Sender refuses to accept terminal type information\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send terminal type information\n\n IAC SB TERMINAL-TYPE SEND IAC SE\n\n Sender requests receiver to transmit his (the rec 884 nested-reference unchanged"},{"id":"IETF RFC 930","type":"specification","body":"IETF","designation":"RFC 930","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc930.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc930.txt","https://www.rfc-editor.org/rfc/rfc930.pdf"],"folder":"IETF/RFC-930","files":{"txt":{"path":"standards/IETF/RFC-930/RFC-930.txt","sha256":"1b051da01bd6a32cfec4068c362f3df620139dd8a683166052f0829c26c893c2"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Marvin Solomon\nRequest for Comments: 930 Edward Wimmers\nSupersedes: RFC 884 University of Wisconsin - Madison\n January 1985\n\n TELNET TERMINAL TYPE OPTION\n\nStatus of This Memo\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n on the ARPA Internet that exchange terminal type information within\n the Telnet protocol are expected to adopt and implement this\n standard. Distribution of this memo is unlimited.\n\n This standard supersedes RFC 884. The only change is to specify that\n the TERMINAL-TYPE IS sub-negotiation should be sent only in response\n to the TERMINAL-TYPE SEND sub-negotiation. See below for further\n explanation.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send ","scope_keywords":["930"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1079","folder":"IETF/RFC-1079","source":"IETF/RFC-1079/RFC-1079.txt","version":null},{"body":"IETF","designation":"RFC 1091","folder":"IETF/RFC-1091","source":"IETF/RFC-1091/RFC-1091.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 930 Network Working Group Marvin Solomon\nRequest for Comments: 930 Edward Wimmers\nSupersedes: RFC 884 University of Wisconsin - Madison\n January 1985\n\n TELNET TERMINAL TYPE OPTION\n\nStatus of This Memo\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n on the ARPA Internet that exchange terminal type information within\n the Telnet protocol are expected to adopt and implement this\n standard. Distribution of this memo is unlimited.\n\n This standard supersedes RFC 884. The only change is to specify that\n the TERMINAL-TYPE IS sub-negotiation should be sent only in response\n to the TERMINAL-TYPE SEND sub-negotiation. See below for further\n explanation.\n\n1. Command Name and Code\n\n TERMINAL-TYPE 24\n\n2. Command Meanings\n\n IAC WILL TERMINAL-TYPE\n\n Sender is willing to send terminal type information in a\n subsequent sub-negotiation\n\n IAC WON'T TERMINAL-TYPE\n\n Sender refuses to send  930 nested-reference unchanged"},{"id":"IETF RFC 8844","type":"specification","body":"IETF","designation":"RFC 8844","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8844.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8844.txt","https://www.rfc-editor.org/rfc/rfc8844.pdf"],"folder":"IETF/RFC-8844","files":{"pdf":{"path":"standards/IETF/RFC-8844/RFC-8844.pdf","sha256":"2dda9e1cc69c7b0c53975aea54951562cabf5704802e08dd70cadae9e24f009f"},"txt":{"path":"standards/IETF/RFC-8844/RFC-8844.txt","sha256":"415790c0d11e44578bde913f33da68f7d9a7ab3768b6ef04da847e93d9898c43"}},"tags":["nested-reference","unchanged"],"summary":"This document describes unknown key-share attacks on the use of\n Datagram Transport Layer Security for the Secure Real-Time Transport\n Protocol (DTLS-SRTP). Similar attacks are described on the use of\n DTLS-SRTP with the identity bindings used in Web Real-Time\n Communications (WebRTC) and SIP identity. These attacks are\n difficult to mount, but they cause a victim to be misled about the\n identity of a communicating peer. This document defines mitigation\n techniques that implementations of RFC 8122 are encouraged to deploy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availab","scope_keywords":["8844","attribute","authentication","certificate","hash","http","https","key","license","subject","tls","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8827","folder":"IETF/RFC-8827","source":"IETF/RFC-8827/RFC-8827.txt","version":null},{"body":"IETF","designation":"RFC 8842","folder":"IETF/RFC-8842","source":"IETF/RFC-8842/RFC-8842.txt","version":null}],"search_text":"IETF RFC 8844 This document describes unknown key-share attacks on the use of\n Datagram Transport Layer Security for the Secure Real-Time Transport\n Protocol (DTLS-SRTP). Similar attacks are described on the use of\n DTLS-SRTP with the identity bindings used in Web Real-Time\n Communications (WebRTC) and SIP identity. These attacks are\n difficult to mount, but they cause a victim to be misled about the\n identity of a communicating peer. This document defines mitigation\n techniques that implementations of RFC 8122 are encouraged to deploy.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is availab 8844 attribute authentication certificate hash http https key license subject tls trust nested-reference unchanged"},{"id":"IETF RFC 8845","type":"specification","body":"IETF","designation":"RFC 8845","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8845.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8845.txt","https://www.rfc-editor.org/rfc/rfc8845.pdf"],"folder":"IETF/RFC-8845","files":{"pdf":{"path":"standards/IETF/RFC-8845/RFC-8845.pdf","sha256":"b50e73876a2ad86610f7011e262f115a0cbbafcef4e8ce1869d16f577bfa1739"},"txt":{"path":"standards/IETF/RFC-8845/RFC-8845.txt","sha256":"69c3cc0e035bed554b3ce26721cacf7d39c6694722777040acce37bdc0873357"}},"tags":["nested-reference","unchanged"],"summary":"This document defines a framework for a protocol to enable devices in\n a telepresence conference to interoperate. The protocol enables\n communication of information about multiple media streams so a\n sending system and receiving system can make reasonable decisions\n about transmitting, selecting, and rendering the media streams. This\n protocol is used in addition to SIP signaling and Session Description\n Protocol (SDP) negotiation for setting up a telepresence session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the cu","scope_keywords":["8845","attribute","attributes","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null}],"search_text":"IETF RFC 8845 This document defines a framework for a protocol to enable devices in\n a telepresence conference to interoperate. The protocol enables\n communication of information about multiple media streams so a\n sending system and receiving system can make reasonable decisions\n about transmitting, selecting, and rendering the media streams. This\n protocol is used in addition to SIP signaling and Session Description\n Protocol (SDP) negotiation for setting up a telepresence session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the cu 8845 attribute attributes http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 8846","type":"specification","body":"IETF","designation":"RFC 8846","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8846.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8846.txt","https://www.rfc-editor.org/rfc/rfc8846.pdf"],"folder":"IETF/RFC-8846","files":{"pdf":{"path":"standards/IETF/RFC-8846/RFC-8846.pdf","sha256":"89cade51c62acf303482126ffbb2b925035b27a91f810011809adf146edc2684"},"txt":{"path":"standards/IETF/RFC-8846/RFC-8846.txt","sha256":"e79a74f517195d59a74e4919d3407b413fc6b2c30e9537db0d1cb90228a3137c"}},"tags":["nested-reference","unchanged"],"summary":"This document provides an XML schema file for the definition of CLUE\n data model types. The term \"CLUE\" stands for \"Controlling Multiple\n Streams for Telepresence\" and is the name of the IETF working group\n in which this document, as well as other companion documents, has\n been developed. The document defines a coherent structure for\n information associated with the description of a telepresence\n scenario.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide f","scope_keywords":["8846","attribute","attributes","http","https","key","license","pid","policy","presentation","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8847","folder":"IETF/RFC-8847","source":"IETF/RFC-8847/RFC-8847.txt","version":null},{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null}],"search_text":"IETF RFC 8846 This document provides an XML schema file for the definition of CLUE\n data model types. The term \"CLUE\" stands for \"Controlling Multiple\n Streams for Telepresence\" and is the name of the IETF working group\n in which this document, as well as other companion documents, has\n been developed. The document defines a coherent structure for\n information associated with the description of a telepresence\n scenario.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide f 8846 attribute attributes http https key license pid policy presentation subject trust nested-reference unchanged"},{"id":"IETF RFC 8849","type":"specification","body":"IETF","designation":"RFC 8849","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8849.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8849.txt","https://www.rfc-editor.org/rfc/rfc8849.pdf"],"folder":"IETF/RFC-8849","files":{"pdf":{"path":"standards/IETF/RFC-8849/RFC-8849.pdf","sha256":"80e2bfcdd17393f500bd45395fd282989df34a707232f3c69e21a500278b9b13"},"txt":{"path":"standards/IETF/RFC-8849/RFC-8849.txt","sha256":"9aea092813c394c6f9cb97bfd79f8fe2c9365311a679b8d6a92e144237af5766"}},"tags":["nested-reference","unchanged"],"summary":"This document describes how the Real-time Transport Protocol (RTP) is\n used in the context of the Controlling Multiple Streams for\n Telepresence (CLUE) protocol. It also describes the mechanisms and\n recommended practice for mapping RTP media streams, as defined in the\n Session Description Protocol (SDP), to CLUE Media Captures and\n defines a new RTP header extension (CaptureID).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain","scope_keywords":["8849","attribute","http","https","key","license","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8848","folder":"IETF/RFC-8848","source":"IETF/RFC-8848/RFC-8848.txt","version":null}],"search_text":"IETF RFC 8849 This document describes how the Real-time Transport Protocol (RTP) is\n used in the context of the Controlling Multiple Streams for\n Telepresence (CLUE) protocol. It also describes the mechanisms and\n recommended practice for mapping RTP media streams, as defined in the\n Session Description Protocol (SDP), to CLUE Media Captures and\n defines a new RTP header extension (CaptureID).\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may be obtain 8849 attribute http https key license subject trust nested-reference unchanged"},{"id":"IETF RFC 885","type":"specification","body":"IETF","designation":"RFC 885","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc885.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc885.txt","https://www.rfc-editor.org/rfc/rfc885.pdf"],"folder":"IETF/RFC-885","files":{"txt":{"path":"standards/IETF/RFC-885/RFC-885.txt","sha256":"83474720f991c0763b267dcceb055da474ce132fce898d0b102fe690d302c88b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 885 ISI\n December 1983\n\n TELNET END OF RECORD OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that need to mark record boundaries within Telnet\nprotocol data are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n END-OF-RECORD 25\n\n2. Command Meanings\n\n IAC WILL END-OF-RECORD\n\n The sender of this command requests permission to begin\n transmission of the Telnet END-OF-RECORD (EOR) code when\n transmitting data characters, or the sender of this command\n confirms it will now begin transmission of EORs with transmitted\n data characters.\n\n IAC WON'T END-OF-RECORD\n\n The sender of this command demands to stop transmitting, or to\n refuses to begin transmitting, the EOR code when transmitting data\n characters.\n\n IAC DO END-OF-RECORD\n\n The sender of this command requests th","scope_keywords":["885","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1576","folder":"IETF/RFC-1576","source":"IETF/RFC-1576/RFC-1576.txt","version":null},{"body":"IETF","designation":"RFC 1647","folder":"IETF/RFC-1647","source":"IETF/RFC-1647/RFC-1647.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2066","folder":"IETF/RFC-2066","source":"IETF/RFC-2066/RFC-2066.txt","version":null},{"body":"IETF","designation":"RFC 2355","folder":"IETF/RFC-2355","source":"IETF/RFC-2355/RFC-2355.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 885 Network Working Group J. Postel\nRequest for Comments: 885 ISI\n December 1983\n\n TELNET END OF RECORD OPTION\n\nThis RFC specifies a standard for the ARPA Internet community. Hosts on\nthe ARPA Internet that need to mark record boundaries within Telnet\nprotocol data are expected to adopt and implement this standard.\n\n1. Command Name and Code\n\n END-OF-RECORD 25\n\n2. Command Meanings\n\n IAC WILL END-OF-RECORD\n\n The sender of this command requests permission to begin\n transmission of the Telnet END-OF-RECORD (EOR) code when\n transmitting data characters, or the sender of this command\n confirms it will now begin transmission of EORs with transmitted\n data characters.\n\n IAC WON'T END-OF-RECORD\n\n The sender of this command demands to stop transmitting, or to\n refuses to begin transmitting, the EOR code when transmitting data\n characters.\n\n IAC DO END-OF-RECORD\n\n The sender of this command requests th 885 key nested-reference unchanged"},{"id":"IETF RFC 8860","type":"specification","body":"IETF","designation":"RFC 8860","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8860.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8860.txt","https://www.rfc-editor.org/rfc/rfc8860.pdf"],"folder":"IETF/RFC-8860","files":{"pdf":{"path":"standards/IETF/RFC-8860/RFC-8860.pdf","sha256":"61ead37327ab50ff3205b1a2c6a84cd421dd817d13581b710e63b20f76880ceb"},"txt":{"path":"standards/IETF/RFC-8860/RFC-8860.txt","sha256":"4768bbb8e2a7c45e8893998603b3aac6aeb51e3736b19fd2b7b18d7f7a7711ab"}},"tags":["nested-reference","unchanged"],"summary":"This document specifies how an RTP session can contain RTP streams\n with media from multiple media types such as audio, video, and text.\n This has been restricted by the RTP specifications (RFCs 3550 and\n 3551), and thus this document updates RFCs 3550 and 3551 to enable\n this behaviour for applications that satisfy the applicability for\n using multiple media types in a single RTP session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may","scope_keywords":["8860","http","https","key","license","risk","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8860 This document specifies how an RTP session can contain RTP streams\n with media from multiple media types such as audio, video, and text.\n This has been restricted by the RTP specifications (RFCs 3550 and\n 3551), and thus this document updates RFCs 3550 and 3551 to enable\n this behaviour for applications that satisfy the applicability for\n using multiple media types in a single RTP session.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering Group (IESG). Further information on\n Internet Standards is available in Section 2 of RFC 7841.\n\n Information about the current status of this document, any errata,\n and how to provide feedback on it may 8860 http https key license risk subject trust nested-reference unchanged"},{"id":"IETF RFC 8861","type":"specification","body":"IETF","designation":"RFC 8861","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8861.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8861.txt","https://www.rfc-editor.org/rfc/rfc8861.pdf"],"folder":"IETF/RFC-8861","files":{"pdf":{"path":"standards/IETF/RFC-8861/RFC-8861.pdf","sha256":"abd72d32234c0e9abf57a52d0296c9b2aee1759ec637e78aff78b732e4a1fc82"},"txt":{"path":"standards/IETF/RFC-8861/RFC-8861.txt","sha256":"62eca9faa4e3f331617b0fcf186920a2a465bf163600c646c9298c5a6303d4e8"}},"tags":["nested-reference","unchanged"],"summary":"RTP allows multiple RTP streams to be sent in a single session but\n requires each Synchronization Source (SSRC) to send RTP Control\n Protocol (RTCP) reception quality reports for every other SSRC\n visible in the session. This causes the number of RTCP reception\n reports to grow with the number of SSRCs, rather than the number of\n endpoints. In many cases, most of these RTCP reception reports are\n unnecessary, since all SSRCs of an endpoint are normally co-located\n and see the same reception quality. This memo defines a Reporting\n Group extension to RTCP to reduce the reporting overhead in such\n scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engi","scope_keywords":["8861","http","https","key","license","profile","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null}],"search_text":"IETF RFC 8861 RTP allows multiple RTP streams to be sent in a single session but\n requires each Synchronization Source (SSRC) to send RTP Control\n Protocol (RTCP) reception quality reports for every other SSRC\n visible in the session. This causes the number of RTCP reception\n reports to grow with the number of SSRCs, rather than the number of\n endpoints. In many cases, most of these RTCP reception reports are\n unnecessary, since all SSRCs of an endpoint are normally co-located\n and see the same reception quality. This memo defines a Reporting\n Group extension to RTCP to reduce the reporting overhead in such\n scenarios.\n\nStatus of This Memo\n\n This is an Internet Standards Track document.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engi 8861 http https key license profile subject trust nested-reference unchanged"},{"id":"IETF RFC 8872","type":"specification","body":"IETF","designation":"RFC 8872","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc8872.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc8872.txt","https://www.rfc-editor.org/rfc/rfc8872.pdf"],"folder":"IETF/RFC-8872","files":{"pdf":{"path":"standards/IETF/RFC-8872/RFC-8872.pdf","sha256":"a17c6289c89a5c5b2acbd4c0acfe81c5f88d27ef0931c2513206ed21ff895a40"},"txt":{"path":"standards/IETF/RFC-8872/RFC-8872.txt","sha256":"c8b5f3ffc5b12267b7e88a1e076a1abc1b195c7a42f0a33996601fc36871e321"}},"tags":["nested-reference","unchanged"],"summary":"The Real-time Transport Protocol (RTP) is a flexible protocol that\n can be used in a wide range of applications, networks, and system\n topologies. That flexibility makes for wide applicability but can\n complicate the application design process. One particular design\n question that has received much attention is how to support multiple\n media streams in RTP. This memo discusses the available options and\n design trade-offs, and provides guidelines on how to use the\n multiplexing features of RTP to support multiple media streams.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering ","scope_keywords":["8872","http","https","identification","key","license","management","subject","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8834","folder":"IETF/RFC-8834","source":"IETF/RFC-8834/RFC-8834.txt","version":null},{"body":"IETF","designation":"RFC 8853","folder":"IETF/RFC-8853","source":"IETF/RFC-8853/RFC-8853.txt","version":null}],"search_text":"IETF RFC 8872 The Real-time Transport Protocol (RTP) is a flexible protocol that\n can be used in a wide range of applications, networks, and system\n topologies. That flexibility makes for wide applicability but can\n complicate the application design process. One particular design\n question that has received much attention is how to support multiple\n media streams in RTP. This memo discusses the available options and\n design trade-offs, and provides guidelines on how to use the\n multiplexing features of RTP to support multiple media streams.\n\nStatus of This Memo\n\n This document is not an Internet Standards Track specification; it is\n published for informational purposes.\n\n This document is a product of the Internet Engineering Task Force\n (IETF). It represents the consensus of the IETF community. It has\n received public review and has been approved for publication by the\n Internet Engineering Steering  8872 http https identification key license management subject trust nested-reference unchanged"},{"id":"IETF RFC 888","type":"specification","body":"IETF","designation":"RFC 888","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc888.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc888.txt","https://www.rfc-editor.org/rfc/rfc888.pdf"],"folder":"IETF/RFC-888","files":{"txt":{"path":"standards/IETF/RFC-888/RFC-888.txt","sha256":"cae38216ae81b849a69201467eda4ca49c55d580ea8a4a2f960ac7d4e317a53e"}},"tags":["nested-reference","unchanged"],"summary":"RFC 888\n\n \"STUB\" EXTERIOR GATEWAY PROTOCOL\n\n Linda J. Seamonson\n\n Eric C. Rosen\n\n BBN Communications\n\n January 1984\n\nThis note describes the Exterior Gateway Protocol used to connect Stub\nGateways to an Autonomous System of core Gateways. This document specifies\nthe working protocol, and defines an ARPA official protocol. All\nimplementers of Gateways should carefully review this document.\n\n\f\n\n RFC 888 JANUARY 1984\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n\n 2 DEFINITIONS AND OVERVIEW.............................. 4\n\n 3 NEIGHBOR ACQUISITION.................................. 7\n\n 4 NEIGHBOR REACHABILITY PROTOCOL....................... 10\n\n 5 NETWORK REACHABILITY (NR) MESSAGE.................... 15\n\n 6 POLLING FOR NR MESSAGES.............................. 22\n\n 7 SENDING NR MESSAGES.................................. 24\n\n 8 INDIRECT NEIGHBORS.............","scope_keywords":["888","algorithm","algorithms","identification","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 1364","folder":"IETF/RFC-1364","source":"IETF/RFC-1364/RFC-1364.txt","version":null},{"body":"IETF","designation":"RFC 1403","folder":"IETF/RFC-1403","source":"IETF/RFC-1403/RFC-1403.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 888 RFC 888\n\n \"STUB\" EXTERIOR GATEWAY PROTOCOL\n\n Linda J. Seamonson\n\n Eric C. Rosen\n\n BBN Communications\n\n January 1984\n\nThis note describes the Exterior Gateway Protocol used to connect Stub\nGateways to an Autonomous System of core Gateways. This document specifies\nthe working protocol, and defines an ARPA official protocol. All\nimplementers of Gateways should carefully review this document.\n\n\f\n\n RFC 888 JANUARY 1984\n\n Table of Contents\n\n 1 INTRODUCTION.......................................... 1\n\n 2 DEFINITIONS AND OVERVIEW.............................. 4\n\n 3 NEIGHBOR ACQUISITION.................................. 7\n\n 4 NEIGHBOR REACHABILITY PROTOCOL....................... 10\n\n 5 NETWORK REACHABILITY (NR) MESSAGE.................... 15\n\n 6 POLLING FOR NR MESSAGES.............................. 22\n\n 7 SENDING NR MESSAGES.................................. 24\n\n 8 INDIRECT NEIGHBORS............. 888 algorithm algorithms identification path subject nested-reference unchanged"},{"id":"IETF RFC 889","type":"specification","body":"IETF","designation":"RFC 889","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc889.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc889.txt","https://www.rfc-editor.org/rfc/rfc889.pdf"],"folder":"IETF/RFC-889","files":{"txt":{"path":"standards/IETF/RFC-889/RFC-889.txt","sha256":"1cf87afaf1c28b1bf3320576e92540334878335451f4ae92b8fdfb03f4611011"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 889 December 1983\n\n Internet Delay Experiments\n\nThis memo reports on some measurement experiments and suggests some possible\nimprovements to the TCP retransmission timeout calculation. This memo is\nboth a status report on the measurements and advice to implementers of TCP.\n\n1. Introduction\n\n This memorandum describes two series of experiments designed to explore\nthe transmission characteristics of the Internet system. One series of\nexperiments was designed to determine the network delays with respect to\npacket length, while the other was designed to assess the effectiveness of the\nTCP retransmission-timeout algorithm specified in the standards documents.\nBoth sets of experiments were conducted during the October - November 1983\ntime frame and used many hosts distributed throughout the Internet system.\n\n The objectives of these experi","scope_keywords":["889","algorithm","path","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 5783","folder":"IETF/RFC-5783","source":"IETF/RFC-5783/RFC-5783.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 889 Network Working Group D.L. Mills\nRequest for Comments: 889 December 1983\n\n Internet Delay Experiments\n\nThis memo reports on some measurement experiments and suggests some possible\nimprovements to the TCP retransmission timeout calculation. This memo is\nboth a status report on the measurements and advice to implementers of TCP.\n\n1. Introduction\n\n This memorandum describes two series of experiments designed to explore\nthe transmission characteristics of the Internet system. One series of\nexperiments was designed to determine the network delays with respect to\npacket length, while the other was designed to assess the effectiveness of the\nTCP retransmission-timeout algorithm specified in the standards documents.\nBoth sets of experiments were conducted during the October - November 1983\ntime frame and used many hosts distributed throughout the Internet system.\n\n The objectives of these experi 889 algorithm path timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 890","type":"specification","body":"IETF","designation":"RFC 890","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc890.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc890.txt","https://www.rfc-editor.org/rfc/rfc890.pdf"],"folder":"IETF/RFC-890","files":{"txt":{"path":"standards/IETF/RFC-890/RFC-890.txt","sha256":"d691e990c0ce75bddf87927c1fb242fc1b34d5aee21d218ae17ca5cb936a73ca"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 890 ISI\n February 1984\n\n Exterior Gateway Protocol Implementation Schedule\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Exterior\n Gateway Protocol in the Internet. This is an official policy\n statement of ICCB and DARPA.\n\nThe Current Situation\n\n Currently the Internet has a number of smart gateways and a number of\n dumb gateways. The smart gateways dynamically exchange routing\n information among themselves using the Gateway Gateway\n Protocol (GGP) [3]. The dumb gateways do not exchange routing\n information dynamically.\n\n The dumb gateways must be listed in the smart gateway routing tables,\n and changes in dumb gateways status (e.g., adding new dumb gateways)\n in the smart gateways tables requires human intervention.\n\n The amount of routing traffic between smart gateways depends on the\n number of","scope_keywords":["890","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 890 Network Working Group Jon Postel\nRequest for Comments: 890 ISI\n February 1984\n\n Exterior Gateway Protocol Implementation Schedule\n\nStatus of this Memo\n\n This memo is a policy statement on the implementation of the Exterior\n Gateway Protocol in the Internet. This is an official policy\n statement of ICCB and DARPA.\n\nThe Current Situation\n\n Currently the Internet has a number of smart gateways and a number of\n dumb gateways. The smart gateways dynamically exchange routing\n information among themselves using the Gateway Gateway\n Protocol (GGP) [3]. The dumb gateways do not exchange routing\n information dynamically.\n\n The dumb gateways must be listed in the smart gateway routing tables,\n and changes in dumb gateways status (e.g., adding new dumb gateways)\n in the smart gateways tables requires human intervention.\n\n The amount of routing traffic between smart gateways depends on the\n number of 890 policy nested-reference unchanged"},{"id":"IETF RFC 891","type":"specification","body":"IETF","designation":"RFC 891","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc891.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc891.txt","https://www.rfc-editor.org/rfc/rfc891.pdf"],"folder":"IETF/RFC-891","files":{"txt":{"path":"standards/IETF/RFC-891/RFC-891.txt","sha256":"eef9c420a4dbc95a50f6d092d60d3790c0fe38303041d7ff2da7c3248762ed18"}},"tags":["nested-reference","unchanged"],"summary":"of detecting loops in routing updates, which establish the\nminimum-delay paths between the virtual hosts. By convention, the\nphysical host ID is assigned as the host ID of one of its virtual\nhosts. A link to a neighbor net is associated with a special virtual\nhost, called a gateway, which is assigned a unique host ID.","scope_keywords":["891","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 891 of detecting loops in routing updates, which establish the\nminimum-delay paths between the virtual hosts. By convention, the\nphysical host ID is assigned as the host ID of one of its virtual\nhosts. A link to a neighbor net is associated with a special virtual\nhost, called a gateway, which is assigned a unique host ID. 891 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 892","type":"specification","body":"IETF","designation":"RFC 892","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc892.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc892.txt","https://www.rfc-editor.org/rfc/rfc892.pdf"],"folder":"IETF/RFC-892","files":{"txt":{"path":"standards/IETF/RFC-892/RFC-892.txt","sha256":"d39e914a68527e43da6fcb49bf36142ea46510e869a49950140898014b3658df"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ISO\nRequest for Comments: 892 December 1983\n\n ISO Transport Protocol Specification\n\nThis document is distributed as an RFC for information only.\nIt does not specify a standard for the ARPA Internet.\n\nNote: This document appeared in:\n\nISO/TC97/SC16/WG6. Information Processing Systems - Open Systems\n Interconnection - Transport Protocol Specification. Computer\n Communication Review 12, 3-4 (July/October 1982), pp. 24-67.\n\nand differs from it only in format.\n\nTable of Contents\n\n0. Introduction\n1. Scope and Field of Application\n2. References\n\nSection One - General\n\n3. Definitions\n4. Symbols and Abbreviations\n5. Overview\n\n 5.1 Service provided by the transport layer\n 5.2 Service assumed from the network layer\n 5.3 Functions of the transport layer\n 5.4 Model of the transport layer\n\nSection Two - Transport Protocol Specification\n\n6. Protocol Mechanisms\n \n 6.1 Assignment to","scope_keywords":["892"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 905","folder":"IETF/RFC-905","source":"IETF/RFC-905/RFC-905.txt","version":null}],"search_text":"IETF RFC 892 Network Working Group ISO\nRequest for Comments: 892 December 1983\n\n ISO Transport Protocol Specification\n\nThis document is distributed as an RFC for information only.\nIt does not specify a standard for the ARPA Internet.\n\nNote: This document appeared in:\n\nISO/TC97/SC16/WG6. Information Processing Systems - Open Systems\n Interconnection - Transport Protocol Specification. Computer\n Communication Review 12, 3-4 (July/October 1982), pp. 24-67.\n\nand differs from it only in format.\n\nTable of Contents\n\n0. Introduction\n1. Scope and Field of Application\n2. References\n\nSection One - General\n\n3. Definitions\n4. Symbols and Abbreviations\n5. Overview\n\n 5.1 Service provided by the transport layer\n 5.2 Service assumed from the network layer\n 5.3 Functions of the transport layer\n 5.4 Model of the transport layer\n\nSection Two - Transport Protocol Specification\n\n6. Protocol Mechanisms\n \n 6.1 Assignment to 892 nested-reference unchanged"},{"id":"IETF RFC 905","type":"specification","body":"IETF","designation":"RFC 905","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc905.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc905.txt","https://www.rfc-editor.org/rfc/rfc905.pdf"],"folder":"IETF/RFC-905","files":{"txt":{"path":"standards/IETF/RFC-905/RFC-905.txt","sha256":"b15fd8a58189016a039c3409eb8f4cd1d9e02d10d9bc2a6fda6a5b5179e084bd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ISO\n Request for Comments: 905 April 1984\n\n ISO Transport Protocol Specification\n ISO DP 8073\n\n Status of this Memo: \n\n This document is distributed as an RFC for information only. It\n does not specify a standard for the ARPA-Internet.\n\n Notes:\n\n 1) RFC 892 is an older version of the ISO Transport Protocol\n Specification. Therefore this RFC should be assumed to\n supercede RFC 892.\n\n 2) This document has been prepared by retyping the text of\n ISO/TC97/SC16/N1576 and then applying proposed editorial\n corrections contained in ISO/TC97/SC16/N1695. These two\n documents, taken together, are undergoing voting within ISO\n as a Draft International Standard (DIS).\n\n 3) Although this RFC has been reviewed after typing, and is\n believed to be substantially correct, it is possible that\n typographic errors not present in the ISO documents have been\n overlooked.\n\n Alex McKenzie\n B","scope_keywords":["905"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1583","folder":"IETF/RFC-1583","source":"IETF/RFC-1583/RFC-1583.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1981","folder":"IETF/RFC-1981","source":"IETF/RFC-1981/RFC-1981.txt","version":null},{"body":"IETF","designation":"RFC 2178","folder":"IETF/RFC-2178","source":"IETF/RFC-2178/RFC-2178.txt","version":null},{"body":"IETF","designation":"RFC 2328","folder":"IETF/RFC-2328","source":"IETF/RFC-2328/RFC-2328.txt","version":null},{"body":"IETF","designation":"RFC 2740","folder":"IETF/RFC-2740","source":"IETF/RFC-2740/RFC-2740.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 905 Network Working Group ISO\n Request for Comments: 905 April 1984\n\n ISO Transport Protocol Specification\n ISO DP 8073\n\n Status of this Memo: \n\n This document is distributed as an RFC for information only. It\n does not specify a standard for the ARPA-Internet.\n\n Notes:\n\n 1) RFC 892 is an older version of the ISO Transport Protocol\n Specification. Therefore this RFC should be assumed to\n supercede RFC 892.\n\n 2) This document has been prepared by retyping the text of\n ISO/TC97/SC16/N1576 and then applying proposed editorial\n corrections contained in ISO/TC97/SC16/N1695. These two\n documents, taken together, are undergoing voting within ISO\n as a Draft International Standard (DIS).\n\n 3) Although this RFC has been reviewed after typing, and is\n believed to be substantially correct, it is possible that\n typographic errors not present in the ISO documents have been\n overlooked.\n\n Alex McKenzie\n B 905 nested-reference unchanged"},{"id":"IETF RFC 893","type":"specification","body":"IETF","designation":"RFC 893","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc893.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc893.txt","https://www.rfc-editor.org/rfc/rfc893.pdf"],"folder":"IETF/RFC-893","files":{"txt":{"path":"standards/IETF/RFC-893/RFC-893.txt","sha256":"4ae0c063a4b05b717909b22367091e31aeec53eeeb0a627af87ac70da0c2d2ef"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Samuel J. Leffler\nRequest for Comments: 893 Michael J. Karels\n University of California at Berkeley\n April 1984\n\n Trailer Encapsulations\n\nStatus of this Memo\n\n This RFC discusses the motivation for use of \"trailer encapsulations\"\n on local-area networks and describes the implementation of such an\n encapsulation on various media. This document is for information\n only. This is NOT an official protocol for the ARPA Internet\n community.\n\nIntroduction\n\n A trailer encapsulation is a link level packet format employed by\n 4.2BSD UNIX (among others). A trailer encapsulation, or \"trailer\",\n may be generated by a system under certain conditions in an effort to\n minimize the number and size of memory-to-memory copy operations\n performed by a receiving host when processing a data packet.\n Trailers are strictly a link level packet format and are not visible\n (when properly imple","scope_keywords":["893","delivery","management","presentation","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 893 Network Working Group Samuel J. Leffler\nRequest for Comments: 893 Michael J. Karels\n University of California at Berkeley\n April 1984\n\n Trailer Encapsulations\n\nStatus of this Memo\n\n This RFC discusses the motivation for use of \"trailer encapsulations\"\n on local-area networks and describes the implementation of such an\n encapsulation on various media. This document is for information\n only. This is NOT an official protocol for the ARPA Internet\n community.\n\nIntroduction\n\n A trailer encapsulation is a link level packet format employed by\n 4.2BSD UNIX (among others). A trailer encapsulation, or \"trailer\",\n may be generated by a system under certain conditions in an effort to\n minimize the number and size of memory-to-memory copy operations\n performed by a receiving host when processing a data packet.\n Trailers are strictly a link level packet format and are not visible\n (when properly imple 893 delivery management presentation validation nested-reference unchanged"},{"id":"IETF RFC 894","type":"specification","body":"IETF","designation":"RFC 894","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc894.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc894.txt","https://www.rfc-editor.org/rfc/rfc894.pdf"],"folder":"IETF/RFC-894","files":{"txt":{"path":"standards/IETF/RFC-894/RFC-894.txt","sha256":"be88b9301e53f986aca3a0e55e488d1d79bae3f88fe3f257640397bc089e7035"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Charles Hornig\nRequest for Comments: 894 Symbolics Cambridge Research Center\n April 1984\n\n A Standard for the Transmission of IP Datagrams over Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Ethernet [2]. This RFC specifies a\n standard protocol for the ARPA-Internet community.\n\nIntroduction\n\n This memo applies to the Ethernet (10-megabit/second, 48-bit\n addresses). The procedure for transmission of IP datagrams on the\n Experimental Ethernet (3-megabit/second, 8-bit addresses) is\n described in [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Ethernet frames. The type\n field of the Ethernet frame must contain the value hexadecimal 0800.\n The data field contains the IP header followed immediately by the IP\n data.\n\n The minimum length of the data field of a packet se","scope_keywords":["894"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0894","folder":"IETF/RFC-0894","source":"IETF/RFC-0894/RFC-0894.txt","version":null},{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1531","folder":"IETF/RFC-1531","source":"IETF/RFC-1531/RFC-1531.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1541","folder":"IETF/RFC-1541","source":"IETF/RFC-1541/RFC-1541.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2074","folder":"IETF/RFC-2074","source":"IETF/RFC-2074/RFC-2074.txt","version":null},{"body":"IETF","designation":"RFC 2131","folder":"IETF/RFC-2131","source":"IETF/RFC-2131/RFC-2131.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2507","folder":"IETF/RFC-2507","source":"IETF/RFC-2507/RFC-2507.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4838","folder":"IETF/RFC-4838","source":"IETF/RFC-4838/RFC-4838.txt","version":null},{"body":"IETF","designation":"RFC 4840","folder":"IETF/RFC-4840","source":"IETF/RFC-4840/RFC-4840.txt","version":null},{"body":"IETF","designation":"RFC 5692","folder":"IETF/RFC-5692","source":"IETF/RFC-5692/RFC-5692.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 894 Network Working Group Charles Hornig\nRequest for Comments: 894 Symbolics Cambridge Research Center\n April 1984\n\n A Standard for the Transmission of IP Datagrams over Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Ethernet [2]. This RFC specifies a\n standard protocol for the ARPA-Internet community.\n\nIntroduction\n\n This memo applies to the Ethernet (10-megabit/second, 48-bit\n addresses). The procedure for transmission of IP datagrams on the\n Experimental Ethernet (3-megabit/second, 8-bit addresses) is\n described in [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Ethernet frames. The type\n field of the Ethernet frame must contain the value hexadecimal 0800.\n The data field contains the IP header followed immediately by the IP\n data.\n\n The minimum length of the data field of a packet se 894 nested-reference unchanged"},{"id":"IETF RFC 895","type":"specification","body":"IETF","designation":"RFC 895","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc895.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc895.txt","https://www.rfc-editor.org/rfc/rfc895.pdf"],"folder":"IETF/RFC-895","files":{"txt":{"path":"standards/IETF/RFC-895/RFC-895.txt","sha256":"1d6290a2436127b0db0fd92d08cfc5d64f2c87667834f3ad17db0f6a7cd50bf8"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jon Postel\nRequest for Comments: 895 ISI\n April 1984\n\n A Standard for the Transmission of IP Datagrams\n over Experimental Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Experimental Ethernet [2]. This\n RFC specifies a standard protocol for the ARPA Internet community.\n\nIntroduction\n\n This memo applies to the Experimental Ethernet (3-megabit/second,\n 8-bit addresses). The procedure for transmission of IP datagrams on\n the Ethernet (10-megabit/second, 48-bit addresses) is described in\n [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Experimental Ethernet\n frames. The type field of the Ethernet frame must contain the value\n 513 (1001 octal). The data field contains the IP header followed\n immediately by the IP data.\n\n If necessary, the data field should be padded t","scope_keywords":["895"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0900","folder":"IETF/RFC-0900","source":"IETF/RFC-0900/RFC-0900.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 900","folder":"IETF/RFC-900","source":"IETF/RFC-900/RFC-900.txt","version":null},{"body":"IETF","designation":"RFC 901","folder":"IETF/RFC-901","source":"IETF/RFC-901/RFC-901.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 895 Network Working Group Jon Postel\nRequest for Comments: 895 ISI\n April 1984\n\n A Standard for the Transmission of IP Datagrams\n over Experimental Ethernet Networks\n\nStatus of this Memo\n\n This RFC specifies a standard method of encapsulating Internet\n Protocol (IP) [1] datagrams on an Experimental Ethernet [2]. This\n RFC specifies a standard protocol for the ARPA Internet community.\n\nIntroduction\n\n This memo applies to the Experimental Ethernet (3-megabit/second,\n 8-bit addresses). The procedure for transmission of IP datagrams on\n the Ethernet (10-megabit/second, 48-bit addresses) is described in\n [3].\n\nFrame Format\n\n IP datagrams are transmitted in standard Experimental Ethernet\n frames. The type field of the Ethernet frame must contain the value\n 513 (1001 octal). The data field contains the IP header followed\n immediately by the IP data.\n\n If necessary, the data field should be padded t 895 nested-reference unchanged"},{"id":"IETF RFC 904","type":"specification","body":"IETF","designation":"RFC 904","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc904.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc904.txt","https://www.rfc-editor.org/rfc/rfc904.pdf"],"folder":"IETF/RFC-904","files":{"txt":{"path":"standards/IETF/RFC-904/RFC-904.txt","sha256":"f17ccae1133a4e657d807fd29b31ef677471b00447b40b55a7943e399817923c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 904 April 1984\n\n Exterior Gateway Protocol Formal Specification\n\n0. Status of this Memo\n\n This RFC is the specification of the Exterior Gateway Protocol\n(EGP). This document updates RFCs 827 and 888. This RFC specifies a\nstandard for the DARPA community. Interactions between gateways of\ndifferent autonomous systems in the ARPA-Internet must follow this \nprotocol.\n\n1. Introduction\n\n This document is a formal specification of the Exterior Gateway\nProtocol (EGP), which is used to exchange net-reachability information\nbetween Internet gateways belonging to the same or different autonomous\nsystems. The specification is intended as a reference guide for\nimplementation, testing and verification and includes suggested\nalgorithmic parameters suitable for operation over a wide set of\nconfigurations, including the ARPANET and many local-network","scope_keywords":["904","algorithm","algorithms","presentation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1093","folder":"IETF/RFC-1093","source":"IETF/RFC-1093/RFC-1093.txt","version":null},{"body":"IETF","designation":"RFC 1105","folder":"IETF/RFC-1105","source":"IETF/RFC-1105/RFC-1105.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1163","folder":"IETF/RFC-1163","source":"IETF/RFC-1163/RFC-1163.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1222","folder":"IETF/RFC-1222","source":"IETF/RFC-1222/RFC-1222.txt","version":null},{"body":"IETF","designation":"RFC 1267","folder":"IETF/RFC-1267","source":"IETF/RFC-1267/RFC-1267.txt","version":null},{"body":"IETF","designation":"RFC 1371","folder":"IETF/RFC-1371","source":"IETF/RFC-1371/RFC-1371.txt","version":null},{"body":"IETF","designation":"RFC 1392","folder":"IETF/RFC-1392","source":"IETF/RFC-1392/RFC-1392.txt","version":null},{"body":"IETF","designation":"RFC 1594","folder":"IETF/RFC-1594","source":"IETF/RFC-1594/RFC-1594.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 1983","folder":"IETF/RFC-1983","source":"IETF/RFC-1983/RFC-1983.txt","version":null},{"body":"IETF","designation":"RFC 2360","folder":"IETF/RFC-2360","source":"IETF/RFC-2360/RFC-2360.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4632","folder":"IETF/RFC-4632","source":"IETF/RFC-4632/RFC-4632.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 904 Network Working Group D.L. Mills\nRequest for Comments: 904 April 1984\n\n Exterior Gateway Protocol Formal Specification\n\n0. Status of this Memo\n\n This RFC is the specification of the Exterior Gateway Protocol\n(EGP). This document updates RFCs 827 and 888. This RFC specifies a\nstandard for the DARPA community. Interactions between gateways of\ndifferent autonomous systems in the ARPA-Internet must follow this \nprotocol.\n\n1. Introduction\n\n This document is a formal specification of the Exterior Gateway\nProtocol (EGP), which is used to exchange net-reachability information\nbetween Internet gateways belonging to the same or different autonomous\nsystems. The specification is intended as a reference guide for\nimplementation, testing and verification and includes suggested\nalgorithmic parameters suitable for operation over a wide set of\nconfigurations, including the ARPANET and many local-network 904 algorithm algorithms presentation nested-reference unchanged"},{"id":"IETF RFC 907","type":"specification","body":"IETF","designation":"RFC 907","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc907.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc907.txt","https://www.rfc-editor.org/rfc/rfc907.pdf"],"folder":"IETF/RFC-907","files":{"txt":{"path":"standards/IETF/RFC-907/RFC-907.txt","sha256":"5f79df6c1b93dc7c5ceb1c99329d30162e201ccd5085069b92d766acd82dcd2c"}},"tags":["nested-reference","unchanged"],"summary":"RFC 907\n\n HOST ACCESS PROTOCOL SPECIFICATION\n\n July 1984\n\n prepared for\n\n Defense Advanced Research Projects Agency\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Bolt Beranek and Newman Laboratories\n 10 Moulton Street\n Cambridge, Massachusetts 02238\n\n\f\n\n RFC 907 Host Access Protocol\n July 1984 Specification\n\n Preface (Status of this Memo)\n\n This document specifies the Host Access Protocol (HAP).\n Although HAP was originally designed as the network-access level\n protocol for the DARPA/DCA sponsored Wideband Packet Satellite\n Network, it is intended that it evolve into a standard interface\n between hosts and packet-switched satellite networks such as\n SATNET and TACNET (aka MATNET) as well as the Wideband Network.\n The HAP specification presented here is a minor revision of, and\n supercedes, the specification presented in Chapter 4 of BBN\n Report No. 4469, the \"PSAT Technical Re","scope_keywords":["907","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1191","folder":"IETF/RFC-1191","source":"IETF/RFC-1191/RFC-1191.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 907 RFC 907\n\n HOST ACCESS PROTOCOL SPECIFICATION\n\n July 1984\n\n prepared for\n\n Defense Advanced Research Projects Agency\n 1400 Wilson Boulevard\n Arlington, Virginia 22209\n\n by\n\n Bolt Beranek and Newman Laboratories\n 10 Moulton Street\n Cambridge, Massachusetts 02238\n\n\f\n\n RFC 907 Host Access Protocol\n July 1984 Specification\n\n Preface (Status of this Memo)\n\n This document specifies the Host Access Protocol (HAP).\n Although HAP was originally designed as the network-access level\n protocol for the DARPA/DCA sponsored Wideband Packet Satellite\n Network, it is intended that it evolve into a standard interface\n between hosts and packet-switched satellite networks such as\n SATNET and TACNET (aka MATNET) as well as the Wideband Network.\n The HAP specification presented here is a minor revision of, and\n supercedes, the specification presented in Chapter 4 of BBN\n Report No. 4469, the \"PSAT Technical Re 907 delivery nested-reference unchanged"},{"id":"IETF RFC 909","type":"specification","body":"IETF","designation":"RFC 909","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc909.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc909.txt","https://www.rfc-editor.org/rfc/rfc909.pdf"],"folder":"IETF/RFC-909","files":{"txt":{"path":"standards/IETF/RFC-909/RFC-909.txt","sha256":"9ac2bfb500f102025679dbb39260b032f019a4e413ef4ffdb20c1c74e57f7085"}},"tags":["nested-reference","unchanged"],"summary":"Loader Debugger Protocol\n\n RFC-909\n\n Christopher Welles\n\n BBN Communications Corporation\n\n Walter Milliken\n\n BBN Laboratories\n\n July 1984\n\nStatus of This Memo\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n\f\n\f\n\n Table of Contents\n\n 1 Introduction.......................................... 1\n 1.1 Purpose of This Document............................ 1\n 1.2 Summary of Features................................. 2\n\n 2 General Description................................... 3\n 2.1 Motivation.......................................... 3\n 2.2 Relation to Other Protocols......................... 4\n 2.2.1 Transport Service Requirements.................... 5\n\n 3 Protocol Operation.................................... 9\n 3.1 Overview............................................ 9","scope_keywords":["909","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 909 Loader Debugger Protocol\n\n RFC-909\n\n Christopher Welles\n\n BBN Communications Corporation\n\n Walter Milliken\n\n BBN Laboratories\n\n July 1984\n\nStatus of This Memo\n\n This RFC specifies a proposed protocol for the ARPA Internet\n community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\n\f\n\f\n\n Table of Contents\n\n 1 Introduction.......................................... 1\n 1.1 Purpose of This Document............................ 1\n 1.2 Summary of Features................................. 2\n\n 2 General Description................................... 3\n 2.1 Motivation.......................................... 3\n 2.2 Relation to Other Protocols......................... 4\n 2.2.1 Transport Service Requirements.................... 5\n\n 3 Protocol Operation.................................... 9\n 3.1 Overview............................................ 9 909 management nested-reference unchanged"},{"id":"IETF RFC 912","type":"specification","body":"IETF","designation":"RFC 912","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc912.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc912.txt","https://www.rfc-editor.org/rfc/rfc912.pdf"],"folder":"IETF/RFC-912","files":{"txt":{"path":"standards/IETF/RFC-912/RFC-912.txt","sha256":"5d037c2cc5718b4085f7538fbc1077f8fd35e7dcee81c0ff28884bcbabb6d52c"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mike StJohns\nRequest for Comments: 912 TPSC\n September 1984\n\n Authentication Service\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The Authentication Server provides a means to determine the identity\n of a user of a particular TCP connection. Given a TCP port number\n pair, it returns a character string which identifies the owner of\n that connection on the server's system. Suggested uses include\n automatic identification and verification of a user during an FTP\n session, additional verification of a TAC dial up user, and access\n verification for a generalized network file server.\n\nOVERVIEW\n\n This is a connection based application on TCP. A server listens for\n TCP connections on TCP port 113 (decimal). Once","scope_keywords":["912","authentication","identification","key","presentation","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 931","folder":"IETF/RFC-931","source":"IETF/RFC-931/RFC-931.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 912 Network Working Group Mike StJohns\nRequest for Comments: 912 TPSC\n September 1984\n\n Authentication Service\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The Authentication Server provides a means to determine the identity\n of a user of a particular TCP connection. Given a TCP port number\n pair, it returns a character string which identifies the owner of\n that connection on the server's system. Suggested uses include\n automatic identification and verification of a user during an FTP\n session, additional verification of a TAC dial up user, and access\n verification for a generalized network file server.\n\nOVERVIEW\n\n This is a connection based application on TCP. A server listens for\n TCP connections on TCP port 113 (decimal). Once 912 authentication identification key presentation trust nested-reference unchanged"},{"id":"IETF RFC 931","type":"specification","body":"IETF","designation":"RFC 931","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc931.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc931.txt","https://www.rfc-editor.org/rfc/rfc931.pdf"],"folder":"IETF/RFC-931","files":{"txt":{"path":"standards/IETF/RFC-931/RFC-931.txt","sha256":"c9fa729753d39cfeee15c15857e3670dd56ad2f7cbdd6e6d6fa68289f898ba09"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mike StJohns\nRequest for Comments: 931 TPSC\nSupersedes: RFC 912 January 1985\n\n Authentication Server\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n This is the second draft of this proposal (superseding RFC 912) and\n incorporates a more formal description of the syntax for the request\n and response dialog, as well as a change to specify the type of user\n identification returned. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The Authentication Server Protocol provides a means to determine the\n identity of a user of a particular TCP connection. Given a TCP port\n number pair, it returns a character string which identifies the owner\n of that connection on the server's system. Suggested uses include\n automatic identification and verification of a user duri","scope_keywords":["931","authentication","identification","key","registered","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1413","folder":"IETF/RFC-1413","source":"IETF/RFC-1413/RFC-1413.txt","version":null},{"body":"IETF","designation":"RFC 6872","folder":"IETF/RFC-6872","source":"IETF/RFC-6872/RFC-6872.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 931 Network Working Group Mike StJohns\nRequest for Comments: 931 TPSC\nSupersedes: RFC 912 January 1985\n\n Authentication Server\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n This is the second draft of this proposal (superseding RFC 912) and\n incorporates a more formal description of the syntax for the request\n and response dialog, as well as a change to specify the type of user\n identification returned. Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n The Authentication Server Protocol provides a means to determine the\n identity of a user of a particular TCP connection. Given a TCP port\n number pair, it returns a character string which identifies the owner\n of that connection on the server's system. Suggested uses include\n automatic identification and verification of a user duri 931 authentication identification key registered trust nested-reference unchanged"},{"id":"IETF RFC 913","type":"specification","body":"IETF","designation":"RFC 913","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc913.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc913.txt","https://www.rfc-editor.org/rfc/rfc913.pdf"],"folder":"IETF/RFC-913","files":{"txt":{"path":"standards/IETF/RFC-913/RFC-913.txt","sha256":"f9ef04cfa0572f12acbe380801de18db3f87ba1302c4eecd5737a025b2ec48a7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mark K. Lottor\nRequest for Comments: 913 MIT\n September 1984\n\n Simple File Transfer Protocol\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n SFTP is a simple file transfer protocol. It fills the need of people\n wanting a protocol that is more useful than TFTP but easier to\n implement (and less powerful) than FTP. SFTP supports user access\n control, file transfers, directory listing, directory changing, file\n renaming and deleting.\n\n SFTP can be implemented with any reliable 8-bit byte stream oriented\n protocol, this document describes its TCP specification. SFTP uses\n only one TCP connection; whereas TFTP implements a connection over\n UDP, and FTP uses two TCP connections (one using the TELNET\n protocol).\n\n","scope_keywords":["913","crl","identification","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0951","folder":"IETF/RFC-0951","source":"IETF/RFC-0951/RFC-0951.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 951","folder":"IETF/RFC-951","source":"IETF/RFC-951/RFC-951.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 913 Network Working Group Mark K. Lottor\nRequest for Comments: 913 MIT\n September 1984\n\n Simple File Transfer Protocol\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n SFTP is a simple file transfer protocol. It fills the need of people\n wanting a protocol that is more useful than TFTP but easier to\n implement (and less powerful) than FTP. SFTP supports user access\n control, file transfers, directory listing, directory changing, file\n renaming and deleting.\n\n SFTP can be implemented with any reliable 8-bit byte stream oriented\n protocol, this document describes its TCP specification. SFTP uses\n only one TCP connection; whereas TFTP implements a connection over\n UDP, and FTP uses two TCP connections (one using the TELNET\n protocol).\n\n 913 crl identification key nested-reference unchanged"},{"id":"IETF RFC 914","type":"specification","body":"IETF","designation":"RFC 914","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc914.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc914.txt","https://www.rfc-editor.org/rfc/rfc914.pdf"],"folder":"IETF/RFC-914","files":{"txt":{"path":"standards/IETF/RFC-914/RFC-914.txt","sha256":"99a1e6c5c1454ab036741e9c07d666feabc62392eeb4e8fe2a6fd73271b74515"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David J. Farber\nRequest for Comments: 914 Gary S. Delp\n Thomas M. Conte\n University of Delaware\n September 1984\n\n A Thinwire Protocol\n for connecting personal computers\n to the INTERNET\n\nStatus of this Memo\n\n This RFC focuses discussion on the particular problems in the\n ARPA-Internet of low speed network interconnection with personal\n computers, and possible methods of solution. None of the proposed\n solutions in this document are intended as standards for the\n ARPA-Internet. Rather, it is hoped that a general consensus will\n emerge as to the appropriate solution to the problems, leading\n eventually to the adoption of standards. Distribution of this memo\n unlimited.\n\nWhat is the Problem Anyway ?\n\n As we connect workstations and personal computers to the INTERNET,\n many of the cost/speed communication tradeoffs change. This has made\n us reconsider the way we juggle ","scope_keywords":["914","algorithm","algorithms","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 935","folder":"IETF/RFC-935","source":"IETF/RFC-935/RFC-935.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 914 Network Working Group David J. Farber\nRequest for Comments: 914 Gary S. Delp\n Thomas M. Conte\n University of Delaware\n September 1984\n\n A Thinwire Protocol\n for connecting personal computers\n to the INTERNET\n\nStatus of this Memo\n\n This RFC focuses discussion on the particular problems in the\n ARPA-Internet of low speed network interconnection with personal\n computers, and possible methods of solution. None of the proposed\n solutions in this document are intended as standards for the\n ARPA-Internet. Rather, it is hoped that a general consensus will\n emerge as to the appropriate solution to the problems, leading\n eventually to the adoption of standards. Distribution of this memo\n unlimited.\n\nWhat is the Problem Anyway ?\n\n As we connect workstations and personal computers to the INTERNET,\n many of the cost/speed communication tradeoffs change. This has made\n us reconsider the way we juggle  914 algorithm algorithms path nested-reference unchanged"},{"id":"IETF RFC 916","type":"specification","body":"IETF","designation":"RFC 916","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc916.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc916.txt","https://www.rfc-editor.org/rfc/rfc916.pdf"],"folder":"IETF/RFC-916","files":{"txt":{"path":"standards/IETF/RFC-916/RFC-916.txt","sha256":"42954fa03fa2a0e56c73168037d4479ba15c3478b1ad73b62e4019fb62183cc3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group G. Finn\nRequest for Comments: 916 ISI\n October 1984\n\n RELIABLE ASYNCHRONOUS TRANSFER PROTOCOL (RATP)\n\nStatus of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This paper proposes and specifies a protocol which allows two\n programs to reliably communicate over a communication link. It\n ensures that the data entering one end of the link if received\n arrives at the other end intact and unaltered. The protocol, named\n RATP, is designed to operate over a full duplex point-to-point\n connection. It contains some features which tailor it to the RS-232\n links now in common use.\n\nIntroduction\n\n We are witnessing today an explosive growth in the small or personal\n computer market. Such inexpensive computers are not normally\n connected to a c","scope_keywords":["916","algorithm","algorithms","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 935","folder":"IETF/RFC-935","source":"IETF/RFC-935/RFC-935.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 916 Network Working Group G. Finn\nRequest for Comments: 916 ISI\n October 1984\n\n RELIABLE ASYNCHRONOUS TRANSFER PROTOCOL (RATP)\n\nStatus of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\n This paper proposes and specifies a protocol which allows two\n programs to reliably communicate over a communication link. It\n ensures that the data entering one end of the link if received\n arrives at the other end intact and unaltered. The protocol, named\n RATP, is designed to operate over a full duplex point-to-point\n connection. It contains some features which tailor it to the RS-232\n links now in common use.\n\nIntroduction\n\n We are witnessing today an explosive growth in the small or personal\n computer market. Such inexpensive computers are not normally\n connected to a c 916 algorithm algorithms management nested-reference unchanged"},{"id":"IETF RFC 917","type":"specification","body":"IETF","designation":"RFC 917","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc917.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc917.txt","https://www.rfc-editor.org/rfc/rfc917.pdf"],"folder":"IETF/RFC-917","files":{"txt":{"path":"standards/IETF/RFC-917/RFC-917.txt","sha256":"6d2b9425752f98eeab3abb398d9d705e9dc864aae5aefd5ce43b703f5f33a1da"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Jeffrey Mogul\nRequest for Comments: 917 Computer Science Department\n Stanford University\n October 1984\n\n INTERNET SUBNETS\n\nStatus Of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n We discuss the utility of \"subnets\" of Internet networks, which are\n logically visible sub-sections of a single Internet network. For\n administrative or technical reasons, many organizations have chosen\n to divide one Internet network into several subnets, instead of\n acquiring a set of Internet network numbers.\n\n We propose procedures for the use of subnets, and discuss approaches\n to solving the problems that arise, particularly that of routing.\n\nAcknowledgment\n\n This proposal is the result of discussion with several other people.\n J. Noel Ch","scope_keywords":["917","algorithm","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 3789","folder":"IETF/RFC-3789","source":"IETF/RFC-3789/RFC-3789.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 917 Network Working Group Jeffrey Mogul\nRequest for Comments: 917 Computer Science Department\n Stanford University\n October 1984\n\n INTERNET SUBNETS\n\nStatus Of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n We discuss the utility of \"subnets\" of Internet networks, which are\n logically visible sub-sections of a single Internet network. For\n administrative or technical reasons, many organizations have chosen\n to divide one Internet network into several subnets, instead of\n acquiring a set of Internet network numbers.\n\n We propose procedures for the use of subnets, and discuss approaches\n to solving the problems that arise, particularly that of routing.\n\nAcknowledgment\n\n This proposal is the result of discussion with several other people.\n J. Noel Ch 917 algorithm key nested-reference unchanged"},{"id":"IETF RFC 918","type":"specification","body":"IETF","designation":"RFC 918","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc918.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc918.txt","https://www.rfc-editor.org/rfc/rfc918.pdf"],"folder":"IETF/RFC-918","files":{"txt":{"path":"standards/IETF/RFC-918/RFC-918.txt","sha256":"7839c676af439dfc90a4cc492411eba8a10dcf6b886a4737c088a4cbbf150cc3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. K. Reynolds\nRequest for Comments: 918 ISI\n October 1984\n\n POST OFFICE PROTOCOL\n\nStatus of this Memo\n\n This RFC suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvement.\n\nIntroduction\n\n The intent of the Post Office Protocol (POP) is to allow a user's\n workstation to access mail from a mailbox server. It is expected\n that mail will be posted from the workstation to the mailbox server\n via the Simple Mail Transfer Protocol (SMTP). For further\n information see RFC-821 [1] and RFC-822 [2].\n\n The status of this protocol is experimental, and this protocol is\n dependent upon TCP.\n\nThe Protocol\n\n The protocol is for the server to be listening for a connection.\n When a connection is opened the server sends a ","scope_keywords":["918","authorization"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1081","folder":"IETF/RFC-1081","source":"IETF/RFC-1081/RFC-1081.txt","version":null},{"body":"IETF","designation":"RFC 1225","folder":"IETF/RFC-1225","source":"IETF/RFC-1225/RFC-1225.txt","version":null},{"body":"IETF","designation":"RFC 923","folder":"IETF/RFC-923","source":"IETF/RFC-923/RFC-923.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 937","folder":"IETF/RFC-937","source":"IETF/RFC-937/RFC-937.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 918 Network Working Group J. K. Reynolds\nRequest for Comments: 918 ISI\n October 1984\n\n POST OFFICE PROTOCOL\n\nStatus of this Memo\n\n This RFC suggests a simple method for workstations to dynamically\n access mail from a mailbox server. This RFC specifies a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvement.\n\nIntroduction\n\n The intent of the Post Office Protocol (POP) is to allow a user's\n workstation to access mail from a mailbox server. It is expected\n that mail will be posted from the workstation to the mailbox server\n via the Simple Mail Transfer Protocol (SMTP). For further\n information see RFC-821 [1] and RFC-822 [2].\n\n The status of this protocol is experimental, and this protocol is\n dependent upon TCP.\n\nThe Protocol\n\n The protocol is for the server to be listening for a connection.\n When a connection is opened the server sends a  918 authorization nested-reference unchanged"},{"id":"IETF RFC 920","type":"specification","body":"IETF","designation":"RFC 920","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc920.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc920.txt","https://www.rfc-editor.org/rfc/rfc920.pdf"],"folder":"IETF/RFC-920","files":{"txt":{"path":"standards/IETF/RFC-920/RFC-920.txt","sha256":"9c2bdad1b1d05b5b9d5935006c2e4304899cf3e6d6d189c61046b2fdd04ee8f4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 920 J. Reynolds\n ISI\n October 1984\n\n Domain Requirements\n\nStatus of this Memo\n\n This memo is a policy statement on the requirements of establishing a\n new domain in the ARPA-Internet and the DARPA research community.\n This is an official policy statement of the IAB and the DARPA.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo restates and refines the requirements on establishing a\n Domain first described in RFC-881 [1]. It adds considerable detail\n to that discussion, and introduces the limited set of top level\n domains.\n\nThe Purpose of Domains\n\n Domains are administrative entities. The purpose and expected use of\n domains is to divide the name management required of a central\n administration and assign it to sub-administrations. There are no\n geographical, topological, or technological constraints on a domain.\n Th","scope_keywords":["920","key","management","policy","presentation","registered"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2240","folder":"IETF/RFC-2240","source":"IETF/RFC-2240/RFC-2240.txt","version":null},{"body":"IETF","designation":"RFC 924","folder":"IETF/RFC-924","source":"IETF/RFC-924/RFC-924.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 987","folder":"IETF/RFC-987","source":"IETF/RFC-987/RFC-987.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 920 Network Working Group J. Postel\nRequest for Comments: 920 J. Reynolds\n ISI\n October 1984\n\n Domain Requirements\n\nStatus of this Memo\n\n This memo is a policy statement on the requirements of establishing a\n new domain in the ARPA-Internet and the DARPA research community.\n This is an official policy statement of the IAB and the DARPA.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n This memo restates and refines the requirements on establishing a\n Domain first described in RFC-881 [1]. It adds considerable detail\n to that discussion, and introduces the limited set of top level\n domains.\n\nThe Purpose of Domains\n\n Domains are administrative entities. The purpose and expected use of\n domains is to divide the name management required of a central\n administration and assign it to sub-administrations. There are no\n geographical, topological, or technological constraints on a domain.\n Th 920 key management policy presentation registered nested-reference unchanged"},{"id":"IETF RFC 925","type":"specification","body":"IETF","designation":"RFC 925","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc925.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc925.txt","https://www.rfc-editor.org/rfc/rfc925.pdf"],"folder":"IETF/RFC-925","files":{"txt":{"path":"standards/IETF/RFC-925/RFC-925.txt","sha256":"59ecfa95cb97c3f3a13cd75e92cfc0498ea165b8cafcf1f4491766b5793f4857"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Postel\nRequest for Comments: 925 ISI\n October 1984\n\n Multi-LAN Address Resolution\n\nSTATUS OF THIS MEMO\n\n This memo is prompted by RFC-917 by Jeffery Mogul on \"Internet\n Subnets\". In that memo, Mogul makes a case for the use of \"explicit\n subnets\" in a multi-LAN environment. In this memo, I attempt to make\n a case for \"transparent subnets\". This RFC suggests a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The problem of treating a set of local area networks (LANs) as one\n Internet network has generated some interest and concern. It is\n inappropriate to give each LAN within an site a distinct Internet\n network number. It is desirable to hide the details of the\n interconnections between the LANs within an site from people,\n gateways, and hosts ou","scope_keywords":["925"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0925","folder":"IETF/RFC-0925","source":"IETF/RFC-0925/RFC-0925.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1931","folder":"IETF/RFC-1931","source":"IETF/RFC-1931/RFC-1931.txt","version":null},{"body":"IETF","designation":"RFC 2002","folder":"IETF/RFC-2002","source":"IETF/RFC-2002/RFC-2002.txt","version":null},{"body":"IETF","designation":"RFC 3220","folder":"IETF/RFC-3220","source":"IETF/RFC-3220/RFC-3220.txt","version":null},{"body":"IETF","designation":"RFC 3344","folder":"IETF/RFC-3344","source":"IETF/RFC-3344/RFC-3344.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5844","folder":"IETF/RFC-5844","source":"IETF/RFC-5844/RFC-5844.txt","version":null},{"body":"IETF","designation":"RFC 5944","folder":"IETF/RFC-5944","source":"IETF/RFC-5944/RFC-5944.txt","version":null},{"body":"IETF","designation":"RFC 6250","folder":"IETF/RFC-6250","source":"IETF/RFC-6250/RFC-6250.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 925 Network Working Group J. Postel\nRequest for Comments: 925 ISI\n October 1984\n\n Multi-LAN Address Resolution\n\nSTATUS OF THIS MEMO\n\n This memo is prompted by RFC-917 by Jeffery Mogul on \"Internet\n Subnets\". In that memo, Mogul makes a case for the use of \"explicit\n subnets\" in a multi-LAN environment. In this memo, I attempt to make\n a case for \"transparent subnets\". This RFC suggests a proposed\n protocol for the ARPA-Internet community, and requests discussion and\n suggestions for improvements. Distribution of this memo is\n unlimited.\n\nINTRODUCTION\n\n The problem of treating a set of local area networks (LANs) as one\n Internet network has generated some interest and concern. It is\n inappropriate to give each LAN within an site a distinct Internet\n network number. It is desirable to hide the details of the\n interconnections between the LANs within an site from people,\n gateways, and hosts ou 925 nested-reference unchanged"},{"id":"IETF RFC 926","type":"specification","body":"IETF","designation":"RFC 926","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc926.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc926.txt","https://www.rfc-editor.org/rfc/rfc926.pdf"],"folder":"IETF/RFC-926","files":{"txt":{"path":"standards/IETF/RFC-926/RFC-926.txt","sha256":"950468c042c4369b7711aa89376acd4b9be38a2fc0eb5f638d4fdcb7f9bf5225"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ISO\nRequest for Comments: 926 December 1984\n\n \n \n Protocol for Providing the Connectionless-Mode Network Services\n \n (Informally - ISO IP)\n\n ISO DIS 8473\n\nStatus of this Memo:\n\n This document is distributed as an RFC for information only. It does\n not specify a standard for the ARPA-Internet. Distribution of this\n memo is unlimited.\n\nNote:\n\n This document has been prepared by retyping the text of ISO DIS 8473 of\n May 1984, which is currently undergoing voting within ISO as a Draft\n International Standard (DIS). Although this RFC has been reviewed\n after typing, and is believed to be substantially correct, it is\n possible that typographic errors not present in the ISO document have\n been overlooked.\n\n Alex McKenzie\n BBN\n\f\n\nRFC 926 December 1984\n\f\n\nRFC 926 December 1984\n\n TABLE OF CONTENTS\n\n 1 SCOPE AND FIELD OF APPLICATION........................ 2\n\n 2 REFERENCES....","scope_keywords":["926"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 926 Network Working Group ISO\nRequest for Comments: 926 December 1984\n\n \n \n Protocol for Providing the Connectionless-Mode Network Services\n \n (Informally - ISO IP)\n\n ISO DIS 8473\n\nStatus of this Memo:\n\n This document is distributed as an RFC for information only. It does\n not specify a standard for the ARPA-Internet. Distribution of this\n memo is unlimited.\n\nNote:\n\n This document has been prepared by retyping the text of ISO DIS 8473 of\n May 1984, which is currently undergoing voting within ISO as a Draft\n International Standard (DIS). Although this RFC has been reviewed\n after typing, and is believed to be substantially correct, it is\n possible that typographic errors not present in the ISO document have\n been overlooked.\n\n Alex McKenzie\n BBN\n\f\n\nRFC 926 December 1984\n\f\n\nRFC 926 December 1984\n\n TABLE OF CONTENTS\n\n 1 SCOPE AND FIELD OF APPLICATION........................ 2\n\n 2 REFERENCES.... 926 nested-reference unchanged"},{"id":"IETF RFC 927","type":"specification","body":"IETF","designation":"RFC 927","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc927.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc927.txt","https://www.rfc-editor.org/rfc/rfc927.pdf"],"folder":"IETF/RFC-927","files":{"txt":{"path":"standards/IETF/RFC-927/RFC-927.txt","sha256":"8d96e37740c10c1955f71f3614e2c0cf3a79302f5f833fb766cafb0f2a0a8e54"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Brian A. Anderson\nRequest for Comments: 927 BBN\n December 1984\n\n TACACS User Identification Telnet Option\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The following is the description of a TELNET option designed to\n facilitate double login avoidance. It is intended primarily for TAC\n connections to target hosts on behalf of TAC users, but it can be\n used between any two consenting hosts. For example, all hosts at one\n site (e.g., BBN) can use this option to avoid double login when\n TELNETing to one another.\n\n1. Command name and code\n\n TUID 26\n\n2. Command Meanings\n\n IAC WILL TUID\n\n The sender (the TELNET user) proposes to authenticate the user and\n send the identifing UUID; or, the sender (the TELNET user","scope_keywords":["927","authentication","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0927","folder":"IETF/RFC-0927","source":"IETF/RFC-0927/RFC-0927.txt","version":null},{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1704","folder":"IETF/RFC-1704","source":"IETF/RFC-1704/RFC-1704.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 4962","folder":"IETF/RFC-4962","source":"IETF/RFC-4962/RFC-4962.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 927 Network Working Group Brian A. Anderson\nRequest for Comments: 927 BBN\n December 1984\n\n TACACS User Identification Telnet Option\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n The following is the description of a TELNET option designed to\n facilitate double login avoidance. It is intended primarily for TAC\n connections to target hosts on behalf of TAC users, but it can be\n used between any two consenting hosts. For example, all hosts at one\n site (e.g., BBN) can use this option to avoid double login when\n TELNETing to one another.\n\n1. Command name and code\n\n TUID 26\n\n2. Command Meanings\n\n IAC WILL TUID\n\n The sender (the TELNET user) proposes to authenticate the user and\n send the identifing UUID; or, the sender (the TELNET user 927 authentication identification nested-reference unchanged"},{"id":"IETF RFC 928","type":"specification","body":"IETF","designation":"RFC 928","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc928.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc928.txt","https://www.rfc-editor.org/rfc/rfc928.pdf"],"folder":"IETF/RFC-928","files":{"txt":{"path":"standards/IETF/RFC-928/RFC-928.txt","sha256":"9670b033d913f4990ade97d17dfd6a883152a7723463dcb2a1e9f55608998cb7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group M. A. Padlipsky\nRequest for Comments: 928 Mitre Corp.\n December 1984\n\n INTRODUCTION TO PROPOSED DOD STANDARD H-FP\n\nStatus Of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nImportant Prefatory Note\n\n The broad outline of the Host-Front End Protocol introduced here and\n described in RFC 929 is the result of the deliberations of a number\n of experienced H-FP designers, who sat as a committee of the DoD\n Protocol Standards Technical Panel under the author's chairmanship.\n The particular protocol to be described is, however, the result of\n the deliberations of a small, ad hoc group, who sat as a de facto\n subcommittee of the H-FP committee, also under the author's\n chairmanship. The protocol, then, follows the consensus of the full\n gro","scope_keywords":["928","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 929","folder":"IETF/RFC-929","source":"IETF/RFC-929/RFC-929.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 928 Network Working Group M. A. Padlipsky\nRequest for Comments: 928 Mitre Corp.\n December 1984\n\n INTRODUCTION TO PROPOSED DOD STANDARD H-FP\n\nStatus Of This Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nImportant Prefatory Note\n\n The broad outline of the Host-Front End Protocol introduced here and\n described in RFC 929 is the result of the deliberations of a number\n of experienced H-FP designers, who sat as a committee of the DoD\n Protocol Standards Technical Panel under the author's chairmanship.\n The particular protocol to be described is, however, the result of\n the deliberations of a small, ad hoc group, who sat as a de facto\n subcommittee of the H-FP committee, also under the author's\n chairmanship. The protocol, then, follows the consensus of the full\n gro 928 subject nested-reference unchanged"},{"id":"IETF RFC 929","type":"specification","body":"IETF","designation":"RFC 929","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc929.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc929.txt","https://www.rfc-editor.org/rfc/rfc929.pdf"],"folder":"IETF/RFC-929","files":{"txt":{"path":"standards/IETF/RFC-929/RFC-929.txt","sha256":"e2f005bf242c2f5e16c837bb1326f13522a3d7ab2144aa7a34f76ff6740b8d63"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Joel Lilienkamp (SDC)\nRequest for Comments: 929 Richard Mandell (SDC)\n Michael Padlipsky (Mitre Corp.)\n December 1984\n\n PROPOSED HOST-FRONT END PROTOCOL\n\nStatus Of This Memo\n\n The reader should be aware of several things in regard to what the\n present document is up to. First and foremost, IT IS A PROPOSAL FOR\n A STANDARD, NOT A STANDARD ITSELF. Next, it assumes that the\n separate document, RFC 928, which is an introduction to the present\n document, has been read before it is. Next, it should be understood\n that \"final cut\" over this version of the document has been exercised\n by the author of RFC 928, not by the primary author of the present\n document, so any readers bothered by style considerations should feel\n free to blame the former, who's used to it, rather than the latter,\n who may well be guiltless. (Editing at a distance finally become too\n hard to manage, ","scope_keywords":["929","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 928","folder":"IETF/RFC-928","source":"IETF/RFC-928/RFC-928.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 929 Network Working Group Joel Lilienkamp (SDC)\nRequest for Comments: 929 Richard Mandell (SDC)\n Michael Padlipsky (Mitre Corp.)\n December 1984\n\n PROPOSED HOST-FRONT END PROTOCOL\n\nStatus Of This Memo\n\n The reader should be aware of several things in regard to what the\n present document is up to. First and foremost, IT IS A PROPOSAL FOR\n A STANDARD, NOT A STANDARD ITSELF. Next, it assumes that the\n separate document, RFC 928, which is an introduction to the present\n document, has been read before it is. Next, it should be understood\n that \"final cut\" over this version of the document has been exercised\n by the author of RFC 928, not by the primary author of the present\n document, so any readers bothered by style considerations should feel\n free to blame the former, who's used to it, rather than the latter,\n who may well be guiltless. (Editing at a distance finally become too\n hard to manage,  929 trust nested-reference unchanged"},{"id":"IETF RFC 932","type":"specification","body":"IETF","designation":"RFC 932","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc932.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc932.txt","https://www.rfc-editor.org/rfc/rfc932.pdf"],"folder":"IETF/RFC-932","files":{"txt":{"path":"standards/IETF/RFC-932/RFC-932.txt","sha256":"d620d0288590e409c450e5768bbef4c3587ddcf4a71b3b7a0243d063f155fc74"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David D. Clark\nRequest for Comments: 932 MIT, LCS\n January 1985\n\n A SUBNETWORK ADDRESSING SCHEME\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n Several recent RFCs have discussed the need for a \"subnet\" structure\n within the internet addressing scheme, and have proposed strategies\n for \"subnetwork\" addressing and routing. In particular, Jeff Mogul\n in his RFC-917, \"Internet Subnets\", describes an addressing scheme in\n which a variable number of the leading bits of the host portion of\n the address are used to identify the subnet. The drawback to this\n scheme is that it is necessary to modify the host implementation in\n order to implement it. While the modification is a simple one, it is\n necessary to retrof","scope_keywords":["932","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 932 Network Working Group David D. Clark\nRequest for Comments: 932 MIT, LCS\n January 1985\n\n A SUBNETWORK ADDRESSING SCHEME\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nINTRODUCTION\n\n Several recent RFCs have discussed the need for a \"subnet\" structure\n within the internet addressing scheme, and have proposed strategies\n for \"subnetwork\" addressing and routing. In particular, Jeff Mogul\n in his RFC-917, \"Internet Subnets\", describes an addressing scheme in\n which a variable number of the leading bits of the host portion of\n the address are used to identify the subnet. The drawback to this\n scheme is that it is necessary to modify the host implementation in\n order to implement it. While the modification is a simple one, it is\n necessary to retrof 932 algorithm nested-reference unchanged"},{"id":"IETF RFC 933","type":"specification","body":"IETF","designation":"RFC 933","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc933.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc933.txt","https://www.rfc-editor.org/rfc/rfc933.pdf"],"folder":"IETF/RFC-933","files":{"txt":{"path":"standards/IETF/RFC-933/RFC-933.txt","sha256":"7e9099060709b7aa2e211939ba0ba0aed092865702bbf36df7eab812fe9355ee"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. Silverman\nRequest for Comments: 933 MITRE-Washington\n January 1985\n\n OUTPUT MARKING TELNET OPTION\n\nStatus of this Memo\n\n This RFC proposes a new option for Telnet for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n This proposed option would allow a Server-Telnet to send a banner to\n a User-Telnet so that this banner would be displayed on the\n workstation screen independently of the application software running\n in the Server-Telnet.\n\n1. Command Name and Code\n\n OUTMRK 27\n\n2. Command Meanings\n\n IAC WILL OUTMRK\n\n Sender is willing to send output marking information in a\n subsequent sub-negotiation.\n\n IAC WON'T OUTMRK\n\n Sender refuses to send output marking information.\n\n IAC DO OUTMRK\n\n Sender is willing to receive output marking information in a\n subsequent sub-negotiation","scope_keywords":["933","crl","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1116","folder":"IETF/RFC-1116","source":"IETF/RFC-1116/RFC-1116.txt","version":null},{"body":"IETF","designation":"RFC 1184","folder":"IETF/RFC-1184","source":"IETF/RFC-1184/RFC-1184.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 980","folder":"IETF/RFC-980","source":"IETF/RFC-980/RFC-980.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 933 Network Working Group S. Silverman\nRequest for Comments: 933 MITRE-Washington\n January 1985\n\n OUTPUT MARKING TELNET OPTION\n\nStatus of this Memo\n\n This RFC proposes a new option for Telnet for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n This proposed option would allow a Server-Telnet to send a banner to\n a User-Telnet so that this banner would be displayed on the\n workstation screen independently of the application software running\n in the Server-Telnet.\n\n1. Command Name and Code\n\n OUTMRK 27\n\n2. Command Meanings\n\n IAC WILL OUTMRK\n\n Sender is willing to send output marking information in a\n subsequent sub-negotiation.\n\n IAC WON'T OUTMRK\n\n Sender refuses to send output marking information.\n\n IAC DO OUTMRK\n\n Sender is willing to receive output marking information in a\n subsequent sub-negotiation 933 crl trust nested-reference unchanged"},{"id":"IETF RFC 934","type":"specification","body":"IETF","designation":"RFC 934","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc934.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc934.txt","https://www.rfc-editor.org/rfc/rfc934.pdf"],"folder":"IETF/RFC-934","files":{"txt":{"path":"standards/IETF/RFC-934/RFC-934.txt","sha256":"b800ad8c475babd672987131db427d1cad72906b53035c1bf8d4d1c213e76b22"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Marshall T. Rose (Delaware)\nRequest for Comments: 934 Einar A. Stefferud (NMA)\n January 1985\n\n Proposed Standard for Message Encapsulation\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction, Scope, and Motivation\n\n The services that a user agent (UA) can offer are varied. Although\n all outgoing mail may be thought of as going through a single posting\n slot to connect to the message transport system (MTS), it is possible\n to consider a message draft being posted as described by one of the\n following four types of postings:\n\n Originate - a new message is composed from scratch, which, to the\n knowledge of the UA, is unrelated to any message previously\n handled by the user.\n\n Reply - a message is composed as a reply","scope_keywords":["934","delivery","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0989","folder":"IETF/RFC-0989","source":"IETF/RFC-0989/RFC-0989.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1153","folder":"IETF/RFC-1153","source":"IETF/RFC-1153/RFC-1153.txt","version":null},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1421","folder":"IETF/RFC-1421","source":"IETF/RFC-1421/RFC-1421.txt","version":null},{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2048","folder":"IETF/RFC-2048","source":"IETF/RFC-2048/RFC-2048.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 987","folder":"IETF/RFC-987","source":"IETF/RFC-987/RFC-987.txt","version":null},{"body":"IETF","designation":"RFC 989","folder":"IETF/RFC-989","source":"IETF/RFC-989/RFC-989.txt","version":null}],"search_text":"IETF RFC 934 Network Working Group Marshall T. Rose (Delaware)\nRequest for Comments: 934 Einar A. Stefferud (NMA)\n January 1985\n\n Proposed Standard for Message Encapsulation\n\nSTATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction, Scope, and Motivation\n\n The services that a user agent (UA) can offer are varied. Although\n all outgoing mail may be thought of as going through a single posting\n slot to connect to the message transport system (MTS), it is possible\n to consider a message draft being posted as described by one of the\n following four types of postings:\n\n Originate - a new message is composed from scratch, which, to the\n knowledge of the UA, is unrelated to any message previously\n handled by the user.\n\n Reply - a message is composed as a reply 934 delivery path trust nested-reference unchanged"},{"id":"IETF RFC 936","type":"specification","body":"IETF","designation":"RFC 936","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc936.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc936.txt","https://www.rfc-editor.org/rfc/rfc936.pdf"],"folder":"IETF/RFC-936","files":{"txt":{"path":"standards/IETF/RFC-936/RFC-936.txt","sha256":"df633c2a4abfd22695861603ccd977ce898904eda85891bf1d1ac9c97c3d2931"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Michael J. Karels\nRequest for Comments: 936 UC Berkeley\n February 1985\n\n Another Internet Subnet Addressing Scheme\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n There have been several proposals for schemes to allow the use of a\n single Internet network number to refer to a collection of physical\n networks under common administration which are reachable from the\n rest of the Internet by a common route. Such schemes allow a\n simplified view of an otherwise complicated topology from hosts and\n gateways outside of this collection. They allow the complexity of\n the number and type of these networks, and routing to them, to be\n localized. Additions and changes in configuration thus cause no\n detectable change,","scope_keywords":["936","algorithm"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 936 Network Working Group Michael J. Karels\nRequest for Comments: 936 UC Berkeley\n February 1985\n\n Another Internet Subnet Addressing Scheme\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nIntroduction\n\n There have been several proposals for schemes to allow the use of a\n single Internet network number to refer to a collection of physical\n networks under common administration which are reachable from the\n rest of the Internet by a common route. Such schemes allow a\n simplified view of an otherwise complicated topology from hosts and\n gateways outside of this collection. They allow the complexity of\n the number and type of these networks, and routing to them, to be\n localized. Additions and changes in configuration thus cause no\n detectable change, 936 algorithm nested-reference unchanged"},{"id":"IETF RFC 938","type":"specification","body":"IETF","designation":"RFC 938","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc938.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc938.txt","https://www.rfc-editor.org/rfc/rfc938.pdf"],"folder":"IETF/RFC-938","files":{"txt":{"path":"standards/IETF/RFC-938/RFC-938.txt","sha256":"ae5992f6f141237c1f4af4b1b838f339009882ee93214976ab160e73ada56106"}},"tags":["nested-reference","unchanged"],"summary":"The Internet Reliable Transaction Protocol (IRTP) is a transport\n level host to host protocol designed for an internet environment. It\n provides reliable, sequenced delivery of packets of data between\n hosts and multiplexes/demultiplexes streams of packets from/to user\n processes representing ports. It is simple to implement, with a\n minimum of connection management, at the possible expense of\n efficiency.\n\nMiller [Page i]\n\f\n\nRFC 938 February 1985\nInternet Reliable Transaction Protocol","scope_keywords":["938","delivery","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 943","folder":"IETF/RFC-943","source":"IETF/RFC-943/RFC-943.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 938 The Internet Reliable Transaction Protocol (IRTP) is a transport\n level host to host protocol designed for an internet environment. It\n provides reliable, sequenced delivery of packets of data between\n hosts and multiplexes/demultiplexes streams of packets from/to user\n processes representing ports. It is simple to implement, with a\n minimum of connection management, at the possible expense of\n efficiency.\n\nMiller [Page i]\n\f\n\nRFC 938 February 1985\nInternet Reliable Transaction Protocol 938 delivery management pid nested-reference unchanged"},{"id":"IETF RFC 940","type":"specification","body":"IETF","designation":"RFC 940","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc940.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc940.txt","https://www.rfc-editor.org/rfc/rfc940.pdf"],"folder":"IETF/RFC-940","files":{"txt":{"path":"standards/IETF/RFC-940/RFC-940.txt","sha256":"eb4c37e8e93601a2ff239ea9b13cf459173e4ee03bc2b016be843db454434fc7"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group GADS\nRequest for Comments: 940 \n April 1985\n\n Toward an Internet Standard Scheme for Subnetting\n\nSTATUS OF THIS MEMO\n\n This RFC discusses standardizing the protocol used in subnetted\n environments in the ARPA-Internet. Distribution of this memo is\n unlimited.\n\n The author of this RFC is the Gateway Algorithms and Data Structures\n (GADS) Task Force, chaired by David L. Mills.\n\nINTRODUCTION\n\n Several sites now contain a complex of local links connected to the\n Internet via a gateway. The details of the internal connectivity are\n of little interest to the rest of the Internet.\n\n One way of organizing these local complexes of links is to use the\n same strategy as the Internet uses to organize networks, that is, to\n declare each link to be an entity (like a network) and to\n interconnect the links with devices that perform routing functions\n (like gateways). This general ","scope_keywords":["940","algorithm","algorithms","key"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1075","folder":"IETF/RFC-1075","source":"IETF/RFC-1075/RFC-1075.txt","version":null},{"body":"IETF","designation":"RFC 944","folder":"IETF/RFC-944","source":"IETF/RFC-944/RFC-944.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 940 Network Working Group GADS\nRequest for Comments: 940 \n April 1985\n\n Toward an Internet Standard Scheme for Subnetting\n\nSTATUS OF THIS MEMO\n\n This RFC discusses standardizing the protocol used in subnetted\n environments in the ARPA-Internet. Distribution of this memo is\n unlimited.\n\n The author of this RFC is the Gateway Algorithms and Data Structures\n (GADS) Task Force, chaired by David L. Mills.\n\nINTRODUCTION\n\n Several sites now contain a complex of local links connected to the\n Internet via a gateway. The details of the internal connectivity are\n of little interest to the rest of the Internet.\n\n One way of organizing these local complexes of links is to use the\n same strategy as the Internet uses to organize networks, that is, to\n declare each link to be an entity (like a network) and to\n interconnect the links with devices that perform routing functions\n (like gateways). This general  940 algorithm algorithms key nested-reference unchanged"},{"id":"IETF RFC 941","type":"specification","body":"IETF","designation":"RFC 941","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc941.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc941.txt","https://www.rfc-editor.org/rfc/rfc941.pdf"],"folder":"IETF/RFC-941","files":{"txt":{"path":"standards/IETF/RFC-941/RFC-941.txt","sha256":"daaccbebccd037349208b58e0c61474ff068b2e60fb8cb3f5b982cef169688b4"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ISO\nRequest for Comments: 941 April 1985\n\n Addendum to the Network Service Definition Covering\n Network Layer Addressing\n\n ISO/DP8348/DAD2\n (also TC 97/SC 6/N 3444)\n\nStatus of this RFC:\n\n This document is distributed as an RFC for information only. It does\n not specify a standard for the ARPA-Internet. Distribution of this\n document is unlimited.\n\nNote:\n\n This document has been prepared by retyping the text of ISO/DP8348/DAD2\n of October 1984 (also numbered SC 6/N 3444), which is currently\n undergoing voting within ISO as a Draft Proposed Addendum to the\n Network Service Definition. Although this RFC has been reviewed after\n typing, and is believed to be substantially correct, it is possible\n that typographic errors not present in the ISO document have been\n overlooked.\n\nAlex McKenzie\nBBN Laboratories\n\nISO/TC-97/SC-6 [Page 1]\n\fRFC 941 April 1985\nNetwork Layer Addres","scope_keywords":["941","identification"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null}],"search_text":"IETF RFC 941 Network Working Group ISO\nRequest for Comments: 941 April 1985\n\n Addendum to the Network Service Definition Covering\n Network Layer Addressing\n\n ISO/DP8348/DAD2\n (also TC 97/SC 6/N 3444)\n\nStatus of this RFC:\n\n This document is distributed as an RFC for information only. It does\n not specify a standard for the ARPA-Internet. Distribution of this\n document is unlimited.\n\nNote:\n\n This document has been prepared by retyping the text of ISO/DP8348/DAD2\n of October 1984 (also numbered SC 6/N 3444), which is currently\n undergoing voting within ISO as a Draft Proposed Addendum to the\n Network Service Definition. Although this RFC has been reviewed after\n typing, and is believed to be substantially correct, it is possible\n that typographic errors not present in the ISO document have been\n overlooked.\n\nAlex McKenzie\nBBN Laboratories\n\nISO/TC-97/SC-6 [Page 1]\n\fRFC 941 April 1985\nNetwork Layer Addres 941 identification nested-reference unchanged"},{"id":"IETF RFC 946","type":"specification","body":"IETF","designation":"RFC 946","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc946.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc946.txt","https://www.rfc-editor.org/rfc/rfc946.pdf"],"folder":"IETF/RFC-946","files":{"txt":{"path":"standards/IETF/RFC-946/RFC-946.txt","sha256":"d0b384a745fc9b7fc3e1311758a4c5a64344caa6a626888cc8670d73a8a83b8d"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group R. Nedved\nRequest for Comments: 946 Carnegie-Mellon University\n May 1985\n\n TELNET TERMINAL LOCATION NUMBER OPTION\n\nStatus of this Memo\n\n This RFC proposes a new option for Telnet for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n In a community of users that share a large degree of common\n facilities, it is often advantageous to use some common feature to\n improve software performance and reduce initial implementation costs.\n\n In March of 1982, CMU designed and implemented based on the growing\n CMU PUP-based network a terminal location database and modified\n existing network software to handle a 64-bit number which some call\n the Terminal Location Number or TTYLOC for short. The number can be\n efficiently stored in operating systems tables and can be passed\n between various","scope_keywords":["946"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 946 Network Working Group R. Nedved\nRequest for Comments: 946 Carnegie-Mellon University\n May 1985\n\n TELNET TERMINAL LOCATION NUMBER OPTION\n\nStatus of this Memo\n\n This RFC proposes a new option for Telnet for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n In a community of users that share a large degree of common\n facilities, it is often advantageous to use some common feature to\n improve software performance and reduce initial implementation costs.\n\n In March of 1982, CMU designed and implemented based on the growing\n CMU PUP-based network a terminal location database and modified\n existing network software to handle a 64-bit number which some call\n the Terminal Location Number or TTYLOC for short. The number can be\n efficiently stored in operating systems tables and can be passed\n between various 946 nested-reference unchanged"},{"id":"IETF RFC 950","type":"specification","body":"IETF","designation":"RFC 950","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc950.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc950.txt","https://www.rfc-editor.org/rfc/rfc950.pdf"],"folder":"IETF/RFC-950","files":{"txt":{"path":"standards/IETF/RFC-950/RFC-950.txt","sha256":"59294d6dbdfcb02589d00ba66386261f8c6e714d8b3f3d2e37b39424f5c9a795"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group J. Mogul (Stanford)\nRequest for Comments: 950 J. Postel (ISI)\n August 1985\n\n Internet Standard Subnetting Procedure\n\nStatus Of This Memo\n\n This RFC specifies a protocol for the ARPA-Internet community. If\n subnetting is implemented it is strongly recommended that these\n procedures be followed. Distribution of this memo is unlimited.\n\nOverview\n\n This memo discusses the utility of \"subnets\" of Internet networks,\n which are logically visible sub-sections of a single Internet\n network. For administrative or technical reasons, many organizations\n have chosen to divide one Internet network into several subnets,\n instead of acquiring a set of Internet network numbers. This memo\n specifies procedures for the use of subnets. These procedures are\n for hosts (e.g., workstations). The procedures used in and between\n subnet gateways are not fully described. Important motivation ","scope_keywords":["950","algorithm","algorithms"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0950","folder":"IETF/RFC-0950","source":"IETF/RFC-0950/RFC-0950.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1002","folder":"IETF/RFC-1002","source":"IETF/RFC-1002/RFC-1002.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1219","folder":"IETF/RFC-1219","source":"IETF/RFC-1219/RFC-1219.txt","version":null},{"body":"IETF","designation":"RFC 1256","folder":"IETF/RFC-1256","source":"IETF/RFC-1256/RFC-1256.txt","version":null},{"body":"IETF","designation":"RFC 1287","folder":"IETF/RFC-1287","source":"IETF/RFC-1287/RFC-1287.txt","version":null},{"body":"IETF","designation":"RFC 1349","folder":"IETF/RFC-1349","source":"IETF/RFC-1349/RFC-1349.txt","version":null},{"body":"IETF","designation":"RFC 1395","folder":"IETF/RFC-1395","source":"IETF/RFC-1395/RFC-1395.txt","version":null},{"body":"IETF","designation":"RFC 1497","folder":"IETF/RFC-1497","source":"IETF/RFC-1497/RFC-1497.txt","version":null},{"body":"IETF","designation":"RFC 1533","folder":"IETF/RFC-1533","source":"IETF/RFC-1533/RFC-1533.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null},{"body":"IETF","designation":"RFC 1878","folder":"IETF/RFC-1878","source":"IETF/RFC-1878/RFC-1878.txt","version":null},{"body":"IETF","designation":"RFC 2132","folder":"IETF/RFC-2132","source":"IETF/RFC-2132/RFC-2132.txt","version":null},{"body":"IETF","designation":"RFC 2401","folder":"IETF/RFC-2401","source":"IETF/RFC-2401/RFC-2401.txt","version":null},{"body":"IETF","designation":"RFC 2663","folder":"IETF/RFC-2663","source":"IETF/RFC-2663/RFC-2663.txt","version":null},{"body":"IETF","designation":"RFC 3021","folder":"IETF/RFC-3021","source":"IETF/RFC-3021/RFC-3021.txt","version":null},{"body":"IETF","designation":"RFC 3442","folder":"IETF/RFC-3442","source":"IETF/RFC-3442/RFC-3442.txt","version":null},{"body":"IETF","designation":"RFC 3790","folder":"IETF/RFC-3790","source":"IETF/RFC-3790/RFC-3790.txt","version":null},{"body":"IETF","designation":"RFC 4903","folder":"IETF/RFC-4903","source":"IETF/RFC-4903/RFC-4903.txt","version":null},{"body":"IETF","designation":"RFC 5942","folder":"IETF/RFC-5942","source":"IETF/RFC-5942/RFC-5942.txt","version":null},{"body":"IETF","designation":"RFC 6274","folder":"IETF/RFC-6274","source":"IETF/RFC-6274/RFC-6274.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 950 Network Working Group J. Mogul (Stanford)\nRequest for Comments: 950 J. Postel (ISI)\n August 1985\n\n Internet Standard Subnetting Procedure\n\nStatus Of This Memo\n\n This RFC specifies a protocol for the ARPA-Internet community. If\n subnetting is implemented it is strongly recommended that these\n procedures be followed. Distribution of this memo is unlimited.\n\nOverview\n\n This memo discusses the utility of \"subnets\" of Internet networks,\n which are logically visible sub-sections of a single Internet\n network. For administrative or technical reasons, many organizations\n have chosen to divide one Internet network into several subnets,\n instead of acquiring a set of Internet network numbers. This memo\n specifies procedures for the use of subnets. These procedures are\n for hosts (e.g., workstations). The procedures used in and between\n subnet gateways are not fully described. Important motivation  950 algorithm algorithms nested-reference unchanged"},{"id":"IETF RFC 955","type":"specification","body":"IETF","designation":"RFC 955","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc955.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc955.txt","https://www.rfc-editor.org/rfc/rfc955.pdf"],"folder":"IETF/RFC-955","files":{"txt":{"path":"standards/IETF/RFC-955/RFC-955.txt","sha256":"d05bf7a44083907f1afbc93e55ffd37a26ed995d29a3e9c756362bd65eea4d8e"}},"tags":["nested-reference","unchanged"],"summary":"here is to urge the solution of this problem within the Internet\n protocol family.","scope_keywords":["955","attribute","attributes"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1045","folder":"IETF/RFC-1045","source":"IETF/RFC-1045/RFC-1045.txt","version":null}],"search_text":"IETF RFC 955 here is to urge the solution of this problem within the Internet\n protocol family. 955 attribute attributes nested-reference unchanged"},{"id":"IETF RFC 956","type":"specification","body":"IETF","designation":"RFC 956","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc956.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc956.txt","https://www.rfc-editor.org/rfc/rfc956.pdf"],"folder":"IETF/RFC-956","files":{"txt":{"path":"standards/IETF/RFC-956/RFC-956.txt","sha256":"9e27f916f3e66aa82d5c8bef75604cd96b3be15eb27d686262258986521ecc45"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 956 M/A-COM Linkabit\n September 1985\n\n Algorithms for Synchronizing Network Clocks\n\nStatus of this Memo\n\n This RFC discussed clock synchronization algorithms for the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Majority-Subset Algorithms\n 3. Clustering Algorithms\n 4. Application to Time-Synchronization Data\n 5. Summary and Conclusions\n 6. References\n Appendix\n A. Experimental Determination of Internet Host Clock Accuracies\n A1. UDP Time Protocol Experiment\n A2. ICMP Timestamp Message Experiment\n A3. Comparison of UDP and ICMP Time\n\nList of Tables\n\n Table 1. C(n,k) for n from 2 to 20\n Table 2. Majority Subsets for n = 3,4,5\n Table 3. Clustering Algorithm using UDP Time Protocol Data\n Table 4. Clustering Algorithm us","scope_keywords":["956","algorithm","algorithms","path","timestamp","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 956 Network Working Group D.L. Mills\nRequest for Comments: 956 M/A-COM Linkabit\n September 1985\n\n Algorithms for Synchronizing Network Clocks\n\nStatus of this Memo\n\n This RFC discussed clock synchronization algorithms for the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Majority-Subset Algorithms\n 3. Clustering Algorithms\n 4. Application to Time-Synchronization Data\n 5. Summary and Conclusions\n 6. References\n Appendix\n A. Experimental Determination of Internet Host Clock Accuracies\n A1. UDP Time Protocol Experiment\n A2. ICMP Timestamp Message Experiment\n A3. Comparison of UDP and ICMP Time\n\nList of Tables\n\n Table 1. C(n,k) for n from 2 to 20\n Table 2. Majority Subsets for n = 3,4,5\n Table 3. Clustering Algorithm using UDP Time Protocol Data\n Table 4. Clustering Algorithm us 956 algorithm algorithms path timestamp trust nested-reference unchanged"},{"id":"IETF RFC 957","type":"specification","body":"IETF","designation":"RFC 957","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc957.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc957.txt","https://www.rfc-editor.org/rfc/rfc957.pdf"],"folder":"IETF/RFC-957","files":{"txt":{"path":"standards/IETF/RFC-957/RFC-957.txt","sha256":"1f88d9a67ba48c3576de023c6992a3f806092b8774c94b80b2750b630491aabb"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 957 M/A-COM Linkabit\n September 1985\n\n Experiments in Network Clock Synchronization\n\nStatus of this Memo\n\n This RFC discusses some experiments in clock synchronization in the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Design of the Synchronization Algorithm\n 2.1. The Logical Clock\n 2.2. Linear Phase Adjustments\n 2.3. Nonlinear Phase Adjustments\n 3. Synchronizing Network Clocks\n 3.1. Reference Clocks and Reference Hosts\n 3.2. Distribution of Timing Information\n 4. Experimental Validation of the Design\n 4.1. Experiment Design\n 4.2. Experiment Execution\n 4.3. Discussion of Results\n 4.3.1. On Power-Grid Clocks\n 4.3.2. On Clocks Synchronized via Network Links\n 4.3.3. On the Accuracy of Radio Clocks\n 4.3.3.1. The Spect","scope_keywords":["957","algorithm","algorithms","subject","timestamp","timestamps","validation"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 957 Network Working Group D.L. Mills\nRequest for Comments: 957 M/A-COM Linkabit\n September 1985\n\n Experiments in Network Clock Synchronization\n\nStatus of this Memo\n\n This RFC discusses some experiments in clock synchronization in the\n ARPA-Internet community, and requests discussion and suggestions for\n improvements. Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Design of the Synchronization Algorithm\n 2.1. The Logical Clock\n 2.2. Linear Phase Adjustments\n 2.3. Nonlinear Phase Adjustments\n 3. Synchronizing Network Clocks\n 3.1. Reference Clocks and Reference Hosts\n 3.2. Distribution of Timing Information\n 4. Experimental Validation of the Design\n 4.1. Experiment Design\n 4.2. Experiment Execution\n 4.3. Discussion of Results\n 4.3.1. On Power-Grid Clocks\n 4.3.2. On Clocks Synchronized via Network Links\n 4.3.3. On the Accuracy of Radio Clocks\n 4.3.3.1. The Spect 957 algorithm algorithms subject timestamp timestamps validation nested-reference unchanged"},{"id":"IETF RFC 958","type":"specification","body":"IETF","designation":"RFC 958","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc958.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc958.txt","https://www.rfc-editor.org/rfc/rfc958.pdf"],"folder":"IETF/RFC-958","files":{"txt":{"path":"standards/IETF/RFC-958/RFC-958.txt","sha256":"86a659beb30ff1afb05875652824dc63627f74337e6d93df77773a7518243732"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 958 M/A-COM Linkabit\n September 1985\n\n Network Time Protocol (NTP)\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Service Model\n 3. Protocol Overview\n 4. State Variables and Formats\n 5. Protocol Operation\n 5.1. Protocol Modes\n 5.2. Message Processing\n 5.3. Network Considerations\n 5.4. Leap Seconds\n 6. References\n Appendix A. UDP Header Format\n Appendix B. NTP Data Format\n\n1. Introduction\n\n This document describes the Network Time Protocol (NTP), a protocol\n for synchronizing a set of network clocks using a set of distributed\n clients and servers. NTP is built on the User Datagram Protocol\n (UDP) [13], which provides a connectionless transport mechan","scope_keywords":["958","algorithm","algorithms","authentication","management","path","presentation","timestamp","timestamps"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1166","folder":"IETF/RFC-1166","source":"IETF/RFC-1166/RFC-1166.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 960","folder":"IETF/RFC-960","source":"IETF/RFC-960/RFC-960.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 997","folder":"IETF/RFC-997","source":"IETF/RFC-997/RFC-997.txt","version":null}],"search_text":"IETF RFC 958 Network Working Group D.L. Mills\nRequest for Comments: 958 M/A-COM Linkabit\n September 1985\n\n Network Time Protocol (NTP)\n\nStatus of this Memo\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nTable of Contents\n\n 1. Introduction\n 2. Service Model\n 3. Protocol Overview\n 4. State Variables and Formats\n 5. Protocol Operation\n 5.1. Protocol Modes\n 5.2. Message Processing\n 5.3. Network Considerations\n 5.4. Leap Seconds\n 6. References\n Appendix A. UDP Header Format\n Appendix B. NTP Data Format\n\n1. Introduction\n\n This document describes the Network Time Protocol (NTP), a protocol\n for synchronizing a set of network clocks using a set of distributed\n clients and servers. NTP is built on the User Datagram Protocol\n (UDP) [13], which provides a connectionless transport mechan 958 algorithm algorithms authentication management path presentation timestamp timestamps nested-reference unchanged"},{"id":"IETF RFC 963","type":"specification","body":"IETF","designation":"RFC 963","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc963.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc963.txt","https://www.rfc-editor.org/rfc/rfc963.pdf"],"folder":"IETF/RFC-963","files":{"txt":{"path":"standards/IETF/RFC-963/RFC-963.txt","sha256":"f96124e3261d587bed71060aefc40eb4589a1bac65d0cf38b022e82feed9c9b9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Deepinder P. Sidhu\nRequest for Comments: 963 Iowa State University\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD INTERNET PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Internet Protocol (MIL-STD-1777) so that one can\n obtain a reliable implementation of this protocol standard.\n Distribution of this note is unlimited.\n\nABSTRACT\n\n This paper points out several significant problems in the\n specification of the Military Standard Internet Protocol\n (MIL-STD-1777, dated August 1983 [MILS83a]). These results are based\n on an initial investigation of this protocol standard. The problems\n are: (1) a failure to reassemble fragmented messages completely; (2)\n a missing state transition; (3) errors in testing for reassembly\n completion; (4) errors in computing fragment sizes;","scope_keywords":["963","delivery"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 963 Network Working Group Deepinder P. Sidhu\nRequest for Comments: 963 Iowa State University\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD INTERNET PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Internet Protocol (MIL-STD-1777) so that one can\n obtain a reliable implementation of this protocol standard.\n Distribution of this note is unlimited.\n\nABSTRACT\n\n This paper points out several significant problems in the\n specification of the Military Standard Internet Protocol\n (MIL-STD-1777, dated August 1983 [MILS83a]). These results are based\n on an initial investigation of this protocol standard. The problems\n are: (1) a failure to reassemble fragmented messages completely; (2)\n a missing state transition; (3) errors in testing for reassembly\n completion; (4) errors in computing fragment sizes; 963 delivery nested-reference unchanged"},{"id":"IETF RFC 964","type":"specification","body":"IETF","designation":"RFC 964","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc964.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc964.txt","https://www.rfc-editor.org/rfc/rfc964.pdf"],"folder":"IETF/RFC-964","files":{"txt":{"path":"standards/IETF/RFC-964/RFC-964.txt","sha256":"e102129df374c4888e308ec5cc02856d31b7b3127812d9160cb2cc12ed2d49b5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Deepinder P. Sidhu\nRequest for Comments: 964 Thomas P. Blumer\n SDC - A Burroughs Company\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD TRANSMISSION CONTROL PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Transmission Control Protocol (MIL-STD-1778) so\n that one can obtain a reliable implementation of this protocol\n standard. Distribution of this note is unlimited.\n\n Reprinted from: Proc. Protocol Specification, Testing and\n Verification IV, (ed.) Y. Yemini, et al, North-Holland (1984).\n\nABSTRACT\n\n This note points out three errors with the specification of the\n Military Standard Transmission Control Protocol (MIL-STD-1778, dated\n August 1983 [MILS83]). These results are based on an initial\n investigation of this protocol standard. The first problem is that\n data acc","scope_keywords":["964","delivery","management","policy"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0964","folder":"IETF/RFC-0964","source":"IETF/RFC-0964/RFC-0964.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 4614","folder":"IETF/RFC-4614","source":"IETF/RFC-4614/RFC-4614.txt","version":null},{"body":"IETF","designation":"RFC 7414","folder":"IETF/RFC-7414","source":"IETF/RFC-7414/RFC-7414.txt","version":null},{"body":"IETF","designation":"RFC 961","folder":"IETF/RFC-961","source":"IETF/RFC-961/RFC-961.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 964 Network Working Group Deepinder P. Sidhu\nRequest for Comments: 964 Thomas P. Blumer\n SDC - A Burroughs Company\n November 1985\n\n SOME PROBLEMS WITH THE SPECIFICATION OF THE\n MILITARY STANDARD TRANSMISSION CONTROL PROTOCOL\n\nSTATUS OF THIS MEMO\n\n The purpose of this RFC is to provide helpful information on the\n Military Standard Transmission Control Protocol (MIL-STD-1778) so\n that one can obtain a reliable implementation of this protocol\n standard. Distribution of this note is unlimited.\n\n Reprinted from: Proc. Protocol Specification, Testing and\n Verification IV, (ed.) Y. Yemini, et al, North-Holland (1984).\n\nABSTRACT\n\n This note points out three errors with the specification of the\n Military Standard Transmission Control Protocol (MIL-STD-1778, dated\n August 1983 [MILS83]). These results are based on an initial\n investigation of this protocol standard. The first problem is that\n data acc 964 delivery management policy nested-reference unchanged"},{"id":"IETF RFC 966","type":"specification","body":"IETF","designation":"RFC 966","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc966.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc966.txt","https://www.rfc-editor.org/rfc/rfc966.pdf"],"folder":"IETF/RFC-966","files":{"txt":{"path":"standards/IETF/RFC-966/RFC-966.txt","sha256":"c92b1a126fd242cc108bb0ffd36274857c9c4e8e0556092bfe43f8f97a866904"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group S. E. Deering\nRequest for Comments: 966 D. R. Cheriton\n Stanford University\n December 1985\n\n Host Groups:\n A Multicast Extension to the Internet Protocol\n\n1. Status of this Memo\n\n This RFC defines a model of service for Internet multicasting and\n proposes an extension to the Internet Protocol (IP) to support such a\n multicast service. Discussion and suggestions for improvements are\n requested. Distribution of this memo is unlimited.\n\n2. Acknowledgements\n\n This memo was adapted from a paper [7] presented at the Ninth Data\n Communications Symposium. This work was sponsored in part by the\n Defense Advanced Research Projects Agency under contract N00039-83-\n K-0431 and National Science Foundation Grant DCR-83-52048.\n\n The Internet task force on end-to-end protocols, headed by Bob\n Braden, has provided valuable input in the development of the host\n group model.\n\n3. Intro","scope_keywords":["966","delivery","management","path"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1045","folder":"IETF/RFC-1045","source":"IETF/RFC-1045/RFC-1045.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 966 Network Working Group S. E. Deering\nRequest for Comments: 966 D. R. Cheriton\n Stanford University\n December 1985\n\n Host Groups:\n A Multicast Extension to the Internet Protocol\n\n1. Status of this Memo\n\n This RFC defines a model of service for Internet multicasting and\n proposes an extension to the Internet Protocol (IP) to support such a\n multicast service. Discussion and suggestions for improvements are\n requested. Distribution of this memo is unlimited.\n\n2. Acknowledgements\n\n This memo was adapted from a paper [7] presented at the Ninth Data\n Communications Symposium. This work was sponsored in part by the\n Defense Advanced Research Projects Agency under contract N00039-83-\n K-0431 and National Science Foundation Grant DCR-83-52048.\n\n The Internet task force on end-to-end protocols, headed by Bob\n Braden, has provided valuable input in the development of the host\n group model.\n\n3. Intro 966 delivery management path nested-reference unchanged"},{"id":"IETF RFC 969","type":"specification","body":"IETF","designation":"RFC 969","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc969.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc969.txt","https://www.rfc-editor.org/rfc/rfc969.pdf"],"folder":"IETF/RFC-969","files":{"txt":{"path":"standards/IETF/RFC-969/RFC-969.txt","sha256":"f41ceb26a25cb913c32c1d5e6102149071a33e878b15fcfa65366a530764f00b"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David D. Clark\nRequest for Comments: 969 Mark L. Lambert\n Lixia Zhang\n M. I. T. Laboratory for Computer Science\n December 1985\n\n NETBLT: A Bulk Data Transfer Protocol\n\n1. STATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n This is a preliminary discussion of the NETBLT protocol. It is\n published for discussion and comment, and does not constitute a\n standard. As the proposal may change, implementation of this\n document is not advised. Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n NETBLT (Network Block Transfer) is a transport level protocol\n intended for the rapid transfer of a large quantity of data between\n computers. It provides a transfer that is reliable and flow\n controlled, and is structured to provide maximum throughput over a\n wide variety of ne","scope_keywords":["969","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1045","folder":"IETF/RFC-1045","source":"IETF/RFC-1045/RFC-1045.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null},{"body":"IETF","designation":"RFC 998","folder":"IETF/RFC-998","source":"IETF/RFC-998/RFC-998.txt","version":null}],"search_text":"IETF RFC 969 Network Working Group David D. Clark\nRequest for Comments: 969 Mark L. Lambert\n Lixia Zhang\n M. I. T. Laboratory for Computer Science\n December 1985\n\n NETBLT: A Bulk Data Transfer Protocol\n\n1. STATUS OF THIS MEMO\n\n This RFC suggests a proposed protocol for the ARPA-Internet\n community, and requests discussion and suggestions for improvements.\n This is a preliminary discussion of the NETBLT protocol. It is\n published for discussion and comment, and does not constitute a\n standard. As the proposal may change, implementation of this\n document is not advised. Distribution of this memo is unlimited.\n\n2. INTRODUCTION\n\n NETBLT (Network Block Transfer) is a transport level protocol\n intended for the rapid transfer of a large quantity of data between\n computers. It provides a transfer that is reliable and flow\n controlled, and is structured to provide maximum throughput over a\n wide variety of ne 969 management pid nested-reference unchanged"},{"id":"IETF RFC 998","type":"specification","body":"IETF","designation":"RFC 998","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc998.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc998.txt","https://www.rfc-editor.org/rfc/rfc998.pdf"],"folder":"IETF/RFC-998","files":{"txt":{"path":"standards/IETF/RFC-998/RFC-998.txt","sha256":"aaafa72618820390f3638b82af5e4786c40b0e5a86ec8aaf2808428ab0d138c3"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David D. Clark\nRequest for Comments: 998 Mark L. Lambert\nObsoletes: RFC 969 Lixia Zhang\n MIT\n March 1987\n\n NETBLT: A Bulk Data Transfer Protocol\n\n1. Status\n\n This document is a description of, and a specification for, the\n NETBLT protocol. It is a revision of the specification published in\n NIC RFC-969. The protocol has been revised after extensive research\n into NETBLT's performance over long-delay, high-bandwidth satellite\n channels. Most of the changes in the protocol specification have to\n do with the computation and use of data timers in a multiple\n buffering data transfer model.\n\n This document is published for discussion and comment, and does not\n constitute a standard. The proposal may change and certain parts of\n the protocol have not yet been specified; implementation of this\n document is therefore not advised.\n\n2. Introduction\n\n NETBLT (NETwork BLock Tran","scope_keywords":["998","algorithm","algorithms","management","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1072","folder":"IETF/RFC-1072","source":"IETF/RFC-1072/RFC-1072.txt","version":null},{"body":"IETF","designation":"RFC 1106","folder":"IETF/RFC-1106","source":"IETF/RFC-1106/RFC-1106.txt","version":null},{"body":"IETF","designation":"RFC 1235","folder":"IETF/RFC-1235","source":"IETF/RFC-1235/RFC-1235.txt","version":null},{"body":"IETF","designation":"RFC 1323","folder":"IETF/RFC-1323","source":"IETF/RFC-1323/RFC-1323.txt","version":null},{"body":"IETF","designation":"RFC 1986","folder":"IETF/RFC-1986","source":"IETF/RFC-1986/RFC-1986.txt","version":null},{"body":"IETF","designation":"RFC 2018","folder":"IETF/RFC-2018","source":"IETF/RFC-2018/RFC-2018.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null}],"search_text":"IETF RFC 998 Network Working Group David D. Clark\nRequest for Comments: 998 Mark L. Lambert\nObsoletes: RFC 969 Lixia Zhang\n MIT\n March 1987\n\n NETBLT: A Bulk Data Transfer Protocol\n\n1. Status\n\n This document is a description of, and a specification for, the\n NETBLT protocol. It is a revision of the specification published in\n NIC RFC-969. The protocol has been revised after extensive research\n into NETBLT's performance over long-delay, high-bandwidth satellite\n channels. Most of the changes in the protocol specification have to\n do with the computation and use of data timers in a multiple\n buffering data transfer model.\n\n This document is published for discussion and comment, and does not\n constitute a standard. The proposal may change and certain parts of\n the protocol have not yet been specified; implementation of this\n document is therefore not advised.\n\n2. Introduction\n\n NETBLT (NETwork BLock Tran 998 algorithm algorithms management pid nested-reference unchanged"},{"id":"IETF RFC 972","type":"specification","body":"IETF","designation":"RFC 972","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc972.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc972.txt","https://www.rfc-editor.org/rfc/rfc972.pdf"],"folder":"IETF/RFC-972","files":{"txt":{"path":"standards/IETF/RFC-972/RFC-972.txt","sha256":"63f169e50f925d6a694bac6f94b9330a6ba42cab4a0343980fbf45aeb3717fb5"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group F. Wancho\nRequest for Comments: 972 WSMR\n January 1986\n\n Password Generator Protocol\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n on the ARPA Internet that choose to implement a Password Generator\n Protocol (PWDGEN) are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\nBACKGROUND\n\n Many security-conscious host administrators are becoming increasingly\n aware that user-selected login passwords are too easy to guess for\n even casual penetration attempts. Some sites have implemented\n dictionary lookup techniques in their password programs to prevent\n ordinary words from being used. Others have implemented some variant\n of a randomly generated password with mixed success. The problem\n arises from the fact that such passwords are difficult to remember\n because they cannot be pronounced ","scope_keywords":["972","algorithm","crl"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1010","folder":"IETF/RFC-1010","source":"IETF/RFC-1010/RFC-1010.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null},{"body":"IETF","designation":"RFC 990","folder":"IETF/RFC-990","source":"IETF/RFC-990/RFC-990.txt","version":null}],"search_text":"IETF RFC 972 Network Working Group F. Wancho\nRequest for Comments: 972 WSMR\n January 1986\n\n Password Generator Protocol\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n on the ARPA Internet that choose to implement a Password Generator\n Protocol (PWDGEN) are expected to adopt and implement this standard.\n Distribution of this memo is unlimited.\n\nBACKGROUND\n\n Many security-conscious host administrators are becoming increasingly\n aware that user-selected login passwords are too easy to guess for\n even casual penetration attempts. Some sites have implemented\n dictionary lookup techniques in their password programs to prevent\n ordinary words from being used. Others have implemented some variant\n of a randomly generated password with mixed success. The problem\n arises from the fact that such passwords are difficult to remember\n because they cannot be pronounced  972 algorithm crl nested-reference unchanged"},{"id":"IETF RFC 973","type":"specification","body":"IETF","designation":"RFC 973","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc973.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc973.txt","https://www.rfc-editor.org/rfc/rfc973.pdf"],"folder":"IETF/RFC-973","files":{"txt":{"path":"standards/IETF/RFC-973/RFC-973.txt","sha256":"ff4b56cfa07101532d1145fabb24b4f9def658a62137c08a046dab66b31b0587"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Paul Mockapetris\nRequest for Comments: 973 ISI\n January 1986\n\n Domain System Changes and Observations\n\nSTATUS OF THIS MEMO\n\n This RFC documents updates to Domain Name System specifications\n RFC-882 [1] and RFC-883 [2], suggests some operational guidelines,\n and discusses some experiences and problem areas in the present\n system. Distribution of this memo is unlimited.\n\n This document includes all changes to the Domain System through\n January, 1986. Change notices and additional discussion are\n available online in file [USC-ISIB.ARPA] DOMAIN.CHANGES.\n\nOVERVIEW\n\n This memo is divided into four major sections:\n\n \"UPDATES\" which discusses changes to the domain specification\n which are in widespread use and should be regarded as being part\n of the specification.\n\n \"OPERATION GUIDELINES\" which suggests rules-of-thumb for using the\n domain system and configuring your datab","scope_keywords":["973","algorithm","algorithms","pid","tls"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 973 Network Working Group Paul Mockapetris\nRequest for Comments: 973 ISI\n January 1986\n\n Domain System Changes and Observations\n\nSTATUS OF THIS MEMO\n\n This RFC documents updates to Domain Name System specifications\n RFC-882 [1] and RFC-883 [2], suggests some operational guidelines,\n and discusses some experiences and problem areas in the present\n system. Distribution of this memo is unlimited.\n\n This document includes all changes to the Domain System through\n January, 1986. Change notices and additional discussion are\n available online in file [USC-ISIB.ARPA] DOMAIN.CHANGES.\n\nOVERVIEW\n\n This memo is divided into four major sections:\n\n \"UPDATES\" which discusses changes to the domain specification\n which are in widespread use and should be regarded as being part\n of the specification.\n\n \"OPERATION GUIDELINES\" which suggests rules-of-thumb for using the\n domain system and configuring your datab 973 algorithm algorithms pid tls nested-reference unchanged"},{"id":"IETF RFC 974","type":"specification","body":"IETF","designation":"RFC 974","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc974.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc974.txt","https://www.rfc-editor.org/rfc/rfc974.pdf"],"folder":"IETF/RFC-974","files":{"txt":{"path":"standards/IETF/RFC-974/RFC-974.txt","sha256":"318ffff5486dea88b454225d89b513b0a0e86be814657feb09d9e3f9016958a6"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Craig Partridge\nRequest for Comments: 974 CSNET CIC BBN Laboratories Inc\n January 1986\n\n MAIL ROUTING AND THE DOMAIN SYSTEM\n\nStatus of this Memo\n\n This RFC presents a description of how mail systems on the Internet\n are expected to route messages based on information from the domain\n system described in RFCs 882, 883 and 973. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n The purpose of this memo is to explain how mailers are to decide how\n to route a message addressed to a given Internet domain name. This\n involves a discussion of how mailers interpret MX RRs, which are used\n for message routing. Note that this memo makes no statement about\n how mailers are to deal with MB and MG RRs, which are used for\n interpreting mailbox names.\n\n Under RFC-882 and RFC-883 certain assumptions about mail addresses\n have been changed. Up to now, one could usually assume ","scope_keywords":["974","pid"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0974","folder":"IETF/RFC-0974","source":"IETF/RFC-0974/RFC-0974.txt","version":null},{"body":"IETF","designation":"RFC 1001","folder":"IETF/RFC-1001","source":"IETF/RFC-1001/RFC-1001.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1032","folder":"IETF/RFC-1032","source":"IETF/RFC-1032/RFC-1032.txt","version":null},{"body":"IETF","designation":"RFC 1101","folder":"IETF/RFC-1101","source":"IETF/RFC-1101/RFC-1101.txt","version":null},{"body":"IETF","designation":"RFC 1426","folder":"IETF/RFC-1426","source":"IETF/RFC-1426/RFC-1426.txt","version":null},{"body":"IETF","designation":"RFC 1480","folder":"IETF/RFC-1480","source":"IETF/RFC-1480/RFC-1480.txt","version":null},{"body":"IETF","designation":"RFC 1486","folder":"IETF/RFC-1486","source":"IETF/RFC-1486/RFC-1486.txt","version":null},{"body":"IETF","designation":"RFC 1528","folder":"IETF/RFC-1528","source":"IETF/RFC-1528/RFC-1528.txt","version":null},{"body":"IETF","designation":"RFC 1535","folder":"IETF/RFC-1535","source":"IETF/RFC-1535/RFC-1535.txt","version":null},{"body":"IETF","designation":"RFC 1536","folder":"IETF/RFC-1536","source":"IETF/RFC-1536/RFC-1536.txt","version":null},{"body":"IETF","designation":"RFC 1537","folder":"IETF/RFC-1537","source":"IETF/RFC-1537/RFC-1537.txt","version":null},{"body":"IETF","designation":"RFC 1591","folder":"IETF/RFC-1591","source":"IETF/RFC-1591/RFC-1591.txt","version":null},{"body":"IETF","designation":"RFC 1652","folder":"IETF/RFC-1652","source":"IETF/RFC-1652/RFC-1652.txt","version":null},{"body":"IETF","designation":"RFC 1653","folder":"IETF/RFC-1653","source":"IETF/RFC-1653/RFC-1653.txt","version":null},{"body":"IETF","designation":"RFC 1713","folder":"IETF/RFC-1713","source":"IETF/RFC-1713/RFC-1713.txt","version":null},{"body":"IETF","designation":"RFC 1845","folder":"IETF/RFC-1845","source":"IETF/RFC-1845/RFC-1845.txt","version":null},{"body":"IETF","designation":"RFC 1870","folder":"IETF/RFC-1870","source":"IETF/RFC-1870/RFC-1870.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2052","folder":"IETF/RFC-2052","source":"IETF/RFC-2052/RFC-2052.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 2219","folder":"IETF/RFC-2219","source":"IETF/RFC-2219/RFC-2219.txt","version":null},{"body":"IETF","designation":"RFC 2476","folder":"IETF/RFC-2476","source":"IETF/RFC-2476/RFC-2476.txt","version":null},{"body":"IETF","designation":"RFC 2532","folder":"IETF/RFC-2532","source":"IETF/RFC-2532/RFC-2532.txt","version":null},{"body":"IETF","designation":"RFC 2782","folder":"IETF/RFC-2782","source":"IETF/RFC-2782/RFC-2782.txt","version":null},{"body":"IETF","designation":"RFC 2821","folder":"IETF/RFC-2821","source":"IETF/RFC-2821/RFC-2821.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2852","folder":"IETF/RFC-2852","source":"IETF/RFC-2852/RFC-2852.txt","version":null},{"body":"IETF","designation":"RFC 3974","folder":"IETF/RFC-3974","source":"IETF/RFC-3974/RFC-3974.txt","version":null},{"body":"IETF","designation":"RFC 4409","folder":"IETF/RFC-4409","source":"IETF/RFC-4409/RFC-4409.txt","version":null},{"body":"IETF","designation":"RFC 5321","folder":"IETF/RFC-5321","source":"IETF/RFC-5321/RFC-5321.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 6950","folder":"IETF/RFC-6950","source":"IETF/RFC-6950/RFC-6950.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 974 Network Working Group Craig Partridge\nRequest for Comments: 974 CSNET CIC BBN Laboratories Inc\n January 1986\n\n MAIL ROUTING AND THE DOMAIN SYSTEM\n\nStatus of this Memo\n\n This RFC presents a description of how mail systems on the Internet\n are expected to route messages based on information from the domain\n system described in RFCs 882, 883 and 973. Distribution of this memo\n is unlimited.\n\nIntroduction\n\n The purpose of this memo is to explain how mailers are to decide how\n to route a message addressed to a given Internet domain name. This\n involves a discussion of how mailers interpret MX RRs, which are used\n for message routing. Note that this memo makes no statement about\n how mailers are to deal with MB and MG RRs, which are used for\n interpreting mailbox names.\n\n Under RFC-882 and RFC-883 certain assumptions about mail addresses\n have been changed. Up to now, one could usually assume  974 pid nested-reference unchanged"},{"id":"IETF RFC 975","type":"specification","body":"IETF","designation":"RFC 975","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc975.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc975.txt","https://www.rfc-editor.org/rfc/rfc975.pdf"],"folder":"IETF/RFC-975","files":{"txt":{"path":"standards/IETF/RFC-975/RFC-975.txt","sha256":"f8a8a46988230af6ce70e7c447486e957b167f28e9e994313047ef662d5cdd32"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D. L. Mills\nRequest for Comments: 975 M/A-COM Linkabit\n February 1986\n\n Autonomous Confederations\n\nStatus of This Memo\n\n This RFC proposes certain enhancements of the Exterior Gateway\n Protocol (EGP) to support a simple, multiple-level routing capability\n while preserving the robustness features of the current EGP model.\n It requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n The enhancements, which do not require retrofits in existing\n implementations in order to interoperate with enhanced\n implementations, in effect generalize the concept of core system to\n include multiple communities of autonomous systems, called autonomous\n confederations. Autonomous confederations maintain a higher degree of\n mutual trust than that assumed between autonomous systems in general,\n including reasonable protection against rout","scope_keywords":["975","algorithm","algorithms","path","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1093","folder":"IETF/RFC-1093","source":"IETF/RFC-1093/RFC-1093.txt","version":null},{"body":"IETF","designation":"RFC 1136","folder":"IETF/RFC-1136","source":"IETF/RFC-1136/RFC-1136.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 975 Network Working Group D. L. Mills\nRequest for Comments: 975 M/A-COM Linkabit\n February 1986\n\n Autonomous Confederations\n\nStatus of This Memo\n\n This RFC proposes certain enhancements of the Exterior Gateway\n Protocol (EGP) to support a simple, multiple-level routing capability\n while preserving the robustness features of the current EGP model.\n It requests discussion and suggestions for improvements.\n Distribution of this memo is unlimited.\n\nOverview\n\n The enhancements, which do not require retrofits in existing\n implementations in order to interoperate with enhanced\n implementations, in effect generalize the concept of core system to\n include multiple communities of autonomous systems, called autonomous\n confederations. Autonomous confederations maintain a higher degree of\n mutual trust than that assumed between autonomous systems in general,\n including reasonable protection against rout 975 algorithm algorithms path trust nested-reference unchanged"},{"id":"IETF RFC 976","type":"specification","body":"IETF","designation":"RFC 976","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc976.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc976.txt","https://www.rfc-editor.org/rfc/rfc976.pdf"],"folder":"IETF/RFC-976","files":{"txt":{"path":"standards/IETF/RFC-976/RFC-976.txt","sha256":"015def59a15f770ed3b59007d0a699d92cc40ea0aa170443126c355d0f0da65a"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Mark. R. Horton\nRequest for Comments: 976 Bell Laboratories\n February 1986\n\n UUCP Mail Interchange Format Standard\n\nStatus of This Memo\n\n In response to the need for maintenance of current information about\n the status and progress of various projects in the ARPA-Internet\n community, this RFC is issued for the benefit of community members.\n The information contained in this document is accurate as of the date\n of publication, but is subject to change. Subsequent RFCs will\n reflect such changes.\n\n This document defines the standard format for the transmission of\n mail messages between machines in the UUCP Project. It does not\n address the format for storage of messages on one machine, nor the\n lower level transport mechanisms used to get the data from one\n machine to the next. It represents a standard for conformance by\n hosts in the UUCP zone. Distribution of this m","scope_keywords":["976","path","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1137","folder":"IETF/RFC-1137","source":"IETF/RFC-1137/RFC-1137.txt","version":null},{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1912","folder":"IETF/RFC-1912","source":"IETF/RFC-1912/RFC-1912.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2142","folder":"IETF/RFC-2142","source":"IETF/RFC-2142/RFC-2142.txt","version":null},{"body":"IETF","designation":"RFC 987","folder":"IETF/RFC-987","source":"IETF/RFC-987/RFC-987.txt","version":null}],"search_text":"IETF RFC 976 Network Working Group Mark. R. Horton\nRequest for Comments: 976 Bell Laboratories\n February 1986\n\n UUCP Mail Interchange Format Standard\n\nStatus of This Memo\n\n In response to the need for maintenance of current information about\n the status and progress of various projects in the ARPA-Internet\n community, this RFC is issued for the benefit of community members.\n The information contained in this document is accurate as of the date\n of publication, but is subject to change. Subsequent RFCs will\n reflect such changes.\n\n This document defines the standard format for the transmission of\n mail messages between machines in the UUCP Project. It does not\n address the format for storage of messages on one machine, nor the\n lower level transport mechanisms used to get the data from one\n machine to the next. It represents a standard for conformance by\n hosts in the UUCP zone. Distribution of this m 976 path subject nested-reference unchanged"},{"id":"IETF RFC 979","type":"specification","body":"IETF","designation":"RFC 979","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc979.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc979.txt","https://www.rfc-editor.org/rfc/rfc979.pdf"],"folder":"IETF/RFC-979","files":{"txt":{"path":"standards/IETF/RFC-979/RFC-979.txt","sha256":"19b461a29406f0280378120a8a0e6177007a41ff3ee2f147cba88b9a01a7cf61"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Andrew G. Malis\nRequest for Comments: 979 BBN Communications Corp.\n March 1986\n\n PSN END-TO-END FUNCTIONAL SPECIFICATION\n\nStatus of this Memo\n\n This memo is an updated version of BBN Report 5775, \"End-to-End\n Functional Specification\". It has been updated to reflect changes\n since that report was written, and is being distributed in this form\n to provide information to the ARPA-Internet community about this\n work. The changes described in this memo will affect AHIP (1822\n LH/DH/HDH) and X.25 hosts directly connected to BBNCC PSNs.\n Information concerning the schedule for deployment of this version of\n the PSN software (Release 7.0) in the ARPANET and the MILNET can be\n obtained from DCA. Distribution of this memo is unlimited.\n\n1 Introduction\n\n This memo contains the functional specification for the new BBNCC PSN\n End-to-End (EE) protocol and module (PSN stands for ","scope_keywords":["979","driving","management","pid","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 991","folder":"IETF/RFC-991","source":"IETF/RFC-991/RFC-991.txt","version":null}],"search_text":"IETF RFC 979 Network Working Group Andrew G. Malis\nRequest for Comments: 979 BBN Communications Corp.\n March 1986\n\n PSN END-TO-END FUNCTIONAL SPECIFICATION\n\nStatus of this Memo\n\n This memo is an updated version of BBN Report 5775, \"End-to-End\n Functional Specification\". It has been updated to reflect changes\n since that report was written, and is being distributed in this form\n to provide information to the ARPA-Internet community about this\n work. The changes described in this memo will affect AHIP (1822\n LH/DH/HDH) and X.25 hosts directly connected to BBNCC PSNs.\n Information concerning the schedule for deployment of this version of\n the PSN software (Release 7.0) in the ARPANET and the MILNET can be\n obtained from DCA. Distribution of this memo is unlimited.\n\n1 Introduction\n\n This memo contains the functional specification for the new BBNCC PSN\n End-to-End (EE) protocol and module (PSN stands for  979 driving management pid subject nested-reference unchanged"},{"id":"IETF RFC 982","type":"specification","body":"IETF","designation":"RFC 982","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc982.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc982.txt","https://www.rfc-editor.org/rfc/rfc982.pdf"],"folder":"IETF/RFC-982","files":{"txt":{"path":"standards/IETF/RFC-982/RFC-982.txt","sha256":"356029cd1e8a8f6fd6b26b86946398b63208077003fbaadbd83ca234dc938563"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ANSI\nRequest for Comments: 982 April 1986\n\n Guidelines for the Specification of the Structure of the\n Domain Specific Part (DSP) of the ISO Standard NSAP Address\n \n\n ANSI Working Document X3S3.3/85-258\n\nStatus of This Memo\n\n The following is a RFC edition of the ANSI \"Guidelines for the\n Specification of the Structure of the Domain Specific Part (DSP) of\n the ISO Standard NSAP Address\". It should be understood that this\n ANSI working document is in a draft state and subject to change.\n\n These Guidelines are an important prerequirement to allow IP\n addressing within the ISO connectionless protocol (CLNS), which\n itself is necessary to allow the coexistance of the IP and the CLNS\n in the Arpanet attached gateways.\n\n A RFC to specify a suitable IP addressing method for ISOgrams is\n currently worked on in Internet Task Forces and should be expected as\n an RFC shortly.\n\n","scope_keywords":["982","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null}],"search_text":"IETF RFC 982 Network Working Group ANSI\nRequest for Comments: 982 April 1986\n\n Guidelines for the Specification of the Structure of the\n Domain Specific Part (DSP) of the ISO Standard NSAP Address\n \n\n ANSI Working Document X3S3.3/85-258\n\nStatus of This Memo\n\n The following is a RFC edition of the ANSI \"Guidelines for the\n Specification of the Structure of the Domain Specific Part (DSP) of\n the ISO Standard NSAP Address\". It should be understood that this\n ANSI working document is in a draft state and subject to change.\n\n These Guidelines are an important prerequirement to allow IP\n addressing within the ISO connectionless protocol (CLNS), which\n itself is necessary to allow the coexistance of the IP and the CLNS\n in the Arpanet attached gateways.\n\n A RFC to specify a suitable IP addressing method for ISOgrams is\n currently worked on in Internet Task Forces and should be expected as\n an RFC shortly.\n\n 982 identification subject nested-reference unchanged"},{"id":"IETF RFC 984","type":"specification","body":"IETF","designation":"RFC 984","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc984.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc984.txt","https://www.rfc-editor.org/rfc/rfc984.pdf"],"folder":"IETF/RFC-984","files":{"txt":{"path":"standards/IETF/RFC-984/RFC-984.txt","sha256":"f72ff03b0ffc6873c8e7f020f2f7febde05121b6c65e1e05dfa28eaac14e34bd"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group David D. Clark\nRequest for Comments: 984 Mark L. Lambert\n M. I. T. Laboratory for Computer Science\n May 1986\n\n PCMAIL: A Distributed Mail System for Personal Computers\n\n1. Status of this Document\n\n This document is a preliminary discussion of the design of a\n personal-computer-based distributed mail system. It is published for\n discussion and comment, and does not constitute a standard. As the\n proposal may change, implementation of this document is not advised.\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n Pcmail is a distributed mail system that provides mail service to an\n arbitrary number of users, each of which owns one or more personal\n computers (PCs). The system is divided into two halves. The first\n consists of a single entity called the \"repository\". The repository\n is a storage center for incoming mail. Mail for a Pcmail user can\n arrive ext","scope_keywords":["984","management"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"IETF RFC 984 Network Working Group David D. Clark\nRequest for Comments: 984 Mark L. Lambert\n M. I. T. Laboratory for Computer Science\n May 1986\n\n PCMAIL: A Distributed Mail System for Personal Computers\n\n1. Status of this Document\n\n This document is a preliminary discussion of the design of a\n personal-computer-based distributed mail system. It is published for\n discussion and comment, and does not constitute a standard. As the\n proposal may change, implementation of this document is not advised.\n Distribution of this memo is unlimited.\n\n2. Introduction\n\n Pcmail is a distributed mail system that provides mail service to an\n arbitrary number of users, each of which owns one or more personal\n computers (PCs). The system is divided into two halves. The first\n consists of a single entity called the \"repository\". The repository\n is a storage center for incoming mail. Mail for a Pcmail user can\n arrive ext 984 management nested-reference unchanged"},{"id":"IETF RFC 986","type":"specification","body":"IETF","designation":"RFC 986","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc986.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc986.txt","https://www.rfc-editor.org/rfc/rfc986.pdf"],"folder":"IETF/RFC-986","files":{"txt":{"path":"standards/IETF/RFC-986/RFC-986.txt","sha256":"d49553110d1360716bcdcfab0f8f6c47589d433c278e8ce3d95d9baf27f1ddf9"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group Ross Callon (BBN)\nRequest for Comments: 986 Hans-Werner Braun (UMich)\n June 1986\n\n WORKING DRAFT\n\n Guidelines for the use of Internet-IP addresses in the\n ISO Connectionless-Mode Network Protocol\n\nStatus of This Memo\n\n This RFC suggests a method to allow the existing IP addressing,\n including the IP protocol field, to be used for the ISO\n Connectionless Network Protocol (CLNP). This is a draft solution to\n one of the problems inherent in the use of \"ISO-grams\" in the DOD\n Internet. Related issues will be discussed in subsequent RFCs. This\n RFC suggests a proposed protocol for the ARPA-Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\n1. Introduction\n\n The CLNP is documented in [1], but for matters of completeness the\n following illustration of the CLNP header is included here as\n Figure 1.\n\n The ","scope_keywords":["986","identification","subject"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1069","folder":"IETF/RFC-1069","source":"IETF/RFC-1069/RFC-1069.txt","version":null}],"search_text":"IETF RFC 986 Network Working Group Ross Callon (BBN)\nRequest for Comments: 986 Hans-Werner Braun (UMich)\n June 1986\n\n WORKING DRAFT\n\n Guidelines for the use of Internet-IP addresses in the\n ISO Connectionless-Mode Network Protocol\n\nStatus of This Memo\n\n This RFC suggests a method to allow the existing IP addressing,\n including the IP protocol field, to be used for the ISO\n Connectionless Network Protocol (CLNP). This is a draft solution to\n one of the problems inherent in the use of \"ISO-grams\" in the DOD\n Internet. Related issues will be discussed in subsequent RFCs. This\n RFC suggests a proposed protocol for the ARPA-Internet community, and\n requests discussion and suggestions for improvements. Distribution\n of this memo is unlimited.\n\n1. Introduction\n\n The CLNP is documented in [1], but for matters of completeness the\n following illustration of the CLNP header is included here as\n Figure 1.\n\n The  986 identification subject nested-reference unchanged"},{"id":"IETF RFC 994","type":"specification","body":"IETF","designation":"RFC 994","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc994.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc994.txt","https://www.rfc-editor.org/rfc/rfc994.pdf"],"folder":"IETF/RFC-994","files":{"txt":{"path":"standards/IETF/RFC-994/RFC-994.txt","sha256":"82c8a0154ab38875a1d65af1910b6a3524d5fe614de19e6ed4fab8c41c5b3077"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ANSI X3S3.3 86-80\nRequest for Comments: 994 ISO TC97/SC6/N 3998\n March 1986\n\n I S O\n INTERNATIONAL ORGANIZATION FOR STANDARDIZATION\n ORGANISATION INTERNATIONALE DE NORMALISATION\n\n ____________________________________________________________________\n | |\n | ISO/TC 97/SC 6 |\n | TELECOMMUNICATIONS AND INFORMATION |\n | EXCHANGE BETWEEN SYSTEMS |\n | Secretariat: USA (ANSI) |\n | |\n | |\n |___________________________________________________________________|\n\nTitle: Final Text of DIS 8473, Protocol for Providing the Connectionless-\n mode Network Service\n\nSource: DIS 8473 Editor\n\nISO 8473 [Page 1]\n\f\nRFC 994 December 1986\n\nContents\n\n1 Scope and Field of Application 6\n\n2 References 7\n\nSECTION ONE. GENERAL 9\n\n3 Definitions 9\n 3.1 Reference Model Definitions . . . . . . . . . . . . . . . . . 9\n 3.2 Service Conventions Definitions . . . . . . . . . . . . . . . 9\n 3.3 Network Layer","scope_keywords":["994"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1131","folder":"IETF/RFC-1131","source":"IETF/RFC-1131/RFC-1131.pdf","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1247","folder":"IETF/RFC-1247","source":"IETF/RFC-1247/RFC-1247.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null}],"search_text":"IETF RFC 994 Network Working Group ANSI X3S3.3 86-80\nRequest for Comments: 994 ISO TC97/SC6/N 3998\n March 1986\n\n I S O\n INTERNATIONAL ORGANIZATION FOR STANDARDIZATION\n ORGANISATION INTERNATIONALE DE NORMALISATION\n\n ____________________________________________________________________\n | |\n | ISO/TC 97/SC 6 |\n | TELECOMMUNICATIONS AND INFORMATION |\n | EXCHANGE BETWEEN SYSTEMS |\n | Secretariat: USA (ANSI) |\n | |\n | |\n |___________________________________________________________________|\n\nTitle: Final Text of DIS 8473, Protocol for Providing the Connectionless-\n mode Network Service\n\nSource: DIS 8473 Editor\n\nISO 8473 [Page 1]\n\f\nRFC 994 December 1986\n\nContents\n\n1 Scope and Field of Application 6\n\n2 References 7\n\nSECTION ONE. GENERAL 9\n\n3 Definitions 9\n 3.1 Reference Model Definitions . . . . . . . . . . . . . . . . . 9\n 3.2 Service Conventions Definitions . . . . . . . . . . . . . . . 9\n 3.3 Network Layer 994 nested-reference unchanged"},{"id":"IETF RFC 995","type":"specification","body":"IETF","designation":"RFC 995","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc995.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc995.txt","https://www.rfc-editor.org/rfc/rfc995.pdf"],"folder":"IETF/RFC-995","files":{"txt":{"path":"standards/IETF/RFC-995/RFC-995.txt","sha256":"8cbe87a5539f12f123d16fd13e53d487b7c01a62f11820c6b14a814698e92644"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group ANSI X3S3.3 86-118\nRequest for Comments: 995 ISO TC97/SC6/N 4053\n April 1986\n\n I S O\n INTERNATIONAL ORGANIZATION FOR STANDARDIZATION\n ORGANISATION INTERNATIONALE DE NORMALISATION\n\n ____________________________________________________________________\n | |\n | ISO/TC 97/SC 6 |\n | TELECOMMUNICATIONS AND INFORMATION |\n | EXCHANGE BETWEEN SYSTEMS |\n | Secretariat: USA (ANSI) |\n | |\n | |\n |_________________________________________________________________|\n\n Title: End System to Intermediate System Routing Exchange Protocol\n for use in conjunction with ISO 8473\n\n Source: SC6/WG2\n Project 97.6.41\n\n _______________________________________________________________________\n |This document is a progression of SC6/N3862, edited to incorporate member |\n |body comments and discussion at the Florence meeting of SC6/WG2. Pursuant |\n |to Recommendation 5 of that meeting, comments from ","scope_keywords":["995"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null}],"search_text":"IETF RFC 995 Network Working Group ANSI X3S3.3 86-118\nRequest for Comments: 995 ISO TC97/SC6/N 4053\n April 1986\n\n I S O\n INTERNATIONAL ORGANIZATION FOR STANDARDIZATION\n ORGANISATION INTERNATIONALE DE NORMALISATION\n\n ____________________________________________________________________\n | |\n | ISO/TC 97/SC 6 |\n | TELECOMMUNICATIONS AND INFORMATION |\n | EXCHANGE BETWEEN SYSTEMS |\n | Secretariat: USA (ANSI) |\n | |\n | |\n |_________________________________________________________________|\n\n Title: End System to Intermediate System Routing Exchange Protocol\n for use in conjunction with ISO 8473\n\n Source: SC6/WG2\n Project 97.6.41\n\n _______________________________________________________________________\n |This document is a progression of SC6/N3862, edited to incorporate member |\n |body comments and discussion at the Florence meeting of SC6/WG2. Pursuant |\n |to Recommendation 5 of that meeting, comments from  995 nested-reference unchanged"},{"id":"IETF RFC 996","type":"specification","body":"IETF","designation":"RFC 996","version":null,"title":null,"purpose":null,"status":"unchanged","download_url":"https://www.rfc-editor.org/rfc/rfc996.txt","download_urls":["https://www.rfc-editor.org/rfc/rfc996.txt","https://www.rfc-editor.org/rfc/rfc996.pdf"],"folder":"IETF/RFC-996","files":{"txt":{"path":"standards/IETF/RFC-996/RFC-996.txt","sha256":"5e30c41e730d3798c2efe7d1575ca32bda383629aa5c4d02f7759de60c687291"}},"tags":["nested-reference","unchanged"],"summary":"Network Working Group D.L. Mills\nRequest for Comments: 996 University of Delaware\n February 1987\n\n Statistics Server\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n and gateways on the DARPA Internet that choose to implement a remote\n statistics monitoring facility may use this protocol to send\n statistics data upon request to a monitoring center or debugging\n host. Distribution of this memo is unlimited.\n\nDISCUSSION\n\n Many host and gateway implementations include a facility which\n records traffic statistics, such as packet counters, error counters\n and significant event counters for debugging and performance\n evluation. Simple data-access and formatting programs can be used to\n display these statistics along with the status of connections, etc.\n Several operating systems, including the various Unix systems and\n Fuzzball systems, already provi","scope_keywords":["996","authentication"],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 2896","folder":"IETF/RFC-2896","source":"IETF/RFC-2896/RFC-2896.txt","version":null}],"search_text":"IETF RFC 996 Network Working Group D.L. Mills\nRequest for Comments: 996 University of Delaware\n February 1987\n\n Statistics Server\n\nSTATUS OF THIS MEMO\n\n This RFC specifies a standard for the ARPA Internet community. Hosts\n and gateways on the DARPA Internet that choose to implement a remote\n statistics monitoring facility may use this protocol to send\n statistics data upon request to a monitoring center or debugging\n host. Distribution of this memo is unlimited.\n\nDISCUSSION\n\n Many host and gateway implementations include a facility which\n records traffic statistics, such as packet counters, error counters\n and significant event counters for debugging and performance\n evluation. Simple data-access and formatting programs can be used to\n display these statistics along with the status of connections, etc.\n Several operating systems, including the various Unix systems and\n Fuzzball systems, already provi 996 authentication nested-reference unchanged"},{"id":"ISO-IEC ISO 1000 V1992","type":"specification","body":"ISO-IEC","designation":"ISO 1000","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+1000","download_urls":["https://www.iso.org/search.html?q=ISO+1000"],"folder":"ISO-IEC/ISO-1000-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2534","folder":"IETF/RFC-2534","source":"IETF/RFC-2534/RFC-2534.txt","version":null}],"search_text":"ISO-IEC ISO 1000 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021","type":"specification","body":"ISO-IEC","designation":"ISO 10021","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021","download_urls":["https://www.iso.org/search.html?q=ISO+10021"],"folder":"ISO-IEC/ISO-10021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1160","folder":"IETF/RFC-1160","source":"IETF/RFC-1160/RFC-1160.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1328","folder":"IETF/RFC-1328","source":"IETF/RFC-1328/RFC-1328.txt","version":null},{"body":"IETF","designation":"RFC 1360","folder":"IETF/RFC-1360","source":"IETF/RFC-1360/RFC-1360.txt","version":null},{"body":"IETF","designation":"RFC 1405","folder":"IETF/RFC-1405","source":"IETF/RFC-1405/RFC-1405.txt","version":null},{"body":"IETF","designation":"RFC 1488","folder":"IETF/RFC-1488","source":"IETF/RFC-1488/RFC-1488.txt","version":null},{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1495","folder":"IETF/RFC-1495","source":"IETF/RFC-1495/RFC-1495.txt","version":null},{"body":"IETF","designation":"RFC 1496","folder":"IETF/RFC-1496","source":"IETF/RFC-1496/RFC-1496.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1530","folder":"IETF/RFC-1530","source":"IETF/RFC-1530/RFC-1530.txt","version":null},{"body":"IETF","designation":"RFC 1565","folder":"IETF/RFC-1565","source":"IETF/RFC-1565/RFC-1565.txt","version":null},{"body":"IETF","designation":"RFC 1648","folder":"IETF/RFC-1648","source":"IETF/RFC-1648/RFC-1648.txt","version":null},{"body":"IETF","designation":"RFC 1649","folder":"IETF/RFC-1649","source":"IETF/RFC-1649/RFC-1649.txt","version":null},{"body":"IETF","designation":"RFC 1664","folder":"IETF/RFC-1664","source":"IETF/RFC-1664/RFC-1664.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1766","folder":"IETF/RFC-1766","source":"IETF/RFC-1766/RFC-1766.txt","version":null},{"body":"IETF","designation":"RFC 1801","folder":"IETF/RFC-1801","source":"IETF/RFC-1801/RFC-1801.txt","version":null},{"body":"IETF","designation":"RFC 1836","folder":"IETF/RFC-1836","source":"IETF/RFC-1836/RFC-1836.txt","version":null},{"body":"IETF","designation":"RFC 1838","folder":"IETF/RFC-1838","source":"IETF/RFC-1838/RFC-1838.txt","version":null},{"body":"IETF","designation":"RFC 1911","folder":"IETF/RFC-1911","source":"IETF/RFC-1911/RFC-1911.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2076","folder":"IETF/RFC-2076","source":"IETF/RFC-2076/RFC-2076.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2163","folder":"IETF/RFC-2163","source":"IETF/RFC-2163/RFC-2163.txt","version":null},{"body":"IETF","designation":"RFC 2248","folder":"IETF/RFC-2248","source":"IETF/RFC-2248/RFC-2248.txt","version":null},{"body":"IETF","designation":"RFC 2249","folder":"IETF/RFC-2249","source":"IETF/RFC-2249/RFC-2249.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2294","folder":"IETF/RFC-2294","source":"IETF/RFC-2294/RFC-2294.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 4021","folder":"IETF/RFC-4021","source":"IETF/RFC-4021/RFC-4021.txt","version":null}],"search_text":"ISO-IEC ISO 10021 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021-2","type":"specification","body":"ISO-IEC","designation":"ISO 10021-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021-2","download_urls":["https://www.iso.org/search.html?q=ISO+10021-2"],"folder":"ISO-IEC/ISO-10021-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"ISO-IEC ISO 10021-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021-4","type":"specification","body":"ISO-IEC","designation":"ISO 10021-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021-4","download_urls":["https://www.iso.org/search.html?q=ISO+10021-4"],"folder":"ISO-IEC/ISO-10021-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"ISO-IEC ISO 10021-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021-6","type":"specification","body":"ISO-IEC","designation":"ISO 10021-6","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021-6","download_urls":["https://www.iso.org/search.html?q=ISO+10021-6"],"folder":"ISO-IEC/ISO-10021-6","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1465","folder":"IETF/RFC-1465","source":"IETF/RFC-1465/RFC-1465.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 10021-6 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021-7","type":"specification","body":"ISO-IEC","designation":"ISO 10021-7","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021-7","download_urls":["https://www.iso.org/search.html?q=ISO+10021-7"],"folder":"ISO-IEC/ISO-10021-7","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 10021-7 nested-reference unavailable"},{"id":"ISO-IEC ISO 10021-8","type":"specification","body":"ISO-IEC","designation":"ISO 10021-8","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10021-8","download_urls":["https://www.iso.org/search.html?q=ISO+10021-8"],"folder":"ISO-IEC/ISO-10021-8","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null}],"search_text":"ISO-IEC ISO 10021-8 nested-reference unavailable"},{"id":"ISO-IEC ISO 10035","type":"specification","body":"ISO-IEC","designation":"ISO 10035","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10035","download_urls":["https://www.iso.org/search.html?q=ISO+10035"],"folder":"ISO-IEC/ISO-10035","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null}],"search_text":"ISO-IEC ISO 10035 nested-reference unavailable"},{"id":"ISO-IEC ISO 10036","type":"specification","body":"ISO-IEC","designation":"ISO 10036","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10036","download_urls":["https://www.iso.org/search.html?q=ISO+10036"],"folder":"ISO-IEC/ISO-10036","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"ISO-IEC ISO 10036 nested-reference unavailable"},{"id":"ISO-IEC ISO 10039","type":"specification","body":"ISO-IEC","designation":"ISO 10039","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10039","download_urls":["https://www.iso.org/search.html?q=ISO+10039"],"folder":"ISO-IEC/ISO-10039","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null}],"search_text":"ISO-IEC ISO 10039 nested-reference unavailable"},{"id":"ISO-IEC ISO 100646-1","type":"specification","body":"ISO-IEC","designation":"ISO 100646-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+100646-1","download_urls":["https://www.iso.org/search.html?q=ISO+100646-1"],"folder":"ISO-IEC/ISO-100646-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null}],"search_text":"ISO-IEC ISO 100646-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 10118-1","type":"specification","body":"ISO-IEC","designation":"ISO 10118-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10118-1","download_urls":["https://www.iso.org/search.html?q=ISO+10118-1"],"folder":"ISO-IEC/ISO-10118-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 10118-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 10118-2","type":"specification","body":"ISO-IEC","designation":"ISO 10118-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10118-2","download_urls":["https://www.iso.org/search.html?q=ISO+10118-2"],"folder":"ISO-IEC/ISO-10118-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 10118-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 10118-3","type":"specification","body":"ISO-IEC","designation":"ISO 10118-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10118-3","download_urls":["https://www.iso.org/search.html?q=ISO+10118-3"],"folder":"ISO-IEC/ISO-10118-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 10118-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 10118-4","type":"specification","body":"ISO-IEC","designation":"ISO 10118-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10118-4","download_urls":["https://www.iso.org/search.html?q=ISO+10118-4"],"folder":"ISO-IEC/ISO-10118-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 10118-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 10160","type":"specification","body":"ISO-IEC","designation":"ISO 10160","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10160","download_urls":["https://www.iso.org/search.html?q=ISO+10160"],"folder":"ISO-IEC/ISO-10160","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"ISO-IEC ISO 10160 nested-reference unavailable"},{"id":"ISO-IEC ISO 10165-4","type":"specification","body":"ISO-IEC","designation":"ISO 10165-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10165-4","download_urls":["https://www.iso.org/search.html?q=ISO+10165-4"],"folder":"ISO-IEC/ISO-10165-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null}],"search_text":"ISO-IEC ISO 10165-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 10175","type":"specification","body":"ISO-IEC","designation":"ISO 10175","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10175","download_urls":["https://www.iso.org/search.html?q=ISO+10175"],"folder":"ISO-IEC/ISO-10175","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"ISO-IEC ISO 10175 nested-reference unavailable"},{"id":"ISO-IEC ISO 10180","type":"specification","body":"ISO-IEC","designation":"ISO 10180","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10180","download_urls":["https://www.iso.org/search.html?q=ISO+10180"],"folder":"ISO-IEC/ISO-10180","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"ISO-IEC ISO 10180 nested-reference unavailable"},{"id":"ISO-IEC ISO 10181-5","type":"specification","body":"ISO-IEC","designation":"ISO 10181-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10181-5","download_urls":["https://www.iso.org/search.html?q=ISO+10181-5"],"folder":"ISO-IEC/ISO-10181-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO 10181-5 nested-reference unavailable"},{"id":"ISO-IEC ISO 105","type":"specification","body":"ISO-IEC","designation":"ISO 105","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+105","download_urls":["https://www.iso.org/search.html?q=ISO+105"],"folder":"ISO-IEC/ISO-105","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 105 nested-reference unavailable"},{"id":"ISO-IEC ISO 10589 V2002","type":"specification","body":"ISO-IEC","designation":"ISO 10589","version":"2002","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10589","download_urls":["https://www.iso.org/search.html?q=ISO+10589"],"folder":"ISO-IEC/ISO-10589-V2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2966","folder":"IETF/RFC-2966","source":"IETF/RFC-2966/RFC-2966.txt","version":null},{"body":"IETF","designation":"RFC 3359","folder":"IETF/RFC-3359","source":"IETF/RFC-3359/RFC-3359.txt","version":null},{"body":"IETF","designation":"RFC 3373","folder":"IETF/RFC-3373","source":"IETF/RFC-3373/RFC-3373.txt","version":null},{"body":"IETF","designation":"RFC 3439","folder":"IETF/RFC-3439","source":"IETF/RFC-3439/RFC-3439.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5120","folder":"IETF/RFC-5120","source":"IETF/RFC-5120/RFC-5120.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null}],"search_text":"ISO-IEC ISO 10589 2002 nested-reference unavailable"},{"id":"ISO-IEC ISO 10646-1 V1993","type":"specification","body":"ISO-IEC","designation":"ISO 10646-1","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10646-1","download_urls":["https://www.iso.org/search.html?q=ISO+10646-1"],"folder":"ISO-IEC/ISO-10646-1-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null}],"search_text":"ISO-IEC ISO 10646-1 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO 10646-2","type":"specification","body":"ISO-IEC","designation":"ISO 10646-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10646-2","download_urls":["https://www.iso.org/search.html?q=ISO+10646-2"],"folder":"ISO-IEC/ISO-10646-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"ISO-IEC ISO 10646-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 10646 V1993","type":"specification","body":"ISO-IEC","designation":"ISO 10646","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10646","download_urls":["https://www.iso.org/search.html?q=ISO+10646"],"folder":"ISO-IEC/ISO-10646-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1342","folder":"IETF/RFC-1342","source":"IETF/RFC-1342/RFC-1342.txt","version":null},{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1489","folder":"IETF/RFC-1489","source":"IETF/RFC-1489/RFC-1489.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1522","folder":"IETF/RFC-1522","source":"IETF/RFC-1522/RFC-1522.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1942","folder":"IETF/RFC-1942","source":"IETF/RFC-1942/RFC-1942.txt","version":null},{"body":"IETF","designation":"RFC 2000","folder":"IETF/RFC-2000","source":"IETF/RFC-2000/RFC-2000.txt","version":null},{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2047","folder":"IETF/RFC-2047","source":"IETF/RFC-2047/RFC-2047.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2192","folder":"IETF/RFC-2192","source":"IETF/RFC-2192/RFC-2192.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2261","folder":"IETF/RFC-2261","source":"IETF/RFC-2261/RFC-2261.txt","version":null},{"body":"IETF","designation":"RFC 2271","folder":"IETF/RFC-2271","source":"IETF/RFC-2271/RFC-2271.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2284","folder":"IETF/RFC-2284","source":"IETF/RFC-2284/RFC-2284.txt","version":null},{"body":"IETF","designation":"RFC 2287","folder":"IETF/RFC-2287","source":"IETF/RFC-2287/RFC-2287.txt","version":null},{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2295","folder":"IETF/RFC-2295","source":"IETF/RFC-2295/RFC-2295.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2384","folder":"IETF/RFC-2384","source":"IETF/RFC-2384/RFC-2384.txt","version":null},{"body":"IETF","designation":"RFC 2396","folder":"IETF/RFC-2396","source":"IETF/RFC-2396/RFC-2396.txt","version":null},{"body":"IETF","designation":"RFC 2400","folder":"IETF/RFC-2400","source":"IETF/RFC-2400/RFC-2400.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2444","folder":"IETF/RFC-2444","source":"IETF/RFC-2444/RFC-2444.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2484","folder":"IETF/RFC-2484","source":"IETF/RFC-2484/RFC-2484.txt","version":null},{"body":"IETF","designation":"RFC 2516","folder":"IETF/RFC-2516","source":"IETF/RFC-2516/RFC-2516.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2571","folder":"IETF/RFC-2571","source":"IETF/RFC-2571/RFC-2571.txt","version":null},{"body":"IETF","designation":"RFC 2595","folder":"IETF/RFC-2595","source":"IETF/RFC-2595/RFC-2595.txt","version":null},{"body":"IETF","designation":"RFC 2596","folder":"IETF/RFC-2596","source":"IETF/RFC-2596/RFC-2596.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2609","folder":"IETF/RFC-2609","source":"IETF/RFC-2609/RFC-2609.txt","version":null},{"body":"IETF","designation":"RFC 2610","folder":"IETF/RFC-2610","source":"IETF/RFC-2610/RFC-2610.txt","version":null},{"body":"IETF","designation":"RFC 2614","folder":"IETF/RFC-2614","source":"IETF/RFC-2614/RFC-2614.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2634","folder":"IETF/RFC-2634","source":"IETF/RFC-2634/RFC-2634.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2662","folder":"IETF/RFC-2662","source":"IETF/RFC-2662/RFC-2662.txt","version":null},{"body":"IETF","designation":"RFC 2683","folder":"IETF/RFC-2683","source":"IETF/RFC-2683/RFC-2683.txt","version":null},{"body":"IETF","designation":"RFC 2718","folder":"IETF/RFC-2718","source":"IETF/RFC-2718/RFC-2718.txt","version":null},{"body":"IETF","designation":"RFC 2720","folder":"IETF/RFC-2720","source":"IETF/RFC-2720/RFC-2720.txt","version":null},{"body":"IETF","designation":"RFC 2730","folder":"IETF/RFC-2730","source":"IETF/RFC-2730/RFC-2730.txt","version":null},{"body":"IETF","designation":"RFC 2776","folder":"IETF/RFC-2776","source":"IETF/RFC-2776/RFC-2776.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2803","folder":"IETF/RFC-2803","source":"IETF/RFC-2803/RFC-2803.txt","version":null},{"body":"IETF","designation":"RFC 2829","folder":"IETF/RFC-2829","source":"IETF/RFC-2829/RFC-2829.txt","version":null},{"body":"IETF","designation":"RFC 2847","folder":"IETF/RFC-2847","source":"IETF/RFC-2847/RFC-2847.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2866","folder":"IETF/RFC-2866","source":"IETF/RFC-2866/RFC-2866.txt","version":null},{"body":"IETF","designation":"RFC 2869","folder":"IETF/RFC-2869","source":"IETF/RFC-2869/RFC-2869.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2957","folder":"IETF/RFC-2957","source":"IETF/RFC-2957/RFC-2957.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3028","folder":"IETF/RFC-3028","source":"IETF/RFC-3028/RFC-3028.txt","version":null},{"body":"IETF","designation":"RFC 3060","folder":"IETF/RFC-3060","source":"IETF/RFC-3060/RFC-3060.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3076","folder":"IETF/RFC-3076","source":"IETF/RFC-3076/RFC-3076.txt","version":null},{"body":"IETF","designation":"RFC 3080","folder":"IETF/RFC-3080","source":"IETF/RFC-3080/RFC-3080.txt","version":null},{"body":"IETF","designation":"RFC 3111","folder":"IETF/RFC-3111","source":"IETF/RFC-3111/RFC-3111.txt","version":null},{"body":"IETF","designation":"RFC 3162","folder":"IETF/RFC-3162","source":"IETF/RFC-3162/RFC-3162.txt","version":null},{"body":"IETF","designation":"RFC 3252","folder":"IETF/RFC-3252","source":"IETF/RFC-3252/RFC-3252.txt","version":null},{"body":"IETF","designation":"RFC 3253","folder":"IETF/RFC-3253","source":"IETF/RFC-3253/RFC-3253.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3318","folder":"IETF/RFC-3318","source":"IETF/RFC-3318/RFC-3318.txt","version":null},{"body":"IETF","designation":"RFC 3320","folder":"IETF/RFC-3320","source":"IETF/RFC-3320/RFC-3320.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3403","folder":"IETF/RFC-3403","source":"IETF/RFC-3403/RFC-3403.txt","version":null},{"body":"IETF","designation":"RFC 3411","folder":"IETF/RFC-3411","source":"IETF/RFC-3411/RFC-3411.txt","version":null},{"body":"IETF","designation":"RFC 3435","folder":"IETF/RFC-3435","source":"IETF/RFC-3435/RFC-3435.txt","version":null},{"body":"IETF","designation":"RFC 3454","folder":"IETF/RFC-3454","source":"IETF/RFC-3454/RFC-3454.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3470","folder":"IETF/RFC-3470","source":"IETF/RFC-3470/RFC-3470.txt","version":null},{"body":"IETF","designation":"RFC 3485","folder":"IETF/RFC-3485","source":"IETF/RFC-3485/RFC-3485.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3550","folder":"IETF/RFC-3550","source":"IETF/RFC-3550/RFC-3550.txt","version":null},{"body":"IETF","designation":"RFC 3579","folder":"IETF/RFC-3579","source":"IETF/RFC-3579/RFC-3579.txt","version":null},{"body":"IETF","designation":"RFC 3588","folder":"IETF/RFC-3588","source":"IETF/RFC-3588/RFC-3588.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3651","folder":"IETF/RFC-3651","source":"IETF/RFC-3651/RFC-3651.txt","version":null},{"body":"IETF","designation":"RFC 3652","folder":"IETF/RFC-3652","source":"IETF/RFC-3652/RFC-3652.txt","version":null},{"body":"IETF","designation":"RFC 3720","folder":"IETF/RFC-3720","source":"IETF/RFC-3720/RFC-3720.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3730","folder":"IETF/RFC-3730","source":"IETF/RFC-3730/RFC-3730.txt","version":null},{"body":"IETF","designation":"RFC 3731","folder":"IETF/RFC-3731","source":"IETF/RFC-3731/RFC-3731.txt","version":null},{"body":"IETF","designation":"RFC 3732","folder":"IETF/RFC-3732","source":"IETF/RFC-3732/RFC-3732.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3735","folder":"IETF/RFC-3735","source":"IETF/RFC-3735/RFC-3735.txt","version":null},{"body":"IETF","designation":"RFC 3744","folder":"IETF/RFC-3744","source":"IETF/RFC-3744/RFC-3744.txt","version":null},{"body":"IETF","designation":"RFC 3748","folder":"IETF/RFC-3748","source":"IETF/RFC-3748/RFC-3748.txt","version":null},{"body":"IETF","designation":"RFC 3780","folder":"IETF/RFC-3780","source":"IETF/RFC-3780/RFC-3780.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3922","folder":"IETF/RFC-3922","source":"IETF/RFC-3922/RFC-3922.txt","version":null},{"body":"IETF","designation":"RFC 3931","folder":"IETF/RFC-3931","source":"IETF/RFC-3931/RFC-3931.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 3981","folder":"IETF/RFC-3981","source":"IETF/RFC-3981/RFC-3981.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4108","folder":"IETF/RFC-4108","source":"IETF/RFC-4108/RFC-4108.txt","version":null},{"body":"IETF","designation":"RFC 4145","folder":"IETF/RFC-4145","source":"IETF/RFC-4145/RFC-4145.txt","version":null},{"body":"IETF","designation":"RFC 4173","folder":"IETF/RFC-4173","source":"IETF/RFC-4173/RFC-4173.txt","version":null},{"body":"IETF","designation":"RFC 4185","folder":"IETF/RFC-4185","source":"IETF/RFC-4185/RFC-4185.txt","version":null},{"body":"IETF","designation":"RFC 4186","folder":"IETF/RFC-4186","source":"IETF/RFC-4186/RFC-4186.txt","version":null},{"body":"IETF","designation":"RFC 4187","folder":"IETF/RFC-4187","source":"IETF/RFC-4187/RFC-4187.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4251","folder":"IETF/RFC-4251","source":"IETF/RFC-4251/RFC-4251.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4253","folder":"IETF/RFC-4253","source":"IETF/RFC-4253/RFC-4253.txt","version":null},{"body":"IETF","designation":"RFC 4254","folder":"IETF/RFC-4254","source":"IETF/RFC-4254/RFC-4254.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4279","folder":"IETF/RFC-4279","source":"IETF/RFC-4279/RFC-4279.txt","version":null},{"body":"IETF","designation":"RFC 4310","folder":"IETF/RFC-4310","source":"IETF/RFC-4310/RFC-4310.txt","version":null},{"body":"IETF","designation":"RFC 4314","folder":"IETF/RFC-4314","source":"IETF/RFC-4314/RFC-4314.txt","version":null},{"body":"IETF","designation":"RFC 4329","folder":"IETF/RFC-4329","source":"IETF/RFC-4329/RFC-4329.txt","version":null},{"body":"IETF","designation":"RFC 4354","folder":"IETF/RFC-4354","source":"IETF/RFC-4354/RFC-4354.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4422","folder":"IETF/RFC-4422","source":"IETF/RFC-4422/RFC-4422.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4505","folder":"IETF/RFC-4505","source":"IETF/RFC-4505/RFC-4505.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4513","folder":"IETF/RFC-4513","source":"IETF/RFC-4513/RFC-4513.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4516","folder":"IETF/RFC-4516","source":"IETF/RFC-4516/RFC-4516.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4535","folder":"IETF/RFC-4535","source":"IETF/RFC-4535/RFC-4535.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4570","folder":"IETF/RFC-4570","source":"IETF/RFC-4570/RFC-4570.txt","version":null},{"body":"IETF","designation":"RFC 4575","folder":"IETF/RFC-4575","source":"IETF/RFC-4575/RFC-4575.txt","version":null},{"body":"IETF","designation":"RFC 4582","folder":"IETF/RFC-4582","source":"IETF/RFC-4582/RFC-4582.txt","version":null},{"body":"IETF","designation":"RFC 4616","folder":"IETF/RFC-4616","source":"IETF/RFC-4616/RFC-4616.txt","version":null},{"body":"IETF","designation":"RFC 4622","folder":"IETF/RFC-4622","source":"IETF/RFC-4622/RFC-4622.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4675","folder":"IETF/RFC-4675","source":"IETF/RFC-4675/RFC-4675.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4712","folder":"IETF/RFC-4712","source":"IETF/RFC-4712/RFC-4712.txt","version":null},{"body":"IETF","designation":"RFC 4716","folder":"IETF/RFC-4716","source":"IETF/RFC-4716/RFC-4716.txt","version":null},{"body":"IETF","designation":"RFC 4752","folder":"IETF/RFC-4752","source":"IETF/RFC-4752/RFC-4752.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 4790","folder":"IETF/RFC-4790","source":"IETF/RFC-4790/RFC-4790.txt","version":null},{"body":"IETF","designation":"RFC 4793","folder":"IETF/RFC-4793","source":"IETF/RFC-4793/RFC-4793.txt","version":null},{"body":"IETF","designation":"RFC 4807","folder":"IETF/RFC-4807","source":"IETF/RFC-4807/RFC-4807.txt","version":null},{"body":"IETF","designation":"RFC 4825","folder":"IETF/RFC-4825","source":"IETF/RFC-4825/RFC-4825.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 4918","folder":"IETF/RFC-4918","source":"IETF/RFC-4918/RFC-4918.txt","version":null},{"body":"IETF","designation":"RFC 4930","folder":"IETF/RFC-4930","source":"IETF/RFC-4930/RFC-4930.txt","version":null},{"body":"IETF","designation":"RFC 4931","folder":"IETF/RFC-4931","source":"IETF/RFC-4931/RFC-4931.txt","version":null},{"body":"IETF","designation":"RFC 4932","folder":"IETF/RFC-4932","source":"IETF/RFC-4932/RFC-4932.txt","version":null},{"body":"IETF","designation":"RFC 4933","folder":"IETF/RFC-4933","source":"IETF/RFC-4933/RFC-4933.txt","version":null},{"body":"IETF","designation":"RFC 4952","folder":"IETF/RFC-4952","source":"IETF/RFC-4952/RFC-4952.txt","version":null},{"body":"IETF","designation":"RFC 4975","folder":"IETF/RFC-4975","source":"IETF/RFC-4975/RFC-4975.txt","version":null},{"body":"IETF","designation":"RFC 5023","folder":"IETF/RFC-5023","source":"IETF/RFC-5023/RFC-5023.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5035","folder":"IETF/RFC-5035","source":"IETF/RFC-5035/RFC-5035.txt","version":null},{"body":"IETF","designation":"RFC 5051","folder":"IETF/RFC-5051","source":"IETF/RFC-5051/RFC-5051.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 5092","folder":"IETF/RFC-5092","source":"IETF/RFC-5092/RFC-5092.txt","version":null},{"body":"IETF","designation":"RFC 5122","folder":"IETF/RFC-5122","source":"IETF/RFC-5122/RFC-5122.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5147","folder":"IETF/RFC-5147","source":"IETF/RFC-5147/RFC-5147.txt","version":null},{"body":"IETF","designation":"RFC 5149","folder":"IETF/RFC-5149","source":"IETF/RFC-5149/RFC-5149.txt","version":null},{"body":"IETF","designation":"RFC 5173","folder":"IETF/RFC-5173","source":"IETF/RFC-5173/RFC-5173.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5209","folder":"IETF/RFC-5209","source":"IETF/RFC-5209/RFC-5209.txt","version":null},{"body":"IETF","designation":"RFC 5228","folder":"IETF/RFC-5228","source":"IETF/RFC-5228/RFC-5228.txt","version":null},{"body":"IETF","designation":"RFC 5229","folder":"IETF/RFC-5229","source":"IETF/RFC-5229/RFC-5229.txt","version":null},{"body":"IETF","designation":"RFC 5255","folder":"IETF/RFC-5255","source":"IETF/RFC-5255/RFC-5255.txt","version":null},{"body":"IETF","designation":"RFC 5256","folder":"IETF/RFC-5256","source":"IETF/RFC-5256/RFC-5256.txt","version":null},{"body":"IETF","designation":"RFC 5257","folder":"IETF/RFC-5257","source":"IETF/RFC-5257/RFC-5257.txt","version":null},{"body":"IETF","designation":"RFC 5261","folder":"IETF/RFC-5261","source":"IETF/RFC-5261/RFC-5261.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5335","folder":"IETF/RFC-5335","source":"IETF/RFC-5335/RFC-5335.txt","version":null},{"body":"IETF","designation":"RFC 5336","folder":"IETF/RFC-5336","source":"IETF/RFC-5336/RFC-5336.txt","version":null},{"body":"IETF","designation":"RFC 5337","folder":"IETF/RFC-5337","source":"IETF/RFC-5337/RFC-5337.txt","version":null},{"body":"IETF","designation":"RFC 5357","folder":"IETF/RFC-5357","source":"IETF/RFC-5357/RFC-5357.txt","version":null},{"body":"IETF","designation":"RFC 5388","folder":"IETF/RFC-5388","source":"IETF/RFC-5388/RFC-5388.txt","version":null},{"body":"IETF","designation":"RFC 5389","folder":"IETF/RFC-5389","source":"IETF/RFC-5389/RFC-5389.txt","version":null},{"body":"IETF","designation":"RFC 5415","folder":"IETF/RFC-5415","source":"IETF/RFC-5415/RFC-5415.txt","version":null},{"body":"IETF","designation":"RFC 5421","folder":"IETF/RFC-5421","source":"IETF/RFC-5421/RFC-5421.txt","version":null},{"body":"IETF","designation":"RFC 5422","folder":"IETF/RFC-5422","source":"IETF/RFC-5422/RFC-5422.txt","version":null},{"body":"IETF","designation":"RFC 5424","folder":"IETF/RFC-5424","source":"IETF/RFC-5424/RFC-5424.txt","version":null},{"body":"IETF","designation":"RFC 5429","folder":"IETF/RFC-5429","source":"IETF/RFC-5429/RFC-5429.txt","version":null},{"body":"IETF","designation":"RFC 5437","folder":"IETF/RFC-5437","source":"IETF/RFC-5437/RFC-5437.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5466","folder":"IETF/RFC-5466","source":"IETF/RFC-5466/RFC-5466.txt","version":null},{"body":"IETF","designation":"RFC 5504","folder":"IETF/RFC-5504","source":"IETF/RFC-5504/RFC-5504.txt","version":null},{"body":"IETF","designation":"RFC 5537","folder":"IETF/RFC-5537","source":"IETF/RFC-5537/RFC-5537.txt","version":null},{"body":"IETF","designation":"RFC 5545","folder":"IETF/RFC-5545","source":"IETF/RFC-5545/RFC-5545.txt","version":null},{"body":"IETF","designation":"RFC 5547","folder":"IETF/RFC-5547","source":"IETF/RFC-5547/RFC-5547.txt","version":null},{"body":"IETF","designation":"RFC 5607","folder":"IETF/RFC-5607","source":"IETF/RFC-5607/RFC-5607.txt","version":null},{"body":"IETF","designation":"RFC 5610","folder":"IETF/RFC-5610","source":"IETF/RFC-5610/RFC-5610.txt","version":null},{"body":"IETF","designation":"RFC 5626","folder":"IETF/RFC-5626","source":"IETF/RFC-5626/RFC-5626.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 5661","folder":"IETF/RFC-5661","source":"IETF/RFC-5661/RFC-5661.txt","version":null},{"body":"IETF","designation":"RFC 5675","folder":"IETF/RFC-5675","source":"IETF/RFC-5675/RFC-5675.txt","version":null},{"body":"IETF","designation":"RFC 5676","folder":"IETF/RFC-5676","source":"IETF/RFC-5676/RFC-5676.txt","version":null},{"body":"IETF","designation":"RFC 5698","folder":"IETF/RFC-5698","source":"IETF/RFC-5698/RFC-5698.txt","version":null},{"body":"IETF","designation":"RFC 5703","folder":"IETF/RFC-5703","source":"IETF/RFC-5703/RFC-5703.txt","version":null},{"body":"IETF","designation":"RFC 5721","folder":"IETF/RFC-5721","source":"IETF/RFC-5721/RFC-5721.txt","version":null},{"body":"IETF","designation":"RFC 5730","folder":"IETF/RFC-5730","source":"IETF/RFC-5730/RFC-5730.txt","version":null},{"body":"IETF","designation":"RFC 5731","folder":"IETF/RFC-5731","source":"IETF/RFC-5731/RFC-5731.txt","version":null},{"body":"IETF","designation":"RFC 5732","folder":"IETF/RFC-5732","source":"IETF/RFC-5732/RFC-5732.txt","version":null},{"body":"IETF","designation":"RFC 5733","folder":"IETF/RFC-5733","source":"IETF/RFC-5733/RFC-5733.txt","version":null},{"body":"IETF","designation":"RFC 5738","folder":"IETF/RFC-5738","source":"IETF/RFC-5738/RFC-5738.txt","version":null},{"body":"IETF","designation":"RFC 5760","folder":"IETF/RFC-5760","source":"IETF/RFC-5760/RFC-5760.txt","version":null},{"body":"IETF","designation":"RFC 5792","folder":"IETF/RFC-5792","source":"IETF/RFC-5792/RFC-5792.txt","version":null},{"body":"IETF","designation":"RFC 5793","folder":"IETF/RFC-5793","source":"IETF/RFC-5793/RFC-5793.txt","version":null},{"body":"IETF","designation":"RFC 5801","folder":"IETF/RFC-5801","source":"IETF/RFC-5801/RFC-5801.txt","version":null},{"body":"IETF","designation":"RFC 5802","folder":"IETF/RFC-5802","source":"IETF/RFC-5802/RFC-5802.txt","version":null},{"body":"IETF","designation":"RFC 5804","folder":"IETF/RFC-5804","source":"IETF/RFC-5804/RFC-5804.txt","version":null},{"body":"IETF","designation":"RFC 5837","folder":"IETF/RFC-5837","source":"IETF/RFC-5837/RFC-5837.txt","version":null},{"body":"IETF","designation":"RFC 5849","folder":"IETF/RFC-5849","source":"IETF/RFC-5849/RFC-5849.txt","version":null},{"body":"IETF","designation":"RFC 5878","folder":"IETF/RFC-5878","source":"IETF/RFC-5878/RFC-5878.txt","version":null},{"body":"IETF","designation":"RFC 5910","folder":"IETF/RFC-5910","source":"IETF/RFC-5910/RFC-5910.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5970","folder":"IETF/RFC-5970","source":"IETF/RFC-5970/RFC-5970.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6047","folder":"IETF/RFC-6047","source":"IETF/RFC-6047/RFC-6047.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6068","folder":"IETF/RFC-6068","source":"IETF/RFC-6068/RFC-6068.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6124","folder":"IETF/RFC-6124","source":"IETF/RFC-6124/RFC-6124.txt","version":null},{"body":"IETF","designation":"RFC 6158","folder":"IETF/RFC-6158","source":"IETF/RFC-6158/RFC-6158.txt","version":null},{"body":"IETF","designation":"RFC 6230","folder":"IETF/RFC-6230","source":"IETF/RFC-6230/RFC-6230.txt","version":null},{"body":"IETF","designation":"RFC 6241","folder":"IETF/RFC-6241","source":"IETF/RFC-6241/RFC-6241.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 6265","folder":"IETF/RFC-6265","source":"IETF/RFC-6265/RFC-6265.txt","version":null},{"body":"IETF","designation":"RFC 6272","folder":"IETF/RFC-6272","source":"IETF/RFC-6272/RFC-6272.txt","version":null},{"body":"IETF","designation":"RFC 6283","folder":"IETF/RFC-6283","source":"IETF/RFC-6283/RFC-6283.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 6376","folder":"IETF/RFC-6376","source":"IETF/RFC-6376/RFC-6376.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null},{"body":"IETF","designation":"RFC 6455","folder":"IETF/RFC-6455","source":"IETF/RFC-6455/RFC-6455.txt","version":null},{"body":"IETF","designation":"RFC 6530","folder":"IETF/RFC-6530","source":"IETF/RFC-6530/RFC-6530.txt","version":null},{"body":"IETF","designation":"RFC 6531","folder":"IETF/RFC-6531","source":"IETF/RFC-6531/RFC-6531.txt","version":null},{"body":"IETF","designation":"RFC 6532","folder":"IETF/RFC-6532","source":"IETF/RFC-6532/RFC-6532.txt","version":null},{"body":"IETF","designation":"RFC 6533","folder":"IETF/RFC-6533","source":"IETF/RFC-6533/RFC-6533.txt","version":null},{"body":"IETF","designation":"RFC 6570","folder":"IETF/RFC-6570","source":"IETF/RFC-6570/RFC-6570.txt","version":null},{"body":"IETF","designation":"RFC 6657","folder":"IETF/RFC-6657","source":"IETF/RFC-6657/RFC-6657.txt","version":null},{"body":"IETF","designation":"RFC 6678","folder":"IETF/RFC-6678","source":"IETF/RFC-6678/RFC-6678.txt","version":null},{"body":"IETF","designation":"RFC 6679","folder":"IETF/RFC-6679","source":"IETF/RFC-6679/RFC-6679.txt","version":null},{"body":"IETF","designation":"RFC 6690","folder":"IETF/RFC-6690","source":"IETF/RFC-6690/RFC-6690.txt","version":null},{"body":"IETF","designation":"RFC 6733","folder":"IETF/RFC-6733","source":"IETF/RFC-6733/RFC-6733.txt","version":null},{"body":"IETF","designation":"RFC 6749","folder":"IETF/RFC-6749","source":"IETF/RFC-6749/RFC-6749.txt","version":null},{"body":"IETF","designation":"RFC 6757","folder":"IETF/RFC-6757","source":"IETF/RFC-6757/RFC-6757.txt","version":null},{"body":"IETF","designation":"RFC 6760","folder":"IETF/RFC-6760","source":"IETF/RFC-6760/RFC-6760.txt","version":null},{"body":"IETF","designation":"RFC 6762","folder":"IETF/RFC-6762","source":"IETF/RFC-6762/RFC-6762.txt","version":null},{"body":"IETF","designation":"RFC 6763","folder":"IETF/RFC-6763","source":"IETF/RFC-6763/RFC-6763.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6838","folder":"IETF/RFC-6838","source":"IETF/RFC-6838/RFC-6838.txt","version":null},{"body":"IETF","designation":"RFC 6855","folder":"IETF/RFC-6855","source":"IETF/RFC-6855/RFC-6855.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null},{"body":"IETF","designation":"RFC 6857","folder":"IETF/RFC-6857","source":"IETF/RFC-6857/RFC-6857.txt","version":null},{"body":"IETF","designation":"RFC 6901","folder":"IETF/RFC-6901","source":"IETF/RFC-6901/RFC-6901.txt","version":null},{"body":"IETF","designation":"RFC 7011","folder":"IETF/RFC-7011","source":"IETF/RFC-7011/RFC-7011.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7227","folder":"IETF/RFC-7227","source":"IETF/RFC-7227/RFC-7227.txt","version":null},{"body":"IETF","designation":"RFC 7252","folder":"IETF/RFC-7252","source":"IETF/RFC-7252/RFC-7252.txt","version":null},{"body":"IETF","designation":"RFC 7254","folder":"IETF/RFC-7254","source":"IETF/RFC-7254/RFC-7254.txt","version":null},{"body":"IETF","designation":"RFC 7301","folder":"IETF/RFC-7301","source":"IETF/RFC-7301/RFC-7301.txt","version":null},{"body":"IETF","designation":"RFC 7303","folder":"IETF/RFC-7303","source":"IETF/RFC-7303/RFC-7303.txt","version":null},{"body":"IETF","designation":"RFC 7464","folder":"IETF/RFC-7464","source":"IETF/RFC-7464/RFC-7464.txt","version":null},{"body":"IETF","designation":"RFC 7483","folder":"IETF/RFC-7483","source":"IETF/RFC-7483/RFC-7483.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7516","folder":"IETF/RFC-7516","source":"IETF/RFC-7516/RFC-7516.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 7518","folder":"IETF/RFC-7518","source":"IETF/RFC-7518/RFC-7518.txt","version":null},{"body":"IETF","designation":"RFC 7530","folder":"IETF/RFC-7530","source":"IETF/RFC-7530/RFC-7530.txt","version":null},{"body":"IETF","designation":"RFC 7542","folder":"IETF/RFC-7542","source":"IETF/RFC-7542/RFC-7542.txt","version":null},{"body":"IETF","designation":"RFC 7564","folder":"IETF/RFC-7564","source":"IETF/RFC-7564/RFC-7564.txt","version":null},{"body":"IETF","designation":"RFC 7572","folder":"IETF/RFC-7572","source":"IETF/RFC-7572/RFC-7572.txt","version":null},{"body":"IETF","designation":"RFC 7613","folder":"IETF/RFC-7613","source":"IETF/RFC-7613/RFC-7613.txt","version":null},{"body":"IETF","designation":"RFC 7616","folder":"IETF/RFC-7616","source":"IETF/RFC-7616/RFC-7616.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 7622","folder":"IETF/RFC-7622","source":"IETF/RFC-7622/RFC-7622.txt","version":null},{"body":"IETF","designation":"RFC 7643","folder":"IETF/RFC-7643","source":"IETF/RFC-7643/RFC-7643.txt","version":null},{"body":"IETF","designation":"RFC 7644","folder":"IETF/RFC-7644","source":"IETF/RFC-7644/RFC-7644.txt","version":null},{"body":"IETF","designation":"RFC 7797","folder":"IETF/RFC-7797","source":"IETF/RFC-7797/RFC-7797.txt","version":null},{"body":"IETF","designation":"RFC 7800","folder":"IETF/RFC-7800","source":"IETF/RFC-7800/RFC-7800.txt","version":null},{"body":"IETF","designation":"RFC 7804","folder":"IETF/RFC-7804","source":"IETF/RFC-7804/RFC-7804.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 7839","folder":"IETF/RFC-7839","source":"IETF/RFC-7839/RFC-7839.txt","version":null},{"body":"IETF","designation":"RFC 7941","folder":"IETF/RFC-7941","source":"IETF/RFC-7941/RFC-7941.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 7992","folder":"IETF/RFC-7992","source":"IETF/RFC-7992/RFC-7992.txt","version":null},{"body":"IETF","designation":"RFC 7994","folder":"IETF/RFC-7994","source":"IETF/RFC-7994/RFC-7994.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8089","folder":"IETF/RFC-8089","source":"IETF/RFC-8089/RFC-8089.txt","version":null},{"body":"IETF","designation":"RFC 8187","folder":"IETF/RFC-8187","source":"IETF/RFC-8187/RFC-8187.txt","version":null},{"body":"IETF","designation":"RFC 8188","folder":"IETF/RFC-8188","source":"IETF/RFC-8188/RFC-8188.txt","version":null},{"body":"IETF","designation":"RFC 8225","folder":"IETF/RFC-8225","source":"IETF/RFC-8225/RFC-8225.txt","version":null},{"body":"IETF","designation":"RFC 8259","folder":"IETF/RFC-8259","source":"IETF/RFC-8259/RFC-8259.txt","version":null},{"body":"IETF","designation":"RFC 8264","folder":"IETF/RFC-8264","source":"IETF/RFC-8264/RFC-8264.txt","version":null},{"body":"IETF","designation":"RFC 8265","folder":"IETF/RFC-8265","source":"IETF/RFC-8265/RFC-8265.txt","version":null},{"body":"IETF","designation":"RFC 8398","folder":"IETF/RFC-8398","source":"IETF/RFC-8398/RFC-8398.txt","version":null},{"body":"IETF","designation":"RFC 8399","folder":"IETF/RFC-8399","source":"IETF/RFC-8399/RFC-8399.txt","version":null},{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 8415","folder":"IETF/RFC-8415","source":"IETF/RFC-8415/RFC-8415.txt","version":null},{"body":"IETF","designation":"RFC 8417","folder":"IETF/RFC-8417","source":"IETF/RFC-8417/RFC-8417.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8461","folder":"IETF/RFC-8461","source":"IETF/RFC-8461/RFC-8461.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null},{"body":"IETF","designation":"RFC 8520","folder":"IETF/RFC-8520","source":"IETF/RFC-8520/RFC-8520.txt","version":null},{"body":"IETF","designation":"RFC 8555","folder":"IETF/RFC-8555","source":"IETF/RFC-8555/RFC-8555.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 8620","folder":"IETF/RFC-8620","source":"IETF/RFC-8620/RFC-8620.txt","version":null},{"body":"IETF","designation":"RFC 8832","folder":"IETF/RFC-8832","source":"IETF/RFC-8832/RFC-8832.txt","version":null},{"body":"IETF","designation":"RFC 8843","folder":"IETF/RFC-8843","source":"IETF/RFC-8843/RFC-8843.txt","version":null},{"body":"IETF","designation":"RFC 8855","folder":"IETF/RFC-8855","source":"IETF/RFC-8855/RFC-8855.txt","version":null},{"body":"IETF","designation":"RFC 8864","folder":"IETF/RFC-8864","source":"IETF/RFC-8864/RFC-8864.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null},{"body":"IETF","designation":"RFC 8941","folder":"IETF/RFC-8941","source":"IETF/RFC-8941/RFC-8941.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9000","folder":"IETF/RFC-9000","source":"IETF/RFC-9000/RFC-9000.txt","version":null},{"body":"IETF","designation":"RFC 9051","folder":"IETF/RFC-9051","source":"IETF/RFC-9051/RFC-9051.txt","version":null},{"body":"IETF","designation":"RFC 9083","folder":"IETF/RFC-9083","source":"IETF/RFC-9083/RFC-9083.txt","version":null},{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null},{"body":"IETF","designation":"RFC 9461","folder":"IETF/RFC-9461","source":"IETF/RFC-9461/RFC-9461.txt","version":null},{"body":"IETF","designation":"RFC 9485","folder":"IETF/RFC-9485","source":"IETF/RFC-9485/RFC-9485.txt","version":null},{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null}],"search_text":"ISO-IEC ISO 10646 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO 10733","type":"specification","body":"ISO-IEC","designation":"ISO 10733","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10733","download_urls":["https://www.iso.org/search.html?q=ISO+10733"],"folder":"ISO-IEC/ISO-10733","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null}],"search_text":"ISO-IEC ISO 10733 nested-reference unavailable"},{"id":"ISO-IEC ISO 10736","type":"specification","body":"ISO-IEC","designation":"ISO 10736","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10736","download_urls":["https://www.iso.org/search.html?q=ISO+10736"],"folder":"ISO-IEC/ISO-10736","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 10736 nested-reference unavailable"},{"id":"ISO-IEC ISO 10747","type":"specification","body":"ISO-IEC","designation":"ISO 10747","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10747","download_urls":["https://www.iso.org/search.html?q=ISO+10747"],"folder":"ISO-IEC/ISO-10747","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null}],"search_text":"ISO-IEC ISO 10747 nested-reference unavailable"},{"id":"ISO-IEC ISO 10918-1","type":"specification","body":"ISO-IEC","designation":"ISO 10918-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+10918-1","download_urls":["https://www.iso.org/search.html?q=ISO+10918-1"],"folder":"ISO-IEC/ISO-10918-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null}],"search_text":"ISO-IEC ISO 10918-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 11172","type":"specification","body":"ISO-IEC","designation":"ISO 11172","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+11172","download_urls":["https://www.iso.org/search.html?q=ISO+11172"],"folder":"ISO-IEC/ISO-11172","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null}],"search_text":"ISO-IEC ISO 11172 nested-reference unavailable"},{"id":"ISO-IEC ISO 11578","type":"specification","body":"ISO-IEC","designation":"ISO 11578","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+11578","download_urls":["https://www.iso.org/search.html?q=ISO+11578"],"folder":"ISO-IEC/ISO-11578","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null}],"search_text":"ISO-IEC ISO 11578 nested-reference unavailable"},{"id":"ISO-IEC ISO 11586","type":"specification","body":"ISO-IEC","designation":"ISO 11586","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+11586","download_urls":["https://www.iso.org/search.html?q=ISO+11586"],"folder":"ISO-IEC/ISO-11586","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 11586 nested-reference unavailable"},{"id":"ISO-IEC ISO 12083 V1993","type":"specification","body":"ISO-IEC","designation":"ISO 12083","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+12083","download_urls":["https://www.iso.org/search.html?q=ISO+12083"],"folder":"ISO-IEC/ISO-12083-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null}],"search_text":"ISO-IEC ISO 12083 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO 128-20","type":"specification","body":"ISO-IEC","designation":"ISO 128-20","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+128-20","download_urls":["https://www.iso.org/search.html?q=ISO+128-20"],"folder":"ISO-IEC/ISO-128-20","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 128-20 nested-reference unavailable"},{"id":"ISO-IEC ISO 128-71","type":"specification","body":"ISO-IEC","designation":"ISO 128-71","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+128-71","download_urls":["https://www.iso.org/search.html?q=ISO+128-71"],"folder":"ISO-IEC/ISO-128-71","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 128-71 nested-reference unavailable"},{"id":"ISO-IEC ISO 13616","type":"specification","body":"ISO-IEC","designation":"ISO 13616","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13616","download_urls":["https://www.iso.org/search.html?q=ISO+13616"],"folder":"ISO-IEC/ISO-13616","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null}],"search_text":"ISO-IEC ISO 13616 nested-reference unavailable"},{"id":"ISO-IEC ISO 13616-1 V2007","type":"specification","body":"ISO-IEC","designation":"ISO 13616-1","version":"2007","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13616-1","download_urls":["https://www.iso.org/search.html?q=ISO+13616-1"],"folder":"ISO-IEC/ISO-13616-1-V2007","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null}],"search_text":"ISO-IEC ISO 13616-1 2007 nested-reference unavailable"},{"id":"ISO-IEC ISO 13818","type":"specification","body":"ISO-IEC","designation":"ISO 13818","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13818","download_urls":["https://www.iso.org/search.html?q=ISO+13818"],"folder":"ISO-IEC/ISO-13818","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"ISO-IEC ISO 13818 nested-reference unavailable"},{"id":"ISO-IEC ISO 13818-1","type":"specification","body":"ISO-IEC","designation":"ISO 13818-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13818-1","download_urls":["https://www.iso.org/search.html?q=ISO+13818-1"],"folder":"ISO-IEC/ISO-13818-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null}],"search_text":"ISO-IEC ISO 13818-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 13818-6","type":"specification","body":"ISO-IEC","designation":"ISO 13818-6","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13818-6","download_urls":["https://www.iso.org/search.html?q=ISO+13818-6"],"folder":"ISO-IEC/ISO-13818-6","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null}],"search_text":"ISO-IEC ISO 13818-6 nested-reference unavailable"},{"id":"ISO-IEC ISO 13888-1","type":"specification","body":"ISO-IEC","designation":"ISO 13888-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+13888-1","download_urls":["https://www.iso.org/search.html?q=ISO+13888-1"],"folder":"ISO-IEC/ISO-13888-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO 13888-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 14289-1","type":"specification","body":"ISO-IEC","designation":"ISO 14289-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14289-1","download_urls":["https://www.iso.org/search.html?q=ISO+14289-1"],"folder":"ISO-IEC/ISO-14289-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"ISO-IEC ISO 14289-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 14496","type":"specification","body":"ISO-IEC","designation":"ISO 14496","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14496","download_urls":["https://www.iso.org/search.html?q=ISO+14496"],"folder":"ISO-IEC/ISO-14496","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null}],"search_text":"ISO-IEC ISO 14496 nested-reference unavailable"},{"id":"ISO-IEC ISO 14533-4","type":"specification","body":"ISO-IEC","designation":"ISO 14533-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14533-4","download_urls":["https://www.iso.org/search.html?q=ISO+14533-4"],"folder":"ISO-IEC/ISO-14533-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"}],"search_text":"ISO-IEC ISO 14533-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 14641","type":"specification","body":"ISO-IEC","designation":"ISO 14641","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14641","download_urls":["https://www.iso.org/search.html?q=ISO+14641"],"folder":"ISO-IEC/ISO-14641","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 14641 cited-by-eu-law implementing-regulation unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO 14641-1 V2018","type":"specification","body":"ISO-IEC","designation":"ISO 14641-1","version":"2018","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14641-1","download_urls":["https://www.iso.org/search.html?q=ISO+14641-1"],"folder":"ISO-IEC/ISO-14641-1-V2018","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 14641-1 2018 nested-reference unavailable"},{"id":"ISO-IEC ISO 14721 V2025","type":"specification","body":"ISO-IEC","designation":"ISO 14721","version":"2025","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14721","download_urls":["https://www.iso.org/search.html?q=ISO+14721"],"folder":"ISO-IEC/ISO-14721-V2025","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"},{"celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","id":"2025-2532","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2532/2025-2532.md","title":"Qualified electronic archiving services"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 14721 2025 cited-by-eu-law implementing-regulation nested-reference unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162 2025-2532 Qualified electronic archiving services 32025R2532"},{"id":"ISO-IEC ISO 14888-1","type":"specification","body":"ISO-IEC","designation":"ISO 14888-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14888-1","download_urls":["https://www.iso.org/search.html?q=ISO+14888-1"],"folder":"ISO-IEC/ISO-14888-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 14888-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 14888-2","type":"specification","body":"ISO-IEC","designation":"ISO 14888-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14888-2","download_urls":["https://www.iso.org/search.html?q=ISO+14888-2"],"folder":"ISO-IEC/ISO-14888-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 14888-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 14888-3","type":"specification","body":"ISO-IEC","designation":"ISO 14888-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+14888-3","download_urls":["https://www.iso.org/search.html?q=ISO+14888-3"],"folder":"ISO-IEC/ISO-14888-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 14888-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 148881-1","type":"specification","body":"ISO-IEC","designation":"ISO 148881-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+148881-1","download_urls":["https://www.iso.org/search.html?q=ISO+148881-1"],"folder":"ISO-IEC/ISO-148881-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 148881-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 15000","type":"specification","body":"ISO-IEC","designation":"ISO 15000","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15000","download_urls":["https://www.iso.org/search.html?q=ISO+15000"],"folder":"ISO-IEC/ISO-15000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 15000 nested-reference unavailable"},{"id":"ISO-IEC ISO 15000-2 V2021","type":"specification","body":"ISO-IEC","designation":"ISO 15000-2","version":"2021","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15000-2","download_urls":["https://www.iso.org/search.html?q=ISO+15000-2"],"folder":"ISO-IEC/ISO-15000-2-V2021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 15000-2 2021 nested-reference unavailable"},{"id":"ISO-IEC ISO 15000-3 V2023","type":"specification","body":"ISO-IEC","designation":"ISO 15000-3","version":"2023","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15000-3","download_urls":["https://www.iso.org/search.html?q=ISO+15000-3"],"folder":"ISO-IEC/ISO-15000-3-V2023","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 15000-3 2023 nested-reference unavailable"},{"id":"ISO-IEC ISO 15489-1 V2001","type":"specification","body":"ISO-IEC","designation":"ISO 15489-1","version":"2001","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15489-1","download_urls":["https://www.iso.org/search.html?q=ISO+15489-1"],"folder":"ISO-IEC/ISO-15489-1-V2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 15489-1 2001 nested-reference unavailable"},{"id":"ISO-IEC ISO 15802-3","type":"specification","body":"ISO-IEC","designation":"ISO 15802-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15802-3","download_urls":["https://www.iso.org/search.html?q=ISO+15802-3"],"folder":"ISO-IEC/ISO-15802-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"ISO-IEC ISO 15802-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 15816","type":"specification","body":"ISO-IEC","designation":"ISO 15816","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15816","download_urls":["https://www.iso.org/search.html?q=ISO+15816"],"folder":"ISO-IEC/ISO-15816","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null}],"search_text":"ISO-IEC ISO 15816 nested-reference unavailable"},{"id":"ISO-IEC ISO 15924 V2004","type":"specification","body":"ISO-IEC","designation":"ISO 15924","version":"2004","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15924","download_urls":["https://www.iso.org/search.html?q=ISO+15924"],"folder":"ISO-IEC/ISO-15924-V2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4676","folder":"IETF/RFC-4676","source":"IETF/RFC-4676/RFC-4676.txt","version":null},{"body":"IETF","designation":"RFC 4776","folder":"IETF/RFC-4776","source":"IETF/RFC-4776/RFC-4776.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null}],"search_text":"ISO-IEC ISO 15924 2004 nested-reference unavailable"},{"id":"ISO-IEC ISO 15930","type":"specification","body":"ISO-IEC","designation":"ISO 15930","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15930","download_urls":["https://www.iso.org/search.html?q=ISO+15930"],"folder":"ISO-IEC/ISO-15930","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null}],"search_text":"ISO-IEC ISO 15930 nested-reference unavailable"},{"id":"ISO-IEC ISO 15930-1 V2001","type":"specification","body":"ISO-IEC","designation":"ISO 15930-1","version":"2001","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15930-1","download_urls":["https://www.iso.org/search.html?q=ISO+15930-1"],"folder":"ISO-IEC/ISO-15930-1-V2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3778","folder":"IETF/RFC-3778","source":"IETF/RFC-3778/RFC-3778.txt","version":null}],"search_text":"ISO-IEC ISO 15930-1 2001 nested-reference unavailable"},{"id":"ISO-IEC ISO 15946","type":"specification","body":"ISO-IEC","designation":"ISO 15946","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15946","download_urls":["https://www.iso.org/search.html?q=ISO+15946"],"folder":"ISO-IEC/ISO-15946","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"}],"search_text":"ISO-IEC ISO 15946 nested-reference unavailable"},{"id":"ISO-IEC ISO 15946-2","type":"specification","body":"ISO-IEC","designation":"ISO 15946-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+15946-2","download_urls":["https://www.iso.org/search.html?q=ISO+15946-2"],"folder":"ISO-IEC/ISO-15946-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO 15946-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 16363 V2011","type":"specification","body":"ISO-IEC","designation":"ISO 16363","version":"2011","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+16363","download_urls":["https://www.iso.org/search.html?q=ISO+16363"],"folder":"ISO-IEC/ISO-16363-V2011","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 16363 2011 nested-reference unavailable"},{"id":"ISO-IEC ISO 16684-1","type":"specification","body":"ISO-IEC","designation":"ISO 16684-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+16684-1","download_urls":["https://www.iso.org/search.html?q=ISO+16684-1"],"folder":"ISO-IEC/ISO-16684-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"ISO-IEC ISO 16684-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 17442","type":"specification","body":"ISO-IEC","designation":"ISO 17442","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+17442","download_urls":["https://www.iso.org/search.html?q=ISO+17442"],"folder":"ISO-IEC/ISO-17442","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"}],"search_text":"ISO-IEC ISO 17442 nested-reference unavailable"},{"id":"ISO-IEC ISO 17442-1 V2020","type":"specification","body":"ISO-IEC","designation":"ISO 17442-1","version":"2020","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+17442-1","download_urls":["https://www.iso.org/search.html?q=ISO+17442-1"],"folder":"ISO-IEC/ISO-17442-1-V2020","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 17442-1 2020 nested-reference unavailable"},{"id":"ISO-IEC ISO 1745","type":"specification","body":"ISO-IEC","designation":"ISO 1745","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+1745","download_urls":["https://www.iso.org/search.html?q=ISO+1745"],"folder":"ISO-IEC/ISO-1745","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null}],"search_text":"ISO-IEC ISO 1745 nested-reference unavailable"},{"id":"ISO-IEC ISO 17799","type":"specification","body":"ISO-IEC","designation":"ISO 17799","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+17799","download_urls":["https://www.iso.org/search.html?q=ISO+17799"],"folder":"ISO-IEC/ISO-17799","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 17799 nested-reference unavailable"},{"id":"ISO-IEC ISO 18004","type":"specification","body":"ISO-IEC","designation":"ISO 18004","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18004","download_urls":["https://www.iso.org/search.html?q=ISO+18004"],"folder":"ISO-IEC/ISO-18004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null}],"search_text":"ISO-IEC ISO 18004 nested-reference unavailable"},{"id":"ISO-IEC ISO 18013-5","type":"specification","body":"ISO-IEC","designation":"ISO 18013-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18013-5","download_urls":["https://www.iso.org/search.html?q=ISO+18013-5"],"folder":"ISO-IEC/ISO-18013-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS13","folder":"ARF/TS13-V1.0.1","source":"ARF/TS13-V1.0.1/TS13-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO 18013-5 nested-reference unavailable"},{"id":"ISO-IEC ISO 18013-7","type":"specification","body":"ISO-IEC","designation":"ISO 18013-7","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18013-7","download_urls":["https://www.iso.org/search.html?q=ISO+18013-7"],"folder":"ISO-IEC/ISO-18013-7","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO 18013-7 nested-reference unavailable"},{"id":"ISO-IEC ISO 18033","type":"specification","body":"ISO-IEC","designation":"ISO 18033","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18033","download_urls":["https://www.iso.org/search.html?q=ISO+18033"],"folder":"ISO-IEC/ISO-18033","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO 18033 nested-reference unavailable"},{"id":"ISO-IEC ISO 18045","type":"specification","body":"ISO-IEC","designation":"ISO 18045","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18045","download_urls":["https://www.iso.org/search.html?q=ISO+18045"],"folder":"ISO-IEC/ISO-18045","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ISO-IEC ISO 18045 nested-reference unavailable"},{"id":"ISO-IEC ISO 18370-2 V2016","type":"specification","body":"ISO-IEC","designation":"ISO 18370-2","version":"2016","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+18370-2","download_urls":["https://www.iso.org/search.html?q=ISO+18370-2"],"folder":"ISO-IEC/ISO-18370-2-V2016","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO 18370-2 2016 nested-reference unavailable"},{"id":"ISO-IEC ISO 19005","type":"specification","body":"ISO-IEC","designation":"ISO 19005","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19005","download_urls":["https://www.iso.org/search.html?q=ISO+19005"],"folder":"ISO-IEC/ISO-19005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ISO-IEC ISO 19005 nested-reference unavailable"},{"id":"ISO-IEC ISO 19005-2","type":"specification","body":"ISO-IEC","designation":"ISO 19005-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19005-2","download_urls":["https://www.iso.org/search.html?q=ISO+19005-2"],"folder":"ISO-IEC/ISO-19005-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"ISO-IEC ISO 19005-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 19005-3","type":"specification","body":"ISO-IEC","designation":"ISO 19005-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19005-3","download_urls":["https://www.iso.org/search.html?q=ISO+19005-3"],"folder":"ISO-IEC/ISO-19005-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"ISO-IEC ISO 19005-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 19770","type":"specification","body":"ISO-IEC","designation":"ISO 19770","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19770","download_urls":["https://www.iso.org/search.html?q=ISO+19770"],"folder":"ISO-IEC/ISO-19770","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"ISO-IEC ISO 19770 nested-reference unavailable"},{"id":"ISO-IEC ISO 19770-2 V2015","type":"specification","body":"ISO-IEC","designation":"ISO 19770-2","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19770-2","download_urls":["https://www.iso.org/search.html?q=ISO+19770-2"],"folder":"ISO-IEC/ISO-19770-2-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"ISO-IEC ISO 19770-2 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO 19794-5","type":"specification","body":"ISO-IEC","designation":"ISO 19794-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+19794-5","download_urls":["https://www.iso.org/search.html?q=ISO+19794-5"],"folder":"ISO-IEC/ISO-19794-5","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 19794-5 cited-by-eu-law implementing-regulation unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977"},{"id":"ISO-IEC ISO 1988","type":"specification","body":"ISO-IEC","designation":"ISO 1988","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+1988","download_urls":["https://www.iso.org/search.html?q=ISO+1988"],"folder":"ISO-IEC/ISO-1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null}],"search_text":"ISO-IEC ISO 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 20008-2","type":"specification","body":"ISO-IEC","designation":"ISO 20008-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+20008-2","download_urls":["https://www.iso.org/search.html?q=ISO+20008-2"],"folder":"ISO-IEC/ISO-20008-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO 20008-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 20022","type":"specification","body":"ISO-IEC","designation":"ISO 20022","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+20022","download_urls":["https://www.iso.org/search.html?q=ISO+20022"],"folder":"ISO-IEC/ISO-20022","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 20022 nested-reference unavailable"},{"id":"ISO-IEC ISO 2009","type":"specification","body":"ISO-IEC","designation":"ISO 2009","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2009","download_urls":["https://www.iso.org/search.html?q=ISO+2009"],"folder":"ISO-IEC/ISO-2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"ISO-IEC ISO 2009 nested-reference unavailable"},{"id":"ISO-IEC ISO 2015","type":"specification","body":"ISO-IEC","designation":"ISO 2015","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2015","download_urls":["https://www.iso.org/search.html?q=ISO+2015"],"folder":"ISO-IEC/ISO-2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null}],"search_text":"ISO-IEC ISO 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO 2022-1986","type":"specification","body":"ISO-IEC","designation":"ISO 2022-1986","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2022-1986","download_urls":["https://www.iso.org/search.html?q=ISO+2022-1986"],"folder":"ISO-IEC/ISO-2022-1986","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1557","folder":"IETF/RFC-1557","source":"IETF/RFC-1557/RFC-1557.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null}],"search_text":"ISO-IEC ISO 2022-1986 nested-reference unavailable"},{"id":"ISO-IEC ISO 2022 V1986","type":"specification","body":"ISO-IEC","designation":"ISO 2022","version":"1986","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2022","download_urls":["https://www.iso.org/search.html?q=ISO+2022"],"folder":"ISO-IEC/ISO-2022-V1986","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1557","folder":"IETF/RFC-1557","source":"IETF/RFC-1557/RFC-1557.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2822","folder":"IETF/RFC-2822","source":"IETF/RFC-2822/RFC-2822.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO 2022 1986 nested-reference unavailable"},{"id":"ISO-IEC ISO 2047","type":"specification","body":"ISO-IEC","designation":"ISO 2047","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2047","download_urls":["https://www.iso.org/search.html?q=ISO+2047"],"folder":"ISO-IEC/ISO-2047","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null}],"search_text":"ISO-IEC ISO 2047 nested-reference unavailable"},{"id":"ISO-IEC ISO 2108 V1992","type":"specification","body":"ISO-IEC","designation":"ISO 2108","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2108","download_urls":["https://www.iso.org/search.html?q=ISO+2108"],"folder":"ISO-IEC/ISO-2108-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2288","folder":"IETF/RFC-2288","source":"IETF/RFC-2288/RFC-2288.txt","version":null},{"body":"IETF","designation":"RFC 3187","folder":"IETF/RFC-3187","source":"IETF/RFC-3187/RFC-3187.txt","version":null}],"search_text":"ISO-IEC ISO 2108 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO 216","type":"specification","body":"ISO-IEC","designation":"ISO 216","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+216","download_urls":["https://www.iso.org/search.html?q=ISO+216"],"folder":"ISO-IEC/ISO-216","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2346","folder":"IETF/RFC-2346","source":"IETF/RFC-2346/RFC-2346.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"ISO-IEC ISO 216 nested-reference unavailable"},{"id":"ISO-IEC ISO 22301","type":"specification","body":"ISO-IEC","designation":"ISO 22301","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+22301","download_urls":["https://www.iso.org/search.html?q=ISO+22301"],"folder":"ISO-IEC/ISO-22301","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 22301 nested-reference unavailable"},{"id":"ISO-IEC ISO 22313","type":"specification","body":"ISO-IEC","designation":"ISO 22313","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+22313","download_urls":["https://www.iso.org/search.html?q=ISO+22313"],"folder":"ISO-IEC/ISO-22313","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 22313 nested-reference unavailable"},{"id":"ISO-IEC ISO 23220-2","type":"specification","body":"ISO-IEC","designation":"ISO 23220-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+23220-2","download_urls":["https://www.iso.org/search.html?q=ISO+23220-2"],"folder":"ISO-IEC/ISO-23220-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 23220-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 23220-7","type":"specification","body":"ISO-IEC","designation":"ISO 23220-7","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+23220-7","download_urls":["https://www.iso.org/search.html?q=ISO+23220-7"],"folder":"ISO-IEC/ISO-23220-7","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ISO-IEC ISO 23220-7 nested-reference unavailable"},{"id":"ISO-IEC ISO 23257 V2022","type":"specification","body":"ISO-IEC","designation":"ISO 23257","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+23257","download_urls":["https://www.iso.org/search.html?q=ISO+23257"],"folder":"ISO-IEC/ISO-23257-V2022","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"},{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 23257 2022 cited-by-eu-law implementing-regulation unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162 2025-2531 Qualified electronic ledgers 32025R2531"},{"id":"ISO-IEC ISO 2375","type":"specification","body":"ISO-IEC","designation":"ISO 2375","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2375","download_urls":["https://www.iso.org/search.html?q=ISO+2375"],"folder":"ISO-IEC/ISO-2375","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null}],"search_text":"ISO-IEC ISO 2375 nested-reference unavailable"},{"id":"ISO-IEC ISO 2382-2 V1976","type":"specification","body":"ISO-IEC","designation":"ISO 2382-2","version":"1976","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+2382-2","download_urls":["https://www.iso.org/search.html?q=ISO+2382-2"],"folder":"ISO-IEC/ISO-2382-2-V1976","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 2382-2 1976 nested-reference unavailable"},{"id":"ISO-IEC ISO 26324 V2012","type":"specification","body":"ISO-IEC","designation":"ISO 26324","version":"2012","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+26324","download_urls":["https://www.iso.org/search.html?q=ISO+26324"],"folder":"ISO-IEC/ISO-26324-V2012","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7669","folder":"IETF/RFC-7669","source":"IETF/RFC-7669/RFC-7669.txt","version":null}],"search_text":"ISO-IEC ISO 26324 2012 nested-reference unavailable"},{"id":"ISO-IEC ISO 269","type":"specification","body":"ISO-IEC","designation":"ISO 269","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+269","download_urls":["https://www.iso.org/search.html?q=ISO+269"],"folder":"ISO-IEC/ISO-269","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null}],"search_text":"ISO-IEC ISO 269 nested-reference unavailable"},{"id":"ISO-IEC ISO 27729 V2012","type":"specification","body":"ISO-IEC","designation":"ISO 27729","version":"2012","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+27729","download_urls":["https://www.iso.org/search.html?q=ISO+27729"],"folder":"ISO-IEC/ISO-27729-V2012","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8141","folder":"IETF/RFC-8141","source":"IETF/RFC-8141/RFC-8141.txt","version":null}],"search_text":"ISO-IEC ISO 27729 2012 nested-reference unavailable"},{"id":"ISO-IEC ISO 29115","type":"specification","body":"ISO-IEC","designation":"ISO 29115","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+29115","download_urls":["https://www.iso.org/search.html?q=ISO+29115"],"folder":"ISO-IEC/ISO-29115","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 521","folder":"ETSI/EN-319-521-V1.1.1","source":"ETSI/EN-319-521-V1.1.1/EN-319-521-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO 29115 nested-reference unavailable"},{"id":"ISO-IEC ISO 3166","type":"specification","body":"ISO-IEC","designation":"ISO 3166","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3166","download_urls":["https://www.iso.org/search.html?q=ISO+3166"],"folder":"ISO-IEC/ISO-3166","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 3166 cited-by-eu-law implementing-regulation unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO 3166-1 V2006","type":"specification","body":"ISO-IEC","designation":"ISO 3166-1","version":"2006","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3166-1","download_urls":["https://www.iso.org/search.html?q=ISO+3166-1"],"folder":"ISO-IEC/ISO-3166-1-V2006","files":{},"tags":["cited-by-eu-law","implementing-decision","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32025R0848","eli":"https://data.europa.eu/eli/reg_impl/2025/848/oj/eng","id":"2025-848","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-848/2025-848.md","title":"Registration of wallet-relying parties"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"},{"celex":"32025D2164","eli":"https://data.europa.eu/eli/dec_impl/2025/2164/oj/eng","id":"2025-2164","kind":"implementing_decision","section":"implementing-decisions","source":"implementing-decisions/2025-2164/2025-2164.md","title":"Trusted lists of trust service providers"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 3166-1 2006 cited-by-eu-law implementing-decision implementing-regulation unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2025-848 Registration of wallet-relying parties 32025R0848 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731 2025-2164 Trusted lists of trust service providers 32025D2164"},{"id":"ISO-IEC ISO 3166-2 V2020","type":"specification","body":"ISO-IEC","designation":"ISO 3166-2","version":"2020","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3166-2","download_urls":["https://www.iso.org/search.html?q=ISO+3166-2"],"folder":"ISO-IEC/ISO-3166-2-V2020","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 5139","folder":"IETF/RFC-5139","source":"IETF/RFC-5139/RFC-5139.txt","version":null}],"search_text":"ISO-IEC ISO 3166-2 2020 cited-by-eu-law implementing-regulation nested-reference unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO 32000-1 V2008","type":"specification","body":"ISO-IEC","designation":"ISO 32000-1","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+32000-1","download_urls":["https://www.iso.org/search.html?q=ISO+32000-1"],"folder":"ISO-IEC/ISO-32000-1-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 142-1","folder":"ETSI/EN-319-142-1-V1.2.1","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 102-2","folder":"ETSI/TS-119-102-2-V1.4.1","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf","version":"1.4.1"},{"body":"IETF","designation":"RFC 7995","folder":"IETF/RFC-7995","source":"IETF/RFC-7995/RFC-7995.txt","version":null}],"search_text":"ISO-IEC ISO 32000-1 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO 3279","type":"specification","body":"ISO-IEC","designation":"ISO 3279","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3279","download_urls":["https://www.iso.org/search.html?q=ISO+3279"],"folder":"ISO-IEC/ISO-3279","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null}],"search_text":"ISO-IEC ISO 3279 nested-reference unavailable"},{"id":"ISO-IEC ISO 3297 V1986","type":"specification","body":"ISO-IEC","designation":"ISO 3297","version":"1986","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3297","download_urls":["https://www.iso.org/search.html?q=ISO+3297"],"folder":"ISO-IEC/ISO-3297-V1986","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2288","folder":"IETF/RFC-2288","source":"IETF/RFC-2288/RFC-2288.txt","version":null},{"body":"IETF","designation":"RFC 3044","folder":"IETF/RFC-3044","source":"IETF/RFC-3044/RFC-3044.txt","version":null},{"body":"IETF","designation":"RFC 5741","folder":"IETF/RFC-5741","source":"IETF/RFC-5741/RFC-5741.txt","version":null},{"body":"IETF","designation":"RFC 7322","folder":"IETF/RFC-7322","source":"IETF/RFC-7322/RFC-7322.txt","version":null}],"search_text":"ISO-IEC ISO 3297 1986 nested-reference unavailable"},{"id":"ISO-IEC ISO 3309-1979","type":"specification","body":"ISO-IEC","designation":"ISO 3309-1979","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3309-1979","download_urls":["https://www.iso.org/search.html?q=ISO+3309-1979"],"folder":"ISO-IEC/ISO-3309-1979","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1331","folder":"IETF/RFC-1331","source":"IETF/RFC-1331/RFC-1331.txt","version":null},{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null}],"search_text":"ISO-IEC ISO 3309-1979 nested-reference unavailable"},{"id":"ISO-IEC ISO 3309-1991","type":"specification","body":"ISO-IEC","designation":"ISO 3309-1991","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3309-1991","download_urls":["https://www.iso.org/search.html?q=ISO+3309-1991"],"folder":"ISO-IEC/ISO-3309-1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1549","folder":"IETF/RFC-1549","source":"IETF/RFC-1549/RFC-1549.txt","version":null}],"search_text":"ISO-IEC ISO 3309-1991 nested-reference unavailable"},{"id":"ISO-IEC ISO 3309 V1984","type":"specification","body":"ISO-IEC","designation":"ISO 3309","version":"1984","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+3309","download_urls":["https://www.iso.org/search.html?q=ISO+3309"],"folder":"ISO-IEC/ISO-3309-V1984","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1172","folder":"IETF/RFC-1172","source":"IETF/RFC-1172/RFC-1172.txt","version":null},{"body":"IETF","designation":"RFC 1331","folder":"IETF/RFC-1331","source":"IETF/RFC-1331/RFC-1331.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1510","folder":"IETF/RFC-1510","source":"IETF/RFC-1510/RFC-1510.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1548","folder":"IETF/RFC-1548","source":"IETF/RFC-1548/RFC-1548.txt","version":null},{"body":"IETF","designation":"RFC 1549","folder":"IETF/RFC-1549","source":"IETF/RFC-1549/RFC-1549.txt","version":null},{"body":"IETF","designation":"RFC 1598","folder":"IETF/RFC-1598","source":"IETF/RFC-1598/RFC-1598.txt","version":null},{"body":"IETF","designation":"RFC 1661","folder":"IETF/RFC-1661","source":"IETF/RFC-1661/RFC-1661.txt","version":null},{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null},{"body":"IETF","designation":"RFC 1663","folder":"IETF/RFC-1663","source":"IETF/RFC-1663/RFC-1663.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1952","folder":"IETF/RFC-1952","source":"IETF/RFC-1952/RFC-1952.txt","version":null},{"body":"IETF","designation":"RFC 1973","folder":"IETF/RFC-1973","source":"IETF/RFC-1973/RFC-1973.txt","version":null},{"body":"IETF","designation":"RFC 2171","folder":"IETF/RFC-2171","source":"IETF/RFC-2171/RFC-2171.txt","version":null},{"body":"IETF","designation":"RFC 2172","folder":"IETF/RFC-2172","source":"IETF/RFC-2172/RFC-2172.txt","version":null},{"body":"IETF","designation":"RFC 2175","folder":"IETF/RFC-2175","source":"IETF/RFC-2175/RFC-2175.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2512","folder":"IETF/RFC-2512","source":"IETF/RFC-2512/RFC-2512.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 3961","folder":"IETF/RFC-3961","source":"IETF/RFC-3961/RFC-3961.txt","version":null},{"body":"IETF","designation":"RFC 6063","folder":"IETF/RFC-6063","source":"IETF/RFC-6063/RFC-6063.txt","version":null},{"body":"IETF","designation":"RFC 6388","folder":"IETF/RFC-6388","source":"IETF/RFC-6388/RFC-6388.txt","version":null}],"search_text":"ISO-IEC ISO 3309 1984 nested-reference unavailable"},{"id":"ISO-IEC ISO 39794","type":"specification","body":"ISO-IEC","designation":"ISO 39794","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+39794","download_urls":["https://www.iso.org/search.html?q=ISO+39794"],"folder":"ISO-IEC/ISO-39794","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 39794 cited-by-eu-law implementing-regulation unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977"},{"id":"ISO-IEC ISO 4217 V2015","type":"specification","body":"ISO-IEC","designation":"ISO 4217","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+4217","download_urls":["https://www.iso.org/search.html?q=ISO+4217"],"folder":"ISO-IEC/ISO-4217-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.6.0","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","version":"2.6.0"},{"body":"IETF","designation":"RFC 1476","folder":"IETF/RFC-1476","source":"IETF/RFC-1476/RFC-1476.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null}],"search_text":"ISO-IEC ISO 4217 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO 4335","type":"specification","body":"ISO-IEC","designation":"ISO 4335","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+4335","download_urls":["https://www.iso.org/search.html?q=ISO+4335"],"folder":"ISO-IEC/ISO-4335","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1331","folder":"IETF/RFC-1331","source":"IETF/RFC-1331/RFC-1331.txt","version":null},{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null},{"body":"IETF","designation":"RFC 1549","folder":"IETF/RFC-1549","source":"IETF/RFC-1549/RFC-1549.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null}],"search_text":"ISO-IEC ISO 4335 nested-reference unavailable"},{"id":"ISO-IEC ISO 4335-1979","type":"specification","body":"ISO-IEC","designation":"ISO 4335-1979","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+4335-1979","download_urls":["https://www.iso.org/search.html?q=ISO+4335-1979"],"folder":"ISO-IEC/ISO-4335-1979","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1134","folder":"IETF/RFC-1134","source":"IETF/RFC-1134/RFC-1134.txt","version":null},{"body":"IETF","designation":"RFC 1171","folder":"IETF/RFC-1171","source":"IETF/RFC-1171/RFC-1171.txt","version":null},{"body":"IETF","designation":"RFC 1331","folder":"IETF/RFC-1331","source":"IETF/RFC-1331/RFC-1331.txt","version":null},{"body":"IETF","designation":"RFC 1549","folder":"IETF/RFC-1549","source":"IETF/RFC-1549/RFC-1549.txt","version":null},{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null}],"search_text":"ISO-IEC ISO 4335-1979 nested-reference unavailable"},{"id":"ISO-IEC ISO 4873","type":"specification","body":"ISO-IEC","designation":"ISO 4873","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+4873","download_urls":["https://www.iso.org/search.html?q=ISO+4873"],"folder":"ISO-IEC/ISO-4873","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null}],"search_text":"ISO-IEC ISO 4873 nested-reference unavailable"},{"id":"ISO-IEC ISO 5-7","type":"specification","body":"ISO-IEC","designation":"ISO 5-7","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+5-7","download_urls":["https://www.iso.org/search.html?q=ISO+5-7"],"folder":"ISO-IEC/ISO-5-7","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 928","folder":"IETF/RFC-928","source":"IETF/RFC-928/RFC-928.txt","version":null}],"search_text":"ISO-IEC ISO 5-7 nested-reference unavailable"},{"id":"ISO-IEC ISO 50001 V2011","type":"specification","body":"ISO-IEC","designation":"ISO 50001","version":"2011","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+50001","download_urls":["https://www.iso.org/search.html?q=ISO+50001"],"folder":"ISO-IEC/ISO-50001-V2011","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null}],"search_text":"ISO-IEC ISO 50001 2011 nested-reference unavailable"},{"id":"ISO-IEC ISO 5427","type":"specification","body":"ISO-IEC","designation":"ISO 5427","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+5427","download_urls":["https://www.iso.org/search.html?q=ISO+5427"],"folder":"ISO-IEC/ISO-5427","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1489","folder":"IETF/RFC-1489","source":"IETF/RFC-1489/RFC-1489.txt","version":null}],"search_text":"ISO-IEC ISO 5427 nested-reference unavailable"},{"id":"ISO-IEC ISO 5786","type":"specification","body":"ISO-IEC","designation":"ISO 5786","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+5786","download_urls":["https://www.iso.org/search.html?q=ISO+5786"],"folder":"ISO-IEC/ISO-5786","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"W3C","designation":"vc-data-model","folder":"W3C/vc-data-model-V1.1","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html","version":"1.1"}],"search_text":"ISO-IEC ISO 5786 nested-reference unavailable"},{"id":"ISO-IEC ISO 5817","type":"specification","body":"ISO-IEC","designation":"ISO 5817","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+5817","download_urls":["https://www.iso.org/search.html?q=ISO+5817"],"folder":"ISO-IEC/ISO-5817","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 5817 nested-reference unavailable"},{"id":"ISO-IEC ISO 6093","type":"specification","body":"ISO-IEC","designation":"ISO 6093","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6093","download_urls":["https://www.iso.org/search.html?q=ISO+6093"],"folder":"ISO-IEC/ISO-6093","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null}],"search_text":"ISO-IEC ISO 6093 nested-reference unavailable"},{"id":"ISO-IEC ISO 6256","type":"specification","body":"ISO-IEC","designation":"ISO 6256","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6256","download_urls":["https://www.iso.org/search.html?q=ISO+6256"],"folder":"ISO-IEC/ISO-6256","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1547","folder":"IETF/RFC-1547","source":"IETF/RFC-1547/RFC-1547.txt","version":null}],"search_text":"ISO-IEC ISO 6256 nested-reference unavailable"},{"id":"ISO-IEC ISO 639","type":"specification","body":"ISO-IEC","designation":"ISO 639","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+639","download_urls":["https://www.iso.org/search.html?q=ISO+639"],"folder":"ISO-IEC/ISO-639","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 639 cited-by-eu-law implementing-regulation unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO 639-1 V2002","type":"specification","body":"ISO-IEC","designation":"ISO 639-1","version":"2002","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+639-1","download_urls":["https://www.iso.org/search.html?q=ISO+639-1"],"folder":"ISO-IEC/ISO-639-1-V2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.6.0","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","version":"2.6.0"},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 4240","folder":"IETF/RFC-4240","source":"IETF/RFC-4240/RFC-4240.txt","version":null},{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO 639-1 2002 nested-reference unavailable"},{"id":"ISO-IEC ISO 639-2 V1998","type":"specification","body":"ISO-IEC","designation":"ISO 639-2","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+639-2","download_urls":["https://www.iso.org/search.html?q=ISO+639-2"],"folder":"ISO-IEC/ISO-639-2-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2731","folder":"IETF/RFC-2731","source":"IETF/RFC-2731/RFC-2731.txt","version":null},{"body":"IETF","designation":"RFC 3066","folder":"IETF/RFC-3066","source":"IETF/RFC-3066/RFC-3066.txt","version":null},{"body":"IETF","designation":"RFC 3282","folder":"IETF/RFC-3282","source":"IETF/RFC-3282/RFC-3282.txt","version":null},{"body":"IETF","designation":"RFC 4645","folder":"IETF/RFC-4645","source":"IETF/RFC-4645/RFC-4645.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 6856","folder":"IETF/RFC-6856","source":"IETF/RFC-6856/RFC-6856.txt","version":null}],"search_text":"ISO-IEC ISO 639-2 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO 639-3 V2007","type":"specification","body":"ISO-IEC","designation":"ISO 639-3","version":"2007","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+639-3","download_urls":["https://www.iso.org/search.html?q=ISO+639-3"],"folder":"ISO-IEC/ISO-639-3-V2007","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null}],"search_text":"ISO-IEC ISO 639-3 2007 nested-reference unavailable"},{"id":"ISO-IEC ISO 639-5 V2008","type":"specification","body":"ISO-IEC","designation":"ISO 639-5","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+639-5","download_urls":["https://www.iso.org/search.html?q=ISO+639-5"],"folder":"ISO-IEC/ISO-639-5-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5645","folder":"IETF/RFC-5645","source":"IETF/RFC-5645/RFC-5645.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null}],"search_text":"ISO-IEC ISO 639-5 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO 6429 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 6429","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6429","download_urls":["https://www.iso.org/search.html?q=ISO+6429"],"folder":"ISO-IEC/ISO-6429-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO 6429 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 646 V1991","type":"specification","body":"ISO-IEC","designation":"ISO 646","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+646","download_urls":["https://www.iso.org/search.html?q=ISO+646"],"folder":"ISO-IEC/ISO-646-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2045","folder":"IETF/RFC-2045","source":"IETF/RFC-2045/RFC-2045.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2204","folder":"IETF/RFC-2204","source":"IETF/RFC-2204/RFC-2204.txt","version":null},{"body":"IETF","designation":"RFC 3367","folder":"IETF/RFC-3367","source":"IETF/RFC-3367/RFC-3367.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 5198","folder":"IETF/RFC-5198","source":"IETF/RFC-5198/RFC-5198.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null}],"search_text":"ISO-IEC ISO 646 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO 6523","type":"specification","body":"ISO-IEC","designation":"ISO 6523","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6523","download_urls":["https://www.iso.org/search.html?q=ISO+6523"],"folder":"ISO-IEC/ISO-6523","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2204","folder":"IETF/RFC-2204","source":"IETF/RFC-2204/RFC-2204.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null},{"body":"IETF","designation":"RFC 982","folder":"IETF/RFC-982","source":"IETF/RFC-982/RFC-982.txt","version":null}],"search_text":"ISO-IEC ISO 6523 nested-reference unavailable"},{"id":"ISO-IEC ISO 6709","type":"specification","body":"ISO-IEC","designation":"ISO 6709","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6709","download_urls":["https://www.iso.org/search.html?q=ISO+6709"],"folder":"ISO-IEC/ISO-6709","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5870","folder":"IETF/RFC-5870","source":"IETF/RFC-5870/RFC-5870.txt","version":null}],"search_text":"ISO-IEC ISO 6709 nested-reference unavailable"},{"id":"ISO-IEC ISO 6937","type":"specification","body":"ISO-IEC","designation":"ISO 6937","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6937","download_urls":["https://www.iso.org/search.html?q=ISO+6937"],"folder":"ISO-IEC/ISO-6937","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1489","folder":"IETF/RFC-1489","source":"IETF/RFC-1489/RFC-1489.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null}],"search_text":"ISO-IEC ISO 6937 nested-reference unavailable"},{"id":"ISO-IEC ISO 6937-2 V1983","type":"specification","body":"ISO-IEC","designation":"ISO 6937-2","version":"1983","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+6937-2","download_urls":["https://www.iso.org/search.html?q=ISO+6937-2"],"folder":"ISO-IEC/ISO-6937-2-V1983","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null}],"search_text":"ISO-IEC ISO 6937-2 1983 nested-reference unavailable"},{"id":"ISO-IEC ISO 70-79","type":"specification","body":"ISO-IEC","designation":"ISO 70-79","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+70-79","download_urls":["https://www.iso.org/search.html?q=ISO+70-79"],"folder":"ISO-IEC/ISO-70-79","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null}],"search_text":"ISO-IEC ISO 70-79 nested-reference unavailable"},{"id":"ISO-IEC ISO 7098","type":"specification","body":"ISO-IEC","designation":"ISO 7098","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7098","download_urls":["https://www.iso.org/search.html?q=ISO+7098"],"folder":"ISO-IEC/ISO-7098","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null}],"search_text":"ISO-IEC ISO 7098 nested-reference unavailable"},{"id":"ISO-IEC ISO 7489","type":"specification","body":"ISO-IEC","designation":"ISO 7489","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7489","download_urls":["https://www.iso.org/search.html?q=ISO+7489"],"folder":"ISO-IEC/ISO-7489","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1716","folder":"IETF/RFC-1716","source":"IETF/RFC-1716/RFC-1716.txt","version":null},{"body":"IETF","designation":"RFC 1812","folder":"IETF/RFC-1812","source":"IETF/RFC-1812/RFC-1812.txt","version":null}],"search_text":"ISO-IEC ISO 7489 nested-reference unavailable"},{"id":"ISO-IEC ISO 7498-2","type":"specification","body":"ISO-IEC","designation":"ISO 7498-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7498-2","download_urls":["https://www.iso.org/search.html?q=ISO+7498-2"],"folder":"ISO-IEC/ISO-7498-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 1124","folder":"IETF/RFC-1124","source":"IETF/RFC-1124/RFC-1124.pdf","version":null},{"body":"IETF","designation":"RFC 1272","folder":"IETF/RFC-1272","source":"IETF/RFC-1272/RFC-1272.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO 7498-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 7498-2-1988","type":"specification","body":"ISO-IEC","designation":"ISO 7498-2-1988","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7498-2-1988","download_urls":["https://www.iso.org/search.html?q=ISO+7498-2-1988"],"folder":"ISO-IEC/ISO-7498-2-1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1508","folder":"IETF/RFC-1508","source":"IETF/RFC-1508/RFC-1508.txt","version":null},{"body":"IETF","designation":"RFC 2078","folder":"IETF/RFC-2078","source":"IETF/RFC-2078/RFC-2078.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null}],"search_text":"ISO-IEC ISO 7498-2-1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 7498-3 V1989","type":"specification","body":"ISO-IEC","designation":"ISO 7498-3","version":"1989","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7498-3","download_urls":["https://www.iso.org/search.html?q=ISO+7498-3"],"folder":"ISO-IEC/ISO-7498-3-V1989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null}],"search_text":"ISO-IEC ISO 7498-3 1989 nested-reference unavailable"},{"id":"ISO-IEC ISO 7498-4 V1989","type":"specification","body":"ISO-IEC","designation":"ISO 7498-4","version":"1989","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7498-4","download_urls":["https://www.iso.org/search.html?q=ISO+7498-4"],"folder":"ISO-IEC/ISO-7498-4-V1989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1272","folder":"IETF/RFC-1272","source":"IETF/RFC-1272/RFC-1272.txt","version":null},{"body":"IETF","designation":"RFC 2063","folder":"IETF/RFC-2063","source":"IETF/RFC-2063/RFC-2063.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null}],"search_text":"ISO-IEC ISO 7498-4 1989 nested-reference unavailable"},{"id":"ISO-IEC ISO 7498 V1984","type":"specification","body":"ISO-IEC","designation":"ISO 7498","version":"1984","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7498","download_urls":["https://www.iso.org/search.html?q=ISO+7498"],"folder":"ISO-IEC/ISO-7498-V1984","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 0989","folder":"IETF/RFC-0989","source":"IETF/RFC-0989/RFC-0989.txt","version":null},{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1040","folder":"IETF/RFC-1040","source":"IETF/RFC-1040/RFC-1040.txt","version":null},{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1113","folder":"IETF/RFC-1113","source":"IETF/RFC-1113/RFC-1113.txt","version":null},{"body":"IETF","designation":"RFC 1136","folder":"IETF/RFC-1136","source":"IETF/RFC-1136/RFC-1136.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1272","folder":"IETF/RFC-1272","source":"IETF/RFC-1272/RFC-1272.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 2094","folder":"IETF/RFC-2094","source":"IETF/RFC-2094/RFC-2094.txt","version":null},{"body":"IETF","designation":"RFC 892","folder":"IETF/RFC-892","source":"IETF/RFC-892/RFC-892.txt","version":null},{"body":"IETF","designation":"RFC 905","folder":"IETF/RFC-905","source":"IETF/RFC-905/RFC-905.txt","version":null},{"body":"IETF","designation":"RFC 926","folder":"IETF/RFC-926","source":"IETF/RFC-926/RFC-926.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null},{"body":"IETF","designation":"RFC 982","folder":"IETF/RFC-982","source":"IETF/RFC-982/RFC-982.txt","version":null},{"body":"IETF","designation":"RFC 989","folder":"IETF/RFC-989","source":"IETF/RFC-989/RFC-989.txt","version":null},{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null},{"body":"IETF","designation":"RFC 995","folder":"IETF/RFC-995","source":"IETF/RFC-995/RFC-995.txt","version":null}],"search_text":"ISO-IEC ISO 7498 1984 nested-reference unavailable"},{"id":"ISO-IEC ISO 7776","type":"specification","body":"ISO-IEC","designation":"ISO 7776","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7776","download_urls":["https://www.iso.org/search.html?q=ISO+7776"],"folder":"ISO-IEC/ISO-7776","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null},{"body":"IETF","designation":"RFC 1553","folder":"IETF/RFC-1553","source":"IETF/RFC-1553/RFC-1553.txt","version":null},{"body":"IETF","designation":"RFC 1663","folder":"IETF/RFC-1663","source":"IETF/RFC-1663/RFC-1663.txt","version":null},{"body":"IETF","designation":"RFC 1717","folder":"IETF/RFC-1717","source":"IETF/RFC-1717/RFC-1717.txt","version":null},{"body":"IETF","designation":"RFC 1990","folder":"IETF/RFC-1990","source":"IETF/RFC-1990/RFC-1990.txt","version":null},{"body":"IETF","designation":"RFC 3366","folder":"IETF/RFC-3366","source":"IETF/RFC-3366/RFC-3366.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null}],"search_text":"ISO-IEC ISO 7776 nested-reference unavailable"},{"id":"ISO-IEC ISO 7812-1985","type":"specification","body":"ISO-IEC","designation":"ISO 7812-1985","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+7812-1985","download_urls":["https://www.iso.org/search.html?q=ISO+7812-1985"],"folder":"ISO-IEC/ISO-7812-1985","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 7812-1985 nested-reference unavailable"},{"id":"ISO-IEC ISO 80000-5","type":"specification","body":"ISO-IEC","designation":"ISO 80000-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+80000-5","download_urls":["https://www.iso.org/search.html?q=ISO+80000-5"],"folder":"ISO-IEC/ISO-80000-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null}],"search_text":"ISO-IEC ISO 80000-5 nested-reference unavailable"},{"id":"ISO-IEC ISO 802","type":"specification","body":"ISO-IEC","designation":"ISO 802","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+802","download_urls":["https://www.iso.org/search.html?q=ISO+802"],"folder":"ISO-IEC/ISO-802","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 802 nested-reference unavailable"},{"id":"ISO-IEC ISO 8023","type":"specification","body":"ISO-IEC","designation":"ISO 8023","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8023","download_urls":["https://www.iso.org/search.html?q=ISO+8023"],"folder":"ISO-IEC/ISO-8023","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null}],"search_text":"ISO-IEC ISO 8023 nested-reference unavailable"},{"id":"ISO-IEC ISO 8072","type":"specification","body":"ISO-IEC","designation":"ISO 8072","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8072","download_urls":["https://www.iso.org/search.html?q=ISO+8072"],"folder":"ISO-IEC/ISO-8072","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 905","folder":"IETF/RFC-905","source":"IETF/RFC-905/RFC-905.txt","version":null}],"search_text":"ISO-IEC ISO 8072 nested-reference unavailable"},{"id":"ISO-IEC ISO 8073 V1992","type":"specification","body":"ISO-IEC","designation":"ISO 8073","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8073","download_urls":["https://www.iso.org/search.html?q=ISO+8073"],"folder":"ISO-IEC/ISO-8073-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null},{"body":"IETF","designation":"RFC 1950","folder":"IETF/RFC-1950","source":"IETF/RFC-1950/RFC-1950.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null}],"search_text":"ISO-IEC ISO 8073 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO 8206","type":"specification","body":"ISO-IEC","designation":"ISO 8206","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8206","download_urls":["https://www.iso.org/search.html?q=ISO+8206"],"folder":"ISO-IEC/ISO-8206","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null}],"search_text":"ISO-IEC ISO 8206 nested-reference unavailable"},{"id":"ISO-IEC ISO 8208 V1984","type":"specification","body":"ISO-IEC","designation":"ISO 8208","version":"1984","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8208","download_urls":["https://www.iso.org/search.html?q=ISO+8208"],"folder":"ISO-IEC/ISO-8208-V1984","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 995","folder":"IETF/RFC-995","source":"IETF/RFC-995/RFC-995.txt","version":null}],"search_text":"ISO-IEC ISO 8208 1984 nested-reference unavailable"},{"id":"ISO-IEC ISO 8326","type":"specification","body":"ISO-IEC","designation":"ISO 8326","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8326","download_urls":["https://www.iso.org/search.html?q=ISO+8326"],"folder":"ISO-IEC/ISO-8326","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8326 nested-reference unavailable"},{"id":"ISO-IEC ISO 8327","type":"specification","body":"ISO-IEC","designation":"ISO 8327","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8327","download_urls":["https://www.iso.org/search.html?q=ISO+8327"],"folder":"ISO-IEC/ISO-8327","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1006","folder":"IETF/RFC-1006","source":"IETF/RFC-1006/RFC-1006.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1859","folder":"IETF/RFC-1859","source":"IETF/RFC-1859/RFC-1859.txt","version":null}],"search_text":"ISO-IEC ISO 8327 nested-reference unavailable"},{"id":"ISO-IEC ISO 8348 V1987","type":"specification","body":"ISO-IEC","designation":"ISO 8348","version":"1987","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8348","download_urls":["https://www.iso.org/search.html?q=ISO+8348"],"folder":"ISO-IEC/ISO-8348-V1987","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1011","folder":"IETF/RFC-1011","source":"IETF/RFC-1011/RFC-1011.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1277","folder":"IETF/RFC-1277","source":"IETF/RFC-1277/RFC-1277.txt","version":null},{"body":"IETF","designation":"RFC 1278","folder":"IETF/RFC-1278","source":"IETF/RFC-1278/RFC-1278.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1637","folder":"IETF/RFC-1637","source":"IETF/RFC-1637/RFC-1637.txt","version":null},{"body":"IETF","designation":"RFC 1706","folder":"IETF/RFC-1706","source":"IETF/RFC-1706/RFC-1706.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 2126","folder":"IETF/RFC-2126","source":"IETF/RFC-2126/RFC-2126.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null},{"body":"IETF","designation":"RFC 926","folder":"IETF/RFC-926","source":"IETF/RFC-926/RFC-926.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null},{"body":"IETF","designation":"RFC 982","folder":"IETF/RFC-982","source":"IETF/RFC-982/RFC-982.txt","version":null},{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null},{"body":"IETF","designation":"RFC 995","folder":"IETF/RFC-995","source":"IETF/RFC-995/RFC-995.txt","version":null}],"search_text":"ISO-IEC ISO 8348 1987 nested-reference unavailable"},{"id":"ISO-IEC ISO 8372","type":"specification","body":"ISO-IEC","designation":"ISO 8372","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8372","download_urls":["https://www.iso.org/search.html?q=ISO+8372"],"folder":"ISO-IEC/ISO-8372","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null}],"search_text":"ISO-IEC ISO 8372 nested-reference unavailable"},{"id":"ISO-IEC ISO 838","type":"specification","body":"ISO-IEC","designation":"ISO 838","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+838","download_urls":["https://www.iso.org/search.html?q=ISO+838"],"folder":"ISO-IEC/ISO-838","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2346","folder":"IETF/RFC-2346","source":"IETF/RFC-2346/RFC-2346.txt","version":null}],"search_text":"ISO-IEC ISO 838 nested-reference unavailable"},{"id":"ISO-IEC ISO 8473-1","type":"specification","body":"ISO-IEC","designation":"ISO 8473-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8473-1","download_urls":["https://www.iso.org/search.html?q=ISO+8473-1"],"folder":"ISO-IEC/ISO-8473-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null}],"search_text":"ISO-IEC ISO 8473-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 8473-1993","type":"specification","body":"ISO-IEC","designation":"ISO 8473-1993","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8473-1993","download_urls":["https://www.iso.org/search.html?q=ISO+8473-1993"],"folder":"ISO-IEC/ISO-8473-1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1575","folder":"IETF/RFC-1575","source":"IETF/RFC-1575/RFC-1575.txt","version":null}],"search_text":"ISO-IEC ISO 8473-1993 nested-reference unavailable"},{"id":"ISO-IEC ISO 8473 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 8473","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8473","download_urls":["https://www.iso.org/search.html?q=ISO+8473"],"folder":"ISO-IEC/ISO-8473-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null},{"body":"IETF","designation":"RFC 1009","folder":"IETF/RFC-1009","source":"IETF/RFC-1009/RFC-1009.txt","version":null},{"body":"IETF","designation":"RFC 1070","folder":"IETF/RFC-1070","source":"IETF/RFC-1070/RFC-1070.txt","version":null},{"body":"IETF","designation":"RFC 1139","folder":"IETF/RFC-1139","source":"IETF/RFC-1139/RFC-1139.txt","version":null},{"body":"IETF","designation":"RFC 1140","folder":"IETF/RFC-1140","source":"IETF/RFC-1140/RFC-1140.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1169","folder":"IETF/RFC-1169","source":"IETF/RFC-1169/RFC-1169.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1200","folder":"IETF/RFC-1200","source":"IETF/RFC-1200/RFC-1200.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1250","folder":"IETF/RFC-1250","source":"IETF/RFC-1250/RFC-1250.txt","version":null},{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1347","folder":"IETF/RFC-1347","source":"IETF/RFC-1347/RFC-1347.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1454","folder":"IETF/RFC-1454","source":"IETF/RFC-1454/RFC-1454.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1478","folder":"IETF/RFC-1478","source":"IETF/RFC-1478/RFC-1478.txt","version":null},{"body":"IETF","designation":"RFC 1479","folder":"IETF/RFC-1479","source":"IETF/RFC-1479/RFC-1479.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1575","folder":"IETF/RFC-1575","source":"IETF/RFC-1575/RFC-1575.txt","version":null},{"body":"IETF","designation":"RFC 1600","folder":"IETF/RFC-1600","source":"IETF/RFC-1600/RFC-1600.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1654","folder":"IETF/RFC-1654","source":"IETF/RFC-1654/RFC-1654.txt","version":null},{"body":"IETF","designation":"RFC 1745","folder":"IETF/RFC-1745","source":"IETF/RFC-1745/RFC-1745.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 1771","folder":"IETF/RFC-1771","source":"IETF/RFC-1771/RFC-1771.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 2763","folder":"IETF/RFC-2763","source":"IETF/RFC-2763/RFC-2763.txt","version":null},{"body":"IETF","designation":"RFC 2966","folder":"IETF/RFC-2966","source":"IETF/RFC-2966/RFC-2966.txt","version":null},{"body":"IETF","designation":"RFC 3002","folder":"IETF/RFC-3002","source":"IETF/RFC-3002/RFC-3002.txt","version":null},{"body":"IETF","designation":"RFC 3219","folder":"IETF/RFC-3219","source":"IETF/RFC-3219/RFC-3219.txt","version":null},{"body":"IETF","designation":"RFC 3373","folder":"IETF/RFC-3373","source":"IETF/RFC-3373/RFC-3373.txt","version":null},{"body":"IETF","designation":"RFC 3563","folder":"IETF/RFC-3563","source":"IETF/RFC-3563/RFC-3563.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3784","folder":"IETF/RFC-3784","source":"IETF/RFC-3784/RFC-3784.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 3795","folder":"IETF/RFC-3795","source":"IETF/RFC-3795/RFC-3795.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 4271","folder":"IETF/RFC-4271","source":"IETF/RFC-4271/RFC-4271.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 4971","folder":"IETF/RFC-4971","source":"IETF/RFC-4971/RFC-4971.txt","version":null},{"body":"IETF","designation":"RFC 5029","folder":"IETF/RFC-5029","source":"IETF/RFC-5029/RFC-5029.txt","version":null},{"body":"IETF","designation":"RFC 5073","folder":"IETF/RFC-5073","source":"IETF/RFC-5073/RFC-5073.txt","version":null},{"body":"IETF","designation":"RFC 5130","folder":"IETF/RFC-5130","source":"IETF/RFC-5130/RFC-5130.txt","version":null},{"body":"IETF","designation":"RFC 5302","folder":"IETF/RFC-5302","source":"IETF/RFC-5302/RFC-5302.txt","version":null},{"body":"IETF","designation":"RFC 5303","folder":"IETF/RFC-5303","source":"IETF/RFC-5303/RFC-5303.txt","version":null},{"body":"IETF","designation":"RFC 5304","folder":"IETF/RFC-5304","source":"IETF/RFC-5304/RFC-5304.txt","version":null},{"body":"IETF","designation":"RFC 5305","folder":"IETF/RFC-5305","source":"IETF/RFC-5305/RFC-5305.txt","version":null},{"body":"IETF","designation":"RFC 5306","folder":"IETF/RFC-5306","source":"IETF/RFC-5306/RFC-5306.txt","version":null},{"body":"IETF","designation":"RFC 5308","folder":"IETF/RFC-5308","source":"IETF/RFC-5308/RFC-5308.txt","version":null},{"body":"IETF","designation":"RFC 5309","folder":"IETF/RFC-5309","source":"IETF/RFC-5309/RFC-5309.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 6119","folder":"IETF/RFC-6119","source":"IETF/RFC-6119/RFC-6119.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6822","folder":"IETF/RFC-6822","source":"IETF/RFC-6822/RFC-6822.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7175","folder":"IETF/RFC-7175","source":"IETF/RFC-7175/RFC-7175.txt","version":null},{"body":"IETF","designation":"RFC 7176","folder":"IETF/RFC-7176","source":"IETF/RFC-7176/RFC-7176.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7178","folder":"IETF/RFC-7178","source":"IETF/RFC-7178/RFC-7178.txt","version":null},{"body":"IETF","designation":"RFC 7180","folder":"IETF/RFC-7180","source":"IETF/RFC-7180/RFC-7180.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7752","folder":"IETF/RFC-7752","source":"IETF/RFC-7752/RFC-7752.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null},{"body":"IETF","designation":"RFC 7961","folder":"IETF/RFC-7961","source":"IETF/RFC-7961/RFC-7961.txt","version":null},{"body":"IETF","designation":"RFC 926","folder":"IETF/RFC-926","source":"IETF/RFC-926/RFC-926.txt","version":null},{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null},{"body":"IETF","designation":"RFC 995","folder":"IETF/RFC-995","source":"IETF/RFC-995/RFC-995.txt","version":null}],"search_text":"ISO-IEC ISO 8473 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 8509","type":"specification","body":"ISO-IEC","designation":"ISO 8509","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8509","download_urls":["https://www.iso.org/search.html?q=ISO+8509"],"folder":"ISO-IEC/ISO-8509","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 926","folder":"IETF/RFC-926","source":"IETF/RFC-926/RFC-926.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null},{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null}],"search_text":"ISO-IEC ISO 8509 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571","type":"specification","body":"ISO-IEC","designation":"ISO 8571","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571","download_urls":["https://www.iso.org/search.html?q=ISO+8571"],"folder":"ISO-IEC/ISO-8571","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571-1","type":"specification","body":"ISO-IEC","designation":"ISO 8571-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571-1","download_urls":["https://www.iso.org/search.html?q=ISO+8571-1"],"folder":"ISO-IEC/ISO-8571-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571-2","type":"specification","body":"ISO-IEC","designation":"ISO 8571-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571-2","download_urls":["https://www.iso.org/search.html?q=ISO+8571-2"],"folder":"ISO-IEC/ISO-8571-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571-3","type":"specification","body":"ISO-IEC","designation":"ISO 8571-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571-3","download_urls":["https://www.iso.org/search.html?q=ISO+8571-3"],"folder":"ISO-IEC/ISO-8571-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571-4","type":"specification","body":"ISO-IEC","designation":"ISO 8571-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571-4","download_urls":["https://www.iso.org/search.html?q=ISO+8571-4"],"folder":"ISO-IEC/ISO-8571-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 8571-5","type":"specification","body":"ISO-IEC","designation":"ISO 8571-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8571-5","download_urls":["https://www.iso.org/search.html?q=ISO+8571-5"],"folder":"ISO-IEC/ISO-8571-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1415","folder":"IETF/RFC-1415","source":"IETF/RFC-1415/RFC-1415.txt","version":null}],"search_text":"ISO-IEC ISO 8571-5 nested-reference unavailable"},{"id":"ISO-IEC ISO 8601-1","type":"specification","body":"ISO-IEC","designation":"ISO 8601-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8601-1","download_urls":["https://www.iso.org/search.html?q=ISO+8601-1"],"folder":"ISO-IEC/ISO-8601-1","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO 8601-1 cited-by-eu-law implementing-regulation unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO 8601 V2019","type":"specification","body":"ISO-IEC","designation":"ISO 8601","version":"2019","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8601","download_urls":["https://www.iso.org/search.html?q=ISO+8601"],"folder":"ISO-IEC/ISO-8601-V2019","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2413","folder":"IETF/RFC-2413","source":"IETF/RFC-2413/RFC-2413.txt","version":null},{"body":"IETF","designation":"RFC 2421","folder":"IETF/RFC-2421","source":"IETF/RFC-2421/RFC-2421.txt","version":null},{"body":"IETF","designation":"RFC 2425","folder":"IETF/RFC-2425","source":"IETF/RFC-2425/RFC-2425.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 2611","folder":"IETF/RFC-2611","source":"IETF/RFC-2611/RFC-2611.txt","version":null},{"body":"IETF","designation":"RFC 2731","folder":"IETF/RFC-2731","source":"IETF/RFC-2731/RFC-2731.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3085","folder":"IETF/RFC-3085","source":"IETF/RFC-3085/RFC-3085.txt","version":null},{"body":"IETF","designation":"RFC 3164","folder":"IETF/RFC-3164","source":"IETF/RFC-3164/RFC-3164.txt","version":null},{"body":"IETF","designation":"RFC 3339","folder":"IETF/RFC-3339","source":"IETF/RFC-3339/RFC-3339.txt","version":null},{"body":"IETF","designation":"RFC 3406","folder":"IETF/RFC-3406","source":"IETF/RFC-3406/RFC-3406.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 4198","folder":"IETF/RFC-4198","source":"IETF/RFC-4198/RFC-4198.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5013","folder":"IETF/RFC-5013","source":"IETF/RFC-5013/RFC-5013.txt","version":null},{"body":"IETF","designation":"RFC 5070","folder":"IETF/RFC-5070","source":"IETF/RFC-5070/RFC-5070.txt","version":null},{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null},{"body":"IETF","designation":"RFC 6492","folder":"IETF/RFC-6492","source":"IETF/RFC-6492/RFC-6492.txt","version":null},{"body":"IETF","designation":"RFC 6509","folder":"IETF/RFC-6509","source":"IETF/RFC-6509/RFC-6509.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7095","folder":"IETF/RFC-7095","source":"IETF/RFC-7095/RFC-7095.txt","version":null},{"body":"IETF","designation":"RFC 7493","folder":"IETF/RFC-7493","source":"IETF/RFC-7493/RFC-7493.txt","version":null},{"body":"IETF","designation":"RFC 7826","folder":"IETF/RFC-7826","source":"IETF/RFC-7826/RFC-7826.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null}],"search_text":"ISO-IEC ISO 8601 2019 nested-reference unavailable"},{"id":"ISO-IEC ISO 8602","type":"specification","body":"ISO-IEC","designation":"ISO 8602","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8602","download_urls":["https://www.iso.org/search.html?q=ISO+8602"],"folder":"ISO-IEC/ISO-8602","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null},{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null}],"search_text":"ISO-IEC ISO 8602 nested-reference unavailable"},{"id":"ISO-IEC ISO 8613","type":"specification","body":"ISO-IEC","designation":"ISO 8613","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8613","download_urls":["https://www.iso.org/search.html?q=ISO+8613"],"folder":"ISO-IEC/ISO-8613","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1494","folder":"IETF/RFC-1494","source":"IETF/RFC-1494/RFC-1494.txt","version":null}],"search_text":"ISO-IEC ISO 8613 nested-reference unavailable"},{"id":"ISO-IEC ISO 8648 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 8648","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8648","download_urls":["https://www.iso.org/search.html?q=ISO+8648"],"folder":"ISO-IEC/ISO-8648-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1136","folder":"IETF/RFC-1136","source":"IETF/RFC-1136/RFC-1136.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 941","folder":"IETF/RFC-941","source":"IETF/RFC-941/RFC-941.txt","version":null},{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null}],"search_text":"ISO-IEC ISO 8648 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 8649","type":"specification","body":"ISO-IEC","designation":"ISO 8649","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8649","download_urls":["https://www.iso.org/search.html?q=ISO+8649"],"folder":"ISO-IEC/ISO-8649","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8649 nested-reference unavailable"},{"id":"ISO-IEC ISO 8650","type":"specification","body":"ISO-IEC","designation":"ISO 8650","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8650","download_urls":["https://www.iso.org/search.html?q=ISO+8650"],"folder":"ISO-IEC/ISO-8650","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8650 nested-reference unavailable"},{"id":"ISO-IEC ISO 8802-2 V1989","type":"specification","body":"ISO-IEC","designation":"ISO 8802-2","version":"1989","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8802-2","download_urls":["https://www.iso.org/search.html?q=ISO+8802-2"],"folder":"ISO-IEC/ISO-8802-2-V1989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1294","folder":"IETF/RFC-1294","source":"IETF/RFC-1294/RFC-1294.txt","version":null},{"body":"IETF","designation":"RFC 1329","folder":"IETF/RFC-1329","source":"IETF/RFC-1329/RFC-1329.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2625","folder":"IETF/RFC-2625","source":"IETF/RFC-2625/RFC-2625.txt","version":null},{"body":"IETF","designation":"RFC 2834","folder":"IETF/RFC-2834","source":"IETF/RFC-2834/RFC-2834.txt","version":null},{"body":"IETF","designation":"RFC 8519","folder":"IETF/RFC-8519","source":"IETF/RFC-8519/RFC-8519.txt","version":null}],"search_text":"ISO-IEC ISO 8802-2 1989 nested-reference unavailable"},{"id":"ISO-IEC ISO 8802-3","type":"specification","body":"ISO-IEC","designation":"ISO 8802-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8802-3","download_urls":["https://www.iso.org/search.html?q=ISO+8802-3"],"folder":"ISO-IEC/ISO-8802-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1368","folder":"IETF/RFC-1368","source":"IETF/RFC-1368/RFC-1368.txt","version":null},{"body":"IETF","designation":"RFC 1515","folder":"IETF/RFC-1515","source":"IETF/RFC-1515/RFC-1515.txt","version":null},{"body":"IETF","designation":"RFC 1516","folder":"IETF/RFC-1516","source":"IETF/RFC-1516/RFC-1516.txt","version":null},{"body":"IETF","designation":"RFC 2063","folder":"IETF/RFC-2063","source":"IETF/RFC-2063/RFC-2063.txt","version":null},{"body":"IETF","designation":"RFC 2108","folder":"IETF/RFC-2108","source":"IETF/RFC-2108/RFC-2108.txt","version":null},{"body":"IETF","designation":"RFC 2239","folder":"IETF/RFC-2239","source":"IETF/RFC-2239/RFC-2239.txt","version":null},{"body":"IETF","designation":"RFC 2722","folder":"IETF/RFC-2722","source":"IETF/RFC-2722/RFC-2722.txt","version":null}],"search_text":"ISO-IEC ISO 8802-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 8802 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 8802","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8802","download_urls":["https://www.iso.org/search.html?q=ISO+8802"],"folder":"ISO-IEC/ISO-8802-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1490","folder":"IETF/RFC-1490","source":"IETF/RFC-1490/RFC-1490.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1707","folder":"IETF/RFC-1707","source":"IETF/RFC-1707/RFC-1707.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1932","folder":"IETF/RFC-1932","source":"IETF/RFC-1932/RFC-1932.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2381","folder":"IETF/RFC-2381","source":"IETF/RFC-2381/RFC-2381.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 935","folder":"IETF/RFC-935","source":"IETF/RFC-935/RFC-935.txt","version":null}],"search_text":"ISO-IEC ISO 8802 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 88022","type":"specification","body":"ISO-IEC","designation":"ISO 88022","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88022","download_urls":["https://www.iso.org/search.html?q=ISO+88022"],"folder":"ISO-IEC/ISO-88022","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 88022 nested-reference unavailable"},{"id":"ISO-IEC ISO 88023","type":"specification","body":"ISO-IEC","designation":"ISO 88023","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88023","download_urls":["https://www.iso.org/search.html?q=ISO+88023"],"folder":"ISO-IEC/ISO-88023","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1284","folder":"IETF/RFC-1284","source":"IETF/RFC-1284/RFC-1284.txt","version":null},{"body":"IETF","designation":"RFC 1398","folder":"IETF/RFC-1398","source":"IETF/RFC-1398/RFC-1398.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1623","folder":"IETF/RFC-1623","source":"IETF/RFC-1623/RFC-1623.txt","version":null},{"body":"IETF","designation":"RFC 1643","folder":"IETF/RFC-1643","source":"IETF/RFC-1643/RFC-1643.txt","version":null},{"body":"IETF","designation":"RFC 1650","folder":"IETF/RFC-1650","source":"IETF/RFC-1650/RFC-1650.txt","version":null},{"body":"IETF","designation":"RFC 2358","folder":"IETF/RFC-2358","source":"IETF/RFC-2358/RFC-2358.txt","version":null},{"body":"IETF","designation":"RFC 2665","folder":"IETF/RFC-2665","source":"IETF/RFC-2665/RFC-2665.txt","version":null},{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 88023 nested-reference unavailable"},{"id":"ISO-IEC ISO 88024","type":"specification","body":"ISO-IEC","designation":"ISO 88024","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88024","download_urls":["https://www.iso.org/search.html?q=ISO+88024"],"folder":"ISO-IEC/ISO-88024","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1230","folder":"IETF/RFC-1230","source":"IETF/RFC-1230/RFC-1230.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 88024 nested-reference unavailable"},{"id":"ISO-IEC ISO 88025","type":"specification","body":"ISO-IEC","designation":"ISO 88025","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88025","download_urls":["https://www.iso.org/search.html?q=ISO+88025"],"folder":"ISO-IEC/ISO-88025","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1231","folder":"IETF/RFC-1231","source":"IETF/RFC-1231/RFC-1231.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1748","folder":"IETF/RFC-1748","source":"IETF/RFC-1748/RFC-1748.txt","version":null},{"body":"IETF","designation":"RFC 3176","folder":"IETF/RFC-3176","source":"IETF/RFC-3176/RFC-3176.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 88025 nested-reference unavailable"},{"id":"ISO-IEC ISO 88026","type":"specification","body":"ISO-IEC","designation":"ISO 88026","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88026","download_urls":["https://www.iso.org/search.html?q=ISO+88026"],"folder":"ISO-IEC/ISO-88026","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1066","folder":"IETF/RFC-1066","source":"IETF/RFC-1066/RFC-1066.txt","version":null},{"body":"IETF","designation":"RFC 1156","folder":"IETF/RFC-1156","source":"IETF/RFC-1156/RFC-1156.txt","version":null},{"body":"IETF","designation":"RFC 1158","folder":"IETF/RFC-1158","source":"IETF/RFC-1158/RFC-1158.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1573","folder":"IETF/RFC-1573","source":"IETF/RFC-1573/RFC-1573.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ISO-IEC ISO 88026 nested-reference unavailable"},{"id":"ISO-IEC ISO 88032","type":"specification","body":"ISO-IEC","designation":"ISO 88032","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88032","download_urls":["https://www.iso.org/search.html?q=ISO+88032"],"folder":"ISO-IEC/ISO-88032","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3635","folder":"IETF/RFC-3635","source":"IETF/RFC-3635/RFC-3635.txt","version":null}],"search_text":"ISO-IEC ISO 88032 nested-reference unavailable"},{"id":"ISO-IEC ISO 8807-1990","type":"specification","body":"ISO-IEC","designation":"ISO 8807-1990","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8807-1990","download_urls":["https://www.iso.org/search.html?q=ISO+8807-1990"],"folder":"ISO-IEC/ISO-8807-1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 8807-1990 nested-reference unavailable"},{"id":"ISO-IEC ISO 8822","type":"specification","body":"ISO-IEC","designation":"ISO 8822","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8822","download_urls":["https://www.iso.org/search.html?q=ISO+8822"],"folder":"ISO-IEC/ISO-8822","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8822 nested-reference unavailable"},{"id":"ISO-IEC ISO 8823","type":"specification","body":"ISO-IEC","designation":"ISO 8823","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8823","download_urls":["https://www.iso.org/search.html?q=ISO+8823"],"folder":"ISO-IEC/ISO-8823","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1683","folder":"IETF/RFC-1683","source":"IETF/RFC-1683/RFC-1683.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8823 nested-reference unavailable"},{"id":"ISO-IEC ISO 8824","type":"specification","body":"ISO-IEC","designation":"ISO 8824","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8824","download_urls":["https://www.iso.org/search.html?q=ISO+8824"],"folder":"ISO-IEC/ISO-8824","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2257","folder":"IETF/RFC-2257","source":"IETF/RFC-2257/RFC-2257.txt","version":null},{"body":"IETF","designation":"RFC 2741","folder":"IETF/RFC-2741","source":"IETF/RFC-2741/RFC-2741.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 8824 nested-reference unavailable"},{"id":"ISO-IEC ISO 8824-1","type":"specification","body":"ISO-IEC","designation":"ISO 8824-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8824-1","download_urls":["https://www.iso.org/search.html?q=ISO+8824-1"],"folder":"ISO-IEC/ISO-8824-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"ISO-IEC ISO 8824-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 8824-2","type":"specification","body":"ISO-IEC","designation":"ISO 8824-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8824-2","download_urls":["https://www.iso.org/search.html?q=ISO+8824-2"],"folder":"ISO-IEC/ISO-8824-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"ISO-IEC ISO 8824-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 8824-3","type":"specification","body":"ISO-IEC","designation":"ISO 8824-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8824-3","download_urls":["https://www.iso.org/search.html?q=ISO+8824-3"],"folder":"ISO-IEC/ISO-8824-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"ISO-IEC ISO 8824-3 nested-reference unavailable"},{"id":"ISO-IEC ISO 8824-4","type":"specification","body":"ISO-IEC","designation":"ISO 8824-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8824-4","download_urls":["https://www.iso.org/search.html?q=ISO+8824-4"],"folder":"ISO-IEC/ISO-8824-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null}],"search_text":"ISO-IEC ISO 8824-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 8825","type":"specification","body":"ISO-IEC","designation":"ISO 8825","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8825","download_urls":["https://www.iso.org/search.html?q=ISO+8825"],"folder":"ISO-IEC/ISO-8825","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null},{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO 8825 nested-reference unavailable"},{"id":"ISO-IEC ISO 8825-1","type":"specification","body":"ISO-IEC","designation":"ISO 8825-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8825-1","download_urls":["https://www.iso.org/search.html?q=ISO+8825-1"],"folder":"ISO-IEC/ISO-8825-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"ISO-IEC ISO 8825-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 8831","type":"specification","body":"ISO-IEC","designation":"ISO 8831","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8831","download_urls":["https://www.iso.org/search.html?q=ISO+8831"],"folder":"ISO-IEC/ISO-8831","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 983","folder":"IETF/RFC-983","source":"IETF/RFC-983/RFC-983.txt","version":null}],"search_text":"ISO-IEC ISO 8831 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-1 V1998","type":"specification","body":"ISO-IEC","designation":"ISO 8859-1","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-1","download_urls":["https://www.iso.org/search.html?q=ISO+8859-1"],"folder":"ISO-IEC/ISO-8859-1-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS01","folder":"ARF/TS01-V1.2","source":"ARF/TS01-V1.2/TS01-V1.2.md","version":"1.2"},{"body":"IETF","designation":"RFC 1154","folder":"IETF/RFC-1154","source":"IETF/RFC-1154/RFC-1154.txt","version":null},{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.pdf","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 1952","folder":"IETF/RFC-1952","source":"IETF/RFC-1952/RFC-1952.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2326","folder":"IETF/RFC-2326","source":"IETF/RFC-2326/RFC-2326.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2543","folder":"IETF/RFC-2543","source":"IETF/RFC-2543/RFC-2543.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2756","folder":"IETF/RFC-2756","source":"IETF/RFC-2756/RFC-2756.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3261","folder":"IETF/RFC-3261","source":"IETF/RFC-3261/RFC-3261.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3494","folder":"IETF/RFC-3494","source":"IETF/RFC-3494/RFC-3494.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4013","folder":"IETF/RFC-4013","source":"IETF/RFC-4013/RFC-4013.txt","version":null},{"body":"IETF","designation":"RFC 4252","folder":"IETF/RFC-4252","source":"IETF/RFC-4252/RFC-4252.txt","version":null},{"body":"IETF","designation":"RFC 4256","folder":"IETF/RFC-4256","source":"IETF/RFC-4256/RFC-4256.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4463","folder":"IETF/RFC-4463","source":"IETF/RFC-4463/RFC-4463.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4630","folder":"IETF/RFC-4630","source":"IETF/RFC-4630/RFC-4630.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6787","folder":"IETF/RFC-6787","source":"IETF/RFC-6787/RFC-6787.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"ISO-IEC ISO 8859-1 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-10 V1992","type":"specification","body":"ISO-IEC","designation":"ISO 8859-10","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-10","download_urls":["https://www.iso.org/search.html?q=ISO+8859-10"],"folder":"ISO-IEC/ISO-8859-10-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"ISO-IEC ISO 8859-10 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-2 V1999","type":"specification","body":"ISO-IEC","designation":"ISO 8859-2","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-2","download_urls":["https://www.iso.org/search.html?q=ISO+8859-2"],"folder":"ISO-IEC/ISO-8859-2-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-2 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-3 V1999","type":"specification","body":"ISO-IEC","designation":"ISO 8859-3","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-3","download_urls":["https://www.iso.org/search.html?q=ISO+8859-3"],"folder":"ISO-IEC/ISO-8859-3-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-3 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-4 V1998","type":"specification","body":"ISO-IEC","designation":"ISO 8859-4","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-4","download_urls":["https://www.iso.org/search.html?q=ISO+8859-4"],"folder":"ISO-IEC/ISO-8859-4-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-4 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-5 V1999","type":"specification","body":"ISO-IEC","designation":"ISO 8859-5","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-5","download_urls":["https://www.iso.org/search.html?q=ISO+8859-5"],"folder":"ISO-IEC/ISO-8859-5-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1896","folder":"IETF/RFC-1896","source":"IETF/RFC-1896/RFC-1896.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO 8859-5 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-6 V1999","type":"specification","body":"ISO-IEC","designation":"ISO 8859-6","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-6","download_urls":["https://www.iso.org/search.html?q=ISO+8859-6"],"folder":"ISO-IEC/ISO-8859-6-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-6 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-7 V1987","type":"specification","body":"ISO-IEC","designation":"ISO 8859-7","version":"1987","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-7","download_urls":["https://www.iso.org/search.html?q=ISO+8859-7"],"folder":"ISO-IEC/ISO-8859-7-V1987","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1554","folder":"IETF/RFC-1554","source":"IETF/RFC-1554/RFC-1554.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-7 1987 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-8-1988","type":"specification","body":"ISO-IEC","designation":"ISO 8859-8-1988","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-8-1988","download_urls":["https://www.iso.org/search.html?q=ISO+8859-8-1988"],"folder":"ISO-IEC/ISO-8859-8-1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null}],"search_text":"ISO-IEC ISO 8859-8-1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-8 V1999","type":"specification","body":"ISO-IEC","designation":"ISO 8859-8","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-8","download_urls":["https://www.iso.org/search.html?q=ISO+8859-8"],"folder":"ISO-IEC/ISO-8859-8-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1555","folder":"IETF/RFC-1555","source":"IETF/RFC-1555/RFC-1555.txt","version":null},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1896","folder":"IETF/RFC-1896","source":"IETF/RFC-1896/RFC-1896.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null}],"search_text":"ISO-IEC ISO 8859-8 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859-9","type":"specification","body":"ISO-IEC","designation":"ISO 8859-9","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859-9","download_urls":["https://www.iso.org/search.html?q=ISO+8859-9"],"folder":"ISO-IEC/ISO-8859-9","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.txt","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1945","folder":"IETF/RFC-1945","source":"IETF/RFC-1945/RFC-1945.txt","version":null},{"body":"IETF","designation":"RFC 2068","folder":"IETF/RFC-2068","source":"IETF/RFC-2068/RFC-2068.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null}],"search_text":"ISO-IEC ISO 8859-9 nested-reference unavailable"},{"id":"ISO-IEC ISO 8859 V1987","type":"specification","body":"ISO-IEC","designation":"ISO 8859","version":"1987","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8859","download_urls":["https://www.iso.org/search.html?q=ISO+8859"],"folder":"ISO-IEC/ISO-8859-V1987","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1312","folder":"IETF/RFC-1312","source":"IETF/RFC-1312/RFC-1312.txt","version":null},{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 1428","folder":"IETF/RFC-1428","source":"IETF/RFC-1428/RFC-1428.txt","version":null},{"body":"IETF","designation":"RFC 1456","folder":"IETF/RFC-1456","source":"IETF/RFC-1456/RFC-1456.txt","version":null},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1842","folder":"IETF/RFC-1842","source":"IETF/RFC-1842/RFC-1842.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1896","folder":"IETF/RFC-1896","source":"IETF/RFC-1896/RFC-1896.txt","version":null},{"body":"IETF","designation":"RFC 2046","folder":"IETF/RFC-2046","source":"IETF/RFC-2046/RFC-2046.txt","version":null},{"body":"IETF","designation":"RFC 2058","folder":"IETF/RFC-2058","source":"IETF/RFC-2058/RFC-2058.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2138","folder":"IETF/RFC-2138","source":"IETF/RFC-2138/RFC-2138.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2831","folder":"IETF/RFC-2831","source":"IETF/RFC-2831/RFC-2831.txt","version":null},{"body":"IETF","designation":"RFC 2865","folder":"IETF/RFC-2865","source":"IETF/RFC-2865/RFC-2865.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 4005","folder":"IETF/RFC-4005","source":"IETF/RFC-4005/RFC-4005.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO 8859 1987 nested-reference unavailable"},{"id":"ISO-IEC ISO 88592","type":"specification","body":"ISO-IEC","designation":"ISO 88592","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+88592","download_urls":["https://www.iso.org/search.html?q=ISO+88592"],"folder":"ISO-IEC/ISO-88592","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1341","folder":"IETF/RFC-1341","source":"IETF/RFC-1341/RFC-1341.pdf","version":null},{"body":"IETF","designation":"RFC 1521","folder":"IETF/RFC-1521","source":"IETF/RFC-1521/RFC-1521.pdf","version":null}],"search_text":"ISO-IEC ISO 88592 nested-reference unavailable"},{"id":"ISO-IEC ISO 8878","type":"specification","body":"ISO-IEC","designation":"ISO 8878","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8878","download_urls":["https://www.iso.org/search.html?q=ISO+8878"],"folder":"ISO-IEC/ISO-8878","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null}],"search_text":"ISO-IEC ISO 8878 nested-reference unavailable"},{"id":"ISO-IEC ISO 8879-1986","type":"specification","body":"ISO-IEC","designation":"ISO 8879-1986","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8879-1986","download_urls":["https://www.iso.org/search.html?q=ISO+8879-1986"],"folder":"ISO-IEC/ISO-8879-1986","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null}],"search_text":"ISO-IEC ISO 8879-1986 nested-reference unavailable"},{"id":"ISO-IEC ISO 8879 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 8879","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8879","download_urls":["https://www.iso.org/search.html?q=ISO+8879"],"folder":"ISO-IEC/ISO-8879-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1873","folder":"IETF/RFC-1873","source":"IETF/RFC-1873/RFC-1873.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2110","folder":"IETF/RFC-2110","source":"IETF/RFC-2110/RFC-2110.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2165","folder":"IETF/RFC-2165","source":"IETF/RFC-2165/RFC-2165.txt","version":null},{"body":"IETF","designation":"RFC 2376","folder":"IETF/RFC-2376","source":"IETF/RFC-2376/RFC-2376.txt","version":null},{"body":"IETF","designation":"RFC 2557","folder":"IETF/RFC-2557","source":"IETF/RFC-2557/RFC-2557.txt","version":null},{"body":"IETF","designation":"RFC 3023","folder":"IETF/RFC-3023","source":"IETF/RFC-3023/RFC-3023.txt","version":null},{"body":"IETF","designation":"RFC 3120","folder":"IETF/RFC-3120","source":"IETF/RFC-3120/RFC-3120.txt","version":null},{"body":"IETF","designation":"RFC 3121","folder":"IETF/RFC-3121","source":"IETF/RFC-3121/RFC-3121.txt","version":null},{"body":"IETF","designation":"RFC 3151","folder":"IETF/RFC-3151","source":"IETF/RFC-3151/RFC-3151.txt","version":null},{"body":"IETF","designation":"RFC 3880","folder":"IETF/RFC-3880","source":"IETF/RFC-3880/RFC-3880.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5218","folder":"IETF/RFC-5218","source":"IETF/RFC-5218/RFC-5218.txt","version":null}],"search_text":"ISO-IEC ISO 8879 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 8883-1","type":"specification","body":"ISO-IEC","designation":"ISO 8883-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8883-1","download_urls":["https://www.iso.org/search.html?q=ISO+8883-1"],"folder":"ISO-IEC/ISO-8883-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1457","folder":"IETF/RFC-1457","source":"IETF/RFC-1457/RFC-1457.txt","version":null}],"search_text":"ISO-IEC ISO 8883-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 8885","type":"specification","body":"ISO-IEC","designation":"ISO 8885","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8885","download_urls":["https://www.iso.org/search.html?q=ISO+8885"],"folder":"ISO-IEC/ISO-8885","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null}],"search_text":"ISO-IEC ISO 8885 nested-reference unavailable"},{"id":"ISO-IEC ISO 8886","type":"specification","body":"ISO-IEC","designation":"ISO 8886","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8886","download_urls":["https://www.iso.org/search.html?q=ISO+8886"],"folder":"ISO-IEC/ISO-8886","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1381","folder":"IETF/RFC-1381","source":"IETF/RFC-1381/RFC-1381.txt","version":null}],"search_text":"ISO-IEC ISO 8886 nested-reference unavailable"},{"id":"ISO-IEC ISO 8895-1","type":"specification","body":"ISO-IEC","designation":"ISO 8895-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+8895-1","download_urls":["https://www.iso.org/search.html?q=ISO+8895-1"],"folder":"ISO-IEC/ISO-8895-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"ISO-IEC ISO 8895-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9000","type":"specification","body":"ISO-IEC","designation":"ISO 9000","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9000","download_urls":["https://www.iso.org/search.html?q=ISO+9000"],"folder":"ISO-IEC/ISO-9000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null}],"search_text":"ISO-IEC ISO 9000 nested-reference unavailable"},{"id":"ISO-IEC ISO 9066","type":"specification","body":"ISO-IEC","designation":"ISO 9066","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9066","download_urls":["https://www.iso.org/search.html?q=ISO+9066"],"folder":"ISO-IEC/ISO-9066","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null}],"search_text":"ISO-IEC ISO 9066 nested-reference unavailable"},{"id":"ISO-IEC ISO 9070","type":"specification","body":"ISO-IEC","designation":"ISO 9070","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9070","download_urls":["https://www.iso.org/search.html?q=ISO+9070"],"folder":"ISO-IEC/ISO-9070","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2426","folder":"IETF/RFC-2426","source":"IETF/RFC-2426/RFC-2426.txt","version":null},{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null},{"body":"IETF","designation":"RFC 6350","folder":"IETF/RFC-6350","source":"IETF/RFC-6350/RFC-6350.txt","version":null}],"search_text":"ISO-IEC ISO 9070 nested-reference unavailable"},{"id":"ISO-IEC ISO 9072","type":"specification","body":"ISO-IEC","designation":"ISO 9072","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9072","download_urls":["https://www.iso.org/search.html?q=ISO+9072"],"folder":"ISO-IEC/ISO-9072","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1085","folder":"IETF/RFC-1085","source":"IETF/RFC-1085/RFC-1085.txt","version":null}],"search_text":"ISO-IEC ISO 9072 nested-reference unavailable"},{"id":"ISO-IEC ISO 9072-1","type":"specification","body":"ISO-IEC","designation":"ISO 9072-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9072-1","download_urls":["https://www.iso.org/search.html?q=ISO+9072-1"],"folder":"ISO-IEC/ISO-9072-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null}],"search_text":"ISO-IEC ISO 9072-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9072-2","type":"specification","body":"ISO-IEC","designation":"ISO 9072-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9072-2","download_urls":["https://www.iso.org/search.html?q=ISO+9072-2"],"folder":"ISO-IEC/ISO-9072-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1095","folder":"IETF/RFC-1095","source":"IETF/RFC-1095/RFC-1095.txt","version":null},{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null}],"search_text":"ISO-IEC ISO 9072-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 9074","type":"specification","body":"ISO-IEC","designation":"ISO 9074","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9074","download_urls":["https://www.iso.org/search.html?q=ISO+9074"],"folder":"ISO-IEC/ISO-9074","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 994","folder":"IETF/RFC-994","source":"IETF/RFC-994/RFC-994.txt","version":null}],"search_text":"ISO-IEC ISO 9074 nested-reference unavailable"},{"id":"ISO-IEC ISO 9074-1989","type":"specification","body":"ISO-IEC","designation":"ISO 9074-1989","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9074-1989","download_urls":["https://www.iso.org/search.html?q=ISO+9074-1989"],"folder":"ISO-IEC/ISO-9074-1989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 9074-1989 nested-reference unavailable"},{"id":"ISO-IEC ISO 9314-1","type":"specification","body":"ISO-IEC","designation":"ISO 9314-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9314-1","download_urls":["https://www.iso.org/search.html?q=ISO+9314-1"],"folder":"ISO-IEC/ISO-9314-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1103","folder":"IETF/RFC-1103","source":"IETF/RFC-1103/RFC-1103.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null}],"search_text":"ISO-IEC ISO 9314-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9314-2","type":"specification","body":"ISO-IEC","designation":"ISO 9314-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9314-2","download_urls":["https://www.iso.org/search.html?q=ISO+9314-2"],"folder":"ISO-IEC/ISO-9314-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1103","folder":"IETF/RFC-1103","source":"IETF/RFC-1103/RFC-1103.txt","version":null},{"body":"IETF","designation":"RFC 1188","folder":"IETF/RFC-1188","source":"IETF/RFC-1188/RFC-1188.txt","version":null},{"body":"IETF","designation":"RFC 1390","folder":"IETF/RFC-1390","source":"IETF/RFC-1390/RFC-1390.txt","version":null}],"search_text":"ISO-IEC ISO 9314-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 9362 V1994","type":"specification","body":"ISO-IEC","designation":"ISO 9362","version":"1994","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9362","download_urls":["https://www.iso.org/search.html?q=ISO+9362"],"folder":"ISO-IEC/ISO-9362-V1994","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null}],"search_text":"ISO-IEC ISO 9362 1994 nested-reference unavailable"},{"id":"ISO-IEC ISO 9542 V1988","type":"specification","body":"ISO-IEC","designation":"ISO 9542","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9542","download_urls":["https://www.iso.org/search.html?q=ISO+9542"],"folder":"ISO-IEC/ISO-9542-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null},{"body":"IETF","designation":"RFC 1162","folder":"IETF/RFC-1162","source":"IETF/RFC-1162/RFC-1162.txt","version":null},{"body":"IETF","designation":"RFC 1195","folder":"IETF/RFC-1195","source":"IETF/RFC-1195/RFC-1195.txt","version":null},{"body":"IETF","designation":"RFC 1200","folder":"IETF/RFC-1200","source":"IETF/RFC-1200/RFC-1200.txt","version":null},{"body":"IETF","designation":"RFC 1213","folder":"IETF/RFC-1213","source":"IETF/RFC-1213/RFC-1213.txt","version":null},{"body":"IETF","designation":"RFC 1237","folder":"IETF/RFC-1237","source":"IETF/RFC-1237/RFC-1237.txt","version":null},{"body":"IETF","designation":"RFC 1238","folder":"IETF/RFC-1238","source":"IETF/RFC-1238/RFC-1238.txt","version":null},{"body":"IETF","designation":"RFC 1250","folder":"IETF/RFC-1250","source":"IETF/RFC-1250/RFC-1250.txt","version":null},{"body":"IETF","designation":"RFC 1354","folder":"IETF/RFC-1354","source":"IETF/RFC-1354/RFC-1354.txt","version":null},{"body":"IETF","designation":"RFC 1377","folder":"IETF/RFC-1377","source":"IETF/RFC-1377/RFC-1377.txt","version":null},{"body":"IETF","designation":"RFC 1454","folder":"IETF/RFC-1454","source":"IETF/RFC-1454/RFC-1454.txt","version":null},{"body":"IETF","designation":"RFC 1461","folder":"IETF/RFC-1461","source":"IETF/RFC-1461/RFC-1461.txt","version":null},{"body":"IETF","designation":"RFC 1526","folder":"IETF/RFC-1526","source":"IETF/RFC-1526/RFC-1526.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2096","folder":"IETF/RFC-2096","source":"IETF/RFC-2096/RFC-2096.txt","version":null},{"body":"IETF","designation":"RFC 3796","folder":"IETF/RFC-3796","source":"IETF/RFC-3796/RFC-3796.txt","version":null},{"body":"IETF","designation":"RFC 4292","folder":"IETF/RFC-4292","source":"IETF/RFC-4292/RFC-4292.txt","version":null}],"search_text":"ISO-IEC ISO 9542 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO 9548","type":"specification","body":"ISO-IEC","designation":"ISO 9548","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9548","download_urls":["https://www.iso.org/search.html?q=ISO+9548"],"folder":"ISO-IEC/ISO-9548","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null}],"search_text":"ISO-IEC ISO 9548 nested-reference unavailable"},{"id":"ISO-IEC ISO 9576","type":"specification","body":"ISO-IEC","designation":"ISO 9576","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9576","download_urls":["https://www.iso.org/search.html?q=ISO+9576"],"folder":"ISO-IEC/ISO-9576","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1240","folder":"IETF/RFC-1240","source":"IETF/RFC-1240/RFC-1240.txt","version":null}],"search_text":"ISO-IEC ISO 9576 nested-reference unavailable"},{"id":"ISO-IEC ISO 9577","type":"specification","body":"ISO-IEC","designation":"ISO 9577","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9577","download_urls":["https://www.iso.org/search.html?q=ISO+9577"],"folder":"ISO-IEC/ISO-9577","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1060","folder":"IETF/RFC-1060","source":"IETF/RFC-1060/RFC-1060.txt","version":null},{"body":"IETF","designation":"RFC 1340","folder":"IETF/RFC-1340","source":"IETF/RFC-1340/RFC-1340.txt","version":null},{"body":"IETF","designation":"RFC 1700","folder":"IETF/RFC-1700","source":"IETF/RFC-1700/RFC-1700.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"ISO-IEC ISO 9577 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594","type":"specification","body":"ISO-IEC","designation":"ISO 9594","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594","download_urls":["https://www.iso.org/search.html?q=ISO+9594"],"folder":"ISO-IEC/ISO-9594","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null},{"body":"IETF","designation":"RFC 1608","folder":"IETF/RFC-1608","source":"IETF/RFC-1608/RFC-1608.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO 9594 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594-1","type":"specification","body":"ISO-IEC","designation":"ISO 9594-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594-1","download_urls":["https://www.iso.org/search.html?q=ISO+9594-1"],"folder":"ISO-IEC/ISO-9594-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 9594-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594-2","type":"specification","body":"ISO-IEC","designation":"ISO 9594-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594-2","download_urls":["https://www.iso.org/search.html?q=ISO+9594-2"],"folder":"ISO-IEC/ISO-9594-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null}],"search_text":"ISO-IEC ISO 9594-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594-6","type":"specification","body":"ISO-IEC","designation":"ISO 9594-6","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594-6","download_urls":["https://www.iso.org/search.html?q=ISO+9594-6"],"folder":"ISO-IEC/ISO-9594-6","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"}],"search_text":"ISO-IEC ISO 9594-6 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594-8","type":"specification","body":"ISO-IEC","designation":"ISO 9594-8","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594-8","download_urls":["https://www.iso.org/search.html?q=ISO+9594-8"],"folder":"ISO-IEC/ISO-9594-8","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1423","folder":"IETF/RFC-1423","source":"IETF/RFC-1423/RFC-1423.txt","version":null},{"body":"IETF","designation":"RFC 1848","folder":"IETF/RFC-1848","source":"IETF/RFC-1848/RFC-1848.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO 9594-8 nested-reference unavailable"},{"id":"ISO-IEC ISO 9594-9","type":"specification","body":"ISO-IEC","designation":"ISO 9594-9","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9594-9","download_urls":["https://www.iso.org/search.html?q=ISO+9594-9"],"folder":"ISO-IEC/ISO-9594-9","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2120","folder":"IETF/RFC-2120","source":"IETF/RFC-2120/RFC-2120.txt","version":null}],"search_text":"ISO-IEC ISO 9594-9 nested-reference unavailable"},{"id":"ISO-IEC ISO 9595","type":"specification","body":"ISO-IEC","designation":"ISO 9595","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9595","download_urls":["https://www.iso.org/search.html?q=ISO+9595"],"folder":"ISO-IEC/ISO-9595","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null}],"search_text":"ISO-IEC ISO 9595 nested-reference unavailable"},{"id":"ISO-IEC ISO 9596","type":"specification","body":"ISO-IEC","designation":"ISO 9596","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9596","download_urls":["https://www.iso.org/search.html?q=ISO+9596"],"folder":"ISO-IEC/ISO-9596","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1189","folder":"IETF/RFC-1189","source":"IETF/RFC-1189/RFC-1189.txt","version":null},{"body":"IETF","designation":"RFC 1470","folder":"IETF/RFC-1470","source":"IETF/RFC-1470/RFC-1470.txt","version":null}],"search_text":"ISO-IEC ISO 9596 nested-reference unavailable"},{"id":"ISO-IEC ISO 9660","type":"specification","body":"ISO-IEC","designation":"ISO 9660","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9660","download_urls":["https://www.iso.org/search.html?q=ISO+9660"],"folder":"ISO-IEC/ISO-9660","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2790","folder":"IETF/RFC-2790","source":"IETF/RFC-2790/RFC-2790.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null}],"search_text":"ISO-IEC ISO 9660 nested-reference unavailable"},{"id":"ISO-IEC ISO 9735","type":"specification","body":"ISO-IEC","designation":"ISO 9735","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9735","download_urls":["https://www.iso.org/search.html?q=ISO+9735"],"folder":"ISO-IEC/ISO-9735","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1767","folder":"IETF/RFC-1767","source":"IETF/RFC-1767/RFC-1767.txt","version":null}],"search_text":"ISO-IEC ISO 9735 nested-reference unavailable"},{"id":"ISO-IEC ISO 9796","type":"specification","body":"ISO-IEC","designation":"ISO 9796","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9796","download_urls":["https://www.iso.org/search.html?q=ISO+9796"],"folder":"ISO-IEC/ISO-9796","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO 9796 nested-reference unavailable"},{"id":"ISO-IEC ISO 9796-1","type":"specification","body":"ISO-IEC","designation":"ISO 9796-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9796-1","download_urls":["https://www.iso.org/search.html?q=ISO+9796-1"],"folder":"ISO-IEC/ISO-9796-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO 9796-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9796-1991","type":"specification","body":"ISO-IEC","designation":"ISO 9796-1991","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9796-1991","download_urls":["https://www.iso.org/search.html?q=ISO+9796-1991"],"folder":"ISO-IEC/ISO-9796-1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO 9796-1991 nested-reference unavailable"},{"id":"ISO-IEC ISO 9796-2","type":"specification","body":"ISO-IEC","designation":"ISO 9796-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9796-2","download_urls":["https://www.iso.org/search.html?q=ISO+9796-2"],"folder":"ISO-IEC/ISO-9796-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 6979","folder":"IETF/RFC-6979","source":"IETF/RFC-6979/RFC-6979.txt","version":null}],"search_text":"ISO-IEC ISO 9796-2 nested-reference unavailable"},{"id":"ISO-IEC ISO 9796-4","type":"specification","body":"ISO-IEC","designation":"ISO 9796-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9796-4","download_urls":["https://www.iso.org/search.html?q=ISO+9796-4"],"folder":"ISO-IEC/ISO-9796-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO 9796-4 nested-reference unavailable"},{"id":"ISO-IEC ISO 9798","type":"specification","body":"ISO-IEC","designation":"ISO 9798","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9798","download_urls":["https://www.iso.org/search.html?q=ISO+9798"],"folder":"ISO-IEC/ISO-9798","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null}],"search_text":"ISO-IEC ISO 9798 nested-reference unavailable"},{"id":"ISO-IEC ISO 9834-1","type":"specification","body":"ISO-IEC","designation":"ISO 9834-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9834-1","download_urls":["https://www.iso.org/search.html?q=ISO+9834-1"],"folder":"ISO-IEC/ISO-9834-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6021","folder":"IETF/RFC-6021","source":"IETF/RFC-6021/RFC-6021.txt","version":null},{"body":"IETF","designation":"RFC 6991","folder":"IETF/RFC-6991","source":"IETF/RFC-6991/RFC-6991.txt","version":null}],"search_text":"ISO-IEC ISO 9834-1 nested-reference unavailable"},{"id":"ISO-IEC ISO 9899 V1990","type":"specification","body":"ISO-IEC","designation":"ISO 9899","version":"1990","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9899","download_urls":["https://www.iso.org/search.html?q=ISO+9899"],"folder":"ISO-IEC/ISO-9899-V1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null}],"search_text":"ISO-IEC ISO 9899 1990 nested-reference unavailable"},{"id":"ISO-IEC ISO 995","type":"specification","body":"ISO-IEC","designation":"ISO 995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+995","download_urls":["https://www.iso.org/search.html?q=ISO+995"],"folder":"ISO-IEC/ISO-995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1000","folder":"IETF/RFC-1000","source":"IETF/RFC-1000/RFC-1000.txt","version":null}],"search_text":"ISO-IEC ISO 995 nested-reference unavailable"},{"id":"ISO-IEC ISO 9999","type":"specification","body":"ISO-IEC","designation":"ISO 9999","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9999","download_urls":["https://www.iso.org/search.html?q=ISO+9999"],"folder":"ISO-IEC/ISO-9999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 9999 nested-reference unavailable"},{"id":"ISO-IEC ISO 9999-1","type":"specification","body":"ISO-IEC","designation":"ISO 9999-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO+9999-1","download_urls":["https://www.iso.org/search.html?q=ISO+9999-1"],"folder":"ISO-IEC/ISO-9999-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO 9999-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10021","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10021","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10021"],"folder":"ISO-IEC/ISO-IEC-10021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2162","folder":"IETF/RFC-2162","source":"IETF/RFC-2162/RFC-2162.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10021-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10021-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10021-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10021-1"],"folder":"ISO-IEC/ISO-IEC-10021-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1138","folder":"IETF/RFC-1138","source":"IETF/RFC-1138/RFC-1138.txt","version":null},{"body":"IETF","designation":"RFC 1148","folder":"IETF/RFC-1148","source":"IETF/RFC-1148/RFC-1148.txt","version":null},{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 3801","folder":"IETF/RFC-3801","source":"IETF/RFC-3801/RFC-3801.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10021-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10021-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10021-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10021-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10021-2"],"folder":"ISO-IEC/ISO-IEC-10021-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1327","folder":"IETF/RFC-1327","source":"IETF/RFC-1327/RFC-1327.txt","version":null},{"body":"IETF","designation":"RFC 1506","folder":"IETF/RFC-1506","source":"IETF/RFC-1506/RFC-1506.txt","version":null},{"body":"IETF","designation":"RFC 1685","folder":"IETF/RFC-1685","source":"IETF/RFC-1685/RFC-1685.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10021-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10021-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10021-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10021-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10021-4"],"folder":"ISO-IEC/ISO-IEC-10021-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10021-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10021-7 V1997","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10021-7","version":"1997","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10021-7","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10021-7"],"folder":"ISO-IEC/ISO-IEC-10021-7-V1997","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10021-7 1997 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10026-1 V1992","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10026-1","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10026-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10026-1"],"folder":"ISO-IEC/ISO-IEC-10026-1-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10026-1 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10038","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10038","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10038","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10038"],"folder":"ISO-IEC/ISO-IEC-10038","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2019","folder":"IETF/RFC-2019","source":"IETF/RFC-2019/RFC-2019.txt","version":null},{"body":"IETF","designation":"RFC 2338","folder":"IETF/RFC-2338","source":"IETF/RFC-2338/RFC-2338.txt","version":null},{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2814","folder":"IETF/RFC-2814","source":"IETF/RFC-2814/RFC-2814.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 3768","folder":"IETF/RFC-3768","source":"IETF/RFC-3768/RFC-3768.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4710","folder":"IETF/RFC-4710","source":"IETF/RFC-4710/RFC-4710.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10038 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10039 V1990","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10039","version":"1990","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10039","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10039"],"folder":"ISO-IEC/ISO-IEC-10039-V1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10039 1990 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10118","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10118","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10118","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10118"],"folder":"ISO-IEC/ISO-IEC-10118","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10118 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10118-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10118-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10118-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10118-1"],"folder":"ISO-IEC/ISO-IEC-10118-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10118-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10118-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10118-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10118-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10118-2"],"folder":"ISO-IEC/ISO-IEC-10118-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10118-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10118-3 V2004","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10118-3","version":"2004","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10118-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10118-3"],"folder":"ISO-IEC/ISO-IEC-10118-3-V2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 2857","folder":"IETF/RFC-2857","source":"IETF/RFC-2857/RFC-2857.txt","version":null},{"body":"IETF","designation":"RFC 4051","folder":"IETF/RFC-4051","source":"IETF/RFC-4051/RFC-4051.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5708","folder":"IETF/RFC-5708","source":"IETF/RFC-5708/RFC-5708.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10118-3 2004 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10118-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10118-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10118-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10118-4"],"folder":"ISO-IEC/ISO-IEC-10118-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10118-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10165-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10165-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10165-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10165-2"],"folder":"ISO-IEC/ISO-IEC-10165-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1142","folder":"IETF/RFC-1142","source":"IETF/RFC-1142/RFC-1142.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10165-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10175","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10175","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10175","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10175"],"folder":"ISO-IEC/ISO-IEC-10175","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 2565","folder":"IETF/RFC-2565","source":"IETF/RFC-2565/RFC-2565.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2567","folder":"IETF/RFC-2567","source":"IETF/RFC-2567/RFC-2567.txt","version":null},{"body":"IETF","designation":"RFC 2568","folder":"IETF/RFC-2568","source":"IETF/RFC-2568/RFC-2568.txt","version":null},{"body":"IETF","designation":"RFC 2910","folder":"IETF/RFC-2910","source":"IETF/RFC-2910/RFC-2910.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3805","folder":"IETF/RFC-3805","source":"IETF/RFC-3805/RFC-3805.txt","version":null},{"body":"IETF","designation":"RFC 3806","folder":"IETF/RFC-3806","source":"IETF/RFC-3806/RFC-3806.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10175 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10179 V1996","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10179","version":"1996","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10179","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10179"],"folder":"ISO-IEC/ISO-IEC-10179-V1996","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3151","folder":"IETF/RFC-3151","source":"IETF/RFC-3151/RFC-3151.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10179 1996 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10181-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10181-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10181-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10181-5"],"folder":"ISO-IEC/ISO-IEC-10181-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3029","folder":"IETF/RFC-3029","source":"IETF/RFC-3029/RFC-3029.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10181-5 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10589 V2002","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10589","version":"2002","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10589","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10589"],"folder":"ISO-IEC/ISO-IEC-10589-V2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1322","folder":"IETF/RFC-1322","source":"IETF/RFC-1322/RFC-1322.txt","version":null},{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 2763","folder":"IETF/RFC-2763","source":"IETF/RFC-2763/RFC-2763.txt","version":null},{"body":"IETF","designation":"RFC 3373","folder":"IETF/RFC-3373","source":"IETF/RFC-3373/RFC-3373.txt","version":null},{"body":"IETF","designation":"RFC 3563","folder":"IETF/RFC-3563","source":"IETF/RFC-3563/RFC-3563.txt","version":null},{"body":"IETF","designation":"RFC 3567","folder":"IETF/RFC-3567","source":"IETF/RFC-3567/RFC-3567.txt","version":null},{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null},{"body":"IETF","designation":"RFC 3786","folder":"IETF/RFC-3786","source":"IETF/RFC-3786/RFC-3786.txt","version":null},{"body":"IETF","designation":"RFC 3847","folder":"IETF/RFC-3847","source":"IETF/RFC-3847/RFC-3847.txt","version":null},{"body":"IETF","designation":"RFC 4444","folder":"IETF/RFC-4444","source":"IETF/RFC-4444/RFC-4444.txt","version":null},{"body":"IETF","designation":"RFC 4593","folder":"IETF/RFC-4593","source":"IETF/RFC-4593/RFC-4593.txt","version":null},{"body":"IETF","designation":"RFC 5089","folder":"IETF/RFC-5089","source":"IETF/RFC-5089/RFC-5089.txt","version":null},{"body":"IETF","designation":"RFC 5310","folder":"IETF/RFC-5310","source":"IETF/RFC-5310/RFC-5310.txt","version":null},{"body":"IETF","designation":"RFC 5311","folder":"IETF/RFC-5311","source":"IETF/RFC-5311/RFC-5311.txt","version":null},{"body":"IETF","designation":"RFC 6165","folder":"IETF/RFC-6165","source":"IETF/RFC-6165/RFC-6165.txt","version":null},{"body":"IETF","designation":"RFC 6232","folder":"IETF/RFC-6232","source":"IETF/RFC-6232/RFC-6232.txt","version":null},{"body":"IETF","designation":"RFC 6233","folder":"IETF/RFC-6233","source":"IETF/RFC-6233/RFC-6233.txt","version":null},{"body":"IETF","designation":"RFC 6325","folder":"IETF/RFC-6325","source":"IETF/RFC-6325/RFC-6325.txt","version":null},{"body":"IETF","designation":"RFC 6326","folder":"IETF/RFC-6326","source":"IETF/RFC-6326/RFC-6326.txt","version":null},{"body":"IETF","designation":"RFC 6327","folder":"IETF/RFC-6327","source":"IETF/RFC-6327/RFC-6327.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6361","folder":"IETF/RFC-6361","source":"IETF/RFC-6361/RFC-6361.txt","version":null},{"body":"IETF","designation":"RFC 6439","folder":"IETF/RFC-6439","source":"IETF/RFC-6439/RFC-6439.txt","version":null},{"body":"IETF","designation":"RFC 6823","folder":"IETF/RFC-6823","source":"IETF/RFC-6823/RFC-6823.txt","version":null},{"body":"IETF","designation":"RFC 7067","folder":"IETF/RFC-7067","source":"IETF/RFC-7067/RFC-7067.txt","version":null},{"body":"IETF","designation":"RFC 7172","folder":"IETF/RFC-7172","source":"IETF/RFC-7172/RFC-7172.txt","version":null},{"body":"IETF","designation":"RFC 7173","folder":"IETF/RFC-7173","source":"IETF/RFC-7173/RFC-7173.txt","version":null},{"body":"IETF","designation":"RFC 7177","folder":"IETF/RFC-7177","source":"IETF/RFC-7177/RFC-7177.txt","version":null},{"body":"IETF","designation":"RFC 7356","folder":"IETF/RFC-7356","source":"IETF/RFC-7356/RFC-7356.txt","version":null},{"body":"IETF","designation":"RFC 7357","folder":"IETF/RFC-7357","source":"IETF/RFC-7357/RFC-7357.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7780","folder":"IETF/RFC-7780","source":"IETF/RFC-7780/RFC-7780.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10589 2002 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10646-1 V2000","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10646-1","version":"2000","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10646-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10646-1"],"folder":"ISO-IEC/ISO-IEC-10646-1-V2000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1505","folder":"IETF/RFC-1505","source":"IETF/RFC-1505/RFC-1505.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1815","folder":"IETF/RFC-1815","source":"IETF/RFC-1815/RFC-1815.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2044","folder":"IETF/RFC-2044","source":"IETF/RFC-2044/RFC-2044.txt","version":null},{"body":"IETF","designation":"RFC 2070","folder":"IETF/RFC-2070","source":"IETF/RFC-2070/RFC-2070.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2152","folder":"IETF/RFC-2152","source":"IETF/RFC-2152/RFC-2152.txt","version":null},{"body":"IETF","designation":"RFC 2218","folder":"IETF/RFC-2218","source":"IETF/RFC-2218/RFC-2218.txt","version":null},{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 2251","folder":"IETF/RFC-2251","source":"IETF/RFC-2251/RFC-2251.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2291","folder":"IETF/RFC-2291","source":"IETF/RFC-2291/RFC-2291.txt","version":null},{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null},{"body":"IETF","designation":"RFC 2440","folder":"IETF/RFC-2440","source":"IETF/RFC-2440/RFC-2440.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2624","folder":"IETF/RFC-2624","source":"IETF/RFC-2624/RFC-2624.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3383","folder":"IETF/RFC-3383","source":"IETF/RFC-3383/RFC-3383.txt","version":null},{"body":"IETF","designation":"RFC 3454","folder":"IETF/RFC-3454","source":"IETF/RFC-3454/RFC-3454.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3530","folder":"IETF/RFC-3530","source":"IETF/RFC-3530/RFC-3530.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4880","folder":"IETF/RFC-4880","source":"IETF/RFC-4880/RFC-4880.txt","version":null},{"body":"IETF","designation":"RFC 5055","folder":"IETF/RFC-5055","source":"IETF/RFC-5055/RFC-5055.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10646-1 2000 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10646-2 V2001","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10646-2","version":"2001","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10646-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10646-2"],"folder":"ISO-IEC/ISO-IEC-10646-2-V2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10646-2 2001 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10646 V2020","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10646","version":"2020","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10646","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10646"],"folder":"ISO-IEC/ISO-IEC-10646-V2020","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 1502","folder":"IETF/RFC-1502","source":"IETF/RFC-1502/RFC-1502.txt","version":null},{"body":"IETF","designation":"RFC 1641","folder":"IETF/RFC-1641","source":"IETF/RFC-1641/RFC-1641.txt","version":null},{"body":"IETF","designation":"RFC 1642","folder":"IETF/RFC-1642","source":"IETF/RFC-1642/RFC-1642.txt","version":null},{"body":"IETF","designation":"RFC 1759","folder":"IETF/RFC-1759","source":"IETF/RFC-1759/RFC-1759.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 2279","folder":"IETF/RFC-2279","source":"IETF/RFC-2279/RFC-2279.txt","version":null},{"body":"IETF","designation":"RFC 2482","folder":"IETF/RFC-2482","source":"IETF/RFC-2482/RFC-2482.txt","version":null},{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 2781","folder":"IETF/RFC-2781","source":"IETF/RFC-2781/RFC-2781.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 3010","folder":"IETF/RFC-3010","source":"IETF/RFC-3010/RFC-3010.txt","version":null},{"body":"IETF","designation":"RFC 3454","folder":"IETF/RFC-3454","source":"IETF/RFC-3454/RFC-3454.txt","version":null},{"body":"IETF","designation":"RFC 3491","folder":"IETF/RFC-3491","source":"IETF/RFC-3491/RFC-3491.txt","version":null},{"body":"IETF","designation":"RFC 3536","folder":"IETF/RFC-3536","source":"IETF/RFC-3536/RFC-3536.txt","version":null},{"body":"IETF","designation":"RFC 3629","folder":"IETF/RFC-3629","source":"IETF/RFC-3629/RFC-3629.txt","version":null},{"body":"IETF","designation":"RFC 3650","folder":"IETF/RFC-3650","source":"IETF/RFC-3650/RFC-3650.txt","version":null},{"body":"IETF","designation":"RFC 3722","folder":"IETF/RFC-3722","source":"IETF/RFC-3722/RFC-3722.txt","version":null},{"body":"IETF","designation":"RFC 3743","folder":"IETF/RFC-3743","source":"IETF/RFC-3743/RFC-3743.txt","version":null},{"body":"IETF","designation":"RFC 3862","folder":"IETF/RFC-3862","source":"IETF/RFC-3862/RFC-3862.txt","version":null},{"body":"IETF","designation":"RFC 3920","folder":"IETF/RFC-3920","source":"IETF/RFC-3920/RFC-3920.txt","version":null},{"body":"IETF","designation":"RFC 3986","folder":"IETF/RFC-3986","source":"IETF/RFC-3986/RFC-3986.txt","version":null},{"body":"IETF","designation":"RFC 3987","folder":"IETF/RFC-3987","source":"IETF/RFC-3987/RFC-3987.txt","version":null},{"body":"IETF","designation":"RFC 4267","folder":"IETF/RFC-4267","source":"IETF/RFC-4267/RFC-4267.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 4690","folder":"IETF/RFC-4690","source":"IETF/RFC-4690/RFC-4690.txt","version":null},{"body":"IETF","designation":"RFC 4765","folder":"IETF/RFC-4765","source":"IETF/RFC-4765/RFC-4765.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 6020","folder":"IETF/RFC-6020","source":"IETF/RFC-6020/RFC-6020.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null},{"body":"IETF","designation":"RFC 6122","folder":"IETF/RFC-6122","source":"IETF/RFC-6122/RFC-6122.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null},{"body":"IETF","designation":"RFC 7012","folder":"IETF/RFC-7012","source":"IETF/RFC-7012/RFC-7012.txt","version":null},{"body":"IETF","designation":"RFC 7950","folder":"IETF/RFC-7950","source":"IETF/RFC-7950/RFC-7950.txt","version":null},{"body":"IETF","designation":"RFC 8489","folder":"IETF/RFC-8489","source":"IETF/RFC-8489/RFC-8489.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10646 2020 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10733","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10733","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10733","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10733"],"folder":"ISO-IEC/ISO-IEC-10733","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10733 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10744 V1992","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10744","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10744","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10744"],"folder":"ISO-IEC/ISO-IEC-10744-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1874","folder":"IETF/RFC-1874","source":"IETF/RFC-1874/RFC-1874.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10744 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10747","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10747","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10747","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10747"],"folder":"ISO-IEC/ISO-IEC-10747","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1629","folder":"IETF/RFC-1629","source":"IETF/RFC-1629/RFC-1629.txt","version":null},{"body":"IETF","designation":"RFC 1774","folder":"IETF/RFC-1774","source":"IETF/RFC-1774/RFC-1774.txt","version":null},{"body":"IETF","designation":"RFC 1930","folder":"IETF/RFC-1930","source":"IETF/RFC-1930/RFC-1930.txt","version":null},{"body":"IETF","designation":"RFC 1965","folder":"IETF/RFC-1965","source":"IETF/RFC-1965/RFC-1965.txt","version":null},{"body":"IETF","designation":"RFC 2439","folder":"IETF/RFC-2439","source":"IETF/RFC-2439/RFC-2439.txt","version":null},{"body":"IETF","designation":"RFC 3065","folder":"IETF/RFC-3065","source":"IETF/RFC-3065/RFC-3065.txt","version":null},{"body":"IETF","designation":"RFC 5065","folder":"IETF/RFC-5065","source":"IETF/RFC-5065/RFC-5065.txt","version":null},{"body":"IETF","designation":"RFC 6396","folder":"IETF/RFC-6396","source":"IETF/RFC-6396/RFC-6396.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10747 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 10918-1 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 10918-1","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+10918-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+10918-1"],"folder":"ISO-IEC/ISO-IEC-10918-1-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 10918-1 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11172","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11172","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11172","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11172"],"folder":"ISO-IEC/ISO-IEC-11172","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11172 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11172-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11172-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11172-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11172-2"],"folder":"ISO-IEC/ISO-IEC-11172-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11172-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11172-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11172-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11172-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11172-3"],"folder":"ISO-IEC/ISO-IEC-11172-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11172-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 113818-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 113818-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+113818-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+113818-1"],"folder":"ISO-IEC/ISO-IEC-113818-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 113818-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11544 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11544","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11544","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11544"],"folder":"ISO-IEC/ISO-IEC-11544-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2531","folder":"IETF/RFC-2531","source":"IETF/RFC-2531/RFC-2531.txt","version":null},{"body":"IETF","designation":"RFC 2879","folder":"IETF/RFC-2879","source":"IETF/RFC-2879/RFC-2879.txt","version":null},{"body":"IETF","designation":"RFC 2880","folder":"IETF/RFC-2880","source":"IETF/RFC-2880/RFC-2880.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11544 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11571","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11571","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11571","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11571"],"folder":"ISO-IEC/ISO-IEC-11571","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11571 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11572","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11572","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11572","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11572"],"folder":"ISO-IEC/ISO-IEC-11572","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11572 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11578 V1996","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11578","version":"1996","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11578","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11578"],"folder":"ISO-IEC/ISO-IEC-11578-V1996","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2518","folder":"IETF/RFC-2518","source":"IETF/RFC-2518/RFC-2518.txt","version":null},{"body":"IETF","designation":"RFC 3645","folder":"IETF/RFC-3645","source":"IETF/RFC-3645/RFC-3645.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11578 1996 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11582","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11582","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11582","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11582"],"folder":"ISO-IEC/ISO-IEC-11582","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11582 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 11770-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 11770-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+11770-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+11770-3"],"folder":"ISO-IEC/ISO-IEC-11770-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 11770-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13213 V1994","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13213","version":"1994","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13213","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13213"],"folder":"ISO-IEC/ISO-IEC-13213-V1994","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2734","folder":"IETF/RFC-2734","source":"IETF/RFC-2734/RFC-2734.txt","version":null},{"body":"IETF","designation":"RFC 3146","folder":"IETF/RFC-3146","source":"IETF/RFC-3146/RFC-3146.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13213 1994 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13818","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13818","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13818","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13818"],"folder":"ISO-IEC/ISO-IEC-13818","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 3189","folder":"IETF/RFC-3189","source":"IETF/RFC-3189/RFC-3189.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13818 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13818-1 V2000","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13818-1","version":"2000","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13818-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13818-1"],"folder":"ISO-IEC/ISO-IEC-13818-1-V2000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13818-1 2000 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13818-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13818-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13818-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13818-2"],"folder":"ISO-IEC/ISO-IEC-13818-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13818-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13818-3 V1995","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13818-3","version":"1995","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13818-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13818-3"],"folder":"ISO-IEC/ISO-IEC-13818-3-V1995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2038","folder":"IETF/RFC-2038","source":"IETF/RFC-2038/RFC-2038.txt","version":null},{"body":"IETF","designation":"RFC 2250","folder":"IETF/RFC-2250","source":"IETF/RFC-2250/RFC-2250.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13818-3 1995 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 138181","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 138181","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+138181","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+138181"],"folder":"ISO-IEC/ISO-IEC-138181","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 138181 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13888","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13888","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13888","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13888"],"folder":"ISO-IEC/ISO-IEC-13888","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-1","folder":"ETSI/EN-319-522-1-V1.2.1","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 13888 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13888-1 V2009","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13888-1","version":"2009","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13888-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13888-1"],"folder":"ISO-IEC/ISO-IEC-13888-1-V2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-1","folder":"ETSI/EN-319-522-1-V1.2.1","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 13888-1 2009 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13888-2 V2010","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13888-2","version":"2010","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13888-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13888-2"],"folder":"ISO-IEC/ISO-IEC-13888-2-V2010","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-1","folder":"ETSI/EN-319-522-1-V1.2.1","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 13888-2 2010 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 13888-3 V2010","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 13888-3","version":"2010","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+13888-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+13888-3"],"folder":"ISO-IEC/ISO-IEC-13888-3-V2010","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 522-1","folder":"ETSI/EN-319-522-1-V1.2.1","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 13888-3 2010 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14469-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14469-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14469-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14469-2"],"folder":"ISO-IEC/ISO-IEC-14469-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14469-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496"],"folder":"ISO-IEC/ISO-IEC-14496","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-1 V2001","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-1","version":"2001","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-1"],"folder":"ISO-IEC/ISO-IEC-14496-1-V2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-1 2001 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-10 V2004","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-10","version":"2004","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-10","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-10"],"folder":"ISO-IEC/ISO-IEC-14496-10-V2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null},{"body":"IETF","designation":"RFC 5104","folder":"IETF/RFC-5104","source":"IETF/RFC-5104/RFC-5104.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-10 2004 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-12","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-12","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-12","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-12"],"folder":"ISO-IEC/ISO-IEC-14496-12","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-12 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-14","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-14","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-14","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-14"],"folder":"ISO-IEC/ISO-IEC-14496-14","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-14 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-15","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-15","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-15","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-15"],"folder":"ISO-IEC/ISO-IEC-14496-15","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4337","folder":"IETF/RFC-4337","source":"IETF/RFC-4337/RFC-4337.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-15 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-2 V2004","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-2","version":"2004","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-2"],"folder":"ISO-IEC/ISO-IEC-14496-2-V2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-2 2004 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-22","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-22","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-22","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-22"],"folder":"ISO-IEC/ISO-IEC-14496-22","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8081","folder":"IETF/RFC-8081","source":"IETF/RFC-8081/RFC-8081.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-22 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14496-3 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14496-3","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14496-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14496-3"],"folder":"ISO-IEC/ISO-IEC-14496-3-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3016","folder":"IETF/RFC-3016","source":"IETF/RFC-3016/RFC-3016.txt","version":null},{"body":"IETF","designation":"RFC 3640","folder":"IETF/RFC-3640","source":"IETF/RFC-3640/RFC-3640.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14496-3 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14516","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14516","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14516","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14516"],"folder":"ISO-IEC/ISO-IEC-14516","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ISO-IEC ISO/IEC 14516 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14533-4 V2019","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14533-4","version":"2019","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14533-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14533-4"],"folder":"ISO-IEC/ISO-IEC-14533-4-V2019","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"}],"search_text":"ISO-IEC ISO/IEC 14533-4 2019 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-262","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-262","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-262","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-262"],"folder":"ISO-IEC/ISO-IEC-14776-262","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-262 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-322","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-322","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-322","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-322"],"folder":"ISO-IEC/ISO-IEC-14776-322","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-322 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-412","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-412","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-412","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-412"],"folder":"ISO-IEC/ISO-IEC-14776-412","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7144","folder":"IETF/RFC-7144","source":"IETF/RFC-7144/RFC-7144.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-412 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-414","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-414","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-414","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-414"],"folder":"ISO-IEC/ISO-IEC-14776-414","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-414 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-452","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-452","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-452","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-452"],"folder":"ISO-IEC/ISO-IEC-14776-452","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-452 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14776-453","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14776-453","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14776-453","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14776-453"],"folder":"ISO-IEC/ISO-IEC-14776-453","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14776-453 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14882-1998","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14882-1998","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14882-1998","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14882-1998"],"folder":"ISO-IEC/ISO-IEC-14882-1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4011","folder":"IETF/RFC-4011","source":"IETF/RFC-4011/RFC-4011.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14882-1998 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14882 V2017","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14882","version":"2017","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14882","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14882"],"folder":"ISO-IEC/ISO-IEC-14882-V2017","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4137","folder":"IETF/RFC-4137","source":"IETF/RFC-4137/RFC-4137.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14882 2017 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14888","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14888","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14888","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14888"],"folder":"ISO-IEC/ISO-IEC-14888","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14888 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14888-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14888-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14888-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14888-1"],"folder":"ISO-IEC/ISO-IEC-14888-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14888-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14888-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14888-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14888-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14888-2"],"folder":"ISO-IEC/ISO-IEC-14888-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14888-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14888-3 V2006","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14888-3","version":"2006","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14888-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14888-3"],"folder":"ISO-IEC/ISO-IEC-14888-3-V2006","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5114","folder":"IETF/RFC-5114","source":"IETF/RFC-5114/RFC-5114.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14888-3 2006 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 14977","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 14977","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+14977","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+14977"],"folder":"ISO-IEC/ISO-IEC-14977","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5511","folder":"IETF/RFC-5511","source":"IETF/RFC-5511/RFC-5511.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 14977 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15000-3 V2023","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15000-3","version":"2023","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15000-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15000-3"],"folder":"ISO-IEC/ISO-IEC-15000-3-V2023","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ISO-IEC ISO/IEC 15000-3 2023 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15408-1 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15408-1","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15408-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15408-1"],"folder":"ISO-IEC/ISO-IEC-15408-1-V2022","files":{},"tags":["cited-by-eu-law","common-criteria","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15408-1 2022 cited-by-eu-law common-criteria implementing-regulation nested-reference unavailable 2025-1942 Recognition of qualified validation services 32025R1942 2025-1944 Qualified electronic registered delivery services 32025R1944"},{"id":"ISO-IEC ISO/IEC 15408-3 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15408-3","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15408-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15408-3"],"folder":"ISO-IEC/ISO-IEC-15408-3-V2022","files":{},"tags":["cited-by-eu-law","common-criteria","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 15408-3 2022 cited-by-eu-law common-criteria implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981"},{"id":"legal:2024-2981","type":"legal_regulation","act_id":"2024-2981","title":"Certification of EUDI Wallets","celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/049b9eb6-b1e1-11ef-acb1-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2024-2981/2024-2981.html","sha256":"e45c7c805a4c14082e8537d14805b159e86aa279c45a4715e2a2e161952be210","size":450763},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/049b9eb6-b1e1-11ef-acb1-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2024-2981/2024-2981.pdf","sha256":"5957c8b08fc411c97d0fc62a9285d3b16aeb4581f40d07878bb91b46720d2a3a","size":1221411}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and the Council as regards the certification of European Digital Identity Wallets Pursuant to Article 5c of Regulation (EU) No 910/2014, the certification of European Digital Identity Wallets (‘wallets’) is to be made in accordance with functional, cybersecurity, and data protection requirements to ensure a high level of security and trust in the wallets. Those certification requirements need to be harmonised across Member States in order to prevent market fragmentation and to build a robust… ‘wallet solution’ means a combination of software, hardware, services, settings, and configurations, including wallet instances, one or more wallet secure cryptographic applications and one or more wallet secure cryptographic devices;","scope_keywords":["article","certification","conformity","council","cryptographic","cybersecurity","data","digital","ensure","european","high","identity","level","market","order","parliament","protection","pursuant","regulation","software","solution","trust","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.116641+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2024-2981 Certification of EUDI Wallets 32024R2981 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and the Council as regards the certification of European Digital Identity Wallets Pursuant to Article 5c of Regulation (EU) No 910/2014, the certification of European Digital Identity Wallets (‘wallets’) is to be made in accordance with functional, cybersecurity, and data protection requirements to ensure a high level of security and trust in the wallets. Those certification requirements need to be harmonised across Member States in order to prevent market fragmentation and to build a robust… ‘wallet solution’ means a combination of software, hardware, services, settings, and configurations, including wallet instances, one or more wallet secure cryptographic applications and one or more wallet secure cryptographic devices; article certification conformity council cryptographic cybersecurity data digital ensure european high identity level market order parliament protection pursuant regulation software solution trust wallet wallets"},{"id":"ISO-IEC ISO/IEC 15408 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15408","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15408","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15408"],"folder":"ISO-IEC/ISO-IEC-15408-V2022","files":{},"tags":["cited-by-eu-law","common-criteria","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R1929","eli":"https://data.europa.eu/eli/reg_impl/2025/1929/oj/eng","id":"2025-1929","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1929/2025-1929.md","title":"Qualified electronic time stamps"},{"celex":"32025R1942","eli":"https://data.europa.eu/eli/reg_impl/2025/1942/oj/eng","id":"2025-1942","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1942/2025-1942.md","title":"Recognition of qualified validation services"},{"celex":"32025R1943","eli":"https://data.europa.eu/eli/reg_impl/2025/1943/oj/eng","id":"2025-1943","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1943/2025-1943.md","title":"Reference standards and validation procedures (QTSP)"},{"celex":"32025R1944","eli":"https://data.europa.eu/eli/reg_impl/2025/1944/oj/eng","id":"2025-1944","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1944/2025-1944.md","title":"Qualified electronic registered delivery services"},{"celex":"32025R1946","eli":"https://data.europa.eu/eli/reg_impl/2025/1946/oj/eng","id":"2025-1946","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1946/2025-1946.md","title":"Qualified preservation services for signatures and seals"},{"celex":"32025R2531","eli":"https://data.europa.eu/eli/reg_impl/2025/2531/oj/eng","id":"2025-2531","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2531/2025-2531.md","title":"Qualified electronic ledgers"},{"celex":"32025R2532","eli":"https://data.europa.eu/eli/reg_impl/2025/2532/oj/eng","id":"2025-2532","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2532/2025-2532.md","title":"Qualified electronic archiving services"},{"celex":"32026R1735","eli":"https://data.europa.eu/eli/reg_impl/2026/1735/oj/eng","id":"2026-1735","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1735/2026-1735.md","title":"Amending CIR 2025/1569 — electronic attestations of attributes (EAA)"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 431-1","folder":"ETSI/TS-119-431-1-V1.3.1","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 441","folder":"ETSI/TS-119-441-V1.2.1","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 5570","folder":"IETF/RFC-5570","source":"IETF/RFC-5570/RFC-5570.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15408 2022 cited-by-eu-law common-criteria implementing-regulation nested-reference unavailable 2025-1929 Qualified electronic time stamps 32025R1929 2025-1942 Recognition of qualified validation services 32025R1942 2025-1943 Reference standards and validation procedures (QTSP) 32025R1943 2025-1944 Qualified electronic registered delivery services 32025R1944 2025-1946 Qualified preservation services for signatures and seals 32025R1946 2025-2531 Qualified electronic ledgers 32025R2531 2025-2532 Qualified electronic archiving services 32025R2532 2026-1735 Amending CIR 2025/1569 — electronic attestations of attributes (EAA) 32026R1735"},{"id":"ISO-IEC ISO/IEC 15504","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15504","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15504","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15504"],"folder":"ISO-IEC/ISO-IEC-15504","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 15504 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15802","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15802","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15802","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15802"],"folder":"ISO-IEC/ISO-IEC-15802","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1638","folder":"IETF/RFC-1638","source":"IETF/RFC-1638/RFC-1638.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15802 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15802-3 V1998","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15802-3","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15802-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15802-3"],"folder":"ISO-IEC/ISO-IEC-15802-3-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2674","folder":"IETF/RFC-2674","source":"IETF/RFC-2674/RFC-2674.txt","version":null},{"body":"IETF","designation":"RFC 2815","folder":"IETF/RFC-2815","source":"IETF/RFC-2815/RFC-2815.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2878","folder":"IETF/RFC-2878","source":"IETF/RFC-2878/RFC-2878.txt","version":null},{"body":"IETF","designation":"RFC 3270","folder":"IETF/RFC-3270","source":"IETF/RFC-3270/RFC-3270.txt","version":null},{"body":"IETF","designation":"RFC 3290","folder":"IETF/RFC-3290","source":"IETF/RFC-3290/RFC-3290.txt","version":null},{"body":"IETF","designation":"RFC 3518","folder":"IETF/RFC-3518","source":"IETF/RFC-3518/RFC-3518.txt","version":null},{"body":"IETF","designation":"RFC 4318","folder":"IETF/RFC-4318","source":"IETF/RFC-4318/RFC-4318.txt","version":null},{"body":"IETF","designation":"RFC 4363","folder":"IETF/RFC-4363","source":"IETF/RFC-4363/RFC-4363.txt","version":null},{"body":"IETF","designation":"RFC 4665","folder":"IETF/RFC-4665","source":"IETF/RFC-4665/RFC-4665.txt","version":null},{"body":"IETF","designation":"RFC 4761","folder":"IETF/RFC-4761","source":"IETF/RFC-4761/RFC-4761.txt","version":null},{"body":"IETF","designation":"RFC 4762","folder":"IETF/RFC-4762","source":"IETF/RFC-4762/RFC-4762.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15802-3 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15802-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15802-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15802-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15802-5"],"folder":"ISO-IEC/ISO-IEC-15802-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15802-5 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15945","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15945","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15945","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15945"],"folder":"ISO-IEC/ISO-IEC-15945","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ISO-IEC ISO/IEC 15945 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15946","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15946","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15946","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15946"],"folder":"ISO-IEC/ISO-IEC-15946","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15946 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15946-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15946-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15946-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15946-1"],"folder":"ISO-IEC/ISO-IEC-15946-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15946-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15946-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15946-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15946-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15946-2"],"folder":"ISO-IEC/ISO-IEC-15946-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null},{"body":"IETF","designation":"RFC 6954","folder":"IETF/RFC-6954","source":"IETF/RFC-6954/RFC-6954.txt","version":null},{"body":"IETF","designation":"RFC 7027","folder":"IETF/RFC-7027","source":"IETF/RFC-7027/RFC-7027.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15946-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15946-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15946-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15946-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15946-3"],"folder":"ISO-IEC/ISO-IEC-15946-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15946-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 15946-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 15946-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+15946-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+15946-4"],"folder":"ISO-IEC/ISO-IEC-15946-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 15946-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 17000 V2020","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17000","version":"2020","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17000","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17000"],"folder":"ISO-IEC/ISO-IEC-17000-V2020","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"}],"search_text":"ISO-IEC ISO/IEC 17000 2020 cited-by-eu-law implementing-regulation nested-reference unavailable 2024-2981 Certification of EUDI Wallets 32024R2981"},{"id":"ISO-IEC ISO/IEC 17011 V2017","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17011","version":"2017","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17011","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17011"],"folder":"ISO-IEC/ISO-IEC-17011-V2017","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17011 2017 cited-by-eu-law implementing-regulation unavailable 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 17020 V2012","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17020","version":"2012","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17020","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17020"],"folder":"ISO-IEC/ISO-IEC-17020-V2012","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17020 2012 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 17021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17021","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17021","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17021"],"folder":"ISO-IEC/ISO-IEC-17021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"}],"search_text":"ISO-IEC ISO/IEC 17021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 17021-1 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17021-1","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17021-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17021-1"],"folder":"ISO-IEC/ISO-IEC-17021-1-V2015","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17021-1 2015 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 17025 V2017","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17025","version":"2017","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17025","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17025"],"folder":"ISO-IEC/ISO-IEC-17025-V2017","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17025 2017 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 17029 V2019","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17029","version":"2019","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17029","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17029"],"folder":"ISO-IEC/ISO-IEC-17029-V2019","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17029 2019 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981"},{"id":"ISO-IEC ISO/IEC 17065 V2012","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17065","version":"2012","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17065","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17065"],"folder":"ISO-IEC/ISO-IEC-17065-V2012","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"}],"search_text":"ISO-IEC ISO/IEC 17065 2012 cited-by-eu-law implementing-regulation nested-reference unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 17067 V2013","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 17067","version":"2013","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+17067","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+17067"],"folder":"ISO-IEC/ISO-IEC-17067-V2013","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R2162","eli":"https://data.europa.eu/eli/reg_impl/2025/2162/oj/eng","id":"2025-2162","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-2162/2025-2162.md","title":"Accreditation of conformity assessment bodies"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 17067 2013 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-2162 Accreditation of conformity assessment bodies 32025R2162"},{"id":"ISO-IEC ISO/IEC 18004 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18004","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18004","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18004"],"folder":"ISO-IEC/ISO-IEC-18004-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18004 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18013","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18013","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18013","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18013"],"folder":"ISO-IEC/ISO-IEC-18013","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 18013 cited-by-eu-law implementing-regulation nested-reference unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO/IEC 18013-5 V2021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18013-5","version":"2021","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18013-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18013-5"],"folder":"ISO-IEC/ISO-IEC-18013-5-V2021","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32024R2982","eli":"https://data.europa.eu/eli/reg_impl/2024/2982/oj/eng","id":"2024-2982","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2982/2024-2982.md","title":"Protocols and interfaces for EUDI Wallets"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS04","folder":"ARF/TS04-V1.0.1","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS09","folder":"ARF/TS09-V1.1","source":"ARF/TS09-V1.1/TS09-V1.1.md","version":"1.1"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS13","folder":"ARF/TS13","source":"ARF/TS13/TS13-V1.0.1.md","version":null},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"SD-JWT","folder":"IETF/SD-JWT","source":"IETF/SD-JWT/SD-JWT.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18013-5 2021 cited-by-eu-law implementing-regulation nested-reference unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2024-2982 Protocols and interfaces for EUDI Wallets 32024R2982 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"legal:2024-2982","type":"legal_regulation","act_id":"2024-2982","title":"Protocols and interfaces for EUDI Wallets","celex":"32024R2982","eli":"https://data.europa.eu/eli/reg_impl/2024/2982/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/0c2d7c7b-b1e1-11ef-acb1-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2024-2982/2024-2982.html","sha256":"6dcd6d801df70c72976faf396166d82990cd6b3b152a10828be5eda3e7b8c213","size":64398},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/0c2d7c7b-b1e1-11ef-acb1-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2024-2982/2024-2982.pdf","sha256":"52008a3723815c0ba3e4473dae6ce14a1e569218ae408375e636c4a9201b731c","size":550657}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards protocols and interfaces to be supported by the European Digital Identity Framework The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, for natural and legal persons, while ensuring the… the issuance of person identification data and electronic attestations of attributes to wallet units;","scope_keywords":["across","attestation","attestations","attributes","council","data","digital","electronic","european","framework","identification","identity","interfaces","member","parliament","person","protocols","regulation","services","states","union","units","wallet","wallets"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.136443+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2024-2982 Protocols and interfaces for EUDI Wallets 32024R2982 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards protocols and interfaces to be supported by the European Digital Identity Framework The European Digital Identity Framework established by Regulation (EU) No 910/2014 is a crucial component in the establishment of a secure and interoperable digital identity ecosystem across the Union. With the European Digital Identity Wallets (‘wallets’) being the cornerstone of the framework, it aims at facilitating access to services across Member States, for natural and legal persons, while ensuring the… the issuance of person identification data and electronic attestations of attributes to wallet units; across attestation attestations attributes council data digital electronic european framework identification identity interfaces member parliament person protocols regulation services states union units wallet wallets"},{"id":"ISO-IEC ISO/IEC 18013-7 V2025","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18013-7","version":"2025","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18013-7","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18013-7"],"folder":"ISO-IEC/ISO-IEC-18013-7-V2025","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 18013-7 2025 cited-by-eu-law implementing-regulation nested-reference unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO/IEC 18014","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18014","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18014","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18014"],"folder":"ISO-IEC/ISO-IEC-18014","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null},{"body":"IETF","designation":"RFC 4738","folder":"IETF/RFC-4738","source":"IETF/RFC-4738/RFC-4738.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18014 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18014-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18014-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18014-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18014-2"],"folder":"ISO-IEC/ISO-IEC-18014-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 431-1","folder":"ETSI/TS-119-431-1-V1.3.1","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf","version":"1.3.1"}],"search_text":"ISO-IEC ISO/IEC 18014-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18031 V2005","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18031","version":"2005","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18031","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18031"],"folder":"ISO-IEC/ISO-IEC-18031-V2005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 4753","folder":"IETF/RFC-4753","source":"IETF/RFC-4753/RFC-4753.txt","version":null},{"body":"IETF","designation":"RFC 5903","folder":"IETF/RFC-5903","source":"IETF/RFC-5903/RFC-5903.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18031 2005 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18032","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18032","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18032","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18032"],"folder":"ISO-IEC/ISO-IEC-18032","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 5639","folder":"IETF/RFC-5639","source":"IETF/RFC-5639/RFC-5639.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18032 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18033","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18033","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18033","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18033"],"folder":"ISO-IEC/ISO-IEC-18033","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4132","folder":"IETF/RFC-4132","source":"IETF/RFC-4132/RFC-4132.txt","version":null},{"body":"IETF","designation":"RFC 4312","folder":"IETF/RFC-4312","source":"IETF/RFC-4312/RFC-4312.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18033 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18033-2 V2010","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18033-2","version":"2010","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18033-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18033-2"],"folder":"ISO-IEC/ISO-IEC-18033-2-V2010","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 5990","folder":"IETF/RFC-5990","source":"IETF/RFC-5990/RFC-5990.txt","version":null},{"body":"IETF","designation":"RFC 6931","folder":"IETF/RFC-6931","source":"IETF/RFC-6931/RFC-6931.txt","version":null},{"body":"IETF","designation":"RFC 9180","folder":"IETF/RFC-9180","source":"IETF/RFC-9180/RFC-9180.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18033-2 2010 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18033-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18033-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18033-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18033-3"],"folder":"ISO-IEC/ISO-IEC-18033-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4162","folder":"IETF/RFC-4162","source":"IETF/RFC-4162/RFC-4162.txt","version":null},{"body":"IETF","designation":"RFC 5528","folder":"IETF/RFC-5528","source":"IETF/RFC-5528/RFC-5528.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 18033-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18045 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18045","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18045","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18045"],"folder":"ISO-IEC/ISO-IEC-18045-V2022","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"ISO-IEC ISO/IEC 18045 2022 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18370","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18370","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18370","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18370"],"folder":"ISO-IEC/ISO-IEC-18370","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 18370 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18370-1 V2016","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18370-1","version":"2016","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18370-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18370-1"],"folder":"ISO-IEC/ISO-IEC-18370-1-V2016","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 18370-1 2016 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 18370-2 V2016","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 18370-2","version":"2016","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+18370-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+18370-2"],"folder":"ISO-IEC/ISO-IEC-18370-2-V2016","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 18370-2 2016 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19011 V2011","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19011","version":"2011","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19011","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19011"],"folder":"ISO-IEC/ISO-IEC-19011-V2011","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"}],"search_text":"ISO-IEC ISO/IEC 19011 2011 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19501 V2005","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19501","version":"2005","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19501","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19501"],"folder":"ISO-IEC/ISO-IEC-19501-V2005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5941","folder":"IETF/RFC-5941","source":"IETF/RFC-5941/RFC-5941.txt","version":null},{"body":"IETF","designation":"RFC 7143","folder":"IETF/RFC-7143","source":"IETF/RFC-7143/RFC-7143.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19501 2005 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19757","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19757","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19757","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19757"],"folder":"ISO-IEC/ISO-IEC-19757","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19757 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19757-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19757-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19757-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19757-1"],"folder":"ISO-IEC/ISO-IEC-19757-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6244","folder":"IETF/RFC-6244","source":"IETF/RFC-6244/RFC-6244.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19757-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19757-2 V2008","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19757-2","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19757-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19757-2"],"folder":"ISO-IEC/ISO-IEC-19757-2-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6022","folder":"IETF/RFC-6022","source":"IETF/RFC-6022/RFC-6022.txt","version":null},{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 6501","folder":"IETF/RFC-6501","source":"IETF/RFC-6501/RFC-6501.txt","version":null},{"body":"IETF","designation":"RFC 7807","folder":"IETF/RFC-7807","source":"IETF/RFC-7807/RFC-7807.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null},{"body":"IETF","designation":"RFC 7991","folder":"IETF/RFC-7991","source":"IETF/RFC-7991/RFC-7991.txt","version":null},{"body":"IETF","designation":"RFC 8428","folder":"IETF/RFC-8428","source":"IETF/RFC-8428/RFC-8428.txt","version":null},{"body":"IETF","designation":"RFC 8610","folder":"IETF/RFC-8610","source":"IETF/RFC-8610/RFC-8610.txt","version":null},{"body":"IETF","designation":"RFC 9457","folder":"IETF/RFC-9457","source":"IETF/RFC-9457/RFC-9457.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19757-2 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19757-3 V2016","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19757-3","version":"2016","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19757-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19757-3"],"folder":"ISO-IEC/ISO-IEC-19757-3-V2016","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6110","folder":"IETF/RFC-6110","source":"IETF/RFC-6110/RFC-6110.txt","version":null},{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19757-3 2016 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19757-8 V2008","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19757-8","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19757-8","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19757-8"],"folder":"ISO-IEC/ISO-IEC-19757-8-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7952","folder":"IETF/RFC-7952","source":"IETF/RFC-7952/RFC-7952.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19757-8 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19770-2 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19770-2","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19770-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19770-2"],"folder":"ISO-IEC/ISO-IEC-19770-2-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8412","folder":"IETF/RFC-8412","source":"IETF/RFC-8412/RFC-8412.txt","version":null},{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19770-2 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19770-5 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19770-5","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19770-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19770-5"],"folder":"ISO-IEC/ISO-IEC-19770-5-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 19770-5 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19790 V2025","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19790","version":"2025","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19790","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19790"],"folder":"ISO-IEC/ISO-IEC-19790-V2025","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 421","folder":"ETSI/EN-319-421-V1.3.1","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 441","folder":"ETSI/TS-119-441-V1.2.1","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 19790 2025 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19792","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19792","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19792","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19792"],"folder":"ISO-IEC/ISO-IEC-19792","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 19792 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19794-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19794-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19794-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19794-5"],"folder":"ISO-IEC/ISO-IEC-19794-5","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 19794-5 cited-by-eu-law implementing-regulation unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO/IEC 19795-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19795-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19795-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19795-1"],"folder":"ISO-IEC/ISO-IEC-19795-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 19795-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 1990","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 1990","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+1990","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+1990"],"folder":"ISO-IEC/ISO-IEC-1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 1990 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19989-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19989-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19989-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19989-1"],"folder":"ISO-IEC/ISO-IEC-19989-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 19989-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 19989-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 19989-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+19989-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+19989-3"],"folder":"ISO-IEC/ISO-IEC-19989-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 19989-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 20008","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 20008","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+20008","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+20008"],"folder":"ISO-IEC/ISO-IEC-20008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 20008 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 20008-1 V2013","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 20008-1","version":"2013","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+20008-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+20008-1"],"folder":"ISO-IEC/ISO-IEC-20008-1-V2013","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 20008-1 2013 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 20008-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 20008-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+20008-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+20008-2"],"folder":"ISO-IEC/ISO-IEC-20008-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 20008-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 20008-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 20008-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+20008-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+20008-3"],"folder":"ISO-IEC/ISO-IEC-20008-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 20008-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 20059","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 20059","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+20059","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+20059"],"folder":"ISO-IEC/ISO-IEC-20059","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 20059 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 2022 V1994","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 2022","version":"1994","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+2022","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+2022"],"folder":"ISO-IEC/ISO-IEC-2022-V1994","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2157","folder":"IETF/RFC-2157","source":"IETF/RFC-2157/RFC-2157.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 2022 1994 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 21320-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 21320-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+21320-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+21320-1"],"folder":"ISO-IEC/ISO-IEC-21320-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 162-1","folder":"ETSI/EN-319-162-1-V1.1.1","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 511","folder":"ETSI/TS-119-511-V1.1.1","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 21320-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 22537 V2006","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 22537","version":"2006","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+22537","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+22537"],"folder":"ISO-IEC/ISO-IEC-22537-V2006","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9535","folder":"IETF/RFC-9535","source":"IETF/RFC-9535/RFC-9535.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 22537 2006 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 23001-8 V2013","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 23001-8","version":"2013","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+23001-8","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+23001-8"],"folder":"ISO-IEC/ISO-IEC-23001-8-V2013","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 23001-8 2013 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 23220","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 23220","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+23220","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+23220"],"folder":"ISO-IEC/ISO-IEC-23220","files":{},"tags":["unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 23220 unavailable"},{"id":"ISO-IEC ISO/IEC 23220-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 23220-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+23220-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+23220-2"],"folder":"ISO-IEC/ISO-IEC-23220-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 23220-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 23220-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 23220-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+23220-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+23220-3"],"folder":"ISO-IEC/ISO-IEC-23220-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 23220-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 23220-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 23220-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+23220-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+23220-4"],"folder":"ISO-IEC/ISO-IEC-23220-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 23220-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 24824-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 24824-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+24824-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+24824-1"],"folder":"ISO-IEC/ISO-IEC-24824-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 24824-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27000","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27000","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27000","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27000"],"folder":"ISO-IEC/ISO-IEC-27000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 27000 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27001 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27001","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27001","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27001"],"folder":"ISO-IEC/ISO-IEC-27001-V2022","files":{},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"},{"celex":"32025R1568","eli":"https://data.europa.eu/eli/reg_impl/2025/1568/oj/eng","id":"2025-1568","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2025-1568/2025-1568.md","title":"Peer review of electronic identification schemes"}],"parent_specifications":[{"body":"ETSI","designation":"EN 319 401","folder":"ETSI/EN-319-401-V3.2.1","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf","version":"3.2.1"},{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 27001 2022 cited-by-eu-law implementing-regulation nested-reference unavailable 2024-2981 Certification of EUDI Wallets 32024R2981 2025-1568 Peer review of electronic identification schemes 32025R1568"},{"id":"legal:2025-1568","type":"legal_regulation","act_id":"2025-1568","title":"Peer review of electronic identification schemes","celex":"32025R1568","eli":"https://data.europa.eu/eli/reg_impl/2025/1568/oj/eng","kind":"implementing_regulation","section":"implementing-acts","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/e85cbfd7-6cdd-11f0-bf4e-01aa75ed71a1.0006.03/DOC_1","path":"implementing-acts/2025-1568/2025-1568.html","sha256":"5105c1633a94a6f5e1fa0157a380014814e44740d49e5eee52c0a6489606b68a","size":145893},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/e85cbfd7-6cdd-11f0-bf4e-01aa75ed71a1.0006.01/DOC_1","path":"implementing-acts/2025-1568/2025-1568.pdf","sha256":"238d0c11456716ce62a2af8c6b586cdede77504a0f150add1634acd8ce43b809","size":625912}},"summary":"laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards procedural arrangements for peer reviews of electronic identification schemes and for cooperation on the organisation of such reviews within the Cooperation Group and repealing Commission Implementing Decision (EU) 2015/296 Regulation (EU) No 910/2014 provides for a peer review mechanism with respect to electronic identification schemes that are to be notified, in which Member States can participate on a voluntary basis. Peer reviews should enable Member States to understand the electronic identification schemes to be notified in accordance with Article 9(1), point (a), of Regulation (EU) No 910/2014 and effectively cooperate with a… Commission Implementing Decision (EU) 2015/296  ( 2 ) established the procedural arrangements for cooperation on electronic…","scope_keywords":["arrangements","article","commission","cooperation","decision","electronic","established","european","group","identification","implementing","member","notified","peer","procedural","regulation","review","reviews","rules","scheme","schemes","state","states","trust"],"summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:15.185260+00:00","sources":["eli-subtitle","recitals"],"status":"ok"},"search_text":"2025-1568 Peer review of electronic identification schemes 32025R1568 implementing_regulation implementing-acts laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards procedural arrangements for peer reviews of electronic identification schemes and for cooperation on the organisation of such reviews within the Cooperation Group and repealing Commission Implementing Decision (EU) 2015/296 Regulation (EU) No 910/2014 provides for a peer review mechanism with respect to electronic identification schemes that are to be notified, in which Member States can participate on a voluntary basis. Peer reviews should enable Member States to understand the electronic identification schemes to be notified in accordance with Article 9(1), point (a), of Regulation (EU) No 910/2014 and effectively cooperate with a… Commission Implementing Decision (EU) 2015/296  ( 2 ) established the procedural arrangements for cooperation on electronic… arrangements article commission cooperation decision electronic established european group identification implementing member notified peer procedural regulation review reviews rules scheme schemes state states trust"},{"id":"ISO-IEC ISO/IEC 27002 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27002","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27002","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27002"],"folder":"ISO-IEC/ISO-IEC-27002-V2022","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 401","folder":"ETSI/EN-319-401-V3.2.1","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf","version":"3.2.1"},{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 101","folder":"ETSI/TS-119-101-V1.1.1","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ISO-IEC ISO/IEC 27002 2022 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27005 V2022","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27005","version":"2022","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27005","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27005"],"folder":"ISO-IEC/ISO-IEC-27005-V2022","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 401","folder":"ETSI/EN-319-401-V3.2.1","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf","version":"3.2.1"}],"search_text":"ISO-IEC ISO/IEC 27005 2022 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27006","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27006","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27006","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27006"],"folder":"ISO-IEC/ISO-IEC-27006","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 403-1","folder":"ETSI/EN-319-403-1-V2.3.1","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf","version":"2.3.1"}],"search_text":"ISO-IEC ISO/IEC 27006 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27565","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27565","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27565","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27565"],"folder":"ISO-IEC/ISO-IEC-27565","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ISO-IEC ISO/IEC 27565 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 27701 V2019","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 27701","version":"2019","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+27701","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+27701"],"folder":"ISO-IEC/ISO-IEC-27701-V2019","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 401","folder":"ETSI/EN-319-401-V3.2.1","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf","version":"3.2.1"}],"search_text":"ISO-IEC ISO/IEC 27701 2019 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 29100 V2011","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 29100","version":"2011","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+29100","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+29100"],"folder":"ISO-IEC/ISO-IEC-29100-V2011","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"}],"search_text":"ISO-IEC ISO/IEC 29100 2011 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 29500-2 V2021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 29500-2","version":"2021","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+29500-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+29500-2"],"folder":"ISO-IEC/ISO-IEC-29500-2-V2021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"}],"search_text":"ISO-IEC ISO/IEC 29500-2 2021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 29794-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 29794-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+29794-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+29794-5"],"folder":"ISO-IEC/ISO-IEC-29794-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 29794-5 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 30107","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 30107","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+30107","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+30107"],"folder":"ISO-IEC/ISO-IEC-30107","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 30107 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 30107-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 30107-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+30107-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+30107-1"],"folder":"ISO-IEC/ISO-IEC-30107-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 30107-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 30107-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 30107-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+30107-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+30107-3"],"folder":"ISO-IEC/ISO-IEC-30107-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 461","folder":"ETSI/TS-119-461-V2.1.1","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf","version":"2.1.1"}],"search_text":"ISO-IEC ISO/IEC 30107-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 30111 V2019","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 30111","version":"2019","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+30111","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+30111"],"folder":"ISO-IEC/ISO-IEC-30111-V2019","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2981","eli":"https://data.europa.eu/eli/reg_impl/2024/2981/oj/eng","id":"2024-2981","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2981/2024-2981.md","title":"Certification of EUDI Wallets"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 30111 2019 cited-by-eu-law implementing-regulation unavailable 2024-2981 Certification of EUDI Wallets 32024R2981"},{"id":"ISO-IEC ISO/IEC 3166","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 3166","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+3166","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+3166"],"folder":"ISO-IEC/ISO-IEC-3166","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 3166 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 3166-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 3166-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+3166-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+3166-1"],"folder":"ISO-IEC/ISO-IEC-3166-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 3166-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 3309 V1991","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 3309","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+3309","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+3309"],"folder":"ISO-IEC/ISO-IEC-3309-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 3309 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 39794-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 39794-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+39794-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+39794-5"],"folder":"ISO-IEC/ISO-IEC-39794-5","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 39794-5 cited-by-eu-law implementing-regulation unavailable 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO/IEC 4335 V1991","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 4335","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+4335","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+4335"],"folder":"ISO-IEC/ISO-IEC-4335-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1662","folder":"IETF/RFC-1662","source":"IETF/RFC-1662/RFC-1662.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 4335 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 5218","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 5218","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+5218","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+5218"],"folder":"ISO-IEC/ISO-IEC-5218","files":{},"tags":["cited-by-eu-law","implementing-regulation","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[{"celex":"32024R2977","eli":"https://data.europa.eu/eli/reg_impl/2024/2977/oj/eng","id":"2024-2977","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2024-2977/2024-2977.md","title":"PID and electronic attestations of attributes (lifecycle)"},{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[],"search_text":"ISO-IEC ISO/IEC 5218 cited-by-eu-law implementing-regulation unavailable 2024-2977 PID and electronic attestations of attributes (lifecycle) 32024R2977 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"ISO-IEC ISO/IEC 6429 V1992","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 6429","version":"1992","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+6429","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+6429"],"folder":"ISO-IEC/ISO-IEC-6429-V1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 1556","folder":"IETF/RFC-1556","source":"IETF/RFC-1556/RFC-1556.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 6429 1992 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 646 V1991","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 646","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+646","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+646"],"folder":"ISO-IEC/ISO-IEC-646-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1468","folder":"IETF/RFC-1468","source":"IETF/RFC-1468/RFC-1468.txt","version":null},{"body":"IETF","designation":"RFC 1866","folder":"IETF/RFC-1866","source":"IETF/RFC-1866/RFC-1866.txt","version":null},{"body":"IETF","designation":"RFC 1922","folder":"IETF/RFC-1922","source":"IETF/RFC-1922/RFC-1922.txt","version":null},{"body":"IETF","designation":"RFC 3467","folder":"IETF/RFC-3467","source":"IETF/RFC-3467/RFC-3467.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4646","folder":"IETF/RFC-4646","source":"IETF/RFC-4646/RFC-4646.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5646","folder":"IETF/RFC-5646","source":"IETF/RFC-5646/RFC-5646.txt","version":null},{"body":"IETF","designation":"RFC 6365","folder":"IETF/RFC-6365","source":"IETF/RFC-6365/RFC-6365.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 646 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7498-1 V1994","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7498-1","version":"1994","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7498-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7498-1"],"folder":"ISO-IEC/ISO-IEC-7498-1-V1994","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2130","folder":"IETF/RFC-2130","source":"IETF/RFC-2130/RFC-2130.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 7498-1 1994 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7498-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7498-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7498-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7498-2"],"folder":"ISO-IEC/ISO-IEC-7498-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ISO-IEC ISO/IEC 7498-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7498-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7498-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7498-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7498-4"],"folder":"ISO-IEC/ISO-IEC-7498-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 7498-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7499-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7499-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7499-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7499-2"],"folder":"ISO-IEC/ISO-IEC-7499-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 7499-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7812-1 V2006","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7812-1","version":"2006","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7812-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7812-1"],"folder":"ISO-IEC/ISO-IEC-7812-1-V2006","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 6030","folder":"IETF/RFC-6030","source":"IETF/RFC-6030/RFC-6030.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6920","folder":"IETF/RFC-6920","source":"IETF/RFC-6920/RFC-6920.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 7812-1 2006 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 7812-2 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 7812-2","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+7812-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+7812-2"],"folder":"ISO-IEC/ISO-IEC-7812-2-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 7812-2 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8073","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8073","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8073","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8073"],"folder":"ISO-IEC/ISO-IEC-8073","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2883","folder":"IETF/RFC-2883","source":"IETF/RFC-2883/RFC-2883.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8073 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8208","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8208","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8208","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8208"],"folder":"ISO-IEC/ISO-IEC-8208","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1382","folder":"IETF/RFC-1382","source":"IETF/RFC-1382/RFC-1382.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null},{"body":"IETF","designation":"RFC 5024","folder":"IETF/RFC-5024","source":"IETF/RFC-5024/RFC-5024.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8208 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8348","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8348","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8348","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8348"],"folder":"ISO-IEC/ISO-IEC-8348","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1768","folder":"IETF/RFC-1768","source":"IETF/RFC-1768/RFC-1768.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 4715","folder":"IETF/RFC-4715","source":"IETF/RFC-4715/RFC-4715.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8348 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8348-1992","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8348-1992","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8348-1992","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8348-1992"],"folder":"ISO-IEC/ISO-IEC-8348-1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8348-1992 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8473","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8473","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8473","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8473"],"folder":"ISO-IEC/ISO-IEC-8473","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null},{"body":"IETF","designation":"RFC 1752","folder":"IETF/RFC-1752","source":"IETF/RFC-1752/RFC-1752.txt","version":null},{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8473 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8473-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8473-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8473-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8473-1"],"folder":"ISO-IEC/ISO-IEC-8473-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3719","folder":"IETF/RFC-3719","source":"IETF/RFC-3719/RFC-3719.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8473-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8473-1992","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8473-1992","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8473-1992","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8473-1992"],"folder":"ISO-IEC/ISO-IEC-8473-1992","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8473-1992 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8802","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8802","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8802","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8802"],"folder":"ISO-IEC/ISO-IEC-8802","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8802 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8802-2","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8802-2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8802-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8802-2"],"folder":"ISO-IEC/ISO-IEC-8802-2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8802-2 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8802-3 V2000","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8802-3","version":"2000","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8802-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8802-3"],"folder":"ISO-IEC/ISO-IEC-8802-3-V2000","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2464","folder":"IETF/RFC-2464","source":"IETF/RFC-2464/RFC-2464.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 2889","folder":"IETF/RFC-2889","source":"IETF/RFC-2889/RFC-2889.txt","version":null},{"body":"IETF","designation":"RFC 3580","folder":"IETF/RFC-3580","source":"IETF/RFC-3580/RFC-3580.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 4326","folder":"IETF/RFC-4326","source":"IETF/RFC-4326/RFC-4326.txt","version":null},{"body":"IETF","designation":"RFC 4448","folder":"IETF/RFC-4448","source":"IETF/RFC-4448/RFC-4448.txt","version":null},{"body":"IETF","designation":"RFC 4947","folder":"IETF/RFC-4947","source":"IETF/RFC-4947/RFC-4947.txt","version":null},{"body":"IETF","designation":"RFC 5163","folder":"IETF/RFC-5163","source":"IETF/RFC-5163/RFC-5163.txt","version":null},{"body":"IETF","designation":"RFC 5184","folder":"IETF/RFC-5184","source":"IETF/RFC-5184/RFC-5184.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8802-3 2000 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8802-5","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8802-5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8802-5","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8802-5"],"folder":"ISO-IEC/ISO-IEC-8802-5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1749","folder":"IETF/RFC-1749","source":"IETF/RFC-1749/RFC-1749.txt","version":null},{"body":"IETF","designation":"RFC 2475","folder":"IETF/RFC-2475","source":"IETF/RFC-2475/RFC-2475.txt","version":null},{"body":"IETF","designation":"RFC 2816","folder":"IETF/RFC-2816","source":"IETF/RFC-2816/RFC-2816.txt","version":null},{"body":"IETF","designation":"RFC 3927","folder":"IETF/RFC-3927","source":"IETF/RFC-3927/RFC-3927.txt","version":null},{"body":"IETF","designation":"RFC 5227","folder":"IETF/RFC-5227","source":"IETF/RFC-5227/RFC-5227.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8802-5 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8824","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8824","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8824","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8824"],"folder":"ISO-IEC/ISO-IEC-8824","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1508","folder":"IETF/RFC-1508","source":"IETF/RFC-1508/RFC-1508.txt","version":null},{"body":"IETF","designation":"RFC 2078","folder":"IETF/RFC-2078","source":"IETF/RFC-2078/RFC-2078.txt","version":null},{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6487","folder":"IETF/RFC-6487","source":"IETF/RFC-6487/RFC-6487.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8824 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8824-1 V2021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8824-1","version":"2021","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8824-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8824-1"],"folder":"ISO-IEC/ISO-IEC-8824-1-V2021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4520","folder":"IETF/RFC-4520","source":"IETF/RFC-4520/RFC-4520.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.pdf","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8824-1 2021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8824-2 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8824-2","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8824-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8824-2"],"folder":"ISO-IEC/ISO-IEC-8824-2-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8824-2 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8824-3 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8824-3","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8824-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8824-3"],"folder":"ISO-IEC/ISO-IEC-8824-3-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8824-3 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8824-4 V2015","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8824-4","version":"2015","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8824-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8824-4"],"folder":"ISO-IEC/ISO-IEC-8824-4-V2015","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2898","folder":"IETF/RFC-2898","source":"IETF/RFC-2898/RFC-2898.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6278","folder":"IETF/RFC-6278","source":"IETF/RFC-6278/RFC-6278.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8018","folder":"IETF/RFC-8018","source":"IETF/RFC-8018/RFC-8018.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8824-4 2015 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 88247-3 V2008","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 88247-3","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+88247-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+88247-3"],"folder":"ISO-IEC/ISO-IEC-88247-3-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 88247-3 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8825-1-2021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8825-1-2021","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8825-1-2021","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8825-1-2021"],"folder":"ISO-IEC/ISO-IEC-8825-1-2021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8825-1-2021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8825-1 V2021","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8825-1","version":"2021","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8825-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8825-1"],"folder":"ISO-IEC/ISO-IEC-8825-1-V2021","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3161","folder":"IETF/RFC-3161","source":"IETF/RFC-3161/RFC-3161.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4523","folder":"IETF/RFC-4523","source":"IETF/RFC-4523/RFC-4523.txt","version":null},{"body":"IETF","designation":"RFC 4531","folder":"IETF/RFC-4531","source":"IETF/RFC-4531/RFC-4531.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5326","folder":"IETF/RFC-5326","source":"IETF/RFC-5326/RFC-5326.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 6256","folder":"IETF/RFC-6256","source":"IETF/RFC-6256/RFC-6256.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9345","folder":"IETF/RFC-9345","source":"IETF/RFC-9345/RFC-9345.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8825-1 2021 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8825-2 V2002","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8825-2","version":"2002","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8825-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8825-2"],"folder":"ISO-IEC/ISO-IEC-8825-2-V2002","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8825-2 2002 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8825 V1987","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8825","version":"1987","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8825","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8825"],"folder":"ISO-IEC/ISO-IEC-8825-V1987","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1508","folder":"IETF/RFC-1508","source":"IETF/RFC-1508/RFC-1508.txt","version":null},{"body":"IETF","designation":"RFC 1698","folder":"IETF/RFC-1698","source":"IETF/RFC-1698/RFC-1698.txt","version":null},{"body":"IETF","designation":"RFC 2078","folder":"IETF/RFC-2078","source":"IETF/RFC-2078/RFC-2078.txt","version":null},{"body":"IETF","designation":"RFC 2743","folder":"IETF/RFC-2743","source":"IETF/RFC-2743/RFC-2743.txt","version":null},{"body":"IETF","designation":"RFC 5050","folder":"IETF/RFC-5050","source":"IETF/RFC-5050/RFC-5050.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8825 1987 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859"],"folder":"ISO-IEC/ISO-IEC-8859","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-1 V1998","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-1","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-1"],"folder":"ISO-IEC/ISO-IEC-8859-1-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2566","folder":"IETF/RFC-2566","source":"IETF/RFC-2566/RFC-2566.txt","version":null},{"body":"IETF","designation":"RFC 2911","folder":"IETF/RFC-2911","source":"IETF/RFC-2911/RFC-2911.txt","version":null},{"body":"IETF","designation":"RFC 3875","folder":"IETF/RFC-3875","source":"IETF/RFC-3875/RFC-3875.txt","version":null},{"body":"IETF","designation":"RFC 3977","folder":"IETF/RFC-3977","source":"IETF/RFC-3977/RFC-3977.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5987","folder":"IETF/RFC-5987","source":"IETF/RFC-5987/RFC-5987.txt","version":null},{"body":"IETF","designation":"RFC 6266","folder":"IETF/RFC-6266","source":"IETF/RFC-6266/RFC-6266.txt","version":null},{"body":"IETF","designation":"RFC 6331","folder":"IETF/RFC-6331","source":"IETF/RFC-6331/RFC-6331.txt","version":null},{"body":"IETF","designation":"RFC 7230","folder":"IETF/RFC-7230","source":"IETF/RFC-7230/RFC-7230.txt","version":null},{"body":"IETF","designation":"RFC 7617","folder":"IETF/RFC-7617","source":"IETF/RFC-7617/RFC-7617.txt","version":null},{"body":"IETF","designation":"RFC 9110","folder":"IETF/RFC-9110","source":"IETF/RFC-9110/RFC-9110.pdf","version":null},{"body":"IETF","designation":"RFC 9285","folder":"IETF/RFC-9285","source":"IETF/RFC-9285/RFC-9285.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-1 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-10 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-10","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-10","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-10"],"folder":"ISO-IEC/ISO-IEC-8859-10-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-10 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-13 V1998","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-13","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-13","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-13"],"folder":"ISO-IEC/ISO-IEC-8859-13-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-13 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-14 V1998","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-14","version":"1998","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-14","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-14"],"folder":"ISO-IEC/ISO-IEC-8859-14-V1998","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-14 1998 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-15 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-15","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-15","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-15"],"folder":"ISO-IEC/ISO-IEC-8859-15-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-15 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-16 V2001","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-16","version":"2001","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-16","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-16"],"folder":"ISO-IEC/ISO-IEC-8859-16-V2001","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-16 2001 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-6 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-6","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-6","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-6"],"folder":"ISO-IEC/ISO-IEC-8859-6-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-6 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-7 V2003","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-7","version":"2003","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-7","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-7"],"folder":"ISO-IEC/ISO-IEC-8859-7-V2003","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-7 2003 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-8 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-8","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-8","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-8"],"folder":"ISO-IEC/ISO-IEC-8859-8-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2640","folder":"IETF/RFC-2640","source":"IETF/RFC-2640/RFC-2640.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-8 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 8859-9 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 8859-9","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+8859-9","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+8859-9"],"folder":"ISO-IEC/ISO-IEC-8859-9-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2049","folder":"IETF/RFC-2049","source":"IETF/RFC-2049/RFC-2049.txt","version":null},{"body":"IETF","designation":"RFC 2278","folder":"IETF/RFC-2278","source":"IETF/RFC-2278/RFC-2278.txt","version":null},{"body":"IETF","designation":"RFC 2978","folder":"IETF/RFC-2978","source":"IETF/RFC-2978/RFC-2978.txt","version":null},{"body":"IETF","designation":"RFC 6055","folder":"IETF/RFC-6055","source":"IETF/RFC-6055/RFC-6055.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 8859-9 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9070 V1991","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9070","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9070","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9070"],"folder":"ISO-IEC/ISO-IEC-9070-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2445","folder":"IETF/RFC-2445","source":"IETF/RFC-2445/RFC-2445.txt","version":null},{"body":"IETF","designation":"RFC 3151","folder":"IETF/RFC-3151","source":"IETF/RFC-3151/RFC-3151.txt","version":null},{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9070 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9075-2 V1999","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9075-2","version":"1999","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9075-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9075-2"],"folder":"ISO-IEC/ISO-IEC-9075-2-V1999","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5323","folder":"IETF/RFC-5323","source":"IETF/RFC-5323/RFC-5323.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9075-2 1999 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9075-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9075-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9075-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9075-3"],"folder":"ISO-IEC/ISO-IEC-9075-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5141","folder":"IETF/RFC-5141","source":"IETF/RFC-5141/RFC-5141.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9075-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9314","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9314","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9314","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9314"],"folder":"ISO-IEC/ISO-IEC-9314","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4297","folder":"IETF/RFC-4297","source":"IETF/RFC-4297/RFC-4297.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9314 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9495","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9495","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9495","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9495"],"folder":"ISO-IEC/ISO-IEC-9495","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9495 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9542 V1988","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9542","version":"1988","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9542","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9542"],"folder":"ISO-IEC/ISO-IEC-9542-V1988","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1356","folder":"IETF/RFC-1356","source":"IETF/RFC-1356/RFC-1356.txt","version":null},{"body":"IETF","designation":"RFC 1561","folder":"IETF/RFC-1561","source":"IETF/RFC-1561/RFC-1561.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9542 1988 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9577","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9577","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9577","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9577"],"folder":"ISO-IEC/ISO-IEC-9577","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6213","folder":"IETF/RFC-6213","source":"IETF/RFC-6213/RFC-6213.txt","version":null},{"body":"IETF","designation":"RFC 6328","folder":"IETF/RFC-6328","source":"IETF/RFC-6328/RFC-6328.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9577 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594"],"folder":"ISO-IEC/ISO-IEC-9594","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1292","folder":"IETF/RFC-1292","source":"IETF/RFC-1292/RFC-1292.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4524","folder":"IETF/RFC-4524","source":"IETF/RFC-4524/RFC-4524.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-1 V2017","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-1","version":"2017","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-1"],"folder":"ISO-IEC/ISO-IEC-9594-1-V2017","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3698","folder":"IETF/RFC-3698","source":"IETF/RFC-3698/RFC-3698.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4512","folder":"IETF/RFC-4512","source":"IETF/RFC-4512/RFC-4512.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-1 2017 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-2 V2005","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-2","version":"2005","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-2"],"folder":"ISO-IEC/ISO-IEC-9594-2-V2005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-2 2005 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-3 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-3","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-3"],"folder":"ISO-IEC/ISO-IEC-9594-3-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4510","folder":"IETF/RFC-4510","source":"IETF/RFC-4510/RFC-4510.txt","version":null},{"body":"IETF","designation":"RFC 4514","folder":"IETF/RFC-4514","source":"IETF/RFC-4514/RFC-4514.txt","version":null},{"body":"IETF","designation":"RFC 4521","folder":"IETF/RFC-4521","source":"IETF/RFC-4521/RFC-4521.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-3 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-4 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-4","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-4"],"folder":"ISO-IEC/ISO-IEC-9594-4-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2120","folder":"IETF/RFC-2120","source":"IETF/RFC-2120/RFC-2120.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-4 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-6 V2008","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-6","version":"2008","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-6","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-6"],"folder":"ISO-IEC/ISO-IEC-9594-6-V2008","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4518","folder":"IETF/RFC-4518","source":"IETF/RFC-4518/RFC-4518.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-6 2008 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-7 V1997","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-7","version":"1997","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-7","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-7"],"folder":"ISO-IEC/ISO-IEC-9594-7-V1997","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-7 1997 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-8 V2020","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-8","version":"2020","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-8","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-8"],"folder":"ISO-IEC/ISO-IEC-9594-8-V2020","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 102-1","folder":"ETSI/EN-319-102-1-V1.4.1","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 411-2","folder":"ETSI/EN-319-411-2-V2.6.1","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf","version":"2.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 412-3","folder":"ETSI/EN-319-412-3-V1.3.1","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.6.0","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","version":"2.6.0"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.1.1","source":"ETSI/TS-119-412-6-V1.1.1/TS-119-412-6-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.2.1","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2407","folder":"IETF/RFC-2407","source":"IETF/RFC-2407/RFC-2407.txt","version":null},{"body":"IETF","designation":"RFC 2510","folder":"IETF/RFC-2510","source":"IETF/RFC-2510/RFC-2510.txt","version":null},{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 2608","folder":"IETF/RFC-2608","source":"IETF/RFC-2608/RFC-2608.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2752","folder":"IETF/RFC-2752","source":"IETF/RFC-2752/RFC-2752.txt","version":null},{"body":"IETF","designation":"RFC 2801","folder":"IETF/RFC-2801","source":"IETF/RFC-2801/RFC-2801.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2985","folder":"IETF/RFC-2985","source":"IETF/RFC-2985/RFC-2985.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3182","folder":"IETF/RFC-3182","source":"IETF/RFC-3182/RFC-3182.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 3520","folder":"IETF/RFC-3520","source":"IETF/RFC-3520/RFC-3520.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5091","folder":"IETF/RFC-5091","source":"IETF/RFC-5091/RFC-5091.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 7292","folder":"IETF/RFC-7292","source":"IETF/RFC-7292/RFC-7292.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null},{"body":"IETF","designation":"RFC 8122","folder":"IETF/RFC-8122","source":"IETF/RFC-8122/RFC-8122.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-8 2020 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9594-9 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9594-9","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9594-9","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9594-9"],"folder":"ISO-IEC/ISO-IEC-9594-9-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2120","folder":"IETF/RFC-2120","source":"IETF/RFC-2120/RFC-2120.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9594-9 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9796-1","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9796-1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9796-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9796-1"],"folder":"ISO-IEC/ISO-IEC-9796-1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9796-1 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9796-2 V2010","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9796-2","version":"2010","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9796-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9796-2"],"folder":"ISO-IEC/ISO-IEC-9796-2-V2010","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 102 176-1","folder":"ETSI/TS-102-176-1-V2.0.0","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf","version":"2.0.0"},{"body":"IETF","designation":"RFC 3447","folder":"IETF/RFC-3447","source":"IETF/RFC-3447/RFC-3447.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 8017","folder":"IETF/RFC-8017","source":"IETF/RFC-8017/RFC-8017.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9796-2 2010 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9796-4","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9796-4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9796-4","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9796-4"],"folder":"ISO-IEC/ISO-IEC-9796-4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9796-4 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9796 V1991","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9796","version":"1991","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9796","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9796"],"folder":"ISO-IEC/ISO-IEC-9796-V1991","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 5832","folder":"IETF/RFC-5832","source":"IETF/RFC-5832/RFC-5832.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9796 1991 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9798","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9798","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9798","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9798"],"folder":"ISO-IEC/ISO-IEC-9798","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9101","folder":"IETF/RFC-9101","source":"IETF/RFC-9101/RFC-9101.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9798 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9798-3","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9798-3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9798-3","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9798-3"],"folder":"ISO-IEC/ISO-IEC-9798-3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2025","folder":"IETF/RFC-2025","source":"IETF/RFC-2025/RFC-2025.txt","version":null},{"body":"IETF","designation":"RFC 3830","folder":"IETF/RFC-3830","source":"IETF/RFC-3830/RFC-3830.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9798-3 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9834-1 V2005","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9834-1","version":"2005","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9834-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9834-1"],"folder":"ISO-IEC/ISO-IEC-9834-1-V2005","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1430","folder":"IETF/RFC-1430","source":"IETF/RFC-1430/RFC-1430.txt","version":null},{"body":"IETF","designation":"RFC 3001","folder":"IETF/RFC-3001","source":"IETF/RFC-3001/RFC-3001.txt","version":null},{"body":"IETF","designation":"RFC 3061","folder":"IETF/RFC-3061","source":"IETF/RFC-3061/RFC-3061.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9834-1 2005 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9834-8 V2004","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9834-8","version":"2004","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9834-8","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9834-8"],"folder":"ISO-IEC/ISO-IEC-9834-8-V2004","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4122","folder":"IETF/RFC-4122","source":"IETF/RFC-4122/RFC-4122.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9834-8 2004 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9899 V2024","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9899","version":"2024","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9899","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9899"],"folder":"ISO-IEC/ISO-IEC-9899-V2024","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2244","folder":"IETF/RFC-2244","source":"IETF/RFC-2244/RFC-2244.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 4997","folder":"IETF/RFC-4997","source":"IETF/RFC-4997/RFC-4997.txt","version":null},{"body":"IETF","designation":"RFC 5137","folder":"IETF/RFC-5137","source":"IETF/RFC-5137/RFC-5137.txt","version":null},{"body":"IETF","designation":"RFC 6386","folder":"IETF/RFC-6386","source":"IETF/RFC-6386/RFC-6386.txt","version":null},{"body":"IETF","designation":"RFC 6557","folder":"IETF/RFC-6557","source":"IETF/RFC-6557/RFC-6557.txt","version":null},{"body":"IETF","designation":"RFC 8746","folder":"IETF/RFC-8746","source":"IETF/RFC-8746/RFC-8746.pdf","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9741","folder":"IETF/RFC-9741","source":"IETF/RFC-9741/RFC-9741.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9899 2024 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9945-1 V1990","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9945-1","version":"1990","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9945-1","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9945-1"],"folder":"ISO-IEC/ISO-IEC-9945-1-V1990","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2307","folder":"IETF/RFC-2307","source":"IETF/RFC-2307/RFC-2307.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9945-1 1990 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9945-2 V1993","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9945-2","version":"1993","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9945-2","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9945-2"],"folder":"ISO-IEC/ISO-IEC-9945-2-V1993","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1345","folder":"IETF/RFC-1345","source":"IETF/RFC-1345/RFC-1345.txt","version":null},{"body":"IETF","designation":"RFC 2277","folder":"IETF/RFC-2277","source":"IETF/RFC-2277/RFC-2277.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9945-2 1993 nested-reference unavailable"},{"id":"ISO-IEC ISO/IEC 9945 V2009","type":"specification","body":"ISO-IEC","designation":"ISO/IEC 9945","version":"2009","title":null,"purpose":null,"status":"unavailable","download_url":"https://www.iso.org/search.html?q=ISO%2FIEC+9945","download_urls":["https://www.iso.org/search.html?q=ISO%2FIEC+9945"],"folder":"ISO-IEC/ISO-IEC-9945-V2009","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3493","folder":"IETF/RFC-3493","source":"IETF/RFC-3493/RFC-3493.txt","version":null},{"body":"IETF","designation":"RFC 3542","folder":"IETF/RFC-3542","source":"IETF/RFC-3542/RFC-3542.txt","version":null},{"body":"IETF","designation":"RFC 3678","folder":"IETF/RFC-3678","source":"IETF/RFC-3678/RFC-3678.txt","version":null},{"body":"IETF","designation":"RFC 4795","folder":"IETF/RFC-4795","source":"IETF/RFC-4795/RFC-4795.txt","version":null},{"body":"IETF","designation":"RFC 5405","folder":"IETF/RFC-5405","source":"IETF/RFC-5405/RFC-5405.txt","version":null},{"body":"IETF","designation":"RFC 5482","folder":"IETF/RFC-5482","source":"IETF/RFC-5482/RFC-5482.txt","version":null},{"body":"IETF","designation":"RFC 6434","folder":"IETF/RFC-6434","source":"IETF/RFC-6434/RFC-6434.txt","version":null},{"body":"IETF","designation":"RFC 8085","folder":"IETF/RFC-8085","source":"IETF/RFC-8085/RFC-8085.txt","version":null}],"search_text":"ISO-IEC ISO/IEC 9945 2009 nested-reference unavailable"},{"id":"ITU-T ITU-T E.106","type":"specification","body":"ITU-T","designation":"ITU-T E.106","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-106/en","download_urls":["https://www.itu.int/rec/T-REC-E-106/en"],"folder":"ITU-T/ITU-T-E.106","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3689","folder":"IETF/RFC-3689","source":"IETF/RFC-3689/RFC-3689.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"ITU-T ITU-T E.106 nested-reference unavailable"},{"id":"ITU-T ITU-T E.123","type":"specification","body":"ITU-T","designation":"ITU-T E.123","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-123/en","download_urls":["https://www.itu.int/rec/T-REC-E-123/en"],"folder":"ITU-T/ITU-T-E.123","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2007","folder":"IETF/RFC-2007","source":"IETF/RFC-2007/RFC-2007.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 3966","folder":"IETF/RFC-3966","source":"IETF/RFC-3966/RFC-3966.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null}],"search_text":"ITU-T ITU-T E.123 nested-reference unavailable"},{"id":"ITU-T ITU-T E.163","type":"specification","body":"ITU-T","designation":"ITU-T E.163","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-163/en","download_urls":["https://www.itu.int/rec/T-REC-E-163/en"],"folder":"ITU-T/ITU-T-E.163","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null}],"search_text":"ITU-T ITU-T E.163 nested-reference unavailable"},{"id":"ITU-T ITU-T E.164","type":"specification","body":"ITU-T","designation":"ITU-T E.164","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-164/en","download_urls":["https://www.itu.int/rec/T-REC-E-164/en"],"folder":"ITU-T/ITU-T-E.164","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null},{"body":"IETF","designation":"RFC 2590","folder":"IETF/RFC-2590","source":"IETF/RFC-2590/RFC-2590.txt","version":null},{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 3172","folder":"IETF/RFC-3172","source":"IETF/RFC-3172/RFC-3172.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null},{"body":"IETF","designation":"RFC 3733","folder":"IETF/RFC-3733","source":"IETF/RFC-3733/RFC-3733.txt","version":null},{"body":"IETF","designation":"RFC 3761","folder":"IETF/RFC-3761","source":"IETF/RFC-3761/RFC-3761.txt","version":null},{"body":"IETF","designation":"RFC 3982","folder":"IETF/RFC-3982","source":"IETF/RFC-3982/RFC-3982.txt","version":null},{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 4497","folder":"IETF/RFC-4497","source":"IETF/RFC-4497/RFC-4497.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4566","folder":"IETF/RFC-4566","source":"IETF/RFC-4566/RFC-4566.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7970","folder":"IETF/RFC-7970","source":"IETF/RFC-7970/RFC-7970.txt","version":null},{"body":"IETF","designation":"RFC 8224","folder":"IETF/RFC-8224","source":"IETF/RFC-8224/RFC-8224.txt","version":null},{"body":"IETF","designation":"RFC 8866","folder":"IETF/RFC-8866","source":"IETF/RFC-8866/RFC-8866.txt","version":null}],"search_text":"ITU-T ITU-T E.164 nested-reference unavailable"},{"id":"ITU-T ITU-T E.180","type":"specification","body":"ITU-T","designation":"ITU-T E.180","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-180/en","download_urls":["https://www.itu.int/rec/T-REC-E-180/en"],"folder":"ITU-T/ITU-T-E.180","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null}],"search_text":"ITU-T ITU-T E.180 nested-reference unavailable"},{"id":"ITU-T ITU-T E.182","type":"specification","body":"ITU-T","designation":"ITU-T E.182","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-182/en","download_urls":["https://www.itu.int/rec/T-REC-E-182/en"],"folder":"ITU-T/ITU-T-E.182","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7462","folder":"IETF/RFC-7462","source":"IETF/RFC-7462/RFC-7462.txt","version":null}],"search_text":"ITU-T ITU-T E.182 nested-reference unavailable"},{"id":"ITU-T ITU-T E.212","type":"specification","body":"ITU-T","designation":"ITU-T E.212","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-212/en","download_urls":["https://www.itu.int/rec/T-REC-E-212/en"],"folder":"ITU-T/ITU-T-E.212","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4006","folder":"IETF/RFC-4006","source":"IETF/RFC-4006/RFC-4006.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null}],"search_text":"ITU-T ITU-T E.212 nested-reference unavailable"},{"id":"ITU-T ITU-T E.361","type":"specification","body":"ITU-T","designation":"ITU-T E.361","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-361/en","download_urls":["https://www.itu.int/rec/T-REC-E-361/en"],"folder":"ITU-T/ITU-T-E.361","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null}],"search_text":"ITU-T ITU-T E.361 nested-reference unavailable"},{"id":"ITU-T ITU-T E.600","type":"specification","body":"ITU-T","designation":"ITU-T E.600","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-600/en","download_urls":["https://www.itu.int/rec/T-REC-E-600/en"],"folder":"ITU-T/ITU-T-E.600","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null}],"search_text":"ITU-T ITU-T E.600 nested-reference unavailable"},{"id":"ITU-T ITU-T E.681","type":"specification","body":"ITU-T","designation":"ITU-T E.681","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-681/en","download_urls":["https://www.itu.int/rec/T-REC-E-681/en"],"folder":"ITU-T/ITU-T-E.681","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null}],"search_text":"ITU-T ITU-T E.681 nested-reference unavailable"},{"id":"ITU-T ITU-T E.701","type":"specification","body":"ITU-T","designation":"ITU-T E.701","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-701/en","download_urls":["https://www.itu.int/rec/T-REC-E-701/en"],"folder":"ITU-T/ITU-T-E.701","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null}],"search_text":"ITU-T ITU-T E.701 nested-reference unavailable"},{"id":"ITU-T ITU-T E.800","type":"specification","body":"ITU-T","designation":"ITU-T E.800","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-800/en","download_urls":["https://www.itu.int/rec/T-REC-E-800/en"],"folder":"ITU-T/ITU-T-E.800","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null}],"search_text":"ITU-T ITU-T E.800 nested-reference unavailable"},{"id":"ITU-T ITU-T E.801","type":"specification","body":"ITU-T","designation":"ITU-T E.801","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-E-801/en","download_urls":["https://www.itu.int/rec/T-REC-E-801/en"],"folder":"ITU-T/ITU-T-E.801","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3272","folder":"IETF/RFC-3272","source":"IETF/RFC-3272/RFC-3272.txt","version":null}],"search_text":"ITU-T ITU-T E.801 nested-reference unavailable"},{"id":"ITU-T ITU-T F.400","type":"specification","body":"ITU-T","designation":"ITU-T F.400","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-F-400/en","download_urls":["https://www.itu.int/rec/T-REC-F-400/en"],"folder":"ITU-T/ITU-T-F.400","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8098","folder":"IETF/RFC-8098","source":"IETF/RFC-8098/RFC-8098.txt","version":null}],"search_text":"ITU-T ITU-T F.400 nested-reference unavailable"},{"id":"ITU-T ITU-T F.700","type":"specification","body":"ITU-T","designation":"ITU-T F.700","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-F-700/en","download_urls":["https://www.itu.int/rec/T-REC-F-700/en"],"folder":"ITU-T/ITU-T-F.700","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null}],"search_text":"ITU-T ITU-T F.700 nested-reference unavailable"},{"id":"ITU-T ITU-T F.703","type":"specification","body":"ITU-T","designation":"ITU-T F.703","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-F-703/en","download_urls":["https://www.itu.int/rec/T-REC-F-703/en"],"folder":"ITU-T/ITU-T-F.703","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null}],"search_text":"ITU-T ITU-T F.703 nested-reference unavailable"},{"id":"ITU-T ITU-T G.101","type":"specification","body":"ITU-T","designation":"ITU-T G.101","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-101/en","download_urls":["https://www.itu.int/rec/T-REC-G-101/en"],"folder":"ITU-T/ITU-T-G.101","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4594","folder":"IETF/RFC-4594","source":"IETF/RFC-4594/RFC-4594.txt","version":null}],"search_text":"ITU-T ITU-T G.101 nested-reference unavailable"},{"id":"ITU-T ITU-T G.102","type":"specification","body":"ITU-T","designation":"ITU-T G.102","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-102/en","download_urls":["https://www.itu.int/rec/T-REC-G-102/en"],"folder":"ITU-T/ITU-T-G.102","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null}],"search_text":"ITU-T ITU-T G.102 nested-reference unavailable"},{"id":"ITU-T ITU-T G.105","type":"specification","body":"ITU-T","designation":"ITU-T G.105","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-105/en","download_urls":["https://www.itu.int/rec/T-REC-G-105/en"],"folder":"ITU-T/ITU-T-G.105","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null}],"search_text":"ITU-T ITU-T G.105 nested-reference unavailable"},{"id":"ITU-T ITU-T G.107","type":"specification","body":"ITU-T","designation":"ITU-T G.107","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-107/en","download_urls":["https://www.itu.int/rec/T-REC-G-107/en"],"folder":"ITU-T/ITU-T-G.107","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 3611","folder":"IETF/RFC-3611","source":"IETF/RFC-3611/RFC-3611.txt","version":null},{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T G.107 nested-reference unavailable"},{"id":"ITU-T ITU-T G.107.1","type":"specification","body":"ITU-T","designation":"ITU-T G.107.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-107-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-107-1/en"],"folder":"ITU-T/ITU-T-G.107.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T G.107.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.108","type":"specification","body":"ITU-T","designation":"ITU-T G.108","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-108/en","download_urls":["https://www.itu.int/rec/T-REC-G-108/en"],"folder":"ITU-T/ITU-T-G.108","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T G.108 nested-reference unavailable"},{"id":"ITU-T ITU-T G.113","type":"specification","body":"ITU-T","designation":"ITU-T G.113","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-113/en","download_urls":["https://www.itu.int/rec/T-REC-G-113/en"],"folder":"ITU-T/ITU-T-G.113","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T G.113 nested-reference unavailable"},{"id":"ITU-T ITU-T G.114","type":"specification","body":"ITU-T","designation":"ITU-T G.114","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-114/en","download_urls":["https://www.itu.int/rec/T-REC-G-114/en"],"folder":"ITU-T/ITU-T-G.114","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 5836","folder":"IETF/RFC-5836","source":"IETF/RFC-5836/RFC-5836.txt","version":null},{"body":"IETF","designation":"RFC 6817","folder":"IETF/RFC-6817","source":"IETF/RFC-6817/RFC-6817.txt","version":null}],"search_text":"ITU-T ITU-T G.114 nested-reference unavailable"},{"id":"ITU-T ITU-T G.117","type":"specification","body":"ITU-T","designation":"ITU-T G.117","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-117/en","download_urls":["https://www.itu.int/rec/T-REC-G-117/en"],"folder":"ITU-T/ITU-T-G.117","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ITU-T ITU-T G.117 nested-reference unavailable"},{"id":"ITU-T ITU-T G.131","type":"specification","body":"ITU-T","designation":"ITU-T G.131","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-131/en","download_urls":["https://www.itu.int/rec/T-REC-G-131/en"],"folder":"ITU-T/ITU-T-G.131","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T G.131 nested-reference unavailable"},{"id":"ITU-T ITU-T G.164","type":"specification","body":"ITU-T","designation":"ITU-T G.164","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-164/en","download_urls":["https://www.itu.int/rec/T-REC-G-164/en"],"folder":"ITU-T/ITU-T-G.164","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T G.164 nested-reference unavailable"},{"id":"ITU-T ITU-T G.165","type":"specification","body":"ITU-T","designation":"ITU-T G.165","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-165/en","download_urls":["https://www.itu.int/rec/T-REC-G-165/en"],"folder":"ITU-T/ITU-T-G.165","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T G.165 nested-reference unavailable"},{"id":"ITU-T ITU-T G.168","type":"specification","body":"ITU-T","designation":"ITU-T G.168","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-168/en","download_urls":["https://www.itu.int/rec/T-REC-G-168/en"],"folder":"ITU-T/ITU-T-G.168","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T G.168 nested-reference unavailable"},{"id":"ITU-T ITU-T G.169","type":"specification","body":"ITU-T","designation":"ITU-T G.169","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-169/en","download_urls":["https://www.itu.int/rec/T-REC-G-169/en"],"folder":"ITU-T/ITU-T-G.169","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T G.169 nested-reference unavailable"},{"id":"ITU-T ITU-T G.177","type":"specification","body":"ITU-T","designation":"ITU-T G.177","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-177/en","download_urls":["https://www.itu.int/rec/T-REC-G-177/en"],"folder":"ITU-T/ITU-T-G.177","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null}],"search_text":"ITU-T ITU-T G.177 nested-reference unavailable"},{"id":"ITU-T ITU-T G.191","type":"specification","body":"ITU-T","designation":"ITU-T G.191","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-191/en","download_urls":["https://www.itu.int/rec/T-REC-G-191/en"],"folder":"ITU-T/ITU-T-G.191","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null}],"search_text":"ITU-T ITU-T G.191 nested-reference unavailable"},{"id":"ITU-T ITU-T G.227","type":"specification","body":"ITU-T","designation":"ITU-T G.227","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-227/en","download_urls":["https://www.itu.int/rec/T-REC-G-227/en"],"folder":"ITU-T/ITU-T-G.227","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ITU-T ITU-T G.227 nested-reference unavailable"},{"id":"ITU-T ITU-T G.691","type":"specification","body":"ITU-T","designation":"ITU-T G.691","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-691/en","download_urls":["https://www.itu.int/rec/T-REC-G-691/en"],"folder":"ITU-T/ITU-T-G.691","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null}],"search_text":"ITU-T ITU-T G.691 nested-reference unavailable"},{"id":"ITU-T ITU-T G.702","type":"specification","body":"ITU-T","designation":"ITU-T G.702","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-702/en","download_urls":["https://www.itu.int/rec/T-REC-G-702/en"],"folder":"ITU-T/ITU-T-G.702","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null}],"search_text":"ITU-T ITU-T G.702 nested-reference unavailable"},{"id":"ITU-T ITU-T G.703","type":"specification","body":"ITU-T","designation":"ITU-T G.703","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-703/en","download_urls":["https://www.itu.int/rec/T-REC-G-703/en"],"folder":"ITU-T/ITU-T-G.703","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"ITU-T ITU-T G.703 nested-reference unavailable"},{"id":"ITU-T ITU-T G.704","type":"specification","body":"ITU-T","designation":"ITU-T G.704","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-704/en","download_urls":["https://www.itu.int/rec/T-REC-G-704/en"],"folder":"ITU-T/ITU-T-G.704","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T G.704 nested-reference unavailable"},{"id":"ITU-T ITU-T G.706","type":"specification","body":"ITU-T","designation":"ITU-T G.706","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-706/en","download_urls":["https://www.itu.int/rec/T-REC-G-706/en"],"folder":"ITU-T/ITU-T-G.706","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null}],"search_text":"ITU-T ITU-T G.706 nested-reference unavailable"},{"id":"ITU-T ITU-T G.707","type":"specification","body":"ITU-T","designation":"ITU-T G.707","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-707/en","download_urls":["https://www.itu.int/rec/T-REC-G-707/en"],"folder":"ITU-T/ITU-T-G.707","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3471","folder":"IETF/RFC-3471","source":"IETF/RFC-3471/RFC-3471.txt","version":null},{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4207","folder":"IETF/RFC-4207","source":"IETF/RFC-4207/RFC-4207.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null}],"search_text":"ITU-T ITU-T G.707 nested-reference unavailable"},{"id":"ITU-T ITU-T G.708","type":"specification","body":"ITU-T","designation":"ITU-T G.708","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-708/en","download_urls":["https://www.itu.int/rec/T-REC-G-708/en"],"folder":"ITU-T/ITU-T-G.708","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null}],"search_text":"ITU-T ITU-T G.708 nested-reference unavailable"},{"id":"ITU-T ITU-T G.709","type":"specification","body":"ITU-T","designation":"ITU-T G.709","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-709/en","download_urls":["https://www.itu.int/rec/T-REC-G-709/en"],"folder":"ITU-T/ITU-T-G.709","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 3945","folder":"IETF/RFC-3945","source":"IETF/RFC-3945/RFC-3945.txt","version":null}],"search_text":"ITU-T ITU-T G.709 nested-reference unavailable"},{"id":"ITU-T ITU-T G.711","type":"specification","body":"ITU-T","designation":"ITU-T G.711","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-711/en","download_urls":["https://www.itu.int/rec/T-REC-G-711/en"],"folder":"ITU-T/ITU-T-G.711","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3714","folder":"IETF/RFC-3714","source":"IETF/RFC-3714/RFC-3714.txt","version":null},{"body":"IETF","designation":"RFC 3951","folder":"IETF/RFC-3951","source":"IETF/RFC-3951/RFC-3951.txt","version":null},{"body":"IETF","designation":"RFC 3952","folder":"IETF/RFC-3952","source":"IETF/RFC-3952/RFC-3952.txt","version":null},{"body":"IETF","designation":"RFC 4504","folder":"IETF/RFC-4504","source":"IETF/RFC-4504/RFC-4504.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 5486","folder":"IETF/RFC-5486","source":"IETF/RFC-5486/RFC-5486.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 6464","folder":"IETF/RFC-6464","source":"IETF/RFC-6464/RFC-6464.txt","version":null},{"body":"IETF","designation":"RFC 6465","folder":"IETF/RFC-6465","source":"IETF/RFC-6465/RFC-6465.txt","version":null},{"body":"IETF","designation":"RFC 7874","folder":"IETF/RFC-7874","source":"IETF/RFC-7874/RFC-7874.txt","version":null}],"search_text":"ITU-T ITU-T G.711 nested-reference unavailable"},{"id":"ITU-T ITU-T G.711.1","type":"specification","body":"ITU-T","designation":"ITU-T G.711.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-711-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-711-1/en"],"folder":"ITU-T/ITU-T-G.711.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8854","folder":"IETF/RFC-8854","source":"IETF/RFC-8854/RFC-8854.txt","version":null}],"search_text":"ITU-T ITU-T G.711.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.719","type":"specification","body":"ITU-T","designation":"ITU-T G.719","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-719/en","download_urls":["https://www.itu.int/rec/T-REC-G-719/en"],"folder":"ITU-T/ITU-T-G.719","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5404","folder":"IETF/RFC-5404","source":"IETF/RFC-5404/RFC-5404.txt","version":null}],"search_text":"ITU-T ITU-T G.719 nested-reference unavailable"},{"id":"ITU-T ITU-T G.722","type":"specification","body":"ITU-T","designation":"ITU-T G.722","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-722/en","download_urls":["https://www.itu.int/rec/T-REC-G-722/en"],"folder":"ITU-T/ITU-T-G.722","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null}],"search_text":"ITU-T ITU-T G.722 nested-reference unavailable"},{"id":"ITU-T ITU-T G.722.1","type":"specification","body":"ITU-T","designation":"ITU-T G.722.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-722-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-722-1/en"],"folder":"ITU-T/ITU-T-G.722.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3047","folder":"IETF/RFC-3047","source":"IETF/RFC-3047/RFC-3047.txt","version":null},{"body":"IETF","designation":"RFC 3389","folder":"IETF/RFC-3389","source":"IETF/RFC-3389/RFC-3389.txt","version":null},{"body":"IETF","designation":"RFC 3794","folder":"IETF/RFC-3794","source":"IETF/RFC-3794/RFC-3794.txt","version":null},{"body":"IETF","designation":"RFC 6366","folder":"IETF/RFC-6366","source":"IETF/RFC-6366/RFC-6366.txt","version":null}],"search_text":"ITU-T ITU-T G.722.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.723.1","type":"specification","body":"ITU-T","designation":"ITU-T G.723.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-723-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-723-1/en"],"folder":"ITU-T/ITU-T-G.723.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null}],"search_text":"ITU-T ITU-T G.723.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.726","type":"specification","body":"ITU-T","designation":"ITU-T G.726","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-726/en","download_urls":["https://www.itu.int/rec/T-REC-G-726/en"],"folder":"ITU-T/ITU-T-G.726","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null}],"search_text":"ITU-T ITU-T G.726 nested-reference unavailable"},{"id":"ITU-T ITU-T G.728","type":"specification","body":"ITU-T","designation":"ITU-T G.728","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-728/en","download_urls":["https://www.itu.int/rec/T-REC-G-728/en"],"folder":"ITU-T/ITU-T-G.728","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1890","folder":"IETF/RFC-1890","source":"IETF/RFC-1890/RFC-1890.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null}],"search_text":"ITU-T ITU-T G.728 nested-reference unavailable"},{"id":"ITU-T ITU-T G.729","type":"specification","body":"ITU-T","designation":"ITU-T G.729","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-729/en","download_urls":["https://www.itu.int/rec/T-REC-G-729/en"],"folder":"ITU-T/ITU-T-G.729","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null}],"search_text":"ITU-T ITU-T G.729 nested-reference unavailable"},{"id":"ITU-T ITU-T G.732","type":"specification","body":"ITU-T","designation":"ITU-T G.732","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-732/en","download_urls":["https://www.itu.int/rec/T-REC-G-732/en"],"folder":"ITU-T/ITU-T-G.732","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"ITU-T ITU-T G.732 nested-reference unavailable"},{"id":"ITU-T ITU-T G.751","type":"specification","body":"ITU-T","designation":"ITU-T G.751","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-751/en","download_urls":["https://www.itu.int/rec/T-REC-G-751/en"],"folder":"ITU-T/ITU-T-G.751","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T G.751 nested-reference unavailable"},{"id":"ITU-T ITU-T G.771","type":"specification","body":"ITU-T","designation":"ITU-T G.771","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-771/en","download_urls":["https://www.itu.int/rec/T-REC-G-771/en"],"folder":"ITU-T/ITU-T-G.771","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3474","folder":"IETF/RFC-3474","source":"IETF/RFC-3474/RFC-3474.txt","version":null},{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 5718","folder":"IETF/RFC-5718","source":"IETF/RFC-5718/RFC-5718.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"ITU-T ITU-T G.771 nested-reference unavailable"},{"id":"ITU-T ITU-T G.775","type":"specification","body":"ITU-T","designation":"ITU-T G.775","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-775/en","download_urls":["https://www.itu.int/rec/T-REC-G-775/en"],"folder":"ITU-T/ITU-T-G.775","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null}],"search_text":"ITU-T ITU-T G.775 nested-reference unavailable"},{"id":"ITU-T ITU-T G.783","type":"specification","body":"ITU-T","designation":"ITU-T G.783","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-783/en","download_urls":["https://www.itu.int/rec/T-REC-G-783/en"],"folder":"ITU-T/ITU-T-G.783","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3498","folder":"IETF/RFC-3498","source":"IETF/RFC-3498/RFC-3498.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null}],"search_text":"ITU-T ITU-T G.783 nested-reference unavailable"},{"id":"ITU-T ITU-T G.784","type":"specification","body":"ITU-T","designation":"ITU-T G.784","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-784/en","download_urls":["https://www.itu.int/rec/T-REC-G-784/en"],"folder":"ITU-T/ITU-T-G.784","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null}],"search_text":"ITU-T ITU-T G.784 nested-reference unavailable"},{"id":"ITU-T ITU-T G.798","type":"specification","body":"ITU-T","designation":"ITU-T G.798","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-798/en","download_urls":["https://www.itu.int/rec/T-REC-G-798/en"],"folder":"ITU-T/ITU-T-G.798","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null}],"search_text":"ITU-T ITU-T G.798 nested-reference unavailable"},{"id":"ITU-T ITU-T G.800","type":"specification","body":"ITU-T","designation":"ITU-T G.800","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-800/en","download_urls":["https://www.itu.int/rec/T-REC-G-800/en"],"folder":"ITU-T/ITU-T-G.800","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7226","folder":"IETF/RFC-7226","source":"IETF/RFC-7226/RFC-7226.txt","version":null}],"search_text":"ITU-T ITU-T G.800 nested-reference unavailable"},{"id":"ITU-T ITU-T G.801","type":"specification","body":"ITU-T","designation":"ITU-T G.801","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-801/en","download_urls":["https://www.itu.int/rec/T-REC-G-801/en"],"folder":"ITU-T/ITU-T-G.801","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null},{"body":"IETF","designation":"RFC 7456","folder":"IETF/RFC-7456","source":"IETF/RFC-7456/RFC-7456.txt","version":null}],"search_text":"ITU-T ITU-T G.801 nested-reference unavailable"},{"id":"ITU-T ITU-T G.802","type":"specification","body":"ITU-T","designation":"ITU-T G.802","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-802/en","download_urls":["https://www.itu.int/rec/T-REC-G-802/en"],"folder":"ITU-T/ITU-T-G.802","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null}],"search_text":"ITU-T ITU-T G.802 nested-reference unavailable"},{"id":"ITU-T ITU-T G.803","type":"specification","body":"ITU-T","designation":"ITU-T G.803","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-803/en","download_urls":["https://www.itu.int/rec/T-REC-G-803/en"],"folder":"ITU-T/ITU-T-G.803","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null},{"body":"IETF","designation":"RFC 4830","folder":"IETF/RFC-4830","source":"IETF/RFC-4830/RFC-4830.txt","version":null},{"body":"IETF","designation":"RFC 7209","folder":"IETF/RFC-7209","source":"IETF/RFC-7209/RFC-7209.txt","version":null}],"search_text":"ITU-T ITU-T G.803 nested-reference unavailable"},{"id":"ITU-T ITU-T G.805","type":"specification","body":"ITU-T","designation":"ITU-T G.805","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-805/en","download_urls":["https://www.itu.int/rec/T-REC-G-805/en"],"folder":"ITU-T/ITU-T-G.805","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3916","folder":"IETF/RFC-3916","source":"IETF/RFC-3916/RFC-3916.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"ITU-T ITU-T G.805 nested-reference unavailable"},{"id":"ITU-T ITU-T G.806","type":"specification","body":"ITU-T","designation":"ITU-T G.806","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-806/en","download_urls":["https://www.itu.int/rec/T-REC-G-806/en"],"folder":"ITU-T/ITU-T-G.806","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null},{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"ITU-T ITU-T G.806 nested-reference unavailable"},{"id":"ITU-T ITU-T G.807","type":"specification","body":"ITU-T","designation":"ITU-T G.807","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-807/en","download_urls":["https://www.itu.int/rec/T-REC-G-807/en"],"folder":"ITU-T/ITU-T-G.807","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null}],"search_text":"ITU-T ITU-T G.807 nested-reference unavailable"},{"id":"ITU-T ITU-T G.808","type":"specification","body":"ITU-T","designation":"ITU-T G.808","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-808/en","download_urls":["https://www.itu.int/rec/T-REC-G-808/en"],"folder":"ITU-T/ITU-T-G.808","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4258","folder":"IETF/RFC-4258","source":"IETF/RFC-4258/RFC-4258.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null}],"search_text":"ITU-T ITU-T G.808 nested-reference unavailable"},{"id":"ITU-T ITU-T G.810","type":"specification","body":"ITU-T","designation":"ITU-T G.810","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-810/en","download_urls":["https://www.itu.int/rec/T-REC-G-810/en"],"folder":"ITU-T/ITU-T-G.810","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"ITU-T ITU-T G.810 nested-reference unavailable"},{"id":"ITU-T ITU-T G.811","type":"specification","body":"ITU-T","designation":"ITU-T G.811","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-811/en","download_urls":["https://www.itu.int/rec/T-REC-G-811/en"],"folder":"ITU-T/ITU-T-G.811","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null}],"search_text":"ITU-T ITU-T G.811 nested-reference unavailable"},{"id":"ITU-T ITU-T G.813","type":"specification","body":"ITU-T","designation":"ITU-T G.813","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-813/en","download_urls":["https://www.itu.int/rec/T-REC-G-813/en"],"folder":"ITU-T/ITU-T-G.813","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null}],"search_text":"ITU-T ITU-T G.813 nested-reference unavailable"},{"id":"ITU-T ITU-T G.821","type":"specification","body":"ITU-T","designation":"ITU-T G.821","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-821/en","download_urls":["https://www.itu.int/rec/T-REC-G-821/en"],"folder":"ITU-T/ITU-T-G.821","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"ITU-T ITU-T G.821 nested-reference unavailable"},{"id":"ITU-T ITU-T G.823","type":"specification","body":"ITU-T","designation":"ITU-T G.823","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-823/en","download_urls":["https://www.itu.int/rec/T-REC-G-823/en"],"folder":"ITU-T/ITU-T-G.823","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T G.823 nested-reference unavailable"},{"id":"ITU-T ITU-T G.824","type":"specification","body":"ITU-T","designation":"ITU-T G.824","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-824/en","download_urls":["https://www.itu.int/rec/T-REC-G-824/en"],"folder":"ITU-T/ITU-T-G.824","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T G.824 nested-reference unavailable"},{"id":"ITU-T ITU-T G.825","type":"specification","body":"ITU-T","designation":"ITU-T G.825","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-825/en","download_urls":["https://www.itu.int/rec/T-REC-G-825/en"],"folder":"ITU-T/ITU-T-G.825","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4842","folder":"IETF/RFC-4842","source":"IETF/RFC-4842/RFC-4842.txt","version":null}],"search_text":"ITU-T ITU-T G.825 nested-reference unavailable"},{"id":"ITU-T ITU-T G.826","type":"specification","body":"ITU-T","designation":"ITU-T G.826","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-826/en","download_urls":["https://www.itu.int/rec/T-REC-G-826/en"],"folder":"ITU-T/ITU-T-G.826","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2495","folder":"IETF/RFC-2495","source":"IETF/RFC-2495/RFC-2495.txt","version":null},{"body":"IETF","designation":"RFC 2558","folder":"IETF/RFC-2558","source":"IETF/RFC-2558/RFC-2558.txt","version":null},{"body":"IETF","designation":"RFC 3592","folder":"IETF/RFC-3592","source":"IETF/RFC-3592/RFC-3592.txt","version":null},{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4553","folder":"IETF/RFC-4553","source":"IETF/RFC-4553/RFC-4553.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5086","folder":"IETF/RFC-5086","source":"IETF/RFC-5086/RFC-5086.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 7893","folder":"IETF/RFC-7893","source":"IETF/RFC-7893/RFC-7893.txt","version":null}],"search_text":"ITU-T ITU-T G.826 nested-reference unavailable"},{"id":"ITU-T ITU-T G.832","type":"specification","body":"ITU-T","designation":"ITU-T G.832","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-832/en","download_urls":["https://www.itu.int/rec/T-REC-G-832/en"],"folder":"ITU-T/ITU-T-G.832","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3946","folder":"IETF/RFC-3946","source":"IETF/RFC-3946/RFC-3946.txt","version":null}],"search_text":"ITU-T ITU-T G.832 nested-reference unavailable"},{"id":"ITU-T ITU-T G.841","type":"specification","body":"ITU-T","designation":"ITU-T G.841","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-841/en","download_urls":["https://www.itu.int/rec/T-REC-G-841/en"],"folder":"ITU-T/ITU-T-G.841","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5317","folder":"IETF/RFC-5317","source":"IETF/RFC-5317/RFC-5317.pdf","version":null}],"search_text":"ITU-T ITU-T G.841 nested-reference unavailable"},{"id":"ITU-T ITU-T G.860","type":"specification","body":"ITU-T","designation":"ITU-T G.860","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-860/en","download_urls":["https://www.itu.int/rec/T-REC-G-860/en"],"folder":"ITU-T/ITU-T-G.860","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"ITU-T ITU-T G.860 nested-reference unavailable"},{"id":"ITU-T ITU-T G.872","type":"specification","body":"ITU-T","designation":"ITU-T G.872","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-872/en","download_urls":["https://www.itu.int/rec/T-REC-G-872/en"],"folder":"ITU-T/ITU-T-G.872","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null},{"body":"IETF","designation":"RFC 4397","folder":"IETF/RFC-4397","source":"IETF/RFC-4397/RFC-4397.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"ITU-T ITU-T G.872 nested-reference unavailable"},{"id":"ITU-T ITU-T G.874","type":"specification","body":"ITU-T","designation":"ITU-T G.874","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-874/en","download_urls":["https://www.itu.int/rec/T-REC-G-874/en"],"folder":"ITU-T/ITU-T-G.874","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null}],"search_text":"ITU-T ITU-T G.874 nested-reference unavailable"},{"id":"ITU-T ITU-T G.874.1","type":"specification","body":"ITU-T","designation":"ITU-T G.874.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-874-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-874-1/en"],"folder":"ITU-T/ITU-T-G.874.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null}],"search_text":"ITU-T ITU-T G.874.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.948","type":"specification","body":"ITU-T","designation":"ITU-T G.948","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-948/en","download_urls":["https://www.itu.int/rec/T-REC-G-948/en"],"folder":"ITU-T/ITU-T-G.948","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ITU-T ITU-T G.948 nested-reference unavailable"},{"id":"ITU-T ITU-T G.957","type":"specification","body":"ITU-T","designation":"ITU-T G.957","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-957/en","download_urls":["https://www.itu.int/rec/T-REC-G-957/en"],"folder":"ITU-T/ITU-T-G.957","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3591","folder":"IETF/RFC-3591","source":"IETF/RFC-3591/RFC-3591.txt","version":null}],"search_text":"ITU-T ITU-T G.957 nested-reference unavailable"},{"id":"ITU-T ITU-T G.984.2","type":"specification","body":"ITU-T","designation":"ITU-T G.984.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-984-2/en","download_urls":["https://www.itu.int/rec/T-REC-G-984-2/en"],"folder":"ITU-T/ITU-T-G.984.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ITU-T ITU-T G.984.2 nested-reference unavailable"},{"id":"ITU-T ITU-T G.989","type":"specification","body":"ITU-T","designation":"ITU-T G.989","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-989/en","download_urls":["https://www.itu.int/rec/T-REC-G-989/en"],"folder":"ITU-T/ITU-T-G.989","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ITU-T ITU-T G.989 nested-reference unavailable"},{"id":"ITU-T ITU-T G.991.2","type":"specification","body":"ITU-T","designation":"ITU-T G.991.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-991-2/en","download_urls":["https://www.itu.int/rec/T-REC-G-991-2/en"],"folder":"ITU-T/ITU-T-G.991.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3276","folder":"IETF/RFC-3276","source":"IETF/RFC-3276/RFC-3276.txt","version":null},{"body":"IETF","designation":"RFC 4319","folder":"IETF/RFC-4319","source":"IETF/RFC-4319/RFC-4319.txt","version":null}],"search_text":"ITU-T ITU-T G.991.2 nested-reference unavailable"},{"id":"ITU-T ITU-T G.992.1","type":"specification","body":"ITU-T","designation":"ITU-T G.992.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-992-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-992-1/en"],"folder":"ITU-T/ITU-T-G.992.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3449","folder":"IETF/RFC-3449","source":"IETF/RFC-3449/RFC-3449.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.992.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.992.2","type":"specification","body":"ITU-T","designation":"ITU-T G.992.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-992-2/en","download_urls":["https://www.itu.int/rec/T-REC-G-992-2/en"],"folder":"ITU-T/ITU-T-G.992.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.992.2 nested-reference unavailable"},{"id":"ITU-T ITU-T G.992.3","type":"specification","body":"ITU-T","designation":"ITU-T G.992.3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-992-3/en","download_urls":["https://www.itu.int/rec/T-REC-G-992-3/en"],"folder":"ITU-T/ITU-T-G.992.3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.992.3 nested-reference unavailable"},{"id":"ITU-T ITU-T G.992.4","type":"specification","body":"ITU-T","designation":"ITU-T G.992.4","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-992-4/en","download_urls":["https://www.itu.int/rec/T-REC-G-992-4/en"],"folder":"ITU-T/ITU-T-G.992.4","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.992.4 nested-reference unavailable"},{"id":"ITU-T ITU-T G.992.5","type":"specification","body":"ITU-T","designation":"ITU-T G.992.5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-992-5/en","download_urls":["https://www.itu.int/rec/T-REC-G-992-5/en"],"folder":"ITU-T/ITU-T-G.992.5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.992.5 nested-reference unavailable"},{"id":"ITU-T ITU-T G.993.1","type":"specification","body":"ITU-T","designation":"ITU-T G.993.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-993-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-993-1/en"],"folder":"ITU-T/ITU-T-G.993.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.993.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.993.2","type":"specification","body":"ITU-T","designation":"ITU-T G.993.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-993-2/en","download_urls":["https://www.itu.int/rec/T-REC-G-993-2/en"],"folder":"ITU-T/ITU-T-G.993.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null},{"body":"IETF","designation":"RFC 7224","folder":"IETF/RFC-7224","source":"IETF/RFC-7224/RFC-7224.txt","version":null}],"search_text":"ITU-T ITU-T G.993.2 nested-reference unavailable"},{"id":"ITU-T ITU-T G.994.1","type":"specification","body":"ITU-T","designation":"ITU-T G.994.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-994-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-994-1/en"],"folder":"ITU-T/ITU-T-G.994.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null}],"search_text":"ITU-T ITU-T G.994.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.995","type":"specification","body":"ITU-T","designation":"ITU-T G.995","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-995/en","download_urls":["https://www.itu.int/rec/T-REC-G-995/en"],"folder":"ITU-T/ITU-T-G.995","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7228","folder":"IETF/RFC-7228","source":"IETF/RFC-7228/RFC-7228.txt","version":null},{"body":"IETF","designation":"RFC 7421","folder":"IETF/RFC-7421","source":"IETF/RFC-7421/RFC-7421.txt","version":null},{"body":"IETF","designation":"RFC 7428","folder":"IETF/RFC-7428","source":"IETF/RFC-7428/RFC-7428.txt","version":null},{"body":"IETF","designation":"RFC 8064","folder":"IETF/RFC-8064","source":"IETF/RFC-8064/RFC-8064.txt","version":null}],"search_text":"ITU-T ITU-T G.995 nested-reference unavailable"},{"id":"ITU-T ITU-T G.997.1","type":"specification","body":"ITU-T","designation":"ITU-T G.997.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-997-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-997-1/en"],"folder":"ITU-T/ITU-T-G.997.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3728","folder":"IETF/RFC-3728","source":"IETF/RFC-3728/RFC-3728.txt","version":null},{"body":"IETF","designation":"RFC 4706","folder":"IETF/RFC-4706","source":"IETF/RFC-4706/RFC-4706.txt","version":null},{"body":"IETF","designation":"RFC 5650","folder":"IETF/RFC-5650","source":"IETF/RFC-5650/RFC-5650.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null}],"search_text":"ITU-T ITU-T G.997.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.998.1","type":"specification","body":"ITU-T","designation":"ITU-T G.998.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-998-1/en","download_urls":["https://www.itu.int/rec/T-REC-G-998-1/en"],"folder":"ITU-T/ITU-T-G.998.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null}],"search_text":"ITU-T ITU-T G.998.1 nested-reference unavailable"},{"id":"ITU-T ITU-T G.998.2","type":"specification","body":"ITU-T","designation":"ITU-T G.998.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-G-998-2/en","download_urls":["https://www.itu.int/rec/T-REC-G-998-2/en"],"folder":"ITU-T/ITU-T-G.998.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6320","folder":"IETF/RFC-6320","source":"IETF/RFC-6320/RFC-6320.txt","version":null}],"search_text":"ITU-T ITU-T G.998.2 nested-reference unavailable"},{"id":"ITU-T ITU-T H.221","type":"specification","body":"ITU-T","designation":"ITU-T H.221","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-221/en","download_urls":["https://www.itu.int/rec/T-REC-H-221/en"],"folder":"ITU-T/ITU-T-H.221","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T H.221 nested-reference unavailable"},{"id":"ITU-T ITU-T H.222.1","type":"specification","body":"ITU-T","designation":"ITU-T H.222.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-222-1/en","download_urls":["https://www.itu.int/rec/T-REC-H-222-1/en"],"folder":"ITU-T/ITU-T-H.222.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null}],"search_text":"ITU-T ITU-T H.222.1 nested-reference unavailable"},{"id":"ITU-T ITU-T H.223","type":"specification","body":"ITU-T","designation":"ITU-T H.223","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-223/en","download_urls":["https://www.itu.int/rec/T-REC-H-223/en"],"folder":"ITU-T/ITU-T-H.223","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null}],"search_text":"ITU-T ITU-T H.223 nested-reference unavailable"},{"id":"ITU-T ITU-T H.225.0","type":"specification","body":"ITU-T","designation":"ITU-T H.225.0","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-225-0/en","download_urls":["https://www.itu.int/rec/T-REC-H-225-0/en"],"folder":"ITU-T/ITU-T-H.225.0","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T H.225.0 nested-reference unavailable"},{"id":"ITU-T ITU-T H.226","type":"specification","body":"ITU-T","designation":"ITU-T H.226","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-226/en","download_urls":["https://www.itu.int/rec/T-REC-H-226/en"],"folder":"ITU-T/ITU-T-H.226","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T H.226 nested-reference unavailable"},{"id":"ITU-T ITU-T H.235","type":"specification","body":"ITU-T","designation":"ITU-T H.235","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-235/en","download_urls":["https://www.itu.int/rec/T-REC-H-235/en"],"folder":"ITU-T/ITU-T-H.235","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4046","folder":"IETF/RFC-4046","source":"IETF/RFC-4046/RFC-4046.txt","version":null}],"search_text":"ITU-T ITU-T H.235 nested-reference unavailable"},{"id":"ITU-T ITU-T H.235.0","type":"specification","body":"ITU-T","designation":"ITU-T H.235.0","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-235-0/en","download_urls":["https://www.itu.int/rec/T-REC-H-235-0/en"],"folder":"ITU-T/ITU-T-H.235.0","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null}],"search_text":"ITU-T ITU-T H.235.0 nested-reference unavailable"},{"id":"ITU-T ITU-T H.235.7","type":"specification","body":"ITU-T","designation":"ITU-T H.235.7","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-235-7/en","download_urls":["https://www.itu.int/rec/T-REC-H-235-7/en"],"folder":"ITU-T/ITU-T-H.235.7","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4650","folder":"IETF/RFC-4650","source":"IETF/RFC-4650/RFC-4650.txt","version":null},{"body":"IETF","designation":"RFC 5197","folder":"IETF/RFC-5197","source":"IETF/RFC-5197/RFC-5197.txt","version":null}],"search_text":"ITU-T ITU-T H.235.7 nested-reference unavailable"},{"id":"ITU-T ITU-T H.241","type":"specification","body":"ITU-T","designation":"ITU-T H.241","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-241/en","download_urls":["https://www.itu.int/rec/T-REC-H-241/en"],"folder":"ITU-T/ITU-T-H.241","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null}],"search_text":"ITU-T ITU-T H.241 nested-reference unavailable"},{"id":"ITU-T ITU-T H.245","type":"specification","body":"ITU-T","designation":"ITU-T H.245","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-245/en","download_urls":["https://www.itu.int/rec/T-REC-H-245/en"],"folder":"ITU-T/ITU-T-H.245","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 5939","folder":"IETF/RFC-5939","source":"IETF/RFC-5939/RFC-5939.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null}],"search_text":"ITU-T ITU-T H.245 nested-reference unavailable"},{"id":"ITU-T ITU-T H.246","type":"specification","body":"ITU-T","designation":"ITU-T H.246","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-246/en","download_urls":["https://www.itu.int/rec/T-REC-H-246/en"],"folder":"ITU-T/ITU-T-H.246","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T H.246 nested-reference unavailable"},{"id":"ITU-T ITU-T H.248","type":"specification","body":"ITU-T","designation":"ITU-T H.248","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-248/en","download_urls":["https://www.itu.int/rec/T-REC-H-248/en"],"folder":"ITU-T/ITU-T-H.248","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 4190","folder":"IETF/RFC-4190","source":"IETF/RFC-4190/RFC-4190.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"ITU-T ITU-T H.248 nested-reference unavailable"},{"id":"ITU-T ITU-T H.248.1","type":"specification","body":"ITU-T","designation":"ITU-T H.248.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-248-1/en","download_urls":["https://www.itu.int/rec/T-REC-H-248-1/en"],"folder":"ITU-T/ITU-T-H.248.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 5125","folder":"IETF/RFC-5125","source":"IETF/RFC-5125/RFC-5125.txt","version":null}],"search_text":"ITU-T ITU-T H.248.1 nested-reference unavailable"},{"id":"ITU-T ITU-T H.248.15","type":"specification","body":"ITU-T","designation":"ITU-T H.248.15","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-248-15/en","download_urls":["https://www.itu.int/rec/T-REC-H-248-15/en"],"folder":"ITU-T/ITU-T-H.248.15","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"ITU-T ITU-T H.248.15 nested-reference unavailable"},{"id":"ITU-T ITU-T H.248.8","type":"specification","body":"ITU-T","designation":"ITU-T H.248.8","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-248-8/en","download_urls":["https://www.itu.int/rec/T-REC-H-248-8/en"],"folder":"ITU-T/ITU-T-H.248.8","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T H.248.8 nested-reference unavailable"},{"id":"ITU-T ITU-T H.261","type":"specification","body":"ITU-T","designation":"ITU-T H.261","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-261/en","download_urls":["https://www.itu.int/rec/T-REC-H-261/en"],"folder":"ITU-T/ITU-T-H.261","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2032","folder":"IETF/RFC-2032","source":"IETF/RFC-2032/RFC-2032.txt","version":null},{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 4587","folder":"IETF/RFC-4587","source":"IETF/RFC-4587/RFC-4587.txt","version":null}],"search_text":"ITU-T ITU-T H.261 nested-reference unavailable"},{"id":"ITU-T ITU-T H.263","type":"specification","body":"ITU-T","designation":"ITU-T H.263","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-263/en","download_urls":["https://www.itu.int/rec/T-REC-H-263/en"],"folder":"ITU-T/ITU-T-H.263","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2190","folder":"IETF/RFC-2190","source":"IETF/RFC-2190/RFC-2190.txt","version":null},{"body":"IETF","designation":"RFC 2429","folder":"IETF/RFC-2429","source":"IETF/RFC-2429/RFC-2429.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3555","folder":"IETF/RFC-3555","source":"IETF/RFC-3555/RFC-3555.txt","version":null},{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 4585","folder":"IETF/RFC-4585","source":"IETF/RFC-4585/RFC-4585.txt","version":null},{"body":"IETF","designation":"RFC 4629","folder":"IETF/RFC-4629","source":"IETF/RFC-4629/RFC-4629.txt","version":null},{"body":"IETF","designation":"RFC 5109","folder":"IETF/RFC-5109","source":"IETF/RFC-5109/RFC-5109.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null}],"search_text":"ITU-T ITU-T H.263 nested-reference unavailable"},{"id":"ITU-T ITU-T H.264","type":"specification","body":"ITU-T","designation":"ITU-T H.264","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-264/en","download_urls":["https://www.itu.int/rec/T-REC-H-264/en"],"folder":"ITU-T/ITU-T-H.264","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3828","folder":"IETF/RFC-3828","source":"IETF/RFC-3828/RFC-3828.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null},{"body":"IETF","designation":"RFC 6190","folder":"IETF/RFC-6190","source":"IETF/RFC-6190/RFC-6190.txt","version":null},{"body":"IETF","designation":"RFC 6236","folder":"IETF/RFC-6236","source":"IETF/RFC-6236/RFC-6236.txt","version":null},{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null},{"body":"IETF","designation":"RFC 8851","folder":"IETF/RFC-8851","source":"IETF/RFC-8851/RFC-8851.txt","version":null}],"search_text":"ITU-T ITU-T H.264 nested-reference unavailable"},{"id":"ITU-T ITU-T H.265","type":"specification","body":"ITU-T","designation":"ITU-T H.265","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-265/en","download_urls":["https://www.itu.int/rec/T-REC-H-265/en"],"folder":"ITU-T/ITU-T-H.265","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7742","folder":"IETF/RFC-7742","source":"IETF/RFC-7742/RFC-7742.txt","version":null}],"search_text":"ITU-T ITU-T H.265 nested-reference unavailable"},{"id":"ITU-T ITU-T H.323","type":"specification","body":"ITU-T","designation":"ITU-T H.323","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-323/en","download_urls":["https://www.itu.int/rec/T-REC-H-323/en"],"folder":"ITU-T/ITU-T-H.323","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3234","folder":"IETF/RFC-3234","source":"IETF/RFC-3234/RFC-3234.txt","version":null},{"body":"IETF","designation":"RFC 3303","folder":"IETF/RFC-3303","source":"IETF/RFC-3303/RFC-3303.txt","version":null},{"body":"IETF","designation":"RFC 3508","folder":"IETF/RFC-3508","source":"IETF/RFC-3508/RFC-3508.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 4094","folder":"IETF/RFC-4094","source":"IETF/RFC-4094/RFC-4094.txt","version":null},{"body":"IETF","designation":"RFC 4694","folder":"IETF/RFC-4694","source":"IETF/RFC-4694/RFC-4694.txt","version":null},{"body":"IETF","designation":"RFC 5117","folder":"IETF/RFC-5117","source":"IETF/RFC-5117/RFC-5117.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 7362","folder":"IETF/RFC-7362","source":"IETF/RFC-7362/RFC-7362.txt","version":null}],"search_text":"ITU-T ITU-T H.323 nested-reference unavailable"},{"id":"ITU-T ITU-T H.324","type":"specification","body":"ITU-T","designation":"ITU-T H.324","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-324/en","download_urls":["https://www.itu.int/rec/T-REC-H-324/en"],"folder":"ITU-T/ITU-T-H.324","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2689","folder":"IETF/RFC-2689","source":"IETF/RFC-2689/RFC-2689.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3984","folder":"IETF/RFC-3984","source":"IETF/RFC-3984/RFC-3984.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null},{"body":"IETF","designation":"RFC 6184","folder":"IETF/RFC-6184","source":"IETF/RFC-6184/RFC-6184.txt","version":null}],"search_text":"ITU-T ITU-T H.324 nested-reference unavailable"},{"id":"ITU-T ITU-T H.332","type":"specification","body":"ITU-T","designation":"ITU-T H.332","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-332/en","download_urls":["https://www.itu.int/rec/T-REC-H-332/en"],"folder":"ITU-T/ITU-T-H.332","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2327","folder":"IETF/RFC-2327","source":"IETF/RFC-2327/RFC-2327.txt","version":null}],"search_text":"ITU-T ITU-T H.332 nested-reference unavailable"},{"id":"ITU-T ITU-T H.341","type":"specification","body":"ITU-T","designation":"ITU-T H.341","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-H-341/en","download_urls":["https://www.itu.int/rec/T-REC-H-341/en"],"folder":"ITU-T/ITU-T-H.341","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null}],"search_text":"ITU-T ITU-T H.341 nested-reference unavailable"},{"id":"ITU-T ITU-T I.255.3","type":"specification","body":"ITU-T","designation":"ITU-T I.255.3","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-255-3/en","download_urls":["https://www.itu.int/rec/T-REC-I-255-3/en"],"folder":"ITU-T/ITU-T-I.255.3","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4542","folder":"IETF/RFC-4542","source":"IETF/RFC-4542/RFC-4542.txt","version":null}],"search_text":"ITU-T ITU-T I.255.3 nested-reference unavailable"},{"id":"ITU-T ITU-T I.320","type":"specification","body":"ITU-T","designation":"ITU-T I.320","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-320/en","download_urls":["https://www.itu.int/rec/T-REC-I-320/en"],"folder":"ITU-T/ITU-T-I.320","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null}],"search_text":"ITU-T ITU-T I.320 nested-reference unavailable"},{"id":"ITU-T ITU-T I.330","type":"specification","body":"ITU-T","designation":"ITU-T I.330","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-330/en","download_urls":["https://www.itu.int/rec/T-REC-I-330/en"],"folder":"ITU-T/ITU-T-I.330","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2127","folder":"IETF/RFC-2127","source":"IETF/RFC-2127/RFC-2127.txt","version":null}],"search_text":"ITU-T ITU-T I.330 nested-reference unavailable"},{"id":"ITU-T ITU-T I.356","type":"specification","body":"ITU-T","designation":"ITU-T I.356","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-356/en","download_urls":["https://www.itu.int/rec/T-REC-I-356/en"],"folder":"ITU-T/ITU-T-I.356","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null}],"search_text":"ITU-T ITU-T I.356 nested-reference unavailable"},{"id":"ITU-T ITU-T I.363","type":"specification","body":"ITU-T","designation":"ITU-T I.363","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-363/en","download_urls":["https://www.itu.int/rec/T-REC-I-363/en"],"folder":"ITU-T/ITU-T-I.363","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null}],"search_text":"ITU-T ITU-T I.363 nested-reference unavailable"},{"id":"ITU-T ITU-T I.363.1","type":"specification","body":"ITU-T","designation":"ITU-T I.363.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-363-1/en","download_urls":["https://www.itu.int/rec/T-REC-I-363-1/en"],"folder":"ITU-T/ITU-T-I.363.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T I.363.1 nested-reference unavailable"},{"id":"ITU-T ITU-T I.363.2","type":"specification","body":"ITU-T","designation":"ITU-T I.363.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-363-2/en","download_urls":["https://www.itu.int/rec/T-REC-I-363-2/en"],"folder":"ITU-T/ITU-T-I.363.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T I.363.2 nested-reference unavailable"},{"id":"ITU-T ITU-T I.363.5","type":"specification","body":"ITU-T","designation":"ITU-T I.363.5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-363-5/en","download_urls":["https://www.itu.int/rec/T-REC-I-363-5/en"],"folder":"ITU-T/ITU-T-I.363.5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3819","folder":"IETF/RFC-3819","source":"IETF/RFC-3819/RFC-3819.txt","version":null},{"body":"IETF","designation":"RFC 4259","folder":"IETF/RFC-4259","source":"IETF/RFC-4259/RFC-4259.txt","version":null},{"body":"IETF","designation":"RFC 4679","folder":"IETF/RFC-4679","source":"IETF/RFC-4679/RFC-4679.txt","version":null}],"search_text":"ITU-T ITU-T I.363.5 nested-reference unavailable"},{"id":"ITU-T ITU-T I.365.1","type":"specification","body":"ITU-T","designation":"ITU-T I.365.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-365-1/en","download_urls":["https://www.itu.int/rec/T-REC-I-365-1/en"],"folder":"ITU-T/ITU-T-I.365.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null}],"search_text":"ITU-T ITU-T I.365.1 nested-reference unavailable"},{"id":"ITU-T ITU-T I.366.1","type":"specification","body":"ITU-T","designation":"ITU-T I.366.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-366-1/en","download_urls":["https://www.itu.int/rec/T-REC-I-366-1/en"],"folder":"ITU-T/ITU-T-I.366.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3337","folder":"IETF/RFC-3337","source":"IETF/RFC-3337/RFC-3337.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T I.366.1 nested-reference unavailable"},{"id":"ITU-T ITU-T I.366.2","type":"specification","body":"ITU-T","designation":"ITU-T I.366.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-366-2/en","download_urls":["https://www.itu.int/rec/T-REC-I-366-2/en"],"folder":"ITU-T/ITU-T-I.366.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3267","folder":"IETF/RFC-3267","source":"IETF/RFC-3267/RFC-3267.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 4867","folder":"IETF/RFC-4867","source":"IETF/RFC-4867/RFC-4867.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T I.366.2 nested-reference unavailable"},{"id":"ITU-T ITU-T I.371","type":"specification","body":"ITU-T","designation":"ITU-T I.371","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-371/en","download_urls":["https://www.itu.int/rec/T-REC-I-371/en"],"folder":"ITU-T/ITU-T-I.371","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null}],"search_text":"ITU-T ITU-T I.371 nested-reference unavailable"},{"id":"ITU-T ITU-T I.380","type":"specification","body":"ITU-T","designation":"ITU-T I.380","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-380/en","download_urls":["https://www.itu.int/rec/T-REC-I-380/en"],"folder":"ITU-T/ITU-T-I.380","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3432","folder":"IETF/RFC-3432","source":"IETF/RFC-3432/RFC-3432.txt","version":null}],"search_text":"ITU-T ITU-T I.380 nested-reference unavailable"},{"id":"ITU-T ITU-T I.432","type":"specification","body":"ITU-T","designation":"ITU-T I.432","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-432/en","download_urls":["https://www.itu.int/rec/T-REC-I-432/en"],"folder":"ITU-T/ITU-T-I.432","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 5728","folder":"IETF/RFC-5728","source":"IETF/RFC-5728/RFC-5728.txt","version":null}],"search_text":"ITU-T ITU-T I.432 nested-reference unavailable"},{"id":"ITU-T ITU-T I.432.1","type":"specification","body":"ITU-T","designation":"ITU-T I.432.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-432-1/en","download_urls":["https://www.itu.int/rec/T-REC-I-432-1/en"],"folder":"ITU-T/ITU-T-I.432.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ITU-T ITU-T I.432.1 nested-reference unavailable"},{"id":"ITU-T ITU-T I.555","type":"specification","body":"ITU-T","designation":"ITU-T I.555","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-555/en","download_urls":["https://www.itu.int/rec/T-REC-I-555/en"],"folder":"ITU-T/ITU-T-I.555","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2684","folder":"IETF/RFC-2684","source":"IETF/RFC-2684/RFC-2684.txt","version":null}],"search_text":"ITU-T ITU-T I.555 nested-reference unavailable"},{"id":"ITU-T ITU-T I.610","type":"specification","body":"ITU-T","designation":"ITU-T I.610","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-I-610/en","download_urls":["https://www.itu.int/rec/T-REC-I-610/en"],"folder":"ITU-T/ITU-T-I.610","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4454","folder":"IETF/RFC-4454","source":"IETF/RFC-4454/RFC-4454.txt","version":null},{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 5254","folder":"IETF/RFC-5254","source":"IETF/RFC-5254/RFC-5254.txt","version":null},{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null}],"search_text":"ITU-T ITU-T I.610 nested-reference unavailable"},{"id":"ITU-T ITU-T J.112","type":"specification","body":"ITU-T","designation":"ITU-T J.112","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-J-112/en","download_urls":["https://www.itu.int/rec/T-REC-J-112/en"],"folder":"ITU-T/ITU-T-J.112","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2669","folder":"IETF/RFC-2669","source":"IETF/RFC-2669/RFC-2669.txt","version":null},{"body":"IETF","designation":"RFC 2670","folder":"IETF/RFC-2670","source":"IETF/RFC-2670/RFC-2670.txt","version":null},{"body":"IETF","designation":"RFC 3083","folder":"IETF/RFC-3083","source":"IETF/RFC-3083/RFC-3083.txt","version":null}],"search_text":"ITU-T ITU-T J.112 nested-reference unavailable"},{"id":"ITU-T ITU-T J.162","type":"specification","body":"ITU-T","designation":"ITU-T J.162","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-J-162/en","download_urls":["https://www.itu.int/rec/T-REC-J-162/en"],"folder":"ITU-T/ITU-T-J.162","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4722","folder":"IETF/RFC-4722","source":"IETF/RFC-4722/RFC-4722.txt","version":null}],"search_text":"ITU-T ITU-T J.162 nested-reference unavailable"},{"id":"ITU-T ITU-T M.140","type":"specification","body":"ITU-T","designation":"ITU-T M.140","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-M-140/en","download_urls":["https://www.itu.int/rec/T-REC-M-140/en"],"folder":"ITU-T/ITU-T-M.140","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3895","folder":"IETF/RFC-3895","source":"IETF/RFC-3895/RFC-3895.txt","version":null},{"body":"IETF","designation":"RFC 3896","folder":"IETF/RFC-3896","source":"IETF/RFC-3896/RFC-3896.txt","version":null},{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null},{"body":"IETF","designation":"RFC 5580","folder":"IETF/RFC-5580","source":"IETF/RFC-5580/RFC-5580.txt","version":null}],"search_text":"ITU-T ITU-T M.140 nested-reference unavailable"},{"id":"ITU-T ITU-T M.301","type":"specification","body":"ITU-T","designation":"ITU-T M.301","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-M-301/en","download_urls":["https://www.itu.int/rec/T-REC-M-301/en"],"folder":"ITU-T/ITU-T-M.301","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null}],"search_text":"ITU-T ITU-T M.301 nested-reference unavailable"},{"id":"ITU-T ITU-T M.310","type":"specification","body":"ITU-T","designation":"ITU-T M.310","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-M-310/en","download_urls":["https://www.itu.int/rec/T-REC-M-310/en"],"folder":"ITU-T/ITU-T-M.310","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3878","folder":"IETF/RFC-3878","source":"IETF/RFC-3878/RFC-3878.txt","version":null},{"body":"IETF","designation":"RFC 4394","folder":"IETF/RFC-4394","source":"IETF/RFC-4394/RFC-4394.txt","version":null}],"search_text":"ITU-T ITU-T M.310 nested-reference unavailable"},{"id":"ITU-T ITU-T M.340","type":"specification","body":"ITU-T","designation":"ITU-T M.340","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-M-340/en","download_urls":["https://www.itu.int/rec/T-REC-M-340/en"],"folder":"ITU-T/ITU-T-M.340","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6988","folder":"IETF/RFC-6988","source":"IETF/RFC-6988/RFC-6988.txt","version":null},{"body":"IETF","designation":"RFC 7326","folder":"IETF/RFC-7326","source":"IETF/RFC-7326/RFC-7326.txt","version":null},{"body":"IETF","designation":"RFC 8014","folder":"IETF/RFC-8014","source":"IETF/RFC-8014/RFC-8014.txt","version":null}],"search_text":"ITU-T ITU-T M.340 nested-reference unavailable"},{"id":"ITU-T ITU-T O.162","type":"specification","body":"ITU-T","designation":"ITU-T O.162","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-O-162/en","download_urls":["https://www.itu.int/rec/T-REC-O-162/en"],"folder":"ITU-T/ITU-T-O.162","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4805","folder":"IETF/RFC-4805","source":"IETF/RFC-4805/RFC-4805.txt","version":null}],"search_text":"ITU-T ITU-T O.162 nested-reference unavailable"},{"id":"ITU-T ITU-T P.120","type":"specification","body":"ITU-T","designation":"ITU-T P.120","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-120/en","download_urls":["https://www.itu.int/rec/T-REC-P-120/en"],"folder":"ITU-T/ITU-T-P.120","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.120 nested-reference unavailable"},{"id":"ITU-T ITU-T P.340","type":"specification","body":"ITU-T","designation":"ITU-T P.340","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-340/en","download_urls":["https://www.itu.int/rec/T-REC-P-340/en"],"folder":"ITU-T/ITU-T-P.340","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.340 nested-reference unavailable"},{"id":"ITU-T ITU-T P.501","type":"specification","body":"ITU-T","designation":"ITU-T P.501","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-501/en","download_urls":["https://www.itu.int/rec/T-REC-P-501/en"],"folder":"ITU-T/ITU-T-P.501","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.501 nested-reference unavailable"},{"id":"ITU-T ITU-T P.502","type":"specification","body":"ITU-T","designation":"ITU-T P.502","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-502/en","download_urls":["https://www.itu.int/rec/T-REC-P-502/en"],"folder":"ITU-T/ITU-T-P.502","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.502 nested-reference unavailable"},{"id":"ITU-T ITU-T P.564","type":"specification","body":"ITU-T","designation":"ITU-T P.564","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-564/en","download_urls":["https://www.itu.int/rec/T-REC-P-564/en"],"folder":"ITU-T/ITU-T-P.564","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6035","folder":"IETF/RFC-6035","source":"IETF/RFC-6035/RFC-6035.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null},{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.564 nested-reference unavailable"},{"id":"ITU-T ITU-T P.581","type":"specification","body":"ITU-T","designation":"ITU-T P.581","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-581/en","download_urls":["https://www.itu.int/rec/T-REC-P-581/en"],"folder":"ITU-T/ITU-T-P.581","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.581 nested-reference unavailable"},{"id":"ITU-T ITU-T P.800","type":"specification","body":"ITU-T","designation":"ITU-T P.800","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-800/en","download_urls":["https://www.itu.int/rec/T-REC-P-800/en"],"folder":"ITU-T/ITU-T-P.800","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 6390","folder":"IETF/RFC-6390","source":"IETF/RFC-6390/RFC-6390.txt","version":null}],"search_text":"ITU-T ITU-T P.800 nested-reference unavailable"},{"id":"ITU-T ITU-T P.810","type":"specification","body":"ITU-T","designation":"ITU-T P.810","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-810/en","download_urls":["https://www.itu.int/rec/T-REC-P-810/en"],"folder":"ITU-T/ITU-T-P.810","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.810 nested-reference unavailable"},{"id":"ITU-T ITU-T P.831","type":"specification","body":"ITU-T","designation":"ITU-T P.831","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-831/en","download_urls":["https://www.itu.int/rec/T-REC-P-831/en"],"folder":"ITU-T/ITU-T-P.831","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.831 nested-reference unavailable"},{"id":"ITU-T ITU-T P.832","type":"specification","body":"ITU-T","designation":"ITU-T P.832","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-832/en","download_urls":["https://www.itu.int/rec/T-REC-P-832/en"],"folder":"ITU-T/ITU-T-P.832","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.832 nested-reference unavailable"},{"id":"ITU-T ITU-T P.861","type":"specification","body":"ITU-T","designation":"ITU-T P.861","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-861/en","download_urls":["https://www.itu.int/rec/T-REC-P-861/en"],"folder":"ITU-T/ITU-T-P.861","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 329-5","folder":"ETSI/TS-101-329-5-V1.1.2","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf","version":"1.1.2"}],"search_text":"ITU-T ITU-T P.861 nested-reference unavailable"},{"id":"ITU-T ITU-T P.862","type":"specification","body":"ITU-T","designation":"ITU-T P.862","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-862/en","download_urls":["https://www.itu.int/rec/T-REC-P-862/en"],"folder":"ITU-T/ITU-T-P.862","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.862 nested-reference unavailable"},{"id":"ITU-T ITU-T P.862.1","type":"specification","body":"ITU-T","designation":"ITU-T P.862.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-862-1/en","download_urls":["https://www.itu.int/rec/T-REC-P-862-1/en"],"folder":"ITU-T/ITU-T-P.862.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.862.1 nested-reference unavailable"},{"id":"ITU-T ITU-T P.862.2","type":"specification","body":"ITU-T","designation":"ITU-T P.862.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-862-2/en","download_urls":["https://www.itu.int/rec/T-REC-P-862-2/en"],"folder":"ITU-T/ITU-T-P.862.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.862.2 nested-reference unavailable"},{"id":"ITU-T ITU-T P.863","type":"specification","body":"ITU-T","designation":"ITU-T P.863","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-P-863/en","download_urls":["https://www.itu.int/rec/T-REC-P-863/en"],"folder":"ITU-T/ITU-T-P.863","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7266","folder":"IETF/RFC-7266","source":"IETF/RFC-7266/RFC-7266.txt","version":null}],"search_text":"ITU-T ITU-T P.863 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.118","type":"specification","body":"ITU-T","designation":"ITU-T Q.118","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-118/en","download_urls":["https://www.itu.int/rec/T-REC-Q-118/en"],"folder":"ITU-T/ITU-T-Q.118","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null}],"search_text":"ITU-T ITU-T Q.118 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.174","type":"specification","body":"ITU-T","designation":"ITU-T Q.174","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-174/en","download_urls":["https://www.itu.int/rec/T-REC-Q-174/en"],"folder":"ITU-T/ITU-T-Q.174","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null}],"search_text":"ITU-T ITU-T Q.174 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.190","type":"specification","body":"ITU-T","designation":"ITU-T Q.190","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-190/en","download_urls":["https://www.itu.int/rec/T-REC-Q-190/en"],"folder":"ITU-T/ITU-T-Q.190","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.pdf","version":null}],"search_text":"ITU-T ITU-T Q.190 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.197","type":"specification","body":"ITU-T","designation":"ITU-T Q.197","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-197/en","download_urls":["https://www.itu.int/rec/T-REC-Q-197/en"],"folder":"ITU-T/ITU-T-Q.197","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 8859","folder":"IETF/RFC-8859","source":"IETF/RFC-8859/RFC-8859.txt","version":null}],"search_text":"ITU-T ITU-T Q.197 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.211","type":"specification","body":"ITU-T","designation":"ITU-T Q.211","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-211/en","download_urls":["https://www.itu.int/rec/T-REC-Q-211/en"],"folder":"ITU-T/ITU-T-Q.211","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3606","folder":"IETF/RFC-3606","source":"IETF/RFC-3606/RFC-3606.txt","version":null}],"search_text":"ITU-T ITU-T Q.211 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.263","type":"specification","body":"ITU-T","designation":"ITU-T Q.263","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-263/en","download_urls":["https://www.itu.int/rec/T-REC-Q-263/en"],"folder":"ITU-T/ITU-T-Q.263","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.263 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.293","type":"specification","body":"ITU-T","designation":"ITU-T Q.293","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-293/en","download_urls":["https://www.itu.int/rec/T-REC-Q-293/en"],"folder":"ITU-T/ITU-T-Q.293","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1755","folder":"IETF/RFC-1755","source":"IETF/RFC-1755/RFC-1755.txt","version":null},{"body":"IETF","designation":"RFC 2331","folder":"IETF/RFC-2331","source":"IETF/RFC-2331/RFC-2331.txt","version":null},{"body":"IETF","designation":"RFC 2363","folder":"IETF/RFC-2363","source":"IETF/RFC-2363/RFC-2363.txt","version":null},{"body":"IETF","designation":"RFC 2364","folder":"IETF/RFC-2364","source":"IETF/RFC-2364/RFC-2364.txt","version":null},{"body":"IETF","designation":"RFC 2514","folder":"IETF/RFC-2514","source":"IETF/RFC-2514/RFC-2514.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null},{"body":"IETF","designation":"RFC 3108","folder":"IETF/RFC-3108","source":"IETF/RFC-3108/RFC-3108.txt","version":null},{"body":"IETF","designation":"RFC 3355","folder":"IETF/RFC-3355","source":"IETF/RFC-3355/RFC-3355.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.293 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.294","type":"specification","body":"ITU-T","designation":"ITU-T Q.294","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-294/en","download_urls":["https://www.itu.int/rec/T-REC-Q-294/en"],"folder":"ITU-T/ITU-T-Q.294","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.294 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.295","type":"specification","body":"ITU-T","designation":"ITU-T Q.295","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-295/en","download_urls":["https://www.itu.int/rec/T-REC-Q-295/en"],"folder":"ITU-T/ITU-T-Q.295","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null}],"search_text":"ITU-T ITU-T Q.295 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.296","type":"specification","body":"ITU-T","designation":"ITU-T Q.296","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-296/en","download_urls":["https://www.itu.int/rec/T-REC-Q-296/en"],"folder":"ITU-T/ITU-T-Q.296","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2382","folder":"IETF/RFC-2382","source":"IETF/RFC-2382/RFC-2382.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.296 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.297","type":"specification","body":"ITU-T","designation":"ITU-T Q.297","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-297/en","download_urls":["https://www.itu.int/rec/T-REC-Q-297/en"],"folder":"ITU-T/ITU-T-Q.297","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null}],"search_text":"ITU-T ITU-T Q.297 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.330","type":"specification","body":"ITU-T","designation":"ITU-T Q.330","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-330/en","download_urls":["https://www.itu.int/rec/T-REC-Q-330/en"],"folder":"ITU-T/ITU-T-Q.330","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5431","folder":"IETF/RFC-5431","source":"IETF/RFC-5431/RFC-5431.txt","version":null}],"search_text":"ITU-T ITU-T Q.330 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.552","type":"specification","body":"ITU-T","designation":"ITU-T Q.552","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-552/en","download_urls":["https://www.itu.int/rec/T-REC-Q-552/en"],"folder":"ITU-T/ITU-T-Q.552","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-1","folder":"ETSI/TS-101-270-1-V1.2.1","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf","version":"1.2.1"}],"search_text":"ITU-T ITU-T Q.552 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.700","type":"specification","body":"ITU-T","designation":"ITU-T Q.700","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-700/en","download_urls":["https://www.itu.int/rec/T-REC-Q-700/en"],"folder":"ITU-T/ITU-T-Q.700","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T Q.700 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.704","type":"specification","body":"ITU-T","designation":"ITU-T Q.704","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-704/en","download_urls":["https://www.itu.int/rec/T-REC-Q-704/en"],"folder":"ITU-T/ITU-T-Q.704","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null}],"search_text":"ITU-T ITU-T Q.704 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.713","type":"specification","body":"ITU-T","designation":"ITU-T Q.713","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-713/en","download_urls":["https://www.itu.int/rec/T-REC-Q-713/en"],"folder":"ITU-T/ITU-T-Q.713","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null}],"search_text":"ITU-T ITU-T Q.713 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.714","type":"specification","body":"ITU-T","designation":"ITU-T Q.714","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-714/en","download_urls":["https://www.itu.int/rec/T-REC-Q-714/en"],"folder":"ITU-T/ITU-T-Q.714","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null}],"search_text":"ITU-T ITU-T Q.714 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.724","type":"specification","body":"ITU-T","designation":"ITU-T Q.724","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-724/en","download_urls":["https://www.itu.int/rec/T-REC-Q-724/en"],"folder":"ITU-T/ITU-T-Q.724","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.724 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.732.2","type":"specification","body":"ITU-T","designation":"ITU-T Q.732.2","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-732-2/en","download_urls":["https://www.itu.int/rec/T-REC-Q-732-2/en"],"folder":"ITU-T/ITU-T-Q.732.2","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null}],"search_text":"ITU-T ITU-T Q.732.2 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.737","type":"specification","body":"ITU-T","designation":"ITU-T Q.737","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-737/en","download_urls":["https://www.itu.int/rec/T-REC-Q-737/en"],"folder":"ITU-T/ITU-T-Q.737","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null}],"search_text":"ITU-T ITU-T Q.737 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.761","type":"specification","body":"ITU-T","designation":"ITU-T Q.761","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-761/en","download_urls":["https://www.itu.int/rec/T-REC-Q-761/en"],"folder":"ITU-T/ITU-T-Q.761","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3204","folder":"IETF/RFC-3204","source":"IETF/RFC-3204/RFC-3204.txt","version":null}],"search_text":"ITU-T ITU-T Q.761 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.763","type":"specification","body":"ITU-T","designation":"ITU-T Q.763","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-763/en","download_urls":["https://www.itu.int/rec/T-REC-Q-763/en"],"folder":"ITU-T/ITU-T-Q.763","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.763 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.764","type":"specification","body":"ITU-T","designation":"ITU-T Q.764","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-764/en","download_urls":["https://www.itu.int/rec/T-REC-Q-764/en"],"folder":"ITU-T/ITU-T-Q.764","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3372","folder":"IETF/RFC-3372","source":"IETF/RFC-3372/RFC-3372.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3578","folder":"IETF/RFC-3578","source":"IETF/RFC-3578/RFC-3578.txt","version":null},{"body":"IETF","designation":"RFC 5341","folder":"IETF/RFC-5341","source":"IETF/RFC-5341/RFC-5341.txt","version":null},{"body":"IETF","designation":"RFC 7375","folder":"IETF/RFC-7375","source":"IETF/RFC-7375/RFC-7375.txt","version":null}],"search_text":"ITU-T ITU-T Q.764 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.765","type":"specification","body":"ITU-T","designation":"ITU-T Q.765","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-765/en","download_urls":["https://www.itu.int/rec/T-REC-Q-765/en"],"folder":"ITU-T/ITU-T-Q.765","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.765 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.765.5","type":"specification","body":"ITU-T","designation":"ITU-T Q.765.5","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-765-5/en","download_urls":["https://www.itu.int/rec/T-REC-Q-765-5/en"],"folder":"ITU-T/ITU-T-Q.765.5","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T Q.765.5 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.767","type":"specification","body":"ITU-T","designation":"ITU-T Q.767","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-767/en","download_urls":["https://www.itu.int/rec/T-REC-Q-767/en"],"folder":"ITU-T/ITU-T-Q.767","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 3578","folder":"IETF/RFC-3578","source":"IETF/RFC-3578/RFC-3578.txt","version":null}],"search_text":"ITU-T ITU-T Q.767 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.769.1","type":"specification","body":"ITU-T","designation":"ITU-T Q.769.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-769-1/en","download_urls":["https://www.itu.int/rec/T-REC-Q-769-1/en"],"folder":"ITU-T/ITU-T-Q.769.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3482","folder":"IETF/RFC-3482","source":"IETF/RFC-3482/RFC-3482.txt","version":null}],"search_text":"ITU-T ITU-T Q.769.1 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.771","type":"specification","body":"ITU-T","designation":"ITU-T Q.771","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-771/en","download_urls":["https://www.itu.int/rec/T-REC-Q-771/en"],"folder":"ITU-T/ITU-T-Q.771","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3868","folder":"IETF/RFC-3868","source":"IETF/RFC-3868/RFC-3868.txt","version":null}],"search_text":"ITU-T ITU-T Q.771 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.825","type":"specification","body":"ITU-T","designation":"ITU-T Q.825","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-825/en","download_urls":["https://www.itu.int/rec/T-REC-Q-825/en"],"folder":"ITU-T/ITU-T-Q.825","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2924","folder":"IETF/RFC-2924","source":"IETF/RFC-2924/RFC-2924.txt","version":null}],"search_text":"ITU-T ITU-T Q.825 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.850","type":"specification","body":"ITU-T","designation":"ITU-T Q.850","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-850/en","download_urls":["https://www.itu.int/rec/T-REC-Q-850/en"],"folder":"ITU-T/ITU-T-Q.850","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3326","folder":"IETF/RFC-3326","source":"IETF/RFC-3326/RFC-3326.txt","version":null},{"body":"IETF","designation":"RFC 3398","folder":"IETF/RFC-3398","source":"IETF/RFC-3398/RFC-3398.txt","version":null},{"body":"IETF","designation":"RFC 4411","folder":"IETF/RFC-4411","source":"IETF/RFC-4411/RFC-4411.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null}],"search_text":"ITU-T ITU-T Q.850 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.921","type":"specification","body":"ITU-T","designation":"ITU-T Q.921","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-921/en","download_urls":["https://www.itu.int/rec/T-REC-Q-921/en"],"folder":"ITU-T/ITU-T-Q.921","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3336","folder":"IETF/RFC-3336","source":"IETF/RFC-3336/RFC-3336.txt","version":null}],"search_text":"ITU-T ITU-T Q.921 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.922","type":"specification","body":"ITU-T","designation":"ITU-T Q.922","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-922/en","download_urls":["https://www.itu.int/rec/T-REC-Q-922/en"],"folder":"ITU-T/ITU-T-Q.922","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3034","folder":"IETF/RFC-3034","source":"IETF/RFC-3034/RFC-3034.txt","version":null},{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null}],"search_text":"ITU-T ITU-T Q.922 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.923","type":"specification","body":"ITU-T","designation":"ITU-T Q.923","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-923/en","download_urls":["https://www.itu.int/rec/T-REC-Q-923/en"],"folder":"ITU-T/ITU-T-Q.923","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3033","folder":"IETF/RFC-3033","source":"IETF/RFC-3033/RFC-3033.txt","version":null}],"search_text":"ITU-T ITU-T Q.923 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.931","type":"specification","body":"ITU-T","designation":"ITU-T Q.931","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-931/en","download_urls":["https://www.itu.int/rec/T-REC-Q-931/en"],"folder":"ITU-T/ITU-T-Q.931","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2128","folder":"IETF/RFC-2128","source":"IETF/RFC-2128/RFC-2128.txt","version":null},{"body":"IETF","designation":"RFC 2719","folder":"IETF/RFC-2719","source":"IETF/RFC-2719/RFC-2719.txt","version":null},{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 4197","folder":"IETF/RFC-4197","source":"IETF/RFC-4197/RFC-4197.txt","version":null},{"body":"IETF","designation":"RFC 4458","folder":"IETF/RFC-4458","source":"IETF/RFC-4458/RFC-4458.txt","version":null},{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null},{"body":"IETF","designation":"RFC 5456","folder":"IETF/RFC-5456","source":"IETF/RFC-5456/RFC-5456.txt","version":null},{"body":"IETF","designation":"RFC 7195","folder":"IETF/RFC-7195","source":"IETF/RFC-7195/RFC-7195.txt","version":null},{"body":"IETF","designation":"RFC 7375","folder":"IETF/RFC-7375","source":"IETF/RFC-7375/RFC-7375.txt","version":null}],"search_text":"ITU-T ITU-T Q.931 nested-reference unavailable"},{"id":"ITU-T ITU-T Q.933","type":"specification","body":"ITU-T","designation":"ITU-T Q.933","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Q-933/en","download_urls":["https://www.itu.int/rec/T-REC-Q-933/en"],"folder":"ITU-T/ITU-T-Q.933","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2115","folder":"IETF/RFC-2115","source":"IETF/RFC-2115/RFC-2115.txt","version":null},{"body":"IETF","designation":"RFC 2427","folder":"IETF/RFC-2427","source":"IETF/RFC-2427/RFC-2427.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 4591","folder":"IETF/RFC-4591","source":"IETF/RFC-4591/RFC-4591.txt","version":null},{"body":"IETF","designation":"RFC 4618","folder":"IETF/RFC-4618","source":"IETF/RFC-4618/RFC-4618.txt","version":null},{"body":"IETF","designation":"RFC 4619","folder":"IETF/RFC-4619","source":"IETF/RFC-4619/RFC-4619.txt","version":null}],"search_text":"ITU-T ITU-T Q.933 nested-reference unavailable"},{"id":"ITU-T ITU-T T.101","type":"specification","body":"ITU-T","designation":"ITU-T T.101","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-T-101/en","download_urls":["https://www.itu.int/rec/T-REC-T-101/en"],"folder":"ITU-T/ITU-T-T.101","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T T.101 nested-reference unavailable"},{"id":"ITU-T ITU-T T.107","type":"specification","body":"ITU-T","designation":"ITU-T T.107","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-T-107/en","download_urls":["https://www.itu.int/rec/T-REC-T-107/en"],"folder":"ITU-T/ITU-T-T.107","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2122","folder":"IETF/RFC-2122","source":"IETF/RFC-2122/RFC-2122.txt","version":null}],"search_text":"ITU-T ITU-T T.107 nested-reference unavailable"},{"id":"ITU-T ITU-T T.120","type":"specification","body":"ITU-T","designation":"ITU-T T.120","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-T-120/en","download_urls":["https://www.itu.int/rec/T-REC-T-120/en"],"folder":"ITU-T/ITU-T-T.120","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T T.120 nested-reference unavailable"},{"id":"ITU-T ITU-T T.140","type":"specification","body":"ITU-T","designation":"ITU-T T.140","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-T-140/en","download_urls":["https://www.itu.int/rec/T-REC-T-140/en"],"folder":"ITU-T/ITU-T-T.140","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2793","folder":"IETF/RFC-2793","source":"IETF/RFC-2793/RFC-2793.txt","version":null},{"body":"IETF","designation":"RFC 2805","folder":"IETF/RFC-2805","source":"IETF/RFC-2805/RFC-2805.txt","version":null},{"body":"IETF","designation":"RFC 4103","folder":"IETF/RFC-4103","source":"IETF/RFC-4103/RFC-4103.txt","version":null},{"body":"IETF","designation":"RFC 5194","folder":"IETF/RFC-5194","source":"IETF/RFC-5194/RFC-5194.txt","version":null}],"search_text":"ITU-T ITU-T T.140 nested-reference unavailable"},{"id":"ITU-T ITU-T V.110","type":"specification","body":"ITU-T","designation":"ITU-T V.110","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-V-110/en","download_urls":["https://www.itu.int/rec/T-REC-V-110/en"],"folder":"ITU-T/ITU-T-V.110","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null}],"search_text":"ITU-T ITU-T V.110 nested-reference unavailable"},{"id":"ITU-T ITU-T V.120","type":"specification","body":"ITU-T","designation":"ITU-T V.120","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-V-120/en","download_urls":["https://www.itu.int/rec/T-REC-V-120/en"],"folder":"ITU-T/ITU-T-V.120","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2806","folder":"IETF/RFC-2806","source":"IETF/RFC-2806/RFC-2806.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null}],"search_text":"ITU-T ITU-T V.120 nested-reference unavailable"},{"id":"ITU-T ITU-T V.150.1","type":"specification","body":"ITU-T","designation":"ITU-T V.150.1","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-V-150-1/en","download_urls":["https://www.itu.int/rec/T-REC-V-150-1/en"],"folder":"ITU-T/ITU-T-V.150.1","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T V.150.1 nested-reference unavailable"},{"id":"ITU-T ITU-T V.152","type":"specification","body":"ITU-T","designation":"ITU-T V.152","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-V-152/en","download_urls":["https://www.itu.int/rec/T-REC-V-152/en"],"folder":"ITU-T/ITU-T-V.152","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4733","folder":"IETF/RFC-4733","source":"IETF/RFC-4733/RFC-4733.txt","version":null},{"body":"IETF","designation":"RFC 4734","folder":"IETF/RFC-4734","source":"IETF/RFC-4734/RFC-4734.txt","version":null}],"search_text":"ITU-T ITU-T V.152 nested-reference unavailable"},{"id":"ITU-T ITU-T X.121","type":"specification","body":"ITU-T","designation":"ITU-T X.121","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-121/en","download_urls":["https://www.itu.int/rec/T-REC-X-121/en"],"folder":"ITU-T/ITU-T-X.121","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1888","folder":"IETF/RFC-1888","source":"IETF/RFC-1888/RFC-1888.txt","version":null},{"body":"IETF","designation":"RFC 2848","folder":"IETF/RFC-2848","source":"IETF/RFC-2848/RFC-2848.txt","version":null},{"body":"IETF","designation":"RFC 2954","folder":"IETF/RFC-2954","source":"IETF/RFC-2954/RFC-2954.txt","version":null},{"body":"IETF","designation":"RFC 3017","folder":"IETF/RFC-3017","source":"IETF/RFC-3017/RFC-3017.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null}],"search_text":"ITU-T ITU-T X.121 nested-reference unavailable"},{"id":"ITU-T ITU-T X.152","type":"specification","body":"ITU-T","designation":"ITU-T X.152","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-152/en","download_urls":["https://www.itu.int/rec/T-REC-X-152/en"],"folder":"ITU-T/ITU-T-X.152","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9393","folder":"IETF/RFC-9393","source":"IETF/RFC-9393/RFC-9393.txt","version":null}],"search_text":"ITU-T ITU-T X.152 nested-reference unavailable"},{"id":"ITU-T ITU-T X.200","type":"specification","body":"ITU-T","designation":"ITU-T X.200","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-200/en","download_urls":["https://www.itu.int/rec/T-REC-X-200/en"],"folder":"ITU-T/ITU-T-X.200","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5921","folder":"IETF/RFC-5921","source":"IETF/RFC-5921/RFC-5921.txt","version":null}],"search_text":"ITU-T ITU-T X.200 nested-reference unavailable"},{"id":"ITU-T ITU-T X.208","type":"specification","body":"ITU-T","designation":"ITU-T X.208","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-208/en","download_urls":["https://www.itu.int/rec/T-REC-X-208/en"],"folder":"ITU-T/ITU-T-X.208","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4151","folder":"IETF/RFC-4151","source":"IETF/RFC-4151/RFC-4151.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 8126","folder":"IETF/RFC-8126","source":"IETF/RFC-8126/RFC-8126.txt","version":null}],"search_text":"ITU-T ITU-T X.208 nested-reference unavailable"},{"id":"ITU-T ITU-T X.209","type":"specification","body":"ITU-T","designation":"ITU-T X.209","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-209/en","download_urls":["https://www.itu.int/rec/T-REC-X-209/en"],"folder":"ITU-T/ITU-T-X.209","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ITU-T ITU-T X.209 nested-reference unavailable"},{"id":"ITU-T ITU-T X.213","type":"specification","body":"ITU-T","designation":"ITU-T X.213","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-213/en","download_urls":["https://www.itu.int/rec/T-REC-X-213/en"],"folder":"ITU-T/ITU-T-X.213","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null}],"search_text":"ITU-T ITU-T X.213 nested-reference unavailable"},{"id":"ITU-T ITU-T X.224","type":"specification","body":"ITU-T","designation":"ITU-T X.224","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-224/en","download_urls":["https://www.itu.int/rec/T-REC-X-224/en"],"folder":"ITU-T/ITU-T-X.224","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1950","folder":"IETF/RFC-1950","source":"IETF/RFC-1950/RFC-1950.txt","version":null}],"search_text":"ITU-T ITU-T X.224 nested-reference unavailable"},{"id":"ITU-T ITU-T X.244","type":"specification","body":"ITU-T","designation":"ITU-T X.244","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-244/en","download_urls":["https://www.itu.int/rec/T-REC-X-244/en"],"folder":"ITU-T/ITU-T-X.244","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 1950","folder":"IETF/RFC-1950","source":"IETF/RFC-1950/RFC-1950.txt","version":null}],"search_text":"ITU-T ITU-T X.244 nested-reference unavailable"},{"id":"ITU-T ITU-T X.400","type":"specification","body":"ITU-T","designation":"ITU-T X.400","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-400/en","download_urls":["https://www.itu.int/rec/T-REC-X-400/en"],"folder":"ITU-T/ITU-T-X.400","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 3854","folder":"IETF/RFC-3854","source":"IETF/RFC-3854/RFC-3854.txt","version":null},{"body":"IETF","designation":"RFC 3855","folder":"IETF/RFC-3855","source":"IETF/RFC-3855/RFC-3855.txt","version":null}],"search_text":"ITU-T ITU-T X.400 nested-reference unavailable"},{"id":"ITU-T ITU-T X.408","type":"specification","body":"ITU-T","designation":"ITU-T X.408","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-408/en","download_urls":["https://www.itu.int/rec/T-REC-X-408/en"],"folder":"ITU-T/ITU-T-X.408","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2156","folder":"IETF/RFC-2156","source":"IETF/RFC-2156/RFC-2156.txt","version":null}],"search_text":"ITU-T ITU-T X.408 nested-reference unavailable"},{"id":"ITU-T ITU-T X.411","type":"specification","body":"ITU-T","designation":"ITU-T X.411","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-411/en","download_urls":["https://www.itu.int/rec/T-REC-X-411/en"],"folder":"ITU-T/ITU-T-X.411","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null}],"search_text":"ITU-T ITU-T X.411 nested-reference unavailable"},{"id":"ITU-T ITU-T X.419","type":"specification","body":"ITU-T","designation":"ITU-T X.419","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-419/en","download_urls":["https://www.itu.int/rec/T-REC-X-419/en"],"folder":"ITU-T/ITU-T-X.419","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ITU-T ITU-T X.419 nested-reference unavailable"},{"id":"ITU-T ITU-T X.420","type":"specification","body":"ITU-T","designation":"ITU-T X.420","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-420/en","download_urls":["https://www.itu.int/rec/T-REC-X-420/en"],"folder":"ITU-T/ITU-T-X.420","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2422","folder":"IETF/RFC-2422","source":"IETF/RFC-2422/RFC-2422.txt","version":null},{"body":"IETF","designation":"RFC 3551","folder":"IETF/RFC-3551","source":"IETF/RFC-3551/RFC-3551.txt","version":null},{"body":"IETF","designation":"RFC 3802","folder":"IETF/RFC-3802","source":"IETF/RFC-3802/RFC-3802.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null}],"search_text":"ITU-T ITU-T X.420 nested-reference unavailable"},{"id":"ITU-T ITU-T X.500","type":"specification","body":"ITU-T","designation":"ITU-T X.500","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-500/en","download_urls":["https://www.itu.int/rec/T-REC-X-500/en"],"folder":"ITU-T/ITU-T-X.500","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ITU-T ITU-T X.500 nested-reference unavailable"},{"id":"ITU-T ITU-T X.501","type":"specification","body":"ITU-T","designation":"ITU-T X.501","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-501/en","download_urls":["https://www.itu.int/rec/T-REC-X-501/en"],"folder":"ITU-T/ITU-T-X.501","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 8446","folder":"IETF/RFC-8446","source":"IETF/RFC-8446/RFC-8446.txt","version":null}],"search_text":"ITU-T ITU-T X.501 nested-reference unavailable"},{"id":"ITU-T ITU-T X.509","type":"specification","body":"ITU-T","designation":"ITU-T X.509","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-509/en","download_urls":["https://www.itu.int/rec/T-REC-X-509/en"],"folder":"ITU-T/ITU-T-X.509","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 132-1","folder":"ETSI/EN-319-132-1-V1.3.1","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"},{"body":"ETSI","designation":"EN 319 411-2","folder":"ETSI/EN-319-411-2-V2.6.1","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf","version":"2.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 412-3","folder":"ETSI/EN-319-412-3-V1.3.1","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.6.0","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","version":"2.6.0"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 903","folder":"ETSI/TS-101-903-V1.3.2","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf","version":"1.3.2"},{"body":"ETSI","designation":"TS 119 182-1","folder":"ETSI/TS-119-182-1-V1.2.1","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.1.1","source":"ETSI/TS-119-412-6-V1.1.1/TS-119-412-6-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 412-6","folder":"ETSI/TS-119-412-6-V1.2.1","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 602","folder":"ETSI/TS-119-602-V1.1.1","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 612","folder":"ETSI/TS-119-612-V2.4.1","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf","version":"2.4.1"},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2527","folder":"IETF/RFC-2527","source":"IETF/RFC-2527/RFC-2527.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2802","folder":"IETF/RFC-2802","source":"IETF/RFC-2802/RFC-2802.txt","version":null},{"body":"IETF","designation":"RFC 2828","folder":"IETF/RFC-2828","source":"IETF/RFC-2828/RFC-2828.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3075","folder":"IETF/RFC-3075","source":"IETF/RFC-3075/RFC-3075.txt","version":null},{"body":"IETF","designation":"RFC 3114","folder":"IETF/RFC-3114","source":"IETF/RFC-3114/RFC-3114.txt","version":null},{"body":"IETF","designation":"RFC 3126","folder":"IETF/RFC-3126","source":"IETF/RFC-3126/RFC-3126.txt","version":null},{"body":"IETF","designation":"RFC 3169","folder":"IETF/RFC-3169","source":"IETF/RFC-3169/RFC-3169.txt","version":null},{"body":"IETF","designation":"RFC 3275","folder":"IETF/RFC-3275","source":"IETF/RFC-3275/RFC-3275.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3281","folder":"IETF/RFC-3281","source":"IETF/RFC-3281/RFC-3281.txt","version":null},{"body":"IETF","designation":"RFC 3379","folder":"IETF/RFC-3379","source":"IETF/RFC-3379/RFC-3379.txt","version":null},{"body":"IETF","designation":"RFC 3546","folder":"IETF/RFC-3546","source":"IETF/RFC-3546/RFC-3546.txt","version":null},{"body":"IETF","designation":"RFC 3647","folder":"IETF/RFC-3647","source":"IETF/RFC-3647/RFC-3647.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4158","folder":"IETF/RFC-4158","source":"IETF/RFC-4158/RFC-4158.txt","version":null},{"body":"IETF","designation":"RFC 4171","folder":"IETF/RFC-4171","source":"IETF/RFC-4171/RFC-4171.txt","version":null},{"body":"IETF","designation":"RFC 4210","folder":"IETF/RFC-4210","source":"IETF/RFC-4210/RFC-4210.txt","version":null},{"body":"IETF","designation":"RFC 4306","folder":"IETF/RFC-4306","source":"IETF/RFC-4306/RFC-4306.txt","version":null},{"body":"IETF","designation":"RFC 4346","folder":"IETF/RFC-4346","source":"IETF/RFC-4346/RFC-4346.txt","version":null},{"body":"IETF","designation":"RFC 4366","folder":"IETF/RFC-4366","source":"IETF/RFC-4366/RFC-4366.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 4572","folder":"IETF/RFC-4572","source":"IETF/RFC-4572/RFC-4572.txt","version":null},{"body":"IETF","designation":"RFC 4949","folder":"IETF/RFC-4949","source":"IETF/RFC-4949/RFC-4949.txt","version":null},{"body":"IETF","designation":"RFC 5091","folder":"IETF/RFC-5091","source":"IETF/RFC-5091/RFC-5091.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5924","folder":"IETF/RFC-5924","source":"IETF/RFC-5924/RFC-5924.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5937","folder":"IETF/RFC-5937","source":"IETF/RFC-5937/RFC-5937.txt","version":null},{"body":"IETF","designation":"RFC 6066","folder":"IETF/RFC-6066","source":"IETF/RFC-6066/RFC-6066.txt","version":null},{"body":"IETF","designation":"RFC 6120","folder":"IETF/RFC-6120","source":"IETF/RFC-6120/RFC-6120.txt","version":null},{"body":"IETF","designation":"RFC 6125","folder":"IETF/RFC-6125","source":"IETF/RFC-6125/RFC-6125.txt","version":null},{"body":"IETF","designation":"RFC 6484","folder":"IETF/RFC-6484","source":"IETF/RFC-6484/RFC-6484.txt","version":null},{"body":"IETF","designation":"RFC 6818","folder":"IETF/RFC-6818","source":"IETF/RFC-6818/RFC-6818.txt","version":null},{"body":"IETF","designation":"RFC 6837","folder":"IETF/RFC-6837","source":"IETF/RFC-6837/RFC-6837.txt","version":null},{"body":"IETF","designation":"RFC 6844","folder":"IETF/RFC-6844","source":"IETF/RFC-6844/RFC-6844.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null}],"search_text":"ITU-T ITU-T X.509 nested-reference unavailable"},{"id":"ITU-T ITU-T X.520","type":"specification","body":"ITU-T","designation":"ITU-T X.520","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-520/en","download_urls":["https://www.itu.int/rec/T-REC-X-520/en"],"folder":"ITU-T/ITU-T-X.520","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS02","folder":"ARF/TS02-V1.0.1","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.6.1","source":"ETSI/EN-319-412-1-V1.6.1/EN-319-412-1-V1.6.1.pdf","version":"1.6.1"},{"body":"ETSI","designation":"EN 319 412-1","folder":"ETSI/EN-319-412-1-V1.7.0","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf","version":"1.7.0"},{"body":"ETSI","designation":"EN 319 412-2","folder":"ETSI/EN-319-412-2-V2.4.1","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf","version":"2.4.1"},{"body":"ETSI","designation":"EN 319 412-3","folder":"ETSI/EN-319-412-3-V1.3.1","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 101 861","folder":"ETSI/TS-101-861-V1.4.1","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf","version":"1.4.1"},{"body":"ETSI","designation":"TS 119 411-8","folder":"ETSI/TS-119-411-8-V1.1.1","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"IETF","designation":"RFC 2247","folder":"IETF/RFC-2247","source":"IETF/RFC-2247/RFC-2247.txt","version":null},{"body":"IETF","designation":"RFC 2252","folder":"IETF/RFC-2252","source":"IETF/RFC-2252/RFC-2252.txt","version":null},{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 2312","folder":"IETF/RFC-2312","source":"IETF/RFC-2312/RFC-2312.txt","version":null},{"body":"IETF","designation":"RFC 2459","folder":"IETF/RFC-2459","source":"IETF/RFC-2459/RFC-2459.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3671","folder":"IETF/RFC-3671","source":"IETF/RFC-3671/RFC-3671.txt","version":null},{"body":"IETF","designation":"RFC 3703","folder":"IETF/RFC-3703","source":"IETF/RFC-3703/RFC-3703.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 3850","folder":"IETF/RFC-3850","source":"IETF/RFC-3850/RFC-3850.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null}],"search_text":"ITU-T ITU-T X.520 nested-reference unavailable"},{"id":"ITU-T ITU-T X.521","type":"specification","body":"ITU-T","designation":"ITU-T X.521","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-521/en","download_urls":["https://www.itu.int/rec/T-REC-X-521/en"],"folder":"ITU-T/ITU-T-X.521","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2256","folder":"IETF/RFC-2256","source":"IETF/RFC-2256/RFC-2256.txt","version":null},{"body":"IETF","designation":"RFC 4519","folder":"IETF/RFC-4519","source":"IETF/RFC-4519/RFC-4519.txt","version":null}],"search_text":"ITU-T ITU-T X.521 nested-reference unavailable"},{"id":"ITU-T ITU-T X.660","type":"specification","body":"ITU-T","designation":"ITU-T X.660","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-660/en","download_urls":["https://www.itu.int/rec/T-REC-X-660/en"],"folder":"ITU-T/ITU-T-X.660","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3279","folder":"IETF/RFC-3279","source":"IETF/RFC-3279/RFC-3279.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4357","folder":"IETF/RFC-4357","source":"IETF/RFC-4357/RFC-4357.txt","version":null},{"body":"IETF","designation":"RFC 4491","folder":"IETF/RFC-4491","source":"IETF/RFC-4491/RFC-4491.txt","version":null},{"body":"IETF","designation":"RFC 4871","folder":"IETF/RFC-4871","source":"IETF/RFC-4871/RFC-4871.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7519","folder":"IETF/RFC-7519","source":"IETF/RFC-7519/RFC-7519.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ITU-T ITU-T X.660 nested-reference unavailable"},{"id":"ITU-T ITU-T X.667","type":"specification","body":"ITU-T","designation":"ITU-T X.667","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-667/en","download_urls":["https://www.itu.int/rec/T-REC-X-667/en"],"folder":"ITU-T/ITU-T-X.667","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null}],"search_text":"ITU-T ITU-T X.667 nested-reference unavailable"},{"id":"ITU-T ITU-T X.672","type":"specification","body":"ITU-T","designation":"ITU-T X.672","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-672/en","download_urls":["https://www.itu.int/rec/T-REC-X-672/en"],"folder":"ITU-T/ITU-T-X.672","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null}],"search_text":"ITU-T ITU-T X.672 nested-reference unavailable"},{"id":"ITU-T ITU-T X.680","type":"specification","body":"ITU-T","designation":"ITU-T X.680","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-680/en","download_urls":["https://www.itu.int/rec/T-REC-X-680/en"],"folder":"ITU-T/ITU-T-X.680","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.5.1","source":"ETSI/EN-319-412-5-V2.5.1/EN-319-412-5-V2.5.1.pdf","version":"2.5.1"},{"body":"ETSI","designation":"EN 319 412-5","folder":"ETSI/EN-319-412-5-V2.6.0","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf","version":"2.6.0"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 411-5","folder":"ETSI/TS-119-411-5-V2.1.1","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf","version":"2.1.1"},{"body":"ETSI","designation":"TS 119 472-1","folder":"ETSI/TS-119-472-1-V1.2.1","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 495","folder":"ETSI/TS-119-495-V1.7.1","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf","version":"1.7.1"},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3039","folder":"IETF/RFC-3039","source":"IETF/RFC-3039/RFC-3039.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3642","folder":"IETF/RFC-3642","source":"IETF/RFC-3642/RFC-3642.txt","version":null},{"body":"IETF","designation":"RFC 3739","folder":"IETF/RFC-3739","source":"IETF/RFC-3739/RFC-3739.txt","version":null},{"body":"IETF","designation":"RFC 4043","folder":"IETF/RFC-4043","source":"IETF/RFC-4043/RFC-4043.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4334","folder":"IETF/RFC-4334","source":"IETF/RFC-4334/RFC-4334.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4511","folder":"IETF/RFC-4511","source":"IETF/RFC-4511/RFC-4511.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5750","folder":"IETF/RFC-5750","source":"IETF/RFC-5750/RFC-5750.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5911","folder":"IETF/RFC-5911","source":"IETF/RFC-5911/RFC-5911.txt","version":null},{"body":"IETF","designation":"RFC 5912","folder":"IETF/RFC-5912","source":"IETF/RFC-5912/RFC-5912.txt","version":null},{"body":"IETF","designation":"RFC 5914","folder":"IETF/RFC-5914","source":"IETF/RFC-5914/RFC-5914.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8411","folder":"IETF/RFC-8411","source":"IETF/RFC-8411/RFC-8411.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8550","folder":"IETF/RFC-8550","source":"IETF/RFC-8550/RFC-8550.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9562","folder":"IETF/RFC-9562","source":"IETF/RFC-9562/RFC-9562.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"ITU-T ITU-T X.680 nested-reference unavailable"},{"id":"ITU-T ITU-T X.681","type":"specification","body":"ITU-T","designation":"ITU-T X.681","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-681/en","download_urls":["https://www.itu.int/rec/T-REC-X-681/en"],"folder":"ITU-T/ITU-T-X.681","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ITU-T ITU-T X.681 nested-reference unavailable"},{"id":"ITU-T ITU-T X.682","type":"specification","body":"ITU-T","designation":"ITU-T X.682","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-682/en","download_urls":["https://www.itu.int/rec/T-REC-X-682/en"],"folder":"ITU-T/ITU-T-X.682","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ITU-T ITU-T X.682 nested-reference unavailable"},{"id":"ITU-T ITU-T X.683","type":"specification","body":"ITU-T","designation":"ITU-T X.683","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-683/en","download_urls":["https://www.itu.int/rec/T-REC-X-683/en"],"folder":"ITU-T/ITU-T-X.683","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5649","folder":"IETF/RFC-5649","source":"IETF/RFC-5649/RFC-5649.txt","version":null},{"body":"IETF","designation":"RFC 5753","folder":"IETF/RFC-5753","source":"IETF/RFC-5753/RFC-5753.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5940","folder":"IETF/RFC-5940","source":"IETF/RFC-5940/RFC-5940.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 8226","folder":"IETF/RFC-8226","source":"IETF/RFC-8226/RFC-8226.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null}],"search_text":"ITU-T ITU-T X.683 nested-reference unavailable"},{"id":"ITU-T ITU-T X.690","type":"specification","body":"ITU-T","designation":"ITU-T X.690","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-690/en","download_urls":["https://www.itu.int/rec/T-REC-X-690/en"],"folder":"ITU-T/ITU-T-X.690","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 122-1","folder":"ETSI/EN-319-122-1-V1.3.1","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TR 102 272","folder":"ETSI/TR-102-272-V1.1.1","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"RFC 2254","folder":"IETF/RFC-2254","source":"IETF/RFC-2254/RFC-2254.txt","version":null},{"body":"IETF","designation":"RFC 2560","folder":"IETF/RFC-2560","source":"IETF/RFC-2560/RFC-2560.txt","version":null},{"body":"IETF","designation":"RFC 2632","folder":"IETF/RFC-2632","source":"IETF/RFC-2632/RFC-2632.txt","version":null},{"body":"IETF","designation":"RFC 2885","folder":"IETF/RFC-2885","source":"IETF/RFC-2885/RFC-2885.txt","version":null},{"body":"IETF","designation":"RFC 2986","folder":"IETF/RFC-2986","source":"IETF/RFC-2986/RFC-2986.txt","version":null},{"body":"IETF","designation":"RFC 3015","folder":"IETF/RFC-3015","source":"IETF/RFC-3015/RFC-3015.txt","version":null},{"body":"IETF","designation":"RFC 3125","folder":"IETF/RFC-3125","source":"IETF/RFC-3125/RFC-3125.txt","version":null},{"body":"IETF","designation":"RFC 3280","folder":"IETF/RFC-3280","source":"IETF/RFC-3280/RFC-3280.txt","version":null},{"body":"IETF","designation":"RFC 3525","folder":"IETF/RFC-3525","source":"IETF/RFC-3525/RFC-3525.txt","version":null},{"body":"IETF","designation":"RFC 3641","folder":"IETF/RFC-3641","source":"IETF/RFC-3641/RFC-3641.txt","version":null},{"body":"IETF","designation":"RFC 3779","folder":"IETF/RFC-3779","source":"IETF/RFC-3779/RFC-3779.txt","version":null},{"body":"IETF","designation":"RFC 3971","folder":"IETF/RFC-3971","source":"IETF/RFC-3971/RFC-3971.txt","version":null},{"body":"IETF","designation":"RFC 3972","folder":"IETF/RFC-3972","source":"IETF/RFC-3972/RFC-3972.txt","version":null},{"body":"IETF","designation":"RFC 4120","folder":"IETF/RFC-4120","source":"IETF/RFC-4120/RFC-4120.txt","version":null},{"body":"IETF","designation":"RFC 4178","folder":"IETF/RFC-4178","source":"IETF/RFC-4178/RFC-4178.txt","version":null},{"body":"IETF","designation":"RFC 4325","folder":"IETF/RFC-4325","source":"IETF/RFC-4325/RFC-4325.txt","version":null},{"body":"IETF","designation":"RFC 4462","folder":"IETF/RFC-4462","source":"IETF/RFC-4462/RFC-4462.txt","version":null},{"body":"IETF","designation":"RFC 4492","folder":"IETF/RFC-4492","source":"IETF/RFC-4492/RFC-4492.txt","version":null},{"body":"IETF","designation":"RFC 4515","folder":"IETF/RFC-4515","source":"IETF/RFC-4515/RFC-4515.txt","version":null},{"body":"IETF","designation":"RFC 4517","folder":"IETF/RFC-4517","source":"IETF/RFC-4517/RFC-4517.txt","version":null},{"body":"IETF","designation":"RFC 4522","folder":"IETF/RFC-4522","source":"IETF/RFC-4522/RFC-4522.txt","version":null},{"body":"IETF","designation":"RFC 4537","folder":"IETF/RFC-4537","source":"IETF/RFC-4537/RFC-4537.txt","version":null},{"body":"IETF","designation":"RFC 4556","folder":"IETF/RFC-4556","source":"IETF/RFC-4556/RFC-4556.txt","version":null},{"body":"IETF","designation":"RFC 5126","folder":"IETF/RFC-5126","source":"IETF/RFC-5126/RFC-5126.txt","version":null},{"body":"IETF","designation":"RFC 5246","folder":"IETF/RFC-5246","source":"IETF/RFC-5246/RFC-5246.txt","version":null},{"body":"IETF","designation":"RFC 5280","folder":"IETF/RFC-5280","source":"IETF/RFC-5280/RFC-5280.txt","version":null},{"body":"IETF","designation":"RFC 5408","folder":"IETF/RFC-5408","source":"IETF/RFC-5408/RFC-5408.txt","version":null},{"body":"IETF","designation":"RFC 5409","folder":"IETF/RFC-5409","source":"IETF/RFC-5409/RFC-5409.txt","version":null},{"body":"IETF","designation":"RFC 5485","folder":"IETF/RFC-5485","source":"IETF/RFC-5485/RFC-5485.txt","version":null},{"body":"IETF","designation":"RFC 5751","folder":"IETF/RFC-5751","source":"IETF/RFC-5751/RFC-5751.txt","version":null},{"body":"IETF","designation":"RFC 5755","folder":"IETF/RFC-5755","source":"IETF/RFC-5755/RFC-5755.txt","version":null},{"body":"IETF","designation":"RFC 5877","folder":"IETF/RFC-5877","source":"IETF/RFC-5877/RFC-5877.txt","version":null},{"body":"IETF","designation":"RFC 5915","folder":"IETF/RFC-5915","source":"IETF/RFC-5915/RFC-5915.txt","version":null},{"body":"IETF","designation":"RFC 5934","folder":"IETF/RFC-5934","source":"IETF/RFC-5934/RFC-5934.txt","version":null},{"body":"IETF","designation":"RFC 5958","folder":"IETF/RFC-5958","source":"IETF/RFC-5958/RFC-5958.txt","version":null},{"body":"IETF","designation":"RFC 5967","folder":"IETF/RFC-5967","source":"IETF/RFC-5967/RFC-5967.txt","version":null},{"body":"IETF","designation":"RFC 6010","folder":"IETF/RFC-6010","source":"IETF/RFC-6010/RFC-6010.txt","version":null},{"body":"IETF","designation":"RFC 6031","folder":"IETF/RFC-6031","source":"IETF/RFC-6031/RFC-6031.txt","version":null},{"body":"IETF","designation":"RFC 6482","folder":"IETF/RFC-6482","source":"IETF/RFC-6482/RFC-6482.txt","version":null},{"body":"IETF","designation":"RFC 6486","folder":"IETF/RFC-6486","source":"IETF/RFC-6486/RFC-6486.txt","version":null},{"body":"IETF","designation":"RFC 6698","folder":"IETF/RFC-6698","source":"IETF/RFC-6698/RFC-6698.txt","version":null},{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null},{"body":"IETF","designation":"RFC 6960","folder":"IETF/RFC-6960","source":"IETF/RFC-6960/RFC-6960.txt","version":null},{"body":"IETF","designation":"RFC 6961","folder":"IETF/RFC-6961","source":"IETF/RFC-6961/RFC-6961.txt","version":null},{"body":"IETF","designation":"RFC 7030","folder":"IETF/RFC-7030","source":"IETF/RFC-7030/RFC-7030.txt","version":null},{"body":"IETF","designation":"RFC 7049","folder":"IETF/RFC-7049","source":"IETF/RFC-7049/RFC-7049.txt","version":null},{"body":"IETF","designation":"RFC 7170","folder":"IETF/RFC-7170","source":"IETF/RFC-7170/RFC-7170.txt","version":null},{"body":"IETF","designation":"RFC 7250","folder":"IETF/RFC-7250","source":"IETF/RFC-7250/RFC-7250.txt","version":null},{"body":"IETF","designation":"RFC 7468","folder":"IETF/RFC-7468","source":"IETF/RFC-7468/RFC-7468.txt","version":null},{"body":"IETF","designation":"RFC 7515","folder":"IETF/RFC-7515","source":"IETF/RFC-7515/RFC-7515.txt","version":null},{"body":"IETF","designation":"RFC 7517","folder":"IETF/RFC-7517","source":"IETF/RFC-7517/RFC-7517.txt","version":null},{"body":"IETF","designation":"RFC 8418","folder":"IETF/RFC-8418","source":"IETF/RFC-8418/RFC-8418.txt","version":null},{"body":"IETF","designation":"RFC 8419","folder":"IETF/RFC-8419","source":"IETF/RFC-8419/RFC-8419.txt","version":null},{"body":"IETF","designation":"RFC 8422","folder":"IETF/RFC-8422","source":"IETF/RFC-8422/RFC-8422.txt","version":null},{"body":"IETF","designation":"RFC 8551","folder":"IETF/RFC-8551","source":"IETF/RFC-8551/RFC-8551.txt","version":null},{"body":"IETF","designation":"RFC 8572","folder":"IETF/RFC-8572","source":"IETF/RFC-8572/RFC-8572.txt","version":null},{"body":"IETF","designation":"RFC 8619","folder":"IETF/RFC-8619","source":"IETF/RFC-8619/RFC-8619.txt","version":null},{"body":"IETF","designation":"RFC 8696","folder":"IETF/RFC-8696","source":"IETF/RFC-8696/RFC-8696.txt","version":null},{"body":"IETF","designation":"RFC 8705","folder":"IETF/RFC-8705","source":"IETF/RFC-8705/RFC-8705.txt","version":null},{"body":"IETF","designation":"RFC 8949","folder":"IETF/RFC-8949","source":"IETF/RFC-8949/RFC-8949.txt","version":null},{"body":"IETF","designation":"RFC 9090","folder":"IETF/RFC-9090","source":"IETF/RFC-9090/RFC-9090.txt","version":null},{"body":"IETF","designation":"RFC 9162","folder":"IETF/RFC-9162","source":"IETF/RFC-9162/RFC-9162.txt","version":null},{"body":"IETF","designation":"RFC 9277","folder":"IETF/RFC-9277","source":"IETF/RFC-9277/RFC-9277.txt","version":null},{"body":"IETF","designation":"RFC 9440","folder":"IETF/RFC-9440","source":"IETF/RFC-9440/RFC-9440.txt","version":null},{"body":"IETF","designation":"RFC 9525","folder":"IETF/RFC-9525","source":"IETF/RFC-9525/RFC-9525.txt","version":null},{"body":"IETF","designation":"RFC 9608","folder":"IETF/RFC-9608","source":"IETF/RFC-9608/RFC-9608.txt","version":null},{"body":"IETF","designation":"RFC 9999","folder":"IETF/RFC-9999","source":"IETF/RFC-9999/RFC-9999.txt","version":null}],"search_text":"ITU-T ITU-T X.690 nested-reference unavailable"},{"id":"ITU-T ITU-T X.691","type":"specification","body":"ITU-T","designation":"ITU-T X.691","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-691/en","download_urls":["https://www.itu.int/rec/T-REC-X-691/en"],"folder":"ITU-T/ITU-T-X.691","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5480","folder":"IETF/RFC-5480","source":"IETF/RFC-5480/RFC-5480.txt","version":null}],"search_text":"ITU-T ITU-T X.691 nested-reference unavailable"},{"id":"ITU-T ITU-T X.700","type":"specification","body":"ITU-T","designation":"ITU-T X.700","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-700/en","download_urls":["https://www.itu.int/rec/T-REC-X-700/en"],"folder":"ITU-T/ITU-T-X.700","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"TS 101 270-2","folder":"ETSI/TS-101-270-2-V1.1.1","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf","version":"1.1.1"}],"search_text":"ITU-T ITU-T X.700 nested-reference unavailable"},{"id":"ITU-T ITU-T X.733","type":"specification","body":"ITU-T","designation":"ITU-T X.733","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-733/en","download_urls":["https://www.itu.int/rec/T-REC-X-733/en"],"folder":"ITU-T/ITU-T-X.733","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null},{"body":"IETF","designation":"RFC 6632","folder":"IETF/RFC-6632","source":"IETF/RFC-6632/RFC-6632.txt","version":null}],"search_text":"ITU-T ITU-T X.733 nested-reference unavailable"},{"id":"ITU-T ITU-T X.736","type":"specification","body":"ITU-T","designation":"ITU-T X.736","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-736/en","download_urls":["https://www.itu.int/rec/T-REC-X-736/en"],"folder":"ITU-T/ITU-T-X.736","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5674","folder":"IETF/RFC-5674","source":"IETF/RFC-5674/RFC-5674.txt","version":null}],"search_text":"ITU-T ITU-T X.736 nested-reference unavailable"},{"id":"ITU-T ITU-T X.744","type":"specification","body":"ITU-T","designation":"ITU-T X.744","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-744/en","download_urls":["https://www.itu.int/rec/T-REC-X-744/en"],"folder":"ITU-T/ITU-T-X.744","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 2564","folder":"IETF/RFC-2564","source":"IETF/RFC-2564/RFC-2564.txt","version":null}],"search_text":"ITU-T ITU-T X.744 nested-reference unavailable"},{"id":"ITU-T ITU-T X.800","type":"specification","body":"ITU-T","designation":"ITU-T X.800","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-800/en","download_urls":["https://www.itu.int/rec/T-REC-X-800/en"],"folder":"ITU-T/ITU-T-X.800","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ITU-T ITU-T X.800 nested-reference unavailable"},{"id":"ITU-T ITU-T X.842","type":"specification","body":"ITU-T","designation":"ITU-T X.842","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-842/en","download_urls":["https://www.itu.int/rec/T-REC-X-842/en"],"folder":"ITU-T/ITU-T-X.842","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ITU-T ITU-T X.842 nested-reference unavailable"},{"id":"ITU-T ITU-T X.843","type":"specification","body":"ITU-T","designation":"ITU-T X.843","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-843/en","download_urls":["https://www.itu.int/rec/T-REC-X-843/en"],"folder":"ITU-T/ITU-T-X.843","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"ETSI","designation":"EN 319 411-1","folder":"ETSI/EN-319-411-1-V1.5.1","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf","version":"1.5.1"}],"search_text":"ITU-T ITU-T X.843 nested-reference unavailable"},{"id":"ITU-T ITU-T X.891","type":"specification","body":"ITU-T","designation":"ITU-T X.891","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-X-891/en","download_urls":["https://www.itu.int/rec/T-REC-X-891/en"],"folder":"ITU-T/ITU-T-X.891","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 6839","folder":"IETF/RFC-6839","source":"IETF/RFC-6839/RFC-6839.txt","version":null}],"search_text":"ITU-T ITU-T X.891 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.122","type":"specification","body":"ITU-T","designation":"ITU-T Y.122","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-122/en","download_urls":["https://www.itu.int/rec/T-REC-Y-122/en"],"folder":"ITU-T/ITU-T-Y.122","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null}],"search_text":"ITU-T ITU-T Y.122 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.130","type":"specification","body":"ITU-T","designation":"ITU-T Y.130","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-130/en","download_urls":["https://www.itu.int/rec/T-REC-Y-130/en"],"folder":"ITU-T/ITU-T-Y.130","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5860","folder":"IETF/RFC-5860","source":"IETF/RFC-5860/RFC-5860.txt","version":null}],"search_text":"ITU-T ITU-T Y.130 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.131","type":"specification","body":"ITU-T","designation":"ITU-T Y.131","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-131/en","download_urls":["https://www.itu.int/rec/T-REC-Y-131/en"],"folder":"ITU-T/ITU-T-Y.131","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4031","folder":"IETF/RFC-4031","source":"IETF/RFC-4031/RFC-4031.txt","version":null},{"body":"IETF","designation":"RFC 4176","folder":"IETF/RFC-4176","source":"IETF/RFC-4176/RFC-4176.txt","version":null}],"search_text":"ITU-T ITU-T Y.131 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.140","type":"specification","body":"ITU-T","designation":"ITU-T Y.140","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-140/en","download_urls":["https://www.itu.int/rec/T-REC-Y-140/en"],"folder":"ITU-T/ITU-T-Y.140","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null}],"search_text":"ITU-T ITU-T Y.140 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.141","type":"specification","body":"ITU-T","designation":"ITU-T Y.141","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-141/en","download_urls":["https://www.itu.int/rec/T-REC-Y-141/en"],"folder":"ITU-T/ITU-T-Y.141","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 4717","folder":"IETF/RFC-4717","source":"IETF/RFC-4717/RFC-4717.txt","version":null},{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T Y.141 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.145","type":"specification","body":"ITU-T","designation":"ITU-T Y.145","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-145/en","download_urls":["https://www.itu.int/rec/T-REC-Y-145/en"],"folder":"ITU-T/ITU-T-Y.145","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5087","folder":"IETF/RFC-5087","source":"IETF/RFC-5087/RFC-5087.txt","version":null}],"search_text":"ITU-T ITU-T Y.145 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.154","type":"specification","body":"ITU-T","designation":"ITU-T Y.154","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-154/en","download_urls":["https://www.itu.int/rec/T-REC-Y-154/en"],"folder":"ITU-T/ITU-T-Y.154","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3393","folder":"IETF/RFC-3393","source":"IETF/RFC-3393/RFC-3393.txt","version":null},{"body":"IETF","designation":"RFC 4150","folder":"IETF/RFC-4150","source":"IETF/RFC-4150/RFC-4150.txt","version":null},{"body":"IETF","designation":"RFC 4737","folder":"IETF/RFC-4737","source":"IETF/RFC-4737/RFC-4737.txt","version":null},{"body":"IETF","designation":"RFC 5481","folder":"IETF/RFC-5481","source":"IETF/RFC-5481/RFC-5481.txt","version":null},{"body":"IETF","designation":"RFC 5559","folder":"IETF/RFC-5559","source":"IETF/RFC-5559/RFC-5559.txt","version":null},{"body":"IETF","designation":"RFC 5560","folder":"IETF/RFC-5560","source":"IETF/RFC-5560/RFC-5560.txt","version":null},{"body":"IETF","designation":"RFC 5835","folder":"IETF/RFC-5835","source":"IETF/RFC-5835/RFC-5835.txt","version":null},{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null},{"body":"IETF","designation":"RFC 6049","folder":"IETF/RFC-6049","source":"IETF/RFC-6049/RFC-6049.txt","version":null},{"body":"IETF","designation":"RFC 6703","folder":"IETF/RFC-6703","source":"IETF/RFC-6703/RFC-6703.txt","version":null},{"body":"IETF","designation":"RFC 6798","folder":"IETF/RFC-6798","source":"IETF/RFC-6798/RFC-6798.txt","version":null},{"body":"IETF","designation":"RFC 7398","folder":"IETF/RFC-7398","source":"IETF/RFC-7398/RFC-7398.txt","version":null},{"body":"IETF","designation":"RFC 7679","folder":"IETF/RFC-7679","source":"IETF/RFC-7679/RFC-7679.txt","version":null},{"body":"IETF","designation":"RFC 7680","folder":"IETF/RFC-7680","source":"IETF/RFC-7680/RFC-7680.txt","version":null},{"body":"IETF","designation":"RFC 7799","folder":"IETF/RFC-7799","source":"IETF/RFC-7799/RFC-7799.txt","version":null}],"search_text":"ITU-T ITU-T Y.154 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.156","type":"specification","body":"ITU-T","designation":"ITU-T Y.156","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-156/en","download_urls":["https://www.itu.int/rec/T-REC-Y-156/en"],"folder":"ITU-T/ITU-T-Y.156","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null}],"search_text":"ITU-T ITU-T Y.156 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.171","type":"specification","body":"ITU-T","designation":"ITU-T Y.171","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-171/en","download_urls":["https://www.itu.int/rec/T-REC-Y-171/en"],"folder":"ITU-T/ITU-T-Y.171","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 3429","folder":"IETF/RFC-3429","source":"IETF/RFC-3429/RFC-3429.txt","version":null},{"body":"IETF","designation":"RFC 4377","folder":"IETF/RFC-4377","source":"IETF/RFC-4377/RFC-4377.txt","version":null},{"body":"IETF","designation":"RFC 4378","folder":"IETF/RFC-4378","source":"IETF/RFC-4378/RFC-4378.txt","version":null},{"body":"IETF","designation":"RFC 5704","folder":"IETF/RFC-5704","source":"IETF/RFC-5704/RFC-5704.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7325","folder":"IETF/RFC-7325","source":"IETF/RFC-7325/RFC-7325.txt","version":null}],"search_text":"ITU-T ITU-T Y.171 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.173","type":"specification","body":"ITU-T","designation":"ITU-T Y.173","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-173/en","download_urls":["https://www.itu.int/rec/T-REC-Y-173/en"],"folder":"ITU-T/ITU-T-Y.173","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5851","folder":"IETF/RFC-5851","source":"IETF/RFC-5851/RFC-5851.txt","version":null},{"body":"IETF","designation":"RFC 5951","folder":"IETF/RFC-5951","source":"IETF/RFC-5951/RFC-5951.txt","version":null},{"body":"IETF","designation":"RFC 6136","folder":"IETF/RFC-6136","source":"IETF/RFC-6136/RFC-6136.txt","version":null},{"body":"IETF","designation":"RFC 6291","folder":"IETF/RFC-6291","source":"IETF/RFC-6291/RFC-6291.txt","version":null},{"body":"IETF","designation":"RFC 6329","folder":"IETF/RFC-6329","source":"IETF/RFC-6329/RFC-6329.txt","version":null},{"body":"IETF","designation":"RFC 6371","folder":"IETF/RFC-6371","source":"IETF/RFC-6371/RFC-6371.txt","version":null},{"body":"IETF","designation":"RFC 6374","folder":"IETF/RFC-6374","source":"IETF/RFC-6374/RFC-6374.txt","version":null},{"body":"IETF","designation":"RFC 7174","folder":"IETF/RFC-7174","source":"IETF/RFC-7174/RFC-7174.txt","version":null},{"body":"IETF","designation":"RFC 7276","folder":"IETF/RFC-7276","source":"IETF/RFC-7276/RFC-7276.txt","version":null},{"body":"IETF","designation":"RFC 7455","folder":"IETF/RFC-7455","source":"IETF/RFC-7455/RFC-7455.txt","version":null}],"search_text":"ITU-T ITU-T Y.173 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.217","type":"specification","body":"ITU-T","designation":"ITU-T Y.217","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-217/en","download_urls":["https://www.itu.int/rec/T-REC-Y-217/en"],"folder":"ITU-T/ITU-T-Y.217","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5975","folder":"IETF/RFC-5975","source":"IETF/RFC-5975/RFC-5975.txt","version":null},{"body":"IETF","designation":"RFC 5976","folder":"IETF/RFC-5976","source":"IETF/RFC-5976/RFC-5976.txt","version":null}],"search_text":"ITU-T ITU-T Y.217 nested-reference unavailable"},{"id":"ITU-T ITU-T Y.261","type":"specification","body":"ITU-T","designation":"ITU-T Y.261","version":null,"title":null,"purpose":null,"status":"unavailable","download_url":"https://www.itu.int/rec/T-REC-Y-261/en","download_urls":["https://www.itu.int/rec/T-REC-Y-261/en"],"folder":"ITU-T/ITU-T-Y.261","files":{},"tags":["nested-reference","unavailable"],"summary":null,"scope_keywords":[],"parent_legal_regulations":[],"parent_specifications":[{"body":"IETF","designation":"RFC 5654","folder":"IETF/RFC-5654","source":"IETF/RFC-5654/RFC-5654.txt","version":null},{"body":"IETF","designation":"RFC 7087","folder":"IETF/RFC-7087","source":"IETF/RFC-7087/RFC-7087.txt","version":null}],"search_text":"ITU-T ITU-T Y.261 nested-reference unavailable"},{"id":"OpenID OpenID Federation V1.0","type":"specification","body":"OpenID","designation":"OpenID Federation","version":"1.0","title":"OpenID Federation","purpose":null,"status":"unchanged","download_url":"https://openid.net/specs/openid-federation-1_0.html","download_urls":["https://openid.net/specs/openid-federation-1_0.html"],"folder":"OpenID/OpenID-Federation-V1.0","files":{"html":{"path":"standards/OpenID/OpenID-Federation-V1.0/OpenID-Federation-V1.0.html","sha256":"4a71afdfbed5755d6704d6a089f450f10aa9914204b283eae5fadee2897d1911"}},"tags":["nested-reference","unchanged"],"summary":"A federation can be expressed as an agreement between parties that trust each other.\n In bilateral federations, direct trust can be established between\n two organizations belonging to the same federation.\n In a multilateral federation, bilateral agreements might not be practical,\n in which case, trust can be mediated by a third party.\n That is the model used in this specification. ¶ \n \n An Entity in the federation must be able to trust that other Entities\n it interacts with belong to the same federation.\n It must also be able to trust that the information the other Entities\n publish about themselves has not been tampered with during transport\n and that it adheres to the federation's policies. ¶ \n \n This specification defines basic components to build multilateral\n federations. It also defines how to apply them in the contexts of OpenID\n Connect and OAuth 2.0. These components can be used","scope_keywords":["openid","federation","http","https","key","license","policies","trust"],"parent_legal_regulations":[],"parent_specifications":[{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"}],"search_text":"OpenID OpenID Federation 1.0 OpenID Federation A federation can be expressed as an agreement between parties that trust each other.\n In bilateral federations, direct trust can be established between\n two organizations belonging to the same federation.\n In a multilateral federation, bilateral agreements might not be practical,\n in which case, trust can be mediated by a third party.\n That is the model used in this specification. ¶ \n \n An Entity in the federation must be able to trust that other Entities\n it interacts with belong to the same federation.\n It must also be able to trust that the information the other Entities\n publish about themselves has not been tampered with during transport\n and that it adheres to the federation's policies. ¶ \n \n This specification defines basic components to build multilateral\n federations. It also defines how to apply them in the contexts of OpenID\n Connect and OAuth 2.0. These components can be used openid federation http https key license policies trust nested-reference unchanged"},{"id":"OpenID OpenID4VC-HAIP V1.0","type":"specification","body":"OpenID","designation":"OpenID4VC-HAIP","version":"1.0","title":"OpenID4VC High Assurance Interoperability Profile","purpose":null,"status":"unchanged","download_url":"https://openid.net/specs/openid4vc-high-assurance-interoperability-profile-1_0-final.html","download_urls":["https://openid.net/specs/openid4vc-high-assurance-interoperability-profile-1_0-final.html","https://openid.net/specs/openid4vc-high-assurance-interoperability-profile-1_0.html"],"folder":"OpenID/OpenID4VC-HAIP-V1.0","files":{"html":{"path":"standards/OpenID/OpenID4VC-HAIP-V1.0/OpenID4VC-HAIP-V1.0.html","sha256":"3996e0479d06b72d6d68668b8ae3cd39fddfc29ae9220c0c3fead7dc060ec4fb"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification defines a profile of OpenID for Verifiable Credentials in combination with the credential formats IETF SD-JWT VC [ I-D.ietf-oauth-sd-jwt-vc ] and ISO mdoc [ ISO.18013-5 ] . The aim is to select features and to define a set of requirements for the existing specifications to enable interoperability among Issuers, Wallets, and Verifiers of Credentials where a high level of security and privacy is required. The profiled specifications include OpenID for Verifiable Credential Issuance [ OIDF.OID4VCI ] , OpenID for Verifiable Presentations [ OIDF.OID4VP ] , IETF SD-JWT VC [ I-D.ietf-oauth-sd-jwt-vc ] , and ISO mdoc [ ISO.18013-5 ] . ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Target Audience/Usage \n \n \n 1.2 .   Errata Revisions \n \n \n 1.3 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Scope \n \n \n 3.1 .   Assumpti","scope_keywords":["openid","haip","credential","credentials","http","https","issuer","key","license","presentation","profile","verifiable","wallet","wallets"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"}],"search_text":"OpenID OpenID4VC-HAIP 1.0 OpenID4VC High Assurance Interoperability Profile This specification defines a profile of OpenID for Verifiable Credentials in combination with the credential formats IETF SD-JWT VC [ I-D.ietf-oauth-sd-jwt-vc ] and ISO mdoc [ ISO.18013-5 ] . The aim is to select features and to define a set of requirements for the existing specifications to enable interoperability among Issuers, Wallets, and Verifiers of Credentials where a high level of security and privacy is required. The profiled specifications include OpenID for Verifiable Credential Issuance [ OIDF.OID4VCI ] , OpenID for Verifiable Presentations [ OIDF.OID4VP ] , IETF SD-JWT VC [ I-D.ietf-oauth-sd-jwt-vc ] , and ISO mdoc [ ISO.18013-5 ] . ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Target Audience/Usage \n \n \n 1.2 .   Errata Revisions \n \n \n 1.3 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Scope \n \n \n 3.1 .   Assumpti openid haip credential credentials http https issuer key license presentation profile verifiable wallet wallets cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"OpenID OpenID4VCI V1.0","type":"specification","body":"OpenID","designation":"OpenID4VCI","version":"1.0","title":"OpenID for Verifiable Credential Issuance","purpose":null,"status":"unchanged","download_url":"https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html","download_urls":["https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html"],"folder":"OpenID/OpenID4VCI-V1.0","files":{"html":{"path":"standards/OpenID/OpenID4VCI-V1.0/OpenID4VCI-V1.0.html","sha256":"f123c3178cacd27688b15b762098a045e9eb35eccfe2f5f18a357c3815e06ba7"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification defines an API for the issuance of Verifiable Credentials. ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Errata revisions \n \n \n 1.2 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Overview \n \n \n 3.1 .   Credential Issuer \n \n \n 3.2 .   OAuth 2.0 \n \n \n 3.3 .   Core Concepts \n \n \n 3.3.1 .   Credential Formats and Credential Format Profiles \n \n \n 3.3.2 .   Batch Credential Issuance \n \n \n 3.3.3 .   Issuance Flow Variations \n \n \n 3.3.4 .   Identifying Credentials Being Issued Throughout the Issuance Flow \n \n \n \n \n 3.4 .   Authorization Code Flow \n \n \n 3.5 .   Pre-Authorized Code Flow \n \n \n \n \n 4 .   Credential Offer Endpoint \n \n \n 4.1 .   Credential Offer \n \n \n 4.1.1 .   Credential Offer Parameters \n \n \n 4.1.2 .   Sending Credential Offer by Value Using credential_offer Parameter \n \n \n 4.1.3 .   Sending Credential ","scope_keywords":["openid","vci","authorization","credential","credentials","http","https","issuer","key","license","profile","profiles","verifiable"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS01","folder":"ARF/TS01-V1.2","source":"ARF/TS01-V1.2/TS01-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS03","folder":"ARF/TS03-V1.5.2","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md","version":"1.5.2"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 471","folder":"ETSI/TS-119-471-V1.1.1","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"},{"body":"IETF","designation":"SD-JWT VC","folder":"IETF/SD-JWT-VC","source":"IETF/SD-JWT-VC/SD-JWT-VC.html","version":null}],"search_text":"OpenID OpenID4VCI 1.0 OpenID for Verifiable Credential Issuance This specification defines an API for the issuance of Verifiable Credentials. ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Errata revisions \n \n \n 1.2 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Overview \n \n \n 3.1 .   Credential Issuer \n \n \n 3.2 .   OAuth 2.0 \n \n \n 3.3 .   Core Concepts \n \n \n 3.3.1 .   Credential Formats and Credential Format Profiles \n \n \n 3.3.2 .   Batch Credential Issuance \n \n \n 3.3.3 .   Issuance Flow Variations \n \n \n 3.3.4 .   Identifying Credentials Being Issued Throughout the Issuance Flow \n \n \n \n \n 3.4 .   Authorization Code Flow \n \n \n 3.5 .   Pre-Authorized Code Flow \n \n \n \n \n 4 .   Credential Offer Endpoint \n \n \n 4.1 .   Credential Offer \n \n \n 4.1.1 .   Credential Offer Parameters \n \n \n 4.1.2 .   Sending Credential Offer by Value Using credential_offer Parameter \n \n \n 4.1.3 .   Sending Credential  openid vci authorization credential credentials http https issuer key license profile profiles verifiable cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"OpenID OpenID4VP V1.0","type":"specification","body":"OpenID","designation":"OpenID4VP","version":"1.0","title":"OpenID for Verifiable Presentations","purpose":null,"status":"unchanged","download_url":"https://openid.net/specs/openid-4-verifiable-presentations-1_0.html","download_urls":["https://openid.net/specs/openid-4-verifiable-presentations-1_0.html"],"folder":"OpenID/OpenID4VP-V1.0","files":{"html":{"path":"standards/OpenID/OpenID4VP-V1.0/OpenID4VP-V1.0.html","sha256":"e4f0abc689afd0a4f6c41b83954d7f970c5263a26143ad861216aea9918993bb"}},"tags":["cited-by-eu-law","implementing-regulation","nested-reference","unchanged"],"summary":"This specification defines a protocol for requesting and presenting Credentials. ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Additional Authors \n \n \n 1.2 .   Errata revisions \n \n \n 1.3 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Overview \n \n \n 3.1 .   Same Device Flow \n \n \n 3.2 .   Cross Device Flow \n \n \n \n \n 4 .   Scope \n \n \n 5 .   Authorization Request \n \n \n 5.1 .   New Parameters \n \n \n 5.2 .   Existing Parameters \n \n \n 5.3 .   Requesting Presentations without Holder Binding Proofs \n \n \n 5.4 .   Examples \n \n \n 5.5 .   Using scope Parameter to Request Presentations \n \n \n 5.6 .   Response Type vp_token \n \n \n 5.7 .   Passing Authorization Request Across Devices \n \n \n 5.8 .   aud of a Request Object \n \n \n 5.9 .   Client Identifier Prefix and Verifier Metadata Management \n \n \n 5.9.1 .   Syntax \n \n \n 5.9.2 .   Fallback \n \n \n ","scope_keywords":["openid","authorization","credential","credentials","holder","http","https","key","license","management","presentation","verifiable"],"parent_legal_regulations":[{"celex":"32026R1731","eli":"https://data.europa.eu/eli/reg_impl/2026/1731/oj/eng","id":"2026-1731","kind":"implementing_regulation","section":"implementing-acts","source":"implementing-acts/2026-1731/2026-1731.md","title":"Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs"}],"parent_specifications":[{"body":"ARF","designation":"TS05","folder":"ARF/TS05-V1.2.1","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md","version":"1.2.1"},{"body":"ARF","designation":"TS07","folder":"ARF/TS07-V0.11","source":"ARF/TS07-V0.11/TS07-V0.11.md","version":"0.11"},{"body":"ARF","designation":"TS10","folder":"ARF/TS10-V1.2","source":"ARF/TS10-V1.2/TS10-V1.2.md","version":"1.2"},{"body":"ARF","designation":"TS11","folder":"ARF/TS11-V1.0.1","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS12","folder":"ARF/TS12-V1.0.1","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md","version":"1.0.1"},{"body":"ARF","designation":"TS13","folder":"ARF/TS13","source":"ARF/TS13/TS13-V1.0.1.md","version":null},{"body":"ARF","designation":"TS14","folder":"ARF/TS14-V1.0","source":"ARF/TS14-V1.0/TS14-V1.0.md","version":"1.0"},{"body":"ETSI","designation":"TR 119 476","folder":"ETSI/TR-119-476-V1.2.1","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 432","folder":"ETSI/TS-119-432-V1.3.1","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf","version":"1.3.1"},{"body":"ETSI","designation":"TS 119 472-2","folder":"ETSI/TS-119-472-2-V1.2.1","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 472-3","folder":"ETSI/TS-119-472-3-V1.1.1","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf","version":"1.1.1"},{"body":"ETSI","designation":"TS 119 475","folder":"ETSI/TS-119-475-V1.2.1","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf","version":"1.2.1"},{"body":"ETSI","designation":"TS 119 478","folder":"ETSI/TS-119-478-V1.1.1","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf","version":"1.1.1"}],"search_text":"OpenID OpenID4VP 1.0 OpenID for Verifiable Presentations This specification defines a protocol for requesting and presenting Credentials. ¶ \n \n \n \n ▲ \n Table of Contents \n \n \n \n 1 .   Introduction \n \n \n 1.1 .   Additional Authors \n \n \n 1.2 .   Errata revisions \n \n \n 1.3 .   Requirements Notation and Conventions \n \n \n \n \n 2 .   Terminology \n \n \n 3 .   Overview \n \n \n 3.1 .   Same Device Flow \n \n \n 3.2 .   Cross Device Flow \n \n \n \n \n 4 .   Scope \n \n \n 5 .   Authorization Request \n \n \n 5.1 .   New Parameters \n \n \n 5.2 .   Existing Parameters \n \n \n 5.3 .   Requesting Presentations without Holder Binding Proofs \n \n \n 5.4 .   Examples \n \n \n 5.5 .   Using scope Parameter to Request Presentations \n \n \n 5.6 .   Response Type vp_token \n \n \n 5.7 .   Passing Authorization Request Across Devices \n \n \n 5.8 .   aud of a Request Object \n \n \n 5.9 .   Client Identifier Prefix and Verifier Metadata Management \n \n \n 5.9.1 .   Syntax \n \n \n 5.9.2 .   Fallback \n \n \n  openid authorization credential credentials holder http https key license management presentation verifiable cited-by-eu-law implementing-regulation nested-reference unchanged 2026-1731 Amending CIRs 2024/2977, 2979, 2980, 2982 — reference standards and specs 32026R1731"},{"id":"legal:eidas-consolidated","type":"legal_regulation","act_id":"eidas-consolidated","section":"regulation","title":"Regulation (EU) No 910/2014 (eIDAS) — consolidated text","celex":"02014R0910-20241018","eli":"http://data.europa.eu/eli/reg/2014/910/2024-10-18/oj/eng","kind":"regulation","files":{"html":{"item_url":"http://publications.europa.eu/resource/cellar/6a1e14d9-907e-11ef-a130-01aa75ed71a1.0007.02/DOC_2","path":"regulation/eidas-consolidated/eidas-consolidated.html","sha256":"b4ab7d733d234eef3a505330717d8a8d4d6388f2d9a0a4bfcde2d1b497ba72ce","size":454927},"pdf":{"item_url":"http://publications.europa.eu/resource/cellar/6a1e14d9-907e-11ef-a130-01aa75ed71a1.0007.03/DOC_2","path":"regulation/eidas-consolidated/eidas-consolidated.pdf","sha256":"1fded3274b202801de22c820bed859bf27b50529faf72fdeabd0a29c32f73604","size":735403}},"scope_keywords":["authentication","certificate","certificates","delivery","electronic","european","identification","legal","means","natural","person","persons","qualified","registered","regulation","seal","service","services","signature","signatures","trust","union","validation","wallets"],"summary":"on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC This Regulation aims to ensure the proper functioning of the internal market and the provision of an adequate level of security of electronic identification means and trust services used across the Union, in order to enable and facilitate the exercise by natural and legal persons of the right to participate in digital society safely and to access online public and private services throughout the Union. For those purposes, this Regulation:\n\n \n\n \n\n(a) \n\n \n\n \n\nlays down the conditions under which Member States are to recognise natural and legal persons’ electronic identification means falling under a notified electronic identification scheme of another Member State and provide and recognise European Digital Identity Wallets;\n\n \n\n \n\n \n\n \n\n(b) \n\n \n\n \n\nlays…","summary_meta":{"artifact":"md","generated_at":"2026-05-19T08:14:14.996299+00:00","sources":["eli-subtitle","article-1-subject-matter"],"status":"ok"},"consolidated_as_of":"2024-10-18","search_text":"eidas-consolidated Regulation (EU) No 910/2014 (eIDAS) — consolidated text 02014R0910-20241018 regulation regulation on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC This Regulation aims to ensure the proper functioning of the internal market and the provision of an adequate level of security of electronic identification means and trust services used across the Union, in order to enable and facilitate the exercise by natural and legal persons of the right to participate in digital society safely and to access online public and private services throughout the Union. For those purposes, this Regulation:\n\n \n\n \n\n(a) \n\n \n\n \n\nlays down the conditions under which Member States are to recognise natural and legal persons’ electronic identification means falling under a notified electronic identification scheme of another Member State and provide and recognise European Digital Identity Wallets;\n\n \n\n \n\n \n\n \n\n(b) \n\n \n\n \n\nlays… authentication certificate certificates delivery electronic european identification legal means natural person persons qualified registered regulation seal service services signature signatures trust union validation wallets"}],"edges":[{"from":"ETSI EN 319 421 V1.3.1","to":"CEN CEN/TS","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"legal:2025-2162","to":"CEN CEN/TS 18170 V2025","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2025-2532","to":"CEN CEN/TS 18170 V2025","kind":"cites","source":"implementing-acts/2025-2532/2025-2532.md"},{"from":"legal:2025-1943","to":"CEN CEN/TS 419261 V2015","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-1942","to":"ETSI EN 319 102-1 V1.4.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1945","to":"ETSI EN 319 102-1 V1.4.1","kind":"cites","source":"implementing-acts/2025-1945/2025-1945.md"},{"from":"legal:2025-1946","to":"ETSI EN 319 102-1 V1.4.1","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"ETSI TS 119 441 V1.2.1","to":"ETSI EN 319 102-1 V1.4.1","kind":"references","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf"},{"from":"legal:2025-2531","to":"ETSI EN 319 122-1 V1.3.1","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2024-2979","to":"ETSI EN 319 132-1 V1.3.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2025-2531","to":"ETSI EN 319 132-1 V1.3.1","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2024-2979","to":"ETSI EN 319 142-1 V1.2.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2026-1731","to":"ETSI EN 319 142-1 V1.2.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2024-2979","to":"ETSI EN 319 162-1 V1.1.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2024-2979","to":"ETSI EN 319 162-2 V1.1.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2025-1566","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1566/2025-1566.md"},{"from":"legal:2025-1567","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1567/2025-1567.md"},{"from":"legal:2025-1569","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1569/2025-1569.md"},{"from":"legal:2025-1929","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"legal:2025-1942","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1943","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1946","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"legal:2025-2160","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-2160/2025-2160.md"},{"from":"legal:2025-2531","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2025-2532","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2025-2532/2025-2532.md"},{"from":"legal:2026-1735","to":"ETSI EN 319 401 V3.2.1","kind":"cites","source":"implementing-acts/2026-1735/2026-1735.md"},{"from":"ETSI TS 119 431-1 V1.3.1","to":"ETSI EN 319 401 V3.2.1","kind":"references","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf"},{"from":"legal:2025-2162","to":"ETSI EN 319 403-1 V2.3.1","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ETSI EN 319 403 V2.3.0","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"legal:2025-1943","to":"ETSI EN 319 411-1 V1.5.1","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 411-1 V1.5.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1943","to":"ETSI EN 319 411-2 V2.6.1","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-2527","to":"ETSI EN 319 411-2 V2.6.1","kind":"cites","source":"implementing-acts/2025-2527/2025-2527.md"},{"from":"legal:2025-1943","to":"ETSI EN 319 412-2 V2.4.1","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2026-1731","to":"ETSI EN 319 412-2 V2.4.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2025-1943","to":"ETSI EN 319 412-3 V1.3.1","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2026-1731","to":"ETSI EN 319 412-3 V1.3.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 495 V1.7.1","to":"ETSI EN 319 412-4 V1.3.0","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"legal:2025-1929","to":"ETSI EN 319 421 V1.3.1","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"legal:2025-2532","to":"ETSI EN 319 421 V1.3.1","kind":"cites","source":"implementing-acts/2025-2532/2025-2532.md"},{"from":"legal:2025-1929","to":"ETSI EN 319 422 V1.1.1","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 521 V1.1.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 522-1 V1.2.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 522-2 V1.2.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1944","to":"ETSI EN 319 522-3 V1.2.1","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2024-2979","to":"ETSI EN 3191 22-1 V1.3.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2025-2162","to":"ETSI EN 319403-1 V2.3.1","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"IETF RFC 5126","to":"ETSI TR 102 272 V1.1.1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"ETSI TR 119 411-5 V2.1.1","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"ARF TS04 V1.0.1","to":"ETSI TR 119 476 V1.2.1","kind":"references","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md"},{"from":"IETF RFC 3728","to":"ETSI TS 101 270-1 V1.2.1","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3728","to":"ETSI TS 101 270-2 V1.1.1","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3432","to":"ETSI TS 101 329-5 V1.1.2","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3611","to":"ETSI TS 101 329-5 V1.1.2","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 7266","to":"ETSI TS 101 329-5 V1.1.2","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"ETSI EN 319 422 V1.1.1","to":"ETSI TS 101 861 V1.4.1","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"IETF RFC 5698","to":"ETSI TS 101 903 V1.3.2","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 6015","to":"ETSI TS 102 034 V1.4.1","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 4998","to":"ETSI TS 102 176-1 V2.0.0","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5698","to":"ETSI TS 102 176-1 V2.0.0","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 6283","to":"ETSI TS 102 176-1 V2.0.0","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"legal:2025-1942","to":"ETSI TS 119 101 V1.1.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1945","to":"ETSI TS 119 101 V1.1.1","kind":"cites","source":"implementing-acts/2025-1945/2025-1945.md"},{"from":"legal:2025-1946","to":"ETSI TS 119 101 V1.1.1","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"ETSI TS 119 102-1 V1.3.1","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI TS 119 441 V1.2.1","to":"ETSI TS 119 102-1 V1.3.1","kind":"references","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf"},{"from":"legal:2025-1942","to":"ETSI TS 119 102-2 V1.4.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1945","to":"ETSI TS 119 102-2 V1.4.1","kind":"cites","source":"implementing-acts/2025-1945/2025-1945.md"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"ETSI TS 119 162-1 V1.1.0","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 162-2 V1.1.1","to":"ETSI TS 119 162-2 V1.1.0","kind":"references","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf"},{"from":"legal:2025-1942","to":"ETSI TS 119 172-4 V1.1.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1945","to":"ETSI TS 119 172-4 V1.1.1","kind":"cites","source":"implementing-acts/2025-1945/2025-1945.md"},{"from":"legal:2025-1946","to":"ETSI TS 119 172-4 V1.1.1","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"legal:2024-2979","to":"ETSI TS 119 182-1 V1.2.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"legal:2025-2531","to":"ETSI TS 119 182-1 V1.2.1","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2025-2527","to":"ETSI TS 119 411-5 V2.1.1","kind":"cites","source":"implementing-acts/2025-2527/2025-2527.md"},{"from":"legal:2026-1730","to":"ETSI TS 119 411-8 V1.1.1","kind":"cites","source":"implementing-acts/2026-1730/2026-1730.md"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"ETSI TS 119 412-1 V1.4.4","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"ETSI TS 119 422 V1.1.0","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"legal:2025-1567","to":"ETSI TS 119 431-1 V1.3.1","kind":"cites","source":"implementing-acts/2025-1567/2025-1567.md"},{"from":"legal:2026-1731","to":"ETSI TS 119 432 V1.3.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2025-1942","to":"ETSI TS 119 441 V1.2.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1566","to":"ETSI TS 119 461 V2.1.1","kind":"cites","source":"implementing-acts/2025-1566/2025-1566.md"},{"from":"legal:2026-798","to":"ETSI TS 119 461 V2.1.1","kind":"cites","source":"implementing-acts/2026-798/2026-798.md"},{"from":"legal:2026-1735","to":"ETSI TS 119 471 V1.1.1","kind":"cites","source":"implementing-acts/2026-1735/2026-1735.md"},{"from":"legal:2026-1731","to":"ETSI TS 119 472-1 V1.2.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2026-1731","to":"ETSI TS 119 472-2 V1.2.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2026-1731","to":"ETSI TS 119 472-3 V1.1.1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2026-1730","to":"ETSI TS 119 475 V1.2.1","kind":"cites","source":"implementing-acts/2026-1730/2026-1730.md"},{"from":"ARF TS05 V1.2.1","to":"ETSI TS 119 475 V1.2.1","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS06 V1.0.1","to":"ETSI TS 119 475 V1.2.1","kind":"references","source":"ARF/TS06-V1.0.1/TS06-V1.0.1.md"},{"from":"legal:2026-1735","to":"ETSI TS 119 478 V1.1.1","kind":"cites","source":"implementing-acts/2026-1735/2026-1735.md"},{"from":"ARF TS11 V1.0.1","to":"ETSI TS 119 478 V1.1.1","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"legal:2025-2527","to":"ETSI TS 119 495 V1.7.1","kind":"cites","source":"implementing-acts/2025-2527/2025-2527.md"},{"from":"legal:2025-1946","to":"ETSI TS 119 511 V1.1.1","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"ARF TS03 V1.5.2","to":"ETSI TS 119 602 V1.1.1","kind":"references","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md"},{"from":"ARF TS11 V1.0.1","to":"ETSI TS 119 602 V1.1.1","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"legal:2025-1942","to":"ETSI TS 119 612 V2.4.1","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1945","to":"ETSI TS 119 612 V2.4.1","kind":"cites","source":"implementing-acts/2025-1945/2025-1945.md"},{"from":"legal:2025-2162","to":"ETSI TS 119 612 V2.4.1","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2025-2164","to":"ETSI TS 119 612 V2.4.1","kind":"cites","source":"implementing-decisions/2025-2164/2025-2164.md"},{"from":"ARF TS05 V1.2.1","to":"ETSI TS 119 612 V2.4.1","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS11 V1.0.1","to":"ETSI TS 119 612 V2.4.1","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"IETF RFC 1060","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2764","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 6325","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 7174","to":"IEEE IEEE -","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 1230","to":"IEEE IEEE --","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1285","to":"IEEE IEEE --","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1512","to":"IEEE IEEE --","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1010","to":"IEEE IEEE ---","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1060","to":"IEEE IEEE ---","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE ---","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 990","to":"IEEE IEEE ---","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE -----","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE .....................96","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 6988","to":"IEEE IEEE 100","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 2130","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2133","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-2133/RFC-2133.txt"},{"from":"IETF RFC 2553","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 2828","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3679","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-3679/RFC-3679.txt"},{"from":"IETF RFC 4833","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 4898","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5444","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5661","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 6557","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6943","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7049","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7252","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7519","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7530","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 8089","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8943","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-8943/RFC-8943.txt"},{"from":"IETF RFC 8949","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8981","to":"IEEE IEEE 1003.1","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 7970","to":"IEEE IEEE 1003.1-2001","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 4833","to":"IEEE IEEE 1003.1-2004","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 6622","to":"IEEE IEEE 1003.1-2008","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 7011","to":"IEEE IEEE 1003.1-2008","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7182","to":"IEEE IEEE 1003.1-2008","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 9162","to":"IEEE IEEE 1003.1-2008","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 2553","to":"IEEE IEEE 1003.1.","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 2168","to":"IEEE IEEE 1003.2-1992","kind":"references","source":"IETF/RFC-2168/RFC-2168.txt"},{"from":"IETF RFC 2915","to":"IEEE IEEE 1003.2-1992","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 3402","to":"IEEE IEEE 1003.2-1992","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IEEE IEEE 1003.2-1992","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 9110","to":"IEEE IEEE 105","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9711","to":"IEEE IEEE 1149.7-2009","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 1667","to":"IEEE IEEE 1278.1","kind":"references","source":"IETF/RFC-1667/RFC-1667.txt"},{"from":"IETF RFC 2502","to":"IEEE IEEE 1278.1-1995","kind":"references","source":"IETF/RFC-2502/RFC-2502.txt"},{"from":"IETF RFC 2502","to":"IEEE IEEE 1278.2-1995","kind":"references","source":"IETF/RFC-2502/RFC-2502.txt"},{"from":"IETF RFC 1759","to":"IEEE IEEE 1284","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 3805","to":"IEEE IEEE 1284","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 1759","to":"IEEE IEEE 1284.1","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 3805","to":"IEEE IEEE 1284.1","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3075","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3275","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3278","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 4050","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-4050/RFC-4050.txt"},{"from":"IETF RFC 4055","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4492","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4556","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4754","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 5008","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5869","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 6931","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 8017","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8422","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9180","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9380","to":"IEEE IEEE 1363","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 3447","to":"IEEE IEEE 1363-2000","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 4753","to":"IEEE IEEE 1363-2000","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 4754","to":"IEEE IEEE 1363-2000","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 5903","to":"IEEE IEEE 1363-2000","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 8017","to":"IEEE IEEE 1363-2000","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 9380","to":"IEEE IEEE 1363.2-2008","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 2734","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-2734/RFC-2734.txt"},{"from":"IETF RFC 2855","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 3146","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3189","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3831","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 4390","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4541","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 6434","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6741","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7143","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7421","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 1394","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 2734","to":"IEEE IEEE 1394-1995","kind":"references","source":"IETF/RFC-2734/RFC-2734.txt"},{"from":"IETF RFC 2855","to":"IEEE IEEE 1394-1995","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 3146","to":"IEEE IEEE 1394-1995","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3189","to":"IEEE IEEE 1394-1995","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 1394-2008","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 1394.","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 6374","to":"IEEE IEEE 1588","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 7164","to":"IEEE IEEE 1588","kind":"references","source":"IETF/RFC-7164/RFC-7164.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 1588","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7384","to":"IEEE IEEE 1588","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7456","to":"IEEE IEEE 1588","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 1588-2002","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 1588-2002.","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 6374","to":"IEEE IEEE 1588-2008","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 1588-2008","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7456","to":"IEEE IEEE 1588-2008","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7821","to":"IEEE IEEE 1588-2008","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7326","to":"IEEE IEEE 1621","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7460","to":"IEEE IEEE 1621","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 6988","to":"IEEE IEEE 1621-2004","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 1722","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 1901","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 3385","to":"IEEE IEEE 1988.","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 1993","to":"IEEE IEEE 28","kind":"references","source":"IETF/RFC-1993/RFC-1993.txt"},{"from":"IETF RFC 6819","to":"IEEE IEEE 3","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 8937","to":"IEEE IEEE 33","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 2373","to":"IEEE IEEE 48","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2374","to":"IEEE IEEE 48","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 3513","to":"IEEE IEEE 48","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3831","to":"IEEE IEEE 48","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 2625","to":"IEEE IEEE 48-","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 4291","to":"IEEE IEEE 48-","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4338","to":"IEEE IEEE 48-","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 8948","to":"IEEE IEEE 48-","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 7460","to":"IEEE IEEE 61850","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 4881","to":"IEEE IEEE 64-","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4919","to":"IEEE IEEE 64-","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 4944","to":"IEEE IEEE 64-","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 7721","to":"IEEE IEEE 64-","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 0919","to":"IEEE IEEE 66","kind":"references","source":"IETF/RFC-0919/RFC-0919.txt"},{"from":"IETF RFC 0922","to":"IEEE IEEE 66","kind":"references","source":"IETF/RFC-0922/RFC-0922.txt"},{"from":"IETF RFC 919","to":"IEEE IEEE 66","kind":"references","source":"IETF/RFC-919/RFC-919.txt"},{"from":"IETF RFC 922","to":"IEEE IEEE 66","kind":"references","source":"IETF/RFC-922/RFC-922.txt"},{"from":"IETF RFC 6397","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 7049","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7285","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7493","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7950","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8259","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8746","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8785","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8941","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IEEE IEEE 754","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 2906","to":"IEEE IEEE 754-1985","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 5976","to":"IEEE IEEE 754-1985","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 6340","to":"IEEE IEEE 754-2008","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 7159","to":"IEEE IEEE 754-2008","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 7493","to":"IEEE IEEE 754-2008","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7950","to":"IEEE IEEE 754-2008","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IEEE IEEE 754-2008","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8610","to":"IEEE IEEE 754-2008.","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8746","to":"IEEE IEEE 754-2019","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8785","to":"IEEE IEEE 754-2019","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8941","to":"IEEE IEEE 754-2019","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IEEE IEEE 754-2019","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9562","to":"IEEE IEEE 754-2019","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 7049","to":"IEEE IEEE 754.","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 8259","to":"IEEE IEEE 754.","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8949","to":"IEEE IEEE 754.","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 1120","to":"IEEE IEEE 78","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1160","to":"IEEE IEEE 78","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 801.1","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 0900","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1009","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1009/RFC-1009.txt"},{"from":"IETF RFC 1010","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1060","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1083","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1083/RFC-1083.txt"},{"from":"IETF RFC 1088","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1088/RFC-1088.txt"},{"from":"IETF RFC 1089","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1089/RFC-1089.txt"},{"from":"IETF RFC 1100","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1100/RFC-1100.txt"},{"from":"IETF RFC 1103","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1103/RFC-1103.txt"},{"from":"IETF RFC 1109","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1118","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1118/RFC-1118.txt"},{"from":"IETF RFC 1122","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1122/RFC-1122.txt"},{"from":"IETF RFC 1132","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1132/RFC-1132.txt"},{"from":"IETF RFC 1140","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1140/RFC-1140.txt"},{"from":"IETF RFC 1142","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1142/RFC-1142.pdf"},{"from":"IETF RFC 1147","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1175","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1177","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1188","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1191","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1195","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1200","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1200/RFC-1200.txt"},{"from":"IETF RFC 1206","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1250","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1250/RFC-1250.txt"},{"from":"IETF RFC 1280","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1294","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1294/RFC-1294.txt"},{"from":"IETF RFC 1325","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1360","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1374","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1390","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1392","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1470","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1483","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1490","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1500","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1526","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1533","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1540","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1577","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1594","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1600","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1715","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1715/RFC-1715.txt"},{"from":"IETF RFC 1720","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1752","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1768","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1780","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1884","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 1897","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1897/RFC-1897.txt"},{"from":"IETF RFC 1920","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 1931","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 1970","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1971","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 1972","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1972/RFC-1972.txt"},{"from":"IETF RFC 1983","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2000","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2019","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2064","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2132","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2153","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2153/RFC-2153.txt"},{"from":"IETF RFC 2200","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2225","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2338","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2373","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2386","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2400","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2427","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2461","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2462","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2464","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2467","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2518","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2522","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2522/RFC-2522.txt"},{"from":"IETF RFC 2625","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2720","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2834","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2998","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3002","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3077","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3193","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3252","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3315","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3318","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3374","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3460","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3513","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3576","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3748","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3768","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3775","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3780","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3794","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3927","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3931","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4005","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4058","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4072","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4118","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4122","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4259","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4291","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4326","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4334","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4389","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4564","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4663","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4675","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4691","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4762","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4763","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4789","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4795","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4814","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4840","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4861","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4907","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4918","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4947","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4962","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5080","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5102","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5121","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5154","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5176","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5216","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5227","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5247","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5494","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5556","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5570","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5798","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5836","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5998","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6021","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6158","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6222","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6320","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6325","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6328","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6459","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6632","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6677","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6741","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6763","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6822","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6959","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6991","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7043","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7136","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7155","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7176","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7180","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7228","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7624","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7637","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7676","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7721","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7780","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7844","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7961","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8064","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8086","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8415","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8926","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8947","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8981","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 900","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 948","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-948/RFC-948.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9562","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 960","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 985","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-985/RFC-985.txt"},{"from":"IETF RFC 990","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IEEE IEEE 802","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3033","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3318","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3794","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802-","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802-1990","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2685","to":"IEEE IEEE 802-1990","kind":"references","source":"IETF/RFC-2685/RFC-2685.txt"},{"from":"IETF RFC 3033","to":"IEEE IEEE 802-1990","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 4171","to":"IEEE IEEE 802-1990","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 3831","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 4338","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 6994","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7136","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7174","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7421","to":"IEEE IEEE 802-2001","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 802-2014","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8947","to":"IEEE IEEE 802-2014","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IEEE IEEE 802-2014","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802-2014","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9711","to":"IEEE IEEE 802-2014","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 7780","to":"IEEE IEEE 802-2014.","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 0970","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-0970/RFC-0970.txt"},{"from":"IETF RFC 1132","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1132/RFC-1132.txt"},{"from":"IETF RFC 1206","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1325","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1707","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1962","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1962/RFC-1962.txt"},{"from":"IETF RFC 1968","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 2723","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-2723/RFC-2723.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 3460","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3579","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3621","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3748","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 4663","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4962","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5416","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 6320","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 7844","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 970","to":"IEEE IEEE 802.","kind":"references","source":"IETF/RFC-970/RFC-970.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1095","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1231","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1286","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1356","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1368","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1374","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1443","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1483","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1490","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1493","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1513","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1516","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1717","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1748","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 1903","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1903/RFC-1903.txt"},{"from":"IETF RFC 1990","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 2019","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2067","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2108","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2285","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2285/RFC-2285.txt"},{"from":"IETF RFC 2338","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2427","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2467","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2579","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2579/RFC-2579.txt"},{"from":"IETF RFC 2613","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2674","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2764","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2834","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2895","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 3069","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3069/RFC-3069.txt"},{"from":"IETF RFC 3176","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3270","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3289","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3318","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3355","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3460","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3488","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3512","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3577","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3579","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3670","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3748","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3768","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3770","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3780","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4005","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4017","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4026","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4026/RFC-4026.txt"},{"from":"IETF RFC 4058","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4072","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4118","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4137","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4137/RFC-4137.txt"},{"from":"IETF RFC 4149","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4188","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4318","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4334","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4389","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4448","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4504","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4554","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4554/RFC-4554.txt"},{"from":"IETF RFC 4663","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4664","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4665","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4675","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4679","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4710","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4712","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4719","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4762","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4779","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4789","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4793","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4835","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4849","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 4851","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4852","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4903","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4942","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4962","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 4968","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5080","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5087","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5102","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5110","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5154","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5180","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5209","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5247","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5296","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5416","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5418","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5433","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5501","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5556","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5607","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5687","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5692","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5757","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5777","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5836","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5851","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 5887","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5997","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6104","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6136","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6158","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6221","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6221/RFC-6221.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6320","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6325","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6328","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6329","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6391","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6439","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6632","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6677","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6748","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6820","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6905","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 6959","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6988","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7030","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7067","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7155","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7170","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7172","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7174","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7180","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7226","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7273","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7276","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7319","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7319/RFC-7319.txt"},{"from":"IETF RFC 7322","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7348","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7356","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7364","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7365","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7368","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7384","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7390","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7406","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7424","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7432","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7455","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7461","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7593","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7637","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7780","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7844","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8014","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8033","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8034","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8034/RFC-8034.txt"},{"from":"IETF RFC 8415","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8926","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8947","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 9190","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9608","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9711","to":"IEEE IEEE 802.1","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 7180","to":"IEEE IEEE 802.1-2001","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.1.","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802.1.","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802.1.","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802.1.","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 7455","to":"IEEE IEEE 802.1.","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 2828","to":"IEEE IEEE 802.10","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4665","to":"IEEE IEEE 802.10","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.10","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4665","to":"IEEE IEEE 802.10-1992","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4665","to":"IEEE IEEE 802.10-1998","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 2865","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 3002","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3135","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3366","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3374","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3455","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3561","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3561/RFC-3561.txt"},{"from":"IETF RFC 3579","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3684","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3748","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3819","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3927","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3990","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-3990/RFC-3990.txt"},{"from":"IETF RFC 4005","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4017","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4072","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4086","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4093","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4118","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4186","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4282","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4305","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4309","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4334","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4564","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4651","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4675","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4732","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4746","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4763","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4779","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4789","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4795","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4814","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4831","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4835","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4840","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4862","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4881","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4907","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4919","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4962","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5006","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5169","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5181","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5184","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5193","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5213","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5216","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5218","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5227","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5247","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5265","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5296","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5320","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5415","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5418","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5422","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5433","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5481","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5548","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 5558","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5690","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5757","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5833","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5836","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5998","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6077","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6158","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6225","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6443","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6574","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6632","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6636","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6677","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6757","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6770","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7155","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7170","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7217","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7278","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7291","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7357","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7406","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7452","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7488","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7542","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7593","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7696","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7839","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7925","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7928","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8520","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8947","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8981","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9190","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.11","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 4564","to":"IEEE IEEE 802.11-","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802.11-","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 5416","to":"IEEE IEEE 802.11-","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5418","to":"IEEE IEEE 802.11-","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 7696","to":"IEEE IEEE 802.11-1997","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802.11-1999","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4907","to":"IEEE IEEE 802.11-2003","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802.11-2003","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.11-2007","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5416","to":"IEEE IEEE 802.11-2007","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 6762","to":"IEEE IEEE 802.11-2007","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.11-2012","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7406","to":"IEEE IEEE 802.11-2012","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7593","to":"IEEE IEEE 802.11-2012","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.11-2012","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 4118","to":"IEEE IEEE 802.11-99","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 3580","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3748","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 4118","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4564","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4764","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 5080","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5418","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5834","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6443","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6632","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6757","to":"IEEE IEEE 802.11.","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 2000","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2020","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2200","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2400","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3176","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3796","to":"IEEE IEEE 802.12","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.12-1995.","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2020","to":"IEEE IEEE 802.12.","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 4830","to":"IEEE IEEE 802.15","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.15.1","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4067","to":"IEEE IEEE 802.15.1","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 5548","to":"IEEE IEEE 802.15.1","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.15.3","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4919","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 4944","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5548","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 5673","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-5673/RFC-5673.txt"},{"from":"IETF RFC 5826","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6282","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6434","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6568","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6574","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6606","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6775","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6997","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7102","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7228","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7252","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7346","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7346/RFC-7346.txt"},{"from":"IETF RFC 7388","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7390","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7397","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7400","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7421","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7452","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7547","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7548","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 7924","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7959","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 8064","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8428","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8613","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9562","to":"IEEE IEEE 802.15.4","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 6282","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6568","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6606","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6775","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7252","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7400","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7428","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 8064","to":"IEEE IEEE 802.15.4-","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 4919","to":"IEEE IEEE 802.15.4-2003","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 4944","to":"IEEE IEEE 802.15.4-2003","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4919","to":"IEEE IEEE 802.15.4-2003.","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.15.4-2006","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.15.4-2020","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 4944","to":"IEEE IEEE 802.15.4.","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 6775","to":"IEEE IEEE 802.15.4.","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7548","to":"IEEE IEEE 802.15.4.","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4840","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4962","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 4968","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5121","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5154","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5181","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5184","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5213","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5216","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5692","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5739","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5851","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6036","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6434","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6443","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6636","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6677","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7421","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IEEE IEEE 802.16","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 5181","to":"IEEE IEEE 802.16-","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 4968","to":"IEEE IEEE 802.16-2004","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5154","to":"IEEE IEEE 802.16-2004","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5181","to":"IEEE IEEE 802.16-2004","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5692","to":"IEEE IEEE 802.16-2009","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 7406","to":"IEEE IEEE 802.16-2009","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 4564","to":"IEEE IEEE 802.16.","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 5181","to":"IEEE IEEE 802.16.","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5692","to":"IEEE IEEE 802.16.","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5851","to":"IEEE IEEE 802.16.","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 7406","to":"IEEE IEEE 802.16.","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 1010","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1054","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1054/RFC-1054.txt"},{"from":"IETF RFC 1060","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1103","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1103/RFC-1103.txt"},{"from":"IETF RFC 1112","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1112/RFC-1112.txt"},{"from":"IETF RFC 1132","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1132/RFC-1132.txt"},{"from":"IETF RFC 1188","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1374","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1377","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1390","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1457","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1469","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1469/RFC-1469.txt"},{"from":"IETF RFC 1483","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1561","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1577","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1683","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1931","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 2067","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2225","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2470","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2625","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2665","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2834","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3289","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3355","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3460","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3635","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4044","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4326","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4840","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 935","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-935/RFC-935.txt"},{"from":"IETF RFC 948","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-948/RFC-948.txt"},{"from":"IETF RFC 988","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-988/RFC-988.txt"},{"from":"IETF RFC 990","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IEEE IEEE 802.2","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802.2-1985","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1294","to":"IEEE IEEE 802.2-1989","kind":"references","source":"IETF/RFC-1294/RFC-1294.txt"},{"from":"IETF RFC 1490","to":"IEEE IEEE 802.2-1989","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1392","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1457","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1983","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3819","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.2.","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4907","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5113","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5164","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5184","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5677","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5757","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5836","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5873","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 6418","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 8553","to":"IEEE IEEE 802.21","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5164","to":"IEEE IEEE 802.21.","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 6443","to":"IEEE IEEE 802.22","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 1000","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1009","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1009/RFC-1009.txt"},{"from":"IETF RFC 1010","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1028","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1028/RFC-1028.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1055","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1055/RFC-1055.txt"},{"from":"IETF RFC 1122","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1122/RFC-1122.txt"},{"from":"IETF RFC 1191","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1284","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1368","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1369","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1369/RFC-1369.txt"},{"from":"IETF RFC 1398","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1457","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1470","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1500","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1515","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1533","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1540","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1584","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1600","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1623","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1643","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1720","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1757","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1780","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1920","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2021","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2063","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2063/RFC-2063.txt"},{"from":"IETF RFC 2108","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2132","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2239","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2285","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2285/RFC-2285.txt"},{"from":"IETF RFC 2358","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2400","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2613","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2665","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2668","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2684","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2722","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2737","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2819","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2828","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2889","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 3176","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3273","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3385","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3621","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3780","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3819","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4065","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4093","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4133","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4181","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4326","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4448","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4502","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4665","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4719","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4789","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4840","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4947","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4957","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 5087","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5121","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5163","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5180","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5184","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5213","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5415","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5851","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 5982","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6391","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6933","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7087","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7176","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7180","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7224","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7276","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7364","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7780","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 943","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 948","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-948/RFC-948.txt"},{"from":"IETF RFC 960","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 985","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-985/RFC-985.txt"},{"from":"IETF RFC 990","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IEEE IEEE 802.3","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.3-","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3580","to":"IEEE IEEE 802.3-","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3927","to":"IEEE IEEE 802.3-","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 5415","to":"IEEE IEEE 802.3-","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 1020","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1020/RFC-1020.txt"},{"from":"IETF RFC 1166","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1398","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1623","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 2358","to":"IEEE IEEE 802.3-1985","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 1284","to":"IEEE IEEE 802.3-1985.","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1398","to":"IEEE IEEE 802.3-1985.","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1623","to":"IEEE IEEE 802.3-1985.","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IEEE IEEE 802.3-1985.","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IEEE IEEE 802.3-1985.","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 5227","to":"IEEE IEEE 802.3-1996","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 3636","to":"IEEE IEEE 802.3-2002","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 4719","to":"IEEE IEEE 802.3-2005","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 5121","to":"IEEE IEEE 802.3-2005","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5342","to":"IEEE IEEE 802.3-2005","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 6291","to":"IEEE IEEE 802.3-2008","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6762","to":"IEEE IEEE 802.3-2008","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6775","to":"IEEE IEEE 802.3-2008","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7042","to":"IEEE IEEE 802.3-2012","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7174","to":"IEEE IEEE 802.3-2012","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 9542","to":"IEEE IEEE 802.3-2012","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 8519","to":"IEEE IEEE 802.3-2015.","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 1177","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1206","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1325","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1457","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 2108","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2239","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2625","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2665","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2668","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3385","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 3635","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 4949","to":"IEEE IEEE 802.3.","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1028","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1028/RFC-1028.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1191","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1230","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1239","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1250","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1250/RFC-1250.txt"},{"from":"IETF RFC 1280","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1360","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1500","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1540","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1600","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1716","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1720","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1780","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1812","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1920","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2200","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2400","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802.4","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 1028","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1028/RFC-1028.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1147","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1177","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1191","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1206","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1229","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1231","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1239","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1248","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1250","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1250/RFC-1250.txt"},{"from":"IETF RFC 1252","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1280","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1325","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1340","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1360","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1392","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1470","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1474","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1500","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1525","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1532","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1540","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1542","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1594","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1600","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1638","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1700","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1716","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1720","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1748","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 1780","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1812","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1920","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 1970","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1983","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2000","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2020","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2200","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2400","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2427","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2461","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2470","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2674","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2814","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2878","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3176","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3518","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3790","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3796","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4750","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4861","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 6272","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7180","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7780","to":"IEEE IEEE 802.5","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 2475","to":"IEEE IEEE 802.5-","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 1042","to":"IEEE IEEE 802.5-1985","kind":"references","source":"IETF/RFC-1042/RFC-1042.txt"},{"from":"IETF RFC 1220","to":"IEEE IEEE 802.5-1988","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 2816","to":"IEEE IEEE 802.5-1995","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3927","to":"IEEE IEEE 802.5-1998","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 5227","to":"IEEE IEEE 802.5-1998","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 2674","to":"IEEE IEEE 802.5.","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 4363","to":"IEEE IEEE 802.5.","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 1077","to":"IEEE IEEE 802.6","kind":"references","source":"IETF/RFC-1077/RFC-1077.txt"},{"from":"IETF RFC 1209","to":"IEEE IEEE 802.6","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 4719","to":"IEEE IEEE 8021","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 1120","to":"IEEE IEEE 87","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1160","to":"IEEE IEEE 87","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 6294","to":"IEEE IEEE 90","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 7765","to":"IEEE IEEE 9945-2009","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 0001","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 0003","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 0003","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 0010","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 0010","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 4627","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-4627/RFC-4627.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 0020","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 0021","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0033","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0037","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0038","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0048","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0061","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0076","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0097","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0137","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0139","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0318","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0333","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0542","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0698","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 0713","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 0713","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 0713","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 0733","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0739","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0742","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0758","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 0768","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 0791","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 0792","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5513","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5513/RFC-5513.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7872","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7872/RFC-7872.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 0793","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0813","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 0813","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0814","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 0815","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0816","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 0816","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 0816","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0817","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 0819","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 0819","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 0819","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0820","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 0821","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 2400","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 0822","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 0826","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 0850","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 0854","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 0868","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0872","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0879","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 0879","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 0879","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 0879","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 0881","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 0882","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 0882","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 0882","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 0882","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 0883","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 0889","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 0894","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 0894","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 0894","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 0896","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0900","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 0903","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 0903","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 0919","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 0922","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 0922","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 0925","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 0925","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 0927","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 0950","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 0951","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 0951","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 0951","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 0952","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0954","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 0959","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 0964","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 0970","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 0970","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 0970","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 0970","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 0974","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 0974","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 0977","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 0989","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1000","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1000","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1002","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-1002/RFC-1002.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1001","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1002","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1003","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1004","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1004","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 1005","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1005","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1005","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1085","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1240","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1275","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1275/RFC-1275.txt"},{"from":"IETF RFC 1277","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1277/RFC-1277.txt"},{"from":"IETF RFC 1278","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1278/RFC-1278.txt"},{"from":"IETF RFC 1287","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1287/RFC-1287.txt"},{"from":"IETF RFC 1292","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1465","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1673","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1673/RFC-1673.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1698","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1801","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 1859","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1920","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2200","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2400","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1006","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1195","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1254","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1254/RFC-1254.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2453","to":"IETF RFC 1009","kind":"references","source":"IETF/RFC-2453/RFC-2453.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1081","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1081/RFC-1081.txt"},{"from":"IETF RFC 1091","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1091/RFC-1091.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1131","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1131/RFC-1131.pdf"},{"from":"IETF RFC 1134","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1010","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 1011","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 1011","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 1011","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 1057","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1057/RFC-1057.txt"},{"from":"IETF RFC 1094","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1094/RFC-1094.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1790","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1790/RFC-1790.txt"},{"from":"IETF RFC 1813","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1813/RFC-1813.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 4506","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-4506/RFC-4506.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 1014","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1016","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1016","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 1016","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1016","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1018","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 114","to":"IETF RFC 102","kind":"references","source":"IETF/RFC-114/RFC-114.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1020","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1021","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1021","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1024","to":"IETF RFC 1023","kind":"references","source":"IETF/RFC-1024/RFC-1024.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 1024","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1024","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1026","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1546","to":"IETF RFC 1027","kind":"references","source":"IETF/RFC-1546/RFC-1546.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 1027","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 1067","to":"IETF RFC 1028","kind":"references","source":"IETF/RFC-1067/RFC-1067.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1028","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1028","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1028","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1028","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 114","to":"IETF RFC 103","kind":"references","source":"IETF/RFC-114/RFC-114.txt"},{"from":"IETF RFC 1986","to":"IETF RFC 1030","kind":"references","source":"IETF/RFC-1986/RFC-1986.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1030","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1031","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1464","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-1464/RFC-1464.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1032","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1664","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 1033","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1107","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1107/RFC-1107.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1178","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1178/RFC-1178.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1274","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1274/RFC-1274.txt"},{"from":"IETF RFC 1279","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1279/RFC-1279.txt"},{"from":"IETF RFC 1287","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1287/RFC-1287.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1436","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1436/RFC-1436.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1464","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1464/RFC-1464.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1486","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1486/RFC-1486.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1535","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1535/RFC-1535.txt"},{"from":"IETF RFC 1536","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1536/RFC-1536.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1630","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1630/RFC-1630.txt"},{"from":"IETF RFC 1637","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1664","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1706","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 1712","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1712/RFC-1712.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1788","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1788/RFC-1788.txt"},{"from":"IETF RFC 1798","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1798/RFC-1798.txt"},{"from":"IETF RFC 1876","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1876/RFC-1876.txt"},{"from":"IETF RFC 1877","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1877/RFC-1877.txt"},{"from":"IETF RFC 1886","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1886/RFC-1886.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 1982","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1982/RFC-1982.txt"},{"from":"IETF RFC 1995","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-1995/RFC-1995.txt"},{"from":"IETF RFC 2016","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2016/RFC-2016.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2137","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2137/RFC-2137.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2181","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2181/RFC-2181.txt"},{"from":"IETF RFC 2182","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2182/RFC-2182.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2247","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2247/RFC-2247.txt"},{"from":"IETF RFC 2280","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2280/RFC-2280.txt"},{"from":"IETF RFC 2308","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2308/RFC-2308.txt"},{"from":"IETF RFC 2317","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2317/RFC-2317.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2536","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2536/RFC-2536.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2539","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2539/RFC-2539.txt"},{"from":"IETF RFC 2540","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2540/RFC-2540.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2606","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2606/RFC-2606.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2826","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2826/RFC-2826.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3225","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3225/RFC-3225.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3364","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3364/RFC-3364.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3491","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3492","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3492/RFC-3492.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4074","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4074/RFC-4074.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4892","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4892/RFC-4892.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 1034","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1274","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1274/RFC-1274.txt"},{"from":"IETF RFC 1279","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1279/RFC-1279.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1464","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1464/RFC-1464.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1486","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1486/RFC-1486.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1535","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1535/RFC-1535.txt"},{"from":"IETF RFC 1536","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1536/RFC-1536.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1609","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1609/RFC-1609.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1637","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1664","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1706","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 1712","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1712/RFC-1712.txt"},{"from":"IETF RFC 1788","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1788/RFC-1788.txt"},{"from":"IETF RFC 1794","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1794/RFC-1794.txt"},{"from":"IETF RFC 1798","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1798/RFC-1798.txt"},{"from":"IETF RFC 1876","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1876/RFC-1876.txt"},{"from":"IETF RFC 1877","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1877/RFC-1877.txt"},{"from":"IETF RFC 1886","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1886/RFC-1886.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1982","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1982/RFC-1982.txt"},{"from":"IETF RFC 1995","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1995/RFC-1995.txt"},{"from":"IETF RFC 1996","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-1996/RFC-1996.txt"},{"from":"IETF RFC 2016","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2016/RFC-2016.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2137","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2137/RFC-2137.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2181","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2181/RFC-2181.txt"},{"from":"IETF RFC 2182","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2182/RFC-2182.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2240","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2240/RFC-2240.txt"},{"from":"IETF RFC 2308","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2308/RFC-2308.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2536","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2536/RFC-2536.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2539","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2539/RFC-2539.txt"},{"from":"IETF RFC 2540","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2540/RFC-2540.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2606","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2606/RFC-2606.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2671","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2671/RFC-2671.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2673","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2673/RFC-2673.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2826","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2826/RFC-2826.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3225","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3225/RFC-3225.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 3375","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3375/RFC-3375.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3425","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3425/RFC-3425.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3491","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4892","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4892/RFC-4892.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4955","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4955/RFC-4955.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7706","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7706/RFC-7706.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7830","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7830/RFC-7830.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1035","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1468","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1554","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1630","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1630/RFC-1630.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1842","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2980","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-2980/RFC-2980.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 1036","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1037","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 3092","to":"IETF RFC 1037","kind":"references","source":"IETF/RFC-3092/RFC-3092.txt"},{"from":"IETF RFC 1108","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-1108/RFC-1108.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1038","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 1114","to":"IETF RFC 1040","kind":"references","source":"IETF/RFC-1114/RFC-1114.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 1041","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 1041","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1041","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 1041","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1041","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1103","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1103/RFC-1103.txt"},{"from":"IETF RFC 1132","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1132/RFC-1132.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1483","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1042","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1043","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1043","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1043","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1044","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1044","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 1044","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 1072","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1072/RFC-1072.txt"},{"from":"IETF RFC 1077","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1077/RFC-1077.txt"},{"from":"IETF RFC 1105","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1105/RFC-1105.txt"},{"from":"IETF RFC 1106","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1106/RFC-1106.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1263","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1263/RFC-1263.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1045","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1046","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1046","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1047","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1047","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1047","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 1047","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1047","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1048","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1049","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 1057","to":"IETF RFC 1050","kind":"references","source":"IETF/RFC-1057/RFC-1057.txt"},{"from":"IETF RFC 1500","to":"IETF RFC 1050","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1051","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 1051","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1051","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1065","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1065/RFC-1065.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1067","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1067/RFC-1067.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1155","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1155/RFC-1155.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 1052","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1053","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1053","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1075","to":"IETF RFC 1054","kind":"references","source":"IETF/RFC-1075/RFC-1075.txt"},{"from":"IETF RFC 1077","to":"IETF RFC 1054","kind":"references","source":"IETF/RFC-1077/RFC-1077.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1055","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1064","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-1064/RFC-1064.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1733","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-1733/RFC-1733.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1056","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 1094","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-1094/RFC-1094.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1790","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-1790/RFC-1790.txt"},{"from":"IETF RFC 1813","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-1813/RFC-1813.txt"},{"from":"IETF RFC 1981","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-1981/RFC-1981.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1057","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1075","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1075/RFC-1075.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1387","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1387/RFC-1387.txt"},{"from":"IETF RFC 1388","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1388/RFC-1388.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1582","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1582/RFC-1582.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1923","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1923/RFC-1923.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2174","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-2174/RFC-2174.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2453","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-2453/RFC-2453.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1058","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1059","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 1171","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1172","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1172/RFC-1172.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1224","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1224/RFC-1224.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 1246","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1246/RFC-1246.txt"},{"from":"IETF RFC 1247","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1329","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1331","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1331/RFC-1331.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1060","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1063","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1064","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1067","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1067/RFC-1067.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1155","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1155/RFC-1155.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 1065","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 1065","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1065/RFC-1065.txt"},{"from":"IETF RFC 1067","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1067/RFC-1067.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1066","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1065","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1065/RFC-1065.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1067","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1068","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 1069","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 0137","to":"IETF RFC 107","kind":"references","source":"IETF/RFC-0137/RFC-0137.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 107","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 137","to":"IETF RFC 107","kind":"references","source":"IETF/RFC-137/RFC-137.txt"},{"from":"IETF RFC 158","to":"IETF RFC 107","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1070","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1070","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1070","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1141","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-1141/RFC-1141.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1624","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-1624/RFC-1624.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1071","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1106","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1106/RFC-1106.txt"},{"from":"IETF RFC 1185","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1185/RFC-1185.txt"},{"from":"IETF RFC 1263","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1263/RFC-1263.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1693","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1693/RFC-1693.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1072","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 1073","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1073","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1073","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1073","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 1075","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 1106","to":"IETF RFC 1077","kind":"references","source":"IETF/RFC-1106/RFC-1106.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 1077","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1078","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 1078","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1078","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1096","to":"IETF RFC 1079","kind":"references","source":"IETF/RFC-1096/RFC-1096.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 1079","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1079","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1079","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1079","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 1080","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1080","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1372","to":"IETF RFC 1080","kind":"references","source":"IETF/RFC-1372/RFC-1372.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 1081","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 1081","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 1100","to":"IETF RFC 1083","kind":"references","source":"IETF/RFC-1100/RFC-1100.txt"},{"from":"IETF RFC 1060","to":"IETF RFC 1084","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 1084","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 1084","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1084","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1085","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1085","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1085","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1086","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1135","to":"IETF RFC 1087","kind":"references","source":"IETF/RFC-1135/RFC-1135.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1087","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1359","to":"IETF RFC 1087","kind":"references","source":"IETF/RFC-1359/RFC-1359.txt"},{"from":"IETF RFC 1855","to":"IETF RFC 1087","kind":"references","source":"IETF/RFC-1855/RFC-1855.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1087","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1088","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1088","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1089","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1089","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1419","to":"IETF RFC 1089","kind":"references","source":"IETF/RFC-1419/RFC-1419.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1089","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 1089","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 0137","to":"IETF RFC 109","kind":"references","source":"IETF/RFC-0137/RFC-0137.txt"},{"from":"IETF RFC 137","to":"IETF RFC 109","kind":"references","source":"IETF/RFC-137/RFC-137.txt"},{"from":"IETF RFC 158","to":"IETF RFC 109","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1090","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1408","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1408/RFC-1408.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1646","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1646/RFC-1646.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1091","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1093","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1093/RFC-1093.txt"},{"from":"IETF RFC 1104","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1104/RFC-1104.txt"},{"from":"IETF RFC 1105","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1105/RFC-1105.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1092","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 1104","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1104/RFC-1104.txt"},{"from":"IETF RFC 1105","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1105/RFC-1105.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1093","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1813","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-1813/RFC-1813.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 1094","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1095","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1408","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-1408/RFC-1408.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1096","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1109","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1109/RFC-1109.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1228","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1228/RFC-1228.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1352","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1352/RFC-1352.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1098","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 0137","to":"IETF RFC 110","kind":"references","source":"IETF/RFC-0137/RFC-0137.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 110","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 137","to":"IETF RFC 110","kind":"references","source":"IETF/RFC-137/RFC-137.txt"},{"from":"IETF RFC 158","to":"IETF RFC 110","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1100","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1279","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1279/RFC-1279.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1415","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1464","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1464/RFC-1464.txt"},{"from":"IETF RFC 1876","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1876/RFC-1876.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1101","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 1104","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-1104/RFC-1104.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 1164","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-1164/RFC-1164.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1102","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 1103","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 1164","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1164/RFC-1164.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1268","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1268/RFC-1268.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1655","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1655/RFC-1655.txt"},{"from":"IETF RFC 1772","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-1772/RFC-1772.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1104","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1237","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1265","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1265/RFC-1265.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1105","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 1110","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-1110/RFC-1110.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1106","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1107","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 1107","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 1457","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1108","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1155","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1155/RFC-1155.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 1109","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 111","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1185","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-1185/RFC-1185.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1110","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1280","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1360","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1500","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1540","to":"IETF RFC 1111","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1131","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1131/RFC-1131.pdf"},{"from":"IETF RFC 1188","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1234","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1234/RFC-1234.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1247","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1287","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1287/RFC-1287.txt"},{"from":"IETF RFC 1301","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1301/RFC-1301.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1469","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1469/RFC-1469.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1693","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1693/RFC-1693.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1768","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1769","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1769/RFC-1769.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1884","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1971","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2117","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2117/RFC-2117.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2236","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2236/RFC-2236.txt"},{"from":"IETF RFC 2250","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2362","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2362/RFC-2362.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2658","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2658/RFC-2658.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2771","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2771/RFC-2771.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3208","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3208/RFC-3208.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 1112","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1124","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1124/RFC-1124.pdf"},{"from":"IETF RFC 1154","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1319","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1319/RFC-1319.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 1113","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1319","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1319/RFC-1319.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 1114","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1319","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1319/RFC-1319.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1115","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1060","to":"IETF RFC 1116","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1143","to":"IETF RFC 1116","kind":"references","source":"IETF/RFC-1143/RFC-1143.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 1116","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1116","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1118","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1165","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1165/RFC-1165.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1600","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1720","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1780","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1119","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1120","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1108","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1108/RFC-1108.txt"},{"from":"IETF RFC 1145","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1145/RFC-1145.txt"},{"from":"IETF RFC 1146","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1146/RFC-1146.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1180","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1180/RFC-1180.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1254","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1254/RFC-1254.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1329","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1370","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1370/RFC-1370.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1546","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1546/RFC-1546.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1770","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1770/RFC-1770.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 1937","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1937/RFC-1937.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2001","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2001/RFC-2001.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2075","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2075/RFC-2075.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2309","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2309/RFC-2309.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2555","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2555/RFC-2555.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2678","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2678/RFC-2678.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2988","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-2988/RFC-2988.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3081","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3081/RFC-3081.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4943","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4943/RFC-4943.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6419","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6419/RFC-6419.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 1122","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1143","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1143/RFC-1143.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1153","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1153/RFC-1153.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1350","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1350/RFC-1350.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1425","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1425/RFC-1425.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1579","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1579/RFC-1579.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1639","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1639/RFC-1639.txt"},{"from":"IETF RFC 1648","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1648/RFC-1648.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1651","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1651/RFC-1651.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1767","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1767/RFC-1767.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1846","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1846/RFC-1846.txt"},{"from":"IETF RFC 1869","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1869/RFC-1869.txt"},{"from":"IETF RFC 1878","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1878/RFC-1878.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2069","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2069/RFC-2069.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2181","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2181/RFC-2181.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2228","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2228/RFC-2228.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2542","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2542/RFC-2542.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2635","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2635/RFC-2635.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1123","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1124","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1125","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1125","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1125","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1126","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1126","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1126","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1165","to":"IETF RFC 1128","kind":"references","source":"IETF/RFC-1165/RFC-1165.txt"},{"from":"IETF RFC 1257","to":"IETF RFC 1128","kind":"references","source":"IETF/RFC-1257/RFC-1257.txt"},{"from":"IETF RFC 1165","to":"IETF RFC 1129","kind":"references","source":"IETF/RFC-1165/RFC-1165.txt"},{"from":"IETF RFC 140","to":"IETF RFC 113","kind":"references","source":"IETF/RFC-140/RFC-140.txt"},{"from":"IETF RFC 1060","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1195","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1245","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1245/RFC-1245.txt"},{"from":"IETF RFC 1246","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1246/RFC-1246.txt"},{"from":"IETF RFC 1247","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1131","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1132","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1132","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1171","to":"IETF RFC 1134","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1134","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1147","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-1147/RFC-1147.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1135","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 1136","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 1136","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 1137","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 1137","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 1137","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1137","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 1138","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1138","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1138","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1139","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1575","to":"IETF RFC 1139","kind":"references","source":"IETF/RFC-1575/RFC-1575.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 114","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 114","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 959","to":"IETF RFC 114","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1140","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1624","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-1624/RFC-1624.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 1141","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 2966","to":"IETF RFC 1142","kind":"references","source":"IETF/RFC-2966/RFC-2966.txt"},{"from":"IETF RFC 3358","to":"IETF RFC 1142","kind":"references","source":"IETF/RFC-3358/RFC-3358.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 1142","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 1142","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 1142","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1143","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1553","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-1553/RFC-1553.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3096","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3096/RFC-3096.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1144","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1146","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-1146/RFC-1146.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1145","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3385","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1146","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 1147","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1147","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1147","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1147","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 1148","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 1148","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1148","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1148","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1543","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-1543/RFC-1543.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 2322","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-2322/RFC-2322.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 7669","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 1149","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 6360","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-6360/RFC-6360.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 1150","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1151","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1151","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1151","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1151","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1153","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1154","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1154","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1154","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1154","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 1154","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1161","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1161/RFC-1161.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1224","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1224/RFC-1224.txt"},{"from":"IETF RFC 1227","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1227/RFC-1227.txt"},{"from":"IETF RFC 1228","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1228/RFC-1228.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1285","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1298","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1298/RFC-1298.txt"},{"from":"IETF RFC 1303","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1303/RFC-1303.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1333","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1333/RFC-1333.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1512","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1513","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1514","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1514/RFC-1514.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 1155","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 1155","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1155/RFC-1155.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1161","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1161/RFC-1161.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1227","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1227/RFC-1227.txt"},{"from":"IETF RFC 1228","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1228/RFC-1228.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1280","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1285","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1156","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1155","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1155/RFC-1155.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1161","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1161/RFC-1161.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1187","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1187/RFC-1187.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1224","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1224/RFC-1224.txt"},{"from":"IETF RFC 1227","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1227/RFC-1227.txt"},{"from":"IETF RFC 1228","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1228/RFC-1228.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1285","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1298","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1298/RFC-1298.txt"},{"from":"IETF RFC 1303","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1303/RFC-1303.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1352","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1352/RFC-1352.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1419","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1419/RFC-1419.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1450","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1450/RFC-1450.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1512","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1513","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1514","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1514/RFC-1514.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1906","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1906/RFC-1906.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2128","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 1157","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 1162","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1158","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1312","to":"IETF RFC 1159","kind":"references","source":"IETF/RFC-1312/RFC-1312.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 116","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1160","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1161","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1161","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1162","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1162","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1164","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1164/RFC-1164.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1265","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1265/RFC-1265.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1397","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1397/RFC-1397.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1163","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1268","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1268/RFC-1268.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1655","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1655/RFC-1655.txt"},{"from":"IETF RFC 1772","to":"IETF RFC 1164","kind":"references","source":"IETF/RFC-1772/RFC-1772.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1165","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 1166","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1169","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1170","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1170","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1170","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 1170","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1172","to":"IETF RFC 1171","kind":"references","source":"IETF/RFC-1172/RFC-1172.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1171","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1220","to":"IETF RFC 1171","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1171","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1172","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1220","to":"IETF RFC 1172","kind":"references","source":"IETF/RFC-1220/RFC-1220.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 1172","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1333","to":"IETF RFC 1172","kind":"references","source":"IETF/RFC-1333/RFC-1333.txt"},{"from":"IETF RFC 1334","to":"IETF RFC 1172","kind":"references","source":"IETF/RFC-1334/RFC-1334.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1173","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1366","to":"IETF RFC 1174","kind":"references","source":"IETF/RFC-1366/RFC-1366.txt"},{"from":"IETF RFC 1466","to":"IETF RFC 1174","kind":"references","source":"IETF/RFC-1466/RFC-1466.txt"},{"from":"IETF RFC 1518","to":"IETF RFC 1174","kind":"references","source":"IETF/RFC-1518/RFC-1518.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 1174","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1174","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1463","to":"IETF RFC 1175","kind":"references","source":"IETF/RFC-1463/RFC-1463.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1732","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-1732/RFC-1732.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2062","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-2062/RFC-2062.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1176","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 1177","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1359","to":"IETF RFC 1178","kind":"references","source":"IETF/RFC-1359/RFC-1359.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1178","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 1179","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1180","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1180","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1180","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1180","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1180","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1356","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 1183","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 1372","to":"IETF RFC 1184","kind":"references","source":"IETF/RFC-1372/RFC-1372.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1184","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1184","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1263","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-1263/RFC-1263.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1185","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 1320","to":"IETF RFC 1186","kind":"references","source":"IETF/RFC-1320/RFC-1320.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1187","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1187","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1329","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1469","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-1469/RFC-1469.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1188","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1224","to":"IETF RFC 1189","kind":"references","source":"IETF/RFC-1224/RFC-1224.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1189","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1633","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1633/RFC-1633.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 1190","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1435","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1435/RFC-1435.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 1981","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-1981/RFC-1981.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2004","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2004/RFC-2004.txt"},{"from":"IETF RFC 2019","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2067","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2343","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2343/RFC-2343.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2431","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2431/RFC-2431.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2979","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-2979/RFC-2979.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 1191","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 1257","to":"IETF RFC 1193","kind":"references","source":"IETF/RFC-1257/RFC-1257.txt"},{"from":"IETF RFC 1196","to":"IETF RFC 1194","kind":"references","source":"IETF/RFC-1196/RFC-1196.txt"},{"from":"IETF RFC 1200","to":"IETF RFC 1194","kind":"references","source":"IETF/RFC-1200/RFC-1200.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1930","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2966","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-2966/RFC-2966.txt"},{"from":"IETF RFC 3358","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3358/RFC-3358.txt"},{"from":"IETF RFC 3359","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3359/RFC-3359.txt"},{"from":"IETF RFC 3373","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3373/RFC-3373.txt"},{"from":"IETF RFC 3567","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3719","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3784","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 3786","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3847","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5130","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5302","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5303","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5308","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6165","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 1195","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 1288","to":"IETF RFC 1196","kind":"references","source":"IETF/RFC-1288/RFC-1288.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1198","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1198","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 1198","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 1200","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 1201","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1201","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1249","to":"IETF RFC 1202","kind":"references","source":"IETF/RFC-1249/RFC-1249.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1202","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1487","to":"IETF RFC 1202","kind":"references","source":"IETF/RFC-1487/RFC-1487.txt"},{"from":"IETF RFC 1777","to":"IETF RFC 1202","kind":"references","source":"IETF/RFC-1777/RFC-1777.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 1203","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1203","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1204","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1204","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 1206","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1206","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1206","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1207","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1207","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1207","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1207","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 1208","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1483","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1735","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-1735/RFC-1735.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1209","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 216","to":"IETF RFC 121","kind":"references","source":"IETF/RFC-216/RFC-216.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1211","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1211","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 1211","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1227","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1227/RFC-1227.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1255","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1255/RFC-1255.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1285","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1303","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1303/RFC-1303.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1512","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1513","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1514","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1514/RFC-1514.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1212","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1212","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1212/RFC-1212.txt"},{"from":"IETF RFC 1215","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1215/RFC-1215.txt"},{"from":"IETF RFC 1224","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1224/RFC-1224.txt"},{"from":"IETF RFC 1229","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1229/RFC-1229.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1232","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1232/RFC-1232.txt"},{"from":"IETF RFC 1233","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1233/RFC-1233.txt"},{"from":"IETF RFC 1238","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1243","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1243/RFC-1243.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1280","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1285","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1285/RFC-1285.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1303","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1303/RFC-1303.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1333","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1333/RFC-1333.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1450","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1450/RFC-1450.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1512","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1513","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1514","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1514/RFC-1514.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1566","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1566/RFC-1566.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1586","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1586/RFC-1586.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1665","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1665/RFC-1665.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1696","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1696/RFC-1696.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1759","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2012","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2012/RFC-2012.txt"},{"from":"IETF RFC 2013","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2013/RFC-2013.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2039","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2039/RFC-2039.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2128","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2206","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2206/RFC-2206.txt"},{"from":"IETF RFC 2213","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2213/RFC-2213.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2325","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2325/RFC-2325.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 1213","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1271","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1271/RFC-1271.txt"},{"from":"IETF RFC 1286","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1286/RFC-1286.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1315","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1315/RFC-1315.txt"},{"from":"IETF RFC 1316","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1316/RFC-1316.txt"},{"from":"IETF RFC 1317","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1317/RFC-1317.txt"},{"from":"IETF RFC 1318","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1318/RFC-1318.txt"},{"from":"IETF RFC 1368","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2579","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2579/RFC-2579.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1215","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1255","to":"IETF RFC 1218","kind":"references","source":"IETF/RFC-1255/RFC-1255.txt"},{"from":"IETF RFC 3531","to":"IETF RFC 1219","kind":"references","source":"IETF/RFC-3531/RFC-3531.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 1220","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1222","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1224","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1224","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1224","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1224","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1224","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 1339","to":"IETF RFC 1225","kind":"references","source":"IETF/RFC-1339/RFC-1339.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1225","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1460","to":"IETF RFC 1225","kind":"references","source":"IETF/RFC-1460/RFC-1460.txt"},{"from":"IETF RFC 1733","to":"IETF RFC 1225","kind":"references","source":"IETF/RFC-1733/RFC-1733.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1226","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1226","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1226","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1226","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1303","to":"IETF RFC 1227","kind":"references","source":"IETF/RFC-1303/RFC-1303.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 1227","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1227","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1227","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1227","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1228","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1228","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 1230","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1231","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1239","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1284","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 1229","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 123","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 165","to":"IETF RFC 123","kind":"references","source":"IETF/RFC-165/RFC-165.txt"},{"from":"IETF RFC 1239","to":"IETF RFC 1230","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1230","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1230","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1230","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1239","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1231","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 1239","to":"IETF RFC 1232","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1232","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1232","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1406","to":"IETF RFC 1232","kind":"references","source":"IETF/RFC-1406/RFC-1406.txt"},{"from":"IETF RFC 1239","to":"IETF RFC 1233","kind":"references","source":"IETF/RFC-1239/RFC-1239.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1233","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1233","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1407","to":"IETF RFC 1233","kind":"references","source":"IETF/RFC-1407/RFC-1407.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 1234","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1235","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1235","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1277","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1277/RFC-1277.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1518","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1518/RFC-1518.txt"},{"from":"IETF RFC 1526","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1768","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1237","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1238","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1238","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1304","to":"IETF RFC 1239","kind":"references","source":"IETF/RFC-1304/RFC-1304.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1239","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1239","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1239","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1240","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2556","to":"IETF RFC 1240","kind":"references","source":"IETF/RFC-2556/RFC-2556.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1240","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 1241","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 1944","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-1944/RFC-1944.txt"},{"from":"IETF RFC 2285","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-2285/RFC-2285.txt"},{"from":"IETF RFC 2432","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-2432/RFC-2432.txt"},{"from":"IETF RFC 2544","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-2544/RFC-2544.txt"},{"from":"IETF RFC 2647","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-2647/RFC-2647.txt"},{"from":"IETF RFC 2889","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 1242","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1419","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1419/RFC-1419.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1906","to":"IETF RFC 1243","kind":"references","source":"IETF/RFC-1906/RFC-1906.txt"},{"from":"IETF RFC 1281","to":"IETF RFC 1244","kind":"references","source":"IETF/RFC-1281/RFC-1281.txt"},{"from":"IETF RFC 1359","to":"IETF RFC 1244","kind":"references","source":"IETF/RFC-1359/RFC-1359.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1244","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1765","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-1765/RFC-1765.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1245","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 1245","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1245/RFC-1245.txt"},{"from":"IETF RFC 1292","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1765","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-1765/RFC-1765.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1246","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 1245","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1245/RFC-1245.txt"},{"from":"IETF RFC 1246","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1246/RFC-1246.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1338","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1338/RFC-1338.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1370","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1370/RFC-1370.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1519","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1519/RFC-1519.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 3137","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-3137/RFC-3137.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 1247","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 1246","to":"IETF RFC 1248","kind":"references","source":"IETF/RFC-1246/RFC-1246.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 1248","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1248","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1249","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1487","to":"IETF RFC 1249","kind":"references","source":"IETF/RFC-1487/RFC-1487.txt"},{"from":"IETF RFC 1777","to":"IETF RFC 1249","kind":"references","source":"IETF/RFC-1777/RFC-1777.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1249","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1264","to":"IETF RFC 1250","kind":"references","source":"IETF/RFC-1264/RFC-1264.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 1250","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 1252","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1354","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1370","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1370/RFC-1370.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1586","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1586/RFC-1586.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1253","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1254","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1254","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1254","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1255","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1255","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 1255","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1370","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1370/RFC-1370.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1788","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1788/RFC-1788.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1900","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1900/RFC-1900.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2281","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2281/RFC-2281.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1256","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1257","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1282","to":"IETF RFC 1258","kind":"references","source":"IETF/RFC-1282/RFC-1282.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1258","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1693","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-1693/RFC-1693.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 1263","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1387","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1387/RFC-1387.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2357","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-2357/RFC-2357.txt"},{"from":"IETF RFC 4794","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-4794/RFC-4794.txt"},{"from":"IETF RFC 6982","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-6982/RFC-6982.txt"},{"from":"IETF RFC 7120","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-7120/RFC-7120.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 1264","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1265","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1265","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1266","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1266","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1265","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1265/RFC-1265.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1268","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1268/RFC-1268.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1338","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1338/RFC-1338.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1397","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1397/RFC-1397.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1478","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1786","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1786/RFC-1786.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 1267","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 1265","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1265/RFC-1265.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1269","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1269/RFC-1269.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1268","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 1266","to":"IETF RFC 1269","kind":"references","source":"IETF/RFC-1266/RFC-1266.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1269","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1269","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1269","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 1269","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 1298","to":"IETF RFC 1270","kind":"references","source":"IETF/RFC-1298/RFC-1298.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1270","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1270","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 1270","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1513","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1513/RFC-1513.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1271","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 1672","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-1672/RFC-1672.txt"},{"from":"IETF RFC 2063","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2063/RFC-2063.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 1272","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 1279","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1279/RFC-1279.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1384","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1384/RFC-1384.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1698","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 1804","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-1804/RFC-1804.txt"},{"from":"IETF RFC 2256","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3061","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-3061/RFC-3061.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 1274","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 1276","to":"IETF RFC 1275","kind":"references","source":"IETF/RFC-1276/RFC-1276.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1275","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1275","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1275","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1276","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1276","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 2120","to":"IETF RFC 1276","kind":"references","source":"IETF/RFC-2120/RFC-2120.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1276","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1276","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1276/RFC-1276.txt"},{"from":"IETF RFC 1278","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1278/RFC-1278.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1465","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 1801","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1277","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1465","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 1278","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 1274","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1274/RFC-1274.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1384","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1384/RFC-1384.txt"},{"from":"IETF RFC 1415","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 1279","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1280","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1280","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1281","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1280","to":"IETF RFC 1282","kind":"references","source":"IETF/RFC-1280/RFC-1280.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1282","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 1282","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 1283","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1283","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1289","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1289/RFC-1289.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1398","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1284","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1512","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-1512/RFC-1512.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1285","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1493","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-1493/RFC-1493.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 1286","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 1335","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1335/RFC-1335.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1560","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1560/RFC-1560.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 1287","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2458","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-2458/RFC-2458.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1288","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1559","to":"IETF RFC 1289","kind":"references","source":"IETF/RFC-1559/RFC-1559.txt"},{"from":"IETF RFC 1308","to":"IETF RFC 1292","kind":"references","source":"IETF/RFC-1308/RFC-1308.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1292","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1292","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 1292","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1586","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1586/RFC-1586.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 1293","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 1356","to":"IETF RFC 1294","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1362","to":"IETF RFC 1294","kind":"references","source":"IETF/RFC-1362/RFC-1362.txt"},{"from":"IETF RFC 1483","to":"IETF RFC 1294","kind":"references","source":"IETF/RFC-1483/RFC-1483.txt"},{"from":"IETF RFC 1586","to":"IETF RFC 1294","kind":"references","source":"IETF/RFC-1586/RFC-1586.txt"},{"from":"IETF RFC 1355","to":"IETF RFC 1295","kind":"references","source":"IETF/RFC-1355/RFC-1355.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1295","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 1295","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 1298","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1298","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1301","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 2357","to":"IETF RFC 1301","kind":"references","source":"IETF/RFC-2357/RFC-2357.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1301","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1303","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1303","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1303","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1303","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1303","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1304","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1304","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1304","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1304","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1600","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1720","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1769","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1769/RFC-1769.txt"},{"from":"IETF RFC 1780","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2330","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2330/RFC-2330.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2980","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-2980/RFC-2980.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4082","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4082/RFC-4082.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 1305","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 1307","to":"IETF RFC 1306","kind":"references","source":"IETF/RFC-1307/RFC-1307.txt"},{"from":"IETF RFC 1306","to":"IETF RFC 1307","kind":"references","source":"IETF/RFC-1306/RFC-1306.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1307","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1307","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 1309","to":"IETF RFC 1308","kind":"references","source":"IETF/RFC-1309/RFC-1309.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1308","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 1308","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1308","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 1308","to":"IETF RFC 1309","kind":"references","source":"IETF/RFC-1308/RFC-1308.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 1309","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1309","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1396","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1396/RFC-1396.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1602","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1602/RFC-1602.txt"},{"from":"IETF RFC 1627","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1627/RFC-1627.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 2026","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-2026/RFC-2026.txt"},{"from":"IETF RFC 2437","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-2437/RFC-2437.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 1310","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 1310","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1310/RFC-1310.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1602","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1602/RFC-1602.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 2026","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-2026/RFC-2026.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 1311","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1312","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1312","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1314","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1314","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1315","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1315","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1315","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1315","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1315","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1316","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 1316","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1316","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1317","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1317","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1317","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1317","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1317","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1318","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2313","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2313/RFC-2313.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2437","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2437/RFC-2437.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 1319","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 1320","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 1321","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1321/RFC-1321.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1510","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1510/RFC-1510.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1760","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1760/RFC-1760.txt"},{"from":"IETF RFC 1938","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1938/RFC-1938.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2313","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-2313/RFC-2313.txt"},{"from":"IETF RFC 2433","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-2433/RFC-2433.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3174","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-3174/RFC-3174.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 1320","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 1321","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 1320","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1320/RFC-1320.txt"},{"from":"IETF RFC 1334","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1334/RFC-1334.txt"},{"from":"IETF RFC 1352","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1352/RFC-1352.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1460","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1460/RFC-1460.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1510","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1510/RFC-1510.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1725","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1725/RFC-1725.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1810","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1810/RFC-1810.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1864","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1864/RFC-1864.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 1938","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1938/RFC-1938.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 1964","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1964/RFC-1964.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1994","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-1994/RFC-1994.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2040","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2040/RFC-2040.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2059","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2059/RFC-2059.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2069","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2069/RFC-2069.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2085","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2085/RFC-2085.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2104","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2104/RFC-2104.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2139","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2139/RFC-2139.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2202","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2202/RFC-2202.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2286","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2286/RFC-2286.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2313","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2313/RFC-2313.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2385","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2385/RFC-2385.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2437","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2437/RFC-2437.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2762","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2762/RFC-2762.txt"},{"from":"IETF RFC 2777","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2777/RFC-2777.txt"},{"from":"IETF RFC 2792","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2792/RFC-2792.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2803","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2803/RFC-2803.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 2945","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2945/RFC-2945.txt"},{"from":"IETF RFC 2961","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-2961/RFC-2961.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3174","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3174/RFC-3174.txt"},{"from":"IETF RFC 3188","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3188/RFC-3188.txt"},{"from":"IETF RFC 3208","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3208/RFC-3208.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3224","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3224/RFC-3224.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 3967","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-3967/RFC-3967.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4122","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 1321","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 1668","to":"IETF RFC 1322","kind":"references","source":"IETF/RFC-1668/RFC-1668.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1693","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-1693/RFC-1693.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2147","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2147/RFC-2147.txt"},{"from":"IETF RFC 2385","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2385/RFC-2385.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2883","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2988","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-2988/RFC-2988.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3649","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3649/RFC-3649.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1323","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1325","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1463","to":"IETF RFC 1325","kind":"references","source":"IETF/RFC-1463/RFC-1463.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1325","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1326","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1326","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1326","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1326","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 1328","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1328/RFC-1328.txt"},{"from":"IETF RFC 1405","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1405/RFC-1405.txt"},{"from":"IETF RFC 1465","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1494","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1495","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1496","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1496/RFC-1496.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1648","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1648/RFC-1648.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1664","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1720","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1766","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1766/RFC-1766.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 1780","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1836","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1920","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2200","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1327","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1496","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-1496/RFC-1496.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1328","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 1329","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1333","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1333/RFC-1333.txt"},{"from":"IETF RFC 1334","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1334/RFC-1334.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1362","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1362/RFC-1362.txt"},{"from":"IETF RFC 1377","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1548","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-1548/RFC-1548.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 1331","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1877","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-1877/RFC-1877.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1332","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1333","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1471","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1471/RFC-1471.txt"},{"from":"IETF RFC 1472","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1472/RFC-1472.txt"},{"from":"IETF RFC 1473","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1473/RFC-1473.txt"},{"from":"IETF RFC 1474","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1474/RFC-1474.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1717","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 1334","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 1366","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1366/RFC-1366.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1466","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1466/RFC-1466.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1335","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1337","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1366","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1366/RFC-1366.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1383","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1383/RFC-1383.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1466","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1466/RFC-1466.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1481","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1481/RFC-1481.txt"},{"from":"IETF RFC 1482","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1482/RFC-1482.txt"},{"from":"IETF RFC 1518","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1518/RFC-1518.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1710","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1710/RFC-1710.txt"},{"from":"IETF RFC 1884","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1338","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1339","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1339","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1339","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1334","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1334/RFC-1334.txt"},{"from":"IETF RFC 1356","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1377","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1393","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1393/RFC-1393.txt"},{"from":"IETF RFC 1408","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1408/RFC-1408.txt"},{"from":"IETF RFC 1409","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1409/RFC-1409.txt"},{"from":"IETF RFC 1413","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1413/RFC-1413.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1416","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1416/RFC-1416.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1492","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1492/RFC-1492.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1522","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1522/RFC-1522.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1548","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1548/RFC-1548.txt"},{"from":"IETF RFC 1552","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1552/RFC-1552.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1570","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1570/RFC-1570.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1590","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1590/RFC-1590.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1602","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1602/RFC-1602.txt"},{"from":"IETF RFC 1638","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1639","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1639/RFC-1639.txt"},{"from":"IETF RFC 1661","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1661/RFC-1661.txt"},{"from":"IETF RFC 1662","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 2067","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 1340","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1342","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1342/RFC-1342.txt"},{"from":"IETF RFC 1343","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1343/RFC-1343.txt"},{"from":"IETF RFC 1344","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1344/RFC-1344.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1425","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1425/RFC-1425.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1437","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1437/RFC-1437.txt"},{"from":"IETF RFC 1440","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1440/RFC-1440.txt"},{"from":"IETF RFC 1468","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1486","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1486/RFC-1486.txt"},{"from":"IETF RFC 1494","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1495","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1496","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1496/RFC-1496.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1563","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-1563/RFC-1563.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2161","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-2161/RFC-2161.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 1341","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 1425","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1425/RFC-1425.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1468","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1495","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1342","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1343","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1344","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1344","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1344","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1344","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1502","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1815","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 1345","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 1348","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1348/RFC-1348.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1385","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1385/RFC-1385.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1526","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1637","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1347","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1348","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1637","to":"IETF RFC 1348","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1348","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1706","to":"IETF RFC 1348","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 1349","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 158","to":"IETF RFC 135","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 1782","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-1782/RFC-1782.txt"},{"from":"IETF RFC 1783","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-1783/RFC-1783.txt"},{"from":"IETF RFC 1784","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-1784/RFC-1784.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1986","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-1986/RFC-1986.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2090","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2090/RFC-2090.txt"},{"from":"IETF RFC 2347","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2347/RFC-2347.txt"},{"from":"IETF RFC 2348","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2348/RFC-2348.txt"},{"from":"IETF RFC 2349","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2349/RFC-2349.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 1350","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 1352","to":"IETF RFC 1351","kind":"references","source":"IETF/RFC-1352/RFC-1352.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1351","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1351","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1351","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1351","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1334","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-1334/RFC-1334.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1353","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-1353/RFC-1353.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 1352","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1351","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-1351/RFC-1351.txt"},{"from":"IETF RFC 1352","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-1352/RFC-1352.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1353","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1354","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1354","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 1354","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1354","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 1354","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 1355","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 1362","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-1362/RFC-1362.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1582","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-1582/RFC-1582.txt"},{"from":"IETF RFC 1598","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-1598/RFC-1598.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1356","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1357","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1807","to":"IETF RFC 1357","kind":"references","source":"IETF/RFC-1807/RFC-1807.txt"},{"from":"IETF RFC 1396","to":"IETF RFC 1358","kind":"references","source":"IETF/RFC-1396/RFC-1396.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1358","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 1358","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1359","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 1359","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1360","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1362","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1633","to":"IETF RFC 1363","kind":"references","source":"IETF/RFC-1633/RFC-1633.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1363","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1363","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1363","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1364","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1367","to":"IETF RFC 1366","kind":"references","source":"IETF/RFC-1367/RFC-1367.txt"},{"from":"IETF RFC 1380","to":"IETF RFC 1366","kind":"references","source":"IETF/RFC-1380/RFC-1380.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1366","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1367","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1481","to":"IETF RFC 1367","kind":"references","source":"IETF/RFC-1481/RFC-1481.txt"},{"from":"IETF RFC 1482","to":"IETF RFC 1367","kind":"references","source":"IETF/RFC-1482/RFC-1482.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1368","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"IETF RFC 1368","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1368","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1369","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1369","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1369","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 1369","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 0137","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-0137/RFC-0137.txt"},{"from":"IETF RFC 0139","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-0139/RFC-0139.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 139","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-139/RFC-139.txt"},{"from":"IETF RFC 158","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 137","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1500","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1500/RFC-1500.txt"},{"from":"IETF RFC 1540","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1540/RFC-1540.txt"},{"from":"IETF RFC 1600","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1610","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1720","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1780","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 1920","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2200","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2400","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1370","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1370","to":"IETF RFC 1371","kind":"references","source":"IETF/RFC-1370/RFC-1370.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1372","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2217","to":"IETF RFC 1372","kind":"references","source":"IETF/RFC-2217/RFC-2217.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1372","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2067","to":"IETF RFC 1374","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 1374","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 1374","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1377","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1377","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1378","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1379","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1719","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1719/RFC-1719.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1955","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-1955/RFC-1955.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 1380","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1381","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1381","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1742","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-1742/RFC-1742.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1382","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1919","to":"IETF RFC 1383","kind":"references","source":"IETF/RFC-1919/RFC-1919.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1383","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 1383","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1384","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1385","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1385","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1385","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 1388","to":"IETF RFC 1387","kind":"references","source":"IETF/RFC-1388/RFC-1388.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1387","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1387","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1387/RFC-1387.txt"},{"from":"IETF RFC 1389","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1389/RFC-1389.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1582","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1582/RFC-1582.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1388","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 1387","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1387/RFC-1387.txt"},{"from":"IETF RFC 1388","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1388/RFC-1388.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2453","to":"IETF RFC 1389","kind":"references","source":"IETF/RFC-2453/RFC-2453.txt"},{"from":"IETF RFC 0139","to":"IETF RFC 139","kind":"references","source":"IETF/RFC-0139/RFC-0139.txt"},{"from":"IETF RFC 0318","to":"IETF RFC 139","kind":"references","source":"IETF/RFC-0318/RFC-0318.txt"},{"from":"IETF RFC 158","to":"IETF RFC 139","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 318","to":"IETF RFC 139","kind":"references","source":"IETF/RFC-318/RFC-318.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 139","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1390","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1390","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1390","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1402","to":"IETF RFC 1392","kind":"references","source":"IETF/RFC-1402/RFC-1402.txt"},{"from":"IETF RFC 1463","to":"IETF RFC 1392","kind":"references","source":"IETF/RFC-1463/RFC-1463.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1392","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1392","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1393","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1395","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 3933","to":"IETF RFC 1396","kind":"references","source":"IETF/RFC-3933/RFC-3933.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1397","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1397","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1515","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1398","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 140","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 1400","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1400","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1400","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 1463","to":"IETF RFC 1402","kind":"references","source":"IETF/RFC-1463/RFC-1463.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1402","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1402","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1855","to":"IETF RFC 1402","kind":"references","source":"IETF/RFC-1855/RFC-1855.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1403","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 2162","to":"IETF RFC 1405","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 1406","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 1407","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 1571","to":"IETF RFC 1408","kind":"references","source":"IETF/RFC-1571/RFC-1571.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 1408","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1408","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1416","to":"IETF RFC 1409","kind":"references","source":"IETF/RFC-1416/RFC-1416.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1409","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 141","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 141","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 2217","to":"IETF RFC 1411","kind":"references","source":"IETF/RFC-2217/RFC-2217.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1411","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 2217","to":"IETF RFC 1412","kind":"references","source":"IETF/RFC-2217/RFC-2217.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1412","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 1414","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-1414/RFC-1414.txt"},{"from":"IETF RFC 1459","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-1459/RFC-1459.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1413","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1414","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 1414","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1414","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1415","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2941","to":"IETF RFC 1416","kind":"references","source":"IETF/RFC-2941/RFC-2941.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1417","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1417","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1417","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 1417","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1418","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1418","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1419","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1419","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1419","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1419","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1419","to":"IETF RFC 1420","kind":"references","source":"IETF/RFC-1419/RFC-1419.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1420","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1420","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1420","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1420","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1864","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1864/RFC-1864.txt"},{"from":"IETF RFC 1875","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-1875/RFC-1875.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2228","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2228/RFC-2228.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2479","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2479/RFC-2479.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 1421","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1430","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1875","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-1875/RFC-1875.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2527","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3647","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 1422","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1875","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1875/RFC-1875.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1890","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 1991","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-1991/RFC-1991.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2313","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2313/RFC-2313.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 1423","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1422","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1422/RFC-1422.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1750","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1750/RFC-1750.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1875","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-1875/RFC-1875.txt"},{"from":"IETF RFC 2314","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-2314/RFC-2314.txt"},{"from":"IETF RFC 2315","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-2315/RFC-2315.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2986","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1424","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1830","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1830/RFC-1830.txt"},{"from":"IETF RFC 1854","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1854/RFC-1854.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1985","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-1985/RFC-1985.txt"},{"from":"IETF RFC 2197","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-2197/RFC-2197.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 1425","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1830","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-1830/RFC-1830.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1426","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1428","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1428","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1428","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 143","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1430","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1588","to":"IETF RFC 1430","kind":"references","source":"IETF/RFC-1588/RFC-1588.txt"},{"from":"IETF RFC 1462","to":"IETF RFC 1432","kind":"references","source":"IETF/RFC-1462/RFC-1462.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1432","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 1433","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1433","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1433","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 1435","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 1579","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-1579/RFC-1579.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1436","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 1437","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1440","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2206","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-2206/RFC-2206.txt"},{"from":"IETF RFC 2213","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-2213/RFC-2213.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1441","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1450","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1450/RFC-1450.txt"},{"from":"IETF RFC 1451","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1451/RFC-1451.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1566","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1566/RFC-1566.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1665","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1665/RFC-1665.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1696","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1696/RFC-1696.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2325","to":"IETF RFC 1442","kind":"references","source":"IETF/RFC-2325/RFC-2325.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1665","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1665/RFC-1665.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1443","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1444","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1451","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1451/RFC-1451.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1566","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1566/RFC-1566.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1665","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1665/RFC-1665.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1696","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1696/RFC-1696.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2206","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-2206/RFC-2206.txt"},{"from":"IETF RFC 2213","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-2213/RFC-2213.txt"},{"from":"IETF RFC 2325","to":"IETF RFC 1445","kind":"references","source":"IETF/RFC-2325/RFC-2325.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1446","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1450","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1450/RFC-1450.txt"},{"from":"IETF RFC 1451","to":"IETF RFC 1447","kind":"references","source":"IETF/RFC-1451/RFC-1451.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1450","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1450/RFC-1450.txt"},{"from":"IETF RFC 1451","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1451/RFC-1451.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1566","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1566/RFC-1566.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1611","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1611/RFC-1611.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1628","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1628/RFC-1628.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1665","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1665/RFC-1665.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1696","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1696/RFC-1696.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2206","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-2206/RFC-2206.txt"},{"from":"IETF RFC 2213","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-2213/RFC-2213.txt"},{"from":"IETF RFC 2325","to":"IETF RFC 1448","kind":"references","source":"IETF/RFC-2325/RFC-2325.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1447","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1447/RFC-1447.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 1449","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1442","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1442/RFC-1442.txt"},{"from":"IETF RFC 1444","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1444/RFC-1444.txt"},{"from":"IETF RFC 1445","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1445/RFC-1445.txt"},{"from":"IETF RFC 1446","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1446/RFC-1446.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1452","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1452/RFC-1452.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 1450","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1451","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1451","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1451","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 1441","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-1441/RFC-1441.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1592","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-1592/RFC-1592.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1452","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1454","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1455","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 1455","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1455","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1455","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1455","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1456","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1457","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1457","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2357","to":"IETF RFC 1458","kind":"references","source":"IETF/RFC-2357/RFC-2357.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1458","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 1458","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 2810","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-2810/RFC-2810.txt"},{"from":"IETF RFC 2811","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-2811/RFC-2811.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 1459","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 173","to":"IETF RFC 146","kind":"references","source":"IETF/RFC-173/RFC-173.txt"},{"from":"IETF RFC 1725","to":"IETF RFC 1460","kind":"references","source":"IETF/RFC-1725/RFC-1725.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 1460","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1461","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1461","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1461","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1461","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1463","to":"IETF RFC 1462","kind":"references","source":"IETF/RFC-1463/RFC-1463.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1462","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1462","to":"IETF RFC 1463","kind":"references","source":"IETF/RFC-1462/RFC-1462.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1463","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1463","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1464","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1465","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1801","to":"IETF RFC 1465","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1465","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1481","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1481/RFC-1481.txt"},{"from":"IETF RFC 1482","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1482/RFC-1482.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1518","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1518/RFC-1518.txt"},{"from":"IETF RFC 1520","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1520/RFC-1520.txt"},{"from":"IETF RFC 1597","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1597/RFC-1597.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1814","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1814/RFC-1814.txt"},{"from":"IETF RFC 1918","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-1918/RFC-1918.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2073","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-2073/RFC-2073.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 1466","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1467","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1467","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1502","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1554","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1815","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1468","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 1469","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 1469","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1469","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 1469","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1470","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1470","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1470","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 1470","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1470","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1471","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1471","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1471","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1471","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1471","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1472","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1472","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1472","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1473","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1473","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1473","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1473","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1474","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1474","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1475","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 1476","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1476","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1476","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1476","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1479","to":"IETF RFC 1478","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1478","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 1992","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-1992/RFC-1992.txt"},{"from":"IETF RFC 2154","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-2154/RFC-2154.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1479","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 1480","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1480","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1481","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1481","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1481","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1467","to":"IETF RFC 1482","kind":"references","source":"IETF/RFC-1467/RFC-1467.txt"},{"from":"IETF RFC 1520","to":"IETF RFC 1482","kind":"references","source":"IETF/RFC-1520/RFC-1520.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1482","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1482","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"IETF RFC 1483","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"IETF RFC 1577","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2098","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2098/RFC-2098.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1483","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1485","to":"IETF RFC 1484","kind":"references","source":"IETF/RFC-1485/RFC-1485.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1484","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 1484","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 1484","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1484/RFC-1484.txt"},{"from":"IETF RFC 1487","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1487/RFC-1487.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1801","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2659","to":"IETF RFC 1485","kind":"references","source":"IETF/RFC-2659/RFC-2659.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 1486","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1568","to":"IETF RFC 1486","kind":"references","source":"IETF/RFC-1568/RFC-1568.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1486","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 1487","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1558","to":"IETF RFC 1487","kind":"references","source":"IETF/RFC-1558/RFC-1558.txt"},{"from":"IETF RFC 1798","to":"IETF RFC 1487","kind":"references","source":"IETF/RFC-1798/RFC-1798.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 1487","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 1487","to":"IETF RFC 1488","kind":"references","source":"IETF/RFC-1487/RFC-1487.txt"},{"from":"IETF RFC 1558","to":"IETF RFC 1488","kind":"references","source":"IETF/RFC-1558/RFC-1558.txt"},{"from":"IETF RFC 1777","to":"IETF RFC 1488","kind":"references","source":"IETF/RFC-1777/RFC-1777.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 1488","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1489","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1489","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1973","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-1973/RFC-1973.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 3070","to":"IETF RFC 1490","kind":"references","source":"IETF/RFC-3070/RFC-3070.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 1492","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 1525","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-1525/RFC-1525.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 1493","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 1495","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1496","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-1496/RFC-1496.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2159","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-2159/RFC-2159.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1494","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1494","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2158","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-2158/RFC-2158.txt"},{"from":"IETF RFC 2161","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-2161/RFC-2161.txt"},{"from":"IETF RFC 2162","to":"IETF RFC 1495","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1496","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1496","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1496","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1496","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1496","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 1497","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1498","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1498","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1498","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 1500","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1494","to":"IETF RFC 1502","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1502","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1502","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1502","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1502","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1505","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1505","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1505","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1505","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1505","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1506","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 1511","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-1511/RFC-1511.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1507","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1509","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-1509/RFC-1509.txt"},{"from":"IETF RFC 1511","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-1511/RFC-1511.txt"},{"from":"IETF RFC 1731","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-1731/RFC-1731.txt"},{"from":"IETF RFC 1961","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-1961/RFC-1961.txt"},{"from":"IETF RFC 1964","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-1964/RFC-1964.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 1508","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 1511","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-1511/RFC-1511.txt"},{"from":"IETF RFC 1961","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-1961/RFC-1961.txt"},{"from":"IETF RFC 1964","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-1964/RFC-1964.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 1509","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1964","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-1964/RFC-1964.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2712","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2712/RFC-2712.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3129","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3129/RFC-3129.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 1510","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1511","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1512","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1512","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1512","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1512","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1512","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 1513","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1759","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2039","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-2039/RFC-2039.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1514","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1515","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1515","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1515","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 1515","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 1516","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1517","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1517","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1517","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1519","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1519/RFC-1519.txt"},{"from":"IETF RFC 1520","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1520/RFC-1520.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1678","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1678/RFC-1678.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1787","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1787/RFC-1787.txt"},{"from":"IETF RFC 1817","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1817/RFC-1817.txt"},{"from":"IETF RFC 1887","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1887/RFC-1887.txt"},{"from":"IETF RFC 1918","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-1918/RFC-1918.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1518","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1520","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1520/RFC-1520.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1631","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1631/RFC-1631.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1655","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1655/RFC-1655.txt"},{"from":"IETF RFC 1678","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1678/RFC-1678.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1772","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1772/RFC-1772.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1787","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1787/RFC-1787.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1817","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1817/RFC-1817.txt"},{"from":"IETF RFC 1878","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1878/RFC-1878.txt"},{"from":"IETF RFC 1918","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1918/RFC-1918.txt"},{"from":"IETF RFC 1930","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2036","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2036/RFC-2036.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1519","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1520","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 1520","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1520","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 1522","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1522/RFC-1522.txt"},{"from":"IETF RFC 1524","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1524/RFC-1524.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1554","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1556","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 1557","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1557/RFC-1557.txt"},{"from":"IETF RFC 1563","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1563/RFC-1563.txt"},{"from":"IETF RFC 1568","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1568/RFC-1568.txt"},{"from":"IETF RFC 1590","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1590/RFC-1590.txt"},{"from":"IETF RFC 1641","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1651","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1651/RFC-1651.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1714","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1714/RFC-1714.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1740","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1740/RFC-1740.txt"},{"from":"IETF RFC 1766","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1766/RFC-1766.txt"},{"from":"IETF RFC 1767","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1767/RFC-1767.txt"},{"from":"IETF RFC 1806","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1806/RFC-1806.txt"},{"from":"IETF RFC 1808","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1808/RFC-1808.txt"},{"from":"IETF RFC 1815","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1830","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1830/RFC-1830.txt"},{"from":"IETF RFC 1842","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1847","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1847/RFC-1847.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1864","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1864/RFC-1864.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1867","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1867/RFC-1867.txt"},{"from":"IETF RFC 1869","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1869/RFC-1869.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1872","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1872/RFC-1872.txt"},{"from":"IETF RFC 1873","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1873/RFC-1873.txt"},{"from":"IETF RFC 1874","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1892","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1892/RFC-1892.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2017","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2017/RFC-2017.txt"},{"from":"IETF RFC 2044","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2111","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2111/RFC-2111.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 1521","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1554","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1556","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 1557","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1557/RFC-1557.txt"},{"from":"IETF RFC 1641","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1651","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1651/RFC-1651.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1815","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1842","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 1867","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1867/RFC-1867.txt"},{"from":"IETF RFC 1869","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1869/RFC-1869.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1522","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1872","to":"IETF RFC 1524","kind":"references","source":"IETF/RFC-1872/RFC-1872.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1524","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1524","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 1524","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 1524","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1525","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1525","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1525","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 1525","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 1525","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 1526","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 1526","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1529","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-1529/RFC-1529.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 2302","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-2302/RFC-2302.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3250","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-3250/RFC-3250.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1528","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 1529","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1529","to":"IETF RFC 1530","kind":"references","source":"IETF/RFC-1529/RFC-1529.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1530","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1530","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1530","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1530","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 1531","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 1531","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1534","to":"IETF RFC 1531","kind":"references","source":"IETF/RFC-1534/RFC-1534.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1531","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1531","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1532","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1534","to":"IETF RFC 1532","kind":"references","source":"IETF/RFC-1534/RFC-1534.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 1532","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1534","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-1534/RFC-1534.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1533","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 1534","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1534","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1534","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1534","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 1534","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 1536","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-1536/RFC-1536.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 1535","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 1535","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-1535/RFC-1535.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1536","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 1535","to":"IETF RFC 1537","kind":"references","source":"IETF/RFC-1535/RFC-1535.txt"},{"from":"IETF RFC 1536","to":"IETF RFC 1537","kind":"references","source":"IETF/RFC-1536/RFC-1536.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1537","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1537","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1543","to":"IETF RFC 1540","kind":"references","source":"IETF/RFC-1543/RFC-1543.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1540","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1627","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1627/RFC-1627.txt"},{"from":"IETF RFC 1678","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1678/RFC-1678.txt"},{"from":"IETF RFC 1766","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1766/RFC-1766.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1541","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 1542","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 1550","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1550/RFC-1550.txt"},{"from":"IETF RFC 1590","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1590/RFC-1590.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1600","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1602","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1602/RFC-1602.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1610","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1610/RFC-1610.txt"},{"from":"IETF RFC 1720","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1720/RFC-1720.txt"},{"from":"IETF RFC 1780","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1780/RFC-1780.txt"},{"from":"IETF RFC 1800","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1800/RFC-1800.txt"},{"from":"IETF RFC 1916","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1916/RFC-1916.txt"},{"from":"IETF RFC 1920","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 2000","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2026","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-2026/RFC-2026.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2200","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1543","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 1884","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2526","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-2526/RFC-2526.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3258","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-3258/RFC-3258.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5548","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1546","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 1548","to":"IETF RFC 1547","kind":"references","source":"IETF/RFC-1548/RFC-1548.txt"},{"from":"IETF RFC 1661","to":"IETF RFC 1547","kind":"references","source":"IETF/RFC-1661/RFC-1661.txt"},{"from":"IETF RFC 1549","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1549/RFC-1549.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1552","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1552/RFC-1552.txt"},{"from":"IETF RFC 1553","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1553/RFC-1553.txt"},{"from":"IETF RFC 1570","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1570/RFC-1570.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1598","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1598/RFC-1598.txt"},{"from":"IETF RFC 1618","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1618/RFC-1618.txt"},{"from":"IETF RFC 1619","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1619/RFC-1619.txt"},{"from":"IETF RFC 1638","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 1548","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 1570","to":"IETF RFC 1549","kind":"references","source":"IETF/RFC-1570/RFC-1570.txt"},{"from":"IETF RFC 1598","to":"IETF RFC 1549","kind":"references","source":"IETF/RFC-1598/RFC-1598.txt"},{"from":"IETF RFC 1618","to":"IETF RFC 1549","kind":"references","source":"IETF/RFC-1618/RFC-1618.txt"},{"from":"IETF RFC 1619","to":"IETF RFC 1549","kind":"references","source":"IETF/RFC-1619/RFC-1619.txt"},{"from":"IETF RFC 168","to":"IETF RFC 155","kind":"references","source":"IETF/RFC-168/RFC-168.txt"},{"from":"IETF RFC 1667","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1667/RFC-1667.txt"},{"from":"IETF RFC 1668","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1668/RFC-1668.txt"},{"from":"IETF RFC 1669","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1669/RFC-1669.txt"},{"from":"IETF RFC 1670","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1670/RFC-1670.txt"},{"from":"IETF RFC 1671","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1671/RFC-1671.txt"},{"from":"IETF RFC 1672","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1672/RFC-1672.txt"},{"from":"IETF RFC 1673","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1673/RFC-1673.txt"},{"from":"IETF RFC 1674","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1674/RFC-1674.txt"},{"from":"IETF RFC 1675","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1675/RFC-1675.txt"},{"from":"IETF RFC 1676","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1676/RFC-1676.txt"},{"from":"IETF RFC 1677","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1677/RFC-1677.txt"},{"from":"IETF RFC 1678","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1678/RFC-1678.txt"},{"from":"IETF RFC 1679","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1679/RFC-1679.txt"},{"from":"IETF RFC 1680","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1680/RFC-1680.txt"},{"from":"IETF RFC 1681","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1681/RFC-1681.txt"},{"from":"IETF RFC 1682","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1682/RFC-1682.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1686","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1686/RFC-1686.txt"},{"from":"IETF RFC 1687","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1687/RFC-1687.txt"},{"from":"IETF RFC 1688","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1688/RFC-1688.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1710","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1710/RFC-1710.txt"},{"from":"IETF RFC 1715","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1715/RFC-1715.txt"},{"from":"IETF RFC 1719","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1719/RFC-1719.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1753","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1753/RFC-1753.txt"},{"from":"IETF RFC 1955","to":"IETF RFC 1550","kind":"references","source":"IETF/RFC-1955/RFC-1955.txt"},{"from":"IETF RFC 1552","to":"IETF RFC 1551","kind":"references","source":"IETF/RFC-1552/RFC-1552.txt"},{"from":"IETF RFC 1553","to":"IETF RFC 1551","kind":"references","source":"IETF/RFC-1553/RFC-1553.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1552","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1553","to":"IETF RFC 1552","kind":"references","source":"IETF/RFC-1553/RFC-1553.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1552","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1551","to":"IETF RFC 1553","kind":"references","source":"IETF/RFC-1551/RFC-1551.txt"},{"from":"IETF RFC 1552","to":"IETF RFC 1553","kind":"references","source":"IETF/RFC-1552/RFC-1552.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 1553","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1553","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1554","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1554","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1555","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 1556","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1556","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1815","to":"IETF RFC 1556","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1556","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1557","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1557","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 1557","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 1557","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 1557","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1558","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1559","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1559","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 1560","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 1560","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1560","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 1561","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1561","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1896","to":"IETF RFC 1563","kind":"references","source":"IETF/RFC-1896/RFC-1896.txt"},{"from":"IETF RFC 1566","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-1566/RFC-1566.txt"},{"from":"IETF RFC 1567","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-1567/RFC-1567.txt"},{"from":"IETF RFC 1697","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-1697/RFC-1697.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2039","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-2039/RFC-2039.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1565","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1566","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1566","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2039","to":"IETF RFC 1566","kind":"references","source":"IETF/RFC-2039/RFC-2039.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1566","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1567","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2039","to":"IETF RFC 1567","kind":"references","source":"IETF/RFC-2039/RFC-2039.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1568","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1638","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 1662","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 1717","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1969","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1969/RFC-1969.txt"},{"from":"IETF RFC 1977","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1977/RFC-1977.txt"},{"from":"IETF RFC 1979","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1979/RFC-1979.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 1993","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-1993/RFC-1993.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1570","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 1571","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1572","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1572","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1595","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1595/RFC-1595.txt"},{"from":"IETF RFC 1596","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1596/RFC-1596.txt"},{"from":"IETF RFC 1604","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1604/RFC-1604.txt"},{"from":"IETF RFC 1623","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1748","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 1757","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1757/RFC-1757.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2128","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2325","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2325/RFC-2325.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 1573","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1575","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 1576","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 1576","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1671","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1671/RFC-1671.txt"},{"from":"IETF RFC 1680","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1680/RFC-1680.txt"},{"from":"IETF RFC 1735","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1735/RFC-1735.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 1937","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-1937/RFC-1937.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2098","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2098/RFC-2098.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 1577","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 1579","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 1579","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 1579","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 1579","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 158","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 196","to":"IETF RFC 158","kind":"references","source":"IETF/RFC-196/RFC-196.txt"},{"from":"IETF RFC 221","to":"IETF RFC 158","kind":"references","source":"IETF/RFC-221/RFC-221.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1580","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1582","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1582","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1584","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1584/RFC-1584.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1586","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1586/RFC-1586.txt"},{"from":"IETF RFC 1587","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1587/RFC-1587.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1765","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1765/RFC-1765.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1930","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 2154","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2154/RFC-2154.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3137","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-3137/RFC-3137.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 1583","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 1585","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1585/RFC-1585.txt"},{"from":"IETF RFC 1587","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1587/RFC-1587.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1765","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1765/RFC-1765.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 2715","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2715/RFC-2715.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 1584","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1585","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 1585","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1586","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1586","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1586","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1586","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1765","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-1765/RFC-1765.txt"},{"from":"IETF RFC 1793","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-1793/RFC-1793.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 1587","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 1588","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 158","to":"IETF RFC 159","kind":"references","source":"IETF/RFC-158/RFC-158.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1872","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-1872/RFC-1872.txt"},{"from":"IETF RFC 1874","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2017","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2017/RFC-2017.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 1590","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2606","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-2606/RFC-2606.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 1591","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1592","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1592","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1592","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1592","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1900","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-1900/RFC-1900.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 1594","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1595","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1595","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1595","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 1595","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 1595","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1596","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1627","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1627/RFC-1627.txt"},{"from":"IETF RFC 1631","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1631/RFC-1631.txt"},{"from":"IETF RFC 1687","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1687/RFC-1687.txt"},{"from":"IETF RFC 1814","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1814/RFC-1814.txt"},{"from":"IETF RFC 1879","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1879/RFC-1879.txt"},{"from":"IETF RFC 1887","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1887/RFC-1887.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1919","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-1919/RFC-1919.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1597","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1598","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1598","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1598","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1602","to":"IETF RFC 1600","kind":"references","source":"IETF/RFC-1602/RFC-1602.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1600","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1627","to":"IETF RFC 1601","kind":"references","source":"IETF/RFC-1627/RFC-1627.txt"},{"from":"IETF RFC 2028","to":"IETF RFC 1601","kind":"references","source":"IETF/RFC-2028/RFC-2028.txt"},{"from":"IETF RFC 2850","to":"IETF RFC 1601","kind":"references","source":"IETF/RFC-2850/RFC-2850.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 1601","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 1603","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1603/RFC-1603.txt"},{"from":"IETF RFC 1627","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1627/RFC-1627.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1790","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1790/RFC-1790.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 1871","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-1871/RFC-1871.txt"},{"from":"IETF RFC 2014","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-2014/RFC-2014.txt"},{"from":"IETF RFC 2026","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-2026/RFC-2026.txt"},{"from":"IETF RFC 2027","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-2027/RFC-2027.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2282","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-2282/RFC-2282.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 1602","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 1871","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-1871/RFC-1871.txt"},{"from":"IETF RFC 2014","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-2014/RFC-2014.txt"},{"from":"IETF RFC 2028","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-2028/RFC-2028.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 7282","to":"IETF RFC 1603","kind":"references","source":"IETF/RFC-7282/RFC-7282.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1604","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1604","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1604","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1608","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1608","to":"IETF RFC 1609","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1609","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 1610","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1611","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1618","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1618","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2615","to":"IETF RFC 1619","kind":"references","source":"IETF/RFC-2615/RFC-2615.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 1619","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1620","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 1937","to":"IETF RFC 1620","kind":"references","source":"IETF/RFC-1937/RFC-1937.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1620","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1620","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 1620","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 1643","to":"IETF RFC 1623","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 1624","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1625","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1625","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1626","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1626","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1626","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1626","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 1626","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1627","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1627","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1628","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1628","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 1628","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 1637","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1706","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 1629","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1808","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-1808/RFC-1808.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2141","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2141/RFC-2141.txt"},{"from":"IETF RFC 2169","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2169/RFC-2169.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 1630","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2182","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2182/RFC-2182.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1631","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 1755","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 2205","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2205/RFC-2205.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 1633","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 1636","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 1706","to":"IETF RFC 1637","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 1638","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 1638","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 1638","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 1682","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-1682/RFC-1682.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 3092","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-3092/RFC-3092.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1639","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 173","to":"IETF RFC 164","kind":"references","source":"IETF/RFC-173/RFC-173.txt"},{"from":"IETF RFC 1642","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2044","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1641","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1641","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1874","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2044","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 1642","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1643","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1643","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1643","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1643","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1643","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1644","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 1646","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1647","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 1647","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 1648","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1648","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1648","to":"IETF RFC 1649","kind":"references","source":"IETF/RFC-1648/RFC-1648.txt"},{"from":"IETF RFC 172","to":"IETF RFC 165","kind":"references","source":"IETF/RFC-172/RFC-172.txt"},{"from":"IETF RFC 264","to":"IETF RFC 165","kind":"references","source":"IETF/RFC-264/RFC-264.txt"},{"from":"IETF RFC 265","to":"IETF RFC 165","kind":"references","source":"IETF/RFC-265/RFC-265.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 1650","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1854","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1854/RFC-1854.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1651","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 1652","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1653","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1653","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1655","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1655/RFC-1655.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1930","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2650","to":"IETF RFC 1654","kind":"references","source":"IETF/RFC-2650/RFC-2650.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 1655","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1657","to":"IETF RFC 1655","kind":"references","source":"IETF/RFC-1657/RFC-1657.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1655","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1656","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1656","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 1656","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-1656/RFC-1656.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 1657","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 1659","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-1659/RFC-1659.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1658","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1659","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1660","to":"IETF RFC 1659","kind":"references","source":"IETF/RFC-1660/RFC-1660.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1659","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1659","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1659","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1658","to":"IETF RFC 1660","kind":"references","source":"IETF/RFC-1658/RFC-1658.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1660","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1660","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1660","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1662","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 1663","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1663/RFC-1663.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1717","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1877","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1877/RFC-1877.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1962","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1962/RFC-1962.txt"},{"from":"IETF RFC 1967","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1967/RFC-1967.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 1969","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1969/RFC-1969.txt"},{"from":"IETF RFC 1973","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1973/RFC-1973.txt"},{"from":"IETF RFC 1974","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1974/RFC-1974.txt"},{"from":"IETF RFC 1977","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1977/RFC-1977.txt"},{"from":"IETF RFC 1979","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1979/RFC-1979.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 1993","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1993/RFC-1993.txt"},{"from":"IETF RFC 1994","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-1994/RFC-1994.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2118","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2118/RFC-2118.txt"},{"from":"IETF RFC 2125","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2125/RFC-2125.txt"},{"from":"IETF RFC 2153","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2153/RFC-2153.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 2420","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2420/RFC-2420.txt"},{"from":"IETF RFC 2433","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2433/RFC-2433.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2615","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2615/RFC-2615.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2809","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2809/RFC-2809.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2886","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2886/RFC-2886.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3374","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3818","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3818/RFC-3818.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5154","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 1661","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 1663","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-1663/RFC-1663.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1967","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-1967/RFC-1967.txt"},{"from":"IETF RFC 1973","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-1973/RFC-1973.txt"},{"from":"IETF RFC 1977","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-1977/RFC-1977.txt"},{"from":"IETF RFC 2171","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2615","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2615/RFC-2615.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 1662","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 1962","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1962/RFC-1962.txt"},{"from":"IETF RFC 1967","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1967/RFC-1967.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 1974","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1974/RFC-1974.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 1993","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-1993/RFC-1993.txt"},{"from":"IETF RFC 2118","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-2118/RFC-2118.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1663","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1664","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1664","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 1664","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1665","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1666","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1667","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1667","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 2502","to":"IETF RFC 1667","kind":"references","source":"IETF/RFC-2502/RFC-2502.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1668","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1669","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 1669","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 167","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1670","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1672","to":"IETF RFC 1671","kind":"references","source":"IETF/RFC-1672/RFC-1672.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1671","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 1671","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1672","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1673","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1674","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1675","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1676","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1677","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 2501","to":"IETF RFC 1677","kind":"references","source":"IETF/RFC-2501/RFC-2501.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1678","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1679","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1679","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 211","to":"IETF RFC 168","kind":"references","source":"IETF/RFC-211/RFC-211.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1680","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1681","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1681","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1682","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1683","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 2162","to":"IETF RFC 1685","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 1686","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1686","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1687","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1688","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1692","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1693","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1695","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-1695/RFC-1695.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 1694","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1694","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-1694/RFC-1694.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2514","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-2514/RFC-2514.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1695","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1696","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1696","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 1697","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1697","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1697","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1698","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1698","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 1710","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1710/RFC-1710.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1717","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1759","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 1788","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1788/RFC-1788.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1851","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1851/RFC-1851.txt"},{"from":"IETF RFC 1852","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1852/RFC-1852.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1962","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1962/RFC-1962.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 1994","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-1994/RFC-1994.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2059","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2059/RFC-2059.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2139","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2139/RFC-2139.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2181","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2181/RFC-2181.txt"},{"from":"IETF RFC 2189","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2189/RFC-2189.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2283","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2283/RFC-2283.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2335","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2335/RFC-2335.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2365","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2365/RFC-2365.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2723","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2723/RFC-2723.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3025","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3025/RFC-3025.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3208","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3208/RFC-3208.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3232","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3232/RFC-3232.txt"},{"from":"IETF RFC 3309","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3309/RFC-3309.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3359","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3359/RFC-3359.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 1700","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 1702","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-1702/RFC-1702.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2341","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2341/RFC-2341.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 1701","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 1702","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 1760","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-1760/RFC-1760.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1938","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-1938/RFC-1938.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2945","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-2945/RFC-2945.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 1704","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1705","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 1706","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1706","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1707","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1707","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1707","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 171","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 172","to":"IETF RFC 171","kind":"references","source":"IETF/RFC-172/RFC-172.txt"},{"from":"IETF RFC 196","to":"IETF RFC 171","kind":"references","source":"IETF/RFC-196/RFC-196.txt"},{"from":"IETF RFC 264","to":"IETF RFC 171","kind":"references","source":"IETF/RFC-264/RFC-264.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1710","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1710","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1712","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1712","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 1712","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 1713","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1713","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1713","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1713","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 1714","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1714","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1715","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 1715","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3194","to":"IETF RFC 1715","kind":"references","source":"IETF/RFC-3194/RFC-3194.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 1715","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 4692","to":"IETF RFC 1715","kind":"references","source":"IETF/RFC-4692/RFC-4692.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1716","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1717","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 1969","to":"IETF RFC 1717","kind":"references","source":"IETF/RFC-1969/RFC-1969.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1717","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 1717","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 1717","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1719","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 172","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 172","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 171","to":"IETF RFC 172","kind":"references","source":"IETF/RFC-171/RFC-171.txt"},{"from":"IETF RFC 265","to":"IETF RFC 172","kind":"references","source":"IETF/RFC-265/RFC-265.txt"},{"from":"IETF RFC 959","to":"IETF RFC 172","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1720","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1720","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1721","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1721","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1721","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1722","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1722","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1722","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1722","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1724","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-1724/RFC-1724.txt"},{"from":"IETF RFC 1923","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-1923/RFC-1923.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2174","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-2174/RFC-2174.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1723","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 1721","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-1721/RFC-1721.txt"},{"from":"IETF RFC 1722","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-1722/RFC-1722.txt"},{"from":"IETF RFC 1723","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-1723/RFC-1723.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 1724","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1725","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 1725","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1725","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1725","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1725","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1726","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1810","to":"IETF RFC 1726","kind":"references","source":"IETF/RFC-1810/RFC-1810.txt"},{"from":"IETF RFC 1835","to":"IETF RFC 1727","kind":"references","source":"IETF/RFC-1835/RFC-1835.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 1727","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 1727","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 1727","to":"IETF RFC 1728","kind":"references","source":"IETF/RFC-1727/RFC-1727.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1729","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 173","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 1731","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-1731/RFC-1731.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2062","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2062/RFC-2062.txt"},{"from":"IETF RFC 2086","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2086/RFC-2086.txt"},{"from":"IETF RFC 2087","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2087/RFC-2087.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1730","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1734","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-1734/RFC-1734.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2980","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-2980/RFC-2980.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1731","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1732","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1733","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 1734","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1735","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1735","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1735","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1735","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1808","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-1808/RFC-1808.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2276","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-2276/RFC-2276.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1736","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2141","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2141/RFC-2141.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2276","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2276/RFC-2276.txt"},{"from":"IETF RFC 2288","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2288/RFC-2288.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 6288","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-6288/RFC-6288.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 1737","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 1738","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 1738","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 1727","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1727/RFC-1727.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1808","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1808/RFC-1808.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 1980","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1980/RFC-1980.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2016","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2016/RFC-2016.txt"},{"from":"IETF RFC 2017","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2017/RFC-2017.txt"},{"from":"IETF RFC 2056","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2056/RFC-2056.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2079","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2079/RFC-2079.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2111","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2111/RFC-2111.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2186","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2186/RFC-2186.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2193","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2193/RFC-2193.txt"},{"from":"IETF RFC 2221","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2221/RFC-2221.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2276","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2276/RFC-2276.txt"},{"from":"IETF RFC 2291","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2368","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2368/RFC-2368.txt"},{"from":"IETF RFC 2369","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2369/RFC-2369.txt"},{"from":"IETF RFC 2371","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2371/RFC-2371.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2392","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2392/RFC-2392.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2511","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2511/RFC-2511.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2560","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2585","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2585/RFC-2585.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2655","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2655/RFC-2655.txt"},{"from":"IETF RFC 2656","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2656/RFC-2656.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 1738","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1739","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1739","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1740","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 1742","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1742","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1745","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1745","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1745","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1747","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1749","to":"IETF RFC 1748","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1748","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1748","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1748","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1748","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1749","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1749","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2412","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2412/RFC-2412.txt"},{"from":"IETF RFC 2433","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2433/RFC-2433.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2536","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2536/RFC-2536.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2777","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2777/RFC-2777.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3174","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3174/RFC-3174.txt"},{"from":"IETF RFC 3217","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3217/RFC-3217.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3766","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3766/RFC-3766.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4056","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4122","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 1750","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 1752","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1752","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 1752","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1752","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 1753","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1753","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 1753","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 1937","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-1937/RFC-1937.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 1755","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1756","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1757","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1759","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 1938","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-1938/RFC-1938.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2945","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-2945/RFC-2945.txt"},{"from":"IETF RFC 4082","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-4082/RFC-4082.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 1760","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1762","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1763","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1764","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 1765","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 1835","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-1835/RFC-1835.txt"},{"from":"IETF RFC 1942","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-1942/RFC-1942.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2413","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2413/RFC-2413.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2482","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2596","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2596/RFC-2596.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2731","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2731/RFC-2731.txt"},{"from":"IETF RFC 2771","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2771/RFC-2771.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 2987","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-2987/RFC-2987.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4645","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 5645","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 1766","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1767","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 1767","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1767","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 1767","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1767","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1768","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 1768","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 1769","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 177","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1770","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 1770","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1770","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 1772","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1772/RFC-1772.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1863","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1863/RFC-1863.txt"},{"from":"IETF RFC 1965","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1965/RFC-1965.txt"},{"from":"IETF RFC 1966","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1966/RFC-1966.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1997","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1997/RFC-1997.txt"},{"from":"IETF RFC 1998","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-1998/RFC-1998.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2280","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2280/RFC-2280.txt"},{"from":"IETF RFC 2283","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2283/RFC-2283.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2796","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2796/RFC-2796.txt"},{"from":"IETF RFC 2842","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2842/RFC-2842.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2918","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-2918/RFC-2918.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3345","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3345/RFC-3345.txt"},{"from":"IETF RFC 3392","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3392/RFC-3392.txt"},{"from":"IETF RFC 3528","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3528/RFC-3528.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4384","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4384/RFC-4384.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 1771","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 1772","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 1773","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1773","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 1773","to":"IETF RFC 1774","kind":"references","source":"IETF/RFC-1773/RFC-1773.txt"},{"from":"IETF RFC 2439","to":"IETF RFC 1774","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1775","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 1779","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-1779/RFC-1779.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 1960","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-1960/RFC-1960.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2559","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2559/RFC-2559.txt"},{"from":"IETF RFC 2587","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2587/RFC-2587.txt"},{"from":"IETF RFC 2657","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2657/RFC-2657.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 1777","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 1960","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-1960/RFC-1960.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2256","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2559","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-2559/RFC-2559.txt"},{"from":"IETF RFC 3001","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-3001/RFC-3001.txt"},{"from":"IETF RFC 3061","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-3061/RFC-3061.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 1778","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 1777","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-1777/RFC-1777.txt"},{"from":"IETF RFC 1778","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-1778/RFC-1778.txt"},{"from":"IETF RFC 1781","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-1781/RFC-1781.txt"},{"from":"IETF RFC 1836","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 1959","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-1959/RFC-1959.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2294","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2872","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-2872/RFC-2872.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 1779","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 1780","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1779","to":"IETF RFC 1781","kind":"references","source":"IETF/RFC-1779/RFC-1779.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 1781","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 1783","to":"IETF RFC 1782","kind":"references","source":"IETF/RFC-1783/RFC-1783.txt"},{"from":"IETF RFC 1784","to":"IETF RFC 1782","kind":"references","source":"IETF/RFC-1784/RFC-1784.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1782","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2090","to":"IETF RFC 1782","kind":"references","source":"IETF/RFC-2090/RFC-2090.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1782","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1782","to":"IETF RFC 1783","kind":"references","source":"IETF/RFC-1782/RFC-1782.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1783","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2090","to":"IETF RFC 1783","kind":"references","source":"IETF/RFC-2090/RFC-2090.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1783","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1782","to":"IETF RFC 1784","kind":"references","source":"IETF/RFC-1782/RFC-1782.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1784","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1784","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1879","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-1879/RFC-1879.txt"},{"from":"IETF RFC 2280","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-2280/RFC-2280.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2769","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-2769/RFC-2769.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 1786","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1787","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1788","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 1788","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1788","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 2339","to":"IETF RFC 1790","kind":"references","source":"IETF/RFC-2339/RFC-2339.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 1790","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 1790","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 1790","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1791","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1792","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4136","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-4136/RFC-4136.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 1793","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1794","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 1794","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 1794","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1794","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 2026","to":"IETF RFC 1796","kind":"references","source":"IETF/RFC-2026/RFC-2026.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 1796","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 1796","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 1879","to":"IETF RFC 1797","kind":"references","source":"IETF/RFC-1879/RFC-1879.txt"},{"from":"IETF RFC 2770","to":"IETF RFC 1797","kind":"references","source":"IETF/RFC-2770/RFC-2770.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 1797","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 1797","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1797","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1798","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 1798","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 1818","to":"IETF RFC 1800","kind":"references","source":"IETF/RFC-1818/RFC-1818.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1800","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1851","to":"IETF RFC 1800","kind":"references","source":"IETF/RFC-1851/RFC-1851.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1800","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 1836","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 1837","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-1837/RFC-1837.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2293","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-2293/RFC-2293.txt"},{"from":"IETF RFC 2294","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1801","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1804","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1867","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-1867/RFC-1867.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1806","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 1807","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 1866","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2368","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2368/RFC-2368.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 1808","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 1809","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1809","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3607","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-3607/RFC-3607.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 1810","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 1878","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-1878/RFC-1878.txt"},{"from":"IETF RFC 1879","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-1879/RFC-1879.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2075","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2075/RFC-2075.txt"},{"from":"IETF RFC 2267","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2267/RFC-2267.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2453","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2453/RFC-2453.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2644","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2644/RFC-2644.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2678","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2678/RFC-2678.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2827","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2827/RFC-2827.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3626","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3626/RFC-3626.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5136","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5136/RFC-5136.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 1812","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 1813","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1814","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1814","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1814","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1815","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1817","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1817","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1818","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 1818","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 3967","to":"IETF RFC 1818","kind":"references","source":"IETF/RFC-3967/RFC-3967.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 1818","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 2098","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-2098/RFC-2098.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 5513","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-5513/RFC-5513.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 1819","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 2022","to":"IETF RFC 1821","kind":"references","source":"IETF/RFC-2022/RFC-2022.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 1821","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 1821","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 1834","to":"IETF RFC 1822","kind":"references","source":"IETF/RFC-1834/RFC-1834.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1822","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1824","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1824","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2065","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2065/RFC-2065.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2207","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2207/RFC-2207.txt"},{"from":"IETF RFC 2243","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2243/RFC-2243.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2362","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2362/RFC-2362.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1825","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 1821","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1821/RFC-1821.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 1828","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1828/RFC-1828.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1971","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2085","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2085/RFC-2085.txt"},{"from":"IETF RFC 2104","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2104/RFC-2104.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2207","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2207/RFC-2207.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1826","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1949","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-1949/RFC-1949.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2008","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2008/RFC-2008.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2082","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2082/RFC-2082.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2207","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2207/RFC-2207.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2289","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2289/RFC-2289.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1827","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1826","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-1826/RFC-1826.txt"},{"from":"IETF RFC 2085","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-2085/RFC-2085.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1828","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1825","to":"IETF RFC 1829","kind":"references","source":"IETF/RFC-1825/RFC-1825.txt"},{"from":"IETF RFC 1827","to":"IETF RFC 1829","kind":"references","source":"IETF/RFC-1827/RFC-1827.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1829","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1829","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1829","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 1830","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 1832","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-1832/RFC-1832.txt"},{"from":"IETF RFC 1833","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-1833/RFC-1833.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2188","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2188/RFC-2188.txt"},{"from":"IETF RFC 2203","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2203/RFC-2203.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 1831","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1833","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-1833/RFC-1833.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2188","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2188/RFC-2188.txt"},{"from":"IETF RFC 2203","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2203/RFC-2203.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4506","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-4506/RFC-4506.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 1832","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2188","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2188/RFC-2188.txt"},{"from":"IETF RFC 2203","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2203/RFC-2203.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 1833","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 1834","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1834","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 1913","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-1913/RFC-1913.txt"},{"from":"IETF RFC 1914","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-1914/RFC-1914.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1835","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 1836","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 1836","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 1837","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 1837","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 1836","to":"IETF RFC 1838","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1842","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1842","to":"IETF RFC 1843","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1843","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1845","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1845","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1845","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 1845","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1846","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1846","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1846","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 1846","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 2015","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2015/RFC-2015.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 1847","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 1867","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-1867/RFC-1867.txt"},{"from":"IETF RFC 2015","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-2015/RFC-2015.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 1848","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 1850","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1851","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1851","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 1851","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1851","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 1851","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 2085","to":"IETF RFC 1852","kind":"references","source":"IETF/RFC-2085/RFC-2085.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 1853","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2197","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-2197/RFC-2197.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 1854","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1855","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 3128","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-3128/RFC-3128.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5722","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-5722/RFC-5722.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1858","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1859","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 1966","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-1966/RFC-1966.txt"},{"from":"IETF RFC 2796","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-2796/RFC-2796.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4223","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-4223/RFC-4223.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 1863","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2069","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2069/RFC-2069.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 1864","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1942","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-1942/RFC-1942.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1980","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-1980/RFC-1980.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2079","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2079/RFC-2079.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2291","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2397","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2397/RFC-2397.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 1866","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2310","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2310/RFC-2310.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2586","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2586/RFC-2586.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 1867","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1868","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2034","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2034/RFC-2034.txt"},{"from":"IETF RFC 2197","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2197/RFC-2197.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 2979","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-2979/RFC-2979.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1869","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 1870","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 1871","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 1871","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 1872","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1873","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 1873","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 1873","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1873","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2111","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-2111/RFC-2111.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 1874","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 1875","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 1876","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1876","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 1876","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 1876","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 2194","to":"IETF RFC 1877","kind":"references","source":"IETF/RFC-2194/RFC-2194.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 1877","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1877","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1877","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 1878","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 1878","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1879","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1881","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 1881","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 1881","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 1881","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 1881","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 1884","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1887","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1887/RFC-1887.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1924","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1924/RFC-1924.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1972","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1972/RFC-1972.txt"},{"from":"IETF RFC 1981","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-1981/RFC-1981.txt"},{"from":"IETF RFC 2019","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2133","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2133/RFC-2133.txt"},{"from":"IETF RFC 2147","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2147/RFC-2147.txt"},{"from":"IETF RFC 2292","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2292/RFC-2292.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 1883","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1886","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1886/RFC-1886.txt"},{"from":"IETF RFC 1887","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1887/RFC-1887.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1897","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1897/RFC-1897.txt"},{"from":"IETF RFC 1924","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1924/RFC-1924.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1971","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 1972","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-1972/RFC-1972.txt"},{"from":"IETF RFC 2019","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2073","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2073/RFC-2073.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2133","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2133/RFC-2133.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2365","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-2365/RFC-2365.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 1884","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1981","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-1981/RFC-1981.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 1885","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 3364","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3364/RFC-3364.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 1886","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 1884","to":"IETF RFC 1887","kind":"references","source":"IETF/RFC-1884/RFC-1884.txt"},{"from":"IETF RFC 2073","to":"IETF RFC 1887","kind":"references","source":"IETF/RFC-2073/RFC-2073.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 1888","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1888","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 1888","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1888","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"IETF RFC 1889","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 1890","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 2029","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2029/RFC-2029.txt"},{"from":"IETF RFC 2032","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2032/RFC-2032.txt"},{"from":"IETF RFC 2038","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2190","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 2198","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2198/RFC-2198.txt"},{"from":"IETF RFC 2211","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2211/RFC-2211.txt"},{"from":"IETF RFC 2250","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2343","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2343/RFC-2343.txt"},{"from":"IETF RFC 2354","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2354/RFC-2354.txt"},{"from":"IETF RFC 2429","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2429/RFC-2429.txt"},{"from":"IETF RFC 2431","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2431/RFC-2431.txt"},{"from":"IETF RFC 2435","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2435/RFC-2435.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2658","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2658/RFC-2658.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 2736","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2736/RFC-2736.txt"},{"from":"IETF RFC 2762","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2762/RFC-2762.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2793","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2833","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2833/RFC-2833.txt"},{"from":"IETF RFC 2862","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2862/RFC-2862.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3009","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3009/RFC-3009.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3304","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3304/RFC-3304.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3389","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3448","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3448/RFC-3448.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 1889","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 189","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 385","to":"IETF RFC 189","kind":"references","source":"IETF/RFC-385/RFC-385.txt"},{"from":"IETF RFC 454","to":"IETF RFC 189","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 739","to":"IETF RFC 189","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 2029","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2029/RFC-2029.txt"},{"from":"IETF RFC 2032","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2032/RFC-2032.txt"},{"from":"IETF RFC 2038","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2190","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 2198","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2198/RFC-2198.txt"},{"from":"IETF RFC 2250","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2429","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2429/RFC-2429.txt"},{"from":"IETF RFC 2431","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2431/RFC-2431.txt"},{"from":"IETF RFC 2435","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2435/RFC-2435.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2586","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2586/RFC-2586.txt"},{"from":"IETF RFC 2658","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2658/RFC-2658.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2833","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2833/RFC-2833.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3389","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 1890","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 1892","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-1892/RFC-1892.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 1891","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 1892","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 2034","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2034/RFC-2034.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3463","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-3463/RFC-3463.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 1893","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1892","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-1892/RFC-1892.txt"},{"from":"IETF RFC 1893","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-1893/RFC-1893.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2034","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2034/RFC-2034.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 1894","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 1896","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 1896","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 1896","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 1896","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1897","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 1897","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 1897","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 1897","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1900","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 1901","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1903","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1903/RFC-1903.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2012","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2012/RFC-2012.txt"},{"from":"IETF RFC 2013","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2013/RFC-2013.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2123","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2123/RFC-2123.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2128","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 2458","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2458/RFC-2458.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2493","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2493/RFC-2493.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2514","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2514/RFC-2514.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1902","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2493","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2493/RFC-2493.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2514","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2514/RFC-2514.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1903","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 2020","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2020/RFC-2020.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1904","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1906","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1906/RFC-1906.txt"},{"from":"IETF RFC 1907","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1907/RFC-1907.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2115","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2128","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 1905","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 2021","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2021/RFC-2021.txt"},{"from":"IETF RFC 2037","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2037/RFC-2037.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2579","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2579/RFC-2579.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 1906","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1904","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1904/RFC-1904.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1908","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1908/RFC-1908.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 1907","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 1901","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1901/RFC-1901.txt"},{"from":"IETF RFC 1902","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1902/RFC-1902.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1906","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1906/RFC-1906.txt"},{"from":"IETF RFC 1909","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1909/RFC-1909.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2089","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2089/RFC-2089.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 1908","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 1910","to":"IETF RFC 1909","kind":"references","source":"IETF/RFC-1910/RFC-1910.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1909","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1909","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1909","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1909","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 1910","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 1910","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 1910","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 1910","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2422","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 1911","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1912","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1914","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-1914/RFC-1914.txt"},{"from":"IETF RFC 2651","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-2651/RFC-2651.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1913","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1913","to":"IETF RFC 1914","kind":"references","source":"IETF/RFC-1913/RFC-1913.txt"},{"from":"IETF RFC 2651","to":"IETF RFC 1914","kind":"references","source":"IETF/RFC-2651/RFC-2651.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1914","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 1915","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1916","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1916","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 2050","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2050/RFC-2050.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2267","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2267/RFC-2267.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2647","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2647/RFC-2647.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2827","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2827/RFC-2827.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3809","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3809/RFC-3809.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3882","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3882/RFC-3882.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4016","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4016/RFC-4016.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5635","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5635/RFC-5635.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6832","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6832/RFC-6832.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7793","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7793/RFC-7793.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 1918","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 1919","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1919","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 1919","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 1919","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 1920","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 1920","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 1920","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1920","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1922","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 1923","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 1923","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1924","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1924","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 1924","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 1925","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 1925","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 1925","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 1961","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-1961/RFC-1961.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2979","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-2979/RFC-2979.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3089","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-3089/RFC-3089.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 1928","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 1929","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1929","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2770","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-2770/RFC-2770.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 1930","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 1931","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 1931","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 1932","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2185","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2185/RFC-2185.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 1933","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1936","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1936","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 1937","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2243","to":"IETF RFC 1938","kind":"references","source":"IETF/RFC-2243/RFC-2243.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 1938","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1938","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3206","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3206/RFC-3206.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4686","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-4686/RFC-4686.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 1939","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 1940","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1940","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 1942","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 1942","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2285","to":"IETF RFC 1944","kind":"references","source":"IETF/RFC-2285/RFC-2285.txt"},{"from":"IETF RFC 2432","to":"IETF RFC 1944","kind":"references","source":"IETF/RFC-2432/RFC-2432.txt"},{"from":"IETF RFC 2544","to":"IETF RFC 1944","kind":"references","source":"IETF/RFC-2544/RFC-2544.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2069","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2069/RFC-2069.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2084","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2084/RFC-2084.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2145","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2145/RFC-2145.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2169","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2169/RFC-2169.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2295","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 1945","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1948","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2189","to":"IETF RFC 1949","kind":"references","source":"IETF/RFC-2189/RFC-2189.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 1949","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 1949","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2627","to":"IETF RFC 1949","kind":"references","source":"IETF/RFC-2627/RFC-2627.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1949","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3274","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-3274/RFC-3274.txt"},{"from":"IETF RFC 3385","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 6713","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-6713/RFC-6713.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 1950","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 1951","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"IETF RFC 2068","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2394","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2394/RFC-2394.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3274","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-3274/RFC-3274.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 6713","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-6713/RFC-6713.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7932","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-7932/RFC-7932.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 1951","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6713","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-6713/RFC-6713.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8478","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-8478/RFC-8478.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 1952","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 1955","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 1955","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 1955","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5338","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5338/RFC-5338.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 1958","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 1959","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 1959","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 1959","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 196","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 221","to":"IETF RFC 196","kind":"references","source":"IETF/RFC-221/RFC-221.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 1960","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 1960","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 1961","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1961","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 1967","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1967/RFC-1967.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 1974","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1974/RFC-1974.txt"},{"from":"IETF RFC 1977","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1977/RFC-1977.txt"},{"from":"IETF RFC 1979","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1979/RFC-1979.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 1993","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-1993/RFC-1993.txt"},{"from":"IETF RFC 2118","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-2118/RFC-2118.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 1962","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 2025","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2479","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2479/RFC-2479.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4401","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4401/RFC-4401.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 1964","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 1966","to":"IETF RFC 1965","kind":"references","source":"IETF/RFC-1966/RFC-1966.txt"},{"from":"IETF RFC 1997","to":"IETF RFC 1965","kind":"references","source":"IETF/RFC-1997/RFC-1997.txt"},{"from":"IETF RFC 2796","to":"IETF RFC 1965","kind":"references","source":"IETF/RFC-2796/RFC-2796.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 1965","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 1965","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 2547","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-2547/RFC-2547.txt"},{"from":"IETF RFC 2796","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-2796/RFC-2796.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 1966","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 1967","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 1967","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 1969","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-1969/RFC-1969.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 2420","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-2420/RFC-2420.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 1968","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 1968","to":"IETF RFC 1969","kind":"references","source":"IETF/RFC-1968/RFC-1968.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 1969","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 1969","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1971","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 1972","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-1972/RFC-1972.txt"},{"from":"IETF RFC 2019","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2080","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2080/RFC-2080.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2292","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2292/RFC-2292.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1970","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 1888","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1972","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-1972/RFC-1972.txt"},{"from":"IETF RFC 2019","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2023","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2023/RFC-2023.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 1971","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 1971","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-1971/RFC-1971.txt"},{"from":"IETF RFC 2073","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-2073/RFC-2073.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 1972","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1973","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 1967","to":"IETF RFC 1974","kind":"references","source":"IETF/RFC-1967/RFC-1967.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 1974","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 1979","to":"IETF RFC 1977","kind":"references","source":"IETF/RFC-1979/RFC-1979.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 1977","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 1979","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 1980","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2292","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2292/RFC-2292.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3542","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3542/RFC-3542.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 1981","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2182","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2182/RFC-2182.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3081","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-3081/RFC-3081.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 1982","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 2350","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-2350/RFC-2350.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2504","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-2504/RFC-2504.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 1983","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 2804","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-2804/RFC-2804.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 1984","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 1985","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 1986","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 1986","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 1987","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 2108","to":"IETF RFC 1988","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1989","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2125","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2125/RFC-2125.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3337","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 1990","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 2015","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-2015/RFC-2015.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3626","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-3626/RFC-3626.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 1991","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 1992","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1992","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 1992","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 1993","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2433","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2433/RFC-2433.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 1994","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 1996","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-1996/RFC-1996.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1995","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1995","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-1995/RFC-1995.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 1996","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1998","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-1998/RFC-1998.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2280","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-2280/RFC-2280.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3704","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-3704/RFC-3704.txt"},{"from":"IETF RFC 3765","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-3765/RFC-3765.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4384","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4384/RFC-4384.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 1997","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 2650","to":"IETF RFC 1998","kind":"references","source":"IETF/RFC-2650/RFC-2650.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 1998","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 2000","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2309","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2309/RFC-2309.txt"},{"from":"IETF RFC 2357","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2357/RFC-2357.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2582","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2582/RFC-2582.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2001","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2004","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2004/RFC-2004.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2267","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2267/RFC-2267.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2644","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2644/RFC-2644.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2827","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2827/RFC-2827.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3025","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3025/RFC-3025.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3141","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3141/RFC-3141.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2002","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2004","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2004/RFC-2004.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2356","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2356/RFC-2356.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 2003","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2004","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 2006","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-2006/RFC-2006.txt"},{"from":"IETF RFC 2209","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-2209/RFC-2209.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2005","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 2005","to":"IETF RFC 2006","kind":"references","source":"IETF/RFC-2005/RFC-2005.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2006","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2006","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2006","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2006","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2007","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 2008","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2260","to":"IETF RFC 2008","kind":"references","source":"IETF/RFC-2260/RFC-2260.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2008","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2008","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2009","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2011","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2012","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2013","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 2013","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2013","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2013","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 2028","to":"IETF RFC 2014","kind":"references","source":"IETF/RFC-2028/RFC-2028.txt"},{"from":"IETF RFC 2850","to":"IETF RFC 2014","kind":"references","source":"IETF/RFC-2850/RFC-2850.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2014","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 2014","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2015","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2016","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2017","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2017","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2017","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2017","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2582","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2582/RFC-2582.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2883","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 2018","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2019","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2020","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2020","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2020","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2021","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 2098","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2098/RFC-2098.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2602","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2602/RFC-2602.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2022","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 2023","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2023","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 2023","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 2023","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2024","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2479","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-2479/RFC-2479.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 2025","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 2028","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2028/RFC-2028.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2256","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2339","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2339/RFC-2339.txt"},{"from":"IETF RFC 2357","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2357/RFC-2357.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2436","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2436/RFC-2436.txt"},{"from":"IETF RFC 2438","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2438/RFC-2438.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2629","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2629/RFC-2629.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2717","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2717/RFC-2717.txt"},{"from":"IETF RFC 2732","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2732/RFC-2732.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2795","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2795/RFC-2795.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2850","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2850/RFC-2850.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2886","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2886/RFC-2886.txt"},{"from":"IETF RFC 2903","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2903/RFC-2903.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3068","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3068/RFC-3068.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3131","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3131/RFC-3131.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3233","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3233/RFC-3233.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3304","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3304/RFC-3304.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3309","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3309/RFC-3309.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3327","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3327/RFC-3327.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3347","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3347/RFC-3347.txt"},{"from":"IETF RFC 3356","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3356/RFC-3356.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3385","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3385/RFC-3385.txt"},{"from":"IETF RFC 3386","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3386/RFC-3386.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3407","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3407/RFC-3407.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3425","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3425/RFC-3425.txt"},{"from":"IETF RFC 3427","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3427/RFC-3427.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3453","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3453/RFC-3453.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3478","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3478/RFC-3478.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3482","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3531","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3531/RFC-3531.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 3563","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3563/RFC-3563.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3589","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3589/RFC-3589.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3643","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3643/RFC-3643.txt"},{"from":"IETF RFC 3667","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3667/RFC-3667.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3683","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3683/RFC-3683.txt"},{"from":"IETF RFC 3690","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3690/RFC-3690.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 3933","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3933/RFC-3933.txt"},{"from":"IETF RFC 3934","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3934/RFC-3934.txt"},{"from":"IETF RFC 3967","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3967/RFC-3967.txt"},{"from":"IETF RFC 3978","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3978/RFC-3978.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 4052","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4052/RFC-4052.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4608","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4608/RFC-4608.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4766","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4766/RFC-4766.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4794","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4794/RFC-4794.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4845","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4845/RFC-4845.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 4897","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4897/RFC-4897.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5111","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5111/RFC-5111.txt"},{"from":"IETF RFC 5125","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5125/RFC-5125.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6410","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6410/RFC-6410.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7127","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7127/RFC-7127.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 2026","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 2028","to":"IETF RFC 2027","kind":"references","source":"IETF/RFC-2028/RFC-2028.txt"},{"from":"IETF RFC 2282","to":"IETF RFC 2027","kind":"references","source":"IETF/RFC-2282/RFC-2282.txt"},{"from":"IETF RFC 3777","to":"IETF RFC 2027","kind":"references","source":"IETF/RFC-3777/RFC-3777.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3233","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3233/RFC-3233.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3667","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3667/RFC-3667.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3978","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3978/RFC-3978.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 2028","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2029","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2029","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2029","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 203","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3643","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-3643/RFC-3643.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4075","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-4075/RFC-4075.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2030","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 2031","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 2031","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 2029","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-2029/RFC-2029.txt"},{"from":"IETF RFC 2190","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 2429","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-2429/RFC-2429.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 2032","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 2033","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2034","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 2435","to":"IETF RFC 2035","kind":"references","source":"IETF/RFC-2435/RFC-2435.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 2036","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2037","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 2250","to":"IETF RFC 2038","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2039","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2039","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 3962","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-3962/RFC-3962.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 2040","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2043","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2287","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2295","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2044","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 2045","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 2045","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 2045","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"IETF RFC 2046","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2077","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2077/RFC-2077.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2158","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2158/RFC-2158.txt"},{"from":"IETF RFC 2159","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2159/RFC-2159.txt"},{"from":"IETF RFC 2161","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2161/RFC-2161.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2302","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2302/RFC-2302.txt"},{"from":"IETF RFC 2306","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2306/RFC-2306.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2392","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2392/RFC-2392.txt"},{"from":"IETF RFC 2397","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2397/RFC-2397.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 2779","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2779/RFC-2779.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3250","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3250/RFC-3250.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3310","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3310/RFC-3310.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3516","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3516/RFC-3516.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3629","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3839","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3839/RFC-3839.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4073","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4073/RFC-4073.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4155","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4155/RFC-4155.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6839","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 2045","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 2046","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"IETF RFC 2045","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2346","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2346/RFC-2346.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 2424","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2424/RFC-2424.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3420","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3420/RFC-3420.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4155","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4155/RFC-4155.txt"},{"from":"IETF RFC 4180","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4180/RFC-4180.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 2046","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 2046","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2368","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2368/RFC-2368.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3516","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3516/RFC-3516.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2047","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2302","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2302/RFC-2302.txt"},{"from":"IETF RFC 2306","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2306/RFC-2306.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2422","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3009","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3009/RFC-3009.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3250","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3250/RFC-3250.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3362","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3362/RFC-3362.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4155","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4155/RFC-4155.txt"},{"from":"IETF RFC 4180","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4180/RFC-4180.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2048","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2049","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 2050","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2051","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2052","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 2055","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2055/RFC-2055.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2054","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 2054","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-2054/RFC-2054.txt"},{"from":"IETF RFC 2224","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-2224/RFC-2224.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2055","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2056","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2059","to":"IETF RFC 2058","kind":"references","source":"IETF/RFC-2059/RFC-2059.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 2058","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 2058","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2194","to":"IETF RFC 2058","kind":"references","source":"IETF/RFC-2194/RFC-2194.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2058","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 2059","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2194","to":"IETF RFC 2059","kind":"references","source":"IETF/RFC-2194/RFC-2194.txt"},{"from":"IETF RFC 216","to":"IETF RFC 206","kind":"references","source":"IETF/RFC-216/RFC-216.txt"},{"from":"IETF RFC 2061","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2061/RFC-2061.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2177","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2177/RFC-2177.txt"},{"from":"IETF RFC 2180","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2180/RFC-2180.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2193","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2193/RFC-2193.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2221","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2221/RFC-2221.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2245","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2245/RFC-2245.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2342","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2342/RFC-2342.txt"},{"from":"IETF RFC 2359","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2359/RFC-2359.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2971","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-2971/RFC-2971.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3348","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3348/RFC-3348.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2060","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 2061","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2061","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2061","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 2062","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2062","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2062","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2064","to":"IETF RFC 2063","kind":"references","source":"IETF/RFC-2064/RFC-2064.txt"},{"from":"IETF RFC 2123","to":"IETF RFC 2063","kind":"references","source":"IETF/RFC-2123/RFC-2123.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2063","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2063","to":"IETF RFC 2064","kind":"references","source":"IETF/RFC-2063/RFC-2063.txt"},{"from":"IETF RFC 2123","to":"IETF RFC 2064","kind":"references","source":"IETF/RFC-2123/RFC-2123.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2064","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2137","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2137/RFC-2137.txt"},{"from":"IETF RFC 2154","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2154/RFC-2154.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2181","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2181/RFC-2181.txt"},{"from":"IETF RFC 2196","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2196/RFC-2196.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2230","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2230/RFC-2230.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2308","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2308/RFC-2308.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2412","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2412/RFC-2412.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2673","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2673/RFC-2673.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 2065","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2066","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 2067","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 2067","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2067","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2068","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2069","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2069/RFC-2069.txt"},{"from":"IETF RFC 2070","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2109","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2109/RFC-2109.txt"},{"from":"IETF RFC 2122","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2145","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2145/RFC-2145.txt"},{"from":"IETF RFC 2169","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2169/RFC-2169.txt"},{"from":"IETF RFC 2186","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2186/RFC-2186.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2194","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2194/RFC-2194.txt"},{"from":"IETF RFC 2227","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2227/RFC-2227.txt"},{"from":"IETF RFC 2291","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2295","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 2296","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2296/RFC-2296.txt"},{"from":"IETF RFC 2310","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2310/RFC-2310.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2371","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2371/RFC-2371.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2560","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2585","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2585/RFC-2585.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2068","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2069","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2310","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2310/RFC-2310.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2482","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2070","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2072","to":"IETF RFC 2071","kind":"references","source":"IETF/RFC-2072/RFC-2072.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2071","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2071","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2071","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 2071","to":"IETF RFC 2072","kind":"references","source":"IETF/RFC-2071/RFC-2071.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2072","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2072","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2072","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2072","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 2073","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2073","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2074","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2074","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2074","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2074","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2074","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2075","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2076","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2077","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2077","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2077","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2203","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2203/RFC-2203.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2478","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2478/RFC-2478.txt"},{"from":"IETF RFC 2479","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2479/RFC-2479.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2078","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2079","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2079","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2079","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2079","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2546","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-2546/RFC-2546.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 2080","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2081","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2082","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2453","to":"IETF RFC 2082","kind":"references","source":"IETF/RFC-2453/RFC-2453.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2082","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 2082","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2082","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2084","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2084","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2202","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-2202/RFC-2202.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2286","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-2286/RFC-2286.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2085","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 3503","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-3503/RFC-3503.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 2086","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2087","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 2087","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 2087","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 2087","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2087","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 2088","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 2257","to":"IETF RFC 2089","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2089","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2089","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2089","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2090","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2091","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2627","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-2627/RFC-2627.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2093","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2627","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-2627/RFC-2627.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2094","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 2945","to":"IETF RFC 2095","kind":"references","source":"IETF/RFC-2945/RFC-2945.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2096","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2096","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2096","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2096","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2097","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2098","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2101","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 2085","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2085/RFC-2085.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2202","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2202/RFC-2202.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2286","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2286/RFC-2286.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2511","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2511/RFC-2511.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2693","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2693/RFC-2693.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2756","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2756/RFC-2756.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2875","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2875/RFC-2875.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2945","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2945/RFC-2945.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3567","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 3967","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-3967/RFC-3967.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4226","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4226/RFC-4226.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4231","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4231/RFC-4231.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4357","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4357/RFC-4357.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4493","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4493/RFC-4493.txt"},{"from":"IETF RFC 4494","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4494/RFC-4494.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4758","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4758/RFC-4758.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5769","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5769/RFC-5769.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 2104","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 2702","to":"IETF RFC 2105","kind":"references","source":"IETF/RFC-2702/RFC-2702.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2107","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 2239","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2108","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 2458","to":"IETF RFC 2109","kind":"references","source":"IETF/RFC-2458/RFC-2458.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2109","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2965","to":"IETF RFC 2109","kind":"references","source":"IETF/RFC-2965/RFC-2965.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 2109","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 2109","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 211","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 300","to":"IETF RFC 211","kind":"references","source":"IETF/RFC-300/RFC-300.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 2110","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2110","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2110","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2110","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2392","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2392/RFC-2392.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2111","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 2112","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 2112","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2112","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2205","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-2205/RFC-2205.txt"},{"from":"IETF RFC 2236","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-2236/RFC-2236.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3208","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3208/RFC-3208.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2113","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2115","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 2117","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2117","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 2117","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 2117","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2118","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 2118","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2118","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"ARF TS03 V1.5.2","to":"IETF RFC 2119","kind":"references","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md"},{"from":"ARF TS07 V0.11","to":"IETF RFC 2119","kind":"references","source":"ARF/TS07-V0.11/TS07-V0.11.md"},{"from":"ARF TS08 V0.11","to":"IETF RFC 2119","kind":"references","source":"ARF/TS08-V0.11/TS08-V0.11.md"},{"from":"ARF TS09 V1.1","to":"IETF RFC 2119","kind":"references","source":"ARF/TS09-V1.1/TS09-V1.1.md"},{"from":"ARF TS10 V1.2","to":"IETF RFC 2119","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 2119","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 2119","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 2119","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 2157","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2180","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2180/RFC-2180.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2193/RFC-2193.txt"},{"from":"IETF RFC 2197","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2197/RFC-2197.txt"},{"from":"IETF RFC 2198","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2198/RFC-2198.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2221","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2221/RFC-2221.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2227","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2227/RFC-2227.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2236","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2236/RFC-2236.txt"},{"from":"IETF RFC 2243","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2243/RFC-2243.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2245","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2245/RFC-2245.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2256","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2281","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2281/RFC-2281.txt"},{"from":"IETF RFC 2284","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2285/RFC-2285.txt"},{"from":"IETF RFC 2290","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2290/RFC-2290.txt"},{"from":"IETF RFC 2295","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2301","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2301/RFC-2301.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2306","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2306/RFC-2306.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2308","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2308/RFC-2308.txt"},{"from":"IETF RFC 2310","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2310/RFC-2310.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2316","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2316/RFC-2316.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2335","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2335/RFC-2335.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2342","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2342/RFC-2342.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2359","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2359/RFC-2359.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2363","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2369","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2369/RFC-2369.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2389","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2389/RFC-2389.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 2419","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2419/RFC-2419.txt"},{"from":"IETF RFC 2420","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2420/RFC-2420.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2422","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 2424","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2424/RFC-2424.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2431","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2431/RFC-2431.txt"},{"from":"IETF RFC 2433","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2433/RFC-2433.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2435","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2435/RFC-2435.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2446","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2446/RFC-2446.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2482","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2511","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2511/RFC-2511.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2526","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2526/RFC-2526.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2546","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2546/RFC-2546.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2559","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2559/RFC-2559.txt"},{"from":"IETF RFC 2560","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2587","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2587/RFC-2587.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2596","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2596/RFC-2596.txt"},{"from":"IETF RFC 2597","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2597/RFC-2597.txt"},{"from":"IETF RFC 2598","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2598/RFC-2598.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2610/RFC-2610.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2615","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2615/RFC-2615.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2631","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2631/RFC-2631.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2644/RFC-2644.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2650","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2650/RFC-2650.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2658","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2658/RFC-2658.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2673","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2673/RFC-2673.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 2696","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2696/RFC-2696.txt"},{"from":"IETF RFC 2702","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2702/RFC-2702.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2711","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2711/RFC-2711.txt"},{"from":"IETF RFC 2715","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2715/RFC-2715.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2717","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2717/RFC-2717.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 2734","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2734/RFC-2734.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2769","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2769/RFC-2769.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2779","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2779/RFC-2779.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2793","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2805","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2809","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2809/RFC-2809.txt"},{"from":"IETF RFC 2810","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2810/RFC-2810.txt"},{"from":"IETF RFC 2811","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2811/RFC-2811.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2833","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2833/RFC-2833.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2836","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2836/RFC-2836.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2855","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2862","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2862/RFC-2862.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2872","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2872/RFC-2872.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2876","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2876/RFC-2876.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 2886","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2886/RFC-2886.txt"},{"from":"IETF RFC 2889","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 2891","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2891/RFC-2891.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 2907","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2907/RFC-2907.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2927","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2927/RFC-2927.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 2937","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2937/RFC-2937.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2961","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2961/RFC-2961.txt"},{"from":"IETF RFC 2965","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2965/RFC-2965.txt"},{"from":"IETF RFC 2971","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2971/RFC-2971.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 2979","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2979/RFC-2979.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2988","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2988/RFC-2988.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3004","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3004/RFC-3004.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3011","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3011/RFC-3011.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3025","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3025/RFC-3025.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3039","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3051","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3051/RFC-3051.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3070","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3070/RFC-3070.txt"},{"from":"IETF RFC 3074","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3074/RFC-3074.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3076","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3114","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3139","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3139/RFC-3139.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3141","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3141/RFC-3141.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3203","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3203/RFC-3203.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3206","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3206/RFC-3206.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3208","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3208/RFC-3208.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3211","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3211/RFC-3211.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3217","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3217/RFC-3217.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3224","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3224/RFC-3224.txt"},{"from":"IETF RFC 3225","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3225/RFC-3225.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3247","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3247/RFC-3247.txt"},{"from":"IETF RFC 3248","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3248/RFC-3248.txt"},{"from":"IETF RFC 3250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3250/RFC-3250.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3262","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3262/RFC-3262.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3274","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3274/RFC-3274.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3309","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3309/RFC-3309.txt"},{"from":"IETF RFC 3310","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3310/RFC-3310.txt"},{"from":"IETF RFC 3311","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3311/RFC-3311.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3325","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3325/RFC-3325.txt"},{"from":"IETF RFC 3326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3326/RFC-3326.txt"},{"from":"IETF RFC 3327","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3327/RFC-3327.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3337","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3347","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3347/RFC-3347.txt"},{"from":"IETF RFC 3348","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3348/RFC-3348.txt"},{"from":"IETF RFC 3351","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3351/RFC-3351.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3357","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3357/RFC-3357.txt"},{"from":"IETF RFC 3358","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3358/RFC-3358.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3362","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3362/RFC-3362.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3368","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3368/RFC-3368.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3373","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3373/RFC-3373.txt"},{"from":"IETF RFC 3375","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3375/RFC-3375.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3386","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3386/RFC-3386.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3389","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3392","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3392/RFC-3392.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3396","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3396/RFC-3396.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3407/RFC-3407.txt"},{"from":"IETF RFC 3408","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3408/RFC-3408.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3420","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3420/RFC-3420.txt"},{"from":"IETF RFC 3421","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3421/RFC-3421.txt"},{"from":"IETF RFC 3423","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3423/RFC-3423.txt"},{"from":"IETF RFC 3425","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3425/RFC-3425.txt"},{"from":"IETF RFC 3427","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3427/RFC-3427.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3431","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3431/RFC-3431.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3438","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3438/RFC-3438.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3445","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3445/RFC-3445.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3448","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3448/RFC-3448.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3454","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3454/RFC-3454.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3457","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3457/RFC-3457.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3463","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3463/RFC-3463.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3477","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3477/RFC-3477.txt"},{"from":"IETF RFC 3478","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3478/RFC-3478.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3486","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3486/RFC-3486.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3491","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3492","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3492/RFC-3492.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3503","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3503/RFC-3503.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3508","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3516","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3516/RFC-3516.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3524","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3524/RFC-3524.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3528","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3528/RFC-3528.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3533","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3533/RFC-3533.txt"},{"from":"IETF RFC 3534","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3534/RFC-3534.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3540","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3540/RFC-3540.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3561","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3561/RFC-3561.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3581","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3581/RFC-3581.txt"},{"from":"IETF RFC 3583","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3583/RFC-3583.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3590/RFC-3590.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3598","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3598/RFC-3598.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3608","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3608/RFC-3608.txt"},{"from":"IETF RFC 3610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3610/RFC-3610.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3626","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3626/RFC-3626.txt"},{"from":"IETF RFC 3629","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3633","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3633/RFC-3633.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3643","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3643/RFC-3643.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3665/RFC-3665.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3674","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3674/RFC-3674.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3683","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3683/RFC-3683.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3685","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3685/RFC-3685.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3688","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3688/RFC-3688.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 3690","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3690/RFC-3690.txt"},{"from":"IETF RFC 3691","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3691/RFC-3691.txt"},{"from":"IETF RFC 3693","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3693/RFC-3693.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3706","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3706/RFC-3706.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3719","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3726","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3726/RFC-3726.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3741","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3741/RFC-3741.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3757","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3757/RFC-3757.txt"},{"from":"IETF RFC 3758","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3758/RFC-3758.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3771","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3771/RFC-3771.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3783","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3783/RFC-3783.txt"},{"from":"IETF RFC 3786","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 3803","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3803/RFC-3803.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3809","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3809/RFC-3809.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 3826","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3826/RFC-3826.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3839","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3839/RFC-3839.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3843","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3843/RFC-3843.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3847","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3857/RFC-3857.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3874","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3874/RFC-3874.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 3894","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3894/RFC-3894.txt"},{"from":"IETF RFC 3898","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3898/RFC-3898.txt"},{"from":"IETF RFC 3902","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3902/RFC-3902.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3936","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3936/RFC-3936.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 3951","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3951/RFC-3951.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3956","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3956/RFC-3956.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 3962","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3962/RFC-3962.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 3969","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3969/RFC-3969.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 3993","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3993/RFC-3993.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4003","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4003/RFC-4003.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4016","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4016/RFC-4016.txt"},{"from":"IETF RFC 4017","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4043","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4049","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4049/RFC-4049.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4056","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4073","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4073/RFC-4073.txt"},{"from":"IETF RFC 4075","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4075/RFC-4075.txt"},{"from":"IETF RFC 4084","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4084/RFC-4084.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4090","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4090/RFC-4090.txt"},{"from":"IETF RFC 4091","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4091/RFC-4091.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4118","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4132","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4137","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4137/RFC-4137.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4139","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4139/RFC-4139.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 4143","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4143/RFC-4143.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4155","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4155/RFC-4155.txt"},{"from":"IETF RFC 4162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 4164","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4164/RFC-4164.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4178","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4178/RFC-4178.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4198","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4226","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4226/RFC-4226.txt"},{"from":"IETF RFC 4231","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4231/RFC-4231.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4242","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4242/RFC-4242.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4245","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4245/RFC-4245.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4258","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4258/RFC-4258.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4262","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4262/RFC-4262.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4311","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4311/RFC-4311.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4315","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4315/RFC-4315.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4331","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4331/RFC-4331.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4345","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4345/RFC-4345.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4349","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4349/RFC-4349.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4357","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4357/RFC-4357.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4361","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4361/RFC-4361.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4376","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4376/RFC-4376.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4378","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4378/RFC-4378.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4401","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4401/RFC-4401.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4419","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4419/RFC-4419.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4427","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4427/RFC-4427.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4437","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4437/RFC-4437.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4449","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4449/RFC-4449.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4470/RFC-4470.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4478","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4478/RFC-4478.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4488","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4488/RFC-4488.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 4491","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4509","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4509/RFC-4509.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4537","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 4564","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4589","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4589/RFC-4589.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4591","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4608","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4608/RFC-4608.txt"},{"from":"IETF RFC 4610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4610/RFC-4610.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4627","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4627/RFC-4627.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4630","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4630/RFC-4630.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4636","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4636/RFC-4636.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4644/RFC-4644.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4649","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4649/RFC-4649.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4657","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4657/RFC-4657.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4667","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4667/RFC-4667.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4674","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4674/RFC-4674.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4680","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4680/RFC-4680.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4694","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4715","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4724","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4724/RFC-4724.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4731","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4731/RFC-4731.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4735","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4735/RFC-4735.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4739","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4739/RFC-4739.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4753","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 4754","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 4756","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4756/RFC-4756.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4759","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4759/RFC-4759.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4766","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4766/RFC-4766.txt"},{"from":"IETF RFC 4771","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4771/RFC-4771.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4781","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4781/RFC-4781.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4785","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4785/RFC-4785.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4806","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4806/RFC-4806.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4820","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4820/RFC-4820.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 4850","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4850/RFC-4850.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4853","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4853/RFC-4853.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4863","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4863/RFC-4863.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4904","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4904/RFC-4904.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4909","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4909/RFC-4909.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4946","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4946/RFC-4946.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4955","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4955/RFC-4955.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4967","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4967/RFC-4967.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 4986","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4986/RFC-4986.txt"},{"from":"IETF RFC 4991","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4991/RFC-4991.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 4994","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4994/RFC-4994.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5001","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5001/RFC-5001.txt"},{"from":"IETF RFC 5003","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5003/RFC-5003.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5016","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5016/RFC-5016.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5035","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5069","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5069/RFC-5069.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5083/RFC-5083.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5091","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5091/RFC-5091.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5094","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5094/RFC-5094.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5103","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5103/RFC-5103.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5111","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5111/RFC-5111.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5117","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5130","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5137","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5142","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5142/RFC-5142.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5159","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5159/RFC-5159.txt"},{"from":"IETF RFC 5161","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5161/RFC-5161.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5163","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5183","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5183/RFC-5183.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5232","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5232/RFC-5232.txt"},{"from":"IETF RFC 5233","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5233/RFC-5233.txt"},{"from":"IETF RFC 5235","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5235/RFC-5235.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5277","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5277/RFC-5277.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5301","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5301/RFC-5301.txt"},{"from":"IETF RFC 5302","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5303","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5308","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5331","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5331/RFC-5331.txt"},{"from":"IETF RFC 5332","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5332/RFC-5332.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5384","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5384/RFC-5384.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5397","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5397/RFC-5397.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5444","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5450","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5450/RFC-5450.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5469","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5469/RFC-5469.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5480","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 5496","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5496/RFC-5496.txt"},{"from":"IETF RFC 5497","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5497/RFC-5497.txt"},{"from":"IETF RFC 5498","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5498/RFC-5498.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5546","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5546/RFC-5546.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5548","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5554","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5554/RFC-5554.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5560","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5635","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5635/RFC-5635.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5640","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5640/RFC-5640.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5663","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5663/RFC-5663.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 5668","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5668/RFC-5668.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5672/RFC-5672.txt"},{"from":"IETF RFC 5673","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5673/RFC-5673.txt"},{"from":"IETF RFC 5674","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5713","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5713/RFC-5713.txt"},{"from":"IETF RFC 5717","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5717/RFC-5717.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5719","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5719/RFC-5719.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5722","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5722/RFC-5722.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5756","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5756/RFC-5756.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5759","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5759/RFC-5759.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5808","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5808/RFC-5808.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5826","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5861","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5861/RFC-5861.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5867","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5867/RFC-5867.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5903","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5932","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5932/RFC-5932.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5937","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5941","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5964","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5964/RFC-5964.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6019","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6019/RFC-6019.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6085","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6085/RFC-6085.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6165","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6188","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6188/RFC-6188.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6206","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6206/RFC-6206.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6212","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6212/RFC-6212.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6221","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6221/RFC-6221.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6243","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6243/RFC-6243.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6351","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6351/RFC-6351.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 6386","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6386/RFC-6386.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6552","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6552/RFC-6552.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6562","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6562/RFC-6562.txt"},{"from":"IETF RFC 6564","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6564/RFC-6564.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6585","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6585/RFC-6585.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6603","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6603/RFC-6603.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6644/RFC-6644.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6737","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6737/RFC-6737.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6807","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6807/RFC-6807.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6834/RFC-6834.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6839","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 6970","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6970/RFC-6970.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 6985","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6985/RFC-6985.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7009","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7083/RFC-7083.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7164","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7164/RFC-7164.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7283","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7283/RFC-7283.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7335","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7335/RFC-7335.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7366","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7366/RFC-7366.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 7464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7465","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7465/RFC-7465.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7539","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7539/RFC-7539.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7685","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7685/RFC-7685.txt"},{"from":"IETF RFC 7693","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7693/RFC-7693.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7706","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7706/RFC-7706.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 7748","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7748/RFC-7748.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7830","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7830/RFC-7830.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8032","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8032/RFC-8032.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8035","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8035/RFC-8035.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8078","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8078/RFC-8078.txt"},{"from":"IETF RFC 8081","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8081/RFC-8081.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8174","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8174/RFC-8174.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8235","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8235/RFC-8235.txt"},{"from":"IETF RFC 8246","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8246/RFC-8246.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8297","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8297/RFC-8297.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8391","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8391/RFC-8391.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8746","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8937","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9021","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9021/RFC-9021.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9106","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9106/RFC-9106.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9285","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 2119","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 2119","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"IETF RFC 2119","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 2119","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 3795","to":"IETF RFC 2120","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2122","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2123","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2125","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2125","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2125","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2556","to":"IETF RFC 2126","kind":"references","source":"IETF/RFC-2556/RFC-2556.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2126","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2126","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2127","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2127","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2127","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2127","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2127","to":"IETF RFC 2128","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2128","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2482","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3375","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-3375/RFC-3375.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 2130","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2165","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2489","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2489/RFC-2489.txt"},{"from":"IETF RFC 2610","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2610/RFC-2610.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2855","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2937","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2937/RFC-2937.txt"},{"from":"IETF RFC 2939","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-2939/RFC-2939.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3004","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3004/RFC-3004.txt"},{"from":"IETF RFC 3011","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3011/RFC-3011.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3074","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3074/RFC-3074.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3203","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3203/RFC-3203.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3396","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3396/RFC-3396.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 3993","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-3993/RFC-3993.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4361","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4361/RFC-4361.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 4580","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4580/RFC-4580.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 2131","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2489","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2489/RFC-2489.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2855","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 2937","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2937/RFC-2937.txt"},{"from":"IETF RFC 2939","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-2939/RFC-2939.txt"},{"from":"IETF RFC 3004","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3004/RFC-3004.txt"},{"from":"IETF RFC 3011","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3011/RFC-3011.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3396","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3396/RFC-3396.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3898","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3898/RFC-3898.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4075","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4075/RFC-4075.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4361","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4361/RFC-4361.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6355","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6355/RFC-6355.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 2132","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 2292","to":"IETF RFC 2133","kind":"references","source":"IETF/RFC-2292/RFC-2292.txt"},{"from":"IETF RFC 2553","to":"IETF RFC 2133","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2133","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2133","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 2137","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2137/RFC-2137.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5158","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5158/RFC-5158.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 2136","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2136","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2136/RFC-2136.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2137","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 2139","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2139/RFC-2139.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2809","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2809/RFC-2809.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2138","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2139","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2140","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2169","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2169/RFC-2169.txt"},{"from":"IETF RFC 2276","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2276/RFC-2276.txt"},{"from":"IETF RFC 2288","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2288/RFC-2288.txt"},{"from":"IETF RFC 2371","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2371/RFC-2371.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2648","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2648/RFC-2648.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 3001","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3001/RFC-3001.txt"},{"from":"IETF RFC 3043","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3043/RFC-3043.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3061","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3061/RFC-3061.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3085","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3085/RFC-3085.txt"},{"from":"IETF RFC 3120","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3120/RFC-3120.txt"},{"from":"IETF RFC 3121","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3121/RFC-3121.txt"},{"from":"IETF RFC 3151","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3151/RFC-3151.txt"},{"from":"IETF RFC 3187","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3187/RFC-3187.txt"},{"from":"IETF RFC 3188","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3188/RFC-3188.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4122","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4179","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4179/RFC-4179.txt"},{"from":"IETF RFC 4195","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4195/RFC-4195.txt"},{"from":"IETF RFC 4198","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4854","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4854/RFC-4854.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 6288","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-6288/RFC-6288.txt"},{"from":"IETF RFC 6755","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-6755/RFC-6755.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 2141","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 2369","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-2369/RFC-2369.txt"},{"from":"IETF RFC 2489","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-2489/RFC-2489.txt"},{"from":"IETF RFC 2635","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-2635/RFC-2635.txt"},{"from":"IETF RFC 2939","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-2939/RFC-2939.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 2142","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2143","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2612","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-2612/RFC-2612.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2144","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2145","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2145","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2145","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2145","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 2147","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2151","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2151","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2151","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2152","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 2153","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 2153","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 2153","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 2153","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 2153","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 3567","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 2154","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 2162","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2294","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2156","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 2157","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 2157","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2157","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2157","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 2157","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 2158","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2158","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2159","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 216","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 2160","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2160","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 2161","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2161","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 2162","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2162","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 2163","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2163","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2163","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 2163","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 2164","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2294","to":"IETF RFC 2164","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2164","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2164","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2610","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-2610/RFC-2610.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2165","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2167","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2167","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 2167","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 2169","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-2169/RFC-2169.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2168","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4198","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2169","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 2174","to":"IETF RFC 2171","kind":"references","source":"IETF/RFC-2174/RFC-2174.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 2171","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2171","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 2171","to":"IETF RFC 2172","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2174","to":"IETF RFC 2172","kind":"references","source":"IETF/RFC-2174/RFC-2174.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 2172","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 2171","to":"IETF RFC 2173","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2174","to":"IETF RFC 2173","kind":"references","source":"IETF/RFC-2174/RFC-2174.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 2173","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2173","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 2171","to":"IETF RFC 2174","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 2174","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2175","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 2171","to":"IETF RFC 2176","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2175","to":"IETF RFC 2176","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2176","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2177","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 2178","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 2178","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2179","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2179","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2180","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2182","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2182/RFC-2182.txt"},{"from":"IETF RFC 2308","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2308/RFC-2308.txt"},{"from":"IETF RFC 2317","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2317/RFC-2317.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2763","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2763/RFC-2763.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5301","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5301/RFC-5301.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 2181","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 3258","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-3258/RFC-3258.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 2182","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2183","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2278","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2184","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2185","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2187","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-2187/RFC-2187.txt"},{"from":"IETF RFC 2227","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-2227/RFC-2227.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2756","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-2756/RFC-2756.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3143","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-3143/RFC-3143.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2186","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 2186","to":"IETF RFC 2187","kind":"references","source":"IETF/RFC-2186/RFC-2186.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 2187","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2188","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 2715","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-2715/RFC-2715.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 2189","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 2429","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-2429/RFC-2429.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 2190","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 2193","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-2193/RFC-2193.txt"},{"from":"IETF RFC 2221","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-2221/RFC-2221.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2342","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-2342/RFC-2342.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2192","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 3348","to":"IETF RFC 2193","kind":"references","source":"IETF/RFC-3348/RFC-3348.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2193","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 2193","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2193","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2194","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2195","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 2350","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-2350/RFC-2350.txt"},{"from":"IETF RFC 2504","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-2504/RFC-2504.txt"},{"from":"IETF RFC 2635","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-2635/RFC-2635.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2196","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 2197","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2197","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 2197","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 2197","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 2354","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-2354/RFC-2354.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 2736","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-2736/RFC-2736.txt"},{"from":"IETF RFC 2793","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2833","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-2833/RFC-2833.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4756","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4756/RFC-4756.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 2198","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 2223","to":"IETF RFC 2200","kind":"references","source":"IETF/RFC-2223/RFC-2223.txt"},{"from":"IETF RFC 2629","to":"IETF RFC 2200","kind":"references","source":"IETF/RFC-2629/RFC-2629.txt"},{"from":"IETF RFC 2189","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-2189/RFC-2189.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 2201","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 2286","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2286/RFC-2286.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2511","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2511/RFC-2511.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4231","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-4231/RFC-4231.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 2202","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2755","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2755/RFC-2755.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 2203","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 2204","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 2207","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2207/RFC-2207.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2209","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2209/RFC-2209.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2211","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2211/RFC-2211.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2430","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2430/RFC-2430.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2638","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2638/RFC-2638.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2711","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2711/RFC-2711.txt"},{"from":"IETF RFC 2745","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2745/RFC-2745.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2749","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2749/RFC-2749.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2872","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2872/RFC-2872.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2961","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2961/RFC-2961.txt"},{"from":"IETF RFC 2996","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2996/RFC-2996.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3139","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3139/RFC-3139.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3210","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3210/RFC-3210.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3469","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3469/RFC-3469.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3524","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3524/RFC-3524.txt"},{"from":"IETF RFC 3583","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3583/RFC-3583.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3726","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3726/RFC-3726.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3936","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3936/RFC-3936.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4090","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4090/RFC-4090.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 2205","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2206","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2206","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2206","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2206","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2205","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-2205/RFC-2205.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2209","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-2209/RFC-2209.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3936","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-3936/RFC-3936.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2207","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2208","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2208","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2208","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2208","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2208","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 2207","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-2207/RFC-2207.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2209","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 221","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2205","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2205/RFC-2205.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2211","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2211/RFC-2211.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2210","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2638","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2638/RFC-2638.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2211","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 2208","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2208/RFC-2208.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2638","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2638/RFC-2638.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2212","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2213","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2213","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2213","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2213","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2214","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2211","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2211/RFC-2211.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2216","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2216/RFC-2216.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2215","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 2210","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2210/RFC-2210.txt"},{"from":"IETF RFC 2211","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2211/RFC-2211.txt"},{"from":"IETF RFC 2212","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2212/RFC-2212.txt"},{"from":"IETF RFC 2215","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2215/RFC-2215.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2216","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2217","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2218","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2219","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2221","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 2221","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2245","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2245/RFC-2245.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2222","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 2222","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2222/RFC-2222.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2400","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 2436","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2436/RFC-2436.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2629","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2629/RFC-2629.txt"},{"from":"IETF RFC 2717","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2717/RFC-2717.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3131","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3131/RFC-3131.txt"},{"from":"IETF RFC 3285","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3285/RFC-3285.txt"},{"from":"IETF RFC 3327","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3327/RFC-3327.txt"},{"from":"IETF RFC 3356","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3356/RFC-3356.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3608","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3608/RFC-3608.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6949","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-6949/RFC-6949.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 2223","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2224","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2224","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2224","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2224","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2337","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2337/RFC-2337.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2601","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2601/RFC-2601.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2225","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2226","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2227","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2227","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 2773","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-2773/RFC-2773.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2228","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2230","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 2388","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-2388/RFC-2388.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2231","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2232","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2320","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2320/RFC-2320.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2233","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2245","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2245/RFC-2245.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2342","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2342/RFC-2342.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2389","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2389/RFC-2389.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2648","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2648/RFC-2648.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2673","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2673/RFC-2673.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2738","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2738/RFC-2738.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3081","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3081/RFC-3081.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3085","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3085/RFC-3085.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3325","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3325/RFC-3325.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3348","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3348/RFC-3348.txt"},{"from":"IETF RFC 3368","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3368/RFC-3368.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3420","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3420/RFC-3420.txt"},{"from":"IETF RFC 3421","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3421/RFC-3421.txt"},{"from":"IETF RFC 3431","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3431/RFC-3431.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3508","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3516","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3516/RFC-3516.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3629","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3691","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3691/RFC-3691.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4122","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4179","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4179/RFC-4179.txt"},{"from":"IETF RFC 4180","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4180/RFC-4180.txt"},{"from":"IETF RFC 4234","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4234/RFC-4234.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 2234","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2235","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2362","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-2362/RFC-2362.txt"},{"from":"IETF RFC 2435","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-2435/RFC-2435.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2715","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-2715/RFC-2715.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3228","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3228/RFC-3228.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 2236","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2238","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2239","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2239","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2239","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2240","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2241","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2242","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2243","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2243","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2243","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2243","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3431","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3431/RFC-3431.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3685","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3685/RFC-3685.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2244","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2244","to":"IETF RFC 2245","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2245","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2245","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 2245","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2246","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2487","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2628","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2628/RFC-2628.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2712","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2712/RFC-2712.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2719","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3078","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3078/RFC-3078.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3268","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3268/RFC-3268.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3423","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3423/RFC-3423.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4082","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4082/RFC-4082.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4132","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4162","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4297","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4357","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4357/RFC-4357.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4680","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4680/RFC-4680.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5469","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5469/RFC-5469.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7465","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7465/RFC-7465.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 2246","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 3039","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2247","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 2248","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2248","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2248","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2248","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2249","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2343","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-2343/RFC-2343.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2250","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2589","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2589/RFC-2589.txt"},{"from":"IETF RFC 2596","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2596/RFC-2596.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2696","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2696/RFC-2696.txt"},{"from":"IETF RFC 2739","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2739/RFC-2739.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2891","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2891/RFC-2891.txt"},{"from":"IETF RFC 2927","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2927/RFC-2927.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3771","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3771/RFC-3771.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2251","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2256","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2589","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2589/RFC-2589.txt"},{"from":"IETF RFC 2596","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2596/RFC-2596.txt"},{"from":"IETF RFC 2657","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2657/RFC-2657.txt"},{"from":"IETF RFC 2739","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2739/RFC-2739.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2927","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2927/RFC-2927.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3674","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3674/RFC-3674.txt"},{"from":"IETF RFC 3698","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3771","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3771/RFC-3771.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 2252","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 2247","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2247/RFC-2247.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2589","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2589/RFC-2589.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 2253","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 2255","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-2255/RFC-2255.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 2254","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 2251","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 2255","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 2247","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2247/RFC-2247.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 2256","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2257","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2257","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 226","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 289","to":"IETF RFC 226","kind":"references","source":"IETF/RFC-289/RFC-289.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2260","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2260","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3704","to":"IETF RFC 2260","kind":"references","source":"IETF/RFC-3704/RFC-3704.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 2260","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 2260","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2261","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 2261","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 2261","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 2261","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2261","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2262","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 2262","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2264","to":"IETF RFC 2262","kind":"references","source":"IETF/RFC-2264/RFC-2264.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 2262","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2262","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2263","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2263","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 2263","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2264","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2264","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2265","to":"IETF RFC 2264","kind":"references","source":"IETF/RFC-2265/RFC-2265.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2264","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2261","to":"IETF RFC 2265","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2262","to":"IETF RFC 2265","kind":"references","source":"IETF/RFC-2262/RFC-2262.txt"},{"from":"IETF RFC 2263","to":"IETF RFC 2265","kind":"references","source":"IETF/RFC-2263/RFC-2263.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 2265","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2266","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2344","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-2344/RFC-2344.txt"},{"from":"IETF RFC 2644","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-2644/RFC-2644.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2267","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 3217","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-3217/RFC-3217.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2268","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2271","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2274","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2274/RFC-2274.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2272","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2273","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2275","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2275/RFC-2275.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2274","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 2271","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2272","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2272/RFC-2272.txt"},{"from":"IETF RFC 2273","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2273/RFC-2273.txt"},{"from":"IETF RFC 2358","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2275","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 2276","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 2291","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3375","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3375/RFC-3375.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4766","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4766/RFC-4766.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5001","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5001/RFC-5001.txt"},{"from":"IETF RFC 5137","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2277","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2279","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2278","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 2277","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2376","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2384","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2610","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2610/RFC-2610.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2718","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2718/RFC-2718.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2793","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2898","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2965","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-2965/RFC-2965.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3076","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3508","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3629","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4630","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-4630/RFC-4630.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 2279","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 2280","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2280","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 2280","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2280","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 2281","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2281","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2281","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 2418","to":"IETF RFC 2282","kind":"references","source":"IETF/RFC-2418/RFC-2418.txt"},{"from":"IETF RFC 2727","to":"IETF RFC 2282","kind":"references","source":"IETF/RFC-2727/RFC-2727.txt"},{"from":"IETF RFC 2850","to":"IETF RFC 2282","kind":"references","source":"IETF/RFC-2850/RFC-2850.txt"},{"from":"IETF RFC 3777","to":"IETF RFC 2282","kind":"references","source":"IETF/RFC-3777/RFC-3777.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2546","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2546/RFC-2546.txt"},{"from":"IETF RFC 2547","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2547/RFC-2547.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 2283","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2484","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 2809","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2809/RFC-2809.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3374","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2284","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 2432","to":"IETF RFC 2285","kind":"references","source":"IETF/RFC-2432/RFC-2432.txt"},{"from":"IETF RFC 2647","to":"IETF RFC 2285","kind":"references","source":"IETF/RFC-2647/RFC-2647.txt"},{"from":"IETF RFC 2889","to":"IETF RFC 2285","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 2285","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2285","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2286","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2287","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2288","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2288","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3187","to":"IETF RFC 2288","kind":"references","source":"IETF/RFC-3187/RFC-3187.txt"},{"from":"IETF RFC 3188","to":"IETF RFC 2288","kind":"references","source":"IETF/RFC-3188/RFC-3188.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2288","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 2444","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2289","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 229","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2290","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2291","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2291","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 2553","to":"IETF RFC 2292","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2292","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 3542","to":"IETF RFC 2292","kind":"references","source":"IETF/RFC-3542/RFC-3542.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2293","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2293","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2294","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2296","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2296/RFC-2296.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2295","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2295","to":"IETF RFC 2296","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2296","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 2297","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2542","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2542/RFC-2542.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3503","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3503/RFC-3503.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2298","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 2302","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2302/RFC-2302.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3250","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-3250/RFC-3250.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 2301","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 2301","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-2301/RFC-2301.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2306","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-2306/RFC-2306.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2302","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 2303","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2303","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2303","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2303","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2303","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 2304","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2304","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2304","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2304","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2304","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2542","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-2542/RFC-2542.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2305","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 2301","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-2301/RFC-2301.txt"},{"from":"IETF RFC 2302","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-2302/RFC-2302.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2306","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2307","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2307","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2307","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 2308","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2638","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2638/RFC-2638.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 2309","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2310","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2311","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2312","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2313","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2311","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2437","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2437/RFC-2437.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 3218","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3218/RFC-3218.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4056","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2313","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2311","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2875","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-2875/RFC-2875.txt"},{"from":"IETF RFC 2986","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2314","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 2315","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"IETF RFC 2311","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2311/RFC-2311.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3713","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3713/RFC-3713.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2315","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3238","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-3238/RFC-3238.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2316","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2317","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2317","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 2317","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2317","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 2317","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 2320","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2320","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2320","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2322","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2323","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2323","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2324","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2324","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2324","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2324","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2324","to":"IETF RFC 2325","kind":"references","source":"IETF/RFC-2324/RFC-2324.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2325","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3466","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3466/RFC-3466.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 2326","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 2771","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2771/RFC-2771.txt"},{"from":"IETF RFC 2833","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2833/RFC-2833.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 3009","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3009/RFC-3009.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3047","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3048","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3048/RFC-3048.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3362","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3362/RFC-3362.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3389","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3524","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3524/RFC-3524.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3556","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3556/RFC-3556.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4091","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4091/RFC-4091.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2327","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 2329","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2329/RFC-2329.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2338","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2367","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2367/RFC-2367.txt"},{"from":"IETF RFC 2370","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2370/RFC-2370.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2991","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-2991/RFC-2991.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 3137","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3137/RFC-3137.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3509","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3509/RFC-3509.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4136","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4136/RFC-4136.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4222","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4222/RFC-4222.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4811","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4811/RFC-4811.txt"},{"from":"IETF RFC 4812","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4812/RFC-4812.txt"},{"from":"IETF RFC 4813","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4813/RFC-4813.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5243","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5243/RFC-5243.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2328","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 2329","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 2678","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2678/RFC-2678.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3357","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3357/RFC-3357.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3763","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-3763/RFC-3763.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5136","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5136/RFC-5136.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5560","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 2330","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2331","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2331","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2331","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 2331","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2331","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2331","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2335","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2335/RFC-2335.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2603","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2603/RFC-2603.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 2332","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2333","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 2334","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2335","to":"IETF RFC 2334","kind":"references","source":"IETF/RFC-2335/RFC-2335.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 2334","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2334","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2334","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2334","to":"IETF RFC 2335","kind":"references","source":"IETF/RFC-2334/RFC-2334.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2335","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2335","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2337","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2337","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2338","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2338","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2338","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2338","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 2339","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 2339","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 2339","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2341","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2342","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2343","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2343","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2827","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-2827/RFC-2827.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3025","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-3025/RFC-3025.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 2344","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2345","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 2346","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 2346","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 2348","to":"IETF RFC 2347","kind":"references","source":"IETF/RFC-2348/RFC-2348.txt"},{"from":"IETF RFC 2349","to":"IETF RFC 2347","kind":"references","source":"IETF/RFC-2349/RFC-2349.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2347","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 3218","to":"IETF RFC 2347","kind":"references","source":"IETF/RFC-3218/RFC-3218.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2347","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2347","to":"IETF RFC 2348","kind":"references","source":"IETF/RFC-2347/RFC-2347.txt"},{"from":"IETF RFC 3347","to":"IETF RFC 2348","kind":"references","source":"IETF/RFC-3347/RFC-3347.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2348","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2347","to":"IETF RFC 2349","kind":"references","source":"IETF/RFC-2347/RFC-2347.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2349","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 2349","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 235","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 240","to":"IETF RFC 235","kind":"references","source":"IETF/RFC-240/RFC-240.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2350","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2350","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2350","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2733","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-2733/RFC-2733.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 2354","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2355","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2355","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3025","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3025/RFC-3025.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2356","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3048","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3048/RFC-3048.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2357","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 2358","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2358","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2358","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2358","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2359","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2359","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4315","to":"IETF RFC 2359","kind":"references","source":"IETF/RFC-4315/RFC-4315.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 2360","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 2365","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2365/RFC-2365.txt"},{"from":"IETF RFC 2715","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2715/RFC-2715.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2991","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2991/RFC-2991.txt"},{"from":"IETF RFC 2992","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-2992/RFC-2992.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2362","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2363","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2363","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 2516","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2364","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2588","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2588/RFC-2588.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2770","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2770/RFC-2770.txt"},{"from":"IETF RFC 2771","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2771/RFC-2771.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2907","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2907/RFC-2907.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2365","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2367","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"ETSI TS 119 602 V1.1.1","to":"IETF RFC 2368","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 2368","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2369","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-2369/RFC-2369.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5546","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-5546/RFC-5546.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2368","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 2369","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 3101","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-3101/RFC-3101.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2370","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 2372","to":"IETF RFC 2371","kind":"references","source":"IETF/RFC-2372/RFC-2372.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2371","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2371","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2371","to":"IETF RFC 2372","kind":"references","source":"IETF/RFC-2371/RFC-2371.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2372","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2374","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2374/RFC-2374.txt"},{"from":"IETF RFC 2375","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2375/RFC-2375.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2526","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2526/RFC-2526.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2546","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2546/RFC-2546.txt"},{"from":"IETF RFC 2553","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2723","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2723/RFC-2723.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2732","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2732/RFC-2732.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2373","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 2770","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2770/RFC-2770.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3587","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3587/RFC-3587.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 2374","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 2373","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-2373/RFC-2373.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2375","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2376","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2377","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2379","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2379","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2379","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2379","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 238","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 238","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2380","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2380","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2380","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2380","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2380","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2381","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2379","to":"IETF RFC 2382","kind":"references","source":"IETF/RFC-2379/RFC-2379.txt"},{"from":"IETF RFC 2380","to":"IETF RFC 2382","kind":"references","source":"IETF/RFC-2380/RFC-2380.txt"},{"from":"IETF RFC 2381","to":"IETF RFC 2382","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 2382","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2384","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2384","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 2384","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2796","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-2796/RFC-2796.txt"},{"from":"IETF RFC 2842","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-2842/RFC-2842.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 3392","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3392/RFC-3392.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4724","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4724/RFC-4724.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4781","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4781/RFC-4781.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2385","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2382","to":"IETF RFC 2386","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2702","to":"IETF RFC 2386","kind":"references","source":"IETF/RFC-2702/RFC-2702.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2386","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2386","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 2392","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-2392/RFC-2392.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2387","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 2388","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 2389","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 2389","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2389","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2389","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2390","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 2392","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 2394","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2394/RFC-2394.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3051","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-3051/RFC-3051.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2393","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2394","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 3051","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-3051/RFC-3051.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2395","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 2396","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"IETF RFC 2397","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2397/RFC-2397.txt"},{"from":"IETF RFC 2483","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2483/RFC-2483.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2617","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2629","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2629/RFC-2629.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2717","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2717/RFC-2717.txt"},{"from":"IETF RFC 2718","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2718/RFC-2718.txt"},{"from":"IETF RFC 2732","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2732/RFC-2732.txt"},{"from":"IETF RFC 2756","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2756/RFC-2756.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2803","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2803/RFC-2803.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2807","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2807/RFC-2807.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 2965","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-2965/RFC-2965.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3076","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3151","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3151/RFC-3151.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3296","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3296/RFC-3296.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3368","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3368/RFC-3368.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3688","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3688/RFC-3688.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3741","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3741/RFC-3741.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3902","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3902/RFC-3902.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5781","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-5781/RFC-5781.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 2396","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 2397","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 2397","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"IETF RFC 3795","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 2397","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 2397","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 2397","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 4614","to":"IETF RFC 2398","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2398","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 240","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2400","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2412","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2412/RFC-2412.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2477","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2477/RFC-2477.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2547","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2547/RFC-2547.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2624","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2628","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2628/RFC-2628.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2719","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3129","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3129/RFC-3129.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3238","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3238/RFC-3238.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3374","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3386","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3386/RFC-3386.txt"},{"from":"IETF RFC 3423","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3423/RFC-3423.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3457","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3457/RFC-3457.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3706","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3706/RFC-3706.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4297","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2401","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2412","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2412/RFC-2412.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3756","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3756/RFC-3756.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2402","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3446","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3446/RFC-3446.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2403","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 2404","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 2405","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2412","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2412/RFC-2412.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3610","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3610/RFC-3610.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2406","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2394","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2394/RFC-2394.txt"},{"from":"IETF RFC 2395","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2395/RFC-2395.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3051","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3051/RFC-3051.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2407","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2628","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2628/RFC-2628.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2408","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2406","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2406/RFC-2406.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2628","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2628/RFC-2628.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2719","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3051","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3051/RFC-3051.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3129","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3129/RFC-3129.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3457","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3457/RFC-3457.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3526","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3526/RFC-3526.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3586","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3586/RFC-3586.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3706","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3706/RFC-3706.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3766","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3766/RFC-3766.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4753","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 4754","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5903","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2409","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 2410","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2403","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2403/RFC-2403.txt"},{"from":"IETF RFC 2404","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2404/RFC-2404.txt"},{"from":"IETF RFC 2405","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2405/RFC-2405.txt"},{"from":"IETF RFC 2410","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2410/RFC-2410.txt"},{"from":"IETF RFC 2451","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2451/RFC-2451.txt"},{"from":"IETF RFC 2857","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3566","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3566/RFC-3566.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4494","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-4494/RFC-4494.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2411","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2408","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-2408/RFC-2408.txt"},{"from":"IETF RFC 2409","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-2409/RFC-2409.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3526","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-3526/RFC-3526.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2412","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 2518","to":"IETF RFC 2413","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2731","to":"IETF RFC 2413","kind":"references","source":"IETF/RFC-2731/RFC-2731.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2413","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 5013","to":"IETF RFC 2413","kind":"references","source":"IETF/RFC-5013/RFC-5013.txt"},{"from":"IETF RFC 2416","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2416/RFC-2416.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 2414","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2598","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-2598/RFC-2598.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2415","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2416","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2417","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2436","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-2436/RFC-2436.txt"},{"from":"IETF RFC 3131","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3131/RFC-3131.txt"},{"from":"IETF RFC 3356","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3356/RFC-3356.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3683","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3683/RFC-3683.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3934","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3934/RFC-3934.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 5111","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-5111/RFC-5111.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 7282","to":"IETF RFC 2418","kind":"references","source":"IETF/RFC-7282/RFC-7282.txt"},{"from":"IETF RFC 2420","to":"IETF RFC 2419","kind":"references","source":"IETF/RFC-2420/RFC-2420.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 2419","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2419","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2419","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2419","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 2716","to":"IETF RFC 2420","kind":"references","source":"IETF/RFC-2716/RFC-2716.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2420","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2420","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2420","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 2422","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 2424","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-2424/RFC-2424.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 3803","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3803/RFC-3803.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2421","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2422","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2422","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 2422","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2423","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2423","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2423","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2423","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2424","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2424","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3803","to":"IETF RFC 2424","kind":"references","source":"IETF/RFC-3803/RFC-3803.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2424","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2426","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2649","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2649/RFC-2649.txt"},{"from":"IETF RFC 2849","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2849/RFC-2849.txt"},{"from":"IETF RFC 2927","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-2927/RFC-2927.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2425","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2739","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-2739/RFC-2739.txt"},{"from":"IETF RFC 2779","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-2779/RFC-2779.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2426","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2795","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-2795/RFC-2795.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2427","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 2428","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2428","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2428","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2428","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2428","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3839","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3839/RFC-3839.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 2429","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 243","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 290","to":"IETF RFC 243","kind":"references","source":"IETF/RFC-290/RFC-290.txt"},{"from":"IETF RFC 2547","to":"IETF RFC 2430","kind":"references","source":"IETF/RFC-2547/RFC-2547.txt"},{"from":"IETF RFC 2702","to":"IETF RFC 2430","kind":"references","source":"IETF/RFC-2702/RFC-2702.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 2430","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2430","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2431","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2431","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2432","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2432","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 2548","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-2548/RFC-2548.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2433","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2489","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2489/RFC-2489.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2611","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2623","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2623/RFC-2623.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2711","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2711/RFC-2711.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2842","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2842/RFC-2842.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2939","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2939/RFC-2939.txt"},{"from":"IETF RFC 2941","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2941/RFC-2941.txt"},{"from":"IETF RFC 2946","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2946/RFC-2946.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3046","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3046/RFC-3046.txt"},{"from":"IETF RFC 3048","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3048/RFC-3048.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3224","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3224/RFC-3224.txt"},{"from":"IETF RFC 3228","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3228/RFC-3228.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3302","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3302/RFC-3302.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3310","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3310/RFC-3310.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3375","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3375/RFC-3375.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3392","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3392/RFC-3392.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3427","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3427/RFC-3427.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3438","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3438/RFC-3438.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3454","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3454/RFC-3454.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3477","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3477/RFC-3477.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3526","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3526/RFC-3526.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3561","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3561/RFC-3561.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3626","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3626/RFC-3626.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3643","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3643/RFC-3643.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3692","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3692/RFC-3692.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3784","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3818","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3818/RFC-3818.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 3936","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3936/RFC-3936.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 3969","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3969/RFC-3969.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4020","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4020/RFC-4020.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4090","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4090/RFC-4090.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4384","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4384/RFC-4384.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4581","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4581/RFC-4581.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4589","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4589/RFC-4589.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4636","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4636/RFC-4636.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4680","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4680/RFC-4680.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4773","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4773/RFC-4773.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4813","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4813/RFC-4813.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5159","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5159/RFC-5159.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5224","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5224/RFC-5224.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2434","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2435","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2435","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2435","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3356","to":"IETF RFC 2436","kind":"references","source":"IETF/RFC-3356/RFC-3356.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 2436","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2437","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2537","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 2437","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2438","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2439","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 2440","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2441","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2442","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2443","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 2444","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2444","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 2444","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 2446","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-2446/RFC-2446.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2739","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-2739/RFC-2739.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2445","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2446","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 2446","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2446","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2446","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 5546","to":"IETF RFC 2446","kind":"references","source":"IETF/RFC-5546/RFC-5546.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2446","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-2446/RFC-2446.txt"},{"from":"IETF RFC 2739","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-2739/RFC-2739.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2447","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 3206","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-3206/RFC-3206.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2449","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2450","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2928","to":"IETF RFC 2450","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2450","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2450","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 2407","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2411","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-2411/RFC-2411.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3602","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3602/RFC-3602.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 2451","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2452","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2452","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2452","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2452","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2452","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3768","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 2453","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2454","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2454","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2455","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2456","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2457","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2458","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2458","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2459","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 861 V1.4.1","to":"IETF RFC 2459","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 2459","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 2246","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2527","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 2528","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2528/RFC-2528.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2560","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2587","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2587/RFC-2587.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2631","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2631/RFC-2631.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2875","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2875/RFC-2875.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3039","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4043","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 2459","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2526","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2526/RFC-2526.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2553","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2553/RFC-2553.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2711","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2711/RFC-2711.txt"},{"from":"IETF RFC 2730","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3089","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3089/RFC-3089.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3542","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3542/RFC-3542.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3587","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3587/RFC-3587.txt"},{"from":"IETF RFC 3595","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3595/RFC-3595.txt"},{"from":"IETF RFC 3633","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3633/RFC-3633.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 3769","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3769/RFC-3769.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3843","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3843/RFC-3843.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5722","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5722/RFC-5722.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5871","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5871/RFC-5871.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6564","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6564/RFC-6564.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7872","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7872/RFC-7872.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2460","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2469","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2469/RFC-2469.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2545","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2545/RFC-2545.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3590","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3590/RFC-3590.txt"},{"from":"IETF RFC 3627","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3627/RFC-3627.txt"},{"from":"IETF RFC 3633","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3633/RFC-3633.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3756","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3756/RFC-3756.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4076","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4076/RFC-4076.txt"},{"from":"IETF RFC 4135","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4135/RFC-4135.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4311","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4311/RFC-4311.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4554","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4554/RFC-4554.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4943","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4943/RFC-4943.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2461","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2464","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3590","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3590/RFC-3590.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3756","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3756/RFC-3756.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4057","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4057/RFC-4057.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4076","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4076/RFC-4076.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4242","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4242/RFC-4242.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 2462","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2473","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2473/RFC-2473.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2463","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2462","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2462/RFC-2462.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2469","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2469/RFC-2469.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 2497","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2497/RFC-2497.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 6085","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-6085/RFC-6085.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 2464","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2454","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-2454/RFC-2454.txt"},{"from":"IETF RFC 2466","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-2466/RFC-2466.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2465","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 2466","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 2894","to":"IETF RFC 2466","kind":"references","source":"IETF/RFC-2894/RFC-2894.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2466","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2466","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 2450","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-2450/RFC-2450.txt"},{"from":"IETF RFC 2469","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-2469/RFC-2469.txt"},{"from":"IETF RFC 2471","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-2471/RFC-2471.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2467","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2468","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2978","to":"IETF RFC 2468","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 2467","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-2467/RFC-2467.txt"},{"from":"IETF RFC 2470","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-2470/RFC-2470.txt"},{"from":"IETF RFC 2472","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-2472/RFC-2472.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3643","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-3643/RFC-3643.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 2469","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 273","to":"IETF RFC 247","kind":"references","source":"IETF/RFC-273/RFC-273.txt"},{"from":"IETF RFC 289","to":"IETF RFC 247","kind":"references","source":"IETF/RFC-289/RFC-289.txt"},{"from":"IETF RFC 2469","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-2469/RFC-2469.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2470","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 2546","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-2546/RFC-2546.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 2928","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-2928/RFC-2928.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 2471","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 2472","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 7040","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-7040/RFC-7040.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2473","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2597","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2597/RFC-2597.txt"},{"from":"IETF RFC 2598","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2598/RFC-2598.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2676","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2676/RFC-2676.txt"},{"from":"IETF RFC 2697","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2697/RFC-2697.txt"},{"from":"IETF RFC 2698","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2698/RFC-2698.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2836","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2836/RFC-2836.txt"},{"from":"IETF RFC 2859","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2859/RFC-2859.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 2991","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2991/RFC-2991.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3248","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3248/RFC-3248.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3662","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3662/RFC-3662.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3763","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3763/RFC-3763.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4222","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4222/RFC-4222.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5594","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5594/RFC-5594.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 2474","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2597","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2597/RFC-2597.txt"},{"from":"IETF RFC 2598","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2598/RFC-2598.txt"},{"from":"IETF RFC 2697","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2697/RFC-2697.txt"},{"from":"IETF RFC 2698","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2698/RFC-2698.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2836","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2836/RFC-2836.txt"},{"from":"IETF RFC 2859","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2859/RFC-2859.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2902","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2902/RFC-2902.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2963","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2963/RFC-2963.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2996","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2996/RFC-2996.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3248","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3248/RFC-3248.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3662","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3662/RFC-3662.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5594","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5594/RFC-5594.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6789","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-6789/RFC-6789.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 2475","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4084","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-4084/RFC-4084.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2476","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2477","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2478","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2478","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2478","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 2478","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4178","to":"IETF RFC 2478","kind":"references","source":"IETF/RFC-4178/RFC-4178.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2479","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 5126","to":"IETF RFC 2479","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 2480","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2480","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2480","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2480","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2480","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 2736","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2736/RFC-2736.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2481","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2482","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 2482","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2482","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3120","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3120/RFC-3120.txt"},{"from":"IETF RFC 3121","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3121/RFC-3121.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 2483","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 2759","to":"IETF RFC 2484","kind":"references","source":"IETF/RFC-2759/RFC-2759.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2484","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2485","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2607","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2607/RFC-2607.txt"},{"from":"IETF RFC 2794","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2794/RFC-2794.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 2486","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 2595","to":"IETF RFC 2487","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2487","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2487","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2487","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2487","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2488","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 2939","to":"IETF RFC 2489","kind":"references","source":"IETF/RFC-2939/RFC-2939.txt"},{"from":"IETF RFC 3679","to":"IETF RFC 2489","kind":"references","source":"IETF/RFC-3679/RFC-3679.txt"},{"from":"IETF RFC 2492","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-2492/RFC-2492.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2491","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2590","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2492","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2493","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2493","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2493","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2493","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2494","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2493","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-2493/RFC-2493.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2496","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-2496/RFC-2496.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2495","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 2493","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-2493/RFC-2493.txt"},{"from":"IETF RFC 2494","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-2494/RFC-2494.txt"},{"from":"IETF RFC 2495","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2558","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2496","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2497","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2497","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2497","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2497","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 2501","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2502","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 2502","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2504","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2504","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2504","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2505","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 2505","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2505","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 2505","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2505","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2534","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2534/RFC-2534.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 2987","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-2987/RFC-2987.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 2506","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 2508","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2508/RFC-2508.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2507","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2509","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-2509/RFC-2509.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2736","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-2736/RFC-2736.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3096","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3096/RFC-3096.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 2508","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 3006","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3006/RFC-3006.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2509","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2986","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2510","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 2510","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 2511","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2512","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2512","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2512","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2512","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2513","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2513","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2513","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2513","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2512","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 2513","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-2513/RFC-2513.txt"},{"from":"IETF RFC 2515","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-2515/RFC-2515.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2514","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 2514","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-2514/RFC-2514.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2515","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 2516","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4331","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4331/RFC-4331.txt"},{"from":"IETF RFC 4437","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4437/RFC-4437.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 2518","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 252","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2520","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2521","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2521","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2521","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 2522","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2523","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 3143","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-3143/RFC-3143.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2525","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3627","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-3627/RFC-3627.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2526","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2527","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2785","to":"IETF RFC 2527","kind":"references","source":"IETF/RFC-2785/RFC-2785.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2527","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3647","to":"IETF RFC 2527","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 2527","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2528","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2876","to":"IETF RFC 2528","kind":"references","source":"IETF/RFC-2876/RFC-2876.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 2528","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 2529","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2530","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2703","to":"IETF RFC 2530","kind":"references","source":"IETF/RFC-2703/RFC-2703.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2530","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2530","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2530","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2531","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2531","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 4143","to":"IETF RFC 2532","kind":"references","source":"IETF/RFC-4143/RFC-4143.txt"},{"from":"IETF RFC 2530","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2530/RFC-2530.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2738","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2738/RFC-2738.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 2913","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2913/RFC-2913.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 2533","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 2506","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-2506/RFC-2506.txt"},{"from":"IETF RFC 2531","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2533","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-2533/RFC-2533.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2534","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 2536","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2536/RFC-2536.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2539","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2539/RFC-2539.txt"},{"from":"IETF RFC 2540","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2540/RFC-2540.txt"},{"from":"IETF RFC 2541","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2541/RFC-2541.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2826","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2826/RFC-2826.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2870","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2870/RFC-2870.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3225","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3225/RFC-3225.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3445","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3445/RFC-3445.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3757","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3757/RFC-3757.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 2535","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2537","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-2537/RFC-2537.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 2536","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2537","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2536","to":"IETF RFC 2537","kind":"references","source":"IETF/RFC-2536/RFC-2536.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2537","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2537","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2538","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2539","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2539","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2539","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2539","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 308","to":"IETF RFC 254","kind":"references","source":"IETF/RFC-308/RFC-308.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2540","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 2540","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 2535","to":"IETF RFC 2541","kind":"references","source":"IETF/RFC-2535/RFC-2535.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2541","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 2541","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 2542","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2542","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2542","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 2542","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2806","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2824","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2824/RFC-2824.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2976","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-2976/RFC-2976.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3087","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3087/RFC-3087.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3204","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3262","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3262/RFC-3262.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3362","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3362/RFC-3362.txt"},{"from":"IETF RFC 3407","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3407/RFC-3407.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4475","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-4475/RFC-4475.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2543","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 25434","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 2647","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-2647/RFC-2647.txt"},{"from":"IETF RFC 2889","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6985","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-6985/RFC-6985.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2544","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 2545","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 2772","to":"IETF RFC 2546","kind":"references","source":"IETF/RFC-2772/RFC-2772.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 2546","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 4026","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4026/RFC-4026.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 2547","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2548","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 2795","to":"IETF RFC 2550","kind":"references","source":"IETF/RFC-2795/RFC-2795.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2553","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 2554","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 2555","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 2555","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2555","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 2556","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 2557","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2558","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2558","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2558","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 2587","to":"IETF RFC 2559","kind":"references","source":"IETF/RFC-2587/RFC-2587.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 2559","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 2559","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2559","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2559","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 2560","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2560","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 2560","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 2560","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3029","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3647","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4806","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4806/RFC-4806.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 2560","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2561","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2562","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2563","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 2564","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2565","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2566","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2567","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2569","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2569/RFC-2569.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2568","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2569","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2570","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2571","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2572","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2573","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2574","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3053","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3053/RFC-3053.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2575","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2576","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2577","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2572","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2572/RFC-2572.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2579","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2579/RFC-2579.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3595","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3595/RFC-3595.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3826","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3826/RFC-3826.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 2578","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2573","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2573/RFC-2573.txt"},{"from":"IETF RFC 2574","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2574/RFC-2574.txt"},{"from":"IETF RFC 2575","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2575/RFC-2575.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2580","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2580/RFC-2580.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3595","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3595/RFC-3595.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 2579","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 2564","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"IETF RFC 2570","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2570/RFC-2570.txt"},{"from":"IETF RFC 2571","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2576","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2576/RFC-2576.txt"},{"from":"IETF RFC 2578","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2578/RFC-2578.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2613","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2613/RFC-2613.txt"},{"from":"IETF RFC 2618","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2618/RFC-2618.txt"},{"from":"IETF RFC 2619","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2619/RFC-2619.txt"},{"from":"IETF RFC 2620","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2620/RFC-2620.txt"},{"from":"IETF RFC 2621","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2621/RFC-2621.txt"},{"from":"IETF RFC 2662","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 2669","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 2674","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2737","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2737/RFC-2737.txt"},{"from":"IETF RFC 2741","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 2786","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2786/RFC-2786.txt"},{"from":"IETF RFC 2790","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 2837","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2837/RFC-2837.txt"},{"from":"IETF RFC 2851","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2851/RFC-2851.txt"},{"from":"IETF RFC 2856","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2856/RFC-2856.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2932","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2932/RFC-2932.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 2959","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2959/RFC-2959.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3014","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3014/RFC-3014.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3595","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3595/RFC-3595.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2580","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 2582","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2582/RFC-2582.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2861","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2861/RFC-2861.txt"},{"from":"IETF RFC 2883","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2988","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2988/RFC-2988.txt"},{"from":"IETF RFC 2991","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-2991/RFC-2991.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3649","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3649/RFC-3649.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3742","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3742/RFC-3742.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2581","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3649","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3649/RFC-3649.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2582","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2584","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2585","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 3379","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5877","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 2585","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 2586","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2586","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 2586","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2587","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2873","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 2587","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2588","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2588","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 2588","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2589","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2589","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3122","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-3122/RFC-3122.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 2590","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2591","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2591","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 2591","to":"IETF RFC 2592","kind":"references","source":"IETF/RFC-2591/RFC-2591.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2592","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2594","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2594","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2595","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2596","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2596","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 2596","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 2697","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2697/RFC-2697.txt"},{"from":"IETF RFC 2698","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2698/RFC-2698.txt"},{"from":"IETF RFC 2836","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2836/RFC-2836.txt"},{"from":"IETF RFC 2859","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2859/RFC-2859.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2884","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2884/RFC-2884.txt"},{"from":"IETF RFC 2963","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2963/RFC-2963.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 2996","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-2996/RFC-2996.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3662","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3662/RFC-3662.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2597","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3247","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3247/RFC-3247.txt"},{"from":"IETF RFC 3248","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3248/RFC-3248.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 2598","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2600","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2601","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2601","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2602","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2602","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2603","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2603","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2605","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3092","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3092/RFC-3092.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3849","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3849/RFC-3849.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 5233","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5233/RFC-5233.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5398","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5398/RFC-5398.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 2606","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2607","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 2609","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2824","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2824/RFC-2824.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3224","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3224/RFC-3224.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3421","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3421/RFC-3421.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3528","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3528/RFC-3528.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2608","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2614","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3224","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3224/RFC-3224.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 2609","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 2608","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3528","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-3528/RFC-3528.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2610","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3085","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3085/RFC-3085.txt"},{"from":"IETF RFC 3187","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3187/RFC-3187.txt"},{"from":"IETF RFC 3188","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3188/RFC-3188.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 2611","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2612","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2847","to":"IETF RFC 2612","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2612","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2819","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-2819/RFC-2819.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2613","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3049","to":"IETF RFC 2614","kind":"references","source":"IETF/RFC-3049/RFC-3049.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 2614","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2615","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 2616","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 2616","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2617","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2617/RFC-2617.txt"},{"from":"IETF RFC 2639","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2639/RFC-2639.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2756","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2756/RFC-2756.txt"},{"from":"IETF RFC 2781","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2854","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2854/RFC-2854.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2965","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-2965/RFC-2965.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3143","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3143/RFC-3143.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3466","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3466/RFC-3466.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4297","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4437","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4437/RFC-4437.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4758","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4758/RFC-4758.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4850","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4850/RFC-4850.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5397","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5397/RFC-5397.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5861","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5861/RFC-5861.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6585","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6585/RFC-6585.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 2616","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3310","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3310/RFC-3310.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3665","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3665/RFC-3665.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2617","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2618","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2618","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2618","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2619","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2619","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2620","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2621","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 2650","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-2650/RFC-2650.txt"},{"from":"IETF RFC 2769","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-2769/RFC-2769.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4012","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-4012/RFC-4012.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 2622","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 2695","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-2695/RFC-2695.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2623","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2624","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2624","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2624","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2624","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 2625","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2887","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-2887/RFC-2887.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 2627","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2628","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2628","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2817","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3934","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-3934/RFC-3934.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4371","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-4371/RFC-4371.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 2629","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"ETSI TS 101 861 V1.4.1","to":"IETF RFC 2630","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"IETF RFC 2631","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2631/RFC-2631.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2785","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2785/RFC-2785.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2876","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2876/RFC-2876.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3114","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3157","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3157/RFC-3157.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3211","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3211/RFC-3211.txt"},{"from":"IETF RFC 3217","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3217/RFC-3217.txt"},{"from":"IETF RFC 3218","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3218/RFC-3218.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3274","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3274/RFC-3274.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2630","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2785","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2785/RFC-2785.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2875","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-2875/RFC-2875.txt"},{"from":"IETF RFC 3217","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3217/RFC-3217.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 2631","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2632","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2630","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2785","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2785/RFC-2785.txt"},{"from":"IETF RFC 2797","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2797/RFC-2797.txt"},{"from":"IETF RFC 2798","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2798/RFC-2798.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2876","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2876/RFC-2876.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3274","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3274/RFC-3274.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3562","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3562/RFC-3562.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 2633","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 2634","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2634","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 2634","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"IETF RFC 2630","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-2630/RFC-2630.txt"},{"from":"IETF RFC 2633","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-2633/RFC-2633.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 3029","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3114","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3161","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5035","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 2634","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 2635","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2635","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2784","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2784/RFC-2784.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2637","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2638","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2638","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2638","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2638","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2639","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 265","to":"IETF RFC 264","kind":"references","source":"IETF/RFC-265/RFC-265.txt"},{"from":"IETF RFC 354","to":"IETF RFC 264","kind":"references","source":"IETF/RFC-354/RFC-354.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2640","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2640","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2640","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 2644","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2645","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2645","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2645","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2646","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2646","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3803","to":"IETF RFC 2646","kind":"references","source":"IETF/RFC-3803/RFC-3803.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 2647","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 4487","to":"IETF RFC 2647","kind":"references","source":"IETF/RFC-4487/RFC-4487.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2647","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2647","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 3044","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 2648","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2649","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 265","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 265","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 264","to":"IETF RFC 265","kind":"references","source":"IETF/RFC-264/RFC-264.txt"},{"from":"IETF RFC 294","to":"IETF RFC 265","kind":"references","source":"IETF/RFC-294/RFC-294.txt"},{"from":"IETF RFC 959","to":"IETF RFC 265","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2650","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2655","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-2655/RFC-2655.txt"},{"from":"IETF RFC 2657","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-2657/RFC-2657.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2651","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2651","to":"IETF RFC 2652","kind":"references","source":"IETF/RFC-2651/RFC-2651.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2652","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2652","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2651","to":"IETF RFC 2653","kind":"references","source":"IETF/RFC-2651/RFC-2651.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2653","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2653","to":"IETF RFC 2654","kind":"references","source":"IETF/RFC-2653/RFC-2653.txt"},{"from":"IETF RFC 2657","to":"IETF RFC 2654","kind":"references","source":"IETF/RFC-2657/RFC-2657.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2654","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2656","to":"IETF RFC 2655","kind":"references","source":"IETF/RFC-2656/RFC-2656.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2655","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2655","to":"IETF RFC 2656","kind":"references","source":"IETF/RFC-2655/RFC-2655.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2656","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 2657","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2657","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 2658","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 2658","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2658","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 2659","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2659","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 2659","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-2659/RFC-2659.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 2660","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 2667","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2667/RFC-2667.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2809","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2809/RFC-2809.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3017","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3070","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3070/RFC-3070.txt"},{"from":"IETF RFC 3153","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3153/RFC-3153.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3193","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3193/RFC-3193.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3438","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3438/RFC-3438.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4667","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4667/RFC-4667.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2661","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2662","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 2694","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2694/RFC-2694.txt"},{"from":"IETF RFC 2709","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2709/RFC-2709.txt"},{"from":"IETF RFC 2719","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4084","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4084/RFC-4084.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 2663","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 2666","to":"IETF RFC 2665","kind":"references","source":"IETF/RFC-2666/RFC-2666.txt"},{"from":"IETF RFC 2668","to":"IETF RFC 2665","kind":"references","source":"IETF/RFC-2668/RFC-2668.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2665","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2665","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2666","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2666","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2667","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 2665","to":"IETF RFC 2668","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2668","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2668","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 2670","to":"IETF RFC 2669","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2669","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2669","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2669","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2669","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 3083","to":"IETF RFC 2670","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2670","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2670","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2670","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2670","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 2672","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-2672/RFC-2672.txt"},{"from":"IETF RFC 2673","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-2673/RFC-2673.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3110","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3110/RFC-3110.txt"},{"from":"IETF RFC 3225","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3225/RFC-3225.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5001","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5001/RFC-5001.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 2671","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5893","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-5893/RFC-5893.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2672","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 2845","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-2845/RFC-2845.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2673","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2674","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2674","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2674","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 2674","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 3686","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-3686/RFC-3686.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 2675","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 2702","to":"IETF RFC 2676","kind":"references","source":"IETF/RFC-2702/RFC-2702.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2676","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2676","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2677","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 2678","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3763","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-3763/RFC-3763.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2679","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3357","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-3357/RFC-3357.txt"},{"from":"IETF RFC 3763","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-3763/RFC-3763.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5560","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 2680","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 2681","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2683","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 2683","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 2683","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2683","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 2685","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-2685/RFC-2685.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2684","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 2684","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 2685","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2878","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3337","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2686","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 2687","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2689","to":"IETF RFC 2687","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2687","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2687","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2688","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2686","to":"IETF RFC 2689","kind":"references","source":"IETF/RFC-2686/RFC-2686.txt"},{"from":"IETF RFC 2687","to":"IETF RFC 2689","kind":"references","source":"IETF/RFC-2687/RFC-2687.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2689","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3337","to":"IETF RFC 2689","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2689","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3092","to":"IETF RFC 269","kind":"references","source":"IETF/RFC-3092/RFC-3092.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2692","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2692","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2693","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2693","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 2693","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2693","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2694","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 2695","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 2891","to":"IETF RFC 2696","kind":"references","source":"IETF/RFC-2891/RFC-2891.txt"},{"from":"IETF RFC 2698","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-2698/RFC-2698.txt"},{"from":"IETF RFC 2963","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-2963/RFC-2963.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2697","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 2697","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-2697/RFC-2697.txt"},{"from":"IETF RFC 2963","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-2963/RFC-2963.txt"},{"from":"IETF RFC 3086","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-3086/RFC-3086.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2698","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3210","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3210/RFC-3210.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3386","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3386/RFC-3386.txt"},{"from":"IETF RFC 3469","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3469/RFC-3469.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3784","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 2702","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 2938","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-2938/RFC-2938.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2703","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 2792","to":"IETF RFC 2704","kind":"references","source":"IETF/RFC-2792/RFC-2792.txt"},{"from":"IETF RFC 2903","to":"IETF RFC 2704","kind":"references","source":"IETF/RFC-2903/RFC-2903.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 2704","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2704","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 2871","to":"IETF RFC 2705","kind":"references","source":"IETF/RFC-2871/RFC-2871.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2705","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3407","to":"IETF RFC 2705","kind":"references","source":"IETF/RFC-3407/RFC-3407.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2705","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2705","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2709","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 2709","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2709","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2709","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 2711","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-2711/RFC-2711.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 3019","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3019/RFC-3019.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3590","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3590/RFC-3590.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 2710","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 2710","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-2710/RFC-2710.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 2711","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 2712","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2715","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 2715","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2715","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 2715","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 2715","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4017","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2716","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 2718","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-2718/RFC-2718.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3368","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3368/RFC-3368.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 2717","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 2717","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-2717/RFC-2717.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 2718","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 2719","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2719","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 2719","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2719","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2723","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-2723/RFC-2723.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2720","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 2723","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-2723/RFC-2723.txt"},{"from":"IETF RFC 2724","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-2724/RFC-2724.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2722","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2723","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2722","to":"IETF RFC 2724","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2724","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2724","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2726","to":"IETF RFC 2725","kind":"references","source":"IETF/RFC-2726/RFC-2726.txt"},{"from":"IETF RFC 2769","to":"IETF RFC 2725","kind":"references","source":"IETF/RFC-2769/RFC-2769.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2725","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4012","to":"IETF RFC 2725","kind":"references","source":"IETF/RFC-4012/RFC-4012.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 2725","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 2726","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2769","to":"IETF RFC 2726","kind":"references","source":"IETF/RFC-2769/RFC-2769.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2726","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2777","to":"IETF RFC 2727","kind":"references","source":"IETF/RFC-2777/RFC-2777.txt"},{"from":"IETF RFC 3233","to":"IETF RFC 2727","kind":"references","source":"IETF/RFC-3233/RFC-3233.txt"},{"from":"IETF RFC 3677","to":"IETF RFC 2727","kind":"references","source":"IETF/RFC-3677/RFC-3677.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 2727","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3777","to":"IETF RFC 2727","kind":"references","source":"IETF/RFC-3777/RFC-3777.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2728","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2729","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 289","to":"IETF RFC 273","kind":"references","source":"IETF/RFC-289/RFC-289.txt"},{"from":"IETF RFC 2770","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2770/RFC-2770.txt"},{"from":"IETF RFC 2771","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2771/RFC-2771.txt"},{"from":"IETF RFC 2776","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2907","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2907/RFC-2907.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 3082","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3082/RFC-3082.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 2730","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 5013","to":"IETF RFC 2731","kind":"references","source":"IETF/RFC-5013/RFC-5013.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3111","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3266","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3266/RFC-3266.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 2732","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 3009","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3009/RFC-3009.txt"},{"from":"IETF RFC 3016","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3267","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 2733","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 2855","to":"IETF RFC 2734","kind":"references","source":"IETF/RFC-2855/RFC-2855.txt"},{"from":"IETF RFC 3146","to":"IETF RFC 2734","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2734","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 2734","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2735","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 2736","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2737","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2738","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2738","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2739","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2739","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2739","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 2739","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4222","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4222/RFC-4222.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5243","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5243/RFC-5243.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2740","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2741","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2741","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2741","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2742","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 2743","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2744","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-2744/RFC-2744.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4178","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4178/RFC-4178.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4401","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4401/RFC-4401.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5554","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5554/RFC-5554.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2743","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 2743","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4401","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-4401/RFC-4401.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5554","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-5554/RFC-5554.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 2744","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2745","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 2745","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2745","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 2745","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-2745/RFC-2745.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2746","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 2746","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-2746/RFC-2746.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3097","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3097/RFC-3097.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 2747","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 2749","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2749/RFC-2749.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2764","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2764/RFC-2764.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3139","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3139/RFC-3139.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3535","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3535/RFC-3535.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4178","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-4178/RFC-4178.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2748","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3139","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3139/RFC-3139.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2749","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 2749","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-2749/RFC-2749.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2753","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-2753/RFC-2753.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2750","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2751","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2751","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2751","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 2752","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2872","to":"IETF RFC 2752","kind":"references","source":"IETF/RFC-2872/RFC-2872.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2752","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2752","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 2748","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2748/RFC-2748.txt"},{"from":"IETF RFC 2749","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2749/RFC-2749.txt"},{"from":"IETF RFC 2750","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2750/RFC-2750.txt"},{"from":"IETF RFC 2751","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2751/RFC-2751.txt"},{"from":"IETF RFC 2752","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2996","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-2996/RFC-2996.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3084","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3084/RFC-3084.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3181","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3181/RFC-3181.txt"},{"from":"IETF RFC 3182","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2753","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2755","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2755","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 2755","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 2756","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2756","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2756","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2757","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2758","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 2759","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2760","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2762","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2762","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 2762","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 3359","to":"IETF RFC 2763","kind":"references","source":"IETF/RFC-3359/RFC-3359.txt"},{"from":"IETF RFC 5301","to":"IETF RFC 2763","kind":"references","source":"IETF/RFC-5301/RFC-5301.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 4026","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-4026/RFC-4026.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2764","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 2766","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-2766/RFC-2766.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3493","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 2765","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 2766","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2767","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2767","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2767","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 2767","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2769","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 2769","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2769","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2770","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2770","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2770","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2770","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2770","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2771","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2771","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2771","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 2771","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 2772","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2772","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 2772","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 2772","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2773","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2773","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2774","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2774","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2774","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 2775","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 2907","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-2907/RFC-2907.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 2974","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-2974/RFC-2974.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2776","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 2727","to":"IETF RFC 2777","kind":"references","source":"IETF/RFC-2727/RFC-2727.txt"},{"from":"IETF RFC 3777","to":"IETF RFC 2777","kind":"references","source":"IETF/RFC-3777/RFC-3777.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 2777","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 2779","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-2779/RFC-2779.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 2778","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 2779","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3138","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3138/RFC-3138.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3228","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3228/RFC-3228.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3540","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3540/RFC-3540.txt"},{"from":"IETF RFC 3692","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-3692/RFC-3692.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 2780","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 2803","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-2803/RFC-2803.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3076","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 2781","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 2915","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-2915/RFC-2915.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3486","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3486/RFC-3486.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3832","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3832/RFC-3832.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4321","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4321/RFC-4321.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4386","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4386/RFC-4386.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 2782","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 2890","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-2890/RFC-2890.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5640","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5640/RFC-5640.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 2784","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 2785","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2786","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2786","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2787","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2788","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 2788","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2789","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 2790","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2792","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 2792","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2792","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2793","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2793","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 2977","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-2977/RFC-2977.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3012","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3012/RFC-3012.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2794","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 2795","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 3065","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 3345","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-3345/RFC-3345.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4223","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-4223/RFC-4223.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 2796","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 2797","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 2985","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3698","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2798","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 289","to":"IETF RFC 280","kind":"references","source":"IETF/RFC-289/RFC-289.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2801","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2807","to":"IETF RFC 2801","kind":"references","source":"IETF/RFC-2807/RFC-2807.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2801","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 2801","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2801","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2802","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2807","to":"IETF RFC 2802","kind":"references","source":"IETF/RFC-2807/RFC-2807.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 2803","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2802","to":"IETF RFC 2803","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2807","to":"IETF RFC 2803","kind":"references","source":"IETF/RFC-2807/RFC-2807.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2804","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2805","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2886","to":"IETF RFC 2805","kind":"references","source":"IETF/RFC-2886/RFC-2886.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2805","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2805","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 2806","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ARF TS05 V1.2.1","to":"IETF RFC 2806","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"IETF RFC 2916","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 2806","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2807","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2807","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2809","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2809","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2809","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2809","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2809","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 281","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 281","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 2811","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-2811/RFC-2811.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 2810","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 2810","to":"IETF RFC 2811","kind":"references","source":"IETF/RFC-2810/RFC-2810.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 2811","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2811","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2811","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 2811","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 2810","to":"IETF RFC 2812","kind":"references","source":"IETF/RFC-2810/RFC-2810.txt"},{"from":"IETF RFC 2811","to":"IETF RFC 2812","kind":"references","source":"IETF/RFC-2811/RFC-2811.txt"},{"from":"IETF RFC 2813","to":"IETF RFC 2812","kind":"references","source":"IETF/RFC-2813/RFC-2813.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2812","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 2810","to":"IETF RFC 2813","kind":"references","source":"IETF/RFC-2810/RFC-2810.txt"},{"from":"IETF RFC 2811","to":"IETF RFC 2813","kind":"references","source":"IETF/RFC-2811/RFC-2811.txt"},{"from":"IETF RFC 2812","to":"IETF RFC 2813","kind":"references","source":"IETF/RFC-2812/RFC-2812.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2813","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2814","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2814","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2814","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2814","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2814","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2815","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2816","to":"IETF RFC 2815","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2815","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2815","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2814","to":"IETF RFC 2816","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"IETF RFC 2816","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2818","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-2818/RFC-2818.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 3229","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 2817","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 2818","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 2818","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"IETF RFC 2817","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-2817/RFC-2817.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6770","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2818","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2819","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 282","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 493","to":"IETF RFC 282","kind":"references","source":"IETF/RFC-493/RFC-493.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4686","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4686/RFC-4686.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5183","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5183/RFC-5183.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5672","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5672/RFC-5672.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 2821","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3431","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3431/RFC-3431.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3598","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3598/RFC-3598.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4155","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4155/RFC-4155.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4475","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4475/RFC-4475.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4686","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4686/RFC-4686.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4997","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5016","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5016/RFC-5016.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5233","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5233/RFC-5233.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2822","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2823","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 2824","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 2824","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2825","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 2825","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 3026","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-3026/RFC-3026.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 2826","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 3013","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3013/RFC-3013.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3697","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3697/RFC-3697.txt"},{"from":"IETF RFC 3704","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3704/RFC-3704.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4832","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4832/RFC-4832.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8073","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-8073/RFC-8073.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 2827","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 3060","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3365","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-3365/RFC-3365.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4766","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4766/RFC-4766.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2828","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2830","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-2830/RFC-2830.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3894","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-3894/RFC-3894.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2829","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 3062","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3062/RFC-3062.txt"},{"from":"IETF RFC 3088","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3088/RFC-3088.txt"},{"from":"IETF RFC 3377","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3377/RFC-3377.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 2830","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 2831","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2833","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 2834","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2834","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2834","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2835","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 2835","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2836","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3140","to":"IETF RFC 2836","kind":"references","source":"IETF/RFC-3140/RFC-3140.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2836","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2836","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2837","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2837","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2918","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-2918/RFC-2918.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3392","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-3392/RFC-3392.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 2842","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2844","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2874","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-2874/RFC-2874.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5001","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5001/RFC-5001.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 2845","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 2846","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3010","to":"IETF RFC 2847","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 2847","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2847","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 2847","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 2847","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2848","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2849","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2849","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 2849","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 2849","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 2849","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 493","to":"IETF RFC 285","kind":"references","source":"IETF/RFC-493/RFC-493.txt"},{"from":"IETF RFC 3710","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-3710/RFC-3710.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 4052","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-4052/RFC-4052.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4714","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-4714/RFC-4714.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 2850","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3176","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2851","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2852","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 2852","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 2852","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 2852","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2852","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2853","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 2854","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2855","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 2855","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 2856","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2857","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 2857","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 2918","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-2918/RFC-2918.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4724","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4724/RFC-4724.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 2858","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 2963","to":"IETF RFC 2859","kind":"references","source":"IETF/RFC-2963/RFC-2963.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2859","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2859","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2859","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4773","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-4773/RFC-4773.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5736","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-5736/RFC-5736.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2860","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 2861","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2862","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 2862","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 2864","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-2864/RFC-2864.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3273","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3273/RFC-3273.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3371","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3371/RFC-3371.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3535","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3535/RFC-3535.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 2863","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2864","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3423","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3423/RFC-3423.txt"},{"from":"IETF RFC 3457","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3457/RFC-3457.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4017","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 2865","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 2866","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2867","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 2867","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-2867/RFC-2867.txt"},{"from":"IETF RFC 2869","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2881","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-2881/RFC-2881.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 3070","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3070/RFC-3070.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2868","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 2868","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-2868/RFC-2868.txt"},{"from":"IETF RFC 2882","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-2882/RFC-2882.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2869","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 287","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 2870","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 2870","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 3258","to":"IETF RFC 2870","kind":"references","source":"IETF/RFC-3258/RFC-3258.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 2870","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 3219","to":"IETF RFC 2871","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2871","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 2871","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2872","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2872","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2872","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 2873","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2873","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2873","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2873","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 3364","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3364/RFC-3364.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 2874","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2875","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 2875","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 2875","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2875","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 2875","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 2876","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 2876","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 2878","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 2880","to":"IETF RFC 2879","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2879","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2879","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 2879","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 288","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 293","to":"IETF RFC 288","kind":"references","source":"IETF/RFC-293/RFC-293.txt"},{"from":"IETF RFC 2879","to":"IETF RFC 2880","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2881","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 2882","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 2883","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2884","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 2886","to":"IETF RFC 2885","kind":"references","source":"IETF/RFC-2886/RFC-2886.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2885","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 2885","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2885","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 2886","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 2886","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2886","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 3048","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-3048/RFC-3048.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2887","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 2889","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 2889","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 289","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3024","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-3024/RFC-3024.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5640","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-5640/RFC-5640.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 2890","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 2891","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3421","to":"IETF RFC 2891","kind":"references","source":"IETF/RFC-3421/RFC-3421.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2891","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 2956","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-2956/RFC-2956.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3089","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3089/RFC-3089.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2893","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 2894","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 2895","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 2895","to":"IETF RFC 2896","kind":"references","source":"IETF/RFC-2895/RFC-2895.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 2896","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3211","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-3211/RFC-3211.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3962","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-3962/RFC-3962.txt"},{"from":"IETF RFC 4009","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4009/RFC-4009.txt"},{"from":"IETF RFC 4269","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4269/RFC-4269.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 2898","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 290","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2902","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2903","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2903","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2903","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 2903","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2903","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 2903","to":"IETF RFC 2904","kind":"references","source":"IETF/RFC-2903/RFC-2903.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2904","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2904","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2904","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 2904","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 2903","to":"IETF RFC 2905","kind":"references","source":"IETF/RFC-2903/RFC-2903.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2905","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2906","to":"IETF RFC 2905","kind":"references","source":"IETF/RFC-2906/RFC-2906.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2905","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 2903","to":"IETF RFC 2906","kind":"references","source":"IETF/RFC-2903/RFC-2903.txt"},{"from":"IETF RFC 2904","to":"IETF RFC 2906","kind":"references","source":"IETF/RFC-2904/RFC-2904.txt"},{"from":"IETF RFC 2905","to":"IETF RFC 2906","kind":"references","source":"IETF/RFC-2905/RFC-2905.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 2906","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 2907","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2907","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2907","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 2907","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-2907/RFC-2907.txt"},{"from":"IETF RFC 2909","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-2909/RFC-2909.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 2908","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 2908","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-2908/RFC-2908.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2909","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 291","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 2911","to":"IETF RFC 2910","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2910","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2910","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 2910","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 2911","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2911","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2911","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2911","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 2911","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 2912","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2913","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2913","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2913","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3347","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3347/RFC-3347.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 2914","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 2916","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-2916/RFC-2916.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 2915","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 3026","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3026/RFC-3026.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3482","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 2916","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 2918","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 2919","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 2920","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3884","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-3884/RFC-3884.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 2923","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2924","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2924","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 2925","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2925","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 2925","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2925","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 2925","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 2927","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 2928","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4773","to":"IETF RFC 2928","kind":"references","source":"IETF/RFC-4773/RFC-4773.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 2928","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 3597","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-3597/RFC-3597.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4431","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-4431/RFC-4431.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2929","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 293","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 2929","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-2929/RFC-2929.txt"},{"from":"IETF RFC 2931","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-2931/RFC-2931.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3445","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3445/RFC-3445.txt"},{"from":"IETF RFC 3645","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 2930","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 2930","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-2930/RFC-2930.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3445","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3445/RFC-3445.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 2931","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2932","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 2932","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2932","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2933","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2934","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2934","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2935","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 2937","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 2937","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 2937","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 2938","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3548","to":"IETF RFC 2938","kind":"references","source":"IETF/RFC-3548/RFC-3548.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2938","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 2938","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 3679","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-3679/RFC-3679.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 2939","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 294","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 294","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2940","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 2946","to":"IETF RFC 2941","kind":"references","source":"IETF/RFC-2946/RFC-2946.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 2941","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2941","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2942","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2943","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2944","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 2945","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 2941","to":"IETF RFC 2946","kind":"references","source":"IETF/RFC-2941/RFC-2941.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 2946","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2946","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2947","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2948","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2949","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2950","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 2951","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 2955","to":"IETF RFC 2954","kind":"references","source":"IETF/RFC-2955/RFC-2955.txt"},{"from":"IETF RFC 3020","to":"IETF RFC 2954","kind":"references","source":"IETF/RFC-3020/RFC-3020.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2954","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 2954","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 2954","to":"IETF RFC 2955","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2955","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 2955","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 2956","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 2956","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 2957","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2957","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 2957","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 2958","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2958","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2959","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 2959","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 2959","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3309","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3309/RFC-3309.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3423","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3423/RFC-3423.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3554","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3554/RFC-3554.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3758","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3758/RFC-3758.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4296","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4296/RFC-4296.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4820","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4820/RFC-4820.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4838","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4838/RFC-4838.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2960","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 3097","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3097/RFC-3097.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3210","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3210/RFC-3210.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 2961","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2962","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 2962","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 2963","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 2963","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2963","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 3041","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-3041/RFC-3041.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 2965","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 3719","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3784","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 3786","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 5130","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5302","to":"IETF RFC 2966","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2971","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 2972","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 2973","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 2973","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2974","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2975","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 2976","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 2989","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-2989/RFC-2989.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 2977","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 2987","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-2987/RFC-2987.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3629","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 2978","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 2979","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 298","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4644","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-4644/RFC-4644.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 2980","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 2982","to":"IETF RFC 2981","kind":"references","source":"IETF/RFC-2982/RFC-2982.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2981","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 2981","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 2981","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2981","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2981","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-2981/RFC-2981.txt"},{"from":"IETF RFC 3144","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-3144/RFC-3144.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 2982","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 2983","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 2984","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3039","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 2985","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 2986","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 2987","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 2987","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 2987","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3448","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3448/RFC-3448.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3465","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3465/RFC-3465.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 2988","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3127","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-3127/RFC-3127.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 2989","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 2990","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 2992","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-2992/RFC-2992.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4311","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-4311/RFC-4311.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 2991","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 2991","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-2991/RFC-2991.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 2992","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6832","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-6832/RFC-6832.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 2993","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 2998","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-2998/RFC-2998.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 2996","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 2997","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 2997","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 2997","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2997","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 2997","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 2990","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-2990/RFC-2990.txt"},{"from":"IETF RFC 2996","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-2996/RFC-2996.txt"},{"from":"IETF RFC 2997","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-2997/RFC-2997.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3583","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-3583/RFC-3583.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 2998","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 300","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3061","to":"IETF RFC 3001","kind":"references","source":"IETF/RFC-3061/RFC-3061.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 3002","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 3002","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3003","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3004","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3004","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3683","to":"IETF RFC 3005","kind":"references","source":"IETF/RFC-3683/RFC-3683.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3005","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3005","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 3005","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 3006","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3006","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3006","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3008","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3008/RFC-3008.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3445","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3445/RFC-3445.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3756","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3756/RFC-3756.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 3007","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 3007","to":"IETF RFC 3008","kind":"references","source":"IETF/RFC-3007/RFC-3007.txt"},{"from":"IETF RFC 3090","to":"IETF RFC 3008","kind":"references","source":"IETF/RFC-3090/RFC-3090.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 3008","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3008","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3008","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3009","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3009","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 3009","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 3010","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 3010","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3010","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3011","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 3011","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3011","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 3011","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3012","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3013","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 3013","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 3013","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 3013","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4177","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-4177/RFC-4177.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3014","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3108","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3015","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 3016","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3016","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3016","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 3016","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3017","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3017","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3018","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 3019","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3019","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 3019","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 3276","to":"IETF RFC 3020","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3020","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3020","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3021","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 3021","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3021","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 3021","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3021","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3221","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3221/RFC-3221.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7498","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7498/RFC-7498.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 3022","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3236","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3236/RFC-3236.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3902","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3902/RFC-3902.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4267","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4267/RFC-4267.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5941","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6351","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6351/RFC-6351.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6839","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 3023","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 3024","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 3115","to":"IETF RFC 3025","kind":"references","source":"IETF/RFC-3115/RFC-3115.txt"},{"from":"IETF RFC 3152","to":"IETF RFC 3026","kind":"references","source":"IETF/RFC-3152/RFC-3152.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 3026","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3027","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 3431","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3431/RFC-3431.txt"},{"from":"IETF RFC 3598","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3598/RFC-3598.txt"},{"from":"IETF RFC 3685","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3685/RFC-3685.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3894","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-3894/RFC-3894.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3028","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3029","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4134","to":"IETF RFC 3029","kind":"references","source":"IETF/RFC-4134/RFC-4134.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3029","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 3030","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3210","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3210/RFC-3210.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3215","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3215/RFC-3215.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3429","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3429/RFC-3429.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3469","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3469/RFC-3469.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4378","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4378/RFC-4378.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5331","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5331/RFC-5331.txt"},{"from":"IETF RFC 5332","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5332/RFC-5332.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 5693","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5693/RFC-5693.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 3031","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3038","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3038/RFC-3038.txt"},{"from":"IETF RFC 3107","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3107/RFC-3107.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3429","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3429/RFC-3429.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4182","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4182/RFC-4182.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4814","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4814/RFC-4814.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5331","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5331/RFC-5331.txt"},{"from":"IETF RFC 5332","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5332/RFC-5332.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 3032","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 3038","to":"IETF RFC 3033","kind":"references","source":"IETF/RFC-3038/RFC-3038.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3033","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3034","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3215","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3215/RFC-3215.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3035","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 3031","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3031/RFC-3031.txt"},{"from":"IETF RFC 3034","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3037","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3037/RFC-3037.txt"},{"from":"IETF RFC 3038","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3038/RFC-3038.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3215","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3215/RFC-3215.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3478","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3478/RFC-3478.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 3036","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 3036","to":"IETF RFC 3037","kind":"references","source":"IETF/RFC-3036/RFC-3036.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3037","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3037","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3037","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 3038","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3035","to":"IETF RFC 3038","kind":"references","source":"IETF/RFC-3035/RFC-3035.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3038","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3038","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 3039","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3039","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3143","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-3143/RFC-3143.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3238","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-3238/RFC-3238.txt"},{"from":"IETF RFC 3466","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-3466/RFC-3466.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 3040","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 3177","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3177/RFC-3177.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3513","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3513/RFC-3513.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4177","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4177/RFC-4177.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 3041","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 3042","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3043","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3043","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3043","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3044","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3044","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3044","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3044","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 3118","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3118/RFC-3118.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3679","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3679/RFC-3679.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 3993","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-3993/RFC-3993.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4649","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4649/RFC-4649.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4994","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-4994/RFC-4994.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6221","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6221/RFC-6221.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 3046","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 3389","to":"IETF RFC 3047","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3047","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3048","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 3049","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3049","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3050","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3051","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3051","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3051","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3051","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3053","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3055","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3068","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3068/RFC-3068.txt"},{"from":"IETF RFC 3162","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3178","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3178/RFC-3178.txt"},{"from":"IETF RFC 3484","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3484/RFC-3484.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5158","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5158/RFC-5158.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6177","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6177/RFC-6177.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 3056","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3057","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3059","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3059","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 306","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3535","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3535/RFC-3535.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3060","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 3061","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 522-2 V1.2.1","to":"IETF RFC 3061","kind":"references","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf"},{"from":"ETSI EN 319 522-3 V1.2.1","to":"IETF RFC 3061","kind":"references","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3061","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"IETF RFC 3061","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3061","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 3305","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 4050","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-4050/RFC-4050.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3061","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 3112","to":"IETF RFC 3062","kind":"references","source":"IETF/RFC-3112/RFC-3112.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 3062","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3062","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 3062","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3063","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3345","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-3345/RFC-3345.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4223","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-4223/RFC-4223.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 3065","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 3059","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3059/RFC-3059.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3253","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3536","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4645","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5645","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3066","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3068","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 3069","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3069","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3070","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3070","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 3070","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3074","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 3074","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3074","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 3074","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 3076","to":"IETF RFC 3075","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 3075","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3075","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3075","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 3075","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3275","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3741","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-3741/RFC-3741.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3076","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3077","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 3079","to":"IETF RFC 3078","kind":"references","source":"IETF/RFC-3079/RFC-3079.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3078","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3079","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 3079","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 530","to":"IETF RFC 308","kind":"references","source":"IETF/RFC-530/RFC-530.pdf"},{"from":"IETF RFC 3081","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3081/RFC-3081.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 3080","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 3081","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3082","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3082","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 3083","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 3139","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3139/RFC-3139.txt"},{"from":"IETF RFC 3159","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3159/RFC-3159.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3535","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3535/RFC-3535.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3084","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3085","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3662","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-3662/RFC-3662.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 3086","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3087","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3087","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3087","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3087","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3088","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3089","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 4219","to":"IETF RFC 3089","kind":"references","source":"IETF/RFC-4219/RFC-4219.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 3089","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 3089","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 3090","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3757","to":"IETF RFC 3090","kind":"references","source":"IETF/RFC-3757/RFC-3757.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3090","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3090","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 3090","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3092","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3092","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3092","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 3092","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 3092","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 3096","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3096/RFC-3096.txt"},{"from":"IETF RFC 3150","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3150/RFC-3150.txt"},{"from":"IETF RFC 3241","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3241/RFC-3241.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3243","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3243/RFC-3243.txt"},{"from":"IETF RFC 3374","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 3408","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3408/RFC-3408.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3759","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3759/RFC-3759.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3843","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3843/RFC-3843.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4164","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4164/RFC-4164.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 4997","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5136","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5136/RFC-5136.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3095","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3243","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-3243/RFC-3243.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3096","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3097","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3100","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 3101","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3235","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3235/RFC-3235.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3102","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3104","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-3104/RFC-3104.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3103","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 3104","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3103","to":"IETF RFC 3104","kind":"references","source":"IETF/RFC-3103/RFC-3103.txt"},{"from":"IETF RFC 3105","to":"IETF RFC 3104","kind":"references","source":"IETF/RFC-3105/RFC-3105.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3104","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3104","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 3102","to":"IETF RFC 3105","kind":"references","source":"IETF/RFC-3102/RFC-3102.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 3105","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3105","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4781","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4781/RFC-4781.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 3107","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3108","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 3110","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3111","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3111","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3111","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 3112","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 3131","to":"IETF RFC 3113","kind":"references","source":"IETF/RFC-3131/RFC-3131.txt"},{"from":"IETF RFC 4052","to":"IETF RFC 3113","kind":"references","source":"IETF/RFC-4052/RFC-4052.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 3113","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 3114","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3114","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3114","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3115","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 3203","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3203/RFC-3203.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3396","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3396/RFC-3396.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3825","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3825/RFC-3825.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3993","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-3993/RFC-3993.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4361","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4361/RFC-4361.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 3118","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3119","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3120","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3120","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3121","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3122","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3122","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3123","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3124","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 3125","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3125","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 3125","to":"IETF RFC 3126","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 3126","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 3126","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3126","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 3127","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4657","to":"IETF RFC 3127","kind":"references","source":"IETF/RFC-4657/RFC-4657.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 3128","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 3129","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3129","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 313","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4052","to":"IETF RFC 3131","kind":"references","source":"IETF/RFC-4052/RFC-4052.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 3131","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3238","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3238/RFC-3238.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3135","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 3137","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 3137","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 3137","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 3137","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 3171","to":"IETF RFC 3138","kind":"references","source":"IETF/RFC-3171/RFC-3171.txt"},{"from":"IETF RFC 3180","to":"IETF RFC 3138","kind":"references","source":"IETF/RFC-3180/RFC-3180.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 3138","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 3138","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3139","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3308","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-3308/RFC-3308.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3763","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-3763/RFC-3763.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 3140","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3141","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3141","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3142","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3142","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 3142","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 3143","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3144","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 3144","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3144","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3145","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 3146","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5136","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-5136/RFC-5136.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 3148","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 315","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 319","to":"IETF RFC 315","kind":"references","source":"IETF/RFC-319/RFC-319.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3150","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3151","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3688","to":"IETF RFC 3151","kind":"references","source":"IETF/RFC-3688/RFC-3688.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 3151","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 3172","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 4159","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-4159/RFC-4159.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 3152","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 3153","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3439","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3155","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3288","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-3288/RFC-3288.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3676","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-3676/RFC-3676.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 3156","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 3760","to":"IETF RFC 3157","kind":"references","source":"IETF/RFC-3760/RFC-3760.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 3157","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3198","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3198/RFC-3198.txt"},{"from":"IETF RFC 3216","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3216/RFC-3216.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3159","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"legal:2025-1929","to":"IETF RFC 3161","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 421 V1.3.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"ETSI TS 101 861 V1.4.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"ETSI TS 119 172-4 V1.1.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-119-172-4-V1.1.1/TS-119-172-4-V1.1.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 3161","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 3125","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 4049","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-4049/RFC-4049.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4810","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-4810/RFC-4810.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6019","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-6019/RFC-6019.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3161","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3633","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3633/RFC-3633.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3162","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 3195","to":"IETF RFC 3164","kind":"references","source":"IETF/RFC-3195/RFC-3195.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3164","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 3164","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 3164","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3164","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3231","to":"IETF RFC 3165","kind":"references","source":"IETF/RFC-3231/RFC-3231.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3165","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3165","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3165","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3448","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3448/RFC-3448.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3540","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3540/RFC-3540.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6789","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6789/RFC-6789.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 3168","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3169","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3169","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3169","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3170","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 3170","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-3170/RFC-3170.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 3171","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 3172","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 3172","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 3172","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 3172","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 3172","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3173","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4270","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4270/RFC-4270.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 3174","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 3175","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 3176","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 3587","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-3587/RFC-3587.txt"},{"from":"IETF RFC 3769","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-3769/RFC-3769.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4692","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-4692/RFC-4692.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6177","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-6177/RFC-6177.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 3177","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 3704","to":"IETF RFC 3178","kind":"references","source":"IETF/RFC-3704/RFC-3704.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 3178","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 3178","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3179","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 0318","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-0318/RFC-0318.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 2235","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-2235/RFC-2235.txt"},{"from":"IETF RFC 435","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-435/RFC-435.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 739","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 318","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 3180","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3181","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3181","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3181","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3181","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3181","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3182","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3187","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3187","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3187","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3187","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3187","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 3305","to":"IETF RFC 3188","kind":"references","source":"IETF/RFC-3305/RFC-3305.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3188","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3188","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 3190","to":"IETF RFC 3189","kind":"references","source":"IETF/RFC-3190/RFC-3190.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 319","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3189","to":"IETF RFC 3190","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 3190","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 3190","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 3191","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 3191","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3191","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3191","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3191","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3192","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 3193","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 3314","to":"IETF RFC 3194","kind":"references","source":"IETF/RFC-3314/RFC-3314.txt"},{"from":"IETF RFC 4692","to":"IETF RFC 3194","kind":"references","source":"IETF/RFC-4692/RFC-4692.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3194","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3195","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3195","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3460","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3460/RFC-3460.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3809","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3809/RFC-3809.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3198","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3200","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3203","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 3203","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3203","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3204","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 3234","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 3205","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 3206","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 3206","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 3207","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3208","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 3208","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 3208","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3208","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 3210","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3210/RFC-3210.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3353","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3353/RFC-3353.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3469","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3469/RFC-3469.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3477","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3477/RFC-3477.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3936","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3936/RFC-3936.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 4090","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4090/RFC-4090.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4657","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4657/RFC-4657.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5392","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 3209","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 3210","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3210","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3210","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 3210","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 3211","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3211","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3211","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3962","to":"IETF RFC 3211","kind":"references","source":"IETF/RFC-3962/RFC-3962.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3211","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3215","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3215/RFC-3215.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3469","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3469/RFC-3469.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 3988","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-3988/RFC-3988.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3212","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 3213","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3214","to":"IETF RFC 3213","kind":"references","source":"IETF/RFC-3214/RFC-3214.txt"},{"from":"IETF RFC 3272","to":"IETF RFC 3213","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3213","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 3214","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3213","to":"IETF RFC 3214","kind":"references","source":"IETF/RFC-3213/RFC-3213.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3214","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 3214","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 3212","to":"IETF RFC 3215","kind":"references","source":"IETF/RFC-3212/RFC-3212.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3215","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3216","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 3216","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 3217","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 3217","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3217","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 3217","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3217","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3218","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3482","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3508","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3219","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 3334","to":"IETF RFC 3220","kind":"references","source":"IETF/RFC-3334/RFC-3334.txt"},{"from":"IETF RFC 3374","to":"IETF RFC 3220","kind":"references","source":"IETF/RFC-3374/RFC-3374.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3220","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3765","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-3765/RFC-3765.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 3221","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3224","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 3226","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-3226/RFC-3226.txt"},{"from":"IETF RFC 3655","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-3655/RFC-3655.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 3225","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 3226","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3226","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 3226","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 3226","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 3376","to":"IETF RFC 3228","kind":"references","source":"IETF/RFC-3376/RFC-3376.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 3228","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3228","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3228","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 3230","to":"IETF RFC 3229","kind":"references","source":"IETF/RFC-3230/RFC-3230.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 388","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-388/RFC-388.txt"},{"from":"IETF RFC 739","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 323","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3230","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 3229","to":"IETF RFC 3230","kind":"references","source":"IETF/RFC-3229/RFC-3229.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 3230","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3231","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3231","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3231","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 3330","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3330/RFC-3330.txt"},{"from":"IETF RFC 3359","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3359/RFC-3359.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3518","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 3232","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 3716","to":"IETF RFC 3233","kind":"references","source":"IETF/RFC-3716/RFC-3716.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 3233","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3726","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-3726/RFC-3726.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5103","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5103/RFC-5103.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 3234","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 3235","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3236","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3237","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3507","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3507/RFC-3507.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 3238","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 3241","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 3243","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-3243/RFC-3243.txt"},{"from":"IETF RFC 3408","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-3408/RFC-3408.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3242","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 3243","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 3243","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3245","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 3247","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3247/RFC-3247.txt"},{"from":"IETF RFC 3248","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3248/RFC-3248.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3246","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 3246","to":"IETF RFC 3247","kind":"references","source":"IETF/RFC-3246/RFC-3246.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3247","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 3247","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 3247","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3248","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3248","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 3248","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 3249","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3249","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 3250","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 3250","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 3252","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3648","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-3648/RFC-3648.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 4331","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-4331/RFC-4331.txt"},{"from":"IETF RFC 4437","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-4437/RFC-4437.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5829","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-5829/RFC-5829.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 3253","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3256","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3257","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4384","to":"IETF RFC 3258","kind":"references","source":"IETF/RFC-4384/RFC-4384.txt"},{"from":"IETF RFC 4892","to":"IETF RFC 3258","kind":"references","source":"IETF/RFC-4892/RFC-4892.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3258","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 3258","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 326","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3270","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5693","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5693/RFC-5693.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 3260","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3261","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"IETF RFC 3262","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3262/RFC-3262.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3264","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3264/RFC-3264.txt"},{"from":"IETF RFC 3265","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3265/RFC-3265.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3310","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3310/RFC-3310.txt"},{"from":"IETF RFC 3311","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3311/RFC-3311.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3321","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3321/RFC-3321.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3324","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3324/RFC-3324.txt"},{"from":"IETF RFC 3325","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3325/RFC-3325.txt"},{"from":"IETF RFC 3326","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3326/RFC-3326.txt"},{"from":"IETF RFC 3327","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3327/RFC-3327.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3351","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3351/RFC-3351.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3362","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3362/RFC-3362.txt"},{"from":"IETF RFC 3372","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3427","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3427/RFC-3427.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3486","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3486/RFC-3486.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3508","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3515","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3515/RFC-3515.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 3524","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3524/RFC-3524.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3574","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3574/RFC-3574.txt"},{"from":"IETF RFC 3578","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3578/RFC-3578.txt"},{"from":"IETF RFC 3581","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3581/RFC-3581.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3608","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3608/RFC-3608.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3665","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3665/RFC-3665.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3857","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3857/RFC-3857.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 3969","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3969/RFC-3969.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4077","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4077/RFC-4077.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4091","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4091/RFC-4091.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4245","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4245/RFC-4245.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4320","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4320/RFC-4320.txt"},{"from":"IETF RFC 4321","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4321/RFC-4321.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4376","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4376/RFC-4376.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4453","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4453/RFC-4453.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4475","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4475/RFC-4475.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4488","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4488/RFC-4488.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4694","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 4715","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4759","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4759/RFC-4759.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 4904","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4904/RFC-4904.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4967","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4967/RFC-4967.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5167","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5167/RFC-5167.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7375","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7375/RFC-7375.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 3261","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 3311","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3311/RFC-3311.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3262","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 3329","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3329/RFC-3329.txt"},{"from":"IETF RFC 3361","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3361/RFC-3361.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4320","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4320/RFC-4320.txt"},{"from":"IETF RFC 4321","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4321/RFC-4321.txt"},{"from":"IETF RFC 4453","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4453/RFC-4453.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3263","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3262","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3262/RFC-3262.txt"},{"from":"IETF RFC 3311","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3311/RFC-3311.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3388","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3388/RFC-3388.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3665","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3665/RFC-3665.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4475","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4475/RFC-4475.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8035","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8035/RFC-8035.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 3264","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 3311","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3311/RFC-3311.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3420","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3420/RFC-3420.txt"},{"from":"IETF RFC 3427","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3427/RFC-3427.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3515","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3515/RFC-3515.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3857","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3857/RFC-3857.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4453","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4453/RFC-4453.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4488","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4488/RFC-4488.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3265","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3266","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3266","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3266","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3839","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-3839/RFC-3839.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3267","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4132","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4162","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3268","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 3269","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3270","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3272","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3443","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-3443/RFC-3443.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4182","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4182/RFC-4182.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3270","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 3346","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-3346/RFC-3346.txt"},{"from":"IETF RFC 3386","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-3386/RFC-3386.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3272","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 3287","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-3287/RFC-3287.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 3273","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 3749","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-3749/RFC-3749.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 4073","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-4073/RFC-4073.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3274","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3275","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3470","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3741","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-3741/RFC-3741.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4050","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-4050/RFC-4050.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4231","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-4231/RFC-4231.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3275","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 3276","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 3276","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3276","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3278","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 5008","to":"IETF RFC 3278","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 3278","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 3278","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3279","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3278","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4050","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4050/RFC-4050.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4491","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5480","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3279","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 328","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 328","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 3280","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 3280","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3280","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3280","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3114","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3278","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3278/RFC-3278.txt"},{"from":"IETF RFC 3279","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3281","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3370","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3647","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3739","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4043","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4134","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4134/RFC-4134.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4261","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4261/RFC-4261.txt"},{"from":"IETF RFC 4262","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4262/RFC-4262.txt"},{"from":"IETF RFC 4270","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4270/RFC-4270.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 4491","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4534","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4534/RFC-4534.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4630","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4630/RFC-4630.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4806","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4806/RFC-4806.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4810","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4810/RFC-4810.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5035","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 3280","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 3281","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3281","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3114","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3369","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3369/RFC-3369.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3820","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3820/RFC-3820.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 3281","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3282","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 3285","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3287","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 3287","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3288","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3289","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 329","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 363","to":"IETF RFC 329","kind":"references","source":"IETF/RFC-363/RFC-363.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 3444","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-3444/RFC-3444.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3290","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 3289","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3289/RFC-3289.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3291","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 3292","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 3296","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 3297","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 330","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3302","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 3302","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3302","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3304","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3304/RFC-3304.txt"},{"from":"IETF RFC 3323","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3323/RFC-3323.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3303","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3304","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3305","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 3307","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3307/RFC-3307.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3849","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3849/RFC-3849.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3956","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-3956/RFC-3956.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 6177","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-6177/RFC-6177.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3306","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 3306","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-3306/RFC-3306.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 3307","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 3308","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3308","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3309","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 331","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 4169","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-4169/RFC-4169.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3310","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 3312","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3312/RFC-3312.txt"},{"from":"IETF RFC 3313","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3313/RFC-3313.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 3311","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3312","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 3313","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3574","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-3574/RFC-3574.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3314","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 3633","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3633/RFC-3633.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3898","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3898/RFC-3898.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4039","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4039/RFC-4039.txt"},{"from":"IETF RFC 4057","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4057/RFC-4057.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4075","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4075/RFC-4075.txt"},{"from":"IETF RFC 4076","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4076/RFC-4076.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4242","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4242/RFC-4242.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4361","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4361/RFC-4361.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4580","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4580/RFC-4580.txt"},{"from":"IETF RFC 4649","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4649/RFC-4649.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4833","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4833/RFC-4833.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 4994","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-4994/RFC-4994.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6221","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6221/RFC-6221.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6355","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6355/RFC-6355.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6603","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6603/RFC-6603.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6644","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6644/RFC-6644.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7083","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7083/RFC-7083.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7283","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7283/RFC-7283.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3315","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3316","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3316","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 3316","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3316","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3316","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3317","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3317","to":"IETF RFC 3318","kind":"references","source":"IETF/RFC-3317/RFC-3317.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 3318","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3319","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 332","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3321","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-3321/RFC-3321.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3486","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-3486/RFC-3486.txt"},{"from":"IETF RFC 4077","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-4077/RFC-4077.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3320","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 3320","to":"IETF RFC 3321","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 4077","to":"IETF RFC 3321","kind":"references","source":"IETF/RFC-4077/RFC-4077.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 3321","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 3325","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-3325/RFC-3325.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3323","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 3325","to":"IETF RFC 3324","kind":"references","source":"IETF/RFC-3325/RFC-3325.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3324","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3324","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 3324","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3325","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3326","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3581","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-3581/RFC-3581.txt"},{"from":"IETF RFC 3608","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-3608/RFC-3608.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 3327","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3329","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 0333","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-0333/RFC-0333.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 739","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 762","to":"IETF RFC 333","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 3704","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-3704/RFC-3704.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5635","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5635/RFC-5635.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 3330","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3334","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3335","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 3337","to":"IETF RFC 3336","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3336","to":"IETF RFC 3337","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3355","to":"IETF RFC 3337","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3338","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3338","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 3338","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"legal:2026-1731","to":"IETF RFC 3339","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3339","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 3730","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5277","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5277/RFC-5277.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8943","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8943/RFC-8943.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 3339","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 3339","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 3519","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3543","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3543/RFC-3543.txt"},{"from":"IETF RFC 3583","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3583/RFC-3583.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4636","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4636/RFC-4636.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3344","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 3345","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 3345","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3346","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3346","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3346","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3347","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3347","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3783","to":"IETF RFC 3347","kind":"references","source":"IETF/RFC-3783/RFC-3783.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 3348","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 3348","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3348","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3350","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 3351","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3351","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 3351","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3351","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3353","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3355","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4052","to":"IETF RFC 3356","kind":"references","source":"IETF/RFC-4052/RFC-4052.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 3356","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 3356","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3356","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 3357","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3357","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 3357","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 3719","to":"IETF RFC 3358","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3358","to":"IETF RFC 3359","kind":"references","source":"IETF/RFC-3358/RFC-3358.txt"},{"from":"IETF RFC 3563","to":"IETF RFC 3359","kind":"references","source":"IETF/RFC-3563/RFC-3563.txt"},{"from":"IETF RFC 3786","to":"IETF RFC 3359","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 5303","to":"IETF RFC 3359","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 3359","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3360","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3319","to":"IETF RFC 3361","kind":"references","source":"IETF/RFC-3319/RFC-3319.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3361","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 3361","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3361","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 3362","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 3363","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 3363","to":"IETF RFC 3364","kind":"references","source":"IETF/RFC-3363/RFC-3363.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3364","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 3364","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3364","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 3364","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 5713","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-5713/RFC-5713.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 3365","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3366","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3368","to":"IETF RFC 3367","kind":"references","source":"IETF/RFC-3368/RFC-3368.txt"},{"from":"IETF RFC 3470","to":"IETF RFC 3367","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3367","to":"IETF RFC 3368","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 3369","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3369","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"IETF RFC 3370","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3370/RFC-3370.txt"},{"from":"IETF RFC 3428","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3428/RFC-3428.txt"},{"from":"IETF RFC 3447","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 3369","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3370","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3447","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3850","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3370","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3371","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 3398","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3487","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-3487/RFC-3487.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3372","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 3719","to":"IETF RFC 3373","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3847","to":"IETF RFC 3373","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3373","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3373","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 5303","to":"IETF RFC 3373","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3374","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3583","to":"IETF RFC 3374","kind":"references","source":"IETF/RFC-3583/RFC-3583.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 3374","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3374","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3374","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 3375","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3375","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3375","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 3375","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 3488","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3488/RFC-3488.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3569","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3569/RFC-3569.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3678","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3678/RFC-3678.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3918","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3918/RFC-3918.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 3376","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 3383","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3494","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3674","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3674/RFC-3674.txt"},{"from":"IETF RFC 3698","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3771","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3771/RFC-3771.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3377","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3379","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3379","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3379","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3674","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3674/RFC-3674.txt"},{"from":"IETF RFC 3698","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3771","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3771/RFC-3771.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 3383","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3385","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3385","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 3564","to":"IETF RFC 3386","kind":"references","source":"IETF/RFC-3564/RFC-3564.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3386","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4427","to":"IETF RFC 3386","kind":"references","source":"IETF/RFC-4427/RFC-4427.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 3386","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3386","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 4091","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4091/RFC-4091.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4756","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-4756/RFC-4756.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 3388","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 3389","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3649","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-3649/RFC-3649.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3390","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4724","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-4724/RFC-4724.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 3392","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 3432","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 3393","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 3537","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-3537/RFC-3537.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5649","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 3394","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3395","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3395","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 3397","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-3397/RFC-3397.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3925","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-3925/RFC-3925.txt"},{"from":"IETF RFC 4280","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-4280/RFC-4280.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 3396","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 3646","to":"IETF RFC 3397","kind":"references","source":"IETF/RFC-3646/RFC-3646.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3397","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3397","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3397","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 3397","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 3578","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-3578/RFC-3578.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3398","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3401","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3402","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3486","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3486/RFC-3486.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 3403","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3405","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3405/RFC-3405.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3761","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3404","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 3401","to":"IETF RFC 3405","kind":"references","source":"IETF/RFC-3401/RFC-3401.txt"},{"from":"IETF RFC 3402","to":"IETF RFC 3405","kind":"references","source":"IETF/RFC-3402/RFC-3402.txt"},{"from":"IETF RFC 3403","to":"IETF RFC 3405","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3404","to":"IETF RFC 3405","kind":"references","source":"IETF/RFC-3404/RFC-3404.txt"},{"from":"IETF RFC 3406","to":"IETF RFC 3405","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4152","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4152/RFC-4152.txt"},{"from":"IETF RFC 4179","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4179/RFC-4179.txt"},{"from":"IETF RFC 4198","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4854","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-4854/RFC-4854.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 6288","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-6288/RFC-6288.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3406","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3407","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3407","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3407","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 3408","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3408","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3408","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3498","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3535","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3535/RFC-3535.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3595","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3595/RFC-3595.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3729","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3729/RFC-3729.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3873","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3873/RFC-3873.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4265","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4265/RFC-4265.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 3410","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 3318","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3826","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3826/RFC-3826.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 3411","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3412","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 3413","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3826","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3826/RFC-3826.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3414","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3418","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3418/RFC-3418.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3433","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3433/RFC-3433.txt"},{"from":"IETF RFC 3434","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3434/RFC-3434.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3415","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3416","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3419","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3419/RFC-3419.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3826","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3826/RFC-3826.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4502","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4502/RFC-4502.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3417","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 3410","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3410/RFC-3410.txt"},{"from":"IETF RFC 3411","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3412","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3412/RFC-3412.txt"},{"from":"IETF RFC 3413","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3413/RFC-3413.txt"},{"from":"IETF RFC 3414","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3414/RFC-3414.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3512","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3512/RFC-3512.txt"},{"from":"IETF RFC 3584","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3584/RFC-3584.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4188","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4188/RFC-4188.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3418","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3419","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 342","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3515","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-3515/RFC-3515.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 3420","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3421","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 3423","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3581","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3581/RFC-3581.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 3424","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 3425","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3426","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 3426","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 3426","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-3426/RFC-3426.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3608","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-3608/RFC-3608.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 3969","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-3969/RFC-3969.txt"},{"from":"IETF RFC 4053","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4053/RFC-4053.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3427","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 3455","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3455/RFC-3455.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4453","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4453/RFC-4453.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 3428","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5586","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3429","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 343","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3430","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3430","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3685","to":"IETF RFC 3431","kind":"references","source":"IETF/RFC-3685/RFC-3685.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 3431","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 4148","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-4148/RFC-4148.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5560","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 3432","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 3591","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 4044","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-4044/RFC-4044.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 3433","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 3577","to":"IETF RFC 3434","kind":"references","source":"IETF/RFC-3577/RFC-3577.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 3434","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3434","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 3435","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 3435","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3435","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3435","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3435","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3758","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-3758/RFC-3758.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3436","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4349","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4349/RFC-4349.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4591","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 3438","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3439","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 344","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3442","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 3442","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3442","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 3442","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5462","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 3443","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7632","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-7632/RFC-7632.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 3444","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 3631","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-3631/RFC-3631.txt"},{"from":"IETF RFC 3658","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-3658/RFC-3658.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 3445","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 3618","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-3618/RFC-3618.txt"},{"from":"IETF RFC 3956","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-3956/RFC-3956.txt"},{"from":"IETF RFC 4610","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-4610/RFC-4610.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 3446","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3447","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3520","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3560","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-3560/RFC-3560.txt"},{"from":"IETF RFC 3778","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4056","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3447","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 3649","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-3649/RFC-3649.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3448","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 3449","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3450","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3451","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 3452","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3452","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3452/RFC-3452.txt"},{"from":"IETF RFC 3695","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3695/RFC-3695.txt"},{"from":"IETF RFC 3738","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3738/RFC-3738.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3941","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-3941/RFC-3941.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3453","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3491","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3553","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3553/RFC-3553.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4013","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4013/RFC-4013.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5051","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5051/RFC-5051.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5893","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5893/RFC-5893.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 3454","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3455","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 3455","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3456","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 3456","to":"IETF RFC 3457","kind":"references","source":"IETF/RFC-3456/RFC-3456.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3457","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 3458","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3458","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 3458","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3458","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 3458","to":"IETF RFC 3459","kind":"references","source":"IETF/RFC-3458/RFC-3458.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 3459","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3459","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 346","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 357","to":"IETF RFC 346","kind":"references","source":"IETF/RFC-357/RFC-357.txt"},{"from":"IETF RFC 3585","to":"IETF RFC 3460","kind":"references","source":"IETF/RFC-3585/RFC-3585.txt"},{"from":"IETF RFC 3644","to":"IETF RFC 3460","kind":"references","source":"IETF/RFC-3644/RFC-3644.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3460","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3460","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3460","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3482","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 3461","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 3462","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3463","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3463","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3463/RFC-3463.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3464","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 3742","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-3742/RFC-3742.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 3465","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 3466","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3570","to":"IETF RFC 3466","kind":"references","source":"IETF/RFC-3570/RFC-3570.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 3466","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 3466","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3467","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3467","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 3467","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 3468","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3468","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 3468","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3469","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 739","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 347","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3470","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3477","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3477/RFC-3477.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3811","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3811/RFC-3811.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4003","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4003/RFC-4003.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4139","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4139/RFC-4139.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3471","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3480","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3480/RFC-3480.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 3472","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 3471","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3472","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3472/RFC-3472.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3476","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3476/RFC-3476.txt"},{"from":"IETF RFC 3477","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3477/RFC-3477.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4003","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4003/RFC-4003.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4139","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4139/RFC-4139.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5063","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5063/RFC-5063.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5420","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3473","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 3474","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 3474","to":"IETF RFC 3476","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3473","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-3473/RFC-3473.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3477","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 3479","to":"IETF RFC 3478","kind":"references","source":"IETF/RFC-3479/RFC-3479.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3478","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 3478","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 3478","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 3478","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3478","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-3478/RFC-3478.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 3479","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 429","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-429/RFC-429.txt"},{"from":"IETF RFC 739","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 348","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 3468","to":"IETF RFC 3480","kind":"references","source":"IETF/RFC-3468/RFC-3468.txt"},{"from":"IETF RFC 3630","to":"IETF RFC 3480","kind":"references","source":"IETF/RFC-3630/RFC-3630.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3480","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3480","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3480","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3481","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 4694","to":"IETF RFC 3482","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4177","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4177/RFC-4177.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4311","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4311/RFC-4311.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4943","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4943/RFC-4943.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5221","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5221/RFC-5221.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6419","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6419/RFC-6419.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3484","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 3485","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3485","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 3485","to":"IETF RFC 3486","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3486","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 3969","to":"IETF RFC 3486","kind":"references","source":"IETF/RFC-3969/RFC-3969.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 3486","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3486","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 3487","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 3690","to":"IETF RFC 3487","kind":"references","source":"IETF/RFC-3690/RFC-3690.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3487","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3487","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3488","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3488","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 3488","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 3581","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3581/RFC-3581.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 3989","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-3989/RFC-3989.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4101","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4101/RFC-4101.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3489","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3491","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3492","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3492/RFC-3492.txt"},{"from":"IETF RFC 3546","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4985","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-4985/RFC-4985.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5301","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5301/RFC-5301.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5672","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5672/RFC-5672.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 3490","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3492","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3492/RFC-3492.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 3491","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 3490","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-3490/RFC-3490.txt"},{"from":"IETF RFC 3696","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-3696/RFC-3696.txt"},{"from":"IETF RFC 3743","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5137","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 3492","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 3542","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-3542/RFC-3542.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3678","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-3678/RFC-3678.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5221","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-5221/RFC-5221.txt"},{"from":"IETF RFC 5338","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-5338/RFC-5338.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 3493","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"IETF RFC 3494","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3494","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 4520","to":"IETF RFC 3494","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 3494","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 3494","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3494","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 3498","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 3502","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3502/RFC-3502.txt"},{"from":"IETF RFC 3503","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3503/RFC-3503.txt"},{"from":"IETF RFC 3516","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3516/RFC-3516.txt"},{"from":"IETF RFC 3656","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3656/RFC-3656.txt"},{"from":"IETF RFC 3691","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3691/RFC-3691.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4315","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4315/RFC-4315.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4686","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4686/RFC-4686.txt"},{"from":"IETF RFC 4731","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4731/RFC-4731.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5161","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5161/RFC-5161.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5183","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5183/RFC-5183.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5232","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5232/RFC-5232.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3501","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4315","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-4315/RFC-4315.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3502","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 3503","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3503","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3503","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3507","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3508","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3508","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 3509","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3511","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3512","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3512","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 3316","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3316/RFC-3316.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3572","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3572/RFC-3572.txt"},{"from":"IETF RFC 3582","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3582/RFC-3582.txt"},{"from":"IETF RFC 3587","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3587/RFC-3587.txt"},{"from":"IETF RFC 3596","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3596/RFC-3596.txt"},{"from":"IETF RFC 3627","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3627/RFC-3627.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3701","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3701/RFC-3701.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3769","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3769/RFC-3769.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 3831","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3831/RFC-3831.txt"},{"from":"IETF RFC 3849","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3849/RFC-3849.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3879","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3879/RFC-3879.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3913","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3913/RFC-3913.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3956","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3956/RFC-3956.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4012","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4012/RFC-4012.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4219","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4219/RFC-4219.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3513","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 3514","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3514","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3514","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 3514","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 3603","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-3603/RFC-3603.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4488","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4488/RFC-4488.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3515","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3516","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3517","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3518","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3518","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3518","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 3518","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3519","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 3521","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-3521/RFC-3521.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 3520","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 3520","to":"IETF RFC 3521","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3521","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 3521","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3521","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 3521","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3782","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-3782/RFC-3782.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 3522","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3523","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 3524","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 3524","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3524","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5125","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-5125/RFC-5125.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 3525","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4753","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 3526","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 3527","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 3527","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 3528","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3529","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 353","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4331","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-4331/RFC-4331.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 3530","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3531","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 3654","to":"IETF RFC 3532","kind":"references","source":"IETF/RFC-3654/RFC-3654.txt"},{"from":"IETF RFC 3534","to":"IETF RFC 3533","kind":"references","source":"IETF/RFC-3534/RFC-3534.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 3533","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 3533","to":"IETF RFC 3534","kind":"references","source":"IETF/RFC-3533/RFC-3533.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3535","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 3535","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3535","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3535","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3536","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 3537","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5649","to":"IETF RFC 3537","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3539","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 385","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-385/RFC-385.txt"},{"from":"IETF RFC 414","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-414/RFC-414.txt"},{"from":"IETF RFC 430","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 438","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-438/RFC-438.txt"},{"from":"IETF RFC 448","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-448/RFC-448.txt"},{"from":"IETF RFC 454","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 501","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-501/RFC-501.txt"},{"from":"IETF RFC 683","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-683/RFC-683.txt"},{"from":"IETF RFC 691","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 959","to":"IETF RFC 354","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 3540","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 3542","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 4636","to":"IETF RFC 3543","kind":"references","source":"IETF/RFC-4636/RFC-4636.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3543","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 3544","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3544","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3544","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3544","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3544","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 4247","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-4247/RFC-4247.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 3545","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3546","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3740","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-3740/RFC-3740.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3973","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-3973/RFC-3973.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 3547","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 3548","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 3544","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3544/RFC-3544.txt"},{"from":"IETF RFC 3545","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3545/RFC-3545.txt"},{"from":"IETF RFC 3547","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3547/RFC-3547.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3556","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3556/RFC-3556.txt"},{"from":"IETF RFC 3605","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3605/RFC-3605.txt"},{"from":"IETF RFC 3611","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 3640","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3725","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3725/RFC-3725.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4028","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4028/RFC-4028.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4337","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5117","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5450","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5450/RFC-5450.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5457","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5457/RFC-5457.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6188","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6188/RFC-6188.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6562","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6562/RFC-6562.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7164","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7164/RFC-7164.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3550","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3555","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3556","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3556/RFC-3556.txt"},{"from":"IETF RFC 3711","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3711/RFC-3711.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3551","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3833","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-3833/RFC-3833.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6386","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6386/RFC-6386.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 3552","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 3688","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-3688/RFC-3688.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6755","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-6755/RFC-6755.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 3553","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 3554","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3554","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3554","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 3551","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3555","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3556","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 3558","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 3565","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-3565/RFC-3565.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3560","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 3561","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 3561","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3561","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 3561","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 3562","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 3563","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 3563","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 3563","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 3564","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 3657","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3657/RFC-3657.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5649","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3565","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 3664","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-3664/RFC-3664.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4434","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4434/RFC-4434.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 3566","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 3847","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 3567","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3568","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4608","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4608/RFC-4608.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 3569","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 435","to":"IETF RFC 357","kind":"references","source":"IETF/RFC-435/RFC-435.txt"},{"from":"IETF RFC 560","to":"IETF RFC 357","kind":"references","source":"IETF/RFC-560/RFC-560.txt"},{"from":"IETF RFC 726","to":"IETF RFC 357","kind":"references","source":"IETF/RFC-726/RFC-726.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 3570","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6770","to":"IETF RFC 3570","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 3572","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3574","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3574","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 3574","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3574","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3575","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 3575","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-3575/RFC-3575.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3576","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3577","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3577","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3577","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 3578","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 3580","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4016","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4016/RFC-4016.txt"},{"from":"IETF RFC 4017","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4137","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4137/RFC-4137.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 3579","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 357","to":"IETF RFC 358","kind":"references","source":"IETF/RFC-357/RFC-357.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3770","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-3770/RFC-3770.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3580","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3581","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3581","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 3581","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4116","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4116/RFC-4116.txt"},{"from":"IETF RFC 4177","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4177/RFC-4177.txt"},{"from":"IETF RFC 4219","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4219/RFC-4219.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 3582","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3583","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3584","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3585","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3585","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3585","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3586","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 3587","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 3589","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3589/RFC-3589.txt"},{"from":"IETF RFC 3846","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3846/RFC-3846.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3957","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-3957/RFC-3957.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5224","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5224/RFC-5224.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5431","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5431/RFC-5431.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5516","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5516/RFC-5516.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5624","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5624/RFC-5624.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5719","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5719/RFC-5719.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6737","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-6737/RFC-6737.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3588","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3589","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 3590","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3591","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 3593","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3593/RFC-3593.txt"},{"from":"IETF RFC 3606","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 3592","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 3592","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3705","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3705/RFC-3705.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4319","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3593","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 3595","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3595","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3595","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3901","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-3901/RFC-3901.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4025","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4025/RFC-4025.txt"},{"from":"IETF RFC 4159","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4159/RFC-4159.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5158","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5158/RFC-5158.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 3596","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 3597","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 5233","to":"IETF RFC 3598","kind":"references","source":"IETF/RFC-5233/RFC-5233.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 360","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 407","to":"IETF RFC 360","kind":"references","source":"IETF/RFC-407/RFC-407.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 3602","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 3968","to":"IETF RFC 3603","kind":"references","source":"IETF/RFC-3968/RFC-3968.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3605","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3606","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 3606","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 3607","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3608","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3608","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 3610","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3611","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3617","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 3617","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3956","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-3956/RFC-3956.txt"},{"from":"IETF RFC 4608","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-4608/RFC-4608.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 3618","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 362","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3620","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3621","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 3621","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3621","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3621","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4811","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4811/RFC-4811.txt"},{"from":"IETF RFC 4812","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4812/RFC-4812.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 3623","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 5444","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5497","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-5497/RFC-5497.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 3626","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3627","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3627","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3627","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 3627","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3627","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3744","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3931","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4011","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4043","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5035","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5051","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5051/RFC-5051.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5137","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7464","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 3629","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 363","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3623","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-3623/RFC-3623.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4222","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4222/RFC-4222.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 3630","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3631","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3631","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3631","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3631","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4580","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4580/RFC-4580.txt"},{"from":"IETF RFC 4649","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4649/RFC-4649.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6603","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6603/RFC-6603.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7083","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7083/RFC-7083.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3633","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 3621","to":"IETF RFC 3635","kind":"references","source":"IETF/RFC-3621/RFC-3621.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 3635","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 3635","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3635","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 3635","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 3636","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3637","to":"IETF RFC 3636","kind":"references","source":"IETF/RFC-3637/RFC-3637.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3636","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3635","to":"IETF RFC 3637","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 3636","to":"IETF RFC 3637","kind":"references","source":"IETF/RFC-3636/RFC-3636.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3640","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 3640","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3640","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 3640","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 3641","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 3641","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 3641","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 3641","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 3642","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3672","to":"IETF RFC 3642","kind":"references","source":"IETF/RFC-3672/RFC-3672.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 3642","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 3642","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3643","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3643","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3643","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 3643","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 3644","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3644","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 3645","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 3645","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 3736","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-3736/RFC-3736.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3646","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"legal:2024-2980","to":"IETF RFC 3647","kind":"cites","source":"implementing-acts/2024-2980/2024-2980.md"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 3647","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"IETF RFC 3647","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-2 V2.6.1","to":"IETF RFC 3647","kind":"references","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf"},{"from":"ETSI TS 119 411-8 V1.1.1","to":"IETF RFC 3647","kind":"references","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf"},{"from":"ETSI TS 119 431-1 V1.3.1","to":"IETF RFC 3647","kind":"references","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf"},{"from":"ETSI TS 119 441 V1.2.1","to":"IETF RFC 3647","kind":"references","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf"},{"from":"IETF RFC 4504","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4810","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-4810/RFC-4810.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 3647","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3648","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 3649","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 365","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 3650","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3650","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 7669","to":"IETF RFC 3650","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 3651","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 3651","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 7669","to":"IETF RFC 3651","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 3650","to":"IETF RFC 3652","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"IETF RFC 3652","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 7669","to":"IETF RFC 3652","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 4098","to":"IETF RFC 3654","kind":"references","source":"IETF/RFC-4098/RFC-4098.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3655","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 3655","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 3655","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 3655","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3656","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4132","to":"IETF RFC 3657","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 3657","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 3657","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3657","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 3755","to":"IETF RFC 3658","kind":"references","source":"IETF/RFC-3755/RFC-3755.txt"},{"from":"IETF RFC 3757","to":"IETF RFC 3658","kind":"references","source":"IETF/RFC-3757/RFC-3757.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3658","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3658","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 366","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3662","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 4109","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4109/RFC-4109.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4434","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4434/RFC-4434.txt"},{"from":"IETF RFC 4615","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4615/RFC-4615.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3664","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 3666","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-3666/RFC-3666.txt"},{"from":"IETF RFC 4244","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-4244/RFC-4244.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3665","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 3665","to":"IETF RFC 3666","kind":"references","source":"IETF/RFC-3665/RFC-3665.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3666","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 3668","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-3668/RFC-3668.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3933","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-3933/RFC-3933.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3667","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 3667","to":"IETF RFC 3668","kind":"references","source":"IETF/RFC-3667/RFC-3667.txt"},{"from":"IETF RFC 3669","to":"IETF RFC 3668","kind":"references","source":"IETF/RFC-3669/RFC-3669.txt"},{"from":"IETF RFC 3933","to":"IETF RFC 3668","kind":"references","source":"IETF/RFC-3933/RFC-3933.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 3669","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 367","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3670","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 3671","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 3671","to":"IETF RFC 3672","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 3672","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 3674","to":"IETF RFC 3673","kind":"references","source":"IETF/RFC-3674/RFC-3674.txt"},{"from":"IETF RFC 3673","to":"IETF RFC 3674","kind":"references","source":"IETF/RFC-3673/RFC-3673.txt"},{"from":"IETF RFC 3866","to":"IETF RFC 3674","kind":"references","source":"IETF/RFC-3866/RFC-3866.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 3674","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4367","to":"IETF RFC 3675","kind":"references","source":"IETF/RFC-4367/RFC-4367.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 3676","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3676","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3676","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 3677","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4333","to":"IETF RFC 3677","kind":"references","source":"IETF/RFC-4333/RFC-4333.txt"},{"from":"IETF RFC 3810","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-3810/RFC-3810.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3678","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 3942","to":"IETF RFC 3679","kind":"references","source":"IETF/RFC-3942/RFC-3942.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 3679","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 3680","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3682","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 3682","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 3682","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 3682","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 3682","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 3934","to":"IETF RFC 3683","kind":"references","source":"IETF/RFC-3934/RFC-3934.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3683","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 3683","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 4919","to":"IETF RFC 3684","kind":"references","source":"IETF/RFC-4919/RFC-4919.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 3684","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 5235","to":"IETF RFC 3685","kind":"references","source":"IETF/RFC-5235/RFC-5235.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 4106","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-4106/RFC-4106.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 3686","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 3680","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3680/RFC-3680.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3880","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4991","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-4991/RFC-4991.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5277","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5277/RFC-5277.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5717","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5717/RFC-5717.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6243","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6243/RFC-6243.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6685","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6685/RFC-6685.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 3688","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 3690","to":"IETF RFC 3689","kind":"references","source":"IETF/RFC-3690/RFC-3690.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3689","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3689","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 369","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 531","to":"IETF RFC 369","kind":"references","source":"IETF/RFC-531/RFC-531.txt"},{"from":"IETF RFC 3689","to":"IETF RFC 3690","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3690","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 3690","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 3691","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 3691","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 3691","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 3691","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4581","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4581/RFC-4581.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4915","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4915/RFC-4915.txt"},{"from":"IETF RFC 4940","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-4940/RFC-4940.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5719","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5719/RFC-5719.txt"},{"from":"IETF RFC 5872","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5872/RFC-5872.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 3692","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 3694","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-3694/RFC-3694.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5069","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5069/RFC-5069.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5808","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5808/RFC-5808.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3693","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 3694","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3695","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 3695","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3696","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3696","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3696","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 3696","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3696","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 3697","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 3703","to":"IETF RFC 3698","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 3698","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 370","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 3701","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3701","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3701","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 3698","to":"IETF RFC 3703","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4948","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4948/RFC-4948.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5635","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5635/RFC-5635.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3704","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 3728","to":"IETF RFC 3705","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3705","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 3705","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3705","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3705","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3706","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3707","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3707","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3707","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 3707","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 3708","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 3932","to":"IETF RFC 3710","kind":"references","source":"IETF/RFC-3932/RFC-3932.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 3710","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 3710","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 3830","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 3951","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3951/RFC-3951.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4040","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4040/RFC-4040.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4184","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4184/RFC-4184.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4534","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4534/RFC-4534.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4771","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4771/RFC-4771.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5117","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6188","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6188/RFC-6188.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6562","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6562/RFC-6562.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3711","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4132","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5932","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-5932/RFC-5932.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3713","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 3714","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3715","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 3716","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4054","to":"IETF RFC 3717","kind":"references","source":"IETF/RFC-4054/RFC-4054.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 3719","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 3719","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3783","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-3783/RFC-3783.txt"},{"from":"IETF RFC 3980","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-3980/RFC-3980.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4850","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4850/RFC-4850.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3720","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3722","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3721","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 3722","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3721","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-3721/RFC-3721.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 4018","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-4018/RFC-4018.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4850","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-4850/RFC-4850.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3723","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 3724","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4032","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4032/RFC-4032.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3725","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4094","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 3726","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 3728","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 3737","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-3737/RFC-3737.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3729","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 373","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 3730","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 3735","to":"IETF RFC 3731","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 3731","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 3731","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 3731","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 3731","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3732","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 3732","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 3732","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 3733","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 3733","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 3733","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 3734","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 3734","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3734","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3735","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 4076","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4076/RFC-4076.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4242","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4242/RFC-4242.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3736","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 3737","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 3737","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3738","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"legal:2025-1929","to":"IETF RFC 3739","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 3739","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"ETSI TS 119 495 V1.7.1","to":"IETF RFC 3739","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"IETF RFC 4949","to":"IETF RFC 3739","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4534","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4534/RFC-4534.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 3740","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 4051","to":"IETF RFC 3741","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3741","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 3742","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 3743","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5397","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-5397/RFC-5397.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 3744","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 4017","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4017/RFC-4017.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4137","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4137/RFC-4137.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4739","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4739/RFC-4739.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 3748","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 3943","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-3943/RFC-3943.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 3749","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 3904","to":"IETF RFC 3750","kind":"references","source":"IETF/RFC-3904/RFC-3904.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3750","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 3750","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4135","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4135/RFC-4135.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4832","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4832/RFC-4832.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 3753","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 3757","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-3757/RFC-3757.txt"},{"from":"IETF RFC 3845","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-3845/RFC-3845.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 3755","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 3964","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-3964/RFC-3964.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4057","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4057/RFC-4057.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 4135","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4135/RFC-4135.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4832","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4832/RFC-4832.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4943","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4943/RFC-4943.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 3756","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 3757","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 3758","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 3759","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 3767","to":"IETF RFC 3760","kind":"references","source":"IETF/RFC-3767/RFC-3767.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3760","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 3760","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 3764","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-3764/RFC-3764.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3966","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4143","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-4143/RFC-4143.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4759","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-4759/RFC-4759.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3761","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3762","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 3763","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 3824","to":"IETF RFC 3764","kind":"references","source":"IETF/RFC-3824/RFC-3824.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3764","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3764","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3764","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 3765","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 3871","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-3871/RFC-3871.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 3766","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3767","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 3768","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3769","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 3769","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 4334","to":"IETF RFC 3770","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 3771","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 3771","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 3753","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-3753/RFC-3753.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 4135","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4135/RFC-4135.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4177","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4177/RFC-4177.txt"},{"from":"IETF RFC 4191","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4191/RFC-4191.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4219","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4219/RFC-4219.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4449","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4449/RFC-4449.txt"},{"from":"IETF RFC 4487","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4487/RFC-4487.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5094","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5094/RFC-5094.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5142","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5142/RFC-5142.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3775","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3963","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-3963/RFC-3963.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3776","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 3797","to":"IETF RFC 3777","kind":"references","source":"IETF/RFC-3797/RFC-3797.txt"},{"from":"IETF RFC 4071","to":"IETF RFC 3777","kind":"references","source":"IETF/RFC-4071/RFC-4071.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 3777","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 3777","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 3778","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 3779","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 378","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3781","to":"IETF RFC 3780","kind":"references","source":"IETF/RFC-3781/RFC-3781.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 3780","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 3780","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 3781","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3782","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3783","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 3785","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-3785/RFC-3785.txt"},{"from":"IETF RFC 3786","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5120","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5130","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 3784","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 3785","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4657","to":"IETF RFC 3785","kind":"references","source":"IETF/RFC-4657/RFC-4657.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 3785","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 3785","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 3786","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 3787","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 3868","to":"IETF RFC 3788","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3792","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3792/RFC-3792.txt"},{"from":"IETF RFC 3793","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3793/RFC-3793.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3796","to":"IETF RFC 3789","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3790","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3790","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3791","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3792","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3792","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3793","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3793","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3794","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3794","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3795","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3795","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3795","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 3796","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3791","to":"IETF RFC 3796","kind":"references","source":"IETF/RFC-3791/RFC-3791.txt"},{"from":"IETF RFC 3777","to":"IETF RFC 3797","kind":"references","source":"IETF/RFC-3777/RFC-3777.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3798","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 3802","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 3803","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-3803/RFC-3803.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3949","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-3949/RFC-3949.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 3801","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3802","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 3803","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3803","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 3806","to":"IETF RFC 3805","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3877","to":"IETF RFC 3805","kind":"references","source":"IETF/RFC-3877/RFC-3877.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 3805","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 3806","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 4026","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4026/RFC-4026.txt"},{"from":"IETF RFC 4031","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 3809","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 381","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3775","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-3775/RFC-3775.txt"},{"from":"IETF RFC 3776","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-3776/RFC-3776.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4045","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4045/RFC-4045.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 3810","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3970","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-3970/RFC-3970.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3811","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 3813","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-3813/RFC-3813.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3916","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3812","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 3812","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-3812/RFC-3812.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3815","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-3815/RFC-3815.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 3813","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3814","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 3814","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 3814","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 3814","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3814","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 3815","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3818","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 3818","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 4259","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 3819","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 3820","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3820","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 3820","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 3822","to":"IETF RFC 3821","kind":"references","source":"IETF/RFC-3822/RFC-3822.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 3821","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3821","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 3822","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3822","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 3824","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 3825","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 3826","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 3828","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4771","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4771/RFC-4771.txt"},{"from":"IETF RFC 4909","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-4909/RFC-4909.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 3830","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 3831","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 3831","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3832","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3832","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3832","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 4218","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4218/RFC-4218.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 3833","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 3834","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 3834","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 3834","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3834","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3834","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 3984","to":"IETF RFC 3839","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 3839","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 3839","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 3841","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-3841/RFC-3841.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3840","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3842","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-3842/RFC-3842.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3841","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 3840","to":"IETF RFC 3842","kind":"references","source":"IETF/RFC-3840/RFC-3840.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3842","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3842","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3842","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3842","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 3843","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 3845","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 3845","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3846","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3846","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 3847","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 5306","to":"IETF RFC 3847","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3848","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 3848","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3848","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 3848","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 3848","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 4085","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-4085/RFC-4085.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5398","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-5398/RFC-5398.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 3849","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 414","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-414/RFC-414.txt"},{"from":"IETF RFC 430","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 448","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-448/RFC-448.txt"},{"from":"IETF RFC 454","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 686","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-686/RFC-686.txt"},{"from":"IETF RFC 691","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 959","to":"IETF RFC 385","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3850","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 3851","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 3850","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3852","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3852/RFC-3852.txt"},{"from":"IETF RFC 3853","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3853/RFC-3853.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3926","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-3926/RFC-3926.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4073","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4073/RFC-4073.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4134","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4134/RFC-4134.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4262","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4262/RFC-4262.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 3851","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 3852","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 3852","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"IETF RFC 3852","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3852","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3850","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3874","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3874/RFC-3874.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4027","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4027/RFC-4027.txt"},{"from":"IETF RFC 4043","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4049","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4049/RFC-4049.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4056","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4073","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4073/RFC-4073.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4134","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4134/RFC-4134.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4231","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4231/RFC-4231.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 4491","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4534","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4534/RFC-4534.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4853","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4853/RFC-4853.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5035","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5083","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5083/RFC-5083.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5091","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5091/RFC-5091.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 3852","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 3853","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 3853","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3853","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3853","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 3854","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 3854","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 3855","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 3855","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 3857","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-3857/RFC-3857.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3856","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3858","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-3858/RFC-3858.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3857","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 3857","to":"IETF RFC 3858","kind":"references","source":"IETF/RFC-3857/RFC-3857.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3858","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3858","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 3858","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3859","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 3861","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3861/RFC-3861.txt"},{"from":"IETF RFC 3862","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3863","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3863/RFC-3863.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3860","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3861","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 3860","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-3860/RFC-3860.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3862","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 3856","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3856/RFC-3856.txt"},{"from":"IETF RFC 3859","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3859/RFC-3859.txt"},{"from":"IETF RFC 3903","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3903/RFC-3903.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 3994","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-3994/RFC-3994.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4119","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4119/RFC-4119.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3863","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 3865","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-3865/RFC-3865.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 3864","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3865","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3865","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 3866","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3868","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3871","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 3873","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 3873","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 3873","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3873","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 3874","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4051","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 4055","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-4055/RFC-4055.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 3874","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3875","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4387","to":"IETF RFC 3875","kind":"references","source":"IETF/RFC-4387/RFC-4387.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 3875","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 3875","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 3878","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 5674","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3877","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 3878","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3878","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 3879","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 739","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 388","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 3880","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 3880","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 3880","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 4778","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-4778/RFC-4778.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5635","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-5635/RFC-5635.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3882","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 3884","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3884","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3884","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3884","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 3885","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 3886","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3886","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 3886","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 3887","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3887","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 3887","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3887","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3887","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3885","to":"IETF RFC 3888","kind":"references","source":"IETF/RFC-3885/RFC-3885.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 3888","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 3889","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 389","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3890","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3891","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3893","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-3893/RFC-3893.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4235","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-4235/RFC-4235.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 3892","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 3891","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-3891/RFC-3891.txt"},{"from":"IETF RFC 3892","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-3892/RFC-3892.txt"},{"from":"IETF RFC 3911","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-3911/RFC-3911.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3893","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 3894","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 3895","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3896","to":"IETF RFC 3895","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 3895","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 3895","to":"IETF RFC 3896","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4805","to":"IETF RFC 3896","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 3896","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3898","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3898","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3898","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3901","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 3901","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3901","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3902","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3903","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3904","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3904","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3904","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 391","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3911","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 3912","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3913","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4026","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4026/RFC-4026.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3916","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5103","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5103/RFC-5103.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 3917","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 3415","to":"IETF RFC 3918","kind":"references","source":"IETF/RFC-3415/RFC-3415.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 392","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4854","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-4854/RFC-4854.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3920","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3923","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-3923/RFC-3923.txt"},{"from":"IETF RFC 4079","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-4079/RFC-4079.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4854","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-4854/RFC-4854.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 3921","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 3922","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 3922","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3922","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 3921","to":"IETF RFC 3923","kind":"references","source":"IETF/RFC-3921/RFC-3921.txt"},{"from":"IETF RFC 3922","to":"IETF RFC 3923","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3923","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3923","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 3925","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 3925","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 3925","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 3925","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 3926","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3926","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 3927","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4349","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4349/RFC-4349.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4591","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4667","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4667/RFC-4667.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5640","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5640/RFC-5640.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 3931","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 4981","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-4981/RFC-4981.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 3932","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3933","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 5111","to":"IETF RFC 3933","kind":"references","source":"IETF/RFC-5111/RFC-5111.txt"},{"from":"IETF RFC 6982","to":"IETF RFC 3933","kind":"references","source":"IETF/RFC-6982/RFC-6982.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3934","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 3934","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3935","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 5377","to":"IETF RFC 3935","kind":"references","source":"IETF/RFC-5377/RFC-5377.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 3935","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 3935","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 3936","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 4046","to":"IETF RFC 3940","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 3940","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 3940","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 3940","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 3940","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 3940","to":"IETF RFC 3941","kind":"references","source":"IETF/RFC-3940/RFC-3940.txt"},{"from":"IETF RFC 4654","to":"IETF RFC 3941","kind":"references","source":"IETF/RFC-4654/RFC-4654.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 3941","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3941","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 4578","to":"IETF RFC 3942","kind":"references","source":"IETF/RFC-4578/RFC-4578.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3942","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 3942","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3942","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3943","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3946","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4054","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4054/RFC-4054.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4427","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4427/RFC-4427.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 3945","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 3945","to":"IETF RFC 3946","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"IETF RFC 4139","to":"IETF RFC 3946","kind":"references","source":"IETF/RFC-4139/RFC-4139.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 3946","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 4093","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-4093/RFC-4093.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 3947","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 3947","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-3947/RFC-3947.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 3948","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 3949","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 3949","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 3952","to":"IETF RFC 3951","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3951","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 3951","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 3951","to":"IETF RFC 3952","kind":"references","source":"IETF/RFC-3951/RFC-3951.txt"},{"from":"IETF RFC 4317","to":"IETF RFC 3952","kind":"references","source":"IETF/RFC-4317/RFC-4317.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3952","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3953","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 3953","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7632","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-7632/RFC-7632.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3954","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 3955","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 4029","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4029/RFC-4029.txt"},{"from":"IETF RFC 4038","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4038/RFC-4038.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 3956","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 3957","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 3957","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 3957","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 3957","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 3958","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 3960","to":"IETF RFC 3959","kind":"references","source":"IETF/RFC-3960/RFC-3960.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 3959","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 3959","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 3959","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-3959/RFC-3959.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 3960","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 3962","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-3962/RFC-3962.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4537","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 3961","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 3961","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 3962","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 4584","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4584/RFC-4584.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 5094","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5094/RFC-5094.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 3963","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5158","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-5158/RFC-5158.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 3964","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 3965","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 4143","to":"IETF RFC 3965","kind":"references","source":"IETF/RFC-4143/RFC-4143.txt"},{"from":"ETSI TS 119 602 V1.1.1","to":"IETF RFC 3966","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 3966","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 4474","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4694","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 4715","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 4759","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4759/RFC-4759.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4904","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4904/RFC-4904.txt"},{"from":"IETF RFC 4967","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-4967/RFC-4967.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3966","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 3967","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 3967","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 4897","to":"IETF RFC 3967","kind":"references","source":"IETF/RFC-4897/RFC-4897.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 3968","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4168","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-4168/RFC-4168.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4967","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-4967/RFC-4967.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 3969","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3970","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 3972","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4016","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4016/RFC-4016.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4135","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4135/RFC-4135.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4286","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4286/RFC-4286.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4832","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4832/RFC-4832.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5154","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6105","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6105/RFC-6105.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 3971","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 3971","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4429","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4429/RFC-4429.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4581","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4581/RFC-4581.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 5014","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5014/RFC-5014.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6644","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6644/RFC-6644.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 3972","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5384","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5384/RFC-5384.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 3973","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 3974","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4644","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-4644/RFC-4644.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 3977","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 3979","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-3979/RFC-3979.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 4748","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4748/RFC-4748.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3978","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 3978","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-3978/RFC-3978.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4226","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4226/RFC-4226.txt"},{"from":"IETF RFC 4693","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4693/RFC-4693.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4879","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4879/RFC-4879.txt"},{"from":"IETF RFC 4986","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-4986/RFC-4986.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 3979","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 3980","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3980","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 3983","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-3983/RFC-3983.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4991","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-4991/RFC-4991.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 3981","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 3982","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3982","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3982","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 3982","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 3982","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 3958","to":"IETF RFC 3983","kind":"references","source":"IETF/RFC-3958/RFC-3958.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 3983","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 3983","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 3983","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 3983","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 3984","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 3984","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 3984","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 4197","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4454","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4863","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-4863/RFC-4863.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 3985","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 3986","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ARF TS05 V1.2.1","to":"IETF RFC 3986","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS11 V1.0.1","to":"IETF RFC 3986","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 412-6 V1.2.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 3986","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 3987","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4007","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4007/RFC-4007.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 4151","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4158","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4227","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4227/RFC-4227.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4267","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4267/RFC-4267.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4325","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4437","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4437/RFC-4437.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4475","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4475/RFC-4475.txt"},{"from":"IETF RFC 4483","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4483/RFC-4483.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4838","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4838/RFC-4838.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4946","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4946/RFC-4946.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5013","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5013/RFC-5013.txt"},{"from":"IETF RFC 5017","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5017/RFC-5017.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5674","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5781","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5781/RFC-5781.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6694","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6694/RFC-6694.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6983","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6983/RFC-6983.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8081","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8081/RFC-8081.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 3986","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4329","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4395","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4395/RFC-4395.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4946","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4946/RFC-4946.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 3987","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 3988","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 3989","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 3989","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 3989","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 399","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4118","to":"IETF RFC 3990","kind":"references","source":"IETF/RFC-4118/RFC-4118.txt"},{"from":"IETF RFC 4564","to":"IETF RFC 3990","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 3990","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 4580","to":"IETF RFC 3993","kind":"references","source":"IETF/RFC-4580/RFC-4580.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 3993","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 3994","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 400","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 413","to":"IETF RFC 400","kind":"references","source":"IETF/RFC-413/RFC-413.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4087","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4087/RFC-4087.txt"},{"from":"IETF RFC 4088","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4088/RFC-4088.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4444","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4546","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4546/RFC-4546.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 4001","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4002","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 4003","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4003","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4005","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4004","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4072","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4072/RFC-4072.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4849","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-4849/RFC-4849.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 4005","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 4006","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5431","to":"IETF RFC 4006","kind":"references","source":"IETF/RFC-5431/RFC-5431.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 4006","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4006","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4006","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7346","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-7346/RFC-7346.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 4007","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 4097","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-4097/RFC-4097.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 4008","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 4010","to":"IETF RFC 4009","kind":"references","source":"IETF/RFC-4010/RFC-4010.txt"},{"from":"IETF RFC 4162","to":"IETF RFC 4009","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 4196","to":"IETF RFC 4009","kind":"references","source":"IETF/RFC-4196/RFC-4196.txt"},{"from":"IETF RFC 4269","to":"IETF RFC 4009","kind":"references","source":"IETF/RFC-4269/RFC-4269.txt"},{"from":"IETF RFC 4162","to":"IETF RFC 4010","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 4010","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 4011","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4011","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 4012","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5769","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5769/RFC-5769.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 4013","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 4015","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 4016","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4016","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 4016","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4016","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 4017","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 4018","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 4018","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4018","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 4019","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 4019","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 4019","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4019","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 4019","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 4858","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-4858/RFC-4858.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7120","to":"IETF RFC 4020","kind":"references","source":"IETF/RFC-7120/RFC-7120.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 4021","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 4021","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4021","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 4021","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4022","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5332","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-5332/RFC-5332.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 4023","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4025","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4176","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 4026","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 4027","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 4028","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 4028","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4028","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 4028","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4029","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4243","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-4243/RFC-4243.txt"},{"from":"IETF RFC 5010","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-5010/RFC-5010.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 4030","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 4110","to":"IETF RFC 4031","kind":"references","source":"IETF/RFC-4110/RFC-4110.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 4031","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 4031","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 4031","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4031","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 4032","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4032","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 4032","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 4032","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 4032","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4095","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4095/RFC-4095.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4431","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4431/RFC-4431.txt"},{"from":"IETF RFC 4470","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4470/RFC-4470.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4509","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4509/RFC-4509.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4648","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4648/RFC-4648.txt"},{"from":"IETF RFC 4686","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4686/RFC-4686.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4892","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4892/RFC-4892.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4955","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4955/RFC-4955.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 4986","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-4986/RFC-4986.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5338","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5338/RFC-5338.txt"},{"from":"IETF RFC 5358","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5358/RFC-5358.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7706","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7706/RFC-7706.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4033","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4035","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4035/RFC-4035.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4343","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4343/RFC-4343.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4431","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4431/RFC-4431.txt"},{"from":"IETF RFC 4470","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4470/RFC-4470.txt"},{"from":"IETF RFC 4509","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4509/RFC-4509.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4955","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4955/RFC-4955.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4986","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-4986/RFC-4986.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8078","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8078/RFC-8078.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4034","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4033","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4033/RFC-4033.txt"},{"from":"IETF RFC 4034","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4034/RFC-4034.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 4185","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4192","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4192/RFC-4192.txt"},{"from":"IETF RFC 4225","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4225/RFC-4225.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4310","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4431","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4431/RFC-4431.txt"},{"from":"IETF RFC 4470","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4470/RFC-4470.txt"},{"from":"IETF RFC 4509","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4509/RFC-4509.txt"},{"from":"IETF RFC 4592","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4592/RFC-4592.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4955","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4955/RFC-4955.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 4986","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-4986/RFC-4986.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4035","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4057","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-4057/RFC-4057.txt"},{"from":"IETF RFC 4291","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-4291/RFC-4291.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4038","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 4039","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 404","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 4040","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 4040","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 4040","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 4043","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4044","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4044","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4045","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4046","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 4049","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 4049","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 4050","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4051","to":"IETF RFC 4050","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 4050","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 4050","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 4051","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4050","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-4050/RFC-4050.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 4051","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 4053","to":"IETF RFC 4052","kind":"references","source":"IETF/RFC-4053/RFC-4053.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 4052","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 4052","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 4052","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 4691","to":"IETF RFC 4053","kind":"references","source":"IETF/RFC-4691/RFC-4691.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 4053","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 4053","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4054","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"IETF RFC 4055","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4056","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-4056/RFC-4056.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5480","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5756","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5756/RFC-5756.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 4055","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4056","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4057","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 4739","to":"IETF RFC 4058","kind":"references","source":"IETF/RFC-4739/RFC-4739.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4058","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 4058","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 4065","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 4065","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4068","to":"IETF RFC 4065","kind":"references","source":"IETF/RFC-4068/RFC-4068.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 4065","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 4065","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 4066","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4066","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 4065","to":"IETF RFC 4067","kind":"references","source":"IETF/RFC-4065/RFC-4065.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4067","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4067","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 4066","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4066/RFC-4066.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4140","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4140/RFC-4140.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4068","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 739","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 407","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 4333","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-4333/RFC-4333.txt"},{"from":"IETF RFC 4371","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-4371/RFC-4371.txt"},{"from":"IETF RFC 4748","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-4748/RFC-4748.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 5377","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-5377/RFC-5377.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 4071","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4072","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 4073","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 4073","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4074","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4697","to":"IETF RFC 4074","kind":"references","source":"IETF/RFC-4697/RFC-4697.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4074","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 4074","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 4075","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4075","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4075","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 4242","to":"IETF RFC 4076","kind":"references","source":"IETF/RFC-4242/RFC-4242.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4076","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4076","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 4896","to":"IETF RFC 4077","kind":"references","source":"IETF/RFC-4896/RFC-4896.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 4077","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 4079","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4079","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 4080","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 4080","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-4080/RFC-4080.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 4081","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 4383","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-4383/RFC-4383.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 5052","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-5052/RFC-5052.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 4082","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4084","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4084","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4085","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4085","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 4004","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4004/RFC-4004.txt"},{"from":"IETF RFC 4107","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4107/RFC-4107.txt"},{"from":"IETF RFC 4108","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4122","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4193","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4193/RFC-4193.txt"},{"from":"IETF RFC 4211","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4211/RFC-4211.txt"},{"from":"IETF RFC 4226","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4226/RFC-4226.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4279","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4401","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4401/RFC-4401.txt"},{"from":"IETF RFC 4449","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4449/RFC-4449.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4493","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4493/RFC-4493.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4615","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4615/RFC-4615.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4880","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4895","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4895/RFC-4895.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5083","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5083/RFC-5083.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8032","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8032/RFC-8032.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9021","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9021/RFC-9021.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 4086","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 4086","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 4087","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4087","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 4087","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 4838","to":"IETF RFC 4088","kind":"references","source":"IETF/RFC-4838/RFC-4838.txt"},{"from":"IETF RFC 5674","to":"IETF RFC 4088","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 4105","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4105/RFC-4105.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4461","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4461/RFC-4461.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5029","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4090","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4092","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-4092/RFC-4092.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4091","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4091","to":"IETF RFC 4092","kind":"references","source":"IETF/RFC-4091/RFC-4091.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4092","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 4092","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4092","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 4093","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 4093","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4093","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4081","to":"IETF RFC 4094","kind":"references","source":"IETF/RFC-4081/RFC-4081.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 4094","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 4095","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4097","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 4098","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 4101","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 4102","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4102","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4102/RFC-4102.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4597","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4597/RFC-4597.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4103","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4105","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4106","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 4449","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-4449/RFC-4449.txt"},{"from":"IETF RFC 4564","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 4656","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-4656/RFC-4656.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4822","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-4822/RFC-4822.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 4107","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 4108","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 4109","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4109","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4109","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4110","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4111","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 4113","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4113","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 4113","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 4116","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 4116","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4116","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 4116","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 4116","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 4117","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 4564","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-4564/RFC-4564.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4118","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4189","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-4189/RFC-4189.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5808","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5808/RFC-5808.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 4119","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 412","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 412","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4121","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4121/RFC-4121.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4537","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 4120","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 4120","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4556","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 5554","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-5554/RFC-5554.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 4121","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"ETSI EN 319 522-2 V1.2.1","to":"IETF RFC 4122","kind":"references","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf"},{"from":"IETF RFC 4479","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4918","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6355","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6355/RFC-6355.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 4122","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4124","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 4125","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 4125","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 4125","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 4125","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 4125","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 4126","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 4126","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 4124","to":"IETF RFC 4127","kind":"references","source":"IETF/RFC-4124/RFC-4124.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 4127","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 4127","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4128","to":"IETF RFC 4127","kind":"references","source":"IETF/RFC-4128/RFC-4128.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 4127","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 4125","to":"IETF RFC 4128","kind":"references","source":"IETF/RFC-4125/RFC-4125.txt"},{"from":"IETF RFC 4126","to":"IETF RFC 4128","kind":"references","source":"IETF/RFC-4126/RFC-4126.txt"},{"from":"IETF RFC 4127","to":"IETF RFC 4128","kind":"references","source":"IETF/RFC-4127/RFC-4127.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 413","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 4132","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5932","to":"IETF RFC 4132","kind":"references","source":"IETF/RFC-5932/RFC-5932.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4132","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4181","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-4181/RFC-4181.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4789","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-4789/RFC-4789.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 4133","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 4357","to":"IETF RFC 4134","kind":"references","source":"IETF/RFC-4357/RFC-4357.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 4134","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 4134","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4134","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4135","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4135","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 4135","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 4222","to":"IETF RFC 4136","kind":"references","source":"IETF/RFC-4222/RFC-4222.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4137","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 4137","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 4138","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 4138","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 4138","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4138","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4139","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4139","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 4139","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 430","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 448","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-448/RFC-448.txt"},{"from":"IETF RFC 454","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 691","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 959","to":"IETF RFC 414","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4977","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-4977/RFC-4977.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4140","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 4142","to":"IETF RFC 4141","kind":"references","source":"IETF/RFC-4142/RFC-4142.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 4141","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 4143","to":"IETF RFC 4142","kind":"references","source":"IETF/RFC-4143/RFC-4143.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4142","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4143","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4143","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4145","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 4146","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4146","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 4146","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5560","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5644","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-5644/RFC-5644.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4148","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4150","to":"IETF RFC 4149","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 4149","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 4150","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 4150","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 4150","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4150","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 4151","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 4151","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 4151","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 4151","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 4133","to":"IETF RFC 4152","kind":"references","source":"IETF/RFC-4133/RFC-4133.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 4152","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 4152","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 4152","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 4155","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 4155","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 4158","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"IETF RFC 4556","to":"IETF RFC 4158","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4158","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4158","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 4158","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 4159","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4162","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4164","to":"IETF RFC 4163","kind":"references","source":"IETF/RFC-4164/RFC-4164.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4163","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4163","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4164","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4164","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 4780","to":"IETF RFC 4168","kind":"references","source":"IETF/RFC-4780/RFC-4780.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 4168","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4168","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4169","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4169","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4171","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 4172","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4174","to":"IETF RFC 4172","kind":"references","source":"IETF/RFC-4174/RFC-4174.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4172","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 4173","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4173","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 4173","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4173","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4171","to":"IETF RFC 4174","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4174","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4174","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4176","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4176","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4176","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4176","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 4177","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4178","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4559","to":"IETF RFC 4178","kind":"references","source":"IETF/RFC-4559/RFC-4559.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 4178","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4178","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 4178","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 4179","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 4179","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 430","to":"IETF RFC 418","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 454","to":"IETF RFC 418","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 4180","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 4180","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 4180","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 4180","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 4181","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4182","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 4182","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4182","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 4184","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 4184","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 4185","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 4186","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4187","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 4268","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-4268/RFC-4268.txt"},{"from":"IETF RFC 4318","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 4188","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 4189","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 4190","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4190","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4311","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-4311/RFC-4311.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5221","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-5221/RFC-5221.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4191","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 5142","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-5142/RFC-5142.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4192","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6177","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6177/RFC-6177.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 4193","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 4195","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 4195","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4196","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 4197","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 4197","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4197","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4197","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 4198","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 420","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4201","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4203","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4203/RFC-4203.txt"},{"from":"IETF RFC 4204","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4204/RFC-4204.txt"},{"from":"IETF RFC 4205","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4205/RFC-4205.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4202","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4203","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4204","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4201","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-4201/RFC-4201.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4206","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-4206/RFC-4206.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4205","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 4202","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4202/RFC-4202.txt"},{"from":"IETF RFC 4207","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4208","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4208/RFC-4208.txt"},{"from":"IETF RFC 4216","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4216/RFC-4216.txt"},{"from":"IETF RFC 4220","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4220/RFC-4220.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4420","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4420/RFC-4420.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4206","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4209","to":"IETF RFC 4207","kind":"references","source":"IETF/RFC-4209/RFC-4209.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 4207","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4394","to":"IETF RFC 4207","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4783","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-4783/RFC-4783.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4208","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 4209","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4209","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 4210","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 4210","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 4211","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 4214","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4214/RFC-4214.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 4213","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 4215","to":"IETF RFC 4214","kind":"references","source":"IETF/RFC-4215/RFC-4215.txt"},{"from":"IETF RFC 4554","to":"IETF RFC 4214","kind":"references","source":"IETF/RFC-4554/RFC-4554.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4214","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4214","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 4214","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4215","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4561","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-4561/RFC-4561.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4736","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-4736/RFC-4736.txt"},{"from":"IETF RFC 4874","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-4874/RFC-4874.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4216","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 4217","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4217","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4217","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4219","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-4219/RFC-4219.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 4218","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4219","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 422","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 443","to":"IETF RFC 422","kind":"references","source":"IETF/RFC-443/RFC-443.txt"},{"from":"IETF RFC 4221","to":"IETF RFC 4220","kind":"references","source":"IETF/RFC-4221/RFC-4221.txt"},{"from":"IETF RFC 4327","to":"IETF RFC 4220","kind":"references","source":"IETF/RFC-4327/RFC-4327.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4220","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4220","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4221","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4221","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4221","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 4222","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 4223","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 4223","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4224","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4225","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 4449","to":"IETF RFC 4226","kind":"references","source":"IETF/RFC-4449/RFC-4449.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 4226","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4226","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 4227","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 4227","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 4230","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4230","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4230","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 4634","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-4634/RFC-4634.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 4231","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4141","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4141/RFC-4141.txt"},{"from":"IETF RFC 4198","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4240","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4288","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4288/RFC-4288.txt"},{"from":"IETF RFC 4314","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4315","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4315/RFC-4315.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4463","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4466","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4466/RFC-4466.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4627","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4627/RFC-4627.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4644","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4644/RFC-4644.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4694","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 4715","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4731","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4731/RFC-4731.txt"},{"from":"IETF RFC 4759","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4759/RFC-4759.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4848","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4848/RFC-4848.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4904","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4904/RFC-4904.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 4997","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 4234","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4235","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4238","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 4313","to":"IETF RFC 4240","kind":"references","source":"IETF/RFC-4313/RFC-4313.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 4240","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 4240","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4240","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 4240","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 4339","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-4339/RFC-4339.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4242","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 4679","to":"IETF RFC 4243","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 4458","to":"IETF RFC 4244","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 4244","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 4244","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4244","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4353","to":"IETF RFC 4245","kind":"references","source":"IETF/RFC-4353/RFC-4353.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 4245","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4245","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 4245","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 4224","to":"IETF RFC 4247","kind":"references","source":"IETF/RFC-4224/RFC-4224.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4345","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4345/RFC-4345.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 4250","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4345","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4345/RFC-4345.txt"},{"from":"IETF RFC 4419","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4419/RFC-4419.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 4251","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 4252","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4254","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4255","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4255/RFC-4255.txt"},{"from":"IETF RFC 4256","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4345","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4345/RFC-4345.txt"},{"from":"IETF RFC 4419","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4419/RFC-4419.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 4253","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 4254","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4255","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4255","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4256","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4258","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4258","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 4258","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 4326","to":"IETF RFC 4259","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4259","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5163","to":"IETF RFC 4259","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4259","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4261","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5756","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-5756/RFC-5756.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 4262","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 4265","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4267","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4268","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 4268","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 4268","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 4269","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 4269","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6194","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6194/RFC-6194.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4270","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 4272","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4272/RFC-4272.txt"},{"from":"IETF RFC 4273","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4273/RFC-4273.txt"},{"from":"IETF RFC 4278","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4278/RFC-4278.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4456","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4456/RFC-4456.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4724","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4724/RFC-4724.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4760","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4760/RFC-4760.txt"},{"from":"IETF RFC 4781","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4781/RFC-4781.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4893","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4893/RFC-4893.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5148","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5148/RFC-5148.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5701","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5701/RFC-5701.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 4271","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4272","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4273","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 4273","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 4278","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 4278","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4278","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5036","to":"IETF RFC 4278","kind":"references","source":"IETF/RFC-5036/RFC-5036.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4278","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4785","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-4785/RFC-4785.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4279","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4280","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4280","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 4186","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4284","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4284/RFC-4284.txt"},{"from":"IETF RFC 4372","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4372/RFC-4372.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 4763","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4763/RFC-4763.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 4282","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4283","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4284","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 4284","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4284","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 4284","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 4284","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 4283","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-4283/RFC-4283.txt"},{"from":"IETF RFC 4640","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-4640/RFC-4640.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4285","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4541","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-4541/RFC-4541.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 4286","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4946","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-4946/RFC-4946.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 5829","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5829/RFC-5829.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 4287","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 4287","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4287/RFC-4287.txt"},{"from":"IETF RFC 4289","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4289/RFC-4289.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4598","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4598/RFC-4598.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4685","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4685/RFC-4685.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4735","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4735/RFC-4735.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5877","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6351","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6351/RFC-6351.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4288","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4289","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 739","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 429","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 4290","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4713","to":"IETF RFC 4290","kind":"references","source":"IETF/RFC-4713/RFC-4713.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 4290","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 4290","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 4290","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4489","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4489/RFC-4489.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4692","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4692/RFC-4692.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4795","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5444","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5498","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5498/RFC-5498.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5548","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5548/RFC-5548.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7346","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7346/RFC-7346.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 4291","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 4292","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4292","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4292","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4292","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 4292","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 4292","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 4293","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 4389","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-4389/RFC-4389.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4966","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-4966/RFC-4966.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4294","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 4297","to":"IETF RFC 4296","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 4296","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 4296","to":"IETF RFC 4297","kind":"references","source":"IETF/RFC-4296/RFC-4296.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 4297","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 4297","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4297","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 430","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 430","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 451","to":"IETF RFC 430","kind":"references","source":"IETF/RFC-451/RFC-451.txt"},{"from":"IETF RFC 463","to":"IETF RFC 430","kind":"references","source":"IETF/RFC-463/RFC-463.txt"},{"from":"IETF RFC 959","to":"IETF RFC 430","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4398","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4398/RFC-4398.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4459","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4459/RFC-4459.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4807","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4818","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4818/RFC-4818.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5444","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 4301","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4410","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4410/RFC-4410.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4494","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4494/RFC-4494.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4764","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4764/RFC-4764.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 4302","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4304","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4304/RFC-4304.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4312","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4418","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4418/RFC-4418.txt"},{"from":"IETF RFC 4494","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4494/RFC-4494.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4705","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4705/RFC-4705.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4303","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4304","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4304","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4304","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4346","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4305","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 4230","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4230/RFC-4230.txt"},{"from":"IETF RFC 4285","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4285/RFC-4285.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4307","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4307/RFC-4307.txt"},{"from":"IETF RFC 4308","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4308/RFC-4308.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4359","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4359/RFC-4359.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4423","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4423/RFC-4423.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4434","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4434/RFC-4434.txt"},{"from":"IETF RFC 4478","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4478/RFC-4478.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4552","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4552/RFC-4552.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4615","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4615/RFC-4615.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4739","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4739/RFC-4739.txt"},{"from":"IETF RFC 4753","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 4754","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4793","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4806","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4806/RFC-4806.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4817","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4817/RFC-4817.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5903","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4306","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 5106","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5106/RFC-5106.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 4307","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4308","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4308","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4308","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4308","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4308","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 4543","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-4543/RFC-4543.txt"},{"from":"IETF RFC 4835","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-4835/RFC-4835.txt"},{"from":"IETF RFC 5116","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-5116/RFC-5116.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4309","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4310","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 4310","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4311","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4311","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 6419","to":"IETF RFC 4311","kind":"references","source":"IETF/RFC-6419/RFC-6419.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4311","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4311","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 5528","to":"IETF RFC 4312","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 4312","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4312","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4313","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4314","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4315","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 4317","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 4318","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4318","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4706","to":"IETF RFC 4319","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 4319","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4321","to":"IETF RFC 4320","kind":"references","source":"IETF/RFC-4321/RFC-4321.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 4320","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4320","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4320","to":"IETF RFC 4321","kind":"references","source":"IETF/RFC-4320/RFC-4320.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 4321","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 4321","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4322","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4322","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 4322","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 4363","to":"IETF RFC 4323","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4325","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4326","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5163","to":"IETF RFC 4326","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4326","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 4327","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 4328","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 4329","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4330","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 4331","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 5620","to":"IETF RFC 4333","kind":"references","source":"IETF/RFC-5620/RFC-5620.txt"},{"from":"IETF RFC 4746","to":"IETF RFC 4334","kind":"references","source":"IETF/RFC-4746/RFC-4746.txt"},{"from":"IETF RFC 5113","to":"IETF RFC 4334","kind":"references","source":"IETF/RFC-5113/RFC-5113.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4334","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 4334","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4336","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 4337","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 4595","to":"IETF RFC 4338","kind":"references","source":"IETF/RFC-4595/RFC-4595.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 4338","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4338","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4338","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4338","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4339","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 4339","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4339","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 4339","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4339","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 434","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4336","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4336/RFC-4336.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5129","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5129/RFC-5129.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4340","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4342","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-4342/RFC-4342.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 4341","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4774","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-4774/RFC-4774.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 4342","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4343","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 4345","to":"IETF RFC 4344","kind":"references","source":"IETF/RFC-4345/RFC-4345.txt"},{"from":"IETF RFC 6229","to":"IETF RFC 4345","kind":"references","source":"IETF/RFC-6229/RFC-6229.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4366","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4422","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4590","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4590/RFC-4590.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4680","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4680/RFC-4680.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 4785","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4785/RFC-4785.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 5005","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5005/RFC-5005.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5023","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5055","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 5091","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5091/RFC-5091.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5158","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5158/RFC-5158.txt"},{"from":"IETF RFC 5189","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5189/RFC-5189.txt"},{"from":"IETF RFC 5209","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5469","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5469/RFC-5469.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7465","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7465/RFC-7465.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 4346","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5238","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5238/RFC-5238.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 4347","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 4591","to":"IETF RFC 4349","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4349","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4349","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 451","to":"IETF RFC 435","kind":"references","source":"IETF/RFC-451/RFC-451.txt"},{"from":"IETF RFC 4354","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4376","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4376/RFC-4376.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4597","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4597/RFC-4597.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5167","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-5167/RFC-5167.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 4353","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 4354","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4355","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4356","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 4491","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 5830","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-5830/RFC-5830.txt"},{"from":"IETF RFC 5832","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4357","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 4359","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 436","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4364","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4364/RFC-4364.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4384","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4384/RFC-4384.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5668","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-5668/RFC-5668.txt"},{"from":"IETF RFC 5701","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-5701/RFC-5701.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 4360","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4477","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-4477/RFC-4477.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4361","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 4362","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4663","to":"IETF RFC 4363","kind":"references","source":"IETF/RFC-4663/RFC-4663.txt"},{"from":"IETF RFC 4675","to":"IETF RFC 4363","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4363","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4360","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4360/RFC-4360.txt"},{"from":"IETF RFC 4365","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4365/RFC-4365.txt"},{"from":"IETF RFC 4382","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4382/RFC-4382.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4655","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4655/RFC-4655.txt"},{"from":"IETF RFC 4659","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4659/RFC-4659.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 4364","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 4365","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 4365","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 4365","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4365","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 4492","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4507","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4507/RFC-4507.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4680","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4680/RFC-4680.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5019","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5019/RFC-5019.txt"},{"from":"IETF RFC 5054","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5054/RFC-5054.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5216","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5216/RFC-5216.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4366","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 4367","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 4748","to":"IETF RFC 4371","kind":"references","source":"IETF/RFC-4748/RFC-4748.txt"},{"from":"IETF RFC 5377","to":"IETF RFC 4371","kind":"references","source":"IETF/RFC-5377/RFC-5377.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 4371","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 4372","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 4376","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4376","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4376","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 4378","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-4378/RFC-4378.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4377","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4378","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 4379","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 438","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 430","to":"IETF RFC 438","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 454","to":"IETF RFC 438","kind":"references","source":"IETF/RFC-454/RFC-454.txt"},{"from":"IETF RFC 959","to":"IETF RFC 438","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4472","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4472/RFC-4472.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4380","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4382","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4382","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 4442","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-4442/RFC-4442.txt"},{"from":"IETF RFC 4563","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-4563/RFC-4563.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 4383","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 4384","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4928","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-4928/RFC-4928.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5586","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4385","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 4386","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 4386","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 4387","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 4387","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4388","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 4389","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 4390","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 4391","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4392","to":"IETF RFC 4391","kind":"references","source":"IETF/RFC-4392/RFC-4392.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 4391","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 4391","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4391","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 4392","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 4393","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 4397","to":"IETF RFC 4394","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5781","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5781/RFC-5781.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6694","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-6694/RFC-6694.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 4395","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 4397","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4397","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 4397","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 4398","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4398","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8078","to":"IETF RFC 4398","kind":"references","source":"IETF/RFC-8078/RFC-8078.txt"},{"from":"IETF RFC 4402","to":"IETF RFC 4401","kind":"references","source":"IETF/RFC-4402/RFC-4402.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4401","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4402","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 4405","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 4405","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 4405","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4405","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 4405","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 4406","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 4407","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4408","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 4409","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 739","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 870","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 900","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 441","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4410","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4412","to":"IETF RFC 4411","kind":"references","source":"IETF/RFC-4412/RFC-4412.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 4411","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 4411","to":"IETF RFC 4412","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4504","to":"IETF RFC 4412","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4542","to":"IETF RFC 4412","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 4412","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4412","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 4413","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4413","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4413","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4415","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 4418","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4462","to":"IETF RFC 4419","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4419","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 4419","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 442","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5420","to":"IETF RFC 4420","kind":"references","source":"IETF/RFC-5420/RFC-5420.txt"},{"from":"IETF RFC 4505","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4616","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4622","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 4752","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 4978","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4978/RFC-4978.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4422","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 4423","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 4427","to":"IETF RFC 4426","kind":"references","source":"IETF/RFC-4427/RFC-4427.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4426","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 4426","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4426","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4426","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-4426/RFC-4426.txt"},{"from":"IETF RFC 4428","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-4428/RFC-4428.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4427","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4427","to":"IETF RFC 4428","kind":"references","source":"IETF/RFC-4427/RFC-4427.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4428","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 4429","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 443","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4430","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4430","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4430","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4430","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 4430","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 4431","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 4615","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-4615/RFC-4615.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4434","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4555","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-4555/RFC-4555.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 4436","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 4437","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4442","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4442","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 4442","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 4620","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4620/RFC-4620.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4443","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4444","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4667","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4667/RFC-4667.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4863","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-4863/RFC-4863.txt"},{"from":"IETF RFC 5003","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5003/RFC-5003.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4446","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4448","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4717","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4842","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4863","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-4863/RFC-4863.txt"},{"from":"IETF RFC 5003","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5003/RFC-5003.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5542","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 4447","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 4446","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4446/RFC-4446.txt"},{"from":"IETF RFC 4447","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4447/RFC-4447.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 4448","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 4651","to":"IETF RFC 4449","kind":"references","source":"IETF/RFC-4651/RFC-4651.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 4449","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4449","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 44520","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 4453","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 4453","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4454","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4454","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4454","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4454","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 4684","to":"IETF RFC 4456","kind":"references","source":"IETF/RFC-4684/RFC-4684.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4456","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 5065","to":"IETF RFC 4456","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 4456","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 4456","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4458","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4459","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4460","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 4460","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 4687","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-4687/RFC-4687.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4461","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 4462","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 5587","to":"IETF RFC 4462","kind":"references","source":"IETF/RFC-5587/RFC-5587.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4462","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4463","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 4469","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-4469/RFC-4469.txt"},{"from":"IETF RFC 4551","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-4551/RFC-4551.txt"},{"from":"IETF RFC 4731","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-4731/RFC-4731.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4466","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4468","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-4468/RFC-4468.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4467","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 4467","to":"IETF RFC 4468","kind":"references","source":"IETF/RFC-4467/RFC-4467.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4468","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4468","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 4468","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4468","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 4469","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 5074","to":"IETF RFC 4470","kind":"references","source":"IETF/RFC-5074/RFC-5074.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4470","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 4470","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4470","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4472","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4472","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4472","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 4472","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 4916","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-4916/RFC-4916.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 4474","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 4474","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-4474/RFC-4474.txt"},{"from":"IETF RFC 4488","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-4488/RFC-4488.txt"},{"from":"IETF RFC 4538","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-4538/RFC-4538.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 4475","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4477","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4477","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4477","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4477","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4478","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 4479","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 448","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 430","to":"IETF RFC 448","kind":"references","source":"IETF/RFC-430/RFC-430.txt"},{"from":"IETF RFC 959","to":"IETF RFC 448","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4479","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4479/RFC-4479.txt"},{"from":"IETF RFC 4481","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4481/RFC-4481.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 4745","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4745/RFC-4745.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 4480","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 4482","to":"IETF RFC 4481","kind":"references","source":"IETF/RFC-4482/RFC-4482.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 4481","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 4482","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 4482","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 4485","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-4485/RFC-4485.txt"},{"from":"IETF RFC 4662","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-4662/RFC-4662.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4483","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4485","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4485","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4487","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 4488","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 4488","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 4488","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 4489","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4490","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 4490","to":"IETF RFC 4491","kind":"references","source":"IETF/RFC-4490/RFC-4490.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4491","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4491","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4492","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4494","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-4494/RFC-4494.txt"},{"from":"IETF RFC 4615","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-4615/RFC-4615.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 4493","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4494","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4497","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 4501","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 4501","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 4502","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4502","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4502","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 4502","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4502","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 4504","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 4504","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4504","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4505","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4505","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4505","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4505","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4505","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5663","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5663/RFC-5663.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 8391","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-8391/RFC-8391.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 4506","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 4507","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4507","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4507","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4507","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4641","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-4641/RFC-4641.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 4509","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 491","to":"IETF RFC 451","kind":"references","source":"IETF/RFC-491/RFC-491.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 4510","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 4511","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 4512","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4513","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"IETF RFC 4514","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"IETF RFC 4514","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"IETF RFC 4510","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4514","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4515","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4515","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4515","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 4515","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4515","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 4516","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"IETF RFC 4510","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4520","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 4516","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4518","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 4517","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 4518","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"ETSI TS 119 412-6 V1.2.1","to":"IETF RFC 4519","kind":"references","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf"},{"from":"IETF RFC 4510","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5941","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 4519","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4516","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4521","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4524","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 4531","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4520","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 4510","to":"IETF RFC 4521","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4521","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 4522","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4517","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4522","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 5126","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4523","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 4519","to":"IETF RFC 4524","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 453","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4531","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4535","to":"IETF RFC 4534","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4534","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-4534/RFC-4534.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4535","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4757","to":"IETF RFC 4537","kind":"references","source":"IETF/RFC-4757/RFC-4757.txt"},{"from":"IETF RFC 4964","to":"IETF RFC 4538","kind":"references","source":"IETF/RFC-4964/RFC-4964.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 4538","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 4538","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4538","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 2235","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-2235/RFC-2235.txt"},{"from":"IETF RFC 448","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-448/RFC-448.txt"},{"from":"IETF RFC 463","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-463/RFC-463.txt"},{"from":"IETF RFC 468","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-468/RFC-468.txt"},{"from":"IETF RFC 691","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 739","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 959","to":"IETF RFC 454","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4540","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4540","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 463","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-463/RFC-463.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4968","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-4968/RFC-4968.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5154","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 4541","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 4542","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4543","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4546","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 4549","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4549","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4549","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 4549","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4549","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 455","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 482","to":"IETF RFC 455","kind":"references","source":"IETF/RFC-482/RFC-482.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 4550","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 4550","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4550","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4550","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4550","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-4550/RFC-4550.txt"},{"from":"IETF RFC 4731","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-4731/RFC-4731.txt"},{"from":"IETF RFC 5161","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5161/RFC-5161.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4551","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 4552","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 4553","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4554","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 501","to":"IETF RFC 4554","kind":"references","source":"IETF/RFC-501/RFC-501.txt"},{"from":"IETF RFC 4621","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-4621/RFC-4621.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 5164","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5164/RFC-5164.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4555","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 4556","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4556","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 4556","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 4559","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4559","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 4560","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4560","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4561","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 4779","to":"IETF RFC 4562","kind":"references","source":"IETF/RFC-4779/RFC-4779.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 4562","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4563","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 4909","to":"IETF RFC 4563","kind":"references","source":"IETF/RFC-4909/RFC-4909.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4563","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4563","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 4563","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4564","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4564","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4570","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4571","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4571/RFC-4571.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4585","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4756","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4756/RFC-4756.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5118","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5118/RFC-5118.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5159","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5159/RFC-5159.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5194","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 4566","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4568","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-4568/RFC-4568.txt"},{"from":"IETF RFC 4650","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4567","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4566","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4567","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-4567/RFC-4567.txt"},{"from":"IETF RFC 5027","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5027/RFC-5027.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6188","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-6188/RFC-6188.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 4568","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4570","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 4570","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4570","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4572","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 4571","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4572","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4575","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 4796","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-4796/RFC-4796.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4574","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 4574","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-4574/RFC-4574.txt"},{"from":"IETF RFC 4579","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-4579/RFC-4579.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 5117","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 4575","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 4577","to":"IETF RFC 4576","kind":"references","source":"IETF/RFC-4577/RFC-4577.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 4576","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4576","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 4576","to":"IETF RFC 4577","kind":"references","source":"IETF/RFC-4576/RFC-4576.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4578","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 4578","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 6355","to":"IETF RFC 4578","kind":"references","source":"IETF/RFC-6355/RFC-6355.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4578","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4578","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5359","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-5359/RFC-5359.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 4579","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 458","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 475","to":"IETF RFC 458","kind":"references","source":"IETF/RFC-475/RFC-475.txt"},{"from":"IETF RFC 959","to":"IETF RFC 458","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 4580","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 4982","to":"IETF RFC 4581","kind":"references","source":"IETF/RFC-4982/RFC-4982.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4581","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4581","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4581","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 4583","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-4583/RFC-4583.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4582","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4582","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4583","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4584","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 4584","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 4587","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 4588","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-4588/RFC-4588.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5117","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5124","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5124/RFC-5124.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4585","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 4587","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 4587","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 4587","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 4588","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 4480","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-4480/RFC-4480.txt"},{"from":"IETF RFC 4676","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4589","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 459","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 514","to":"IETF RFC 459","kind":"references","source":"IETF/RFC-514/RFC-514.txt"},{"from":"IETF RFC 531","to":"IETF RFC 459","kind":"references","source":"IETF/RFC-531/RFC-531.txt"},{"from":"IETF RFC 4740","to":"IETF RFC 4590","kind":"references","source":"IETF/RFC-4740/RFC-4740.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 4590","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4591","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4591","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4592","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5668","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5668/RFC-5668.txt"},{"from":"IETF RFC 5701","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5701/RFC-5701.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4593","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 5127","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-5127/RFC-5127.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4594","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 4595","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4595","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4595","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4597","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4597","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 4597","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 4598","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 459","to":"IETF RFC 460","kind":"references","source":"IETF/RFC-459/RFC-459.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4608","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4608/RFC-4608.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4610","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4610/RFC-4610.txt"},{"from":"IETF RFC 4732","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4732/RFC-4732.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5384","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5384/RFC-5384.txt"},{"from":"IETF RFC 5496","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5496/RFC-5496.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6807","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6807/RFC-6807.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 4601","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 4605","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-4605/RFC-4605.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 4604","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 4605","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 4606","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4604","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-4604/RFC-4604.txt"},{"from":"IETF RFC 4609","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-4609/RFC-4609.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5496","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5496/RFC-5496.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4607","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4608","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4608","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 4601","to":"IETF RFC 4609","kind":"references","source":"IETF/RFC-4601/RFC-4601.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4609","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 4609","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4609","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 4609","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4610","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4614","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4615","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4615","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4615","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4615","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4615","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4616","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4618","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4618","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 4618","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4618","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 4618","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 4619","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4619","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4619","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 4890","to":"IETF RFC 4620","kind":"references","source":"IETF/RFC-4890/RFC-4890.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4621","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4770","to":"IETF RFC 4622","kind":"references","source":"IETF/RFC-4770/RFC-4770.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 4622","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 4618","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4719","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-4719/RFC-4719.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5542","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-5542/RFC-5542.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4623","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6839","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 4627","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 4629","to":"IETF RFC 4628","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 4629","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 4629","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 463","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 463","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4851","to":"IETF RFC 4630","kind":"references","source":"IETF/RFC-4851/RFC-4851.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4630","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 4864","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-4864/RFC-4864.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4984","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-4984/RFC-4984.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 4632","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 4635","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-4635/RFC-4635.txt"},{"from":"IETF RFC 4808","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-4808/RFC-4808.txt"},{"from":"IETF RFC 4868","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-4868/RFC-4868.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5008","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5008/RFC-5008.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6229","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-6229/RFC-6229.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 4634","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 4635","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 4635","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 4635","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 4635","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4635","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 4721","to":"IETF RFC 4636","kind":"references","source":"IETF/RFC-4721/RFC-4721.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4637","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4640","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 4640","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 4640","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4640","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 4640","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4641","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4642","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 4643","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4642","to":"IETF RFC 4643","kind":"references","source":"IETF/RFC-4642/RFC-4642.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4643","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4643","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 4643","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 4644","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4644","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 4645","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 4645","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5645","to":"IETF RFC 4645","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 4645","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 4645","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4647","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-4647/RFC-4647.txt"},{"from":"IETF RFC 4690","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4790","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 5013","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5013/RFC-5013.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5645","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 4646","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 4646","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 4647","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 4648","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"IETF RFC 4648","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 4648","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 3977","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4643","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-4643/RFC-4643.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4954","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-4954/RFC-4954.txt"},{"from":"IETF RFC 4959","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-4959/RFC-4959.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9285","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 4648","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 4649","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 4649","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 4649","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 4738","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4650","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 4866","to":"IETF RFC 4651","kind":"references","source":"IETF/RFC-4866/RFC-4866.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4651","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4651","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 4653","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 4653","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 4653","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4653","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 4653","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 4654","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4654","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 4654","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4654","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4654","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 4657","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-4657/RFC-4657.txt"},{"from":"IETF RFC 4674","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-4674/RFC-4674.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4655","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 4656","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 4674","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-4674/RFC-4674.txt"},{"from":"IETF RFC 4726","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-4726/RFC-4726.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4657","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4659","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 4660","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 4660","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 4661","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 4662","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 4660","to":"IETF RFC 4663","kind":"references","source":"IETF/RFC-4660/RFC-4660.txt"},{"from":"IETF RFC 4661","to":"IETF RFC 4663","kind":"references","source":"IETF/RFC-4661/RFC-4661.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4663","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4663","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4665","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4667","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-4667/RFC-4667.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 4847","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-4847/RFC-4847.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4664","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 4664","to":"IETF RFC 4665","kind":"references","source":"IETF/RFC-4664/RFC-4664.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4665","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4665","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4665","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 4665","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4667","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4667","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 4669","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-4669/RFC-4669.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4668","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4668","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-4668/RFC-4668.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4669","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 467","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 501","to":"IETF RFC 467","kind":"references","source":"IETF/RFC-501/RFC-501.txt"},{"from":"IETF RFC 4671","to":"IETF RFC 4670","kind":"references","source":"IETF/RFC-4671/RFC-4671.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4670","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4670","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4670","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4670","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4670","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-4670/RFC-4670.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4671","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4673","to":"IETF RFC 4672","kind":"references","source":"IETF/RFC-4673/RFC-4673.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4672","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4672","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4672","to":"IETF RFC 4673","kind":"references","source":"IETF/RFC-4672/RFC-4672.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 4673","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4673","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4927","to":"IETF RFC 4674","kind":"references","source":"IETF/RFC-4927/RFC-4927.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 4674","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 4674","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4674","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4674","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4675","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4675","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4675","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4675","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4776","to":"IETF RFC 4676","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4679","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 468","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 468","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 3652","to":"IETF RFC 468","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 959","to":"IETF RFC 468","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4681","to":"IETF RFC 4680","kind":"references","source":"IETF/RFC-4681/RFC-4681.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 4680","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 4680","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 4680","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4680","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4681","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4683","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 4684","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4684","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4684","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4684","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4684","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 4685","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 5016","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-5016/RFC-5016.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 4686","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 4834","to":"IETF RFC 4687","kind":"references","source":"IETF/RFC-4834/RFC-4834.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 4687","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 4687","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4687","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 469","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 4690","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 4691","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4692","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4693","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 4694","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4694","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4697","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4697","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4697","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 4701","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 4701","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 4701","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4702","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 4701","to":"IETF RFC 4703","kind":"references","source":"IETF/RFC-4701/RFC-4701.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 4703","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4704","to":"IETF RFC 4703","kind":"references","source":"IETF/RFC-4704/RFC-4704.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 4703","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 4703","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 4703","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-4703/RFC-4703.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4704","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4705","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5650","to":"IETF RFC 4706","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4706","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 4706","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 4710","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 4710","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 4710","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4710","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 4711","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4711","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 4712","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4711","to":"IETF RFC 4712","kind":"references","source":"IETF/RFC-4711/RFC-4711.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4712","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4712","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 4713","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 4713","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 4713","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4714","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 4714","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 4715","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 4716","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4717","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 4717","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 4891","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-4891/RFC-4891.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4718","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 4720","to":"IETF RFC 4719","kind":"references","source":"IETF/RFC-4720/RFC-4720.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 4719","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 4719","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4720","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 4742","to":"IETF RFC 4721","kind":"references","source":"IETF/RFC-4742/RFC-4742.txt"},{"from":"IETF RFC 4857","to":"IETF RFC 4721","kind":"references","source":"IETF/RFC-4857/RFC-4857.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 4721","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 4721","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 4730","to":"IETF RFC 4722","kind":"references","source":"IETF/RFC-4730/RFC-4730.txt"},{"from":"IETF RFC 4781","to":"IETF RFC 4724","kind":"references","source":"IETF/RFC-4781/RFC-4781.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 4724","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4724","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 4724","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4726","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 4775","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-4775/RFC-4775.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5871","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-5871/RFC-5871.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 4727","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 473","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4722","to":"IETF RFC 4730","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4730","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5057","to":"IETF RFC 4730","kind":"references","source":"IETF/RFC-5057/RFC-5057.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 4730","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 4731","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 4731","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4731","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 4731","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4731","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6386","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6386/RFC-6386.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4732","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 4734","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5167","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-5167/RFC-5167.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 4733","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 4733","to":"IETF RFC 4734","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 4734","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 4734","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 4735","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4736","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4736","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5481","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 4737","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4738","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 4739","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4739","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4739","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5090","to":"IETF RFC 4740","kind":"references","source":"IETF/RFC-5090/RFC-5090.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 4740","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4740","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 4743","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-4743/RFC-4743.txt"},{"from":"IETF RFC 4744","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-4744/RFC-4744.txt"},{"from":"IETF RFC 5277","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5277/RFC-5277.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5717","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5717/RFC-5717.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 4741","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 4741","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-4741/RFC-4741.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 4742","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4743","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4744","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4745","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4746","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4748","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 4748","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 4748","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 475","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 491","to":"IETF RFC 475","kind":"references","source":"IETF/RFC-491/RFC-491.txt"},{"from":"IETF RFC 959","to":"IETF RFC 475","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 4750","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 4750","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4750","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 4750","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 5034","to":"IETF RFC 4752","kind":"references","source":"IETF/RFC-5034/RFC-5034.txt"},{"from":"IETF RFC 5092","to":"IETF RFC 4752","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 4752","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4752","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4752","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 4754","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-4754/RFC-4754.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5114","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5903","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 4753","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 4754","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 4756","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 4756","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 4756","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 4756","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 4756","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4757","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 4757","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 4758","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 4758","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 4759","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4797","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-4797/RFC-4797.txt"},{"from":"IETF RFC 4798","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-4798/RFC-4798.txt"},{"from":"IETF RFC 4852","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-4852/RFC-4852.txt"},{"from":"IETF RFC 5015","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5015/RFC-5015.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 5512","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5512/RFC-5512.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 4760","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 4762","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4761","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 4761","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 4762","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4763","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4763","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4764","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 4764","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 4766","to":"IETF RFC 4765","kind":"references","source":"IETF/RFC-4766/RFC-4766.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 4765","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 4765","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 4766","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4769","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 4770","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 5159","to":"IETF RFC 4771","kind":"references","source":"IETF/RFC-5159/RFC-5159.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4771","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4771","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4771","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 4772","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 4843","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-4843/RFC-4843.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5736","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-5736/RFC-5736.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 4773","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 4774","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 4929","to":"IETF RFC 4775","kind":"references","source":"IETF/RFC-4929/RFC-4929.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 4775","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4775","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 5139","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 4776","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 4778","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 4778","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4778","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4778","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4779","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4779","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4779","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4779","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4779","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 478","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 478","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4780","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4781","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5033","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-5033/RFC-5033.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4782","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 4783","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4783","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4783","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 4785","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 4785","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4785","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4786","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5135","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5135/RFC-5135.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4787","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 4788","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 4789","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4789","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 479","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 479","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4791","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-4791/RFC-4791.txt"},{"from":"IETF RFC 5051","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5051/RFC-5051.txt"},{"from":"IETF RFC 5228","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5235","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5235/RFC-5235.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 4790","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 4791","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 6585","to":"IETF RFC 4791","kind":"references","source":"IETF/RFC-6585/RFC-6585.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 4791","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4791","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 4791","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4793","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6982","to":"IETF RFC 4794","kind":"references","source":"IETF/RFC-6982/RFC-6982.txt"},{"from":"IETF RFC 7120","to":"IETF RFC 4794","kind":"references","source":"IETF/RFC-7120/RFC-7120.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 4794","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4795","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4796","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4797","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 4798","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 480","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 480","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 4801","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 4803","to":"IETF RFC 4802","kind":"references","source":"IETF/RFC-4803/RFC-4803.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4802","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 4802","to":"IETF RFC 4803","kind":"references","source":"IETF/RFC-4802/RFC-4802.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4803","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 4805","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 4806","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4806","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4806","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4806","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 4806","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4807","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4808","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4808","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 4808","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4809","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4998","to":"IETF RFC 4810","kind":"references","source":"IETF/RFC-4998/RFC-4998.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 4810","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 4810","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 4810","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 4812","to":"IETF RFC 4811","kind":"references","source":"IETF/RFC-4812/RFC-4812.txt"},{"from":"IETF RFC 4813","to":"IETF RFC 4811","kind":"references","source":"IETF/RFC-4813/RFC-4813.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 4811","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 4813","to":"IETF RFC 4812","kind":"references","source":"IETF/RFC-4813/RFC-4813.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 4812","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 4811","to":"IETF RFC 4813","kind":"references","source":"IETF/RFC-4811/RFC-4811.txt"},{"from":"IETF RFC 4812","to":"IETF RFC 4813","kind":"references","source":"IETF/RFC-4812/RFC-4812.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 4813","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 4813","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 4814","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 4815","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 4815","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4816","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4817","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 4817","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 4818","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4818","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4818","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4818","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4818","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 482","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4820","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 4820","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-4820/RFC-4820.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4821","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 4822","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 4822","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 4822","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4822","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4823","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4826","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-4826/RFC-4826.txt"},{"from":"IETF RFC 4827","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-4827/RFC-4827.txt"},{"from":"IETF RFC 5025","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5025/RFC-5025.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 4825","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 4825","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4826","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4827","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 4828","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 5348","to":"IETF RFC 4828","kind":"references","source":"IETF/RFC-5348/RFC-5348.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 4828","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4828","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 4828","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4830","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 4832","to":"IETF RFC 4830","kind":"references","source":"IETF/RFC-4832/RFC-4832.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4830","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 4830","to":"IETF RFC 4831","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4831","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 4831","to":"IETF RFC 4832","kind":"references","source":"IETF/RFC-4831/RFC-4831.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4832","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 4832","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 4833","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4833","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 4834","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 4834","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4834","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4835","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 5050","to":"IETF RFC 4838","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 4838","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 4838","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 4840","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4840","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 4842","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4842","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 5156","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-5156/RFC-5156.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5338","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-5338/RFC-5338.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 4843","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 4845","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-4845/RFC-4845.txt"},{"from":"IETF RFC 4846","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-4846/RFC-4846.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5620","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5620/RFC-5620.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 4844","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4845","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 4845","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4846","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 4846","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 4846","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 5195","to":"IETF RFC 4847","kind":"references","source":"IETF/RFC-5195/RFC-5195.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4847","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 4847","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4847","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 4848","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 4848","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 4848","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 4848","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 5176","to":"IETF RFC 4849","kind":"references","source":"IETF/RFC-5176/RFC-5176.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 4849","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 4850","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 5077","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-5077/RFC-5077.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 4851","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4852","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 4852","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4852","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 4853","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4854","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 4854","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 4856","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-4856/RFC-4856.txt"},{"from":"IETF RFC 4867","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5109","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 5188","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-5188/RFC-5188.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 4855","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 4855","to":"IETF RFC 4856","kind":"references","source":"IETF/RFC-4855/RFC-4855.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 4856","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 4857","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 4857","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 4858","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4943","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-4943/RFC-4943.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5175","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5175/RFC-5175.txt"},{"from":"IETF RFC 5180","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5180/RFC-5180.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6105","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6105/RFC-6105.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4861","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4941","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-4941/RFC-4941.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 5006","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5006/RFC-5006.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5080","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5080/RFC-5080.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 6603","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6603/RFC-6603.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4862","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 4863","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4864","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4866","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 4867","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 4867","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 4867","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 4867","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 4869","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-4869/RFC-4869.txt"},{"from":"IETF RFC 4894","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-4894/RFC-4894.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7539","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-7539/RFC-7539.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 4868","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 4869","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4869","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 4869","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 4869","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 487","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 501","to":"IETF RFC 487","kind":"references","source":"IETF/RFC-501/RFC-501.txt"},{"from":"IETF RFC 505","to":"IETF RFC 487","kind":"references","source":"IETF/RFC-505/RFC-505.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 4870","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 4870","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-4870/RFC-4870.txt"},{"from":"IETF RFC 5016","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5016/RFC-5016.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5672","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5672/RFC-5672.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4871","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 4873","to":"IETF RFC 4872","kind":"references","source":"IETF/RFC-4873/RFC-4873.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 4872","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4872","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4875","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-4875/RFC-4875.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4873","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4872","to":"IETF RFC 4874","kind":"references","source":"IETF/RFC-4872/RFC-4872.txt"},{"from":"IETF RFC 4920","to":"IETF RFC 4874","kind":"references","source":"IETF/RFC-4920/RFC-4920.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4874","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 4874","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5501","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4875","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5149","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5380","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5380/RFC-5380.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4877","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 4879","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 5081","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5081/RFC-5081.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 4880","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 4957","to":"IETF RFC 4881","kind":"references","source":"IETF/RFC-4957/RFC-4957.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 4884","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 4885","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 4886","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 4886","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4886","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4980","to":"IETF RFC 4886","kind":"references","source":"IETF/RFC-4980/RFC-4980.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 4887","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 4887","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4888","to":"IETF RFC 4887","kind":"references","source":"IETF/RFC-4888/RFC-4888.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4887","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 4888","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 4888","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4887","to":"IETF RFC 4888","kind":"references","source":"IETF/RFC-4887/RFC-4887.txt"},{"from":"IETF RFC 4889","to":"IETF RFC 4888","kind":"references","source":"IETF/RFC-4889/RFC-4889.txt"},{"from":"IETF RFC 4885","to":"IETF RFC 4889","kind":"references","source":"IETF/RFC-4885/RFC-4885.txt"},{"from":"IETF RFC 4886","to":"IETF RFC 4889","kind":"references","source":"IETF/RFC-4886/RFC-4886.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4890","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 4925","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-4925/RFC-4925.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 4891","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 4892","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4892","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 5668","to":"IETF RFC 4893","kind":"references","source":"IETF/RFC-5668/RFC-5668.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4893","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 4893","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 4893","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 4893","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4894","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 4895","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 5049","to":"IETF RFC 4896","kind":"references","source":"IETF/RFC-5049/RFC-5049.txt"},{"from":"IETF RFC 4844","to":"IETF RFC 4897","kind":"references","source":"IETF/RFC-4844/RFC-4844.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 4898","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 4898","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 4898","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4898","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4898","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 5154","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4903","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 4904","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 4907","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4907","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4909","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 501","to":"IETF RFC 491","kind":"references","source":"IETF/RFC-501/RFC-501.txt"},{"from":"IETF RFC 505","to":"IETF RFC 491","kind":"references","source":"IETF/RFC-505/RFC-505.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 4915","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 4916","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5397","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-5397/RFC-5397.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6585","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-6585/RFC-6585.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 4918","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 5673","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-5673/RFC-5673.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 4919","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 4920","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 4920","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4924","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 7040","to":"IETF RFC 4925","kind":"references","source":"IETF/RFC-7040/RFC-7040.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 4927","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5143","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-5143/RFC-5143.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 6374","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4928","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5317","to":"IETF RFC 4929","kind":"references","source":"IETF/RFC-5317/RFC-5317.txt"},{"from":"IETF RFC 5654","to":"IETF RFC 4929","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 4929","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4929","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 549","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-549/RFC-549.txt"},{"from":"IETF RFC 553","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-553/RFC-553.txt"},{"from":"IETF RFC 980","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 493","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 4930","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 4931","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 4932","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 4932","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 4932","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 4933","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 4933","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 4933","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 4934","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4934","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 4940","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 4862","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-4862/RFC-4862.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5072","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5072/RFC-5072.txt"},{"from":"IETF RFC 5121","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5121/RFC-5121.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5214","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5214/RFC-5214.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 4941","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 5095","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-5095/RFC-5095.txt"},{"from":"IETF RFC 5157","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-5157/RFC-5157.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5211","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-5211/RFC-5211.txt"},{"from":"IETF RFC 5722","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-5722/RFC-5722.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 4942","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 5018","to":"IETF RFC 4943","kind":"references","source":"IETF/RFC-5018/RFC-5018.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 4943","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 4943","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 4943","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4943","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 4944","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 5026","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-5026/RFC-5026.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 4945","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 4946","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5163","to":"IETF RFC 4947","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 4947","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4948","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 4949","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 495","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 562","to":"IETF RFC 495","kind":"references","source":"IETF/RFC-562/RFC-562.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 4950","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4950","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 4952","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 4953","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 4954","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 4956","to":"IETF RFC 4955","kind":"references","source":"IETF/RFC-4956/RFC-4956.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 4955","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 5155","to":"IETF RFC 4956","kind":"references","source":"IETF/RFC-5155/RFC-5155.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 4956","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 4956","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 4956","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 4956","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5184","to":"IETF RFC 4957","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 4957","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 4957","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4959","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 4959","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6737","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6737/RFC-6737.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 4960","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 4961","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 4962","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 4963","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4964","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4924","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-4924/RFC-4924.txt"},{"from":"IETF RFC 4942","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-4942/RFC-4942.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 4966","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4967","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4967","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 5154","to":"IETF RFC 4968","kind":"references","source":"IETF/RFC-5154/RFC-5154.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 4968","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4969","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 497","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 4973","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-4973/RFC-4973.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 4970","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 4972","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-4972/RFC-4972.txt"},{"from":"IETF RFC 5073","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 4971","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 4971","to":"IETF RFC 4972","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 4970","to":"IETF RFC 4973","kind":"references","source":"IETF/RFC-4970/RFC-4970.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 4973","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 4976","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-4976/RFC-4976.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5509","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-5509/RFC-5509.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4975","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4975","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4976","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 4977","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 4977","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 4978","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 4978","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 4978","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 4979","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 4980","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 4981","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 4982","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 4982","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4982","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4982","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 4982","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 4984","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 4985","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 5011","to":"IETF RFC 4986","kind":"references","source":"IETF/RFC-5011/RFC-5011.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 4987","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 4992","to":"IETF RFC 4991","kind":"references","source":"IETF/RFC-4992/RFC-4992.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 4991","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 4991","to":"IETF RFC 4992","kind":"references","source":"IETF/RFC-4991/RFC-4991.txt"},{"from":"IETF RFC 4993","to":"IETF RFC 4992","kind":"references","source":"IETF/RFC-4993/RFC-4993.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 4992","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 4991","to":"IETF RFC 4993","kind":"references","source":"IETF/RFC-4991/RFC-4991.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 4994","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 4994","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4995","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 4997","to":"IETF RFC 4995","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4995","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 4995","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 4995","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 4996","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 4996","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4996","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 4996","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 4997","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 4997","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 4997","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 162-2 V1.1.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 4998","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 5698","to":"IETF RFC 4998","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 4998","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 4998","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 4998","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 5001","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 5001","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5003","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 5003","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 5003","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5005","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 5005","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 5005","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5006","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 5006","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5006","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 5460","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-5460/RFC-5460.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 5007","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5008","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 505","to":"IETF RFC 501","kind":"references","source":"IETF/RFC-505/RFC-505.txt"},{"from":"IETF RFC 5107","to":"IETF RFC 5010","kind":"references","source":"IETF/RFC-5107/RFC-5107.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5011","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 5011","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 5011","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 5011","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5069","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5069/RFC-5069.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5012","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 5013","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 5220","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-5220/RFC-5220.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 5014","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 5059","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5059/RFC-5059.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5294","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5294/RFC-5294.txt"},{"from":"IETF RFC 5384","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5384/RFC-5384.txt"},{"from":"IETF RFC 5496","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5496/RFC-5496.txt"},{"from":"IETF RFC 5501","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5501/RFC-5501.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6807","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-6807/RFC-6807.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5015","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5016","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 5017","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 5017","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 5017","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 5239","to":"IETF RFC 5018","kind":"references","source":"IETF/RFC-5239/RFC-5239.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5018","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5018","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5018","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 5019","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5019","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5022","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 5829","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-5829/RFC-5829.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5023","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5024","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5039","to":"IETF RFC 5025","kind":"references","source":"IETF/RFC-5039/RFC-5039.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 5025","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 5025","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 5025","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5026","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 5027","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 5027","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 5027","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5027","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 5028","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 5029","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5029","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5031","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 5033","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5033","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5033","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 5033","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 5033","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5034","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5034","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5034","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5034","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5035","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 5035","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 522-3 V1.2.1","to":"IETF RFC 5035","kind":"references","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"IETF RFC 5035","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 5035","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 5126","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5035","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5036","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 5039","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 5039","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5040","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5041","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5042","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 5043","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5043","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5043","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5044","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 5045","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 5045","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5045","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5045","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5045/RFC-5045.txt"},{"from":"IETF RFC 5047","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5047/RFC-5047.txt"},{"from":"IETF RFC 5048","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5048/RFC-5048.txt"},{"from":"IETF RFC 5056","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-5056/RFC-5056.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5046","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 5047","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5047","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5047","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5048","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 5048","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5048","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5049","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 949","to":"IETF RFC 505","kind":"references","source":"IETF/RFC-949/RFC-949.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 5050","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 5050","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 5050","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 5051","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 5401","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-5401/RFC-5401.txt"},{"from":"IETF RFC 5445","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-5445/RFC-5445.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5052","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5054","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5054","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5054","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5055","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5403","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5403/RFC-5403.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5554","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5554/RFC-5554.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5056","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 5589","to":"IETF RFC 5057","kind":"references","source":"IETF/RFC-5589/RFC-5589.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5057","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5057","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 5060","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-5060/RFC-5060.txt"},{"from":"IETF RFC 5110","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-5110/RFC-5110.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5059","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 506","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 506","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5060","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5043","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-5043/RFC-5043.txt"},{"from":"IETF RFC 5062","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-5062/RFC-5062.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 5061","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 5061","to":"IETF RFC 5062","kind":"references","source":"IETF/RFC-5061/RFC-5061.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 5062","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 5063","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 5063","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5064","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 5065","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 5065","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5067","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5068","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5068","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5068","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 5012","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-5012/RFC-5012.txt"},{"from":"IETF RFC 5031","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-5031/RFC-5031.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5069","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5941","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 6685","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6685/RFC-6685.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 5070","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 5072","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5073","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 5074","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 5074","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 5074","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 5169","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-5169/RFC-5169.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5077","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 5080","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 5081","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5081","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 5081","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5081","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5082","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5084","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-5084/RFC-5084.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5083","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 5083","to":"IETF RFC 5084","kind":"references","source":"IETF/RFC-5083/RFC-5083.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5084","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5084","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5084","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5084","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 5086","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5254","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5641","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5641/RFC-5641.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5085","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 5086","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5086","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5086","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 5086","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 5086","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5087","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5087","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 5087","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 5087","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 5089","to":"IETF RFC 5088","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5088","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5088","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 5088","to":"IETF RFC 5089","kind":"references","source":"IETF/RFC-5088/RFC-5088.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5089","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5089","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 509","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5090","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 5091","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 5091","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 5091","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 5091","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5091","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 5092","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 5092","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5092","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5092","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5213","to":"IETF RFC 5094","kind":"references","source":"IETF/RFC-5213/RFC-5213.txt"},{"from":"IETF RFC 5871","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-5871/RFC-5871.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 5095","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 5097","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5103","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5103/RFC-5103.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5101","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5103","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5103/RFC-5103.txt"},{"from":"IETF RFC 5153","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5153/RFC-5153.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5102","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5103","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5104","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 5106","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5106","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 5106","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 5107","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 5107","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5109","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 5110","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 5111","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 5113","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5729","to":"IETF RFC 5113","kind":"references","source":"IETF/RFC-5729/RFC-5729.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5113","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 5114","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5282","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5282/RFC-5282.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5297","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5297/RFC-5297.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7539","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7539/RFC-7539.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5116","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 5104","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5117","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 5118","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 534","to":"IETF RFC 512","kind":"references","source":"IETF/RFC-534/RFC-534.txt"},{"from":"IETF RFC 5130","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 5120","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 5121","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 5122","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 5506","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-5506/RFC-5506.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5124","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 5197","to":"IETF RFC 5125","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 5125","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5125","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5125","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 5125","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 5126","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5126","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 5127","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 5127","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 5127","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5127","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5127","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 5128","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 5128","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5128","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5128","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 5128","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 5462","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-5462/RFC-5462.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5129","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 513","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 562","to":"IETF RFC 513","kind":"references","source":"IETF/RFC-562/RFC-562.pdf"},{"from":"IETF RFC 7752","to":"IETF RFC 5130","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 5135","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5135","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 5135","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 5166","to":"IETF RFC 5136","kind":"references","source":"IETF/RFC-5166/RFC-5166.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 5136","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 5136","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 5137","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5137","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 5137","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5491","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-5491/RFC-5491.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5139","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 531","to":"IETF RFC 514","kind":"references","source":"IETF/RFC-531/RFC-531.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 5141","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 5685","to":"IETF RFC 5142","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5142","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 5143","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 5143","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 5147","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5147","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 5148","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5148","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 5148","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5148","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 5148","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5149","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 5149","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 5150","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 5151","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5152","to":"IETF RFC 5151","kind":"references","source":"IETF/RFC-5152/RFC-5152.txt"},{"from":"IETF RFC 5283","to":"IETF RFC 5151","kind":"references","source":"IETF/RFC-5283/RFC-5283.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 5151","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5151","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 5150","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-5150/RFC-5150.txt"},{"from":"IETF RFC 5151","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-5151/RFC-5151.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5376","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-5376/RFC-5376.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5152","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5153","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5153","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5153","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5153","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 5181","to":"IETF RFC 5154","kind":"references","source":"IETF/RFC-5181/RFC-5181.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 5154","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5702","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-5702/RFC-5702.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5155","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 5156","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 5156","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5156","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5156","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5156","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 5157","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 5157","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 5157","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 5157","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 5158","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5158","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5159","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5161","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5162","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5162","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5162","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 5162","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5162","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5163","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5164","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5164","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 5166","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 5166","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5166","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5167","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5168","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 5169","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 5169","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 5173","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5173","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5175","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 5176","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5180","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5180","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5181","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5181","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5181","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5181","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5182","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5182","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5183","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 5184","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 5184","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5184","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 5188","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 5190","to":"IETF RFC 5189","kind":"references","source":"IETF/RFC-5190/RFC-5190.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5189","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 531","to":"IETF RFC 519","kind":"references","source":"IETF/RFC-531/RFC-531.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 5190","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5190","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 5192","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-5192/RFC-5192.txt"},{"from":"IETF RFC 5193","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-5193/RFC-5193.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5872","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-5872/RFC-5872.txt"},{"from":"IETF RFC 5873","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5191","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 5192","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 5193","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5194","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 5195","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 5195","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 5195","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 5195","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 5197","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 5197","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5197","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 5284","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5284/RFC-5284.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5388","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 5198","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 520","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 520","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5338","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5338/RFC-5338.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 5201","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 5202","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 5202","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5202","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5202","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 5203","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5203","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 5204","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5203","to":"IETF RFC 5204","kind":"references","source":"IETF/RFC-5203/RFC-5203.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 5204","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5206","to":"IETF RFC 5204","kind":"references","source":"IETF/RFC-5206/RFC-5206.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5204","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 5205","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 5205","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5205","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5202","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5202/RFC-5202.txt"},{"from":"IETF RFC 5204","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5204/RFC-5204.txt"},{"from":"IETF RFC 5205","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5205/RFC-5205.txt"},{"from":"IETF RFC 5207","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5207/RFC-5207.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 5206","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5207","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5207","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5207","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 5208","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5208","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5208","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 5208","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 5208","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 5209","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5211","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 5211","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5211","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5212","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 5213","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5375","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5375/RFC-5375.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 5214","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 5247","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 5216","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5218","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 5218","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5218","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 5218","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 5218","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 522","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 538","to":"IETF RFC 522","kind":"references","source":"IETF/RFC-538/RFC-538.txt"},{"from":"IETF RFC 5221","to":"IETF RFC 5220","kind":"references","source":"IETF/RFC-5221/RFC-5221.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5220","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 5220","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 5220","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 5220","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5221","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 5221","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 5223","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-5223/RFC-5223.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 5964","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-5964/RFC-5964.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5222","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5223","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 5431","to":"IETF RFC 5224","kind":"references","source":"IETF/RFC-5431/RFC-5431.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5224","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5225","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 5222","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5222/RFC-5222.txt"},{"from":"IETF RFC 5248","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5248/RFC-5248.txt"},{"from":"IETF RFC 5250","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5250/RFC-5250.txt"},{"from":"IETF RFC 5265","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5265/RFC-5265.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 5304","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5308","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5341","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5343","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5343/RFC-5343.txt"},{"from":"IETF RFC 5350","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5350/RFC-5350.txt"},{"from":"IETF RFC 5357","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5384","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5384/RFC-5384.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5395","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5395/RFC-5395.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5431","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5431/RFC-5431.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5444","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5444/RFC-5444.txt"},{"from":"IETF RFC 5447","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5447/RFC-5447.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5453","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5453/RFC-5453.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 5457","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5457/RFC-5457.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5492","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5492/RFC-5492.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5513","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5513/RFC-5513.txt"},{"from":"IETF RFC 5516","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5516/RFC-5516.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5668","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5668/RFC-5668.txt"},{"from":"IETF RFC 5685","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5685/RFC-5685.txt"},{"from":"IETF RFC 5701","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5701/RFC-5701.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5719","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5719/RFC-5719.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5736","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5736/RFC-5736.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5871","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5871/RFC-5871.txt"},{"from":"IETF RFC 5872","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5872/RFC-5872.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6212","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6212/RFC-6212.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6685","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6685/RFC-6685.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6694","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6694/RFC-6694.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6755","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6755/RFC-6755.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7009","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 7120","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7120/RFC-7120.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7319","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7319/RFC-7319.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7346","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7346/RFC-7346.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5226","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 5227","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 5227","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 5227","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5183","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5183/RFC-5183.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5231","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5231/RFC-5231.txt"},{"from":"IETF RFC 5232","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5232/RFC-5232.txt"},{"from":"IETF RFC 5233","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5233/RFC-5233.txt"},{"from":"IETF RFC 5235","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5235/RFC-5235.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5228","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5230","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5230/RFC-5230.txt"},{"from":"IETF RFC 5232","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5232/RFC-5232.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5229","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5230","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 5183","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5183/RFC-5183.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5232","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5232/RFC-5232.txt"},{"from":"IETF RFC 5235","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5235/RFC-5235.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5231","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5232","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5232","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5232","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5233","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5233","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 5122","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5137","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5141","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5147","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5161","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5161/RFC-5161.txt"},{"from":"IETF RFC 5162","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5162/RFC-5162.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5191","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5191/RFC-5191.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5285","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5285/RFC-5285.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5323","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5393","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5393/RFC-5393.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5432","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5432/RFC-5432.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5464","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5464/RFC-5464.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5576","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5576/RFC-5576.txt"},{"from":"IETF RFC 5583","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5583/RFC-5583.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5657","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5657/RFC-5657.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5781","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5781/RFC-5781.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6694","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6694/RFC-6694.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7405","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7405/RFC-7405.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 7464","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 5234","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 5234","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 5229","to":"IETF RFC 5235","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 5235","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5463","to":"IETF RFC 5235","kind":"references","source":"IETF/RFC-5463/RFC-5463.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5235","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5235","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5237","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 5238","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5239","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 5239","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 5239","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 5239","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5239","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 539","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-539/RFC-539.txt"},{"from":"IETF RFC 555","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-555/RFC-555.txt"},{"from":"IETF RFC 561","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-561/RFC-561.txt"},{"from":"IETF RFC 753","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 767","to":"IETF RFC 524","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 5243","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5769","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5769/RFC-5769.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8421","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8421/RFC-8421.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5245","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"IETF RFC 5246","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"IETF RFC 5246","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ETSI TS 119 495 V1.7.1","to":"IETF RFC 5246","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"IETF RFC 5247","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5247/RFC-5247.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5469","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5469/RFC-5469.txt"},{"from":"IETF RFC 5479","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5479/RFC-5479.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 5489","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5489/RFC-5489.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5582","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5582/RFC-5582.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 5932","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5932/RFC-5932.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7009","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7366","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7366/RFC-7366.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7465","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7465/RFC-7465.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7685","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7685/RFC-7685.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 5246","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5295","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5295/RFC-5295.txt"},{"from":"IETF RFC 5433","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5433/RFC-5433.txt"},{"from":"IETF RFC 5448","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5448/RFC-5448.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5247","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 5248","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 5248","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5248","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5248","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5248","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 5250","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 5250","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 5250","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5250","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 5252","to":"IETF RFC 5251","kind":"references","source":"IETF/RFC-5252/RFC-5252.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 5251","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 5252","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5253","to":"IETF RFC 5252","kind":"references","source":"IETF/RFC-5253/RFC-5253.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 5252","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5251","to":"IETF RFC 5253","kind":"references","source":"IETF/RFC-5251/RFC-5251.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 5254","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 5254","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5254","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5254","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 5256","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5258","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-5258/RFC-5258.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5255","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5255","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5257","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5267","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-5267/RFC-5267.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5256","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5257","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5257","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5258","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5259","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5259","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5259","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 5261","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 5261","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 5261","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 5261","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 5261","to":"IETF RFC 5262","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5263","to":"IETF RFC 5262","kind":"references","source":"IETF/RFC-5263/RFC-5263.txt"},{"from":"IETF RFC 5262","to":"IETF RFC 5263","kind":"references","source":"IETF/RFC-5262/RFC-5262.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5263","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5266","to":"IETF RFC 5265","kind":"references","source":"IETF/RFC-5266/RFC-5266.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 5265","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5265","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5454","to":"IETF RFC 5266","kind":"references","source":"IETF/RFC-5454/RFC-5454.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5266","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5267","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5267","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5267","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5267","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5267","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 5269","to":"IETF RFC 5268","kind":"references","source":"IETF/RFC-5269/RFC-5269.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 5268","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5268","to":"IETF RFC 5269","kind":"references","source":"IETF/RFC-5268/RFC-5268.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 5269","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5273","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-5273/RFC-5273.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 5275","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5272","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 5274","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-5274/RFC-5274.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 5273","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 5272","to":"IETF RFC 5274","kind":"references","source":"IETF/RFC-5272/RFC-5272.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5274","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5274","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5274","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5275","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 5277","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 5278","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"legal:2025-1943","to":"IETF RFC 5280","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-2162","to":"IETF RFC 5280","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 5280","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ARF TS10 V1.2","to":"IETF RFC 5280","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS11 V1.0.1","to":"IETF RFC 5280","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 412-3 V1.3.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf"},{"from":"ETSI EN 319 421 V1.3.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 411-8 V1.1.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI TS 119 495 V1.7.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 5280","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 5275","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5275/RFC-5275.txt"},{"from":"IETF RFC 5281","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5281/RFC-5281.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5480","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5539","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5539/RFC-5539.txt"},{"from":"IETF RFC 5652","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5652/RFC-5652.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5759","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5759/RFC-5759.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5877","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5937","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 5280","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 5580","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 5281","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5282","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5282","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5282","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5282","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 5561","to":"IETF RFC 5283","kind":"references","source":"IETF/RFC-5561/RFC-5561.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 5284","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5450","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-5450/RFC-5450.txt"},{"from":"IETF RFC 5484","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-5484/RFC-5484.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5285","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5826","to":"IETF RFC 5286","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5286","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5286","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5289","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-5289/RFC-5289.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5288","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 5288","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-5288/RFC-5288.txt"},{"from":"IETF RFC 5430","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-5430/RFC-5430.txt"},{"from":"IETF RFC 5487","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-5487/RFC-5487.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 5289","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5290","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5293","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5293","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 5294","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5294","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 5296","to":"IETF RFC 5295","kind":"references","source":"IETF/RFC-5296/RFC-5296.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 5295","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5295","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5295","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 5296","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 5296","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 5296","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5296","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5296","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 5297","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5297","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5298","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 739","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 870","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 900","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 530","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 5301","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5301","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 5302","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5303","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 5301","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5301/RFC-5301.txt"},{"from":"IETF RFC 5302","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5303","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5305","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5308","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5310","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5304","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 5302","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5308","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6165","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 5305","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 5307","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-5307/RFC-5307.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 5306","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 5311","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5543","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-5543/RFC-5543.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5307","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 5308","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 5308","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5308","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 5308","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5309","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5309","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5309","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 531","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5709","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-5709/RFC-5709.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 5310","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5311","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5316","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 5317","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5317","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5317","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 532","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 532","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 5320","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 5320","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5320","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 5320","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5429","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5442","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5442/RFC-5442.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5672","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5672/RFC-5672.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5321","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"legal:2024-2977","to":"IETF RFC 5322","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2026-1731","to":"IETF RFC 5322","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 5322","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ARF TS05 V1.2.1","to":"IETF RFC 5322","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ETSI EN 319 522-2 V1.2.1","to":"IETF RFC 5322","kind":"references","source":"ETSI/EN-319-522-2-V1.2.1/EN-319-522-2-V1.2.1.pdf"},{"from":"ETSI EN 319 522-3 V1.2.1","to":"IETF RFC 5322","kind":"references","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 5322","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 5322","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 5321","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5423","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5423/RFC-5423.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5518","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5518/RFC-5518.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5547","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 5322","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 5323","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 5325","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 5325","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 5325","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 5326","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5327","to":"IETF RFC 5326","kind":"references","source":"IETF/RFC-5327/RFC-5327.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 5326","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 5326","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 5325","to":"IETF RFC 5327","kind":"references","source":"IETF/RFC-5325/RFC-5325.txt"},{"from":"IETF RFC 5326","to":"IETF RFC 5327","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5328","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 5329","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 5329","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 534","to":"IETF RFC 533","kind":"references","source":"IETF/RFC-534/RFC-534.txt"},{"from":"IETF RFC 5316","to":"IETF RFC 5330","kind":"references","source":"IETF/RFC-5316/RFC-5316.txt"},{"from":"IETF RFC 5332","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-5332/RFC-5332.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5331","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 5331","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-5331/RFC-5331.txt"},{"from":"IETF RFC 5342","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-5342/RFC-5342.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 5332","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 5333","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5335","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5336","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 5337","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5504","to":"IETF RFC 5337","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5337","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5337","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5337","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5338","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 534","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5286","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5286/RFC-5286.txt"},{"from":"IETF RFC 5309","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5329","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5329/RFC-5329.txt"},{"from":"IETF RFC 5330","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5330/RFC-5330.txt"},{"from":"IETF RFC 5392","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5392/RFC-5392.txt"},{"from":"IETF RFC 5449","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5449/RFC-5449.txt"},{"from":"IETF RFC 5613","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5613/RFC-5613.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 5340","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 5341","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 5494","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 5342","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5343","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5343","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5622","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5622/RFC-5622.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 5348","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5350","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 5357","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 5452","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-5452/RFC-5452.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5358","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5359","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 5359","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 5359","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 5359","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 5361","to":"IETF RFC 5360","kind":"references","source":"IETF/RFC-5361/RFC-5361.txt"},{"from":"IETF RFC 5362","to":"IETF RFC 5360","kind":"references","source":"IETF/RFC-5362/RFC-5362.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 5360","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 5361","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 5362","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5360","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5360/RFC-5360.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5367","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5367/RFC-5367.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 5363","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 5364","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5365","to":"IETF RFC 5364","kind":"references","source":"IETF/RFC-5365/RFC-5365.txt"},{"from":"IETF RFC 5366","to":"IETF RFC 5364","kind":"references","source":"IETF/RFC-5366/RFC-5366.txt"},{"from":"IETF RFC 5368","to":"IETF RFC 5364","kind":"references","source":"IETF/RFC-5368/RFC-5368.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5364","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 5365","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 5365","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 5366","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5364","to":"IETF RFC 5366","kind":"references","source":"IETF/RFC-5364/RFC-5364.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 5366","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 5363","to":"IETF RFC 5367","kind":"references","source":"IETF/RFC-5363/RFC-5363.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5367","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 5367","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 5368","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 5369","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 5370","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 5406","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-5406/RFC-5406.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 5374","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 5375","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 5375","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5376","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 5378","to":"IETF RFC 5377","kind":"references","source":"IETF/RFC-5378/RFC-5378.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 5377","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 5377","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-5377/RFC-5377.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 5378","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 538","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 5380","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 5382","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5383","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5496","to":"IETF RFC 5384","kind":"references","source":"IETF/RFC-5496/RFC-5496.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5384","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6807","to":"IETF RFC 5384","kind":"references","source":"IETF/RFC-6807/RFC-6807.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 5386","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 5386","to":"IETF RFC 5387","kind":"references","source":"IETF/RFC-5386/RFC-5386.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 5387","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5387","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5387","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5388","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5769","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5769/RFC-5769.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 5389","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 539","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 555","to":"IETF RFC 539","kind":"references","source":"IETF/RFC-555/RFC-555.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 5391","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5392","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5393","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5393","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 5393","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 5507","to":"IETF RFC 5395","kind":"references","source":"IETF/RFC-5507/RFC-5507.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 5395","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 5395","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 5395","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5396","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5396","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5396","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5396","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 5396","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 5397","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5397","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 5398","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 5401","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 5403","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5403","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5403","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5403","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5404","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 5404","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 5555","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-5555/RFC-5555.txt"},{"from":"IETF RFC 5571","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-5571/RFC-5571.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5405","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 5406","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 5406","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5406","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5406","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 5409","to":"IETF RFC 5408","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 5408","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 5408","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 5408","to":"IETF RFC 5409","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 5409","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 5417","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-5417/RFC-5417.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5415","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5416","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5418","to":"IETF RFC 5416","kind":"references","source":"IETF/RFC-5418/RFC-5418.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 5416","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 5416","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5416","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5417","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5415","to":"IETF RFC 5418","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5416","to":"IETF RFC 5418","kind":"references","source":"IETF/RFC-5416/RFC-5416.txt"},{"from":"IETF RFC 0542","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-0542/RFC-0542.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 555","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-555/RFC-555.txt"},{"from":"IETF RFC 614","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-614/RFC-614.txt"},{"from":"IETF RFC 624","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-624/RFC-624.txt"},{"from":"IETF RFC 640","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-640/RFC-640.txt"},{"from":"IETF RFC 683","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-683/RFC-683.txt"},{"from":"IETF RFC 686","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-686/RFC-686.txt"},{"from":"IETF RFC 739","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 759","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 762","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 775","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-775/RFC-775.txt"},{"from":"IETF RFC 959","to":"IETF RFC 542","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 5440","to":"IETF RFC 5420","kind":"references","source":"IETF/RFC-5440/RFC-5440.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 5420","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 5420","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 5420","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 5422","to":"IETF RFC 5421","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5421","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5421","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 5421","to":"IETF RFC 5422","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5422","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5422","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5423","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5423","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5425","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5425/RFC-5425.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5427","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5427/RFC-5427.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5612","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5612/RFC-5612.txt"},{"from":"IETF RFC 5674","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5706","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5706/RFC-5706.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5424","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5425","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5424","to":"IETF RFC 5426","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5426","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5426","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5426","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 5427","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5427","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5429","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5429","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5430","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5430","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5431","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5432","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5433","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5433","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5433","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 5436","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-5436/RFC-5436.txt"},{"from":"IETF RFC 5437","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5435","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 5435","to":"IETF RFC 5436","kind":"references","source":"IETF/RFC-5435/RFC-5435.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5437","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 5511","to":"IETF RFC 5440","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5440","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5440","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5442","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5442","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5443","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 5497","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-5497/RFC-5497.txt"},{"from":"IETF RFC 5498","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-5498/RFC-5498.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 5444","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 5740","to":"IETF RFC 5445","kind":"references","source":"IETF/RFC-5740/RFC-5740.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5445","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5447","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 5447","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 5447","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5447","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 5447","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 5448","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5448","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5449","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5450","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 5450","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5450","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 5617","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-5617/RFC-5617.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6212","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6212/RFC-6212.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5451","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 5452","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5452","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 5452","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 5452","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 5452","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 5453","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5454","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 5457","to":"IETF RFC 5456","kind":"references","source":"IETF/RFC-5457/RFC-5457.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5456","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5456","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 5457","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 5460","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5461","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 5559","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5586","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-5586/RFC-5586.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5462","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5463","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5465","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-5465/RFC-5465.txt"},{"from":"IETF RFC 5466","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5464","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5465","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5465","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5465","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5465","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5530","to":"IETF RFC 5466","kind":"references","source":"IETF/RFC-5530/RFC-5530.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5466","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5469","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6985","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-6985/RFC-6985.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 5470","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5471","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5471","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5471","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5471","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 5470","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5470/RFC-5470.txt"},{"from":"IETF RFC 5471","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5471/RFC-5471.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5472","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5473","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5474","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 5475","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5476","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 5472","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5472/RFC-5472.txt"},{"from":"IETF RFC 5473","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5473/RFC-5473.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5475","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5475/RFC-5475.txt"},{"from":"IETF RFC 5476","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5476/RFC-5476.txt"},{"from":"IETF RFC 5610","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5477","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 5479","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5759","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5759/RFC-5759.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 5480","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 5481","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5482","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5482","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5484","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 5484","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5485","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5486","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 5486","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5487","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 5487","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5489","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5489","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5489","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 5489","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 549","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5491","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 5549","to":"IETF RFC 5492","kind":"references","source":"IETF/RFC-5549/RFC-5549.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 5492","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5493","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 5494","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 5494","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 5494","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 5496","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 5496","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 5496","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5497","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 5497","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5497","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5498","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5498","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 5501","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5501","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5504","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5505","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 5505","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5505","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5506","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 5507","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 5507","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5507","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 5507","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 5508","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 5509","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 5511","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 5512","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 5512","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5640","to":"IETF RFC 5512","kind":"references","source":"IETF/RFC-5640/RFC-5640.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 5513","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5513","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5516","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 6212","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-6212/RFC-6212.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5518","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 555","to":"IETF RFC 552","kind":"references","source":"IETF/RFC-555/RFC-555.txt"},{"from":"IETF RFC 5529","to":"IETF RFC 5528","kind":"references","source":"IETF/RFC-5529/RFC-5529.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 5528","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5529","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 549","to":"IETF RFC 553","kind":"references","source":"IETF/RFC-549/RFC-549.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5530","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5530","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 5532","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-5532/RFC-5532.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5531","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5532","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5534","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-5534/RFC-5534.txt"},{"from":"IETF RFC 5535","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-5535/RFC-5535.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5533","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 5534","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5534","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 5534","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 5534","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 5533","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-5533/RFC-5533.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5535","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 5536","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 5536","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 5537","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 5537","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 5539","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 5542","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 5542","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 5543","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 5546","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-5546/RFC-5546.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 5545","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5546","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5546","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5546","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 5621","to":"IETF RFC 5547","kind":"references","source":"IETF/RFC-5621/RFC-5621.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5547","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 5547","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 5826","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 5548","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 5549","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 5549","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 5549","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 555","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5551","to":"IETF RFC 5550","kind":"references","source":"IETF/RFC-5551/RFC-5551.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 5550","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5551","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5554","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5568","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-5568/RFC-5568.txt"},{"from":"IETF RFC 5637","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-5637/RFC-5637.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5555","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5556","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 5556","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5556","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 5556","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 5558","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5558","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 5558","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 5559","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 556","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 566","to":"IETF RFC 556","kind":"references","source":"IETF/RFC-566/RFC-566.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 5560","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 5560","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5560","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5560","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5560","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 5561","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5561","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5561","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5561","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5562","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5562","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 5562","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 5562","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 5566","to":"IETF RFC 5565","kind":"references","source":"IETF/RFC-5566/RFC-5566.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 5565","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5565","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 5565","to":"IETF RFC 5566","kind":"references","source":"IETF/RFC-5565/RFC-5565.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 5566","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5566","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 5567","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 5648","to":"IETF RFC 5568","kind":"references","source":"IETF/RFC-5648/RFC-5648.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5568","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 5568","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5568","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 5569","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 5569","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5569","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5570","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5570","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 5570","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 5570","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 5619","to":"IETF RFC 5571","kind":"references","source":"IETF/RFC-5619/RFC-5619.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5571","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 5571","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 5575","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 5575","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5576","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 5580","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5580","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 5580","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5582","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 5582","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 5691","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-5691/RFC-5691.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5583","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5585","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5585","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5585","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5585","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5586","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5587","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 5589","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5589","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 5589","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 593","to":"IETF RFC 559","kind":"references","source":"IETF/RFC-593/RFC-593.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5590","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5592","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-5592/RFC-5592.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 5591","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 5590","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-5590/RFC-5590.txt"},{"from":"IETF RFC 5591","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-5591/RFC-5591.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 5592","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 5594","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 5595","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 5595","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5595","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5595","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 5596","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5597","to":"IETF RFC 5596","kind":"references","source":"IETF/RFC-5597/RFC-5597.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5596","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 5597","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 5550","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-5550/RFC-5550.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 5598","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 560","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5602","to":"IETF RFC 5601","kind":"references","source":"IETF/RFC-5602/RFC-5602.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5601","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 5601","to":"IETF RFC 5602","kind":"references","source":"IETF/RFC-5601/RFC-5601.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 5606","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 5608","to":"IETF RFC 5607","kind":"references","source":"IETF/RFC-5608/RFC-5608.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 5607","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 5607","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5607","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 5607","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 5608","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5608","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 561","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 680","to":"IETF RFC 561","kind":"references","source":"IETF/RFC-680/RFC-680.txt"},{"from":"IETF RFC 753","to":"IETF RFC 561","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 561","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 767","to":"IETF RFC 561","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 5655","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-5655/RFC-5655.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5610","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5612","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5612","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 5612","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 5614","to":"IETF RFC 5613","kind":"references","source":"IETF/RFC-5614/RFC-5614.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 5613","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 5613","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 5614","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5617","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 5619","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 580","to":"IETF RFC 562","kind":"references","source":"IETF/RFC-580/RFC-580.txt"},{"from":"IETF RFC 5744","to":"IETF RFC 5620","kind":"references","source":"IETF/RFC-5744/RFC-5744.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 5620","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5621","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5621","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5622","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 5622","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5622","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 5622","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 5624","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 5624","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5625","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5626","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5628","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-5628/RFC-5628.txt"},{"from":"IETF RFC 5630","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-5630/RFC-5630.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5627","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 5627","to":"IETF RFC 5628","kind":"references","source":"IETF/RFC-5627/RFC-5627.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5630","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 5635","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5637","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 5639","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 5639","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 5639","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 5639","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5640","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 5640","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 5640","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5641","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5641","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 5644","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 5644","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 5644","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 5644","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 5646","to":"IETF RFC 5645","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5645","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 5646","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI EN 319 522-3 V1.2.1","to":"IETF RFC 5646","kind":"references","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 5646","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 5646","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"IETF RFC 5646","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 5646","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 5456","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5545","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5645","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5698","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 5646","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 5646","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 5646","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 5845","to":"IETF RFC 5648","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5648","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5648","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 5649","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 5649","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5649","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5649","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 739","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 565","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5650","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5650","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 5651","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 5651","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5651","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5651","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 5652","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5652","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 5652","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 5652","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 5698","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6019","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6019/RFC-6019.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 5652","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 5659","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5659/RFC-5659.txt"},{"from":"IETF RFC 5704","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6941","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-6941/RFC-6941.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 5654","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 5655","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6410","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6410/RFC-6410.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 5657","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5659","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 566","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5660","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5660","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5663","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-5663/RFC-5663.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5661","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5662","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 5662","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5663","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5664","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5665","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5665","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5665","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5666","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 5666","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5666","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5667","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5667","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 5668","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5669","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5669","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 567","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5696","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-5696/RFC-5696.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5670","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5672","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5672","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 5826","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 5673","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5674","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5676","to":"IETF RFC 5675","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5675","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5675","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5675","to":"IETF RFC 5676","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5676","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5676","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5677","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5678","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5679","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5679","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 5681","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 5682","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5682","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 5682","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 5682","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 5682","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 5685","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 5685","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5685","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5808","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-5808/RFC-5808.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5687","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 5689","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 880","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 569","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5690","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5690","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 5690","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 5690","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5691","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5692","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5692","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5692","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 5693","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 5693","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5693","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5693","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 5694","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5695","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5670","to":"IETF RFC 5696","kind":"references","source":"IETF/RFC-5670/RFC-5670.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5696","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5696","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 5696","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5696","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5698","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 5701","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 5701","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 5702","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5702","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 5702","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5703","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5704","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5704","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 5705","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 5706","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5707","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 5708","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5709","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 5709","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 5709","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5709","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 5709","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 571","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 571","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 5713","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5713","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5713","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5714","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5715","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 5717","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 5717","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5717","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5717","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5718","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5718","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5719","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5719","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 5720","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5720","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5721","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5721","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5721","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 5722","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5723","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 5723","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5723","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5725","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 5725","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5725","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 5725","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5727","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5727","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5727","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5727","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 5727","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5728","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5729","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5729","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5729","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5730","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5731","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 5732","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5732","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 5733","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5733","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5733","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5733","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5734","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 5736","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-5736/RFC-5736.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5735","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 5736","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 5736","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5736","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5736","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 5737","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5738","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5738","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5738","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5739","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5739","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 5739","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5739","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 5739","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5740","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5456","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5457","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5457/RFC-5457.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5569","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5569/RFC-5569.txt"},{"from":"IETF RFC 5639","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5661","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5662","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5662/RFC-5662.txt"},{"from":"IETF RFC 5663","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5663/RFC-5663.txt"},{"from":"IETF RFC 5664","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5664/RFC-5664.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5666","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5666/RFC-5666.txt"},{"from":"IETF RFC 5667","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5667/RFC-5667.txt"},{"from":"IETF RFC 5669","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5669/RFC-5669.txt"},{"from":"IETF RFC 5687","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5687/RFC-5687.txt"},{"from":"IETF RFC 5690","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5690/RFC-5690.txt"},{"from":"IETF RFC 5705","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5705/RFC-5705.txt"},{"from":"IETF RFC 5708","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5713","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5713/RFC-5713.txt"},{"from":"IETF RFC 5718","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5719","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5719/RFC-5719.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5721","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5723","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5723/RFC-5723.txt"},{"from":"IETF RFC 5725","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5725/RFC-5725.txt"},{"from":"IETF RFC 5727","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5727/RFC-5727.txt"},{"from":"IETF RFC 5728","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 5736","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5736/RFC-5736.txt"},{"from":"IETF RFC 5737","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5737/RFC-5737.txt"},{"from":"IETF RFC 5738","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5739","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5739/RFC-5739.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5746","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5746/RFC-5746.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5756","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5756/RFC-5756.txt"},{"from":"IETF RFC 5757","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5757/RFC-5757.txt"},{"from":"IETF RFC 5758","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5758/RFC-5758.txt"},{"from":"IETF RFC 5759","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5759/RFC-5759.txt"},{"from":"IETF RFC 5760","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5768","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5768/RFC-5768.txt"},{"from":"IETF RFC 5769","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5769/RFC-5769.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5771","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5771/RFC-5771.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 5777","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5777/RFC-5777.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 5780","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5780/RFC-5780.txt"},{"from":"IETF RFC 5781","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5781/RFC-5781.txt"},{"from":"IETF RFC 5782","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5782/RFC-5782.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5785","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5785/RFC-5785.txt"},{"from":"IETF RFC 5788","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5788/RFC-5788.txt"},{"from":"IETF RFC 5789","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5789/RFC-5789.txt"},{"from":"IETF RFC 5790","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5790/RFC-5790.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5796","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5796/RFC-5796.txt"},{"from":"IETF RFC 5798","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5798/RFC-5798.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5808","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5808/RFC-5808.txt"},{"from":"IETF RFC 5815","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5815/RFC-5815.txt"},{"from":"IETF RFC 5816","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5816/RFC-5816.txt"},{"from":"IETF RFC 5819","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5819/RFC-5819.txt"},{"from":"IETF RFC 5825","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5825/RFC-5825.txt"},{"from":"IETF RFC 5826","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5826/RFC-5826.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5829","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5829/RFC-5829.txt"},{"from":"IETF RFC 5830","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5830/RFC-5830.txt"},{"from":"IETF RFC 5831","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5831/RFC-5831.txt"},{"from":"IETF RFC 5832","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 5835","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5836","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5839","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5839/RFC-5839.txt"},{"from":"IETF RFC 5840","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5840/RFC-5840.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 5848","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5848/RFC-5848.txt"},{"from":"IETF RFC 5849","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5855","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5855/RFC-5855.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5860","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5861","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5861/RFC-5861.txt"},{"from":"IETF RFC 5863","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5863/RFC-5863.txt"},{"from":"IETF RFC 5864","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5864/RFC-5864.txt"},{"from":"IETF RFC 5865","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5865/RFC-5865.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 5867","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5867/RFC-5867.txt"},{"from":"IETF RFC 5869","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5869/RFC-5869.txt"},{"from":"IETF RFC 5870","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 5871","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5871/RFC-5871.txt"},{"from":"IETF RFC 5872","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5872/RFC-5872.txt"},{"from":"IETF RFC 5873","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 5877","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 5880","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5880/RFC-5880.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 5887","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5887/RFC-5887.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 5889","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5889/RFC-5889.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5893","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5893/RFC-5893.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5895","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5895/RFC-5895.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 5903","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5909","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5909/RFC-5909.txt"},{"from":"IETF RFC 5910","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5911","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 5930","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5930/RFC-5930.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 5932","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5932/RFC-5932.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5937","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5941","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 5952","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5952/RFC-5952.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5964","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5964/RFC-5964.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 5969","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5969/RFC-5969.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 5983","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5983/RFC-5983.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 5987","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 5991","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5991/RFC-5991.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 5997","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5997/RFC-5997.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6014","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6014/RFC-6014.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6019","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6019/RFC-6019.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6030","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6034","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6034/RFC-6034.txt"},{"from":"IETF RFC 6035","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6036","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6036/RFC-6036.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6043","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6043/RFC-6043.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6057","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6057/RFC-6057.txt"},{"from":"IETF RFC 6059","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6059/RFC-6059.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6065","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6065/RFC-6065.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6081","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6081/RFC-6081.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6085","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6085/RFC-6085.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6091","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6096","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6096/RFC-6096.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6105","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6105/RFC-6105.txt"},{"from":"IETF RFC 6106","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6106/RFC-6106.txt"},{"from":"IETF RFC 6108","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6108/RFC-6108.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 6119","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6130","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6130/RFC-6130.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6141","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6141/RFC-6141.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6149","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6149/RFC-6149.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6151","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6151/RFC-6151.txt"},{"from":"IETF RFC 6152","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6152/RFC-6152.txt"},{"from":"IETF RFC 6154","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6154/RFC-6154.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6158","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6164","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6164/RFC-6164.txt"},{"from":"IETF RFC 6165","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6177","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6177/RFC-6177.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6184","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6188","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6188/RFC-6188.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6194","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6194/RFC-6194.txt"},{"from":"IETF RFC 6195","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6195/RFC-6195.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6206","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6206/RFC-6206.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6212","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6212/RFC-6212.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6215","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6215/RFC-6215.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6221","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6221/RFC-6221.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6225","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6225/RFC-6225.txt"},{"from":"IETF RFC 6229","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6229/RFC-6229.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6243","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6243/RFC-6243.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 6247","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6247/RFC-6247.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6283","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6288","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6288/RFC-6288.txt"},{"from":"IETF RFC 6291","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6297","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6297/RFC-6297.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 6313","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6313/RFC-6313.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6321","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6321/RFC-6321.txt"},{"from":"IETF RFC 6323","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6323/RFC-6323.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6336","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6336/RFC-6336.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6340","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6340/RFC-6340.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6349","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6349/RFC-6349.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6351","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6351/RFC-6351.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6355","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6355/RFC-6355.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6360","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6360/RFC-6360.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6368","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6368/RFC-6368.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6382","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6382/RFC-6382.txt"},{"from":"IETF RFC 6386","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6386/RFC-6386.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6410","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6410/RFC-6410.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6419","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6419/RFC-6419.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 6424","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6424/RFC-6424.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6430","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6430/RFC-6430.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6452","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6452/RFC-6452.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6501","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6549","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6549/RFC-6549.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6552","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6552/RFC-6552.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6557","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 6562","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6562/RFC-6562.txt"},{"from":"IETF RFC 6563","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6563/RFC-6563.txt"},{"from":"IETF RFC 6564","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6564/RFC-6564.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6577","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6577/RFC-6577.txt"},{"from":"IETF RFC 6582","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6582/RFC-6582.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6585","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6585/RFC-6585.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6603","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6603/RFC-6603.txt"},{"from":"IETF RFC 6604","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6604/RFC-6604.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6620","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6620/RFC-6620.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6635","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6635/RFC-6635.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6644","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6644/RFC-6644.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6649","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6649/RFC-6649.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6657","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 6666","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6666/RFC-6666.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6685","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6685/RFC-6685.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6694","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6694/RFC-6694.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6708","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6708/RFC-6708.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6713","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6713/RFC-6713.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6737","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6737/RFC-6737.txt"},{"from":"IETF RFC 6739","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6739/RFC-6739.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6755","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6755/RFC-6755.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6770","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6789","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6789/RFC-6789.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6793","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6793/RFC-6793.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6807","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6807/RFC-6807.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6832","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6832/RFC-6832.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6834","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6834/RFC-6834.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6839","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 6841","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6841/RFC-6841.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6891","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6891/RFC-6891.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6941","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6941/RFC-6941.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6949","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6949/RFC-6949.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 6970","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6970/RFC-6970.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 6979","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 6982","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6982/RFC-6982.txt"},{"from":"IETF RFC 6983","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6983/RFC-6983.txt"},{"from":"IETF RFC 6985","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6985/RFC-6985.txt"},{"from":"IETF RFC 6987","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6987/RFC-6987.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7009","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7040","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7040/RFC-7040.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7064","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7064/RFC-7064.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7083","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7083/RFC-7083.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7120","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7120/RFC-7120.txt"},{"from":"IETF RFC 7127","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7127/RFC-7127.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7164","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7164/RFC-7164.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7195","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7218","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7218/RFC-7218.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7282","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7282/RFC-7282.txt"},{"from":"IETF RFC 7283","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7283/RFC-7283.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7319","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7319/RFC-7319.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7335","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7335/RFC-7335.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 7337","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7337/RFC-7337.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7346","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7346/RFC-7346.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7366","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7366/RFC-7366.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7375","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7375/RFC-7375.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7396","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7396/RFC-7396.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7405","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7405/RFC-7405.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 7464","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7465","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7465/RFC-7465.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7495","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7495/RFC-7495.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 7498","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7498/RFC-7498.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 7536","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7536/RFC-7536.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7539","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7539/RFC-7539.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7632","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7632/RFC-7632.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7669","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7685","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7685/RFC-7685.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7693","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7693/RFC-7693.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7706","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7706/RFC-7706.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 7748","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7748/RFC-7748.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 7793","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7793/RFC-7793.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7830","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7830/RFC-7830.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 5741","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 5741","to":"IETF RFC 5742","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 5742","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 5742","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5742","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 5742","to":"IETF RFC 5743","kind":"references","source":"IETF/RFC-5742/RFC-5742.txt"},{"from":"IETF RFC 5743","to":"IETF RFC 5744","kind":"references","source":"IETF/RFC-5743/RFC-5743.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 5746","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5888","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-5888/RFC-5888.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5750","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5752","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5752/RFC-5752.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5756","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5756/RFC-5756.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5967","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 5990","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 5751","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5752","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5752","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5752","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 5752","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5753","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 5639","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5753","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 5754","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5755","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 5755","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 412-6 V1.2.1","to":"IETF RFC 5755","kind":"references","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 5755","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"IETF RFC 5750","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5877","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5912","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5755","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 5755","to":"IETF RFC 5756","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5756","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 5757","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 5750","to":"IETF RFC 5758","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5754","to":"IETF RFC 5758","kind":"references","source":"IETF/RFC-5754/RFC-5754.txt"},{"from":"IETF RFC 5759","to":"IETF RFC 5758","kind":"references","source":"IETF/RFC-5759/RFC-5759.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5758","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 5758","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5759","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6318","to":"IETF RFC 5759","kind":"references","source":"IETF/RFC-6318/RFC-6318.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 5759","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 5759","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 5759","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5760","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5762","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-5762/RFC-5762.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6128","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6128/RFC-6128.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8035","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8035/RFC-8035.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5761","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5968","to":"IETF RFC 5762","kind":"references","source":"IETF/RFC-5968/RFC-5968.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5762","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5762","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5762","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 5764","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-5764/RFC-5764.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 5763","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 5764","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 3263","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-3263/RFC-3263.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 5767","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5767/RFC-5767.txt"},{"from":"IETF RFC 5770","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5770/RFC-5770.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5928","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5928/RFC-5928.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 6062","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6062/RFC-6062.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6263","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6263/RFC-6263.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5766","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 5763","to":"IETF RFC 5767","kind":"references","source":"IETF/RFC-5763/RFC-5763.txt"},{"from":"IETF RFC 5853","to":"IETF RFC 5767","kind":"references","source":"IETF/RFC-5853/RFC-5853.txt"},{"from":"IETF RFC 5245","to":"IETF RFC 5768","kind":"references","source":"IETF/RFC-5245/RFC-5245.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5768","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5769","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 5770","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6761","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-6761/RFC-6761.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5771","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 5776","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-5776/RFC-5776.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5775","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 5776","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 5776","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5776","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 5778","to":"IETF RFC 5777","kind":"references","source":"IETF/RFC-5778/RFC-5778.txt"},{"from":"IETF RFC 5866","to":"IETF RFC 5777","kind":"references","source":"IETF/RFC-5866/RFC-5866.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5777","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 5777","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 5779","to":"IETF RFC 5778","kind":"references","source":"IETF/RFC-5779/RFC-5779.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 5778","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5778","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 5779","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5779","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 5779","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 5780","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5780","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5780","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 5780","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5781","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 5782","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 5782","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5782","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 5782","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 5783","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5783","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8307","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8307/RFC-8307.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 5785","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 5785","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF RFC 9051","to":"IETF RFC 5788","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7396","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-7396/RFC-7396.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5789","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 579","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5790","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 5790","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 5793","to":"IETF RFC 5792","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5792","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5792","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5792","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 5792","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 5792","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 5793","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 5761","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-5761/RFC-5761.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 5795","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5796","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 5796","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 5796","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 5798","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 5798","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 5798","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 580","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5801","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 5801","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5801","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5803","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-5803/RFC-5803.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 5802","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5803","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 5804","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5804","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 5804","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5804","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5808","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5808","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5808","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5808","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 5982","to":"IETF RFC 5815","kind":"references","source":"IETF/RFC-5982/RFC-5982.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 5815","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5815","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 5815","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5815","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 421 V1.3.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"ETSI TS 101 861 V1.4.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 5816","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 6372","to":"IETF RFC 5817","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 5819","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 5819","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 5819","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 5819","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5825","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 5826","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 5827","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5827","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 5827","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 5827","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 5827","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5829","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 5829","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 5830","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 5831","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5933","to":"IETF RFC 5832","kind":"references","source":"IETF/RFC-5933/RFC-5933.txt"},{"from":"IETF RFC 5834","to":"IETF RFC 5833","kind":"references","source":"IETF/RFC-5834/RFC-5834.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5833","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5833","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 5833","to":"IETF RFC 5834","kind":"references","source":"IETF/RFC-5833/RFC-5833.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5834","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 5834","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 6049","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 5835","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 5873","to":"IETF RFC 5836","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5836","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 5837","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5837","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5838","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6665","to":"IETF RFC 5839","kind":"references","source":"IETF/RFC-6665/RFC-6665.txt"},{"from":"IETF RFC 5879","to":"IETF RFC 5840","kind":"references","source":"IETF/RFC-5879/RFC-5879.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5840","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5845","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-5845/RFC-5845.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6279","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-6279/RFC-6279.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 5844","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 6224","to":"IETF RFC 5845","kind":"references","source":"IETF/RFC-6224/RFC-6224.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 5845","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 5845","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 5848","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5848","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5849","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 5849","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5851","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5851","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5852","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5853","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5853","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5853","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 7092","to":"IETF RFC 5853","kind":"references","source":"IETF/RFC-7092/RFC-7092.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 5853","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 5855","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 5855","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5855","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5855","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5856","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 5856","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5856","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 5857","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5858","to":"IETF RFC 5857","kind":"references","source":"IETF/RFC-5858/RFC-5858.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5857","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5857","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5857","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 5856","to":"IETF RFC 5858","kind":"references","source":"IETF/RFC-5856/RFC-5856.txt"},{"from":"IETF RFC 5857","to":"IETF RFC 5858","kind":"references","source":"IETF/RFC-5857/RFC-5857.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5858","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 586","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5860","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 5861","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 5861","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 5861","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 5861","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5863","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5863","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5863","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5863","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 5864","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5864","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 5865","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 5865","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5866","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5866","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 5866","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5866","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7102","to":"IETF RFC 5867","kind":"references","source":"IETF/RFC-7102/RFC-7102.txt"},{"from":"IETF RFC 5931","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-5931/RFC-5931.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8937","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 5869","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 5870","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 5870","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 5871","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 5873","to":"IETF RFC 5872","kind":"references","source":"IETF/RFC-5873/RFC-5873.txt"},{"from":"IETF RFC 6677","to":"IETF RFC 5873","kind":"references","source":"IETF/RFC-6677/RFC-6677.txt"},{"from":"IETF RFC 5878","to":"IETF RFC 5877","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 6042","to":"IETF RFC 5878","kind":"references","source":"IETF/RFC-6042/RFC-6042.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5878","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 5878","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 5878","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5878","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5879","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5880","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5881","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5881","to":"IETF RFC 5882","kind":"references","source":"IETF/RFC-5881/RFC-5881.txt"},{"from":"IETF RFC 5885","to":"IETF RFC 5882","kind":"references","source":"IETF/RFC-5885/RFC-5885.txt"},{"from":"IETF RFC 6213","to":"IETF RFC 5882","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 5882","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5882","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5883","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5884","to":"IETF RFC 5883","kind":"references","source":"IETF/RFC-5884/RFC-5884.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5883","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5883","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5882","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-5882/RFC-5882.txt"},{"from":"IETF RFC 5883","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-5883/RFC-5883.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5884","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5885","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 5885","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5885","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5902","to":"IETF RFC 5887","kind":"references","source":"IETF/RFC-5902/RFC-5902.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5887","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 5887","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 5887","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 5939","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 5956","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-5956/RFC-5956.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 7104","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-7104/RFC-7104.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5888","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5889","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 5889","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5893","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-5893/RFC-5893.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6066","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6630","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6630/RFC-6630.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5890","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5893","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-5893/RFC-5893.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 5895","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-5895/RFC-5895.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6068","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5891","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6452","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-6452/RFC-6452.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5892","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5893","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5891","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-5891/RFC-5891.txt"},{"from":"IETF RFC 5892","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-5892/RFC-5892.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5894","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6265","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 5895","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 5898","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 5901","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5901","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 5901","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 5901","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 5901","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 5902","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5902","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 5902","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 5902","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 5903","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 5906","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-5906/RFC-5906.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6051","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6051/RFC-6051.txt"},{"from":"IETF RFC 6105","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6105/RFC-6105.txt"},{"from":"IETF RFC 6222","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6222/RFC-6222.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 7164","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7164/RFC-7164.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 5905","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 5906","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5908","to":"IETF RFC 5906","kind":"references","source":"IETF/RFC-5908/RFC-5908.txt"},{"from":"IETF RFC 7384","to":"IETF RFC 5906","kind":"references","source":"IETF/RFC-7384/RFC-7384.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 5906","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5908","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5908","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 5908","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 5909","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 5909","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 5909","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5910","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 5910","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5910","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5910","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5911","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 5912","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 5911","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5912","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"IETF RFC 5912","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"IETF RFC 5911","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5914","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5915","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5940","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6025","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6025/RFC-6025.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6210","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6210/RFC-6210.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6277","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6277/RFC-6277.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 5912","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 5934","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5937","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 5914","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 5958","to":"IETF RFC 5915","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5918","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 5918","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 5919","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5918","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-5918/RFC-5918.txt"},{"from":"IETF RFC 5919","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-5919/RFC-5919.txt"},{"from":"IETF RFC 5921","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6073","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6073/RFC-6073.txt"},{"from":"IETF RFC 6348","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6348/RFC-6348.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6391","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6391/RFC-6391.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6941","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6941/RFC-6941.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 5920","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 5960","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-5960/RFC-5960.txt"},{"from":"IETF RFC 6215","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6215/RFC-6215.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6941","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-6941/RFC-6941.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 5921","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 5923","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-5923/RFC-5923.txt"},{"from":"IETF RFC 5924","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6230","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 5922","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 5923","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5922","to":"IETF RFC 5924","kind":"references","source":"IETF/RFC-5922/RFC-5922.txt"},{"from":"IETF RFC 5926","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-5926/RFC-5926.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 5925","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 5926","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 5926","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 5926","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5926","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5926","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 5927","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 7065","to":"IETF RFC 5928","kind":"references","source":"IETF/RFC-7065/RFC-7065.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 5928","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 5928","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 5801","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6813","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-6813/RFC-6813.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 5929","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 593","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 593","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5930","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5931","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5931","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 5931","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5932","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6367","to":"IETF RFC 5932","kind":"references","source":"IETF/RFC-6367/RFC-6367.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 5933","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 5937","to":"IETF RFC 5934","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 6010","to":"IETF RFC 5934","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6024","to":"IETF RFC 5934","kind":"references","source":"IETF/RFC-6024/RFC-6024.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 5934","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 5936","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6818","to":"IETF RFC 5937","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6871","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-6871/RFC-6871.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5939","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 5940","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 5985","to":"IETF RFC 5941","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 5941","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 5942","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5942","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5942","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5942","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 6245","to":"IETF RFC 5944","kind":"references","source":"IETF/RFC-6245/RFC-6245.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5944","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 5944","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 5944","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 5944","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 5951","to":"IETF RFC 5950","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 5950","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 5951","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 5953","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-5953/RFC-5953.txt"},{"from":"IETF RFC 5954","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-5954/RFC-5954.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6052","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6052/RFC-6052.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 6874","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6874/RFC-6874.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 5952","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5953","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6353","to":"IETF RFC 5953","kind":"references","source":"IETF/RFC-6353/RFC-6353.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 5953","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 5954","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 5954","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 5954","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 6015","to":"IETF RFC 5956","kind":"references","source":"IETF/RFC-6015/RFC-6015.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 5956","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 5956","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 5956","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 5958","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 6072","to":"IETF RFC 5959","kind":"references","source":"IETF/RFC-6072/RFC-6072.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 596","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6370","to":"IETF RFC 5960","kind":"references","source":"IETF/RFC-6370/RFC-6370.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 5960","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 5960","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 5960","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 5961","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5964","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6430","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6430/RFC-6430.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 5965","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 5966","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 5967","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 5968","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 5968","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 5969","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 597","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 606","to":"IETF RFC 597","kind":"references","source":"IETF/RFC-606/RFC-606.txt"},{"from":"IETF RFC 6853","to":"IETF RFC 5970","kind":"references","source":"IETF/RFC-6853/RFC-6853.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 5970","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5970","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 5970","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5971","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5973","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5973","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 5973","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5974","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5974","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 5974","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5974","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5974","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5975","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5976","to":"IETF RFC 5975","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5975","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 5978","to":"IETF RFC 5975","kind":"references","source":"IETF/RFC-5978/RFC-5978.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5976","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5974","to":"IETF RFC 5977","kind":"references","source":"IETF/RFC-5974/RFC-5974.txt"},{"from":"IETF RFC 5975","to":"IETF RFC 5977","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5971","to":"IETF RFC 5978","kind":"references","source":"IETF/RFC-5971/RFC-5971.txt"},{"from":"IETF RFC 5973","to":"IETF RFC 5978","kind":"references","source":"IETF/RFC-5973/RFC-5973.txt"},{"from":"IETF RFC 5977","to":"IETF RFC 5978","kind":"references","source":"IETF/RFC-5977/RFC-5977.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 5978","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6183","to":"IETF RFC 5982","kind":"references","source":"IETF/RFC-6183/RFC-6183.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 5982","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5982","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 5982","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 5983","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 5986","to":"IETF RFC 5985","kind":"references","source":"IETF/RFC-5986/RFC-5986.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 5985","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5985","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 5985","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5985","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 5986","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 5986","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 5986","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 5986","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 5988","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-5988/RFC-5988.txt"},{"from":"IETF RFC 6266","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 5987","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 5989","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-5989/RFC-5989.txt"},{"from":"IETF RFC 6415","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-6415/RFC-6415.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 5988","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 5989","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 5990","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 5990","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 5991","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 5991","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 5998","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-5998/RFC-5998.txt"},{"from":"IETF RFC 6027","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6027/RFC-6027.txt"},{"from":"IETF RFC 6040","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6040/RFC-6040.txt"},{"from":"IETF RFC 6054","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6054/RFC-6054.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6090","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6090/RFC-6090.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6124","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6193","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6193/RFC-6193.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6281","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6281/RFC-6281.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6320","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 5996","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 5997","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 5997","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 5997","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 5998","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 5998","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 600","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 601","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 6010","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 6012","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6012","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6012","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 6013","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 6013","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6013","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6014","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 6015","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 6019","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 6019","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6019","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 6019","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6095","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6095/RFC-6095.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6243","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6243/RFC-6243.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6020","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6087","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6087/RFC-6087.txt"},{"from":"IETF RFC 6110","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6021","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6022","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6024","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 6024","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 6024","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 6024","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 6268","to":"IETF RFC 6025","kind":"references","source":"IETF/RFC-6268/RFC-6268.txt"},{"from":"IETF RFC 6071","to":"IETF RFC 6027","kind":"references","source":"IETF/RFC-6071/RFC-6071.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 603","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 6030","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 6030","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 6030","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 6063","to":"IETF RFC 6031","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6031","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 6034","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 6034","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 6035","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6035","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 6035","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6036","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6039","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 6040","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 6042","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6042","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6267","to":"IETF RFC 6043","kind":"references","source":"IETF/RFC-6267/RFC-6267.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 6043","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 6043","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6043","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 6046","to":"IETF RFC 6045","kind":"references","source":"IETF/RFC-6046/RFC-6046.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 6045","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6045","to":"IETF RFC 6046","kind":"references","source":"IETF/RFC-6045/RFC-6045.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 6046","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6047","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6248","to":"IETF RFC 6049","kind":"references","source":"IETF/RFC-6248/RFC-6248.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 6049","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 6049","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7160","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-7160/RFC-7160.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6051","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6052","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6407","to":"IETF RFC 6054","kind":"references","source":"IETF/RFC-6407/RFC-6407.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6055","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6169","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6169/RFC-6169.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6056","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 6789","to":"IETF RFC 6057","kind":"references","source":"IETF/RFC-6789/RFC-6789.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 6057","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 6057","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 6059","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 606","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 623","to":"IETF RFC 606","kind":"references","source":"IETF/RFC-623/RFC-623.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 6062","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 6062","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 6062","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6062","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 6062","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 6031","to":"IETF RFC 6063","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6064","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6065","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 6066","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 6091","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6091/RFC-6091.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6961","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 6962","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-6962/RFC-6962.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7366","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7366/RFC-7366.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 6066","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 6047","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 6068","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6069","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 614","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-614/RFC-614.txt"},{"from":"IETF RFC 624","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-624/RFC-624.txt"},{"from":"IETF RFC 7159","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-7159/RFC-7159.txt"},{"from":"IETF RFC 959","to":"IETF RFC 607","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6071","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 6071","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 6071","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 6072","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 6074","to":"IETF RFC 6073","kind":"references","source":"IETF/RFC-6074/RFC-6074.txt"},{"from":"IETF RFC 6136","to":"IETF RFC 6074","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6074","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 6074","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 6077","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 6077","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6077","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 608","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 623","to":"IETF RFC 608","kind":"references","source":"IETF/RFC-623/RFC-623.txt"},{"from":"IETF RFC 810","to":"IETF RFC 608","kind":"references","source":"IETF/RFC-810/RFC-810.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 6080","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6080","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 6081","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6081","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6083","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6084","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 6085","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 6086","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 6086","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 6087","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6087","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 6087","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6087","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 6089","to":"IETF RFC 6088","kind":"references","source":"IETF/RFC-6089/RFC-6089.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 6089","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6294","to":"IETF RFC 6089","kind":"references","source":"IETF/RFC-6294/RFC-6294.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6278","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7748","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7748/RFC-7748.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 6090","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 6091","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6091","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6091","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 6092","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 6093","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6093","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 6093","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6095","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 6096","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 6096","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 6096","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6101","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 6105","to":"IETF RFC 6104","kind":"references","source":"IETF/RFC-6105/RFC-6105.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 6104","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 6104","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 6104","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 6104","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 6104","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-6104/RFC-6104.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 6105","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 6106","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 6561","to":"IETF RFC 6108","kind":"references","source":"IETF/RFC-6561/RFC-6561.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6108","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 6110","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6110","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6110","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 6110","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6115","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6115","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 6116","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 6116","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 6118","to":"IETF RFC 6117","kind":"references","source":"IETF/RFC-6118/RFC-6118.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 6117","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 6117","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6117","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 6118","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 6118","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 6119","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6122","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6280","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6280/RFC-6280.txt"},{"from":"IETF RFC 6366","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8073","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8073/RFC-8073.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 6120","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6121","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 6122","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 6122","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 6122","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 6122","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6122","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6123","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6124","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6121","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6121/RFC-6121.txt"},{"from":"IETF RFC 6186","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6186/RFC-6186.txt"},{"from":"IETF RFC 6394","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6394/RFC-6394.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6749","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 6125","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6127","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 6127","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 6128","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6128","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6622","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-6622/RFC-6622.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 6130","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 6714","to":"IETF RFC 6135","kind":"references","source":"IETF/RFC-6714/RFC-6714.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 6135","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6136","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 6136","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 614","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 614","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6337","to":"IETF RFC 6141","kind":"references","source":"IETF/RFC-6337/RFC-6337.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6204","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6204/RFC-6204.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6459","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-6459/RFC-6459.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6144","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6156","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6156/RFC-6156.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6145","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6147","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6147/RFC-6147.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6269","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6269/RFC-6269.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6970","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-6970/RFC-6970.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7498","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7498/RFC-7498.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6146","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6144","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6144/RFC-6144.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6147","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6149","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 6149","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 6149","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 6149","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 6149","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 615","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6150","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6150","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6150/RFC-6150.txt"},{"from":"IETF RFC 6176","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6176/RFC-6176.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7292","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 7693","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-7693/RFC-7693.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 6151","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 6152","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 6154","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6154","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6157","to":"IETF RFC 6156","kind":"references","source":"IETF/RFC-6157/RFC-6157.txt"},{"from":"IETF RFC 6544","to":"IETF RFC 6156","kind":"references","source":"IETF/RFC-6544/RFC-6544.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 6157","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 6157","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6421","to":"IETF RFC 6158","kind":"references","source":"IETF/RFC-6421/RFC-6421.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6158","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 6158","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6929","to":"IETF RFC 6158","kind":"references","source":"IETF/RFC-6929/RFC-6929.txt"},{"from":"IETF RFC 6583","to":"IETF RFC 6164","kind":"references","source":"IETF/RFC-6583/RFC-6583.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6164","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 6164","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6164","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6165","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 6127","to":"IETF RFC 6169","kind":"references","source":"IETF/RFC-6127/RFC-6127.txt"},{"from":"IETF RFC 6180","to":"IETF RFC 6169","kind":"references","source":"IETF/RFC-6180/RFC-6180.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6169","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 6169","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 6169","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6176","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 6177","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6180","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 6180","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6535","to":"IETF RFC 6180","kind":"references","source":"IETF/RFC-6535/RFC-6535.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 6181","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 6181","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 6181","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6181","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6181","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 6182","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 6182","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6182","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6182","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6235","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-6235/RFC-6235.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 6183","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 6190","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6236","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 6184","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 6186","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6187","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 6189","to":"IETF RFC 6188","kind":"references","source":"IETF/RFC-6189/RFC-6189.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 6188","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6188","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 6562","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-6562/RFC-6562.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6189","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 6190","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 6190","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 6190","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6191","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6191","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6193","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6234","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-6234/RFC-6234.txt"},{"from":"IETF RFC 6275","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-6275/RFC-6275.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6584","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-6584/RFC-6584.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 6194","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 6686","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-6686/RFC-6686.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 6195","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 6202","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 6202","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 6264","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-6264/RFC-6264.txt"},{"from":"IETF RFC 6296","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-6296/RFC-6296.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6204","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6206","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 6206","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6206","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6211","to":"IETF RFC 6210","kind":"references","source":"IETF/RFC-6211/RFC-6211.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 6211","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 7515","to":"IETF RFC 6211","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 6212","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 6213","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 6213","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6213","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 6215","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 6219","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6219","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6219","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6219","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 6221","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 6221","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6221","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 6222","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 6222","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 7022","to":"IETF RFC 6222","kind":"references","source":"IETF/RFC-7022/RFC-7022.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6222","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 6224","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 6225","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 6225","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6225","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 6225","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 6225","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 6229","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 6229","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 625","to":"IETF RFC 623","kind":"references","source":"IETF/RFC-625/RFC-625.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6230","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6230","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6233","to":"IETF RFC 6232","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 6232","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 6232","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 6232","to":"IETF RFC 6233","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 6233","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 6233","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 6506","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6506/RFC-6506.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6931","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7218","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7218/RFC-7218.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7693","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7693/RFC-7693.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8032","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8032/RFC-8032.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6234","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 6235","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 6236","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6236","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 6236","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 6236","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6236","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 624","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 624","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 959","to":"IETF RFC 624","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6242","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6242/RFC-6242.txt"},{"from":"IETF RFC 6243","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6243/RFC-6243.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6536","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6536/RFC-6536.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 6241","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 6241","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6470","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-6470/RFC-6470.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 6242","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 6244","to":"IETF RFC 6243","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6243","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6244","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 6244","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 6245","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 6247","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 6247","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6247","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 6248","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6248","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 625","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6250","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 6250","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6250","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 6256","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 6263","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6849","to":"IETF RFC 6263","kind":"references","source":"IETF/RFC-6849/RFC-6849.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 6263","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 6263","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6263","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 6264","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6264","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6750","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6265","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 6266","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 6266","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 6266","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 6266","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 6267","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6267","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 6268","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 8520","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 6268","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 6302","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6302/RFC-6302.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6343","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6343/RFC-6343.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 6269","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 6271","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 6272","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6272","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 6272","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6272","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 6946","to":"IETF RFC 6274","kind":"references","source":"IETF/RFC-6946/RFC-6946.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6274","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 6274","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6274","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6636","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6636/RFC-6636.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6757","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6275","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 6960","to":"IETF RFC 6277","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 6278","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 6705","to":"IETF RFC 6279","kind":"references","source":"IETF/RFC-6705/RFC-6705.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 6279","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 6442","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6442/RFC-6442.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6772","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6772/RFC-6772.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 6280","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 6281","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6281","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 6281","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6568","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-6568/RFC-6568.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6775","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-6775/RFC-6775.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 6282","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 162-2 V1.1.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/EN-319-162-2-V1.1.1/EN-319-162-2-V1.1.1.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 6283","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 6285","to":"IETF RFC 6284","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6284","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 6285","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6642","to":"IETF RFC 6285","kind":"references","source":"IETF/RFC-6642/RFC-6642.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 6285","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6285","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6288","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7319","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7319/RFC-7319.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 6291","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 6294","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6294","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6296","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 6297","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 6297","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6817","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"IETF RFC 6928","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-6928/RFC-6928.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 6298","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 630","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 686","to":"IETF RFC 630","kind":"references","source":"IETF/RFC-686/RFC-686.txt"},{"from":"IETF RFC 691","to":"IETF RFC 630","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 959","to":"IETF RFC 630","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 6302","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6302","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6302","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 6303","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 6303","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 7793","to":"IETF RFC 6303","kind":"references","source":"IETF/RFC-7793/RFC-7793.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6303","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6303","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 6304","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6305","to":"IETF RFC 6304","kind":"references","source":"IETF/RFC-6305/RFC-6305.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 6304","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6303","to":"IETF RFC 6305","kind":"references","source":"IETF/RFC-6303/RFC-6303.txt"},{"from":"IETF RFC 6304","to":"IETF RFC 6305","kind":"references","source":"IETF/RFC-6304/RFC-6304.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6310","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6310","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6313","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6313","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 6313","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 6313","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 6317","to":"IETF RFC 6316","kind":"references","source":"IETF/RFC-6317/RFC-6317.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 6316","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6316","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6316","to":"IETF RFC 6317","kind":"references","source":"IETF/RFC-6316/RFC-6316.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6317","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 6318","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6320","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 6321","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 6321","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 6323","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6324","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6324","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6905","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-6905/RFC-6905.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 6325","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 6325","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6327","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6361","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6326","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 6327","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6439","to":"IETF RFC 6327","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6327","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 6327","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 6327","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 6326","to":"IETF RFC 6328","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6329","to":"IETF RFC 6328","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6328","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6328","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 6328","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6329","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 633","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 6331","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 6334","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6334/RFC-6334.txt"},{"from":"IETF RFC 6346","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6346/RFC-6346.txt"},{"from":"IETF RFC 6619","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6619/RFC-6619.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6970","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-6970/RFC-6970.txt"},{"from":"IETF RFC 7040","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7040/RFC-7040.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7335","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7335/RFC-7335.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6333","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 6333","to":"IETF RFC 6334","kind":"references","source":"IETF/RFC-6333/RFC-6333.txt"},{"from":"IETF RFC 7040","to":"IETF RFC 6334","kind":"references","source":"IETF/RFC-7040/RFC-7040.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6334","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6334","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 6408","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6408/RFC-6408.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7348","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7348/RFC-7348.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7595","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7595/RFC-7595.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6335","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 6336","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6336","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 6336","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 6336","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 7088","to":"IETF RFC 6337","kind":"references","source":"IETF/RFC-7088/RFC-7088.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 6340","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 6340","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6324","to":"IETF RFC 6343","kind":"references","source":"IETF/RFC-6324/RFC-6324.txt"},{"from":"IETF RFC 6598","to":"IETF RFC 6343","kind":"references","source":"IETF/RFC-6598/RFC-6598.txt"},{"from":"IETF RFC 6431","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-6431/RFC-6431.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 6346","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 6460","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6460/RFC-6460.txt"},{"from":"IETF RFC 6520","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6520/RFC-6520.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6655","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6655/RFC-6655.txt"},{"from":"IETF RFC 6679","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7027","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7345","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7345/RFC-7345.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7366","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7366/RFC-7366.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7507","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7507/RFC-7507.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7562","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7562/RFC-7562.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6347","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 6348","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 6348","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6703","to":"IETF RFC 6349","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6349","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6351","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-6351/RFC-6351.txt"},{"from":"IETF RFC 6352","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-6352/RFC-6352.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 6350","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 6350","to":"IETF RFC 6351","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6868","to":"IETF RFC 6351","kind":"references","source":"IETF/RFC-6868/RFC-6868.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 6351","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 6352","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6615","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-6615/RFC-6615.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6779","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-6779/RFC-6779.txt"},{"from":"IETF RFC 6933","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-6933/RFC-6933.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6353","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 6355","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 6355","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 6355","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6355","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 6356","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6356","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6356","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 6360","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 6361","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 6364","to":"IETF RFC 6363","kind":"references","source":"IETF/RFC-6364/RFC-6364.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 6363","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 6363","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 6363","to":"IETF RFC 6364","kind":"references","source":"IETF/RFC-6363/RFC-6363.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6364","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6570","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6912","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-6912/RFC-6912.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6365","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 6366","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6367","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 6368","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 6371","to":"IETF RFC 6370","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6371","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 6372","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 6372","to":"IETF RFC 6373","kind":"references","source":"IETF/RFC-6372/RFC-6372.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6374","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6374","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 6374","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 6374","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 6374","to":"IETF RFC 6375","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6375","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6375","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6377","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6377/RFC-6377.txt"},{"from":"IETF RFC 6409","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6409/RFC-6409.txt"},{"from":"IETF RFC 6430","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6430/RFC-6430.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6541","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6541/RFC-6541.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6376","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6376","to":"IETF RFC 6377","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6377","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6378","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6380","to":"IETF RFC 6379","kind":"references","source":"IETF/RFC-6380/RFC-6380.txt"},{"from":"IETF RFC 7321","to":"IETF RFC 6379","kind":"references","source":"IETF/RFC-7321/RFC-7321.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 638","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6379","to":"IETF RFC 6380","kind":"references","source":"IETF/RFC-6379/RFC-6379.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 6382","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6386","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 6386","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 6386","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 6389","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6389/RFC-6389.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6388","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6388","to":"IETF RFC 6389","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6707","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6707/RFC-6707.txt"},{"from":"IETF RFC 6770","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 6776","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6776/RFC-6776.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 6390","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 6391","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6790","to":"IETF RFC 6391","kind":"references","source":"IETF/RFC-6790/RFC-6790.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6391","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 6394","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6394","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6397","to":"IETF RFC 6396","kind":"references","source":"IETF/RFC-6397/RFC-6397.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6396","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 6397","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 686","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-686/RFC-686.txt"},{"from":"IETF RFC 691","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 739","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 775","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-775/RFC-775.txt"},{"from":"IETF RFC 959","to":"IETF RFC 640","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6403","to":"IETF RFC 6402","kind":"references","source":"IETF/RFC-6403/RFC-6403.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6402","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 6402","to":"IETF RFC 6403","kind":"references","source":"IETF/RFC-6402/RFC-6402.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6403","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 6404","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6406","to":"IETF RFC 6405","kind":"references","source":"IETF/RFC-6406/RFC-6406.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 6406","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 6518","to":"IETF RFC 6407","kind":"references","source":"IETF/RFC-6518/RFC-6518.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6408","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 6408","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6647","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-6647/RFC-6647.txt"},{"from":"IETF RFC 6785","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-6785/RFC-6785.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6409","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6576","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-6576/RFC-6576.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7063","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-7063/RFC-7063.txt"},{"from":"IETF RFC 7127","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-7127/RFC-7127.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 6410","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 6415","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6415","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6415","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 6419","to":"IETF RFC 6418","kind":"references","source":"IETF/RFC-6419/RFC-6419.txt"},{"from":"IETF RFC 6731","to":"IETF RFC 6418","kind":"references","source":"IETF/RFC-6731/RFC-6731.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6418","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6418","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 6418","to":"IETF RFC 6419","kind":"references","source":"IETF/RFC-6418/RFC-6418.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6419","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 6419","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 6421","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6440","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-6440/RFC-6440.txt"},{"from":"IETF RFC 6610","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-6610/RFC-6610.txt"},{"from":"IETF RFC 6977","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-6977/RFC-6977.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6422","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6423","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 6424","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6424","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 6425","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6425","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6426","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6426","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6427","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6427","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6428","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6428","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 6429","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6429","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 840","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 643","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6430","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6430","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6431","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 6540","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-6540/RFC-6540.txt"},{"from":"IETF RFC 6606","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-6606/RFC-6606.txt"},{"from":"IETF RFC 6672","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-6672/RFC-6672.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 6434","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6435","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6435","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 6436","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6436","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6438","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-6438/RFC-6438.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 6437","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 6436","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-6436/RFC-6436.txt"},{"from":"IETF RFC 6437","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-6437/RFC-6437.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7098","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-7098/RFC-7098.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 6438","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 6439","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 6422","to":"IETF RFC 6440","kind":"references","source":"IETF/RFC-6422/RFC-6422.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6440","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 6443","to":"IETF RFC 6442","kind":"references","source":"IETF/RFC-6443/RFC-6443.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 6442","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6442","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6444","to":"IETF RFC 6443","kind":"references","source":"IETF/RFC-6444/RFC-6444.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6443","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 6443","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 6444","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 6590","to":"IETF RFC 6449","kind":"references","source":"IETF/RFC-6590/RFC-6590.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6449","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 6452","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 6452","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 6452","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 6455","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6555","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6555/RFC-6555.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6454","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6454","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-6454/RFC-6454.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8307","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8307/RFC-8307.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6455","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6525","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-6525/RFC-6525.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7765","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-7765/RFC-7765.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 6458","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 6877","to":"IETF RFC 6459","kind":"references","source":"IETF/RFC-6877/RFC-6877.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6459","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7278","to":"IETF RFC 6459","kind":"references","source":"IETF/RFC-7278/RFC-7278.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 6459","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 6605","to":"IETF RFC 6460","kind":"references","source":"IETF/RFC-6605/RFC-6605.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6460","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6460","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6465","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 6464","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 6464","to":"IETF RFC 6465","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6904","to":"IETF RFC 6465","kind":"references","source":"IETF/RFC-6904/RFC-6904.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 6465","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6465","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 6465","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 6466","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6470","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6478","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 6480","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6481","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6483","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6483/RFC-6483.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6482","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6483","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6483","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6484","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6485","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6486","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6488","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6488/RFC-6488.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6490","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6490/RFC-6490.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6492","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6487","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6482","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6485","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6485/RFC-6485.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6489","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6489/RFC-6489.txt"},{"from":"IETF RFC 6493","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-6493/RFC-6493.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6488","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6486","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6487","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6489","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6490","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6481","to":"IETF RFC 6490","kind":"references","source":"IETF/RFC-6481/RFC-6481.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6490","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6480","to":"IETF RFC 6491","kind":"references","source":"IETF/RFC-6480/RFC-6480.txt"},{"from":"IETF RFC 6484","to":"IETF RFC 6492","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6492","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 6493","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6916","to":"IETF RFC 6493","kind":"references","source":"IETF/RFC-6916/RFC-6916.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6493","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6495","to":"IETF RFC 6494","kind":"references","source":"IETF/RFC-6495/RFC-6495.txt"},{"from":"IETF RFC 6496","to":"IETF RFC 6494","kind":"references","source":"IETF/RFC-6496/RFC-6496.txt"},{"from":"IETF RFC 6980","to":"IETF RFC 6494","kind":"references","source":"IETF/RFC-6980/RFC-6980.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 6495","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6494","to":"IETF RFC 6496","kind":"references","source":"IETF/RFC-6494/RFC-6494.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 6496","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 6501","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 6501","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6501","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 6503","to":"IETF RFC 6502","kind":"references","source":"IETF/RFC-6503/RFC-6503.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 6502","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 6503","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6503","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6504","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 6504","to":"IETF RFC 6505","kind":"references","source":"IETF/RFC-6504/RFC-6504.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 6506","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 6507","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 6508","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6509","to":"IETF RFC 6508","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6507","to":"IETF RFC 6509","kind":"references","source":"IETF/RFC-6507/RFC-6507.txt"},{"from":"IETF RFC 6508","to":"IETF RFC 6509","kind":"references","source":"IETF/RFC-6508/RFC-6508.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6509","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 651","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 859","to":"IETF RFC 651","kind":"references","source":"IETF/RFC-859/RFC-859.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 6510","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6510","to":"IETF RFC 6511","kind":"references","source":"IETF/RFC-6510/RFC-6510.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 6511","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6511","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6512","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 6511","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-6511/RFC-6511.txt"},{"from":"IETF RFC 6512","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-6512/RFC-6512.txt"},{"from":"IETF RFC 6514","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-6514/RFC-6514.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 6513","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 6513","to":"IETF RFC 6514","kind":"references","source":"IETF/RFC-6513/RFC-6513.txt"},{"from":"IETF RFC 7117","to":"IETF RFC 6514","kind":"references","source":"IETF/RFC-7117/RFC-7117.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 6514","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 6514","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 6514","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6518","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6862","to":"IETF RFC 6518","kind":"references","source":"IETF/RFC-6862/RFC-6862.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 6518","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 6518","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 652","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 6520","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 6522","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 6522","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 6522","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6522","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 6526","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-6526/RFC-6526.txt"},{"from":"IETF RFC 7053","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-7053/RFC-7053.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 6525","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6526","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6526","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6526","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6528","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6528","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6528","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 653","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 6530","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 6531","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6532","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 6533","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"IETF RFC 6533","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6533","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 6533","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6533","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6535","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6643","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-6643/RFC-6643.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 6536","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 654","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6540","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6540","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 6541","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7850","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-7850/RFC-7850.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 6544","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 6546","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-6546/RFC-6546.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8073","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-8073/RFC-8073.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 6545","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 6545","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-6545/RFC-6545.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 7203","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-7203/RFC-7203.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 6546","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 6549","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 655","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6552","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6552/RFC-6552.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6554","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6554/RFC-6554.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 6550","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6551","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6552","to":"IETF RFC 6551","kind":"references","source":"IETF/RFC-6552/RFC-6552.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6551","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 6551","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 6551","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6552","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6551","to":"IETF RFC 6552","kind":"references","source":"IETF/RFC-6551/RFC-6551.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6552","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6553","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6553","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6550","to":"IETF RFC 6554","kind":"references","source":"IETF/RFC-6550/RFC-6550.txt"},{"from":"IETF RFC 6553","to":"IETF RFC 6554","kind":"references","source":"IETF/RFC-6553/RFC-6553.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6554","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 6554","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 6554","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6555","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6555","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6555","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6555","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 6557","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 656","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6561","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 6561","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6561","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6561","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6716","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-6716/RFC-6716.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6562","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6563","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7045","to":"IETF RFC 6564","kind":"references","source":"IETF/RFC-7045/RFC-7045.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 6564","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 6568","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 657","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6690","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 6570","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 6574","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6574","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 6574","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 6576","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 6576","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 6576","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 6576","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 6576","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 6577","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 658","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 6582","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6582","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 6582","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 6582","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 6583","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6583","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6583","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 6583","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 6726","to":"IETF RFC 6584","kind":"references","source":"IETF/RFC-6726/RFC-6726.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 6585","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 6590","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6590","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6590","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6591","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 6591","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 6591","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6591","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6591","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6598","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6724","to":"IETF RFC 6598","kind":"references","source":"IETF/RFC-6724/RFC-6724.txt"},{"from":"IETF RFC 6791","to":"IETF RFC 6598","kind":"references","source":"IETF/RFC-6791/RFC-6791.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 6598","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7793","to":"IETF RFC 6598","kind":"references","source":"IETF/RFC-7793/RFC-7793.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6603","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6603","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6603","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6603","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6603","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 6604","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 6781","to":"IETF RFC 6605","kind":"references","source":"IETF/RFC-6781/RFC-6781.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 6606","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 6607","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 6607","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 6607","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6610","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 6614","to":"IETF RFC 6613","kind":"references","source":"IETF/RFC-6614/RFC-6614.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6613","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 6613","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 6613","to":"IETF RFC 6614","kind":"references","source":"IETF/RFC-6613/RFC-6613.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 6614","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 6614","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6614","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 6727","to":"IETF RFC 6615","kind":"references","source":"IETF/RFC-6727/RFC-6727.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6615","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6615","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 6615","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 6615","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6619","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6619","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 6620","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 6620","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 6620","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 6620","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 6621","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 6622","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 6627","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 6630","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6632","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 6632","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6633","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7322","to":"IETF RFC 6635","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 6635","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6636","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6639","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6642","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6643","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 6643","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7227","to":"IETF RFC 6644","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6647","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6963","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-6963/RFC-6963.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 6648","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 6649","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 6651","to":"IETF RFC 6650","kind":"references","source":"IETF/RFC-6651/RFC-6651.txt"},{"from":"IETF RFC 6652","to":"IETF RFC 6650","kind":"references","source":"IETF/RFC-6652/RFC-6652.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6650","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6651","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6651","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6651","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 6650","to":"IETF RFC 6652","kind":"references","source":"IETF/RFC-6650/RFC-6650.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6652","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6652","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 6652","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7251","to":"IETF RFC 6655","kind":"references","source":"IETF/RFC-7251/RFC-7251.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6655","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6655","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6655","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 6838","to":"IETF RFC 6657","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 6657","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 6657","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 6660","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 6660","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 6660","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 6660","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 6661","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 6661","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6662","to":"IETF RFC 6661","kind":"references","source":"IETF/RFC-6662/RFC-6662.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 6662","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6660","to":"IETF RFC 6662","kind":"references","source":"IETF/RFC-6660/RFC-6660.txt"},{"from":"IETF RFC 6661","to":"IETF RFC 6662","kind":"references","source":"IETF/RFC-6661/RFC-6661.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6665","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 6910","to":"IETF RFC 6665","kind":"references","source":"IETF/RFC-6910/RFC-6910.txt"},{"from":"IETF RFC 7247","to":"IETF RFC 6665","kind":"references","source":"IETF/RFC-7247/RFC-7247.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 6665","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 6666","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6669","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6669","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6670","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6671","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 6927","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-6927/RFC-6927.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7129","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-7129/RFC-7129.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6672","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 6675","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 6678","to":"IETF RFC 6677","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 6677","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6677","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7029","to":"IETF RFC 6678","kind":"references","source":"IETF/RFC-7029/RFC-7029.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6678","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6679","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 6685","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6686","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 6690","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6691","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6691","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6691","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 6691","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 6694","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 6694","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 6797","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-6797/RFC-6797.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6844","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7218","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7218/RFC-7218.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 6698","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 6702","to":"IETF RFC 6701","kind":"references","source":"IETF/RFC-6702/RFC-6702.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 6701","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 6701","to":"IETF RFC 6702","kind":"references","source":"IETF/RFC-6701/RFC-6701.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 6702","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 6808","to":"IETF RFC 6703","kind":"references","source":"IETF/RFC-6808/RFC-6808.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 6703","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 6703","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 6703","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 6703","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 6705","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 6770","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-6770/RFC-6770.txt"},{"from":"IETF RFC 6983","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-6983/RFC-6983.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 7337","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-7337/RFC-7337.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 6707","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 6708","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6709","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 6713","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 6713","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 6714","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6714","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 6714","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6716","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 6716","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 6716","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6716","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 6716","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6720","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7078","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7078/RFC-7078.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8421","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8421/RFC-8421.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6724","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6726","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 6728","to":"IETF RFC 6727","kind":"references","source":"IETF/RFC-6728/RFC-6728.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6727","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 6728","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 6728","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 6728","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 6731","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 6737","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-6737/RFC-6737.txt"},{"from":"IETF RFC 7155","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-7155/RFC-7155.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 6733","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6736","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 6737","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6739","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 674","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 684","to":"IETF RFC 674","kind":"references","source":"IETF/RFC-684/RFC-684.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6740","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6741","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6742","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6743","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6744","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6745","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6746","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6748","to":"IETF RFC 6747","kind":"references","source":"IETF/RFC-6748/RFC-6748.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6742","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6742/RFC-6742.txt"},{"from":"IETF RFC 6743","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6743/RFC-6743.txt"},{"from":"IETF RFC 6744","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6744/RFC-6744.txt"},{"from":"IETF RFC 6745","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6745/RFC-6745.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 6748","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 6749","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 6749","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 6749","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 6749","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 6750","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-6750/RFC-6750.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 7009","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 6749","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 721","to":"IETF RFC 675","kind":"references","source":"IETF/RFC-721/RFC-721.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 675","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 6750","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 6749","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6819","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-6819/RFC-6819.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 6750","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7522","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 6755","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 6757","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 6760","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6760","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 6761","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6761","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6763","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6762","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6762","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6764","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6764/RFC-6764.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 6763","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6764","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 6770","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 7337","to":"IETF RFC 6770","kind":"references","source":"IETF/RFC-7337/RFC-7337.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 6770","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 6770","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 6770","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 6973","to":"IETF RFC 6772","kind":"references","source":"IETF/RFC-6973/RFC-6973.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6773","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6773","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6957","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-6957/RFC-6957.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 6775","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 6798","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 6776","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 6779","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 840","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 678","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 6840","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-6840/RFC-6840.txt"},{"from":"IETF RFC 7344","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-7344/RFC-7344.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6781","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6851","to":"IETF RFC 6785","kind":"references","source":"IETF/RFC-6851/RFC-6851.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6787","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7141","to":"IETF RFC 6789","kind":"references","source":"IETF/RFC-7141/RFC-7141.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 6789","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 6789","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 6789","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 6789","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 6790","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6790","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 6790","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 6790","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6791","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6791","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 6791","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 6843","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-6843/RFC-6843.txt"},{"from":"IETF RFC 6958","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-6958/RFC-6958.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7266","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6792","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 6793","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 6793","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 6793","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 6793","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 6797","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 6792","to":"IETF RFC 6798","kind":"references","source":"IETF/RFC-6792/RFC-6792.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 6798","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 0713","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-0713/RFC-0713.txt"},{"from":"IETF RFC 0733","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-0733/RFC-0733.txt"},{"from":"IETF RFC 713","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-713/RFC-713.txt"},{"from":"IETF RFC 733","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-733/RFC-733.txt"},{"from":"IETF RFC 753","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 767","to":"IETF RFC 680","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6807","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 7290","to":"IETF RFC 6808","kind":"references","source":"IETF/RFC-7290/RFC-7290.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 6808","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 6808","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 6811","to":"IETF RFC 6810","kind":"references","source":"IETF/RFC-6811/RFC-6811.txt"},{"from":"IETF RFC 7132","to":"IETF RFC 6810","kind":"references","source":"IETF/RFC-7132/RFC-7132.txt"},{"from":"IETF RFC 6810","to":"IETF RFC 6811","kind":"references","source":"IETF/RFC-6810/RFC-6810.txt"},{"from":"IETF RFC 6876","to":"IETF RFC 6813","kind":"references","source":"IETF/RFC-6876/RFC-6876.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 6813","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 6817","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 6818","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 6943","to":"IETF RFC 6818","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 6818","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 6819","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 7009","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-7009/RFC-7009.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 6819","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 6820","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 6820","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 6823","to":"IETF RFC 6822","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 6822","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6822","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 6822","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6822","to":"IETF RFC 6823","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 6823","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 6823","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 6824","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6824","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6824","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 6824","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 6824","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6829","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 739","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 683","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6832","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6832/RFC-6832.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6834","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6834/RFC-6834.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 6830","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6831","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 6831","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6832","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 6832","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6834","to":"IETF RFC 6832","kind":"references","source":"IETF/RFC-6834/RFC-6834.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 6832","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 6832","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6833","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 6833","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6836","to":"IETF RFC 6833","kind":"references","source":"IETF/RFC-6836/RFC-6836.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 6833","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6834","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6835","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6831","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6831/RFC-6831.txt"},{"from":"IETF RFC 6832","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6832/RFC-6832.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"IETF RFC 6837","to":"IETF RFC 6836","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 6837","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6833","to":"IETF RFC 6837","kind":"references","source":"IETF/RFC-6833/RFC-6833.txt"},{"from":"IETF RFC 6835","to":"IETF RFC 6837","kind":"references","source":"IETF/RFC-6835/RFC-6835.txt"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"IETF RFC 6838","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 6838","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 6838","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 6839","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6901","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 6920","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 7030","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7578","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7578/RFC-7578.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8081","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8081/RFC-8081.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 6838","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 6838","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 6838","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 6838","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 7033","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-7033/RFC-7033.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 6839","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 684","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 6840","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6840","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6840","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6840","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6841","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6841","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 6841","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6841","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 6843","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 6844","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 6844","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6846","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6881","to":"IETF RFC 6849","kind":"references","source":"IETF/RFC-6881/RFC-6881.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6849","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7162","to":"IETF RFC 6851","kind":"references","source":"IETF/RFC-7162/RFC-7162.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 6851","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6851","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 7031","to":"IETF RFC 6853","kind":"references","source":"IETF/RFC-7031/RFC-7031.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6854","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6856","to":"IETF RFC 6855","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6855","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 6855","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 6855","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 6857","to":"IETF RFC 6856","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 6856","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 6857","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 6857","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 6855","to":"IETF RFC 6858","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 686","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 686","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 691","to":"IETF RFC 686","kind":"references","source":"IETF/RFC-691/RFC-691.txt"},{"from":"IETF RFC 959","to":"IETF RFC 686","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 6863","to":"IETF RFC 6862","kind":"references","source":"IETF/RFC-6863/RFC-6863.txt"},{"from":"IETF RFC 6952","to":"IETF RFC 6863","kind":"references","source":"IETF/RFC-6952/RFC-6952.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6864","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 6864","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6864","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6864","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 6879","to":"IETF RFC 6866","kind":"references","source":"IETF/RFC-6879/RFC-6879.txt"},{"from":"IETF RFC 7095","to":"IETF RFC 6868","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 687","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 6871","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6871","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 6873","to":"IETF RFC 6872","kind":"references","source":"IETF/RFC-6873/RFC-6873.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 6872","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 6873","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 6874","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 6876","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 6876","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 6876","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 7335","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-7335/RFC-7335.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6877","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 6866","to":"IETF RFC 6879","kind":"references","source":"IETF/RFC-6866/RFC-6866.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6879","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7406","to":"IETF RFC 6881","kind":"references","source":"IETF/RFC-7406/RFC-7406.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6883","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 6943","to":"IETF RFC 6885","kind":"references","source":"IETF/RFC-6943/RFC-6943.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 6885","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 6885","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 6885","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6886","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6886","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-6886/RFC-6886.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6970","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-6970/RFC-6970.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6887","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6947","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-6947/RFC-6947.txt"},{"from":"IETF RFC 7362","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6888","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 7050","to":"IETF RFC 6890","kind":"references","source":"IETF/RFC-7050/RFC-7050.txt"},{"from":"IETF RFC 7291","to":"IETF RFC 6890","kind":"references","source":"IETF/RFC-7291/RFC-7291.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 6890","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 6890","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 6890","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 6895","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-6895/RFC-6895.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 6975","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-6975/RFC-6975.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7830","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7830/RFC-7830.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 6891","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6894","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 7553","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-7553/RFC-7553.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 6895","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6897","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 6902","to":"IETF RFC 6901","kind":"references","source":"IETF/RFC-6902/RFC-6902.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 6901","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 6901","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 6901","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 6901","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 6901","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF RFC 7644","to":"IETF RFC 6902","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 6902","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 7089","to":"IETF RFC 6903","kind":"references","source":"IETF/RFC-7089/RFC-7089.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 6904","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 6904","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 6904","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 6904","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 6904","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 6905","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 6905","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 6905","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 6905","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6908","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 739","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 743","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-743/RFC-743.txt"},{"from":"IETF RFC 750","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 775","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-775/RFC-775.txt"},{"from":"IETF RFC 776","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 959","to":"IETF RFC 691","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 6910","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 7542","to":"IETF RFC 6912","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 6916","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6920","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 6920","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 6920","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 6921","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 6925","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6925","to":"IETF RFC 6926","kind":"references","source":"IETF/RFC-6925/RFC-6925.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 6926","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 6926","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 6927","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 6927","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 6928","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 6929","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 6931","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"IETF RFC 7522","to":"IETF RFC 6931","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 6933","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 6933","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 6933","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 6933","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 6933","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 6935","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 6935","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-6935/RFC-6935.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 6936","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6937","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 6937","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 6937","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 6939","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 6939","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7087","to":"IETF RFC 6941","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7226","to":"IETF RFC 6941","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6941","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7320","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7320/RFC-7320.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7564","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 6943","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 7739","to":"IETF RFC 6946","kind":"references","source":"IETF/RFC-7739/RFC-7739.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 6946","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 6946","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 6946","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 6947","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 6949","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 6950","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6950","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 6951","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 6952","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 6952","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 6989","to":"IETF RFC 6954","kind":"references","source":"IETF/RFC-6989/RFC-6989.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 6957","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 6958","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 6958","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 7039","to":"IETF RFC 6959","kind":"references","source":"IETF/RFC-7039/RFC-7039.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-2 V2.6.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"IETF RFC 6960","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 6961","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 6960","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7633","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-7633/RFC-7633.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6961","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6962","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6963","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 697","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 775","to":"IETF RFC 697","kind":"references","source":"IETF/RFC-775/RFC-775.txt"},{"from":"IETF RFC 959","to":"IETF RFC 697","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 6970","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 7258","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7258/RFC-7258.txt"},{"from":"IETF RFC 7398","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7521","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7536","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7536/RFC-7536.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 6973","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 6975","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 6975","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 6977","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8937","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 6979","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 0698","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-0698/RFC-0698.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 900","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 698","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7066","to":"IETF RFC 6980","kind":"references","source":"IETF/RFC-7066/RFC-7066.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 6980","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 6981","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 6982","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 6983","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 6983","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7312","to":"IETF RFC 6985","kind":"references","source":"IETF/RFC-7312/RFC-7312.txt"},{"from":"IETF RFC 7770","to":"IETF RFC 6987","kind":"references","source":"IETF/RFC-7770/RFC-7770.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 6988","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 6988","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 6988","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 6988","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 6954","to":"IETF RFC 6989","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 6989","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 6989","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 6989","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 6991","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 6994","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 6994","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 6994","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 6998","to":"IETF RFC 6997","kind":"references","source":"IETF/RFC-6998/RFC-6998.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 6997","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 6997","to":"IETF RFC 6998","kind":"references","source":"IETF/RFC-6997/RFC-6997.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 700","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 700","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 800","to":"IETF RFC 700","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7208","to":"IETF RFC 7001","kind":"references","source":"IETF/RFC-7208/RFC-7208.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 7001","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 7002","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 7002","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 7002","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7002","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 7002","to":"IETF RFC 7003","kind":"references","source":"IETF/RFC-7002/RFC-7002.txt"},{"from":"IETF RFC 7004","to":"IETF RFC 7003","kind":"references","source":"IETF/RFC-7004/RFC-7004.txt"},{"from":"IETF RFC 7097","to":"IETF RFC 7003","kind":"references","source":"IETF/RFC-7097/RFC-7097.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7003","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 7003","to":"IETF RFC 7004","kind":"references","source":"IETF/RFC-7003/RFC-7003.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7006","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7007","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 7009","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7009","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7009","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7496","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7496/RFC-7496.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 7011","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 6988","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7013","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7013/RFC-7013.txt"},{"from":"IETF RFC 7014","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7014/RFC-7014.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7012","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7012","to":"IETF RFC 7013","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 7013","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7015","to":"IETF RFC 7014","kind":"references","source":"IETF/RFC-7015/RFC-7015.txt"},{"from":"IETF RFC 7326","to":"IETF RFC 7015","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 7016","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 702","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 7020","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7022","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 7023","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7023","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 7027","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 7029","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 703","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7114","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-7114/RFC-7114.txt"},{"from":"IETF RFC 7170","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7030","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 7031","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7033","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 7033","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7033","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 7039","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7039","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7039","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 7040","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7043","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7043/RFC-7043.txt"},{"from":"IETF RFC 7136","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7136/RFC-7136.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 7042","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 7042","to":"IETF RFC 7043","kind":"references","source":"IETF/RFC-7042/RFC-7042.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 7043","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 7112","to":"IETF RFC 7045","kind":"references","source":"IETF/RFC-7112/RFC-7112.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 7045","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 7045","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 7045","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7045","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 7049","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 8075","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8746","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8943","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8943/RFC-8943.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 7049","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 7049","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 8305","to":"IETF RFC 7050","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 7050","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7050","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7050","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 7053","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 7761","to":"IETF RFC 7063","kind":"references","source":"IETF/RFC-7761/RFC-7761.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 7064","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7064","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 7350","to":"IETF RFC 7065","kind":"references","source":"IETF/RFC-7350/RFC-7350.txt"},{"from":"IETF RFC 7006","to":"IETF RFC 7066","kind":"references","source":"IETF/RFC-7006/RFC-7006.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7067","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7067","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 739","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 800","to":"IETF RFC 707","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 7070","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 7070","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 7070","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7072","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-7072/RFC-7072.txt"},{"from":"IETF RFC 7073","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-7073/RFC-7073.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7071","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 7072","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 7072","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7070","to":"IETF RFC 7073","kind":"references","source":"IETF/RFC-7070/RFC-7070.txt"},{"from":"IETF RFC 7071","to":"IETF RFC 7073","kind":"references","source":"IETF/RFC-7071/RFC-7071.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7074","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7157","to":"IETF RFC 7078","kind":"references","source":"IETF/RFC-7157/RFC-7157.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 7079","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7079","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 739","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 800","to":"IETF RFC 708","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7084","to":"IETF RFC 7083","kind":"references","source":"IETF/RFC-7084/RFC-7084.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 7083","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 7083","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7083","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 7084","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7084","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 7084","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7084","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 7087","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 7087","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 7088","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 7089","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 7092","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 7092","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 7092","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7094","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 7094","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7095","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 7095","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7095","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7097","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7098","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 7102","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7102","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 7104","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 7104","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7104","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7104","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7107","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7111","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 7113","to":"IETF RFC 7112","kind":"references","source":"IETF/RFC-7113/RFC-7113.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 7112","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7112","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 7113","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 7113","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 7114","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 7209","to":"IETF RFC 7117","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 7117","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 7117","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7117","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 7118","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7153","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7153/RFC-7153.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 7120","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 7127","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7129","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 7129","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7129","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 7129","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7129","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 7049","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 722","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-722/RFC-722.txt"},{"from":"IETF RFC 753","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 767","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 713","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7132","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 7217","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-7217/RFC-7217.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7136","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 7141","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 7141","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 7141","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 7141","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7144","to":"IETF RFC 7143","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 7143","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 7143","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7143","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7143","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 7144","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 7144","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 7145","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7146","to":"IETF RFC 7145","kind":"references","source":"IETF/RFC-7146/RFC-7146.txt"},{"from":"IETF RFC 7143","to":"IETF RFC 7146","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 7146","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7146","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 7153","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7156","to":"IETF RFC 7155","kind":"references","source":"IETF/RFC-7156/RFC-7156.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7156","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 7157","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7157","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7396","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7396/RFC-7396.txt"},{"from":"IETF RFC 7464","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7493","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7159","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 7159","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 7656","to":"IETF RFC 7160","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 7160","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7160","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7160","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7160","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7162","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 7164","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 7164","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7164","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7171","to":"IETF RFC 7170","kind":"references","source":"IETF/RFC-7171/RFC-7171.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 7170","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7170","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7170","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 7170","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 7171","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 7171","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7172","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 7173","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7173","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 7174","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7174","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 7174","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 7175","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7175","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7175","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7175","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7356","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7176","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7174","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7177","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7175","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7179","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7179/RFC-7179.txt"},{"from":"IETF RFC 7180","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7178","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7179","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 7179","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7179","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7179","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7172","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7176","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7180","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7182","to":"IETF RFC 7181","kind":"references","source":"IETF/RFC-7182/RFC-7182.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 7181","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 7181","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 7182","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 7183","to":"IETF RFC 7182","kind":"references","source":"IETF/RFC-7183/RFC-7183.txt"},{"from":"IETF RFC 7181","to":"IETF RFC 7183","kind":"references","source":"IETF/RFC-7181/RFC-7181.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7195","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7195","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 7198","to":"IETF RFC 7197","kind":"references","source":"IETF/RFC-7198/RFC-7198.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 7197","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7197","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7197","to":"IETF RFC 7198","kind":"references","source":"IETF/RFC-7197/RFC-7197.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 7198","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 7201","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 7201","to":"IETF RFC 7202","kind":"references","source":"IETF/RFC-7201/RFC-7201.txt"},{"from":"IETF RFC 7587","to":"IETF RFC 7202","kind":"references","source":"IETF/RFC-7587/RFC-7587.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 7203","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 7203","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 7203","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 7489","to":"IETF RFC 7208","kind":"references","source":"IETF/RFC-7489/RFC-7489.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7208","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7208","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 7208","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 7432","to":"IETF RFC 7209","kind":"references","source":"IETF/RFC-7432/RFC-7432.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 721","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7217","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 7218","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 7218","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 7218","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 7218","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7218","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 2720","to":"IETF RFC 722","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 753","to":"IETF RFC 722","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 722","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 7224","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 7223","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 7223","to":"IETF RFC 7224","kind":"references","source":"IETF/RFC-7223/RFC-7223.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 7224","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 7224","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 7226","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 7550","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-7550/RFC-7550.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 7227","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7397","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7397/RFC-7397.txt"},{"from":"IETF RFC 7400","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7400/RFC-7400.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7228","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 722","to":"IETF RFC 723","kind":"references","source":"IETF/RFC-722/RFC-722.txt"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 7230","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 7230","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"IETF RFC 7231","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7301","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7337","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7337/RFC-7337.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7541","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8307","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8307/RFC-8307.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 7230","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7240","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7240/RFC-7240.txt"},{"from":"IETF RFC 7285","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7285/RFC-7285.txt"},{"from":"IETF RFC 7303","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8297","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8297/RFC-8297.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7231","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 7231","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 7230","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7239","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7239/RFC-7239.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8246","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8246/RFC-8246.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7232","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7233","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7232","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7232/RFC-7232.txt"},{"from":"IETF RFC 7233","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7233/RFC-7233.txt"},{"from":"IETF RFC 7235","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7235/RFC-7235.txt"},{"from":"IETF RFC 7238","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7238/RFC-7238.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8246","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8246/RFC-8246.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7234","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 7235","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 422 V1.1.1","to":"IETF RFC 7235","kind":"references","source":"ETSI/EN-319-422-V1.1.1/EN-319-422-V1.1.1.pdf"},{"from":"IETF RFC 7230","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7234","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7234/RFC-7234.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7486","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7486/RFC-7486.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7615","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7235","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 7238","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 7538","to":"IETF RFC 7238","kind":"references","source":"IETF/RFC-7538/RFC-7538.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7239","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 7239","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 7239","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 7239","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 7239","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7240","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 7247","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 7247","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 7247","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 7250","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 7251","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7251","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7250","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7368","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7368/RFC-7368.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7641","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7641/RFC-7641.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8307","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8307/RFC-8307.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 7252","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 7255","to":"IETF RFC 7254","kind":"references","source":"IETF/RFC-7255/RFC-7255.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7254","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 7254","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7254","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 7254","to":"IETF RFC 7255","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 7255","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 7340","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7340/RFC-7340.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7435","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7435/RFC-7435.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7536","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7536/RFC-7536.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7624","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7624/RFC-7624.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7258","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 731","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-731/RFC-731.txt"},{"from":"IETF RFC 732","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-732/RFC-732.txt"},{"from":"IETF RFC 900","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 726","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 7262","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7266","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 727","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 7272","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7272","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7272","to":"IETF RFC 7273","kind":"references","source":"IETF/RFC-7272/RFC-7272.txt"},{"from":"IETF RFC 7656","to":"IETF RFC 7273","kind":"references","source":"IETF/RFC-7656/RFC-7656.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7273","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7274","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 7276","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7277","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 7277","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7278","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7278","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 731","to":"IETF RFC 728","kind":"references","source":"IETF/RFC-731/RFC-731.txt"},{"from":"IETF RFC 732","to":"IETF RFC 728","kind":"references","source":"IETF/RFC-732/RFC-732.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7282","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 7283","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7283","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 7285","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7754","to":"IETF RFC 7288","kind":"references","source":"IETF/RFC-7754/RFC-7754.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7288","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7289","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 729","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 731","to":"IETF RFC 729","kind":"references","source":"IETF/RFC-731/RFC-731.txt"},{"from":"IETF RFC 732","to":"IETF RFC 729","kind":"references","source":"IETF/RFC-732/RFC-732.txt"},{"from":"IETF RFC 800","to":"IETF RFC 729","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 7290","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7488","to":"IETF RFC 7291","kind":"references","source":"IETF/RFC-7488/RFC-7488.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 7292","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 7292","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7539","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-7539/RFC-7539.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 7296","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 7301","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 7303","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7807","to":"IETF RFC 7303","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7303","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7303","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 7303","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 731","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 800","to":"IETF RFC 731","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 7312","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 7312","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 7312","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 7319","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1043","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-1043/RFC-1043.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 800","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 900","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 732","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7320","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7320","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7320","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7320","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 7320","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7321","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 7749","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7749/RFC-7749.txt"},{"from":"IETF RFC 7841","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7841/RFC-7841.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7993","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7993/RFC-7993.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 7322","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 7323","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 7323","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7323","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 7323","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7323","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 7324","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 7325","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 7326","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 7326","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 7326","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2234","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-2234/RFC-2234.txt"},{"from":"IETF RFC 2235","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-2235/RFC-2235.txt"},{"from":"IETF RFC 4234","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-4234/RFC-4234.txt"},{"from":"IETF RFC 5234","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-5234/RFC-5234.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 753","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 759","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 767","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 772","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-772/RFC-772.txt"},{"from":"IETF RFC 780","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-780/RFC-780.txt"},{"from":"IETF RFC 788","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-788/RFC-788.txt"},{"from":"IETF RFC 805","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-805/RFC-805.txt"},{"from":"IETF RFC 806","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-806/RFC-806.txt"},{"from":"IETF RFC 840","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 841","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-841/RFC-841.txt"},{"from":"IETF RFC 880","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 733","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 7335","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7335","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 7337","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-7337/RFC-7337.txt"},{"from":"IETF RFC 7736","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-7736/RFC-7736.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7336","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 7336","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-7336/RFC-7336.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7337","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 736","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-736/RFC-736.txt"},{"from":"IETF RFC 739","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 746","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-746/RFC-746.txt"},{"from":"IETF RFC 747","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-747/RFC-747.txt"},{"from":"IETF RFC 749","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-749/RFC-749.txt"},{"from":"IETF RFC 750","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 779","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-779/RFC-779.txt"},{"from":"IETF RFC 790","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 800","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 820","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 734","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7375","to":"IETF RFC 7340","kind":"references","source":"IETF/RFC-7375/RFC-7375.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 7340","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7340","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7340","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 7341","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 7341","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 7341","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7341","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7344","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8078","to":"IETF RFC 7344","kind":"references","source":"IETF/RFC-8078/RFC-8078.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7344","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 7344","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7344","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 7345","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 7345","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 7390","to":"IETF RFC 7346","kind":"references","source":"IETF/RFC-7390/RFC-7390.txt"},{"from":"IETF RFC 7424","to":"IETF RFC 7348","kind":"references","source":"IETF/RFC-7424/RFC-7424.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7348","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7348","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7348","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 7348","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 800","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 900","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 735","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7675","to":"IETF RFC 7350","kind":"references","source":"IETF/RFC-7675/RFC-7675.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7350","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 7350","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 7357","to":"IETF RFC 7356","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7356","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7356","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7357","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7357","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 749","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-749/RFC-749.txt"},{"from":"IETF RFC 800","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 900","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 736","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 7362","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7365","to":"IETF RFC 7364","kind":"references","source":"IETF/RFC-7365/RFC-7365.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 7364","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7364","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7364","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 7364","to":"IETF RFC 7365","kind":"references","source":"IETF/RFC-7364/RFC-7364.txt"},{"from":"IETF RFC 7637","to":"IETF RFC 7365","kind":"references","source":"IETF/RFC-7637/RFC-7637.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7365","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7365","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 7365","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 7457","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-7457/RFC-7457.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7366","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 7421","to":"IETF RFC 7368","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 7368","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7368","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 737","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 737","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 959","to":"IETF RFC 737","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 7375","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7375","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 0739","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-0739/RFC-0739.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 739","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-739/RFC-739.txt"},{"from":"IETF RFC 750","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 738","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 7384","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 7384","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 7384","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 7388","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 2204","to":"IETF RFC 739","kind":"references","source":"IETF/RFC-2204/RFC-2204.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 739","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7390","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 7390","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7390","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7396","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 7452","to":"IETF RFC 7397","kind":"references","source":"IETF/RFC-7452/RFC-7452.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7397","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 7398","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 750","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 765","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-765/RFC-765.txt"},{"from":"IETF RFC 776","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 959","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 960","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 740","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7428","to":"IETF RFC 7400","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7400","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 7405","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 7406","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7406","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 7407","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 7407","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 750","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 767","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 776","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 870","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 900","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 741","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7413","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 7414","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 7414","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 7414","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1135","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1135/RFC-1135.txt"},{"from":"IETF RFC 1194","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1194/RFC-1194.txt"},{"from":"IETF RFC 1196","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1196/RFC-1196.txt"},{"from":"IETF RFC 1288","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-1288/RFC-1288.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 750","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-750/RFC-750.txt"},{"from":"IETF RFC 758","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-758/RFC-758.txt"},{"from":"IETF RFC 762","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-762/RFC-762.txt"},{"from":"IETF RFC 776","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 779","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-779/RFC-779.txt"},{"from":"IETF RFC 790","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 812","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-812/RFC-812.txt"},{"from":"IETF RFC 820","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 900","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 742","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7421","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7421","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7421","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7421","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7424","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 7428","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 743","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 743","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 959","to":"IETF RFC 743","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 7606","to":"IETF RFC 7432","kind":"references","source":"IETF/RFC-7606/RFC-7606.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7619","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7619/RFC-7619.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7435","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7450","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7452","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7452","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7452","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7452","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 7456","to":"IETF RFC 7455","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 7455","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7455","to":"IETF RFC 7456","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7457","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 747","to":"IETF RFC 746","kind":"references","source":"IETF/RFC-747/RFC-747.txt"},{"from":"IETF RFC 7461","to":"IETF RFC 7460","kind":"references","source":"IETF/RFC-7461/RFC-7461.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7460","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7460","to":"IETF RFC 7461","kind":"references","source":"IETF/RFC-7460/RFC-7460.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7461","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 7463","to":"IETF RFC 7462","kind":"references","source":"IETF/RFC-7463/RFC-7463.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7462","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 7462","to":"IETF RFC 7463","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 7464","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 7464","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 7464","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 7464","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7568","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-7568/RFC-7568.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7465","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 7469","to":"IETF RFC 7468","kind":"references","source":"IETF/RFC-7469/RFC-7469.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 7468","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7468","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 7468","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7469","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 749","to":"IETF RFC 747","kind":"references","source":"IETF/RFC-749/RFC-749.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 7478","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7478","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7480","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7481","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7483","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7482","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7481","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7481/RFC-7481.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7484","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7484/RFC-7484.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7483","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 7480","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-7480/RFC-7480.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7485","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-7485/RFC-7485.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7484","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 7485","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7485","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7485","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7486","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7486","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7488","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7489","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7489","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7489","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 7489","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 749","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 7493","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 7495","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 7495","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 7496","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 7496","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 7496","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 7665","to":"IETF RFC 7498","kind":"references","source":"IETF/RFC-7665/RFC-7665.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 7498","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7498","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 753","to":"IETF RFC 750","kind":"references","source":"IETF/RFC-753/RFC-753.txt"},{"from":"IETF RFC 7525","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-7525/RFC-7525.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7507","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 751","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 751","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7510","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 7610","to":"IETF RFC 7513","kind":"references","source":"IETF/RFC-7610/RFC-7610.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7513","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"legal:2025-2531","to":"IETF RFC 7515","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2026-1731","to":"IETF RFC 7515","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2026-248","to":"IETF RFC 7515","kind":"cites","source":"implementing-acts/2026-248/2026-248.md"},{"from":"ARF TS02 V1.0.1","to":"IETF RFC 7515","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"IETF RFC 7515","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"IETF RFC 7516","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 7515","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 7515","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"IETF RFC 7515","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"ARF TS10 V1.2","to":"IETF RFC 7516","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 7516","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 7516","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"IETF RFC 7515","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7516","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 7516","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7517","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7517","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 7517","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"IETF RFC 7515","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7518","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7517","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 7517","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"IETF RFC 7517","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"ARF TS10 V1.2","to":"IETF RFC 7518","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7518","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"IETF RFC 7518","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"IETF RFC 7515","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7519","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7638","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7638/RFC-7638.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7518","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"legal:2025-848","to":"IETF RFC 7519","kind":"cites","source":"implementing-acts/2025-848/2025-848.md"},{"from":"legal:2026-1731","to":"IETF RFC 7519","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS03 V1.5.2","to":"IETF RFC 7519","kind":"references","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 7519","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7519","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 7515","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7797","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 7519","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 7519","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"IETF RFC 7519","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 7519","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7521","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 7522","to":"IETF RFC 7521","kind":"references","source":"IETF/RFC-7522/RFC-7522.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 7521","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7521","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 7521","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 7521","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"ETSI EN 319 522-3 V1.2.1","to":"IETF RFC 7522","kind":"references","source":"ETSI/EN-319-522-3-V1.2.1/EN-319-522-3-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7522","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 7521","to":"IETF RFC 7522","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7523","to":"IETF RFC 7522","kind":"references","source":"IETF/RFC-7523/RFC-7523.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7522","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7523","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7523","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 7521","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-7521/RFC-7521.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 7523","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 7515","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 7592","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 7636","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7636/RFC-7636.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7653","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7653/RFC-7653.txt"},{"from":"IETF RFC 7662","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7662/RFC-7662.txt"},{"from":"IETF RFC 7696","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7696/RFC-7696.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 7830","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7830/RFC-7830.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7525","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 753","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 800","to":"IETF RFC 753","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 806","to":"IETF RFC 753","kind":"references","source":"IETF/RFC-806/RFC-806.txt"},{"from":"IETF RFC 840","to":"IETF RFC 753","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 841","to":"IETF RFC 753","kind":"references","source":"IETF/RFC-841/RFC-841.txt"},{"from":"IETF RFC 7531","to":"IETF RFC 7530","kind":"references","source":"IETF/RFC-7531/RFC-7531.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 7530","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 7530","to":"IETF RFC 7531","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7594","to":"IETF RFC 7536","kind":"references","source":"IETF/RFC-7594/RFC-7594.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7538","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7538","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7538","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 7539","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7539","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7539","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 7539","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 759","to":"IETF RFC 754","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7540","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 7541","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-7541/RFC-7541.txt"},{"from":"IETF RFC 7694","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-7694/RFC-7694.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7838","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-7838/RFC-7838.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8297","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8297/RFC-8297.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 7540","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 7541","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 7593","to":"IETF RFC 7542","kind":"references","source":"IETF/RFC-7593/RFC-7593.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 7542","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7542","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7542","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 7548","to":"IETF RFC 7547","kind":"references","source":"IETF/RFC-7548/RFC-7548.txt"},{"from":"IETF RFC 7547","to":"IETF RFC 7548","kind":"references","source":"IETF/RFC-7547/RFC-7547.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 7548","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 7550","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7550","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7553","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 7553","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 7713","to":"IETF RFC 7560","kind":"references","source":"IETF/RFC-7713/RFC-7713.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7560","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7562","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 7613","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7790","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-7790/RFC-7790.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 7564","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 7566","to":"IETF RFC 7565","kind":"references","source":"IETF/RFC-7566/RFC-7566.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7566","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8034","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8034/RFC-8034.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 7567","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 7627","to":"IETF RFC 7568","kind":"references","source":"IETF/RFC-7627/RFC-7627.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7568","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7568","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7568","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7568","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 7573","to":"IETF RFC 7572","kind":"references","source":"IETF/RFC-7573/RFC-7573.txt"},{"from":"IETF RFC 7590","to":"IETF RFC 7572","kind":"references","source":"IETF/RFC-7590/RFC-7590.txt"},{"from":"IETF RFC 7572","to":"IETF RFC 7573","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 7578","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7578","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 0758","to":"IETF RFC 758","kind":"references","source":"IETF/RFC-0758/RFC-0758.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 758","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 758","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 7587","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7587","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 7587","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 7588","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7588","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7589","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7589","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7589","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 767","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-767/RFC-767.txt"},{"from":"IETF RFC 776","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 800","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 820","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 870","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 759","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 7590","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7590","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 7590","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7590","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"ARF TS11 V1.0.1","to":"IETF RFC 7591","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7591","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7591","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 7592","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-7592/RFC-7592.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7591","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 7591","to":"IETF RFC 7592","kind":"references","source":"IETF/RFC-7591/RFC-7591.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7593","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 7594","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 7594","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"IETF RFC 7594","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7595","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 7596","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 7596","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7596","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7753","to":"IETF RFC 7596","kind":"references","source":"IETF/RFC-7753/RFC-7753.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7596","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7597","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 7596","to":"IETF RFC 7598","kind":"references","source":"IETF/RFC-7596/RFC-7596.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 7598","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 7598","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7618","to":"IETF RFC 7598","kind":"references","source":"IETF/RFC-7618/RFC-7618.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7598","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7598","to":"IETF RFC 7599","kind":"references","source":"IETF/RFC-7598/RFC-7598.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7599","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 7599","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 0768","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-0768/RFC-0768.txt"},{"from":"IETF RFC 0791","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-0791/RFC-0791.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 761","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-761/RFC-761.txt"},{"from":"IETF RFC 768","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-768/RFC-768.txt"},{"from":"IETF RFC 776","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 777","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-777/RFC-777.txt"},{"from":"IETF RFC 791","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-791/RFC-791.txt"},{"from":"IETF RFC 800","to":"IETF RFC 760","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 7604","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7605","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7605","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 7606","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 0768","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-0768/RFC-0768.txt"},{"from":"IETF RFC 0793","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-0793/RFC-0793.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 768","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-768/RFC-768.txt"},{"from":"IETF RFC 776","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 780","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-780/RFC-780.txt"},{"from":"IETF RFC 793","to":"IETF RFC 761","kind":"references","source":"IETF/RFC-793/RFC-793.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7610","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7610","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7610","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7613","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 7616","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7615","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7616","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 7615","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-7615/RFC-7615.txt"},{"from":"IETF RFC 7617","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7616","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7617","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 7616","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7617","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 7618","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7619","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 0768","to":"IETF RFC 762","kind":"references","source":"IETF/RFC-0768/RFC-0768.txt"},{"from":"IETF RFC 759","to":"IETF RFC 762","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 760","to":"IETF RFC 762","kind":"references","source":"IETF/RFC-760/RFC-760.txt"},{"from":"IETF RFC 768","to":"IETF RFC 762","kind":"references","source":"IETF/RFC-768/RFC-768.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 7622","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7622","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 7626","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-7626/RFC-7626.txt"},{"from":"IETF RFC 7687","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-7687/RFC-7687.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7624","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 7816","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-7816/RFC-7816.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7626","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 7677","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-7677/RFC-7677.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7627","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 7632","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 7632","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 7633","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7633","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7636","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7636","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 8252","to":"IETF RFC 7636","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7636","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7636","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7636","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 7636","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7637","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 7637","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7637","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 7637","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 7800","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7638","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1350","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-1350/RFC-1350.txt"},{"from":"IETF RFC 776","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 783","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-783/RFC-783.txt"},{"from":"IETF RFC 790","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 801","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 820","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 764","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 7641","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 7644","to":"IETF RFC 7643","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7643","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 7643","to":"IETF RFC 7644","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7644","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 7644","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 775","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-775/RFC-775.txt"},{"from":"IETF RFC 776","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 790","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 801","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 820","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 887","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 900","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 959","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 960","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 765","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 7653","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 7653","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7667","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-7667/RFC-7667.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7656","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7657","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7657","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7657","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7657","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7657","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 7658","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 7659","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7659","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 7661","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 7662","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 7662","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 8414","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 7662","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 7665","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7665","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 7667","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 7667","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7667","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 7667","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7667","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7669","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 7669","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 759","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-759/RFC-759.txt"},{"from":"IETF RFC 840","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 767","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7671","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7673","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-7673/RFC-7673.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7672","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 7671","to":"IETF RFC 7673","kind":"references","source":"IETF/RFC-7671/RFC-7671.txt"},{"from":"IETF RFC 7672","to":"IETF RFC 7673","kind":"references","source":"IETF/RFC-7672/RFC-7672.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7673","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 7673","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7673","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7675","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 7675","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 7675","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 7675","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 7676","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 7676","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7676","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 7804","to":"IETF RFC 7677","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7677","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 7679","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 7679","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 0768","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0768/RFC-0768.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1067","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1067/RFC-1067.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1085","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1098","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1098/RFC-1098.txt"},{"from":"IETF RFC 1157","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1157/RFC-1157.txt"},{"from":"IETF RFC 1161","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1161/RFC-1161.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1234","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1234/RFC-1234.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1240","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1283","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1283/RFC-1283.txt"},{"from":"IETF RFC 1298","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1298/RFC-1298.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1350","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1350/RFC-1350.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1418","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1418/RFC-1418.txt"},{"from":"IETF RFC 1420","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1420/RFC-1420.txt"},{"from":"IETF RFC 1448","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1448/RFC-1448.txt"},{"from":"IETF RFC 1449","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1449/RFC-1449.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1769","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1769/RFC-1769.txt"},{"from":"IETF RFC 1770","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1770/RFC-1770.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1905","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1905/RFC-1905.txt"},{"from":"IETF RFC 1906","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1906/RFC-1906.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1986","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-1986/RFC-1986.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2013","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2013/RFC-2013.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2058","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2059","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2059/RFC-2059.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2107","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2107/RFC-2107.txt"},{"from":"IETF RFC 2138","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2139","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2139/RFC-2139.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2865","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3096","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3096/RFC-3096.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3261","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3416","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3416/RFC-3416.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3450","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3450/RFC-3450.txt"},{"from":"IETF RFC 3451","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3451/RFC-3451.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3576","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3576/RFC-3576.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3948","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3948/RFC-3948.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 3985","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-3985/RFC-3985.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4113","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4113/RFC-4113.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4636","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4636/RFC-4636.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4944","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4944/RFC-4944.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5097","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5097/RFC-5097.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5486","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5505","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5505/RFC-5505.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5651","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5651/RFC-5651.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5775","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5775/RFC-5775.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 6012","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6012/RFC-6012.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6064","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6064/RFC-6064.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6282","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6282/RFC-6282.txt"},{"from":"IETF RFC 6285","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6285/RFC-6285.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6773","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6773/RFC-6773.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7388","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7388/RFC-7388.txt"},{"from":"IETF RFC 7510","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7510/RFC-7510.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 776","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 783","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-783/RFC-783.txt"},{"from":"IETF RFC 790","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 820","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 840","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 870","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 882","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 887","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 900","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 901","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 906","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-906/RFC-906.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 923","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 960","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 768","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 7680","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 7680","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7685","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7687","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 769","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 798","to":"IETF RFC 769","kind":"references","source":"IETF/RFC-798/RFC-798.txt"},{"from":"IETF RFC 980","to":"IETF RFC 769","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 769","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9106","to":"IETF RFC 7693","kind":"references","source":"IETF/RFC-9106/RFC-9106.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 7693","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7694","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 7696","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 7700","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 7701","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 7706","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 7721","to":"IETF RFC 7707","kind":"references","source":"IETF/RFC-7721/RFC-7721.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7707","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7707","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7707","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 7712","to":"IETF RFC 7711","kind":"references","source":"IETF/RFC-7712/RFC-7712.txt"},{"from":"IETF RFC 7817","to":"IETF RFC 7711","kind":"references","source":"IETF/RFC-7817/RFC-7817.txt"},{"from":"IETF RFC 7711","to":"IETF RFC 7712","kind":"references","source":"IETF/RFC-7711/RFC-7711.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7712","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7713","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7871","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-7871/RFC-7871.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7719","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 776","to":"IETF RFC 772","kind":"references","source":"IETF/RFC-776/RFC-776.txt"},{"from":"IETF RFC 780","to":"IETF RFC 772","kind":"references","source":"IETF/RFC-780/RFC-780.txt"},{"from":"IETF RFC 7707","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-7707/RFC-7707.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7721","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 7819","to":"IETF RFC 7724","kind":"references","source":"IETF/RFC-7819/RFC-7819.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7728","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7736","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7736","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7736","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7736","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7736","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 7739","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7739","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7739","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 7742","to":"IETF RFC 7741","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 7741","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7741","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7742","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7742","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8032","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8032/RFC-8032.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8411","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 7748","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7749","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7749","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 7749","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 7749","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 840","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 775","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 7752","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 7857","to":"IETF RFC 7753","kind":"references","source":"IETF/RFC-7857/RFC-7857.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7753","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7754","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7754","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7754","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 7757","to":"IETF RFC 7755","kind":"references","source":"IETF/RFC-7757/RFC-7757.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 7756","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 7757","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 7757","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7757","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 776","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 776","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 7761","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 7765","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 7828","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-7828/RFC-7828.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7766","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 778","to":"IETF RFC 777","kind":"references","source":"IETF/RFC-778/RFC-778.txt"},{"from":"IETF RFC 7752","to":"IETF RFC 7770","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 0792","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-0792/RFC-0792.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 777","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-777/RFC-777.txt"},{"from":"IETF RFC 792","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-792/RFC-792.txt"},{"from":"IETF RFC 840","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 778","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7780","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 779","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 7790","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7793","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7793","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 7797","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"IETF RFC 8322","to":"IETF RFC 7797","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7797","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7799","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 788","to":"IETF RFC 780","kind":"references","source":"IETF/RFC-788/RFC-788.txt"},{"from":"IETF RFC 790","to":"IETF RFC 780","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 801","to":"IETF RFC 780","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"legal:2026-1731","to":"IETF RFC 7800","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 7800","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"IETF RFC 8705","to":"IETF RFC 7800","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 7800","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7800","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 7800","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"IETF RFC 7800","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7804","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 7806","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 7806","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7807","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7807","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 7807","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7807","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 7807","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 7816","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 7816","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7816","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7816","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 7817","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7817","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 7819","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7819","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 7820","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 7822","to":"IETF RFC 7821","kind":"references","source":"IETF/RFC-7822/RFC-7822.txt"},{"from":"IETF RFC 7821","to":"IETF RFC 7822","kind":"references","source":"IETF/RFC-7821/RFC-7821.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 7822","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 7844","to":"IETF RFC 7824","kind":"references","source":"IETF/RFC-7844/RFC-7844.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7824","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7824","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7825","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 7825","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 7826","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7826","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7826","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7826","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7828","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1350","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1350/RFC-1350.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 790","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 820","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 879","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-879/RFC-879.txt"},{"from":"IETF RFC 880","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 887","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 900","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 906","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-906/RFC-906.txt"},{"from":"IETF RFC 923","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 960","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 783","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7858","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-7858/RFC-7858.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7830","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7838","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7839","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 7825","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7825/RFC-7825.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7839","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7872","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7872/RFC-7872.txt"},{"from":"IETF RFC 7873","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7873/RFC-7873.txt"},{"from":"IETF RFC 7893","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 7895","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7895/RFC-7895.txt"},{"from":"IETF RFC 7905","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7905/RFC-7905.txt"},{"from":"IETF RFC 7914","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7914/RFC-7914.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 7924","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7924/RFC-7924.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 7932","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7932/RFC-7932.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7937","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7937/RFC-7937.txt"},{"from":"IETF RFC 7941","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7942","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7942/RFC-7942.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7959","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7959/RFC-7959.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 7967","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7967/RFC-7967.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 7970","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7975","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7975/RFC-7975.txt"},{"from":"IETF RFC 7977","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7977/RFC-7977.txt"},{"from":"IETF RFC 7983","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7983/RFC-7983.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7993","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7993/RFC-7993.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 8017","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8018","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8020","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8020/RFC-8020.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8027","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8027/RFC-8027.txt"},{"from":"IETF RFC 8030","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8030/RFC-8030.txt"},{"from":"IETF RFC 8032","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8032/RFC-8032.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8034","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8034/RFC-8034.txt"},{"from":"IETF RFC 8035","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8035/RFC-8035.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8053","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8053/RFC-8053.txt"},{"from":"IETF RFC 8054","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8054/RFC-8054.txt"},{"from":"IETF RFC 8055","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8055/RFC-8055.txt"},{"from":"IETF RFC 8064","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 8073","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8073/RFC-8073.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8078","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8078/RFC-8078.txt"},{"from":"IETF RFC 8081","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8081/RFC-8081.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8089","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8091","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8091/RFC-8091.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 8108","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8108/RFC-8108.txt"},{"from":"IETF RFC 8109","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8109/RFC-8109.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8141","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8145","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8145/RFC-8145.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8164","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8164/RFC-8164.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8174","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8174/RFC-8174.txt"},{"from":"IETF RFC 8179","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8179/RFC-8179.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8235","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8235/RFC-8235.txt"},{"from":"IETF RFC 8240","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8240/RFC-8240.txt"},{"from":"IETF RFC 8246","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8246/RFC-8246.txt"},{"from":"IETF RFC 8248","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8248/RFC-8248.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8297","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8297/RFC-8297.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8307","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8307/RFC-8307.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8391","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8391/RFC-8391.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8411","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8421","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8421/RFC-8421.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8478","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8478/RFC-8478.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8746","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8903","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8903/RFC-8903.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8937","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8943","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8943/RFC-8943.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 9021","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9021/RFC-9021.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9106","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9106/RFC-9106.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9285","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 7841","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 7841","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 7824","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-7824/RFC-7824.txt"},{"from":"IETF RFC 7934","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-7934/RFC-7934.txt"},{"from":"IETF RFC 7969","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-7969/RFC-7969.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 7844","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8122","to":"IETF RFC 7850","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7850","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7857","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7857","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 7857","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 7858","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 8165","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-8165/RFC-8165.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 7871","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 7872","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 7872","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 7929","to":"IETF RFC 7873","kind":"references","source":"IETF/RFC-7929/RFC-7929.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7873","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 7873","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7873","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 7873","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 7874","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 7874","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 7874","to":"IETF RFC 7875","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 0821","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-0821/RFC-0821.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 790","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 800","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 801","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 821","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-821/RFC-821.txt"},{"from":"IETF RFC 840","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 788","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7889","to":"IETF RFC 7888","kind":"references","source":"IETF/RFC-7889/RFC-7889.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 7888","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 7888","to":"IETF RFC 7889","kind":"references","source":"IETF/RFC-7888/RFC-7888.txt"},{"from":"IETF RFC 4593","to":"IETF RFC 789","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 7893","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 7895","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7895","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7895","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 7895","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 0791","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-0791/RFC-0791.txt"},{"from":"IETF RFC 0793","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-0793/RFC-0793.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 791","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-791/RFC-791.txt"},{"from":"IETF RFC 793","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-793/RFC-793.txt"},{"from":"IETF RFC 800","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 801","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 802","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-802/RFC-802.txt"},{"from":"IETF RFC 810","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-810/RFC-810.txt"},{"from":"IETF RFC 823","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-823/RFC-823.txt"},{"from":"IETF RFC 824","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-824/RFC-824.txt"},{"from":"IETF RFC 830","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-830/RFC-830.txt"},{"from":"IETF RFC 840","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 790","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 7905","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 0792","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0792/RFC-0792.txt"},{"from":"IETF RFC 0793","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0793/RFC-0793.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0919","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0919/RFC-0919.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1006","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1016","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1016/RFC-1016.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1075","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1075/RFC-1075.txt"},{"from":"IETF RFC 1085","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 1131","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1131/RFC-1131.pdf"},{"from":"IETF RFC 1134","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1171","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1195","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1234","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1234/RFC-1234.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1240","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1241","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1241/RFC-1241.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1247","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 1248","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1248/RFC-1248.txt"},{"from":"IETF RFC 1252","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1252/RFC-1252.txt"},{"from":"IETF RFC 1253","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1253/RFC-1253.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1265","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1265/RFC-1265.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1329","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1356","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1383","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1383/RFC-1383.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1455","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1455/RFC-1455.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1476","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 1517","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1517/RFC-1517.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1573","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1624","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1624/RFC-1624.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1710","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1710/RFC-1710.txt"},{"from":"IETF RFC 1716","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1717","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1769","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1769/RFC-1769.txt"},{"from":"IETF RFC 1770","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1770/RFC-1770.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1774","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1810","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1810/RFC-1810.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1819","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1819/RFC-1819.txt"},{"from":"IETF RFC 1850","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1850/RFC-1850.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 1858","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1858/RFC-1858.txt"},{"from":"IETF RFC 1859","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 1883","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1883/RFC-1883.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1940","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1940/RFC-1940.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1990","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2004","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2004/RFC-2004.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2067","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2067/RFC-2067.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2096","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2145","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2145/RFC-2145.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2233","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2233/RFC-2233.txt"},{"from":"IETF RFC 2283","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2283/RFC-2283.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2386","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2386/RFC-2386.txt"},{"from":"IETF RFC 2393","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2393/RFC-2393.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2402","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2402/RFC-2402.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2434","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2434/RFC-2434.txt"},{"from":"IETF RFC 2441","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2441/RFC-2441.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2460","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2460/RFC-2460.txt"},{"from":"IETF RFC 2474","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2474/RFC-2474.txt"},{"from":"IETF RFC 2475","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2529","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2529/RFC-2529.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2661","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2661/RFC-2661.txt"},{"from":"IETF RFC 2678","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2678/RFC-2678.txt"},{"from":"IETF RFC 2679","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2679/RFC-2679.txt"},{"from":"IETF RFC 2680","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2680/RFC-2680.txt"},{"from":"IETF RFC 2681","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2681/RFC-2681.txt"},{"from":"IETF RFC 2734","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2734/RFC-2734.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2795","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2795/RFC-2795.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2835","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2835/RFC-2835.txt"},{"from":"IETF RFC 2858","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2858/RFC-2858.txt"},{"from":"IETF RFC 2863","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2863/RFC-2863.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2962","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2962/RFC-2962.txt"},{"from":"IETF RFC 2983","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-2983/RFC-2983.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3056","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3056/RFC-3056.txt"},{"from":"IETF RFC 3095","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3095/RFC-3095.txt"},{"from":"IETF RFC 3096","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3096/RFC-3096.txt"},{"from":"IETF RFC 3164","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3173","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3173/RFC-3173.txt"},{"from":"IETF RFC 3175","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3175/RFC-3175.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3260","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3260/RFC-3260.txt"},{"from":"IETF RFC 3269","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3269/RFC-3269.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3290","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3393","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 3417","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3417/RFC-3417.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3489","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3489/RFC-3489.txt"},{"from":"IETF RFC 3514","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3514/RFC-3514.txt"},{"from":"IETF RFC 3519","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3519/RFC-3519.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3550","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3670","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3670/RFC-3670.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3682","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3682/RFC-3682.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3692","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3692/RFC-3692.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3750","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3750/RFC-3750.txt"},{"from":"IETF RFC 3779","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3814","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3814/RFC-3814.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3843","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3843/RFC-3843.txt"},{"from":"IETF RFC 3890","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3890/RFC-3890.txt"},{"from":"IETF RFC 3917","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3917/RFC-3917.txt"},{"from":"IETF RFC 3982","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4006","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4019","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4019/RFC-4019.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4067","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4067/RFC-4067.txt"},{"from":"IETF RFC 4103","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4149","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4149/RFC-4149.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4213","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4213/RFC-4213.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4302","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4302/RFC-4302.txt"},{"from":"IETF RFC 4303","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4303/RFC-4303.txt"},{"from":"IETF RFC 4305","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4305/RFC-4305.txt"},{"from":"IETF RFC 4309","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4309/RFC-4309.txt"},{"from":"IETF RFC 4322","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4322/RFC-4322.txt"},{"from":"IETF RFC 4323","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4323/RFC-4323.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4380","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4380/RFC-4380.txt"},{"from":"IETF RFC 4385","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4385/RFC-4385.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4513","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4540","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4540/RFC-4540.txt"},{"from":"IETF RFC 4553","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4607","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4607/RFC-4607.txt"},{"from":"IETF RFC 4623","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4623/RFC-4623.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 4710","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4727","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4727/RFC-4727.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4750","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4750/RFC-4750.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4815","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4815/RFC-4815.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4945","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4945/RFC-4945.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4963","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4963/RFC-4963.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 4997","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5082","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5082/RFC-5082.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5225","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5225/RFC-5225.txt"},{"from":"IETF RFC 5226","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5226/RFC-5226.txt"},{"from":"IETF RFC 5237","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5237/RFC-5237.txt"},{"from":"IETF RFC 5280","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5340","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5340/RFC-5340.txt"},{"from":"IETF RFC 5389","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5426","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5426/RFC-5426.txt"},{"from":"IETF RFC 5474","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5474/RFC-5474.txt"},{"from":"IETF RFC 5477","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5477/RFC-5477.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5720","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5720/RFC-5720.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5766","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5766/RFC-5766.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5804","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6125","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6328","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 6396","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6621","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6621/RFC-6621.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6746","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6746/RFC-6746.txt"},{"from":"IETF RFC 6830","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6830/RFC-6830.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6864","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6864/RFC-6864.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7325","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7679","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 790","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 792","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-792/RFC-792.txt"},{"from":"IETF RFC 793","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-793/RFC-793.txt"},{"from":"IETF RFC 795","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-795/RFC-795.txt"},{"from":"IETF RFC 796","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-796/RFC-796.txt"},{"from":"IETF RFC 800","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 801","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 810","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-810/RFC-810.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 820","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 823","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-823/RFC-823.txt"},{"from":"IETF RFC 824","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-824/RFC-824.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 840","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 870","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 879","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-879/RFC-879.txt"},{"from":"IETF RFC 880","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 887","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 900","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 901","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 906","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-906/RFC-906.txt"},{"from":"IETF RFC 908","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-908/RFC-908.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 919","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-919/RFC-919.txt"},{"from":"IETF RFC 923","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 960","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 983","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-983/RFC-983.txt"},{"from":"IETF RFC 990","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 791","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 7914","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 8021","to":"IETF RFC 7915","kind":"references","source":"IETF/RFC-8021/RFC-8021.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7915","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 7919","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-7919/RFC-7919.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7918","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 7919","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7919","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7919","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 0791","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0791/RFC-0791.txt"},{"from":"IETF RFC 0792","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0792/RFC-0792.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 0896","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0896/RFC-0896.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1016","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1016/RFC-1016.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1195","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1241","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1241/RFC-1241.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1393","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1393/RFC-1393.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1458","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1458/RFC-1458.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1788","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1788/RFC-1788.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1853","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1853/RFC-1853.txt"},{"from":"IETF RFC 1885","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1885/RFC-1885.txt"},{"from":"IETF RFC 1937","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1937/RFC-1937.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2003","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2003/RFC-2003.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2201","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2201/RFC-2201.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2463","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2463/RFC-2463.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2765","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2765/RFC-2765.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3032","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3032/RFC-3032.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3209","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3209/RFC-3209.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4008","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4008/RFC-4008.txt"},{"from":"IETF RFC 4023","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4023/RFC-4023.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4377","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4379","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4379/RFC-4379.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4443","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4443/RFC-4443.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4787","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4787/RFC-4787.txt"},{"from":"IETF RFC 4838","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4838/RFC-4838.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4884","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4884/RFC-4884.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5085","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5085/RFC-5085.txt"},{"from":"IETF RFC 5087","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5201","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5201/RFC-5201.txt"},{"from":"IETF RFC 5320","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5320/RFC-5320.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5837","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6115","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6115/RFC-6115.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6425","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6425/RFC-6425.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6760","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6951","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-6951/RFC-6951.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7276","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7450","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7450/RFC-7450.txt"},{"from":"IETF RFC 7588","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7588/RFC-7588.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 7658","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7658/RFC-7658.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 790","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 791","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-791/RFC-791.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 800","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 801","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 820","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 823","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-823/RFC-823.txt"},{"from":"IETF RFC 840","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 870","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 879","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-879/RFC-879.txt"},{"from":"IETF RFC 880","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 887","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 896","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-896/RFC-896.txt"},{"from":"IETF RFC 900","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 792","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7925","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-7925/RFC-7925.txt"},{"from":"IETF RFC 8094","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-8094/RFC-8094.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7924","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7925","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7925","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 7925","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 7925","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 7928","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 7929","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 7929","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 7929","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0821","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0821/RFC-0821.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1006","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1072","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1072/RFC-1072.txt"},{"from":"IETF RFC 1085","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1105","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1105/RFC-1105.txt"},{"from":"IETF RFC 1106","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1106/RFC-1106.txt"},{"from":"IETF RFC 1144","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1144/RFC-1144.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1185","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1185/RFC-1185.txt"},{"from":"IETF RFC 1189","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1190","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1190/RFC-1190.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1241","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1241/RFC-1241.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1270","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1270/RFC-1270.txt"},{"from":"IETF RFC 1301","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1301/RFC-1301.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1626","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1626/RFC-1626.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1693","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1693/RFC-1693.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1726","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1726/RFC-1726.txt"},{"from":"IETF RFC 1770","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1770/RFC-1770.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1831","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1831/RFC-1831.txt"},{"from":"IETF RFC 1858","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1858/RFC-1858.txt"},{"from":"IETF RFC 1859","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1982","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1982/RFC-1982.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2012","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2012/RFC-2012.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2326","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2452","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2452/RFC-2452.txt"},{"from":"IETF RFC 2481","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2481/RFC-2481.txt"},{"from":"IETF RFC 2488","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2488/RFC-2488.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2637","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2637/RFC-2637.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2675","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2675/RFC-2675.txt"},{"from":"IETF RFC 2747","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2747/RFC-2747.txt"},{"from":"IETF RFC 2760","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2760/RFC-2760.txt"},{"from":"IETF RFC 2775","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2775/RFC-2775.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 2795","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2795/RFC-2795.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2873","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2873/RFC-2873.txt"},{"from":"IETF RFC 2883","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 2885","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 2960","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2960/RFC-2960.txt"},{"from":"IETF RFC 2975","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2975/RFC-2975.txt"},{"from":"IETF RFC 2988","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2988/RFC-2988.txt"},{"from":"IETF RFC 2993","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-2993/RFC-2993.txt"},{"from":"IETF RFC 3015","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3018","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3018/RFC-3018.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3033","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3042","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3042/RFC-3042.txt"},{"from":"IETF RFC 3080","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3081","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3081/RFC-3081.txt"},{"from":"IETF RFC 3124","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3124/RFC-3124.txt"},{"from":"IETF RFC 3135","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3135/RFC-3135.txt"},{"from":"IETF RFC 3142","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3142/RFC-3142.txt"},{"from":"IETF RFC 3148","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3148/RFC-3148.txt"},{"from":"IETF RFC 3155","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3155/RFC-3155.txt"},{"from":"IETF RFC 3168","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3168/RFC-3168.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3242","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3242/RFC-3242.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3257","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3257/RFC-3257.txt"},{"from":"IETF RFC 3291","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3291/RFC-3291.txt"},{"from":"IETF RFC 3360","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3360/RFC-3360.txt"},{"from":"IETF RFC 3366","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3430","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3430/RFC-3430.txt"},{"from":"IETF RFC 3436","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3436/RFC-3436.txt"},{"from":"IETF RFC 3449","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3481","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3481/RFC-3481.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 3517","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3517/RFC-3517.txt"},{"from":"IETF RFC 3522","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3522/RFC-3522.txt"},{"from":"IETF RFC 3525","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3530","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3588","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3708","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3708/RFC-3708.txt"},{"from":"IETF RFC 3715","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3715/RFC-3715.txt"},{"from":"IETF RFC 3720","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3723","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3723/RFC-3723.txt"},{"from":"IETF RFC 3724","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3724/RFC-3724.txt"},{"from":"IETF RFC 3730","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3734","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3734/RFC-3734.txt"},{"from":"IETF RFC 3748","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3783","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3783/RFC-3783.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3821","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3821/RFC-3821.txt"},{"from":"IETF RFC 3828","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3920","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3954","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3954/RFC-3954.txt"},{"from":"IETF RFC 3955","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-3955/RFC-3955.txt"},{"from":"IETF RFC 4001","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4001/RFC-4001.txt"},{"from":"IETF RFC 4015","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4015/RFC-4015.txt"},{"from":"IETF RFC 4022","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4022/RFC-4022.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4145","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4163","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4163/RFC-4163.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4180","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4180/RFC-4180.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4294","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4294/RFC-4294.txt"},{"from":"IETF RFC 4297","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 4340","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4340/RFC-4340.txt"},{"from":"IETF RFC 4341","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4341/RFC-4341.txt"},{"from":"IETF RFC 4347","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4347/RFC-4347.txt"},{"from":"IETF RFC 4362","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4362/RFC-4362.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4430","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4430/RFC-4430.txt"},{"from":"IETF RFC 4497","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4511","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4594","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 4712","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4737","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4782","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4782/RFC-4782.txt"},{"from":"IETF RFC 4786","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4786/RFC-4786.txt"},{"from":"IETF RFC 4821","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4821/RFC-4821.txt"},{"from":"IETF RFC 4898","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4898/RFC-4898.txt"},{"from":"IETF RFC 4930","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4934","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4934/RFC-4934.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4953","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4953/RFC-4953.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 4961","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4961/RFC-4961.txt"},{"from":"IETF RFC 4987","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4987/RFC-4987.txt"},{"from":"IETF RFC 4995","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4995/RFC-4995.txt"},{"from":"IETF RFC 4996","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-4996/RFC-4996.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5040","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5040/RFC-5040.txt"},{"from":"IETF RFC 5041","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5041/RFC-5041.txt"},{"from":"IETF RFC 5042","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5042/RFC-5042.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5046","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5046/RFC-5046.txt"},{"from":"IETF RFC 5101","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5101/RFC-5101.txt"},{"from":"IETF RFC 5102","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5102/RFC-5102.txt"},{"from":"IETF RFC 5128","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5128/RFC-5128.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5246","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5383","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5383/RFC-5383.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5482","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 5508","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5508/RFC-5508.txt"},{"from":"IETF RFC 5513","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5513/RFC-5513.txt"},{"from":"IETF RFC 5531","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5531/RFC-5531.txt"},{"from":"IETF RFC 5562","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5562/RFC-5562.txt"},{"from":"IETF RFC 5570","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"IETF RFC 5575","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5575/RFC-5575.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 5596","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5596/RFC-5596.txt"},{"from":"IETF RFC 5625","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5625/RFC-5625.txt"},{"from":"IETF RFC 5626","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5660","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5660/RFC-5660.txt"},{"from":"IETF RFC 5665","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5665/RFC-5665.txt"},{"from":"IETF RFC 5677","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5677/RFC-5677.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5730","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5734","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5734/RFC-5734.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 5795","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5795/RFC-5795.txt"},{"from":"IETF RFC 5827","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5827/RFC-5827.txt"},{"from":"IETF RFC 5898","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5898/RFC-5898.txt"},{"from":"IETF RFC 5905","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5905/RFC-5905.txt"},{"from":"IETF RFC 5925","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5925/RFC-5925.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 5936","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5936/RFC-5936.txt"},{"from":"IETF RFC 5961","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5961/RFC-5961.txt"},{"from":"IETF RFC 5966","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5966/RFC-5966.txt"},{"from":"IETF RFC 5985","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-5985/RFC-5985.txt"},{"from":"IETF RFC 6013","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6013/RFC-6013.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6039","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6039/RFC-6039.txt"},{"from":"IETF RFC 6056","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6056/RFC-6056.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6077","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6077/RFC-6077.txt"},{"from":"IETF RFC 6083","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6083/RFC-6083.txt"},{"from":"IETF RFC 6084","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6084/RFC-6084.txt"},{"from":"IETF RFC 6086","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6086/RFC-6086.txt"},{"from":"IETF RFC 6088","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6088/RFC-6088.txt"},{"from":"IETF RFC 6092","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6092/RFC-6092.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6120","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6135","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6135/RFC-6135.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6146","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6146/RFC-6146.txt"},{"from":"IETF RFC 6181","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6181/RFC-6181.txt"},{"from":"IETF RFC 6182","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6182/RFC-6182.txt"},{"from":"IETF RFC 6191","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6191/RFC-6191.txt"},{"from":"IETF RFC 6202","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6202/RFC-6202.txt"},{"from":"IETF RFC 6219","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6219/RFC-6219.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6256","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6284","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6284/RFC-6284.txt"},{"from":"IETF RFC 6298","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6298/RFC-6298.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 6347","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6347/RFC-6347.txt"},{"from":"IETF RFC 6356","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6356/RFC-6356.txt"},{"from":"IETF RFC 6390","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 6429","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6429/RFC-6429.txt"},{"from":"IETF RFC 6434","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 6458","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6458/RFC-6458.txt"},{"from":"IETF RFC 6466","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6466/RFC-6466.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 6574","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6574/RFC-6574.txt"},{"from":"IETF RFC 6627","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6627/RFC-6627.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6633","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6633/RFC-6633.txt"},{"from":"IETF RFC 6675","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6675/RFC-6675.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 6733","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6787","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6824","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6824/RFC-6824.txt"},{"from":"IETF RFC 6846","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6846/RFC-6846.txt"},{"from":"IETF RFC 6887","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6887/RFC-6887.txt"},{"from":"IETF RFC 6888","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6888/RFC-6888.txt"},{"from":"IETF RFC 6897","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6897/RFC-6897.txt"},{"from":"IETF RFC 6921","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6921/RFC-6921.txt"},{"from":"IETF RFC 6936","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6936/RFC-6936.txt"},{"from":"IETF RFC 6937","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6937/RFC-6937.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7011","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7094","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7094/RFC-7094.txt"},{"from":"IETF RFC 7111","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7111/RFC-7111.txt"},{"from":"IETF RFC 7145","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7145/RFC-7145.txt"},{"from":"IETF RFC 7202","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7202/RFC-7202.txt"},{"from":"IETF RFC 7228","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7230","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7252","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7288","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7288/RFC-7288.txt"},{"from":"IETF RFC 7323","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7323/RFC-7323.txt"},{"from":"IETF RFC 7413","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7413/RFC-7413.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7540","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7540/RFC-7540.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7604","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7604/RFC-7604.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7657","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7657/RFC-7657.txt"},{"from":"IETF RFC 7661","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7661/RFC-7661.txt"},{"from":"IETF RFC 7676","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7676/RFC-7676.txt"},{"from":"IETF RFC 7766","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7766/RFC-7766.txt"},{"from":"IETF RFC 7826","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7872","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7872/RFC-7872.txt"},{"from":"IETF RFC 788","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-788/RFC-788.txt"},{"from":"IETF RFC 790","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-790/RFC-790.txt"},{"from":"IETF RFC 7915","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7915/RFC-7915.txt"},{"from":"IETF RFC 7918","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7918/RFC-7918.txt"},{"from":"IETF RFC 7928","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7928/RFC-7928.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 800","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 801","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-801/RFC-801.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 820","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 821","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-821/RFC-821.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 840","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 870","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 879","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-879/RFC-879.txt"},{"from":"IETF RFC 880","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 882","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 887","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 900","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 915","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 923","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 959","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 960","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 793","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 7932","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 7934","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 7937","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 840","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 794","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 7941","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 7941","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 7941","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 7942","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 0791","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-0791/RFC-0791.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 791","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-791/RFC-791.txt"},{"from":"IETF RFC 840","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 795","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7950","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7952","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 8022","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8022/RFC-8022.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 7951","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 7951","to":"IETF RFC 7952","kind":"references","source":"IETF/RFC-7951/RFC-7951.txt"},{"from":"IETF RFC 8040","to":"IETF RFC 7952","kind":"references","source":"IETF/RFC-8040/RFC-8040.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 7952","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8075","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8075/RFC-8075.txt"},{"from":"IETF RFC 8132","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8132/RFC-8132.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 7959","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 0791","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-0791/RFC-0791.txt"},{"from":"IETF RFC 1005","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-1005/RFC-1005.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 791","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-791/RFC-791.txt"},{"from":"IETF RFC 810","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-810/RFC-810.txt"},{"from":"IETF RFC 811","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-811/RFC-811.txt"},{"from":"IETF RFC 840","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 878","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-878/RFC-878.txt"},{"from":"IETF RFC 880","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 953","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-953/RFC-953.txt"},{"from":"IETF RFC 961","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 796","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 7961","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 7967","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 7967","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 7969","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 924","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 797","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8134","to":"IETF RFC 7970","kind":"references","source":"IETF/RFC-8134/RFC-8134.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 7970","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 7970","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 7975","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 7975","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 7977","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 798","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 800","to":"IETF RFC 798","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 7983","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 7983","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 7983","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 799","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 800","to":"IETF RFC 799","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7990","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7993","to":"IETF RFC 7990","kind":"references","source":"IETF/RFC-7993/RFC-7993.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7996","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7996/RFC-7996.txt"},{"from":"IETF RFC 7997","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7997/RFC-7997.txt"},{"from":"IETF RFC 7998","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-7998/RFC-7998.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 7991","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7992","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7993","to":"IETF RFC 7992","kind":"references","source":"IETF/RFC-7993/RFC-7993.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7992","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF SD-JWT VC","to":"IETF RFC 7992","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF RFC 7990","to":"IETF RFC 7993","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7993","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7993","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7994","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 7994","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7995","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7996","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7996","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7990","to":"IETF RFC 7997","kind":"references","source":"IETF/RFC-7990/RFC-7990.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7997","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7994","to":"IETF RFC 7997","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 7995","to":"IETF RFC 7997","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 7998","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 7998","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 800","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 8007","to":"IETF RFC 8006","kind":"references","source":"IETF/RFC-8007/RFC-8007.txt"},{"from":"IETF RFC 8008","to":"IETF RFC 8006","kind":"references","source":"IETF/RFC-8008/RFC-8008.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 8007","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8007","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8006","to":"IETF RFC 8008","kind":"references","source":"IETF/RFC-8006/RFC-8006.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1475","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-1475/RFC-1475.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 1707","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 800","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 805","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-805/RFC-805.txt"},{"from":"IETF RFC 820","to":"IETF RFC 801","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 8014","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8014","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"IETF RFC 8017","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 8017","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 8152","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 8017","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"ARF TS10 V1.2","to":"IETF RFC 8018","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"IETF RFC 8152","to":"IETF RFC 8018","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 8018","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 802","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 851","to":"IETF RFC 802","kind":"references","source":"IETF/RFC-851/RFC-851.txt"},{"from":"IETF RFC 852","to":"IETF RFC 802","kind":"references","source":"IETF/RFC-852/RFC-852.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 8020","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8020","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 8021","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8022","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8022","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8027","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 8030","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8030","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8037","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8037/RFC-8037.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8411","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 8032","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 8034","to":"IETF RFC 8033","kind":"references","source":"IETF/RFC-8034/RFC-8034.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8033","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 8034","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 8035","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8037","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8037","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 804","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 924","to":"IETF RFC 804","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 804","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 804","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 804","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 8040","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8045","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 805","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 805","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 882","to":"IETF RFC 805","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 805","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 8187","to":"IETF RFC 8053","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8143","to":"IETF RFC 8054","kind":"references","source":"IETF/RFC-8143/RFC-8143.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 8055","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 806","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8064","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8071","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8073","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8075","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 8075","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8075","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 8078","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8081","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 8081","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 8083","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 8083","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8083","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 8084","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 8084","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8084","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8084/RFC-8084.txt"},{"from":"IETF RFC 8086","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8086/RFC-8086.txt"},{"from":"IETF RFC 8087","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8087/RFC-8087.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8085","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 8086","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8086","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8086","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 8087","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8087","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8087","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8088","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 8089","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 8412","to":"IETF RFC 8089","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 8089","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8091","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 8094","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 8098","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8098","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0952","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-0952/RFC-0952.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 811","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-811/RFC-811.txt"},{"from":"IETF RFC 840","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 900","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 952","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-952/RFC-952.txt"},{"from":"IETF RFC 960","to":"IETF RFC 810","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 8083","to":"IETF RFC 8108","kind":"references","source":"IETF/RFC-8083/RFC-8083.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8108","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8108","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8108","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 8109","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 8109","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 810","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-810/RFC-810.txt"},{"from":"IETF RFC 820","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 900","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 953","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-953/RFC-953.txt"},{"from":"IETF RFC 960","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 811","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0954","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-0954/RFC-0954.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1712","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-1712/RFC-1712.txt"},{"from":"IETF RFC 820","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 900","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 954","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-954/RFC-954.txt"},{"from":"IETF RFC 960","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 812","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8122","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8152","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8391","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8391/RFC-8391.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8411","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8126","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 0817","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-0817/RFC-0817.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2581","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-2581/RFC-2581.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 4460","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-4460/RFC-4460.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4960","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-4960/RFC-4960.txt"},{"from":"IETF RFC 5681","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-5681/RFC-5681.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 817","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-817/RFC-817.txt"},{"from":"IETF RFC 840","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 813","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8132","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8132","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 8274","to":"IETF RFC 8134","kind":"references","source":"IETF/RFC-8274/RFC-8274.txt"},{"from":"IETF RFC 0817","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-0817/RFC-0817.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 5595","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-5595/RFC-5595.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 817","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-817/RFC-817.txt"},{"from":"IETF RFC 840","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 814","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8126","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 8141","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8143","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8145","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 8145","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 0817","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-0817/RFC-0817.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1858","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-1858/RFC-1858.txt"},{"from":"IETF RFC 2011","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-2011/RFC-2011.txt"},{"from":"IETF RFC 2465","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-2465/RFC-2465.txt"},{"from":"IETF RFC 3511","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-3511/RFC-3511.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 817","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-817/RFC-817.txt"},{"from":"IETF RFC 840","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 815","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 8152","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 8152","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"IETF RFC 8230","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 9021","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9021/RFC-9021.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8152","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8156","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 0814","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-0814/RFC-0814.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4907","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-4907/RFC-4907.txt"},{"from":"IETF RFC 5461","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-5461/RFC-5461.txt"},{"from":"IETF RFC 5927","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-5927/RFC-5927.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 814","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-814/RFC-814.txt"},{"from":"IETF RFC 840","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 816","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8162","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8162","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8164","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 8164","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8164","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 8165","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8165","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8168","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 0814","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-0814/RFC-0814.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 814","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-814/RFC-814.txt"},{"from":"IETF RFC 840","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 817","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ARF TS03 V1.5.2","to":"IETF RFC 8174","kind":"references","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md"},{"from":"ARF TS09 V1.1","to":"IETF RFC 8174","kind":"references","source":"ARF/TS09-V1.1/TS09-V1.1.md"},{"from":"ARF TS10 V1.2","to":"IETF RFC 8174","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 8174","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"IETF RFC 8152","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8152/RFC-8152.txt"},{"from":"IETF RFC 8156","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8156/RFC-8156.txt"},{"from":"IETF RFC 8162","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8162/RFC-8162.txt"},{"from":"IETF RFC 8168","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8168/RFC-8168.txt"},{"from":"IETF RFC 8188","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8198","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8198/RFC-8198.txt"},{"from":"IETF RFC 8213","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8213/RFC-8213.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8230","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8230/RFC-8230.txt"},{"from":"IETF RFC 8235","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8235/RFC-8235.txt"},{"from":"IETF RFC 8246","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8246/RFC-8246.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 8252","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8252/RFC-8252.txt"},{"from":"IETF RFC 8257","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8257/RFC-8257.txt"},{"from":"IETF RFC 8259","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8260","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8260/RFC-8260.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8279","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8279/RFC-8279.txt"},{"from":"IETF RFC 8285","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8285/RFC-8285.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 8297","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8297/RFC-8297.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8310","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8310/RFC-8310.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8312","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8312/RFC-8312.txt"},{"from":"IETF RFC 8314","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8314/RFC-8314.txt"},{"from":"IETF RFC 8322","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8322/RFC-8322.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8336","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8391","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8391/RFC-8391.txt"},{"from":"IETF RFC 8392","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8392/RFC-8392.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8439","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8439/RFC-8439.txt"},{"from":"IETF RFC 8441","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8441/RFC-8441.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8452","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8452/RFC-8452.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8467","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8467/RFC-8467.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8573","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8573/RFC-8573.txt"},{"from":"IETF RFC 8586","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8586/RFC-8586.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8619","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8707","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8707/RFC-8707.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8746","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8937","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8937/RFC-8937.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8945","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8945/RFC-8945.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8985","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8985/RFC-8985.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9021","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9021/RFC-9021.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9106","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9106/RFC-9106.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9285","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9485","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8174","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 8174","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 8174","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 8554","to":"IETF RFC 8179","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 820","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 818","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8288","to":"IETF RFC 8187","kind":"references","source":"IETF/RFC-8288/RFC-8288.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8187","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 8291","to":"IETF RFC 8188","kind":"references","source":"IETF/RFC-8291/RFC-8291.txt"},{"from":"IETF RFC 0819","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-0819/RFC-0819.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 800","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 830","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-830/RFC-830.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 882","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 915","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 819","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 8981","to":"IETF RFC 8190","kind":"references","source":"IETF/RFC-8981/RFC-8981.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 8198","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 8198","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8198","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 820","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 820","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 840","to":"IETF RFC 820","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 880","to":"IETF RFC 820","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 820","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 8201","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8201/RFC-8201.txt"},{"from":"IETF RFC 8250","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8250/RFC-8250.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8305","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8305/RFC-8305.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8612","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8612/RFC-8612.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8200","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8200","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8200/RFC-8200.txt"},{"from":"IETF RFC 8300","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8300/RFC-8300.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8201","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0821","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-0821/RFC-0821.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1064","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1064/RFC-1064.txt"},{"from":"IETF RFC 1081","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1081/RFC-1081.txt"},{"from":"IETF RFC 1090","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1090/RFC-1090.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1135","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1135/RFC-1135.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1175","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1175/RFC-1175.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1204","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1204/RFC-1204.txt"},{"from":"IETF RFC 1208","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1208/RFC-1208.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1343","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1343/RFC-1343.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1425","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1425/RFC-1425.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1440","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1440/RFC-1440.txt"},{"from":"IETF RFC 1460","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1460/RFC-1460.txt"},{"from":"IETF RFC 1492","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1492/RFC-1492.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1524","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1524/RFC-1524.txt"},{"from":"IETF RFC 1568","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1568/RFC-1568.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1651","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1651/RFC-1651.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1725","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1725/RFC-1725.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1767","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1767/RFC-1767.txt"},{"from":"IETF RFC 1830","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1830/RFC-1830.txt"},{"from":"IETF RFC 1835","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1835/RFC-1835.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1846","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1846/RFC-1846.txt"},{"from":"IETF RFC 1854","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1854/RFC-1854.txt"},{"from":"IETF RFC 1869","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1869/RFC-1869.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1893","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1893/RFC-1893.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 1985","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-1985/RFC-1985.txt"},{"from":"IETF RFC 2033","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2033/RFC-2033.txt"},{"from":"IETF RFC 2034","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2034/RFC-2034.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2197","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2197/RFC-2197.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2414","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2414/RFC-2414.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2449","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2449/RFC-2449.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2486","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2486/RFC-2486.txt"},{"from":"IETF RFC 2487","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2487/RFC-2487.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2645","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2645/RFC-2645.txt"},{"from":"IETF RFC 2646","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2646/RFC-2646.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2705","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2705/RFC-2705.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2920","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2920/RFC-2920.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 2979","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-2979/RFC-2979.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3207","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3207/RFC-3207.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3390","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3390/RFC-3390.txt"},{"from":"IETF RFC 3435","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3463","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3463/RFC-3463.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3848","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3848/RFC-3848.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 4282","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-4282/RFC-4282.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5068","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-5068/RFC-5068.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 800","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 820","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 900","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 915","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 923","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 937","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-937/RFC-937.txt"},{"from":"IETF RFC 943","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 987","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-987/RFC-987.txt"},{"from":"IETF RFC 990","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 821","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 8213","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0821","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-0821/RFC-0821.txt"},{"from":"IETF RFC 0850","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-0850/RFC-0850.txt"},{"from":"IETF RFC 0989","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-0989/RFC-0989.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1064","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1064/RFC-1064.txt"},{"from":"IETF RFC 1081","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1081/RFC-1081.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1123","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1123/RFC-1123.txt"},{"from":"IETF RFC 1137","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1137/RFC-1137.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1140","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1140/RFC-1140.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1153","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1153/RFC-1153.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1208","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1208/RFC-1208.txt"},{"from":"IETF RFC 1211","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1211/RFC-1211.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 1274","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1274/RFC-1274.txt"},{"from":"IETF RFC 1279","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1279/RFC-1279.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1328","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1328/RFC-1328.txt"},{"from":"IETF RFC 1340","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1342","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1342/RFC-1342.txt"},{"from":"IETF RFC 1343","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1343/RFC-1343.txt"},{"from":"IETF RFC 1344","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1344/RFC-1344.txt"},{"from":"IETF RFC 1360","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1405","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1405/RFC-1405.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1423","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1424","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1424/RFC-1424.txt"},{"from":"IETF RFC 1425","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1425/RFC-1425.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1428","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1460","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1460/RFC-1460.txt"},{"from":"IETF RFC 1465","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 1468","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1470","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1485","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1485/RFC-1485.txt"},{"from":"IETF RFC 1486","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1486/RFC-1486.txt"},{"from":"IETF RFC 1488","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1494","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1495","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1522","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1522/RFC-1522.txt"},{"from":"IETF RFC 1524","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1524/RFC-1524.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1554","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1555","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1556","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 1557","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1557/RFC-1557.txt"},{"from":"IETF RFC 1565","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1630","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1630/RFC-1630.txt"},{"from":"IETF RFC 1641","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1648","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1648/RFC-1648.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1651","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1651/RFC-1651.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1664","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1685","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1685/RFC-1685.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1725","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1725/RFC-1725.txt"},{"from":"IETF RFC 1730","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1730/RFC-1730.txt"},{"from":"IETF RFC 1732","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1732/RFC-1732.txt"},{"from":"IETF RFC 1733","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1733/RFC-1733.txt"},{"from":"IETF RFC 1734","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1734/RFC-1734.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1766","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1766/RFC-1766.txt"},{"from":"IETF RFC 1767","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1767/RFC-1767.txt"},{"from":"IETF RFC 1779","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1779/RFC-1779.txt"},{"from":"IETF RFC 1786","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1786/RFC-1786.txt"},{"from":"IETF RFC 1801","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 1806","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1806/RFC-1806.txt"},{"from":"IETF RFC 1808","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1808/RFC-1808.txt"},{"from":"IETF RFC 1830","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1830/RFC-1830.txt"},{"from":"IETF RFC 1834","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1834/RFC-1834.txt"},{"from":"IETF RFC 1836","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 1838","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 1842","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1847","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1847/RFC-1847.txt"},{"from":"IETF RFC 1848","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 1864","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1864/RFC-1864.txt"},{"from":"IETF RFC 1869","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1869/RFC-1869.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1872","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1872/RFC-1872.txt"},{"from":"IETF RFC 1873","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1873/RFC-1873.txt"},{"from":"IETF RFC 1889","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1889/RFC-1889.txt"},{"from":"IETF RFC 1891","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1891/RFC-1891.txt"},{"from":"IETF RFC 1892","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1892/RFC-1892.txt"},{"from":"IETF RFC 1894","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1894/RFC-1894.txt"},{"from":"IETF RFC 1911","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 1920","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1920/RFC-1920.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1939","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1939/RFC-1939.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2000","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2007","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2007/RFC-2007.txt"},{"from":"IETF RFC 2017","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2017/RFC-2017.txt"},{"from":"IETF RFC 2034","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2034/RFC-2034.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2060","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2060/RFC-2060.txt"},{"from":"IETF RFC 2062","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2062/RFC-2062.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2079","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2079/RFC-2079.txt"},{"from":"IETF RFC 2086","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2086/RFC-2086.txt"},{"from":"IETF RFC 2087","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2087/RFC-2087.txt"},{"from":"IETF RFC 2088","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2088/RFC-2088.txt"},{"from":"IETF RFC 2095","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2095/RFC-2095.txt"},{"from":"IETF RFC 2110","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2111","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2111/RFC-2111.txt"},{"from":"IETF RFC 2112","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2112/RFC-2112.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2152","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2160","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2160/RFC-2160.txt"},{"from":"IETF RFC 2162","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 2163","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2164","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2164/RFC-2164.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2168","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2168/RFC-2168.txt"},{"from":"IETF RFC 2180","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2180/RFC-2180.txt"},{"from":"IETF RFC 2183","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2183/RFC-2183.txt"},{"from":"IETF RFC 2184","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2184/RFC-2184.txt"},{"from":"IETF RFC 2192","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2193","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2193/RFC-2193.txt"},{"from":"IETF RFC 2195","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2195/RFC-2195.txt"},{"from":"IETF RFC 2200","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2200/RFC-2200.txt"},{"from":"IETF RFC 2218","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 2231","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2231/RFC-2231.txt"},{"from":"IETF RFC 2234","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2234/RFC-2234.txt"},{"from":"IETF RFC 2243","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2243/RFC-2243.txt"},{"from":"IETF RFC 2245","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2245/RFC-2245.txt"},{"from":"IETF RFC 2248","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2252","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2253","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2253/RFC-2253.txt"},{"from":"IETF RFC 2254","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2280","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2280/RFC-2280.txt"},{"from":"IETF RFC 2294","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 2298","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2298/RFC-2298.txt"},{"from":"IETF RFC 2303","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2303/RFC-2303.txt"},{"from":"IETF RFC 2304","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2304/RFC-2304.txt"},{"from":"IETF RFC 2305","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2305/RFC-2305.txt"},{"from":"IETF RFC 2307","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2312","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2327","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2359","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2359/RFC-2359.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2368","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2368/RFC-2368.txt"},{"from":"IETF RFC 2369","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2369/RFC-2369.txt"},{"from":"IETF RFC 2377","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2377/RFC-2377.txt"},{"from":"IETF RFC 2387","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2387/RFC-2387.txt"},{"from":"IETF RFC 2392","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2392/RFC-2392.txt"},{"from":"IETF RFC 2396","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2400","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2421","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2423","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2423/RFC-2423.txt"},{"from":"IETF RFC 2425","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2440","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2442","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2442/RFC-2442.txt"},{"from":"IETF RFC 2445","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2447","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2447/RFC-2447.txt"},{"from":"IETF RFC 2459","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2479","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2479/RFC-2479.txt"},{"from":"IETF RFC 2480","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2480/RFC-2480.txt"},{"from":"IETF RFC 2505","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2505/RFC-2505.txt"},{"from":"IETF RFC 2527","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2538","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2538/RFC-2538.txt"},{"from":"IETF RFC 2542","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2542/RFC-2542.txt"},{"from":"IETF RFC 2543","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2554","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2554/RFC-2554.txt"},{"from":"IETF RFC 2557","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 2565","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2622","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2622/RFC-2622.txt"},{"from":"IETF RFC 2632","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2634","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2635","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2635/RFC-2635.txt"},{"from":"IETF RFC 2652","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2652/RFC-2652.txt"},{"from":"IETF RFC 2654","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2654/RFC-2654.txt"},{"from":"IETF RFC 2660","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2660/RFC-2660.txt"},{"from":"IETF RFC 2683","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 2692","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2692/RFC-2692.txt"},{"from":"IETF RFC 2704","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2704/RFC-2704.txt"},{"from":"IETF RFC 2725","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2725/RFC-2725.txt"},{"from":"IETF RFC 2774","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2774/RFC-2774.txt"},{"from":"IETF RFC 2801","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2825","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2825/RFC-2825.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2829","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2831","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2846","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2846/RFC-2846.txt"},{"from":"IETF RFC 2848","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 2910","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2912","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2912/RFC-2912.txt"},{"from":"IETF RFC 2919","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2919/RFC-2919.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2971","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-2971/RFC-2971.txt"},{"from":"IETF RFC 3028","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3030","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3030/RFC-3030.txt"},{"from":"IETF RFC 3050","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3050/RFC-3050.txt"},{"from":"IETF RFC 3066","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3156","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3156/RFC-3156.txt"},{"from":"IETF RFC 3191","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3191/RFC-3191.txt"},{"from":"IETF RFC 3192","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3192/RFC-3192.txt"},{"from":"IETF RFC 3249","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3249/RFC-3249.txt"},{"from":"IETF RFC 3280","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3282","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 3297","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3297/RFC-3297.txt"},{"from":"IETF RFC 3335","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3335/RFC-3335.txt"},{"from":"IETF RFC 3339","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3379","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3459","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3459/RFC-3459.txt"},{"from":"IETF RFC 3461","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3461/RFC-3461.txt"},{"from":"IETF RFC 3462","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3462/RFC-3462.txt"},{"from":"IETF RFC 3464","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3464/RFC-3464.txt"},{"from":"IETF RFC 3501","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3501/RFC-3501.txt"},{"from":"IETF RFC 3641","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3647","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3798","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3798/RFC-3798.txt"},{"from":"IETF RFC 3801","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 3834","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3834/RFC-3834.txt"},{"from":"IETF RFC 3851","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3851/RFC-3851.txt"},{"from":"IETF RFC 3854","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 3864","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3864/RFC-3864.txt"},{"from":"IETF RFC 3875","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3886","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3886/RFC-3886.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3888","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3888/RFC-3888.txt"},{"from":"IETF RFC 3965","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3965/RFC-3965.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4021","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 4190","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4234","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4234/RFC-4234.txt"},{"from":"IETF RFC 4250","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4250/RFC-4250.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4301","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4301/RFC-4301.txt"},{"from":"IETF RFC 4306","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4356","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4356/RFC-4356.txt"},{"from":"IETF RFC 4405","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4405/RFC-4405.txt"},{"from":"IETF RFC 4406","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4406/RFC-4406.txt"},{"from":"IETF RFC 4407","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4407/RFC-4407.txt"},{"from":"IETF RFC 4408","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4408/RFC-4408.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 4515","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4523","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4549","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4549/RFC-4549.txt"},{"from":"IETF RFC 4683","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4683/RFC-4683.txt"},{"from":"IETF RFC 4716","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4718","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4718/RFC-4718.txt"},{"from":"IETF RFC 4765","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4809","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4809/RFC-4809.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4871","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 4877","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4877/RFC-4877.txt"},{"from":"IETF RFC 4933","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 4952","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 5064","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5064/RFC-5064.txt"},{"from":"IETF RFC 5070","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5173","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5182","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5182/RFC-5182.txt"},{"from":"IETF RFC 5234","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5234/RFC-5234.txt"},{"from":"IETF RFC 5259","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5259/RFC-5259.txt"},{"from":"IETF RFC 5293","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5293/RFC-5293.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5322","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5322/RFC-5322.txt"},{"from":"IETF RFC 5335","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5337","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5374","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5374/RFC-5374.txt"},{"from":"IETF RFC 5387","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5387/RFC-5387.txt"},{"from":"IETF RFC 5451","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5451/RFC-5451.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 5537","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5598","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5598/RFC-5598.txt"},{"from":"IETF RFC 5703","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5751","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5901","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5901/RFC-5901.txt"},{"from":"IETF RFC 5965","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5965/RFC-5965.txt"},{"from":"IETF RFC 5996","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-5996/RFC-5996.txt"},{"from":"IETF RFC 6331","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6430","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6430/RFC-6430.txt"},{"from":"IETF RFC 6449","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6449/RFC-6449.txt"},{"from":"IETF RFC 6522","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6522/RFC-6522.txt"},{"from":"IETF RFC 6530","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6532","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6591","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6591/RFC-6591.txt"},{"from":"IETF RFC 6648","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6648/RFC-6648.txt"},{"from":"IETF RFC 6709","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6709/RFC-6709.txt"},{"from":"IETF RFC 6854","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6854/RFC-6854.txt"},{"from":"IETF RFC 6858","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-6858/RFC-6858.txt"},{"from":"IETF RFC 7001","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-7001/RFC-7001.txt"},{"from":"IETF RFC 7296","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-7296/RFC-7296.txt"},{"from":"IETF RFC 7407","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-7407/RFC-7407.txt"},{"from":"IETF RFC 7589","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-7589/RFC-7589.txt"},{"from":"IETF RFC 800","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-800/RFC-800.txt"},{"from":"IETF RFC 8098","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 820","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 821","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-821/RFC-821.txt"},{"from":"IETF RFC 840","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 8438","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-8438/RFC-8438.txt"},{"from":"IETF RFC 8474","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-8474/RFC-8474.txt"},{"from":"IETF RFC 850","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-850/RFC-850.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 880","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 915","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 924","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 937","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-937/RFC-937.txt"},{"from":"IETF RFC 944","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 987","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-987/RFC-987.txt"},{"from":"IETF RFC 989","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-989/RFC-989.txt"},{"from":"IETF RFC 991","to":"IETF RFC 822","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8225","to":"IETF RFC 8224","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 8224","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8224","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8224","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 8225","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8226","to":"IETF RFC 8225","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8417","to":"IETF RFC 8225","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8224","to":"IETF RFC 8226","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 840","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 823","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8230","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8230","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 8235","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 0820","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 820","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 870","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 900","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 997","to":"IETF RFC 824","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 8240","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8246","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8246","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 8412","to":"IETF RFC 8248","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8250","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 8252","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 8252","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8252","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 8257","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8311","to":"IETF RFC 8257","kind":"references","source":"IETF/RFC-8311/RFC-8311.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8257","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"ARF TS10 V1.2","to":"IETF RFC 8259","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 8259","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"IETF RFC 8259","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 8259","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 8259","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 8224","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8414","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8414/RFC-8414.txt"},{"from":"IETF RFC 8427","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8427/RFC-8427.txt"},{"from":"IETF RFC 8428","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8693","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8693/RFC-8693.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8785","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8785/RFC-8785.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8941","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8259","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 8259","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 0820","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0903","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-0903/RFC-0903.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1209","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1209/RFC-1209.txt"},{"from":"IETF RFC 1329","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1433","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1433/RFC-1433.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1577","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1577/RFC-1577.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1620","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1620/RFC-1620.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1701","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1701/RFC-1701.txt"},{"from":"IETF RFC 1735","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1735/RFC-1735.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 1970","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-1970/RFC-1970.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2225","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2225/RFC-2225.txt"},{"from":"IETF RFC 2332","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2332/RFC-2332.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2461","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2461/RFC-2461.txt"},{"from":"IETF RFC 2469","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2469/RFC-2469.txt"},{"from":"IETF RFC 2491","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2491/RFC-2491.txt"},{"from":"IETF RFC 2625","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3077","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3077/RFC-3077.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3315","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3315/RFC-3315.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 3579","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3684","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3684/RFC-3684.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 3819","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4058","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4058/RFC-4058.txt"},{"from":"IETF RFC 4293","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4293/RFC-4293.txt"},{"from":"IETF RFC 4338","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4338/RFC-4338.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4391","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4391/RFC-4391.txt"},{"from":"IETF RFC 4436","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4436/RFC-4436.txt"},{"from":"IETF RFC 4562","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4562/RFC-4562.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 4861","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4861/RFC-4861.txt"},{"from":"IETF RFC 4881","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4881/RFC-4881.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5007","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5007/RFC-5007.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5227","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 5556","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5556/RFC-5556.txt"},{"from":"IETF RFC 5558","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5558/RFC-5558.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5838","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5838/RFC-5838.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6069","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6069/RFC-6069.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6740","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6740/RFC-6740.txt"},{"from":"IETF RFC 6741","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6741/RFC-6741.txt"},{"from":"IETF RFC 6747","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6747/RFC-6747.txt"},{"from":"IETF RFC 6820","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6820/RFC-6820.txt"},{"from":"IETF RFC 6939","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6939/RFC-6939.txt"},{"from":"IETF RFC 6959","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-6959/RFC-6959.txt"},{"from":"IETF RFC 7067","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7277","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-7277/RFC-7277.txt"},{"from":"IETF RFC 7513","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-7513/RFC-7513.txt"},{"from":"IETF RFC 7780","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8014","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 820","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8415","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 870","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 879","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-879/RFC-879.txt"},{"from":"IETF RFC 900","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 903","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-903/RFC-903.txt"},{"from":"IETF RFC 906","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-906/RFC-906.txt"},{"from":"IETF RFC 923","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 960","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 826","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8261","to":"IETF RFC 8260","kind":"references","source":"IETF/RFC-8261/RFC-8261.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8260","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8261","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 8264","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8266","to":"IETF RFC 8264","kind":"references","source":"IETF/RFC-8266/RFC-8266.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8264","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8264","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 8265","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8265","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8264","to":"IETF RFC 8266","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"IETF RFC 8266","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 0820","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-0820/RFC-0820.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1125","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1125/RFC-1125.txt"},{"from":"IETF RFC 1136","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1136/RFC-1136.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1322","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2235","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-2235/RFC-2235.txt"},{"from":"IETF RFC 820","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-820/RFC-820.txt"},{"from":"IETF RFC 840","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-840/RFC-840.txt"},{"from":"IETF RFC 870","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 827","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8274","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8293","to":"IETF RFC 8279","kind":"references","source":"IETF/RFC-8293/RFC-8293.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8285","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8285","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8285","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 8285","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8285","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"IETF RFC 8288","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"IETF RFC 8336","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-8336/RFC-8336.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 8288","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 8290","to":"IETF RFC 8289","kind":"references","source":"IETF/RFC-8290/RFC-8290.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8289","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 8290","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8291","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8926","to":"IETF RFC 8293","kind":"references","source":"IETF/RFC-8926/RFC-8926.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8297","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 8297","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 830","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 830","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 830","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 882","to":"IETF RFC 830","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 830","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8300","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8421","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-8421/RFC-8421.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8305","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 8323","to":"IETF RFC 8307","kind":"references","source":"IETF/RFC-8323/RFC-8323.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 8307","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 8310","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8310","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8310","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8310","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 8310","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8311","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8311","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8311","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 8511","to":"IETF RFC 8312","kind":"references","source":"IETF/RFC-8511/RFC-8511.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8312","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 8314","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 8314","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8314","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 832","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 847","to":"IETF RFC 832","kind":"references","source":"IETF/RFC-847/RFC-847.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 8322","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8322","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8615","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-8615/RFC-8615.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8323","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 8404","to":"IETF RFC 8336","kind":"references","source":"IETF/RFC-8404/RFC-8404.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 8336","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8336","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8792","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-8792/RFC-8792.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8340","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8341","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8341","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8341/RFC-8341.txt"},{"from":"IETF RFC 8343","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8343/RFC-8343.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8348","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8348/RFC-8348.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8791","to":"IETF RFC 8342","kind":"references","source":"IETF/RFC-8791/RFC-8791.txt"},{"from":"IETF RFC 8340","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8340/RFC-8340.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8344","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8344/RFC-8344.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8343","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8342","to":"IETF RFC 8344","kind":"references","source":"IETF/RFC-8342/RFC-8342.txt"},{"from":"IETF RFC 8349","to":"IETF RFC 8344","kind":"references","source":"IETF/RFC-8349/RFC-8349.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8348","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8407","to":"IETF RFC 8349","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8366","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8554","to":"IETF RFC 8391","kind":"references","source":"IETF/RFC-8554/RFC-8554.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8391","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"legal:2025-848","to":"IETF RFC 8392","kind":"cites","source":"implementing-acts/2025-848/2025-848.md"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 8392","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 8747","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9334","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9334/RFC-9334.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 8392","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 8392","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 8399","to":"IETF RFC 8398","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8398","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8398","to":"IETF RFC 8399","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 880","to":"IETF RFC 840","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 8404","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8404","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8407","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8407","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 841","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 8411","to":"IETF RFC 8410","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8418","to":"IETF RFC 8410","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"IETF RFC 8410","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"IETF RFC 8410","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8410","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8410","to":"IETF RFC 8411","kind":"references","source":"IETF/RFC-8410/RFC-8410.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8412","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 8414","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 8628","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8414","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8415","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 8725","to":"IETF RFC 8417","kind":"references","source":"IETF/RFC-8725/RFC-8725.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 8418","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 8419","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8445","to":"IETF RFC 8421","kind":"references","source":"IETF/RFC-8445/RFC-8445.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8422","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8427","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8610","to":"IETF RFC 8428","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8428","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 8428","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 8428","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8428","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 843","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8438","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8439","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8439","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8439","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8439","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8439","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8441","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 8421","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8421/RFC-8421.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8445","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"IETF RFC 8446","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 8446","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 495 V1.7.1","to":"IETF RFC 8446","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"IETF RFC 8407","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8407/RFC-8407.txt"},{"from":"IETF RFC 8447","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8447/RFC-8447.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 8470","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8470/RFC-8470.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8489","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 8521","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8521/RFC-8521.txt"},{"from":"IETF RFC 8555","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8613","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8628","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8628/RFC-8628.txt"},{"from":"IETF RFC 8705","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8752","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8752/RFC-8752.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9146","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9146/RFC-9146.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9162","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8446","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8449","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-8449/RFC-8449.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8996","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-8996/RFC-8996.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9155","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-9155/RFC-9155.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 8447","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 8446","to":"IETF RFC 8449","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8452","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8461","to":"IETF RFC 8460","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8460","to":"IETF RFC 8461","kind":"references","source":"IETF/RFC-8460/RFC-8460.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8461","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 8461","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8461","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 8465","to":"IETF RFC 8464","kind":"references","source":"IETF/RFC-8465/RFC-8465.txt"},{"from":"IETF RFC 9039","to":"IETF RFC 8464","kind":"references","source":"IETF/RFC-9039/RFC-9039.txt"},{"from":"IETF RFC 8464","to":"IETF RFC 8465","kind":"references","source":"IETF/RFC-8464/RFC-8464.txt"},{"from":"IETF RFC 8484","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-8484/RFC-8484.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8467","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 1705","to":"IETF RFC 847","kind":"references","source":"IETF/RFC-1705/RFC-1705.txt"},{"from":"IETF RFC 8740","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-8740/RFC-8740.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 8470","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 8472","to":"IETF RFC 8471","kind":"references","source":"IETF/RFC-8472/RFC-8472.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 8471","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 8471","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 8471","to":"IETF RFC 8472","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 8473","to":"IETF RFC 8472","kind":"references","source":"IETF/RFC-8473/RFC-8473.txt"},{"from":"IETF RFC 8471","to":"IETF RFC 8473","kind":"references","source":"IETF/RFC-8471/RFC-8471.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8474","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 8879","to":"IETF RFC 8478","kind":"references","source":"IETF/RFC-8879/RFC-8879.txt"},{"from":"IETF RFC 8490","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8490/RFC-8490.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8744","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8744/RFC-8744.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 8484","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8489","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8489","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8489","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8490","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8490","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 8767","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8767/RFC-8767.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8806","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8806/RFC-8806.txt"},{"from":"IETF RFC 8901","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8901/RFC-8901.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 8499","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 0850","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-0850/RFC-0850.txt"},{"from":"IETF RFC 0977","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-0977/RFC-0977.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 5536","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-5536/RFC-5536.txt"},{"from":"IETF RFC 7231","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-7231/RFC-7231.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 977","to":"IETF RFC 850","kind":"references","source":"IETF/RFC-977/RFC-977.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 851","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 852","to":"IETF RFC 851","kind":"references","source":"IETF/RFC-852/RFC-852.txt"},{"from":"IETF RFC 878","to":"IETF RFC 851","kind":"references","source":"IETF/RFC-878/RFC-878.txt"},{"from":"IETF RFC 991","to":"IETF RFC 851","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8511","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8512","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8512","to":"IETF RFC 8513","kind":"references","source":"IETF/RFC-8512/RFC-8512.txt"},{"from":"IETF RFC 8520","to":"IETF RFC 8519","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8519","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 852","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 851","to":"IETF RFC 852","kind":"references","source":"IETF/RFC-851/RFC-851.txt"},{"from":"IETF RFC 991","to":"IETF RFC 852","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8520","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8520","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 8521","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 8521","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 0854","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-0854/RFC-0854.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1091","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1091/RFC-1091.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1143","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1143/RFC-1143.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1207","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1207/RFC-1207.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1443","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1443/RFC-1443.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1646","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1646/RFC-1646.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1903","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1903/RFC-1903.txt"},{"from":"IETF RFC 1922","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1948","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1948/RFC-1948.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 2579","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2579/RFC-2579.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2941","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2941/RFC-2941.txt"},{"from":"IETF RFC 2946","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2946/RFC-2946.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 3169","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3780","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3993","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-3993/RFC-3993.txt"},{"from":"IETF RFC 4111","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-4111/RFC-4111.txt"},{"from":"IETF RFC 4251","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4580","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-4580/RFC-4580.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 5929","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-5929/RFC-5929.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6528","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-6528/RFC-6528.txt"},{"from":"IETF RFC 870","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 915","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 923","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 959","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 960","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 854","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1091","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-1091/RFC-1091.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2951","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-2951/RFC-2951.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 5920","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-5920/RFC-5920.txt"},{"from":"IETF RFC 880","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 855","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8551","to":"IETF RFC 8550","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8550","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 8550","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8689","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-8689/RFC-8689.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9051","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8551","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 8553","to":"IETF RFC 8552","kind":"references","source":"IETF/RFC-8553/RFC-8553.txt"},{"from":"IETF RFC 8572","to":"IETF RFC 8552","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 8552","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 8552","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8553","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8554","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9608","to":"IETF RFC 8555","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1646","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1646/RFC-1646.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 856","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 857","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8572","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 8915","to":"IETF RFC 8573","kind":"references","source":"IETF/RFC-8915/RFC-8915.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 858","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8768","to":"IETF RFC 8586","kind":"references","source":"IETF/RFC-8768/RFC-8768.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8586","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 859","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 860","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 861","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"legal:2026-1731","to":"IETF RFC 8610","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 8610","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 8610","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 8610","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 8613","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8613/RFC-8613.txt"},{"from":"IETF RFC 8618","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8618/RFC-8618.txt"},{"from":"IETF RFC 8742","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8742/RFC-8742.txt"},{"from":"IETF RFC 8746","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 8747","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8747/RFC-8747.txt"},{"from":"IETF RFC 8778","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8778/RFC-8778.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8610","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8612","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8612","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8612","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8903","to":"IETF RFC 8612","kind":"references","source":"IETF/RFC-8903/RFC-8903.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8612","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8974","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-8974/RFC-8974.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8613","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 8620","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8820","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-8820/RFC-8820.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8615","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8618","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8618","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 8696","to":"IETF RFC 8619","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2925","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-2925/RFC-2925.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4560","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-4560/RFC-4560.txt"},{"from":"IETF RFC 870","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 862","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8620","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8627","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8627","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 8627","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 8628","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 870","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 863","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 870","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 864","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 870","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 865","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 870","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 866","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 6020","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 7950","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 870","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 867","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0868","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-0868/RFC-0868.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1769","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-1769/RFC-1769.txt"},{"from":"IETF RFC 2030","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-2030/RFC-2030.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 7273","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-7273/RFC-7273.txt"},{"from":"IETF RFC 870","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 868","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 8689","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 900","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 869","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 8693","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8696","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 880","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 882","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 883","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 887","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-887/RFC-887.txt"},{"from":"IETF RFC 901","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 870","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 8705","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9126","to":"IETF RFC 8705","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 8705","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8705","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8705","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8705","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9068","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9126","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8707","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 880","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 901","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 871","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0872","to":"IETF RFC 872","kind":"references","source":"IETF/RFC-0872/RFC-0872.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 872","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 872","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 8725","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 9068","to":"IETF RFC 8725","kind":"references","source":"IETF/RFC-9068/RFC-9068.txt"},{"from":"IETF RFC 9101","to":"IETF RFC 8725","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8725","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8725","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 8725","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 8725","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 8738","to":"IETF RFC 8737","kind":"references","source":"IETF/RFC-8738/RFC-8738.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8738","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8740","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 8740","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8742","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8742","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8742","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8744","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 8949","to":"IETF RFC 8746","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8747","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 1683","to":"IETF RFC 875","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 8890","to":"IETF RFC 8752","kind":"references","source":"IETF/RFC-8890/RFC-8890.txt"},{"from":"IETF RFC 8914","to":"IETF RFC 8767","kind":"references","source":"IETF/RFC-8914/RFC-8914.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8768","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8768","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1183","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1183/RFC-1183.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1356","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1461","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 870","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 880","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-880/RFC-880.txt"},{"from":"IETF RFC 900","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 877","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 9019","to":"IETF RFC 8778","kind":"references","source":"IETF/RFC-9019/RFC-9019.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8778","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1546","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-1546/RFC-1546.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 900","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 878","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8783","to":"IETF RFC 8782","kind":"references","source":"IETF/RFC-8783/RFC-8783.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8782","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8903","to":"IETF RFC 8782","kind":"references","source":"IETF/RFC-8903/RFC-8903.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8782","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8782","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 8782","to":"IETF RFC 8783","kind":"references","source":"IETF/RFC-8782/RFC-8782.txt"},{"from":"IETF RFC 8811","to":"IETF RFC 8783","kind":"references","source":"IETF/RFC-8811/RFC-8811.txt"},{"from":"IETF RFC 8903","to":"IETF RFC 8783","kind":"references","source":"IETF/RFC-8903/RFC-8903.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8783","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8783","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF SD-JWT","to":"IETF RFC 8785","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 0879","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-0879/RFC-0879.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1134","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1171","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1188","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1332","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1332/RFC-1332.txt"},{"from":"IETF RFC 1390","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 2923","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-2923/RFC-2923.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4828","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-4828/RFC-4828.txt"},{"from":"IETF RFC 6145","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-6145/RFC-6145.txt"},{"from":"IETF RFC 6691","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-6691/RFC-6691.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7597","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-7597/RFC-7597.txt"},{"from":"IETF RFC 7599","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-7599/RFC-7599.txt"},{"from":"IETF RFC 901","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 879","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8791","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 8792","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 8792","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8792","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 8792","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8792","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 870","to":"IETF RFC 880","kind":"references","source":"IETF/RFC-870/RFC-870.txt"},{"from":"IETF RFC 8932","to":"IETF RFC 8806","kind":"references","source":"IETF/RFC-8932/RFC-8932.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8806","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 0881","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-0881/RFC-0881.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 3245","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-3245/RFC-3245.txt"},{"from":"IETF RFC 897","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-897/RFC-897.txt"},{"from":"IETF RFC 901","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 921","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-921/RFC-921.txt"},{"from":"IETF RFC 924","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 881","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8973","to":"IETF RFC 8811","kind":"references","source":"IETF/RFC-8973/RFC-8973.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8811","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 883","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-883/RFC-883.txt"},{"from":"IETF RFC 915","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 960","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 882","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 8820","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 9162","to":"IETF RFC 8820","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8820","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 8825","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8825","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 8825","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8825","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8826","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8826","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8826","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8826","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8826","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8827","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8826","to":"IETF RFC 8828","kind":"references","source":"IETF/RFC-8826/RFC-8826.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8828","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8828","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 8828","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8829","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 8829","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8829","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8829","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8829","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 0882","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-0882/RFC-0882.txt"},{"from":"IETF RFC 0883","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-0883/RFC-0883.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1002","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-1002/RFC-1002.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 882","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-882/RFC-882.txt"},{"from":"IETF RFC 915","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 960","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 883","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8830","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8830","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 8830","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8832","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 8831","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8832","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8832","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8832","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8832","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8834","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8834","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8828","to":"IETF RFC 8835","kind":"references","source":"IETF/RFC-8828/RFC-8828.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8836","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8837","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8838","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8838","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8838","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8863","to":"IETF RFC 8838","kind":"references","source":"IETF/RFC-8863/RFC-8863.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8839","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 900","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 930","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-930/RFC-930.txt"},{"from":"IETF RFC 943","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 884","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8840","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8838","to":"IETF RFC 8840","kind":"references","source":"IETF/RFC-8838/RFC-8838.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8840","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8831","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8831/RFC-8831.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 8841","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8842","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8842","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8842","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8852","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8852/RFC-8852.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8854","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8843","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8827","to":"IETF RFC 8844","kind":"references","source":"IETF/RFC-8827/RFC-8827.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8844","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8845","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8845","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8846","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8846","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8847","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8847","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8848","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8848","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8849","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1576","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1576/RFC-1576.txt"},{"from":"IETF RFC 1647","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1647/RFC-1647.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2066","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-2066/RFC-2066.txt"},{"from":"IETF RFC 2355","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-2355/RFC-2355.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 923","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 885","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 8847","to":"IETF RFC 8850","kind":"references","source":"IETF/RFC-8847/RFC-8847.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8850","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8850","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8851","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8851","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8852","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8852","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8852","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8853","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8851","to":"IETF RFC 8853","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8854","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8854","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8855","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8855","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8855","to":"IETF RFC 8856","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8856","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8858","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8858","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8858","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8858","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8829","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8829/RFC-8829.txt"},{"from":"IETF RFC 8830","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8830/RFC-8830.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8840","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8840/RFC-8840.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8842","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8842/RFC-8842.txt"},{"from":"IETF RFC 8843","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8858","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8858/RFC-8858.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8859","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8860","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8861","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8839","to":"IETF RFC 8863","kind":"references","source":"IETF/RFC-8839/RFC-8839.txt"},{"from":"IETF RFC 8841","to":"IETF RFC 8864","kind":"references","source":"IETF/RFC-8841/RFC-8841.txt"},{"from":"IETF RFC 8848","to":"IETF RFC 8864","kind":"references","source":"IETF/RFC-8848/RFC-8848.txt"},{"from":"IETF RFC 8850","to":"IETF RFC 8864","kind":"references","source":"IETF/RFC-8850/RFC-8850.txt"},{"from":"IETF RFC 8866","to":"IETF RFC 8864","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8873","to":"IETF RFC 8864","kind":"references","source":"IETF/RFC-8873/RFC-8873.txt"},{"from":"IETF RFC 8856","to":"IETF RFC 8866","kind":"references","source":"IETF/RFC-8856/RFC-8856.txt"},{"from":"IETF RFC 8859","to":"IETF RFC 8866","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8866","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 8866","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1382","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 900","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 887","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8834","to":"IETF RFC 8872","kind":"references","source":"IETF/RFC-8834/RFC-8834.txt"},{"from":"IETF RFC 8853","to":"IETF RFC 8872","kind":"references","source":"IETF/RFC-8853/RFC-8853.txt"},{"from":"IETF RFC 8864","to":"IETF RFC 8873","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 8879","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8879","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8879","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8879","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 1364","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1364/RFC-1364.txt"},{"from":"IETF RFC 1403","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1403/RFC-1403.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1745","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 900","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 888","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 901","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 889","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8890","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 8900","to":"IETF RFC 8899","kind":"references","source":"IETF/RFC-8900/RFC-8900.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8899","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 901","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 890","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 8899","to":"IETF RFC 8900","kind":"references","source":"IETF/RFC-8899/RFC-8899.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8901","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8903","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 900","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 891","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8914","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8914","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8914","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 8915","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 892","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 905","to":"IETF RFC 892","kind":"references","source":"IETF/RFC-905/RFC-905.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8926","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 901","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 893","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 8932","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8932","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9180","to":"IETF RFC 8937","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 8937","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 0894","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-0894/RFC-0894.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2507","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-2507/RFC-2507.txt"},{"from":"IETF RFC 3252","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4253","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4838","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-4838/RFC-4838.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 5692","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-5692/RFC-5692.txt"},{"from":"IETF RFC 5851","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6272","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 900","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 894","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 8941","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8941","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 8941","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 8941","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 8941","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"legal:2026-1731","to":"IETF RFC 8943","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"IETF RFC 9165","to":"IETF RFC 8943","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 8976","to":"IETF RFC 8945","kind":"references","source":"IETF/RFC-8976/RFC-8976.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8945","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9471","to":"IETF RFC 8945","kind":"references","source":"IETF/RFC-9471/RFC-9471.txt"},{"from":"IETF RFC 8948","to":"IETF RFC 8947","kind":"references","source":"IETF/RFC-8948/RFC-8948.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8947","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 8947","to":"IETF RFC 8948","kind":"references","source":"IETF/RFC-8947/RFC-8947.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8948","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"legal:2026-1731","to":"IETF RFC 8949","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"IETF RFC 9052","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9090","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9165","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9165/RFC-9165.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9542","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9542/RFC-9542.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 8949","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 900","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 901","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 923","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 895","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0896","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-0896/RFC-0896.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1016","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1016/RFC-1016.txt"},{"from":"IETF RFC 1072","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1072/RFC-1072.txt"},{"from":"IETF RFC 1254","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1254/RFC-1254.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 2126","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2309","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-2309/RFC-2309.txt"},{"from":"IETF RFC 2525","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-2525/RFC-2525.txt"},{"from":"IETF RFC 2556","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-2556/RFC-2556.txt"},{"from":"IETF RFC 2914","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-2914/RFC-2914.txt"},{"from":"IETF RFC 3539","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-3539/RFC-3539.txt"},{"from":"IETF RFC 3714","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 4138","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-4138/RFC-4138.txt"},{"from":"IETF RFC 4172","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-4172/RFC-4172.txt"},{"from":"IETF RFC 4413","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-4413/RFC-4413.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 4653","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-4653/RFC-4653.txt"},{"from":"IETF RFC 5044","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-5044/RFC-5044.txt"},{"from":"IETF RFC 5290","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-5290/RFC-5290.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5682","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-5682/RFC-5682.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 7560","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-7560/RFC-7560.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 8289","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-8289/RFC-8289.txt"},{"from":"IETF RFC 901","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 896","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 897","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 901","to":"IETF RFC 897","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 915","to":"IETF RFC 897","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 921","to":"IETF RFC 897","kind":"references","source":"IETF/RFC-921/RFC-921.txt"},{"from":"IETF RFC 9132","to":"IETF RFC 8973","kind":"references","source":"IETF/RFC-9132/RFC-9132.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 8974","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 8974","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 8976","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8981","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 8985","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 8996","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 8999","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 901","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-901/RFC-901.txt"},{"from":"IETF RFC 924","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 900","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9076","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9076/RFC-9076.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9175","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9175/RFC-9175.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9000","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 8999","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-8999/RFC-8999.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9002","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-9002/RFC-9002.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9001","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9000","to":"IETF RFC 9002","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9001","to":"IETF RFC 9002","kind":"references","source":"IETF/RFC-9001/RFC-9001.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 9002","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9002","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 9002","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 0900","to":"IETF RFC 901","kind":"references","source":"IETF/RFC-0900/RFC-0900.txt"},{"from":"IETF RFC 900","to":"IETF RFC 901","kind":"references","source":"IETF/RFC-900/RFC-900.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 9019","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 9021","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 0903","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-0903/RFC-0903.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1201","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1201/RFC-1201.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1374","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1374/RFC-1374.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1490","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2390","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-2390/RFC-2390.txt"},{"from":"IETF RFC 2427","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2834","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 7961","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 8519","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 906","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-906/RFC-906.txt"},{"from":"IETF RFC 923","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 960","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 903","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 9039","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1066","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1093","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1093/RFC-1093.txt"},{"from":"IETF RFC 1105","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1105/RFC-1105.txt"},{"from":"IETF RFC 1156","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1163","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1163/RFC-1163.txt"},{"from":"IETF RFC 1213","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1222","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1222/RFC-1222.txt"},{"from":"IETF RFC 1267","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1267/RFC-1267.txt"},{"from":"IETF RFC 1371","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1371/RFC-1371.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1654","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1752","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1771","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1930","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 1932","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2360","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-2360/RFC-2360.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 4271","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4632","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-4632/RFC-4632.txt"},{"from":"IETF RFC 924","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 904","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 1583","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1583/RFC-1583.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1981","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-1981/RFC-1981.txt"},{"from":"IETF RFC 2178","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-2178/RFC-2178.txt"},{"from":"IETF RFC 2328","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-2328/RFC-2328.txt"},{"from":"IETF RFC 2740","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-2740/RFC-2740.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 960","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 905","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9051","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 9052","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 9053","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9054","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9054/RFC-9054.txt"},{"from":"IETF RFC 9338","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9338/RFC-9338.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9052","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 9053","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9053","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 9054","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 906","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 906","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 906","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 5970","to":"IETF RFC 906","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 951","to":"IETF RFC 906","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9068","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9068","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9470","to":"IETF RFC 9068","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9068","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1191","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-1191/RFC-1191.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 924","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 907","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9103","to":"IETF RFC 9076","kind":"references","source":"IETF/RFC-9103/RFC-9103.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 9076","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1072","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1072/RFC-1072.txt"},{"from":"IETF RFC 1151","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1151/RFC-1151.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2757","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-2757/RFC-2757.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 909","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-909/RFC-909.txt"},{"from":"IETF RFC 923","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 908","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9083","to":"IETF RFC 9082","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 9082","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9082","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 9083","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9224","to":"IETF RFC 9083","kind":"references","source":"IETF/RFC-9224/RFC-9224.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9083","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 924","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 909","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 9090","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 9090","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"ARF TS12 V1.0.1","to":"IETF RFC 9101","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9101","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF RFC 9101","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"IETF RFC 9126","to":"IETF RFC 9101","kind":"references","source":"IETF/RFC-9126/RFC-9126.txt"},{"from":"IETF RFC 9207","to":"IETF RFC 9101","kind":"references","source":"IETF/RFC-9207/RFC-9207.txt"},{"from":"IETF RFC 9396","to":"IETF RFC 9101","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9101","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9250","to":"IETF RFC 9103","kind":"references","source":"IETF/RFC-9250/RFC-9250.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9103","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 9052","to":"IETF RFC 9106","kind":"references","source":"IETF/RFC-9052/RFC-9052.txt"},{"from":"IETF RFC 9380","to":"IETF RFC 9106","kind":"references","source":"IETF/RFC-9380/RFC-9380.txt"},{"from":"legal:2025-1929","to":"IETF RFC 9110","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9110","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9110","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9111","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9193","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9193/RFC-9193.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9209","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9209/RFC-9209.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9457","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 9470","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 9110","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 9110","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 9110","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9112","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9112/RFC-9112.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9111","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9111","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9111/RFC-9111.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9112","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 9113","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9110","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9110/RFC-9110.txt"},{"from":"IETF RFC 9204","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9204/RFC-9204.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 9218","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9218/RFC-9218.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 9460","to":"IETF RFC 9114","kind":"references","source":"IETF/RFC-9460/RFC-9460.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 923","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 931","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-931/RFC-931.txt"},{"from":"IETF RFC 943","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 912","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9126","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 9396","to":"IETF RFC 9126","kind":"references","source":"IETF/RFC-9396/RFC-9396.txt"},{"from":"IETF RFC 9449","to":"IETF RFC 9126","kind":"references","source":"IETF/RFC-9449/RFC-9449.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9126","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 923","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 943","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 960","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 913","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 9132","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 935","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-935/RFC-935.txt"},{"from":"IETF RFC 944","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 914","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9147","to":"IETF RFC 9146","kind":"references","source":"IETF/RFC-9147/RFC-9147.txt"},{"from":"IETF RFC 9053","to":"IETF RFC 9147","kind":"references","source":"IETF/RFC-9053/RFC-9053.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9147","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9345","to":"IETF RFC 9147","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9360","to":"IETF RFC 9147","kind":"references","source":"IETF/RFC-9360/RFC-9360.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9147","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 923","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 943","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 915","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 9155","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9155","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 935","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-935/RFC-935.txt"},{"from":"IETF RFC 944","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 916","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ARF TS05 V1.2.1","to":"IETF RFC 9162","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF RFC 9162","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 411-8 V1.1.1","to":"IETF RFC 9162","kind":"references","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf"},{"from":"IETF RFC 9325","to":"IETF RFC 9162","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 9165","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 9165","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9165","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9165","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 3789","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-3789/RFC-3789.txt"},{"from":"IETF RFC 924","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 917","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9177","to":"IETF RFC 9175","kind":"references","source":"IETF/RFC-9177/RFC-9177.txt"},{"from":"IETF RFC 9277","to":"IETF RFC 9177","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1081","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-1081/RFC-1081.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 923","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 924","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 937","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-937/RFC-937.txt"},{"from":"IETF RFC 943","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 918","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 9180","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9180","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 0919","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-0919/RFC-0919.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5405","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 6890","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-6890/RFC-6890.txt"},{"from":"IETF RFC 8085","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 8190","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-8190/RFC-8190.txt"},{"from":"IETF RFC 944","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 951","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-951/RFC-951.txt"},{"from":"IETF RFC 961","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 919","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9191","to":"IETF RFC 9190","kind":"references","source":"IETF/RFC-9191/RFC-9191.txt"},{"from":"IETF RFC 9190","to":"IETF RFC 9191","kind":"references","source":"IETF/RFC-9190/RFC-9190.txt"},{"from":"IETF RFC 9325","to":"IETF RFC 9191","kind":"references","source":"IETF/RFC-9325/RFC-9325.txt"},{"from":"IETF RFC 9876","to":"IETF RFC 9193","kind":"references","source":"IETF/RFC-9876/RFC-9876.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9193","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2240","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-2240/RFC-2240.txt"},{"from":"IETF RFC 924","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 987","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-987/RFC-987.txt"},{"from":"IETF RFC 991","to":"IETF RFC 920","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9114","to":"IETF RFC 9204","kind":"references","source":"IETF/RFC-9114/RFC-9114.txt"},{"from":"IETF RFC 9292","to":"IETF RFC 9204","kind":"references","source":"IETF/RFC-9292/RFC-9292.txt"},{"from":"IETF RFC 9440","to":"IETF RFC 9204","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 9205","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9207","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"IETF RFC 9700","to":"IETF RFC 9207","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9230","to":"IETF RFC 9209","kind":"references","source":"IETF/RFC-9230/RFC-9230.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 921","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 924","to":"IETF RFC 921","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 944","to":"IETF RFC 921","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 921","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 921","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9113","to":"IETF RFC 9218","kind":"references","source":"IETF/RFC-9113/RFC-9113.txt"},{"from":"IETF RFC 9205","to":"IETF RFC 9218","kind":"references","source":"IETF/RFC-9205/RFC-9205.txt"},{"from":"IETF RFC 0922","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-0922/RFC-0922.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1878","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-1878/RFC-1878.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 5735","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-5735/RFC-5735.txt"},{"from":"IETF RFC 6491","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-6491/RFC-6491.txt"},{"from":"IETF RFC 944","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 922","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9224","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 915","to":"IETF RFC 923","kind":"references","source":"IETF/RFC-915/RFC-915.txt"},{"from":"IETF RFC 924","to":"IETF RFC 923","kind":"references","source":"IETF/RFC-924/RFC-924.txt"},{"from":"IETF RFC 937","to":"IETF RFC 923","kind":"references","source":"IETF/RFC-937/RFC-937.txt"},{"from":"IETF RFC 944","to":"IETF RFC 923","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 923","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9230","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 923","to":"IETF RFC 924","kind":"references","source":"IETF/RFC-923/RFC-923.txt"},{"from":"IETF RFC 0925","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-0925/RFC-0925.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1931","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-1931/RFC-1931.txt"},{"from":"IETF RFC 2002","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-2002/RFC-2002.txt"},{"from":"IETF RFC 3220","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-3220/RFC-3220.txt"},{"from":"IETF RFC 3344","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-3344/RFC-3344.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5844","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-5844/RFC-5844.txt"},{"from":"IETF RFC 5944","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-5944/RFC-5944.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 944","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 925","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 9250","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9250","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 943","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 926","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 0927","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-0927/RFC-0927.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 4962","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-4962/RFC-4962.txt"},{"from":"IETF RFC 943","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 927","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9277","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 929","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-929/RFC-929.txt"},{"from":"IETF RFC 944","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 928","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 9285","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 928","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-928/RFC-928.txt"},{"from":"IETF RFC 944","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 929","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9292","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1079","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-1079/RFC-1079.txt"},{"from":"IETF RFC 1091","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-1091/RFC-1091.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 943","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 930","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1413","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-1413/RFC-1413.txt"},{"from":"IETF RFC 6872","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-6872/RFC-6872.txt"},{"from":"IETF RFC 944","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 931","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 932","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 944","to":"IETF RFC 932","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 932","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 932","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9325","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9325","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9325","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1116","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-1116/RFC-1116.txt"},{"from":"IETF RFC 1184","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-1184/RFC-1184.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 943","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 960","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 933","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9397","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9397/RFC-9397.txt"},{"from":"IETF RFC 9711","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9334","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 9393","to":"IETF RFC 9338","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9338","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 0989","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-0989/RFC-0989.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1153","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1153/RFC-1153.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1341","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1421","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1421/RFC-1421.txt"},{"from":"IETF RFC 1505","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2045","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2047","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2048","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-2048/RFC-2048.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 7468","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 987","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-987/RFC-987.txt"},{"from":"IETF RFC 989","to":"IETF RFC 934","kind":"references","source":"IETF/RFC-989/RFC-989.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9345","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 1547","to":"IETF RFC 935","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 936","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 944","to":"IETF RFC 936","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 936","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 936","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"legal:2026-1731","to":"IETF RFC 9360","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF RFC 9360","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF RFC 9360","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 9711","to":"IETF RFC 9360","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1064","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1064/RFC-1064.txt"},{"from":"IETF RFC 1081","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1081/RFC-1081.txt"},{"from":"IETF RFC 1176","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1176/RFC-1176.txt"},{"from":"IETF RFC 1203","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1203/RFC-1203.txt"},{"from":"IETF RFC 1225","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-1225/RFC-1225.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 943","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 937","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 943","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 944","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 960","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 938","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ARF TS14 V1.0","to":"IETF RFC 9380","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"IETF RFC 9711","to":"IETF RFC 9393","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9396","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9396","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9397","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 940","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1075","to":"IETF RFC 940","kind":"references","source":"IETF/RFC-1075/RFC-1075.txt"},{"from":"IETF RFC 944","to":"IETF RFC 940","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 961","to":"IETF RFC 940","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 940","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 941","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1237","to":"IETF RFC 941","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1629","to":"IETF RFC 941","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1154","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 944","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-944/RFC-944.txt"},{"from":"IETF RFC 959","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 961","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 943","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1131","to":"IETF RFC 944","kind":"references","source":"IETF/RFC-1131/RFC-1131.pdf"},{"from":"IETF RFC 1247","to":"IETF RFC 944","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 943","to":"IETF RFC 944","kind":"references","source":"IETF/RFC-943/RFC-943.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9440","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF RFC 9449","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9449","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9470","to":"IETF RFC 9449","kind":"references","source":"IETF/RFC-9470/RFC-9470.txt"},{"from":"IETF RFC 9700","to":"IETF RFC 9449","kind":"references","source":"IETF/RFC-9700/RFC-9700.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9449","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9458","to":"IETF RFC 9457","kind":"references","source":"IETF/RFC-9458/RFC-9458.txt"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 9457","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"W3C vc-data-model V1.1","to":"IETF RFC 9458","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 1010","to":"IETF RFC 946","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 946","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 946","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 960","to":"IETF RFC 946","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 990","to":"IETF RFC 946","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 9461","to":"IETF RFC 9460","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9460","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9525","to":"IETF RFC 9461","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9470","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 9471","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 960","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 948","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9535","to":"IETF RFC 9485","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 9741","to":"IETF RFC 9485","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 949","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 959","to":"IETF RFC 949","kind":"references","source":"IETF/RFC-959/RFC-959.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 9499","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 0950","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-0950/RFC-0950.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1002","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1002/RFC-1002.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1219","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1219/RFC-1219.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1287","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1287/RFC-1287.txt"},{"from":"IETF RFC 1349","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1349/RFC-1349.txt"},{"from":"IETF RFC 1395","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1395/RFC-1395.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1878","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-1878/RFC-1878.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2401","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-2401/RFC-2401.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 3021","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-3021/RFC-3021.txt"},{"from":"IETF RFC 3442","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-3442/RFC-3442.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4903","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-4903/RFC-4903.txt"},{"from":"IETF RFC 5942","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-5942/RFC-5942.txt"},{"from":"IETF RFC 6274","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-6274/RFC-6274.txt"},{"from":"IETF RFC 961","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 950","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0951","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-0951/RFC-0951.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1256","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1256/RFC-1256.txt"},{"from":"IETF RFC 1497","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1497/RFC-1497.txt"},{"from":"IETF RFC 1531","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1531/RFC-1531.txt"},{"from":"IETF RFC 1532","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1532/RFC-1532.txt"},{"from":"IETF RFC 1533","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1533/RFC-1533.txt"},{"from":"IETF RFC 1541","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1541/RFC-1541.txt"},{"from":"IETF RFC 1542","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1542/RFC-1542.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1933","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-1933/RFC-1933.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2131","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-2131/RFC-2131.txt"},{"from":"IETF RFC 2132","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-2132/RFC-2132.txt"},{"from":"IETF RFC 2893","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-2893/RFC-2893.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3002","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3396","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-3396/RFC-3396.txt"},{"from":"IETF RFC 3527","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-3527/RFC-3527.txt"},{"from":"IETF RFC 3790","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-3790/RFC-3790.txt"},{"from":"IETF RFC 4030","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-4030/RFC-4030.txt"},{"from":"IETF RFC 4173","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4388","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-4388/RFC-4388.txt"},{"from":"IETF RFC 4390","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-4390/RFC-4390.txt"},{"from":"IETF RFC 4947","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5494","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-5494/RFC-5494.txt"},{"from":"IETF RFC 6607","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-6607/RFC-6607.txt"},{"from":"IETF RFC 6632","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 6926","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-6926/RFC-6926.txt"},{"from":"IETF RFC 6994","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-6994/RFC-6994.txt"},{"from":"IETF RFC 7341","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-7341/RFC-7341.txt"},{"from":"IETF RFC 7724","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-7724/RFC-7724.txt"},{"from":"IETF RFC 960","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 951","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0952","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-0952/RFC-0952.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1459","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1459/RFC-1459.txt"},{"from":"IETF RFC 1649","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 2317","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-2317/RFC-2317.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3492","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-3492/RFC-3492.txt"},{"from":"IETF RFC 3731","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3986","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 4290","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-4290/RFC-4290.txt"},{"from":"IETF RFC 4702","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-4702/RFC-4702.txt"},{"from":"IETF RFC 4931","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 5731","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5890","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-5890/RFC-5890.txt"},{"from":"IETF RFC 5894","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-5894/RFC-5894.txt"},{"from":"IETF RFC 6021","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6055","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6365","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6698","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6885","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6885/RFC-6885.txt"},{"from":"IETF RFC 6991","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7482","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-7482/RFC-7482.txt"},{"from":"IETF RFC 7719","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-7719/RFC-7719.txt"},{"from":"IETF RFC 8499","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-8499/RFC-8499.txt"},{"from":"IETF RFC 8552","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-8552/RFC-8552.txt"},{"from":"IETF RFC 9082","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-9082/RFC-9082.txt"},{"from":"IETF RFC 9499","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-9499/RFC-9499.txt"},{"from":"IETF RFC 961","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 952","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9728","to":"IETF RFC 9525","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 961","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 953","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9535","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF SD-JWT VC","to":"IETF RFC 9535","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF RFC 0954","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-0954/RFC-0954.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1609","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1609/RFC-1609.txt"},{"from":"IETF RFC 1714","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1714/RFC-1714.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1834","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1834/RFC-1834.txt"},{"from":"IETF RFC 1835","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-1835/RFC-1835.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2167","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2167/RFC-2167.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2957","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2958","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-2958/RFC-2958.txt"},{"from":"IETF RFC 3467","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3707","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-3707/RFC-3707.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3912","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-3912/RFC-3912.txt"},{"from":"IETF RFC 3981","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 961","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 954","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9562","to":"IETF RFC 9542","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 1045","to":"IETF RFC 955","kind":"references","source":"IETF/RFC-1045/RFC-1045.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 956","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 961","to":"IETF RFC 956","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 956","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9562","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9711","to":"IETF RFC 9562","kind":"references","source":"IETF/RFC-9711/RFC-9711.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 957","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 961","to":"IETF RFC 957","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 957","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 960","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 961","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 990","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 958","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 0959","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-0959/RFC-0959.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1177","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1177/RFC-1177.txt"},{"from":"IETF RFC 1204","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1204/RFC-1204.txt"},{"from":"IETF RFC 1206","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1206/RFC-1206.txt"},{"from":"IETF RFC 1244","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1244/RFC-1244.txt"},{"from":"IETF RFC 1325","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1325/RFC-1325.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1408","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1408/RFC-1408.txt"},{"from":"IETF RFC 1415","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1440","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1440/RFC-1440.txt"},{"from":"IETF RFC 1521","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1572","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1572/RFC-1572.txt"},{"from":"IETF RFC 1579","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1579/RFC-1579.txt"},{"from":"IETF RFC 1594","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1594/RFC-1594.txt"},{"from":"IETF RFC 1630","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1630/RFC-1630.txt"},{"from":"IETF RFC 1639","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1639/RFC-1639.txt"},{"from":"IETF RFC 1704","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1704/RFC-1704.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1739","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1739/RFC-1739.txt"},{"from":"IETF RFC 1919","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1919/RFC-1919.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2074","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2074/RFC-2074.txt"},{"from":"IETF RFC 2101","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2101/RFC-2101.txt"},{"from":"IETF RFC 2130","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2228","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2228/RFC-2228.txt"},{"from":"IETF RFC 2246","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2246/RFC-2246.txt"},{"from":"IETF RFC 2389","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2389/RFC-2389.txt"},{"from":"IETF RFC 2428","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2428/RFC-2428.txt"},{"from":"IETF RFC 2577","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2577/RFC-2577.txt"},{"from":"IETF RFC 2585","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2585/RFC-2585.txt"},{"from":"IETF RFC 2592","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2592/RFC-2592.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2640","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2663","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2663/RFC-2663.txt"},{"from":"IETF RFC 2767","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2767/RFC-2767.txt"},{"from":"IETF RFC 2773","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2773/RFC-2773.txt"},{"from":"IETF RFC 2828","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3022","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3022/RFC-3022.txt"},{"from":"IETF RFC 3027","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3027/RFC-3027.txt"},{"from":"IETF RFC 3040","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3040/RFC-3040.txt"},{"from":"IETF RFC 3165","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3165/RFC-3165.txt"},{"from":"IETF RFC 3205","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3205/RFC-3205.txt"},{"from":"IETF RFC 3237","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3237/RFC-3237.txt"},{"from":"IETF RFC 3303","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3338","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3338/RFC-3338.txt"},{"from":"IETF RFC 3395","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3395/RFC-3395.txt"},{"from":"IETF RFC 3568","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3568/RFC-3568.txt"},{"from":"IETF RFC 3617","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3617/RFC-3617.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3927","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4217","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-4217/RFC-4217.txt"},{"from":"IETF RFC 4330","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-4330/RFC-4330.txt"},{"from":"IETF RFC 4501","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-4501/RFC-4501.txt"},{"from":"IETF RFC 4823","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-4823/RFC-4823.txt"},{"from":"IETF RFC 4949","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5024","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5198","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5218","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5382","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5382/RFC-5382.txt"},{"from":"IETF RFC 5485","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5607","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5694","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-5694/RFC-5694.txt"},{"from":"IETF RFC 6022","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6080","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6080/RFC-6080.txt"},{"from":"IETF RFC 6093","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6093/RFC-6093.txt"},{"from":"IETF RFC 6101","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6101/RFC-6101.txt"},{"from":"IETF RFC 6250","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6250/RFC-6250.txt"},{"from":"IETF RFC 6335","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-6335/RFC-6335.txt"},{"from":"IETF RFC 7605","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-7605/RFC-7605.txt"},{"from":"IETF RFC 7755","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-7755/RFC-7755.txt"},{"from":"IETF RFC 961","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 990","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 959","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 4840","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-4840/RFC-4840.txt"},{"from":"IETF RFC 961","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 980","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 991","to":"IETF RFC 960","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"IETF RFC 9608","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"IETF RFC 9608","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"IETF RFC 960","to":"IETF RFC 961","kind":"references","source":"IETF/RFC-960/RFC-960.txt"},{"from":"IETF RFC 980","to":"IETF RFC 961","kind":"references","source":"IETF/RFC-980/RFC-980.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 963","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 961","to":"IETF RFC 963","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 963","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0964","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-0964/RFC-0964.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 4614","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-4614/RFC-4614.txt"},{"from":"IETF RFC 7414","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-7414/RFC-7414.txt"},{"from":"IETF RFC 961","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-961/RFC-961.txt"},{"from":"IETF RFC 991","to":"IETF RFC 964","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 966","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 966","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 966","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1045","to":"IETF RFC 966","kind":"references","source":"IETF/RFC-1045/RFC-1045.txt"},{"from":"IETF RFC 991","to":"IETF RFC 966","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1045","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-1045/RFC-1045.txt"},{"from":"IETF RFC 1700","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 990","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 998","to":"IETF RFC 969","kind":"references","source":"IETF/RFC-998/RFC-998.txt"},{"from":"IETF RFC 0970","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-0970/RFC-0970.txt"},{"from":"IETF RFC 1016","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-1016/RFC-1016.txt"},{"from":"IETF RFC 1254","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-1254/RFC-1254.txt"},{"from":"IETF RFC 5783","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-5783/RFC-5783.txt"},{"from":"IETF RFC 7567","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-7567/RFC-7567.txt"},{"from":"IETF RFC 7806","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-7806/RFC-7806.txt"},{"from":"IETF RFC 8033","to":"IETF RFC 970","kind":"references","source":"IETF/RFC-8033/RFC-8033.txt"},{"from":"ETSI TS 119 478 V1.1.1","to":"IETF RFC 9700","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 9728","to":"IETF RFC 9700","kind":"references","source":"IETF/RFC-9728/RFC-9728.txt"},{"from":"IETF RFC 9781","to":"IETF RFC 9711","kind":"references","source":"IETF/RFC-9781/RFC-9781.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 9711","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9711","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 972","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 972","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 990","to":"IETF RFC 972","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 973","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 973","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 973","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 991","to":"IETF RFC 973","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 0974","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-0974/RFC-0974.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1032","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1032/RFC-1032.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1426","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1426/RFC-1426.txt"},{"from":"IETF RFC 1480","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1480/RFC-1480.txt"},{"from":"IETF RFC 1486","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1486/RFC-1486.txt"},{"from":"IETF RFC 1528","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1528/RFC-1528.txt"},{"from":"IETF RFC 1535","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1535/RFC-1535.txt"},{"from":"IETF RFC 1536","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1536/RFC-1536.txt"},{"from":"IETF RFC 1537","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1537/RFC-1537.txt"},{"from":"IETF RFC 1591","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1591/RFC-1591.txt"},{"from":"IETF RFC 1652","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1652/RFC-1652.txt"},{"from":"IETF RFC 1653","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1653/RFC-1653.txt"},{"from":"IETF RFC 1713","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1713/RFC-1713.txt"},{"from":"IETF RFC 1845","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1845/RFC-1845.txt"},{"from":"IETF RFC 1870","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1870/RFC-1870.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2052","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2052/RFC-2052.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2476","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2476/RFC-2476.txt"},{"from":"IETF RFC 2532","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2532/RFC-2532.txt"},{"from":"IETF RFC 2782","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2782/RFC-2782.txt"},{"from":"IETF RFC 2821","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2821/RFC-2821.txt"},{"from":"IETF RFC 2822","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2852","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-2852/RFC-2852.txt"},{"from":"IETF RFC 3974","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-3974/RFC-3974.txt"},{"from":"IETF RFC 4409","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-4409/RFC-4409.txt"},{"from":"IETF RFC 5321","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-5321/RFC-5321.txt"},{"from":"IETF RFC 5336","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 6950","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-6950/RFC-6950.txt"},{"from":"IETF RFC 991","to":"IETF RFC 974","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9741","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 975","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1093","to":"IETF RFC 975","kind":"references","source":"IETF/RFC-1093/RFC-1093.txt"},{"from":"IETF RFC 1136","to":"IETF RFC 975","kind":"references","source":"IETF/RFC-1136/RFC-1136.txt"},{"from":"IETF RFC 991","to":"IETF RFC 975","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1137","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1137/RFC-1137.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1530","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1912","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-1912/RFC-1912.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 987","to":"IETF RFC 976","kind":"references","source":"IETF/RFC-987/RFC-987.txt"},{"from":"IETF RFC 0977","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-0977/RFC-0977.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1392","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1392/RFC-1392.txt"},{"from":"IETF RFC 1580","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1580/RFC-1580.txt"},{"from":"IETF RFC 1630","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1630/RFC-1630.txt"},{"from":"IETF RFC 1738","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1738/RFC-1738.txt"},{"from":"IETF RFC 1945","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1983","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-1983/RFC-1983.txt"},{"from":"IETF RFC 2068","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2076","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2142","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2142/RFC-2142.txt"},{"from":"IETF RFC 2151","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2151/RFC-2151.txt"},{"from":"IETF RFC 2219","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2219/RFC-2219.txt"},{"from":"IETF RFC 2594","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2594/RFC-2594.txt"},{"from":"IETF RFC 2616","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2616/RFC-2616.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 2924","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 2980","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-2980/RFC-2980.txt"},{"from":"IETF RFC 3023","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3552","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3552/RFC-3552.txt"},{"from":"IETF RFC 3675","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3675/RFC-3675.txt"},{"from":"IETF RFC 3795","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3887","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3887/RFC-3887.txt"},{"from":"IETF RFC 3977","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 4086","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-4086/RFC-4086.txt"},{"from":"IETF RFC 990","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 977","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 9782","to":"IETF RFC 9781","kind":"references","source":"IETF/RFC-9782/RFC-9782.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9781","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9782","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 979","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 991","to":"IETF RFC 979","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1812","to":"IETF RFC 980","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 982","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1006","to":"IETF RFC 983","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 983","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 983","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 990","to":"IETF RFC 983","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 984","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 985","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 986","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1069","to":"IETF RFC 986","kind":"references","source":"IETF/RFC-1069/RFC-1069.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1026","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1026/RFC-1026.txt"},{"from":"IETF RFC 1120","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1120/RFC-1120.txt"},{"from":"IETF RFC 1137","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1137/RFC-1137.txt"},{"from":"IETF RFC 1138","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1160","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1274","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1274/RFC-1274.txt"},{"from":"IETF RFC 1327","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1360","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1405","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1405/RFC-1405.txt"},{"from":"IETF RFC 1506","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 2156","to":"IETF RFC 987","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 9999","to":"IETF RFC 9876","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1010","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-1010/RFC-1010.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1054","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-1054/RFC-1054.txt"},{"from":"IETF RFC 1166","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-1166/RFC-1166.txt"},{"from":"IETF RFC 2780","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-2780/RFC-2780.txt"},{"from":"IETF RFC 990","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 991","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 997","to":"IETF RFC 988","kind":"references","source":"IETF/RFC-997/RFC-997.txt"},{"from":"IETF RFC 0989","to":"IETF RFC 989","kind":"references","source":"IETF/RFC-0989/RFC-0989.txt"},{"from":"IETF RFC 5585","to":"IETF RFC 989","kind":"references","source":"IETF/RFC-5585/RFC-5585.txt"},{"from":"IETF RFC 1001","to":"IETF RFC 990","kind":"references","source":"IETF/RFC-1001/RFC-1001.txt"},{"from":"IETF RFC 1002","to":"IETF RFC 990","kind":"references","source":"IETF/RFC-1002/RFC-1002.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 990","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 991","to":"IETF RFC 990","kind":"references","source":"IETF/RFC-991/RFC-991.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 991","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 990","to":"IETF RFC 991","kind":"references","source":"IETF/RFC-990/RFC-990.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1131","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1131/RFC-1131.pdf"},{"from":"IETF RFC 1237","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1247","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1247/RFC-1247.txt"},{"from":"IETF RFC 1561","to":"IETF RFC 994","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 995","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1070","to":"IETF RFC 995","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1237","to":"IETF RFC 995","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 996","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 996","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 997","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 997","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1101","to":"IETF RFC 997","kind":"references","source":"IETF/RFC-1101/RFC-1101.txt"},{"from":"IETF RFC 1000","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1072","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1072/RFC-1072.txt"},{"from":"IETF RFC 1106","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1106/RFC-1106.txt"},{"from":"IETF RFC 1235","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1235/RFC-1235.txt"},{"from":"IETF RFC 1323","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1323/RFC-1323.txt"},{"from":"IETF RFC 1986","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-1986/RFC-1986.txt"},{"from":"IETF RFC 2018","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-2018/RFC-2018.txt"},{"from":"IETF RFC 2896","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-2896/RFC-2896.txt"},{"from":"IETF RFC 3794","to":"IETF RFC 998","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 7991","to":"IETF RFC 9999","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 7992","to":"IETF RFC 9999","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"legal:2026-1731","to":"IETF SD-JWT","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS05 V1.2.1","to":"IETF SD-JWT","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS10 V1.2","to":"IETF SD-JWT","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS11 V1.0.1","to":"IETF SD-JWT","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ARF TS12 V1.0.1","to":"IETF SD-JWT","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ARF TS13","to":"IETF SD-JWT","kind":"references","source":"ARF/TS13/TS13-V1.0.1.md"},{"from":"ARF TS14 V1.0","to":"IETF SD-JWT","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"IETF SD-JWT","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF SD-JWT VC","to":"IETF SD-JWT","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"W3C vc-data-model V1.1","to":"IETF SD-JWT","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"legal:2026-1731","to":"IETF SD-JWT VC","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS04 V1.0.1","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md"},{"from":"ARF TS05 V1.2.1","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS09 V1.1","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS09-V1.1/TS09-V1.1.md"},{"from":"ARF TS10 V1.2","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS11 V1.0.1","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ARF TS12 V1.0.1","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ARF TS13","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS13/TS13-V1.0.1.md"},{"from":"ARF TS14 V1.0","to":"IETF SD-JWT VC","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"IETF SD-JWT VC","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"IETF SD-JWT VC","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"IETF SD-JWT VC","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"IETF SD-JWT VC","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"IETF SD-JWT VC","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"IETF SD-JWT","to":"IETF SD-JWT VC","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"IETF RFC 2534","to":"ISO-IEC ISO 1000 V1992","kind":"references","source":"IETF/RFC-2534/RFC-2534.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1160","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1160/RFC-1160.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1328","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1328/RFC-1328.txt"},{"from":"IETF RFC 1360","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1360/RFC-1360.txt"},{"from":"IETF RFC 1405","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1405/RFC-1405.txt"},{"from":"IETF RFC 1488","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1488/RFC-1488.txt"},{"from":"IETF RFC 1494","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1495","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1495/RFC-1495.txt"},{"from":"IETF RFC 1496","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1496/RFC-1496.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1506","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1530","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1530/RFC-1530.txt"},{"from":"IETF RFC 1565","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1565/RFC-1565.txt"},{"from":"IETF RFC 1648","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1648/RFC-1648.txt"},{"from":"IETF RFC 1649","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1649/RFC-1649.txt"},{"from":"IETF RFC 1664","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1664/RFC-1664.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1766","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1766/RFC-1766.txt"},{"from":"IETF RFC 1801","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1801/RFC-1801.txt"},{"from":"IETF RFC 1836","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1836/RFC-1836.txt"},{"from":"IETF RFC 1838","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1838/RFC-1838.txt"},{"from":"IETF RFC 1911","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1911/RFC-1911.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2076","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2076/RFC-2076.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2163","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2163/RFC-2163.txt"},{"from":"IETF RFC 2248","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2248/RFC-2248.txt"},{"from":"IETF RFC 2249","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2249/RFC-2249.txt"},{"from":"IETF RFC 2252","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2294","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2294/RFC-2294.txt"},{"from":"IETF RFC 2421","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 3066","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 4021","to":"ISO-IEC ISO 10021","kind":"references","source":"IETF/RFC-4021/RFC-4021.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO 10021-2","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO 10021-2","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO 10021-2","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1465","to":"ISO-IEC ISO 10021-2","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO 10021-2","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO 10021-4","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO 10021-4","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO 10021-4","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO 10021-4","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1465","to":"ISO-IEC ISO 10021-6","kind":"references","source":"IETF/RFC-1465/RFC-1465.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 10021-6","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO 10021-7","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO 10021-7","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO 10021-7","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO 10021-7","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 10021-7","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1494","to":"ISO-IEC ISO 10021-8","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 10021-8","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 10021-8","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 10035","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 10036","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 10039","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 2527","to":"ISO-IEC ISO 100646-1","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 3647","to":"ISO-IEC ISO 100646-1","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 10118-1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 10118-1","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 10118-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 10118-2","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 10118-3","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 10118-3","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 10118-4","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 10118-4","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 10160","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 10165-4","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 10175","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 10180","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 10180","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 10181-5","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 105","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1195","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1377","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1526","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2966","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-2966/RFC-2966.txt"},{"from":"IETF RFC 3359","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3359/RFC-3359.txt"},{"from":"IETF RFC 3373","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3373/RFC-3373.txt"},{"from":"IETF RFC 3439","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3439/RFC-3439.txt"},{"from":"IETF RFC 3567","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3719","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3784","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 4444","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4593","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4971","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 5029","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5073","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5120","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5120/RFC-5120.txt"},{"from":"IETF RFC 5130","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5302","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5303","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5304","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5305","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5308","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5309","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 6325","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6822","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7752","to":"ISO-IEC ISO 10589 V2002","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 2044","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2459","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3280","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 4103","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO 10646-1 V1993","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 10646-2","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1342","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1342/RFC-1342.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1489","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1489/RFC-1489.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1522","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1522/RFC-1522.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 1815","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1890","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1942","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-1942/RFC-1942.txt"},{"from":"IETF RFC 2000","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2000/RFC-2000.txt"},{"from":"IETF RFC 2044","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2047","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2047/RFC-2047.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2192","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2192/RFC-2192.txt"},{"from":"IETF RFC 2218","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 2244","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2251","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2254","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2261","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2261/RFC-2261.txt"},{"from":"IETF RFC 2271","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2271/RFC-2271.txt"},{"from":"IETF RFC 2277","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2284","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2284/RFC-2284.txt"},{"from":"IETF RFC 2287","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2287/RFC-2287.txt"},{"from":"IETF RFC 2291","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2295","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2295/RFC-2295.txt"},{"from":"IETF RFC 2326","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2376","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2384","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2384/RFC-2384.txt"},{"from":"IETF RFC 2396","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2396/RFC-2396.txt"},{"from":"IETF RFC 2400","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2400/RFC-2400.txt"},{"from":"IETF RFC 2440","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2444","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2444/RFC-2444.txt"},{"from":"IETF RFC 2445","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2459","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2482","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2484","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2484/RFC-2484.txt"},{"from":"IETF RFC 2516","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2516/RFC-2516.txt"},{"from":"IETF RFC 2518","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2543","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2571","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2571/RFC-2571.txt"},{"from":"IETF RFC 2595","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2595/RFC-2595.txt"},{"from":"IETF RFC 2596","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2596/RFC-2596.txt"},{"from":"IETF RFC 2608","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2609","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2609/RFC-2609.txt"},{"from":"IETF RFC 2610","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2610/RFC-2610.txt"},{"from":"IETF RFC 2614","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2614/RFC-2614.txt"},{"from":"IETF RFC 2624","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2634","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2634/RFC-2634.txt"},{"from":"IETF RFC 2640","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2662","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2662/RFC-2662.txt"},{"from":"IETF RFC 2683","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2683/RFC-2683.txt"},{"from":"IETF RFC 2718","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2718/RFC-2718.txt"},{"from":"IETF RFC 2720","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2720/RFC-2720.txt"},{"from":"IETF RFC 2730","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2730/RFC-2730.txt"},{"from":"IETF RFC 2776","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2776/RFC-2776.txt"},{"from":"IETF RFC 2781","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2793","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2803","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2803/RFC-2803.txt"},{"from":"IETF RFC 2829","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2829/RFC-2829.txt"},{"from":"IETF RFC 2847","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2847/RFC-2847.txt"},{"from":"IETF RFC 2865","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2866","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2866/RFC-2866.txt"},{"from":"IETF RFC 2869","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2869/RFC-2869.txt"},{"from":"IETF RFC 2898","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2957","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2957/RFC-2957.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3010","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3023","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3028","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3028/RFC-3028.txt"},{"from":"IETF RFC 3060","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3060/RFC-3060.txt"},{"from":"IETF RFC 3075","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3076","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3076/RFC-3076.txt"},{"from":"IETF RFC 3080","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3080/RFC-3080.txt"},{"from":"IETF RFC 3111","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3111/RFC-3111.txt"},{"from":"IETF RFC 3162","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3162/RFC-3162.txt"},{"from":"IETF RFC 3252","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3252/RFC-3252.txt"},{"from":"IETF RFC 3253","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3253/RFC-3253.txt"},{"from":"IETF RFC 3261","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3275","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3280","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3318","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3318/RFC-3318.txt"},{"from":"IETF RFC 3320","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3320/RFC-3320.txt"},{"from":"IETF RFC 3383","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3403","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3403/RFC-3403.txt"},{"from":"IETF RFC 3411","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3411/RFC-3411.txt"},{"from":"IETF RFC 3435","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3435/RFC-3435.txt"},{"from":"IETF RFC 3454","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3454/RFC-3454.txt"},{"from":"IETF RFC 3467","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3470","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3470/RFC-3470.txt"},{"from":"IETF RFC 3485","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3485/RFC-3485.txt"},{"from":"IETF RFC 3508","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3520","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3530","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3536","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3546","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3550","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3550/RFC-3550.txt"},{"from":"IETF RFC 3579","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3579/RFC-3579.txt"},{"from":"IETF RFC 3588","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3588/RFC-3588.txt"},{"from":"IETF RFC 3629","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3650","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3651","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3651/RFC-3651.txt"},{"from":"IETF RFC 3652","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3652/RFC-3652.txt"},{"from":"IETF RFC 3720","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3720/RFC-3720.txt"},{"from":"IETF RFC 3722","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3730","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3730/RFC-3730.txt"},{"from":"IETF RFC 3731","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3731/RFC-3731.txt"},{"from":"IETF RFC 3732","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3732/RFC-3732.txt"},{"from":"IETF RFC 3733","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3735","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3735/RFC-3735.txt"},{"from":"IETF RFC 3744","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3744/RFC-3744.txt"},{"from":"IETF RFC 3748","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3748/RFC-3748.txt"},{"from":"IETF RFC 3780","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3780/RFC-3780.txt"},{"from":"IETF RFC 3795","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3862","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3868","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3920","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3922","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3922/RFC-3922.txt"},{"from":"IETF RFC 3931","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3931/RFC-3931.txt"},{"from":"IETF RFC 3977","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 3981","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3981/RFC-3981.txt"},{"from":"IETF RFC 3986","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4005","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4011","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4043","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4103","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4108","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4108/RFC-4108.txt"},{"from":"IETF RFC 4145","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4145/RFC-4145.txt"},{"from":"IETF RFC 4173","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4173/RFC-4173.txt"},{"from":"IETF RFC 4185","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4185/RFC-4185.txt"},{"from":"IETF RFC 4186","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4186/RFC-4186.txt"},{"from":"IETF RFC 4187","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4187/RFC-4187.txt"},{"from":"IETF RFC 4210","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4251","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4251/RFC-4251.txt"},{"from":"IETF RFC 4252","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4253","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4253/RFC-4253.txt"},{"from":"IETF RFC 4254","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4254/RFC-4254.txt"},{"from":"IETF RFC 4256","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4279","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4279/RFC-4279.txt"},{"from":"IETF RFC 4310","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4310/RFC-4310.txt"},{"from":"IETF RFC 4314","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4314/RFC-4314.txt"},{"from":"IETF RFC 4329","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4329/RFC-4329.txt"},{"from":"IETF RFC 4354","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4354/RFC-4354.txt"},{"from":"IETF RFC 4366","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4422","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4422/RFC-4422.txt"},{"from":"IETF RFC 4462","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4463","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4505","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4505/RFC-4505.txt"},{"from":"IETF RFC 4511","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4512","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4513","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4513/RFC-4513.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4515","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4516","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4516/RFC-4516.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4520","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4535","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4535/RFC-4535.txt"},{"from":"IETF RFC 4566","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4570","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4570/RFC-4570.txt"},{"from":"IETF RFC 4575","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4575/RFC-4575.txt"},{"from":"IETF RFC 4582","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4582/RFC-4582.txt"},{"from":"IETF RFC 4616","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4616/RFC-4616.txt"},{"from":"IETF RFC 4622","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4622/RFC-4622.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4675","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4675/RFC-4675.txt"},{"from":"IETF RFC 4676","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4712","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4712/RFC-4712.txt"},{"from":"IETF RFC 4716","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4716/RFC-4716.txt"},{"from":"IETF RFC 4752","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4752/RFC-4752.txt"},{"from":"IETF RFC 4776","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 4790","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4790/RFC-4790.txt"},{"from":"IETF RFC 4793","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4793/RFC-4793.txt"},{"from":"IETF RFC 4807","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4807/RFC-4807.txt"},{"from":"IETF RFC 4825","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4825/RFC-4825.txt"},{"from":"IETF RFC 4880","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 4918","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4918/RFC-4918.txt"},{"from":"IETF RFC 4930","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4930/RFC-4930.txt"},{"from":"IETF RFC 4931","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4931/RFC-4931.txt"},{"from":"IETF RFC 4932","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4932/RFC-4932.txt"},{"from":"IETF RFC 4933","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4933/RFC-4933.txt"},{"from":"IETF RFC 4952","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4952/RFC-4952.txt"},{"from":"IETF RFC 4975","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-4975/RFC-4975.txt"},{"from":"IETF RFC 5023","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5023/RFC-5023.txt"},{"from":"IETF RFC 5024","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5035","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5035/RFC-5035.txt"},{"from":"IETF RFC 5051","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5051/RFC-5051.txt"},{"from":"IETF RFC 5055","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 5092","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5092/RFC-5092.txt"},{"from":"IETF RFC 5122","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5122/RFC-5122.txt"},{"from":"IETF RFC 5137","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5147","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5147/RFC-5147.txt"},{"from":"IETF RFC 5149","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5149/RFC-5149.txt"},{"from":"IETF RFC 5173","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5173/RFC-5173.txt"},{"from":"IETF RFC 5194","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 5198","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5209","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5209/RFC-5209.txt"},{"from":"IETF RFC 5228","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5228/RFC-5228.txt"},{"from":"IETF RFC 5229","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5229/RFC-5229.txt"},{"from":"IETF RFC 5255","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5255/RFC-5255.txt"},{"from":"IETF RFC 5256","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5256/RFC-5256.txt"},{"from":"IETF RFC 5257","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5257/RFC-5257.txt"},{"from":"IETF RFC 5261","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5261/RFC-5261.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5335","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5335/RFC-5335.txt"},{"from":"IETF RFC 5336","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5336/RFC-5336.txt"},{"from":"IETF RFC 5337","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5337/RFC-5337.txt"},{"from":"IETF RFC 5357","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5357/RFC-5357.txt"},{"from":"IETF RFC 5388","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5388/RFC-5388.txt"},{"from":"IETF RFC 5389","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5389/RFC-5389.txt"},{"from":"IETF RFC 5415","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5415/RFC-5415.txt"},{"from":"IETF RFC 5421","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5421/RFC-5421.txt"},{"from":"IETF RFC 5422","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5422/RFC-5422.txt"},{"from":"IETF RFC 5424","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5424/RFC-5424.txt"},{"from":"IETF RFC 5429","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5429/RFC-5429.txt"},{"from":"IETF RFC 5437","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5437/RFC-5437.txt"},{"from":"IETF RFC 5456","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5466","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5466/RFC-5466.txt"},{"from":"IETF RFC 5504","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5504/RFC-5504.txt"},{"from":"IETF RFC 5537","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5537/RFC-5537.txt"},{"from":"IETF RFC 5545","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5545/RFC-5545.txt"},{"from":"IETF RFC 5547","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5547/RFC-5547.txt"},{"from":"IETF RFC 5607","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5607/RFC-5607.txt"},{"from":"IETF RFC 5610","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5610/RFC-5610.txt"},{"from":"IETF RFC 5626","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5626/RFC-5626.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5661","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5661/RFC-5661.txt"},{"from":"IETF RFC 5675","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5675/RFC-5675.txt"},{"from":"IETF RFC 5676","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5676/RFC-5676.txt"},{"from":"IETF RFC 5698","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5698/RFC-5698.txt"},{"from":"IETF RFC 5703","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5703/RFC-5703.txt"},{"from":"IETF RFC 5721","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5721/RFC-5721.txt"},{"from":"IETF RFC 5730","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5730/RFC-5730.txt"},{"from":"IETF RFC 5731","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5731/RFC-5731.txt"},{"from":"IETF RFC 5732","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5732/RFC-5732.txt"},{"from":"IETF RFC 5733","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5733/RFC-5733.txt"},{"from":"IETF RFC 5738","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5738/RFC-5738.txt"},{"from":"IETF RFC 5760","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5760/RFC-5760.txt"},{"from":"IETF RFC 5792","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5792/RFC-5792.txt"},{"from":"IETF RFC 5793","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5793/RFC-5793.txt"},{"from":"IETF RFC 5801","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5801/RFC-5801.txt"},{"from":"IETF RFC 5802","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5802/RFC-5802.txt"},{"from":"IETF RFC 5804","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5804/RFC-5804.txt"},{"from":"IETF RFC 5837","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5837/RFC-5837.txt"},{"from":"IETF RFC 5849","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5849/RFC-5849.txt"},{"from":"IETF RFC 5878","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5878/RFC-5878.txt"},{"from":"IETF RFC 5910","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5910/RFC-5910.txt"},{"from":"IETF RFC 5914","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5970","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5970/RFC-5970.txt"},{"from":"IETF RFC 5987","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6020","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6031","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6047","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6047/RFC-6047.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6063","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6068","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6068/RFC-6068.txt"},{"from":"IETF RFC 6120","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6122","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6124","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6124/RFC-6124.txt"},{"from":"IETF RFC 6158","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6158/RFC-6158.txt"},{"from":"IETF RFC 6230","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6230/RFC-6230.txt"},{"from":"IETF RFC 6241","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6241/RFC-6241.txt"},{"from":"IETF RFC 6244","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 6265","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6265/RFC-6265.txt"},{"from":"IETF RFC 6272","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6272/RFC-6272.txt"},{"from":"IETF RFC 6283","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6283/RFC-6283.txt"},{"from":"IETF RFC 6320","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6331","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 6350","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 6376","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6376/RFC-6376.txt"},{"from":"IETF RFC 6396","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 6455","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6455/RFC-6455.txt"},{"from":"IETF RFC 6530","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6530/RFC-6530.txt"},{"from":"IETF RFC 6531","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6531/RFC-6531.txt"},{"from":"IETF RFC 6532","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6532/RFC-6532.txt"},{"from":"IETF RFC 6533","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6533/RFC-6533.txt"},{"from":"IETF RFC 6570","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6570/RFC-6570.txt"},{"from":"IETF RFC 6657","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6657/RFC-6657.txt"},{"from":"IETF RFC 6678","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6678/RFC-6678.txt"},{"from":"IETF RFC 6679","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6679/RFC-6679.txt"},{"from":"IETF RFC 6690","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6690/RFC-6690.txt"},{"from":"IETF RFC 6733","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6733/RFC-6733.txt"},{"from":"IETF RFC 6749","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6749/RFC-6749.txt"},{"from":"IETF RFC 6757","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6757/RFC-6757.txt"},{"from":"IETF RFC 6760","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6760/RFC-6760.txt"},{"from":"IETF RFC 6762","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6762/RFC-6762.txt"},{"from":"IETF RFC 6763","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6763/RFC-6763.txt"},{"from":"IETF RFC 6787","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6838","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6838/RFC-6838.txt"},{"from":"IETF RFC 6855","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6855/RFC-6855.txt"},{"from":"IETF RFC 6856","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 6857","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6857/RFC-6857.txt"},{"from":"IETF RFC 6901","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-6901/RFC-6901.txt"},{"from":"IETF RFC 7011","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7011/RFC-7011.txt"},{"from":"IETF RFC 7049","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7170","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7227","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7227/RFC-7227.txt"},{"from":"IETF RFC 7252","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7252/RFC-7252.txt"},{"from":"IETF RFC 7254","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7254/RFC-7254.txt"},{"from":"IETF RFC 7301","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7301/RFC-7301.txt"},{"from":"IETF RFC 7303","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7303/RFC-7303.txt"},{"from":"IETF RFC 7464","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7464/RFC-7464.txt"},{"from":"IETF RFC 7483","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7483/RFC-7483.txt"},{"from":"IETF RFC 7493","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7515","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7516","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7516/RFC-7516.txt"},{"from":"IETF RFC 7517","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 7518","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7518/RFC-7518.txt"},{"from":"IETF RFC 7530","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7530/RFC-7530.txt"},{"from":"IETF RFC 7542","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7542/RFC-7542.txt"},{"from":"IETF RFC 7564","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7564/RFC-7564.txt"},{"from":"IETF RFC 7572","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7572/RFC-7572.txt"},{"from":"IETF RFC 7613","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7613/RFC-7613.txt"},{"from":"IETF RFC 7616","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7616/RFC-7616.txt"},{"from":"IETF RFC 7617","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 7622","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7622/RFC-7622.txt"},{"from":"IETF RFC 7643","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7643/RFC-7643.txt"},{"from":"IETF RFC 7644","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7644/RFC-7644.txt"},{"from":"IETF RFC 7797","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7797/RFC-7797.txt"},{"from":"IETF RFC 7800","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7800/RFC-7800.txt"},{"from":"IETF RFC 7804","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7804/RFC-7804.txt"},{"from":"IETF RFC 7826","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 7839","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7839/RFC-7839.txt"},{"from":"IETF RFC 7941","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7941/RFC-7941.txt"},{"from":"IETF RFC 7950","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 7970","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 7992","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7992/RFC-7992.txt"},{"from":"IETF RFC 7994","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-7994/RFC-7994.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8089","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8089/RFC-8089.txt"},{"from":"IETF RFC 8187","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8187/RFC-8187.txt"},{"from":"IETF RFC 8188","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8188/RFC-8188.txt"},{"from":"IETF RFC 8225","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8225/RFC-8225.txt"},{"from":"IETF RFC 8259","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8259/RFC-8259.txt"},{"from":"IETF RFC 8264","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8264/RFC-8264.txt"},{"from":"IETF RFC 8265","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8265/RFC-8265.txt"},{"from":"IETF RFC 8398","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8398/RFC-8398.txt"},{"from":"IETF RFC 8399","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8399/RFC-8399.txt"},{"from":"IETF RFC 8412","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8415","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8415/RFC-8415.txt"},{"from":"IETF RFC 8417","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8417/RFC-8417.txt"},{"from":"IETF RFC 8428","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8461","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8461/RFC-8461.txt"},{"from":"IETF RFC 8489","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 8520","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8520/RFC-8520.txt"},{"from":"IETF RFC 8555","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8555/RFC-8555.txt"},{"from":"IETF RFC 8610","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 8620","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8620/RFC-8620.txt"},{"from":"IETF RFC 8832","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8832/RFC-8832.txt"},{"from":"IETF RFC 8843","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8843/RFC-8843.txt"},{"from":"IETF RFC 8855","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8855/RFC-8855.txt"},{"from":"IETF RFC 8864","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8864/RFC-8864.txt"},{"from":"IETF RFC 8866","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 8941","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8941/RFC-8941.txt"},{"from":"IETF RFC 8949","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9000","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9000/RFC-9000.txt"},{"from":"IETF RFC 9051","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9051/RFC-9051.txt"},{"from":"IETF RFC 9083","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9083/RFC-9083.txt"},{"from":"IETF RFC 9101","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 9277","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9393","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9461","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9461/RFC-9461.txt"},{"from":"IETF RFC 9485","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9485/RFC-9485.txt"},{"from":"IETF RFC 9535","to":"ISO-IEC ISO 10646 V1993","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 4444","to":"ISO-IEC ISO 10733","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 10736","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1745","to":"ISO-IEC ISO 10747","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 5065","to":"ISO-IEC ISO 10747","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 10918-1","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 11172","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 11172","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 11172","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 3645","to":"ISO-IEC ISO 11578","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 11586","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 11586","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 12083 V1993","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 12083 V1993","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 128-20","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 128-71","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5941","to":"ISO-IEC ISO 13616","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 5941","to":"ISO-IEC ISO 13616-1 V2007","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 3819","to":"ISO-IEC ISO 13818","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4326","to":"ISO-IEC ISO 13818-1","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4947","to":"ISO-IEC ISO 13818-1","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 2326","to":"ISO-IEC ISO 13818-6","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 13888-1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 7995","to":"ISO-IEC ISO 14289-1","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 3640","to":"ISO-IEC ISO 14496","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"ISO-IEC ISO 14533-4","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"legal:2025-2162","to":"ISO-IEC ISO 14641","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO 14641-1 V2018","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"legal:2025-2162","to":"ISO-IEC ISO 14721 V2025","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2025-2532","to":"ISO-IEC ISO 14721 V2025","kind":"cites","source":"implementing-acts/2025-2532/2025-2532.md"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO 14721 V2025","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 14888-1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 14888-1","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 14888-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 14888-2","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO 14888-3","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 14888-3","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 14888-3","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 148881-1","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO 15000","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO 15000","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO 15000-2 V2021","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO 15000-3 V2023","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO 15000-3 V2023","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"ISO-IEC ISO 15489-1 V2001","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"IETF RFC 3819","to":"ISO-IEC ISO 15802-3","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3114","to":"ISO-IEC ISO 15816","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3282","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 4645","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4676","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-4676/RFC-4676.txt"},{"from":"IETF RFC 4776","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-4776/RFC-4776.txt"},{"from":"IETF RFC 5645","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 15924 V2004","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 3778","to":"ISO-IEC ISO 15930","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"IETF RFC 3778","to":"ISO-IEC ISO 15930-1 V2001","kind":"references","source":"IETF/RFC-3778/RFC-3778.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO 15946","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 15946-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO 16363 V2011","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 7995","to":"ISO-IEC ISO 16684-1","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"ISO-IEC ISO 17442","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ARF TS02 V1.0.1","to":"ISO-IEC ISO 17442-1 V2020","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI TS 119 475 V1.2.1","to":"ISO-IEC ISO 17442-1 V2020","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO 17442-1 V2020","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 1745","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 17799","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 9285","to":"ISO-IEC ISO 18004","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"ARF TS13","to":"ISO-IEC ISO 18013-5","kind":"references","source":"ARF/TS13-V1.0.1/TS13-V1.0.1.md"},{"from":"ARF TS14 V1.0","to":"ISO-IEC ISO 18013-5","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"ISO-IEC ISO 18013-5","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO 18013-7","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO 18033","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO 18045","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO 18370-2 V2016","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO 19005","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"IETF RFC 7995","to":"ISO-IEC ISO 19005-2","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7995","to":"ISO-IEC ISO 19005-3","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 7970","to":"ISO-IEC ISO 19770","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 9393","to":"ISO-IEC ISO 19770-2 V2015","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"legal:2024-2977","to":"ISO-IEC ISO 19794-5","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"IETF RFC 1292","to":"ISO-IEC ISO 1988","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO 20008-2","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ARF TS12 V1.0.1","to":"ISO-IEC ISO 20022","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 20022","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 8412","to":"ISO-IEC ISO 2009","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 8412","to":"ISO-IEC ISO 2015","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 1468","to":"ISO-IEC ISO 2022-1986","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1554","to":"ISO-IEC ISO 2022-1986","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1557","to":"ISO-IEC ISO 2022-1986","kind":"references","source":"IETF/RFC-1557/RFC-1557.txt"},{"from":"IETF RFC 1815","to":"ISO-IEC ISO 2022-1986","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO 2022-1986","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1428","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1468","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1554","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1557","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1557/RFC-1557.txt"},{"from":"IETF RFC 1815","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2045","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2822","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2822/RFC-2822.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3536","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 4120","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 2022 V1986","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 2047","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 2288","to":"ISO-IEC ISO 2108 V1992","kind":"references","source":"IETF/RFC-2288/RFC-2288.txt"},{"from":"IETF RFC 3187","to":"ISO-IEC ISO 2108 V1992","kind":"references","source":"IETF/RFC-3187/RFC-3187.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 216","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2346","to":"ISO-IEC ISO 216","kind":"references","source":"IETF/RFC-2346/RFC-2346.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 216","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 216","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 216","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO 22301","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO 22313","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO 23220-2","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TS 119 471 V1.1.1","to":"ISO-IEC ISO 23220-2","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO 23220-7","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO 23257 V2022","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2025-2531","to":"ISO-IEC ISO 23257 V2022","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 2375","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 2375","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 2382-2 V1976","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 7669","to":"ISO-IEC ISO 26324 V2012","kind":"references","source":"IETF/RFC-7669/RFC-7669.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 269","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 269","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 269","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 269","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 8141","to":"ISO-IEC ISO 27729 V2012","kind":"references","source":"IETF/RFC-8141/RFC-8141.txt"},{"from":"ETSI EN 319 521 V1.1.1","to":"ISO-IEC ISO 29115","kind":"references","source":"ETSI/EN-319-521-V1.1.1/EN-319-521-V1.1.1.pdf"},{"from":"legal:2024-2977","to":"ISO-IEC ISO 3166","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2026-1731","to":"ISO-IEC ISO 3166","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2024-2977","to":"ISO-IEC ISO 3166-1 V2006","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2025-848","to":"ISO-IEC ISO 3166-1 V2006","kind":"cites","source":"implementing-acts/2025-848/2025-848.md"},{"from":"legal:2026-1731","to":"ISO-IEC ISO 3166-1 V2006","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"legal:2025-2164","to":"ISO-IEC ISO 3166-1 V2006","kind":"cites","source":"implementing-decisions/2025-2164/2025-2164.md"},{"from":"legal:2024-2977","to":"ISO-IEC ISO 3166-2 V2020","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2026-1731","to":"ISO-IEC ISO 3166-2 V2020","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"IETF RFC 3367","to":"ISO-IEC ISO 3166-2 V2020","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 5139","to":"ISO-IEC ISO 3166-2 V2020","kind":"references","source":"IETF/RFC-5139/RFC-5139.txt"},{"from":"ETSI EN 319 142-1 V1.2.1","to":"ISO-IEC ISO 32000-1 V2008","kind":"references","source":"ETSI/EN-319-142-1-V1.2.1/EN-319-142-1-V1.2.1.pdf"},{"from":"ETSI TS 119 102-2 V1.4.1","to":"ISO-IEC ISO 32000-1 V2008","kind":"references","source":"ETSI/TS-119-102-2-V1.4.1/TS-119-102-2-V1.4.1.pdf"},{"from":"IETF RFC 7995","to":"ISO-IEC ISO 32000-1 V2008","kind":"references","source":"IETF/RFC-7995/RFC-7995.txt"},{"from":"IETF RFC 3044","to":"ISO-IEC ISO 3279","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 2288","to":"ISO-IEC ISO 3297 V1986","kind":"references","source":"IETF/RFC-2288/RFC-2288.txt"},{"from":"IETF RFC 3044","to":"ISO-IEC ISO 3297 V1986","kind":"references","source":"IETF/RFC-3044/RFC-3044.txt"},{"from":"IETF RFC 5741","to":"ISO-IEC ISO 3297 V1986","kind":"references","source":"IETF/RFC-5741/RFC-5741.txt"},{"from":"IETF RFC 7322","to":"ISO-IEC ISO 3297 V1986","kind":"references","source":"IETF/RFC-7322/RFC-7322.txt"},{"from":"IETF RFC 1134","to":"ISO-IEC ISO 3309-1979","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1171","to":"ISO-IEC ISO 3309-1979","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1331","to":"ISO-IEC ISO 3309-1979","kind":"references","source":"IETF/RFC-1331/RFC-1331.txt"},{"from":"IETF RFC 1662","to":"ISO-IEC ISO 3309-1979","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 1549","to":"ISO-IEC ISO 3309-1991","kind":"references","source":"IETF/RFC-1549/RFC-1549.txt"},{"from":"IETF RFC 1134","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1171","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1172","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1172/RFC-1172.txt"},{"from":"IETF RFC 1331","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1331/RFC-1331.txt"},{"from":"IETF RFC 1340","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1510","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1510/RFC-1510.txt"},{"from":"IETF RFC 1547","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1548","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1548/RFC-1548.txt"},{"from":"IETF RFC 1549","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1549/RFC-1549.txt"},{"from":"IETF RFC 1598","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1598/RFC-1598.txt"},{"from":"IETF RFC 1661","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1661/RFC-1661.txt"},{"from":"IETF RFC 1662","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 1663","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1663/RFC-1663.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1952","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1952/RFC-1952.txt"},{"from":"IETF RFC 1973","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-1973/RFC-1973.txt"},{"from":"IETF RFC 2171","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2171/RFC-2171.txt"},{"from":"IETF RFC 2172","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2172/RFC-2172.txt"},{"from":"IETF RFC 2175","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2175/RFC-2175.txt"},{"from":"IETF RFC 2363","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2512","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-2512/RFC-2512.txt"},{"from":"IETF RFC 3819","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 3961","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-3961/RFC-3961.txt"},{"from":"IETF RFC 6063","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-6063/RFC-6063.txt"},{"from":"IETF RFC 6388","to":"ISO-IEC ISO 3309 V1984","kind":"references","source":"IETF/RFC-6388/RFC-6388.txt"},{"from":"legal:2024-2977","to":"ISO-IEC ISO 39794","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"ARF TS12 V1.0.1","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI EN 319 412-5 V2.6.0","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf"},{"from":"IETF RFC 1476","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-1476/RFC-1476.txt"},{"from":"IETF RFC 2801","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 4006","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 5070","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 5941","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 7970","to":"ISO-IEC ISO 4217 V2015","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 1134","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1171","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1331","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-1331/RFC-1331.txt"},{"from":"IETF RFC 1547","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"IETF RFC 1549","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-1549/RFC-1549.txt"},{"from":"IETF RFC 3366","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 4335","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 1134","to":"ISO-IEC ISO 4335-1979","kind":"references","source":"IETF/RFC-1134/RFC-1134.txt"},{"from":"IETF RFC 1171","to":"ISO-IEC ISO 4335-1979","kind":"references","source":"IETF/RFC-1171/RFC-1171.txt"},{"from":"IETF RFC 1331","to":"ISO-IEC ISO 4335-1979","kind":"references","source":"IETF/RFC-1331/RFC-1331.txt"},{"from":"IETF RFC 1549","to":"ISO-IEC ISO 4335-1979","kind":"references","source":"IETF/RFC-1549/RFC-1549.txt"},{"from":"IETF RFC 1662","to":"ISO-IEC ISO 4335-1979","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 4873","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 928","to":"ISO-IEC ISO 5-7","kind":"references","source":"IETF/RFC-928/RFC-928.txt"},{"from":"IETF RFC 7326","to":"ISO-IEC ISO 50001 V2011","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 1489","to":"ISO-IEC ISO 5427","kind":"references","source":"IETF/RFC-1489/RFC-1489.txt"},{"from":"W3C vc-data-model V1.1","to":"ISO-IEC ISO 5786","kind":"references","source":"W3C/vc-data-model-V1.1/vc-data-model-V1.1.html"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 5817","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 8610","to":"ISO-IEC ISO 6093","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 1547","to":"ISO-IEC ISO 6256","kind":"references","source":"IETF/RFC-1547/RFC-1547.txt"},{"from":"legal:2026-1731","to":"ISO-IEC ISO 639","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI EN 319 412-5 V2.6.0","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf"},{"from":"IETF RFC 3066","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3282","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 4240","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-4240/RFC-4240.txt"},{"from":"IETF RFC 4645","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5645","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 639-1 V2002","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 2731","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-2731/RFC-2731.txt"},{"from":"IETF RFC 3066","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-3066/RFC-3066.txt"},{"from":"IETF RFC 3282","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-3282/RFC-3282.txt"},{"from":"IETF RFC 4645","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-4645/RFC-4645.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5645","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 6856","to":"ISO-IEC ISO 639-2 V1998","kind":"references","source":"IETF/RFC-6856/RFC-6856.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 639-3 V2007","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5645","to":"ISO-IEC ISO 639-3 V2007","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 639-3 V2007","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 5645","to":"ISO-IEC ISO 639-5 V2008","kind":"references","source":"IETF/RFC-5645/RFC-5645.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 639-5 V2008","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 6429 V1988","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 6429 V1988","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 6429 V1988","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 6429 V1988","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1428","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1468","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2045","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-2045/RFC-2045.txt"},{"from":"IETF RFC 2046","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2204","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-2204/RFC-2204.txt"},{"from":"IETF RFC 3367","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-3367/RFC-3367.txt"},{"from":"IETF RFC 3467","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5024","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 5198","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-5198/RFC-5198.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 646 V1991","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 1237","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2204","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-2204/RFC-2204.txt"},{"from":"IETF RFC 4043","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 982","to":"ISO-IEC ISO 6523","kind":"references","source":"IETF/RFC-982/RFC-982.txt"},{"from":"IETF RFC 5870","to":"ISO-IEC ISO 6709","kind":"references","source":"IETF/RFC-5870/RFC-5870.txt"},{"from":"IETF RFC 1489","to":"ISO-IEC ISO 6937","kind":"references","source":"IETF/RFC-1489/RFC-1489.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 6937","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 6937","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 6937-2 V1983","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 6937-2 V1983","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 70-79","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 3743","to":"ISO-IEC ISO 7098","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 1716","to":"ISO-IEC ISO 7489","kind":"references","source":"IETF/RFC-1716/RFC-1716.txt"},{"from":"IETF RFC 1812","to":"ISO-IEC ISO 7489","kind":"references","source":"IETF/RFC-1812/RFC-1812.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO 7498-2","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 1124","to":"ISO-IEC ISO 7498-2","kind":"references","source":"IETF/RFC-1124/RFC-1124.pdf"},{"from":"IETF RFC 1272","to":"ISO-IEC ISO 7498-2","kind":"references","source":"IETF/RFC-1272/RFC-1272.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 7498-2","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 7498-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 1508","to":"ISO-IEC ISO 7498-2-1988","kind":"references","source":"IETF/RFC-1508/RFC-1508.txt"},{"from":"IETF RFC 2078","to":"ISO-IEC ISO 7498-2-1988","kind":"references","source":"IETF/RFC-2078/RFC-2078.txt"},{"from":"IETF RFC 2743","to":"ISO-IEC ISO 7498-2-1988","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 7498-3 V1989","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 7498-4 V1989","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1272","to":"ISO-IEC ISO 7498-4 V1989","kind":"references","source":"IETF/RFC-1272/RFC-1272.txt"},{"from":"IETF RFC 2063","to":"ISO-IEC ISO 7498-4 V1989","kind":"references","source":"IETF/RFC-2063/RFC-2063.txt"},{"from":"IETF RFC 2722","to":"ISO-IEC ISO 7498-4 V1989","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 0989","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-0989/RFC-0989.txt"},{"from":"IETF RFC 1000","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1040","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1040/RFC-1040.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1113","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1113/RFC-1113.txt"},{"from":"IETF RFC 1136","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1136/RFC-1136.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1272","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1272/RFC-1272.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 2094","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-2094/RFC-2094.txt"},{"from":"IETF RFC 892","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-892/RFC-892.txt"},{"from":"IETF RFC 905","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-905/RFC-905.txt"},{"from":"IETF RFC 926","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-926/RFC-926.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 982","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-982/RFC-982.txt"},{"from":"IETF RFC 989","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-989/RFC-989.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 995","to":"ISO-IEC ISO 7498 V1984","kind":"references","source":"IETF/RFC-995/RFC-995.txt"},{"from":"IETF RFC 1381","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1553","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-1553/RFC-1553.txt"},{"from":"IETF RFC 1663","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-1663/RFC-1663.txt"},{"from":"IETF RFC 1717","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-1717/RFC-1717.txt"},{"from":"IETF RFC 1990","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-1990/RFC-1990.txt"},{"from":"IETF RFC 3366","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-3366/RFC-3366.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 5024","to":"ISO-IEC ISO 7776","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 7812-1985","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 7812-1985","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 8428","to":"ISO-IEC ISO 80000-5","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 802","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3176","to":"ISO-IEC ISO 8023","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 1006","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1859","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 2126","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 905","to":"ISO-IEC ISO 8072","kind":"references","source":"IETF/RFC-905/RFC-905.txt"},{"from":"IETF RFC 1006","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1859","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 1950","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-1950/RFC-1950.txt"},{"from":"IETF RFC 2126","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 2883","to":"ISO-IEC ISO 8073 V1992","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 1382","to":"ISO-IEC ISO 8206","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1377","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1382","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1490","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 2427","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 5024","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 995","to":"ISO-IEC ISO 8208 V1984","kind":"references","source":"IETF/RFC-995/RFC-995.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8326","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1006","to":"ISO-IEC ISO 8327","kind":"references","source":"IETF/RFC-1006/RFC-1006.txt"},{"from":"IETF RFC 1683","to":"ISO-IEC ISO 8327","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8327","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1859","to":"ISO-IEC ISO 8327","kind":"references","source":"IETF/RFC-1859/RFC-1859.txt"},{"from":"IETF RFC 1000","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1011","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1011/RFC-1011.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1237","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1277","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1277/RFC-1277.txt"},{"from":"IETF RFC 1278","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1278/RFC-1278.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1637","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1637/RFC-1637.txt"},{"from":"IETF RFC 1706","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1706/RFC-1706.txt"},{"from":"IETF RFC 1768","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 2126","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-2126/RFC-2126.txt"},{"from":"IETF RFC 4715","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 926","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-926/RFC-926.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 982","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-982/RFC-982.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 995","to":"ISO-IEC ISO 8348 V1987","kind":"references","source":"IETF/RFC-995/RFC-995.txt"},{"from":"IETF RFC 1423","to":"ISO-IEC ISO 8372","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 2346","to":"ISO-IEC ISO 838","kind":"references","source":"IETF/RFC-2346/RFC-2346.txt"},{"from":"IETF RFC 1768","to":"ISO-IEC ISO 8473-1","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1575","to":"ISO-IEC ISO 8473-1993","kind":"references","source":"IETF/RFC-1575/RFC-1575.txt"},{"from":"IETF RFC 1000","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 1009","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1009/RFC-1009.txt"},{"from":"IETF RFC 1070","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1070/RFC-1070.txt"},{"from":"IETF RFC 1139","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1139/RFC-1139.txt"},{"from":"IETF RFC 1140","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1140/RFC-1140.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1162","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1169","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1169/RFC-1169.txt"},{"from":"IETF RFC 1195","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1200","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1200/RFC-1200.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1237","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1238","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1250","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1250/RFC-1250.txt"},{"from":"IETF RFC 1322","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1347","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1347/RFC-1347.txt"},{"from":"IETF RFC 1377","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1454","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1454/RFC-1454.txt"},{"from":"IETF RFC 1461","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1478","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1478/RFC-1478.txt"},{"from":"IETF RFC 1479","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1479/RFC-1479.txt"},{"from":"IETF RFC 1490","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1526","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1575","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1575/RFC-1575.txt"},{"from":"IETF RFC 1600","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1600/RFC-1600.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1654","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1654/RFC-1654.txt"},{"from":"IETF RFC 1745","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1745/RFC-1745.txt"},{"from":"IETF RFC 1752","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1755","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1768","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1771","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1771/RFC-1771.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2331","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2427","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2439","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 2763","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-2763/RFC-2763.txt"},{"from":"IETF RFC 2966","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-2966/RFC-2966.txt"},{"from":"IETF RFC 3002","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3002/RFC-3002.txt"},{"from":"IETF RFC 3219","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3219/RFC-3219.txt"},{"from":"IETF RFC 3373","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3373/RFC-3373.txt"},{"from":"IETF RFC 3563","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3563/RFC-3563.txt"},{"from":"IETF RFC 3567","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3719","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3784","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3784/RFC-3784.txt"},{"from":"IETF RFC 3786","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 3795","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3795/RFC-3795.txt"},{"from":"IETF RFC 3796","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 3847","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 4271","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-4271/RFC-4271.txt"},{"from":"IETF RFC 4444","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4593","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 4971","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-4971/RFC-4971.txt"},{"from":"IETF RFC 5029","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5029/RFC-5029.txt"},{"from":"IETF RFC 5073","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5073/RFC-5073.txt"},{"from":"IETF RFC 5130","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5130/RFC-5130.txt"},{"from":"IETF RFC 5302","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5302/RFC-5302.txt"},{"from":"IETF RFC 5303","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5303/RFC-5303.txt"},{"from":"IETF RFC 5304","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5304/RFC-5304.txt"},{"from":"IETF RFC 5305","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5305/RFC-5305.txt"},{"from":"IETF RFC 5306","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5306/RFC-5306.txt"},{"from":"IETF RFC 5308","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5308/RFC-5308.txt"},{"from":"IETF RFC 5309","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5309/RFC-5309.txt"},{"from":"IETF RFC 5310","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5311","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 6119","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6119/RFC-6119.txt"},{"from":"IETF RFC 6165","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6232","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6325","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6329","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6361","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6439","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6822","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6822/RFC-6822.txt"},{"from":"IETF RFC 6823","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7067","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7172","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7175","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7175/RFC-7175.txt"},{"from":"IETF RFC 7176","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7176/RFC-7176.txt"},{"from":"IETF RFC 7177","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7178","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7178/RFC-7178.txt"},{"from":"IETF RFC 7180","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7180/RFC-7180.txt"},{"from":"IETF RFC 7356","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7752","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7752/RFC-7752.txt"},{"from":"IETF RFC 7780","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 7961","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-7961/RFC-7961.txt"},{"from":"IETF RFC 926","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-926/RFC-926.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 995","to":"ISO-IEC ISO 8473 V1988","kind":"references","source":"IETF/RFC-995/RFC-995.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8509","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 926","to":"ISO-IEC ISO 8509","kind":"references","source":"IETF/RFC-926/RFC-926.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 8509","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 8509","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571-1","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571-2","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571-3","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571-4","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"IETF RFC 1415","to":"ISO-IEC ISO 8571-5","kind":"references","source":"IETF/RFC-1415/RFC-1415.txt"},{"from":"legal:2026-1731","to":"ISO-IEC ISO 8601-1","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS05 V1.2.1","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS10 V1.2","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS12 V1.0.1","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TS 119 602 V1.1.1","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2326","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2413","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2413/RFC-2413.txt"},{"from":"IETF RFC 2421","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2421/RFC-2421.txt"},{"from":"IETF RFC 2425","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2425/RFC-2425.txt"},{"from":"IETF RFC 2426","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 2518","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 2611","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2611/RFC-2611.txt"},{"from":"IETF RFC 2731","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2731/RFC-2731.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2885","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2924","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3015","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3085","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3085/RFC-3085.txt"},{"from":"IETF RFC 3164","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3164/RFC-3164.txt"},{"from":"IETF RFC 3339","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3339/RFC-3339.txt"},{"from":"IETF RFC 3406","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3406/RFC-3406.txt"},{"from":"IETF RFC 3525","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3862","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3880","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 4151","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 4198","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-4198/RFC-4198.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4765","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5013","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-5013/RFC-5013.txt"},{"from":"IETF RFC 5070","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-5070/RFC-5070.txt"},{"from":"IETF RFC 6021","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6350","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 6492","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6492/RFC-6492.txt"},{"from":"IETF RFC 6509","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6509/RFC-6509.txt"},{"from":"IETF RFC 6787","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 6991","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 7049","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7095","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-7095/RFC-7095.txt"},{"from":"IETF RFC 7493","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-7493/RFC-7493.txt"},{"from":"IETF RFC 7826","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-7826/RFC-7826.txt"},{"from":"IETF RFC 8949","to":"ISO-IEC ISO 8601 V2019","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 8602","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 8602","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8613","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1494","to":"ISO-IEC ISO 8613","kind":"references","source":"IETF/RFC-1494/RFC-1494.txt"},{"from":"IETF RFC 1136","to":"ISO-IEC ISO 8648 V1988","kind":"references","source":"IETF/RFC-1136/RFC-1136.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8648 V1988","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 941","to":"ISO-IEC ISO 8648 V1988","kind":"references","source":"IETF/RFC-941/RFC-941.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 8648 V1988","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 8649","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 8649","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8649","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8650","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 8650","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 8650","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8650","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1294","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-1294/RFC-1294.txt"},{"from":"IETF RFC 1329","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-1329/RFC-1329.txt"},{"from":"IETF RFC 1490","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 2427","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2625","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-2625/RFC-2625.txt"},{"from":"IETF RFC 2834","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-2834/RFC-2834.txt"},{"from":"IETF RFC 8519","to":"ISO-IEC ISO 8802-2 V1989","kind":"references","source":"IETF/RFC-8519/RFC-8519.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1368","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-1368/RFC-1368.txt"},{"from":"IETF RFC 1515","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-1515/RFC-1515.txt"},{"from":"IETF RFC 1516","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-1516/RFC-1516.txt"},{"from":"IETF RFC 2063","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-2063/RFC-2063.txt"},{"from":"IETF RFC 2108","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-2108/RFC-2108.txt"},{"from":"IETF RFC 2239","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-2239/RFC-2239.txt"},{"from":"IETF RFC 2722","to":"ISO-IEC ISO 8802-3","kind":"references","source":"IETF/RFC-2722/RFC-2722.txt"},{"from":"IETF RFC 1060","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1340","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1490","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1490/RFC-1490.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1707","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1707/RFC-1707.txt"},{"from":"IETF RFC 1755","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1932","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-1932/RFC-1932.txt"},{"from":"IETF RFC 2331","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2381","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-2381/RFC-2381.txt"},{"from":"IETF RFC 2427","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 4259","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 935","to":"ISO-IEC ISO 8802 V1988","kind":"references","source":"IETF/RFC-935/RFC-935.txt"},{"from":"IETF RFC 1573","to":"ISO-IEC ISO 88022","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 88022","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 88022","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 88022","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1066","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1284","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1284/RFC-1284.txt"},{"from":"IETF RFC 1398","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1398/RFC-1398.txt"},{"from":"IETF RFC 1573","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1623","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1623/RFC-1623.txt"},{"from":"IETF RFC 1643","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1643/RFC-1643.txt"},{"from":"IETF RFC 1650","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-1650/RFC-1650.txt"},{"from":"IETF RFC 2358","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-2358/RFC-2358.txt"},{"from":"IETF RFC 2665","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-2665/RFC-2665.txt"},{"from":"IETF RFC 3635","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 88023","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1066","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1230","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1230/RFC-1230.txt"},{"from":"IETF RFC 1573","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 3176","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 88024","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1066","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1231","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1231/RFC-1231.txt"},{"from":"IETF RFC 1573","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1748","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-1748/RFC-1748.txt"},{"from":"IETF RFC 3176","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-3176/RFC-3176.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 88025","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 1066","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1066/RFC-1066.txt"},{"from":"IETF RFC 1156","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1156/RFC-1156.txt"},{"from":"IETF RFC 1158","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1158/RFC-1158.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1573","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1573/RFC-1573.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 7224","to":"ISO-IEC ISO 88026","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3635","to":"ISO-IEC ISO 88032","kind":"references","source":"IETF/RFC-3635/RFC-3635.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 8807-1990","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 8807-1990","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8822","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 8822","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 8822","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8822","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8823","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1683","to":"ISO-IEC ISO 8823","kind":"references","source":"IETF/RFC-1683/RFC-1683.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8823","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2257","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-2257/RFC-2257.txt"},{"from":"IETF RFC 2741","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-2741/RFC-2741.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 8824","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO 8824-1","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO 8824-2","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO 8824-3","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO 8824-4","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 8825","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 8825","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 8825","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 8825","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 8825","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO 8825-1","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 983","to":"ISO-IEC ISO 8831","kind":"references","source":"IETF/RFC-983/RFC-983.txt"},{"from":"ARF TS01 V1.2","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"ARF/TS01-V1.2/TS01-V1.2.md"},{"from":"IETF RFC 1154","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1154/RFC-1154.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1554","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1641/RFC-1641.pdf"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1874","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1890","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 1952","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-1952/RFC-1952.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2058","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2138","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2326","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2326/RFC-2326.txt"},{"from":"IETF RFC 2327","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2459","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2543","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2543/RFC-2543.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2756","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2756/RFC-2756.txt"},{"from":"IETF RFC 2831","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2865","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3261","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-3261/RFC-3261.txt"},{"from":"IETF RFC 3280","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3494","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-3494/RFC-3494.txt"},{"from":"IETF RFC 3875","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 4005","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4013","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4013/RFC-4013.txt"},{"from":"IETF RFC 4252","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4252/RFC-4252.txt"},{"from":"IETF RFC 4256","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4256/RFC-4256.txt"},{"from":"IETF RFC 4462","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4463","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4463/RFC-4463.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4566","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4630","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-4630/RFC-4630.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6787","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-6787/RFC-6787.txt"},{"from":"IETF RFC 8866","to":"ISO-IEC ISO 8859-1 V1998","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-10 V1992","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-2 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-3 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-4 V1998","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1896","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1896/RFC-1896.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 3536","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 8859-5 V1999","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1556","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-6 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1554","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1554/RFC-1554.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-7 V1987","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-8-1988","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1555","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1555/RFC-1555.txt"},{"from":"IETF RFC 1556","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1896","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1896/RFC-1896.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO 8859-8 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-1341/RFC-1341.txt"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-1521/RFC-1521.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1945","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-1945/RFC-1945.txt"},{"from":"IETF RFC 2068","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-2068/RFC-2068.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO 8859-9","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 1312","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1312/RFC-1312.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 1428","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1428/RFC-1428.txt"},{"from":"IETF RFC 1456","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1456/RFC-1456.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1842","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1842/RFC-1842.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1896","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-1896/RFC-1896.txt"},{"from":"IETF RFC 2046","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2046/RFC-2046.txt"},{"from":"IETF RFC 2058","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2058/RFC-2058.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2138","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2138/RFC-2138.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2640","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2831","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2831/RFC-2831.txt"},{"from":"IETF RFC 2865","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-2865/RFC-2865.txt"},{"from":"IETF RFC 3023","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 4005","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-4005/RFC-4005.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 5137","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO 8859 V1987","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 1341","to":"ISO-IEC ISO 88592","kind":"references","source":"IETF/RFC-1341/RFC-1341.pdf"},{"from":"IETF RFC 1521","to":"ISO-IEC ISO 88592","kind":"references","source":"IETF/RFC-1521/RFC-1521.pdf"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO 8878","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 8879-1986","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 8879-1986","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1873","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-1873/RFC-1873.txt"},{"from":"IETF RFC 1874","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2110","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2110/RFC-2110.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2165","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2165/RFC-2165.txt"},{"from":"IETF RFC 2376","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2376/RFC-2376.txt"},{"from":"IETF RFC 2557","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-2557/RFC-2557.txt"},{"from":"IETF RFC 3023","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-3023/RFC-3023.txt"},{"from":"IETF RFC 3120","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-3120/RFC-3120.txt"},{"from":"IETF RFC 3121","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-3121/RFC-3121.txt"},{"from":"IETF RFC 3151","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-3151/RFC-3151.txt"},{"from":"IETF RFC 3880","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-3880/RFC-3880.txt"},{"from":"IETF RFC 4765","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5218","to":"ISO-IEC ISO 8879 V1988","kind":"references","source":"IETF/RFC-5218/RFC-5218.txt"},{"from":"IETF RFC 1457","to":"ISO-IEC ISO 8883-1","kind":"references","source":"IETF/RFC-1457/RFC-1457.txt"},{"from":"IETF RFC 1381","to":"ISO-IEC ISO 8885","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 1381","to":"ISO-IEC ISO 8886","kind":"references","source":"IETF/RFC-1381/RFC-1381.txt"},{"from":"IETF RFC 8859","to":"ISO-IEC ISO 8895-1","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 9000","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 9066","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2426","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-2426/RFC-2426.txt"},{"from":"IETF RFC 2445","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 6350","to":"ISO-IEC ISO 9070","kind":"references","source":"IETF/RFC-6350/RFC-6350.txt"},{"from":"IETF RFC 1085","to":"ISO-IEC ISO 9072","kind":"references","source":"IETF/RFC-1085/RFC-1085.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 9072-1","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 9072-1","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1095","to":"ISO-IEC ISO 9072-2","kind":"references","source":"IETF/RFC-1095/RFC-1095.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 9072-2","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 994","to":"ISO-IEC ISO 9074","kind":"references","source":"IETF/RFC-994/RFC-994.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 9074-1989","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 9074-1989","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1103","to":"ISO-IEC ISO 9314-1","kind":"references","source":"IETF/RFC-1103/RFC-1103.txt"},{"from":"IETF RFC 1188","to":"ISO-IEC ISO 9314-1","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1390","to":"ISO-IEC ISO 9314-1","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 1103","to":"ISO-IEC ISO 9314-2","kind":"references","source":"IETF/RFC-1103/RFC-1103.txt"},{"from":"IETF RFC 1188","to":"ISO-IEC ISO 9314-2","kind":"references","source":"IETF/RFC-1188/RFC-1188.txt"},{"from":"IETF RFC 1390","to":"ISO-IEC ISO 9314-2","kind":"references","source":"IETF/RFC-1390/RFC-1390.txt"},{"from":"IETF RFC 5941","to":"ISO-IEC ISO 9362 V1994","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1162","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1162/RFC-1162.txt"},{"from":"IETF RFC 1195","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1195/RFC-1195.txt"},{"from":"IETF RFC 1200","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1200/RFC-1200.txt"},{"from":"IETF RFC 1213","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1213/RFC-1213.txt"},{"from":"IETF RFC 1237","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1237/RFC-1237.txt"},{"from":"IETF RFC 1238","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1238/RFC-1238.txt"},{"from":"IETF RFC 1250","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1250/RFC-1250.txt"},{"from":"IETF RFC 1354","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1354/RFC-1354.txt"},{"from":"IETF RFC 1377","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1377/RFC-1377.txt"},{"from":"IETF RFC 1454","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1454/RFC-1454.txt"},{"from":"IETF RFC 1461","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1461/RFC-1461.txt"},{"from":"IETF RFC 1526","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1526/RFC-1526.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1768","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2096","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-2096/RFC-2096.txt"},{"from":"IETF RFC 3796","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-3796/RFC-3796.txt"},{"from":"IETF RFC 4292","to":"ISO-IEC ISO 9542 V1988","kind":"references","source":"IETF/RFC-4292/RFC-4292.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 9548","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1240","to":"ISO-IEC ISO 9576","kind":"references","source":"IETF/RFC-1240/RFC-1240.txt"},{"from":"IETF RFC 1060","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-1060/RFC-1060.txt"},{"from":"IETF RFC 1340","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-1340/RFC-1340.txt"},{"from":"IETF RFC 1700","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-1700/RFC-1700.txt"},{"from":"IETF RFC 1755","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 2331","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 3355","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 6213","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6328","to":"ISO-IEC ISO 9577","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 9594","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1292","to":"ISO-IEC ISO 9594","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"IETF RFC 1608","to":"ISO-IEC ISO 9594","kind":"references","source":"IETF/RFC-1608/RFC-1608.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO 9594","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO 9594","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 9594-1","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 9594-1","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1848","to":"ISO-IEC ISO 9594-2","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 4043","to":"ISO-IEC ISO 9594-2","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"ETSI TS 101 861 V1.4.1","to":"ISO-IEC ISO 9594-6","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"IETF RFC 1423","to":"ISO-IEC ISO 9594-8","kind":"references","source":"IETF/RFC-1423/RFC-1423.txt"},{"from":"IETF RFC 1848","to":"ISO-IEC ISO 9594-8","kind":"references","source":"IETF/RFC-1848/RFC-1848.txt"},{"from":"IETF RFC 2510","to":"ISO-IEC ISO 9594-8","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO 9594-8","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO 9594-8","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2120","to":"ISO-IEC ISO 9594-9","kind":"references","source":"IETF/RFC-2120/RFC-2120.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 9595","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1470","to":"ISO-IEC ISO 9595","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 1189","to":"ISO-IEC ISO 9596","kind":"references","source":"IETF/RFC-1189/RFC-1189.txt"},{"from":"IETF RFC 1470","to":"ISO-IEC ISO 9596","kind":"references","source":"IETF/RFC-1470/RFC-1470.txt"},{"from":"IETF RFC 2790","to":"ISO-IEC ISO 9660","kind":"references","source":"IETF/RFC-2790/RFC-2790.txt"},{"from":"IETF RFC 4765","to":"ISO-IEC ISO 9660","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 1767","to":"ISO-IEC ISO 9735","kind":"references","source":"IETF/RFC-1767/RFC-1767.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO 9796","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO 9796","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 3447","to":"ISO-IEC ISO 9796-1","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO 9796-1","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO 9796-1991","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 9796-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 6979","to":"ISO-IEC ISO 9796-2","kind":"references","source":"IETF/RFC-6979/RFC-6979.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO 9796-4","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 9101","to":"ISO-IEC ISO 9798","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 6021","to":"ISO-IEC ISO 9834-1","kind":"references","source":"IETF/RFC-6021/RFC-6021.txt"},{"from":"IETF RFC 6991","to":"ISO-IEC ISO 9834-1","kind":"references","source":"IETF/RFC-6991/RFC-6991.txt"},{"from":"IETF RFC 4997","to":"ISO-IEC ISO 9899 V1990","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 6557","to":"ISO-IEC ISO 9899 V1990","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 1000","to":"ISO-IEC ISO 995","kind":"references","source":"IETF/RFC-1000/RFC-1000.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 9999","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO 9999-1","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO/IEC 10021","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO/IEC 10021","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO/IEC 10021","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO/IEC 10021","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2162","to":"ISO-IEC ISO/IEC 10021","kind":"references","source":"IETF/RFC-2162/RFC-2162.txt"},{"from":"IETF RFC 1138","to":"ISO-IEC ISO/IEC 10021-1","kind":"references","source":"IETF/RFC-1138/RFC-1138.txt"},{"from":"IETF RFC 1148","to":"ISO-IEC ISO/IEC 10021-1","kind":"references","source":"IETF/RFC-1148/RFC-1148.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO/IEC 10021-1","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO/IEC 10021-1","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 3801","to":"ISO-IEC ISO/IEC 10021-1","kind":"references","source":"IETF/RFC-3801/RFC-3801.txt"},{"from":"IETF RFC 1327","to":"ISO-IEC ISO/IEC 10021-2","kind":"references","source":"IETF/RFC-1327/RFC-1327.txt"},{"from":"IETF RFC 1506","to":"ISO-IEC ISO/IEC 10021-2","kind":"references","source":"IETF/RFC-1506/RFC-1506.txt"},{"from":"IETF RFC 1685","to":"ISO-IEC ISO/IEC 10021-2","kind":"references","source":"IETF/RFC-1685/RFC-1685.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO/IEC 10021-4","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO/IEC 10021-7 V1997","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO/IEC 10021-7 V1997","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2422","to":"ISO-IEC ISO/IEC 10021-7 V1997","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 3802","to":"ISO-IEC ISO/IEC 10021-7 V1997","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 10021-7 V1997","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO/IEC 10026-1 V1992","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 1749","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2019","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2019/RFC-2019.txt"},{"from":"IETF RFC 2338","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2338/RFC-2338.txt"},{"from":"IETF RFC 2674","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2814","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2814/RFC-2814.txt"},{"from":"IETF RFC 2815","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2878","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3270","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3290","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3518","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 3768","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-3768/RFC-3768.txt"},{"from":"IETF RFC 4318","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4363","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4665","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4710","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4710/RFC-4710.txt"},{"from":"IETF RFC 4761","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"ISO-IEC ISO/IEC 10038","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO/IEC 10039 V1990","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 10118","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 10118-1","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 10118-1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 10118-1","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 10118-2","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 10118-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 10118-2","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 2857","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-2857/RFC-2857.txt"},{"from":"IETF RFC 4051","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-4051/RFC-4051.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5708","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-5708/RFC-5708.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 6931","to":"ISO-IEC ISO/IEC 10118-3 V2004","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 10118-4","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 10118-4","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 1142","to":"ISO-IEC ISO/IEC 10165-2","kind":"references","source":"IETF/RFC-1142/RFC-1142.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 2565","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2565/RFC-2565.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2567","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2567/RFC-2567.txt"},{"from":"IETF RFC 2568","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2568/RFC-2568.txt"},{"from":"IETF RFC 2910","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2910/RFC-2910.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3805","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-3805/RFC-3805.txt"},{"from":"IETF RFC 3806","to":"ISO-IEC ISO/IEC 10175","kind":"references","source":"IETF/RFC-3806/RFC-3806.txt"},{"from":"IETF RFC 3151","to":"ISO-IEC ISO/IEC 10179 V1996","kind":"references","source":"IETF/RFC-3151/RFC-3151.txt"},{"from":"IETF RFC 3029","to":"ISO-IEC ISO/IEC 10181-5","kind":"references","source":"IETF/RFC-3029/RFC-3029.txt"},{"from":"IETF RFC 3125","to":"ISO-IEC ISO/IEC 10181-5","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3126","to":"ISO-IEC ISO/IEC 10181-5","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3161","to":"ISO-IEC ISO/IEC 10181-5","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 10181-5","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 1322","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-1322/RFC-1322.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 2763","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-2763/RFC-2763.txt"},{"from":"IETF RFC 3373","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3373/RFC-3373.txt"},{"from":"IETF RFC 3563","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3563/RFC-3563.txt"},{"from":"IETF RFC 3567","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3567/RFC-3567.txt"},{"from":"IETF RFC 3719","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 3786","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3786/RFC-3786.txt"},{"from":"IETF RFC 3847","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-3847/RFC-3847.txt"},{"from":"IETF RFC 4444","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-4444/RFC-4444.txt"},{"from":"IETF RFC 4593","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-4593/RFC-4593.txt"},{"from":"IETF RFC 5089","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-5089/RFC-5089.txt"},{"from":"IETF RFC 5310","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-5310/RFC-5310.txt"},{"from":"IETF RFC 5311","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-5311/RFC-5311.txt"},{"from":"IETF RFC 6165","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6165/RFC-6165.txt"},{"from":"IETF RFC 6232","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6232/RFC-6232.txt"},{"from":"IETF RFC 6233","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6233/RFC-6233.txt"},{"from":"IETF RFC 6325","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6325/RFC-6325.txt"},{"from":"IETF RFC 6326","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6326/RFC-6326.txt"},{"from":"IETF RFC 6327","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6327/RFC-6327.txt"},{"from":"IETF RFC 6329","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6361","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6361/RFC-6361.txt"},{"from":"IETF RFC 6439","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6439/RFC-6439.txt"},{"from":"IETF RFC 6823","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-6823/RFC-6823.txt"},{"from":"IETF RFC 7067","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7067/RFC-7067.txt"},{"from":"IETF RFC 7172","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7172/RFC-7172.txt"},{"from":"IETF RFC 7173","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7173/RFC-7173.txt"},{"from":"IETF RFC 7177","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7177/RFC-7177.txt"},{"from":"IETF RFC 7356","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7356/RFC-7356.txt"},{"from":"IETF RFC 7357","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7357/RFC-7357.txt"},{"from":"IETF RFC 7455","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7780","to":"ISO-IEC ISO/IEC 10589 V2002","kind":"references","source":"IETF/RFC-7780/RFC-7780.txt"},{"from":"IETF RFC 1505","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1505/RFC-1505.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1815","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1815/RFC-1815.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1874","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1890","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2044","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2044/RFC-2044.txt"},{"from":"IETF RFC 2070","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2070/RFC-2070.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2152","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2152/RFC-2152.txt"},{"from":"IETF RFC 2218","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2218/RFC-2218.txt"},{"from":"IETF RFC 2244","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 2251","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2251/RFC-2251.txt"},{"from":"IETF RFC 2252","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2279","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2291","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2291/RFC-2291.txt"},{"from":"IETF RFC 2327","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2440","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2440/RFC-2440.txt"},{"from":"IETF RFC 2482","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2624","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2624/RFC-2624.txt"},{"from":"IETF RFC 2640","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2781","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2793","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3010","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3280","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3383","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3383/RFC-3383.txt"},{"from":"IETF RFC 3454","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3454/RFC-3454.txt"},{"from":"IETF RFC 3467","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3508","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3530","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3530/RFC-3530.txt"},{"from":"IETF RFC 3536","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3629","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3722","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3920","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 4103","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 4511","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4880","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-4880/RFC-4880.txt"},{"from":"IETF RFC 5055","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-5055/RFC-5055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 10646-1 V2000","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 3467","to":"ISO-IEC ISO/IEC 10646-2 V2001","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 3629","to":"ISO-IEC ISO/IEC 10646-2 V2001","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3743","to":"ISO-IEC ISO/IEC 10646-2 V2001","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 10646-2 V2001","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 1502","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-1502/RFC-1502.txt"},{"from":"IETF RFC 1641","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-1641/RFC-1641.txt"},{"from":"IETF RFC 1642","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-1642/RFC-1642.txt"},{"from":"IETF RFC 1759","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-1759/RFC-1759.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 2279","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-2279/RFC-2279.txt"},{"from":"IETF RFC 2482","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-2482/RFC-2482.txt"},{"from":"IETF RFC 2640","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 2781","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-2781/RFC-2781.txt"},{"from":"IETF RFC 2801","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 3010","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3010/RFC-3010.txt"},{"from":"IETF RFC 3454","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3454/RFC-3454.txt"},{"from":"IETF RFC 3491","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3491/RFC-3491.txt"},{"from":"IETF RFC 3536","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3536/RFC-3536.txt"},{"from":"IETF RFC 3629","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3629/RFC-3629.txt"},{"from":"IETF RFC 3650","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3650/RFC-3650.txt"},{"from":"IETF RFC 3722","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3722/RFC-3722.txt"},{"from":"IETF RFC 3743","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3743/RFC-3743.txt"},{"from":"IETF RFC 3862","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3862/RFC-3862.txt"},{"from":"IETF RFC 3920","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3920/RFC-3920.txt"},{"from":"IETF RFC 3986","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3986/RFC-3986.txt"},{"from":"IETF RFC 3987","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-3987/RFC-3987.txt"},{"from":"IETF RFC 4267","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-4267/RFC-4267.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 4690","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-4690/RFC-4690.txt"},{"from":"IETF RFC 4765","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-4765/RFC-4765.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 6020","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-6020/RFC-6020.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6122","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-6122/RFC-6122.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 7012","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-7012/RFC-7012.txt"},{"from":"IETF RFC 7950","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-7950/RFC-7950.txt"},{"from":"IETF RFC 8489","to":"ISO-IEC ISO/IEC 10646 V2020","kind":"references","source":"IETF/RFC-8489/RFC-8489.txt"},{"from":"IETF RFC 1382","to":"ISO-IEC ISO/IEC 10733","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 1874","to":"ISO-IEC ISO/IEC 10744 V1992","kind":"references","source":"IETF/RFC-1874/RFC-1874.txt"},{"from":"IETF RFC 1629","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-1629/RFC-1629.txt"},{"from":"IETF RFC 1774","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-1774/RFC-1774.txt"},{"from":"IETF RFC 1930","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-1930/RFC-1930.txt"},{"from":"IETF RFC 1965","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-1965/RFC-1965.txt"},{"from":"IETF RFC 2439","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-2439/RFC-2439.txt"},{"from":"IETF RFC 3065","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-3065/RFC-3065.txt"},{"from":"IETF RFC 5065","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-5065/RFC-5065.txt"},{"from":"IETF RFC 6396","to":"ISO-IEC ISO/IEC 10747","kind":"references","source":"IETF/RFC-6396/RFC-6396.txt"},{"from":"IETF RFC 2531","to":"ISO-IEC ISO/IEC 10918-1 V1993","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2879","to":"ISO-IEC ISO/IEC 10918-1 V1993","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"ISO-IEC ISO/IEC 10918-1 V1993","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 1890","to":"ISO-IEC ISO/IEC 11172","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 11172","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 11172","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 3189","to":"ISO-IEC ISO/IEC 11172","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3551","to":"ISO-IEC ISO/IEC 11172","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 11172-2","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 11172-2","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 1890","to":"ISO-IEC ISO/IEC 11172-3","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 11172-3","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 11172-3","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 3551","to":"ISO-IEC ISO/IEC 11172-3","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4947","to":"ISO-IEC ISO/IEC 113818-1","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5163","to":"ISO-IEC ISO/IEC 113818-1","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 2531","to":"ISO-IEC ISO/IEC 11544 V1993","kind":"references","source":"IETF/RFC-2531/RFC-2531.txt"},{"from":"IETF RFC 2879","to":"ISO-IEC ISO/IEC 11544 V1993","kind":"references","source":"IETF/RFC-2879/RFC-2879.txt"},{"from":"IETF RFC 2880","to":"ISO-IEC ISO/IEC 11544 V1993","kind":"references","source":"IETF/RFC-2880/RFC-2880.txt"},{"from":"IETF RFC 4497","to":"ISO-IEC ISO/IEC 11571","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 2719","to":"ISO-IEC ISO/IEC 11572","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 3204","to":"ISO-IEC ISO/IEC 11572","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 4458","to":"ISO-IEC ISO/IEC 11572","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4497","to":"ISO-IEC ISO/IEC 11572","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 2518","to":"ISO-IEC ISO/IEC 11578 V1996","kind":"references","source":"IETF/RFC-2518/RFC-2518.txt"},{"from":"IETF RFC 3645","to":"ISO-IEC ISO/IEC 11578 V1996","kind":"references","source":"IETF/RFC-3645/RFC-3645.txt"},{"from":"IETF RFC 4151","to":"ISO-IEC ISO/IEC 11578 V1996","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 3204","to":"ISO-IEC ISO/IEC 11582","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 4497","to":"ISO-IEC ISO/IEC 11582","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 3830","to":"ISO-IEC ISO/IEC 11770-3","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 2734","to":"ISO-IEC ISO/IEC 13213 V1994","kind":"references","source":"IETF/RFC-2734/RFC-2734.txt"},{"from":"IETF RFC 3146","to":"ISO-IEC ISO/IEC 13213 V1994","kind":"references","source":"IETF/RFC-3146/RFC-3146.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 13818","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 13818","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 3189","to":"ISO-IEC ISO/IEC 13818","kind":"references","source":"IETF/RFC-3189/RFC-3189.txt"},{"from":"IETF RFC 3819","to":"ISO-IEC ISO/IEC 13818-1 V2000","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4326","to":"ISO-IEC ISO/IEC 13818-1 V2000","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 13818-2","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 13818-2","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 2038","to":"ISO-IEC ISO/IEC 13818-3 V1995","kind":"references","source":"IETF/RFC-2038/RFC-2038.txt"},{"from":"IETF RFC 2250","to":"ISO-IEC ISO/IEC 13818-3 V1995","kind":"references","source":"IETF/RFC-2250/RFC-2250.txt"},{"from":"IETF RFC 4259","to":"ISO-IEC ISO/IEC 13818-3 V1995","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4947","to":"ISO-IEC ISO/IEC 138181","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"ETSI EN 319 522-1 V1.2.1","to":"ISO-IEC ISO/IEC 13888","kind":"references","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf"},{"from":"ETSI EN 319 522-1 V1.2.1","to":"ISO-IEC ISO/IEC 13888-1 V2009","kind":"references","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 13888-1 V2009","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 3126","to":"ISO-IEC ISO/IEC 13888-1 V2009","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 13888-1 V2009","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"ETSI EN 319 522-1 V1.2.1","to":"ISO-IEC ISO/IEC 13888-2 V2010","kind":"references","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf"},{"from":"ETSI EN 319 522-1 V1.2.1","to":"ISO-IEC ISO/IEC 13888-3 V2010","kind":"references","source":"ETSI/EN-319-522-1-V1.2.1/EN-319-522-1-V1.2.1.pdf"},{"from":"IETF RFC 3016","to":"ISO-IEC ISO/IEC 14469-2","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3640","to":"ISO-IEC ISO/IEC 14496","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 6190","to":"ISO-IEC ISO/IEC 14496","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 3016","to":"ISO-IEC ISO/IEC 14496-1 V2001","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3640","to":"ISO-IEC ISO/IEC 14496-1 V2001","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496-1 V2001","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 3984","to":"ISO-IEC ISO/IEC 14496-10 V2004","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496-10 V2004","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 5104","to":"ISO-IEC ISO/IEC 14496-10 V2004","kind":"references","source":"IETF/RFC-5104/RFC-5104.txt"},{"from":"IETF RFC 6184","to":"ISO-IEC ISO/IEC 14496-10 V2004","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"ISO-IEC ISO/IEC 14496-10 V2004","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496-12","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496-14","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 3984","to":"ISO-IEC ISO/IEC 14496-15","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4337","to":"ISO-IEC ISO/IEC 14496-15","kind":"references","source":"IETF/RFC-4337/RFC-4337.txt"},{"from":"IETF RFC 3016","to":"ISO-IEC ISO/IEC 14496-2 V2004","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3640","to":"ISO-IEC ISO/IEC 14496-2 V2004","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"IETF RFC 4585","to":"ISO-IEC ISO/IEC 14496-2 V2004","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 6236","to":"ISO-IEC ISO/IEC 14496-2 V2004","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 8081","to":"ISO-IEC ISO/IEC 14496-22","kind":"references","source":"IETF/RFC-8081/RFC-8081.txt"},{"from":"IETF RFC 3016","to":"ISO-IEC ISO/IEC 14496-3 V1999","kind":"references","source":"IETF/RFC-3016/RFC-3016.txt"},{"from":"IETF RFC 3640","to":"ISO-IEC ISO/IEC 14496-3 V1999","kind":"references","source":"IETF/RFC-3640/RFC-3640.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 14516","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"ISO-IEC ISO/IEC 14533-4 V2019","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-262","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-322","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-412","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7144","to":"ISO-IEC ISO/IEC 14776-412","kind":"references","source":"IETF/RFC-7144/RFC-7144.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-414","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-452","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 14776-453","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 4011","to":"ISO-IEC ISO/IEC 14882-1998","kind":"references","source":"IETF/RFC-4011/RFC-4011.txt"},{"from":"IETF RFC 4137","to":"ISO-IEC ISO/IEC 14882 V2017","kind":"references","source":"IETF/RFC-4137/RFC-4137.txt"},{"from":"IETF RFC 8746","to":"ISO-IEC ISO/IEC 14882 V2017","kind":"references","source":"IETF/RFC-8746/RFC-8746.txt"},{"from":"IETF RFC 5639","to":"ISO-IEC ISO/IEC 14888","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 14888","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 14888-1","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 14888-1","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 14888-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 14888-2","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5114","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-5114/RFC-5114.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5639","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 6954","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 7027","to":"ISO-IEC ISO/IEC 14888-3 V2006","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 5511","to":"ISO-IEC ISO/IEC 14977","kind":"references","source":"IETF/RFC-5511/RFC-5511.txt"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO/IEC 15000-3 V2023","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"legal:2025-1942","to":"ISO-IEC ISO/IEC 15408-1 V2022","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1944","to":"ISO-IEC ISO/IEC 15408-1 V2022","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 15408-1 V2022","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"ISO-IEC ISO/IEC 15408-1 V2022","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 15408-1 V2022","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 15408-3 V2022","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-1929","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-1929/2025-1929.md"},{"from":"legal:2025-1942","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-1942/2025-1942.md"},{"from":"legal:2025-1943","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-1943/2025-1943.md"},{"from":"legal:2025-1944","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-1944/2025-1944.md"},{"from":"legal:2025-1946","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-1946/2025-1946.md"},{"from":"legal:2025-2531","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-2531/2025-2531.md"},{"from":"legal:2025-2532","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2025-2532/2025-2532.md"},{"from":"legal:2026-1735","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"cites","source":"implementing-acts/2026-1735/2026-1735.md"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 421 V1.3.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"ETSI TS 119 431-1 V1.3.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf"},{"from":"ETSI TS 119 441 V1.2.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 3647","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 5570","to":"ISO-IEC ISO/IEC 15408 V2022","kind":"references","source":"IETF/RFC-5570/RFC-5570.txt"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO/IEC 15504","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"IETF RFC 1638","to":"ISO-IEC ISO/IEC 15802","kind":"references","source":"IETF/RFC-1638/RFC-1638.txt"},{"from":"IETF RFC 2674","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-2674/RFC-2674.txt"},{"from":"IETF RFC 2815","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-2815/RFC-2815.txt"},{"from":"IETF RFC 2816","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2878","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-2878/RFC-2878.txt"},{"from":"IETF RFC 3270","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-3270/RFC-3270.txt"},{"from":"IETF RFC 3290","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-3290/RFC-3290.txt"},{"from":"IETF RFC 3518","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-3518/RFC-3518.txt"},{"from":"IETF RFC 4318","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-4318/RFC-4318.txt"},{"from":"IETF RFC 4363","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-4363/RFC-4363.txt"},{"from":"IETF RFC 4665","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-4665/RFC-4665.txt"},{"from":"IETF RFC 4761","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-4761/RFC-4761.txt"},{"from":"IETF RFC 4762","to":"ISO-IEC ISO/IEC 15802-3 V1998","kind":"references","source":"IETF/RFC-4762/RFC-4762.txt"},{"from":"IETF RFC 2427","to":"ISO-IEC ISO/IEC 15802-5","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 15945","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"IETF RFC 5639","to":"ISO-IEC ISO/IEC 15946","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 15946-1","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 15946-1","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5639","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 6954","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-6954/RFC-6954.txt"},{"from":"IETF RFC 7027","to":"ISO-IEC ISO/IEC 15946-2","kind":"references","source":"IETF/RFC-7027/RFC-7027.txt"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 15946-3","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 15946-3","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 15946-4","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 15946-4","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17000 V2020","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 17000 V2020","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO/IEC 17000 V2020","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17011 V2017","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17020 V2012","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17020 V2012","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 17021","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17021-1 V2015","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17021-1 V2015","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17025 V2017","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17025 V2017","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17029 V2019","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17065 V2012","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17065 V2012","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 17065 V2012","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 17067 V2013","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-2162","to":"ISO-IEC ISO/IEC 17067 V2013","kind":"cites","source":"implementing-acts/2025-2162/2025-2162.md"},{"from":"IETF RFC 9285","to":"ISO-IEC ISO/IEC 18004 V2015","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 18013","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 432 V1.3.1","to":"ISO-IEC ISO/IEC 18013","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"ISO-IEC ISO/IEC 18013","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"legal:2024-2977","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2024-2982","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"cites","source":"implementing-acts/2024-2982/2024-2982.md"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS04 V1.0.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ARF/TS04-V1.0.1/TS04-V1.0.1.md"},{"from":"ARF TS09 V1.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ARF/TS09-V1.1/TS09-V1.1.md"},{"from":"ARF TS10 V1.2","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS13","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ARF/TS13/TS13-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF SD-JWT","to":"ISO-IEC ISO/IEC 18013-5 V2021","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 18013-7 V2025","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 18013-7 V2025","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 3830","to":"ISO-IEC ISO/IEC 18014","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 4738","to":"ISO-IEC ISO/IEC 18014","kind":"references","source":"IETF/RFC-4738/RFC-4738.txt"},{"from":"IETF RFC 5197","to":"ISO-IEC ISO/IEC 18014","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"ETSI TS 119 431-1 V1.3.1","to":"ISO-IEC ISO/IEC 18014-2","kind":"references","source":"ETSI/TS-119-431-1-V1.3.1/TS-119-431-1-V1.3.1.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 18031 V2005","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 4753","to":"ISO-IEC ISO/IEC 18031 V2005","kind":"references","source":"IETF/RFC-4753/RFC-4753.txt"},{"from":"IETF RFC 5903","to":"ISO-IEC ISO/IEC 18031 V2005","kind":"references","source":"IETF/RFC-5903/RFC-5903.txt"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 18032","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 5639","to":"ISO-IEC ISO/IEC 18032","kind":"references","source":"IETF/RFC-5639/RFC-5639.txt"},{"from":"IETF RFC 4132","to":"ISO-IEC ISO/IEC 18033","kind":"references","source":"IETF/RFC-4132/RFC-4132.txt"},{"from":"IETF RFC 4312","to":"ISO-IEC ISO/IEC 18033","kind":"references","source":"IETF/RFC-4312/RFC-4312.txt"},{"from":"IETF RFC 3447","to":"ISO-IEC ISO/IEC 18033-2 V2010","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 5990","to":"ISO-IEC ISO/IEC 18033-2 V2010","kind":"references","source":"IETF/RFC-5990/RFC-5990.txt"},{"from":"IETF RFC 6931","to":"ISO-IEC ISO/IEC 18033-2 V2010","kind":"references","source":"IETF/RFC-6931/RFC-6931.txt"},{"from":"IETF RFC 9180","to":"ISO-IEC ISO/IEC 18033-2 V2010","kind":"references","source":"IETF/RFC-9180/RFC-9180.txt"},{"from":"IETF RFC 4162","to":"ISO-IEC ISO/IEC 18033-3","kind":"references","source":"IETF/RFC-4162/RFC-4162.txt"},{"from":"IETF RFC 5528","to":"ISO-IEC ISO/IEC 18033-3","kind":"references","source":"IETF/RFC-5528/RFC-5528.txt"},{"from":"ARF TS11 V1.0.1","to":"ISO-IEC ISO/IEC 18045 V2022","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 18370","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 18370-1 V2016","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 18370-2 V2016","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 19011 V2011","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"IETF RFC 5941","to":"ISO-IEC ISO/IEC 19501 V2005","kind":"references","source":"IETF/RFC-5941/RFC-5941.txt"},{"from":"IETF RFC 7143","to":"ISO-IEC ISO/IEC 19501 V2005","kind":"references","source":"IETF/RFC-7143/RFC-7143.txt"},{"from":"IETF RFC 7326","to":"ISO-IEC ISO/IEC 19501 V2005","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 6110","to":"ISO-IEC ISO/IEC 19757","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6110","to":"ISO-IEC ISO/IEC 19757-1","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6244","to":"ISO-IEC ISO/IEC 19757-1","kind":"references","source":"IETF/RFC-6244/RFC-6244.txt"},{"from":"IETF RFC 7952","to":"ISO-IEC ISO/IEC 19757-1","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 6022","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-6022/RFC-6022.txt"},{"from":"IETF RFC 6110","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 6501","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-6501/RFC-6501.txt"},{"from":"IETF RFC 7807","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-7807/RFC-7807.txt"},{"from":"IETF RFC 7952","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7991","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-7991/RFC-7991.txt"},{"from":"IETF RFC 8428","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-8428/RFC-8428.txt"},{"from":"IETF RFC 8610","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-8610/RFC-8610.txt"},{"from":"IETF RFC 9457","to":"ISO-IEC ISO/IEC 19757-2 V2008","kind":"references","source":"IETF/RFC-9457/RFC-9457.txt"},{"from":"IETF RFC 6110","to":"ISO-IEC ISO/IEC 19757-3 V2016","kind":"references","source":"IETF/RFC-6110/RFC-6110.txt"},{"from":"IETF RFC 7952","to":"ISO-IEC ISO/IEC 19757-3 V2016","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 7952","to":"ISO-IEC ISO/IEC 19757-8 V2008","kind":"references","source":"IETF/RFC-7952/RFC-7952.txt"},{"from":"IETF RFC 8412","to":"ISO-IEC ISO/IEC 19770-2 V2015","kind":"references","source":"IETF/RFC-8412/RFC-8412.txt"},{"from":"IETF RFC 9393","to":"ISO-IEC ISO/IEC 19770-2 V2015","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 9393","to":"ISO-IEC ISO/IEC 19770-5 V2015","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 19790 V2025","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 421 V1.3.1","to":"ISO-IEC ISO/IEC 19790 V2025","kind":"references","source":"ETSI/EN-319-421-V1.3.1/EN-319-421-V1.3.1.pdf"},{"from":"ETSI TS 119 441 V1.2.1","to":"ISO-IEC ISO/IEC 19790 V2025","kind":"references","source":"ETSI/TS-119-441-V1.2.1/TS-119-441-V1.2.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"ISO-IEC ISO/IEC 19790 V2025","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO/IEC 19790 V2025","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 19792","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 19794-5","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 19795-1","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO/IEC 1990","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 19989-1","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 19989-3","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 20008","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ARF TS14 V1.0","to":"ISO-IEC ISO/IEC 20008-1 V2013","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 20008-1 V2013","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 20008-2","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 20008-3","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 20059","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2157","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-2157/RFC-2157.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 4120","to":"ISO-IEC ISO/IEC 2022 V1994","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"ETSI EN 319 162-1 V1.1.1","to":"ISO-IEC ISO/IEC 21320-1","kind":"references","source":"ETSI/EN-319-162-1-V1.1.1/EN-319-162-1-V1.1.1.pdf"},{"from":"ETSI TS 119 511 V1.1.1","to":"ISO-IEC ISO/IEC 21320-1","kind":"references","source":"ETSI/TS-119-511-V1.1.1/TS-119-511-V1.1.1.pdf"},{"from":"IETF RFC 9535","to":"ISO-IEC ISO/IEC 22537 V2006","kind":"references","source":"IETF/RFC-9535/RFC-9535.txt"},{"from":"IETF RFC 7742","to":"ISO-IEC ISO/IEC 23001-8 V2013","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"ISO-IEC ISO/IEC 23220-2","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO/IEC 23220-2","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 23220-3","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 23220-4","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 6839","to":"ISO-IEC ISO/IEC 24824-1","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO/IEC 27000","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"legal:2025-1568","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"cites","source":"implementing-acts/2025-1568/2025-1568.md"},{"from":"ETSI EN 319 401 V3.2.1","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"references","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"ISO-IEC ISO/IEC 27001 V2022","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"ETSI EN 319 401 V3.2.1","to":"ISO-IEC ISO/IEC 27002 V2022","kind":"references","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 27002 V2022","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 27002 V2022","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 27002 V2022","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 101 V1.1.1","to":"ISO-IEC ISO/IEC 27002 V2022","kind":"references","source":"ETSI/TS-119-101-V1.1.1/TS-119-101-V1.1.1.pdf"},{"from":"ETSI EN 319 401 V3.2.1","to":"ISO-IEC ISO/IEC 27005 V2022","kind":"references","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf"},{"from":"ETSI EN 319 403-1 V2.3.1","to":"ISO-IEC ISO/IEC 27006","kind":"references","source":"ETSI/EN-319-403-1-V2.3.1/EN-319-403-1-V2.3.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 27565","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI EN 319 401 V3.2.1","to":"ISO-IEC ISO/IEC 27701 V2019","kind":"references","source":"ETSI/EN-319-401-V3.2.1/EN-319-401-V3.2.1.pdf"},{"from":"ARF TS02 V1.0.1","to":"ISO-IEC ISO/IEC 29100 V2011","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"ISO-IEC ISO/IEC 29500-2 V2021","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 29794-5","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 30107","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 30107-1","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"ETSI TS 119 461 V2.1.1","to":"ISO-IEC ISO/IEC 30107-3","kind":"references","source":"ETSI/TS-119-461-V2.1.1/TS-119-461-V2.1.1.pdf"},{"from":"legal:2024-2981","to":"ISO-IEC ISO/IEC 30111 V2019","kind":"cites","source":"implementing-acts/2024-2981/2024-2981.md"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 3166","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 3166-1","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 1662","to":"ISO-IEC ISO/IEC 3309 V1991","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"IETF RFC 3819","to":"ISO-IEC ISO/IEC 3309 V1991","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 39794-5","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"IETF RFC 1662","to":"ISO-IEC ISO/IEC 4335 V1991","kind":"references","source":"IETF/RFC-1662/RFC-1662.txt"},{"from":"legal:2024-2977","to":"ISO-IEC ISO/IEC 5218","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2026-1731","to":"ISO-IEC ISO/IEC 5218","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ETSI TS 119 602 V1.1.1","to":"ISO-IEC ISO/IEC 6429 V1992","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO/IEC 6429 V1992","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 1556","to":"ISO-IEC ISO/IEC 6429 V1992","kind":"references","source":"IETF/RFC-1556/RFC-1556.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO/IEC 6429 V1992","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 1468","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-1468/RFC-1468.txt"},{"from":"IETF RFC 1866","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-1866/RFC-1866.txt"},{"from":"IETF RFC 1922","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-1922/RFC-1922.txt"},{"from":"IETF RFC 3467","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-3467/RFC-3467.txt"},{"from":"IETF RFC 4120","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4646","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-4646/RFC-4646.txt"},{"from":"IETF RFC 5408","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5646","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-5646/RFC-5646.txt"},{"from":"IETF RFC 6365","to":"ISO-IEC ISO/IEC 646 V1991","kind":"references","source":"IETF/RFC-6365/RFC-6365.txt"},{"from":"IETF RFC 2130","to":"ISO-IEC ISO/IEC 7498-1 V1994","kind":"references","source":"IETF/RFC-2130/RFC-2130.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 7498-1 V1994","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 7498-1 V1994","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 7498-2","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 7498-4","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 7498-4","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 7174","to":"ISO-IEC ISO/IEC 7498-4","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 7499-2","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 7499-2","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 7812-1 V2006","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 7812-1 V2006","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 6030","to":"ISO-IEC ISO/IEC 7812-1 V2006","kind":"references","source":"IETF/RFC-6030/RFC-6030.txt"},{"from":"IETF RFC 6031","to":"ISO-IEC ISO/IEC 7812-1 V2006","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6920","to":"ISO-IEC ISO/IEC 7812-1 V2006","kind":"references","source":"IETF/RFC-6920/RFC-6920.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 7812-2 V1993","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 7812-2 V1993","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2883","to":"ISO-IEC ISO/IEC 8073","kind":"references","source":"IETF/RFC-2883/RFC-2883.txt"},{"from":"IETF RFC 1356","to":"ISO-IEC ISO/IEC 8208","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1382","to":"ISO-IEC ISO/IEC 8208","kind":"references","source":"IETF/RFC-1382/RFC-1382.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO/IEC 8208","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 5024","to":"ISO-IEC ISO/IEC 8208","kind":"references","source":"IETF/RFC-5024/RFC-5024.txt"},{"from":"IETF RFC 6328","to":"ISO-IEC ISO/IEC 8208","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO/IEC 8348","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1768","to":"ISO-IEC ISO/IEC 8348","kind":"references","source":"IETF/RFC-1768/RFC-1768.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO/IEC 8348","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 4715","to":"ISO-IEC ISO/IEC 8348","kind":"references","source":"IETF/RFC-4715/RFC-4715.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO/IEC 8348-1992","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1356","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 1752","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-1752/RFC-1752.txt"},{"from":"IETF RFC 1755","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 1888","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2331","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 3606","to":"ISO-IEC ISO/IEC 8473","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 3719","to":"ISO-IEC ISO/IEC 8473-1","kind":"references","source":"IETF/RFC-3719/RFC-3719.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO/IEC 8473-1992","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 3525","to":"ISO-IEC ISO/IEC 8802","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4259","to":"ISO-IEC ISO/IEC 8802","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4326","to":"ISO-IEC ISO/IEC 8802","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4947","to":"ISO-IEC ISO/IEC 8802","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 1749","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2363","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2885","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3355","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 4326","to":"ISO-IEC ISO/IEC 8802-2","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 2464","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-2464/RFC-2464.txt"},{"from":"IETF RFC 2816","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 2889","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-2889/RFC-2889.txt"},{"from":"IETF RFC 3580","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-3580/RFC-3580.txt"},{"from":"IETF RFC 3927","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 4326","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-4326/RFC-4326.txt"},{"from":"IETF RFC 4448","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-4448/RFC-4448.txt"},{"from":"IETF RFC 4947","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-4947/RFC-4947.txt"},{"from":"IETF RFC 5163","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-5163/RFC-5163.txt"},{"from":"IETF RFC 5184","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-5184/RFC-5184.txt"},{"from":"IETF RFC 5227","to":"ISO-IEC ISO/IEC 8802-3 V2000","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 1749","to":"ISO-IEC ISO/IEC 8802-5","kind":"references","source":"IETF/RFC-1749/RFC-1749.txt"},{"from":"IETF RFC 2475","to":"ISO-IEC ISO/IEC 8802-5","kind":"references","source":"IETF/RFC-2475/RFC-2475.txt"},{"from":"IETF RFC 2816","to":"ISO-IEC ISO/IEC 8802-5","kind":"references","source":"IETF/RFC-2816/RFC-2816.txt"},{"from":"IETF RFC 3927","to":"ISO-IEC ISO/IEC 8802-5","kind":"references","source":"IETF/RFC-3927/RFC-3927.txt"},{"from":"IETF RFC 5227","to":"ISO-IEC ISO/IEC 8802-5","kind":"references","source":"IETF/RFC-5227/RFC-5227.txt"},{"from":"IETF RFC 1508","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-1508/RFC-1508.txt"},{"from":"IETF RFC 2078","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-2078/RFC-2078.txt"},{"from":"IETF RFC 2156","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2743","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 3854","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 4511","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 5940","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 6031","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6487","to":"ISO-IEC ISO/IEC 8824","kind":"references","source":"IETF/RFC-6487/RFC-6487.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2898","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3739","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 4325","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4512","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4520","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4520/RFC-4520.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4531","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4537","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5246","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5480","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5485","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5649","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5750","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5755","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5877","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5915","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6256","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6278","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 6961","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 7030","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8411","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8418","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8550","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8619","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 9345","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-9345/RFC-9345.pdf"},{"from":"IETF RFC 9562","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9608","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"ISO-IEC ISO/IEC 8824-1 V2021","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2898","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5649","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6278","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ISO-IEC ISO/IEC 8824-2 V2015","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2898","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5649","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ISO-IEC ISO/IEC 8824-3 V2015","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2898","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-2898/RFC-2898.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5649","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6278","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-6278/RFC-6278.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8018","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-8018/RFC-8018.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ISO-IEC ISO/IEC 8824-4 V2015","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 88247-3 V2008","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 9608","to":"ISO-IEC ISO/IEC 8825-1-2021","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2560","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3161","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-3161/RFC-3161.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3779","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3854","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 4511","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 4522","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4523","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4523/RFC-4523.txt"},{"from":"IETF RFC 4531","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4531/RFC-4531.txt"},{"from":"IETF RFC 4537","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5246","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5326","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5326/RFC-5326.txt"},{"from":"IETF RFC 5485","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5751","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5755","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5877","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5915","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5967","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 6256","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6256/RFC-6256.txt"},{"from":"IETF RFC 6482","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6486","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6698","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6839","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6960","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 7030","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7250","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 7468","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 8418","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8446","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"IETF RFC 8551","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8572","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8619","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 9162","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9277","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9345","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-9345/RFC-9345.txt"},{"from":"IETF RFC 9525","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9999","to":"ISO-IEC ISO/IEC 8825-1 V2021","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 5480","to":"ISO-IEC ISO/IEC 8825-2 V2002","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 1508","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-1508/RFC-1508.txt"},{"from":"IETF RFC 1698","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-1698/RFC-1698.txt"},{"from":"IETF RFC 2078","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-2078/RFC-2078.txt"},{"from":"IETF RFC 2743","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-2743/RFC-2743.txt"},{"from":"IETF RFC 5050","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-5050/RFC-5050.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 6031","to":"ISO-IEC ISO/IEC 8825 V1987","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 4120","to":"ISO-IEC ISO/IEC 8859","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2566","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-2566/RFC-2566.txt"},{"from":"IETF RFC 2911","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-2911/RFC-2911.txt"},{"from":"IETF RFC 3875","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-3875/RFC-3875.txt"},{"from":"IETF RFC 3977","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-3977/RFC-3977.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5987","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-5987/RFC-5987.txt"},{"from":"IETF RFC 6266","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-6266/RFC-6266.txt"},{"from":"IETF RFC 6331","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-6331/RFC-6331.txt"},{"from":"IETF RFC 7230","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-7230/RFC-7230.txt"},{"from":"IETF RFC 7617","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-7617/RFC-7617.txt"},{"from":"IETF RFC 9110","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-9110/RFC-9110.pdf"},{"from":"IETF RFC 9285","to":"ISO-IEC ISO/IEC 8859-1 V1998","kind":"references","source":"IETF/RFC-9285/RFC-9285.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO/IEC 8859-10 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO/IEC 8859-10 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO/IEC 8859-10 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-10 V1999","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-13 V1998","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-14 V1998","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-15 V1999","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-16 V2001","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-6 V1999","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-7 V2003","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2640","to":"ISO-IEC ISO/IEC 8859-8 V1999","kind":"references","source":"IETF/RFC-2640/RFC-2640.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-8 V1999","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2049","to":"ISO-IEC ISO/IEC 8859-9 V1999","kind":"references","source":"IETF/RFC-2049/RFC-2049.txt"},{"from":"IETF RFC 2278","to":"ISO-IEC ISO/IEC 8859-9 V1999","kind":"references","source":"IETF/RFC-2278/RFC-2278.txt"},{"from":"IETF RFC 2978","to":"ISO-IEC ISO/IEC 8859-9 V1999","kind":"references","source":"IETF/RFC-2978/RFC-2978.txt"},{"from":"IETF RFC 6055","to":"ISO-IEC ISO/IEC 8859-9 V1999","kind":"references","source":"IETF/RFC-6055/RFC-6055.txt"},{"from":"IETF RFC 2445","to":"ISO-IEC ISO/IEC 9070 V1991","kind":"references","source":"IETF/RFC-2445/RFC-2445.txt"},{"from":"IETF RFC 3151","to":"ISO-IEC ISO/IEC 9070 V1991","kind":"references","source":"IETF/RFC-3151/RFC-3151.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO/IEC 9070 V1991","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 5323","to":"ISO-IEC ISO/IEC 9075-2 V1999","kind":"references","source":"IETF/RFC-5323/RFC-5323.txt"},{"from":"IETF RFC 5141","to":"ISO-IEC ISO/IEC 9075-3","kind":"references","source":"IETF/RFC-5141/RFC-5141.txt"},{"from":"IETF RFC 4297","to":"ISO-IEC ISO/IEC 9314","kind":"references","source":"IETF/RFC-4297/RFC-4297.txt"},{"from":"IETF RFC 1292","to":"ISO-IEC ISO/IEC 9495","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"IETF RFC 1356","to":"ISO-IEC ISO/IEC 9542 V1988","kind":"references","source":"IETF/RFC-1356/RFC-1356.txt"},{"from":"IETF RFC 1561","to":"ISO-IEC ISO/IEC 9542 V1988","kind":"references","source":"IETF/RFC-1561/RFC-1561.txt"},{"from":"IETF RFC 6213","to":"ISO-IEC ISO/IEC 9577","kind":"references","source":"IETF/RFC-6213/RFC-6213.txt"},{"from":"IETF RFC 6328","to":"ISO-IEC ISO/IEC 9577","kind":"references","source":"IETF/RFC-6328/RFC-6328.txt"},{"from":"IETF RFC 1292","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-1292/RFC-1292.txt"},{"from":"IETF RFC 3546","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 4366","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4510","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4518","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4524","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-4524/RFC-4524.txt"},{"from":"IETF RFC 5750","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 6066","to":"ISO-IEC ISO/IEC 9594","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 2312","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2632","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3698","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-3698/RFC-3698.txt"},{"from":"IETF RFC 3850","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4510","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4512","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4512/RFC-4512.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 4519","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4522","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5755","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 8550","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 9562","to":"ISO-IEC ISO/IEC 9594-1 V2017","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 2025","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2312","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2407","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2510","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2608","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2632","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3739","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5755","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 9594-2 V2005","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 4510","to":"ISO-IEC ISO/IEC 9594-3 V1993","kind":"references","source":"IETF/RFC-4510/RFC-4510.txt"},{"from":"IETF RFC 4514","to":"ISO-IEC ISO/IEC 9594-3 V1993","kind":"references","source":"IETF/RFC-4514/RFC-4514.txt"},{"from":"IETF RFC 4521","to":"ISO-IEC ISO/IEC 9594-3 V1993","kind":"references","source":"IETF/RFC-4521/RFC-4521.txt"},{"from":"IETF RFC 2120","to":"ISO-IEC ISO/IEC 9594-4 V1993","kind":"references","source":"IETF/RFC-2120/RFC-2120.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 2312","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2510","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2608","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2632","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 3641","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3739","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4517","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4518","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-4518/RFC-4518.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5958","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 9594-6 V2008","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 2510","to":"ISO-IEC ISO/IEC 9594-7 V1997","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2608","to":"ISO-IEC ISO/IEC 9594-7 V1997","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 9594-7 V1997","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"ETSI EN 319 102-1 V1.4.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-102-1-V1.4.1/EN-319-102-1-V1.4.1.pdf"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-2 V2.6.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 412-3 V1.3.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf"},{"from":"ETSI EN 319 412-5 V2.6.0","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 119 412-6 V1.2.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2025","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 2312","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2407","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2407/RFC-2407.txt"},{"from":"IETF RFC 2510","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2510/RFC-2510.txt"},{"from":"IETF RFC 2527","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 2608","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2608/RFC-2608.txt"},{"from":"IETF RFC 2632","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2752","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2752/RFC-2752.txt"},{"from":"IETF RFC 2801","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2801/RFC-2801.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2985","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2985/RFC-2985.txt"},{"from":"IETF RFC 2986","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3075","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3182","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3182/RFC-3182.txt"},{"from":"IETF RFC 3275","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3280","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3379","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3447","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 3520","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3520/RFC-3520.txt"},{"from":"IETF RFC 3546","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3647","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3739","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4210","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4366","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5091","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-5091/RFC-5091.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5937","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 6066","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6484","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6818","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 7292","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-7292/RFC-7292.txt"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 8122","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-8122/RFC-8122.txt"},{"from":"IETF RFC 8226","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 9525","to":"ISO-IEC ISO/IEC 9594-8 V2020","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 2120","to":"ISO-IEC ISO/IEC 9594-9 V1993","kind":"references","source":"IETF/RFC-2120/RFC-2120.txt"},{"from":"IETF RFC 3447","to":"ISO-IEC ISO/IEC 9796-1","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO/IEC 9796-1","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 9796-2 V2010","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 102 176-1 V2.0.0","to":"ISO-IEC ISO/IEC 9796-2 V2010","kind":"references","source":"ETSI/TS-102-176-1-V2.0.0/TS-102-176-1-V2.0.0.pdf"},{"from":"IETF RFC 3447","to":"ISO-IEC ISO/IEC 9796-2 V2010","kind":"references","source":"IETF/RFC-3447/RFC-3447.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 9796-2 V2010","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 8017","to":"ISO-IEC ISO/IEC 9796-2 V2010","kind":"references","source":"IETF/RFC-8017/RFC-8017.txt"},{"from":"IETF RFC 5126","to":"ISO-IEC ISO/IEC 9796-4","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ISO-IEC ISO/IEC 9796 V1991","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TR 119 476 V1.2.1","to":"ISO-IEC ISO/IEC 9796 V1991","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"IETF RFC 5832","to":"ISO-IEC ISO/IEC 9796 V1991","kind":"references","source":"IETF/RFC-5832/RFC-5832.txt"},{"from":"IETF RFC 9101","to":"ISO-IEC ISO/IEC 9798","kind":"references","source":"IETF/RFC-9101/RFC-9101.txt"},{"from":"IETF RFC 2025","to":"ISO-IEC ISO/IEC 9798-3","kind":"references","source":"IETF/RFC-2025/RFC-2025.txt"},{"from":"IETF RFC 3830","to":"ISO-IEC ISO/IEC 9798-3","kind":"references","source":"IETF/RFC-3830/RFC-3830.txt"},{"from":"IETF RFC 1430","to":"ISO-IEC ISO/IEC 9834-1 V2005","kind":"references","source":"IETF/RFC-1430/RFC-1430.txt"},{"from":"IETF RFC 3001","to":"ISO-IEC ISO/IEC 9834-1 V2005","kind":"references","source":"IETF/RFC-3001/RFC-3001.txt"},{"from":"IETF RFC 3061","to":"ISO-IEC ISO/IEC 9834-1 V2005","kind":"references","source":"IETF/RFC-3061/RFC-3061.txt"},{"from":"IETF RFC 5280","to":"ISO-IEC ISO/IEC 9834-1 V2005","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 9562","to":"ISO-IEC ISO/IEC 9834-1 V2005","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 4122","to":"ISO-IEC ISO/IEC 9834-8 V2004","kind":"references","source":"IETF/RFC-4122/RFC-4122.txt"},{"from":"IETF RFC 9562","to":"ISO-IEC ISO/IEC 9834-8 V2004","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 2244","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-2244/RFC-2244.txt"},{"from":"IETF RFC 4737","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 4997","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-4997/RFC-4997.txt"},{"from":"IETF RFC 5137","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-5137/RFC-5137.txt"},{"from":"IETF RFC 6386","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-6386/RFC-6386.txt"},{"from":"IETF RFC 6557","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-6557/RFC-6557.txt"},{"from":"IETF RFC 8746","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-8746/RFC-8746.pdf"},{"from":"IETF RFC 8949","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9277","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9741","to":"ISO-IEC ISO/IEC 9899 V2024","kind":"references","source":"IETF/RFC-9741/RFC-9741.txt"},{"from":"IETF RFC 2307","to":"ISO-IEC ISO/IEC 9945-1 V1990","kind":"references","source":"IETF/RFC-2307/RFC-2307.txt"},{"from":"IETF RFC 2828","to":"ISO-IEC ISO/IEC 9945-1 V1990","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ISO-IEC ISO/IEC 9945-1 V1990","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 1345","to":"ISO-IEC ISO/IEC 9945-2 V1993","kind":"references","source":"IETF/RFC-1345/RFC-1345.txt"},{"from":"IETF RFC 2277","to":"ISO-IEC ISO/IEC 9945-2 V1993","kind":"references","source":"IETF/RFC-2277/RFC-2277.txt"},{"from":"IETF RFC 3493","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-3493/RFC-3493.txt"},{"from":"IETF RFC 3542","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-3542/RFC-3542.txt"},{"from":"IETF RFC 3678","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-3678/RFC-3678.txt"},{"from":"IETF RFC 4795","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-4795/RFC-4795.txt"},{"from":"IETF RFC 5405","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-5405/RFC-5405.txt"},{"from":"IETF RFC 5482","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-5482/RFC-5482.txt"},{"from":"IETF RFC 6434","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-6434/RFC-6434.txt"},{"from":"IETF RFC 8085","to":"ISO-IEC ISO/IEC 9945 V2009","kind":"references","source":"IETF/RFC-8085/RFC-8085.txt"},{"from":"IETF RFC 3689","to":"ITU-T ITU-T E.106","kind":"references","source":"IETF/RFC-3689/RFC-3689.txt"},{"from":"IETF RFC 4190","to":"ITU-T ITU-T E.106","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 4542","to":"ITU-T ITU-T E.106","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 2007","to":"ITU-T ITU-T E.123","kind":"references","source":"IETF/RFC-2007/RFC-2007.txt"},{"from":"IETF RFC 2806","to":"ITU-T ITU-T E.123","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 3966","to":"ITU-T ITU-T E.123","kind":"references","source":"IETF/RFC-3966/RFC-3966.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T E.123","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T E.123","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 1888","to":"ITU-T ITU-T E.163","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 1888","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2127","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 2590","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-2590/RFC-2590.txt"},{"from":"IETF RFC 2806","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 2848","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2954","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3017","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 3172","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3172/RFC-3172.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3482","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3733","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3733/RFC-3733.txt"},{"from":"IETF RFC 3761","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3761/RFC-3761.txt"},{"from":"IETF RFC 3982","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-3982/RFC-3982.txt"},{"from":"IETF RFC 4006","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 4497","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-4497/RFC-4497.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4566","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-4566/RFC-4566.txt"},{"from":"IETF RFC 4694","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 5456","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 5486","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 7195","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7970","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-7970/RFC-7970.txt"},{"from":"IETF RFC 8224","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-8224/RFC-8224.txt"},{"from":"IETF RFC 8866","to":"ITU-T ITU-T E.164","kind":"references","source":"IETF/RFC-8866/RFC-8866.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T E.180","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T E.180","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T E.180","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T E.180","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 7462","to":"ITU-T ITU-T E.182","kind":"references","source":"IETF/RFC-7462/RFC-7462.txt"},{"from":"IETF RFC 4006","to":"ITU-T ITU-T E.212","kind":"references","source":"IETF/RFC-4006/RFC-4006.txt"},{"from":"IETF RFC 5580","to":"ITU-T ITU-T E.212","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 5976","to":"ITU-T ITU-T E.361","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 3272","to":"ITU-T ITU-T E.600","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 3449","to":"ITU-T ITU-T E.681","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 3272","to":"ITU-T ITU-T E.701","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 6390","to":"ITU-T ITU-T E.800","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 3272","to":"ITU-T ITU-T E.801","kind":"references","source":"IETF/RFC-3272/RFC-3272.txt"},{"from":"IETF RFC 8098","to":"ITU-T ITU-T F.400","kind":"references","source":"IETF/RFC-8098/RFC-8098.txt"},{"from":"IETF RFC 5194","to":"ITU-T ITU-T F.700","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 4103","to":"ITU-T ITU-T F.703","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 5194","to":"ITU-T ITU-T F.703","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 4594","to":"ITU-T ITU-T G.101","kind":"references","source":"IETF/RFC-4594/RFC-4594.txt"},{"from":"IETF RFC 5481","to":"ITU-T ITU-T G.102","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 6035","to":"ITU-T ITU-T G.102","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6798","to":"ITU-T ITU-T G.102","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 5481","to":"ITU-T ITU-T G.105","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.107","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 3611","to":"ITU-T ITU-T G.107","kind":"references","source":"IETF/RFC-3611/RFC-3611.txt"},{"from":"IETF RFC 6035","to":"ITU-T ITU-T G.107","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6390","to":"ITU-T ITU-T G.107","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T G.107","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T G.107.1","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.108","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T G.108","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.113","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.114","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 5836","to":"ITU-T ITU-T G.114","kind":"references","source":"IETF/RFC-5836/RFC-5836.txt"},{"from":"IETF RFC 6817","to":"ITU-T ITU-T G.114","kind":"references","source":"IETF/RFC-6817/RFC-6817.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"ITU-T ITU-T G.117","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.131","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T G.164","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T G.165","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.168","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.169","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.177","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 4504","to":"ITU-T ITU-T G.177","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.191","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"ITU-T ITU-T G.227","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.691","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.702","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.702","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"ITU-T ITU-T G.703","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.703","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.703","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"ITU-T ITU-T G.704","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"IETF RFC 2495","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 3895","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5086","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T G.704","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.706","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.706","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5086","to":"ITU-T ITU-T G.706","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 3471","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-3471/RFC-3471.txt"},{"from":"IETF RFC 3946","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4207","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-4207/RFC-4207.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4842","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 6371","to":"ITU-T ITU-T G.707","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 3946","to":"ITU-T ITU-T G.708","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.709","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3945","to":"ITU-T ITU-T G.709","kind":"references","source":"IETF/RFC-3945/RFC-3945.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.711","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 1890","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 3389","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3714","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-3714/RFC-3714.txt"},{"from":"IETF RFC 3951","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-3951/RFC-3951.txt"},{"from":"IETF RFC 3952","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-3952/RFC-3952.txt"},{"from":"IETF RFC 4504","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-4504/RFC-4504.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 5486","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-5486/RFC-5486.txt"},{"from":"IETF RFC 5975","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 6464","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-6464/RFC-6464.txt"},{"from":"IETF RFC 6465","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-6465/RFC-6465.txt"},{"from":"IETF RFC 7874","to":"ITU-T ITU-T G.711","kind":"references","source":"IETF/RFC-7874/RFC-7874.txt"},{"from":"IETF RFC 8854","to":"ITU-T ITU-T G.711.1","kind":"references","source":"IETF/RFC-8854/RFC-8854.txt"},{"from":"IETF RFC 5404","to":"ITU-T ITU-T G.719","kind":"references","source":"IETF/RFC-5404/RFC-5404.txt"},{"from":"IETF RFC 1890","to":"ITU-T ITU-T G.722","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T G.722","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.722","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3047","to":"ITU-T ITU-T G.722.1","kind":"references","source":"IETF/RFC-3047/RFC-3047.txt"},{"from":"IETF RFC 3389","to":"ITU-T ITU-T G.722.1","kind":"references","source":"IETF/RFC-3389/RFC-3389.txt"},{"from":"IETF RFC 3794","to":"ITU-T ITU-T G.722.1","kind":"references","source":"IETF/RFC-3794/RFC-3794.txt"},{"from":"IETF RFC 6366","to":"ITU-T ITU-T G.722.1","kind":"references","source":"IETF/RFC-6366/RFC-6366.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T G.723.1","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T G.726","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 2422","to":"ITU-T ITU-T G.726","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.726","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3802","to":"ITU-T ITU-T G.726","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 1890","to":"ITU-T ITU-T G.728","kind":"references","source":"IETF/RFC-1890/RFC-1890.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T G.728","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.728","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T G.729","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T G.729","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.732","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.751","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T G.751","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 3474","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-3474/RFC-3474.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 4394","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 5718","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-5718/RFC-5718.txt"},{"from":"IETF RFC 5921","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 5951","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.771","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 2495","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 3895","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5086","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 7893","to":"ITU-T ITU-T G.775","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 3498","to":"ITU-T ITU-T G.783","kind":"references","source":"IETF/RFC-3498/RFC-3498.txt"},{"from":"IETF RFC 4394","to":"ITU-T ITU-T G.783","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4842","to":"ITU-T ITU-T G.783","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 4842","to":"ITU-T ITU-T G.784","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.798","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 7226","to":"ITU-T ITU-T G.800","kind":"references","source":"IETF/RFC-7226/RFC-7226.txt"},{"from":"IETF RFC 7276","to":"ITU-T ITU-T G.801","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7455","to":"ITU-T ITU-T G.801","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 7456","to":"ITU-T ITU-T G.801","kind":"references","source":"IETF/RFC-7456/RFC-7456.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.802","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 3946","to":"ITU-T ITU-T G.803","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 4830","to":"ITU-T ITU-T G.803","kind":"references","source":"IETF/RFC-4830/RFC-4830.txt"},{"from":"IETF RFC 7209","to":"ITU-T ITU-T G.803","kind":"references","source":"IETF/RFC-7209/RFC-7209.txt"},{"from":"IETF RFC 3916","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-3916/RFC-3916.txt"},{"from":"IETF RFC 4394","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 5654","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5921","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 6371","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.805","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 4842","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 5860","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 5951","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6371","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7276","to":"ITU-T ITU-T G.806","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 4397","to":"ITU-T ITU-T G.807","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 4258","to":"ITU-T ITU-T G.808","kind":"references","source":"IETF/RFC-4258/RFC-4258.txt"},{"from":"IETF RFC 4394","to":"ITU-T ITU-T G.808","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 4397","to":"ITU-T ITU-T G.808","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 5654","to":"ITU-T ITU-T G.808","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 5921","to":"ITU-T ITU-T G.808","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.810","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.810","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.811","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 7276","to":"ITU-T ITU-T G.811","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 5317","to":"ITU-T ITU-T G.813","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.821","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T G.823","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T G.824","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 4842","to":"ITU-T ITU-T G.825","kind":"references","source":"IETF/RFC-4842/RFC-4842.txt"},{"from":"IETF RFC 2495","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-2495/RFC-2495.txt"},{"from":"IETF RFC 2558","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-2558/RFC-2558.txt"},{"from":"IETF RFC 3592","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-3592/RFC-3592.txt"},{"from":"IETF RFC 3895","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4553","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-4553/RFC-4553.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5086","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-5086/RFC-5086.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 7893","to":"ITU-T ITU-T G.826","kind":"references","source":"IETF/RFC-7893/RFC-7893.txt"},{"from":"IETF RFC 3946","to":"ITU-T ITU-T G.832","kind":"references","source":"IETF/RFC-3946/RFC-3946.txt"},{"from":"IETF RFC 5317","to":"ITU-T ITU-T G.841","kind":"references","source":"IETF/RFC-5317/RFC-5317.pdf"},{"from":"IETF RFC 5951","to":"ITU-T ITU-T G.860","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.872","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 4397","to":"ITU-T ITU-T G.872","kind":"references","source":"IETF/RFC-4397/RFC-4397.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T G.872","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.874","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.874.1","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 7224","to":"ITU-T ITU-T G.948","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3591","to":"ITU-T ITU-T G.957","kind":"references","source":"IETF/RFC-3591/RFC-3591.txt"},{"from":"IETF RFC 7224","to":"ITU-T ITU-T G.984.2","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 7224","to":"ITU-T ITU-T G.989","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"IETF RFC 3276","to":"ITU-T ITU-T G.991.2","kind":"references","source":"IETF/RFC-3276/RFC-3276.txt"},{"from":"IETF RFC 4319","to":"ITU-T ITU-T G.991.2","kind":"references","source":"IETF/RFC-4319/RFC-4319.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T G.992.1","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 3449","to":"ITU-T ITU-T G.992.1","kind":"references","source":"IETF/RFC-3449/RFC-3449.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.992.1","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.992.1","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T G.992.2","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.992.2","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.992.2","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.992.3","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.992.3","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.992.4","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.992.4","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.992.5","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.992.5","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 3728","to":"ITU-T ITU-T G.993.1","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.993.1","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.993.2","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.993.2","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5851","to":"ITU-T ITU-T G.993.2","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6320","to":"ITU-T ITU-T G.993.2","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 7224","to":"ITU-T ITU-T G.993.2","kind":"references","source":"IETF/RFC-7224/RFC-7224.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T G.994.1","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.994.1","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 7228","to":"ITU-T ITU-T G.995","kind":"references","source":"IETF/RFC-7228/RFC-7228.txt"},{"from":"IETF RFC 7421","to":"ITU-T ITU-T G.995","kind":"references","source":"IETF/RFC-7421/RFC-7421.txt"},{"from":"IETF RFC 7428","to":"ITU-T ITU-T G.995","kind":"references","source":"IETF/RFC-7428/RFC-7428.txt"},{"from":"IETF RFC 8064","to":"ITU-T ITU-T G.995","kind":"references","source":"IETF/RFC-8064/RFC-8064.txt"},{"from":"IETF RFC 3728","to":"ITU-T ITU-T G.997.1","kind":"references","source":"IETF/RFC-3728/RFC-3728.txt"},{"from":"IETF RFC 4706","to":"ITU-T ITU-T G.997.1","kind":"references","source":"IETF/RFC-4706/RFC-4706.txt"},{"from":"IETF RFC 5650","to":"ITU-T ITU-T G.997.1","kind":"references","source":"IETF/RFC-5650/RFC-5650.txt"},{"from":"IETF RFC 5851","to":"ITU-T ITU-T G.997.1","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6320","to":"ITU-T ITU-T G.998.1","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 6320","to":"ITU-T ITU-T G.998.2","kind":"references","source":"IETF/RFC-6320/RFC-6320.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.221","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.221","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.221","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T H.222.1","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 2190","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 2689","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3984","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 6184","to":"ITU-T ITU-T H.223","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.225.0","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.225.0","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3508","to":"ITU-T ITU-T H.225.0","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.225.0","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.226","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.235","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.235","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3508","to":"ITU-T ITU-T H.235","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.235","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4046","to":"ITU-T ITU-T H.235","kind":"references","source":"IETF/RFC-4046/RFC-4046.txt"},{"from":"IETF RFC 4650","to":"ITU-T ITU-T H.235.0","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 4650","to":"ITU-T ITU-T H.235.7","kind":"references","source":"IETF/RFC-4650/RFC-4650.txt"},{"from":"IETF RFC 5197","to":"ITU-T ITU-T H.235.7","kind":"references","source":"IETF/RFC-5197/RFC-5197.txt"},{"from":"IETF RFC 3984","to":"ITU-T ITU-T H.241","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 6184","to":"ITU-T ITU-T H.241","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 2689","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3984","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4094","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4585","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 5939","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-5939/RFC-5939.txt"},{"from":"IETF RFC 6184","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"ITU-T ITU-T H.245","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.246","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.246","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.246","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.248","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.248","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 4190","to":"ITU-T ITU-T H.248","kind":"references","source":"IETF/RFC-4190/RFC-4190.txt"},{"from":"IETF RFC 8859","to":"ITU-T ITU-T H.248","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.248.1","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 5125","to":"ITU-T ITU-T H.248.1","kind":"references","source":"IETF/RFC-5125/RFC-5125.txt"},{"from":"IETF RFC 8859","to":"ITU-T ITU-T H.248.15","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.248.8","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 2032","to":"ITU-T ITU-T H.261","kind":"references","source":"IETF/RFC-2032/RFC-2032.txt"},{"from":"IETF RFC 2190","to":"ITU-T ITU-T H.261","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T H.261","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4587","to":"ITU-T ITU-T H.261","kind":"references","source":"IETF/RFC-4587/RFC-4587.txt"},{"from":"IETF RFC 2190","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-2190/RFC-2190.txt"},{"from":"IETF RFC 2429","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-2429/RFC-2429.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3555","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-3555/RFC-3555.txt"},{"from":"IETF RFC 3828","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 4585","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-4585/RFC-4585.txt"},{"from":"IETF RFC 4629","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-4629/RFC-4629.txt"},{"from":"IETF RFC 5109","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-5109/RFC-5109.txt"},{"from":"IETF RFC 6236","to":"ITU-T ITU-T H.263","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 3828","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-3828/RFC-3828.txt"},{"from":"IETF RFC 3984","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 6184","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 6190","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-6190/RFC-6190.txt"},{"from":"IETF RFC 6236","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-6236/RFC-6236.txt"},{"from":"IETF RFC 7742","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 8851","to":"ITU-T ITU-T H.264","kind":"references","source":"IETF/RFC-8851/RFC-8851.txt"},{"from":"IETF RFC 7742","to":"ITU-T ITU-T H.265","kind":"references","source":"IETF/RFC-7742/RFC-7742.txt"},{"from":"IETF RFC 2805","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3234","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3234/RFC-3234.txt"},{"from":"IETF RFC 3303","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3303/RFC-3303.txt"},{"from":"IETF RFC 3508","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3508/RFC-3508.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4094","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-4094/RFC-4094.txt"},{"from":"IETF RFC 4694","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-4694/RFC-4694.txt"},{"from":"IETF RFC 5117","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-5117/RFC-5117.txt"},{"from":"IETF RFC 5341","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 7362","to":"ITU-T ITU-T H.323","kind":"references","source":"IETF/RFC-7362/RFC-7362.txt"},{"from":"IETF RFC 2689","to":"ITU-T ITU-T H.324","kind":"references","source":"IETF/RFC-2689/RFC-2689.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T H.324","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3984","to":"ITU-T ITU-T H.324","kind":"references","source":"IETF/RFC-3984/RFC-3984.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T H.324","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 6184","to":"ITU-T ITU-T H.324","kind":"references","source":"IETF/RFC-6184/RFC-6184.txt"},{"from":"IETF RFC 2327","to":"ITU-T ITU-T H.332","kind":"references","source":"IETF/RFC-2327/RFC-2327.txt"},{"from":"IETF RFC 2805","to":"ITU-T ITU-T H.341","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 4542","to":"ITU-T ITU-T I.255.3","kind":"references","source":"IETF/RFC-4542/RFC-4542.txt"},{"from":"IETF RFC 3033","to":"ITU-T ITU-T I.320","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 2127","to":"ITU-T ITU-T I.330","kind":"references","source":"IETF/RFC-2127/RFC-2127.txt"},{"from":"IETF RFC 3393","to":"ITU-T ITU-T I.356","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 4737","to":"ITU-T ITU-T I.356","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5481","to":"ITU-T ITU-T I.356","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 3355","to":"ITU-T ITU-T I.363","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 5728","to":"ITU-T ITU-T I.363","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.363.1","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.363.1","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T I.363.1","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.363.1","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T I.363.1","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3336","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3337","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T I.363.2","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 2684","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3819","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-3819/RFC-3819.txt"},{"from":"IETF RFC 4259","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-4259/RFC-4259.txt"},{"from":"IETF RFC 4679","to":"ITU-T ITU-T I.363.5","kind":"references","source":"IETF/RFC-4679/RFC-4679.txt"},{"from":"IETF RFC 2684","to":"ITU-T ITU-T I.365.1","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3336","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3337","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-3337/RFC-3337.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.366.1","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3267","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-3267/RFC-3267.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 4867","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-4867/RFC-4867.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T I.366.2","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T I.371","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T I.371","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T I.371","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4717","to":"ITU-T ITU-T I.371","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 3432","to":"ITU-T ITU-T I.380","kind":"references","source":"IETF/RFC-3432/RFC-3432.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T I.432","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 5728","to":"ITU-T ITU-T I.432","kind":"references","source":"IETF/RFC-5728/RFC-5728.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T I.432.1","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 2684","to":"ITU-T ITU-T I.555","kind":"references","source":"IETF/RFC-2684/RFC-2684.txt"},{"from":"IETF RFC 4377","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4454","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-4454/RFC-4454.txt"},{"from":"IETF RFC 4717","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 5254","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-5254/RFC-5254.txt"},{"from":"IETF RFC 5851","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 6291","to":"ITU-T ITU-T I.610","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 2669","to":"ITU-T ITU-T J.112","kind":"references","source":"IETF/RFC-2669/RFC-2669.txt"},{"from":"IETF RFC 2670","to":"ITU-T ITU-T J.112","kind":"references","source":"IETF/RFC-2670/RFC-2670.txt"},{"from":"IETF RFC 3083","to":"ITU-T ITU-T J.112","kind":"references","source":"IETF/RFC-3083/RFC-3083.txt"},{"from":"IETF RFC 4722","to":"ITU-T ITU-T J.162","kind":"references","source":"IETF/RFC-4722/RFC-4722.txt"},{"from":"IETF RFC 3895","to":"ITU-T ITU-T M.140","kind":"references","source":"IETF/RFC-3895/RFC-3895.txt"},{"from":"IETF RFC 3896","to":"ITU-T ITU-T M.140","kind":"references","source":"IETF/RFC-3896/RFC-3896.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T M.140","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 5580","to":"ITU-T ITU-T M.140","kind":"references","source":"IETF/RFC-5580/RFC-5580.txt"},{"from":"IETF RFC 6291","to":"ITU-T ITU-T M.301","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 3878","to":"ITU-T ITU-T M.310","kind":"references","source":"IETF/RFC-3878/RFC-3878.txt"},{"from":"IETF RFC 4394","to":"ITU-T ITU-T M.310","kind":"references","source":"IETF/RFC-4394/RFC-4394.txt"},{"from":"IETF RFC 6988","to":"ITU-T ITU-T M.340","kind":"references","source":"IETF/RFC-6988/RFC-6988.txt"},{"from":"IETF RFC 7326","to":"ITU-T ITU-T M.340","kind":"references","source":"IETF/RFC-7326/RFC-7326.txt"},{"from":"IETF RFC 8014","to":"ITU-T ITU-T M.340","kind":"references","source":"IETF/RFC-8014/RFC-8014.txt"},{"from":"IETF RFC 4805","to":"ITU-T ITU-T O.162","kind":"references","source":"IETF/RFC-4805/RFC-4805.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.120","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.340","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.501","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.502","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 6035","to":"ITU-T ITU-T P.564","kind":"references","source":"IETF/RFC-6035/RFC-6035.txt"},{"from":"IETF RFC 6390","to":"ITU-T ITU-T P.564","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.564","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.581","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.800","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 5559","to":"ITU-T ITU-T P.800","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 6390","to":"ITU-T ITU-T P.800","kind":"references","source":"IETF/RFC-6390/RFC-6390.txt"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.810","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.831","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.832","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"ETSI TS 101 329-5 V1.1.2","to":"ITU-T ITU-T P.861","kind":"references","source":"ETSI/TS-101-329-5-V1.1.2/TS-101-329-5-V1.1.2.pdf"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.862","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.862.1","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.862.2","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 7266","to":"ITU-T ITU-T P.863","kind":"references","source":"IETF/RFC-7266/RFC-7266.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.118","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 7398","to":"ITU-T ITU-T Q.174","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.190","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 8859","to":"ITU-T ITU-T Q.190","kind":"references","source":"IETF/RFC-8859/RFC-8859.pdf"},{"from":"IETF RFC 8859","to":"ITU-T ITU-T Q.197","kind":"references","source":"IETF/RFC-8859/RFC-8859.txt"},{"from":"IETF RFC 3606","to":"ITU-T ITU-T Q.211","kind":"references","source":"IETF/RFC-3606/RFC-3606.txt"},{"from":"IETF RFC 2805","to":"ITU-T ITU-T Q.263","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.263","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.263","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3336","to":"ITU-T ITU-T Q.263","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.263","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 1755","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-1755/RFC-1755.txt"},{"from":"IETF RFC 2331","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-2331/RFC-2331.txt"},{"from":"IETF RFC 2363","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-2363/RFC-2363.txt"},{"from":"IETF RFC 2364","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-2364/RFC-2364.txt"},{"from":"IETF RFC 2514","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-2514/RFC-2514.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3033","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 3108","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-3108/RFC-3108.txt"},{"from":"IETF RFC 3355","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-3355/RFC-3355.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.293","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.294","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.294","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.294","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3033","to":"ITU-T ITU-T Q.295","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 2382","to":"ITU-T ITU-T Q.296","kind":"references","source":"IETF/RFC-2382/RFC-2382.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.296","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.296","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.296","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3033","to":"ITU-T ITU-T Q.297","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 5431","to":"ITU-T ITU-T Q.330","kind":"references","source":"IETF/RFC-5431/RFC-5431.txt"},{"from":"ETSI TS 101 270-1 V1.2.1","to":"ITU-T ITU-T Q.552","kind":"references","source":"ETSI/TS-101-270-1-V1.2.1/TS-101-270-1-V1.2.1.pdf"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T Q.700","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T Q.700","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 2719","to":"ITU-T ITU-T Q.704","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 3868","to":"ITU-T ITU-T Q.713","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 3868","to":"ITU-T ITU-T Q.714","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.724","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.724","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4458","to":"ITU-T ITU-T Q.732.2","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.737","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3204","to":"ITU-T ITU-T Q.761","kind":"references","source":"IETF/RFC-3204/RFC-3204.txt"},{"from":"IETF RFC 2848","to":"ITU-T ITU-T Q.763","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.763","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.763","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.763","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.763","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3372","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-3372/RFC-3372.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3578","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-3578/RFC-3578.txt"},{"from":"IETF RFC 5341","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-5341/RFC-5341.txt"},{"from":"IETF RFC 7375","to":"ITU-T ITU-T Q.764","kind":"references","source":"IETF/RFC-7375/RFC-7375.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.765","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.765","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.765","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.765.5","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.767","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 3578","to":"ITU-T ITU-T Q.767","kind":"references","source":"IETF/RFC-3578/RFC-3578.txt"},{"from":"IETF RFC 3482","to":"ITU-T ITU-T Q.769.1","kind":"references","source":"IETF/RFC-3482/RFC-3482.txt"},{"from":"IETF RFC 3868","to":"ITU-T ITU-T Q.771","kind":"references","source":"IETF/RFC-3868/RFC-3868.txt"},{"from":"IETF RFC 2924","to":"ITU-T ITU-T Q.825","kind":"references","source":"IETF/RFC-2924/RFC-2924.txt"},{"from":"IETF RFC 3326","to":"ITU-T ITU-T Q.850","kind":"references","source":"IETF/RFC-3326/RFC-3326.txt"},{"from":"IETF RFC 3398","to":"ITU-T ITU-T Q.850","kind":"references","source":"IETF/RFC-3398/RFC-3398.txt"},{"from":"IETF RFC 4411","to":"ITU-T ITU-T Q.850","kind":"references","source":"IETF/RFC-4411/RFC-4411.txt"},{"from":"IETF RFC 4458","to":"ITU-T ITU-T Q.850","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 3336","to":"ITU-T ITU-T Q.921","kind":"references","source":"IETF/RFC-3336/RFC-3336.txt"},{"from":"IETF RFC 2427","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2954","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3034","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-3034/RFC-3034.txt"},{"from":"IETF RFC 4591","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4618","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"ITU-T ITU-T Q.922","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 3033","to":"ITU-T ITU-T Q.923","kind":"references","source":"IETF/RFC-3033/RFC-3033.txt"},{"from":"IETF RFC 2128","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-2128/RFC-2128.txt"},{"from":"IETF RFC 2719","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-2719/RFC-2719.txt"},{"from":"IETF RFC 2805","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 4197","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-4197/RFC-4197.txt"},{"from":"IETF RFC 4458","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-4458/RFC-4458.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5456","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-5456/RFC-5456.txt"},{"from":"IETF RFC 7195","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-7195/RFC-7195.txt"},{"from":"IETF RFC 7375","to":"ITU-T ITU-T Q.931","kind":"references","source":"IETF/RFC-7375/RFC-7375.txt"},{"from":"IETF RFC 2115","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-2115/RFC-2115.txt"},{"from":"IETF RFC 2427","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-2427/RFC-2427.txt"},{"from":"IETF RFC 2954","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 4591","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-4591/RFC-4591.txt"},{"from":"IETF RFC 4618","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-4618/RFC-4618.txt"},{"from":"IETF RFC 4619","to":"ITU-T ITU-T Q.933","kind":"references","source":"IETF/RFC-4619/RFC-4619.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T T.101","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 2122","to":"ITU-T ITU-T T.107","kind":"references","source":"IETF/RFC-2122/RFC-2122.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T T.120","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 2793","to":"ITU-T ITU-T T.140","kind":"references","source":"IETF/RFC-2793/RFC-2793.txt"},{"from":"IETF RFC 2805","to":"ITU-T ITU-T T.140","kind":"references","source":"IETF/RFC-2805/RFC-2805.txt"},{"from":"IETF RFC 4103","to":"ITU-T ITU-T T.140","kind":"references","source":"IETF/RFC-4103/RFC-4103.txt"},{"from":"IETF RFC 5194","to":"ITU-T ITU-T T.140","kind":"references","source":"IETF/RFC-5194/RFC-5194.txt"},{"from":"IETF RFC 2806","to":"ITU-T ITU-T V.110","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 3017","to":"ITU-T ITU-T V.110","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 2806","to":"ITU-T ITU-T V.120","kind":"references","source":"IETF/RFC-2806/RFC-2806.txt"},{"from":"IETF RFC 3017","to":"ITU-T ITU-T V.120","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T V.150.1","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T V.150.1","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 4733","to":"ITU-T ITU-T V.152","kind":"references","source":"IETF/RFC-4733/RFC-4733.txt"},{"from":"IETF RFC 4734","to":"ITU-T ITU-T V.152","kind":"references","source":"IETF/RFC-4734/RFC-4734.txt"},{"from":"IETF RFC 1888","to":"ITU-T ITU-T X.121","kind":"references","source":"IETF/RFC-1888/RFC-1888.txt"},{"from":"IETF RFC 2848","to":"ITU-T ITU-T X.121","kind":"references","source":"IETF/RFC-2848/RFC-2848.txt"},{"from":"IETF RFC 2954","to":"ITU-T ITU-T X.121","kind":"references","source":"IETF/RFC-2954/RFC-2954.txt"},{"from":"IETF RFC 3017","to":"ITU-T ITU-T X.121","kind":"references","source":"IETF/RFC-3017/RFC-3017.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T X.121","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 9393","to":"ITU-T ITU-T X.152","kind":"references","source":"IETF/RFC-9393/RFC-9393.txt"},{"from":"IETF RFC 2828","to":"ITU-T ITU-T X.200","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 4949","to":"ITU-T ITU-T X.200","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5921","to":"ITU-T ITU-T X.200","kind":"references","source":"IETF/RFC-5921/RFC-5921.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.208","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 3850","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4151","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-4151/RFC-4151.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5934","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 6010","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 8126","to":"ITU-T ITU-T X.208","kind":"references","source":"IETF/RFC-8126/RFC-8126.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.209","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T X.213","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T X.213","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T X.213","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 1950","to":"ITU-T ITU-T X.224","kind":"references","source":"IETF/RFC-1950/RFC-1950.txt"},{"from":"IETF RFC 1950","to":"ITU-T ITU-T X.244","kind":"references","source":"IETF/RFC-1950/RFC-1950.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.400","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 3854","to":"ITU-T ITU-T X.400","kind":"references","source":"IETF/RFC-3854/RFC-3854.txt"},{"from":"IETF RFC 3855","to":"ITU-T ITU-T X.400","kind":"references","source":"IETF/RFC-3855/RFC-3855.txt"},{"from":"IETF RFC 2156","to":"ITU-T ITU-T X.408","kind":"references","source":"IETF/RFC-2156/RFC-2156.txt"},{"from":"IETF RFC 2459","to":"ITU-T ITU-T X.411","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.411","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.411","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5912","to":"ITU-T ITU-T X.411","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 4949","to":"ITU-T ITU-T X.419","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 2422","to":"ITU-T ITU-T X.420","kind":"references","source":"IETF/RFC-2422/RFC-2422.txt"},{"from":"IETF RFC 3551","to":"ITU-T ITU-T X.420","kind":"references","source":"IETF/RFC-3551/RFC-3551.txt"},{"from":"IETF RFC 3802","to":"ITU-T ITU-T X.420","kind":"references","source":"IETF/RFC-3802/RFC-3802.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.420","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4949","to":"ITU-T ITU-T X.420","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.500","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2312","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3671","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3850","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4522","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5750","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5755","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6125","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 8550","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 9562","to":"ITU-T ITU-T X.500","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.501","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.501","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2252","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2256","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2312","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2459","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3039","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3114","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3671","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3703","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3739","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4158","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4306","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4346","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5246","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5485","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5755","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 6010","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6125","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 8446","to":"ITU-T ITU-T X.501","kind":"references","source":"IETF/RFC-8446/RFC-8446.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 132-1 V1.3.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-132-1-V1.3.1/EN-319-132-1-V1.3.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-2 V2.6.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-411-2-V2.6.1/EN-319-411-2-V2.6.1.pdf"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 412-3 V1.3.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf"},{"from":"ETSI EN 319 412-5 V2.6.0","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 903 V1.3.2","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TS-101-903-V1.3.2/TS-101-903-V1.3.2.pdf"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 412-6 V1.2.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TS-119-412-6-V1.2.1/TS-119-412-6-V1.2.1.pdf"},{"from":"ETSI TS 119 602 V1.1.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TS-119-602-V1.1.1/TS-119-602-V1.1.1.pdf"},{"from":"ETSI TS 119 612 V2.4.1","to":"ITU-T ITU-T X.509","kind":"references","source":"ETSI/TS-119-612-V2.4.1/TS-119-612-V2.4.1.pdf"},{"from":"IETF RFC 2256","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2312","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2459","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2527","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2527/RFC-2527.txt"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2802","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2802/RFC-2802.txt"},{"from":"IETF RFC 2828","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2828/RFC-2828.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3039","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3075","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3075/RFC-3075.txt"},{"from":"IETF RFC 3114","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3114/RFC-3114.txt"},{"from":"IETF RFC 3126","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3126/RFC-3126.txt"},{"from":"IETF RFC 3169","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3169/RFC-3169.txt"},{"from":"IETF RFC 3275","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3275/RFC-3275.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3281","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3281/RFC-3281.txt"},{"from":"IETF RFC 3379","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3379/RFC-3379.txt"},{"from":"IETF RFC 3546","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3546/RFC-3546.txt"},{"from":"IETF RFC 3647","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3647/RFC-3647.txt"},{"from":"IETF RFC 3739","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4043","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4158","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4158/RFC-4158.txt"},{"from":"IETF RFC 4171","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4171/RFC-4171.txt"},{"from":"IETF RFC 4210","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4210/RFC-4210.txt"},{"from":"IETF RFC 4306","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4306/RFC-4306.txt"},{"from":"IETF RFC 4346","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4346/RFC-4346.txt"},{"from":"IETF RFC 4366","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4366/RFC-4366.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 4572","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4572/RFC-4572.txt"},{"from":"IETF RFC 4949","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-4949/RFC-4949.txt"},{"from":"IETF RFC 5091","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5091/RFC-5091.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5755","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5914","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5924","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5924/RFC-5924.txt"},{"from":"IETF RFC 5934","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5937","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-5937/RFC-5937.txt"},{"from":"IETF RFC 6066","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6066/RFC-6066.txt"},{"from":"IETF RFC 6120","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6120/RFC-6120.txt"},{"from":"IETF RFC 6125","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6125/RFC-6125.txt"},{"from":"IETF RFC 6484","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6484/RFC-6484.txt"},{"from":"IETF RFC 6818","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6818/RFC-6818.txt"},{"from":"IETF RFC 6837","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6837/RFC-6837.txt"},{"from":"IETF RFC 6844","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-6844/RFC-6844.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 9525","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9608","to":"ITU-T ITU-T X.509","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"ARF TS02 V1.0.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ARF/TS02-V1.0.1/TS02-V1.0.1.md"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 412-1 V1.7.0","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/EN-319-412-1-V1.7.0/EN-319-412-1-V1.7.0.pdf"},{"from":"ETSI EN 319 412-2 V2.4.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/EN-319-412-2-V2.4.1/EN-319-412-2-V2.4.1.pdf"},{"from":"ETSI EN 319 412-3 V1.3.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/EN-319-412-3-V1.3.1/EN-319-412-3-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 101 861 V1.4.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/TS-101-861-V1.4.1/TS-101-861-V1.4.1.pdf"},{"from":"ETSI TS 119 411-8 V1.1.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/TS-119-411-8-V1.1.1/TS-119-411-8-V1.1.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"ITU-T ITU-T X.520","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"IETF RFC 2247","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2247/RFC-2247.txt"},{"from":"IETF RFC 2252","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2252/RFC-2252.txt"},{"from":"IETF RFC 2256","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 2312","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2312/RFC-2312.txt"},{"from":"IETF RFC 2459","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2459/RFC-2459.txt"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 3039","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3671","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3671/RFC-3671.txt"},{"from":"IETF RFC 3703","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3703/RFC-3703.txt"},{"from":"IETF RFC 3739","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 3850","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-3850/RFC-3850.txt"},{"from":"IETF RFC 4043","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.520","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 2256","to":"ITU-T ITU-T X.521","kind":"references","source":"IETF/RFC-2256/RFC-2256.txt"},{"from":"IETF RFC 4519","to":"ITU-T ITU-T X.521","kind":"references","source":"IETF/RFC-4519/RFC-4519.txt"},{"from":"IETF RFC 3279","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-3279/RFC-3279.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 4043","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4334","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4357","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-4357/RFC-4357.txt"},{"from":"IETF RFC 4491","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-4491/RFC-4491.txt"},{"from":"IETF RFC 4871","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-4871/RFC-4871.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 7515","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7519","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-7519/RFC-7519.txt"},{"from":"IETF RFC 9090","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9562","to":"ITU-T ITU-T X.660","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9562","to":"ITU-T ITU-T X.667","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9090","to":"ITU-T ITU-T X.672","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI EN 319 412-5 V2.6.0","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/EN-319-412-5-V2.6.0/EN-319-412-5-V2.6.0.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"ETSI TS 119 411-5 V2.1.1","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/TS-119-411-5-V2.1.1/TS-119-411-5-V2.1.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 495 V1.7.1","to":"ITU-T ITU-T X.680","kind":"references","source":"ETSI/TS-119-495-V1.7.1/TS-119-495-V1.7.1.pdf"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3039","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3039/RFC-3039.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3642","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3642/RFC-3642.txt"},{"from":"IETF RFC 3739","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-3739/RFC-3739.txt"},{"from":"IETF RFC 4043","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4043/RFC-4043.txt"},{"from":"IETF RFC 4120","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4325","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4334","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4334/RFC-4334.txt"},{"from":"IETF RFC 4492","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4511","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4511/RFC-4511.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4537","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5246","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5408","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5480","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"IETF RFC 5485","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5649","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5750","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5750/RFC-5750.txt"},{"from":"IETF RFC 5751","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5753","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5755","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5877","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5911","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5911/RFC-5911.txt"},{"from":"IETF RFC 5912","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5912/RFC-5912.txt"},{"from":"IETF RFC 5914","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5914/RFC-5914.txt"},{"from":"IETF RFC 5915","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5934","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5940","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6010","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6031","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6961","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 7030","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8411","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8411/RFC-8411.txt"},{"from":"IETF RFC 8418","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8550","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8550/RFC-8550.txt"},{"from":"IETF RFC 8551","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8619","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8696","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 9090","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9162","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9562","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-9562/RFC-9562.txt"},{"from":"IETF RFC 9608","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"ITU-T ITU-T X.680","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.681","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5649","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5940","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6031","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ITU-T ITU-T X.681","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5649","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5940","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6031","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ITU-T ITU-T X.682","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.683","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5649","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5649/RFC-5649.txt"},{"from":"IETF RFC 5753","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5753/RFC-5753.txt"},{"from":"IETF RFC 5915","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5940","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5940/RFC-5940.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 6031","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 8226","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-8226/RFC-8226.txt"},{"from":"IETF RFC 8551","to":"ITU-T ITU-T X.683","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"ETSI EN 319 122-1 V1.3.1","to":"ITU-T ITU-T X.690","kind":"references","source":"ETSI/EN-319-122-1-V1.3.1/EN-319-122-1-V1.3.1.pdf"},{"from":"ETSI TR 102 272 V1.1.1","to":"ITU-T ITU-T X.690","kind":"references","source":"ETSI/TR-102-272-V1.1.1/TR-102-272-V1.1.1.pdf"},{"from":"IETF RFC 2254","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-2254/RFC-2254.txt"},{"from":"IETF RFC 2560","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-2560/RFC-2560.txt"},{"from":"IETF RFC 2632","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-2632/RFC-2632.txt"},{"from":"IETF RFC 2885","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-2885/RFC-2885.txt"},{"from":"IETF RFC 2986","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-2986/RFC-2986.txt"},{"from":"IETF RFC 3015","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3015/RFC-3015.txt"},{"from":"IETF RFC 3125","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3125/RFC-3125.txt"},{"from":"IETF RFC 3280","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3280/RFC-3280.txt"},{"from":"IETF RFC 3525","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3525/RFC-3525.txt"},{"from":"IETF RFC 3641","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3641/RFC-3641.txt"},{"from":"IETF RFC 3779","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3779/RFC-3779.txt"},{"from":"IETF RFC 3971","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3971/RFC-3971.txt"},{"from":"IETF RFC 3972","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-3972/RFC-3972.txt"},{"from":"IETF RFC 4120","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4120/RFC-4120.txt"},{"from":"IETF RFC 4178","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4178/RFC-4178.txt"},{"from":"IETF RFC 4325","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4325/RFC-4325.txt"},{"from":"IETF RFC 4462","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4462/RFC-4462.txt"},{"from":"IETF RFC 4492","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4492/RFC-4492.txt"},{"from":"IETF RFC 4515","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4515/RFC-4515.txt"},{"from":"IETF RFC 4517","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4517/RFC-4517.txt"},{"from":"IETF RFC 4522","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4522/RFC-4522.txt"},{"from":"IETF RFC 4537","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4537/RFC-4537.txt"},{"from":"IETF RFC 4556","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-4556/RFC-4556.txt"},{"from":"IETF RFC 5126","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5126/RFC-5126.txt"},{"from":"IETF RFC 5246","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5246/RFC-5246.txt"},{"from":"IETF RFC 5280","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5280/RFC-5280.txt"},{"from":"IETF RFC 5408","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5408/RFC-5408.txt"},{"from":"IETF RFC 5409","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5409/RFC-5409.txt"},{"from":"IETF RFC 5485","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5485/RFC-5485.txt"},{"from":"IETF RFC 5751","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5751/RFC-5751.txt"},{"from":"IETF RFC 5755","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5755/RFC-5755.txt"},{"from":"IETF RFC 5877","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5877/RFC-5877.txt"},{"from":"IETF RFC 5915","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5915/RFC-5915.txt"},{"from":"IETF RFC 5934","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5934/RFC-5934.txt"},{"from":"IETF RFC 5958","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5958/RFC-5958.txt"},{"from":"IETF RFC 5967","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-5967/RFC-5967.txt"},{"from":"IETF RFC 6010","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6010/RFC-6010.txt"},{"from":"IETF RFC 6031","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6031/RFC-6031.txt"},{"from":"IETF RFC 6482","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6482/RFC-6482.txt"},{"from":"IETF RFC 6486","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6486/RFC-6486.txt"},{"from":"IETF RFC 6698","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6698/RFC-6698.txt"},{"from":"IETF RFC 6839","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 6960","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6960/RFC-6960.txt"},{"from":"IETF RFC 6961","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-6961/RFC-6961.txt"},{"from":"IETF RFC 7030","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7030/RFC-7030.txt"},{"from":"IETF RFC 7049","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7049/RFC-7049.txt"},{"from":"IETF RFC 7170","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7170/RFC-7170.txt"},{"from":"IETF RFC 7250","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7250/RFC-7250.txt"},{"from":"IETF RFC 7468","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7468/RFC-7468.txt"},{"from":"IETF RFC 7515","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7515/RFC-7515.txt"},{"from":"IETF RFC 7517","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-7517/RFC-7517.txt"},{"from":"IETF RFC 8418","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8418/RFC-8418.txt"},{"from":"IETF RFC 8419","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8419/RFC-8419.txt"},{"from":"IETF RFC 8422","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8422/RFC-8422.txt"},{"from":"IETF RFC 8551","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8551/RFC-8551.txt"},{"from":"IETF RFC 8572","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8572/RFC-8572.txt"},{"from":"IETF RFC 8619","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8619/RFC-8619.txt"},{"from":"IETF RFC 8696","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8696/RFC-8696.txt"},{"from":"IETF RFC 8705","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8705/RFC-8705.txt"},{"from":"IETF RFC 8949","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-8949/RFC-8949.txt"},{"from":"IETF RFC 9090","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9090/RFC-9090.txt"},{"from":"IETF RFC 9162","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9162/RFC-9162.txt"},{"from":"IETF RFC 9277","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9277/RFC-9277.txt"},{"from":"IETF RFC 9440","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9440/RFC-9440.txt"},{"from":"IETF RFC 9525","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9525/RFC-9525.txt"},{"from":"IETF RFC 9608","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9608/RFC-9608.txt"},{"from":"IETF RFC 9999","to":"ITU-T ITU-T X.690","kind":"references","source":"IETF/RFC-9999/RFC-9999.txt"},{"from":"IETF RFC 5480","to":"ITU-T ITU-T X.691","kind":"references","source":"IETF/RFC-5480/RFC-5480.txt"},{"from":"ETSI TS 101 270-2 V1.1.1","to":"ITU-T ITU-T X.700","kind":"references","source":"ETSI/TS-101-270-2-V1.1.1/TS-101-270-2-V1.1.1.pdf"},{"from":"IETF RFC 5674","to":"ITU-T ITU-T X.733","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 6632","to":"ITU-T ITU-T X.733","kind":"references","source":"IETF/RFC-6632/RFC-6632.txt"},{"from":"IETF RFC 5674","to":"ITU-T ITU-T X.736","kind":"references","source":"IETF/RFC-5674/RFC-5674.txt"},{"from":"IETF RFC 2564","to":"ITU-T ITU-T X.744","kind":"references","source":"IETF/RFC-2564/RFC-2564.txt"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ITU-T ITU-T X.800","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ITU-T ITU-T X.842","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"ETSI EN 319 411-1 V1.5.1","to":"ITU-T ITU-T X.843","kind":"references","source":"ETSI/EN-319-411-1-V1.5.1/EN-319-411-1-V1.5.1.pdf"},{"from":"IETF RFC 6839","to":"ITU-T ITU-T X.891","kind":"references","source":"IETF/RFC-6839/RFC-6839.txt"},{"from":"IETF RFC 5976","to":"ITU-T ITU-T Y.122","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5860","to":"ITU-T ITU-T Y.130","kind":"references","source":"IETF/RFC-5860/RFC-5860.txt"},{"from":"IETF RFC 4031","to":"ITU-T ITU-T Y.131","kind":"references","source":"IETF/RFC-4031/RFC-4031.txt"},{"from":"IETF RFC 4176","to":"ITU-T ITU-T Y.131","kind":"references","source":"IETF/RFC-4176/RFC-4176.txt"},{"from":"IETF RFC 5654","to":"ITU-T ITU-T Y.140","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 4717","to":"ITU-T ITU-T Y.141","kind":"references","source":"IETF/RFC-4717/RFC-4717.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T Y.141","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 5087","to":"ITU-T ITU-T Y.145","kind":"references","source":"IETF/RFC-5087/RFC-5087.txt"},{"from":"IETF RFC 3393","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-3393/RFC-3393.txt"},{"from":"IETF RFC 4150","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-4150/RFC-4150.txt"},{"from":"IETF RFC 4737","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-4737/RFC-4737.txt"},{"from":"IETF RFC 5481","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5481/RFC-5481.txt"},{"from":"IETF RFC 5559","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5559/RFC-5559.txt"},{"from":"IETF RFC 5560","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5560/RFC-5560.txt"},{"from":"IETF RFC 5835","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5835/RFC-5835.txt"},{"from":"IETF RFC 5975","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 6049","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-6049/RFC-6049.txt"},{"from":"IETF RFC 6703","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-6703/RFC-6703.txt"},{"from":"IETF RFC 6798","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-6798/RFC-6798.txt"},{"from":"IETF RFC 7398","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-7398/RFC-7398.txt"},{"from":"IETF RFC 7679","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-7679/RFC-7679.txt"},{"from":"IETF RFC 7680","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-7680/RFC-7680.txt"},{"from":"IETF RFC 7799","to":"ITU-T ITU-T Y.154","kind":"references","source":"IETF/RFC-7799/RFC-7799.txt"},{"from":"IETF RFC 5951","to":"ITU-T ITU-T Y.156","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 3429","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-3429/RFC-3429.txt"},{"from":"IETF RFC 4377","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-4377/RFC-4377.txt"},{"from":"IETF RFC 4378","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-4378/RFC-4378.txt"},{"from":"IETF RFC 5704","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-5704/RFC-5704.txt"},{"from":"IETF RFC 7276","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7325","to":"ITU-T ITU-T Y.171","kind":"references","source":"IETF/RFC-7325/RFC-7325.txt"},{"from":"IETF RFC 5851","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-5851/RFC-5851.txt"},{"from":"IETF RFC 5951","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-5951/RFC-5951.txt"},{"from":"IETF RFC 6136","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-6136/RFC-6136.txt"},{"from":"IETF RFC 6291","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-6291/RFC-6291.txt"},{"from":"IETF RFC 6329","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-6329/RFC-6329.txt"},{"from":"IETF RFC 6371","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-6371/RFC-6371.txt"},{"from":"IETF RFC 6374","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-6374/RFC-6374.txt"},{"from":"IETF RFC 7174","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-7174/RFC-7174.txt"},{"from":"IETF RFC 7276","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-7276/RFC-7276.txt"},{"from":"IETF RFC 7455","to":"ITU-T ITU-T Y.173","kind":"references","source":"IETF/RFC-7455/RFC-7455.txt"},{"from":"IETF RFC 5975","to":"ITU-T ITU-T Y.217","kind":"references","source":"IETF/RFC-5975/RFC-5975.txt"},{"from":"IETF RFC 5976","to":"ITU-T ITU-T Y.217","kind":"references","source":"IETF/RFC-5976/RFC-5976.txt"},{"from":"IETF RFC 5654","to":"ITU-T ITU-T Y.261","kind":"references","source":"IETF/RFC-5654/RFC-5654.txt"},{"from":"IETF RFC 7087","to":"ITU-T ITU-T Y.261","kind":"references","source":"IETF/RFC-7087/RFC-7087.txt"},{"from":"ARF TS11 V1.0.1","to":"OpenID OpenID Federation V1.0","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"legal:2026-1731","to":"OpenID OpenID4VC-HAIP V1.0","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS12 V1.0.1","to":"OpenID OpenID4VC-HAIP V1.0","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"OpenID OpenID4VC-HAIP V1.0","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"OpenID OpenID4VC-HAIP V1.0","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"OpenID OpenID4VC-HAIP V1.0","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"legal:2026-1731","to":"OpenID OpenID4VCI V1.0","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS01 V1.2","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS01-V1.2/TS01-V1.2.md"},{"from":"ARF TS03 V1.5.2","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS03-V1.5.2/TS03-V1.5.2.md"},{"from":"ARF TS10 V1.2","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS11 V1.0.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ARF TS12 V1.0.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ARF TS14 V1.0","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 471 V1.1.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ETSI/TS-119-471-V1.1.1/TS-119-471-V1.1.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF SD-JWT VC","to":"OpenID OpenID4VCI V1.0","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"legal:2026-1731","to":"OpenID OpenID4VP V1.0","kind":"cites","source":"implementing-acts/2026-1731/2026-1731.md"},{"from":"ARF TS05 V1.2.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS05-V1.2.1/TS05-V1.2.1.md"},{"from":"ARF TS07 V0.11","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS07-V0.11/TS07-V0.11.md"},{"from":"ARF TS10 V1.2","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS10-V1.2/TS10-V1.2.md"},{"from":"ARF TS11 V1.0.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS11-V1.0.1/TS11-V1.0.1.md"},{"from":"ARF TS12 V1.0.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS12-V1.0.1/TS12-V1.0.1.md"},{"from":"ARF TS13","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS13/TS13-V1.0.1.md"},{"from":"ARF TS14 V1.0","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ARF/TS14-V1.0/TS14-V1.0.md"},{"from":"ETSI TR 119 476 V1.2.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TR-119-476-V1.2.1/TR-119-476-V1.2.1.pdf"},{"from":"ETSI TS 119 432 V1.3.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TS-119-432-V1.3.1/TS-119-432-V1.3.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 472-3 V1.1.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TS-119-472-3-V1.1.1/TS-119-472-3-V1.1.1.pdf"},{"from":"ETSI TS 119 475 V1.2.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TS-119-475-V1.2.1/TS-119-475-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"OpenID OpenID4VP V1.0","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"legal:2024-2977","to":"W3C vc-data-model V1.1","kind":"cites","source":"implementing-acts/2024-2977/2024-2977.md"},{"from":"legal:2024-2979","to":"W3C vc-data-model V1.1","kind":"cites","source":"implementing-acts/2024-2979/2024-2979.md"},{"from":"ETSI TS 119 182-1 V1.2.1","to":"W3C vc-data-model V1.1","kind":"references","source":"ETSI/TS-119-182-1-V1.2.1/TS-119-182-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-1 V1.2.1","to":"W3C vc-data-model V1.1","kind":"references","source":"ETSI/TS-119-472-1-V1.2.1/TS-119-472-1-V1.2.1.pdf"},{"from":"ETSI TS 119 472-2 V1.2.1","to":"W3C vc-data-model V1.1","kind":"references","source":"ETSI/TS-119-472-2-V1.2.1/TS-119-472-2-V1.2.1.pdf"},{"from":"ETSI TS 119 478 V1.1.1","to":"W3C vc-data-model V1.1","kind":"references","source":"ETSI/TS-119-478-V1.1.1/TS-119-478-V1.1.1.pdf"},{"from":"IETF SD-JWT VC","to":"W3C vc-data-model V1.1","kind":"references","source":"IETF/SD-JWT-VC/SD-JWT-VC.html"},{"from":"IETF SD-JWT","to":"W3C vc-data-model V1.1","kind":"references","source":"IETF/SD-JWT/SD-JWT.txt"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS01 V1.2","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS02 V1.0.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS03 V1.5.2","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS04 V1.0.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS05 V1.2.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS06 V1.0.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS07 V0.11","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS08 V0.11","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS09 V1.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS10 V1.2","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS11 V1.0.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS12 V1.0.1","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS13","kind":"references","source":"ARF/technical-specifications"},{"from":"ARF EC technical specifications (TS01–TS14) V3.0.0","to":"ARF TS14 V1.0","kind":"references","source":"ARF/technical-specifications"},{"from":"legal:2024-2979","to":"ARF EC technical specifications (TS01–TS14) V3.0.0","kind":"related","source":"corpus:arf-wallet-acts"}]}
